On Mon, 25 Nov 2019 08:44, Werner Koch said:
> Thanks. I don't see that INSIDE_EMACS is propagated and I can duplicate
My fault. We pass the the envvars to pinentry using setnev in an atfork
handler. Thus we do not see them in the Assuan log. I added some
logging to so that we can now see wit
* Werner Koch:
> I will look into this today so that a possible fix can go into 2.2.18.
Thanks a lot, Werner.
-Ralph
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
On Sat, 16 Nov 2019 18:22, Ralph Seichter said:
> ipc". I added the latter, and the resulting log file is available via
> https://seichter.de/aegi6bee9eShu/gpg-agent.log . Note that I killed
Thanks. I don't see that INSIDE_EMACS is propagated and I can duplicate
that problem here. I will look i
* Ralph Seichter:
> https://seichter.de/aegi6bee9eShu/gpg-agent.log
Gentle bump, because I posted this a week ago. Did you have a chance to
examine the log, Werner?
-Ralph
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailm
* Werner Koch:
> You forgot to _add_
>
> debug-pinentry
> debug ipc
> verbose
>
> to gpg-agent.conf.
Here's the gpg-agent.conf I used:
default-cache-ttl
max-cache-ttl
no-allow-mark-trusted
enable-ssh-support
pinentry-program /home/xyz/bin/pinentry-wrapper
debug-pinentry
log-fi
On Fri, 15 Nov 2019 21:45, Ralph Seichter said:
> gpg-agent[27187]: failed to read the secret key
> gpg-agent[27187]: command 'PKDECRYPT' failed: Timeout
You forgot to _add_
debug-pinentry
debug ipc
verbose
to gpg-agent.conf. (The "debug ipc" is helpful because it shows what
gpg is request
* Werner Koch:
> INSIDE_EMACS support is in GnUPG since 2.1.5 (4 years ago). It seems
> that for whatever reasons Emacs does not pass that envvar on.
Perhaps I need to build Emacs "by hand" to get full control over all
options, instead of relying on the existing Gentoo ebuild. Not that I
want to
On Thu, 14 Nov 2019 19:54, Ralph Seichter said:
> $ cat /tmp/pinentry-wrapper.log
> INSIDE_EMACS is ''
Pinentry consideres that it is not run from Emacs and thus it does not
forward requests to Emacs but uses the standard pinentry (or should
return an error for pinentry-emacs). INSIDE_EMACS
* Filipp Gunbin via Gnupg-users:
> I see this in NEWS for Emacs 27.1 (unreleased master).
>
> --8<---cut here---start->8---
> *** 'epa-pinentry-mode' is renamed to 'epg-pinentry-mode'.
> It now applies to epg functions as well as epa functions.
I tried both epa
* Werner Koch via Gnupg-users:
> ${TMPDIR-/tmp}/emacs$(id -u)/pinentry
The socket exists and the permissions look OK (read/write access for my
Linux user).
> If you insert a pinentry wrapper, can you see the INSIDE_EMACS envvar?
I just tried the following wrapper script:
#!/usr/bin/env bash
On 13/11/2019 17:58 +0100, Ralph Seichter wrote:
> * Filipp Gunbin via Gnupg-users:
>
>> I have 2.2.17 and it works with empty gpg-agent.conf and just this
>> line in .emacs:
>> (setq epg-pinentry-mode 'loopback)
>
> I use the same GnuPG version, but the Emacs variable setting you
> suggested make
Sorry, previous message went unfinished.
On 13/11/2019 17:58 +0100, Ralph Seichter wrote:
> I use the same GnuPG version, but the Emacs variable setting you
> suggested makes no difference for me. That's Emacs version 26.3,
> which I should have mentioned earlier.
I see this in NEWS for Emacs 27
On Wed, 13 Nov 2019 17:58, Ralph Seichter said:
> I use the same GnuPG version, but the Emacs variable setting you
> suggested makes no difference for me. That's Emacs version 26.3,
> which I should have mentioned earlier.
Yet another regression in Emacs? I am still cursing over 26.
Fortunately
* raf via Gnupg-users:
> Wherever it needs to be to get added to the gpg command line when
> invoked from within emacs.
As far as I can tell, that's what epa-pinentry-mode is used for (which I
tried unsuccessfully, as stated in my OP). I think I have tried every
EasyPG trick and workaround that I
Ralph Seichter wrote:
> * raf via Gnupg-users:
>
> > Does "--pinentry-mode loopback" make any difference?
>
> Where exactly do you suggest I add this option?
>
> -Ralph
Wherever it needs to be to get added to the gpg command line
when invoked from within emacs.
Or as a setting in gpg's config
* Filipp Gunbin via Gnupg-users:
> I have 2.2.17 and it works with empty gpg-agent.conf and just this
> line in .emacs:
> (setq epg-pinentry-mode 'loopback)
I use the same GnuPG version, but the Emacs variable setting you
suggested makes no difference for me. That's Emacs version 26.3,
which I sh
* raf via Gnupg-users:
> Does "--pinentry-mode loopback" make any difference?
Where exactly do you suggest I add this option?
-Ralph
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Which version of GnuPG are you using? I have 2.2.17 and it works with
empty gpg-agent.conf and just this line in .emacs:
(setq epg-pinentry-mode 'loopback)
Filipp
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listin
Ralph Seichter wrote:
> I asked about the following on the Notmuch mailing list first, and
> Daniel Kahn Gillmor offered some advice, but the issue is not yet
> resolved. I'm hoping for additional input from the GnuPG community.
>
> I use Dovecot with a Maildir-based message store, allowing me to
I asked about the following on the Notmuch mailing list first, and
Daniel Kahn Gillmor offered some advice, but the issue is not yet
resolved. I'm hoping for additional input from the GnuPG community.
I use Dovecot with a Maildir-based message store, allowing me to access
my mail using various IMA
20 matches
Mail list logo