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

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
file command can't identify the zip64 format correctly.

Version-Release number of selected component (if applicable):
zip-3.0-1.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. Create an archive as zip v3.0 format. 
$ echo foo | zip > test.zip 

2. Check a file type of the created archive by the file command. 
$ file test.zip 

Actual results:
The file command identifies a zip64 format archive as "data". 

Expected results:
The file command identifies a zip64 format archive as "ZIP64 archive data". 

Additional info:
magic bit from zip file 

50 4B 03 04  14 < -- correctly identified    --> PK...
50 4B 03 04  2D <-- incorrectly identified --> PK..-

From magic definition file
# ZIP archives (Greg Roelofs, c/o zip-bugs.edu)
0       string          PK\003\004
>30     ubelong         !0x6d696d65
...
>>4     byte            0x14            Zip archive data, at least v2.0 to extract
!:mime  application/zip
<-- add here
>>4     byte            0x2d            Zip64 archive data, at least v3.0 to extract
!:mime  application/zip


Adding 2d to the list here should fix this.  2D is used to identify "zip64" format. This issue can also be triggered

Patch - https://bugzilla.redhat.com/attachment.cgi?id=449876

I've tested the patch and it works, thanks.

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
The file utility has been updated to recognize the ZIP64 file format.

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.

http://rhn.redhat.com/errata/RHBA-2011-0204.html