3 ms·
Successfully shipping the runtime in multiple web browsers works pretty well as social proof. People figure that if the sandboxing and portability is good enoug
by skybrian 5y ago
Successfully shipping the runtime in multiple web browsers works pretty well as social proof. People figure that if the sandboxing and portability is good enough for web browser vendors to trust it, it's probably good enough for them.
Java rode that train in the early days of the web with applets. But the user experience wasn't good and there were security holes, and Java support was gradually removed.
A lot of other languages tried this, but didn't get wide adoption.
- pjmlp 5y agoSecure? "Everything Old is New Again: Binary Security of WebAssembly" https://www.usenix.org/conference/usenixsecurity20/presentation/lehmann https://www.usenix.org/conference/usenixsecurity20/presentat... Other research papers are bound to appear as the security community finally starts looking into WebAssembly security claims. Marketing is everything.
- Matheus28 5y agoI skimmed through the pdf in less than 10 minutes, but from what it seems, it is pointing out how vulnerable binaries compiled to WebAssembly are still vulnerable to exploitation. Well, duh. What WebAssembly protects is the host machine, not the binary running inside the VM. None of these are attacks on the VM itself.
- pjmlp 5y agoBasically just nothing more than an OS process. It is not duh when WebAssembly advocates use the security sales pitch.
- Matheus28 5y agoThe entire point is running completely untrusted code safely contained from the host. Not protect the code from itself (which was never the intention). It might bare some resemblance to OS processes in its sandbox capabilities, but it offers a lot more: - OS independent - CPU independent - Easy target for compilers - Easily embeddable - Code cannot modify itself in memory (which makes the point below easier) - Easy to prove safe from accessing the host (very limited instruction set, can only access a certain address range of memory). It is hard to make a mistake implementing a VM. It's not too complex, and you can make sure every memory load/write instruction emitted is written to target "(BASE_ADDRESS<<32) | x", with x being the pointer as seen from inside the wasm, and BASE_ADDRESS being the upper 32 bits of the 4 GiB aligned range you have of virtual memory for the module The fact that it is widely implemented by browsers helps prove all these points. I'm sure the next big fun project for some people is gonna be writing a microkernel that runs wasm binaries in ring 0. It's that safe (of course, spectre might add a bit of overhead to context switching still).
- pjmlp 5y agoAll valuable points when one ignores the history of bytecode distribution formats since the early 1960's, capabilities and containers security measures on OS processes. No need to modify the code when data can be corrupted and thus be misused to influence the decisions taken by the code. Yes, it will be probably a fun project replicating Burroughs architecture in 2021. By the way, had Chrome the same market share in 2010 that it enjoys today, everyone would be talking how great PNaCL is.
- unrealhoang 5y agoFlash and Java had the market, but failed, so I wouldn’t be too excited about PNaCL. Isn’t the open-source, foundation-based standard the selling point of wasm?
- pjmlp 5y agoThey did not fail, politics killed them, the same politics that pushed for WebAssembly, but thanks to the WebAssembly pandora box, they were reborn just like Phoenix out of the ashes, https://leaningtech.com/cheerpj https://leaningtech.com/cheerpj https://leaningtech.com/cheerpx-for-flash https://leaningtech.com/cheerpx-for-flash Enjoy
- sitkack 5y agoI don't understand why you are so bitter about this. The fact that Wasm has a binary representation is orthogonal to the design. It has CFI and capabilities. CFI allows it to be compiled down to native code safely and run inside the same address space of the containing process. Capabilities control what gets in or out. You would be well served to ignore the whole bytecode aspect and just accept the Wast.
- infogulch 5y agoYes, WA has a defined security scope: it's right between the host and the WA program, and if you choose to sidestep it by eval-ing the output of a potentially malicious WA program, or simply handing it secrets, obviously you can get poor outcomes. No, WA has not solved the halting problem and fixed all bugs in sandboxed programs. Yes, it's important for people developing WA-based systems to acknowledge the above limitations. You've been brandying about this paper for the last year as if it means something that it doesn't [1-12]. Every time someone actually reads it they come to the same conclusion that this paper says nothing about the WA-host memory barrier -- and "everyone" includes the authors themselves [13]. And every time you respond by moving the goal posts with "but but WA isn't magic security pixie dust that solves all security problems". If I sound annoyed it's because I've been pushing back on your FUD with nary a direct response that acknowledges these limitations to your narrative and I am annoyed. Also, it's been a year now, where are all these papers that break WA that you keep promising? Are you privy to WA-host memory barrier breaking results that have yet to be published (and aren't just repackaged CPU vulnerabilities)? I'm open to evaluating the claim of such a break being found in the future, but there's no evidence for it yet. [1-12]: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=pjmlp%20Everything%20Old%20Is%20New%20Again%3A%20Binary%20Security%20of%20WebAssembly&sort=byPopularity&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... [13]: https://news.ycombinator.com/item?id=24223979 https://news.ycombinator.com/item?id=24223979
- pjmlp 5y agoI will keep pushing FUD as you call it, because the so called "security" improvements of WebAssembly aren't there. Just marketing, it doesn't matter that the host isn't directly exploited, when it can be affected by the behaviour of internal corrupted datastructurs inside the WASM module, just like an exploited OS process afects the surroundoing environment with its actions. A security sales pitch used to stagnate the state of RIA during the last 10 years. As for the papers not being there, I guess it is more fun to try to exploit other stuff than WebAssembly. Rest assured that you will be notified when they get announced.
- infogulch 5y ago