Would a patch like this be acceptable?
--- openssh/session.c Wed Apr 18 10:29:34 2001
+++ openssh-RTM/session.c Tue May 1 09:51:22 2001
@@ -1088,9 +1088,12 @@
switch, so we let login(1) to this for us. */
if (!options.use_login) {
#ifdef HAVE_OSF_SIA
- session_setup_sia(pw->pw_name, s->ttyfd == -1 ? NULL
: s->tty);
- if (!check_quietlogin(s, command))
+ if (!check_quietlogin(s, command)) {
+ session_setup_sia(pw->pw_name, s->ttyfd == -1
? NULL : s->tty);
do_motd();
+ } else {
+ session_setup_sia(pw->pw_name, NULL);
+ }
#else /* HAVE_OSF_SIA */
#ifdef HAVE_CYGWIN
if (is_winnt) {
--
Ricardo Muggli (ricardo.muggli at mnsu.edu)
Systems Manager
Information and Technology Services
Minnesota State University, Mankato
101 Morris Hall
Mankato, MN 56001
Phone: (507) 389-1164 Fax: (507) 389-6115
On Tue, 1 May 2001, Ricardo Muggli wrote:
> I have tried this with openssh-2.5.2p2 and openssh-SNAP-20010501.
> I have noticed that with a .hushlogin file in my home directory I still
> get messages.
>
> With the .hushlogin file I get these messages:
> Last successful login for ricardo: Tue May 1 08:06:00 2001 from
> blah.mnsu.edu
> Last unsuccessful login for ricardo: Tue May 1 08:05:21 2001 from
> blah.mnsu.edu
>
> Without the .hushlogin file I get the same messages along with /etc/motd
>
> It appears that these messages are being produced from withing auth-sia.c
> during sia_ses_estab(). I couldn't tell if there was some way to
suppress
> these messages or not. Does anybody on this list know if these messages
> can be suppressed? If then can be, we should fix it so these messages are
> printed when there is no .hushlogin and suppressed when there is a
> .hushlogin or there is a command.
>
> Thanks,
>
> --
> Ricardo Muggli (ricardo.muggli at mnsu.edu)
> Systems Manager
> Information and Technology Services
> Minnesota State University, Mankato
> 101 Morris Hall
> Mankato, MN 56001
> Phone: (507) 389-1164 Fax: (507) 389-6115
>
>