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

Mitigating abuse of the event depth parameter over federation #3802

Open
benparsons opened this issue May 10, 2018 · 4 comments
Open

Mitigating abuse of the event depth parameter over federation #3802

benparsons opened this issue May 10, 2018 · 4 comments
Labels
blocked Something needs to be done before action can be taken on this PR/issue. kind:core MSC which is critical to the protocol's success needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal requires-room-version An idea which will require a bump in room version s2s Server-to-Server API (federation) unassigned-room-version Remove this label when things get versioned.

Comments

@benparsons
Copy link
Member

Documentation: https://docs.google.com/document/d/16ofbjluy8ZKYL6nt7WLHG4GqSodJUWLUxHhI6xPEjr4/edit
Author: @ara4n
Date: 30/04/2018

@ara4n ara4n added the proposal A matrix spec change proposal label May 15, 2018
@turt2live turt2live added the s2s Server-to-Server API (federation) label Jul 10, 2018
@turt2live
Copy link
Member

Does this have an implementation component already?

@richvdh
Copy link
Member

richvdh commented Nov 7, 2018

Does this have an implementation component already?

Erik started work on it (PR list at matrix-org/synapse#3785), but got distracted.

A temporary mitigation was put in place via #1230.

@turt2live turt2live removed the s2s Server-to-Server API (federation) label Jan 7, 2019
@turt2live
Copy link
Member

This is still missing an implementation as far as I can tell. Downgraded from spec-pr-missing to our new "pending implementation" status. This MSC does not require a FCP due to being grandfathered from an older system, and has already been considered "accepted".

@turt2live turt2live added the s2s Server-to-Server API (federation) label Jan 7, 2019
@turt2live turt2live added the kind:core MSC which is critical to the protocol's success label Apr 21, 2020
@turt2live turt2live added the unassigned-room-version Remove this label when things get versioned. label Apr 6, 2021
@turt2live turt2live added the needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. label Jun 8, 2021
@turt2live
Copy link
Member

This is blocked on implementation, which is unlikely to happen any time soon. I'm also curious if this should go through another round of review/FCP given its age and having followed a legacy process in the past.

@turt2live turt2live added the blocked Something needs to be done before action can be taken on this PR/issue. label Jan 6, 2022
@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
@ara4n ara4n transferred this issue from matrix-org/matrix-spec May 9, 2022
@turt2live turt2live added the requires-room-version An idea which will require a bump in room version label May 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Something needs to be done before action can be taken on this PR/issue. kind:core MSC which is critical to the protocol's success needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal requires-room-version An idea which will require a bump in room version s2s Server-to-Server API (federation) unassigned-room-version Remove this label when things get versioned.
Projects
None yet
Development

No branches or pull requests

5 participants