WASM Security Sandboxing
Discussions debate WebAssembly's sandboxing capabilities, security model compared to JavaScript and native code, and potential for exploits or safe untrusted code execution.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Currently WASM has less security protections than native sandboxes, not more. Read security section of the standard.
Wasm is not sandboxed. Wasm is simply another standard way of writing instructions that can be platform independent. Wasm has no standard library software for sandboxing. Sandboxing is entirely dependent upon software implimenting execution of wasm instructions. Very few do this, there are fewer from reputable sources that do it without a JavaScript engine, and none that put sandboxing first.
Wasm is sandboxed. It's designed to be entirely safe to run.
Why would WASM be any less secure than JavaScript?
WASM only provides sandboxing. That is not the same as security nor it means runtime safety nor protection from undefined behavior.
Security. WASM is sandboxed by design.
Wasm can be sandboxed. Its a safe as visiting a website with javascript.
What are the security implications of wasm?
That's super cool! Interesting that WASM provides a way to sandbox untrusted code. Did you consider sandboxing JS with iframes as an alternative?
WASM offers much less security mechanisms than OS services + containers.