all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Pankaj Jangid <pankaj@codeisgreat.org>
Cc: 45916@debbugs.gnu.org
Subject: bug#45916: 28.0.50; Inconsistent EasyPG behaviour when encrypting .gpg files
Date: Mon, 09 May 2022 16:23:49 +0200	[thread overview]
Message-ID: <87bkw66ayy.fsf@gnus.org> (raw)
In-Reply-To: <m2turhcj8j.fsf@codeisgreat.org> (Pankaj Jangid's message of "Sat, 16 Jan 2021 15:10:44 +0530")

Pankaj Jangid <pankaj@codeisgreat.org> writes:

>> 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.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

I was unable to reproduce the bug in Emacs 29.

> 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.

Not that I can see...

Are you still seeing any issues in this area in recent Emacs versions?
There's been quite a few bug fixes in this area over the last year, if I
remember correctly.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2022-05-09 14:23 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
2022-05-09 14:23   ` Lars Ingebrigtsen [this message]

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=87bkw66ayy.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=45916@debbugs.gnu.org \
    --cc=pankaj@codeisgreat.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.