DRM Based on Trusted Computing Chips

An anonymous reader writes "We've always know that Trusted Computing is really about DRM, but computer makers always denied it. Now that their Trusted Computing chips are standard on most new PCs, they've decided to come clean. According to Information Week, Lenovo has demonstrated a Thinkpad with built-in Microsoft and Adobe DRM that uses a Trusted Computing chip with a fingerprint sensor. Even worse: 'The system is also aimed at tracking who reads a document and when, because the chip can report back every access attempt. If you access the file, your fingerprint is recorded.'"

Comments

Re:Oh no, I can hear them cry

[KitFox]

like "now this piece of shit tells me that I am not allowed to watch my damn video again just because I got my Windows reinstalled!"

Don't act like it's news. Microsoft already changed it's license agreement. Now, for all you folks who like to upgrade your computers, a new motherboard means you need to buy a new copy of windows for a new license. Yep! Windows MAY NOT be transferred between different PC's and changing out the motherboard constitutes a new PC according to Microsoft now. In fact, according to a Technet Community Chat, replacing a DEFECTIVE Motherboard still requires a new license! As they said:
"Q: k guys, my question is .i have a system i sold, mainboard is to handle a 3.2 processor but originally sold it with 2.4 with promise of upgradeability to 3.2, though main board works fine with 2.4 it does not with 3.2, is this considered a failed mainboard
A: This is still considered an upgrade if the motherboard is changed. You might want to try using the latest BIOS for the motherboard. If it still doesn't support the 3.2 GHz CPU and you replace the motherboard then you'll have to sell them a new OS." - Microsoft Technet Community Chat

Quite a bit of fun, no?

What about virtual machines?

[Anonymous Coward]

How would this sort of thing affect something like VMWare? If the O/S needs to be booted up on a trusted platform surely you won't be able to install it on a virtual machine. If the virtual machine can fool the O/S into thinking it's running on a trusted platform, doesn't that mean that you can get around the trusted component?

Re:getting out of computing?

[rbanffy]

We should not run. We should fight back.

Fortunately, we don't need firearms for this. We can stop using and recomending DRM capable hardware and we can halt software development for it. We must be very vocal in our opposition to this. We may may be few, but I am sure this audience is more influential than the average.

Re:Right but...Change is good

[Antique Geekmeister]

You're missing a lot of details about this software. It's closed source, and a violation of the DMCA to reverse engineer it. That means writing an open source version of the encryption/decryption tools is going to be a nightmare.

Second, running it at the OS level instead of the hardware level of the built-in features of the Intel CPU's is going to really slow it down: that will probably hurt performance a lot of open source versions of the Trusted Computing tools, even if they're legally created.

Third, the next logical stage of Trusted Computing is hardware locking: motherboards that won't load unsigned boot loaders, or won't access DVD drives or hard drives without being authenticated with Trusted Computing licenses to be held by OS distributions or DVD drive and software vendors. This can be used to block open source operating systems from even booting, or to prevent Trusted Computing managed DVD drives from being able to read DVD's that have Trusted Computing signed DVD's in them without a Trusted Computing signed media player.

It's very nasty, and it's at the core of why Microsoft and Hollywood are collaborating so well in this project.

Trusted Computing Rootkit - Cryptoviral Extortion

[NZheretic]

Trusted Computing DRM is the perfect plaform for Cryptoviral extortion : What is cryptoviral extortion?

4. What is cryptoviral extortion?

Cryptoviral extortion, which uses public key cryptography, is a denial of resources attack that was introduced in [YY96a]. It is a three-round protocol that is carried out by an attacker against a victim. The attack is carried out via a cryptovirus that uses a hybrid cryptosystem to encrypt host data while deleting or overwriting the original data in the process. The protocol is as follows:

(protocol setup phase) An asymmetric key pair is generated by the virus author on a smartcard and the public key is placed within the virus. The private key is designated as "non-exportable" so that even the virus author cannot obtain it's bit representation. Thus, the private key is generated, stored, and used on the smartcard. Ideally, the smartcard will implement two-factor security: something the virus author knows (a PIN number) and something the virus writer has (the smartcard that contains the private key). Also, the card will ideally be immune to differential power analysis, timing attacks, etc. to prevent the virus author from ever learning the bits of the private key. A standards-based approach can be used, e.g., the use of an approved FIPS 140-2 level 2 or higher device (e.g., when it is level 4 the private key will be destroyed if the casing is breached). In the U.S. the virus author cannot be forced to bear witness against himself or herself (Fifth Amendment) and so the PIN can remain confidential. The purpose of this setup phase is to limit the effectiveness of seizing and analyzing the smartcard under subpoena or warrant (competent evidence).

1) (virus author -> victim) The virus author deploys the cryptovirus. At a later time the virus activates on what could be tens or even hundreds of thousands of machines. The remainder of this description will cover the protocol for just one such machine. When the virus activates, it uses a true random bit generator (TRBG) to generate a symmetric key and initialization vector (IV) uniformly at random. It is essential that the TRBG produce truly random bits to prevent the symmetric key and IV from being guessed or otherwise determined by the victim at a later date. The virus then encrypts host data with this random symmetric key and IV (e.g., using cipher-block chaining (CBC) mode). The virus concatenates the IV with the symmetric key and then encrypts the resulting string using the public key of the virus author (e.g., using RSA-OAEP). The encrypted plaintext is then held ransom. The virus notifies the victim that the attack has occured (e.g., via a dialog box on the victim's screen) and states that the asymmetric ciphertext will be needed to restore the data. The virus author states his or her demands in return for the data. The virus author and victim can send asymmetrically encrypted messages to each other via a public bulletin board to try to preserve the attacker's anonymity. Alternatively, digital pseudonyms and mix-networks can be used.

2) (victim -> virus author) If the victim complies by paying the ransom and transmitting the asymmetric ciphertext to the virus author then the virus author decrypts the ciphertext using the private key that only the virus author has access to (the one on his or her smartcard). This reveals the symmetric key and IV that was used in the attack.

3) (virus author -> victim) The virus author sends the symmetric key and IV to the victim. These are then used to decrypt the data that was held ransom.

(security) The attack is ineffective if the data can be recovered from backups. Antiviral experts cannot retrieve the private decryption key by analyzing the virus since only the public key will be found. The importance of using hybrid encryption can be seen from the followi

Re:Right but...Change is good

[marcosdumay]

You mean that we can create more artificail scarcity, that will create more artificial markets where people trade more virtual goods. All that while adding near to zero worth on the real markets out there.

We really need to get out of those pyramids. Not create more.