3 ms·
> Luckily pax anticipated that attack when releasing the KERNEXEC patch and fixed it a while ago. Naturally.
by dmix 7y ago
> Luckily pax anticipated that attack when releasing the KERNEXEC patch and fixed it a while ago.
Naturally.
- justinjlynn 7y agoSo, I'm wondering why it's not upstream in mainline.
- yjftsjthsd-h 7y agoProbably the usual reasons; security-minded patchsets make the kernel more attack resistant, but do so by changing things in ways that trade off against performance or compatibility, and Linux is obsessive about compatibility and cares about performance. I'm not going to say that one approach is objectively better or worse; it's just tradeoffs, and upstream/vanilla Linux prefers a different set of tradeoffs than PAX/GRsecurity/etc.
- staticassertion 7y agoPolitics.
- justinjlynn 7y agoThat applies to everything - it's not a reason, it's an excuse. More specifically, I meant - what was the technical rationale for its exclusion?
- staticassertion 7y agoNone. It is all politics.
- staticassertion 7y agoMore context: https://forums.grsecurity.net/viewtopic.php?t=4463 https://forums.grsecurity.net/viewtopic.php?t=4463 They had a mitigation for this out in no time, as I recall.