Alan Milligan writes:

Hi,

I did not get a response to my Mail::SpamAssassin::AuthCourier posting
whereby I raised a concern about the lack of UID information being
returned from authdaemond for getpwnam-based authentications.

Maybe that's because this does not appear to be true.

# ./authtest mrsam
Authenticated: module authdaemon
Home directory: /home/mrsam
UID/GID: 501/100
AUTHADDR=mrsam
AUTHFULLNAME=Mr. Sam
[EMAIL PROTECTED] authlib]# ./authtest mrsam mypassword
Authenticated: module authdaemon
Home directory: /home/mrsam
UID/GID: 501/100
AUTHADDR=mrsam
AUTHFULLNAME=Mr. Sam

Upon closer inspection, the reason for this appears to be that
authinfo->sysuserid is deliberately left unset.

While this is not an issue for Courier per se, the implicitness of the
UID setting in later processing means authdaemond is not terribly usable
in non-Courier contexts such as here where SpamAssassin is retrieving
virtual account information.

The following patches ensure that the UID field is primed for *all*
authentication mechanisms.

The following patch doesn't do anything. Actually, the only thing it does is that it initializes auxiliary groups, on systems that include individual accounts into multiple groups.

Which is something that authdaemon (nor Courier) doesn't care about, so even with that patch the auxilary group information will not be received via the authdaemon socket.



Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to