Skip to content

Commit f68ea33

Browse files
committed
clarify that double publish is not allowed
1 parent 504d7e7 commit f68ea33

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

text/0000-cargo-asymmetric-tokens.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,10 @@ The registry server will validate the PASETO, and check the footer and claims:
116116
- The URL matches the registry base URL (to make sure a PASETO sent to one registry can't be used to authenticate to another, and to prevent typosquatting/homoglyph attacks)
117117
- The PASETO is still within its valid time period (to limit replay attacks). We recommend a 15 minute limit, but a shorter time can be used by a registry to further decrease replayability. Or a longer one can be used to better accommodate clock skew.
118118
- If the server issues challenges, that the challenge has not yet been answered.
119-
- If the operation is a mutation, that the package, version, and hash match the request.
119+
- If the operation is a mutation:
120+
- That the operation matches the `mutation` field an is one of `publish`, `yank`, or `unyank`.
121+
- That the package, version, and hash match the request.
122+
- If the mutation is `publish`, that the version has not already been published.
120123

121124
See the [Appendix: Token Examples](#token-examples) for a walk through of constructing some tokens.
122125

0 commit comments

Comments
 (0)