Bug 10721 - .asc extension for PGP files not managed well
Summary: .asc extension for PGP files not managed well
Status: RESOLVED FIXED
Alias: None
Product: shared-mime-info
Classification: Unclassified
Component: freedesktop.org.xml (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Jonathan Blandford
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-23 03:51 UTC by Sebastian Dröge (slomo)
Modified: 2010-01-29 12:56 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
testcase for a clear text signature (gpg --clearsign file) (249 bytes, application/pgp-signature)
2010-01-29 12:51 UTC, Daniel Leidert 		Details
testcase for an ascii armored public key (gpg --armor -o key.asc --export $key) (1.60 KB, application/pgp-keys)
2010-01-29 12:53 UTC, Daniel Leidert 		Details
View All

Description Sebastian Dröge (slomo) 2007-04-23 03:51:18 UTC 
Hi,
the .asc extension for PGP files is not really managed well currently. It's only registred for application/pgp-encrypted but people also use it for ASCII signatures and keys.

The same applies for the .gpg and .pgp extensions.

The current behaviour makes it impossible to open a ASCII signature file from nautilus as the extension and content differ.

Giving the 3 extensions to all 3 types won't give the desired behaviour in nautilus though, it still believes that the .asc extension maps to the encrypted files and doesn't want to open the file because extension and content differ.


Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/105874

Bye
Comment 1 Bastien Nocera 2009-04-20 10:44:35 UTC 
Patch? Test case?
Comment 2 Daniel Leidert 2010-01-29 12:51:12 UTC 
Created attachment 32909 [details]
testcase for a clear text signature (gpg --clearsign file)
Comment 3 Daniel Leidert 2010-01-29 12:53:10 UTC 
Created attachment 32910 [details]
testcase for an ascii armored public key (gpg --armor -o key.asc --export $key)
Comment 4 Daniel Leidert 2010-01-29 12:56:32 UTC 
My last tests resturn the correct results with standard::content-type (testcases have been attached). To me this looks like the issue has been fixed. Setting to resolved/fixed.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.