Marc Haber writes: > I am now trying to adapt that module to the new authentication code. > If I understand correctly, I am expected to change the code in > preauthcustom.c to do what I need. If this the recommended way of > creating a custom auth module? Or is it a better idea t make a copy of > the authcustom, creating an authscript module? How do I adapt the > build process to have the new module automatically built?
It's easier to simply modify authcustom. Creating a new module requires some hairy changes to the Makefile. > Also, the new code asks for a function that simply verifies if the > user account in question exists. Since I am validating against a > background POP3 system, I can't say if an account exists. The only > thing I can do is verifying if a given password belongs to a given > account. If either password or account is wrong, I get the same error > state, so I can't say if this is the wrong password for an existing > account. What is my authpre function to return in this case? Should I > always return "account exists"? That's a problem. Not only does the function need to return an indication if the account exists, but also what it's home directory and uid/gid are. -- Sam _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
