From cabc393b6bb08a3cf3ea260bf4b7834dd9da1ffb Mon Sep 17 00:00:00 2001 From: Lotus CI Date: Fri, 16 Oct 2026 18:35:59 -0400 Subject: [PATCH] Revert Draupnir Rust crypto (#26): it fails to start without a device-bound token With experimentalRustCrypto: true, Draupnir 2.9.0 exits on startup with "Encryption not possible: server not revealing device ID": its access token is not bound to a device, which matrix-bot-sdk crypto requires. Restores experimentalRustCrypto: false so the deploy hook brings it back. To enable encryption later, give Draupnir a device-bound access token (a normal password login) first. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5 --- draupnir/production.yaml | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/draupnir/production.yaml b/draupnir/production.yaml index 77d0d1a..d4899e5 100644 --- a/draupnir/production.yaml +++ b/draupnir/production.yaml @@ -7,11 +7,7 @@ pantalaimon: username: draupnir password: "" -# The management room (and most Lotus rooms) are end-to-end encrypted. Without -# crypto Draupnir can post there but can't read commands, so `!draupnir …` was -# silently ignored (LotusGuild/cinny audit, 2026-10-13). Rust crypto stores its -# keys under dataPath. -experimentalRustCrypto: true +experimentalRustCrypto: false dataPath: "/data/storage"