Update wildcard pattern behavior

This commit adds explicit examples of targets that are not matched by a
wildcard. It also adds a note warning users that incorrect assumptions
about wildcard behavior can potentially lead to an untrusted role
signing for a target.

Signed-off-by: Aditya Sirish <aditya@saky.in>

Author: adityasaky

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: 2023-04-14
+Date: 2024-02-23
 Editor: Justin Cappos, NYU
 Editor: Trishank Karthik Kuppusamy, Datadog
 Editor: Joshua Lock, Verizon
@@ -1093,8 +1093,17 @@ attributes are OPTIONAL, if used, exactly one of them should be set.
       `"foo-version-2.tgz"` and `"foo-version-a.tgz"`, but not
       `"foo-version-alpha.tgz"`.
     * a <a>PATHPATTERN</a> of `"*.tgz"` would match `"foo.tgz"` and `"bar.tgz"`,
-      but not `"targets/foo.tgz"`
-    * a <a>PATHPATTERN</a> of `"foo.tgz"` would match only `"foo.tgz"`
+      but not `"targets/foo.tgz"`.
+    * a <a>PATHPATTERN</a> of `"foo.tgz"` would match only `"foo.tgz"`.
+    * a <a>PATHPATTERN</a> of `"foo/*"` matches `"foo/bar.tgz"` but not
+      `"foo/baz/bar.tgz"`, `"foo/bar/baz/bar.tgz"`, and so on.
+
+    Note: It is important to understand the functioning of path patterns to
+    avoid mistaken assumptions that can lead to a false sense of security. For
+    example, an assumption that `"foo/*"` applies recursively to all files in
+    subdirectories of `foo` in a terminating delegation could allow a subsequent
+    delegated role that should not be trusted to sign for a target.
+
 
 
 Prioritized delegations allow clients to resolve conflicts between delegated