security
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| security [2026/03/30 02:16] – admin | security [2026/03/30 02:34] (current) – admin | ||
|---|---|---|---|
| Line 18: | Line 18: | ||
| * Security And Privacy Notes: | * Security And Privacy Notes: | ||
| * While messages are encrypted in E2EE rooms, privacy leaks are possible. Metadata is not encrypted and currently not supported by the protocol, although it' being worked on.This includes usernames of who are in encrypted chat rooms, who created the room, and the title of the room. | * While messages are encrypted in E2EE rooms, privacy leaks are possible. Metadata is not encrypted and currently not supported by the protocol, although it' being worked on.This includes usernames of who are in encrypted chat rooms, who created the room, and the title of the room. | ||
| - | * Homeserver owners can join encrypted chats and impersonate users by adding their own device key to the target users account. | + | * Homeserver owners can join encrypted chats technically. They would have to impersonate users by adding their own device key to the targeted user account. |
| * A stolen domain for homeserver can gain rights as any user that has joined the room from the homeserver, This is due to Matrix stores permissions as user@homeserverDomain.com for rooms. | * A stolen domain for homeserver can gain rights as any user that has joined the room from the homeserver, This is due to Matrix stores permissions as user@homeserverDomain.com for rooms. | ||
| * Fluffychat client is recommended, | * Fluffychat client is recommended, | ||
| * Users joining E2EE encrypted rooms can not see past messages. This is being worked on currently (https:// | * Users joining E2EE encrypted rooms can not see past messages. This is being worked on currently (https:// | ||
security.txt · Last modified: 2026/03/30 02:34 by admin