From owner-freebsd-current Thu Dec 30 15:13:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 7AB3114E40 for ; Thu, 30 Dec 1999 15:13:33 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id RAA08317; Thu, 30 Dec 1999 17:13:29 -0600 (CST) Date: Thu, 30 Dec 1999 17:13:28 -0600 (CST) From: Steve Price To: "Thomas T. Veldhouse" Cc: djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG Subject: Re: troubles with X In-Reply-To: <004a01bf5317$56bc56c0$0100a8c0@veldy.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Dec 1999, Thomas T. Veldhouse wrote: # Here is the answer I was given by somebody on this list last week. # # #/etc/pam.conf # # tricky tricky forgive me # xserver auth sufficient pam_permit.so no_use # # If we don't match anything else, default to using getpwnam(). # other auth required pam_unix.so # try_first_pass # other account required pam_unix.so # try_first_pass This is really not a 'fix' per se. It is more like a workaround as it disables PAM without having to recompile X. Or at least that's the way I read it. Surely there is a way to really use PAM authentication? If this *is* the official fix then I should probably commit it to src/etc/pam.conf because everyone setting up a new system is going to run into this very same problem if they install X. BTW, thanks for the quick reply. :) -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message