From owner-freebsd-questions  Thu Feb  6 14:19:49 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA10271
          for questions-outgoing; Thu, 6 Feb 1997 14:19:49 -0800 (PST)
Received: from revelstone.jvm.com (revelstone.jvm.com [207.98.213.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA10252
          for <questions@freebsd.org>; Thu, 6 Feb 1997 14:19:43 -0800 (PST)
Received: (from fbsdlist@localhost) by revelstone.jvm.com (8.7.5/8.6.12) id RAA05680; Thu, 6 Feb 1997 17:19:07 -0500 (EST)
Date: Thu, 6 Feb 1997 17:19:06 -0500 (EST)
From: Cliff Addy <fbsdlist@revelstone.jvm.com>
To: questions@freebsd.org
Subject: Security hole in 2.1.6 (was: Links don't work for 2.1.6)
In-Reply-To: <199702060312.UAA04364@hemi.com>
Message-ID: <Pine.BSF.3.91.970206171703.5288A-100000@revelstone.jvm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 5 Feb 1997, Ade Barkah wrote:

> | There has been a serious security hole found in FreeBSD 2.1.6 that
> | is being fixed right now. It will be replaced with a new release,
> | FreeBSD 2.1.7, which will contain fixes for this and other bugs. The

Holy crap, Batman!  OK, for those of us who *just* installed 2.1.6 from 
the subscription disc, is there an easy way to patch the hole?