sshd+ssh localhost connects, but don't reach the shell

[Vilar Camara]

Hello Larry,

>Two other things to try/consider
>
>   1. Firewall restrictions (port 22 by default).

Well, as I said before, I always shut down the firewall during my tests, so 
it should be no problem. Anyway, port 22 is in the Windows Firewall 
Exceptions list -- just to prevent some Windows bug, because I never use the 
Windows Firewall.

>   2. Running the server in debug mode will provide better diagnostics than
>      the verbose output of the client, though looking at both together in
>      real-time can be even more enlightening.

How is that? Do you mean configuring the service to record its output? (I 
don't know how to do it, could you explain it if this is the case?) Or 
running it as a non-daemon process (/usr/sbin/sshd -Ddd)?

I had tried the latter case. For the sake of completeness, I'll transcribe 
the complete client-server "conversation":

-- Server: I ran "/usr/sbin/sshd -Dddddd". Output follows:

debug2: load_server_config: filename /etc/sshd_config
debug2: load_server_config: done config len = 189
debug2: parse_server_config: config /etc/sshd_config len 189
debug1: sshd version OpenSSH_4.3p2
debug1: private host key: #0 type 0 RSA1
debug3: Not a RSA1 key file /etc/ssh_host_rsa_key.
debug1: read PEM private key done: type RSA
debug1: private host key: #1 type 1 RSA
debug3: Not a RSA1 key file /etc/ssh_host_dsa_key.
debug1: read PEM private key done: type DSA
debug1: private host key: #2 type 2 DSA
debug1: rexec_argv[0]='/usr/sbin/sshd'
debug1: rexec_argv[1]='-Dddddd'
debug2: fd 3 setting O_NONBLOCK
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
Generating 768 bit RSA key.
RSA key generation complete.

-- Client: I ran "ssh -vvvvv localhost". Output follows:

OpenSSH_4.3p2, OpenSSL 0.9.8a 11 Oct 2005
debug1: Reading configuration data /etc/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to localhost [127.0.0.1] port 22.
debug1: Connection established.
debug1: identity file /home/vilarnt/.ssh/identity type 0
debug3: Not a RSA1 key file /home/vilarnt/.ssh/id_rsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type 'Proc-Type:'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type 'DEK-Info:'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
(previous line repeated many times)
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: missing keytype
debug1: identity file /home/vilarnt/.ssh/id_rsa type 1
debug3: Not a RSA1 key file /home/vilarnt/.ssh/id_dsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type 'Proc-Type:'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type 'DEK-Info:'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
(previous line repeated many times)
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: missing keytype
debug1: identity file /home/vilarnt/.ssh/id_dsa type 2

-- Server: responded:

debug1: fd 4 clearing O_NONBLOCK
debug1: Server will not fork when running in debugging mode.
debug3: send_rexec_state: entering fd = 7 config len 189
debug3: ssh_msg_send: type 0
debug3: send_rexec_state: done
debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7

Now both terminals are stuck. The server one doesn't even respond to Ctrl+C.

Interesting, there are strange server complaints about /etc/ssh_host_rsa_key 
and /etc/ssh_host_dsa_key not being a RSA1 key file, even given that they 
were automatically generated by the ssh-host-config script.

Do you have any additional tip? My next step is to test it in a NTFS 
partition.

The sad part is that I *had* used sshd in my machine about a year ago and 
everything went fine. Now I'm trying to revive it and I'm having no luck at 
all.

--
Best regards,
Vilar Camara Neto



--
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/