From: Nick Mathewson Date: Thu, 3 May 2007 17:43:49 +0000 (+0000) Subject: r12642@catbus: nickm | 2007-05-03 13:43:24 -0400 X-Git-Tag: tor-0.2.0.1-alpha~180 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=f3d1121ff7250bfed01247237205571bc8e0757d;p=thirdparty%2Ftor.git r12642@catbus: nickm | 2007-05-03 13:43:24 -0400 Document the nonpersistent controller-only options. svn:r10107 --- diff --git a/doc/spec/control-spec.txt b/doc/spec/control-spec.txt index 4adcbd8b5f..64596bac97 100644 --- a/doc/spec/control-spec.txt +++ b/doc/spec/control-spec.txt @@ -1338,3 +1338,39 @@ $Id$ command in both protocol versions, and implementations can detect which error they have received. +5.4. Options for use by controllers + + Tor provides a few special configuration options for use by controllers. + These options can be set and examined by the SETCONF and GETCONF commands, + but are not saved to disk by SAVECONF. + + Generally, these options make Tor unusable by disabling a portion of Tor's + normal operations. Unless a controller provides replacement functionality + to fill this gap, Tor will not correctly handle user requests. + + __AllDirOptionsPrivate + + If true, Tor will try to launch all directory operations through + anonymous connections. (Ordinarily, Tor only tries to anonymize + requests related to hidden services.) This option will slow down + directory access, and may stop Tor from working entirely if it does not + yet have enough directory information to build circuits. + + (Boolean. Default: "0".) + + __DisablePredictedCircuits + + If true, Tor will not launch preemptive "general purpose" circuits for + streams to attach to. (It will still launch circuits for testing and + for hidden services.) + + (Boolean. Default: "0".) + + __LeaveStreamsUnattached + + If true, Tor will not automatically attach new streams to circuits; + instead, the controller must attach them with ATTACHSTREAM. If the + controller does not attach the streams, their data will never be routed. + + (Boolean. Default: "0".) +