- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Tue, Dec 10
I don't really understand the problem. After all gpg-agent seems to be started using gpgconf --launch gpg-agent which should handle the locking properly.
In T7262#195642, @ametzler1 wrote:I read this as bumping the version-number e.g. from 1.24.5 to 2.0.0 without e.g. bumping the soname or changing the api_version as specified in the .pc file. (FWIW I think that is a great plan.)
Mon, Dec 9
Dec 8 2024
Dec 6 2024
Dec 5 2024
@ilf: Yes these message are emitted using log_info in 2.4.7 and 2.5.2. Thus they don't case a failure exit. I will silence them with --quiet in 2.5.3.
A workaround exists with the new option --ignore-crl-extensions.
Dec 4 2024
Works for me in an NSIS installer. The VSD beta thing also works with copied conf files.
(gpg4win-5.0.0-beta27 with some local mods)
Kleo needs this only because it wants to directly talk to gpg-agent via Assuan. For example to get smartcard infos. What about delaying this part until you have received some data back from gpg or gpgsm? This makes sure that the agent has been started.
Dec 3 2024
Let me guess: Kleopatra starts the agent using gpgconf --launch gpg-agent which in turn uses gpg-connect-agent to actually start the agent if needed. Kleopatra does not seem to wait for the launch to succeed and fires up gpg and gpgsm. They both wait for the gpg-agent to be started and both use the same locking strategy. However, this involves a pseudo random wait which should avoid deadlocks. See gnupg/common/dotlock.c:next_wait_interval
Dec 2 2024
Just a reminder: with Gnuk 1.2.15 and an ed25519 key PubkeyAuthentication unbound is required for hosts using the new feature.
Then please upload whatever README you want there. My release checklist does not mention any README.
Nov 28 2024
Nov 27 2024
Nov 26 2024
Nov 25 2024
I cherry picked your patch for master and 2.4.
Nov 22 2024
For master fixed with rGbb6b38c24010258c7cb2da840d0a088fe43393b3 (Wrong bug id used).
Also fixed for gnupg24.
Nov 21 2024
We may do this for gpg4win-5 but not for the current versions.
[GNUPG:] BEGIN_DECRYPTION [GNUPG:] DECRYPTION_INFO 0 9 0 [GNUPG:] PLAINTEXT 62 1732178872 [GNUPG:] PLAINTEXT_LENGTH 72 You will be advanced socially, without any special effort on your part. [GNUPG:] DECRYPTION_OKAY
You are right. Printing the algo was missing in gnupg22.
Nov 20 2024
Please do not add milestone tags.
Nov 19 2024
2.2. reaches EOL in 6 weeks and thus we won't look at a potential problem with no real world impact.