Night 2026-10-17: restore keeps the DB password (R-1106, 07 §7.4), restic 0.19.1, hardening; 8 rows closed, 7 filed; evidence
gates / gates (push) Successful in 6m57s

This commit is contained in:
admin committed 2026-10-16 23:59:53 +02:00
1 parent 96e15c15ba
commit 5c36d4c110
39 files changed
+2250 -23

No files matched your search

+13
View File
@@ -26,6 +26,19 @@
---
## 2026-10-17 — night: restore after a reinstall, restic 0.19.1, hardening (controller v0.324.0, catalog `af75dc0`)
| Row | What | Closed | Evidence |
|---|---|---|---|
| **R-1065** | **After the Plex claim the box does not set Plex's libraries until the next wiring run.** (P3) | CLOSED 2026-10-17 — **controller v0.324.0**: a successful Plex claim schedules the media wiring (`RunMediaWiringSoon`, both claim routes). `TestPlexClaim_TriggersMediaWiring` (claimed / refused / never claimed), red-proved. Not seen live: no claim code tonight; the N100's next claim is the live observation. | `audits/night-restore-2026-10-17/` |
| **R-926** | **After a household removes an `after_install` app keeping its backups and then restores it, nobody has checked whether the app page still shows a password that works.** (P3) | CLOSED 2026-10-17 — answered from the code and fixed where it was wrong. After a unit restore that had to GENERATE a `type: password` login, the page never shows it and says to use the old password (R-694's `RestoredLogins`) — the household's own password works (measured for grocy 2026-10-10). The path that was wrong: an off-site restore over a reinstall kept the reinstall's admin login as „the login”; since **controller v0.324.0** `SetStackSecretValues` records those as restored-login fields too (`TestR1106_SetStackSecretValues`, red-proved). | `audits/night-restore-2026-10-17/` |
| **R-1106** | **An app with a database that is removed, reinstalled and then fully restored from the off-site copy comes back unusable: the restore puts back the OLD database volume, which carries the old install's database password, while the reinstall generated a new one.** (P2) | CLOSED 2026-10-17 — **controller v0.324.0** (operator decision 1A): the database password comes back with the data. The off-site full restore over a reinstall writes the snapshot's password before the database starts (only when the snapshot replays the DB volume); the shared unit-restore env refuses, before any change, when neither the unit nor an install OLDER than the data holds it; O4 never generates a DB password. **Live on demo-hp 9201** (rc.1, the dashboard's posts): Rallly (Postgres) and Grimmory (MariaDB) seeded, removed, reinstalled, restored — off-site path: marker row + books file back, both apps healthy, the app's and the dump user's DB logins work (last night: crash loop and held); on-box path (Rallly) the same; the refusal (Rallly unit without its password) refused with the app untouched; „use my kept data” (Grimmory) the same. Tests `TestR1106_*` red-proved; catalog gate `db-credentials`. `07` §7.4. | `audits/night-restore-2026-10-17/` |
| **R-127** | **The catalog's `data_key: true` flag is UNRELIABLE — at least four data-encrypting keys the catalog itself labels as encryption keys are unflagged; and the O4 restore path can regenerate a DB password that then does not match the restored data directory** (P3) | CLOSED 2026-10-17 — leg (a) was pushed 2026-10-06 (catalog `c265b37`); leg (b) is decided (operator decision 1A) and built in **controller v0.324.0** with R-1106: a database password is never regenerated for restored data, the unit's value wins, a restore without it is refused before any change. 20 DB credential fields in 17 apps (the 18 counted here plus apps added since), all `type: secret`, gated by `db-credentials`. | `audits/night-restore-2026-10-17/` |
| **R-1108** | **A share added while sharing is on but the household password is not yet set is not exported once the password is set, if the samba container was already running: `SetSMBPassword` rewrites `smb.conf` and the compose file but starts the stack only when it is NOT running, and the next reconcile sees „unchanged + running" and does nothing.** (P4) | CLOSED 2026-10-17 — **controller v0.324.0**: `SetSMBPassword` applies changed files when the stack is already running. `TestSambaPassword_ShareAddedBeforePasswordIsApplied` + companion, red-proved. Live on demo-hp: a share added before the password was set, reached with `smbclient` from DooPlex (the exact „first password failed” order needs a box that never had a password — that order rests on the test). | `audits/night-restore-2026-10-17/` |
| **R-983** | **Seven small dashboard weaknesses: after sign-in the browser can be sent to another site; the server-reboot route acts on a GET, so a link can reboot the guest (** (P3) | CLOSED 2026-10-17 — the six remaining items in **controller v0.324.0**, one red-proved test each (`TestR983_*`): sign-in `next` stays on the box; `X-Frame-Options: DENY` + `frame-ancestors 'none'`; a try is counted before the password check (dashboard and family gate); settings password minimum = the claim's 12; reset-code requests limited (1 per visitor per minute, 3 per box per 15 min); logout is POST + CSRF (dashboard, family gate — the dashboard's sign-out link had done nothing since 2026-02-25). Headless Chrome on demo-hp's public address: sign in, headers, POST sign-out, sign in again. Remaining limiters → R-1111. | `audits/night-restore-2026-10-17/` |
| **R-976** | **A family member's session can be copied out of a family-gated app, and a dashboard password reset does not end family or gate sessions; so a stolen session keeps working for up to 30 days.** (P3) | CLOSED 2026-10-17 — **controller v0.324.0**: a password change or reset ends every dashboard, family and setup-gate session (the gate key rotated and saved); a family app cookie carries a per-app HMAC token, never the session. `TestR976_*` red-proved (a restart check included). Headless Chrome on demo-hp: the family-gated Grimmory and the setup-gated Rallly open for the household. Raw storage → R-1112; growth → R-1113. | `audits/night-restore-2026-10-17/` |
| **R-1017** | **A comment names a guard test that does not exist.** (P3) | CLOSED 2026-10-17 — the guard exists: `TestNoBareDrivePathToUserdataDir` (parses every non-test Go file; one listed exception), red-proved four ways. It found a real one: the remove dialog's „kept folders” list was empty on the system-drive fallback (`delete.go` `userdataKept`) — fixed in **controller v0.324.0**, `TestRemoveStack_R800_UserdataKeptOnSystemDrive`. Sibling helpers → R-1110. | `audits/night-restore-2026-10-17/` |
## 2026-10-16 — burndown 2 (controller v0.322.0)
| Row | What | Closed | Evidence |