Latest Gear Live Videos
Tuesday August 2, 2005 11:45 am
Why Trustworthy Computing Is A Bad Idea
A number of sites have picked up the story that Intel Developer kits from Apple include TCPA/TPM DRM in the Kernel. TCPA/TPM DRM is a technical term for a Trustworthy Computing solution that limits what fair use consumers can use with the media they own. Basically it lets an application control what other applications or pieces of hardware can access it’s files. For instance a file created in Quicktime could be signed with a quicktime flag meaning no 3rd party applications or other users could view that file. There has been no word on how Apple is going to implement TCPA/TPM DRM yet, but conceivably they could use it to say that no non-DRM’ed pieces of media could be played on a machine making the assumption that if a file does not include DRM then it must be pirated. TCPA/TPM DRM also features the ability to create a secure encrypted channel between a graphics card and a monitor that supports TCPA - this unfortunately not only would help “prevent” piracy by capturing the live stream from the computer to the monitor (something not really done in practice anyway) but would force you to buy a TCPA compliant monitor.
Of course Windows Vista will have TCPA/TPM DRM built in as well - it’s one of Microsoft’s big selling points. I’m not sure how they are spinning it as a benefit to consumers as this does nothing but hurt innocent users wishing to exercise fair use of their content - pirates will always find a method to getting around DRM solutions. TCPA is a technology that only hinders consumers, and benefits no-one but the MPAA, RIAA, and other large greedy organizations that don’t trust their paying customers. With both Apple and Microsoft playing into the media organizations wishes for TCPA to be widely adopted then the consumer loses choice, freedom, and the ability to exercise fair use of the media they both own and enjoy. Check out a possible solution and more information about TCPA after the jump.
Luckily Apple customers will have a choice of sorts - unlike Windows operating systems OS X’s kernel Darwin is an open source project - Darwin and the BSD subsystems source code is freely available under the Apple Public Source License (APSL), a license similar to GNU. APSL permits the modification and redistribution of the Darwin source code permitting that you follow certain restrictions. Under APSL you are permitted to modify the software without public distribution without limit.
It is therefor possible for future users of Intel based OS X users to make a choice - to have Trustworthy Computing features, or to run a script (which will be easy and legal to distribute) which will remove the TCPA features, recompile the Darwin Kernel locally, and then reboot to their newly TCPA-free kernel. Mind you - in doing this parts of the operating system that rely on TCPA would of course no long work - iTunes, and Quicktime for sure would break, as would any other media centric application that was being developed for the to rely on TCPA being present in the kernel. Mind you - giving up those applications would make OS X a less attractive option in the marketplace, you the consumer can at least rest easy knowing that you have that option.
At this point Apple is preventing this by requiring TCPA for use of the Aqua GUI - a feature to prevent OS X from being hacked into working on non-Apple sold hardware. This is one of the few legitimate uses of TCPA - Apple deciding that inferior hardware should not be able to run their product and thus possibly give the user a less stable experience. This does unfortunately mean that if a user chooses to remove TCPA from their kernel they would be unable to boot into GUI mode on their computer - Apple sold or otherwise, but they would have the option of using Darwin and the BSD subsystem as they please. Whereas this Gear Live editor disagrees strongly with Apples decision to restrict OS X to their hardware anyone can see the reasoning - when a company loses control of their hardware they lose control of their software and it’s ability to rely on specific hardware compatibilities or levels of quality control - think about how many people complain when Windows crashes frequently on the cheap hardware so present in the marketplace at the moment. In an ideal world anyone would be able to legally purchase their copy of OS X and run it on any machine they chose to accepting that if you ran it on non-Apple hardware that I was going to have the occasional system crash or incompatibility - then again this is not a perfect world and things like Trustworthy Computing really go a long way to remind us all of that.
Is Linux going to be the answer? Will Linux be the last bastion of DRM free computing where the user is in control of their system, and not a faceless corporation bent on increasing profits at the expense of the consumer? The only hope to avoid this eventuality is for the free media revolution that sites like the Pod Safe Music Network are starting and for this to spread to all forms of audio, video, and text content. In that media utopia the consumer and artists win, and DRM looses. Where do you, our readers put your proverbial dollar in this war on DRM?
Read More
| Intel Developer kits with TCPA
Read More
| Great Essay by Cory Doctorow on TCPA
- Related Tags:
Advertisement
Advertisement
Advertisement
© Gear Live Inc. – User-posted content, unless source is quoted, is licensed under a Creative Commons Public Domain License. Gear Live graphics, logos, designs, page headers, button icons, videos, articles, blogs, forums, scripts and other service names are the trademarks of Gear Live Inc.
Digg This




Comments:
The author didn’t look into how the TPM DRM is being used on the developer machines before writing that. It’s been discovered the kernel has the basic calls to access the TPM chip via a module, and Rosetta requires TPM to function. The GUI is not blocked out because it has been coded to require TPM, the GUI fails to start because a few small pieces are still PPC code on the developer machines, thus requiring Rosetta, thus requiring TPM.
I am going to reserve judgement on all of this for when Apple actually ships a consumer x86 box. DRM isn’t a dirty word, it’s what you do with it that might be dirty. If Apple protects their core buisness of selling hardware by locking OS X to their hardware, then guess what, nothing has changed. I can’t load OS X on an IBM PowerPC server today, and that didn’t stop me from buying a Powerbook. If I can’t load OS X tomorrow on a Dell, I still won’t care.
I will however care if they do go forward with additional DRM trickery. But considering how long Tiger and PowerPC Macs will be supported, they either would have had to start on the DRM path before the switchover, or only be able to enforce DRM restrictions on a very small percentage of Mac users in 2006.
Reply to this: comment | thread
Drakino,
You are correct and I may have written the article in a misleading way. I don’t think all DRM is bad, just that it can and most often is used incorrectly. I really don’t have that big of a problem with Apple restricting their operating system to their hardware with DRM, I just fear the slippery slope that could follow. Once TCPA is common on many operating systems and over several versions it’s easy to “tighten your grasp” or be forced to by content providers because the capability is there.
I’m not saying I won’t buy a Intel based Mac with TCPA in it - I’m just saying that I’ve very wary of what this bodes for the future, and if it does get bad I’ll have to look to other solutionms.
Reply to this: comment | thread
Comments: Page 1 of 1 pages