Add secure remote transport and session storage safeguards #968

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

Scope

Implement the runtime plumbing for remote secret-input sessions, including process boundaries and state handling needed by the selected mobile adapter and engine registry. Prefer short-lived in-memory state; if restart recovery is required, store only non-sensitive metadata and require a new submission challenge.

Ensure the normal agent/tool execution path cannot accidentally consume or persist the raw value. Add bounded concurrency and rate limits to prevent abuse.

Acceptance criteria

  • Raw secret values do not cross the model, issue/forge, normal chat transcript, or general event-bus boundaries.
  • Session metadata is bounded, expires deterministically, and is cleaned up on success, failure, cancellation, and shutdown.
  • Replay, brute-force, concurrent submissions, and resource-exhaustion protections are implemented and tested.
  • Remote input is disabled or reports unavailable when no authorized writable engine is configured.
  • Security-sensitive operations have structured audit events containing actor/target/outcome but never the value.

Close reason

Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic.


Imported from beads archie-core-1786748942414-13-14bd990e · GitHub #508 · type task · priority P1 · created 2026-08-14 · closed 2026-08-18

## Scope Implement the runtime plumbing for remote secret-input sessions, including process boundaries and state handling needed by the selected mobile adapter and engine registry. Prefer short-lived in-memory state; if restart recovery is required, store only non-sensitive metadata and require a new submission challenge. Ensure the normal agent/tool execution path cannot accidentally consume or persist the raw value. Add bounded concurrency and rate limits to prevent abuse. ## Acceptance criteria - Raw secret values do not cross the model, issue/forge, normal chat transcript, or general event-bus boundaries. - Session metadata is bounded, expires deterministically, and is cleaned up on success, failure, cancellation, and shutdown. - Replay, brute-force, concurrent submissions, and resource-exhaustion protections are implemented and tested. - Remote input is disabled or reports unavailable when no authorized writable engine is configured. - Security-sensitive operations have structured audit events containing actor/target/outcome but never the value. ### Close reason Orphaned children of epic archie-core-1786748942324-9-509793a0, which was closed as pivoted-away: 'value-entry web form duplicates the Bitwarden app for bws and adds a secret-accepting web surface for no gain... Replaced by fresh-resolving sops/vault/age engines... value-entry UX deferred until a writable engine without a mobile path exists.' The replacement work already shipped (secret engine plugins for sops/vault/age). These 6 tasks were never closed alongside their parent epic. --- _Imported from beads `archie-core-1786748942414-13-14bd990e` · GitHub #508 · type task · priority P1 · created 2026-08-14 · closed 2026-08-18_
sam added the hightask labels 2026-10-27 13:38:30 +00:00
sam self-assigned this 2026-10-27 13:38:30 +00:00
sam closed this issue 2026-10-27 13:38:30 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#968