to-device messages can be processed out-of-order, causing dropped keys and decryption errors #25723
Labels
A-E2EE
O-Uncommon
Most users are unlikely to come across this or unexpected workflow
S-Major
Severely degrades major functionality or product features, with no satisfactory workaround
T-Defect
Z-Awaiting-Element-R
Issues in code which will be replaced by the port of Element's crypto layer to Rust
Events - including to-device messages - received over /sync are decrypted in parallel. libolm can handle some reordering of to-device messages: it remembers up to 40 "skipped keys", but in extreme cases, this parallelisation can cause reordering so bad that message keys are forgotten.
The text was updated successfully, but these errors were encountered: