Right now, our SOCKS handling code doesn't accept attempts to include a password authenticator in the handshake, as supported by SOCKS5. We could implement this without too much effort. The rationale for doing this was to handle SOCKS clients that don't know how _not_ to include authentication information.