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

Another device verification doesn't give access to keys backup #20699

Closed
waclaw66 opened this issue Jan 24, 2022 · 1 comment
Closed

Another device verification doesn't give access to keys backup #20699

waclaw66 opened this issue Jan 24, 2022 · 1 comment
Labels
A-E2EE A-E2EE-SAS-Verification O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect

Comments

@waclaw66
Copy link
Contributor

waclaw66 commented Jan 24, 2022

Steps to reproduce

There is a big difference when a new device is verified with another device or with a phrase.

obrazek

With a phrase it gives instant access to server backup of keys and all encrypted messages are immediately decrypted.

On the other hand, when a device is verified with another device, you can see many messages
** Unable to decrypt: The sender's device has not sent us the keys for this message. **
until keys are fetched from other devices. And very often they are not.

Outcome

What did you expect?

There should not be different outcome depending on used verification method.
There is no such problem with Element Android.

What happened instead?

Another device verification gives you bad user experience.

Operating system

Windows 10

Browser information

Firefox 96b10

URL for webapp

own

Application version

Element version: 1.9.9 Olm version: 3.2.8

Homeserver

own

Will you send logs?

No

@germain-gg germain-gg added A-E2EE A-E2EE-SAS-Verification O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround labels Jan 24, 2022
@richvdh
Copy link
Member

richvdh commented Jan 21, 2025

Sounds like the other device didn't have the key backup key to share with you. Tracked at element-hq/element-meta#2642

@richvdh richvdh closed this as completed Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE A-E2EE-SAS-Verification O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect
Projects
None yet
Development

No branches or pull requests

3 participants