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) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
