Bug 249473 - File magic file wrongly identifies text file as MPEG-4 LO-EP audio stream
Summary: File magic file wrongly identifies text file as MPEG-4 LO-EP audio stream
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: file   
(Show other bugs)
Version: 5.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Tomas Smetana
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-07-24 21:16 UTC by Rodrigo Barbosa
Modified: 2009-01-20 22:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-20 22:02:51 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Sample file to reproduce the bug (23 bytes, application/octet-stream)
2007-07-24 21:16 UTC, Rodrigo Barbosa
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:0208 normal SHIPPED_LIVE file bug fix and enhancement update 2009-01-20 16:06:14 UTC

Description Rodrigo Barbosa 2007-07-24 21:16:49 UTC
Description of problem:
File will identify any text file starting with "Má" (iso-8859-1) as a MPEG-4
LO-EP audio stream. Since that character combination is fairly common on several
languages, this can cause serious problems.

Version-Release number of selected component (if applicable):

How reproducible:
Attached file

Steps to Reproduce:
1. $ file magic-bug-sample.txt

Actual results:
magic-bug-sample.txt: MPEG-4 LO-EP audio stream

Expected results:
magic-bug-sample.txt: ISO-8859 text

Additional info:

Comment 1 Rodrigo Barbosa 2007-07-24 21:16:49 UTC
Created attachment 159888 [details]
Sample file to reproduce the bug

Comment 2 Tomas Smetana 2008-02-01 09:43:16 UTC
You're right.  I think we should rather remove support for the MPEG LO-EP format
-- it's very rare and if it really can be determined by the first two bytes
only, it makes more sense to report the text files correctly.

Comment 3 Rodrigo Barbosa 2008-02-01 16:10:19 UTC
That is pretty much what I have been doing on my server. Removing the support
for that format and recompiling the mgc file.
Interesting too is the fact this only happens with the regular (non-mime) file
detection. The mime-type detection shows the file correctly, which points to
further problems, since there is a discrepancy between the regular and the
mime-type magic files.

Comment 4 RHEL Product and Program Management 2008-06-04 22:49:01 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update

Comment 9 errata-xmlrpc 2009-01-20 22:02:51 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.