Re:Chromium unconditionally downloads binary blob
by mortehu on Tuesday June 16, 2015 @09:47AM
(#9725683)
While there's "almost no third party adoption", there are two pretty significant uses: The Flash player and the PDF viewer. Browsers that rely on NPAPI for these get all of Adobe's security bugs on top of their own. You may say that Flash and PDF doesn't exist in your view of the web, but it definitely does for many people.
[ Parent
| on HN ]
Re:Chromium unconditionally downloads binary blob
by jug on Tuesday June 16, 2015 @10:46AM
(#9726163)
It does, and I enjoy mp4 videos and I'm not bothered much by DRM on Netflix either, but should a component like NaCl implying a binary blob be part of an open source software.. by default? Feels weird to have it included with Chromium by default. Weren't Chrome and Chromium originally separated in order to make one compatible with open source distributions, so that this sort of thing would be avoided? A conflict with Debian sounds like a pretty big one.
Re:Chromium unconditionally downloads binary blob
by strcat on Tuesday June 16, 2015 @10:56AM
(#9726236)
NaCl doesn't imply proprietary any more than a JavaScript engine does. The downloaded code is bytecode at an abstraction level a bit below C but quite a bit above assembly. It's not substantially different from a freedom perspective than code compiled to asm.js or just minified JavaScript. Both are usually proprietary and require reverse engineering work to decipher.
Re:Chromium unconditionally downloads binary blob
by vezzy-fnord on Tuesday June 16, 2015 @11:41AM
(#9726570)
As it's not the "preferred form of the work", I think it is proprietary - same way any object/intermediate or obfuscated code would be.
Re:Chromium unconditionally downloads binary blob
by rockdoe on Wednesday June 17, 2015 @04:45AM
(#9730629)
>NaCl doesn't imply proprietary any more than a JavaScript engine does
Re:Chromium unconditionally downloads binary blob
by diamondlovesyou on Wednesday June 17, 2015 @11:23AM
(#9732401)
> The downloaded code is bytecode at an abstraction level a bit below C but quite a bit above assembly.
You just described PNaCl, not NaCl. NaCl is architecture specific and already sandboxed (ie the SFI part of NaCl), whereas PNaCl is not.
Re:Chromium unconditionally downloads binary blob
by cpeterso on Tuesday June 16, 2015 @01:20PM
(#9727355)
Chrome's Flash Player uses PPAPI (Pepper), not NaCl. Pepper Flash is still running Adobe's native code, not NaCl code.
Re:Chromium unconditionally downloads binary blob
by mortehu on Wednesday June 17, 2015 @02:43PM
(#9734336)
Aha, I see it's a shared object. It's sandboxed, though, so quite similar to NaCl.
Both NaCl and the plugins are running native code. NaCl is not PNaCl.
Re:Chromium unconditionally downloads binary blob
by rockdoe on Wednesday June 17, 2015 @04:43AM
(#9730625)
So it's using the NaCl sandbox and interface without the bytecode parts?