From: Jens Lechtenboerger <jens.lechtenboerger@fsfe.org>
To: 20634@debbugs.gnu.org
Subject: bug#20634: 25.0.50; Conflict between Tramp and EasyPG
Date: Sat, 23 May 2015 17:23:38 +0200 [thread overview]
Message-ID: <87fv6n8ghx.fsf@informationelle-selbstbestimmung-im-internet.de> (raw)
Hi there,
I use EasyPG for transparent access of encrypted files with
extension .gpg. If I copy an encrypted file, say test.gpg, via ssh
(Tramp) to a remote location, then I’m asked what public key to use
for encryption (none for symmetric encryption), and the encrypted
file is encrypted again, rendering it useless from within Emacs.
(If I open the remote file via Tramp, the outer layer of encryption
is removed, and I see the original encrypted file.)
Recipe:
0. Encrypt a file: test.gpg
1. emacs -Q
2. Open directory of test.gpg (C-x C-f).
3. Copy (C) the file to a remote location
(e.g., /user@localhost:/tmp).
The key chooser opens. Copy is cancelled if I cancel the choice.
Otherwise, a remote file is created, which is not a copy but an
encrypted file with two layers of encryption.
4. Open the remote file (C-x C-f /user@localhost:/tmp/test.gpg).
Observe encrypted data.
In contrast, if I copy an encrypted file to a local directory, it is
copied without extra encryption.
Note also that if I copy a plaintext file (test.txt) locally to one
with gpg extension (test.gpg), it remains a plaintext file. If I
copy that to a remote location, it gets encrypted. This may be a
bug or a feature, but is certainly inconsistent behavior.
Best wishes
Jens
next reply other threads:[~2015-05-23 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 15:23 Jens Lechtenboerger [this message]
2015-05-24 16:24 ` bug#20634: 25.0.50; Conflict between Tramp and EasyPG Michael Albinus
2015-05-25 10:47 ` Michael Albinus
2015-05-25 16:32 ` Jens Lechtenboerger
2015-05-25 18:35 ` Michael Albinus
[not found] ` <87k2vva0lw.fsf@informationelle-selbstbestimmung-im-internet.de>
2015-05-26 14:17 ` Michael Albinus
2015-05-26 14:31 ` Jens Lechtenboerger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fv6n8ghx.fsf@informationelle-selbstbestimmung-im-internet.de \
--to=jens.lechtenboerger@fsfe.org \
--cc=20634@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.