Add feature to parse both pkcs12 truststore and keystore formats #315
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
npdgm
force-pushed
the
find-parse-p12
branch
3 times, most recently
from
1052baa to
9dbeae0
Compare
# Conflicts: # go.mod
…besides p12 in future
…ords.yml key value (we are using pkcs12: key in this case, more container types can be added later
npdgm
force-pushed
the
find-parse-p12
branch
from
e34c3dc to
e88ef6c
Compare
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, no other implementations, even https://github.com/joe-elliott/cert-exporter supports reading both keystore and truststore.
This feature adds in that functionality to read password protected pkcs12 containers and read both keystore and truststore certificates for monitoring of expiring certificates.