Skip to content

Commit e53f11c

Browse files
committed
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 3ca7683 commit e53f11c

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
@@ -1149,8 +1149,10 @@ as FILENAME.EXT.
11491149
file. If the new timestamp metadata file has expired, discard it, abort the
11501150
update cycle, and report the potential freeze attack.
11511151

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

0 commit comments

Comments
 (0)