After having issues with users playing with experimental E2EE, I tried to disable the feature, but it is still shown.
Steps to reproduce:
testing: {
// Disables the End to End Encryption feature. Useful for debugging
// issues related to insertable streams.
disableE2EE: true,
Expected behavior:
E2EE should not be listed in the security modal window.
Actual behavior:
E2EE should is listed in the security modal window.
Server information:
Jitsi on Debian 10.9:
ii jitsi-meet 2.0.5765-1 all WebRTC JavaScript video conferences
ii jitsi-meet-prosody 1.0.4900-1 all Prosody configuration for Jitsi Meet
un jitsi-meet-tokens <none> <none> (no description available)
ii jitsi-meet-turnserver 1.0.4900-1 all Configures coturn to be used with Jitsi Meet
ii jitsi-meet-web 1.0.4900-1 all WebRTC JavaScript video conferences
ii jitsi-meet-web-config 1.0.4900-1 all Configuration for web serving of Jitsi Meet
un jitsi-videobridge <none> <none> (no description available)
ii jitsi-videobridge2 2.1-478-gc6da57bd-1 all WebRTC compatible Selective Forwarding Unit (SFU)
Client information:
Chrome macOS, Jitsi-Meet-Electron macOS.
Additional information:
According to @saghul it "looks like when we refactored things around we no longer honor disableE2EE."
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Description:
After having issues with users playing with experimental E2EE, I tried to disable the feature, but it is still shown.
Steps to reproduce:
Expected behavior:
E2EE should not be listed in the security modal window.
Actual behavior:
E2EE should is listed in the security modal window.
Server information:
Jitsi on Debian 10.9:
Client information:
Chrome macOS, Jitsi-Meet-Electron macOS.
Additional information:
According to @saghul it "looks like when we refactored things around we no longer honor disableE2EE."