News for hackers. Stuff that matters.
Re:Update on HTML5 Video for Netflix by criddell on Wednesday March 22, 2017 @04:34PM (#13934635)
> First, the DRM is still not standard. Only the interface to it is.

Is a programming language a good analogy? The C++ spec says what a switch-statement should do, but nothing about how it must be implemented, right?

> New browsers face a new barrier to entry

It's not really a new barrier to entry though, is it? If I wrote a browser last year, were my chances of getting Netflix to support it better then than they are now?

What about if I wrote a new DRM scheme? With a standard interface, are the barriers to entry for me now lower?

Re:Update on HTML5 Video for Netflix by izacus on Wednesday March 22, 2017 @05:00PM (#13934907)
> Is a programming language a good analogy? The C++ spec says what a switch-statement should do, but nothing about how it must be implemented, right?

No it isn't. Example: Netflix will ask for Widevine DRM provider (and exactly that provider!). It's a proprietary closed licensed platform and your system needs to have their binary blob licensed and compiled for it. If you don't have it and didn't pay for it, you won't be able to decrypt the DRM. Of course to get your DRM blob to run, you'll also have to prove and promise to the DRM provider that you have locked out the user from their own device so they won't be able to accidentally record the video they watch.

It's impossible to make your own open implementation or compete with existing players because they built the fact that you need to negotiate with them for licensing into the standard.

Re:Update on HTML5 Video for Netflix by criddell on Thursday March 23, 2017 @08:20AM (#13939110)
> It's impossible to make your own open implementation

I don't think that's true. It's still just a plugin so as long as implement something like the Gecko Media Plugin / CDM, you should be good, or at least no worse off than before where you had to support the Flash or Silverlight plugin.

Re:Update on HTML5 Video for Netflix by merb on Wednesday March 22, 2017 @07:49PM (#13936218)
well at least as it looks Widevine has no license fees for Device Manufacturers i.e. browsers. You only need to contact them. Not sure how this company makes any money tough. (maybe through training courses)
Re:Update on HTML5 Video for Netflix by criddell on Wednesday March 22, 2017 @05:06PM (#13934961)
I'm still not getting how this is a step backwards. Last year there was no Netflix on Linux. This year there is.

Is there a better way to make strong DRM?

Re:Update on HTML5 Video for Netflix by azakai on Wednesday March 22, 2017 @06:43PM (#13935724)
It's true that in the short term this can seem like a step forward - we went from bad to slightly less bad. But it's also harmful and dangerous in the long term for all the reasons being discussed.
Re:Update on HTML5 Video for Netflix by BuuQu9hu on Wednesday March 22, 2017 @06:05PM (#13935430)
The 'Open Web' means "My browser can access ANY AND ALL CONTENT on the Web given that it supports the necessary standards."

This DRM implementation would add this suffix: "and any number of third parties have chosen to allow my browser to use their proprietary decryption modules." This is the opposite of the Open Web and therefore a threat to user freedom and the integrity of the Web as a whole.

Re:Update on HTML5 Video for Netflix by criddell on Thursday March 23, 2017 @10:42AM (#13940116)
The internet is used for a heck of a lot more than content destined for a browser.
Re:Update on HTML5 Video for Netflix by asdfgadsfgasfdg on Wednesday March 22, 2017 @05:15PM (#13935042)
EME is a much bigger barrier than the old system of plugins. With plugins you implemented the right API for the silverlight plugin and netflix would work. In the future you need to not just implement the API but persuade someone to build the plugin for your browser and then persuade each individual DRM using site to work with your browser.
Re:Update on HTML5 Video for Netflix by caf on Wednesday March 22, 2017 @09:02PM (#13936613)
The CDM is just a plugin - on Firefox it's a Gecko Media Plugin, and it seems easier to implement the GMP API than the NPAPI for Silverlight, since it's a lot more restricted.
Re:Update on HTML5 Video for Netflix by asdfgadsfgasfdg on Thursday March 23, 2017 @03:32PM (#13943353)
Please re-read my post.

These steps are not technical but they are very significant.

Consider how you would provide this plugin to your users as the author of a new browser? You have to ask the plugin authors for permission to use it.

Then consider that you have to persuade Netflix to allow the users of your browser to use their site (without changing user agents).

Neither of these steps were required with NPAPI

Re:Update on HTML5 Video for Netflix by caf on Thursday March 23, 2017 @07:16PM (#13945224)
Your browser can just download the plugin from Google the same way Firefox does. No permission required since you're not distributing it yourself. This is no different than the case of the Silverlight plugin.

There is no reason why Netflix would need to do user-agent sniffing - the EME API is built around request access to specific "Key Systems" (eg. Widevine) by well-known-name. If they do user-agent sniffing that's an entirely separate issue, and is just as much as problem in the Silverlight case.

Re:Update on HTML5 Video for Netflix by criddell on Thursday March 23, 2017 @09:40PM (#13945876)
> You have to ask the plugin authors for permission to use it.

I don't believe that's true. The plugin is freely available. You just have to write the host.

I don't think Netflix or the rights owners would care since the stream is protected equally in any browser.

Re:Update on HTML5 Video for Netflix by amluto on Wednesday March 22, 2017 @04:41PM (#13934716)
> Is a programming language a good analogy? The C++ spec says what a switch-statement should do, but nothing about how it must be implemented, right?

That's not what's going on, though. It's an API that a DRM provider can implement. A website that gets a DRM provider it doesn't recognize will refuse to work with it.