Skip to content

Fix dead Cosign and Wasabi links in spec docs #2223

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sarankumar1325 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix dead Cosign and Wasabi links in spec docs #2223

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/spec/v1/buckets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions docs/spec/v1/helmcharts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
---
Expand Down Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions docs/spec/v1/ocirepositories.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
---
Expand Down Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion docs/spec/v1beta2/buckets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions docs/spec/v1beta2/helmcharts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
---
Expand Down Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions docs/spec/v1beta2/ocirepositories.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
---
Expand Down Expand Up @@ -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
Expand Down