summaryrefslogtreecommitdiff
path: root/UPGRADING
diff options
context:
space:
mode:
authorDamien Miller <djm@mindrot.org>1999-12-26 14:04:33 +1100
committerDamien Miller <djm@mindrot.org>1999-12-26 14:04:33 +1100
commitd49621ea530ce976a17ba043eedba137c60bc10a (patch)
tree70d7e18e93018564fc595d6e4593f12ffaa2ebe1 /UPGRADING
parent780b376a372f4eefb4c7cda8a8dd2e15cc390c19 (diff)
- Disable logging of PAM success and failures, PAM is verbose enough.
Unfortunatly there is currently no way to disable auth failure messages. Mention this in UPGRADING file and sent message to PAM developers
Diffstat (limited to 'UPGRADING')
-rw-r--r--UPGRADING8
1 files changed, 8 insertions, 0 deletions
diff --git a/UPGRADING b/UPGRADING
index f9732cf5..854bd229 100644
--- a/UPGRADING
+++ b/UPGRADING
@@ -45,3 +45,11 @@ rid yourself of these message, edit you known_hosts files and replace
the incorrect key length (usually "1024") with the correct key length
(usually "1023").
+5. Spurious PAM authentication messages in logfiles
+
+OpenSSH will generate spurious authentication failures at every login,
+similar to "authentication failure; (uid=0) -> root for sshd service".
+These are generated because OpenSSH first tries to determine whether a
+user needs authentication to login (e.g. empty password). Unfortunatly
+PAM likes to log all authentication events, this one included.
+