matrix-org / matrix-org/matrix-spec

Concept of blocking IP users (ban by IP). (SPEC-82)

Open
#55 1 comment 0 reactions 0 assignees View on GitHub
A-Client-Server feature room-vNext
Dominant language
HTML
Stars
330
Forks
150
Avg merge
2h 21m
Merged PRs (30d)
3

Description

I as a user XMPP, appreciate it for including anonymity, but XMPP has a problem with blocking.
I do not understand why they were not smart enough to ban by ip but without disclosing it.

I suggest in Matrix make so:
1. We can to ban the already known IP (obtained outside the Matrix).
2. We can ban by IP, but the IP is not issued! You can show hash ­­– IP + salt. Salt should be become attached to the server, so that it was impossible to make some rainbow tables, and built not on the basis of the domain name, but rather on server hardware.
3. Subnet ban as for me a very bad decision, but it can be done without disclosing IP (you can do a hash on every part of IP ­­– "solthash.solthash.solthash.solthash").
4. Can make settings the server and/or rooms where specify display the IP or not, but when entering in such chatroom (which shows IP) should be a warning with confirmation for enter to the chatroom (this is important!). In addition possible in the account settings, add checkbox "not to enter the room where the displayed IP".

(Imported from https://matrix.org/jira/browse/SPEC-82)

(Reported by NightFox)

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the imported SPEC-82 request and the surrounding Matrix specification to determine where IP-ban and disclosure behavior would belong. Done would require an agreed, implementable scope for IP bans, privacy-preserving representation, subnet handling, and room-entry warnings or settings.

Written by the indexing model from the issue text.

Assessment

Domain
security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.