[red-hat-konflux]

This PR contains the following updates:

Package	Type	Update	Change
sigstore/cosign	uses-with	minor	v2.2.4 → v2.6.5

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

sigstore/cosign (sigstore/cosign)

v2.6.5

Compare Source

Changelog

This release backports GHSA-fx35-mq7g-6g98 (Verification bypass via public key in legacy bundle) to Cosign v2.6.x.

We strongly encourage folks to continue their migration to the bundle format. The Cosign v3.1.x releases support both formats; the primary change being that the default for signing is the bundle format (although you can specify --new-bundle-format=false to sign with the old format). The verification commands in Cosign v3.1.x support both formats, and will try to detect the format for you for maximum compatibility.

Thanks to all contributors!

v2.6.4

Compare Source

This release is a backport of OCI manifest fixes, and better support for cosign attestation download when you are using a mix of old Cosign signatures with the more recent bundle format.

We strongly encourage folks to continue their migration to the bundle format. The Cosign v3.1.x releases support both formats; the primary change being that the default for signing is the bundle format (although you can specify --new-bundle-format=false to sign with the old format). The verification commands in Cosign v3.1.x support both formats, and will try to detect the format for you for maximum compatibility.

Changelog

• 26261f0 Allow attestation download to handle both bundle types (#​4996) (#​5017)
• d49a0c1 fix: include artifactType in OCI 1.1 signature referrer manifest (cherry-pick PR-4997 to release-2.6) (#​5002)

Thanks to all contributors!

v2.6.3

Compare Source

Changelog

v2.6.3 resolves GHSA-w6c6-c85g-mmv6.

• fecddd3 Fix DSSE predicate check (#​4802)
• 564c5b1 Backport bundle detection to sign and attest (#​4727)

Thanks to all contributors!

v2.6.2

Compare Source

v2.6.2 resolves GHSA-whqx-f9j3-ch6m.

Changes

• Fix bundle verify path for old bundle/trusted root (GHSA-whqx-f9j3-ch6m) (#​4624)
• bump sigstore deps to resolve build errors (#​4619)

v2.6.1

Compare Source

Bug Fixes

• Partially populate the output of cosign verify when working with new bundles (#​4416)
• Bump sigstore-go, move conformance back to tagged release (#​4426)

v2.6.0

Compare Source

v2.6.0 introduces a number of new features, including:

• Signing an in-toto statement rather than Cosign constructing one from a predicate, along with verifying a statement's subject using a digest and digest algorithm rather than providing a file reference (#​4306)
• Uploading a signature and its verification material (a "bundle") as an OCI Image 1.1 referring artifact, completing #​3927 (#​4316)
• Providing service URLs for signing and attesting using a SigningConfig. Note that this is required when using a Rekor v2 instance (#​4319)

Example generation and verification of a signed in-toto statement:

cosign attest-blob --new-bundle-format=true --bundle="digest-key-test.sigstore.json" --key="cosign.key" --statement="../sigstore-go/examples/sigstore-go-signing/intoto.txt"
cosign verify-blob-attestation --bundle="digest-key-test.sigstore.json" --key=cosign.pub --type=unused --digest="b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9" --digestAlg="sha256"

Example container signing and verification using the new bundle format and referring artifacts:

cosign sign --new-bundle-format=true ghcr.io/user/alpine@sha256:a19367999603840546b8612572e338ec076c6d1f2fec61760a9e11410f546733
cosign verify --new-bundle-format=true ghcr.io/user/alpine@sha256:a19367999603840546b8612572e338ec076c6d1f2fec61760a9e11410f546733

Example usage of a signing config provided by the public good instance's TUF repository:

cosign sign-blob --use-signing-config --bundle sigstore.json README.md
cosign verify-blob --new-bundle-format --bundle sigstore.json --certificate-identity $EMAIL --certificate-oidc-issuer $ISSUER --use-signed-timestamps README.md

v2.6.0 leverages sigstore-go's signing and verification APIs gated behind these new flags. In an upcoming major release, we will be
updating Cosign to default to producing and consuming bundles to align with all other Sigstore SDKs.

Features

• Add to attest-blob the ability to supply a complete in-toto statement, and add to verify-blob-attestation the ability to verify with just a digest (#​4306)
• Have cosign sign support bundle format (#​4316)
• Add support for SigningConfig for sign-blob/attest-blob, support Rekor v2 (#​4319)
• Add support for SigningConfig in sign/attest (#​4371)
• Support self-managed keys when signing with sigstore-go (#​4368)
• Don't require timestamps when verifying with a key (#​4337)
• Don't load content from TUF if trusted root path is specified (#​4347)
• Add a terminal spinner while signing with sigstore-go (#​4402)
• Require exclusively a SigningConfig or service URLs when signing (#​4403)
• Remove SHA256 assumption in sign-blob/verify-blob (#​4050)
• Bump sigstore-go, support alternative hash algorithms with keys (#​4386)

Breaking API Changes

• sign.SignerFromKeyOpts no longer generates a key. Instead, it returns whether or not the client needs to generate a key, and if so, clients
  should call sign.KeylessSigner. This allows clients to more easily manage key generation.

Bug Fixes

• Verify subject with bundle only when checking claims (#​4320)
• Fixes to cosign sign / verify for the new bundle format (#​4346)

v2.5.3

Compare Source

Features

• Add signing-config create command (#​4280)
• Allow multiple services to be specified for trusted-root create (#​4285)
• feat: Add OCI 1.1+ experimental support to tree (#​4205)
• Add validity period end for trusted-root create (#​4271)

Bug Fixes

• Fix cert verification logic for trusted-root/SCTs (#​4294)
• force when copying the latest image to overwrite (#​4298)
• avoid double-loading trustedroot from file (#​4264)

v2.5.2

Compare Source

Bug Fixes

• Do not load trusted root when CT env key is set

Documentation

• docs: improve doc for --no-upload option (#​4206)

v2.5.1

Compare Source

Features

• Add Rekor v2 support for trusted-root create (#​4242)
• Add baseUrl and Uri to trusted-root create command
• Upgrade to TUF v2 client with trusted root
• Don't verify SCT for a private PKI cert (#​4225)
• Bump TSA library to relax EKU chain validation rules (#​4219)

Bug Fixes

• Bump sigstore-go to pick up log index=0 fix (#​4162)
• remove unused recursive flag on attest command (#​4187)

Docs

• Fix indentation in verify-blob cmd examples (#​4160)

Releases

• ensure we copy the latest tags on each release (#​4157)

Contributors

• arthurus-rex
• Babak K. Shandiz
• Bob Callaway
• Carlos Tadeu Panato Junior
• Colleen Murphy
• Dmitry Savintsev
• Emmanuel Ferdman
• Hayden B
• Ville Skyttä

v2.5.0

Compare Source

v2.5.0 includes an implementation of the new bundle specification,
attesting and verifying OCI image attestations uploaded as OCI artifacts.
This feature is currently gated behind the --new-bundle-format flag
when running cosign attest.

Features

• Add support for new bundle specification for attesting/verifying OCI image attestations (#​3889)
• Feat/non filename completions (#​4115)
• Add TSA certificate related flags and fields for cosign attest (#​4079)

Fixes

• cmd/cosign/cli: fix typo in ignoreTLogMessage (#​4111)
• Fix replace with compliant image mediatype (#​4077)

Contributors

• Bob Callaway
• Carlos Tadeu Panato Junior
• Cody Soyland
• Dmitry Savintsev
• Hayden B
• Ramon Petgrave
• Riccardo Schirone
• Stef Graces
• Ville Skyttä

v2.4.3

Compare Source

Features

• Bump sigstore/sigstore to support KMS plugins (#​4073)
• Enable fetching signatures without remote get. (#​4047)
• Feat/file flag completion improvements (#​4028)
• Update builder to use go1.23.6 (#​4052)

Bug Fixes

• fix parsing error in --only for cosign copy (#​4049)

Cleanup

• Refactor verifyNewBundle into library function (#​4013)
• fix comment typo and imports order (#​4061)
• sync comment with parameter name in function signature (#​4063)
• sort properly Go imports (#​4071)

Contributors

• Bob Callaway
• Carlos Tadeu Panato Junior
• Cody Soyland
• Dmitry Savintsev
• Hayden B
• Tomasz Janiszewski
• Ville Skyttä

v2.4.2

Compare Source

Features

• Updated open-policy-agent to 1.1.0 library (#​4036)
  • Note that only Rego v0 policies are supported at this time
• Add UseSignedTimestamps to CheckOpts, refactor TSA options (#​4006)
• Add support for verifying root checksum in cosign initialize (#​3953)
• Detect if user supplied a valid protobuf bundle (#​3931)
• Add a log message if user doesn't provide --trusted-root (#​3933)
• Support mTLS towards container registry (#​3922)
• Add bundle create helper command (#​3901)
• Add trusted-root create helper command (#​3876)

Bug Fixes

• fix: set tls config while retaining other fields from default http transport (#​4007)
• policy fuzzer: ignore known panics (#​3993)
• Fix for multiple WithRemote options (#​3982)
• Add nightly conformance test workflow (#​3979)
• Fix copy --only for signatures + update/align docs (#​3904)

Documentation

• Remove usage.md from spec, point to client spec (#​3918)
• move reference from gcr to ghcr (#​3897)

Contributors

• AdamKorcz
• Aditya Sirish
• Bob Callaway
• Carlos Tadeu Panato Junior
• Cody Soyland
• Colleen Murphy
• Hayden B
• Jussi Kukkonen
• Marco Franssen
• Nianyu Shen
• Slavek Kabrda
• Søren Juul
• Warren Hodgkinson
• Zach Steindler

v2.4.1

Compare Source

v2.4.1 largely contains bug fixes and updates dependencies.

Features

• Added fuzzing coverage to multiple packages

Bug Fixes

• Fix bug in attest-blob when using a timestamp authority with new bundles (#​3877)
• fix: documentation link for installation guide (#​3884)

Contributors

• AdamKorcz
• Bob Callaway
• Carlos Tadeu Panato Junior
• Hayden B
• Hemil K
• Sota Sugiura
• Zach Steindler

v2.4.0

Compare Source

v2.4.0 begins the modernization of the Cosign client, which includes:

• Support for the newer Sigstore specification-compliant bundle format
• Support for providing trust roots (e.g. Fulcio certificates, Rekor keys)
  through a trust root file, instead of many different flags
• Conformance test suite integration to verify signing and verification behavior

In future updates, we'll include:

• General support for the trust root file, instead of only when using the bundle
  format during verification
• Simplification of trust root flags and deprecation of the
  Cosign-specific bundle format
• Bundle support with container signing

We have also moved nightly Cosign container builds to GHCR instead of GCR.

Features

• Add new bundle support to verify-blob and verify-blob-attestation (#​3796)
• Adding protobuf bundle support to sign-blob and attest-blob (#​3752)
• Bump sigstore/sigstore to support email_verified as string or boolean (#​3819)
• Conformance testing for cosign (#​3806)
• move incremental builds per commit to GHCR instead of GCR (#​3808)
• Add support for recording creation timestamp for cosign attest (#​3797)
• Include SCT verification failure details in error message (#​3799)

Contributors

• Bob Callaway
• Hayden B
• Slavek Kabrda
• Zach Steindler
• Zsolt Horvath

v2.3.0

Compare Source

Features

• Add PayloadProvider interface to decouple AttestationToPayloadJSON from oci.Signature interface (#​3693)
• add registry options to cosign save (#​3645)
• Add debug providers command. (#​3728)
• Make config layers in ociremote mountable (#​3741)
• upgrade to go1.22 (#​3739)
• adds tsa cert chain check for env var or tuf targets. (#​3600)
• add --ca-roots and --ca-intermediates flags to 'cosign verify' (#​3464)
• add handling of keyless verification for all verify commands (#​3761)

Bug Fixes

• fix: close attestationFile (#​3679)
• Set bundleVerified to true after Rekor verification (Resolves #​3740) (#​3745)

Documentation

• Document ImportKeyPair and LoadPrivateKey functions in pkg/cosign (#​3776)

Testing

• Refactor KMS E2E tests (#​3684)
• Remove sign_blob_test.sh test (#​3707)
• Remove KMS E2E test script (#​3702)
• Refactor insecure registry E2E tests (#​3701)

Contributors

• Billy Lynch
• bminahan73
• Bob Callaway
• Carlos Tadeu Panato Junior
• Cody Soyland
• Colleen Murphy
• Dmitry Savintsev
• guangwu
• Hayden B
• Hector Fernandez
• ian hundere
• Jason Power
• Jon Johnson
• Max Lambrecht
• Meeki1l

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux[bot]
Once this PR has been reviewed and has the lgtm label, please assign darkdoc for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a validatedpatterns member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.