From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Cc: info-gnus-english@gnu.org
Subject: Re: Passphrase caching for GnuPG in Emacs?
Date: Mon, 9 Nov 2015 09:45:39 +0100 [thread overview]
Message-ID: <20151109084539.GB12671@tuxteam.de> (raw)
In-Reply-To: <87vb9cwkef.fsf@informationelle-selbstbestimmung-im-internet.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, Nov 08, 2015 at 05:00:56PM +0100, Jens Lechtenboerger wrote:
> Hi there,
>
> I plan to refactor the code used for GnuPG in the Message mode of
> Emacs [...]
> If I’m not mistaken (please let me know if I’m wrong), with GnuPG
> 2.x (and gpgsm) passphrases cannot be cached within Emacs as
> gpg-agent is started automatically and tries to invoke a pinentry
> program.
Just a question: how do you plan to handle this pinentry?
The last time I gave gpg 2 a try, a crude GTK dialog appeared from
nowhere (disrupting my command line workflow). I just ran away,
screaming.
It seems there's a command-line pinentry these days. From Emacs,
my dream would be that it's Emacs which handles user interaction.
Have you any ideas?
thanks
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlZAXTMACgkQBcgs9XrR2kY4DACfZk9kozGfkc5/QUuENtz+rVGx
2B0An3AG4k0MJl0bmBV7PZpYl7R+YOEj
=vhaT
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-11-09 8:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 16:00 Passphrase caching for GnuPG in Emacs? Jens Lechtenboerger
2015-11-09 8:45 ` tomas [this message]
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
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
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=20151109084539.GB12671@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@gnu.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).