Gary Mort
2014-07-16 02:35:55 UTC
NPAPI is deprecated and should not be used for plug-ins - so I'm curious on what the alternative is for things like encrypted media extensions.
It seems that rather then providing a method for anyone to create plugins for drm enabled media, Firefox is instead providing a single closed sourced implementation based on "DRM requires closed systems to operate as currently required and is designed to remove user control," https://blog.mozilla.org/blog/2014/05/14/drm-and-the-challenge-of-serving-users/
Obviously the above statement is not true, but it seems that instead of providing choice Mozilla has decided to force one solution onto everyone.
DRM protection could be as simple as passing all blocks of media data through a simple circular shift. The only "secret" part of the plugin would be the block size and the rotation size. Sure, such DRM is trivial to break, but then all DRM is eventually trivial to break - so if someone wants mild drm protection they could easily provide a plugin to do so.
However, there does not appear to be an api to provide small compiled bits of code/plugins. Am I missing something or is this really the case?
The ability to have competing DRM mechanisms has, in the past, provided protection from companies that have decided to abuse the need for DRM software to include all sorts of abuses, spyware, trojans, etc.
It seems that rather then providing a method for anyone to create plugins for drm enabled media, Firefox is instead providing a single closed sourced implementation based on "DRM requires closed systems to operate as currently required and is designed to remove user control," https://blog.mozilla.org/blog/2014/05/14/drm-and-the-challenge-of-serving-users/
Obviously the above statement is not true, but it seems that instead of providing choice Mozilla has decided to force one solution onto everyone.
DRM protection could be as simple as passing all blocks of media data through a simple circular shift. The only "secret" part of the plugin would be the block size and the rotation size. Sure, such DRM is trivial to break, but then all DRM is eventually trivial to break - so if someone wants mild drm protection they could easily provide a plugin to do so.
However, there does not appear to be an api to provide small compiled bits of code/plugins. Am I missing something or is this really the case?
The ability to have competing DRM mechanisms has, in the past, provided protection from companies that have decided to abuse the need for DRM software to include all sorts of abuses, spyware, trojans, etc.