From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Alok K. Dhir" Subject: RE: OT: password management Date: Wed, 8 Jan 2003 10:42:08 -0500 Sender: linux-admin-owner@vger.kernel.org Message-ID: <000601c2b72c$814f0a00$6501a8c0@frodo> References: Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Id: Content-Type: text/plain; charset="us-ascii" To: "'Shaw, Marco'" , linux-admin@vger.kernel.org Actually, PAM in itself doesn't have any bearing on the architecture being distributed or not - that is, you can easily set PAM up to use an LDAP or NIS back end, and it will use it. > -----Original Message----- > From: linux-admin-owner@vger.kernel.org > [mailto:linux-admin-owner@vger.kernel.org] On Behalf Of Shaw, Marco > Sent: Wednesday, January 08, 2003 10:44 AM > To: linux-admin@vger.kernel.org > Subject: RE: OT: password management > > > > >PAM (Pluggable Application Modules) provide a > >centralized mechanism for authenticating all services. > >It applies to login, rlogin, telnet, rsh, PPP, su > >among others. In fact, PAM can be used for any linux > application. The > >best documentation is available at > >http://www.kernel.org/linux/libs/pam/ >Neon. Keeping in mind, that unless I'm mistaken of some unknown functionality, PAM does not support a "distributed architecture". In other words, it's good for the server it's running on only. If the original poster is looking to centralize account management, then PAM, by itself will not be sufficient. Something like NIS, NIS+, or some kind of centralized LDAP database would need to be setup. Marco RHCE - To unsubscribe from this list: send the line "unsubscribe linux-admin" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html