Re: January/February KDE PIM summary blog post
Ingo Klöcker <[email protected]> Sat, 04 Mar 2023 17:58:51 +0100
| Newsgroups | gmane.comp.kde.devel.pim |
|---|---|
| Message-ID | <5914960.lOV4Wx5bFT@daneel> |
On Mittwoch, 22. Februar 2023 17:09:32 CET Volker Krause wrote: > If you have contributed in January or February, a summary of your most > noteworthy changes would be helpful, bonus points for corresponding > screenshots or links to already existing blog posts. ### Kleopatra * Multiple files with certificates are now imported one after the other instead of concurrently. This makes it easier to figure out for which file one has entered the wrong passphrase and avoids problems with concurrent modification of the certificate storage. ([T6323](https://dev.gnupg.org/T6323)) * If a compliance mode is active, then Kleopatra now offers only compliant algorithms when creating new OpenPGP certificates or S/MIME CSRs. ([T6325] (https://dev.gnupg.org/T6325)) * Kleopatra now uses gpgtar instead of gpg combined with tar, when creating or decrypting encrypted archives. This should speed up the creation or decryption of large encrypted archives on Windows. ([T5478](https://dev.gnupg.org/T5478)) * The users can now give a different file name if after the completion of a signing and/or encryption operation Kleopatra detects that there is already a file with the original file name of the signing/encryption result. Previously, the users could only choose to overwrite the existing file or to cancel the operation. ([T6372](https://dev.gnupg.org/T6372)) The screenshot isn't really that impressive. Regards, Ingo
T6372.png
(image/png, 24 KB) - not displayed
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQTbjgIOMowwlCBgvyGxb1mVFkdKugUCZAN4ywAKCRCxb1mVFkdK ukzrAQDplnhypGQ3UsMFFrgsN67FbTmVxnE/x0SuC968uTGTmwD+JGjNdLcjzWZy gjg8vjklOkfXlvEAxpbbKZBLy8I2UAo= =V6Aa -----END PGP SIGNATURE-----