commit 0b8aaf185c5ee990341df21467007a207973eaaf Author: Sebastian Hahn sebastian@torproject.org Date: Thu Jul 21 17:45:45 2011 +0200

Add some new requirements to the README --- README | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/README b/README index 5e2fa87..eb618ab 100644 --- a/README +++ b/README @@ -20,7 +20,7 @@ Software Requirements

The following are required to run TorBEL on your system:

- - Tor 0.2.2.13-alpha or higher recommended, with an open + - Tor 0.2.2.30-rc or higher recommended, with an open control port. - Python (>= 2.5 is required, >= 2.6 is recommended and required for JSON support) @@ -52,6 +52,7 @@ is available in your torrc: - FetchDirInfoExtraEarly 1 (Tor >= 0.2.2.13-alpha) - LearnCircuitBuiltTimeout 0 (Tor >= 0.2.2.14-alpha) - WarnUnsafeSocks 0 (Tor >= 0.2.2.14-alpha) + - FetchV2Networkstatus 1 (Tor >= 0.2.2.26-beta) These options significantly affect Tor's operation and thus you should not run other applications that depend on Tor's normal operation with the same instance used by TorBEL. @@ -151,4 +152,4 @@ You can configure TorBEL to log to any combination of stdout, syslog, and a (non-rotated) log file. Logging to file is extremely useful for debugging. Be warned that if your log_level is set to DEBUG or lower, your daemon.log (or wherever your syslog ends up) will get utterly -spammed. You have been warned! \ No newline at end of file +spammed. You have been warned!