coulomb/railiance-forge
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

security: record scanner custody recovery across Kubernetes restarts
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a1346b-72a4-7d40-b8bd-8b8ca346cfa2
This commit is contained in:
tegwick 2026-10-13 15:01:37 +02:00
parent ec1d7c591a
commit 2c11c366ce
1 changed files with 21 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

23
workplans/FORGE-WP-0006-independent-secret-detection.md
View file

@ -133,8 +133,27 @@ and `activate_forge_template.py`. Rollback retains the ConfigMap inert and uses
an explicit default template selection because merely removing the environment
variable would leave the saved setting behind. Original immutable October 12
activation remains bound to its old pod and must not be rewritten or replayed.
Authenticated production HTTP/SSO/frontend creation, the other 143 existing
repositories, import/mirror and wider detection/response coverage remain open.
Authenticated production HTTP/SSO/frontend creation, the other 144 existing
repositories (fresh 166-repository inventory), import/mirror and wider detection/response coverage remain open.
2026-10-13 custody recovery: the generation-12 health/hash/malformed-input
acceptance above missed a restart regression. The next normal source push refused
with `scanner-file-refused`: both binaries were 0775 after Kubernetes volume
processing. FORGE6-TEMPLATE-LIFECYCLE-001 remains a failed original trial.
Recovery revision 2 verified the exact binary hashes/owners and restored 0755;
this repository's queued `ec1d7c5` push then succeeded. Revision 3 persists an
unprivileged hash/owner-checking init guard in railiance-apps `50b66c4`, mounting
only the existing security subtree. Generations 13 and 14 completed that guard
and passed inherited installed-hook clean acceptance, intermediate-secret refusal,
quarantine removal and clean recovery. Six isolated custody cases pass. Native
temporary probes exclude builtin authorization; ordinary SSH pushes are checked
separately. Initial rejected dry-run preparations remain recorded. Rollback must
explicitly restore modes after removing the guard. Custodian evidence:
`docs/evidence/2026-10-13-netkingdom-security/forge-custody-recovery-summary.json`.
Fresh inventory is 166 repositories: 22 admitted profiles and 144 builtin-only;
one default tree has gitlinks, needing compatibility treatment before expansion.
Production HTTP/SSO/frontend, import/mirror, CI and response acceptance remain
open. T02/T03 are not complete from this repaired lifecycle slice.
## Verify CI independence, detection response and complete coverage