summaryrefslogtreecommitdiff
path: root/package/dropbear/Config.in
diff options
context:
space:
mode:
authorMike Frysinger <vapier@gentoo.org>2005-10-29 07:01:33 +0000
committerMike Frysinger <vapier@gentoo.org>2005-10-29 07:01:33 +0000
commitd11b70150e5eda6f610e0f05f2554cd14373af69 (patch)
tree22510af5edb598b919134d3c197b12c4225410f1 /package/dropbear/Config.in
parent06b151e5c90718786d0bdc90b30e3f753ad60ea0 (diff)
rename dropbear_sshd to just dropbear
Diffstat (limited to 'package/dropbear/Config.in')
-rw-r--r--package/dropbear/Config.in21
1 files changed, 21 insertions, 0 deletions
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.