-
Notifications
You must be signed in to change notification settings - Fork 295
feat(crypto): Add EncryptionInfo
to Decrypted
to-device variant
#5074
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
Merged
Merged
Changes from 2 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
f14ecc9
feat(crypto): Add `EncryptionInfo` to `Decrypted` to-device variant
BillCarsonFr 0c4a895
fixup: coverage, test deserialize new format
BillCarsonFr 732e9bc
review: remove un-needed Ser/DeSer for ProcessedToDeviceEvent
BillCarsonFr 5bc7184
review: use assert_let!
BillCarsonFr 519cabd
Merge branch 'main' into valere/crypto/olm_encryption_info
BillCarsonFr df2863a
review: Extract a `get_olm_encryption_info` helper function
BillCarsonFr ef03d24
review: Move current change to the top of change log
BillCarsonFr 3bfc862
fixup: post rebase cleanup, order and short syntax for dependency
BillCarsonFr File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Why the stringly typing?
Curve25519Publickey
is aCopy
type so it's cheaper to copy it around, provides stronger typing and has ato_base64()
method if you do need a string.I feel like we've been here already once.
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.
It tried to keep it consistent with the other variant.
I suppose I have then to use
serde(deserialize_with = "deserialize_curve_key", .. "serialize_curve_key"
?I'll do it too for
MegolmV1AesSha2
to stay consistantThere 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.
Actually I am not sure about this change.
To do it, I need to add vodozemac as a dependency of matrix-sdk-common (it is not yet), would I need also to add some
feature = "e2e-encryption"
cfg?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.
I had another look, and if I just refactor both Olm and Megolm variant to use
Curve25519Publickey
instead of strings, I'll need tocommon
crate to depend onvodozemac
TimelineEventKind
) we need to movedeserialize_curve_key
andserialize_curve_key
from crypto crate down to common crate (that will also bring back a dependency to zeroize).This is touching several tests files. Looks like a candidate for a separate PR