Skip to content
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

overloaded server: Duplicate message index, possible replay attack #12855

Closed
foresto opened this issue Mar 24, 2020 · 1 comment
Closed

overloaded server: Duplicate message index, possible replay attack #12855

foresto opened this issue Mar 24, 2020 · 1 comment
Labels

Comments

@foresto
Copy link

foresto commented Mar 24, 2020

Description

The matrix.org server is overloaded today, and some messages (which often take 10-30 seconds to send) trigger error text like this:

** Unable to decrypt: Error: Duplicate message index, possible replay attack:
[CRYPTOTEXTCRYPTOTEXTCRYPTOTEXTCRYPTOTEXTCRYPTOTEXTCRYPTOTEXTCRYPTOTEXTCRYPTOTEXT] **
Re-request encryption keys from your other sessions. 

Steps to reproduce

  • Use an overloaded server
  • Chat for an hour or three
  • Watch for the spurious error messages

It looks to me like something that might happen if a messaging client retried its outgoing messages when an overloaded server didn't respond quickly, those retries were eventually accepted, and mistakenly identified as a replay attack.

If that (or similar) is indeed what is happening, it would be helpful if the system would recognize harmless retry messages, and ignore them, rather than spamming the room with noisy warning messages that are cryptic, misleading, and worrisome to average users.

Version information

This was experienced in a room that had Windows and Linux users of riot desktop, versions 1.5.12 and 1.5.13.

@turt2live
Copy link
Member

This is matrix-org/synapse#3365

t3chguy added a commit that referenced this issue Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants