From d11b70150e5eda6f610e0f05f2554cd14373af69 Mon Sep 17 00:00:00 2001 From: Mike Frysinger Date: Sat, 29 Oct 2005 07:01:33 +0000 Subject: rename dropbear_sshd to just dropbear --- package/dropbear/Config.in | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 package/dropbear/Config.in (limited to 'package/dropbear/Config.in') diff --git a/package/dropbear/Config.in b/package/dropbear/Config.in new file mode 100644 index 000000000..a545001db --- /dev/null +++ b/package/dropbear/Config.in @@ -0,0 +1,21 @@ +config BR2_PACKAGE_DROPBEAR + bool "dropbear" + default n + help + A small SSH 2 server designed for small memory environments. + + http://matt.ucc.asn.au/dropbear/dropbear.html + +config BR2_PACKAGE_DROPBEAR_URANDOM + bool " Use /dev/urandom (low entropy systems only)?" + default n + depends on BR2_PACKAGE_DROPBEAR + 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. -- cgit v1.2.3