It sends complete garbage to SOCKS5 as well

[makkarpov]

Steps to reproduce:

1. Start TOR instance
2. Specify socks://localhost:9150 as your entry proxy.
3. Try to connect

Well, expected behaviour is obvious. Actual behaviour - nothing happens. And here is why:

Client closes connection afterwards. But it's successfull password authentication. If you specify upstream proxy that does not require authentication (e.g. SSH with -D xxx), it works:

So, first of all -- do not announce that you support password authentication when actually you have no credentials to send, second -- your client breaks connection even after successfull authentication.