Re: [7.0-Beta] can no longer ssh into just upgraded host

From: Jeremy Chadwick <koitsu_at_FreeBSD.org>
Date: Wed, 31 Oct 2007 07:39:44 -0700
On Wed, Oct 31, 2007 at 03:18:13PM +0100, Dag-Erling Smørgrav wrote:
> Jeremy Chadwick <koitsu_at_FreeBSD.org> writes:
> > On Fri, Oct 26, 2007 at 01:47:07PM -0500, Rob Zietlow wrote:
> >> #ssh -vv 192.168.8.163
> >> OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003
> >> debug1: Reading configuration data /etc/ssh/ssh_config
> >> debug1: Applying options for *
> >> debug2: ssh_connect: needpriv 0
> >> debug1: Connecting to 192.168.8.163 [192.168.8.163] 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 -1
> >> ssh_exchange_identification: read: Connection reset by peer
> >
> > Sounds like it might be a PAM-related problem.  Have you looked
> > at /var/log/messages or "dmesg -a"?
> 
> What makes you think it might be PAM-related?  They don't even get as
> far as exchanging version strings.

An old -stable post I read is what made me think it might be
PAM-related:

http://lists.freebsd.org/pipermail/freebsd-stable/2004-November/009414.html

I don't know what stage PAM is actually induced within sshd (are any
PAM-related API calls done before version exchange, etc.).

-- 
| Jeremy Chadwick                                    jdc at parodius.com |
| Parodius Networking                           http://www.parodius.com/ |
| UNIX Systems Administrator                      Mountain View, CA, USA |
| Making life hard for others since 1977.                  PGP: 4BD6C0CB |
Received on Wed Oct 31 2007 - 13:48:39 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:20 UTC