From 4c417472ecdcac2c6eb8498ec4dc2dac16e66bfb Mon Sep 17 00:00:00 2001 From: Krzysztof kuhy Rudnicki Date: Sun, 1 Nov 2026 19:10:30 +0100 Subject: [PATCH] docs: E2E must cover export_keys Co-Authored-By: Claude Sonnet 5.5 Claude-Session: https://claude.ai/code/session_01WzxdWXTUM9dpnCS2wtFkx4 --- TODO-crdt-e2e-encryption.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/TODO-crdt-e2e-encryption.md b/TODO-crdt-e2e-encryption.md index 253629a..6828da1 100644 --- a/TODO-crdt-e2e-encryption.md +++ b/TODO-crdt-e2e-encryption.md @@ -11,6 +11,9 @@ local-first: hologram.page/blog/local-first-means-three-different-things). random key stored in the OS keystore and copied to new devices. - Migration: re-encrypt existing logs in place, or new prefix + one-time copy. - Scope: payload only (keep HLC/ids clear for merge) or whole record. +- diet_guard's `export_keys` document (random data-export keys, synced as a + keyring) sits in plaintext in RTDB, so Firebase can read them: it must move + under E2E too, with its key source decided here first. - tutor uses its own RTDB client (`~/src/tutor/app/lib/sync/rtdb_client.dart`): in or out of scope.