Tue, Apr 16
Sat, Mar 23
Thanks, that patch works for me.
Mar 18 2024
Mar 7 2024
Mar 6 2024
See also rG40b85d8e8cecadf35e51e84b30de4fac820d714b for gnupg 2.4.
Mar 4 2024
How to test:
Mar 1 2024
In 2.4 we have rG1383aa475 which does
Pushed the change in: rGf50c543326c2: agent: Allow simple KEYINFO command when restricted.
Feb 29 2024
No, thank you both for the speedy responses :)
Thanks a lot for your quick testing.
The commit rGff42ed0d69bb: gpg: Enhance agent_probe_secret_key to return bigger value. of GnuPG 2.2 introduced this bug.
Feb 21 2024
Okay, backported to 2.2.
Feb 16 2024
I was wrong for the semantics of proxy->outtoken. It is zero when run_proxy_connect is called and enabled during the negotiation.
@hlein Thanks a lot for quick testing.
Thank you @gniibe! Applied the rG848546b05ab0: dirmngr: Fix the regression of use of proxy for TLS connection. changes here, and 2.4.4 works here now.
IIUC, the code for keep_alive is for negotiation of proxy. If so, something like this is the fix:
Right. I was wrong assuming the code in 2.2 branch is stable (that is: well tested).
Feb 15 2024
Werner wants the import via gpg-agent
Jan 26 2024
We need to test the PIN, PUK and reset code stuff in 2.2
Is in 2.4.4 and will go into 2.2.43
Jan 24 2024
Tested for 2.4
Fixed in 2.4.4 and 2.2.43 - see above for affected versions.
We need to fix 2.2.42 too. This because we backported the responsible patch.