Mozilla to Bake-In DRM in Next Version of Firefox

Earlier262875283_ca33f09edd[1] today Mozilla acquiesced to a market reality which ebook retailers have known for years.

Ask anyone who has tried to launch an ebookstore and they'll tell you that the only way to get titles from major publishers is to integrate DRM into the ebookstore - often times at high cost. Many publishers simply won't distribute to an ebookstore that lacks DRM, with some even going so far as to question the security of new types of DRM (like the custom DRM used by Oyster).

Similarly, the only way for a browser maker to support commercially streamed video is to enable support for DRM. In the past that meant indirectly supporting DRM via Flash and Silverlight, but in the future streaming DRM is going to have to be built in to the web browsers.

And so today, in a long and meandering blog post, Mozilla announced that they would be integrating DRM into the next version of Firefox. They will be using closed-source code, but to add an extra layer of protection they will wrap that code in open source code.

Ostensibly this change is going to make it easy for end users, but it also puts web browser makers between a rock and a hard place. Either they integrate the new DRM, or they lose relevance.

I agree with them when they say they don't really have a choice:

We very much want to see a different system.  Unfortunately, Mozilla alone cannot change the industry on DRM at this point.  In the past Firefox has changed the industry, and we intend to do so again.  Today, however, we cannot cause the change we want regarding DRM.  The other major browser vendors — Google, Microsoft and Apple — have already implemented the new system.   In addition, the old system will be retired shortly.  As a result, the new implementation of DRM will soon become the only way browsers can provide access to DRM-controlled content.

There's no definite timeline for crippling Firefox with the new DRM, but they did say that it is coming. It will be first be tested in developer builds, before it is inflicted upon users. Mozilla plans to have the DRM disabled by default, requiring a user to enable it before watching a streaming video, but it will be present in future Windows, OSX, and Linux versions of the Firefox web browser.

There's no mention of Android, which is unfortunate. As we know from trying to get Amazon Instant Video working on the platform, Flash support on Android is spotty at best, and Silverlight is not supported at all. This is part of the reason why so many streaming video services have deployed their own app.

6 thoughts on “Mozilla to Bake-In DRM in Next Version of Firefox

      1. I use Fedora, where any closed-source binaries like that, are left out.
        This means, mp3 support, most of movie codecs, even video drivers that are closed source have to be installed from a different source.

        As far as I’m concerned, Firefox is done.
        They should have created an addon, just like those for Flash or Java …

      2. At some point, the un-encrypted content is going to be given to the open source section of the code, for display, etc.

        Or is Firefox no longer open source?

        1. It’s still open source.

          If you’re asking about hacking the DRM , that will probably happen, yes. The current streaming DRM (Flash and Silverlight) is thoroughly hacked. Netflix exclusive shows like House of Cards are available in the darkweb.

        2. As far as I’ve read, Firefox now embeds an Adobe blob to process the managed content. The unencrypted content need not necessarily reside anywhere in the computer’s accessible memory, if some sufficiently sophisticated DRM scheme were used. I’m not entirely sure what, for instance, HDCP 2.0 and future technologies will provide in that respect. Circumventing DRM might become increasingly difficult, if it is deeply embedded in the hardware you use. Such things might wait for you everywhere some day: http://en.wikipedia.org/wiki/Intel_HD_and_Iris_Graphics#Intel_Insider

          However, past solutions got circumvented sooner or later. Content providers concerned about compatibility issues or that certain users might boycott their services entirely might also decide not to use DRM technologies, which might have their own costs anyway.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>