Early communication on control socket can sever connection
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.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information