From owner-freebsd-questions@FreeBSD.ORG Wed Feb 4 11:01:28 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C554716A4CF for ; Wed, 4 Feb 2004 11:01:28 -0800 (PST) Received: from rdsnet.ro (smtp.rdsnet.ro [62.231.74.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3594243D48 for ; Wed, 4 Feb 2004 11:01:26 -0800 (PST) (envelope-from itetcu@apropo.ro) Received: (qmail 17674 invoked from network); 4 Feb 2004 19:01:25 -0000 Received: from unknown (HELO it.buh.cameradicommercio.ro) (81.196.25.19) by mail.rdsnet.ro with SMTP; 4 Feb 2004 19:01:25 -0000 Date: Wed, 4 Feb 2004 21:02:57 +0200 From: Ion-Mihai Tetcu To: Kris Kennaway Message-Id: <20040204210257.1b309012@it.buh.cameradicommercio.ro> In-Reply-To: <20040204183520.GA25749@xor.obsecurity.org> References: <0HSK009A6HZBMY@mail.etat.lu> <20040204183520.GA25749@xor.obsecurity.org> X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: Didier WIROTH cc: freebsd-questions@freebsd.org Subject: Re: ssh error "PRNG is not seeded" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Feb 2004 19:01:28 -0000 On Wed, 4 Feb 2004 10:35:20 -0800 Kris Kennaway wrote: > On Wed, Feb 04, 2004 at 05:04:24PM +0100, Didier WIROTH wrote: > > Hi, > > I've chosen "do want to login via ssh=NO" (can't exactly remember but it was > > a similar question) during setup of freebsd5.2, now, when I try to use scp > > or ssh client I get the following error message: > > "PRNG is not seeded" > > > > How can I solve the problem?! > > Have you built a custom kernel? You may have removed support for the > (effectively mandatory) 'random' device; add it back or kldload the > module. Hm, I remember having this issue a few days ago and it magically disappeared, if memory serves; if not I had a slightly (few deay) kernel/world out of sync. But the kernel had random. -- IOnut Unregistered ;) FreeBSD user