From 22403a09b3ae2902ece9bc8a293ac207ae2adbde Mon Sep 17 00:00:00 2001 From: saurabhsadhalesuse Date: Thu, 18 Sep 2025 16:04:42 +0530 Subject: [PATCH] Updating the broken hyperlink The previous links were broken. Changed the link to correctly reflect. --- docs/05.policy/03.admission/01.sigstore/01.sigstore.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/05.policy/03.admission/01.sigstore/01.sigstore.md b/docs/05.policy/03.admission/01.sigstore/01.sigstore.md index 8a8507786..1a637086c 100644 --- a/docs/05.policy/03.admission/01.sigstore/01.sigstore.md +++ b/docs/05.policy/03.admission/01.sigstore/01.sigstore.md @@ -21,7 +21,7 @@ A private root of trust requires the the keys and/or certificates from your priv ![sigstore](2configure-private-root-of-trust.png) -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/). +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/). To configure a keypair verifier, provide a name, and a public key corresponding to a target private key.