UBSan support in just-released Linux kernel http://lwn.net/Articles/673317/ …
-
-
Replying to @johnregehr
@johnregehr@RichFelker For hardening or debug? Ubsan memory structures are read write and could be troublesome.1 reply 0 retweets 0 likes -
Replying to @sortiecat
@sortiecat@johnregehr@RichFelker Which memory structures?1 reply 0 retweets 0 likes -
Replying to @CopperheadOS
@CopperheadSec For each source location, writable string pointer + line no + whether breakpoint disabled @ohnregehr@RichFelker1 reply 0 retweets 1 like -
Replying to @sortiecat
@CopperheadSec@RichFelker Not issue for gcc libubsan, not meant for production, but becomes a concern when used with secure handlers1 reply 0 retweets 0 likes -
Replying to @sortiecat
@sortiecat@RichFelker The debugging mode isn't for hardening. The trapping mode is for hardening. There's a reason for them being distinct.2 replies 0 retweets 0 likes -
Replying to @CopperheadOS
@sortiecat@RichFelker Haven't looked at the kernel patches, but it's easy to tell which form they're using. Ideally both would be exposed.1 reply 0 retweets 0 likes -
Replying to @CopperheadOS
@sortiecat@RichFelker In the non-debug mode there's either a trapping instruction or a function call with no parameters to do the same.1 reply 0 retweets 0 likes
@CopperheadSec @sortiecat Note: function call can even be unsafe if the attacker managed to clobber the GOT in the process of causing UB.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.