Em 16-06-2016 11:51, Peter Lebbing escreveu: > On 16/06/16 16:13, Mike Kaufmann wrote: >> I've tried this commands with all the KeyGrips that are listed with a >> command similar to >> gpg2 --with-keygrip -K DCDFDFA4 sec rsa1024/DCDFDFA4 2012-03-17. > That part got accidentally mangled when I asked my mailer to reflow the > message. It was supposed to be: > >> $ gpg2 --with-keygrip -K DCDFDFA4 >> sec rsa1024/DCDFDFA4 2012-03-17 [SC] [expires: 2016-06-17] >> Keygrip = 2F677680CA15F6F7B963AF35822E8EC01FBF840A >> uid err Test Teststra <test@work.invalid> >> uid err Test Teststra (Koning van Wezel) <test@example.invalid> >> ssb rsa1024/77A3395A 2012-03-17 [E] >> Keygrip = 15CB764B81D542CF921978CA89910C69D53F4E2D >> ssb rsa2048/38EF7410 2016-01-12 [A] >> Keygrip = 3D88DC9D60F791821AF8D537EEAC3C8DF7720D63 > > >> I always receive the message >> ERR 67108881 No secret key <GPG Agent> > I'm at a loss, frankly. I don't understand. You're using GnuPG v2.1.11, > you can use the key itself, but the agent isn't aware of having it! That > does not compute. I can only think of one thing. Are you really using > GnuPG v2.1.11, or do you have GnuPG 1.4 co-installed and are you using > that? If the latter, that's not going to work with keygrips. If the name > of the binary you're invoking is "gpg", what does > "gpg --version" say? > > Could you show the invocation and output of using gpg to sign or decrypt > something? Please add "-v" to the command line to make it more verbose. > And could you show command and output for determining the keygrip you're > intending to use? > > HTH, > > Peter. >
Hello guys, I think this is related to the following issue I opened last year: https://bugs.gnupg.org/gnupg/issue2015 Best Regards, Marcos A. Lenharo _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
