On Tue, Oct 03, 2017 at 06:54:52PM +0200, Maxime Villard wrote: > Just like disabling va0 or enabling PaX mprotect; if you feel like these are > no issues, then what's the fuss. You would be well served to read the "rdtsc > is still enabled by default" part of my email.
Disabling va0 is low impact. Enabling PaX mprotect by default is far from it. It doesn't help that again the set of people enforcing this policies and the set of people that work on actually fixing the fallout is wildly disjunct. > I'm not responding to this nonsensical thread anymore, everything got told > months ago. The option is here, people don't need to give a damn about it > unless they explicitly want to - which is still legitimate in some cases, > including for kaslr, whether it pleases you or not. There are plenty of > useless sysctls to complain about if you like. Funny. You've been ignoring the replies you got month ago, so of course there is nothing new to discuss. Frankly, I don't find that acceptable behavior. Joerg
