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.

Sign up for GitHub

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

Jump to bottom

new session shown as not trusted, despite doing the verification dance #22962

Closed
richvdh opened this issue Jul 29, 2022 · 7 comments
Closed

new session shown as not trusted, despite doing the verification dance #22962

richvdh opened this issue Jul 29, 2022 · 7 comments
Labels
A-E2EE A-E2EE-Cross-Signing A-E2EE-SAS-Verification O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect X-Needs-Investigation

Comments

@richvdh
Copy link
Member

richvdh commented Jul 29, 2022

Steps to reproduce

  1. start a new eleweb session
  2. verify it from another device (QR code scan)
  3. new session still shows as not trusted

Outcome

What did you expect?

Device should be shown as verified

What happened instead?

I, and others, see my new session as unverified

image

image

Operating system

Ubuntu 22.04

Application version

Element Nightly version: 2022071901 Olm version: 3.2.8

How did you install the app?

nightly debian

Homeserver

synapse 1.61.0

Will you send logs?

Yes
@richvdh
Copy link
Member Author

richvdh commented Jul 29, 2022

possibly again related to lack of gnome-keyring?

@richvdh
Copy link
Member Author

richvdh commented Jul 29, 2022

I tried to do the verification again with an emoji comparison, but no improvement.

@turt2live turt2live added S-Minor Impairs non-critical functionality or suitable workarounds exist X-Needs-Investigation O-Uncommon Most users are unlikely to come across this or unexpected workflow labels Aug 5, 2022
@richvdh
Copy link
Member Author

richvdh commented Aug 9, 2022

Is this maybe the same as #21919?

@richvdh
Copy link
Member Author

richvdh commented Aug 9, 2022

btw it is 100% reproducible for me - no matter how many times I do the verification dance it doesn't help.

@richvdh
Copy link
Member Author

richvdh commented Aug 9, 2022

oh, or possibly vector-im/element-meta#1879 is a closer match

@richvdh richvdh mentioned this issue Aug 12, 2022
Closed
@MichaelErjemenko
Copy link

I observe the same behaviour for two accounts, but cannot reproduce it for one of my own accounts.

  1. New device_b login (Chrome)
  2. old and verified device_a (Android Element-App) verifies device_b
  3. device_b can decrypt all messages
  4. device_b is shown as unverified like already descirbed in the issue desciption

@richvdh
Copy link
Member Author

richvdh commented Oct 31, 2022

well, this seems to have fixed itself somewhere along the line.

@richvdh richvdh closed this as completed Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-E2EE A-E2EE-Cross-Signing A-E2EE-SAS-Verification O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect X-Needs-Investigation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@dkasak @turt2live @richvdh @MichaelErjemenko