I wonder how compiler vendors are going to deal with this? Will each compiler be assigned a digital signature to imbed in the dll, or does this mean we are going to have to include a spoof for every C program we compile for Windows?
This kind of legislation is difficult to implement in practice. Unless someone signs a Non Disclosure Agreement and then releases information that he or she received while under the NDA, how could you prosecute? If the information leaked is not an exact copy of the classified information, who decides where the "dew point" is whereby information could actually be seen as having been "leaked"?
Ever since the media reported that negative incident with NT, I have had a hard time believing that we have all the facts we need to make a good judgement.
Slashdot Mirror
I wonder how compiler vendors are going to deal with this? Will each compiler be assigned a digital signature to imbed in the dll, or does this mean we are going to have to include a spoof for every C program we compile for Windows?
Probably depends on whether the force varies with the square of the distance, the cube of the distance or some other multiple.
The article said the 57 year old man kept three of the rotors? Sounds like a conspiracy :)
It's not fair, the good witch wasn't the math major. I guess now I will have to use my public keys only once to send a longer symmetrical key.
This kind of legislation is difficult to implement in practice. Unless someone signs a Non Disclosure Agreement and then releases information that he or she received while under the NDA, how could you prosecute? If the information leaked is not an exact copy of the classified information, who decides where the "dew point" is whereby information could actually be seen as having been "leaked"?
Ever since the media reported that negative incident with NT, I have had a hard time believing that we have all the facts we need to make a good judgement.