Lorenzo,
I've linked your patch in the RHEL bug I opened a while ago,
but I'm not sure if they'll incorporate it... we might need to
forward it to RH support instead of going through bugzilla.
I don't suppose you want to extend saslauthd's logging
capability to create a limited log (for failed auth) even without the
debug flag... do you? For example, logging something like this into
syslog:
saslauthd [PID]: failed AUTH login for user <user> from <host> [IP]
This is less verbose than the debug-level log (and would be
logged only on auth failure, not success), and it would also create
the appropriate fail-log even when not using pam or other plugins
(i.e. even if saslauthd is used on its own).
If you're up for it, I think such a log function would be
highly appreciated (by me, at least!). Ideally, it would be enabled
by default, but could be disabled by using a -quiet flag on launch
(just like the debug-level logging can be manually enabled with
-verbose).
Thanks. =)
--- Amir
At 5:31 PM +0200 05/24/2011, Lorenzo M. Catucci wrote:
Just to let all know that the ...2.1.23 patch is working well on an old
production system of ours,
with a patched 2.1.22 version.
Thank you all, yours
lorenzo
--
--- Amir
3Phase Internet Solutions
http://www.3phase.com
