From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: [BUG] Prefer AUTH=CRAM-MD5 makes login fail in some IMAP servers.
Date: Mon, 24 Jan 2011 11:44:42 -0600 [thread overview]
Message-ID: <87tygyci2d.fsf@lifelogs.com> (raw)
In-Reply-To: <87mxmsrb2l.fsf@gnus.org>
On Sat, 22 Jan 2011 20:29:54 +0100 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> If it is just your particular server that has this problem, then I guess
LI> this isn't a Gnus problem. However, if it's a common bug in some IMAP
LI> servers, perhaps Gnus should default to using LOGIN, which is faster
LI> than CRAM-MD5 (one less round trip to the server), and is probably
LI> tested a lot more than CRAM-MD5.
LI> The drawback is that if you're talking to your IMAP server over a plain
LI> network connection (boo!) to a server that doesn't support STARTTLS
LI> (boo!), but the server has both CRAM-MD5 and LOGIN enabled, then your
LI> passwords will be transferred unencrypted (boo!).
LI> nnimap could default to using CRAM-MD5 in that particular case, but then
LI> we're kinda into a very special case, and if CRAM-MD5 is buggy, then
LI> some people will be affected anyway...
I think CRAM-MD5 should be preferred if it's available. The user should
be able to disable that preference like any other login method.
Ted
next prev parent reply other threads:[~2011-01-24 17:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 18:21 Emilio Jesús Gallego Arias
2011-01-11 18:51 ` Lars Magne Ingebrigtsen
2011-01-11 21:52 ` Emilio Jesús Gallego Arias
2011-01-11 21:57 ` Lars Magne Ingebrigtsen
2011-01-11 22:55 ` Emilio Jesús Gallego Arias
2011-01-22 19:29 ` Lars Ingebrigtsen
2011-01-24 17:44 ` Ted Zlatanov [this message]
2011-01-24 22:07 ` Lars Ingebrigtsen
2011-01-24 22:10 ` Ted Zlatanov
2011-01-24 22:30 ` Lars Ingebrigtsen
2011-01-25 17:03 ` Ted Zlatanov
2011-01-25 21:28 ` Lars Ingebrigtsen
2011-01-25 22:00 ` Lars Ingebrigtsen
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=87tygyci2d.fsf@lifelogs.com \
--to=tzz@lifelogs.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).