-
Notifications
You must be signed in to change notification settings - Fork 382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tpm2_tools error 0x70001 with fips-updates on 22.04 #3420
Comments
awithy
changed the title
pm2_tools error 0x70001 with fips-updates on 22.04
tpm2_tools error 0x70001 with fips-updates on 22.04
Jul 27, 2024
Yes, the ERROR originates from an OpenSSL call to DigestSignInit for an HMAC. |
JuergenReppSIT
added a commit
to JuergenReppSIT/tpm2-tools
that referenced
this issue
Oct 4, 2024
For authentication of an object always an HMAC session was used. For an unsalted session an openssl HMAC key with the size of the auth value was created. This caused problems with the OpenSSL FIPS mode if the key length is less than 112 bits. To avoid this the option --pwd-session (-z) is added. Here the session handle ESYS_TR_PASSWORD will be used. For example, now the EK can be used to create a salted session: tpm2_createek --pwd-session -Q --key-algorithm rsa --ek-context ek.ctx tpm2_startauthsession -Q --session salted_session.ctx --hmac-session --tpmkey-context ek.ctx tpm2_sessionconfig -Q salted_session.ctx --enable-decrypt tpm2_createprimary -c prim.ctx -P session:salted_session.ctx Adresses: tpm2-software#3420 Signed-off-by: Juergen Repp <[email protected]>
JuergenReppSIT
added a commit
to JuergenReppSIT/tpm2-tools
that referenced
this issue
Oct 7, 2024
For authentication of an object always an HMAC session was used. For an unsalted session an openssl HMAC key with the size of the auth value was created. This caused problems with the OpenSSL FIPS mode if the key length is less than 112 bits. To avoid this the option --pwd-session (-z) is added. Here the session handle ESYS_TR_PASSWORD will be used. For example, now the EK can be used to create a salted session: tpm2_createek --pwd-session -Q --key-algorithm rsa --ek-context ek.ctx tpm2_startauthsession -Q --session salted_session.ctx --hmac-session --tpmkey-context ek.ctx tpm2_sessionconfig -Q salted_session.ctx --enable-decrypt tpm2_createprimary -c prim.ctx -P session:salted_session.ctx Adresses: tpm2-software#3420 Signed-off-by: Juergen Repp <[email protected]>
AndreasFuchsTPM
pushed a commit
that referenced
this issue
Dec 11, 2024
For authentication of an object always an HMAC session was used. For an unsalted session an openssl HMAC key with the size of the auth value was created. This caused problems with the OpenSSL FIPS mode if the key length is less than 112 bits. To avoid this the option --pwd-session (-z) is added. Here the session handle ESYS_TR_PASSWORD will be used. For example, now the EK can be used to create a salted session: tpm2_createek --pwd-session -Q --key-algorithm rsa --ek-context ek.ctx tpm2_startauthsession -Q --session salted_session.ctx --hmac-session --tpmkey-context ek.ctx tpm2_sessionconfig -Q salted_session.ctx --enable-decrypt tpm2_createprimary -c prim.ctx -P session:salted_session.ctx Adresses: #3420 Signed-off-by: Juergen Repp <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OS: Ubuntu 22.04 with fips-updates
Symptom: Use of TPM2 tools fails with error code 0x70001 (e.g.,
tpm2_clear
,tpm2_nvdefine 0x1500018 -C o -s 32
). I assume this is an incompatibility between tpm2-tools (5.2-1build1) and the fips OpenSSL package (3.0.5-0ubuntu0.1+Fips2.1).Example:
Steps to reproduce:
sudo tpm2_clear
This looks similar to:
#2957
Thank you in advance for considering this issue. Please let me know if I can help troubleshoot further.
The text was updated successfully, but these errors were encountered: