mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-16 23:33:29 +00:00
The step confirmed one key, the active application key. A restore needs more: off-host copies are sealed under BACKUP_ENCRYPTION_KEY, a copy written before a rotation needs the retired application key it was written under, and every session, token and share link hangs off API_TOKEN_HMAC_KEY. An operator could do everything the step asked and still be unable to read a single backup. The recovery kit lists every key a restore of this server needs, by id and fingerprint, never key material: - each id in ENCRYPTION_KEYS, plus any retired id a stored copy (innerKeyIds) or an off-host object inside the bucket's retention (OffhostBackupKeyUse) still lists, also once the server dropped it; - BACKUP_ENCRYPTION_KEY and each BACKUP_ENCRYPTION_PREVIOUS_KEYS entry, named by the id their objects record; - API_TOKEN_HMAC_KEY. Confirming records the set the admin was shown and refuses a stale one with 409 recovery.kit.stale. The kit is due again as soon as a key it lists is not in that set (a rotation, a new backup key, a re-keyed install); a key that merely drops out does not make it due. "Check my copy" now checks any key in the kit. Migration 0487 carries a confirmation given under the old step forward as a kit holding that key, so that part stays confirmed, and drops the four app_settings columns. It also creates the two tables the readiness evaluation uses (restore_drill_outcomes, recovery_readiness_notices). The routes move to /api/admin/recovery-kit; the reader of the keys the backups still need moves out of the encryption status route into src/lib/recovery/backup-key-needs.ts so the kit and the status view share one definition.
30 lines
1018 B
TypeScript
30 lines
1018 B
TypeScript
/**
|
|
* GET /api/admin/recovery-kit
|
|
*
|
|
* The recovery kit: every key a restore of this instance needs (the
|
|
* application keys, including retired ones a backup still lists, the off-host
|
|
* backup keys and the token key), each with its fingerprint and why it is
|
|
* needed, and whether the admin's confirmation covers it. Ids and
|
|
* fingerprints only, never key material. Cookie-only admin.
|
|
*/
|
|
import { apiHandler, requireAdmin } from "@/lib/api-handler";
|
|
import { apiSuccess } from "@/lib/api-response";
|
|
import { annotate } from "@/lib/logging/context";
|
|
import { readRecoveryKit } from "@/lib/recovery/kit";
|
|
|
|
export const dynamic = "force-dynamic";
|
|
|
|
export const GET = apiHandler(async () => {
|
|
await requireAdmin();
|
|
annotate({ action: { name: "admin.recoveryKit.status" } });
|
|
const kit = await readRecoveryKit();
|
|
annotate({
|
|
meta: {
|
|
recovery_kit_due: kit.due,
|
|
recovery_kit_keys: kit.keys.length,
|
|
recovery_kit_unconfirmed: kit.unconfirmed.length,
|
|
},
|
|
});
|
|
return apiSuccess(kit);
|
|
});
|