[prev in list] [next in list] [prev in thread] [next in thread]
List: gnupg-users
Subject: Re: dirmngr timeout
From: Laszlo Papp <lpapp () kde ! org>
Date: 2018-04-13 10:00:59
Message-ID: CAOMwXhNRv+tLUk-sv=jJn9-O9isqrc1ZD5=wOkWAj=gjs151zQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Fri, Apr 13, 2018 at 10:46 AM, Werner Koch <wk@gnupg.org> wrote:
> On Thu, 12 Apr 2018 15:45, lpapp@kde.org said:
>
> [Full quote trimmed]
> > It looks like if I run dirmngr manually, as follows, with
> honor-http-proxy,
> > gpg works:
> >
> > dirmngr --daemon
>
> It will also work if dirnmnr is automatically started by gpg or via
> gpgconf --launch dirmngr.
>
> > But when it is run as dirmngr --supervised, gpg does not seem to work
> until
> > the http-proxy is specified in the config explicitly.
>
> It seems that systemd has a different view on the envvars and thus your
> somewhere set http_proxy=foo:port is not inherited by dirmngr.
> According to IRC there are ways to set envvars for specific systemd
> actions. If can find them out it would be nice if you can document that
> in a reply.
>
Yes, I meant to reply yesterday after solving this.
systemd --user import-environment http_proxy
is what I used.
>
>
> Shalom-Salam,
>
> Werner
>
>
> --
> # Please read: Daniel Ellsberg - The Doomsday Machine #
> Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
>
[Attachment #5 (text/html)]
<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr \
13, 2018 at 10:46 AM, Werner Koch <span dir="ltr"><<a href="mailto:wk@gnupg.org" \
target="_blank">wk@gnupg.org</a>></span> wrote:<br><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, 12 Apr \
2018 15:45, <a href="mailto:lpapp@kde.org">lpapp@kde.org</a> said:<br> <br>
[Full quote trimmed]<br>
<span class="">> It looks like if I run dirmngr manually, as follows, with \
honor-http-proxy,<br> > gpg works:<br>
><br>
> dirmngr --daemon<br>
<br>
</span>It will also work if dirnmnr is automatically started by gpg or via<br>
gpgconf --launch dirmngr.<br>
<span class=""><br>
> But when it is run as dirmngr --supervised, gpg does not seem to work until<br>
> the http-proxy is specified in the config explicitly.<br>
<br>
</span>It seems that systemd has a different view on the envvars and thus your<br>
somewhere set http_proxy=foo:port is not inherited by dirmngr.<br>
According to IRC there are ways to set envvars for specific systemd<br>
actions. If can find them out it would be nice if you can document that<br>
in a reply.<br></blockquote><div><br></div><div>Yes, I meant to reply yesterday after \
solving this.</div><div><br></div><div>systemd --user import-environment \
http_proxy</div><div><br></div><div>is what I used.</div><div> </div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> <br>
<br>
Shalom-Salam,<br>
<div class="HOEnZb"><div class="h5"><br>
Werner<br>
<br>
<br>
-- <br>
# Please read: Daniel Ellsberg - The Doomsday Machine #<br>
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.<br>
</div></div></blockquote></div><br></div></div>
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
[prev in list] [next in list] [prev in thread] [next in thread]