mirror of
https://github.com/theupdateframework/python-tuf
synced 2026-05-24 10:08:28 +00:00
Update tuf-spec.txt
Address issue #364. The specification includes examples of metadata with version numbers listed, but the description of snapshot.json does not. The `custom` field is listed only in targets metadata.
This commit is contained in:
parent
af17421709
commit
fbd901422f
1 changed files with 17 additions and 12 deletions
|
|
@ -381,8 +381,9 @@ Version 1.0 (Draft)
|
|||
|
||||
/snapshot.json
|
||||
|
||||
Signed by the snapshot role's keys. Lists hashes and sizes of all
|
||||
metadata files other than timestamp.json.
|
||||
Signed by the snapshot role's keys. Lists the version numbers of all
|
||||
metadata files other than timestamp.json. For the root role, the
|
||||
hash(es), size, and version number are listed.
|
||||
|
||||
/targets.json
|
||||
|
||||
|
|
@ -391,9 +392,10 @@ Version 1.0 (Draft)
|
|||
|
||||
/timestamp.json
|
||||
|
||||
Signed by the timestamp role's keys. Lists hashes and size of the
|
||||
snapshot file. This is the first and potentially only file that needs
|
||||
to be downloaded when clients poll for the existence of updates.
|
||||
Signed by the timestamp role's keys. Lists hash(es), size, and version
|
||||
number of the snapshot file. This is the first and potentially only
|
||||
file that needs to be downloaded when clients poll for the existence
|
||||
of updates.
|
||||
|
||||
/mirrors.json (optional)
|
||||
|
||||
|
|
@ -630,9 +632,10 @@ Version 1.0 (Draft)
|
|||
|
||||
4.4. File formats: snapshot.json
|
||||
|
||||
The snapshot.json file is signed by the snapshot role. It lists hashes and
|
||||
sizes of all metadata on the repository, excluding timestamp.json and
|
||||
mirrors.json.
|
||||
The snapshot.json file is signed by the snapshot role. It lists the version
|
||||
numbers of all metadata on the repository, excluding timestamp.json and
|
||||
mirrors.json. For the root role, the hash(es), size, and version number
|
||||
are listed.
|
||||
|
||||
The format of snapshot.json is as follows:
|
||||
|
||||
|
|
@ -647,16 +650,18 @@ Version 1.0 (Draft)
|
|||
{ METAPATH : {
|
||||
"length" : LENGTH,
|
||||
"hashes" : HASHES,
|
||||
("custom" : { ... }) }
|
||||
"version" : VERSION }
|
||||
, ...
|
||||
}
|
||||
|
||||
METAPATH is the the metadata file's path on the repository relative to the
|
||||
metadata base URL.
|
||||
|
||||
The HASHES and LENGTH are the hashes and length of the file. LENGTH is an
|
||||
integer. HASHES is a dictionary that specifies one or more hashes, including
|
||||
the cryptographic hash function. For example: { "sha256": HASH, ... }
|
||||
The HASHES and LENGTH are the hashes and length of the file, both of which
|
||||
are only specified for the root file. VERSION is listed for the root file
|
||||
and all other roles available on the repository. LENGTH is an integer.
|
||||
HASHES is a dictionary that specifies one or more hashes, including the
|
||||
cryptographic hash function. For example: { "sha256": HASH, ... }.
|
||||
|
||||
A signed snapshot.json example file:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue