element-hq / element-hq/element-android

Element Android does not share E2EE keys with other clients

Open
#5,305 1 comment 0 reactions 0 assignees View on GitHub
A-E2EE A-E2EE-Key-Backup O-Uncommon S-Major T-Defect
Dominant language
Kotlin
Stars
3.7k
Forks
917
PR merge metrics
No merged PRs in 30d

Description

### Steps to reproduce

1. Have a session in Android Element with everything (cross-signing, secure backup, encrypted rooms) in working order.
2. Log into Element Web )`Element version: 1.10.4; Olm version: 3.2.8`) , verify the new session with (for example) Emoji comparison.
3. Confirm your verification worked:
![20220222_16h53m34s_grim](https://user-images.githubusercontent.com/1059827/155159321-eceffc0b-b02c-46c3-9b81-2355d6ffd6c4.png)
4. **Observe Outcome**
5. Attempt to *Restore from Backup* in Element Web.
6. A message about 600 keys being imported appears.
7. **Observe Outcome**
8. Attempt to *Export E2E room keys* on Element Android
9. Upload the file (565k) in to *Import E2E room keys*
10. **Observe Outcome**
11. Click *Re-request encryption keys from your other sessions.* in a DM
12. **Observe Outcome**

### Outcome

#### What did you expect?

To be able to read other people's encrypted messages in DMs, like they show in Element Android.

#### What happened instead?

Messages from other people in two encrypted rooms do not show. Only a message
> Unable to decrypt: You are not authorised to read the message.

### Your phone model

_No response_

### Operating system version

Android 9

### Application version and app store

Element 1.4.0 [40104000] (F-d1e496624), Olm 3.2.10

### Homeserver

matrix.org

### Will you send logs?

Yes

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.