3 ms·

In a browser environment, sure because browsers need to sandbox webpages. But WASM runs on different environments too.

• flohofwoe 5y ago
  It's also important outside the browser, WASM could be the solution for running untrusted code without a walled-garden app distribution model, but only if the sandbox actually works.
  • pjmlp 5y ago
    As long as the internal memory doesn't get corrupted due to lack of bounds checking inside linear memory internal accesses. Corruption that can then be used to subvert the behaviour of functions being called.
    • flohofwoe 5y ago
      That's a language-level problem, e.g. "just use Rust" if you're concerned about "sandbox-internal" memory corruption (and that this internal corruption can't be used to alter the behaviour of called host platform functions is why APIs must be designed with security in mind - WASM running in browsers has the same problem, that's why WebGL does additional validation compared to native GL implementations).
      • pjmlp 5y ago
        Just use language X only works when not relying on 3rd party WASM libraries, also I bet emscripten sees much more use on the wild than Rust. WebGL additional validation is so good that the only way to work around exploits is to blacklist user's hardware, OS and GPU drivers. Thus rendering those nice 60 FPS scenes into a single digit FPS caused by software emulation. Security would be so much better if liability was already thing across the industry, and not only on high integrity systems.