Earlier quoted context omitted.
Ah ok. So everything with a JIT will need this. I think I might even have read that somewhere long ago. This is a weird thing by the way. It seems to me like you should be able to debug or do VM syscalls against yourself because there is no escalation of privilege. Debugging another process makes much more sense to block. But maybe my opinion is invalid because I also happen to think disallowing jit with kernel permi…
> So everything with a JIT will need this. Actual JITs (ones blessed by Apple, not hacks like these) possess the dynamic-codesigning entitlement, and can just make RWX pages. > But maybe my opinion is invalid because I also happen to think disallowing jit with kernel permissions is very silly. Your opinion isn't invalid, but it goes against Apple's security model of iOS (namely: apps should not be able to modify them…
And my position is this is a silly approach, or, maybe is ok but should be opt-in, or perhaps opt-out with third parties being automatically trusted to decide they want to use JIT without hoops.
W^X is good default policy but Apple's policy is unreasonable and paranoid.