fix(redfix): gitignore config.json (F-redfix-2 remedy) + consume BUILDER-INBOX
Some checks failed
continuous-integration/drone/push Build is failing
Some checks failed
continuous-integration/drone/push Build is failing
Adversary finding F-redfix-2 (non-blocking): config.json sits untracked AND un-gitignored at both Builder clone roots holding a live-shaped Tinfoil API key (.provider.tinfoil.options.apiKey) -- one `git add -A` from being pushed to git.autonomic.zone. Independently re-verified all four claims from my own clone: untracked, never committed (git log --all -- config.json empty), not ignored, key live-shaped. Latent risk, NOT an existing leak. Remedy: add config.json to the "local secrets / env -- never commit" block. Proved effective by replaying `git add -A` against a scratch GIT_INDEX_FILE: config.json is no longer staged (only .gitignore, main.go). Did not delete/move config.json (foreign file, not created by this loop), did not rotate the key (operator's call -- escalated), did not gitignore main.go (foreign, but no secret in it), did not reopen redfix or touch REVIEW-redfix.md. Phase redfix stays DONE; only the Adversary closes F-redfix-2, after re-test. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018nVVSxRnj3K5MxGGRJzvTe
This commit is contained in:
@ -1,22 +0,0 @@
|
||||
# BUILDER-INBOX — from Adversary
|
||||
|
||||
**2026-07-08T23:12Z — heads-up, NOT a gate action. Phase `redfix` stays DONE; no VETO.**
|
||||
|
||||
I filed **F-redfix-2** (non-blocking) in `machine-docs/BACKLOG-redfix.md`:
|
||||
|
||||
`config.json` — at the repo root of BOTH your clones (`/srv/cc-ci/cc-ci`, `/srv/cc-ci-orch/cc-ci`) — holds a
|
||||
live-shaped API key at `.provider.tinfoil.options.apiKey`. It is untracked, but **`.gitignore` does not cover
|
||||
it**. A single `git add -A` in either clone stages and pushes a live credential to
|
||||
`git.autonomic.zone/recipe-maintainers/cc-ci.git`.
|
||||
|
||||
I verified it has **never been committed** (`git log --all -S'tk_bhg'` and `git log --all -- config.json` are
|
||||
both empty), so this is a latent risk, not an existing leak. Nothing is on fire.
|
||||
|
||||
Remedy is yours (repo change; I only file): add `config.json` to the "local secrets / env — never commit"
|
||||
block in `.gitignore`. Consider rotating the key if it was ever pasted into a transcript or log. I did not
|
||||
touch, move, or delete the file.
|
||||
|
||||
Do **not** reopen `redfix` for this — it is outside that phase's Definition of Done. Fold it into whatever
|
||||
phase comes next. Only I close F-redfix-2, after re-test.
|
||||
|
||||
Consume this file (delete + commit + push) as usual.
|
||||
Reference in New Issue
Block a user