From owner-freebsd-security  Sat May 31 11:21:58 1997
Return-Path: <owner-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id LAA02383
          for security-outgoing; Sat, 31 May 1997 11:21:58 -0700 (PDT)
Received: from eyelab.psy.msu.edu (eyelab.psy.msu.edu [35.8.64.179])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA02374
          for <freebsd-security@freebsd.org>; Sat, 31 May 1997 11:21:56 -0700 (PDT)
Received: from psy219.psy.msu.edu (psy219.psy.msu.edu [35.8.64.167])
	by eyelab.psy.msu.edu (8.8.5/8.8.5) with SMTP id OAA21343
	for <freebsd-security@freebsd.org>; Sat, 31 May 1997 14:19:08 -0400 (EDT)
X-Authentication-Warning: eyelab.psy.msu.edu: psy219.psy.msu.edu [35.8.64.167] didn't use HELO protocol
Message-Id: <3.0.2.32.19970531142155.006dec74@eyelab.msu.edu>
X-Sender: root@eyelab.msu.edu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32)
Date: Sat, 31 May 1997 14:21:55 -0400
To: freebsd-security@freebsd.org
From: Gary Schrock <root@eyelab.psy.msu.edu>
Subject: ftpd signal handler race?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Regarding the CERT announcement just recently about a problem with ftpd,
according to the information there it was implied that only 2.2+ was fixed,
and that the changes weren't in the 2.1 line.  When looking through the cvs
logs on the freebsd web site, I ran across a checkin on the RELENG_2_1_0
line that seemed to imply that this problem was fixed.  So is it true that
if one's tracking the 2.1-STABLE line then this problem has been fixed
regardless of what the cert announcement says?

Thanks

Gary Schrock
root@eyelab.msu.edu