The RAND_DRBG (crypto/rand/drbg_lib) APIs are quite some mess and sit badly
with the move to provider based infrastructure.
They are definitely being deprecated in master but without more, the extra
layer of indirection and additional complexity generating random numbers will
remain.
The option
If this is not going to break 99% of users + it improves the interface + the
replacement to achieve the same is a few lines of code and is likely to occur
in one place in an app, then it seems reasonable to change it to me.
> On 27 Jul 2020, at 11:08 am, Dr Paul Dale wrote:
>
> The RAND_DRBG
i.e. Choose option (1)
> On 27 Jul 2020, at 11:14 am, SHANE LONTIS wrote:
>
> If this is not going to break 99% of users + it improves the interface + the
> replacement to achieve the same is a few lines of code and is likely to occur
> in one place in an app, then it seems reasonable to cha
