gcry_create_nonce after a snapshot or checkpoint restore

[NIIBE Yutaka]

Hello,

Please note that adding new control means update of API.  Thus... I
wonder if it's needed or not (hesitate to do that, just only for this
purpose).

Anyhow, attached is a patch to fix GCRYCTL_CLOSE_RANDOM_DEVICE, so that
it surely finalizes the buffer for gcry_create_nonce.

My idea is: let us apply this change of GCRYCTL_CLOSE_RANDOM_DEVICE at
first.  An application should use GCRYCTL_CLOSE_RANDOM_DEVICE when it
needs to reseed the random number generation (for now).  Let us see if
better name of the control will be needed.
-- 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-random-Make-sure-GCRYCTL_CLOSE_RANDOM_DEVICE-finish-.patch
Type: text/x-diff
Size: 3255 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gcrypt-devel/attachments/20261104/02bf7848/attachment.patch>