Open andlabs opened 9 years ago
Thanks; I'll keep this in mind too.
also use the clang static analyzer
-fsanitize=memory
Hello. While is fine add hardening flags, to prevent overflow to be exploited, if you talk about asan, just consider this: http://www.openwall.com/lists/oss-security/2016/02/17/9
Yes, I'm aware I'm using "hardening" as a generic term here. With the cmake scripts I have set up I can make it so that asan and what not are only included in the debugging builds if I do switch them on (and I really should); thanks for the note!
If using clang, we can use -fsanitize=undefined -fsanitize-trap-on-error
in production. That is not only safe, but also a significant security improvement.
Interesting. Do you have any more information (such as links) about those options?
see https://github.com/telegramdesktop/tdesktop/issues/1112
TODO other sanitizers?