Hello...
I always have a memory leak problem (I use one of the last snapshot,
on Sparc Solaris 9).
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.
By the way, I think that there is an 'array index out of bound' bug
in src/modules.c :
/*
* Allow old names, too.
*/
if (!next) {
next = cf_subsection_find_next(cs, sub,
old_section_type_value[comp].typename);
}
This supposes that old_section_type_value has the same length than
section_type_value (well, beeing at least as long). But
old_section_type_value is shorter, so 'comp' goes out of bound, right ?
Regards.
--
Samuel Degrande LIFL - UMR 8022 CNRS - Bat M3
Phone: (33)3.20.43.47.38 USTL - Universite de Lille 1
Fax: (33)3.20.43.65.66 59655 VILLENEUVE D'ASCQ CEDEX - FRANCE
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
