wireguard-openbsd/lib/libcrypto/arc4random/arc4random_linux.h, branch jd/queueboosts

Using pthread_atfork instead of __register_atfork with uClibc on noMMU

2019-07-11T10:37:28Z

uClibc on noMMU doesn't provide __register_atfork(). Reported by redbirdtek on Github issue. https://github.com/libressl-portable/portable/issues/538 ok bcook@

Tighten behavior of _rs_allocate failure for portable arc4random implementations.

2016-06-30T12:19:51Z

In the event of a failure in _rs_allocate for rsx, we still have a reference to freed memory for rs on return. Not a huge deal since we subsequently abort in _rs_init, but it looks strange on its own. ok deraadt@

Calling clone(2) with CLONE_NEWPID yields multiple processes with pid=1.

2016-01-04T02:04:56Z

Work around this particular case by reseeding whenever pid=1, but as guenther@ notes, directly calling clone(2), and then forking to match another pid, provides other ways to bypass new process detection on Linux. Hopefully at some point Linux implements something like MAP_INHERIT_ZERO, and does not invent a corresponding mechanism to subvert it. Noted by Sebastian Krahmer and the opmsg team. See http://stealth.openwall.net/crypto/randup.c for a test program. ok beck@

back in september I did the large abstraction refactoring to allow these

2015-01-15T06:57:18Z

other systems to fit into the same mold, so add copyright

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

2014-08-13T06:04:10Z

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

Move more OS-specific functionality to arc4random.h headers.

2014-07-20T20:51:13Z

Move and raise(SIGKILL) calls to OS-specific headers. On OpenBSD, move thread_private.h as well to arc4random.h. On Windows, use TerminateProcess on getentropy failure. ok deraadt@

Move _ARC4_ATFORK handlers from thread_private.h in portable.

2014-07-19T15:29:25Z

move _ARC4_LOCK/UNLOCK primitives from thread_private into OS-specific modules

2014-07-19T14:34:38Z

fixup typos

2014-07-19T13:02:28Z

Change _rs_allocate so it can combine the two regions (rs and rsx)

2014-07-19T00:08:41Z

into one if a system has an awesome getentropy(). In that case it is valid to totally throw away the rsx state in the child. If the getentropy() is not very good and has a lazy reseed operation, this combining is a bad idea, and the reseed should probably continue to use the "something old, something new" mix. _rs_allocate() can accomodate either method, but not on the fly. ok matthew