From owner-freebsd-current  Wed Apr  5 05:04:31 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA18235 for current-outgoing; Wed, 5 Apr 1995 05:04:31 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA18228; Wed, 5 Apr 1995 05:04:15 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id WAA18226; Wed, 5 Apr 1995 22:00:21 +1000
Date: Wed, 5 Apr 1995 22:00:21 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199504051200.WAA18226@godzilla.zeta.org.au>
To: current@freefall.cdrom.com, jkh@freefall.cdrom.com
Subject: Re: "Cookbook" for security.
Sender: current-owner@FreeBSD.org
Precedence: bulk

>Poul and I were talking about the whole immutable flag issue, and
>since cpio, tar, pax and friends don't support the notion of
>extracting these extra flags ANYWAY, we might as well make a virtue of
>a vice and go "cookbook" style on it, where some central well-known
>file contains information that can be used to apply the flags in
>question after the system is installed.  For that matter, the file can
>also contain MD5 checksums so that you can verify that all the
>"important" files have not been changed from the release copies.
>Needless to say, the "cookbook" file should be highly immutable itself
>in these cases :-).

/etc/mtree/* is supposed to be used for this.  Guess what other friend
doesn't support chflags(). :-).

Bruce