Page 1 of 1

Any chance we will get HTML5 DRM support at some point?

Posted: 2018-03-06, 21:51
by PCMasterRace
It's the only way Netflix, YouTube Red, Amazon Prime Video, or really any premium video streaming will ever work. I would love to use PaleMoon as my primary browser, but without DRM and WebExtensions support (for LastPass and a few others) the prospects of that are sadly pretty slim. :cry:
Or is there a way to get Netflix/Amazon to play in Palemoon without using HTML5 or Silverlight?
What about this Baskilisk thing? I have not tried it yet, I will give it a look now.

Re: Any chance we will get HTML5 DRM support at some point?

Posted: 2018-03-06, 22:34
by New Tobin Paradigm
Not in Pale Moon.

Re: Any chance we will get HTML5 DRM support at some point?

Posted: 2018-03-06, 22:36
by Sajadi
You can use Basilisk for DRM and Webextensions - even if Webextensions support is more or less experimental only.

Re: Any chance we will get HTML5 DRM support at some point?

Posted: 2018-03-06, 22:38
by PCMasterRace
That's too bad. I guess I'll just have to keep switching back and forth between PM and FFDE. I did get an older version of LastPass to work but I'm not sure if i will be able to use the biometric access with it.

Re: Any chance we will get HTML5 DRM support at some point?

Posted: 2018-03-08, 06:09
by Moonchild
PCMasterRace wrote:That's too bad.
Definitely depends on your view on blackbox DRM inside an Open Source browser...

Re: Any chance we will get HTML5 DRM support at some point?

Posted: 2018-03-08, 08:12
by WilliamK
Moonchild wrote:blackbox DRM
Wikipedia defines "blackbox DRM" as a non open-source solution. So supporting a DRM solution in an open-source browser does pose a huge problem, not just from a licensing point of view, but from a security view because it would expose the essence of the DRM and make it openly available for exploit.

Re: Any chance we will get HTML5 DRM support at some point?

Posted: 2018-03-08, 11:03
by Moonchild
WilliamK wrote:Wikipedia defines "blackbox DRM" as a non open-source solution.
Which is exactly what EME is. It downloads and uses closed-source content decryption modules.
WilliamK wrote:So supporting a DRM solution in an open-source browser does pose a huge problem, not just from a licensing point of view, but from a security view because it would expose the essence of the DRM and make it openly available for exploit.
Actually, it's the other way around. The essence (source) of the DRM is never revealed, and in fact the licensing of those modules prevents anyone from analyzing what it does, including doing so to report exploits. If you find a security vulnerability in a CDM, you had better not report it because you'd get sued for breach of license ("reverse-engineering" etc.). Of course that won't stop malicious elements from finding vulnerabilities and exploiting them.
But from a FOSS point of view, this is indeed bad; one advantage of FOSS is that there is always the clear transparency that the source is open for anyone to audit. That's not possible with DRM solutions through EME, which will download and run unchecked, unaudited executable code in the browser that could contain literally anything a supplier wants to put into it.