From owner-freebsd-current  Mon Oct  7 04:42:59 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id EAA18488
          for current-outgoing; Mon, 7 Oct 1996 04:42:59 -0700 (PDT)
Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA18476
          for <current@freebsd.org>; Mon, 7 Oct 1996 04:42:56 -0700 (PDT)
Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id LAA15073; Mon, 7 Oct 1996 11:33:21 GMT
Date: Mon, 7 Oct 1996 20:33:20 +0900 (JST)
From: Michael Hancock <michaelh@cet.co.jp>
To: Bruce Evans <bde@zeta.org.au>
cc: current@freebsd.org
Subject: Re: secure level diffs to kern_mib.c, LINT
In-Reply-To: <199610071049.UAA26363@godzilla.zeta.org.au>
Message-ID: <Pine.SV4.3.93.961007201126.14678B-100000@parkplace.cet.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 7 Oct 1996, Bruce Evans wrote:

> >> Actually, securelevel 1 is normally so insecure that it shouldn't be used.
> >> It essentially only provides write protection of /dev/mem and /dev/kmem.
> >
> >Isn't write protection of /dev/mem /dev/kmem a good enough reason for use? 
> 
> No, it gives a false sense of security.  Start with securelevel 2, where

Put this in the man pages with explanations for people who want a shade of
grey instead of just black and white. 

If they decide to use it, they're responsible for their choice not you.

Regards,


Mike