How Firefox Will Handle DRM In HTML
An anonymous reader writes "Last year the W3C approved the inclusion of DRM in future HTML revisions. It's called Encrypted Media Extensions, and it was not well received by the web community. Nevertheless, it had the support of several major browser makers, and now Mozilla CTO Andreas Gal has a post explaining how Firefox will be implementing EME. He says, 'This is a difficult and uncomfortable step for us given our vision of a completely open Web, but it also gives us the opportunity to actually shape the DRM space and be an advocate for our users and their rights in this debate. ... From the security perspective, for Mozilla it is essential that all code in the browser is open so that users and security researchers can see and audit the code. DRM systems explicitly rely on the source code not being available. In addition, DRM systems also often have unfavorable privacy properties. ... Firefox does not load this module directly. Instead, we wrap it into an open-source sandbox. In our implementation, the CDM will have no access to the user's hard drive or the network. Instead, the sandbox will provide the CDM only with communication mechanism with Firefox for receiving encrypted data and for displaying the results.'"
As with all DRM schemes, it's only a matter of time before this is broken. However, to save the decrypted content to the hard drive, one has to, well, have access to the hard drive. Does Firefox's architecture actually get in the way of users eventually pirating the content? Might have to switch browsers if that's the case.
THIS is a good reason to oust a Mozilla CEO.
Given the recent update, I suspect the answer will be the same for both.
(I feel like this joke is nerdy even by slashdot standards.)
Mozilla just ousted their chair over something that screws over far fewer people than this.
LK
"Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
Current number of websites using EME is 0.
Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
PaleMoon is a Firefox fork that appears to be doing very well. I dont know for sure, but I suspect they will correctly sort this into the unwanted features bucket and skip it.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Friends don't let friends enable ecmascript.
What we need to do is figure out how to apply DRM to the personal information emanating from our machines. You will then be able to lawfully defend against those who profit from that information. Of course you could work out an arrangement to get a slice of the gross coinage as well ;).
Current number of websites using MEME is over 9000.
Get free satoshi (Bitcoin) and Dogecoins
Oh look. Here's a whole _page_ of Ayn Rand quotes about compromise
or...
http://aynrandlexicon.com/lexi...
Many folks have a go at the idea that they can somehow tame evil or compromise with it without being tainted too much. I'm not sure this has ever really worked out.
There is a lot to like about the Richard Stallmans of the world. They are clear about the what and the why, and they stick to their guns.
My opinions are my own, and do not necessarily represent those of my employer.
Gopher over TOR.
"Flyin' in just a sweet place,
Never been known to fail..."
How long before someone codes a module to bypass the DRM handling?
From Cory Doctorow's article today...
Rather that deal with it in such a complex way, they should just do what linux did for years with MP3s. Popup box "This is an MP3, we can install the thing you need to listen to it, but it's not open source. Do you want it? Yes/No" Simple as that. Let users chose. I don't see how this is any different.
Then they can let their plugin community quietly subvert the entire mechanism, just like they have everything else, and the industry will abandon it.
But this is an open-source browser we're talking about. If we don't want DRM, we can make a build of it without the DRM piece.
Being open-source has nothing to do with this. The number of people who will use a fork is essentially zero when compared to Firefox's total userbase.
The problem is that Mozilla has thrown away the power that comes from being able to speak for hundreds of millions of users out of fear of losing some of those users. That's a path to irrelevancy, they've traded the vision that made them popular in the first place for the hope of maintaining marketshare. It is a total MBA move, as if Mozilla should be driven by profits instead of advocacy.
Brendan Eich may have had some opinions that people don't like, but at least he stuck to his morals. Now that he's gone, the new CTO, this Andreas Gal, seems more likely to compromise. DRM is evil, but Dr. Gal thinks he's clever, and is trying to wrap it in an open-source sandbox. Let the exploits come.
Oh well, now I do have an actual reason to boycott Firefox.
Have a nice time.
Obviously you are correct. A UI which exposes control interfaces to the user is bad. The future is to expose control interfaces ONLY to remote ad agencies, and keep the dirty users in their place.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Friends don't let friends enable ecmascript.
Mozilla did not "oust" him. He stepped down after the wider community spoke up. This is being forced by a bunch of DRM happy corps (MS, Apple, Google) and their media industry buddies (Netflix, MPAA, et. al.)
http://slashdot.org/comments.p...
Well, here you are standing on principles. :)
You wanted to watch Youtube vids, so you run Google Chrome, which has even more liberal implementation of this DRM.
You didn't boycott Youtube.
So, this is why Firefox is implementing it. They no longer have the leverage. Google Chrome is bundled with Flash, with Adobe Acrobat, with Oracle Java. It is pushed on every google website people interact with - Search, Plus, Docs, Youtube, Translate. There's the google app store, ChromeOS, Android...
I doubt Brendan would have held out against this either. Firefox' choice is to accede to its users, or become even more marginalised.
I'm glad they are using their limited remaining leverage to try and at least ensure user privacy and security and offer something that is cross-platform, with an open source auditable wrapper and actually works under Linux.
-- perl -e'print pack"H*","6e656d6f406d38792e6f7267"'
There are other options as well.
You have a LOT of Windows and Shareware, in that list. ;-)
I browse from a 1995 era SGI, and a QNX Neutrino RTOS VM. I'm contemplating Acorn RiscOS on a RaspberryPi.
"Flyin' in just a sweet place,
Never been known to fail..."
Youtube uses EME for 1080p streams, no EME and you only get 720p or lower
Youtube uses Media Source Extensions for 1080p streams. That's completely different; it's a way to source data to a <video> element from Javascript. They use it to implement their dynamic HTTP streaming, where rather than just sucking down a file you suck down individual file segments allowing dynamic quality adjustments based on your available bandwidth. There's no DRM involved.
Ah, that explains it; you're the Clifford Stoll of this place!
Someday, ask me about my connection to Markus Hess. We had a Fortran 77 class together, before his infamy...
"Flyin' in just a sweet place,
Never been known to fail..."
It's sad seeing this, but its also good to keep in mind - this standard was pushed by Microsoft, Google and others. As such its already "live" in Chrome (as of Release 25 if memory serves, current Chrome release is 29 I believe) as its in WebKit (so ad Safari and Opera as well). Microsoft will add it to IE if they haven't already - leaving Firefox and its slowly dwindling user base. Since 75% of the PC web and nearly all of the mobile web will be making use of this - it'd be a market share death sentence for Mozilla to take a stand and say we just won't implement these "standards" in Firefox - (JMHO, but most general users would notice that what they want using this cgap works with Chrome, IE etc. and not with Firefox and just stop using Firefox making the Firefox user base melt away faster). I don't like Mozilla doing this, but I can easily understand why they are.
The difference is that the CDM will be sandboxed in a low-privilege process with no direct access to the OS and kernel, which is not at all how Flash works.
We've tried sandboxing the plug-in process Flash runs in. It breaks all sorts of existing Flash-using stuff, unfortunately.
The benefit of having a sandbox from day 1 is that you don't have that problem.
It's amusing to read the reports on right-leaning news sites. According to them, he was forced out by the 'gay mafia.' They use that phrase quite a lot.
this is bigger than an open source project or even one browser
this is about the standards of the internet and openness...no DRM is just as important as Net Neutrality
the W3C are total sell-outs to corporate interests in DRM...complete and total...now it appears firefox has joined them
the WHATWG is the only reason we are stuck with 90s-era spaghetti code on websites now...they developed HTML5 and finalized CSS3...
HTML would be spyware if the W3C had its way...and HTML5 would not exist w/o the WHATWG
Thank you Dave Raggett
Are Adobe going to make a Linux version of the DRM module? Because their record with Linux versions of their PDF DRM tech is VERY POOR. We get research articles from the British Library which are DRM'd, and our Linux users can't read them. One solution is to complain to BL at which point they will often just email you a plain old unDRMd PDF. The mega-facepalm thing is that the British Library came out against DRM-content a few years ago, and have done a massive backtrack because the publishers didn't like it.
Whether DRM is a bad thing or an insanely bad thing (ok, or a good thing, whatever), I don't ever want to see "This Content Cannot Be Viewed On Your Nerdy Linux Operating System" popups ever. But if this is Adobe's shitcreek we're wading through, I think I will.