From owner-freebsd-security  Fri Jun 27 00:39:18 1997
Return-Path: <owner-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id AAA09424
          for security-outgoing; Fri, 27 Jun 1997 00:39:18 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA09418
          for <security@freebsd.org>; Fri, 27 Jun 1997 00:39:14 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id AAA29999; Fri, 27 Jun 1997 00:39:34 -0700 (PDT)
To: David Nugent <davidn@labs.usn.blaze.net.au>
cc: Sean Kelly <kelly@fsl.noaa.gov>, security@freebsd.org
Subject: Re: Attempt to compromise root 
In-reply-to: Your message of "Fri, 27 Jun 1997 16:57:40 +1000."
             <199706270657.QAA00874@labs.usn.blaze.net.au> 
Date: Fri, 27 Jun 1997 00:39:32 -0700
Message-ID: <29995.867397172@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> >  You mean of the exact tree you've installed?  Hmmmm.  There are
> >  the foo.mtree files in each distribution, but is there some reason
> >  why that wouldn't be enough?
> 
> md5 checksums would be the go. But there are tools in existence that
> already do this available on many/most UNIX security-related sites.

The mtree files _do_ contain md5 checksums.  Uh, have you actually
looked at them? :-)

					Jordan