path: root/doc/sag/Linux-PAM_SAG.xml
diff options
Diffstat (limited to 'doc/sag/Linux-PAM_SAG.xml')
1 files changed, 13 insertions, 7 deletions
diff --git a/doc/sag/Linux-PAM_SAG.xml b/doc/sag/Linux-PAM_SAG.xml
index eef2b71f..f608512e 100644
--- a/doc/sag/Linux-PAM_SAG.xml
+++ b/doc/sag/Linux-PAM_SAG.xml
@@ -16,7 +16,7 @@
- <releaseinfo>Version 1.0, 3. April 2008</releaseinfo>
+ <releaseinfo>Version 1.1, 16. June 2009</releaseinfo>
This manual documents what a system-administrator needs to know about
@@ -27,7 +27,7 @@
- <chapter id='sag-introductoin'>
+ <chapter id='sag-introduction'>
<emphasis remap='B'>Linux-PAM</emphasis> (Pluggable Authentication
@@ -85,7 +85,7 @@
here for locating these files are those of the relevant RFC (RFC-86.0,
see <link linkend="sag-see-also">bibliography"</link>). If you are
using a distribution of Linux (or some other operating system) that
- supports PAM but chooses to distribute these files in a diferent way
+ supports PAM but chooses to distribute these files in a different way
you should be careful when copying examples directly from the text.
@@ -210,7 +210,7 @@
If a program is going to use PAM, then it has to have PAM
functions explicitly coded into the program. If you have
access to the source code you can add the appropriate PAM
- functions. If you do not have accessto the source code, and
+ functions. If you do not have access to the source code, and
the binary does not have the PAM functions included, then
it is not possible to use PAM.
@@ -227,7 +227,7 @@
xpointer='xpointer(//section[@id = "pam.conf-syntax"]/*)' />
- <section id='sag-configuratin-dirctory'>
+ <section id='sag-configuration-directory'>
<title>Directory based configuration</title>
<xi:include xmlns:xi=""
@@ -333,7 +333,7 @@ session required
<chapter id='sag-security-issues'>
<title>Security issues</title>
- <section id='sag-scurity-issues-wrong'>
+ <section id='sag-security-issues-wrong'>
<title>If something goes wrong</title>
<emphasis remap='B'>Linux-PAM</emphasis> has the potential
@@ -341,7 +341,7 @@ session required
choose to have no security or absolute security (no access
permitted). In general, <emphasis remap='B'>Linux-PAM</emphasis>
errs towards the latter. Any number of configuration errors
- can dissable access to your system partially, or completely.
+ can disable access to your system partially, or completely.
The most dramatic problem that is likely to be encountered when
@@ -443,6 +443,8 @@ session required
<xi:include xmlns:xi=""
<xi:include xmlns:xi=""
+ href="pam_pwhistory.xml"/>
+ <xi:include xmlns:xi=""
<xi:include xmlns:xi=""
@@ -457,8 +459,12 @@ session required
<xi:include xmlns:xi=""
<xi:include xmlns:xi=""
+ href="pam_tally2.xml"/>
+ <xi:include xmlns:xi=""
<xi:include xmlns:xi=""
+ href="pam_timestamp.xml"/>
+ <xi:include xmlns:xi=""
<xi:include xmlns:xi=""