3 ms·
Apparently nobody wants to take the 'secure default' performance hit of setting CONFIG_INIT_STACK_ALL_ZERO , as it will look slower compared to other distros.
by worthless-trash 5y ago
Apparently nobody wants to take the 'secure default' performance hit of setting CONFIG_INIT_STACK_ALL_ZERO , as it will look slower compared to other distros.
- mustache_kimono 5y agoYeesh.
- pjmlp 5y agoAndroid and Windows do take that hit. https://android-developers.googleblog.com/2020/06/system-hardening-in-android-11.html?m=1 https://android-developers.googleblog.com/2020/06/system-har... https://msrc-blog.microsoft.com/2020/05/13/solving-uninitialized-stack-memory-on-windows/ https://msrc-blog.microsoft.com/2020/05/13/solving-uninitial...
- josefx 5y agoAs far as I can find that flag seems to be clang specific? Which distros even use clang? Also since the Kernel is not pure C not all safety options are safe, at one point a few distros enabled stack overflow protection, only to end up with a kernel that randomly corrupted application stacks.