Dropbear 0.52 should be using /dev/urandom, which AFAIK won't block? Unless the behaviour of recent kernels has changed...
If Dropbear is blocking on the random device it should log something - could you check the auth logs? Matt On Tue, Sep 01, 2009 at 11:42:14AM +0200, [email protected] wrote: > Package: dropbear > Version: 0.52-2 > Severity: normal > > hi! > > dropbear seems to block at startup until it has read enough entropy. > so if entropy is provided somewhat slowly, the startup blocks. as i just > found out, this blocking seems to occur before going to the background. > > i guess it's generally worth considering whether it's wise that way, or if it > might be better to first go to the background and then read entropy (and > block). > > in case blocking in the foreground is intended behaviour, > /usr/share/initramfs-tools/scripts/init-premount/dropbear should be changed, > executing dropbear in the background in the first place (make last line > "/sbin/dropbear &" instead of "/sbin/dropbear") - otherwise taking long to > gather entropy translates into blocking the boot procedure... > > regards, > > Chris > > > > > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
