2005-10-29 09:01:33 +02:00
|
|
|
config BR2_PACKAGE_DROPBEAR
|
|
|
|
|
bool "dropbear"
|
2004-10-09 08:13:40 +02:00
|
|
|
default n
|
|
|
|
|
help
|
2004-10-14 22:33:45 +02:00
|
|
|
A small SSH 2 server designed for small memory environments.
|
2004-10-09 08:13:40 +02:00
|
|
|
|
2005-10-29 09:01:33 +02:00
|
|
|
http://matt.ucc.asn.au/dropbear/dropbear.html
|
2005-03-09 09:30:47 +01:00
|
|
|
|
2005-10-29 09:01:33 +02:00
|
|
|
config BR2_PACKAGE_DROPBEAR_URANDOM
|
2007-07-06 13:42:03 +02:00
|
|
|
bool "Use /dev/urandom (low entropy systems only)?"
|
2005-03-09 09:30:47 +01:00
|
|
|
default n
|
2005-10-29 09:01:33 +02:00
|
|
|
depends on BR2_PACKAGE_DROPBEAR
|
2005-03-09 09:30:47 +01:00
|
|
|
help
|
|
|
|
|
By default, dropbear uses the much more secure /dev/random. If you
|
|
|
|
|
are using a system lacking usable entropy sources, this could cause
|
|
|
|
|
the dropbear ssh daemon to block forever waiting for entropy that
|
|
|
|
|
will never arrive. By making dropbear use /dev/urandom, you can
|
|
|
|
|
prevent Dropbear from blocking while waiting on the random device.
|
|
|
|
|
This could however significantly reduce the security of your ssh
|
|
|
|
|
connections. Make sure you know what you are doing if you enable
|
|
|
|
|
this option -- most people should answer N.
|
