From owner-freebsd-security Sat Oct 6 4:24: 2 2001 Delivered-To: freebsd-security@freebsd.org Received: from drkshdw.org (user4.net011.fl.sprint-hsd.net [207.30.203.4]) by hub.freebsd.org (Postfix) with SMTP id 96FC237B403 for ; Sat, 6 Oct 2001 04:23:58 -0700 (PDT) Received: (qmail 71554 invoked from network); 6 Oct 2001 11:23:57 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by 0 with SMTP; 6 Oct 2001 11:23:57 -0000 Date: Sat, 6 Oct 2001 07:23:57 -0400 (EDT) From: Jeff Palmer To: Dave Chapeskie Cc: Subject: Re: Kern Secure Level In-Reply-To: <20011006041601.A7815@ddm.wox.org> Message-ID: <20011006072116.H71529-100000@Scorpio.drkshdw.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, 6 Oct 2001, Dave Chapeskie wrote: > On Sat, Oct 06, 2001 at 02:36:41AM -0400, Jeff Palmer wrote: > > A lot of newbie (please, no flames if this includes anyone reading this > > list) a lot of newbie admins will read about securelevels, and make > > the entire /bin /sbin and other directories immutable. This is a BAD > > THING! > > Bzzzt! Thanks for playing! > > You have it backwards. There is no security (other than from typos) in > making files in /sbin immutable if /sbin itself is not immutable. > Bzzzt? thanks for playing? didn't reaize I was playing. And pardon me, but I thought "and make the entire /bin and /sbin directory..." meant the directory as well as the files? (Hint: the key operative word here is "entire") Pardon me, but I think it'd be better for everyone involved if you didn't try to make this into a gameshow. Instead of saying exactly what I said, try reading the post? Just an idea.. Jeff Palmer scorpio@drkshdw.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message