GitLab

We simply use the text color also for links. Links are still
recognizable by the underlining.

GnuPG-bug-id: 5535

* Make ResultItemWidget a composite widget that can receive focus.
* Ensure correct focus order when adding a new result item widget.
* Add forceSetTabOrder helper for setting the focus order of widgets
  with any focus policy (including Qt::NoFocus).

GnuPG-bug-id: 5535

* Add UrlLabel, a label for displaying a single link, which
  * automatically gives focus to/selects the displayed link when the
    label gets focus,
  * sends a text selection event to the accessibility clients when
    a link is selected,
  * works around a bug in QLabel::focusNextPrevChild(false)
* Add AccessibleRichTextLabel which allows accessibility clients to
  retrieve the selected text of a UrlLabel
* Use UrlLabel for the Diagnostics/Show Audit Log label

GnuPG-bug-id: 5535

MR: !5

GPGME will soon get support for it.

With GPGME 1.11.2 there will be an "Audit Log" for OpenPGP
that allows kleopatra to show gpg's stderr in case of errors.

With GPGME 1.11.2 we can detect if an MDC error occured
because of an old algorithm. This is common enough that
we need a proper handling.

It is now detected, the user is shown a notification and
gets the option to "Force decryption" so that the
user could then ideally re-encrypt the file with a modern
algo.

GnuPG-Bug-Id: T4038

Fixes 'lambda-expression in unevaluated context' error in some places and generally
switches to Q_ASSERT, which is what we should be using in a Qt app anyway.

This notes down the copyright in files where I modified more
then 20% of the lines in the last two years according to git
blame.

After a verify with no public key the next step for the user
should be to import / certify the key. So we should offer these
options.

If we have no information it's too strong to warn. This is
especially discouraging users to sign + encrypt because an
encrypted only message looks better to others who don't have
a key with a high validity for you.

The difference between Neutral and Negative was also to small
in the current KColorScheme for us to work.

Manual Decrypt / Verify is already an interactive task. The
user can just look at the color / summary line anyway and ignore
the details. Change based on user feedback.

This also includes lots of boost::shared_ptr -> std::shared_ptr
changes, but there are still places where boost is used. We should
definitely do a second round of clean up later on.

This uses the same colors as KMail does. Should be moved into
libkleo. This also changes how the stylesheet is applied to avoid
inherting the stylesheet in the certificatedetailsdialog.

This handles the keyLink directly in the resultitemwidget and
fixes the behavior, by matching the expected format with the
actual keylink format.

BUG: 355084