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

2017-02-20 Thread 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

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

2017-02-18 Thread Yuri D'Elia
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 pas

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

2016-09-03 Thread Werner Koch
On Sat, 3 Sep 2016 13:46, wav...@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 bei

Bug#836458: Cannot edit key stored with an empty passphrase

2016-09-03 Thread Yuri D'Elia
Package: gnupg Version: 2.1.15-2 Severity: important gnupg2 seems to think best that empty passphrases should be abolished. During the migration from gpg1 to 2, a key previously stored with an empty passphrase cannot be used anymore: - attempting to use the key prompts for a passphrase, even th