-
Notifications
You must be signed in to change notification settings - Fork 734
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/fix 5906 #5939
Feature/bca/fix 5906 #5939
Conversation
...android/src/main/java/org/matrix/android/sdk/internal/crypto/crosssigning/CrossSigningOlm.kt
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR, some minor comments.
...android/src/main/java/org/matrix/android/sdk/internal/crypto/crosssigning/CrossSigningOlm.kt
Outdated
Show resolved
Hide resolved
.../src/main/java/im/vector/app/features/crypto/keysbackup/settings/KeysBackupManageActivity.kt
Outdated
Show resolved
Hide resolved
...m/vector/app/features/crypto/keysbackup/settings/KeysBackupSettingsRecyclerViewController.kt
Show resolved
Hide resolved
...c/main/java/im/vector/app/features/crypto/keysbackup/settings/KeysBackupSettingsViewModel.kt
Outdated
Show resolved
Hide resolved
vector/src/main/java/im/vector/app/features/crypto/quads/SharedSecureStorageViewModel.kt
Show resolved
Hide resolved
e988804
to
da1fbb4
Compare
3eb8e42
to
8077406
Compare
This may fix some of the crypto integration tests that are going to be ignored in #6025 - will wait for this to merge before deciding the final set of tests to ignore. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (static review)
Matrix SDKIntegration Tests Results:
|
Fixes #5906
Fixes #1260
Fixes #3368
Type of change
Content
Change to keep 4S in sync with megolm backup:
If 4S is setup and you try to delete then create a new megolm backup, you will now be prompted to enter the 4S passphrase. A new random key will be generated for the backup and will be then saved in the 4S (replacing the old one), and will also be saved locally for gossiping.
Code Change => The
SharedSecureStorageActivity
has been modified to support 2 modes now, read and write. So all the code to request the password/key is the same. In the write mode you can now pass a secretName/Value to be stored.Sign & Verify backup using MSK signature.
When the backup is created we now also add the MSK signature if possible (cross signing enabled and we have private part).
The signature is also checked in order to trust the backup .
Code Change =>
KeysBackupVersionTrustSignature
is changed to a sealed class ofDeviceSignature
orUserSignature
The backup settings screens have been modified to show the new signatures.
A new class
CrossSigningOlm
has been extracted (session scope) and holds the olmPkSigning objects than can be then injected in both CrossSigningService and KeyBackupServiceScreenshots / GIFs
Tests
See step to reproduce from #5906
Unit test has been updated to check signatures
Tested devices
Checklist