From owner-freebsd-stable@FreeBSD.ORG Thu Sep 1 19:59:36 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F47316A443 for ; Thu, 1 Sep 2005 19:59:36 +0000 (GMT) (envelope-from stephane@enertiasoft.com) Received: from mx1.enertiatech.com (a72-29-234-73.enertiatech.com [72.29.234.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6A7D43D45 for ; Thu, 1 Sep 2005 19:59:35 +0000 (GMT) (envelope-from stephane@enertiasoft.com) Received: from localhost (localhost [127.0.0.1]) by mx1.enertiatech.com (Postfix) with ESMTP id D3806631D for ; Thu, 1 Sep 2005 11:29:26 -0600 (MDT) Received: from mx1.enertiatech.com ([127.0.0.1]) by localhost (mx1.enertiatech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16944-01 for ; Thu, 1 Sep 2005 11:29:26 -0600 (MDT) Received: from [10.0.0.34] (unknown [10.0.0.34]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.enertiatech.com (Postfix) with ESMTP id 1103262C8 for ; Thu, 1 Sep 2005 11:29:26 -0600 (MDT) Mime-Version: 1.0 (Apple Message framework v734) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-stable@freebsd.org From: Stephane Raimbault Date: Thu, 1 Sep 2005 11:29:24 -0600 X-Mailer: Apple Mail (2.734) X-Virus-Scanned: amavisd-new at enertiasoft.com Subject: 5.4: Can't start ssh due to entropy source blocking? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2005 19:59:36 -0000 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 . This will timeout in 300 seconds, but waiting for the timeout without typing junk may make the entropy source deliver predictable output. Just hit 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.