From: Raphael Kubo da Costa <kubito@gmail.com>
To: ding@gnus.org
Subject: Re: Making Gnus ask my IMAP username and password after the recent auth-source changes
Date: Thu, 17 Feb 2011 11:34:43 -0200 [thread overview]
Message-ID: <ijj85l$8js$1@dough.gmane.org> (raw)
In-Reply-To: <87d3mqj36i.fsf@lifelogs.com>
Ted Zlatanov wrote:
> On Thu, 17 Feb 2011 01:34:25 -0200 Raphael Kubo da Costa
> RKdC> I am still wondering if the prompts I get are better than the old
> RKdC> though -- the old code used to infer the port from my ~/.gnus
> RKdC> (via nnimap-server-port),
>
> This can be helped with `auth-source-creation-defaults'. I will add a
> default to the first port to `nnimap-credentials'.
Well, it got a bit confusing now.
I need to use port 993 to connect to the IMAP server. Previously, Gnus tried
the port list for ssl (143, 993, imap and imaps), settled on 993 and asked
me for my username and password showing "imap.gmail.com:993" in the prompt.
Now, the prompt shows me "Personal:143", so the host is not shown, and the
port is wrong. It then asks me to write this information (with the wrong
port) into ~/.authinfo.gpg. I then choose "n" and it works fine, because
after that Gnus ends up connecting to port 993.
> RKdC> and did not show the password in clear text when asking to store
> RKdC> the data in ~/.authinfo.gpg. Is it possible to at least hide the
> RKdC> password in the last prompt?
> Hmm. But then you couldn't see the actual line that was added. I'm not
> sure what's the right thing here.
Any other program that prompts for confirmation of this sort of data usually
uses "***" or something like that when asking to write the password.
Wouldn't it be possible to at least add a variable for the paranoid? :)
next prev parent reply other threads:[~2011-02-17 13:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 2:06 Raphael Kubo da Costa
2011-02-15 13:46 ` Ted Zlatanov
2011-02-15 20:57 ` Raphael Kubo da Costa
2011-02-16 19:13 ` Ted Zlatanov
2011-02-16 20:39 ` Matt Lundin
2011-02-16 20:46 ` Ted Zlatanov
2011-02-17 1:15 ` Matt Lundin
2011-02-17 11:03 ` Ted Zlatanov
2011-02-17 13:49 ` Matt Lundin
2011-02-17 14:20 ` Matt Lundin
2011-02-17 15:22 ` Steinar Bang
2011-02-18 20:21 ` Ted Zlatanov
2011-02-21 19:40 ` Steinar Bang
2011-02-17 3:34 ` Raphael Kubo da Costa
2011-02-17 11:44 ` Ted Zlatanov
2011-02-17 13:34 ` Raphael Kubo da Costa [this message]
2011-02-17 14:16 ` Ted Zlatanov
2011-02-17 23:54 ` Lars Ingebrigtsen
2011-02-18 20:19 ` Ted Zlatanov
2011-02-18 23:10 ` Lars Ingebrigtsen
2011-02-22 21:52 ` Ted Zlatanov
2011-02-23 8:52 ` Lars Ingebrigtsen
2011-02-23 14:47 ` Ted Zlatanov
2011-02-23 17:00 ` Raphael Kubo da Costa
2011-02-23 17:09 ` Ted Zlatanov
2011-02-23 17:56 ` Raphael Kubo da Costa
2011-02-23 18:56 ` Ted Zlatanov
2011-02-25 4:42 ` Lars Ingebrigtsen
2011-02-25 11:31 ` Ted Zlatanov
2011-03-05 12:15 ` Lars Magne Ingebrigtsen
2011-03-08 18:26 ` Ted Zlatanov
2011-03-15 16:28 ` Lars Magne Ingebrigtsen
2011-03-15 16:43 ` Ted Zlatanov
2011-02-23 23:35 ` Lars Ingebrigtsen
2011-02-23 23:36 ` Lars Ingebrigtsen
2011-02-24 5:43 ` Ted Zlatanov
2011-02-24 11:35 ` Lars Ingebrigtsen
2011-02-24 13:06 ` Ted Zlatanov
2011-02-24 13:48 ` Raphael Kubo da Costa
2011-02-24 16:42 ` Ted Zlatanov
2011-02-25 4:47 ` 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='ijj85l$8js$1@dough.gmane.org' \
--to=kubito@gmail.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).