Stephane Raimbault
2005-Sep-01 19:59 UTC
5.4: Can't start ssh due to entropy source blocking?
I installed a fresh 5.4-RELEASE/amd64 system on a Dell PE1850 and when attempting to setup sshd for the server I'm getting a weird error: # /etc/rc.d/sshd start /etc/rc.d/sshd: WARNING: Setting entropy source to blocking mode. ===================================================Type a full screenful of random junk to unblock it and remember to finish with <enter>. This will timeout in 300 seconds, but waiting for the timeout without typing junk may make the entropy source deliver predictable output. Just hit <enter> for fast+insecure startup. ===================================================kern.random.sys.seeded: 0 -> 0 PRNG is not seeded PRNG is not seeded PRNG is not seeded # I tried rebooting the system and letting it start a startup, but the same thing occurred. I've setup a few 5.4 systems and this is the first time I ran into this particular problem. Doing some googling I'm guessing that the /dev/random isn't seeded properly? I'm a bit confused about that, but that's all I have found thus far. Any suggestions as to what I need to be doing to resolve my problem would be most helpful. Has anyone else ran into this problem on a 5.4- RELEASE system. Thank you, Stephane.
On Sep 1, 2005, at 1:29 PM, Stephane Raimbault wrote:> Type a full screenful of random junk to unblock > it and remember to finish with <enter>. This will > timeout in 300 seconds, but waiting for > the timeout without typing junk may make the > entropy source deliver predictable output. > > Just hit <enter> for fast+insecure startup. >so what did you do, just hit enter or did you follow the instructions and type a screenful of junk? Vivek Khera, Ph.D. +1-301-869-4449 x806
I ran into it just yesterday. I was walking a newb in our IT department through setting up a server, and he used all caps for the domain.tld portion of the server name - testbed.ZETRON.COM. Had the same problem as you describe. Edited the /etc/rc.conf, had him reboot and try again, and it worked just fine. Kurt> -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org]On Behalf Of > Stephane Raimbault > Sent: Thursday, September 01, 2005 13:18 > To: Vivek Khera > Cc: freebsd-stable@freebsd.org > Subject: Re: 5.4: Can't start ssh due to entropy source blocking? > > > yes sorry I wasn't more clear. I tried putting a bunch of junk on > the screen as well as just left it blank and the result was the > same. Is it possible I didn't provide enough junk? I haven't seen > this behavior before? > > Thanks, > Stephane > > On 1-Sep-05, at 2:07 PM, Vivek Khera wrote: > > > > > On Sep 1, 2005, at 1:29 PM, Stephane Raimbault wrote: > > > > > >> Type a full screenful of random junk to unblock > >> it and remember to finish with <enter>. This will > >> timeout in 300 seconds, but waiting for > >> the timeout without typing junk may make the > >> entropy source deliver predictable output. > >> > >> Just hit <enter> for fast+insecure startup. > >> > >> > > > > so what did you do, just hit enter or did you follow the > > instructions and type a screenful of junk? > > > > > > Vivek Khera, Ph.D. > > +1-301-869-4449 x806 > > > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable- > > unsubscribe@freebsd.org" > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" >