RBAC-5: seal a per-daughter Forgejo-webhook HMAC secret (plat/mitosis#32) #58
No reviewers
Labels
No labels
bug
discussion
duplicate
enhancement
goal
help wanted
horizon:backlog
horizon:governance
horizon:mvp
invalid
operator-decision
question
roadmap
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-platform/mitosis!58
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/rbac-5-webhook-hmac-seal"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
RBAC-5 (plat/mitosis#32): seal the webhook HMAC secret per daughter
fork_regen_secretsnow mints a freshWEBHOOK_SECRET(openssl rand -hex 32) and seals it into the daughter'splat-agents-secrets, sealed to the sovereign fork key. The agents Deployment already loads it viaenvFrom(plat-agents-secrets), so the dispatcher readsWEBHOOK_SECRETand both signs the Forgejo system-hook and verifiesX-Hub-Signature-256on/hookbefore dispatch (agents PR).Edits
fork_regen_secretsonly (germinate seam; bin/up untouched — DOM-2 owns it).Validation. Ran
fork_rekey_sops+fork_regen_secretsagainst a fresh gitops clone with a throwaway fork key: the decryptedplat-agents-secretscarriesWEBHOOK_SECRET(sops-decryptable by the fork key), and two independent runs produce distinct secrets (per-daughter randomness confirmed).Pairs with agents PR (verify + seal-into-Forgejo). Do not merge — orchestrator gates.
🤖 Generated with Claude Code