sshd closing connection on reception of username
From: Peter Robinett (peterr_at_uchicago.edu)
Date: 02/12/05
- Previous message: Robert L Sowders: "RE: PKA on OpenSSH on Cygwin"
- Next in thread: Darren Tucker: "Re: sshd closing connection on reception of username"
- Reply: Darren Tucker: "Re: sshd closing connection on reception of username"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 12 Feb 2005 00:21:14 -0600 To: secureshell@securityfocus.com
Hi, I'm new to the list, so my apologies if this is the wrong place or
someone answered this question before (I did try to look through the
archives).
Anyway, here's my problem and hopefully someone might have a clue what's
going on: I was logged in to a linux box (Mandrake 10.0) when my
wireless internet connection on my client machine died. Now when I try
to ssh to the server it fails. The attached output.txt file shows what
happens. Everything seems to go fine until the last line, when the
remote server closes the connection. If I don't pass a user name (by
using putty on Windows), it will throw up a login prompt. I enter a user
name and hit return and it will immediately quit, meaning that, I
believe, the connection has been terminated by the remote server upon
receipt of the user name. Note: I was installing some dependencies of
apache2, so I guess it's conceivable that that messed up the machine
when my connection was broken.
I even tried connecting with openssl: "openssl s_client -connect
beachhead.dhs.org:443". The problem here is that the connection is
refused, which I assume is because I don't have apache running (the
reason I was originally logged in, to fix it). Connecting to port 22
gives the following message:
CONNECTED(00000003)
1256:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown
protocol:s23_clnt.c:460
I assume this is the ssl client not knowing how to handle the ssh
server's responses.
Thanks for your time!
Peter Robinett
OpenSSH_3.9p1, OpenSSL 0.9.7e 25 Oct 2004
Pseudo-terminal will not be allocated because stdin is not a terminal.
debug2: ssh_connect: needpriv 0
debug1: Connecting to beachhead.dhs.org [216.250.80.201] port 22.
debug1: Connection established.
debug1: identity file /home/Peter/.ssh/identity type -1
debug1: identity file /home/Peter/.ssh/id_rsa type -1
debug1: identity file /home/Peter/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.5p1
debug1: match: OpenSSH_3.5p1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.9p1
debug2: fd 4 setting O_NONBLOCK
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: mac_init: found hmac-md5
debug1: kex: server->client aes128-cbc hmac-md5 none
debug2: mac_init: found hmac-md5
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug2: dh_gen_key: priv key bits set: 144/256
debug2: bits set: 525/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug3: check_host_in_hostfile: filename /home/Peter/.ssh/known_hosts
debug3: check_host_in_hostfile: match line 1
debug3: check_host_in_hostfile: filename /home/Peter/.ssh/known_hosts
debug3: check_host_in_hostfile: match line 1
debug1: Host 'beachhead.dhs.org' is known and matches the RSA host key.
debug1: Found key in /home/Peter/.ssh/known_hosts:1
debug2: bits set: 475/1024
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /home/Peter/.ssh/identity (0x0)
debug2: key: /home/Peter/.ssh/id_rsa (0x0)
debug2: key: /home/Peter/.ssh/id_dsa (0x0)
Connection closed by 216.250.80.201
- Previous message: Robert L Sowders: "RE: PKA on OpenSSH on Cygwin"
- Next in thread: Darren Tucker: "Re: sshd closing connection on reception of username"
- Reply: Darren Tucker: "Re: sshd closing connection on reception of username"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|