From: Taylor Yu Date: Thu, 9 Jan 2020 16:41:26 +0000 (-0600) Subject: manpage: GuardfractionFile is authority-only X-Git-Tag: tor-0.4.3.1-alpha~37^2~2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=4e597673b727a059550ddbdfe9b0c6f38f717f61;p=thirdparty%2Ftor.git manpage: GuardfractionFile is authority-only Only directory authorities use the GuardfractionFile option, so move it to that section. Part of ticket 32846. --- diff --git a/doc/tor.1.txt b/doc/tor.1.txt index c843112d01..26098f7349 100644 --- a/doc/tor.1.txt +++ b/doc/tor.1.txt @@ -1954,12 +1954,6 @@ The following options are useful only for clients (that is, if Authorities or Single Onion Services. In these cases, this option is ignored. (Default: 1) -//Out of order because it logically belongs with the UseGuardFraction option -[[GuardfractionFile]] **GuardfractionFile** __FILENAME__:: - V3 authoritative directories only. Configures the location of the - guardfraction file which contains information about how long relays - have been guards. (Default: unset) - [[UseGuardFraction]] **UseGuardFraction** **0**|**1**|**auto**:: This option specifies whether clients should use the guardfraction information found in the consensus during path @@ -2994,6 +2988,11 @@ on the public Tor network. be written to temporary file, then renamed to the configured filename. (Default: unset) +[[GuardfractionFile]] **GuardfractionFile** __FILENAME__:: + V3 authoritative directories only. Configures the location of the + guardfraction file which contains information about how long relays + have been guards. (Default: unset) + [[V3AuthUseLegacyKey]] **V3AuthUseLegacyKey** **0**|**1**:: If set, the directory authority will sign consensuses not only with its own signing key, but also with a "legacy" key and certificate with a