ockam
ockam copied to clipboard
Implement CryptoRng trait for ockam_vault
We need secure crypto rng in multiple places both inside and outside of vault. thread_rng() is one of potential implementations of CryptoRng, which is not what we always want (especially in no-std environments). Probably, better approach is to let Vault implementation to provide us with CryptoRng impl. Many places that need rng already have access to Vault, so it will be easy to replace thread_rng() usage there, in some places it can be tricky. The actual switching issue is described here #1846. But this should be done first