similar to: [Bug 1053] The nonquery messages from PAM account aren't forwarded to user (privsep)

http://bugzilla.mindrot.org/show_bug.cgi?id=1053 ------- Additional Comments From dtucker at zip.com.au 2005-07-14 13:51 ------- Created an attachment (id=938) --> (http://bugzilla.mindrot.org/attachment.cgi?id=938&action=view) only send messages from monitor on pam_account account failure This is one way to fix this. There might be a tidier way... ------- You are receiving this

http://bugzilla.mindrot.org/show_bug.cgi?id=1053 ------- Additional Comments From dtucker at zip.com.au 2005-09-30 10:59 ------- This is the same thing as bug #1087, right? ------- 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=1053 Summary: The nonquery messages from PAM account aren't forwarded to user (privsep) Product: Portable OpenSSH Version: 4.1p1 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: PAM support

http://bugzilla.mindrot.org/show_bug.cgi?id=939 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED ------- Comment #2 from dtucker at zip.com.au 2006-10-07 11:37 ------- Change all RESOLVED bug to CLOSED with the exception

http://bugzilla.mindrot.org/show_bug.cgi?id=892 Summary: Send output from PAM account modules to user Product: Portable OpenSSH Version: -current Platform: Other OS/Version: All Status: NEW Severity: normal Priority: P2 Component: PAM support AssignedTo: openssh-bugs at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=463 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #235 is|0 |1 obsolete| | Attachment #288 is|0 |1 obsolete|

Hi. If sshd is configured to use PAM and UsePrivilegeSeparation=no or you are logging is as root, any messages returned by PAM session modules are not displayed to the user. (Even when the config file has privsep=yes, logging in as root disables privsep anyway since there's no point, so it behaves the same way as privsep=no). I think I've figured out why: when privsep=no,

http://bugzilla.mindrot.org/show_bug.cgi?id=1047 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[RELENG] Bugs planned to be |[RELENG] Bugs planned to be |fixed for the release after |fixed for the 4.3 release |4.1

http://bugzilla.mindrot.org/show_bug.cgi?id=289 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Additional Comments From dtucker at zip.com.au 2002-06-25

http://bugzilla.mindrot.org/show_bug.cgi?id=355 ------- Additional Comments From dtucker at zip.com.au 2002-08-25 18:10 ------- It looks like the call to loginsuccess() fails because it's done as a non-privileged user. This is bad because in addition to generating the message it also clears the failed login counter that leads to account lockout. The following patch fixes it for me

http://bugzilla.mindrot.org/show_bug.cgi?id=1189 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED ------- Comment #18 from dtucker at zip.com.au 2006-10-07 11:45 ------- Change all RESOLVED bug to CLOSED with the exception

http://bugzilla.mindrot.org/show_bug.cgi?id=560 Summary: Privsep child continues to run after monitor killed. Product: Portable OpenSSH Version: -current Platform: ix86 URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=164797 OS/Version: Linux Status: NEW Severity: normal Priority: P2

http://bugzilla.mindrot.org/show_bug.cgi?id=210 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED ------- Comment #5 from dtucker at zip.com.au 2006-09-28 19:25 ------- With the release of 4.4, we believe that this bug is

http://bugzilla.mindrot.org/show_bug.cgi?id=839 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #600 is|0 |1 obsolete| | ------- Additional Comments From dtucker at zip.com.au 2004-05-21 13:08 -------

http://bugzilla.mindrot.org/show_bug.cgi?id=1308 Darren Tucker <dtucker at zip.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE CC|

http://bugzilla.mindrot.org/show_bug.cgi?id=463 ------- Additional Comments From dtucker at zip.com.au 2003-01-07 23:43 ------- Generate the message earlier in the login process and store for display after session startup? Rather than another variable for this (eg aixloginmsg, maybe __pam_msg), what about using a single Buffer for storing all of the messages to be displayed after login?

http://bugzilla.mindrot.org/show_bug.cgi?id=423 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |serg at bspb.ru ------- Additional Comments From dtucker at zip.com.au 2003-05-13 09:55 ------- *** Bug 562 has been marked as a

http://bugzilla.mindrot.org/show_bug.cgi?id=463 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO|14 | nThis| | ------- You are receiving this mail because: ------- You are the assignee for the

http://bugzilla.mindrot.org/show_bug.cgi?id=463 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |822 nThis| | ------- You are receiving this mail because: ------- You are the assignee for

http://bugzilla.mindrot.org/show_bug.cgi?id=270 ------- Additional Comments From dtucker at zip.com.au 2002-06-09 19:59 ------- Created an attachment (id=111) sshd output on AIX w/PrivSep ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.