Even in our own country I can think of two specific examples of repressive laws & organizations being broken up without a revolution. Look at Teddy Roosevelt busting up various trusts (something that was unprecedented), or the albeit painful development of equal rights for women and blacks. Especially in the case of racial discrimination there were numerous laws to not only enforce discrimination, but disenfranchise those people who the Federal government was explicitely trying to give a voice.
I know a lot of ideas have already been tossed around, but here a couple more...
As much as I get annoyed with the fact that my windows installation seems to need a new security patch every week, it's a distinct advantage of a software system that it can be updated so quickly and easily. What will happen if (or when) a bug is found in the hardware part of Palladium? Will there be something to the extent of a bios update? Will there be a software work around? Will people have to go out and get a new chip (and if so, what happens to those who don't do it as quickly as others).
I don't know if you want to find out the answer to this one, but let's assume that a Palladium system can prevent digital copying 100% of the time on signed media that they don't want copying. What's to stop someone from doing something as simple as connecting a tape recorder or VCR to an A/V connection and thereby making an "unsigned" copy of the media to be distributed on your peer to peer network of choice? The answer I see could be nothing (which would undermine the ability to actually manage digital rights) or that Palladium my cut out A/V (or other) devices, which I would find VERY scary.
What would the exact criteria be for getting programs or code to be certified "Palladium Compliant". For example, let's say I work for a bank that has online banking software, and we find a hole or bug that MUST be fixed. Would every iteration of code have to be sent to MS or some third party for 'approval'. Also, not to be cynical, but if MS is the one doing quality control, how do they respond to the fact that some of their products are just a tad lacking in quality of code?
Finally, if someone were to hack a Palladium signature, and potentially shut down, control, erase, etc. a users machine, what would type of recovery procedures would there be (or even controls to ensure that a signed program isn't doing something it shouldn't be).
Slashdot Mirror
Even in our own country I can think of two specific examples of repressive laws & organizations being broken up without a revolution. Look at Teddy Roosevelt busting up various trusts (something that was unprecedented), or the albeit painful development of equal rights for women and blacks. Especially in the case of racial discrimination there were numerous laws to not only enforce discrimination, but disenfranchise those people who the Federal government was explicitely trying to give a voice.
I know a lot of ideas have already been tossed around, but here a couple more...
As much as I get annoyed with the fact that my windows installation seems to need a new security patch every week, it's a distinct advantage of a software system that it can be updated so quickly and easily. What will happen if (or when) a bug is found in the hardware part of Palladium? Will there be something to the extent of a bios update? Will there be a software work around? Will people have to go out and get a new chip (and if so, what happens to those who don't do it as quickly as others).
I don't know if you want to find out the answer to this one, but let's assume that a Palladium system can prevent digital copying 100% of the time on signed media that they don't want copying. What's to stop someone from doing something as simple as connecting a tape recorder or VCR to an A/V connection and thereby making an "unsigned" copy of the media to be distributed on your peer to peer network of choice? The answer I see could be nothing (which would undermine the ability to actually manage digital rights) or that Palladium my cut out A/V (or other) devices, which I would find VERY scary.
What would the exact criteria be for getting programs or code to be certified "Palladium Compliant". For example, let's say I work for a bank that has online banking software, and we find a hole or bug that MUST be fixed. Would every iteration of code have to be sent to MS or some third party for 'approval'. Also, not to be cynical, but if MS is the one doing quality control, how do they respond to the fact that some of their products are just a tad lacking in quality of code?
Finally, if someone were to hack a Palladium signature, and potentially shut down, control, erase, etc. a users machine, what would type of recovery procedures would there be (or even controls to ensure that a signed program isn't doing something it shouldn't be).