Linux kernel security needs work: http://www.washingtonpost.com/sf/business/2015/11/05/net-of-insecurity-the-kernel-of-the-argument/ … join the Kernel Self Protection Project: http://www.openwall.com/lists/kernel-hardening/2015/11/05/1 …
-
-
Replying to @kees_cook
@kees_cook The ARM implementations of KERNEXEC and UDEREF would be a good place to start. Insignificant performance hit and no segmentation.1 reply 0 retweets 0 likes -
Replying to @CopperheadOS
@kees_cook Linus probably wouldn't veto using ARM memory domains as he will with segmentation.2 replies 0 retweets 0 likes -
Replying to @CopperheadOS
@CopperheadSec But rmk might veto it. http://lists.infradead.org/pipermail/linux-arm-kernel/2015-August/366632.html …2 replies 0 retweets 1 like -
Replying to @kees_cook
@kees_cook Well, maybe@grsecurity (spender) would be willing to review your changes and sign off on stuff. Google could just pay for it.1 reply 0 retweets 0 likes -
Replying to @CopperheadOS
@kees_cook@grsecurity Could just do it via https://www.google.com/about/appsecurity/patch-rewards/ … if you wanted to skip the business side bureaucracy.1 reply 0 retweets 0 likes -
Replying to @CopperheadOS
@kees_cook There seems to be an assumption that@grsecurity and@paxteam aren't willing to help upstream stuff, but has anyone asked?2 replies 0 retweets 0 likes -
Replying to @CopperheadOS
@kees_cook@grsecurity@paxteam Obviously they wouldn't want be the ones actually submitting it and dealing with upstream.1 reply 0 retweets 0 likes -
Replying to @CopperheadOS
@kees_cook@grsecurity@paxteam If Google simply paid to have features extracted into independent patches, they would probably do it...2 replies 0 retweets 0 likes -
Replying to @CopperheadOS
@kees_cook@grsecurity@paxteam And just pay Emese to upstream and maintain -fsanitize=size-overflow as part of GCC? Seems simple enough.2 replies 0 retweets 0 likes
@CopperheadSec I look forward to Emese's Core Infrastructure Initiative proposal! Seriously, let's get it in, and get people paid.
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.