Okay froods,
https://dev.gnupg.org/rGb5f356e9fba2d99909f8f54d7b7e6836bed87b68
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
pgpkuq5DgyTJT.pgp
Description: PGP signature
On Wed, 24 May 2017 23:36, d...@fifthhorseman.net said:
> full dirmngr flush on every network change -- in particular, that would
> mean that every time we join the network, we would be more likely to
> announce to the network about the various CRLs and keyservers that we're
Good point. That
On Wed 2017-05-24 16:14:22 +0200, Stefan Bühler wrote:
> On 05/24/2017 02:14 PM, Werner Koch wrote:
>> Hi!
>>
>> When you switch the laptop connection you should flush dirmngr anyway
>> and thus I do not consider the need to do this just for the resolver.
>>
>> gpgconf --reload dirmngr
>>
>>
Hi,
On 05/24/2017 02:14 PM, Werner Koch wrote:
> Hi!
>
> When you switch the laptop connection you should flush dirmngr anyway
> and thus I do not consider the need to do this just for the resolver.
>
> gpgconf --reload dirmngr
>
> in the ifup script should do that job. Note that gpgconf
Hi!
When you switch the laptop connection you should flush dirmngr anyway
and thus I do not consider the need to do this just for the resolver.
gpgconf --reload dirmngr
in the ifup script should do that job. Note that gpgconf won't start a
component on --reload or --kill if it is not yet
Package: dirmngr
Version: 2.1.18-6
Hi,
dirmngr doesn't reload /etc/resolv.conf but is a long-living process.
For laptop users resolv.conf might change more than once a day, and
having to remember or even knowing you have to kill/SIGHUP dirmngr is
not helping the gpg usecase...
When using
6 matches
Mail list logo
