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

End-to-End Encryption UI Does Not Reflect Olm Failures Correctly #15655

Open
2 of 11 tasks
laky241 opened this issue Feb 21, 2025 · 2 comments
Open
2 of 11 tasks

End-to-End Encryption UI Does Not Reflect Olm Failures Correctly #15655

laky241 opened this issue Feb 21, 2025 · 2 comments

Comments

@laky241
Copy link

laky241 commented Feb 21, 2025

What happened?

When Olm is unavailable, the E2E UI behaves incorrectly:

If E2E was enabled before Olm was removed, the lock icon remains even though encryption is no longer active.

If Olm is missing when a user enables E2E, the lock icon never appears, and there is no warning that encryption is disabled.

Steps to Reproduce

Case 1: Lock Icon Stuck Even After Olm is Disabled

Join a Jitsi meeting.
Enable End-to-End Encryption.
Manually disable Olm in the browser.
Try to toggle E2E off → The lock icon remains even though encryption is inactive.

Case 2: No Lock Icon When E2E is Enabled Without Olm

Disable Olm before joining a meeting.
Join a meeting and enable End-to-End Encryption.
The lock icon never appears, and the UI gives no indication that encryption is disabled.

Image

Platform

  • Chrome (or Chromium based)
  • Firefox
  • Safari
  • Other desktop browser
  • Android browser
  • iOS browser
  • Electron app
  • Android mobile app
  • iOS mobile app
  • Custom app using a mobile SDK

Browser / app / sdk version

133.0.6943.126/127

Relevant log output

Reproducibility

  • The problem is reproducible on meet.jit.si

More details?

No response

@laky241
Copy link
Author

laky241 commented Feb 21, 2025

should i start working ?

@saghul
Copy link
Member

saghul commented Feb 22, 2025

Sure a PR would be welcome!

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

Successfully merging a pull request may close this issue.

2 participants