element-hq / element-hq/element-web

Authenticity of own messages cannot be guaranteed

Open
#17,134 0 comments 0 reactions 0 assignees View on GitHub
A-E2EE-Cross-Signing S-Tolerable T-Defect X-Needs-Community-Testing
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### Description

![obrazek](https://user-images.githubusercontent.com/15554561/116859916-06905880-ac01-11eb-8438-6b490a73d026.png)

### Steps to reproduce

- lets have multiple ecrypted and properly cross-signed devices
- all except for mobile with Element Android are offline
- send messages from Element Android in the evening
- look at those own messages in the morning on home PC - grey shields next to messages sent from Element Android previous evening, cache cleared - no change
- look at those own messages in the morning on work PC - no problem, no grey shield, same Element Web page

There shoudn't be any grey shields on home PC.

When a new Element Web session is created, all existing messages within all e2e rooms, have that error message with grey shield. New messages are ok, no grey shield is shown.

![obrazek](https://user-images.githubusercontent.com/15554561/116861052-c7630700-ac02-11eb-92a7-1e5e6fec468d.png)

### Version information

- **Platform**: web
- **Browser**: Firefox 89b7 on both PC
- **OS**: Windows
- **URL**: self hosted Element Web 1.7.26

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.