Skip to contentSkip to conversation

Calculating name of created AK- server side

tpm2 kuba.michal.n at gmail.com 2 participants 9 messages Jan 28, 2021 – Jun 18, 2022

lore
Share & tools
lore

kuba.michal.n at gmail.com

#0 lore raw

Hello!
I would like to know if it is possible to calculate name of AK generated by host on a remote server? I have read about remote attestation. To ensure the AK matches EK we have to make credential using name of the AK. To achieve this we have to either:
a) calculate name of the AK on server
b) receive name of the AK from host and believe it's a name for a proper AK

Am I missing something?

I have searched for explanation in docs posted on TCG's site, but I just can't find anything useful for nameAlg.

I would be thankful for any help or advice :D

#2 lore raw

Hello Imran! Thank You for your response

I have read this tutorial before writing my question. It's just amazing :D My question relates to this command:

tpm2_makecredential \
--tcti none \
--encryption-key rsa_ek.pub \
--secret file_input.data \
--name $loaded_key_name \ # this line :)
--credential-blob cred.out

Anonymity is not our concern. We want to ensure that only those computers which were handed by us to our employees can access internal resources. My idea was to generate EK and AK just like in tutorial, and then send EK certificate and public part of AK to some auth server. Then server would calculate the name and make use of tpm2_makecredential.

I have probably overlooked something really important.

Thank you in advance :D

#3 lore raw

I see. A quick explainer :)

So AKname is not a secret. Neither is it possible to fake one. And so can be handed from the client to the server anytime. (tpm2_readpublic -c ak.ctx -n ak.name)

The credential challenge posed by the server (makecredential) wraps and encrypts a plaintext-credential using the EKpublic and AKname.

Only a client with access to the respective sensitive(private) portions of the EK and AK will have to load the keys on the TPM and it is then able to unwrap/decrypt the credentialBlob with credential-activation.

#4 lore raw

Thank You for clear explanation :D