Your message dated Sun, 16 Apr 2006 10:17:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#355414: fixed in dropbear 0.48.1-1
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)

--- Begin Message ---
Package: dropbear
Severity: normal

This is the same problem as in #310732. In other words, dropbear
depends on /dev/random having enough entropy, but not all systems have
enough entropy in there. This causes logins to hang.

This is true especially for embedded systems where dropbear is likely
to be used due to its smaller memory footprint. Debian is now running
on many such systems (especially some of the architectures), so I
don't think it's fair to dismiss the bug by saying that /dev/random
can be expected to have enough entropy.

I'm not sure what the solution would be though. Some ideas:

- Run-time option to choose random device (/dev/random or
/dev/urandom).
- Run-time option to use PRNGD or EGD.
- Better documentation of this problem.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)



--- End Message ---
--- Begin Message ---
Source: dropbear
Source-Version: 0.48.1-1

We believe that the bug you reported is fixed in the latest version of
dropbear, which is due to be installed in the Debian FTP archive:

dropbear_0.48.1-1.diff.gz
  to pool/main/d/dropbear/dropbear_0.48.1-1.diff.gz
dropbear_0.48.1-1.dsc
  to pool/main/d/dropbear/dropbear_0.48.1-1.dsc
dropbear_0.48.1-1_i386.deb
  to pool/main/d/dropbear/dropbear_0.48.1-1_i386.deb
dropbear_0.48.1.orig.tar.gz
  to pool/main/d/dropbear/dropbear_0.48.1.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gerrit Pape <[EMAIL PROTECTED]> (supplier of updated dropbear package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 16 Apr 2006 16:16:40 +0000
Source: dropbear
Binary: dropbear
Architecture: source i386
Version: 0.48.1-1
Distribution: unstable
Urgency: medium
Maintainer: Gerrit Pape <[EMAIL PROTECTED]>
Changed-By: Gerrit Pape <[EMAIL PROTECTED]>
Description: 
 dropbear   - lightweight SSH2 server and client
Closes: 351882 355414
Changes: 
 dropbear (0.48.1-1) unstable; urgency=medium
 .
   * new upstream point release.
     * Compile fix for scp
   * debian/diff/dbclient.1.diff: new: document -R option to dbclient
     accurately (thx Markus Schaber; closes: #351882).
   * debian/dropbear.README.Debian: document a workaround for systems with
     possibly blocking /dev/random device (closes: #355414)..
Files: 
 cbcfa94355bfb6edffa3594c2d03cc14 556 net optional dropbear_0.48.1-1.dsc
 ca8e53a766faec831882831364568421 1473114 net optional 
dropbear_0.48.1.orig.tar.gz
 d7aa8b235eb4a6b853f7b5ae5a122986 1633 net optional dropbear_0.48.1-1.diff.gz
 384a1b16459788223110422786191b05 210848 net optional dropbear_0.48.1-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEQnhrGJoyQbxwpv8RAi3RAJ9gscaBAADwLq5qYQ9/G+DT4MtwhQCbBbdc
S2EVhUlq70+4uxOr1TFdWrs=
=2Ylw
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to