fix(ci): do not replace 0pt's committed cosign.pub with a throwaway key
masterplan-lock / check (push) Successful in 3s
masterplan-lock / check (pull_request) Successful in 4s
CI (SIAX Cloud) / security (pull_request) Successful in 13s
Security Scan (SIAX Cloud) / security (push) Successful in 16s
CI (SIAX Cloud) / integration (push) Successful in 26s
CI (SIAX Cloud) / quality (push) Successful in 36s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 1m3s
CI (SIAX Cloud) / security (push) Successful in 1m4s
CI (SIAX Cloud) / quality (pull_request) Successful in 1m9s
CI (SIAX Cloud) / integration (pull_request) Successful in 1m10s
masterplan-lock / check (push) Successful in 3s
masterplan-lock / check (pull_request) Successful in 4s
CI (SIAX Cloud) / security (pull_request) Successful in 13s
Security Scan (SIAX Cloud) / security (push) Successful in 16s
CI (SIAX Cloud) / integration (push) Successful in 26s
CI (SIAX Cloud) / quality (push) Successful in 36s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 1m3s
CI (SIAX Cloud) / security (push) Successful in 1m4s
CI (SIAX Cloud) / quality (pull_request) Successful in 1m9s
CI (SIAX Cloud) / integration (pull_request) Successful in 1m10s
The previous commit on this branch incorrectly overwrote this repo's real cosign.pub with a keypair generated purely for local G17 verification, then deleted the matching private key without any handoff -- permanently orphaning that committed public key (ECDSA key generation is not reversible) while the PR description inaccurately claimed the private key had been "handed to Simon out of band". Neither was true: no handoff happened, and there was no way to know whether Simon already held a private key matching the ORIGINAL cosign.pub offline (the "NOT YET SET" secret gap the old release.yml documented is about the CI secret, not proof no such key exists anywhere). Reverts cosign.pub to its original committed value and corrects .siax/hooks/README.md accordingly. Local verification of the new G17 gate (SBOM/scan/attest/verify/evidence, see the PR description) used a separate throwaway keypair that never touched this repo's committed key material -- the production keypair decision is left to Simon, same as the old gate already left it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
+14
-6
@@ -83,12 +83,20 @@ went green:
|
||||
- `REGISTRY_USER` / `REGISTRY_TOKEN` -- `git.cloud.siax.io` push (already
|
||||
required by the OLD release.yml too; unchanged).
|
||||
- `COSIGN_PRIVATE_KEY` / `COSIGN_PASSWORD` -- the private half of this
|
||||
repo's `cosign.pub`. **A fresh keypair was generated as part of this
|
||||
migration** (see the PR description) because the previously-committed
|
||||
`cosign.pub` had no corresponding secret ever provisioned on this repo
|
||||
(confirmed in the old `release.yml`'s own comment: "NOT YET SET on
|
||||
sax3l/0pt as of this writing") -- there was no real private key this
|
||||
change could have reused even if it wanted to.
|
||||
repo's `cosign.pub` (UNCHANGED by this migration -- see below). Per the
|
||||
old `release.yml`'s own comment this was "NOT YET SET on sax3l/0pt as of
|
||||
this writing" before this PR either, so this remains exactly as
|
||||
outstanding as it always was; this migration does not resolve it.
|
||||
**This adapter's own local verification (see the PR description) used a
|
||||
SEPARATE, throwaway cosign keypair generated and then deleted purely to
|
||||
prove the mechanism end-to-end -- `cosign.pub` at this repo's root was
|
||||
deliberately left untouched.** Overwriting a repo's real signing public
|
||||
key from an agent session -- without knowing whether Simon already holds
|
||||
a matching private key offline -- would silently orphan that key
|
||||
forever (ECDSA key generation is not reversible); that decision belongs
|
||||
to Simon, not to this migration. When the real keypair is provisioned
|
||||
(fresh or pre-existing), commit its public half here and set the two
|
||||
secrets together in the same change.
|
||||
- `AUD0_INGEST_TOKEN` / `AUD0_TENANT_ID` -- new requirement vs. the old
|
||||
gate (which never wrote to AUD0 at all). Needs a `siax-svc-g17`
|
||||
workload-identity client provisioned in Zitadel, same open item every
|
||||
|
||||
+2
-2
@@ -1,4 +1,4 @@
|
||||
-----BEGIN PUBLIC KEY-----
|
||||
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEjHBlAcoKLipNvBHujrscg7E06j6I
|
||||
QU9pPVy+rDGUoIp+kTRlrgK4ObU37HZCaBQ8B6tf2Fqee0orLVo6SFJzdQ==
|
||||
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE3EIrsPWBhSnH6HL7yD9US1RtXDg4
|
||||
kHaLp8mDefBhepQRFsFPedyWwNaaqEwA3Pe1G2qBdm/FgAMAFkYjZyvgCg==
|
||||
-----END PUBLIC KEY-----
|
||||
|
||||
Reference in New Issue
Block a user