boringssl/crypto/rand
David Benjamin 81091d55e1 Don't use uninitialized memory in RAND_bytes.
We can't actually catch this with MSan because it requires all code be
instrumented, so it needs a NO_ASM build which no disables that code. valgrind
doesn't notice either, possibly because there's some computation being done on
it. Still, we shouldn't use uninitialized memory.

Also get us closer to being instrumentable by MSan, but the runner tests will
need to build against an instrumented STL and I haven't tried that yet.

Change-Id: I2d65697a3269b5b022899f361730a85c51ecaa12
Reviewed-on: https://boringssl-review.googlesource.com/4760
Reviewed-by: Adam Langley <agl@google.com>
2015-05-15 20:31:27 +00:00
..
asm rand: new-style locking and support rdrand. 2015-04-14 20:13:42 +00:00
CMakeLists.txt rand: new-style locking and support rdrand. 2015-04-14 20:13:42 +00:00
hwrand.c Fix OPENSSL_NO_ASM build and promote to a cmake build flag. 2015-05-05 00:20:35 +00:00
internal.h rand: new-style locking and support rdrand. 2015-04-14 20:13:42 +00:00
rand.c Don't use uninitialized memory in RAND_bytes. 2015-05-15 20:31:27 +00:00
urandom.c rand: new-style locking and support rdrand. 2015-04-14 20:13:42 +00:00
windows.c rand: new-style locking and support rdrand. 2015-04-14 20:13:42 +00:00