Encryption keys not shared in one of my DMs
See original GitHub issueSteps to reproduce
- Open a DM
- Send a message
Outcome
What did you expect?
The message can be decrypted by the recipient.
What happened instead?
Here’s the DM from the recipient (@Half-Shot)'s side:
The messages that were successfully decrypted were sent from Element Web, the ones which keys seem to be withheld were sent from Element Android.
This room (!CxwbkNeawVzFvdXwza:half-shot.uk
) is the only one impacted that I’ve seen (I’ve been able to send encrypted messages in other rooms which Half-Shot has been able to see), but this issue happens consistently with every message that I send to this room with Element Android.
Your phone model
Fairphone 3
Operating system version
Android 11
Application version and app store
Element version 1.5.2 [40105022] (G-b11679) - Matrix SDK version 1.5.2 (f6411d67) - Olm version 3.2.12 - From Play Store with beta channel joined
Homeserver
abolivier.bzh
Will you send logs?
Yes
Are you willing to provide a PR?
No
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Setting an encryption key for a replication instance
To encrypt the storage used by a replication instance, AWS DMS uses a AWS KMS key that is unique to your AWS account....
Read more >Manage Keys of Encrypted Shared Folders - Knowledge Center
Go to Control Panel > Shared Folder > Encryption > Key Manager. Click Add. Select an encrypted shared folder. Select the cypher for...
Read more >Twitter DMs likely to get end-to-end encryption; Blue returning
In a rare piece of good news about the social network, Twitter DMs (direct messages) look set to get end-to-end encryption.
Read more >What is end-to-end encryption on Instagram?
The content of your messages and calls in an end-to-end encrypted chat is ... your calls except the people who have these special...
Read more >Encrypted DMs may be coming to Twitter (assuming it survives ...
“This number was generated from your encryption keys from this ... I'm still not sure why I would move to a platform with...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I had the same problem and could fix that by deleting all “dead” sessions. I suspect (might be totally wrong here) that session A1 (my side) sent encrypted messages to session B2, that was stale / not accessible. Thus session B1 (the intended recipient) could not decrypt these messages because it could not get the required keys from session B2. Anyway it is rather unfortunate for a decrypted DM to suddenly stop working. It did not recover for three weeks.
NB: I had another session A2 open, that could still communicate without problems with peer session B1. That was rather confusing. The nontechnical user owning session B1 was not particularly impressed 😕.
They weren’t, because Element Android no longer responds to room-key-requests from other users.
Unfortunately I don’t think we can do much more here, since we don’t have the logs from when the room key should have been sent in the first place.