os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- s/ipfw(8)/&man.ipfw.8;

Browse source 
- Some s/IPSec/IPsec I missed in my previous check.
I will fix some other things in that section (VPN over IPsec) in future
commits.
This commit is contained in:
Marc Fonvieille 2003-08-03 09:07:29 +00:00
parent ebeccc039d
commit 1dc4e14672
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=17750
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
en_US.ISO8859-1/books/handbook/security/chapter.sgml
View file

@ -3272,7 +3272,7 @@ Destination Gateway Flags Refs Use Netif Expire
<para>It greatly simplifies testing if you configure the
firewall to allow all traffic through the VPN. You can always
tighten things up later. If you are using ipfw(8) on the
tighten things up later. If you are using &man.ipfw.8; on the
gateway machines then a command like</para>
<programlisting>ipfw add 1 allow ip from any to any via gif0</programlisting>
@ -3380,7 +3380,7 @@ route_vpn="192.168.2.0 192.168.2.1 netmask 0xffffff00"
<sect2>
<title>Step 2: Securing the link</title>
<para>To secure the link we will be using IPSec. IPSec provides
<para>To secure the link we will be using IPsec. IPsec provides
a mechanism for two hosts to agree on an encryption key, and to
then use this key in order to encrypt data between the two
hosts.</para>
@ -3407,7 +3407,7 @@ route_vpn="192.168.2.0 192.168.2.1 netmask 0xffffff00"
<para>Security associations and security policies are both
maintained by the kernel, and can be modified by userland
programs. However, before you can do this you must configure the
kernel to support IPSec and the Encapsulated Security Payload
kernel to support IPsec and the Encapsulated Security Payload
(ESP) protocol. This is done by configuring a kernel with:</para>
<programlisting>options IPSEC