5 ms·
It's pretty ironic how they titled their announcement post "How to build a plugin system on the web and also sleep well at night"
by tiborsaas 7y ago
It's pretty ironic how they titled their announcement post "How to build a plugin system on the web and also sleep well at night"
- naringas 7y agoit is not that ironic, they did such a throrough job that they managed to swap out their problematic solution into their plan b easily enough.
- rstupek 7y agoI think the point was they swapped out one problematic solution for another
- AriaMinaei 7y agoThey explained the trade-offs in the original blog post. They had considered this class of security holes and had a contingency plan in case one would be detected. They simply executed that plan. I'd say they handled it very well.
- AgentME 7y agoThe Realms polyfill solution was inherently hacky: it tries to shim a sandbox into an environment that didn't have one, and it makes it too easy to accidentally leak capabilities into the sandbox. WebAssembly was built from the start as completely sandboxed (if you want the sandbox to communicate with the world, you have to write each bridge yourself), and it's not as easy to directly share references to host objects into the sandbox, so it's unlikely to happen by accident. It's a blacklist (Realms polyfill) vs whitelist (WebAssembly) kind of situation. Whitelist approaches are almost always easier to secure and verify.
- rubbingalcohol 7y agoYeah it was a bit too smug. Having a bit of humility is never a bad thing. It's a good skill to learn, and experiences like this can help.
- AriaMinaei 7y agoDownvoted because clearly you either haven't thoroughly read the original blog post or do not remember it very well. In the post, they clearly mentioned that such security holes might be found, and they explained their contingency plan, which they now executed.