On 26.02.2017 16:03, Joerg Sonnenberger wrote: > On Sun, Feb 26, 2017 at 02:52:39PM +0100, Kamil Rytarowski wrote: >> It looks difficult to understand on the first sight, the need to >> "reinvent" malloc(3) with this approach. > > The point here is to have strict segration between code and non-code. It > doesn't work perfectly due to the additional book keeping pointers, but > pretty well. > >> Can we have something like MAP_NOMPROTECT? Something like it would be >> used to mmap(2) RWX region: >> >> void *mapping = mmap(NULL, rounded_size, PROT_READ | PROT_WRITE | >> PROT_EXEC, MAP_ANON | MAP_PRIVATE | MAP_NOMPROTECT, -1, 0); >> >> Are doubled mappings more secure than this? > > Yes, they are. It means you have to at least guess the second location. > > Joerg > While I'm not judging about the technical parts of the diffs, the general idea looks reasonable.
Attachment:
signature.asc
Description: OpenPGP digital signature