Date: Fri, 11 Dec 2009 10:49:21 -0600 From: Steve Randall <srandall52@gmail.com> To: David Southwell <david@vizion2000.net> Cc: freebsd-ports@freebsd.org Subject: Re: CUPS/PAM configuration authentication problem. Message-ID: <20091211104921.14f05a92@locust.local> In-Reply-To: <200912111444.12602.david@vizion2000.net> References: <200912111444.12602.david@vizion2000.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 11 Dec 2009 14:44:12 +0000 David Southwell <david@vizion2000.net> wrote: > > Hi > Thanks to some help from people on the freebsd-questions lists I have > finally succeeded in getting cups the server to communicate with my > printer and print. > HOWEVER!! > > One minor niggling problem remains. I still cannot communicate with the > cups management interface on http://localhost:631 due to password > authentication failure. <snip> > > On good authority I believe I have a PAM configuration error most likely - and > was told to check my /etc/pam.d/cups file. Not that I would know what to do > with it when I found it!!! > > However there is no /etc/pam.d/cups file !! > > BUT: there is a /usr/local/etc/pam.d/cups > > which has the following lines: > auth required pam_unknown.so nodelay > account required pam_unknown.so I looked at the cups configuration script, and it appears you have found a bug in configuring the PAM option. (Which defaults to "off", so it probably isn't tested much.) Where the file says "pam_unknown.so" it should say "pam_unix.so". Make that simple change and you should be up and running. But if you don't know what to do with the PAM file, you might as well just rebuild cups-base with the PAM option turned back off. You don't need PAM if all you want is normal Unix authentication. HTH
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091211104921.14f05a92>