Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 652476

Summary:	file utility detects text file with MZ at the start as MSDOS EXE
Product:	Red Hat Enterprise Linux 4	Reporter:	Victor Orgos <v_orgos>
Component:	file	Assignee:	Jan Kaluža <jkaluza>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.8	CC:	ovasik
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-11-12 12:25:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Victor Orgos 2010-11-11 23:51:05 UTC

Description of problem:
file utility detects text files with the characters MZ at the start of the file as MS-DOS executable (EXE)

Version-Release number of selected component (if applicable):
# rpm -q file
file-4.10-8.el4

How reproducible:
every time

Steps to Reproduce:
1. create file with MZ at the start of the file
2. run file tool 
3.
  
Actual results:
/tmp/testfile.test: MS-DOS executable (EXE)

Expected results:
ASCII file

Additional info:
Ubuntu 10 correct detects these cases as ASCII files.

Comment 1 Ondrej Vasik 2010-11-12 12:25:43 UTC

Thanks for report - but compare something comparable - Ubuntu-10.10 contains file utility from year 2010 (at least I hope so :) ), RHEL-4 contains file utility from year 2004. If you'll try RHEL-6, such file is correctly detected as ASCII file. 

As RHEL-4 is very late in Release Cycle and is now only targetting important and security issues, I'm going to close this bugzilla WONTFIX - as this is not going to be fixed in RHEL-4. Feel free to contact product support if you think the problem is important enough to be solved in RHEL-4 - bugzilla is not a support tool for RHEL.