Yes that is the correct issue occurring effectively pam never sees the rhost
data from sendmail which can be seen in the auth log.
Jan 25 16:56:12 uvt-yakkety saslauthd[3020]: pam_unix(smtp:auth):
authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=
user=powersj
I did some more
Hi, Thanks for the reply.
First of I will say that everything to reproduce this is a default
configuration for saslauthd. You simply have to install it. The next
part would be to install any of the other default like imapd(no
configuration required) or sendmail(which does need configured). Or any
Public bug reported:
When using sasl2-bin and saslauthd it will fail to work correctly with pam.
The first major problem is that that it will fail to report the rhost
address in the log which means auth failures cannot be policed and no
useful data (the ip address) is reported to the log file.
I can confirm that I had the same problem with the kernel. This was due to it
being a vm in a xen environment which was booting from the host kernel which
was why it was not upgraded.
After upgrading the kernel and apt to the most recent version all is
working normally again.
--
You received
What I think that might be useful is being able to get a list of open file
descriptors of the process and the point of the execve is being called. I
suspect that its failing because it doesn't have access to something so it get
an EPERM
The only reference to execve failing in the man page is
5 matches
Mail list logo
