3 ms·

First off, the normal glibc/GCC stack canary is per-process, not per-stack. (I started writing a more detailed reply based on the commit description, but there

First off, the normal glibc/GCC stack canary is per-process, not per-stack. (I started writing a more detailed reply based on the commit description, but there was too much speculation without seeing their source code).

brynet 8y ago
OpenBSD's is per shared library, i.e: libc has a different stack cookie than your application and/or other libraries. RETGUARD however, is per function.