bump: update go-tuf and add testing for hex encoded sign verify #374
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
Signed-off-by: Asra Ali <asraa@google.com>
asraa
requested review from
haydentherapper,
joshuagl,
kommendorkapten and
dlorenc
|
Nice to see that a lot of code was removed and replaced with the |
Preparation for deprecating it hehe 👿 |
Signed-off-by: Asra Ali <asraa@google.com>
dlorenc
approved these changes
Sep 12, 2022
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.
Signed-off-by: Asra Ali asraa@google.com
This is PART 1 of the plan to implement hex to PEM ecdsa key migration:
#329 (comment)
Summary
SignCmdcan verify against the go-tuf verifier.This does not change any functionality in the code. We are still using ECDSA keys for the HSM and online key signers. Wait for the following parts of the change!
Release Note
Documentation