From: Pierre Neidhardt <ambrevar@gmail.com>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Missing pinentry-emacs for gpg-agent?
Date: Tue, 27 Mar 2018 23:58:09 +0530 [thread overview]
Message-ID: <87woxxbcg6.fsf@gmail.com> (raw)
In-Reply-To: <87d0zpecv3.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
Oleg Pykhalov <go.wigust@gmail.com> writes:
> I'm sorry to steal a potential contribution to Guix, but you could try:
>
> ‘M-x view-emacs-news’:
>
> * New Modes and Packages in Emacs 25.1
>
> ** pinentry.el allows GnuPG passphrase to be prompted through the
> minibuffer instead of a graphical dialog, depending on whether the
> gpg command is called from Emacs (i.e., INSIDE_EMACS environment
> variable is set). This feature requires newer versions of GnuPG
> (2.1.5 or later) and Pinentry (0.9.5 or later). To use this
> feature, add "allow-emacs-pinentry" to "~/.gnupg/gpg-agent.conf" and
> reload the configuration with "gpgconf --reload gpg-agent".
Unless I'm mistaken, this won't work without pinentry-emacs when gpg is
used to decrypt data, e.g. `gpg -d FILE`. I do not know about a
INSIDE_EMACS environment variable. How is it set?
--
Pierre Neidhardt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-03-27 18:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 6:17 Missing pinentry-emacs for gpg-agent? Pierre Neidhardt
2018-03-27 9:53 ` Ludovic Courtès
2018-03-27 15:45 ` Alex Kost
2018-03-27 15:50 ` Oleg Pykhalov
2018-03-27 18:28 ` Pierre Neidhardt [this message]
2018-03-27 20:22 ` Vladimir Sedach
2018-03-28 4:49 ` Pierre Neidhardt
2018-03-28 7:04 ` Oleg Pykhalov
2018-03-28 7:17 ` Pierre Neidhardt
2018-03-28 8:29 ` Pierre Neidhardt
2018-03-29 7:30 ` Oleg Pykhalov
2018-03-29 7:23 ` Oleg Pykhalov
2018-03-29 8:44 ` Pierre Neidhardt
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=87woxxbcg6.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=go.wigust@gmail.com \
--cc=help-guix@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.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.