Skip to content

Commit 9d21a28

Browse files
committed
Consolidate KEYID remarks in format principles
The "File formats: general principles" section had two separate places discussing KEYIDs, consolidate those in the same place -- where the definition is. Signed-off-by: Joshua Lock <jlock@vmware.com>
1 parent d26a912 commit 9d21a28

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

tuf-spec.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -527,7 +527,8 @@ All signed metadata objects have the format:
527527

528528
: <dfn for="role">KEYID</dfn>
529529
::
530-
The identifier of the key signing the <a for="role">ROLE</a> dictionary.
530+
The identifier of the key signing the <a for="role">ROLE</a> object,
531+
which is a hexdigest of the SHA-256 hash of the canonical form of the key.
531532

532533
: <dfn>SIGNATURE</dfn>
533534
::
@@ -635,9 +636,6 @@ The <dfn for="keytype">"ecdsa-sha2-nistp256"</dfn> format is:
635636
::
636637
PEM format and a string.
637638

638-
The <a for="role">KEYID</a> of a key is the hexdigest of the SHA-256 hash of
639-
the canonical form of the key.
640-
641639
Metadata <dfn>date-time</dfn> follows the ISO 8601 standard. The expected
642640
format of the combined date and time string is "YYYY-MM-DDTHH:MM:SSZ". Time is
643641
always in UTC, and the "Z" time zone designator is attached to indicate a

0 commit comments

Comments
 (0)