Bug 485308 - Public keys for encryption will be shown as "bad" in the composer, even if they can be used for encryption
Summary: Public keys for encryption will be shown as "bad" in the composer, even if th...
Status: REPORTED
Alias: None
Product: kmail2
Classification: Applications
Component: crypto (show other bugs)
Version: 6.0.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-10 06:40 UTC by Bernhard E. Reiter
Modified: 2024-04-11 06:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
showing the composer and kleopatra displaying the problem (79.31 KB, image/png)
2024-04-10 06:40 UTC, Bernhard E. Reiter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard E. Reiter 2024-04-10 06:40:49 UTC
Created attachment 168332 [details]
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.klassen@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.klassen@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
Comment 1 Bernhard E. Reiter 2024-04-10 07:01:54 UTC
the about dialog of Kontact says 6.0.1, while the package is 24.02.1-kf.265.4.
Comment 2 Bernhard E. Reiter 2024-04-10 07:03:06 UTC
Okay, listing both packages:
kontact-24.02.1-kf.236.3.x86_64
kmail-24.02.1-kf.265.4.x86_64
Comment 3 Bernhard E. Reiter 2024-04-11 06:46:11 UTC
There is a sister report at https://dev.gnupg.org/T7075