From owner-freebsd-security Mon Sep 6 8:40:27 1999 Delivered-To: freebsd-security@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 215B314DA9; Mon, 6 Sep 1999 08:40:23 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA74893; Mon, 6 Sep 1999 08:39:54 -0700 (PDT) (envelope-from dillon) Date: Mon, 6 Sep 1999 08:39:54 -0700 (PDT) From: Matthew Dillon Message-Id: <199909061539.IAA74893@apollo.backplane.com> To: Dag-Erling Smorgrav Cc: KATO Takenori , bde@zeta.org.au, freebsd-hackers@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: Init(8) cannot decrease securelevel References: <199909060513.PAA12402@godzilla.zeta.org.au> <19990906142342F.kato@gneiss.eps.nagoya-u.ac.jp> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org : :KATO Takenori writes: :> The kernel runs with four different levels of security. :> ! Any super-user process can raise the security level, but no process :> can lower it. : :How about "The security level can only be raised by the super-user, :and cannot be lowered by anyone." instead? : :DES :-- :Dag-Erling Smorgrav - des@flood.ping.uio.no Though, as a side note, it should be noted that if you have DDB enabled then lowering the secure level is pretty easy to do. If you have access to the console, of course. We used this trick at BEST a couple of times. Still, I think this might qualify as a bug in the securelevel implementation. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message