Skip to content
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

FAPI: Fix usage of external PEM keys for PolicyAuthorize. #2848

Conversation

JuergenReppSIT
Copy link
Member

  • PolicyAuthorize with an external imported PEM key did not work if the default nameAlg for the imported key (sha1) was not equal to the default nameAlg in the current fapi profile. The nameAlg from the profile is now used for the imported key.
  • To prevent a possible double free after cleanup of a policy the NULL pointer is set for the reference to this policy.

@JuergenReppSIT JuergenReppSIT force-pushed the fapi-fix-policy-authorize-with-imported-pem-key branch from ea2337f to 23be137 Compare June 2, 2024 16:15
@JuergenReppSIT JuergenReppSIT added bug backport Issues to be backported to old-stable labels Jun 3, 2024
* PolicyAuthorize with an external imported PEM key did not work if
  the default nameAlg for the imported key (sha1) was not equal to
  the default nameAlg in the current fapi profile.
  The nameAlg from the profile is now used for the imported key.
* To prevent a possible double free after cleanup of a policy
  the NULL pointer is set for the reference to this policy.

Signed-off-by: Juergen Repp <[email protected]>
@JuergenReppSIT JuergenReppSIT force-pushed the fapi-fix-policy-authorize-with-imported-pem-key branch from 23be137 to 3155417 Compare June 10, 2024 07:04
@JuergenReppSIT JuergenReppSIT merged commit ba2ea64 into tpm2-software:master Jun 10, 2024
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Issues to be backported to old-stable bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants