openbsd/src/lib/libcrypto/arc4random, branch libressl-v2.1.2

correct the failure case for getentropy on win32

2014-11-11T13:54:33+00:00

CryptAcquireContext and CryptGenRandom returns zero (FALSE) if fails. From: Dongsheng Song

Add hooks to override native arc4random_buf on FreeBSD.

2014-11-03T06:23:30+00:00

The FreeBSD-native arc4random_buf implementation falls back to weak sources of entropy if the sysctl fails. Remove these dangerous fallbacks by overriding locally. Unfortunately, pthread_atfork() is also broken on FreeBSD (at least 9 and 10) if a program does not link to -lthr. Callbacks registered with pthread_atfork() simply fail silently. So, it is not always possible to detect a PID wraparound. I wish we could do better. This improves arc4random_buf's safety compared to the native FreeBSD implementation. Tested on FreeBSD 9 and 10.

include header needed by older linux kernels

2014-10-11T16:44:05+00:00

not all versions of include by default

preserve errno value on success.

2014-08-28T01:00:57+00:00

If getrandom returns a temporary failure, make sure errno is not polluted when it succeeds. Thanks to deraadt@ for pointing it out.

only build the getrandom path if SYS_getrandom is defined.

2014-08-16T18:42:41+00:00

like the sysctl path

getrandom(2) support for getentropy_linux

2014-08-16T17:21:56+00:00

This enables support for the new getrandom(2) syscall in Linux 3.17. If the call exists and fails, return a failure in getentropy(2) emulation as well. This adds a EINTR check in case the urandom pool is not initialized. Tested on Fedora Rawhide with 3.17rc0 and Ubuntu 14.04 ok deraadt@

munmap correct object in (extremely unlikely, and effectively terminal)

2014-08-13T06:04:10+00:00

case of failing to map the 2nd object. found by Paul Maurers

better match proposed syscall api

2014-07-22T01:15:58+00:00

protect sysctl path with SYS__sysctl instead; from enh@google, ok bcook

2014-07-21T23:34:54+00:00

Use explicit_bzero() instead of memset() on buffers going out of scope.

2014-07-21T20:19:47+00:00

Also, zero the SHA256 context. suggested by "eric" in a comment on an opensslrampage.org post ok miod@ deraadt@