On November 16, 2021 8:03 PM, brian m. carlson wrote:

On 2021-11-16 at 23:20:45, rsbecker@nexbridge.com wrote:

quoted

We do link with libcurl and use OpenSSL as a DLL to handle TLS. The
underlying random source for the nonstop-* configurations as of
OpenSSL 3.0 are PNRG supplied by the vendor (HPE) on ia64 and the
hardware rdrand* instructions on x86. I know that part of the OpenSSL
code rather intimately.

Great, as long as you don't define NO_OPENSSL, I think I can make this work
with OpenSSL by calling RAND_bytes, which will use whatever OpenSSL uses.
I'll work on that for a v2 to see if that will meet the needs for your platform,
and if not, I'll try something else.

That should also have the pleasant side effect of making this more portable
even for those people who do have less common platforms, since OpenSSL
will likely be an option there.

I checked config.mak.uname. We should be fine with that qualification.

Regards,
Randall