Looking at sign_file I can see several places though where it does goto leave before gcry_md_open is called on md. So the fix seems obvious to initalize md to NULL so that the gcry_md_close in the leave part does not work on an uninitialized variable.

gpg (GnuPG) 2.4.4-beta56
libgcrypt 1.11.0
gpg -z0 --yes --batch -esu ldata-test -r ldata-test 10gb-random.dat > 10gb.gp 13,37s user 22,54s system 95% cpu 37,421 total

Please excuse my question but this issue has been WIP for 8 months. I think it was forgotten a bit. Especially since we are not shipping Okular for general signing of PDF documents this issue might help as a stopgap for Smartcards which we do not yet support natively and reduce the pressure a bit to add more PKCS#15 smartcards which can currently be used with Adobe and Mozilla NSS through their proprietary PKCS#11 modules. So I would like to raise the priority for this a bit. But I don't think high is appropriate. That would be for werner to decide.

If you tested it yourself I would say this is enough to move such a task to resolved. If someone else should test it you should remove yourself as the assignee. I will test this by comparing 2.4 performance to master. We need to clean up the WIP tasks in our workboard.

Hello,
this is a support question since you are not a customer to my knowlege please use https://www.gpg4win.org/community.html

In T6775#177408, @werner wrote:

Are you sure this is from a regular Outlook installation and not the common web based outlook? Please enable GpgOL logging and share the log with us. Do not use production keys or messages.

There should not be an exception "Invalid crypto engine" in that call. I expect that gnupg errors out immediately if the parameter with tofu is given while instead it should print a warning and show no information. Or of it errors then Invalid Crypto Engine is definitely the wrong error for that.

I got an idea. Since the gnupg manual is part of that submenu I will include the gnupg manual in Gpg4win. Not sure yet what to do about Linux since we don't have the manual there as PDF. Maybe just an online link to the GnuPG documentation in that case.

I did this locally:

--- a/lang/python/tests/support.py
+++ b/lang/python/tests/support.py
@@ -46,13 +46,15 @@ def is_gpg_version(version):

We now use a temporary .part files when creating the archive. On success, they are renamed. Otherwise, they are removed (if possible).

Done. Will be tested with the parent issue T6584.

Thanks. I'll apply your patch.

Done. The visibility of the advanced options is now remembered. For individual certifications the advanced options are not visible by default, for bulk/group certifications they are visible by default. Therefore, the state is stored separately for both cases.

Yes pretty sure about that, ok we will provide you log, thank you

A quick test shows that the latest patches allow to set and show an expiration date beyond 2038. A new VSD beta will soon be available to customers. And we should also think about getting a gpg4win bug fix release out.

Are you sure this is from a regular Outlook installation and not the common web based outlook? Please enable GpgOL logging and share the log with us. Do not use production keys or messages.

Sorry took a while to download all the debug info. Maybe we have different libical versions and this is a libical issue.

Hi Andre,

For 32 bit WIndows I now hacked some extra code to handle the expiration time if given as ISO string. Although gpg won't display the time correctly on the command line, Kleopatra does this and also allows to set the expiration time.

Or better wait. We can now pass "seconds=2147483648" as expire value but that is added to the creation date which might not want we want. I'll look again into this.

Can be tested with vsd 3.1.90.252

Will be in 2.4.4. GPGME 1.23.0 with support has been released.

I just noticed this because it was accidentally assigned to me and WIP. Since you already mention it in T6325 I would close this as a duplicate of T6325 because at least they can be tested together and testing is the only thing left here that it works with the next 2.2 version.