From owner-freebsd-security Fri Sep 17 4:29:23 1999 Delivered-To: freebsd-security@freebsd.org Received: from ares.maths.adelaide.edu.au (ares.maths.adelaide.edu.au [129.127.246.5]) by hub.freebsd.org (Postfix) with ESMTP id CBFD2151DB for ; Fri, 17 Sep 1999 04:29:18 -0700 (PDT) (envelope-from glewis@ares.maths.adelaide.edu.au) Received: (from glewis@localhost) by ares.maths.adelaide.edu.au (8.9.3/8.9.3) id UAA67518; Fri, 17 Sep 1999 20:58:59 +0930 (CST) (envelope-from glewis) From: Greg Lewis Message-Id: <199909171128.UAA67518@ares.maths.adelaide.edu.au> Subject: Re: Securing a system that's been rooted remotely In-Reply-To: <37E21A0A.1075F204@ispro.net.tr> from Evren Yurtesen at "Sep 17, 1999 10:38:02 am" To: Evren Yurtesen Date: Fri, 17 Sep 1999 20:58:59 +0930 (CST) Cc: freebsd-security@freebsd.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > So what is the best way to set securelevel at boot time? > > Evren Alter the values of kern_securelevel_enable (to "YES") and kern_securelevel (to say "1", "2" or "3") in /etc/rc.conf. -- Greg Lewis glewis@trc.adelaide.edu.au Computing Officer +61 8 8303 5083 Teletraffic Research Centre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message