The patch worked, thank you very much.

Use the source! GnuPG is free software.

Thank you for the log.

Here is the log file requested.

Here is the change remained:

diff --git a/src/fips.c b/src/fips.c
index bcadc5f2..5499aee8 100644
--- a/src/fips.c
+++ b/src/fips.c
@@ -82,6 +82,12 @@ static void fips_new_state (enum module_states new_state);

Before rebasing, I pushed a change to simplify access to no_secure_memory variable by rC209d98dcf66b: Simplify the logic for no_secure_memory..

I tested the change of last_update after importing a same key with different content, but found that there is still no change.

So, please show us gpg-error-config-test.log by your build.

Ok, I have subscribed to the mailing list. I have resent the DCO.

DCO has not appeared on mailing-list. You can this from check list archives, https://lists.gnupg.org/pipermail/gcrypt-devel/2021-December/thread.html

Thanks Jussi, I did not receive the list moderator's email so I am not sure if the it has been posted on gcrypt-devel@gnupg.org. If not, I can resend the DCO. Thanks.

I did some finishing touches on coding style:

On import. Please use gnupg-devel mailing list for further API questions. This is a bug tracker and not a help forum.

Hi Jussi,

Thank you for the answer then! You can probably review our guide then https://github.com/ossf/great-mfa-project/blob/main/guide/token-usage-guide.md :)

A clumsy workaround for the Kleo bug is to put "keyserver ldap:///" into the global gpg.conf after an ignore section containing keyserver. This will let gpgconf emit "ldap:///" unless a local gpg.conf exists.

Nice. The way with KS_GET and assuan is much better then I thought about using a temporary home and a --locate-key

Thanks. If I'm reading correctly, that fix was pushed in July. Any idea when the next release might come out?

Thank you for your report.

Few comments on new patch: