Browse Source

Fix TestingDirAuthVoteHSDir docs: HSDir flag needs DirPort

Fix an error in the manual page and comments for
TestingDirAuthVoteHSDir, which suggested that a
HSDir required "ORPort connectivity". While this is true,
it is in no way unique to the HSDir flag. Of all the flags,
only HSDirs need a DirPort configured in order for the
authorities to assign that particular flag.

Fixed as part of 14882. Patch by "teor".
Bugfix on 0.2.6.3 (f9d57473e1ff on 10 January 2015).
teor 9 years ago
parent
commit
0cb82013cc
2 changed files with 2 additions and 2 deletions
  1. 1 1
      doc/tor.1.txt
  2. 1 1
      src/or/or.h

+ 1 - 1
doc/tor.1.txt

@@ -2347,7 +2347,7 @@ The following options are used for running a testing Tor network.
 [[TestingDirAuthVoteHSDir]] **TestingDirAuthVoteHSDir** __node__,__node__,__...__::
     A list of identity fingerprints and country codes and
     address patterns of nodes to vote HSDir for regardless of their
-    uptime and ORPort connectivity. See the **ExcludeNodes** option for more
+    uptime and DirPort. See the **ExcludeNodes** option for more
     information on how to specify nodes.
  +
     In order for this option to have any effect, **TestingTorNetwork**

+ 1 - 1
src/or/or.h

@@ -4100,7 +4100,7 @@ typedef struct {
   routerset_t *TestingDirAuthVoteGuard;
 
   /** Relays in a testing network which should be voted HSDir
-   * regardless of uptime and ORPort connectivity.
+   * regardless of uptime and DirPort.
    * Respects VoteOnHidServDirectoriesV2. */
   routerset_t *TestingDirAuthVoteHSDir;