fix(e2ee): correct misleading log messages after KDF revert (MAT-144)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
4
voice.py
4
voice.py
@@ -732,14 +732,14 @@ class VoiceSession:
|
||||
logger.warning("e2ee_state set_key failed: %s", exc)
|
||||
|
||||
await self.lk_room.connect(self.lk_url, jwt, options=room_opts)
|
||||
logger.info("Connected (E2EE=Python-HKDF+RAW), remote=%d",
|
||||
logger.info("Connected (E2EE=HKDF), remote=%d",
|
||||
len(self.lk_room.remote_participants))
|
||||
|
||||
# Set bot's own key immediately after connect — local frame cryptor exists at connect time.
|
||||
# Pre-derive via HKDF in Python since KDF_RAW is set (no Rust-side derivation).
|
||||
kp = self.lk_room.e2ee_manager.key_provider
|
||||
_derive_and_set_key(kp, bot_identity, self._bot_key, 0)
|
||||
logger.info("Set bot derived key for %s (%d raw bytes)", bot_identity, len(self._bot_key))
|
||||
logger.info("Set bot key for %s (%d bytes)", bot_identity, len(self._bot_key))
|
||||
|
||||
# Element Call rotates its key when bot joins. Wait up to 3s for the
|
||||
# rotated key to arrive via nio sync before proceeding. If it arrives,
|
||||
|
||||
Reference in New Issue
Block a user