yep, they're completely different animals. Trustworthy computing: ensuring reliability and integrity of the user experience Trusted computing: securing the system against the user.
I thought Trustworthy Computing was a scheme intended to ensure that no part (of the user experience) could fail?
As opposed to Trusted Computing, which I think is what you're actually referring to here, this instead of protecting the system from failure, secured the system against user violations such as overwriting the bootloader with one that isn't signed (like for instance, replacing or enhancing the BIOS with a signed EFI that prevents the user from installing alternative OSes such as OSX onto a commodity x64 or GNU/Linux onto a MS-subsidised laptop (think £250 deal at PC World. How do you think they get so cheap?)), TPM and TXT which can be used in tandem to lock a software license/instance to a specific machine using a specific hardware setup where the hardware has burned-in unique RSA hashes per device (didn't MS do this with Windows at one point where even replacing a wireless card killed the COA key?), Asshole Detectors (I don't know if this term is in common use, it just sounds cool) such as XBox Live, and vendor lock-in on the pretext of securing a closed network (such as the aforementioned XBox Live, any number of persistent online games such as World of Warcraft...)...
Dre never attended college, he tried getting into Northrop Aviation but they wouldn't even take him on as an apprentice because his GPA was so low. Source: http://uk.ask.com/question/wha...
uh... founded in the US: check. Headquartered in the US: check. Trades on the NASDAQ: check. Pioneered the Double Irish with a Dutch Sandwich tax dodge to reduce its global tax bill to.06% of pre tax earnings (which only works in the American tax system): check.
I think Apple, Inc. owes the United States a bit fucking more than mere allegiance.
no, it didn't. It was there in Magna Carta, it was extended to include everyone in the Liberty of Subject Act of 1354. Loosely contemporised, it reads "No punishment without crime".
actually, there is the Stored Communications Act which protects mobile phone data from incident searches: also refer to the Riley decisions (Riley v. California and United States v. Wurie). THIS DOES NOT prevent searches specific to data known to exist even if it's locked down (Wisconsin v. Feldman). Argument could be (has been in England recently but citations escape me) made that refusal to disclose decryption passcodes to obtain data known or suspected to exist is confirmation of its existence and nature (Guilty until Proven Innocent). Such legal behaviour, I suspect, has also been employed to justify several detentions of indeterminate length at Gitmo.
This. Hardware specific keys are the killer for any forensic attempt. It makes breaking a copied image totally impossible (otherwise what would be the point?). Combine that with a baked bruteforce/tamper killswitch, and you have a secured drive that has just one weakness: the ability of its owner (or not) to resist the charms of law enforcement.
"You do not have to say anything but it may harm your defence if you do not mention when questioned something you might later rely on in court."
What the caution should say, is "...it *WILL* harm your defence..."
You still have the right to silence in England, the new inference is that you are guilty until you prove your innocence (by talking to the police during the interrogation stage).
(also, that by remaining completely silent you're more than likely to be sectioned under the Mental Health Act, the Official Solicitor is called in and your most basic human rights are abrogated including your right to not be experimented on like a lab rat).
my project, my code until it's paid for. Contract terms agreed by all parties. When the buyer says "I'm not paying you", are you going to leave your fucking toolbox on his forecourt?? Are you actually fucking INSANE??
Core: ancient Dell laptops, which are nice and quiet and run on 70W power supplies. Seven of those, and five dozen hard drives from 120GB all the way up to 2TB apiece either in USB enclosures or in rackmount/grab boxes which are in turn connected via USB IDE adapters. So there's some hotswapping involved but all told I have about 40TB of storage.
I've killed projects* half an hour from full deployment because certain parties refused to stump up their end of the contract.
I am NOT building databases because I enjoy the challenge. I don't, in fact databases are the bane of my existence. I would rather deal with the hardware side of things.
*by killed read: walked away with the entire project source on a flash drive in my pocket and all backups obliterated, all orders for hardware cancelled and a note on my workbench saying "Pay up or you don't see me or the project again".
yep, they're completely different animals.
Trustworthy computing: ensuring reliability and integrity of the user experience
Trusted computing: securing the system against the user.
I thought Trustworthy Computing was a scheme intended to ensure that no part (of the user experience) could fail?
As opposed to Trusted Computing, which I think is what you're actually referring to here, this instead of protecting the system from failure, secured the system against user violations such as overwriting the bootloader with one that isn't signed (like for instance, replacing or enhancing the BIOS with a signed EFI that prevents the user from installing alternative OSes such as OSX onto a commodity x64 or GNU/Linux onto a MS-subsidised laptop (think £250 deal at PC World. How do you think they get so cheap?)), TPM and TXT which can be used in tandem to lock a software license/instance to a specific machine using a specific hardware setup where the hardware has burned-in unique RSA hashes per device (didn't MS do this with Windows at one point where even replacing a wireless card killed the COA key?), Asshole Detectors (I don't know if this term is in common use, it just sounds cool) such as XBox Live, and vendor lock-in on the pretext of securing a closed network (such as the aforementioned XBox Live, any number of persistent online games such as World of Warcraft...)...
If the CD isn't Redbook, and the MP3 doesn't play on my V3, then I don't want them. ...and if it's anything after Zooropa, you can keep it anyway.
uh... that's sample rate, not audio frequency (the ceiling for which in humans is around 20KHz).
my phone won't play DRM'd mp3.
If it doesn't play on my phone, it gets deleted. End of.
Dre never attended college, he tried getting into Northrop Aviation but they wouldn't even take him on as an apprentice because his GPA was so low. Source: http://uk.ask.com/question/wha...
"Dr." is simply a moniker.
citations needed. My information comes from the WINE project, not your arse. WINE is a compatibility layer. A compatibility layer is not an emulator.
WINE is a recursive acronym, it stands for "WINE Is Not an Emulator"...
Bit of a clue, there.
pepper and monosodium glutamate.
Makes even town pigeons taste like chicken!
Dammit, I was going to go with "Popplers" or "Tastecicles".
uh... at my house. I've lived here 14 years and raised four children.
Read the Feldman case again, I think you missed something.
Enigma was issued a US patent in 1928.
#1657411
uh... founded in the US: check. .06% of pre tax earnings (which only works in the American tax system): check.
Headquartered in the US: check.
Trades on the NASDAQ: check.
Pioneered the Double Irish with a Dutch Sandwich tax dodge to reduce its global tax bill to
I think Apple, Inc. owes the United States a bit fucking more than mere allegiance.
no, it didn't. It was there in Magna Carta, it was extended to include everyone in the Liberty of Subject Act of 1354. Loosely contemporised, it reads "No punishment without crime".
actually, there is the Stored Communications Act which protects mobile phone data from incident searches: also refer to the Riley decisions (Riley v. California and United States v. Wurie). THIS DOES NOT prevent searches specific to data known to exist even if it's locked down (Wisconsin v. Feldman). Argument could be (has been in England recently but citations escape me) made that refusal to disclose decryption passcodes to obtain data known or suspected to exist is confirmation of its existence and nature (Guilty until Proven Innocent). Such legal behaviour, I suspect, has also been employed to justify several detentions of indeterminate length at Gitmo.
This. Hardware specific keys are the killer for any forensic attempt. It makes breaking a copied image totally impossible (otherwise what would be the point?). Combine that with a baked bruteforce/tamper killswitch, and you have a secured drive that has just one weakness: the ability of its owner (or not) to resist the charms of law enforcement.
"You do not have to say anything but it may harm your defence if you do not mention when questioned something you might later rely on in court."
What the caution should say, is "...it *WILL* harm your defence..."
You still have the right to silence in England, the new inference is that you are guilty until you prove your innocence (by talking to the police during the interrogation stage).
(also, that by remaining completely silent you're more than likely to be sectioned under the Mental Health Act, the Official Solicitor is called in and your most basic human rights are abrogated including your right to not be experimented on like a lab rat).
anybody can serve a warrant, police are there for when a little persuasion is required.
New iphone announced and greeted with total indifference.
Apple tries to sweeten the deal with claim of new "unbreakable" device encryption.
Something doesn't feel right.
my project, my code until it's paid for. Contract terms agreed by all parties. When the buyer says "I'm not paying you", are you going to leave your fucking toolbox on his forecourt?? Are you actually fucking INSANE??
Core: ancient Dell laptops, which are nice and quiet and run on 70W power supplies. Seven of those, and five dozen hard drives from 120GB all the way up to 2TB apiece either in USB enclosures or in rackmount/grab boxes which are in turn connected via USB IDE adapters. So there's some hotswapping involved but all told I have about 40TB of storage.
right on. Mozilla isn't dead, it's been forked to shit and back.
I've killed projects* half an hour from full deployment because certain parties refused to stump up their end of the contract.
I am NOT building databases because I enjoy the challenge. I don't, in fact databases are the bane of my existence. I would rather deal with the hardware side of things.
*by killed read: walked away with the entire project source on a flash drive in my pocket and all backups obliterated, all orders for hardware cancelled and a note on my workbench saying "Pay up or you don't see me or the project again".
Nexus for the win.