Noel Burton-Krahn writes:
There's a reason for that weird forking mechanism. The big comment that you removed explains what the reason is. There are some major memory leaks in PAM. Or at least there were. The code that runs in the parent context is also used in authdaemon, as a persistent process. If the parent carries out the PAM calls, the memory leaks will quickly accumulate. That's why the PAM calls must occur in the child process, and the parent process only receives the indication if the authentication succeeded.1. authpam didn't pass on the environment stored in pam_getenvlist(). Now it does.2. authpam used a weird forking mechanism so a child process can end the pam session. One process does pam, the other returns authentication success,
That's why your changes will not work anywhere except your particular environment/configuration.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
