From owner-freebsd-security Mon Oct 5 13:59:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01015 for freebsd-security-outgoing; Mon, 5 Oct 1998 13:59:27 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01010 for ; Mon, 5 Oct 1998 13:59:25 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id OAA04161; Mon, 5 Oct 1998 14:44:51 -0600 (MDT) Message-Id: <4.1.19981005144059.00bef900@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 05 Oct 1998 14:42:48 -0600 To: Sheldon Hearn , freebsd-security@FreeBSD.ORG From: Brett Glass Subject: Re: The necessary steps for logging (the problem is fixed) In-Reply-To: <1135.907613873@axl.training.iafrica.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 08:57 PM 10/5/98 +0200, Sheldon Hearn wrote: >Anyone with intelligent comment on the usefulness of using only tabs as >separators and not whitespace, as is the norm for many conf formats? I don't think it's useful. Most people quote items with spaces anyway, either because they do not remember whether spaces are allowed in that case or because they want to be sure. I think that distinguishing between different "kinds" of whitespace creates a pitfall for the unwary and does nothing useful. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message