From: "Peter Münster" <pmlists@free.fr>
To: info-gnus-english@gnu.org
Subject: Re: Passphrase caching for GnuPG in Emacs?
Date: Wed, 23 Dec 2015 15:00:20 +0100 [thread overview]
Message-ID: <87wps5s1sb.fsf@free.fr> (raw)
In-Reply-To: <loom.20151222T225103-271@post.gmane.org>
On Tue, Dec 22 2015, Greg Bell wrote:
> Note to everybody trying to get this to work - I noticed that passphrases
> entered into pinentry-curses (0.8.3) don't get cached by gpg-agent for some
> reason. Using pinentry-gtk or pinentry-curses, they do. Weird, I know.
There is also this nice tool: /usr/lib64/gpg-preset-passphrase
--
Peter
next prev parent reply other threads:[~2015-12-23 14:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 16:00 Jens Lechtenboerger
2015-11-09 8:45 ` tomas
2015-11-09 13:47 ` Stefan Monnier
2015-11-09 13:45 ` tomas
2015-11-09 13:55 ` Jens Lechtenboerger
2015-11-09 13:50 ` tomas
2015-11-11 8:15 ` Kevin Brubeck Unhammer
2015-11-12 16:43 ` Jens Lechtenboerger
2015-11-13 8:24 ` Kevin Brubeck Unhammer
2015-12-22 21:58 ` Greg Bell
2015-12-23 14:00 ` Peter Münster [this message]
2016-01-05 15:40 ` Teemu Likonen
2016-01-05 15:58 ` Jens Lechtenboerger
2016-01-05 18:16 ` Jude DaShiell
2016-01-05 19:06 ` Teemu Likonen
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=87wps5s1sb.fsf@free.fr \
--to=pmlists@free.fr \
--cc=info-gnus-english@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.
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 NNTP newsgroup(s).