Workaround is to add

On Sat, 29 Jul 2017 15:12, noreply@dev.gnupg.org said:

Please provide information on how you build this. That is invocation of configure and make and best attsch the created config.log.

Sure it won't apply because it is part of 2.1.22. ;-)

Your build system is not correctly set up. How did did you invoke configure?

2.1.22 released - the plan for 2.2 is end of August. But it is just a plan.

All fixed. (famous last words)

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 ...

Hmmm.

I am pretty sure that was also fixed by rGa0d0cbee7654 for T3308

Okay, decryption now gives only a warning.

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?

This is a question on how to install and use gpgme. Please direct this to the gnupg-devel mailing list.

I'd suggest that you install the missing nPth library. The configure message is pretty clear about it.
The warnings are irrelevant.

That is due to your fix for T2236 where you reused the code from keyedit which was intended to work only on the console.

Well, iff we implement that for gpg we also need to implement it for gpgsm.

We can't do anything about thisfor the oldversions. You may use libgcrypt 1.8.0 which has a faster entropy collector and also allows to map /dev/random to /dev/urandom using the new /etc/gcrypt/random.conf

.

FWIW, using a Debian specific thing is not portable and Unix sockets won't work on Windows. Thus using the standard localhost connection is simpler than adding extra complexity.

Okay, I implemented the second part and Tor is now used if availabale.
--no-use-tor disables Tor.
--use-tor forces use Tor and can't be reset.

This is a rendered version of the ID as of commit 584fd6c795530b9d3b290781ef09fd58a2fe0cf3 of the rfc4880bis repo.

So this is basically 0what GNOME does with its keyring daemon and pinentry-gnome.

I don't understand what you mean by unlocking gpg-agent. Can you please explain in detail what you try to achieve.

I think disabling the tooltips for the gtk Pinentry is the way to go.

We now strip trailing slashes (and backslashes on Windows) when setting the home directory with --homedir and when retrieving it from GNUPGHOME.

I would say this is okay now. We switch to the Windows system directory which is unlikely to have non-ascii characters. If we ever need to change this, this can now be done in gnupg-chdir and the new gnupg_daemon_rootdir functions.

rG166d0d7a2439f30c0a250faadc16ce3453447d71 is a first take on this. It is not complete but should be sufficient for now.

This needs to be changed. See the comments for the commit.

Thinking again about this: The easiest way is to move the existing chdir ("/") out of the ifndef W32 block. That is moving just the #endif.

I doubt that this is a full solution to the described problem because under Windows "/" is not the root of all files.

This is a support question - please ask on a gnupg mailing list or ask your Solaris vendor on how to properly install gcc.

The warning is just a warning, so no problem. The pragma even indicates the compiler for which it is intended.