Thanks people, thanks aheinecke, for your support.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 27 2019
3.1.6 is released.
3.1.6 is released. Please test again and reopen this issue if you still have problems.
Thanks!
3.1.6 is released
3.1.6 is released.
3.1.6 is released.
3.1.6 is released.
3.1.6 is released.
gpg4win 3.1.6 is released which contains this fix.
3.1.6 is released please use that one.
3.1.6 is released
Sorry, this did not make it into 3.1.6. But I'll definitely see about it for the next release. If it is an institutional / corporate issue you could also contract us through www.gnupg.com
Strangely, if I look at my upgrade history, it cannot be caused by gnupg or libusb update. Everything was working fine in February 2019.
BTW in 2.2.15 you can also do
I forgot: Instead of importing the missing internal CA, this works:
I agree, the question is which CRL is checked when how. Maybe there is some mistake on my side. Here is a recipe for Debian:
I don't think this is a bug. Failure to encrypt when CRL check fails is expected.
Mar 26 2019
In T4427#123774, @werner wrote:Can you please run
gpg --debug ipc -vKwhich will also start gpg-agent and print some diagnostics. You may want to redact the output. You can also run
Actually you should never use --debug-all; we have more specific log levels. Use --debug help to see them.
From: aheinecke (Andre Heinecke)
Sent: Montag, 28. Januar 2019 19:25
fwiw. Your patch is beautiful in which it follows our coding style and
debug output. I'm confident that we will accept it but currently I have
to read up on Job's a bit.
Is there a way I could help you with this? This issue is hampering adoption
of GnuPG 2 here.
--
Jan Echternach
News for 1.13.0:
- Support GPGME_AUDITLOG_DIAG for gpgsm. [T4426]
I changed it. My rationale to check for <=0 here was to catch "-1" invalid handle values that might be somehow created / passed and not caught earlier.
Many thanks for the fast fix! Decryption works now. I'll report another bug for encryption.
Trying to install the update manually (according to windows update my windows is fully updated) it says "This update is not meant for your computer" and aborts.