Fri, Sep 12
fix tested and confirmed with GnuPG 2.5.12 on windows 10
Thu, Sep 4
i've included logfiles for gpg-agent and scdaemon with debug-level 10. the files include
Wed, Sep 3
Tue, Sep 2
We will do a new gpg4win beta soon.
@m.eik Could you please enable debug option for gpg-agent and get the log output for the crash?
Thu, Aug 28
Wed, Aug 27
Jun 18 2025
This was release with 2.5.7.
May 27 2025
Thanks, that was the only issue building there.
Please re-open if you find other Cygwin related build problems.
You know that Cygwin is not supported but if that is the only place it should not arm to fix it.
May 26 2025
May 9 2025
(2) Update the documentation of default-cache-ttl zero value disabling caching.
I am going to do:
(1) Recover old behavior with max-cache-ttl = 0
(2) Update the documentation of default-cache-ttl zero value disabling caching.
May 8 2025
I can't see any documentation that a value of 0 disables the cache. The user might have used some undefined behaviour. For example in the old code we did a housecleaning when we were idle but the new code uses a timer and another thread for flushing the cache. We could open a feature request to entire disable the cache but I bet that we will get a lot of new bug reports because users will then need to enter their passphrase too often for one operation.
It's not my intention. I didn't know the feature of disabling caching by max-cache-ttl to 0.
Well, it's a regression if a user intends so.
May 7 2025
Lucas Mülling commented yesterday on gnupg-devel:
Feb 12 2025
Here we go:
Alright, my above putenv option won't work because it modifies the session environment and thus needs to be run for each gpg-agent session (connection). Adding a putenv_startrup option would help here but this way each connection could chnage the environment - also not good. In the end a way to modify the used environment variables, as you suggested, is a better way.
Feb 11 2025
Yes, the workaround is to use a pinentry wrapper script that sets the value back to the correct one and then invokes the real pinentry.
Feb 10 2025
Jan 23 2025
Jan 8 2025
Got a simple fix for this which does two things:
- Correctly act upon an error from the backup file writing
- Print a warning note.
There is a regression due to the regression fix in rGb30c15bf7c5336c4abb1f9dcd974cd77ba6c61a7 (from Dec 24 2015) or some related commits:
Dec 6 2024
Dec 5 2024
Dec 2 2024
Closed, since this was documentation for the workaround, four years ago.
Just a reminder: with Gnuk 1.2.15 and an ed25519 key PubkeyAuthentication unbound is required for hosts using the new feature.
Nov 29 2024
Fixed in 2.5.0 and 2.4.6.
Fixed in 2.4.6.