Bug 50 - Couldn't open random pool "yes": No such file or directory
Summary: Couldn't open random pool "yes": No such file or directory
Status: CLOSED FIXED
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: Build system (show other bugs)
Version: -current
Hardware: All All
: P2 minor
Assignee: OpenSSH Bugzilla mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-19 03:37 AEDT by Patrick King
Modified: 2004-04-14 12:24 AEST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick King 2001-12-19 03:37:40 AEDT 
I am receiving the error :

Couldn't open random pool "yes": No such file or directory

when doing a "make install". Here are my configuration options :

./configure --with-random=/dev/random --prefix=/usr/local/ss
h_new --disable-suid-ssh --with-random --with-tcp-wrappers --x-includes=/usr/ope
nwin/include --x-libraries=/usr/openwin/lib --with-xauth=/usr/openwin/bin/xauth"


Note : /dev/random exists because I am using ANDIrand from 
http://www.solarisresources.com/search_engine/devrandom.html. Here is the 
random file :

crw-r--r--   1 root     sys      133,  0 Dec 17 11:05 /dev/random
Comment 1 Kevin Steves 2001-12-20 08:08:55 AEDT 
if you remove the duplicate --with-random does it work?  configure
should be more robust here.
Comment 2 Damien Miller 2002-01-14 19:03:15 AEDT 
Fixed in -current. The --with-random and --with-prngd-socket now check that
their argument is an absolute path. They will also warn (but not fail) if the
path specified in the argument is not readable.
Comment 3 Damien Miller 2004-04-14 12:24:17 AEST 
Mass change of RESOLVED bugs to CLOSED