-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
It should be possible to configure a list of IPs synapse will not make outbound connections to #3953
Comments
There's really no point in checking for destinations called "localhost" because there is nothing stopping people creating other DNS entries which point to 127.0.0.1. The right fix for this is #3953. Blocking localhost, on the other hand, means that you get a surprise when trying to connect a test server on localhost to an existing server (with a 'normal' server_name).
fixed by #5043 |
Is it possible to blacklist a domain like this? I got thousands of warnings in my log about a domain, that is not reacheable any more |
@rubo77 We don't support blacklisting a domain (yet), but if you can resolve the DNS to an IP address you should be able to add it to Alternatively it could be blocked at the firewall level. |
I guess there is no use to block a domain, that is not reacheable anyway. I tried this:
But this didn't have any effect, I still get errors like
|
We have
url_preview_ip_range_blacklist
, but no equivalent for federation requests. The attack surface is of course much smaller, but I still don't like the idea of my synapse going and hitting random HTTP servers within my firewall because someone pointed a DNS record at them. In particular, it's currently possible to make synapse send requests back to itself with a DNS record which resolves to 127.0.0.1The text was updated successfully, but these errors were encountered: