Skip to content

Consistent snapshots for root metadata #52

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Oct 3, 2019
Merged

Consistent snapshots for root metadata #52

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
eb2927e
Consistent snapshots for root metadata
trishankatdatadog Oct 3, 2019
992ae37
clarify
trishankatdatadog Oct 3, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions tuf-spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1353,6 +1353,10 @@ non-volatile storage as FILENAME.EXT.
snapshots are not written by the repository, then the attribute may either
be left unspecified or be set to the False value. Otherwise, it must be
set to the True value.

Regardless of whether consistent snapshots are ever used or not, all
released versions of root metadata files should always be provided
so that outdated clients can update to the latest available root.

For more details on how this would apply on a community repository, please
see https://github.com/theupdateframework/pep-on-pypi-with-tuf#producing-consistent-snapshots
Expand Down