Skip to content

Commit 5f62112

Browse files
lukpuehmnm678
authored andcommitted
Clarify recovery from ffwd on top-level targets
To recover from a fast-forward attack on the top-level targets metadata, only targets and snapshot (not timestamp) metadata must be untrusted/deleted. Targets, because it was attacker controlled, and snapshot, because it unwittingly might have unwittingly recorded the attacker controlled targets version.
1 parent 7d1695e commit 5f62112

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

tuf-spec.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1327,9 +1327,10 @@ it in the next step.
13271327
paper](https://ssl.engineering.nyu.edu/papers/kuppusamy-mercury-usenix-2017.pdf)
13281328
for more details.
13291329

1330-
1. **Targets recovery** If a threshold of targets keys are removed
1331-
from the root metadata, delete the old top-level targets, snapshot, and
1332-
timestamp metadata files.
1330+
1. **Targets recovery** If a threshold of targets keys have been
1331+
removed in the new trusted root metadata compared to the previous trusted
1332+
root metadata, delete the old top-level targets and snapshot metadata
1333+
files.
13331334

13341335
2. **Snapshot recovery** If a threshold of snapshot keys have
13351336
been removed in the new trusted root metadata compared to the previous

0 commit comments

Comments
 (0)