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

After a device verification, the device is still unverified #27502

Closed
florianduros opened this issue May 27, 2024 · 2 comments
Closed

After a device verification, the device is still unverified #27502

florianduros opened this issue May 27, 2024 · 2 comments
Labels
A-E2EE-SAS-Verification A-Element-R Issues affecting the port of Element's crypto layer to Rust 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

@florianduros
Copy link
Member

Steps to reproduce

  1. Launch verification from unverified Device B
  2. Accept request from Device A
  3. Do emoji SAS between the two devices
  4. The verification ends with success
  5. But in the session settings tab, the device is still unverified (If I refresh, the device stays unverified)
Screenshot 2024-05-27 at 15 16 33

Outcome

What did you expect?

I'm expecting the device B to be verified.

What happened instead?

Operating system

No response

Browser information

No response

URL for webapp

local element

Application version

Element version: !!UNSET!! Crypto version: Rust SDK 0.7.0 (068a0af), Vodozemac 0.6.0

Homeserver

No response

Will you send logs?

Yes
@florianduros florianduros added T-Defect A-Element-R Issues affecting the port of Element's crypto layer to Rust S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Uncommon Most users are unlikely to come across this or unexpected workflow labels May 27, 2024
@dosubot dosubot bot added A-E2EE-SAS-Verification S-Critical Prevents work, causes data loss and/or has no workaround labels May 27, 2024
@BillCarsonFr
Copy link
Member

BillCarsonFr commented May 27, 2024 •
edited
Loading

It's an incomplete session problem:
Device A (existing device) : cross_signing_self_signing_privkey_cached: false

So A cannot cross-sign and can't gossip the key to device B (the new login)

So occurence of that #27655

@BillCarsonFr BillCarsonFr mentioned this issue May 27, 2024
Open
@florianduros florianduros removed the S-Critical Prevents work, causes data loss and/or has no workaround label May 27, 2024
@richvdh
Copy link
Member

richvdh commented Jun 28, 2024

Duplicate of #27655

@richvdh richvdh marked this as a duplicate of #27655 Jun 28, 2024
@richvdh richvdh closed this as completed Jun 28, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 28, 2024
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-SAS-Verification A-Element-R Issues affecting the port of Element's crypto layer to Rust 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
Milestone
No milestone
Development

No branches or pull requests
3 participants
@richvdh @florianduros @BillCarsonFr