![Niklas B Profile](https://pbs.twimg.com/profile_images/980119921857323011/ZacU1faE_x96.jpg)
Niklas B
@_niklasb
Followers
15K
Following
6K
Statuses
3K
We at @dfsec_com are currently looking for a senior Linux kernel researcher, feel free to DM if you’re curious :)
1
29
96
DMs were apparently disabled, but fixed now
We at @dfsec_com are currently looking for a senior Linux kernel researcher, feel free to DM if you’re curious :)
1
1
13
Software transactional memory is probably the one thing I miss the most from my Haskell developer times. IMO it is the most intuitive way to write concurrent code by far. It‘s wild to see it implemented in such a complex context as C++, amazing effort
0
1
15
@m40282845 @adhsec yeah that’s for sure, WPA and unencrypted networks are rejected, question is what else
0
0
0
@jduck @5aelo @farazsth98 @adhsec @silviocesare @mboehme_ again, there is no bug here and the compiler produces correct output. FATAL is surely noreturn. UB is introduced in some unrelated place
0
0
0
@jduck @5aelo @farazsth98 @adhsec @silviocesare @mboehme_ There was/is no actual issue/bug in the code (the switch is exhaustive), what is being considered here are just ideas to nudge the compiler to reliably produce a compilation output that has the intended security properties (which are a superset of those provided by C++ itself)
2
0
2
@5aelo @jduck @farazsth98 @adhsec @silviocesare @mboehme_ But of course you are likely heavily relying on this specific compiler behavior in countless other places in a similar fashion anyway
0
0
2
@5aelo @jduck @farazsth98 @adhsec @silviocesare @mboehme_ The real fix to me seems to change the enum to an `enum X : int { … }`
1
0
1