News for hackers. Stuff that matters.

A comment on Grsecurity Developer Spender's Feelings on the State of Linux Security. Parent comment

Re:Grsecurity Developer Spender's Feelings on the State of L... by fulafel on Sunday November 08, 2015 @02:46AM (#10527874)
Or you could just use a memory safe language instead of getting into the C mitigation arms race.

Time and time again mitigation techs have gotten widely deployed, exploits have caught up, it's a perpetual cycle. Yes the exploitation gets a little harder each time around, but you don't get sound memory safety that way.

[ Parent | on HN ]
Re:Grsecurity Developer Spender's Feelings on the State of L... by nickpsecurity on Sunday November 08, 2015 @10:13AM (#10528671)
I agree: my main recommendation for new projects. However, avoiding C or porting Linux/BSD to a safe language fell on deaf ears for decades. So, for them, I recommend techniques that work with C and UNIX architecture. Maybe more progress that way.
[ Parent | on HN ]