mirror of
https://gitlab.com/shorewall/code.git
synced 2025-01-03 03:59:16 +01:00
Release notes Update
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1568 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
parent
acdf9b94a6
commit
7082c76f60
File diff suppressed because it is too large
Load Diff
@ -49,6 +49,10 @@
|
|||||||
<section>
|
<section>
|
||||||
<title>Shorewall 2.1 and Kernel 2.6 IPSEC</title>
|
<title>Shorewall 2.1 and Kernel 2.6 IPSEC</title>
|
||||||
|
|
||||||
|
<para>This is <emphasis role="bold">not</emphasis> a HOWTO for Kernel 2.6
|
||||||
|
IPSEC -- for that, please see <ulink
|
||||||
|
url="http://www.ipsec-howto.org/">http://www.ipsec-howto.org/</ulink>.</para>
|
||||||
|
|
||||||
<para>The 2.6 Linux Kernel introduces new facilities for defining
|
<para>The 2.6 Linux Kernel introduces new facilities for defining
|
||||||
encrypted communication between hosts in a network. The network
|
encrypted communication between hosts in a network. The network
|
||||||
administrator defines a set of Security Policies which are stored in the
|
administrator defines a set of Security Policies which are stored in the
|
||||||
@ -109,9 +113,10 @@
|
|||||||
</listitem>
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>A <filename>new /etc/shorewall/ipsec</filename> file allows you
|
<para>A <filename>new </filename><ulink
|
||||||
to associate zones with traffic that will be encrypted or that has
|
url="Documentation.htm#Ipsec"><filename>/etc/shorewall/ipsec</filename></ulink>
|
||||||
been decrypted.</para>
|
file allows you to associate zones with traffic that will be encrypted
|
||||||
|
or that has been decrypted.</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</orderedlist>
|
</orderedlist>
|
||||||
|
|
||||||
@ -150,7 +155,8 @@
|
|||||||
|
|
||||||
<para>Finally, the OPTIONS, IN OPTIONS and OUT OPTIONS columns in
|
<para>Finally, the OPTIONS, IN OPTIONS and OUT OPTIONS columns in
|
||||||
/etc/shorewall/ipsec can be used to match the zone to a particular (set
|
/etc/shorewall/ipsec can be used to match the zone to a particular (set
|
||||||
of) SA(s) used to encrypt and decrypt traffic to/from the zone.</para>
|
of) SA(s) used to encrypt and decrypt traffic to/from the zone and the
|
||||||
|
security policies that select which traffic to encrypt/decrypt.</para>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
<section>
|
<section>
|
||||||
|
Loading…
Reference in New Issue
Block a user