-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi-party E2EE voice calls via Jitsi #1147
Comments
it is not actually in release yet. |
But yes otherwise this is possible and even planned. More interestingly, Jitsi may be using some of Matrix' crypto for it:
|
It is released, I just tested it myself on the web app and desktop app (but it's not yet on Android). |
The post I linked to was written on April 12, it seems they have deployed the feature widely since then (although it's still considered in Beta). |
Well as per the doc I linked, it is still WIP and the programmatic interface is not yet stable. |
Ok I understand now. But maybe worth monitoring as it seems this progresses quite fast. |
Any updates on this? I only found talk+slides from 2021: |
It's being done without jitsi with element call |
Currently ore in the future? The source of your reference is https://www.privacyguides.org/en/real-time-communication/ which has:
|
It is being worked on, see :
It doesn't seem production ready yet but the element implementation is quite promising. |
Is your suggestion related to a problem? Please describe.
Since April 12, Jitsi Meet implements multi-party E2EE by setting a key. Up to now, Riot could only encrypt 1-on-1 voice calls, but not multiparty voice calls as this relied on Jitsi Meet which did not implement multi-party E2EE due to technical limitations at the time.
Describe the solution you'd like
It would be great if Riot could automatically setup this key when using Jitsi Meet for video calls. I am not a security expert, but a randomly generated key shared between parties through Matrix (which is E2EE by default now) may be enough?
The text was updated successfully, but these errors were encountered: