Skip to content

Add encrypted Chrome session export/import with real A-to-fresh-B proof - #17

Open
benjaminshafii wants to merge 2 commits into
fix/runtime-health-and-vncfrom
feat/browser-session-transfer
Open

benjaminshafii wants to merge 2 commits into
fix/runtime-health-and-vncfrom
feat/browser-session-transfer

Conversation

@benjaminshafii

Copy link
Copy Markdown
Member

Summary

  • Add operator-only browser session capture/restore using guest-loopback CDP and pinned SSH.
  • Require explicit sensitive-data consent, HTTPS origin scope, TTL, host-only cookie semantics, and encrypted AES-GCM vault storage outside the source VM and repository.
  • Transfer only approved cookies/localStorage; no personal profile, Keychain, browser passwords, passkeys, IndexedDB, device-bound tokens, or arbitrary app state.

Real acceptance

  • Logged in once to a dedicated private HTTPS test service in actual GUI Chrome in VM A.
  • Saved encrypted state outside A, stopped A, and created B from the clean starter (not a clone of A).
  • Verified B initially signed out with zero cookies and no marker.
  • Restored the export; B authenticated using the SAME server session record, with successful-login/session-issuance counts still 1/1.
  • Closed/reopened Chrome in B and verified the same record, persisted cookie and localStorage again. HttpOnly remained invisible to page JS.
  • Deleted the test export. Colleague VM left running throughout this transfer test. Demo is temporary and session expires after one hour.

126 tests and publication hygiene pass. Sanitized evidence, setup failures and test-only certificate pin caveat are in reports/browser-session-transfer-2026-10-16.md. No private credentials, addresses, logs or screenshots are included.

Dependency / limits

Stacked on #16 because its required separate approval is still outstanding. Do not bypass protections. This is independently implemented CDP transfer, not a Cua Teleport SDK integration or proof every external service accepts copied sessions. Restore is additive/nontransactional; dedicated profile selection is operator-attested. Review before broad deployment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant