From owner-freebsd-doc@FreeBSD.ORG Fri Nov 19 20:33:38 2004 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B738016A4CE for ; Fri, 19 Nov 2004 20:33:38 +0000 (GMT) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D23943D1F for ; Fri, 19 Nov 2004 20:33:38 +0000 (GMT) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 4E02C580; Fri, 19 Nov 2004 14:33:38 -0600 (CST) Date: Fri, 19 Nov 2004 14:33:38 -0600 From: Tillman Hodgson To: freebsd-doc@freebsd.org Message-ID: <20041119203338.GF61766@seekingfire.com> References: <419E4747.6070001@FreeBSD.org> <20041119193745.GD61766@seekingfire.com> <419E510B.6020800@elvandar.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <419E510B.6020800@elvandar.org> X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/personal/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers X-Tillman-rules: yes he does User-Agent: Mutt/1.5.6i Subject: Re: Proposal regarding security chapter X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 20:33:38 -0000 On Fri, Nov 19, 2004 at 09:01:15PM +0100, Remko Lodder wrote: > Tillman Hodgson wrote: > > > >"Firewall", by itself, doesn't feel like an intuitive place to split > >topics to me (aside from the convenience of its size). However, I > >can see a natural split between network security and host security. > >In that scenario, MAC would become the largest portion of the host > >security chapter. > > > >That still leaves security with 2 chapters, unfortunately. It only > >addressed the page count balance between the two chapters. > > Well, i had a tiny little discussion on EFNet on our docs channel > (#bsddocs) and there is another suggestion to make a section V for > security and place all security related stuff in there like > MAC,Firewalls,Secure system stuff (or whatever it should be named). I like this idea the best. Ok, granted, in one of aspects I'm a security consultant and so I'm a /little/ biased as to it's importance, but there's a practical benefit as well: Each topic gets it's own chapter. And, seriously, some of the Security sub-chapters suffer from too-many-sub-level-itis. This would alleviate a lot of that. > I do not think that it's good to place Firewall and Mac into one > chapter. But that's perhaps a bit of taste :) Nope, I agree with you. I was proposing to have a network and a host (or local, which Tom suggested for a name) chapter. Firewalling would be in the network chapter, MAC would be in the local chapter. This is now my second-best ideal, though, after the new Section V idea. -T -- "Yield to temptation; it may not pass your way again." -- Robert Heinlein