Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify "paths" and "path_hash_prefixes" #158

Closed
wants to merge 1 commit into from
Closed

Clarify "paths" and "path_hash_prefixes" #158

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions tuf-spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ Title: The Update Framework Specification
Shortname: TUF
Status: LS
Abstract: A framework for securing software update systems.
Date: 2020-12-11
Date: 2020-04-21
Editor: Justin Cappos, NYU
Editor: Trishank Karthik Kuppusamy, Datadog
Editor: Joshua Lock, VMware
Expand All @@ -16,7 +16,7 @@ Boilerplate: copyright no, conformance no
Local Boilerplate: header yes
Markup Shorthands: css no, markdown yes
Metadata Include: This version off, Abstract off
Text Macro: VERSION 1.0.17
Text Macro: VERSION 1.0.19
</pre>

Note: We strive to make the specification easy to implement, so if you come
Expand Down Expand Up @@ -1018,9 +1018,8 @@ as is described for the <a>root.json</a> file.
package that are not made by the delegated party or its descendants to be
ignored.

In order to discuss target paths, a role MUST specify only one of the
<a>"path_hash_prefixes"</a> or <a for="delegation-role">"paths"</a> attributes, each of which we
discuss next.
The <a>"path_hash_prefixes"</a> and <a for="delegation-role">"paths"</a>
attributes are optional, if used, exactly one of them should be set.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
attributes are optional, if used, exactly one of them should be set.
attributes are OPTIONAL, if used, exactly one of them should be set.

We use RFC 2119 keywords in the spec.


: <dfn>"path_hash_prefixes"</dfn>
::
Expand Down