Displaying 3 results from an estimated 3 matches for "pam_session_open".
2006 Jun 22
4
[Bug 926] pam_session_close called as user or not at all
http://bugzilla.mindrot.org/show_bug.cgi?id=926
carsten.benecke at rrz.uni-hamburg.de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carsten.benecke at rrz.uni-
| |hamburg.de
------- Comment #16 from
2006 May 22
9
[Bug 926] pam_session_close called as user or not at all
http://bugzilla.mindrot.org/show_bug.cgi?id=926
------- Comment #8 from djm at mindrot.org 2006-05-22 15:12 -------
I don't understand - surely the limits should be applied in the *child*
process and not the parent process?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
2005 May 22
3
[Bug 926] pam_session_close called as user or not at all
...to the login/logout recording in loginrec.c
(to be called from the monitor). The existing loginmsg handling would allow any
messages returned by PAM to be sent to the user.
This would allow per-session login recording and would allow the
pam_session_close to be called from the same process as the pam_session_open.
It would mean that pam_session_open() would not be called be pam_setcred (since
in privsep we switch to the real user very early). I'm not sure if that's going
to be a problem or not.
Comments (esp. from PAM folks) welcome.
------- You are receiving this mail because: -------
You are...