Your message dated Sun, 25 Sep 2005 13:38:49 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#310732: dropbear does not work on low entropy systems
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 25 May 2005 14:18:31 +0000
>From [EMAIL PROTECTED] Wed May 25 07:18:31 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mailgw.mikrotik.com [159.148.172.194]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DawiN-0007WU-00; Wed, 25 May 2005 07:18:31 -0700
Received: from [10.5.8.105] (helo=[10.5.8.105])
by mailgw.mikrotik.com with esmtp (Exim 4.50)
id 1Dawg7-0001Yx-Kt; Wed, 25 May 2005 17:16:11 +0300
From: Dmitry Golubev <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: dropbear does not work on low entropy systems
Date: Wed, 25 May 2005 17:18:05 +0300
User-Agent: KMail/1.7.2
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <[EMAIL PROTECTED]>
X-mailgw.mikrotik.com-MailScanner: Found to be clean
X-mailgw.mikrotik.com-MailScanner-SpamCheck: not spam,
SpamAssassin (score=-2.82, required 5, ALL_TRUSTED -2.82)
X-MailScanner-From: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: dropbear
Version: 0.45-2
Severity: seriuos
Installed dropbear package on RouterBOARD500 (mipsel architecture)
successfully, but when clients connect, they do not even get to the login
prompt. As explained here:
http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/2005q1/000151.html
i changed options.h file so that it would work with /dev/urandom instead
of /dev/random , and it started to work.
I am using Debian GNU/Linux 3.1, kernel 2.4.30.
---------------------------------------
Received: (at 310732-done) by bugs.debian.org; 25 Sep 2005 13:45:01 +0000
>From [EMAIL PROTECTED] Sun Sep 25 06:45:01 2005
Return-path: <[EMAIL PROTECTED]>
Received: from a.mx.smarden.org [212.21.76.77]
by spohr.debian.org with smtp (Exim 3.36 1 (Debian))
id 1EJWoO-0000uX-00; Sun, 25 Sep 2005 06:45:01 -0700
Received: (qmail 20462 invoked by uid 1000); 25 Sep 2005 13:38:40 -0000
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 25 Sep 2005 13:38:49 +0000
From: Gerrit Pape <[EMAIL PROTECTED]>
To: Dmitry Golubev <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#310732: dropbear does not work on low entropy systems
Reply-To: [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
On Sun, May 29, 2005 at 02:13:30PM +0300, Dmitry Golubev wrote:
> > yes, but do you suggest to switch the Debian packages to use
> > /dev/urandom by default? I don't think it's a good idea, most systems
> > with Debian installed should provide enough entropy through /dev/random.
> > A solution could be to have dropbear first check /dev/random, and if it
> > blocks, to fall back to /dev/urandom.
>
> I am nowhere near understanding the differences between the two files, but
> your solution seems good. I spent half of a day trying to find why it does
> not work...
Hi Dmitry, more recent versions of dropbear now print an error message
to the logs in case /dev/random blocks. The default still is to use
/dev/random by default, as nearly all Debian systems should support it
just fine.
Thanks, Gerrit.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
