> In the 90s our sector started to look (again) at VMs as viable alternatives for software platforms.
Now we are back at it with WebAssembly, as if it was something new.
Now we are back at it with WebAssembly, as if it was something new.
it's also why WASM is so slow compared to native executables; security guarantees have a performance cost.
https://www.usenix.org/conference/usenixsecurity20/presentat...
https://www.usenix.org/conference/usenixsecurity21/presentat...
my point stands though. WASM is not ActiveX where the whole applet has admin permission on the computer.
More devs should get security trainings.
On this specific case, it is quite a big deal to add write and execute controls to the WASM memory, so it requires further justification than "I can do stack underflow attacks on my C code". Even though "I can do stack underflow attacks on my C code" is relevant information.
In fact, everybody is trying very hard to use all the experience we've got with the 90's VM, and getting annoyed here and there when it's different enough that they can't.