[pkg-gnupg-maint] Bug#836458: Bug#836458: Bug#836458: Cannot edit key stored with an empty passphrase

[Daniel Kahn Gillmor]

Version: 2.1.18-1

On Sat 2017-02-18 18:15:12 -0500, Yuri D'Elia wrote:
> On Sat, Sep 03 2016, Werner Koch wrote:
>> I just tried this:
>>
>>   gpg  --edit-key some_key_with_no_passphrase
>>
>> At the prompt, I set a new passphrase using the "passwd" command.  A bit
>> annoying is that you need to repeat it for the subkey.  Next I used
>> "passwd" again and entered an empty passphrase.  I had to confirm that I
>> really want an empty one ("Yes, no protection needed") but then I got my
>> passphrase less key back.  FWIW, I am using the standard Gtk+ Pinentry,
>
> I refreshed my setup a week ago, and started with a fresh environment
> where I re-imported my existing keys and attempted to create new ones.
>
> I cannot reproduce this issue with the current gpg, so I apologize for
> the noise. Maybe there was some issue on my part.

I'm marking this as done with 2.1.18-1, since it think it was likely
solved upstream since 2.1.15-2.  Sorry to not have more details about
specifically when it was resolved.  if someone has more specific info,
please update the fixed/found metadata on this bug.

thanks for following up here, Yuri!

       --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20170220/475a3bc8/attachment.sig>