Skip to content
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

Open
lrq3000 opened this issue Jun 8, 2020 · 10 comments
Open

Multi-party E2EE voice calls via Jitsi #1147

lrq3000 opened this issue Jun 8, 2020 · 10 comments

Comments

@lrq3000
Copy link

lrq3000 commented Jun 8, 2020

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?

@t3chguy
Copy link
Member

t3chguy commented Jun 8, 2020

NOTE e2ee is work in progress. This document describes some of the high-level concepts and outlines the design. Please refer to the source code for details.

https://github.com/jitsi/lib-jitsi-meet/blob/master/doc/e2ee.md#end-to-end-encryption-using-insertable-streams

it is not actually in release yet.

@t3chguy t3chguy added the A-Jitsi label Jun 8, 2020
@t3chguy
Copy link
Member

t3chguy commented Jun 8, 2020

But yes otherwise this is possible and even planned.

More interestingly, Jitsi may be using some of Matrix' crypto for it:

Our next step is therefore to work out exactly how key management and exchange would work. We expect we will be using The Double Ratchet Algorithm through libolm but the details are still to be ironed out.

@lrq3000
Copy link
Author

lrq3000 commented Jun 8, 2020

It is released, I just tested it myself on the web app and desktop app (but it's not yet on Android).

@lrq3000
Copy link
Author

lrq3000 commented Jun 8, 2020

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).

@t3chguy
Copy link
Member

t3chguy commented Jun 8, 2020

Well as per the doc I linked, it is still WIP and the programmatic interface is not yet stable.

@lrq3000
Copy link
Author

lrq3000 commented Jun 8, 2020

Ok I understand now. But maybe worth monitoring as it seems this progresses quite fast.

@ptman
Copy link

ptman commented Mar 13, 2023

It's being done without jitsi with element call

@t3chguy t3chguy transferred this issue from element-hq/element-web Mar 13, 2023
@rriemann
Copy link

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:

Group voice and video calls are not E2EE, and use Jitsi, but this is expected to change with Native Group VoIP Signalling. Group calls have no authentication currently, meaning that non-room participants can also join the calls. We recommend that you do not use this feature for private meetings.

@Dunexus
Copy link

Dunexus commented Apr 28, 2023

It is being worked on, see :

It doesn't seem production ready yet but the element implementation is quite promising.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants