I have updated D297: 785_sign-fix.patch patch to minimize the impact only to secret key lookup.

Here is finish_lookup with want_secret flag.

This has larger impact for key lookup.

While trying to identify the cause of this problem, I found that the import doesn't success with expired key.

My change only addressed the use case with smartcard. So, I removed [TESTING] tag.

Now, 2.1.22 or later supports automatic selection of secret key by available key on card.
Closing.

[Shameless self-kudos]

That was fast ;-) But a bit of luck too since I sually don't show up at the tty late in the evening.

But not for 2.2

This is more or less what gpgme does/sees when loopback mode is enabled / disabled:

My pleasure.

OK, I changed my own purpose. I don't touch internal representations.

Thanks.

ntbtls 0.1.2 has been released as well gnupg 2.2.1 with other fixes and the Windows installer using that new ntbtls.

IIRC, the actual reason for introducing GPG_TTY was a problem with GTK which required a tty for whatever reasons. The original user for the curses pinentry was Mutt and that didn't require that envvar. A much, much better solution would be a fixed ctermid(3) to return the real controlling tty and not the virtual tty /dev/tty. Unfortunately other libc implementations behave the same (I just checked OpenBSD).

I added the missing curves to ntbtls and will soon do a new release. To please some folks here I also added the Brainpool curves ;-)

You can't access that server even from Windows7 due to an uncommon ECC curve. I need to investigate but it is likely that ntbtls does not yet support it.

Looks resolved in beta 307. Signing and exporting to public is now so fast even the first time around that I can't reproduce this condition.

Resolved for me with beta 307. Kleopatra gets launched, starts a few GPG services, then the message gets signed. It takes 20-30 seconds, but that's expected. It's much faster after the first time.

False alarm, this should be closed. It was caused by enabling SMIME support in GPGOL while the sender only had an OpenPGP cert, no SMIME cert. Hence Kleopatra threw a message that it could not unambiguously determine the right cert, then offers only one cert (OpenPGP) for user.

Tested Beta 305 which was more or less fine, today installed Beta 307 and have problems again. The problems today are so far only Oulook hangs, which resolve after around 15-30 seconds. Sadly once it started with the first hangs, it hangs a minute (or so) later again and I can barely change the mail. Those are all plain mails, without any encryption/signature.

Any update on this? Ready to do a pinentry release?

Updated translation el.po file from latest commit in gnupg repo.

This error appears in versions 2.1.15 to 2.2.0 on all platforms.