* doc/guide.tex: Include example PAM configuration file

ejabberd.pam (thanks to Evgeniy Khramtsov)(EJAB-704)
* doc/guide.html: Likewise

SVN Revision: 1489

diff --git a/ChangeLog b/ChangeLog
index ad02d16ee4a3a7fb4a97e98e49d00ffeeea73b10..4a6bf0371f6294d397b300a1d274a61e65c911ec 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,9 @@
 2008-07-24  Badlop  <badlop@process-one.net>
 
+       * doc/guide.tex: Include example PAM configuration file
+       ejabberd.pam (thanks to Evgeniy Khramtsov)(EJAB-704)
+       * doc/guide.html: Likewise
+
        * src/mod_proxy65/mod_proxy65_lib.erl: Send protocol compliant
        SOCKS5 reply; this breaks support of uncompliant Psi<0.10 (thanks
        to Felix Geyer)(EJAB-632)

diff --git a/doc/guide.html b/doc/guide.html
index 3dc534742f4651a0ea97cd6aa2367a1d0efe5368..735efca6428fd14b75d914f6226471658e9e3242 100644 (file)
--- a/doc/guide.html
+++ b/doc/guide.html
@@ -959,8 +959,12 @@ version, you can <TT>kill(1)</TT> <TT>epam</TT> process periodically to reduce i
 consumption: <TT>ejabberd</TT> will restart this process immediately.
 </LI><LI CLASS="li-itemize"><TT>epam</TT> program tries to turn off delays on authentication failures.
 However, some PAM modules ignore this behavior and rely on their own configuration options.
-The example configuration file <TT>ejabberd.pam</TT> shows how to turn off delays in
-<TT>pam_unix.so</TT> module. It is not a ready to use configuration file: you must use it
+You can create a configuration file <TT>ejabberd.pam</TT>.
+This example shows how to turn off delays in <TT>pam_unix.so</TT> module:
+<PRE CLASS="verbatim">#%PAM-1.0
+auth        sufficient  pam_unix.so likeauth nullok nodelay
+account     sufficient  pam_unix.so
+</PRE>That is not a ready to use configuration file: you must use it
 as a hint when building your own PAM configuration instead. Note that if you want to disable
 delays on authentication failures in the PAM configuration file, you have to restrict access
 to this file, so a malicious user can&#X2019;t use your configuration to perform brute-force

diff --git a/doc/guide.tex b/doc/guide.tex
index 2432e7affd234d0768aa53f9d973306f9e15cc44..e1b00877a2b2897ad8a13e478a2744b719f11424 100644 (file)
--- a/doc/guide.tex
+++ b/doc/guide.tex
@@ -1140,8 +1140,14 @@ version, you can \term{kill(1)} \term{epam} process periodically to reduce its m
 consumption: \ejabberd{} will restart this process immediately.
 \item \term{epam} program tries to turn off delays on authentication failures.
 However, some PAM modules ignore this behavior and rely on their own configuration options.
-The example configuration file \term{ejabberd.pam} shows how to turn off delays in
-\term{pam\_unix.so} module. It is not a ready to use configuration file: you must use it
+You can create a configuration file \term{ejabberd.pam}.
+This example shows how to turn off delays in \term{pam\_unix.so} module:
+\begin{verbatim}
+#%PAM-1.0
+auth        sufficient  pam_unix.so likeauth nullok nodelay
+account     sufficient  pam_unix.so
+\end{verbatim}
+That is not a ready to use configuration file: you must use it
 as a hint when building your own PAM configuration instead. Note that if you want to disable
 delays on authentication failures in the PAM configuration file, you have to restrict access
 to this file, so a malicious user can't use your configuration to perform brute-force