Ticket #2355: 0001-Update-man-page-for-new-UseBridges-tristate.patch

File 0001-Update-man-page-for-new-UseBridges-tristate.patch, 1.4 KB (added by anonym, 8 years ago)

Update man page for new UseBridges tristate behaviour.

  • doc/tor.1.txt

    From 121276156bcdaa679dbeeade9d5cbd17d6811a6e Mon Sep 17 00:00:00 2001
    From: anonym <anonym@lavabit.com>
    Date: Mon, 30 May 2011 23:52:02 +0200
    Subject: [PATCH] Update man page for new UseBridges tristate behaviour.
    
    ---
     doc/tor.1.txt |   10 +++++++---
     1 files changed, 7 insertions(+), 3 deletions(-)
    
    diff --git a/doc/tor.1.txt b/doc/tor.1.txt
    index 8fe4fe8..5012a95 100644
    a b The following options are useful only for clients (that is, if 
    708708    from the configured bridge authorities when feasible. It will fall back to
    709709    a direct request if the authority responds with a 404. (Default: 0)
    710710
    711 **UseBridges** **0**|**1**::
    712     When set, Tor will fetch descriptors for each bridge listed in the "Bridge"
     711**UseBridges** **0**|**1**|**auto**::
     712    Make Tor fetch descriptors for each bridge listed in the "Bridge"
    713713    config lines, and use these relays as both entry guards and directory
    714     guards. (Default: 0)
     714    guards. If the option is 1, bridges must be used and if no bridges are
     715    configured Tor will not make any connections until a bridge is configured;
     716    if it's "auto", Tor will use bridges if any are configured, otherwise it
     717    will connect directly to the Tor network; if it's 0, bridges are not used
     718    at all. (Defaults to auto)
    715719
    716720**UseEntryGuards** **0**|**1**::
    717721    If this option is set to 1, we pick a few long-term entry servers, and try