Skip to content
This repository has been archived by the owner on Sep 11, 2024. It is now read-only.

Enable encryption in DMs with device keys #3913

Merged
merged 3 commits into from
Jan 23, 2020
Merged

Conversation

jryans
Copy link
Collaborator

@jryans jryans commented Jan 23, 2020

When the cross-signing lab is enabled, this changes DMs to use encryption as
long as all invited users have uploaded device keys (which we're using as a
proxy for "has some client that understands E2E").

Fixes element-hq/element-web#12005

This changes `createRoom` so it has more control of the room's initial state,
and appends state for different features, rather resetting the entire state
array. This makes room for also controlling encryption state in the next change.
When the cross-signing lab is enabled, this changes DMs to use encryption as
long as all invited users have uploaded device keys (which we're using as a
proxy for "has some client that understands E2E").

Fixes element-hq/element-web#12005
@jryans jryans requested a review from a team January 23, 2020 16:06
@jryans jryans merged commit e3027d3 into develop Jan 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Negotiate E2E by default for DMs
2 participants