[PATCH] doc: clarify dirmngr use-tor documentation

Daniel Kahn Gillmor dkg at fifthhorseman.net
Wed May 8 13:57:42 CEST 2019


On Wed 2019-05-08 08:18:57 +0200, Werner Koch wrote:
> On Fri,  3 May 2019 10:50, dkg at fifthhorseman.net said:
>
>> This isn't "extra hard" though -- it just means "gpgconf --kill dirmngr"
>> instead of "gpgconf --reload dirmngr", right?  (or SIGTERM instead of
>> SIGHUP)
>
> GPA and Kleopatra can do an reload automatically on changing an option.
> They don't provide a GUI element to restart dirmngr.

so if you change this option in GPA or Kleopatra, it doesn't actually
change?  That sounds perplexing.

>> Is this marginal increase in "hardness" worth the additional confusion
>> and complexity in configuration?
>
> Probably not; we may change it in 2.3

Thanks.  I've opened https://dev.gnupg.org/T4488 to track this issue.

         --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20190508/3d129af0/attachment.sig>


More information about the Gnupg-devel mailing list