UTD messages sent before migration to Rust Crypto are incorrectly shown as Expected UTDs #27590
Assignees
Labels
A-E2EE
A-Element-R
Issues affecting the port of Element's crypto layer to Rust
O-Occasional
Affects or can be seen by some users regularly or most users rarely
S-Minor
Impairs non-critical functionality or suitable workarounds exist
T-Defect
Z-UISI
Unable to decrypt errors
Comments
richvdh
added
T-Defect
S-Minor
dosubot
bot
added
A-E2EE
S-Major
|
@richvdh should this be a blocker to any further migration? |
richvdh
added a commit
to matrix-org/matrix-rust-sdk-crypto-wasm
that referenced
this issue
Jun 18, 2024
|
Probably. matrix-org/matrix-rust-sdk-crypto-wasm#128 should fix it. |
richvdh
removed
the
S-Major
|
Reopening until the fix lands in EW |
richvdh
added a commit
to matrix-org/matrix-js-sdk
that referenced
this issue
Jun 20, 2024
github-merge-queue bot
pushed a commit
to matrix-org/matrix-js-sdk
that referenced
this issue
Jun 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you receive a message which you cannot decrypt, using the legacy crypto stack, it is shown as a regular "Unable to Decrypt" event.
Then, if you are migrated to Rust crypto, the same message is incorrectly treated as an Expected UTD, with the error message:
(Note that you don't actually have to have seen the event on legacy crypto to hit the bug: the point is that you must have been migrated to Rust crypto after the message was sent. The migrated session is incorrectly treated as being "new".)
The text was updated successfully, but these errors were encountered: