3 ms·
Randomizing system calls is probably not going to be all that helpful, as your exploit code will just read the table where you keep this information. Some OSes
by saagarjha 6y ago
Randomizing system calls is probably not going to be all that helpful, as your exploit code will just read the table where you keep this information. Some OSes (OpenBSD) will do randomization based on object files and sections, which you can do things with like place each function in a different section and relink. This would require an exploit to leak addresses, which is a better situation I guess; the downside is that this adds complexity and is fundamentally incompatible with certain operating systems (Darwin). As for JITs…I mean, they kind of need to exist, but I am unsure what to do there other than "your app doesn't seem like it needs a JIT" will mean, especially as more programs ship with language runtimes and browser engines.
- johncolanduoni 6y ago> Some OSes (OpenBSD) will do randomization based on object files and sections, which you can do things with like place each function in a different section and relink. This would require an exploit to leak addresses, which is a better situation I guess; the downside is that this adds complexity and is fundamentally incompatible with certain operating systems (Darwin). Doesn’t Darwin’s linking model effectively do this separation (though I don’t know about randomization) unconditionally, with the whole “atom” thing? IME the linker does tree shaking effectively without per-function sections, and I have trouble seeing how that would work otherwise.