That means you have to 'tell' MS when you make your system dual boot and write a GRUB MBR to your boot partition. Tell me that there is no potential for abuse here.
yup. That's the part that concerns me the most. Not just overwriting your MBR -- what about the potential of the TCPA subsystem in collaboration with the TBB to block your own device drivers written for your own (experimental, read: uncertified) devices? What will this enable CAs to do to smaller electronics firms? Everyone loves it when you can get, say, an optical mouse for a fraction of the cost of the M$ certified one -- and when the cheaper one works with linux. What happens when the insert your new cool device here is probed by the TBB at power-up, prior to boot, and is written off as "device not found" simply because it came from some guy's garage up in San Leandro.
Sure, it SAYS you can deactivate TBB/TCMA, but can you really? What if half your other devices require it to be activated in order to run at all? Then you'd have to grandfather in your new device as a "legacy" device, in the nomenclature of the spec itself.
So it's not just a matter of "What will DRM/Palladium/Trusted Computing do to people who write and distribute their own code? Music? Eyewitness reports of police brutality? People who seem to be having a hard time getting dist keys from the CA?" It's more like something that could kill innovative small companies in the computer industry -- you know the ones who design and build third party peripherals that compete with -- oh! Compaq, HP, IBM, Microsoft and Intel! Gee isn't that interesting that they're also the ones drafting the trusted computing standard?
You know, I'd trust "trusted computing" more if
it were coming from the IEEE or IETF. Shoot, even the ISO would be welcome here. The usual suspects for drafting standards seem to be noticable by their absence on this one.
Slashdot Mirror
yup. That's the part that concerns me the most. Not just overwriting your MBR -- what about the potential of the TCPA subsystem in collaboration with the TBB to block your own device drivers written for your own (experimental, read: uncertified) devices? What will this enable CAs to do to smaller electronics firms? Everyone loves it when you can get, say, an optical mouse for a fraction of the cost of the M$ certified one -- and when the cheaper one works with linux. What happens when the insert your new cool device here is probed by the TBB at power-up, prior to boot, and is written off as "device not found" simply because it came from some guy's garage up in San Leandro.
Sure, it SAYS you can deactivate TBB/TCMA, but can you really? What if half your other devices require it to be activated in order to run at all? Then you'd have to grandfather in your new device as a "legacy" device, in the nomenclature of the spec itself.
So it's not just a matter of "What will DRM/Palladium/Trusted Computing do to people who write and distribute their own code? Music? Eyewitness reports of police brutality? People who seem to be having a hard time getting dist keys from the CA?" It's more like something that could kill innovative small companies in the computer industry -- you know the ones who design and build third party peripherals that compete with -- oh! Compaq, HP, IBM, Microsoft and Intel! Gee isn't that interesting that they're also the ones drafting the trusted computing standard?
You know, I'd trust "trusted computing" more if it were coming from the IEEE or IETF. Shoot, even the ISO would be welcome here. The usual suspects for drafting standards seem to be noticable by their absence on this one.