-
Notifications
You must be signed in to change notification settings - Fork 711
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
Feature/bca/e2e message info #5006
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Matrix SDKIntegration Tests Results:
|
BillCarsonFr
force-pushed
the
feature/bca/e2e_message_info
branch
from
January 21, 2022 08:16
3c076e2
to
724a39d
Compare
BillCarsonFr
force-pushed
the
feature/bca/e2e_message_info
branch
from
February 4, 2022 14:57
724a39d
to
8c321ba
Compare
Not ready to be merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #4891
Add a new developer mode screen to review cryptography info for a message. This screen allows to see details on the key sharing process, as well as to manually review incoming room key requests (that could allow to recover from an unable to decrypt error)
The new screen is accessible from the message context menu
This screen displays several informations regarding e2e:
- List of incoming room request from devices that couldn't decrypt
- List of all user|device this key was originaly shared with
- An option to re-request the keys
Incoming room key requests can be reviewed, and the user can decide to manually forward the key (even if the request was declined initialy)