No, too much release work. Better just one AppImage. Or well one VSD (based on 2.2) and one regular (based on 2.3)

I do not think that we should put any more support for FDs into gpgrt. The goal is to move entirely to the Win32 API.

Your item "2. Allow exporting multiple groups at the same time." is not really important. If you want to do that, please make sure that each group is exported to a separate file.

Please see T5696.

No autoreconf etc. Use only our method to cross build. That is $src/libgcrypt/autogen.sh --build-w32.

Here are the two test certificates mentioned in the commit log:

We could use a new mode #define GCRY_GET_CONFIG_FIPS 1 with gcry_get_config:

What is your Pinentry version, which OS is that, and which terminal type?

Can you given a example on how this would look like. In particulr are placeholders some kind of forced template or just a grey background text?

No, our admin left us and took all scripts and docs with him. We need to set it up again. You better use this system anyway, patches etc on GitHib are not used.

GnuPG requires a Unix system to build. We do not support building natively on Windows. Sorry.

Okay, I revisited the code:

Do not user Reiner SCT those readers are all buggy and work only on Windows - if at all. Stay away from them and get a real reader and not the incompatible broken stuff from that company. I spent way too much time trying to get those readers working. That time is better invested in support for hardware which is standard compatible or are helpful to get stuff running.

The internal hashing of ed25519 is not used by OpenPGP but instead we pass the hash of the message to the ed25519 function and thus to the card. Pushing a message through a card is a no-go - way too slow for any normal sized message.

That does not seem to be right. You don't need 255 bytes for an ECC key. It would be best to get scdaemon logs simialr to the gpg-agent logs. Set "debug ipc,cardio" into scdaemon.conf.

What is the rational for this change?

Yes, keep the internal SHA-3.

Blowfish is not part of OpenPGP and according to its creator not the best cipher. Sorry to say no. You may nevertheless be interested in the recent discussion threads on PQC on the cryptography ML.

Closing. In case the audit will request more, we can re-open this task.

I think we can close this. In January we will have an external audit (BITV) which hopefully will confirm our tests. They auditor will also provide a list of things to improve (if any).