On Thu, Feb 23, 2012 at 3:25 PM, Tab Atkins Jr. <jackalmage@gmail.com>wrote: > This does not solve the problems brought up last time against adding > DRM to <video>. In particular, a browser like Mozilla is *legally > prevented* from actually implementing DRM, because they have to reveal > all their code, including the decryption code that contains the > secrets you use to decrypt. does that mean that mozilla must publish the code for every OS it runs on? does FF not employ APIs implemented by the OS for which it has no control or even knowledge of implementation details? i don't see any difference in using an abstract DRM or CP API that maps to a concrete, undisclosed OS implementation and any other uses of OS APIs by a browser
Received on Thursday, 23 February 2012 23:07:22 UTC