[Bug 66134] Not happy decrypting ascii-armored files with the standard .asc extension

peridot peridot.faceted at gmail.com
Wed Dec 20 16:41:36 UTC 2006

Public bug reported:

Binary package hint: seahorse

When I double-click on one of the (many) encrypted files I have (all
ascii-armoured, all with the extension .asc) I get a long rude message
from nautilus telling me the file doesn't have the extension its MIME
type says it should and so it's probably a trojan. It does not tell me
what extension I should rename the file to, and it won't decrypt the

I can decrypt the file just fine by renaming it to .pgp; .asc is the
extension produced by the KDE tool I used to encrypt the files (and it's
a standard extension for ascii-armoured files, not just signatures).

More generally, the extension (.pgp vs. .asc) is not really of any use
in determining what the file contains (encrypted message, signed
message, detached signature, public keys, private keys, some combination
of the above...); the correct approach would be to claim .pgp .asc and
.sig and have seahorse identify what kind of file it is.

This is the version of seahorse (and nautilus etcetera) in Dapper Drake
LTS, 0.9.3.

** Affects: shared-mime-info (Ubuntu)
     Importance: Undecided
         Status: Fix Released

Not happy decrypting ascii-armored files with the standard .asc extension

More information about the desktop-bugs mailing list