[pkg-gnupg-maint] Bug#801247: [gpg-agent] Env variables not available in some unknown cases
aeris
aeris at imirhil.fr
Wed Feb 15 15:42:47 UTC 2017
Package: gpg-agent
--- Please enter the report below this line. ---
Hi,
Seems not related to pinentry-gnome3 directly.
I use a custom pinentry python script (not using any gpg provided pinentry) to
use kwallet, and I think I hit the same trouble.
Triggering pinentry invocation from shell (gpg) or desktop app (kmail), all is
good. Triggering pinentry through gpg-agent ssh export, fails.
The difference in my case is env variable.
On the working case :
LANG LISTEN_FDNAMES MANAGERPID SHELL XDG_RUNTIME_DIR JOURNAL_STREAM
LISTEN_FDS LISTEN_PID XAUTHORITY LOGNAME USER PATH XMODIFIERS HOME
GTK_IM_MODULE _assuan_pipe_connect_pid DBUS_SESSION_BUS_ADDRESS INVOCATION_ID
On the not working case :
LANG LISTEN_FDNAMES MANAGERPID SHELL XDG_RUNTIME_DIR JOURNAL_STREAM
LISTEN_FDS LISTEN_PID LOGNAME USER PATH HOME _assuan_pipe_connect_pid
INVOCATION_ID
Missing between the two :
XAUTHORITY XMODIFIERS GTK_IM_MODULE DBUS_SESSION_BUS_ADDRESS
Seems all X session related env variable are not propagated.
Pinentry is from the same gpg-agent, I don’t kill it between invocation.
There is trouble whatever the first call you do (shell/desktop or ssh), shell/
desktop always work even on a agent started with ssh and ssh always fail even
on a shell/desktop started agent.
In my case, forcing manually the DBUS_SESSION_BUS_ADDRESS on my script resolve
the trouble but ugly workaround (need to edit the script for each new
session…). Without this variable, KWallet.Wallet.OpenWallet fails, perhaps the
same thing happens with gnome wallet.
So, it’s seems something on gpg-agent which filter env variable based on an
unknown criteria, probably related to X session.
As far I as know, I don’t faced this trouble some weeks ago with same
configuration, so perhaps a regression somewhere. It works on my setup on
2016-12-29.
I try to downgrade to gnupg 2.1.16-3 (used until 2017-01-04), but no more
luck. This fact lets me to thing it’s perhaps not at all related to gnupg.
The process which run gpg-agent is systemd in my case.
/lib/systemd/systemd --user
\_ /usr/bin/dirmngr --supervised
\_ /usr/bin/gpg-agent --supervised
--- System information. ---
Architecture:
Kernel: Linux 4.9.0-1-amd64
Debian Release: 9.0
515 testing vwakviie2ienjx6t.onion
510 stable-updates vwakviie2ienjx6t.onion
505 stable vwakviie2ienjx6t.onion
505 stable sgvtcaew4bxjd7ln.onion
500 unstable vwakviie2ienjx6t.onion
100 jessie-backports vwakviie2ienjx6t.onion
1 experimental vwakviie2ienjx6t.onion
--- Package information. ---
ii gnupg 2.1.16-3
amd64 GNU privacy guard - a free PGP replacement
ii gnupg-agent 2.1.16-3
amd64 GNU privacy guard - cryptographic agent
ii gnupg2 2.1.16-3
all GNU privacy guard - a free PGP replacement (dummy transitional
package)
ii gnupg 2.1.18-3
amd64 GNU privacy guard - a free PGP replacement
ii gnupg-agent 2.1.18-3
amd64 GNU privacy guard - cryptographic agent
ii gnupg2 2.1.18-3
all GNU privacy guard - a free PGP replacement (dummy transitional
package)
--
Aeris
Individual crypto-terrorist group self-radicalized on the digital Internet
https://imirhil.fr/
Protect your privacy, encrypt your communications
GPG : EFB74277 ECE4E222
OTR : 5769616D 2D3DAC72
https://café-vie-privée.fr/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20170215/d147d0f6/attachment.sig>
More information about the pkg-gnupg-maint
mailing list