From: Pankaj Jangid <pankaj@codeisgreat.org>
To: 45916@debbugs.gnu.org
Subject: bug#45916: 28.0.50; Inconsistent EasyPG behaviour when encrypting .gpg files
Date: Sat, 16 Jan 2021 15:10:44 +0530 [thread overview]
Message-ID: <m2turhcj8j.fsf@codeisgreat.org> (raw)
In-Reply-To: <m2y2gt71de.fsf@mb2.local.i-did-not-set--mail-host-address--so-tickle-me> (Pankaj Jangid's message of "Sat, 16 Jan 2021 13:35:33 +0530")
> 1. emacs -Q
> 2. eval ‘(defvar epg-pinentry-mode 'loopback)’
> 3. C-c C-f ~/x.gpg RET
> 4. Write some text
> 5. C-x C-s ; this prompts for selecting key and saves using that.
> 6. C-x k ;
> 7. C-c C-f ~/x.gpg RET ; open again
> 8. make some changes
> 9. C-x C-s ; asks for passphrase for symmetric key encryption
> Behaviour in step 5 and 9 should be same. _Or_ if the file was already
> saved encrypted with a public-key then it should use the same key again.
More info (it is fixed after invoking ‘M-x epa-file-select-keys’)
Now I opened ~/x.gpg again and invoke ‘M-x epa-file-select-keys’ and
selected the desired public key and saved (C-x C-s). Now it saved the
file using the public key.
I see that, when I open a .gpg file it sets a buffer-local variable
‘epa-file-encrypt-to’. Which makes it automatically use the public key
because the value of ‘epa-file-select-keys’ is nil (default).
And after I invoked ‘M-x epa-file-select-keys’, it is consistently
behaving as described in the manuals i.e. Step (9) is not asking for
symmetric key encryption passphrase any more.
Probably the ‘epa-file-encrypt-to’ was not being set earlier after
opening a .gpg file.
My question is - does invoking ‘M-x epa-file-select-keys’ save the
information somewhere on the filesystem? Only after invoking this the
behaviour got fixed.
next prev parent reply other threads:[~2021-01-16 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 8:05 bug#45916: 28.0.50; Inconsistent EasyPG behaviour when encrypting .gpg files Pankaj Jangid
2021-01-16 9:40 ` Pankaj Jangid [this message]
2022-05-09 14:23 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2turhcj8j.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=45916@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).