RAND_add() forces a reseed to the DRBGs and uses the passed material
(not as entropy but as additional input).
EVP_RAND_reseed() is a more direct interface but remember that the built
in DRBGs are free to ignore what the user claims is /entropy/. History
has shown us time and again that
Hi All,
In OpenSSL 1.1.1 version, we were using RAND_DRBG for random number generation.
Using "RAND_DRBG_set_callbacks", we were able to call into our custom API for
entropy and nonce generation.
How can this be achieved with EVP_RAND implementation i.e. does it allow
entropy to be provided?
On 3/23/21 11:06 PM, Matt Caswell wrote:
On 23/03/2021 15:47, Embedded Devel wrote:
Do you know if your application is statically linked or dynamically
linked to OpenSSL?
Ive attached the code in question if it helps
original code was deprecated, and changed from
/* if
On Wed, Mar 24, 2021, 10:54 PM Embedded Devel wrote:
>
> On 3/23/21 11:06 PM, Matt Caswell wrote:
> >
> >
> > On 23/03/2021 15:47, Embedded Devel wrote:
> >>> Do you know if your application is statically linked or dynamically
> >>> linked to OpenSSL?
> >> Ive attached the code in question if it
On 3/24/21 9:53 PM, Embedded Devel wrote:
On 3/23/21 11:06 PM, Matt Caswell wrote:
On 23/03/2021 15:47, Embedded Devel wrote:
Do you know if your application is statically linked or dynamically
linked to OpenSSL?
Ive attached the code in question if it helps
and nope still have the
I tried to get through this on my own, not being a openssl developer,
made progress but still no joy
so we had an app that was written some 8-10 years ago, which worked fine
for client/server tls
update to today, no longer functional, deprecations in openssl cause errors
it is not a large
