From owner-freebsd-current  Mon Oct  7 04:00:53 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id EAA08223
          for current-outgoing; Mon, 7 Oct 1996 04:00:53 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA08148
          for <current@freebsd.org>; Mon, 7 Oct 1996 04:00:07 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id UAA26363; Mon, 7 Oct 1996 20:49:28 +1000
Date: Mon, 7 Oct 1996 20:49:28 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199610071049.UAA26363@godzilla.zeta.org.au>
To: bde@zeta.org.au, michaelh@cet.co.jp
Subject: Re: secure level diffs to kern_mib.c, LINT
Cc: current@freebsd.org
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> 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
there are fewer bugs and the bugs are easier to fix.

Bruce