diff options
Diffstat (limited to 'en_US.ISO8859-1/books/handbook/security/chapter.sgml')
| -rw-r--r-- | en_US.ISO8859-1/books/handbook/security/chapter.sgml | 44 |
1 files changed, 22 insertions, 22 deletions
diff --git a/en_US.ISO8859-1/books/handbook/security/chapter.sgml b/en_US.ISO8859-1/books/handbook/security/chapter.sgml index 1233c5254e..8d77b2cf36 100644 --- a/en_US.ISO8859-1/books/handbook/security/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/security/chapter.sgml @@ -5396,14 +5396,14 @@ drwxr-xr-x 2 robert robert 512 Nov 10 11:54 public_html</programlisting> <quote>Security Advisories</quote>. These advisories are usually mailed to the security lists and noted in the Errata only after the appropriate releases have been patched. This section - will work to explain what an advisory is, how to understand it, + will work to explain what an advisory is, how to understand them, and what measures to take in order to patch a system.</para> <sect2> <title>What does an advisory look like?</title> <para>The &os; security advisories look similar to the one below, - taken from the &a.security-notifications.name; mailing list.</para> + taken from the security mailing list.</para> <programlisting>============================================================================= &os;-SA-XX:XX.UTIL Security Advisory @@ -5456,33 +5456,33 @@ VII. References<co id="co-ref"></programlisting> <calloutlist> <callout arearefs="co-topic"> - <para>The <literal>Topic</literal> field indicates exactly what the problem is. + <para>The topic field indicates exactly what the problem is. It is basically an introduction to the current security advisory and notes the utility with the vulnerability.</para> </callout> <callout arearefs="co-category"> - <para>The <literal>Category</literal> refers to the affected part of the system - which may be one of <literal>core</literal>, <literal>contrib</literal>, or <literal>ports</literal>. The <literal>core</literal> + <para>The Category refers to the affected part of the system + which may be one of core, contrib, or ports. The core category means that the vulnerability affects a core - component of the &os; operating system. The <literal>contrib</literal> + component of the &os; operating system. The contrib category means that the vulnerability affects software contributed to the &os; Project, such as - <application>sendmail</application>. Finally the <literal>ports</literal> + <application>Sendmail</application>. Finally the ports category indicates that the vulnerability affects add on software available as part of the ports collection.</para> </callout> <callout arearefs="co-module"> - <para>The <literal>Module</literal> field refers to the component location, for - instance <literal>sys</literal>. In this example, we see that the module, - <literal>sys</literal>, is affected; therefore, this vulnerability + <para>The Module field refers to the component location, for + instance sys. In this example, we see that the module, + sys, is affected; therefore, this vulnerability affects a component used within the kernel.</para> </callout> <callout arearefs="co-announce"> - <para>The <literal>Announced</literal> field reflects the date said security + <para>The Announced field reflects the date said security advisory was published, or announced to the world. This means that the security team has verified that the problem does exist and that a patch has been committed to the &os; @@ -5490,13 +5490,13 @@ VII. References<co id="co-ref"></programlisting> </callout> <callout arearefs="co-credit"> - <para>The <literal>Credits</literal> field gives credit to the individual or + <para>The Credits field gives credit to the individual or organization who noticed the vulnerability and reported it.</para> </callout> <callout arearefs="co-affects"> - <para>The <literal>Affects</literal> field explains which releases of &os; are + <para>The Affects field explains which releases of &os; are affected by this vulnerability. For the kernel, a quick look over the output from <command>ident</command> on the affected files will help in determining the revision. @@ -5507,32 +5507,32 @@ VII. References<co id="co-ref"></programlisting> </callout> <callout arearefs="co-corrected"> - <para>The <literal>Corrected</literal> field indicates the date, time, time + <para>The Corrected field indicates the date, time, time offset, and release that was corrected.</para> </callout> <callout arearefs="co-only"> - <para>The <literal>&os; only</literal> field indicates whether this vulnerability + <para>The &os; only field indicates whether this vulnerability affects just &os;, or if it affects other operating systems as well.</para> </callout> <callout arearefs="co-backround"> - <para>The <literal>Background</literal> field gives information on exactly what + <para>The background field gives information on exactly what the affected utility is. Most of the time this is why the utility exists in &os;, what it is used for, and a bit of information on how the utility came to be.</para> </callout> <callout arearefs="co-descript"> - <para>The <literal>Problem Description</literal> field explains the security hole + <para>The Problem Description field explains the security hole in depth. This can include information on flawed code, or even how the utility could be maliciously used to open a security hole.</para> </callout> <callout arearefs="co-impact"> - <para>The <literal>Impact</literal> field describes what type of impact the + <para>The Impact field describes what type of impact the problem could have on a system. For example, this could be anything from a denial of service attack, to extra privileges available to users, or even giving the attacker @@ -5540,7 +5540,7 @@ VII. References<co id="co-ref"></programlisting> </callout> <callout arearefs="co-workaround"> - <para>The <literal>Workaround</literal> field offers a feasible workaround to + <para>The Workaround field offers a feasible workaround to system administrators who may be incapable of upgrading the system. This may be due to time constraints, network availability, or a slew of other reasons. Regardless, @@ -5550,21 +5550,21 @@ VII. References<co id="co-ref"></programlisting> </callout> <callout arearefs="co-solution"> - <para>The <literal>Solution</literal> field offers instructions on patching the + <para>The Solution field offers instructions on patching the affected system. This is a step by step tested and verified method for getting a system patched and working securely.</para> </callout> <callout arearefs="co-details"> - <para>The <literal>Correction Details</literal> field displays the + <para>The Correction Details field displays the <acronym>CVS</acronym> branch or release name with the periods changed to underscore characters. It also shows the revision number of the affected files within each branch.</para> <callout arearefs="co-ref"> - <para>The <literal>References</literal> field usually offers sources of other + <para>The References field usually offers sources of other information. This can included web <acronym>URL</acronym>s, books, mailing lists, and newsgroups.</para> </callout> |