From: Lars Magne Ingebrigtsen <lmi@gnus.org>
To: bug-gnu-emacs@gnu.org
Subject: Re: bug#7487: 24.0.50; Gnus nnimap broken
Date: Wed, 08 Dec 2010 00:32:36 +0100 [thread overview]
Message-ID: <m3y681duqz.fsf@quimbies.gnus.org> (raw)
In-Reply-To: 87aakihof8.fsf@lifelogs.com
Ted Zlatanov <tzz@lifelogs.com> writes:
>>> Upon logging in, I am prompted to add my login credentials to
>>> ~/.authinfo.gpg. This brings up a confusing buffer asking me to mark
>>> a public key, which I have discovered by trial and error only works if
>>> I select no public keys so it falls back on symetric encryption.
>
> LMI> Yes, that interface is so confusing it's ridiculous.
>
> I also had trouble with it the first time. Perhaps there should be more
> information on that screen.
This is what the user is faced with:
----
Select recipents for encryption.
If no one is selected, symmetric encryption will be performed.
- `m' to mark a key on the line
- `u' to unmark a key on the line
[Cancel][OK]
e <person I somehow have a certificate for>
----
And this is for storing a ~/.authinfo.gpg file. If there's one thing
the user don't want to do, it's "select recipient for encryption".
And how many users know what "symmetric encryption" is anyway?
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.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-12-07 23:32 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 [this message]
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
[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=m3y681duqz.fsf@quimbies.gnus.org \
--to=lmi@gnus.org \
--cc=bug-gnu-emacs@gnu.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.
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).