You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/faq.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ rotate offline keys), and how to periodically update and re-sign metadata.
20
20
21
21
For (2), an adopter has to figure out how to ship the initial Root file, and
22
22
implement
23
-
[the TUF download and verification workflow](https://theupdateframework.github.io/specification/latest/#detailed-client-workflow)
23
+
[the TUF download and verification workflow](/specification/latest/#detailed-client-workflow)
24
24
in their language of choice if one of the existing implementations is
25
25
insufficient.
26
26
@@ -116,7 +116,7 @@ bandwidth associated with downloading the large file many times can be saved.
116
116
The reference implementation provides an
117
117
[easy way to distribute target files across many targets metadata](https://github.com/theupdateframework/python-tuf/blob/v0.20.0/examples/repo_example/hashed_bin_delegation.py)
118
118
(i.e., delegating to hashed bins), which the specification refers to as
0 commit comments