mirror of
https://github.com/ergochat/ergo.git
synced 2024-11-10 22:19:31 +01:00
Merge pull request #1239 from slingamn/issue1228_disable_lookup_hostnames
fix #1228
This commit is contained in:
commit
c8e2dcb1e9
10
default.yaml
10
default.yaml
@ -141,10 +141,11 @@ server:
|
||||
# they cannot be relayed to websocket clients).
|
||||
enforce-utf8: true
|
||||
|
||||
# whether to look up user hostnames with reverse DNS.
|
||||
# (disabling this will expose user IPs instead of hostnames;
|
||||
# to make IP/hostname information private, see the ip-cloaking section)
|
||||
lookup-hostnames: true
|
||||
# whether to look up user hostnames with reverse DNS. there are 3 possibilities:
|
||||
# 1. lookup-hostnames enabled, IP cloaking disabled; users will see each other's hostnames
|
||||
# 2. lookup-hostnames disabled, IP cloaking disabled; users will see each other's numeric IPs
|
||||
# 3. [the default] IP cloaking enabled; users will see cloaked hostnames
|
||||
lookup-hostnames: false
|
||||
# whether to confirm hostname lookups using "forward-confirmed reverse DNS", i.e., for
|
||||
# any hostname returned from reverse DNS, resolve it back to an IP address and reject it
|
||||
# unless it matches the connecting IP
|
||||
@ -258,6 +259,7 @@ server:
|
||||
# DNS, users see fake domain names like pwbs2ui4377257x8.oragono. These names are
|
||||
# generated deterministically from the underlying IP address, but if the underlying
|
||||
# IP is not already known, it is infeasible to recover it from the cloaked name.
|
||||
# If you disable this, you should probably enable lookup-hostnames in its place.
|
||||
ip-cloaking:
|
||||
# whether to enable IP cloaking
|
||||
enabled: true
|
||||
|
Loading…
Reference in New Issue
Block a user