Content deleted Content added
enforcer linux security module |
audio output would be secure up to the hardware (but obviously insecure once outside the computer) |
||
Line 81:
One of the early motivations behind trusted computing was a desire to support stricter [[Digital Rights Management]] (DRM): technology to prevent users from sharing and using copyrighted or private files without permission. Microsoft has announced a DRM technology that it says will make use of trusted computing.
Trusted computing can be used for DRM. An example could be downloading a music file from a band: the band could come up with rules for how their music can be used. For example, they might only want the user to play the file three times a day without paying more money. Also, they could use remote attestation to only send their music to a music player that enforces their rules: sealed storage would prevent the user from opening the file with another player that did not enforce the restrictions. Memory curtaining would prevent the user from making an unrestricted copy of the file while it's playing, and secure output would prevent capturing what is sent to the sound card - although the sound card's output could still be recorded externally by conventional means, such as by simply connecting an audio
Without remote attestation, this problem would not exist. The user could simply download the song with a player that did not enforce the band's restrictions, or one that lets him convert the song to an "unrestricted" format such as [[MP3]].
| |||