wireguard-openbsd/lib/libcrypto/arc4random, branch master WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/lib/libcrypto/arc4random?h=master 2020-11-11T10:41:24Z Update getentropy on Windows to use Cryptography Next Generation (CNG). 2020-11-11T10:41:24Z bcook bcook@openbsd.org 2020-11-11T10:41:24Z urn:sha1:314a6cc33f2cb54420226ae83922255a7a405beb wincrypt is deprecated and no longer works with newer Windows environments, such as in Windows Store apps. make fixed-sized fixed-value mib[] arrays be const 2020-10-12T22:08:32Z deraadt deraadt@openbsd.org 2020-10-12T22:08:32Z urn:sha1:87afc19ed9256ae3cb7c5266911abf02218c2a35 ok guenther tb millert As done everywhere else, use a local version of MINIMUM() and avoid 2020-05-17T14:44:20Z deraadt deraadt@openbsd.org 2020-05-17T14:44:20Z urn:sha1:557f50bebc1500345a39cc6f8881a4b155a2959b conflict against a potential define min() from some other scope. Using pthread_atfork instead of __register_atfork with uClibc on noMMU 2019-07-11T10:37:28Z inoguchi inoguchi@openbsd.org 2019-07-11T10:37:28Z urn:sha1:d1c464858201e6c951a93a471f75572ea026e2db uClibc on noMMU doesn't provide __register_atfork(). Reported by redbirdtek on Github issue. https://github.com/libressl-portable/portable/issues/538 ok bcook@ Saw a mention somewhere a while back that the gotdata() function in 2018-11-20T08:04:28Z deraadt deraadt@openbsd.org 2018-11-20T08:04:28Z urn:sha1:03b209d2bddddd6fe333a3c8aabf014de1b406ec here could creates non-uniformity since very short fetches of 0 would be excluded. blocks of 0 are just as random as any other data, including blocks of 4 4 4.. This is a misguided attempt to identify errors from the entropy churn/gather code doesn't make sense, errors don't happen. ok bcook ensure SYS_getrandom and GRND_NONBLOCK are both defined before using getrandom(2) 2018-03-13T22:53:28Z bcook bcook@openbsd.org 2018-03-13T22:53:28Z urn:sha1:e698281d1756730aea0e267a621d18672518ab39 Based on discussion here https://github.com/libressl-portable/openbsd/pull/82 Suggested fix from jsing@ Switch Linux getrandom() usage to non-blocking mode, continuing to 2017-04-29T18:43:31Z beck beck@openbsd.org 2017-04-29T18:43:31Z urn:sha1:edb2eeb7da8494998d0073f8aaeb8478cee5e00b use fallback mechanims if unsuccessful. The design of Linux getrandom is broken. It has an uninitialized phase coupled with blocking behaviour, which is unacceptable from within a library at boot time without possible recovery. ok deraadt@ jsing@ add iOS support for getentropy 2016-09-03T15:24:09Z bcook bcook@openbsd.org 2016-09-03T15:24:09Z urn:sha1:c283a6cd12d146ce15a4cddc7934dc9d18b68220 from Jacob Berkman, ok beck@ Update the link for the getentropy(2) manual to man.openbsd.org/ 2016-08-07T03:27:21Z tb tb@openbsd.org 2016-08-07T03:27:21Z urn:sha1:b8461433ba0ae3a060ab82e618da25ae2f3ba5dd ok deraadt@ Tighten behavior of _rs_allocate failure for portable arc4random implementations. 2016-06-30T12:19:51Z bcook bcook@openbsd.org 2016-06-30T12:19:51Z urn:sha1:545f6b86ded87dbc7c6e5c5d540edde0277a0fcf 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@