saslauthd SASL_IPREMOTEPORT -> PAM_RHOST

[Amir 'CG' Caspi]

Hi Sean,

	I'm digging through some old emails since I'm trying to 
finally get this stuff to work.  RH seems to be making a little 
progress in implementing Lorenzo's patch to get saslauthd to log 
rhost via PAM, but I'm curious about your suggestion here... what did 
you mean by changing the syslog to a different device, and getting 
sasl to log the info?  Would this require not using pam anymore?  I'm 
not all that familiar with the guts of sasl, pam, etc. so additional 
details would be helpful.

Thanks.
						--- Amir

At 3:18 PM -0400 05/23/2011, omalleys at msu.edu wrote:
>Quoting Amir 'CG' Caspi <cepheid at 3phase.com>:
>
>>	Of course, the rhost really is the most important piece 
>>anyway, since that's what I need for firewalling.  I can live 
>>without the bad username, since apparently it's not logged anyway 
>>even with other services.
>
>
>in the saslauthd code, I think there is a section that allows -sasl- 
>to log the information you want. It would probably be easier to 
>modify it there.
>
>IE remove the debug flag requirement and change the syslog to the 
>device you want.