Skip to content

Commit d5da437

Browse files
committed
Define DELEGATOR in targets workflow
Use DELEGATOR instead of TARGETS during the DFS for clarity Signed-off-by: Marina Moore <mnm678@gmail.com>
1 parent 21731f4 commit d5da437

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
@@ -1485,8 +1485,8 @@ it in the next step.
14851485
2. Otherwise, recursively search the list of delegations in
14861486
order of appearance.
14871487

1488-
1. Let DELEGATEE denote the current target role TARGETS is
1489-
delegating to.
1488+
1. Let DELEGATOR be the current target role TARGETS and DELEGATEE denote
1489+
the current target role DELEGATOR is delegating to.
14901490

14911491
2. **Download the DELEGATEE targets metadata file**, up to either
14921492
the number of bytes specified in the snapshot metadata file, or some Z
@@ -1509,7 +1509,7 @@ it in the next step.
15091509

15101510
4. **Check for an arbitrary software attack.** The new DELEGATEE
15111511
metadata file MUST have been signed by a threshold of keys specified in the
1512-
TARGETS metadata file. If the new DELEGATEE metadata file is not signed
1512+
DELEGATOR metadata file. If the new DELEGATEE metadata file is not signed
15131513
as required, abort the update cycle, and report the failure.
15141514

15151515
5. **Check for a freeze attack.** The latest known time

0 commit comments

Comments
 (0)