Sep 26 2023
Lot's of changes since 2.4.
May 11 2023
Feb 27 2023
The code has meanwhile been reworked and the mentioned test server is not anymore available
Jun 9 2022
Added --enable-maintainer-mode to ./configure
Apr 28 2022
Please try a decent version of Gpg4win - we have fixed dozens of bugs in the mean time If the problems persists, please re-open this bug.
Sep 21 2021
GnuPG 2.0 reached end-of-life nearly 4 years ago. See https://gnupg.org/download/index.html#end-of-life . Same for Gpg4win. They are not maintained and its use is very risky due to unfixed bugs. Please update to a recent version.
Jan 5 2021
Please try using the current version (3.1.14) and if the problem persists re-open this bug. In this case we will also need a more detailed report.
Aug 9 2020
No more info was provided.
Jul 16 2020
No info received in3 years.
Oct 15 2018
The current version is 0.9.10 and the reported 0.9.5 is 4 years old. We also received no more info.
Jul 1 2017
That's fine. The 2.0 branch will reach EOL in 6 months and we will
probably only do a last maintenance release. No need to backport this
Jun 30 2017
Btw, if you want to use the test script, you have to use "gpg2 --keyid-format short".
I have verified that it works fine in 2.1.21. I did not test 2.0.30, but that's very old, just use the latest 2.1.x version. gpg 1.4 also only receives critical fixes.
Jun 23 2017
Jun 22 2017
I don't know if this ever landed. If not, please reopen. We now have a bug tracker that can do nice patch management, too :)
May 23 2017
We can close this. The current Master of GpgOL states that Outlook 2003 and 2007 Support is no longer maintained and we will remove support for this altogether in new versions. With current Master this issue also no longer occurs.
Mar 30 2017
Feb 3 2017
Jan 6 2017
Jul 14 2016
I see. We use system() in the random test to re-execute itself. This involves
the shell and thus the problem. Need to uses fork/exec or CreateProcess calls
for that test. I guess this needs to wait until we have moved that to code to
libgpg-error as our portability layer.
This is still a problem on OS X 10.11.5. OS X's System Integrity Protection
"feature" is causing that test failure. If S.I.P is disabled there's no problem.
A similar-looking test failure happens in perl
(https://rt.perl.org/Public/Bug/Display.html?id=126706). Perhaps the diagnosis is
the same here.
Mar 29 2016
Mar 17 2016
Jan 26 2016
Jan 22 2016
Jan 15 2016
Feel free to -re-opne if you experience the same problem with a current gnupg