Skip to content

Clarify rotation in 1.9 #74

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from

Conversation

mnm678
Copy link
Collaborator

@mnm678 mnm678 commented Dec 13, 2019

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.

Copy link
Member

@lukpueh lukpueh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

tuf-spec.md Outdated
@@ -1116,7 +1116,7 @@ repo](https://github.com/theupdateframework/specification/issues).
cycle, report the potential freeze attack. On the next update cycle, begin
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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A threshold of timestamp / snapshot keys compared to what? Version N of the root metadata file from Step 1.1?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I will clarify in the text.

@lukpueh
Copy link
Member

lukpueh commented Jan 30, 2020

Superseded by #86

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants