From owner-freebsd-security  Tue Jul 29 09:59:43 1997
Return-Path: <owner-freebsd-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA28893
          for security-outgoing; Tue, 29 Jul 1997 09:59:43 -0700 (PDT)
Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA28880
          for <security@freebsd.org>; Tue, 29 Jul 1997 09:59:40 -0700 (PDT)
Received: (from jas@localhost)
	by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id JAA25886;
	Tue, 29 Jul 1997 09:57:36 -0700 (PDT)
Date: Tue, 29 Jul 1997 09:57:36 -0700 (PDT)
From: Jim Shankland <jas@flyingfox.com>
Message-Id: <199707291657.JAA25886@biggusdiskus.flyingfox.com>
To: vince@mail.MCESTATE.COM
Subject: Re: security hole in FreeBSD
Cc: security@freebsd.org
Sender: owner-freebsd-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Vincent Poy <vince@mail.MCESTATE.COM> writes:

> I just verified it and you're right....  I wonder how the .rhosts got
> there in the first place.

Gee, do you think maybe ... the cracker put it there?  Nah.  Too obvious.

Say, how many email messages have we seen on this thread?  The subject
line notwithstanding, this is not about a security hole in FreeBSD.
The hole is elsewhere.  In any event, I'm going to start deleting unread
all mail whose subject is "Security hole in FreeBSD"; so, if anyone
wishes to report or discuss an actual security hole in FreeBSD, I
would be most appreciative if you would use a different subject line
for that mail.  Thanks in advance.

Jim Shankland
Flying Fox Computer Systems, Inc.