On 12/18/2014 12:14 AM, Theo de Raadt wrote:
getentropy*.c: cannot call abort() because some systems have unsafe
corefiles
arc4random.c: if(_rs_allocate(...) == -1) abort();
Am I missing any difference between the two cases?
(brain,cvsweb,google+gmane weren't any help)
Policy.
; Linux x86_64; rv:31.0) Gecko/20100101
Icedove/31.3.0
MIME-Version: 1.0
To: Theo de Raadt dera...@cvs.openbsd.org
CC: tech@openbsd.org
Subject: Re: [nitpicking] abort in arc4random?
References: 201412181729.sbihtcva034...@mx-2.infinito.ipnext.it
In-Reply-To: 201412181729.sbihtcva034...@mx-2
The comment says, AS A WHOLE:
/*
* Entropy collection via /dev/urandom and sysctl have failed.
*
* No other API exists for collecting entropy. See the large
* comment block above.
*
* We have very few options:
*
The comment says, AS A WHOLE:
/*
* Entropy collection via /dev/urandom and sysctl have failed.
*
* No other API exists for collecting entropy. See the large
* comment block above.
*
* We have very few options:
getentropy*.c: cannot call abort() because some systems have unsafe
corefiles
arc4random.c: if(_rs_allocate(...) == -1) abort();
Am I missing any difference between the two cases?
(brain,cvsweb,google+gmane weren't any help)
getentropy*.c: cannot call abort() because some systems have unsafe
corefiles
arc4random.c: if(_rs_allocate(...) == -1) abort();
Am I missing any difference between the two cases?
(brain,cvsweb,google+gmane weren't any help)
Policy.
getentropy() should eventually be a lower level
