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

Verification not possible on newly logged in windows desktop session #27056

Open
JMoVS opened this issue Feb 19, 2024 · 11 comments
Open

Verification not possible on newly logged in windows desktop session #27056

JMoVS opened this issue Feb 19, 2024 · 11 comments
Labels
A-E2EE-SAS-Verification A-Element-R Issues affecting the port of Element's crypto layer to Rust O-Occasional Affects or can be seen by some users regularly or most users rarely S-Critical Prevents work, causes data loss and/or has no workaround T-Defect

Comments

@JMoVS
Copy link

JMoVS commented Feb 19, 2024

Steps to reproduce

  1. Login to new Element Desktop on Windows session
  2. try to verify with another device
  3. an error occurs that the device could not be verified and remains in an untrusted state

Outcome

What did you expect?

verification to work

What happened instead?

various error messages resulting in an unverified session

Operating system

Windows

Application version

Element version 1.11.58

How did you install the app?

No response

Homeserver

No response

Will you send logs?

Yes

@JMoVS JMoVS added the T-Defect label Feb 19, 2024
@JMoVS
Copy link
Author

JMoVS commented Feb 19, 2024

I wouldn't be surprised if this is somehow related to the rust sdk rollout on new logins...

@t3chguy
Copy link
Member

t3chguy commented Feb 19, 2024

Will you send logs?
Yes

Please send logs.

@t3chguy t3chguy added the X-Needs-Info This issue is blocked awaiting information from the reporter label Feb 19, 2024
@JMoVS
Copy link
Author

JMoVS commented Feb 19, 2024

Logs should have just arrived from my colleague. It now somehow shows up as verified, but a different session shows up as unverified which we now removed.

@andzejsp
Copy link

can confirm im having the same problem as of last week.

For me after i scan QR code on my phone, it just stays on this screen for ever.

image

I need to end the application, and open it again to see my chats but my room encryption keys are not loaded so i cant see messages :(

@t3chguy t3chguy transferred this issue from element-hq/element-desktop Feb 22, 2024
@MidhunSureshR MidhunSureshR added S-Critical Prevents work, causes data loss and/or has no workaround A-E2EE-SAS-Verification O-Occasional Affects or can be seen by some users regularly or most users rarely A-Element-R Issues affecting the port of Element's crypto layer to Rust labels Mar 7, 2024
@github-actions github-actions bot added the Z-Labs label Mar 7, 2024
@richvdh richvdh removed the X-Needs-Info This issue is blocked awaiting information from the reporter label Mar 11, 2024
@github-actions github-actions bot removed the Z-Labs label Mar 11, 2024
@andzejsp
Copy link

So any progress on this problem? Still experiencing this.. :(

@gongarher
Copy link

Same problem here. I am unable to verify my pc session. I have tried with multiple web browsers and desktop app. Also, I have tried with different security keys, where the verification process ends successfully but my pc session remains unverified :(. I can see messages from my desktop but cannot send a single message 🙃 Any workaround here? Thanks in advance.

@andzejsp
Copy link

andzejsp commented May 4, 2024

Same problem here. I am unable to verify my pc session. I have tried with multiple web browsers and desktop app. Also, I have tried with different security keys, where the verification process ends successfully but my pc session remains unverified :(. I can see messages from my desktop but cannot send a single message 🙃 Any workaround here? Thanks in advance.

yes i found a solution, just use this client instead https://schildi.chat/desktop/

@gongarher
Copy link

Same problem here. I am unable to verify my pc session. I have tried with multiple web browsers and desktop app. Also, I have tried with different security keys, where the verification process ends successfully but my pc session remains unverified :(. I can see messages from my desktop but cannot send a single message 🙃 Any workaround here? Thanks in advance.

yes i found a solution, just use this client instead https://schildi.chat/desktop/

Thanks! That worked

@cmedcoff
Copy link

cmedcoff commented Dec 6, 2024

This is still a problem, any updates. Trying to roll this out to a new org.

Using the security key to verify won't display "looks good" until one uploads twice, and even then after pressing "Continue" the "Verify this session" pop-up/dialog remains.

@andzejsp
Copy link

andzejsp commented Dec 6, 2024

This is still a problem, any updates. Trying to roll this out to a new org.

Using the security key to verify won't display "looks good" until one uploads twice, and even then after pressing "Continue" the "Verify this session" pop-up/dialog remains.

Forget about it buddy. They were part of a diddy freak off and now in the middle of lawsuit so aint nobody got time for that... use cinny or schildi app

@cmedcoff
Copy link

cmedcoff commented Dec 6, 2024

This is still a problem, any updates. Trying to roll this out to a new org.
Using the security key to verify won't display "looks good" until one uploads twice, and even then after pressing "Continue" the "Verify this session" pop-up/dialog remains.

Forget about it buddy. They were part of a diddy freak off and now in the middle of lawsuit so aint nobody got time for that... use cinny or schildi app

What does that even mean?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE-SAS-Verification A-Element-R Issues affecting the port of Element's crypto layer to Rust O-Occasional Affects or can be seen by some users regularly or most users rarely S-Critical Prevents work, causes data loss and/or has no workaround T-Defect
Projects
None yet
Development

No branches or pull requests

7 participants