GitLab

Instead of trying to guess which kind of certificates a file contains
and then just importing the detected kind of certificates, we simply
do an opportunistic import, i.e. we (try to) import OpenPGP and X.509
certificates.

GnuPG-bug-id: 5638

The lookup is not started automatically to prevent unwanted leaking
of information.

GnuPG-bug-id: 5624

Ingo Klöcker authored Oct 31, 2021 and Ingo Klöcker committed Oct 31, 2021

It seems gcc doesn't need this, but clang does.

(cherry picked from commit 82e6ec24)

GnuPG-bug-id: 5666

GnuPG-bug-id: 5666

GnuPG-bug-id: 5672

GnuPG-bug-id: 5672

Without specifying "QPushButton", Qt also applied the background color
to the tooltip which made it very hard to read because the tooltip uses
white text and the positive/negative background color is a light
green/red.

GnuPG-bug-id: 5362

If GnuPG is configured to enforce de-vs compliance, but isn't de-vs
compliant, then show a message that signing/encrypting is not possible
and disable the corresponding buttons.

GnuPG-bug-id: 5362, 5653

If GnuPG is configured to enforce de-vs compliance, but isn't de-vs
compliant, then tell the users that signing/encrypting is not possible
when they try to sign/encrypt something.

GnuPG-bug-id: 5362, 5653

GnuPG-bug-id: 5362

GnuPG-bug-id: 5362

Change using code of deprecated Kleo::gpgComplianceP() and
Kleo::Formatting::complianceMode() to use the new helpers
Kleo::gnupgUsesDeVsCompliance() or Kleo::gnupgIsDeVsCompliant().

The general rule is: If GnuPG doesn't pass the basic de-vs compliance
check, then it makes no sense to label anything as de-vs compliant.

GnuPG-bug-id: 5362

GnuPG-bug-id: 5663

Task: https://phabricator.kde.org/T14543

This allows the user to get a list of smartcard readers that have been
detected by GnuPG. The readers are listed with the reader IDs used by
GnuPG to identify certain readers, e.g. for the reader-port option of
scdaemon.

GnuPG-bug-id: 5662

GnuPG-bug-id: 5661

This option disables the selection of public keys to use for encryption.

GnuPG-bug-id: 5661

GnuPG-bug-id: 5652

This is used by Gpg4win to append the Gpg4win version instead of the
KDE release service version to the version number.

The possibility to override the RELEASE_SERVICE_VERSION was inadvertently
removed with d07f085d.

This version includes the second part of the uiserver socket fix.

(cherry picked from commit 55cdf4f9)

This ensures that clients find the uiserver socket used by Kleopatra.

GnuPG-bug-id: 5619

This is neccessary because the commit:
a0883f36

Has a very large impact on bug reports. We need to have our
users check easily if they have that commit or not.

Calling GpgME::dirInfo() which uses 'gpgconf --list-dirs' implicitly
creates the socket directory (since gpg 2.1.20), so we omit a check.
For older versions of gpg (which are unsupported since a long time)
we keep using the old code which may create a gnupg home directory
with unsafe permissions.

GnuPG-bug-id: 5619
BUG: 441957
FIXED-IN: 21.08.2

When testing this with 2.2.31 it showed errors so better
not offer a button that only produces an error. According
to the GnuPG Maintainer this should work with 2.3

Having them with row stretch and aligned in the center had the
effect that the widgets moved when new recipents were added. So
we just stretch the second row now to ensure that it takes up
the available space.

When Kleopatra is started the readerstatus thread may check
for smartcards before the gpg-agent and scdaemon are started
which can take a while, especially on Windows. So we now
handle the GPG_ERR_ASS_CONNECT_FAILED and wait for it to
come up. GnuPG itself does something similar.

The accessibility improvements are finished for now and there
were several new features that should be distinguished.