From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: bug-gnu-emacs@gnu.org, bugs@gnus.org
Subject: bug#7487: 24.0.50; Gnus nnimap broken
Date: Thu, 09 Dec 2010 22:10:35 +0100 [thread overview]
Message-ID: <m3y67yfy9g.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <jwv8vzzdi9a.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> that I'm tempted to go back to just storing this data in the plain-text
>> ~/.authinfo file until all this has been worked out.
>
> No!!!! Or only after prompting the user five times for
> (different) confirmation.
If you look at other widely used software packages, like Firefox, they
default to just storing the passwords in an (obfuscated) non-encrypted
file. I don't think that's such a bad default.
>> When writing the ~/.authinfo.gpg file, the user should be queried one
>> thing: "Password for ~/.authinfo.gpg: ****". And that's it, in my
>> extremely humble opinion.
>
> I partly agree, though some users won't have a key-pair setup, others
> will have several, so the right thing to do may be either to use
> symmetric encryption, or to guess which key-pair to use, and since it's
> a guess there needs to be a way for the user to override the guess.
Again, if you look at what the user experience is with, say, Firefox --
if you have password encryption turned on, then Firefox will prompt you
for the password to unlock your credential storage. This is intuitive
and works well.
If you want a more complicated credential storage setup, then that
should be a user option, not a default. At present, the ~/.authinfo.gpg
credential storage is not something you can present to a normal user and
expect them to understand at all.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-12-09 21:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1290791691.11667.bug-gnu-emacs@gnu.org>
2010-11-28 2:56 ` bug#7487: 24.0.50; Gnus nnimap broken Lars Magne Ingebrigtsen
[not found] ` <m3ipziupey.fsf@quimbies.gnus.org>
2010-12-06 16:11 ` Ted Zlatanov
2010-12-07 23:32 ` Lars Magne Ingebrigtsen
2010-12-08 17:00 ` Jason Rumney
2010-12-09 21:15 ` Lars Magne Ingebrigtsen
2010-12-10 2:55 ` Stefan Monnier
[not found] ` <ids61l$jr6$2@quimby.gnus.org>
2010-12-10 16:18 ` Lars Magne Ingebrigtsen
2010-12-08 17:05 ` Jason Rumney
2010-12-08 23:32 ` Stefan Monnier
2010-12-09 21:10 ` Lars Magne Ingebrigtsen [this message]
[not found] ` <mailman.1.1291931529.5417.bug-gnu-emacs@gnu.org>
2010-12-10 18:48 ` Ted Zlatanov
2010-12-10 20:56 ` Stefan Monnier
[not found] ` <mailman.38.1292016144.4804.bug-gnu-emacs@gnu.org>
2010-12-13 3:19 ` Lars Magne Ingebrigtsen
2010-12-13 17:08 ` Ted Zlatanov
2010-12-13 20:11 ` Lars Magne Ingebrigtsen
2010-12-14 1:08 ` Daiki Ueno
2010-12-15 2:06 ` Daiki Ueno
[not found] ` <mailman.3.1292379760.6505.bug-gnu-emacs@gnu.org>
2010-12-15 14:39 ` Ted Zlatanov
2010-12-15 22:05 ` Daiki Ueno
2010-12-15 23:42 ` Daiki Ueno
2010-12-16 2:45 ` Daiki Ueno
[not found] ` <mailman.13.1292467961.28766.bug-gnu-emacs@gnu.org>
2010-12-16 16:00 ` Ted Zlatanov
2010-12-16 19:15 ` Ted Zlatanov
2010-12-16 19:39 ` Lars Magne Ingebrigtsen
2010-12-16 19:44 ` Lars Magne Ingebrigtsen
2010-11-26 17:10 Jason Rumney
2010-12-05 16:49 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3y67yfy9g.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=bugs@gnus.org \
--cc=monnier@iro.umontreal.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).