On Thu, Aug 14, 2003 at 11:57:48AM +0200, Degrande_Samuel wrote: > I tried to track it and found the memory leak to be IN the solaris > pam modules. After some talks with other people, it seems that > every pam implementation (Solaris, Linux...) suffers from memory leak, > and everybody tell to use a forked process to proceed the pam > authentication. What do you think of that ? I could propose you > a rlm_pam module which fork a new child every <given_number> > authentication request.
Yeah, every PAM module out there will leak all the **resp pointers. This was underspecified by the PAM people. We should come up with a workaround for this. I'm surprised you'd be doing something in PAM that you can't do "natively" with freeradius modules. /fc - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
