Re: Entering passphrase twice when sending PGP signed message

[Hrvoje Niksic <hniksic@xemacs.org>]

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.

In other words, I'd prefer to have two knobs to twist:

- Cache passphrase:

  * Without time limit.
  * With time limit.
  * For the duration of sending of one mail (i.e. to guarantee that I
    only have to type it once for any single mail.)
  * Never cache it.

- Confirm signing/encryption:

  * Confirm signing.
  * Confirm encryption.
  * Confirm both.

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.


[1]
Who ever came up with those key bindings??