-
Notifications
You must be signed in to change notification settings - Fork 213
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
Add event decryption decoration #1743
Conversation
31f4b85
to
8cfde97
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## develop #1743 +/- ##
===========================================
+ Coverage 25.83% 25.85% +0.02%
===========================================
Files 615 616 +1
Lines 96992 97076 +84
Branches 41796 41832 +36
===========================================
+ Hits 25060 25102 +42
- Misses 71114 71155 +41
- Partials 818 819 +1
... and 9 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
Hi @Anderas, |
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 😎
changelog.d/pr-1743.change
Outdated
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.
Should we have a .api
changelog too that documents the removal of the untrusted
property and its replacements for other users of the SDK?
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.
Yea that makes sense, renamed. thx
04894c0
to
a7c9b01
Compare
a7c9b01
to
9e5a4ac
Compare
Previously the legacy SDK would expose
untrusted
property to mark events that were decrypted using an untrusted key (e.g. one downloaded from asymmetrical backup). On the app side, this untrusted property would be combined with other encryption properties, namely the trust of the sender and their device. Only then the combine result gets turned into a visual decoration (e.g. red or grey shield).To improve this, and align with rust-sdk, expose the decoration color directly from the crypto SDK, alongside an explanation message if necessary. This moves some of the trust computation down to the crypto module and leaves the app with fewer decisions to make.