-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Lars Oppermann wrote: | Daniel Carrera wrote: | |> Lars Oppermann wrote: |> |>> While defining a DRM container is possible (as we all aggree), the |>> problem is with the enforcment of that container on an open platform. |>> 'Enforce' and 'open' just don't work well together I guess ;) |> |> |> Though it's not inconceivable. After all, the most powerful encryption |> algorithms (El Gamal, Blowfish) are open. |> |> Let's see if we can look at DRM from that approach. Ecryption systems |> can be open and reliable because their security depends not on the |> secrecy of the algorithm, but the secrecy of a key. Therefore, we |> might guess that an open DRM system would have to be similar. |> |> I don't have a direct application of that to DRM, but I wanted to |> throw that out for brainstorming. | | | The problem here seems to be, that DRM starts where encryption ends. <snip> | Bests | ~Lars |
There has been prior discussion on this topic (check the archives if interested) but I will summarise my previous comments thus: The only reason apparent to me for the use of DRM on office documents (movies and music may be a separate argument) is to allow a vendor of proprietary software to lock-in existing customers, not only to their product, BUT potentially forcing upgrades on a schedule of the vendor's choosing - all to access your OWN data. The other possible scenario is where a market mismatch exists (e.g. large customer:small supplier) then a business may find it necessary to purchase a proprietary product to continue dealing with their large and very important customer.
DRM, IMO, does not add anything worthwhile that is not already available ~ via PKI encryption/authentication - which doesn't require a proprietary solution.
Ric
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCAtpYzF8kS4Euk0QRAstcAJ0Q/9ZqP5Jt4mwAfDnprnbHho4hVACgoMOC 72AoWtuqKLr0CNU9gHSFhHs= =z+bN -----END PGP SIGNATURE-----
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
