2 ms·
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 deploy
by fulafel 11y ago
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.
- nickpsecurity 11y agoI 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.