Hmm, I guess PAM with mysql won't really do the same thing, because it can't supply the homedir/uid/gid etc. If you use pam, the daemon will expect to find those things in /etc/passwd which defeats using virtual users in the first place.
Going to apply the contrib mysql patch now and see how that goes :)
Thanks, Skye
Word on the street is Skye Poier said:
Hi again,
I'm on Freebsd 4.x and instead of using the mysql patch, it seems like it would be easier to just use "auth_passdb = pam *" with the pam_mysql drop-in.
I'm not really a pam.conf writing expert though. Here's what it currently contains (works for /etc/passwd users)
imap auth required pam_unix.so imap account required pam_unix.so try_first_pass imap session required pam_deny.so
How would I set it up so that it first checks to see if the user is in /etc/passwd (as above) and then checks pam_mysql.so?
Example from the pam_mysql readme:
auth optional pam_mysql.so user=root passwd=password account required pam_mysql.so user=root passwd=password
Is anyone else using this setup? Any disadvantages?
Thanks, Skye