-
Notifications
You must be signed in to change notification settings - Fork 493
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Negotiate E2E by default for DMs #2943
Labels
A-E2EE
feature
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements
Milestone
Comments
manuroe
added this to the Sprint 25: Cross-signing and e2e by default - phase 1 milestone
Jan 27, 2020
manuroe
added a commit
to matrix-org/matrix-ios-sdk
that referenced
this issue
Jan 28, 2020
manuroe
added a commit
that referenced
this issue
Jan 28, 2020
manuroe
added a commit
that referenced
this issue
Jan 28, 2020
Kamino cloned this issue to vector-im/riotX-android |
kittykat
added
the
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements
label
Apr 6, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-E2EE
feature
T-Enhancement
New features, changes in functionality, performance boosts, user-facing improvements
From riot-web created by jryans: element-hq/element-web#12005
When the cross-signing labs flag is on, we want to create DMs as E2E by default. There are no UX changes or toggles in the create DM flow for this. Since not all users support E2E yet (bots, bridges, people with only non-E2E clients), we need to be a bit careful.
When creating the DM room, check if the other user has shared device keys. If yes, then create an encrypted room, otherwise fallback to unencrypted.
The text was updated successfully, but these errors were encountered: