--- Comment #50 from Petr Pisar <ppisar@???> ---
I'm thinking the decision to implement the sealocator was a mistake. At the end
it only workaround imperfect security checks in the kernel (SELinux or
FreeBSD). The checks exist to prevent from executing at run-time hand-written
machine code. And this is what JIT is.
You are receiving this mail because:
You are on the CC list for the bug.
This message was posted to the following mailing lists: