Repository navigation
Add SHA384 algorithm support - #139
Merged
Merged
Conversation
gustavo16a
force-pushed
the
add-pesign-sha384-algorithm
branch
from
September 8, 2026 17:09
28516f9 to
7aff0b7
Compare
vathpela
force-pushed
the
add-pesign-sha384-algorithm
branch
from
September 16, 2026 14:11
7aff0b7 to
1e6769d
Compare
"pesign -d sha384" currently returns not found, as the algorithm is not implemented in the CMS signature generation and verification process. Therefore, this commit adds SHA384 algorithm support. Signed-off-by: Gustavo dos Santos Cardoso <gustavo_16a@hotmail.com>
vathpela
force-pushed
the
add-pesign-sha384-algorithm
branch
from
September 16, 2026 14:17
1e6769d to
be4c9f7
Compare
nfrayer
self-requested a review
September 16, 2026 14:39
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
2 participants
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.
Currently SHA384 algorithm is not supported for pesign. With the command below returning not found:
In general SHA256 is always used, however in some cases, some HSMs only expose SHA384 algorithms.
This change was tested generating signature attributes and then reattaching it to the binary, the workflow was like below:
After that with OVMF build and secureboot enabled with loaded certificate (
RSA4096_cert.pem) into db, the shellx64.signed.efi binary was successfully booted.