Protocol Simulations / TPM 2.0 PQC Playground
What you will do: Send raw TPM 2.0 commands from the Command Builder — TPM2_GetCapability, TPM2_CreatePrimary, TPM2_Encapsulate, TPM2_SignDigest — with ML-KEM or ML-DSA, then run Quote or Certify on the Attestation tab.
Worked example: On Attestation keep the ML-DSA-65 key, PCRs sha256:0,1,2,3,7 and the default nonce, press Run Quote: the result shows the 3309-byte signature, OpenSSL WASM verify says Signature Verified Successfully, plus a JSON bundle.
Runtime and privacy: The cryptographic exercise runs in this browser. Review the site privacy terms before entering sensitive material; use synthetic inputs for learning and evaluation.
Browse all Crypto Lab tools · Learn with Secure Boot & Firmware PQC
For your role
- Developer / Engineer
- Run the eight tracks from Boot & discover to An honest TPM in the Learn tab, then use the Command Builder to send raw commands such as TPM2_GetCapability to the WebAssembly TPM: the Execution Log shows tags, return codes and the ML-KEM and ML-DSA primitives.
- Security Architect
- Track T3, Key establishment — transport vs encapsulation, and T6, Factory identity, show where a TPM's trust model changes under PQC; the V2.7 EKs and EK Certs tabs read the post-quantum endorsement key templates and certificates.
- Researcher / Academic
- Run the V1.85 Compliance Suite from the Command Builder and the ML-DSA Attestation tab's Quote / Certify with in-browser verify: track T8 shows how to detect fake crypto and spec drift yourself.
TPM 2.0 PQC Playground
Execute raw TPM 2.0 commands directly within the browser using the WebAssembly-compiledpqctpm emulator. Explore ML-KEM and ML-DSA using an engine derived from the earlier TCG V1.85 RC4 snapshot. The current normative reference is the final TCG TPM 2.0 Library Version 185 (March 2026). Commands run against this local software emulator, not a physical TPM; the displayed results do not demonstrate hardware-backed key protection or device attestation.
Boot & discover — one software TPM, two cryptographic eras
The browser started a local software TPM emulator when this page loaded. These steps send actual TPM wire commands to that emulator: self-test, read its algorithm table, then make an invalid request to observe a specified refusal. This exercises the protocol and software engine; it does not probe a physical TPM.
TCG V1.85 (published March 2026) did not replace the TPM command set — it EXTENDED it. Everything classical still works; the PQC algorithms and commands were added alongside. GetCapability is the migration story in one response.
Waiting for the WASM TPM to initialize — steps enable once the engine is ready.
Steps
Run all restarts this sample lesson and stops at the first failed check. Only the declared command and response code count as an expected refusal; other errors remain incomplete. Retry a failed step after resolving its error.
TPM2_SelfTest(fullTest=YES)
1. Run the full algorithm self-test
TPM2_GetCapability(TPM_CAP_ALGS)
2. Read the algorithm table — both eras in one list
TPM2_GetCapability(TPM_CAP_TPM_PROPERTIES)
3. Check the version this chip actually claims to be
TPM2_GetRandom(32)
4. Request 32 bytes from the software TPM emulator
TPM2_Startup (again)
5. Break a rule on purpose: start an already-started TPM
Production Tool Capabilities & Verification Requirements
What this sample check establishes: Exercises TPM 2.0 command/response hierarchies (`TPM2_CreatePrimary`, `TPM2_Create`, `TPM2_Sign`, `TPM2_Quote`, PCR policy binding) and PQC migration patterns.
Browser sandbox limitation (non-certification boundary): Uses an in-browser software TPM simulator; it does not measure discrete SPI/I2C TPM 2.0 chip latency or physical bus interposer protection.
What to require and test in your production tools:
- TCG TPM 2.0 Library Version 185 or later firmware/hardware supporting post-quantum algorithms (`ML-DSA`, `HashML-DSA`, `ML-KEM`) as silicon ships.
- Hybrid TPM + host software/HSM key-wrapping patterns where existing soldered TPM 2.0 chips support only classical algorithms (typically RSA-2048 / ECC P-256 at minimum).
- PCR-bound sealing policies verified against signed UEFI Secure Boot and OS kernel measurements.
Try it
- 1. Predict before you run it.
- 2. Run or change the tool above.
- 3. Explain what the result shows.
Track T5 says pure ML-DSA must see the whole message. What TPM command difference does that produce?
Next step
Turn it into a plan: Infrastructure Modernization PlannerThis tool practises the Secure Boot & Firmware PQC module, phase 6 (Infrastructure & Performance); Infrastructure Modernization Planner produces a deliverable of that phase.
Related content
Next in Protocol Simulations