GitLab

GnuPG-bug-id: 5283

GnuPG-bug-id: 5283

GnuPG-bug-id: 5283

If mixed protocols are not allowed, but for some recipients there are
only OpenPGP keys and for others there are only S/MIME certificates,
then the resolution should fail.

GnuPG-bug-id: 5283

GnuPG-bug-id: 5283

If a common override for an address is given, then the protocol-specific
overrides for this address are ignored.

GnuPG-bug-id: 5283

If the common overrides for an address consist of OpenPGP and S/MIME keys,
then leave the protocol-specific resolutions of the address empty.
If, OTOH, the common overrides for an address contain only keys for
one protocol, then use those for the protocol-specific resolution.

GnuPG-bug-id: 5283

GnuPG-bug-id: 5283

GnuPG-bug-id: 5283

GnuPG-bug-id: 5283

... to get actual and expected values in case of a test failure

GnuPG-bug-id: 5283

* Add trusted S/MIME test CA and replace self-signed S/MIME certificates
  with certificates certified by the test CA
* Add OpenPGP keys and S/MIME certificates with lower/same/higher validity
  than/as corresponding OpenPGP keys and S/MIME certificates
* Remove secret keys of S/MIME certificates of test recipients

GnuPG-bug-id: 5283

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

appearanceFilters was always empty. The code uses MatchContexts to
define filters as appearance-only filters.

GnuPG-bug-id: 5388

GnuPG-bug-id: 5388

These filters mark expired/revoked not VS-NfD compliant keys that have
not been validated (e.g. the result of a remote lookup).

GnuPG-bug-id: 5388

This makes the filters also match expired/revoked keys looked up remotely.
It's possible that the expiry/revocation information returned by the
keyserver is wrong/forged because (some) keyservers do not verify
signatures, but I think it's okay to mark (seemingly) expired keys.

GnuPG-bug-id: 5388

Keys that have not been validated, e.g. keys show in the key server
lookup dialog, cannot be checked for VS-NfD compliance.

GnuPG-bug-id: 5388

Show "not checked" resp. "The validity cannot be checked at the moment."
for keys that have not been validated, e.g. keys that have been looked
up remotely.

GnuPG-bug-id: 5388

Fixes copy&paste error introduced with 5d64856b

GnuPG-bug-id: 5283

Where possible qBinaryFind is replaced with std::binary_search. All
other occurrences are replaced with a custom replacement.

I think using this replacement is much more convenient and results
in better readable and less errorprone code than replacing all usages of
qBinaryFind with std::lower_bound() and the necessary additional check
of the resulting iterator, in particular if a lambda expression is used
as custom comparison function.

If resolution with mixed protocols is allowed, then create a "best of"
list of the resolved OpenPGP and S/MIME keys, i.e. for a given recipient
take either the OpenPGP keys or the S/MIME keys where the choice if
based first on validity and then on the preferred protocol (with OpenPGP
as last resort).

GnuPG-bug-id: 5283

Previously, the result contained empty key lists for unresolved
recipients.

GnuPG-bug-id: 5283

... instead of per protocol and then per address

GnuPG-bug-id: 5283

... instead of per protocol and then per address

GnuPG-bug-id: 5283

GnuPG-bug-id: 5283

GnuPG-bug-id: 5283

The implementations only use variables and methods of the private class.

GnuPG-bug-id: 5283