openssh bugs - Apr 2005 - [Bug 1020] PrintLastLog doesn't work for UsePrivilegeseparation yes

http://bugzilla.mindrot.org/show_bug.cgi?id=1020

           Summary: PrintLastLog doesn't work for UsePrivilegeseparation yes
           Product: Portable OpenSSH
           Version: 4.0p1
          Platform: HPPA
        OS/Version: HP-UX
            Status: NEW
          Severity: normal
          Priority: P2
         Component: sshd
        AssignedTo: openssh-bugs at mindrot.org
        ReportedBy: senthilkumar_sen at hotpop.com


When I enabled Privilegeseparation the PrintLastLog directive doesn't work
as
expected. There is no Last Login details displayed but however when I disable 
Privilegeseparation the Last Login details are displayed. This happens for 
Non-root user. Im seeing this behaviour in OpenSSH 4.0p1.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1020





------- Additional Comments From djm at mindrot.org  2005-04-21 15:28 -------
*** Bug 1021 has been marked as a duplicate of this bug. ***



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1020





------- Additional Comments From dtucker at zip.com.au  2005-04-21 20:14 -------
Which version of HP-UX is this, and are you using PAM?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=1020


senthilkumar_sen at hotpop.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From senthilkumar_sen at hotpop.com  2005-04-25
17:42 -------
This is not a problem in Base OpenSSH code. I did some enhancement for the bug 
980 (logging shell pid to utmp) and those changes are responsible for this 
problem. I will mark this bug as Invalid. Thanks for the time.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.