[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #8898 [Tor]: Tor says it closes socks listener, but doesn't actually close it.
#8898: Tor says it closes socks listener, but doesn't actually close it.
------------------------+---------------------------------------------------
Reporter: bastik | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor | Version: Tor: unspecified
Keywords: tor-client | Parent:
Points: | Actualpoints:
------------------------+---------------------------------------------------
With Tor 0.2.4.12-alpha on Windows 7 64 bit (probably not limited to this
set-up) Tor says it would close a socks listener, but it does not. (Lucky
me)
I added "SocksPort 127.0.0.1:9090" to my torrc which contained a similar
line with port 9001.
Because the instance is a bridge, I didn't want to close and restart Tor.
I went to the advanced settings of Vidalia and clicked on edit the current
torrc. Then I marked only the newly added line and selected "Apply
selected only".
Vidalia logged:
[Notice] Opening Socks listener on 127.0.0.1:9090
[Notice] Closing no-longer-configured Socks listener on 127.0.0.1:9001
[Notice] Closing old Socks listener on 127.0.0.1:9001
but port 9001 is still used by Tor and the connection is not broken.
When I look in the torrc now the line "SocksPort 127.0.0.1:9001" is gone,
the "SocksPort 127.0.0.1:9090" remains.
(The commented PublishServerDescriptor 0 is gone as well)
How to reproduce:
- Launch Tor with SocksPort set to some port
- Edit your torrc and add another SocksPort line
- Open Vidalia and apply only the line you added
- See what appears in the log and how it mismatches what actually happens
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8898>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs