From owner-freebsd-questions@FreeBSD.ORG Wed Jan 19 08:04:06 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEF6D16A4CE for ; Wed, 19 Jan 2005 08:04:06 +0000 (GMT) Received: from jupiter.picknowl.com.au (jupiter.picknowl.com.au [203.87.94.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32AD243D49 for ; Wed, 19 Jan 2005 08:04:06 +0000 (GMT) (envelope-from imoore@picknowl.com.au) Received: from daemon.foo.com (adsl-176-70.swiftdsl.com.au [218.214.176.70]) by jupiter.picknowl.com.au (Postfix) with ESMTP id 7BCC896CEA for ; Wed, 19 Jan 2005 18:34:02 +1030 (CST) From: Ian Moore User-Agent: KMail/1.7.2 MIME-Version: 1.0 To: Questions Free BSD Date: Wed, 19 Jan 2005 18:33:15 +1030 Content-Type: multipart/signed; boundary="nextPart1826385.yEA8vn0364"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501191833.37349.imoore@picknowl.com.au> Subject: SSH suddenly giving pam error for existing user X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 08:04:06 -0000 --nextPart1826385.yEA8vn0364 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, I can normally ssh to my home computer (using password authentication), but= =20 today it's stopped working. The last time I did it was about 9 days ago fro= m=20 work & it worked then. The console log shows: Jan 19 17:04:25 daemon sshd[61084]: error: PAM: authentication error for=20 imoore from firewall. I've tried connecting from 2 different remote hosts, one at work & another= =20 elsewhere - same result. When I got home today, I tried creating a new user & then ssh'ed to a remot= e=20 machine & ssh'ed back to mine with the new username. I was able to log in OK as the new user. I then changed the password for my normal user & tried to ssh back with the= =20 new password, but I still can't login. I'm running 5.3-RELEASE-p2. I have upgraded a few ports since ssh last work= ed=20 =2D openoffice and a few bit & pieces - I'm not sure what exactly.=20 I haven't altered my ipfw config in that time, nor have I upgraded the base= =20 system or kernel. Can anyone think what might have caused this? Cheers, =2D-=20 Ian GPG Key: http://homepages.picknowl.com.au/imoore/imoore.asc --nextPart1826385.yEA8vn0364 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB7hRZfITqkXhImmIRAuUSAKCQUpLjpKzJpVP9QAPu5yzaYGduBACdErAl 5g1chbp4Wy6xAsJ2sBBFOcA= =z433 -----END PGP SIGNATURE----- --nextPart1826385.yEA8vn0364--