Currently TrustedProxy = whatever must be specified in the config file by hand. I think that ZNC should automatically trust 127.0.0.0/8 and ::1 as something on localhost sending the X-Real-IP or X-Forwarded-For is setup by administrator or otherwise trusted.
With external hosts there is no way to know who has set the reverse proxy or if the user even is a reverse proxy, so TrustedProxy should be left for those.
Currently `TrustedProxy = whatever` must be specified in the config file by hand. I think that ZNC should automatically trust `127.0.0.0/8` and `::1` as something on localhost sending the `X-Real-IP` or `X-Forwarded-For` is setup by administrator or otherwise trusted.
With external hosts there is no way to know who has set the reverse proxy or if the user even is a reverse proxy, so `TrustedProxy` should be left for those.
- Debian GNU/Linux 7.9 (wheezy)
- ZNC 1.7.x-git-441-d66cb36 - http://znc.in
- IPv6: yes, SSL: yes, DNS: threads, charset: yes
<!-- github-sync-id:108442811 -->
2015-09-26 08:54:38+0300 < kerio> hell naw
2015-09-26 08:54:56+0300 < Mikaela> if naw is no, why not?
2015-09-26 08:55:21+0300 < kerio> that only works if you completely trust all the users on your box
2015-09-26 08:56:02+0300 < Mikaela> I don'ẗ think that is required as the reverse proxy makes no sense on other ports than 80/443 which are root controlled
2015-09-26 08:56:15+0300 < kerio> what
2015-09-26 08:56:20+0300 < Mikaela> and why would users on the box send false headers?
2015-09-26 08:56:52+0300 < kerio> even a supposed privileged web server won't connect to your znc from port 80
2015-09-26 08:57:13+0300 < kerio> and they'll send false headers because they're dicks, duh
I want to believe that people are better than that, but maybe that blocks this anyway.
```
2015-09-26 08:54:38+0300 < kerio> hell naw
2015-09-26 08:54:56+0300 < Mikaela> if naw is no, why not?
2015-09-26 08:55:21+0300 < kerio> that only works if you completely trust all the users on your box
2015-09-26 08:56:02+0300 < Mikaela> I don'ẗ think that is required as the reverse proxy makes no sense on other ports than 80/443 which are root controlled
2015-09-26 08:56:15+0300 < kerio> what
2015-09-26 08:56:20+0300 < Mikaela> and why would users on the box send false headers?
2015-09-26 08:56:52+0300 < kerio> even a supposed privileged web server won't connect to your znc from port 80
2015-09-26 08:57:13+0300 < kerio> and they'll send false headers because they're dicks, duh
```
I want to believe that people are better than that, but maybe that blocks this anyway.
<!-- github-comment-id:143401536 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently
TrustedProxy = whatevermust be specified in the config file by hand. I think that ZNC should automatically trust127.0.0.0/8and::1as something on localhost sending theX-Real-IPorX-Forwarded-Foris setup by administrator or otherwise trusted.With external hosts there is no way to know who has set the reverse proxy or if the user even is a reverse proxy, so
TrustedProxyshould be left for those.I want to believe that people are better than that, but maybe that blocks this anyway.