From: "Mark D. Baushke" <mdb@juniper.net>
To: help-gnats@gnu.org
Subject: Re: PAM Authentication Patch
Date: Mon, 21 Jun 2004 15:34:00 -0000 [thread overview]
Message-ID: <85764.1087802701@juniper.net> (raw)
In-Reply-To: Mail from Chad Walstrom <chewie@wookimus.net> dated Sun, 20 Jun 2004 12:58:49 CDT <20040620175849.GC13514@wookimus.net>
Chad Walstrom <chewie@wookimus.net> writes:
> Chad Walstrom wrote:
> > We should make it abundantly clear in the
> > documentation that use of PAM authentication
> > should be thoroughly protected. If such
> > measures cannot be taken, don't enable PAM.
>
> Additionally, we can't always assume that
> because something uses PAM, it'll authentication
> against system accounts. There are dbm modules,
> ldap modules, etc. that can be used for account
> management.
While I do understand that it is *possible* to
enable PAM and not endanger other applications or
systems. I also understand that very few people or
organizations will consider keeping such things
separate in such a safe configuration unless the
documentation clearly states that there are
security implications to be considered.
Yes, I am being paranoid. right now it seems
fairly clear that gnatsd authentication is not
very strongly protected. Folks are more likely to
believe something is 'secure' if it can talk to
PAM even though there may be explicit basis for
that belief.
-- Mark
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2004-06-21 7:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 21:20 CVS, Documentation, TODO Lists, New Maintainer, and Stuff Chad C. Walstrom
2004-06-10 21:44 ` Chad C. Walstrom
2004-06-13 8:51 ` Mel Hatzis
2004-06-13 23:01 ` Andrew Gray
2004-06-11 22:28 ` Yngve Svendsen
2004-06-14 17:07 ` Pankaj K Garg
2004-06-14 17:16 ` Chad C. Walstrom
2004-06-20 17:39 ` PAM Authentication Patch Pankaj K Garg
[not found] ` <gargp@earthlink.net>
2004-06-20 17:59 ` Mark D. Baushke
2004-06-21 7:25 ` Chad Walstrom
2004-06-21 15:26 ` Chad Walstrom
[not found] ` <chewie@wookimus.net>
2004-06-21 15:34 ` Mark D. Baushke [this message]
2004-11-04 1:27 ` Preparing 4.1 Mark D. Baushke
2004-11-04 3:15 ` Chad Walstrom
2004-11-04 19:15 ` Chad Walstrom
2004-11-17 23:26 ` Chad Walstrom
2004-06-21 16:13 ` PAM Authentication Patch Chad Walstrom
2004-10-29 21:33 Preparing 4.1 Chad C. Walstrom
2004-10-31 14:03 ` Pankaj Garg
2004-11-01 19:09 ` Pankaj Garg
2004-11-03 22:39 ` Chad C. Walstrom
2004-11-03 22:46 ` Chad C. Walstrom
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=85764.1087802701@juniper.net \
--to=mdb@juniper.net \
--cc=help-gnats@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).