Federation explicit denylist and allowlist support #31
Labels
No labels
Bug
Cherry-picking
Dependencies
Documentation
Duplicate
Enhancement
Good first issue
Help wanted
Inherited
Invalid
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Performance
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Priority
Unknown
Security
Wont fix
no-priority
old/blocked
old/ci/cd
old/core-matrix
old/database
old/github_actions
old/high-priority
old/low-priority
old/medium-priority
old/question
old/rocksdb
old/rust
packaging
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#31
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Similar to Synapse's options: config options and/or admin room commands to support denying federation with certain servers, and allowlist servers for an allowlist-only federation setup.
Rethinking this now, I don't think this feature is particularly useful in practice. Malicious/offensive events will just be federated to you through other servers in the room.
It's only somewhat useful for blocking DMs / room invites from a server, and even then it needs to be extended to client
/sync
not just on the receiving federation endpoints.Additionally, a private federation setup should be done with a firewall and not purely on the application level.
Conduwuit has implemented a lot of moderation utilities since this was made. If a better use-case for this comes up that existing tools cannot cover, we can look at this again. The work in the submitted PR may be repurposed or referenced for some other future things.