simplifying the use of --throw-keyid option

[Todd]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Shaw wrote:
> On Wed, Apr 02, 2003 at 03:39:35AM +0200, Malte Gell wrote:
>
>> if one gets a message encrypted with the --throw-keyid option the 
>> receiver's GnuPG has to try all available secret keys and this can be a 
>> bit annoying if one has several secret keys.
>> So, wouldn't it be a nice idea to have a new option "--encrypted-with" 
>> to simplify this ?
>
> The development branch has better handling of such messages.  Instead
> of prompting for each secret key, it prompts for a single passphrase
> and tries it against all keys.  This will be in 1.4.

Pardon me for asking a question when I know very little about the subject,
but why not display the key for which gpg is asking for a passphrase?  I'm
thinking of what ssh does, using key based authentication, it will prompt
you something like:

    Enter passphrase for key '/home/user/.ssh/id_rsa':

Could that be done for gpg when it's trying your various secret keys?
Obviously, it would use either the keyid or some other identifier in place
of the file path as ssh uses.

- -- 
Todd              OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp
============================================================================
Why does a slight tax increase cost you two hundred dollars and a
substantial tax cut save you thirty cents?
    -- Peg Bracken

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.

iD8DBQE+i4u0uv+09NZUB1oRAq04AKDaBNqgoz816e1ohRIecjxfgPFBEQCcDGBd
54P+mLwVU73kmtKWTIoml4w=
=hpP1
-----END PGP SIGNATURE-----