Skip to content
Snippets Groups Projects
  1. Oct 04, 2019
  2. Oct 03, 2019
  3. Oct 02, 2019
    • Brendan Abolivier's avatar
      Changelog · 24efea33
      Brendan Abolivier authored
      Unverified
      24efea33
    • Brendan Abolivier's avatar
      Lint · 972c9f65
      Brendan Abolivier authored
      Unverified
      972c9f65
    • Brendan Abolivier's avatar
      Don't 500 code when trying to exchange a revoked 3PID invite · 5705ecae
      Brendan Abolivier authored
      While this is not documented in the spec (but should be), Riot (and other clients) revoke 3PID invites by sending a m.room.third_party_invite event with an empty ({}) content to the room's state.
      When the invited 3PID gets associated with a MXID, the identity server (which doesn't know about revocations) sends down to the MXID's homeserver all of the undelivered invites it has for this 3PID. The homeserver then tries to talk to the inviting homeserver in order to exchange these invite for m.room.member events.
      When one of the invite is revoked, the inviting homeserver responds with a 500 error because it tries to extract a 'display_name' property from the content, which is empty. This might cause the invited server to consider that the server is down and not try to exchange other, valid invites (or at least delay it).
      
      This fix handles the case of revoked invites by avoiding trying to fetch a 'display_name' from the original invite's content, and letting the m.room.member event fail the auth rules (because, since the original invite's content is empty, it doesn't have public keys), which results in sending a 403 with the correct error message to the invited server.
      Unverified
      5705ecae
  4. Oct 01, 2019
  5. Sep 30, 2019
  6. Sep 27, 2019
  7. Sep 26, 2019
Loading