From b6eb42a59b2bbb50def8ba3ddb125761a5347cae Mon Sep 17 00:00:00 2001 From: Hemil K Date: Thu, 19 Sep 2024 13:49:37 -0700 Subject: [PATCH] Update README.md Signed-off-by: Hemil K --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 9c8ec5ba8ac..f4ceb7716ad 100644 --- a/README.md +++ b/README.md @@ -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 @@ -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 @@ -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 @@ -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