In SOCKS5 dynamic forwarding, we were echoing back DST.{ADDR,PORT} as
authorjacob <jacob@cda61777-01e9-0310-a592-d414129be87e>
Fri, 10 Oct 2003 21:20:01 +0000 (21:20 +0000)
committerjacob <jacob@cda61777-01e9-0310-a592-d414129be87e>
Fri, 10 Oct 2003 21:20:01 +0000 (21:20 +0000)
commit04df1251fd697930c32e36ef60115620d23ebe81
tree31521abbef82dc85707e695157aa30188d088c1b
parent183f030373dccfeb2ad4f7f1c46aa71d8dfabc93
In SOCKS5 dynamic forwarding, we were echoing back DST.{ADDR,PORT} as
BND.{ADDR,PORT}. Besides being clearly wrong, correspondence with
Sascha Schwarz suggests that this can confuse some SOCKS5 clients
(Aventail and sockscap32) which seem to assume that the reply must
have ATYP=1 (IPv4 literal) and so get the length wrong.

Now all replies have ATYP=1 with BND.{ADDR,PORT} = 0.0.0.0:0 -- this
apparently follows practice in OpenSSH. (We don't have enough info to
fill these fields in correctly.)

git-svn-id: svn://svn.tartarus.org/sgt/putty@3496 cda61777-01e9-0310-a592-d414129be87e
portfwd.c