Displaying 5 results from an estimated 5 matches for "benecke".
2004 Sep 01
2
openssh-3.9p1: no pam_close_session() invocation
...version 3.9p1.
After closing a ssh-session the pam_close_session() function is not
invoked. Enabling PrivilegeSeparation (UsePrivilegeSeparation yes) does not
help.
Could someone acknowledge the problem, or even better, could some openssh
developer fix it?
With kind regards
CB
--
Dr. Carsten Benecke, Regionales Rechenzentrum, Universit?t Hamburg,
Schl?terstr. 70, D-20146 Hamburg, Tel.: ++49 40 42838 3097,
Fax: ++49 40 42838 3096, mailto: Carsten.Benecke at rrz.uni-hamburg.de
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.d...
2003 Sep 26
1
openssh-3.7.1p2: no pam_close_session() invocation
...Subsystem sftp /local/libexec/sftp-server
---
> Subsystem sftp /local/libexec/sftp-server
By the way: This is a bug in the documentation: The default for UsePAM in
3.7.1p2 is "no" while "#UsePAM yes" implies the opposite.
Regards,
Carsten
--
Dr. Carsten Benecke, Regionales Rechenzentrum, Universit?t Hamburg,
Schl?terstr. 70, D-20146 Hamburg, Tel.: ++49 40 42838 3097,
Fax: ++49 40 42838 3096, mailto: Carsten.Benecke at rrz.uni-hamburg.de
2004 Sep 04
3
[Bug 926] pam_session_close called as user or not at all
...h-unix-
dev&m=106458208520320
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: PAM support
AssignedTo: openssh-bugs at mindrot.org
ReportedBy: dtucker at zip.com.au
Reported by Dr. Carsten Benecke:
"I guess that the forked child process that calls the sshpam_cleanup()
function is forked before the parent calls do_pam_session() (which sets
sshpam_session_open to true)."
and Chris Jensen:
"But when I exit the session, pam_sm_close_session gets called, but it
only runs as the...
2009 Mar 02
0
Implementing conditional read-only attributes of ActiveRecord objects
Hello,
my goal is to implement the option of specifying a condition in
attr_protected, attr_readonly and possibly other attribute methods in
ActiveRecord objects.
Rationale (example):
class User < AR:Base
# User should not be able to modify fields any more once they have
been verified
attr_readonly :firstname, :lastname, :gender_id, :birthdate, :if
=> :passport_verified?
# ...
end