lol, grsecurity went fully closed, probably in an attempt to stop the Kernel Self Protection Project from making it obsolete
4
6
1
22
It is in 4.8.17, and 4.7.10, and 4.6.5 (July last year), you're really up for complaining about whatever right?
1
christ this whole thing is dumb. here’s a challenge: give me a kernel binary. not the secret jewels, just a binary, but it has to have[..]
1
1
[..]all the protections of the commercial version enabled. and i will break it, if only to take out my annoyance.
1
1
Replying to @comex @marcan42 @lazytyped
you can compile a kernel so cut your teeth on the public version first and see how you fare then we'll talk about the next step.

Apr 29, 2017 · 9:23 AM UTC

2
2
Replying to @paxteam @marcan42 @lazytyped
I will if you insist, though I’d rather not waste my time developing approaches that are mitigated by your other stuff.
Replying to @paxteam @marcan42 @lazytyped
Of course, that is exactly what /you/ want: to be able to claim that my results are invalid for some reason or other.
1
1
if you're unsure if a given exploit technique is in scope just ask me.
2
more replies