W3C home > Mailing lists > Public > public-html-media@w3.org > February 2013

Re: Oppose DRM ! Re: CfC: to publish Encrypted Media Extensions specification as a First Public Working Draft (FPWD)

From: Mark Watson <watsonm@netflix.com>
Date: Tue, 12 Feb 2013 15:08:06 +0000
To: Henri Sivonen <hsivonen@iki.fi>
CC: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, "Timothy B. Terriberry" <tterriberry@mozilla.com>, "public-html-media@w3.org" <public-html-media@w3.org>
Message-ID: <0F2E0D51-C3C4-4EB0-9B7E-57FB45F1AD43@netflix.com>


Sent from my iPhone

On Feb 12, 2013, at 5:55 AM, "Henri Sivonen" <hsivonen@iki.fi> wrote:

> (Moving from -admin to -media.)
> 
> On Tue, Feb 12, 2013 at 5:03 AM, Mark Watson <watsonm@netflix.com> wrote:
>> There is also this: http://sourceforge.net/projects/openipmp/ ?
> 
> It seems that this is an implementation of OMA DRM. Upon quick
> inspection, it seems to me that OMA DRM depends on a client-side
> secret (private key for a public key) that the user can't read or
> replace and on the DRM-related software on the client device not being
> user-modifiable. Have I understood correctly?

I'm not familiar with how the key provisioning works, but yes, in general DRM relies on there being a non-user-modifiable* component on the client side (this should be obvious based on the goals of DRM).

...Mark

* of course I mean 'difficult to modify for some formal definition of difficult'.
> 
> -- 
> Henri Sivonen
> hsivonen@iki.fi
> http://hsivonen.iki.fi/
> 
Received on Tuesday, 12 February 2013 15:08:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:48:32 UTC