You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think there is still a use where you want to initialize the RNG so that it produces a predictable output. Typically, before the API change, it was possible to initialize the RNG with Fortuna and a seed. I think that this type of usage is still valid and that the deprecation on Mirage_crypto_unix.initialize should be removed. WDYT?
The text was updated successfully, but these errors were encountered:
I'm not sure I understand the demand for a "predictable RNG", but you can always:
let()=let g =Mirage_crypto_rng.create ~seed:"private" (moduleMirage_crypto_rng.Fortuna) inMirage_crypto_rng.set_default_generator g
Now, with Mirage_crypto_rng_unix.initialize -- there was no predictability given, since that used CPU instructions & whirwhind & getrandom for an initial seed.
Be aware that the set_default_generator is a global mutable cell, thus any other library may set it. To really ensure using the predictable RNG you want to have, pass the g explicit to generate.
I think there is still a use where you want to initialize the RNG so that it produces a predictable output. Typically, before the API change, it was possible to initialize the RNG with
Fortuna
and a seed. I think that this type of usage is still valid and that the deprecation onMirage_crypto_unix.initialize
should be removed. WDYT?The text was updated successfully, but these errors were encountered: