Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: auth-source for new users (was: Gnus startup problems?)
Date: Mon, 13 Feb 2012 12:11:21 -0500	[thread overview]
Message-ID: <87sjie4q12.fsf_-_@lifelogs.com> (raw)
In-Reply-To: <87y5san1wo.fsf@gnus.org>

On Fri, 10 Feb 2012 16:28:23 +0100 Lars Ingebrigtsen <larsi@gnus.org> wrote: 

LI> Antoine Levitt <antoine.levitt@gmail.com> writes:
>> It did - in authinfo. I answered "n" in order not to mess up my config,
>> and it prompted me for the password again when I opened a
>> folder. Presumably it could have saved it in memory, even if I didn't
>> write it in authinfo.

LI> Yes, it probably should have.  Ted?

(to anyone interested, we're talking about new users with no auth-source
setup, not those who have already set up an authinfo file as suggested
by the auth-source docs)

We're discussing this in an emacs bug thread.  I'm not sure what's the
right solution here.  There's valid scenarios for:

1) keeping the username+password in memory only (easy to implement!)

2) saving them to a keychain immediately

3) saving them to a netrc/authinfo file immediately

4) saving all credentials to a netrc/authinfo file later, keeping them
in memory now

I favor (4) but Stefan Monnier likes (2) and keychains in general, and
there seems to be no consensus on what's best.  So any opinions are
welcome.

Ted




  reply	other threads:[~2012-02-13 17:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 22:47 Gnus startup problems? Lars Ingebrigtsen
2012-02-09 23:07 ` Antoine Levitt
2012-02-10  3:30   ` Lars Ingebrigtsen
2012-02-10  8:18     ` Antoine Levitt
2012-02-10 15:28       ` Lars Ingebrigtsen
2012-02-13 17:11         ` Ted Zlatanov [this message]
2012-02-13 18:39           ` auth-source for new users Michael Albinus
2012-02-13 19:45           ` 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=87sjie4q12.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).