3 ms·
> BoringSSL just uses /dev/urandom directly. Only if there's no hardware RNG support which I admit can happen (it's not perfect, I freely admit that). I suspe
by ryuuchin 10y ago
> BoringSSL just uses /dev/urandom directly.
Only if there's no hardware RNG support which I admit can happen (it's not perfect, I freely admit that). I suspect that for Google's use on their servers it's a non-issue (assuming where they use it and need the high(er) speed stuff they'll always have rdrand support). If there is rdrand support then it will only reseed from /dev/urandom after every 1MB (or 1024 calls) of generated random data (per thread).