GNU bug report logs -
#12923
24.2; epa-file--find-file-not-found-function: Opening input file: Can't decrypt, Exit
Previous Next
Reported by: Oleksandr Gavenko <gavenkoa <at> gmail.com>
Date: Sun, 18 Nov 2012 13:44:02 UTC
Severity: normal
Found in version 24.2
Fixed in version 29.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Oleksandr Gavenko <gavenkoa <at> gmail.com> writes:
> So Emacs break some usual convention used by gpg about .gpg extension...
>
> $ file /home/user/.gnupg/pubring.gpg
> /home/user/.gnupg/pubring.gpg: GPG key public ring
Oh, I didn't know that the file command defines such a magic:
# GnuPG
# The format is very similar to pgp
0 string \001gpg GPG key trust database
>4 byte x version %d
# Note: magic.mime had 0x8501 for the next line instead of 0x8502
0 beshort 0x8502 GPG encrypted data
!:mime text/PGP # encoding: data
# This magic is not particularly good, as the keyrings don't have true
# magic. Nevertheless, it covers many keyrings.
0 beshort 0x9901 GPG key public ring
!:mime application/x-gnupg-keyring
> I expect that Emacs open this file in any case (ever if it doesn't support
> some "standard" .gpg format - open it literary as fall back!).
The rationale of the current behavior (try decryption only) was that a
.gpg file may contain GPG packets which can have any type of GPG data
(encrypted, signed, public keys, ...) in theory.
If the above magic works well for typical use-cases, it might be worth
adding them to Emacs too.
Regards,
--
Daiki Ueno
This bug report was last modified 3 years and 170 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.