gpg-wks-client generates empty files

[Werner Koch]

On Thu, 19 Aug 2021 17:14, Jonas Tobias Hopusch said:

> It's good to see one of you respond to my mail. I was worried that maybe the
> mailinglist broke both the SPF and DKIM checks and prevented it from being

Sorry, for taking long to reply.

> It's been a few months since I generated the key with GnuPG so I don't know if I
> put the extra spaces there. Maybe it's a consequence of leaving out my name
> during UID creation? (Back then I was hesitant to put my name on that key though
> my view on that is more relaxed by now.)

I general we strip all leading and trailing spaces. But there are of
course ways to generate such a user-id, it is covered by the specs.

> This question I'm asking myself at this explanation for the issue is why my
> Gitea instance's signing key was also affected by the bug. (The one with the
> autosign at gitea.jotoho.de UID)

Well, this

           /* Fixme: Unescape fields[9] */
           if (!append_to_uidinfo_list (&mboxes, fields[9],

explains it.  gpg --with-colons returns the user-id with C-style
escapes.  The "https://" has a colon and thus needs escaping.

I have pushed fixes for both bugs to 2.3 and 2.2


Shalom-Salam,

   Werner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20210820/eb77beb1/attachment.sig>