E2E - Unable to read messages on a private channel on 4.3.1 version

Description:

Hi everyone,

In connection with the tests, for the E2E functionality, there was a problem relating to private room encryption. In some cases, it is not possible to decrypt messages after reset E2E key.

Steps to reproduce:

1. Enable E2E encryption feature in administration panel
2. Log in to the account of two users
3. Accept the encyption feature and save the key password (this applies to two users)
4. Create private room, enable E2E encryption and add second user.
5. Start typing test messages
6. Reset E2E key on owner and user account.
7. Log in to the rocket.chat again
8. After obtaining new keys, we are unable to decrypt previous messages.

Expected behavior:

After changing the encryption key, both the user and the administrator do not have access to resources in the form of encrypted messages. The channel is unreadable to both sides.

Actual behavior:

Due to the possibility of losing the password to the existing key, there should be a better security in terms of gaining possible access to previous messages. In some cases it is impossible.

Server Setup Information:

• Version of Rocket.Chat Server: 4.3.1
• Operating System: CentOS Linux 7 (Core)
• Deployment Method: docker
• Number of Running Instances: 3
• DB Replicaset Oplog: 3
• NodeJS Version: X
• MongoDB Version: 4.0.14 / wiredTiger (oplog Enable)

Client Setup Information

• Desktop App or Browser Version: Desktop App & Browser version
• Operating System: Windows 10 Pro

Additional context

Relevant logs:

The report names no source files, tests, or entry points. Reproduce the issue on Rocket.Chat 4.3.1 using the listed two-user private-room and E2E key-reset steps, then clarify the conflicting expected and actual behavior before locating the encryption flow and defining the correct result.