Re: Why file content sniffing sucks

  I guess as an unix/linux admin I expect "file somefilename"  to tell
me the file type before I open it an editor or any other app, if there
is room for doubt. :)

  My only point being that the number of times I actually need that file
identified for me can be counted on 5 fingers on any given week.  Why
force a user to employ the feature every time they open their file
browser.  You're point that it is less broken then other methods of
context typing files is irrelevant, the question is it necessary?

  By the way I'm not knocking the feature, it's cool.  I just want to
know why I have to use it every time I open the file browser :)

to On Wed, 2003-12-24 at 11:25, iain wrote:
> On Wed, 2003-12-24 at 10:59 -0500, Pat Smith wrote:
> >   As a long time Gnome user, I kind of question the need for forcing
> > what should be an optional feature on the user base. 
> Why should it be an optional feature?
> [ ] Use really broken file identification based on extension type that
> can never be fixed
> [ ] Use file identification based on contents of file that can be fixed
> by tweaking algorithm
> Hmmm, great options there.
> How do you ID the following files
> "wine"
> "my-sexy-picture.jpg"
> Hmmm, dunno, dunno, oh jpg...whoops, no, it was an executable trojan
> renamed to a jpg to trick me into running it.
> Short less facetious answer: File content sniffing is less broken than
> any other method of IDing a filetype, and if it is broken, then the
> algorithm needs tweaking to make it better. It is not an "optional
> feature" and doesn't need to be.
> iain
Pat Smith
UNIX Administrator
Iron Mountain Inc.
1000 Campus Drive
Collegeville, Pa 19465
psmith imrm com

This email and its attachments are confidential under applicable law are 
intended for use of the senders addressee only, unless the sender expressly
agrees otherwise, or unless a separate written agreement exists between 
Iron Mountain and a recipient company governing communications between the 
parties and any data that may be so transmitted. Transmission of email over
the Internet is not a secure communications medium. If you are requesting or
have requested the transmittal of personal data, as defined in applicable
privacy laws, by means of email or in an attachment to email, you may wish
to select a more secure alternate means of transmittal that better supports
your obligations to protect such personal data. If the recipient of this 
message is not the recipient named above, and/or you have received this email
in error, you must take no action based on the information in this email.
You are hereby notified that any dissemination, misuse or copying or 
disclosure of this communication by a recipient who has received this message
in error is strictly prohibited. If this message is received in error please 
return this email to the sender and immediately highlight any error in 
Thank You

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]