summaryrefslogtreecommitdiffstats
path: root/package/knock/Config.in
diff options
context:
space:
mode:
authornico <nico@3c298f89-4303-0410-b956-a3cf2f4a3e73>2005-11-29 19:00:17 +0000
committernico <nico@3c298f89-4303-0410-b956-a3cf2f4a3e73>2005-11-29 19:00:17 +0000
commitec8315f754bb48a2bf3336793ad84798331d7ee4 (patch)
treee76180f7cb47780d41c7e7c28833f247cdeed38f /package/knock/Config.in
parent9bdb5ee5bf970b612d780c53cabfb9e4df463e3c (diff)
add knock package (thanks to Florian Fainelli)
git-svn-id: svn://svn.openwrt.org/openwrt/trunk/openwrt@2569 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'package/knock/Config.in')
-rw-r--r--package/knock/Config.in41
1 files changed, 41 insertions, 0 deletions
diff --git a/package/knock/Config.in b/package/knock/Config.in
new file mode 100644
index 000000000..3f90b496d
--- /dev/null
+++ b/package/knock/Config.in
@@ -0,0 +1,41 @@
+config BR2_COMPILE_KNOCK
+ tristate
+ default n
+ depends BR2_PACKAGE_KNOCK || BR2_PACKAGE_KNOCKD
+
+config BR2_PACKAGE_KNOCK
+ prompt "knock............................. A port-knocking client"
+ tristate
+ default m if CONFIG_DEVEL
+ select BR2_COMPILE_KNOCK
+ help
+ It listens to all traffic on an ethernet (or PPP) interface,
+ looking for special "knock" sequences of port-hits. A client
+ makes these port-hits by sending a TCP (or UDP) packet to a
+ port on the server. This port need not be open -- since
+ knockd listens at the link-layer level, it sees all traffic
+ even if it's destined for a closed port. When the server
+ detects a specific sequence of port-hits, it runs a command
+ defined in its configuration file. This can be used to open
+ up holes in a firewall for quick access.
+
+ http://www.zeroflux.org/cgi-bin/cvstrac/knock/wiki
+
+config BR2_PACKAGE_KNOCKD
+ prompt "knockd............................ A port-knocking server"
+ tristate
+ default m if CONFIG_DEVEL
+ select BR2_COMPILE_KNOCK
+ help
+ It listens to all traffic on an ethernet (or PPP) interface,
+ looking for special "knock" sequences of port-hits. A client
+ makes these port-hits by sending a TCP (or UDP) packet to a
+ port on the server. This port need not be open -- since
+ knockd listens at the link-layer level, it sees all traffic
+ even if it's destined for a closed port. When the server
+ detects a specific sequence of port-hits, it runs a command
+ defined in its configuration file. This can be used to open
+ up holes in a firewall for quick access.
+
+ http://www.zeroflux.org/cgi-bin/cvstrac/knock/wiki
+