Ticket History #157: Telnetd doesn't know about IRIX

From kenh@cmf.nrl.navy.mil Wed Nov 6 13:50:21 1996
Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by rt-11.MIT.EDU (8.7.5/8.7.3) with SMTP id NAA19492 for <bugs@RT-11.MIT.EDU>; Wed, 6 Nov 1996 13:50:20 -0500
Received: from [134.207.10.161] by MIT.EDU with SMTP
id AA10090; Wed, 6 Nov 96 13:50:13 EST
Received: from elvis.cmf.nrl.navy.mil (kenh@elvis.cmf.nrl.navy.mil [134.207.10.38]) by ginger.cmf.nrl.navy.mil (8.7.5/8.7.3) with ESMTP id NAA28494 for <krb5-bugs@mit.edu>; Wed, 6 Nov 1996 13:50:10 -0500 (EST)
Received: (kenh@localhost) by elvis.cmf.nrl.navy.mil (8.6.12/8.6.11) id NAA03485; Wed, 6 Nov 1996 13:50:02 -0500
Message-Id: <199611061850.NAA03485@elvis.cmf.nrl.navy.mil>
Date: Wed, 6 Nov 1996 13:50:02 -0500
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
Reply-To: kenh@cmf.nrl.navy.mil
To: krb5-bugs@MIT.EDU
Subject: Telnetd incorrectly identifies Irix as BSD 4.4
X-Send-Pr-Version: 3.2

Naval Research Lab

System: SunOS elvis 4.1.3_U1 13 sun4m
Architecture: sun4


If you run the Kerberos telnet daemon under IRIX, the login banner identifies
the system as "BSD 4.4". This is because telnetd doesn't know about IRIX
and the default banner is BSD 4.4.
Use telnetd under Irix.


The following patch seems to do the trick:

--- appl/telnet/telnetd/ext.h.orig Thu Oct 31 12:52:58 1996
+++ appl/telnet/telnetd/ext.h Thu Oct 31 12:55:44 1996
@@ -234,7 +234,11 @@
# ifdef ultrix
# define DEFAULT_IM "\r\n\r\nULTRIX (%h) (%t)\r\n\r\r\n\r"
# else
-# define DEFAULT_IM "\r\n\r\n4.4 BSD UNIX (%h) (%t)\r\n\r\r\n\r"
+# ifdef sgi
+# define DEFAULT_IM "\r\n\r\nIRIX (%h) (%t)\r\n\r\r\n\r"
+# else
+# define DEFAULT_IM "\r\n\r\n4.4 BSD UNIX (%h) (%t)\r\n\r\r\n\r"
+# endif
# endif
# endif
# endif

From: Sam Hartman <hartmans@MIT.EDU>
To: kenh@cmf.nrl.navy.mil
Cc: krb5-bugs@MIT.EDU, krb5-bugs-redist@MIT.EDU
Subject: Re: telnet/157: Telnetd incorrectly identifies Irix as BSD 4.4
Date: 07 Nov 1996 15:12:34 -0500

I'm really tempted to remove the OS-specific banner all
together; it's unnecessary non-portable code.

--Sam

From: Tom Perrine <tep@SDSC.EDU>
To: hartmans@MIT.EDU
Cc: kenh@cmf.nrl.navy.mil, krb5-bugs@MIT.EDU, krb5-bugs-redist@MIT.EDU
Subject: Re: telnet/157: Telnetd incorrectly identifies Irix as BSD 4.4
Date: Thu, 7 Nov 1996 12:38:58 -0800 (PST)




I would heartily agree with this. I would even consider replacing
this with a "Kerberos-telnetd version string", which would be MUCH
more useful.

--
Tom E. Perrine (tep@SDSC.EDU) | San Diego Supercomputer Center
http://www.sdsc.edu/~tep/ | Voice: +1.619.534.5000
"Ille Albus Canne Vinco Homines" - You Know Who

From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
To: krb5-bugs@MIT.EDU, krb5-bugs-redist@MIT.EDU
Cc: Subject: Re: telnet/157: Telnetd incorrectly identifies Irix as BSD 4.4
Date: Thu, 07 Nov 1996 15:56:39 -0500


I dunno, I can see arguments on both sides. You could say that exposing the
Kerberos version string would be potential information for crackers (but then,
so is the OS type).

I guess my two main concerns are:

- It's not right to report the wrong OS type
- I would like to keep some of the original appearance of telnetd the same
since users get easily confused by new things.

--Ken

State-Changed-From-To: open-closed
State-Changed-By: raeburn
State-Changed-When: Thu Sep 13 22:14:50 2001
State-Changed-Why:

The message isn't used any more, at least not anything hardcoded into
telnetd.