fix: use correct Rekor URLs to activate privacy warning - #5054
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #5054 +/- ##
==========================================
- Coverage 40.10% 39.69% -0.41%
==========================================
Files 155 207 +52
Lines 10044 13048 +3004
==========================================
+ Hits 4028 5180 +1152
- Misses 5530 7134 +1604
- Partials 486 734 +248 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
#5055 for the linter fix |
|
can you rebase? |
|
@Hayden-IO quick question: I thought you wanted a URL-based match when we were discussing in the other PR? |
|
That shouldn't change, matching should still be based on URLs. The previous PR didn't account for the divergent codepaths between the Cosign signing API and the sigstore-go signing API, so it was only checking the |
Signed-off-by: Aaron Lew <64337293+aaronlew02@users.noreply.github.com>
Signed-off-by: Aaron Lew <64337293+aaronlew02@users.noreply.github.com>
… instead of KeyOpts Signed-off-by: Aaron Lew <64337293+aaronlew02@users.noreply.github.com>
8e8962d to
36d750d
Compare
Summary
This change updates the Rekor public good instance privacy warning for
signandsign-blobto appear only when the Rekor public good instance is to be used.Previously,
ShouldUploadToTlogonly checkedKeyOpts.RekorURL, despite the fact thatKeyOpts.RekorURLdefaults to the public good Rekor URL even when a signing config is provided containing a different transparency log URL. Now,ShouldUploadToTloginstead checks the signing config created for users that do not provide one manually.To make this work, the following refactors occur:
ko.RekorURLwhen--tlog-upload=false.NewSigningConfigFromKeyOptsno longer has atlogUploadinput, and the relevant logic has been extracted for afterShouldUploadToTlogis called.ShouldUploadToTlogis called.