aboutsummaryrefslogtreecommitdiff
path: root/network/knock
diff options
context:
space:
mode:
authorB. Watson <yalhcru@gmail.com>2022-03-13 18:06:19 -0400
committerB. Watson <yalhcru@gmail.com>2022-03-13 18:06:19 -0400
commit53e1f941d5ed273f1cab72366c7e7fcd06633697 (patch)
tree04a85b1c2b8f7e0db028cf1e7557c0060cdbfe10 /network/knock
parente68e5889fe54bb35253b009e810044ff617b72f4 (diff)
network/knock: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
Diffstat (limited to 'network/knock')
-rw-r--r--network/knock/README19
1 files changed, 9 insertions, 10 deletions
diff --git a/network/knock/README b/network/knock/README
index 1af140baead2..c439f9ced428 100644
--- a/network/knock/README
+++ b/network/knock/README
@@ -1,10 +1,9 @@
-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.
-
+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.