From 6eb5f122e5225bbd30e217a6a7d5eea3f5d7ab9e Mon Sep 17 00:00:00 2001 From: Martin Vrachev Date: Wed, 21 Apr 2021 19:41:18 +0300 Subject: [PATCH] Clarify "paths" and "path_hash_prefixes" Clarify "paths" and "path_hash_prefixes" in delegations, because currently, it's not properly defined which of these options can be used to create a valid target file: - BOTH paths and path_hash_prefixes - ONLY ONE of paths and path_hash_prefixes - NONE of paths and path_hash_prefixes With this change, I aim to define clearly that a valid target file will contain ONLY ONE of them or NONE of them. Signed-off-by: Martin Vrachev --- tuf-spec.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/tuf-spec.md b/tuf-spec.md index 8a6dde1..81a7a0f 100644 --- a/tuf-spec.md +++ b/tuf-spec.md @@ -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 @@ -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 Note: We strive to make the specification easy to implement, so if you come @@ -1018,9 +1018,8 @@ as is described for the root.json 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 -"path_hash_prefixes" or "paths" attributes, each of which we -discuss next. +The "path_hash_prefixes" and "paths" +attributes are optional, if used, exactly one of them should be set. : "path_hash_prefixes" ::