Well... I'm just trying, for the test, to do something like:
debian:~/openssl# strace -xe trace=file,read,write,close
/usr/local/ssl/bin/openssl rand 10
[...]
open(/dev/urandom, O_RDONLY|O_NOCTTY|O_NONBLOCK) = 3
read(3,
You don't even need to modify e_os.h. You can just pass in a new value
for DEVRANDOM using the gcc -D compiler option. For instance, maybe you
have a hardware device mapped to a Linux device file called
/dev/entropy1. You can override DEVRANDOM to use this device without
modifying any OpenSSL
On Mar 11, 2015, at 11:40 AM, Alberto Roman Linacero aro...@alienvault.com
wrote:
Dear all, I'm doing an strace to the FIPS validated version of
openssl, and I'm seeing that is uses /dev/urandom. I thought that the
FIPS validated module always use /dev/random, isn't this the case, or
am
