From owner-freebsd-security  Tue Nov 19 18:09:13 1996
Return-Path: owner-security
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id SAA24187
          for security-outgoing; Tue, 19 Nov 1996 18:09:13 -0800 (PST)
Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA24180
          for <freebsd-security@freebsd.org>; Tue, 19 Nov 1996 18:09:00 -0800 (PST)
Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM)
	id AA24914; Tue, 19 Nov 1996 18:08:59 -0800
Date: Tue, 19 Nov 1996 18:08:59 -0800 (PST)
From: "Brian N. Handy" <handy@sag.space.lockheed.com>
To: freebsd-security@freebsd.org
Subject: Re: Futile rexecd holes
In-Reply-To: <199611200032.LAA03928@genesis.atrad.adelaide.edu.au>
Message-Id: <Pine.OSF.3.94.961119180704.19924E-100000@sag.space.lockheed.com>
X-Files: The truth is out there
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 20 Nov 1996, Michael Smith wrote:

>Cy Schubert - ITSD Open Systems Group stands accused of saying:
>> This is the first I've heard of a "service pack update."  What is a "service 
>> pack update?"  Is it similar in concept to Sun's SunSolve CDROM or IBM's PUT 
>> (Program Update Tape)?
>
>It sounds to me like a concept-in-progress.
>
>> How does one get a "service pack update?"
>
>I would say that if someone were to produce binary update kits for things
>like this, that people would be very happy.  Basically you do something like
>this :

Wow...this is scary.  Someone makes a crack about Micro$oft's bug fix
system, and suddenly we're implementing it? :-)

Scared, very scared of the impending FreeBSD Service Pack I,

Brian