Skip to content

Commit fae9636

Browse files
saurabhsadhalesusekakabisht
authored andcommitted
[5.4] Updating the broken hyperlink
Linked to same #199
1 parent 0a6d695 commit fae9636

File tree

1 file changed

+1
-1
lines changed
  • versioned_docs/version-5.4/05.policy/03.admission/01.sigstore

1 file changed

+1
-1
lines changed

versioned_docs/version-5.4/05.policy/03.admission/01.sigstore/01.sigstore.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ A private root of trust requires the the keys and/or certificates from your priv
2121

2222
![sigstore](2configure-private-root-of-trust.png)
2323

24-
Next, for a given root of trust, configure each of the verifiers that you would like to use during admission control. There are two types of verifiers: keypair and keyless. A keypair verifier would be used when trying to verify an image signed by a user-defined private key. A keyless verifier would be used when verifying a signature generated by Sigstore's keyless pattern. More information about the Sigstore signing methods can be seen [here](https://docs.sigstore.dev/cosign/overview/).
24+
Next, for a given root of trust, configure each of the verifiers that you would like to use during admission control. There are two types of verifiers: keypair and keyless. A keypair verifier would be used when trying to verify an image signed by a user-defined private key. A keyless verifier would be used when verifying a signature generated by Sigstore's keyless pattern. More information about the Sigstore signing methods can be seen [here](https://docs.sigstore.dev/quickstart/quickstart-cosign/).
2525

2626
To configure a keypair verifier, provide a name, and a public key corresponding to a target private key.
2727

0 commit comments

Comments
 (0)