From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] gmail login
Date: Fri, 15 May 2009 13:57:38 -0400 [thread overview]
Message-ID: <1242409947-sup-5182@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <8c09a1500905151037m351adedyefdde82c244e17c0@mail.gmail.com>
Excerpts from Maurice McCarthy's message of Fri May 15 13:37:08 -0400 2009:
> The sup log tells me that when I log in to my
> gmail account it ends up logging in using
> plain text.
This is normal and just a part of a standard IMAP connection auth
sequence. Unless you've got kerberos enabled/SASL auth stuff in
place, the standard IMAP auth options are all pretty nasty (pop3 is no
better)...
> Fri May 15 17:20:06 +0000 2009: CRAM-MD5 authentication failed:
> Net::IMAP::NoResponseError. Trying LOGIN auth...
> Fri May 15 17:20:06 +0000 2009: LOGIN authentication failed:
> Net::IMAP::NoResponseError. Trying plain-text LOGIN...
> Fri May 15 17:20:06 +0000 2009: Successfully connected to
> imaps://imap.googlemail.com:993/INBOX.
You still connected via an ssl secured connection, so even using
horrible auth mechanisms like this, you're reasonably protected during
transit.
Looks good from here.
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090515/3372a1e8/attachment.bin>
prev parent reply other threads:[~2009-05-15 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 17:37 Maurice McCarthy
2009-05-15 17:57 ` Ben Walton [this message]
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=1242409947-sup-5182@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
/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