-
Notifications
You must be signed in to change notification settings - Fork 281
Clarify procedure for updating to new root.json #444
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
Conversation
Client's should validate new root.json according to the threshold and keys set by its previous version. See @heartsucker comment [here](theupdateframework/rust-tuf#42 (comment))
|
@heartsucker Let us know if this PR captures the case you raised in issue rust-tuf/32 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's still a bit confusing. How about this paragraph?
To replace a compromised root key or any other top-level role key, the root
role signs a new root.json file that lists the updated trusted keys for the
role.
In the event that the keys being updated are root keys, it is important to
note that the new root.json must at least be signed by the keys listed as
root keys in the previous version of root.json, up to the threshold listed for
root in the previous version of root.json. If this is not the case, clients will
(correctly) not validate the new root.json file.
|
@awwad I added your and heartsucker's suggestions. What do you think of the changes? |
|
I think it's good, with the typo at the end fixed. You don't think my wording was wordy / unclear, then, I gather? |
|
Oh - btw, contingent on the instructions for the client updater procedure being added as well, which we talked about. (Something like what @heartsucker has in #444). I guess @trishankkarthik is doing that? |
|
Yup, a detailed client update workflow is being added to the specification in pull request #440. |
Clients should validate new root.json according to the threshold and keys set by its previous version.
See @heartsucker's comment here.