Thanks.

Thanks. May also happen if the first print_assuan_status fails.

In T4225#119482, @aheinecke wrote:

Can you give me the exact steps what you are doing?
"Generation of an OTP" is strange to me. I have an FST-1 hardware token that runs the same software as a yubikey (GNUK) but I'm not so well versed in all the windows use cases. But I am interested to fix them.

I've closed this as a dup because the pinentry-qt is the default one on Windows and T4123 describes your problem.

Is it possible that you have used a different pinentry in the past? Like the GTK one?

Can you give me the exact steps what you are doing?
"Generation of an OTP" is strange to me. I have an FST-1 hardware token that runs the same software as a yubikey (GNUK) but I'm not so well versed in all the windows use cases. But I am interested to fix them.

Fixed in 1.8

Fixed in 1.8

yat2m updated. Thanks.

Thanks.

Thanks again.

Added a missing free in case of read error.

If I understand the code correctly the mapping is done to let the system optimize the memory management so that the full contents of the file are not kept in memory, or is there a different reason?

Thanks. Not a real world problem now but needs to be fixed.

Thanks. There is an easier solution for this, though: I now trim trailing LFs.

Maybe related, flush also does not work on Windows:

May I suggest to use a (new) gpgrt-config instead of the current name libgpg-error-config. The long term plan is to change the name of the library.

For what it's worth I found some more places where data leaked out even in log level 1. It will probably be a bit of a process to get this clean to a 100% as there is no automated way to decide what needs to be filtered and what not.