The device /dev/random is supposed to block when it runs out of entropy,
while /dev/urandom starts producing pseudo random numbers when no real
randomness is available, such as on a server with no keyboard
activity. Since OpenSSH defaults to urandom this should not
occur. You might check that you configure really picked the urandom
device, and not /dev/random.
Amanda.
On Thu, 12 Apr 2001, Jon Wilson wrote:
> The OpenSSH was compiled from source. Redhat Sparc is very like Redhat
> i386, and does have /dev/random
>
> I have not been able to replicate this. Any ideas about how I might do so,
> or other (more technical?) forums I might discuss this matter in? I like
> (open)ssh, but it is not much use if it randomly crashes on boxes I have
> poor physical access to.
>
> Jon
>
> On Wed, 11 Apr 2001, Lutz Jaenicke wrote:
> > On Wed, Apr 11, 2001 at 01:43:48AM +0100, Jon Wilson wrote:
> > > I am getting the error: "Couldn't obtain random bytes (error 604389476)"
> > > from my openssh daemon.
> > >
> > > Could somone explain what this error means, and what I might do to stop
> > > it reoccuring? I get it after about 4 days uptime.
> > >
> > > The box in question is a dual processor Sparc20, running Redhat 6.2 Sparc
> > > Linux (stock Redhat 2.2.14-5.0smp kernel). SSH version is OpenSSH_2.5.2p2.
> >
> > I never touched a Redhat Sparc Linux, but provided it also does supply
> > a /dev/random device, this error should never occur.
> > If the OpenSSH version is also coming as a package from Redhat, I would
> > recommend you to complain to them.
> >
> > Best regards,
> > Lutz
