summaryrefslogtreecommitdiff
path: root/openwrt/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
commit6894f2b2348da2ce554d2b460e5bd40d6d25f56a (patch)
tree8dbaeaef9d0e8713b0708f4176af75c5b3cf86c9 /openwrt/package/knock/Config.in
parent00ae91b96d0b615b188140586a465718808bd759 (diff)
add knock package (thanks to Florian Fainelli)
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@2569 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'openwrt/package/knock/Config.in')
-rw-r--r--openwrt/package/knock/Config.in41
1 files changed, 41 insertions, 0 deletions
diff --git a/openwrt/package/knock/Config.in b/openwrt/package/knock/Config.in
new file mode 100644
index 0000000000..3f90b496d5
--- /dev/null
+++ b/openwrt/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
+