Page MenuHome GnuPG

dirmngr 2.2 does not ask keyservers for fingerprints
Testing, NormalPublic

Description

The change should be backported to 2.2 to fix key lookups by gnupg-vs-desktop-3.1.22.0-x86_64.AppImage on the default key server.

Event Timeline

Hello,
thanx for fixing this issue ...

Where do i will find the fixed version in order to build an udated AppImage ?

Will this be fixed in gpg 2.2.36 (maybe a reloaded version like gnupg-w32-2.2.35_20220502) or 2.2.37 ?

Best regards ...
Veit

It will hopefully be fixed in 2.2.37.

What i don't understand is ...

When this should be an issue in dirmngr, why does the search on mentioned keyservers work with kleopatra 3.1.16 and an updated backend gpg-2.2.36:


Ah .. Ok, i missed the thread:
Kleopatra: Certificate lookup shows only one result even if there are 100s matches

This also explains the small list of results in contrary to the list that you get from the web frontend ...

Due to https://dev.gnupg.org/T5725#153224 ("The fingerprints are needed by Kleopatra as unique identifier for keys."), is this still implemented in that way ?

Best regards,

Veit

Due to https://dev.gnupg.org/T5725#153224 ("The fingerprints are needed by Kleopatra as unique identifier for keys."), is this still implemented in that way ?

Yes. There is no other way to uniquely identify keys. Even the long key ID that's returned by key servers can be forged nowadays.

ikloecker changed the task status from Open to Testing.Tue, Jul 26, 9:54 AM
ikloecker removed werner as the assignee of this task.
ikloecker triaged this task as Normal priority.
ikloecker moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.
ikloecker added a project: Testing.

The fix has been merged to the 2.2 branch.