Johnny Lam writes:
Sam Varshavchik wrote:Johnny Lam writes:The script takes an "AUTH" request, checks the username/password using the "chkpw_pam" program, then makes a separate connection to authdaemond to make a "PRE" request to return the account data. Since authProg simply sends "FAIL" for a "PRE" request, the request falls through to the authuserdb module.This simple idea works and required almost no programming, but I'd like to know if there's a nicer way to do this.There's one potential problem with this. The default configuration setting runs 5 authdaemond processes.You get five logins come in at the same time. You turn around and reconnect to authdaemond, five times. Your connection requests will timeout because no more authdaemond processes are available.Yes, that is true. I forgot to mention that I had doubled the default number of authdaemond processes that are started from 5 to 10. Despite the increased resource usage, I'm pleased that there was a simple way to mix having a virtual shared folder setup with a separate PAM-based authentication procedure.
Replace “five” with “ten”, in the given example.
pgpXZD6frueUE.pgp
Description: PGP signature
