Bug 328

Summary:	starting sshd yeilds PRNG not seeded
Product:	Portable OpenSSH	Reporter:	Gary Walters <gwalters>
Component:	sshd	Assignee:	OpenSSH Bugzilla mailing list <openssh-bugs>
Status:	CLOSED WORKSFORME
Severity:	major
Priority:	P1
Version:	-current
Hardware:	SPARC
OS:	Solaris

Description Gary Walters 2002-07-02 06:33:36 AEST

PRNGD seems to be working fine according to egd. When I go to start 3.4p1 
version of sshd, I get PRNG not seeded and that is all. This used to work with 
3.01p1 of sshd.

Any help is appretiated.

Gary Walters

Comment 1 Luc Suryo 2002-07-02 06:45:36 AEST

This may not be a openssh problem....
If the openssh/openssl was compiled to use /dev/urandom (or /dev/random)
and your system does not have the proper path installed to support /dev/urandom
(or /dev/urandom) this is what you will see when you try to start sshd/ssh

check if this is the case:
ls -l /dev/*random

strings {path-to}/sshd | grep random
strings {path-to}/ssh  | grep random


i'm not sure IF openssh should use another methode in case there is no
/dev/random (or /dev/urandom) as openssl is the one that tells openssh
what to use (am i correct?)

Comment 2 Damien Miller 2002-07-02 18:02:01 AEST

You will need to supply a fair bit more information:

1. How did you configure OpenSSH? (The "./configure" commandline and the summary
it prints would be sufficient)

2. How have you configured OpenSSL? Has it been built or configured to use EGD
itself?

Comment 3 Damien Miller 2002-07-02 18:02:54 AEST

If you are running the built-in PRNG support, try also running "ssh-rand-helper
-v -v -v" from the commandline.

Comment 4 Damien Miller 2002-09-10 22:12:50 AEST

two months, no reply = closed bug

Comment 5 Damien Miller 2004-04-14 12:24:18 AEST

Mass change of RESOLVED bugs to CLOSED