Tor socks5 auth spec violation

[handpickencounter]

Username should always be

<torS0X>0

https://spec.torproject.org/socks-extensions.html

If the SOCKS5 Username/Password fields are present but the Username does not begin with this byte sequence, it indicates legacy isolation. New client implementations SHOULD NOT use legacy isolation. A SocksPort may be configured to reject legacy isolation.

These extensions are in use whenever the SOCKS5 Username begins with the 8-byte "magic" sequence [3c 74 6f 72 53 30 58 3e]. (This is the ASCII encoding of ).

When the format type is [30] (the ascii encoding of 0), we interpret the rest of the Username field and the Password field as follows:

The remainder of the Username field must be empty.

The Password field is stream isolation parameter. If it is empty, the stream isolation parameter is an empty string.

[JeremyRand]

Interesting, I wasn't aware of this spec change. Should be straightforward to support. Thanks for the heads up.