Skip to content

Commit f1d2e71

Browse files
lukpuehjoshuagl
authored andcommitted
Revert "97312dd" and "d97da38"
This reverts commits: - Clarify timestamp.json METAFILES format 97312dd - LENGTH isn't optional in timestamp.json for snapshot.json d97da38
1 parent 4202bab commit f1d2e71

File tree

1 file changed

+2
-23
lines changed

1 file changed

+2
-23
lines changed

tuf-spec.md

Lines changed: 2 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -979,31 +979,10 @@ repo](https://github.com/theupdateframework/specification/issues).
979979
"meta" : METAFILES
980980
}
981981

982-
METAFILES is an object whose format is the following:
983-
984-
{ METAPATH : {
985-
"version" : VERSION,
986-
"length" : LENGTH, |
987-
"hashes" : HASHES }
988-
, ...
989-
}
990-
991-
METAPATH is the snapshot.json file's path on the repository relative to the
992-
metadata base URL.
993-
994-
VERSION is the version of the snapshot metadata as listed in the
982+
METAFILES is the same is described for the snapshot.json file. In the case
983+
of the timestamp.json file, this MUST only include a description of the
995984
snapshot.json file.
996985

997-
LENGTH is the integer length in bytes of the snapshot metadata file.
998-
999-
HASHES is the dictionary that specifies one or more hashes of the snapshot
1000-
metadata file, including the cryptographic hash function. For example:
1001-
{ "sha256": HASH, ... }.
1002-
1003-
Note: METAFILES is the same as is described for the snapshot.json file, only
1004-
the LENGTH and HASHES are not optional and in the case of the timestamp.json
1005-
file, this MUST only include a description of the snapshot.json file.
1006-
1007986
A signed timestamp.json example file:
1008987

1009988
{

0 commit comments

Comments
 (0)