News for hackers. Stuff that matters.

A comment on Toward _FORTIFY_SOURCE Parity Between Clang and GCC.

Re:Toward _FORTIFY_SOURCE Parity Between Clang and GCC by kccqzy on Wednesday February 12, 2020 @11:15PM (#22315297)
How does this relate to the address sanitizer? I believe ASan can catch all of the issues caught by _FORTIFY_SOURCE. Does the latter have fewer checks and better runtime performance? I'm guessing it is considered by most to be fine using _FORTIFY_SOURCE in production binaries but too much overhead for ASan?
[ Parent | on HN ]
Re:Toward _FORTIFY_SOURCE Parity Between Clang and GCC by zzz11 on Wednesday February 12, 2020 @11:58PM (#22315426)
_FORTIFY_SOURCE is a rather weak but fast mitigation for a narrow class of security issues. AddressSanitizer is a bug finding tool (2x CPU overhead!), for a different and much wider class of issues.

Edit: there is some overlap, of course.

[ Parent | on HN ]