Bug 575 - a bug make me crazy--PRNG is not seeded
Summary: a bug make me crazy--PRNG is not seeded
Status: CLOSED WORKSFORME
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: Build system (show other bugs)
Version: -current
Hardware: Other Linux
: P2 normal
Assignee: OpenSSH Bugzilla mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-24 20:17 AEST by lion
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 lion 2003-05-24 20:17:03 AEST 
hi:
	
    Now, i have a headache for a embeded product, i need port openssh to this 
platform,
it's arch is ARCA1(a chinese CPU), it's not important.
    
    ok, i compiled the openssh3.3.6p1 with arca1 compiler, it's ok.
    
    after i put it on the platform, a message show me on the screen----PRNG is 
not seeded. 

    God! i search solution for a whole day, but no result. 
 
    my openssl version is 0.9.6, my system have not the device RANDOM, may be 
caused by this reason? 

    what can i do? copy a '/dev/random' and '/dev/urandom' to /dev on the ARCA1 
platform from any where in x86 system? i tried, but failed.

    give me a solution for this problem please, it's really important for me.

  								
					thanks a lot, linux fans 
                                                        
	                                                         
lion_3875@sina.com
¡¡¡¡¡¡¡¡¡¡¡¡¡¡							
							¡¡2003-05-24
Comment 1 Ben Lindstrom 2003-05-25 05:38:35 AEST 
1. check for a /dev/random and /dev/urandom  (all Linux should have it
no matter what cpu they are running on).
2. at the end of ./configure  it shows you a matrix of features.  Please
post that.  One of the lines has to do with testing to see if OpenSSL can
seed itself or if it needs help.

- Ben
Comment 2 Darren Tucker 2003-05-25 16:18:08 AEST 
/dev/random and /dev/urandom are device special files, so you'll need to either 
"cp -a" them or recreate them with the appropriate mknod commands on your 
platform.

You may need to recompile OpenSSL once you've created the device files, then 
recompile OpenSSH.

You can also try configure'ing OpenSSH with --with-rand-helper.
Comment 3 Damien Miller 2003-06-04 23:46:31 AEST 
Local configuration issue
Comment 4 Damien Miller 2004-04-14 12:24:19 AEST 
Mass change of RESOLVED bugs to CLOSED