Opened 4 years ago

Last modified 21 months ago

#15661 new defect

Same "non-loopback address" notice is printed twice

Reported by: yurivict271 Owned by:
Priority: Very Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: easy, intro, usability tor-relay torrc configuration bootstrap
Cc: Actual Points:
Parent ID: Points: small
Reviewer: Sponsor:

Description

The following command line produces each notice twice.

This is not a big deal, but something is wrong in the code and needs to be fixed.

/usr/local/bin/tor --ignore-missing-torrc -f /no/file --PidFile /var/tmp/vbox-to-tor/tap7/tor.pid --RunAsDaemon 1 --DataDirectory /var/tmp/vbox-to-tor/tap7/data --+Log "notice file /var/tmp/vbox-to-tor/tap7/tor.log" --DNSPort 53 --DNSListenAddress 172.16.7.1 --TransPort 9030 --TransListenAddress 172.16.7.1 --SocksPort 0
Apr 12 21:38:09.478 [notice] Tor v0.2.6.6 (git-bb8c4e69ca5c8bca) running on FreeBSD with Libevent 2.0.22-stable, OpenSSL 1.0.2a and Zlib 1.2.8.
Apr 12 21:38:09.478 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Apr 12 21:38:09.478 [notice] Configuration file "/no/file" not present, using reasonable defaults.

Apr 12 21:38:09.483 [notice] You configured a non-loopback address '172.16.7.1:53' for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Apr 12 21:38:09.483 [notice] You configured a non-loopback address '172.16.7.1:9030' for TransPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Apr 12 21:38:09.484 [notice] You configured a non-loopback address '172.16.7.1:53' for DNSPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Apr 12 21:38:09.485 [notice] You configured a non-loopback address '172.16.7.1:9030' for TransPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Apr 12 21:38:09.485 [notice] Opening DNS listener on 172.16.7.1:53
Apr 12 21:38:09.485 [notice] Opening Transparent pf/netfilter listener on 172.16.7.1:9030
Apr 12 21:38:09.485 [warn] Fixing permissions on directory /var/tmp/vbox-to-tor/tap7/data

Child Tickets

Change History (10)

comment:1 Changed 4 years ago by gk

Component: - Select a componentTor

comment:2 Changed 3 years ago by nickm

Milestone: Tor: 0.2.8.x-final

comment:3 Changed 3 years ago by nickm

Points: small
Priority: normaltrivial

comment:4 Changed 3 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.???

Move a bunch of (but not all) low-priority items to 0.2.???. If you write a patch, it can still get into 0.2.8

comment:5 Changed 3 years ago by teor

Severity: Normal

This could be related to #15380.

comment:6 Changed 2 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:7 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:8 Changed 22 months ago by nickm

Keywords: easy intro added

comment:9 Changed 22 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:10 Changed 21 months ago by nickm

Keywords: usability tor-relay torrc configuration bootstrap added
Note: See TracTickets for help on using tickets.