diff --git a/docs/spec/v1/buckets.md b/docs/spec/v1/buckets.md index 8caadbe58..2f34f9e3a 100644 --- a/docs/spec/v1/buckets.md +++ b/docs/spec/v1/buckets.md @@ -144,7 +144,7 @@ attempt to communicate with the specified [Endpoint](#endpoint) using the [Minio Client SDK](https://github.com/minio/minio-go), which can communicate with any Amazon S3 compatible object storage (including [GCS](https://cloud.google.com/storage/docs/interoperability), -[Wasabi](https://wasabi-support.zendesk.com/hc/en-us/articles/360002079671-How-do-I-use-Minio-Client-with-Wasabi-), +[Wasabi](https://docs.wasabi.com/docs/how-do-i-use-minio-client-with-wasabi), and many others). The `generic` Provider _requires_ a [Secret reference](#secret-reference) to a diff --git a/docs/spec/v1/helmcharts.md b/docs/spec/v1/helmcharts.md index 87ee52ae0..22011bf2a 100644 --- a/docs/spec/v1/helmcharts.md +++ b/docs/spec/v1/helmcharts.md @@ -274,7 +274,7 @@ signatures. The field offers three subfields: #### Cosign -The `cosign` provider can be used to verify the signature of an OCI artifact using either a known public key or via the [Cosign Keyless](https://github.com/sigstore/cosign/blob/main/KEYLESS.md) procedure. +The `cosign` provider can be used to verify the signature of an OCI artifact using either a known public key or via the [Cosign Keyless](https://docs.sigstore.dev/cosign/signing/overview/) procedure. ```yaml --- @@ -321,7 +321,7 @@ This allows for older HelmCharts to be valid as long as the right key is in the ##### Keyless verification For publicly available HelmCharts, which are signed using the -[Cosign Keyless](https://github.com/sigstore/cosign/blob/main/KEYLESS.md) procedure, +[Cosign Keyless](https://docs.sigstore.dev/cosign/signing/overview/) procedure, you can enable the verification by omitting the `.verify.secretRef` field. To verify the identity's subject and the OIDC issuer present in the Fulcio diff --git a/docs/spec/v1/ocirepositories.md b/docs/spec/v1/ocirepositories.md index 67fa8c584..63b2b43bb 100644 --- a/docs/spec/v1/ocirepositories.md +++ b/docs/spec/v1/ocirepositories.md @@ -624,7 +624,7 @@ signatures. The field offers three subfields: #### Cosign The `cosign` provider can be used to verify the signature of an OCI artifact using either a known public key -or via the [Cosign Keyless](https://github.com/sigstore/cosign/blob/main/KEYLESS.md) procedure. +or via the [Cosign Keyless](https://docs.sigstore.dev/cosign/signing/overview/) procedure. ```yaml --- @@ -671,7 +671,7 @@ This allows for older artifacts to be valid as long as the right key is in the s ##### Keyless verification For publicly available OCI artifacts, which are signed using the -[Cosign Keyless](https://github.com/sigstore/cosign/blob/main/KEYLESS.md) procedure, +[Cosign Keyless](https://docs.sigstore.dev/cosign/signing/overview/) procedure, you can enable the verification by omitting the `.verify.secretRef` field. To verify the identity's subject and the OIDC issuer present in the Fulcio diff --git a/docs/spec/v1beta2/buckets.md b/docs/spec/v1beta2/buckets.md index a78516f88..6aa09053f 100644 --- a/docs/spec/v1beta2/buckets.md +++ b/docs/spec/v1beta2/buckets.md @@ -141,7 +141,7 @@ attempt to communicate with the specified [Endpoint](#endpoint) using the [Minio Client SDK](https://github.com/minio/minio-go), which can communicate with any Amazon S3 compatible object storage (including [GCS](https://cloud.google.com/storage/docs/interoperability), -[Wasabi](https://wasabi-support.zendesk.com/hc/en-us/articles/360002079671-How-do-I-use-Minio-Client-with-Wasabi-), +[Wasabi](https://docs.wasabi.com/docs/how-do-i-use-minio-client-with-wasabi), and many others). The `generic` Provider _requires_ a [Secret reference](#secret-reference) to a diff --git a/docs/spec/v1beta2/helmcharts.md b/docs/spec/v1beta2/helmcharts.md index 3932a9694..051091591 100644 --- a/docs/spec/v1beta2/helmcharts.md +++ b/docs/spec/v1beta2/helmcharts.md @@ -274,7 +274,7 @@ signatures. The field offers three subfields: #### Cosign -The `cosign` provider can be used to verify the signature of an OCI artifact using either a known public key or via the [Cosign Keyless](https://github.com/sigstore/cosign/blob/main/KEYLESS.md) procedure. +The `cosign` provider can be used to verify the signature of an OCI artifact using either a known public key or via the [Cosign Keyless](https://docs.sigstore.dev/cosign/signing/overview/) procedure. ```yaml --- @@ -321,7 +321,7 @@ This allows for older HelmCharts to be valid as long as the right key is in the ##### Keyless verification For publicly available HelmCharts, which are signed using the -[Cosign Keyless](https://github.com/sigstore/cosign/blob/main/KEYLESS.md) procedure, +[Cosign Keyless](https://docs.sigstore.dev/cosign/signing/overview/) procedure, you can enable the verification by omitting the `.verify.secretRef` field. To verify the identity's subject and the OIDC issuer present in the Fulcio diff --git a/docs/spec/v1beta2/ocirepositories.md b/docs/spec/v1beta2/ocirepositories.md index eb5de4c5f..299a4010d 100644 --- a/docs/spec/v1beta2/ocirepositories.md +++ b/docs/spec/v1beta2/ocirepositories.md @@ -552,7 +552,7 @@ signatures. The field offers three subfields: #### Cosign The `cosign` provider can be used to verify the signature of an OCI artifact using either a known public key -or via the [Cosign Keyless](https://github.com/sigstore/cosign/blob/main/KEYLESS.md) procedure. +or via the [Cosign Keyless](https://docs.sigstore.dev/cosign/signing/overview/) procedure. ```yaml --- @@ -599,7 +599,7 @@ This allows for older artifacts to be valid as long as the right key is in the s ##### Keyless verification For publicly available OCI artifacts, which are signed using the -[Cosign Keyless](https://github.com/sigstore/cosign/blob/main/KEYLESS.md) procedure, +[Cosign Keyless](https://docs.sigstore.dev/cosign/signing/overview/) procedure, you can enable the verification by omitting the `.verify.secretRef` field. To verify the identity's subject and the OIDC issuer present in the Fulcio