On Sun, 2014-10-26 at 17:31 +, Yawning Angel wrote:
> On Sun, 26 Oct 2014 14:34:59 +0100
> Rob van der Hoeven wrote:
>
> > So, the SOCKS protocol supports redirection to another SOCKS server.
> > An all-zero address/port simply means: use the server/port that you
> > are currently connected
Thank you for the explanation! This was the exactly the question. (I was
just wondering why BND.ADDR and BND.PORT get set to NUL, )
Have a nice day!
Am 2014-10-26 18:31, schrieb Yawning Angel:
On Sun, 26 Oct 2014 14:34:59 +0100
Rob van der Hoeven wrote:
So, the SOCKS protocol supports redir
On Sun, 26 Oct 2014 14:34:59 +0100
Rob van der Hoeven wrote:
> So, the SOCKS protocol supports redirection to another SOCKS server.
> An all-zero address/port simply means: use the server/port that you
> are currently connected to.
That's a really interesting way of interpreting that part of th
> address. When the connection gets granted I am getting a response from
> the socks server:
> (hex data of the tcp payload)
>
> 0x05 0x00 0x00 0x01 0x00 0x00 0x00 0x00 0x00 0x00
>
> Regarding to the SOCKS specification this means that the request is
> granted. But I don't understand the 0x01 i
Hm... Did you try Wireshark on it?
2014-10-26 11:46 GMT+03:00 spriver :
> Hi everyone!
>
> I am trying to understand the communication between an application and Tor
> (especially connecting to a hidden service). I am tracing packets on
> loopback between a torified netcat request to connect to a
Hi everyone!
I am trying to understand the communication between an application and
Tor (especially connecting to a hidden service). I am tracing packets on
loopback between a torified netcat request to connect to a .onion
address. When the connection gets granted I am getting a response from
