Linked by David Adams on Tue 29th Jun 2010 17:39 UTC, submitted by waid0004
Windows An Italian Windows site called "Windowsette" has published some purported secret Microsoft documents outlining some design and strategy plans for Windows 8. The Microsoft Kitchen blog has provided some analysis of the documents. The documents appear genuine, and there's lots of interesting information there.
Thread beginning with comment 431942
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: standards but DMR
by lemur2 on Wed 30th Jun 2010 00:03 UTC in reply to "RE: standards but DMR"
Member since:

Standards and drm by no mean rule each other out. DRM is basically just a way to encrypt data in a manner where only a predefined program (or set of programs) gets access to them. It doesn't imply you have to use obscure data formats. And it does improve sourcing options, because now instances that refuse to distribute their data without encryption can play.

Nitpick: Signing packages (which involves encryption) as an integrity check is part of the way that Linux package managers work. This is not DRM howver, because it is not third-party rights that are managed ... it is just simply an integrity check.

One can't have a repository or package manager (or App store) work properly without integrity checks involving encryption, but only an App Store requires DRM.

Reply Parent Score: 2

RE[3]: standards but DMR
by vivainio on Wed 30th Jun 2010 08:08 in reply to "RE[2]: standards but DMR"
vivainio Member since:

Nitpick: Signing packages (which involves encryption) as an integrity check is part of the way that Linux package managers work. ...

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.

Reply Parent Score: 2