"You may not impose any further restrictions" means you cannot build the hardware
Dear moron, people who build the hardware don't have to follow GPL. HTH.
Have you ever read the spec? I have, and I can find nothing like what you're saying in it.
The TCM is designed to tell others the truth about software you're running. Nothing more, nothing less. If you're not comfortable with it, you have the option to be silent, but you don't have an option to lie. Well, you can try, but no one will trust you. That's all there is about it.
CSS is broken because someone left the keys in the open (and they are too short to be secure anyway). If DVDCCA disallowed software players, and used 128-bit keys, there would be no deCSS. That's more or less what will happen with TPM.
If you don't have a blue-laser disc player, your feature will not work either, GPL or no GPL. If you don't have the right hardware, your app won't work. Similarly, if you don't have the right keys to send to the right hardware, your app won't work. The hardware, as well as the keys, are not parts of the (GPLed or not) software. It's your responsibility to obtain them, and it's your choice how do you do that. (For the keys, I suggest running a signed copy.)
All features of your modified executable will work. DRM servers of media corps will refuse to give you keys for playing their content, because you won't be able to lie to them. But who told you that you have a right to get these keys by lying?
You just can't get them signed. Unless you somehow persuade the signing authority to review your modifications, that is.
Unsigned binaries won't be able to play play DRMed files (which you shouldn't have anyway) but should still work with your normal files. The trusted CPY will be happy to execute them, it will just refuse to flag them as trusted.
You could send messages that self-destruct in ten seconds after being opened. That's silly, I know.
Well, security of communication is a big plus in any case. These little suckers, among other things, should be more resistant to pwnage than present day systems.
If you need more speed, you don't take more reaction mass with you, you just pump more energy. There's no limit as to how much external energy you can apply (within reason:)
to the velocity of outgoing paint molecules. That's momentum conservation:v_craft*m_craft = v_paint*m_paint. To increase velocity, you just pump more energy (and maybe use paint that boils at higher temperature).
something called "stored energy density". For rocket fuel it's X J/kg (look up a suitable value for X, I'm lazy). For microwaves it's exactly infinity J/kg because microwaves are not stored on board. There's some difference, eh?
If you want your own format, go ahead and create one. You don't need MS schemas for that. You *only* *need* them to read and write MS formats. And you can use them for that purpose.
A file format which anyone could modify would not be "just" open, but really free. We don't expect MS to go that far.
About the IP law, I mean. It is generally held that one cannot copyright a language (an XML schema is a language in my view) but apparently there are some patent issues. In addition, the files that physically contain things such as XML schemata may be copyrighted. You probably can code one up yourself from the documentation, in which case it would be legal to use (maybe, IANAL).
Now, there's a license that allows you to use these things. You can use the patents only to read and write MS files, but that's the only thing you need them for anyway. There's only one other slight problem, that of of required attribution. But it's mostly theoretical. You can't distribute your XSLTs under GPL, big deal. Sounds open enough for my purposes.
Slashdot Mirror
There's a paper on how trusted computing can enable more secure, user-friendly P2P neetworks. It's linked to here somewhere, look it up.
Glad some people figure it out. Microsoft is opposed to TCPA (now called TCG) exactly because it's an open spec.
"You may not impose any further restrictions" means you cannot build the hardware Dear moron, people who build the hardware don't have to follow GPL. HTH.
One per chip, not one per maker/model.
Thank you very much. So I figure you haven't read the spec?
They will go all happy happy joy joy. Or something something.
The TCM is designed to tell others the truth about software you're running. Nothing more, nothing less. If you're not comfortable with it, you have the option to be silent, but you don't have an option to lie. Well, you can try, but no one will trust you. That's all there is about it.
CSS is broken because someone left the keys in the open (and they are too short to be secure anyway). If DVDCCA disallowed software players, and used 128-bit keys, there would be no deCSS. That's more or less what will happen with TPM.
If you don't have a blue-laser disc player, your feature will not work either, GPL or no GPL. If you don't have the right hardware, your app won't work. Similarly, if you don't have the right keys to send to the right hardware, your app won't work. The hardware, as well as the keys, are not parts of the (GPLed or not) software. It's your responsibility to obtain them, and it's your choice how do you do that. (For the keys, I suggest running a signed copy.)
All features of your modified executable will work. DRM servers of media corps will refuse to give you keys for playing their content, because you won't be able to lie to them. But who told you that you have a right to get these keys by lying?
Amen i say.
Those idiots in the TCPA alliance would never think about it. I feel safe in your hands.
Unsigned binaries won't be able to play play DRMed files (which you shouldn't have anyway) but should still work with your normal files. The trusted CPY will be happy to execute them, it will just refuse to flag them as trusted.
Well, security of communication is a big plus in any case. These little suckers, among other things, should be more resistant to pwnage than present day systems.
Better yet, lead 'em. It would be ridiculously funny if Trusted $FREENIX were released before Trusted Windows or Trusted MacOS.
this particular character when you hit single-quote key on your keyboard. Or do they?
Says something about our editors, eh?
If you need more speed, you don't take more reaction mass with you, you just pump more energy. There's no limit as to how much external energy you can apply (within reason :)
to the velocity of outgoing paint molecules. That's momentum conservation:v_craft*m_craft = v_paint*m_paint. To increase velocity, you just pump more energy (and maybe use paint that boils at higher temperature).
something called "stored energy density". For rocket fuel it's X J/kg (look up a suitable value for X, I'm lazy). For microwaves it's exactly infinity J/kg because microwaves are not stored on board. There's some difference, eh?
You're not a physicist either. Or a speller, for that matter.
can't you attach the power supply and microwave emiter to the craft?
Sure, just give me a power supply of zero mass. Pure genius.
will you? You don't carry your "fuel source" with you, because fuel is energy and you don't carry energy, you carry only working body.
A file format which anyone could modify would not be "just" open, but really free. We don't expect MS to go that far.
Now, there's a license that allows you to use these things. You can use the patents only to read and write MS files, but that's the only thing you need them for anyway. There's only one other slight problem, that of of required attribution. But it's mostly theoretical. You can't distribute your XSLTs under GPL, big deal. Sounds open enough for my purposes.
Use a browser recommended by Microsoft. Really, do it. And an operating system while you're at it. Don't even ask me about the mail client.