confide:vault — the THREE LOCKS for storing RED data
Operationalizes the defense-in-depth storage posture in
confide/docs/THREE-LOCKS.md: real (RED) transcripts rest behind three independent
locks, so compromising one does not expose a client. To read a real transcript an
attacker needs the device password AND the encrypted-store password AND the
age key — three separate secrets, ideally held in different places.
| Lock |
What |
Protects against |
| 1 — Device |
FileVault full-disk encryption + strong login password + short auto-lock |
a lost/stolen/USB-booted machine |
| 2 — Store |
RED in a dedicated ENCRYPTED store (encrypted APFS volume / AES-256 .dmg), NOT in Documents and NEVER in iCloud/Dropbox |
other apps, other users, silent cloud sync |
| 3 — Per-file |
each RED file sops/age-encrypted at rest, age key stored SEPARATELY; processing in a no-network VM/container |
files individually sealed; key not beside the data |
NON-DESTRUCTIVE — read before running
--check (the default) runs only read-only probes: fdesetup status,
shutil.which(sops/age), and os.path.exists(...). It never moves, deletes, or
encrypts data and never runs fdesetup enable, hdiutil, age-keygen, or rm.
- It reports each lock ✓/✗ and prints the exact command to fix every ✗ — for the user
to review and run themselves.
--init-age generates an age key only with that explicit flag, and never
overwrites an existing key.
--init-store PATH only prints the encrypted-store creation command; it does not
execute disk-image creation. Refuses cloud-synced paths.
- Never move, encrypt, or delete the user's RED data on their behalf without explicit
confirmation. There is no destructive default.
Run it
# default = read-only status check + checklist with fix commands
python3 skills/vault/scripts/vault.py --check
python3 skills/vault/scripts/vault.py --json # structured status dict
# point at your own RED store to verify it's not cloud-synced
python3 skills/vault/scripts/vault.py --store-path ~/CONFIDE-RED.dmg
# optional, GUARDED helpers (explicit flags only)
python3 skills/vault/scripts/vault.py --init-age # make an age key (never overwrites)
python3 skills/vault/scripts/vault.py --init-store ~/CONFIDE-RED.dmg # prints the hdiutil command
lock_status() is importable and returns:
{
"device": {"filevault": bool},
"store": {"present": bool, "path": str|None, "cloud_synced": bool, "safe": bool},
"perfile": {"sops": bool, "age": bool, "key": bool, "key_path": str|None}
}
How to help the user
- Run
--check and read back the ✓/✗ checklist.
- For each ✗, show the printed fix command (e.g.
sudo fdesetup enable,
age-keygen -o ~/.config/confide/age.key,
hdiutil create -encryption AES-256 … ~/CONFIDE-RED.dmg) and let the user run it.
- Confirm the RED store is not inside iCloud/Dropbox (
store.safe).
- Show the sops/age encrypt+decrypt recipe (printed in the checklist) so RED stays
ciphertext at rest and is decrypted only in-memory inside the isolated pipeline
(
confide/docs/ISOLATION.md). Only GREEN (redacted) output ever leaves the machine.
See confide/docs/THREE-LOCKS.md (the model + checklist) and confide/docs/ISOLATION.md
(red/green flow, no-network VM/container).
1---
2name: vault
3description: >-
4 Set up and verify the CONFIDE THREE LOCKS for storing RED (real, identifiable) session
5 data at rest — device FileVault, a dedicated encrypted store, and per-file sops/age
6 encryption. Use when the user says "set up confide vault", "encrypt my session data",
7 "three locks", "secure store for transcripts", "sops/age for RED data", or asks how to
8 store real therapy/coaching transcripts safely. NON-DESTRUCTIVE: it CHECKS each lock's
9 status and prints the EXACT command to fix any gap; it never moves, deletes, or encrypts
10 data, and never runs `fdesetup enable`/`hdiutil`/`age-keygen` without an explicit flag
11 and your confirmation. Probes are read-only (`fdesetup status`, which sops/age, key path).
12metadata:
13 source: https://skillmd.com/skills/glebis/vault
14---
15
16# confide:vault — the THREE LOCKS for storing RED data
17
18Operationalizes the defense-in-depth storage posture in
19`confide/docs/THREE-LOCKS.md`: real (RED) transcripts rest behind **three independent
20locks**, so compromising one does not expose a client. To read a real transcript an
21attacker needs the **device password** AND the **encrypted-store password** AND the
22**age key** — three separate secrets, ideally held in different places.
23
24| Lock | What | Protects against |
25|---|---|---|
26| **1 — Device** | FileVault full-disk encryption + strong login password + short auto-lock | a lost/stolen/USB-booted machine |
27| **2 — Store** | RED in a dedicated ENCRYPTED store (encrypted APFS volume / AES-256 `.dmg`), NOT in Documents and NEVER in iCloud/Dropbox | other apps, other users, silent cloud sync |
28| **3 — Per-file** | each RED file `sops`/`age`-encrypted at rest, age key stored SEPARATELY; processing in a no-network VM/container | files individually sealed; key not beside the data |
29
30## NON-DESTRUCTIVE — read before running
31- `--check` (the default) runs **only read-only probes**: `fdesetup status`,
32 `shutil.which(sops/age)`, and `os.path.exists(...)`. It **never** moves, deletes, or
33 encrypts data and **never** runs `fdesetup enable`, `hdiutil`, `age-keygen`, or `rm`.
34- It reports each lock ✓/✗ and prints the **exact command** to fix every ✗ — for the user
35 to review and run themselves.
36- `--init-age` generates an age key **only** with that explicit flag, and **never**
37 overwrites an existing key.
38- `--init-store PATH` only **prints** the encrypted-store creation command; it does not
39 execute disk-image creation. Refuses cloud-synced paths.
40- Never move, encrypt, or delete the user's RED data on their behalf without explicit
41 confirmation. There is no destructive default.
42
43## Run it
44
45```bash
46# default = read-only status check + checklist with fix commands
47python3 skills/vault/scripts/vault.py --check
48python3 skills/vault/scripts/vault.py --json # structured status dict
49
50# point at your own RED store to verify it's not cloud-synced
51python3 skills/vault/scripts/vault.py --store-path ~/CONFIDE-RED.dmg
52
53# optional, GUARDED helpers (explicit flags only)
54python3 skills/vault/scripts/vault.py --init-age # make an age key (never overwrites)
55python3 skills/vault/scripts/vault.py --init-store ~/CONFIDE-RED.dmg # prints the hdiutil command
56```
57
58`lock_status()` is importable and returns:
59
60```
61{
62 "device": {"filevault": bool},
63 "store": {"present": bool, "path": str|None, "cloud_synced": bool, "safe": bool},
64 "perfile": {"sops": bool, "age": bool, "key": bool, "key_path": str|None}
65}
66```
67
68## How to help the user
69
701. Run `--check` and read back the ✓/✗ checklist.
712. For each ✗, show the printed fix command (e.g. `sudo fdesetup enable`,
72 `age-keygen -o ~/.config/confide/age.key`,
73 `hdiutil create -encryption AES-256 … ~/CONFIDE-RED.dmg`) and let the user run it.
743. Confirm the RED store is **not** inside iCloud/Dropbox (`store.safe`).
754. Show the sops/age encrypt+decrypt recipe (printed in the checklist) so RED stays
76 ciphertext at rest and is decrypted only in-memory inside the isolated pipeline
77 (`confide/docs/ISOLATION.md`). Only GREEN (redacted) output ever leaves the machine.
78
79See `confide/docs/THREE-LOCKS.md` (the model + checklist) and `confide/docs/ISOLATION.md`
80(red/green flow, no-network VM/container).