Conflicting TPM2 engines and storage formats
David Woodhouse
Quoted 25 lines · James Bottomley
Quoted 21 lines
Quoted 11 lines
Quoted 10 lines
thanks for the summary. I agree with all of them. Some more things to agree on:
Primarykeys.publicArea:
- .type =TPM2_ALG_ECC,
.nameAlg =TPM2_ALG_SHA256
- .objectAttributes = (TPMA_OBJECT_USERWITHAUTH|TPMA_OBJECT_RESTRICTED|TPMA_OBJECT_DECRYPT|TPMA_OBJECT_FIXEDTPM|TPMA_OBJECT_FIXEDPARENT|TPMA_OBJECT_SENSITIVEDATAORIGIN)Quoted 9 lines
Actually, this is way too little. In fact we don't care about the asymmetric key at all because it's the derived symmetric key that's used to encrypt the private blob (so you're missing its parameters). Unfortunately the type and all the asymmetric parameters (including a lot you haven't show here) are part of the name which is input to KDFa for the symmetric key. Let's just follow all the provisioning guidance because it does outline them in a table, so just say "The ECC Template from the EK and TPM provisioning guides".
Quoted 3 lines
That seems to make sense. Other than the objectAttributes, what else have we done *differently* to the template in the provisioning guides?
Quoted 5 lines
Nothing, everything else seems to match including the symmetric parameters, the curve and the unique point. The annoying thing is the name as input to KDFa. It's the sha256 sum of the entire public area, so every single parameter has to match to get the KDFa to spit back the same symmetric key.
The provisioning guide says to set TPMA_OBJECT_NODA, doesn't it?