Re:Wasmtime 1.0
by jon-wood on Tuesday September 20, 2022 @02:16PM
(#32915722)
Personally I’d want to be very cautious about this. It’s probably more secure than just running this untrusted binary directly on a server full of user uploaded content but I don’t know what level of confidence is should have in wasmtime not having any container escapes possible.
[ Parent
| on HN ]
Re:Wasmtime 1.0
by schemescape on Tuesday September 20, 2022 @02:36PM
(#32915993)
Yes. Consider that Spectre allowed reading browser memory that wasn’t exposed to JavaScript from within the JS sandbox. Something similar probably would have been possible with WASM, if Spectre hadn’t already been found and mitigated.
I love capability based limits like this (and in Deno), but they’re not a panacea.