FWIW,
I seem to be having the same problem. Last week I reinstalled Windows
XP, SP2 & Cygwin. Since then I can't ssh into my Windows box. I also
observed the:
debug2: channel 0: rcvd eof
but haven't had the chance to track it down. Prior to the
re-installation exercise it was perfect for at least the last couple of
years. Needless to say I am watching this thread with interest. Let me
know if I can send anything along.
but haven't had the chance to track it down. Needless to say I am watching
this thread with interest.
Kyle A. Dawson wrote:
That command does not work
$ ssh -v -v -v -v -v myhost --login -i -x
OpenSSH_4.7p1, OpenSSL 0.9.8g 19 Oct 2007
ssh: unknown option -- -
usage: ssh [-1246AaCfgKkMNnqsTtVvXxY] [-b bind_address] [-c cipher_spec]
[-D [bind_address:]port] [-e escape_char] [-F configfile]
[-i identity_file] [-L [bind_address:]port:host:hostport]
[-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]
[-R [bind_address:]port:host:hostport] [-S ctl_path]
[-w local_tun[:remote_tun]] [EMAIL PROTECTED] [command]
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Dave Korn
Sent: Friday, January 18, 2008 8:45 AM
To: cygwin@cygwin.com
Subject: RE: RE: ssh interactive shell not working
On 18 January 2008 14:07, Kyle A. Dawson wrote:
Ok, here is the output from the debug
$ ssh -v -v -v -v -v myhost
OpenSSH_4.7p1, OpenSSL 0.9.8g 19 Oct 2007
debug2: ssh_connect: needpriv 0
Doh. Sorry, my fault - that doesn't really show us enough, although it
does
show...
debug3: tty_make_modes: 93 0
debug2: channel 0: request shell confirm 0
debug2: fd 3 setting TCP_NODELAY
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel 0: rcvd adjust 2097152
^^^^^^^^^^ that at this point, you were successfully connected, and ...
debug2: channel 0: rcvd eof
^^^ immediately afterward the other end sent an EOF and closed the
channel,
for no obvious reason.
The client has not changed at all and worked before, I have many clients
that were working, now all stopped. So I think it is on the server side.
Agreed, it's the startup scripts on the server side I was talking about,
but
my commandline didn't turn on bash debugging as well as ssh debugging.
Please try again with:
$ ssh -v -v -v -v -v myhost bash --login -i -x
and we should see your bash startup scripts running in the debug output.
cheers,
DaveK
--
Roger Wells, P.E.
SAIC
221 Third St
Newport, RI 02840
401-847-4210 (voice)
401-849-1585 (fax)
[EMAIL PROTECTED]
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
