Content deleted Content added
VulcanSphere (talk | contribs) →Platform integrity: Adding screenshot showing the example of TPM 2.0 Platform Configuration Registers (PCR) |
Anastrophe (talk | contribs) m Rollback edit(s) by 2003:C5:F26:1100:1146:5FA1:76A2:45FE (talk): Reverting good faith edits: This has all the earmarks of link/engagement/advert by the company in question.. (UV 0.1.6) |
||
| (31 intermediate revisions by 16 users not shown) | |||
Line 1:
{{Short description|
{{Infobox technology standard
| image = File:Lenovo N20 Chrome - motherboard - Infineon SLB9655TT12-49890.jpg
| caption = An example Trusted Platform Module, the [[Infineon]] SLB9655TT12
| title = Trusted Platform Module
| status = Published
Line 11 ⟶ 13:
| abbreviation = TPM
| ___domain = [[Secure cryptoprocessor]]
| website = {{plain list|
* {{URL|https://www.iso.org/standard/66510.html|ISO/IEC 11889-1:2015}}
* {{URL|https://www.iso.org/standard/66511.html|ISO/IEC 11889-2:2015}}
* {{URL|https://www.iso.org/standard/66512.html|ISO/IEC 11889-3:2015}}
* {{URL|https://www.iso.org/standard/66513.html|ISO/IEC 11889-4:2015}}
}}
}}
A '''Trusted Platform Module''' ('''TPM''') is a [[secure cryptoprocessor]] that implements the '''ISO/IEC 11889''' standard. Common uses are verifying that the [[boot process]] starts from a trusted combination of hardware and software and storing disk encryption keys.
A TPM 2.0 implementation is part of the [[Windows 11]] system requirements.<ref>{{Cite web |last=Warren |first=Tom |date=2021-06-25 |title=Why Windows 11 is forcing everyone to use TPM chips |url=https://www.theverge.com/2021/6/25/22550376/microsoft-windows-11-tpm-chips-requirement-security |access-date=2021-11-13 |publisher=The Verge |language=en |archive-date=2023-12-07 |archive-url=https://web.archive.org/web/20231207200801/https://www.theverge.com/2021/6/25/22550376/microsoft-windows-11-tpm-chips-requirement-security |url-status=live }}</ref>
== History ==
The first TPM version that was deployed was 1.1b in 2003.<ref>{{Citation |last1=Arthur |first1=Will |title=History of the TPM |date=2015 |work=A Practical Guide to TPM 2.0: Using the New Trusted Platform Module in the New Age of Security |pages=1–5 |editor-last=Arthur |editor-first=Will |place=Berkeley, CA |publisher=Apress |language=en |doi=10.1007/978-1-4302-6584-9_1 |isbn=978-1-4302-6584-9 |last2=Challener |first2=David |last3=Goldman |first3=Kenneth |editor2-last=Challener |editor2-first=David |editor3-last=Goldman |editor3-first=Kenneth|doi-access=free }}</ref>
On April 9, 2014, the [[Trusted Computing Group]] announced a major upgrade to their specification entitled ''TPM Library Specification 2.0''.<ref>{{Cite web |date=2014-04-01 |title=Trusted Computing Group Releases TPM 2.0 Specification for Improved Platform and Device Security |url=https://trustedcomputinggroup.org/trusted-computing-group-releases-tpm-2-0-specification-improved-platform-device-security/ |access-date=2021-11-08 |publisher=Trusted Computing Group |language=en-US |archive-date=2025-03-06 |archive-url=https://web.archive.org/web/20250306010354/https://trustedcomputinggroup.org/trusted-computing-group-releases-tpm-2-0-specification-improved-platform-device-security/ |url-status=live }}</ref> The group continues work on the standard incorporating errata, algorithmic additions and new commands, with its most recent edition published as 2.0 in November 2019.<ref name="TPM_Library_Specs">{{cite web |url=https://www.trustedcomputinggroup.org/tpm-library-specification/ |title=TPM Library Specification 2.0 |publisher=Trusted Computing Group |access-date=October 30, 2016 |archive-date=29 October 2016 |archive-url=https://web.archive.org/web/20161029235918/https://www.trustedcomputinggroup.org/tpm-library-specification/ |url-status=live }}</ref> This version became ISO/IEC 11889:2015.
When a new revision is released it is divided into multiple parts by the Trusted Computing Group. Each part consists of a document that makes up the whole of the new TPM specification.
Line 30 ⟶ 37:
* Part 3 Commands
* Part 4 Supporting Routines (added in TPM 2.0)
=== Version differences ===
While TPM 2.0 addresses many of the same use cases and has similar features, the details are different. TPM 2.0 is not backward compatible with TPM 1.2.<ref>{{Citation |title=Trusted Platform Module Library |date=October 30, 2014 |access-date=October 27, 2016 |archive-url=https://web.archive.org/web/20161028083957/https://www.trustedcomputinggroup.org/wp-content/uploads/TPM-Rev-2.0-Part-1-Architecture-01.16.pdf |archive-date=October 28, 2016 |url-status=live |chapter=Part 1: Architecture |chapter-url=https://www.trustedcomputinggroup.org/wp-content/uploads/TPM-Rev-2.0-Part-1-Architecture-01.16.pdf |publisher=Trusted Computing Group}}</ref><ref>{{Cite web |title=TPM 1.2 vs. 2.0 Features {{pipe}} Dell US |url=https://www.dell.com/support/article/en-us/sln312590/tpm-1-2-vs-2-0-features?lang=en}}</ref><ref>{{Cite web |title=TPM 1.2, 2.0 and FTPM (Firmware-based TPM) Information |url=http://aps2.toshiba-tro.de/kb0/TSB8B03XO0000R01.htm |url-status=live |archive-url=https://web.archive.org/web/20200206234241/http://aps2.toshiba-tro.de/kb0/TSB8B03XO0000R01.htm |archive-date=February 6, 2020 |access-date=August 31, 2020}}</ref>
{| class="wikitable"
|-
! Specification
! width="45%" | TPM 1.2
! width="55%" | TPM 2.0
|-
| Architecture
| A complete specification is intended to consist of a platform-specific protection profile which references a common three part TPM 1.2 library.<ref name="TPM_Main_Specs" /> In practice, only a PC Client protection profile was created for TPM 1.2. Protection profiles for [[Personal digital assistant|PDA]] and [[Mobile phone|cellular]] were intended to be defined,<ref name="TPM_Main_Specs" /> but were never published.
| A complete specification consists of a platform-specific specification which references a common four-part TPM 2.0 library.<ref name="TPM2.0Book">{{Cite book |last1=Arthur |first1=Will |title=A Practical Guide to TPM 2.0: Using the New Trusted Platform Module in the New Age of Security |last2=Challener |first2=David |last3=Goldman |first3=Kenneth |date=2015 |publisher=[[Apress]] Media, LLC |isbn=978-1430265832 |___location=[[New York City]] |page=69 |doi=10.1007/978-1-4302-6584-9 |s2cid=27168869}}</ref><ref name="TPM_Library_Specs" /> Platform-specific specifications define what parts of the library are mandatory, optional, or banned for that platform; and detail other requirements for that platform.<ref name="TPM2.0Book" /> Platform-specific specifications include PC Client,<ref>{{cite web |title=PC Client Protection Profile for TPM 2.0 – Trusted Computing Group |url=https://www.trustedcomputinggroup.org/pc-client-protection-profile-tpm-2-0/ |url-status=live |archive-url=https://web.archive.org/web/20161031085440/https://www.trustedcomputinggroup.org/pc-client-protection-profile-tpm-2-0/ |archive-date=October 31, 2016 |access-date=October 30, 2016 |website=trustedcomputinggroup.org}}</ref> mobile,<ref>{{cite web |title=TPM 2.0 Mobile Reference Architecture Specification – Trusted Computing Group |url=https://www.trustedcomputinggroup.org/tpm-2-0-mobile-reference-architecture-specification/ |url-status=live |archive-url=https://web.archive.org/web/20161101103322/https://www.trustedcomputinggroup.org/tpm-2-0-mobile-reference-architecture-specification/ |archive-date=November 1, 2016 |access-date=October 31, 2016 |publisher=trustedcomputinggroup.org}}</ref> and Automotive-Thin.<ref>{{cite web |date=1 March 2015 |title=TCG TPM 2.0 Library Profile for Automotive-Thin |url=https://trustedcomputinggroup.org/tcg-tpm-2-0-library-profile-automotive-thin/ |url-status=live |archive-url=https://web.archive.org/web/20170426062330/https://trustedcomputinggroup.org/tcg-tpm-2-0-library-profile-automotive-thin/ |archive-date=April 26, 2017 |access-date=April 25, 2017 |website=trustedcomputinggroup.org}}</ref>
|-
| Algorithms
| [[SHA-1]] and [[RSA (algorithm)|RSA]] are required.<ref name="TPM1.2Rev116Part2">{{Cite web |title=Archived copy |url=http://trustedcomputinggroup.org/wp-content/uploads/TPM-Main-Part-2-TPM-Structures_v1.2_rev116_01032011.pdf |url-status=live |archive-url=https://web.archive.org/web/20161030140755/http://trustedcomputinggroup.org/wp-content/uploads/TPM-Main-Part-2-TPM-Structures_v1.2_rev116_01032011.pdf |archive-date=October 30, 2016 |access-date=October 29, 2016}}</ref> [[Advanced Encryption Standard|AES]] is optional.<ref name="TPM1.2Rev116Part2" /> [[Triple DES]] was once an optional algorithm in earlier versions of TPM 1.2,<ref>{{Cite web |title=Archived copy |url=http://trustedcomputinggroup.org/wp-content/uploads/mainP2Struct_rev85.pdf |url-status=live |archive-url=https://web.archive.org/web/20161030080258/http://trustedcomputinggroup.org/wp-content/uploads/mainP2Struct_rev85.pdf |archive-date=October 30, 2016 |access-date=October 29, 2016}}</ref> but has been removed from TPM 1.2 version 103.<ref>{{Cite web |date=July 9, 2007 |title=TPM Main Specification Level 2 Version 1.2, Revision 103: Part 1 Design Principles |url=https://trustedcomputinggroup.org/wp-content/uploads/mainP1DPrev103.pdf |access-date=February 16, 2024}}</ref> The MGF1 hash-based mask generation function that is defined in [[PKCS 1|PKCS#1]] is required.<ref name="TPM1.2Rev116Part2" />
| The PC Client Platform TPM Profile (PTP) Specification requires [[SHA-1]] and [[SHA-256]] for hashes; [[RSA (algorithm)|RSA]], [[Elliptic curve cryptography|ECC]] using the [[National Institute of Standards and Technology|NIST]] P-256 curve for [[public-key cryptography]] and asymmetric [[digital signature]] generation and verification; [[HMAC]] for symmetric digital signature generation and verification; 128-bit [[Advanced Encryption Standard|AES]] for [[symmetric-key algorithm]]; and the MGF1 hash-based mask generation function that is defined in [[PKCS 1|PKCS#1]] are required by the TCG PC Client Platform TPM Profile (PTP) Specification.<ref name="PCClient">{{Cite web |date=September 29, 2021 |title=TCG Protection Profile for PC Client Specific TPM 2.0 Library Revision 1.59; Version 1.3 |url=https://trustedcomputinggroup.org/wp-content/uploads/TCG_PCClient_PP_1p3_for_Library_1p59_pub_29sept2021.pdf |access-date=February 16, 2024 |archive-date=March 6, 2025 |archive-url=https://web.archive.org/web/20250306143206/https://trustedcomputinggroup.org/wp-content/uploads/TCG_PCClient_PP_1p3_for_Library_1p59_pub_29sept2021.pdf |url-status=live }}</ref> Many other algorithms are also defined but are optional.<ref>{{Cite web |title=Archived copy |url=https://www.trustedcomputinggroup.org/wp-content/uploads/TCG_Algorithm_Registry_Rev_1.22.pdf |url-status=live |archive-url=https://web.archive.org/web/20161031085411/https://www.trustedcomputinggroup.org/wp-content/uploads/TCG_Algorithm_Registry_Rev_1.22.pdf |archive-date=October 31, 2016 |access-date=October 30, 2016}}</ref> Note that [[Triple DES]] was added into the TPM 2.0 library, but with restrictions to reject [[weak key]]s.<ref>{{Cite web |title=Archived copy |url=https://trustedcomputinggroup.org/wp-content/uploads/TCG-_Algorithm_Registry_Rev_1.27_FinalPublication.pdf |url-status=live |archive-url=https://web.archive.org/web/20190123223556/https://trustedcomputinggroup.org/wp-content/uploads/TCG-_Algorithm_Registry_Rev_1.27_FinalPublication.pdf |archive-date=January 23, 2019 |access-date=January 23, 2019}}</ref> Also, elliptic cryptography [[Direct Anonymous Attestation]] (ECDAA) using Barreto-Naehrig ECC curves which was mandatory in earlier versions has been made optional in the PC Client profile version 1.59.<ref name="PCClient" />
|-
| Crypto Primitives
| A [[Random number generation|random number generator]], a [[Public-key cryptography|public-key cryptographic algorithm]], a [[cryptographic hash function]], a mask generation function, [[digital signature]] generation and verification, and [[Direct Anonymous Attestation]] are required.<ref name="TPM1.2Rev116Part2" /> [[Symmetric-key algorithm]]s and [[exclusive or]] are optional.<ref name="TPM1.2Rev116Part2" /> [[Key generation]] is also required.<ref>{{Cite web |title=Archived copy |url=http://trustedcomputinggroup.org/wp-content/uploads/TPM-Main-Part-1-Design-Principles_v1.2_rev116_01032011.pdf |url-status=live |archive-url=https://web.archive.org/web/20161031085415/http://trustedcomputinggroup.org/wp-content/uploads/TPM-Main-Part-1-Design-Principles_v1.2_rev116_01032011.pdf |archive-date=October 31, 2016 |access-date=October 30, 2016}}</ref>
| A [[Random number generation|random number generator]], [[Public-key cryptography|public-key cryptographic algorithms]], [[cryptographic hash function]]s, [[symmetric-key algorithm]]s, [[digital signature]] generation and verification, mask generation functions, and [[exclusive or]] are required by the TCG PC Client Platform TPM Profile (PTP) Specification.<ref name="PCClient" /> [[Elliptic curve cryptography|ECC]]-based [[Direct Anonymous Attestation]] using the Barreto–Naehrig 256-bit curve is optional for the TCG PC Client Platform TPM Profile (PTP) Specification.<ref name="PCClient" /> The TPM 2.0 common library specification also requires [[key generation]] and [[key derivation function]]s.<ref>{{Cite web |title=Archived copy |url=https://www.trustedcomputinggroup.org/wp-content/uploads/TPM-Rev-2.0-Part-1-Architecture-01.16.pdf |url-status=live |archive-url=https://web.archive.org/web/20161028083957/https://www.trustedcomputinggroup.org/wp-content/uploads/TPM-Rev-2.0-Part-1-Architecture-01.16.pdf |archive-date=October 28, 2016 |access-date=October 27, 2016}}</ref>
|-
| Hierarchy
| One (storage)
| Three (platform, storage and endorsement)
|-
| Root keys
| One (SRK RSA-2048)
| Multiple keys and algorithms per hierarchy
|-
| Authorization
| [[Hash-based message authentication code|HMAC]], PCR, locality, physical presence
| Password, [[Hash-based message authentication code|HMAC]], and policy (which covers HMAC, PCR, locality, and physical presence).
|-
| NVRAM
| Unstructured data
| Unstructured data, counter, bitmap, extend, PIN pass and fail
|}
The TPM 2.0 policy authorization includes the 1.2 HMAC, locality, physical presence, and PCR. It adds authorization based on an asymmetric digital signature, indirection to another authorization secret, counters and time limits, NVRAM values, a particular command or command parameters, and physical presence. It permits the ANDing and ORing of these authorization primitives to construct complex authorization policies.<ref>{{Citation |title=Trusted Platform Module Library; Part 3: Commands |date=March 13, 2014 |url=http://www.trustedcomputinggroup.org/files/static_page_files/C213752B-1A4B-B294-D053D90DF2AB69C5/TPM%20Rev%202.0%20Part%203%20-%20Commands%2001.07-2014-03-13-code.pdf |access-date=September 2, 2014 |archive-url=https://web.archive.org/web/20140903132917/http://www.trustedcomputinggroup.org/files/static_page_files/C213752B-1A4B-B294-D053D90DF2AB69C5/TPM%20Rev%202.0%20Part%203%20-%20Commands%2001.07-2014-03-13-code.pdf |archive-date=September 3, 2014 |url-status=live |section=Section 23: Enhanced Authorization (EA) Commands |publisher=Trusted Computing Group}}</ref>
== Overview ==
[[File:TPM 1.2 diagram.svg|thumb|upright=1.5|Components of a Trusted Platform Module complying with the TPM version 1.2 standard]]
The Trusted Platform Module (TPM) provides:
* A [[hardware random number generator]]<ref>{{cite arXiv | eprint = 1008.2223 | title = Benchmarking the True Random Number Generator of TPM Chips | author1 = Alin Suciu | author2= Tudor Carean| class =cs.CR| year =2010}}</ref><ref>{{Citation | title=TPM Main Specification Level 2|url=https://trustedcomputinggroup.org/wp-content/uploads/TPM-Main-Part-1-Design-Principles_v1.2_rev116_01032011.pdf |volume=Part 1 Design Principles| edition=Version 1.2, Revision 116|access-date=12 September 2017|archive-date=24 February 2021|archive-url=https://web.archive.org/web/20210224215928/https://trustedcomputinggroup.org/wp-content/uploads/TPM-Main-Part-1-Design-Principles_v1.2_rev116_01032011.pdf | url-status=live}}</ref>
* Facilities for the secure generation of [[cryptographic keys]] for limited uses.
* [[Remote attestation]]: Creates a nearly unforgeable [[Cryptographic hash function|hash key]] summary of the hardware and software configuration. One could use the hash to verify that the hardware and software have not been changed. The software in charge of hashing the setup determines the extent of the summary.
* [[Late binding|Binding]]: Data is encrypted using the TPM bind key, a unique [[RSA (algorithm)|RSA]] key descended from a storage key. Computers that incorporate a TPM can create cryptographic keys and encrypt them so that they can only be decrypted by the TPM. This process, often called wrapping or binding a key, can help protect the key from disclosure. Each TPM has a master wrapping key, called the storage root key, which is stored within the TPM itself. User-level RSA key containers are stored with the Windows user profile for a particular user and can be used to encrypt and decrypt information for applications that run under that specific user identity.<ref>{{cite web | url=https://docs.microsoft.com/en-us/previous-versions/aspnet/f5cs0acs(v=vs.100) | title=Understanding Machine-Level and User-Level RSA Key Containers | date=October 22, 2014 | access-date=June 2, 2022 | archive-date=June 2, 2022 | archive-url=https://web.archive.org/web/20220602134828/https://docs.microsoft.com/en-us/previous-versions/aspnet/f5cs0acs(v=vs.100) | url-status=live }}</ref><ref>{{cite web|url=http://linux.die.net/man/3/tspi_data_bind|title=tspi_data_bind(3) – Encrypts data blob|format=Posix manual page|publisher=Trusted Computing Group|access-date=October 27, 2009|archive-date=November 29, 2013|archive-url=https://web.archive.org/web/20131129101856/http://linux.die.net/man/3/tspi_data_bind | url-status=live}}</ref>
* [[Sealed storage]]: Specifies the TPM state<ref>{{Citation | url = https://trustedcomputinggroup.org/wp-content/uploads/TCG_TPM2_r1p59_Part1_Architecture_pub.pdf | title = Trusted Platform Module Library Specification, Family "2.0" | edition = Level 00, Revision 01.59 | volume = Part 1 – Architecture, Section 12, TPM Operational States | publisher = Trusted Computing Group | access-date = January 17, 2021 | archive-date = January 9, 2021 | archive-url = https://web.archive.org/web/20210109164407/https://trustedcomputinggroup.org/wp-content/uploads/TCG_TPM2_r1p59_Part1_Architecture_pub.pdf | url-status = live }}</ref> for the data to be decrypted (unsealed).<ref>{{Citation | url = http://www.trustedcomputinggroup.org/files/static_page_files/72C33D71-1A4B-B294-D02C7DF86630BE7C/TPM%20Main-Part%203%20Commands_v1.2_rev116_01032011.pdf | title = TPM Main Specification Level 2 | edition = Version 1.2, Revision 116 | volume = Part 3 – Commands | publisher = Trusted Computing Group | access-date = June 22, 2011 | archive-date = September 28, 2011 | archive-url = https://web.archive.org/web/20110928031628/http://www.trustedcomputinggroup.org/files/static_page_files/72C33D71-1A4B-B294-D02C7DF86630BE7C/TPM%20Main-Part%203%20Commands_v1.2_rev116_01032011.pdf | url-status = live }}</ref>
* Other [[Trusted Computing]] functions for the data to be decrypted (unsealed).<ref>{{Citation| url = https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-vista/cc749022(v=ws.10)?redirectedfrom=MSDN| title = Microsoft Article on TPM| date = July 25, 2008| access-date = April 1, 2021| archive-date = January 2, 2021| archive-url = https://web.archive.org/web/20210102105127/https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-vista/cc749022(v=ws.10)?redirectedfrom=MSDN| url-status = live}}</ref>
Line 45 ⟶ 93:
=== Platform integrity ===
[[File:TPM 2.0 implementation on Linux screenshot.png|thumb|upright=1.
The primary scope of TPM is to ensure the [[data integrity|integrity]] of a platform during boot time. In this context, "integrity" means "behaves as intended", and a "platform" is any computer device regardless of its [[operating system]]. This is to ensure that the [[boot process]] starts from a trusted combination of hardware and software, and continues until the operating system has fully booted and [[Application software|applications]] are running.
Line 59 ⟶ 107:
[[Full disk encryption]] utilities, such as [[dm-crypt]], can use this technology to protect the keys used to encrypt the computer's storage devices and provide integrity [[authentication]] for a trusted boot pathway that includes firmware and the [[boot sector]].<ref>{{cite web|url=https://www.techsectora.com/2021/02/tpm-header-what-is-it-and-why-is-it-used.html?m=1|title=TPM Encryption | access-date=March 29, 2021|archive-date=June 28, 2021|archive-url=https://web.archive.org/web/20210628045716/https://www.techsectora.com/2021/02/tpm-header-what-is-it-and-why-is-it-used.html?m=1 | url-status=live}}</ref>
== Implementations ==
[[File:TPM Asus.jpg|thumb|right|Trusted Platform Module installed on a mainboard]]
=== Laptops and notebooks ===
In 2006 new [[laptop]]s began being sold with a built-in TPM chip. In the future, this concept could be co-located on an existing [[motherboard]] chip in computers, or any other device where the TPM facilities could be employed, such as a [[cellphone]]. On a PC, either the [[Low Pin Count]] (LPC) bus or the [[Serial Peripheral Interface]] (SPI) bus is used to connect to the TPM chip.
Line 98 ⟶ 114:
The [[Trusted Computing Group]] (TCG) has certified TPM chips manufactured by [[Infineon Technologies]], [[Nuvoton]], and [[STMicroelectronics]],<ref>{{Cite web | url = https://www.trustedcomputinggroup.org/membership/certification/tpm-certified-products/ | title = TPM Certified Products List | publisher = Trusted Computing Group | access-date = October 1, 2016 | archive-date = October 14, 2016 | archive-url = https://web.archive.org/web/20161014153730/http://www.trustedcomputinggroup.org/membership/certification/tpm-certified-products/ | url-status = live }}</ref> having assigned TPM vendor [[Identity document|ID]]s to [[Advanced Micro Devices]], [[Atmel]], [[Broadcom]], [[IBM]], Infineon, [[Intel]], [[Lenovo]], [[National Semiconductor]], Nationz Technologies, Nuvoton, [[Qualcomm]], [[Rockchip]], [[Microchip Technology|Standard Microsystems Corporation]], STMicroelectronics, [[Samsung]], Sinosun, [[Texas Instruments]], and [[Winbond]].<ref>{{Cite web | url = https://www.trustedcomputinggroup.org/wp-content/uploads/Vendor_ID_Registry_0-8_clean.pdf | title = TCG Vendor ID Registry | date = 23 September 2015 | access-date = 27 October 2016 | archive-date = 28 October 2016 | archive-url = https://web.archive.org/web/20161028083456/https://www.trustedcomputinggroup.org/wp-content/uploads/Vendor_ID_Registry_0-8_clean.pdf | url-status = live }}</ref>
=== TPM 2.0
There are five different types of TPM 2.0 implementations (listed in order from most to least secure):<ref name="TPMRecs">{{Cite web |url=https://docs.microsoft.com/en-us/windows/device-security/tpm/tpm-recommendations |title=TPM Recommendations |last1=Lich |first1=Brian |last2=Browers |first2=Nick |date=27 October 2017 |website=Microsoft Docs |publisher=[[Microsoft]] |last3=Hall |first3=Justin |last4=McIlhargey |first4=Bill |last5=Farag |first5=Hany |access-date=10 January 2018 |archive-date=11 January 2018 |archive-url=https://web.archive.org/web/20180111052704/https://docs.microsoft.com/en-us/windows/device-security/tpm/tpm-recommendations |url-status=live }}</ref><ref name="TPMBrief">{{Cite web|url=https://www.trustedcomputinggroup.org/wp-content/uploads/TPM-2.0-A-Brief-Introduction.pdf|title=Trusted Platform Module 2.0: A Brief Introduction |date=October 13, 2016 | publisher=Trusted Computing Group |access-date=March 31, 2018|archive-date=February 3, 2019 | archive-url=https://web.archive.org/web/20190203202259/https://www.trustedcomputinggroup.org/wp-content/uploads/TPM-2.0-A-Brief-Introduction.pdf |url-status=live}}</ref>
*
*
*
*
*
=== Open source
{{Infobox software
| name = TPM 2.0 Reference Implementation
| logo =
| screenshot =
| screenshot size =
| caption =
| developer = [[Microsoft]]
| released =
| latest release version =
| latest release date =
| repo = {{URL|https://github.com/Microsoft/ms-tpm-20-ref}}
| programming language = [[C (programming language)|C]], [[C++]]
| operating system =
| language =
| genre = TPM implementation
| license = [[BSD License]]
| website = {{URL|https://trustedcomputinggroup.org/tpm-library-specification}}
}}The official TCG reference implementation of the TPM 2.0 Specification has been developed by [[Microsoft]]. It is licensed under [[BSD License]] and the [[source code]] is available on [[GitHub]].<ref>{{Cite web |url=https://github.com/Microsoft/ms-tpm-20-ref |title=GitHub - microsoft/ms-tpm-20-ref: Reference implementation of the TCG Trusted Platform Module 2.0 specification. |publisher=GitHub |access-date=April 5, 2020 |archive-date=October 27, 2020 |archive-url=https://web.archive.org/web/20201027190036/https://github.com/microsoft/ms-tpm-20-ref |url-status=live }}</ref>
In 2018 [[Intel]] open-sourced its Trusted Platform Module 2.0 (TPM2) software stack with support for Linux and Microsoft Windows.<ref>{{Cite web |url=https://www.phoronix.com/scan.php?page=news_item&px=Intel-New-Open-Source-TPM2 |title=Intel Open-Sources New TPM2 Software Stack - Phoronix |access-date=April 5, 2020 |archive-date=August 10, 2020 |archive-url=https://web.archive.org/web/20200810025300/https://www.phoronix.com/scan.php?page=news_item&px=Intel-New-Open-Source-TPM2 |url-status=live }}</ref> The source code is hosted on GitHub and licensed under [[BSD License]].<ref>{{Cite web |url=https://github.com/tpm2-software |title=Linux TPM2 & TSS2 Software |website=[[GitHub]] |access-date=April 5, 2020 |archive-date=July 9, 2020 |archive-url=https://web.archive.org/web/20200709134944/https://github.com/tpm2-software |url-status=live }}</ref><ref>{{Cite web |url=https://software.intel.com/en-us/blogs/2018/08/29/tpm2-software-stack-open-source |title=The TPM2 Software Stack: Introducing a Major Open Source Release Intel Software |access-date=April 5, 2020 |archive-date=April 9, 2020 |archive-url=https://web.archive.org/web/20200409075120/https://software.intel.com/en-us/blogs/2018/08/29/tpm2-software-stack-open-source |url-status=live }}</ref>
Line 115 ⟶ 148:
[[IBM]]'s Software TPM 2.0 is an implementation of the TCG TPM 2.0 specification. It is based on the TPM specification Parts 3 and 4 and source code donated by Microsoft. It contains additional files to complete the implementation. The source code is hosted on [[SourceForge]]<ref>{{Cite web |url=https://sourceforge.net/projects/ibmswtpm2/ |title=IBM's Software TPM 2.0 download {{!}} SourceForge.net |access-date=April 5, 2020 |archive-date=June 12, 2019 |archive-url=https://web.archive.org/web/20190612221519/https://sourceforge.net/projects/ibmswtpm2/ |url-status=live }}</ref> and [[GitHub]]<ref>{{Cite web |url=https://github.com/kgoldman/ibmswtpm2/ |title=IBM SW TPM 2.0 |website=[[GitHub]] |access-date=June 2, 2021 |archive-date=September 18, 2020 |archive-url=https://web.archive.org/web/20200918030405/https://github.com/kgoldman/ibmswtpm2 |url-status=live }}</ref> and licensed under BSD License.
In 2022, [[Advanced Micro Devices|AMD]] announced that under certain circumstances their fTPM implementation causes performance problems. A fix is available in form of a [[BIOS]]-Update.<ref>{{Cite web |date=2022-03-08 |title=Intermittent System Stutter Experienced with fTPM Enabled on Windows 10 and 11 |url=https://www.amd.com/en/support/kb/faq/pa-410 |access-date=2022-07-02 |publisher=AMD |archive-date=2024-03-25 |archive-url=https://web.archive.org/web/20240325023648/https://www.amd.com/en/support/kb/faq/pa-410 |url-status=live }}</ref><ref>{{Cite web |author1=Paul Alcorn |date=2022-03-07 |title=AMD Issues Fix and Workaround for Ryzen's fTPM Stuttering Issues |url=https://www.tomshardware.com/news/amd-issues-fix-and-workaround-for-ftpm-stuttering-issues |access-date=2022-07-02 |website=Tom's Hardware |language=en}}</ref>
== Reception ==
The [[Trusted Computing Group]] (TCG) has faced resistance to the deployment of this technology in some areas, where some authors see possible uses not specifically related to [[Trusted Computing]], which may raise privacy concerns. The concerns include the abuse of remote validation of software decides what software is allowed to run and possible ways to follow actions taken by the user being recorded in a database, in a manner that is completely undetectable to the user.<ref>{{cite web | first = Richard Matthew | last = Stallman | url = https://www.gnu.org/philosophy/can-you-trust.html | title = Project GNU | publisher = Free Software Foundation | access-date = 21 July 2016 | archive-date = 29 June 2011 | archive-url = https://web.archive.org/web/20110629082333/http://www.gnu.org/philosophy/can-you-trust.html | url-status = live }}</ref>
The [[TrueCrypt]] disk encryption utility, as well as its derivative [[VeraCrypt]], do not support TPM. The original TrueCrypt developers were of the opinion that the exclusive purpose of the TPM is "to protect against attacks that require the attacker to have administrator privileges, or physical access to the computer". The attacker who has physical or administrative access to a computer can circumvent TPM, e.g., by installing a hardware [[keystroke logger]], by resetting TPM, or by capturing memory contents and retrieving TPM-issued keys. The condemning text goes so far as to claim that TPM is entirely redundant.<ref>{{Cite web |title=TrueCrypt User Guide |url=https://www.grc.com/misc/truecrypt/TrueCrypt%20User%20Guide.pdf |website=truecrypt.org |publisher=TrueCrypt Foundation |via=grc.com |date=7 February 2012 |page=129 |access-date=20 February 2018 |archive-date=25 December 2019 |archive-url=https://web.archive.org/web/20191225153826/https://www.grc.com/misc/truecrypt/TrueCrypt%20User%20Guide.pdf |url-status=live }}</ref> The VeraCrypt publisher has reproduced the original allegation with no changes other than replacing "TrueCrypt" with "VeraCrypt".<ref>{{cite web | url=https://www.veracrypt.fr/en/FAQ.html |
In 2015 [[Richard Stallman]] suggested to replace the term "Trusted computing" with the term "Treacherous computing" due to the danger that the computer can be made to systematically disobey its owner if the cryptographical keys are kept secret from them. He also considers that TPMs available for PCs in 2015 are not currently{{clarify timeframe|date=December 2022}} dangerous and that there is no reason '''not''' to include one in a computer or support it in software due to failed attempts from the industry to use that technology for [[Digital rights management|DRM]], but that the TPM2 released in 2022 is precisely the "[[Trusted Computing|treacherous computing]]" threat he had warned of.<ref>{{Cite web|title=Can You Trust Your Computer? - GNU Project - Free Software Foundation|url=https://www.gnu.org/philosophy/can-you-trust.en.html|access-date=2023-09-06|website=www.gnu.org|archive-date=2025-02-26|archive-url=https://web.archive.org/web/20250226214859/https://www.gnu.org/philosophy/can-you-trust.en.html|url-status=live}}</ref>
In August 2023, [[Linus Torvalds]], who was frustrated with AMD fTPM's stuttering bugs opined, "Let's just disable the stupid fTPM <code>hwrnd</code> thing." He said the CPU-based random number generation, <code>[[RDRAND|rdrand
==
In 2010 [[Christopher Tarnovsky]] presented an attack against TPMs at [[Black Hat Briefings]], where he claimed to be able to extract secrets from a single TPM. He was able to do this after 6 months of work by inserting a probe and spying on an [[Bus (computing)|internal bus]] for the Infineon SLE 66 CL PC.<ref>{{Cite web|url=https://www.networkworld.com/news/2010/020210-black-hat-processor-security.html|title=Black Hat: Researcher claims hack of processor used to secure Xbox 360, other products|date=January 30, 2012|access-date=August 10, 2017|url-status=bot: unknown|archive-url=https://web.archive.org/web/20120130095246/https://www.networkworld.com/news/2010/020210-black-hat-processor-security.html|archive-date=January 30, 2012}}</ref><ref>{{Cite web|url=https://hackaday.com/2010/02/09/tpm-crytography-cracked/|title=TPM crytography cracked|last=Szczys|first=Mike|date=February 9, 2010|website=HACKADAY|archive-url=https://web.archive.org/web/20100212050338/https://hackaday.com/2010/02/09/tpm-crytography-cracked/|archive-date=February 12, 2010}}</ref>
Line 183 ⟶ 178:
Main [[tboot|Trusted Boot (tboot)]] distributions before November 2017 are affected by a dynamic root of trust for measurement (DRTM) attack {{CVE|2017-16837}}, which affects computers running on [[Trusted Execution Technology|Intel's Trusted eXecution Technology (TXT)]] for the boot-up routine.<ref name=Bleeping />
In October 2017, it was reported that a code library developed by [[Infineon Technologies|Infineon]], which had been in widespread use in its TPMs, contained a vulnerability, known as [[ROCA vulnerability|ROCA]], which generated weak [[RSA (cryptosystem)|RSA]] key pairs that allowed private keys to be inferred from [[public key cryptography|public keys]]. As a result, all systems depending upon the privacy of such weak keys are vulnerable to compromise, such as [[identity theft]] or spoofing.<ref name="ars20171016">{{cite web |last1=Goodin |first1=Dan |date=October 16, 2017 |title=Millions of high-security crypto keys crippled by newly discovered flaw |url=https://arstechnica.com/information-technology/2017/10/crypto-failure-cripples-millions-of-high-security-keys-750k-estonian-ids/ |url-status=live |archive-url=https://web.archive.org/web/20181019012939/https://arstechnica.com/information-technology/2017/10/crypto-failure-cripples-millions-of-high-security-keys-750k-estonian-ids/ |archive-date=October 19, 2018 |access-date=October 18, 2017 |publisher=Ars Technica}}</ref> Cryptosystems that store encryption keys directly in the TPM without [[Blinding (cryptography)|blinding]] could be at particular risk to these types of attacks, as passwords and other factors would be meaningless if the attacks can extract encryption secrets.<ref>{{Cite web |title=Can the NSA Break Microsoft's BitLocker? – Schneier on Security |url=https://www.schneier.com/blog/archives/2015/03/can_the_nsa_bre_1.html |url-status=live |archive-url=https://web.archive.org/web/20170810210547/https://www.schneier.com/blog/archives/2015/03/can_the_nsa_bre_1.html |archive-date=August 10, 2017 |access-date=August 10, 2017 |website=www.schneier.com}}</ref> Infineon has released firmware updates for its TPMs to manufacturers who have used them.<ref>{{Cite web |title="TPM Update - Infineon Technologies" |url=https://www.infineon.com/cms/en/product/promopages/tpm-update/ |url-status=live |archive-url=https://web.archive.org/web/20210205072055/https://www.infineon.com/cms/en/product/promopages/tpm-update/ |archive-date=February 5, 2021 |access-date=March 19, 2021}}</ref>
In 2018, a design flaw in the TPM 2.0 specification for the static root of trust for measurement (SRTM) was reported ({{CVE|2018-6622}}). It allows an adversary to reset and forge platform configuration registers which are designed to securely hold measurements of software that are used for bootstrapping a computer.<ref name=USENIX27>{{cite conference|url=https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-han.pdf|title=A Bad Dream: Subverting Trusted Platform Module While You Are Sleeping| last1=Seunghun| first1=Han| last2=Wook| first2=Shin | last3=Jun-Hyeok | first3=Park | last4=HyoungChun | first4=Kim|date=August 15–17, 2018 | publisher=USENIX Association | ___location=Baltimore, MD, USA|conference=27th USENIX Security Symposium | isbn=9781939133045 | archive-url=https://web.archive.org/web/20180820032203/https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-han.pdf | archive-date=20 August 2018 | url-status=live}}</ref> Fixing it requires hardware-specific firmware patches.<ref name=USENIX27 /> An attacker abuses power interrupts and TPM state restores to trick TPM into thinking that it is running on non-tampered components.<ref name=Bleeping>{{cite web | url=https://www.bleepingcomputer.com/news/security/researchers-detail-two-new-attacks-on-tpm-chips/ | title=Researchers Detail Two New Attacks on TPM Chips | first=Catalin | last=Cimpanu| publisher=Bleeping Computer | date=August 29, 2018|access-date=28 September 2019 | archive-url=https://web.archive.org/web/20181007062452/https://www.bleepingcomputer.com/news/security/researchers-detail-two-new-attacks-on-tpm-chips/|archive-date=7 October 2018|url-status=live}}</ref>
In 2021, the Dolos Group showed an attack on a discrete TPM, where the TPM chip itself had some tamper resistance, but the other endpoints of its communication bus did not. They read a full-disk-encryption key as it was transmitted across the motherboard, and used it to decrypt the laptop's SSD.<ref>{{cite web |url=https://arstechnica.com/gadgets/2021/08/how-to-go-from-stolen-pc-to-network-intrusion-in-30-minutes/ |title=Trusted platform module security defeated in 30 minutes, no soldering required |date=August 3, 2021}}</ref>
== Availability ==
Currently, a TPM is provided by nearly all PC and notebook manufacturers in their products.
Vendors include:
* [[Infineon]] provides both TPM chips and TPM software, which are delivered as [[Original equipment manufacturer|OEM]] versions with new computers as well as separately by Infineon for products with TPM technology which comply with TCG standards. For example, Infineon licensed TPM management software to Broadcom Corp. in 2004.<ref>{{cite web|url=https://www.heise.de/newsticker/meldung/Trusted-Platform-Module-TPM-im-LAN-Adapter-143777.html|title=Trusted Platform Module (TPM) im LAN-Adapter|date=March 12, 2005 |publisher=Heise Online|access-date=January 7, 2019|archive-date=January 7, 2019|archive-url=https://web.archive.org/web/20190107232935/https://www.heise.de/newsticker/meldung/Trusted-Platform-Module-TPM-im-LAN-Adapter-143777.html|url-status=live}}</ref>
* [[Microchip Technology|Microchip]] (formerly Atmel) manufactured TPM devices that it claims to be compliant to the Trusted Platform Module specification version 1.2 revision 116 and offered with several interfaces (LPC, SPI, and
* [[Nuvoton]] Technology Corporation provides TPM devices for PC applications. Nuvoton also provides TPM devices for embedded systems and Internet of Things (IoT) applications via
* [[STMicroelectronics]] has provided TPMs for PC platforms and embedded systems since 2005. The product offering
There are also hybrid types; for example, TPM can be integrated into an [[Ethernet]] controller, thus eliminating the need for a separate motherboard component.<ref>{{cite web | url = https://www.trustedcomputinggroup.org/files/temp/4B551C9F-1D09-3519-AD45C1F0B5D61714/TPM%20Overview.pdf | title = Replacing Vulnerable Software with Secure Hardware: The Trusted Platform Module (TPM) and How to Use It in the Enterprise | year = 2008 | access-date = June 7, 2014 | publisher = Trusted computing group | archive-date = July 14, 2014 | archive-url = https://web.archive.org/web/20140714233816/https://www.trustedcomputinggroup.org/files/temp/4B551C9F-1D09-3519-AD45C1F0B5D61714/TPM%20Overview.pdf | url-status = live }}</ref><ref>{{cite web | url = http://www.broadcom.com/products/Ethernet-Controllers-and-Adapters/Enterprise-Client-Controllers/BCM5752 | title = NetXtreme Gigabit Ethernet Controller with Integrated TPM1.2 for Desktops | date = May 6, 2009 | access-date = June 7, 2014 | publisher = Broadcom | archive-date = June 14, 2014 | archive-url = https://web.archive.org/web/20140614134124/http://www.broadcom.com/products/Ethernet-Controllers-and-Adapters/Enterprise-Client-Controllers/BCM5752 | url-status = live }}</ref>
Line 216 ⟶ 203:
Since July 28, 2016, all new Microsoft device models, lines, or series (or updating the hardware configuration of an existing model, line, or series with a major update, such as CPU, graphic cards) implement, and enable by default TPM 2.0.
While TPM 1.2 parts are discrete silicon components, which are typically soldered on the motherboard, TPM 2.0 is available as a discrete (dTPM) silicon component in a single semiconductor package, an integrated component incorporated in one or more semiconductor packages - alongside other logic units in the same package(s), and as a firmware (fTPM) based component running in a trusted execution environment (TEE) on a general purpose System-on-a-chip (SoC).<ref>{{cite web | url=https://www.thewindowsclub.com/tpm-vs-ptt-differences | title=TPM vs PTT: What are the main differences between these technologies? | date=August 9, 2021 | access-date=June 2, 2022 | archive-date=February 12, 2025 | archive-url=https://web.archive.org/web/20250212042620/https://www.thewindowsclub.com/tpm-vs-ptt-differences | url-status=live }}</ref>
=== Virtual TPM ===
* [[Google Compute Engine]]
* The libtpms library provides software emulation of a Trusted Platform Module (TPM 1.2 and TPM 2.0). It targets the integration of TPM functionality into hypervisors, primarily into Qemu.<ref>{{cite web
=== Operating systems ===
* [[Windows 11]] requires TPM 2.0 support as a minimum system requirement.<ref>{{Cite web|last=Microsoft|title=Windows 11 Specs and System Requirements {{!}} Microsoft|url=https://www.microsoft.com/en-us/windows/windows-11-specifications|access-date=2021-10-02|website=Windows|language=en-us|archive-date=2022-05-31|archive-url=https://web.archive.org/web/20220531013104/https://www.microsoft.com/en-us/windows/windows-11-specifications|url-status=live}}</ref><ref>{{cite conference | last = Chabaud | first = Florent | title = Setting Hardware Root-of-Trust from Edge to Cloud, and How to Use it | book-title = Proceedings of the 29th Computer & Electronics Security Application Rendezvous | pages = 115–130 | publisher = C&ESAR 2022 | ___location = Rennes, France | date = November 15–16, 2022 | editor1-last = le Guernic | editor1-first = Gurvan | url = https://ceur-ws.org/Vol-3329/paper-07.pdf | access-date = 2024-01-08 | archive-date = 2025-03-06 | archive-url = https://web.archive.org/web/20250306105606/https://ceur-ws.org/Vol-3329/paper-07.pdf | url-status = live }} Location: Université de Rennes 1, Campus de Beaulieu, IRISA/Inria Rennes, 263 avenue du Général Leclerc, 35042 RENNES cedex.</ref> On many systems TPM is disabled by default which requires changing settings in the computer's UEFI to enable it.<ref>{{Cite web|date=2021-06-24|title=Windows 11 update: TPM 2.0 and PC Health Check confusion|url=https://www.slashgear.com/windows-11-tpm-2-0-update-system-requirement-confusion-24679866/|url-status=live|archive-url=https://web.archive.org/web/20210624203318/https://www.slashgear.com/windows-11-tpm-2-0-update-system-requirement-confusion-24679866/|archive-date=June 24, 2021|access-date=2021-06-24|website=SlashGear|language=en-US}}</ref>
* [[Windows 8]] and later have native support for TPM 2.0.
* [[Windows 7]] can install an official patch to add TPM 2.0 support.<ref>{{Cite web |url=https://support.microsoft.com/en-us/topic/update-to-add-support-for-tpm-2-0-in-windows-7-and-windows-server-2008-r2-8ef7d943-995e-ee23-0c54-06600e368e1c |title=Update to add support for TPM 2.0 in Windows 7 and Windows Server 2008 R2 - Microsoft Support |access-date=2024-01-04 |archive-date=2025-02-12 |archive-url=https://web.archive.org/web/20250212025821/https://support.microsoft.com/en-us/topic/update-to-add-support-for-tpm-2-0-in-windows-7-and-windows-server-2008-r2-8ef7d943-995e-ee23-0c54-06600e368e1c |url-status=live }}</ref>
* [[Windows Vista]] through [[Windows 10]] have native support for TPM 1.2.
* The Trusted Platform Module 2.0 (TPM 2.0) has been supported by the [[Linux kernel]] since version
=== Platforms ===
Line 235 ⟶ 222:
* [[Google]] includes TPMs in [[Chromebook]]s as part of their security model.<ref>{{cite web |url = https://chrome.googleblog.com/2011/07/chromebook-security-browsing-more.html |title = Chromebook security: browsing more securely |work = Chrome Blog |access-date = April 7, 2013 |archive-date = April 25, 2016 |archive-url = https://web.archive.org/web/20160425070152/https://chrome.googleblog.com/2011/07/chromebook-security-browsing-more.html |url-status = live }}</ref>
* [[Oracle Corporation|Oracle]] ships TPMs in their X- and T-Series Systems such as T3 or T4 series of servers.<ref>{{cite web | url= http://www.oracle.com/us/products/servers-storage/solaris/solaris-and-sparc-t4-497273.pdf | title= Oracle Solaris and Oracle SPARC T4 Servers— Engineered Together for Enterprise Cloud Deployments | publisher= Oracle | access-date= October 12, 2012 | archive-date= October 24, 2012 | archive-url= https://web.archive.org/web/20121024150758/http://www.oracle.com/us/products/servers-storage/solaris/solaris-and-sparc-t4-497273.pdf | url-status= live }}</ref> Support is included in [[Solaris (operating system)|Solaris 11]].<ref>{{cite web |url=http://docs.oracle.com/cd/E23824_01/html/821-1462/tpmadm-1m.html |title=tpmadm |type=manpage |publisher=Oracle |access-date=October 12, 2012 |archive-date=November 14, 2012 |archive-url=https://web.archive.org/web/20121114112129/http://docs.oracle.com/cd/E23824_01/html/821-1462/tpmadm-1m.html |url-status=live }}</ref>
* In 2006, with the introduction of first Macintosh models with Intel processors, Apple started to ship Macs with TPM. Apple never provided an official driver, but there was a port under [[GNU General Public License|GPL]] available.<ref>{{Citation | first = Amit | last = Singh | chapter-url = http://www.osxbook.com/book/bonus/chapter10/tpm/ | title = OS X book | chapter = Trusted Computing for Mac OS X | access-date = August 2, 2011 | archive-date = July 21, 2011 | archive-url = https://web.archive.org/web/20110721080011/http://www.osxbook.com/book/bonus/chapter10/tpm/ | url-status = live }}.</ref> Apple has not shipped a computer with TPM since 2006.<ref>{{cite web | url = http://www.pcworld.com/article/157966/laptop_security.html | title = Your Laptop Data Is Not Safe. So Fix It | date = January 20, 2009 | work = PC World | access-date = August 22, 2013 | archive-date = November 4, 2013 | archive-url = https://web.archive.org/web/20131104211218/http://www.pcworld.com/article/157966/laptop_security.html | url-status = live }}</ref> Starting in 2016, Apple products began adopting Apple's own trusted hardware component called "Secure Enclave", originally as a separate chip and later as an integrated part of Apple silicon CPUs. Apple Secure Enclave is not TPM-compatible.<ref>{{cite web |title=A brief history of Mac enclaves and exclaves |url=https://eclecticlight.co/2024/06/15/a-brief-history-of-mac-enclaves-and-exclaves/#:~:text=Intel%20Macs&text=A%20year%20later%2C%20in%20December,contemporaneous%20iPads%20and%20iPod%20Touch. |website=The Eclectic Light Company |access-date=1 February 2025}}</ref>
* In 2011, Taiwanese manufacturer [[Micro-Star International|MSI]] launched its Windpad 110W tablet featuring an [[Advanced Micro Devices|AMD]] CPU and Infineon Security Platform TPM, which ships with controlling software version 3.7. The chip is disabled by default but can be enabled with the included, pre-installed software.<ref>{{cite web|url=http://www.msi.com/product/windpad/WindPad-110W.html|work=Winpad 110W|title=TPM. Complete protection for peace of mind|publisher=MSI|access-date=May 20, 2013|archive-date=May 13, 2013|archive-url=https://web.archive.org/web/20130513043710/http://www.msi.com/product/windpad/WindPad-110W.html|url-status=live}}</ref>
Line 247 ⟶ 234:
=== Software ===
* [[Microsoft]] operating systems [[Windows Vista]] and later use the chip in conjunction with the included disk encryption component named [[BitLocker]]. Microsoft had announced that from January 1, 2015, all computers will have to be equipped with a TPM 2.0 module in order to pass [[Windows 8.1]] [[hardware certification]].<ref>{{cite web| url = http://msdn.microsoft.com/en-us/library/windows/hardware/hh748188.aspx| title = Windows Hardware Certification Requirements| publisher = Microsoft| access-date = July 23, 2013| archive-date = June 29, 2021| archive-url = https://web.archive.org/web/20210629081025/https://docs.microsoft.com/en-us/previous-versions/windows/hardware/cert-program/?redirectedfrom=MSDN| url-status = live}}</ref> However, in a December 2014 review of the Windows Certification Program this was instead made an optional requirement. However, TPM 2.0 is required for [[InstantGo|connected standby]] systems.<ref>{{cite web |url = https://msdn.microsoft.com/en-us/library/windows/hardware/jj128256 |title = Windows Hardware Certification Requirements for Client and Server Systems |publisher = Microsoft |access-date = June 5, 2015 |archive-date = July 1, 2015 |archive-url = https://web.archive.org/web/20150701150150/https://msdn.microsoft.com/en-US/library/windows/hardware/jj128256 |url-status = live }}</ref> Virtual machines running on Hyper-V can have their own virtual TPM module starting with Windows 10 1511 and Windows Server 2016.<ref>{{cite web|url=https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/what-s-new-in-hyper-v-on-windows|title=What's new in Hyper-V on Windows Server 2016|publisher=Microsoft|access-date=March 24, 2017|archive-date=March 25, 2017|archive-url=https://web.archive.org/web/20170325113136/https://technet.microsoft.com/en-us/windows-server-docs/compute/hyper-v/what-s-new-in-hyper-v-on-windows|url-status=live}}</ref> Microsoft Windows includes two TPM related [[command (computing)|commands]]: {{Mono|tpmtool}}, a utility that can be used to retrieve information about the TPM, and {{Mono|tpmvscmgr}}, a [[command-line interface|command-line]] tool that allows creating and deleting TPM virtual [[smart card]]s on a computer.<ref>
== Endorsement keys ==
Line 255 ⟶ 242:
These manufacturers typically provide their [[Certificate Authority|certificate authority]] root (and sometimes intermediate) certificates on their web sites.
* [[AMD]]<ref>{{citation | title=AMD EK RSA Root Certificate | url=https://ftpm.amd.com/pki/aia/264D39A23CEB5D5B49D610044EEBD121 | access-date=2021-07-23 | archive-date=2021-07-23 | archive-url=https://web.archive.org/web/20210723184749/https://ftpm.amd.com/pki/aia/264D39A23CEB5D5B49D610044EEBD121 | url-status=live }}</ref><ref>{{citation | title=AMD EK ECC Root Certificate | url=https://ftpm.amd.com/pki/aia/23452201D41C5AB064032BD23F158FEF | access-date=2021-07-23 | archive-date=2021-07-23 | archive-url=https://web.archive.org/web/20210723184748/https://ftpm.amd.com/pki/aia/23452201D41C5AB064032BD23F158FEF | url-status=live }}</ref><ref>{{citation | title=AMD EK Ryzen 6000 RSA Intermediate Certificate | url=https://ftpm.amd.com/pki/aia/51ADE34A2F8253525E2321AD63F7B197 | access-date=2021-07-23 | archive-date=2021-07-23 | archive-url=https://web.archive.org/web/20210723184748/https://ftpm.amd.com/pki/aia/51ADE34A2F8253525E2321AD63F7B197 | url-status=live }}</ref><ref>{{citation | title=AMD EK Ryzen 6000 ECC Intermediate Certificate | url=https://ftpm.amd.com/pki/aia/D30EE6F7557055BA66AD1A1DD1157D2C | access-date=2021-07-23 | archive-date=2021-07-23 | archive-url=https://web.archive.org/web/20210723184748/https://ftpm.amd.com/pki/aia/D30EE6F7557055BA66AD1A1DD1157D2C | url-status=live }}</ref>
* [[Infineon]]<ref>{{citation| title=Infineon Root Certificate | url=https://www.infineon.com/cms/en/product/promopages/optiga_tpm_certificates/}}</ref>
* [[Intel]]<ref>{{citation| title=Intel EK Root Certificate | url=https://upgrades.intel.com/content/CRL/ekcert/EKRootPublicKey.cer}}</ref><ref>{{citation | title=Intel EK Intermediate Certificate | url=https://upgrades.intel.com/content/CRL/ekcert/SPTHEPIDPROD_EK_Platform_Public_Key.cer | access-date=2021-07-23 | archive-date=2021-07-23 | archive-url=https://web.archive.org/web/20210723150732/https://upgrades.intel.com/content/CRL/ekcert/SPTHEPIDPROD_EK_Platform_Public_Key.cer | url-status=live }}</ref>
* NationZ<ref>{{citation | title = NationZ EK Root Certificate | url = https://pki.nationz.com.cn/EkRootCA/EkRootCA.crt | access-date = 2021-07-23 | archive-date = 2021-07-23 | archive-url = https://web.archive.org/web/20210723150732/https://pki.nationz.com.cn/EkRootCA/EkRootCA.crt | url-status = live }}</ref><ref>{{citation| title = NationZ EK Intermediate Certificate | url=https://pki.nationz.com.cn/EkMfrCA001/EkMfrCA001.crt}}</ref><ref>{{citation| title = NationZ EK Intermediate Certificate | url=https://pki.nationz.com.cn/EkMfrCA002/EkMfrCA002.crt}}</ref><ref>{{citation | title = NationZ EK Intermediate Certificate | url = https://pki.nationz.com.cn/EkMfrCA003/EkMfrCA003.crt | access-date = 2021-07-23 | archive-date = 2021-07-23 | archive-url = https://web.archive.org/web/20210723150736/https://pki.nationz.com.cn/EkMfrCA003/EkMfrCA003.crt | url-status = live }}</ref>
* [[Nuvoton]]<ref>{{citation| title = Nuvoton EK Root Certificate 1110 | url=https://www.nuvoton.com/security/NTC-TPM-EK-Cert/Nuvoton%20TPM%20Root%20CA%201110.cer}}</ref><ref>{{citation | title = Nuvoton EK Root Certificate 1111 | url = https://www.nuvoton.com/security/NTC-TPM-EK-Cert/Nuvoton%20TPM%20Root%20CA%201111.cer | access-date = 2021-07-26 | archive-date = 2021-07-26 | archive-url = https://web.archive.org/web/20210726215035/https://www.nuvoton.com/security/NTC-TPM-EK-Cert/Nuvoton%20TPM%20Root%20CA%201111.cer | url-status = live }}</ref><ref>{{citation| title = Nuvoton EK Root Certificate 2110 | url=https://www.nuvoton.com/security/NTC-TPM-EK-Cert/Nuvoton%20TPM%20Root%20CA%202110.cer}}</ref><ref>{{citation| title = Nuvoton EK Root Certificate 2111 | url=https://www.nuvoton.com/security/NTC-TPM-EK-Cert/Nuvoton%20TPM%20Root%20CA%202111.cer}}</ref><ref>{{citation| title = Nuvoton EK Root Certificate 2112 | url=https://www.nuvoton.com/security/NTC-TPM-EK-Cert/Nuvoton%20TPM%20Root%20CA%202112.cer}}</ref>
* [[STMicroelectronics|ST Micro]]<ref>{{citation | title = ST Micro EK GlobalSign Certificate | url = https://secure.globalsign.com/cacert/gstpmroot.crt | access-date = 2021-07-23 | archive-date = 2021-07-23 | archive-url = https://web.archive.org/web/20210723150736/https://secure.globalsign.com/cacert/gstpmroot.crt | url-status = live }}</ref><ref>{{citation | title = ST Micro EK Root Certificate | url = https://secure.globalsign.com/cacert/stmtpmekroot.crt | access-date = 2021-07-23 | archive-date = 2021-07-23 | archive-url = https://web.archive.org/web/20210723150731/https://secure.globalsign.com/cacert/stmtpmekroot.crt | url-status = live }}</ref><ref>{{citation| title = ST Micro EK Intermediate Certificate | url=https://secure.globalsign.com/cacert/stmtpmekint01.crt}}</ref><ref>{{citation | title = ST Micro EK Intermediate Certificate | url = https://secure.globalsign.com/cacert/stmtpmekint02.crt | access-date = 2021-07-23 | archive-date = 2021-07-23 | archive-url = https://web.archive.org/web/20210723150734/https://secure.globalsign.com/cacert/stmtpmekint02.crt | url-status = live }}</ref><ref>{{citation| title = ST Micro EK Intermediate Certificate | url=https://secure.globalsign.com/cacert/stmtpmekint03.crt}}</ref><ref>{{citation| title = ST Micro EK Intermediate Certificate | url=https://secure.globalsign.com/cacert/stmtpmekint04.crt}}</ref><ref>{{citation | title = ST Micro EK Intermediate Certificate | url = https://secure.globalsign.com/cacert/stmtpmekint05.crt | access-date = 2021-07-23 | archive-date = 2021-07-23 | archive-url = https://web.archive.org/web/20210723150735/https://secure.globalsign.com/cacert/stmtpmekint05.crt | url-status = live }}</ref><ref>{{citation| title = ST Micro EK GlobalSign ECC Certificate | url=https://secure.globalsign.com/cacert/tpmeccroot.crt}}</ref><ref>{{citation| title = ST Micro EK ECC Root Certificate | url=https://secure.globalsign.com/stmtpmeccroot01.crt}}</ref><ref>{{citation| title = ST Micro EK ECC Intermediate Certificate | url=https://secure.globalsign.com/stmtpmeccint01.crt}}</ref>
==
To utilize a TPM, the user needs a software library that communicates with the TPM and provides a friendlier API than the raw TPM communication. Currently, there are several such open-source TPM 2.0 libraries. Some of them also support TPM 1.2, but mostly TPM 1.2 chips are now deprecated and modern development is focused on TPM 2.0.
Typically, a TPM library provides an API with one-to-one mappings to TPM commands. The TCG specification calls this layer the System API (SAPI). This way, the user has more control over the TPM operations,
There is currently only one stack that follows the TCG specification. All the other available open-source TPM libraries use their own form of richer API.
Line 286 ⟶ 273:
|{{Yes}}
|{{Yes}}
|Maybe{{efn|There is an application note{{r|r={{Cite web|last=AG|first=Infineon Technologies|title=
|-
|ibmtss<ref>{{Cite web|title=IBM TSS for TPM 2.0|url=https://sourceforge.net/projects/ibmtpm20tss|access-date=June 2, 2021|archive-date=June 29, 2021|archive-url=https://web.archive.org/web/20210629081044/https://sourceforge.net/projects/ibmtpm20tss/|url-status=live}}</ref><ref>{{Cite web|title = IBM TSS for TPM 2.0|website = [[GitHub]]|url = https://github.com/kgoldman/ibmtss|access-date = June 2, 2021|archive-date = June 29, 2021|archive-url = https://web.archive.org/web/20210629081026/https://github.com/kgoldman/ibmtss|url-status = live}}</ref>
Line 326 ⟶ 313:
{{noteslist}}
These TPM libraries are sometimes also called TPM stacks, because they provide the interface for the developer or user to interact with the TPM. As seen from the table, the TPM stacks abstract the operating system and transport layer, so the user could migrate one application between platforms. For example, by using TPM stack API the user would interact the same way with a TPM, regardless if the physical chip is connected over SPI,
== See also ==
| |||