From owner-freebsd-security  Fri Jun 20 13:45:21 1997
Return-Path: <owner-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id NAA23977
          for security-outgoing; Fri, 20 Jun 1997 13:45:21 -0700 (PDT)
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA23972
          for <freebsd-security@FreeBSD.ORG>; Fri, 20 Jun 1997 13:45:08 -0700 (PDT)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id QAA02968;
	Fri, 20 Jun 1997 16:45:01 -0400 (EDT)
Date: Fri, 20 Jun 1997 16:45:01 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <199706202045.QAA02968@khavrinen.lcs.mit.edu>
To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc: freebsd-security@FreeBSD.ORG
Subject: Attempt to compromise root
In-Reply-To: <199706201909.PAA02705@khavrinen.lcs.mit.edu>
References: <33AAB0CA.2781E494@fsl.noaa.gov>
	<199706201909.PAA02705@khavrinen.lcs.mit.edu>
Sender: owner-security@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

<<On Fri, 20 Jun 1997 15:09:16 -0400 (EDT), I wrote:

> There already is such a thing.  Every recent release includes mtree
> files with md5 digests of everything included in the distribution.
> See the FTP site or CD-ROM.

I forgot to mention....

Probably the release engineer should generate and publish a digital
signature of the files and the distribution's associated
CHECKSUMS.MD5.  Actually, the installation system ought to be able
itself to at least verify the MD5s of the tarballs it retrieves.

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
wollman@lcs.mit.edu  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA|                     - Susan Aglukark and Chad Irschick