Trusted computing: Difference between revisions
m link FSM/FSF |
m Fix red links |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 24: | Line 24: | ||
==Why it's considered to be a problem== | ==Why it's considered to be a problem== | ||
One problem highlighted by Stallman and others is user ownership and freedom. Depending on the device, various user actions may be restricted and or completely prohibited. Installing and using third party and or alternative software from operating systems to applications may be restricted and or completely impossible. Modifying certain system settings may be restricted and or completely impossible. | One problem highlighted by Stallman and others is [[Right to own|user ownership and freedom]]. Depending on the device, various user actions may be restricted and or completely prohibited. Installing and using third party and or alternative software from operating systems to applications may be restricted and or completely impossible. Modifying certain system settings may be restricted and or completely impossible. | ||
Other highlighted problems relate to privacy and security. Because of hardware and software level backdoor, an affected system could be vulnerable to remote tampering, sabotage and attack, both when the machine is on and off. Data including files and documents can be edited, encrypted and/or deleted without the user's consent nor knowledge. System settings can be edited without the user's consent nor knowledge. | Other highlighted problems relate to privacy and security. Because of hardware and software level backdoor, an affected system could be vulnerable to remote tampering, sabotage and attack, both when the machine is on and off. Data including files and documents can be edited, encrypted and/or deleted without the user's consent nor knowledge. System settings can be edited without the user's consent nor knowledge. | ||
If a login account, such as a [[Microsoft account]] requires credentials stored in the TPM in order to sign in and unlock data encryption keys, then if the computer with the TPM is damaged, the user may not be able to log in to the account, so they can not decrypt the data on their computer. Thus hardware failure that does not affect storage devices directly can result in data loss and loss of any value associated with the account. It is possible to prevent loss by backing up credentials and decryption keys, but Microsoft Windows, for example, does not do reasonable diligence to make sure people use it safely. | If a login account, such as a [[Microsoft account]] requires credentials stored in the [[wikipedia:Trusted_Platform_Module|TPM]] in order to sign in and unlock data encryption keys, then if the computer with the TPM is damaged, the user may not be able to log in to the account, so they can not decrypt the data on their computer. Thus hardware failure that does not affect storage devices directly can result in data loss and loss of any value associated with the account. It is possible to prevent loss by backing up credentials and decryption keys, but [[Microsoft Windows]], for example, does not do reasonable diligence to make sure people use it safely. | ||
==Examples== | ==Examples== | ||
Some notable examples include: | Some notable examples include: | ||
*Windows Vista, Windows 7, Windows 8 and Windows RT (They use a Trusted Platform Module to facilitate BitLocker Drive Encryption)<ref>{{Cite journal |title=A Disk Encryption Algorithm for Windows Vista |url=http://download.microsoft.com/download/0/2/3/0238acaf-d3bf-4a6d-b3d6-0a0be4bbb36e/BitLockerCipher200608.pdf |journal=[[Microsoft | *Windows Vista, Windows 7, Windows 8 and Windows RT (They use a Trusted Platform Module to facilitate BitLocker Drive Encryption)<ref>{{Cite journal |title=A Disk Encryption Algorithm for Windows Vista |url=http://download.microsoft.com/download/0/2/3/0238acaf-d3bf-4a6d-b3d6-0a0be4bbb36e/BitLockerCipher200608.pdf |journal=[[Microsoft]] |archive-url=https://web.archive.org/web/20061007171043/http://download.microsoft.com/download/0/2/3/0238acaf-d3bf-4a6d-b3d6-0a0be4bbb36e/BitLockerCipher200608.pdf |archive-date=7 Oct 2006}}</ref> | ||
*[[ | *[[Signal]] messenger<ref>{{Cite web |title=Scaling secure enclave environments with Signal and Azure confidential computing |url=https://customers.microsoft.com/en-us/story/1374464612401582154-signal-nonprofit-azure-security |url-status=live |archive-url=http://web.archive.org/web/20241111200600/https://customers.microsoft.com/en-us/story/1374464612401582154-signal-nonprofit-azure-security |archive-date=11 Nov 2024}}</ref> | ||
*and the e-prescription service E-Rezept<ref>{{Cite web |title=Confidential Computing soll Patientendaten schützen |url=https://www.healthcare-computing.de/confidential-computing-soll-patientendaten-schuetzen-a-996680/ |archive-url=http://web.archive.org/web/20220926124209/https://www.healthcare-computing.de/confidential-computing-soll-patientendaten-schuetzen-a-996680/ |archive-date=26 Sep 2022}}</ref> | *and the e-prescription service E-Rezept<ref>{{Cite web |title=Confidential Computing soll Patientendaten schützen |url=https://www.healthcare-computing.de/confidential-computing-soll-patientendaten-schuetzen-a-996680/ |archive-url=http://web.archive.org/web/20220926124209/https://www.healthcare-computing.de/confidential-computing-soll-patientendaten-schuetzen-a-996680/ |archive-date=26 Sep 2022}}</ref> | ||
*[[Microsoft Windows 11]] requires TPM 2.0 module and Microsoft account for installation. | *[[Microsoft Windows 11]] requires TPM 2.0 module and Microsoft account for installation. | ||
==See also== | |||
*[[Secure boot]] | |||
==References== | ==References== | ||
{{reflist}} | {{reflist}} | ||
[[Category:Common terms]] | [[Category:Common terms]] | ||