with VS-Desktop-3.3.90.19-Beta, and settings disableAutoPreview and ReadAsPlain
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Oct 10 2025
Oct 9 2025
Might this be related to T4953?
Oct 6 2025
(auto resolved due to the keyword "resolved" in the commit message)
The window was not reenabled on failure see 8d174d5
Oct 4 2025
That is on purpose. With a signed mail you have at least a way to tell who sent the mail. An unsigned but encrypted mail can be send by anyone and you netter don't use HTML links there.
Oct 2 2025
(removed: wrong statement)
Note: I also activated Sign/Encrypt by default, if that matters
see also https://dev.gnupg.org/T7609
Sep 30 2025
Sep 29 2025
Sep 25 2025
Sep 24 2025
ECC support for X.509 and in particular pkcs#12 format is limited. That is in general not a problem because such certificates are stored on a token and not on disk.
Tested with VS-Desktop-3.3.90.12-Beta
Sep 23 2025
2.2 test can be done with GnuPG-VS-Desktop-3.3.90.12-Beta-Standard.msi from Sep 17
Sep 22 2025
Using gpg4win-5.0.0-beta369 @ win10 I can't reproduce it with use-keyboxd, but without use-keyboxd:
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).