W3C abandons consensus, standardizes DRM, EFF resigns

Re:W3C abandons consensus, standardizes DRM, EFF resigns by tptacek on Monday September 18, 2017 @04:54PM (#15279467)

I don't know a lot of software security people who work on browser security that agree with this. The prevailing sentiment is the opposite: that standardize DRM reduces the attack surface of proprietary DRM down to that of a CDM, rather than full-featured browser plugins. By doing so, EME is improving security, not damaging it.

[ Parent | on HN ]

Re:W3C abandons consensus, standardizes DRM, EFF resigns by icebraining on Monday September 18, 2017 @06:07PM (#15280106)

We could have neither, though.

[ Parent | on HN ]

Re:W3C abandons consensus, standardizes DRM, EFF resigns by tptacek on Monday September 18, 2017 @06:47PM (#15280368)

By what, banning plugins? Now you're asking the anti-DRM people to do exactly what they're angry at the pro-DRM people for doing: preventing people from running a particular kind of program on their computer. It's an incoherent position.

[ Parent | on HN ]

Re:W3C abandons consensus, standardizes DRM, EFF resigns by Furmark on Wednesday September 20, 2017 @04:49AM (#15291791)

Not banning, simply not providing api for them.

[ Parent | on HN ]

Re:W3C abandons consensus, standardizes DRM, EFF resigns by tptacek on Wednesday September 20, 2017 @11:51AM (#15295113)

That doesn't work. Look what happens with AV providers: they hack their own plugin interface into the browser, and everybody loses more security.

[ Parent | on HN ]

Re:W3C abandons consensus, standardizes DRM, EFF resigns by madez on Monday September 18, 2017 @08:39PM (#15280926)

You can have arbitrary exceptions to ensure coherency. There is no reasonable need to have a position without exceptions. Reality isn't that simple.

[ Parent | on HN ]