3 ms·
If this sandbox enables Firefox to safely host DRM malware, it could very well be used like a generic "Docker for the client", right? People could write high-pe
by Udo 12y ago
If this sandbox enables Firefox to safely host DRM malware, it could very well be used like a generic "Docker for the client", right? People could write high-performance code blobs in native chunks for things like online games, and Firefox would just load them without endangering the user's system or data.
Maybe someone with in-depth knowledge of the sandbox could weigh in about its actual security, I'd be interested in hearing about it.
Because if it's not secure enough to allow arbitrary code from random websites to execute safely, it's sure as hell not secure enough to run that DRM crap. What happens instead is Firefox becomes a vector for Trojan horses and root kits installable on my computer on behalf of any interest group imaginable.
I switched from Chrome to Firefox specifically for things like these.
- maxerickson 12y agoI think native code sand boxing got to browsers before docker: https://developer.chrome.com/native-client https://developer.chrome.com/native-client
- Udo 12y agoThat's Chrome, does Firefox have anything like this? And if it does, why do we need an extra sandbox format for the DRM stuff again?
- maxerickson 12y agoThere was a big kertuffle a few years back where Mozilla made it clear they weren't going to support anything like native client (and they then put a bunch of resources into asm.js). I don't know if that has changed or not, I don't pay close attention. I only mentioned it because of the "Docker for the client" line, that it already exists is a pretty emphatic yes.
- Udo 12y ago> I only mentioned it because of the "Docker for the client" line, You're right. I corrected the original comment to make it clearer I'm talking about Firefox. The point was to call out the sandbox argument a bit, since I'm not so sure it's actually safe to run malware in it.
- deleted 12y ago[deleted]