Federation allow list #673
No reviewers
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#673
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "JadedBlueEyes/federation-allow-list"
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?
This adds an
allowed_remote_server_names
. When empty, all remote servers are allowed. When set, servers not in the list are treated the same asforbidden_remote_server_names
.This additionally makes these options apply to remote media fetching and remote room directory fetching.
Not sure if ignoring messages from servers not in the allow-list is the best behaviour - it may result in some unexpected behaviour in cases like #672, where users are in a room with a non-allowed user via an allowed user. Perhaps this should be a separate option?
Unfortunately, the example config won't regenerate for me.
Tested and appears to work well (
matrix-limited-federation.pissing.dev
, only allowspissing.dev
)A useful enhancement for this and related options may be glob matching, or reading from a policy room. Out of scope for this, though.
Rebased on the latest main, but I haven't tested config live reload with this as it's not a feature I use
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.