From owner-freebsd-security  Tue Jul 29 18:14:09 1997
Return-Path: <owner-freebsd-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id SAA26536
          for security-outgoing; Tue, 29 Jul 1997 18:14:09 -0700 (PDT)
Received: from eyelab.psy.msu.edu (eyelab.psy.msu.edu [35.8.64.179])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA26526
          for <freebsd-security@freebsd.org>; Tue, 29 Jul 1997 18:14:02 -0700 (PDT)
Received: from default (pm131-00.dialip.mich.net [35.9.14.191])
	by eyelab.psy.msu.edu (8.8.6/8.8.5) with SMTP id VAA01876
	for <freebsd-security@freebsd.org>; Tue, 29 Jul 1997 21:08:01 -0400 (EDT)
Message-Id: <3.0.3.32.19970729211037.006c2180@eyelab.msu.edu>
X-Sender: root@eyelab.msu.edu
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Tue, 29 Jul 1997 21:10:37 -0400
To: freebsd-security@freebsd.org
From: Gary Schrock <root@eyelab.psy.msu.edu>
Subject: Re: security hole in FreeBSD
In-Reply-To: <Pine.BSF.3.95.970729151209.3844n-100000@mail.MCESTATE.COM>
References: <Pine.BSI.3.95.970728231717.25484I-100000@milehigh.denver.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>	There would be no way to compare checksums of files anyways since
>these machines were both running -CURRENT and each revision of -CURRENT
>would have different checksums anyways.  

  Now that one I have to disagree with.  It's trivial to use something like
mtree to set up your own set of files with checksums.  And probably well
worth the effort.


Gary Schrock
root@eyelab.msu.edu