From f20179d6931df17c9310fd911dd4a348141ba72c Mon Sep 17 00:00:00 2001 From: Waldemar Brodkorb Date: Tue, 30 Jan 2018 04:01:56 +0000 Subject: remove arc4random (rc4 based) OpenBSD arc4random is using chacha20 cipher algorithm for a long time. This copy is still based on deprecated rc4 cipher algorithm. We could either update the arc4random.c or drop it. Drop it. Users should better use libbsd when using arc4random interface. Musl/glibc does not have arc4random either. --- extra/Configs/Config.in | 22 ---------------------- 1 file changed, 22 deletions(-) (limited to 'extra/Configs') diff --git a/extra/Configs/Config.in b/extra/Configs/Config.in index bf2defbae..deb165a8e 100644 --- a/extra/Configs/Config.in +++ b/extra/Configs/Config.in @@ -2012,28 +2012,6 @@ config UCLIBC_BUILD_PIE assembler functions must be written as position independent code (PIC). -config UCLIBC_HAS_ARC4RANDOM - bool "Include the arc4random() function" - help - Answer Y to support the OpenBSD-like arc4random() function. This - function picks a random number between 0 and N, and will always return - something even if the random driver is dead. If urandom fails then - gettimeofday(2) will be used as the random seed. This function is - designed to be more dependable than invoking /dev/urandom directly. - OpenSSL and OpenNTPD currently support this function. - - Most people will answer N. - -config ARC4RANDOM_USES_NODEV - bool "Do not use /dev/urandom with arc4random()" - depends on UCLIBC_HAS_ARC4RANDOM - help - Answer Y to use gettimeofday(2) and getpid(2) exclusively for - arc4random(). This is not a bad idea for a diskless system, but - it uses a lot of syscalls to stir each array element. - - Most people will answer N. - config HAVE_NO_SSP bool -- cgit v1.2.3