September 17th, 2024

Dave: Discord's New End-to-End Encryption for Audio and Video

Discord has launched DAVE, an end-to-end encryption protocol for audio and video calls, ensuring only participants access content, with dynamic keys and open-source design for enhanced user privacy.

Read original articleLink Icon
Dave: Discord's New End-to-End Encryption for Audio and Video

Discord has introduced a new end-to-end encryption (E2EE) protocol for audio and video calls, named DAVE, aimed at enhancing user privacy for its 200 million monthly users. The rollout will begin with direct messages, group messages, voice channels, and Go Live streams. The DAVE protocol ensures that only call participants can access the content of their conversations, with encryption keys changing dynamically as users join or leave calls. The protocol has been developed in collaboration with cybersecurity firm Trail of Bits, which conducted a thorough review of its design and implementation. DAVE is designed to be open and auditable, with a whitepaper and open-source libraries available for public scrutiny. The protocol utilizes Messaging Layer Security (MLS) for scalable group key exchanges and maintains high-quality audio and video without compromising performance. Users will be able to verify call participants through out-of-band comparisons of verification codes. While audio and video will be encrypted, text messages will continue to follow Discord's existing content moderation policies. The transition to E2EE will be seamless for users, who will not need to manage encryption keys or device settings. Discord aims to make E2EE the default for all voice and video communications in the future.

- Discord launches DAVE, an end-to-end encryption protocol for audio and video calls.

- The protocol ensures only participants can access call content, with dynamic encryption keys.

- Developed with cybersecurity firm Trail of Bits, DAVE is open-source and auditable.

- Messaging Layer Security is used for scalable key exchanges, maintaining call quality.

- Users can verify participants through out-of-band verification codes.

Link Icon 5 comments
By @derelicta - 2 months
I don't really understand the reasoning between implementing E2EE for video and audio but not for chats in themselves. I feel like for those things, its either all or nothing, otherwise its mostly useless.
By @DrillShopper - 2 months
Cool, how about you let me use this with an open source client so I know the client isn't phoning the decrypted data home now.
By @RadiozRadioz - 2 months
I'm so tired of this. It's really simple:

If the client is proprietary and controlled by the vendor, E2EE is meaningless.

Last I checked, Discord is a proprietary application that updates itself on startup with freshly baked proprietary blobs straight from Discord Inc. They can say all they want about how great the encryption itself is, sure I believe them, but as long as alternative clients are forbidden and Discord's proprietary self-changing software exists on either end, it doesn't matter.

By @ivraatiems - 2 months
I've been watching a slow enshittification of Discord over the last few years and preparing to move to the Next Thing in a year or two, but this actually seems like a great move, and technically interesting. Is there a downside/drawback I'm not seeing?