GNU bug report logs - #21274
25.0.50; epa doesn't understand GPG's default-key option

Previous Next

Full log

View this message in rfc822 format

From: Daiki Ueno <ueno <at> gnu.org>
To: Richard Stallman <rms <at> gnu.org>
Cc: Werner Koch <wk <at> gnupg.org>, 21274 <at> debbugs.gnu.org
Subject: bug#21274: 25.0.50; epa doesn't understand GPG's default-key option
Date: Mon, 17 Aug 2015 17:08:17 +0900

Daiki Ueno <ueno <at> gnu.org> writes:

> Richard Stallman <rms <at> gnu.org> writes:
>
>> Someone sent me gpg-encrypted mail using the throw-keyids option,
>> which I think means it doesn't say which person each key belongs to.
>> The result was I was asked for a passphrase for each key until
>> mine came up.
>>
>> I'm told the recommend way to deal with receiving such mail
>> is to specify default-key in gpg.conf.  I have that setting,
>> so it looks like EPA doesn't recognize it.
>
> According to the GnuPG manual, --default-key is used for signing, not
> for decrypting a message encrypted with --throw-keyids or
> --hidden-recipient.  IMO, it sounds like a natural extension for
> --default-key to support that use-case.  Werner, what do you think?

Apparently, this has already been implemented in GnuPG 2.1, but not in
GnuPG 2.0 nor 1.4:

http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=54591341
http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=blob;f=g10/getkey.c;h=ad7e71cf7ddca38a917756b8a0675b665c3eddec;hb=54591341#l2565

Maybe good to update the documentation and possibly backport it to other
branches?

Regards,
-- 
Daiki Ueno

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.