Re: November/December KDE PIM summary blog post

On Mittwoch, 28. Dezember 2022 10:02:06 CET Volker Krause wrote:
> Hello everyone,
> 
> it's time for the bi-monthly blog post again :)

Here is a summary of (my changes) in Kleopatra:

### Kleopatra

On 20 December, [Gpg4win 4.1.0](https://lists.wald.intevation.org/pipermail/
gpg4win-announce/2022/000099.html) including the brand-new GnuPG 2.4.0 and a 
current snapshot of Kleopatra was released for Windows. On the same day, 
[GnuPG Desktop®](https://gnupg.org/download/index.html#binary) based on the 
same sources was released as AppImage for Linux.

These releases include the following (usability) improvements and fixes that 
were made in the last two months:

* The problem that a wrong user ID was sometimes preselected when certifying a 
single user ID of a key with invalid user IDs was fixed. ([T6265](https://
dev.gnupg.org/T6265))
* Actions that require the secret key material can no longer be started if the 
secret key material is not available (e.g. because it is stored on a smart 
card). This prevents confusing errors when users tried to use those actions. 
([T6214](https://dev.gnupg.org/T6214))
* The initial keylisting that is done on the start of Kleopatra does now 
suppress the potentially slow automatic key validity check. This prevents 
seemingly random slow starts of Kleopatra. ([T6261](https://dev.gnupg.org/
T6261))
* The workflow for giving your own keys and the keys of other people the power 
to certify other keys was radically simplified. ([T6148](https://dev.gnupg.org/
T6148))
* The workflow for moving a private key to a smart card was simplified by 
offering the deletion of the locally stored private key after copying a key to 
a smart card. Previously, this workflow involved the export of the public key, 
the deletion of the complete certificate and the re-import of the exported 
public key. ([T5836](https://dev.gnupg.org/T5836))
* Additionally, two bugs were fixed that could occur when copying a key to a 
smart card. ([T6281](https://dev.gnupg.org/T6281)), ([T6287](https://
dev.gnupg.org/T6287))
* Invalid S/MIME certificates are no longer offered when encrypting something. 
([T6216](https://dev.gnupg.org/T6216))
* The generation of an ECC key with curve Curve25519 on a smart card is now 
only offered if the smart card supports this curve. ([T4429](https://
dev.gnupg.org/T4429))
* Kleopatra now supports newer NetKey smart cards additionally to NetKey v3 
smart cards. ([T6277](https://dev.gnupg.org/T6277))
* The certificate import was improved by offering diagnostic output after the 
import (to better identify problems) ([T6268](https://dev.gnupg.org/T6268)), 
by skipping the optional certification process when importing own public keys 
([T6183](https://dev.gnupg.org/T6183)), by reporting failed imports 
immediately when importing multiple files ([T6302](https://dev.gnupg.org/
T6302)), and by supporting the import of UTF-16 (and UTF-32) encoded 
certificates ([T6298](https://dev.gnupg.org/T6298)).
* When editing certificate groups the list of available certificates now only 
shows certificates that are not in the group. This makes it easier to spot 
certificates that are missing in the group ([T6295](https://dev.gnupg.org/
T6295)).
* On Windows, sometimes texts with international characters that were read 
from the backend processes were displayed incorrectly, e.g. the details of S/
MIME certificates. This problem was fixed. ([T5960](https://dev.gnupg.org/
T5960))
* It's no longer possible to start the certification process for expired keys. 
And canceling the certification process is now handled gracefully. ([T6305]
(https://dev.gnupg.org/T6305))

Regards,
Ingo

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQTbjgIOMowwlCBgvyGxb1mVFkdKugUCY68cgQAKCRCxb1mVFkdK
ujZxAQDs24OYsWPzpE3Z47LH0AECGW27SuK8xIYXLiXALDjgJQD6AiDX3HajGQP0
C3d0x48ttgFXkn2RdmuKsAxIccTrxgI=
=pXZq
-----END PGP SIGNATURE-----