On 08 Mar (06:12:41), Yawning Angel wrote:
On Fri, 7 Mar 2014 10:45:14 -0500
David Goulet dgou...@ev0ke.net wrote:
Quoting rfc1928:
When a reply (REP value other than X'00') indicates a failure, the
SOCKS server MUST terminate the TCP connection shortly after sending
the reply. This
On Sat, 8 Mar 2014 09:08:06 -0500
David Goulet dgou...@ev0ke.net wrote:
[snippity]
I can see one use for having custom keys along with a name space
which is to having a way to identify the SOCKS connection on the
control port for knowing in which country the exit is for
instance (or
Sorry this response took so long. I've been kind of busy.
On Sat, 01 Mar 2014 13:57:34 +0100
Sebastian G. bastik.tor bastik@googlemail.com wrote:
To me it is clear that the two are messed up, but I'm not sure what's
the correct order.
Indeed. Since there isn't a clear advantage to going
On 07 Mar (14:03:35), Yawning Angel wrote:
Sorry this response took so long. I've been kind of busy.
On Sat, 01 Mar 2014 13:57:34 +0100
Sebastian G. bastik.tor bastik@googlemail.com wrote:
To me it is clear that the two are messed up, but I'm not sure what's
the correct order.
On Fri, 7 Mar 2014 10:45:14 -0500
David Goulet dgou...@ev0ke.net wrote:
Quoting rfc1928:
When a reply (REP value other than X'00') indicates a failure, the
SOCKS server MUST terminate the TCP connection shortly after sending
the reply. This must be no more than 10 seconds after detecting
28.02.2014 09:53, Yawning Angel:
2.2. Tor Extended SOCKS5 Reply Codes
We introduce the following additional SOCKS5 reply codes to be sent
in the REP field of a SOCKS5 message. Implementations MUST NOT
send any of the extended codes unless the initiator has indicated
that it understands the
Hello all,
Based on feedback from nickm/arma, I have extended the proposal to also
cover Tor's SOCKS port, including response codes related to hidden
service status.
Additionally, instead of having a username/password field pre-defined,
the extended authentication method has been generalized to
