In reply to post ID 1037
hi,
i attached a SOCKS5 log and hope it will help you.
In this log you see the Hash f72a23ee01525181e1cf6b5235390902e189f0c2 build from:
i removed some content of the file because it was a big PDF document. The file starts with the bytes "25 50" and ends with the bytes "46 0A".
When the file is complete the sender should close the socket. You also know the lenght of the file from the si request. If you count the received bytes and show the progress then you know when the file is complete, even when the sender doesnt close the socket.
Alex
i attached a SOCKS5 log and hope it will help you.
In this log you see the Hash f72a23ee01525181e1cf6b5235390902e189f0c2 build from:
- sid: s5b_92a0d0f56112ac36
- initiator: gnauck@myjabber.net/Psi
- target: gnauck@jabber.org/Exodus
i removed some content of the file because it was a big PDF document. The file starts with the bytes "25 50" and ends with the bytes "46 0A".
When the file is complete the sender should close the socket. You also know the lenght of the file from the si request. If you count the received bytes and show the progress then you know when the file is complete, even when the sender doesnt close the socket.
Alex
The author has attached one file to this post:
socks5.html 2.8 kBytes
You have no permission to open this file.
You have no permission to open this file.