You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might actually get support from Discord directly, given it is something worked on by Discord (Web Crypto API might not me something great and complex like in Node's to support multiple algorithms and bunch of SSL but at least it can do cryptographically safe data generation and I suppose that might be enough, although I have little experience with stuff like diffie-hellman key exchange, password hashing and sync/async encryption algorithms implementation). That makes it low-priority, at least unless it reaches the stage I find some info Discord doesn't care about web or call it as part of "official clients".
That being said, I kinda didn't noticed that Discord actually had some plans to take care about e2ee. I'm still pesimistic about it tho, e2ee implementations within centralised services have a bad habbit of key exchange being handled by that service, and if that process is being obfuscated or badly taken care of, there are no guarantees that key you use isn't being stored somewhere or MITM isn't happening. Still, I didn't check the DAVE specifically so I have very little knowledge on it.
Description
No response
Suggestions
Add support for Discord's Audio & Video End-to-End Encryption (DAVE) protocol.
Alternatives
Official discord client
Additional Context
Library: https://github.com/discord/libdave
Protocol whitepaper: https://github.com/discord/dave-protocol https://daveprotocol.com/
The text was updated successfully, but these errors were encountered: