From: Daiki Ueno <ueno@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: tzz@lifelogs.com, 15552@debbugs.gnu.org
Subject: bug#15552: 24.3.50; epa-file-cache-passphrase-for-symmetric-encryption not respected with GnuPG 2.x
Date: Thu, 10 Oct 2013 12:08:39 +0900 [thread overview]
Message-ID: <m3eh7t3jrc.fsf-ueno@gnu.org> (raw)
In-Reply-To: <jwvr4buzktz.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Wed, 09 Oct 2013 08:40:34 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> The docstring should prominently say that this var doesn't work with
> gpg2 because gpg2 does not let Emacs cache the passphrase (IIUC we
> can't make this var effective without changes in gpg2).
OK, I'll add it, though I'd also like to add a note saying that setting
this variable for gpg2 is kind of nonsense.
>> I didn't get the question correctly, then. Look at the matrix of
>> (info "(epa) Caching Passphrases"), check when a user is suggested to
>> "set up elisp passphrase cache".
>
> That repeats the fact that symmetric encryption is handled differently
> but still doesn't help me understand why.
Because passphrase caching feature for symmetric encryption is rather
new and not supported by gpg1 (yet).
next prev parent reply other threads:[~2013-10-10 3:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 17:56 bug#15552: 24.3.50; epa-file-cache-passphrase-for-symmetric-encryption not respected with GnuPG 2.x Teodor Zlatanov
2013-10-07 23:41 ` Daiki Ueno
2013-10-08 0:46 ` Ted Zlatanov
2013-10-08 3:14 ` Stefan Monnier
2013-10-08 7:03 ` Daiki Ueno
2013-10-08 10:47 ` Ted Zlatanov
2013-10-08 17:17 ` Stefan Monnier
2013-10-08 21:51 ` Daiki Ueno
2013-10-09 3:01 ` Stefan Monnier
2013-10-09 3:53 ` Daiki Ueno
2013-10-09 9:32 ` Ted Zlatanov
2013-10-09 12:40 ` Stefan Monnier
2013-10-10 3:08 ` Daiki Ueno [this message]
2013-10-10 13:25 ` Ted Zlatanov
2013-10-10 14:31 ` Stefan Monnier
2013-10-10 14:32 ` Stefan Monnier
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=m3eh7t3jrc.fsf-ueno@gnu.org \
--to=ueno@gnu.org \
--cc=15552@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=tzz@lifelogs.com \
/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.