MXRealmCryptoStore: Make sure secrets in the DB are encrypted #1027
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.
Fix element-hq/element-ios#3867
Require https://gitlab.matrix.org/matrix-org/olm/-/merge_requests/17.
It embeds the realm db migration code refactoring made in #973 even if no migration is required here.
We cannot use the built-in encryption offered by Realm because it does not support multi-process. So, let's encrypt every single thing in a clear Realm db.