4 ms·
The problem with Flash and Java was that they were not integrated with the browser's sandbox. WASM is integrated with the sandbox. How would allowing DOM acces
by NoahKAndrews 4y ago
The problem with Flash and Java was that they were not integrated with the browser's sandbox. WASM is integrated with the sandbox.
How would allowing DOM access be insecure? The DOM is designed to be completely controlled by the webpage. I don't see how adding an additional way for the webpage to do so adds any insecurity.
- satvikpendem 4y agoIndeed, as if sites today already can't snoop with JS instead of WASM.
- tabtab 4y agoWhy offer TWO snoop vectors? And crypto miners would target WASM over JS, giving WASM a bad name.
- pjmlp 4y agoYet, one can still compile Heartbleed into a WASM module. It adds more ways to sneak unwanted code into the page or do cross execution that shouldn't happen in first place, while staying inside the sandbox.