DataAuthentication

Selects how the client authenticates the data surrounding an attestation proof.

Signature signs the complete CertificationRequestInfo with the freshly attested key. This authenticates its subject, attributes, extensions, and public key and proves possession of the private key.

Hash is intended for ceremonies where proof of possession is not required, for example when using the private key would trigger user authentication. The client constructs an AttestationHashInput containing the TBS CSR version, subject, extensions, and all attributes except the attestation proof. Its DER encoding is hashed with Hash.algorithm. The resulting digest is used as nonce and fed into the key attestation flow. The client responds with an unsigned CertificationRequestInfo completed with the generated public key and attestation proof. The verifier verifies the attestation, checks that its key equals the TBS CSR public key, removes the public key and proof, and recomputes the digest. This binds every other TBS CSR field but deliberately provides no proof of possession.

Inheritors