From: "Alok K. Dhir" <adhir@symplicity.com>
To: "'Shaw, Marco'" <Marco.Shaw@aliant.ca>, linux-admin@vger.kernel.org
Subject: RE: OT: password management
Date: Wed, 8 Jan 2003 10:42:08 -0500 [thread overview]
Message-ID: <000601c2b72c$814f0a00$6501a8c0@frodo> (raw)
In-Reply-To: <C65F89D1AC0BB54B865127151A24DA780E490301@nbexchm2.aliant.icn>
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
next prev parent reply other threads:[~2003-01-08 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 15:44 OT: password management Shaw, Marco
2003-01-08 15:42 ` Alok K. Dhir [this message]
2003-01-08 16:12 ` Saint Neon
-- strict thread matches above, loose matches on Subject: below --
2003-01-08 13:53 Miguel González Castaños
2003-01-08 15:22 ` Saint Neon
2003-01-08 15:38 ` Miguel González Castaños
2003-01-08 23:58 ` Milan P. Stanic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000601c2b72c$814f0a00$6501a8c0@frodo' \
--to=adhir@symplicity.com \
--cc=Marco.Shaw@aliant.ca \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).