From owner-freebsd-current Thu Dec 30 17:16:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from snowy.org (snowy.org [203.37.251.14]) by hub.freebsd.org (Postfix) with ESMTP id 8CD4E15363 for ; Thu, 30 Dec 1999 17:16:25 -0800 (PST) (envelope-from snowy@snowy.org) Received: from localhost (snowy@localhost) by snowy.org (8.9.3/8.9.3) with ESMTP id LAA96454; Fri, 31 Dec 1999 11:16:04 +1000 (EST) (envelope-from snowy@snowy.org) Date: Fri, 31 Dec 1999 11:16:04 +1000 (EST) From: Sleepless in Brisbane To: Steve Price Cc: "Thomas T. Veldhouse" , djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG Subject: Re: troubles with X In-Reply-To: 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, Steve Price wrote: > 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. On a side note I found this fixed a problem with logging in via XDM that I have been seeing lately as well but just haven't had the time to track down; so it could certainly be helpful for more than just those running local displays. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message