dirmngr timeout

[Laszlo Papp]

On Fri, Apr 13, 2018 at 10:46 AM, Werner Koch <wk at gnupg.org> wrote:

> On Thu, 12 Apr 2018 15:45, lpapp at 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20180413/84b114b1/attachment.html>