From owner-freebsd-security  Thu May  1 21:40:30 1997
Return-Path: <owner-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA11703
          for security-outgoing; Thu, 1 May 1997 21:40:30 -0700 (PDT)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA11698
          for <freebsd-security@freebsd.org>; Thu, 1 May 1997 21:40:27 -0700 (PDT)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 1.60 #1)
	id 0wNA8o-0005XU-00; Thu, 1 May 1997 22:40:18 -0600
To: mhpower@mit.edu
Subject: Re: Telnetd problem? 
Cc: bradley@dunn.org, freebsd-security@freebsd.org
In-reply-to: Your message of "Thu, 01 May 1997 18:53:59 EDT."
		<199705012253.SAA06953@charon.MIT.EDU> 
References: <199705012253.SAA06953@charon.MIT.EDU>  
Date: Thu, 01 May 1997 22:40:18 -0600
From: Warner Losh <imp@village.org>
Message-Id: <E0wNA8o-0005XU-00@rover.village.org>
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199705012253.SAA06953@charon.MIT.EDU> mhpower@mit.edu writes:
: The code is also inside "#if defined(LOGIN_R)" "#endif", as it is in
: many other variants of this telnetd. I haven't personally seen any
: environments in which LOGIN_R is defined at build time, and I suspect
: it's not normally defined on FreeBSD systems. There may be some systems
: where LOGIN_R is defined, but I think typically the code is not
: actually problematic as a consequence of it not actually being compiled.

I can't find any either.  However, my paranoia is such that I've gone
ahead and fixed it locally which means it will eventually make it into
the tree.  Since I get identical .o files before and after, I don't
think that it is a big deal.

Warner