You need to be logged in to post in the forums. If you do not have an account, please sign up first.
DRM-like Encryption in HTML5
HTML5 is supposed to set the web free. Free to deliver and shape online media in any web browser. However, several of the standard's greatest champions want to be able to restrict the use of audio and video tags through encrypted media extensions.
So far about the new HTML5 standards and their champions.
New standards have to please big money first.
Thereafter they have to please content providers.
The consumer/user as always comes last.
Every morning a lion wakes up. It knows it must outrun the slowest gazelle or it will starve to death.
It doesn't matter whether you are a lion or a gazelle: when the sun comes up, you'd better be running.
It seems to me that this is simply a request for a key-based decryption option to be included in the standard, to be employed (or not) by the original owner of the content. Unless one is philosophically opposed to copyright, I'm having difficulty seeing the problem here.
...The proposed system works using a key-based content decryption system controlled by applications, thusly providing the copy protection that so many content owners desire. Naturally, the proposal specifically states that "no DRM is added to the HTML5 specification" if it's adopted, but letting apps lock up audio and video content sure sounds like digital rights management to us. ...
Really, I don't see it mattering to the browser if the stream is encrypted. It isn't the page that is encrypted, there may not even be anything within the page saying whether the video is or not. The playback engine would see the file is encrypted and ask for a key (not the browser) ... so, it's not DRM-like (it is DRM), but it's not in HTML5 either.
1. March 2012, 18:54:30 (edited)