Enabling E2E in direct message channel is possible only to other member

[Gummikavalier]

Description:

Enabling E2E-encryption requires edit-room permission that normally comes with the ownership of the private channel.

When the user establishes a direct room with other user, he does not always get the ownership for that channel. E2E is missing in the menu for the lack of edit-room privilege.

Steps to reproduce:

1. Start a new direct message channel with other user
2. Check three dot menu in the message pane top right.
3. There is no E2E option to select.

Expected behavior:

There should be an E2E option in the direct messages channel for the both members of the channel.

Actual behavior:

When the user does not have ownership or edit-room permission on the direct channel:

When the user does have ownership or edit-room permission on the direct channel:

Server Setup Information:

• Version of Rocket.Chat Server: 3.0.5
• Operating System: CentOS7
• Deployment Method: tar
• Number of Running Instances: 20
• DB Replicaset Oplog: enabled
• NodeJS Version: v12.14.0
• MongoDB Version: 3.6.17

Client Setup Information

• Desktop App or Browser Version: Firefox

[Gummikavalier]

Additional testing showed that neither participant in the direct room can enable E2E. Neither one is an owner (or admin) it seems.

There will be at least an option to enable E2E by default in the version 3.1.0:
#16928

[github-actions]

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.

[Gummikavalier]

This issue is still valid in RC 3.3.3.

Current behauvior is bad because it completely prevents the use of encryption on direct channels for everybody else except for the admin accounts.

There is a global setting for admins to enable E2E for all direct channels, but since mobile clients don't support it yet, enabling it globally would make mobile clients unusable for direct communication.