From owner-freebsd-questions Tue Jun 19 12:10:29 2001 Delivered-To: freebsd-questions@freebsd.org Received: from yertle.kciLink.com (yertle.kcilink.com [216.194.193.105]) by hub.freebsd.org (Postfix) with ESMTP id 8AFBB37B407 for ; Tue, 19 Jun 2001 12:10:25 -0700 (PDT) (envelope-from khera@kcilink.com) Received: by yertle.kciLink.com (Postfix, from userid 100) id 1FACF2E462; Tue, 19 Jun 2001 15:10:23 -0400 (EDT) To: questions@freebsd.org Newsgroups: ml.freebsd.questions Subject: Re: SSH and PAM still broken? References: <20010619111333.D65613@msu.edu> From: Vivek Khera Date: 19 Jun 2001 15:10:22 -0400 Message-ID: Organization: Khera Communications, Inc., Rockville, MD Lines: 17 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) In-Reply-To: <20010619111333.D65613@msu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Posted-To: ml.freebsd.questions Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The following message is a courtesy copy of an article that has been posted to ml.freebsd.questions as well. >>>>> "EG" == Edward Glowacki writes: EG> around a while. The best information on how to fix it I've found EG> was to update /etc/pam.conf, except the version I have already has EG> the prescribed fixes. Is there something I missed here, or is EG> PAM&SSH just broken? This is a wholly different problem from what you found in the archives about fixing pam.conf. It has to do with a busted libpam. Fix is to update to a newer snapshot (I just replaced libpam and associated modules). The busted libpam existed for about one or two days. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message