Comments (8)
One imagined scenario is when you're rotating keys, you might want to sign the image with old.key and new.key at the same time, until you eventually cycle out old.key.
If the UX of having to specify multiple key passphrases makes this unfeasible that's understandable, it's still possible to just call cosign sign
multiple times in the meantime.
from cosign.
Multiply keys in rotation makes sense to me.
The same might hold for cosign verify in the context of validating multiple signatures, definitely possible to call cosign verify
multiple times by whoever is enforcing a policy, but might be worth adding support for batched verification.
from cosign.
Hmmm, the part about avoiding multiple trips to the registry makes sense - but I'm not sure I understand the usecase fully. I understand wanting to sign multiple times, but if the same "caller" has the ability to sign with multiple keys simultaneously, from the same environment, they sort of seem redundant.
Could you add any more detail?
from cosign.
Hmmm, the part about avoiding multiple trips to the registry makes sense - but I'm not sure I understand the usecase fully. I understand wanting to sign multiple times, but if the same "caller" has the ability to sign with multiple keys simultaneously, from the same environment, they sort of seem redundant.
Could you add any more detail?
Sure. First of all, I don't really feel that strongly about not emitting any signatures if any signing operation fails. I mostly just wanted to be able to pass multiple keys to the CLI, and being able to avoid registry operations seemed nice to have, and I thought I'd be less surprised in general if the cosign invocation either "succeeded" or "failed", and couldn't partially succeed.
If you think it's conceptually better to allow cosign sign -key=bad.key -key=good.key
to sign with the good key and log that it failed with the bad one, I won't fight too hard.
from cosign.
Sorry i think i wasn't clear - it's not about whether it would log or continue on failure.
I'm trying to understand why you would want to sign multiple times with multiple keys at the same time.
from cosign.
In all of my imaginary contrived workflows, i would sign once in CI with a key that only the CI system has access to, then sign from my machine with a key that only I have access to.
from cosign.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days.
from cosign.
This issue was closed because it has been stalled for 5 days with no activity.
from cosign.
Related Issues (20)
- cosign verify with certificates requires the --certificate-identity and --certificate-oidc-issuer flags HOT 2
- `cosign.VerifyImageAttestations` fails to verify attestations, returns `unable to verify bundle: matching bundle to payload: invalid kind value: "dsse"`" HOT 1
- cosign attach command couldn't attach the rekor-bundle to an image HOT 1
- Reconsider deprecation of SBOM attachments HOT 1
- Keyless verification with Bring Your Own Public Key Infrastructure (BYOPKI) HOT 2
- Add support for providing a trust root file for private deployments HOT 1
- Cosign Verify fails with azure akv intermittent HOT 1
- Cosign Verify fails with azure akv intermittent HOT 1
- Cosign verify does not work with only certificate and certificate chain HOT 1
- OIDC provider debugging HOT 1
- `bundleVerified` Flag Not Set After Successful Rekor Online Verification in Cosign
- Support AES management key on YubiKeys with 5.7.x firmware
- Error in GetTSACerts function
- TUF key verification fails, even though identity verification validates HOT 6
- Why not using an empty configuration for the signature on OCI 1.1? HOT 1
- Cosign can't verify by local key exported from HashiVault HOT 1
- main.go:74: error during command execution: signing **image:tag**: provenance predicate: required field builder missing HOT 1
- main.go:74: error during command execution: signing <registry>/<app>@s<digest>: PUT https://***att: MANIFEST_INVALID: manifest invalid; map[description:Could not locate artifact '***.att/manifest.json' HOT 1
- feature: 'cosign verify-*' add flags --ca-roots and --ca-intermediates to allow multiple CA roots
- fix golangci-lint issues in the test/ directory HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cosign.