Skip to contentSkip to conversation

Conflicting TPM2 engines and storage formats

tpm2 Fuchs 2 participants 2 messages Oct 5, 2018 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Fuchs

#1 lore raw

We can tag -----BEGIN TSS2 PRIVATE KEY----- vs -----BEGIN TSS1 PRIVATE KEY----- then the contents can be completely different...
What do you say ?
________________________________________
From: James Bottomley [James.Bottomley(a)hansenpartnership.com]
Sent: Friday, October 05, 2018 17:29
To: Fuchs, Andreas; David Woodhouse; tpm2(a)lists.01.org; Nikos Mavrogiannopoulos
Cc: Richard Levitte
Subject: Re: [tpm2] Conflicting TPM2 engines and storage formats

Quoted 3 lines · Andreas

Actually, I like the TSS2 PEM Tag.
We could then also get rid of the OPTIONAL for publicKey, since we won't support TPMv1.2 anymore.

Actually, we might. It seems a lot of embedded is still 1.2 and they're having huge difficulty with trousers, so the ibmtss is growing a small 1.2 part that makes a direct tpm connection as well.

There's no harm to 2.0 in keeping it optional and it preserves the 1.2 compatibility just in case.

James

#2 lore raw
Quoted 4 lines · Andreas

We can tag -----BEGIN TSS2 PRIVATE KEY----- vs -----BEGIN TSS1 PRIVATE KEY-----
then the contents can be completely different... What do you say ?

I have no objection to that. In practice, anyone using TPMv1 keys is currently using the with -----BEGIN TSS KEY BLOB----- anyway. I don't think anyone ever actually implemented James's idea of putting a TPMv1 blob into his ASN.1 structure. And even if his engine ends up supporting both, doing both PEM tags is also fine.

But conversely, I don't see any problem with the 'pubkey' element being marked optional in the ASN.1 structure definition, even if it actually has to be there in practice.

It's not like there aren't an infinite number of *other* ways you can make a blob which matches the ASN.1 definition but won't actually work...