| ... | ... | @@ -105,9 +105,9 @@ Yes! fairmeeting is very GDPR sensitive and does not store anything from a confe |
|
|
|
|
|
|
|
### Is fairmeeting encrypted?
|
|
|
|
|
|
|
|
Yes. fairmeeting uses the WebRTC standard, which has [encryption built in](https://jitsi.org/security). Choose a room name, nobody else can guess, unless you want visitors by chance :wink:. You can also lock a room by setting a password (and pressing return) after all participants joined. For advanced security, [E2EE can be activated](https://jitsi.org/e2ee-in-jitsi/) by sharing a common secret with the shield icon. Only supported for participants with Chrome/Chromium, MS Edge, Opera, Brave browser or the [Jitsi Desktop App](https://github.com/jitsi/jitsi-meet-electron).
|
|
|
|
Yes. fairmeeting uses the WebRTC standard, which has [encryption built in](https://jitsi.org/security). Choose a room name, nobody else can guess, unless you want visitors by chance :wink:. You can also lock a room by setting a password (and pressing return) after all participants joined.
|
|
|
|
|
|
|
|
In detail: Jitsi uses 2 layers of encryption ([source](https://community.jitsi.org/t/why-do-we-need-to-use-srtp-when-e2ee-is-enabled/127532)).
|
|
|
|
Jitsi uses 2 layers of encryption ([source](https://community.jitsi.org/t/why-do-we-need-to-use-srtp-when-e2ee-is-enabled/127532)).
|
|
|
|
|
|
|
|
- Encrypting the audio/video media at the source with AES-GCM
|
|
|
|
- Then add metadata and encrypt again with DTLS-SRTP
|
| ... | ... | |
