Marc-André Bombeck 29c5b5b83b fix(crypto): one read order for a sealed column beside its readable one ...

Notes, workout tracks and the cached insights payload each read their
ciphertext and legacy column their own way: the cache read the readable
column first, and the two that read the ciphertext first disagreed on a
value that does not open. readSealedOrLegacy fixes the order (ciphertext
whenever present, the readable column only without one, never as a stand-in
for a failed open) and makes each caller state what a failed open means.

2026-10-20 09:29:03 +02:00

..

__tests__

fix(crypto): one read order for a sealed column beside its readable one

2026-10-20 09:29:03 +02:00

canary.ts

Ask the newest values before the key check refuses

2026-10-04 01:58:04 +02:00

encrypted-columns.ts

chore: strip planning tags from comments and enable the rule

2026-10-20 09:08:40 +02:00

encryption-corpus.ts

fix(crypto): keep updatedAt when key rotation re-seals a value

2026-10-05 13:07:22 +02:00

key-backup.ts

feat(encryption): back up the key, and refuse to serve when it cannot open the database

2026-10-03 18:06:28 +02:00

note-cipher.ts

fix(crypto): one read order for a sealed column beside its readable one

2026-10-20 09:29:03 +02:00

sealed-or-legacy.ts

fix(crypto): one read order for a sealed column beside its readable one

2026-10-20 09:29:03 +02:00