Adds keyid_hash_algorithms to returned key objects #37
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.
Fixes #36 and, once integrated and TUF is updated to use the new version, theupdateframework/python-tuf#412.
The functions listed below all return key objects that can carry an optional
keyid_hash_algorithms
field according to their schema. With this PR we always add thekeyid_hash_algorithm
field to the returned object, in:e.g.:
The PR also changes PUBLIC_KEY_SCHEMA to accept the optional
keyid_hash_algorithm
(like ANYKEY_SCHEMA).The reason for adding this field is to be able to associate a key with e.g. a signature created by that key, but listing a different keyid, because a different keyid hash algorithm was used. By trying all possible algorithms, the key can still be matched.