Bug 11119

Summary:	Update mailcap (/etc/mime.types) to know e.g. vnd.openxmlformats-*
Product:	Mageia	Reporter:	Marc Krämer <mageia>
Component:	RPM Packages	Assignee:	Florian Hubold <doktor5000>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	doktor5000, fundawang, luigiwalser, pterjan
Version:	Cauldron	Keywords:	Triaged
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	mailcap	CVE:
Status comment:
Bug Depends on:
Bug Blocks:	2027

Description Marc Krämer 2013-08-31 14:33:18 CEST

Both mailing and apache use this file to determine the file type for download etc.

According to the comment in this file, the version is from 2008.
I think at least a few common file extensions for openoffice or MS products should be added.

Manuel Hiebel 2013-09-09 19:27:11 CEST

CC: (none) => doktor5000, fundawang, pterjan
Keywords: (none) => Triaged

Comment 1 Florian Hubold 2013-09-09 20:37:42 CEST

Normally this mailcap file should not be used, programs should use the defaults from shared-mime-info. You may want to check https://bugs.mageia.org/show_bug.cgi?id=2027

Comment 2 Marc Krämer 2013-09-09 21:47:49 CEST

I think it is a good idea of having only one database at a time.
but the current situation is, that apache & postfix or php don't search any shared-mime-info but only one simple file.

Since I don't know how quick all programs are patched to use shared-mime-info, wouldn't it be best to get a more recent list of mime-types and integrate them or maybe just generate the list out of the shared-mime-types?

But concerning shared-mime-types: are mimetypes of not installed applications (e.g. libreoffice) are available? or do I have to install libreoffice on every webserver just to have these mime-types available to apache to make it show the correct header information on download?

Comment 3 Florian Hubold 2013-09-09 22:09:45 CEST

Yes, the idea is to have only shared-mime-info.
And yes you only need to have shared-mime-info installed. Please read up on it.

Comment 4 Marc Krämer 2013-09-09 22:30:09 CEST

sorry to bother you again, but I don't see how to tell this apache directive to use a shared mime info.
http://httpd.apache.org/docs/current/mod/mod_mime.html#typesconfig

Comment 5 Marc Krämer 2014-08-22 14:13:48 CEST

this problem still exists.
The provided file is from 2008. Since apache still uses this file, it should be updated, either automatic generated from shared-mime-info or just provide a more up-to-date file.

Comment 6 Marc Krämer 2014-08-22 14:16:40 CEST

just checked fedora, even they have a newer file, e.g. xltm, docx are listed.

Florian Hubold 2014-08-24 17:40:34 CEST

Blocks: (none) => 2027

Comment 7 Florian Hubold 2014-08-24 17:42:49 CEST

Yep, and they killed mailcap.vga more then 10 years ago.

Although we should be aware about related security issues, e.g.:
https://bugzilla.redhat.com/show_bug.cgi?id=479010
https://bugs.freedesktop.org/show_bug.cgi?id=19377

Will try to update mailcap

Comment 8 Florian Hubold 2014-08-24 20:47:13 CEST

Please check with latest mailcap-2.1.42-1.mga5 from cauldron.
As this is quite an invasive change, will probably not be backported to Mageia 3 or 4.

Source RPM: mailcap-2.0.4-29.mga3.src.rpm => mailcap
Summary: Update /etc/mime.types to know e.g. vnd.openxmlformats-* => Update mailcap (/etc/mime.types) to know e.g. vnd.openxmlformats-*
Status: NEW => ASSIGNED
Assignee: bugsquad => doktor5000

Comment 9 Marc Krämer 2014-08-25 00:36:47 CEST

thanks.
I've installed it, but I don't expect any sideeffects, since it's only a file for determining the mime-type by extension. For me it's more important a newer file gets shipped in future versions than to patch an old version.

Comment 10 Florian Hubold 2014-08-25 21:43:22 CEST

Then closing this one.

@Luigi: Do you want this documented somewhere, as I'd only add a few words about this in release notes.

Status: ASSIGNED => RESOLVED
CC: (none) => luigiwalser
Resolution: (none) => FIXED

Comment 11 David Walser 2014-08-25 21:46:28 CEST

Only needs to be documented if the update causes users/sysadmins to need any intervention to handle the update.

Version: 3 => Cauldron