From owner-freebsd-questions Wed Mar 14 9:10:49 2001 Delivered-To: freebsd-questions@freebsd.org Received: from dsl-64-193-218-89.telocity.com (dsl-64-193-218-89.telocity.com [64.193.218.89]) by hub.freebsd.org (Postfix) with SMTP id C5D0C37B72B for ; Wed, 14 Mar 2001 09:10:44 -0800 (PST) (envelope-from lucas@slb.to) Received: (qmail 22713 invoked by uid 1000); 14 Mar 2001 17:11:06 -0000 Date: Wed, 14 Mar 2001 11:11:06 -0600 From: Lucas Bergman To: Charles Burns Cc: questions@freebsd.org Subject: Re: SSH now refuses all connections Message-ID: <20010314111106.C17107@billygoat.slb.to> Reply-To: lucas@slb.to References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from burnscharlesn@hotmail.com on Tue, Mar 13, 2001 at 08:58:38PM -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A few make worlds ago, SSHD began refusing all connections... The OpenSSH shipped recently became PAM-enabled. You probably need to make your /etc/pam.conf like the one in /usr/src/etc. Since I don't have any special PAM setup, "cp /usr/src/etc/pam.conf /etc" worked for me. If this is the problem, then "grep sshd /var/log/messages" should produce some whining about PAM modules. > Speaking of denying access to "nogroup", it doesn't seem to work... I have no idea about all of this. If no one picks up my slack and answers this one, you might try posting it in a separate message. (One question per post is the law of the land in -questions.) Lucas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message