commit: 058af966a3ba02ef1321e58a3bf40c1b5266d3c7
[log]
author: Jan Wilken Dörrie <jdoerrie@chromium.org>
Wed May 27 09:55:47 2026
committer: Copybara-Service <copybara-worker@google.com>
Wed May 27 09:57:39 2026
tree: c9194f39919e6b60d9a85cfc9a5d6d618cdf7a8e
parent: 754c888afc968f7e8a6fa1f08bb9928fa6ab371f [diff]

[dbsc] Implement Rust TPM response parser for key certification

This CL introduces the memory-safe Rust parser for TPM2_Certify
responses, specifically validating the TPM2B_ATTEST and TPMT_SIGNATURE
structures. The parsed results are securely bounded and returned across
the CXX boundary via a CertifyResponse struct.

Bug: 501306222
Change-Id: Iacaf6b6c6325c0969b3939ef2dd782436a6a6964
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7830199
Reviewed-by: Elly <ellyjones@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1636806}
NOKEYCHECK=True
GitOrigin-RevId: 962f4cd8c41baab61806dcd5bdf1a8ce3afe793b

3 files changed

tree: c9194f39919e6b60d9a85cfc9a5d6d618cdf7a8e

README.md

//crypto README

This directory contains implementations of crypto primitives for use in Chromium. Most of these are either:

Wrappers around platform-specific APIs (DPAPI, libsecret, etc), so that code elsewhere in Chromium can use cross-platform abstractions, or
Wrappers around BoringSSL APIs that use Chromium-native types like base::span and similar

There is very little actual cryptographic code in //crypto - it is mostly wrappers.

This directory is actively being refactored as of 2025-06. See PLAN.md.

Commonly-Used Interfaces

AEAD: crypto/aead
Hashing: crypto/hash
HMACs: crypto/hmac
Key derivation: crypto/kdf
Public / private keys: crypto/keypair
Randomness: crypto/random
Signatures: crypto/sign

Many interfaces in this directory are deprecated and being changed or removed; check the comment at the top of the header file before using them.

Advice For Clients

Ciphertext, keys, certificates, and other cryptographic material are generally sequences of bytes, not characters, so prefer using byte-oriented types to represent them: vector<uint8_t>, array<uint8_t>, and span<uint8_t> rather than string and string_view.
To serialize private keys, use keypair::PrivateKey::ToPrivateKeyInfo(), which returns a PKCS#8 PrivateKeyInfo structure serialized as a byte vector. To unserialize keys in this format, use keypair::PrivateKey::FromPrivateKeyInfo().
To serialize public keys, use keypair::PublicKey::ToSubjectPublicKeyInfo() or keypair::PrivateKey::ToSubjectPublicKeyInfo(), which return a X.509 SubjectPublicKeyInfo structure serialized as a byte vector. To unserialize public keys in this format, use keypair::PublicKey::FromPublicKeyInfo().
SubjectPublicKeyInfo and PrivateKeyInfo can represent many kinds of keys, so code that expects a specific kind of key must check the kind after deserialization.
To serialize symmetric keys (AEAD, HMAC, or symmetric encryption keys), use a raw sequence of bytes for the key material. Represent these keys in memory using vector<uint8_t>, array<uint8_t>, or span<uint8_t> directly.