Re:FreeBSD – a lesson in poor defaults
by jemsa on Tuesday December 26, 2017 @07:02PM
(#16011862)
Yet FreeBSD hasn't done a single thing to improve the current state of exploit mitigations.
It doesn't matter how many people are writing code, grsecurity is mainly Spender & pipacs aka PaXTeam yet 14 Linux developers couldn't spot the vulnerabilities they've created by copy pasting and editing code from grsecrutiy.
You can't really blame others for trying while FreeBSD hasn't tried a single thing yet.
[ Parent
| on HN ]
Re:FreeBSD – a lesson in poor defaults
by tachion on Wednesday December 27, 2017 @02:55AM
(#16013500)
No one, at least not me, is blaming him for trying. But he is to be blamed for sending a poorly written and badly designed patch, unwilling to work on it until it meets the quality of the FreeBSD project and then 'forking' FreeBSD, applying these widely criticised patches and making a social campaign of "they don't want to fix security" instead of "they don't want to introduce bad code" what would be much closer to the truth.