Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org, info-gnus-english@gnu.org
Subject: Re: Passphrase caching for GnuPG in Emacs?
Date: Mon, 9 Nov 2015 14:45:20 +0100	[thread overview]
Message-ID: <20151109134520.GB21743@tuxteam.de> (raw)
In-Reply-To: <jwvmvuns2uw.fsf-monnier+gmane.emacs.help@gnu.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Nov 09, 2015 at 08:47:42AM -0500, Stefan Monnier wrote:
> > It seems there's a command-line pinentry these days.  From Emacs,
> > my dream would be that it's Emacs which handles user interaction.
> 
> IIUC with a recent enough Emacs and recent enough GnuPG, Emacs will/can
> indeed play the role of "pinentry agent" (so it provides the usual
> Emacs UI, and along with that the usual Emacs insecurity of course).

Phew :-)

Thanks
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlZAo3AACgkQBcgs9XrR2kYLTwCfemqJ2toz6PAh8+6ORXe7l84z
zPwAnjDXhrVPQQ6ltR+5o5TltryOIXSZ
=HXXL
-----END PGP SIGNATURE-----



  reply	other threads:[~2015-11-09 13:45 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 [this message]
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
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=20151109134520.GB21743@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=info-gnus-english@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).