diff options
author | Damien Miller <djm@mindrot.org> | 1999-12-26 14:04:33 +1100 |
---|---|---|
committer | Damien Miller <djm@mindrot.org> | 1999-12-26 14:04:33 +1100 |
commit | d49621ea530ce976a17ba043eedba137c60bc10a (patch) | |
tree | 70d7e18e93018564fc595d6e4593f12ffaa2ebe1 /UPGRADING | |
parent | 780b376a372f4eefb4c7cda8a8dd2e15cc390c19 (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-- | UPGRADING | 8 |
1 files changed, 8 insertions, 0 deletions
@@ -45,3 +45,11 @@ rid yourself of these message, edit you known_hosts files and replace | |||
45 | the incorrect key length (usually "1024") with the correct key length | 45 | the incorrect key length (usually "1024") with the correct key length |
46 | (usually "1023"). | 46 | (usually "1023"). |
47 | 47 | ||
48 | 5. Spurious PAM authentication messages in logfiles | ||
49 | |||
50 | OpenSSH will generate spurious authentication failures at every login, | ||
51 | similar to "authentication failure; (uid=0) -> root for sshd service". | ||
52 | These are generated because OpenSSH first tries to determine whether a | ||
53 | user needs authentication to login (e.g. empty password). Unfortunatly | ||
54 | PAM likes to log all authentication events, this one included. | ||
55 | |||