by mail.netbsd.org with SMTP; 24 Oct 2000 15:48:31 -0000
	by noc.untraceable.net (8.11.1/8.11.1/bonk!) id e9OFmDp28593;
	Tue, 24 Oct 2000 11:48:13 -0400 (EDT)
Date: Tue, 24 Oct 2000 11:48:12 -0400
From: Andrew Brown <atatat@atatdot.net>
To: Jon Lindgren <jlindgren@slk.com>
Cc: tech-security@netbsd.org, tech-kern@netbsd.org
Subject: Re: security sysctl? (was: r/o filesystem restrictions for firewall?)
Message-ID: <20001024114812.A28507@noc.untraceable.net>
Reply-To: Andrew Brown <atatat@atatdot.net>
References: <Pine.WNT.4.21.0010241054380.709-100000@a28043.net.slk.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Pine.WNT.4.21.0010241054380.709-100000@a28043.net.slk.com>; from jlindgren@slk.com on Tue, Oct 24, 2000 at 11:05:38AM -0400
Return-Receipt-To: receipts@daemon.org

>This was furthered into using sysctl's to do accomplish the same
>results... having a security section with knobs to frob which turn
>different features (such as allowing ipf or ipnat rules to be added,
>etc...).  And of course, after that, making the security section
>read-only, so if one cracks the box certain features can't be re-enabled.

no...you misunderstood me.  the "last" security knob would mark the
*entire* sysctl mib as read-only wrt userland, not just the security
mib.

i envisioned adjusting whatever needed to be adjusted, and then
closing the box.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."