From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Entering passphrase twice when sending PGP signed message
Date: Sun, 14 Sep 2003 23:48:22 +0200 [thread overview]
Message-ID: <iluekyjxcrd.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3brtnz3uy.fsf@hniksic.iskon.hr> (Hrvoje Niksic's message of "Sun, 14 Sep 2003 19:17:41 +0200")
Hrvoje Niksic <hniksic@xemacs.org> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> I agree, but to clarify, I think the passphrase cache should have a
>> few modes: (I'm not sure the modes marked with '(?)' are useful.)
>>
>> * Disabled.
>> * Enabled for decrypt. (?)
>> * Enabled for sign. (?)
>> * Enabled for decrypt and sign.
>> * Enabled for decrypt and sign, but require confirmation for sign.
>> * Enabled for decrypt and sign, but require confirmation for decrypt. (?)
>> * Enabled for decrypt and sign, but require confirmation.
>>
>> I.e., I didn't mean PGG should ask for a passphrase and then issue
>> yes-or-no-p, instead I meant that if the passphrase is cached, PGG
>> should use yes-or-no-p before using the cache.
>
> I still believe that caching should be orthogonal to using
> yes-or-no-p. That is, if confirmation is required for signing, I
> should be required to confirm. Then, depending on whether passphrase
> has been cached or not, I may or may not also have to type in the
> passphrase.
If you run with a disabled passphrase cache, I don't think this would
result in a sensible user interface. Specifically: you would have to
enter the passphrase AND type 'yes' every time. I would be rather
annoyed by the useless yes-or-no-p query in this situation. Entering
the passphrase is, to me at least, the same as approving the
operation.
> On the other hand, does it really happen to you that you could sign
> something by mistake? When I was signing my mail, I had to press `C-c
> C-m s o' [1] to add the appropriate MML markup -- it didn't happen
> automagically.
It happens for me automatically, I have some hooks that look up an
attribute in my bbdb that say if I should add a MML encrypt tag, per
recipient. But my customization is buggy (naturally), so sometimes it
add a MML tag erroneously, and I rarely notice until I try to send the
message. But since there is a passphrase prompt (or would be a
yes-or-no-p) I can C-g and remove the MML tag.
> Who ever came up with those key bindings??
Can you find a better, unallocated, key binding, that doesn't conflict
with some mode that often can be enabled in message buffers?
next prev parent reply other threads:[~2003-09-14 21:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 13:27 Hrvoje Niksic
2003-09-13 21:24 ` Simon Josefsson
2003-09-13 23:20 ` Hrvoje Niksic
2003-09-14 0:41 ` Simon Josefsson
2003-09-14 1:22 ` Hrvoje Niksic
2003-09-14 12:05 ` Simon Josefsson
2003-09-14 15:06 ` Hrvoje Niksic
2003-09-14 15:18 ` Simon Josefsson
2003-09-14 17:17 ` Hrvoje Niksic
2003-09-14 21:48 ` Simon Josefsson [this message]
2003-09-14 23:03 ` Jesper Harder
2003-09-14 23:15 ` Simon Josefsson
2003-09-15 0:52 ` Jesper Harder
2003-09-15 11:18 ` Simon Josefsson
2003-10-17 18:03 ` Lars Magne Ingebrigtsen
2003-10-17 21:44 ` Simon Josefsson
2003-10-17 22:39 ` Lars Magne Ingebrigtsen
2003-10-18 0:04 ` Simon Josefsson
2003-10-18 15:49 ` Jesper Harder
2003-10-18 16:26 ` Lars Magne Ingebrigtsen
2005-10-13 19:48 ` Attachments and security menu (was: Entering passphrase twice when sending PGP signed message) Reiner Steib
2006-04-26 20:30 ` Attachments and security menu Reiner Steib
2003-09-14 21:02 ` Entering passphrase twice when sending PGP signed message Matthias Andree
2003-09-14 21:38 ` Simon Josefsson
2003-09-14 23:12 ` Matthias Andree
2003-09-14 23:49 ` Simon Josefsson
2003-09-15 0:10 ` Matthias Andree
2003-09-13 23:30 ` Jesper Harder
2003-09-14 1:17 ` Hrvoje Niksic
2003-09-14 1:45 ` Jesper Harder
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=iluekyjxcrd.fsf@latte.josefsson.org \
--to=jas@extundo.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).