1 Changes in version 0.2.3.14-alpha - 2012-04-23
2 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
3 candidate. It also dramatically speeds up AES: fast relays should
4 consider switching to the newer OpenSSL library.
6 o Directory authority changes:
7 - Change IP address for ides (v3 directory authority), and rename
11 - Avoid logging uninitialized data when unable to decode a hidden
12 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
13 - Avoid a client-side assertion failure when receiving an INTRODUCE2
14 cell on a general purpose circuit. Fixes bug 5644; bugfix on
16 - If authorities are unable to get a v2 consensus document from other
17 directory authorities, they no longer fall back to fetching
18 them from regular directory caches. Fixes bug 5635; bugfix on
19 0.2.2.26-beta, where routers stopped downloading v2 consensus
21 - When we start a Tor client with a normal consensus already cached,
22 be willing to download a microdescriptor consensus. Fixes bug 4011;
25 o Major features (performance):
26 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
27 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
28 vectorized AES implementations as appropriate. These can be much,
29 much faster than other AES implementations.
31 o Minor bugfixes (0.2.2.x and earlier):
32 - Don't launch more than 10 service-side introduction-point circuits
33 for a hidden service in five minutes. Previously, we would consider
34 launching more introduction-point circuits if at least one second
35 had passed without any introduction-point circuits failing. Fixes
36 bug 4607; bugfix on 0.0.7pre1.
37 - Change the BridgePassword feature (part of the "bridge community"
38 design, which is not yet implemented) to use a time-independent
39 comparison. The old behavior might have allowed an adversary
40 to use timing to guess the BridgePassword value. Fixes bug 5543;
41 bugfix on 0.2.0.14-alpha.
42 - Enforce correct return behavior of tor_vsscanf() when the '%%'
43 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
44 - When sending an HTTP/1.1 proxy request, include a Host header.
45 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
46 - Don't log that we have "decided to publish new relay descriptor"
47 unless we are actually publishing a descriptor. Fixes bug 3942;
48 bugfix on 0.2.2.28-beta.
50 o Minor bugfixes (0.2.3.x):
51 - Fix a bug where a bridge authority crashes (on a failed assert)
52 if it has seen no directory requests when it's time to write
53 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
54 - Fix bug stomping on ORPort option NoListen and ignoring option
55 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
56 - In the testsuite, provide a large enough buffer in the tor_sscanf
57 unit test. Otherwise we'd overrun that buffer and crash during
58 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
60 - Make sure we create the keys directory if it doesn't exist and we're
61 about to store the dynamic Diffie-Hellman parameters. Fixes bug
62 5572; bugfix on 0.2.3.13-alpha.
63 - Fix a small memory leak when trying to decode incorrect base16
64 authenticator during SAFECOOKIE authentication. Found by
65 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
68 - Add more information to a log statement that might help track down
69 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
70 non-IP address" messages (or any Bug messages, for that matter!),
71 please let us know about it.
72 - Relays now understand an IPv6 address when they get one from a
73 directory server. Resolves ticket 4875.
74 - Resolve IPv6 addresses in bridge and entry statistics to country
75 code "??" which means we at least count them. Resolves ticket 5053;
76 improves on 0.2.3.9-alpha.
77 - Update to the April 3 2012 Maxmind GeoLite Country database.
78 - Begin a doc/state-contents.txt file to explain the contents of
79 the Tor state file. Fixes bug 2987.
81 o Default torrc changes:
82 - Stop listing "socksport 9050" in torrc.sample. We open a socks
83 port on 9050 by default anyway, so this should not change anything
85 - Stop mentioning the deprecated *ListenAddress options in
86 torrc.sample. Fixes bug 5438.
87 - Document unit of bandwidth related options in sample torrc.
91 - The "torify" script no longer supports the "tsocks" socksifier
92 tool, since tsocks doesn't support DNS and UDP right for Tor.
93 Everyone should be using torsocks instead. Fixes bugs 3530 and
94 5180. Based on a patch by "ugh".
97 - Change the symmetric cipher interface so that creating and
98 initializing a stream cipher are no longer separate functions.
99 - Remove all internal support for unpadded RSA. We never used it, and
100 it would be a bad idea to start.
103 Changes in version 0.2.3.13-alpha - 2012-03-26
104 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
105 in managed pluggable transports, as well as providing other cleanups
106 that get us closer to a release candidate.
108 o Directory authority changes:
109 - Change IP address for maatuska (v3 directory authority).
112 - Provide controllers with a safer way to implement the cookie
113 authentication mechanism. With the old method, if another locally
114 running program could convince a controller that it was the Tor
115 process, then that program could trick the contoller into telling
116 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
117 authentication method uses a challenge-response approach to prevent
118 this attack. Fixes bug 5185, implements proposal 193.
119 - Never use a bridge or a controller-supplied node as an exit, even
120 if its exit policy allows it. Found by wanoskarnet. Fixes bug
121 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
122 and 0.2.0.3-alpha (for bridge-purpose descriptors).
123 - Only build circuits if we have a sufficient threshold of the total
124 descriptors that are marked in the consensus with the "Exit"
125 flag. This mitigates an attack proposed by wanoskarnet, in which
126 all of a client's bridges collude to restrict the exit nodes that
127 the client knows about. Fixes bug 5343.
129 o Major bugfixes (on Tor 0.2.3.x):
130 - Avoid an assert when managed proxies like obfsproxy are configured,
131 and we receive HUP signals or setconf attempts too rapidly. This
132 situation happens most commonly when Vidalia tries to attach to
133 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
134 bugfix on 0.2.3.6-alpha.
135 - Fix a relay-side pluggable transports bug where managed proxies were
136 unreachable from the Internet, because Tor asked them to bind on
137 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
138 - Stop discarding command-line arguments when TestingTorNetwork
139 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
140 0.2.3.9-alpha, where task 4552 added support for two layers of
142 - Resume allowing the unit tests to run in gdb. This was accidentally
143 made impossible when the DisableDebuggerAttachment option was
144 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
145 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
146 0.2.3.11-alpha. Reported by Anthony G. Basile.
148 o Minor bugfixes (on 0.2.2.x and earlier):
149 - Ensure we don't cannibalize circuits that are longer than three hops
150 already, so we don't end up making circuits with 5 or more
151 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
152 0.1.0.1-rc which introduced cannibalization.
153 - Detect and reject certain misformed escape sequences in
154 configuration values. Previously, these values would cause us
155 to crash if received in a torrc file or over an authenticated
156 control port. Bug found by Esteban Manchado Velázquez, and
157 independently by Robert Connolly from Matta Consulting who further
158 noted that it allows a post-authentication heap overflow. Patch
159 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
160 bugfix on 0.2.0.16-alpha.
161 - Fix a compile warning when using the --enable-openbsd-malloc
162 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
163 - Directory caches no longer refuse to clean out descriptors because
164 of missing v2 networkstatus documents, unless they're configured
165 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
166 0.2.2.26-beta. Patch by Daniel Bryg.
167 - Update to the latest version of the tinytest unit testing framework.
168 This includes a couple of bugfixes that can be relevant for
169 running forked unit tests on Windows, and removes all reserved
172 o Minor bugfixes (on 0.2.3.x):
173 - On a failed pipe() call, don't leak file descriptors. Fixes bug
174 4296; bugfix on 0.2.3.1-alpha.
175 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
176 until after we have received a CERTS cell. Fixes bug 4361; bugfix
177 on 0.2.3.6-alpha. Patch by "frosty".
178 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
179 option, so that the IP stack doesn't decide to use it for IPv4
180 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
181 - Ensure that variables set in Tor's environment cannot override
182 environment variables that Tor passes to a managed
183 pluggable-transport proxy. Previously, Tor would pass every
184 variable in its environment to managed proxies along with the new
185 ones, in such a way that on many operating systems, the inherited
186 environment variables would override those which Tor tried to
187 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
188 bugfix on 0.2.3.9-alpha for Windows.
191 - A wide variety of new unit tests by Esteban Manchado Velázquez.
192 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
193 - Update to the March 6 2012 Maxmind GeoLite Country database.
196 Changes in version 0.2.3.12-alpha - 2012-02-13
197 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
198 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
199 when Tor is configured to use a pluggable transport like obfsproxy.
202 - Fix builds when the path to sed, openssl, or sha1sum contains
203 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
205 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
206 connections. This change should allow busy exit relays to stop
207 running out of available sockets as quickly. Fixes bug 4950;
208 bugfix on 0.2.2.26-beta.
209 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
210 would ask the bridge for microdescriptors, which are only supported
211 in 0.2.3.x, and then fail to bootstrap when it didn't get the
212 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
213 - Properly set up obfsproxy's environment when in managed mode. The
214 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
215 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
216 5076 and 5082; bugfix on 0.2.3.6-alpha.
219 - Use the dead_strip option when building Tor on OS X. This reduces
220 binary size by almost 19% when linking openssl and libevent
221 statically, which we do for Tor Browser Bundle.
222 - Fix broken URLs in the sample torrc file, and tell readers about
223 the OutboundBindAddress, ExitPolicyRejectPrivate, and
224 PublishServerDescriptor options. Addresses bug 4652.
225 - Update to the February 7 2012 Maxmind GeoLite Country database.
228 - Downgrade the "We're missing a certificate" message from notice
229 to info: people kept mistaking it for a real problem, whereas it
230 is seldom the problem even when we are failing to bootstrap. Fixes
231 bug 5067; bugfix on 0.2.0.10-alpha.
232 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
233 managed pluggable transport server proxy's environment.
234 Previously, we would put it there, even though Tor doesn't
235 implement an 'extended server port' yet, and even though Tor
236 almost certainly isn't listening at that address. For now, we set
237 it to an empty string to avoid crashing older obfsproxies. Bugfix
239 - Log the heartbeat message every HeartbeatPeriod seconds, not every
240 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
241 0.2.3.1-alpha. Bug reported by Scott Bennett.
242 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
243 bugfix on 0.2.3.11-alpha.
244 - Update "ClientOnly" man page entry to explain that there isn't
245 really any point to messing with it. Resolves ticket 5005.
246 - Use the correct CVE number for CVE-2011-4576 in our comments and
247 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
250 o Code simplifications and refactoring:
251 - Use the _WIN32 macro throughout our code to detect Windows.
252 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
256 Changes in version 0.2.3.11-alpha - 2012-01-22
257 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
258 the last step of the plan to limit maximum circuit length, includes
259 a wide variety of hidden service performance and correctness fixes,
260 works around an OpenSSL security flaw if your distro is too stubborn
261 to upgrade, and fixes a bunch of smaller issues.
264 - Now that Tor 0.2.0.x is completely deprecated, enable the final
265 part of "Proposal 110: Avoiding infinite length circuits" by
266 refusing all circuit-extend requests that do not use a relay_early
267 cell. This change helps Tor resist a class of denial-of-service
268 attacks by limiting the maximum circuit length.
269 - Adjust the number of introduction points that a hidden service
270 will try to maintain based on how long its introduction points
271 remain in use and how many introductions they handle. Fixes
273 - Try to use system facilities for enumerating local interface
274 addresses, before falling back to our old approach (which was
275 binding a UDP socket, and calling getsockname() on it). That
276 approach was scaring OS X users whose draconian firewall
277 software warned about binding to UDP sockets, regardless of
278 whether packets were sent. Now we try to use getifaddrs(),
279 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
280 system supports. Resolves ticket 1827.
282 o Major security workaround:
283 - When building or running with any version of OpenSSL earlier
284 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
285 versions have a bug (CVE-2011-4576) in which their block cipher
286 padding includes uninitialized data, potentially leaking sensitive
287 information to any peer with whom they make a SSLv3 connection. Tor
288 does not use SSL v3 by default, but a hostile client or server
289 could force an SSLv3 connection in order to gain information that
290 they shouldn't have been able to get. The best solution here is to
291 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
292 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
293 to make sure that the bug can't happen.
296 - Fix the SOCKET_OK test that we use to tell when socket
297 creation fails so that it works on Win64. Fixes part of bug 4533;
298 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
299 - Correct our replacements for the timeradd() and timersub() functions
300 on platforms that lack them (for example, Windows). The timersub()
301 function is used when expiring circuits, while timeradd() is
302 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
303 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
304 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
305 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
306 bug at runtime, not compile time, because some distributions hack
307 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
308 on 0.2.3.9-alpha. Found by Pascal.
310 o Minor features (controller):
311 - Use absolute path names when reporting the torrc filename in the
312 control protocol, so a controller can more easily find the torrc
313 file. Resolves bug 1101.
314 - Extend the control protocol to report flags that control a circuit's
315 path selection in CIRC events and in replies to 'GETINFO
316 circuit-status'. Implements part of ticket 2411.
317 - Extend the control protocol to report the hidden service address
318 and current state of a hidden-service-related circuit in CIRC
319 events and in replies to 'GETINFO circuit-status'. Implements part
321 - When reporting the path to the cookie file to the controller,
322 give an absolute path. Resolves ticket 4881.
323 - Allow controllers to request an event notification whenever a
324 circuit is cannibalized or its purpose is changed. Implements
326 - Include the creation time of a circuit in CIRC and CIRC2
327 control-port events and the list produced by the 'GETINFO
328 circuit-status' control-port command.
330 o Minor features (directory authorities):
331 - Directory authorities now reject versions of Tor older than
332 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
333 inclusive. These versions accounted for only a small fraction of
334 the Tor network, and have numerous known security issues. Resolves
336 - Authority operators can now vote for all relays in a given
337 set of countries to be BadDir/BadExit/Invalid/Rejected.
338 - Provide two consensus parameters (FastFlagMinThreshold and
339 FastFlagMaxThreshold) to control the range of allowable bandwidths
340 for the Fast directory flag. These allow authorities to run
341 experiments on appropriate requirements for being a "Fast" node.
342 The AuthDirFastGuarantee config value still applies.
343 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
344 directory authority option (introduced in Tor 0.2.2.34).
346 o Minor features (other):
347 - Don't disable the DirPort when we cannot exceed our AccountingMax
348 limit during this interval because the effective bandwidthrate is
349 low enough. This is useful in a situation where AccountMax is only
350 used as an additional safeguard or to provide statistics.
351 - Prepend an informative header to generated dynamic_dh_params files.
352 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
353 EntryNodes will have no effect. Resolves issue 2571.
354 - Log more useful messages when we fail to disable debugger
356 - Log which authority we're missing votes from when we go to fetch
357 them from the other auths.
358 - Log (at debug level) whenever a circuit's purpose is changed.
359 - Add missing documentation for the MaxClientCircuitsPending,
360 UseMicrodescriptors, UserspaceIOCPBuffers, and
361 _UseFilteringSSLBufferevents options, all introduced during
363 - Update to the January 3 2012 Maxmind GeoLite Country database.
365 o Minor bugfixes (hidden services):
366 - Don't close hidden service client circuits which have almost
367 finished connecting to their destination when they reach
368 the normal circuit-build timeout. Previously, we would close
369 introduction circuits which are waiting for an acknowledgement
370 from the introduction point, and rendezvous circuits which have
371 been specified in an INTRODUCE1 cell sent to a hidden service,
372 after the normal CBT. Now, we mark them as 'timed out', and launch
373 another rendezvous attempt in parallel. This behavior change can
374 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
375 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
376 - Don't close hidden-service-side rendezvous circuits when they
377 reach the normal circuit-build timeout. This behaviour change can
378 be disabled using the new
379 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
380 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
381 - Make sure we never mark the wrong rendezvous circuit as having
382 had its introduction cell acknowleged by the introduction-point
383 relay. Previously, when we received an INTRODUCE_ACK cell on a
384 client-side hidden-service introduction circuit, we might have
385 marked a rendezvous circuit other than the one we specified in
386 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
387 a warning message and interfered with the hidden service
388 connection-establishment process. Fixes bug 4759; bugfix on
389 0.2.3.3-alpha, when we added the stream-isolation feature which
390 might cause Tor to open multiple rendezvous circuits for the same
392 - Don't trigger an assertion failure when we mark a new client-side
393 hidden-service introduction circuit for close during the process
394 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
397 o Minor bugfixes (log messages):
398 - Correctly spell "connect" in a log message on failure to create a
399 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
401 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
402 Fixes bug 4856; bugfix on Tor 0.0.6.
403 - Fix the log message describing how we work around discovering
404 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
405 4837; bugfix on 0.2.2.9-alpha.
406 - When logging about a disallowed .exit name, do not also call it
407 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
409 o Minor bugfixes (build fixes):
410 - During configure, detect when we're building with clang version
411 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
412 CFLAGS. clang doesn't support them yet.
413 - During configure, search for library containing cos function as
414 libm lives in libcore on some platforms (BeOS/Haiku). Linking
415 against libm was hard-coded before. Fixes the first part of bug
416 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
418 - Detect attempts to build Tor on (as yet hypothetical) versions
419 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
420 fix for bug 4533. Bugfix on 0.2.2.28-beta.
421 - Preprocessor directives should not be put inside the arguments
422 of a macro. This would break compilation with GCC releases prior
423 to version 3.3. We would never recommend such an old GCC version,
424 but it is apparently required for binary compatibility on some
425 platforms (namely, certain builds of Haiku). Fixes the other part
426 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
429 o Minor bugfixes (other):
430 - Older Linux kernels erroneously respond to strange nmap behavior
431 by having accept() return successfully with a zero-length
432 socket. When this happens, just close the connection. Previously,
433 we would try harder to learn the remote address: but there was
434 no such remote address to learn, and our method for trying to
435 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
436 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
437 - Fix null-pointer access that could occur if TLS allocation failed.
438 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
439 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
440 accidentally been reverted.
441 - Fix our implementation of crypto_random_hostname() so it can't
442 overflow on ridiculously large inputs. (No Tor version has ever
443 provided this kind of bad inputs, but let's be correct in depth.)
444 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
445 - Find more places in the code that should have been testing for
446 invalid sockets using the SOCKET_OK macro. Required for a fix
447 for bug 4533. Bugfix on 0.2.2.28-beta.
448 - Fix an assertion failure when, while running with bufferevents, a
449 connection finishes connecting after it is marked for close, but
450 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
451 - test_util_spawn_background_ok() hardcoded the expected value
452 for ENOENT to 2. This isn't portable as error numbers are
453 platform specific, and particularly the hurd has ENOENT at
454 0x40000002. Construct expected string at runtime, using the correct
455 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
456 - Reject attempts to disable DisableDebuggerAttachment while Tor is
457 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
458 - Use an appropriate-width type for sockets in tor-fw-helper on
459 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
462 - When sending or relaying a RELAY_EARLY cell, we used to convert
463 it to a RELAY cell if the connection was using the v1 link
464 protocol. This was a workaround for older versions of Tor, which
465 didn't handle RELAY_EARLY cells properly. Now that all supported
466 versions can handle RELAY_EARLY cells, and now that we're enforcing
467 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
468 remove this workaround. Addresses bug 4786.
470 o Code simplifications and refactoring:
471 - Use OpenSSL's built-in SSL_state_string_long() instead of our
472 own homebrewed ssl_state_to_string() replacement. Patch from
473 Emile Snyder. Fixes bug 4653.
474 - Use macros to indicate OpenSSL versions, so we don't need to worry
475 about accidental hexadecimal bit shifts.
476 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
478 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
479 - Use the smartlist_add_asprintf() alias more consistently.
480 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
481 invalid value, rather than just -1.
482 - Rename a handful of old identifiers, mostly related to crypto
483 structures and crypto functions. By convention, our "create an
484 object" functions are called "type_new()", our "free an object"
485 functions are called "type_free()", and our types indicate that
486 they are types only with a final "_t". But a handful of older
487 types and functions broke these rules, with function names like
488 "type_create" or "subsystem_op_type", or with type names like
492 Changes in version 0.2.3.10-alpha - 2011-12-16
493 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
494 Tor's buffers code. Absolutely everybody should upgrade.
496 The bug relied on an incorrect calculation when making data continuous
497 in one of our IO buffers, if the first chunk of the buffer was
498 misaligned by just the wrong amount. The miscalculation would allow an
499 attacker to overflow a piece of heap-allocated memory. To mount this
500 attack, the attacker would need to either open a SOCKS connection to
501 Tor's SocksPort (usually restricted to localhost), or target a Tor
502 instance configured to make its connections through a SOCKS proxy
503 (which Tor does not do by default).
505 Good security practice requires that all heap-overflow bugs should be
506 presumed to be exploitable until proven otherwise, so we are treating
507 this as a potential code execution attack. Please upgrade immediately!
508 This bug does not affect bufferevents-based builds of Tor. Special
509 thanks to "Vektor" for reporting this issue to us!
511 This release also contains a few minor bugfixes for issues discovered
515 - Fix a heap overflow bug that could occur when trying to pull
516 data into the first chunk of a buffer, when that chunk had
517 already had some data drained from it. Fixes CVE-2011-2778;
518 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
521 - If we can't attach streams to a rendezvous circuit when we
522 finish connecting to a hidden service, clear the rendezvous
523 circuit's stream-isolation state and try to attach streams
524 again. Previously, we cleared rendezvous circuits' isolation
525 state either too early (if they were freshly built) or not at all
526 (if they had been built earlier and were cannibalized). Bugfix on
527 0.2.3.3-alpha; fixes bug 4655.
528 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
529 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
530 - Fix an assertion failure when a relay with accounting enabled
531 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
534 - Update to the December 6 2011 Maxmind GeoLite Country database.
537 Changes in version 0.2.2.35 - 2011-12-16
538 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
539 buffers code. Absolutely everybody should upgrade.
541 The bug relied on an incorrect calculation when making data continuous
542 in one of our IO buffers, if the first chunk of the buffer was
543 misaligned by just the wrong amount. The miscalculation would allow an
544 attacker to overflow a piece of heap-allocated memory. To mount this
545 attack, the attacker would need to either open a SOCKS connection to
546 Tor's SocksPort (usually restricted to localhost), or target a Tor
547 instance configured to make its connections through a SOCKS proxy
548 (which Tor does not do by default).
550 Good security practice requires that all heap-overflow bugs should be
551 presumed to be exploitable until proven otherwise, so we are treating
552 this as a potential code execution attack. Please upgrade immediately!
553 This bug does not affect bufferevents-based builds of Tor. Special
554 thanks to "Vektor" for reporting this issue to us!
556 Tor 0.2.2.35 also fixes several bugs in previous versions, including
557 crash bugs for unusual configurations, and a long-term bug that
558 would prevent Tor from starting on Windows machines with draconian
561 With this release, we remind everyone that 0.2.0.x has reached its
562 formal end-of-life. Those Tor versions have many known flaws, and
563 nobody should be using them. You should upgrade -- ideally to the
564 0.2.2.x series. If you're using a Linux or BSD and its packages are
565 obsolete, stop using those packages and upgrade anyway.
567 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
568 longer receive support after some time in early 2012.
571 - Fix a heap overflow bug that could occur when trying to pull
572 data into the first chunk of a buffer, when that chunk had
573 already had some data drained from it. Fixes CVE-2011-2778;
574 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
575 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
576 that it doesn't attempt to allocate a socketpair. This could cause
577 some problems on Windows systems with overzealous firewalls. Fix for
578 bug 4457; workaround for Libevent versions 2.0.1-alpha through
580 - If we mark an OR connection for close based on a cell we process,
581 don't process any further cells on it. We already avoid further
582 reads on marked-for-close connections, but now we also discard the
583 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
584 which was the first version where we might mark a connection for
585 close based on processing a cell on it.
586 - Correctly sanity-check that we don't underflow on a memory
587 allocation (and then assert) for hidden service introduction
588 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
589 bugfix on 0.2.1.5-alpha.
590 - Fix a memory leak when we check whether a hidden service
591 descriptor has any usable introduction points left. Fixes bug
592 4424. Bugfix on 0.2.2.25-alpha.
593 - Don't crash when we're running as a relay and don't have a GeoIP
594 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
595 we've had in the 0.2.3.x branch already.
596 - When running as a client, do not print a misleading (and plain
597 wrong) log message that we're collecting "directory request"
598 statistics: clients don't collect statistics. Also don't create a
599 useless (because empty) stats file in the stats/ directory. Fixes
600 bug 4353; bugfix on 0.2.2.34.
603 - Detect failure to initialize Libevent. This fix provides better
604 detection for future instances of bug 4457.
605 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
606 function. This was eating up hideously large amounts of time on some
607 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
608 - Resolve an integer overflow bug in smartlist_ensure_capacity().
609 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
611 - Don't warn about unused log_mutex in log.c when building with
612 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
613 0.1.0.6-rc which introduced --disable-threads.
614 - When configuring, starting, or stopping an NT service, stop
615 immediately after the service configuration attempt has succeeded
616 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
617 - When sending a NETINFO cell, include the original address
618 received for the other side, not its canonical address. Found
619 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
620 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
621 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
622 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
623 occurred when a client tried to fetch a descriptor for a bridge
624 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
625 - Backport fixes for a pair of compilation warnings on Windows.
626 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
627 - If we had ever tried to call tor_addr_to_str on an address of
628 unknown type, we would have done a strdup on an uninitialized
629 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
630 Reported by "troll_un".
631 - Correctly detect and handle transient lookup failures from
632 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
633 Reported by "troll_un".
634 - Fix null-pointer access that could occur if TLS allocation failed.
635 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
636 - Use tor_socket_t type for listener argument to accept(). Fixes bug
637 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
640 - Add two new config options for directory authorities:
641 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
642 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
643 that is always sufficient to satisfy the bandwidth requirement for
644 the Guard flag. Now it will be easier for researchers to simulate
645 Tor networks with different values. Resolves ticket 4484.
646 - When Tor ignores a hidden service specified in its configuration,
647 include the hidden service's directory in the warning message.
648 Previously, we would only tell the user that some hidden service
649 was ignored. Bugfix on 0.0.6; fixes bug 4426.
650 - Update to the December 6 2011 Maxmind GeoLite Country database.
653 - Make it easier to automate expert package builds on Windows,
654 by removing an absolute path from makensis.exe command.
657 Changes in version 0.2.3.9-alpha - 2011-12-08
658 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
659 a "DisableNetwork" security feature that bundles can use to avoid
660 touching the network until bridges are configured, moves forward on
661 the pluggable transport design, fixes a flaw in the hidden service
662 design that unnecessarily prevented clients with wrong clocks from
663 reaching hidden services, and fixes a wide variety of other issues.
666 - Clients can now connect to private bridges over IPv6. Bridges
667 still need at least one IPv4 address in order to connect to
668 other relays. Note that we don't yet handle the case where the
669 user has two bridge lines for the same bridge (one IPv4, one
670 IPv6). Implements parts of proposal 186.
671 - New "DisableNetwork" config option to prevent Tor from launching any
672 connections or accepting any connections except on a control port.
673 Bundles and controllers can set this option before letting Tor talk
674 to the rest of the network, for example to prevent any connections
675 to a non-bridge address. Packages like Orbot can also use this
676 option to instruct Tor to save power when the network is off.
677 - Clients and bridges can now be configured to use a separate
678 "transport" proxy. This approach makes the censorship arms race
679 easier by allowing bridges to use protocol obfuscation plugins. It
680 implements the "managed proxy" part of proposal 180 (ticket 3472).
681 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
682 implementation. It makes AES_CTR about 7% faster than our old one
683 (which was about 10% faster than the one OpenSSL used to provide).
684 Resolves ticket 4526.
685 - Add a "tor2web mode" for clients that want to connect to hidden
686 services non-anonymously (and possibly more quickly). As a safety
687 measure to try to keep users from turning this on without knowing
688 what they are doing, tor2web mode must be explicitly enabled at
689 compile time, and a copy of Tor compiled to run in tor2web mode
690 cannot be used as a normal Tor client. Implements feature 2553.
691 - Add experimental support for running on Windows with IOCP and no
692 kernel-space socket buffers. This feature is controlled by a new
693 "UserspaceIOCPBuffers" config option (off by default), which has
694 no effect unless Tor has been built with support for bufferevents,
695 is running on Windows, and has enabled IOCP. This may, in the long
696 run, help solve or mitigate bug 98.
697 - Use a more secure consensus parameter voting algorithm. Now at
698 least three directory authorities or a majority of them must
699 vote on a given parameter before it will be included in the
700 consensus. Implements proposal 178.
703 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
704 They used to check that the timestamp was within 30 minutes
705 of their system clock, so they could cap the size of their
706 replay-detection cache, but that approach unnecessarily refused
707 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
708 the v3 intro-point protocol (the first one which sent a timestamp
709 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
710 - Only use the EVP interface when AES acceleration is enabled,
711 to avoid a 5-7% performance regression. Resolves issue 4525;
712 bugfix on 0.2.3.8-alpha.
714 o Privacy/anonymity features (bridge detection):
715 - Make bridge SSL certificates a bit more stealthy by using random
716 serial numbers, in the same fashion as OpenSSL when generating
717 self-signed certificates. Implements ticket 4584.
718 - Introduce a new config option "DynamicDHGroups", enabled by
719 default, which provides each bridge with a unique prime DH modulus
720 to be used during SSL handshakes. This option attempts to help
721 against censors who might use the Apache DH modulus as a static
722 identifier for bridges. Addresses ticket 4548.
724 o Minor features (new/different config options):
725 - New configuration option "DisableDebuggerAttachment" (on by default)
726 to prevent basic debugging attachment attempts by other processes.
727 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
728 - Allow MapAddress directives to specify matches against super-domains,
729 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
730 Implements issue 933.
731 - Slightly change behavior of "list" options (that is, config
732 options that can appear more than once) when they appear both in
733 torrc and on the command line. Previously, the command-line options
734 would be appended to the ones from torrc. Now, the command-line
735 options override the torrc options entirely. This new behavior
736 allows the user to override list options (like exit policies and
737 ports to listen on) from the command line, rather than simply
738 appending to the list.
739 - You can get the old (appending) command-line behavior for "list"
740 options by prefixing the option name with a "+".
741 - You can remove all the values for a "list" option from the command
742 line without adding any new ones by prefixing the option name
744 - Add experimental support for a "defaults" torrc file to be parsed
745 before the regular torrc. Torrc options override the defaults file's
746 options in the same way that the command line overrides the torrc.
747 The SAVECONF controller command saves only those options which
748 differ between the current configuration and the defaults file. HUP
749 reloads both files. (Note: This is an experimental feature; its
750 behavior will probably be refined in future 0.2.3.x-alpha versions
751 to better meet packagers' needs.) Implements task 4552.
754 - Try to make the introductory warning message that Tor prints on
755 startup more useful for actually finding help and information.
756 Resolves ticket 2474.
757 - Running "make version" now displays the version of Tor that
758 we're about to build. Idea from katmagic; resolves issue 4400.
759 - Expire old or over-used hidden service introduction points.
760 Required by fix for bug 3460.
761 - Move the replay-detection cache for the RSA-encrypted parts of
762 INTRODUCE2 cells to the introduction point data structures.
763 Previously, we would use one replay-detection cache per hidden
764 service. Required by fix for bug 3460.
765 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
766 public key replay-detection cache from 60 minutes to 5 minutes. This
767 replay-detection cache is now used only to detect multiple
768 INTRODUCE2 cells specifying the same rendezvous point, so we can
769 avoid launching multiple simultaneous attempts to connect to it.
771 o Minor bugfixes (on Tor 0.2.2.x and earlier):
772 - Resolve an integer overflow bug in smartlist_ensure_capacity().
773 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
775 - Fix a minor formatting issue in one of tor-gencert's error messages.
777 - Prevent a false positive from the check-spaces script, by disabling
778 the "whitespace between function name and (" check for functions
780 - Fix a log message suggesting that people contact a non-existent
781 email address. Fixes bug 3448.
782 - Fix null-pointer access that could occur if TLS allocation failed.
783 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
784 - Report a real bootstrap problem to the controller on router
785 identity mismatch. Previously we just said "foo", which probably
786 made a lot of sense at the time. Fixes bug 4169; bugfix on
788 - If we had ever tried to call tor_addr_to_str() on an address of
789 unknown type, we would have done a strdup() on an uninitialized
790 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
791 Reported by "troll_un".
792 - Correctly detect and handle transient lookup failures from
793 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
794 Reported by "troll_un".
795 - Use tor_socket_t type for listener argument to accept(). Fixes bug
796 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
797 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
798 bug 4532; found by "troll_un".
800 o Minor bugfixes (on Tor 0.2.3.x):
801 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
803 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
804 circuit for use as a hidden service client's rendezvous point.
805 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
806 with help from wanoskarnet.
807 - Restore behavior of overriding SocksPort, ORPort, and similar
808 options from the command line. Bugfix on 0.2.3.3-alpha.
811 - Properly handle the case where the build-tree is not the same
812 as the source tree when generating src/common/common_sha1.i,
813 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
814 bugfix on 0.2.0.1-alpha.
816 o Code simplifications, cleanups, and refactorings:
817 - Remove the pure attribute from all functions that used it
818 previously. In many cases we assigned it incorrectly, because the
819 functions might assert or call impure functions, and we don't have
820 evidence that keeping the pure attribute is worthwhile. Implements
821 changes suggested in ticket 4421.
822 - Remove some dead code spotted by coverity. Fixes cid 432.
823 Bugfix on 0.2.3.1-alpha, closes bug 4637.
826 Changes in version 0.2.3.8-alpha - 2011-11-22
827 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
828 socketpair-related bug that has been bothering Windows users. It adds
829 support to serve microdescriptors to controllers, so Vidalia's network
830 map can resume listing relays (once Vidalia implements its side),
831 and adds better support for hardware AES acceleration. Finally, it
832 starts the process of adjusting the bandwidth cutoff for getting the
833 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
834 that tiny relays harm performance more than they help network capacity.
837 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
838 that it doesn't attempt to allocate a socketpair. This could cause
839 some problems on Windows systems with overzealous firewalls. Fix for
840 bug 4457; workaround for Libevent versions 2.0.1-alpha through
842 - Correctly sanity-check that we don't underflow on a memory
843 allocation (and then assert) for hidden service introduction
844 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
845 bugfix on 0.2.1.5-alpha.
846 - Remove the artificially low cutoff of 20KB to guarantee the Fast
847 flag. In the past few years the average relay speed has picked
848 up, and while the "top 7/8 of the network get the Fast flag" and
849 "all relays with 20KB or more of capacity get the Fast flag" rules
850 used to have the same result, now the top 7/8 of the network has
851 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
852 - Fix a rare assertion failure when checking whether a v0 hidden
853 service descriptor has any usable introduction points left, and
854 we don't have enough information to build a circuit to the first
855 intro point named in the descriptor. The HS client code in
856 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
857 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
858 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
859 - Make bridge authorities not crash when they are asked for their own
860 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
861 - When running as a client, do not print a misleading (and plain
862 wrong) log message that we're collecting "directory request"
863 statistics: clients don't collect statistics. Also don't create a
864 useless (because empty) stats file in the stats/ directory. Fixes
865 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
868 - Allow Tor controllers like Vidalia to obtain the microdescriptor
869 for a relay by identity digest or nickname. Previously,
870 microdescriptors were only available by their own digests, so a
871 controller would have to ask for and parse the whole microdescriptor
872 consensus in order to look up a single relay's microdesc. Fixes
873 bug 3832; bugfix on 0.2.3.1-alpha.
874 - Use OpenSSL's EVP interface for AES encryption, so that all AES
875 operations can use hardware acceleration (if present). Resolves
878 o Minor bugfixes (on 0.2.2.x and earlier):
879 - Detect failure to initialize Libevent. This fix provides better
880 detection for future instances of bug 4457.
881 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
882 function. This was eating up hideously large amounts of time on some
883 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
884 - Don't warn about unused log_mutex in log.c when building with
885 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
886 0.1.0.6-rc which introduced --disable-threads.
887 - Allow manual 'authenticate' commands to the controller interface
888 from netcat (nc) as well as telnet. We were rejecting them because
889 they didn't come with the expected whitespace at the end of the
890 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
891 - Fix some (not actually triggerable) buffer size checks in usage of
892 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
894 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
895 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
896 - When configuring, starting, or stopping an NT service, stop
897 immediately after the service configuration attempt has succeeded
898 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
899 - When sending a NETINFO cell, include the original address
900 received for the other side, not its canonical address. Found
901 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
902 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
903 can pick them up when the tests aren't disabled. Bugfix on
904 0.2.2.4-alpha which introduced tinytest.
905 - Fix a memory leak when we check whether a hidden service
906 descriptor has any usable introduction points left. Fixes bug
907 4424. Bugfix on 0.2.2.25-alpha.
908 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
909 occurred when a client tried to fetch a descriptor for a bridge
910 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
912 o Minor bugfixes (on 0.2.3.x):
913 - Make util unit tests build correctly with MSVC. Bugfix on
914 0.2.3.3-alpha. Patch by Gisle Vanem.
915 - Successfully detect AUTH_CHALLENGE cells with no recognized
916 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
918 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
919 it should still send a NETINFO cell to allow the connection to
920 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
922 - Log less loudly when we get an invalid authentication certificate
923 from a source other than a directory authority: it's not unusual
924 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
926 - Tolerate servers with more clock skew in their authentication
927 certificates than previously. Fixes bug 4371; bugfix on
929 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
930 on 0.2.3.4-alpha and 0.2.3.6-alpha.
933 - Add two new config options for directory authorities:
934 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
935 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
936 that is always sufficient to satisfy the bandwidth requirement for
937 the Guard flag. Now it will be easier for researchers to simulate
938 Tor networks with different values. Resolves ticket 4484.
939 - When Tor ignores a hidden service specified in its configuration,
940 include the hidden service's directory in the warning message.
941 Previously, we would only tell the user that some hidden service
942 was ignored. Bugfix on 0.0.6; fixes bug 4426.
943 - When we fail to initialize Libevent, retry with IOCP disabled so we
944 don't need to turn on multi-threading support in Libevent, which in
945 turn requires a working socketpair(). This is a workaround for bug
946 4457, which affects Libevent versions from 2.0.1-alpha through
948 - Detect when we try to build on a platform that doesn't define
949 AF_UNSPEC to 0. We don't work there, so refuse to compile.
950 - Update to the November 1 2011 Maxmind GeoLite Country database.
953 - Make it easier to automate expert package builds on Windows,
954 by removing an absolute path from makensis.exe command.
956 o Code simplifications and refactoring:
957 - Remove some redundant #include directives throughout the code.
958 Patch from Andrea Gelmini.
959 - Unconditionally use OpenSSL's AES implementation instead of our
960 old built-in one. OpenSSL's AES has been better for a while, and
961 relatively few servers should still be on any version of OpenSSL
962 that doesn't have good optimized assembly AES.
963 - Use the name "CERTS" consistently to refer to the new cell type;
964 we were calling it CERT in some places and CERTS in others.
967 - Numerous new unit tests for functions in util.c and address.c by
969 - The long-disabled benchmark tests are now split into their own
970 ./src/test/bench binary.
971 - The benchmark tests can now use more accurate timers than
972 gettimeofday() when such timers are available.
975 Changes in version 0.2.3.7-alpha - 2011-10-30
976 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
977 the new v3 handshake. It also resolves yet another bridge address
981 - If we mark an OR connection for close based on a cell we process,
982 don't process any further cells on it. We already avoid further
983 reads on marked-for-close connections, but now we also discard the
984 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
985 which was the first version where we might mark a connection for
986 close based on processing a cell on it.
987 - Fix a double-free bug that would occur when we received an invalid
988 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
989 bugfix on 0.2.3.6-alpha.
990 - Bridges no longer include their address in NETINFO cells on outgoing
991 OR connections, to allow them to blend in better with clients.
992 Removes another avenue for enumerating bridges. Reported by
993 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
994 cells were introduced.
997 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
998 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1001 Changes in version 0.2.3.6-alpha - 2011-10-26
1002 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
1003 anonymity vulnerability where an attacker can deanonymize Tor
1004 users. Everybody should upgrade.
1006 This release also features support for a new v3 connection handshake
1007 protocol, and fixes to make hidden service connections more robust.
1010 - Implement a new handshake protocol (v3) for authenticating Tors to
1011 each other over TLS. It should be more resistant to fingerprinting
1012 than previous protocols, and should require less TLS hacking for
1013 future Tor implementations. Implements proposal 176.
1014 - Allow variable-length padding cells to disguise the length of
1015 Tor's TLS records. Implements part of proposal 184.
1017 o Privacy/anonymity fixes (clients):
1018 - Clients and bridges no longer send TLS certificate chains on
1019 outgoing OR connections. Previously, each client or bridge would
1020 use the same cert chain for all outgoing OR connections until
1021 its IP address changes, which allowed any relay that the client
1022 or bridge contacted to determine which entry guards it is using.
1023 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1024 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1025 no longer considers that connection as suitable for satisfying a
1026 circuit EXTEND request. Now relays can protect clients from the
1027 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1028 - Directory authorities no longer assign the Guard flag to relays
1029 that haven't upgraded to the above "refuse EXTEND requests
1030 to client connections" fix. Now directory authorities can
1031 protect clients from the CVE-2011-2768 issue even if neither
1032 the clients nor the relays have upgraded yet. There's a new
1033 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
1034 to let us transition smoothly, else tomorrow there would be no
1037 o Major bugfixes (hidden services):
1038 - Improve hidden service robustness: when an attempt to connect to
1039 a hidden service ends, be willing to refetch its hidden service
1040 descriptors from each of the HSDir relays responsible for them
1041 immediately. Previously, we would not consider refetching the
1042 service's descriptors from each HSDir for 15 minutes after the last
1043 fetch, which was inconvenient if the hidden service was not running
1044 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
1045 - When one of a hidden service's introduction points appears to be
1046 unreachable, stop trying it. Previously, we would keep trying
1047 to build circuits to the introduction point until we lost the
1048 descriptor, usually because the user gave up and restarted Tor.
1049 Partly fixes bug 3825.
1050 - Don't launch a useless circuit after failing to use one of a
1051 hidden service's introduction points. Previously, we would
1052 launch a new introduction circuit, but not set the hidden service
1053 which that circuit was intended to connect to, so it would never
1054 actually be used. A different piece of code would then create a
1055 new introduction circuit correctly. Bug reported by katmagic and
1056 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
1058 o Major bugfixes (other):
1059 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1060 that they initiated. Relays could distinguish incoming bridge
1061 connections from client connections, creating another avenue for
1062 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1063 Found by "frosty_un".
1064 - Don't update the AccountingSoftLimitHitAt state file entry whenever
1065 tor gets started. This prevents a wrong average bandwidth
1066 estimate, which would cause relays to always start a new accounting
1067 interval at the earliest possible moment. Fixes bug 2003; bugfix
1068 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
1069 immensely in tracking this bug down.
1070 - Fix a crash bug when changing node restrictions while a DNS lookup
1071 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
1074 o Minor bugfixes (on 0.2.2.x and earlier):
1075 - When a hidden service turns an extra service-side introduction
1076 circuit into a general-purpose circuit, free the rend_data and
1077 intro_key fields first, so we won't leak memory if the circuit
1078 is cannibalized for use as another service-side introduction
1079 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
1080 - Rephrase the log message emitted if the TestSocks check is
1081 successful. Patch from Fabian Keil; fixes bug 4094.
1082 - Bridges now skip DNS self-tests, to act a little more stealthily.
1083 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
1084 bridges. Patch by "warms0x".
1085 - Remove a confusing dollar sign from the example fingerprint in the
1086 man page, and also make the example fingerprint a valid one. Fixes
1087 bug 4309; bugfix on 0.2.1.3-alpha.
1088 - Fix internal bug-checking logic that was supposed to catch
1089 failures in digest generation so that it will fail more robustly
1090 if we ask for a nonexistent algorithm. Found by Coverity Scan.
1091 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
1092 - Report any failure in init_keys() calls launched because our
1093 IP address has changed. Spotted by Coverity Scan. Bugfix on
1094 0.1.1.4-alpha; fixes CID 484.
1096 o Minor bugfixes (on 0.2.3.x):
1097 - Fix a bug in configure.in that kept it from building a configure
1098 script with autoconf versions earlier than 2.61. Fixes bug 2430;
1099 bugfix on 0.2.3.1-alpha.
1100 - Don't warn users that they are exposing a client port to the
1101 Internet if they have specified an RFC1918 address. Previously,
1102 we would warn if the user had specified any non-loopback
1103 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
1104 - Fix memory leaks in the failing cases of the new SocksPort and
1105 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
1106 fixes coverity CIDs 485, 486, and 487.
1109 - When a hidden service's introduction point times out, consider
1110 trying it again during the next attempt to connect to the
1111 HS. Previously, we would not try it again unless a newly fetched
1112 descriptor contained it. Required by fixes for bugs 1297 and 3825.
1113 - The next version of Windows will be called Windows 8, and it has
1114 a major version of 6, minor version of 2. Correctly identify that
1115 version instead of calling it "Very recent version". Resolves
1116 ticket 4153; reported by funkstar.
1117 - The Bridge Authority now writes statistics on how many bridge
1118 descriptors it gave out in total, and how many unique descriptors
1119 it gave out. It also lists how often the most and least commonly
1120 fetched descriptors were given out, as well as the median and
1121 25th/75th percentile. Implements tickets 4200 and 4294.
1122 - Update to the October 4 2011 Maxmind GeoLite Country database.
1124 o Code simplifications and refactoring:
1125 - Remove some old code to remember statistics about which descriptors
1126 we've served as a directory mirror. The feature wasn't used and
1127 is outdated now that microdescriptors are around.
1128 - Rename Tor functions that turn strings into addresses, so that
1129 "parse" indicates that no hostname resolution occurs, and
1130 "lookup" indicates that hostname resolution may occur. This
1131 should help prevent mistakes in the future. Fixes bug 3512.
1134 Changes in version 0.2.2.34 - 2011-10-26
1135 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
1136 can deanonymize Tor users. Everybody should upgrade.
1138 The attack relies on four components: 1) Clients reuse their TLS cert
1139 when talking to different relays, so relays can recognize a user by
1140 the identity key in her cert. 2) An attacker who knows the client's
1141 identity key can probe each guard relay to see if that identity key
1142 is connected to that guard relay right now. 3) A variety of active
1143 attacks in the literature (starting from "Low-Cost Traffic Analysis
1144 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
1145 discover the guard relays that a Tor user visiting the website is using.
1146 4) Clients typically pick three guards at random, so the set of guards
1147 for a given user could well be a unique fingerprint for her. This
1148 release fixes components #1 and #2, which is enough to block the attack;
1149 the other two remain as open research problems. Special thanks to
1150 "frosty_un" for reporting the issue to us!
1152 Clients should upgrade so they are no longer recognizable by the TLS
1153 certs they present. Relays should upgrade so they no longer allow a
1154 remote attacker to probe them to test whether unpatched clients are
1155 currently connected to them.
1157 This release also fixes several vulnerabilities that allow an attacker
1158 to enumerate bridge relays. Some bridge enumeration attacks still
1159 remain; see for example proposal 188.
1161 o Privacy/anonymity fixes (clients):
1162 - Clients and bridges no longer send TLS certificate chains on
1163 outgoing OR connections. Previously, each client or bridge would
1164 use the same cert chain for all outgoing OR connections until
1165 its IP address changes, which allowed any relay that the client
1166 or bridge contacted to determine which entry guards it is using.
1167 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1168 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1169 no longer considers that connection as suitable for satisfying a
1170 circuit EXTEND request. Now relays can protect clients from the
1171 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1172 - Directory authorities no longer assign the Guard flag to relays
1173 that haven't upgraded to the above "refuse EXTEND requests
1174 to client connections" fix. Now directory authorities can
1175 protect clients from the CVE-2011-2768 issue even if neither
1176 the clients nor the relays have upgraded yet. There's a new
1177 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
1178 to let us transition smoothly, else tomorrow there would be no
1181 o Privacy/anonymity fixes (bridge enumeration):
1182 - Bridge relays now do their directory fetches inside Tor TLS
1183 connections, like all the other clients do, rather than connecting
1184 directly to the DirPort like public relays do. Removes another
1185 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
1186 - Bridges relays now build circuits for themselves in a more similar
1187 way to how clients build them. Removes another avenue for
1188 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
1189 when bridges were introduced.
1190 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1191 that they initiated. Relays could distinguish incoming bridge
1192 connections from client connections, creating another avenue for
1193 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1194 Found by "frosty_un".
1197 - Fix a crash bug when changing node restrictions while a DNS lookup
1198 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
1200 - Don't launch a useless circuit after failing to use one of a
1201 hidden service's introduction points. Previously, we would
1202 launch a new introduction circuit, but not set the hidden service
1203 which that circuit was intended to connect to, so it would never
1204 actually be used. A different piece of code would then create a
1205 new introduction circuit correctly. Bug reported by katmagic and
1206 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
1209 - Change an integer overflow check in the OpenBSD_Malloc code so
1210 that GCC is less likely to eliminate it as impossible. Patch
1211 from Mansour Moufid. Fixes bug 4059.
1212 - When a hidden service turns an extra service-side introduction
1213 circuit into a general-purpose circuit, free the rend_data and
1214 intro_key fields first, so we won't leak memory if the circuit
1215 is cannibalized for use as another service-side introduction
1216 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
1217 - Bridges now skip DNS self-tests, to act a little more stealthily.
1218 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
1219 bridges. Patch by "warms0x".
1220 - Fix internal bug-checking logic that was supposed to catch
1221 failures in digest generation so that it will fail more robustly
1222 if we ask for a nonexistent algorithm. Found by Coverity Scan.
1223 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
1224 - Report any failure in init_keys() calls launched because our
1225 IP address has changed. Spotted by Coverity Scan. Bugfix on
1226 0.1.1.4-alpha; fixes CID 484.
1228 o Minor bugfixes (log messages and documentation):
1229 - Remove a confusing dollar sign from the example fingerprint in the
1230 man page, and also make the example fingerprint a valid one. Fixes
1231 bug 4309; bugfix on 0.2.1.3-alpha.
1232 - The next version of Windows will be called Windows 8, and it has
1233 a major version of 6, minor version of 2. Correctly identify that
1234 version instead of calling it "Very recent version". Resolves
1235 ticket 4153; reported by funkstar.
1236 - Downgrade log messages about circuit timeout calibration from
1237 "notice" to "info": they don't require or suggest any human
1238 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
1239 bugfix on 0.2.2.14-alpha.
1242 - Turn on directory request statistics by default and include them in
1243 extra-info descriptors. Don't break if we have no GeoIP database.
1244 Backported from 0.2.3.1-alpha; implements ticket 3951.
1245 - Update to the October 4 2011 Maxmind GeoLite Country database.
1248 Changes in version 0.2.1.31 - 2011-10-26
1249 Tor 0.2.1.31 backports important security and privacy fixes for
1250 oldstable. This release is intended only for package maintainers and
1251 others who cannot use the 0.2.2 stable series. All others should be
1252 using Tor 0.2.2.x or newer.
1254 o Security fixes (also included in 0.2.2.x):
1255 - Replace all potentially sensitive memory comparison operations
1256 with versions whose runtime does not depend on the data being
1257 compared. This will help resist a class of attacks where an
1258 adversary can use variations in timing information to learn
1259 sensitive data. Fix for one case of bug 3122. (Safe memcmp
1260 implementation by Robert Ransom based partially on code by DJB.)
1261 - Fix an assert in parsing router descriptors containing IPv6
1262 addresses. This one took down the directory authorities when
1263 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
1265 o Privacy/anonymity fixes (also included in 0.2.2.x):
1266 - Clients and bridges no longer send TLS certificate chains on
1267 outgoing OR connections. Previously, each client or bridge would
1268 use the same cert chain for all outgoing OR connections until
1269 its IP address changes, which allowed any relay that the client
1270 or bridge contacted to determine which entry guards it is using.
1271 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1272 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1273 no longer considers that connection as suitable for satisfying a
1274 circuit EXTEND request. Now relays can protect clients from the
1275 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1276 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1277 that they initiated. Relays could distinguish incoming bridge
1278 connections from client connections, creating another avenue for
1279 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1280 Found by "frosty_un".
1281 - When receiving a hidden service descriptor, check that it is for
1282 the hidden service we wanted. Previously, Tor would store any
1283 hidden service descriptors that a directory gave it, whether it
1284 wanted them or not. This wouldn't have let an attacker impersonate
1285 a hidden service, but it did let directories pre-seed a client
1286 with descriptors that it didn't want. Bugfix on 0.0.6.
1287 - Avoid linkability based on cached hidden service descriptors: forget
1288 all hidden service descriptors cached as a client when processing a
1289 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
1290 - Make the bridge directory authority refuse to answer directory
1291 requests for "all" descriptors. It used to include bridge
1292 descriptors in its answer, which was a major information leak.
1293 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
1294 - Don't attach new streams to old rendezvous circuits after SIGNAL
1295 NEWNYM. Previously, we would keep using an existing rendezvous
1296 circuit if it remained open (i.e. if it were kept open by a
1297 long-lived stream, or if a new stream were attached to it before
1298 Tor could notice that it was old and no longer in use). Bugfix on
1299 0.1.1.15-rc; fixes bug 3375.
1301 o Minor bugfixes (also included in 0.2.2.x):
1302 - When we restart our relay, we might get a successful connection
1303 from the outside before we've started our reachability tests,
1304 triggering a warning: "ORPort found reachable, but I have no
1305 routerinfo yet. Failing to inform controller of success." This
1306 bug was harmless unless Tor is running under a controller
1307 like Vidalia, in which case the controller would never get a
1308 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
1310 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
1311 enabled. Fixes bug 1526.
1312 - Remove undocumented option "-F" from tor-resolve: it hasn't done
1313 anything since 0.2.1.16-rc.
1314 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
1315 None of the cases where we did this before were wrong, but by making
1316 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
1317 - Fix a rare crash bug that could occur when a client was configured
1318 with a large number of bridges. Fixes bug 2629; bugfix on
1319 0.2.1.2-alpha. Bugfix by trac user "shitlei".
1320 - Correct the warning displayed when a rendezvous descriptor exceeds
1321 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
1323 - Fix an uncommon assertion failure when running with DNSPort under
1324 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
1325 - When warning about missing zlib development packages during compile,
1326 give the correct package names. Bugfix on 0.2.0.1-alpha.
1327 - Require that introduction point keys and onion keys have public
1328 exponent 65537. Bugfix on 0.2.0.10-alpha.
1329 - Do not crash when our configuration file becomes unreadable, for
1330 example due to a permissions change, between when we start up
1331 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
1333 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
1335 - Always NUL-terminate the sun_path field of a sockaddr_un before
1336 passing it to the kernel. (Not a security issue: kernels are
1337 smart enough to reject bad sockaddr_uns.) Found by Coverity;
1338 CID #428. Bugfix on Tor 0.2.0.3-alpha.
1339 - Don't stack-allocate the list of supplementary GIDs when we're
1340 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
1341 could take up to 256K, which is way too much stack. Found by
1342 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
1344 o Minor bugfixes (only in 0.2.1.x):
1345 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
1346 rely on them. Bugfix on 0.2.1.30.
1347 - Use git revisions instead of svn revisions when generating our
1348 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
1350 o Minor features (also included in 0.2.2.x):
1351 - Adjust the expiration time on our SSL session certificates to
1352 better match SSL certs seen in the wild. Resolves ticket 4014.
1353 - Allow nameservers with IPv6 address. Resolves bug 2574.
1354 - Update to the October 4 2011 Maxmind GeoLite Country database.
1357 Changes in version 0.2.3.5-alpha - 2011-09-28
1358 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
1359 bridge relays; fixes an assertion error that many users started hitting
1360 today; and adds the ability to refill token buckets more often than
1361 once per second, allowing significant performance improvements.
1364 - Bridge relays now do their directory fetches inside Tor TLS
1365 connections, like all the other clients do, rather than connecting
1366 directly to the DirPort like public relays do. Removes another
1367 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
1368 - Bridges relays now build circuits for themselves in a more similar
1369 way to how clients build them. Removes another avenue for
1370 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
1371 when bridges were introduced.
1374 - Fix an "Assertion md->held_by_node == 1 failed" error that could
1375 occur when the same microdescriptor was referenced by two node_t
1376 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
1378 o Major features (networking):
1379 - Add a new TokenBucketRefillInterval option to refill token buckets
1380 more frequently than once per second. This should improve network
1381 performance, alleviate queueing problems, and make traffic less
1382 bursty. Implements proposal 183; closes ticket 3630. Design by
1383 Florian Tschorsch and Björn Scheuermann; implementation by
1387 - Change an integer overflow check in the OpenBSD_Malloc code so
1388 that GCC is less likely to eliminate it as impossible. Patch
1389 from Mansour Moufid. Fixes bug 4059.
1391 o Minor bugfixes (usability):
1392 - Downgrade log messages about circuit timeout calibration from
1393 "notice" to "info": they don't require or suggest any human
1394 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
1395 bugfix on 0.2.2.14-alpha.
1397 o Minor features (diagnostics):
1398 - When the system call to create a listener socket fails, log the
1399 error message explaining why. This may help diagnose bug 4027.
1402 Changes in version 0.2.3.4-alpha - 2011-09-13
1403 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
1404 tweak to Tor's TLS handshake that makes relays and bridges that run
1405 this new version reachable from Iran again. It also fixes a few new
1406 bugs in 0.2.3.x, and teaches relays to recognize when they're not
1407 listed in the network consensus and republish.
1409 o Major bugfixes (also part of 0.2.2.33):
1410 - Avoid an assertion failure when reloading a configuration with
1411 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
1412 3923; bugfix on 0.2.2.25-alpha.
1414 o Minor features (security, also part of 0.2.2.33):
1415 - Check for replays of the public-key encrypted portion of an
1416 INTRODUCE1 cell, in addition to the current check for replays of
1417 the g^x value. This prevents a possible class of active attacks
1418 by an attacker who controls both an introduction point and a
1419 rendezvous point, and who uses the malleability of AES-CTR to
1420 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
1421 that these attacks is infeasible (requiring the attacker to send
1422 on the order of zettabytes of altered cells in a short interval),
1423 but we'd rather block them off in case there are any classes of
1424 this attack that we missed. Reported by Willem Pinckaers.
1426 o Minor features (also part of 0.2.2.33):
1427 - Adjust the expiration time on our SSL session certificates to
1428 better match SSL certs seen in the wild. Resolves ticket 4014.
1429 - Change the default required uptime for a relay to be accepted as
1430 a HSDir (hidden service directory) from 24 hours to 25 hours.
1431 Improves on 0.2.0.10-alpha; resolves ticket 2649.
1432 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
1433 authorities to abstain from voting on assignment of the HSDir
1434 consensus flag. Related to bug 2649.
1435 - Update to the September 6 2011 Maxmind GeoLite Country database.
1437 o Minor bugfixes (also part of 0.2.2.33):
1438 - Demote the 'replay detected' log message emitted when a hidden
1439 service receives the same Diffie-Hellman public key in two different
1440 INTRODUCE2 cells to info level. A normal Tor client can cause that
1441 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
1442 fixes part of bug 2442.
1443 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
1444 level. There is nothing that a hidden service's operator can do
1445 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
1447 - Clarify a log message specifying the characters permitted in
1448 HiddenServiceAuthorizeClient client names. Previously, the log
1449 message said that "[A-Za-z0-9+-_]" were permitted; that could have
1450 given the impression that every ASCII character between "+" and "_"
1451 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
1453 o Build fixes (also part of 0.2.2.33):
1454 - Clean up some code issues that prevented Tor from building on older
1455 BSDs. Fixes bug 3894; reported by "grarpamp".
1456 - Search for a platform-specific version of "ar" when cross-compiling.
1457 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
1460 - Fix a bug where the SocksPort option (for example) would get
1461 ignored and replaced by the default if a SocksListenAddress
1462 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
1466 - Relays now try regenerating and uploading their descriptor more
1467 frequently if they are not listed in the consensus, or if the
1468 version of their descriptor listed in the consensus is too
1469 old. This fix should prevent situations where a server declines
1470 to re-publish itself because it has done so too recently, even
1471 though the authorities decided not to list its recent-enough
1472 descriptor. Fix for bug 3327.
1475 - Relays now include a reason for regenerating their descriptors
1476 in an HTTP header when uploading to the authorities. This will
1477 make it easier to debug descriptor-upload issues in the future.
1478 - When starting as root and then changing our UID via the User
1479 control option, and we have a ControlSocket configured, make sure
1480 that the ControlSocket is owned by the same account that Tor will
1481 run under. Implements ticket 3421; fix by Jérémy Bobbio.
1484 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
1485 utility function used in the control-port code). This shouldn't
1486 ever happen unless Tor is completely out of memory, but if it did
1487 happen and Tor somehow recovered from it, Tor could have sent a log
1488 message to a control port in the middle of a reply to a controller
1489 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
1490 - Make 'FetchUselessDescriptors' cause all descriptor types and
1491 all consensus types (including microdescriptors) to get fetched.
1492 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
1495 - Make a new "entry connection" struct as an internal subtype of "edge
1496 connection", to simplify the code and make exit connections smaller.
1499 Changes in version 0.2.2.33 - 2011-09-13
1500 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
1501 TLS handshake that makes relays and bridges that run this new version
1502 reachable from Iran again.
1505 - Avoid an assertion failure when reloading a configuration with
1506 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
1507 3923; bugfix on 0.2.2.25-alpha.
1509 o Minor features (security):
1510 - Check for replays of the public-key encrypted portion of an
1511 INTRODUCE1 cell, in addition to the current check for replays of
1512 the g^x value. This prevents a possible class of active attacks
1513 by an attacker who controls both an introduction point and a
1514 rendezvous point, and who uses the malleability of AES-CTR to
1515 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
1516 that these attacks are infeasible (requiring the attacker to send
1517 on the order of zettabytes of altered cells in a short interval),
1518 but we'd rather block them off in case there are any classes of
1519 this attack that we missed. Reported by Willem Pinckaers.
1522 - Adjust the expiration time on our SSL session certificates to
1523 better match SSL certs seen in the wild. Resolves ticket 4014.
1524 - Change the default required uptime for a relay to be accepted as
1525 a HSDir (hidden service directory) from 24 hours to 25 hours.
1526 Improves on 0.2.0.10-alpha; resolves ticket 2649.
1527 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
1528 authorities to abstain from voting on assignment of the HSDir
1529 consensus flag. Related to bug 2649.
1530 - Update to the September 6 2011 Maxmind GeoLite Country database.
1532 o Minor bugfixes (documentation and log messages):
1533 - Correct the man page to explain that HashedControlPassword and
1534 CookieAuthentication can both be set, in which case either method
1535 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
1536 when we decided to allow these config options to both be set. Issue
1538 - Demote the 'replay detected' log message emitted when a hidden
1539 service receives the same Diffie-Hellman public key in two different
1540 INTRODUCE2 cells to info level. A normal Tor client can cause that
1541 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
1542 fixes part of bug 2442.
1543 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
1544 level. There is nothing that a hidden service's operator can do
1545 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
1547 - Clarify a log message specifying the characters permitted in
1548 HiddenServiceAuthorizeClient client names. Previously, the log
1549 message said that "[A-Za-z0-9+-_]" were permitted; that could have
1550 given the impression that every ASCII character between "+" and "_"
1551 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
1554 - Provide a substitute implementation of lround() for MSVC, which
1555 apparently lacks it. Patch from Gisle Vanem.
1556 - Clean up some code issues that prevented Tor from building on older
1557 BSDs. Fixes bug 3894; reported by "grarpamp".
1558 - Search for a platform-specific version of "ar" when cross-compiling.
1559 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
1562 Changes in version 0.2.3.3-alpha - 2011-09-01
1563 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
1564 security, and provides client-side support for the microdescriptor
1565 and optimistic data features introduced earlier in the 0.2.3.x
1566 series. It also includes numerous critical bugfixes in the (optional)
1567 bufferevent-based networking backend.
1569 o Major features (stream isolation):
1570 - You can now configure Tor so that streams from different
1571 applications are isolated on different circuits, to prevent an
1572 attacker who sees your streams as they leave an exit node from
1573 linking your sessions to one another. To do this, choose some way
1574 to distinguish the applications: have them connect to different
1575 SocksPorts, or have one of them use SOCKS4 while the other uses
1576 SOCKS5, or have them pass different authentication strings to the
1577 SOCKS proxy. Then, use the new SocksPort syntax to configure the
1578 degree of isolation you need. This implements Proposal 171.
1579 - There's a new syntax for specifying multiple client ports (such as
1580 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
1581 multiple *Port entries with full addr:port syntax on each.
1582 The old *ListenAddress format is still supported, but you can't
1583 mix it with the new *Port syntax.
1585 o Major features (other):
1586 - Enable microdescriptor fetching by default for clients. This allows
1587 clients to download a much smaller amount of directory information.
1588 To disable it (and go back to the old-style consensus and
1589 descriptors), set "UseMicrodescriptors 0" in your torrc file.
1590 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
1591 "PortForwarding" config option), now supports Windows.
1592 - When using an exit relay running 0.2.3.x, clients can now
1593 "optimistically" send data before the exit relay reports that
1594 the stream has opened. This saves a round trip when starting
1595 connections where the client speaks first (such as web browsing).
1596 This behavior is controlled by a consensus parameter (currently
1597 disabled). To turn it on or off manually, use the "OptimisticData"
1598 torrc option. Implements proposal 181; code by Ian Goldberg.
1600 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
1601 - When using IOCP on Windows, we need to enable Libevent windows
1603 - The IOCP backend now works even when the user has not specified
1604 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
1605 Fixes part of bug 3752.
1606 - Correctly record the bytes we've read and written when using
1607 bufferevents, so that we can include them in our bandwidth history
1608 and advertised bandwidth. Fixes bug 3803.
1609 - Apply rate-limiting only at the bottom of a chain of filtering
1610 bufferevents. This prevents us from filling up internal read
1611 buffers and violating rate-limits when filtering bufferevents
1612 are enabled. Fixes part of bug 3804.
1613 - Add high-watermarks to the output buffers for filtered
1614 bufferevents. This prevents us from filling up internal write
1615 buffers and wasting CPU cycles when filtering bufferevents are
1616 enabled. Fixes part of bug 3804.
1617 - Correctly notice when data has been written from a bufferevent
1618 without flushing it completely. Fixes bug 3805.
1619 - Fix a bug where server-side tunneled bufferevent-based directory
1620 streams would get closed prematurely. Fixes bug 3814.
1621 - Fix a use-after-free error with per-connection rate-limiting
1622 buckets. Fixes bug 3888.
1624 o Major bugfixes (also part of 0.2.2.31-rc):
1625 - If we're configured to write our ControlPorts to disk, only write
1626 them after switching UID and creating the data directory. This way,
1627 we don't fail when starting up with a nonexistent DataDirectory
1628 and a ControlPortWriteToFile setting based on that directory. Fixes
1629 bug 3747; bugfix on Tor 0.2.2.26-beta.
1632 - Added a new CONF_CHANGED event so that controllers can be notified
1633 of any configuration changes made by other controllers, or by the
1634 user. Implements ticket 1692.
1635 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
1636 leak when using bufferevents, and lets Libevent worry about how to
1637 best copy data out of a buffer.
1638 - Replace files in stats/ rather than appending to them. Now that we
1639 include statistics in extra-info descriptors, it makes no sense to
1640 keep old statistics forever. Implements ticket 2930.
1642 o Minor features (build compatibility):
1643 - Limited, experimental support for building with nmake and MSVC.
1644 - Provide a substitute implementation of lround() for MSVC, which
1645 apparently lacks it. Patch from Gisle Vanem.
1647 o Minor features (also part of 0.2.2.31-rc):
1648 - Update to the August 2 2011 Maxmind GeoLite Country database.
1650 o Minor bugfixes (on 0.2.3.x-alpha):
1651 - Fix a spurious warning when parsing SOCKS requests with
1652 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
1653 - Get rid of a harmless warning that could happen on relays running
1654 with bufferevents. The warning was caused by someone doing an http
1655 request to a relay's orport. Also don't warn for a few related
1656 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
1658 o Minor bugfixes (on 2.2.x and earlier):
1659 - Correct the man page to explain that HashedControlPassword and
1660 CookieAuthentication can both be set, in which case either method
1661 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
1662 when we decided to allow these config options to both be set. Issue
1664 - The "--quiet" and "--hush" options now apply not only to Tor's
1665 behavior before logs are configured, but also to Tor's behavior in
1666 the absense of configured logs. Fixes bug 3550; bugfix on
1669 o Minor bugfixes (also part of 0.2.2.31-rc):
1670 - Write several files in text mode, on OSes that distinguish text
1671 mode from binary mode (namely, Windows). These files are:
1672 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
1673 that collect those statistics; 'client_keys' and 'hostname' for
1674 hidden services that use authentication; and (in the tor-gencert
1675 utility) newly generated identity and signing keys. Previously,
1676 we wouldn't specify text mode or binary mode, leading to an
1677 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
1678 the DirRecordUsageByCountry option which would have triggered
1679 the assertion failure was added), although this assertion failure
1680 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
1681 - Selectively disable deprecation warnings on OS X because Lion
1682 started deprecating the shipped copy of openssl. Fixes bug 3643.
1683 - Remove an extra pair of quotation marks around the error
1684 message in control-port STATUS_GENERAL BUG events. Bugfix on
1685 0.1.2.6-alpha; fixes bug 3732.
1686 - When unable to format an address as a string, report its value
1687 as "???" rather than reusing the last formatted address. Bugfix
1690 o Code simplifications and refactoring:
1691 - Rewrite the listener-selection logic so that parsing which ports
1692 we want to listen on is now separate from binding to the ports
1696 - Building Tor with bufferevent support now requires Libevent
1697 2.0.13-stable or later. Previous versions of Libevent had bugs in
1698 SSL-related bufferevents and related issues that would make Tor
1699 work badly with bufferevents. Requiring 2.0.13-stable also allows
1700 Tor with bufferevents to take advantage of Libevent APIs
1701 introduced after 2.0.8-rc.
1704 Changes in version 0.2.2.32 - 2011-08-27
1705 The Tor 0.2.2 release series is dedicated to the memory of Andreas
1706 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
1707 a founder of the PETS community, a leader in our field, a mentor,
1708 and a friend. He left us with these words: "I had the possibility
1709 to contribute to this world that is not as it should be. I hope I
1710 could help in some areas to make the world a better place, and that
1711 I could also encourage other people to be engaged in improving the
1712 world. Please, stay engaged. This world needs you, your love, your
1713 initiative -- now I cannot be part of that anymore."
1715 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
1716 ready. More than two years in the making, this release features improved
1717 client performance and hidden service reliability, better compatibility
1718 for Android, correct behavior for bridges that listen on more than
1719 one address, more extensible and flexible directory object handling,
1720 better reporting of network statistics, improved code security, and
1721 many many other features and bugfixes.
1724 Changes in version 0.2.2.31-rc - 2011-08-17
1725 Tor 0.2.2.31-rc is the second and hopefully final release candidate
1726 for the Tor 0.2.2.x series.
1729 - Remove an extra pair of quotation marks around the error
1730 message in control-port STATUS_GENERAL BUG events. Bugfix on
1731 0.1.2.6-alpha; fixes bug 3732.
1732 - If we're configured to write our ControlPorts to disk, only write
1733 them after switching UID and creating the data directory. This way,
1734 we don't fail when starting up with a nonexistent DataDirectory
1735 and a ControlPortWriteToFile setting based on that directory. Fixes
1736 bug 3747; bugfix on Tor 0.2.2.26-beta.
1739 - Update to the August 2 2011 Maxmind GeoLite Country database.
1742 - Allow GETINFO fingerprint to return a fingerprint even when
1743 we have not yet built a router descriptor. Fixes bug 3577;
1744 bugfix on 0.2.0.1-alpha.
1745 - Write several files in text mode, on OSes that distinguish text
1746 mode from binary mode (namely, Windows). These files are:
1747 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
1748 that collect those statistics; 'client_keys' and 'hostname' for
1749 hidden services that use authentication; and (in the tor-gencert
1750 utility) newly generated identity and signing keys. Previously,
1751 we wouldn't specify text mode or binary mode, leading to an
1752 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
1753 the DirRecordUsageByCountry option which would have triggered
1754 the assertion failure was added), although this assertion failure
1755 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
1756 - Selectively disable deprecation warnings on OS X because Lion
1757 started deprecating the shipped copy of openssl. Fixes bug 3643.
1758 - When unable to format an address as a string, report its value
1759 as "???" rather than reusing the last formatted address. Bugfix
1763 Changes in version 0.2.3.2-alpha - 2011-07-18
1764 Tor 0.2.3.2-alpha introduces two new experimental features:
1765 microdescriptors and pluggable transports. It also continues cleaning
1766 up a variety of recently introduced features.
1769 - Clients can now use microdescriptors instead of regular descriptors
1770 to build circuits. Microdescriptors are authority-generated
1771 summaries of regular descriptors' contents, designed to change
1772 very rarely (see proposal 158 for details). This feature is
1773 designed to save bandwidth, especially for clients on slow internet
1774 connections. It's off by default for now, since nearly no caches
1775 support it, but it will be on-by-default for clients in a future
1776 version. You can use the UseMicrodescriptors option to turn it on.
1777 - Tor clients using bridges can now be configured to use a separate
1778 'transport' proxy for each bridge. This approach helps to resist
1779 censorship by allowing bridges to use protocol obfuscation
1780 plugins. It implements part of proposal 180. Implements ticket 2841.
1781 - While we're trying to bootstrap, record how many TLS connections
1782 fail in each state, and report which states saw the most failures
1783 in response to any bootstrap failures. This feature may speed up
1784 diagnosis of censorship events. Implements ticket 3116.
1786 o Major bugfixes (on 0.2.3.1-alpha):
1787 - When configuring a large set of nodes in EntryNodes (as with
1788 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
1789 random subset to be guards, and choose them in random
1790 order. Fixes bug 2798.
1791 - Tor could crash when remembering a consensus in a non-used consensus
1792 flavor without having a current consensus set. Fixes bug 3361.
1793 - Comparing an unknown address to a microdescriptor's shortened exit
1794 policy would always give a "rejected" result. Fixes bug 3599.
1795 - Using microdescriptors as a client no longer prevents Tor from
1796 uploading and downloading hidden service descriptors. Fixes
1800 - Allow nameservers with IPv6 address. Resolves bug 2574.
1801 - Accept attempts to include a password authenticator in the
1802 handshake, as supported by SOCKS5. This handles SOCKS clients that
1803 don't know how to omit a password when authenticating. Resolves
1805 - When configuring a large set of nodes in EntryNodes, and there are
1806 enough of them listed as Guard so that we don't need to consider
1807 the non-guard entries, prefer the ones listed with the Guard flag.
1808 - Check for and recover from inconsistency in the microdescriptor
1809 cache. This will make it harder for us to accidentally free a
1810 microdescriptor without removing it from the appropriate data
1811 structures. Fixes issue 3135; issue noted by "wanoskarnet".
1812 - Log SSL state transitions at log level DEBUG, log domain
1813 HANDSHAKE. This can be useful for debugging censorship events.
1814 Implements ticket 3264.
1815 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
1816 implements ticket 3439.
1818 o Minor bugfixes (on 0.2.3.1-alpha):
1819 - Do not free all general-purpose regular descriptors just
1820 because microdescriptor use is enabled. Fixes bug 3113.
1821 - Correctly link libevent_openssl when --enable-static-libevent
1822 is passed to configure. Fixes bug 3118.
1823 - Bridges should not complain during their heartbeat log messages that
1824 they are unlisted in the consensus: that's more or less the point
1825 of being a bridge. Fixes bug 3183.
1826 - Report a SIGNAL event to controllers when acting on a delayed
1827 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
1828 event to the controller if we acted on a SIGNAL NEWNYM command
1829 immediately, and otherwise not report a SIGNAL event for the
1830 command at all. Fixes bug 3349.
1831 - Fix a crash when handling the SIGNAL controller command or
1832 reporting ERR-level status events with bufferevents enabled. Found
1833 by Robert Ransom. Fixes bug 3367.
1834 - Always ship the tor-fw-helper manpage in our release tarballs.
1835 Fixes bug 3389. Reported by Stephen Walker.
1836 - Fix a class of double-mark-for-close bugs when bufferevents
1837 are enabled. Fixes bug 3403.
1838 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
1839 - Add SIGNAL to the list returned by the 'GETINFO events/names'
1840 control-port command. Fixes part of bug 3465.
1841 - Prevent using negative indices during unit test runs when read_all()
1842 fails. Spotted by coverity.
1843 - Fix a rare memory leak when checking the nodelist without it being
1844 present. Found by coverity.
1845 - Only try to download a microdescriptor-flavored consensus from
1846 a directory cache that provides them.
1848 o Minor bugfixes (on 0.2.2.x and earlier):
1849 - Assert that hidden-service-related operations are not performed
1850 using single-hop circuits. Previously, Tor would assert that
1851 client-side streams are not attached to single-hop circuits,
1852 but not that other sensitive operations on the client and service
1853 side are not performed using single-hop circuits. Fixes bug 3332;
1855 - Don't publish a new relay descriptor when we reload our onion key,
1856 unless the onion key has actually changed. Fixes bug 3263 and
1857 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
1858 - Allow GETINFO fingerprint to return a fingerprint even when
1859 we have not yet built a router descriptor. Fixes bug 3577;
1860 bugfix on 0.2.0.1-alpha.
1861 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
1862 on 0.2.2.4-alpha; fixes bug 3427.
1864 o Code simplification and refactoring:
1865 - Use tor_sscanf() in place of scanf() in more places through the
1866 code. This makes us a little more locale-independent, and
1867 should help shut up code-analysis tools that can't tell
1868 a safe sscanf string from a dangerous one.
1869 - Use tt_assert(), not tor_assert(), for checking for test failures.
1870 This makes the unit tests more able to go on in the event that
1872 - Split connection_about_to_close() into separate functions for each
1876 - On Windows, we now define the _WIN32_WINNT macros only if they
1877 are not already defined. This lets the person building Tor decide,
1878 if they want, to require a later version of Windows.
1881 Changes in version 0.2.2.30-rc - 2011-07-07
1882 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
1883 series. It fixes a few smaller bugs, but generally appears stable.
1884 Please test it and let us know whether it is!
1887 - Send a SUCCEEDED stream event to the controller when a reverse
1888 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
1889 discovered by katmagic.
1890 - Always NUL-terminate the sun_path field of a sockaddr_un before
1891 passing it to the kernel. (Not a security issue: kernels are
1892 smart enough to reject bad sockaddr_uns.) Found by Coverity;
1893 CID #428. Bugfix on Tor 0.2.0.3-alpha.
1894 - Don't stack-allocate the list of supplementary GIDs when we're
1895 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
1896 could take up to 256K, which is way too much stack. Found by
1897 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
1898 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
1899 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
1900 fixes part of bug 3465.
1901 - Fix a memory leak when receiving a descriptor for a hidden
1902 service we didn't ask for. Found by Coverity; CID #30. Bugfix
1906 - Update to the July 1 2011 Maxmind GeoLite Country database.
1909 Changes in version 0.2.2.29-beta - 2011-06-20
1910 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
1911 have bridge lines in their torrc but don't want to use them; gets
1912 us closer to having the control socket feature working on Debian;
1913 and fixes a variety of smaller bugs.
1916 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
1917 When we changed the default behavior to "use bridges if any
1918 are listed in the torrc", we surprised users who had bridges
1919 in their torrc files but who didn't actually want to use them.
1920 Partial resolution for bug 3354.
1923 - Don't attach new streams to old rendezvous circuits after SIGNAL
1924 NEWNYM. Previously, we would keep using an existing rendezvous
1925 circuit if it remained open (i.e. if it were kept open by a
1926 long-lived stream, or if a new stream were attached to it before
1927 Tor could notice that it was old and no longer in use). Bugfix on
1928 0.1.1.15-rc; fixes bug 3375.
1931 - Fix a bug when using ControlSocketsGroupWritable with User. The
1932 directory's group would be checked against the current group, not
1933 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
1934 bugfix on 0.2.2.26-beta.
1935 - Make connection_printf_to_buf()'s behaviour sane. Its callers
1936 expect it to emit a CRLF iff the format string ends with CRLF;
1937 it actually emitted a CRLF iff (a) the format string ended with
1938 CRLF or (b) the resulting string was over 1023 characters long or
1939 (c) the format string did not end with CRLF *and* the resulting
1940 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
1941 fixes part of bug 3407.
1942 - Make send_control_event_impl()'s behaviour sane. Its callers
1943 expect it to always emit a CRLF at the end of the string; it
1944 might have emitted extra control characters as well. Bugfix on
1945 0.1.1.9-alpha; fixes another part of bug 3407.
1946 - Make crypto_rand_int() check the value of its input correctly.
1947 Previously, it accepted values up to UINT_MAX, but could return a
1948 negative number if given a value above INT_MAX+1. Found by George
1949 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
1950 - Avoid a segfault when reading a malformed circuit build state
1951 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
1953 - When asked about a DNS record type we don't support via a
1954 client DNSPort, reply with NOTIMPL rather than an empty
1955 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
1956 - Fix a rare memory leak during stats writing. Found by coverity.
1959 - Update to the June 1 2011 Maxmind GeoLite Country database.
1961 o Code simplifications and refactoring:
1962 - Remove some dead code as indicated by coverity.
1963 - Remove a few dead assignments during router parsing. Found by
1965 - Add some forgotten return value checks during unit tests. Found
1967 - Don't use 1-bit wide signed bit fields. Found by coverity.
1970 Changes in version 0.2.2.28-beta - 2011-06-04
1971 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
1972 fixed a big bug in whether relays stay in the consensus consistently,
1973 we moved closer to handling bridges and hidden services correctly,
1974 and we started the process of better handling the dreaded "my Vidalia
1975 died, and now my Tor demands a password when I try to reconnect to it"
1979 - Don't decide to make a new descriptor when receiving a HUP signal.
1980 This bug has caused a lot of 0.2.2.x relays to disappear from the
1981 consensus periodically. Fixes the most common case of triggering
1982 bug 1810; bugfix on 0.2.2.7-alpha.
1983 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
1984 - Don't try to build descriptors if "ORPort auto" is set and we
1985 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
1987 - Resolve a crash that occurred when setting BridgeRelay to 1 with
1988 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
1989 - Apply circuit timeouts to opened hidden-service-related circuits
1990 based on the correct start time. Previously, we would apply the
1991 circuit build timeout based on time since the circuit's creation;
1992 it was supposed to be applied based on time since the circuit
1993 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
1994 - Use the same circuit timeout for client-side introduction
1995 circuits as for other four-hop circuits, rather than the timeout
1996 for single-hop directory-fetch circuits; the shorter timeout may
1997 have been appropriate with the static circuit build timeout in
1998 0.2.1.x and earlier, but caused many hidden service access attempts
1999 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
2000 on 0.2.2.2-alpha; fixes another part of bug 1297.
2001 - In ticket 2511 we fixed a case where you could use an unconfigured
2002 bridge if you had configured it as a bridge the last time you ran
2003 Tor. Now fix another edge case: if you had configured it as a bridge
2004 but then switched to a different bridge via the controller, you
2005 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
2009 - Add an __OwningControllerProcess configuration option and a
2010 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
2011 that when it exits, Tor will shut down. Implements feature 3049.
2012 - If "UseBridges 1" is set and no bridges are configured, Tor will
2013 now refuse to build any circuits until some bridges are set.
2014 If "UseBridges auto" is set, Tor will use bridges if they are
2015 configured and we are not running as a server, but otherwise will
2016 make circuits as usual. The new default is "auto". Patch by anonym,
2017 so the Tails LiveCD can stop automatically revealing you as a Tor
2021 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2022 - Remove a trailing asterisk from "exit-policy/default" in the
2023 output of the control port command "GETINFO info/names". Bugfix
2025 - Use a wide type to hold sockets when built for 64-bit Windows builds.
2027 - Warn when the user configures two HiddenServiceDir lines that point
2028 to the same directory. Bugfix on 0.0.6 (the version introducing
2029 HiddenServiceDir); fixes bug 3289.
2030 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
2031 part of bug 2748; bugfix on 0.2.0.10-alpha.
2032 - Log malformed requests for rendezvous descriptors as protocol
2033 warnings, not warnings. Also, use a more informative log message
2034 in case someone sees it at log level warning without prior
2035 info-level messages. Fixes the other part of bug 2748; bugfix
2037 - Clear the table recording the time of the last request for each
2038 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
2039 Previously, we would clear our HS descriptor cache on SIGNAL
2040 NEWNYM, but if we had previously retrieved a descriptor (or tried
2041 to) from every directory responsible for it, we would refuse to
2042 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
2044 - Fix a log message that said "bits" while displaying a value in
2045 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
2047 - When checking for 1024-bit keys, check for 1024 bits, not 128
2048 bytes. This allows Tor to correctly discard keys of length 1017
2049 through 1023. Bugfix on 0.0.9pre5.
2052 - Relays now log the reason for publishing a new relay descriptor,
2053 so we have a better chance of hunting down instances of bug 1810.
2054 Resolves ticket 3252.
2055 - Revise most log messages that refer to nodes by nickname to
2056 instead use the "$key=nickname at address" format. This should be
2057 more useful, especially since nicknames are less and less likely
2058 to be unique. Resolves ticket 3045.
2059 - Log (at info level) when purging pieces of hidden-service-client
2060 state because of SIGNAL NEWNYM.
2063 - Remove undocumented option "-F" from tor-resolve: it hasn't done
2064 anything since 0.2.1.16-rc.
2067 Changes in version 0.2.2.27-beta - 2011-05-18
2068 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
2069 release, and also adds a few more general bugfixes.
2072 - Fix a crash bug when changing bridges in a running Tor process.
2073 Fixes bug 3213; bugfix on 0.2.2.26-beta.
2074 - When the controller configures a new bridge, don't wait 10 to 60
2075 seconds before trying to fetch its descriptor. Bugfix on
2076 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
2079 - Require that onion keys have exponent 65537 in microdescriptors too.
2080 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
2081 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
2082 Changed the limit to 512 characters by removing base64 newlines.
2083 Fixes bug 2752. Fix by Michael Yakubovich.
2084 - When a client starts or stops using bridges, never use a circuit
2085 that was built before the configuration change. This behavior could
2086 put at risk a user who uses bridges to ensure that her traffic
2087 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
2091 Changes in version 0.2.2.26-beta - 2011-05-17
2092 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
2093 also introduces a new "socksport auto" approach that should make it
2094 easier to run multiple Tors on the same system, and does a lot of
2095 cleanup to get us closer to a release candidate.
2097 o Security/privacy fixes:
2098 - Replace all potentially sensitive memory comparison operations
2099 with versions whose runtime does not depend on the data being
2100 compared. This will help resist a class of attacks where an
2101 adversary can use variations in timing information to learn
2102 sensitive data. Fix for one case of bug 3122. (Safe memcmp
2103 implementation by Robert Ransom based partially on code by DJB.)
2104 - When receiving a hidden service descriptor, check that it is for
2105 the hidden service we wanted. Previously, Tor would store any
2106 hidden service descriptors that a directory gave it, whether it
2107 wanted them or not. This wouldn't have let an attacker impersonate
2108 a hidden service, but it did let directories pre-seed a client
2109 with descriptors that it didn't want. Bugfix on 0.0.6.
2110 - On SIGHUP, do not clear out all TrackHostExits mappings, client
2111 DNS cache entries, and virtual address mappings: that's what
2112 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
2115 - The options SocksPort, ControlPort, and so on now all accept a
2116 value "auto" that opens a socket on an OS-selected port. A
2117 new ControlPortWriteToFile option tells Tor to write its
2118 actual control port or ports to a chosen file. If the option
2119 ControlPortFileGroupReadable is set, the file is created as
2120 group-readable. Now users can run two Tor clients on the same
2121 system without needing to manually mess with parameters. Resolves
2122 part of ticket 3076.
2123 - Set SO_REUSEADDR on all sockets, not just listeners. This should
2124 help busy exit nodes avoid running out of useable ports just
2125 because all the ports have been used in the near past. Resolves
2129 - New "GETINFO net/listeners/(type)" controller command to return
2130 a list of addresses and ports that are bound for listeners for a
2131 given connection type. This is useful when the user has configured
2132 "SocksPort auto" and the controller needs to know which port got
2133 chosen. Resolves another part of ticket 3076.
2134 - Add a new ControlSocketsGroupWritable configuration option: when
2135 it is turned on, ControlSockets are group-writeable by the default
2136 group of the current user. Patch by Jérémy Bobbio; implements
2138 - Tor now refuses to create a ControlSocket in a directory that is
2139 world-readable (or group-readable if ControlSocketsGroupWritable
2140 is 0). This is necessary because some operating systems do not
2141 enforce permissions on an AF_UNIX sockets. Permissions on the
2142 directory holding the socket, however, seems to work everywhere.
2143 - Rate-limit a warning about failures to download v2 networkstatus
2144 documents. Resolves part of bug 1352.
2145 - Backport code from 0.2.3.x that allows directory authorities to
2146 clean their microdescriptor caches. Needed to resolve bug 2230.
2147 - When an HTTPS proxy reports "403 Forbidden", we now explain
2148 what it means rather than calling it an unexpected status code.
2149 Closes bug 2503. Patch from Michael Yakubovich.
2150 - Update to the May 1 2011 Maxmind GeoLite Country database.
2153 - Authorities now clean their microdesc cache periodically and when
2154 reading from disk initially, not only when adding new descriptors.
2155 This prevents a bug where we could lose microdescriptors. Bugfix
2156 on 0.2.2.6-alpha. Fixes bug 2230.
2157 - Do not crash when our configuration file becomes unreadable, for
2158 example due to a permissions change, between when we start up
2159 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2161 - Avoid a bug that would keep us from replacing a microdescriptor
2162 cache on Windows. (We would try to replace the file while still
2163 holding it open. That's fine on Unix, but Windows doesn't let us
2164 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
2165 - Add missing explanations for the authority-related torrc options
2166 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
2167 man page. Resolves issue 2379.
2168 - As an authority, do not upload our own vote or signature set to
2169 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
2170 it would get flagged as a duplicate. Resolves bug 3026.
2171 - Accept hidden service descriptors if we think we might be a hidden
2172 service directory, regardless of what our consensus says. This
2173 helps robustness, since clients and hidden services can sometimes
2174 have a more up-to-date view of the network consensus than we do,
2175 and if they think that the directory authorities list us a HSDir,
2176 we might actually be one. Related to bug 2732; bugfix on
2178 - When a controller changes TrackHostExits, remove mappings for
2179 hosts that should no longer have their exits tracked. Bugfix on
2181 - When a controller changes VirtualAddrNetwork, remove any mappings
2182 for hosts that were automapped to the old network. Bugfix on
2184 - When a controller changes one of the AutomapHosts* options, remove
2185 any mappings for hosts that should no longer be automapped. Bugfix
2187 - Do not reset the bridge descriptor download status every time we
2188 re-parse our configuration or get a configuration change. Fixes
2189 bug 3019; bugfix on 0.2.0.3-alpha.
2191 o Minor bugfixes (code cleanup):
2192 - When loading the microdesc journal, remember its current size.
2193 In 0.2.2, this helps prevent the microdesc journal from growing
2194 without limit on authorities (who are the only ones to use it in
2195 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
2196 Fix posted by "cypherpunks."
2197 - The microdesc journal is supposed to get rebuilt only if it is
2198 at least _half_ the length of the store, not _twice_ the length
2199 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
2200 - Fix a potential null-pointer dereference while computing a
2201 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
2203 - Avoid a possible null-pointer dereference when rebuilding the mdesc
2204 cache without actually having any descriptors to cache. Bugfix on
2205 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
2206 - If we fail to compute the identity digest of a v3 legacy keypair,
2207 warn, and don't use a buffer-full of junk instead. Bugfix on
2208 0.2.1.1-alpha; fixes bug 3106.
2209 - Resolve an untriggerable issue in smartlist_string_num_isin(),
2210 where if the function had ever in the future been used to check
2211 for the presence of a too-large number, it would have given an
2212 incorrect result. (Fortunately, we only used it for 16-bit
2213 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
2214 - Require that introduction point keys and onion handshake keys
2215 have a public exponent of 65537. Starts to fix bug 3207; bugfix
2219 - Caches no longer download and serve v2 networkstatus documents
2220 unless FetchV2Networkstatus flag is set: these documents haven't
2221 haven't been used by clients or relays since 0.2.0.x. Resolves
2225 Changes in version 0.2.3.1-alpha - 2011-05-05
2226 Tor 0.2.3.1-alpha adds some new experimental features, including support
2227 for an improved network IO backend, IOCP networking on Windows,
2228 microdescriptor caching, "fast-start" support for streams, and automatic
2229 home router configuration. There are also numerous internal improvements
2230 to try to make the code easier for developers to work with.
2232 This is the first alpha release in a new series, so expect there to be
2233 bugs. Users who would rather test out a more stable branch should
2234 stay with 0.2.2.x for now.
2237 - Tor can now optionally build with the "bufferevents" buffered IO
2238 backend provided by Libevent 2. To use this feature, make sure you
2239 have the latest possible version of Libevent, and pass the
2240 --enable-bufferevents flag to configure when building Tor from
2241 source. This feature will make our networking code more flexible,
2242 let us stack layers on each other, and let us use more efficient
2243 zero-copy transports where available.
2244 - As an experimental feature, Tor can use IOCP for networking on Windows.
2245 Once this code is tuned and optimized, it promises much better
2246 performance than the select-based backend we've used in the past. To
2247 try this feature, you must build Tor with Libevent 2, configure Tor
2248 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
2249 your torrc. There are known bugs here: only try this if you can help
2250 debug it as it breaks.
2251 - The EntryNodes option can now include country codes like {de} or IP
2252 addresses or network masks. Previously we had disallowed these options
2253 because we didn't have an efficient way to keep the list up to
2254 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
2255 - Exit nodes now accept and queue data on not-yet-connected streams.
2256 Previously, the client wasn't allowed to send data until the stream was
2257 connected, which slowed down all connections. This change will enable
2258 clients to perform a "fast-start" on streams and send data without
2259 having to wait for a confirmation that the stream has opened. (Patch
2260 from Ian Goldberg; implements the server side of Proposal 174.)
2261 - Tor now has initial support for automatic port mapping on the many
2262 home routers that support NAT-PMP or UPnP. (Not yet supported on
2263 Windows). To build the support code, you'll need to have libnatpnp
2264 library and/or the libminiupnpc library, and you'll need to enable the
2265 feature specifically by passing "--enable-upnp" and/or
2266 "--enable-natpnp" to configure. To turn it on, use the new
2267 PortForwarding option.
2268 - Caches now download, cache, and serve multiple "flavors" of the
2269 consensus, including a flavor that describes microdescriptors.
2270 - Caches now download, cache, and serve microdescriptors -- small
2271 summaries of router descriptors that are authenticated by all of the
2272 directory authorities. Once enough caches are running this code,
2273 clients will be able to save significant amounts of directory bandwidth
2274 by downloading microdescriptors instead of router descriptors.
2277 - Make logging resolution configurable with a new LogTimeGranularity
2278 option, and change the default from 1 millisecond to 1 second.
2279 Implements enhancement 1668.
2280 - We log which torrc file we're using on startup. Implements ticket
2282 - Ordinarily, Tor does not count traffic from private addresses (like
2283 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
2284 There is now a new option, CountPrivateBandwidth, to disable this
2285 behavior. Patch from Daniel Cagara.
2286 - New --enable-static-tor configure option for building Tor as
2287 statically as possible. Idea, general hackery and thoughts from
2288 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
2290 - If you set the NumCPUs option to 0, Tor will now try to detect how
2291 many CPUs you have. This is the new default behavior.
2292 - Turn on directory request statistics by default and include them in
2293 extra-info descriptors. Don't break if we have no GeoIP database.
2294 - Relays that set "ConnDirectionStatistics 1" write statistics on the
2295 bidirectional use of connections to disk every 24 hours.
2296 - Add a GeoIP file digest to the extra-info descriptor. Implements
2298 - The NodeFamily option -- which let you declare that you want to
2299 consider nodes to be part of a family whether they list themselves
2300 that way or not -- now allows IP address ranges and country codes.
2301 - Add a new 'Heartbeat' log message type to periodically log a message
2302 describing Tor's status at level Notice. This feature is meant for
2303 operators who log at notice, and want to make sure that their Tor
2304 server is still working. Implementation by George Kadianakis.
2306 o Minor bugfixes (on 0.2.2.25-alpha):
2307 - When loading the microdesc journal, remember its current size.
2308 In 0.2.2, this helps prevent the microdesc journal from growing
2309 without limit on authorities (who are the only ones to use it in
2310 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
2311 Fix posted by "cypherpunks."
2312 - The microdesc journal is supposed to get rebuilt only if it is
2313 at least _half_ the length of the store, not _twice_ the length
2314 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
2315 - If as an authority we fail to compute the identity digest of a v3
2316 legacy keypair, warn, and don't use a buffer-full of junk instead.
2317 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
2318 - Authorities now clean their microdesc cache periodically and when
2319 reading from disk initially, not only when adding new descriptors.
2320 This prevents a bug where we could lose microdescriptors. Bugfix
2323 o Minor features (controller):
2324 - Add a new SIGNAL event to the controller interface so that
2325 controllers can be notified when Tor handles a signal. Resolves
2326 issue 1955. Patch by John Brooks.
2327 - Add a new GETINFO option to get total bytes read and written. Patch
2328 from pipe, revised by atagar. Resolves ticket 2345.
2329 - Implement some GETINFO controller fields to provide information about
2330 the Tor process's pid, euid, username, and resource limits.
2333 - Our build system requires automake 1.6 or later to create the
2334 Makefile.in files. Previously, you could have used 1.4.
2335 This only affects developers and people building Tor from git;
2336 people who build Tor from the source distribution without changing
2337 the Makefile.am files should be fine.
2338 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
2339 so on. This is more robust against some of the failure modes
2340 associated with running the autotools pieces on their own.
2342 o Minor packaging issues:
2343 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
2344 already created. Patch from Andreas Stieger. Fixes bug 2573.
2346 o Code simplifications and refactoring:
2347 - A major revision to our internal node-selecting and listing logic.
2348 Tor already had at least two major ways to look at the question of
2349 "which Tor servers do we know about": a list of router descriptors,
2350 and a list of entries in the current consensus. With
2351 microdescriptors, we're adding a third. Having so many systems
2352 without an abstraction layer over them was hurting the codebase.
2353 Now, we have a new "node_t" abstraction that presents a consistent
2354 interface to a client's view of a Tor node, and holds (nearly) all
2355 of the mutable state formerly in routerinfo_t and routerstatus_t.
2356 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
2357 no longer link against Libevent: they never used it, but
2358 our library structure used to force them to link it.
2361 - Remove some old code to work around even older versions of Tor that
2362 used forked processes to handle DNS requests. Such versions of Tor
2363 are no longer in use as servers.
2365 o Documentation fixes:
2366 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
2367 - Add missing documentation for the authority-related torrc options
2368 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
2372 Changes in version 0.2.2.25-alpha - 2011-04-29
2373 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
2374 robust, routers no longer overreport their bandwidth, Win7 should crash
2375 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
2376 now prevents hidden service-related activity from being linkable. It
2377 provides more information to Vidalia so you can see if your bridge is
2378 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
2379 StrictNodes configuration options to make them more reliable, more
2380 understandable, and more regularly applied. If you use those options,
2381 please see the revised documentation for them in the manual page.
2384 - Relays were publishing grossly inflated bandwidth values because
2385 they were writing their state files wrong--now they write the
2386 correct value. Also, resume reading bandwidth history from the
2387 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
2388 - Improve hidden service robustness: When we find that we have
2389 extended a hidden service's introduction circuit to a relay not
2390 listed as an introduction point in the HS descriptor we currently
2391 have, retry with an introduction point from the current
2392 descriptor. Previously we would just give up. Fixes bugs 1024 and
2393 1930; bugfix on 0.2.0.10-alpha.
2394 - Clients now stop trying to use an exit node associated with a given
2395 destination by TrackHostExits if they fail to reach that exit node.
2396 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
2397 - Fix crash bug on platforms where gmtime and localtime can return
2398 NULL. Windows 7 users were running into this one. Fixes part of bug
2399 2077. Bugfix on all versions of Tor. Found by boboper.
2401 o Security and stability fixes:
2402 - Don't double-free a parsable, but invalid, microdescriptor, even if
2403 it is followed in the blob we're parsing by an unparsable
2404 microdescriptor. Fixes an issue reported in a comment on bug 2954.
2405 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
2406 - If the Nickname configuration option isn't given, Tor would pick a
2407 nickname based on the local hostname as the nickname for a relay.
2408 Because nicknames are not very important in today's Tor and the
2409 "Unnamed" nickname has been implemented, this is now problematic
2410 behavior: It leaks information about the hostname without being
2411 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
2412 introduced the Unnamed nickname. Reported by tagnaq.
2413 - Fix an uncommon assertion failure when running with DNSPort under
2414 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
2415 - Avoid linkability based on cached hidden service descriptors: forget
2416 all hidden service descriptors cached as a client when processing a
2417 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
2420 - Export GeoIP information on bridge usage to controllers even if we
2421 have not yet been running for 24 hours. Now Vidalia bridge operators
2422 can get more accurate and immediate feedback about their
2423 contributions to the network.
2425 o Major features and bugfixes (node selection):
2426 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
2427 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
2428 options. Previously, we had been ambiguous in describing what
2429 counted as an "exit" node, and what operations exactly "StrictNodes
2430 0" would permit. This created confusion when people saw nodes built
2431 through unexpected circuits, and made it hard to tell real bugs from
2432 surprises. Now the intended behavior is:
2433 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
2434 a node that delivers user traffic outside the Tor network.
2435 . "Entry", in the context of EntryNodes, means a node used as the
2436 first hop of a multihop circuit. It doesn't include direct
2437 connections to directory servers.
2438 . "ExcludeNodes" applies to all nodes.
2439 . "StrictNodes" changes the behavior of ExcludeNodes only. When
2440 StrictNodes is set, Tor should avoid all nodes listed in
2441 ExcludeNodes, even when it will make user requests fail. When
2442 StrictNodes is *not* set, then Tor should follow ExcludeNodes
2443 whenever it can, except when it must use an excluded node to
2444 perform self-tests, connect to a hidden service, provide a
2445 hidden service, fulfill a .exit request, upload directory
2446 information, or fetch directory information.
2447 Collectively, the changes to implement the behavior fix bug 1090.
2448 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
2449 a node is listed in both, it's treated as excluded.
2450 - ExcludeNodes now applies to directory nodes -- as a preference if
2451 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
2452 Don't exclude all the directory authorities and set StrictNodes to 1
2453 unless you really want your Tor to break.
2454 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
2455 - ExcludeExitNodes now overrides .exit requests.
2456 - We don't use bridges listed in ExcludeNodes.
2457 - When StrictNodes is 1:
2458 . We now apply ExcludeNodes to hidden service introduction points
2459 and to rendezvous points selected by hidden service users. This
2460 can make your hidden service less reliable: use it with caution!
2461 . If we have used ExcludeNodes on ourself, do not try relay
2462 reachability self-tests.
2463 . If we have excluded all the directory authorities, we will not
2464 even try to upload our descriptor if we're a relay.
2465 . Do not honor .exit requests to an excluded node.
2466 - Remove a misfeature that caused us to ignore the Fast/Stable flags
2467 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
2468 - When the set of permitted nodes changes, we now remove any mappings
2469 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
2471 - We never cannibalize a circuit that had excluded nodes on it, even
2472 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
2473 - Revert a change where we would be laxer about attaching streams to
2474 circuits than when building the circuits. This was meant to prevent
2475 a set of bugs where streams were never attachable, but our improved
2476 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
2477 - Keep track of how many times we launch a new circuit to handle a
2478 given stream. Too many launches could indicate an inconsistency
2479 between our "launch a circuit to handle this stream" logic and our
2480 "attach this stream to one of the available circuits" logic.
2481 - Improve log messages related to excluded nodes.
2484 - Fix a spurious warning when moving from a short month to a long
2485 month on relays with month-based BandwidthAccounting. Bugfix on
2486 0.2.2.17-alpha; fixes bug 3020.
2487 - When a client finds that an origin circuit has run out of 16-bit
2488 stream IDs, we now mark it as unusable for new streams. Previously,
2489 we would try to close the entire circuit. Bugfix on 0.0.6.
2490 - Add a forgotten cast that caused a compile warning on OS X 10.6.
2491 Bugfix on 0.2.2.24-alpha.
2492 - Be more careful about reporting the correct error from a failed
2493 connect() system call. Under some circumstances, it was possible to
2494 look at an incorrect value for errno when sending the end reason.
2495 Bugfix on 0.1.0.1-rc.
2496 - Correctly handle an "impossible" overflow cases in connection byte
2497 counting, where we write or read more than 4GB on an edge connection
2498 in a single second. Bugfix on 0.1.2.8-beta.
2499 - Correct the warning displayed when a rendezvous descriptor exceeds
2500 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
2502 - Clients and hidden services now use HSDir-flagged relays for hidden
2503 service descriptor downloads and uploads even if the relays have no
2504 DirPort set and the client has disabled TunnelDirConns. This will
2505 eventually allow us to give the HSDir flag to relays with no
2506 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
2507 - Downgrade "no current certificates known for authority" message from
2508 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
2509 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
2510 2917. Bugfix on 0.1.1.1-alpha.
2511 - Only limit the lengths of single HS descriptors, even when multiple
2512 HS descriptors are published to an HSDir relay in a single POST
2513 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
2514 - Write the current time into the LastWritten line in our state file,
2515 rather than the time from the previous write attempt. Also, stop
2516 trying to use a time of -1 in our log statements. Fixes bug 3039;
2517 bugfix on 0.2.2.14-alpha.
2518 - Be more consistent in our treatment of file system paths. "~" should
2519 get expanded to the user's home directory in the Log config option.
2520 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
2521 feature for the -f and --DataDirectory options.
2524 - Make sure every relay writes a state file at least every 12 hours.
2525 Previously, a relay could go for weeks without writing its state
2526 file, and on a crash could lose its bandwidth history, capacity
2527 estimates, client country statistics, and so on. Addresses bug 3012.
2528 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
2529 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
2530 clients are already deprecated because of security bugs.
2531 - Don't allow v0 hidden service authorities to act as clients.
2532 Required by fix for bug 3000.
2533 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
2534 by fix for bug 3000.
2535 - Ensure that no empty [dirreq-](read|write)-history lines are added
2536 to an extrainfo document. Implements ticket 2497.
2538 o Code simplification and refactoring:
2539 - Remove workaround code to handle directory responses from servers
2540 that had bug 539 (they would send HTTP status 503 responses _and_
2541 send a body too). Since only server versions before
2542 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
2543 keep the workaround in place.
2544 - Remove the old 'fuzzy time' logic. It was supposed to be used for
2545 handling calculations where we have a known amount of clock skew and
2546 an allowed amount of unknown skew. But we only used it in three
2547 places, and we never adjusted the known/unknown skew values. This is
2548 still something we might want to do someday, but if we do, we'll
2549 want to do it differently.
2550 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
2551 None of the cases where we did this before were wrong, but by making
2552 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
2553 - Use GetTempDir to find the proper temporary directory location on
2554 Windows when generating temporary files for the unit tests. Patch by
2558 Changes in version 0.2.2.24-alpha - 2011-04-08
2559 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
2560 prevented Tor clients from effectively using "multihomed" bridges,
2561 that is, bridges that listen on multiple ports or IP addresses so users
2562 can continue to use some of their addresses even if others get blocked.
2565 - Fix a bug where bridge users who configure the non-canonical
2566 address of a bridge automatically switch to its canonical
2567 address. If a bridge listens at more than one address, it should be
2568 able to advertise those addresses independently and any non-blocked
2569 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
2571 - If you configured Tor to use bridge A, and then quit and
2572 configured Tor to use bridge B instead, it would happily continue
2573 to use bridge A if it's still reachable. While this behavior is
2574 a feature if your goal is connectivity, in some scenarios it's a
2575 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
2576 - Directory authorities now use data collected from their own
2577 uptime observations when choosing whether to assign the HSDir flag
2578 to relays, instead of trusting the uptime value the relay reports in
2579 its descriptor. This change helps prevent an attack where a small
2580 set of nodes with frequently-changing identity keys can blackhole
2581 a hidden service. (Only authorities need upgrade; others will be
2582 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
2585 - When we restart our relay, we might get a successful connection
2586 from the outside before we've started our reachability tests,
2587 triggering a warning: "ORPort found reachable, but I have no
2588 routerinfo yet. Failing to inform controller of success." This
2589 bug was harmless unless Tor is running under a controller
2590 like Vidalia, in which case the controller would never get a
2591 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
2593 - Make directory authorities more accurate at recording when
2594 relays that have failed several reachability tests became
2595 unreachable, so we can provide more accuracy at assigning Stable,
2596 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
2597 - Fix an issue that prevented static linking of libevent on
2598 some platforms (notably Linux). Fixes bug 2698; bugfix on
2599 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
2600 the --with-static-libevent configure option).
2601 - We now ask the other side of a stream (the client or the exit)
2602 for more data on that stream when the amount of queued data on
2603 that stream dips low enough. Previously, we wouldn't ask the
2604 other side for more data until either it sent us more data (which
2605 it wasn't supposed to do if it had exhausted its window!) or we
2606 had completely flushed all our queued data. This flow control fix
2607 should improve throughput. Fixes bug 2756; bugfix on the earliest
2608 released versions of Tor (svn commit r152).
2609 - Avoid a double-mark-for-free warning when failing to attach a
2610 transparent proxy connection. (We thought we had fixed this in
2611 0.2.2.23-alpha, but it turns out our fix was checking the wrong
2612 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
2613 bug) and 0.2.2.23-alpha (the incorrect fix).
2614 - When warning about missing zlib development packages during compile,
2615 give the correct package names. Bugfix on 0.2.0.1-alpha.
2618 - Directory authorities now log the source of a rejected POSTed v3
2620 - Make compilation with clang possible when using
2621 --enable-gcc-warnings by removing two warning options that clang
2622 hasn't implemented yet and by fixing a few warnings. Implements
2624 - When expiring circuits, use microsecond timers rather than
2625 one-second timers. This can avoid an unpleasant situation where a
2626 circuit is launched near the end of one second and expired right
2627 near the beginning of the next, and prevent fluctuations in circuit
2629 - Use computed circuit-build timeouts to decide when to launch
2630 parallel introduction circuits for hidden services. (Previously,
2631 we would retry after 15 seconds.)
2632 - Update to the April 1 2011 Maxmind GeoLite Country database.
2635 - Create the /var/run/tor directory on startup on OpenSUSE if it is
2636 not already created. Patch from Andreas Stieger. Fixes bug 2573.
2638 o Documentation changes:
2639 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
2640 - Resolve all doxygen warnings except those for missing documentation.
2642 - Add doxygen documentation for more functions, fields, and types.
2645 Changes in version 0.2.2.23-alpha - 2011-03-08
2646 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
2647 they restart they don't lose their bandwidth capacity estimate. This
2648 release also fixes a diverse set of user-facing bugs, ranging from
2649 relays overrunning their rate limiting to clients falsely warning about
2650 clock skew to bridge descriptor leaks by our bridge directory authority.
2653 - Stop sending a CLOCK_SKEW controller status event whenever
2654 we fetch directory information from a relay that has a wrong clock.
2655 Instead, only inform the controller when it's a trusted authority
2656 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
2657 the rest of bug 1074.
2658 - Fix an assert in parsing router descriptors containing IPv6
2659 addresses. This one took down the directory authorities when
2660 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
2661 - Make the bridge directory authority refuse to answer directory
2662 requests for "all" descriptors. It used to include bridge
2663 descriptors in its answer, which was a major information leak.
2664 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
2665 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
2666 Tor would ignore their RelayBandwidthBurst setting,
2667 potentially using more bandwidth than expected. Bugfix on
2668 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
2669 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
2670 hidserv" in her torrc. The 'hidserv' argument never controlled
2671 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
2674 - Relays now save observed peak bandwidth throughput rates to their
2675 state file (along with total usage, which was already saved)
2676 so that they can determine their correct estimated bandwidth on
2677 restart. Resolves bug 1863, where Tor relays would reset their
2678 estimated bandwidth to 0 after restarting.
2679 - Directory authorities now take changes in router IP address and
2680 ORPort into account when determining router stability. Previously,
2681 if a router changed its IP or ORPort, the authorities would not
2682 treat it as having any downtime for the purposes of stability
2683 calculation, whereas clients would experience downtime since the
2684 change could take a while to propagate to them. Resolves issue 1035.
2685 - Enable Address Space Layout Randomization (ASLR) and Data Execution
2686 Prevention (DEP) by default on Windows to make it harder for
2687 attackers to exploit vulnerabilities. Patch from John Brooks.
2689 o Minor bugfixes (on 0.2.1.x and earlier):
2690 - Fix a rare crash bug that could occur when a client was configured
2691 with a large number of bridges. Fixes bug 2629; bugfix on
2692 0.2.1.2-alpha. Bugfix by trac user "shitlei".
2693 - Avoid a double mark-for-free warning when failing to attach a
2694 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
2696 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
2697 found by "cypherpunks". This bug was introduced before the first
2698 Tor release, in svn commit r110.
2699 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
2700 don't mention them in the manpage. Fixes bug 2450; issue
2701 spotted by keb and G-Lo.
2702 - Fix a bug in bandwidth history state parsing that could have been
2703 triggered if a future version of Tor ever changed the timing
2704 granularity at which bandwidth history is measured. Bugfix on
2706 - When a relay decides that its DNS is too broken for it to serve
2707 as an exit server, it advertised itself as a non-exit, but
2708 continued to act as an exit. This could create accidental
2709 partitioning opportunities for users. Instead, if a relay is
2710 going to advertise reject *:* as its exit policy, it should
2711 really act with exit policy "reject *:*". Fixes bug 2366.
2712 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
2713 - In the special case where you configure a public exit relay as your
2714 bridge, Tor would be willing to use that exit relay as the last
2715 hop in your circuit as well. Now we fail that circuit instead.
2716 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
2717 - Fix a bug with our locking implementation on Windows that couldn't
2718 correctly detect when a file was already locked. Fixes bug 2504,
2719 bugfix on 0.2.1.6-alpha.
2720 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
2721 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
2723 - Set target port in get_interface_address6() correctly. Bugfix
2724 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
2725 - Directory authorities are now more robust to hops back in time
2726 when calculating router stability. Previously, if a run of uptime
2727 or downtime appeared to be negative, the calculation could give
2728 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
2730 - Fix an assert that got triggered when using the TestingTorNetwork
2731 configuration option and then issuing a GETINFO config-text control
2732 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
2734 o Minor bugfixes (on 0.2.2.x):
2735 - Clients should not weight BadExit nodes as Exits in their node
2736 selection. Similarly, directory authorities should not count BadExit
2737 bandwidth as Exit bandwidth when computing bandwidth-weights.
2738 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
2739 - Correctly clear our dir_read/dir_write history when there is an
2740 error parsing any bw history value from the state file. Bugfix on
2742 - Resolve a bug in verifying signatures of directory objects
2743 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
2744 Fixes bug 2409. Found by "piebeer".
2745 - Bridge authorities no longer crash on SIGHUP when they try to
2746 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
2750 - Log less aggressively about circuit timeout changes, and improve
2751 some other circuit timeout messages. Resolves bug 2004.
2752 - Log a little more clearly about the times at which we're no longer
2753 accepting new connections. Resolves bug 2181.
2754 - Reject attempts at the client side to open connections to private
2755 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
2756 a randomly chosen exit node. Attempts to do so are always
2757 ill-defined, generally prevented by exit policies, and usually
2758 in error. This will also help to detect loops in transparent
2759 proxy configurations. You can disable this feature by setting
2760 "ClientRejectInternalAddresses 0" in your torrc.
2761 - Always treat failure to allocate an RSA key as an unrecoverable
2763 - Update to the March 1 2011 Maxmind GeoLite Country database.
2765 o Minor features (log subsystem):
2766 - Add documentation for configuring logging at different severities in
2767 different log domains. We've had this feature since 0.2.1.1-alpha,
2768 but for some reason it never made it into the manpage. Fixes
2770 - Make it simpler to specify "All log domains except for A and B".
2771 Previously you needed to say "[*,~A,~B]". Now you can just say
2773 - Add a "LogMessageDomains 1" option to include the domains of log
2774 messages along with the messages. Without this, there's no way
2775 to use log domains without reading the source or doing a lot
2778 o Packaging changes:
2779 - Stop shipping the Tor specs files and development proposal documents
2780 in the tarball. They are now in a separate git repository at
2781 git://git.torproject.org/torspec.git
2784 Changes in version 0.2.1.30 - 2011-02-23
2785 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
2786 change is a slight tweak to Tor's TLS handshake that makes relays
2787 and bridges that run this new version reachable from Iran again.
2788 We don't expect this tweak will win the arms race long-term, but it
2789 buys us time until we roll out a better solution.
2792 - Stop sending a CLOCK_SKEW controller status event whenever
2793 we fetch directory information from a relay that has a wrong clock.
2794 Instead, only inform the controller when it's a trusted authority
2795 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
2796 the rest of bug 1074.
2797 - Fix a bounds-checking error that could allow an attacker to
2798 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
2800 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
2801 Tor would ignore their RelayBandwidthBurst setting,
2802 potentially using more bandwidth than expected. Bugfix on
2803 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
2804 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
2805 hidserv" in her torrc. The 'hidserv' argument never controlled
2806 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
2809 - Adjust our TLS Diffie-Hellman parameters to match those used by
2811 - Update to the February 1 2011 Maxmind GeoLite Country database.
2814 - Check for and reject overly long directory certificates and
2815 directory tokens before they have a chance to hit any assertions.
2816 Bugfix on 0.2.1.28. Found by "doorss".
2817 - Bring the logic that gathers routerinfos and assesses the
2818 acceptability of circuits into line. This prevents a Tor OP from
2819 getting locked in a cycle of choosing its local OR as an exit for a
2820 path (due to a .exit request) and then rejecting the circuit because
2821 its OR is not listed yet. It also prevents Tor clients from using an
2822 OR running in the same instance as an exit (due to a .exit request)
2823 if the OR does not meet the same requirements expected of an OR
2824 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
2826 o Packaging changes:
2827 - Stop shipping the Tor specs files and development proposal documents
2828 in the tarball. They are now in a separate git repository at
2829 git://git.torproject.org/torspec.git
2830 - Do not include Git version tags as though they are SVN tags when
2831 generating a tarball from inside a repository that has switched
2832 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
2835 Changes in version 0.2.2.22-alpha - 2011-01-25
2836 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
2837 main other change is a slight tweak to Tor's TLS handshake that makes
2838 relays and bridges that run this new version reachable from Iran again.
2839 We don't expect this tweak will win the arms race long-term, but it
2840 will buy us a bit more time until we roll out a better solution.
2843 - Fix a bounds-checking error that could allow an attacker to
2844 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
2846 - Don't assert when changing from bridge to relay or vice versa
2847 via the controller. The assert happened because we didn't properly
2848 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
2849 bug 2433. Reported by bastik.
2852 - Adjust our TLS Diffie-Hellman parameters to match those used by
2854 - Provide a log message stating which geoip file we're parsing
2855 instead of just stating that we're parsing the geoip file.
2856 Implements ticket 2432.
2859 - Check for and reject overly long directory certificates and
2860 directory tokens before they have a chance to hit any assertions.
2861 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
2864 Changes in version 0.2.2.21-alpha - 2011-01-15
2865 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
2866 continues our recent code security audit work. The main fix resolves
2867 a remote heap overflow vulnerability that can allow remote code
2868 execution (CVE-2011-0427). Other fixes address a variety of assert
2869 and crash bugs, most of which we think are hard to exploit remotely.
2871 o Major bugfixes (security), also included in 0.2.1.29:
2872 - Fix a heap overflow bug where an adversary could cause heap
2873 corruption. This bug probably allows remote code execution
2874 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
2876 - Prevent a denial-of-service attack by disallowing any
2877 zlib-compressed data whose compression factor is implausibly
2878 high. Fixes part of bug 2324; reported by "doorss".
2879 - Zero out a few more keys in memory before freeing them. Fixes
2880 bug 2384 and part of bug 2385. These key instances found by
2881 "cypherpunks", based on Andrew Case's report about being able
2882 to find sensitive data in Tor's memory space if you have enough
2883 permissions. Bugfix on 0.0.2pre9.
2885 o Major bugfixes (crashes), also included in 0.2.1.29:
2886 - Prevent calls to Libevent from inside Libevent log handlers.
2887 This had potential to cause a nasty set of crashes, especially
2888 if running Libevent with debug logging enabled, and running
2889 Tor with a controller watching for low-severity log messages.
2890 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
2891 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
2892 underflow errors there too. Fixes the other part of bug 2324.
2893 - Fix a bug where we would assert if we ever had a
2894 cached-descriptors.new file (or another file read directly into
2895 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
2896 on 0.2.1.25. Found by doorss.
2897 - Fix some potential asserts and parsing issues with grossly
2898 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
2901 o Minor bugfixes (other), also included in 0.2.1.29:
2902 - Fix a bug with handling misformed replies to reverse DNS lookup
2903 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
2904 bug reported by doorss.
2905 - Fix compilation on mingw when a pthreads compatibility library
2906 has been installed. (We don't want to use it, so we shouldn't
2907 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
2908 - Fix a bug where we would declare that we had run out of virtual
2909 addresses when the address space was only half-exhausted. Bugfix
2911 - Correctly handle the case where AutomapHostsOnResolve is set but
2912 no virtual addresses are available. Fixes bug 2328; bugfix on
2913 0.1.2.1-alpha. Bug found by doorss.
2914 - Correctly handle wrapping around when we run out of virtual
2915 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
2917 o Minor features, also included in 0.2.1.29:
2918 - Update to the January 1 2011 Maxmind GeoLite Country database.
2919 - Introduce output size checks on all of our decryption functions.
2921 o Build changes, also included in 0.2.1.29:
2922 - Tor does not build packages correctly with Automake 1.6 and earlier;
2923 added a check to Makefile.am to make sure that we're building with
2924 Automake 1.7 or later.
2925 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
2926 because we built it with a too-old version of automake. Thus that
2927 release broke ./configure --enable-openbsd-malloc, which is popular
2928 among really fast exit relays on Linux.
2930 o Major bugfixes, new in 0.2.2.21-alpha:
2931 - Prevent crash/heap corruption when the cbtnummodes consensus
2932 parameter is set to 0 or large values. Fixes bug 2317; bugfix
2935 o Major features, new in 0.2.2.21-alpha:
2936 - Introduce minimum/maximum values that clients will believe
2937 from the consensus. Now we'll have a better chance to avoid crashes
2938 or worse when a consensus param has a weird value.
2940 o Minor features, new in 0.2.2.21-alpha:
2941 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
2942 used on bridges, and it makes bridge scanning somewhat easier.
2943 - If writing the state file to disk fails, wait up to an hour before
2944 retrying again, rather than trying again each second. Fixes bug
2945 2346; bugfix on Tor 0.1.1.3-alpha.
2946 - Make Libevent log messages get delivered to controllers later,
2947 and not from inside the Libevent log handler. This prevents unsafe
2948 reentrant Libevent calls while still letting the log messages
2950 - Detect platforms that brokenly use a signed size_t, and refuse to
2951 build there. Found and analyzed by doorss and rransom.
2952 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
2955 o Minor bugfixes, new in 0.2.2.21-alpha:
2956 - Handle SOCKS messages longer than 128 bytes long correctly, rather
2957 than waiting forever for them to finish. Fixes bug 2330; bugfix
2958 on 0.2.0.16-alpha. Found by doorss.
2959 - Add assertions to check for overflow in arguments to
2960 base32_encode() and base32_decode(); fix a signed-unsigned
2961 comparison there too. These bugs are not actually reachable in Tor,
2962 but it's good to prevent future errors too. Found by doorss.
2963 - Correctly detect failures to create DNS requests when using Libevent
2964 versions before v2. (Before Libevent 2, we used our own evdns
2965 implementation. Its return values for Libevent's evdns_resolve_*()
2966 functions are not consistent with those from Libevent.) Fixes bug
2967 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
2969 o Documentation, new in 0.2.2.21-alpha:
2970 - Document the default socks host and port (127.0.0.1:9050) for
2974 Changes in version 0.2.1.29 - 2011-01-15
2975 Tor 0.2.1.29 continues our recent code security audit work. The main
2976 fix resolves a remote heap overflow vulnerability that can allow remote
2977 code execution. Other fixes address a variety of assert and crash bugs,
2978 most of which we think are hard to exploit remotely.
2980 o Major bugfixes (security):
2981 - Fix a heap overflow bug where an adversary could cause heap
2982 corruption. This bug probably allows remote code execution
2983 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
2985 - Prevent a denial-of-service attack by disallowing any
2986 zlib-compressed data whose compression factor is implausibly
2987 high. Fixes part of bug 2324; reported by "doorss".
2988 - Zero out a few more keys in memory before freeing them. Fixes
2989 bug 2384 and part of bug 2385. These key instances found by
2990 "cypherpunks", based on Andrew Case's report about being able
2991 to find sensitive data in Tor's memory space if you have enough
2992 permissions. Bugfix on 0.0.2pre9.
2994 o Major bugfixes (crashes):
2995 - Prevent calls to Libevent from inside Libevent log handlers.
2996 This had potential to cause a nasty set of crashes, especially
2997 if running Libevent with debug logging enabled, and running
2998 Tor with a controller watching for low-severity log messages.
2999 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
3000 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
3001 underflow errors there too. Fixes the other part of bug 2324.
3002 - Fix a bug where we would assert if we ever had a
3003 cached-descriptors.new file (or another file read directly into
3004 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
3005 on 0.2.1.25. Found by doorss.
3006 - Fix some potential asserts and parsing issues with grossly
3007 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
3010 o Minor bugfixes (other):
3011 - Fix a bug with handling misformed replies to reverse DNS lookup
3012 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
3013 bug reported by doorss.
3014 - Fix compilation on mingw when a pthreads compatibility library
3015 has been installed. (We don't want to use it, so we shouldn't
3016 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
3017 - Fix a bug where we would declare that we had run out of virtual
3018 addresses when the address space was only half-exhausted. Bugfix
3020 - Correctly handle the case where AutomapHostsOnResolve is set but
3021 no virtual addresses are available. Fixes bug 2328; bugfix on
3022 0.1.2.1-alpha. Bug found by doorss.
3023 - Correctly handle wrapping around to when we run out of virtual
3024 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
3025 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
3026 because we built it with a too-old version of automake. Thus that
3027 release broke ./configure --enable-openbsd-malloc, which is popular
3028 among really fast exit relays on Linux.
3031 - Update to the January 1 2011 Maxmind GeoLite Country database.
3032 - Introduce output size checks on all of our decryption functions.
3035 - Tor does not build packages correctly with Automake 1.6 and earlier;
3036 added a check to Makefile.am to make sure that we're building with
3037 Automake 1.7 or later.
3040 Changes in version 0.2.2.20-alpha - 2010-12-17
3041 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
3042 exploitable bugs. We also fix a variety of other significant bugs,
3043 change the IP address for one of our directory authorities, and update
3044 the minimum version that Tor relays must run to join the network.
3047 - Fix a remotely exploitable bug that could be used to crash instances
3048 of Tor remotely by overflowing on the heap. Remote-code execution
3049 hasn't been confirmed, but can't be ruled out. Everyone should
3050 upgrade. Bugfix on the 0.1.1 series and later.
3051 - Fix a bug that could break accounting on 64-bit systems with large
3052 time_t values, making them hibernate for impossibly long intervals.
3053 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
3054 - Fix a logic error in directory_fetches_from_authorities() that
3055 would cause all _non_-exits refusing single-hop-like circuits
3056 to fetch from authorities, when we wanted to have _exits_ fetch
3057 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
3059 - Fix a stream fairness bug that would cause newer streams on a given
3060 circuit to get preference when reading bytes from the origin or
3061 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
3062 introduced before the first Tor release, in svn revision r152.
3064 o Directory authority changes:
3065 - Change IP address and ports for gabelmoo (v3 directory authority).
3068 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
3069 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
3070 - Fix an off-by-one error in calculating some controller command
3071 argument lengths. Fortunately, this mistake is harmless since
3072 the controller code does redundant NUL termination too. Found by
3073 boboper. Bugfix on 0.1.1.1-alpha.
3074 - Do not dereference NULL if a bridge fails to build its
3075 extra-info descriptor. Found by an anonymous commenter on
3076 Trac. Bugfix on 0.2.2.19-alpha.
3079 - Update to the December 1 2010 Maxmind GeoLite Country database.
3080 - Directory authorities now reject relays running any versions of
3081 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
3082 known bugs that keep RELAY_EARLY cells from working on rendezvous
3083 circuits. Followup to fix for bug 2081.
3084 - Directory authorities now reject relays running any version of Tor
3085 older than 0.2.0.26-rc. That version is the earliest that fetches
3086 current directory information correctly. Fixes bug 2156.
3087 - Report only the top 10 ports in exit-port stats in order not to
3088 exceed the maximum extra-info descriptor length of 50 KB. Implements
3092 Changes in version 0.2.1.28 - 2010-12-17
3093 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
3094 exploitable bugs. We also took this opportunity to change the IP address
3095 for one of our directory authorities, and to update the geoip database
3099 - Fix a remotely exploitable bug that could be used to crash instances
3100 of Tor remotely by overflowing on the heap. Remote-code execution
3101 hasn't been confirmed, but can't be ruled out. Everyone should
3102 upgrade. Bugfix on the 0.1.1 series and later.
3104 o Directory authority changes:
3105 - Change IP address and ports for gabelmoo (v3 directory authority).
3108 - Update to the December 1 2010 Maxmind GeoLite Country database.
3111 Changes in version 0.2.1.27 - 2010-11-23
3112 Yet another OpenSSL security patch broke its compatibility with Tor:
3113 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
3114 also took this opportunity to fix several crash bugs, integrate a new
3115 directory authority, and update the bundled GeoIP database.
3118 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
3119 No longer set the tlsext_host_name extension on server SSL objects;
3120 but continue to set it on client SSL objects. Our goal in setting
3121 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
3122 bugfix on 0.2.1.1-alpha.
3123 - Do not log messages to the controller while shrinking buffer
3124 freelists. Doing so would sometimes make the controller connection
3125 try to allocate a buffer chunk, which would mess up the internals
3126 of the freelist and cause an assertion failure. Fixes bug 1125;
3127 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
3128 - Learn our external IP address when we're a relay or bridge, even if
3129 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
3130 where we introduced bridge relays that don't need to publish to
3131 be useful. Fixes bug 2050.
3132 - Do even more to reject (and not just ignore) annotations on
3133 router descriptors received anywhere but from the cache. Previously
3134 we would ignore such annotations at first, but cache them to disk
3135 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
3136 - When you're using bridges and your network goes away and your
3137 bridges get marked as down, recover when you attempt a new socks
3138 connection (if the network is back), rather than waiting up to an
3139 hour to try fetching new descriptors for your bridges. Bugfix on
3140 0.2.0.3-alpha; fixes bug 1981.
3143 - Move to the November 2010 Maxmind GeoLite country db (rather
3144 than the June 2009 ip-to-country GeoIP db) for our statistics that
3145 count how many users relays are seeing from each country. Now we'll
3146 have more accurate data, especially for many African countries.
3148 o New directory authorities:
3149 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
3153 - Fix an assertion failure that could occur in directory caches or
3154 bridge users when using a very short voting interval on a testing
3155 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
3157 - Enforce multiplicity rules when parsing annotations. Bugfix on
3158 0.2.0.8-alpha. Found by piebeer.
3159 - Allow handshaking OR connections to take a full KeepalivePeriod
3160 seconds to handshake. Previously, we would close them after
3161 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
3162 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
3164 - When building with --enable-gcc-warnings on OpenBSD, disable
3165 warnings in system headers. This makes --enable-gcc-warnings
3166 pass on OpenBSD 4.8.
3169 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
3170 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
3171 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
3172 Servers can start sending this code when enough clients recognize
3173 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
3174 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
3175 Patch from mingw-san.
3178 - Remove the old debian/ directory from the main Tor distribution.
3179 The official Tor-for-debian git repository lives at the URL
3180 https://git.torproject.org/debian/tor.git
3181 - Stop shipping the old doc/website/ directory in the tarball. We
3182 changed the website format in late 2010, and what we shipped in
3183 0.2.1.26 really wasn't that useful anyway.
3186 Changes in version 0.2.2.19-alpha - 2010-11-22
3187 Yet another OpenSSL security patch broke its compatibility with Tor:
3188 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
3191 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
3192 No longer set the tlsext_host_name extension on server SSL objects;
3193 but continue to set it on client SSL objects. Our goal in setting
3194 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
3195 bugfix on 0.2.1.1-alpha.
3198 - Try harder not to exceed the maximum length of 50 KB when writing
3199 statistics to extra-info descriptors. This bug was triggered by very
3200 fast relays reporting exit-port, entry, and dirreq statistics.
3201 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
3202 - Publish a router descriptor even if generating an extra-info
3203 descriptor fails. Previously we would not publish a router
3204 descriptor without an extra-info descriptor; this can cause fast
3205 exit relays collecting exit-port statistics to drop from the
3206 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
3209 Changes in version 0.2.2.18-alpha - 2010-11-16
3210 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
3211 us lately, makes unpublished bridge relays able to detect their IP
3212 address, and fixes a wide variety of other bugs to get us much closer
3213 to a stable release.
3216 - Do even more to reject (and not just ignore) annotations on
3217 router descriptors received anywhere but from the cache. Previously
3218 we would ignore such annotations at first, but cache them to disk
3219 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
3220 - Do not log messages to the controller while shrinking buffer
3221 freelists. Doing so would sometimes make the controller connection
3222 try to allocate a buffer chunk, which would mess up the internals
3223 of the freelist and cause an assertion failure. Fixes bug 1125;
3224 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
3225 - Learn our external IP address when we're a relay or bridge, even if
3226 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
3227 where we introduced bridge relays that don't need to publish to
3228 be useful. Fixes bug 2050.
3229 - Maintain separate TLS contexts and certificates for incoming and
3230 outgoing connections in bridge relays. Previously we would use the
3231 same TLS contexts and certs for incoming and outgoing connections.
3232 Bugfix on 0.2.0.3-alpha; addresses bug 988.
3233 - Maintain separate identity keys for incoming and outgoing TLS
3234 contexts in bridge relays. Previously we would use the same
3235 identity keys for incoming and outgoing TLS contexts. Bugfix on
3236 0.2.0.3-alpha; addresses the other half of bug 988.
3237 - Avoid an assertion failure when we as an authority receive a
3238 duplicate upload of a router descriptor that we already have,
3239 but which we previously considered an obsolete descriptor.
3240 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
3241 - Avoid a crash bug triggered by looking at a dangling pointer while
3242 setting the network status consensus. Found by Robert Ransom.
3243 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
3244 - Fix a logic error where servers that _didn't_ act as exits would
3245 try to keep their server lists more aggressively up to date than
3246 exits, when it was supposed to be the other way around. Bugfix
3249 o Minor bugfixes (on Tor 0.2.1.x and earlier):
3250 - When we're trying to guess whether we know our IP address as
3251 a relay, we would log various ways that we failed to guess
3252 our address, but never log that we ended up guessing it
3253 successfully. Now add a log line to help confused and anxious
3254 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
3255 - Bring the logic that gathers routerinfos and assesses the
3256 acceptability of circuits into line. This prevents a Tor OP from
3257 getting locked in a cycle of choosing its local OR as an exit for a
3258 path (due to a .exit request) and then rejecting the circuit because
3259 its OR is not listed yet. It also prevents Tor clients from using an
3260 OR running in the same instance as an exit (due to a .exit request)
3261 if the OR does not meet the same requirements expected of an OR
3262 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
3263 - Correctly describe errors that occur when generating a TLS object.
3264 Previously we would attribute them to a failure while generating a
3265 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
3267 - Enforce multiplicity rules when parsing annotations. Bugfix on
3268 0.2.0.8-alpha. Found by piebeer.
3269 - Fix warnings that newer versions of autoconf produced during
3270 ./autogen.sh. These warnings appear to be harmless in our case,
3271 but they were extremely verbose. Fixes bug 2020.
3273 o Minor bugfixes (on Tor 0.2.2.x):
3274 - Enable protection of small arrays whenever we build with gcc
3275 hardening features, not only when also building with warnings
3276 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
3279 - Make hidden services work better in private Tor networks by not
3280 requiring any uptime to join the hidden service descriptor
3281 DHT. Implements ticket 2088.
3282 - Rate-limit the "your application is giving Tor only an IP address"
3283 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
3284 - When AllowSingleHopExits is set, print a warning to explain to the
3285 relay operator why most clients are avoiding her relay.
3286 - Update to the November 1 2010 Maxmind GeoLite Country database.
3288 o Code simplifications and refactoring:
3289 - When we fixed bug 1038 we had to put in a restriction not to send
3290 RELAY_EARLY cells on rend circuits. This was necessary as long
3291 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
3292 active. Now remove this obsolete check. Resolves bug 2081.
3293 - Some options used different conventions for uppercasing of acronyms
3294 when comparing manpage and source. Fix those in favor of the
3295 manpage, as it makes sense to capitalize acronyms.
3296 - Remove the torrc.complete file. It hasn't been kept up to date
3297 and users will have better luck checking out the manpage.
3298 - Remove the obsolete "NoPublish" option; it has been flagged
3299 as obsolete and has produced a warning since 0.1.1.18-rc.
3300 - Remove everything related to building the expert bundle for OS X.
3301 It has confused many users, doesn't work right on OS X 10.6,
3302 and is hard to get rid of once installed. Resolves bug 1274.
3305 Changes in version 0.2.2.17-alpha - 2010-09-30
3306 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
3307 to use one-hop circuits (which can put the exit relays at higher risk,
3308 plus unbalance the network); fixes a big bug in bandwidth accounting
3309 for relays that want to limit their monthly bandwidth use; fixes a
3310 big pile of bugs in how clients tolerate temporary network failure;
3311 and makes our adaptive circuit build timeout feature (which improves
3312 client performance if your network is fast while not breaking things
3313 if your network is slow) better handle bad networks.
3316 - Exit relays now try harder to block exit attempts from unknown
3317 relays, to make it harder for people to use them as one-hop proxies
3318 a la tortunnel. Controlled by the refuseunknownexits consensus
3319 parameter (currently enabled), or you can override it on your
3320 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
3322 o Major bugfixes (0.2.1.x and earlier):
3323 - Fix a bug in bandwidth accounting that could make us use twice
3324 the intended bandwidth when our interval start changes due to
3325 daylight saving time. Now we tolerate skew in stored vs computed
3326 interval starts: if the start of the period changes by no more than
3327 50% of the period's duration, we remember bytes that we transferred
3328 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
3329 - Always search the Windows system directory for system DLLs, and
3330 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
3331 - When you're using bridges and your network goes away and your
3332 bridges get marked as down, recover when you attempt a new socks
3333 connection (if the network is back), rather than waiting up to an
3334 hour to try fetching new descriptors for your bridges. Bugfix on
3335 0.2.0.3-alpha; fixes bug 1981.
3337 o Major bugfixes (on 0.2.2.x):
3338 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
3340 - Fix a segfault that could happen when operating a bridge relay with
3341 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
3342 - The consensus bandwidth-weights (used by clients to choose fast
3343 relays) entered an unexpected edge case in September where
3344 Exits were much scarcer than Guards, resulting in bad weight
3345 recommendations. Now we compute them using new constraints that
3346 should succeed in all cases. Also alter directory authorities to
3347 not include the bandwidth-weights line if they fail to produce
3348 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
3349 - When weighting bridges during path selection, we used to trust
3350 the bandwidths they provided in their descriptor, only capping them
3351 at 10MB/s. This turned out to be problematic for two reasons:
3352 Bridges could claim to handle a lot more traffic then they
3353 actually would, thus making more clients pick them and have a
3354 pretty effective DoS attack. The other issue is that new bridges
3355 that might not have a good estimate for their bw capacity yet
3356 would not get used at all unless no other bridges are available
3357 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
3359 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
3360 - Ignore cannibalized circuits when recording circuit build times.
3361 This should provide for a minor performance improvement for hidden
3362 service users using 0.2.2.14-alpha, and should remove two spurious
3363 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
3364 - Simplify the logic that causes us to decide if the network is
3365 unavailable for purposes of recording circuit build times. If we
3366 receive no cells whatsoever for the entire duration of a circuit's
3367 full measured lifetime, the network is probably down. Also ignore
3368 one-hop directory fetching circuit timeouts when calculating our
3369 circuit build times. These changes should hopefully reduce the
3370 cases where we see ridiculous circuit build timeouts for people
3371 with spotty wireless connections. Fixes part of bug 1772; bugfix
3373 - Prevent the circuit build timeout from becoming larger than
3374 the maximum build time we have ever seen. Also, prevent the time
3375 period for measurement circuits from becoming larger than twice that
3376 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
3379 - When we run out of directory information such that we can't build
3380 circuits, but then get enough that we can build circuits, log when
3381 we actually construct a circuit, so the user has a better chance of
3382 knowing what's going on. Fixes bug 1362.
3383 - Be more generous with how much bandwidth we'd use up (with
3384 accounting enabled) before entering "soft hibernation". Previously,
3385 we'd refuse new connections and circuits once we'd used up 95% of
3386 our allotment. Now, we use up 95% of our allotment, AND make sure
3387 that we have no more than 500MB (or 3 hours of expected traffic,
3388 whichever is lower) remaining before we enter soft hibernation.
3389 - If we've configured EntryNodes and our network goes away and/or all
3390 our entrynodes get marked down, optimistically retry them all when
3391 a new socks application request appears. Fixes bug 1882.
3392 - Add some more defensive programming for architectures that can't
3393 handle unaligned integer accesses. We don't know of any actual bugs
3394 right now, but that's the best time to fix them. Fixes bug 1943.
3395 - Support line continuations in the torrc config file. If a line
3396 ends with a single backslash character, the newline is ignored, and
3397 the configuration value is treated as continuing on the next line.
3400 o Minor bugfixes (on 0.2.1.x and earlier):
3401 - For bandwidth accounting, calculate our expected bandwidth rate
3402 based on the time during which we were active and not in
3403 soft-hibernation during the last interval. Previously, we were
3404 also considering the time spent in soft-hibernation. If this
3405 was a long time, we would wind up underestimating our bandwidth
3406 by a lot, and skewing our wakeup time towards the start of the
3407 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
3409 o Minor bugfixes (on 0.2.2.x):
3410 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
3411 which were disabled by the circuit build timeout changes in
3412 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
3413 - Make sure we don't warn about missing bandwidth weights when
3414 choosing bridges or other relays not in the consensus. Bugfix on
3415 0.2.2.10-alpha; fixes bug 1805.
3416 - In our logs, do not double-report signatures from unrecognized
3417 authorities both as "from unknown authority" and "not
3418 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
3421 Changes in version 0.2.2.16-alpha - 2010-09-17
3422 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
3423 evident at exit relays), and also continues to resolve all the little
3424 bugs that have been filling up trac lately.
3426 o Major bugfixes (stream-level fairness):
3427 - When receiving a circuit-level SENDME for a blocked circuit, try
3428 to package cells fairly from all the streams that had previously
3429 been blocked on that circuit. Previously, we had started with the
3430 oldest stream, and allowed each stream to potentially exhaust
3431 the circuit's package window. This gave older streams on any
3432 given circuit priority over newer ones. Fixes bug 1937. Detected
3433 originally by Camilo Viecco. This bug was introduced before the
3434 first Tor release, in svn commit r152: it is the new winner of
3435 the longest-lived bug prize.
3436 - When the exit relay got a circuit-level sendme cell, it started
3437 reading on the exit streams, even if had 500 cells queued in the
3438 circuit queue already, so the circuit queue just grew and grew in
3439 some cases. We fix this by not re-enabling reading on receipt of a
3440 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
3441 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
3443 - Newly created streams were allowed to read cells onto circuits,
3444 even if the circuit's cell queue was blocked and waiting to drain.
3445 This created potential unfairness, as older streams would be
3446 blocked, but newer streams would gladly fill the queue completely.
3447 We add code to detect this situation and prevent any stream from
3448 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
3452 - Update to the September 1 2010 Maxmind GeoLite Country database.
3453 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
3454 not. This would lead to a cookie that is still not group readable.
3455 Closes bug 1843. Suggested by katmagic.
3456 - When logging a rate-limited warning, we now mention how many messages
3457 got suppressed since the last warning.
3458 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
3459 do individual connection-level rate limiting of clients. The torrc
3460 config options with the same names trump the consensus params, if
3461 both are present. Replaces the old "bwconnrate" and "bwconnburst"
3462 consensus params which were broken from 0.2.2.7-alpha through
3463 0.2.2.14-alpha. Closes bug 1947.
3464 - When a router changes IP address or port, authorities now launch
3465 a new reachability test for it. Implements ticket 1899.
3466 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
3467 2 no signature, 4 required" messages about consensus signatures
3468 easier to read, and make sure they get logged at the same severity
3469 as the messages explaining which keys are which. Fixes bug 1290.
3470 - Don't warn when we have a consensus that we can't verify because
3471 of missing certificates, unless those certificates are ones
3472 that we have been trying and failing to download. Fixes bug 1145.
3473 - If you configure your bridge with a known identity fingerprint,
3474 and the bridge authority is unreachable (as it is in at least
3475 one country now), fall back to directly requesting the descriptor
3476 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
3478 - When building with --enable-gcc-warnings on OpenBSD, disable
3479 warnings in system headers. This makes --enable-gcc-warnings
3480 pass on OpenBSD 4.8.
3482 o Minor bugfixes (on 0.2.1.x and earlier):
3483 - Authorities will now attempt to download consensuses if their
3484 own efforts to make a live consensus have failed. This change
3485 means authorities that restart will fetch a valid consensus, and
3486 it means authorities that didn't agree with the current consensus
3487 will still fetch and serve it if it has enough signatures. Bugfix
3488 on 0.2.0.9-alpha; fixes bug 1300.
3489 - Ensure DNS requests launched by "RESOLVE" commands from the
3490 controller respect the __LeaveStreamsUnattached setconf options. The
3491 same goes for requests launched via DNSPort or transparent
3492 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
3493 - Allow handshaking OR connections to take a full KeepalivePeriod
3494 seconds to handshake. Previously, we would close them after
3495 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
3496 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
3498 - Rate-limit "Failed to hand off onionskin" warnings.
3499 - Never relay a cell for a circuit we have already destroyed.
3500 Between marking a circuit as closeable and finally closing it,
3501 it may have been possible for a few queued cells to get relayed,
3502 even though they would have been immediately dropped by the next
3503 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
3504 - Never queue a cell for a circuit that's already been marked
3506 - Never vote for a server as "Running" if we have a descriptor for
3507 it claiming to be hibernating, and that descriptor was published
3508 more recently than our last contact with the server. Bugfix on
3509 0.2.0.3-alpha; fixes bug 911.
3510 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
3513 o Minor bugfixes (on 0.2.2.x):
3514 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
3515 down if a directory fetch fails and you've configured either
3516 bridges or EntryNodes. The intent was to mark the relay as down
3517 _unless_ you're using bridges or EntryNodes, since if you are
3518 then you could quickly run out of entry points.
3519 - Fix the Windows directory-listing code. A bug introduced in
3520 0.2.2.14-alpha could make Windows directory servers forget to load
3521 some of their cached v2 networkstatus files.
3522 - Really allow clients to use relays as bridges. Fixes bug 1776;
3523 bugfix on 0.2.2.15-alpha.
3524 - Demote a warn to info that happens when the CellStatistics option
3525 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
3526 Reported by Moritz Bartl.
3527 - On Windows, build correctly either with or without Unicode support.
3528 This is necessary so that Tor can support fringe platforms like
3529 Windows 98 (which has no Unicode), or Windows CE (which has no
3530 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
3533 - Add a unit test for cross-platform directory-listing code.
3536 Changes in version 0.2.2.15-alpha - 2010-08-18
3537 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
3538 fixes a variety of other bugs that were preventing performance
3539 experiments from moving forward, fixes several bothersome memory leaks,
3540 and generally closes a lot of smaller bugs that have been filling up
3544 - Stop assigning the HSDir flag to relays that disable their
3545 DirPort (and thus will refuse to answer directory requests). This
3546 fix should dramatically improve the reachability of hidden services:
3547 hidden services and hidden service clients pick six HSDir relays
3548 to store and retrieve the hidden service descriptor, and currently
3549 about half of the HSDir relays will refuse to work. Bugfix on
3550 0.2.0.10-alpha; fixes part of bug 1693.
3551 - The PerConnBWRate and Burst config options, along with the
3552 bwconnrate and bwconnburst consensus params, initialized each conn's
3553 token bucket values only when the connection is established. Now we
3554 update them if the config options change, and update them every time
3555 we get a new consensus. Otherwise we can encounter an ugly edge
3556 case where we initialize an OR conn to client-level bandwidth,
3557 but then later the relay joins the consensus and we leave it
3558 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
3559 - Fix a regression that caused Tor to rebind its ports if it receives
3560 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
3563 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
3564 should give us approximately 40-50% more Guard-flagged nodes,
3565 improving the anonymity the Tor network can provide and also
3566 decreasing the dropoff in throughput that relays experience when
3567 they first get the Guard flag.
3568 - Allow enabling or disabling the *Statistics config options while
3572 - Update to the August 1 2010 Maxmind GeoLite Country database.
3573 - Have the controller interface give a more useful message than
3574 "Internal Error" in response to failed GETINFO requests.
3575 - Warn when the same option is provided more than once in a torrc
3576 file, on the command line, or in a single SETCONF statement, and
3577 the option is one that only accepts a single line. Closes bug 1384.
3578 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
3579 Patch from mingw-san.
3580 - Add support for the country code "{??}" in torrc options like
3581 ExcludeNodes, to indicate all routers of unknown country. Closes
3583 - Relays report the number of bytes spent on answering directory
3584 requests in extra-info descriptors similar to {read,write}-history.
3585 Implements enhancement 1790.
3587 o Minor bugfixes (on 0.2.1.x and earlier):
3588 - Complain if PublishServerDescriptor is given multiple arguments that
3589 include 0 or 1. This configuration will be rejected in the future.
3590 Bugfix on 0.2.0.1-alpha; closes bug 1107.
3591 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
3592 Bugfix on 0.2.0.13-alpha; closes bug 928.
3593 - Change "Application request when we're believed to be offline."
3594 notice to "Application request when we haven't used client
3595 functionality lately.", to clarify that it's not an error. Bugfix
3596 on 0.0.9.3; fixes bug 1222.
3597 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
3598 would return "551 Internal error" rather than "552 Unrecognized key
3599 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
3600 - Users can't configure a regular relay to be their bridge. It didn't
3601 work because when Tor fetched the bridge descriptor, it found
3602 that it already had it, and didn't realize that the purpose of the
3603 descriptor had changed. Now we replace routers with a purpose other
3604 than bridge with bridge descriptors when fetching them. Bugfix on
3605 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
3606 refetch the descriptor with router purpose 'general', disabling
3608 - Fix a rare bug in rend_fn unit tests: we would fail a test when
3609 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
3610 on 0.2.0.10-alpha; fixes bug 1808.
3611 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
3612 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
3613 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
3614 Servers can start sending this code when enough clients recognize
3615 it. Also update the spec to reflect this new reason. Bugfix on
3616 0.1.0.1-rc; fixes part of bug 1793.
3617 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
3618 when we switch from being a public relay to a bridge. Otherwise
3619 there will still be clients that see the relay in their consensus,
3620 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
3622 - Instead of giving an assertion failure on an internal mismatch
3623 on estimated freelist size, just log a BUG warning and try later.
3624 Mitigates but does not fix bug 1125.
3625 - Fix an assertion failure that could occur in caches or bridge users
3626 when using a very short voting interval on a testing network.
3627 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
3629 o Minor bugfixes (on 0.2.2.x):
3630 - Alter directory authorities to always consider Exit-flagged nodes
3631 as potential Guard nodes in their votes. The actual decision to
3632 use Exits as Guards is done in the consensus bandwidth weights.
3633 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
3634 - When the controller is reporting the purpose of circuits that
3635 didn't finish building before the circuit build timeout, it was
3636 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
3637 - Our libevent version parsing code couldn't handle versions like
3638 1.4.14b-stable and incorrectly warned the user about using an
3639 old and broken version of libevent. Treat 1.4.14b-stable like
3640 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
3642 - Don't use substitution references like $(VAR:MOD) when
3643 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
3644 '$(:x)' to 'x' rather than the empty string. This bites us in
3645 doc/ when configured with --disable-asciidoc. Bugfix on
3646 0.2.2.9-alpha; fixes bug 1773.
3647 - Remove a spurious hidden service server-side log notice about
3648 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
3650 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
3652 - Correctly report written bytes on linked connections. Found while
3653 implementing 1790. Bugfix on 0.2.2.4-alpha.
3654 - Fix three memory leaks: one in circuit_build_times_parse_state(),
3655 one in dirvote_add_signatures_to_pending_consensus(), and one every
3656 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
3657 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
3659 o Code simplifications and refactoring:
3660 - Take a first step towards making or.h smaller by splitting out
3661 function definitions for all source files in src/or/. Leave
3662 structures and defines in or.h for now.
3663 - Remove a bunch of unused function declarations as well as a block of
3664 #if 0'd code from the unit tests. Closes bug 1824.
3665 - New unit tests for exit-port history statistics; refactored exit
3666 statistics code to be more easily tested.
3667 - Remove the old debian/ directory from the main Tor distribution.
3668 The official Tor-for-debian git repository lives at the URL
3669 https://git.torproject.org/debian/tor.git
3672 Changes in version 0.2.2.14-alpha - 2010-07-12
3673 Tor 0.2.2.14-alpha greatly improves client-side handling of
3674 circuit build timeouts, which are used to estimate speed and improve
3675 performance. We also move to a much better GeoIP database, port Tor to
3676 Windows CE, introduce new compile flags that improve code security,
3677 add an eighth v3 directory authority, and address a lot of more
3681 - Tor directory authorities no longer crash when started with a
3682 cached-microdesc-consensus file in their data directory. Bugfix
3683 on 0.2.2.6-alpha; fixes bug 1532.
3684 - Treat an unset $HOME like an empty $HOME rather than triggering an
3685 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
3686 - Ignore negative and large circuit build timeout values that can
3687 happen during a suspend or hibernate. These values caused various
3688 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
3689 - Alter calculation of Pareto distribution parameter 'Xm' for
3690 Circuit Build Timeout learning to use the weighted average of the
3691 top N=3 modes (because we have three entry guards). Considering
3692 multiple modes should improve the timeout calculation in some cases,
3693 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
3695 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
3696 right censored distribution model. This approach improves over the
3697 synthetic timeout generation approach that was producing insanely
3698 high timeout values. Now we calculate build timeouts using truncated
3699 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
3700 - Do not close circuits that are under construction when they reach
3701 the circuit build timeout. Instead, leave them building (but do not
3702 use them) for up until the time corresponding to the 95th percentile
3703 on the Pareto CDF or 60 seconds, whichever is greater. This is done
3704 to provide better data for the new Pareto model. This percentile
3705 can be controlled by the consensus.
3708 - Move to the June 2010 Maxmind GeoLite country db (rather than the
3709 June 2009 ip-to-country GeoIP db) for our statistics that count
3710 how many users relays are seeing from each country. Now we have
3711 more accurate data for many African countries.
3712 - Port Tor to build and run correctly on Windows CE systems, using
3713 the wcecompat library. Contributed by Valerio Lupi.
3714 - New "--enable-gcc-hardening" ./configure flag (off by default)
3715 to turn on gcc compile time hardening options. It ensures
3716 that signed ints have defined behavior (-fwrapv), enables
3717 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
3718 with canaries (-fstack-protector-all), turns on ASLR protection if
3719 supported by the kernel (-fPIE, -pie), and adds additional security
3720 related warnings. Verified to work on Mac OS X and Debian Lenny.
3721 - New "--enable-linker-hardening" ./configure flag (off by default)
3722 to turn on ELF specific hardening features (relro, now). This does
3723 not work with Mac OS X or any other non-ELF binary format.
3725 o New directory authorities:
3726 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
3730 - New config option "WarnUnsafeSocks 0" disables the warning that
3731 occurs whenever Tor receives a socks handshake using a version of
3732 the socks protocol that can only provide an IP address (rather
3733 than a hostname). Setups that do DNS locally over Tor are fine,
3734 and we shouldn't spam the logs in that case.
3735 - Convert the HACKING file to asciidoc, and add a few new sections
3736 to it, explaining how we use Git, how we make changelogs, and
3737 what should go in a patch.
3738 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
3739 event, to give information on the current rate of circuit timeouts
3740 over our stored history.
3741 - Add ability to disable circuit build time learning via consensus
3742 parameter and via a LearnCircuitBuildTimeout config option. Also
3743 automatically disable circuit build time calculation if we are
3744 either a AuthoritativeDirectory, or if we fail to write our state
3745 file. Fixes bug 1296.
3746 - More gracefully handle corrupt state files, removing asserts
3747 in favor of saving a backup and resetting state.
3748 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
3752 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
3754 - When a2x fails, mention that the user could disable manpages instead
3755 of trying to fix their asciidoc installation.
3756 - Where available, use Libevent 2.0's periodic timers so that our
3757 once-per-second cleanup code gets called even more closely to
3758 once per second than it would otherwise. Fixes bug 943.
3759 - If you run a bridge that listens on multiple IP addresses, and
3760 some user configures a bridge address that uses a different IP
3761 address than your bridge writes in its router descriptor, and the
3762 user doesn't specify an identity key, their Tor would discard the
3763 descriptor because "it isn't one of our configured bridges", and
3764 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
3765 Bugfix on 0.2.0.3-alpha.
3766 - If OpenSSL fails to make a duplicate of a private or public key, log
3767 an error message and try to exit cleanly. May help with debugging
3768 if bug 1209 ever remanifests.
3769 - Save a couple bytes in memory allocation every time we escape
3770 certain characters in a string. Patch from Florian Zumbiehl.
3771 - Make it explicit that we don't cannibalize one-hop circuits. This
3772 happens in the wild, but doesn't turn out to be a problem because
3773 we fortunately don't use those circuits. Many thanks to outofwords
3774 for the initial analysis and to swissknife who confirmed that
3775 two-hop circuits are actually created.
3776 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
3777 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
3778 - Eliminate a case where a circuit build time warning was displayed
3779 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
3782 Changes in version 0.2.1.26 - 2010-05-02
3783 Tor 0.2.1.26 addresses the recent connection and memory overload
3784 problems we've been seeing on relays, especially relays with their
3785 DirPort open. If your relay has been crashing, or you turned it off
3786 because it used too many resources, give this release a try.
3788 This release also fixes yet another instance of broken OpenSSL libraries
3789 that was causing some relays to drop out of the consensus.
3792 - Teach relays to defend themselves from connection overload. Relays
3793 now close idle circuits early if it looks like they were intended
3794 for directory fetches. Relays are also more aggressive about closing
3795 TLS connections that have no circuits on them. Such circuits are
3796 unlikely to be re-used, and tens of thousands of them were piling
3797 up at the fast relays, causing the relays to run out of sockets
3798 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
3799 their directory fetches over TLS).
3800 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
3801 that claim to be earlier than 0.9.8m, but which have in reality
3802 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
3803 behavior. Possible fix for some cases of bug 1346.
3804 - Directory mirrors were fetching relay descriptors only from v2
3805 directory authorities, rather than v3 authorities like they should.
3806 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
3807 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
3810 - Finally get rid of the deprecated and now harmful notion of "clique
3811 mode", where directory authorities maintain TLS connections to
3815 - In the util/threads test, no longer free the test_mutex before all
3816 worker threads have finished. Bugfix on 0.2.1.6-alpha.
3817 - The master thread could starve the worker threads quite badly on
3818 certain systems, causing them to run only partially in the allowed
3819 window. This resulted in test failures. Now the master thread sleeps
3820 occasionally for a few microseconds while the two worker-threads
3821 compete for the mutex. Bugfix on 0.2.0.1-alpha.
3824 Changes in version 0.2.2.13-alpha - 2010-04-24
3825 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
3826 problems we've been seeing on relays, especially relays with their
3827 DirPort open. If your relay has been crashing, or you turned it off
3828 because it used too many resources, give this release a try.
3831 - Teach relays to defend themselves from connection overload. Relays
3832 now close idle circuits early if it looks like they were intended
3833 for directory fetches. Relays are also more aggressive about closing
3834 TLS connections that have no circuits on them. Such circuits are
3835 unlikely to be re-used, and tens of thousands of them were piling
3836 up at the fast relays, causing the relays to run out of sockets
3837 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
3838 their directory fetches over TLS).
3841 - Finally get rid of the deprecated and now harmful notion of "clique
3842 mode", where directory authorities maintain TLS connections to
3844 - Directory authorities now do an immediate reachability check as soon
3845 as they hear about a new relay. This change should slightly reduce
3846 the time between setting up a relay and getting listed as running
3847 in the consensus. It should also improve the time between setting
3848 up a bridge and seeing use by bridge users.
3849 - Directory authorities no longer launch a TLS connection to every
3850 relay as they startup. Now that we have 2k+ descriptors cached,
3851 the resulting network hiccup is becoming a burden. Besides,
3852 authorities already avoid voting about Running for the first half
3853 hour of their uptime.
3856 Changes in version 0.2.2.12-alpha - 2010-04-20
3857 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
3858 handle and vote on descriptors. It was causing relays to drop out of
3862 - Many relays have been falling out of the consensus lately because
3863 not enough authorities know about their descriptor for them to get
3864 a majority of votes. When we deprecated the v2 directory protocol,
3865 we got rid of the only way that v3 authorities can hear from each
3866 other about other descriptors. Now authorities examine every v3
3867 vote for new descriptors, and fetch them from that authority. Bugfix
3869 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
3870 and a warning in or.h related to bandwidth_weight_rule_t that
3871 prevented clean compile on OS X. Fixes bug 1363; bugfix on
3873 - Fix a segfault on relays when DirReqStatistics is enabled
3874 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
3878 - Demote a confusing TLS warning that relay operators might get when
3879 someone tries to talk to their OrPort. It is neither the operator's
3880 fault nor can they do anything about it. Fixes bug 1364; bugfix
3884 Changes in version 0.2.2.11-alpha - 2010-04-15
3885 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
3886 libraries that was causing some relays to drop out of the consensus.
3889 - Directory mirrors were fetching relay descriptors only from v2
3890 directory authorities, rather than v3 authorities like they should.
3891 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
3892 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
3893 - Fix a parsing error that made every possible value of
3894 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
3895 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
3896 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
3897 about the option without breaking older ones.
3898 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
3899 that claim to be earlier than 0.9.8m, but which have in reality
3900 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
3901 behavior. Possible fix for some cases of bug 1346.
3904 - Experiment with a more aggressive approach to preventing clients
3905 from making one-hop exit streams. Exit relays who want to try it
3906 out can set "RefuseUnknownExits 1" in their torrc, and then look
3907 for "Attempt by %s to open a stream" log messages. Let us know
3909 - Add support for statically linking zlib by specifying
3910 --enable-static-zlib, to go with our support for statically linking
3911 openssl and libevent. Resolves bug 1358.
3914 - Fix a segfault that happens whenever a Tor client that is using
3915 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
3917 - When we cleaned up the contrib/tor-exit-notice.html file, we left
3918 out the first line. Fixes bug 1295.
3919 - When building the manpage from a tarball, we required asciidoc, but
3920 the asciidoc -> roff/html conversion was already done for the
3921 tarball. Make 'make' complain only when we need asciidoc (either
3922 because we're compiling directly from git, or because we altered
3923 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
3924 - When none of the directory authorities vote on any params, Tor
3925 segfaulted when trying to make the consensus from the votes. We
3926 didn't trigger the bug in practice, because authorities do include
3927 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
3930 - In the util/threads test, no longer free the test_mutex before all
3931 worker threads have finished. Bugfix on 0.2.1.6-alpha.
3932 - The master thread could starve the worker threads quite badly on
3933 certain systems, causing them to run only partially in the allowed
3934 window. This resulted in test failures. Now the master thread sleeps
3935 occasionally for a few microseconds while the two worker-threads
3936 compete for the mutex. Bugfix on 0.2.0.1-alpha.
3939 Changes in version 0.2.2.10-alpha - 2010-03-07
3940 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
3941 could prevent relays from guessing their IP address correctly. It also
3942 starts the groundwork for another client-side performance boost, since
3943 currently we're not making efficient use of relays that have both the
3944 Guard flag and the Exit flag.
3947 - Fix a regression from our patch for bug 1244 that caused relays
3948 to guess their IP address incorrectly if they didn't set Address
3949 in their torrc and/or their address fails to resolve. Bugfix on
3950 0.2.2.9-alpha; fixes bug 1269.
3952 o Major features (performance):
3953 - Directory authorities now compute consensus weightings that instruct
3954 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
3955 and no flag. Clients that use these weightings will distribute
3956 network load more evenly across these different relay types. The
3957 weightings are in the consensus so we can change them globally in
3958 the future. Extra thanks to "outofwords" for finding some nasty
3959 security bugs in the first implementation of this feature.
3961 o Minor features (performance):
3962 - Always perform router selections using weighted relay bandwidth,
3963 even if we don't need a high capacity circuit at the time. Non-fast
3964 circuits now only differ from fast ones in that they can use relays
3965 not marked with the Fast flag. This "feature" could turn out to
3966 be a horrible bug; we should investigate more before it goes into
3970 - Allow disabling building of the manpages. Skipping the manpage
3971 speeds up the build considerably.
3973 o Minor bugfixes (on 0.2.2.x):
3974 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
3975 Bugfix on 0.2.2.9-alpha.
3976 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
3977 config option. Bugfix on 0.2.2.7-alpha.
3978 - Ship the asciidoc-helper file in the tarball, so that people can
3979 build from source if they want to, and touching the .1.txt files
3980 doesn't break the build. Bugfix on 0.2.2.9-alpha.
3982 o Minor bugfixes (on 0.2.1.x or earlier):
3983 - Fix a dereference-then-NULL-check sequence when publishing
3984 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
3986 - Fix another dereference-then-NULL-check sequence. Bugfix on
3987 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
3988 - Make sure we treat potentially not NUL-terminated strings correctly.
3989 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
3991 o Code simplifications and refactoring:
3992 - Fix some urls in the exit notice file and make it XHTML1.1 strict
3993 compliant. Based on a patch from Christian Kujau.
3994 - Don't use sed in asciidoc-helper anymore.
3995 - Make the build process fail if asciidoc cannot be found and
3996 building with asciidoc isn't disabled.
3999 Changes in version 0.2.2.9-alpha - 2010-02-22
4000 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
4001 location of a directory authority, and cleans up a bunch of small bugs.
4003 o Directory authority changes:
4004 - Change IP address for dannenberg (v3 directory authority), and
4005 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
4006 service directory authority) from the list.
4009 - Make Tor work again on the latest OS X: when deciding whether to
4010 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4011 version at run-time, not compile time. We need to do this because
4012 Apple doesn't update its dev-tools headers when it updates its
4013 libraries in a security patch.
4014 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4015 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4016 a memory leak when requesting a hidden service descriptor we've
4017 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4019 - Authorities could be tricked into giving out the Exit flag to relays
4020 that didn't allow exiting to any ports. This bug could screw
4021 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
4022 1238. Bug discovered by Martin Kowalczyk.
4023 - When freeing a session key, zero it out completely. We only zeroed
4024 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4025 patched by ekir. Fixes bug 1254.
4028 - Fix static compilation by listing the openssl libraries in the right
4029 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
4030 - Resume handling .exit hostnames in a special way: originally we
4031 stripped the .exit part and used the requested exit relay. In
4032 0.2.2.1-alpha we stopped treating them in any special way, meaning
4033 if you use a .exit address then Tor will pass it on to the exit
4034 relay. Now we reject the .exit stream outright, since that behavior
4035 might be more expected by the user. Found and diagnosed by Scott
4036 Bennett and Downie on or-talk.
4037 - Don't spam the controller with events when we have no file
4038 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
4039 for log messages was already solved from bug 748.)
4040 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
4042 - Make the DNSPort option work with libevent 2.x. Don't alter the
4043 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
4044 - Emit a GUARD DROPPED controller event for a case we missed.
4045 - Make more fields in the controller protocol case-insensitive, since
4046 control-spec.txt said they were.
4047 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4048 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4049 - Fix a spec conformance issue: the network-status-version token
4050 must be the first token in a v3 consensus or vote. Discovered by
4051 parakeep. Bugfix on 0.2.0.3-alpha.
4053 o Code simplifications and refactoring:
4054 - Generate our manpage and HTML documentation using Asciidoc. This
4055 change should make it easier to maintain the documentation, and
4057 - Remove the --enable-iphone option. According to reports from Marco
4058 Bonetti, Tor builds fine without any special tweaking on recent
4059 iPhone SDK versions.
4060 - Removed some unnecessary files from the source distribution. The
4061 AUTHORS file has now been merged into the people page on the
4062 website. The roadmaps and design doc can now be found in the
4063 projects directory in svn.
4064 - Enabled various circuit build timeout constants to be controlled
4065 by consensus parameters. Also set better defaults for these
4066 parameters based on experimentation on broadband and simulated
4070 - The 'EXTENDCIRCUIT' control port command can now be used with
4071 a circ id of 0 and no path. This feature will cause Tor to build
4072 a new 'fast' general purpose circuit using its own path selection
4074 - Added a BUILDTIMEOUT_SET controller event to describe changes
4075 to the circuit build timeout.
4076 - Future-proof the controller protocol a bit by ignoring keyword
4077 arguments we do not recognize.
4078 - Expand homedirs passed to tor-checkkey. This should silence a
4079 coverity complaint about passing a user-supplied string into
4080 open() without checking it.
4083 Changes in version 0.2.1.25 - 2010-03-16
4084 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
4085 prevent relays from guessing their IP address correctly. It also fixes
4086 several minor potential security bugs.
4089 - Fix a regression from our patch for bug 1244 that caused relays
4090 to guess their IP address incorrectly if they didn't set Address
4091 in their torrc and/or their address fails to resolve. Bugfix on
4092 0.2.1.23; fixes bug 1269.
4093 - When freeing a session key, zero it out completely. We only zeroed
4094 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4095 patched by ekir. Fixes bug 1254.
4098 - Fix a dereference-then-NULL-check sequence when publishing
4099 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4101 - Fix another dereference-then-NULL-check sequence. Bugfix on
4102 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4103 - Make sure we treat potentially not NUL-terminated strings correctly.
4104 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4108 Changes in version 0.2.1.24 - 2010-02-21
4109 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
4113 - Work correctly out-of-the-box with even more vendor-patched versions
4114 of OpenSSL. In particular, make it so Debian and OS X don't need
4115 customized patches to run/build.
4118 Changes in version 0.2.1.23 - 2010-02-13
4119 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
4120 again on the latest OS X, and updates the location of a directory
4123 o Major bugfixes (performance):
4124 - We were selecting our guards uniformly at random, and then weighting
4125 which of our guards we'd use uniformly at random. This imbalance
4126 meant that Tor clients were severely limited on throughput (and
4127 probably latency too) by the first hop in their circuit. Now we
4128 select guards weighted by currently advertised bandwidth. We also
4129 automatically discard guards picked using the old algorithm. Fixes
4130 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
4133 - Make Tor work again on the latest OS X: when deciding whether to
4134 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4135 version at run-time, not compile time. We need to do this because
4136 Apple doesn't update its dev-tools headers when it updates its
4137 libraries in a security patch.
4138 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4139 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4140 a memory leak when requesting a hidden service descriptor we've
4141 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4144 o Directory authority changes:
4145 - Change IP address for dannenberg (v3 directory authority), and
4146 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
4147 service directory authority) from the list.
4150 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4151 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4154 - Avoid a mad rush at the beginning of each month when each client
4155 rotates half of its guards. Instead we spread the rotation out
4156 throughout the month, but we still avoid leaving a precise timestamp
4157 in the state file about when we first picked the guard. Improves
4158 over the behavior introduced in 0.1.2.17.
4161 Changes in version 0.2.2.8-alpha - 2010-01-26
4162 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
4163 causing bridge relays to disappear. If you're running a bridge,
4167 - Fix a memory corruption bug on bridges that occured during the
4168 inclusion of stats data in extra-info descriptors. Also fix the
4169 interface for geoip_get_bridge_stats* to prevent similar bugs in
4170 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
4171 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
4174 - Ignore OutboundBindAddress when connecting to localhost.
4175 Connections to localhost need to come _from_ localhost, or else
4176 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
4180 Changes in version 0.2.2.7-alpha - 2010-01-19
4181 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
4182 as laying the groundwork for further relay-side performance fixes. It
4183 also starts cleaning up client behavior with respect to the EntryNodes,
4184 ExitNodes, and StrictNodes config options.
4186 This release also rotates two directory authority keys, due to a
4187 security breach of some of the Torproject servers.
4189 o Directory authority changes:
4190 - Rotate keys (both v3 identity and relay identity) for moria1
4193 o Major features (performance):
4194 - We were selecting our guards uniformly at random, and then weighting
4195 which of our guards we'd use uniformly at random. This imbalance
4196 meant that Tor clients were severely limited on throughput (and
4197 probably latency too) by the first hop in their circuit. Now we
4198 select guards weighted by currently advertised bandwidth. We also
4199 automatically discard guards picked using the old algorithm. Fixes
4200 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
4201 - When choosing which cells to relay first, relays can now favor
4202 circuits that have been quiet recently, to provide lower latency
4203 for low-volume circuits. By default, relays enable or disable this
4204 feature based on a setting in the consensus. You can override
4205 this default by using the new "CircuitPriorityHalflife" config
4206 option. Design and code by Ian Goldberg, Can Tang, and Chris
4208 - Add separate per-conn write limiting to go with the per-conn read
4209 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
4210 but never per-conn write limits.
4211 - New consensus params "bwconnrate" and "bwconnburst" to let us
4212 rate-limit client connections as they enter the network. It's
4213 controlled in the consensus so we can turn it on and off for
4214 experiments. It's starting out off. Based on proposal 163.
4216 o Major features (relay selection options):
4217 - Switch to a StrictNodes config option, rather than the previous
4218 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
4219 "StrictExcludeNodes" option.
4220 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
4221 change during a config reload, mark and discard all our origin
4222 circuits. This fix should address edge cases where we change the
4223 config options and but then choose a circuit that we created before
4225 - If EntryNodes or ExitNodes are set, be more willing to use an
4226 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
4228 - Make EntryNodes config option much more aggressive even when
4229 StrictNodes is not set. Before it would prepend your requested
4230 entrynodes to your list of guard nodes, but feel free to use others
4231 after that. Now it chooses only from your EntryNodes if any of
4232 those are available, and only falls back to others if a) they're
4233 all down and b) StrictNodes is not set.
4234 - Now we refresh your entry guards from EntryNodes at each consensus
4235 fetch -- rather than just at startup and then they slowly rot as
4236 the network changes.
4239 - Stop bridge directory authorities from answering dbg-stability.txt
4240 directory queries, which would let people fetch a list of all
4241 bridge identities they track. Bugfix on 0.2.1.6-alpha.
4244 - Log a notice when we get a new control connection. Now it's easier
4245 for security-conscious users to recognize when a local application
4246 is knocking on their controller door. Suggested by bug 1196.
4247 - New config option "CircuitStreamTimeout" to override our internal
4248 timeout schedule for how many seconds until we detach a stream from
4249 a circuit and try a new circuit. If your network is particularly
4250 slow, you might want to set this to a number like 60.
4251 - New controller command "getinfo config-text". It returns the
4252 contents that Tor would write if you send it a SAVECONF command,
4253 so the controller can write the file to disk itself.
4254 - New options for SafeLogging to allow scrubbing only log messages
4255 generated while acting as a relay.
4256 - Ship the bridges spec file in the tarball too.
4257 - Avoid a mad rush at the beginning of each month when each client
4258 rotates half of its guards. Instead we spread the rotation out
4259 throughout the month, but we still avoid leaving a precise timestamp
4260 in the state file about when we first picked the guard. Improves
4261 over the behavior introduced in 0.1.2.17.
4263 o Minor bugfixes (compiling):
4264 - Fix compilation on OS X 10.3, which has a stub mlockall() but
4265 hides it. Bugfix on 0.2.2.6-alpha.
4266 - Fix compilation on Solaris by removing support for the
4267 DisableAllSwap config option. Solaris doesn't have an rlimit for
4268 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
4271 o Minor bugfixes (crashes):
4272 - Do not segfault when writing buffer stats when we haven't observed
4273 a single circuit to report about. Found by Fabian Lanze. Bugfix on
4275 - If we're in the pathological case where there's no exit bandwidth
4276 but there is non-exit bandwidth, or no guard bandwidth but there
4277 is non-guard bandwidth, don't crash during path selection. Bugfix
4279 - Fix an impossible-to-actually-trigger buffer overflow in relay
4280 descriptor generation. Bugfix on 0.1.0.15.
4282 o Minor bugfixes (privacy):
4283 - Fix an instance where a Tor directory mirror might accidentally
4284 log the IP address of a misbehaving Tor client. Bugfix on
4286 - Don't list Windows capabilities in relay descriptors. We never made
4287 use of them, and maybe it's a bad idea to publish them. Bugfix
4290 o Minor bugfixes (other):
4291 - Resolve an edge case in path weighting that could make us misweight
4292 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
4293 - Fix statistics on client numbers by country as seen by bridges that
4294 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
4295 intervals instead of variable 12-to-48-hour intervals.
4296 - After we free an internal connection structure, overwrite it
4297 with a different memory value than we use for overwriting a freed
4298 internal circuit structure. Should help with debugging. Suggested
4300 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
4304 - Remove the HSAuthorityRecordStats option that version 0 hidden
4305 service authorities could have used to track statistics of overall
4306 hidden service usage.
4309 Changes in version 0.2.1.22 - 2010-01-19
4310 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
4311 authorities -- it would tell you its whole history of bridge descriptors
4312 if you make the right directory request. This stable update also
4313 rotates two of the seven v3 directory authority keys and locations.
4315 o Directory authority changes:
4316 - Rotate keys (both v3 identity and relay identity) for moria1
4320 - Stop bridge directory authorities from answering dbg-stability.txt
4321 directory queries, which would let people fetch a list of all
4322 bridge identities they track. Bugfix on 0.2.1.6-alpha.
4325 Changes in version 0.2.1.21 - 2009-12-21
4326 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
4327 library. If you use Tor on Linux / Unix and you're getting SSL
4328 renegotiation errors, upgrading should help. We also recommend an
4329 upgrade if you're an exit relay.
4332 - Work around a security feature in OpenSSL 0.9.8l that prevents our
4333 handshake from working unless we explicitly tell OpenSSL that we
4334 are using SSL renegotiation safely. We are, of course, but OpenSSL
4335 0.9.8l won't work unless we say we are.
4336 - Avoid crashing if the client is trying to upload many bytes and the
4337 circuit gets torn down at the same time, or if the flip side
4338 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
4341 - Do not refuse to learn about authority certs and v2 networkstatus
4342 documents that are older than the latest consensus. This bug might
4343 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
4344 Spotted and fixed by xmux.
4345 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
4346 trigger platform-specific option misparsing case found by Coverity
4348 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
4349 trigger assert. Fixes bug 1173.
4352 Changes in version 0.2.2.6-alpha - 2009-11-19
4353 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
4354 support for the new lower-footprint "microdescriptor" directory design,
4355 future-proofing our consensus format against new hash functions or
4356 other changes, and an Android port. It also makes Tor compatible with
4357 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
4360 - Directory authorities can now create, vote on, and serve multiple
4361 parallel formats of directory data as part of their voting process.
4362 Partially implements Proposal 162: "Publish the consensus in
4364 - Directory authorities can now agree on and publish small summaries
4365 of router information that clients can use in place of regular
4366 server descriptors. This transition will eventually allow clients
4367 to use far less bandwidth for downloading information about the
4368 network. Begins the implementation of Proposal 158: "Clients
4369 download consensus + microdescriptors".
4370 - The directory voting system is now extensible to use multiple hash
4371 algorithms for signatures and resource selection. Newer formats
4372 are signed with SHA256, with a possibility for moving to a better
4373 hash algorithm in the future.
4374 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
4375 current and future memory pages via mlockall(). On supported
4376 platforms (modern Linux and probably BSD but not Windows or OS X),
4377 this should effectively disable any and all attempts to page out
4378 memory. This option requires that you start your Tor as root --
4379 if you use DisableAllSwap, please consider using the User option
4380 to properly reduce the privileges of your Tor.
4381 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
4382 to help Tor build correctly for Android phones.
4385 - Work around a security feature in OpenSSL 0.9.8l that prevents our
4386 handshake from working unless we explicitly tell OpenSSL that we
4387 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
4388 won't work unless we say we are.
4391 - Fix a crash bug when trying to initialize the evdns module in
4392 Libevent 2. Bugfix on 0.2.1.16-rc.
4393 - Stop logging at severity 'warn' when some other Tor client tries
4394 to establish a circuit with us using weak DH keys. It's a protocol
4395 violation, but that doesn't mean ordinary users need to hear about
4396 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
4397 - Do not refuse to learn about authority certs and v2 networkstatus
4398 documents that are older than the latest consensus. This bug might
4399 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
4400 Spotted and fixed by xmux.
4401 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
4402 - If all authorities restart at once right before a consensus vote,
4403 nobody will vote about "Running", and clients will get a consensus
4404 with no usable relays. Instead, authorities refuse to build a
4405 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
4406 - If your relay can't keep up with the number of incoming create
4407 cells, it would log one warning per failure into your logs. Limit
4408 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
4409 - Bridges now use "reject *:*" as their default exit policy. Bugfix
4410 on 0.2.0.3-alpha; fixes bug 1113.
4411 - Fix a memory leak on directory authorities during voting that was
4412 introduced in 0.2.2.1-alpha. Found via valgrind.
4415 Changes in version 0.2.1.20 - 2009-10-15
4416 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
4417 services at once, prepares for more performance improvements, and
4418 fixes a bunch of smaller bugs.
4420 The Windows and OS X bundles also include a more recent Vidalia,
4421 and switch from Privoxy to Polipo.
4423 The OS X installers are now drag and drop. It's best to un-install
4424 Tor/Vidalia and then install this new bundle, rather than upgrade. If
4425 you want to upgrade, you'll need to update the paths for Tor and Polipo
4426 in the Vidalia Settings window.
4429 - Send circuit or stream sendme cells when our window has decreased
4430 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
4431 by Karsten when testing the "reduce circuit window" performance
4432 patch. Bugfix on the 54th commit on Tor -- from July 2002,
4433 before the release of Tor 0.0.0. This is the new winner of the
4435 - Fix a remotely triggerable memory leak when a consensus document
4436 contains more than one signature from the same voter. Bugfix on
4438 - Avoid segfault in rare cases when finishing an introduction circuit
4439 as a client and finding out that we don't have an introduction key
4440 for it. Fixes bug 1073. Reported by Aaron Swartz.
4443 - Tor now reads the "circwindow" parameter out of the consensus,
4444 and uses that value for its circuit package window rather than the
4445 default of 1000 cells. Begins the implementation of proposal 168.
4447 o New directory authorities:
4448 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
4450 - Move moria1 and tonga to alternate IP addresses.
4453 - Fix a signed/unsigned compile warning in 0.2.1.19.
4454 - Fix possible segmentation fault on directory authorities. Bugfix on
4456 - Fix an extremely rare infinite recursion bug that could occur if
4457 we tried to log a message after shutting down the log subsystem.
4458 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
4459 - Fix an obscure bug where hidden services on 64-bit big-endian
4460 systems might mis-read the timestamp in v3 introduce cells, and
4461 refuse to connect back to the client. Discovered by "rotor".
4462 Bugfix on 0.2.1.6-alpha.
4463 - We were triggering a CLOCK_SKEW controller status event whenever
4464 we connect via the v2 connection protocol to any relay that has
4465 a wrong clock. Instead, we should only inform the controller when
4466 it's a trusted authority that claims our clock is wrong. Bugfix
4467 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
4468 - We were telling the controller about CHECKING_REACHABILITY and
4469 REACHABILITY_FAILED status events whenever we launch a testing
4470 circuit or notice that one has failed. Instead, only tell the
4471 controller when we want to inform the user of overall success or
4472 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
4474 - Don't warn when we're using a circuit that ends with a node
4475 excluded in ExcludeExitNodes, but the circuit is not used to access
4476 the outside world. This should help fix bug 1090. Bugfix on
4478 - Work around a small memory leak in some versions of OpenSSL that
4479 stopped the memory used by the hostname TLS extension from being
4483 - Add a "getinfo status/accepted-server-descriptor" controller
4484 command, which is the recommended way for controllers to learn
4485 whether our server descriptor has been successfully received by at
4486 least on directory authority. Un-recommend good-server-descriptor
4487 getinfo and status events until we have a better design for them.
4490 Changes in version 0.2.2.5-alpha - 2009-10-11
4491 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
4494 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
4496 o Directory authorities:
4497 - Temporarily (just for this release) move dizum to an alternate
4501 Changes in version 0.2.2.4-alpha - 2009-10-10
4502 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
4503 introduces a new unit test framework, shifts directry authority
4504 addresses around to reduce the impact from recent blocking events,
4505 and fixes a few smaller bugs.
4508 - Fix several more asserts in the circuit_build_times code, for
4509 example one that causes Tor to fail to start once we have
4510 accumulated 5000 build times in the state file. Bugfixes on
4511 0.2.2.2-alpha; fixes bug 1108.
4513 o New directory authorities:
4514 - Move moria1 and Tonga to alternate IP addresses.
4517 - Log SSL state transitions at debug level during handshake, and
4518 include SSL states in error messages. This may help debug future
4519 SSL handshake issues.
4520 - Add a new "Handshake" log domain for activities that happen
4521 during the TLS handshake.
4522 - Revert to the "June 3 2009" ip-to-country file. The September one
4523 seems to have removed most US IP addresses.
4524 - Directory authorities now reject Tor relays with versions less than
4525 0.1.2.14. This step cuts out four relays from the current network,
4526 none of which are very big.
4529 - Fix a couple of smaller issues with gathering statistics. Bugfixes
4531 - Fix two memory leaks in the error case of
4532 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
4533 - Don't count one-hop circuits when we're estimating how long it
4534 takes circuits to build on average. Otherwise we'll set our circuit
4535 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
4536 - Directory authorities no longer change their opinion of, or vote on,
4537 whether a router is Running, unless they have themselves been
4538 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
4541 o Code simplifications and refactoring:
4542 - Revise our unit tests to use the "tinytest" framework, so we
4543 can run tests in their own processes, have smarter setup/teardown
4544 code, and so on. The unit test code has moved to its own
4545 subdirectory, and has been split into multiple modules.
4548 Changes in version 0.2.2.3-alpha - 2009-09-23
4549 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
4552 - Fix an overzealous assert in our new circuit build timeout code.
4553 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
4556 - If the networkstatus consensus tells us that we should use a
4557 negative circuit package window, ignore it. Otherwise we'll
4558 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
4561 Changes in version 0.2.2.2-alpha - 2009-09-21
4562 Tor 0.2.2.2-alpha introduces our latest performance improvement for
4563 clients: Tor tracks the average time it takes to build a circuit, and
4564 avoids using circuits that take too long to build. For fast connections,
4565 this feature can cut your expected latency in half. For slow or flaky
4566 connections, it could ruin your Tor experience. Let us know if it does!
4569 - Tor now tracks how long it takes to build client-side circuits
4570 over time, and adapts its timeout to local network performance.
4571 Since a circuit that takes a long time to build will also provide
4572 bad performance, we get significant latency improvements by
4573 discarding the slowest 20% of circuits. Specifically, Tor creates
4574 circuits more aggressively than usual until it has enough data
4575 points for a good timeout estimate. Implements proposal 151.
4576 We are especially looking for reports (good and bad) from users with
4577 both EDGE and broadband connections that can move from broadband
4578 to EDGE and find out if the build-time data in the .tor/state gets
4579 reset without loss of Tor usability. You should also see a notice
4580 log message telling you that Tor has reset its timeout.
4581 - Directory authorities can now vote on arbitary integer values as
4582 part of the consensus process. This is designed to help set
4583 network-wide parameters. Implements proposal 167.
4584 - Tor now reads the "circwindow" parameter out of the consensus,
4585 and uses that value for its circuit package window rather than the
4586 default of 1000 cells. Begins the implementation of proposal 168.
4589 - Fix a remotely triggerable memory leak when a consensus document
4590 contains more than one signature from the same voter. Bugfix on
4594 - Fix an extremely rare infinite recursion bug that could occur if
4595 we tried to log a message after shutting down the log subsystem.
4596 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
4597 - Fix parsing for memory or time units given without a space between
4598 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
4599 - A networkstatus vote must contain exactly one signature. Spec
4600 conformance issue. Bugfix on 0.2.0.3-alpha.
4601 - Fix an obscure bug where hidden services on 64-bit big-endian
4602 systems might mis-read the timestamp in v3 introduce cells, and
4603 refuse to connect back to the client. Discovered by "rotor".
4604 Bugfix on 0.2.1.6-alpha.
4605 - We were triggering a CLOCK_SKEW controller status event whenever
4606 we connect via the v2 connection protocol to any relay that has
4607 a wrong clock. Instead, we should only inform the controller when
4608 it's a trusted authority that claims our clock is wrong. Bugfix
4609 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
4610 - We were telling the controller about CHECKING_REACHABILITY and
4611 REACHABILITY_FAILED status events whenever we launch a testing
4612 circuit or notice that one has failed. Instead, only tell the
4613 controller when we want to inform the user of overall success or
4614 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
4616 - Don't warn when we're using a circuit that ends with a node
4617 excluded in ExcludeExitNodes, but the circuit is not used to access
4618 the outside world. This should help fix bug 1090, but more problems
4619 remain. Bugfix on 0.2.1.6-alpha.
4620 - Work around a small memory leak in some versions of OpenSSL that
4621 stopped the memory used by the hostname TLS extension from being
4623 - Make our 'torify' script more portable; if we have only one of
4624 'torsocks' or 'tsocks' installed, don't complain to the user;
4625 and explain our warning about tsocks better.
4628 - Add a "getinfo status/accepted-server-descriptor" controller
4629 command, which is the recommended way for controllers to learn
4630 whether our server descriptor has been successfully received by at
4631 least on directory authority. Un-recommend good-server-descriptor
4632 getinfo and status events until we have a better design for them.
4633 - Update to the "September 4 2009" ip-to-country file.
4636 Changes in version 0.2.2.1-alpha - 2009-08-26
4637 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
4638 Tor clients to bootstrap on networks where only port 80 is reachable,
4639 makes it more straightforward to support hardware crypto accelerators,
4640 and starts the groundwork for gathering stats safely at relays.
4643 - Start the process of disabling ".exit" address notation, since it
4644 can be used for a variety of esoteric application-level attacks
4645 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
4648 o New directory authorities:
4649 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
4653 - New AccelName and AccelDir options add support for dynamic OpenSSL
4654 hardware crypto acceleration engines.
4655 - Tor now supports tunneling all of its outgoing connections over
4656 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
4657 configuration options. Code by Christopher Davis.
4660 - Send circuit or stream sendme cells when our window has decreased
4661 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
4662 by Karsten when testing the "reduce circuit window" performance
4663 patch. Bugfix on the 54th commit on Tor -- from July 2002,
4664 before the release of Tor 0.0.0. This is the new winner of the
4667 o New options for gathering stats safely:
4668 - Directory mirrors that set "DirReqStatistics 1" write statistics
4669 about directory requests to disk every 24 hours. As compared to the
4670 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
4671 1) stats are written to disk exactly every 24 hours; 2) estimated
4672 shares of v2 and v3 requests are determined as mean values, not at
4673 the end of a measurement period; 3) unresolved requests are listed
4674 with country code '??'; 4) directories also measure download times.
4675 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
4676 number of exit streams and transferred bytes per port to disk every
4678 - Relays that set "CellStatistics 1" write statistics on how long
4679 cells spend in their circuit queues to disk every 24 hours.
4680 - Entry nodes that set "EntryStatistics 1" write statistics on the
4681 rough number and origins of connecting clients to disk every 24
4683 - Relays that write any of the above statistics to disk and set
4684 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
4685 their extra-info documents.
4688 - New --digests command-line switch to output the digests of the
4689 source files Tor was built with.
4690 - The "torify" script now uses torsocks where available.
4691 - The memarea code now uses a sentinel value at the end of each area
4692 to make sure nothing writes beyond the end of an area. This might
4693 help debug some conceivable causes of bug 930.
4694 - Time and memory units in the configuration file can now be set to
4695 fractional units. For example, "2.5 GB" is now a valid value for
4697 - Certain Tor clients (such as those behind check.torproject.org) may
4698 want to fetch the consensus in an extra early manner. To enable this
4699 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
4700 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
4701 as only certain clients who must have this information sooner should
4703 - Instead of adding the svn revision to the Tor version string, report
4704 the git commit (when we're building from a git checkout).
4707 - If any of the v3 certs we download are unparseable, we should
4708 actually notice the failure so we don't retry indefinitely. Bugfix
4709 on 0.2.0.x; reported by "rotator".
4710 - If the cached cert file is unparseable, warn but don't exit.
4711 - Fix possible segmentation fault on directory authorities. Bugfix on
4713 - When Tor fails to parse a descriptor of any kind, dump it to disk.
4714 Might help diagnosing bug 1051.
4716 o Deprecated and removed features:
4717 - The controller no longer accepts the old obsolete "addr-mappings/"
4718 or "unregistered-servers-" GETINFO values.
4719 - Hidden services no longer publish version 0 descriptors, and clients
4720 do not request or use version 0 descriptors. However, the old hidden
4721 service authorities still accept and serve version 0 descriptors
4722 when contacted by older hidden services/clients.
4723 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
4724 always on; using them is necessary for correct forward-compatible
4726 - Remove support for .noconnect style addresses. Nobody was using
4727 them, and they provided another avenue for detecting Tor users
4728 via application-level web tricks.
4730 o Packaging changes:
4731 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
4732 installer bundles. See
4733 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
4734 for details of what's new in Vidalia 0.2.3.
4735 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
4736 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
4737 configuration file, rather than the old Privoxy.
4738 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
4739 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
4740 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
4741 better compatibility with OS X 10.6, aka Snow Leopard.
4742 - OS X Vidalia Bundle: The multi-package installer is now replaced
4743 by a simple drag and drop to the /Applications folder. This change
4744 occurred with the upgrade to Vidalia 0.2.3.
4747 Changes in version 0.2.1.19 - 2009-07-28
4748 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
4749 services on Tor 0.2.1.3-alpha through 0.2.1.18.
4752 - Make accessing hidden services on 0.2.1.x work right again.
4753 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
4754 part of patch provided by "optimist".
4757 - When a relay/bridge is writing out its identity key fingerprint to
4758 the "fingerprint" file and to its logs, write it without spaces. Now
4759 it will look like the fingerprints in our bridges documentation,
4760 and confuse fewer users.
4763 - Relays no longer publish a new server descriptor if they change
4764 their MaxAdvertisedBandwidth config option but it doesn't end up
4765 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
4766 fixes bug 1026. Patch from Sebastian.
4767 - Avoid leaking memory every time we get a create cell but we have
4768 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
4769 fixes bug 1034. Reported by BarkerJr.
4772 Changes in version 0.2.1.18 - 2009-07-24
4773 Tor 0.2.1.18 lays the foundations for performance improvements,
4774 adds status events to help users diagnose bootstrap problems, adds
4775 optional authentication/authorization for hidden services, fixes a
4776 variety of potential anonymity problems, and includes a huge pile of
4777 other features and bug fixes.
4780 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
4783 Changes in version 0.2.1.17-rc - 2009-07-07
4784 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
4785 candidate for the 0.2.1.x series. It lays the groundwork for further
4786 client performance improvements, and also fixes a big bug with directory
4787 authorities that were causing them to assign Guard and Stable flags
4790 The Windows bundles also finally include the geoip database that we
4791 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
4792 should actually install Torbutton rather than giving you a cryptic
4793 failure message (oops).
4796 - Clients now use the bandwidth values in the consensus, rather than
4797 the bandwidth values in each relay descriptor. This approach opens
4798 the door to more accurate bandwidth estimates once the directory
4799 authorities start doing active measurements. Implements more of
4803 - When Tor clients restart after 1-5 days, they discard all their
4804 cached descriptors as too old, but they still use the cached
4805 consensus document. This approach is good for robustness, but
4806 bad for performance: since they don't know any bandwidths, they
4807 end up choosing at random rather than weighting their choice by
4808 speed. Fixed by the above feature of putting bandwidths in the
4809 consensus. Bugfix on 0.2.0.x.
4810 - Directory authorities were neglecting to mark relays down in their
4811 internal histories if the relays fall off the routerlist without
4812 ever being found unreachable. So there were relays in the histories
4813 that haven't been seen for eight months, and are listed as being
4814 up for eight months. This wreaked havoc on the "median wfu"
4815 and "median mtbf" calculations, in turn making Guard and Stable
4816 flags very wrong, hurting network performance. Fixes bugs 696 and
4817 969. Bugfix on 0.2.0.6-alpha.
4820 - Serve the DirPortFrontPage page even when we have been approaching
4821 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
4822 - The control port would close the connection before flushing long
4823 replies, such as the network consensus, if a QUIT command was issued
4824 before the reply had completed. Now, the control port flushes all
4825 pending replies before closing the connection. Also fixed a spurious
4826 warning when a QUIT command is issued after a malformed or rejected
4827 AUTHENTICATE command, but before the connection was closed. Patch
4828 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
4829 - When we can't find an intro key for a v2 hidden service descriptor,
4830 fall back to the v0 hidden service descriptor and log a bug message.
4831 Workaround for bug 1024.
4832 - Fix a log message that did not respect the SafeLogging option.
4836 - If we're a relay and we change our IP address, be more verbose
4837 about the reason that made us change. Should help track down
4838 further bugs for relays on dynamic IP addresses.
4841 Changes in version 0.2.0.35 - 2009-06-24
4843 - Avoid crashing in the presence of certain malformed descriptors.
4844 Found by lark, and by automated fuzzing.
4845 - Fix an edge case where a malicious exit relay could convince a
4846 controller that the client's DNS question resolves to an internal IP
4847 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
4850 - Finally fix the bug where dynamic-IP relays disappear when their
4851 IP address changes: directory mirrors were mistakenly telling
4852 them their old address if they asked via begin_dir, so they
4853 never got an accurate answer about their new address, so they
4854 just vanished after a day. For belt-and-suspenders, relays that
4855 don't set Address in their config now avoid using begin_dir for
4856 all direct connections. Should fix bugs 827, 883, and 900.
4857 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
4858 that would occur on some exit nodes when DNS failures and timeouts
4859 occurred in certain patterns. Fix for bug 957.
4862 - When starting with a cache over a few days old, do not leak
4863 memory for the obsolete router descriptors in it. Bugfix on
4864 0.2.0.33; fixes bug 672.
4865 - Hidden service clients didn't use a cached service descriptor that
4866 was older than 15 minutes, but wouldn't fetch a new one either,
4867 because there was already one in the cache. Now, fetch a v2
4868 descriptor unless the same descriptor was added to the cache within
4869 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
4872 Changes in version 0.2.1.16-rc - 2009-06-20
4873 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
4874 a bunch of minor bugs.
4877 - Fix an edge case where a malicious exit relay could convince a
4878 controller that the client's DNS question resolves to an internal IP
4879 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
4881 o Major performance improvements (on 0.2.0.x):
4882 - Disable and refactor some debugging checks that forced a linear scan
4883 over the whole server-side DNS cache. These accounted for over 50%
4884 of CPU time on a relatively busy exit node's gprof profile. Found
4886 - Disable some debugging checks that appeared in exit node profile
4890 - Update to the "June 3 2009" ip-to-country file.
4891 - Do not have tor-resolve automatically refuse all .onion addresses;
4892 if AutomapHostsOnResolve is set in your torrc, this will work fine.
4894 o Minor bugfixes (on 0.2.0.x):
4895 - Log correct error messages for DNS-related network errors on
4897 - Fix a race condition that could cause crashes or memory corruption
4898 when running as a server with a controller listening for log
4900 - Avoid crashing when we have a policy specified in a DirPolicy or
4901 SocksPolicy or ReachableAddresses option with ports set on it,
4902 and we re-load the policy. May fix bug 996.
4903 - Hidden service clients didn't use a cached service descriptor that
4904 was older than 15 minutes, but wouldn't fetch a new one either,
4905 because there was already one in the cache. Now, fetch a v2
4906 descriptor unless the same descriptor was added to the cache within
4907 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
4909 o Minor bugfixes (on 0.2.1.x):
4910 - Don't warn users about low port and hibernation mix when they
4911 provide a *ListenAddress directive to fix that. Bugfix on
4913 - When switching back and forth between bridge mode, do not start
4914 gathering GeoIP data until two hours have passed.
4915 - Do not complain that the user has requested an excluded node as
4916 an exit when the node is not really an exit. This could happen
4917 because the circuit was for testing, or an introduction point.
4921 Changes in version 0.2.1.15-rc - 2009-05-25
4922 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
4923 series. It fixes a major bug on fast exit relays, as well as a variety
4926 o Major bugfixes (on 0.2.0.x):
4927 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
4928 that would occur on some exit nodes when DNS failures and timeouts
4929 occurred in certain patterns. Fix for bug 957.
4931 o Minor bugfixes (on 0.2.0.x):
4932 - Actually return -1 in the error case for read_bandwidth_usage().
4933 Harmless bug, since we currently don't care about the return value
4934 anywhere. Bugfix on 0.2.0.9-alpha.
4935 - Provide a more useful log message if bug 977 (related to buffer
4936 freelists) ever reappears, and do not crash right away.
4937 - Fix an assertion failure on 64-bit platforms when we allocated
4938 memory right up to the end of a memarea, then realigned the memory
4939 one step beyond the end. Fixes a possible cause of bug 930.
4940 - Protect the count of open sockets with a mutex, so we can't
4941 corrupt it when two threads are closing or opening sockets at once.
4942 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
4943 - Don't allow a bridge to publish its router descriptor to a
4944 non-bridge directory authority. Fixes part of bug 932.
4945 - When we change to or from being a bridge, reset our counts of
4946 client usage by country. Fixes bug 932.
4947 - Fix a bug that made stream bandwidth get misreported to the
4949 - Stop using malloc_usable_size() to use more area than we had
4950 actually allocated: it was safe, but made valgrind really unhappy.
4951 - Fix a memory leak when v3 directory authorities load their keys
4952 and cert from disk. Bugfix on 0.2.0.1-alpha.
4954 o Minor bugfixes (on 0.2.1.x):
4955 - Fix use of freed memory when deciding to mark a non-addable
4956 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
4959 Changes in version 0.2.1.14-rc - 2009-04-12
4960 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
4961 series. It begins fixing some major performance problems, and also
4962 finally addresses the bug that was causing relays on dynamic IP
4963 addresses to fall out of the directory.
4966 - Clients replace entry guards that were chosen more than a few months
4967 ago. This change should significantly improve client performance,
4968 especially once more people upgrade, since relays that have been
4969 a guard for a long time are currently overloaded.
4971 o Major bugfixes (on 0.2.0):
4972 - Finally fix the bug where dynamic-IP relays disappear when their
4973 IP address changes: directory mirrors were mistakenly telling
4974 them their old address if they asked via begin_dir, so they
4975 never got an accurate answer about their new address, so they
4976 just vanished after a day. For belt-and-suspenders, relays that
4977 don't set Address in their config now avoid using begin_dir for
4978 all direct connections. Should fix bugs 827, 883, and 900.
4979 - Relays were falling out of the networkstatus consensus for
4980 part of a day if they changed their local config but the
4981 authorities discarded their new descriptor as "not sufficiently
4982 different". Now directory authorities accept a descriptor as changed
4983 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
4985 - Avoid crashing in the presence of certain malformed descriptors.
4986 Found by lark, and by automated fuzzing.
4989 - When generating circuit events with verbose nicknames for
4990 controllers, try harder to look up nicknames for routers on a
4991 circuit. (Previously, we would look in the router descriptors we had
4992 for nicknames, but not in the consensus.) Partial fix for bug 941.
4993 - If the bridge config line doesn't specify a port, assume 443.
4994 This makes bridge lines a bit smaller and easier for users to
4996 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
4997 bytes (aka 20KB/s), to match our documentation. Also update
4998 directory authorities so they always assign the Fast flag to relays
4999 with 20KB/s of capacity. Now people running relays won't suddenly
5000 find themselves not seeing any use, if the network gets faster
5002 - Update to the "April 3 2009" ip-to-country file.
5005 - Avoid trying to print raw memory to the logs when we decide to
5006 give up on downloading a given relay descriptor. Bugfix on
5008 - In tor-resolve, when the Tor client to use is specified by
5009 <hostname>:<port>, actually use the specified port rather than
5010 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
5011 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
5012 - When starting with a cache over a few days old, do not leak
5013 memory for the obsolete router descriptors in it. Bugfix on
5015 - Avoid double-free on list of successfully uploaded hidden
5016 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
5017 - Change memarea_strndup() implementation to work even when
5018 duplicating a string at the end of a page. This bug was
5019 harmless for now, but could have meant crashes later. Fix by
5020 lark. Bugfix on 0.2.1.1-alpha.
5021 - Limit uploaded directory documents to be 16M rather than 500K.
5022 The directory authorities were refusing v3 consensus votes from
5023 other authorities, since the votes are now 504K. Fixes bug 959;
5024 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
5025 - Directory authorities should never send a 503 "busy" response to
5026 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
5030 Changes in version 0.2.1.13-alpha - 2009-03-09
5031 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
5032 cleanups. We're finally getting close to a release candidate.
5035 - Correctly update the list of which countries we exclude as
5036 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
5037 lark. Bugfix on 0.2.1.6-alpha.
5039 o Minor bugfixes (on 0.2.0.x and earlier):
5040 - Automatically detect MacOSX versions earlier than 10.4.0, and
5041 disable kqueue from inside Tor when running with these versions.
5042 We previously did this from the startup script, but that was no
5043 help to people who didn't use the startup script. Resolves bug 863.
5044 - When we had picked an exit node for a connection, but marked it as
5045 "optional", and it turned out we had no onion key for the exit,
5046 stop wanting that exit and try again. This situation may not
5047 be possible now, but will probably become feasible with proposal
5048 158. Spotted by rovv. Fixes another case of bug 752.
5049 - Clients no longer cache certificates for authorities they do not
5050 recognize. Bugfix on 0.2.0.9-alpha.
5051 - When we can't transmit a DNS request due to a network error, retry
5052 it after a while, and eventually transmit a failing response to
5053 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
5054 - If the controller claimed responsibility for a stream, but that
5055 stream never finished making its connection, it would live
5056 forever in circuit_wait state. Now we close it after SocksTimeout
5057 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
5058 - Drop begin cells to a hidden service if they come from the middle
5059 of a circuit. Patch from lark.
5060 - When we erroneously receive two EXTEND cells for the same circuit
5061 ID on the same connection, drop the second. Patch from lark.
5062 - Fix a crash that occurs on exit nodes when a nameserver request
5063 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
5064 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
5066 - Do not assume that a stack-allocated character array will be
5067 64-bit aligned on platforms that demand that uint64_t access is
5068 aligned. Possible fix for bug 604.
5069 - Parse dates and IPv4 addresses in a locale- and libc-independent
5070 manner, to avoid platform-dependent behavior on malformed input.
5071 - Build correctly when configured to build outside the main source
5072 path. Patch from Michael Gold.
5073 - We were already rejecting relay begin cells with destination port
5074 of 0. Now also reject extend cells with destination port or address
5075 of 0. Suggested by lark.
5077 o Minor bugfixes (on 0.2.1.x):
5078 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
5079 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
5080 - If we're an exit node, scrub the IP address to which we are exiting
5081 in the logs. Bugfix on 0.2.1.8-alpha.
5084 - On Linux, use the prctl call to re-enable core dumps when the user
5086 - New controller event NEWCONSENSUS that lists the networkstatus
5087 lines for every recommended relay. Now controllers like Torflow
5088 can keep up-to-date on which relays they should be using.
5089 - Update to the "February 26 2009" ip-to-country file.
5092 Changes in version 0.2.0.34 - 2009-02-08
5093 Tor 0.2.0.34 features several more security-related fixes. You should
5094 upgrade, especially if you run an exit relay (remote crash) or a
5095 directory authority (remote infinite loop), or you're on an older
5096 (pre-XP) or not-recently-patched Windows (remote exploit).
5098 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
5099 have many known flaws, and nobody should be using them. You should
5100 upgrade. If you're using a Linux or BSD and its packages are obsolete,
5101 stop using those packages and upgrade anyway.
5104 - Fix an infinite-loop bug on handling corrupt votes under certain
5105 circumstances. Bugfix on 0.2.0.8-alpha.
5106 - Fix a temporary DoS vulnerability that could be performed by
5107 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
5108 - Avoid a potential crash on exit nodes when processing malformed
5109 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
5110 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
5111 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
5114 - Fix compilation on systems where time_t is a 64-bit integer.
5115 Patch from Matthias Drochner.
5116 - Don't consider expiring already-closed client connections. Fixes
5117 bug 893. Bugfix on 0.0.2pre20.
5120 Changes in version 0.2.1.12-alpha - 2009-02-08
5121 Tor 0.2.1.12-alpha features several more security-related fixes. You
5122 should upgrade, especially if you run an exit relay (remote crash) or
5123 a directory authority (remote infinite loop), or you're on an older
5124 (pre-XP) or not-recently-patched Windows (remote exploit). It also
5125 includes a big pile of minor bugfixes and cleanups.
5128 - Fix an infinite-loop bug on handling corrupt votes under certain
5129 circumstances. Bugfix on 0.2.0.8-alpha.
5130 - Fix a temporary DoS vulnerability that could be performed by
5131 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
5132 - Avoid a potential crash on exit nodes when processing malformed
5133 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
5136 - Let controllers actually ask for the "clients_seen" event for
5137 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
5138 reported by Matt Edman.
5139 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
5141 - Fix a bug in address parsing that was preventing bridges or hidden
5142 service targets from being at IPv6 addresses.
5143 - Solve a bug that kept hardware crypto acceleration from getting
5144 enabled when accounting was turned on. Fixes bug 907. Bugfix on
5146 - Remove a bash-ism from configure.in to build properly on non-Linux
5147 platforms. Bugfix on 0.2.1.1-alpha.
5148 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
5149 headers. Bugfix on 0.2.0.10-alpha.
5150 - Don't consider expiring already-closed client connections. Fixes
5151 bug 893. Bugfix on 0.0.2pre20.
5152 - Fix another interesting corner-case of bug 891 spotted by rovv:
5153 Previously, if two hosts had different amounts of clock drift, and
5154 one of them created a new connection with just the wrong timing,
5155 the other might decide to deprecate the new connection erroneously.
5156 Bugfix on 0.1.1.13-alpha.
5157 - Resolve a very rare crash bug that could occur when the user forced
5158 a nameserver reconfiguration during the middle of a nameserver
5159 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
5160 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
5161 Bugfix on 0.2.1.7-alpha.
5162 - If we're using bridges and our network goes away, be more willing
5163 to forgive our bridges and try again when we get an application
5164 request. Bugfix on 0.2.0.x.
5167 - Support platforms where time_t is 64 bits long. (Congratulations,
5168 NetBSD!) Patch from Matthias Drochner.
5169 - Add a 'getinfo status/clients-seen' controller command, in case
5170 controllers want to hear clients_seen events but connect late.
5173 - Disable GCC's strict alias optimization by default, to avoid the
5174 likelihood of its introducing subtle bugs whenever our code violates
5175 the letter of C99's alias rules.
5178 Changes in version 0.2.0.33 - 2009-01-21
5179 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
5180 useful to users. It also finally fixes a bug where a relay or client
5181 that's been off for many days would take a long time to bootstrap.
5183 This update also fixes an important security-related bug reported by
5184 Ilja van Sprundel. You should upgrade. (We'll send out more details
5185 about the bug once people have had some time to upgrade.)
5188 - Fix a heap-corruption bug that may be remotely triggerable on
5189 some platforms. Reported by Ilja van Sprundel.
5192 - When a stream at an exit relay is in state "resolving" or
5193 "connecting" and it receives an "end" relay cell, the exit relay
5194 would silently ignore the end cell and not close the stream. If
5195 the client never closes the circuit, then the exit relay never
5196 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
5198 - When sending CREATED cells back for a given circuit, use a 64-bit
5199 connection ID to find the right connection, rather than an addr:port
5200 combination. Now that we can have multiple OR connections between
5201 the same ORs, it is no longer possible to use addr:port to uniquely
5202 identify a connection.
5203 - Bridge relays that had DirPort set to 0 would stop fetching
5204 descriptors shortly after startup, and then briefly resume
5205 after a new bandwidth test and/or after publishing a new bridge
5206 descriptor. Bridge users that try to bootstrap from them would
5207 get a recent networkstatus but would get descriptors from up to
5208 18 hours earlier, meaning most of the descriptors were obsolete
5209 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
5210 - Prevent bridge relays from serving their 'extrainfo' document
5211 to anybody who asks, now that extrainfo docs include potentially
5212 sensitive aggregated client geoip summaries. Bugfix on
5214 - If the cached networkstatus consensus is more than five days old,
5215 discard it rather than trying to use it. In theory it could be
5216 useful because it lists alternate directory mirrors, but in practice
5217 it just means we spend many minutes trying directory mirrors that
5218 are long gone from the network. Also discard router descriptors as
5219 we load them if they are more than five days old, since the onion
5220 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
5223 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
5224 could make gcc generate non-functional binary search code. Bugfix
5226 - Build correctly on platforms without socklen_t.
5227 - Compile without warnings on solaris.
5228 - Avoid potential crash on internal error during signature collection.
5229 Fixes bug 864. Patch from rovv.
5230 - Correct handling of possible malformed authority signing key
5231 certificates with internal signature types. Fixes bug 880.
5232 Bugfix on 0.2.0.3-alpha.
5233 - Fix a hard-to-trigger resource leak when logging credential status.
5235 - When we can't initialize DNS because the network is down, do not
5236 automatically stop Tor from starting. Instead, we retry failed
5237 dns_init() every 10 minutes, and change the exit policy to reject
5238 *:* until one succeeds. Fixes bug 691.
5239 - Use 64 bits instead of 32 bits for connection identifiers used with
5240 the controller protocol, to greatly reduce risk of identifier reuse.
5241 - When we're choosing an exit node for a circuit, and we have
5242 no pending streams, choose a good general exit rather than one that
5243 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
5244 - Fix another case of assuming, when a specific exit is requested,
5245 that we know more than the user about what hosts it allows.
5246 Fixes one case of bug 752. Patch from rovv.
5247 - Clip the MaxCircuitDirtiness config option to a minimum of 10
5248 seconds. Warn the user if lower values are given in the
5249 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
5250 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
5251 user if lower values are given in the configuration. Bugfix on
5252 0.1.1.17-rc. Patch by Sebastian.
5253 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
5254 the cache because we already had a v0 descriptor with the same ID.
5255 Bugfix on 0.2.0.18-alpha.
5256 - Fix a race condition when freeing keys shared between main thread
5257 and CPU workers that could result in a memory leak. Bugfix on
5258 0.1.0.1-rc. Fixes bug 889.
5259 - Send a valid END cell back when a client tries to connect to a
5260 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
5261 840. Patch from rovv.
5262 - Check which hops rendezvous stream cells are associated with to
5263 prevent possible guess-the-streamid injection attacks from
5264 intermediate hops. Fixes another case of bug 446. Based on patch
5266 - If a broken client asks a non-exit router to connect somewhere,
5267 do not even do the DNS lookup before rejecting the connection.
5268 Fixes another case of bug 619. Patch from rovv.
5269 - When a relay gets a create cell it can't decrypt (e.g. because it's
5270 using the wrong onion key), we were dropping it and letting the
5271 client time out. Now actually answer with a destroy cell. Fixes
5272 bug 904. Bugfix on 0.0.2pre8.
5274 o Minor bugfixes (hidden services):
5275 - Do not throw away existing introduction points on SIGHUP. Bugfix on
5276 0.0.6pre1. Patch by Karsten. Fixes bug 874.
5279 - Report the case where all signatures in a detached set are rejected
5280 differently than the case where there is an error handling the
5282 - When we realize that another process has modified our cached
5283 descriptors, print out a more useful error message rather than
5284 triggering an assertion. Fixes bug 885. Patch from Karsten.
5285 - Implement the 0x20 hack to better resist DNS poisoning: set the
5286 case on outgoing DNS requests randomly, and reject responses that do
5287 not match the case correctly. This logic can be disabled with the
5288 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
5289 of servers that do not reliably preserve case in replies. See
5290 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
5292 - Check DNS replies for more matching fields to better resist DNS
5294 - Never use OpenSSL compression: it wastes RAM and CPU trying to
5295 compress cells, which are basically all encrypted, compressed, or
5299 Changes in version 0.2.1.11-alpha - 2009-01-20
5300 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
5301 week it will take a long time to bootstrap again" bug. It also fixes
5302 an important security-related bug reported by Ilja van Sprundel. You
5303 should upgrade. (We'll send out more details about the bug once people
5304 have had some time to upgrade.)
5307 - Fix a heap-corruption bug that may be remotely triggerable on
5308 some platforms. Reported by Ilja van Sprundel.
5311 - Discard router descriptors as we load them if they are more than
5312 five days old. Otherwise if Tor is off for a long time and then
5313 starts with cached descriptors, it will try to use the onion
5314 keys in those obsolete descriptors when building circuits. Bugfix
5315 on 0.2.0.x. Fixes bug 887.
5318 - Try to make sure that the version of Libevent we're running with
5319 is binary-compatible with the one we built with. May address bug
5321 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
5322 for bug 905. Bugfix on 0.2.1.7-alpha.
5323 - Add a new --enable-local-appdata configuration switch to change
5324 the default location of the datadir on win32 from APPDATA to
5325 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
5326 entirely. Patch from coderman.
5329 - Make outbound DNS packets respect the OutboundBindAddress setting.
5330 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
5331 - When our circuit fails at the first hop (e.g. we get a destroy
5332 cell back), avoid using that OR connection anymore, and also
5333 tell all the one-hop directory requests waiting for it that they
5334 should fail. Bugfix on 0.2.1.3-alpha.
5335 - In the torify(1) manpage, mention that tsocks will leak your
5339 Changes in version 0.2.1.10-alpha - 2009-01-06
5340 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
5341 would make the bridge relay not so useful if it had DirPort set to 0,
5342 and one that could let an attacker learn a little bit of information
5343 about the bridge's users), and a bug that would cause your Tor relay
5344 to ignore a circuit create request it can't decrypt (rather than reply
5345 with an error). It also fixes a wide variety of other bugs.
5348 - If the cached networkstatus consensus is more than five days old,
5349 discard it rather than trying to use it. In theory it could
5350 be useful because it lists alternate directory mirrors, but in
5351 practice it just means we spend many minutes trying directory
5352 mirrors that are long gone from the network. Helps bug 887 a bit;
5354 - Bridge relays that had DirPort set to 0 would stop fetching
5355 descriptors shortly after startup, and then briefly resume
5356 after a new bandwidth test and/or after publishing a new bridge
5357 descriptor. Bridge users that try to bootstrap from them would
5358 get a recent networkstatus but would get descriptors from up to
5359 18 hours earlier, meaning most of the descriptors were obsolete
5360 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
5361 - Prevent bridge relays from serving their 'extrainfo' document
5362 to anybody who asks, now that extrainfo docs include potentially
5363 sensitive aggregated client geoip summaries. Bugfix on
5367 - New controller event "clients_seen" to report a geoip-based summary
5368 of which countries we've seen clients from recently. Now controllers
5369 like Vidalia can show bridge operators that they're actually making
5371 - Build correctly against versions of OpenSSL 0.9.8 or later built
5372 without support for deprecated functions.
5373 - Update to the "December 19 2008" ip-to-country file.
5375 o Minor bugfixes (on 0.2.0.x):
5376 - Authorities now vote for the Stable flag for any router whose
5377 weighted MTBF is at least 5 days, regardless of the mean MTBF.
5378 - Do not remove routers as too old if we do not have any consensus
5379 document. Bugfix on 0.2.0.7-alpha.
5380 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
5381 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
5382 - When an exit relay resolves a stream address to a local IP address,
5383 do not just keep retrying that same exit relay over and
5384 over. Instead, just close the stream. Addresses bug 872. Bugfix
5385 on 0.2.0.32. Patch from rovv.
5386 - If a hidden service sends us an END cell, do not consider
5387 retrying the connection; just close it. Patch from rovv.
5388 - When we made bridge authorities stop serving bridge descriptors over
5389 unencrypted links, we also broke DirPort reachability testing for
5390 bridges. So bridges with a non-zero DirPort were printing spurious
5391 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
5392 - When a relay gets a create cell it can't decrypt (e.g. because it's
5393 using the wrong onion key), we were dropping it and letting the
5394 client time out. Now actually answer with a destroy cell. Fixes
5395 bug 904. Bugfix on 0.0.2pre8.
5396 - Squeeze 2-5% out of client performance (according to oprofile) by
5397 improving the implementation of some policy-manipulation functions.
5399 o Minor bugfixes (on 0.2.1.x):
5400 - Make get_interface_address() function work properly again; stop
5401 guessing the wrong parts of our address as our address.
5402 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
5403 send on that circuit. Otherwise we might violate the proposal-110
5404 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
5406 - When we're sending non-EXTEND cells to the first hop in a circuit,
5407 for example to use an encrypted directory connection, we don't need
5408 to use RELAY_EARLY cells: the first hop knows what kind of cell
5409 it is, and nobody else can even see the cell type. Conserving
5410 RELAY_EARLY cells makes it easier to cannibalize circuits like
5412 - Stop logging nameserver addresses in reverse order.
5413 - If we are retrying a directory download slowly over and over, do
5414 not automatically give up after the 254th failure. Bugfix on
5416 - Resume reporting accurate "stream end" reasons to the local control
5417 port. They were lost in the changes for Proposal 148. Bugfix on
5420 o Deprecated and removed features:
5421 - The old "tor --version --version" command, which would print out
5422 the subversion "Id" of most of the source files, is now removed. It
5423 turned out to be less useful than we'd expected, and harder to
5426 o Code simplifications and refactoring:
5427 - Change our header file guard macros to be less likely to conflict
5428 with system headers. Adam Langley noticed that we were conflicting
5429 with log.h on Android.
5430 - Tool-assisted documentation cleanup. Nearly every function or
5431 static variable in Tor should have its own documentation now.
5434 Changes in version 0.2.1.9-alpha - 2008-12-25
5435 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
5437 o New directory authorities:
5438 - gabelmoo (the authority run by Karsten Loesing) now has a new
5442 - Never use a connection with a mismatched address to extend a
5443 circuit, unless that connection is canonical. A canonical
5444 connection is one whose address is authenticated by the router's
5445 identity key, either in a NETINFO cell or in a router descriptor.
5446 - Avoid a possible memory corruption bug when receiving hidden service
5447 descriptors. Bugfix on 0.2.1.6-alpha.
5450 - Fix a logic error that would automatically reject all but the first
5451 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
5452 part of bug 813/868. Bug spotted by coderman.
5453 - When a stream at an exit relay is in state "resolving" or
5454 "connecting" and it receives an "end" relay cell, the exit relay
5455 would silently ignore the end cell and not close the stream. If
5456 the client never closes the circuit, then the exit relay never
5457 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
5459 - When we can't initialize DNS because the network is down, do not
5460 automatically stop Tor from starting. Instead, retry failed
5461 dns_init() every 10 minutes, and change the exit policy to reject
5462 *:* until one succeeds. Fixes bug 691.
5465 - Give a better error message when an overzealous init script says
5466 "sudo -u username tor --user username". Makes Bug 882 easier for
5468 - When a directory authority gives us a new guess for our IP address,
5469 log which authority we used. Hopefully this will help us debug
5470 the recent complaints about bad IP address guesses.
5471 - Detect svn revision properly when we're using git-svn.
5472 - Try not to open more than one descriptor-downloading connection
5473 to an authority at once. This should reduce load on directory
5474 authorities. Fixes bug 366.
5475 - Add cross-certification to newly generated certificates, so that
5476 a signing key is enough information to look up a certificate.
5477 Partial implementation of proposal 157.
5478 - Start serving certificates by <identity digest, signing key digest>
5479 pairs. Partial implementation of proposal 157.
5480 - Clients now never report any stream end reason except 'MISC'.
5481 Implements proposal 148.
5482 - On platforms with a maximum syslog string length, truncate syslog
5483 messages to that length ourselves, rather than relying on the
5484 system to do it for us.
5485 - Optimize out calls to time(NULL) that occur for every IO operation,
5486 or for every cell. On systems where time() is a slow syscall,
5487 this fix will be slightly helpful.
5488 - Exit servers can now answer resolve requests for ip6.arpa addresses.
5489 - When we download a descriptor that we then immediately (as
5490 a directory authority) reject, do not retry downloading it right
5491 away. Should save some bandwidth on authorities. Fix for bug
5492 888. Patch by Sebastian Hahn.
5493 - When a download gets us zero good descriptors, do not notify
5494 Tor that new directory information has arrived.
5495 - Avoid some nasty corner cases in the logic for marking connections
5496 as too old or obsolete or noncanonical for circuits. Partial
5499 o Minor features (controller):
5500 - New CONSENSUS_ARRIVED event to note when a new consensus has
5501 been fetched and validated.
5502 - When we realize that another process has modified our cached
5503 descriptors file, print out a more useful error message rather
5504 than triggering an assertion. Fixes bug 885. Patch from Karsten.
5505 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
5506 controllers to prevent SIGHUP from reloading the
5507 configuration. Fixes bug 856.
5510 - Resume using the correct "REASON=" stream when telling the
5511 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
5512 - When a canonical connection appears later in our internal list
5513 than a noncanonical one for a given OR ID, always use the
5514 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
5516 - Clip the MaxCircuitDirtiness config option to a minimum of 10
5517 seconds. Warn the user if lower values are given in the
5518 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
5519 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
5520 user if lower values are given in the configuration. Bugfix on
5521 0.1.1.17-rc. Patch by Sebastian.
5522 - Fix a race condition when freeing keys shared between main thread
5523 and CPU workers that could result in a memory leak. Bugfix on
5524 0.1.0.1-rc. Fixes bug 889.
5526 o Minor bugfixes (hidden services):
5527 - Do not throw away existing introduction points on SIGHUP (bugfix on
5528 0.0.6pre1); also, do not stall hidden services because we're
5529 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
5530 by John Brooks. Patch by Karsten. Fixes bug 874.
5531 - Fix a memory leak when we decline to add a v2 rendezvous
5532 descriptor to the cache because we already had a v0 descriptor
5533 with the same ID. Bugfix on 0.2.0.18-alpha.
5535 o Deprecated and removed features:
5536 - RedirectExits has been removed. It was deprecated since
5538 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
5539 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
5540 - Cell pools are now always enabled; --disable-cell-pools is ignored.
5542 o Code simplifications and refactoring:
5543 - Rename the confusing or_is_obsolete field to the more appropriate
5544 is_bad_for_new_circs, and move it to or_connection_t where it
5546 - Move edge-only flags from connection_t to edge_connection_t: not
5547 only is this better coding, but on machines of plausible alignment,
5548 it should save 4-8 bytes per connection_t. "Every little bit helps."
5549 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
5550 for consistency; keep old option working for backward compatibility.
5551 - Simplify the code for finding connections to use for a circuit.
5554 Changes in version 0.2.1.8-alpha - 2008-12-08
5555 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
5556 builds better on unusual platforms like Solaris and old OS X, and
5557 fixes a variety of other issues.
5560 - New DirPortFrontPage option that takes an html file and publishes
5561 it as "/" on the DirPort. Now relay operators can provide a
5562 disclaimer without needing to set up a separate webserver. There's
5563 a sample disclaimer in contrib/tor-exit-notice.html.
5566 - When the client is choosing entry guards, now it selects at most
5567 one guard from a given relay family. Otherwise we could end up with
5568 all of our entry points into the network run by the same operator.
5569 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
5572 - Fix a DOS opportunity during the voting signature collection process
5573 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
5574 - Fix a possible segfault when establishing an exit connection. Bugfix
5578 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
5580 - Made Tor a little less aggressive about deleting expired
5581 certificates. Partial fix for bug 854.
5582 - Stop doing unaligned memory access that generated bus errors on
5583 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
5584 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
5585 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
5586 - Make USR2 log-level switch take effect immediately. Bugfix on
5588 - If one win32 nameserver fails to get added, continue adding the
5589 rest, and don't automatically fail.
5590 - Use fcntl() for locking when flock() is not available. Should fix
5591 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
5592 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
5593 could make gcc generate non-functional binary search code. Bugfix
5595 - Build correctly on platforms without socklen_t.
5596 - Avoid potential crash on internal error during signature collection.
5597 Fixes bug 864. Patch from rovv.
5598 - Do not use C's stdio library for writing to log files. This will
5599 improve logging performance by a minute amount, and will stop
5600 leaking fds when our disk is full. Fixes bug 861.
5601 - Stop erroneous use of O_APPEND in cases where we did not in fact
5602 want to re-seek to the end of a file before every last write().
5603 - Correct handling of possible malformed authority signing key
5604 certificates with internal signature types. Fixes bug 880. Bugfix
5606 - Fix a hard-to-trigger resource leak when logging credential status.
5610 - Directory mirrors no longer fetch the v1 directory or
5611 running-routers files. They are obsolete, and nobody asks for them
5612 anymore. This is the first step to making v1 authorities obsolete.
5614 o Minor features (controller):
5615 - Return circuit purposes in response to GETINFO circuit-status. Fixes
5619 Changes in version 0.2.0.32 - 2008-11-20
5620 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
5621 packages (and maybe other packages) noticed by Theo de Raadt, fixes
5622 a smaller security flaw that might allow an attacker to access local
5623 services, further improves hidden service performance, and fixes a
5624 variety of other issues.
5627 - The "User" and "Group" config options did not clear the
5628 supplementary group entries for the Tor process. The "User" option
5629 is now more robust, and we now set the groups to the specified
5630 user's primary group. The "Group" option is now ignored. For more
5631 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
5632 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
5633 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
5634 - The "ClientDNSRejectInternalAddresses" config option wasn't being
5635 consistently obeyed: if an exit relay refuses a stream because its
5636 exit policy doesn't allow it, we would remember what IP address
5637 the relay said the destination address resolves to, even if it's
5638 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
5641 - Fix a DOS opportunity during the voting signature collection process
5642 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
5644 o Major bugfixes (hidden services):
5645 - When fetching v0 and v2 rendezvous service descriptors in parallel,
5646 we were failing the whole hidden service request when the v0
5647 descriptor fetch fails, even if the v2 fetch is still pending and
5648 might succeed. Similarly, if the last v2 fetch fails, we were
5649 failing the whole hidden service request even if a v0 fetch is
5650 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
5651 - When extending a circuit to a hidden service directory to upload a
5652 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
5653 requests failed, because the router descriptor has not been
5654 downloaded yet. In these cases, do not attempt to upload the
5655 rendezvous descriptor, but wait until the router descriptor is
5656 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
5657 descriptor from a hidden service directory for which the router
5658 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
5662 - Fix several infrequent memory leaks spotted by Coverity.
5663 - When testing for libevent functions, set the LDFLAGS variable
5664 correctly. Found by Riastradh.
5665 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
5666 bootstrapping with tunneled directory connections. Bugfix on
5667 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
5668 - When asked to connect to A.B.exit:80, if we don't know the IP for A
5669 and we know that server B rejects most-but-not all connections to
5670 port 80, we would previously reject the connection. Now, we assume
5671 the user knows what they were asking for. Fixes bug 752. Bugfix
5672 on 0.0.9rc5. Diagnosed by BarkerJr.
5673 - If we overrun our per-second write limits a little, count this as
5674 having used up our write allocation for the second, and choke
5675 outgoing directory writes. Previously, we had only counted this when
5676 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
5677 Bugfix on 0.2.0.x (??).
5678 - Remove the old v2 directory authority 'lefkada' from the default
5679 list. It has been gone for many months.
5680 - Stop doing unaligned memory access that generated bus errors on
5681 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
5682 - Make USR2 log-level switch take effect immediately. Bugfix on
5685 o Minor bugfixes (controller):
5686 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
5687 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
5690 Changes in version 0.2.1.7-alpha - 2008-11-08
5691 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
5692 packages (and maybe other packages) noticed by Theo de Raadt, fixes
5693 a smaller security flaw that might allow an attacker to access local
5694 services, adds better defense against DNS poisoning attacks on exit
5695 relays, further improves hidden service performance, and fixes a
5696 variety of other issues.
5699 - The "ClientDNSRejectInternalAddresses" config option wasn't being
5700 consistently obeyed: if an exit relay refuses a stream because its
5701 exit policy doesn't allow it, we would remember what IP address
5702 the relay said the destination address resolves to, even if it's
5703 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
5704 - The "User" and "Group" config options did not clear the
5705 supplementary group entries for the Tor process. The "User" option
5706 is now more robust, and we now set the groups to the specified
5707 user's primary group. The "Group" option is now ignored. For more
5708 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
5709 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
5710 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
5711 - Do not use or believe expired v3 authority certificates. Patch
5712 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
5715 - Now NodeFamily and MyFamily config options allow spaces in
5716 identity fingerprints, so it's easier to paste them in.
5717 Suggested by Lucky Green.
5718 - Implement the 0x20 hack to better resist DNS poisoning: set the
5719 case on outgoing DNS requests randomly, and reject responses that do
5720 not match the case correctly. This logic can be disabled with the
5721 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
5722 of servers that do not reliably preserve case in replies. See
5723 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
5725 - Preserve case in replies to DNSPort requests in order to support
5726 the 0x20 hack for resisting DNS poisoning attacks.
5728 o Hidden service performance improvements:
5729 - When the client launches an introduction circuit, retry with a
5730 new circuit after 30 seconds rather than 60 seconds.
5731 - Launch a second client-side introduction circuit in parallel
5732 after a delay of 15 seconds (based on work by Christian Wilms).
5733 - Hidden services start out building five intro circuits rather
5734 than three, and when the first three finish they publish a service
5735 descriptor using those. Now we publish our service descriptor much
5736 faster after restart.
5739 - Minor fix in the warning messages when you're having problems
5740 bootstrapping; also, be more forgiving of bootstrap problems when
5741 we're still making incremental progress on a given bootstrap phase.
5742 - When we're choosing an exit node for a circuit, and we have
5743 no pending streams, choose a good general exit rather than one that
5744 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
5745 - Send a valid END cell back when a client tries to connect to a
5746 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
5747 840. Patch from rovv.
5748 - If a broken client asks a non-exit router to connect somewhere,
5749 do not even do the DNS lookup before rejecting the connection.
5750 Fixes another case of bug 619. Patch from rovv.
5751 - Fix another case of assuming, when a specific exit is requested,
5752 that we know more than the user about what hosts it allows.
5753 Fixes another case of bug 752. Patch from rovv.
5754 - Check which hops rendezvous stream cells are associated with to
5755 prevent possible guess-the-streamid injection attacks from
5756 intermediate hops. Fixes another case of bug 446. Based on patch
5758 - Avoid using a negative right-shift when comparing 32-bit
5759 addresses. Possible fix for bug 845 and bug 811.
5760 - Make the assert_circuit_ok() function work correctly on circuits that
5761 have already been marked for close.
5762 - Fix read-off-the-end-of-string error in unit tests when decoding
5763 introduction points.
5764 - Fix uninitialized size field for memory area allocation: may improve
5765 memory performance during directory parsing.
5766 - Treat duplicate certificate fetches as failures, so that we do
5767 not try to re-fetch an expired certificate over and over and over.
5768 - Do not say we're fetching a certificate when we'll in fact skip it
5769 because of a pending download.
5772 Changes in version 0.2.1.6-alpha - 2008-09-30
5773 Tor 0.2.1.6-alpha further improves performance and robustness of
5774 hidden services, starts work on supporting per-country relay selection,
5775 and fixes a variety of smaller issues.
5778 - Implement proposal 121: make it possible to build hidden services
5779 that only certain clients are allowed to connect to. This is
5780 enforced at several points, so that unauthorized clients are unable
5781 to send INTRODUCE cells to the service, or even (depending on the
5782 type of authentication) to learn introduction points. This feature
5783 raises the bar for certain kinds of active attacks against hidden
5784 services. Code by Karsten Loesing.
5785 - Relays now store and serve v2 hidden service descriptors by default,
5786 i.e., the new default value for HidServDirectoryV2 is 1. This is
5787 the last step in proposal 114, which aims to make hidden service
5788 lookups more reliable.
5789 - Start work to allow node restrictions to include country codes. The
5790 syntax to exclude nodes in a country with country code XX is
5791 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
5792 refinement to decide what config options should take priority if
5793 you ask to both use a particular node and exclude it.
5794 - Allow ExitNodes list to include IP ranges and country codes, just
5795 like the Exclude*Nodes lists. Patch from Robert Hogan.
5798 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
5799 Tor to fail to start if you had it configured to use a bridge
5800 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
5801 - When extending a circuit to a hidden service directory to upload a
5802 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
5803 requests failed, because the router descriptor had not been
5804 downloaded yet. In these cases, we now wait until the router
5805 descriptor is downloaded, and then retry. Likewise, clients
5806 now skip over a hidden service directory if they don't yet have
5807 its router descriptor, rather than futilely requesting it and
5808 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
5810 - When fetching v0 and v2 rendezvous service descriptors in parallel,
5811 we were failing the whole hidden service request when the v0
5812 descriptor fetch fails, even if the v2 fetch is still pending and
5813 might succeed. Similarly, if the last v2 fetch fails, we were
5814 failing the whole hidden service request even if a v0 fetch is
5815 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
5816 - DNS replies need to have names matching their requests, but
5817 these names should be in the questions section, not necessarily
5818 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
5821 - Update to the "September 1 2008" ip-to-country file.
5822 - Allow ports 465 and 587 in the default exit policy again. We had
5823 rejected them in 0.1.0.15, because back in 2005 they were commonly
5824 misconfigured and ended up as spam targets. We hear they are better
5825 locked down these days.
5826 - Use a lockfile to make sure that two Tor processes are not
5827 simultaneously running with the same datadir.
5828 - Serve the latest v3 networkstatus consensus via the control
5829 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
5830 - Better logging about stability/reliability calculations on directory
5832 - Drop the requirement to have an open dir port for storing and
5833 serving v2 hidden service descriptors.
5834 - Directory authorities now serve a /tor/dbg-stability.txt URL to
5835 help debug WFU and MTBF calculations.
5836 - Implement most of Proposal 152: allow specialized servers to permit
5837 single-hop circuits, and clients to use those servers to build
5838 single-hop circuits when using a specialized controller. Patch
5839 from Josh Albrecht. Resolves feature request 768.
5840 - Add a -p option to tor-resolve for specifying the SOCKS port: some
5841 people find host:port too confusing.
5842 - Make TrackHostExit mappings expire a while after their last use, not
5843 after their creation. Patch from Robert Hogan.
5844 - Provide circuit purposes along with circuit events to the controller.
5847 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
5849 - Fixed some memory leaks -- some quite frequent, some almost
5850 impossible to trigger -- based on results from Coverity.
5851 - When testing for libevent functions, set the LDFLAGS variable
5852 correctly. Found by Riastradh.
5853 - Fix an assertion bug in parsing policy-related options; possible fix
5855 - Catch and report a few more bootstrapping failure cases when Tor
5856 fails to establish a TCP connection. Cleanup on 0.2.1.x.
5857 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
5858 bootstrapping with tunneled directory connections. Bugfix on
5859 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
5860 - When asked to connect to A.B.exit:80, if we don't know the IP for A
5861 and we know that server B rejects most-but-not all connections to
5862 port 80, we would previously reject the connection. Now, we assume
5863 the user knows what they were asking for. Fixes bug 752. Bugfix
5864 on 0.0.9rc5. Diagnosed by BarkerJr.
5865 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
5866 service directories if they have no advertised dir port. Bugfix
5868 - If we overrun our per-second write limits a little, count this as
5869 having used up our write allocation for the second, and choke
5870 outgoing directory writes. Previously, we had only counted this when
5871 we had met our limits precisely. Fixes bug 824. Patch by rovv.
5872 Bugfix on 0.2.0.x (??).
5873 - Avoid a "0 divided by 0" calculation when calculating router uptime
5874 at directory authorities. Bugfix on 0.2.0.8-alpha.
5875 - Make DNS resolved controller events into "CLOSED", not
5876 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
5878 - Fix a bug where an unreachable relay would establish enough
5879 reachability testing circuits to do a bandwidth test -- if
5880 we already have a connection to the middle hop of the testing
5881 circuit, then it could establish the last hop by using the existing
5882 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
5883 circuits no longer use entry guards in 0.2.1.3-alpha.
5884 - If we have correct permissions on $datadir, we complain to stdout
5885 and fail to start. But dangerous permissions on
5886 $datadir/cached-status/ would cause us to open a log and complain
5887 there. Now complain to stdout and fail to start in both cases. Fixes
5888 bug 820, reported by seeess.
5889 - Remove the old v2 directory authority 'lefkada' from the default
5890 list. It has been gone for many months.
5892 o Code simplifications and refactoring:
5893 - Revise the connection_new functions so that a more typesafe variant
5894 exists. This will work better with Coverity, and let us find any
5895 actual mistakes we're making here.
5896 - Refactor unit testing logic so that dmalloc can be used sensibly
5897 with unit tests to check for memory leaks.
5898 - Move all hidden-service related fields from connection and circuit
5899 structure to substructures: this way they won't eat so much memory.
5902 Changes in version 0.2.0.31 - 2008-09-03
5903 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
5904 a big bug we're seeing where in rare cases traffic from one Tor stream
5905 gets mixed into another stream, and fixes a variety of smaller issues.
5908 - Make sure that two circuits can never exist on the same connection
5909 with the same circuit ID, even if one is marked for close. This
5910 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
5911 - Relays now reject risky extend cells: if the extend cell includes
5912 a digest of all zeroes, or asks to extend back to the relay that
5913 sent the extend cell, tear down the circuit. Ideas suggested
5915 - If not enough of our entry guards are available so we add a new
5916 one, we might use the new one even if it overlapped with the
5917 current circuit's exit relay (or its family). Anonymity bugfix
5918 pointed out by rovv.
5921 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
5922 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
5923 - Correctly detect the presence of the linux/netfilter_ipv4.h header
5924 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
5925 - Pick size of default geoip filename string correctly on windows.
5926 Fixes bug 806. Bugfix on 0.2.0.30.
5927 - Make the autoconf script accept the obsolete --with-ssl-dir
5928 option as an alias for the actually-working --with-openssl-dir
5929 option. Fix the help documentation to recommend --with-openssl-dir.
5930 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
5931 - When using the TransPort option on OpenBSD, and using the User
5932 option to change UID and drop privileges, make sure to open
5933 /dev/pf before dropping privileges. Fixes bug 782. Patch from
5934 Christopher Davis. Bugfix on 0.1.2.1-alpha.
5935 - Try to attach connections immediately upon receiving a RENDEZVOUS2
5936 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
5937 on the client side when connecting to a hidden service. Bugfix
5938 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
5939 - When closing an application-side connection because its circuit is
5940 getting torn down, generate the stream event correctly. Bugfix on
5941 0.1.2.x. Anonymous patch.
5944 Changes in version 0.2.1.5-alpha - 2008-08-31
5945 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
5946 in a lot of the infrastructure for adding authorization to hidden
5947 services, lays the groundwork for having clients read their load
5948 balancing information out of the networkstatus consensus rather than
5949 the individual router descriptors, addresses two potential anonymity
5950 issues, and fixes a variety of smaller issues.
5953 - Convert many internal address representations to optionally hold
5955 - Generate and accept IPv6 addresses in many protocol elements.
5956 - Make resolver code handle nameservers located at ipv6 addresses.
5957 - Begin implementation of proposal 121 ("Client authorization for
5958 hidden services"): configure hidden services with client
5959 authorization, publish descriptors for them, and configure
5960 authorization data for hidden services at clients. The next
5961 step is to actually access hidden services that perform client
5963 - More progress toward proposal 141: Network status consensus
5964 documents and votes now contain bandwidth information for each
5965 router and a summary of that router's exit policy. Eventually this
5966 will be used by clients so that they do not have to download every
5967 known descriptor before building circuits.
5969 o Major bugfixes (on 0.2.0.x and before):
5970 - When sending CREATED cells back for a given circuit, use a 64-bit
5971 connection ID to find the right connection, rather than an addr:port
5972 combination. Now that we can have multiple OR connections between
5973 the same ORs, it is no longer possible to use addr:port to uniquely
5974 identify a connection.
5975 - Relays now reject risky extend cells: if the extend cell includes
5976 a digest of all zeroes, or asks to extend back to the relay that
5977 sent the extend cell, tear down the circuit. Ideas suggested
5979 - If not enough of our entry guards are available so we add a new
5980 one, we might use the new one even if it overlapped with the
5981 current circuit's exit relay (or its family). Anonymity bugfix
5982 pointed out by rovv.
5985 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
5986 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
5987 - When using the TransPort option on OpenBSD, and using the User
5988 option to change UID and drop privileges, make sure to open /dev/pf
5989 before dropping privileges. Fixes bug 782. Patch from Christopher
5990 Davis. Bugfix on 0.1.2.1-alpha.
5991 - Correctly detect the presence of the linux/netfilter_ipv4.h header
5992 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
5993 - Add a missing safe_str() call for a debug log message.
5994 - Use 64 bits instead of 32 bits for connection identifiers used with
5995 the controller protocol, to greatly reduce risk of identifier reuse.
5996 - Make the autoconf script accept the obsolete --with-ssl-dir
5997 option as an alias for the actually-working --with-openssl-dir
5998 option. Fix the help documentation to recommend --with-openssl-dir.
5999 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
6002 - Rate-limit too-many-sockets messages: when they happen, they happen
6003 a lot. Resolves bug 748.
6004 - Resist DNS poisoning a little better by making sure that names in
6005 answer sections match.
6006 - Print the SOCKS5 error message string as well as the error code
6007 when a tor-resolve request fails. Patch from Jacob.
6010 Changes in version 0.2.1.4-alpha - 2008-08-04
6011 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
6014 - The address part of exit policies was not correctly written
6015 to router descriptors. This generated router descriptors that failed
6016 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
6018 - Tor triggered a false assert when extending a circuit to a relay
6019 but we already have a connection open to that relay. Noticed by
6020 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
6023 - Fix a hidden service logging bug: in some edge cases, the router
6024 descriptor of a previously picked introduction point becomes
6025 obsolete and we need to give up on it rather than continually
6026 complaining that it has become obsolete. Observed by xiando. Bugfix
6030 - Take out the TestVia config option, since it was a workaround for
6031 a bug that was fixed in Tor 0.1.1.21.
6034 Changes in version 0.2.1.3-alpha - 2008-08-03
6035 Tor 0.2.1.3-alpha implements most of the pieces to prevent
6036 infinite-length circuit attacks (see proposal 110); fixes a bug that
6037 might cause exit relays to corrupt streams they send back; allows
6038 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
6039 ExcludeExitNodes config options; and fixes a big pile of bugs.
6041 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
6042 - Send a bootstrap problem "warn" event on the first problem if the
6043 reason is NO_ROUTE (that is, our network is down).
6046 - Implement most of proposal 110: The first K cells to be sent
6047 along a circuit are marked as special "early" cells; only K "early"
6048 cells will be allowed. Once this code is universal, we can block
6049 certain kinds of DOS attack by requiring that EXTEND commands must
6050 be sent using an "early" cell.
6053 - Try to attach connections immediately upon receiving a RENDEZVOUS2
6054 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
6055 on the client side when connecting to a hidden service. Bugfix
6056 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
6057 - Ensure that two circuits can never exist on the same connection
6058 with the same circuit ID, even if one is marked for close. This
6059 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
6062 - When relays do their initial bandwidth measurement, don't limit
6063 to just our entry guards for the test circuits. Otherwise we tend
6064 to have multiple test circuits going through a single entry guard,
6065 which makes our bandwidth test less accurate. Fixes part of bug 654;
6066 patch contributed by Josh Albrecht.
6067 - Add an ExcludeExitNodes option so users can list a set of nodes
6068 that should be be excluded from the exit node position, but
6069 allowed elsewhere. Implements proposal 151.
6070 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
6071 ExcludeNodes and ExcludeExitNodes lists.
6072 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
6073 be more efficient. Formerly it was quadratic in the number of
6074 servers; now it should be linear. Fixes bug 509.
6075 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
6076 and n_conn_id_digest fields into a separate structure that's
6077 only needed when the circuit has not yet attached to an n_conn.
6080 - Change the contrib/tor.logrotate script so it makes the new
6081 logs as "_tor:_tor" rather than the default, which is generally
6082 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
6083 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
6084 warnings (occasionally), but it can also cause the compiler to
6085 eliminate error-checking code. Suggested by Peter Gutmann.
6086 - When a hidden service is giving up on an introduction point candidate
6087 that was not included in the last published rendezvous descriptor,
6088 don't reschedule publication of the next descriptor. Fixes bug 763.
6090 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
6091 HiddenServiceExcludeNodes as obsolete: they never worked properly,
6092 and nobody claims to be using them. Fixes bug 754. Bugfix on
6093 0.1.0.1-rc. Patch from Christian Wilms.
6094 - Fix a small alignment and memory-wasting bug on buffer chunks.
6097 o Minor bugfixes (controller):
6098 - When closing an application-side connection because its circuit
6099 is getting torn down, generate the stream event correctly.
6100 Bugfix on 0.1.2.x. Anonymous patch.
6103 - Remove all backward-compatibility code to support relays running
6104 versions of Tor so old that they no longer work at all on the
6108 Changes in version 0.2.0.30 - 2008-07-15
6110 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
6111 warnings (occasionally), but it can also cause the compiler to
6112 eliminate error-checking code. Suggested by Peter Gutmann.
6115 Changes in version 0.2.0.29-rc - 2008-07-08
6116 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
6117 hidden-service performance bugs, and fixes a bunch of smaller bugs.
6120 - If you have more than one bridge but don't know their keys,
6121 you would only launch a request for the descriptor of the first one
6122 on your list. (Tor considered launching requests for the others, but
6123 found that it already had a connection on the way for $0000...0000
6124 so it didn't open another.) Bugfix on 0.2.0.x.
6125 - If you have more than one bridge but don't know their keys, and the
6126 connection to one of the bridges failed, you would cancel all
6127 pending bridge connections. (After all, they all have the same
6128 digest.) Bugfix on 0.2.0.x.
6129 - When a hidden service was trying to establish an introduction point,
6130 and Tor had built circuits preemptively for such purposes, we
6131 were ignoring all the preemptive circuits and launching a new one
6132 instead. Bugfix on 0.2.0.14-alpha.
6133 - When a hidden service was trying to establish an introduction point,
6134 and Tor *did* manage to reuse one of the preemptively built
6135 circuits, it didn't correctly remember which one it used,
6136 so it asked for another one soon after, until there were no
6137 more preemptive circuits, at which point it launched one from
6138 scratch. Bugfix on 0.0.9.x.
6139 - Make directory servers include the X-Your-Address-Is: http header in
6140 their responses even for begin_dir conns. Now clients who only
6141 ever use begin_dir connections still have a way to learn their IP
6142 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
6145 - Fix a macro/CPP interaction that was confusing some compilers:
6146 some GCCs don't like #if/#endif pairs inside macro arguments.
6148 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
6149 Fixes bug 704; fix from Steven Murdoch.
6150 - When opening /dev/null in finish_daemonize(), do not pass the
6151 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
6152 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
6153 - Correctly detect transparent proxy support on Linux hosts that
6154 require in.h to be included before netfilter_ipv4.h. Patch
6156 - Disallow session resumption attempts during the renegotiation
6157 stage of the v2 handshake protocol. Clients should never be trying
6158 session resumption at this point, but apparently some did, in
6159 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
6160 found by Geoff Goodell.
6163 Changes in version 0.2.1.2-alpha - 2008-06-20
6164 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
6165 make it easier to set up your own private Tor network; fixes several
6166 big bugs with using more than one bridge relay; fixes a big bug with
6167 offering hidden services quickly after Tor starts; and uses a better
6168 API for reporting potential bootstrapping problems to the controller.
6171 - New TestingTorNetwork config option to allow adjustment of
6172 previously constant values that, while reasonable, could slow
6173 bootstrapping. Implements proposal 135. Patch from Karsten.
6176 - If you have more than one bridge but don't know their digests,
6177 you would only learn a request for the descriptor of the first one
6178 on your list. (Tor considered launching requests for the others, but
6179 found that it already had a connection on the way for $0000...0000
6180 so it didn't open another.) Bugfix on 0.2.0.x.
6181 - If you have more than one bridge but don't know their digests,
6182 and the connection to one of the bridges failed, you would cancel
6183 all pending bridge connections. (After all, they all have the
6184 same digest.) Bugfix on 0.2.0.x.
6185 - When establishing a hidden service, introduction points that
6186 originate from cannibalized circuits are completely ignored and not
6187 included in rendezvous service descriptors. This might be another
6188 reason for delay in making a hidden service available. Bugfix
6189 from long ago (0.0.9.x?)
6192 - Allow OpenSSL to use dynamic locks if it wants.
6193 - When building a consensus, do not include routers that are down.
6194 This will cut down 30% to 40% on consensus size. Implements
6196 - In directory authorities' approved-routers files, allow
6197 fingerprints with or without space.
6198 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
6199 controller can query our current bootstrap state in case it attaches
6200 partway through and wants to catch up.
6201 - Send an initial "Starting" bootstrap status event, so we have a
6202 state to start out in.
6205 - Asking for a conditional consensus at .../consensus/<fingerprints>
6206 would crash a dirserver if it did not already have a
6207 consensus. Bugfix on 0.2.1.1-alpha.
6208 - Clean up some macro/CPP interactions: some GCC versions don't like
6209 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
6212 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
6213 - Directory authorities shouldn't complain about bootstrapping
6214 problems just because they do a lot of reachability testing and
6215 some of the connection attempts fail.
6216 - Start sending "count" and "recommendation" key/value pairs in
6217 bootstrap problem status events, so the controller can hear about
6218 problems even before Tor decides they're worth reporting for sure.
6219 - If you're using bridges, generate "bootstrap problem" warnings
6220 as soon as you run out of working bridges, rather than waiting
6221 for ten failures -- which will never happen if you have less than
6223 - If we close our OR connection because there's been a circuit
6224 pending on it for too long, we were telling our bootstrap status
6225 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
6228 Changes in version 0.2.1.1-alpha - 2008-06-13
6229 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
6230 were making the Tor process bloat especially on Linux; makes our TLS
6231 handshake blend in better; sends "bootstrap phase" status events to
6232 the controller, so it can keep the user informed of progress (and
6233 problems) fetching directory information and establishing circuits;
6234 and adds a variety of smaller features.
6237 - More work on making our TLS handshake blend in: modify the list
6238 of ciphers advertised by OpenSSL in client mode to even more
6239 closely resemble a common web browser. We cheat a little so that
6240 we can advertise ciphers that the locally installed OpenSSL doesn't
6242 - Start sending "bootstrap phase" status events to the controller,
6243 so it can keep the user informed of progress fetching directory
6244 information and establishing circuits. Also inform the controller
6245 if we think we're stuck at a particular bootstrap phase. Implements
6247 - Resume using OpenSSL's RAND_poll() for better (and more portable)
6248 cross-platform entropy collection again. We used to use it, then
6249 stopped using it because of a bug that could crash systems that
6250 called RAND_poll when they had a lot of fds open. It looks like the
6251 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
6252 at startup, and to call RAND_poll() when we reseed later only if
6253 we have a non-buggy OpenSSL version.
6256 - When we choose to abandon a new entry guard because we think our
6257 older ones might be better, close any circuits pending on that
6258 new entry guard connection. This fix should make us recover much
6259 faster when our network is down and then comes back. Bugfix on
6260 0.1.2.8-beta; found by lodger.
6262 o Memory fixes and improvements:
6263 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
6264 to avoid unused RAM in buffer chunks and memory pools.
6265 - Speed up parsing and cut down on memory fragmentation by using
6266 stack-style allocations for parsing directory objects. Previously,
6267 this accounted for over 40% of allocations from within Tor's code
6268 on a typical directory cache.
6269 - Use a Bloom filter rather than a digest-based set to track which
6270 descriptors we need to keep around when we're cleaning out old
6271 router descriptors. This speeds up the computation significantly,
6272 and may reduce fragmentation.
6273 - Reduce the default smartlist size from 32 to 16; it turns out that
6274 most smartlists hold around 8-12 elements tops.
6275 - Make dumpstats() log the fullness and size of openssl-internal
6277 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
6278 patch to their OpenSSL, turn it on to save memory on servers. This
6279 patch will (with any luck) get included in a mainline distribution
6281 - Never use OpenSSL compression: it wastes RAM and CPU trying to
6282 compress cells, which are basically all encrypted, compressed,
6286 - Stop reloading the router list from disk for no reason when we
6287 run out of reachable directory mirrors. Once upon a time reloading
6288 it would set the 'is_running' flag back to 1 for them. It hasn't
6289 done that for a long time.
6290 - In very rare situations new hidden service descriptors were
6291 published earlier than 30 seconds after the last change to the
6292 service. (We currently think that a hidden service descriptor
6293 that's been stable for 30 seconds is worth publishing.)
6296 - Allow separate log levels to be configured for different logging
6297 domains. For example, this allows one to log all notices, warnings,
6298 or errors, plus all memory management messages of level debug or
6299 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
6300 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
6301 and stop using a warning that had become unfixably verbose under
6303 - New --hush command-line option similar to --quiet. While --quiet
6304 disables all logging to the console on startup, --hush limits the
6305 output to messages of warning and error severity.
6306 - Servers support a new URL scheme for consensus downloads that
6307 allows the client to specify which authorities are trusted.
6308 The server then only sends the consensus if the client will trust
6309 it. Otherwise a 404 error is sent back. Clients use this
6310 new scheme when the server supports it (meaning it's running
6311 0.2.1.1-alpha or later). Implements proposal 134.
6312 - New configure/torrc options (--enable-geoip-stats,
6313 DirRecordUsageByCountry) to record how many IPs we've served
6314 directory info to in each country code, how many status documents
6315 total we've sent to each country code, and what share of the total
6316 directory requests we should expect to see.
6317 - Use the TLS1 hostname extension to more closely resemble browser
6319 - Lots of new unit tests.
6320 - Add a macro to implement the common pattern of iterating through
6321 two parallel lists in lockstep.
6324 Changes in version 0.2.0.28-rc - 2008-06-13
6325 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
6326 performance bug, and fixes a bunch of smaller bugs.
6329 - Fix a bug where, when we were choosing the 'end stream reason' to
6330 put in our relay end cell that we send to the exit relay, Tor
6331 clients on Windows were sometimes sending the wrong 'reason'. The
6332 anonymity problem is that exit relays may be able to guess whether
6333 the client is running Windows, thus helping partition the anonymity
6334 set. Down the road we should stop sending reasons to exit relays,
6335 or otherwise prevent future versions of this bug.
6338 - While setting up a hidden service, some valid introduction circuits
6339 were overlooked and abandoned. This might be the reason for
6340 the long delay in making a hidden service available. Bugfix on
6344 - Update to the "June 9 2008" ip-to-country file.
6345 - Run 'make test' as part of 'make dist', so we stop releasing so
6346 many development snapshots that fail their unit tests.
6349 - When we're checking if we have enough dir info for each relay
6350 to begin establishing circuits, make sure that we actually have
6351 the descriptor listed in the consensus, not just any descriptor.
6353 - Bridge relays no longer print "xx=0" in their extrainfo document
6354 for every single country code in the geoip db. Bugfix on
6356 - Only warn when we fail to load the geoip file if we were planning to
6357 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
6358 - If we change our MaxAdvertisedBandwidth and then reload torrc,
6359 Tor won't realize it should publish a new relay descriptor. Fixes
6360 bug 688, reported by mfr. Bugfix on 0.1.2.x.
6361 - When we haven't had any application requests lately, don't bother
6362 logging that we have expired a bunch of descriptors. Bugfix
6364 - Make relay cells written on a connection count as non-padding when
6365 tracking how long a connection has been in use. Bugfix on
6366 0.2.0.1-alpha. Spotted by lodger.
6367 - Fix unit tests in 0.2.0.27-rc.
6368 - Fix compile on Windows.
6371 Changes in version 0.2.0.27-rc - 2008-06-03
6372 Tor 0.2.0.27-rc adds a few features we left out of the earlier
6373 release candidates. In particular, we now include an IP-to-country
6374 GeoIP database, so controllers can easily look up what country a
6375 given relay is in, and so bridge relays can give us some sanitized
6376 summaries about which countries are making use of bridges. (See proposal
6377 126-geoip-fetching.txt for details.)
6380 - Include an IP-to-country GeoIP file in the tarball, so bridge
6381 relays can report sanitized summaries of the usage they're seeing.
6384 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
6385 Robert Hogan. Fixes the first part of bug 681.
6386 - Make bridge authorities never serve extrainfo docs.
6387 - Add support to detect Libevent versions in the 1.4.x series
6389 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
6390 - Include a new contrib/tor-exit-notice.html file that exit relay
6391 operators can put on their website to help reduce abuse queries.
6394 - When tunneling an encrypted directory connection, and its first
6395 circuit fails, do not leave it unattached and ask the controller
6396 to deal. Fixes the second part of bug 681.
6397 - Make bridge authorities correctly expire old extrainfo documents
6401 Changes in version 0.2.0.26-rc - 2008-05-13
6402 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
6403 in Debian's OpenSSL packages. All users running any 0.2.0.x version
6404 should upgrade, whether they're running Debian or not.
6406 o Major security fixes:
6407 - Use new V3 directory authority keys on the tor26, gabelmoo, and
6408 moria1 V3 directory authorities. The old keys were generated with
6409 a vulnerable version of Debian's OpenSSL package, and must be
6410 considered compromised. Other authorities' keys were not generated
6411 with an affected version of OpenSSL.
6414 - List authority signatures as "unrecognized" based on DirServer
6415 lines, not on cert cache. Bugfix on 0.2.0.x.
6418 - Add a new V3AuthUseLegacyKey option to make it easier for
6419 authorities to change their identity keys if they have to.
6422 Changes in version 0.2.0.25-rc - 2008-04-23
6423 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
6426 - Remember to initialize threading before initializing logging.
6427 Otherwise, many BSD-family implementations will crash hard on
6428 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
6431 - Authorities correctly free policies on bad servers on
6432 exit. Fixes bug 672. Bugfix on 0.2.0.x.
6435 Changes in version 0.2.0.24-rc - 2008-04-22
6436 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
6437 v3 directory authority, makes relays with dynamic IP addresses and no
6438 DirPort notice more quickly when their IP address changes, fixes a few
6439 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
6441 o New directory authorities:
6442 - Take lefkada out of the list of v3 directory authorities, since
6443 it has been down for months.
6444 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
6448 - Detect address changes more quickly on non-directory mirror
6449 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
6451 o Minor features (security):
6452 - Reject requests for reverse-dns lookup of names that are in
6453 a private address space. Patch from lodger.
6454 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
6457 o Minor bugfixes (crashes):
6458 - Avoid a rare assert that can trigger when Tor doesn't have much
6459 directory information yet and it tries to fetch a v2 hidden
6460 service descriptor. Fixes bug 651, reported by nwf.
6461 - Initialize log mutex before initializing dmalloc. Otherwise,
6462 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
6463 - Use recursive pthread mutexes in order to avoid deadlock when
6464 logging debug-level messages to a controller. Bug spotted by nwf,
6465 bugfix on 0.2.0.16-alpha.
6467 o Minor bugfixes (resource management):
6468 - Keep address policies from leaking memory: start their refcount
6469 at 1, not 2. Bugfix on 0.2.0.16-alpha.
6470 - Free authority certificates on exit, so they don't look like memory
6471 leaks. Bugfix on 0.2.0.19-alpha.
6472 - Free static hashtables for policy maps and for TLS connections on
6473 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
6474 - Avoid allocating extra space when computing consensuses on 64-bit
6475 platforms. Bug spotted by aakova.
6477 o Minor bugfixes (misc):
6478 - Do not read the configuration file when we've only been told to
6479 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
6480 based on patch from Sebastian Hahn.
6481 - Exit relays that are used as a client can now reach themselves
6482 using the .exit notation, rather than just launching an infinite
6483 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
6484 - When attempting to open a logfile fails, tell us why.
6485 - Fix a dumb bug that was preventing us from knowing that we should
6486 preemptively build circuits to handle expected directory requests.
6487 Fixes bug 660. Bugfix on 0.1.2.x.
6488 - Warn less verbosely about clock skew from netinfo cells from
6489 untrusted sources. Fixes bug 663.
6490 - Make controller stream events for DNS requests more consistent,
6491 by adding "new stream" events for DNS requests, and removing
6492 spurious "stream closed" events" for cached reverse resolves.
6493 Patch from mwenge. Fixes bug 646.
6494 - Correctly notify one-hop connections when a circuit build has
6495 failed. Possible fix for bug 669. Found by lodger.
6498 Changes in version 0.2.0.23-rc - 2008-03-24
6499 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
6500 makes bootstrapping faster if the first directory mirror you contact
6501 is down. The bundles also include the new Vidalia 0.1.2 release.
6504 - When a tunneled directory request is made to a directory server
6505 that's down, notice after 30 seconds rather than 120 seconds. Also,
6506 fail any begindir streams that are pending on it, so they can
6507 retry elsewhere. This was causing multi-minute delays on bootstrap.
6510 Changes in version 0.2.0.22-rc - 2008-03-18
6511 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
6512 enables encrypted directory connections by default for non-relays, fixes
6513 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
6514 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
6517 - Enable encrypted directory connections by default for non-relays,
6518 so censor tools that block Tor directory connections based on their
6519 plaintext patterns will no longer work. This means Tor works in
6520 certain censored countries by default again.
6523 - Make sure servers always request certificates from clients during
6524 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
6525 - Do not enter a CPU-eating loop when a connection is closed in
6526 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
6527 diagnosed by lodger; bugfix on 0.2.0.20-rc.
6528 - Fix assertion failure that could occur when a blocked circuit
6529 became unblocked, and it had pending client DNS requests. Bugfix
6530 on 0.2.0.1-alpha. Fixes bug 632.
6532 o Minor bugfixes (on 0.1.2.x):
6533 - Generate "STATUS_SERVER" events rather than misspelled
6534 "STATUS_SEVER" events. Caught by mwenge.
6535 - When counting the number of bytes written on a TLS connection,
6536 look at the BIO actually used for writing to the network, not
6537 at the BIO used (sometimes) to buffer data for the network.
6538 Looking at different BIOs could result in write counts on the
6539 order of ULONG_MAX. Fixes bug 614.
6540 - On Windows, correctly detect errors when listing the contents of
6541 a directory. Fix from lodger.
6543 o Minor bugfixes (on 0.2.0.x):
6544 - Downgrade "sslv3 alert handshake failure" message to INFO.
6545 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
6546 left BandwidthRate and BandwidthBurst at the default, we would be
6547 silently limited by those defaults. Now raise them to match the
6548 RelayBandwidth* values.
6549 - Fix the SVK version detection logic to work correctly on a branch.
6550 - Make --enable-openbsd-malloc work correctly on Linux with alpha
6551 CPUs. Fixes bug 625.
6552 - Logging functions now check that the passed severity is sane.
6553 - Use proper log levels in the testsuite call of
6554 get_interface_address6().
6555 - When using a nonstandard malloc, do not use the platform values for
6556 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
6557 - Make the openbsd malloc code use 8k pages on alpha CPUs and
6559 - Detect mismatched page sizes when using --enable-openbsd-malloc.
6560 - Avoid double-marked-for-close warning when certain kinds of invalid
6561 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
6562 for bug 617. Bugfix on 0.2.0.1-alpha.
6563 - Make sure that the "NULL-means-reject *:*" convention is followed by
6564 all the policy manipulation functions, avoiding some possible crash
6565 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
6566 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
6567 actually works, and doesn't warn about every single reverse lookup.
6568 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
6571 - Only log guard node status when guard node status has changed.
6572 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
6573 make "INFO" 75% less verbose.
6576 Changes in version 0.2.0.21-rc - 2008-03-02
6577 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
6578 makes Tor work well with Vidalia again, fixes a rare assert bug,
6579 and fixes a pair of more minor bugs. The bundles also include Vidalia
6580 0.1.0 and Torbutton 1.1.16.
6583 - The control port should declare that it requires password auth
6584 when HashedControlSessionPassword is set too. Patch from Matt Edman;
6585 bugfix on 0.2.0.20-rc. Fixes bug 615.
6586 - Downgrade assert in connection_buckets_decrement() to a log message.
6587 This may help us solve bug 614, and in any case will make its
6588 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
6589 - We were sometimes miscounting the number of bytes read from the
6590 network, causing our rate limiting to not be followed exactly.
6591 Bugfix on 0.2.0.16-alpha. Reported by lodger.
6594 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
6595 OpenSSL versions should have been working fine. Diagnosis and patch
6596 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
6597 Bugfix on 0.2.0.20-rc.
6600 Changes in version 0.2.0.20-rc - 2008-02-24
6601 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
6602 makes more progress towards normalizing Tor's TLS handshake, makes
6603 hidden services work better again, helps relays bootstrap if they don't
6604 know their IP address, adds optional support for linking in openbsd's
6605 allocator or tcmalloc, allows really fast relays to scale past 15000
6606 sockets, and fixes a bunch of minor bugs reported by Veracode.
6609 - Enable the revised TLS handshake based on the one designed by
6610 Steven Murdoch in proposal 124, as revised in proposal 130. It
6611 includes version negotiation for OR connections as described in
6612 proposal 105. The new handshake is meant to be harder for censors
6613 to fingerprint, and it adds the ability to detect certain kinds of
6614 man-in-the-middle traffic analysis attacks. The version negotiation
6615 feature will allow us to improve Tor's link protocol more safely
6617 - Choose which bridge to use proportional to its advertised bandwidth,
6618 rather than uniformly at random. This should speed up Tor for
6619 bridge users. Also do this for people who set StrictEntryNodes.
6620 - When a TrackHostExits-chosen exit fails too many times in a row,
6621 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
6624 - Resolved problems with (re-)fetching hidden service descriptors.
6625 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
6627 - If we only ever used Tor for hidden service lookups or posts, we
6628 would stop building circuits and start refusing connections after
6629 24 hours, since we falsely believed that Tor was dormant. Reported
6630 by nwf; bugfix on 0.1.2.x.
6631 - Servers that don't know their own IP address should go to the
6632 authorities for their first directory fetch, even if their DirPort
6633 is off or if they don't know they're reachable yet. This will help
6634 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
6635 - When counting the number of open sockets, count not only the number
6636 of sockets we have received from the socket() call, but also
6637 the number we've gotten from accept() and socketpair(). This bug
6638 made us fail to count all sockets that we were using for incoming
6639 connections. Bugfix on 0.2.0.x.
6640 - Fix code used to find strings within buffers, when those strings
6641 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
6642 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
6643 - Add a new __HashedControlSessionPassword option for controllers
6644 to use for one-off session password hashes that shouldn't get
6645 saved to disk by SAVECONF --- Vidalia users were accumulating a
6646 pile of HashedControlPassword lines in their torrc files, one for
6647 each time they had restarted Tor and then clicked Save. Make Tor
6648 automatically convert "HashedControlPassword" to this new option but
6649 only when it's given on the command line. Partial fix for bug 586.
6651 o Minor features (performance):
6652 - Tune parameters for cell pool allocation to minimize amount of
6654 - Add OpenBSD malloc code from phk as an optional malloc
6655 replacement on Linux: some glibc libraries do very poorly
6656 with Tor's memory allocation patterns. Pass
6657 --enable-openbsd-malloc to get the replacement malloc code.
6658 - Add a --with-tcmalloc option to the configure script to link
6659 against tcmalloc (if present). Does not yet search for
6660 non-system include paths.
6661 - Stop imposing an arbitrary maximum on the number of file descriptors
6662 used for busy servers. Bug reported by Olaf Selke; patch from
6665 o Minor features (other):
6666 - When SafeLogging is disabled, log addresses along with all TLS
6668 - When building with --enable-gcc-warnings, check for whether Apple's
6669 warning "-Wshorten-64-to-32" is available.
6670 - Add a --passphrase-fd argument to the tor-gencert command for
6673 o Minor bugfixes (memory leaks and code problems):
6674 - We were leaking a file descriptor if Tor started with a zero-length
6675 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
6676 - Detect size overflow in zlib code. Reported by Justin Ferguson and
6678 - We were comparing the raw BridgePassword entry with a base64'ed
6679 version of it, when handling a "/tor/networkstatus-bridges"
6680 directory request. Now compare correctly. Noticed by Veracode.
6681 - Recover from bad tracked-since value in MTBF-history file.
6683 - Alter the code that tries to recover from unhandled write
6684 errors, to not try to flush onto a socket that's given us
6685 unhandled errors. Bugfix on 0.1.2.x.
6686 - Make Unix controlsockets work correctly on OpenBSD. Patch from
6687 tup. Bugfix on 0.2.0.3-alpha.
6689 o Minor bugfixes (other):
6690 - If we have an extra-info document for our server, always make
6691 it available on the control port, even if we haven't gotten
6692 a copy of it from an authority yet. Patch from mwenge.
6693 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
6694 - Directory mirrors no longer include a guess at the client's IP
6695 address if the connection appears to be coming from the same /24
6696 network; it was producing too many wrong guesses.
6697 - Make the new hidden service code respect the SafeLogging setting.
6698 Bugfix on 0.2.0.x. Patch from Karsten.
6699 - When starting as an authority, do not overwrite all certificates
6700 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
6701 - If we're trying to flush the last bytes on a connection (for
6702 example, when answering a directory request), reset the
6703 time-to-give-up timeout every time we manage to write something
6704 on the socket. Bugfix on 0.1.2.x.
6705 - Change the behavior of "getinfo status/good-server-descriptor"
6706 so it doesn't return failure when any authority disappears.
6707 - Even though the man page said that "TrackHostExits ." should
6708 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
6709 - Report TLS "zero return" case as a "clean close" and "IO error"
6710 as a "close". Stop calling closes "unexpected closes": existing
6711 Tors don't use SSL_close(), so having a connection close without
6712 the TLS shutdown handshake is hardly unexpected.
6713 - Send NAMESERVER_STATUS messages for a single failed nameserver
6716 o Code simplifications and refactoring:
6717 - Remove the tor_strpartition function: its logic was confused,
6718 and it was only used for one thing that could be implemented far
6722 Changes in version 0.2.0.19-alpha - 2008-02-09
6723 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
6724 handshake, makes path selection for relays more secure and IP address
6725 guessing more robust, and generally fixes a lot of bugs in preparation
6726 for calling the 0.2.0 branch stable.
6729 - Do not include recognizeable strings in the commonname part of
6730 Tor's x509 certificates.
6733 - If we're a relay, avoid picking ourselves as an introduction point,
6734 a rendezvous point, or as the final hop for internal circuits. Bug
6735 reported by taranis and lodger. Bugfix on 0.1.2.x.
6736 - Patch from "Andrew S. Lists" to catch when we contact a directory
6737 mirror at IP address X and he says we look like we're coming from
6738 IP address X. Bugfix on 0.1.2.x.
6740 o Minor features (security):
6741 - Be more paranoid about overwriting sensitive memory on free(),
6742 as a defensive programming tactic to ensure forward secrecy.
6744 o Minor features (directory authority):
6745 - Actually validate the options passed to AuthDirReject,
6746 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
6747 - Reject router descriptors with out-of-range bandwidthcapacity or
6748 bandwidthburst values.
6750 o Minor features (controller):
6751 - Reject controller commands over 1MB in length. This keeps rogue
6752 processes from running us out of memory.
6754 o Minor features (misc):
6755 - Give more descriptive well-formedness errors for out-of-range
6756 hidden service descriptor/protocol versions.
6757 - Make memory debugging information describe more about history
6758 of cell allocation, so we can help reduce our memory use.
6760 o Deprecated features (controller):
6761 - The status/version/num-versioning and status/version/num-concurring
6762 GETINFO options are no longer useful in the v3 directory protocol:
6763 treat them as deprecated, and warn when they're used.
6766 - When our consensus networkstatus has been expired for a while, stop
6767 being willing to build circuits using it. Fixes bug 401. Bugfix
6769 - Directory caches now fetch certificates from all authorities
6770 listed in a networkstatus consensus, even when they do not
6771 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
6772 - When connecting to a bridge without specifying its key, insert
6773 the connection into the identity-to-connection map as soon as
6774 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
6775 - Detect versions of OS X where malloc_good_size() is present in the
6776 library but never actually declared. Resolves bug 587. Bugfix
6778 - Stop incorrectly truncating zlib responses to directory authority
6779 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
6780 - Stop recommending that every server operator send mail to tor-ops.
6781 Resolves bug 597. Bugfix on 0.1.2.x.
6782 - Don't trigger an assert if we start a directory authority with a
6783 private IP address (like 127.0.0.1).
6784 - Avoid possible failures when generating a directory with routers
6785 with over-long versions strings, or too many flags set. Bugfix
6787 - If an attempt to launch a DNS resolve request over the control
6788 port fails because we have overrun the limit on the number of
6789 connections, tell the controller that the request has failed.
6790 - Avoid using too little bandwidth when our clock skips a few
6791 seconds. Bugfix on 0.1.2.x.
6792 - Fix shell error when warning about missing packages in configure
6793 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
6794 - Do not become confused when receiving a spurious VERSIONS-like
6795 cell from a confused v1 client. Bugfix on 0.2.0.x.
6796 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
6797 introduction points for a hidden service have failed. Patch from
6798 Karsten Loesing. Bugfix on 0.2.0.x.
6800 o Code simplifications and refactoring:
6801 - Remove some needless generality from cpuworker code, for improved
6803 - Stop overloading the circuit_t.onionskin field for both "onionskin
6804 from a CREATE cell that we are waiting for a cpuworker to be
6805 assigned" and "onionskin from an EXTEND cell that we are going to
6806 send to an OR as soon as we are connected". Might help with bug 600.
6807 - Add an in-place version of aes_crypt() so that we can avoid doing a
6808 needless memcpy() call on each cell payload.
6811 Changes in version 0.2.0.18-alpha - 2008-01-25
6812 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
6813 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
6814 that can warn or reject connections to ports generally associated with
6815 vulnerable-plaintext protocols.
6817 o New directory authorities:
6818 - Set up dannenberg (run by CCC) as the sixth v3 directory
6822 - Fix a major memory leak when attempting to use the v2 TLS
6823 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
6824 - We accidentally enabled the under-development v2 TLS handshake
6825 code, which was causing log entries like "TLS error while
6826 renegotiating handshake". Disable it again. Resolves bug 590.
6827 - We were computing the wrong Content-Length: header for directory
6828 responses that need to be compressed on the fly, causing clients
6829 asking for those items to always fail. Bugfix on 0.2.0.x; partially
6833 - Avoid going directly to the directory authorities even if you're a
6834 relay, if you haven't found yourself reachable yet or if you've
6835 decided not to advertise your dirport yet. Addresses bug 556.
6836 - If we've gone 12 hours since our last bandwidth check, and we
6837 estimate we have less than 50KB bandwidth capacity but we could
6838 handle more, do another bandwidth test.
6839 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
6840 Tor can warn and/or refuse connections to ports commonly used with
6841 vulnerable-plaintext protocols. Currently we warn on ports 23,
6842 109, 110, and 143, but we don't reject any.
6845 - When we setconf ClientOnly to 1, close any current OR and Dir
6846 listeners. Reported by mwenge.
6847 - When we get a consensus that's been signed by more people than
6848 we expect, don't log about it; it's not a big deal. Reported
6852 - Don't answer "/tor/networkstatus-bridges" directory requests if
6853 the request isn't encrypted.
6854 - Make "ClientOnly 1" config option disable directory ports too.
6855 - Patches from Karsten Loesing to make v2 hidden services more
6856 robust: work even when there aren't enough HSDir relays available;
6857 retry when a v2 rend desc fetch fails; but don't retry if we
6858 already have a usable v0 rend desc.
6861 Changes in version 0.2.0.17-alpha - 2008-01-17
6862 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
6865 - Make the tor-gencert man page get included correctly in the tarball.
6868 Changes in version 0.2.0.16-alpha - 2008-01-17
6869 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
6870 Loesing, and generally cleans up a lot of features and minor bugs.
6872 o New directory authorities:
6873 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
6876 o Major performance improvements:
6877 - Switch our old ring buffer implementation for one more like that
6878 used by free Unix kernels. The wasted space in a buffer with 1mb
6879 of data will now be more like 8k than 1mb. The new implementation
6880 also avoids realloc();realloc(); patterns that can contribute to
6881 memory fragmentation.
6884 - Configuration files now accept C-style strings as values. This
6885 helps encode characters not allowed in the current configuration
6886 file format, such as newline or #. Addresses bug 557.
6887 - Although we fixed bug 539 (where servers would send HTTP status 503
6888 responses _and_ send a body too), there are still servers out
6889 there that haven't upgraded. Therefore, make clients parse such
6890 bodies when they receive them.
6891 - When we're not serving v2 directory information, there is no reason
6892 to actually keep any around. Remove the obsolete files and directory
6893 on startup if they are very old and we aren't going to serve them.
6895 o Minor performance improvements:
6896 - Reference-count and share copies of address policy entries; only 5%
6897 of them were actually distinct.
6898 - Never walk through the list of logs if we know that no log is
6899 interested in a given message.
6902 - When an authority has not signed a consensus, do not try to
6903 download a nonexistent "certificate with key 00000000". Bugfix
6904 on 0.2.0.x. Fixes bug 569.
6905 - Fix a rare assert error when we're closing one of our threads:
6906 use a mutex to protect the list of logs, so we never write to the
6907 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
6908 bug 575, which is kind of the revenge of bug 222.
6909 - Patch from Karsten Loesing to complain less at both the client
6910 and the relay when a relay used to have the HSDir flag but doesn't
6911 anymore, and we try to upload a hidden service descriptor.
6912 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
6914 - Do not try to download missing certificates until we have tried
6915 to check our fallback consensus. Fixes bug 583.
6916 - Make bridges round reported GeoIP stats info up to the nearest
6917 estimate, not down. Now we can distinguish between "0 people from
6918 this country" and "1 person from this country".
6919 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
6920 - Avoid possible segfault if key generation fails in
6921 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
6922 - Avoid segfault in the case where a badly behaved v2 versioning
6923 directory sends a signed networkstatus with missing client-versions.
6925 - Avoid segfaults on certain complex invocations of
6926 router_get_by_hexdigest(). Bugfix on 0.1.2.
6927 - Correct bad index on array access in parse_http_time(). Bugfix
6929 - Fix possible bug in vote generation when server versions are present
6930 but client versions are not.
6931 - Fix rare bug on REDIRECTSTREAM control command when called with no
6932 port set: it could erroneously report an error when none had
6934 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
6935 compressing large objects and find ourselves with more than 4k
6936 left over. Bugfix on 0.2.0.
6937 - Fix a small memory leak when setting up a hidden service.
6938 - Fix a few memory leaks that could in theory happen under bizarre
6940 - Fix an assert if we post a general-purpose descriptor via the
6941 control port but that descriptor isn't mentioned in our current
6942 network consensus. Bug reported by Jon McLachlan; bugfix on
6945 o Minor features (controller):
6946 - Get NS events working again. Patch from tup.
6947 - The GETCONF command now escapes and quotes configuration values
6948 that don't otherwise fit into the torrc file.
6949 - The SETCONF command now handles quoted values correctly.
6951 o Minor features (directory authorities):
6952 - New configuration options to override default maximum number of
6953 servers allowed on a single IP address. This is important for
6954 running a test network on a single host.
6955 - Actually implement the -s option to tor-gencert.
6956 - Add a manual page for tor-gencert.
6958 o Minor features (bridges):
6959 - Bridge authorities no longer serve bridge descriptors over
6960 unencrypted connections.
6962 o Minor features (other):
6963 - Add hidden services and DNSPorts to the list of things that make
6964 Tor accept that it has running ports. Change starting Tor with no
6965 ports from a fatal error to a warning; we might change it back if
6966 this turns out to confuse anybody. Fixes bug 579.
6969 Changes in version 0.1.2.19 - 2008-01-17
6970 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
6971 exit policy a little bit more conservative so it's safer to run an
6972 exit relay on a home system, and fixes a variety of smaller issues.
6975 - Exit policies now reject connections that are addressed to a
6976 relay's public (external) IP address too, unless
6977 ExitPolicyRejectPrivate is turned off. We do this because too
6978 many relays are running nearby to services that trust them based
6982 - When the clock jumps forward a lot, do not allow the bandwidth
6983 buckets to become negative. Fixes bug 544.
6984 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
6985 on every successful resolve. Reported by Mike Perry.
6986 - Purge old entries from the "rephist" database and the hidden
6987 service descriptor database even when DirPort is zero.
6988 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
6989 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
6990 crashing or mis-answering these requests.
6991 - When we decide to send a 503 response to a request for servers, do
6992 not then also send the server descriptors: this defeats the whole
6993 purpose. Fixes bug 539.
6996 - Changing the ExitPolicyRejectPrivate setting should cause us to
6997 rebuild our server descriptor.
6998 - Fix handling of hex nicknames when answering controller requests for
6999 networkstatus by name, or when deciding whether to warn about
7000 unknown routers in a config option. (Patch from mwenge.)
7001 - Fix a couple of hard-to-trigger autoconf problems that could result
7002 in really weird results on platforms whose sys/types.h files define
7003 nonstandard integer types.
7004 - Don't try to create the datadir when running --verify-config or
7005 --hash-password. Resolves bug 540.
7006 - If we were having problems getting a particular descriptor from the
7007 directory caches, and then we learned about a new descriptor for
7008 that router, we weren't resetting our failure count. Reported
7010 - Although we fixed bug 539 (where servers would send HTTP status 503
7011 responses _and_ send a body too), there are still servers out there
7012 that haven't upgraded. Therefore, make clients parse such bodies
7013 when they receive them.
7014 - Run correctly on systems where rlim_t is larger than unsigned long.
7015 This includes some 64-bit systems.
7016 - Run correctly on platforms (like some versions of OS X 10.5) where
7017 the real limit for number of open files is OPEN_FILES, not rlim_max
7018 from getrlimit(RLIMIT_NOFILES).
7019 - Avoid a spurious free on base64 failure.
7020 - Avoid segfaults on certain complex invocations of
7021 router_get_by_hexdigest().
7022 - Fix rare bug on REDIRECTSTREAM control command when called with no
7023 port set: it could erroneously report an error when none had
7027 Changes in version 0.2.0.15-alpha - 2007-12-25
7028 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
7029 features added in 0.2.0.13-alpha.
7032 - Fix several remotely triggerable asserts based on DirPort requests
7033 for a v2 or v3 networkstatus object before we were prepared. This
7034 was particularly bad for 0.2.0.13 and later bridge relays, who
7035 would never have a v2 networkstatus and would thus always crash
7036 when used. Bugfixes on 0.2.0.x.
7037 - Estimate the v3 networkstatus size more accurately, rather than
7038 estimating it at zero bytes and giving it artificially high priority
7039 compared to other directory requests. Bugfix on 0.2.0.x.
7042 - Fix configure.in logic for cross-compilation.
7043 - When we load a bridge descriptor from the cache, and it was
7044 previously unreachable, mark it as retriable so we won't just
7045 ignore it. Also, try fetching a new copy immediately. Bugfixes
7047 - The bridge GeoIP stats were counting other relays, for example
7048 self-reachability and authority-reachability tests.
7051 - Support compilation to target iPhone; patch from cjacker huang.
7052 To build for iPhone, pass the --enable-iphone option to configure.
7055 Changes in version 0.2.0.14-alpha - 2007-12-23
7057 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
7058 without a datadirectory from a previous Tor install. Reported
7060 - Fix a crash when we fetch a descriptor that turns out to be
7061 unexpected (it used to be in our networkstatus when we started
7062 fetching it, but it isn't in our current networkstatus), and we
7063 aren't using bridges. Bugfix on 0.2.0.x.
7064 - Fix a crash when accessing hidden services: it would work the first
7065 time you use a given introduction point for your service, but
7066 on subsequent requests we'd be using garbage memory. Fixed by
7067 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
7068 - Fix a crash when we load a bridge descriptor from disk but we don't
7069 currently have a Bridge line for it in our torrc. Bugfix on
7073 - If bridge authorities set BridgePassword, they will serve a
7074 snapshot of known bridge routerstatuses from their DirPort to
7075 anybody who knows that password. Unset by default.
7078 - Make the unit tests build again.
7079 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
7080 - Make PublishServerDescriptor default to 1, so the default doesn't
7081 have to change as we invent new directory protocol versions.
7082 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
7083 be included unless sys/time.h is already included. Fixes
7084 bug 553. Bugfix on 0.2.0.x.
7085 - If we receive a general-purpose descriptor and then receive an
7086 identical bridge-purpose descriptor soon after, don't discard
7087 the next one as a duplicate.
7090 - If BridgeRelay is set to 1, then the default for
7091 PublishServerDescriptor is now "bridge" rather than "v2,v3".
7092 - If the user sets RelayBandwidthRate but doesn't set
7093 RelayBandwidthBurst, then make them equal rather than erroring out.
7096 Changes in version 0.2.0.13-alpha - 2007-12-21
7097 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
7098 Goodell, fixes many more bugs, and adds a lot of infrastructure for
7101 o New directory authorities:
7102 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
7106 - Only update guard status (usable / not usable) once we have
7107 enough directory information. This was causing us to always pick
7108 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
7109 causing us to discard all our guards on startup if we hadn't been
7110 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
7111 - Purge old entries from the "rephist" database and the hidden
7112 service descriptor databases even when DirPort is zero. Bugfix
7114 - We were ignoring our RelayBandwidthRate for the first 30 seconds
7115 after opening a circuit -- even a relayed circuit. Bugfix on
7117 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
7118 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
7119 crashing or mis-answering these types of requests.
7120 - Relays were publishing their server descriptor to v1 and v2
7121 directory authorities, but they didn't try publishing to v3-only
7122 authorities. Fix this; and also stop publishing to v1 authorities.
7124 - When we were reading router descriptors from cache, we were ignoring
7125 the annotations -- so for example we were reading in bridge-purpose
7126 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
7127 - When we decided to send a 503 response to a request for servers, we
7128 were then also sending the server descriptors: this defeats the
7129 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
7132 - Bridge relays now behave like clients with respect to time
7133 intervals for downloading new consensus documents -- otherwise they
7134 stand out. Bridge users now wait until the end of the interval,
7135 so their bridge relay will be sure to have a new consensus document.
7136 - Three new config options (AlternateDirAuthority,
7137 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
7138 user selectively replace the default directory authorities by type,
7139 rather than the all-or-nothing replacement that DirServer offers.
7140 - Tor can now be configured to read a GeoIP file from disk in one
7141 of two formats. This can be used by controllers to map IP addresses
7142 to countries. Eventually, it may support exit-by-country.
7143 - When possible, bridge relays remember which countries users
7144 are coming from, and report aggregate information in their
7145 extra-info documents, so that the bridge authorities can learn
7146 where Tor is blocked.
7147 - Bridge directory authorities now do reachability testing on the
7148 bridges they know. They provide router status summaries to the
7149 controller via "getinfo ns/purpose/bridge", and also dump summaries
7150 to a file periodically.
7151 - Stop fetching directory info so aggressively if your DirPort is
7152 on but your ORPort is off; stop fetching v2 dir info entirely.
7153 You can override these choices with the new FetchDirInfoEarly
7157 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
7158 consensus documents when there are too many relays at a single
7159 IP address. Now clear it in v2 network status documents too, and
7160 also clear it in routerinfo_t when the relay is no longer listed
7161 in the relevant networkstatus document.
7162 - Don't crash if we get an unexpected value for the
7163 PublishServerDescriptor config option. Reported by Matt Edman;
7164 bugfix on 0.2.0.9-alpha.
7165 - Our new v2 hidden service descriptor format allows descriptors
7166 that have no introduction points. But Tor crashed when we tried
7167 to build a descriptor with no intro points (and it would have
7168 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
7170 - Fix building with dmalloc 5.5.2 with glibc.
7171 - Reject uploaded descriptors and extrainfo documents if they're
7172 huge. Otherwise we'll cache them all over the network and it'll
7173 clog everything up. Reported by Aljosha Judmayer.
7174 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
7175 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
7176 - When the DANGEROUS_VERSION controller status event told us we're
7177 running an obsolete version, it used the string "OLD" to describe
7178 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
7179 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
7180 - If we can't expand our list of entry guards (e.g. because we're
7181 using bridges or we have StrictEntryNodes set), don't mark relays
7182 down when they fail a directory request. Otherwise we're too quick
7183 to mark all our entry points down. Bugfix on 0.1.2.x.
7184 - Fix handling of hex nicknames when answering controller requests for
7185 networkstatus by name, or when deciding whether to warn about unknown
7186 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
7187 - Fix a couple of hard-to-trigger autoconf problems that could result
7188 in really weird results on platforms whose sys/types.h files define
7189 nonstandard integer types. Bugfix on 0.1.2.x.
7190 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
7191 - Don't crash on name lookup when we have no current consensus. Fixes
7192 bug 538; bugfix on 0.2.0.x.
7193 - Only Tors that want to mirror the v2 directory info should
7194 create the "cached-status" directory in their datadir. (All Tors
7195 used to create it.) Bugfix on 0.2.0.9-alpha.
7196 - Directory authorities should only automatically download Extra Info
7197 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
7200 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
7201 consumers. (We already do this on HUP.)
7202 - Authorities and caches fetch the v2 networkstatus documents
7203 less often, now that v3 is encouraged.
7204 - Add a new config option BridgeRelay that specifies you want to
7205 be a bridge relay. Right now the only difference is that it makes
7206 you answer begin_dir requests, and it makes you cache dir info,
7207 even if your DirPort isn't on.
7208 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
7209 ask about source, timestamp of arrival, purpose, etc. We need
7210 something like this to help Vidalia not do GeoIP lookups on bridge
7212 - Allow multiple HashedControlPassword config lines, to support
7213 multiple controller passwords.
7214 - Authorities now decide whether they're authoritative for a given
7215 router based on the router's purpose.
7216 - New config options AuthDirBadDir and AuthDirListBadDirs for
7217 authorities to mark certain relays as "bad directories" in the
7218 networkstatus documents. Also supports the "!baddir" directive in
7219 the approved-routers file.
7222 Changes in version 0.2.0.12-alpha - 2007-11-16
7223 This twelfth development snapshot fixes some more build problems as
7224 well as a few minor bugs.
7227 - Make it build on OpenBSD again. Patch from tup.
7228 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
7229 package-building for Red Hat, OS X, etc.
7231 o Minor bugfixes (on 0.1.2.x):
7232 - Changing the ExitPolicyRejectPrivate setting should cause us to
7233 rebuild our server descriptor.
7235 o Minor bugfixes (on 0.2.0.x):
7236 - When we're lacking a consensus, don't try to perform rendezvous
7237 operations. Reported by Karsten Loesing.
7238 - Fix a small memory leak whenever we decide against using a
7239 newly picked entry guard. Reported by Mike Perry.
7240 - When authorities detected more than two relays running on the same
7241 IP address, they were clearing all the status flags but forgetting
7242 to clear the "hsdir" flag. So clients were being told that a
7243 given relay was the right choice for a v2 hsdir lookup, yet they
7244 never had its descriptor because it was marked as 'not running'
7246 - If we're trying to fetch a bridge descriptor and there's no way
7247 the bridge authority could help us (for example, we don't know
7248 a digest, or there is no bridge authority), don't be so eager to
7249 fall back to asking the bridge authority.
7250 - If we're using bridges or have strictentrynodes set, and our
7251 chosen exit is in the same family as all our bridges/entry guards,
7252 then be flexible about families.
7255 - When we negotiate a v2 link-layer connection (not yet implemented),
7256 accept RELAY_EARLY cells and turn them into RELAY cells if we've
7257 negotiated a v1 connection for their next step. Initial code for
7261 Changes in version 0.2.0.11-alpha - 2007-11-12
7262 This eleventh development snapshot fixes some build problems with
7263 the previous snapshot. It also includes a more secure-by-default exit
7264 policy for relays, fixes an enormous memory leak for exit relays, and
7265 fixes another bug where servers were falling out of the directory list.
7268 - Exit policies now reject connections that are addressed to a
7269 relay's public (external) IP address too, unless
7270 ExitPolicyRejectPrivate is turned off. We do this because too
7271 many relays are running nearby to services that trust them based
7272 on network address. Bugfix on 0.1.2.x.
7275 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
7276 on every successful resolve. Reported by Mike Perry; bugfix
7278 - On authorities, never downgrade to old router descriptors simply
7279 because they're listed in the consensus. This created a catch-22
7280 where we wouldn't list a new descriptor because there was an
7281 old one in the consensus, and we couldn't get the new one in the
7282 consensus because we wouldn't list it. Possible fix for bug 548.
7283 Also, this might cause bug 543 to appear on authorities; if so,
7284 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
7286 o Packaging fixes on 0.2.0.10-alpha:
7287 - We were including instructions about what to do with the
7288 src/config/fallback-consensus file, but we weren't actually
7289 including it in the tarball. Disable all of that for now.
7292 - Allow people to say PreferTunnelledDirConns rather than
7293 PreferTunneledDirConns, for those alternate-spellers out there.
7296 - Don't reevaluate all the information from our consensus document
7297 just because we've downloaded a v2 networkstatus that we intend
7298 to cache. Fixes bug 545; bugfix on 0.2.0.x.
7301 Changes in version 0.2.0.10-alpha - 2007-11-10
7302 This tenth development snapshot adds a third v3 directory authority
7303 run by Mike Perry, adds most of Karsten Loesing's new hidden service
7304 descriptor format, fixes a bad crash bug and new bridge bugs introduced
7305 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
7306 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
7307 addresses many more minor issues.
7309 o New directory authorities:
7310 - Set up ides (run by Mike Perry) as the third v3 directory authority.
7313 - Allow tunnelled directory connections to ask for an encrypted
7314 "begin_dir" connection or an anonymized "uses a full Tor circuit"
7315 connection independently. Now we can make anonymized begin_dir
7316 connections for (e.g.) more secure hidden service posting and
7318 - More progress on proposal 114: code from Karsten Loesing to
7319 implement new hidden service descriptor format.
7320 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
7321 accommodate the growing number of servers that use the default
7322 and are reaching it.
7323 - Directory authorities use a new formula for selecting which nodes
7324 to advertise as Guards: they must be in the top 7/8 in terms of
7325 how long we have known about them, and above the median of those
7326 nodes in terms of weighted fractional uptime.
7327 - Make "not enough dir info yet" warnings describe *why* Tor feels
7328 it doesn't have enough directory info yet.
7331 - Stop servers from crashing if they set a Family option (or
7332 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
7334 - Make bridge users work again -- the move to v3 directories in
7335 0.2.0.9-alpha had introduced a number of bugs that made bridges
7336 no longer work for clients.
7337 - When the clock jumps forward a lot, do not allow the bandwidth
7338 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
7340 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
7341 - When the consensus lists a router descriptor that we previously were
7342 mirroring, but that we considered non-canonical, reload the
7343 descriptor as canonical. This fixes bug 543 where Tor servers
7344 would start complaining after a few days that they don't have
7345 enough directory information to build a circuit.
7346 - Consider replacing the current consensus when certificates arrive
7347 that make the pending consensus valid. Previously, we were only
7348 considering replacement when the new certs _didn't_ help.
7349 - Fix an assert error on startup if we didn't already have the
7350 consensus and certs cached in our datadirectory: we were caching
7351 the consensus in consensus_waiting_for_certs but then free'ing it
7353 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
7354 Request) if we need more v3 certs but we've already got pending
7355 requests for all of them.
7356 - Correctly back off from failing certificate downloads. Fixes
7358 - Authorities don't vote on the Running flag if they have been running
7359 for less than 30 minutes themselves. Fixes bug 547, where a newly
7360 started authority would vote that everyone was down.
7363 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
7364 it, it had no AES, and it hasn't seen any security patches since
7368 - Clients now hold circuitless TLS connections open for 1.5 times
7369 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
7370 rebuild a new circuit over them within that timeframe. Previously,
7371 they held them open only for KeepalivePeriod (5 minutes).
7372 - Use "If-Modified-Since" to avoid retrieving consensus
7373 networkstatuses that we already have.
7374 - When we have no consensus, check FallbackNetworkstatusFile (defaults
7375 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
7376 we start knowing some directory caches.
7377 - When we receive a consensus from the future, warn about skew.
7378 - Improve skew reporting: try to give the user a better log message
7379 about how skewed they are, and how much this matters.
7380 - When we have a certificate for an authority, believe that
7381 certificate's claims about the authority's IP address.
7382 - New --quiet command-line option to suppress the default console log.
7383 Good in combination with --hash-password.
7384 - Authorities send back an X-Descriptor-Not-New header in response to
7385 an accepted-but-discarded descriptor upload. Partially implements
7387 - Make the log message for "tls error. breaking." more useful.
7388 - Better log messages about certificate downloads, to attempt to
7389 track down the second incarnation of bug 546.
7391 o Minor features (bridges):
7392 - If bridge users set UpdateBridgesFromAuthority, but the digest
7393 they ask for is a 404 from the bridge authority, they now fall
7394 back to trying the bridge directly.
7395 - Bridges now use begin_dir to publish their server descriptor to
7396 the bridge authority, even when they haven't set TunnelDirConns.
7398 o Minor features (controller):
7399 - When reporting clock skew, and we know that the clock is _at least
7400 as skewed_ as some value, but we don't know the actual value,
7401 report the value as a "minimum skew."
7404 - Update linux-tor-prio.sh script to allow QoS based on the uid of
7405 the Tor process. Patch from Marco Bonetti with tweaks from Mike
7409 - Refuse to start if both ORPort and UseBridges are set. Bugfix
7410 on 0.2.0.x, suggested by Matt Edman.
7411 - Don't stop fetching descriptors when FetchUselessDescriptors is
7412 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
7413 reported by tup and ioerror.
7414 - Better log message on vote from unknown authority.
7415 - Don't log "Launching 0 request for 0 router" message.
7417 o Minor bugfixes (memory leaks):
7418 - Stop leaking memory every time we parse a v3 certificate. Bugfix
7420 - Stop leaking memory every time we load a v3 certificate. Bugfix
7421 on 0.2.0.1-alpha. Fixes bug 536.
7422 - Stop leaking a cached networkstatus on exit. Bugfix on
7424 - Stop leaking voter information every time we free a consensus.
7425 Bugfix on 0.2.0.3-alpha.
7426 - Stop leaking signed data every time we check a voter signature.
7427 Bugfix on 0.2.0.3-alpha.
7428 - Stop leaking a signature every time we fail to parse a consensus or
7429 a vote. Bugfix on 0.2.0.3-alpha.
7430 - Stop leaking v2_download_status_map on shutdown. Bugfix on
7432 - Stop leaking conn->nickname every time we make a connection to a
7433 Tor relay without knowing its expected identity digest (e.g. when
7434 using bridges). Bugfix on 0.2.0.3-alpha.
7436 - Minor bugfixes (portability):
7437 - Run correctly on platforms where rlim_t is larger than unsigned
7438 long, and/or where the real limit for number of open files is
7439 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
7440 particular, these may be needed for OS X 10.5.
7443 Changes in version 0.1.2.18 - 2007-10-28
7444 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
7445 hidden service introduction that were causing huge delays, and a big
7446 bug that was causing some servers to disappear from the network status
7447 lists for a few hours each day.
7449 o Major bugfixes (crashes):
7450 - If a connection is shut down abruptly because of something that
7451 happened inside connection_flushed_some(), do not call
7452 connection_finished_flushing(). Should fix bug 451:
7453 "connection_stop_writing: Assertion conn->write_event failed"
7454 Bugfix on 0.1.2.7-alpha.
7455 - Fix possible segfaults in functions called from
7456 rend_process_relay_cell().
7458 o Major bugfixes (hidden services):
7459 - Hidden services were choosing introduction points uniquely by
7460 hexdigest, but when constructing the hidden service descriptor
7461 they merely wrote the (potentially ambiguous) nickname.
7462 - Clients now use the v2 intro format for hidden service
7463 connections: they specify their chosen rendezvous point by identity
7464 digest rather than by (potentially ambiguous) nickname. These
7465 changes could speed up hidden service connections dramatically.
7467 o Major bugfixes (other):
7468 - Stop publishing a new server descriptor just because we get a
7469 HUP signal. This led (in a roundabout way) to some servers getting
7470 dropped from the networkstatus lists for a few hours each day.
7471 - When looking for a circuit to cannibalize, consider family as well
7472 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
7473 circuit cannibalization).
7474 - When a router wasn't listed in a new networkstatus, we were leaving
7475 the flags for that router alone -- meaning it remained Named,
7476 Running, etc -- even though absence from the networkstatus means
7477 that it shouldn't be considered to exist at all anymore. Now we
7478 clear all the flags for routers that fall out of the networkstatus
7479 consensus. Fixes bug 529.
7482 - Don't try to access (or alter) the state file when running
7483 --list-fingerprint or --verify-config or --hash-password. Resolves
7485 - When generating information telling us how to extend to a given
7486 router, do not try to include the nickname if it is
7487 absent. Resolves bug 467.
7488 - Fix a user-triggerable segfault in expand_filename(). (There isn't
7489 a way to trigger this remotely.)
7490 - When sending a status event to the controller telling it that an
7491 OR address is reachable, set the port correctly. (Previously we
7492 were reporting the dir port.)
7493 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
7494 command. Bugfix on 0.1.2.17.
7495 - When loading bandwidth history, do not believe any information in
7496 the future. Fixes bug 434.
7497 - When loading entry guard information, do not believe any information
7499 - When we have our clock set far in the future and generate an
7500 onion key, then re-set our clock to be correct, we should not stop
7501 the onion key from getting rotated.
7502 - On some platforms, accept() can return a broken address. Detect
7503 this more quietly, and deal accordingly. Fixes bug 483.
7504 - It's not actually an error to find a non-pending entry in the DNS
7505 cache when canceling a pending resolve. Don't log unless stuff
7506 is fishy. Resolves bug 463.
7507 - Don't reset trusted dir server list when we set a configuration
7508 option. Patch from Robert Hogan.
7509 - Don't try to create the datadir when running --verify-config or
7510 --hash-password. Resolves bug 540.
7513 Changes in version 0.2.0.9-alpha - 2007-10-24
7514 This ninth development snapshot switches clients to the new v3 directory
7515 system; allows servers to be listed in the network status even when they
7516 have the same nickname as a registered server; and fixes many other
7517 bugs including a big one that was causing some servers to disappear
7518 from the network status lists for a few hours each day.
7520 o Major features (directory system):
7521 - Clients now download v3 consensus networkstatus documents instead
7522 of v2 networkstatus documents. Clients and caches now base their
7523 opinions about routers on these consensus documents. Clients only
7524 download router descriptors listed in the consensus.
7525 - Authorities now list servers who have the same nickname as
7526 a different named server, but list them with a new flag,
7527 "Unnamed". Now we can list servers that happen to pick the same
7528 nickname as a server that registered two years ago and then
7529 disappeared. Partially implements proposal 122.
7530 - If the consensus lists a router as "Unnamed", the name is assigned
7531 to a different router: do not identify the router by that name.
7532 Partially implements proposal 122.
7533 - Authorities can now come to a consensus on which method to use to
7534 compute the consensus. This gives us forward compatibility.
7537 - Stop publishing a new server descriptor just because we HUP or
7538 when we find our DirPort to be reachable but won't actually publish
7539 it. New descriptors without any real changes are dropped by the
7540 authorities, and can screw up our "publish every 18 hours" schedule.
7542 - When a router wasn't listed in a new networkstatus, we were leaving
7543 the flags for that router alone -- meaning it remained Named,
7544 Running, etc -- even though absence from the networkstatus means
7545 that it shouldn't be considered to exist at all anymore. Now we
7546 clear all the flags for routers that fall out of the networkstatus
7547 consensus. Fixes bug 529; bugfix on 0.1.2.x.
7548 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
7549 extrainfo documents and then discard them immediately for not
7550 matching the latest router. Bugfix on 0.2.0.1-alpha.
7552 o Minor features (v3 directory protocol):
7553 - Allow tor-gencert to generate a new certificate without replacing
7555 - Allow certificates to include an address.
7556 - When we change our directory-cache settings, reschedule all voting
7557 and download operations.
7558 - Reattempt certificate downloads immediately on failure, as long as
7559 we haven't failed a threshold number of times yet.
7560 - Delay retrying consensus downloads while we're downloading
7561 certificates to verify the one we just got. Also, count getting a
7562 consensus that we already have (or one that isn't valid) as a failure,
7563 and count failing to get the certificates after 20 minutes as a
7565 - Build circuits and download descriptors even if our consensus is a
7566 little expired. (This feature will go away once authorities are
7569 o Minor features (router descriptor cache):
7570 - If we find a cached-routers file that's been sitting around for more
7571 than 28 days unmodified, then most likely it's a leftover from
7572 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
7574 - When we (as a cache) download a descriptor because it was listed
7575 in a consensus, remember when the consensus was supposed to expire,
7576 and don't expire the descriptor until then.
7578 o Minor features (performance):
7579 - Call routerlist_remove_old_routers() much less often. This should
7580 speed startup, especially on directory caches.
7581 - Don't try to launch new descriptor downloads quite so often when we
7582 already have enough directory information to build circuits.
7583 - Base64 decoding was actually showing up on our profile when parsing
7584 the initial descriptor file; switch to an in-process all-at-once
7585 implementation that's about 3.5x times faster than calling out to
7588 o Minor features (compilation):
7589 - Detect non-ASCII platforms (if any still exist) and refuse to
7590 build there: some of our code assumes that 'A' is 65 and so on.
7592 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
7593 - Make the "next period" votes into "current period" votes immediately
7594 after publishing the consensus; avoid a heisenbug that made them
7595 stick around indefinitely.
7596 - When we discard a vote as a duplicate, do not report this as
7598 - Treat missing v3 keys or certificates as an error when running as a
7599 v3 directory authority.
7600 - When we're configured to be a v3 authority, but we're only listed
7601 as a non-v3 authority in our DirServer line for ourself, correct
7603 - If an authority doesn't have a qualified hostname, just put
7604 its address in the vote. This fixes the problem where we referred to
7605 "moria on moria:9031."
7606 - Distinguish between detached signatures for the wrong period, and
7607 detached signatures for a divergent vote.
7608 - Fix a small memory leak when computing a consensus.
7609 - When there's no concensus, we were forming a vote every 30
7610 minutes, but writing the "valid-after" line in our vote based
7611 on our configured V3AuthVotingInterval: so unless the intervals
7612 matched up, we immediately rejected our own vote because it didn't
7613 start at the voting interval that caused us to construct a vote.
7615 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
7616 - Delete unverified-consensus when the real consensus is set.
7617 - Consider retrying a consensus networkstatus fetch immediately
7618 after one fails: don't wait 60 seconds to notice.
7619 - When fetching a consensus as a cache, wait until a newer consensus
7620 should exist before trying to replace the current one.
7621 - Use a more forgiving schedule for retrying failed consensus
7622 downloads than for other types.
7624 o Minor bugfixes (other directory issues):
7625 - Correct the implementation of "download votes by digest." Bugfix on
7627 - Authorities no longer send back "400 you're unreachable please fix
7628 it" errors to Tor servers that aren't online all the time. We're
7629 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
7631 o Minor bugfixes (controller):
7632 - Don't reset trusted dir server list when we set a configuration
7633 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
7634 - Respond to INT and TERM SIGNAL commands before we execute the
7635 signal, in case the signal shuts us down. We had a patch in
7636 0.1.2.1-alpha that tried to do this by queueing the response on
7637 the connection's buffer before shutting down, but that really
7638 isn't the same thing at all. Bug located by Matt Edman.
7640 o Minor bugfixes (misc):
7641 - Correctly check for bad options to the "PublishServerDescriptor"
7642 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
7643 - Stop leaking memory on failing case of base32_decode, and make
7644 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
7645 - Don't try to download extrainfo documents when we're trying to
7646 fetch enough directory info to build a circuit: having enough
7647 info should get priority. Bugfix on 0.2.0.x.
7648 - Don't complain that "your server has not managed to confirm that its
7649 ports are reachable" if we haven't been able to build any circuits
7650 yet. Bug found by spending four hours without a v3 consensus. Bugfix
7652 - Detect the reason for failing to mmap a descriptor file we just
7653 wrote, and give a more useful log message. Fixes bug 533. Bugfix
7656 o Code simplifications and refactoring:
7657 - Remove support for the old bw_accounting file: we've been storing
7658 bandwidth accounting information in the state file since
7659 0.1.2.5-alpha. This may result in bandwidth accounting errors
7660 if you try to upgrade from 0.1.1.x or earlier, or if you try to
7661 downgrade to 0.1.1.x or earlier.
7662 - New convenience code to locate a file within the DataDirectory.
7663 - Move non-authority functionality out of dirvote.c.
7664 - Refactor the arguments for router_pick_{directory_|trusteddir}server
7665 so that they all take the same named flags.
7668 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
7669 Unix users an easy way to script their Tor process (e.g. by
7670 adjusting bandwidth based on the time of the day).
7673 Changes in version 0.2.0.8-alpha - 2007-10-12
7674 This eighth development snapshot fixes a crash bug that's been bothering
7675 us since February 2007, lets bridge authorities store a list of bridge
7676 descriptors they've seen, gets v3 directory voting closer to working,
7677 starts caching v3 directory consensus documents on directory mirrors,
7678 and fixes a variety of smaller issues including some minor memory leaks.
7680 o Major features (router descriptor cache):
7681 - Store routers in a file called cached-descriptors instead of in
7682 cached-routers. Initialize cached-descriptors from cached-routers
7683 if the old format is around. The new format allows us to store
7684 annotations along with descriptors.
7685 - Use annotations to record the time we received each descriptor, its
7686 source, and its purpose.
7687 - Disable the SETROUTERPURPOSE controller command: it is now
7689 - Controllers should now specify cache=no or cache=yes when using
7690 the +POSTDESCRIPTOR command.
7691 - Bridge authorities now write bridge descriptors to disk, meaning
7692 we can export them to other programs and begin distributing them
7695 o Major features (directory authorities):
7696 - When a v3 authority is missing votes or signatures, it now tries
7698 - Directory authorities track weighted fractional uptime as well as
7699 weighted mean-time-between failures. WFU is suitable for deciding
7700 whether a node is "usually up", while MTBF is suitable for deciding
7701 whether a node is "likely to stay up." We need both, because
7702 "usually up" is a good requirement for guards, while "likely to
7703 stay up" is a good requirement for long-lived connections.
7705 o Major features (v3 directory system):
7706 - Caches now download v3 network status documents as needed,
7707 and download the descriptors listed in them.
7708 - All hosts now attempt to download and keep fresh v3 authority
7709 certificates, and re-attempt after failures.
7710 - More internal-consistency checks for vote parsing.
7712 o Major bugfixes (crashes):
7713 - If a connection is shut down abruptly because of something that
7714 happened inside connection_flushed_some(), do not call
7715 connection_finished_flushing(). Should fix bug 451. Bugfix on
7718 o Major bugfixes (performance):
7719 - Fix really bad O(n^2) performance when parsing a long list of
7720 routers: Instead of searching the entire list for an "extra-info "
7721 string which usually wasn't there, once for every routerinfo
7722 we read, just scan lines forward until we find one we like.
7724 - When we add data to a write buffer in response to the data on that
7725 write buffer getting low because of a flush, do not consider the
7726 newly added data as a candidate for immediate flushing, but rather
7727 make it wait until the next round of writing. Otherwise, we flush
7728 and refill recursively, and a single greedy TLS connection can
7729 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
7731 o Minor features (v3 authority system):
7732 - Add more ways for tools to download the votes that lead to the
7734 - Send a 503 when low on bandwidth and a vote, consensus, or
7735 certificate is requested.
7736 - If-modified-since is now implemented properly for all kinds of
7737 certificate requests.
7739 o Minor bugfixes (network statuses):
7740 - Tweak the implementation of proposal 109 slightly: allow at most
7741 two Tor servers on the same IP address, except if it's the location
7742 of a directory authority, in which case allow five. Bugfix on
7745 o Minor bugfixes (controller):
7746 - When sending a status event to the controller telling it that an
7747 OR address is reachable, set the port correctly. (Previously we
7748 were reporting the dir port.) Bugfix on 0.1.2.x.
7750 o Minor bugfixes (v3 directory system):
7751 - Fix logic to look up a cert by its signing key digest. Bugfix on
7753 - Only change the reply to a vote to "OK" if it's not already
7754 set. This gets rid of annoying "400 OK" log messages, which may
7755 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
7756 - When we get a valid consensus, recompute the voting schedule.
7757 - Base the valid-after time of a vote on the consensus voting
7758 schedule, not on our preferred schedule.
7759 - Make the return values and messages from signature uploads and
7760 downloads more sensible.
7761 - Fix a memory leak when serving votes and consensus documents, and
7762 another when serving certificates.
7764 o Minor bugfixes (performance):
7765 - Use a slightly simpler string hashing algorithm (copying Python's
7766 instead of Java's) and optimize our digest hashing algorithm to take
7767 advantage of 64-bit platforms and to remove some possibly-costly
7769 - Fix a minor memory leak whenever we parse guards from our state
7770 file. Bugfix on 0.2.0.7-alpha.
7771 - Fix a minor memory leak whenever we write out a file. Bugfix on
7773 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
7774 command. Bugfix on 0.2.0.5-alpha.
7776 o Minor bugfixes (portability):
7777 - On some platforms, accept() can return a broken address. Detect
7778 this more quietly, and deal accordingly. Fixes bug 483.
7779 - Stop calling tor_strlower() on uninitialized memory in some cases.
7780 Bugfix in 0.2.0.7-alpha.
7782 o Minor bugfixes (usability):
7783 - Treat some 403 responses from directory servers as INFO rather than
7784 WARN-severity events.
7785 - It's not actually an error to find a non-pending entry in the DNS
7786 cache when canceling a pending resolve. Don't log unless stuff is
7787 fishy. Resolves bug 463.
7789 o Minor bugfixes (anonymity):
7790 - Never report that we've used more bandwidth than we're willing to
7791 relay: it leaks how much non-relay traffic we're using. Resolves
7793 - When looking for a circuit to cannibalize, consider family as well
7794 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
7795 circuit cannibalization).
7797 o Code simplifications and refactoring:
7798 - Make a bunch of functions static. Remove some dead code.
7799 - Pull out about a third of the really big routerlist.c; put it in a
7800 new module, networkstatus.c.
7801 - Merge the extra fields in local_routerstatus_t back into
7802 routerstatus_t: we used to need one routerstatus_t for each
7803 authority's opinion, plus a local_routerstatus_t for the locally
7804 computed consensus opinion. To save space, we put the locally
7805 modified fields into local_routerstatus_t, and only the common
7806 stuff into routerstatus_t. But once v3 directories are in use,
7807 clients and caches will no longer need to hold authority opinions;
7808 thus, the rationale for keeping the types separate is now gone.
7809 - Make the code used to reschedule and reattempt downloads more
7811 - Turn all 'Are we a directory server/mirror?' logic into a call to
7813 - Remove the code to generate the oldest (v1) directory format.
7814 The code has been disabled since 0.2.0.5-alpha.
7817 Changes in version 0.2.0.7-alpha - 2007-09-21
7818 This seventh development snapshot makes bridges work again, makes bridge
7819 authorities work for the first time, fixes two huge performance flaws
7820 in hidden services, and fixes a variety of minor issues.
7822 o New directory authorities:
7823 - Set up moria1 and tor26 as the first v3 directory authorities. See
7824 doc/spec/dir-spec.txt for details on the new directory design.
7826 o Major bugfixes (crashes):
7827 - Fix possible segfaults in functions called from
7828 rend_process_relay_cell(). Bugfix on 0.1.2.x.
7830 o Major bugfixes (bridges):
7831 - Fix a bug that made servers send a "404 Not found" in response to
7832 attempts to fetch their server descriptor. This caused Tor servers
7833 to take many minutes to establish reachability for their DirPort,
7834 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
7835 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
7836 users configure that and specify a bridge with an identity
7837 fingerprint, now they will lookup the bridge descriptor at the
7838 default bridge authority via a one-hop tunnel, but once circuits
7839 are established they will switch to a three-hop tunnel for later
7840 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
7842 o Major bugfixes (hidden services):
7843 - Hidden services were choosing introduction points uniquely by
7844 hexdigest, but when constructing the hidden service descriptor
7845 they merely wrote the (potentially ambiguous) nickname.
7846 - Clients now use the v2 intro format for hidden service
7847 connections: they specify their chosen rendezvous point by identity
7848 digest rather than by (potentially ambiguous) nickname. Both
7849 are bugfixes on 0.1.2.x, and they could speed up hidden service
7850 connections dramatically. Thanks to Karsten Loesing.
7852 o Minor features (security):
7853 - As a client, do not believe any server that tells us that an
7854 address maps to an internal address space.
7855 - Make it possible to enable HashedControlPassword and
7856 CookieAuthentication at the same time.
7858 o Minor features (guard nodes):
7859 - Tag every guard node in our state file with the version that
7860 we believe added it, or with our own version if we add it. This way,
7861 if a user temporarily runs an old version of Tor and then switches
7862 back to a new one, she doesn't automatically lose her guards.
7864 o Minor features (speed):
7865 - When implementing AES counter mode, update only the portions of the
7866 counter buffer that need to change, and don't keep separate
7867 network-order and host-order counters when they are the same (i.e.,
7868 on big-endian hosts.)
7870 o Minor features (controller):
7871 - Accept LF instead of CRLF on controller, since some software has a
7872 hard time generating real Internet newlines.
7873 - Add GETINFO values for the server status events
7874 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
7878 - Routers no longer include bandwidth-history lines in their
7879 descriptors; this information is already available in extra-info
7880 documents, and including it in router descriptors took up 60%
7881 (!) of compressed router descriptor downloads. Completes
7882 implementation of proposal 104.
7883 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
7884 and TorControl.py, as they use the old v0 controller protocol,
7885 and are obsoleted by TorFlow anyway.
7886 - Drop support for v1 rendezvous descriptors, since we never used
7887 them anyway, and the code has probably rotted by now. Based on
7888 patch from Karsten Loesing.
7889 - On OSX, stop warning the user that kqueue support in libevent is
7890 "experimental", since it seems to have worked fine for ages.
7893 - When generating information telling us how to extend to a given
7894 router, do not try to include the nickname if it is absent. Fixes
7895 bug 467. Bugfix on 0.2.0.3-alpha.
7896 - Fix a user-triggerable (but not remotely-triggerable) segfault
7897 in expand_filename(). Bugfix on 0.1.2.x.
7898 - Fix a memory leak when freeing incomplete requests from DNSPort.
7899 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
7900 - Don't try to access (or alter) the state file when running
7901 --list-fingerprint or --verify-config or --hash-password. (Resolves
7902 bug 499.) Bugfix on 0.1.2.x.
7903 - Servers used to decline to publish their DirPort if their
7904 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
7905 were below a threshold. Now they only look at BandwidthRate and
7906 RelayBandwidthRate. Bugfix on 0.1.2.x.
7907 - Remove an optimization in the AES counter-mode code that assumed
7908 that the counter never exceeded 2^68. When the counter can be set
7909 arbitrarily as an IV (as it is by Karsten's new hidden services
7910 code), this assumption no longer holds. Bugfix on 0.1.2.x.
7911 - Resume listing "AUTHORITY" flag for authorities in network status.
7912 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
7914 o Code simplifications and refactoring:
7915 - Revamp file-writing logic so we don't need to have the entire
7916 contents of a file in memory at once before we write to disk. Tor,
7918 - Turn "descriptor store" into a full-fledged type.
7919 - Move all NT services code into a separate source file.
7920 - Unify all code that computes medians, percentile elements, etc.
7921 - Get rid of a needless malloc when parsing address policies.
7924 Changes in version 0.1.2.17 - 2007-08-30
7925 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
7926 X bundles. Vidalia 0.0.14 makes authentication required for the
7927 ControlPort in the default configuration, which addresses important
7928 security risks. Everybody who uses Vidalia (or another controller)
7931 In addition, this Tor update fixes major load balancing problems with
7932 path selection, which should speed things up a lot once many people
7935 o Major bugfixes (security):
7936 - We removed support for the old (v0) control protocol. It has been
7937 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
7938 become more of a headache than it's worth.
7940 o Major bugfixes (load balancing):
7941 - When choosing nodes for non-guard positions, weight guards
7942 proportionally less, since they already have enough load. Patch
7944 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
7945 will allow fast Tor servers to get more attention.
7946 - When we're upgrading from an old Tor version, forget our current
7947 guards and pick new ones according to the new weightings. These
7948 three load balancing patches could raise effective network capacity
7949 by a factor of four. Thanks to Mike Perry for measurements.
7951 o Major bugfixes (stream expiration):
7952 - Expire not-yet-successful application streams in all cases if
7953 they've been around longer than SocksTimeout. Right now there are
7954 some cases where the stream will live forever, demanding a new
7955 circuit every 15 seconds. Fixes bug 454; reported by lodger.
7957 o Minor features (controller):
7958 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
7959 is valid before any authentication has been received. It tells
7960 a controller what kind of authentication is expected, and what
7961 protocol is spoken. Implements proposal 119.
7963 o Minor bugfixes (performance):
7964 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
7965 greatly speeding up loading cached-routers from disk on startup.
7966 - Disable sentinel-based debugging for buffer code: we squashed all
7967 the bugs that this was supposed to detect a long time ago, and now
7968 its only effect is to change our buffer sizes from nice powers of
7969 two (which platform mallocs tend to like) to values slightly over
7970 powers of two (which make some platform mallocs sad).
7972 o Minor bugfixes (misc):
7973 - If exit bandwidth ever exceeds one third of total bandwidth, then
7974 use the correct formula to weight exit nodes when choosing paths.
7975 Based on patch from Mike Perry.
7976 - Choose perfectly fairly among routers when choosing by bandwidth and
7977 weighting by fraction of bandwidth provided by exits. Previously, we
7978 would choose with only approximate fairness, and correct ourselves
7979 if we ran off the end of the list.
7980 - If we require CookieAuthentication but we fail to write the
7981 cookie file, we would warn but not exit, and end up in a state
7982 where no controller could authenticate. Now we exit.
7983 - If we require CookieAuthentication, stop generating a new cookie
7984 every time we change any piece of our config.
7985 - Refuse to start with certain directory authority keys, and
7986 encourage people using them to stop.
7987 - Terminate multi-line control events properly. Original patch
7989 - Fix a minor memory leak when we fail to find enough suitable
7990 servers to choose a circuit.
7991 - Stop leaking part of the descriptor when we run into a particularly
7992 unparseable piece of it.
7995 Changes in version 0.2.0.6-alpha - 2007-08-26
7996 This sixth development snapshot features a new Vidalia version in the
7997 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
7998 the ControlPort in the default configuration, which addresses important
8001 In addition, this snapshot fixes major load balancing problems
8002 with path selection, which should speed things up a lot once many
8003 people have upgraded. The directory authorities also use a new
8004 mean-time-between-failure approach to tracking which servers are stable,
8005 rather than just looking at the most recent uptime.
8007 o New directory authorities:
8008 - Set up Tonga as the default bridge directory authority.
8011 - Directory authorities now track servers by weighted
8012 mean-times-between-failures. When we have 4 or more days of data,
8013 use measured MTBF rather than declared uptime to decide whether
8014 to call a router Stable. Implements proposal 108.
8016 o Major bugfixes (load balancing):
8017 - When choosing nodes for non-guard positions, weight guards
8018 proportionally less, since they already have enough load. Patch
8020 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
8021 will allow fast Tor servers to get more attention.
8022 - When we're upgrading from an old Tor version, forget our current
8023 guards and pick new ones according to the new weightings. These
8024 three load balancing patches could raise effective network capacity
8025 by a factor of four. Thanks to Mike Perry for measurements.
8027 o Major bugfixes (descriptor parsing):
8028 - Handle unexpected whitespace better in malformed descriptors. Bug
8029 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
8032 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
8033 GETINFO for Torstat to use until it can switch to using extrainfos.
8034 - Optionally (if built with -DEXPORTMALLINFO) export the output
8035 of mallinfo via http, as tor/mallinfo.txt. Only accessible
8039 - Do not intermix bridge routers with controller-added
8040 routers. (Bugfix on 0.2.0.x)
8041 - Do not fail with an assert when accept() returns an unexpected
8042 address family. Addresses but does not wholly fix bug 483. (Bugfix
8044 - Let directory authorities startup even when they can't generate
8045 a descriptor immediately, e.g. because they don't know their
8047 - Stop putting the authentication cookie in a file called "0"
8048 in your working directory if you don't specify anything for the
8049 new CookieAuthFile option. Reported by Matt Edman.
8050 - Make it possible to read the PROTOCOLINFO response in a way that
8051 conforms to our control-spec. Reported by Matt Edman.
8052 - Fix a minor memory leak when we fail to find enough suitable
8053 servers to choose a circuit. Bugfix on 0.1.2.x.
8054 - Stop leaking part of the descriptor when we run into a particularly
8055 unparseable piece of it. Bugfix on 0.1.2.x.
8056 - Unmap the extrainfo cache file on exit.
8059 Changes in version 0.2.0.5-alpha - 2007-08-19
8060 This fifth development snapshot fixes compilation on Windows again;
8061 fixes an obnoxious client-side bug that slowed things down and put
8062 extra load on the network; gets us closer to using the v3 directory
8063 voting scheme; makes it easier for Tor controllers to use cookie-based
8064 authentication; and fixes a variety of other bugs.
8067 - Version 1 directories are no longer generated in full. Instead,
8068 authorities generate and serve "stub" v1 directories that list
8069 no servers. This will stop Tor versions 0.1.0.x and earlier from
8070 working, but (for security reasons) nobody should be running those
8073 o Major bugfixes (compilation, 0.2.0.x):
8074 - Try to fix Win32 compilation again: improve checking for IPv6 types.
8075 - Try to fix MSVC compilation: build correctly on platforms that do
8076 not define s6_addr16 or s6_addr32.
8077 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
8080 o Major bugfixes (stream expiration):
8081 - Expire not-yet-successful application streams in all cases if
8082 they've been around longer than SocksTimeout. Right now there are
8083 some cases where the stream will live forever, demanding a new
8084 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
8087 o Minor features (directory servers):
8088 - When somebody requests a list of statuses or servers, and we have
8089 none of those, return a 404 rather than an empty 200.
8091 o Minor features (directory voting):
8092 - Store v3 consensus status consensuses on disk, and reload them
8095 o Minor features (security):
8096 - Warn about unsafe ControlPort configurations.
8097 - Refuse to start with certain directory authority keys, and
8098 encourage people using them to stop.
8100 o Minor features (controller):
8101 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
8102 is valid before any authentication has been received. It tells
8103 a controller what kind of authentication is expected, and what
8104 protocol is spoken. Implements proposal 119.
8105 - New config option CookieAuthFile to choose a new location for the
8106 cookie authentication file, and config option
8107 CookieAuthFileGroupReadable to make it group-readable.
8109 o Minor features (unit testing):
8110 - Add command-line arguments to unit-test executable so that we can
8111 invoke any chosen test from the command line rather than having
8112 to run the whole test suite at once; and so that we can turn on
8113 logging for the unit tests.
8115 o Minor bugfixes (on 0.1.2.x):
8116 - If we require CookieAuthentication but we fail to write the
8117 cookie file, we would warn but not exit, and end up in a state
8118 where no controller could authenticate. Now we exit.
8119 - If we require CookieAuthentication, stop generating a new cookie
8120 every time we change any piece of our config.
8121 - When loading bandwidth history, do not believe any information in
8122 the future. Fixes bug 434.
8123 - When loading entry guard information, do not believe any information
8125 - When we have our clock set far in the future and generate an
8126 onion key, then re-set our clock to be correct, we should not stop
8127 the onion key from getting rotated.
8128 - Clean up torrc sample config file.
8129 - Do not automatically run configure from autogen.sh. This
8130 non-standard behavior tended to annoy people who have built other
8133 o Minor bugfixes (on 0.2.0.x):
8134 - Fix a bug with AutomapHostsOnResolve that would always cause
8135 the second request to fail. Bug reported by Kate. Bugfix on
8137 - Fix a bug in ADDRMAP controller replies that would sometimes
8138 try to print a NULL. Patch from tup.
8139 - Read v3 directory authority keys from the right location.
8140 - Numerous bugfixes to directory voting code.
8143 Changes in version 0.1.2.16 - 2007-08-01
8144 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
8145 remote attacker in certain situations to rewrite the user's torrc
8146 configuration file. This can completely compromise anonymity of users
8147 in most configurations, including those running the Vidalia bundles,
8148 TorK, etc. Or worse.
8150 o Major security fixes:
8151 - Close immediately after missing authentication on control port;
8152 do not allow multiple authentication attempts.
8155 Changes in version 0.2.0.4-alpha - 2007-08-01
8156 This fourth development snapshot fixes a critical security vulnerability
8157 for most users, specifically those running Vidalia, TorK, etc. Everybody
8158 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
8160 o Major security fixes:
8161 - Close immediately after missing authentication on control port;
8162 do not allow multiple authentication attempts.
8164 o Major bugfixes (compilation):
8165 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
8168 o Minor features (performance):
8169 - Be even more aggressive about releasing RAM from small
8170 empty buffers. Thanks to our free-list code, this shouldn't be too
8171 performance-intensive.
8172 - Disable sentinel-based debugging for buffer code: we squashed all
8173 the bugs that this was supposed to detect a long time ago, and
8174 now its only effect is to change our buffer sizes from nice
8175 powers of two (which platform mallocs tend to like) to values
8176 slightly over powers of two (which make some platform mallocs sad).
8177 - Log malloc statistics from mallinfo() on platforms where it
8181 Changes in version 0.2.0.3-alpha - 2007-07-29
8182 This third development snapshot introduces new experimental
8183 blocking-resistance features and a preliminary version of the v3
8184 directory voting design, and includes many other smaller features
8188 - The first pieces of our "bridge" design for blocking-resistance
8189 are implemented. People can run bridge directory authorities;
8190 people can run bridges; and people can configure their Tor clients
8191 with a set of bridges to use as the first hop into the Tor network.
8192 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
8194 - Create listener connections before we setuid to the configured
8195 User and Group. Now non-Windows users can choose port values
8196 under 1024, start Tor as root, and have Tor bind those ports
8197 before it changes to another UID. (Windows users could already
8199 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
8200 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
8201 on "vserver" accounts. (Patch from coderman.)
8202 - Be even more aggressive about separating local traffic from relayed
8203 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
8205 o Major features (experimental):
8206 - First cut of code for "v3 dir voting": directory authorities will
8207 vote on a common network status document rather than each publishing
8208 their own opinion. This code needs more testing and more corner-case
8209 handling before it's ready for use.
8212 - Directory authorities now call routers Fast if their bandwidth is
8213 at least 100KB/s, and consider their bandwidth adequate to be a
8214 Guard if it is at least 250KB/s, no matter the medians. This fix
8215 complements proposal 107. [Bugfix on 0.1.2.x]
8216 - Directory authorities now never mark more than 3 servers per IP as
8217 Valid and Running. (Implements proposal 109, by Kevin Bauer and
8219 - Minor change to organizationName and commonName generation
8220 procedures in TLS certificates during Tor handshakes, to invalidate
8221 some earlier censorware approaches. This is not a long-term
8222 solution, but applying it will give us a bit of time to look into
8223 the epidemiology of countermeasures as they spread.
8225 o Major bugfixes (directory):
8226 - Rewrite directory tokenization code to never run off the end of
8227 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
8229 o Minor features (controller):
8230 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
8231 match requests to applications. (Patch from Robert Hogan.)
8232 - Report address and port correctly on connections to DNSPort. (Patch
8234 - Add a RESOLVE command to launch hostname lookups. (Original patch
8236 - Add GETINFO status/enough-dir-info to let controllers tell whether
8237 Tor has downloaded sufficient directory information. (Patch
8239 - You can now use the ControlSocket option to tell Tor to listen for
8240 controller connections on Unix domain sockets on systems that
8241 support them. (Patch from Peter Palfrader.)
8242 - STREAM NEW events are generated for DNSPort requests and for
8243 tunneled directory connections. (Patch from Robert Hogan.)
8244 - New "GETINFO address-mappings/*" command to get address mappings
8245 with expiry information. "addr-mappings/*" is now deprecated.
8248 o Minor features (misc):
8249 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
8251 - The tor-gencert tool for v3 directory authorities now creates all
8252 files as readable to the file creator only, and write-protects
8253 the authority identity key.
8254 - When dumping memory usage, list bytes used in buffer memory
8256 - When running with dmalloc, dump more stats on hup and on exit.
8257 - Directory authorities now fail quickly and (relatively) harmlessly
8258 if they generate a network status document that is somehow
8261 o Traffic load balancing improvements:
8262 - If exit bandwidth ever exceeds one third of total bandwidth, then
8263 use the correct formula to weight exit nodes when choosing paths.
8264 (Based on patch from Mike Perry.)
8265 - Choose perfectly fairly among routers when choosing by bandwidth and
8266 weighting by fraction of bandwidth provided by exits. Previously, we
8267 would choose with only approximate fairness, and correct ourselves
8268 if we ran off the end of the list. [Bugfix on 0.1.2.x]
8270 o Performance improvements:
8271 - Be more aggressive with freeing buffer RAM or putting it on the
8273 - Use Critical Sections rather than Mutexes for synchronizing threads
8274 on win32; Mutexes are heavier-weight, and designed for synchronizing
8277 o Deprecated and removed features:
8278 - RedirectExits is now deprecated.
8279 - Stop allowing address masks that do not correspond to bit prefixes.
8280 We have warned about these for a really long time; now it's time
8281 to reject them. (Patch from croup.)
8283 o Minor bugfixes (directory):
8284 - Fix another crash bug related to extra-info caching. (Bug found by
8285 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
8286 - Directories no longer return a "304 not modified" when they don't
8287 have the networkstatus the client asked for. Also fix a memory
8288 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
8289 - We had accidentally labelled 0.1.2.x directory servers as not
8290 suitable for begin_dir requests, and had labelled no directory
8291 servers as suitable for uploading extra-info documents. [Bugfix
8294 o Minor bugfixes (dns):
8295 - Fix a crash when DNSPort is set more than once. (Patch from Robert
8296 Hogan.) [Bugfix on 0.2.0.2-alpha]
8297 - Add DNSPort connections to the global connection list, so that we
8298 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
8300 - Fix a dangling reference that could lead to a crash when DNSPort is
8301 changed or closed (Patch from Robert Hogan.) [Bugfix on
8304 o Minor bugfixes (controller):
8305 - Provide DNS expiry times in GMT, not in local time. For backward
8306 compatibility, ADDRMAP events only provide GMT expiry in an extended
8307 field. "GETINFO address-mappings" always does the right thing.
8308 - Use CRLF line endings properly in NS events.
8309 - Terminate multi-line control events properly. (Original patch
8310 from tup.) [Bugfix on 0.1.2.x-alpha]
8311 - Do not include spaces in SOURCE_ADDR fields in STREAM
8312 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
8315 Changes in version 0.1.2.15 - 2007-07-17
8316 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
8317 problems, fixes compilation on BSD, and fixes a variety of other
8318 bugs. Everybody should upgrade.
8320 o Major bugfixes (compilation):
8321 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
8323 o Major bugfixes (crashes):
8324 - Try even harder not to dereference the first character after
8325 an mmap(). Reported by lodger.
8326 - Fix a crash bug in directory authorities when we re-number the
8327 routerlist while inserting a new router.
8328 - When the cached-routers file is an even multiple of the page size,
8329 don't run off the end and crash. (Fixes bug 455; based on idea
8331 - Fix eventdns.c behavior on Solaris: It is critical to include
8332 orconfig.h _before_ sys/types.h, so that we can get the expected
8333 definition of _FILE_OFFSET_BITS.
8335 o Major bugfixes (security):
8336 - Fix a possible buffer overrun when using BSD natd support. Bug
8338 - When sending destroy cells from a circuit's origin, don't include
8339 the reason for tearing down the circuit. The spec says we didn't,
8340 and now we actually don't. Reported by lodger.
8341 - Keep streamids from different exits on a circuit separate. This
8342 bug may have allowed other routers on a given circuit to inject
8343 cells into streams. Reported by lodger; fixes bug 446.
8344 - If there's a never-before-connected-to guard node in our list,
8345 never choose any guards past it. This way we don't expand our
8346 guard list unless we need to.
8348 o Minor bugfixes (guard nodes):
8349 - Weight guard selection by bandwidth, so that low-bandwidth nodes
8350 don't get overused as guards.
8352 o Minor bugfixes (directory):
8353 - Correctly count the number of authorities that recommend each
8354 version. Previously, we were under-counting by 1.
8355 - Fix a potential crash bug when we load many server descriptors at
8356 once and some of them make others of them obsolete. Fixes bug 458.
8358 o Minor bugfixes (hidden services):
8359 - Stop tearing down the whole circuit when the user asks for a
8360 connection to a port that the hidden service didn't configure.
8363 o Minor bugfixes (misc):
8364 - On Windows, we were preventing other processes from reading
8365 cached-routers while Tor was running. Reported by janbar.
8366 - Fix a possible (but very unlikely) bug in picking routers by
8367 bandwidth. Add a log message to confirm that it is in fact
8368 unlikely. Patch from lodger.
8369 - Backport a couple of memory leak fixes.
8370 - Backport miscellaneous cosmetic bugfixes.
8373 Changes in version 0.2.0.2-alpha - 2007-06-02
8374 o Major bugfixes on 0.2.0.1-alpha:
8375 - Fix an assertion failure related to servers without extra-info digests.
8376 Resolves bugs 441 and 442.
8378 o Minor features (directory):
8379 - Support "If-Modified-Since" when answering HTTP requests for
8380 directories, running-routers documents, and network-status documents.
8381 (There's no need to support it for router descriptors, since those
8382 are downloaded by descriptor digest.)
8384 o Minor build issues:
8385 - Clear up some MIPSPro compiler warnings.
8386 - When building from a tarball on a machine that happens to have SVK
8387 installed, report the micro-revision as whatever version existed
8388 in the tarball, not as "x".
8391 Changes in version 0.2.0.1-alpha - 2007-06-01
8392 This early development snapshot provides new features for people running
8393 Tor as both a client and a server (check out the new RelayBandwidth
8394 config options); lets Tor run as a DNS proxy; and generally moves us
8395 forward on a lot of fronts.
8397 o Major features, server usability:
8398 - New config options RelayBandwidthRate and RelayBandwidthBurst:
8399 a separate set of token buckets for relayed traffic. Right now
8400 relayed traffic is defined as answers to directory requests, and
8401 OR connections that don't have any local circuits on them.
8403 o Major features, client usability:
8404 - A client-side DNS proxy feature to replace the need for
8405 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
8406 for DNS requests on port 9999, use the Tor network to resolve them
8407 anonymously, and send the reply back like a regular DNS server.
8408 The code still only implements a subset of DNS.
8409 - Make PreferTunneledDirConns and TunnelDirConns work even when
8410 we have no cached directory info. This means Tor clients can now
8411 do all of their connections protected by TLS.
8413 o Major features, performance and efficiency:
8414 - Directory authorities accept and serve "extra info" documents for
8415 routers. These documents contain fields from router descriptors
8416 that aren't usually needed, and that use a lot of excess
8417 bandwidth. Once these fields are removed from router descriptors,
8418 the bandwidth savings should be about 60%. [Partially implements
8420 - Servers upload extra-info documents to any authority that accepts
8421 them. Authorities (and caches that have been configured to download
8422 extra-info documents) download them as needed. [Partially implements
8424 - Change the way that Tor buffers data that it is waiting to write.
8425 Instead of queueing data cells in an enormous ring buffer for each
8426 client->OR or OR->OR connection, we now queue cells on a separate
8427 queue for each circuit. This lets us use less slack memory, and
8428 will eventually let us be smarter about prioritizing different kinds
8430 - Use memory pools to allocate cells with better speed and memory
8431 efficiency, especially on platforms where malloc() is inefficient.
8432 - Stop reading on edge connections when their corresponding circuit
8433 buffers are full; start again as the circuits empty out.
8435 o Major features, other:
8436 - Add an HSAuthorityRecordStats option that hidden service authorities
8437 can use to track statistics of overall hidden service usage without
8438 logging information that would be very useful to an attacker.
8439 - Start work implementing multi-level keys for directory authorities:
8440 Add a standalone tool to generate key certificates. (Proposal 103.)
8443 - Directory authorities now call routers Stable if they have an
8444 uptime of at least 30 days, even if that's not the median uptime
8445 in the network. Implements proposal 107, suggested by Kevin Bauer
8448 o Minor fixes (resource management):
8449 - Count the number of open sockets separately from the number
8450 of active connection_t objects. This will let us avoid underusing
8451 our allocated connection limit.
8452 - We no longer use socket pairs to link an edge connection to an
8453 anonymous directory connection or a DirPort test connection.
8454 Instead, we track the link internally and transfer the data
8455 in-process. This saves two sockets per "linked" connection (at the
8456 client and at the server), and avoids the nasty Windows socketpair()
8458 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
8459 for every single inactive connection_t. Free items from the
8460 4k/16k-buffer free lists when they haven't been used for a while.
8462 o Minor features (build):
8463 - Make autoconf search for libevent, openssl, and zlib consistently.
8464 - Update deprecated macros in configure.in.
8465 - When warning about missing headers, tell the user to let us
8466 know if the compile succeeds anyway, so we can downgrade the
8468 - Include the current subversion revision as part of the version
8469 string: either fetch it directly if we're in an SVN checkout, do
8470 some magic to guess it if we're in an SVK checkout, or use
8471 the last-detected version if we're building from a .tar.gz.
8472 Use this version consistently in log messages.
8474 o Minor features (logging):
8475 - Always prepend "Bug: " to any log message about a bug.
8476 - Put a platform string (e.g. "Linux i686") in the startup log
8477 message, so when people paste just their logs, we know if it's
8478 OpenBSD or Windows or what.
8479 - When logging memory usage, break down memory used in buffers by
8482 o Minor features (directory system):
8483 - New config option V2AuthoritativeDirectory that all directory
8484 authorities should set. This will let future authorities choose
8485 not to serve V2 directory information.
8486 - Directory authorities allow multiple router descriptors and/or extra
8487 info documents to be uploaded in a single go. This will make
8488 implementing proposal 104 simpler.
8490 o Minor features (controller):
8491 - Add a new config option __DisablePredictedCircuits designed for
8492 use by the controller, when we don't want Tor to build any circuits
8494 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
8495 so we can exit from the middle of the circuit.
8496 - Implement "getinfo status/circuit-established".
8497 - Implement "getinfo status/version/..." so a controller can tell
8498 whether the current version is recommended, and whether any versions
8499 are good, and how many authorities agree. (Patch from shibz.)
8501 o Minor features (hidden services):
8502 - Allow multiple HiddenServicePort directives with the same virtual
8503 port; when they occur, the user is sent round-robin to one
8504 of the target ports chosen at random. Partially fixes bug 393 by
8505 adding limited ad-hoc round-robining.
8507 o Minor features (other):
8509 - Add a new AutomapHostsOnResolve option: when it is enabled, any
8510 resolve request for hosts matching a given pattern causes Tor to
8511 generate an internal virtual address mapping for that host. This
8512 allows DNSPort to work sensibly with hidden service users. By
8513 default, .exit and .onion addresses are remapped; the list of
8514 patterns can be reconfigured with AutomapHostsSuffixes.
8515 - Add an "-F" option to tor-resolve to force a resolve for a .onion
8516 address. Thanks to the AutomapHostsOnResolve option, this is no
8517 longer a completely silly thing to do.
8518 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
8519 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
8520 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
8521 minus 1 byte: the actual maximum declared bandwidth.
8524 - Removed support for the old binary "version 0" controller protocol.
8525 This has been deprecated since 0.1.1, and warnings have been issued
8526 since 0.1.2. When we encounter a v0 control message, we now send
8527 back an error and close the connection.
8528 - Remove the old "dns worker" server DNS code: it hasn't been default
8529 since 0.1.2.2-alpha, and all the servers seem to be using the new
8532 o Minor bugfixes (portability):
8533 - Even though Windows is equally happy with / and \ as path separators,
8534 try to use \ consistently on Windows and / consistently on Unix: it
8535 makes the log messages nicer.
8536 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
8537 - Read resolv.conf files correctly on platforms where read() returns
8538 partial results on small file reads.
8540 o Minor bugfixes (directory):
8541 - Correctly enforce that elements of directory objects do not appear
8542 more often than they are allowed to appear.
8543 - When we are reporting the DirServer line we just parsed, we were
8544 logging the second stanza of the key fingerprint, not the first.
8546 o Minor bugfixes (logging):
8547 - When we hit an EOF on a log (probably because we're shutting down),
8548 don't try to remove the log from the list: just mark it as
8549 unusable. (Bulletproofs against bug 222.)
8551 o Minor bugfixes (other):
8552 - In the exitlist script, only consider the most recently published
8553 server descriptor for each server. Also, when the user requests
8554 a list of servers that _reject_ connections to a given address,
8555 explicitly exclude the IPs that also have servers that accept
8556 connections to that address. (Resolves bug 405.)
8557 - Stop allowing hibernating servers to be "stable" or "fast".
8558 - On Windows, we were preventing other processes from reading
8559 cached-routers while Tor was running. (Reported by janbar)
8560 - Make the NodeFamilies config option work. (Reported by
8561 lodger -- it has never actually worked, even though we added it
8563 - Check return values from pthread_mutex functions.
8564 - Don't save non-general-purpose router descriptors to the disk cache,
8565 because we have no way of remembering what their purpose was when
8567 - Add even more asserts to hunt down bug 417.
8568 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
8569 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
8570 Add a log message to confirm that it is in fact unlikely.
8572 o Minor bugfixes (controller):
8573 - Make 'getinfo fingerprint' return a 551 error if we're not a
8574 server, so we match what the control spec claims we do. Reported
8576 - Fix a typo in an error message when extendcircuit fails that
8577 caused us to not follow the \r\n-based delimiter protocol. Reported
8580 o Code simplifications and refactoring:
8581 - Stop passing around circuit_t and crypt_path_t pointers that are
8582 implicit in other procedure arguments.
8583 - Drop the old code to choke directory connections when the
8584 corresponding OR connections got full: thanks to the cell queue
8585 feature, OR conns don't get full any more.
8586 - Make dns_resolve() handle attaching connections to circuits
8587 properly, so the caller doesn't have to.
8588 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
8589 - Keep the connection array as a dynamic smartlist_t, rather than as
8590 a fixed-sized array. This is important, as the number of connections
8591 is becoming increasingly decoupled from the number of sockets.
8594 Changes in version 0.1.2.14 - 2007-05-25
8595 Tor 0.1.2.14 changes the addresses of two directory authorities (this
8596 change especially affects those who serve or use hidden services),
8597 and fixes several other crash- and security-related bugs.
8599 o Directory authority changes:
8600 - Two directory authorities (moria1 and moria2) just moved to new
8601 IP addresses. This change will particularly affect those who serve
8602 or use hidden services.
8604 o Major bugfixes (crashes):
8605 - If a directory server runs out of space in the connection table
8606 as it's processing a begin_dir request, it will free the exit stream
8607 but leave it attached to the circuit, leading to unpredictable
8608 behavior. (Reported by seeess, fixes bug 425.)
8609 - Fix a bug in dirserv_remove_invalid() that would cause authorities
8610 to corrupt memory under some really unlikely scenarios.
8611 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
8612 - Avoid segfaults when reading from mmaped descriptor file. (Reported
8615 o Major bugfixes (security):
8616 - When choosing an entry guard for a circuit, avoid using guards
8617 that are in the same family as the chosen exit -- not just guards
8618 that are exactly the chosen exit. (Reported by lodger.)
8620 o Major bugfixes (resource management):
8621 - If a directory authority is down, skip it when deciding where to get
8622 networkstatus objects or descriptors. Otherwise we keep asking
8623 every 10 seconds forever. Fixes bug 384.
8624 - Count it as a failure if we fetch a valid network-status but we
8625 don't want to keep it. Otherwise we'll keep fetching it and keep
8626 not wanting to keep it. Fixes part of bug 422.
8627 - If all of our dirservers have given us bad or no networkstatuses
8628 lately, then stop hammering them once per minute even when we
8629 think they're failed. Fixes another part of bug 422.
8632 - Actually set the purpose correctly for descriptors inserted with
8634 - When we have k non-v2 authorities in our DirServer config,
8635 we ignored the last k authorities in the list when updating our
8637 - Correctly back-off from requesting router descriptors that we are
8638 having a hard time downloading.
8639 - Read resolv.conf files correctly on platforms where read() returns
8640 partial results on small file reads.
8641 - Don't rebuild the entire router store every time we get 32K of
8642 routers: rebuild it when the journal gets very large, or when
8643 the gaps in the store get very large.
8646 - When routers publish SVN revisions in their router descriptors,
8647 authorities now include those versions correctly in networkstatus
8649 - Warn when using a version of libevent before 1.3b to run a server on
8650 OSX or BSD: these versions interact badly with userspace threads.
8653 Changes in version 0.1.2.13 - 2007-04-24
8654 This release features some major anonymity fixes, such as safer path
8655 selection; better client performance; faster bootstrapping, better
8656 address detection, and better DNS support for servers; write limiting as
8657 well as read limiting to make servers easier to run; and a huge pile of
8658 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
8660 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
8661 of the Freenode IRC network, remembering his patience and vision for
8662 free speech on the Internet.
8665 - Fix a memory leak when we ask for "all" networkstatuses and we
8666 get one we don't recognize.
8667 - Add more asserts to hunt down bug 417.
8668 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
8671 Changes in version 0.1.2.12-rc - 2007-03-16
8673 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
8674 directory information requested inside Tor connections (i.e. via
8675 begin_dir cells). It only triggered when the same connection was
8676 serving other data at the same time. Reported by seeess.
8679 - When creating a circuit via the controller, send a 'launched'
8680 event when we're done, so we follow the spec better.
8683 Changes in version 0.1.2.11-rc - 2007-03-15
8684 o Minor bugfixes (controller), reported by daejees:
8685 - Correct the control spec to match how the code actually responds
8686 to 'getinfo addr-mappings/*'.
8687 - The control spec described a GUARDS event, but the code
8688 implemented a GUARD event. Standardize on GUARD, but let people
8692 Changes in version 0.1.2.10-rc - 2007-03-07
8693 o Major bugfixes (Windows):
8694 - Do not load the NT services library functions (which may not exist)
8695 just to detect if we're a service trying to shut down. Now we run
8696 on Win98 and friends again.
8698 o Minor bugfixes (other):
8699 - Clarify a couple of log messages.
8700 - Fix a misleading socks5 error number.
8703 Changes in version 0.1.2.9-rc - 2007-03-02
8704 o Major bugfixes (Windows):
8705 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
8706 of the usual GCC "%llu". This prevents a bug when saving 64-bit
8707 int configuration values: the high-order 32 bits would get
8708 truncated. In particular, we were being bitten by the default
8709 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
8710 and maybe also bug 397.)
8712 o Minor bugfixes (performance):
8713 - Use OpenSSL's AES implementation on platforms where it's faster.
8714 This could save us as much as 10% CPU usage.
8716 o Minor bugfixes (server):
8717 - Do not rotate onion key immediately after setting it for the first
8720 o Minor bugfixes (directory authorities):
8721 - Stop calling servers that have been hibernating for a long time
8722 "stable". Also, stop letting hibernating or obsolete servers affect
8723 uptime and bandwidth cutoffs.
8724 - Stop listing hibernating servers in the v1 directory.
8726 o Minor bugfixes (hidden services):
8727 - Upload hidden service descriptors slightly less often, to reduce
8728 load on authorities.
8730 o Minor bugfixes (other):
8731 - Fix an assert that could trigger if a controller quickly set then
8732 cleared EntryNodes. Bug found by Udo van den Heuvel.
8733 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
8735 - Fix a potential race condition in the rpm installer. Found by
8737 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
8738 of 2 as indicating that the server is completely bad; it sometimes
8739 means that the server is just bad for the request in question. (may fix
8740 the last of bug 326.)
8741 - Disable encrypted directory connections when we don't have a server
8742 descriptor for the destination. We'll get this working again in
8746 Changes in version 0.1.2.8-beta - 2007-02-26
8747 o Major bugfixes (crashes):
8748 - Stop crashing when the controller asks us to resetconf more than
8749 one config option at once. (Vidalia 0.0.11 does this.)
8750 - Fix a crash that happened on Win98 when we're given command-line
8751 arguments: don't try to load NT service functions from advapi32.dll
8752 except when we need them. (Bug introduced in 0.1.2.7-alpha;
8754 - Fix a longstanding obscure crash bug that could occur when
8755 we run out of DNS worker processes. (Resolves bug 390.)
8757 o Major bugfixes (hidden services):
8758 - Correctly detect whether hidden service descriptor downloads are
8759 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
8761 o Major bugfixes (accounting):
8762 - When we start during an accounting interval before it's time to wake
8763 up, remember to wake up at the correct time. (May fix bug 342.)
8765 o Minor bugfixes (controller):
8766 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
8767 clear the corresponding on_circuit variable, and remember later
8768 that we don't need to send a redundant CLOSED event. Resolves part
8770 - Report events where a resolve succeeded or where we got a socks
8771 protocol error correctly, rather than calling both of them
8773 - Change reported stream target addresses to IP consistently when
8774 we finally get the IP from an exit node.
8775 - Send log messages to the controller even if they happen to be very
8778 o Minor bugfixes (other):
8779 - Display correct results when reporting which versions are
8780 recommended, and how recommended they are. (Resolves bug 383.)
8781 - Improve our estimates for directory bandwidth to be less random:
8782 guess that an unrecognized directory will have the average bandwidth
8783 from all known directories, not that it will have the average
8784 bandwidth from those directories earlier than it on the list.
8785 - If we start a server with ClientOnly 1, then set ClientOnly to 0
8786 and hup, stop triggering an assert based on an empty onion_key.
8787 - On platforms with no working mmap() equivalent, don't warn the
8788 user when cached-routers doesn't exist.
8789 - Warn the user when mmap() [or its equivalent] fails for some reason
8790 other than file-not-found.
8791 - Don't warn the user when cached-routers.new doesn't exist: that's
8792 perfectly fine when starting up for the first time.
8793 - When EntryNodes are configured, rebuild the guard list to contain,
8794 in order: the EntryNodes that were guards before; the rest of the
8795 EntryNodes; the nodes that were guards before.
8796 - Mask out all signals in sub-threads; only the libevent signal
8797 handler should be processing them. This should prevent some crashes
8798 on some machines using pthreads. (Patch from coderman.)
8799 - Fix switched arguments on memset in the implementation of
8800 tor_munmap() for systems with no mmap() call.
8801 - When Tor receives a router descriptor that it asked for, but
8802 no longer wants (because it has received fresh networkstatuses
8803 in the meantime), do not warn the user. Cache the descriptor if
8804 we're a cache; drop it if we aren't.
8805 - Make earlier entry guards _really_ get retried when the network
8807 - On a malformed DNS reply, always give an error to the corresponding
8809 - Build with recent libevents on platforms that do not define the
8810 nonstandard types "u_int8_t" and friends.
8812 o Minor features (controller):
8813 - Warn the user when an application uses the obsolete binary v0
8814 control protocol. We're planning to remove support for it during
8815 the next development series, so it's good to give people some
8817 - Add STREAM_BW events to report per-entry-stream bandwidth
8818 use. (Patch from Robert Hogan.)
8819 - Rate-limit SIGNEWNYM signals in response to controllers that
8820 impolitely generate them for every single stream. (Patch from
8821 mwenge; closes bug 394.)
8822 - Make REMAP stream events have a SOURCE (cache or exit), and
8823 make them generated in every case where we get a successful
8824 connected or resolved cell.
8826 o Minor bugfixes (performance):
8827 - Call router_have_min_dir_info half as often. (This is showing up in
8828 some profiles, but not others.)
8829 - When using GCC, make log_debug never get called at all, and its
8830 arguments never get evaluated, when no debug logs are configured.
8831 (This is showing up in some profiles, but not others.)
8834 - Remove some never-implemented options. Mark PathlenCoinWeight as
8836 - Implement proposal 106: Stop requiring clients to have well-formed
8837 certificates; stop checking nicknames in certificates. (Clients
8838 have certificates so that they can look like Tor servers, but in
8839 the future we might want to allow them to look like regular TLS
8840 clients instead. Nicknames in certificates serve no purpose other
8841 than making our protocol easier to recognize on the wire.)
8842 - Revise messages on handshake failure again to be even more clear about
8843 which are incoming connections and which are outgoing.
8844 - Discard any v1 directory info that's over 1 month old (for
8845 directories) or over 1 week old (for running-routers lists).
8846 - Do not warn when individual nodes in the configuration's EntryNodes,
8847 ExitNodes, etc are down: warn only when all possible nodes
8848 are down. (Fixes bug 348.)
8849 - Always remove expired routers and networkstatus docs before checking
8850 whether we have enough information to build circuits. (Fixes
8852 - Put a lower-bound on MaxAdvertisedBandwidth.
8855 Changes in version 0.1.2.7-alpha - 2007-02-06
8856 o Major bugfixes (rate limiting):
8857 - Servers decline directory requests much more aggressively when
8858 they're low on bandwidth. Otherwise they end up queueing more and
8859 more directory responses, which can't be good for latency.
8860 - But never refuse directory requests from local addresses.
8861 - Fix a memory leak when sending a 503 response for a networkstatus
8863 - Be willing to read or write on local connections (e.g. controller
8864 connections) even when the global rate limiting buckets are empty.
8865 - If our system clock jumps back in time, don't publish a negative
8866 uptime in the descriptor. Also, don't let the global rate limiting
8867 buckets go absurdly negative.
8868 - Flush local controller connection buffers periodically as we're
8869 writing to them, so we avoid queueing 4+ megabytes of data before
8872 o Major bugfixes (NT services):
8873 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
8874 command-line flag so that admins can override the default by saying
8875 "tor --service install --user "SomeUser"". This will not affect
8876 existing installed services. Also, warn the user that the service
8877 will look for its configuration file in the service user's
8878 %appdata% directory. (We can't do the 'hardwire the user's appdata
8879 directory' trick any more, since we may not have read access to that
8882 o Major bugfixes (other):
8883 - Previously, we would cache up to 16 old networkstatus documents
8884 indefinitely, if they came from nontrusted authorities. Now we
8885 discard them if they are more than 10 days old.
8886 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
8888 - Detect and reject malformed DNS responses containing circular
8890 - If exits are rare enough that we're not marking exits as guards,
8891 ignore exit bandwidth when we're deciding the required bandwidth
8893 - When we're handling a directory connection tunneled over Tor,
8894 don't fill up internal memory buffers with all the data we want
8895 to tunnel; instead, only add it if the OR connection that will
8896 eventually receive it has some room for it. (This can lead to
8897 slowdowns in tunneled dir connections; a better solution will have
8900 o Minor bugfixes (dns):
8901 - Add some defensive programming to eventdns.c in an attempt to catch
8902 possible memory-stomping bugs.
8903 - Detect and reject DNS replies containing IPv4 or IPv6 records with
8904 an incorrect number of bytes. (Previously, we would ignore the
8906 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
8907 in the correct order, and doesn't crash.
8908 - Free memory held in recently-completed DNS lookup attempts on exit.
8909 This was not a memory leak, but may have been hiding memory leaks.
8910 - Handle TTL values correctly on reverse DNS lookups.
8911 - Treat failure to parse resolv.conf as an error.
8913 o Minor bugfixes (other):
8914 - Fix crash with "tor --list-fingerprint" (reported by seeess).
8915 - When computing clock skew from directory HTTP headers, consider what
8916 time it was when we finished asking for the directory, not what
8918 - Expire socks connections if they spend too long waiting for the
8919 handshake to finish. Previously we would let them sit around for
8920 days, if the connecting application didn't close them either.
8921 - And if the socks handshake hasn't started, don't send a
8922 "DNS resolve socks failed" handshake reply; just close it.
8923 - Stop using C functions that OpenBSD's linker doesn't like.
8924 - Don't launch requests for descriptors unless we have networkstatuses
8925 from at least half of the authorities. This delays the first
8926 download slightly under pathological circumstances, but can prevent
8927 us from downloading a bunch of descriptors we don't need.
8928 - Do not log IPs with TLS failures for incoming TLS
8929 connections. (Fixes bug 382.)
8930 - If the user asks to use invalid exit nodes, be willing to use
8932 - Stop using the reserved ac_cv namespace in our configure script.
8933 - Call stat() slightly less often; use fstat() when possible.
8934 - Refactor the way we handle pending circuits when an OR connection
8935 completes or fails, in an attempt to fix a rare crash bug.
8936 - Only rewrite a conn's address based on X-Forwarded-For: headers
8937 if it's a parseable public IP address; and stop adding extra quotes
8938 to the resulting address.
8941 - Weight directory requests by advertised bandwidth. Now we can
8942 let servers enable write limiting but still allow most clients to
8943 succeed at their directory requests. (We still ignore weights when
8944 choosing a directory authority; I hope this is a feature.)
8947 - Create a new file ReleaseNotes which was the old ChangeLog. The
8948 new ChangeLog file now includes the summaries for all development
8950 - Check for addresses with invalid characters at the exit as well
8951 as at the client, and warn less verbosely when they fail. You can
8952 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
8953 - Adapt a patch from goodell to let the contrib/exitlist script
8954 take arguments rather than require direct editing.
8955 - Inform the server operator when we decide not to advertise a
8956 DirPort due to AccountingMax enabled or a low BandwidthRate. It
8957 was confusing Zax, so now we're hopefully more helpful.
8958 - Bring us one step closer to being able to establish an encrypted
8959 directory tunnel without knowing a descriptor first. Still not
8960 ready yet. As part of the change, now assume we can use a
8961 create_fast cell if we don't know anything about a router.
8962 - Allow exit nodes to use nameservers running on ports other than 53.
8963 - Servers now cache reverse DNS replies.
8964 - Add an --ignore-missing-torrc command-line option so that we can
8965 get the "use sensible defaults if the configuration file doesn't
8966 exist" behavior even when specifying a torrc location on the command
8969 o Minor features (controller):
8970 - Track reasons for OR connection failure; make these reasons
8971 available via the controller interface. (Patch from Mike Perry.)
8972 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
8973 can learn when clients are sending malformed hostnames to Tor.
8974 - Clean up documentation for controller status events.
8975 - Add a REMAP status to stream events to note that a stream's
8976 address has changed because of a cached address or a MapAddress
8980 Changes in version 0.1.2.6-alpha - 2007-01-09
8982 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
8983 connection handles more than 4 gigs in either direction, we crash.
8984 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
8985 advertised exit node, somebody might try to exit from us when
8986 we're bootstrapping and before we've built our descriptor yet.
8987 Refuse the connection rather than crashing.
8990 - Warn if we (as a server) find that we've resolved an address that we
8991 weren't planning to resolve.
8992 - Warn that using select() on any libevent version before 1.1 will be
8993 unnecessarily slow (even for select()).
8994 - Flush ERR-level controller status events just like we currently
8995 flush ERR-level log events, so that a Tor shutdown doesn't prevent
8996 the controller from learning about current events.
8998 o Minor features (more controller status events):
8999 - Implement EXTERNAL_ADDRESS server status event so controllers can
9000 learn when our address changes.
9001 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
9002 can learn when directories reject our descriptor.
9003 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
9004 can learn when a client application is speaking a non-socks protocol
9006 - Implement DANGEROUS_SOCKS client status event so controllers
9007 can learn when a client application is leaking DNS addresses.
9008 - Implement BUG general status event so controllers can learn when
9009 Tor is unhappy about its internal invariants.
9010 - Implement CLOCK_SKEW general status event so controllers can learn
9011 when Tor thinks the system clock is set incorrectly.
9012 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
9013 server status events so controllers can learn when their descriptors
9014 are accepted by a directory.
9015 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
9016 server status events so controllers can learn about Tor's progress in
9017 deciding whether it's reachable from the outside.
9018 - Implement BAD_LIBEVENT general status event so controllers can learn
9019 when we have a version/method combination in libevent that needs to
9021 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
9022 and DNS_USELESS server status events so controllers can learn
9023 about changes to DNS server status.
9025 o Minor features (directory):
9026 - Authorities no longer recommend exits as guards if this would shift
9027 too much load to the exit nodes.
9030 Changes in version 0.1.2.5-alpha - 2007-01-06
9032 - Enable write limiting as well as read limiting. Now we sacrifice
9033 capacity if we're pushing out lots of directory traffic, rather
9034 than overrunning the user's intended bandwidth limits.
9035 - Include TLS overhead when counting bandwidth usage; previously, we
9036 would count only the bytes sent over TLS, but not the bytes used
9038 - Support running the Tor service with a torrc not in the same
9039 directory as tor.exe and default to using the torrc located in
9040 the %appdata%\Tor\ of the user who installed the service. Patch
9042 - Servers now check for the case when common DNS requests are going to
9043 wildcarded addresses (i.e. all getting the same answer), and change
9044 their exit policy to reject *:* if it's happening.
9045 - Implement BEGIN_DIR cells, so we can connect to the directory
9046 server via TLS to do encrypted directory requests rather than
9047 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
9048 config options if you like.
9050 o Minor features (config and docs):
9051 - Start using the state file to store bandwidth accounting data:
9052 the bw_accounting file is now obsolete. We'll keep generating it
9053 for a while for people who are still using 0.1.2.4-alpha.
9054 - Try to batch changes to the state file so that we do as few
9055 disk writes as possible while still storing important things in
9057 - The state file and the bw_accounting file get saved less often when
9058 the AvoidDiskWrites config option is set.
9059 - Make PIDFile work on Windows (untested).
9060 - Add internal descriptions for a bunch of configuration options:
9061 accessible via controller interface and in comments in saved
9063 - Reject *:563 (NNTPS) in the default exit policy. We already reject
9064 NNTP by default, so this seems like a sensible addition.
9065 - Clients now reject hostnames with invalid characters. This should
9066 avoid some inadvertent info leaks. Add an option
9067 AllowNonRFC953Hostnames to disable this behavior, in case somebody
9068 is running a private network with hosts called @, !, and #.
9069 - Add a maintainer script to tell us which options are missing
9070 documentation: "make check-docs".
9071 - Add a new address-spec.txt document to describe our special-case
9072 addresses: .exit, .onion, and .noconnnect.
9074 o Minor features (DNS):
9075 - Ongoing work on eventdns infrastructure: now it has dns server
9076 and ipv6 support. One day Tor will make use of it.
9077 - Add client-side caching for reverse DNS lookups.
9078 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
9079 - When we change nameservers or IP addresses, reset and re-launch
9080 our tests for DNS hijacking.
9082 o Minor features (directory):
9083 - Authorities now specify server versions in networkstatus. This adds
9084 about 2% to the size of compressed networkstatus docs, and allows
9085 clients to tell which servers support BEGIN_DIR and which don't.
9086 The implementation is forward-compatible with a proposed future
9087 protocol version scheme not tied to Tor versions.
9088 - DirServer configuration lines now have an orport= option so
9089 clients can open encrypted tunnels to the authorities without
9090 having downloaded their descriptors yet. Enabled for moria1,
9091 moria2, tor26, and lefkada now in the default configuration.
9092 - Directory servers are more willing to send a 503 "busy" if they
9093 are near their write limit, especially for v1 directory requests.
9094 Now they can use their limited bandwidth for actual Tor traffic.
9095 - Clients track responses with status 503 from dirservers. After a
9096 dirserver has given us a 503, we try not to use it until an hour has
9097 gone by, or until we have no dirservers that haven't given us a 503.
9098 - When we get a 503 from a directory, and we're not a server, we don't
9099 count the failure against the total number of failures allowed
9100 for the thing we're trying to download.
9101 - Report X-Your-Address-Is correctly from tunneled directory
9102 connections; don't report X-Your-Address-Is when it's an internal
9103 address; and never believe reported remote addresses when they're
9105 - Protect against an unlikely DoS attack on directory servers.
9106 - Add a BadDirectory flag to network status docs so that authorities
9107 can (eventually) tell clients about caches they believe to be
9110 o Minor features (controller):
9111 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
9112 - Reimplement GETINFO so that info/names stays in sync with the
9114 - Implement "GETINFO fingerprint".
9115 - Implement "SETEVENTS GUARD" so controllers can get updates on
9116 entry guard status as it changes.
9118 o Minor features (clean up obsolete pieces):
9119 - Remove some options that have been deprecated since at least
9120 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
9121 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
9123 - We no longer look for identity and onion keys in "identity.key" and
9124 "onion.key" -- these were replaced by secret_id_key and
9125 secret_onion_key in 0.0.8pre1.
9126 - We no longer require unrecognized directory entries to be
9129 o Major bugfixes (security):
9130 - Stop sending the HttpProxyAuthenticator string to directory
9131 servers when directory connections are tunnelled through Tor.
9132 - Clients no longer store bandwidth history in the state file.
9133 - Do not log introduction points for hidden services if SafeLogging
9135 - When generating bandwidth history, round down to the nearest
9136 1k. When storing accounting data, round up to the nearest 1k.
9137 - When we're running as a server, remember when we last rotated onion
9138 keys, so that we will rotate keys once they're a week old even if
9139 we never stay up for a week ourselves.
9141 o Major bugfixes (other):
9142 - Fix a longstanding bug in eventdns that prevented the count of
9143 timed-out resolves from ever being reset. This bug caused us to
9144 give up on a nameserver the third time it timed out, and try it
9145 10 seconds later... and to give up on it every time it timed out
9147 - Take out the '5 second' timeout from the connection retry
9148 schedule. Now the first connect attempt will wait a full 10
9149 seconds before switching to a new circuit. Perhaps this will help
9150 a lot. Based on observations from Mike Perry.
9151 - Fix a bug on the Windows implementation of tor_mmap_file() that
9152 would prevent the cached-routers file from ever loading. Reported
9156 - Fix an assert failure when a directory authority sets
9157 AuthDirRejectUnlisted and then receives a descriptor from an
9158 unlisted router. Reported by seeess.
9159 - Avoid a double-free when parsing malformed DirServer lines.
9160 - Fix a bug when a BSD-style PF socket is first used. Patch from
9162 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
9163 to resolve an address at a given exit node even when they ask for
9165 - Servers no longer ever list themselves in their "family" line,
9166 even if configured to do so. This makes it easier to configure
9167 family lists conveniently.
9168 - When running as a server, don't fall back to 127.0.0.1 when no
9169 nameservers are configured in /etc/resolv.conf; instead, make the
9170 user fix resolv.conf or specify nameservers explicitly. (Resolves
9172 - Stop accepting certain malformed ports in configured exit policies.
9173 - Don't re-write the fingerprint file every restart, unless it has
9175 - Stop warning when a single nameserver fails: only warn when _all_ of
9176 our nameservers have failed. Also, when we only have one nameserver,
9177 raise the threshold for deciding that the nameserver is dead.
9178 - Directory authorities now only decide that routers are reachable
9179 if their identity keys are as expected.
9180 - When the user uses bad syntax in the Log config line, stop
9181 suggesting other bad syntax as a replacement.
9182 - Correctly detect ipv6 DNS capability on OpenBSD.
9184 o Minor bugfixes (controller):
9185 - Report the circuit number correctly in STREAM CLOSED events. Bug
9186 reported by Mike Perry.
9187 - Do not report bizarre values for results of accounting GETINFOs
9188 when the last second's write or read exceeds the allotted bandwidth.
9189 - Report "unrecognized key" rather than an empty string when the
9190 controller tries to fetch a networkstatus that doesn't exist.
9193 Changes in version 0.1.1.26 - 2006-12-14
9194 o Security bugfixes:
9195 - Stop sending the HttpProxyAuthenticator string to directory
9196 servers when directory connections are tunnelled through Tor.
9197 - Clients no longer store bandwidth history in the state file.
9198 - Do not log introduction points for hidden services if SafeLogging
9202 - Fix an assert failure when a directory authority sets
9203 AuthDirRejectUnlisted and then receives a descriptor from an
9204 unlisted router (reported by seeess).
9207 Changes in version 0.1.2.4-alpha - 2006-12-03
9209 - Add support for using natd; this allows FreeBSDs earlier than
9210 5.1.2 to have ipfw send connections through Tor without using
9211 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
9214 - Make all connections to addresses of the form ".noconnect"
9215 immediately get closed. This lets application/controller combos
9216 successfully test whether they're talking to the same Tor by
9217 watching for STREAM events.
9218 - Make cross.sh cross-compilation script work even when autogen.sh
9219 hasn't been run. (Patch from Michael Mohr.)
9220 - Statistics dumped by -USR2 now include a breakdown of public key
9221 operations, for profiling.
9224 - Fix a major leak when directory authorities parse their
9225 approved-routers list, a minor memory leak when we fail to pick
9226 an exit node, and a few rare leaks on errors.
9227 - Handle TransPort connections even when the server sends data before
9228 the client sends data. Previously, the connection would just hang
9229 until the client sent data. (Patch from tup based on patch from
9231 - Avoid assert failure when our cached-routers file is empty on
9235 - Don't log spurious warnings when we see a circuit close reason we
9236 don't recognize; it's probably just from a newer version of Tor.
9237 - Have directory authorities allow larger amounts of drift in uptime
9238 without replacing the server descriptor: previously, a server that
9239 restarted every 30 minutes could have 48 "interesting" descriptors
9241 - Start linking to the Tor specification and Tor reference manual
9242 correctly in the Windows installer.
9243 - Add Vidalia to the OS X uninstaller script, so when we uninstall
9244 Tor/Privoxy we also uninstall Vidalia.
9245 - Resume building on Irix64, and fix a lot of warnings from its
9247 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
9248 when we're running as a client.
9251 Changes in version 0.1.1.25 - 2006-11-04
9253 - When a client asks us to resolve (rather than connect to)
9254 an address, and we have a cached answer, give them the cached
9255 answer. Previously, we would give them no answer at all.
9256 - We were building exactly the wrong circuits when we predict
9257 hidden service requirements, meaning Tor would have to build all
9258 its circuits on demand.
9259 - If none of our live entry guards have a high uptime, but we
9260 require a guard with a high uptime, try adding a new guard before
9261 we give up on the requirement. This patch should make long-lived
9262 connections more stable on average.
9263 - When testing reachability of our DirPort, don't launch new
9264 tests when there's already one in progress -- unreachable
9265 servers were stacking up dozens of testing streams.
9267 o Security bugfixes:
9268 - When the user sends a NEWNYM signal, clear the client-side DNS
9269 cache too. Otherwise we continue to act on previous information.
9272 - Avoid a memory corruption bug when creating a hash table for
9274 - Avoid possibility of controller-triggered crash when misusing
9275 certain commands from a v0 controller on platforms that do not
9276 handle printf("%s",NULL) gracefully.
9277 - Avoid infinite loop on unexpected controller input.
9278 - Don't log spurious warnings when we see a circuit close reason we
9279 don't recognize; it's probably just from a newer version of Tor.
9280 - Add Vidalia to the OS X uninstaller script, so when we uninstall
9281 Tor/Privoxy we also uninstall Vidalia.
9284 Changes in version 0.1.2.3-alpha - 2006-10-29
9286 - Prepare for servers to publish descriptors less often: never
9287 discard a descriptor simply for being too old until either it is
9288 recommended by no authorities, or until we get a better one for
9289 the same router. Make caches consider retaining old recommended
9290 routers for even longer.
9291 - If most authorities set a BadExit flag for a server, clients
9292 don't think of it as a general-purpose exit. Clients only consider
9293 authorities that advertise themselves as listing bad exits.
9294 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
9295 headers for content, so that we can work better in the presence of
9296 caching HTTP proxies.
9297 - Allow authorities to list nodes as bad exits by fingerprint or by
9300 o Minor features, controller:
9301 - Add a REASON field to CIRC events; for backward compatibility, this
9302 field is sent only to controllers that have enabled the extended
9303 event format. Also, add additional reason codes to explain why
9304 a given circuit has been destroyed or truncated. (Patches from
9306 - Add a REMOTE_REASON field to extended CIRC events to tell the
9307 controller about why a remote OR told us to close a circuit.
9308 - Stream events also now have REASON and REMOTE_REASON fields,
9309 working much like those for circuit events.
9310 - There's now a GETINFO ns/... field so that controllers can ask Tor
9311 about the current status of a router.
9312 - A new event type "NS" to inform a controller when our opinion of
9313 a router's status has changed.
9314 - Add a GETINFO events/names and GETINFO features/names so controllers
9315 can tell which events and features are supported.
9316 - A new CLEARDNSCACHE signal to allow controllers to clear the
9317 client-side DNS cache without expiring circuits.
9319 o Security bugfixes:
9320 - When the user sends a NEWNYM signal, clear the client-side DNS
9321 cache too. Otherwise we continue to act on previous information.
9324 - Avoid sending junk to controllers or segfaulting when a controller
9325 uses EVENT_NEW_DESC with verbose nicknames.
9326 - Stop triggering asserts if the controller tries to extend hidden
9327 service circuits (reported by mwenge).
9328 - Avoid infinite loop on unexpected controller input.
9329 - When the controller does a "GETINFO network-status", tell it
9330 about even those routers whose descriptors are very old, and use
9331 long nicknames where appropriate.
9332 - Change NT service functions to be loaded on demand. This lets us
9333 build with MinGW without breaking Tor for Windows 98 users.
9334 - Do DirPort reachability tests less often, since a single test
9335 chews through many circuits before giving up.
9336 - In the hidden service example in torrc.sample, stop recommending
9337 esoteric and discouraged hidden service options.
9338 - When stopping an NT service, wait up to 10 sec for it to actually
9339 stop. Patch from Matt Edman; resolves bug 295.
9340 - Fix handling of verbose nicknames with ORCONN controller events:
9341 make them show up exactly when requested, rather than exactly when
9343 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
9344 printing a duplicate "$" in the keys we send (reported by mwenge).
9345 - Correctly set maximum connection limit on Cygwin. (This time
9347 - Try to detect Windows correctly when cross-compiling.
9348 - Detect the size of the routers file correctly even if it is
9349 corrupted (on systems without mmap) or not page-aligned (on systems
9350 with mmap). This bug was harmless.
9351 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
9352 to open a stream fails; now we do in more cases. This should
9353 make clients able to find a good exit faster in some cases, since
9354 unhandleable requests will now get an error rather than timing out.
9355 - Resolve two memory leaks when rebuilding the on-disk router cache
9356 (reported by fookoowa).
9357 - Clean up minor code warnings suggested by the MIPSpro C compiler,
9358 and reported by some Centos users.
9359 - Controller signals now work on non-Unix platforms that don't define
9360 SIGUSR1 and SIGUSR2 the way we expect.
9361 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
9362 values before failing, and always enables eventdns.
9363 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
9364 Try to fix this in configure.in by checking for most functions
9365 before we check for libevent.
9368 Changes in version 0.1.2.2-alpha - 2006-10-07
9370 - Make our async eventdns library on-by-default for Tor servers,
9371 and plan to deprecate the separate dnsworker threads.
9372 - Add server-side support for "reverse" DNS lookups (using PTR
9373 records so clients can determine the canonical hostname for a given
9374 IPv4 address). Only supported by servers using eventdns; servers
9375 now announce in their descriptors whether they support eventdns.
9376 - Specify and implement client-side SOCKS5 interface for reverse DNS
9377 lookups (see doc/socks-extensions.txt).
9378 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
9379 connect to directory servers through Tor. Previously, clients needed
9380 to find Tor exits to make private connections to directory servers.
9381 - Avoid choosing Exit nodes for entry or middle hops when the
9382 total bandwidth available from non-Exit nodes is much higher than
9383 the total bandwidth available from Exit nodes.
9384 - Workaround for name servers (like Earthlink's) that hijack failing
9385 DNS requests and replace the no-such-server answer with a "helpful"
9386 redirect to an advertising-driven search portal. Also work around
9387 DNS hijackers who "helpfully" decline to hijack known-invalid
9388 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
9389 lets you turn it off.
9390 - Send out a burst of long-range padding cells once we've established
9391 that we're reachable. Spread them over 4 circuits, so hopefully
9392 a few will be fast. This exercises our bandwidth and bootstraps
9393 us into the directory more quickly.
9395 o New/improved config options:
9396 - Add new config option "ResolvConf" to let the server operator
9397 choose an alternate resolve.conf file when using eventdns.
9398 - Add an "EnforceDistinctSubnets" option to control our "exclude
9399 servers on the same /16" behavior. It's still on by default; this
9400 is mostly for people who want to operate private test networks with
9401 all the machines on the same subnet.
9402 - If one of our entry guards is on the ExcludeNodes list, or the
9403 directory authorities don't think it's a good guard, treat it as
9404 if it were unlisted: stop using it as a guard, and throw it off
9405 the guards list if it stays that way for a long time.
9406 - Allow directory authorities to be marked separately as authorities
9407 for the v1 directory protocol, the v2 directory protocol, and
9408 as hidden service directories, to make it easier to retire old
9409 authorities. V1 authorities should set "HSAuthoritativeDir 1"
9410 to continue being hidden service authorities too.
9411 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
9413 o Minor features, controller:
9414 - Fix CIRC controller events so that controllers can learn the
9415 identity digests of non-Named servers used in circuit paths.
9416 - Let controllers ask for more useful identifiers for servers. Instead
9417 of learning identity digests for un-Named servers and nicknames
9418 for Named servers, the new identifiers include digest, nickname,
9419 and indication of Named status. Off by default; see control-spec.txt
9420 for more information.
9421 - Add a "getinfo address" controller command so it can display Tor's
9422 best guess to the user.
9423 - New controller event to alert the controller when our server
9424 descriptor has changed.
9425 - Give more meaningful errors on controller authentication failure.
9427 o Minor features, other:
9428 - When asked to resolve a hostname, don't use non-exit servers unless
9429 requested to do so. This allows servers with broken DNS to be
9430 useful to the network.
9431 - Divide eventdns log messages into warn and info messages.
9432 - Reserve the nickname "Unnamed" for routers that can't pick
9433 a hostname: any router can call itself Unnamed; directory
9434 authorities will never allocate Unnamed to any particular router;
9435 clients won't believe that any router is the canonical Unnamed.
9436 - Only include function names in log messages for info/debug messages.
9437 For notice/warn/err, the content of the message should be clear on
9438 its own, and printing the function name only confuses users.
9439 - Avoid some false positives during reachability testing: don't try
9440 to test via a server that's on the same /24 as us.
9441 - If we fail to build a circuit to an intended enclave, and it's
9442 not mandatory that we use that enclave, stop wanting it.
9443 - When eventdns is enabled, allow multithreaded builds on NetBSD and
9444 OpenBSD. (We had previously disabled threads on these platforms
9445 because they didn't have working thread-safe resolver functions.)
9447 o Major bugfixes, anonymity/security:
9448 - If a client asked for a server by name, and there's a named server
9449 in our network-status but we don't have its descriptor yet, we
9450 could return an unnamed server instead.
9451 - Fix NetBSD bug that could allow someone to force uninitialized RAM
9452 to be sent to a server's DNS resolver. This only affects NetBSD
9453 and other platforms that do not bounds-check tolower().
9454 - Reject (most) attempts to use Tor circuits with length one. (If
9455 many people start using Tor as a one-hop proxy, exit nodes become
9456 a more attractive target for compromise.)
9457 - Just because your DirPort is open doesn't mean people should be
9458 able to remotely teach you about hidden service descriptors. Now
9459 only accept rendezvous posts if you've got HSAuthoritativeDir set.
9461 o Major bugfixes, other:
9462 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
9463 - When a client asks the server to resolve (not connect to)
9464 an address, and it has a cached answer, give them the cached answer.
9465 Previously, the server would give them no answer at all.
9466 - Allow really slow clients to not hang up five minutes into their
9467 directory downloads (suggested by Adam J. Richter).
9468 - We were building exactly the wrong circuits when we anticipated
9469 hidden service requirements, meaning Tor would have to build all
9470 its circuits on demand.
9471 - Avoid crashing when we mmap a router cache file of size 0.
9472 - When testing reachability of our DirPort, don't launch new
9473 tests when there's already one in progress -- unreachable
9474 servers were stacking up dozens of testing streams.
9476 o Minor bugfixes, correctness:
9477 - If we're a directory mirror and we ask for "all" network status
9478 documents, we would discard status documents from authorities
9480 - Avoid a memory corruption bug when creating a hash table for
9482 - Avoid controller-triggered crash when misusing certain commands
9483 from a v0 controller on platforms that do not handle
9484 printf("%s",NULL) gracefully.
9485 - Don't crash when a controller sends a third argument to an
9486 "extendcircuit" request.
9487 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
9488 response; fix error code when "getinfo dir/status/" fails.
9489 - Avoid crash when telling controller stream-status and a stream
9491 - Patch from Adam Langley to fix assert() in eventdns.c.
9492 - Fix a debug log message in eventdns to say "X resolved to Y"
9493 instead of "X resolved to X".
9494 - Make eventdns give strings for DNS errors, not just error numbers.
9495 - Track unreachable entry guards correctly: don't conflate
9496 'unreachable by us right now' with 'listed as down by the directory
9497 authorities'. With the old code, if a guard was unreachable by
9498 us but listed as running, it would clog our guard list forever.
9499 - Behave correctly in case we ever have a network with more than
9500 2GB/s total advertised capacity.
9501 - Make TrackExitHosts case-insensitive, and fix the behavior of
9502 ".suffix" TrackExitHosts items to avoid matching in the middle of
9504 - Finally fix the openssl warnings from newer gccs that believe that
9505 ignoring a return value is okay, but casting a return value and
9506 then ignoring it is a sign of madness.
9507 - Prevent the contrib/exitlist script from printing the same
9508 result more than once.
9509 - Patch from Steve Hildrey: Generate network status correctly on
9510 non-versioning dirservers.
9511 - Don't listen to the X-Your-Address-Is hint if you did the lookup
9512 via Tor; otherwise you'll think you're the exit node's IP address.
9514 o Minor bugfixes, performance:
9515 - Two small performance improvements on parsing descriptors.
9516 - Major performance improvement on inserting descriptors: change
9517 algorithm from O(n^2) to O(n).
9518 - Make the common memory allocation path faster on machines where
9519 malloc(0) returns a pointer.
9520 - Start remembering X-Your-Address-Is directory hints even if you're
9521 a client, so you can become a server more smoothly.
9522 - Avoid duplicate entries on MyFamily line in server descriptor.
9524 o Packaging, features:
9525 - Remove architecture from OS X builds. The official builds are
9526 now universal binaries.
9527 - The Debian package now uses --verify-config when (re)starting,
9528 to distinguish configuration errors from other errors.
9529 - Update RPMs to require libevent 1.1b.
9531 o Packaging, bugfixes:
9532 - Patches so Tor builds with MinGW on Windows.
9533 - Patches so Tor might run on Cygwin again.
9534 - Resume building on non-gcc compilers and ancient gcc. Resume
9535 building with the -O0 compile flag. Resume building cleanly on
9537 - Run correctly on OS X platforms with case-sensitive filesystems.
9538 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
9539 - Add autoconf checks so Tor can build on Solaris x86 again.
9542 - Documented (and renamed) ServerDNSSearchDomains and
9543 ServerDNSResolvConfFile options.
9544 - Be clearer that the *ListenAddress directives can be repeated
9548 Changes in version 0.1.1.24 - 2006-09-29
9550 - Allow really slow clients to not hang up five minutes into their
9551 directory downloads (suggested by Adam J. Richter).
9552 - Fix major performance regression from 0.1.0.x: instead of checking
9553 whether we have enough directory information every time we want to
9554 do something, only check when the directory information has changed.
9555 This should improve client CPU usage by 25-50%.
9556 - Don't crash if, after a server has been running for a while,
9557 it can't resolve its hostname.
9560 - Allow Tor to start when RunAsDaemon is set but no logs are set.
9561 - Don't crash when the controller receives a third argument to an
9562 "extendcircuit" request.
9563 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
9564 response; fix error code when "getinfo dir/status/" fails.
9565 - Fix configure.in to not produce broken configure files with
9566 more recent versions of autoconf. Thanks to Clint for his auto*
9568 - Fix security bug on NetBSD that could allow someone to force
9569 uninitialized RAM to be sent to a server's DNS resolver. This
9570 only affects NetBSD and other platforms that do not bounds-check
9572 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
9573 methods: these are known to be buggy.
9574 - If we're a directory mirror and we ask for "all" network status
9575 documents, we would discard status documents from authorities
9579 Changes in version 0.1.2.1-alpha - 2006-08-27
9581 - Add "eventdns" async dns library from Adam Langley, tweaked to
9582 build on OSX and Windows. Only enabled if you pass the
9583 --enable-eventdns argument to configure.
9584 - Allow servers with no hostname or IP address to learn their
9585 IP address by asking the directory authorities. This code only
9586 kicks in when you would normally have exited with a "no address"
9587 error. Nothing's authenticated, so use with care.
9588 - Rather than waiting a fixed amount of time between retrying
9589 application connections, we wait only 5 seconds for the first,
9590 10 seconds for the second, and 15 seconds for each retry after
9591 that. Hopefully this will improve the expected user experience.
9592 - Patch from Tup to add support for transparent AP connections:
9593 this basically bundles the functionality of trans-proxy-tor
9594 into the Tor mainline. Now hosts with compliant pf/netfilter
9595 implementations can redirect TCP connections straight to Tor
9596 without diverting through SOCKS. Needs docs.
9597 - Busy directory servers save lots of memory by spooling server
9598 descriptors, v1 directories, and v2 networkstatus docs to buffers
9599 as needed rather than en masse. Also mmap the cached-routers
9600 files, so we don't need to keep the whole thing in memory too.
9601 - Automatically avoid picking more than one node from the same
9602 /16 network when constructing a circuit.
9603 - Revise and clean up the torrc.sample that we ship with; add
9604 a section for BandwidthRate and BandwidthBurst.
9607 - Split circuit_t into origin_circuit_t and or_circuit_t, and
9608 split connection_t into edge, or, dir, control, and base structs.
9609 These will save quite a bit of memory on busy servers, and they'll
9610 also help us track down bugs in the code and bugs in the spec.
9611 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
9612 or later. Log when we are doing this, so we can diagnose it when
9613 it fails. (Also, recommend libevent 1.1b for kqueue and
9614 win32 methods; deprecate libevent 1.0b harder; make libevent
9615 recommendation system saner.)
9616 - Start being able to build universal binaries on OS X (thanks
9618 - Export the default exit policy via the control port, so controllers
9619 don't need to guess what it is / will be later.
9620 - Add a man page entry for ProtocolWarnings.
9621 - Add TestVia config option to the man page.
9622 - Remove even more protocol-related warnings from Tor server logs,
9623 such as bad TLS handshakes and malformed begin cells.
9624 - Stop fetching descriptors if you're not a dir mirror and you
9625 haven't tried to establish any circuits lately. [This currently
9626 causes some dangerous behavior, because when you start up again
9627 you'll use your ancient server descriptors.]
9628 - New DirPort behavior: if you have your dirport set, you download
9629 descriptors aggressively like a directory mirror, whether or not
9631 - Get rid of the router_retry_connections notion. Now routers
9632 no longer try to rebuild long-term connections to directory
9633 authorities, and directory authorities no longer try to rebuild
9634 long-term connections to all servers. We still don't hang up
9635 connections in these two cases though -- we need to look at it
9636 more carefully to avoid flapping, and we likely need to wait til
9637 0.1.1.x is obsolete.
9638 - Drop compatibility with obsolete Tors that permit create cells
9639 to have the wrong circ_id_type.
9640 - Re-enable per-connection rate limiting. Get rid of the "OP
9641 bandwidth" concept. Lay groundwork for "bandwidth classes" --
9642 separate global buckets that apply depending on what sort of conn
9644 - Start publishing one minute or so after we find our ORPort
9645 to be reachable. This will help reduce the number of descriptors
9646 we have for ourselves floating around, since it's quite likely
9647 other things (e.g. DirPort) will change during that minute too.
9648 - Fork the v1 directory protocol into its own spec document,
9649 and mark dir-spec.txt as the currently correct (v2) spec.
9652 - When we find our DirPort to be reachable, publish a new descriptor
9653 so we'll tell the world (reported by pnx).
9654 - Publish a new descriptor after we hup/reload. This is important
9655 if our config has changed such that we'll want to start advertising
9656 our DirPort now, etc.
9657 - Allow Tor to start when RunAsDaemon is set but no logs are set.
9658 - When we have a state file we cannot parse, tell the user and
9659 move it aside. Now we avoid situations where the user starts
9660 Tor in 1904, Tor writes a state file with that timestamp in it,
9661 the user fixes her clock, and Tor refuses to start.
9662 - Fix configure.in to not produce broken configure files with
9663 more recent versions of autoconf. Thanks to Clint for his auto*
9665 - "tor --verify-config" now exits with -1(255) or 0 depending on
9666 whether the config options are bad or good.
9667 - Resolve bug 321 when using dnsworkers: append a period to every
9668 address we resolve at the exit node, so that we do not accidentally
9669 pick up local addresses, and so that failing searches are retried
9670 in the resolver search domains. (This is already solved for
9671 eventdns.) (This breaks Blossom servers for now.)
9672 - If we are using an exit enclave and we can't connect, e.g. because
9673 its webserver is misconfigured to not listen on localhost, then
9674 back off and try connecting from somewhere else before we fail.
9677 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
9678 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
9679 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
9680 when the IP address is mapped through MapAddress to a hostname.
9681 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
9682 useless IPv6 DNS resolves.
9683 - Patch suggested by Karsten Loesing: respond to SIGNAL command
9684 before we execute the signal, in case the signal shuts us down.
9685 - Clean up AllowInvalidNodes man page entry.
9686 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
9687 - Add more asserts to track down an assert error on a windows Tor
9688 server with connection_add being called with socket == -1.
9689 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
9690 - Fix misleading log messages: an entry guard that is "unlisted",
9691 as well as not known to be "down" (because we've never heard
9692 of it), is not therefore "up".
9693 - Remove code to special-case "-cvs" ending, since it has not
9694 actually mattered since 0.0.9.
9695 - Make our socks5 handling more robust to broken socks clients:
9696 throw out everything waiting on the buffer in between socks
9697 handshake phases, since they can't possibly (so the theory
9698 goes) have predicted what we plan to respond to them.
9701 Changes in version 0.1.1.23 - 2006-07-30
9703 - Fast Tor servers, especially exit nodes, were triggering asserts
9704 due to a bug in handling the list of pending DNS resolves. Some
9705 bugs still remain here; we're hunting them.
9706 - Entry guards could crash clients by sending unexpected input.
9707 - More fixes on reachability testing: if you find yourself reachable,
9708 then don't ever make any client requests (so you stop predicting
9709 circuits), then hup or have your clock jump, then later your IP
9710 changes, you won't think circuits are working, so you won't try to
9711 test reachability, so you won't publish.
9714 - Avoid a crash if the controller does a resetconf firewallports
9715 and then a setconf fascistfirewall=1.
9716 - Avoid an integer underflow when the dir authority decides whether
9717 a router is stable: we might wrongly label it stable, and compute
9718 a slightly wrong median stability, when a descriptor is published
9720 - Fix a place where we might trigger an assert if we can't build our
9721 own server descriptor yet.
9724 Changes in version 0.1.1.22 - 2006-07-05
9726 - Fix a big bug that was causing servers to not find themselves
9727 reachable if they changed IP addresses. Since only 0.1.1.22+
9728 servers can do reachability testing correctly, now we automatically
9729 make sure to test via one of these.
9730 - Fix to allow clients and mirrors to learn directory info from
9731 descriptor downloads that get cut off partway through.
9732 - Directory authorities had a bug in deciding if a newly published
9733 descriptor was novel enough to make everybody want a copy -- a few
9734 servers seem to be publishing new descriptors many times a minute.
9736 - Fix a rare bug that was causing some servers to complain about
9737 "closing wedged cpuworkers" and skip some circuit create requests.
9738 - Make the Exit flag in directory status documents actually work.
9741 Changes in version 0.1.1.21 - 2006-06-10
9742 o Crash and assert fixes from 0.1.1.20:
9743 - Fix a rare crash on Tor servers that have enabled hibernation.
9744 - Fix a seg fault on startup for Tor networks that use only one
9745 directory authority.
9746 - Fix an assert from a race condition that occurs on Tor servers
9747 while exiting, where various threads are trying to log that they're
9748 exiting, and delete the logs, at the same time.
9749 - Make our unit tests pass again on certain obscure platforms.
9752 - Add support for building SUSE RPM packages.
9753 - Speed up initial bootstrapping for clients: if we are making our
9754 first ever connection to any entry guard, then don't mark it down
9756 - When only one Tor server in the network is labelled as a guard,
9757 and we've already picked him, we would cycle endlessly picking him
9758 again, being unhappy about it, etc. Now we specifically exclude
9759 current guards when picking a new guard.
9760 - Servers send create cells more reliably after the TLS connection
9761 is established: we were sometimes forgetting to send half of them
9762 when we had more than one pending.
9763 - If we get a create cell that asks us to extend somewhere, but the
9764 Tor server there doesn't match the expected digest, we now send
9765 a destroy cell back, rather than silently doing nothing.
9766 - Make options->RedirectExit work again.
9767 - Make cookie authentication for the controller work again.
9768 - Stop being picky about unusual characters in the arguments to
9769 mapaddress. It's none of our business.
9770 - Add a new config option "TestVia" that lets you specify preferred
9771 middle hops to use for test circuits. Perhaps this will let me
9772 debug the reachability problems better.
9774 o Log / documentation fixes:
9775 - If we're a server and some peer has a broken TLS certificate, don't
9776 log about it unless ProtocolWarnings is set, i.e., we want to hear
9777 about protocol violations by others.
9778 - Fix spelling of VirtualAddrNetwork in man page.
9779 - Add a better explanation at the top of the autogenerated torrc file
9780 about what happened to our old torrc.
9783 Changes in version 0.1.1.20 - 2006-05-23
9785 - Downgrade a log severity where servers complain that they're
9787 - Avoid a compile warning on FreeBSD.
9788 - Remove string size limit on NEWDESC messages; solve bug 291.
9789 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
9790 more thoroughly when we're running on windows.
9793 Changes in version 0.1.1.19-rc - 2006-05-03
9795 - Regenerate our local descriptor if it's dirty and we try to use
9796 it locally (e.g. if it changes during reachability detection).
9797 - If we setconf our ORPort to 0, we continued to listen on the
9798 old ORPort and receive connections.
9799 - Avoid a second warning about machine/limits.h on Debian
9801 - Be willing to add our own routerinfo into the routerlist.
9802 Now authorities will include themselves in their directories
9803 and network-statuses.
9804 - Stop trying to upload rendezvous descriptors to every
9805 directory authority: only try the v1 authorities.
9806 - Servers no longer complain when they think they're not
9807 registered with the directory authorities. There were too many
9809 - Backport dist-rpm changes so rpms can be built without errors.
9812 - Implement an option, VirtualAddrMask, to set which addresses
9813 get handed out in response to mapaddress requests. This works
9814 around a bug in tsocks where 127.0.0.0/8 is never socksified.
9817 Changes in version 0.1.1.18-rc - 2006-04-10
9819 - Work harder to download live network-statuses from all the
9820 directory authorities we know about. Improve the threshold
9821 decision logic so we're more robust to edge cases.
9822 - When fetching rendezvous descriptors, we were willing to ask
9823 v2 authorities too, which would always return 404.
9826 - Stop listing down or invalid nodes in the v1 directory. This will
9827 reduce its bulk by about 1/3, and reduce load on directory
9829 - When deciding whether a router is Fast or Guard-worthy, consider
9830 his advertised BandwidthRate and not just the BandwidthCapacity.
9831 - No longer ship INSTALL and README files -- they are useless now.
9832 - Force rpmbuild to behave and honor target_cpu.
9833 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
9834 - Start to include translated versions of the tor-doc-*.html
9835 files, along with the screenshots. Still needs more work.
9836 - Start sending back 512 and 451 errors if mapaddress fails,
9837 rather than not sending anything back at all.
9838 - When we fail to bind or listen on an incoming or outgoing
9839 socket, we should close it before failing. otherwise we just
9840 leak it. (thanks to weasel for finding.)
9841 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
9842 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
9843 - Make NoPublish (even though deprecated) work again.
9844 - Fix a minor security flaw where a versioning auth dirserver
9845 could list a recommended version many times in a row to make
9846 clients more convinced that it's recommended.
9847 - Fix crash bug if there are two unregistered servers running
9848 with the same nickname, one of them is down, and you ask for
9849 them by nickname in your EntryNodes or ExitNodes. Also, try
9850 to pick the one that's running rather than an arbitrary one.
9851 - Fix an infinite loop we could hit if we go offline for too long.
9852 - Complain when we hit WSAENOBUFS on recv() or write() too.
9853 Perhaps this will help us hunt the bug.
9854 - If you're not a versioning dirserver, don't put the string
9855 "client-versions \nserver-versions \n" in your network-status.
9856 - Lower the minimum required number of file descriptors to 1000,
9857 so we can have some overhead for Valgrind on Linux, where the
9858 default ulimit -n is 1024.
9861 - Add tor.dizum.com as the fifth authoritative directory server.
9862 - Add a new config option FetchUselessDescriptors, off by default,
9863 for when you plan to run "exitlist" on your client and you want
9864 to know about even the non-running descriptors.
9867 Changes in version 0.1.1.17-rc - 2006-03-28
9869 - Clients and servers since 0.1.1.10-alpha have been expiring
9870 connections whenever they are idle for 5 minutes and they *do*
9871 have circuits on them. Oops. With this new version, clients will
9872 discard their previous entry guard choices and avoid choosing
9873 entry guards running these flawed versions.
9874 - Fix memory leak when uncompressing concatenated zlib streams. This
9875 was causing substantial leaks over time on Tor servers.
9876 - The v1 directory was including servers as much as 48 hours old,
9877 because that's how the new routerlist->routers works. Now only
9878 include them if they're 20 hours old or less.
9881 - Resume building on irix64, netbsd 2.0, etc.
9882 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
9884 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
9885 and it is confusing some users.
9886 - Mirrors stop caching the v1 directory so often.
9887 - Make the max number of old descriptors that a cache will hold
9888 rise with the number of directory authorities, so we can scale.
9889 - Change our win32 uname() hack to be more forgiving about what
9890 win32 versions it thinks it's found.
9893 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
9895 - When the controller's *setconf commands fail, collect an error
9896 message in a string and hand it back to the controller.
9897 - Make the v2 dir's "Fast" flag based on relative capacity, just
9898 like "Stable" is based on median uptime. Name everything in the
9899 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
9900 - Log server fingerprint on startup, so new server operators don't
9901 have to go hunting around their filesystem for it.
9902 - Return a robots.txt on our dirport to discourage google indexing.
9903 - Let the controller ask for GETINFO dir/status/foo so it can ask
9904 directly rather than connecting to the dir port. Only works when
9905 dirport is set for now.
9907 o New config options rather than constants in the code:
9908 - SocksTimeout: How long do we let a socks connection wait
9909 unattached before we fail it?
9910 - CircuitBuildTimeout: Cull non-open circuits that were born
9911 at least this many seconds ago.
9912 - CircuitIdleTimeout: Cull open clean circuits that were born
9913 at least this many seconds ago.
9916 Changes in version 0.1.1.16-rc - 2006-03-18
9917 o Bugfixes on 0.1.1.15-rc:
9918 - Fix assert when the controller asks to attachstream a connect-wait
9919 or resolve-wait stream.
9920 - Now do address rewriting when the controller asks us to attach
9921 to a particular circuit too. This will let Blossom specify
9922 "moria2.exit" without having to learn what moria2's IP address is.
9923 - Make the "tor --verify-config" command-line work again, so people
9924 can automatically check if their torrc will parse.
9925 - Authoritative dirservers no longer require an open connection from
9926 a server to consider him "reachable". We need this change because
9927 when we add new auth dirservers, old servers won't know not to
9929 - Let Tor build on Sun CC again.
9930 - Fix an off-by-one buffer size in dirserv.c that magically never
9931 hit our three authorities but broke sjmurdoch's own tor network.
9932 - If we as a directory mirror don't know of any v1 directory
9933 authorities, then don't try to cache any v1 directories.
9934 - Stop warning about unknown servers in our family when they are
9935 given as hex digests.
9936 - Stop complaining as quickly to the server operator that he
9937 hasn't registered his nickname/key binding.
9938 - Various cleanups so we can add new V2 Auth Dirservers.
9939 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
9940 reflect the updated flags in our v2 dir protocol.
9941 - Resume allowing non-printable characters for exit streams (both
9942 for connecting and for resolving). Now we tolerate applications
9943 that don't follow the RFCs. But continue to block malformed names
9946 o Bugfixes on 0.1.0.x:
9947 - Fix assert bug in close_logs(): when we close and delete logs,
9948 remove them all from the global "logfiles" list.
9949 - Fix minor integer overflow in calculating when we expect to use up
9950 our bandwidth allocation before hibernating.
9951 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
9952 there are multiple SSLs installed with different versions.
9953 - When we try to be a server and Address is not explicitly set and
9954 our hostname resolves to a private IP address, try to use an
9955 interface address if it has a public address. Now Windows machines
9956 that think of themselves as localhost can work by default.
9959 - Let the controller ask for GETINFO dir/server/foo so it can ask
9960 directly rather than connecting to the dir port.
9961 - Let the controller tell us about certain router descriptors
9962 that it doesn't want Tor to use in circuits. Implement
9963 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
9964 - New config option SafeSocks to reject all application connections
9965 using unsafe socks protocols. Defaults to off.
9968 Changes in version 0.1.1.15-rc - 2006-03-11
9969 o Bugfixes and cleanups:
9970 - When we're printing strings from the network, don't try to print
9971 non-printable characters. This protects us against shell escape
9972 sequence exploits, and also against attacks to fool humans into
9973 misreading their logs.
9974 - Fix a bug where Tor would fail to establish any connections if you
9975 left it off for 24 hours and then started it: we were happy with
9976 the obsolete network statuses, but they all referred to router
9977 descriptors that were too old to fetch, so we ended up with no
9978 valid router descriptors.
9979 - Fix a seg fault in the controller's "getinfo orconn-status"
9980 command while listing status on incoming handshaking connections.
9981 Introduce a status name "NEW" for these connections.
9982 - If we get a linelist or linelist_s config option from the torrc
9983 (e.g. ExitPolicy) and it has no value, warn and skip rather than
9984 silently resetting it to its default.
9985 - Don't abandon entry guards until they've been down or gone for
9987 - Cleaner and quieter log messages.
9990 - New controller signal NEWNYM that makes new application requests
9992 - Add a new circuit purpose 'controller' to let the controller ask
9993 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
9994 controller command to let you specify the purpose if you're
9995 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
9996 command to let you change a circuit's purpose after it's been
9998 - Accept "private:*" in routerdesc exit policies; not generated yet
9999 because older Tors do not understand it.
10000 - Add BSD-style contributed startup script "rc.subr" from Peter
10004 Changes in version 0.1.1.14-alpha - 2006-02-20
10005 o Bugfixes on 0.1.1.x:
10006 - Don't die if we ask for a stdout or stderr log (even implicitly)
10007 and we're set to RunAsDaemon -- just warn.
10008 - We still had a few bugs in the OR connection rotation code that
10009 caused directory servers to slowly aggregate connections to other
10010 fast Tor servers. This time for sure!
10011 - Make log entries on Win32 include the name of the function again.
10012 - We were treating a pair of exit policies if they were equal even
10013 if one said accept and the other said reject -- causing us to
10014 not always publish a new descriptor since we thought nothing
10016 - Retry pending server downloads as well as pending networkstatus
10017 downloads when we unexpectedly get a socks request.
10018 - We were ignoring the IS_FAST flag in the directory status,
10019 meaning we were willing to pick trivial-bandwidth nodes for "fast"
10021 - If the controller's SAVECONF command fails (e.g. due to file
10022 permissions), let the controller know that it failed.
10025 - If we're trying to be a Tor server and running Windows 95/98/ME
10026 as a server, explain that we'll likely crash.
10027 - When we're a server, a client asks for an old-style directory,
10028 and our write bucket is empty, don't give it to him. This way
10029 small servers can continue to serve the directory *sometimes*,
10030 without getting overloaded.
10031 - Compress exit policies even more -- look for duplicate lines
10033 - Clients now honor the "guard" flag in the router status when
10034 picking entry guards, rather than looking at is_fast or is_stable.
10035 - Retain unrecognized lines in $DATADIR/state file, so that we can
10036 be forward-compatible.
10037 - Generate 18.0.0.0/8 address policy format in descs when we can;
10038 warn when the mask is not reducible to a bit-prefix.
10039 - Let the user set ControlListenAddress in the torrc. This can be
10040 dangerous, but there are some cases (like a secured LAN) where it
10042 - Split ReachableAddresses into ReachableDirAddresses and
10043 ReachableORAddresses, so we can restrict Dir conns to port 80
10044 and OR conns to port 443.
10045 - Now we can target arch and OS in rpm builds (contributed by
10046 Phobos). Also make the resulting dist-rpm filename match the
10048 - New config options to help controllers: FetchServerDescriptors
10049 and FetchHidServDescriptors for whether to fetch server
10050 info and hidserv info or let the controller do it, and
10051 PublishServerDescriptor and PublishHidServDescriptors.
10052 - Also let the controller set the __AllDirActionsPrivate config
10053 option if you want all directory fetches/publishes to happen via
10054 Tor (it assumes your controller bootstraps your circuits).
10057 Changes in version 0.1.0.17 - 2006-02-17
10058 o Crash bugfixes on 0.1.0.x:
10059 - When servers with a non-zero DirPort came out of hibernation,
10060 sometimes they would trigger an assert.
10062 o Other important bugfixes:
10063 - On platforms that don't have getrlimit (like Windows), we were
10064 artificially constraining ourselves to a max of 1024
10065 connections. Now just assume that we can handle as many as 15000
10066 connections. Hopefully this won't cause other problems.
10068 o Backported features:
10069 - When we're a server, a client asks for an old-style directory,
10070 and our write bucket is empty, don't give it to him. This way
10071 small servers can continue to serve the directory *sometimes*,
10072 without getting overloaded.
10073 - Whenever you get a 503 in response to a directory fetch, try
10074 once more. This will become important once servers start sending
10075 503's whenever they feel busy.
10076 - Fetch a new directory every 120 minutes, not every 40 minutes.
10077 Now that we have hundreds of thousands of users running the old
10078 directory algorithm, it's starting to hurt a lot.
10079 - Bump up the period for forcing a hidden service descriptor upload
10080 from 20 minutes to 1 hour.
10083 Changes in version 0.1.1.13-alpha - 2006-02-09
10084 o Crashes in 0.1.1.x:
10085 - When you tried to setconf ORPort via the controller, Tor would
10086 crash. So people using TorCP to become a server were sad.
10087 - Solve (I hope) the stack-smashing bug that we were seeing on fast
10088 servers. The problem appears to be something do with OpenSSL's
10089 random number generation, or how we call it, or something. Let me
10090 know if the crashes continue.
10091 - Turn crypto hardware acceleration off by default, until we find
10092 somebody smart who can test it for us. (It appears to produce
10093 seg faults in at least some cases.)
10094 - Fix a rare assert error when we've tried all intro points for
10095 a hidden service and we try fetching the service descriptor again:
10096 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
10099 - Fix a major load balance bug: we were round-robining in 16 KB
10100 chunks, and servers with bandwidthrate of 20 KB, while downloading
10101 a 600 KB directory, would starve their other connections. Now we
10102 try to be a bit more fair.
10103 - Dir authorities and mirrors were never expiring the newest
10104 descriptor for each server, causing memory and directory bloat.
10105 - Fix memory-bloating and connection-bloating bug on servers: We
10106 were never closing any connection that had ever had a circuit on
10107 it, because we were checking conn->n_circuits == 0, yet we had a
10108 bug that let it go negative.
10109 - Make Tor work using squid as your http proxy again -- squid
10110 returns an error if you ask for a URL that's too long, and it uses
10111 a really generic error message. Plus, many people are behind a
10112 transparent squid so they don't even realize it.
10113 - On platforms that don't have getrlimit (like Windows), we were
10114 artificially constraining ourselves to a max of 1024
10115 connections. Now just assume that we can handle as many as 15000
10116 connections. Hopefully this won't cause other problems.
10117 - Add a new config option ExitPolicyRejectPrivate which defaults to
10118 1. This means all exit policies will begin with rejecting private
10119 addresses, unless the server operator explicitly turns it off.
10122 - Clients no longer download descriptors for non-running
10124 - Before we add new directory authorities, we should make it
10125 clear that only v1 authorities should receive/publish hidden
10126 service descriptors.
10129 - As soon as we've fetched some more directory info, immediately
10130 try to download more server descriptors. This way we don't have
10131 a 10 second pause during initial bootstrapping.
10132 - Remove even more loud log messages that the server operator can't
10134 - When we're running an obsolete or un-recommended version, make
10135 the log message more clear about what the problem is and what
10136 versions *are* still recommended.
10137 - Provide a more useful warn message when our onion queue gets full:
10138 the CPU is too slow or the exit policy is too liberal.
10139 - Don't warn when we receive a 503 from a dirserver/cache -- this
10140 will pave the way for them being able to refuse if they're busy.
10141 - When we fail to bind a listener, try to provide a more useful
10142 log message: e.g., "Is Tor already running?"
10143 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
10144 Goldberg can prove things about our handshake protocol more
10146 - MaxConn has been obsolete for a while now. Document the ConnLimit
10147 config option, which is a *minimum* number of file descriptors
10148 that must be available else Tor refuses to start.
10149 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
10150 if you log to syslog and want something other than LOG_DAEMON.
10151 - Make dirservers generate a separate "guard" flag to mean,
10152 "would make a good entry guard". Make clients parse it and vote
10153 on it. Not used by clients yet.
10154 - Implement --with-libevent-dir option to ./configure. Also, improve
10155 search techniques to find libevent, and use those for openssl too.
10156 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
10157 - Only start testing reachability once we've established a
10158 circuit. This will make startup on dirservers less noisy.
10159 - Don't try to upload hidden service descriptors until we have
10160 established a circuit.
10161 - Fix the controller's "attachstream 0" command to treat conn like
10162 it just connected, doing address remapping, handling .exit and
10163 .onion idioms, and so on. Now we're more uniform in making sure
10164 that the controller hears about new and closing connections.
10167 Changes in version 0.1.1.12-alpha - 2006-01-11
10168 o Bugfixes on 0.1.1.x:
10169 - The fix to close duplicate server connections was closing all
10170 Tor client connections if they didn't establish a circuit
10171 quickly enough. Oops.
10172 - Fix minor memory issue (double-free) that happened on exit.
10174 o Bugfixes on 0.1.0.x:
10175 - Tor didn't warn when it failed to open a log file.
10178 Changes in version 0.1.1.11-alpha - 2006-01-10
10179 o Crashes in 0.1.1.x:
10180 - Include all the assert/crash fixes from 0.1.0.16.
10181 - If you start Tor and then quit very quickly, there were some
10182 races that tried to free things that weren't allocated yet.
10183 - Fix a rare memory stomp if you're running hidden services.
10184 - Fix segfault when specifying DirServer in config without nickname.
10185 - Fix a seg fault when you finish connecting to a server but at
10186 that moment you dump his server descriptor.
10187 - Extendcircuit and Attachstream controller commands would
10188 assert/crash if you don't give them enough arguments.
10189 - Fix an assert error when we're out of space in the connection_list
10190 and we try to post a hidden service descriptor (reported by weasel).
10191 - If you specify a relative torrc path and you set RunAsDaemon in
10192 your torrc, then it chdir()'s to the new directory. If you HUP,
10193 it tries to load the new torrc location, fails, and exits.
10194 The fix: no longer allow a relative path to torrc using -f.
10197 - Implement "entry guards": automatically choose a handful of entry
10198 nodes and stick with them for all circuits. Only pick new guards
10199 when the ones you have are unsuitable, and if the old guards
10200 become suitable again, switch back. This will increase security
10201 dramatically against certain end-point attacks. The EntryNodes
10202 config option now provides some hints about which entry guards you
10203 want to use most; and StrictEntryNodes means to only use those.
10204 - New directory logic: download by descriptor digest, not by
10205 fingerprint. Caches try to download all listed digests from
10206 authorities; clients try to download "best" digests from caches.
10207 This avoids partitioning and isolating attacks better.
10208 - Make the "stable" router flag in network-status be the median of
10209 the uptimes of running valid servers, and make clients pay
10210 attention to the network-status flags. Thus the cutoff adapts
10211 to the stability of the network as a whole, making IRC, IM, etc
10212 connections more reliable.
10215 - Tor servers with dynamic IP addresses were needing to wait 18
10216 hours before they could start doing reachability testing using
10217 the new IP address and ports. This is because they were using
10218 the internal descriptor to learn what to test, yet they were only
10219 rebuilding the descriptor once they decided they were reachable.
10220 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
10221 to download certain server descriptors, throw them away, and then
10222 fetch them again after 30 minutes. Now mirrors throw away these
10223 server descriptors so clients can't get them.
10224 - We were leaving duplicate connections to other ORs open for a week,
10225 rather than closing them once we detect a duplicate. This only
10226 really affected authdirservers, but it affected them a lot.
10227 - Spread the authdirservers' reachability testing over the entire
10228 testing interval, so we don't try to do 500 TLS's at once every
10232 - If the network is down, and we try to connect to a conn because
10233 we have a circuit in mind, and we timeout (30 seconds) because the
10234 network never answers, we were expiring the circuit, but we weren't
10235 obsoleting the connection or telling the entry_guards functions.
10236 - Some Tor servers process billions of cells per day. These statistics
10237 need to be uint64_t's.
10238 - Check for integer overflows in more places, when adding elements
10239 to smartlists. This could possibly prevent a buffer overflow
10240 on malicious huge inputs. I don't see any, but I haven't looked
10242 - ReachableAddresses kept growing new "reject *:*" lines on every
10244 - When you "setconf log" via the controller, it should remove all
10245 logs. We were automatically adding back in a "log notice stdout".
10246 - Newly bootstrapped Tor networks couldn't establish hidden service
10247 circuits until they had nodes with high uptime. Be more tolerant.
10248 - We were marking servers down when they could not answer every piece
10249 of the directory request we sent them. This was far too harsh.
10250 - Fix the torify (tsocks) config file to not use Tor for localhost
10252 - Directory authorities now go to the proper authority when asking for
10253 a networkstatus, even when they want a compressed one.
10254 - Fix a harmless bug that was causing Tor servers to log
10255 "Got an end because of misc error, but we're not an AP. Closing."
10256 - Authorities were treating their own descriptor changes as cosmetic,
10257 meaning the descriptor available in the network-status and the
10258 descriptor that clients downloaded were different.
10259 - The OS X installer was adding a symlink for tor_resolve but
10260 the binary was called tor-resolve (reported by Thomas Hardly).
10261 - Workaround a problem with some http proxies where they refuse GET
10262 requests that specify "Content-Length: 0" (reported by Adrian).
10263 - Fix wrong log message when you add a "HiddenServiceNodes" config
10264 line without any HiddenServiceDir line (reported by Chris Thomas).
10267 - Write the TorVersion into the state file so we have a prayer of
10268 keeping forward and backward compatibility.
10269 - Revive the FascistFirewall config option rather than eliminating it:
10270 now it's a synonym for ReachableAddresses *:80,*:443.
10271 - Clients choose directory servers from the network status lists,
10272 not from their internal list of router descriptors. Now they can
10273 go to caches directly rather than needing to go to authorities
10275 - Directory authorities ignore router descriptors that have only
10276 cosmetic differences: do this for 0.1.0.x servers now too.
10277 - Add a new flag to network-status indicating whether the server
10278 can answer v2 directory requests too.
10279 - Authdirs now stop whining so loudly about bad descriptors that
10280 they fetch from other dirservers. So when there's a log complaint,
10281 it's for sure from a freshly uploaded descriptor.
10282 - Reduce memory requirements in our structs by changing the order
10284 - There used to be two ways to specify your listening ports in a
10285 server descriptor: on the "router" line and with a separate "ports"
10286 line. Remove support for the "ports" line.
10287 - New config option "AuthDirRejectUnlisted" for auth dirservers as
10288 a panic button: if we get flooded with unusable servers we can
10289 revert to only listing servers in the approved-routers file.
10290 - Auth dir servers can now mark a fingerprint as "!reject" or
10291 "!invalid" in the approved-routers file (as its nickname), to
10292 refuse descriptors outright or include them but marked as invalid.
10293 - Servers store bandwidth history across restarts/crashes.
10294 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
10295 get a better idea of why their circuits failed. Not used yet.
10296 - Directory mirrors now cache up to 16 unrecognized network-status
10297 docs. Now we can add new authdirservers and they'll be cached too.
10298 - When picking a random directory, prefer non-authorities if any
10300 - New controller option "getinfo desc/all-recent" to fetch the
10301 latest server descriptor for every router that Tor knows about.
10304 Changes in version 0.1.0.16 - 2006-01-02
10305 o Crash bugfixes on 0.1.0.x:
10306 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
10307 corrupting the heap, losing FDs, or crashing when we need to resize
10308 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
10309 - It turns out sparc64 platforms crash on unaligned memory access
10310 too -- so detect and avoid this.
10311 - Handle truncated compressed data correctly (by detecting it and
10313 - Fix possible-but-unlikely free(NULL) in control.c.
10314 - When we were closing connections, there was a rare case that
10315 stomped on memory, triggering seg faults and asserts.
10316 - Avoid potential infinite recursion when building a descriptor. (We
10317 don't know that it ever happened, but better to fix it anyway.)
10318 - We were neglecting to unlink marked circuits from soon-to-close OR
10319 connections, which caused some rare scribbling on freed memory.
10320 - Fix a memory stomping race bug when closing the joining point of two
10321 rendezvous circuits.
10322 - Fix an assert in time parsing found by Steven Murdoch.
10324 o Other bugfixes on 0.1.0.x:
10325 - When we're doing reachability testing, provide more useful log
10326 messages so the operator knows what to expect.
10327 - Do not check whether DirPort is reachable when we are suppressing
10328 advertising it because of hibernation.
10329 - When building with -static or on Solaris, we sometimes needed -ldl.
10330 - When we're deciding whether a stream has enough circuits around
10331 that can handle it, count the freshly dirty ones and not the ones
10332 that are so dirty they won't be able to handle it.
10333 - When we're expiring old circuits, we had a logic error that caused
10334 us to close new rendezvous circuits rather than old ones.
10335 - Give a more helpful log message when you try to change ORPort via
10336 the controller: you should upgrade Tor if you want that to work.
10337 - We were failing to parse Tor versions that start with "Tor ".
10338 - Tolerate faulty streams better: when a stream fails for reason
10339 exitpolicy, stop assuming that the router is lying about his exit
10340 policy. When a stream fails for reason misc, allow it to retry just
10341 as if it was resolvefailed. When a stream has failed three times,
10342 reset its failure count so we can try again and get all three tries.
10345 Changes in version 0.1.1.10-alpha - 2005-12-11
10346 o Correctness bugfixes on 0.1.0.x:
10347 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
10348 corrupting the heap, losing FDs, or crashing when we need to resize
10349 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
10350 - Stop doing the complex voodoo overkill checking for insecure
10351 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
10352 - When we were closing connections, there was a rare case that
10353 stomped on memory, triggering seg faults and asserts.
10354 - We were neglecting to unlink marked circuits from soon-to-close OR
10355 connections, which caused some rare scribbling on freed memory.
10356 - When we're deciding whether a stream has enough circuits around
10357 that can handle it, count the freshly dirty ones and not the ones
10358 that are so dirty they won't be able to handle it.
10359 - Recover better from TCP connections to Tor servers that are
10360 broken but don't tell you (it happens!); and rotate TLS
10361 connections once a week.
10362 - When we're expiring old circuits, we had a logic error that caused
10363 us to close new rendezvous circuits rather than old ones.
10364 - Fix a scary-looking but apparently harmless bug where circuits
10365 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
10366 servers, and never switch to state CIRCUIT_STATE_OPEN.
10367 - When building with -static or on Solaris, we sometimes needed to
10369 - Give a useful message when people run Tor as the wrong user,
10370 rather than telling them to start chowning random directories.
10371 - We were failing to inform the controller about new .onion streams.
10373 o Security bugfixes on 0.1.0.x:
10374 - Refuse server descriptors if the fingerprint line doesn't match
10375 the included identity key. Tor doesn't care, but other apps (and
10376 humans) might actually be trusting the fingerprint line.
10377 - We used to kill the circuit when we receive a relay command we
10378 don't recognize. Now we just drop it.
10379 - Start obeying our firewall options more rigorously:
10380 . If we can't get to a dirserver directly, try going via Tor.
10381 . Don't ever try to connect (as a client) to a place our
10382 firewall options forbid.
10383 . If we specify a proxy and also firewall options, obey the
10384 firewall options even when we're using the proxy: some proxies
10385 can only proxy to certain destinations.
10386 - Fix a bug found by Lasse Overlier: when we were making internal
10387 circuits (intended to be cannibalized later for rendezvous and
10388 introduction circuits), we were picking them so that they had
10389 useful exit nodes. There was no need for this, and it actually
10390 aids some statistical attacks.
10391 - Start treating internal circuits and exit circuits separately.
10392 It's important to keep them separate because internal circuits
10393 have their last hops picked like middle hops, rather than like
10394 exit hops. So exiting on them will break the user's expectations.
10396 o Bugfixes on 0.1.1.x:
10397 - Take out the mis-feature where we tried to detect IP address
10398 flapping for people with DynDNS, and chose not to upload a new
10399 server descriptor sometimes.
10400 - Try to be compatible with OpenSSL 0.9.6 again.
10401 - Log fix: when the controller is logging about .onion addresses,
10402 sometimes it didn't include the ".onion" part of the address.
10403 - Don't try to modify options->DirServers internally -- if the
10404 user didn't specify any, just add the default ones directly to
10405 the trusted dirserver list. This fixes a bug where people running
10406 controllers would use SETCONF on some totally unrelated config
10407 option, and Tor would start yelling at them about changing their
10409 - Let the controller's redirectstream command specify a port, in
10410 case the controller wants to change that too.
10411 - When we requested a pile of server descriptors, we sometimes
10412 accidentally launched a duplicate request for the first one.
10413 - Bugfix for trackhostexits: write down the fingerprint of the
10414 chosen exit, not its nickname, because the chosen exit might not
10416 - When parsing foo.exit, if foo is unknown, and we are leaving
10417 circuits unattached, set the chosen_exit field and leave the
10418 address empty. This matters because controllers got confused
10420 - Directory authorities no longer try to download server
10421 descriptors that they know they will reject.
10423 o Features and updates:
10424 - Replace balanced trees with hash tables: this should make stuff
10425 significantly faster.
10426 - Resume using the AES counter-mode implementation that we ship,
10427 rather than OpenSSL's. Ours is significantly faster.
10428 - Many other CPU and memory improvements.
10429 - Add a new config option FastFirstHopPK (on by default) so clients
10430 do a trivial crypto handshake for their first hop, since TLS has
10431 already taken care of confidentiality and authentication.
10432 - Add a new config option TestSocks so people can see if their
10433 applications are using socks4, socks4a, socks5-with-ip, or
10434 socks5-with-hostname. This way they don't have to keep mucking
10435 with tcpdump and wondering if something got cached somewhere.
10436 - Warn when listening on a public address for socks. I suspect a
10437 lot of people are setting themselves up as open socks proxies,
10438 and they have no idea that jerks on the Internet are using them,
10439 since they simply proxy the traffic into the Tor network.
10440 - Add "private:*" as an alias in configuration for policies. Now
10441 you can simplify your exit policy rather than needing to list
10442 every single internal or nonroutable network space.
10443 - Add a new controller event type that allows controllers to get
10444 all server descriptors that were uploaded to a router in its role
10445 as authoritative dirserver.
10446 - Start shipping socks-extensions.txt, tor-doc-unix.html,
10447 tor-doc-server.html, and stylesheet.css in the tarball.
10448 - Stop shipping tor-doc.html in the tarball.
10451 Changes in version 0.1.1.9-alpha - 2005-11-15
10452 o Usability improvements:
10453 - Start calling it FooListenAddress rather than FooBindAddress,
10454 since few of our users know what it means to bind an address
10456 - Reduce clutter in server logs. We're going to try to make
10457 them actually usable now. New config option ProtocolWarnings that
10458 lets you hear about how _other Tors_ are breaking the protocol. Off
10460 - Divide log messages into logging domains. Once we put some sort
10461 of interface on this, it will let people looking at more verbose
10462 log levels specify the topics they want to hear more about.
10463 - Make directory servers return better http 404 error messages
10464 instead of a generic "Servers unavailable".
10465 - Check for even more Windows version flags when writing the platform
10466 string in server descriptors, and note any we don't recognize.
10467 - Clean up more of the OpenSSL memory when exiting, so we can detect
10468 memory leaks better.
10469 - Make directory authorities be non-versioning, non-naming by
10470 default. Now we can add new directory servers without requiring
10471 their operators to pay close attention.
10472 - When logging via syslog, include the pid whenever we provide
10473 a log entry. Suggested by Todd Fries.
10475 o Performance improvements:
10476 - Directory servers now silently throw away new descriptors that
10477 haven't changed much if the timestamps are similar. We do this to
10478 tolerate older Tor servers that upload a new descriptor every 15
10479 minutes. (It seemed like a good idea at the time.)
10480 - Inline bottleneck smartlist functions; use fast versions by default.
10481 - Add a "Map from digest to void*" abstraction digestmap_t so we
10482 can do less hex encoding/decoding. Use it in router_get_by_digest()
10483 to resolve a performance bottleneck.
10484 - Allow tor_gzip_uncompress to extract as much as possible from
10485 truncated compressed data. Try to extract as many
10486 descriptors as possible from truncated http responses (when
10487 DIR_PURPOSE_FETCH_ROUTERDESC).
10488 - Make circ->onionskin a pointer, not a static array. moria2 was using
10489 125000 circuit_t's after it had been up for a few weeks, which
10490 translates to 20+ megs of wasted space.
10491 - The private half of our EDH handshake keys are now chosen out
10492 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
10494 o Security improvements:
10495 - Start making directory caches retain old routerinfos, so soon
10496 clients can start asking by digest of descriptor rather than by
10497 fingerprint of server.
10498 - Add half our entropy from RAND_poll in OpenSSL. This knows how
10499 to use egd (if present), openbsd weirdness (if present), vms/os2
10500 weirdness (if we ever port there), and more in the future.
10502 o Bugfixes on 0.1.0.x:
10503 - Do round-robin writes of at most 16 kB per write. This might be
10504 more fair on loaded Tor servers, and it might resolve our Windows
10505 crash bug. It might also slow things down.
10506 - Our TLS handshakes were generating a single public/private
10507 keypair for the TLS context, rather than making a new one for
10508 each new connections. Oops. (But we were still rotating them
10509 periodically, so it's not so bad.)
10510 - When we were cannibalizing a circuit with a particular exit
10511 node in mind, we weren't checking to see if that exit node was
10512 already present earlier in the circuit. Oops.
10513 - When a Tor server's IP changes (e.g. from a dyndns address),
10514 upload a new descriptor so clients will learn too.
10515 - Really busy servers were keeping enough circuits open on stable
10516 connections that they were wrapping around the circuit_id
10517 space. (It's only two bytes.) This exposed a bug where we would
10518 feel free to reuse a circuit_id even if it still exists but has
10519 been marked for close. Try to fix this bug. Some bug remains.
10520 - If we would close a stream early (e.g. it asks for a .exit that
10521 we know would refuse it) but the LeaveStreamsUnattached config
10522 option is set by the controller, then don't close it.
10524 o Bugfixes on 0.1.1.8-alpha:
10525 - Fix a big pile of memory leaks, some of them serious.
10526 - Do not try to download a routerdesc if we would immediately reject
10528 - Resume inserting a newline between all router descriptors when
10529 generating (old style) signed directories, since our spec says
10531 - When providing content-type application/octet-stream for
10532 server descriptors using .z, we were leaving out the
10533 content-encoding header. Oops. (Everything tolerated this just
10534 fine, but that doesn't mean we need to be part of the problem.)
10535 - Fix a potential seg fault in getconf and getinfo using version 1
10536 of the controller protocol.
10537 - Avoid crash: do not check whether DirPort is reachable when we
10538 are suppressing it because of hibernation.
10539 - Make --hash-password not crash on exit.
10542 Changes in version 0.1.1.8-alpha - 2005-10-07
10543 o New features (major):
10544 - Clients don't download or use the directory anymore. Now they
10545 download and use network-statuses from the trusted dirservers,
10546 and fetch individual server descriptors as needed from mirrors.
10547 See dir-spec.txt for all the gory details.
10548 - Be more conservative about whether to advertise our DirPort.
10549 The main change is to not advertise if we're running at capacity
10550 and either a) we could hibernate or b) our capacity is low and
10551 we're using a default DirPort.
10552 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
10554 o New features (minor):
10555 - Try to be smart about when to retry network-status and
10556 server-descriptor fetches. Still needs some tuning.
10557 - Stop parsing, storing, or using running-routers output (but
10558 mirrors still cache and serve it).
10559 - Consider a threshold of versioning dirservers (dirservers who have
10560 an opinion about which Tor versions are still recommended) before
10561 deciding whether to warn the user that he's obsolete.
10562 - Dirservers can now reject/invalidate by key and IP, with the
10563 config options "AuthDirInvalid" and "AuthDirReject". This is
10564 useful since currently we automatically list servers as running
10565 and usable even if we know they're jerks.
10566 - Provide dire warnings to any users who set DirServer; move it out
10567 of torrc.sample and into torrc.complete.
10568 - Add MyFamily to torrc.sample in the server section.
10569 - Add nicknames to the DirServer line, so we can refer to them
10570 without requiring all our users to memorize their IP addresses.
10571 - When we get an EOF or a timeout on a directory connection, note
10572 how many bytes of serverdesc we are dropping. This will help
10573 us determine whether it is smart to parse incomplete serverdesc
10575 - Add a new function to "change pseudonyms" -- that is, to stop
10576 using any currently-dirty circuits for new streams, so we don't
10577 link new actions to old actions. Currently it's only called on
10578 HUP (or SIGNAL RELOAD).
10579 - On sighup, if UseHelperNodes changed to 1, use new circuits.
10580 - Start using RAND_bytes rather than RAND_pseudo_bytes from
10581 OpenSSL. Also, reseed our entropy every hour, not just at
10582 startup. And entropy in 512-bit chunks, not 160-bit chunks.
10584 o Fixes on 0.1.1.7-alpha:
10585 - Nobody ever implemented EVENT_ADDRMAP for control protocol
10586 version 0, so don't let version 0 controllers ask for it.
10587 - If you requested something with too many newlines via the
10588 v1 controller protocol, you could crash tor.
10589 - Fix a number of memory leaks, including some pretty serious ones.
10590 - Re-enable DirPort testing again, so Tor servers will be willing
10591 to advertise their DirPort if it's reachable.
10592 - On TLS handshake, only check the other router's nickname against
10593 its expected nickname if is_named is set.
10595 o Fixes forward-ported from 0.1.0.15:
10596 - Don't crash when we don't have any spare file descriptors and we
10597 try to spawn a dns or cpu worker.
10598 - Make the numbers in read-history and write-history into uint64s,
10599 so they don't overflow and publish negatives in the descriptor.
10601 o Fixes on 0.1.0.x:
10602 - For the OS X package's modified privoxy config file, comment
10603 out the "logfile" line so we don't log everything passed
10605 - We were whining about using socks4 or socks5-with-local-lookup
10606 even when it's an IP in the "virtual" range we designed exactly
10608 - We were leaking some memory every time the client changes IPs.
10609 - Never call free() on tor_malloc()d memory. This will help us
10610 use dmalloc to detect memory leaks.
10611 - Check for named servers when looking them up by nickname;
10612 warn when we'recalling a non-named server by its nickname;
10613 don't warn twice about the same name.
10614 - Try to list MyFamily elements by key, not by nickname, and warn
10615 if we've not heard of the server.
10616 - Make windows platform detection (uname equivalent) smarter.
10617 - It turns out sparc64 doesn't like unaligned access either.
10620 Changes in version 0.1.0.15 - 2005-09-23
10621 o Bugfixes on 0.1.0.x:
10622 - Reject ports 465 and 587 (spam targets) in default exit policy.
10623 - Don't crash when we don't have any spare file descriptors and we
10624 try to spawn a dns or cpu worker.
10625 - Get rid of IgnoreVersion undocumented config option, and make us
10626 only warn, never exit, when we're running an obsolete version.
10627 - Don't try to print a null string when your server finds itself to
10628 be unreachable and the Address config option is empty.
10629 - Make the numbers in read-history and write-history into uint64s,
10630 so they don't overflow and publish negatives in the descriptor.
10631 - Fix a minor memory leak in smartlist_string_remove().
10632 - We were only allowing ourselves to upload a server descriptor at
10633 most every 20 minutes, even if it changed earlier than that.
10634 - Clean up log entries that pointed to old URLs.
10637 Changes in version 0.1.1.7-alpha - 2005-09-14
10638 o Fixes on 0.1.1.6-alpha:
10639 - Exit servers were crashing when people asked them to make a
10640 connection to an address not in their exit policy.
10641 - Looking up a non-existent stream for a v1 control connection would
10643 - Fix a seg fault if we ask a dirserver for a descriptor by
10644 fingerprint but he doesn't know about him.
10645 - SETCONF was appending items to linelists, not clearing them.
10646 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
10647 out and refuse the setconf if it would fail.
10648 - Downgrade the dirserver log messages when whining about
10652 - Add Peter Palfrader's check-tor script to tor/contrib/
10653 It lets you easily check whether a given server (referenced by
10654 nickname) is reachable by you.
10655 - Numerous changes to move towards client-side v2 directories. Not
10658 o Fixes on 0.1.0.x:
10659 - If the user gave tor an odd number of command-line arguments,
10660 we were silently ignoring the last one. Now we complain and fail.
10661 [This wins the oldest-bug prize -- this bug has been present since
10662 November 2002, as released in Tor 0.0.0.]
10663 - Do not use unaligned memory access on alpha, mips, or mipsel.
10664 It *works*, but is very slow, so we treat them as if it doesn't.
10665 - Retry directory requests if we fail to get an answer we like
10666 from a given dirserver (we were retrying before, but only if
10667 we fail to connect).
10668 - When writing the RecommendedVersions line, sort them first.
10669 - When the client asked for a rendezvous port that the hidden
10670 service didn't want to provide, we were sending an IP address
10671 back along with the end cell. Fortunately, it was zero. But stop
10673 - Correct "your server is reachable" log entries to indicate that
10674 it was self-testing that told us so.
10677 Changes in version 0.1.1.6-alpha - 2005-09-09
10678 o Fixes on 0.1.1.5-alpha:
10679 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
10680 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
10681 - Fix bug with tor_memmem finding a match at the end of the string.
10682 - Make unit tests run without segfaulting.
10683 - Resolve some solaris x86 compile warnings.
10684 - Handle duplicate lines in approved-routers files without warning.
10685 - Fix bug where as soon as a server refused any requests due to his
10686 exit policy (e.g. when we ask for localhost and he tells us that's
10687 127.0.0.1 and he won't do it), we decided he wasn't obeying his
10688 exit policy using him for any exits.
10689 - Only do openssl hardware accelerator stuff if openssl version is
10692 o New controller features/fixes:
10693 - Add a "RESETCONF" command so you can set config options like
10694 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
10695 a config option in the torrc with no value, then it clears it
10696 entirely (rather than setting it to its default).
10697 - Add a "GETINFO config-file" to tell us where torrc is.
10698 - Avoid sending blank lines when GETINFO replies should be empty.
10699 - Add a QUIT command for the controller (for using it manually).
10700 - Fix a bug in SAVECONF that was adding default dirservers and
10701 other redundant entries to the torrc file.
10703 o Start on the new directory design:
10704 - Generate, publish, cache, serve new network-status format.
10705 - Publish individual descriptors (by fingerprint, by "all", and by
10707 - Publish client and server recommended versions separately.
10708 - Allow tor_gzip_uncompress() to handle multiple concatenated
10709 compressed strings. Serve compressed groups of router
10710 descriptors. The compression logic here could be more
10712 - Distinguish v1 authorities (all currently trusted directories)
10713 from v2 authorities (all trusted directories).
10714 - Change DirServers config line to note which dirs are v1 authorities.
10715 - Add configuration option "V1AuthoritativeDirectory 1" which
10716 moria1, moria2, and tor26 should set.
10717 - Remove option when getting directory cache to see whether they
10718 support running-routers; they all do now. Replace it with one
10719 to see whether caches support v2 stuff.
10722 - Dirservers now do their own external reachability testing of each
10723 Tor server, and only list them as running if they've been found to
10724 be reachable. We also send back warnings to the server's logs if
10725 it uploads a descriptor that we already believe is unreachable.
10726 - Implement exit enclaves: if we know an IP address for the
10727 destination, and there's a running Tor server at that address
10728 which allows exit to the destination, then extend the circuit to
10729 that exit first. This provides end-to-end encryption and end-to-end
10730 authentication. Also, if the user wants a .exit address or enclave,
10731 use 4 hops rather than 3, and cannibalize a general circ for it
10733 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
10734 controller. Also, rotate dns and cpu workers if the controller
10735 changes options that will affect them; and initialize the dns
10736 worker cache tree whether or not we start out as a server.
10737 - Only upload a new server descriptor when options change, 18
10738 hours have passed, uptime is reset, or bandwidth changes a lot.
10739 - Check [X-]Forwarded-For headers in HTTP requests when generating
10740 log messages. This lets people run dirservers (and caches) behind
10741 Apache but still know which IP addresses are causing warnings.
10743 o Config option changes:
10744 - Replace (Fascist)Firewall* config options with a new
10745 ReachableAddresses option that understands address policies.
10746 For example, "ReachableAddresses *:80,*:443"
10747 - Get rid of IgnoreVersion undocumented config option, and make us
10748 only warn, never exit, when we're running an obsolete version.
10749 - Make MonthlyAccountingStart config option truly obsolete now.
10751 o Fixes on 0.1.0.x:
10752 - Reject ports 465 and 587 in the default exit policy, since
10753 people have started using them for spam too.
10754 - It turns out we couldn't bootstrap a network since we added
10755 reachability detection in 0.1.0.1-rc. Good thing the Tor network
10756 has never gone down. Add an AssumeReachable config option to let
10757 servers and dirservers bootstrap. When we're trying to build a
10758 high-uptime or high-bandwidth circuit but there aren't enough
10759 suitable servers, try being less picky rather than simply failing.
10760 - Our logic to decide if the OR we connected to was the right guy
10761 was brittle and maybe open to a mitm for unverified routers.
10762 - We weren't cannibalizing circuits correctly for
10763 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
10764 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
10765 build those from scratch. This should make hidden services faster.
10766 - Predict required circuits better, with an eye toward making hidden
10767 services faster on the service end.
10768 - Retry streams if the exit node sends back a 'misc' failure. This
10769 should result in fewer random failures. Also, after failing
10770 from resolve failed or misc, reset the num failures, so we give
10771 it a fair shake next time we try.
10772 - Clean up the rendezvous warn log msgs, and downgrade some to info.
10773 - Reduce severity on logs about dns worker spawning and culling.
10774 - When we're shutting down and we do something like try to post a
10775 server descriptor or rendezvous descriptor, don't complain that
10776 we seem to be unreachable. Of course we are, we're shutting down.
10777 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
10778 We don't use them yet, but maybe one day our DNS resolver will be
10779 able to discover them.
10780 - Make ContactInfo mandatory for authoritative directory servers.
10781 - Require server descriptors to list IPv4 addresses -- hostnames
10782 are no longer allowed. This also fixes some potential security
10783 problems with people providing hostnames as their address and then
10784 preferentially resolving them to partition users.
10785 - Change log line for unreachability to explicitly suggest /etc/hosts
10786 as the culprit. Also make it clearer what IP address and ports we're
10787 testing for reachability.
10788 - Put quotes around user-supplied strings when logging so users are
10789 more likely to realize if they add bad characters (like quotes)
10791 - Let auth dir servers start without specifying an Address config
10793 - Make unit tests (and other invocations that aren't the real Tor)
10794 run without launching listeners, creating subdirectories, and so on.
10797 Changes in version 0.1.1.5-alpha - 2005-08-08
10798 o Bugfixes included in 0.1.0.14.
10800 o Bugfixes on 0.1.0.x:
10801 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
10802 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
10803 it would silently using ignore the 6668.
10806 Changes in version 0.1.0.14 - 2005-08-08
10807 o Bugfixes on 0.1.0.x:
10808 - Fix the other half of the bug with crypto handshakes
10810 - Fix an assert trigger if you send a 'signal term' via the
10811 controller when it's listening for 'event info' messages.
10814 Changes in version 0.1.1.4-alpha - 2005-08-04
10815 o Bugfixes included in 0.1.0.13.
10818 - Improve tor_gettimeofday() granularity on windows.
10819 - Make clients regenerate their keys when their IP address changes.
10820 - Implement some more GETINFO goodness: expose helper nodes, config
10821 options, getinfo keys.
10824 Changes in version 0.1.0.13 - 2005-08-04
10825 o Bugfixes on 0.1.0.x:
10826 - Fix a critical bug in the security of our crypto handshakes.
10827 - Fix a size_t underflow in smartlist_join_strings2() that made
10828 it do bad things when you hand it an empty smartlist.
10829 - Fix Windows installer to ship Tor license (thanks to Aphex for
10830 pointing out this oversight) and put a link to the doc directory
10832 - Explicitly set no-unaligned-access for sparc: it turns out the
10833 new gcc's let you compile broken code, but that doesn't make it
10837 Changes in version 0.1.1.3-alpha - 2005-07-23
10838 o Bugfixes on 0.1.1.2-alpha:
10839 - Fix a bug in handling the controller's "post descriptor"
10841 - Fix several bugs in handling the controller's "extend circuit"
10843 - Fix a bug in handling the controller's "stream status" event.
10844 - Fix an assert failure if we have a controller listening for
10845 circuit events and we go offline.
10846 - Re-allow hidden service descriptors to publish 0 intro points.
10847 - Fix a crash when generating your hidden service descriptor if
10848 you don't have enough intro points already.
10850 o New features on 0.1.1.2-alpha:
10851 - New controller function "getinfo accounting", to ask how
10852 many bytes we've used in this time period.
10853 - Experimental support for helper nodes: a lot of the risk from
10854 a small static adversary comes because users pick new random
10855 nodes every time they rebuild a circuit. Now users will try to
10856 stick to the same small set of entry nodes if they can. Not
10857 enabled by default yet.
10859 o Bugfixes on 0.1.0.12:
10860 - If you're an auth dir server, always publish your dirport,
10861 even if you haven't yet found yourself to be reachable.
10862 - Fix a size_t underflow in smartlist_join_strings2() that made
10863 it do bad things when you hand it an empty smartlist.
10866 Changes in version 0.1.0.12 - 2005-07-18
10867 o New directory servers:
10868 - tor26 has changed IP address.
10870 o Bugfixes on 0.1.0.x:
10871 - Fix a possible double-free in tor_gzip_uncompress().
10872 - When --disable-threads is set, do not search for or link against
10873 pthreads libraries.
10874 - Don't trigger an assert if an authoritative directory server
10875 claims its dirport is 0.
10876 - Fix bug with removing Tor as an NT service: some people were
10877 getting "The service did not return an error." Thanks to Matt
10881 Changes in version 0.1.1.2-alpha - 2005-07-15
10882 o New directory servers:
10883 - tor26 has changed IP address.
10885 o Bugfixes on 0.1.0.x, crashes/leaks:
10886 - Port the servers-not-obeying-their-exit-policies fix from
10888 - Fix an fd leak in start_daemon().
10889 - On Windows, you can't always reopen a port right after you've
10890 closed it. So change retry_listeners() to only close and re-open
10891 ports that have changed.
10892 - Fix a possible double-free in tor_gzip_uncompress().
10894 o Bugfixes on 0.1.0.x, usability:
10895 - When tor_socketpair() fails in Windows, give a reasonable
10896 Windows-style errno back.
10897 - Let people type "tor --install" as well as "tor -install" when
10899 want to make it an NT service.
10900 - NT service patch from Matt Edman to improve error messages.
10901 - When the controller asks for a config option with an abbreviated
10902 name, give the full name in our response.
10903 - Correct the man page entry on TrackHostExitsExpire.
10904 - Looks like we were never delivering deflated (i.e. compressed)
10905 running-routers lists, even when asked. Oops.
10906 - When --disable-threads is set, do not search for or link against
10907 pthreads libraries.
10909 o Bugfixes on 0.1.1.x:
10910 - Fix a seg fault with autodetecting which controller version is
10914 - New hidden service descriptor format: put a version in it, and
10915 let people specify introduction/rendezvous points that aren't
10916 in "the directory" (which is subjective anyway).
10917 - Allow the DEBUG controller event to work again. Mark certain log
10918 entries as "don't tell this to controllers", so we avoid cycles.
10921 Changes in version 0.1.0.11 - 2005-06-30
10922 o Bugfixes on 0.1.0.x:
10923 - Fix major security bug: servers were disregarding their
10924 exit policies if clients behaved unexpectedly.
10925 - Make OS X init script check for missing argument, so we don't
10926 confuse users who invoke it incorrectly.
10927 - Fix a seg fault in "tor --hash-password foo".
10928 - The MAPADDRESS control command was broken.
10931 Changes in version 0.1.1.1-alpha - 2005-06-29
10933 - Make OS X init script check for missing argument, so we don't
10934 confuse users who invoke it incorrectly.
10935 - Fix a seg fault in "tor --hash-password foo".
10936 - Fix a possible way to DoS dirservers.
10937 - When we complain that your exit policy implicitly allows local or
10938 private address spaces, name them explicitly so operators can
10940 - Make the log message less scary when all the dirservers are
10941 temporarily unreachable.
10942 - We were printing the number of idle dns workers incorrectly when
10946 - Revised controller protocol (version 1) that uses ascii rather
10947 than binary. Add supporting libraries in python and java so you
10948 can use the controller from your applications without caring how
10949 our protocol works.
10950 - Spiffy new support for crypto hardware accelerators. Can somebody
10954 Changes in version 0.0.9.10 - 2005-06-16
10955 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
10956 - Refuse relay cells that claim to have a length larger than the
10957 maximum allowed. This prevents a potential attack that could read
10958 arbitrary memory (e.g. keys) from an exit server's process
10962 Changes in version 0.1.0.10 - 2005-06-14
10963 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
10964 libevent before 1.1a.
10967 Changes in version 0.1.0.9-rc - 2005-06-09
10969 - Reset buf->highwater every time buf_shrink() is called, not just on
10970 a successful shrink. This was causing significant memory bloat.
10971 - Fix buffer overflow when checking hashed passwords.
10972 - Security fix: if seeding the RNG on Win32 fails, quit.
10973 - Allow seeding the RNG on Win32 even when you're not running as
10975 - Disable threading on Solaris too. Something is wonky with it,
10976 cpuworkers, and reentrant libs.
10977 - Reenable the part of the code that tries to flush as soon as an
10978 OR outbuf has a full TLS record available. Perhaps this will make
10979 OR outbufs not grow as huge except in rare cases, thus saving lots
10980 of CPU time plus memory.
10981 - Reject malformed .onion addresses rather then passing them on as
10982 normal web requests.
10983 - Adapt patch from Adam Langley: fix possible memory leak in
10984 tor_lookup_hostname().
10985 - Initialize libevent later in the startup process, so the logs are
10986 already established by the time we start logging libevent warns.
10987 - Use correct errno on win32 if libevent fails.
10988 - Check and warn about known-bad/slow libevent versions.
10989 - Pay more attention to the ClientOnly config option.
10990 - Have torctl.in/tor.sh.in check for location of su binary (needed
10992 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
10993 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
10994 HttpProxyAuthenticator
10995 - Stop warning about sigpipes in the logs. We're going to
10996 pretend that getting these occassionally is normal and fine.
10997 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
10999 installer screens; and don't put stuff into StartupItems unless
11000 the user asks you to.
11001 - Require servers that use the default dirservers to have public IP
11002 addresses. We have too many servers that are configured with private
11003 IPs and their admins never notice the log entries complaining that
11004 their descriptors are being rejected.
11005 - Add OSX uninstall instructions. An actual uninstall script will
11009 Changes in version 0.1.0.8-rc - 2005-05-23
11011 - It turns out that kqueue on OS X 10.3.9 was causing kernel
11012 panics. Disable kqueue on all OS X Tors.
11013 - Fix RPM: remove duplicate line accidentally added to the rpm
11015 - Disable threads on openbsd too, since its gethostaddr is not
11017 - Tolerate libevent 0.8 since it still works, even though it's
11019 - Enable building on Red Hat 9.0 again.
11020 - Allow the middle hop of the testing circuit to be running any
11021 version, now that most of them have the bugfix to let them connect
11022 to unknown servers. This will allow reachability testing to work
11023 even when 0.0.9.7-0.0.9.9 become obsolete.
11024 - Handle relay cells with rh.length too large. This prevents
11025 a potential attack that could read arbitrary memory (maybe even
11026 keys) from the exit server's process.
11027 - We screwed up the dirport reachability testing when we don't yet
11028 have a cached version of the directory. Hopefully now fixed.
11029 - Clean up router_load_single_router() (used by the controller),
11030 so it doesn't seg fault on error.
11031 - Fix a minor memory leak when somebody establishes an introduction
11032 point at your Tor server.
11033 - If a socks connection ends because read fails, don't warn that
11034 you're not sending a socks reply back.
11037 - Add HttpProxyAuthenticator config option too, that works like
11038 the HttpsProxyAuthenticator config option.
11039 - Encode hashed controller passwords in hex instead of base64,
11040 to make it easier to write controllers.
11043 Changes in version 0.1.0.7-rc - 2005-05-17
11045 - Fix a bug in the OS X package installer that prevented it from
11046 installing on Tiger.
11047 - Fix a script bug in the OS X package installer that made it
11048 complain during installation.
11049 - Find libevent even if it's hiding in /usr/local/ and your
11050 CFLAGS and LDFLAGS don't tell you to look there.
11051 - Be able to link with libevent as a shared library (the default
11052 after 1.0d), even if it's hiding in /usr/local/lib and even
11053 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
11054 assuming you're running gcc. Otherwise fail and give a useful
11056 - Fix a bug in the RPM packager: set home directory for _tor to
11057 something more reasonable when first installing.
11058 - Free a minor amount of memory that is still reachable on exit.
11061 Changes in version 0.1.0.6-rc - 2005-05-14
11063 - Implement --disable-threads configure option. Disable threads on
11064 netbsd by default, because it appears to have no reentrant resolver
11066 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
11067 release (1.1) detects and disables kqueue if it's broken.
11068 - Append default exit policy before checking for implicit internal
11069 addresses. Now we don't log a bunch of complaints on startup
11070 when using the default exit policy.
11071 - Some people were putting "Address " in their torrc, and they had
11072 a buggy resolver that resolved " " to 0.0.0.0. Oops.
11073 - If DataDir is ~/.tor, and that expands to /.tor, then default to
11074 LOCALSTATEDIR/tor instead.
11075 - Fix fragmented-message bug in TorControl.py.
11076 - Resolve a minor bug which would prevent unreachable dirports
11077 from getting suppressed in the published descriptor.
11078 - When the controller gave us a new descriptor, we weren't resolving
11079 it immediately, so Tor would think its address was 0.0.0.0 until
11080 we fetched a new directory.
11081 - Fix an uppercase/lowercase case error in suppressing a bogus
11082 libevent warning on some Linuxes.
11085 - Begin scrubbing sensitive strings from logs by default. Turn off
11086 the config option SafeLogging if you need to do debugging.
11087 - Switch to a new buffer management algorithm, which tries to avoid
11088 reallocing and copying quite as much. In first tests it looks like
11089 it uses *more* memory on average, but less cpu.
11090 - First cut at support for "create-fast" cells. Clients can use
11091 these when extending to their first hop, since the TLS already
11092 provides forward secrecy and authentication. Not enabled on
11094 - When dirservers refuse a router descriptor, we now log its
11095 contactinfo, platform, and the poster's IP address.
11096 - Call tor_free_all instead of connections_free_all after forking, to
11097 save memory on systems that need to fork.
11098 - Whine at you if you're a server and you don't set your contactinfo.
11099 - Implement --verify-config command-line option to check if your torrc
11100 is valid without actually launching Tor.
11101 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
11102 rather than just rejecting it.
11105 Changes in version 0.1.0.5-rc - 2005-04-27
11107 - Stop trying to print a null pointer if an OR conn fails because
11108 we didn't like its cert.
11110 - Switch our internal buffers implementation to use a ring buffer,
11111 to hopefully improve performance for fast servers a lot.
11112 - Add HttpsProxyAuthenticator support (basic auth only), based
11113 on patch from Adam Langley.
11114 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
11115 the fast servers that have been joining lately.
11116 - Give hidden service accesses extra time on the first attempt,
11117 since 60 seconds is often only barely enough. This might improve
11119 - Improve performance for dirservers: stop re-parsing the whole
11120 directory every time you regenerate it.
11121 - Add more debugging info to help us find the weird dns freebsd
11122 pthreads bug; cleaner debug messages to help track future issues.
11125 Changes in version 0.0.9.9 - 2005-04-23
11126 o Bugfixes on 0.0.9.x:
11127 - If unofficial Tor clients connect and send weird TLS certs, our
11128 Tor server triggers an assert. This release contains a minimal
11129 backport from the broader fix that we put into 0.1.0.4-rc.
11132 Changes in version 0.1.0.4-rc - 2005-04-23
11134 - If unofficial Tor clients connect and send weird TLS certs, our
11135 Tor server triggers an assert. Stop asserting, and start handling
11136 TLS errors better in other situations too.
11137 - When the controller asks us to tell it about all the debug-level
11138 logs, it turns out we were generating debug-level logs while
11139 telling it about them, which turns into a bad loop. Now keep
11140 track of whether you're sending a debug log to the controller,
11141 and don't log when you are.
11142 - Fix the "postdescriptor" feature of the controller interface: on
11143 non-complete success, only say "done" once.
11145 - Clients are now willing to load balance over up to 2mB, not 1mB,
11146 of advertised bandwidth capacity.
11147 - Add a NoPublish config option, so you can be a server (e.g. for
11148 testing running Tor servers in other Tor networks) without
11149 publishing your descriptor to the primary dirservers.
11152 Changes in version 0.1.0.3-rc - 2005-04-08
11153 o Improvements on 0.1.0.2-rc:
11154 - Client now retries when streams end early for 'hibernating' or
11155 'resource limit' reasons, rather than failing them.
11156 - More automated handling for dirserver operators:
11157 - Automatically approve nodes running 0.1.0.2-rc or later,
11158 now that the the reachability detection stuff is working.
11159 - Now we allow two unverified servers with the same nickname
11160 but different keys. But if a nickname is verified, only that
11161 nickname+key are allowed.
11162 - If you're an authdirserver connecting to an address:port,
11163 and it's not the OR you were expecting, forget about that
11164 descriptor. If he *was* the one you were expecting, then forget
11165 about all other descriptors for that address:port.
11166 - Allow servers to publish descriptors from 12 hours in the future.
11167 Corollary: only whine about clock skew from the dirserver if
11168 he's a trusted dirserver (since now even verified servers could
11169 have quite wrong clocks).
11170 - Adjust maximum skew and age for rendezvous descriptors: let skew
11171 be 48 hours rather than 90 minutes.
11172 - Efficiency improvements:
11173 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
11174 it much faster to look up a circuit for each relay cell.
11175 - Remove most calls to assert_all_pending_dns_resolves_ok(),
11176 since they're eating our cpu on exit nodes.
11177 - Stop wasting time doing a case insensitive comparison for every
11178 dns name every time we do any lookup. Canonicalize the names to
11179 lowercase and be done with it.
11180 - Start sending 'truncated' cells back rather than destroy cells,
11181 if the circuit closes in front of you. This means we won't have
11182 to abandon partially built circuits.
11183 - Only warn once per nickname from add_nickname_list_to_smartlist
11184 per failure, so an entrynode or exitnode choice that's down won't
11186 - Put a note in the torrc about abuse potential with the default
11188 - Revise control spec and implementation to allow all log messages to
11189 be sent to controller with their severities intact (suggested by
11190 Matt Edman). Update TorControl to handle new log event types.
11191 - Provide better explanation messages when controller's POSTDESCRIPTOR
11193 - Stop putting nodename in the Platform string in server descriptors.
11194 It doesn't actually help, and it is confusing/upsetting some people.
11196 o Bugfixes on 0.1.0.2-rc:
11197 - We were printing the host mask wrong in exit policies in server
11198 descriptors. This isn't a critical bug though, since we were still
11199 obeying the exit policy internally.
11200 - Fix Tor when compiled with libevent but without pthreads: move
11201 connection_unregister() from _connection_free() to
11203 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
11204 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
11205 when we look through the connection array, we'll find any of the
11206 cpu/dnsworkers. This is no good.
11208 o Bugfixes on 0.0.9.8:
11209 - Fix possible bug on threading platforms (e.g. win32) which was
11210 leaking a file descriptor whenever a cpuworker or dnsworker died.
11211 - When using preferred entry or exit nodes, ignore whether the
11212 circuit wants uptime or capacity. They asked for the nodes, they
11214 - chdir() to your datadirectory at the *end* of the daemonize process,
11215 not the beginning. This was a problem because the first time you
11216 run tor, if your datadir isn't there, and you have runasdaemon set
11217 to 1, it will try to chdir to it before it tries to create it. Oops.
11218 - Handle changed router status correctly when dirserver reloads
11219 fingerprint file. We used to be dropping all unverified descriptors
11220 right then. The bug was hidden because we would immediately
11221 fetch a directory from another dirserver, which would include the
11222 descriptors we just dropped.
11223 - When we're connecting to an OR and he's got a different nickname/key
11224 than we were expecting, only complain loudly if we're an OP or a
11225 dirserver. Complaining loudly to the OR admins just confuses them.
11226 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
11227 artificially capped at 500kB.
11230 Changes in version 0.0.9.8 - 2005-04-07
11231 o Bugfixes on 0.0.9.x:
11232 - We have a bug that I haven't found yet. Sometimes, very rarely,
11233 cpuworkers get stuck in the 'busy' state, even though the cpuworker
11234 thinks of itself as idle. This meant that no new circuits ever got
11235 established. Here's a workaround to kill any cpuworker that's been
11236 busy for more than 100 seconds.
11239 Changes in version 0.1.0.2-rc - 2005-04-01
11240 o Bugfixes on 0.1.0.1-rc:
11241 - Fixes on reachability detection:
11242 - Don't check for reachability while hibernating.
11243 - If ORPort is reachable but DirPort isn't, still publish the
11244 descriptor, but zero out DirPort until it's found reachable.
11245 - When building testing circs for ORPort testing, use only
11246 high-bandwidth nodes, so fewer circuits fail.
11247 - Complain about unreachable ORPort separately from unreachable
11248 DirPort, so the user knows what's going on.
11249 - Make sure we only conclude ORPort reachability if we didn't
11250 initiate the conn. Otherwise we could falsely conclude that
11251 we're reachable just because we connected to the guy earlier
11252 and he used that same pipe to extend to us.
11253 - Authdirservers shouldn't do ORPort reachability detection,
11254 since they're in clique mode, so it will be rare to find a
11255 server not already connected to them.
11256 - When building testing circuits, always pick middle hops running
11257 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
11258 bug. (This is a kludge; it will go away when 0.0.9.x becomes
11260 - When we decide we're reachable, actually publish our descriptor
11262 - Fix bug in redirectstream in the controller.
11263 - Fix the state descriptor strings so logs don't claim edge streams
11264 are in a different state than they actually are.
11265 - Use recent libevent features when possible (this only really affects
11266 win32 and osx right now, because the new libevent with these
11267 features hasn't been released yet). Add code to suppress spurious
11269 - Prevent possible segfault in connection_close_unattached_ap().
11270 - Fix newlines on torrc in win32.
11271 - Improve error msgs when tor-resolve fails.
11273 o Improvements on 0.0.9.x:
11274 - New experimental script tor/contrib/ExerciseServer.py (needs more
11275 work) that uses the controller interface to build circuits and
11276 fetch pages over them. This will help us bootstrap servers that
11277 have lots of capacity but haven't noticed it yet.
11278 - New experimental script tor/contrib/PathDemo.py (needs more work)
11279 that uses the controller interface to let you choose whole paths
11281 "<hostname>.<path,separated by dots>.<length of path>.path"
11282 - When we've connected to an OR and handshaked but didn't like
11283 the result, we were closing the conn without sending destroy
11284 cells back for pending circuits. Now send those destroys.
11287 Changes in version 0.0.9.7 - 2005-04-01
11288 o Bugfixes on 0.0.9.x:
11289 - Fix another race crash bug (thanks to Glenn Fink for reporting).
11290 - Compare identity to identity, not to nickname, when extending to
11291 a router not already in the directory. This was preventing us from
11292 extending to unknown routers. Oops.
11293 - Make sure to create OS X Tor user in <500 range, so we aren't
11294 creating actual system users.
11295 - Note where connection-that-hasn't-sent-end was marked, and fix
11296 a few really loud instances of this harmless bug (it's fixed more
11300 Changes in version 0.1.0.1-rc - 2005-03-28
11302 - Add reachability testing. Your Tor server will automatically try
11303 to see if its ORPort and DirPort are reachable from the outside,
11304 and it won't upload its descriptor until it decides they are.
11305 - Handle unavailable hidden services better. Handle slow or busy
11306 hidden services better.
11307 - Add support for CONNECTing through https proxies, with "HttpsProxy"
11309 - New exit policy: accept most low-numbered ports, rather than
11310 rejecting most low-numbered ports.
11311 - More Tor controller support (still experimental). See
11312 http://tor.eff.org/doc/control-spec.txt for all the new features,
11313 including signals to emulate unix signals from any platform;
11314 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
11315 closestream; closecircuit; etc.
11316 - Make nt services work and start on startup on win32 (based on
11317 patch by Matt Edman).
11318 - Add a new AddressMap config directive to rewrite incoming socks
11319 addresses. This lets you, for example, declare an implicit
11320 required exit node for certain sites.
11321 - Add a new TrackHostExits config directive to trigger addressmaps
11322 for certain incoming socks addresses -- for sites that break when
11323 your exit keeps changing (based on patch by Mike Perry).
11324 - Redo the client-side dns cache so it's just an addressmap too.
11325 - Notice when our IP changes, and reset stats/uptime/reachability.
11326 - When an application is using socks5, give him the whole variety of
11327 potential socks5 responses (connect refused, host unreachable, etc),
11328 rather than just "success" or "failure".
11329 - A more sane version numbering system. See
11330 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
11331 - New contributed script "exitlist": a simple python script to
11332 parse directories and find Tor nodes that exit to listed
11334 - New contributed script "privoxy-tor-toggle" to toggle whether
11335 Privoxy uses Tor. Seems to be configured for Debian by default.
11336 - Report HTTP reasons to client when getting a response from directory
11337 servers -- so you can actually know what went wrong.
11338 - New config option MaxAdvertisedBandwidth which lets you advertise
11339 a low bandwidthrate (to not attract as many circuits) while still
11340 allowing a higher bandwidthrate in reality.
11342 o Robustness/stability fixes:
11343 - Make Tor use Niels Provos's libevent instead of its current
11344 poll-but-sometimes-select mess. This will let us use faster async
11345 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
11347 - pthread support now too. This was forced because when we forked,
11348 we ended up wasting a lot of duplicate ram over time. Also switch
11349 to foo_r versions of some library calls to allow reentry and
11351 - Better handling for heterogeneous / unreliable nodes:
11352 - Annotate circuits w/ whether they aim to contain high uptime nodes
11353 and/or high capacity nodes. When building circuits, choose
11355 - This means that every single node in an intro rend circuit,
11356 not just the last one, will have a minimum uptime.
11357 - New config option LongLivedPorts to indicate application streams
11358 that will want high uptime circuits.
11359 - Servers reset uptime when a dir fetch entirely fails. This
11360 hopefully reflects stability of the server's network connectivity.
11361 - If somebody starts his tor server in Jan 2004 and then fixes his
11362 clock, don't make his published uptime be a year.
11363 - Reset published uptime when you wake up from hibernation.
11364 - Introduce a notion of 'internal' circs, which are chosen without
11365 regard to the exit policy of the last hop. Intro and rendezvous
11366 circs must be internal circs, to avoid leaking information. Resolve
11367 and connect streams can use internal circs if they want.
11368 - New circuit pooling algorithm: make sure to have enough circs around
11369 to satisfy any predicted ports, and also make sure to have 2 internal
11370 circs around if we've required internal circs lately (and with high
11371 uptime if we've seen that lately too).
11372 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
11373 which describes how often we retry making new circuits if current
11374 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
11375 how long we're willing to make use of an already-dirty circuit.
11376 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
11377 circ as necessary, if there are any completed ones lying around
11378 when we try to launch one.
11379 - Make hidden services try to establish a rendezvous for 30 seconds,
11380 rather than for n (where n=3) attempts to build a circuit.
11381 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
11382 "ShutdownWaitLength".
11383 - Try to be more zealous about calling connection_edge_end when
11384 things go bad with edge conns in connection.c.
11385 - Revise tor-spec to add more/better stream end reasons.
11386 - Revise all calls to connection_edge_end to avoid sending "misc",
11387 and to take errno into account where possible.
11390 - Fix a race condition that can trigger an assert, when we have a
11391 pending create cell and an OR connection fails right then.
11392 - Fix several double-mark-for-close bugs, e.g. where we were finding
11393 a conn for a cell even if that conn is already marked for close.
11394 - Make sequence of log messages when starting on win32 with no config
11395 file more reasonable.
11396 - When choosing an exit node for a new non-internal circ, don't take
11397 into account whether it'll be useful for any pending x.onion
11398 addresses -- it won't.
11399 - Turn addr_policy_compare from a tristate to a quadstate; this should
11400 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
11401 for google.com" problem.
11402 - Make "platform" string in descriptor more accurate for Win32 servers,
11403 so it's not just "unknown platform".
11404 - Fix an edge case in parsing config options (thanks weasel).
11405 If they say "--" on the commandline, it's not an option.
11406 - Reject odd-looking addresses at the client (e.g. addresses that
11407 contain a colon), rather than having the server drop them because
11409 - tor-resolve requests were ignoring .exit if there was a working circuit
11410 they could use instead.
11411 - REUSEADDR on normal platforms means you can rebind to the port
11412 right after somebody else has let it go. But REUSEADDR on win32
11413 means to let you bind to the port _even when somebody else
11414 already has it bound_! So, don't do that on Win32.
11415 - Change version parsing logic: a version is "obsolete" if it is not
11416 recommended and (1) there is a newer recommended version in the
11417 same series, or (2) there are no recommended versions in the same
11418 series, but there are some recommended versions in a newer series.
11419 A version is "new" if it is newer than any recommended version in
11421 - Stop most cases of hanging up on a socks connection without sending
11425 - Require BandwidthRate to be at least 20kB/s for servers.
11426 - When a dirserver causes you to give a warn, mention which dirserver
11428 - New config option DirAllowPrivateAddresses for authdirservers.
11429 Now by default they refuse router descriptors that have non-IP or
11430 private-IP addresses.
11431 - Stop publishing socksport in the directory, since it's not
11432 actually meant to be public. For compatibility, publish a 0 there
11434 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
11435 smart" value, that is low for servers and high for clients.
11436 - If our clock jumps forward by 100 seconds or more, assume something
11437 has gone wrong with our network and abandon all not-yet-used circs.
11438 - Warn when exit policy implicitly allows local addresses.
11439 - If we get an incredibly skewed timestamp from a dirserver mirror
11440 that isn't a verified OR, don't warn -- it's probably him that's
11442 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
11443 cookies to disk and doesn't log each web request to disk. (Thanks
11444 to Brett Carrington for pointing this out.)
11445 - When a client asks us for a dir mirror and we don't have one,
11446 launch an attempt to get a fresh one.
11447 - If we're hibernating and we get a SIGINT, exit immediately.
11448 - Add --with-dmalloc ./configure option, to track memory leaks.
11449 - And try to free all memory on closing, so we can detect what
11451 - Cache local dns resolves correctly even when they're .exit
11453 - Give a better warning when some other server advertises an
11454 ORPort that is actually an apache running ssl.
11455 - Add "opt hibernating 1" to server descriptor to make it clearer
11456 whether the server is hibernating.
11459 Changes in version 0.0.9.6 - 2005-03-24
11460 o Bugfixes on 0.0.9.x (crashes and asserts):
11461 - Add new end stream reasons to maintainance branch. Fix bug where
11462 reason (8) could trigger an assert. Prevent bug from recurring.
11463 - Apparently win32 stat wants paths to not end with a slash.
11464 - Fix assert triggers in assert_cpath_layer_ok(), where we were
11465 blowing away the circuit that conn->cpath_layer points to, then
11466 checking to see if the circ is well-formed. Backport check to make
11467 sure we dont use the cpath on a closed connection.
11468 - Prevent circuit_resume_edge_reading_helper() from trying to package
11469 inbufs for marked-for-close streams.
11470 - Don't crash on hup if your options->address has become unresolvable.
11471 - Some systems (like OS X) sometimes accept() a connection and tell
11472 you the remote host is 0.0.0.0:0. If this happens, due to some
11473 other mis-features, we get confused; so refuse the conn for now.
11475 o Bugfixes on 0.0.9.x (other):
11476 - Fix harmless but scary "Unrecognized content encoding" warn message.
11477 - Add new stream error reason: TORPROTOCOL reason means "you are not
11478 speaking a version of Tor I understand; say bye-bye to your stream."
11479 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
11480 into the future, now that we are more tolerant of skew. This
11481 resolves a bug where a Tor server would refuse to cache a directory
11482 because all the directories it gets are too far in the future;
11483 yet the Tor server never logs any complaints about clock skew.
11484 - Mac packaging magic: make man pages useable, and do not overwrite
11485 existing torrc files.
11486 - Make OS X log happily to /var/log/tor/tor.log
11489 Changes in version 0.0.9.5 - 2005-02-22
11490 o Bugfixes on 0.0.9.x:
11491 - Fix an assert race at exit nodes when resolve requests fail.
11492 - Stop picking unverified dir mirrors--it only leads to misery.
11493 - Patch from Matt Edman to make NT services work better. Service
11494 support is still not compiled into the executable by default.
11495 - Patch from Dmitri Bely so the Tor service runs better under
11496 the win32 SYSTEM account.
11497 - Make tor-resolve actually work (?) on Win32.
11498 - Fix a sign bug when getrlimit claims to have 4+ billion
11499 file descriptors available.
11500 - Stop refusing to start when bandwidthburst == bandwidthrate.
11501 - When create cells have been on the onion queue more than five
11502 seconds, just send back a destroy and take them off the list.
11505 Changes in version 0.0.9.4 - 2005-02-03
11506 o Bugfixes on 0.0.9:
11507 - Fix an assert bug that took down most of our servers: when
11508 a server claims to have 1 GB of bandwidthburst, don't
11510 - Don't crash as badly if we have spawned the max allowed number
11511 of dnsworkers, or we're out of file descriptors.
11512 - Block more file-sharing ports in the default exit policy.
11513 - MaxConn is now automatically set to the hard limit of max
11514 file descriptors we're allowed (ulimit -n), minus a few for
11516 - Give a clearer message when servers need to raise their
11517 ulimit -n when they start running out of file descriptors.
11518 - SGI Compatibility patches from Jan Schaumann.
11519 - Tolerate a corrupt cached directory better.
11520 - When a dirserver hasn't approved your server, list which one.
11521 - Go into soft hibernation after 95% of the bandwidth is used,
11522 not 99%. This is especially important for daily hibernators who
11523 have a small accounting max. Hopefully it will result in fewer
11524 cut connections when the hard hibernation starts.
11525 - Load-balance better when using servers that claim more than
11526 800kB/s of capacity.
11527 - Make NT services work (experimental, only used if compiled in).
11530 Changes in version 0.0.9.3 - 2005-01-21
11531 o Bugfixes on 0.0.9:
11532 - Backport the cpu use fixes from main branch, so busy servers won't
11533 need as much processor time.
11534 - Work better when we go offline and then come back, or when we
11535 run Tor at boot before the network is up. We do this by
11536 optimistically trying to fetch a new directory whenever an
11537 application request comes in and we think we're offline -- the
11538 human is hopefully a good measure of when the network is back.
11539 - Backport some minimal hidserv bugfixes: keep rend circuits open as
11540 long as you keep using them; actually publish hidserv descriptors
11541 shortly after they change, rather than waiting 20-40 minutes.
11542 - Enable Mac startup script by default.
11543 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
11544 - When you update AllowUnverifiedNodes or FirewallPorts via the
11545 controller's setconf feature, we were always appending, never
11547 - When you update HiddenServiceDir via setconf, it was screwing up
11548 the order of reading the lines, making it fail.
11549 - Do not rewrite a cached directory back to the cache; otherwise we
11550 will think it is recent and not fetch a newer one on startup.
11551 - Workaround for webservers that lie about Content-Encoding: Tor
11552 now tries to autodetect compressed directories and compression
11553 itself. This lets us Proxypass dir fetches through apache.
11556 Changes in version 0.0.9.2 - 2005-01-04
11557 o Bugfixes on 0.0.9 (crashes and asserts):
11558 - Fix an assert on startup when the disk is full and you're logging
11560 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
11561 style address, then we'd crash.
11562 - Fix an assert trigger when the running-routers string we get from
11563 a dirserver is broken.
11564 - Make worker threads start and run on win32. Now win32 servers
11566 - Bandaid (not actually fix, but now it doesn't crash) an assert
11567 where the dns worker dies mysteriously and the main Tor process
11568 doesn't remember anything about the address it was resolving.
11570 o Bugfixes on 0.0.9 (Win32):
11571 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
11572 name out of the warning/assert messages.
11573 - Fix a superficial "unhandled error on read" bug on win32.
11574 - The win32 installer no longer requires a click-through for our
11575 license, since our Free Software license grants rights but does not
11577 - Win32: When connecting to a dirserver fails, try another one
11578 immediately. (This was already working for non-win32 Tors.)
11579 - Stop trying to parse $HOME on win32 when hunting for default
11581 - Make tor-resolve.c work on win32 by calling network_init().
11583 o Bugfixes on 0.0.9 (other):
11584 - Make 0.0.9.x build on Solaris again.
11585 - Due to a fencepost error, we were blowing away the \n when reporting
11586 confvalue items in the controller. So asking for multiple config
11587 values at once couldn't work.
11588 - When listing circuits that are pending on an opening OR connection,
11589 if we're an OR we were listing circuits that *end* at us as
11590 being pending on every listener, dns/cpu worker, etc. Stop that.
11591 - Dirservers were failing to create 'running-routers' or 'directory'
11592 strings if we had more than some threshold of routers. Fix them so
11593 they can handle any number of routers.
11594 - Fix a superficial "Duplicate mark for close" bug.
11595 - Stop checking for clock skew for OR connections, even for servers.
11596 - Fix a fencepost error that was chopping off the last letter of any
11597 nickname that is the maximum allowed nickname length.
11598 - Update URLs in log messages so they point to the new website.
11599 - Fix a potential problem in mangling server private keys while
11600 writing to disk (not triggered yet, as far as we know).
11601 - Include the licenses for other free software we include in Tor,
11602 now that we're shipping binary distributions more regularly.
11605 Changes in version 0.0.9.1 - 2004-12-15
11606 o Bugfixes on 0.0.9:
11607 - Make hibernation actually work.
11608 - Make HashedControlPassword config option work.
11609 - When we're reporting event circuit status to a controller,
11610 don't use the stream status code.
11613 Changes in version 0.0.9 - 2004-12-12
11615 - Clean up manpage and torrc.sample file.
11616 - Clean up severities and text of log warnings.
11618 - Make servers trigger an assert when they enter hibernation.
11621 Changes in version 0.0.9rc7 - 2004-12-08
11622 o Bugfixes on 0.0.9rc:
11623 - Fix a stack-trashing crash when an exit node begins hibernating.
11624 - Avoid looking at unallocated memory while considering which
11625 ports we need to build circuits to cover.
11626 - Stop a sigpipe: when an 'end' cell races with eof from the app,
11627 we shouldn't hold-open-until-flush if the eof arrived first.
11628 - Fix a bug with init_cookie_authentication() in the controller.
11629 - When recommending new-format log lines, if the upper bound is
11630 LOG_ERR, leave it implicit.
11632 o Bugfixes on 0.0.8.1:
11633 - Fix a whole slew of memory leaks.
11634 - Fix isspace() and friends so they still make Solaris happy
11635 but also so they don't trigger asserts on win32.
11636 - Fix parse_iso_time on platforms without strptime (eg win32).
11637 - win32: tolerate extra "readable" events better.
11638 - win32: when being multithreaded, leave parent fdarray open.
11639 - Make unit tests work on win32.
11642 Changes in version 0.0.9rc6 - 2004-12-06
11643 o Bugfixes on 0.0.9pre:
11644 - Clean up some more integer underflow opportunities (not exploitable
11646 - While hibernating, hup should not regrow our listeners.
11647 - Send an end to the streams we close when we hibernate, rather
11648 than just chopping them off.
11649 - React to eof immediately on non-open edge connections.
11651 o Bugfixes on 0.0.8.1:
11652 - Calculate timeout for waiting for a connected cell from the time
11653 we sent the begin cell, not from the time the stream started. If
11654 it took a long time to establish the circuit, we would time out
11655 right after sending the begin cell.
11656 - Fix router_compare_addr_to_addr_policy: it was not treating a port
11657 of * as always matching, so we were picking reject *:* nodes as
11658 exit nodes too. Oops.
11661 - New circuit building strategy: keep a list of ports that we've
11662 used in the past 6 hours, and always try to have 2 circuits open
11663 or on the way that will handle each such port. Seed us with port
11664 80 so web users won't complain that Tor is "slow to start up".
11665 - Make kill -USR1 dump more useful stats about circuits.
11666 - When warning about retrying or giving up, print the address, so
11667 the user knows which one it's talking about.
11668 - If you haven't used a clean circuit in an hour, throw it away,
11669 just to be on the safe side. (This means after 6 hours a totally
11670 unused Tor client will have no circuits open.)
11673 Changes in version 0.0.9rc5 - 2004-12-01
11674 o Bugfixes on 0.0.8.1:
11675 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
11676 - Let resolve conns retry/expire also, rather than sticking around
11678 - If we are using select, make sure we stay within FD_SETSIZE.
11680 o Bugfixes on 0.0.9pre:
11681 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
11682 but doesn't seem to be currently; thanks to Ilja van Sprundel for
11684 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
11685 instead. Impose minima and maxima for all *Period options; impose
11686 even tighter maxima for fetching if we are a caching dirserver.
11687 Clip rather than rejecting.
11688 - Fetch cached running-routers from servers that serve it (that is,
11689 authdirservers and servers running 0.0.9rc5-cvs or later.)
11692 - Accept *:706 (silc) in default exit policy.
11693 - Implement new versioning format for post 0.1.
11694 - Support "foo.nickname.exit" addresses, to let Alice request the
11695 address "foo" as viewed by exit node "nickname". Based on a patch
11697 - Make tor --version --version dump the cvs Id of every file.
11700 Changes in version 0.0.9rc4 - 2004-11-28
11701 o Bugfixes on 0.0.8.1:
11702 - Make windows sockets actually non-blocking (oops), and handle
11703 win32 socket errors better.
11705 o Bugfixes on 0.0.9rc1:
11706 - Actually catch the -USR2 signal.
11709 Changes in version 0.0.9rc3 - 2004-11-25
11710 o Bugfixes on 0.0.8.1:
11711 - Flush the log file descriptor after we print "Tor opening log file",
11712 so we don't see those messages days later.
11714 o Bugfixes on 0.0.9rc1:
11715 - Make tor-resolve work again.
11716 - Avoid infinite loop in tor-resolve if tor hangs up on it.
11717 - Fix an assert trigger for clients/servers handling resolves.
11720 Changes in version 0.0.9rc2 - 2004-11-24
11721 o Bugfixes on 0.0.9rc1:
11722 - I broke socks5 support while fixing the eof bug.
11723 - Allow unitless bandwidths and intervals; they default to bytes
11725 - New servers don't start out hibernating; they are active until
11726 they run out of bytes, so they have a better estimate of how
11727 long it takes, and so their operators can know they're working.
11730 Changes in version 0.0.9rc1 - 2004-11-23
11731 o Bugfixes on 0.0.8.1:
11732 - Finally fix a bug that's been plaguing us for a year:
11733 With high load, circuit package window was reaching 0. Whenever
11734 we got a circuit-level sendme, we were reading a lot on each
11735 socket, but only writing out a bit. So we would eventually reach
11736 eof. This would be noticed and acted on even when there were still
11737 bytes sitting in the inbuf.
11738 - When poll() is interrupted, we shouldn't believe the revents values.
11740 o Bugfixes on 0.0.9pre6:
11741 - Fix hibernate bug that caused pre6 to be broken.
11742 - Don't keep rephist info for routers that haven't had activity for
11743 24 hours. (This matters now that clients have keys, since we track
11745 - Never call close_temp_logs while validating log options.
11746 - Fix backslash-escaping on tor.sh.in and torctl.in.
11749 - Implement weekly/monthly/daily accounting: now you specify your
11750 hibernation properties by
11751 AccountingMax N bytes|KB|MB|GB|TB
11752 AccountingStart day|week|month [day] HH:MM
11753 Defaults to "month 1 0:00".
11754 - Let bandwidth and interval config options be specified as 5 bytes,
11755 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
11756 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
11757 get back to normal.)
11758 - If your requested entry or exit node has advertised bandwidth 0,
11760 - Be more greedy about filling up relay cells -- we try reading again
11761 once we've processed the stuff we read, in case enough has arrived
11762 to fill the last cell completely.
11763 - Apply NT service patch from Osamu Fujino. Still needs more work.
11766 Changes in version 0.0.9pre6 - 2004-11-15
11767 o Bugfixes on 0.0.8.1:
11768 - Fix assert failure on malformed socks4a requests.
11769 - Use identity comparison, not nickname comparison, to choose which
11770 half of circuit-ID-space each side gets to use. This is needed
11771 because sometimes we think of a router as a nickname, and sometimes
11772 as a hex ID, and we can't predict what the other side will do.
11773 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
11774 write() call will fail and we handle it there.
11775 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
11776 and smartlist_len, which are two major profiling offenders.
11778 o Bugfixes on 0.0.9pre5:
11779 - Fix a bug in read_all that was corrupting config files on windows.
11780 - When we're raising the max number of open file descriptors to
11781 'unlimited', don't log that we just raised it to '-1'.
11782 - Include event code with events, as required by control-spec.txt.
11783 - Don't give a fingerprint when clients do --list-fingerprint:
11784 it's misleading, because it will never be the same again.
11785 - Stop using strlcpy in tor_strndup, since it was slowing us
11787 - Remove warn on startup about missing cached-directory file.
11788 - Make kill -USR1 work again.
11789 - Hibernate if we start tor during the "wait for wakeup-time" phase
11790 of an accounting interval. Log our hibernation plans better.
11791 - Authoritative dirservers now also cache their directory, so they
11792 have it on start-up.
11795 - Fetch running-routers; cache running-routers; compress
11796 running-routers; serve compressed running-routers.z
11797 - Add NSI installer script contributed by J Doe.
11798 - Commit VC6 and VC7 workspace/project files.
11799 - Commit a tor.spec for making RPM files, with help from jbash.
11800 - Add contrib/torctl.in contributed by Glenn Fink.
11801 - Implement the control-spec's SAVECONF command, to write your
11802 configuration to torrc.
11803 - Get cookie authentication for the controller closer to working.
11804 - Include control-spec.txt in the tarball.
11805 - When set_conf changes our server descriptor, upload a new copy.
11806 But don't upload it too often if there are frequent changes.
11807 - Document authentication config in man page, and document signals
11809 - Clean up confusing parts of man page and torrc.sample.
11810 - Make expand_filename handle ~ and ~username.
11811 - Use autoconf to enable largefile support where necessary. Use
11812 ftello where available, since ftell can fail at 2GB.
11813 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
11814 log more informatively.
11815 - Give a slightly more useful output for "tor -h".
11816 - Refuse application socks connections to port 0.
11817 - Check clock skew for verified servers, but allow unverified
11818 servers and clients to have any clock skew.
11819 - Break DirFetchPostPeriod into:
11820 - DirFetchPeriod for fetching full directory,
11821 - StatusFetchPeriod for fetching running-routers,
11822 - DirPostPeriod for posting server descriptor,
11823 - RendPostPeriod for posting hidden service descriptors.
11824 - Make sure the hidden service descriptors are at a random offset
11825 from each other, to hinder linkability.
11828 Changes in version 0.0.9pre5 - 2004-11-09
11829 o Bugfixes on 0.0.9pre4:
11830 - Fix a seg fault in unit tests (doesn't affect main program).
11831 - Fix an assert bug where a hidden service provider would fail if
11832 the first hop of his rendezvous circuit was down.
11833 - Hidden service operators now correctly handle version 1 style
11834 INTRODUCE1 cells (nobody generates them still, so not a critical
11836 - If do_hup fails, actually notice.
11837 - Handle more errnos from accept() without closing the listener.
11838 Some OpenBSD machines were closing their listeners because
11839 they ran out of file descriptors.
11840 - Send resolve cells to exit routers that are running a new
11841 enough version of the resolve code to work right.
11842 - Better handling of winsock includes on non-MSV win32 compilers.
11843 - Some people had wrapped their tor client/server in a script
11844 that would restart it whenever it died. This did not play well
11845 with our "shut down if your version is obsolete" code. Now people
11846 don't fetch a new directory if their local cached version is
11848 - Make our autogen.sh work on ksh as well as bash.
11851 - Hibernation: New config option "AccountingMaxKB" lets you
11852 set how many KBytes per month you want to allow your server to
11853 consume. Rather than spreading those bytes out evenly over the
11854 month, we instead hibernate for some of the month and pop up
11855 at a deterministic time, work until the bytes are consumed, then
11856 hibernate again. Config option "MonthlyAccountingStart" lets you
11857 specify which day of the month your billing cycle starts on.
11858 - Control interface: a separate program can now talk to your
11859 client/server over a socket, and get/set config options, receive
11860 notifications of circuits and streams starting/finishing/dying,
11861 bandwidth used, etc. The next step is to get some GUIs working.
11862 Let us know if you want to help out. See doc/control-spec.txt .
11863 - Ship a contrib/tor-control.py as an example script to interact
11864 with the control port.
11865 - "tor --hash-password zzyxz" will output a salted password for
11866 use in authenticating to the control interface.
11867 - New log format in config:
11868 "Log minsev[-maxsev] stdout|stderr|syslog" or
11869 "Log minsev[-maxsev] file /var/foo"
11872 - DirPolicy config option, to let people reject incoming addresses
11873 from their dirserver.
11874 - "tor --list-fingerprint" will list your identity key fingerprint
11876 - Add "pass" target for RedirectExit, to make it easier to break
11877 out of a sequence of RedirectExit rules.
11878 - Clients now generate a TLS cert too, in preparation for having
11879 them act more like real nodes.
11880 - Ship src/win32/ in the tarball, so people can use it to build.
11881 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
11883 - New "router-status" line in directory, to better bind each verified
11884 nickname to its identity key.
11885 - Deprecate unofficial config option abbreviations, and abbreviations
11886 not on the command line.
11887 - Add a pure-C tor-resolve implementation.
11888 - Use getrlimit and friends to ensure we can reach MaxConn (currently
11889 1024) file descriptors.
11891 o Code security improvements, inspired by Ilja:
11892 - Replace sprintf with snprintf. (I think they were all safe, but
11894 - Replace strcpy/strncpy with strlcpy in more places.
11895 - Avoid strcat; use snprintf or strlcat instead.
11896 - snprintf wrapper with consistent (though not C99) overflow behavior.
11899 Changes in version 0.0.9pre4 - 2004-10-17
11900 o Bugfixes on 0.0.9pre3:
11901 - If the server doesn't specify an exit policy, use the real default
11902 exit policy, not reject *:*.
11903 - Ignore fascistfirewall when uploading/downloading hidden service
11904 descriptors, since we go through Tor for those; and when using
11905 an HttpProxy, since we assume it can reach them all.
11906 - When looking for an authoritative dirserver, use only the ones
11907 configured at boot. Don't bother looking in the directory.
11908 - The rest of the fix for get_default_conf_file() on older win32.
11909 - Make 'Routerfile' config option obsolete.
11912 - New 'MyFamily nick1,...' config option for a server to
11913 specify other servers that shouldn't be used in the same circuit
11914 with it. Only believed if nick1 also specifies us.
11915 - New 'NodeFamily nick1,nick2,...' config option for a client to
11916 specify nodes that it doesn't want to use in the same circuit.
11917 - New 'Redirectexit pattern address:port' config option for a
11918 server to redirect exit connections, e.g. to a local squid.
11921 Changes in version 0.0.9pre3 - 2004-10-13
11922 o Bugfixes on 0.0.8.1:
11923 - Better torrc example lines for dirbindaddress and orbindaddress.
11924 - Improved bounds checking on parsed ints (e.g. config options and
11925 the ones we find in directories.)
11926 - Better handling of size_t vs int, so we're more robust on 64
11928 - Fix the rest of the bug where a newly started OR would appear
11929 as unverified even after we've added his fingerprint and hupped
11931 - Fix a bug from 0.0.7: when read() failed on a stream, we would
11932 close it without sending back an end. So 'connection refused'
11933 would simply be ignored and the user would get no response.
11935 o Bugfixes on 0.0.9pre2:
11936 - Serving the cached-on-disk directory to people is bad. We now
11937 provide no directory until we've fetched a fresh one.
11938 - Workaround for bug on windows where cached-directories get crlf
11940 - Make get_default_conf_file() work on older windows too.
11941 - If we write a *:* exit policy line in the descriptor, don't write
11942 any more exit policy lines.
11945 - Use only 0.0.9pre1 and later servers for resolve cells.
11946 - Make the dirservers file obsolete.
11947 - Include a dir-signing-key token in directories to tell the
11948 parsing entity which key is being used to sign.
11949 - Remove the built-in bulky default dirservers string.
11950 - New config option "Dirserver %s:%d [fingerprint]", which can be
11951 repeated as many times as needed. If no dirservers specified,
11952 default to moria1,moria2,tor26.
11953 - Make moria2 advertise a dirport of 80, so people behind firewalls
11954 will be able to get a directory.
11955 - Http proxy support
11956 - Dirservers translate requests for http://%s:%d/x to /x
11957 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
11958 be routed through this host.
11959 - Clients ask for /tor/x rather than /x for new enough dirservers.
11960 This way we can one day coexist peacefully with apache.
11961 - Clients specify a "Host: %s%d" http header, to be compatible
11962 with more proxies, and so running squid on an exit node can work.
11965 Changes in version 0.0.8.1 - 2004-10-13
11967 - Fix a seg fault that can be triggered remotely for Tor
11968 clients/servers with an open dirport.
11969 - Fix a rare assert trigger, where routerinfos for entries in
11970 our cpath would expire while we're building the path.
11971 - Fix a bug in OutboundBindAddress so it (hopefully) works.
11972 - Fix a rare seg fault for people running hidden services on
11973 intermittent connections.
11974 - Fix a bug in parsing opt keywords with objects.
11975 - Fix a stale pointer assert bug when a stream detaches and
11977 - Fix a string format vulnerability (probably not exploitable)
11978 in reporting stats locally.
11979 - Fix an assert trigger: sometimes launching circuits can fail
11980 immediately, e.g. because too many circuits have failed recently.
11981 - Fix a compile warning on 64 bit platforms.
11984 Changes in version 0.0.9pre2 - 2004-10-03
11986 - Make fetching a cached directory work for 64-bit platforms too.
11987 - Make zlib.h a required header, not an optional header.
11990 Changes in version 0.0.9pre1 - 2004-10-01
11992 - Stop using separate defaults for no-config-file and
11993 empty-config-file. Now you have to explicitly turn off SocksPort,
11994 if you don't want it open.
11995 - Fix a bug in OutboundBindAddress so it (hopefully) works.
11996 - Improve man page to mention more of the 0.0.8 features.
11997 - Fix a rare seg fault for people running hidden services on
11998 intermittent connections.
11999 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
12001 - Fix more dns related bugs: send back resolve_failed and end cells
12002 more reliably when the resolve fails, rather than closing the
12003 circuit and then trying to send the cell. Also attach dummy resolve
12004 connections to a circuit *before* calling dns_resolve(), to fix
12005 a bug where cached answers would never be sent in RESOLVED cells.
12006 - When we run out of disk space, or other log writing error, don't
12007 crash. Just stop logging to that log and continue.
12008 - We were starting to daemonize before we opened our logs, so if
12009 there were any problems opening logs, we would complain to stderr,
12010 which wouldn't work, and then mysteriously exit.
12011 - Fix a rare bug where sometimes a verified OR would connect to us
12012 before he'd uploaded his descriptor, which would cause us to
12013 assign conn->nickname as though he's unverified. Now we look through
12014 the fingerprint list to see if he's there.
12015 - Fix a rare assert trigger, where routerinfos for entries in
12016 our cpath would expire while we're building the path.
12019 - Clients can ask dirservers for /dir.z to get a compressed version
12020 of the directory. Only works for servers running 0.0.9, of course.
12021 - Make clients cache directories and use them to seed their router
12022 lists at startup. This means clients have a datadir again.
12023 - Configuration infrastructure support for warning on obsolete
12025 - Respond to content-encoding headers by trying to uncompress as
12027 - Reply with a deflated directory when a client asks for "dir.z".
12028 We could use allow-encodings instead, but allow-encodings isn't
12029 specified in HTTP 1.0.
12030 - Raise the max dns workers from 50 to 100.
12031 - Discourage people from setting their dirfetchpostperiod more often
12032 than once per minute.
12033 - Protect dirservers from overzealous descriptor uploading -- wait
12034 10 seconds after directory gets dirty, before regenerating.
12037 Changes in version 0.0.8 - 2004-08-25
12038 o Port it to SunOS 5.9 / Athena
12041 Changes in version 0.0.8rc2 - 2004-08-20
12042 o Make it compile on cygwin again.
12043 o When picking unverified routers, skip those with low uptime and/or
12044 low bandwidth, depending on what properties you care about.
12047 Changes in version 0.0.8rc1 - 2004-08-18
12048 o Changes from 0.0.7.3:
12050 - Fix assert triggers: if the other side returns an address 0.0.0.0,
12051 don't put it into the client dns cache.
12052 - If a begin failed due to exit policy, but we believe the IP address
12053 should have been allowed, switch that router to exitpolicy reject *:*
12054 until we get our next directory.
12056 - Clients choose nodes proportional to advertised bandwidth.
12057 - Avoid using nodes with low uptime as introduction points.
12058 - Handle servers with dynamic IP addresses: don't replace
12059 options->Address with the resolved one at startup, and
12060 detect our address right before we make a routerinfo each time.
12061 - 'FascistFirewall' option to pick dirservers and ORs on specific
12062 ports; plus 'FirewallPorts' config option to tell FascistFirewall
12063 which ports are open. (Defaults to 80,443)
12064 - Be more aggressive about trying to make circuits when the network
12065 has changed (e.g. when you unsuspend your laptop).
12066 - Check for time skew on http headers; report date in response to
12068 - If the entrynode config line has only one node, don't pick it as
12070 - Add strict{entry|exit}nodes config options. If set to 1, then
12071 we refuse to build circuits that don't include the specified entry
12073 - OutboundBindAddress config option, to bind to a specific
12074 IP address for outgoing connect()s.
12075 - End truncated log entries (e.g. directories) with "[truncated]".
12077 o Patches to 0.0.8preX:
12079 - Patches to compile and run on win32 again (maybe)?
12080 - Fix crash when looking for ~/.torrc with no $HOME set.
12081 - Fix a race bug in the unit tests.
12082 - Handle verified/unverified name collisions better when new
12083 routerinfo's arrive in a directory.
12084 - Sometimes routers were getting entered into the stats before
12085 we'd assigned their identity_digest. Oops.
12086 - Only pick and establish intro points after we've gotten a
12089 - AllowUnverifiedNodes config option to let circuits choose no-name
12090 routers in entry,middle,exit,introduction,rendezvous positions.
12091 Allow middle and rendezvous positions by default.
12092 - Add a man page for tor-resolve.
12095 Changes in version 0.0.7.3 - 2004-08-12
12096 o Stop dnsworkers from triggering an assert failure when you
12097 ask them to resolve the host "".
12100 Changes in version 0.0.8pre3 - 2004-08-09
12101 o Changes from 0.0.7.2:
12102 - Allow multiple ORs with same nickname in routerlist -- now when
12103 people give us one identity key for a nickname, then later
12104 another, we don't constantly complain until the first expires.
12105 - Remember used bandwidth (both in and out), and publish 15-minute
12106 snapshots for the past day into our descriptor.
12107 - You can now fetch $DIRURL/running-routers to get just the
12108 running-routers line, not the whole descriptor list. (But
12109 clients don't use this yet.)
12110 - When people mistakenly use Tor as an http proxy, point them
12111 at the tor-doc.html rather than the INSTALL.
12112 - Remove our mostly unused -- and broken -- hex_encode()
12113 function. Use base16_encode() instead. (Thanks to Timo Lindfors
12114 for pointing out this bug.)
12115 - Rotate onion keys every 12 hours, not every 2 hours, so we have
12116 fewer problems with people using the wrong key.
12117 - Change the default exit policy to reject the default edonkey,
12118 kazaa, gnutella ports.
12119 - Add replace_file() to util.[ch] to handle win32's rename().
12121 o Changes from 0.0.8preX:
12122 - Fix two bugs in saving onion keys to disk when rotating, so
12123 hopefully we'll get fewer people using old onion keys.
12124 - Fix an assert error that was making SocksPolicy not work.
12125 - Be willing to expire routers that have an open dirport -- it's
12126 just the authoritative dirservers we want to not forget.
12127 - Reject tor-resolve requests for .onion addresses early, so we
12128 don't build a whole rendezvous circuit and then fail.
12129 - When you're warning a server that he's unverified, don't cry
12130 wolf unpredictably.
12131 - Fix a race condition: don't try to extend onto a connection
12132 that's still handshaking.
12133 - For servers in clique mode, require the conn to be open before
12134 you'll choose it for your path.
12135 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
12136 end relay cell, etc.
12137 - Measure bandwidth capacity over the last 24 hours, not just 12
12138 - Bugfix: authoritative dirservers were making and signing a new
12139 directory for each client, rather than reusing the cached one.
12142 Changes in version 0.0.8pre2 - 2004-08-04
12143 o Changes from 0.0.7.2:
12145 - Check directory signature _before_ you decide whether you're
12146 you're running an obsolete version and should exit.
12147 - Check directory signature _before_ you parse the running-routers
12148 list to decide who's running or verified.
12149 - Bugfixes and features:
12150 - Check return value of fclose while writing to disk, so we don't
12151 end up with broken files when servers run out of disk space.
12152 - Log a warning if the user uses an unsafe socks variant, so people
12153 are more likely to learn about privoxy or socat.
12154 - Dirservers now include RFC1123-style dates in the HTTP headers,
12155 which one day we will use to better detect clock skew.
12157 o Changes from 0.0.8pre1:
12158 - Make it compile without warnings again on win32.
12159 - Log a warning if you're running an unverified server, to let you
12160 know you might want to get it verified.
12161 - Only pick a default nickname if you plan to be a server.
12164 Changes in version 0.0.8pre1 - 2004-07-23
12166 - Made our unit tests compile again on OpenBSD 3.5, and tor
12167 itself compile again on OpenBSD on a sparc64.
12168 - We were neglecting milliseconds when logging on win32, so
12169 everything appeared to happen at the beginning of each second.
12171 o Protocol changes:
12172 - 'Extend' relay cell payloads now include the digest of the
12173 intended next hop's identity key. Now we can verify that we're
12174 extending to the right router, and also extend to routers we
12175 hadn't heard of before.
12178 - Tor nodes can now act as relays (with an advertised ORPort)
12179 without being manually verified by the dirserver operators.
12180 - Uploaded descriptors of unverified routers are now accepted
12181 by the dirservers, and included in the directory.
12182 - Verified routers are listed by nickname in the running-routers
12183 list; unverified routers are listed as "$<fingerprint>".
12184 - We now use hash-of-identity-key in most places rather than
12185 nickname or addr:port, for improved security/flexibility.
12186 - To avoid Sybil attacks, paths still use only verified servers.
12187 But now we have a chance to play around with hybrid approaches.
12188 - Nodes track bandwidth usage to estimate capacity (not used yet).
12189 - ClientOnly option for nodes that never want to become servers.
12190 - Directory caching.
12191 - "AuthoritativeDir 1" option for the official dirservers.
12192 - Now other nodes (clients and servers) will cache the latest
12193 directory they've pulled down.
12194 - They can enable their DirPort to serve it to others.
12195 - Clients will pull down a directory from any node with an open
12196 DirPort, and check the signature/timestamp correctly.
12197 - Authoritative dirservers now fetch directories from other
12198 authdirservers, to stay better synced.
12199 - Running-routers list tells who's down also, along with noting
12200 if they're verified (listed by nickname) or unverified (listed
12202 - Allow dirservers to serve running-router list separately.
12203 This isn't used yet.
12204 - ORs connect-on-demand to other ORs
12205 - If you get an extend cell to an OR you're not connected to,
12206 connect, handshake, and forward the create cell.
12207 - The authoritative dirservers stay connected to everybody,
12208 and everybody stays connected to 0.0.7 servers, but otherwise
12209 clients/servers expire unused connections after 5 minutes.
12210 - When servers get a sigint, they delay 30 seconds (refusing new
12211 connections) then exit. A second sigint causes immediate exit.
12212 - File and name management:
12213 - Look for .torrc if no CONFDIR "torrc" is found.
12214 - If no datadir is defined, then choose, make, and secure ~/.tor
12216 - If torrc not found, exitpolicy reject *:*.
12217 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
12218 - If no nickname is defined, derive default from hostname.
12219 - Rename secret key files, e.g. identity.key -> secret_id_key,
12220 to discourage people from mailing their identity key to tor-ops.
12221 - Refuse to build a circuit before the directory has arrived --
12222 it won't work anyway, since you won't know the right onion keys
12224 - Try other dirservers immediately if the one you try is down. This
12225 should tolerate down dirservers better now.
12226 - Parse tor version numbers so we can do an is-newer-than check
12227 rather than an is-in-the-list check.
12228 - New socks command 'resolve', to let us shim gethostbyname()
12230 - A 'tor_resolve' script to access the socks resolve functionality.
12231 - A new socks-extensions.txt doc file to describe our
12232 interpretation and extensions to the socks protocols.
12233 - Add a ContactInfo option, which gets published in descriptor.
12234 - Publish OR uptime in descriptor (and thus in directory) too.
12235 - Write tor version at the top of each log file
12236 - New docs in the tarball:
12238 - Document that you should proxy your SSL traffic too.
12241 Changes in version 0.0.7.2 - 2004-07-07
12242 o A better fix for the 0.0.0.0 problem, that will hopefully
12243 eliminate the remaining related assertion failures.
12246 Changes in version 0.0.7.1 - 2004-07-04
12247 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
12248 since internally we use 0.0.0.0 to signify "not yet resolved".
12251 Changes in version 0.0.7 - 2004-06-07
12252 o Updated the man page to reflect the new features.
12255 Changes in version 0.0.7rc2 - 2004-06-06
12256 o Changes from 0.0.7rc1:
12257 - Make it build on Win32 again.
12258 o Changes from 0.0.6.2:
12259 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
12263 Changes in version 0.0.7rc1 - 2004-06-02
12265 - On sighup, we were adding another log without removing the first
12266 one. So log messages would get duplicated n times for n sighups.
12267 - Several cases of using a connection after we'd freed it. The
12268 problem was that connections that are pending resolve are in both
12269 the pending_resolve tree, and also the circuit's resolving_streams
12270 list. When you want to remove one, you must remove it from both.
12271 - Fix a double-mark-for-close where an end cell arrived for a
12272 resolving stream, and then the resolve failed.
12273 - Check directory signatures based on name of signer, not on whom
12274 we got the directory from. This will let us cache directories more
12277 - Crank up some of our constants to handle more users.
12280 Changes in version 0.0.7pre1 - 2004-06-02
12281 o Fixes for crashes and other obnoxious bugs:
12282 - Fix an epipe bug: sometimes when directory connections failed
12283 to connect, we would give them a chance to flush before closing
12285 - When we detached from a circuit because of resolvefailed, we
12286 would immediately try the same circuit twice more, and then
12287 give up on the resolve thinking we'd tried three different
12289 - Limit the number of intro circuits we'll attempt to build for a
12290 hidden service per 15-minute period.
12291 - Check recommended-software string *early*, before actually parsing
12292 the directory. Thus we can detect an obsolete version and exit,
12293 even if the new directory format doesn't parse.
12294 o Fixes for security bugs:
12295 - Remember which nodes are dirservers when you startup, and if a
12296 random OR enables his dirport, don't automatically assume he's
12297 a trusted dirserver.
12299 - Directory connections were asking the wrong poll socket to
12300 start writing, and not asking themselves to start writing.
12301 - When we detached from a circuit because we sent a begin but
12302 didn't get a connected, we would use it again the first time;
12303 but after that we would correctly switch to a different one.
12304 - Stop warning when the first onion decrypt attempt fails; they
12305 will sometimes legitimately fail now that we rotate keys.
12306 - Override unaligned-access-ok check when $host_cpu is ia64 or
12307 arm. Apparently they allow it but the kernel whines.
12308 - Dirservers try to reconnect periodically too, in case connections
12310 - Fix some memory leaks in directory servers.
12311 - Allow backslash in Win32 filenames.
12312 - Made Tor build complain-free on FreeBSD, hopefully without
12313 breaking other BSD builds. We'll see.
12315 - Doxygen markup on all functions and global variables.
12316 - Make directory functions update routerlist, not replace it. So
12317 now directory disagreements are not so critical a problem.
12318 - Remove the upper limit on number of descriptors in a dirserver's
12319 directory (not that we were anywhere close).
12320 - Allow multiple logfiles at different severity ranges.
12321 - Allow *BindAddress to specify ":port" rather than setting *Port
12322 separately. Allow multiple instances of each BindAddress config
12323 option, so you can bind to multiple interfaces if you want.
12324 - Allow multiple exit policy lines, which are processed in order.
12325 Now we don't need that huge line with all the commas in it.
12326 - Enable accept/reject policies on SOCKS connections, so you can bind
12327 to 0.0.0.0 but still control who can use your OP.
12330 Changes in version 0.0.6.2 - 2004-05-16
12331 o Our integrity-checking digest was checking only the most recent cell,
12332 not the previous cells like we'd thought.
12333 Thanks to Stefan Mark for finding the flaw!
12336 Changes in version 0.0.6.1 - 2004-05-06
12337 o Fix two bugs in our AES counter-mode implementation (this affected
12338 onion-level stream encryption, but not TLS-level). It turns
12339 out we were doing something much more akin to a 16-character
12340 polyalphabetic cipher. Oops.
12341 Thanks to Stefan Mark for finding the flaw!
12342 o Retire moria3 as a directory server, and add tor26 as a directory
12346 Changes in version 0.0.6 - 2004-05-02
12347 [version bump only]
12350 Changes in version 0.0.6rc4 - 2004-05-01
12351 o Update the built-in dirservers list to use the new directory format
12352 o Fix a rare seg fault: if a node offering a hidden service attempts
12353 to build a circuit to Alice's rendezvous point and fails before it
12354 reaches the last hop, it retries with a different circuit, but
12356 o Handle windows socket errors correctly.
12359 Changes in version 0.0.6rc3 - 2004-04-28
12360 o Don't expire non-general excess circuits (if we had enough
12361 circuits open, we were expiring rendezvous circuits -- even
12362 when they had a stream attached. oops.)
12363 o Fetch randomness from /dev/urandom better (not via fopen/fread)
12364 o Better debugging for tls errors
12365 o Some versions of openssl have an SSL_pending function that erroneously
12366 returns bytes when there is a non-application record pending.
12367 o Set Content-Type on the directory and hidserv descriptor.
12368 o Remove IVs from cipher code, since AES-ctr has none.
12369 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
12370 o We were using an array of length zero in a few places.
12371 o win32's gethostbyname can't resolve an IP to an IP.
12372 o win32's close can't close a socket.
12375 Changes in version 0.0.6rc2 - 2004-04-26
12376 o Fix a bug where we were closing tls connections intermittently.
12377 It turns out openssl keeps its errors around -- so if an error
12378 happens, and you don't ask about it, and then another openssl
12379 operation happens and succeeds, and you ask if there was an error,
12380 it tells you about the first error. Fun fun.
12381 o Fix a bug that's been lurking since 27 may 03 (!)
12382 When passing back a destroy cell, we would use the wrong circ id.
12383 'Mostly harmless', but still worth fixing.
12384 o Since we don't support truncateds much, don't bother sending them;
12385 just close the circ.
12386 o check for <machine/limits.h> so we build on NetBSD again (I hope).
12387 o don't crash if a conn that sent a begin has suddenly lost its circuit
12388 (this was quite rare).
12391 Changes in version 0.0.6rc1 - 2004-04-25
12392 o We now rotate link (tls context) keys and onion keys.
12393 o CREATE cells now include oaep padding, so you can tell
12394 if you decrypted them correctly.
12395 o Add bandwidthburst to server descriptor.
12396 o Directories now say which dirserver signed them.
12397 o Use a tor_assert macro that logs failed assertions too.
12400 Changes in version 0.0.6pre5 - 2004-04-18
12401 o changes from 0.0.6pre4:
12402 - make tor build on broken freebsd 5.2 installs
12403 - fix a failed assert when you try an intro point, get a nack, and try
12404 a second one and it works.
12405 - when alice uses a port that the hidden service doesn't accept,
12406 it now sends back an end cell (denied by exit policy). otherwise
12407 alice would just have to wait to time out.
12408 - fix another rare bug: when we had tried all the intro
12409 points for a hidden service, we fetched the descriptor
12410 again, but we left our introcirc thinking it had already
12411 sent an intro, so it kept waiting for a response...
12412 - bugfix: when you sleep your hidden-service laptop, as soon
12413 as it wakes up it tries to upload a service descriptor, but
12414 socketpair fails for some reason (localhost not up yet?).
12415 now we simply give up on that upload, and we'll try again later.
12416 i'd still like to find the bug though.
12417 - if an intro circ waiting for an ack dies before getting one, then
12419 - we were reusing stale service descriptors and refetching usable
12423 Changes in version 0.0.6pre4 - 2004-04-14
12424 o changes from 0.0.6pre3:
12425 - when bob fails to connect to the rendezvous point, and his
12426 circ didn't fail because of the rendezvous point itself, then
12427 he retries a couple of times
12428 - we expire introduction and rendezvous circs more thoroughly
12429 (sometimes they were hanging around forever)
12430 - we expire unattached rendezvous streams that have been around
12431 too long (they were sticking around forever).
12432 - fix a measly fencepost error that was crashing everybody with
12436 Changes in version 0.0.6pre3 - 2004-04-14
12437 o changes from 0.0.6pre2:
12438 - make hup work again
12439 - fix some memory leaks for dirservers
12440 - allow more skew in rendezvous descriptor timestamps, to help
12441 handle people like blanu who don't know what time it is
12442 - normal circs are 3 hops, but some rend/intro circs are 4, if
12443 the initiator doesn't get to choose the last hop
12444 - send acks for introductions, so alice can know whether to try
12446 - bob publishes intro points more correctly
12447 o changes from 0.0.5:
12448 - fix an assert trigger that's been plaguing us since the days
12449 of 0.0.2prexx (thanks weasel!)
12450 - retry stream correctly when we fail to connect because of
12451 exit-policy-reject (should try another) or can't-resolve-address
12452 (also should try another, because dns on random internet servers
12454 - when we hup a dirserver and we've *removed* a server from the
12455 approved-routers list, now we remove that server from the
12456 in-memory directories too
12459 Changes in version 0.0.6pre2 - 2004-04-08
12460 o We fixed our base32 implementation. Now it works on all architectures.
12463 Changes in version 0.0.6pre1 - 2004-04-08
12465 - Hidden services and rendezvous points are implemented. Go to
12466 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
12467 hidden services. (This only works via a socks4a proxy such as
12468 Privoxy, and currently it's quite slow.)
12471 Changes in version 0.0.5 - 2004-03-30
12472 [version bump only]
12475 Changes in version 0.0.5rc3 - 2004-03-29
12476 o Install torrc as torrc.sample -- we no longer clobber your
12478 o Re-enable recommendedversion checking (we broke it in rc2, oops)
12479 o Add in a 'notice' log level for things the operator should hear
12480 but that aren't warnings
12483 Changes in version 0.0.5rc2 - 2004-03-29
12484 o Hold socks connection open until reply is flushed (if possible)
12485 o Make exit nodes resolve IPs to IPs immediately, rather than asking
12486 the dns farm to do it.
12487 o Fix c99 aliasing warnings in rephist.c
12488 o Don't include server descriptors that are older than 24 hours in the
12490 o Give socks 'reject' replies their whole 15s to attempt to flush,
12491 rather than seeing the 60s timeout and assuming the flush had failed.
12492 o Clean automake droppings from the cvs repository
12495 Changes in version 0.0.5rc1 - 2004-03-28
12496 o Fix mangled-state bug in directory fetching (was causing sigpipes).
12497 o Only build circuits after we've fetched the directory: clients were
12498 using only the directory servers before they'd fetched a directory.
12499 This also means longer startup time; so it goes.
12500 o Fix an assert trigger where an OP would fail to handshake, and we'd
12501 expect it to have a nickname.
12502 o Work around a tsocks bug: do a socks reject when AP connection dies
12503 early, else tsocks goes into an infinite loop.
12506 Changes in version 0.0.4 - 2004-03-26
12507 o When connecting to a dirserver or OR and the network is down,
12511 Changes in version 0.0.3 - 2004-03-26
12512 o Warn and fail if server chose a nickname with illegal characters
12513 o Port to Solaris and Sparc:
12514 - include missing header fcntl.h
12515 - have autoconf find -lsocket -lnsl automatically
12516 - deal with hardware word alignment
12517 - make uname() work (solaris has a different return convention)
12518 - switch from using signal() to sigaction()
12519 o Preliminary work on reputation system:
12520 - Keep statistics on success/fail of connect attempts; they're published
12521 by kill -USR1 currently.
12522 - Add a RunTesting option to try to learn link state by creating test
12523 circuits, even when SocksPort is off.
12524 - Remove unused open circuits when there are too many.
12527 Changes in version 0.0.2 - 2004-03-19
12528 - Include strlcpy and strlcat for safer string ops
12529 - define INADDR_NONE so we compile (but still not run) on solaris
12532 Changes in version 0.0.2pre27 - 2004-03-14
12534 - Allow internal tor networks (we were rejecting internal IPs,
12535 now we allow them if they're set explicitly).
12536 - And fix a few endian issues.
12539 Changes in version 0.0.2pre26 - 2004-03-14
12541 - If a stream times out after 15s without a connected cell, don't
12542 try that circuit again: try a new one.
12543 - Retry streams at most 4 times. Then give up.
12544 - When a dirserver gets a descriptor from an unknown router, it
12545 logs its fingerprint (so the dirserver operator can choose to
12546 accept it even without mail from the server operator).
12547 - Inform unapproved servers when we reject their descriptors.
12548 - Make tor build on Windows again. It works as a client, who knows
12550 - Clearer instructions in the torrc for how to set up a server.
12551 - Be more efficient about reading fd's when our global token bucket
12552 (used for rate limiting) becomes empty.
12554 - Stop asserting that computers always go forward in time. It's
12556 - When we sent a cell (e.g. destroy) and then marked an OR connection
12557 expired, we might close it before finishing a flush if the other
12558 side isn't reading right then.
12559 - Don't allow dirservers to start if they haven't defined
12560 RecommendedVersions
12561 - We were caching transient dns failures. Oops.
12562 - Prevent servers from publishing an internal IP as their address.
12563 - Address a strcat vulnerability in circuit.c
12566 Changes in version 0.0.2pre25 - 2004-03-04
12568 - Put the OR's IP in its router descriptor, not its fqdn. That way
12569 we'll stop being stalled by gethostbyname for nodes with flaky dns,
12572 - If the user typed in an address that didn't resolve, the server
12576 Changes in version 0.0.2pre24 - 2004-03-03
12578 - Fix an assertion failure in dns.c, where we were trying to dequeue
12579 a pending dns resolve even if it wasn't pending
12580 - Fix a spurious socks5 warning about still trying to write after the
12581 connection is finished.
12582 - Hold certain marked_for_close connections open until they're finished
12583 flushing, rather than losing bytes by closing them too early.
12584 - Correctly report the reason for ending a stream
12585 - Remove some duplicate calls to connection_mark_for_close
12586 - Put switch_id and start_daemon earlier in the boot sequence, so it
12587 will actually try to chdir() to options.DataDirectory
12588 - Make 'make test' exit(1) if a test fails; fix some unit tests
12589 - Make tor fail when you use a config option it doesn't know about,
12590 rather than warn and continue.
12591 - Make --version work
12592 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
12595 Changes in version 0.0.2pre23 - 2004-02-29
12597 - Print a statement when the first circ is finished, so the user
12598 knows it's working.
12599 - If a relay cell is unrecognized at the end of the circuit,
12600 send back a destroy. (So attacks to mutate cells are more
12602 - New config option 'excludenodes' to avoid certain nodes for circuits.
12603 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
12604 so you can collect coredumps there.
12606 - Fix a bug in tls flushing where sometimes data got wedged and
12607 didn't flush until more data got sent. Hopefully this bug was
12608 a big factor in the random delays we were seeing.
12609 - Make 'connected' cells include the resolved IP, so the client
12610 dns cache actually gets populated.
12611 - Disallow changing from ORPort=0 to ORPort>0 on hup.
12612 - When we time-out on a stream and detach from the circuit, send an
12613 end cell down it first.
12614 - Only warn about an unknown router (in exitnodes, entrynodes,
12615 excludenodes) after we've fetched a directory.
12618 Changes in version 0.0.2pre22 - 2004-02-26
12620 - Servers publish less revealing uname information in descriptors.
12621 - More memory tracking and assertions, to crash more usefully when
12623 - If the default torrc isn't there, just use some default defaults.
12624 Plus provide an internal dirservers file if they don't have one.
12625 - When the user tries to use Tor as an http proxy, give them an http
12626 501 failure explaining that we're a socks proxy.
12627 - Dump a new router.desc on hup, to help confused people who change
12628 their exit policies and then wonder why router.desc doesn't reflect
12630 - Clean up the generic tor.sh init script that we ship with.
12632 - If the exit stream is pending on the resolve, and a destroy arrives,
12633 then the stream wasn't getting removed from the pending list. I
12634 think this was the one causing recent server crashes.
12635 - Use a more robust poll on OSX 10.3, since their poll is flaky.
12636 - When it couldn't resolve any dirservers, it was useless from then on.
12637 Now it reloads the RouterFile (or default dirservers) if it has no
12639 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
12640 many users don't even *have* a /usr/local/sbin/.
12643 Changes in version 0.0.2pre21 - 2004-02-18
12645 - There's a ChangeLog file that actually reflects the changelog.
12646 - There's a 'torify' wrapper script, with an accompanying
12647 tor-tsocks.conf, that simplifies the process of using tsocks for
12648 tor. It even has a man page.
12649 - The tor binary gets installed to sbin rather than bin now.
12650 - Retry streams where the connected cell hasn't arrived in 15 seconds
12651 - Clean up exit policy handling -- get the default out of the torrc,
12652 so we can update it without forcing each server operator to fix
12654 - Allow imaps and pop3s in default exit policy
12656 - Prevent picking middleman nodes as the last node in the circuit
12659 Changes in version 0.0.2pre20 - 2004-01-30
12661 - We now have a deb package, and it's in debian unstable. Go to
12662 it, apt-getters. :)
12663 - I've split the TotalBandwidth option into BandwidthRate (how many
12664 bytes per second you want to allow, long-term) and
12665 BandwidthBurst (how many bytes you will allow at once before the cap
12666 kicks in). This better token bucket approach lets you, say, set
12667 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
12668 performance while not exceeding your monthly bandwidth quota.
12669 - Push out a tls record's worth of data once you've got it, rather
12670 than waiting until you've read everything waiting to be read. This
12671 may improve performance by pipelining better. We'll see.
12672 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
12673 from failed circuits (if they haven't been connected yet) and attach
12675 - Expire old streams that haven't managed to connect. Some day we'll
12676 have them reattach to new circuits instead.
12679 - Fix several memory leaks that were causing servers to become bloated
12681 - Fix a few very rare assert triggers. A few more remain.
12682 - Setuid to User _before_ complaining about running as root.
12685 Changes in version 0.0.2pre19 - 2004-01-07
12687 - Fix deadlock condition in dns farm. We were telling a child to die by
12688 closing the parent's file descriptor to him. But newer children were
12689 inheriting the open file descriptor from the parent, and since they
12690 weren't closing it, the socket never closed, so the child never read
12691 eof, so he never knew to exit. Similarly, dns workers were holding
12692 open other sockets, leading to all sorts of chaos.
12693 - New cleaner daemon() code for forking and backgrounding.
12694 - If you log to a file, it now prints an entry at the top of the
12695 logfile so you know it's working.
12696 - The onionskin challenge length was 30 bytes longer than necessary.
12697 - Started to patch up the spec so it's not quite so out of date.
12700 Changes in version 0.0.2pre18 - 2004-01-02
12702 - Fix endian issues with the 'integrity' field in the relay header.
12703 - Fix a potential bug where connections in state
12704 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
12707 Changes in version 0.0.2pre17 - 2003-12-30
12709 - Made --debuglogfile (or any second log file, actually) work.
12710 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
12711 adversary could force us into an infinite loop.
12714 - Each onionskin handshake now includes a hash of the computed key,
12715 to prove the server's identity and help perfect forward secrecy.
12716 - Changed cell size from 256 to 512 bytes (working toward compatibility
12718 - Changed cell length to 2 bytes, and moved it to the relay header.
12719 - Implemented end-to-end integrity checking for the payloads of
12721 - Separated streamid from 'recognized' (otherwise circuits will get
12722 messed up when we try to have streams exit from the middle). We
12723 use the integrity-checking to confirm that a cell is addressed to
12725 - Randomize the initial circid and streamid values, so an adversary who
12726 breaks into a node can't learn how many circuits or streams have
12730 Changes in version 0.0.2pre16 - 2003-12-14
12732 - Fixed a bug that made HUP trigger an assert
12733 - Fixed a bug where a circuit that immediately failed wasn't being
12734 counted as a failed circuit in counting retries.
12737 - Now we close the circuit when we get a truncated cell: otherwise we're
12738 open to an anonymity attack where a bad node in the path truncates
12739 the circuit and then we open streams at him.
12740 - Add port ranges to exit policies
12741 - Add a conservative default exit policy
12742 - Warn if you're running tor as root
12743 - on HUP, retry OR connections and close/rebind listeners
12744 - options.EntryNodes: try these nodes first when picking the first node
12745 - options.ExitNodes: if your best choices happen to include any of
12746 your preferred exit nodes, you choose among just those preferred
12748 - options.ExcludedNodes: nodes that are never picked in path building
12751 Changes in version 0.0.2pre15 - 2003-12-03
12752 o Robustness and bugfixes:
12753 - Sometimes clients would cache incorrect DNS resolves, which would
12754 really screw things up.
12755 - An OP that goes offline would slowly leak all its sockets and stop
12757 - A wide variety of bugfixes in exit node selection, exit policy
12758 handling, and processing pending streams when a new circuit is
12760 - Pick nodes for a path only from those the directory says are up
12761 - Choose randomly from all running dirservers, not always the first one
12762 - Increase allowed http header size for directory fetch.
12763 - Stop writing to stderr (if we're daemonized it will be closed).
12764 - Enable -g always, so cores will be more useful to me.
12765 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
12768 - Wrote a man page. It lists commonly used options.
12771 - Change default loglevel to warn.
12772 - Make PidFile default to null rather than littering in your CWD.
12773 - OnionRouter config option is now obsolete. Instead it just checks
12775 - Moved to a single unified torrc file for both clients and servers.
12778 Changes in version 0.0.2pre14 - 2003-11-29
12779 o Robustness and bugfixes:
12780 - Force the admin to make the DataDirectory himself
12781 - to get ownership/permissions right
12782 - so clients no longer make a DataDirectory and then never use it
12783 - fix bug where a client who was offline for 45 minutes would never
12784 pull down a directory again
12785 - fix (or at least hide really well) the dns assert bug that was
12786 causing server crashes
12787 - warnings and improved robustness wrt clockskew for certs
12788 - use the native daemon(3) to daemonize, when available
12789 - exit if bind() fails
12790 - exit if neither socksport nor orport is defined
12791 - include our own tor_timegm (Win32 doesn't have its own)
12792 - bugfix for win32 with lots of connections
12793 - fix minor bias in PRNG
12794 - make dirserver more robust to corrupt cached directory
12797 - Wrote the design document (woo)
12799 o Circuit building and exit policies:
12800 - Circuits no longer try to use nodes that the directory has told them
12802 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
12803 bitcounts (18.0.0.0/8).
12804 - Make AP connections standby for a circuit if no suitable circuit
12805 exists, rather than failing
12806 - Circuits choose exit node based on addr/port, exit policies, and
12807 which AP connections are standing by
12808 - Bump min pathlen from 2 to 3
12809 - Relay end cells have a payload to describe why the stream ended.
12810 - If the stream failed because of exit policy, try again with a new
12812 - Clients have a dns cache to remember resolved addresses.
12813 - Notice more quickly when we have no working circuits
12816 - APPort is now called SocksPort
12817 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
12819 - RecommendedVersions is now a config variable rather than
12820 hardcoded (for dirservers)
12821 - Reloads config on HUP
12822 - Usage info on -h or --help
12823 - If you set User and Group config vars, it'll setu/gid to them.
12826 Changes in version 0.0.2pre13 - 2003-10-19
12827 o General stability:
12828 - SSL_write no longer fails when it returns WANTWRITE and the number
12829 of bytes in the buf has changed by the next SSL_write call.
12830 - Fix segfault fetching directory when network is down
12831 - Fix a variety of minor memory leaks
12832 - Dirservers reload the fingerprints file on HUP, so I don't have
12833 to take down the network when I approve a new router
12834 - Default server config file has explicit Address line to specify fqdn
12837 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
12838 - Make listener connections not ever alloc bufs
12840 o Autoconf improvements:
12841 - don't clobber an external CFLAGS in ./configure
12842 - Make install now works
12843 - create var/lib/tor on make install
12844 - autocreate a tor.sh initscript to help distribs
12845 - autocreate the torrc and sample-server-torrc with correct paths
12847 o Log files and Daemonizing now work:
12848 - If --DebugLogFile is specified, log to it at -l debug
12849 - If --LogFile is specified, use it instead of commandline
12850 - If --RunAsDaemon is set, tor forks and backgrounds on startup