3 ms·
> or a better arbitrary runtime like WASM > It's the component and security model itself. WASI and the WASM component model proposal [1] are moving to a capab
by the_duke 4y ago
> or a better arbitrary runtime like WASM
> It's the component and security model itself.
WASI and the WASM component model proposal [1] are moving to a capability based system (enabled by unforgeable references aka `reftype`) and to isolation between different parts of your code, which would make isolating and restricting dependencies really easy.
Combined with interface types (essentially a universal cross-language ABI) the ecosystem has the building blocks for building very secure systems.
Sadly progress has been very slow, with no end in sight, but I remain hopeful.
[1] https://github.com/WebAssembly/component-model https://github.com/WebAssembly/component-model
- cmrdporcupine 4y agoAgreed. I have been watching this as well a bit, esp as the startup I'm now working at is working in the "hosted WASM" area. But it still seems early days. And not clear if their goals correspond to mine (WASI doesn't fit their/our use case generally, but a lightweight component model for WASM does). Probably I should watch this more closely, or see if there's a reasonable way I could get involved. I still think there's a long rough road to "get there from here" in the context of the browser though, which has already defined its own (non-capability based) security and component model. Luckily what I work on right now doesn't involve the browser.