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
Change default text about "full encryption" #5659
Comments
Technically one could discuss that "fully encrypted" does not pretend to mean "end to end encrypted". Everything that goes over the network still is "fully encrypted"? But yeah, I can understand why people might say it is misleading. |
Exactly. No unencrypted data is ever transported. So it’s fully encrypted in transit, and since nothing is stored at rest, that’s all there is to it. We are not saying it’s E2EE, because it’s not, yet. |
Please see: https://jitsi.org/news/security/ |
@saghul
And this is the actual problem. The term "fully encrypted" suggests that nobody except the meeting participants can access audio and video. According to your post on GitHub and the linked blog post, this isn't the case since everything is decrypted on the server. Even if the streams aren't written to permanent storage by default, it isn't "fully secure." A server-side attacker can record streams due to missing encryption. So you should at least clarify in the "fully encrypted" statements that this only applies to data in transit. |
Fully encrypted != Fully encrypted in transit. That qualifier is non-trivial. You cannot omit it and argue that it still technically means the same, because it simply does not. FWIW, the phrase "fully encrypted in transit" would be misleading. "Fully encrypted" is simply false. |
We started a poll in the Fediverse. The results after 220 votes:
The results clearly show that "fully encrypted" is actually a misleading term. |
As for why "fully encrypted in transit" is misleading, imagine a physical package containing some server hardware being sent from a manufacturer to a customer. Customers might care about security and request that the manufacturer sends servers in a locked box only for the customer to unlock and open it. One might call that "fully locked in transit". Then imagine these boxes were opened, and re-locked in transport hubs. Would that still qualify as "fully locked in transit"? Technically when the boxes are opened they are temporarily not "in transit" as they are sitting in a transport hub waiting to be put onto the next leg of their trip to the customer. |
@saghul Contrary to this, 74% think that it means "end-to-end encryption" which is clearly not the case. |
I want to voice my support for clarifying exactly what you mean by "fully encrypted" as OP suggested. Having to dig up this information on Github from community suggestions is not ideal, but the suggested solution is both reasonable and concise. Thanks for considering! |
"P2P calls are end-to-end encrypted, group calls are protected by transport encryption" may intimidate casual users because it contains too much jargon. Furthermore, even that could be considered misleading, because two-party calls may fail to negotiate a direct peer-to-peer connection and fall back to being relayed through the bridge. I'd suggest simply dropping the word "fully" from "fully encrypted". No meaning would be lost, and it would no longer imply anything about the strength of the encryption system. Anyone who wants to research the details can do so — but the front page is not the place for such details. |
Good idea! You could simply embed the security url directly into the word encryption, because taking the time to read this blurb likely means you do want to know: I count myself amongst this crowd. 👍 example: Jitsi is an encrypted, 100% open source video conferencing solution that you can use all day, every day, for free — with no account needed. |
Is your feature request related to a problem you are facing?
The default landing pages of Jitsi instances currently state "In fact, invite everyone you know. {{app}} is a fully encrypted, 100% open source video conferencing solution that you can use all day, every day, for free — with no account needed." Example
According to your own GitHub repo and this post, this isn't actually the case.
Describe the solution you'd like
Change the default text to something like:
"In fact, invite everyone you know. {{app}} is a 100% open source video conferencing solution that you can use all day, every day, for free — with no account needed. P2P calls are end-to-end encrypted, group calls are protected by transport encryption."
In addition, P2P calls are only E2E encrypted if they aren't use the Jitsi Videobridge. Only a suggestion, the final text could be much shorter.
Besides, the same applies to https://jitsi.org/jitsi-meet/. Here it is stated: "Jitsi Meet is a fully encrypted, 100% open source video conferencing solution that you can use all day, every day, for free — with no account needed."
The text was updated successfully, but these errors were encountered: