GNU bug report logs -
#1471
23.0.60; Visiting GnuPG-encrypted file yields "file exists, but cannot be read"
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 1471 in the body.
You can then email your comments to 1471 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#1471
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
Eric Hanchrow <eric.hanchrow <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
Emacs Bugs <bug-gnu-emacs <at> gnu.org>
.
Full text and
rfc822 format available.
Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):
Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.
Your bug report will be posted to the emacs-pretest-bug <at> gnu.org mailing list.
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
At the shell:
$ cd /usr/local/src/emacs-via-git/src/
create a tiny encrypted file.
$ echo Fee fi fo fum | gpg --symmetric > decrypt-me.gpg
gpg: gpg-agent is not available in this session
You can't see it in this transcript, but I typed a very short passphrase: "foo"
Proof that the file is indeed encrypted:
$ cat decrypt-me.gpg
-----BEGIN PGP MESSAGE-----
Version: GnuPG v1.4.9 (GNU/Linux)
jA0EAwMCJkAO8t1a89pgySSta9bxO023orfaXtK+Y0RuUP+8ohMfpLLgVlYWiTeN
sX8mKnE=
=HGzp
-----END PGP MESSAGE-----
Proof that I haven't forgotten the passphrase:
$ gpg --decrypt < decrypt-me.gpg
gpg: CAST5 encrypted data
gpg: gpg-agent is not available in this session
Enter passphrase: gpg: encrypted with 1 passphrase
Fee fi fo fum
gpg: WARNING: message was not integrity protected
Now let's visit the file in emacs:
$ ./emacs -Q -nw
I then typed C-x C-f decrypt-me.gpg RET. Emacs prompted me for the
passphrase for symmetric encryption, as I'd expect. I entered it, and
then instead of seeing "Fee fi fo fum" in the buffer, as I'd expected, I
saw an error in the echo area: "File exists, but cannot be read".
If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
`bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
/usr/local/src/emacs-via-git/etc/DEBUG for instructions.
In GNU Emacs 23.0.60.9 (i686-pc-linux-gnu, GTK+ Version 2.14.4)
of 2008-12-01 on debian
configured using `configure '--enable-maintainer-mode' '--with-xpm=yes' '--with-jpeg=no' '--with-gif=no' '--with-tiff=no' '--with-xft' '--with-x-toolkit=gtk''
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: nil
value of $XMODIFIERS: nil
locale-coding-system: utf-8-unix
default-enable-multibyte-characters: t
Major mode: Emacs-Lisp
Minor modes in effect:
erc-ring-mode: t
erc-pcomplete-mode: t
erc-netsplit-mode: t
smerge-mode: t
eldoc-mode: t
erc-button-mode: t
erc-fill-mode: t
erc-stamp-mode: t
erc-autojoin-mode: t
erc-track-mode: t
erc-track-minor-mode: t
erc-match-mode: t
erc-log-mode: t
erc-services-mode: t
erc-networks-mode: t
erc-irccontrols-mode: t
erc-noncommands-mode: t
erc-readonly-mode: t
desktop-save-mode: t
recentf-mode: t
display-time-mode: t
global-auto-revert-mode: t
diff-auto-refine-mode: t
shell-dirtrack-mode: t
iswitchb-mode: t
tooltip-mode: t
mouse-wheel-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
global-auto-composition-mode: t
auto-composition-mode: t
auto-encryption-mode: t
auto-compression-mode: t
line-number-mode: t
transient-mark-mode: t
Recent input:
RET C-x k RET ESC x r e p o r t - e m a c s - b TAB
RET C-g C-x b i n i RET ESC < C-s g p g C-s C-s C-s
C-s C-a C-s e a s y C-s C-a ESC x ESC p RET
Recent messages:
Partially completed
/home/erich/private/: 0% (0/19181)
File exists, but cannot be read
/home/erich/private/: 0% (0/19181)
File exists, but cannot be read
/home/erich/private/: 0% (0/19181)
File exists, but cannot be read
Quit
Mark set
Mark saved where search started [2 times]
--
If you can't change your underwear, can you be sure you have any?
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#1471
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
Daiki Ueno <ueno <at> unixuser.org>
:
Extra info received and forwarded to list. Copy sent to
Emacs Bugs <bug-gnu-emacs <at> gnu.org>
.
Full text and
rfc822 format available.
Message #10 received at 1471 <at> emacsbugs.donarmstrong.com (full text, mbox):
>>>>> In <87hc5mjzex.fsf <at> offby1.atm01.sea.blarg.net>
>>>>> Eric Hanchrow <eric.hanchrow <at> gmail.com> wrote:
> At the shell:
> $ cd /usr/local/src/emacs-via-git/src/
> create a tiny encrypted file.
> $ echo Fee fi fo fum | gpg --symmetric > decrypt-me.gpg
> gpg: gpg-agent is not available in this session
> You can't see it in this transcript, but I typed a very short passphrase: "foo"
> Proof that the file is indeed encrypted:
> $ cat decrypt-me.gpg
> -----BEGIN PGP MESSAGE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> jA0EAwMCJkAO8t1a89pgySSta9bxO023orfaXtK+Y0RuUP+8ohMfpLLgVlYWiTeN
> sX8mKnE=
> =HGzp
> -----END PGP MESSAGE-----
> Proof that I haven't forgotten the passphrase:
> $ gpg --decrypt < decrypt-me.gpg
> gpg: CAST5 encrypted data
> gpg: gpg-agent is not available in this session
> Enter passphrase: gpg: encrypted with 1 passphrase
> Fee fi fo fum
> gpg: WARNING: message was not integrity protected
> Now let's visit the file in emacs:
> $ ./emacs -Q -nw
> I then typed C-x C-f decrypt-me.gpg RET. Emacs prompted me for the
> passphrase for symmetric encryption, as I'd expect. I entered it, and
> then instead of seeing "Fee fi fo fum" in the buffer, as I'd expected, I
> saw an error in the echo area: "File exists, but cannot be read".
I can't reproduce it. Could you please try again with
(setq epg-debug t)
and provide the content of the " *epg-debug*" buffer?
Regards,
--
Daiki Ueno
Tags added: moreinfo
Request was from
Glenn Morris <rgm <at> gnu.org>
to
control <at> emacsbugs.donarmstrong.com
.
(Fri, 12 Dec 2008 04:10:05 GMT)
Full text and
rfc822 format available.
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#1471
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
Rudi Schlatte <rudi <at> constantly.at>
:
Extra info received and forwarded to list. Copy sent to
Emacs Bugs <bug-gnu-emacs <at> gnu.org>
.
Full text and
rfc822 format available.
Message #17 received at 1471 <at> emacsbugs.donarmstrong.com (full text, mbox):
[Message part 1 (text/plain, inline)]
Just as additional datapoint: I saw the reported behavior too, at
roughly the same time as the original report, but not in an emacs
compiled from yesterday's git mirror. Opening a file encrypted with
gpg works as expected again for me again.
Rudi
[smime.p7s (application/pkcs7-signature, attachment)]
Reply sent
to
Daiki Ueno <ueno <at> unixuser.org>
:
You have taken responsibility.
(Wed, 17 Dec 2008 07:10:21 GMT)
Full text and
rfc822 format available.
Notification sent
to
Eric Hanchrow <eric.hanchrow <at> gmail.com>
:
bug acknowledged by developer.
(Wed, 17 Dec 2008 07:10:21 GMT)
Full text and
rfc822 format available.
Message #22 received at 1471-done <at> emacsbugs.donarmstrong.com (full text, mbox):
>>>>> In <84E12317-4EF9-48A6-9D17-F9ABAB090617 <at> constantly.at>
>>>>> Rudi Schlatte <rudi <at> constantly.at> wrote:
> Just as additional datapoint: I saw the reported behavior too, at
> roughly the same time as the original report, but not in an emacs
> compiled from yesterday's git mirror. Opening a file encrypted with
> gpg works as expected again for me again.
Thanks for the information. I also got the same report from Eric
privately. He said that the bug seems like fixed at some time between
the following dates:
Date: Tue Dec 2 01:12:39 2008 +0000
Date: Wed Dec 3 21:57:10 2008 +0000
Since I had not added any change (except a wording patch) in that time
span, I suspect other part of Emacs affected the behavior.
Now I'm trying to close this bug.
Regards,
--
Daiki Ueno
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> emacsbugs.donarmstrong.com
.
(Wed, 14 Jan 2009 15:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 16 years and 158 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.