Ah okay, that was Windows were we have a couple of warnings anyway. Must have missed that one.

Aiiih, what happend to the sentinel attribute? I need to check.

Original issue (of pinentry-curses, which should be killed by CTRL-C) is related to T2011: gnupg should notify cancellation of its operation to gpg-agent to kill pinentry, I suppose. It is fixed in master and testing.
I don't know about the second one with pinentry-tty.

Fixed in master.

Gnuk implements the feature, and newer GnuPG shows a dialog to request pushing the ack button.

Your problem is apparently not an issue of upstream development of GnuPG; It is your setup script (agent.sh?) which specifies /dev/shm/SOMETHING.
Standard GnuPG never does that. We have no idea about use of /dev/shm/SOMETHING.

No. Pinentry is always 32 bits for us.

Could it be possible that it's a 32/64 bit issue?

Is this with the /MINIMAL flag?

Some of my terminology: I call "case", "shell", and "board".

Strange, even if they are missing in the Gpg4win insttall dir they should be picked up from GnuPG which is added to PATH.

Libdns is not our own code and our intention was to keep it in sync with upstream. However, after some initial success the upstream author lost interest. We now consider to rework the code to remove a bit of the more creative use of C99 and maybe even get rid of some of the used C99 features (gnupg is mainly C90 with some exceptions).

I don't think code page is the problem per se though.

0.10.0

Which version of gpa is that?

Please try "gpg --quick-gen-key" which takes the user-id on the command line - that uses a different code path.

Thanks for that summary.

Final fix was rG380bce13d94f: agent: Use clock or clock_gettime for calibration., with clock.
Closing this patch.

Since it seems there is a renewed interest in adding ECC support to GpgSM (as indicated by the T4098 feature request), I would like to write down here more details about this task.

The metal case, I bought from here (it's expensive CNY3.00, for individuals): https://item.taobao.com/item.htm?id=550180089286

For prototype, I used:

• ZL-272 (without slits): https://detail.1688.com/offer/566273410945.html
• ZL-271, the metal shell: https://detail.1688.com/offer/566197153418.html

• Repository for PCB design: https://git.gniibe.org/cgit/gnuk/fst-01.git/
  • tag: release/3.01 is the latest for the design itself, but last commit 8ee4e0d53a73993e42d1c2ccc12b08757338f4b1 added data sheet for connector.
    • • The particular data sheet is for a variant of connector with slits.
    • in the output directory, I put additional information as well as the gerber output: https://git.gniibe.org/cgit/gnuk/fst-01.git/tree/output?id=8ee4e0d53a73993e42d1c2ccc12b08757338f4b1
    • In output/README.txt, there are information for procurement for the GD32F103 chip and ZL-272 connector.
    • But those are the ones I specified, and the actual vendors/distributors are different
    • For ZL-272 with slits, it seems that it's DongGuan Yuliang Electronics Co., Limited (http://www.dgyuliang.net) which provides the connector
• The test plan I specified is: https://www.gniibe.org/memo/development/fst-01/fst-01sz-testplan.html

Pinentry already has a ttyalert option which may be set to beep or flash to ring the bell or flash the terminal, respectively (see commit 1dba96fafa123f3631c0a50bb01835306c23b903).

Released 2.5.3 today: