4 ms·
> untrusted binaries afaik, wasm is not 'binaries' in that it's not an arbitrary blob of machine code fed right into the cpu. it's still running in a sandbox
by abiox 9y ago
> untrusted binaries
afaik, wasm is not 'binaries' in that it's not an arbitrary blob of machine code fed right into the cpu. it's still running in a sandbox (a la javascript) including similar limitations wrt CORS etc.
- sitkack 9y agoAnd a sandbox so powerful that all the browser vendors just turned off SharedArrayBuffer. https://www.chromium.org/Home/chromium-security/ssca https://www.chromium.org/Home/chromium-security/ssca https://blog.mozilla.org/security/2018/01/03/mitigations-landing-new-class-timing-attack/ https://blog.mozilla.org/security/2018/01/03/mitigations-lan... WASM is portable binaries.
- abiox 9y agowell, i guess in the same way that javascript or anything else is, when there are sandbox escapes. bugs are a thing.
- austincheney 9y ago> it's still running in a sandbox (a la javascript) People frequently make this comparison upon hearing the term sandbox, but this is a weak comparison. Yes JavaScript executes in a sandbox, but the JavaScript (JIT) sandbox is purely for performance instead of isolation, which is like comparing a pencil sharpener to a bulldozer just because they are both portable machines. A better comparison of the JavaScript (JIT) sandbox is the JVM.