3 ms·
You shouldn't be running ASAN in production as a hardening tool. The authors advise against it. It introduces vulnerabilities, it's a lot of complex code that
by anon1385 10y ago
You shouldn't be running ASAN in production as a hardening tool. The authors advise against it.
It introduces vulnerabilities, it's a lot of complex code that wasn't written with hardening in mind, it defeats ASLR, and there are many memory errors it can't detect (which an attacker can use to bypass the checks if they suspect you are using ASAN).
If you want to "harden" your code against an attacker who doesn't know what they are doing then it might help. If you want to stop attacks by somebody skilled then enabling it is making you less secure.
- AstralStorm 10y agoIn fact, ASan is meant to be a debug/testing tool, not to be used in production. However, the only way to test something exhaustively is often in production... Heck, there is no good debug malloc style library mentioned either plus flags to disable malloc optimizations present in the GCC.