swift       05/06/08 19:19:07

  Modified:    xml/htdocs/doc/en/handbook/draft pax-utils.xml
  Log:
  Fix spelling mistakes

Revision  Changes    Path
1.2       +18 -18    xml/htdocs/doc/en/handbook/draft/pax-utils.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/pax-utils.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/pax-utils.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/handbook/draft/pax-utils.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo

Index: pax-utils.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/pax-utils.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- pax-utils.xml       8 Jun 2005 19:09:16 -0000       1.1
+++ pax-utils.xml       8 Jun 2005 19:19:07 -0000       1.2
@@ -1,11 +1,11 @@
 <?xml version='1.0' encoding="UTF-8"?>
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/pax-utils.xml,v 1.1 
2005/06/08 19:09:16 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/pax-utils.xml,v 1.2 
2005/06/08 19:19:07 swift Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
-<guide link="/doc/en/pax-utils.xml">
-<title>Gentoo Pax Utils</title>
+<guide link="/doc/en/handbook/draft/pax-utils.xml">
+<title>Gentoo Pax Utilities</title>
 
 <author title="Author">
   <mail link="[EMAIL PROTECTED]">Sven Vermeulen</mail>
@@ -32,15 +32,15 @@
 <body>
 
 <p>
-The security of a system goes beyond firewalling and good service
-configurations. The binaries you run, the libraries you load, might also be
-vulnerable against attacks. Although the exact vulnerabilities are not known
-until they are discovered, there are ways to prevent them from happening.
+The security of a system goes beyond setting up a decent firewall and good 
+service configurations. The binaries you run, the libraries you load, might 
+also be vulnerable against attacks. Although the exact vulnerabilities are not 
+known until they are discovered, there are ways to prevent them from happening.
 </p>
 
 <p>
-One possible attack vector is to make advantage of writeable <e>and</e>
-executable segments in a program or library, allowing malafide users to run
+One possible attack vector is to make advantage of writable <e>and</e>
+executable segments in a program or library, allowing malicious users to run
 their own code using the vulnerable application or library.
 </p>
 
@@ -48,7 +48,7 @@
 This guide will inform you how to use the <c>pax-utils</c> package to find
 and identify problematic binaries. We will also cover the use of <c>pspax</c> 
(a
 tool to view PAX-specific capabilities) and <c>dumpelf</c> (a tool that prints
-out a C structure containing a workeable copy of a given object).
+out a C structure containing a workable copy of a given object).
 </p>
 
 <p>
@@ -91,12 +91,12 @@
   <li>
     The <e>Program Header</e> informs the system how to create a process from
     the binary file. It is actually a table consisting of entries for each
-    segment in the program. Each entry contains the type, addresses (fysical 
and
-    virtual), size, ...
+    segment in the program. Each entry contains the type, addresses (physical 
+    and virtual), size, ...
   </li>
   <li>
     The <e>Section Header</e> is a table consisting of entries for each section
-    in the program. Each entry contains the name, type, size, ... and also
+    in the program. Each entry contains the name, type, size, ... and
     <e>what</e> information the section holds.
   </li>
   <li>
@@ -284,12 +284,12 @@
 <tr>
   <ti>-f [arg]</ti>
   <ti>--from [arg]</ti>
-  <ti>Read input from a given file name instead of stdin</ti>
+  <ti>Read input from a given file name instead of standard input</ti>
 </tr>
 <tr>
   <ti>-o [arg]</ti>
   <ti>--file [arg]</ti>
-  <ti>Write output to a given file instead of stdout</ti>
+  <ti>Write output to a given file instead of standard output</ti>
 </tr>
 <tr>
   <ti>-B</ti>
@@ -309,7 +309,7 @@
 </table>
 
 <p>
-The format specifiers for the <c>-F</c> option are fiven in the following 
table.
+The format specifiers for the <c>-F</c> option are given in the following 
table.
 Prefix each specifier with <c>%</c> (verbose) or <c>#</c> (silent) accordingly.
 </p>
 
@@ -386,7 +386,7 @@
 <p>
 A text relocation is a relocation in the text segment. Since text segments
 contain executable code, system administrators might prefer not to have these
-segments writeable. This is perfectly possible, but since text relocations
+segments writable. This is perfectly possible, but since text relocations
 actually write in the text segment, it is not always feasible. 
 </p>
 
@@ -435,7 +435,7 @@
 
 <p>
 If we want to scan all executables in the current working directory, PATH
-environment and library paths and report those who have a writeable and
+environment and library paths and report those who have a writable and
 executable PT_LOAD or PT_GNU_STACK marking, you could use the following 
command:
 </p>
 



-- 
[email protected] mailing list

Reply via email to