[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[or-cvs] r23896: {} we just need the pot files (translation/trunk/projects/manpages/po/templates)



Author: runa
Date: 2010-12-05 19:23:15 +0000 (Sun, 05 Dec 2010)
New Revision: 23896

Removed:
   translation/trunk/projects/manpages/po/templates/tor-resolve.1.po
   translation/trunk/projects/manpages/po/templates/tor.1.po
   translation/trunk/projects/manpages/po/templates/torify.1.po
Log:
we just need the pot files

Deleted: translation/trunk/projects/manpages/po/templates/tor-resolve.1.po
===================================================================
--- translation/trunk/projects/manpages/po/templates/tor-resolve.1.po	2010-12-05 19:16:01 UTC (rev 23895)
+++ translation/trunk/projects/manpages/po/templates/tor-resolve.1.po	2010-12-05 19:23:15 UTC (rev 23896)
@@ -1,154 +0,0 @@
-# SOME DESCRIPTIVE TITLE
-# Copyright (C) YEAR The Tor Project, Inc.
-# This file is distributed under the same license as the PACKAGE package.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2010-05-27 19:09+0300\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <LL@xxxxxx>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"X-Generator: Translate Toolkit 1.5.3\n"
-
-# type: Plain text
-#: tor-resolve.1.txt:6
-#, no-wrap
-msgid ""
-"// Copyright (c) The Tor Project, Inc.\n"
-"// See LICENSE for licensing information\n"
-"// This is an asciidoc file used to generate the manpage/html reference.\n"
-"// Learn asciidoc on http://www.methods.co.nz/asciidoc/userguide.html\n";
-"tor-resolve(1)\n"
-"==============\n"
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:8
-msgid "Peter Palfrader"
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:10
-#, no-wrap
-msgid ""
-"NAME\n"
-"----\n"
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:12
-msgid "tor-resolve - resolve a hostname to an IP address via tor"
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:14
-#, no-wrap
-msgid ""
-"SYNOPSIS\n"
-"--------\n"
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:16
-#, no-wrap
-msgid ""
-"**tor-resolve** [-4|-5] [-v] [-x] __hostname__ "
-"[__sockshost__[:__socksport__]]\n"
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:18
-#, no-wrap
-msgid ""
-"DESCRIPTION\n"
-"-----------\n"
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:21
-#, no-wrap
-msgid ""
-"**tor-resolve** is a simple script to connect to a SOCKS proxy that knows "
-"about\n"
-"the SOCKS RESOLVE command, hand it a hostname, and return an IP address.\n"
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:23
-#, no-wrap
-msgid ""
-"OPTIONS\n"
-"-------\n"
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:26
-#, no-wrap
-msgid ""
-"**-v**::\n"
-"    Display verbose output.\n"
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:29
-#, no-wrap
-msgid ""
-"**-x**::\n"
-"    Perform a reverse lookup: get the PTR record for an IPv4 address.\n"
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:32
-#, no-wrap
-msgid ""
-"**-5**::\n"
-"    Use the SOCKS5 protocol. (Default)\n"
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:36
-#, no-wrap
-msgid ""
-"**-4**::\n"
-"    Use the SOCKS4a protocol rather than the default SOCKS5 "
-"protocol. Doesn't\n"
-"    support reverse DNS.\n"
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:38
-#, no-wrap
-msgid ""
-"SEE ALSO\n"
-"--------\n"
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:40
-#, no-wrap
-msgid "**tor**(1), **torify**(1). +\n"
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:42
-msgid "See doc/socks-extensions.txt in the Tor package for protocol details."
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:44
-#, no-wrap
-msgid ""
-"AUTHORS\n"
-"-------\n"
-msgstr ""
-
-# type: Plain text
-#: tor-resolve.1.txt:45
-msgid "Roger Dingledine <arma@xxxxxxx>, Nick Mathewson <nickm@xxxxxxxxxxxx>."
-msgstr ""

Deleted: translation/trunk/projects/manpages/po/templates/tor.1.po
===================================================================
--- translation/trunk/projects/manpages/po/templates/tor.1.po	2010-12-05 19:16:01 UTC (rev 23895)
+++ translation/trunk/projects/manpages/po/templates/tor.1.po	2010-12-05 19:23:15 UTC (rev 23896)
@@ -1,3063 +0,0 @@
-# SOME DESCRIPTIVE TITLE
-# Copyright (C) YEAR The Tor Project, Inc.
-# This file is distributed under the same license as the PACKAGE package.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2010-05-27 18:49+0300\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <LL@xxxxxx>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"X-Generator: Translate Toolkit 1.5.3\n"
-
-# type: Plain text
-#: tor.1.txt:6
-#, no-wrap
-msgid ""
-"// Copyright (c) The Tor Project, Inc.\n"
-"// See LICENSE for licensing information\n"
-"// This is an asciidoc file used to generate the manpage/html reference.\n"
-"// Learn asciidoc on http://www.methods.co.nz/asciidoc/userguide.html\n";
-"TOR(1)\n"
-"======\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:9
-#, no-wrap
-msgid ""
-"NAME\n"
-"----\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:11
-msgid "tor - The second-generation onion router"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:14
-#, no-wrap
-msgid ""
-"SYNOPSIS\n"
-"--------\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:16
-#, no-wrap
-msgid "**tor** [__OPTION__ __value__]...\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:18
-#, no-wrap
-msgid ""
-"DESCRIPTION\n"
-"-----------\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:25
-msgid ""
-"__tor__ is a connection-oriented anonymizing communication service. Users "
-"choose a source-routed path through a set of nodes, and negotiate a "
-"\"virtual circuit\" through the network, in which each node knows its "
-"predecessor and successor, but no others. Traffic flowing down the circuit "
-"is unwrapped by a symmetric key at each node, which reveals the downstream "
-"node. +"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:30
-msgid ""
-"Basically __tor__ provides a distributed network of servers (\"onion "
-"routers\").  Users bounce their TCP streams -- web traffic, ftp, ssh, etc -- "
-"around the routers, and recipients, observers, and even the routers "
-"themselves have difficulty tracking the source of the stream."
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:32
-#, no-wrap
-msgid ""
-"OPTIONS\n"
-"-------\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:35
-#, no-wrap
-msgid ""
-"**-h**, **-help**::\n"
-"    Display a short help message and exit.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:38
-#, no-wrap
-msgid ""
-"**-f** __FILE__::\n"
-"    FILE contains further \"option value\" paris. (Default: "
-"@CONFDIR@/torrc)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:41
-#, no-wrap
-msgid ""
-"**--hash-password**::\n"
-"    Generates a hashed password for control port access.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:44
-#, no-wrap
-msgid ""
-"**--list-fingerprint**::\n"
-"    Generate your keys and output your nickname and fingerprint.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:47
-#, no-wrap
-msgid ""
-"**--verify-config**::\n"
-"    Verify the configuration file is valid.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:52
-#, no-wrap
-msgid ""
-"**--nt-service**::\n"
-"    **--service [install|remove|start|stop]** Manage the Tor Windows\n"
-"    NT/2000/XP service. Current instructions can be found at\n"
-"    https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#WinNTService\n";
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:55
-#, no-wrap
-msgid ""
-"**--list-torrc-options**::\n"
-"    List all valid options.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:58
-#, no-wrap
-msgid ""
-"**--version**::\n"
-"    Display Tor version and exit.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:63
-#, no-wrap
-msgid ""
-"**--quiet**::\n"
-"    Do not start Tor with a console log unless explicitly requested to do "
-"so.\n"
-"    (By default, Tor starts out logging messages at level \"notice\" or "
-"higher to\n"
-"    the console, until it has parsed its configuration.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:68
-#, no-wrap
-msgid ""
-"Other options can be specified either on the command-line (--option\n"
-"    value), or in the configuration file (option value or option "
-"\"value\").\n"
-"    Options are case-insensitive. C-style escaped characters are allowed "
-"inside\n"
-"    quoted values.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:73
-#, no-wrap
-msgid ""
-"**BandwidthRate** __N__ **bytes**|**KB**|**MB**|**GB**::\n"
-"    A token bucket limits the average incoming bandwidth usage on this node "
-"to\n"
-"    the specified number of bytes per second, and the average outgoing\n"
-"    bandwidth usage to that same value. (Default: 5 MB)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:77
-#, no-wrap
-msgid ""
-"**BandwidthBurst** __N__ **bytes**|**KB**|**MB**|**GB**::\n"
-"    Limit the maximum token bucket size (also known as the burst) to the "
-"given\n"
-"    number of bytes in each direction. (Default: 10 MB)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:84
-#, no-wrap
-msgid ""
-"**MaxAdvertisedBandwidth** __N__ **bytes**|**KB**|**MB**|**GB**::\n"
-"    If set, we will not advertise more than this amount of bandwidth for "
-"our\n"
-"    BandwidthRate. Server operators who want to reduce the number of "
-"clients\n"
-"    who ask to build circuits through them (since this is proportional to\n"
-"    advertised bandwidth rate) can thus reduce the CPU demands on their "
-"server\n"
-"    without impacting network performance.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:91
-#, no-wrap
-msgid ""
-"**RelayBandwidthRate** __N__ **bytes**|**KB**|**MB**|**GB**::\n"
-"    If defined, a separate token bucket limits the average incoming "
-"bandwidth\n"
-"    usage for \\_relayed traffic_ on this node to the specified number of "
-"bytes\n"
-"    per second, and the average outgoing bandwidth usage to that same "
-"value.\n"
-"    Relayed traffic currently is calculated to include answers to "
-"directory\n"
-"    requests, but that may change in future versions. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:96
-#, no-wrap
-msgid ""
-"**RelayBandwidthBurst** __N__ **bytes**|**KB**|**MB**|**GB**::\n"
-"    Limit the maximum token bucket size (also known as the burst) for\n"
-"    \\_relayed traffic_ to the given number of bytes in each direction.\n"
-"    (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:101
-#, no-wrap
-msgid ""
-"**PerConnBWRate** __N__ **bytes**|**KB**|**MB**|**GB**::\n"
-"    If set, do separate rate limiting for each connection from a "
-"non-relay.\n"
-"    You should never need to change this value, since a network-wide value "
-"is\n"
-"    published in the consensus and your relay will use that value. (Default: "
-"0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:106
-#, no-wrap
-msgid ""
-"**PerConnBWBurst** __N__ **bytes**|**KB**|**MB**|**GB**::\n"
-"    If set, do separate rate limiting for each connection from a "
-"non-relay.\n"
-"    You should never need to change this value, since a network-wide value "
-"is\n"
-"    published in the consensus and your relay will use that value. (Default: "
-"0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:115
-#, no-wrap
-msgid ""
-"**ConLimit** __NUM__::\n"
-"    The minimum number of file descriptors that must be available to the "
-"Tor\n"
-"    process before it will start. Tor will ask the OS for as many file\n"
-"    descriptors as the OS will allow (you can find this by \"ulimit -H "
-"-n\").\n"
-"    If this number is less than ConnLimit, then Tor will refuse to "
-"start. +\n"
-" +\n"
-"    You probably don't need to adjust this. It has no effect on Windows\n"
-"    since that platform lacks getrlimit(). (Default: 1000)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:136
-#, no-wrap
-msgid ""
-"**ConstrainedSockets** **0**|**1**::\n"
-"    If set, Tor will tell the kernel to attempt to shrink the buffers for "
-"all\n"
-"    sockets to the size specified in **ConstrainedSockSize**. This is useful "
-"for\n"
-"    virtual servers and other environments where system level TCP buffers "
-"may\n"
-"    be limited. If you're on a virtual server, and you encounter the "
-"\"Error\n"
-"    creating network socket: No buffer space available\" message, you are\n"
-"    likely experiencing this problem. +\n"
-" +\n"
-"    The preferred solution is to have the admin increase the buffer pool "
-"for\n"
-"    the host itself via /proc/sys/net/ipv4/tcp_mem or equivalent facility;\n"
-"    this configuration option is a second-resort. +\n"
-" +\n"
-"    The DirPort option should also not be used if TCP buffers are "
-"scarce. The\n"
-"    cached directory requests consume additional sockets which exacerbates\n"
-"    the problem. +\n"
-" +\n"
-"    You should **not** enable this feature unless you encounter the \"no "
-"buffer\n"
-"    space available\" issue. Reducing the TCP buffers affects window size "
-"for\n"
-"    the TCP stream and will reduce throughput in proportion to round trip\n"
-"    time on long paths. (Default: 0.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:141
-#, no-wrap
-msgid ""
-"**ConstrainedSockSize** __N__ **bytes**|**KB**::\n"
-"    When **ConstrainedSockets** is enabled the receive and transmit buffers "
-"for\n"
-"    all sockets will be set to this limit. Must be a value between 2048 "
-"and\n"
-"    262144, in 1024 byte increments. Default of 8192 is recommended.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:149
-#, no-wrap
-msgid ""
-"**ControlPort** __Port__::\n"
-"    If set, Tor will accept connections on this port and allow those\n"
-"    connections to control the Tor process using the Tor Control Protocol\n"
-"    (described in control-spec.txt). Note: unless you also specify one of\n"
-"    **HashedControlPassword** or **CookieAuthentication**, setting this "
-"option will\n"
-"    cause Tor to allow any process on the local host to control it. This\n"
-"    option is required for many Tor controllers; most use the value of "
-"9051.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:157
-#, no-wrap
-msgid ""
-"**ControlListenAddress** __IP__[:__PORT__]::\n"
-"    Bind the controller listener to this address. If you specify a port, "
-"bind\n"
-"    to this port rather than the one specified in ControlPort. We strongly\n"
-"    recommend that you leave this alone unless you know what you're doing,\n"
-"    since giving attackers access to your control listener is really\n"
-"    dangerous. (Default: 127.0.0.1) This directive can be specified "
-"multiple\n"
-"    times to bind to multiple addresses/ports.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:161
-#, no-wrap
-msgid ""
-"**ControlSocket** __Path__::\n"
-"    Like ControlPort, but listens on a Unix domain socket, rather than a "
-"TCP\n"
-"    socket. (Unix and Unix-like systems only.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:168
-#, no-wrap
-msgid ""
-"**HashedControlPassword** __hashed_password__::\n"
-"    Don't allow any connections on the control port except when the other\n"
-"    process knows the password whose one-way hash is "
-"__hashed_password__. You\n"
-"    can compute the hash of a password by running \"tor --hash-password\n"
-"    __password__\". You can provide several acceptable passwords by using "
-"more\n"
-"    than one HashedControlPassword line.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:175
-#, no-wrap
-msgid ""
-"**CookieAuthentication** **0**|**1**::\n"
-"    If this option is set to 1, don't allow any connections on the control "
-"port\n"
-"    except when the connecting process knows the contents of a file named\n"
-"    \"control_auth_cookie\", which Tor will create in its data "
-"directory. This\n"
-"    authentication method should only be used on systems with good "
-"filesystem\n"
-"    security. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:179
-#, no-wrap
-msgid ""
-"**CookieAuthFile** __Path__::\n"
-"    If set, this option overrides the default location and file name\n"
-"    for Tor's cookie file. (See CookieAuthentication above.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:185
-#, no-wrap
-msgid ""
-"**CookieAuthFileGroupReadable** **0**|**1**|__Groupname__::\n"
-"    If this option is set to 0, don't allow the filesystem group to read "
-"the\n"
-"    cookie file. If the option is set to 1, make the cookie file readable "
-"by\n"
-"    the default GID. [Making the file readable by other groups is not yet\n"
-"    implemented; let us know if you need this for some reason.] (Default: "
-"0).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:188
-#, no-wrap
-msgid ""
-"**DataDirectory** __DIR__::\n"
-"    Store working data in DIR (Default: @LOCALSTATEDIR@/lib/tor)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:211
-#, no-wrap
-msgid ""
-"**DirServer** [__nickname__] [**flags**] __address__:__port__ "
-"__fingerprint__::\n"
-"    Use a nonstandard authoritative directory server at the provided "
-"address\n"
-"    and port, with the specified key fingerprint. This option can be "
-"repeated\n"
-"    many times, for multiple authoritative directory servers. Flags are\n"
-"    separated by spaces, and determine what kind of an authority this "
-"directory\n"
-"    is. By default, every authority is authoritative for current "
-"(\"v2\")-style\n"
-"    directories, unless the \"no-v2\" flag is given. If the \"v1\" flags "
-"is\n"
-"    provided, Tor will use this server as an authority for old-style (v1)\n"
-"    directories as well. (Only directory mirrors care about this.) Tor "
-"will\n"
-"    use this server as an authority for hidden service information if the "
-"\"hs\"\n"
-"    flag is set, or if the \"v1\" flag is set and the \"no-hs\" flag is "
-"**not** set.\n"
-"    Tor will use this authority as a bridge authoritative directory if the\n"
-"    \"bridge\" flag is set. If a flag \"orport=**port**\" is given, Tor will "
-"use the\n"
-"    given port when opening encrypted tunnels to the dirserver. Lastly, if "
-"a\n"
-"    flag \"v3ident=**fp**\" is given, the dirserver is a v3 directory "
-"authority\n"
-"    whose v3 long-term signing key has the fingerprint **fp**. +\n"
-" +\n"
-"    If no **dirserver** line is given, Tor will use the default directory\n"
-"    servers. NOTE: this option is intended for setting up a private Tor\n"
-"    network with its own directory authorities. If you use it, you will be\n"
-"    distinguishable from other users, because you won't believe the same\n"
-"    authorities they do.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:213
-#, no-wrap
-msgid ""
-"**AlternateDirAuthority** [__nickname__] [**flags**] __address__:__port__ "
-"__fingerprint__ +\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:215
-#, no-wrap
-msgid ""
-"**AlternateHSAuthority** [__nickname__] [**flags**] __address__:__port__ "
-"__fingerprint__ +\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:222
-#, no-wrap
-msgid ""
-"**AlternateBridgeAuthority** [__nickname__] [**flags**] __address__:__port__ "
-"__ fingerprint__::\n"
-"    As DirServer, but replaces less of the default directory "
-"authorities. Using\n"
-"    AlternateDirAuthority replaces the default Tor directory authorities, "
-"but\n"
-"    leaves the hidden service authorities and bridge authorities in place.\n"
-"    Similarly, Using AlternateHSAuthority replaces the default hidden "
-"service\n"
-"    authorities, but not the directory or bridge authorities.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:230
-#, no-wrap
-msgid ""
-"**DisableAllSwap** **0**|**1**::\n"
-"    If set to 1, Tor will attempt to lock all current and future memory "
-"pages,\n"
-"    so that memory cannot be paged out. Windows, OS X and Solaris are "
-"currently\n"
-"    not supported. We believe that this feature works on modern Gnu/Linux\n"
-"    distributions, and that it should work on *BSD systems "
-"(untested). This\n"
-"    option requires that you start your Tor as root, and you should use "
-"the\n"
-"    **User** option to properly reduce Tor's privileges. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:235
-#, no-wrap
-msgid ""
-"**FetchDirInfoEarly** **0**|**1**::\n"
-"    If set to 1, Tor will always fetch directory information like other\n"
-"    directory caches, even if you don't meet the normal criteria for "
-"fetching\n"
-"    early. Normal users should leave it off. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:241
-#, no-wrap
-msgid ""
-"**FetchDirInfoExtraEarly** **0**|**1**::\n"
-"    If set to 1, Tor will fetch directory information before other "
-"directory\n"
-"    caches. It will attempt to download directory information closer to "
-"the\n"
-"    start of the consensus period. Normal users should leave it off.\n"
-"    (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:246
-#, no-wrap
-msgid ""
-"**FetchHidServDescriptors** **0**|**1**::\n"
-"    If set to 0, Tor will never fetch any hidden service descriptors from "
-"the\n"
-"    rendezvous directories. This option is only useful if you're using a "
-"Tor\n"
-"    controller that handles hidden service fetches for you. (Default: 1)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:252
-#, no-wrap
-msgid ""
-"**FetchServerDescriptors** **0**|**1**::\n"
-"    If set to 0, Tor will never fetch any network status summaries or "
-"server\n"
-"    descriptors from the directory servers. This option is only useful if\n"
-"    you're using a Tor controller that handles directory fetches for you.\n"
-"    (Default: 1)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:259
-#, no-wrap
-msgid ""
-"**FetchUselessDescriptors** **0**|**1**::\n"
-"    If set to 1, Tor will fetch every non-obsolete descriptor from the\n"
-"    authorities that it hears about. Otherwise, it will avoid fetching "
-"useless\n"
-"    descriptors, for example for routers that are not running. This option "
-"is\n"
-"    useful if you're using the contributed \"exitlist\" script to enumerate "
-"Tor\n"
-"    nodes that exit to certain addresses. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:264
-#, no-wrap
-msgid ""
-"**HTTPProxy** __host__[:__port__]::\n"
-"    Tor will make all its directory requests through this host:port (or "
-"host:80\n"
-"    if port is not specified), rather than connecting directly to any "
-"directory\n"
-"    servers.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:270
-#, no-wrap
-msgid ""
-"**HTTPProxyAuthenticator** __username:password__::\n"
-"    If defined, Tor will use this username:password for Basic HTTP proxy\n"
-"    authentication, as in RFC 2617. This is currently the only form of "
-"HTTP\n"
-"    proxy authentication that Tor supports; feel free to submit a patch if "
-"you\n"
-"    want it to support others.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:277
-#, no-wrap
-msgid ""
-"**HTTPSProxy** __host__[:__port__]::\n"
-"    Tor will make all its OR (SSL) connections through this host:port (or\n"
-"    host:443 if port is not specified), via HTTP CONNECT rather than "
-"connecting\n"
-"    directly to servers. You may want to set **FascistFirewall** to "
-"restrict\n"
-"    the set of ports you might try to connect to, if your HTTPS proxy only\n"
-"    allows connecting to certain ports.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:283
-#, no-wrap
-msgid ""
-"**HTTPSProxyAuthenticator** __username:password__::\n"
-"    If defined, Tor will use this username:password for Basic HTTPS proxy\n"
-"    authentication, as in RFC 2617. This is currently the only form of "
-"HTTPS\n"
-"    proxy authentication that Tor supports; feel free to submit a patch if "
-"you\n"
-"    want it to support others.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:287
-#, no-wrap
-msgid ""
-"**Socks4Proxy** __host__[:__port__]::\n"
-"    Tor will make all OR connections through the SOCKS 4 proxy at "
-"host:port\n"
-"    (or host:1080 if port is not specified).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:291
-#, no-wrap
-msgid ""
-"**Socks5Proxy** __host__[:__port__]::\n"
-"    Tor will make all OR connections through the SOCKS 5 proxy at "
-"host:port\n"
-"    (or host:1080 if port is not specified).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:293
-#, no-wrap
-msgid "**Socks5ProxyUsername** __username__ +\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:298
-#, no-wrap
-msgid ""
-"**Socks5ProxyPassword** __password__::\n"
-"    If defined, authenticate to the SOCKS 5 server using username and "
-"password\n"
-"    in accordance to RFC 1929. Both username and password must be between 1 "
-"and\n"
-"    255 characters.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:304
-#, no-wrap
-msgid ""
-"**KeepalivePeriod** __NUM__::\n"
-"    To keep firewalls from expiring connections, send a padding keepalive "
-"cell\n"
-"    every NUM seconds on open connections that are in use. If the "
-"connection\n"
-"    has no open circuits, it will instead be closed after NUM seconds of\n"
-"    idleness. (Default: 5 minutes)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:313
-#, no-wrap
-msgid ""
-"**Log** __minSeverity__[-__maxSeverity__] "
-"**stderr**|**stdout**|**syslog**::\n"
-"    Send all messages between __minSeverity__ and __maxSeverity__ to the "
-"standard\n"
-"    output stream, the standard error stream, or to the system log. (The\n"
-"    \"syslog\" value is only supported on Unix.) Recognized severity levels "
-"are\n"
-"    debug, info, notice, warn, and err. We advise using \"notice\" in most "
-"cases,\n"
-"    since anything more verbose may provide sensitive information to an\n"
-"    attacker who obtains the logs. If only one severity level is given, "
-"all\n"
-"    messages of that level or higher will be sent to the listed "
-"destination.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:319
-#, no-wrap
-msgid ""
-"**Log** __minSeverity__[-__maxSeverity__] **file** __FILENAME__::\n"
-"    As above, but send log messages to the listed filename. The\n"
-"    \"Log\" option may appear more than once in a configuration file.\n"
-"    Messages are sent to all the logs that match their severity\n"
-"    level.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:325
-#, no-wrap
-msgid ""
-"**OutboundBindAddress** __IP__::\n"
-"    Make all outbound connections originate from the IP address "
-"specified. This\n"
-"    is only useful when you have multiple network interfaces, and you want "
-"all\n"
-"    of Tor's outgoing connections to use a single one.  This setting will "
-"be\n"
-"    ignored for connections to the loopback addresses (127.0.0.0/8 and "
-"::1).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:329
-#, no-wrap
-msgid ""
-"**PidFile** __FILE__::\n"
-"    On startup, write our PID to FILE. On clean shutdown, remove\n"
-"    FILE.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:334
-#, no-wrap
-msgid ""
-"**ProtocolWarnings** **0**|**1**::\n"
-"    If 1, Tor will log with severity \\'warn' various cases of other parties "
-"not\n"
-"    following the Tor specification. Otherwise, they are logged with "
-"severity\n"
-"    \\'info'. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:339
-#, no-wrap
-msgid ""
-"**RunAsDaemon** **0**|**1**::\n"
-"    If 1, Tor forks and daemonizes to the background. This option has no "
-"effect\n"
-"    on Windows; instead you should use the --service command-line option.\n"
-"    (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:351
-#, no-wrap
-msgid ""
-"**SafeLogging** **0**|**1**|**relay**::\n"
-"    Tor can scrub potentially sensitive strings from log messages (e.g.\n"
-"    addresses) by replacing them with the string [scrubbed]. This way logs "
-"can\n"
-"    still be useful, but they don't leave behind personally identifying\n"
-"    information about what sites a user might have visited. +\n"
-" +\n"
-"    If this option is set to 0, Tor will not perform any scrubbing, if it "
-"is\n"
-"    set to 1, all potentially sensitive strings are replaced. If it is set "
-"to\n"
-"    relay, all log messages generated when acting as a relay are sanitized, "
-"but\n"
-"    all messages generated when acting as a client are not. (Default: 1)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:354
-#, no-wrap
-msgid ""
-"**User** __UID__::\n"
-"    On startup, setuid to this user and setgid to their primary group.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:358
-#, no-wrap
-msgid ""
-"**HardwareAccel** **0**|**1**::\n"
-"    If non-zero, try to use built-in (static) crypto hardware acceleration "
-"when\n"
-"    available. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:363
-#, no-wrap
-msgid ""
-"**AccelName** __NAME__::\n"
-"    When using OpenSSL hardware crypto acceleration attempt to load the "
-"dynamic\n"
-"    engine of this name. This must be used for any dynamic hardware "
-"engine.\n"
-"    Names can be verified with the openssl engine command.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:367
-#, no-wrap
-msgid ""
-"**AccelDir** __DIR__::\n"
-"    Specify this option if using dynamic hardware acceleration and the "
-"engine\n"
-"    implementation library resides somewhere other than the OpenSSL "
-"default.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:372
-#, no-wrap
-msgid ""
-"**AvoidDiskWrites** **0**|**1**::\n"
-"    If non-zero, try to write to disk less frequently than we would "
-"otherwise.\n"
-"    This is useful when running on flash memory or other media that "
-"support\n"
-"    only a limited number of writes. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:377
-#, no-wrap
-msgid ""
-"**TunnelDirConns** **0**|**1**::\n"
-"    If non-zero, when a directory server we contact supports it, we will "
-"build\n"
-"    a one-hop circuit and make an encrypted connection via its ORPort.\n"
-"    (Default: 1)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:381
-#, no-wrap
-msgid ""
-"**PreferTunneledDirConns** **0**|**1**::\n"
-"    If non-zero, we will avoid directory servers that don't support "
-"tunneled\n"
-"    directory connections, when possible. (Default: 1)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:393
-#, no-wrap
-msgid ""
-"**CircuitPriorityHalflife** __NUM1__::\n"
-"    If this value is set, we override the default algorithm for choosing "
-"which\n"
-"    circuit's cell to deliver or relay next. When the value is 0, we\n"
-"    round-robin between the active circuits on a connection, delivering "
-"one\n"
-"    cell from each in turn. When the value is positive, we prefer "
-"delivering\n"
-"    cells from whichever connection has the lowest weighted cell count, "
-"where\n"
-"    cells are weighted exponentially according to the supplied\n"
-"    CircuitPriorityHalflife value (in seconds). If this option is not set "
-"at\n"
-"    all, we use the behavior recommended in the current consensus\n"
-"    networkstatus. This is an advanced option; you generally shouldn't "
-"have\n"
-"    to mess with it. (Default: not set.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:395
-#, no-wrap
-msgid ""
-"CLIENT OPTIONS\n"
-"--------------\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:399
-msgid ""
-"The following options are useful only for clients (that is, if **SocksPort** "
-"is non-zero):"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:406
-#, no-wrap
-msgid ""
-"**AllowInvalidNodes** "
-"**entry**|**exit**|**middle**|**introduction**|**rendezvous**|**...**::\n"
-"    If some Tor servers are obviously not working right, the directory\n"
-"    authorities can manually mark them as invalid, meaning that it's not\n"
-"    recommended you use them for entry or exit positions in your "
-"circuits. You\n"
-"    can opt to use them in some circuit positions, though. The default is\n"
-"    \"middle,rendezvous\", and other choices are not advised.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:413
-#, no-wrap
-msgid ""
-"**ExcludeSingleHopRelays** **0**|**1**::\n"
-"    This option controls whether circuits built by Tor will include relays "
-"with\n"
-"    the AllowSingleHopExits flag set to true. If ExcludeSingleHopRelays is "
-"set\n"
-"    to 0, these relays will be included. Note that these relays might be "
-"at\n"
-"    higher risk of being seized or observed, so they are not normally "
-"included.\n"
-"    (Default: 1)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:421
-#, no-wrap
-msgid ""
-"**Bridge** __IP__:__ORPort__ [fingerprint]::\n"
-"    When set along with UseBridges, instructs Tor to use the relay at\n"
-"    \"IP:ORPort\" as a \"bridge\" relaying into the Tor network. If "
-"\"fingerprint\"\n"
-"    is provided (using the same format as for DirServer), we will verify "
-"that\n"
-"    the relay running at that location has the right fingerprint. We also "
-"use\n"
-"    fingerprint to look up the bridge descriptor at the bridge authority, "
-"if\n"
-"    it's provided and if UpdateBridgesFromAuthority is set too.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:425
-#, no-wrap
-msgid ""
-"**CircuitBuildTimeout** __NUM__::\n"
-"    Try for at most NUM seconds when building circuits. If the circuit "
-"isn't\n"
-"    open in that time, give up on it. (Default: 1 minute.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:433
-#, no-wrap
-msgid ""
-"**CircuitIdleTimeout** __NUM__::\n"
-"    If we have kept a clean (never used) circuit around for NUM seconds, "
-"then\n"
-"    close it. This way when the Tor client is entirely idle, it can expire "
-"all\n"
-"    of its circuits, and then expire its TLS connections. Also, if we end "
-"up\n"
-"    making a circuit that is not useful for exiting any of the requests "
-"we're\n"
-"    receiving, it won't forever take up a slot in the circuit "
-"list. (Default: 1\n"
-"    hour.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:439
-#, no-wrap
-msgid ""
-"**CircuitStreamTimeout** __NUM__::\n"
-"    If non-zero, this option overrides our internal timeout schedule for "
-"how\n"
-"    many seconds until we detach a stream from a circuit and try a new "
-"circuit.\n"
-"    If your network is particularly slow, you might want to set this to a\n"
-"    number like 60. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:446
-#, no-wrap
-msgid ""
-"**ClientOnly** **0**|**1**::\n"
-"    If set to 1, Tor will under no circumstances run as a server or serve\n"
-"    directory requests. The default is to run as a client unless ORPort is\n"
-"    configured. (Usually, you don't need to set this; Tor is pretty smart "
-"at\n"
-"    figuring out whether you are reliable and high-bandwidth enough to be "
-"a\n"
-"    useful server.) (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:451
-#, no-wrap
-msgid ""
-"**ExcludeNodes** __node__,__node__,__...__::\n"
-"    A list of identity fingerprints, nicknames, country codes and address\n"
-"    patterns of nodes to never use when building a circuit. (Example:\n"
-"    ExcludeNodes SlowServer, $    EFFFFFFFFFFFFFFF, \\{cc}, 255.254.0.0/8)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:457
-#, no-wrap
-msgid ""
-"**ExcludeExitNodes** __node__,__node__,__...__::\n"
-"    A list of identity fingerprints, nicknames, country codes and address\n"
-"    patterns of nodes to never use when picking an exit node. Note that "
-"any\n"
-"    node listed in ExcludeNodes is automatically considered to be part of "
-"this\n"
-"    list.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:462
-#, no-wrap
-msgid ""
-"**EntryNodes** __node__,__node__,__...__::\n"
-"    A list of identity fingerprints, nicknames, country codes and address\n"
-"    patterns of nodes to use for the first hop in normal circuits. These "
-"are\n"
-"    treated only as preferences unless StrictNodes (see below) is also "
-"set.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:467
-#, no-wrap
-msgid ""
-"**ExitNodes** __node__,__node__,__...__::\n"
-"    A list of identity fingerprints, nicknames, country codes and address\n"
-"    patterns of nodes to use for the last hop in normal exit "
-"circuits. These\n"
-"    are treated only as preferences unless StrictNodes (see below) is also "
-"set.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:475
-#, no-wrap
-msgid ""
-"**StrictNodes** **0**|**1**::\n"
-"    If 1 and EntryNodes config option is set, Tor will never use any nodes\n"
-"    besides those listed in EntryNodes for the first hop of a normal "
-"circuit.\n"
-"    If 1 and ExitNodes config option is set, Tor will never use any nodes\n"
-"    besides those listed in ExitNodes for the last hop of a normal exit\n"
-"    circuit. Note that Tor might still use these nodes for non-exit "
-"circuits\n"
-"    such as one-hop directory fetches or hidden service support circuits.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:483
-#, no-wrap
-msgid ""
-"**FascistFirewall** **0**|**1**::\n"
-"    If 1, Tor will only create outgoing connections to ORs running on "
-"ports\n"
-"    that your firewall allows (defaults to 80 and 443; see "
-"**FirewallPorts**).\n"
-"    This will allow you to run Tor as a client behind a firewall with\n"
-"    restrictive policies, but will not allow you to run as a server behind "
-"such\n"
-"    a firewall. If you prefer more fine-grained control, use\n"
-"    ReachableAddresses instead.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:488
-#, no-wrap
-msgid ""
-"**FirewallPorts** __PORTS__::\n"
-"    A list of ports that your firewall allows you to connect to. Only used "
-"when\n"
-"    **FascistFirewall** is set. This option is deprecated; use "
-"ReachableAddresses\n"
-"    instead. (Default: 80, 443)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:498
-#, no-wrap
-msgid ""
-"**HidServAuth** __onion-address__ __auth-cookie__ [__service-name__]::\n"
-"    Client authorization for a hidden service. Valid onion addresses contain "
-"16\n"
-"    characters in a-z2-7 plus \".onion\", and valid auth cookies contain "
-"22\n"
-"    characters in A-Za-z0-9+/. The service name is only used for internal\n"
-"    purposes, e.g., for Tor controllers. This option may be used multiple "
-"times\n"
-"    for different hidden services. If a hidden service uses authorization "
-"and\n"
-"    this option is not set, the hidden service is not accessible. Hidden\n"
-"    services can be configured to require authorization using the \n"
-"    **HiddenServiceAuthorizeClient** option.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:507
-#, no-wrap
-msgid ""
-"**ReachableAddresses** __ADDR__[/__MASK__][:__PORT__]...::\n"
-"    A comma-separated list of IP addresses and ports that your firewall "
-"allows\n"
-"    you to connect to. The format is as for the addresses in ExitPolicy, "
-"except\n"
-"    that \"accept\" is understood unless \"reject\" is explicitly "
-"provided. For\n"
-"    example, \\'ReachableAddresses 99.0.0.0/8, reject 18.0.0.0/8:80, "
-"accept\n"
-"    \\*:80' means that your firewall allows connections to everything inside "
-"net\n"
-"    99, rejects port 80 connections to net 18, and accepts connections to "
-"port\n"
-"    80 otherwise. (Default: \\'accept \\*:*'.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:514
-#, no-wrap
-msgid ""
-"**ReachableDirAddresses** __ADDR__[/__MASK__][:__PORT__]...::\n"
-"    Like **ReachableAddresses**, a list of addresses and ports. Tor will "
-"obey\n"
-"    these restrictions when fetching directory information, using standard "
-"HTTP\n"
-"    GET requests. If not set explicitly then the value of\n"
-"    **ReachableAddresses** is used. If **HTTPProxy** is set then these\n"
-"    connections will go through that proxy.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:527
-#, no-wrap
-msgid ""
-"**ReachableORAddresses** __ADDR__[/__MASK__][:__PORT__]...::\n"
-"    Like **ReachableAddresses**, a list of addresses and ports. Tor will "
-"obey\n"
-"    these restrictions when connecting to Onion Routers, using TLS/SSL. If "
-"not\n"
-"    set explicitly then the value of **ReachableAddresses** is used. If\n"
-"    **HTTPSProxy** is set then these connections will go through that "
-"proxy. +\n"
-" +\n"
-"    The separation between **ReachableORAddresses** and\n"
-"    **ReachableDirAddresses** is only interesting when you are connecting\n"
-"    through proxies (see **HTTPProxy** and **HTTPSProxy**). Most proxies "
-"limit\n"
-"    TLS connections (which Tor uses to connect to Onion Routers) to port "
-"443,\n"
-"    and some limit HTTP GET requests (which Tor uses for fetching "
-"directory\n"
-"    information) to port 80.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:534
-#, no-wrap
-msgid ""
-"**LongLivedPorts** __PORTS__::\n"
-"    A list of ports for services that tend to have long-running "
-"connections\n"
-"    (e.g. chat and interactive shells). Circuits for streams that use "
-"these\n"
-"    ports will contain only high-uptime nodes, to reduce the chance that a "
-"node\n"
-"    will go down before the stream is finished. (Default: 21, 22, 706, "
-"1863,\n"
-"    5050, 5190, 5222, 5223, 6667, 6697, 8300)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:541
-#, no-wrap
-msgid ""
-"**MapAddress** __address__ __newaddress__::\n"
-"    When a request for address arrives to Tor, it will rewrite it to "
-"newaddress\n"
-"    before processing it. For example, if you always want connections to\n"
-"    www.indymedia.org to exit via __torserver__ (where __torserver__ is "
-"the\n"
-"    nickname of the server), use \"MapAddress www.indymedia.org\n"
-"    www.indymedia.org.torserver.exit\".\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:545
-#, no-wrap
-msgid ""
-"**NewCircuitPeriod** __NUM__::\n"
-"    Every NUM seconds consider whether to build a new circuit. (Default: "
-"30\n"
-"    seconds)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:550
-#, no-wrap
-msgid ""
-"**MaxCircuitDirtiness** __NUM__::\n"
-"    Feel free to reuse a circuit that was first used at most NUM seconds "
-"ago,\n"
-"    but never attach a new stream to a circuit that is too old. (Default: "
-"10\n"
-"    minutes)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:557
-#, no-wrap
-msgid ""
-"**NodeFamily** __node__,__node__,__...__::\n"
-"    The Tor servers, defined by their identity fingerprints or nicknames,\n"
-"    constitute a \"family\" of similar or co-administered servers, so never "
-"use\n"
-"    any two of them in the same circuit. Defining a NodeFamily is only "
-"needed\n"
-"    when a server doesn't list the family itself (with MyFamily). This "
-"option\n"
-"    can be used multiple times.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:562
-#, no-wrap
-msgid ""
-"**EnforceDistinctSubnets** **0**|**1**::\n"
-"    If 1, Tor will not put two servers whose IP addresses are \"too close\" "
-"on\n"
-"    the same circuit. Currently, two addresses are \"too close\" if they lie "
-"in\n"
-"    the same /16 range. (Default: 1)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:567
-#, no-wrap
-msgid ""
-"**SocksPort** __PORT__::\n"
-"    Advertise this port to listen for connections from Socks-speaking\n"
-"    applications. Set this to 0 if you don't want to allow application\n"
-"    connections. (Default: 9050)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:573
-#, no-wrap
-msgid ""
-"**SocksListenAddress** __IP__[:__PORT__]::\n"
-"    Bind to this address to listen for connections from Socks-speaking\n"
-"    applications. (Default: 127.0.0.1) You can also specify a port (e.g.\n"
-"    192.168.0.1:9100). This directive can be specified multiple times to "
-"bind\n"
-"    to multiple addresses/ports.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:578
-#, no-wrap
-msgid ""
-"**SocksPolicy** __policy__,__policy__,__...__::\n"
-"    Set an entrance policy for this server, to limit who can connect to "
-"the\n"
-"    SocksPort and DNSPort ports. The policies have the same form as exit\n"
-"    policies below.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:583
-#, no-wrap
-msgid ""
-"**SocksTimeout** __NUM__::\n"
-"    Let a socks connection wait NUM seconds handshaking, and NUM seconds\n"
-"    unattached waiting for an appropriate circuit, before we fail "
-"it. (Default:\n"
-"    2 minutes.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:595
-#, no-wrap
-msgid ""
-"**TrackHostExits** __host__,__.domain__,__...__::\n"
-"    For each value in the comma separated list, Tor will track recent\n"
-"    connections to hosts that match this value and attempt to reuse the "
-"same\n"
-"    exit node for each. If the value is prepended with a \\'.\\', it is "
-"treated as\n"
-"    matching an entire domain. If one of the values is just a \\'.', it "
-"means\n"
-"    match everything. This option is useful if you frequently connect to "
-"sites\n"
-"    that will expire all your authentication cookies (i.e. log you out) if\n"
-"    your IP address changes. Note that this option does have the "
-"disadvantage\n"
-"    of making it more clear that a given history is associated with a "
-"single\n"
-"    user. However, most people who would wish to observe this will observe "
-"it\n"
-"    through cookies or other protocol-specific means anyhow.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:600
-#, no-wrap
-msgid ""
-"**TrackHostExitsExpire** __NUM__::\n"
-"    Since exit servers go up and down, it is desirable to expire the\n"
-"    association between host and exit server after NUM seconds. The default "
-"is\n"
-"    1800 seconds (30 minutes).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:605
-#, no-wrap
-msgid ""
-"**UpdateBridgesFromAuthority** **0**|**1**::\n"
-"    When set (along with UseBridges), Tor will try to fetch bridge "
-"descriptors\n"
-"    from the configured bridge authorities when feasible. It will fall back "
-"to\n"
-"    a direct request if the authority responds with a 404. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:610
-#, no-wrap
-msgid ""
-"**UseBridges** **0**|**1**::\n"
-"    When set, Tor will fetch descriptors for each bridge listed in the "
-"\"Bridge\"\n"
-"    config lines, and use these relays as both entry guards and directory\n"
-"    guards. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:616
-#, no-wrap
-msgid ""
-"**UseEntryGuards** **0**|**1**::\n"
-"    If this option is set to 1, we pick a few long-term entry servers, and "
-"try\n"
-"    to stick with them. This is desirable because constantly changing "
-"servers\n"
-"    increases the odds that an adversary who owns some servers will observe "
-"a\n"
-"    fraction of your paths. (Defaults to 1.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:620
-#, no-wrap
-msgid ""
-"**NumEntryGuards** __NUM__::\n"
-"    If UseEntryGuards is set to 1, we will try to pick a total of NUM "
-"routers\n"
-"    as long-term entries for our circuits. (Defaults to 3.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:627
-#, no-wrap
-msgid ""
-"**SafeSocks** **0**|**1**::\n"
-"    When this option is enabled, Tor will reject application connections "
-"that\n"
-"    use unsafe variants of the socks protocol -- ones that only provide an "
-"IP\n"
-"    address, meaning the application is doing a DNS resolve first.\n"
-"    Specifically, these are socks4 and socks5 when not doing remote DNS.\n"
-"    (Defaults to 0.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:634
-#, no-wrap
-msgid ""
-"**TestSocks** **0**|**1**::\n"
-"    When this option is enabled, Tor will make a notice-level log entry "
-"for\n"
-"    each connection to the Socks port indicating whether the request used "
-"a\n"
-"    safe socks protocol or an unsafe one (see above entry on "
-"SafeSocks). This\n"
-"    helps to determine whether an application using Tor is possibly "
-"leaking\n"
-"    DNS requests. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:645
-#, no-wrap
-msgid ""
-"**VirtualAddrNetwork** __Address__/__bits__::\n"
-"    When a controller asks for a virtual (unused) address with the "
-"MAPADDRESS\n"
-"    command, Tor picks an unassigned address from this range. (Default:\n"
-"    127.192.0.0/10) +\n"
-" +\n"
-"    When providing proxy server service to a network of computers using a "
-"tool\n"
-"    like dns-proxy-tor, change this address to \"10.192.0.0/10\" or\n"
-"    \"172.16.0.0/12\". The default **VirtualAddrNetwork** address range on "
-"a\n"
-"    properly configured machine will route to the loopback interface. For\n"
-"    local use, no change to the default VirtualAddrNetwork setting is "
-"needed.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:651
-#, no-wrap
-msgid ""
-"**AllowNonRFC953Hostnames** **0**|**1**::\n"
-"    When this option is disabled, Tor blocks hostnames containing illegal\n"
-"    characters (like @ and :) rather than sending them to an exit node to "
-"be\n"
-"    resolved. This helps trap accidental attempts to resolve URLs and so "
-"on.\n"
-"    (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:657
-#, no-wrap
-msgid ""
-"**AllowDotExit** **0**|**1**::\n"
-"    If enabled, we convert \"www.google.com.foo.exit\" addresses on the\n"
-"    SocksPort/TransPort/NatdPort into \"www.google.com\" addresses that exit "
-"from\n"
-"    the node \"foo\". Disabled by default since attacking websites and "
-"exit\n"
-"    relays can use it to manipulate your path selection. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:667
-#, no-wrap
-msgid ""
-"**FastFirstHopPK** **0**|**1**::\n"
-"    When this option is disabled, Tor uses the public key step for the "
-"first\n"
-"    hop of creating circuits. Skipping it is generally safe since we have\n"
-"    already used TLS to authenticate the relay and to establish "
-"forward-secure\n"
-"    keys. Turning this option off makes circuit building slower. +\n"
-" +\n"
-"    Note that Tor will always use the public key step for the first hop if "
-"it's\n"
-"    operating as a relay, and it will never use the public key step if it\n"
-"    doesn't yet know the onion key of the first hop. (Default: 1)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:675
-#, no-wrap
-msgid ""
-"**TransPort** __PORT__::\n"
-"    If non-zero, enables transparent proxy support on __PORT__ (by "
-"convention,\n"
-"    9040). Requires OS support for transparent proxies, such as BSDs' pf "
-"or\n"
-"    Linux's IPTables. If you're planning to use Tor as a transparent proxy "
-"for\n"
-"    a network, you'll want to examine and change VirtualAddrNetwork from "
-"the\n"
-"    default setting. You'll also want to set the TransListenAddress option "
-"for\n"
-"    the network you'd like to proxy. (Default: 0).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:680
-#, no-wrap
-msgid ""
-"**TransListenAddress** __IP__[:__PORT__]::\n"
-"    Bind to this address to listen for transparent proxy "
-"connections. (Default:\n"
-"    127.0.0.1). This is useful for exporting a transparent proxy server to "
-"an\n"
-"    entire network.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:685
-#, no-wrap
-msgid ""
-"**NATDPort** __PORT__::\n"
-"    Allow old versions of ipfw (as included in old versions of FreeBSD, "
-"etc.)\n"
-"    to send connections through Tor using the NATD protocol. This option "
-"is\n"
-"    only for people who cannot use TransPort.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:688
-#, no-wrap
-msgid ""
-"**NATDListenAddress** __IP__[:__PORT__]::\n"
-"    Bind to this address to listen for NATD connections. (Default: "
-"127.0.0.1).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:695
-#, no-wrap
-msgid ""
-"**AutomapHostsOnResolve** **0**|**1**::\n"
-"    When this option is enabled, and we get a request to resolve an "
-"address\n"
-"    that ends with one of the suffixes in **AutomapHostsSuffixes**, we map "
-"an\n"
-"    unused virtual address to that address, and return the new virtual "
-"address. \n"
-"    This is handy for making \".onion\" addresses work with applications "
-"that\n"
-"    resolve an address and then connect to it. (Default: 0).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:699
-#, no-wrap
-msgid ""
-"**AutomapHostsSuffixes** __SUFFIX__,__SUFFIX__,__...__::\n"
-"    A comma-separated list of suffixes to use with "
-"**AutomapHostsOnResolve**.\n"
-"    The \".\" suffix is equivalent to \"all addresses.\" (Default: "
-".exit,.onion).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:703
-#, no-wrap
-msgid ""
-"**DNSPort** __PORT__::\n"
-"    If non-zero, Tor listens for UDP DNS requests on this port and "
-"resolves\n"
-"    them anonymously. (Default: 0).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:706
-#, no-wrap
-msgid ""
-"**DNSListenAddress** __IP__[:__PORT__]::\n"
-"    Bind to this address to listen for DNS connections. (Default: "
-"127.0.0.1).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:712
-#, no-wrap
-msgid ""
-"**ClientDNSRejectInternalAddresses** **0**|**1**::\n"
-"    If true, Tor does not believe any anonymously retrieved DNS answer "
-"that\n"
-"    tells it that an address resolves to an internal address (like 127.0.0.1 "
-"or\n"
-"    192.168.0.1). This option prevents certain browser-based attacks; "
-"don't\n"
-"    turn it off unless you know what you're doing. (Default: 1).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:718
-#, no-wrap
-msgid ""
-"**DownloadExtraInfo** **0**|**1**::\n"
-"    If true, Tor downloads and caches \"extra-info\" documents. These "
-"documents\n"
-"    contain information about servers other than the information in their\n"
-"    regular router descriptors. Tor does not use this information for "
-"anything\n"
-"    itself; to save bandwidth, leave this option turned off. (Default: 0).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:724
-#, no-wrap
-msgid ""
-"**FallbackNetworkstatusFile** __FILENAME__::\n"
-"    If Tor doesn't have a cached networkstatus file, it starts out using "
-"this\n"
-"    one instead. Even if this file is out of date, Tor can still use it to\n"
-"    learn about directory mirrors, so it doesn't need to put load on the\n"
-"    authorities. (Default: None).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:730
-#, no-wrap
-msgid ""
-"**WarnPlaintextPorts** __port__,__port__,__...__::\n"
-"    Tells Tor to issue a warnings whenever the user tries to make an "
-"anonymous\n"
-"    connection to one of these ports. This option is designed to alert "
-"users\n"
-"    to services that risk sending passwords in the clear. (Default:\n"
-"    23,109,110,143).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:734
-#, no-wrap
-msgid ""
-"**RejectPlaintextPorts** __port__,__port__,__...__::\n"
-"    Like WarnPlaintextPorts, but instead of warning about risky port uses, "
-"Tor\n"
-"    will instead refuse to make the connection. (Default: None).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:736
-#, no-wrap
-msgid ""
-"SERVER OPTIONS\n"
-"--------------\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:740
-msgid ""
-"The following options are useful only for servers (that is, if ORPort is "
-"non-zero):"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:745
-#, no-wrap
-msgid ""
-"**Address** __address__::\n"
-"    The IP address or fully qualified domain name of this server (e.g.\n"
-"    moria.mit.edu). You can leave this unset, and Tor will guess your IP\n"
-"    address.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:750
-#, no-wrap
-msgid ""
-"**AllowSingleHopExits** **0**|**1**::\n"
-"    This option controls whether clients can use this server as a single "
-"hop\n"
-"    proxy. If set to 1, clients can use this server as an exit even if it "
-"is\n"
-"    the only hop in the circuit. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:757
-#, no-wrap
-msgid ""
-"**AssumeReachable** **0**|**1**::\n"
-"    This option is used when bootstrapping a new Tor network. If set to 1,\n"
-"    don't do self-reachability testing; just upload your server descriptor\n"
-"    immediately. If **AuthoritativeDirectory** is also set, this option\n"
-"    instructs the dirserver to bypass remote reachability testing too and "
-"list\n"
-"    all connected servers as running.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:763
-#, no-wrap
-msgid ""
-"**BridgeRelay** **0**|**1**::\n"
-"    Sets the relay to act as a \"bridge\" with respect to relaying "
-"connections\n"
-"    from bridge users to the Tor network. Mainly it influences how the "
-"relay\n"
-"    will cache and serve directory information. Usually used in "
-"combination\n"
-"    with PublishServerDescriptor.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:768
-#, no-wrap
-msgid ""
-"**ContactInfo** __email_address__::\n"
-"    Administrative contact information for server. This line might get "
-"picked\n"
-"    up by spam harvesters, so you may want to obscure the fact that it's "
-"an\n"
-"    email address.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:801
-#, no-wrap
-msgid ""
-"**ExitPolicy** __policy__,__policy__,__...__::\n"
-"    Set an exit policy for this server. Each policy is of the form\n"
-"    \"**accept**|**reject** __ADDR__[/__MASK__][:__PORT__]\". If /__MASK__ "
-"is\n"
-"    omitted then this policy just applies to the host given. Instead of "
-"giving\n"
-"    a host or network you can also use \"\\*\" to denote the universe "
-"(0.0.0.0/0).\n"
-"    __PORT__ can be a single port number, an interval of ports\n"
-"    \"__FROM_PORT__-__TO_PORT__\", or \"\\*\". If __PORT__ is omitted, that "
-"means\n"
-"    \"\\*\". +\n"
-" +\n"
-"    For example, \"accept 18.7.22.69:\\*,reject 18.0.0.0/8:\\*,accept "
-"\\*:\\*\" would\n"
-"    reject any traffic destined for MIT except for web.mit.edu, and accept\n"
-"    anything else. +\n"
-" +\n"
-"    To specify all internal and link-local networks (including 0.0.0.0/8,\n"
-"    169.254.0.0/16,    127.0.0.0/8,    192.168.0.0/16, 10.0.0.0/8, and\n"
-"    172.16.0.0/12), you can use the \"private\" alias instead of an "
-"address.\n"
-"    These addresses are rejected by default (at the beginning of your exit\n"
-"    policy), along with your public IP address, unless you set the\n"
-"    ExitPolicyRejectPrivate config option to 0. For example, once you've "
-"done\n"
-"    that, you could allow HTTP to 127.0.0.1 and block all other connections "
-"to\n"
-"    internal networks with \"accept 127.0.0.1:80,reject private:\\*\", "
-"though that\n"
-"    may also allow connections to your own computer that are addressed to "
-"its\n"
-"    public (external) IP address. See RFC 1918 and RFC 3330 for more "
-"details\n"
-"    about internal and reserved IP address space. +\n"
-" +\n"
-"    This directive can be specified multiple times so you don't have to put "
-"it\n"
-"    all on one line. +\n"
-" +\n"
-"    Policies are considered first to last, and the first match wins. If "
-"you\n"
-"    want to \\_replace_ the default exit policy, end your exit policy with\n"
-"    either a reject \\*:* or an accept \\*:*. Otherwise, you're "
-"\\_augmenting_\n"
-"    (prepending to) the default exit policy. The default exit policy is: +\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:813
-#, no-wrap
-msgid ""
-"       reject *:25\n"
-"       reject *:119\n"
-"       reject *:135-139\n"
-"       reject *:445\n"
-"       reject *:563\n"
-"       reject *:1214\n"
-"       reject *:4661-4666\n"
-"       reject *:6346-6429\n"
-"       reject *:6699\n"
-"       reject *:6881-6999\n"
-"       accept *:*\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:818
-#, no-wrap
-msgid ""
-"**ExitPolicyRejectPrivate** **0**|**1**::\n"
-"    Reject all private (local) networks, along with your own public IP "
-"address,\n"
-"    at the beginning of your exit policy. See above entry on ExitPolicy.\n"
-"    (Default: 1)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:822
-#, no-wrap
-msgid ""
-"**MaxOnionsPending** __NUM__::\n"
-"    If you have more than this number of onionskins queued for decrypt, "
-"reject\n"
-"    new ones. (Default: 100)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:830
-#, no-wrap
-msgid ""
-"**MyFamily** __node__,__node__,__...__::\n"
-"    Declare that this Tor server is controlled or administered by a group "
-"or\n"
-"    organization identical or similar to that of the other servers, defined "
-"by\n"
-"    their identity fingerprints or nicknames. When two servers both "
-"declare\n"
-"    that they are in the same \\'family', Tor clients will not use them in "
-"the\n"
-"    same circuit. (Each server only needs to list the other servers in its\n"
-"    family; it doesn't need to list itself, but it won't hurt.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:834
-#, no-wrap
-msgid ""
-"**Nickname** __name__::\n"
-"    Set the server's nickname to \\'name'. Nicknames must be between 1 and "
-"19\n"
-"    characters inclusive, and must contain only the characters "
-"[a-zA-Z0-9].\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:837
-#, no-wrap
-msgid ""
-"**NumCPUs** __num__::\n"
-"    How many processes to use at once for decrypting onionskins. (Default: "
-"1)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:840
-#, no-wrap
-msgid ""
-"**ORPort** __PORT__::\n"
-"    Advertise this port to listen for connections from Tor clients and "
-"servers.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:846
-#, no-wrap
-msgid ""
-"**ORListenAddress** __IP__[:__PORT__]::\n"
-"    Bind to this IP address to listen for connections from Tor clients and\n"
-"    servers. If you specify a port, bind to this port rather than the one\n"
-"    specified in ORPort. (Default: 0.0.0.0) This directive can be "
-"specified\n"
-"    multiple times to bind to multiple addresses/ports.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:857
-#, no-wrap
-msgid ""
-"**PublishServerDescriptor** "
-"**0**|**1**|**v1**|**v2**|**v3**|**bridge**|**hidserv**,**...**::\n"
-"    This option is only considered if you have an ORPort defined. You can\n"
-"    choose multiple arguments, separated by commas.\n"
-" +\n"
-"    If set to 0, Tor will act as a server but it will not publish its\n"
-"    descriptor to the directory authorities. (This is useful if you're "
-"testing\n"
-"    out your server, or if you're using a Tor controller that handles "
-"directory\n"
-"    publishing for you.) Otherwise, Tor will publish its descriptor to all\n"
-"    directory authorities of the type(s) specified. The value \"1\" is the\n"
-"    default, which means \"publish to the appropriate authorities\".\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:863
-#, no-wrap
-msgid ""
-"**ShutdownWaitLength** __NUM__::\n"
-"    When we get a SIGINT and we're a server, we begin shutting down:\n"
-"    we close listeners and start refusing new circuits. After **NUM**\n"
-"    seconds, we exit. If we get a second SIGINT, we exit immedi-\n"
-"    ately. (Default: 30 seconds)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:877
-#, no-wrap
-msgid ""
-"**AccountingMax** __N__ **bytes**|**KB**|**MB**|**GB**|**TB**::\n"
-"    Never send more than the specified number of bytes in a given "
-"accounting\n"
-"    period, or receive more than that number in the period. For example, "
-"with\n"
-"    AccountingMax set to 1 GB, a server could send 900 MB and receive 800 "
-"MB\n"
-"    and continue running. It will only hibernate once one of the two reaches "
-"1\n"
-"    GB. When the number of bytes is exhausted, Tor will hibernate until "
-"some\n"
-"    time in the next accounting period. To prevent all servers from waking "
-"at\n"
-"    the same time, Tor will also wait until a random point in each period\n"
-"    before waking up. If you have bandwidth cost issues, enabling "
-"hibernation\n"
-"    is preferable to setting a low bandwidth, since it provides users with "
-"a\n"
-"    collection of fast servers that are up some of the time, which is more\n"
-"    useful than a set of slow servers that are always \"available\".\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:888
-#, no-wrap
-msgid ""
-"**AccountingStart** **day**|**week**|**month** [__day__] __HH:MM__::\n"
-"    Specify how long accounting periods last. If **month** is given, each\n"
-"    accounting period runs from the time __HH:MM__ on the __dayth__ day of "
-"one\n"
-"    month to the same day and time of the next. (The day must be between 1 "
-"and\n"
-"    28.) If **week** is given, each accounting period runs from the time "
-"__HH:MM__\n"
-"    of the __dayth__ day of one week to the same day and time of the next "
-"week,\n"
-"    with Monday as day 1 and Sunday as day 7. If **day** is given, each\n"
-"    accounting period runs from the time __HH:MM__ each day to the same time "
-"on\n"
-"    the next day. All times are local, and given in 24-hour time. (Defaults "
-"to\n"
-"    \"month 1 0:00\".)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:895
-#, no-wrap
-msgid ""
-"**ServerDNSResolvConfFile** __filename__::\n"
-"    Overrides the default DNS configuration with the configuration in\n"
-"    __filename__. The file format is the same as the standard Unix\n"
-"    \"**resolv.conf**\" file (7). This option, like all other ServerDNS "
-"options,\n"
-"    only affects name lookups that your server does on behalf of clients.\n"
-"    (Defaults to use the system DNS configuration.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:901
-#, no-wrap
-msgid ""
-"**ServerDNSAllowBrokenConfig** **0**|**1**::\n"
-"    If this option is false, Tor exits immediately if there are problems\n"
-"    parsing the system DNS configuration or connecting to nameservers.\n"
-"    Otherwise, Tor continues to periodically retry the system nameservers "
-"until\n"
-"    it eventually succeeds. (Defaults to \"1\".)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:908
-#, no-wrap
-msgid ""
-"**ServerDNSSearchDomains** **0**|**1**::\n"
-"    If set to 1, then we will search for addresses in the local search "
-"domain.\n"
-"    For example, if this system is configured to believe it is in\n"
-"    \"example.com\", and a client tries to connect to \"www\", the client "
-"will be\n"
-"    connected to \"www.example.com\". This option only affects name lookups "
-"that\n"
-"    your server does on behalf of clients. (Defaults to \"0\".)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:915
-#, no-wrap
-msgid ""
-"**ServerDNSDetectHijacking** **0**|**1**::\n"
-"    When this option is set to 1, we will test periodically to determine\n"
-"    whether our local nameservers have been configured to hijack failing "
-"DNS\n"
-"    requests (usually to an advertising site). If they are, we will attempt "
-"to\n"
-"    correct this. This option only affects name lookups that your server "
-"does\n"
-"    on behalf of clients. (Defaults to \"1\".)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:922
-#, no-wrap
-msgid ""
-"**ServerDNSTestAddresses** __address__,__address__,__...__::\n"
-"    When we're detecting DNS hijacking, make sure that these __valid__ "
-"addresses\n"
-"    aren't getting redirected. If they are, then our DNS is completely "
-"useless,\n"
-"    and we'll reset our exit policy to \"reject *:*\". This option only "
-"affects\n"
-"    name lookups that your server does on behalf of clients. (Defaults to\n"
-"    \"www.google.com, www.mit.edu, www.yahoo.com, www.slashdot.org\".)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:929
-#, no-wrap
-msgid ""
-"**ServerDNSAllowNonRFC953Hostnames** **0**|**1**::\n"
-"    When this option is disabled, Tor does not try to resolve hostnames\n"
-"    containing illegal characters (like @ and :) rather than sending them to "
-"an\n"
-"    exit node to be resolved. This helps trap accidental attempts to "
-"resolve\n"
-"    URLs and so on. This option only affects name lookups that your server "
-"does\n"
-"    on behalf of clients. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:935
-#, no-wrap
-msgid ""
-"**BridgeRecordUsageByCountry** **0**|**1**::\n"
-"    When this option is enabled and BridgeRelay is also enabled, and we "
-"have\n"
-"    GeoIP data, Tor keeps a keep a per-country count of how many client\n"
-"    addresses have contacted it so that it can help the bridge authority "
-"guess\n"
-"    which countries have blocked access to it. (Default: 1)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:943
-#, no-wrap
-msgid ""
-"**ServerDNSRandomizeCase** **0**|**1**::\n"
-"    When this option is set, Tor sets the case of each character randomly "
-"in\n"
-"    outgoing DNS requests, and makes sure that the case matches in DNS "
-"replies.\n"
-"    This so-called \"0x20 hack\" helps resist some types of DNS poisoning "
-"attack.\n"
-"    For more information, see \"Increased DNS Forgery Resistance through\n"
-"    0x20-Bit Encoding\". This option only affects name lookups that your "
-"server\n"
-"    does on behalf of clients. (Default: 1)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:946
-#, no-wrap
-msgid ""
-"**GeoIPFile** __filename__::\n"
-"    A filename containing GeoIP data, for use with "
-"BridgeRecordUsageByCountry.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:951
-#, no-wrap
-msgid ""
-"**CellStatistics** **0**|**1**::\n"
-"    When this option is enabled, Tor writes statistics on the mean time "
-"that\n"
-"    cells spend in circuit queues to disk every 24 hours. Cannot be "
-"changed\n"
-"    while Tor is running. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:956
-#, no-wrap
-msgid ""
-"**DirReqStatistics** **0**|**1**::\n"
-"    When this option is enabled, Tor writes statistics on the number and\n"
-"    response time of network status requests to disk every 24 hours. Cannot "
-"be\n"
-"    changed while Tor is running. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:961
-#, no-wrap
-msgid ""
-"**EntryStatistics** **0**|**1**::\n"
-"    When this option is enabled, Tor writes statistics on the number of\n"
-"    directly connecting clients to disk every 24 hours. Cannot be changed "
-"while\n"
-"    Tor is running. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:966
-#, no-wrap
-msgid ""
-"**ExitPortStatistics** **0**|**1**::\n"
-"    When this option is enabled, Tor writes statistics on the number of "
-"relayed\n"
-"    bytes and opened stream per exit port to disk every 24 hours. Cannot "
-"be\n"
-"    changed while Tor is running. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:971
-#, no-wrap
-msgid ""
-"**ExtraInfoStatistics** **0**|**1**::\n"
-"    When this option is enabled, Tor includes previously gathered statistics "
-"in\n"
-"    its extra-info documents that it uploads to the directory authorities.\n"
-"    (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:973
-#, no-wrap
-msgid ""
-"DIRECTORY SERVER OPTIONS\n"
-"------------------------\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:977
-msgid ""
-"The following options are useful only for directory servers (that is, if "
-"DirPort is non-zero):"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:985
-#, no-wrap
-msgid ""
-"**AuthoritativeDirectory** **0**|**1**::\n"
-"    When this option is set to 1, Tor operates as an authoritative "
-"directory\n"
-"    server. Instead of caching the directory, it generates its own list of\n"
-"    good servers, signs it, and sends that to the clients. Unless the "
-"clients\n"
-"    already have you listed as a trusted directory, you probably do not "
-"want\n"
-"    to set this option. Please coordinate with the other admins at\n"
-"    tor-ops@xxxxxxxxxxxxxx if you think you should be a directory.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:991
-#, no-wrap
-msgid ""
-"**DirPortFrontPage** __FILENAME__::\n"
-"    When this option is set, it takes an HTML file and publishes it as \"/\" "
-"on\n"
-"    the DirPort. Now relay operators can provide a disclaimer without "
-"needing\n"
-"    to set up a separate webserver. There's a sample disclaimer in\n"
-"    contrib/tor-exit-notice.html.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:996
-#, no-wrap
-msgid ""
-"**V1AuthoritativeDirectory** **0**|**1**::\n"
-"    When this option is set in addition to **AuthoritativeDirectory**, Tor\n"
-"    generates version 1 directory and running-routers documents (for "
-"legacy\n"
-"    Tor clients up to 0.1.0.x).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1002
-#, no-wrap
-msgid ""
-"**V2AuthoritativeDirectory** **0**|**1**::\n"
-"    When this option is set in addition to **AuthoritativeDirectory**, Tor\n"
-"    generates version 2 network statuses and serves descriptors, etc as\n"
-"    described in doc/spec/dir-spec-v2.txt (for Tor clients and servers "
-"running\n"
-"    0.1.1.x and 0.1.2.x).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1008
-#, no-wrap
-msgid ""
-"**V3AuthoritativeDirectory** **0**|**1**::\n"
-"    When this option is set in addition to **AuthoritativeDirectory**, Tor\n"
-"    generates version 3 network statuses and serves descriptors, etc as\n"
-"    described in doc/spec/dir-spec.txt (for Tor clients and servers running "
-"at\n"
-"    least 0.2.0.x).\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1015
-#, no-wrap
-msgid ""
-"**VersioningAuthoritativeDirectory** **0**|**1**::\n"
-"    When this option is set to 1, Tor adds information on which versions "
-"of\n"
-"    Tor are still believed safe for use to the published directory. Each\n"
-"    version 1 authority is automatically a versioning authority; version 2\n"
-"    authorities provide this service optionally. See "
-"**RecommendedVersions**,\n"
-"    **RecommendedClientVersions**, and **RecommendedServerVersions**.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1024
-#, no-wrap
-msgid ""
-"**NamingAuthoritativeDirectory** **0**|**1**::\n"
-"    When this option is set to 1, then the server advertises that it has\n"
-"    opinions about nickname-to-fingerprint bindings. It will include these\n"
-"    opinions in its published network-status pages, by listing servers "
-"with\n"
-"    the flag \"Named\" if a correct binding between that nickname and "
-"fingerprint\n"
-"    has been registered with the dirserver. Naming dirservers will refuse "
-"to\n"
-"    accept or publish descriptors that contradict a registered "
-"binding. See\n"
-"    **approved-routers** in the **FILES** section below.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1028
-#, no-wrap
-msgid ""
-"**HSAuthoritativeDir** **0**|**1**::\n"
-"    When this option is set in addition to **AuthoritativeDirectory**, Tor "
-"also\n"
-"    accepts and serves hidden service descriptors. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1033
-#, no-wrap
-msgid ""
-"**HidServDirectoryV2** **0**|**1**::\n"
-"    When this option is set, Tor accepts and serves v2 hidden service\n"
-"    descriptors. Setting DirPort is not required for this, because clients\n"
-"    connect via the ORPort by default. (Default: 1)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1038
-#, no-wrap
-msgid ""
-"**BridgeAuthoritativeDir** **0**|**1**::\n"
-"    When this option is set in addition to **AuthoritativeDirectory**, Tor\n"
-"    accepts and serves router descriptors, but it caches and serves the "
-"main\n"
-"    networkstatus documents rather than generating its own. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1042
-#, no-wrap
-msgid ""
-"**MinUptimeHidServDirectoryV2** __N__ "
-"**seconds**|**minutes**|**hours**|**days**|**weeks**::\n"
-"    Minimum uptime of a v2 hidden service directory to be accepted as such "
-"by\n"
-"    authoritative directories. (Default: 24 hours)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1045
-#, no-wrap
-msgid ""
-"**DirPort** __PORT__::\n"
-"    Advertise the directory service on this port.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1051
-#, no-wrap
-msgid ""
-"**DirListenAddress** __IP__[:__PORT__]::\n"
-"    Bind the directory service to this address. If you specify a port, bind "
-"to\n"
-"    this port rather than the one specified in DirPort.  (Default: "
-"0.0.0.0)\n"
-"    This directive can be specified multiple times  to bind to multiple\n"
-"    addresses/ports.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1055
-#, no-wrap
-msgid ""
-"**DirPolicy** __policy__,__policy__,__...__::\n"
-"    Set an entrance policy for this server, to limit who can connect to "
-"the\n"
-"    directory ports. The policies have the same form as exit policies "
-"above.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1057
-#, no-wrap
-msgid ""
-"DIRECTORY AUTHORITY SERVER OPTIONS\n"
-"----------------------------------\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1065
-#, no-wrap
-msgid ""
-"**RecommendedVersions** __STRING__::\n"
-"    STRING is a comma-separated list of Tor versions currently believed to "
-"be\n"
-"    safe. The list is included in each directory, and nodes which pull down "
-"the\n"
-"    directory learn whether they need to upgrade. This option can appear\n"
-"    multiple times: the values from multiple lines are spliced "
-"together. When\n"
-"    this is set then **VersioningAuthoritativeDirectory** should be set "
-"too.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1072
-#, no-wrap
-msgid ""
-"**RecommendedClientVersions** __STRING__::\n"
-"    STRING is a comma-separated list of Tor versions currently believed to "
-"be\n"
-"    safe for clients to use. This information is included in version 2\n"
-"    directories. If this is not set then the value of "
-"**RecommendedVersions**\n"
-"    is used. When this is set then **VersioningAuthoritativeDirectory** "
-"should\n"
-"    be set too.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1079
-#, no-wrap
-msgid ""
-"**RecommendedServerVersions** __STRING__::\n"
-"    STRING is a comma-separated list of Tor versions currently believed to "
-"be\n"
-"    safe for servers to use. This information is included in version 2\n"
-"    directories. If this is not set then the value of "
-"**RecommendedVersions**\n"
-"    is used. When this is set then **VersioningAuthoritativeDirectory** "
-"should\n"
-"    be set too.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1083
-#, no-wrap
-msgid ""
-"**ConsensusParams** __STRING__::\n"
-"    STRING is a space-separated list of key=value pairs that Tor will "
-"include\n"
-"    in the \"params\" line of its networkstatus vote.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1088
-#, no-wrap
-msgid ""
-"**DirAllowPrivateAddresses** **0**|**1**::\n"
-"    If set to 1, Tor will accept router descriptors with arbitrary "
-"\"Address\"\n"
-"    elements. Otherwise, if the address is not an IP address or is a private "
-"IP\n"
-"    address, it will reject the router descriptor. Defaults to 0.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1093
-#, no-wrap
-msgid ""
-"**AuthDirBadDir** __AddressPattern...__::\n"
-"    Authoritative directories only. A set of address patterns for servers "
-"that\n"
-"    will be listed as bad directories in any network status document this\n"
-"    authority publishes, if **AuthDirListBadDirs** is set.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1098
-#, no-wrap
-msgid ""
-"**AuthDirBadExit** __AddressPattern...__::\n"
-"    Authoritative directories only. A set of address patterns for servers "
-"that\n"
-"    will be listed as bad exits in any network status document this "
-"authority\n"
-"    publishes, if **AuthDirListBadExits** is set.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1103
-#, no-wrap
-msgid ""
-"**AuthDirInvalid** __AddressPattern...__::\n"
-"    Authoritative directories only. A set of address patterns for servers "
-"that\n"
-"    will never be listed as \"valid\" in any network status document that "
-"this\n"
-"    authority publishes.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1109
-#, no-wrap
-msgid ""
-"**AuthDirReject** __AddressPattern__...::\n"
-"    Authoritative directories only. A set of address patterns for servers "
-"that\n"
-"    will never be listed at all in any network status document that this\n"
-"    authority publishes, or accepted as an OR address in any descriptor\n"
-"    submitted for publication by this authority.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1116
-#, no-wrap
-msgid ""
-"**AuthDirListBadDirs** **0**|**1**::\n"
-"    Authoritative directories only. If set to 1, this directory has some\n"
-"    opinion about which nodes are unsuitable as directory caches. (Do not "
-"set\n"
-"    this to 1 unless you plan to list non-functioning directories as bad;\n"
-"    otherwise, you are effectively voting in favor  of every declared\n"
-"    directory.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1122
-#, no-wrap
-msgid ""
-"**AuthDirListBadExits** **0**|**1**::\n"
-"    Authoritative directories only. If set to 1, this directory has some\n"
-"    opinion about which nodes are unsuitable as exit nodes. (Do not set this "
-"to\n"
-"    1 unless you plan to list non-functioning exits as bad; otherwise, you "
-"are\n"
-"    effectively voting in favor of every declared exit as an exit.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1128
-#, no-wrap
-msgid ""
-"**AuthDirRejectUnlisted** **0**|**1**::\n"
-"    Authoritative directories only. If set to 1, the directory server "
-"rejects\n"
-"    all uploaded server descriptors that aren't explicitly listed in the\n"
-"    fingerprints file. This acts as a \"panic button\" if we get hit with a "
-"Sybil\n"
-"    attack. (Default: 0)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1133
-#, no-wrap
-msgid ""
-"**AuthDirMaxServersPerAddr** __NUM__::\n"
-"    Authoritative directories only. The maximum number of servers that we "
-"will\n"
-"    list as acceptable on a single IP address. Set this to \"0\" for \"no "
-"limit\".\n"
-"    (Default: 2)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1137
-#, no-wrap
-msgid ""
-"**AuthDirMaxServersPerAuthAddr** __NUM__::\n"
-"    Authoritative directories only. Like AuthDirMaxServersPerAddr, but "
-"applies\n"
-"    to addresses shared with directory authorities. (Default: 5)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1143
-#, no-wrap
-msgid ""
-"**V3AuthVotingInterval** __N__ **minutes**|**hours**::\n"
-"    V3 authoritative directories only. Configures the server's preferred "
-"voting\n"
-"    interval. Note that voting will __actually__ happen at an interval "
-"chosen\n"
-"    by consensus from all the authorities' preferred intervals. This time\n"
-"    SHOULD divide evenly into a day. (Default: 1 hour)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1149
-#, no-wrap
-msgid ""
-"**V3AuthVoteDelay** __N__ **minutes**|**hours**::\n"
-"    V3 authoritative directories only. Configures the server's preferred "
-"delay\n"
-"    between publishing its vote and assuming it has all the votes from all "
-"the\n"
-"    other authorities. Note that the actual time used is not the server's\n"
-"    preferred time, but the consensus of all preferences. (Default: 5 "
-"minutes.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1156
-#, no-wrap
-msgid ""
-"**V3AuthDistDelay** __N__ **minutes**|**hours**::\n"
-"    V3 authoritative directories only. Configures the server's preferred  "
-"delay\n"
-"    between publishing its consensus and signature and assuming  it has all "
-"the\n"
-"    signatures from all the other authorities. Note that the actual time "
-"used\n"
-"    is not the server's preferred time,  but the consensus of all "
-"preferences.\n"
-"    (Default: 5 minutes.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1164
-#, no-wrap
-msgid ""
-"**V3AuthNIntervalsValid** __NUM__::\n"
-"    V3 authoritative directories only. Configures the number of "
-"VotingIntervals\n"
-"    for which each consensus should be valid for. Choosing high numbers\n"
-"    increases network partitioning risks; choosing low numbers increases\n"
-"    directory traffic. Note that the actual number of intervals used is not "
-"the\n"
-"    server's preferred number, but the consensus of all preferences. Must be "
-"at\n"
-"    least 2. (Default: 3.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1166
-#, no-wrap
-msgid ""
-"HIDDEN SERVICE OPTIONS\n"
-"----------------------\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1169
-msgid "The following options are used to configure a hidden service."
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1174
-#, no-wrap
-msgid ""
-"**HiddenServiceDir** __DIRECTORY__::\n"
-"    Store data files for a hidden service in DIRECTORY. Every hidden "
-"service\n"
-"    must have a separate directory. You may use this option  multiple times "
-"to\n"
-"    specify multiple services.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1183
-#, no-wrap
-msgid ""
-"**HiddenServicePort** __VIRTPORT__ [__TARGET__]::\n"
-"    Configure a virtual port VIRTPORT for a hidden service. You may use "
-"this\n"
-"    option multiple times; each time applies to the service using the most\n"
-"    recent hiddenservicedir. By default, this option maps the virtual port "
-"to\n"
-"    the same port on 127.0.0.1. You may override the target port, address, "
-"or\n"
-"    both by specifying a target of addr, port, or addr:port. You may also "
-"have\n"
-"    multiple lines with  the same VIRTPORT: when a user connects to that\n"
-"    VIRTPORT, one of the TARGETs from those lines will be chosen at "
-"random.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1189
-#, no-wrap
-msgid ""
-"**PublishHidServDescriptors** **0**|**1**::\n"
-"    If set to 0, Tor will run any hidden services you configure, but it "
-"won't\n"
-"    advertise them to the rendezvous directory. This option is only useful "
-"if\n"
-"    you're using a Tor controller that handles hidserv publishing for you.\n"
-"    (Default: 1)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1193
-#, no-wrap
-msgid ""
-"**HiddenServiceVersion** __version__,__version__,__...__::\n"
-"    A list of rendezvous service descriptor versions to publish for the "
-"hidden\n"
-"    service. Currently, only version 2 is supported. (Default: 2)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1205
-#, no-wrap
-msgid ""
-"**HiddenServiceAuthorizeClient** __auth-type__ "
-"__client-name__,__client-name__,__...__::\n"
-"    If configured, the hidden service is accessible for authorized clients\n"
-"    only. The auth-type can either be \\'basic' for a general-purpose\n"
-"    authorization protocol or \\'stealth' for a less scalable protocol that "
-"also\n"
-"    hides service activity from unauthorized clients. Only clients that "
-"are\n"
-"    listed here are authorized to access the hidden service. Valid client "
-"names\n"
-"    are 1 to 19 characters  long and only use characters in A-Za-z0-9+-_ "
-"(no\n"
-"    spaces). If this option is set, the hidden service is not accessible "
-"for\n"
-"    clients without authorization any more. Generated authorization data can "
-"be\n"
-"    found in the hostname file. Clients need to put this authorization data "
-"in\n"
-"    their configuration file using **HidServAuth**.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1210
-#, no-wrap
-msgid ""
-"**RendPostPeriod** __N__ "
-"**seconds**|**minutes**|**hours**|**days**|**weeks**::\n"
-"    Every time the specified period elapses, Tor uploads any rendezvous \n"
-"    service descriptors to the directory servers. This information  is "
-"also\n"
-"    uploaded whenever it changes. (Default: 20 minutes)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1212
-#, no-wrap
-msgid ""
-"TESTING NETWORK OPTIONS\n"
-"-----------------------\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1215
-msgid "The following options are used for running a testing Tor network."
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1221
-#, no-wrap
-msgid ""
-"**TestingTorNetwork** **0**|**1**::\n"
-"    If set to 1, Tor adjusts default values of the configuration options "
-"below,\n"
-"    so that it is easier to set up a testing Tor network. May only be set "
-"if\n"
-"    non-default set of DirServers is set. Cannot be unset while Tor is "
-"running.\n"
-"    (Default: 0) +\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1238
-#, no-wrap
-msgid ""
-"       ServerDNSAllowBrokenConfig 1\n"
-"       DirAllowPrivateAddresses 1\n"
-"       EnforceDistinctSubnets 0\n"
-"       AssumeReachable 1\n"
-"       AuthDirMaxServersPerAddr 0\n"
-"       AuthDirMaxServersPerAuthAddr 0\n"
-"       ClientDNSRejectInternalAddresses 0\n"
-"       ExitPolicyRejectPrivate 0\n"
-"       V3AuthVotingInterval 5 minutes\n"
-"       V3AuthVoteDelay 20 seconds\n"
-"       V3AuthDistDelay 20 seconds\n"
-"       TestingV3AuthInitialVotingInterval 5 minutes\n"
-"       TestingV3AuthInitialVoteDelay 20 seconds\n"
-"       TestingV3AuthInitialDistDelay 20 seconds\n"
-"       TestingAuthDirTimeToLearnReachability 0 minutes\n"
-"       TestingEstimatedDescriptorPropagationTime 0 minutes\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1243
-#, no-wrap
-msgid ""
-"**TestingV3AuthInitialVotingInterval** __N__ **minutes**|**hours**::\n"
-"    Like V3AuthVotingInterval, but for initial voting interval before the "
-"first\n"
-"    consensus has been created. Changing this requires that\n"
-"    **TestingTorNetwork** is set. (Default: 30 minutes)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1248
-#, no-wrap
-msgid ""
-"**TestingV3AuthInitialVoteDelay** __N__ **minutes**|**hours**::\n"
-"    Like TestingV3AuthInitialVoteDelay, but for initial voting interval "
-"before\n"
-"    the first consensus has been created. Changing this requires that\n"
-"    **TestingTorNetwork** is set. (Default: 5 minutes)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1253
-#, no-wrap
-msgid ""
-"**TestingV3AuthInitialDistDelay** __N__ **minutes**|**hours**::\n"
-"    Like TestingV3AuthInitialDistDelay, but for initial voting interval "
-"before\n"
-"    the first consensus has been created. Changing this requires that\n"
-"    **TestingTorNetwork** is set. (Default: 5 minutes)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1258
-#, no-wrap
-msgid ""
-"**TestingAuthDirTimeToLearnReachability** __N__ **minutes**|**hours**::\n"
-"    After starting as an authority, do not make claims about whether "
-"routers\n"
-"    are Running until this much time has passed. Changing this requires\n"
-"    that **TestingTorNetwork** is set.  (Default: 30 minutes)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1263
-#, no-wrap
-msgid ""
-"**TestingEstimatedDescriptorPropagationTime** __N__ "
-"**minutes**|**hours**::\n"
-"    Clients try downloading router descriptors from directory caches after "
-"this\n"
-"    time. Changing this requires that **TestingTorNetwork** is "
-"set. (Default:\n"
-"    10 minutes)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1265
-#, no-wrap
-msgid ""
-"SIGNALS\n"
-"-------\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1268
-msgid "Tor catches the following signals:"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1271
-#, no-wrap
-msgid ""
-"**SIGTERM**::\n"
-"    Tor will catch this, clean up and sync to disk if necessary, and exit.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1276
-#, no-wrap
-msgid ""
-"**SIGINT**::\n"
-"    Tor clients behave as with SIGTERM; but Tor servers will do a "
-"controlled\n"
-"    slow shutdown, closing listeners and waiting 30 seconds before "
-"exiting.\n"
-"    (The delay can be configured with the ShutdownWaitLength config "
-"option.)\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1281
-#, no-wrap
-msgid ""
-"**SIGHUP**:: \n"
-"    The signal instructs Tor to reload its configuration (including closing "
-"and\n"
-"    reopening logs), fetch a new directory, and kill and restart its "
-"helper\n"
-"    processes if applicable.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1284
-#, no-wrap
-msgid ""
-"**SIGUSR1**::\n"
-"    Log statistics about current connections, past connections, and "
-"throughput.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1288
-#, no-wrap
-msgid ""
-"**SIGUSR2**::\n"
-"    Switch all logs to loglevel debug. You can go back to the old loglevels "
-"by\n"
-"    sending a SIGHUP.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1292
-#, no-wrap
-msgid ""
-"**SIGCHLD**::\n"
-"    Tor receives this signal when one of its helper processes has exited, so "
-"it\n"
-"    can clean up.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1295
-#, no-wrap
-msgid ""
-"**SIGPIPE**::\n"
-"    Tor catches this signal and ignores it.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1298
-#, no-wrap
-msgid ""
-"**SIGXFSZ**::\n"
-"    If this signal exists on your platform, Tor catches and ignores it.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1300
-#, no-wrap
-msgid ""
-"FILES\n"
-"-----\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1304
-#, no-wrap
-msgid ""
-"**@CONFDIR@/torrc**::\n"
-"    The configuration file, which contains \"option value\" pairs.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1307
-#, no-wrap
-msgid ""
-"**@LOCALSTATEDIR@/lib/tor/**::\n"
-"    The tor process stores keys and other data here.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1312
-#, no-wrap
-msgid ""
-"__DataDirectory__**/cached-status/**::\n"
-"    The most recently downloaded network status document for each "
-"authority.\n"
-"    Each file holds one such document; the filenames are the hexadecimal\n"
-"    identity key fingerprints of the directory authorities.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1319
-#, no-wrap
-msgid ""
-"__DataDirectory__**/cached-descriptors** and **cached-descriptors.new**::\n"
-"    These files hold downloaded router statuses. Some routers may appear "
-"more\n"
-"    than once; if so, the most recently published descriptor is "
-"used. Lines\n"
-"    beginning with @-signs are annotations that contain more information "
-"about\n"
-"    a given router. The \".new\" file is an append-only journal; when it "
-"gets\n"
-"    too large, all entries are merged into a new cached-descriptors file.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1323
-#, no-wrap
-msgid ""
-"__DataDirectory__**/cached-routers** and **cached-routers.new**::\n"
-"    Obsolete versions of cached-descriptors and "
-"cached-descriptors.new. When\n"
-"    Tor can't find the newer files, it looks here instead.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1334
-#, no-wrap
-msgid ""
-"__DataDirectory__**/state**::\n"
-"    A set of persistent key-value mappings. These are documented in\n"
-"    the file. These include:\n"
-"            - The current entry guards and their status.\n"
-"            - The current bandwidth accounting values (unused so far; see\n"
-"            below).\n"
-"            - When the file was last written\n"
-"            - What version of Tor generated the state file\n"
-"            - A short history of bandwidth usage, as produced in the "
-"router\n"
-"            descriptors.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1340
-#, no-wrap
-msgid ""
-"__DataDirectory__**/bw_accounting**::\n"
-"    Used to track bandwidth accounting values (when the current period "
-"starts\n"
-"    and ends; how much has been read and written so far this period). This "
-"file\n"
-"    is obsolete, and the data is now stored in the \\'state' file as "
-"well. Only\n"
-"    used when bandwidth accounting is enabled.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1346
-#, no-wrap
-msgid ""
-"__DataDirectory__**/control_auth_cookie**::\n"
-"    Used for cookie authentication with the controller. Location can be\n"
-"    overridden by the CookieAuthFile config option. Regenerated on "
-"startup. See\n"
-"    control-spec.txt for details. Only used when cookie authentication is\n"
-"    enabled.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1349
-#, no-wrap
-msgid ""
-"__DataDirectory__**/keys/***::\n"
-"    Only used by servers. Holds identity keys and onion keys.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1352
-#, no-wrap
-msgid ""
-"__DataDirectory__**/fingerprint**::\n"
-"    Only used by servers. Holds the fingerprint of the server's identity "
-"key.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1362
-#, no-wrap
-msgid ""
-"__DataDirectory__**/approved-routers**::\n"
-"    Only for naming authoritative directory servers (see\n"
-"    **NamingAuthoritativeDirectory**). This file lists nickname to "
-"identity\n"
-"    bindings. Each line lists a nickname and a fingerprint separated by\n"
-"    whitespace. See your **fingerprint** file in the __DataDirectory__ for "
-"an\n"
-"    example line. If the nickname is **!reject** then descriptors from the\n"
-"    given identity (fingerprint) are rejected by this server. If it is\n"
-"    **!invalid** then descriptors are accepted but marked in the directory "
-"as\n"
-"    not valid, that is, not recommended.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1367
-#, no-wrap
-msgid ""
-"__DataDirectory__**/router-stability**::\n"
-"    Only used by authoritative directory servers. Tracks measurements for\n"
-"    router mean-time-between-failures so that authorities have a good idea "
-"of\n"
-"    how to set their Stable flags.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1372
-#, no-wrap
-msgid ""
-"__HiddenServiceDirectory__**/hostname**::\n"
-"    The <base32-encoded-fingerprint>.onion domain name for this hidden "
-"service.\n"
-"    If the hidden service is restricted to authorized clients only, this "
-"file\n"
-"    also contains authorization data for all clients.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1375
-#, no-wrap
-msgid ""
-"__HiddenServiceDirectory__**/private_key**::\n"
-"    The private key for this hidden service.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1379
-#, no-wrap
-msgid ""
-"__HiddenServiceDirectory__**/client_keys**::\n"
-"    Authorization data for a hidden service that is only accessible by\n"
-"    authorized clients.\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1381
-#, no-wrap
-msgid ""
-"SEE ALSO\n"
-"--------\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1383
-#, no-wrap
-msgid "**privoxy**(1), **tsocks**(1), **torify**(1) +\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1385
-#, no-wrap
-msgid "**https://www.torproject.org/**\n";
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1388
-#, no-wrap
-msgid ""
-"BUGS\n"
-"----\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1391
-msgid "Plenty, probably. Tor is still in development. Please report them."
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1393
-#, no-wrap
-msgid ""
-"AUTHORS\n"
-"-------\n"
-msgstr ""
-
-# type: Plain text
-#: tor.1.txt:1395
-msgid "Roger Dingledine [arma at mit.edu], Nick Mathewson [nickm at alum.mit.edu]."
-msgstr ""

Deleted: translation/trunk/projects/manpages/po/templates/torify.1.po
===================================================================
--- translation/trunk/projects/manpages/po/templates/torify.1.po	2010-12-05 19:16:01 UTC (rev 23895)
+++ translation/trunk/projects/manpages/po/templates/torify.1.po	2010-12-05 19:23:15 UTC (rev 23896)
@@ -1,147 +0,0 @@
-# SOME DESCRIPTIVE TITLE
-# Copyright (C) YEAR The Tor Project, Inc.
-# This file is distributed under the same license as the PACKAGE package.
-# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#, fuzzy
-msgid ""
-msgstr ""
-"Project-Id-Version: PACKAGE VERSION\n"
-"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2010-05-27 19:08+0300\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
-"Language-Team: LANGUAGE <LL@xxxxxx>\n"
-"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit\n"
-"X-Generator: Translate Toolkit 1.5.3\n"
-
-# type: Plain text
-#: torify.1.txt:6
-#, no-wrap
-msgid ""
-"// Copyright (c) The Tor Project, Inc.\n"
-"// See LICENSE for licensing information\n"
-"// This is an asciidoc file used to generate the manpage/html reference.\n"
-"// Learn asciidoc on http://www.methods.co.nz/asciidoc/userguide.html\n";
-"torify(1)\n"
-"=========\n"
-msgstr ""
-
-# type: Plain text
-#: torify.1.txt:9
-msgid "Peter Palfrader Jacob Appelbaum"
-msgstr ""
-
-# type: Plain text
-#: torify.1.txt:11
-#, no-wrap
-msgid ""
-"NAME\n"
-"----\n"
-msgstr ""
-
-# type: Plain text
-#: torify.1.txt:13
-msgid "torify - wrapper for torsocks or tsocks and tor"
-msgstr ""
-
-# type: Plain text
-#: torify.1.txt:15
-#, no-wrap
-msgid ""
-"SYNOPSIS\n"
-"--------\n"
-msgstr ""
-
-# type: Plain text
-#: torify.1.txt:17
-#, no-wrap
-msgid "**torify** __application__ [__application's__ __arguments__]\n"
-msgstr ""
-
-# type: Plain text
-#: torify.1.txt:19
-#, no-wrap
-msgid ""
-"DESCRIPTION\n"
-"-----------\n"
-msgstr ""
-
-# type: Plain text
-#: torify.1.txt:23
-#, no-wrap
-msgid ""
-"**torify** is a simple wrapper that attempts to find the best underlying "
-"Tor\n"
-"wrapper available on a system. It calls torsocks or tsocks with a tor "
-"specific\n"
-"configuration file. +\n"
-msgstr ""
-
-# type: Plain text
-#: torify.1.txt:26
-msgid ""
-"torsocks is an improved wrapper that explictly rejects UDP, safely resolves "
-"DNS lookups and properly socksifies your TCP connections. +"
-msgstr ""
-
-# type: Plain text
-#: torify.1.txt:29
-msgid ""
-"tsocks itself is a wrapper between the tsocks library and the application "
-"that you would like to run socksified. +"
-msgstr ""
-
-# type: Plain text
-#: torify.1.txt:32
-msgid ""
-"Please note that since both method use LD_PRELOAD, torify cannot be applied "
-"to suid binaries."
-msgstr ""
-
-# type: Plain text
-#: torify.1.txt:34
-#, no-wrap
-msgid ""
-"WARNING\n"
-"-------\n"
-msgstr ""
-
-# type: Plain text
-#: torify.1.txt:42
-msgid ""
-"You should also be aware that the way tsocks currently works only TCP "
-"connections are socksified. Be aware that this will in most circumstances "
-"not include hostname lookups which would still be routed through your normal "
-"system resolver to your usual resolving nameservers. The **tor-resolve**(1) "
-"tool can be useful as a workaround in some cases. The Tor FAQ at "
-"https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ might have further "
-"information on this subject. +"
-msgstr ""
-
-# type: Plain text
-#: torify.1.txt:44
-msgid "When used with torsocks, torify should not leak DNS requests or UDP data. +"
-msgstr ""
-
-# type: Plain text
-#: torify.1.txt:46
-msgid "Both will leak ICMP data."
-msgstr ""
-
-# type: Plain text
-#: torify.1.txt:48
-#, no-wrap
-msgid ""
-"SEE ALSO\n"
-"--------\n"
-msgstr ""
-
-# type: Plain text
-#: torify.1.txt:50
-#, no-wrap
-msgid ""
-"**tor**(1), **tor-resolve**(1), **torsocks**(1), **tsocks**(1),\n"
-"**tsocks.conf**(5).\n"
-msgstr ""