Linked by David Adams on Tue 29th Jun 2010 17:39 UTC, submitted by waid0004
Thread beginning with comment 431968
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2008-12-26
I don't understand what you are saying here. DRM is not about package managers, it's about what those applications can do after they have been installed.
DRM can work like this:
- Download program Foo
- App manager verifies that it's okay and extracts the package. It stores the checksum of all the files it installs
- When the app is launched, it can access hidden data storage called FooSecrets (with encryption keys/whatever). It's the only application that can access that data storage.
- If you try to replace application Foo with your own application, kernel sees that checksum has changed. The application will run, but it will not allow you to access FooSecrets anymore.
FooSecrets is not accessible in the local file system - rather, it's in a "fritz chip" (trusted platform module). Only a pristine unmodified kernel can see the device, because it's enabled by the bootloader.