Using gpg4win-5.0.0-beta369 @ win10 I can't reproduce it with use-keyboxd, but without use-keyboxd:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Sep 23 2025
Sep 22 2025
Sep 18 2025
Looks like there is a rights problem modifying the body of those mails
Every time when we try to modify the HTMLBODY or BODY property we fail with MAPI_E_NO_ACCESS.
The attached mails in those tests where ms-tnef formated (winmail.dat)
omhelp.cpp:lookup_oom_dispid:160 wchar_t alloc 00000155d9abfe80:HTMLBody
07:35:08/5284/oomhelp.cpp:put_oom_string:674 wchar_t alloc 00000155ccf77710:<html><head></head><body><table border="0" width="100%" cellspacing="1" cellpadding="1" bgcolor="#0069cc"><tr><td bgcolor="#0080ff"><p><span style="font-weight:600; background-color:#0080ff;"><center>OpenPGP Nachricht</center><span></p></td></tr><tr><td bgcolor="#e0f0ff"><center><br/>Bitte warten Sie w�hrend die Nachricht entschl�sselt / gepr�ft wird...</td></tr></table></body></html>
07:35:08/5284/oomhelp.cpp:put_oom_string: Putting 'HTMLBody' failed: 0x80020009
07:35:08/5284/DBG_OOM/oomhelp.cpp:dump_excepinfo: Exception:
wCode: 0x1000
wReserved: 0x0
source: Microsoft Outlook
desc: Sie besitzen nicht die erforderliche Berechtigung, um diesen Vorgang auszuf�hren.
help: null
helpCtx: 0x0
deferredFill: 0000000000000000
scode: 0x80070005
07:35:08/5284/TRACE/oomhelp.cpp:put_oom_string:699: return
07:35:08/5284/ERROR/mail.cpp:decryptVerify_o: Failed to modify html body of item.Sep 17 2025
Sep 16 2025
Backported to 2.2 but not yes tested with 2.2
Can you please repeat this with gpg4win-5-beta using the keyboxd and also using the pubring.kbx (i.e. w/o use-keyboxd in common.conf)?
Sep 10 2025
Sep 9 2025
Sep 8 2025
Here are the messages and logs, when trying to open them:
Sep 5 2025
Sep 3 2025
Note that disabling Auto-preview is not the default and has only been implemented to work around severe performance degradation with certain MalwareAnti-Virus software.
In contrast to gnupg22 master did not proper show OCB compliance - not everything has yet been forward ported. But we can do so now and test master by setting GNUPG_ASSUME_COMPLIANCE=de-vs
Sep 2 2025
Apr 2 2025
Mar 7 2025
Checked with version 4.0.0.250370 (Gpg4win-5.0.0-beta125):
Feb 13 2025
Feb 12 2025
Feb 10 2025
Feb 5 2025
Jan 31 2025
Jan 22 2025
VS-Desktop-3.2.94.481-Beta: OK
Jan 16 2025
works in VS-Desktop-3.2.94.481-Beta, the certificate for the newly generated key has the default expiry date of 3 years there.
Jan 9 2025
Backported for VSD 3.3
Jan 7 2025
OK in VS-Desktop-3.2.94.478-Beta
removing the gpgcom tag as its only relevant for vsd and is already backported
Jan 6 2025
Backported for VSD 3.3
Dec 20 2024
Works, tested with VS-Desktop-3.2.94.474-Beta
The layout is totally different now in VS-Desktop-3.2.94.474-Beta but the "generate new key" action is now hidden for the slots (while still there in Gpg4win 4.4).
Dec 16 2024
There's the VERSION file that is used for customizing the About data for VSD and GnuPG Desktop. It's an ini format file that's read with QSettings.
Doing the changes to the text is easy enough, but I'm not sure whether we have a nice way of doing something only in a VSD version.
The changes had to be reverted, a working solution is planned for later
Dec 3 2024
Looks like there's something not correct in the completion model. Or we use different criteria for showing the blue "i" (as "information") which doesn't make it better. Reopen?
This is long done, but only for Qt 6-based releases. Andre's comment T6663#175481 has also been addressed.
Tested Gpg4win 4.4:
Interesting, when you search for the UID, it looks as before, with the green check mark:
I think this is resolved. In the Sign/Encrypt dialog we now offer the individual user IDs instead of the certificates, i.e. the two user IDs of the Udo certificate are both offered and one should be listed as certified and the other one as not certified (if one is certified and the other one isn't; for me both user IDs are ultimately trusted).
Nov 21 2024
Nov 19 2024
I suggest to make the following text changes for the VSD versions only:
Nov 14 2024
Nov 8 2024
Gpg4win-Beta-75:
Checked the property details of some files in "Progams (X86)" and found several without product name, E.g. libgpg-error-0.dll and other dlls located at C:\Program Files (x86)\GnuPG\bin.
Or gpgolconfig.exe at C:\Program Files (x86)\Gpg4win\bin and the examble from above, libKF5JobWidgets.dll, shows no product name either.
Nov 5 2024
Oct 23 2024
This is now merged into master
Oct 17 2024
After recompiling, it works!
I backported the work of Andre for qt6 to master/kf5. It's in the branch work/carl/product-name-kf5
Oct 9 2024
This is also relevant for VSD 3.3. Backport is not needed, but gpg4win/VSD needs to include current gpgme.
Oct 4 2024
gpg4win-Beta-50:
Columns are now displayed as expected with a fresh installation, too.
Oct 1 2024
Sep 26 2024
That was resolved with vsd 3.2.0
Aug 19 2024
Without administrator rights it does not work for me, since it then cannot write to %PROGRAMDATA% to install the VS-NfD mode config files. But the only thing for "does not work anyway" that I know and could quickly see is that "IPC connect call failed" problem with GPGEX (which we are planning to remove / replace anyway). So I don't think it is very important to remove this and addtionally we do not know if this is something that is used, we have offered it from the beginning but have no data if our customers use it. We can suspect that we would have seen more support questions about the gpgex error if it was widely used. But I always thought that the "only for me" installation option was useful for some use cases.
I think the executables also use the same values for translation.
Okay, I see now that this is US-English and Unicode.
Okay. let me do that for the next library releases.
Aug 8 2024
The additional changes have been backported for VSD 3.3
Aug 6 2024
To clarify what I mean by the missing VarFileInfo block. Currently the GnuPG binaries have versioninfo.rc files but only the version number is displayed for dlls as their pattern did not have the VerFileInfo block: The libassuan-0.dll displayed in this screenshot is from the 2.2.43 package and the assuan-9.dll is self compiled but including the patch below that. I would like to commit such a patch to all libraries that require it if that is okay with you.
Aug 5 2024
I added some comments to the commit. But
Aug 1 2024
Jul 29 2024
A better solution might be to use categories to have that element "this message will be signed / this message will be encrypted" above the edit window. But what I find more important and so much more a high priority is that in cases we have a failure saving the draft info flags an error message should come up. This happened for a customer and in the logs I could see that MAPI returned an error. the button was not toggled in this case but the mail also was not marked for encryption. T7144 is the task for that so I'd suggest to start with that one.
In gpgoladdin:
Changing the icon is unusual and does not match a native look and feel in Outlook where toggle icons are there for a reason, to be toggled or not. This is also the way how Outlooks native encrypt & sign works and Microsoft will probably have thought about this a bit.
Jul 28 2024
Phew. Got it. a new script: "gccwrap.sh.in"
Jul 9 2024
fixed in https://invent.kde.org/pim/kleopatra/-/merge_requests/243; we were not calling the visibility logic when initially creating the view.
Jul 5 2024
I have to correct myself. After restarting Kleopatra, only the following columns are shown, without any changes from my side:
Jul 4 2024
On a fresh install Version 3.2.2.2405000+git~ (Gpg4win-4.3.2-beta35) are now all available columns displayed by default: