From owner-freebsd-security Sun Sep 19 22:34:26 1999 Delivered-To: freebsd-security@freebsd.org Received: from forced.attrition.org (attrition.org [198.77.217.13]) by hub.freebsd.org (Postfix) with ESMTP id 33BFA14E82; Sun, 19 Sep 1999 22:34:23 -0700 (PDT) (envelope-from jobe@attrition.org) Received: from localhost (jobe@localhost) by forced.attrition.org (8.9.3/0.0.1.beta.nospam) with SMTP id WAA19310; Sun, 19 Sep 1999 22:38:05 -0600 Date: Sun, 19 Sep 1999 22:38:05 -0600 (MDT) From: Jobe To: Brett Glass Cc: Neil Blakey-Milner , Matthew Dillon , freebsd-security@FreeBSD.ORG, Nik Clayton Subject: Re: Documentation of security features In-Reply-To: <4.2.0.58.19990919181430.045dd330@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 19 Sep 1999, Brett Glass wrote: > At 10:44 AM 9/19/99 -0600, Jobe wrote: > > >So enlighten me, what 'key security' options do the size of the documented > >man pages define? Is there some obscure denial of service attack related > >to the size of the man pages?!? And as for the links for securelevel and > >similar things, what the hell does this man page problem have to do with > >that? > > If administrators can't find documentation, they won't be able to secure > their systems easily -- and FreeBSD will gain an undeserved reputation for > being less secure. Also, they'll ask the same questions repeatedly on mailing > lists, etc. Ok, so exactly what security intensive procedures and protocols rely on the userland handling of a foreground and/or background processes. > > Any failure of the man system to guide users to the right answer -- or even > give them a hint -- is something that should most certainly be fixed. Hence > my comments, which I think are very much apropos. As I have stated in prior mails to this list, THIS IS NOT A SECURITY ISSUE. The location and handling of the csh and related man pages IS NOT A SECURITY ISSUE. You need to familiarize yourself with the other freebsd mailing liss, such as: freebsd-bugs freebsd-chat freebsd-questions This sort of mail needs to be directed to the appropriate lists. --Jobe > > --Brett > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message