On Sun, 17 Jul 2005, Michael Berg wrote: > The latest libpam-umask (0.02) encounters a SIGSEGV (Segmentation fault)
this is because of some unfortunate code that i don't even think should be in the module... it's a result of the "per-user umask" support. it segfaults for any user which does *not* have a ~/.pam_umask file... but it's even worse... there's a pointer manipulation error causing the segfault -- the "user" parm passed to pam_get_item is a pointer to random garbage which pam_get_item then fills in... there's an off-by-1 in the umask_file_path allocation... it logs far too much... and per-user support really should be optional. i'm working on a patch... -dean -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
