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

Unable to trust another session #23712

Closed
Nono-m0le opened this issue Nov 6, 2022 · 4 comments
Closed

Unable to trust another session #23712

Nono-m0le opened this issue Nov 6, 2022 · 4 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-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Needs-Investigation

Comments

@Nono-m0le
Copy link

Nono-m0le commented Nov 6, 2022

Steps to reproduce

I'm using my account on 4 devices, among 3 already trusted : Windows with Chrome, Windows with Firefox, Android with Element app and finally Linux with Firefox which I can't trust.

  1. I use the verification with another devices. Everything seems to works, until the end
  2. When I check the list of trusted devices, the latest one is not.
  3. The options "Never send encrypted messages to unverified sessions from this session" is disabled on all devices.

On the firefox logs I got that :
Verification completed! Marking devices verified:

But a bit later :

user_signing requested by SCTUYNDPNM, but not found in cache rageshake.ts:64:12
Request denied for m.cross_signing.user_signing secret for SCTUYNDPNM rageshake.ts:64:12
session backup key requested by SCTUYNDPNM, but not found in cache rageshake.ts:64:12
Request denied for m.megolm_backup.v1 secret for SCTUYNDPNM

Outcome

What did you expect?

my 4th device to be trusted

What happened instead?

My 4th devices is still not trusted

Operating system

Debian 11

Browser information

Firefox 106.0.5

URL for webapp

https://app.element.io/

Application version

Element version 1.5.4

Homeserver

matrix.org

Will you send logs?

Yes

@andybalaam andybalaam added 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 Nov 7, 2022
@t3chguy
Copy link
Member

t3chguy commented Nov 7, 2022

@Nono-m0le unfortunately am not seeing your logs, could you please upload them again, from both sides of the verification ideally? Thanks

@t3chguy t3chguy added the X-Needs-Info This issue is blocked awaiting information from the reporter label Nov 7, 2022
@Nono-m0le
Copy link
Author

Nono-m0le commented Nov 7, 2022

This is from the device I can't trust:

issue.txt
log-0.log
log-1.log
log-2.log
log-3.log
log-4.log

The other side is the Element App, I cannot run rageshake from there it seems.

@Nono-m0le
Copy link
Author

it turns out, with one of my other 2 devices, I finally suceed to trust my fourth device.
The issue remains (could it be caused because of the App ?). Let me know if I shall close the issue (as solve on my case), or let it open (as the initial issue may still raise at some point).

@t3chguy t3chguy removed the X-Needs-Info This issue is blocked awaiting information from the reporter label Nov 8, 2022
@richvdh
Copy link
Member

richvdh commented Sep 17, 2024

this seems to have bit-rotted

@richvdh richvdh closed this as completed Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Needs-Investigation
Projects
None yet
Development

No branches or pull requests

5 participants