Skip to content
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

Jump to bottom

Update README.md to fix links #3886

Merged
merged 1 commit into from
Sep 20, 2024
Merged

Update README.md to fix links #3886

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
10 changes: 5 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ ENTRYPOINT [ "cosign" ]
## Quick Start

This shows how to:
* sign a container image with the default identity-based "keyless signing" method (see [the documentation for more information](https://docs.sigstore.dev/signing/overview/))
* sign a container image with the default identity-based "keyless signing" method (see [the documentation for more information](https://docs.sigstore.dev/cosign/signing/overview/))
* verify the container image

### Sign a container and store the signature in the registry
Expand Down Expand Up @@ -190,7 +190,7 @@ OCI registries are useful for storing more than just container images!

This section shows how to leverage these for an easy-to-use, backwards-compatible artifact distribution system that integrates well with the rest of Sigstore.

See [the documentation](https://docs.sigstore.dev/signing/other_types/) for more information.
See [the documentation](https://docs.sigstore.dev/cosign/signing/other_types/) for more information.

### Blobs

Expand Down Expand Up @@ -314,11 +314,11 @@ $ cosign verify-attestation --key cosign.pub $IMAGE_URI

## Detailed Usage

See the [Usage documentation](https://docs.sigstore.dev/signing/overview/) for more information.
See the [Usage documentation](https://docs.sigstore.dev/cosign/signing/overview/) for more information.

## Hardware-based Tokens

See the [Hardware Tokens documentation](https://docs.sigstore.dev/key_management/hardware-based-tokens/) for information on how to use `cosign` with hardware.
See the [Hardware Tokens documentation](https://docs.sigstore.dev/cosign/key_management/hardware-based-tokens/) for information on how to use `cosign` with hardware.

## Registry Support

Expand Down Expand Up @@ -492,7 +492,7 @@ The proposed mechanism is flexible enough to support signing arbitrary things.
`cosign` supports using a KMS provider to generate and sign keys.
Right now cosign supports Hashicorp Vault, AWS KMS, GCP KMS, Azure Key Vault and we are hoping to support more in the future!

See the [KMS docs](https://docs.sigstore.dev/key_management/overview/) for more details.
See the [KMS docs](https://docs.sigstore.dev/cosign/key_management/overview/) for more details.

### OCI Artifacts

Expand Down
Loading