Skip to content

Commit 68d24e2

Browse files
lukpuehjoshuagl
authored andcommitted
Clarify snapshot download limit on client
Describe how to use a client-defined upper limit for snapshot metadata if timestamp does not specify its length.
1 parent f1d2e71 commit 68d24e2

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

tuf-spec.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1153,8 +1153,10 @@ as FILENAME.EXT.
11531153
file. If the new timestamp metadata file has expired, discard it, abort the
11541154
update cycle, and report the potential freeze attack.
11551155

1156-
**3**. **Download snapshot metadata file**, up to the number of bytes specified
1157-
in the timestamp metadata file. If consistent snapshots are not used (see
1156+
**3**. **Download snapshot metadata file**, up to the number of bytes
1157+
specified in the timestamp metadata file. If not specified, download up to a
1158+
number of bytes set by the authors of the application using TUF. This may be
1159+
tens of kilobytes. If consistent snapshots are not used (see
11581160
Section 7), then the filename used to download the snapshot metadata file is of
11591161
the fixed form FILENAME.EXT (e.g., snapshot.json). Otherwise, the filename is
11601162
of the form VERSION_NUMBER.FILENAME.EXT (e.g., 42.snapshot.json), where

0 commit comments

Comments
 (0)