Incorrect "non-loopback address" warnings
When running Tor in a FreeBSD jail with the IP address 10.0.0.2, a torrc that contains these directives: TransListenAddress 127.0.0.1 SocksListenAddress 10.0.0.2 ControlListenAddress 127.0.0.1 Results in these messages: ``` Dec 31 11:27:31.879 [notice] Tor v0.2.4.7-alpha (git-e46e1ed1bc50ad24) (with bufferevents) running on FreeBSD with Libevent 2.0.16-stable and OpenSSL 1.0.1c. Dec 31 11:27:31.880 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Dec 31 11:27:31.880 [notice] This version is not a stable Tor release. Expect more bugs than usual. Dec 31 11:27:31.880 [notice] Read configuration file "/usr/local/etc/tor/torrc". Dec 31 11:27:31.893 [notice] You configured a non-loopback address '10.0.0.2:9050' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted. Dec 31 11:27:31.893 [notice] You configured a non-loopback address '10.0.0.2:9050' for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted. Dec 31 11:27:31.893 [notice] You configured a non-loopback address '10.0.0.2:9050' for TransPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted. [...] Dec 31 11:27:31.895 [notice] You configured a non-loopback address '10.0.0.2:9050' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted. Dec 31 11:27:31.895 [notice] You configured a non-loopback address '10.0.0.2:9050' for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted. Dec 31 11:27:31.895 [notice] You configured a non-loopback address '10.0.0.2:9050' for TransPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted. Dec 31 11:27:31.895 [notice] Opening Socks listener on 10.0.0.2:9050 Dec 31 11:27:31.896 [notice] Opening DNS listener on 127.0.0.1:53 Dec 31 11:27:31.896 [notice] Opening Transparent pf/netfilter listener on 127.0.0.1:9040 Dec 31 11:27:31.896 [notice] Opening Control listener on 127.0.0.1:9051 Dec 31 11:27:31.896 [notice] Opening Control listener on /var/run/tor/tor-socket ``` The fact that some messages are shown twice is legacy/trac#4019, this report is about the incorrect warnings for the listeners on 127.0.0.1. It looks like the Socks address 10.0.0.2:9050 is used for all complaints. With a torrc that contains these directives: TransListenAddress 127.0.0.1 SocksListenAddress 127.0.0.1 ControlListenAddress 127.0.0.1 No warnings are shown, even though the risk (in the described FreeBSD jail) is equivalent. ``` Dec 31 12:19:17.414 [notice] Tor v0.2.4.7-alpha (git-e46e1ed1bc50ad24) (with bufferevents) running on FreeBSD with Libevent 2.0.16-stable and OpenSSL 1.0.1c. Dec 31 12:19:17.415 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Dec 31 12:19:17.415 [notice] This version is not a stable Tor release. Expect more bugs than usual. Dec 31 12:19:17.415 [notice] Read configuration file "/usr/local/etc/tor/torrc". [...] Dec 31 12:19:17.431 [notice] Opening Socks listener on 127.0.0.1:9050 Dec 31 12:19:17.431 [notice] Opening DNS listener on 127.0.0.1:53 Dec 31 12:19:17.431 [notice] Opening Transparent pf/netfilter listener on 127.0.0.1:9040 Dec 31 12:19:17.431 [notice] Opening Control listener on 127.0.0.1:9051 Dec 31 12:19:17.431 [notice] Opening Control listener on /var/run/tor/tor-socket ```
issue