From 97747d58fa04aa210af48dfe54333ca9defb5d9d Mon Sep 17 00:00:00 2001 From: Nico Wiedemann Date: Thu, 1 Oct 2026 15:51:48 +0200 Subject: [PATCH 1/2] Say what turning on encryption does to existing access keys A key made before encryption carries no copy of the new content key, so it signs in and reads nothing afterwards, and the cloud now revokes OAuth connections at the moment encryption is turned on so a Claude connector asks to reconnect. The screen listing what encryption costs said neither. It now has a line saying existing keys must be replaced and connected AI tools will ask to connect again, in en, de and zh, with a CHANGELOG entry. Co-Authored-By: Claude Opus 5 (1M context) --- CHANGELOG.md | 7 +++++++ src/lib/components/EncryptionPanel.svelte | 1 + src/lib/i18n/locales/de.json | 1 + src/lib/i18n/locales/en.json | 1 + src/lib/i18n/locales/zh.json | 1 + 5 files changed, 11 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index abd0deb..e3e796e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,6 +11,13 @@ popover, not for the person who wrote the commit. ## [Unreleased] +### Changed +- **Turning on encryption now says what happens to your existing access keys.** A key made + before encryption cannot read the encrypted account, because it carries no copy of the new + key, so it has to be replaced afterwards. AI tools connected by signing in, such as a + Claude connector, are disconnected when you turn encryption on and ask you to connect + again. Keys you made by hand are kept, and the account page marks the ones to replace + ## [1.10.0] - 2026-10-01 ### Added diff --git a/src/lib/components/EncryptionPanel.svelte b/src/lib/components/EncryptionPanel.svelte index 771b8da..9dfaf33 100644 --- a/src/lib/components/EncryptionPanel.svelte +++ b/src/lib/components/EncryptionPanel.svelte @@ -365,6 +365,7 @@ See the GNU Affero General Public License for more details.