MFen: r37165 -> r38826
Fix typo. [1] Merging work done by: delphij Submitted by: Sutra Zhou (zhoushuqun at gmail dot com) [1] Obtained from: The FreeBSD Simplified Chinese Project
This commit is contained in:
parent
418e795a80
commit
82b11d4b3e
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=39266
1 changed files with 20 additions and 18 deletions
|
@ -2,7 +2,7 @@
|
|||
The FreeBSD Documentation Project
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.96
|
||||
Original Revision: r38826
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
|
@ -316,7 +316,7 @@ device pfsync</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>可用的 rc.conf 选项</title>
|
||||
<title>可用的 <filename>rc.conf</filename> 选项</title>
|
||||
|
||||
<para>The following &man.rc.conf.5; statements configure
|
||||
<acronym>PF</acronym> and &man.pflog.4; at boot:</para>
|
||||
|
@ -352,8 +352,10 @@ pflog_flags="" #
|
|||
<para>在浏览 <ulink
|
||||
url="http://www.openbsd.org/faq/pf/">PF FAQ</ulink> 时,
|
||||
请时刻注意不同版本的 &os; 可能会使用不同版本的 PF。 目前,
|
||||
&os; 使用的是与
|
||||
OpenBSD 4.1 相同的 <acronym>PF</acronym>版本。</para>
|
||||
&os; 8.<replaceable>X</replaceable> 和之前的系统使用的是与
|
||||
OpenBSD 4.1 相同版本的 <acronym>PF</acronym>。
|
||||
&os; 9.<replaceable>X</replaceable> 和之后的系统使用的是与
|
||||
OpenBSD 4.5 相同版本的 <acronym>PF</acronym>。</para>
|
||||
</warning>
|
||||
|
||||
<para>&a.pf; 是一个提有关配置使用 <acronym>PF</acronym>
|
||||
|
@ -389,7 +391,7 @@ pflog_flags="" #
|
|||
|
||||
<row>
|
||||
<entry><command>pfctl <option>-F</option> all <option>-f</option> /etc/pf.conf</command></entry>
|
||||
<entry>清楚所有规则 (nat, filter, state, table, 等等。)
|
||||
<entry>清除所有规则 (nat, filter, state, table, 等等。)
|
||||
并读取 <filename>/etc/pf.conf</filename></entry>
|
||||
</row>
|
||||
|
||||
|
@ -589,7 +591,7 @@ options IPFILTER_DEFAULT_BLOCK</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>可用的 rc.conf 选项</title>
|
||||
<title>可用的 <filename>rc.conf</filename> 选项</title>
|
||||
|
||||
<para>要在启动时激活 IPF, 需要在 <filename>/etc/rc.conf</filename>
|
||||
中增加下面的设置:</para>
|
||||
|
@ -999,12 +1001,12 @@ sh /etc/ipf.rules.script</programlisting>
|
|||
这些是编写明示允许防火墙规则集的基本要素。</para>
|
||||
|
||||
<warning>
|
||||
<para>当对防火墙规则进行操作时, 应该
|
||||
<para>当对防火墙规则进行操作时, 应
|
||||
<emphasis>谨慎行事</emphasis>。 某些配置可能会
|
||||
<emphasis>将您反锁在</emphasis> 服务器外面。
|
||||
安全起见, 您可以考虑在第一次进行防火墙配置时在本地控制台上,
|
||||
而不是远程, 例如通过
|
||||
<application>ssh</application> 来进行。</para>
|
||||
保险起见, 您可以考虑在第一次进行防火墙配置时在本地控制台上,
|
||||
而不是远程, 如通过
|
||||
<application>ssh</application> 来进行。</para>
|
||||
</warning>
|
||||
</sect2>
|
||||
|
||||
|
@ -1324,11 +1326,11 @@ sh /etc/ipf.rules.script</programlisting>
|
|||
|
||||
<para>如果记录的包的端口号并不是您所知道的,
|
||||
可以在 <filename>/etc/services</filename> 或 <ulink
|
||||
url="http://www.securitystats.com/tools/portsearch.php"></ulink>
|
||||
url="http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers"></ulink>
|
||||
了解端口号通常的用途。</para>
|
||||
|
||||
<para>参考下面的网页, 了解木马使用的端口:<ulink
|
||||
url="http://www.simovits.com/trojans/trojans.html"></ulink>。</para>
|
||||
<para>参考下面的网页, 了解木马使用的端口: <ulink
|
||||
url="http://www.sans.org/security-resources/idfaq/oddports.php"></ulink>。</para>
|
||||
|
||||
<para>下面是我在自己的系统中使用的完整的, 非常安全的
|
||||
<literal>明示允许</literal> 防火墙规则集。 直接使用这个规则集不会给您造成问题,
|
||||
|
@ -2496,10 +2498,10 @@ ks="keep-state" # just too lazy to key this each time
|
|||
无效的包应被丢弃和消失。 这样, 攻击者便无法知道包是否到达了您的系统。
|
||||
攻击者对系统了解的越少, 其攻击的难度也就越大。 如果不知道端口号,
|
||||
可以查阅 <filename>/etc/services/</filename> 或到 <ulink
|
||||
url="http://www.securitystats.com/tools/portsearch.php"></ulink>
|
||||
url="http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers"></ulink>
|
||||
并查找一下端口号, 以了解其用途。 另外,
|
||||
您也可以在这个网页上了解常见木马所使用的端口: <ulink
|
||||
url="http://www.simovits.com/trojans/trojans.html"></ulink>。</para>
|
||||
url="http://www.sans.org/security-resources/idfaq/oddports.php"></ulink>。</para>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
|
@ -2571,7 +2573,7 @@ pif="dc0" # public interface name of NIC
|
|||
# Interface facing Public Internet (Outbound Section)
|
||||
# Interrogate session start requests originating from behind the
|
||||
# firewall on the private network or from this gateway server
|
||||
# destine for the public Internet.
|
||||
# destined for the public Internet.
|
||||
#################################################################
|
||||
|
||||
# Allow out access to my ISP's Domain name server.
|
||||
|
@ -2609,7 +2611,7 @@ pif="dc0" # public interface name of NIC
|
|||
# Allow out Time
|
||||
$cmd 00260 allow tcp from any to any 37 out via $pif setup keep-state
|
||||
|
||||
# Allow out nntp news (i.e. news groups)
|
||||
# Allow out nntp news (i.e., news groups)
|
||||
$cmd 00270 allow tcp from any to any 119 out via $pif setup keep-state
|
||||
|
||||
# Allow out secure FTP, Telnet, and SCP
|
||||
|
@ -2899,7 +2901,7 @@ pif="rl0" # public interface name of NIC
|
|||
# Allow out Time
|
||||
$cmd 090 $skip tcp from any to any 37 out via $pif setup keep-state
|
||||
|
||||
# Allow out nntp news (i.e. news groups)
|
||||
# Allow out nntp news (i.e., news groups)
|
||||
$cmd 100 $skip tcp from any to any 119 out via $pif setup keep-state
|
||||
|
||||
# Allow out secure FTP, Telnet, and SCP
|
||||
|
|
Loading…
Reference in a new issue