Trusted Computing: Difference between revisions
Fixed tone and improved the quality of writing. (Will soon edit this page again to fix the remaining half and the references) |
→Why it's considered to be a problem: tone edits |
||
| (One intermediate revision by one other user not shown) | |||
| Line 8: | Line 8: | ||
The workings of Trusted Computing are based on six key principles, these being : | The workings of Trusted Computing are based on six key principles, these being : | ||
# Sealed storage | #Sealed storage | ||
# Memory curtaining / protected execution | #Memory curtaining / protected execution | ||
# Secure input and output | #Secure input and output | ||
# Endorsement key | #Endorsement key | ||
# Remote attestation | #Remote attestation | ||
# Trusted Third Party (TTP) | #Trusted Third Party (TTP) | ||
Sealed storage consists in the protection of information trough binding it to the configuration of the platform being used. Trough this one may for example lock certain files from being opened if they lack the needed license. | Sealed storage consists in the protection of information trough binding it to the configuration of the platform being used. Trough this one may for example lock certain files from being opened if they lack the needed license. | ||
| Line 24: | Line 24: | ||
==Why it's considered to be a problem== | ==Why it's considered to be a problem== | ||
One problem 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 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. | |||
==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 Corp.]]}}</ref> | |||
*[[Signal data collection|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}}</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/}}</ref> | |||
==References== | ==References== | ||