Hi guys,
I belive that we are taking to many steps at a time here when discussing DRM. As Christian pointed out, DRM, in general, provides means for owners of some content to control what others are allowed to do.
In oder to implement those means, the content is usualy encrypted, and only conforming applications are allowed to decrypt the content. This is where it gets quite complicated, because it somehow has to be ensured, that only the 'right' applications are able to decrypt the content.
Today, this is implemented through closed source implementations as is with media-players, or licensing as with DVD player hardware.
These are models of which I don't know how they could be applied to open source software. Anyone could recompile the application and just comment out the restriction checks.
Is anyone aware of a way those two concepts can co-exist? Because as soon as the content has been decrypted, an application could do anything with it, which renders DRM virtually unusable on the application level. DRM on the hardware level (like trusted computing) however still needs Applications to be authorized.
Can anyone think of a scenario that would work?
~Lars
-- Lars Oppermann <[EMAIL PROTECTED]> Sun Microsystems Inc. Software Engineer - StarOffice http://www.sun.com/staroffice
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
