You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was hoping to see your thoughts on IMPLEMENT_RANDOMIZE_STACK when you documented ThreadOpenConnections, but I saw it was glossed over. It's always been something that bothered me for some reason.
Why not just use built-in ASLR? Pretty sure VS and mingw supported it.
How does it actually work? It doesn't seem like it should, but I'm a bit of a simpleton.
Have you ever seen anyone do anything similar? I've looked at a lot of old C/C++ code, and have never come across anything like it.
The text was updated successfully, but these errors were encountered:
My educated guess is that he either didn't know or he was aware of the limitations of ASLR back then and decided to "roll-his-own".
Even today when the entire base system in Windows 10 uses ASLR, image randomization on Windows is per-boot, not per-process. This means that attackers can guess the location of code pretty reliably. The stack itself is randomized per-process though.
I was hoping to see your thoughts on IMPLEMENT_RANDOMIZE_STACK when you documented ThreadOpenConnections, but I saw it was glossed over. It's always been something that bothered me for some reason.
The text was updated successfully, but these errors were encountered: