Opened 8 years ago

Closed 8 years ago

Last modified 7 years ago

#4523 closed defect (invalid)

Early communication on control socket can sever connection

Reported by: atagar Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords: tor-relay
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

When tor has a control port you can start interacting with the port when bootstrapping indicates that it has reached 5%. There are three things you can send on this initially established port...

  • PROTOCOLINFO
  • AUTHENTICATE
  • anything else => "Authentication required.\r\n"

When tor has a ControlSocket, however, you can issue an AUTHENTICATE or PROTOCOLINFO but anything else will cause the socket connection to be closed (without an "Authentication required." response).

This only happens while tor is initially bootstrapping. I ran into this while writing the stem integ tests and if I introduced a ten second wait before trying to use the control socket tor properly gives an "Authentication required." response.

This is with Tor v0.2.1.30.

Child Tickets

Change History (3)

comment:1 Changed 8 years ago by atagar

Resolution: invalid
Status: newclosed

Ahhh, oops. Misunderstood the socket response, it was actually working fine but just breaking the socket pipe in a manner I didn't expect. Sorry about the noise. :)

comment:2 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:3 Changed 7 years ago by nickm

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