Encrypt binding secrets at rest #475

Closed
opened 2026-10-27 13:36:28 +00:00 by sam · 0 comments
Owner

binding.Binding.Secret is currently stored as plaintext in the bindings.secret TEXT column. Anyone with read access to the SQLite file (the same access level as captured_events.body and tasks.body) sees HMAC secrets in plaintext. Add at-rest encryption for the secret column so a leaked database file does not leak sender-side shared secrets. See docs/prds/webhook-intake-security.md point 5. Decide the cipher (likely AES-GCM with a key derived from archied's secret registry or a deployment-level key file), the key-rotation story, and whether captured_events.body redaction is upgraded at the same time. Phase F work for t2db.

Close reason

Closed


Imported from beads archie-core-t2db.7 · GitHub #688 · type feature · priority P2 · created 2026-09-02 · closed 2026-09-02

binding.Binding.Secret is currently stored as plaintext in the bindings.secret TEXT column. Anyone with read access to the SQLite file (the same access level as captured_events.body and tasks.body) sees HMAC secrets in plaintext. Add at-rest encryption for the secret column so a leaked database file does not leak sender-side shared secrets. See docs/prds/webhook-intake-security.md point 5. Decide the cipher (likely AES-GCM with a key derived from archied's secret registry or a deployment-level key file), the key-rotation story, and whether captured_events.body redaction is upgraded at the same time. Phase F work for t2db. ### Close reason Closed --- _Imported from beads `archie-core-t2db.7` · GitHub #688 · type feature · priority P2 · created 2026-09-02 · closed 2026-09-02_
sam added the mediumfeature labels 2026-10-27 13:36:28 +00:00
sam self-assigned this 2026-10-27 13:36:28 +00:00
sam closed this issue 2026-10-27 13:36:28 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#475