summaryrefslogtreecommitdiff
path: root/network/knock/README
diff options
context:
space:
mode:
authorJoey Trungale <joey@trungale.net>2010-05-12 23:32:20 +0200
committerDavid Somero <xgizzmo@slackbuilds.org>2010-05-12 23:32:20 +0200
commit43858c38016b71d1112b70f70a4c37755140af55 (patch)
treed2c48a92afd45085341b53df22eff71d6132fd14 /network/knock/README
parent4a3fd527941ac66e06f4e54ee1dcffe531dbfdff (diff)
downloadslackbuilds-43858c38016b71d1112b70f70a4c37755140af55.tar.gz
network/knock: Added to 12.2 repository
Diffstat (limited to 'network/knock/README')
-rw-r--r--network/knock/README10
1 files changed, 10 insertions, 0 deletions
diff --git a/network/knock/README b/network/knock/README
new file mode 100644
index 0000000000..1af140baea
--- /dev/null
+++ b/network/knock/README
@@ -0,0 +1,10 @@
+Knockd and knock are a port-knock server and client, respectively. Knockd
+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.
+