Unix administration - why connection closed for publickey authentication?

This is Interesting: Free IT Magazines  
Home > Archive > Unix administration > May 2004 > why connection closed for publickey authentication?





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author why connection closed for publickey authentication?
Bing

2004-05-19, 5:40 pm

Please see the debug information below. Would anybody tell why the
connection closed at the end? host.my.edu is running sshd fine. I've
tried ssh to another server in debug mode, seems the next debug line
should be "Server accepts key: blah" in normal cases. But ssh did not
get that point before the connnection was closed. What should I
check?

---------
% ssh -l user -v host.my.edu

OpenSSH_3.7p1, SSH protocols 1.5/2.0, OpenSSL 0.9.7a Feb 19 2003
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to host.my.edu [IP omitted here] port 22.
debug1: Connection established.
debug1: identity file /home/user/.ssh/identity type -1
debug1: identity file /home/user/.ssh/id_rsa type -1
debug1: identity file /home/user/.ssh/id_dsa type 2
debug1: Remote protocol version 2.0, remote software version
OpenSSH_3.5p1
debug1: match: OpenSSH_3.5p1 pat
OpenSSH_3.2*,OpenSSH_3.3*,OpenSSH_3.4*,OpenSSH_
3.5*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.7p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'host.my.edu' is known and matches the RSA host ke
y.
debug1: Found key in /home/user/.ssh/known_hosts:5
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue:
publickey,password,keyboard-interacti
ve
debug1: Next authentication method: publickey
debug1: Trying private key: /home/user/.ssh/identity
debug1: Trying private key: /home/user/.ssh/id_rsa
debug1: Offering public key: /home/user/.ssh/id_dsa
Connection closed by <IP address omitted here>
debug1: Calling cleanup 0x8060040(0x0)
-----------

I would appreciate any help.

Bing
Darren Tucker

2004-05-20, 5:38 am

In article <b4287274.0405191331.5a53f39b@posting.google.com>,
Bing <bdu@iastate.edu> wrote:
>Please see the debug information below. Would anybody tell why the
>connection closed at the end?


>debug1: Trying private key: /home/user/.ssh/id_rsa
>debug1: Offering public key: /home/user/.ssh/id_dsa
>Connection closed by <IP address omitted here>
>debug1: Calling cleanup 0x8060040(0x0)


It looks like the server is dying for some reason. Can you reproduce the
problem with a current OpenSSH (ie 3.8.1p1)? If so, please open a bug at
at bugzilla.mindrot.org and we'll see if we can figure it out.

--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com