From owner-freebsd-stable Sat Jun 9 2:46:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by hub.freebsd.org (Postfix) with ESMTP id 8104C37B401; Sat, 9 Jun 2001 02:46:28 -0700 (PDT) (envelope-from pete@ns.altadena.net) Received: (from pete@localhost) by ns.altadena.net (8.11.3/8.8.8) id f599jeC28852; Sat, 9 Jun 2001 02:45:40 -0700 (PDT) (envelope-from pete) From: Pete Carah Message-Id: <200106090945.f599jeC28852@ns.altadena.net> Subject: Re: Two pam/ssh questions. In-Reply-To: <200106090859.f598xYQ27347@ns.altadena.net> To: stable@freebsd.org Date: Sat, 9 Jun 2001 02:45:39 -0700 (PDT) Cc: markm@freebsd.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Following up on my own note: > The problem is most likely that the pam upgrade happened but the > MFC for changes to pam.conf got forgotten. That is true but isn't enough. There are also many changes (like a whole new vendor import) in openssh. I'm too tired now to deal with this. > If you look at a pam.conf from -current it is *VERY* different. I'm > going to import that from my current box once it comes on line > (it's on a remote ISDN line and only comes on line when ntp decides > to poll :-) and see what it does. Doesn't help enough. The problem appears to be that if you don't use password auth, then no pam module gets loaded. Then when setcred is called the dispatch fails. -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message