Do not close the PKCS11 context on startup #282
Merged
Conversation
This file contains 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
When Fulcio is started with PKCS11 CA, every signing request fails with "context is closed" error. This is because the private key is loaded once but then its context is closed. The private key of the CA doesn't change during the entire lifecycle of Fulcio and it cannot be used without active context. Closes: sigstore#281 Signed-off-by: Radoslav Gerganov <rgerganov@vmware.com>
dlorenc
approved these changes
Dec 15, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When Fulcio is started with PKCS11 CA, every signing request fails with
"context is closed" error. This is because the private key is loaded
once but then its context is closed. The private key of the CA doesn't
change during the entire lifecycle of Fulcio and it cannot be used
without active context.
Closes: #281
Signed-off-by: Radoslav Gerganov rgerganov@vmware.com