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

[Werner Koch]

On Sat,  3 Sep 2016 13:46, wavexx at thregr.org said:

> gnupg2 seems to think best that empty passphrases should be abolished.

No, it does not think so.  In fact I often create keys w/o a passphrase.

> - attempting to use the key prompts for a passphrase, even though entering an
>  empty one is being refused.

I don't get a pinentry prompt  for a key w/o a passphrase.

> - editing the key and using 'passwd' results in the same (the empty passphrase
>  is refused when entering the existing passphrase).

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,


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
 /* Join us at OpenPGP.conf  <https://openpgp-conf.org> */
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 162 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20160903/f1c7ffe2/attachment.sig>