https://bugs.kde.org/show_bug.cgi?id=485308
Bug ID: 485308 Summary: Public keys for encryption will be shown as "bad" in the composer, even if they can be used for encryption Classification: Applications Product: kmail2 Version: 5.24.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: bernh...@intevation.de Target Milestone: --- Created attachment 168332 --> https://bugs.kde.org/attachment.cgi?id=168332&action=edit showing the composer and kleopatra displaying the problem Recipients that the user wants to encrypt to are shown as red while the"validity" of a corresponding public key is just "unknown". This is a regression from a previous version and inconsistent with the display of the same public key in Kleopatra. STEPS TO REPRODUCE 1. Make sure to have an email address with a public key in GnuPG that is not fully "valid" for encryption. E.g. by calling `LANG=C gpg --locate-external-keys christoph.klas...@intevation.de` to get the pubkey via WKD, see something like `pub rsa3072/BA842B59E4A30D2F 2021-09-27 [SC] [expires: 2026-07-30] 978EE1FDE4F929229B3207CBBA842B59E4A30D2F uid [ unknown] Christoph Klassen <christoph.klas...@intevation.de> sub rsa3072/11CD70D4D6223146 2021-09-27 [E] [expires: 2026-07-30]` 2. Open the composer, enter the email address. 3. Select "encrypt" 4. (optional) Send the email, and observe a dialog where you can okay the pubkey and encryption, showing that this can be done. 5. (optional) click on the icon to open Kleopatra and see that the pubkey has a validity of unknown. OBSERVED RESULT There is an icon shown left to the address that is a red square with a white cross. If you click on it, you see Kleopatra where there is a purple square with a white question mark. See kontact-24.02.1-pubkey-selection-problem-1.png EXPECTED RESULT As in previous versions the icon should be neutral to indicate that encryption is possible while there is not much trust that the pubkey belongs to the owner of the email address. (Ideally a pubkey fetched via WKD should have enough trust to allow encryption directly, because kmail does not know (yet?) that the pubkey has been fetched via WKD, it must chose an icon that stand for both situations, fully unknown and basic validity.) SOFTWARE/OS VERSIONS rpm -qa | grep kontact- kontact-lang-24.02.1-kf.236.3.noarch Operating System: openSUSE Leap 15.5 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.