4 ms·
> DRM's dark history — from the Sony rootkit malware to draconian anti-circumvention laws — demonstrates that integrating it into Web standards would be nothing
by lucb1e 10y ago
> DRM's dark history — from the Sony rootkit malware to draconian anti-circumvention laws — demonstrates that integrating it into Web standards would be nothing but bad for Web users.
This is where I get scared. What if DRM does not become a web standard? What is the alternative that companies will want to use instead?
That is for me the only reason why standardization might potentially be a good thing. Not because DRM is good, but because the alternative might be worse.
Everything in the past has been broken anyway. From CSS to AACS to HDCP[1]. I was hoping Firefox (and perhaps Chromium, but Google would probably not be so kind as to open source that part of the code) would have the DRM code built in so that we can spoof the whole thing with simple modifications. Better than having to reverse engineer Sony malware.
[1] https://en.wikipedia.org/wiki/Illegal_number https://en.wikipedia.org/wiki/Illegal_number
- gsnedders 10y ago> From CSS to AACS to HDCP[1]. I was hoping Firefox (and perhaps Chromium, but Google would probably not be so kind as to open source that part of the code) would have the DRM code built in so that we can spoof the whole thing with simple modifications. That fails to fulfil the requirements of pretty much any level of DRM, and hence such an implementation would be totally ignored and unused, and sites would continue to use Flash in preference to it. (I wish I could find the document Google published last year about the different levels of DRM the industry has been concluded need to exist for them to use; alas, I cannot!)
- lucb1e 10y ago> such an implementation would be totally ignored and unused Yeah I am a bit scared of that too, but then what would be the point of standardization in the first place?
- gsnedders 10y agoPrimarily to have a standard API to determine what DRM schemes the UA supports. A less important part of it is to avoid a different code-path for each different DRM scheme each with its own API.
- kijin 10y agoIf you standardize it, you legitimize it. The most important difference between Sony malware and an open-source crypto library is not that the former is more difficult to reverse-engineer. It is that the former is illegal to reverse-engineer, at least in some parts of the world. This is what gives content owners the illusion that their DRM protects them. They are not looking for bulletproof technical protection. Social and legal high ground is good enough for them and their propaganda machine. If DRM becomes standardized, it becomes much harder for the rest of us to make a convincing argument that this crap is not what the web was meant to be. The next thing you know, users of DRM-free browsers will be shown error pages telling them upgrade to a more standards-compliant alternative.