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

Creating a direct message channel, inviting a user, then turning on end to end encryption results in failure to exchange keys #11094

Open
michaeljgray opened this issue Oct 8, 2019 · 0 comments
Labels

Comments

@michaeljgray
Copy link

michaeljgray commented Oct 8, 2019

Description

Enabling end to end encryption after inviting a user to a direct chat channel presents the invited user with an error saying that the initiator of the invite needs to verify keys, even though keys are already verified.

Steps to reproduce

  • User A and User B enable "Do not send to unverified devices" on their client settings
  • User A verifies keys with User B
  • User A creates a direct chat with User B
  • Before User B accepts the invitation, user A enables end to end encryption
  • User B accepts the invitation
  • User B is presented with a key validation error
  • User B can try to initiate verification, but User A never sees it
  • User A does not see any errors

Describe how what happens differs from what you expected.

Logs being sent: yes/no

Version information

  • Platform: Desktop

For the desktop app:

  • OS: Windows 10 64-bit
  • Version: riot-web version: 1.4.2 olm version: 3.1.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant