diff options
| author | James Bottomley <James.Bottomley@HansenPartnership.com> | 2024-04-18 09:56:44 -0400 |
|---|---|---|
| committer | James Bottomley <James.Bottomley@HansenPartnership.com> | 2024-04-18 15:14:24 -0400 |
| commit | a9d52c05faf1509cf45c97834fbd14a5268b8d6f (patch) | |
| tree | 6e244298a85467ad60837806958fe3d878b63feb | |
| parent | 897d73fca93c2d8cb3b60f929978145cdbb95dcb (diff) | |
| download | openssl_tpm2_engine-a9d52c05faf1509cf45c97834fbd14a5268b8d6f.tar.gz | |
doc: update draft RFC to specify the template exactly
The TCG created some confusion with primary templates over what should
be in the unique value. All implementations so far have taken the
view that it should be two zero size points. However, the L template
and earlier TCG drafts required two 32 byte zero filled points. To
clear this up entirely, specify that the P-256 key must use the H-2
template (matching what everyone currently does) and that the RSA2048
key must use the H-1 template.
Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
Reviewed-by: David Woodhouse <dwmw@amazon.co.uk>
| -rw-r--r-- | doc/draft-bottomley-tpm2-keys.xml | 24 |
1 files changed, 20 insertions, 4 deletions
diff --git a/doc/draft-bottomley-tpm2-keys.xml b/doc/draft-bottomley-tpm2-keys.xml index 960b923..db58618 100644 --- a/doc/draft-bottomley-tpm2-keys.xml +++ b/doc/draft-bottomley-tpm2-keys.xml @@ -232,11 +232,17 @@ An alternate method (rfc include) is described in the references. implementation MUST run TPM2_CreatePrimary on the handle using the TCG specified Elliptic Curve template <xref target="TCG-Provision"/> (section 7.5.1 for the Storage - and other seeds or 7.4.1 for the endorsement seed) for - the NIST P-256 curve if rsaParent is absent or the RSA + and other seeds or 7.4.1 for the endorsement seed) which + refers to the TCG EK Credential Profile <xref + target="TCG-EK-Profile"/> . Since there are several + possible templates, implementations MUST always use the H + template (the one with zero size unique fields). The + template used MUST be H-2 (EK Credential Profile section + B.4.5) for the NIST P-256 curve if rsaParent is absent or + the H-1 (EK Credential Profile section B.4.4) RSA template with a key length of 2048 if rsaParent is - present and true and use the primary key so generated - as the parent. + present and true and use the primary key so generated as + the parent. </t> </section> <section title="pubkey"> @@ -729,6 +735,16 @@ An alternate method (rfc include) is described in the references. <date year="2017" month="March" day="15"/> </front> </reference> + <reference anchor="TCG-EK-Profile" target="https://trustedcomputinggroup.org/resource/http-trustedcomputinggroup-org-wp-content-uploads-tcg-ek-credential-profile-v-2-5-r2_published-pdf/"> + <front> + <title>TCG EK Credential Profile For TPM Family 2.0; Level + 0</title> + <author> + <organization>Trusted Computing Group</organization> + </author> + <date year="2022" month="January" day="26"/> + </front> + </reference> </references> <references title="Informative References"> <reference anchor="TPM GENIE" target="https://www.nccgroup.com/globalassets/about-us/us/documents/tpm-genie.pdf"> |