Kleopatra: Improve Kleopatras detection of keyservers
Closed, ResolvedPublic

Assigned To
Authored By
• werner
Oct 27 2021, 4:18 PM
Tags

Description

Kleopatra seems to use the "keyserver" entry from gpg.conf to enable
the automatic key lookup via fingerprint from a smartcard. Thus if
the keyserver is only defined in dirmngr.conf this auto key fetch does
not work. It is a bit surprising given that the standard keyserver
lookup works anyway.

Suggestion: Check the keyserver option from gpg.conf and from
dirmngr.conf and enable the auto key fetch if either of them exists.

Details

Version
3.1.19

Event Timeline

• werner created this task.
• werner created this object with edit policy "Contributor (Project)".
• ikloecker moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ikloecker changed the task status from Open to Testing.Oct 28 2021, 2:55 PM
• ikloecker moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ikloecker added a subscriber: • ikloecker.

Kleopatra now checks both keyserver options. Previously, Kleopatra checked only one of them depending on the version of gpg (< 2.3.0 vs. >= 2.3.0). Note that the automatic lookup is only done if the keyserver option specifies an LDAP server, i.e. if it starts with "ldap".

• ikloecker renamed this task from Improve Kleopatras detection of keyservers to Kleopatra: Improve Kleopatras detection of keyservers.Dec 5 2022, 8:40 AM
• ebo claimed this task.
• ebo added a subscriber: • ebo.

works. tested with VSD 3.1.26 (gpg 2.2.41) and keyserver entry in dirmngr.conf only.

• ebo moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Apr 5 2023, 2:06 PM