fix: Update the ecdsa key type to the latest spec (1.0.32). #508
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 old ecdsa key type is kept to be able to consume older metadata files.
Release Notes:
The go-tuf package now understands the ecdsa key type as specified by The Updateframework specification v1.0.32.
Types of changes:
Description of the changes being introduced by the pull request:
TUF spec v1.0.32 does not specify the
ecdsa-sha2-nistp256
key type anymore. Instead the key type isecdsa
. See this PR for more details.This fix adds
ecdsa
as a known key type, and the default to use when returning the "public data" for a key. The old format (ecdsa-sha2-nistp256
) is still recognized as a valid key type.Please verify and check that the pull request fulfills the following requirements: