Content deleted Content added
Zeroandones (talk | contribs) mNo edit summary |
turned ext links to refs |
||
Line 29:
==Criticism==
{{more2|Trusted Computing#Criticism}}
The group has faced widescale opposition from the [[free software]] community on the grounds that the technology they are developing has a negative impact on the users' privacy and can create customer [[vendor lock-in|lock-in]], especially if it is used to create [[Digital rights management|DRM]] applications. It has received criticism from the [[GNU|GNU/Linux]] and [[FreeBSD]] communities, as well as the software development community in general. Significant backlash amongst the Trusted Computing Group was present during [[Richard Stallman]]'s speech at the [[Hackers on Planet Earth]] conference in July 2006, in New York. Richard Stallman and the [[Free Software Foundation]] have also criticized the group publicly in other speeches. The criticism calls Trusted Computing "Treacherous Computing" instead and warns that vendors can lock out software that is not officially signed by specific vendors, rendering it unusable.<ref>[http://www.gnu.org/philosophy/can-you-trust.html "Can you trust your computer?"] by [[Richard Stallman]], from the [[GNU Project]] website</ref>▼
▲The group has faced widescale opposition from the [[free software]] community on the grounds that the technology they are developing has a negative impact on the users' privacy and can create customer [[vendor lock-in|lock-in]], especially if it is used to create [[Digital rights management|DRM]] applications. It has received criticism from the [[GNU|GNU/Linux]] and [[FreeBSD]] communities, as well as the software development community in general. Significant backlash amongst the Trusted Computing Group was present during [[Richard Stallman]]'s speech at the [[Hackers on Planet Earth]] conference in July 2006, in New York. Richard Stallman and the [[Free Software Foundation]] have also criticized the group publicly in other speeches. The criticism calls Trusted Computing "Treacherous Computing" instead and warns that vendors can lock out software that is not officially signed by specific vendors, rendering it unusable.
Privacy concerns with the TCG revolve around the fact that each TPM has a unique keypair, called the "endorsement key", that identifies the platform. In initial versions of the TPM (version 1.1), the TCG addressed privacy concerns by suggesting the use of a "Privacy CA" that could certify [[pseudonymity|pseudonymous]] machine credentials. By having separate credentials for interacting with different parties, actions could not be linked, and so some level of privacy is provided. However, this requires trust in the Privacy CA, who could still link pseudonyms to the common, identifying machine credential. Since this left unresolved privacy concerns, version 1.2 of the TPM specification introduced "[[Direct anonymous attestation]]": a protocol based on the idea of a [[zero-knowledge proof]] which allows a TPM user to receive a certification in such a way that the Privacy CA would not be able to link requests to a single user or platform, while still being able to identify rogue TPMs.
Privacy concerns for TPM were
==[[ISO]] Standardization efforts ==
Line 205 ⟶ 204:
==External links==
* [http://www.trustedcomputinggroup.org/ TCG website], with a [http://www.trustedcomputinggroup.org/blog blog]
* [http://www.gnu.org/philosophy/can-you-trust.html "Can you trust your computer?"] by [[Richard Stallman]], from the [[GNU Project]] website
* [http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html Trusted Computing FAQ] by [[Ross J. Anderson (professor)|Ross Anderson]]
[[Category:Trusted computing]]
|