Add support for non-bundled X.509 certificates to "Check Certificates" workflow #782
Conversation
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
…" workflow The digital certificates used for code signing are often stored in an archive file of the PKCS arduino#12 format, which allows multiple objects to be bundled in a single file. However, it also might occur that a single certificate is stored in X.509 format. Previously, the "Check Certificates" workflow only supported certificates in a PKCS arduino#12 archive. Support is hereby added to the workflow for validation of X.509 certificates in addition to PKCS arduino#12.
per1234
added
type: enhancement
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.
The digital certificates used for code signing are often stored in an archive file of the PKCS #12 format, which allows multiple objects to be bundled in a single file.
However, it also might occur that a single certificate is stored in X.509 format.
Previously, the "Check Certificates" workflow only supported certificates in a PKCS #12 archive. Support is hereby added to the workflow for validation of X.509 certificates in addition to PKCS #12.