[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] using the same passwords for everything
- Subject: Re: [cobalt-users] using the same passwords for everything
- From: "E.B. Dreger" <eddy+public+spam@xxxxxxxxxxxxxxxxx>
- Date: Thu Jan 16 20:34:00 2003
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
JK> Date: Thu, 16 Jan 2003 21:09:47 -0500
JK> From: Josh Kuperman
JK> The partial answer to this is that I need to use PAM modules. Cobalt
JK> servers come with a mod_auth_pam_external that allows a web site to
JK> validate users agains their passwd. There is also a module for Squid
JK> but I'm not sure how to configure it. In theory I should just be able
man 8 pam # this manpage comes with the OS
man 8 pam_auth # this manpage comes with squid
JK> to add a squid entry in /etc/pam.d, but I would love to know if anyone
JK> has done this - since for all I know I'm the only RaQ XTR user who
JK> built his own squid. I may have to ask on the Squid list anyhow.
Haven't done it, but it looks like one creates
/etc/pam.d/squid
with the options needed to create your authentication db from
whatever backend you choose. Alternatively, you can change the
name from "squid" (see the second manpage I mentioned), although
I'd probably leave it be.
Theoretically, it should be simple. PAM is designed as a simple
"middle layer" to make the myriad of applications play nicely
with the host of authentication databases.
Eddy
--
Brotsman & Dreger, Inc. - EverQuick Internet Division
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 (785) 865-5885 Lawrence and [inter]national
Phone: +1 (316) 794-8922 Wichita
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@xxxxxxxxx>, or you are likely to
be blocked.