NSS Updated On Ubuntu 12.04/14.04 To Allow Netflix Support

[droidhacker]

Works fine in Fedora 20 with Chrome Beta.

You don't need the beta any more. Chrome release (37) does the job.

[abral]

It's nice how many people always talk against DRM and then complain that an opensource browser built by a community that hates DRM doesn't support DRM since the beginning.

[peppercats]

doesn't work with chromium, open bug on ubuntu's bug tracker about it.

[Daktyl198]

firefox does not support the needed DRM (HTML5 DRM thingy).
Untill firefox wakes up from its sleep netflix cant do nothing about it.
BTW i doubt firefox will support it anytime soon. it barely supports youtube video in html5, its missing so many codecs and stuff (even flash sucks on it... STILL FUCKING WAITING FOR SHUMWAY OR USE PEEPER!!!!) firefox is just... too slow...

PS: i used to love firefox thats why it makes me so angry to see it in this state.

It's supported Youtube HTML5 very well for ages (though, that may be because I'm on Nightly), and I don't know what you mean when you say it's "Missing so many codecs". On both my Windows 8.1 and Manjaro Linux installs, it supports almost every codec that is used on the web (h.264, mp4, ogg, wemb, etc).\

Also, Firefox isn't "sleeping" in relation to the DRM module "thingy"; they have to wait for Adobe to finish creating the module itself. After THAT, Netflix has to alter/provide new DRM binaries that will work with that DRM module.

[FireBurn]

For those folk using Gentoo I've put an ebuild here: https://bugs.gentoo.org/show_bug.cgi?id=523476 with the new widevine DRM support

[Luke]

UA whitelisting is a good reason not to rely on a site or subscribe to it

So... They use the browser's UA to "detect" what version of NSS is used, and once their reference distro updates to the correct version of NSS, they'll whitelist the useragent string ? This is completely broken, there's no relationship between the UA string and the version of NSS.

Pushing for for majors distros to ship the required version of NSS is a good thing, but using UA whitelisting like this is a big WTF.

If you pay money to subscribe to a site using UA filtering, you don't know what they will block next. Don't risk your money, cancel your subscription today. It's one thing to hack UAs to defeat blocking by a site you can access for free, quite another to bet real meatspace money on winning a hacker war against their "security" team. This is literally as good a reason as principled opposition to DRM to dump Netflix.

Full disclosure: You cannot use netflix, Hulu, or any other DRMed content on any machine I own, that is by intentional design on my end not to support DRM. You can use Bittorrent just fine, though the only thing I've used if for is big distro disk files when the servers providing them are busy and asking everyone to torrent so as to take the load off the servers.

[liam]

Why the hell are they filtering user agent strings rather than capabilities? The browser either has the extensions or not. If not, it won't work anyway.

[nanonyme]

Okay, so will not work with out-of-the box Chromium but will eventually work with out-of-the box Firefox. Good to know

[kringel]

For Firefox (I prefer Firefox) you'll have to wait probably 1-2 versions until Mozilla fixes the remaining issues with Media Source Extensions (MSE, test it e.g. at the youtube.com/html5 page). And they also need a Plugin, called EME ("Encrypted Media Extensions"), which will be provided by Adobe. https://hacks.mozilla.org/2014/05/re...n-and-w3c-eme/

[kringel]

Do you need Chrome for this or is Chromium enough?

It should work with Chromium, like Chromium works with the libpepperflash-Plugin and also works with the pdf-plugin.

You will need Chromium v37 minimum. And the same version of Google Chrome. (Download the deb, make a directory, dpkg -x google-chrome.deb <directory> -- this will extract it)


In *this* directory find opt/google/chrome/libwidevinecdmadapter.so and opt/google/chrome/libwidevinecdm.so

copy these two in the Chromium folder (in /usr/..., not your home folder)

Start Chromium. In Chromium enter "aboutlugins" (or "chrome://plugins") There should be something like "Widevine Content Decryption Module". it should be activated.

Let's summarize. You need: 1.) Chromium at least v37. 2.) The two libwidevine*.so files from the extracted Google Chrome deb.-package 3.) At least libnss3* (v3.16.2) on your system installed (or in the google chrome, or chromium folder). But 3.) is solved automatically with Ubuntu's update. Debian jessie testing also have this recent version (v3.17)

And 4.) The "User Agent Switcher for Chrome" hack. I guess only for a few days.

I haven't tried it yet but I wish you good luck trying it with Chromium.