I have now disabled the rewriting in the 2.4 branch. Those who want to keep the old behaviour may add

could not trigger it with the described steps on windows

works for 4,1 GB, too.
(Tested with Gpg4win-4.2.0-beta346)

Move back to the backlog and trigger re-evalutation of priority (which was high).

And of course we also need to adjust GPGME

We also need PROGRESS lines in gpgsm.

I agree that the "future" won't come, ever. (for libgcrypt)

works

works

It does not work as described for subkeys with later expiry dates if the primary key has already expired:

I doubt that we will ever be able to use the flexible array thingy. The old pattern has been used for nearly 50 years and replacing it will just introduce bugs.
Do you use offsetof for that reason?

I found that for EdDSA other than pure Ed25519, it can supply context.
I changed the semantics and API for adding context and input data, as we need to support both simultaneously.

I changed the lg-input-data.diff patch not to break the ABI, reusing the published symbol of gcry_pk_random_override_new.
With this approach, if/when needed, backporting may be easier.
Drawback is debugging internal of libgcrypt will be a bit confusing.

Thanks, we will take care of this.

Let's fix this in Libgcrypt (ignore setting of the handler)

This is related to T6511

Another approach would be having "non-hash" algo for gcry_md_open.

Before adding FIPS support flag and tests, we need to modify implementation:

• Adding PCT check for EdDSA
• Adding support of gcry_pk_hash_sign/verify API for EdDSA

Thanks. I think that it was the oldest one: FSF used to be there in Cambridge, then moved to Tremont St. in Boston, and now it's in Franklin St.