Kleopatra from VSD installations should now use gpgv from the GnuPG installed by VSD when verifying the signature of the VERSION file. GPD and Gpg4win installations both use gpgv from the GnuPG installed at the value of the registry key "Software\\GnuPG:Install Directory".
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jul 31 2025
Jul 30 2025
If an error occurs then we emit a failure. But if gpg crashes then gpgme just sees a broken pipe.
Some lines from the log:
2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: [GNUPG:] DECRYPTION_KEY 46ED5D7758C1BD71C27AF928 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: FFA2FCCB2EC589F8 98111E67AE06F2BEFD2BDE10C5D6C91 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: 9005F36A4 u<LF> 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: [GNUPG:] BEGIN_DECRYPTION<LF> 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: [GNUPG:] DECRYPTION_INFO 2 9 0 0<LF> 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: [GNUPG:] PLAINTEXT 62 1753871344 <LF> [...] 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: [GNUPG:] NEWSIG<LF> [...] 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: [GNUPG:] KEY_CONSIDERED F8D51DE0EE16E9B57009B8DE 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: 458612006D8E6F0D 0<LF> [...] 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: [GNUPG:] GPGTAR_EXTRACT 2 0 0 0 0 0 0<LF> [...] 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_io_read: check: [GNUPG:] SUCCESS<LF> [...] 2025-07-30 12:35:29 gpgme[716.808] gpgme:reader: check: ctx->hdd=0x000001b90c8a6a60 got EOF (broken pipe) [...] 2025-07-30 12:35:29 gpgme[716.23bc] _gpgme_cancel_with_err: enter: ctx=0x000001b90c854430 ctx_err=117440570, op_err=0 [...] 2025-07-30 12:35:29 gpgme[716.1e08] gpgme:reader: check: ctx->hdd=0x000001b90c8a68c0 got EOF (closed by us) [...] 2025-07-30 12:35:29 gpgme[716.23bc] gpgme_op_decrypt_ext:186: error: No data <GPGME>\n 2025-07-30 12:35:29 gpgme[716.23bc] gpgme_op_verify_result: enter: ctx=0x000001b90c854430 2025-07-30 12:35:29 gpgme[716.23bc] gpgme_op_verify_result: leave: result=0x000001b90c7d1150 2025-07-30 12:35:29 gpgme[716.23bc] gpgme_get_protocol: call: ctx=0x000001b90c854430 ctx->protocol=0 (OpenPGP) 2025-07-30 12:35:29 gpgme[716.23bc] gpgme_op_decrypt_result: enter: ctx=0x000001b90c854430 2025-07-30 12:35:29 gpgme[716.23bc] gpgme_op_decrypt_result: check: ctx=0x000001b90c854430 result: recipient: keyid=FFA2FCCB2EC589F8, pubkey_algo=302, status=Success 2025-07-30 12:35:29 gpgme[716.23bc] gpgme_op_decrypt_result: leave: result=0x000001b90c5e3290
-> there's a broken pipe; _gpgme_cancel_with_err has ctx_err 117440570 = (GPGME, No data)
-> gpgme_op_decrypt_ext reports an error: No data <GPGME>\n
-> There doesn't seem to be a verify result (although the archive is signed and encrypted)
-> There is a decrypt result with status Success
I had a quick look at the status messages that gpg emits. Unfortunately, gpg doesn't emit a status message after successfully signing a key. So, we may have to check whether the signed key really has a new certification to ensure that the operation succeeded. And we should make future version of gpg emit a success status.
I can confirm that the crash is fixed by the change.
Jul 29 2025
The fix should be available in gpg4win-5.0.0-beta350.
Ideally, this will be solved for VSD 3.4.
Jul 28 2025
Jul 24 2025
Other duplicate texts:
- Enter some characters for Password and some other characters for Repeat and press Return.
- Message box pops up to inform user that the two entered texts don't match. NVDA reads
does not match - try again dialog OK button Enter (not audible) does not match - try again dialog
This has been fixed in pinentry-qt5 (which is used by VSD 3.x).
Jul 23 2025
Done.
Jul 22 2025
Backported for VSD 3.4
Done for gpg4win 5 and backported for VSD 3.4 (provided that the gpg4win-4-branch will be used for VSD 3.4).
Jul 16 2025
Shouldn't be necessary because QGuiApplication's quitOnLastWindowClosed defaults to true, but it shouldn't hurt either.
Add gpd5x tag to ensure testing with Gpg4win.
Jul 15 2025
It's intentional that with Gpg4win migration from %LOCALAPPDATA% does not work because %LOCALAPPDATA% is used by VSD (and GPD) but not by any old Gpg4win.
Jul 14 2025
Jul 13 2025
Jul 10 2025
Jul 9 2025
Jul 8 2025
Staring at some Process Monitor logs I noticed that dirmngr wastes 3-4 seconds trying to connect to localhost:9050 and localhost:9150 looking for tor. After adding no-use-tor to dirmngr.conf dirmngr starts reasonably fast.
In T7379#195089, @ikloecker wrote:Kleopatra does now read the certificates from the card and import them itself instead of relying on gpgsm --learn-card.
Jul 7 2025
I have built the run-* test programs of gpgme for Windows. run-keylist --cms --secret takes about 23 seconds. 3.7 seconds are gpgme initialization/setup (gpgconf --list-dirs, gpgconf --list-components, gpg --version, gpgsm --version, gpgconf --version). Most time (2 x 6-8 s) is lost starting gpg-agent and dirmngr. (keyboxd is not enabled here.)