Date: Thu, 24 May 2007 01:41:31 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: cperciva@freebsd.org Cc: freebsd-arch@freebsd.org Subject: Re: RFC: Removing file(1)+libmagic(3) from the base system Message-ID: <20070524.014131.756908450.imp@bsdimp.com> In-Reply-To: <46553A6B.7070904@freebsd.org> References: <20070523213251.GA14733@keltia.freenix.fr> <20070523.161038.-1989860747.imp@bsdimp.com> <46553A6B.7070904@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <46553A6B.7070904@freebsd.org>
Colin Percival <cperciva@freebsd.org> writes:
: > I guess I fail to see how this is any different than the .gz bugs that
: > were found a while ago. Nobody suggested removing .gz from the tree
: > because a few bugs were found. Everybody suggested updating right
: > away to fix those bugs. File is no different, and really should
: > remain in the tree.
:
: Deflate is one file format which is used quite often. File parses several
: different formats, including several which are not tested often (i.e., have
: a much higher chance of including parse bugs).
Now you are really reaching... File does it work by reading in meta
data (in one format, well tested) that describes how to parse the
files using a simple meta-language to describe offsets. I think you
are really reaching here, unless you can show some conclusive evidence
to support that this can cause problems (apart from core dumps from
memory exhaustion, and the like). Can you point to one of the magic
meta files that has a description so complex that it will likely cause
these kinds of things to happen?
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070524.014131.756908450.imp>