3 ms·
> capabilities-based security model offered by WebAssembly What? Since when does WebAssembly natively ship with a "capabilities-based security model"? > prote
by capableweb 3y ago
> capabilities-based security model offered by WebAssembly
What? Since when does WebAssembly natively ship with a "capabilities-based security model"?
> protecting against a wide range of vulnerabilities, including those that may not be public yet but can be preemptively mitigated through these mechanisms
Not yet public vulnerabilities?
Who was this article/summary written by? Reeks of GPT or at least someone who doesn't actually know the subject very well.
- ridruejo 3y agoCapabilities based means that by default Wasm cannot do anything with the outside world. You have to explicitly declare the specific access you are giving, for example if the runtime implements WASI filesystem access you need to specify which parts of the underlying filesystem will be accessible to the module Not yet public means exactly that. You may have a buffer overflow issue in your code that you are unaware of. There are technologies that help mitigate those when/if discovered. Wasm is one of them but not the only one (ie most modern compilers have specific settings to harden the binaries against some issues)