Nov 4 2024
Kleopatra shows this option in GnuPG System because gpgconf --list-options gpg-agent lists this option.
High priority since it affects accessibility and was mentioned as problem in the accessibility reports.
This isn't really important at the moment.
Ctrl+A + Ctrl+C to copy to clipboard and Ctrl+V do paste isn't exactly super complicated for people who know how to use the clipboard. -> Low
We decided that Kleopatra should behave the same way as GnuPG when the user clicks "Wrong". Kleopatra should inform the user that the certificate has been marked as not trusted because of the wrong fingerprint.
As discussed today let's use the following heuristic:
- If we find a certificate for the recipient (sub)key in the key cache (ignoring ADSK subkeys) then list this certificate as recipient.
- Else: If we find a single certificate for the recipient (sub)key in the key cache (including ADSK subkeys) then list this certificate as recipient.
- Else: In a second pass, check if any of the already known recipient certificates has a(n ADSK) subkey matching the unknown recipient (sub)key. In this case list this recipient again (so that formatRecipientsDetails doesn't assume an unknown recipient).
- Else: Count the recipient as unknown.
Close ticket. We don't need two tickets for collecting group-related tickets.
Remove assignment. Ticket collections are not actionable by a developer.
Oct 31 2024
@TobiasFella prepared the installation in https://dev.gnupg.org/rW9218ebfb7c01478a6fa7b2892fec4d9fd83ba273 . I left some comments on this commit.
Werner backported this to GnuPG 2.2.45.
Oct 30 2024
$ gpgsm --version gpgsm (GnuPG) 2.2.45-beta27 libgcrypt 1.8.12-beta1 libksba 1.6.7
The last two usages of KIconLoader have been remove in kleopatra master. (libkleo was already good.)
Note that Kleopatra already has clipboard integration via its tray icon, i.e. you can directly sign/encrypt/decrypt/import the clipboard content from there. Unfortunately, it uses a complete different UI for selecting the recipients. Lots of room for improvement/consolidation.
Kleopatra (master; KF6)
Kleopatra just checks if the option "default-new-key-adsk" is set (i.e. it doesn't matter if it's an option with scalar value or list value). The other two options that were changed are not used by Kleopatra.
Oct 29 2024
The possibility to drag certificates from Kleopatra to somewhere else has been disabled for Windows builds. The change has also been backported for vsd33. In the vsd33 AppImage it should still be possible to export certificates by dragging them from Kleopatra to, for example, Dolphin. Maybe we still want to remove the vsd33 tag.
Kleopatra now asks the same questions as the GnuPG backend. The choices the user can make are a bit different because the user already told Kleopatra that they want to trust (or distrust) a root certificate. Therefore, the first dialog only has "Yes" and "Cancel". And the fingerprint dialog (which is only shown for Trust but not for Distrust) only has "Correct" and "Wrong". Another difference is that in GnuPG clicking "Wrong" makes GnuPG mark the certificate as untrusted (which is a bit surprising). In Kleopatra the certificate is left unchanged if the user selects "Wrong".
If gpg-agent's option "no-allow-mark-trusted" is set then the actions "Trust root certificate" and "Distrust root certificate" won't be available. If the option is set while Kleopatra is running then it needs to be restarted to get rid of the actions. If one tries to use the actions then Kleopatra will tell you that you are not allowed to do this. Similarly one needs to restart Kleopatra to make the action available again after the option was unset.
Backported for vsd33
Oct 28 2024
Backported for vsd33
Backported for vsd33 (as discussed with ebo)
Oct 25 2024
This bug exists since Kleopatra offers "Trust root certificate" (i.e. since 2010). allow-mark-trusted seems to be default since Gpg4win 2.1.0. If admins really want to prevent users from messing with the trustlist then they anyway have to use the no-user-trustlist option.