From owner-freebsd-security  Mon Aug  5 07:40:40 1996
Return-Path: owner-security
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA21553
          for security-outgoing; Mon, 5 Aug 1996 07:40:40 -0700 (PDT)
Received: from www.hsc.wvu.edu (www.hsc.wvu.edu [157.182.98.68])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA21547
          for <freebsd-security@freebsd.org>; Mon, 5 Aug 1996 07:40:37 -0700 (PDT)
Received: (from jsigmon@localhost) by www.hsc.wvu.edu (8.6.12/8.6.12) id KAA14877; Mon, 5 Aug 1996 10:41:46 -0400
Date: Mon, 5 Aug 1996 10:41:46 -0400 (EDT)
From: Jeremy Sigmon <jsigmon@www.hsc.wvu.edu>
To: Nathan Lawson <nlawson@kdat.csc.calpoly.edu>
cc: Brandon Gillespie <brandon@tombstone.sunrem.com>,
        freebsd-security@freebsd.org
Subject: Re: Crack 4.1 patches for FBSD
In-Reply-To: <199608030513.WAA02366@kdat.calpoly.edu>
Message-ID: <Pine.BSF.3.91.960805103925.14830B-100000@www.hsc.wvu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Fri, 2 Aug 1996, Nathan Lawson wrote:

> I'm actually interested in a 'secure' release of FreeBSD, with daemons not
> running as root, no complicated mailers, few to no setuid binaries -- in
> essence, what I do to my FreeBSD systems as soon as I install them.
> 
> Unfortunately, I have recently started a very demanding job and do not have
> the time to contribute to such a project.  My apologies.
> 

Even just a HTML checklist of your actions after installing FreeBSD would
be nice to look at something like:

* Install FreeBSD
* Remove tftp from inetd because ...
etc...