element-hq / element-web

A glossy Matrix collaboration client for the web.
https://element.io
GNU Affero General Public License v3.0
11.05k stars 1.97k forks source link

Unable to trust another session #23712

Closed Nono-m0le closed 2 weeks ago

Nono-m0le commented 1 year ago

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

t3chguy commented 1 year ago

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

Nono-m0le commented 1 year ago

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 commented 1 year ago

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).

richvdh commented 2 weeks ago

this seems to have bit-rotted