From 46e83cce55f45160bf6b3fb3270389cef17a9694 Mon Sep 17 00:00:00 2001 From: Badlop Date: Thu, 24 Jul 2008 18:21:40 +0000 Subject: * doc/guide.tex: Include example PAM configuration file ejabberd.pam (thanks to Evgeniy Khramtsov)(EJAB-704) * doc/guide.html: Likewise SVN Revision: 1489 --- doc/guide.html | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'doc/guide.html') diff --git a/doc/guide.html b/doc/guide.html index c67f1210..af65e7ea 100644 --- a/doc/guide.html +++ b/doc/guide.html @@ -976,8 +976,12 @@ version, you can kill(1) epam process periodically to reduce i consumption: ejabberd will restart this process immediately.
  • 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 ejabberd.pam shows how to turn off delays in -pam_unix.so module. It is not a ready to use configuration file: you must use it +You can create a configuration file ejabberd.pam. +This example shows how to turn off delays in pam_unix.so module: +
    #%PAM-1.0
+auth        sufficient  pam_unix.so likeauth nullok nodelay
+account     sufficient  pam_unix.so
+
    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 -- cgit v1.2.3