Skip to content

Commit 3f5f5c0

Browse files
committed
Add definition for KEY
Add a KEY definition to the part of the "File formats: general principles" section that describes the KEY format. Signed-off-by: Joshua Lock <[email protected]>
1 parent 3fa355b commit 3f5f5c0

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

tuf-spec.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -534,7 +534,7 @@ All signed metadata objects have the format:
534534
A hex-encoded signature of the canonical form of the metadata for <a for="role">ROLE</a>.
535535

536536

537-
All keys have the format:
537+
All <dfn>KEY</dfn>s have the format:
538538

539539
<pre highlight="json">
540540
{
@@ -662,7 +662,7 @@ The "signed" portion of <a>root.json</a> is as follows:
662662
"version" : <a for="role">VERSION</a>,
663663
"expires" : <a>EXPIRES</a>,
664664
"keys" : {
665-
<a for="root">KEYID</a> : KEY,
665+
<a for="root">KEYID</a> : <a>KEY</a>,
666666
...
667667
},
668668
"roles" : {
@@ -983,7 +983,7 @@ as is described for the <a>root.json</a> file.
983983
<pre highlight="json">
984984
{
985985
"keys" : {
986-
<a for="role">KEYID</a> : KEY,
986+
<a for="role">KEYID</a> : <a>KEY</a>,
987987
...
988988
},
989989
"roles" : [

0 commit comments

Comments
 (0)