tpm2: Add missing check for disallowed SHA1 HMAC creation#573
Merged
stefanberger merged 1 commit intomasterfrom Mar 19, 2026
Merged
tpm2: Add missing check for disallowed SHA1 HMAC creation#573stefanberger merged 1 commit intomasterfrom
stefanberger merged 1 commit intomasterfrom
Conversation
stefanberger
force-pushed
the
master.next
branch
from
94dc182 to
69b2f67
Compare
CryptSelectMac is called (only) from TPM2_HMAC and TPM2_Mac_Start and needs to check whether the creation of an HMAC with SHA1 is not allowed per the profile attribute no-sha1-hmac-creation and/or no-sha1-hmac. Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
stefanberger
force-pushed
the
master.next
branch
from
69b2f67 to
b9eee49
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CryptSelectMac is called (only) from TPM2_HMAC and TPM2_Mac_Start and needs to check whether the creation of an HMAC with SHA1 is not allowed per the profile attribute no-sha1-hmac-creation and/or no-sha1-hmac.