[tor-bugs] #22572 [Core Tor/Tor]: please don't kill WarnUnsafeSocks option
Tor Bug Tracker & Wiki
blackhole at torproject.org
Sun Jun 18 15:01:50 UTC 2017
#22572: please don't kill WarnUnsafeSocks option
--------------------------+------------------------------------
Reporter: starlight | Owner:
Type: defect | Status: reopened
Priority: Medium | Milestone:
Component: Core Tor/Tor | Version: Tor: 0.2.9.2-alpha
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------+------------------------------------
Changes (by cypherpunks):
* status: closed => reopened
* resolution: not a bug =>
Comment:
Replying to [comment:7 starlight]:
> Not so fast! It's been awhile since this was a bother and I forgot that
the log spamming occurs on an control channel event monitoring stream.
With `WarnUnsafeSocks=1` this log is still flooding with pointless
messages when DNS queries are purposefully sent over a Tor connection. I
have restored `WarnUnsafeSocks=0` and my position remains that the setting
is useful at least up to and including 0.2.9.x. I have not tested 0.3.0.x
versions.
The code referred to in comment:3 sends out the controller message no
matter the value of `SafeSocks`. I'm assuming this is to prevent
configuration options from hiding events from the controllers.
Because this is now about the controller message it sounds like a
duplicate of #22461. Can you check if your issue is a duplicate of #22461?
If it's not a duplicate, can you give some more information about your
setup in order to reproduce the issue?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22572#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list