https://bugs.exim.org/show_bug.cgi?id=1749
--- Comment #26 from Zoltan Herczeg <hzmester@???> ---
Thank you for working on this. However I will probably just drop the current
protected allocator implementation since mprotect does not seems the right way
to support "security enhanced" systems.
I don't really understand the logic of security guys (RW -> R-X is unsafe, but
mapping the same area twice for writing and executing is safe...), but I really
want a single implementation. I will probably copy the regular executable
allocator and extend it with temporary file support and dual mapping. It might
create many temporary files during an execution, but that will be the trade-of.
--
You are receiving this mail because:
You are on the CC list for the bug.
