[Midnightbsd-cvs] src [11857] trunk/share/examples/ipfilter/ipf-howto.txt: fix typos

[laffer1 at midnightbsd.org]

Revision: 11857
          http://svnweb.midnightbsd.org/src/?rev=11857
Author:   laffer1
Date:     2018-07-13 08:53:45 -0400 (Fri, 13 Jul 2018)
Log Message:
-----------
fix typos

Modified Paths:
--------------
    trunk/share/examples/ipfilter/ipf-howto.txt

Property Changed:
----------------
    trunk/share/examples/ipfilter/ipf-howto.txt

Modified: trunk/share/examples/ipfilter/ipf-howto.txt
===================================================================
--- trunk/share/examples/ipfilter/ipf-howto.txt	2018-07-13 12:51:43 UTC (rev 11856)
+++ trunk/share/examples/ipfilter/ipf-howto.txt	2018-07-13 12:53:45 UTC (rev 11857)
@@ -8,7 +8,7 @@
 
               Brendan Conoboy <synk at swcp.com>
             Erik Fichtner <emf at obfuscation.org>
-            $FreeBSD: src/share/examples/ipfilter/ipf-howto.txt,v 1.2 2003/01/01 18:48:48 schweikh Exp $
+            $MidnightBSD$
 
                 Fri Apr 20 09:31:14 EDT 2001
 
@@ -1036,11 +1036,11 @@
 it's not a server, it's a client.  And this  client  doesn't
 want  unauthorized  packets  entering  its  IP stack at all.
 However, the client wants full access to  the  internet  and
-the  reply packets that such privledge entails.  This simple
+the reply packets that such privilege entails.  This simple
 ruleset creates state entries for  every  new  outgoing  TCP
 session.   Again,  since a state entry is created, these new
 TCP sessions are free to talk back and forth as they  please
-without  the  hinderance or inspection of the firewall rule-
+without the hindrance or inspection of the firewall rule-
 set.  We mentioned that this also works for UDP and ICMP:
 
     block in  quick on tun0 all
@@ -1271,7 +1271,7 @@
 This  works  because  every  packet  that  should be allowed
 through makes it into the state table  before  the  blocking
 rules  are reached. The only scan this won't detect is a SYN
-scan itself.  If you're truely worried about that, you might
+scan itself.  If you're truly worried about that, you might
 even want to log all initial SYN packets.
 
 3.6.  Responding To a Blocked Packet
@@ -2564,7 +2564,7 @@
 your  firewall,  thereby  subverting its ruleset?  This is a
 common problem administrators must face,  particularly  when
 they're  using  firewall  solutions  on top of their Unix/NT
-machines.  Some use it as an arguement for blackbox hardware
+machines.  Some use it as an argument for blackbox hardware
 solutions,  under  the flawed notion that inherent obscurity
 
 


Property changes on: trunk/share/examples/ipfilter/ipf-howto.txt
___________________________________________________________________
Added: svn:keywords
## -0,0 +1 ##
+MidnightBSD=%H
\ No newline at end of property