search

yash069 / puttycyg

Automatically exported from code.google.com/p/puttycyg
0 stars 0 forks source link

Please make a PuttyCyg based on latest Putty, current PuttyCyg propagates a serious remote port forwarding bug as manifested with a latest OpenSSH_6.1 OpenSSL 1.0.1c 10 May 2012 OpenBSD remote host. #73

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
A serious bug that has been fixed in mainstream Putty over the last year 
remains in PuttyCyg.

Can you please make a new PuttyCyg version based on the latest Putty sources 
and release it?

Thanks!!

How to make the bug show:

1. Install latest PuttyCyg on your Windows XP SP3 machine
2. Install OpenBSD-current snapshot as of 17 November 2012 on a remote machine
3. Make a PuttyCyg connection to the SSHD on the OBSD machine.
4. Set up a remote port forward (independent of if this is done before or after 
connect time). I used port 2010 on both sides, i.e. port forward of OBSD port 
2010 to Windows 127.0.0.1:2010 .
(5. In the "Event log" window in PuttyCyg, it shows that the port forwarding 
was set up successfully.)
6. Set up a TCP server that accepts connections on the Windows machine, any 
that proves a connection got through will do.
7. Run "telnet localhost 2010" on the OBSD machine.

Outcome: Telnet either returns "connection refused" or connects for part of a 
second, communicates no data, and then reports the connection is closed. No 
connection attempt is made by PuttyCyg as to forward the connection.

If you just use the latest Putty for Windows x86 as downloaded from Putty's 
website instead of latest PuttyCyg, it *works*. Also doing the same to the same 
remote host with -R 2010:localhost:2010 using the OpenSSH client application on 
a Linux box *works*.

Original issue reported on code.google.com by mikael....@gmail.com on 20 Nov 2012 at 10:36

GoogleCodeExporter commented 8 years ago 
Ah I should mention, I doublechecked with ordinary Putty 0.60.0.0 from 2008, 
and it does have this bug too.

So it's clear the bug is directly inherited from the old Putty source tree and 
that it's virtually 100% sure it's resolved by making a new PuttyCyg by 
applying the patches to the current Putty source tree.

Original comment by mikael....@gmail.com on 20 Nov 2012 at 10:46