From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Subject: Re: AUTH=PLAIN support
Date: Sun, 31 Oct 2010 17:31:05 -0400 [thread overview]
Message-ID: <m3bp6a3v7y.fsf@jhcloos.com> (raw)
In-Reply-To: <m3wroyl5qv.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 31 Oct 2010 16:52:08 +0100")
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
LMI> It seems kinda weird, though. AUTHENTICATE PLAIN is just basically a
LMI> base64-encoded version of LOGIN, so I'm not quite understanding what the
LMI> point is...
I'm sure the discourse went something like:
TLSsupporter> kill off LOGIN! kill off LOGIN! kill off LOGIN!
StatusQuo> But we need to auth against out /etc/shadow, and that
StatusQuo> requires the user send their secret to the server
and AUTH=PLAIN was the compromize.
And the TLS guys should prefer TLS client cert aaa anyway.
On the plus side, it does allow the separation of authentication and
authorization realms, so that, eg, the each support tech at example.com
could log in to the support@example.com account as themselves. That
would allow the audit logs to show exactly who did what.
But, yes, otherwise it is just /different/ than LOGIN, not better.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2010-10-31 21:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 1:20 Lars Magne Ingebrigtsen
2010-10-30 19:38 ` Tibor Simko
2010-10-30 19:41 ` Lars Magne Ingebrigtsen
2010-10-30 20:22 ` Tibor Simko
2010-10-30 20:31 ` Lars Magne Ingebrigtsen
2010-10-30 20:46 ` Tibor Simko
2010-10-30 22:37 ` James Cloos
2010-10-31 15:52 ` Lars Magne Ingebrigtsen
2010-10-31 21:31 ` James Cloos [this message]
2010-10-31 21:45 ` Russ Allbery
2010-10-31 21:53 ` Lars Magne Ingebrigtsen
2010-11-01 12:23 ` Tibor Simko
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=m3bp6a3v7y.fsf@jhcloos.com \
--to=cloos@jhcloos.com \
--cc=ding@gnus.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).