search for: display_loginmsg

...user limits */ } do_setusercontext(pw); /* * PAM session modules in do_setusercontext may have * generated messages, so if this in an interactive * login then display them too. */ if (!check_quietlogin(s, command)) display_loginmsg(); But I found a problem - in this place the code is already running with the user privileges, so the limits file (/etc/limits) is unreadable for it (normaly it's owned by root with privs 600). If I chmod to 644 or chown to the user trying to log in, it can be read and the limits are set. To...

...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, do_pam_session is called *after* display_loginmsg, so the PAM messages are stored too late to be displayed to the user. One option would be to move display_loginmsg later, but that would change the message order on other platforms, so the attached patch just adds another call after do_setusercontext (the buffer is cleared after each, so ther...

...uot;session.c", function do_child(). In line 1426, the following code has been added to the portable version of OpenSSH: /* * PAM session modules in do_setusercontext may have * generated messages, so if this in an interactive * login then display them too. */ if (command == NULL) display_loginmsg(); According to the ChangeLog: 20040701 - (dtucker) [session.c] Call display_loginmsg again after do_pam_session. Ensures messages from PAM modules are displayed when privsep=no. Unfortunately, this breaks .hushlogin. As long as I run "ssh somehost somecommand", it obvi...

Hi. Some people have reported that login messages reported by sshd have extra newlines. It looks like there are 2 causes of this: a) some PAM modules like to return messages of "", which sshd dutifully appends a newline to and stores for later display. b) display_loginmsg appends a newline too (I think this dates back to before PAM supplied its own newlines). The attached (trivial) patch fixes this: it auth-pam will not append newlines, and loginmsg is displayed as a literal string (so any newlines needed must be supplied by whatever is appending to loginmsg)....

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