From owner-freebsd-arch@FreeBSD.ORG Wed May 23 22:06:36 2007 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2EF2516A41F; Wed, 23 May 2007 22:06:36 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id E32B113C45B; Wed, 23 May 2007 22:06:35 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l4NM47tN078749; Wed, 23 May 2007 16:04:07 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 23 May 2007 16:04:20 -0600 (MDT) Message-Id: <20070523.160420.163264050.imp@bsdimp.com> To: cperciva@freebsd.org From: "M. Warner Losh" In-Reply-To: <465482BA.4050607@freebsd.org> References: <200705231753.l4NHrTEm025055@hergotha.csail.mit.edu> <465482BA.4050607@freebsd.org> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 23 May 2007 16:04:12 -0600 (MDT) Cc: wollman@hergotha.csail.mit.edu, freebsd-arch@freebsd.org Subject: Re: RFC: Removing file(1)+libmagic(3) from the base system X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2007 22:06:36 -0000 In message: <465482BA.4050607@freebsd.org> Colin Percival writes: : Garrett Wollman wrote: : > In article you write: : >> FreeBSD architects and file(1) maintainer, : >> 3. Due to its nature as a program which parses multiple data formats, it : >> poses an unusually high risk of having security problems in the future : >> (cf. ethereal/wireshark). : > : > And this doesn't apply to, say, awk(1)? : : Eh? Unless I'm seriously confused, awk doesn't parse any data formats... It handles arbitrary data from potentially hostile sources as well. But only when the users asks it to do so... Warner