Log the correct "auto" port number for listening sockets

When "auto" was used for the port number for a listening socket, the
message logged after opening the socket would incorrectly say port 0
instead of the actual port used.

Fixes bug 29144; bugfix on 0.3.5.1-alpha

Signed-off-by: Kris Katterjohn <katterjohn@gmail.com>
This commit is contained in:
Kris Katterjohn 2019-01-21 13:12:53 -06:00 committed by teor
parent de0969ef78
commit 389ee834b6
No known key found for this signature in database
GPG Key ID: 10FEAA0E7075672A
2 changed files with 6 additions and 1 deletions

5
changes/bug29144 Normal file
View File

@ -0,0 +1,5 @@
o Minor bugfixes (logging):
- Log the correct port number for listening sockets when "auto" is
used to let Tor pick the port number. Previously, port 0 was
logged instead of the actual port number. Fixes bug 29144;
bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.

View File

@ -1527,7 +1527,7 @@ connection_listener_new(const struct sockaddr *listensockaddr,
conn_type_to_string(type), conn->address);
} else {
log_notice(LD_NET, "Opened %s on %s",
conn_type_to_string(type), fmt_addrport(&addr, usePort));
conn_type_to_string(type), fmt_addrport(&addr, gotPort));
}
return conn;