The Node API docs for WASI say:WASI gives sandboxed WebAssembly applications access to the underlying operating system via a collection of POSIX-like functionsBut I can't find information anywhere on exactly what the "sandbox" isMy understanding is that the WASM script has no access to memory outside of it's sandbox. Is that a good assumption?I would guess that the constructor arguments (args and envs) are copies of the corresponding data structures (process.argv and process.env) in the Node script environment?Does the WASM script have any access to system resources - IPC sockets, network, file system, or any other system call?
Submitted February 26, 2020 at 04:16PM by calligraphic-io
No comments:
Post a Comment