From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Some issues with new nnimap
Date: Sun, 26 Sep 2010 14:50:07 +0200 [thread overview]
Message-ID: <m3eicgy8hs.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m3iq1sy9r7.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Ok, I see the problem. If the auth sources don't exist (i.e., no
> ~/.authinfo), auth-sources.el won't prompt for user name/password at
> all. I'll fix that.
I've now done this for the ~/.authinfo and ~/.authinfo.gpg cases, but
I'm not sure how the Secret Service API is supposed to work, so I'll
leave that bit to Ted. :-)
Looking at the code, it only seems to store the (queried-for) password,
and not the user name? That can't be right...
So now there's two saving things in auth-source-create -- one in the
loop in the passwd branch, and one at the end after both the user name
and passwords have been collected. That should be fixed.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-09-26 12:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 5:53 Drew Hess
2010-09-26 12:22 ` Lars Magne Ingebrigtsen
2010-09-26 12:50 ` Lars Magne Ingebrigtsen [this message]
2010-09-26 21:00 ` Drew Hess
2010-09-26 21:02 ` Lars Magne Ingebrigtsen
2010-09-26 21:37 ` Drew Hess
2010-09-27 17:38 ` Lars Magne Ingebrigtsen
2010-09-26 19:57 ` nndoc groups beeping (was: Some issues with new nnimap) Andreas Seltenreich
2010-09-26 20:09 ` Drew Hess
[not found] ` <AANLkTi=jMSdPR=up4gW_b2m_QrRghXCLCcjxU9oPd1w_@mail.gmail.com>
2010-09-26 20:11 ` nndoc groups beeping Andreas Seltenreich
2010-09-26 20:40 ` Drew Hess
2010-09-26 21:13 ` Lars Magne Ingebrigtsen
2010-09-29 22:25 ` Lars Magne Ingebrigtsen
2010-09-26 21:12 ` Some issues with new nnimap Lars Magne 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=m3eicgy8hs.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).