News for hackers. Stuff that matters.
Re:WebAssembly Browser Preview by icebraining on Monday October 31, 2016 @07:31PM (#12841924)
A middle ground is to allow memory to be either writable or executable at any given time, but not both (W^X). At least Firefox's JIT already implements this.
Re:WebAssembly Browser Preview by geofft on Monday October 31, 2016 @10:40PM (#12842947)
Yeah, iOS's JIT does the same thing, I believe (it JITs a page and then turns it execute-only). But it's not completely foolproof since a sufficiently lucky buffer overflow can, in theory, overwrite the JIT page while it is being JITed, and then wait for it to be executed.
Re:WebAssembly Browser Preview by CalChris on Monday October 31, 2016 @07:41PM (#12841985)
W^X, which is a really good+necessary idea, allows ROP. Still I think it's a necessary part of Defense in Depth for JITs which then necessarily leads to some bloat.