Skip to content

Conversation

@pull
Copy link

@pull pull bot commented Aug 5, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.3)

Can you help keep this open source service alive? 💖 Please sponsor : )

Previously, when --check-claims was set to false and a bundle in the new
format was provided, we'd still try to check the in-toto subject digest
and algorithm. These values weren't being set since they were
conditioned on checking claims. Now, we skip digest verification if
check-claims is false with a new bundle.

Signed-off-by: Hayden B <[email protected]>
@pull pull bot locked and limited conversation to collaborators Aug 5, 2025
@pull pull bot added the ⤵️ pull label Aug 5, 2025
dependabot bot and others added 27 commits August 5, 2025 15:18
Also needed to bump grpc-gcp-go to fix an incompatibility with the
latest googleapis library

Signed-off-by: Hayden B <[email protected]>
Bumps [google.golang.org/api](https://github.com/googleapis/google-api-go-client) from 0.243.0 to 0.244.0.
- [Release notes](https://github.com/googleapis/google-api-go-client/releases)
- [Changelog](https://github.com/googleapis/google-api-go-client/blob/main/CHANGES.md)
- [Commits](googleapis/google-api-go-client@v0.243.0...v0.244.0)

---
updated-dependencies:
- dependency-name: google.golang.org/api
  dependency-version: 0.244.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…r v2 (#4319)

* Refactor fetching an ID token into its own package

This will allow these functions to be reused by other parts of the
codebase, and eventually we can move these into an external package for
use by other libraries.

Signed-off-by: Hayden B <[email protected]>

* Add support for SigningConfig for sign-blob/attest-blob

Signed-off-by: Hayden B <[email protected]>

* Refactor identity token retrieval into its own method

Signed-off-by: Hayden B <[email protected]>

* Disallow self-managed keys with a signing config temporarily

Signed-off-by: Hayden B <[email protected]>

---------

Signed-off-by: Hayden B <[email protected]>
Co-authored-by: Hayden B <[email protected]>
---------

Signed-off-by: Zach Steindler <[email protected]>
Bumps [actions/checkout](https://github.com/actions/checkout) from 4.2.2 to 5.0.0.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](actions/checkout@11bd719...08c6903)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-version: 5.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps the actions group with 3 updates: [actions/cache](https://github.com/actions/cache), [sigstore/sigstore-conformance](https://github.com/sigstore/sigstore-conformance) and [chainguard-dev/actions](https://github.com/chainguard-dev/actions).


Updates `actions/cache` from 4.2.3 to 4.2.4
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](actions/cache@5a3ec84...0400d5f)

Updates `sigstore/sigstore-conformance` from 0.0.18 to 0.0.19
- [Release notes](https://github.com/sigstore/sigstore-conformance/releases)
- [Commits](sigstore/sigstore-conformance@fd90e6b...a7ac671)

Updates `chainguard-dev/actions` from 1.4.8 to 1.4.9
- [Release notes](https://github.com/chainguard-dev/actions/releases)
- [Changelog](https://github.com/chainguard-dev/actions/blob/main/.goreleaser.yml)
- [Commits](chainguard-dev/actions@df684a7...b1933e3)

---
updated-dependencies:
- dependency-name: actions/cache
  dependency-version: 4.2.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
- dependency-name: sigstore/sigstore-conformance
  dependency-version: 0.0.19
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
- dependency-name: chainguard-dev/actions
  dependency-version: 1.4.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [github.com/sigstore/sigstore-go](https://github.com/sigstore/sigstore-go) from 1.1.1-0.20250801180901-37e45ae9c250 to 1.1.1.
- [Release notes](https://github.com/sigstore/sigstore-go/releases)
- [Commits](https://github.com/sigstore/sigstore-go/commits/v1.1.1)

---
updated-dependencies:
- dependency-name: github.com/sigstore/sigstore-go
  dependency-version: 1.1.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps the gomod group with 4 updates: cuelang.org/go, [github.com/buildkite/agent/v3](https://github.com/buildkite/agent), google.golang.org/protobuf and [sigs.k8s.io/release-utils](https://github.com/kubernetes-sigs/release-utils).


Updates `cuelang.org/go` from 0.14.0 to 0.14.1

Updates `github.com/buildkite/agent/v3` from 3.103.0 to 3.103.1
- [Release notes](https://github.com/buildkite/agent/releases)
- [Changelog](https://github.com/buildkite/agent/blob/main/CHANGELOG.md)
- [Commits](buildkite/agent@v3.103.0...v3.103.1)

Updates `google.golang.org/protobuf` from 1.36.6 to 1.36.7

Updates `sigs.k8s.io/release-utils` from 0.12.0 to 0.12.1
- [Release notes](https://github.com/kubernetes-sigs/release-utils/releases)
- [Commits](kubernetes-sigs/release-utils@v0.12.0...v0.12.1)

---
updated-dependencies:
- dependency-name: cuelang.org/go
  dependency-version: 0.14.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gomod
- dependency-name: github.com/buildkite/agent/v3
  dependency-version: 3.103.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gomod
- dependency-name: google.golang.org/protobuf
  dependency-version: 1.36.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gomod
- dependency-name: sigs.k8s.io/release-utils
  dependency-version: 0.12.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gomod
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.40.0 to 0.41.0.
- [Commits](golang/crypto@v0.40.0...v0.41.0)

---
updated-dependencies:
- dependency-name: golang.org/x/crypto
  dependency-version: 0.41.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…4341)

Bumps [github.com/go-jose/go-jose/v4](https://github.com/go-jose/go-jose) from 4.0.5 to 4.1.2.
- [Release notes](https://github.com/go-jose/go-jose/releases)
- [Commits](go-jose/go-jose@v4.0.5...v4.1.2)

---
updated-dependencies:
- dependency-name: github.com/go-jose/go-jose/v4
  dependency-version: 4.1.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Fixes to cosign sign / verify for the new bundle format

Signed-off-by: Zach Steindler <[email protected]>

* Update function signature to pass crypto.PublicKey directly

Signed-off-by: Zach Steindler <[email protected]>

---------

Signed-off-by: Zach Steindler <[email protected]>
This supports signing and verification with Rekor v2 with a
user-provided signing key. Timestamps will only be required for
verifying Fulcio certificates.

Signed-off-by: Hayden B <[email protected]>
Co-authored-by: Hayden B <[email protected]>
That way cosign verify-attestation can work in offline environments.

Signed-off-by: Zach Steindler <[email protected]>
Bumps [google.golang.org/api](https://github.com/googleapis/google-api-go-client) from 0.246.0 to 0.247.0.
- [Release notes](https://github.com/googleapis/google-api-go-client/releases)
- [Changelog](https://github.com/googleapis/google-api-go-client/blob/main/CHANGES.md)
- [Commits](googleapis/google-api-go-client@v0.246.0...v0.247.0)

---
updated-dependencies:
- dependency-name: google.golang.org/api
  dependency-version: 0.247.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [gitlab.com/gitlab-org/api/client-go](https://gitlab.com/gitlab-org/api/client-go) from 0.137.0 to 0.140.0.
- [Release notes](https://gitlab.com/gitlab-org/api/client-go/tags)
- [Changelog](https://gitlab.com/gitlab-org/api/client-go/blob/main/CHANGELOG.md)
- [Commits](https://gitlab.com/gitlab-org/api/client-go/compare/v0.137.0...v0.140.0)

---
updated-dependencies:
- dependency-name: gitlab.com/gitlab-org/api/client-go
  dependency-version: 0.140.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
One of the dependencies has hardcoded a specific version of go, which
forces all clients to use that version of Go in their own modules. This
is unnecessarily restrictive, rather libraries should specify the
minimum Go version necessary to build, and consumers should use the
latest patch release when building to pick up bug fixes.

Signed-off-by: Hayden B <[email protected]>
Bumps the actions group with 1 update: [chainguard-dev/actions](https://github.com/chainguard-dev/actions).


Updates `chainguard-dev/actions` from 1.4.9 to 1.4.10
- [Release notes](https://github.com/chainguard-dev/actions/releases)
- [Changelog](https://github.com/chainguard-dev/actions/blob/main/.goreleaser.yml)
- [Commits](chainguard-dev/actions@b1933e3...1df2b55)

---
updated-dependencies:
- dependency-name: chainguard-dev/actions
  dependency-version: 1.4.10
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: actions
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps the gomod group with 4 updates: [github.com/sigstore/rekor-tiles](https://github.com/sigstore/rekor-tiles), [k8s.io/api](https://github.com/kubernetes/api), [k8s.io/apimachinery](https://github.com/kubernetes/apimachinery) and [k8s.io/client-go](https://github.com/kubernetes/client-go).


Updates `github.com/sigstore/rekor-tiles` from 0.1.7-0.20250624231741-98cd4a77300f to 0.1.9
- [Release notes](https://github.com/sigstore/rekor-tiles/releases)
- [Changelog](https://github.com/sigstore/rekor-tiles/blob/main/Dockerfile.release)
- [Commits](https://github.com/sigstore/rekor-tiles/commits/v0.1.9)

Updates `k8s.io/api` from 0.33.3 to 0.33.4
- [Commits](kubernetes/api@v0.33.3...v0.33.4)

Updates `k8s.io/apimachinery` from 0.33.3 to 0.33.4
- [Commits](kubernetes/apimachinery@v0.33.3...v0.33.4)

Updates `k8s.io/client-go` from 0.33.3 to 0.33.4
- [Changelog](https://github.com/kubernetes/client-go/blob/master/CHANGELOG.md)
- [Commits](kubernetes/client-go@v0.33.3...v0.33.4)

---
updated-dependencies:
- dependency-name: github.com/sigstore/rekor-tiles
  dependency-version: 0.1.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gomod
- dependency-name: k8s.io/api
  dependency-version: 0.33.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gomod
- dependency-name: k8s.io/apimachinery
  dependency-version: 0.33.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gomod
- dependency-name: k8s.io/client-go
  dependency-version: 0.33.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gomod
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [github.com/go-viper/mapstructure/v2](https://github.com/go-viper/mapstructure) from 2.3.0 to 2.4.0.
- [Release notes](https://github.com/go-viper/mapstructure/releases)
- [Changelog](https://github.com/go-viper/mapstructure/blob/main/CHANGELOG.md)
- [Commits](go-viper/mapstructure@v2.3.0...v2.4.0)

---
updated-dependencies:
- dependency-name: github.com/go-viper/mapstructure/v2
  dependency-version: 2.4.0
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
#4365)

Bumps [github.com/buildkite/agent/v3](https://github.com/buildkite/agent) from 3.98.2 to 3.103.1.
- [Release notes](https://github.com/buildkite/agent/releases)
- [Changelog](https://github.com/buildkite/agent/blob/main/CHANGELOG.md)
- [Commits](buildkite/agent@v3.98.2...v3.103.1)

---
updated-dependencies:
- dependency-name: github.com/buildkite/agent/v3
  dependency-version: 3.103.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps the gomod group with 1 update: google.golang.org/protobuf.


Updates `google.golang.org/protobuf` from 1.36.7 to 1.36.8

---
updated-dependencies:
- dependency-name: google.golang.org/protobuf
  dependency-version: 1.36.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gomod
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
bobcallaway and others added 30 commits January 6, 2026 07:58
Reuse the digest obtained from SignedEntity instead of re-resolving it
in subsequent calls to AttestationTag, SignatureTag, SBOMTag, and
Referrers. This eliminates redundant manifest fetches and improves
performance

Signed-off-by: Bob Callaway <[email protected]>
Bumps the gomod group with 1 update: cuelang.org/go.


Updates `cuelang.org/go` from 0.15.1 to 0.15.3

---
updated-dependencies:
- dependency-name: cuelang.org/go
  dependency-version: 0.15.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gomod
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [gitlab.com/gitlab-org/api/client-go](https://gitlab.com/gitlab-org/api/client-go) from 1.10.0 to 1.11.0.
- [Release notes](https://gitlab.com/gitlab-org/api/client-go/tags)
- [Changelog](https://gitlab.com/gitlab-org/api/client-go/blob/main/CHANGELOG.md)
- [Commits](https://gitlab.com/gitlab-org/api/client-go/compare/v1.10.0...v1.11.0)

---
updated-dependencies:
- dependency-name: gitlab.com/gitlab-org/api/client-go
  dependency-version: 1.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Ensure the bundle signature and key are compared to the rekor entry
every time, not just when trusted root is used. Sigstore-go's VerifySET
does not do this full comparison, we'd need to go through one of the
more comprehensive Verify* functions to get this level of verification
from the library.

Signed-off-by: Colleen Murphy <[email protected]>
Signed-off-by: Hayden <[email protected]>
Co-authored-by: Colleen Murphy <[email protected]>
Static CT, like Rekor v2, needs the origin string of the log server to
create a verifier, so include it when generating the trusted root.

Signed-off-by: Colleen Murphy <[email protected]>
Bumps [github.com/sigstore/fulcio](https://github.com/sigstore/fulcio) from 1.8.4 to 1.8.5.
- [Release notes](https://github.com/sigstore/fulcio/releases)
- [Changelog](https://github.com/sigstore/fulcio/blob/main/CHANGELOG.md)
- [Commits](sigstore/fulcio@v1.8.4...v1.8.5)

---
updated-dependencies:
- dependency-name: github.com/sigstore/fulcio
  dependency-version: 1.8.5
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Add a short note to VerifyRFC3161Timestamp clarifying that RFC3161 timestamp verification does not perform CRL/OCSP revocation checks, and that Sigstore's default workflow relies on TUF-distributed trust material + validity metadata for revocation.

Signed-off-by: konkoleg <[email protected]>
Signed-off-by: Colleen Murphy <[email protected]>
Bumps [github.com/sigstore/rekor](https://github.com/sigstore/rekor) from 1.4.3 to 1.5.0.
- [Release notes](https://github.com/sigstore/rekor/releases)
- [Changelog](https://github.com/sigstore/rekor/blob/main/CHANGELOG.md)
- [Commits](sigstore/rekor@v1.4.3...v1.5.0)

---
updated-dependencies:
- dependency-name: github.com/sigstore/rekor
  dependency-version: 1.5.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* fix: avoid panic on malformed replace payload

Signed-off-by: 1seal <[email protected]>

* test: cover missing payload in Replace

Signed-off-by: 1seal <[email protected]>

* test: add license header for replaceop test

Signed-off-by: 1seal <[email protected]>

* test: cover invalid base64 payload in Replace

Signed-off-by: 1seal <[email protected]>

* test: address review feedback for replaceop

Signed-off-by: 1seal <[email protected]>

---------

Signed-off-by: 1seal <[email protected]>
Previously, `VerifyBundle` assumed `bundle.Payload.Body` was always a
string and performed a direct type assertion. If the body was a different
type (e.g., due to a malformed bundle), this would cause a panic.

This change adds a check to safely assert the type of `bundle.Payload.Body`.

Signed-off-by: Hayden <[email protected]>
…4662)

Bumps the gomod group with 3 updates in the / directory: [github.com/buildkite/agent/v3](https://github.com/buildkite/agent), [github.com/miekg/pkcs11](https://github.com/miekg/pkcs11) and [github.com/open-policy-agent/opa](https://github.com/open-policy-agent/opa).


Updates `github.com/buildkite/agent/v3` from 3.115.2 to 3.115.4
- [Release notes](https://github.com/buildkite/agent/releases)
- [Changelog](https://github.com/buildkite/agent/blob/main/CHANGELOG.md)
- [Commits](buildkite/agent@v3.115.2...v3.115.4)

Updates `github.com/miekg/pkcs11` from 1.1.1 to 1.1.2
- [Changelog](https://github.com/miekg/pkcs11/blob/master/release.go)
- [Commits](miekg/pkcs11@v1.1.1...v1.1.2)

Updates `github.com/open-policy-agent/opa` from 1.12.1 to 1.12.3
- [Release notes](https://github.com/open-policy-agent/opa/releases)
- [Changelog](https://github.com/open-policy-agent/opa/blob/main/CHANGELOG.md)
- [Commits](open-policy-agent/opa@v1.12.1...v1.12.3)

---
updated-dependencies:
- dependency-name: github.com/buildkite/agent/v3
  dependency-version: 3.115.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gomod
- dependency-name: github.com/miekg/pkcs11
  dependency-version: 1.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gomod
- dependency-name: github.com/open-policy-agent/opa
  dependency-version: 1.12.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: gomod
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…#4626)

* Allow --local-image with --new-bundle-format for v2 signatures

Remove the mutual exclusivity constraint between --local-image and
--new-bundle-format flags in verify and verify-attestation commands.
This enables verification of v2-signed images saved as local OCI layouts
when using cosign v3.

Add HasLocalBundles() function that auto-detects the signature format
by checking for dev.sigstore.cosign/bundle annotations in the local
OCI layout. If no bundles are found (v2 attached signatures), the
verification falls back to v2 mode automatically.

This mirrors the existing auto-detection pattern used for registry-based
verification via GetBundles().

Signed-off-by: Tuomo Tanskanen <[email protected]>

* Add tests for local image format auto-detection

Add unit tests for HasLocalBundles() and HasLocalAttestationBundles()
functions covering v2 signatures, v3 bundles, and edge cases.

Add e2e test TestSaveLoadAutoDetectFormat to verify the auto-detection
works correctly for both v2 attached signatures and v3 bundles.

Signed-off-by: Tuomo Tanskanen <[email protected]>

* Enable full local verification of v3 sigstore bundles

Add GetLocalBundles() and verifyLocalImageAttestationsSigstoreBundle()
to support verifying v3 bundles directly from local OCI layouts.

Refactors hasLocalSigstoreBundles() to getLocalBundleDescriptors() for
reuse, and updates VerifyLocalImageAttestations() to use the new v3
verification path when NewBundleFormat is true.

Signed-off-by: Tuomo Tanskanen <[email protected]>

* Add tests for local v3 bundle verification

Add unit tests for GetLocalBundles() covering valid layouts, missing
blobs, and error cases. Update e2e test to verify v3 bundles directly
from local OCI layout without registry round-trip.

Signed-off-by: Tuomo Tanskanen <[email protected]>

---------

Signed-off-by: Tuomo Tanskanen <[email protected]>
There was an assumption that a certificate would be issued during the
validity period of all certificates in its chain. If a certificate was
issued such that its NotAfter timestamp was past the NotAfter of another
certificate in the chain, that would have not been detected. This is
because during verification, we use the leaf certificate's NotBefore
timestamp to verify the chain's validity, but check only the leaf
certificate's validity against any provided timestamps (either from the
Rekor timestamp, a signed timestamp, or the current time).

This scenario is not expected with a typical chain since a CA shouldn't
issue a certificate that outlives an issuer.

This change enforces that the entire chain is valid at any of those
provided timestamps.

Signed-off-by: Hayden <[email protected]>
* fix: avoid panic on malformed tlog entry body

Signed-off-by: 1seal <[email protected]>

# Conflicts:
#	pkg/cosign/tlog_test.go

# Please enter the commit message for your changes. Lines starting
# with '#' will be kept; you may remove them yourself if you want to.
# An empty message aborts the commit.
#
# interactive rebase in progress; onto 806d06c
# Last command done (1 command done):
#    pick 51c102e # fix: avoid panic on malformed tlog entry body
# Next command to do (1 remaining command):
#    pick 3fc4def # test: adjust ComputeLeafHash coverage
# You are currently rebasing branch 'fix/no-panic-computeleafhash-body' on '806d06c'.
#
# Changes to be committed:
#	modified:   pkg/cosign/tlog.go
#	modified:   pkg/cosign/tlog_test.go
#

* test: adjust ComputeLeafHash coverage

Signed-off-by: 1seal <[email protected]>

---------

Signed-off-by: 1seal <[email protected]>
https://github.com/sigstore/cosign/actions/runs/21301111439 shows a syntax error with the currently escaped `[`. This updates the xfail to match what's in sigstore-go, and updates the nightly test as well.

Signed-off-by: Hayden <[email protected]>
Currently, when verifying a bundle with a short-lived certificate and a
Rekor v2 entry, users must specify --use-signed-timestamps and provide a
signed timestamp, because Rekor v2 entries do not contain integrated
timestamps unlike Rekor v1. This isn't a great UX.

This change opportunistically sets --use-signed-timestamps when we
detect that a user is verifying a short-lived certificate with a Rekor
v2 entry. We won't automatically set this with a mixed Rekor v1 and
Rekor v2 bundle (which the tooling will not produce, this would be for
any custom clients) or when verifying with a managed key.

Fixes #4500

Signed-off-by: Hayden <[email protected]>
Bumps the all group with 1 update: golang.


Updates `golang` from 1.25.5 to 1.25.6

---
updated-dependencies:
- dependency-name: golang
  dependency-version: 1.25.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: all
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [github.com/theupdateframework/go-tuf/v2](https://github.com/theupdateframework/go-tuf) from 2.3.0 to 2.4.1.
- [Release notes](https://github.com/theupdateframework/go-tuf/releases)
- [Commits](theupdateframework/go-tuf@v2.3.0...v2.4.1)

---
updated-dependencies:
- dependency-name: github.com/theupdateframework/go-tuf/v2
  dependency-version: 2.4.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
When using Rekor v2, the log entry does not provide a Signed Entry Timestamp
that validates the time of inclusion. For keyless signing with short-lived certificates,
a trusted timestamp is required to verify the certificate was valid at the time of signing.

This change updates the new sign path to enforce that a timestamp authority is configured when
Rekor v2 is to be used with Fulcio and no TSA URL is provided.

This should not affect users signing using the public instance, since
the signing configuration includes a public TSA.

Signed-off-by: Hayden <[email protected]>
Signed-off-by: Zach Steindler <[email protected]>
---------

Signed-off-by: Zach Steindler <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.