Opened 8 years ago

Closed 8 years ago

Last modified 7 years ago

#4654 closed defect (fixed)

Control TCP Socket not created under some circumstances

Reported by: cypherpunks Owned by:
Priority: Low Milestone: Tor: 0.2.3.x-final
Component: Core Tor/Tor Version: Tor: 0.2.3.8-alpha
Severity: Keywords: tor-client
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hi!

I had to set ControlPort to get tor to open a control socket for TCP. Setting ControlListenAddress to e.g. 10.0.1.140:12345 does not suffice.

Additionally, I had to configure any kind of authentication method. The Documentation does not state, that authentication must be used to get a control socket. It actually says, that no authentication will be used unless it is configured explicitly.

I am using version v0.2.3.8-alpha with git commit id git-68475fc5c5a806eb.

Child Tickets

Change History (4)

comment:1 Changed 8 years ago by Sebastian

Component: - Select a componentTor Client

comment:2 Changed 8 years ago by Sebastian

Resolution: fixed
Status: newclosed

This is fixed in master already, should be in the next alpha release.

comment:3 Changed 7 years ago by nickm

Keywords: tor-client added

comment:4 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.