3 ms·
> I doubt anyone else but them is going to be auditing the various touch points with QuickJS for any kind of sandboxing escaping. I don't think this is releva
by nicoburns 7y ago
> I doubt anyone else but them is going to be auditing the various touch points with QuickJS for any kind of sandboxing escaping.
I don't think this is relevant. QuickJS-in-wasm doesn't have access to the host environment in the first place. They're not relying on QuickJS for sandboxing, they're relying on WASM. And the WASM runtimes have plenty of eyeballs.
- gfodor 7y agoThere's still interop code though, isn't part of the challenge with this ensuring that there's no security holes in the communication layer between the VM and the outer application? Perhaps they have that concern regardless, but I think a standard set of patterns + shims will eventually converge for Realms.
- azakai 7y agoThere is interop code between the wasm and its JS runtime, but that's very easy to audit for exactly what the wasm is given and what it returns. Also that interop code will be a combination of standard runtime code - very heavily tested, unless they are using something very new - and code they write themselves for their specific application - which they control. So I think this is the safer route for security. It does have a speed penalty atm, but sounds like it's worth it for Figma.