From: Barry Fishman <barry@ecubist.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Password prompt inside Emacs with epg-gpg-program -> "gpg2"?
Date: Wed, 10 Feb 2016 08:47:49 -0500 [thread overview]
Message-ID: <m3io1wad8a.fsf@ecube.ecubist.org> (raw)
In-Reply-To: mailman.4186.1455011693.843.help-gnu-emacs@gnu.org
On 2016-02-09 10:54:30 +0100, Joakim Jalap wrote:
> pinentry-emacs can be built from the pintry repo at
> git.gnupg.org/pintry.git.
>
> Together with the correct envvars set, this allows us to input passwords
> from Emacs, yes :)
>
> However this seems to be seen as a sort of hack, and it's disabled by
> default on Arch Linux, FreeBSD and Debian as it seems, so I have had to
> build it from source. I guess that alienates a lot of users though :/
But it *is* enabled by default in Arch, and included as a separate
package in Fedora.
For Arch, its even part of core:
$ pacman -Ss pinentry
core/pinentry 0.9.7-1 [installed]
Collection of simple PIN or passphrase entry dialogs which utilize the
Assuan protocol
$ pacman -Qo /usr/bin/pinentry-emacs
/usr/bin/pinentry-emacs is owned by pinentry 0.9.7-1
--
Barry Fishman
next prev parent reply other threads:[~2016-02-10 13:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 14:44 Password prompt inside Emacs with epg-gpg-program -> "gpg2"? Michael Heerdegen
2016-02-08 15:10 ` Teemu Likonen
2016-02-08 15:39 ` Michael Heerdegen
2016-02-08 17:00 ` Joakim Jalap
2016-02-08 17:54 ` Michael Heerdegen
2016-02-08 18:38 ` Joakim Jalap
2016-02-08 18:56 ` Michael Heerdegen
2016-02-08 19:07 ` Joakim Jalap
2016-02-08 20:26 ` Michael Heerdegen
2016-02-09 9:11 ` Joakim Jalap
2016-02-09 8:58 ` tomas
2016-02-09 1:01 ` Lars Ingebrigtsen
2016-02-09 3:23 ` Daiki Ueno
2016-02-09 3:49 ` Lars Ingebrigtsen
2016-02-09 7:02 ` Daiki Ueno
2016-02-09 22:50 ` Lars Ingebrigtsen
2016-02-09 9:54 ` Joakim Jalap
[not found] ` <mailman.4186.1455011693.843.help-gnu-emacs@gnu.org>
2016-02-10 13:47 ` Barry Fishman [this message]
2016-02-10 15:16 ` Joakim Jalap
2016-02-15 11:15 ` Lele Gaifax
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=m3io1wad8a.fsf@ecube.ecubist.org \
--to=barry@ecubist.org \
--cc=help-gnu-emacs@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).