> Now we have exploits for libraries and runtimes that often allow access to arbitrary application data. If this functionality is in a separate process without

> Now we have exploits for libraries and runtimes that often allow access to arbitrary application data. If this functionality is in a separate process without such privileges, application data will be safe. Even now if OpenSSL would not have made their own memory manager focusing on performance this bug would not have such major consequences. Frankly they should just accept performance penalties and make a memory manager that focuses on security. As an example all allocations should be from mmap so that any overflow will automatically segfault (with checks that one doesn't get continuous pages from the OS unmapping selectively to create disjoint areas). Every free should be a munmap etc. I do also agree that moving this to a separate process would be useful.