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

Add a missing "a". Also, spell "premise" correctly.

Browse source
This commit is contained in:
Daniel Harris 2001-01-18 23:43:31 +00:00
parent 7b2d582bc9
commit 7dbd09c337
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=8702
2 changed files with 8 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

8
en_US.ISO8859-1/articles/dialup-firewall/article.sgml
View file

@ -1,7 +1,7 @@
<!-- <!--
The FreeBSD Documentation Project The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/articles/dialup-firewall/article.sgml,v 1.3 2000/07/11 10:21:49 nbm Exp $ $FreeBSD: doc/en_US.ISO_8859-1/articles/dialup-firewall/article.sgml,v 1.4 2000/08/19 20:51:20 ben Exp $
--> -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN" [ <!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN" [
@ -24,7 +24,7 @@
</author> </author>
</authorgroup> </authorgroup>
<pubdate>$Date: 2000-08-19 20:51:20 $</pubdate> <pubdate>$Date: 2001-01-18 23:43:31 $</pubdate>
<abstract> <abstract>
<para>This article documents how to setup a firewall using a PPP <para>This article documents how to setup a firewall using a PPP
@ -121,7 +121,7 @@
prevents tools such as nmap etc from identifying the TCP/IP prevents tools such as nmap etc from identifying the TCP/IP
stack of the machine, but breaks support for RFC1644 stack of the machine, but breaks support for RFC1644
extensions. This is NOT recommended if the machine will be extensions. This is NOT recommended if the machine will be
running web server.</para> running a web server.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
</variablelist> </variablelist>
@ -183,7 +183,7 @@ ppp_profile="<replaceable>profile</replaceable>"</programlisting>
your own rulebase. First, let's start with the basics of closed your own rulebase. First, let's start with the basics of closed
firewalling. What you want to do is deny everything by default and then firewalling. What you want to do is deny everything by default and then
only open up for the things you really need. Rules should be in the only open up for the things you really need. Rules should be in the
order of allow first and then deny. The premis is that you add the order of allow first and then deny. The premise is that you add the
rules for your allows, and then everything else is denied. :)</para> rules for your allows, and then everything else is denied. :)</para>
<para>Now, let's make the dir /etc/firewall. Change into the directory and <para>Now, let's make the dir /etc/firewall. Change into the directory and

8
en_US.ISO_8859-1/articles/dialup-firewall/article.sgml
View file

@ -1,7 +1,7 @@
<!-- <!--
The FreeBSD Documentation Project The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/articles/dialup-firewall/article.sgml,v 1.3 2000/07/11 10:21:49 nbm Exp $ $FreeBSD: doc/en_US.ISO_8859-1/articles/dialup-firewall/article.sgml,v 1.4 2000/08/19 20:51:20 ben Exp $
--> -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN" [ <!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN" [
@ -24,7 +24,7 @@
</author> </author>
</authorgroup> </authorgroup>
<pubdate>$Date: 2000-08-19 20:51:20 $</pubdate> <pubdate>$Date: 2001-01-18 23:43:31 $</pubdate>
<abstract> <abstract>
<para>This article documents how to setup a firewall using a PPP <para>This article documents how to setup a firewall using a PPP
@ -121,7 +121,7 @@
prevents tools such as nmap etc from identifying the TCP/IP prevents tools such as nmap etc from identifying the TCP/IP
stack of the machine, but breaks support for RFC1644 stack of the machine, but breaks support for RFC1644
extensions. This is NOT recommended if the machine will be extensions. This is NOT recommended if the machine will be
running web server.</para> running a web server.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
</variablelist> </variablelist>
@ -183,7 +183,7 @@ ppp_profile="<replaceable>profile</replaceable>"</programlisting>
your own rulebase. First, let's start with the basics of closed your own rulebase. First, let's start with the basics of closed
firewalling. What you want to do is deny everything by default and then firewalling. What you want to do is deny everything by default and then
only open up for the things you really need. Rules should be in the only open up for the things you really need. Rules should be in the
order of allow first and then deny. The premis is that you add the order of allow first and then deny. The premise is that you add the
rules for your allows, and then everything else is denied. :)</para> rules for your allows, and then everything else is denied. :)</para>
<para>Now, let's make the dir /etc/firewall. Change into the directory and <para>Now, let's make the dir /etc/firewall. Change into the directory and