From owner-freebsd-security  Mon Jul 15 03:38:54 1996
Return-Path: owner-security
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id DAA27298
          for security-outgoing; Mon, 15 Jul 1996 03:38:54 -0700 (PDT)
Received: from mercury.gaianet.net (root@mercury.gaianet.net [206.171.98.26])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA27289;
          Mon, 15 Jul 1996 03:38:52 -0700 (PDT)
Received: (from vince@localhost) by mercury.gaianet.net (8.7.5/8.6.12) id DAA03747; Mon, 15 Jul 1996 03:38:48 -0700 (PDT)
Date: Mon, 15 Jul 1996 03:38:48 -0700 (PDT)
From: -Vince- <vince@mercury.gaianet.net>
To: Gary Palmer <gpalmer@freebsd.org>
cc: jbhunt <jbhunt@mercury.gaianet.net>, freebsd-security@freebsd.org,
        root@mercury.gaianet.net
Subject: Re: New EXPLOIT located! 
In-Reply-To: <3588.837425885@orion.webspan.net>
Message-ID: <Pine.BSF.3.91.960715033754.1637K-100000@mercury.gaianet.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 15 Jul 1996, Gary Palmer wrote:

> -Vince- wrote in message ID
> <Pine.BSF.3.91.960715012012.1637F-100000@mercury.gaianet.net>:
> > > You *HAVE* applied the rdist patch(es), or better yet, DISABLED rdist
> > > totally, haven't you?
> 
> > 	Only took out the setuid flag... Have the patches been applied to 
> > the latest -current since I just recompiled rdist from the latest 
> > -current sources...
> 
> Huh? rdist shouldn't be vunerable if it HAS had the setuid bit
> removed... (unless I really am mis-understanding something)

	Hmmm, even with the setuid bit, his exploit doesn't work anymore...
I guess the sources for July 14th really changed it cause it can't find 
distfile for rdist any longer...

Vince