Hello. I seem to have the particular combination of "running in a Windows console window, CYGWIN=... notty ..., Forward X11 yes, and Protocol 2" mentioned by Corinna Vinschen in her 2001-10-26 posting which results in Ctrl-C killing my Cygwin SSH sessions under Windows.
I checked both the Cygwin mailing list archive and the openssh-unix-dev mailing list archive and have found no further comments on this problem. Corinna's post asking for help debugging the problem was the last reference I found. Has there been any progress fixing this? If not, then I'd be happy to try to debug the problem if someone could suggest a first step. FWIW, I'm experiencing the problem using OpenSSH_3.0.2p1, SSH protocols 1.5/2.0, OpenSSL 0x0090603f CYGWIN_NT-4.0 CS831 1.3.9(0.51/3/2) 2002-01-21 12:48 i686 unknown WinNT4.0sp6a (output of "cygcheck -s -v -r -h" available upon request) My CYGWIN environment variable is set to "binmode" only. For now, I think I can work around the problem by adding "tty" to CYGWIN, but according to the User's Guide, this is not compatible with "some Windows programs", so I fear turning tty on may have unanticipated side effects. I welcome any suggestions or information others might have. -Brian Kasper -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
