- User Since
- Mar 27 2017, 4:49 PM (166 w, 2 d)
Jul 13 2017
Thank you very much for addressing this so quickly. I agree that corrupt data needs no further details here.
Jul 12 2017
I am using Debian 9 with the packaged versions. For gnupg this is 2.1.18.
Jul 11 2017
Jul 20 2010
EDIT: The NO_SECKEY comes from a second key for which I do not have the private
key. But all I get after pressing cancel is BAD_PASSPHRASE, which could happen
as well if the user really got it right on the second try.
Hmmm... I am talking about GnuPG 1.4.10 here. I am not getting anything like
this. I am, however, using gpg-agent from gpg2.