Page MenuHome GnuPG

Kleopatra: Failing at certifying key
Closed, ResolvedPublic

Description

Hello,
my problem is, that I want to authenticate a public key from a friend of mine. But it has to be visible for everyone and it should be exportable. So I did the checkmark at "Authenticate visible for everyone (exportable)" (02.png) but I get an Error (03a.png) which only occurs, when I want to make a visible authentication. And I don't know what to do because I found nothing in web to this error message nor error code.

Event Timeline

werner added a subscriber: werner.

Please let us know your gpg4win version.

This comment was removed by Chris1991.

The about dialog where it tells unknown windows version means it's Gpg4win-3.1.13 (the only version affected by T5056 )

Could you try this with the current Version 3.1.15 again? There were some changes that might have an effect.

The "general error" is pretty common when signing keys when Kleopatra's expectation of what the backend does do not overlap.

Alternatively you can use the command line "gpg --sign-key NAME_OR_KEYID" to do it on the command line without kleopatra. But it would be interesting if GnuPG on the command line would also run in an error or give you some kind of warning message or something that might explain why Kleopatra runs into this unexpected state.

I set it to Normal priority. It would be good to find out what exactly is the problem with this key so that we can fix this in kleopatra and handle it.

ikloecker renamed this task from Failing at authenticating key to Kleopatra: Failing at authenticating key.Dec 5 2022, 9:17 AM
ikloecker renamed this task from Kleopatra: Failing at authenticating key to Kleopatra: Failing at certifying key.
ikloecker removed Version.

Wild guess: Since creating a local certification seems to work, but creating an exportable certification fails, maybe the problem occurs when trying to promote an existing local certification to an exportable certification.

ikloecker claimed this task.

Gpg4win 4.4.0 has just been released. I assume that this has been fixed in the meantime. In particular, "General error" should happen a lot less. If the problem still occurs with Gpg4win 4.4.0 then reopen the ticket.