Skip to content

should repository make unversioned root metadata available or not? #184

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
jku opened this issue Sep 15, 2021 · 1 comment · Fixed by #187
Closed

should repository make unversioned root metadata available or not? #184

jku opened this issue Sep 15, 2021 · 1 comment · Fixed by #187

Comments

@jku
Copy link
Member

jku commented Sep 15, 2021

small inconsistency with regards to root.json versions: 6.2.1. Writing consistent snapshots states:

an implementation must write both root.json and version_number.root.json because it is possible to download root metadata both with and without known version numbers.

It is not in fact documented that client could download root without a version (client workflow only downloads versioned roots). I can see how a Trust-On-First-Use (TOFU) client initialization could use this but that is not defined in the spec.

I guess either

  • TOFU initialization could be mentioned as a possibility (even if not recommended)
  • the requirement to offer unversioned root.json should not be there
@joshuagl
Copy link
Member

Nice spot. Given the current spec, I do not think the repository should make unversioned root metadata available.

AFAICT the inconsistency is because in earlier versions of the spec root was not bootstrapped out-of-band and was always (I think) TOFU. Current spec explicitly does not want root metadata to be TOFU, we [always]:(https://theupdateframework.github.io/specification/latest/#load-trusted-root)

assume that a good, trusted copy of this file was shipped with the package manager or software updater using an out-of-band process.

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 a pull request may close this issue.

2 participants