Required for the GnuPG 2.2.0 release
Mar 15 2018
Oct 22 2017
Sep 1 2017
Aug 23 2017
ENABLE_NLS is not defined as it should be but we still have to define L_ in that case if simple_gettext is used to have some gettext. This was fixed by 6158811304937b592601ef30c29c5a5cdbaa88ea
Aug 7 2017
Aug 4 2017
auto-key-locate now defaults to "local,wkd" and --auto-key-retrieve is also the default.
Aug 3 2017
Yes, any auto-key-locate entry should disable the defaults.
Aug 2 2017
IMO for now we should not add DANE as this has been published for a while and we don't see widespread adoption. To avoid additional delays I would keep it disabled by default for now. But you know the pros / cons there better then me.
So your suggestion is that
auto-key-retrieve auto-key-locate local auto-key-locate wkd auto-key-locate dane
shall be the new default unless --disable-dirmngr is also used?
Jul 31 2017
A new installer is now available:
Patched installer is better. This is also a good test on whether the build works with custom patches.
Or you publish some gnupg-2.1.23-beta3 or so. Would also be ok imo.
I'd say a patched installer with a different date. This is how I would have handled this in the Gpg4win 2.x times.
How, shall we build just a new patched installer or do a full new release?
That was an easy one.
Workaround is to add
Uhm. I can't reproduce this with a dirmngr built on my development system.
Jul 28 2017
That real bug is not a bug but a wrong error message. Due to the use of OCB we catch passphrase by means of that AEAD mode and not by looking at the cleartext. That resulted in a wrong error message. Fixed to return Bad Passphrase instead.
Segv/ref-count error found. Now for the real bug ...
I tried to reproduce this through various scripts in variations of
but failed. So maybe interactive usage plays a role here or it was fixed.
Jul 27 2017
From this I take it that the checksum error comes from gcrypt but is wrongly propagated as Pinentry error.
With the vsnfdhome attached to this report:
I don't understand the GPG_ERR_CHECKSUM coming according to Justus' log from Pinentry. A likeley reason for that error is an OCB decrypt failure in Libgcrypt (e.g. extended protected key format) - but from Pinentry?
Maybe related: T3187
I'm in a checksum error scenario again.
Jul 11 2017
This is very odd indeed. Here is my guru log, it is the same as yours, but except of dying of the assertion, it just continues:
Jul 10 2017
Yes, signing failed: Bad Passphrase but that may be later.
I only get checksum errors: