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

Few rewordings to fix the confusing "number of scenarios" mentions.

Browse source 
This section still requires a lot of work...

Submitted by:	many persons
This commit is contained in:
Marc Fonvieille 2004-09-17 13:14:38 +00:00
parent 115cd3f6e3
commit a9bf11e7be
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=22380
1 changed files with 6 additions and 7 deletions

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

@ -4203,19 +4203,18 @@ options IPSEC_DEBUG #debug for IP security
<sect2>
<title>The Problem</title>
<para>There's no standard for what constitutes a VPN. VPNs can
<para>There is no standard for what constitutes a VPN. VPNs can
be implemented using a number of different technologies, each of
which have their own strengths and weaknesses. This article
presents a number of scenarios, and strategies for implementing a
VPN for each scenario.</para>
which have their own strengths and weaknesses. This section
presents a scenario, and the strategies used for implementing a
VPN for this scenario.</para>
</sect2>
<sect2>
<title>Scenario #1: Two networks, connected to the Internet, to
<title>The Scenario: Two networks, connected to the Internet, to
behave as one</title>
<para>This is the scenario that caused me to first investigating
VPNs. The premise is as follows:</para>
<para>The premise is as follows:</para>
<itemizedlist>
<listitem>