Mercurial > dropbear
comparison debian/dropbear.README.Debian @ 399:a707e6148060
merge of '5fdf69ca60d1683cdd9f4c2595134bed26394834'
and '6b61c50f4cf888bea302ac8fcf5dbb573b443251'
author | Matt Johnston <matt@ucc.asn.au> |
---|---|
date | Sat, 03 Feb 2007 08:20:34 +0000 |
parents | 1857c2c551ea |
children | 8c2d2edadf2a |
comparison
equal
deleted
inserted
replaced
394:17d097fc111c | 399:a707e6148060 |
---|---|
37 % /etc/init.d/dropbear restart | 37 % /etc/init.d/dropbear restart |
38 | 38 |
39 See the Dropbear homepage for more information: | 39 See the Dropbear homepage for more information: |
40 http://matt.ucc.asn.au/dropbear/dropbear.html | 40 http://matt.ucc.asn.au/dropbear/dropbear.html |
41 | 41 |
42 | |
43 Entropy from /dev/random | |
44 ------------------------ | |
45 | |
46 The dropbear binary package is configured at compile time to read | |
47 entropy from /dev/random. If /dev/random on a system blocks when | |
48 reading data from it, client logins may be delayed until the client | |
49 times out. The dropbear server writes a notice to the logs when it | |
50 sees /dev/random blocking. A workaround for such systems is to | |
51 re-compile the package with DROPBEAR_RANDOM_DEV set to /dev/urandom | |
52 in options.h. |