|
|
@ -16,11 +16,11 @@ description: |-
|
|
|
|
the following order:
|
|
|
|
the following order:
|
|
|
|
|
|
|
|
|
|
|
|
1. If there is no `m.room.server_acl` event in the room state, allow.
|
|
|
|
1. If there is no `m.room.server_acl` event in the room state, allow.
|
|
|
|
#. If the server name is an IP address (v4 or v6) literal, and `allow_ip_literals`
|
|
|
|
2. If the server name is an IP address (v4 or v6) literal, and `allow_ip_literals`
|
|
|
|
is present and `false`, deny.
|
|
|
|
is present and `false`, deny.
|
|
|
|
#. If the server name matches an entry in the `deny` list, deny.
|
|
|
|
3. If the server name matches an entry in the `deny` list, deny.
|
|
|
|
#. If the server name matches an entry in the `allow` list, allow.
|
|
|
|
4. If the server name matches an entry in the `allow` list, allow.
|
|
|
|
#. Otherwise, deny.
|
|
|
|
5. Otherwise, deny.
|
|
|
|
|
|
|
|
|
|
|
|
**Note:**
|
|
|
|
**Note:**
|
|
|
|
Server ACLs do not restrict the events relative to the room DAG via authorisation
|
|
|
|
Server ACLs do not restrict the events relative to the room DAG via authorisation
|
|
|
|