Tue, Jun 2
Backported for VSD 3.4
Backported for VSD 3.4
Mon, Jun 1
The relevant changes for Werner's suggestions in T8210#216670 have been ported for VSD 3.4. Try to run Kleopatra as admin to get instructions which registry key to set to which value.
Thu, May 28
It was confirmed that my observation is not relevant for the very special case fixed in this ticket.
In VS-Desktop-4.0.90.1216-Beta (Kleopatra: 782c464a9801d6189e3d3be494922f42857bd26c, GnuPG: 2.5.18) the order of the categories as shown in the Kleopatra settings changes when quitting and restarting Kleopatra.
In VS-Desktop-4.0.90.1216-Beta the VSD-related categories are shown additionally to the categories used in Gpg4win.
Wed, May 27
diff --git a/qt5/src/poppler-form.cc b/qt5/src/poppler-form.cc index 4cf6cb532..6974bdbaa 100644 --- a/qt5/src/poppler-form.cc +++ b/qt5/src/poppler-form.cc @@ -1052,8 +1052,9 @@ static CertificateInfoPrivate *createCertificateInfoPrivate(const X509Certificat certPriv->nick_name = QString::fromStdString(ci->getNickName().toStr());
@ikloecker didn't we have this issue in the past ?
Fri, May 22
Needs testing (also for gpd5x) to understand the current state.
Mon, May 18
VSD 3.4 and Gpg4win 5.x now require gpgex-1.1.1 which includes the fix.
This also affects the VSD 3.4-beta.
Mon, May 11
Thu, May 7
Also setting fixed for VSD 3.4 assuming that gpg4win-tools will be updated for VSD 3.4. (There are no branches in gpg4win-tools.)
Immutability should now be respected for all settings on the GpgOL config page. Additionally, the "autoencryptUntrusted" option was sometimes enabled even if "autoresolved" was unchecked.
Apr 26 2026
Apr 23 2026
As I'd like to have it in vsd34, I'll set that tag (and of course gpd5x, too)
Apr 21 2026
Implemented for the Notepad and Sign/Encrypt Files. Can be tested with the certificates in T6702#216065.
Apr 16 2026
Looks good to me on vsd-3.3.7-beta90.9 @ win10:
Apr 15 2026
Apr 14 2026
Seems I forgot to note that icon removal works when resetting to defaults. And the VSD related Categories are no longer shown in Gpg4win. Tested now with Gpg4win 5.0.2, but I believe it was already ok in 5.0.0.
Apr 13 2026
Apr 8 2026
Maybe. EncryptionResult has a list of invalid recipients and I've changed the code to show the Retry dialog only if there's at least one invalid recipient.
Your suggestion sounds ok to me, maybe with a slight change for the message: "Failed to encrypt the notepad because at least on certificate could not be validated."
I tried to add the list of invalid recipients to the message box, but it seems that gpgsm stops the validation of the certificates at the first invalid recipient. I got only the first Bob certificate reported as invalid recipient when I tried to encrypt to both Bob certificates so that it doesn't make sense to list the (incomplete) list of invalid recipients. It also means that Kleopatra cannot update the invalid recipient certificates because it knows only of one invalid certificate.
Ideally the certificate would change, but Kleopatra has no idea that this certificate turned out to be not valid. In fact, Kleopatra doesn't even know that the encryption failed because of some certificate. It could have failed for any other reason (e.g. full disk). Kleopatra only knows that an error occurred and offers to retry with lower security. (I looked at GpgOL and it does the same.)
yes, basically it's what we want.
Apr 7 2026
Current implementation for the case of an S/MIME certificate which turns out to be invalid when it's used for encryption. Is that what we want?
