Rework keys to remove PemReader, user BC instead #568
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
|
this should fix some of the key fuzzing issues in: https://bugs.chromium.org/p/oss-fuzz/issues/list?q=label:Proj-sigstore-java |
patflynn
reviewed
Nov 4, 2023
Signed-off-by: Appu Goundan <[email protected]>
loosebazooka
force-pushed
the
fix-keys-fuzzer
branch
from
7c19a05 to
9446dfb
Compare
patflynn
approved these changes
Nov 7, 2023
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.
PEM reader will error in unexpected ways because it is too permissive for poorly formed objects.
While I was reworking that, it made sense to just clean up the Keys stuff