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

Unabbreviate "versus", correct "build" to "built", add comma to i.e.,

Browse source 
Insert spaces before callouts to improve readability.
This commit is contained in:
Warren Block 2012-01-29 02:54:43 +00:00
parent 9058d04c74
commit d59c6a518d
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=38339
1 changed files with 22 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -295,7 +295,7 @@
</indexterm> </indexterm>
<note> <note>
<title>Command vs. Protocol</title> <title>Command Versus Protocol</title>
<para>Throughout this document, we will use <para>Throughout this document, we will use
<application>bold</application> text to refer to an <application>bold</application> text to refer to an
@ -650,7 +650,7 @@
<note> <note>
<para>Bumping the secure level to 1 or higher may cause a few <para>Bumping the secure level to 1 or higher may cause a few
problems to X11 (access to <filename>/dev/io</filename> will problems to X11 (access to <filename>/dev/io</filename> will
be blocked), or to the installation of &os; build from be blocked), or to the installation of &os; built from
source (the <maketarget>installworld</maketarget> part of source (the <maketarget>installworld</maketarget> part of
the process needs to temporarily reset the append-only and the process needs to temporarily reset the append-only and
immutable flags of some files), and in a few other cases. immutable flags of some files), and in a few other cases.
@ -669,8 +669,8 @@
<para>If the kernel's secure level is raised to 1 or a higher <para>If the kernel's secure level is raised to 1 or a higher
value, it may be useful to set the <literal>schg</literal> value, it may be useful to set the <literal>schg</literal>
flag on critical startup binaries, directories, and script flag on critical startup binaries, directories, and script
files (i.e. everything that gets run up to the point where the files (i.e., everything that gets run up to the point where
securelevel is set). This might be overdoing it, and the securelevel is set). This might be overdoing it, and
upgrading the system is much more difficult when it operates upgrading the system is much more difficult when it operates
at a high secure level. A less strict compromise is to run at a high secure level. A less strict compromise is to run
the system at a higher secure level but skip setting the the system at a higher secure level but skip setting the
@ -828,7 +828,7 @@
</orderedlist> </orderedlist>
<para>A common DoS attack scenario is attacking a forking server <para>A common DoS attack scenario is attacking a forking server
and making it spawning so many child processes that the host and making it spawn so many child processes that the host
system eventually runs out of memory, file descriptors, etc. system eventually runs out of memory, file descriptors, etc.
and then grinds to a halt. <application>inetd</application> and then grinds to a halt. <application>inetd</application>
(see &man.inetd.8;) has several options to limit this sort of (see &man.inetd.8;) has several options to limit this sort of
@ -1528,7 +1528,7 @@ ALL : ALL \
<warning> <warning>
<para>It may be possible to launch a denial of service <para>It may be possible to launch a denial of service
attack on the server if an attacker, or group of attackers attack on the server if an attacker, or group of attackers,
could flood these daemons with connection requests.</para> could flood these daemons with connection requests.</para>
</warning> </warning>
@ -1554,7 +1554,7 @@ ALL : .example.com \
<filename>/var/log/connections.log</filename> file.</para> <filename>/var/log/connections.log</filename> file.</para>
<para>Aside from the already explained substitution characters <para>Aside from the already explained substitution characters
above, e.g. <literal>%a</literal>, a few others exist. See above, e.g., <literal>%a</literal>, a few others exist. See
the &man.hosts.access.5; manual page for the complete the &man.hosts.access.5; manual page for the complete
list.</para> list.</para>
</sect3> </sect3>
@ -3897,13 +3897,13 @@ You are advised to update or deinstall the affected package(s) immediately.</pro
FreeBSD-SA-XX:XX.UTIL Security Advisory FreeBSD-SA-XX:XX.UTIL Security Advisory
The FreeBSD Project The FreeBSD Project
Topic: denial of service due to some problem<co id="co-topic"> Topic: denial of service due to some problem <co id="co-topic">
Category: core<co id="co-category"> Category: core <co id="co-category">
Module: sys<co id="co-module"> Module: sys <co id="co-module">
Announced: 2003-09-23<co id="co-announce"> Announced: 2003-09-23 <co id="co-announce">
Credits: Person<co id="co-credit"> Credits: Person <co id="co-credit">
Affects: All releases of &os;<co id="co-affects"> Affects: All releases of &os; <co id="co-affects">
&os; 4-STABLE prior to the correction date &os; 4-STABLE prior to the correction date
Corrected: 2003-09-23 16:42:59 UTC (RELENG_4, 4.9-PRERELEASE) Corrected: 2003-09-23 16:42:59 UTC (RELENG_4, 4.9-PRERELEASE)
2003-09-23 20:08:42 UTC (RELENG_5_1, 5.1-RELEASE-p6) 2003-09-23 20:08:42 UTC (RELENG_5_1, 5.1-RELEASE-p6)
@ -3913,33 +3913,33 @@ Corrected: 2003-09-23 16:42:59 UTC (RELENG_4, 4.9-PRERELEASE)
2003-09-23 16:49:46 UTC (RELENG_4_6, 4.6-RELEASE-p21) 2003-09-23 16:49:46 UTC (RELENG_4_6, 4.6-RELEASE-p21)
2003-09-23 16:51:24 UTC (RELENG_4_5, 4.5-RELEASE-p33) 2003-09-23 16:51:24 UTC (RELENG_4_5, 4.5-RELEASE-p33)
2003-09-23 16:52:45 UTC (RELENG_4_4, 4.4-RELEASE-p43) 2003-09-23 16:52:45 UTC (RELENG_4_4, 4.4-RELEASE-p43)
2003-09-23 16:54:39 UTC (RELENG_4_3, 4.3-RELEASE-p39)<co id="co-corrected"> 2003-09-23 16:54:39 UTC (RELENG_4_3, 4.3-RELEASE-p39) <co id="co-corrected">
<acronym>CVE</acronym> Name: CVE-XXXX-XXXX<co id="co-cve"> <acronym>CVE</acronym> Name: CVE-XXXX-XXXX <co id="co-cve">
For general information regarding FreeBSD Security Advisories, For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the including descriptions of the fields above, security branches, and the
following sections, please visit following sections, please visit
http://www.FreeBSD.org/security/. http://www.FreeBSD.org/security/.
I. Background<co id="co-backround"> I. Background <co id="co-backround">
II. Problem Description<co id="co-descript"> II. Problem Description <co id="co-descript">
III. Impact<co id="co-impact"> III. Impact <co id="co-impact">
IV. Workaround<co id="co-workaround"> IV. Workaround <co id="co-workaround">
V. Solution<co id="co-solution"> V. Solution <co id="co-solution">
VI. Correction details<co id="co-details"> VI. Correction details <co id="co-details">
VII. References<co id="co-ref"></programlisting> VII. References <co id="co-ref"></programlisting>
<calloutlist> <calloutlist>
<callout arearefs="co-topic"> <callout arearefs="co-topic">