Re: RFC: Removing file(1)+libmagic(3) from the base system

At 7:12 PM +0000 5/23/07, Poul-Henning Kamp wrote:
In message <46546E16.9070707@xxxxxxxxxxx>, Colin Percival writes:
FreeBSD architects and file(1) maintainer,

> I'd like to remove file(1) and libmagic(3) from the FreeBSD base
> system for the following reasons:
>
> 1. I don't see it as being a necessary component of a UNIX-like
> operating system.

On this I would tend to disagree strongly. The ability to identify
random files have been a key component of UNIX for many years and
I think people would be significantly surprised if we stopped
providing it.

I concur with PHK. There has been a 'file' command on every unix
system I have used in the past 15 (or more) years. If FreeBSD
removes the file(1) command, almost every sysadmin will simply
install it from ports.

The file(1) command does not run as a daemon, it is not setuid or
setgid, and has no special access to any information which must be
kept secure (such as /etc/passwd). I don't see why we would single
out that command based on one buffer overflow.

I realize that every security advisory involves a lot of rush work
on the part of the security team, but I don't think that file(1)
has been guilty often enough for us to consider removing it. And I
think removing it for *security* reasons is particularly pointless
when we know that every unix sysadmin is just going to install it
from ports if it was not in the base system.

Mark me as a strong vote against removing it from the base system.

If we really think that file(1) command is a serious security problem,
then we should do things to limit the damage it can do. Moving it
into an always-installed port will not improve security (IMO).

--
Garance Alistair Drosehn = drosehn@xxxxxxx
Senior Systems Programmer or gad@xxxxxxxxxxx
Rensselaer Polytechnic Institute; Troy, NY; USA
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: The Coming Greater Depression
    ... and how big a business IT security ... example a linux user group mailing list to find out what is going on... ... sure, and please believe me, the command line is the most powerful ... some extent, but only at the price of a) far less power, and b) far ...
    (rec.martial-arts)
  • [SECURITY] telnet client
    ... For general information regarding FreeBSD Security Advisories, ... The telnetcommand is a TELNET protocol client, ... fixed-sized buffer. ... src/UPDATING ...
    (comp.unix.bsd.freebsd.misc)
  • [security bulletin] SSRT4794 rev.0 HPStorageWorks Command View XP access restriction bypass
    ... The information in this Security bulletin should be acted upon ... A potential security vulnerability has been identified in Command ... StorageWorks Disk Array XP128, Surestore Disk Array XP256, ...
    (Bugtraq)
  • Re: security question(s)
    ... so on but I dont understand where the security issues actually are. ... If you allow user-supplied input on a shell command-line unaltered, ... What USER-SUPPLIED input is going to be used (especially on the command ... Unchecked user-supplied strings in shell commands are very touchy. ...
    (comp.lang.php)
  • Re: rootkit and trojan hunting
    ... security space, to keep my knowledge up to date. ... There are two other general reasons that I don't like seeing people ... (Is a decent open source WYSIWYG word ... recall, AIDE was created before the open source version of Tripwire, ...
    (Focus-IDS)