Clarify rotation in 1.9#74
Closed
mnm678 wants to merge 3 commits into
Closed
Conversation
| at step 0 and version N of the root metadata file. | ||
|
|
||
| * **1.9**. **If the timestamp and / or snapshot keys have been rotated, then | ||
| * **1.9**. **If a threshold of timestamp and / or snapshot keys have been removed, then |
Contributor
There was a problem hiding this comment.
A threshold of timestamp / snapshot keys compared to what? Version N of the root metadata file from Step 1.1?
Collaborator
Author
There was a problem hiding this comment.
Yes, I will clarify in the text.
Member
|
Superseded by #86 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Addresses part of #71
Replace the use of 'rotate' with a description of the keys that would be removed when recovering from a fast-forward attack.