From f938dc2f6e5ccef39f30ab3934b59b379fbe41fd Mon Sep 17 00:00:00 2001 From: Radoslav Dimitrov Date: Sun, 3 Dec 2023 18:53:11 +0200 Subject: [PATCH] Update docs/oci-image-verification.md Co-authored-by: Fredrik Skogman Signed-off-by: Radoslav Dimitrov --- docs/oci-image-verification.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/oci-image-verification.md b/docs/oci-image-verification.md index 11b4e82c..799ccd80 100644 --- a/docs/oci-image-verification.md +++ b/docs/oci-image-verification.md @@ -30,7 +30,10 @@ In this example, we'll use the `sigstore-go` CLI to verify an OCI image referenc The image we are going to verify is `ghcr.io/stacklok/minder/server:latest` ```shell -sigstore-go --ociImage="ghcr.io/stacklok/minder/server:latest" --tufRootURL="tuf-repo-cdn.sigstore.dev" --expectedSANRegex="^https://github.com/stacklok/minder/" --expectedIssuer="https://token.actions.githubusercontent.com" +$ sigstore-go --ociImage="ghcr.io/stacklok/minder/server:latest" \ + --tufRootURL="tuf-repo-cdn.sigstore.dev" \ + --expectedSANRegex="^https://github.com/stacklok/minder/" \ + --expectedIssuer="https://token.actions.githubusercontent.com" ``` Upon successful verification, the CLI will print the verification result in JSON format along with a `Verification successful!` message.