-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
|> Which part of (B) have I missed? I need to see the UID down this |> socket!! | | |The part that instead of UID/GID authdaemon may return a single >username |instead, in which case the uid/gid comes from getpasswd() on the given |username.
In the interests of consistency of API across authentication mechanisms, and to avoid confusion in other esoteric usages of authdaemond why not just accept my patch??
Cheers, Alan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.3.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org Comment:
iD8DBQE/7ED/CfroLk4EZpkRAgnBAKCn1fCJcYEKRKIKTU7ssEakvbjkqwCeMWRw /ryoeADfG/CbCXsuTGT8VGc= =3uFQ -----END PGP SIGNATURE-----
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
