[Bug 1646233] [NEW] file command incorrectly identifies a gzipped file as being a Minix filesystem

Rarylson Freitas rarylson at gmail.com
Wed Nov 30 20:39:27 UTC 2016


Public bug reported:

In Ubuntu 14.04, the command `file` (1:5.14-2ubuntu3.3) incorrectly
identifies a gzipped file as being a Minix filesystem.

Example:

```
$ file gzip-minix.eml 
gzip-minix.eml: Minix filesystem, V3, 43470 zones
$ file -v
file-5.14
magic file from /etc/magic:/usr/share/misc/magic
```

The workaround I'm using is passing the `-k` (keep going) param to file.

```
$ file -k gzip-minix.eml 
gzip-minix.eml: Minix filesystem, V3, 43470 zones\012- gzip compressed data, from Unix
```

In Ubuntu 16.04, however, the file is correctly identified.

```
$ file gzip-minix.eml 
gzip-minix.eml: gzip compressed data, from Unix
$ file -v
file-5.25
magic file from /etc/magic:/usr/share/misc/magic
```

This bug has a description very similar to those reported in these URLs:

- https://bugzilla.redhat.com/show_bug.cgi?id=873997
- https://bugzilla.redhat.com/show_bug.cgi?id=758429

However, despite the very similar description, I didn't find any problem
with the JPEG files attached in these bug reports.

Note: The error is occurring in about 1 gzipped file for each 60000 or
100000 files I have in my data filesystem. Because some of these files
contain sensitive information, I'm attaching only one of them (an
innocent example).

** Affects: file (Ubuntu)
     Importance: Undecided
         Status: New

** Attachment added: "gzip-minix.eml"
   https://bugs.launchpad.net/bugs/1646233/+attachment/4785419/+files/gzip-minix.eml

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1646233

Title:
  file command incorrectly identifies a gzipped file as being a Minix
  filesystem

Status in file package in Ubuntu:
  New

Bug description:
  In Ubuntu 14.04, the command `file` (1:5.14-2ubuntu3.3) incorrectly
  identifies a gzipped file as being a Minix filesystem.

  Example:

  ```
  $ file gzip-minix.eml 
  gzip-minix.eml: Minix filesystem, V3, 43470 zones
  $ file -v
  file-5.14
  magic file from /etc/magic:/usr/share/misc/magic
  ```

  The workaround I'm using is passing the `-k` (keep going) param to
  file.

  ```
  $ file -k gzip-minix.eml 
  gzip-minix.eml: Minix filesystem, V3, 43470 zones\012- gzip compressed data, from Unix
  ```

  In Ubuntu 16.04, however, the file is correctly identified.

  ```
  $ file gzip-minix.eml 
  gzip-minix.eml: gzip compressed data, from Unix
  $ file -v
  file-5.25
  magic file from /etc/magic:/usr/share/misc/magic
  ```

  This bug has a description very similar to those reported in these
  URLs:

  - https://bugzilla.redhat.com/show_bug.cgi?id=873997
  - https://bugzilla.redhat.com/show_bug.cgi?id=758429

  However, despite the very similar description, I didn't find any
  problem with the JPEG files attached in these bug reports.

  Note: The error is occurring in about 1 gzipped file for each 60000 or
  100000 files I have in my data filesystem. Because some of these files
  contain sensitive information, I'm attaching only one of them (an
  innocent example).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file/+bug/1646233/+subscriptions



More information about the foundations-bugs mailing list