Page MenuHome GnuPG

Kleopatra: Adapt to config changes in GnuPG master
Closed, ResolvedPublic

Description

For use with GnuPG-2.3 Kleopatra / GPGME and the cryptoconfig GUI in libkleo need some adaptions because some options changed and some are new.

@ikloecker Can you look into this? I don't know the differences myself and would compare the options from "gpgconf --list-options gpg" for example from 2.3 and 2.2 to find differences.

Event Timeline

ikloecker moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Mar 3 2021, 2:36 PM

When opening the configuration dialog Kleopatra reports:

Backend error: gpgconf does not seem to know the entry for dirmngr/LDAP/LDAP Server
Backend error: gpgconf does not seem to know the entry for gpg/Keyserver/keyserver
Backend error: gpgconf has wrong type for dirmngr/LDAP/ldaptimeout: 2 0
Backend error: gpgconf does not seem to know the entry for dirmngr/LDAP/max-replies

Also:

org.kde.pim.kleopatra: "Backend error: gpgconf doesn't seem to know the entry for gpg-agent/Security/allow-mark-trusted"
org.kde.pim.kleopatra: "Backend error: gpgconf doesn't seem to know the entry for gpgsm/Security/auto-issuer-key-retrieve"

ikloecker moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Mar 8 2021, 1:03 PM

Reopening because at least a debug build of Kleopatra crashes with an assertion when applying changes.

Applying changes is fixed.

Retrieving the default (public) key algorithm from GnuPG 2.3 works now.