Fix: Remove an extra registry request from verification path. #2285
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
imjasonh
previously approved these changes
Sep 27, 2022
mattmoor
force-pushed
the
eliminate-extra-fetch
branch
from
8da8416
to
7338646
Compare
Codecov Report
@@ Coverage Diff @@
## main #2285 +/- ##
==========================================
- Coverage 29.02% 29.00% -0.03%
==========================================
Files 131 131
Lines 7872 7878 +6
==========================================
Hits 2285 2285
- Misses 5275 5281 +6
Partials 312 312
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
mattmoor
commented
Sep 27, 2022
🐛 Remove an extra registry request when supplied with a digest.
The current logic calls `getSignedEntity` which must determine the media type of the referenced entity in order to produce an appropriately types `SignedEntity`. However, we are only interested in the attached signatures (or
attestations) and not the underlying structure, so when we are passed a digest, this roundtrip is entirely superfluous.
This changes this logic to explicitly resolve the digest (since verification wants to know the `v1.Hash`), which is free for digests. Then we explicitly invoke `ociremote.Signatures()` on one of
`ociremote.{Signature,Attestation}Tag`, which is also free (since we always pass the digest).
/kind bug
Signed-off-by: Matt Moore <mattmoor@chainguard.dev>
mattmoor
force-pushed
the
eliminate-extra-fetch
branch
from
7338646
to
25f75e0
Compare
dlorenc
approved these changes
Sep 27, 2022
jeff-mccoy
pushed a commit
to defenseunicorns/zarf
that referenced
this pull request
Oct 7, 2022
[](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [github.com/sigstore/cosign](https://togithub.com/sigstore/cosign) | require | minor | `v1.12.1` -> `v1.13.0` | --- ### Release Notes <details> <summary>sigstore/cosign</summary> ### [`v1.13.0`](https://togithub.com/sigstore/cosign/blob/HEAD/CHANGELOG.md#v1130) [Compare Source](https://togithub.com/sigstore/cosign/compare/v1.12.1...v1.13.0) > # Highlights > > - For users who have deployed a private instance of Fulcio release v0.6.x and issue certificates with the Username identity, you will need to upgrade to use this version." #### Enhancements - Add support for Fulcio username identity in SAN ([sigstore/cosign#2291) - Data race in FetchSignaturesForReference ([sigstore/cosign#2283) - Check error on chain verification failure ([sigstore/cosign#2284) - feat: improve the verification message ([sigstore/cosign#2268) - feat: use stdin as an input for predicate ([sigstore/cosign#2269) #### Bug Fixes - fix: make tlog entry lookups for online verification shard-aware ([sigstore/cosign#2297) - Fix: Create a static copy of signatures as part of verification. ([sigstore/cosign#2287) - Fix: Remove an extra registry request from verification path. ([sigstore/cosign#2285) - fix pivtool generate key touch policy ([sigstore/cosign#2282) #### Others - use scaffolding 0.4.8 for tests. ([sigstore/cosign#2280) #### Contributors - Asra Ali ([@​asraa](https://togithub.com/asraa)) - Batuhan Apaydın ([@​developer-guy](https://togithub.com/developer-guy)) - Carlos Tadeu Panato Junior ([@​cpanato](https://togithub.com/cpanato)) - Hayden Blauzvern ([@​haydentherapper](https://togithub.com/haydentherapper)) - Matt Moore ([@​mattmoor](https://togithub.com/mattmoor)) - Ross Tannenbaum ([@​RTann](https://togithub.com/RTann)) - Ville Aikas ([@​vaikas](https://togithub.com/vaikas)) </details> --- ### Configuration 📅 **Schedule**: 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, click this checkbox. --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/defenseunicorns/zarf). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzMi4yMjIuMyIsInVwZGF0ZWRJblZlciI6IjMyLjIyMi4zIn0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
](https://renovatebot.com){kind=link}
Noxsios
pushed a commit
to defenseunicorns/zarf
that referenced
this pull request
Mar 8, 2023
[](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [github.com/sigstore/cosign](https://togithub.com/sigstore/cosign) | require | minor | `v1.12.1` -> `v1.13.0` | --- ### Release Notes <details> <summary>sigstore/cosign</summary> ### [`v1.13.0`](https://togithub.com/sigstore/cosign/blob/HEAD/CHANGELOG.md#v1130) [Compare Source](https://togithub.com/sigstore/cosign/compare/v1.12.1...v1.13.0) > # Highlights > > - For users who have deployed a private instance of Fulcio release v0.6.x and issue certificates with the Username identity, you will need to upgrade to use this version." #### Enhancements - Add support for Fulcio username identity in SAN ([sigstore/cosign#2291) - Data race in FetchSignaturesForReference ([sigstore/cosign#2283) - Check error on chain verification failure ([sigstore/cosign#2284) - feat: improve the verification message ([sigstore/cosign#2268) - feat: use stdin as an input for predicate ([sigstore/cosign#2269) #### Bug Fixes - fix: make tlog entry lookups for online verification shard-aware ([sigstore/cosign#2297) - Fix: Create a static copy of signatures as part of verification. ([sigstore/cosign#2287) - Fix: Remove an extra registry request from verification path. ([sigstore/cosign#2285) - fix pivtool generate key touch policy ([sigstore/cosign#2282) #### Others - use scaffolding 0.4.8 for tests. ([sigstore/cosign#2280) #### Contributors - Asra Ali ([@​asraa](https://togithub.com/asraa)) - Batuhan Apaydın ([@​developer-guy](https://togithub.com/developer-guy)) - Carlos Tadeu Panato Junior ([@​cpanato](https://togithub.com/cpanato)) - Hayden Blauzvern ([@​haydentherapper](https://togithub.com/haydentherapper)) - Matt Moore ([@​mattmoor](https://togithub.com/mattmoor)) - Ross Tannenbaum ([@​RTann](https://togithub.com/RTann)) - Ville Aikas ([@​vaikas](https://togithub.com/vaikas)) </details> --- ### Configuration 📅 **Schedule**: 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, click this checkbox. --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://app.renovatebot.com/dashboard#github/defenseunicorns/zarf). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzMi4yMjIuMyIsInVwZGF0ZWRJblZlciI6IjMyLjIyMi4zIn0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🐛 Remove an extra registry request when supplied with a digest.
The current logic calls
getSignedEntitywhich must determine the media type of the referenced entity in order to produce an appropriately typesSignedEntity. However, we are only interested in the attached signatures (or attestations) and not the underlying structure, so when we are passed a digest, this roundtrip is entirely superfluous.This changes this logic to explicitly resolve the digest (since verification wants to know the
v1.Hash), which is free for digests. Then we explicitly invokeociremote.Signatures()on one ofociremote.{Signature,Attestation}Tag, which is also free (since we always pass the digest)./kind bug
Signed-off-by: Matt Moore mattmoor@chainguard.dev
Release Note
Make signature/attestation verification slightly more efficient when passed a digest (as we always are in
policy-controller).Documentation