Minor editorial change.

Fork: 0

tundra / tperimeter

Browse code Minor editorial change. master
1 parent ab93326 commit d1b182e557e1e13fddd8fe2c366f660f73f70663 tundra authored on 25 Sep 2006

Patch

Unified Split

Showing 1 changed file

                Ignore Space
               Show notes
              View
            
          
          4 ■■■■■
          tperimeter.txt
               .. footer:: $Id: tperimeter.txt,v 1.109 2006/09/25 08:21:00 tundra Exp $
.. footer:: $Id: tperimeter.txt,v 1.110 2006/09/25 08:23:23 tundra Exp $
 
 
=====================================================
``tperimeter`` - A Dynamic TCP Wrapper Control System
  4) The ``tperimeter.py`` file is written to require full IP
     quads when requesting access.  For example, although tcp
     wrappers allow entries like ``64.23.`` to specify a range
     of addresses, you *cannot* enter such an IP specification via
     ``tperimeter``.
     the ``tperimeter`` web interface.
 
  5) When initially logging into the ``tperimeter`` interface,
     the user probably does not know their "real" dynamic IP
     address - i.e., The address they need opened by ``tperimeter``
+.. footer:: $Id: tperimeter.txt,v 1.109 2006/09/25 08:21:00 tundra Exp $
+.. footer:: $Id: tperimeter.txt,v 1.110 2006/09/25 08:23:23 tundra Exp $
 =====================================================
 ``tperimeter`` - A Dynamic TCP Wrapper Control System
 ) The ``tperimeter.py`` file is written to require full IP
      quads when requesting access.  For example, although tcp
      wrappers allow entries like ``64.23.`` to specify a range
      of addresses, you *cannot* enter such an IP specification via
+     ``tperimeter``.
+     the ``tperimeter`` web interface.
 ) When initially logging into the ``tperimeter`` interface,
      the user probably does not know their "real" dynamic IP
      address - i.e., The address they need opened by ``tperimeter``

Show line notes below