1 Changes in version 0.2.2.22-alpha - 2011-01-25
2 o Major bugfixes (security):
3 - Fix a bounds-checking error that could allow an attacker to
4 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
8 - Adjust our TLS Diffie-Hellman parameters to match those used by
12 - Check for and reject overly long directory certificates and
13 directory tokens before they have a chance to hit any assertions.
14 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
17 Changes in version 0.2.2.21-alpha - 2011-01-15
18 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
19 continues our recent code security audit work. The main fix resolves
20 a remote heap overflow vulnerability that can allow remote code
21 execution (CVE-2011-0427). Other fixes address a variety of assert
22 and crash bugs, most of which we think are hard to exploit remotely.
24 o Major bugfixes (security), also included in 0.2.1.29:
25 - Fix a heap overflow bug where an adversary could cause heap
26 corruption. This bug probably allows remote code execution
27 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
29 - Prevent a denial-of-service attack by disallowing any
30 zlib-compressed data whose compression factor is implausibly
31 high. Fixes part of bug 2324; reported by "doorss".
32 - Zero out a few more keys in memory before freeing them. Fixes
33 bug 2384 and part of bug 2385. These key instances found by
34 "cypherpunks", based on Andrew Case's report about being able
35 to find sensitive data in Tor's memory space if you have enough
36 permissions. Bugfix on 0.0.2pre9.
38 o Major bugfixes (crashes), also included in 0.2.1.29:
39 - Prevent calls to Libevent from inside Libevent log handlers.
40 This had potential to cause a nasty set of crashes, especially
41 if running Libevent with debug logging enabled, and running
42 Tor with a controller watching for low-severity log messages.
43 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
44 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
45 underflow errors there too. Fixes the other part of bug 2324.
46 - Fix a bug where we would assert if we ever had a
47 cached-descriptors.new file (or another file read directly into
48 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
49 on 0.2.1.25. Found by doorss.
50 - Fix some potential asserts and parsing issues with grossly
51 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
54 o Minor bugfixes (other), also included in 0.2.1.29:
55 - Fix a bug with handling misformed replies to reverse DNS lookup
56 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
57 bug reported by doorss.
58 - Fix compilation on mingw when a pthreads compatibility library
59 has been installed. (We don't want to use it, so we shouldn't
60 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
61 - Fix a bug where we would declare that we had run out of virtual
62 addresses when the address space was only half-exhausted. Bugfix
64 - Correctly handle the case where AutomapHostsOnResolve is set but
65 no virtual addresses are available. Fixes bug 2328; bugfix on
66 0.1.2.1-alpha. Bug found by doorss.
67 - Correctly handle wrapping around when we run out of virtual
68 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
70 o Minor features, also included in 0.2.1.29:
71 - Update to the January 1 2011 Maxmind GeoLite Country database.
72 - Introduce output size checks on all of our decryption functions.
74 o Build changes, also included in 0.2.1.29:
75 - Tor does not build packages correctly with Automake 1.6 and earlier;
76 added a check to Makefile.am to make sure that we're building with
77 Automake 1.7 or later.
78 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
79 because we built it with a too-old version of automake. Thus that
80 release broke ./configure --enable-openbsd-malloc, which is popular
81 among really fast exit relays on Linux.
83 o Major bugfixes, new in 0.2.2.21-alpha:
84 - Prevent crash/heap corruption when the cbtnummodes consensus
85 parameter is set to 0 or large values. Fixes bug 2317; bugfix
88 o Major features, new in 0.2.2.21-alpha:
89 - Introduce minimum/maximum values that clients will believe
90 from the consensus. Now we'll have a better chance to avoid crashes
91 or worse when a consensus param has a weird value.
93 o Minor features, new in 0.2.2.21-alpha:
94 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
95 used on bridges, and it makes bridge scanning somewhat easier.
96 - If writing the state file to disk fails, wait up to an hour before
97 retrying again, rather than trying again each second. Fixes bug
98 2346; bugfix on Tor 0.1.1.3-alpha.
99 - Make Libevent log messages get delivered to controllers later,
100 and not from inside the Libevent log handler. This prevents unsafe
101 reentrant Libevent calls while still letting the log messages
103 - Detect platforms that brokenly use a signed size_t, and refuse to
104 build there. Found and analyzed by doorss and rransom.
105 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
108 o Minor bugfixes, new in 0.2.2.21-alpha:
109 - Handle SOCKS messages longer than 128 bytes long correctly, rather
110 than waiting forever for them to finish. Fixes bug 2330; bugfix
111 on 0.2.0.16-alpha. Found by doorss.
112 - Add assertions to check for overflow in arguments to
113 base32_encode() and base32_decode(); fix a signed-unsigned
114 comparison there too. These bugs are not actually reachable in Tor,
115 but it's good to prevent future errors too. Found by doorss.
116 - Correctly detect failures to create DNS requests when using Libevent
117 versions before v2. (Before Libevent 2, we used our own evdns
118 implementation. Its return values for Libevent's evdns_resolve_*()
119 functions are not consistent with those from Libevent.) Fixes bug
120 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
122 o Documentation, new in 0.2.2.21-alpha:
123 - Document the default socks host and port (127.0.0.1:9050) for
127 Changes in version 0.2.1.29 - 2011-01-15
128 Tor 0.2.1.29 continues our recent code security audit work. The main
129 fix resolves a remote heap overflow vulnerability that can allow remote
130 code execution. Other fixes address a variety of assert and crash bugs,
131 most of which we think are hard to exploit remotely.
133 o Major bugfixes (security):
134 - Fix a heap overflow bug where an adversary could cause heap
135 corruption. This bug probably allows remote code execution
136 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
138 - Prevent a denial-of-service attack by disallowing any
139 zlib-compressed data whose compression factor is implausibly
140 high. Fixes part of bug 2324; reported by "doorss".
141 - Zero out a few more keys in memory before freeing them. Fixes
142 bug 2384 and part of bug 2385. These key instances found by
143 "cypherpunks", based on Andrew Case's report about being able
144 to find sensitive data in Tor's memory space if you have enough
145 permissions. Bugfix on 0.0.2pre9.
147 o Major bugfixes (crashes):
148 - Prevent calls to Libevent from inside Libevent log handlers.
149 This had potential to cause a nasty set of crashes, especially
150 if running Libevent with debug logging enabled, and running
151 Tor with a controller watching for low-severity log messages.
152 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
153 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
154 underflow errors there too. Fixes the other part of bug 2324.
155 - Fix a bug where we would assert if we ever had a
156 cached-descriptors.new file (or another file read directly into
157 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
158 on 0.2.1.25. Found by doorss.
159 - Fix some potential asserts and parsing issues with grossly
160 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
163 o Minor bugfixes (other):
164 - Fix a bug with handling misformed replies to reverse DNS lookup
165 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
166 bug reported by doorss.
167 - Fix compilation on mingw when a pthreads compatibility library
168 has been installed. (We don't want to use it, so we shouldn't
169 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
170 - Fix a bug where we would declare that we had run out of virtual
171 addresses when the address space was only half-exhausted. Bugfix
173 - Correctly handle the case where AutomapHostsOnResolve is set but
174 no virtual addresses are available. Fixes bug 2328; bugfix on
175 0.1.2.1-alpha. Bug found by doorss.
176 - Correctly handle wrapping around to when we run out of virtual
177 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
178 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
179 because we built it with a too-old version of automake. Thus that
180 release broke ./configure --enable-openbsd-malloc, which is popular
181 among really fast exit relays on Linux.
184 - Update to the January 1 2011 Maxmind GeoLite Country database.
185 - Introduce output size checks on all of our decryption functions.
188 - Tor does not build packages correctly with Automake 1.6 and earlier;
189 added a check to Makefile.am to make sure that we're building with
190 Automake 1.7 or later.
193 Changes in version 0.2.2.20-alpha - 2010-12-17
194 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
195 exploitable bugs. We also fix a variety of other significant bugs,
196 change the IP address for one of our directory authorities, and update
197 the minimum version that Tor relays must run to join the network.
200 - Fix a remotely exploitable bug that could be used to crash instances
201 of Tor remotely by overflowing on the heap. Remote-code execution
202 hasn't been confirmed, but can't be ruled out. Everyone should
203 upgrade. Bugfix on the 0.1.1 series and later.
204 - Fix a bug that could break accounting on 64-bit systems with large
205 time_t values, making them hibernate for impossibly long intervals.
206 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
207 - Fix a logic error in directory_fetches_from_authorities() that
208 would cause all _non_-exits refusing single-hop-like circuits
209 to fetch from authorities, when we wanted to have _exits_ fetch
210 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
212 - Fix a stream fairness bug that would cause newer streams on a given
213 circuit to get preference when reading bytes from the origin or
214 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
215 introduced before the first Tor release, in svn revision r152.
217 o Directory authority changes:
218 - Change IP address and ports for gabelmoo (v3 directory authority).
221 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
222 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
223 - Fix an off-by-one error in calculating some controller command
224 argument lengths. Fortunately, this mistake is harmless since
225 the controller code does redundant NUL termination too. Found by
226 boboper. Bugfix on 0.1.1.1-alpha.
227 - Do not dereference NULL if a bridge fails to build its
228 extra-info descriptor. Found by an anonymous commenter on
229 Trac. Bugfix on 0.2.2.19-alpha.
232 - Update to the December 1 2010 Maxmind GeoLite Country database.
233 - Directory authorities now reject relays running any versions of
234 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
235 known bugs that keep RELAY_EARLY cells from working on rendezvous
236 circuits. Followup to fix for bug 2081.
237 - Directory authorities now reject relays running any version of Tor
238 older than 0.2.0.26-rc. That version is the earliest that fetches
239 current directory information correctly. Fixes bug 2156.
240 - Report only the top 10 ports in exit-port stats in order not to
241 exceed the maximum extra-info descriptor length of 50 KB. Implements
245 Changes in version 0.2.1.28 - 2010-12-17
246 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
247 exploitable bugs. We also took this opportunity to change the IP address
248 for one of our directory authorities, and to update the geoip database
252 - Fix a remotely exploitable bug that could be used to crash instances
253 of Tor remotely by overflowing on the heap. Remote-code execution
254 hasn't been confirmed, but can't be ruled out. Everyone should
255 upgrade. Bugfix on the 0.1.1 series and later.
257 o Directory authority changes:
258 - Change IP address and ports for gabelmoo (v3 directory authority).
261 - Update to the December 1 2010 Maxmind GeoLite Country database.
264 Changes in version 0.2.1.27 - 2010-11-23
265 Yet another OpenSSL security patch broke its compatibility with Tor:
266 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
267 also took this opportunity to fix several crash bugs, integrate a new
268 directory authority, and update the bundled GeoIP database.
271 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
272 No longer set the tlsext_host_name extension on server SSL objects;
273 but continue to set it on client SSL objects. Our goal in setting
274 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
275 bugfix on 0.2.1.1-alpha.
276 - Do not log messages to the controller while shrinking buffer
277 freelists. Doing so would sometimes make the controller connection
278 try to allocate a buffer chunk, which would mess up the internals
279 of the freelist and cause an assertion failure. Fixes bug 1125;
280 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
281 - Learn our external IP address when we're a relay or bridge, even if
282 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
283 where we introduced bridge relays that don't need to publish to
284 be useful. Fixes bug 2050.
285 - Do even more to reject (and not just ignore) annotations on
286 router descriptors received anywhere but from the cache. Previously
287 we would ignore such annotations at first, but cache them to disk
288 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
289 - When you're using bridges and your network goes away and your
290 bridges get marked as down, recover when you attempt a new socks
291 connection (if the network is back), rather than waiting up to an
292 hour to try fetching new descriptors for your bridges. Bugfix on
293 0.2.0.3-alpha; fixes bug 1981.
296 - Move to the November 2010 Maxmind GeoLite country db (rather
297 than the June 2009 ip-to-country GeoIP db) for our statistics that
298 count how many users relays are seeing from each country. Now we'll
299 have more accurate data, especially for many African countries.
301 o New directory authorities:
302 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
306 - Fix an assertion failure that could occur in directory caches or
307 bridge users when using a very short voting interval on a testing
308 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
310 - Enforce multiplicity rules when parsing annotations. Bugfix on
311 0.2.0.8-alpha. Found by piebeer.
312 - Allow handshaking OR connections to take a full KeepalivePeriod
313 seconds to handshake. Previously, we would close them after
314 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
315 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
317 - When building with --enable-gcc-warnings on OpenBSD, disable
318 warnings in system headers. This makes --enable-gcc-warnings
322 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
323 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
324 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
325 Servers can start sending this code when enough clients recognize
326 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
327 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
328 Patch from mingw-san.
331 - Remove the old debian/ directory from the main Tor distribution.
332 The official Tor-for-debian git repository lives at the URL
333 https://git.torproject.org/debian/tor.git
334 - Stop shipping the old doc/website/ directory in the tarball. We
335 changed the website format in late 2010, and what we shipped in
336 0.2.1.26 really wasn't that useful anyway.
339 Changes in version 0.2.2.19-alpha - 2010-11-22
340 Yet another OpenSSL security patch broke its compatibility with Tor:
341 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
344 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
345 No longer set the tlsext_host_name extension on server SSL objects;
346 but continue to set it on client SSL objects. Our goal in setting
347 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
348 bugfix on 0.2.1.1-alpha.
351 - Try harder not to exceed the maximum length of 50 KB when writing
352 statistics to extra-info descriptors. This bug was triggered by very
353 fast relays reporting exit-port, entry, and dirreq statistics.
354 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
355 - Publish a router descriptor even if generating an extra-info
356 descriptor fails. Previously we would not publish a router
357 descriptor without an extra-info descriptor; this can cause fast
358 exit relays collecting exit-port statistics to drop from the
359 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
362 Changes in version 0.2.2.18-alpha - 2010-11-16
363 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
364 us lately, makes unpublished bridge relays able to detect their IP
365 address, and fixes a wide variety of other bugs to get us much closer
369 - Do even more to reject (and not just ignore) annotations on
370 router descriptors received anywhere but from the cache. Previously
371 we would ignore such annotations at first, but cache them to disk
372 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
373 - Do not log messages to the controller while shrinking buffer
374 freelists. Doing so would sometimes make the controller connection
375 try to allocate a buffer chunk, which would mess up the internals
376 of the freelist and cause an assertion failure. Fixes bug 1125;
377 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
378 - Learn our external IP address when we're a relay or bridge, even if
379 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
380 where we introduced bridge relays that don't need to publish to
381 be useful. Fixes bug 2050.
382 - Maintain separate TLS contexts and certificates for incoming and
383 outgoing connections in bridge relays. Previously we would use the
384 same TLS contexts and certs for incoming and outgoing connections.
385 Bugfix on 0.2.0.3-alpha; addresses bug 988.
386 - Maintain separate identity keys for incoming and outgoing TLS
387 contexts in bridge relays. Previously we would use the same
388 identity keys for incoming and outgoing TLS contexts. Bugfix on
389 0.2.0.3-alpha; addresses the other half of bug 988.
390 - Avoid an assertion failure when we as an authority receive a
391 duplicate upload of a router descriptor that we already have,
392 but which we previously considered an obsolete descriptor.
393 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
394 - Avoid a crash bug triggered by looking at a dangling pointer while
395 setting the network status consensus. Found by Robert Ransom.
396 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
397 - Fix a logic error where servers that _didn't_ act as exits would
398 try to keep their server lists more aggressively up to date than
399 exits, when it was supposed to be the other way around. Bugfix
402 o Minor bugfixes (on Tor 0.2.1.x and earlier):
403 - When we're trying to guess whether we know our IP address as
404 a relay, we would log various ways that we failed to guess
405 our address, but never log that we ended up guessing it
406 successfully. Now add a log line to help confused and anxious
407 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
408 - Bring the logic that gathers routerinfos and assesses the
409 acceptability of circuits into line. This prevents a Tor OP from
410 getting locked in a cycle of choosing its local OR as an exit for a
411 path (due to a .exit request) and then rejecting the circuit because
412 its OR is not listed yet. It also prevents Tor clients from using an
413 OR running in the same instance as an exit (due to a .exit request)
414 if the OR does not meet the same requirements expected of an OR
415 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
416 - Correctly describe errors that occur when generating a TLS object.
417 Previously we would attribute them to a failure while generating a
418 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
420 - Enforce multiplicity rules when parsing annotations. Bugfix on
421 0.2.0.8-alpha. Found by piebeer.
422 - Fix warnings that newer versions of autoconf produced during
423 ./autogen.sh. These warnings appear to be harmless in our case,
424 but they were extremely verbose. Fixes bug 2020.
426 o Minor bugfixes (on Tor 0.2.2.x):
427 - Enable protection of small arrays whenever we build with gcc
428 hardening features, not only when also building with warnings
429 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
432 - Make hidden services work better in private Tor networks by not
433 requiring any uptime to join the hidden service descriptor
434 DHT. Implements ticket 2088.
435 - Rate-limit the "your application is giving Tor only an IP address"
436 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
437 - When AllowSingleHopExits is set, print a warning to explain to the
438 relay operator why most clients are avoiding her relay.
439 - Update to the November 1 2010 Maxmind GeoLite Country database.
441 o Code simplifications and refactoring:
442 - When we fixed bug 1038 we had to put in a restriction not to send
443 RELAY_EARLY cells on rend circuits. This was necessary as long
444 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
445 active. Now remove this obsolete check. Resolves bug 2081.
446 - Some options used different conventions for uppercasing of acronyms
447 when comparing manpage and source. Fix those in favor of the
448 manpage, as it makes sense to capitalize acronyms.
449 - Remove the torrc.complete file. It hasn't been kept up to date
450 and users will have better luck checking out the manpage.
451 - Remove the obsolete "NoPublish" option; it has been flagged
452 as obsolete and has produced a warning since 0.1.1.18-rc.
453 - Remove everything related to building the expert bundle for OS X.
454 It has confused many users, doesn't work right on OS X 10.6,
455 and is hard to get rid of once installed. Resolves bug 1274.
458 Changes in version 0.2.2.17-alpha - 2010-09-30
459 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
460 to use one-hop circuits (which can put the exit relays at higher risk,
461 plus unbalance the network); fixes a big bug in bandwidth accounting
462 for relays that want to limit their monthly bandwidth use; fixes a
463 big pile of bugs in how clients tolerate temporary network failure;
464 and makes our adaptive circuit build timeout feature (which improves
465 client performance if your network is fast while not breaking things
466 if your network is slow) better handle bad networks.
469 - Exit relays now try harder to block exit attempts from unknown
470 relays, to make it harder for people to use them as one-hop proxies
471 a la tortunnel. Controlled by the refuseunknownexits consensus
472 parameter (currently enabled), or you can override it on your
473 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
475 o Major bugfixes (0.2.1.x and earlier):
476 - Fix a bug in bandwidth accounting that could make us use twice
477 the intended bandwidth when our interval start changes due to
478 daylight saving time. Now we tolerate skew in stored vs computed
479 interval starts: if the start of the period changes by no more than
480 50% of the period's duration, we remember bytes that we transferred
481 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
482 - Always search the Windows system directory for system DLLs, and
483 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
484 - When you're using bridges and your network goes away and your
485 bridges get marked as down, recover when you attempt a new socks
486 connection (if the network is back), rather than waiting up to an
487 hour to try fetching new descriptors for your bridges. Bugfix on
488 0.2.0.3-alpha; fixes bug 1981.
490 o Major bugfixes (on 0.2.2.x):
491 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
493 - Fix a segfault that could happen when operating a bridge relay with
494 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
495 - The consensus bandwidth-weights (used by clients to choose fast
496 relays) entered an unexpected edge case in September where
497 Exits were much scarcer than Guards, resulting in bad weight
498 recommendations. Now we compute them using new constraints that
499 should succeed in all cases. Also alter directory authorities to
500 not include the bandwidth-weights line if they fail to produce
501 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
502 - When weighting bridges during path selection, we used to trust
503 the bandwidths they provided in their descriptor, only capping them
504 at 10MB/s. This turned out to be problematic for two reasons:
505 Bridges could claim to handle a lot more traffic then they
506 actually would, thus making more clients pick them and have a
507 pretty effective DoS attack. The other issue is that new bridges
508 that might not have a good estimate for their bw capacity yet
509 would not get used at all unless no other bridges are available
510 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
512 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
513 - Ignore cannibalized circuits when recording circuit build times.
514 This should provide for a minor performance improvement for hidden
515 service users using 0.2.2.14-alpha, and should remove two spurious
516 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
517 - Simplify the logic that causes us to decide if the network is
518 unavailable for purposes of recording circuit build times. If we
519 receive no cells whatsoever for the entire duration of a circuit's
520 full measured lifetime, the network is probably down. Also ignore
521 one-hop directory fetching circuit timeouts when calculating our
522 circuit build times. These changes should hopefully reduce the
523 cases where we see ridiculous circuit build timeouts for people
524 with spotty wireless connections. Fixes part of bug 1772; bugfix
526 - Prevent the circuit build timeout from becoming larger than
527 the maximum build time we have ever seen. Also, prevent the time
528 period for measurement circuits from becoming larger than twice that
529 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
532 - When we run out of directory information such that we can't build
533 circuits, but then get enough that we can build circuits, log when
534 we actually construct a circuit, so the user has a better chance of
535 knowing what's going on. Fixes bug 1362.
536 - Be more generous with how much bandwidth we'd use up (with
537 accounting enabled) before entering "soft hibernation". Previously,
538 we'd refuse new connections and circuits once we'd used up 95% of
539 our allotment. Now, we use up 95% of our allotment, AND make sure
540 that we have no more than 500MB (or 3 hours of expected traffic,
541 whichever is lower) remaining before we enter soft hibernation.
542 - If we've configured EntryNodes and our network goes away and/or all
543 our entrynodes get marked down, optimistically retry them all when
544 a new socks application request appears. Fixes bug 1882.
545 - Add some more defensive programming for architectures that can't
546 handle unaligned integer accesses. We don't know of any actual bugs
547 right now, but that's the best time to fix them. Fixes bug 1943.
548 - Support line continuations in the torrc config file. If a line
549 ends with a single backslash character, the newline is ignored, and
550 the configuration value is treated as continuing on the next line.
553 o Minor bugfixes (on 0.2.1.x and earlier):
554 - For bandwidth accounting, calculate our expected bandwidth rate
555 based on the time during which we were active and not in
556 soft-hibernation during the last interval. Previously, we were
557 also considering the time spent in soft-hibernation. If this
558 was a long time, we would wind up underestimating our bandwidth
559 by a lot, and skewing our wakeup time towards the start of the
560 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
562 o Minor bugfixes (on 0.2.2.x):
563 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
564 which were disabled by the circuit build timeout changes in
565 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
566 - Make sure we don't warn about missing bandwidth weights when
567 choosing bridges or other relays not in the consensus. Bugfix on
568 0.2.2.10-alpha; fixes bug 1805.
569 - In our logs, do not double-report signatures from unrecognized
570 authorities both as "from unknown authority" and "not
571 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
574 Changes in version 0.2.2.16-alpha - 2010-09-17
575 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
576 evident at exit relays), and also continues to resolve all the little
577 bugs that have been filling up trac lately.
579 o Major bugfixes (stream-level fairness):
580 - When receiving a circuit-level SENDME for a blocked circuit, try
581 to package cells fairly from all the streams that had previously
582 been blocked on that circuit. Previously, we had started with the
583 oldest stream, and allowed each stream to potentially exhaust
584 the circuit's package window. This gave older streams on any
585 given circuit priority over newer ones. Fixes bug 1937. Detected
586 originally by Camilo Viecco. This bug was introduced before the
587 first Tor release, in svn commit r152: it is the new winner of
588 the longest-lived bug prize.
589 - When the exit relay got a circuit-level sendme cell, it started
590 reading on the exit streams, even if had 500 cells queued in the
591 circuit queue already, so the circuit queue just grew and grew in
592 some cases. We fix this by not re-enabling reading on receipt of a
593 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
594 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
596 - Newly created streams were allowed to read cells onto circuits,
597 even if the circuit's cell queue was blocked and waiting to drain.
598 This created potential unfairness, as older streams would be
599 blocked, but newer streams would gladly fill the queue completely.
600 We add code to detect this situation and prevent any stream from
601 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
605 - Update to the September 1 2010 Maxmind GeoLite Country database.
606 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
607 not. This would lead to a cookie that is still not group readable.
608 Closes bug 1843. Suggested by katmagic.
609 - When logging a rate-limited warning, we now mention how many messages
610 got suppressed since the last warning.
611 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
612 do individual connection-level rate limiting of clients. The torrc
613 config options with the same names trump the consensus params, if
614 both are present. Replaces the old "bwconnrate" and "bwconnburst"
615 consensus params which were broken from 0.2.2.7-alpha through
616 0.2.2.14-alpha. Closes bug 1947.
617 - When a router changes IP address or port, authorities now launch
618 a new reachability test for it. Implements ticket 1899.
619 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
620 2 no signature, 4 required" messages about consensus signatures
621 easier to read, and make sure they get logged at the same severity
622 as the messages explaining which keys are which. Fixes bug 1290.
623 - Don't warn when we have a consensus that we can't verify because
624 of missing certificates, unless those certificates are ones
625 that we have been trying and failing to download. Fixes bug 1145.
626 - If you configure your bridge with a known identity fingerprint,
627 and the bridge authority is unreachable (as it is in at least
628 one country now), fall back to directly requesting the descriptor
629 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
631 - When building with --enable-gcc-warnings on OpenBSD, disable
632 warnings in system headers. This makes --enable-gcc-warnings
635 o Minor bugfixes (on 0.2.1.x and earlier):
636 - Authorities will now attempt to download consensuses if their
637 own efforts to make a live consensus have failed. This change
638 means authorities that restart will fetch a valid consensus, and
639 it means authorities that didn't agree with the current consensus
640 will still fetch and serve it if it has enough signatures. Bugfix
641 on 0.2.0.9-alpha; fixes bug 1300.
642 - Ensure DNS requests launched by "RESOLVE" commands from the
643 controller respect the __LeaveStreamsUnattached setconf options. The
644 same goes for requests launched via DNSPort or transparent
645 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
646 - Allow handshaking OR connections to take a full KeepalivePeriod
647 seconds to handshake. Previously, we would close them after
648 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
649 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
651 - Rate-limit "Failed to hand off onionskin" warnings.
652 - Never relay a cell for a circuit we have already destroyed.
653 Between marking a circuit as closeable and finally closing it,
654 it may have been possible for a few queued cells to get relayed,
655 even though they would have been immediately dropped by the next
656 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
657 - Never queue a cell for a circuit that's already been marked
659 - Never vote for a server as "Running" if we have a descriptor for
660 it claiming to be hibernating, and that descriptor was published
661 more recently than our last contact with the server. Bugfix on
662 0.2.0.3-alpha; fixes bug 911.
663 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
666 o Minor bugfixes (on 0.2.2.x):
667 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
668 down if a directory fetch fails and you've configured either
669 bridges or EntryNodes. The intent was to mark the relay as down
670 _unless_ you're using bridges or EntryNodes, since if you are
671 then you could quickly run out of entry points.
672 - Fix the Windows directory-listing code. A bug introduced in
673 0.2.2.14-alpha could make Windows directory servers forget to load
674 some of their cached v2 networkstatus files.
675 - Really allow clients to use relays as bridges. Fixes bug 1776;
676 bugfix on 0.2.2.15-alpha.
677 - Demote a warn to info that happens when the CellStatistics option
678 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
679 Reported by Moritz Bartl.
680 - On Windows, build correctly either with or without Unicode support.
681 This is necessary so that Tor can support fringe platforms like
682 Windows 98 (which has no Unicode), or Windows CE (which has no
683 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
686 - Add a unit test for cross-platform directory-listing code.
689 Changes in version 0.2.2.15-alpha - 2010-08-18
690 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
691 fixes a variety of other bugs that were preventing performance
692 experiments from moving forward, fixes several bothersome memory leaks,
693 and generally closes a lot of smaller bugs that have been filling up
697 - Stop assigning the HSDir flag to relays that disable their
698 DirPort (and thus will refuse to answer directory requests). This
699 fix should dramatically improve the reachability of hidden services:
700 hidden services and hidden service clients pick six HSDir relays
701 to store and retrieve the hidden service descriptor, and currently
702 about half of the HSDir relays will refuse to work. Bugfix on
703 0.2.0.10-alpha; fixes part of bug 1693.
704 - The PerConnBWRate and Burst config options, along with the
705 bwconnrate and bwconnburst consensus params, initialized each conn's
706 token bucket values only when the connection is established. Now we
707 update them if the config options change, and update them every time
708 we get a new consensus. Otherwise we can encounter an ugly edge
709 case where we initialize an OR conn to client-level bandwidth,
710 but then later the relay joins the consensus and we leave it
711 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
712 - Fix a regression that caused Tor to rebind its ports if it receives
713 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
716 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
717 should give us approximately 40-50% more Guard-flagged nodes,
718 improving the anonymity the Tor network can provide and also
719 decreasing the dropoff in throughput that relays experience when
720 they first get the Guard flag.
721 - Allow enabling or disabling the *Statistics config options while
725 - Update to the August 1 2010 Maxmind GeoLite Country database.
726 - Have the controller interface give a more useful message than
727 "Internal Error" in response to failed GETINFO requests.
728 - Warn when the same option is provided more than once in a torrc
729 file, on the command line, or in a single SETCONF statement, and
730 the option is one that only accepts a single line. Closes bug 1384.
731 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
732 Patch from mingw-san.
733 - Add support for the country code "{??}" in torrc options like
734 ExcludeNodes, to indicate all routers of unknown country. Closes
736 - Relays report the number of bytes spent on answering directory
737 requests in extra-info descriptors similar to {read,write}-history.
738 Implements enhancement 1790.
740 o Minor bugfixes (on 0.2.1.x and earlier):
741 - Complain if PublishServerDescriptor is given multiple arguments that
742 include 0 or 1. This configuration will be rejected in the future.
743 Bugfix on 0.2.0.1-alpha; closes bug 1107.
744 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
745 Bugfix on 0.2.0.13-alpha; closes bug 928.
746 - Change "Application request when we're believed to be offline."
747 notice to "Application request when we haven't used client
748 functionality lately.", to clarify that it's not an error. Bugfix
749 on 0.0.9.3; fixes bug 1222.
750 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
751 would return "551 Internal error" rather than "552 Unrecognized key
752 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
753 - Users can't configure a regular relay to be their bridge. It didn't
754 work because when Tor fetched the bridge descriptor, it found
755 that it already had it, and didn't realize that the purpose of the
756 descriptor had changed. Now we replace routers with a purpose other
757 than bridge with bridge descriptors when fetching them. Bugfix on
758 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
759 refetch the descriptor with router purpose 'general', disabling
761 - Fix a rare bug in rend_fn unit tests: we would fail a test when
762 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
763 on 0.2.0.10-alpha; fixes bug 1808.
764 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
765 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
766 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
767 Servers can start sending this code when enough clients recognize
768 it. Also update the spec to reflect this new reason. Bugfix on
769 0.1.0.1-rc; fixes part of bug 1793.
770 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
771 when we switch from being a public relay to a bridge. Otherwise
772 there will still be clients that see the relay in their consensus,
773 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
775 - Instead of giving an assertion failure on an internal mismatch
776 on estimated freelist size, just log a BUG warning and try later.
777 Mitigates but does not fix bug 1125.
778 - Fix an assertion failure that could occur in caches or bridge users
779 when using a very short voting interval on a testing network.
780 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
782 o Minor bugfixes (on 0.2.2.x):
783 - Alter directory authorities to always consider Exit-flagged nodes
784 as potential Guard nodes in their votes. The actual decision to
785 use Exits as Guards is done in the consensus bandwidth weights.
786 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
787 - When the controller is reporting the purpose of circuits that
788 didn't finish building before the circuit build timeout, it was
789 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
790 - Our libevent version parsing code couldn't handle versions like
791 1.4.14b-stable and incorrectly warned the user about using an
792 old and broken version of libevent. Treat 1.4.14b-stable like
793 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
795 - Don't use substitution references like $(VAR:MOD) when
796 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
797 '$(:x)' to 'x' rather than the empty string. This bites us in
798 doc/ when configured with --disable-asciidoc. Bugfix on
799 0.2.2.9-alpha; fixes bug 1773.
800 - Remove a spurious hidden service server-side log notice about
801 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
803 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
805 - Correctly report written bytes on linked connections. Found while
806 implementing 1790. Bugfix on 0.2.2.4-alpha.
807 - Fix three memory leaks: one in circuit_build_times_parse_state(),
808 one in dirvote_add_signatures_to_pending_consensus(), and one every
809 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
810 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
812 o Code simplifications and refactoring:
813 - Take a first step towards making or.h smaller by splitting out
814 function definitions for all source files in src/or/. Leave
815 structures and defines in or.h for now.
816 - Remove a bunch of unused function declarations as well as a block of
817 #if 0'd code from the unit tests. Closes bug 1824.
818 - New unit tests for exit-port history statistics; refactored exit
819 statistics code to be more easily tested.
820 - Remove the old debian/ directory from the main Tor distribution.
821 The official Tor-for-debian git repository lives at the URL
822 https://git.torproject.org/debian/tor.git
825 Changes in version 0.2.2.14-alpha - 2010-07-12
826 Tor 0.2.2.14-alpha greatly improves client-side handling of
827 circuit build timeouts, which are used to estimate speed and improve
828 performance. We also move to a much better GeoIP database, port Tor to
829 Windows CE, introduce new compile flags that improve code security,
830 add an eighth v3 directory authority, and address a lot of more
834 - Tor directory authorities no longer crash when started with a
835 cached-microdesc-consensus file in their data directory. Bugfix
836 on 0.2.2.6-alpha; fixes bug 1532.
837 - Treat an unset $HOME like an empty $HOME rather than triggering an
838 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
839 - Ignore negative and large circuit build timeout values that can
840 happen during a suspend or hibernate. These values caused various
841 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
842 - Alter calculation of Pareto distribution parameter 'Xm' for
843 Circuit Build Timeout learning to use the weighted average of the
844 top N=3 modes (because we have three entry guards). Considering
845 multiple modes should improve the timeout calculation in some cases,
846 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
848 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
849 right censored distribution model. This approach improves over the
850 synthetic timeout generation approach that was producing insanely
851 high timeout values. Now we calculate build timeouts using truncated
852 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
853 - Do not close circuits that are under construction when they reach
854 the circuit build timeout. Instead, leave them building (but do not
855 use them) for up until the time corresponding to the 95th percentile
856 on the Pareto CDF or 60 seconds, whichever is greater. This is done
857 to provide better data for the new Pareto model. This percentile
858 can be controlled by the consensus.
861 - Move to the June 2010 Maxmind GeoLite country db (rather than the
862 June 2009 ip-to-country GeoIP db) for our statistics that count
863 how many users relays are seeing from each country. Now we have
864 more accurate data for many African countries.
865 - Port Tor to build and run correctly on Windows CE systems, using
866 the wcecompat library. Contributed by Valerio Lupi.
867 - New "--enable-gcc-hardening" ./configure flag (off by default)
868 to turn on gcc compile time hardening options. It ensures
869 that signed ints have defined behavior (-fwrapv), enables
870 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
871 with canaries (-fstack-protector-all), turns on ASLR protection if
872 supported by the kernel (-fPIE, -pie), and adds additional security
873 related warnings. Verified to work on Mac OS X and Debian Lenny.
874 - New "--enable-linker-hardening" ./configure flag (off by default)
875 to turn on ELF specific hardening features (relro, now). This does
876 not work with Mac OS X or any other non-ELF binary format.
878 o New directory authorities:
879 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
883 - New config option "WarnUnsafeSocks 0" disables the warning that
884 occurs whenever Tor receives only an IP address instead of a
885 hostname. Setups that do DNS locally over Tor are fine, and we
886 shouldn't spam the logs in that case.
887 - Convert the HACKING file to asciidoc, and add a few new sections
888 to it, explaining how we use Git, how we make changelogs, and
889 what should go in a patch.
890 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
891 event, to give information on the current rate of circuit timeouts
892 over our stored history.
893 - Add ability to disable circuit build time learning via consensus
894 parameter and via a LearnCircuitBuildTimeout config option. Also
895 automatically disable circuit build time calculation if we are
896 either a AuthoritativeDirectory, or if we fail to write our state
897 file. Fixes bug 1296.
898 - More gracefully handle corrupt state files, removing asserts
899 in favor of saving a backup and resetting state.
900 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
904 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
906 - When a2x fails, mention that the user could disable manpages instead
907 of trying to fix their asciidoc installation.
908 - Where available, use Libevent 2.0's periodic timers so that our
909 once-per-second cleanup code gets called even more closely to
910 once per second than it would otherwise. Fixes bug 943.
911 - If you run a bridge that listens on multiple IP addresses, and
912 some user configures a bridge address that uses a different IP
913 address than your bridge writes in its router descriptor, and the
914 user doesn't specify an identity key, their Tor would discard the
915 descriptor because "it isn't one of our configured bridges", and
916 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
917 Bugfix on 0.2.0.3-alpha.
918 - If OpenSSL fails to make a duplicate of a private or public key, log
919 an error message and try to exit cleanly. May help with debugging
920 if bug 1209 ever remanifests.
921 - Save a couple bytes in memory allocation every time we escape
922 certain characters in a string. Patch from Florian Zumbiehl.
923 - Make it explicit that we don't cannibalize one-hop circuits. This
924 happens in the wild, but doesn't turn out to be a problem because
925 we fortunately don't use those circuits. Many thanks to outofwords
926 for the initial analysis and to swissknife who confirmed that
927 two-hop circuits are actually created.
928 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
929 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
930 - Eliminate a case where a circuit build time warning was displayed
931 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
934 Changes in version 0.2.1.26 - 2010-05-02
935 Tor 0.2.1.26 addresses the recent connection and memory overload
936 problems we've been seeing on relays, especially relays with their
937 DirPort open. If your relay has been crashing, or you turned it off
938 because it used too many resources, give this release a try.
940 This release also fixes yet another instance of broken OpenSSL libraries
941 that was causing some relays to drop out of the consensus.
944 - Teach relays to defend themselves from connection overload. Relays
945 now close idle circuits early if it looks like they were intended
946 for directory fetches. Relays are also more aggressive about closing
947 TLS connections that have no circuits on them. Such circuits are
948 unlikely to be re-used, and tens of thousands of them were piling
949 up at the fast relays, causing the relays to run out of sockets
950 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
951 their directory fetches over TLS).
952 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
953 that claim to be earlier than 0.9.8m, but which have in reality
954 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
955 behavior. Possible fix for some cases of bug 1346.
956 - Directory mirrors were fetching relay descriptors only from v2
957 directory authorities, rather than v3 authorities like they should.
958 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
959 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
962 - Finally get rid of the deprecated and now harmful notion of "clique
963 mode", where directory authorities maintain TLS connections to
967 - In the util/threads test, no longer free the test_mutex before all
968 worker threads have finished. Bugfix on 0.2.1.6-alpha.
969 - The master thread could starve the worker threads quite badly on
970 certain systems, causing them to run only partially in the allowed
971 window. This resulted in test failures. Now the master thread sleeps
972 occasionally for a few microseconds while the two worker-threads
973 compete for the mutex. Bugfix on 0.2.0.1-alpha.
976 Changes in version 0.2.2.13-alpha - 2010-04-24
977 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
978 problems we've been seeing on relays, especially relays with their
979 DirPort open. If your relay has been crashing, or you turned it off
980 because it used too many resources, give this release a try.
983 - Teach relays to defend themselves from connection overload. Relays
984 now close idle circuits early if it looks like they were intended
985 for directory fetches. Relays are also more aggressive about closing
986 TLS connections that have no circuits on them. Such circuits are
987 unlikely to be re-used, and tens of thousands of them were piling
988 up at the fast relays, causing the relays to run out of sockets
989 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
990 their directory fetches over TLS).
993 - Finally get rid of the deprecated and now harmful notion of "clique
994 mode", where directory authorities maintain TLS connections to
996 - Directory authorities now do an immediate reachability check as soon
997 as they hear about a new relay. This change should slightly reduce
998 the time between setting up a relay and getting listed as running
999 in the consensus. It should also improve the time between setting
1000 up a bridge and seeing use by bridge users.
1001 - Directory authorities no longer launch a TLS connection to every
1002 relay as they startup. Now that we have 2k+ descriptors cached,
1003 the resulting network hiccup is becoming a burden. Besides,
1004 authorities already avoid voting about Running for the first half
1005 hour of their uptime.
1008 Changes in version 0.2.2.12-alpha - 2010-04-20
1009 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
1010 handle and vote on descriptors. It was causing relays to drop out of
1014 - Many relays have been falling out of the consensus lately because
1015 not enough authorities know about their descriptor for them to get
1016 a majority of votes. When we deprecated the v2 directory protocol,
1017 we got rid of the only way that v3 authorities can hear from each
1018 other about other descriptors. Now authorities examine every v3
1019 vote for new descriptors, and fetch them from that authority. Bugfix
1021 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
1022 and a warning in or.h related to bandwidth_weight_rule_t that
1023 prevented clean compile on OS X. Fixes bug 1363; bugfix on
1025 - Fix a segfault on relays when DirReqStatistics is enabled
1026 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
1030 - Demote a confusing TLS warning that relay operators might get when
1031 someone tries to talk to their OrPort. It is neither the operator's
1032 fault nor can they do anything about it. Fixes bug 1364; bugfix
1036 Changes in version 0.2.2.11-alpha - 2010-04-15
1037 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
1038 libraries that was causing some relays to drop out of the consensus.
1041 - Directory mirrors were fetching relay descriptors only from v2
1042 directory authorities, rather than v3 authorities like they should.
1043 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
1044 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
1045 - Fix a parsing error that made every possible value of
1046 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
1047 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
1048 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
1049 about the option without breaking older ones.
1050 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
1051 that claim to be earlier than 0.9.8m, but which have in reality
1052 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
1053 behavior. Possible fix for some cases of bug 1346.
1056 - Experiment with a more aggressive approach to preventing clients
1057 from making one-hop exit streams. Exit relays who want to try it
1058 out can set "RefuseUnknownExits 1" in their torrc, and then look
1059 for "Attempt by %s to open a stream" log messages. Let us know
1061 - Add support for statically linking zlib by specifying
1062 --enable-static-zlib, to go with our support for statically linking
1063 openssl and libevent. Resolves bug 1358.
1066 - Fix a segfault that happens whenever a Tor client that is using
1067 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
1069 - When we cleaned up the contrib/tor-exit-notice.html file, we left
1070 out the first line. Fixes bug 1295.
1071 - When building the manpage from a tarball, we required asciidoc, but
1072 the asciidoc -> roff/html conversion was already done for the
1073 tarball. Make 'make' complain only when we need asciidoc (either
1074 because we're compiling directly from git, or because we altered
1075 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
1076 - When none of the directory authorities vote on any params, Tor
1077 segfaulted when trying to make the consensus from the votes. We
1078 didn't trigger the bug in practice, because authorities do include
1079 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
1082 - In the util/threads test, no longer free the test_mutex before all
1083 worker threads have finished. Bugfix on 0.2.1.6-alpha.
1084 - The master thread could starve the worker threads quite badly on
1085 certain systems, causing them to run only partially in the allowed
1086 window. This resulted in test failures. Now the master thread sleeps
1087 occasionally for a few microseconds while the two worker-threads
1088 compete for the mutex. Bugfix on 0.2.0.1-alpha.
1091 Changes in version 0.2.2.10-alpha - 2010-03-07
1092 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
1093 could prevent relays from guessing their IP address correctly. It also
1094 starts the groundwork for another client-side performance boost, since
1095 currently we're not making efficient use of relays that have both the
1096 Guard flag and the Exit flag.
1099 - Fix a regression from our patch for bug 1244 that caused relays
1100 to guess their IP address incorrectly if they didn't set Address
1101 in their torrc and/or their address fails to resolve. Bugfix on
1102 0.2.2.9-alpha; fixes bug 1269.
1104 o Major features (performance):
1105 - Directory authorities now compute consensus weightings that instruct
1106 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
1107 and no flag. Clients that use these weightings will distribute
1108 network load more evenly across these different relay types. The
1109 weightings are in the consensus so we can change them globally in
1110 the future. Extra thanks to "outofwords" for finding some nasty
1111 security bugs in the first implementation of this feature.
1113 o Minor features (performance):
1114 - Always perform router selections using weighted relay bandwidth,
1115 even if we don't need a high capacity circuit at the time. Non-fast
1116 circuits now only differ from fast ones in that they can use relays
1117 not marked with the Fast flag. This "feature" could turn out to
1118 be a horrible bug; we should investigate more before it goes into
1122 - Allow disabling building of the manpages. Skipping the manpage
1123 speeds up the build considerably.
1125 o Minor bugfixes (on 0.2.2.x):
1126 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
1127 Bugfix on 0.2.2.9-alpha.
1128 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
1129 config option. Bugfix on 0.2.2.7-alpha.
1130 - Ship the asciidoc-helper file in the tarball, so that people can
1131 build from source if they want to, and touching the .1.txt files
1132 doesn't break the build. Bugfix on 0.2.2.9-alpha.
1134 o Minor bugfixes (on 0.2.1.x or earlier):
1135 - Fix a dereference-then-NULL-check sequence when publishing
1136 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
1138 - Fix another dereference-then-NULL-check sequence. Bugfix on
1139 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
1140 - Make sure we treat potentially not NUL-terminated strings correctly.
1141 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
1143 o Code simplifications and refactoring:
1144 - Fix some urls in the exit notice file and make it XHTML1.1 strict
1145 compliant. Based on a patch from Christian Kujau.
1146 - Don't use sed in asciidoc-helper anymore.
1147 - Make the build process fail if asciidoc cannot be found and
1148 building with asciidoc isn't disabled.
1151 Changes in version 0.2.2.9-alpha - 2010-02-22
1152 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
1153 location of a directory authority, and cleans up a bunch of small bugs.
1155 o Directory authority changes:
1156 - Change IP address for dannenberg (v3 directory authority), and
1157 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
1158 service directory authority) from the list.
1161 - Make Tor work again on the latest OS X: when deciding whether to
1162 use strange flags to turn TLS renegotiation on, detect the OpenSSL
1163 version at run-time, not compile time. We need to do this because
1164 Apple doesn't update its dev-tools headers when it updates its
1165 libraries in a security patch.
1166 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
1167 that could happen on 32-bit platforms with 64-bit time_t. Also fix
1168 a memory leak when requesting a hidden service descriptor we've
1169 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
1171 - Authorities could be tricked into giving out the Exit flag to relays
1172 that didn't allow exiting to any ports. This bug could screw
1173 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
1174 1238. Bug discovered by Martin Kowalczyk.
1175 - When freeing a session key, zero it out completely. We only zeroed
1176 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
1177 patched by ekir. Fixes bug 1254.
1180 - Fix static compilation by listing the openssl libraries in the right
1181 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
1182 - Resume handling .exit hostnames in a special way: originally we
1183 stripped the .exit part and used the requested exit relay. In
1184 0.2.2.1-alpha we stopped treating them in any special way, meaning
1185 if you use a .exit address then Tor will pass it on to the exit
1186 relay. Now we reject the .exit stream outright, since that behavior
1187 might be more expected by the user. Found and diagnosed by Scott
1188 Bennett and Downie on or-talk.
1189 - Don't spam the controller with events when we have no file
1190 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
1191 for log messages was already solved from bug 748.)
1192 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
1194 - Make the DNSPort option work with libevent 2.x. Don't alter the
1195 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
1196 - Emit a GUARD DROPPED controller event for a case we missed.
1197 - Make more fields in the controller protocol case-insensitive, since
1198 control-spec.txt said they were.
1199 - Refactor resolve_my_address() to not use gethostbyname() anymore.
1200 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
1201 - Fix a spec conformance issue: the network-status-version token
1202 must be the first token in a v3 consensus or vote. Discovered by
1203 parakeep. Bugfix on 0.2.0.3-alpha.
1205 o Code simplifications and refactoring:
1206 - Generate our manpage and HTML documentation using Asciidoc. This
1207 change should make it easier to maintain the documentation, and
1209 - Remove the --enable-iphone option. According to reports from Marco
1210 Bonetti, Tor builds fine without any special tweaking on recent
1211 iPhone SDK versions.
1212 - Removed some unnecessary files from the source distribution. The
1213 AUTHORS file has now been merged into the people page on the
1214 website. The roadmaps and design doc can now be found in the
1215 projects directory in svn.
1216 - Enabled various circuit build timeout constants to be controlled
1217 by consensus parameters. Also set better defaults for these
1218 parameters based on experimentation on broadband and simulated
1222 - The 'EXTENDCIRCUIT' control port command can now be used with
1223 a circ id of 0 and no path. This feature will cause Tor to build
1224 a new 'fast' general purpose circuit using its own path selection
1226 - Added a BUILDTIMEOUT_SET controller event to describe changes
1227 to the circuit build timeout.
1228 - Future-proof the controller protocol a bit by ignoring keyword
1229 arguments we do not recognize.
1230 - Expand homedirs passed to tor-checkkey. This should silence a
1231 coverity complaint about passing a user-supplied string into
1232 open() without checking it.
1235 Changes in version 0.2.1.25 - 2010-03-16
1236 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
1237 prevent relays from guessing their IP address correctly. It also fixes
1238 several minor potential security bugs.
1241 - Fix a regression from our patch for bug 1244 that caused relays
1242 to guess their IP address incorrectly if they didn't set Address
1243 in their torrc and/or their address fails to resolve. Bugfix on
1244 0.2.1.23; fixes bug 1269.
1245 - When freeing a session key, zero it out completely. We only zeroed
1246 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
1247 patched by ekir. Fixes bug 1254.
1250 - Fix a dereference-then-NULL-check sequence when publishing
1251 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
1253 - Fix another dereference-then-NULL-check sequence. Bugfix on
1254 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
1255 - Make sure we treat potentially not NUL-terminated strings correctly.
1256 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
1260 Changes in version 0.2.1.24 - 2010-02-21
1261 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
1265 - Work correctly out-of-the-box with even more vendor-patched versions
1266 of OpenSSL. In particular, make it so Debian and OS X don't need
1267 customized patches to run/build.
1270 Changes in version 0.2.1.23 - 2010-02-13
1271 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
1272 again on the latest OS X, and updates the location of a directory
1275 o Major bugfixes (performance):
1276 - We were selecting our guards uniformly at random, and then weighting
1277 which of our guards we'd use uniformly at random. This imbalance
1278 meant that Tor clients were severely limited on throughput (and
1279 probably latency too) by the first hop in their circuit. Now we
1280 select guards weighted by currently advertised bandwidth. We also
1281 automatically discard guards picked using the old algorithm. Fixes
1282 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
1285 - Make Tor work again on the latest OS X: when deciding whether to
1286 use strange flags to turn TLS renegotiation on, detect the OpenSSL
1287 version at run-time, not compile time. We need to do this because
1288 Apple doesn't update its dev-tools headers when it updates its
1289 libraries in a security patch.
1290 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
1291 that could happen on 32-bit platforms with 64-bit time_t. Also fix
1292 a memory leak when requesting a hidden service descriptor we've
1293 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
1296 o Directory authority changes:
1297 - Change IP address for dannenberg (v3 directory authority), and
1298 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
1299 service directory authority) from the list.
1302 - Refactor resolve_my_address() to not use gethostbyname() anymore.
1303 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
1306 - Avoid a mad rush at the beginning of each month when each client
1307 rotates half of its guards. Instead we spread the rotation out
1308 throughout the month, but we still avoid leaving a precise timestamp
1309 in the state file about when we first picked the guard. Improves
1310 over the behavior introduced in 0.1.2.17.
1313 Changes in version 0.2.2.8-alpha - 2010-01-26
1314 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
1315 causing bridge relays to disappear. If you're running a bridge,
1319 - Fix a memory corruption bug on bridges that occured during the
1320 inclusion of stats data in extra-info descriptors. Also fix the
1321 interface for geoip_get_bridge_stats* to prevent similar bugs in
1322 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
1323 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
1326 - Ignore OutboundBindAddress when connecting to localhost.
1327 Connections to localhost need to come _from_ localhost, or else
1328 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
1332 Changes in version 0.2.2.7-alpha - 2010-01-19
1333 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
1334 as laying the groundwork for further relay-side performance fixes. It
1335 also starts cleaning up client behavior with respect to the EntryNodes,
1336 ExitNodes, and StrictNodes config options.
1338 This release also rotates two directory authority keys, due to a
1339 security breach of some of the Torproject servers.
1341 o Directory authority changes:
1342 - Rotate keys (both v3 identity and relay identity) for moria1
1345 o Major features (performance):
1346 - We were selecting our guards uniformly at random, and then weighting
1347 which of our guards we'd use uniformly at random. This imbalance
1348 meant that Tor clients were severely limited on throughput (and
1349 probably latency too) by the first hop in their circuit. Now we
1350 select guards weighted by currently advertised bandwidth. We also
1351 automatically discard guards picked using the old algorithm. Fixes
1352 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
1353 - When choosing which cells to relay first, relays can now favor
1354 circuits that have been quiet recently, to provide lower latency
1355 for low-volume circuits. By default, relays enable or disable this
1356 feature based on a setting in the consensus. You can override
1357 this default by using the new "CircuitPriorityHalflife" config
1358 option. Design and code by Ian Goldberg, Can Tang, and Chris
1360 - Add separate per-conn write limiting to go with the per-conn read
1361 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
1362 but never per-conn write limits.
1363 - New consensus params "bwconnrate" and "bwconnburst" to let us
1364 rate-limit client connections as they enter the network. It's
1365 controlled in the consensus so we can turn it on and off for
1366 experiments. It's starting out off. Based on proposal 163.
1368 o Major features (relay selection options):
1369 - Switch to a StrictNodes config option, rather than the previous
1370 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
1371 "StrictExcludeNodes" option.
1372 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
1373 change during a config reload, mark and discard all our origin
1374 circuits. This fix should address edge cases where we change the
1375 config options and but then choose a circuit that we created before
1377 - If EntryNodes or ExitNodes are set, be more willing to use an
1378 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
1380 - Make EntryNodes config option much more aggressive even when
1381 StrictNodes is not set. Before it would prepend your requested
1382 entrynodes to your list of guard nodes, but feel free to use others
1383 after that. Now it chooses only from your EntryNodes if any of
1384 those are available, and only falls back to others if a) they're
1385 all down and b) StrictNodes is not set.
1386 - Now we refresh your entry guards from EntryNodes at each consensus
1387 fetch -- rather than just at startup and then they slowly rot as
1388 the network changes.
1391 - Stop bridge directory authorities from answering dbg-stability.txt
1392 directory queries, which would let people fetch a list of all
1393 bridge identities they track. Bugfix on 0.2.1.6-alpha.
1396 - Log a notice when we get a new control connection. Now it's easier
1397 for security-conscious users to recognize when a local application
1398 is knocking on their controller door. Suggested by bug 1196.
1399 - New config option "CircuitStreamTimeout" to override our internal
1400 timeout schedule for how many seconds until we detach a stream from
1401 a circuit and try a new circuit. If your network is particularly
1402 slow, you might want to set this to a number like 60.
1403 - New controller command "getinfo config-text". It returns the
1404 contents that Tor would write if you send it a SAVECONF command,
1405 so the controller can write the file to disk itself.
1406 - New options for SafeLogging to allow scrubbing only log messages
1407 generated while acting as a relay.
1408 - Ship the bridges spec file in the tarball too.
1409 - Avoid a mad rush at the beginning of each month when each client
1410 rotates half of its guards. Instead we spread the rotation out
1411 throughout the month, but we still avoid leaving a precise timestamp
1412 in the state file about when we first picked the guard. Improves
1413 over the behavior introduced in 0.1.2.17.
1415 o Minor bugfixes (compiling):
1416 - Fix compilation on OS X 10.3, which has a stub mlockall() but
1417 hides it. Bugfix on 0.2.2.6-alpha.
1418 - Fix compilation on Solaris by removing support for the
1419 DisableAllSwap config option. Solaris doesn't have an rlimit for
1420 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
1423 o Minor bugfixes (crashes):
1424 - Do not segfault when writing buffer stats when we haven't observed
1425 a single circuit to report about. Found by Fabian Lanze. Bugfix on
1427 - If we're in the pathological case where there's no exit bandwidth
1428 but there is non-exit bandwidth, or no guard bandwidth but there
1429 is non-guard bandwidth, don't crash during path selection. Bugfix
1431 - Fix an impossible-to-actually-trigger buffer overflow in relay
1432 descriptor generation. Bugfix on 0.1.0.15.
1434 o Minor bugfixes (privacy):
1435 - Fix an instance where a Tor directory mirror might accidentally
1436 log the IP address of a misbehaving Tor client. Bugfix on
1438 - Don't list Windows capabilities in relay descriptors. We never made
1439 use of them, and maybe it's a bad idea to publish them. Bugfix
1442 o Minor bugfixes (other):
1443 - Resolve an edge case in path weighting that could make us misweight
1444 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
1445 - Fix statistics on client numbers by country as seen by bridges that
1446 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
1447 intervals instead of variable 12-to-48-hour intervals.
1448 - After we free an internal connection structure, overwrite it
1449 with a different memory value than we use for overwriting a freed
1450 internal circuit structure. Should help with debugging. Suggested
1452 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
1456 - Remove the HSAuthorityRecordStats option that version 0 hidden
1457 service authorities could have used to track statistics of overall
1458 hidden service usage.
1461 Changes in version 0.2.1.22 - 2010-01-19
1462 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
1463 authorities -- it would tell you its whole history of bridge descriptors
1464 if you make the right directory request. This stable update also
1465 rotates two of the seven v3 directory authority keys and locations.
1467 o Directory authority changes:
1468 - Rotate keys (both v3 identity and relay identity) for moria1
1472 - Stop bridge directory authorities from answering dbg-stability.txt
1473 directory queries, which would let people fetch a list of all
1474 bridge identities they track. Bugfix on 0.2.1.6-alpha.
1477 Changes in version 0.2.1.21 - 2009-12-21
1478 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
1479 library. If you use Tor on Linux / Unix and you're getting SSL
1480 renegotiation errors, upgrading should help. We also recommend an
1481 upgrade if you're an exit relay.
1484 - Work around a security feature in OpenSSL 0.9.8l that prevents our
1485 handshake from working unless we explicitly tell OpenSSL that we
1486 are using SSL renegotiation safely. We are, of course, but OpenSSL
1487 0.9.8l won't work unless we say we are.
1488 - Avoid crashing if the client is trying to upload many bytes and the
1489 circuit gets torn down at the same time, or if the flip side
1490 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
1493 - Do not refuse to learn about authority certs and v2 networkstatus
1494 documents that are older than the latest consensus. This bug might
1495 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
1496 Spotted and fixed by xmux.
1497 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
1498 trigger platform-specific option misparsing case found by Coverity
1500 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
1501 trigger assert. Fixes bug 1173.
1504 Changes in version 0.2.2.6-alpha - 2009-11-19
1505 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
1506 support for the new lower-footprint "microdescriptor" directory design,
1507 future-proofing our consensus format against new hash functions or
1508 other changes, and an Android port. It also makes Tor compatible with
1509 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
1512 - Directory authorities can now create, vote on, and serve multiple
1513 parallel formats of directory data as part of their voting process.
1514 Partially implements Proposal 162: "Publish the consensus in
1516 - Directory authorities can now agree on and publish small summaries
1517 of router information that clients can use in place of regular
1518 server descriptors. This transition will eventually allow clients
1519 to use far less bandwidth for downloading information about the
1520 network. Begins the implementation of Proposal 158: "Clients
1521 download consensus + microdescriptors".
1522 - The directory voting system is now extensible to use multiple hash
1523 algorithms for signatures and resource selection. Newer formats
1524 are signed with SHA256, with a possibility for moving to a better
1525 hash algorithm in the future.
1526 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
1527 current and future memory pages via mlockall(). On supported
1528 platforms (modern Linux and probably BSD but not Windows or OS X),
1529 this should effectively disable any and all attempts to page out
1530 memory. This option requires that you start your Tor as root --
1531 if you use DisableAllSwap, please consider using the User option
1532 to properly reduce the privileges of your Tor.
1533 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
1534 to help Tor build correctly for Android phones.
1537 - Work around a security feature in OpenSSL 0.9.8l that prevents our
1538 handshake from working unless we explicitly tell OpenSSL that we
1539 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
1540 won't work unless we say we are.
1543 - Fix a crash bug when trying to initialize the evdns module in
1544 Libevent 2. Bugfix on 0.2.1.16-rc.
1545 - Stop logging at severity 'warn' when some other Tor client tries
1546 to establish a circuit with us using weak DH keys. It's a protocol
1547 violation, but that doesn't mean ordinary users need to hear about
1548 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
1549 - Do not refuse to learn about authority certs and v2 networkstatus
1550 documents that are older than the latest consensus. This bug might
1551 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
1552 Spotted and fixed by xmux.
1553 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
1554 - If all authorities restart at once right before a consensus vote,
1555 nobody will vote about "Running", and clients will get a consensus
1556 with no usable relays. Instead, authorities refuse to build a
1557 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
1558 - If your relay can't keep up with the number of incoming create
1559 cells, it would log one warning per failure into your logs. Limit
1560 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
1561 - Bridges now use "reject *:*" as their default exit policy. Bugfix
1562 on 0.2.0.3-alpha; fixes bug 1113.
1563 - Fix a memory leak on directory authorities during voting that was
1564 introduced in 0.2.2.1-alpha. Found via valgrind.
1567 Changes in version 0.2.1.20 - 2009-10-15
1568 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
1569 services at once, prepares for more performance improvements, and
1570 fixes a bunch of smaller bugs.
1572 The Windows and OS X bundles also include a more recent Vidalia,
1573 and switch from Privoxy to Polipo.
1575 The OS X installers are now drag and drop. It's best to un-install
1576 Tor/Vidalia and then install this new bundle, rather than upgrade. If
1577 you want to upgrade, you'll need to update the paths for Tor and Polipo
1578 in the Vidalia Settings window.
1581 - Send circuit or stream sendme cells when our window has decreased
1582 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
1583 by Karsten when testing the "reduce circuit window" performance
1584 patch. Bugfix on the 54th commit on Tor -- from July 2002,
1585 before the release of Tor 0.0.0. This is the new winner of the
1587 - Fix a remotely triggerable memory leak when a consensus document
1588 contains more than one signature from the same voter. Bugfix on
1590 - Avoid segfault in rare cases when finishing an introduction circuit
1591 as a client and finding out that we don't have an introduction key
1592 for it. Fixes bug 1073. Reported by Aaron Swartz.
1595 - Tor now reads the "circwindow" parameter out of the consensus,
1596 and uses that value for its circuit package window rather than the
1597 default of 1000 cells. Begins the implementation of proposal 168.
1599 o New directory authorities:
1600 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
1602 - Move moria1 and tonga to alternate IP addresses.
1605 - Fix a signed/unsigned compile warning in 0.2.1.19.
1606 - Fix possible segmentation fault on directory authorities. Bugfix on
1608 - Fix an extremely rare infinite recursion bug that could occur if
1609 we tried to log a message after shutting down the log subsystem.
1610 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
1611 - Fix an obscure bug where hidden services on 64-bit big-endian
1612 systems might mis-read the timestamp in v3 introduce cells, and
1613 refuse to connect back to the client. Discovered by "rotor".
1614 Bugfix on 0.2.1.6-alpha.
1615 - We were triggering a CLOCK_SKEW controller status event whenever
1616 we connect via the v2 connection protocol to any relay that has
1617 a wrong clock. Instead, we should only inform the controller when
1618 it's a trusted authority that claims our clock is wrong. Bugfix
1619 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
1620 - We were telling the controller about CHECKING_REACHABILITY and
1621 REACHABILITY_FAILED status events whenever we launch a testing
1622 circuit or notice that one has failed. Instead, only tell the
1623 controller when we want to inform the user of overall success or
1624 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
1626 - Don't warn when we're using a circuit that ends with a node
1627 excluded in ExcludeExitNodes, but the circuit is not used to access
1628 the outside world. This should help fix bug 1090. Bugfix on
1630 - Work around a small memory leak in some versions of OpenSSL that
1631 stopped the memory used by the hostname TLS extension from being
1635 - Add a "getinfo status/accepted-server-descriptor" controller
1636 command, which is the recommended way for controllers to learn
1637 whether our server descriptor has been successfully received by at
1638 least on directory authority. Un-recommend good-server-descriptor
1639 getinfo and status events until we have a better design for them.
1642 Changes in version 0.2.2.5-alpha - 2009-10-11
1643 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
1646 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
1648 o New directory authorities:
1649 - Move dizum to an alternate IP address.
1652 Changes in version 0.2.2.4-alpha - 2009-10-10
1653 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
1654 introduces a new unit test framework, shifts directry authority
1655 addresses around to reduce the impact from recent blocking events,
1656 and fixes a few smaller bugs.
1659 - Fix several more asserts in the circuit_build_times code, for
1660 example one that causes Tor to fail to start once we have
1661 accumulated 5000 build times in the state file. Bugfixes on
1662 0.2.2.2-alpha; fixes bug 1108.
1664 o New directory authorities:
1665 - Move moria1 and Tonga to alternate IP addresses.
1668 - Log SSL state transitions at debug level during handshake, and
1669 include SSL states in error messages. This may help debug future
1670 SSL handshake issues.
1671 - Add a new "Handshake" log domain for activities that happen
1672 during the TLS handshake.
1673 - Revert to the "June 3 2009" ip-to-country file. The September one
1674 seems to have removed most US IP addresses.
1675 - Directory authorities now reject Tor relays with versions less than
1676 0.1.2.14. This step cuts out four relays from the current network,
1677 none of which are very big.
1680 - Fix a couple of smaller issues with gathering statistics. Bugfixes
1682 - Fix two memory leaks in the error case of
1683 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
1684 - Don't count one-hop circuits when we're estimating how long it
1685 takes circuits to build on average. Otherwise we'll set our circuit
1686 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
1687 - Directory authorities no longer change their opinion of, or vote on,
1688 whether a router is Running, unless they have themselves been
1689 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
1692 o Code simplifications and refactoring:
1693 - Revise our unit tests to use the "tinytest" framework, so we
1694 can run tests in their own processes, have smarter setup/teardown
1695 code, and so on. The unit test code has moved to its own
1696 subdirectory, and has been split into multiple modules.
1699 Changes in version 0.2.2.3-alpha - 2009-09-23
1700 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
1703 - Fix an overzealous assert in our new circuit build timeout code.
1704 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
1707 - If the networkstatus consensus tells us that we should use a
1708 negative circuit package window, ignore it. Otherwise we'll
1709 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
1712 Changes in version 0.2.2.2-alpha - 2009-09-21
1713 Tor 0.2.2.2-alpha introduces our latest performance improvement for
1714 clients: Tor tracks the average time it takes to build a circuit, and
1715 avoids using circuits that take too long to build. For fast connections,
1716 this feature can cut your expected latency in half. For slow or flaky
1717 connections, it could ruin your Tor experience. Let us know if it does!
1720 - Tor now tracks how long it takes to build client-side circuits
1721 over time, and adapts its timeout to local network performance.
1722 Since a circuit that takes a long time to build will also provide
1723 bad performance, we get significant latency improvements by
1724 discarding the slowest 20% of circuits. Specifically, Tor creates
1725 circuits more aggressively than usual until it has enough data
1726 points for a good timeout estimate. Implements proposal 151.
1727 We are especially looking for reports (good and bad) from users with
1728 both EDGE and broadband connections that can move from broadband
1729 to EDGE and find out if the build-time data in the .tor/state gets
1730 reset without loss of Tor usability. You should also see a notice
1731 log message telling you that Tor has reset its timeout.
1732 - Directory authorities can now vote on arbitary integer values as
1733 part of the consensus process. This is designed to help set
1734 network-wide parameters. Implements proposal 167.
1735 - Tor now reads the "circwindow" parameter out of the consensus,
1736 and uses that value for its circuit package window rather than the
1737 default of 1000 cells. Begins the implementation of proposal 168.
1740 - Fix a remotely triggerable memory leak when a consensus document
1741 contains more than one signature from the same voter. Bugfix on
1745 - Fix an extremely rare infinite recursion bug that could occur if
1746 we tried to log a message after shutting down the log subsystem.
1747 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
1748 - Fix parsing for memory or time units given without a space between
1749 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
1750 - A networkstatus vote must contain exactly one signature. Spec
1751 conformance issue. Bugfix on 0.2.0.3-alpha.
1752 - Fix an obscure bug where hidden services on 64-bit big-endian
1753 systems might mis-read the timestamp in v3 introduce cells, and
1754 refuse to connect back to the client. Discovered by "rotor".
1755 Bugfix on 0.2.1.6-alpha.
1756 - We were triggering a CLOCK_SKEW controller status event whenever
1757 we connect via the v2 connection protocol to any relay that has
1758 a wrong clock. Instead, we should only inform the controller when
1759 it's a trusted authority that claims our clock is wrong. Bugfix
1760 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
1761 - We were telling the controller about CHECKING_REACHABILITY and
1762 REACHABILITY_FAILED status events whenever we launch a testing
1763 circuit or notice that one has failed. Instead, only tell the
1764 controller when we want to inform the user of overall success or
1765 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
1767 - Don't warn when we're using a circuit that ends with a node
1768 excluded in ExcludeExitNodes, but the circuit is not used to access
1769 the outside world. This should help fix bug 1090, but more problems
1770 remain. Bugfix on 0.2.1.6-alpha.
1771 - Work around a small memory leak in some versions of OpenSSL that
1772 stopped the memory used by the hostname TLS extension from being
1774 - Make our 'torify' script more portable; if we have only one of
1775 'torsocks' or 'tsocks' installed, don't complain to the user;
1776 and explain our warning about tsocks better.
1779 - Add a "getinfo status/accepted-server-descriptor" controller
1780 command, which is the recommended way for controllers to learn
1781 whether our server descriptor has been successfully received by at
1782 least on directory authority. Un-recommend good-server-descriptor
1783 getinfo and status events until we have a better design for them.
1784 - Update to the "September 4 2009" ip-to-country file.
1787 Changes in version 0.2.2.1-alpha - 2009-08-26
1788 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
1789 Tor clients to bootstrap on networks where only port 80 is reachable,
1790 makes it more straightforward to support hardware crypto accelerators,
1791 and starts the groundwork for gathering stats safely at relays.
1794 - Start the process of disabling ".exit" address notation, since it
1795 can be used for a variety of esoteric application-level attacks
1796 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
1799 o New directory authorities:
1800 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
1804 - New AccelName and AccelDir options add support for dynamic OpenSSL
1805 hardware crypto acceleration engines.
1806 - Tor now supports tunneling all of its outgoing connections over
1807 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
1808 configuration options. Code by Christopher Davis.
1811 - Send circuit or stream sendme cells when our window has decreased
1812 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
1813 by Karsten when testing the "reduce circuit window" performance
1814 patch. Bugfix on the 54th commit on Tor -- from July 2002,
1815 before the release of Tor 0.0.0. This is the new winner of the
1818 o New options for gathering stats safely:
1819 - Directories that set "DirReqStatistics 1" write statistics on
1820 directory request to disk every 24 hours. As compared to the
1821 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
1822 1) stats are written to disk exactly every 24 hours; 2) estimated
1823 shares of v2 and v3 requests are determined as mean values, not at
1824 the end of a measurement period; 3) unresolved requests are listed
1825 with country code '??'; 4) directories also measure download times.
1826 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
1827 number of exit streams and transferred bytes per port to disk every
1829 - Relays that set "CellStatistics 1" write statistics on how long
1830 cells spend in their circuit queues to disk every 24 hours.
1831 - Entry nodes that set "EntryStatistics 1" write statistics on the
1832 rough number and origins of connecting clients to disk every 24
1834 - Relays that write any of the above statistics to disk and set
1835 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
1836 their extra-info documents.
1839 - New --digests command-line switch to output the digests of the
1840 source files Tor was built with.
1841 - The "torify" script now uses torsocks where available.
1842 - The memarea code now uses a sentinel value at the end of each area
1843 to make sure nothing writes beyond the end of an area. This might
1844 help debug some conceivable causes of bug 930.
1845 - Time and memory units in the configuration file can now be set to
1846 fractional units. For example, "2.5 GB" is now a valid value for
1848 - Certain Tor clients (such as those behind check.torproject.org) may
1849 want to fetch the consensus in an extra early manner. To enable this
1850 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
1851 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
1852 as only certain clients who must have this information sooner should
1854 - Instead of adding the svn revision to the Tor version string, report
1855 the git commit (when we're building from a git checkout).
1858 - If any the v3 certs we download are unparseable, we should actually
1859 notice the failure so we don't retry indefinitely. Bugfix on
1860 0.2.0.x; reported by "rotator".
1861 - If the cached cert file is unparseable, warn but don't exit.
1862 - Fix possible segmentation fault on directory authorities. Bugfix on
1864 - When Tor fails to parse a descriptor of any kind, dump it to disk.
1865 Might help diagnosing bug 1051.
1867 o Deprecated and removed features:
1868 - The controller no longer accepts the old obsolete "addr-mappings/"
1869 or "unregistered-servers-" GETINFO values.
1870 - Hidden services no longer publish version 0 descriptors, and clients
1871 do not request or use version 0 descriptors. However, the old hidden
1872 service authorities still accept and serve version 0 descriptors
1873 when contacted by older hidden services/clients.
1874 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
1875 always on; using them is necessary for correct forward-compatible
1877 - Remove support for .noconnect style addresses. Nobody was using
1878 them, and they provided another avenue for detecting Tor users
1879 via application-level web tricks.
1881 o Packaging changes:
1882 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
1883 installer bundles. See
1884 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
1885 for details of what's new in Vidalia 0.2.3.
1886 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
1887 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
1888 configuration file, rather than the old Privoxy.
1889 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
1890 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
1891 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
1892 better compatibility with OS X 10.6, aka Snow Leopard.
1893 - OS X Vidalia Bundle: The multi-package installer is now replaced
1894 by a simple drag and drop to the /Applications folder. This change
1895 occurred with the upgrade to Vidalia 0.2.3.
1898 Changes in version 0.2.1.19 - 2009-07-28
1899 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
1900 services on Tor 0.2.1.3-alpha through 0.2.1.18.
1903 - Make accessing hidden services on 0.2.1.x work right again.
1904 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
1905 part of patch provided by "optimist".
1908 - When a relay/bridge is writing out its identity key fingerprint to
1909 the "fingerprint" file and to its logs, write it without spaces. Now
1910 it will look like the fingerprints in our bridges documentation,
1911 and confuse fewer users.
1914 - Relays no longer publish a new server descriptor if they change
1915 their MaxAdvertisedBandwidth config option but it doesn't end up
1916 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
1917 fixes bug 1026. Patch from Sebastian.
1918 - Avoid leaking memory every time we get a create cell but we have
1919 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
1920 fixes bug 1034. Reported by BarkerJr.
1923 Changes in version 0.2.1.18 - 2009-07-24
1924 Tor 0.2.1.18 lays the foundations for performance improvements,
1925 adds status events to help users diagnose bootstrap problems, adds
1926 optional authentication/authorization for hidden services, fixes a
1927 variety of potential anonymity problems, and includes a huge pile of
1928 other features and bug fixes.
1931 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
1934 Changes in version 0.2.1.17-rc - 2009-07-07
1935 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
1936 candidate for the 0.2.1.x series. It lays the groundwork for further
1937 client performance improvements, and also fixes a big bug with directory
1938 authorities that were causing them to assign Guard and Stable flags
1941 The Windows bundles also finally include the geoip database that we
1942 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
1943 should actually install Torbutton rather than giving you a cryptic
1944 failure message (oops).
1947 - Clients now use the bandwidth values in the consensus, rather than
1948 the bandwidth values in each relay descriptor. This approach opens
1949 the door to more accurate bandwidth estimates once the directory
1950 authorities start doing active measurements. Implements more of
1954 - When Tor clients restart after 1-5 days, they discard all their
1955 cached descriptors as too old, but they still use the cached
1956 consensus document. This approach is good for robustness, but
1957 bad for performance: since they don't know any bandwidths, they
1958 end up choosing at random rather than weighting their choice by
1959 speed. Fixed by the above feature of putting bandwidths in the
1960 consensus. Bugfix on 0.2.0.x.
1961 - Directory authorities were neglecting to mark relays down in their
1962 internal histories if the relays fall off the routerlist without
1963 ever being found unreachable. So there were relays in the histories
1964 that haven't been seen for eight months, and are listed as being
1965 up for eight months. This wreaked havoc on the "median wfu"
1966 and "median mtbf" calculations, in turn making Guard and Stable
1967 flags very wrong, hurting network performance. Fixes bugs 696 and
1968 969. Bugfix on 0.2.0.6-alpha.
1971 - Serve the DirPortFrontPage page even when we have been approaching
1972 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
1973 - The control port would close the connection before flushing long
1974 replies, such as the network consensus, if a QUIT command was issued
1975 before the reply had completed. Now, the control port flushes all
1976 pending replies before closing the connection. Also fixed a spurious
1977 warning when a QUIT command is issued after a malformed or rejected
1978 AUTHENTICATE command, but before the connection was closed. Patch
1979 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
1980 - When we can't find an intro key for a v2 hidden service descriptor,
1981 fall back to the v0 hidden service descriptor and log a bug message.
1982 Workaround for bug 1024.
1983 - Fix a log message that did not respect the SafeLogging option.
1987 - If we're a relay and we change our IP address, be more verbose
1988 about the reason that made us change. Should help track down
1989 further bugs for relays on dynamic IP addresses.
1992 Changes in version 0.2.0.35 - 2009-06-24
1994 - Avoid crashing in the presence of certain malformed descriptors.
1995 Found by lark, and by automated fuzzing.
1996 - Fix an edge case where a malicious exit relay could convince a
1997 controller that the client's DNS question resolves to an internal IP
1998 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
2001 - Finally fix the bug where dynamic-IP relays disappear when their
2002 IP address changes: directory mirrors were mistakenly telling
2003 them their old address if they asked via begin_dir, so they
2004 never got an accurate answer about their new address, so they
2005 just vanished after a day. For belt-and-suspenders, relays that
2006 don't set Address in their config now avoid using begin_dir for
2007 all direct connections. Should fix bugs 827, 883, and 900.
2008 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
2009 that would occur on some exit nodes when DNS failures and timeouts
2010 occurred in certain patterns. Fix for bug 957.
2013 - When starting with a cache over a few days old, do not leak
2014 memory for the obsolete router descriptors in it. Bugfix on
2015 0.2.0.33; fixes bug 672.
2016 - Hidden service clients didn't use a cached service descriptor that
2017 was older than 15 minutes, but wouldn't fetch a new one either,
2018 because there was already one in the cache. Now, fetch a v2
2019 descriptor unless the same descriptor was added to the cache within
2020 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
2023 Changes in version 0.2.1.16-rc - 2009-06-20
2024 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
2025 a bunch of minor bugs.
2028 - Fix an edge case where a malicious exit relay could convince a
2029 controller that the client's DNS question resolves to an internal IP
2030 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
2032 o Major performance improvements (on 0.2.0.x):
2033 - Disable and refactor some debugging checks that forced a linear scan
2034 over the whole server-side DNS cache. These accounted for over 50%
2035 of CPU time on a relatively busy exit node's gprof profile. Found
2037 - Disable some debugging checks that appeared in exit node profile
2041 - Update to the "June 3 2009" ip-to-country file.
2042 - Do not have tor-resolve automatically refuse all .onion addresses;
2043 if AutomapHostsOnResolve is set in your torrc, this will work fine.
2045 o Minor bugfixes (on 0.2.0.x):
2046 - Log correct error messages for DNS-related network errors on
2048 - Fix a race condition that could cause crashes or memory corruption
2049 when running as a server with a controller listening for log
2051 - Avoid crashing when we have a policy specified in a DirPolicy or
2052 SocksPolicy or ReachableAddresses option with ports set on it,
2053 and we re-load the policy. May fix bug 996.
2054 - Hidden service clients didn't use a cached service descriptor that
2055 was older than 15 minutes, but wouldn't fetch a new one either,
2056 because there was already one in the cache. Now, fetch a v2
2057 descriptor unless the same descriptor was added to the cache within
2058 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
2060 o Minor bugfixes (on 0.2.1.x):
2061 - Don't warn users about low port and hibernation mix when they
2062 provide a *ListenAddress directive to fix that. Bugfix on
2064 - When switching back and forth between bridge mode, do not start
2065 gathering GeoIP data until two hours have passed.
2066 - Do not complain that the user has requested an excluded node as
2067 an exit when the node is not really an exit. This could happen
2068 because the circuit was for testing, or an introduction point.
2072 Changes in version 0.2.1.15-rc - 2009-05-25
2073 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
2074 series. It fixes a major bug on fast exit relays, as well as a variety
2077 o Major bugfixes (on 0.2.0.x):
2078 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
2079 that would occur on some exit nodes when DNS failures and timeouts
2080 occurred in certain patterns. Fix for bug 957.
2082 o Minor bugfixes (on 0.2.0.x):
2083 - Actually return -1 in the error case for read_bandwidth_usage().
2084 Harmless bug, since we currently don't care about the return value
2085 anywhere. Bugfix on 0.2.0.9-alpha.
2086 - Provide a more useful log message if bug 977 (related to buffer
2087 freelists) ever reappears, and do not crash right away.
2088 - Fix an assertion failure on 64-bit platforms when we allocated
2089 memory right up to the end of a memarea, then realigned the memory
2090 one step beyond the end. Fixes a possible cause of bug 930.
2091 - Protect the count of open sockets with a mutex, so we can't
2092 corrupt it when two threads are closing or opening sockets at once.
2093 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
2094 - Don't allow a bridge to publish its router descriptor to a
2095 non-bridge directory authority. Fixes part of bug 932.
2096 - When we change to or from being a bridge, reset our counts of
2097 client usage by country. Fixes bug 932.
2098 - Fix a bug that made stream bandwidth get misreported to the
2100 - Stop using malloc_usable_size() to use more area than we had
2101 actually allocated: it was safe, but made valgrind really unhappy.
2102 - Fix a memory leak when v3 directory authorities load their keys
2103 and cert from disk. Bugfix on 0.2.0.1-alpha.
2105 o Minor bugfixes (on 0.2.1.x):
2106 - Fix use of freed memory when deciding to mark a non-addable
2107 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
2110 Changes in version 0.2.1.14-rc - 2009-04-12
2111 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
2112 series. It begins fixing some major performance problems, and also
2113 finally addresses the bug that was causing relays on dynamic IP
2114 addresses to fall out of the directory.
2117 - Clients replace entry guards that were chosen more than a few months
2118 ago. This change should significantly improve client performance,
2119 especially once more people upgrade, since relays that have been
2120 a guard for a long time are currently overloaded.
2122 o Major bugfixes (on 0.2.0):
2123 - Finally fix the bug where dynamic-IP relays disappear when their
2124 IP address changes: directory mirrors were mistakenly telling
2125 them their old address if they asked via begin_dir, so they
2126 never got an accurate answer about their new address, so they
2127 just vanished after a day. For belt-and-suspenders, relays that
2128 don't set Address in their config now avoid using begin_dir for
2129 all direct connections. Should fix bugs 827, 883, and 900.
2130 - Relays were falling out of the networkstatus consensus for
2131 part of a day if they changed their local config but the
2132 authorities discarded their new descriptor as "not sufficiently
2133 different". Now directory authorities accept a descriptor as changed
2134 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
2136 - Avoid crashing in the presence of certain malformed descriptors.
2137 Found by lark, and by automated fuzzing.
2140 - When generating circuit events with verbose nicknames for
2141 controllers, try harder to look up nicknames for routers on a
2142 circuit. (Previously, we would look in the router descriptors we had
2143 for nicknames, but not in the consensus.) Partial fix for bug 941.
2144 - If the bridge config line doesn't specify a port, assume 443.
2145 This makes bridge lines a bit smaller and easier for users to
2147 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
2148 bytes (aka 20KB/s), to match our documentation. Also update
2149 directory authorities so they always assign the Fast flag to relays
2150 with 20KB/s of capacity. Now people running relays won't suddenly
2151 find themselves not seeing any use, if the network gets faster
2153 - Update to the "April 3 2009" ip-to-country file.
2156 - Avoid trying to print raw memory to the logs when we decide to
2157 give up on downloading a given relay descriptor. Bugfix on
2159 - In tor-resolve, when the Tor client to use is specified by
2160 <hostname>:<port>, actually use the specified port rather than
2161 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
2162 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
2163 - When starting with a cache over a few days old, do not leak
2164 memory for the obsolete router descriptors in it. Bugfix on
2166 - Avoid double-free on list of successfully uploaded hidden
2167 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
2168 - Change memarea_strndup() implementation to work even when
2169 duplicating a string at the end of a page. This bug was
2170 harmless for now, but could have meant crashes later. Fix by
2171 lark. Bugfix on 0.2.1.1-alpha.
2172 - Limit uploaded directory documents to be 16M rather than 500K.
2173 The directory authorities were refusing v3 consensus votes from
2174 other authorities, since the votes are now 504K. Fixes bug 959;
2175 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
2176 - Directory authorities should never send a 503 "busy" response to
2177 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
2181 Changes in version 0.2.1.13-alpha - 2009-03-09
2182 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
2183 cleanups. We're finally getting close to a release candidate.
2186 - Correctly update the list of which countries we exclude as
2187 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
2188 lark. Bugfix on 0.2.1.6-alpha.
2190 o Minor bugfixes (on 0.2.0.x and earlier):
2191 - Automatically detect MacOSX versions earlier than 10.4.0, and
2192 disable kqueue from inside Tor when running with these versions.
2193 We previously did this from the startup script, but that was no
2194 help to people who didn't use the startup script. Resolves bug 863.
2195 - When we had picked an exit node for a connection, but marked it as
2196 "optional", and it turned out we had no onion key for the exit,
2197 stop wanting that exit and try again. This situation may not
2198 be possible now, but will probably become feasible with proposal
2199 158. Spotted by rovv. Fixes another case of bug 752.
2200 - Clients no longer cache certificates for authorities they do not
2201 recognize. Bugfix on 0.2.0.9-alpha.
2202 - When we can't transmit a DNS request due to a network error, retry
2203 it after a while, and eventually transmit a failing response to
2204 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
2205 - If the controller claimed responsibility for a stream, but that
2206 stream never finished making its connection, it would live
2207 forever in circuit_wait state. Now we close it after SocksTimeout
2208 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
2209 - Drop begin cells to a hidden service if they come from the middle
2210 of a circuit. Patch from lark.
2211 - When we erroneously receive two EXTEND cells for the same circuit
2212 ID on the same connection, drop the second. Patch from lark.
2213 - Fix a crash that occurs on exit nodes when a nameserver request
2214 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
2215 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
2217 - Do not assume that a stack-allocated character array will be
2218 64-bit aligned on platforms that demand that uint64_t access is
2219 aligned. Possible fix for bug 604.
2220 - Parse dates and IPv4 addresses in a locale- and libc-independent
2221 manner, to avoid platform-dependent behavior on malformed input.
2222 - Build correctly when configured to build outside the main source
2223 path. Patch from Michael Gold.
2224 - We were already rejecting relay begin cells with destination port
2225 of 0. Now also reject extend cells with destination port or address
2226 of 0. Suggested by lark.
2228 o Minor bugfixes (on 0.2.1.x):
2229 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
2230 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
2231 - If we're an exit node, scrub the IP address to which we are exiting
2232 in the logs. Bugfix on 0.2.1.8-alpha.
2235 - On Linux, use the prctl call to re-enable core dumps when the user
2237 - New controller event NEWCONSENSUS that lists the networkstatus
2238 lines for every recommended relay. Now controllers like Torflow
2239 can keep up-to-date on which relays they should be using.
2240 - Update to the "February 26 2009" ip-to-country file.
2243 Changes in version 0.2.0.34 - 2009-02-08
2244 Tor 0.2.0.34 features several more security-related fixes. You should
2245 upgrade, especially if you run an exit relay (remote crash) or a
2246 directory authority (remote infinite loop), or you're on an older
2247 (pre-XP) or not-recently-patched Windows (remote exploit).
2249 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
2250 have many known flaws, and nobody should be using them. You should
2251 upgrade. If you're using a Linux or BSD and its packages are obsolete,
2252 stop using those packages and upgrade anyway.
2255 - Fix an infinite-loop bug on handling corrupt votes under certain
2256 circumstances. Bugfix on 0.2.0.8-alpha.
2257 - Fix a temporary DoS vulnerability that could be performed by
2258 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
2259 - Avoid a potential crash on exit nodes when processing malformed
2260 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
2261 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
2262 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
2265 - Fix compilation on systems where time_t is a 64-bit integer.
2266 Patch from Matthias Drochner.
2267 - Don't consider expiring already-closed client connections. Fixes
2268 bug 893. Bugfix on 0.0.2pre20.
2271 Changes in version 0.2.1.12-alpha - 2009-02-08
2272 Tor 0.2.1.12-alpha features several more security-related fixes. You
2273 should upgrade, especially if you run an exit relay (remote crash) or
2274 a directory authority (remote infinite loop), or you're on an older
2275 (pre-XP) or not-recently-patched Windows (remote exploit). It also
2276 includes a big pile of minor bugfixes and cleanups.
2279 - Fix an infinite-loop bug on handling corrupt votes under certain
2280 circumstances. Bugfix on 0.2.0.8-alpha.
2281 - Fix a temporary DoS vulnerability that could be performed by
2282 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
2283 - Avoid a potential crash on exit nodes when processing malformed
2284 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
2287 - Let controllers actually ask for the "clients_seen" event for
2288 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
2289 reported by Matt Edman.
2290 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
2292 - Fix a bug in address parsing that was preventing bridges or hidden
2293 service targets from being at IPv6 addresses.
2294 - Solve a bug that kept hardware crypto acceleration from getting
2295 enabled when accounting was turned on. Fixes bug 907. Bugfix on
2297 - Remove a bash-ism from configure.in to build properly on non-Linux
2298 platforms. Bugfix on 0.2.1.1-alpha.
2299 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
2300 headers. Bugfix on 0.2.0.10-alpha.
2301 - Don't consider expiring already-closed client connections. Fixes
2302 bug 893. Bugfix on 0.0.2pre20.
2303 - Fix another interesting corner-case of bug 891 spotted by rovv:
2304 Previously, if two hosts had different amounts of clock drift, and
2305 one of them created a new connection with just the wrong timing,
2306 the other might decide to deprecate the new connection erroneously.
2307 Bugfix on 0.1.1.13-alpha.
2308 - Resolve a very rare crash bug that could occur when the user forced
2309 a nameserver reconfiguration during the middle of a nameserver
2310 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
2311 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
2312 Bugfix on 0.2.1.7-alpha.
2313 - If we're using bridges and our network goes away, be more willing
2314 to forgive our bridges and try again when we get an application
2315 request. Bugfix on 0.2.0.x.
2318 - Support platforms where time_t is 64 bits long. (Congratulations,
2319 NetBSD!) Patch from Matthias Drochner.
2320 - Add a 'getinfo status/clients-seen' controller command, in case
2321 controllers want to hear clients_seen events but connect late.
2324 - Disable GCC's strict alias optimization by default, to avoid the
2325 likelihood of its introducing subtle bugs whenever our code violates
2326 the letter of C99's alias rules.
2329 Changes in version 0.2.0.33 - 2009-01-21
2330 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
2331 useful to users. It also finally fixes a bug where a relay or client
2332 that's been off for many days would take a long time to bootstrap.
2334 This update also fixes an important security-related bug reported by
2335 Ilja van Sprundel. You should upgrade. (We'll send out more details
2336 about the bug once people have had some time to upgrade.)
2339 - Fix a heap-corruption bug that may be remotely triggerable on
2340 some platforms. Reported by Ilja van Sprundel.
2343 - When a stream at an exit relay is in state "resolving" or
2344 "connecting" and it receives an "end" relay cell, the exit relay
2345 would silently ignore the end cell and not close the stream. If
2346 the client never closes the circuit, then the exit relay never
2347 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
2349 - When sending CREATED cells back for a given circuit, use a 64-bit
2350 connection ID to find the right connection, rather than an addr:port
2351 combination. Now that we can have multiple OR connections between
2352 the same ORs, it is no longer possible to use addr:port to uniquely
2353 identify a connection.
2354 - Bridge relays that had DirPort set to 0 would stop fetching
2355 descriptors shortly after startup, and then briefly resume
2356 after a new bandwidth test and/or after publishing a new bridge
2357 descriptor. Bridge users that try to bootstrap from them would
2358 get a recent networkstatus but would get descriptors from up to
2359 18 hours earlier, meaning most of the descriptors were obsolete
2360 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
2361 - Prevent bridge relays from serving their 'extrainfo' document
2362 to anybody who asks, now that extrainfo docs include potentially
2363 sensitive aggregated client geoip summaries. Bugfix on
2365 - If the cached networkstatus consensus is more than five days old,
2366 discard it rather than trying to use it. In theory it could be
2367 useful because it lists alternate directory mirrors, but in practice
2368 it just means we spend many minutes trying directory mirrors that
2369 are long gone from the network. Also discard router descriptors as
2370 we load them if they are more than five days old, since the onion
2371 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
2374 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
2375 could make gcc generate non-functional binary search code. Bugfix
2377 - Build correctly on platforms without socklen_t.
2378 - Compile without warnings on solaris.
2379 - Avoid potential crash on internal error during signature collection.
2380 Fixes bug 864. Patch from rovv.
2381 - Correct handling of possible malformed authority signing key
2382 certificates with internal signature types. Fixes bug 880.
2383 Bugfix on 0.2.0.3-alpha.
2384 - Fix a hard-to-trigger resource leak when logging credential status.
2386 - When we can't initialize DNS because the network is down, do not
2387 automatically stop Tor from starting. Instead, we retry failed
2388 dns_init() every 10 minutes, and change the exit policy to reject
2389 *:* until one succeeds. Fixes bug 691.
2390 - Use 64 bits instead of 32 bits for connection identifiers used with
2391 the controller protocol, to greatly reduce risk of identifier reuse.
2392 - When we're choosing an exit node for a circuit, and we have
2393 no pending streams, choose a good general exit rather than one that
2394 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
2395 - Fix another case of assuming, when a specific exit is requested,
2396 that we know more than the user about what hosts it allows.
2397 Fixes one case of bug 752. Patch from rovv.
2398 - Clip the MaxCircuitDirtiness config option to a minimum of 10
2399 seconds. Warn the user if lower values are given in the
2400 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
2401 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
2402 user if lower values are given in the configuration. Bugfix on
2403 0.1.1.17-rc. Patch by Sebastian.
2404 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
2405 the cache because we already had a v0 descriptor with the same ID.
2406 Bugfix on 0.2.0.18-alpha.
2407 - Fix a race condition when freeing keys shared between main thread
2408 and CPU workers that could result in a memory leak. Bugfix on
2409 0.1.0.1-rc. Fixes bug 889.
2410 - Send a valid END cell back when a client tries to connect to a
2411 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
2412 840. Patch from rovv.
2413 - Check which hops rendezvous stream cells are associated with to
2414 prevent possible guess-the-streamid injection attacks from
2415 intermediate hops. Fixes another case of bug 446. Based on patch
2417 - If a broken client asks a non-exit router to connect somewhere,
2418 do not even do the DNS lookup before rejecting the connection.
2419 Fixes another case of bug 619. Patch from rovv.
2420 - When a relay gets a create cell it can't decrypt (e.g. because it's
2421 using the wrong onion key), we were dropping it and letting the
2422 client time out. Now actually answer with a destroy cell. Fixes
2423 bug 904. Bugfix on 0.0.2pre8.
2425 o Minor bugfixes (hidden services):
2426 - Do not throw away existing introduction points on SIGHUP. Bugfix on
2427 0.0.6pre1. Patch by Karsten. Fixes bug 874.
2430 - Report the case where all signatures in a detached set are rejected
2431 differently than the case where there is an error handling the
2433 - When we realize that another process has modified our cached
2434 descriptors, print out a more useful error message rather than
2435 triggering an assertion. Fixes bug 885. Patch from Karsten.
2436 - Implement the 0x20 hack to better resist DNS poisoning: set the
2437 case on outgoing DNS requests randomly, and reject responses that do
2438 not match the case correctly. This logic can be disabled with the
2439 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
2440 of servers that do not reliably preserve case in replies. See
2441 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
2443 - Check DNS replies for more matching fields to better resist DNS
2445 - Never use OpenSSL compression: it wastes RAM and CPU trying to
2446 compress cells, which are basically all encrypted, compressed, or
2450 Changes in version 0.2.1.11-alpha - 2009-01-20
2451 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
2452 week it will take a long time to bootstrap again" bug. It also fixes
2453 an important security-related bug reported by Ilja van Sprundel. You
2454 should upgrade. (We'll send out more details about the bug once people
2455 have had some time to upgrade.)
2458 - Fix a heap-corruption bug that may be remotely triggerable on
2459 some platforms. Reported by Ilja van Sprundel.
2462 - Discard router descriptors as we load them if they are more than
2463 five days old. Otherwise if Tor is off for a long time and then
2464 starts with cached descriptors, it will try to use the onion
2465 keys in those obsolete descriptors when building circuits. Bugfix
2466 on 0.2.0.x. Fixes bug 887.
2469 - Try to make sure that the version of Libevent we're running with
2470 is binary-compatible with the one we built with. May address bug
2472 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
2473 for bug 905. Bugfix on 0.2.1.7-alpha.
2474 - Add a new --enable-local-appdata configuration switch to change
2475 the default location of the datadir on win32 from APPDATA to
2476 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
2477 entirely. Patch from coderman.
2480 - Make outbound DNS packets respect the OutboundBindAddress setting.
2481 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
2482 - When our circuit fails at the first hop (e.g. we get a destroy
2483 cell back), avoid using that OR connection anymore, and also
2484 tell all the one-hop directory requests waiting for it that they
2485 should fail. Bugfix on 0.2.1.3-alpha.
2486 - In the torify(1) manpage, mention that tsocks will leak your
2490 Changes in version 0.2.1.10-alpha - 2009-01-06
2491 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
2492 would make the bridge relay not so useful if it had DirPort set to 0,
2493 and one that could let an attacker learn a little bit of information
2494 about the bridge's users), and a bug that would cause your Tor relay
2495 to ignore a circuit create request it can't decrypt (rather than reply
2496 with an error). It also fixes a wide variety of other bugs.
2499 - If the cached networkstatus consensus is more than five days old,
2500 discard it rather than trying to use it. In theory it could
2501 be useful because it lists alternate directory mirrors, but in
2502 practice it just means we spend many minutes trying directory
2503 mirrors that are long gone from the network. Helps bug 887 a bit;
2505 - Bridge relays that had DirPort set to 0 would stop fetching
2506 descriptors shortly after startup, and then briefly resume
2507 after a new bandwidth test and/or after publishing a new bridge
2508 descriptor. Bridge users that try to bootstrap from them would
2509 get a recent networkstatus but would get descriptors from up to
2510 18 hours earlier, meaning most of the descriptors were obsolete
2511 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
2512 - Prevent bridge relays from serving their 'extrainfo' document
2513 to anybody who asks, now that extrainfo docs include potentially
2514 sensitive aggregated client geoip summaries. Bugfix on
2518 - New controller event "clients_seen" to report a geoip-based summary
2519 of which countries we've seen clients from recently. Now controllers
2520 like Vidalia can show bridge operators that they're actually making
2522 - Build correctly against versions of OpenSSL 0.9.8 or later built
2523 without support for deprecated functions.
2524 - Update to the "December 19 2008" ip-to-country file.
2526 o Minor bugfixes (on 0.2.0.x):
2527 - Authorities now vote for the Stable flag for any router whose
2528 weighted MTBF is at least 5 days, regardless of the mean MTBF.
2529 - Do not remove routers as too old if we do not have any consensus
2530 document. Bugfix on 0.2.0.7-alpha.
2531 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
2532 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
2533 - When an exit relay resolves a stream address to a local IP address,
2534 do not just keep retrying that same exit relay over and
2535 over. Instead, just close the stream. Addresses bug 872. Bugfix
2536 on 0.2.0.32. Patch from rovv.
2537 - If a hidden service sends us an END cell, do not consider
2538 retrying the connection; just close it. Patch from rovv.
2539 - When we made bridge authorities stop serving bridge descriptors over
2540 unencrypted links, we also broke DirPort reachability testing for
2541 bridges. So bridges with a non-zero DirPort were printing spurious
2542 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
2543 - When a relay gets a create cell it can't decrypt (e.g. because it's
2544 using the wrong onion key), we were dropping it and letting the
2545 client time out. Now actually answer with a destroy cell. Fixes
2546 bug 904. Bugfix on 0.0.2pre8.
2547 - Squeeze 2-5% out of client performance (according to oprofile) by
2548 improving the implementation of some policy-manipulation functions.
2550 o Minor bugfixes (on 0.2.1.x):
2551 - Make get_interface_address() function work properly again; stop
2552 guessing the wrong parts of our address as our address.
2553 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
2554 send on that circuit. Otherwise we might violate the proposal-110
2555 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
2557 - When we're sending non-EXTEND cells to the first hop in a circuit,
2558 for example to use an encrypted directory connection, we don't need
2559 to use RELAY_EARLY cells: the first hop knows what kind of cell
2560 it is, and nobody else can even see the cell type. Conserving
2561 RELAY_EARLY cells makes it easier to cannibalize circuits like
2563 - Stop logging nameserver addresses in reverse order.
2564 - If we are retrying a directory download slowly over and over, do
2565 not automatically give up after the 254th failure. Bugfix on
2567 - Resume reporting accurate "stream end" reasons to the local control
2568 port. They were lost in the changes for Proposal 148. Bugfix on
2571 o Deprecated and removed features:
2572 - The old "tor --version --version" command, which would print out
2573 the subversion "Id" of most of the source files, is now removed. It
2574 turned out to be less useful than we'd expected, and harder to
2577 o Code simplifications and refactoring:
2578 - Change our header file guard macros to be less likely to conflict
2579 with system headers. Adam Langley noticed that we were conflicting
2580 with log.h on Android.
2581 - Tool-assisted documentation cleanup. Nearly every function or
2582 static variable in Tor should have its own documentation now.
2585 Changes in version 0.2.1.9-alpha - 2008-12-25
2586 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
2588 o New directory authorities:
2589 - gabelmoo (the authority run by Karsten Loesing) now has a new
2593 - Never use a connection with a mismatched address to extend a
2594 circuit, unless that connection is canonical. A canonical
2595 connection is one whose address is authenticated by the router's
2596 identity key, either in a NETINFO cell or in a router descriptor.
2597 - Avoid a possible memory corruption bug when receiving hidden service
2598 descriptors. Bugfix on 0.2.1.6-alpha.
2601 - Fix a logic error that would automatically reject all but the first
2602 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
2603 part of bug 813/868. Bug spotted by coderman.
2604 - When a stream at an exit relay is in state "resolving" or
2605 "connecting" and it receives an "end" relay cell, the exit relay
2606 would silently ignore the end cell and not close the stream. If
2607 the client never closes the circuit, then the exit relay never
2608 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
2610 - When we can't initialize DNS because the network is down, do not
2611 automatically stop Tor from starting. Instead, retry failed
2612 dns_init() every 10 minutes, and change the exit policy to reject
2613 *:* until one succeeds. Fixes bug 691.
2616 - Give a better error message when an overzealous init script says
2617 "sudo -u username tor --user username". Makes Bug 882 easier for
2619 - When a directory authority gives us a new guess for our IP address,
2620 log which authority we used. Hopefully this will help us debug
2621 the recent complaints about bad IP address guesses.
2622 - Detect svn revision properly when we're using git-svn.
2623 - Try not to open more than one descriptor-downloading connection
2624 to an authority at once. This should reduce load on directory
2625 authorities. Fixes bug 366.
2626 - Add cross-certification to newly generated certificates, so that
2627 a signing key is enough information to look up a certificate.
2628 Partial implementation of proposal 157.
2629 - Start serving certificates by <identity digest, signing key digest>
2630 pairs. Partial implementation of proposal 157.
2631 - Clients now never report any stream end reason except 'MISC'.
2632 Implements proposal 148.
2633 - On platforms with a maximum syslog string length, truncate syslog
2634 messages to that length ourselves, rather than relying on the
2635 system to do it for us.
2636 - Optimize out calls to time(NULL) that occur for every IO operation,
2637 or for every cell. On systems where time() is a slow syscall,
2638 this fix will be slightly helpful.
2639 - Exit servers can now answer resolve requests for ip6.arpa addresses.
2640 - When we download a descriptor that we then immediately (as
2641 a directory authority) reject, do not retry downloading it right
2642 away. Should save some bandwidth on authorities. Fix for bug
2643 888. Patch by Sebastian Hahn.
2644 - When a download gets us zero good descriptors, do not notify
2645 Tor that new directory information has arrived.
2646 - Avoid some nasty corner cases in the logic for marking connections
2647 as too old or obsolete or noncanonical for circuits. Partial
2650 o Minor features (controller):
2651 - New CONSENSUS_ARRIVED event to note when a new consensus has
2652 been fetched and validated.
2653 - When we realize that another process has modified our cached
2654 descriptors file, print out a more useful error message rather
2655 than triggering an assertion. Fixes bug 885. Patch from Karsten.
2656 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
2657 controllers to prevent SIGHUP from reloading the
2658 configuration. Fixes bug 856.
2661 - Resume using the correct "REASON=" stream when telling the
2662 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
2663 - When a canonical connection appears later in our internal list
2664 than a noncanonical one for a given OR ID, always use the
2665 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
2667 - Clip the MaxCircuitDirtiness config option to a minimum of 10
2668 seconds. Warn the user if lower values are given in the
2669 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
2670 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
2671 user if lower values are given in the configuration. Bugfix on
2672 0.1.1.17-rc. Patch by Sebastian.
2673 - Fix a race condition when freeing keys shared between main thread
2674 and CPU workers that could result in a memory leak. Bugfix on
2675 0.1.0.1-rc. Fixes bug 889.
2677 o Minor bugfixes (hidden services):
2678 - Do not throw away existing introduction points on SIGHUP (bugfix on
2679 0.0.6pre1); also, do not stall hidden services because we're
2680 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
2681 by John Brooks. Patch by Karsten. Fixes bug 874.
2682 - Fix a memory leak when we decline to add a v2 rendezvous
2683 descriptor to the cache because we already had a v0 descriptor
2684 with the same ID. Bugfix on 0.2.0.18-alpha.
2686 o Deprecated and removed features:
2687 - RedirectExits has been removed. It was deprecated since
2689 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
2690 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
2691 - Cell pools are now always enabled; --disable-cell-pools is ignored.
2693 o Code simplifications and refactoring:
2694 - Rename the confusing or_is_obsolete field to the more appropriate
2695 is_bad_for_new_circs, and move it to or_connection_t where it
2697 - Move edge-only flags from connection_t to edge_connection_t: not
2698 only is this better coding, but on machines of plausible alignment,
2699 it should save 4-8 bytes per connection_t. "Every little bit helps."
2700 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
2701 for consistency; keep old option working for backward compatibility.
2702 - Simplify the code for finding connections to use for a circuit.
2705 Changes in version 0.2.1.8-alpha - 2008-12-08
2706 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
2707 builds better on unusual platforms like Solaris and old OS X, and
2708 fixes a variety of other issues.
2711 - New DirPortFrontPage option that takes an html file and publishes
2712 it as "/" on the DirPort. Now relay operators can provide a
2713 disclaimer without needing to set up a separate webserver. There's
2714 a sample disclaimer in contrib/tor-exit-notice.html.
2717 - When the client is choosing entry guards, now it selects at most
2718 one guard from a given relay family. Otherwise we could end up with
2719 all of our entry points into the network run by the same operator.
2720 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
2723 - Fix a DOS opportunity during the voting signature collection process
2724 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
2725 - Fix a possible segfault when establishing an exit connection. Bugfix
2729 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
2731 - Made Tor a little less aggressive about deleting expired
2732 certificates. Partial fix for bug 854.
2733 - Stop doing unaligned memory access that generated bus errors on
2734 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
2735 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
2736 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
2737 - Make USR2 log-level switch take effect immediately. Bugfix on
2739 - If one win32 nameserver fails to get added, continue adding the
2740 rest, and don't automatically fail.
2741 - Use fcntl() for locking when flock() is not available. Should fix
2742 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
2743 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
2744 could make gcc generate non-functional binary search code. Bugfix
2746 - Build correctly on platforms without socklen_t.
2747 - Avoid potential crash on internal error during signature collection.
2748 Fixes bug 864. Patch from rovv.
2749 - Do not use C's stdio library for writing to log files. This will
2750 improve logging performance by a minute amount, and will stop
2751 leaking fds when our disk is full. Fixes bug 861.
2752 - Stop erroneous use of O_APPEND in cases where we did not in fact
2753 want to re-seek to the end of a file before every last write().
2754 - Correct handling of possible malformed authority signing key
2755 certificates with internal signature types. Fixes bug 880. Bugfix
2757 - Fix a hard-to-trigger resource leak when logging credential status.
2761 - Directory mirrors no longer fetch the v1 directory or
2762 running-routers files. They are obsolete, and nobody asks for them
2763 anymore. This is the first step to making v1 authorities obsolete.
2765 o Minor features (controller):
2766 - Return circuit purposes in response to GETINFO circuit-status. Fixes
2770 Changes in version 0.2.0.32 - 2008-11-20
2771 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
2772 packages (and maybe other packages) noticed by Theo de Raadt, fixes
2773 a smaller security flaw that might allow an attacker to access local
2774 services, further improves hidden service performance, and fixes a
2775 variety of other issues.
2778 - The "User" and "Group" config options did not clear the
2779 supplementary group entries for the Tor process. The "User" option
2780 is now more robust, and we now set the groups to the specified
2781 user's primary group. The "Group" option is now ignored. For more
2782 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
2783 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
2784 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
2785 - The "ClientDNSRejectInternalAddresses" config option wasn't being
2786 consistently obeyed: if an exit relay refuses a stream because its
2787 exit policy doesn't allow it, we would remember what IP address
2788 the relay said the destination address resolves to, even if it's
2789 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
2792 - Fix a DOS opportunity during the voting signature collection process
2793 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
2795 o Major bugfixes (hidden services):
2796 - When fetching v0 and v2 rendezvous service descriptors in parallel,
2797 we were failing the whole hidden service request when the v0
2798 descriptor fetch fails, even if the v2 fetch is still pending and
2799 might succeed. Similarly, if the last v2 fetch fails, we were
2800 failing the whole hidden service request even if a v0 fetch is
2801 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
2802 - When extending a circuit to a hidden service directory to upload a
2803 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
2804 requests failed, because the router descriptor has not been
2805 downloaded yet. In these cases, do not attempt to upload the
2806 rendezvous descriptor, but wait until the router descriptor is
2807 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
2808 descriptor from a hidden service directory for which the router
2809 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
2813 - Fix several infrequent memory leaks spotted by Coverity.
2814 - When testing for libevent functions, set the LDFLAGS variable
2815 correctly. Found by Riastradh.
2816 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
2817 bootstrapping with tunneled directory connections. Bugfix on
2818 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
2819 - When asked to connect to A.B.exit:80, if we don't know the IP for A
2820 and we know that server B rejects most-but-not all connections to
2821 port 80, we would previously reject the connection. Now, we assume
2822 the user knows what they were asking for. Fixes bug 752. Bugfix
2823 on 0.0.9rc5. Diagnosed by BarkerJr.
2824 - If we overrun our per-second write limits a little, count this as
2825 having used up our write allocation for the second, and choke
2826 outgoing directory writes. Previously, we had only counted this when
2827 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
2828 Bugfix on 0.2.0.x (??).
2829 - Remove the old v2 directory authority 'lefkada' from the default
2830 list. It has been gone for many months.
2831 - Stop doing unaligned memory access that generated bus errors on
2832 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
2833 - Make USR2 log-level switch take effect immediately. Bugfix on
2836 o Minor bugfixes (controller):
2837 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
2838 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
2841 Changes in version 0.2.1.7-alpha - 2008-11-08
2842 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
2843 packages (and maybe other packages) noticed by Theo de Raadt, fixes
2844 a smaller security flaw that might allow an attacker to access local
2845 services, adds better defense against DNS poisoning attacks on exit
2846 relays, further improves hidden service performance, and fixes a
2847 variety of other issues.
2850 - The "ClientDNSRejectInternalAddresses" config option wasn't being
2851 consistently obeyed: if an exit relay refuses a stream because its
2852 exit policy doesn't allow it, we would remember what IP address
2853 the relay said the destination address resolves to, even if it's
2854 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
2855 - The "User" and "Group" config options did not clear the
2856 supplementary group entries for the Tor process. The "User" option
2857 is now more robust, and we now set the groups to the specified
2858 user's primary group. The "Group" option is now ignored. For more
2859 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
2860 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
2861 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
2862 - Do not use or believe expired v3 authority certificates. Patch
2863 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
2866 - Now NodeFamily and MyFamily config options allow spaces in
2867 identity fingerprints, so it's easier to paste them in.
2868 Suggested by Lucky Green.
2869 - Implement the 0x20 hack to better resist DNS poisoning: set the
2870 case on outgoing DNS requests randomly, and reject responses that do
2871 not match the case correctly. This logic can be disabled with the
2872 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
2873 of servers that do not reliably preserve case in replies. See
2874 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
2876 - Preserve case in replies to DNSPort requests in order to support
2877 the 0x20 hack for resisting DNS poisoning attacks.
2879 o Hidden service performance improvements:
2880 - When the client launches an introduction circuit, retry with a
2881 new circuit after 30 seconds rather than 60 seconds.
2882 - Launch a second client-side introduction circuit in parallel
2883 after a delay of 15 seconds (based on work by Christian Wilms).
2884 - Hidden services start out building five intro circuits rather
2885 than three, and when the first three finish they publish a service
2886 descriptor using those. Now we publish our service descriptor much
2887 faster after restart.
2890 - Minor fix in the warning messages when you're having problems
2891 bootstrapping; also, be more forgiving of bootstrap problems when
2892 we're still making incremental progress on a given bootstrap phase.
2893 - When we're choosing an exit node for a circuit, and we have
2894 no pending streams, choose a good general exit rather than one that
2895 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
2896 - Send a valid END cell back when a client tries to connect to a
2897 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
2898 840. Patch from rovv.
2899 - If a broken client asks a non-exit router to connect somewhere,
2900 do not even do the DNS lookup before rejecting the connection.
2901 Fixes another case of bug 619. Patch from rovv.
2902 - Fix another case of assuming, when a specific exit is requested,
2903 that we know more than the user about what hosts it allows.
2904 Fixes another case of bug 752. Patch from rovv.
2905 - Check which hops rendezvous stream cells are associated with to
2906 prevent possible guess-the-streamid injection attacks from
2907 intermediate hops. Fixes another case of bug 446. Based on patch
2909 - Avoid using a negative right-shift when comparing 32-bit
2910 addresses. Possible fix for bug 845 and bug 811.
2911 - Make the assert_circuit_ok() function work correctly on circuits that
2912 have already been marked for close.
2913 - Fix read-off-the-end-of-string error in unit tests when decoding
2914 introduction points.
2915 - Fix uninitialized size field for memory area allocation: may improve
2916 memory performance during directory parsing.
2917 - Treat duplicate certificate fetches as failures, so that we do
2918 not try to re-fetch an expired certificate over and over and over.
2919 - Do not say we're fetching a certificate when we'll in fact skip it
2920 because of a pending download.
2923 Changes in version 0.2.1.6-alpha - 2008-09-30
2924 Tor 0.2.1.6-alpha further improves performance and robustness of
2925 hidden services, starts work on supporting per-country relay selection,
2926 and fixes a variety of smaller issues.
2929 - Implement proposal 121: make it possible to build hidden services
2930 that only certain clients are allowed to connect to. This is
2931 enforced at several points, so that unauthorized clients are unable
2932 to send INTRODUCE cells to the service, or even (depending on the
2933 type of authentication) to learn introduction points. This feature
2934 raises the bar for certain kinds of active attacks against hidden
2935 services. Code by Karsten Loesing.
2936 - Relays now store and serve v2 hidden service descriptors by default,
2937 i.e., the new default value for HidServDirectoryV2 is 1. This is
2938 the last step in proposal 114, which aims to make hidden service
2939 lookups more reliable.
2940 - Start work to allow node restrictions to include country codes. The
2941 syntax to exclude nodes in a country with country code XX is
2942 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
2943 refinement to decide what config options should take priority if
2944 you ask to both use a particular node and exclude it.
2945 - Allow ExitNodes list to include IP ranges and country codes, just
2946 like the Exclude*Nodes lists. Patch from Robert Hogan.
2949 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
2950 Tor to fail to start if you had it configured to use a bridge
2951 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
2952 - When extending a circuit to a hidden service directory to upload a
2953 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
2954 requests failed, because the router descriptor had not been
2955 downloaded yet. In these cases, we now wait until the router
2956 descriptor is downloaded, and then retry. Likewise, clients
2957 now skip over a hidden service directory if they don't yet have
2958 its router descriptor, rather than futilely requesting it and
2959 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
2961 - When fetching v0 and v2 rendezvous service descriptors in parallel,
2962 we were failing the whole hidden service request when the v0
2963 descriptor fetch fails, even if the v2 fetch is still pending and
2964 might succeed. Similarly, if the last v2 fetch fails, we were
2965 failing the whole hidden service request even if a v0 fetch is
2966 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
2967 - DNS replies need to have names matching their requests, but
2968 these names should be in the questions section, not necessarily
2969 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
2972 - Update to the "September 1 2008" ip-to-country file.
2973 - Allow ports 465 and 587 in the default exit policy again. We had
2974 rejected them in 0.1.0.15, because back in 2005 they were commonly
2975 misconfigured and ended up as spam targets. We hear they are better
2976 locked down these days.
2977 - Use a lockfile to make sure that two Tor processes are not
2978 simultaneously running with the same datadir.
2979 - Serve the latest v3 networkstatus consensus via the control
2980 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
2981 - Better logging about stability/reliability calculations on directory
2983 - Drop the requirement to have an open dir port for storing and
2984 serving v2 hidden service descriptors.
2985 - Directory authorities now serve a /tor/dbg-stability.txt URL to
2986 help debug WFU and MTBF calculations.
2987 - Implement most of Proposal 152: allow specialized servers to permit
2988 single-hop circuits, and clients to use those servers to build
2989 single-hop circuits when using a specialized controller. Patch
2990 from Josh Albrecht. Resolves feature request 768.
2991 - Add a -p option to tor-resolve for specifying the SOCKS port: some
2992 people find host:port too confusing.
2993 - Make TrackHostExit mappings expire a while after their last use, not
2994 after their creation. Patch from Robert Hogan.
2995 - Provide circuit purposes along with circuit events to the controller.
2998 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
3000 - Fixed some memory leaks -- some quite frequent, some almost
3001 impossible to trigger -- based on results from Coverity.
3002 - When testing for libevent functions, set the LDFLAGS variable
3003 correctly. Found by Riastradh.
3004 - Fix an assertion bug in parsing policy-related options; possible fix
3006 - Catch and report a few more bootstrapping failure cases when Tor
3007 fails to establish a TCP connection. Cleanup on 0.2.1.x.
3008 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
3009 bootstrapping with tunneled directory connections. Bugfix on
3010 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
3011 - When asked to connect to A.B.exit:80, if we don't know the IP for A
3012 and we know that server B rejects most-but-not all connections to
3013 port 80, we would previously reject the connection. Now, we assume
3014 the user knows what they were asking for. Fixes bug 752. Bugfix
3015 on 0.0.9rc5. Diagnosed by BarkerJr.
3016 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
3017 service directories if they have no advertised dir port. Bugfix
3019 - If we overrun our per-second write limits a little, count this as
3020 having used up our write allocation for the second, and choke
3021 outgoing directory writes. Previously, we had only counted this when
3022 we had met our limits precisely. Fixes bug 824. Patch by rovv.
3023 Bugfix on 0.2.0.x (??).
3024 - Avoid a "0 divided by 0" calculation when calculating router uptime
3025 at directory authorities. Bugfix on 0.2.0.8-alpha.
3026 - Make DNS resolved controller events into "CLOSED", not
3027 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
3029 - Fix a bug where an unreachable relay would establish enough
3030 reachability testing circuits to do a bandwidth test -- if
3031 we already have a connection to the middle hop of the testing
3032 circuit, then it could establish the last hop by using the existing
3033 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
3034 circuits no longer use entry guards in 0.2.1.3-alpha.
3035 - If we have correct permissions on $datadir, we complain to stdout
3036 and fail to start. But dangerous permissions on
3037 $datadir/cached-status/ would cause us to open a log and complain
3038 there. Now complain to stdout and fail to start in both cases. Fixes
3039 bug 820, reported by seeess.
3040 - Remove the old v2 directory authority 'lefkada' from the default
3041 list. It has been gone for many months.
3043 o Code simplifications and refactoring:
3044 - Revise the connection_new functions so that a more typesafe variant
3045 exists. This will work better with Coverity, and let us find any
3046 actual mistakes we're making here.
3047 - Refactor unit testing logic so that dmalloc can be used sensibly
3048 with unit tests to check for memory leaks.
3049 - Move all hidden-service related fields from connection and circuit
3050 structure to substructures: this way they won't eat so much memory.
3053 Changes in version 0.2.0.31 - 2008-09-03
3054 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
3055 a big bug we're seeing where in rare cases traffic from one Tor stream
3056 gets mixed into another stream, and fixes a variety of smaller issues.
3059 - Make sure that two circuits can never exist on the same connection
3060 with the same circuit ID, even if one is marked for close. This
3061 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
3062 - Relays now reject risky extend cells: if the extend cell includes
3063 a digest of all zeroes, or asks to extend back to the relay that
3064 sent the extend cell, tear down the circuit. Ideas suggested
3066 - If not enough of our entry guards are available so we add a new
3067 one, we might use the new one even if it overlapped with the
3068 current circuit's exit relay (or its family). Anonymity bugfix
3069 pointed out by rovv.
3072 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
3073 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
3074 - Correctly detect the presence of the linux/netfilter_ipv4.h header
3075 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
3076 - Pick size of default geoip filename string correctly on windows.
3077 Fixes bug 806. Bugfix on 0.2.0.30.
3078 - Make the autoconf script accept the obsolete --with-ssl-dir
3079 option as an alias for the actually-working --with-openssl-dir
3080 option. Fix the help documentation to recommend --with-openssl-dir.
3081 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
3082 - When using the TransPort option on OpenBSD, and using the User
3083 option to change UID and drop privileges, make sure to open
3084 /dev/pf before dropping privileges. Fixes bug 782. Patch from
3085 Christopher Davis. Bugfix on 0.1.2.1-alpha.
3086 - Try to attach connections immediately upon receiving a RENDEZVOUS2
3087 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
3088 on the client side when connecting to a hidden service. Bugfix
3089 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
3090 - When closing an application-side connection because its circuit is
3091 getting torn down, generate the stream event correctly. Bugfix on
3092 0.1.2.x. Anonymous patch.
3095 Changes in version 0.2.1.5-alpha - 2008-08-31
3096 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
3097 in a lot of the infrastructure for adding authorization to hidden
3098 services, lays the groundwork for having clients read their load
3099 balancing information out of the networkstatus consensus rather than
3100 the individual router descriptors, addresses two potential anonymity
3101 issues, and fixes a variety of smaller issues.
3104 - Convert many internal address representations to optionally hold
3106 - Generate and accept IPv6 addresses in many protocol elements.
3107 - Make resolver code handle nameservers located at ipv6 addresses.
3108 - Begin implementation of proposal 121 ("Client authorization for
3109 hidden services"): configure hidden services with client
3110 authorization, publish descriptors for them, and configure
3111 authorization data for hidden services at clients. The next
3112 step is to actually access hidden services that perform client
3114 - More progress toward proposal 141: Network status consensus
3115 documents and votes now contain bandwidth information for each
3116 router and a summary of that router's exit policy. Eventually this
3117 will be used by clients so that they do not have to download every
3118 known descriptor before building circuits.
3120 o Major bugfixes (on 0.2.0.x and before):
3121 - When sending CREATED cells back for a given circuit, use a 64-bit
3122 connection ID to find the right connection, rather than an addr:port
3123 combination. Now that we can have multiple OR connections between
3124 the same ORs, it is no longer possible to use addr:port to uniquely
3125 identify a connection.
3126 - Relays now reject risky extend cells: if the extend cell includes
3127 a digest of all zeroes, or asks to extend back to the relay that
3128 sent the extend cell, tear down the circuit. Ideas suggested
3130 - If not enough of our entry guards are available so we add a new
3131 one, we might use the new one even if it overlapped with the
3132 current circuit's exit relay (or its family). Anonymity bugfix
3133 pointed out by rovv.
3136 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
3137 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
3138 - When using the TransPort option on OpenBSD, and using the User
3139 option to change UID and drop privileges, make sure to open /dev/pf
3140 before dropping privileges. Fixes bug 782. Patch from Christopher
3141 Davis. Bugfix on 0.1.2.1-alpha.
3142 - Correctly detect the presence of the linux/netfilter_ipv4.h header
3143 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
3144 - Add a missing safe_str() call for a debug log message.
3145 - Use 64 bits instead of 32 bits for connection identifiers used with
3146 the controller protocol, to greatly reduce risk of identifier reuse.
3147 - Make the autoconf script accept the obsolete --with-ssl-dir
3148 option as an alias for the actually-working --with-openssl-dir
3149 option. Fix the help documentation to recommend --with-openssl-dir.
3150 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
3153 - Rate-limit too-many-sockets messages: when they happen, they happen
3154 a lot. Resolves bug 748.
3155 - Resist DNS poisoning a little better by making sure that names in
3156 answer sections match.
3157 - Print the SOCKS5 error message string as well as the error code
3158 when a tor-resolve request fails. Patch from Jacob.
3161 Changes in version 0.2.1.4-alpha - 2008-08-04
3162 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
3165 - The address part of exit policies was not correctly written
3166 to router descriptors. This generated router descriptors that failed
3167 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
3169 - Tor triggered a false assert when extending a circuit to a relay
3170 but we already have a connection open to that relay. Noticed by
3171 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
3174 - Fix a hidden service logging bug: in some edge cases, the router
3175 descriptor of a previously picked introduction point becomes
3176 obsolete and we need to give up on it rather than continually
3177 complaining that it has become obsolete. Observed by xiando. Bugfix
3181 - Take out the TestVia config option, since it was a workaround for
3182 a bug that was fixed in Tor 0.1.1.21.
3185 Changes in version 0.2.1.3-alpha - 2008-08-03
3186 Tor 0.2.1.3-alpha implements most of the pieces to prevent
3187 infinite-length circuit attacks (see proposal 110); fixes a bug that
3188 might cause exit relays to corrupt streams they send back; allows
3189 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
3190 ExcludeExitNodes config options; and fixes a big pile of bugs.
3192 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
3193 - Send a bootstrap problem "warn" event on the first problem if the
3194 reason is NO_ROUTE (that is, our network is down).
3197 - Implement most of proposal 110: The first K cells to be sent
3198 along a circuit are marked as special "early" cells; only K "early"
3199 cells will be allowed. Once this code is universal, we can block
3200 certain kinds of DOS attack by requiring that EXTEND commands must
3201 be sent using an "early" cell.
3204 - Try to attach connections immediately upon receiving a RENDEZVOUS2
3205 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
3206 on the client side when connecting to a hidden service. Bugfix
3207 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
3208 - Ensure that two circuits can never exist on the same connection
3209 with the same circuit ID, even if one is marked for close. This
3210 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
3213 - When relays do their initial bandwidth measurement, don't limit
3214 to just our entry guards for the test circuits. Otherwise we tend
3215 to have multiple test circuits going through a single entry guard,
3216 which makes our bandwidth test less accurate. Fixes part of bug 654;
3217 patch contributed by Josh Albrecht.
3218 - Add an ExcludeExitNodes option so users can list a set of nodes
3219 that should be be excluded from the exit node position, but
3220 allowed elsewhere. Implements proposal 151.
3221 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
3222 ExcludeNodes and ExcludeExitNodes lists.
3223 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
3224 be more efficient. Formerly it was quadratic in the number of
3225 servers; now it should be linear. Fixes bug 509.
3226 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
3227 and n_conn_id_digest fields into a separate structure that's
3228 only needed when the circuit has not yet attached to an n_conn.
3231 - Change the contrib/tor.logrotate script so it makes the new
3232 logs as "_tor:_tor" rather than the default, which is generally
3233 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
3234 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
3235 warnings (occasionally), but it can also cause the compiler to
3236 eliminate error-checking code. Suggested by Peter Gutmann.
3237 - When a hidden service is giving up on an introduction point candidate
3238 that was not included in the last published rendezvous descriptor,
3239 don't reschedule publication of the next descriptor. Fixes bug 763.
3241 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
3242 HiddenServiceExcludeNodes as obsolete: they never worked properly,
3243 and nobody claims to be using them. Fixes bug 754. Bugfix on
3244 0.1.0.1-rc. Patch from Christian Wilms.
3245 - Fix a small alignment and memory-wasting bug on buffer chunks.
3248 o Minor bugfixes (controller):
3249 - When closing an application-side connection because its circuit
3250 is getting torn down, generate the stream event correctly.
3251 Bugfix on 0.1.2.x. Anonymous patch.
3254 - Remove all backward-compatibility code to support relays running
3255 versions of Tor so old that they no longer work at all on the
3259 Changes in version 0.2.0.30 - 2008-07-15
3261 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
3262 warnings (occasionally), but it can also cause the compiler to
3263 eliminate error-checking code. Suggested by Peter Gutmann.
3266 Changes in version 0.2.0.29-rc - 2008-07-08
3267 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
3268 hidden-service performance bugs, and fixes a bunch of smaller bugs.
3271 - If you have more than one bridge but don't know their keys,
3272 you would only launch a request for the descriptor of the first one
3273 on your list. (Tor considered launching requests for the others, but
3274 found that it already had a connection on the way for $0000...0000
3275 so it didn't open another.) Bugfix on 0.2.0.x.
3276 - If you have more than one bridge but don't know their keys, and the
3277 connection to one of the bridges failed, you would cancel all
3278 pending bridge connections. (After all, they all have the same
3279 digest.) Bugfix on 0.2.0.x.
3280 - When a hidden service was trying to establish an introduction point,
3281 and Tor had built circuits preemptively for such purposes, we
3282 were ignoring all the preemptive circuits and launching a new one
3283 instead. Bugfix on 0.2.0.14-alpha.
3284 - When a hidden service was trying to establish an introduction point,
3285 and Tor *did* manage to reuse one of the preemptively built
3286 circuits, it didn't correctly remember which one it used,
3287 so it asked for another one soon after, until there were no
3288 more preemptive circuits, at which point it launched one from
3289 scratch. Bugfix on 0.0.9.x.
3290 - Make directory servers include the X-Your-Address-Is: http header in
3291 their responses even for begin_dir conns. Now clients who only
3292 ever use begin_dir connections still have a way to learn their IP
3293 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
3296 - Fix a macro/CPP interaction that was confusing some compilers:
3297 some GCCs don't like #if/#endif pairs inside macro arguments.
3299 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
3300 Fixes bug 704; fix from Steven Murdoch.
3301 - When opening /dev/null in finish_daemonize(), do not pass the
3302 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
3303 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
3304 - Correctly detect transparent proxy support on Linux hosts that
3305 require in.h to be included before netfilter_ipv4.h. Patch
3307 - Disallow session resumption attempts during the renegotiation
3308 stage of the v2 handshake protocol. Clients should never be trying
3309 session resumption at this point, but apparently some did, in
3310 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
3311 found by Geoff Goodell.
3314 Changes in version 0.2.1.2-alpha - 2008-06-20
3315 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
3316 make it easier to set up your own private Tor network; fixes several
3317 big bugs with using more than one bridge relay; fixes a big bug with
3318 offering hidden services quickly after Tor starts; and uses a better
3319 API for reporting potential bootstrapping problems to the controller.
3322 - New TestingTorNetwork config option to allow adjustment of
3323 previously constant values that, while reasonable, could slow
3324 bootstrapping. Implements proposal 135. Patch from Karsten.
3327 - If you have more than one bridge but don't know their digests,
3328 you would only learn a request for the descriptor of the first one
3329 on your list. (Tor considered launching requests for the others, but
3330 found that it already had a connection on the way for $0000...0000
3331 so it didn't open another.) Bugfix on 0.2.0.x.
3332 - If you have more than one bridge but don't know their digests,
3333 and the connection to one of the bridges failed, you would cancel
3334 all pending bridge connections. (After all, they all have the
3335 same digest.) Bugfix on 0.2.0.x.
3336 - When establishing a hidden service, introduction points that
3337 originate from cannibalized circuits are completely ignored and not
3338 included in rendezvous service descriptors. This might be another
3339 reason for delay in making a hidden service available. Bugfix
3340 from long ago (0.0.9.x?)
3343 - Allow OpenSSL to use dynamic locks if it wants.
3344 - When building a consensus, do not include routers that are down.
3345 This will cut down 30% to 40% on consensus size. Implements
3347 - In directory authorities' approved-routers files, allow
3348 fingerprints with or without space.
3349 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
3350 controller can query our current bootstrap state in case it attaches
3351 partway through and wants to catch up.
3352 - Send an initial "Starting" bootstrap status event, so we have a
3353 state to start out in.
3356 - Asking for a conditional consensus at .../consensus/<fingerprints>
3357 would crash a dirserver if it did not already have a
3358 consensus. Bugfix on 0.2.1.1-alpha.
3359 - Clean up some macro/CPP interactions: some GCC versions don't like
3360 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
3363 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
3364 - Directory authorities shouldn't complain about bootstrapping
3365 problems just because they do a lot of reachability testing and
3366 some of the connection attempts fail.
3367 - Start sending "count" and "recommendation" key/value pairs in
3368 bootstrap problem status events, so the controller can hear about
3369 problems even before Tor decides they're worth reporting for sure.
3370 - If you're using bridges, generate "bootstrap problem" warnings
3371 as soon as you run out of working bridges, rather than waiting
3372 for ten failures -- which will never happen if you have less than
3374 - If we close our OR connection because there's been a circuit
3375 pending on it for too long, we were telling our bootstrap status
3376 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
3379 Changes in version 0.2.1.1-alpha - 2008-06-13
3380 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
3381 were making the Tor process bloat especially on Linux; makes our TLS
3382 handshake blend in better; sends "bootstrap phase" status events to
3383 the controller, so it can keep the user informed of progress (and
3384 problems) fetching directory information and establishing circuits;
3385 and adds a variety of smaller features.
3388 - More work on making our TLS handshake blend in: modify the list
3389 of ciphers advertised by OpenSSL in client mode to even more
3390 closely resemble a common web browser. We cheat a little so that
3391 we can advertise ciphers that the locally installed OpenSSL doesn't
3393 - Start sending "bootstrap phase" status events to the controller,
3394 so it can keep the user informed of progress fetching directory
3395 information and establishing circuits. Also inform the controller
3396 if we think we're stuck at a particular bootstrap phase. Implements
3398 - Resume using OpenSSL's RAND_poll() for better (and more portable)
3399 cross-platform entropy collection again. We used to use it, then
3400 stopped using it because of a bug that could crash systems that
3401 called RAND_poll when they had a lot of fds open. It looks like the
3402 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
3403 at startup, and to call RAND_poll() when we reseed later only if
3404 we have a non-buggy OpenSSL version.
3407 - When we choose to abandon a new entry guard because we think our
3408 older ones might be better, close any circuits pending on that
3409 new entry guard connection. This fix should make us recover much
3410 faster when our network is down and then comes back. Bugfix on
3411 0.1.2.8-beta; found by lodger.
3413 o Memory fixes and improvements:
3414 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
3415 to avoid unused RAM in buffer chunks and memory pools.
3416 - Speed up parsing and cut down on memory fragmentation by using
3417 stack-style allocations for parsing directory objects. Previously,
3418 this accounted for over 40% of allocations from within Tor's code
3419 on a typical directory cache.
3420 - Use a Bloom filter rather than a digest-based set to track which
3421 descriptors we need to keep around when we're cleaning out old
3422 router descriptors. This speeds up the computation significantly,
3423 and may reduce fragmentation.
3424 - Reduce the default smartlist size from 32 to 16; it turns out that
3425 most smartlists hold around 8-12 elements tops.
3426 - Make dumpstats() log the fullness and size of openssl-internal
3428 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
3429 patch to their OpenSSL, turn it on to save memory on servers. This
3430 patch will (with any luck) get included in a mainline distribution
3432 - Never use OpenSSL compression: it wastes RAM and CPU trying to
3433 compress cells, which are basically all encrypted, compressed,
3437 - Stop reloading the router list from disk for no reason when we
3438 run out of reachable directory mirrors. Once upon a time reloading
3439 it would set the 'is_running' flag back to 1 for them. It hasn't
3440 done that for a long time.
3441 - In very rare situations new hidden service descriptors were
3442 published earlier than 30 seconds after the last change to the
3443 service. (We currently think that a hidden service descriptor
3444 that's been stable for 30 seconds is worth publishing.)
3447 - Allow separate log levels to be configured for different logging
3448 domains. For example, this allows one to log all notices, warnings,
3449 or errors, plus all memory management messages of level debug or
3450 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
3451 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
3452 and stop using a warning that had become unfixably verbose under
3454 - New --hush command-line option similar to --quiet. While --quiet
3455 disables all logging to the console on startup, --hush limits the
3456 output to messages of warning and error severity.
3457 - Servers support a new URL scheme for consensus downloads that
3458 allows the client to specify which authorities are trusted.
3459 The server then only sends the consensus if the client will trust
3460 it. Otherwise a 404 error is sent back. Clients use this
3461 new scheme when the server supports it (meaning it's running
3462 0.2.1.1-alpha or later). Implements proposal 134.
3463 - New configure/torrc options (--enable-geoip-stats,
3464 DirRecordUsageByCountry) to record how many IPs we've served
3465 directory info to in each country code, how many status documents
3466 total we've sent to each country code, and what share of the total
3467 directory requests we should expect to see.
3468 - Use the TLS1 hostname extension to more closely resemble browser
3470 - Lots of new unit tests.
3471 - Add a macro to implement the common pattern of iterating through
3472 two parallel lists in lockstep.
3475 Changes in version 0.2.0.28-rc - 2008-06-13
3476 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
3477 performance bug, and fixes a bunch of smaller bugs.
3480 - Fix a bug where, when we were choosing the 'end stream reason' to
3481 put in our relay end cell that we send to the exit relay, Tor
3482 clients on Windows were sometimes sending the wrong 'reason'. The
3483 anonymity problem is that exit relays may be able to guess whether
3484 the client is running Windows, thus helping partition the anonymity
3485 set. Down the road we should stop sending reasons to exit relays,
3486 or otherwise prevent future versions of this bug.
3489 - While setting up a hidden service, some valid introduction circuits
3490 were overlooked and abandoned. This might be the reason for
3491 the long delay in making a hidden service available. Bugfix on
3495 - Update to the "June 9 2008" ip-to-country file.
3496 - Run 'make test' as part of 'make dist', so we stop releasing so
3497 many development snapshots that fail their unit tests.
3500 - When we're checking if we have enough dir info for each relay
3501 to begin establishing circuits, make sure that we actually have
3502 the descriptor listed in the consensus, not just any descriptor.
3504 - Bridge relays no longer print "xx=0" in their extrainfo document
3505 for every single country code in the geoip db. Bugfix on
3507 - Only warn when we fail to load the geoip file if we were planning to
3508 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
3509 - If we change our MaxAdvertisedBandwidth and then reload torrc,
3510 Tor won't realize it should publish a new relay descriptor. Fixes
3511 bug 688, reported by mfr. Bugfix on 0.1.2.x.
3512 - When we haven't had any application requests lately, don't bother
3513 logging that we have expired a bunch of descriptors. Bugfix
3515 - Make relay cells written on a connection count as non-padding when
3516 tracking how long a connection has been in use. Bugfix on
3517 0.2.0.1-alpha. Spotted by lodger.
3518 - Fix unit tests in 0.2.0.27-rc.
3519 - Fix compile on Windows.
3522 Changes in version 0.2.0.27-rc - 2008-06-03
3523 Tor 0.2.0.27-rc adds a few features we left out of the earlier
3524 release candidates. In particular, we now include an IP-to-country
3525 GeoIP database, so controllers can easily look up what country a
3526 given relay is in, and so bridge relays can give us some sanitized
3527 summaries about which countries are making use of bridges. (See proposal
3528 126-geoip-fetching.txt for details.)
3531 - Include an IP-to-country GeoIP file in the tarball, so bridge
3532 relays can report sanitized summaries of the usage they're seeing.
3535 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
3536 Robert Hogan. Fixes the first part of bug 681.
3537 - Make bridge authorities never serve extrainfo docs.
3538 - Add support to detect Libevent versions in the 1.4.x series
3540 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
3541 - Include a new contrib/tor-exit-notice.html file that exit relay
3542 operators can put on their website to help reduce abuse queries.
3545 - When tunneling an encrypted directory connection, and its first
3546 circuit fails, do not leave it unattached and ask the controller
3547 to deal. Fixes the second part of bug 681.
3548 - Make bridge authorities correctly expire old extrainfo documents
3552 Changes in version 0.2.0.26-rc - 2008-05-13
3553 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
3554 in Debian's OpenSSL packages. All users running any 0.2.0.x version
3555 should upgrade, whether they're running Debian or not.
3557 o Major security fixes:
3558 - Use new V3 directory authority keys on the tor26, gabelmoo, and
3559 moria1 V3 directory authorities. The old keys were generated with
3560 a vulnerable version of Debian's OpenSSL package, and must be
3561 considered compromised. Other authorities' keys were not generated
3562 with an affected version of OpenSSL.
3565 - List authority signatures as "unrecognized" based on DirServer
3566 lines, not on cert cache. Bugfix on 0.2.0.x.
3569 - Add a new V3AuthUseLegacyKey option to make it easier for
3570 authorities to change their identity keys if they have to.
3573 Changes in version 0.2.0.25-rc - 2008-04-23
3574 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
3577 - Remember to initialize threading before initializing logging.
3578 Otherwise, many BSD-family implementations will crash hard on
3579 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
3582 - Authorities correctly free policies on bad servers on
3583 exit. Fixes bug 672. Bugfix on 0.2.0.x.
3586 Changes in version 0.2.0.24-rc - 2008-04-22
3587 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
3588 v3 directory authority, makes relays with dynamic IP addresses and no
3589 DirPort notice more quickly when their IP address changes, fixes a few
3590 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
3592 o New directory authorities:
3593 - Take lefkada out of the list of v3 directory authorities, since
3594 it has been down for months.
3595 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
3599 - Detect address changes more quickly on non-directory mirror
3600 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
3602 o Minor features (security):
3603 - Reject requests for reverse-dns lookup of names that are in
3604 a private address space. Patch from lodger.
3605 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
3608 o Minor bugfixes (crashes):
3609 - Avoid a rare assert that can trigger when Tor doesn't have much
3610 directory information yet and it tries to fetch a v2 hidden
3611 service descriptor. Fixes bug 651, reported by nwf.
3612 - Initialize log mutex before initializing dmalloc. Otherwise,
3613 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
3614 - Use recursive pthread mutexes in order to avoid deadlock when
3615 logging debug-level messages to a controller. Bug spotted by nwf,
3616 bugfix on 0.2.0.16-alpha.
3618 o Minor bugfixes (resource management):
3619 - Keep address policies from leaking memory: start their refcount
3620 at 1, not 2. Bugfix on 0.2.0.16-alpha.
3621 - Free authority certificates on exit, so they don't look like memory
3622 leaks. Bugfix on 0.2.0.19-alpha.
3623 - Free static hashtables for policy maps and for TLS connections on
3624 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
3625 - Avoid allocating extra space when computing consensuses on 64-bit
3626 platforms. Bug spotted by aakova.
3628 o Minor bugfixes (misc):
3629 - Do not read the configuration file when we've only been told to
3630 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
3631 based on patch from Sebastian Hahn.
3632 - Exit relays that are used as a client can now reach themselves
3633 using the .exit notation, rather than just launching an infinite
3634 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
3635 - When attempting to open a logfile fails, tell us why.
3636 - Fix a dumb bug that was preventing us from knowing that we should
3637 preemptively build circuits to handle expected directory requests.
3638 Fixes bug 660. Bugfix on 0.1.2.x.
3639 - Warn less verbosely about clock skew from netinfo cells from
3640 untrusted sources. Fixes bug 663.
3641 - Make controller stream events for DNS requests more consistent,
3642 by adding "new stream" events for DNS requests, and removing
3643 spurious "stream closed" events" for cached reverse resolves.
3644 Patch from mwenge. Fixes bug 646.
3645 - Correctly notify one-hop connections when a circuit build has
3646 failed. Possible fix for bug 669. Found by lodger.
3649 Changes in version 0.2.0.23-rc - 2008-03-24
3650 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
3651 makes bootstrapping faster if the first directory mirror you contact
3652 is down. The bundles also include the new Vidalia 0.1.2 release.
3655 - When a tunneled directory request is made to a directory server
3656 that's down, notice after 30 seconds rather than 120 seconds. Also,
3657 fail any begindir streams that are pending on it, so they can
3658 retry elsewhere. This was causing multi-minute delays on bootstrap.
3661 Changes in version 0.2.0.22-rc - 2008-03-18
3662 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
3663 enables encrypted directory connections by default for non-relays, fixes
3664 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
3665 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
3668 - Enable encrypted directory connections by default for non-relays,
3669 so censor tools that block Tor directory connections based on their
3670 plaintext patterns will no longer work. This means Tor works in
3671 certain censored countries by default again.
3674 - Make sure servers always request certificates from clients during
3675 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
3676 - Do not enter a CPU-eating loop when a connection is closed in
3677 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
3678 diagnosed by lodger; bugfix on 0.2.0.20-rc.
3679 - Fix assertion failure that could occur when a blocked circuit
3680 became unblocked, and it had pending client DNS requests. Bugfix
3681 on 0.2.0.1-alpha. Fixes bug 632.
3683 o Minor bugfixes (on 0.1.2.x):
3684 - Generate "STATUS_SERVER" events rather than misspelled
3685 "STATUS_SEVER" events. Caught by mwenge.
3686 - When counting the number of bytes written on a TLS connection,
3687 look at the BIO actually used for writing to the network, not
3688 at the BIO used (sometimes) to buffer data for the network.
3689 Looking at different BIOs could result in write counts on the
3690 order of ULONG_MAX. Fixes bug 614.
3691 - On Windows, correctly detect errors when listing the contents of
3692 a directory. Fix from lodger.
3694 o Minor bugfixes (on 0.2.0.x):
3695 - Downgrade "sslv3 alert handshake failure" message to INFO.
3696 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
3697 left BandwidthRate and BandwidthBurst at the default, we would be
3698 silently limited by those defaults. Now raise them to match the
3699 RelayBandwidth* values.
3700 - Fix the SVK version detection logic to work correctly on a branch.
3701 - Make --enable-openbsd-malloc work correctly on Linux with alpha
3702 CPUs. Fixes bug 625.
3703 - Logging functions now check that the passed severity is sane.
3704 - Use proper log levels in the testsuite call of
3705 get_interface_address6().
3706 - When using a nonstandard malloc, do not use the platform values for
3707 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
3708 - Make the openbsd malloc code use 8k pages on alpha CPUs and
3710 - Detect mismatched page sizes when using --enable-openbsd-malloc.
3711 - Avoid double-marked-for-close warning when certain kinds of invalid
3712 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
3713 for bug 617. Bugfix on 0.2.0.1-alpha.
3714 - Make sure that the "NULL-means-reject *:*" convention is followed by
3715 all the policy manipulation functions, avoiding some possible crash
3716 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
3717 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
3718 actually works, and doesn't warn about every single reverse lookup.
3719 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
3722 - Only log guard node status when guard node status has changed.
3723 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
3724 make "INFO" 75% less verbose.
3727 Changes in version 0.2.0.21-rc - 2008-03-02
3728 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
3729 makes Tor work well with Vidalia again, fixes a rare assert bug,
3730 and fixes a pair of more minor bugs. The bundles also include Vidalia
3731 0.1.0 and Torbutton 1.1.16.
3734 - The control port should declare that it requires password auth
3735 when HashedControlSessionPassword is set too. Patch from Matt Edman;
3736 bugfix on 0.2.0.20-rc. Fixes bug 615.
3737 - Downgrade assert in connection_buckets_decrement() to a log message.
3738 This may help us solve bug 614, and in any case will make its
3739 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
3740 - We were sometimes miscounting the number of bytes read from the
3741 network, causing our rate limiting to not be followed exactly.
3742 Bugfix on 0.2.0.16-alpha. Reported by lodger.
3745 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
3746 OpenSSL versions should have been working fine. Diagnosis and patch
3747 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
3748 Bugfix on 0.2.0.20-rc.
3751 Changes in version 0.2.0.20-rc - 2008-02-24
3752 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
3753 makes more progress towards normalizing Tor's TLS handshake, makes
3754 hidden services work better again, helps relays bootstrap if they don't
3755 know their IP address, adds optional support for linking in openbsd's
3756 allocator or tcmalloc, allows really fast relays to scale past 15000
3757 sockets, and fixes a bunch of minor bugs reported by Veracode.
3760 - Enable the revised TLS handshake based on the one designed by
3761 Steven Murdoch in proposal 124, as revised in proposal 130. It
3762 includes version negotiation for OR connections as described in
3763 proposal 105. The new handshake is meant to be harder for censors
3764 to fingerprint, and it adds the ability to detect certain kinds of
3765 man-in-the-middle traffic analysis attacks. The version negotiation
3766 feature will allow us to improve Tor's link protocol more safely
3768 - Choose which bridge to use proportional to its advertised bandwidth,
3769 rather than uniformly at random. This should speed up Tor for
3770 bridge users. Also do this for people who set StrictEntryNodes.
3771 - When a TrackHostExits-chosen exit fails too many times in a row,
3772 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
3775 - Resolved problems with (re-)fetching hidden service descriptors.
3776 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
3778 - If we only ever used Tor for hidden service lookups or posts, we
3779 would stop building circuits and start refusing connections after
3780 24 hours, since we falsely believed that Tor was dormant. Reported
3781 by nwf; bugfix on 0.1.2.x.
3782 - Servers that don't know their own IP address should go to the
3783 authorities for their first directory fetch, even if their DirPort
3784 is off or if they don't know they're reachable yet. This will help
3785 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
3786 - When counting the number of open sockets, count not only the number
3787 of sockets we have received from the socket() call, but also
3788 the number we've gotten from accept() and socketpair(). This bug
3789 made us fail to count all sockets that we were using for incoming
3790 connections. Bugfix on 0.2.0.x.
3791 - Fix code used to find strings within buffers, when those strings
3792 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
3793 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
3794 - Add a new __HashedControlSessionPassword option for controllers
3795 to use for one-off session password hashes that shouldn't get
3796 saved to disk by SAVECONF --- Vidalia users were accumulating a
3797 pile of HashedControlPassword lines in their torrc files, one for
3798 each time they had restarted Tor and then clicked Save. Make Tor
3799 automatically convert "HashedControlPassword" to this new option but
3800 only when it's given on the command line. Partial fix for bug 586.
3802 o Minor features (performance):
3803 - Tune parameters for cell pool allocation to minimize amount of
3805 - Add OpenBSD malloc code from phk as an optional malloc
3806 replacement on Linux: some glibc libraries do very poorly
3807 with Tor's memory allocation patterns. Pass
3808 --enable-openbsd-malloc to get the replacement malloc code.
3809 - Add a --with-tcmalloc option to the configure script to link
3810 against tcmalloc (if present). Does not yet search for
3811 non-system include paths.
3812 - Stop imposing an arbitrary maximum on the number of file descriptors
3813 used for busy servers. Bug reported by Olaf Selke; patch from
3816 o Minor features (other):
3817 - When SafeLogging is disabled, log addresses along with all TLS
3819 - When building with --enable-gcc-warnings, check for whether Apple's
3820 warning "-Wshorten-64-to-32" is available.
3821 - Add a --passphrase-fd argument to the tor-gencert command for
3824 o Minor bugfixes (memory leaks and code problems):
3825 - We were leaking a file descriptor if Tor started with a zero-length
3826 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
3827 - Detect size overflow in zlib code. Reported by Justin Ferguson and
3829 - We were comparing the raw BridgePassword entry with a base64'ed
3830 version of it, when handling a "/tor/networkstatus-bridges"
3831 directory request. Now compare correctly. Noticed by Veracode.
3832 - Recover from bad tracked-since value in MTBF-history file.
3834 - Alter the code that tries to recover from unhandled write
3835 errors, to not try to flush onto a socket that's given us
3836 unhandled errors. Bugfix on 0.1.2.x.
3837 - Make Unix controlsockets work correctly on OpenBSD. Patch from
3838 tup. Bugfix on 0.2.0.3-alpha.
3840 o Minor bugfixes (other):
3841 - If we have an extra-info document for our server, always make
3842 it available on the control port, even if we haven't gotten
3843 a copy of it from an authority yet. Patch from mwenge.
3844 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
3845 - Directory mirrors no longer include a guess at the client's IP
3846 address if the connection appears to be coming from the same /24
3847 network; it was producing too many wrong guesses.
3848 - Make the new hidden service code respect the SafeLogging setting.
3849 Bugfix on 0.2.0.x. Patch from Karsten.
3850 - When starting as an authority, do not overwrite all certificates
3851 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
3852 - If we're trying to flush the last bytes on a connection (for
3853 example, when answering a directory request), reset the
3854 time-to-give-up timeout every time we manage to write something
3855 on the socket. Bugfix on 0.1.2.x.
3856 - Change the behavior of "getinfo status/good-server-descriptor"
3857 so it doesn't return failure when any authority disappears.
3858 - Even though the man page said that "TrackHostExits ." should
3859 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
3860 - Report TLS "zero return" case as a "clean close" and "IO error"
3861 as a "close". Stop calling closes "unexpected closes": existing
3862 Tors don't use SSL_close(), so having a connection close without
3863 the TLS shutdown handshake is hardly unexpected.
3864 - Send NAMESERVER_STATUS messages for a single failed nameserver
3867 o Code simplifications and refactoring:
3868 - Remove the tor_strpartition function: its logic was confused,
3869 and it was only used for one thing that could be implemented far
3873 Changes in version 0.2.0.19-alpha - 2008-02-09
3874 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
3875 handshake, makes path selection for relays more secure and IP address
3876 guessing more robust, and generally fixes a lot of bugs in preparation
3877 for calling the 0.2.0 branch stable.
3880 - Do not include recognizeable strings in the commonname part of
3881 Tor's x509 certificates.
3884 - If we're a relay, avoid picking ourselves as an introduction point,
3885 a rendezvous point, or as the final hop for internal circuits. Bug
3886 reported by taranis and lodger. Bugfix on 0.1.2.x.
3887 - Patch from "Andrew S. Lists" to catch when we contact a directory
3888 mirror at IP address X and he says we look like we're coming from
3889 IP address X. Bugfix on 0.1.2.x.
3891 o Minor features (security):
3892 - Be more paranoid about overwriting sensitive memory on free(),
3893 as a defensive programming tactic to ensure forward secrecy.
3895 o Minor features (directory authority):
3896 - Actually validate the options passed to AuthDirReject,
3897 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
3898 - Reject router descriptors with out-of-range bandwidthcapacity or
3899 bandwidthburst values.
3901 o Minor features (controller):
3902 - Reject controller commands over 1MB in length. This keeps rogue
3903 processes from running us out of memory.
3905 o Minor features (misc):
3906 - Give more descriptive well-formedness errors for out-of-range
3907 hidden service descriptor/protocol versions.
3908 - Make memory debugging information describe more about history
3909 of cell allocation, so we can help reduce our memory use.
3911 o Deprecated features (controller):
3912 - The status/version/num-versioning and status/version/num-concurring
3913 GETINFO options are no longer useful in the v3 directory protocol:
3914 treat them as deprecated, and warn when they're used.
3917 - When our consensus networkstatus has been expired for a while, stop
3918 being willing to build circuits using it. Fixes bug 401. Bugfix
3920 - Directory caches now fetch certificates from all authorities
3921 listed in a networkstatus consensus, even when they do not
3922 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
3923 - When connecting to a bridge without specifying its key, insert
3924 the connection into the identity-to-connection map as soon as
3925 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
3926 - Detect versions of OS X where malloc_good_size() is present in the
3927 library but never actually declared. Resolves bug 587. Bugfix
3929 - Stop incorrectly truncating zlib responses to directory authority
3930 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
3931 - Stop recommending that every server operator send mail to tor-ops.
3932 Resolves bug 597. Bugfix on 0.1.2.x.
3933 - Don't trigger an assert if we start a directory authority with a
3934 private IP address (like 127.0.0.1).
3935 - Avoid possible failures when generating a directory with routers
3936 with over-long versions strings, or too many flags set. Bugfix
3938 - If an attempt to launch a DNS resolve request over the control
3939 port fails because we have overrun the limit on the number of
3940 connections, tell the controller that the request has failed.
3941 - Avoid using too little bandwidth when our clock skips a few
3942 seconds. Bugfix on 0.1.2.x.
3943 - Fix shell error when warning about missing packages in configure
3944 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
3945 - Do not become confused when receiving a spurious VERSIONS-like
3946 cell from a confused v1 client. Bugfix on 0.2.0.x.
3947 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
3948 introduction points for a hidden service have failed. Patch from
3949 Karsten Loesing. Bugfix on 0.2.0.x.
3951 o Code simplifications and refactoring:
3952 - Remove some needless generality from cpuworker code, for improved
3954 - Stop overloading the circuit_t.onionskin field for both "onionskin
3955 from a CREATE cell that we are waiting for a cpuworker to be
3956 assigned" and "onionskin from an EXTEND cell that we are going to
3957 send to an OR as soon as we are connected". Might help with bug 600.
3958 - Add an in-place version of aes_crypt() so that we can avoid doing a
3959 needless memcpy() call on each cell payload.
3962 Changes in version 0.2.0.18-alpha - 2008-01-25
3963 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
3964 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
3965 that can warn or reject connections to ports generally associated with
3966 vulnerable-plaintext protocols.
3968 o New directory authorities:
3969 - Set up dannenberg (run by CCC) as the sixth v3 directory
3973 - Fix a major memory leak when attempting to use the v2 TLS
3974 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
3975 - We accidentally enabled the under-development v2 TLS handshake
3976 code, which was causing log entries like "TLS error while
3977 renegotiating handshake". Disable it again. Resolves bug 590.
3978 - We were computing the wrong Content-Length: header for directory
3979 responses that need to be compressed on the fly, causing clients
3980 asking for those items to always fail. Bugfix on 0.2.0.x; partially
3984 - Avoid going directly to the directory authorities even if you're a
3985 relay, if you haven't found yourself reachable yet or if you've
3986 decided not to advertise your dirport yet. Addresses bug 556.
3987 - If we've gone 12 hours since our last bandwidth check, and we
3988 estimate we have less than 50KB bandwidth capacity but we could
3989 handle more, do another bandwidth test.
3990 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
3991 Tor can warn and/or refuse connections to ports commonly used with
3992 vulnerable-plaintext protocols. Currently we warn on ports 23,
3993 109, 110, and 143, but we don't reject any.
3996 - When we setconf ClientOnly to 1, close any current OR and Dir
3997 listeners. Reported by mwenge.
3998 - When we get a consensus that's been signed by more people than
3999 we expect, don't log about it; it's not a big deal. Reported
4003 - Don't answer "/tor/networkstatus-bridges" directory requests if
4004 the request isn't encrypted.
4005 - Make "ClientOnly 1" config option disable directory ports too.
4006 - Patches from Karsten Loesing to make v2 hidden services more
4007 robust: work even when there aren't enough HSDir relays available;
4008 retry when a v2 rend desc fetch fails; but don't retry if we
4009 already have a usable v0 rend desc.
4012 Changes in version 0.2.0.17-alpha - 2008-01-17
4013 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
4016 - Make the tor-gencert man page get included correctly in the tarball.
4019 Changes in version 0.2.0.16-alpha - 2008-01-17
4020 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
4021 Loesing, and generally cleans up a lot of features and minor bugs.
4023 o New directory authorities:
4024 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
4027 o Major performance improvements:
4028 - Switch our old ring buffer implementation for one more like that
4029 used by free Unix kernels. The wasted space in a buffer with 1mb
4030 of data will now be more like 8k than 1mb. The new implementation
4031 also avoids realloc();realloc(); patterns that can contribute to
4032 memory fragmentation.
4035 - Configuration files now accept C-style strings as values. This
4036 helps encode characters not allowed in the current configuration
4037 file format, such as newline or #. Addresses bug 557.
4038 - Although we fixed bug 539 (where servers would send HTTP status 503
4039 responses _and_ send a body too), there are still servers out
4040 there that haven't upgraded. Therefore, make clients parse such
4041 bodies when they receive them.
4042 - When we're not serving v2 directory information, there is no reason
4043 to actually keep any around. Remove the obsolete files and directory
4044 on startup if they are very old and we aren't going to serve them.
4046 o Minor performance improvements:
4047 - Reference-count and share copies of address policy entries; only 5%
4048 of them were actually distinct.
4049 - Never walk through the list of logs if we know that no log is
4050 interested in a given message.
4053 - When an authority has not signed a consensus, do not try to
4054 download a nonexistent "certificate with key 00000000". Bugfix
4055 on 0.2.0.x. Fixes bug 569.
4056 - Fix a rare assert error when we're closing one of our threads:
4057 use a mutex to protect the list of logs, so we never write to the
4058 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
4059 bug 575, which is kind of the revenge of bug 222.
4060 - Patch from Karsten Loesing to complain less at both the client
4061 and the relay when a relay used to have the HSDir flag but doesn't
4062 anymore, and we try to upload a hidden service descriptor.
4063 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
4065 - Do not try to download missing certificates until we have tried
4066 to check our fallback consensus. Fixes bug 583.
4067 - Make bridges round reported GeoIP stats info up to the nearest
4068 estimate, not down. Now we can distinguish between "0 people from
4069 this country" and "1 person from this country".
4070 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
4071 - Avoid possible segfault if key generation fails in
4072 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
4073 - Avoid segfault in the case where a badly behaved v2 versioning
4074 directory sends a signed networkstatus with missing client-versions.
4076 - Avoid segfaults on certain complex invocations of
4077 router_get_by_hexdigest(). Bugfix on 0.1.2.
4078 - Correct bad index on array access in parse_http_time(). Bugfix
4080 - Fix possible bug in vote generation when server versions are present
4081 but client versions are not.
4082 - Fix rare bug on REDIRECTSTREAM control command when called with no
4083 port set: it could erroneously report an error when none had
4085 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
4086 compressing large objects and find ourselves with more than 4k
4087 left over. Bugfix on 0.2.0.
4088 - Fix a small memory leak when setting up a hidden service.
4089 - Fix a few memory leaks that could in theory happen under bizarre
4091 - Fix an assert if we post a general-purpose descriptor via the
4092 control port but that descriptor isn't mentioned in our current
4093 network consensus. Bug reported by Jon McLachlan; bugfix on
4096 o Minor features (controller):
4097 - Get NS events working again. Patch from tup.
4098 - The GETCONF command now escapes and quotes configuration values
4099 that don't otherwise fit into the torrc file.
4100 - The SETCONF command now handles quoted values correctly.
4102 o Minor features (directory authorities):
4103 - New configuration options to override default maximum number of
4104 servers allowed on a single IP address. This is important for
4105 running a test network on a single host.
4106 - Actually implement the -s option to tor-gencert.
4107 - Add a manual page for tor-gencert.
4109 o Minor features (bridges):
4110 - Bridge authorities no longer serve bridge descriptors over
4111 unencrypted connections.
4113 o Minor features (other):
4114 - Add hidden services and DNSPorts to the list of things that make
4115 Tor accept that it has running ports. Change starting Tor with no
4116 ports from a fatal error to a warning; we might change it back if
4117 this turns out to confuse anybody. Fixes bug 579.
4120 Changes in version 0.1.2.19 - 2008-01-17
4121 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
4122 exit policy a little bit more conservative so it's safer to run an
4123 exit relay on a home system, and fixes a variety of smaller issues.
4126 - Exit policies now reject connections that are addressed to a
4127 relay's public (external) IP address too, unless
4128 ExitPolicyRejectPrivate is turned off. We do this because too
4129 many relays are running nearby to services that trust them based
4133 - When the clock jumps forward a lot, do not allow the bandwidth
4134 buckets to become negative. Fixes bug 544.
4135 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
4136 on every successful resolve. Reported by Mike Perry.
4137 - Purge old entries from the "rephist" database and the hidden
4138 service descriptor database even when DirPort is zero.
4139 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
4140 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
4141 crashing or mis-answering these requests.
4142 - When we decide to send a 503 response to a request for servers, do
4143 not then also send the server descriptors: this defeats the whole
4144 purpose. Fixes bug 539.
4147 - Changing the ExitPolicyRejectPrivate setting should cause us to
4148 rebuild our server descriptor.
4149 - Fix handling of hex nicknames when answering controller requests for
4150 networkstatus by name, or when deciding whether to warn about
4151 unknown routers in a config option. (Patch from mwenge.)
4152 - Fix a couple of hard-to-trigger autoconf problems that could result
4153 in really weird results on platforms whose sys/types.h files define
4154 nonstandard integer types.
4155 - Don't try to create the datadir when running --verify-config or
4156 --hash-password. Resolves bug 540.
4157 - If we were having problems getting a particular descriptor from the
4158 directory caches, and then we learned about a new descriptor for
4159 that router, we weren't resetting our failure count. Reported
4161 - Although we fixed bug 539 (where servers would send HTTP status 503
4162 responses _and_ send a body too), there are still servers out there
4163 that haven't upgraded. Therefore, make clients parse such bodies
4164 when they receive them.
4165 - Run correctly on systems where rlim_t is larger than unsigned long.
4166 This includes some 64-bit systems.
4167 - Run correctly on platforms (like some versions of OS X 10.5) where
4168 the real limit for number of open files is OPEN_FILES, not rlim_max
4169 from getrlimit(RLIMIT_NOFILES).
4170 - Avoid a spurious free on base64 failure.
4171 - Avoid segfaults on certain complex invocations of
4172 router_get_by_hexdigest().
4173 - Fix rare bug on REDIRECTSTREAM control command when called with no
4174 port set: it could erroneously report an error when none had
4178 Changes in version 0.2.0.15-alpha - 2007-12-25
4179 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
4180 features added in 0.2.0.13-alpha.
4183 - Fix several remotely triggerable asserts based on DirPort requests
4184 for a v2 or v3 networkstatus object before we were prepared. This
4185 was particularly bad for 0.2.0.13 and later bridge relays, who
4186 would never have a v2 networkstatus and would thus always crash
4187 when used. Bugfixes on 0.2.0.x.
4188 - Estimate the v3 networkstatus size more accurately, rather than
4189 estimating it at zero bytes and giving it artificially high priority
4190 compared to other directory requests. Bugfix on 0.2.0.x.
4193 - Fix configure.in logic for cross-compilation.
4194 - When we load a bridge descriptor from the cache, and it was
4195 previously unreachable, mark it as retriable so we won't just
4196 ignore it. Also, try fetching a new copy immediately. Bugfixes
4198 - The bridge GeoIP stats were counting other relays, for example
4199 self-reachability and authority-reachability tests.
4202 - Support compilation to target iPhone; patch from cjacker huang.
4203 To build for iPhone, pass the --enable-iphone option to configure.
4206 Changes in version 0.2.0.14-alpha - 2007-12-23
4208 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
4209 without a datadirectory from a previous Tor install. Reported
4211 - Fix a crash when we fetch a descriptor that turns out to be
4212 unexpected (it used to be in our networkstatus when we started
4213 fetching it, but it isn't in our current networkstatus), and we
4214 aren't using bridges. Bugfix on 0.2.0.x.
4215 - Fix a crash when accessing hidden services: it would work the first
4216 time you use a given introduction point for your service, but
4217 on subsequent requests we'd be using garbage memory. Fixed by
4218 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
4219 - Fix a crash when we load a bridge descriptor from disk but we don't
4220 currently have a Bridge line for it in our torrc. Bugfix on
4224 - If bridge authorities set BridgePassword, they will serve a
4225 snapshot of known bridge routerstatuses from their DirPort to
4226 anybody who knows that password. Unset by default.
4229 - Make the unit tests build again.
4230 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
4231 - Make PublishServerDescriptor default to 1, so the default doesn't
4232 have to change as we invent new directory protocol versions.
4233 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
4234 be included unless sys/time.h is already included. Fixes
4235 bug 553. Bugfix on 0.2.0.x.
4236 - If we receive a general-purpose descriptor and then receive an
4237 identical bridge-purpose descriptor soon after, don't discard
4238 the next one as a duplicate.
4241 - If BridgeRelay is set to 1, then the default for
4242 PublishServerDescriptor is now "bridge" rather than "v2,v3".
4243 - If the user sets RelayBandwidthRate but doesn't set
4244 RelayBandwidthBurst, then make them equal rather than erroring out.
4247 Changes in version 0.2.0.13-alpha - 2007-12-21
4248 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
4249 Goodell, fixes many more bugs, and adds a lot of infrastructure for
4252 o New directory authorities:
4253 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
4257 - Only update guard status (usable / not usable) once we have
4258 enough directory information. This was causing us to always pick
4259 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
4260 causing us to discard all our guards on startup if we hadn't been
4261 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
4262 - Purge old entries from the "rephist" database and the hidden
4263 service descriptor databases even when DirPort is zero. Bugfix
4265 - We were ignoring our RelayBandwidthRate for the first 30 seconds
4266 after opening a circuit -- even a relayed circuit. Bugfix on
4268 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
4269 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
4270 crashing or mis-answering these types of requests.
4271 - Relays were publishing their server descriptor to v1 and v2
4272 directory authorities, but they didn't try publishing to v3-only
4273 authorities. Fix this; and also stop publishing to v1 authorities.
4275 - When we were reading router descriptors from cache, we were ignoring
4276 the annotations -- so for example we were reading in bridge-purpose
4277 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
4278 - When we decided to send a 503 response to a request for servers, we
4279 were then also sending the server descriptors: this defeats the
4280 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
4283 - Bridge relays now behave like clients with respect to time
4284 intervals for downloading new consensus documents -- otherwise they
4285 stand out. Bridge users now wait until the end of the interval,
4286 so their bridge relay will be sure to have a new consensus document.
4287 - Three new config options (AlternateDirAuthority,
4288 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
4289 user selectively replace the default directory authorities by type,
4290 rather than the all-or-nothing replacement that DirServer offers.
4291 - Tor can now be configured to read a GeoIP file from disk in one
4292 of two formats. This can be used by controllers to map IP addresses
4293 to countries. Eventually, it may support exit-by-country.
4294 - When possible, bridge relays remember which countries users
4295 are coming from, and report aggregate information in their
4296 extra-info documents, so that the bridge authorities can learn
4297 where Tor is blocked.
4298 - Bridge directory authorities now do reachability testing on the
4299 bridges they know. They provide router status summaries to the
4300 controller via "getinfo ns/purpose/bridge", and also dump summaries
4301 to a file periodically.
4302 - Stop fetching directory info so aggressively if your DirPort is
4303 on but your ORPort is off; stop fetching v2 dir info entirely.
4304 You can override these choices with the new FetchDirInfoEarly
4308 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
4309 consensus documents when there are too many relays at a single
4310 IP address. Now clear it in v2 network status documents too, and
4311 also clear it in routerinfo_t when the relay is no longer listed
4312 in the relevant networkstatus document.
4313 - Don't crash if we get an unexpected value for the
4314 PublishServerDescriptor config option. Reported by Matt Edman;
4315 bugfix on 0.2.0.9-alpha.
4316 - Our new v2 hidden service descriptor format allows descriptors
4317 that have no introduction points. But Tor crashed when we tried
4318 to build a descriptor with no intro points (and it would have
4319 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
4321 - Fix building with dmalloc 5.5.2 with glibc.
4322 - Reject uploaded descriptors and extrainfo documents if they're
4323 huge. Otherwise we'll cache them all over the network and it'll
4324 clog everything up. Reported by Aljosha Judmayer.
4325 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
4326 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
4327 - When the DANGEROUS_VERSION controller status event told us we're
4328 running an obsolete version, it used the string "OLD" to describe
4329 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
4330 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
4331 - If we can't expand our list of entry guards (e.g. because we're
4332 using bridges or we have StrictEntryNodes set), don't mark relays
4333 down when they fail a directory request. Otherwise we're too quick
4334 to mark all our entry points down. Bugfix on 0.1.2.x.
4335 - Fix handling of hex nicknames when answering controller requests for
4336 networkstatus by name, or when deciding whether to warn about unknown
4337 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
4338 - Fix a couple of hard-to-trigger autoconf problems that could result
4339 in really weird results on platforms whose sys/types.h files define
4340 nonstandard integer types. Bugfix on 0.1.2.x.
4341 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
4342 - Don't crash on name lookup when we have no current consensus. Fixes
4343 bug 538; bugfix on 0.2.0.x.
4344 - Only Tors that want to mirror the v2 directory info should
4345 create the "cached-status" directory in their datadir. (All Tors
4346 used to create it.) Bugfix on 0.2.0.9-alpha.
4347 - Directory authorities should only automatically download Extra Info
4348 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
4351 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
4352 consumers. (We already do this on HUP.)
4353 - Authorities and caches fetch the v2 networkstatus documents
4354 less often, now that v3 is encouraged.
4355 - Add a new config option BridgeRelay that specifies you want to
4356 be a bridge relay. Right now the only difference is that it makes
4357 you answer begin_dir requests, and it makes you cache dir info,
4358 even if your DirPort isn't on.
4359 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
4360 ask about source, timestamp of arrival, purpose, etc. We need
4361 something like this to help Vidalia not do GeoIP lookups on bridge
4363 - Allow multiple HashedControlPassword config lines, to support
4364 multiple controller passwords.
4365 - Authorities now decide whether they're authoritative for a given
4366 router based on the router's purpose.
4367 - New config options AuthDirBadDir and AuthDirListBadDirs for
4368 authorities to mark certain relays as "bad directories" in the
4369 networkstatus documents. Also supports the "!baddir" directive in
4370 the approved-routers file.
4373 Changes in version 0.2.0.12-alpha - 2007-11-16
4374 This twelfth development snapshot fixes some more build problems as
4375 well as a few minor bugs.
4378 - Make it build on OpenBSD again. Patch from tup.
4379 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
4380 package-building for Red Hat, OS X, etc.
4382 o Minor bugfixes (on 0.1.2.x):
4383 - Changing the ExitPolicyRejectPrivate setting should cause us to
4384 rebuild our server descriptor.
4386 o Minor bugfixes (on 0.2.0.x):
4387 - When we're lacking a consensus, don't try to perform rendezvous
4388 operations. Reported by Karsten Loesing.
4389 - Fix a small memory leak whenever we decide against using a
4390 newly picked entry guard. Reported by Mike Perry.
4391 - When authorities detected more than two relays running on the same
4392 IP address, they were clearing all the status flags but forgetting
4393 to clear the "hsdir" flag. So clients were being told that a
4394 given relay was the right choice for a v2 hsdir lookup, yet they
4395 never had its descriptor because it was marked as 'not running'
4397 - If we're trying to fetch a bridge descriptor and there's no way
4398 the bridge authority could help us (for example, we don't know
4399 a digest, or there is no bridge authority), don't be so eager to
4400 fall back to asking the bridge authority.
4401 - If we're using bridges or have strictentrynodes set, and our
4402 chosen exit is in the same family as all our bridges/entry guards,
4403 then be flexible about families.
4406 - When we negotiate a v2 link-layer connection (not yet implemented),
4407 accept RELAY_EARLY cells and turn them into RELAY cells if we've
4408 negotiated a v1 connection for their next step. Initial code for
4412 Changes in version 0.2.0.11-alpha - 2007-11-12
4413 This eleventh development snapshot fixes some build problems with
4414 the previous snapshot. It also includes a more secure-by-default exit
4415 policy for relays, fixes an enormous memory leak for exit relays, and
4416 fixes another bug where servers were falling out of the directory list.
4419 - Exit policies now reject connections that are addressed to a
4420 relay's public (external) IP address too, unless
4421 ExitPolicyRejectPrivate is turned off. We do this because too
4422 many relays are running nearby to services that trust them based
4423 on network address. Bugfix on 0.1.2.x.
4426 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
4427 on every successful resolve. Reported by Mike Perry; bugfix
4429 - On authorities, never downgrade to old router descriptors simply
4430 because they're listed in the consensus. This created a catch-22
4431 where we wouldn't list a new descriptor because there was an
4432 old one in the consensus, and we couldn't get the new one in the
4433 consensus because we wouldn't list it. Possible fix for bug 548.
4434 Also, this might cause bug 543 to appear on authorities; if so,
4435 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
4437 o Packaging fixes on 0.2.0.10-alpha:
4438 - We were including instructions about what to do with the
4439 src/config/fallback-consensus file, but we weren't actually
4440 including it in the tarball. Disable all of that for now.
4443 - Allow people to say PreferTunnelledDirConns rather than
4444 PreferTunneledDirConns, for those alternate-spellers out there.
4447 - Don't reevaluate all the information from our consensus document
4448 just because we've downloaded a v2 networkstatus that we intend
4449 to cache. Fixes bug 545; bugfix on 0.2.0.x.
4452 Changes in version 0.2.0.10-alpha - 2007-11-10
4453 This tenth development snapshot adds a third v3 directory authority
4454 run by Mike Perry, adds most of Karsten Loesing's new hidden service
4455 descriptor format, fixes a bad crash bug and new bridge bugs introduced
4456 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
4457 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
4458 addresses many more minor issues.
4460 o New directory authorities:
4461 - Set up ides (run by Mike Perry) as the third v3 directory authority.
4464 - Allow tunnelled directory connections to ask for an encrypted
4465 "begin_dir" connection or an anonymized "uses a full Tor circuit"
4466 connection independently. Now we can make anonymized begin_dir
4467 connections for (e.g.) more secure hidden service posting and
4469 - More progress on proposal 114: code from Karsten Loesing to
4470 implement new hidden service descriptor format.
4471 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
4472 accommodate the growing number of servers that use the default
4473 and are reaching it.
4474 - Directory authorities use a new formula for selecting which nodes
4475 to advertise as Guards: they must be in the top 7/8 in terms of
4476 how long we have known about them, and above the median of those
4477 nodes in terms of weighted fractional uptime.
4478 - Make "not enough dir info yet" warnings describe *why* Tor feels
4479 it doesn't have enough directory info yet.
4482 - Stop servers from crashing if they set a Family option (or
4483 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
4485 - Make bridge users work again -- the move to v3 directories in
4486 0.2.0.9-alpha had introduced a number of bugs that made bridges
4487 no longer work for clients.
4488 - When the clock jumps forward a lot, do not allow the bandwidth
4489 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
4491 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
4492 - When the consensus lists a router descriptor that we previously were
4493 mirroring, but that we considered non-canonical, reload the
4494 descriptor as canonical. This fixes bug 543 where Tor servers
4495 would start complaining after a few days that they don't have
4496 enough directory information to build a circuit.
4497 - Consider replacing the current consensus when certificates arrive
4498 that make the pending consensus valid. Previously, we were only
4499 considering replacement when the new certs _didn't_ help.
4500 - Fix an assert error on startup if we didn't already have the
4501 consensus and certs cached in our datadirectory: we were caching
4502 the consensus in consensus_waiting_for_certs but then free'ing it
4504 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
4505 Request) if we need more v3 certs but we've already got pending
4506 requests for all of them.
4507 - Correctly back off from failing certificate downloads. Fixes
4509 - Authorities don't vote on the Running flag if they have been running
4510 for less than 30 minutes themselves. Fixes bug 547, where a newly
4511 started authority would vote that everyone was down.
4514 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
4515 it, it had no AES, and it hasn't seen any security patches since
4519 - Clients now hold circuitless TLS connections open for 1.5 times
4520 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
4521 rebuild a new circuit over them within that timeframe. Previously,
4522 they held them open only for KeepalivePeriod (5 minutes).
4523 - Use "If-Modified-Since" to avoid retrieving consensus
4524 networkstatuses that we already have.
4525 - When we have no consensus, check FallbackNetworkstatusFile (defaults
4526 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
4527 we start knowing some directory caches.
4528 - When we receive a consensus from the future, warn about skew.
4529 - Improve skew reporting: try to give the user a better log message
4530 about how skewed they are, and how much this matters.
4531 - When we have a certificate for an authority, believe that
4532 certificate's claims about the authority's IP address.
4533 - New --quiet command-line option to suppress the default console log.
4534 Good in combination with --hash-password.
4535 - Authorities send back an X-Descriptor-Not-New header in response to
4536 an accepted-but-discarded descriptor upload. Partially implements
4538 - Make the log message for "tls error. breaking." more useful.
4539 - Better log messages about certificate downloads, to attempt to
4540 track down the second incarnation of bug 546.
4542 o Minor features (bridges):
4543 - If bridge users set UpdateBridgesFromAuthority, but the digest
4544 they ask for is a 404 from the bridge authority, they now fall
4545 back to trying the bridge directly.
4546 - Bridges now use begin_dir to publish their server descriptor to
4547 the bridge authority, even when they haven't set TunnelDirConns.
4549 o Minor features (controller):
4550 - When reporting clock skew, and we know that the clock is _at least
4551 as skewed_ as some value, but we don't know the actual value,
4552 report the value as a "minimum skew."
4555 - Update linux-tor-prio.sh script to allow QoS based on the uid of
4556 the Tor process. Patch from Marco Bonetti with tweaks from Mike
4560 - Refuse to start if both ORPort and UseBridges are set. Bugfix
4561 on 0.2.0.x, suggested by Matt Edman.
4562 - Don't stop fetching descriptors when FetchUselessDescriptors is
4563 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
4564 reported by tup and ioerror.
4565 - Better log message on vote from unknown authority.
4566 - Don't log "Launching 0 request for 0 router" message.
4568 o Minor bugfixes (memory leaks):
4569 - Stop leaking memory every time we parse a v3 certificate. Bugfix
4571 - Stop leaking memory every time we load a v3 certificate. Bugfix
4572 on 0.2.0.1-alpha. Fixes bug 536.
4573 - Stop leaking a cached networkstatus on exit. Bugfix on
4575 - Stop leaking voter information every time we free a consensus.
4576 Bugfix on 0.2.0.3-alpha.
4577 - Stop leaking signed data every time we check a voter signature.
4578 Bugfix on 0.2.0.3-alpha.
4579 - Stop leaking a signature every time we fail to parse a consensus or
4580 a vote. Bugfix on 0.2.0.3-alpha.
4581 - Stop leaking v2_download_status_map on shutdown. Bugfix on
4583 - Stop leaking conn->nickname every time we make a connection to a
4584 Tor relay without knowing its expected identity digest (e.g. when
4585 using bridges). Bugfix on 0.2.0.3-alpha.
4587 - Minor bugfixes (portability):
4588 - Run correctly on platforms where rlim_t is larger than unsigned
4589 long, and/or where the real limit for number of open files is
4590 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
4591 particular, these may be needed for OS X 10.5.
4594 Changes in version 0.1.2.18 - 2007-10-28
4595 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
4596 hidden service introduction that were causing huge delays, and a big
4597 bug that was causing some servers to disappear from the network status
4598 lists for a few hours each day.
4600 o Major bugfixes (crashes):
4601 - If a connection is shut down abruptly because of something that
4602 happened inside connection_flushed_some(), do not call
4603 connection_finished_flushing(). Should fix bug 451:
4604 "connection_stop_writing: Assertion conn->write_event failed"
4605 Bugfix on 0.1.2.7-alpha.
4606 - Fix possible segfaults in functions called from
4607 rend_process_relay_cell().
4609 o Major bugfixes (hidden services):
4610 - Hidden services were choosing introduction points uniquely by
4611 hexdigest, but when constructing the hidden service descriptor
4612 they merely wrote the (potentially ambiguous) nickname.
4613 - Clients now use the v2 intro format for hidden service
4614 connections: they specify their chosen rendezvous point by identity
4615 digest rather than by (potentially ambiguous) nickname. These
4616 changes could speed up hidden service connections dramatically.
4618 o Major bugfixes (other):
4619 - Stop publishing a new server descriptor just because we get a
4620 HUP signal. This led (in a roundabout way) to some servers getting
4621 dropped from the networkstatus lists for a few hours each day.
4622 - When looking for a circuit to cannibalize, consider family as well
4623 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
4624 circuit cannibalization).
4625 - When a router wasn't listed in a new networkstatus, we were leaving
4626 the flags for that router alone -- meaning it remained Named,
4627 Running, etc -- even though absence from the networkstatus means
4628 that it shouldn't be considered to exist at all anymore. Now we
4629 clear all the flags for routers that fall out of the networkstatus
4630 consensus. Fixes bug 529.
4633 - Don't try to access (or alter) the state file when running
4634 --list-fingerprint or --verify-config or --hash-password. Resolves
4636 - When generating information telling us how to extend to a given
4637 router, do not try to include the nickname if it is
4638 absent. Resolves bug 467.
4639 - Fix a user-triggerable segfault in expand_filename(). (There isn't
4640 a way to trigger this remotely.)
4641 - When sending a status event to the controller telling it that an
4642 OR address is reachable, set the port correctly. (Previously we
4643 were reporting the dir port.)
4644 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
4645 command. Bugfix on 0.1.2.17.
4646 - When loading bandwidth history, do not believe any information in
4647 the future. Fixes bug 434.
4648 - When loading entry guard information, do not believe any information
4650 - When we have our clock set far in the future and generate an
4651 onion key, then re-set our clock to be correct, we should not stop
4652 the onion key from getting rotated.
4653 - On some platforms, accept() can return a broken address. Detect
4654 this more quietly, and deal accordingly. Fixes bug 483.
4655 - It's not actually an error to find a non-pending entry in the DNS
4656 cache when canceling a pending resolve. Don't log unless stuff
4657 is fishy. Resolves bug 463.
4658 - Don't reset trusted dir server list when we set a configuration
4659 option. Patch from Robert Hogan.
4660 - Don't try to create the datadir when running --verify-config or
4661 --hash-password. Resolves bug 540.
4664 Changes in version 0.2.0.9-alpha - 2007-10-24
4665 This ninth development snapshot switches clients to the new v3 directory
4666 system; allows servers to be listed in the network status even when they
4667 have the same nickname as a registered server; and fixes many other
4668 bugs including a big one that was causing some servers to disappear
4669 from the network status lists for a few hours each day.
4671 o Major features (directory system):
4672 - Clients now download v3 consensus networkstatus documents instead
4673 of v2 networkstatus documents. Clients and caches now base their
4674 opinions about routers on these consensus documents. Clients only
4675 download router descriptors listed in the consensus.
4676 - Authorities now list servers who have the same nickname as
4677 a different named server, but list them with a new flag,
4678 "Unnamed". Now we can list servers that happen to pick the same
4679 nickname as a server that registered two years ago and then
4680 disappeared. Partially implements proposal 122.
4681 - If the consensus lists a router as "Unnamed", the name is assigned
4682 to a different router: do not identify the router by that name.
4683 Partially implements proposal 122.
4684 - Authorities can now come to a consensus on which method to use to
4685 compute the consensus. This gives us forward compatibility.
4688 - Stop publishing a new server descriptor just because we HUP or
4689 when we find our DirPort to be reachable but won't actually publish
4690 it. New descriptors without any real changes are dropped by the
4691 authorities, and can screw up our "publish every 18 hours" schedule.
4693 - When a router wasn't listed in a new networkstatus, we were leaving
4694 the flags for that router alone -- meaning it remained Named,
4695 Running, etc -- even though absence from the networkstatus means
4696 that it shouldn't be considered to exist at all anymore. Now we
4697 clear all the flags for routers that fall out of the networkstatus
4698 consensus. Fixes bug 529; bugfix on 0.1.2.x.
4699 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
4700 extrainfo documents and then discard them immediately for not
4701 matching the latest router. Bugfix on 0.2.0.1-alpha.
4703 o Minor features (v3 directory protocol):
4704 - Allow tor-gencert to generate a new certificate without replacing
4706 - Allow certificates to include an address.
4707 - When we change our directory-cache settings, reschedule all voting
4708 and download operations.
4709 - Reattempt certificate downloads immediately on failure, as long as
4710 we haven't failed a threshold number of times yet.
4711 - Delay retrying consensus downloads while we're downloading
4712 certificates to verify the one we just got. Also, count getting a
4713 consensus that we already have (or one that isn't valid) as a failure,
4714 and count failing to get the certificates after 20 minutes as a
4716 - Build circuits and download descriptors even if our consensus is a
4717 little expired. (This feature will go away once authorities are
4720 o Minor features (router descriptor cache):
4721 - If we find a cached-routers file that's been sitting around for more
4722 than 28 days unmodified, then most likely it's a leftover from
4723 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
4725 - When we (as a cache) download a descriptor because it was listed
4726 in a consensus, remember when the consensus was supposed to expire,
4727 and don't expire the descriptor until then.
4729 o Minor features (performance):
4730 - Call routerlist_remove_old_routers() much less often. This should
4731 speed startup, especially on directory caches.
4732 - Don't try to launch new descriptor downloads quite so often when we
4733 already have enough directory information to build circuits.
4734 - Base64 decoding was actually showing up on our profile when parsing
4735 the initial descriptor file; switch to an in-process all-at-once
4736 implementation that's about 3.5x times faster than calling out to
4739 o Minor features (compilation):
4740 - Detect non-ASCII platforms (if any still exist) and refuse to
4741 build there: some of our code assumes that 'A' is 65 and so on.
4743 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
4744 - Make the "next period" votes into "current period" votes immediately
4745 after publishing the consensus; avoid a heisenbug that made them
4746 stick around indefinitely.
4747 - When we discard a vote as a duplicate, do not report this as
4749 - Treat missing v3 keys or certificates as an error when running as a
4750 v3 directory authority.
4751 - When we're configured to be a v3 authority, but we're only listed
4752 as a non-v3 authority in our DirServer line for ourself, correct
4754 - If an authority doesn't have a qualified hostname, just put
4755 its address in the vote. This fixes the problem where we referred to
4756 "moria on moria:9031."
4757 - Distinguish between detached signatures for the wrong period, and
4758 detached signatures for a divergent vote.
4759 - Fix a small memory leak when computing a consensus.
4760 - When there's no concensus, we were forming a vote every 30
4761 minutes, but writing the "valid-after" line in our vote based
4762 on our configured V3AuthVotingInterval: so unless the intervals
4763 matched up, we immediately rejected our own vote because it didn't
4764 start at the voting interval that caused us to construct a vote.
4766 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
4767 - Delete unverified-consensus when the real consensus is set.
4768 - Consider retrying a consensus networkstatus fetch immediately
4769 after one fails: don't wait 60 seconds to notice.
4770 - When fetching a consensus as a cache, wait until a newer consensus
4771 should exist before trying to replace the current one.
4772 - Use a more forgiving schedule for retrying failed consensus
4773 downloads than for other types.
4775 o Minor bugfixes (other directory issues):
4776 - Correct the implementation of "download votes by digest." Bugfix on
4778 - Authorities no longer send back "400 you're unreachable please fix
4779 it" errors to Tor servers that aren't online all the time. We're
4780 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
4782 o Minor bugfixes (controller):
4783 - Don't reset trusted dir server list when we set a configuration
4784 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
4785 - Respond to INT and TERM SIGNAL commands before we execute the
4786 signal, in case the signal shuts us down. We had a patch in
4787 0.1.2.1-alpha that tried to do this by queueing the response on
4788 the connection's buffer before shutting down, but that really
4789 isn't the same thing at all. Bug located by Matt Edman.
4791 o Minor bugfixes (misc):
4792 - Correctly check for bad options to the "PublishServerDescriptor"
4793 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
4794 - Stop leaking memory on failing case of base32_decode, and make
4795 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
4796 - Don't try to download extrainfo documents when we're trying to
4797 fetch enough directory info to build a circuit: having enough
4798 info should get priority. Bugfix on 0.2.0.x.
4799 - Don't complain that "your server has not managed to confirm that its
4800 ports are reachable" if we haven't been able to build any circuits
4801 yet. Bug found by spending four hours without a v3 consensus. Bugfix
4803 - Detect the reason for failing to mmap a descriptor file we just
4804 wrote, and give a more useful log message. Fixes bug 533. Bugfix
4807 o Code simplifications and refactoring:
4808 - Remove support for the old bw_accounting file: we've been storing
4809 bandwidth accounting information in the state file since
4810 0.1.2.5-alpha. This may result in bandwidth accounting errors
4811 if you try to upgrade from 0.1.1.x or earlier, or if you try to
4812 downgrade to 0.1.1.x or earlier.
4813 - New convenience code to locate a file within the DataDirectory.
4814 - Move non-authority functionality out of dirvote.c.
4815 - Refactor the arguments for router_pick_{directory_|trusteddir}server
4816 so that they all take the same named flags.
4819 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
4820 Unix users an easy way to script their Tor process (e.g. by
4821 adjusting bandwidth based on the time of the day).
4824 Changes in version 0.2.0.8-alpha - 2007-10-12
4825 This eighth development snapshot fixes a crash bug that's been bothering
4826 us since February 2007, lets bridge authorities store a list of bridge
4827 descriptors they've seen, gets v3 directory voting closer to working,
4828 starts caching v3 directory consensus documents on directory mirrors,
4829 and fixes a variety of smaller issues including some minor memory leaks.
4831 o Major features (router descriptor cache):
4832 - Store routers in a file called cached-descriptors instead of in
4833 cached-routers. Initialize cached-descriptors from cached-routers
4834 if the old format is around. The new format allows us to store
4835 annotations along with descriptors.
4836 - Use annotations to record the time we received each descriptor, its
4837 source, and its purpose.
4838 - Disable the SETROUTERPURPOSE controller command: it is now
4840 - Controllers should now specify cache=no or cache=yes when using
4841 the +POSTDESCRIPTOR command.
4842 - Bridge authorities now write bridge descriptors to disk, meaning
4843 we can export them to other programs and begin distributing them
4846 o Major features (directory authorities):
4847 - When a v3 authority is missing votes or signatures, it now tries
4849 - Directory authorities track weighted fractional uptime as well as
4850 weighted mean-time-between failures. WFU is suitable for deciding
4851 whether a node is "usually up", while MTBF is suitable for deciding
4852 whether a node is "likely to stay up." We need both, because
4853 "usually up" is a good requirement for guards, while "likely to
4854 stay up" is a good requirement for long-lived connections.
4856 o Major features (v3 directory system):
4857 - Caches now download v3 network status documents as needed,
4858 and download the descriptors listed in them.
4859 - All hosts now attempt to download and keep fresh v3 authority
4860 certificates, and re-attempt after failures.
4861 - More internal-consistency checks for vote parsing.
4863 o Major bugfixes (crashes):
4864 - If a connection is shut down abruptly because of something that
4865 happened inside connection_flushed_some(), do not call
4866 connection_finished_flushing(). Should fix bug 451. Bugfix on
4869 o Major bugfixes (performance):
4870 - Fix really bad O(n^2) performance when parsing a long list of
4871 routers: Instead of searching the entire list for an "extra-info "
4872 string which usually wasn't there, once for every routerinfo
4873 we read, just scan lines forward until we find one we like.
4875 - When we add data to a write buffer in response to the data on that
4876 write buffer getting low because of a flush, do not consider the
4877 newly added data as a candidate for immediate flushing, but rather
4878 make it wait until the next round of writing. Otherwise, we flush
4879 and refill recursively, and a single greedy TLS connection can
4880 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
4882 o Minor features (v3 authority system):
4883 - Add more ways for tools to download the votes that lead to the
4885 - Send a 503 when low on bandwidth and a vote, consensus, or
4886 certificate is requested.
4887 - If-modified-since is now implemented properly for all kinds of
4888 certificate requests.
4890 o Minor bugfixes (network statuses):
4891 - Tweak the implementation of proposal 109 slightly: allow at most
4892 two Tor servers on the same IP address, except if it's the location
4893 of a directory authority, in which case allow five. Bugfix on
4896 o Minor bugfixes (controller):
4897 - When sending a status event to the controller telling it that an
4898 OR address is reachable, set the port correctly. (Previously we
4899 were reporting the dir port.) Bugfix on 0.1.2.x.
4901 o Minor bugfixes (v3 directory system):
4902 - Fix logic to look up a cert by its signing key digest. Bugfix on
4904 - Only change the reply to a vote to "OK" if it's not already
4905 set. This gets rid of annoying "400 OK" log messages, which may
4906 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
4907 - When we get a valid consensus, recompute the voting schedule.
4908 - Base the valid-after time of a vote on the consensus voting
4909 schedule, not on our preferred schedule.
4910 - Make the return values and messages from signature uploads and
4911 downloads more sensible.
4912 - Fix a memory leak when serving votes and consensus documents, and
4913 another when serving certificates.
4915 o Minor bugfixes (performance):
4916 - Use a slightly simpler string hashing algorithm (copying Python's
4917 instead of Java's) and optimize our digest hashing algorithm to take
4918 advantage of 64-bit platforms and to remove some possibly-costly
4920 - Fix a minor memory leak whenever we parse guards from our state
4921 file. Bugfix on 0.2.0.7-alpha.
4922 - Fix a minor memory leak whenever we write out a file. Bugfix on
4924 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
4925 command. Bugfix on 0.2.0.5-alpha.
4927 o Minor bugfixes (portability):
4928 - On some platforms, accept() can return a broken address. Detect
4929 this more quietly, and deal accordingly. Fixes bug 483.
4930 - Stop calling tor_strlower() on uninitialized memory in some cases.
4931 Bugfix in 0.2.0.7-alpha.
4933 o Minor bugfixes (usability):
4934 - Treat some 403 responses from directory servers as INFO rather than
4935 WARN-severity events.
4936 - It's not actually an error to find a non-pending entry in the DNS
4937 cache when canceling a pending resolve. Don't log unless stuff is
4938 fishy. Resolves bug 463.
4940 o Minor bugfixes (anonymity):
4941 - Never report that we've used more bandwidth than we're willing to
4942 relay: it leaks how much non-relay traffic we're using. Resolves
4944 - When looking for a circuit to cannibalize, consider family as well
4945 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
4946 circuit cannibalization).
4948 o Code simplifications and refactoring:
4949 - Make a bunch of functions static. Remove some dead code.
4950 - Pull out about a third of the really big routerlist.c; put it in a
4951 new module, networkstatus.c.
4952 - Merge the extra fields in local_routerstatus_t back into
4953 routerstatus_t: we used to need one routerstatus_t for each
4954 authority's opinion, plus a local_routerstatus_t for the locally
4955 computed consensus opinion. To save space, we put the locally
4956 modified fields into local_routerstatus_t, and only the common
4957 stuff into routerstatus_t. But once v3 directories are in use,
4958 clients and caches will no longer need to hold authority opinions;
4959 thus, the rationale for keeping the types separate is now gone.
4960 - Make the code used to reschedule and reattempt downloads more
4962 - Turn all 'Are we a directory server/mirror?' logic into a call to
4964 - Remove the code to generate the oldest (v1) directory format.
4965 The code has been disabled since 0.2.0.5-alpha.
4968 Changes in version 0.2.0.7-alpha - 2007-09-21
4969 This seventh development snapshot makes bridges work again, makes bridge
4970 authorities work for the first time, fixes two huge performance flaws
4971 in hidden services, and fixes a variety of minor issues.
4973 o New directory authorities:
4974 - Set up moria1 and tor26 as the first v3 directory authorities. See
4975 doc/spec/dir-spec.txt for details on the new directory design.
4977 o Major bugfixes (crashes):
4978 - Fix possible segfaults in functions called from
4979 rend_process_relay_cell(). Bugfix on 0.1.2.x.
4981 o Major bugfixes (bridges):
4982 - Fix a bug that made servers send a "404 Not found" in response to
4983 attempts to fetch their server descriptor. This caused Tor servers
4984 to take many minutes to establish reachability for their DirPort,
4985 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
4986 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
4987 users configure that and specify a bridge with an identity
4988 fingerprint, now they will lookup the bridge descriptor at the
4989 default bridge authority via a one-hop tunnel, but once circuits
4990 are established they will switch to a three-hop tunnel for later
4991 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
4993 o Major bugfixes (hidden services):
4994 - Hidden services were choosing introduction points uniquely by
4995 hexdigest, but when constructing the hidden service descriptor
4996 they merely wrote the (potentially ambiguous) nickname.
4997 - Clients now use the v2 intro format for hidden service
4998 connections: they specify their chosen rendezvous point by identity
4999 digest rather than by (potentially ambiguous) nickname. Both
5000 are bugfixes on 0.1.2.x, and they could speed up hidden service
5001 connections dramatically. Thanks to Karsten Loesing.
5003 o Minor features (security):
5004 - As a client, do not believe any server that tells us that an
5005 address maps to an internal address space.
5006 - Make it possible to enable HashedControlPassword and
5007 CookieAuthentication at the same time.
5009 o Minor features (guard nodes):
5010 - Tag every guard node in our state file with the version that
5011 we believe added it, or with our own version if we add it. This way,
5012 if a user temporarily runs an old version of Tor and then switches
5013 back to a new one, she doesn't automatically lose her guards.
5015 o Minor features (speed):
5016 - When implementing AES counter mode, update only the portions of the
5017 counter buffer that need to change, and don't keep separate
5018 network-order and host-order counters when they are the same (i.e.,
5019 on big-endian hosts.)
5021 o Minor features (controller):
5022 - Accept LF instead of CRLF on controller, since some software has a
5023 hard time generating real Internet newlines.
5024 - Add GETINFO values for the server status events
5025 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
5029 - Routers no longer include bandwidth-history lines in their
5030 descriptors; this information is already available in extra-info
5031 documents, and including it in router descriptors took up 60%
5032 (!) of compressed router descriptor downloads. Completes
5033 implementation of proposal 104.
5034 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
5035 and TorControl.py, as they use the old v0 controller protocol,
5036 and are obsoleted by TorFlow anyway.
5037 - Drop support for v1 rendezvous descriptors, since we never used
5038 them anyway, and the code has probably rotted by now. Based on
5039 patch from Karsten Loesing.
5040 - On OSX, stop warning the user that kqueue support in libevent is
5041 "experimental", since it seems to have worked fine for ages.
5044 - When generating information telling us how to extend to a given
5045 router, do not try to include the nickname if it is absent. Fixes
5046 bug 467. Bugfix on 0.2.0.3-alpha.
5047 - Fix a user-triggerable (but not remotely-triggerable) segfault
5048 in expand_filename(). Bugfix on 0.1.2.x.
5049 - Fix a memory leak when freeing incomplete requests from DNSPort.
5050 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
5051 - Don't try to access (or alter) the state file when running
5052 --list-fingerprint or --verify-config or --hash-password. (Resolves
5053 bug 499.) Bugfix on 0.1.2.x.
5054 - Servers used to decline to publish their DirPort if their
5055 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
5056 were below a threshold. Now they only look at BandwidthRate and
5057 RelayBandwidthRate. Bugfix on 0.1.2.x.
5058 - Remove an optimization in the AES counter-mode code that assumed
5059 that the counter never exceeded 2^68. When the counter can be set
5060 arbitrarily as an IV (as it is by Karsten's new hidden services
5061 code), this assumption no longer holds. Bugfix on 0.1.2.x.
5062 - Resume listing "AUTHORITY" flag for authorities in network status.
5063 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
5065 o Code simplifications and refactoring:
5066 - Revamp file-writing logic so we don't need to have the entire
5067 contents of a file in memory at once before we write to disk. Tor,
5069 - Turn "descriptor store" into a full-fledged type.
5070 - Move all NT services code into a separate source file.
5071 - Unify all code that computes medians, percentile elements, etc.
5072 - Get rid of a needless malloc when parsing address policies.
5075 Changes in version 0.1.2.17 - 2007-08-30
5076 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
5077 X bundles. Vidalia 0.0.14 makes authentication required for the
5078 ControlPort in the default configuration, which addresses important
5079 security risks. Everybody who uses Vidalia (or another controller)
5082 In addition, this Tor update fixes major load balancing problems with
5083 path selection, which should speed things up a lot once many people
5086 o Major bugfixes (security):
5087 - We removed support for the old (v0) control protocol. It has been
5088 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
5089 become more of a headache than it's worth.
5091 o Major bugfixes (load balancing):
5092 - When choosing nodes for non-guard positions, weight guards
5093 proportionally less, since they already have enough load. Patch
5095 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
5096 will allow fast Tor servers to get more attention.
5097 - When we're upgrading from an old Tor version, forget our current
5098 guards and pick new ones according to the new weightings. These
5099 three load balancing patches could raise effective network capacity
5100 by a factor of four. Thanks to Mike Perry for measurements.
5102 o Major bugfixes (stream expiration):
5103 - Expire not-yet-successful application streams in all cases if
5104 they've been around longer than SocksTimeout. Right now there are
5105 some cases where the stream will live forever, demanding a new
5106 circuit every 15 seconds. Fixes bug 454; reported by lodger.
5108 o Minor features (controller):
5109 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
5110 is valid before any authentication has been received. It tells
5111 a controller what kind of authentication is expected, and what
5112 protocol is spoken. Implements proposal 119.
5114 o Minor bugfixes (performance):
5115 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
5116 greatly speeding up loading cached-routers from disk on startup.
5117 - Disable sentinel-based debugging for buffer code: we squashed all
5118 the bugs that this was supposed to detect a long time ago, and now
5119 its only effect is to change our buffer sizes from nice powers of
5120 two (which platform mallocs tend to like) to values slightly over
5121 powers of two (which make some platform mallocs sad).
5123 o Minor bugfixes (misc):
5124 - If exit bandwidth ever exceeds one third of total bandwidth, then
5125 use the correct formula to weight exit nodes when choosing paths.
5126 Based on patch from Mike Perry.
5127 - Choose perfectly fairly among routers when choosing by bandwidth and
5128 weighting by fraction of bandwidth provided by exits. Previously, we
5129 would choose with only approximate fairness, and correct ourselves
5130 if we ran off the end of the list.
5131 - If we require CookieAuthentication but we fail to write the
5132 cookie file, we would warn but not exit, and end up in a state
5133 where no controller could authenticate. Now we exit.
5134 - If we require CookieAuthentication, stop generating a new cookie
5135 every time we change any piece of our config.
5136 - Refuse to start with certain directory authority keys, and
5137 encourage people using them to stop.
5138 - Terminate multi-line control events properly. Original patch
5140 - Fix a minor memory leak when we fail to find enough suitable
5141 servers to choose a circuit.
5142 - Stop leaking part of the descriptor when we run into a particularly
5143 unparseable piece of it.
5146 Changes in version 0.2.0.6-alpha - 2007-08-26
5147 This sixth development snapshot features a new Vidalia version in the
5148 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
5149 the ControlPort in the default configuration, which addresses important
5152 In addition, this snapshot fixes major load balancing problems
5153 with path selection, which should speed things up a lot once many
5154 people have upgraded. The directory authorities also use a new
5155 mean-time-between-failure approach to tracking which servers are stable,
5156 rather than just looking at the most recent uptime.
5158 o New directory authorities:
5159 - Set up Tonga as the default bridge directory authority.
5162 - Directory authorities now track servers by weighted
5163 mean-times-between-failures. When we have 4 or more days of data,
5164 use measured MTBF rather than declared uptime to decide whether
5165 to call a router Stable. Implements proposal 108.
5167 o Major bugfixes (load balancing):
5168 - When choosing nodes for non-guard positions, weight guards
5169 proportionally less, since they already have enough load. Patch
5171 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
5172 will allow fast Tor servers to get more attention.
5173 - When we're upgrading from an old Tor version, forget our current
5174 guards and pick new ones according to the new weightings. These
5175 three load balancing patches could raise effective network capacity
5176 by a factor of four. Thanks to Mike Perry for measurements.
5178 o Major bugfixes (descriptor parsing):
5179 - Handle unexpected whitespace better in malformed descriptors. Bug
5180 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
5183 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
5184 GETINFO for Torstat to use until it can switch to using extrainfos.
5185 - Optionally (if built with -DEXPORTMALLINFO) export the output
5186 of mallinfo via http, as tor/mallinfo.txt. Only accessible
5190 - Do not intermix bridge routers with controller-added
5191 routers. (Bugfix on 0.2.0.x)
5192 - Do not fail with an assert when accept() returns an unexpected
5193 address family. Addresses but does not wholly fix bug 483. (Bugfix
5195 - Let directory authorities startup even when they can't generate
5196 a descriptor immediately, e.g. because they don't know their
5198 - Stop putting the authentication cookie in a file called "0"
5199 in your working directory if you don't specify anything for the
5200 new CookieAuthFile option. Reported by Matt Edman.
5201 - Make it possible to read the PROTOCOLINFO response in a way that
5202 conforms to our control-spec. Reported by Matt Edman.
5203 - Fix a minor memory leak when we fail to find enough suitable
5204 servers to choose a circuit. Bugfix on 0.1.2.x.
5205 - Stop leaking part of the descriptor when we run into a particularly
5206 unparseable piece of it. Bugfix on 0.1.2.x.
5207 - Unmap the extrainfo cache file on exit.
5210 Changes in version 0.2.0.5-alpha - 2007-08-19
5211 This fifth development snapshot fixes compilation on Windows again;
5212 fixes an obnoxious client-side bug that slowed things down and put
5213 extra load on the network; gets us closer to using the v3 directory
5214 voting scheme; makes it easier for Tor controllers to use cookie-based
5215 authentication; and fixes a variety of other bugs.
5218 - Version 1 directories are no longer generated in full. Instead,
5219 authorities generate and serve "stub" v1 directories that list
5220 no servers. This will stop Tor versions 0.1.0.x and earlier from
5221 working, but (for security reasons) nobody should be running those
5224 o Major bugfixes (compilation, 0.2.0.x):
5225 - Try to fix Win32 compilation again: improve checking for IPv6 types.
5226 - Try to fix MSVC compilation: build correctly on platforms that do
5227 not define s6_addr16 or s6_addr32.
5228 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
5231 o Major bugfixes (stream expiration):
5232 - Expire not-yet-successful application streams in all cases if
5233 they've been around longer than SocksTimeout. Right now there are
5234 some cases where the stream will live forever, demanding a new
5235 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
5238 o Minor features (directory servers):
5239 - When somebody requests a list of statuses or servers, and we have
5240 none of those, return a 404 rather than an empty 200.
5242 o Minor features (directory voting):
5243 - Store v3 consensus status consensuses on disk, and reload them
5246 o Minor features (security):
5247 - Warn about unsafe ControlPort configurations.
5248 - Refuse to start with certain directory authority keys, and
5249 encourage people using them to stop.
5251 o Minor features (controller):
5252 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
5253 is valid before any authentication has been received. It tells
5254 a controller what kind of authentication is expected, and what
5255 protocol is spoken. Implements proposal 119.
5256 - New config option CookieAuthFile to choose a new location for the
5257 cookie authentication file, and config option
5258 CookieAuthFileGroupReadable to make it group-readable.
5260 o Minor features (unit testing):
5261 - Add command-line arguments to unit-test executable so that we can
5262 invoke any chosen test from the command line rather than having
5263 to run the whole test suite at once; and so that we can turn on
5264 logging for the unit tests.
5266 o Minor bugfixes (on 0.1.2.x):
5267 - If we require CookieAuthentication but we fail to write the
5268 cookie file, we would warn but not exit, and end up in a state
5269 where no controller could authenticate. Now we exit.
5270 - If we require CookieAuthentication, stop generating a new cookie
5271 every time we change any piece of our config.
5272 - When loading bandwidth history, do not believe any information in
5273 the future. Fixes bug 434.
5274 - When loading entry guard information, do not believe any information
5276 - When we have our clock set far in the future and generate an
5277 onion key, then re-set our clock to be correct, we should not stop
5278 the onion key from getting rotated.
5279 - Clean up torrc sample config file.
5280 - Do not automatically run configure from autogen.sh. This
5281 non-standard behavior tended to annoy people who have built other
5284 o Minor bugfixes (on 0.2.0.x):
5285 - Fix a bug with AutomapHostsOnResolve that would always cause
5286 the second request to fail. Bug reported by Kate. Bugfix on
5288 - Fix a bug in ADDRMAP controller replies that would sometimes
5289 try to print a NULL. Patch from tup.
5290 - Read v3 directory authority keys from the right location.
5291 - Numerous bugfixes to directory voting code.
5294 Changes in version 0.1.2.16 - 2007-08-01
5295 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
5296 remote attacker in certain situations to rewrite the user's torrc
5297 configuration file. This can completely compromise anonymity of users
5298 in most configurations, including those running the Vidalia bundles,
5299 TorK, etc. Or worse.
5301 o Major security fixes:
5302 - Close immediately after missing authentication on control port;
5303 do not allow multiple authentication attempts.
5306 Changes in version 0.2.0.4-alpha - 2007-08-01
5307 This fourth development snapshot fixes a critical security vulnerability
5308 for most users, specifically those running Vidalia, TorK, etc. Everybody
5309 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
5311 o Major security fixes:
5312 - Close immediately after missing authentication on control port;
5313 do not allow multiple authentication attempts.
5315 o Major bugfixes (compilation):
5316 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
5319 o Minor features (performance):
5320 - Be even more aggressive about releasing RAM from small
5321 empty buffers. Thanks to our free-list code, this shouldn't be too
5322 performance-intensive.
5323 - Disable sentinel-based debugging for buffer code: we squashed all
5324 the bugs that this was supposed to detect a long time ago, and
5325 now its only effect is to change our buffer sizes from nice
5326 powers of two (which platform mallocs tend to like) to values
5327 slightly over powers of two (which make some platform mallocs sad).
5328 - Log malloc statistics from mallinfo() on platforms where it
5332 Changes in version 0.2.0.3-alpha - 2007-07-29
5333 This third development snapshot introduces new experimental
5334 blocking-resistance features and a preliminary version of the v3
5335 directory voting design, and includes many other smaller features
5339 - The first pieces of our "bridge" design for blocking-resistance
5340 are implemented. People can run bridge directory authorities;
5341 people can run bridges; and people can configure their Tor clients
5342 with a set of bridges to use as the first hop into the Tor network.
5343 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
5345 - Create listener connections before we setuid to the configured
5346 User and Group. Now non-Windows users can choose port values
5347 under 1024, start Tor as root, and have Tor bind those ports
5348 before it changes to another UID. (Windows users could already
5350 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
5351 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
5352 on "vserver" accounts. (Patch from coderman.)
5353 - Be even more aggressive about separating local traffic from relayed
5354 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
5356 o Major features (experimental):
5357 - First cut of code for "v3 dir voting": directory authorities will
5358 vote on a common network status document rather than each publishing
5359 their own opinion. This code needs more testing and more corner-case
5360 handling before it's ready for use.
5363 - Directory authorities now call routers Fast if their bandwidth is
5364 at least 100KB/s, and consider their bandwidth adequate to be a
5365 Guard if it is at least 250KB/s, no matter the medians. This fix
5366 complements proposal 107. [Bugfix on 0.1.2.x]
5367 - Directory authorities now never mark more than 3 servers per IP as
5368 Valid and Running. (Implements proposal 109, by Kevin Bauer and
5370 - Minor change to organizationName and commonName generation
5371 procedures in TLS certificates during Tor handshakes, to invalidate
5372 some earlier censorware approaches. This is not a long-term
5373 solution, but applying it will give us a bit of time to look into
5374 the epidemiology of countermeasures as they spread.
5376 o Major bugfixes (directory):
5377 - Rewrite directory tokenization code to never run off the end of
5378 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
5380 o Minor features (controller):
5381 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
5382 match requests to applications. (Patch from Robert Hogan.)
5383 - Report address and port correctly on connections to DNSPort. (Patch
5385 - Add a RESOLVE command to launch hostname lookups. (Original patch
5387 - Add GETINFO status/enough-dir-info to let controllers tell whether
5388 Tor has downloaded sufficient directory information. (Patch
5390 - You can now use the ControlSocket option to tell Tor to listen for
5391 controller connections on Unix domain sockets on systems that
5392 support them. (Patch from Peter Palfrader.)
5393 - STREAM NEW events are generated for DNSPort requests and for
5394 tunneled directory connections. (Patch from Robert Hogan.)
5395 - New "GETINFO address-mappings/*" command to get address mappings
5396 with expiry information. "addr-mappings/*" is now deprecated.
5399 o Minor features (misc):
5400 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
5402 - The tor-gencert tool for v3 directory authorities now creates all
5403 files as readable to the file creator only, and write-protects
5404 the authority identity key.
5405 - When dumping memory usage, list bytes used in buffer memory
5407 - When running with dmalloc, dump more stats on hup and on exit.
5408 - Directory authorities now fail quickly and (relatively) harmlessly
5409 if they generate a network status document that is somehow
5412 o Traffic load balancing improvements:
5413 - If exit bandwidth ever exceeds one third of total bandwidth, then
5414 use the correct formula to weight exit nodes when choosing paths.
5415 (Based on patch from Mike Perry.)
5416 - Choose perfectly fairly among routers when choosing by bandwidth and
5417 weighting by fraction of bandwidth provided by exits. Previously, we
5418 would choose with only approximate fairness, and correct ourselves
5419 if we ran off the end of the list. [Bugfix on 0.1.2.x]
5421 o Performance improvements:
5422 - Be more aggressive with freeing buffer RAM or putting it on the
5424 - Use Critical Sections rather than Mutexes for synchronizing threads
5425 on win32; Mutexes are heavier-weight, and designed for synchronizing
5428 o Deprecated and removed features:
5429 - RedirectExits is now deprecated.
5430 - Stop allowing address masks that do not correspond to bit prefixes.
5431 We have warned about these for a really long time; now it's time
5432 to reject them. (Patch from croup.)
5434 o Minor bugfixes (directory):
5435 - Fix another crash bug related to extra-info caching. (Bug found by
5436 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
5437 - Directories no longer return a "304 not modified" when they don't
5438 have the networkstatus the client asked for. Also fix a memory
5439 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
5440 - We had accidentally labelled 0.1.2.x directory servers as not
5441 suitable for begin_dir requests, and had labelled no directory
5442 servers as suitable for uploading extra-info documents. [Bugfix
5445 o Minor bugfixes (dns):
5446 - Fix a crash when DNSPort is set more than once. (Patch from Robert
5447 Hogan.) [Bugfix on 0.2.0.2-alpha]
5448 - Add DNSPort connections to the global connection list, so that we
5449 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
5451 - Fix a dangling reference that could lead to a crash when DNSPort is
5452 changed or closed (Patch from Robert Hogan.) [Bugfix on
5455 o Minor bugfixes (controller):
5456 - Provide DNS expiry times in GMT, not in local time. For backward
5457 compatibility, ADDRMAP events only provide GMT expiry in an extended
5458 field. "GETINFO address-mappings" always does the right thing.
5459 - Use CRLF line endings properly in NS events.
5460 - Terminate multi-line control events properly. (Original patch
5461 from tup.) [Bugfix on 0.1.2.x-alpha]
5462 - Do not include spaces in SOURCE_ADDR fields in STREAM
5463 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
5466 Changes in version 0.1.2.15 - 2007-07-17
5467 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
5468 problems, fixes compilation on BSD, and fixes a variety of other
5469 bugs. Everybody should upgrade.
5471 o Major bugfixes (compilation):
5472 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
5474 o Major bugfixes (crashes):
5475 - Try even harder not to dereference the first character after
5476 an mmap(). Reported by lodger.
5477 - Fix a crash bug in directory authorities when we re-number the
5478 routerlist while inserting a new router.
5479 - When the cached-routers file is an even multiple of the page size,
5480 don't run off the end and crash. (Fixes bug 455; based on idea
5482 - Fix eventdns.c behavior on Solaris: It is critical to include
5483 orconfig.h _before_ sys/types.h, so that we can get the expected
5484 definition of _FILE_OFFSET_BITS.
5486 o Major bugfixes (security):
5487 - Fix a possible buffer overrun when using BSD natd support. Bug
5489 - When sending destroy cells from a circuit's origin, don't include
5490 the reason for tearing down the circuit. The spec says we didn't,
5491 and now we actually don't. Reported by lodger.
5492 - Keep streamids from different exits on a circuit separate. This
5493 bug may have allowed other routers on a given circuit to inject
5494 cells into streams. Reported by lodger; fixes bug 446.
5495 - If there's a never-before-connected-to guard node in our list,
5496 never choose any guards past it. This way we don't expand our
5497 guard list unless we need to.
5499 o Minor bugfixes (guard nodes):
5500 - Weight guard selection by bandwidth, so that low-bandwidth nodes
5501 don't get overused as guards.
5503 o Minor bugfixes (directory):
5504 - Correctly count the number of authorities that recommend each
5505 version. Previously, we were under-counting by 1.
5506 - Fix a potential crash bug when we load many server descriptors at
5507 once and some of them make others of them obsolete. Fixes bug 458.
5509 o Minor bugfixes (hidden services):
5510 - Stop tearing down the whole circuit when the user asks for a
5511 connection to a port that the hidden service didn't configure.
5514 o Minor bugfixes (misc):
5515 - On Windows, we were preventing other processes from reading
5516 cached-routers while Tor was running. Reported by janbar.
5517 - Fix a possible (but very unlikely) bug in picking routers by
5518 bandwidth. Add a log message to confirm that it is in fact
5519 unlikely. Patch from lodger.
5520 - Backport a couple of memory leak fixes.
5521 - Backport miscellaneous cosmetic bugfixes.
5524 Changes in version 0.2.0.2-alpha - 2007-06-02
5525 o Major bugfixes on 0.2.0.1-alpha:
5526 - Fix an assertion failure related to servers without extra-info digests.
5527 Resolves bugs 441 and 442.
5529 o Minor features (directory):
5530 - Support "If-Modified-Since" when answering HTTP requests for
5531 directories, running-routers documents, and network-status documents.
5532 (There's no need to support it for router descriptors, since those
5533 are downloaded by descriptor digest.)
5535 o Minor build issues:
5536 - Clear up some MIPSPro compiler warnings.
5537 - When building from a tarball on a machine that happens to have SVK
5538 installed, report the micro-revision as whatever version existed
5539 in the tarball, not as "x".
5542 Changes in version 0.2.0.1-alpha - 2007-06-01
5543 This early development snapshot provides new features for people running
5544 Tor as both a client and a server (check out the new RelayBandwidth
5545 config options); lets Tor run as a DNS proxy; and generally moves us
5546 forward on a lot of fronts.
5548 o Major features, server usability:
5549 - New config options RelayBandwidthRate and RelayBandwidthBurst:
5550 a separate set of token buckets for relayed traffic. Right now
5551 relayed traffic is defined as answers to directory requests, and
5552 OR connections that don't have any local circuits on them.
5554 o Major features, client usability:
5555 - A client-side DNS proxy feature to replace the need for
5556 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
5557 for DNS requests on port 9999, use the Tor network to resolve them
5558 anonymously, and send the reply back like a regular DNS server.
5559 The code still only implements a subset of DNS.
5560 - Make PreferTunneledDirConns and TunnelDirConns work even when
5561 we have no cached directory info. This means Tor clients can now
5562 do all of their connections protected by TLS.
5564 o Major features, performance and efficiency:
5565 - Directory authorities accept and serve "extra info" documents for
5566 routers. These documents contain fields from router descriptors
5567 that aren't usually needed, and that use a lot of excess
5568 bandwidth. Once these fields are removed from router descriptors,
5569 the bandwidth savings should be about 60%. [Partially implements
5571 - Servers upload extra-info documents to any authority that accepts
5572 them. Authorities (and caches that have been configured to download
5573 extra-info documents) download them as needed. [Partially implements
5575 - Change the way that Tor buffers data that it is waiting to write.
5576 Instead of queueing data cells in an enormous ring buffer for each
5577 client->OR or OR->OR connection, we now queue cells on a separate
5578 queue for each circuit. This lets us use less slack memory, and
5579 will eventually let us be smarter about prioritizing different kinds
5581 - Use memory pools to allocate cells with better speed and memory
5582 efficiency, especially on platforms where malloc() is inefficient.
5583 - Stop reading on edge connections when their corresponding circuit
5584 buffers are full; start again as the circuits empty out.
5586 o Major features, other:
5587 - Add an HSAuthorityRecordStats option that hidden service authorities
5588 can use to track statistics of overall hidden service usage without
5589 logging information that would be very useful to an attacker.
5590 - Start work implementing multi-level keys for directory authorities:
5591 Add a standalone tool to generate key certificates. (Proposal 103.)
5594 - Directory authorities now call routers Stable if they have an
5595 uptime of at least 30 days, even if that's not the median uptime
5596 in the network. Implements proposal 107, suggested by Kevin Bauer
5599 o Minor fixes (resource management):
5600 - Count the number of open sockets separately from the number
5601 of active connection_t objects. This will let us avoid underusing
5602 our allocated connection limit.
5603 - We no longer use socket pairs to link an edge connection to an
5604 anonymous directory connection or a DirPort test connection.
5605 Instead, we track the link internally and transfer the data
5606 in-process. This saves two sockets per "linked" connection (at the
5607 client and at the server), and avoids the nasty Windows socketpair()
5609 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
5610 for every single inactive connection_t. Free items from the
5611 4k/16k-buffer free lists when they haven't been used for a while.
5613 o Minor features (build):
5614 - Make autoconf search for libevent, openssl, and zlib consistently.
5615 - Update deprecated macros in configure.in.
5616 - When warning about missing headers, tell the user to let us
5617 know if the compile succeeds anyway, so we can downgrade the
5619 - Include the current subversion revision as part of the version
5620 string: either fetch it directly if we're in an SVN checkout, do
5621 some magic to guess it if we're in an SVK checkout, or use
5622 the last-detected version if we're building from a .tar.gz.
5623 Use this version consistently in log messages.
5625 o Minor features (logging):
5626 - Always prepend "Bug: " to any log message about a bug.
5627 - Put a platform string (e.g. "Linux i686") in the startup log
5628 message, so when people paste just their logs, we know if it's
5629 OpenBSD or Windows or what.
5630 - When logging memory usage, break down memory used in buffers by
5633 o Minor features (directory system):
5634 - New config option V2AuthoritativeDirectory that all directory
5635 authorities should set. This will let future authorities choose
5636 not to serve V2 directory information.
5637 - Directory authorities allow multiple router descriptors and/or extra
5638 info documents to be uploaded in a single go. This will make
5639 implementing proposal 104 simpler.
5641 o Minor features (controller):
5642 - Add a new config option __DisablePredictedCircuits designed for
5643 use by the controller, when we don't want Tor to build any circuits
5645 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
5646 so we can exit from the middle of the circuit.
5647 - Implement "getinfo status/circuit-established".
5648 - Implement "getinfo status/version/..." so a controller can tell
5649 whether the current version is recommended, and whether any versions
5650 are good, and how many authorities agree. (Patch from shibz.)
5652 o Minor features (hidden services):
5653 - Allow multiple HiddenServicePort directives with the same virtual
5654 port; when they occur, the user is sent round-robin to one
5655 of the target ports chosen at random. Partially fixes bug 393 by
5656 adding limited ad-hoc round-robining.
5658 o Minor features (other):
5660 - Add a new AutomapHostsOnResolve option: when it is enabled, any
5661 resolve request for hosts matching a given pattern causes Tor to
5662 generate an internal virtual address mapping for that host. This
5663 allows DNSPort to work sensibly with hidden service users. By
5664 default, .exit and .onion addresses are remapped; the list of
5665 patterns can be reconfigured with AutomapHostsSuffixes.
5666 - Add an "-F" option to tor-resolve to force a resolve for a .onion
5667 address. Thanks to the AutomapHostsOnResolve option, this is no
5668 longer a completely silly thing to do.
5669 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
5670 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
5671 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
5672 minus 1 byte: the actual maximum declared bandwidth.
5675 - Removed support for the old binary "version 0" controller protocol.
5676 This has been deprecated since 0.1.1, and warnings have been issued
5677 since 0.1.2. When we encounter a v0 control message, we now send
5678 back an error and close the connection.
5679 - Remove the old "dns worker" server DNS code: it hasn't been default
5680 since 0.1.2.2-alpha, and all the servers seem to be using the new
5683 o Minor bugfixes (portability):
5684 - Even though Windows is equally happy with / and \ as path separators,
5685 try to use \ consistently on Windows and / consistently on Unix: it
5686 makes the log messages nicer.
5687 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
5688 - Read resolv.conf files correctly on platforms where read() returns
5689 partial results on small file reads.
5691 o Minor bugfixes (directory):
5692 - Correctly enforce that elements of directory objects do not appear
5693 more often than they are allowed to appear.
5694 - When we are reporting the DirServer line we just parsed, we were
5695 logging the second stanza of the key fingerprint, not the first.
5697 o Minor bugfixes (logging):
5698 - When we hit an EOF on a log (probably because we're shutting down),
5699 don't try to remove the log from the list: just mark it as
5700 unusable. (Bulletproofs against bug 222.)
5702 o Minor bugfixes (other):
5703 - In the exitlist script, only consider the most recently published
5704 server descriptor for each server. Also, when the user requests
5705 a list of servers that _reject_ connections to a given address,
5706 explicitly exclude the IPs that also have servers that accept
5707 connections to that address. (Resolves bug 405.)
5708 - Stop allowing hibernating servers to be "stable" or "fast".
5709 - On Windows, we were preventing other processes from reading
5710 cached-routers while Tor was running. (Reported by janbar)
5711 - Make the NodeFamilies config option work. (Reported by
5712 lodger -- it has never actually worked, even though we added it
5714 - Check return values from pthread_mutex functions.
5715 - Don't save non-general-purpose router descriptors to the disk cache,
5716 because we have no way of remembering what their purpose was when
5718 - Add even more asserts to hunt down bug 417.
5719 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
5720 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
5721 Add a log message to confirm that it is in fact unlikely.
5723 o Minor bugfixes (controller):
5724 - Make 'getinfo fingerprint' return a 551 error if we're not a
5725 server, so we match what the control spec claims we do. Reported
5727 - Fix a typo in an error message when extendcircuit fails that
5728 caused us to not follow the \r\n-based delimiter protocol. Reported
5731 o Code simplifications and refactoring:
5732 - Stop passing around circuit_t and crypt_path_t pointers that are
5733 implicit in other procedure arguments.
5734 - Drop the old code to choke directory connections when the
5735 corresponding OR connections got full: thanks to the cell queue
5736 feature, OR conns don't get full any more.
5737 - Make dns_resolve() handle attaching connections to circuits
5738 properly, so the caller doesn't have to.
5739 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
5740 - Keep the connection array as a dynamic smartlist_t, rather than as
5741 a fixed-sized array. This is important, as the number of connections
5742 is becoming increasingly decoupled from the number of sockets.
5745 Changes in version 0.1.2.14 - 2007-05-25
5746 Tor 0.1.2.14 changes the addresses of two directory authorities (this
5747 change especially affects those who serve or use hidden services),
5748 and fixes several other crash- and security-related bugs.
5750 o Directory authority changes:
5751 - Two directory authorities (moria1 and moria2) just moved to new
5752 IP addresses. This change will particularly affect those who serve
5753 or use hidden services.
5755 o Major bugfixes (crashes):
5756 - If a directory server runs out of space in the connection table
5757 as it's processing a begin_dir request, it will free the exit stream
5758 but leave it attached to the circuit, leading to unpredictable
5759 behavior. (Reported by seeess, fixes bug 425.)
5760 - Fix a bug in dirserv_remove_invalid() that would cause authorities
5761 to corrupt memory under some really unlikely scenarios.
5762 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
5763 - Avoid segfaults when reading from mmaped descriptor file. (Reported
5766 o Major bugfixes (security):
5767 - When choosing an entry guard for a circuit, avoid using guards
5768 that are in the same family as the chosen exit -- not just guards
5769 that are exactly the chosen exit. (Reported by lodger.)
5771 o Major bugfixes (resource management):
5772 - If a directory authority is down, skip it when deciding where to get
5773 networkstatus objects or descriptors. Otherwise we keep asking
5774 every 10 seconds forever. Fixes bug 384.
5775 - Count it as a failure if we fetch a valid network-status but we
5776 don't want to keep it. Otherwise we'll keep fetching it and keep
5777 not wanting to keep it. Fixes part of bug 422.
5778 - If all of our dirservers have given us bad or no networkstatuses
5779 lately, then stop hammering them once per minute even when we
5780 think they're failed. Fixes another part of bug 422.
5783 - Actually set the purpose correctly for descriptors inserted with
5785 - When we have k non-v2 authorities in our DirServer config,
5786 we ignored the last k authorities in the list when updating our
5788 - Correctly back-off from requesting router descriptors that we are
5789 having a hard time downloading.
5790 - Read resolv.conf files correctly on platforms where read() returns
5791 partial results on small file reads.
5792 - Don't rebuild the entire router store every time we get 32K of
5793 routers: rebuild it when the journal gets very large, or when
5794 the gaps in the store get very large.
5797 - When routers publish SVN revisions in their router descriptors,
5798 authorities now include those versions correctly in networkstatus
5800 - Warn when using a version of libevent before 1.3b to run a server on
5801 OSX or BSD: these versions interact badly with userspace threads.
5804 Changes in version 0.1.2.13 - 2007-04-24
5805 This release features some major anonymity fixes, such as safer path
5806 selection; better client performance; faster bootstrapping, better
5807 address detection, and better DNS support for servers; write limiting as
5808 well as read limiting to make servers easier to run; and a huge pile of
5809 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
5811 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
5812 of the Freenode IRC network, remembering his patience and vision for
5813 free speech on the Internet.
5816 - Fix a memory leak when we ask for "all" networkstatuses and we
5817 get one we don't recognize.
5818 - Add more asserts to hunt down bug 417.
5819 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
5822 Changes in version 0.1.2.12-rc - 2007-03-16
5824 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
5825 directory information requested inside Tor connections (i.e. via
5826 begin_dir cells). It only triggered when the same connection was
5827 serving other data at the same time. Reported by seeess.
5830 - When creating a circuit via the controller, send a 'launched'
5831 event when we're done, so we follow the spec better.
5834 Changes in version 0.1.2.11-rc - 2007-03-15
5835 o Minor bugfixes (controller), reported by daejees:
5836 - Correct the control spec to match how the code actually responds
5837 to 'getinfo addr-mappings/*'.
5838 - The control spec described a GUARDS event, but the code
5839 implemented a GUARD event. Standardize on GUARD, but let people
5843 Changes in version 0.1.2.10-rc - 2007-03-07
5844 o Major bugfixes (Windows):
5845 - Do not load the NT services library functions (which may not exist)
5846 just to detect if we're a service trying to shut down. Now we run
5847 on Win98 and friends again.
5849 o Minor bugfixes (other):
5850 - Clarify a couple of log messages.
5851 - Fix a misleading socks5 error number.
5854 Changes in version 0.1.2.9-rc - 2007-03-02
5855 o Major bugfixes (Windows):
5856 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
5857 of the usual GCC "%llu". This prevents a bug when saving 64-bit
5858 int configuration values: the high-order 32 bits would get
5859 truncated. In particular, we were being bitten by the default
5860 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
5861 and maybe also bug 397.)
5863 o Minor bugfixes (performance):
5864 - Use OpenSSL's AES implementation on platforms where it's faster.
5865 This could save us as much as 10% CPU usage.
5867 o Minor bugfixes (server):
5868 - Do not rotate onion key immediately after setting it for the first
5871 o Minor bugfixes (directory authorities):
5872 - Stop calling servers that have been hibernating for a long time
5873 "stable". Also, stop letting hibernating or obsolete servers affect
5874 uptime and bandwidth cutoffs.
5875 - Stop listing hibernating servers in the v1 directory.
5877 o Minor bugfixes (hidden services):
5878 - Upload hidden service descriptors slightly less often, to reduce
5879 load on authorities.
5881 o Minor bugfixes (other):
5882 - Fix an assert that could trigger if a controller quickly set then
5883 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
5884 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
5886 - Fix a potential race condition in the rpm installer. Found by
5888 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
5889 of 2 as indicating that the server is completely bad; it sometimes
5890 means that the server is just bad for the request in question. (may fix
5891 the last of bug 326.)
5892 - Disable encrypted directory connections when we don't have a server
5893 descriptor for the destination. We'll get this working again in
5897 Changes in version 0.1.2.8-beta - 2007-02-26
5898 o Major bugfixes (crashes):
5899 - Stop crashing when the controller asks us to resetconf more than
5900 one config option at once. (Vidalia 0.0.11 does this.)
5901 - Fix a crash that happened on Win98 when we're given command-line
5902 arguments: don't try to load NT service functions from advapi32.dll
5903 except when we need them. (Bug introduced in 0.1.2.7-alpha;
5905 - Fix a longstanding obscure crash bug that could occur when
5906 we run out of DNS worker processes. (Resolves bug 390.)
5908 o Major bugfixes (hidden services):
5909 - Correctly detect whether hidden service descriptor downloads are
5910 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
5912 o Major bugfixes (accounting):
5913 - When we start during an accounting interval before it's time to wake
5914 up, remember to wake up at the correct time. (May fix bug 342.)
5916 o Minor bugfixes (controller):
5917 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
5918 clear the corresponding on_circuit variable, and remember later
5919 that we don't need to send a redundant CLOSED event. (Resolves part
5921 - Report events where a resolve succeeded or where we got a socks
5922 protocol error correctly, rather than calling both of them
5924 - Change reported stream target addresses to IP consistently when
5925 we finally get the IP from an exit node.
5926 - Send log messages to the controller even if they happen to be very
5929 o Minor bugfixes (other):
5930 - Display correct results when reporting which versions are
5931 recommended, and how recommended they are. (Resolves bug 383.)
5932 - Improve our estimates for directory bandwidth to be less random:
5933 guess that an unrecognized directory will have the average bandwidth
5934 from all known directories, not that it will have the average
5935 bandwidth from those directories earlier than it on the list.
5936 - If we start a server with ClientOnly 1, then set ClientOnly to 0
5937 and hup, stop triggering an assert based on an empty onion_key.
5938 - On platforms with no working mmap() equivalent, don't warn the
5939 user when cached-routers doesn't exist.
5940 - Warn the user when mmap() [or its equivalent] fails for some reason
5941 other than file-not-found.
5942 - Don't warn the user when cached-routers.new doesn't exist: that's
5943 perfectly fine when starting up for the first time.
5944 - When EntryNodes are configured, rebuild the guard list to contain,
5945 in order: the EntryNodes that were guards before; the rest of the
5946 EntryNodes; the nodes that were guards before.
5947 - Mask out all signals in sub-threads; only the libevent signal
5948 handler should be processing them. This should prevent some crashes
5949 on some machines using pthreads. (Patch from coderman.)
5950 - Fix switched arguments on memset in the implementation of
5951 tor_munmap() for systems with no mmap() call.
5952 - When Tor receives a router descriptor that it asked for, but
5953 no longer wants (because it has received fresh networkstatuses
5954 in the meantime), do not warn the user. Cache the descriptor if
5955 we're a cache; drop it if we aren't.
5956 - Make earlier entry guards _really_ get retried when the network
5958 - On a malformed DNS reply, always give an error to the corresponding
5960 - Build with recent libevents on platforms that do not define the
5961 nonstandard types "u_int8_t" and friends.
5963 o Minor features (controller):
5964 - Warn the user when an application uses the obsolete binary v0
5965 control protocol. We're planning to remove support for it during
5966 the next development series, so it's good to give people some
5968 - Add STREAM_BW events to report per-entry-stream bandwidth
5969 use. (Patch from Robert Hogan.)
5970 - Rate-limit SIGNEWNYM signals in response to controllers that
5971 impolitely generate them for every single stream. (Patch from
5972 mwenge; closes bug 394.)
5973 - Make REMAP stream events have a SOURCE (cache or exit), and
5974 make them generated in every case where we get a successful
5975 connected or resolved cell.
5977 o Minor bugfixes (performance):
5978 - Call router_have_min_dir_info half as often. (This is showing up in
5979 some profiles, but not others.)
5980 - When using GCC, make log_debug never get called at all, and its
5981 arguments never get evaluated, when no debug logs are configured.
5982 (This is showing up in some profiles, but not others.)
5985 - Remove some never-implemented options. Mark PathlenCoinWeight as
5987 - Implement proposal 106: Stop requiring clients to have well-formed
5988 certificates; stop checking nicknames in certificates. (Clients
5989 have certificates so that they can look like Tor servers, but in
5990 the future we might want to allow them to look like regular TLS
5991 clients instead. Nicknames in certificates serve no purpose other
5992 than making our protocol easier to recognize on the wire.)
5993 - Revise messages on handshake failure again to be even more clear about
5994 which are incoming connections and which are outgoing.
5995 - Discard any v1 directory info that's over 1 month old (for
5996 directories) or over 1 week old (for running-routers lists).
5997 - Do not warn when individual nodes in the configuration's EntryNodes,
5998 ExitNodes, etc are down: warn only when all possible nodes
5999 are down. (Fixes bug 348.)
6000 - Always remove expired routers and networkstatus docs before checking
6001 whether we have enough information to build circuits. (Fixes
6003 - Put a lower-bound on MaxAdvertisedBandwidth.
6006 Changes in version 0.1.2.7-alpha - 2007-02-06
6007 o Major bugfixes (rate limiting):
6008 - Servers decline directory requests much more aggressively when
6009 they're low on bandwidth. Otherwise they end up queueing more and
6010 more directory responses, which can't be good for latency.
6011 - But never refuse directory requests from local addresses.
6012 - Fix a memory leak when sending a 503 response for a networkstatus
6014 - Be willing to read or write on local connections (e.g. controller
6015 connections) even when the global rate limiting buckets are empty.
6016 - If our system clock jumps back in time, don't publish a negative
6017 uptime in the descriptor. Also, don't let the global rate limiting
6018 buckets go absurdly negative.
6019 - Flush local controller connection buffers periodically as we're
6020 writing to them, so we avoid queueing 4+ megabytes of data before
6023 o Major bugfixes (NT services):
6024 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
6025 command-line flag so that admins can override the default by saying
6026 "tor --service install --user "SomeUser"". This will not affect
6027 existing installed services. Also, warn the user that the service
6028 will look for its configuration file in the service user's
6029 %appdata% directory. (We can't do the 'hardwire the user's appdata
6030 directory' trick any more, since we may not have read access to that
6033 o Major bugfixes (other):
6034 - Previously, we would cache up to 16 old networkstatus documents
6035 indefinitely, if they came from nontrusted authorities. Now we
6036 discard them if they are more than 10 days old.
6037 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
6039 - Detect and reject malformed DNS responses containing circular
6041 - If exits are rare enough that we're not marking exits as guards,
6042 ignore exit bandwidth when we're deciding the required bandwidth
6044 - When we're handling a directory connection tunneled over Tor,
6045 don't fill up internal memory buffers with all the data we want
6046 to tunnel; instead, only add it if the OR connection that will
6047 eventually receive it has some room for it. (This can lead to
6048 slowdowns in tunneled dir connections; a better solution will have
6051 o Minor bugfixes (dns):
6052 - Add some defensive programming to eventdns.c in an attempt to catch
6053 possible memory-stomping bugs.
6054 - Detect and reject DNS replies containing IPv4 or IPv6 records with
6055 an incorrect number of bytes. (Previously, we would ignore the
6057 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
6058 in the correct order, and doesn't crash.
6059 - Free memory held in recently-completed DNS lookup attempts on exit.
6060 This was not a memory leak, but may have been hiding memory leaks.
6061 - Handle TTL values correctly on reverse DNS lookups.
6062 - Treat failure to parse resolv.conf as an error.
6064 o Minor bugfixes (other):
6065 - Fix crash with "tor --list-fingerprint" (reported by seeess).
6066 - When computing clock skew from directory HTTP headers, consider what
6067 time it was when we finished asking for the directory, not what
6069 - Expire socks connections if they spend too long waiting for the
6070 handshake to finish. Previously we would let them sit around for
6071 days, if the connecting application didn't close them either.
6072 - And if the socks handshake hasn't started, don't send a
6073 "DNS resolve socks failed" handshake reply; just close it.
6074 - Stop using C functions that OpenBSD's linker doesn't like.
6075 - Don't launch requests for descriptors unless we have networkstatuses
6076 from at least half of the authorities. This delays the first
6077 download slightly under pathological circumstances, but can prevent
6078 us from downloading a bunch of descriptors we don't need.
6079 - Do not log IPs with TLS failures for incoming TLS
6080 connections. (Fixes bug 382.)
6081 - If the user asks to use invalid exit nodes, be willing to use
6083 - Stop using the reserved ac_cv namespace in our configure script.
6084 - Call stat() slightly less often; use fstat() when possible.
6085 - Refactor the way we handle pending circuits when an OR connection
6086 completes or fails, in an attempt to fix a rare crash bug.
6087 - Only rewrite a conn's address based on X-Forwarded-For: headers
6088 if it's a parseable public IP address; and stop adding extra quotes
6089 to the resulting address.
6092 - Weight directory requests by advertised bandwidth. Now we can
6093 let servers enable write limiting but still allow most clients to
6094 succeed at their directory requests. (We still ignore weights when
6095 choosing a directory authority; I hope this is a feature.)
6098 - Create a new file ReleaseNotes which was the old ChangeLog. The
6099 new ChangeLog file now includes the summaries for all development
6101 - Check for addresses with invalid characters at the exit as well
6102 as at the client, and warn less verbosely when they fail. You can
6103 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
6104 - Adapt a patch from goodell to let the contrib/exitlist script
6105 take arguments rather than require direct editing.
6106 - Inform the server operator when we decide not to advertise a
6107 DirPort due to AccountingMax enabled or a low BandwidthRate. It
6108 was confusing Zax, so now we're hopefully more helpful.
6109 - Bring us one step closer to being able to establish an encrypted
6110 directory tunnel without knowing a descriptor first. Still not
6111 ready yet. As part of the change, now assume we can use a
6112 create_fast cell if we don't know anything about a router.
6113 - Allow exit nodes to use nameservers running on ports other than 53.
6114 - Servers now cache reverse DNS replies.
6115 - Add an --ignore-missing-torrc command-line option so that we can
6116 get the "use sensible defaults if the configuration file doesn't
6117 exist" behavior even when specifying a torrc location on the command
6120 o Minor features (controller):
6121 - Track reasons for OR connection failure; make these reasons
6122 available via the controller interface. (Patch from Mike Perry.)
6123 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
6124 can learn when clients are sending malformed hostnames to Tor.
6125 - Clean up documentation for controller status events.
6126 - Add a REMAP status to stream events to note that a stream's
6127 address has changed because of a cached address or a MapAddress
6131 Changes in version 0.1.2.6-alpha - 2007-01-09
6133 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
6134 connection handles more than 4 gigs in either direction, we crash.
6135 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
6136 advertised exit node, somebody might try to exit from us when
6137 we're bootstrapping and before we've built our descriptor yet.
6138 Refuse the connection rather than crashing.
6141 - Warn if we (as a server) find that we've resolved an address that we
6142 weren't planning to resolve.
6143 - Warn that using select() on any libevent version before 1.1 will be
6144 unnecessarily slow (even for select()).
6145 - Flush ERR-level controller status events just like we currently
6146 flush ERR-level log events, so that a Tor shutdown doesn't prevent
6147 the controller from learning about current events.
6149 o Minor features (more controller status events):
6150 - Implement EXTERNAL_ADDRESS server status event so controllers can
6151 learn when our address changes.
6152 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
6153 can learn when directories reject our descriptor.
6154 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
6155 can learn when a client application is speaking a non-socks protocol
6157 - Implement DANGEROUS_SOCKS client status event so controllers
6158 can learn when a client application is leaking DNS addresses.
6159 - Implement BUG general status event so controllers can learn when
6160 Tor is unhappy about its internal invariants.
6161 - Implement CLOCK_SKEW general status event so controllers can learn
6162 when Tor thinks the system clock is set incorrectly.
6163 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
6164 server status events so controllers can learn when their descriptors
6165 are accepted by a directory.
6166 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
6167 server status events so controllers can learn about Tor's progress in
6168 deciding whether it's reachable from the outside.
6169 - Implement BAD_LIBEVENT general status event so controllers can learn
6170 when we have a version/method combination in libevent that needs to
6172 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
6173 and DNS_USELESS server status events so controllers can learn
6174 about changes to DNS server status.
6176 o Minor features (directory):
6177 - Authorities no longer recommend exits as guards if this would shift
6178 too much load to the exit nodes.
6181 Changes in version 0.1.2.5-alpha - 2007-01-06
6183 - Enable write limiting as well as read limiting. Now we sacrifice
6184 capacity if we're pushing out lots of directory traffic, rather
6185 than overrunning the user's intended bandwidth limits.
6186 - Include TLS overhead when counting bandwidth usage; previously, we
6187 would count only the bytes sent over TLS, but not the bytes used
6189 - Support running the Tor service with a torrc not in the same
6190 directory as tor.exe and default to using the torrc located in
6191 the %appdata%\Tor\ of the user who installed the service. Patch
6193 - Servers now check for the case when common DNS requests are going to
6194 wildcarded addresses (i.e. all getting the same answer), and change
6195 their exit policy to reject *:* if it's happening.
6196 - Implement BEGIN_DIR cells, so we can connect to the directory
6197 server via TLS to do encrypted directory requests rather than
6198 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
6199 config options if you like.
6201 o Minor features (config and docs):
6202 - Start using the state file to store bandwidth accounting data:
6203 the bw_accounting file is now obsolete. We'll keep generating it
6204 for a while for people who are still using 0.1.2.4-alpha.
6205 - Try to batch changes to the state file so that we do as few
6206 disk writes as possible while still storing important things in
6208 - The state file and the bw_accounting file get saved less often when
6209 the AvoidDiskWrites config option is set.
6210 - Make PIDFile work on Windows (untested).
6211 - Add internal descriptions for a bunch of configuration options:
6212 accessible via controller interface and in comments in saved
6214 - Reject *:563 (NNTPS) in the default exit policy. We already reject
6215 NNTP by default, so this seems like a sensible addition.
6216 - Clients now reject hostnames with invalid characters. This should
6217 avoid some inadvertent info leaks. Add an option
6218 AllowNonRFC953Hostnames to disable this behavior, in case somebody
6219 is running a private network with hosts called @, !, and #.
6220 - Add a maintainer script to tell us which options are missing
6221 documentation: "make check-docs".
6222 - Add a new address-spec.txt document to describe our special-case
6223 addresses: .exit, .onion, and .noconnnect.
6225 o Minor features (DNS):
6226 - Ongoing work on eventdns infrastructure: now it has dns server
6227 and ipv6 support. One day Tor will make use of it.
6228 - Add client-side caching for reverse DNS lookups.
6229 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
6230 - When we change nameservers or IP addresses, reset and re-launch
6231 our tests for DNS hijacking.
6233 o Minor features (directory):
6234 - Authorities now specify server versions in networkstatus. This adds
6235 about 2% to the size of compressed networkstatus docs, and allows
6236 clients to tell which servers support BEGIN_DIR and which don't.
6237 The implementation is forward-compatible with a proposed future
6238 protocol version scheme not tied to Tor versions.
6239 - DirServer configuration lines now have an orport= option so
6240 clients can open encrypted tunnels to the authorities without
6241 having downloaded their descriptors yet. Enabled for moria1,
6242 moria2, tor26, and lefkada now in the default configuration.
6243 - Directory servers are more willing to send a 503 "busy" if they
6244 are near their write limit, especially for v1 directory requests.
6245 Now they can use their limited bandwidth for actual Tor traffic.
6246 - Clients track responses with status 503 from dirservers. After a
6247 dirserver has given us a 503, we try not to use it until an hour has
6248 gone by, or until we have no dirservers that haven't given us a 503.
6249 - When we get a 503 from a directory, and we're not a server, we don't
6250 count the failure against the total number of failures allowed
6251 for the thing we're trying to download.
6252 - Report X-Your-Address-Is correctly from tunneled directory
6253 connections; don't report X-Your-Address-Is when it's an internal
6254 address; and never believe reported remote addresses when they're
6256 - Protect against an unlikely DoS attack on directory servers.
6257 - Add a BadDirectory flag to network status docs so that authorities
6258 can (eventually) tell clients about caches they believe to be
6261 o Minor features (controller):
6262 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
6263 - Reimplement GETINFO so that info/names stays in sync with the
6265 - Implement "GETINFO fingerprint".
6266 - Implement "SETEVENTS GUARD" so controllers can get updates on
6267 entry guard status as it changes.
6269 o Minor features (clean up obsolete pieces):
6270 - Remove some options that have been deprecated since at least
6271 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
6272 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
6274 - We no longer look for identity and onion keys in "identity.key" and
6275 "onion.key" -- these were replaced by secret_id_key and
6276 secret_onion_key in 0.0.8pre1.
6277 - We no longer require unrecognized directory entries to be
6280 o Major bugfixes (security):
6281 - Stop sending the HttpProxyAuthenticator string to directory
6282 servers when directory connections are tunnelled through Tor.
6283 - Clients no longer store bandwidth history in the state file.
6284 - Do not log introduction points for hidden services if SafeLogging
6286 - When generating bandwidth history, round down to the nearest
6287 1k. When storing accounting data, round up to the nearest 1k.
6288 - When we're running as a server, remember when we last rotated onion
6289 keys, so that we will rotate keys once they're a week old even if
6290 we never stay up for a week ourselves.
6292 o Major bugfixes (other):
6293 - Fix a longstanding bug in eventdns that prevented the count of
6294 timed-out resolves from ever being reset. This bug caused us to
6295 give up on a nameserver the third time it timed out, and try it
6296 10 seconds later... and to give up on it every time it timed out
6298 - Take out the '5 second' timeout from the connection retry
6299 schedule. Now the first connect attempt will wait a full 10
6300 seconds before switching to a new circuit. Perhaps this will help
6301 a lot. Based on observations from Mike Perry.
6302 - Fix a bug on the Windows implementation of tor_mmap_file() that
6303 would prevent the cached-routers file from ever loading. Reported
6307 - Fix an assert failure when a directory authority sets
6308 AuthDirRejectUnlisted and then receives a descriptor from an
6309 unlisted router. Reported by seeess.
6310 - Avoid a double-free when parsing malformed DirServer lines.
6311 - Fix a bug when a BSD-style PF socket is first used. Patch from
6313 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
6314 to resolve an address at a given exit node even when they ask for
6316 - Servers no longer ever list themselves in their "family" line,
6317 even if configured to do so. This makes it easier to configure
6318 family lists conveniently.
6319 - When running as a server, don't fall back to 127.0.0.1 when no
6320 nameservers are configured in /etc/resolv.conf; instead, make the
6321 user fix resolv.conf or specify nameservers explicitly. (Resolves
6323 - Stop accepting certain malformed ports in configured exit policies.
6324 - Don't re-write the fingerprint file every restart, unless it has
6326 - Stop warning when a single nameserver fails: only warn when _all_ of
6327 our nameservers have failed. Also, when we only have one nameserver,
6328 raise the threshold for deciding that the nameserver is dead.
6329 - Directory authorities now only decide that routers are reachable
6330 if their identity keys are as expected.
6331 - When the user uses bad syntax in the Log config line, stop
6332 suggesting other bad syntax as a replacement.
6333 - Correctly detect ipv6 DNS capability on OpenBSD.
6335 o Minor bugfixes (controller):
6336 - Report the circuit number correctly in STREAM CLOSED events. Bug
6337 reported by Mike Perry.
6338 - Do not report bizarre values for results of accounting GETINFOs
6339 when the last second's write or read exceeds the allotted bandwidth.
6340 - Report "unrecognized key" rather than an empty string when the
6341 controller tries to fetch a networkstatus that doesn't exist.
6344 Changes in version 0.1.1.26 - 2006-12-14
6345 o Security bugfixes:
6346 - Stop sending the HttpProxyAuthenticator string to directory
6347 servers when directory connections are tunnelled through Tor.
6348 - Clients no longer store bandwidth history in the state file.
6349 - Do not log introduction points for hidden services if SafeLogging
6353 - Fix an assert failure when a directory authority sets
6354 AuthDirRejectUnlisted and then receives a descriptor from an
6355 unlisted router (reported by seeess).
6358 Changes in version 0.1.2.4-alpha - 2006-12-03
6360 - Add support for using natd; this allows FreeBSDs earlier than
6361 5.1.2 to have ipfw send connections through Tor without using
6362 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
6365 - Make all connections to addresses of the form ".noconnect"
6366 immediately get closed. This lets application/controller combos
6367 successfully test whether they're talking to the same Tor by
6368 watching for STREAM events.
6369 - Make cross.sh cross-compilation script work even when autogen.sh
6370 hasn't been run. (Patch from Michael Mohr.)
6371 - Statistics dumped by -USR2 now include a breakdown of public key
6372 operations, for profiling.
6375 - Fix a major leak when directory authorities parse their
6376 approved-routers list, a minor memory leak when we fail to pick
6377 an exit node, and a few rare leaks on errors.
6378 - Handle TransPort connections even when the server sends data before
6379 the client sends data. Previously, the connection would just hang
6380 until the client sent data. (Patch from tup based on patch from
6382 - Avoid assert failure when our cached-routers file is empty on
6386 - Don't log spurious warnings when we see a circuit close reason we
6387 don't recognize; it's probably just from a newer version of Tor.
6388 - Have directory authorities allow larger amounts of drift in uptime
6389 without replacing the server descriptor: previously, a server that
6390 restarted every 30 minutes could have 48 "interesting" descriptors
6392 - Start linking to the Tor specification and Tor reference manual
6393 correctly in the Windows installer.
6394 - Add Vidalia to the OS X uninstaller script, so when we uninstall
6395 Tor/Privoxy we also uninstall Vidalia.
6396 - Resume building on Irix64, and fix a lot of warnings from its
6398 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
6399 when we're running as a client.
6402 Changes in version 0.1.1.25 - 2006-11-04
6404 - When a client asks us to resolve (rather than connect to)
6405 an address, and we have a cached answer, give them the cached
6406 answer. Previously, we would give them no answer at all.
6407 - We were building exactly the wrong circuits when we predict
6408 hidden service requirements, meaning Tor would have to build all
6409 its circuits on demand.
6410 - If none of our live entry guards have a high uptime, but we
6411 require a guard with a high uptime, try adding a new guard before
6412 we give up on the requirement. This patch should make long-lived
6413 connections more stable on average.
6414 - When testing reachability of our DirPort, don't launch new
6415 tests when there's already one in progress -- unreachable
6416 servers were stacking up dozens of testing streams.
6418 o Security bugfixes:
6419 - When the user sends a NEWNYM signal, clear the client-side DNS
6420 cache too. Otherwise we continue to act on previous information.
6423 - Avoid a memory corruption bug when creating a hash table for
6425 - Avoid possibility of controller-triggered crash when misusing
6426 certain commands from a v0 controller on platforms that do not
6427 handle printf("%s",NULL) gracefully.
6428 - Avoid infinite loop on unexpected controller input.
6429 - Don't log spurious warnings when we see a circuit close reason we
6430 don't recognize; it's probably just from a newer version of Tor.
6431 - Add Vidalia to the OS X uninstaller script, so when we uninstall
6432 Tor/Privoxy we also uninstall Vidalia.
6435 Changes in version 0.1.2.3-alpha - 2006-10-29
6437 - Prepare for servers to publish descriptors less often: never
6438 discard a descriptor simply for being too old until either it is
6439 recommended by no authorities, or until we get a better one for
6440 the same router. Make caches consider retaining old recommended
6441 routers for even longer.
6442 - If most authorities set a BadExit flag for a server, clients
6443 don't think of it as a general-purpose exit. Clients only consider
6444 authorities that advertise themselves as listing bad exits.
6445 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
6446 headers for content, so that we can work better in the presence of
6447 caching HTTP proxies.
6448 - Allow authorities to list nodes as bad exits by fingerprint or by
6451 o Minor features, controller:
6452 - Add a REASON field to CIRC events; for backward compatibility, this
6453 field is sent only to controllers that have enabled the extended
6454 event format. Also, add additional reason codes to explain why
6455 a given circuit has been destroyed or truncated. (Patches from
6457 - Add a REMOTE_REASON field to extended CIRC events to tell the
6458 controller about why a remote OR told us to close a circuit.
6459 - Stream events also now have REASON and REMOTE_REASON fields,
6460 working much like those for circuit events.
6461 - There's now a GETINFO ns/... field so that controllers can ask Tor
6462 about the current status of a router.
6463 - A new event type "NS" to inform a controller when our opinion of
6464 a router's status has changed.
6465 - Add a GETINFO events/names and GETINFO features/names so controllers
6466 can tell which events and features are supported.
6467 - A new CLEARDNSCACHE signal to allow controllers to clear the
6468 client-side DNS cache without expiring circuits.
6470 o Security bugfixes:
6471 - When the user sends a NEWNYM signal, clear the client-side DNS
6472 cache too. Otherwise we continue to act on previous information.
6475 - Avoid sending junk to controllers or segfaulting when a controller
6476 uses EVENT_NEW_DESC with verbose nicknames.
6477 - Stop triggering asserts if the controller tries to extend hidden
6478 service circuits (reported by mwenge).
6479 - Avoid infinite loop on unexpected controller input.
6480 - When the controller does a "GETINFO network-status", tell it
6481 about even those routers whose descriptors are very old, and use
6482 long nicknames where appropriate.
6483 - Change NT service functions to be loaded on demand. This lets us
6484 build with MinGW without breaking Tor for Windows 98 users.
6485 - Do DirPort reachability tests less often, since a single test
6486 chews through many circuits before giving up.
6487 - In the hidden service example in torrc.sample, stop recommending
6488 esoteric and discouraged hidden service options.
6489 - When stopping an NT service, wait up to 10 sec for it to actually
6490 stop. (Patch from Matt Edman; resolves bug 295.)
6491 - Fix handling of verbose nicknames with ORCONN controller events:
6492 make them show up exactly when requested, rather than exactly when
6494 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
6495 printing a duplicate "$" in the keys we send (reported by mwenge).
6496 - Correctly set maximum connection limit on Cygwin. (This time
6498 - Try to detect Windows correctly when cross-compiling.
6499 - Detect the size of the routers file correctly even if it is
6500 corrupted (on systems without mmap) or not page-aligned (on systems
6501 with mmap). This bug was harmless.
6502 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
6503 to open a stream fails; now we do in more cases. This should
6504 make clients able to find a good exit faster in some cases, since
6505 unhandleable requests will now get an error rather than timing out.
6506 - Resolve two memory leaks when rebuilding the on-disk router cache
6507 (reported by fookoowa).
6508 - Clean up minor code warnings suggested by the MIPSpro C compiler,
6509 and reported by some Centos users.
6510 - Controller signals now work on non-Unix platforms that don't define
6511 SIGUSR1 and SIGUSR2 the way we expect.
6512 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
6513 values before failing, and always enables eventdns.
6514 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
6515 Try to fix this in configure.in by checking for most functions
6516 before we check for libevent.
6519 Changes in version 0.1.2.2-alpha - 2006-10-07
6521 - Make our async eventdns library on-by-default for Tor servers,
6522 and plan to deprecate the separate dnsworker threads.
6523 - Add server-side support for "reverse" DNS lookups (using PTR
6524 records so clients can determine the canonical hostname for a given
6525 IPv4 address). Only supported by servers using eventdns; servers
6526 now announce in their descriptors whether they support eventdns.
6527 - Specify and implement client-side SOCKS5 interface for reverse DNS
6528 lookups (see doc/socks-extensions.txt).
6529 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
6530 connect to directory servers through Tor. Previously, clients needed
6531 to find Tor exits to make private connections to directory servers.
6532 - Avoid choosing Exit nodes for entry or middle hops when the
6533 total bandwidth available from non-Exit nodes is much higher than
6534 the total bandwidth available from Exit nodes.
6535 - Workaround for name servers (like Earthlink's) that hijack failing
6536 DNS requests and replace the no-such-server answer with a "helpful"
6537 redirect to an advertising-driven search portal. Also work around
6538 DNS hijackers who "helpfully" decline to hijack known-invalid
6539 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
6540 lets you turn it off.
6541 - Send out a burst of long-range padding cells once we've established
6542 that we're reachable. Spread them over 4 circuits, so hopefully
6543 a few will be fast. This exercises our bandwidth and bootstraps
6544 us into the directory more quickly.
6546 o New/improved config options:
6547 - Add new config option "ResolvConf" to let the server operator
6548 choose an alternate resolve.conf file when using eventdns.
6549 - Add an "EnforceDistinctSubnets" option to control our "exclude
6550 servers on the same /16" behavior. It's still on by default; this
6551 is mostly for people who want to operate private test networks with
6552 all the machines on the same subnet.
6553 - If one of our entry guards is on the ExcludeNodes list, or the
6554 directory authorities don't think it's a good guard, treat it as
6555 if it were unlisted: stop using it as a guard, and throw it off
6556 the guards list if it stays that way for a long time.
6557 - Allow directory authorities to be marked separately as authorities
6558 for the v1 directory protocol, the v2 directory protocol, and
6559 as hidden service directories, to make it easier to retire old
6560 authorities. V1 authorities should set "HSAuthoritativeDir 1"
6561 to continue being hidden service authorities too.
6562 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
6564 o Minor features, controller:
6565 - Fix CIRC controller events so that controllers can learn the
6566 identity digests of non-Named servers used in circuit paths.
6567 - Let controllers ask for more useful identifiers for servers. Instead
6568 of learning identity digests for un-Named servers and nicknames
6569 for Named servers, the new identifiers include digest, nickname,
6570 and indication of Named status. Off by default; see control-spec.txt
6571 for more information.
6572 - Add a "getinfo address" controller command so it can display Tor's
6573 best guess to the user.
6574 - New controller event to alert the controller when our server
6575 descriptor has changed.
6576 - Give more meaningful errors on controller authentication failure.
6578 o Minor features, other:
6579 - When asked to resolve a hostname, don't use non-exit servers unless
6580 requested to do so. This allows servers with broken DNS to be
6581 useful to the network.
6582 - Divide eventdns log messages into warn and info messages.
6583 - Reserve the nickname "Unnamed" for routers that can't pick
6584 a hostname: any router can call itself Unnamed; directory
6585 authorities will never allocate Unnamed to any particular router;
6586 clients won't believe that any router is the canonical Unnamed.
6587 - Only include function names in log messages for info/debug messages.
6588 For notice/warn/err, the content of the message should be clear on
6589 its own, and printing the function name only confuses users.
6590 - Avoid some false positives during reachability testing: don't try
6591 to test via a server that's on the same /24 as us.
6592 - If we fail to build a circuit to an intended enclave, and it's
6593 not mandatory that we use that enclave, stop wanting it.
6594 - When eventdns is enabled, allow multithreaded builds on NetBSD and
6595 OpenBSD. (We had previously disabled threads on these platforms
6596 because they didn't have working thread-safe resolver functions.)
6598 o Major bugfixes, anonymity/security:
6599 - If a client asked for a server by name, and there's a named server
6600 in our network-status but we don't have its descriptor yet, we
6601 could return an unnamed server instead.
6602 - Fix NetBSD bug that could allow someone to force uninitialized RAM
6603 to be sent to a server's DNS resolver. This only affects NetBSD
6604 and other platforms that do not bounds-check tolower().
6605 - Reject (most) attempts to use Tor circuits with length one. (If
6606 many people start using Tor as a one-hop proxy, exit nodes become
6607 a more attractive target for compromise.)
6608 - Just because your DirPort is open doesn't mean people should be
6609 able to remotely teach you about hidden service descriptors. Now
6610 only accept rendezvous posts if you've got HSAuthoritativeDir set.
6612 o Major bugfixes, other:
6613 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
6614 - When a client asks the server to resolve (not connect to)
6615 an address, and it has a cached answer, give them the cached answer.
6616 Previously, the server would give them no answer at all.
6617 - Allow really slow clients to not hang up five minutes into their
6618 directory downloads (suggested by Adam J. Richter).
6619 - We were building exactly the wrong circuits when we anticipated
6620 hidden service requirements, meaning Tor would have to build all
6621 its circuits on demand.
6622 - Avoid crashing when we mmap a router cache file of size 0.
6623 - When testing reachability of our DirPort, don't launch new
6624 tests when there's already one in progress -- unreachable
6625 servers were stacking up dozens of testing streams.
6627 o Minor bugfixes, correctness:
6628 - If we're a directory mirror and we ask for "all" network status
6629 documents, we would discard status documents from authorities
6631 - Avoid a memory corruption bug when creating a hash table for
6633 - Avoid controller-triggered crash when misusing certain commands
6634 from a v0 controller on platforms that do not handle
6635 printf("%s",NULL) gracefully.
6636 - Don't crash when a controller sends a third argument to an
6637 "extendcircuit" request.
6638 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
6639 response; fix error code when "getinfo dir/status/" fails.
6640 - Avoid crash when telling controller stream-status and a stream
6642 - Patch from Adam Langley to fix assert() in eventdns.c.
6643 - Fix a debug log message in eventdns to say "X resolved to Y"
6644 instead of "X resolved to X".
6645 - Make eventdns give strings for DNS errors, not just error numbers.
6646 - Track unreachable entry guards correctly: don't conflate
6647 'unreachable by us right now' with 'listed as down by the directory
6648 authorities'. With the old code, if a guard was unreachable by
6649 us but listed as running, it would clog our guard list forever.
6650 - Behave correctly in case we ever have a network with more than
6651 2GB/s total advertised capacity.
6652 - Make TrackExitHosts case-insensitive, and fix the behavior of
6653 ".suffix" TrackExitHosts items to avoid matching in the middle of
6655 - Finally fix the openssl warnings from newer gccs that believe that
6656 ignoring a return value is okay, but casting a return value and
6657 then ignoring it is a sign of madness.
6658 - Prevent the contrib/exitlist script from printing the same
6659 result more than once.
6660 - Patch from Steve Hildrey: Generate network status correctly on
6661 non-versioning dirservers.
6662 - Don't listen to the X-Your-Address-Is hint if you did the lookup
6663 via Tor; otherwise you'll think you're the exit node's IP address.
6665 o Minor bugfixes, performance:
6666 - Two small performance improvements on parsing descriptors.
6667 - Major performance improvement on inserting descriptors: change
6668 algorithm from O(n^2) to O(n).
6669 - Make the common memory allocation path faster on machines where
6670 malloc(0) returns a pointer.
6671 - Start remembering X-Your-Address-Is directory hints even if you're
6672 a client, so you can become a server more smoothly.
6673 - Avoid duplicate entries on MyFamily line in server descriptor.
6675 o Packaging, features:
6676 - Remove architecture from OS X builds. The official builds are
6677 now universal binaries.
6678 - The Debian package now uses --verify-config when (re)starting,
6679 to distinguish configuration errors from other errors.
6680 - Update RPMs to require libevent 1.1b.
6682 o Packaging, bugfixes:
6683 - Patches so Tor builds with MinGW on Windows.
6684 - Patches so Tor might run on Cygwin again.
6685 - Resume building on non-gcc compilers and ancient gcc. Resume
6686 building with the -O0 compile flag. Resume building cleanly on
6688 - Run correctly on OS X platforms with case-sensitive filesystems.
6689 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
6690 - Add autoconf checks so Tor can build on Solaris x86 again.
6693 - Documented (and renamed) ServerDNSSearchDomains and
6694 ServerDNSResolvConfFile options.
6695 - Be clearer that the *ListenAddress directives can be repeated
6699 Changes in version 0.1.1.24 - 2006-09-29
6701 - Allow really slow clients to not hang up five minutes into their
6702 directory downloads (suggested by Adam J. Richter).
6703 - Fix major performance regression from 0.1.0.x: instead of checking
6704 whether we have enough directory information every time we want to
6705 do something, only check when the directory information has changed.
6706 This should improve client CPU usage by 25-50%.
6707 - Don't crash if, after a server has been running for a while,
6708 it can't resolve its hostname.
6711 - Allow Tor to start when RunAsDaemon is set but no logs are set.
6712 - Don't crash when the controller receives a third argument to an
6713 "extendcircuit" request.
6714 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
6715 response; fix error code when "getinfo dir/status/" fails.
6716 - Fix configure.in to not produce broken configure files with
6717 more recent versions of autoconf. Thanks to Clint for his auto*
6719 - Fix security bug on NetBSD that could allow someone to force
6720 uninitialized RAM to be sent to a server's DNS resolver. This
6721 only affects NetBSD and other platforms that do not bounds-check
6723 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
6724 methods: these are known to be buggy.
6725 - If we're a directory mirror and we ask for "all" network status
6726 documents, we would discard status documents from authorities
6730 Changes in version 0.1.2.1-alpha - 2006-08-27
6732 - Add "eventdns" async dns library from Adam Langley, tweaked to
6733 build on OSX and Windows. Only enabled if you pass the
6734 --enable-eventdns argument to configure.
6735 - Allow servers with no hostname or IP address to learn their
6736 IP address by asking the directory authorities. This code only
6737 kicks in when you would normally have exited with a "no address"
6738 error. Nothing's authenticated, so use with care.
6739 - Rather than waiting a fixed amount of time between retrying
6740 application connections, we wait only 5 seconds for the first,
6741 10 seconds for the second, and 15 seconds for each retry after
6742 that. Hopefully this will improve the expected user experience.
6743 - Patch from Tup to add support for transparent AP connections:
6744 this basically bundles the functionality of trans-proxy-tor
6745 into the Tor mainline. Now hosts with compliant pf/netfilter
6746 implementations can redirect TCP connections straight to Tor
6747 without diverting through SOCKS. Needs docs.
6748 - Busy directory servers save lots of memory by spooling server
6749 descriptors, v1 directories, and v2 networkstatus docs to buffers
6750 as needed rather than en masse. Also mmap the cached-routers
6751 files, so we don't need to keep the whole thing in memory too.
6752 - Automatically avoid picking more than one node from the same
6753 /16 network when constructing a circuit.
6754 - Revise and clean up the torrc.sample that we ship with; add
6755 a section for BandwidthRate and BandwidthBurst.
6758 - Split circuit_t into origin_circuit_t and or_circuit_t, and
6759 split connection_t into edge, or, dir, control, and base structs.
6760 These will save quite a bit of memory on busy servers, and they'll
6761 also help us track down bugs in the code and bugs in the spec.
6762 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
6763 or later. Log when we are doing this, so we can diagnose it when
6764 it fails. (Also, recommend libevent 1.1b for kqueue and
6765 win32 methods; deprecate libevent 1.0b harder; make libevent
6766 recommendation system saner.)
6767 - Start being able to build universal binaries on OS X (thanks
6769 - Export the default exit policy via the control port, so controllers
6770 don't need to guess what it is / will be later.
6771 - Add a man page entry for ProtocolWarnings.
6772 - Add TestVia config option to the man page.
6773 - Remove even more protocol-related warnings from Tor server logs,
6774 such as bad TLS handshakes and malformed begin cells.
6775 - Stop fetching descriptors if you're not a dir mirror and you
6776 haven't tried to establish any circuits lately. [This currently
6777 causes some dangerous behavior, because when you start up again
6778 you'll use your ancient server descriptors.]
6779 - New DirPort behavior: if you have your dirport set, you download
6780 descriptors aggressively like a directory mirror, whether or not
6782 - Get rid of the router_retry_connections notion. Now routers
6783 no longer try to rebuild long-term connections to directory
6784 authorities, and directory authorities no longer try to rebuild
6785 long-term connections to all servers. We still don't hang up
6786 connections in these two cases though -- we need to look at it
6787 more carefully to avoid flapping, and we likely need to wait til
6788 0.1.1.x is obsolete.
6789 - Drop compatibility with obsolete Tors that permit create cells
6790 to have the wrong circ_id_type.
6791 - Re-enable per-connection rate limiting. Get rid of the "OP
6792 bandwidth" concept. Lay groundwork for "bandwidth classes" --
6793 separate global buckets that apply depending on what sort of conn
6795 - Start publishing one minute or so after we find our ORPort
6796 to be reachable. This will help reduce the number of descriptors
6797 we have for ourselves floating around, since it's quite likely
6798 other things (e.g. DirPort) will change during that minute too.
6799 - Fork the v1 directory protocol into its own spec document,
6800 and mark dir-spec.txt as the currently correct (v2) spec.
6803 - When we find our DirPort to be reachable, publish a new descriptor
6804 so we'll tell the world (reported by pnx).
6805 - Publish a new descriptor after we hup/reload. This is important
6806 if our config has changed such that we'll want to start advertising
6807 our DirPort now, etc.
6808 - Allow Tor to start when RunAsDaemon is set but no logs are set.
6809 - When we have a state file we cannot parse, tell the user and
6810 move it aside. Now we avoid situations where the user starts
6811 Tor in 1904, Tor writes a state file with that timestamp in it,
6812 the user fixes her clock, and Tor refuses to start.
6813 - Fix configure.in to not produce broken configure files with
6814 more recent versions of autoconf. Thanks to Clint for his auto*
6816 - "tor --verify-config" now exits with -1(255) or 0 depending on
6817 whether the config options are bad or good.
6818 - Resolve bug 321 when using dnsworkers: append a period to every
6819 address we resolve at the exit node, so that we do not accidentally
6820 pick up local addresses, and so that failing searches are retried
6821 in the resolver search domains. (This is already solved for
6822 eventdns.) (This breaks Blossom servers for now.)
6823 - If we are using an exit enclave and we can't connect, e.g. because
6824 its webserver is misconfigured to not listen on localhost, then
6825 back off and try connecting from somewhere else before we fail.
6828 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
6829 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
6830 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
6831 when the IP address is mapped through MapAddress to a hostname.
6832 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
6833 useless IPv6 DNS resolves.
6834 - Patch suggested by Karsten Loesing: respond to SIGNAL command
6835 before we execute the signal, in case the signal shuts us down.
6836 - Clean up AllowInvalidNodes man page entry.
6837 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
6838 - Add more asserts to track down an assert error on a windows Tor
6839 server with connection_add being called with socket == -1.
6840 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
6841 - Fix misleading log messages: an entry guard that is "unlisted",
6842 as well as not known to be "down" (because we've never heard
6843 of it), is not therefore "up".
6844 - Remove code to special-case "-cvs" ending, since it has not
6845 actually mattered since 0.0.9.
6846 - Make our socks5 handling more robust to broken socks clients:
6847 throw out everything waiting on the buffer in between socks
6848 handshake phases, since they can't possibly (so the theory
6849 goes) have predicted what we plan to respond to them.
6852 Changes in version 0.1.1.23 - 2006-07-30
6854 - Fast Tor servers, especially exit nodes, were triggering asserts
6855 due to a bug in handling the list of pending DNS resolves. Some
6856 bugs still remain here; we're hunting them.
6857 - Entry guards could crash clients by sending unexpected input.
6858 - More fixes on reachability testing: if you find yourself reachable,
6859 then don't ever make any client requests (so you stop predicting
6860 circuits), then hup or have your clock jump, then later your IP
6861 changes, you won't think circuits are working, so you won't try to
6862 test reachability, so you won't publish.
6865 - Avoid a crash if the controller does a resetconf firewallports
6866 and then a setconf fascistfirewall=1.
6867 - Avoid an integer underflow when the dir authority decides whether
6868 a router is stable: we might wrongly label it stable, and compute
6869 a slightly wrong median stability, when a descriptor is published
6871 - Fix a place where we might trigger an assert if we can't build our
6872 own server descriptor yet.
6875 Changes in version 0.1.1.22 - 2006-07-05
6877 - Fix a big bug that was causing servers to not find themselves
6878 reachable if they changed IP addresses. Since only 0.1.1.22+
6879 servers can do reachability testing correctly, now we automatically
6880 make sure to test via one of these.
6881 - Fix to allow clients and mirrors to learn directory info from
6882 descriptor downloads that get cut off partway through.
6883 - Directory authorities had a bug in deciding if a newly published
6884 descriptor was novel enough to make everybody want a copy -- a few
6885 servers seem to be publishing new descriptors many times a minute.
6887 - Fix a rare bug that was causing some servers to complain about
6888 "closing wedged cpuworkers" and skip some circuit create requests.
6889 - Make the Exit flag in directory status documents actually work.
6892 Changes in version 0.1.1.21 - 2006-06-10
6893 o Crash and assert fixes from 0.1.1.20:
6894 - Fix a rare crash on Tor servers that have enabled hibernation.
6895 - Fix a seg fault on startup for Tor networks that use only one
6896 directory authority.
6897 - Fix an assert from a race condition that occurs on Tor servers
6898 while exiting, where various threads are trying to log that they're
6899 exiting, and delete the logs, at the same time.
6900 - Make our unit tests pass again on certain obscure platforms.
6903 - Add support for building SUSE RPM packages.
6904 - Speed up initial bootstrapping for clients: if we are making our
6905 first ever connection to any entry guard, then don't mark it down
6907 - When only one Tor server in the network is labelled as a guard,
6908 and we've already picked him, we would cycle endlessly picking him
6909 again, being unhappy about it, etc. Now we specifically exclude
6910 current guards when picking a new guard.
6911 - Servers send create cells more reliably after the TLS connection
6912 is established: we were sometimes forgetting to send half of them
6913 when we had more than one pending.
6914 - If we get a create cell that asks us to extend somewhere, but the
6915 Tor server there doesn't match the expected digest, we now send
6916 a destroy cell back, rather than silently doing nothing.
6917 - Make options->RedirectExit work again.
6918 - Make cookie authentication for the controller work again.
6919 - Stop being picky about unusual characters in the arguments to
6920 mapaddress. It's none of our business.
6921 - Add a new config option "TestVia" that lets you specify preferred
6922 middle hops to use for test circuits. Perhaps this will let me
6923 debug the reachability problems better.
6925 o Log / documentation fixes:
6926 - If we're a server and some peer has a broken TLS certificate, don't
6927 log about it unless ProtocolWarnings is set, i.e., we want to hear
6928 about protocol violations by others.
6929 - Fix spelling of VirtualAddrNetwork in man page.
6930 - Add a better explanation at the top of the autogenerated torrc file
6931 about what happened to our old torrc.
6934 Changes in version 0.1.1.20 - 2006-05-23
6936 - Downgrade a log severity where servers complain that they're
6938 - Avoid a compile warning on FreeBSD.
6939 - Remove string size limit on NEWDESC messages; solve bug 291.
6940 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
6941 more thoroughly when we're running on windows.
6944 Changes in version 0.1.1.19-rc - 2006-05-03
6946 - Regenerate our local descriptor if it's dirty and we try to use
6947 it locally (e.g. if it changes during reachability detection).
6948 - If we setconf our ORPort to 0, we continued to listen on the
6949 old ORPort and receive connections.
6950 - Avoid a second warning about machine/limits.h on Debian
6952 - Be willing to add our own routerinfo into the routerlist.
6953 Now authorities will include themselves in their directories
6954 and network-statuses.
6955 - Stop trying to upload rendezvous descriptors to every
6956 directory authority: only try the v1 authorities.
6957 - Servers no longer complain when they think they're not
6958 registered with the directory authorities. There were too many
6960 - Backport dist-rpm changes so rpms can be built without errors.
6963 - Implement an option, VirtualAddrMask, to set which addresses
6964 get handed out in response to mapaddress requests. This works
6965 around a bug in tsocks where 127.0.0.0/8 is never socksified.
6968 Changes in version 0.1.1.18-rc - 2006-04-10
6970 - Work harder to download live network-statuses from all the
6971 directory authorities we know about. Improve the threshold
6972 decision logic so we're more robust to edge cases.
6973 - When fetching rendezvous descriptors, we were willing to ask
6974 v2 authorities too, which would always return 404.
6977 - Stop listing down or invalid nodes in the v1 directory. This will
6978 reduce its bulk by about 1/3, and reduce load on directory
6980 - When deciding whether a router is Fast or Guard-worthy, consider
6981 his advertised BandwidthRate and not just the BandwidthCapacity.
6982 - No longer ship INSTALL and README files -- they are useless now.
6983 - Force rpmbuild to behave and honor target_cpu.
6984 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
6985 - Start to include translated versions of the tor-doc-*.html
6986 files, along with the screenshots. Still needs more work.
6987 - Start sending back 512 and 451 errors if mapaddress fails,
6988 rather than not sending anything back at all.
6989 - When we fail to bind or listen on an incoming or outgoing
6990 socket, we should close it before failing. otherwise we just
6991 leak it. (thanks to weasel for finding.)
6992 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
6993 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
6994 - Make NoPublish (even though deprecated) work again.
6995 - Fix a minor security flaw where a versioning auth dirserver
6996 could list a recommended version many times in a row to make
6997 clients more convinced that it's recommended.
6998 - Fix crash bug if there are two unregistered servers running
6999 with the same nickname, one of them is down, and you ask for
7000 them by nickname in your EntryNodes or ExitNodes. Also, try
7001 to pick the one that's running rather than an arbitrary one.
7002 - Fix an infinite loop we could hit if we go offline for too long.
7003 - Complain when we hit WSAENOBUFS on recv() or write() too.
7004 Perhaps this will help us hunt the bug.
7005 - If you're not a versioning dirserver, don't put the string
7006 "client-versions \nserver-versions \n" in your network-status.
7007 - Lower the minimum required number of file descriptors to 1000,
7008 so we can have some overhead for Valgrind on Linux, where the
7009 default ulimit -n is 1024.
7012 - Add tor.dizum.com as the fifth authoritative directory server.
7013 - Add a new config option FetchUselessDescriptors, off by default,
7014 for when you plan to run "exitlist" on your client and you want
7015 to know about even the non-running descriptors.
7018 Changes in version 0.1.1.17-rc - 2006-03-28
7020 - Clients and servers since 0.1.1.10-alpha have been expiring
7021 connections whenever they are idle for 5 minutes and they *do*
7022 have circuits on them. Oops. With this new version, clients will
7023 discard their previous entry guard choices and avoid choosing
7024 entry guards running these flawed versions.
7025 - Fix memory leak when uncompressing concatenated zlib streams. This
7026 was causing substantial leaks over time on Tor servers.
7027 - The v1 directory was including servers as much as 48 hours old,
7028 because that's how the new routerlist->routers works. Now only
7029 include them if they're 20 hours old or less.
7032 - Resume building on irix64, netbsd 2.0, etc.
7033 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
7035 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
7036 and it is confusing some users.
7037 - Mirrors stop caching the v1 directory so often.
7038 - Make the max number of old descriptors that a cache will hold
7039 rise with the number of directory authorities, so we can scale.
7040 - Change our win32 uname() hack to be more forgiving about what
7041 win32 versions it thinks it's found.
7044 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
7046 - When the controller's *setconf commands fail, collect an error
7047 message in a string and hand it back to the controller.
7048 - Make the v2 dir's "Fast" flag based on relative capacity, just
7049 like "Stable" is based on median uptime. Name everything in the
7050 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
7051 - Log server fingerprint on startup, so new server operators don't
7052 have to go hunting around their filesystem for it.
7053 - Return a robots.txt on our dirport to discourage google indexing.
7054 - Let the controller ask for GETINFO dir/status/foo so it can ask
7055 directly rather than connecting to the dir port. Only works when
7056 dirport is set for now.
7058 o New config options rather than constants in the code:
7059 - SocksTimeout: How long do we let a socks connection wait
7060 unattached before we fail it?
7061 - CircuitBuildTimeout: Cull non-open circuits that were born
7062 at least this many seconds ago.
7063 - CircuitIdleTimeout: Cull open clean circuits that were born
7064 at least this many seconds ago.
7067 Changes in version 0.1.1.16-rc - 2006-03-18
7068 o Bugfixes on 0.1.1.15-rc:
7069 - Fix assert when the controller asks to attachstream a connect-wait
7070 or resolve-wait stream.
7071 - Now do address rewriting when the controller asks us to attach
7072 to a particular circuit too. This will let Blossom specify
7073 "moria2.exit" without having to learn what moria2's IP address is.
7074 - Make the "tor --verify-config" command-line work again, so people
7075 can automatically check if their torrc will parse.
7076 - Authoritative dirservers no longer require an open connection from
7077 a server to consider him "reachable". We need this change because
7078 when we add new auth dirservers, old servers won't know not to
7080 - Let Tor build on Sun CC again.
7081 - Fix an off-by-one buffer size in dirserv.c that magically never
7082 hit our three authorities but broke sjmurdoch's own tor network.
7083 - If we as a directory mirror don't know of any v1 directory
7084 authorities, then don't try to cache any v1 directories.
7085 - Stop warning about unknown servers in our family when they are
7086 given as hex digests.
7087 - Stop complaining as quickly to the server operator that he
7088 hasn't registered his nickname/key binding.
7089 - Various cleanups so we can add new V2 Auth Dirservers.
7090 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
7091 reflect the updated flags in our v2 dir protocol.
7092 - Resume allowing non-printable characters for exit streams (both
7093 for connecting and for resolving). Now we tolerate applications
7094 that don't follow the RFCs. But continue to block malformed names
7097 o Bugfixes on 0.1.0.x:
7098 - Fix assert bug in close_logs(): when we close and delete logs,
7099 remove them all from the global "logfiles" list.
7100 - Fix minor integer overflow in calculating when we expect to use up
7101 our bandwidth allocation before hibernating.
7102 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
7103 there are multiple SSLs installed with different versions.
7104 - When we try to be a server and Address is not explicitly set and
7105 our hostname resolves to a private IP address, try to use an
7106 interface address if it has a public address. Now Windows machines
7107 that think of themselves as localhost can work by default.
7110 - Let the controller ask for GETINFO dir/server/foo so it can ask
7111 directly rather than connecting to the dir port.
7112 - Let the controller tell us about certain router descriptors
7113 that it doesn't want Tor to use in circuits. Implement
7114 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
7115 - New config option SafeSocks to reject all application connections
7116 using unsafe socks protocols. Defaults to off.
7119 Changes in version 0.1.1.15-rc - 2006-03-11
7120 o Bugfixes and cleanups:
7121 - When we're printing strings from the network, don't try to print
7122 non-printable characters. This protects us against shell escape
7123 sequence exploits, and also against attacks to fool humans into
7124 misreading their logs.
7125 - Fix a bug where Tor would fail to establish any connections if you
7126 left it off for 24 hours and then started it: we were happy with
7127 the obsolete network statuses, but they all referred to router
7128 descriptors that were too old to fetch, so we ended up with no
7129 valid router descriptors.
7130 - Fix a seg fault in the controller's "getinfo orconn-status"
7131 command while listing status on incoming handshaking connections.
7132 Introduce a status name "NEW" for these connections.
7133 - If we get a linelist or linelist_s config option from the torrc
7134 (e.g. ExitPolicy) and it has no value, warn and skip rather than
7135 silently resetting it to its default.
7136 - Don't abandon entry guards until they've been down or gone for
7138 - Cleaner and quieter log messages.
7141 - New controller signal NEWNYM that makes new application requests
7143 - Add a new circuit purpose 'controller' to let the controller ask
7144 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
7145 controller command to let you specify the purpose if you're
7146 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
7147 command to let you change a circuit's purpose after it's been
7149 - Accept "private:*" in routerdesc exit policies; not generated yet
7150 because older Tors do not understand it.
7151 - Add BSD-style contributed startup script "rc.subr" from Peter
7155 Changes in version 0.1.1.14-alpha - 2006-02-20
7156 o Bugfixes on 0.1.1.x:
7157 - Don't die if we ask for a stdout or stderr log (even implicitly)
7158 and we're set to RunAsDaemon -- just warn.
7159 - We still had a few bugs in the OR connection rotation code that
7160 caused directory servers to slowly aggregate connections to other
7161 fast Tor servers. This time for sure!
7162 - Make log entries on Win32 include the name of the function again.
7163 - We were treating a pair of exit policies if they were equal even
7164 if one said accept and the other said reject -- causing us to
7165 not always publish a new descriptor since we thought nothing
7167 - Retry pending server downloads as well as pending networkstatus
7168 downloads when we unexpectedly get a socks request.
7169 - We were ignoring the IS_FAST flag in the directory status,
7170 meaning we were willing to pick trivial-bandwidth nodes for "fast"
7172 - If the controller's SAVECONF command fails (e.g. due to file
7173 permissions), let the controller know that it failed.
7176 - If we're trying to be a Tor server and running Windows 95/98/ME
7177 as a server, explain that we'll likely crash.
7178 - When we're a server, a client asks for an old-style directory,
7179 and our write bucket is empty, don't give it to him. This way
7180 small servers can continue to serve the directory *sometimes*,
7181 without getting overloaded.
7182 - Compress exit policies even more -- look for duplicate lines
7184 - Clients now honor the "guard" flag in the router status when
7185 picking entry guards, rather than looking at is_fast or is_stable.
7186 - Retain unrecognized lines in $DATADIR/state file, so that we can
7187 be forward-compatible.
7188 - Generate 18.0.0.0/8 address policy format in descs when we can;
7189 warn when the mask is not reducible to a bit-prefix.
7190 - Let the user set ControlListenAddress in the torrc. This can be
7191 dangerous, but there are some cases (like a secured LAN) where it
7193 - Split ReachableAddresses into ReachableDirAddresses and
7194 ReachableORAddresses, so we can restrict Dir conns to port 80
7195 and OR conns to port 443.
7196 - Now we can target arch and OS in rpm builds (contributed by
7197 Phobos). Also make the resulting dist-rpm filename match the
7199 - New config options to help controllers: FetchServerDescriptors
7200 and FetchHidServDescriptors for whether to fetch server
7201 info and hidserv info or let the controller do it, and
7202 PublishServerDescriptor and PublishHidServDescriptors.
7203 - Also let the controller set the __AllDirActionsPrivate config
7204 option if you want all directory fetches/publishes to happen via
7205 Tor (it assumes your controller bootstraps your circuits).
7208 Changes in version 0.1.0.17 - 2006-02-17
7209 o Crash bugfixes on 0.1.0.x:
7210 - When servers with a non-zero DirPort came out of hibernation,
7211 sometimes they would trigger an assert.
7213 o Other important bugfixes:
7214 - On platforms that don't have getrlimit (like Windows), we were
7215 artificially constraining ourselves to a max of 1024
7216 connections. Now just assume that we can handle as many as 15000
7217 connections. Hopefully this won't cause other problems.
7219 o Backported features:
7220 - When we're a server, a client asks for an old-style directory,
7221 and our write bucket is empty, don't give it to him. This way
7222 small servers can continue to serve the directory *sometimes*,
7223 without getting overloaded.
7224 - Whenever you get a 503 in response to a directory fetch, try
7225 once more. This will become important once servers start sending
7226 503's whenever they feel busy.
7227 - Fetch a new directory every 120 minutes, not every 40 minutes.
7228 Now that we have hundreds of thousands of users running the old
7229 directory algorithm, it's starting to hurt a lot.
7230 - Bump up the period for forcing a hidden service descriptor upload
7231 from 20 minutes to 1 hour.
7234 Changes in version 0.1.1.13-alpha - 2006-02-09
7235 o Crashes in 0.1.1.x:
7236 - When you tried to setconf ORPort via the controller, Tor would
7237 crash. So people using TorCP to become a server were sad.
7238 - Solve (I hope) the stack-smashing bug that we were seeing on fast
7239 servers. The problem appears to be something do with OpenSSL's
7240 random number generation, or how we call it, or something. Let me
7241 know if the crashes continue.
7242 - Turn crypto hardware acceleration off by default, until we find
7243 somebody smart who can test it for us. (It appears to produce
7244 seg faults in at least some cases.)
7245 - Fix a rare assert error when we've tried all intro points for
7246 a hidden service and we try fetching the service descriptor again:
7247 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
7250 - Fix a major load balance bug: we were round-robining in 16 KB
7251 chunks, and servers with bandwidthrate of 20 KB, while downloading
7252 a 600 KB directory, would starve their other connections. Now we
7253 try to be a bit more fair.
7254 - Dir authorities and mirrors were never expiring the newest
7255 descriptor for each server, causing memory and directory bloat.
7256 - Fix memory-bloating and connection-bloating bug on servers: We
7257 were never closing any connection that had ever had a circuit on
7258 it, because we were checking conn->n_circuits == 0, yet we had a
7259 bug that let it go negative.
7260 - Make Tor work using squid as your http proxy again -- squid
7261 returns an error if you ask for a URL that's too long, and it uses
7262 a really generic error message. Plus, many people are behind a
7263 transparent squid so they don't even realize it.
7264 - On platforms that don't have getrlimit (like Windows), we were
7265 artificially constraining ourselves to a max of 1024
7266 connections. Now just assume that we can handle as many as 15000
7267 connections. Hopefully this won't cause other problems.
7268 - Add a new config option ExitPolicyRejectPrivate which defaults to
7269 1. This means all exit policies will begin with rejecting private
7270 addresses, unless the server operator explicitly turns it off.
7273 - Clients no longer download descriptors for non-running
7275 - Before we add new directory authorities, we should make it
7276 clear that only v1 authorities should receive/publish hidden
7277 service descriptors.
7280 - As soon as we've fetched some more directory info, immediately
7281 try to download more server descriptors. This way we don't have
7282 a 10 second pause during initial bootstrapping.
7283 - Remove even more loud log messages that the server operator can't
7285 - When we're running an obsolete or un-recommended version, make
7286 the log message more clear about what the problem is and what
7287 versions *are* still recommended.
7288 - Provide a more useful warn message when our onion queue gets full:
7289 the CPU is too slow or the exit policy is too liberal.
7290 - Don't warn when we receive a 503 from a dirserver/cache -- this
7291 will pave the way for them being able to refuse if they're busy.
7292 - When we fail to bind a listener, try to provide a more useful
7293 log message: e.g., "Is Tor already running?"
7294 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
7295 Goldberg can prove things about our handshake protocol more
7297 - MaxConn has been obsolete for a while now. Document the ConnLimit
7298 config option, which is a *minimum* number of file descriptors
7299 that must be available else Tor refuses to start.
7300 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
7301 if you log to syslog and want something other than LOG_DAEMON.
7302 - Make dirservers generate a separate "guard" flag to mean,
7303 "would make a good entry guard". Make clients parse it and vote
7304 on it. Not used by clients yet.
7305 - Implement --with-libevent-dir option to ./configure. Also, improve
7306 search techniques to find libevent, and use those for openssl too.
7307 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
7308 - Only start testing reachability once we've established a
7309 circuit. This will make startup on dirservers less noisy.
7310 - Don't try to upload hidden service descriptors until we have
7311 established a circuit.
7312 - Fix the controller's "attachstream 0" command to treat conn like
7313 it just connected, doing address remapping, handling .exit and
7314 .onion idioms, and so on. Now we're more uniform in making sure
7315 that the controller hears about new and closing connections.
7318 Changes in version 0.1.1.12-alpha - 2006-01-11
7319 o Bugfixes on 0.1.1.x:
7320 - The fix to close duplicate server connections was closing all
7321 Tor client connections if they didn't establish a circuit
7322 quickly enough. Oops.
7323 - Fix minor memory issue (double-free) that happened on exit.
7325 o Bugfixes on 0.1.0.x:
7326 - Tor didn't warn when it failed to open a log file.
7329 Changes in version 0.1.1.11-alpha - 2006-01-10
7330 o Crashes in 0.1.1.x:
7331 - Include all the assert/crash fixes from 0.1.0.16.
7332 - If you start Tor and then quit very quickly, there were some
7333 races that tried to free things that weren't allocated yet.
7334 - Fix a rare memory stomp if you're running hidden services.
7335 - Fix segfault when specifying DirServer in config without nickname.
7336 - Fix a seg fault when you finish connecting to a server but at
7337 that moment you dump his server descriptor.
7338 - Extendcircuit and Attachstream controller commands would
7339 assert/crash if you don't give them enough arguments.
7340 - Fix an assert error when we're out of space in the connection_list
7341 and we try to post a hidden service descriptor (reported by weasel).
7342 - If you specify a relative torrc path and you set RunAsDaemon in
7343 your torrc, then it chdir()'s to the new directory. If you HUP,
7344 it tries to load the new torrc location, fails, and exits.
7345 The fix: no longer allow a relative path to torrc using -f.
7348 - Implement "entry guards": automatically choose a handful of entry
7349 nodes and stick with them for all circuits. Only pick new guards
7350 when the ones you have are unsuitable, and if the old guards
7351 become suitable again, switch back. This will increase security
7352 dramatically against certain end-point attacks. The EntryNodes
7353 config option now provides some hints about which entry guards you
7354 want to use most; and StrictEntryNodes means to only use those.
7355 - New directory logic: download by descriptor digest, not by
7356 fingerprint. Caches try to download all listed digests from
7357 authorities; clients try to download "best" digests from caches.
7358 This avoids partitioning and isolating attacks better.
7359 - Make the "stable" router flag in network-status be the median of
7360 the uptimes of running valid servers, and make clients pay
7361 attention to the network-status flags. Thus the cutoff adapts
7362 to the stability of the network as a whole, making IRC, IM, etc
7363 connections more reliable.
7366 - Tor servers with dynamic IP addresses were needing to wait 18
7367 hours before they could start doing reachability testing using
7368 the new IP address and ports. This is because they were using
7369 the internal descriptor to learn what to test, yet they were only
7370 rebuilding the descriptor once they decided they were reachable.
7371 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
7372 to download certain server descriptors, throw them away, and then
7373 fetch them again after 30 minutes. Now mirrors throw away these
7374 server descriptors so clients can't get them.
7375 - We were leaving duplicate connections to other ORs open for a week,
7376 rather than closing them once we detect a duplicate. This only
7377 really affected authdirservers, but it affected them a lot.
7378 - Spread the authdirservers' reachability testing over the entire
7379 testing interval, so we don't try to do 500 TLS's at once every
7383 - If the network is down, and we try to connect to a conn because
7384 we have a circuit in mind, and we timeout (30 seconds) because the
7385 network never answers, we were expiring the circuit, but we weren't
7386 obsoleting the connection or telling the entry_guards functions.
7387 - Some Tor servers process billions of cells per day. These statistics
7388 need to be uint64_t's.
7389 - Check for integer overflows in more places, when adding elements
7390 to smartlists. This could possibly prevent a buffer overflow
7391 on malicious huge inputs. I don't see any, but I haven't looked
7393 - ReachableAddresses kept growing new "reject *:*" lines on every
7395 - When you "setconf log" via the controller, it should remove all
7396 logs. We were automatically adding back in a "log notice stdout".
7397 - Newly bootstrapped Tor networks couldn't establish hidden service
7398 circuits until they had nodes with high uptime. Be more tolerant.
7399 - We were marking servers down when they could not answer every piece
7400 of the directory request we sent them. This was far too harsh.
7401 - Fix the torify (tsocks) config file to not use Tor for localhost
7403 - Directory authorities now go to the proper authority when asking for
7404 a networkstatus, even when they want a compressed one.
7405 - Fix a harmless bug that was causing Tor servers to log
7406 "Got an end because of misc error, but we're not an AP. Closing."
7407 - Authorities were treating their own descriptor changes as cosmetic,
7408 meaning the descriptor available in the network-status and the
7409 descriptor that clients downloaded were different.
7410 - The OS X installer was adding a symlink for tor_resolve but
7411 the binary was called tor-resolve (reported by Thomas Hardly).
7412 - Workaround a problem with some http proxies where they refuse GET
7413 requests that specify "Content-Length: 0" (reported by Adrian).
7414 - Fix wrong log message when you add a "HiddenServiceNodes" config
7415 line without any HiddenServiceDir line (reported by Chris Thomas).
7418 - Write the TorVersion into the state file so we have a prayer of
7419 keeping forward and backward compatibility.
7420 - Revive the FascistFirewall config option rather than eliminating it:
7421 now it's a synonym for ReachableAddresses *:80,*:443.
7422 - Clients choose directory servers from the network status lists,
7423 not from their internal list of router descriptors. Now they can
7424 go to caches directly rather than needing to go to authorities
7426 - Directory authorities ignore router descriptors that have only
7427 cosmetic differences: do this for 0.1.0.x servers now too.
7428 - Add a new flag to network-status indicating whether the server
7429 can answer v2 directory requests too.
7430 - Authdirs now stop whining so loudly about bad descriptors that
7431 they fetch from other dirservers. So when there's a log complaint,
7432 it's for sure from a freshly uploaded descriptor.
7433 - Reduce memory requirements in our structs by changing the order
7435 - There used to be two ways to specify your listening ports in a
7436 server descriptor: on the "router" line and with a separate "ports"
7437 line. Remove support for the "ports" line.
7438 - New config option "AuthDirRejectUnlisted" for auth dirservers as
7439 a panic button: if we get flooded with unusable servers we can
7440 revert to only listing servers in the approved-routers file.
7441 - Auth dir servers can now mark a fingerprint as "!reject" or
7442 "!invalid" in the approved-routers file (as its nickname), to
7443 refuse descriptors outright or include them but marked as invalid.
7444 - Servers store bandwidth history across restarts/crashes.
7445 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
7446 get a better idea of why their circuits failed. Not used yet.
7447 - Directory mirrors now cache up to 16 unrecognized network-status
7448 docs. Now we can add new authdirservers and they'll be cached too.
7449 - When picking a random directory, prefer non-authorities if any
7451 - New controller option "getinfo desc/all-recent" to fetch the
7452 latest server descriptor for every router that Tor knows about.
7455 Changes in version 0.1.0.16 - 2006-01-02
7456 o Crash bugfixes on 0.1.0.x:
7457 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
7458 corrupting the heap, losing FDs, or crashing when we need to resize
7459 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
7460 - It turns out sparc64 platforms crash on unaligned memory access
7461 too -- so detect and avoid this.
7462 - Handle truncated compressed data correctly (by detecting it and
7464 - Fix possible-but-unlikely free(NULL) in control.c.
7465 - When we were closing connections, there was a rare case that
7466 stomped on memory, triggering seg faults and asserts.
7467 - Avoid potential infinite recursion when building a descriptor. (We
7468 don't know that it ever happened, but better to fix it anyway.)
7469 - We were neglecting to unlink marked circuits from soon-to-close OR
7470 connections, which caused some rare scribbling on freed memory.
7471 - Fix a memory stomping race bug when closing the joining point of two
7472 rendezvous circuits.
7473 - Fix an assert in time parsing found by Steven Murdoch.
7475 o Other bugfixes on 0.1.0.x:
7476 - When we're doing reachability testing, provide more useful log
7477 messages so the operator knows what to expect.
7478 - Do not check whether DirPort is reachable when we are suppressing
7479 advertising it because of hibernation.
7480 - When building with -static or on Solaris, we sometimes needed -ldl.
7481 - When we're deciding whether a stream has enough circuits around
7482 that can handle it, count the freshly dirty ones and not the ones
7483 that are so dirty they won't be able to handle it.
7484 - When we're expiring old circuits, we had a logic error that caused
7485 us to close new rendezvous circuits rather than old ones.
7486 - Give a more helpful log message when you try to change ORPort via
7487 the controller: you should upgrade Tor if you want that to work.
7488 - We were failing to parse Tor versions that start with "Tor ".
7489 - Tolerate faulty streams better: when a stream fails for reason
7490 exitpolicy, stop assuming that the router is lying about his exit
7491 policy. When a stream fails for reason misc, allow it to retry just
7492 as if it was resolvefailed. When a stream has failed three times,
7493 reset its failure count so we can try again and get all three tries.
7496 Changes in version 0.1.1.10-alpha - 2005-12-11
7497 o Correctness bugfixes on 0.1.0.x:
7498 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
7499 corrupting the heap, losing FDs, or crashing when we need to resize
7500 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
7501 - Stop doing the complex voodoo overkill checking for insecure
7502 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
7503 - When we were closing connections, there was a rare case that
7504 stomped on memory, triggering seg faults and asserts.
7505 - We were neglecting to unlink marked circuits from soon-to-close OR
7506 connections, which caused some rare scribbling on freed memory.
7507 - When we're deciding whether a stream has enough circuits around
7508 that can handle it, count the freshly dirty ones and not the ones
7509 that are so dirty they won't be able to handle it.
7510 - Recover better from TCP connections to Tor servers that are
7511 broken but don't tell you (it happens!); and rotate TLS
7512 connections once a week.
7513 - When we're expiring old circuits, we had a logic error that caused
7514 us to close new rendezvous circuits rather than old ones.
7515 - Fix a scary-looking but apparently harmless bug where circuits
7516 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
7517 servers, and never switch to state CIRCUIT_STATE_OPEN.
7518 - When building with -static or on Solaris, we sometimes needed to
7520 - Give a useful message when people run Tor as the wrong user,
7521 rather than telling them to start chowning random directories.
7522 - We were failing to inform the controller about new .onion streams.
7524 o Security bugfixes on 0.1.0.x:
7525 - Refuse server descriptors if the fingerprint line doesn't match
7526 the included identity key. Tor doesn't care, but other apps (and
7527 humans) might actually be trusting the fingerprint line.
7528 - We used to kill the circuit when we receive a relay command we
7529 don't recognize. Now we just drop it.
7530 - Start obeying our firewall options more rigorously:
7531 . If we can't get to a dirserver directly, try going via Tor.
7532 . Don't ever try to connect (as a client) to a place our
7533 firewall options forbid.
7534 . If we specify a proxy and also firewall options, obey the
7535 firewall options even when we're using the proxy: some proxies
7536 can only proxy to certain destinations.
7537 - Fix a bug found by Lasse Overlier: when we were making internal
7538 circuits (intended to be cannibalized later for rendezvous and
7539 introduction circuits), we were picking them so that they had
7540 useful exit nodes. There was no need for this, and it actually
7541 aids some statistical attacks.
7542 - Start treating internal circuits and exit circuits separately.
7543 It's important to keep them separate because internal circuits
7544 have their last hops picked like middle hops, rather than like
7545 exit hops. So exiting on them will break the user's expectations.
7547 o Bugfixes on 0.1.1.x:
7548 - Take out the mis-feature where we tried to detect IP address
7549 flapping for people with DynDNS, and chose not to upload a new
7550 server descriptor sometimes.
7551 - Try to be compatible with OpenSSL 0.9.6 again.
7552 - Log fix: when the controller is logging about .onion addresses,
7553 sometimes it didn't include the ".onion" part of the address.
7554 - Don't try to modify options->DirServers internally -- if the
7555 user didn't specify any, just add the default ones directly to
7556 the trusted dirserver list. This fixes a bug where people running
7557 controllers would use SETCONF on some totally unrelated config
7558 option, and Tor would start yelling at them about changing their
7560 - Let the controller's redirectstream command specify a port, in
7561 case the controller wants to change that too.
7562 - When we requested a pile of server descriptors, we sometimes
7563 accidentally launched a duplicate request for the first one.
7564 - Bugfix for trackhostexits: write down the fingerprint of the
7565 chosen exit, not its nickname, because the chosen exit might not
7567 - When parsing foo.exit, if foo is unknown, and we are leaving
7568 circuits unattached, set the chosen_exit field and leave the
7569 address empty. This matters because controllers got confused
7571 - Directory authorities no longer try to download server
7572 descriptors that they know they will reject.
7574 o Features and updates:
7575 - Replace balanced trees with hash tables: this should make stuff
7576 significantly faster.
7577 - Resume using the AES counter-mode implementation that we ship,
7578 rather than OpenSSL's. Ours is significantly faster.
7579 - Many other CPU and memory improvements.
7580 - Add a new config option FastFirstHopPK (on by default) so clients
7581 do a trivial crypto handshake for their first hop, since TLS has
7582 already taken care of confidentiality and authentication.
7583 - Add a new config option TestSocks so people can see if their
7584 applications are using socks4, socks4a, socks5-with-ip, or
7585 socks5-with-hostname. This way they don't have to keep mucking
7586 with tcpdump and wondering if something got cached somewhere.
7587 - Warn when listening on a public address for socks. I suspect a
7588 lot of people are setting themselves up as open socks proxies,
7589 and they have no idea that jerks on the Internet are using them,
7590 since they simply proxy the traffic into the Tor network.
7591 - Add "private:*" as an alias in configuration for policies. Now
7592 you can simplify your exit policy rather than needing to list
7593 every single internal or nonroutable network space.
7594 - Add a new controller event type that allows controllers to get
7595 all server descriptors that were uploaded to a router in its role
7596 as authoritative dirserver.
7597 - Start shipping socks-extensions.txt, tor-doc-unix.html,
7598 tor-doc-server.html, and stylesheet.css in the tarball.
7599 - Stop shipping tor-doc.html in the tarball.
7602 Changes in version 0.1.1.9-alpha - 2005-11-15
7603 o Usability improvements:
7604 - Start calling it FooListenAddress rather than FooBindAddress,
7605 since few of our users know what it means to bind an address
7607 - Reduce clutter in server logs. We're going to try to make
7608 them actually usable now. New config option ProtocolWarnings that
7609 lets you hear about how _other Tors_ are breaking the protocol. Off
7611 - Divide log messages into logging domains. Once we put some sort
7612 of interface on this, it will let people looking at more verbose
7613 log levels specify the topics they want to hear more about.
7614 - Make directory servers return better http 404 error messages
7615 instead of a generic "Servers unavailable".
7616 - Check for even more Windows version flags when writing the platform
7617 string in server descriptors, and note any we don't recognize.
7618 - Clean up more of the OpenSSL memory when exiting, so we can detect
7619 memory leaks better.
7620 - Make directory authorities be non-versioning, non-naming by
7621 default. Now we can add new directory servers without requiring
7622 their operators to pay close attention.
7623 - When logging via syslog, include the pid whenever we provide
7624 a log entry. Suggested by Todd Fries.
7626 o Performance improvements:
7627 - Directory servers now silently throw away new descriptors that
7628 haven't changed much if the timestamps are similar. We do this to
7629 tolerate older Tor servers that upload a new descriptor every 15
7630 minutes. (It seemed like a good idea at the time.)
7631 - Inline bottleneck smartlist functions; use fast versions by default.
7632 - Add a "Map from digest to void*" abstraction digestmap_t so we
7633 can do less hex encoding/decoding. Use it in router_get_by_digest()
7634 to resolve a performance bottleneck.
7635 - Allow tor_gzip_uncompress to extract as much as possible from
7636 truncated compressed data. Try to extract as many
7637 descriptors as possible from truncated http responses (when
7638 DIR_PURPOSE_FETCH_ROUTERDESC).
7639 - Make circ->onionskin a pointer, not a static array. moria2 was using
7640 125000 circuit_t's after it had been up for a few weeks, which
7641 translates to 20+ megs of wasted space.
7642 - The private half of our EDH handshake keys are now chosen out
7643 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
7645 o Security improvements:
7646 - Start making directory caches retain old routerinfos, so soon
7647 clients can start asking by digest of descriptor rather than by
7648 fingerprint of server.
7649 - Add half our entropy from RAND_poll in OpenSSL. This knows how
7650 to use egd (if present), openbsd weirdness (if present), vms/os2
7651 weirdness (if we ever port there), and more in the future.
7653 o Bugfixes on 0.1.0.x:
7654 - Do round-robin writes of at most 16 kB per write. This might be
7655 more fair on loaded Tor servers, and it might resolve our Windows
7656 crash bug. It might also slow things down.
7657 - Our TLS handshakes were generating a single public/private
7658 keypair for the TLS context, rather than making a new one for
7659 each new connections. Oops. (But we were still rotating them
7660 periodically, so it's not so bad.)
7661 - When we were cannibalizing a circuit with a particular exit
7662 node in mind, we weren't checking to see if that exit node was
7663 already present earlier in the circuit. Oops.
7664 - When a Tor server's IP changes (e.g. from a dyndns address),
7665 upload a new descriptor so clients will learn too.
7666 - Really busy servers were keeping enough circuits open on stable
7667 connections that they were wrapping around the circuit_id
7668 space. (It's only two bytes.) This exposed a bug where we would
7669 feel free to reuse a circuit_id even if it still exists but has
7670 been marked for close. Try to fix this bug. Some bug remains.
7671 - If we would close a stream early (e.g. it asks for a .exit that
7672 we know would refuse it) but the LeaveStreamsUnattached config
7673 option is set by the controller, then don't close it.
7675 o Bugfixes on 0.1.1.8-alpha:
7676 - Fix a big pile of memory leaks, some of them serious.
7677 - Do not try to download a routerdesc if we would immediately reject
7679 - Resume inserting a newline between all router descriptors when
7680 generating (old style) signed directories, since our spec says
7682 - When providing content-type application/octet-stream for
7683 server descriptors using .z, we were leaving out the
7684 content-encoding header. Oops. (Everything tolerated this just
7685 fine, but that doesn't mean we need to be part of the problem.)
7686 - Fix a potential seg fault in getconf and getinfo using version 1
7687 of the controller protocol.
7688 - Avoid crash: do not check whether DirPort is reachable when we
7689 are suppressing it because of hibernation.
7690 - Make --hash-password not crash on exit.
7693 Changes in version 0.1.1.8-alpha - 2005-10-07
7694 o New features (major):
7695 - Clients don't download or use the directory anymore. Now they
7696 download and use network-statuses from the trusted dirservers,
7697 and fetch individual server descriptors as needed from mirrors.
7698 See dir-spec.txt for all the gory details.
7699 - Be more conservative about whether to advertise our DirPort.
7700 The main change is to not advertise if we're running at capacity
7701 and either a) we could hibernate or b) our capacity is low and
7702 we're using a default DirPort.
7703 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
7705 o New features (minor):
7706 - Try to be smart about when to retry network-status and
7707 server-descriptor fetches. Still needs some tuning.
7708 - Stop parsing, storing, or using running-routers output (but
7709 mirrors still cache and serve it).
7710 - Consider a threshold of versioning dirservers (dirservers who have
7711 an opinion about which Tor versions are still recommended) before
7712 deciding whether to warn the user that he's obsolete.
7713 - Dirservers can now reject/invalidate by key and IP, with the
7714 config options "AuthDirInvalid" and "AuthDirReject". This is
7715 useful since currently we automatically list servers as running
7716 and usable even if we know they're jerks.
7717 - Provide dire warnings to any users who set DirServer; move it out
7718 of torrc.sample and into torrc.complete.
7719 - Add MyFamily to torrc.sample in the server section.
7720 - Add nicknames to the DirServer line, so we can refer to them
7721 without requiring all our users to memorize their IP addresses.
7722 - When we get an EOF or a timeout on a directory connection, note
7723 how many bytes of serverdesc we are dropping. This will help
7724 us determine whether it is smart to parse incomplete serverdesc
7726 - Add a new function to "change pseudonyms" -- that is, to stop
7727 using any currently-dirty circuits for new streams, so we don't
7728 link new actions to old actions. Currently it's only called on
7729 HUP (or SIGNAL RELOAD).
7730 - On sighup, if UseHelperNodes changed to 1, use new circuits.
7731 - Start using RAND_bytes rather than RAND_pseudo_bytes from
7732 OpenSSL. Also, reseed our entropy every hour, not just at
7733 startup. And entropy in 512-bit chunks, not 160-bit chunks.
7735 o Fixes on 0.1.1.7-alpha:
7736 - Nobody ever implemented EVENT_ADDRMAP for control protocol
7737 version 0, so don't let version 0 controllers ask for it.
7738 - If you requested something with too many newlines via the
7739 v1 controller protocol, you could crash tor.
7740 - Fix a number of memory leaks, including some pretty serious ones.
7741 - Re-enable DirPort testing again, so Tor servers will be willing
7742 to advertise their DirPort if it's reachable.
7743 - On TLS handshake, only check the other router's nickname against
7744 its expected nickname if is_named is set.
7746 o Fixes forward-ported from 0.1.0.15:
7747 - Don't crash when we don't have any spare file descriptors and we
7748 try to spawn a dns or cpu worker.
7749 - Make the numbers in read-history and write-history into uint64s,
7750 so they don't overflow and publish negatives in the descriptor.
7753 - For the OS X package's modified privoxy config file, comment
7754 out the "logfile" line so we don't log everything passed
7756 - We were whining about using socks4 or socks5-with-local-lookup
7757 even when it's an IP in the "virtual" range we designed exactly
7759 - We were leaking some memory every time the client changes IPs.
7760 - Never call free() on tor_malloc()d memory. This will help us
7761 use dmalloc to detect memory leaks.
7762 - Check for named servers when looking them up by nickname;
7763 warn when we'recalling a non-named server by its nickname;
7764 don't warn twice about the same name.
7765 - Try to list MyFamily elements by key, not by nickname, and warn
7766 if we've not heard of the server.
7767 - Make windows platform detection (uname equivalent) smarter.
7768 - It turns out sparc64 doesn't like unaligned access either.
7771 Changes in version 0.1.0.15 - 2005-09-23
7772 o Bugfixes on 0.1.0.x:
7773 - Reject ports 465 and 587 (spam targets) in default exit policy.
7774 - Don't crash when we don't have any spare file descriptors and we
7775 try to spawn a dns or cpu worker.
7776 - Get rid of IgnoreVersion undocumented config option, and make us
7777 only warn, never exit, when we're running an obsolete version.
7778 - Don't try to print a null string when your server finds itself to
7779 be unreachable and the Address config option is empty.
7780 - Make the numbers in read-history and write-history into uint64s,
7781 so they don't overflow and publish negatives in the descriptor.
7782 - Fix a minor memory leak in smartlist_string_remove().
7783 - We were only allowing ourselves to upload a server descriptor at
7784 most every 20 minutes, even if it changed earlier than that.
7785 - Clean up log entries that pointed to old URLs.
7788 Changes in version 0.1.1.7-alpha - 2005-09-14
7789 o Fixes on 0.1.1.6-alpha:
7790 - Exit servers were crashing when people asked them to make a
7791 connection to an address not in their exit policy.
7792 - Looking up a non-existent stream for a v1 control connection would
7794 - Fix a seg fault if we ask a dirserver for a descriptor by
7795 fingerprint but he doesn't know about him.
7796 - SETCONF was appending items to linelists, not clearing them.
7797 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
7798 out and refuse the setconf if it would fail.
7799 - Downgrade the dirserver log messages when whining about
7803 - Add Peter Palfrader's check-tor script to tor/contrib/
7804 It lets you easily check whether a given server (referenced by
7805 nickname) is reachable by you.
7806 - Numerous changes to move towards client-side v2 directories. Not
7810 - If the user gave tor an odd number of command-line arguments,
7811 we were silently ignoring the last one. Now we complain and fail.
7812 [This wins the oldest-bug prize -- this bug has been present since
7813 November 2002, as released in Tor 0.0.0.]
7814 - Do not use unaligned memory access on alpha, mips, or mipsel.
7815 It *works*, but is very slow, so we treat them as if it doesn't.
7816 - Retry directory requests if we fail to get an answer we like
7817 from a given dirserver (we were retrying before, but only if
7818 we fail to connect).
7819 - When writing the RecommendedVersions line, sort them first.
7820 - When the client asked for a rendezvous port that the hidden
7821 service didn't want to provide, we were sending an IP address
7822 back along with the end cell. Fortunately, it was zero. But stop
7824 - Correct "your server is reachable" log entries to indicate that
7825 it was self-testing that told us so.
7828 Changes in version 0.1.1.6-alpha - 2005-09-09
7829 o Fixes on 0.1.1.5-alpha:
7830 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
7831 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
7832 - Fix bug with tor_memmem finding a match at the end of the string.
7833 - Make unit tests run without segfaulting.
7834 - Resolve some solaris x86 compile warnings.
7835 - Handle duplicate lines in approved-routers files without warning.
7836 - Fix bug where as soon as a server refused any requests due to his
7837 exit policy (e.g. when we ask for localhost and he tells us that's
7838 127.0.0.1 and he won't do it), we decided he wasn't obeying his
7839 exit policy using him for any exits.
7840 - Only do openssl hardware accelerator stuff if openssl version is
7843 o New controller features/fixes:
7844 - Add a "RESETCONF" command so you can set config options like
7845 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
7846 a config option in the torrc with no value, then it clears it
7847 entirely (rather than setting it to its default).
7848 - Add a "GETINFO config-file" to tell us where torrc is.
7849 - Avoid sending blank lines when GETINFO replies should be empty.
7850 - Add a QUIT command for the controller (for using it manually).
7851 - Fix a bug in SAVECONF that was adding default dirservers and
7852 other redundant entries to the torrc file.
7854 o Start on the new directory design:
7855 - Generate, publish, cache, serve new network-status format.
7856 - Publish individual descriptors (by fingerprint, by "all", and by
7858 - Publish client and server recommended versions separately.
7859 - Allow tor_gzip_uncompress() to handle multiple concatenated
7860 compressed strings. Serve compressed groups of router
7861 descriptors. The compression logic here could be more
7863 - Distinguish v1 authorities (all currently trusted directories)
7864 from v2 authorities (all trusted directories).
7865 - Change DirServers config line to note which dirs are v1 authorities.
7866 - Add configuration option "V1AuthoritativeDirectory 1" which
7867 moria1, moria2, and tor26 should set.
7868 - Remove option when getting directory cache to see whether they
7869 support running-routers; they all do now. Replace it with one
7870 to see whether caches support v2 stuff.
7873 - Dirservers now do their own external reachability testing of each
7874 Tor server, and only list them as running if they've been found to
7875 be reachable. We also send back warnings to the server's logs if
7876 it uploads a descriptor that we already believe is unreachable.
7877 - Implement exit enclaves: if we know an IP address for the
7878 destination, and there's a running Tor server at that address
7879 which allows exit to the destination, then extend the circuit to
7880 that exit first. This provides end-to-end encryption and end-to-end
7881 authentication. Also, if the user wants a .exit address or enclave,
7882 use 4 hops rather than 3, and cannibalize a general circ for it
7884 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
7885 controller. Also, rotate dns and cpu workers if the controller
7886 changes options that will affect them; and initialize the dns
7887 worker cache tree whether or not we start out as a server.
7888 - Only upload a new server descriptor when options change, 18
7889 hours have passed, uptime is reset, or bandwidth changes a lot.
7890 - Check [X-]Forwarded-For headers in HTTP requests when generating
7891 log messages. This lets people run dirservers (and caches) behind
7892 Apache but still know which IP addresses are causing warnings.
7894 o Config option changes:
7895 - Replace (Fascist)Firewall* config options with a new
7896 ReachableAddresses option that understands address policies.
7897 For example, "ReachableAddresses *:80,*:443"
7898 - Get rid of IgnoreVersion undocumented config option, and make us
7899 only warn, never exit, when we're running an obsolete version.
7900 - Make MonthlyAccountingStart config option truly obsolete now.
7903 - Reject ports 465 and 587 in the default exit policy, since
7904 people have started using them for spam too.
7905 - It turns out we couldn't bootstrap a network since we added
7906 reachability detection in 0.1.0.1-rc. Good thing the Tor network
7907 has never gone down. Add an AssumeReachable config option to let
7908 servers and dirservers bootstrap. When we're trying to build a
7909 high-uptime or high-bandwidth circuit but there aren't enough
7910 suitable servers, try being less picky rather than simply failing.
7911 - Our logic to decide if the OR we connected to was the right guy
7912 was brittle and maybe open to a mitm for unverified routers.
7913 - We weren't cannibalizing circuits correctly for
7914 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
7915 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
7916 build those from scratch. This should make hidden services faster.
7917 - Predict required circuits better, with an eye toward making hidden
7918 services faster on the service end.
7919 - Retry streams if the exit node sends back a 'misc' failure. This
7920 should result in fewer random failures. Also, after failing
7921 from resolve failed or misc, reset the num failures, so we give
7922 it a fair shake next time we try.
7923 - Clean up the rendezvous warn log msgs, and downgrade some to info.
7924 - Reduce severity on logs about dns worker spawning and culling.
7925 - When we're shutting down and we do something like try to post a
7926 server descriptor or rendezvous descriptor, don't complain that
7927 we seem to be unreachable. Of course we are, we're shutting down.
7928 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
7929 We don't use them yet, but maybe one day our DNS resolver will be
7930 able to discover them.
7931 - Make ContactInfo mandatory for authoritative directory servers.
7932 - Require server descriptors to list IPv4 addresses -- hostnames
7933 are no longer allowed. This also fixes some potential security
7934 problems with people providing hostnames as their address and then
7935 preferentially resolving them to partition users.
7936 - Change log line for unreachability to explicitly suggest /etc/hosts
7937 as the culprit. Also make it clearer what IP address and ports we're
7938 testing for reachability.
7939 - Put quotes around user-supplied strings when logging so users are
7940 more likely to realize if they add bad characters (like quotes)
7942 - Let auth dir servers start without specifying an Address config
7944 - Make unit tests (and other invocations that aren't the real Tor)
7945 run without launching listeners, creating subdirectories, and so on.
7948 Changes in version 0.1.1.5-alpha - 2005-08-08
7949 o Bugfixes included in 0.1.0.14.
7951 o Bugfixes on 0.1.0.x:
7952 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
7953 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
7954 it would silently using ignore the 6668.
7957 Changes in version 0.1.0.14 - 2005-08-08
7958 o Bugfixes on 0.1.0.x:
7959 - Fix the other half of the bug with crypto handshakes
7961 - Fix an assert trigger if you send a 'signal term' via the
7962 controller when it's listening for 'event info' messages.
7965 Changes in version 0.1.1.4-alpha - 2005-08-04
7966 o Bugfixes included in 0.1.0.13.
7969 - Improve tor_gettimeofday() granularity on windows.
7970 - Make clients regenerate their keys when their IP address changes.
7971 - Implement some more GETINFO goodness: expose helper nodes, config
7972 options, getinfo keys.
7975 Changes in version 0.1.0.13 - 2005-08-04
7976 o Bugfixes on 0.1.0.x:
7977 - Fix a critical bug in the security of our crypto handshakes.
7978 - Fix a size_t underflow in smartlist_join_strings2() that made
7979 it do bad things when you hand it an empty smartlist.
7980 - Fix Windows installer to ship Tor license (thanks to Aphex for
7981 pointing out this oversight) and put a link to the doc directory
7983 - Explicitly set no-unaligned-access for sparc: it turns out the
7984 new gcc's let you compile broken code, but that doesn't make it
7988 Changes in version 0.1.1.3-alpha - 2005-07-23
7989 o Bugfixes on 0.1.1.2-alpha:
7990 - Fix a bug in handling the controller's "post descriptor"
7992 - Fix several bugs in handling the controller's "extend circuit"
7994 - Fix a bug in handling the controller's "stream status" event.
7995 - Fix an assert failure if we have a controller listening for
7996 circuit events and we go offline.
7997 - Re-allow hidden service descriptors to publish 0 intro points.
7998 - Fix a crash when generating your hidden service descriptor if
7999 you don't have enough intro points already.
8001 o New features on 0.1.1.2-alpha:
8002 - New controller function "getinfo accounting", to ask how
8003 many bytes we've used in this time period.
8004 - Experimental support for helper nodes: a lot of the risk from
8005 a small static adversary comes because users pick new random
8006 nodes every time they rebuild a circuit. Now users will try to
8007 stick to the same small set of entry nodes if they can. Not
8008 enabled by default yet.
8010 o Bugfixes on 0.1.0.12:
8011 - If you're an auth dir server, always publish your dirport,
8012 even if you haven't yet found yourself to be reachable.
8013 - Fix a size_t underflow in smartlist_join_strings2() that made
8014 it do bad things when you hand it an empty smartlist.
8017 Changes in version 0.1.0.12 - 2005-07-18
8018 o New directory servers:
8019 - tor26 has changed IP address.
8021 o Bugfixes on 0.1.0.x:
8022 - Fix a possible double-free in tor_gzip_uncompress().
8023 - When --disable-threads is set, do not search for or link against
8025 - Don't trigger an assert if an authoritative directory server
8026 claims its dirport is 0.
8027 - Fix bug with removing Tor as an NT service: some people were
8028 getting "The service did not return an error." Thanks to Matt
8032 Changes in version 0.1.1.2-alpha - 2005-07-15
8033 o New directory servers:
8034 - tor26 has changed IP address.
8036 o Bugfixes on 0.1.0.x, crashes/leaks:
8037 - Port the servers-not-obeying-their-exit-policies fix from
8039 - Fix an fd leak in start_daemon().
8040 - On Windows, you can't always reopen a port right after you've
8041 closed it. So change retry_listeners() to only close and re-open
8042 ports that have changed.
8043 - Fix a possible double-free in tor_gzip_uncompress().
8045 o Bugfixes on 0.1.0.x, usability:
8046 - When tor_socketpair() fails in Windows, give a reasonable
8047 Windows-style errno back.
8048 - Let people type "tor --install" as well as "tor -install" when
8050 want to make it an NT service.
8051 - NT service patch from Matt Edman to improve error messages.
8052 - When the controller asks for a config option with an abbreviated
8053 name, give the full name in our response.
8054 - Correct the man page entry on TrackHostExitsExpire.
8055 - Looks like we were never delivering deflated (i.e. compressed)
8056 running-routers lists, even when asked. Oops.
8057 - When --disable-threads is set, do not search for or link against
8060 o Bugfixes on 0.1.1.x:
8061 - Fix a seg fault with autodetecting which controller version is
8065 - New hidden service descriptor format: put a version in it, and
8066 let people specify introduction/rendezvous points that aren't
8067 in "the directory" (which is subjective anyway).
8068 - Allow the DEBUG controller event to work again. Mark certain log
8069 entries as "don't tell this to controllers", so we avoid cycles.
8072 Changes in version 0.1.0.11 - 2005-06-30
8073 o Bugfixes on 0.1.0.x:
8074 - Fix major security bug: servers were disregarding their
8075 exit policies if clients behaved unexpectedly.
8076 - Make OS X init script check for missing argument, so we don't
8077 confuse users who invoke it incorrectly.
8078 - Fix a seg fault in "tor --hash-password foo".
8079 - The MAPADDRESS control command was broken.
8082 Changes in version 0.1.1.1-alpha - 2005-06-29
8084 - Make OS X init script check for missing argument, so we don't
8085 confuse users who invoke it incorrectly.
8086 - Fix a seg fault in "tor --hash-password foo".
8087 - Fix a possible way to DoS dirservers.
8088 - When we complain that your exit policy implicitly allows local or
8089 private address spaces, name them explicitly so operators can
8091 - Make the log message less scary when all the dirservers are
8092 temporarily unreachable.
8093 - We were printing the number of idle dns workers incorrectly when
8097 - Revised controller protocol (version 1) that uses ascii rather
8098 than binary. Add supporting libraries in python and java so you
8099 can use the controller from your applications without caring how
8101 - Spiffy new support for crypto hardware accelerators. Can somebody
8105 Changes in version 0.0.9.10 - 2005-06-16
8106 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
8107 - Refuse relay cells that claim to have a length larger than the
8108 maximum allowed. This prevents a potential attack that could read
8109 arbitrary memory (e.g. keys) from an exit server's process
8113 Changes in version 0.1.0.10 - 2005-06-14
8114 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
8115 libevent before 1.1a.
8118 Changes in version 0.1.0.9-rc - 2005-06-09
8120 - Reset buf->highwater every time buf_shrink() is called, not just on
8121 a successful shrink. This was causing significant memory bloat.
8122 - Fix buffer overflow when checking hashed passwords.
8123 - Security fix: if seeding the RNG on Win32 fails, quit.
8124 - Allow seeding the RNG on Win32 even when you're not running as
8126 - Disable threading on Solaris too. Something is wonky with it,
8127 cpuworkers, and reentrant libs.
8128 - Reenable the part of the code that tries to flush as soon as an
8129 OR outbuf has a full TLS record available. Perhaps this will make
8130 OR outbufs not grow as huge except in rare cases, thus saving lots
8131 of CPU time plus memory.
8132 - Reject malformed .onion addresses rather then passing them on as
8133 normal web requests.
8134 - Adapt patch from Adam Langley: fix possible memory leak in
8135 tor_lookup_hostname().
8136 - Initialize libevent later in the startup process, so the logs are
8137 already established by the time we start logging libevent warns.
8138 - Use correct errno on win32 if libevent fails.
8139 - Check and warn about known-bad/slow libevent versions.
8140 - Pay more attention to the ClientOnly config option.
8141 - Have torctl.in/tor.sh.in check for location of su binary (needed
8143 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
8144 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
8145 HttpProxyAuthenticator
8146 - Stop warning about sigpipes in the logs. We're going to
8147 pretend that getting these occassionally is normal and fine.
8148 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
8150 installer screens; and don't put stuff into StartupItems unless
8151 the user asks you to.
8152 - Require servers that use the default dirservers to have public IP
8153 addresses. We have too many servers that are configured with private
8154 IPs and their admins never notice the log entries complaining that
8155 their descriptors are being rejected.
8156 - Add OSX uninstall instructions. An actual uninstall script will
8160 Changes in version 0.1.0.8-rc - 2005-05-23
8162 - It turns out that kqueue on OS X 10.3.9 was causing kernel
8163 panics. Disable kqueue on all OS X Tors.
8164 - Fix RPM: remove duplicate line accidentally added to the rpm
8166 - Disable threads on openbsd too, since its gethostaddr is not
8168 - Tolerate libevent 0.8 since it still works, even though it's
8170 - Enable building on Red Hat 9.0 again.
8171 - Allow the middle hop of the testing circuit to be running any
8172 version, now that most of them have the bugfix to let them connect
8173 to unknown servers. This will allow reachability testing to work
8174 even when 0.0.9.7-0.0.9.9 become obsolete.
8175 - Handle relay cells with rh.length too large. This prevents
8176 a potential attack that could read arbitrary memory (maybe even
8177 keys) from the exit server's process.
8178 - We screwed up the dirport reachability testing when we don't yet
8179 have a cached version of the directory. Hopefully now fixed.
8180 - Clean up router_load_single_router() (used by the controller),
8181 so it doesn't seg fault on error.
8182 - Fix a minor memory leak when somebody establishes an introduction
8183 point at your Tor server.
8184 - If a socks connection ends because read fails, don't warn that
8185 you're not sending a socks reply back.
8188 - Add HttpProxyAuthenticator config option too, that works like
8189 the HttpsProxyAuthenticator config option.
8190 - Encode hashed controller passwords in hex instead of base64,
8191 to make it easier to write controllers.
8194 Changes in version 0.1.0.7-rc - 2005-05-17
8196 - Fix a bug in the OS X package installer that prevented it from
8197 installing on Tiger.
8198 - Fix a script bug in the OS X package installer that made it
8199 complain during installation.
8200 - Find libevent even if it's hiding in /usr/local/ and your
8201 CFLAGS and LDFLAGS don't tell you to look there.
8202 - Be able to link with libevent as a shared library (the default
8203 after 1.0d), even if it's hiding in /usr/local/lib and even
8204 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
8205 assuming you're running gcc. Otherwise fail and give a useful
8207 - Fix a bug in the RPM packager: set home directory for _tor to
8208 something more reasonable when first installing.
8209 - Free a minor amount of memory that is still reachable on exit.
8212 Changes in version 0.1.0.6-rc - 2005-05-14
8214 - Implement --disable-threads configure option. Disable threads on
8215 netbsd by default, because it appears to have no reentrant resolver
8217 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
8218 release (1.1) detects and disables kqueue if it's broken.
8219 - Append default exit policy before checking for implicit internal
8220 addresses. Now we don't log a bunch of complaints on startup
8221 when using the default exit policy.
8222 - Some people were putting "Address " in their torrc, and they had
8223 a buggy resolver that resolved " " to 0.0.0.0. Oops.
8224 - If DataDir is ~/.tor, and that expands to /.tor, then default to
8225 LOCALSTATEDIR/tor instead.
8226 - Fix fragmented-message bug in TorControl.py.
8227 - Resolve a minor bug which would prevent unreachable dirports
8228 from getting suppressed in the published descriptor.
8229 - When the controller gave us a new descriptor, we weren't resolving
8230 it immediately, so Tor would think its address was 0.0.0.0 until
8231 we fetched a new directory.
8232 - Fix an uppercase/lowercase case error in suppressing a bogus
8233 libevent warning on some Linuxes.
8236 - Begin scrubbing sensitive strings from logs by default. Turn off
8237 the config option SafeLogging if you need to do debugging.
8238 - Switch to a new buffer management algorithm, which tries to avoid
8239 reallocing and copying quite as much. In first tests it looks like
8240 it uses *more* memory on average, but less cpu.
8241 - First cut at support for "create-fast" cells. Clients can use
8242 these when extending to their first hop, since the TLS already
8243 provides forward secrecy and authentication. Not enabled on
8245 - When dirservers refuse a router descriptor, we now log its
8246 contactinfo, platform, and the poster's IP address.
8247 - Call tor_free_all instead of connections_free_all after forking, to
8248 save memory on systems that need to fork.
8249 - Whine at you if you're a server and you don't set your contactinfo.
8250 - Implement --verify-config command-line option to check if your torrc
8251 is valid without actually launching Tor.
8252 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
8253 rather than just rejecting it.
8256 Changes in version 0.1.0.5-rc - 2005-04-27
8258 - Stop trying to print a null pointer if an OR conn fails because
8259 we didn't like its cert.
8261 - Switch our internal buffers implementation to use a ring buffer,
8262 to hopefully improve performance for fast servers a lot.
8263 - Add HttpsProxyAuthenticator support (basic auth only), based
8264 on patch from Adam Langley.
8265 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
8266 the fast servers that have been joining lately.
8267 - Give hidden service accesses extra time on the first attempt,
8268 since 60 seconds is often only barely enough. This might improve
8270 - Improve performance for dirservers: stop re-parsing the whole
8271 directory every time you regenerate it.
8272 - Add more debugging info to help us find the weird dns freebsd
8273 pthreads bug; cleaner debug messages to help track future issues.
8276 Changes in version 0.0.9.9 - 2005-04-23
8277 o Bugfixes on 0.0.9.x:
8278 - If unofficial Tor clients connect and send weird TLS certs, our
8279 Tor server triggers an assert. This release contains a minimal
8280 backport from the broader fix that we put into 0.1.0.4-rc.
8283 Changes in version 0.1.0.4-rc - 2005-04-23
8285 - If unofficial Tor clients connect and send weird TLS certs, our
8286 Tor server triggers an assert. Stop asserting, and start handling
8287 TLS errors better in other situations too.
8288 - When the controller asks us to tell it about all the debug-level
8289 logs, it turns out we were generating debug-level logs while
8290 telling it about them, which turns into a bad loop. Now keep
8291 track of whether you're sending a debug log to the controller,
8292 and don't log when you are.
8293 - Fix the "postdescriptor" feature of the controller interface: on
8294 non-complete success, only say "done" once.
8296 - Clients are now willing to load balance over up to 2mB, not 1mB,
8297 of advertised bandwidth capacity.
8298 - Add a NoPublish config option, so you can be a server (e.g. for
8299 testing running Tor servers in other Tor networks) without
8300 publishing your descriptor to the primary dirservers.
8303 Changes in version 0.1.0.3-rc - 2005-04-08
8304 o Improvements on 0.1.0.2-rc:
8305 - Client now retries when streams end early for 'hibernating' or
8306 'resource limit' reasons, rather than failing them.
8307 - More automated handling for dirserver operators:
8308 - Automatically approve nodes running 0.1.0.2-rc or later,
8309 now that the the reachability detection stuff is working.
8310 - Now we allow two unverified servers with the same nickname
8311 but different keys. But if a nickname is verified, only that
8312 nickname+key are allowed.
8313 - If you're an authdirserver connecting to an address:port,
8314 and it's not the OR you were expecting, forget about that
8315 descriptor. If he *was* the one you were expecting, then forget
8316 about all other descriptors for that address:port.
8317 - Allow servers to publish descriptors from 12 hours in the future.
8318 Corollary: only whine about clock skew from the dirserver if
8319 he's a trusted dirserver (since now even verified servers could
8320 have quite wrong clocks).
8321 - Adjust maximum skew and age for rendezvous descriptors: let skew
8322 be 48 hours rather than 90 minutes.
8323 - Efficiency improvements:
8324 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
8325 it much faster to look up a circuit for each relay cell.
8326 - Remove most calls to assert_all_pending_dns_resolves_ok(),
8327 since they're eating our cpu on exit nodes.
8328 - Stop wasting time doing a case insensitive comparison for every
8329 dns name every time we do any lookup. Canonicalize the names to
8330 lowercase and be done with it.
8331 - Start sending 'truncated' cells back rather than destroy cells,
8332 if the circuit closes in front of you. This means we won't have
8333 to abandon partially built circuits.
8334 - Only warn once per nickname from add_nickname_list_to_smartlist
8335 per failure, so an entrynode or exitnode choice that's down won't
8337 - Put a note in the torrc about abuse potential with the default
8339 - Revise control spec and implementation to allow all log messages to
8340 be sent to controller with their severities intact (suggested by
8341 Matt Edman). Update TorControl to handle new log event types.
8342 - Provide better explanation messages when controller's POSTDESCRIPTOR
8344 - Stop putting nodename in the Platform string in server descriptors.
8345 It doesn't actually help, and it is confusing/upsetting some people.
8347 o Bugfixes on 0.1.0.2-rc:
8348 - We were printing the host mask wrong in exit policies in server
8349 descriptors. This isn't a critical bug though, since we were still
8350 obeying the exit policy internally.
8351 - Fix Tor when compiled with libevent but without pthreads: move
8352 connection_unregister() from _connection_free() to
8354 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
8355 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
8356 when we look through the connection array, we'll find any of the
8357 cpu/dnsworkers. This is no good.
8359 o Bugfixes on 0.0.9.8:
8360 - Fix possible bug on threading platforms (e.g. win32) which was
8361 leaking a file descriptor whenever a cpuworker or dnsworker died.
8362 - When using preferred entry or exit nodes, ignore whether the
8363 circuit wants uptime or capacity. They asked for the nodes, they
8365 - chdir() to your datadirectory at the *end* of the daemonize process,
8366 not the beginning. This was a problem because the first time you
8367 run tor, if your datadir isn't there, and you have runasdaemon set
8368 to 1, it will try to chdir to it before it tries to create it. Oops.
8369 - Handle changed router status correctly when dirserver reloads
8370 fingerprint file. We used to be dropping all unverified descriptors
8371 right then. The bug was hidden because we would immediately
8372 fetch a directory from another dirserver, which would include the
8373 descriptors we just dropped.
8374 - When we're connecting to an OR and he's got a different nickname/key
8375 than we were expecting, only complain loudly if we're an OP or a
8376 dirserver. Complaining loudly to the OR admins just confuses them.
8377 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
8378 artificially capped at 500kB.
8381 Changes in version 0.0.9.8 - 2005-04-07
8382 o Bugfixes on 0.0.9.x:
8383 - We have a bug that I haven't found yet. Sometimes, very rarely,
8384 cpuworkers get stuck in the 'busy' state, even though the cpuworker
8385 thinks of itself as idle. This meant that no new circuits ever got
8386 established. Here's a workaround to kill any cpuworker that's been
8387 busy for more than 100 seconds.
8390 Changes in version 0.1.0.2-rc - 2005-04-01
8391 o Bugfixes on 0.1.0.1-rc:
8392 - Fixes on reachability detection:
8393 - Don't check for reachability while hibernating.
8394 - If ORPort is reachable but DirPort isn't, still publish the
8395 descriptor, but zero out DirPort until it's found reachable.
8396 - When building testing circs for ORPort testing, use only
8397 high-bandwidth nodes, so fewer circuits fail.
8398 - Complain about unreachable ORPort separately from unreachable
8399 DirPort, so the user knows what's going on.
8400 - Make sure we only conclude ORPort reachability if we didn't
8401 initiate the conn. Otherwise we could falsely conclude that
8402 we're reachable just because we connected to the guy earlier
8403 and he used that same pipe to extend to us.
8404 - Authdirservers shouldn't do ORPort reachability detection,
8405 since they're in clique mode, so it will be rare to find a
8406 server not already connected to them.
8407 - When building testing circuits, always pick middle hops running
8408 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
8409 bug. (This is a kludge; it will go away when 0.0.9.x becomes
8411 - When we decide we're reachable, actually publish our descriptor
8413 - Fix bug in redirectstream in the controller.
8414 - Fix the state descriptor strings so logs don't claim edge streams
8415 are in a different state than they actually are.
8416 - Use recent libevent features when possible (this only really affects
8417 win32 and osx right now, because the new libevent with these
8418 features hasn't been released yet). Add code to suppress spurious
8420 - Prevent possible segfault in connection_close_unattached_ap().
8421 - Fix newlines on torrc in win32.
8422 - Improve error msgs when tor-resolve fails.
8424 o Improvements on 0.0.9.x:
8425 - New experimental script tor/contrib/ExerciseServer.py (needs more
8426 work) that uses the controller interface to build circuits and
8427 fetch pages over them. This will help us bootstrap servers that
8428 have lots of capacity but haven't noticed it yet.
8429 - New experimental script tor/contrib/PathDemo.py (needs more work)
8430 that uses the controller interface to let you choose whole paths
8432 "<hostname>.<path,separated by dots>.<length of path>.path"
8433 - When we've connected to an OR and handshaked but didn't like
8434 the result, we were closing the conn without sending destroy
8435 cells back for pending circuits. Now send those destroys.
8438 Changes in version 0.0.9.7 - 2005-04-01
8439 o Bugfixes on 0.0.9.x:
8440 - Fix another race crash bug (thanks to Glenn Fink for reporting).
8441 - Compare identity to identity, not to nickname, when extending to
8442 a router not already in the directory. This was preventing us from
8443 extending to unknown routers. Oops.
8444 - Make sure to create OS X Tor user in <500 range, so we aren't
8445 creating actual system users.
8446 - Note where connection-that-hasn't-sent-end was marked, and fix
8447 a few really loud instances of this harmless bug (it's fixed more
8451 Changes in version 0.1.0.1-rc - 2005-03-28
8453 - Add reachability testing. Your Tor server will automatically try
8454 to see if its ORPort and DirPort are reachable from the outside,
8455 and it won't upload its descriptor until it decides they are.
8456 - Handle unavailable hidden services better. Handle slow or busy
8457 hidden services better.
8458 - Add support for CONNECTing through https proxies, with "HttpsProxy"
8460 - New exit policy: accept most low-numbered ports, rather than
8461 rejecting most low-numbered ports.
8462 - More Tor controller support (still experimental). See
8463 http://tor.eff.org/doc/control-spec.txt for all the new features,
8464 including signals to emulate unix signals from any platform;
8465 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
8466 closestream; closecircuit; etc.
8467 - Make nt services work and start on startup on win32 (based on
8468 patch by Matt Edman).
8469 - Add a new AddressMap config directive to rewrite incoming socks
8470 addresses. This lets you, for example, declare an implicit
8471 required exit node for certain sites.
8472 - Add a new TrackHostExits config directive to trigger addressmaps
8473 for certain incoming socks addresses -- for sites that break when
8474 your exit keeps changing (based on patch by Mike Perry).
8475 - Redo the client-side dns cache so it's just an addressmap too.
8476 - Notice when our IP changes, and reset stats/uptime/reachability.
8477 - When an application is using socks5, give him the whole variety of
8478 potential socks5 responses (connect refused, host unreachable, etc),
8479 rather than just "success" or "failure".
8480 - A more sane version numbering system. See
8481 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
8482 - New contributed script "exitlist": a simple python script to
8483 parse directories and find Tor nodes that exit to listed
8485 - New contributed script "privoxy-tor-toggle" to toggle whether
8486 Privoxy uses Tor. Seems to be configured for Debian by default.
8487 - Report HTTP reasons to client when getting a response from directory
8488 servers -- so you can actually know what went wrong.
8489 - New config option MaxAdvertisedBandwidth which lets you advertise
8490 a low bandwidthrate (to not attract as many circuits) while still
8491 allowing a higher bandwidthrate in reality.
8493 o Robustness/stability fixes:
8494 - Make Tor use Niels Provos's libevent instead of its current
8495 poll-but-sometimes-select mess. This will let us use faster async
8496 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
8498 - pthread support now too. This was forced because when we forked,
8499 we ended up wasting a lot of duplicate ram over time. Also switch
8500 to foo_r versions of some library calls to allow reentry and
8502 - Better handling for heterogeneous / unreliable nodes:
8503 - Annotate circuits w/ whether they aim to contain high uptime nodes
8504 and/or high capacity nodes. When building circuits, choose
8506 - This means that every single node in an intro rend circuit,
8507 not just the last one, will have a minimum uptime.
8508 - New config option LongLivedPorts to indicate application streams
8509 that will want high uptime circuits.
8510 - Servers reset uptime when a dir fetch entirely fails. This
8511 hopefully reflects stability of the server's network connectivity.
8512 - If somebody starts his tor server in Jan 2004 and then fixes his
8513 clock, don't make his published uptime be a year.
8514 - Reset published uptime when you wake up from hibernation.
8515 - Introduce a notion of 'internal' circs, which are chosen without
8516 regard to the exit policy of the last hop. Intro and rendezvous
8517 circs must be internal circs, to avoid leaking information. Resolve
8518 and connect streams can use internal circs if they want.
8519 - New circuit pooling algorithm: make sure to have enough circs around
8520 to satisfy any predicted ports, and also make sure to have 2 internal
8521 circs around if we've required internal circs lately (and with high
8522 uptime if we've seen that lately too).
8523 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
8524 which describes how often we retry making new circuits if current
8525 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
8526 how long we're willing to make use of an already-dirty circuit.
8527 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
8528 circ as necessary, if there are any completed ones lying around
8529 when we try to launch one.
8530 - Make hidden services try to establish a rendezvous for 30 seconds,
8531 rather than for n (where n=3) attempts to build a circuit.
8532 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
8533 "ShutdownWaitLength".
8534 - Try to be more zealous about calling connection_edge_end when
8535 things go bad with edge conns in connection.c.
8536 - Revise tor-spec to add more/better stream end reasons.
8537 - Revise all calls to connection_edge_end to avoid sending "misc",
8538 and to take errno into account where possible.
8541 - Fix a race condition that can trigger an assert, when we have a
8542 pending create cell and an OR connection fails right then.
8543 - Fix several double-mark-for-close bugs, e.g. where we were finding
8544 a conn for a cell even if that conn is already marked for close.
8545 - Make sequence of log messages when starting on win32 with no config
8546 file more reasonable.
8547 - When choosing an exit node for a new non-internal circ, don't take
8548 into account whether it'll be useful for any pending x.onion
8549 addresses -- it won't.
8550 - Turn addr_policy_compare from a tristate to a quadstate; this should
8551 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
8552 for google.com" problem.
8553 - Make "platform" string in descriptor more accurate for Win32 servers,
8554 so it's not just "unknown platform".
8555 - Fix an edge case in parsing config options (thanks weasel).
8556 If they say "--" on the commandline, it's not an option.
8557 - Reject odd-looking addresses at the client (e.g. addresses that
8558 contain a colon), rather than having the server drop them because
8560 - tor-resolve requests were ignoring .exit if there was a working circuit
8561 they could use instead.
8562 - REUSEADDR on normal platforms means you can rebind to the port
8563 right after somebody else has let it go. But REUSEADDR on win32
8564 means to let you bind to the port _even when somebody else
8565 already has it bound_! So, don't do that on Win32.
8566 - Change version parsing logic: a version is "obsolete" if it is not
8567 recommended and (1) there is a newer recommended version in the
8568 same series, or (2) there are no recommended versions in the same
8569 series, but there are some recommended versions in a newer series.
8570 A version is "new" if it is newer than any recommended version in
8572 - Stop most cases of hanging up on a socks connection without sending
8576 - Require BandwidthRate to be at least 20kB/s for servers.
8577 - When a dirserver causes you to give a warn, mention which dirserver
8579 - New config option DirAllowPrivateAddresses for authdirservers.
8580 Now by default they refuse router descriptors that have non-IP or
8581 private-IP addresses.
8582 - Stop publishing socksport in the directory, since it's not
8583 actually meant to be public. For compatibility, publish a 0 there
8585 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
8586 smart" value, that is low for servers and high for clients.
8587 - If our clock jumps forward by 100 seconds or more, assume something
8588 has gone wrong with our network and abandon all not-yet-used circs.
8589 - Warn when exit policy implicitly allows local addresses.
8590 - If we get an incredibly skewed timestamp from a dirserver mirror
8591 that isn't a verified OR, don't warn -- it's probably him that's
8593 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
8594 cookies to disk and doesn't log each web request to disk. (Thanks
8595 to Brett Carrington for pointing this out.)
8596 - When a client asks us for a dir mirror and we don't have one,
8597 launch an attempt to get a fresh one.
8598 - If we're hibernating and we get a SIGINT, exit immediately.
8599 - Add --with-dmalloc ./configure option, to track memory leaks.
8600 - And try to free all memory on closing, so we can detect what
8602 - Cache local dns resolves correctly even when they're .exit
8604 - Give a better warning when some other server advertises an
8605 ORPort that is actually an apache running ssl.
8606 - Add "opt hibernating 1" to server descriptor to make it clearer
8607 whether the server is hibernating.
8610 Changes in version 0.0.9.6 - 2005-03-24
8611 o Bugfixes on 0.0.9.x (crashes and asserts):
8612 - Add new end stream reasons to maintainance branch. Fix bug where
8613 reason (8) could trigger an assert. Prevent bug from recurring.
8614 - Apparently win32 stat wants paths to not end with a slash.
8615 - Fix assert triggers in assert_cpath_layer_ok(), where we were
8616 blowing away the circuit that conn->cpath_layer points to, then
8617 checking to see if the circ is well-formed. Backport check to make
8618 sure we dont use the cpath on a closed connection.
8619 - Prevent circuit_resume_edge_reading_helper() from trying to package
8620 inbufs for marked-for-close streams.
8621 - Don't crash on hup if your options->address has become unresolvable.
8622 - Some systems (like OS X) sometimes accept() a connection and tell
8623 you the remote host is 0.0.0.0:0. If this happens, due to some
8624 other mis-features, we get confused; so refuse the conn for now.
8626 o Bugfixes on 0.0.9.x (other):
8627 - Fix harmless but scary "Unrecognized content encoding" warn message.
8628 - Add new stream error reason: TORPROTOCOL reason means "you are not
8629 speaking a version of Tor I understand; say bye-bye to your stream."
8630 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
8631 into the future, now that we are more tolerant of skew. This
8632 resolves a bug where a Tor server would refuse to cache a directory
8633 because all the directories it gets are too far in the future;
8634 yet the Tor server never logs any complaints about clock skew.
8635 - Mac packaging magic: make man pages useable, and do not overwrite
8636 existing torrc files.
8637 - Make OS X log happily to /var/log/tor/tor.log
8640 Changes in version 0.0.9.5 - 2005-02-22
8641 o Bugfixes on 0.0.9.x:
8642 - Fix an assert race at exit nodes when resolve requests fail.
8643 - Stop picking unverified dir mirrors--it only leads to misery.
8644 - Patch from Matt Edman to make NT services work better. Service
8645 support is still not compiled into the executable by default.
8646 - Patch from Dmitri Bely so the Tor service runs better under
8647 the win32 SYSTEM account.
8648 - Make tor-resolve actually work (?) on Win32.
8649 - Fix a sign bug when getrlimit claims to have 4+ billion
8650 file descriptors available.
8651 - Stop refusing to start when bandwidthburst == bandwidthrate.
8652 - When create cells have been on the onion queue more than five
8653 seconds, just send back a destroy and take them off the list.
8656 Changes in version 0.0.9.4 - 2005-02-03
8657 o Bugfixes on 0.0.9:
8658 - Fix an assert bug that took down most of our servers: when
8659 a server claims to have 1 GB of bandwidthburst, don't
8661 - Don't crash as badly if we have spawned the max allowed number
8662 of dnsworkers, or we're out of file descriptors.
8663 - Block more file-sharing ports in the default exit policy.
8664 - MaxConn is now automatically set to the hard limit of max
8665 file descriptors we're allowed (ulimit -n), minus a few for
8667 - Give a clearer message when servers need to raise their
8668 ulimit -n when they start running out of file descriptors.
8669 - SGI Compatibility patches from Jan Schaumann.
8670 - Tolerate a corrupt cached directory better.
8671 - When a dirserver hasn't approved your server, list which one.
8672 - Go into soft hibernation after 95% of the bandwidth is used,
8673 not 99%. This is especially important for daily hibernators who
8674 have a small accounting max. Hopefully it will result in fewer
8675 cut connections when the hard hibernation starts.
8676 - Load-balance better when using servers that claim more than
8677 800kB/s of capacity.
8678 - Make NT services work (experimental, only used if compiled in).
8681 Changes in version 0.0.9.3 - 2005-01-21
8682 o Bugfixes on 0.0.9:
8683 - Backport the cpu use fixes from main branch, so busy servers won't
8684 need as much processor time.
8685 - Work better when we go offline and then come back, or when we
8686 run Tor at boot before the network is up. We do this by
8687 optimistically trying to fetch a new directory whenever an
8688 application request comes in and we think we're offline -- the
8689 human is hopefully a good measure of when the network is back.
8690 - Backport some minimal hidserv bugfixes: keep rend circuits open as
8691 long as you keep using them; actually publish hidserv descriptors
8692 shortly after they change, rather than waiting 20-40 minutes.
8693 - Enable Mac startup script by default.
8694 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
8695 - When you update AllowUnverifiedNodes or FirewallPorts via the
8696 controller's setconf feature, we were always appending, never
8698 - When you update HiddenServiceDir via setconf, it was screwing up
8699 the order of reading the lines, making it fail.
8700 - Do not rewrite a cached directory back to the cache; otherwise we
8701 will think it is recent and not fetch a newer one on startup.
8702 - Workaround for webservers that lie about Content-Encoding: Tor
8703 now tries to autodetect compressed directories and compression
8704 itself. This lets us Proxypass dir fetches through apache.
8707 Changes in version 0.0.9.2 - 2005-01-04
8708 o Bugfixes on 0.0.9 (crashes and asserts):
8709 - Fix an assert on startup when the disk is full and you're logging
8711 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
8712 style address, then we'd crash.
8713 - Fix an assert trigger when the running-routers string we get from
8714 a dirserver is broken.
8715 - Make worker threads start and run on win32. Now win32 servers
8717 - Bandaid (not actually fix, but now it doesn't crash) an assert
8718 where the dns worker dies mysteriously and the main Tor process
8719 doesn't remember anything about the address it was resolving.
8721 o Bugfixes on 0.0.9 (Win32):
8722 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
8723 name out of the warning/assert messages.
8724 - Fix a superficial "unhandled error on read" bug on win32.
8725 - The win32 installer no longer requires a click-through for our
8726 license, since our Free Software license grants rights but does not
8728 - Win32: When connecting to a dirserver fails, try another one
8729 immediately. (This was already working for non-win32 Tors.)
8730 - Stop trying to parse $HOME on win32 when hunting for default
8732 - Make tor-resolve.c work on win32 by calling network_init().
8734 o Bugfixes on 0.0.9 (other):
8735 - Make 0.0.9.x build on Solaris again.
8736 - Due to a fencepost error, we were blowing away the \n when reporting
8737 confvalue items in the controller. So asking for multiple config
8738 values at once couldn't work.
8739 - When listing circuits that are pending on an opening OR connection,
8740 if we're an OR we were listing circuits that *end* at us as
8741 being pending on every listener, dns/cpu worker, etc. Stop that.
8742 - Dirservers were failing to create 'running-routers' or 'directory'
8743 strings if we had more than some threshold of routers. Fix them so
8744 they can handle any number of routers.
8745 - Fix a superficial "Duplicate mark for close" bug.
8746 - Stop checking for clock skew for OR connections, even for servers.
8747 - Fix a fencepost error that was chopping off the last letter of any
8748 nickname that is the maximum allowed nickname length.
8749 - Update URLs in log messages so they point to the new website.
8750 - Fix a potential problem in mangling server private keys while
8751 writing to disk (not triggered yet, as far as we know).
8752 - Include the licenses for other free software we include in Tor,
8753 now that we're shipping binary distributions more regularly.
8756 Changes in version 0.0.9.1 - 2004-12-15
8757 o Bugfixes on 0.0.9:
8758 - Make hibernation actually work.
8759 - Make HashedControlPassword config option work.
8760 - When we're reporting event circuit status to a controller,
8761 don't use the stream status code.
8764 Changes in version 0.0.9 - 2004-12-12
8766 - Clean up manpage and torrc.sample file.
8767 - Clean up severities and text of log warnings.
8769 - Make servers trigger an assert when they enter hibernation.
8772 Changes in version 0.0.9rc7 - 2004-12-08
8773 o Bugfixes on 0.0.9rc:
8774 - Fix a stack-trashing crash when an exit node begins hibernating.
8775 - Avoid looking at unallocated memory while considering which
8776 ports we need to build circuits to cover.
8777 - Stop a sigpipe: when an 'end' cell races with eof from the app,
8778 we shouldn't hold-open-until-flush if the eof arrived first.
8779 - Fix a bug with init_cookie_authentication() in the controller.
8780 - When recommending new-format log lines, if the upper bound is
8781 LOG_ERR, leave it implicit.
8783 o Bugfixes on 0.0.8.1:
8784 - Fix a whole slew of memory leaks.
8785 - Fix isspace() and friends so they still make Solaris happy
8786 but also so they don't trigger asserts on win32.
8787 - Fix parse_iso_time on platforms without strptime (eg win32).
8788 - win32: tolerate extra "readable" events better.
8789 - win32: when being multithreaded, leave parent fdarray open.
8790 - Make unit tests work on win32.
8793 Changes in version 0.0.9rc6 - 2004-12-06
8794 o Bugfixes on 0.0.9pre:
8795 - Clean up some more integer underflow opportunities (not exploitable
8797 - While hibernating, hup should not regrow our listeners.
8798 - Send an end to the streams we close when we hibernate, rather
8799 than just chopping them off.
8800 - React to eof immediately on non-open edge connections.
8802 o Bugfixes on 0.0.8.1:
8803 - Calculate timeout for waiting for a connected cell from the time
8804 we sent the begin cell, not from the time the stream started. If
8805 it took a long time to establish the circuit, we would time out
8806 right after sending the begin cell.
8807 - Fix router_compare_addr_to_addr_policy: it was not treating a port
8808 of * as always matching, so we were picking reject *:* nodes as
8809 exit nodes too. Oops.
8812 - New circuit building strategy: keep a list of ports that we've
8813 used in the past 6 hours, and always try to have 2 circuits open
8814 or on the way that will handle each such port. Seed us with port
8815 80 so web users won't complain that Tor is "slow to start up".
8816 - Make kill -USR1 dump more useful stats about circuits.
8817 - When warning about retrying or giving up, print the address, so
8818 the user knows which one it's talking about.
8819 - If you haven't used a clean circuit in an hour, throw it away,
8820 just to be on the safe side. (This means after 6 hours a totally
8821 unused Tor client will have no circuits open.)
8824 Changes in version 0.0.9rc5 - 2004-12-01
8825 o Bugfixes on 0.0.8.1:
8826 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
8827 - Let resolve conns retry/expire also, rather than sticking around
8829 - If we are using select, make sure we stay within FD_SETSIZE.
8831 o Bugfixes on 0.0.9pre:
8832 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
8833 but doesn't seem to be currently; thanks to Ilja van Sprundel for
8835 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
8836 instead. Impose minima and maxima for all *Period options; impose
8837 even tighter maxima for fetching if we are a caching dirserver.
8838 Clip rather than rejecting.
8839 - Fetch cached running-routers from servers that serve it (that is,
8840 authdirservers and servers running 0.0.9rc5-cvs or later.)
8843 - Accept *:706 (silc) in default exit policy.
8844 - Implement new versioning format for post 0.1.
8845 - Support "foo.nickname.exit" addresses, to let Alice request the
8846 address "foo" as viewed by exit node "nickname". Based on a patch
8848 - Make tor --version --version dump the cvs Id of every file.
8851 Changes in version 0.0.9rc4 - 2004-11-28
8852 o Bugfixes on 0.0.8.1:
8853 - Make windows sockets actually non-blocking (oops), and handle
8854 win32 socket errors better.
8856 o Bugfixes on 0.0.9rc1:
8857 - Actually catch the -USR2 signal.
8860 Changes in version 0.0.9rc3 - 2004-11-25
8861 o Bugfixes on 0.0.8.1:
8862 - Flush the log file descriptor after we print "Tor opening log file",
8863 so we don't see those messages days later.
8865 o Bugfixes on 0.0.9rc1:
8866 - Make tor-resolve work again.
8867 - Avoid infinite loop in tor-resolve if tor hangs up on it.
8868 - Fix an assert trigger for clients/servers handling resolves.
8871 Changes in version 0.0.9rc2 - 2004-11-24
8872 o Bugfixes on 0.0.9rc1:
8873 - I broke socks5 support while fixing the eof bug.
8874 - Allow unitless bandwidths and intervals; they default to bytes
8876 - New servers don't start out hibernating; they are active until
8877 they run out of bytes, so they have a better estimate of how
8878 long it takes, and so their operators can know they're working.
8881 Changes in version 0.0.9rc1 - 2004-11-23
8882 o Bugfixes on 0.0.8.1:
8883 - Finally fix a bug that's been plaguing us for a year:
8884 With high load, circuit package window was reaching 0. Whenever
8885 we got a circuit-level sendme, we were reading a lot on each
8886 socket, but only writing out a bit. So we would eventually reach
8887 eof. This would be noticed and acted on even when there were still
8888 bytes sitting in the inbuf.
8889 - When poll() is interrupted, we shouldn't believe the revents values.
8891 o Bugfixes on 0.0.9pre6:
8892 - Fix hibernate bug that caused pre6 to be broken.
8893 - Don't keep rephist info for routers that haven't had activity for
8894 24 hours. (This matters now that clients have keys, since we track
8896 - Never call close_temp_logs while validating log options.
8897 - Fix backslash-escaping on tor.sh.in and torctl.in.
8900 - Implement weekly/monthly/daily accounting: now you specify your
8901 hibernation properties by
8902 AccountingMax N bytes|KB|MB|GB|TB
8903 AccountingStart day|week|month [day] HH:MM
8904 Defaults to "month 1 0:00".
8905 - Let bandwidth and interval config options be specified as 5 bytes,
8906 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
8907 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
8908 get back to normal.)
8909 - If your requested entry or exit node has advertised bandwidth 0,
8911 - Be more greedy about filling up relay cells -- we try reading again
8912 once we've processed the stuff we read, in case enough has arrived
8913 to fill the last cell completely.
8914 - Apply NT service patch from Osamu Fujino. Still needs more work.
8917 Changes in version 0.0.9pre6 - 2004-11-15
8918 o Bugfixes on 0.0.8.1:
8919 - Fix assert failure on malformed socks4a requests.
8920 - Use identity comparison, not nickname comparison, to choose which
8921 half of circuit-ID-space each side gets to use. This is needed
8922 because sometimes we think of a router as a nickname, and sometimes
8923 as a hex ID, and we can't predict what the other side will do.
8924 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
8925 write() call will fail and we handle it there.
8926 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
8927 and smartlist_len, which are two major profiling offenders.
8929 o Bugfixes on 0.0.9pre5:
8930 - Fix a bug in read_all that was corrupting config files on windows.
8931 - When we're raising the max number of open file descriptors to
8932 'unlimited', don't log that we just raised it to '-1'.
8933 - Include event code with events, as required by control-spec.txt.
8934 - Don't give a fingerprint when clients do --list-fingerprint:
8935 it's misleading, because it will never be the same again.
8936 - Stop using strlcpy in tor_strndup, since it was slowing us
8938 - Remove warn on startup about missing cached-directory file.
8939 - Make kill -USR1 work again.
8940 - Hibernate if we start tor during the "wait for wakeup-time" phase
8941 of an accounting interval. Log our hibernation plans better.
8942 - Authoritative dirservers now also cache their directory, so they
8943 have it on start-up.
8946 - Fetch running-routers; cache running-routers; compress
8947 running-routers; serve compressed running-routers.z
8948 - Add NSI installer script contributed by J Doe.
8949 - Commit VC6 and VC7 workspace/project files.
8950 - Commit a tor.spec for making RPM files, with help from jbash.
8951 - Add contrib/torctl.in contributed by Glenn Fink.
8952 - Implement the control-spec's SAVECONF command, to write your
8953 configuration to torrc.
8954 - Get cookie authentication for the controller closer to working.
8955 - Include control-spec.txt in the tarball.
8956 - When set_conf changes our server descriptor, upload a new copy.
8957 But don't upload it too often if there are frequent changes.
8958 - Document authentication config in man page, and document signals
8960 - Clean up confusing parts of man page and torrc.sample.
8961 - Make expand_filename handle ~ and ~username.
8962 - Use autoconf to enable largefile support where necessary. Use
8963 ftello where available, since ftell can fail at 2GB.
8964 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
8965 log more informatively.
8966 - Give a slightly more useful output for "tor -h".
8967 - Refuse application socks connections to port 0.
8968 - Check clock skew for verified servers, but allow unverified
8969 servers and clients to have any clock skew.
8970 - Break DirFetchPostPeriod into:
8971 - DirFetchPeriod for fetching full directory,
8972 - StatusFetchPeriod for fetching running-routers,
8973 - DirPostPeriod for posting server descriptor,
8974 - RendPostPeriod for posting hidden service descriptors.
8975 - Make sure the hidden service descriptors are at a random offset
8976 from each other, to hinder linkability.
8979 Changes in version 0.0.9pre5 - 2004-11-09
8980 o Bugfixes on 0.0.9pre4:
8981 - Fix a seg fault in unit tests (doesn't affect main program).
8982 - Fix an assert bug where a hidden service provider would fail if
8983 the first hop of his rendezvous circuit was down.
8984 - Hidden service operators now correctly handle version 1 style
8985 INTRODUCE1 cells (nobody generates them still, so not a critical
8987 - If do_hup fails, actually notice.
8988 - Handle more errnos from accept() without closing the listener.
8989 Some OpenBSD machines were closing their listeners because
8990 they ran out of file descriptors.
8991 - Send resolve cells to exit routers that are running a new
8992 enough version of the resolve code to work right.
8993 - Better handling of winsock includes on non-MSV win32 compilers.
8994 - Some people had wrapped their tor client/server in a script
8995 that would restart it whenever it died. This did not play well
8996 with our "shut down if your version is obsolete" code. Now people
8997 don't fetch a new directory if their local cached version is
8999 - Make our autogen.sh work on ksh as well as bash.
9002 - Hibernation: New config option "AccountingMaxKB" lets you
9003 set how many KBytes per month you want to allow your server to
9004 consume. Rather than spreading those bytes out evenly over the
9005 month, we instead hibernate for some of the month and pop up
9006 at a deterministic time, work until the bytes are consumed, then
9007 hibernate again. Config option "MonthlyAccountingStart" lets you
9008 specify which day of the month your billing cycle starts on.
9009 - Control interface: a separate program can now talk to your
9010 client/server over a socket, and get/set config options, receive
9011 notifications of circuits and streams starting/finishing/dying,
9012 bandwidth used, etc. The next step is to get some GUIs working.
9013 Let us know if you want to help out. See doc/control-spec.txt .
9014 - Ship a contrib/tor-control.py as an example script to interact
9015 with the control port.
9016 - "tor --hash-password zzyxz" will output a salted password for
9017 use in authenticating to the control interface.
9018 - New log format in config:
9019 "Log minsev[-maxsev] stdout|stderr|syslog" or
9020 "Log minsev[-maxsev] file /var/foo"
9023 - DirPolicy config option, to let people reject incoming addresses
9024 from their dirserver.
9025 - "tor --list-fingerprint" will list your identity key fingerprint
9027 - Add "pass" target for RedirectExit, to make it easier to break
9028 out of a sequence of RedirectExit rules.
9029 - Clients now generate a TLS cert too, in preparation for having
9030 them act more like real nodes.
9031 - Ship src/win32/ in the tarball, so people can use it to build.
9032 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
9034 - New "router-status" line in directory, to better bind each verified
9035 nickname to its identity key.
9036 - Deprecate unofficial config option abbreviations, and abbreviations
9037 not on the command line.
9038 - Add a pure-C tor-resolve implementation.
9039 - Use getrlimit and friends to ensure we can reach MaxConn (currently
9040 1024) file descriptors.
9042 o Code security improvements, inspired by Ilja:
9043 - Replace sprintf with snprintf. (I think they were all safe, but
9045 - Replace strcpy/strncpy with strlcpy in more places.
9046 - Avoid strcat; use snprintf or strlcat instead.
9047 - snprintf wrapper with consistent (though not C99) overflow behavior.
9050 Changes in version 0.0.9pre4 - 2004-10-17
9051 o Bugfixes on 0.0.9pre3:
9052 - If the server doesn't specify an exit policy, use the real default
9053 exit policy, not reject *:*.
9054 - Ignore fascistfirewall when uploading/downloading hidden service
9055 descriptors, since we go through Tor for those; and when using
9056 an HttpProxy, since we assume it can reach them all.
9057 - When looking for an authoritative dirserver, use only the ones
9058 configured at boot. Don't bother looking in the directory.
9059 - The rest of the fix for get_default_conf_file() on older win32.
9060 - Make 'Routerfile' config option obsolete.
9063 - New 'MyFamily nick1,...' config option for a server to
9064 specify other servers that shouldn't be used in the same circuit
9065 with it. Only believed if nick1 also specifies us.
9066 - New 'NodeFamily nick1,nick2,...' config option for a client to
9067 specify nodes that it doesn't want to use in the same circuit.
9068 - New 'Redirectexit pattern address:port' config option for a
9069 server to redirect exit connections, e.g. to a local squid.
9072 Changes in version 0.0.9pre3 - 2004-10-13
9073 o Bugfixes on 0.0.8.1:
9074 - Better torrc example lines for dirbindaddress and orbindaddress.
9075 - Improved bounds checking on parsed ints (e.g. config options and
9076 the ones we find in directories.)
9077 - Better handling of size_t vs int, so we're more robust on 64
9079 - Fix the rest of the bug where a newly started OR would appear
9080 as unverified even after we've added his fingerprint and hupped
9082 - Fix a bug from 0.0.7: when read() failed on a stream, we would
9083 close it without sending back an end. So 'connection refused'
9084 would simply be ignored and the user would get no response.
9086 o Bugfixes on 0.0.9pre2:
9087 - Serving the cached-on-disk directory to people is bad. We now
9088 provide no directory until we've fetched a fresh one.
9089 - Workaround for bug on windows where cached-directories get crlf
9091 - Make get_default_conf_file() work on older windows too.
9092 - If we write a *:* exit policy line in the descriptor, don't write
9093 any more exit policy lines.
9096 - Use only 0.0.9pre1 and later servers for resolve cells.
9097 - Make the dirservers file obsolete.
9098 - Include a dir-signing-key token in directories to tell the
9099 parsing entity which key is being used to sign.
9100 - Remove the built-in bulky default dirservers string.
9101 - New config option "Dirserver %s:%d [fingerprint]", which can be
9102 repeated as many times as needed. If no dirservers specified,
9103 default to moria1,moria2,tor26.
9104 - Make moria2 advertise a dirport of 80, so people behind firewalls
9105 will be able to get a directory.
9106 - Http proxy support
9107 - Dirservers translate requests for http://%s:%d/x to /x
9108 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
9109 be routed through this host.
9110 - Clients ask for /tor/x rather than /x for new enough dirservers.
9111 This way we can one day coexist peacefully with apache.
9112 - Clients specify a "Host: %s%d" http header, to be compatible
9113 with more proxies, and so running squid on an exit node can work.
9116 Changes in version 0.0.8.1 - 2004-10-13
9118 - Fix a seg fault that can be triggered remotely for Tor
9119 clients/servers with an open dirport.
9120 - Fix a rare assert trigger, where routerinfos for entries in
9121 our cpath would expire while we're building the path.
9122 - Fix a bug in OutboundBindAddress so it (hopefully) works.
9123 - Fix a rare seg fault for people running hidden services on
9124 intermittent connections.
9125 - Fix a bug in parsing opt keywords with objects.
9126 - Fix a stale pointer assert bug when a stream detaches and
9128 - Fix a string format vulnerability (probably not exploitable)
9129 in reporting stats locally.
9130 - Fix an assert trigger: sometimes launching circuits can fail
9131 immediately, e.g. because too many circuits have failed recently.
9132 - Fix a compile warning on 64 bit platforms.
9135 Changes in version 0.0.9pre2 - 2004-10-03
9137 - Make fetching a cached directory work for 64-bit platforms too.
9138 - Make zlib.h a required header, not an optional header.
9141 Changes in version 0.0.9pre1 - 2004-10-01
9143 - Stop using separate defaults for no-config-file and
9144 empty-config-file. Now you have to explicitly turn off SocksPort,
9145 if you don't want it open.
9146 - Fix a bug in OutboundBindAddress so it (hopefully) works.
9147 - Improve man page to mention more of the 0.0.8 features.
9148 - Fix a rare seg fault for people running hidden services on
9149 intermittent connections.
9150 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
9152 - Fix more dns related bugs: send back resolve_failed and end cells
9153 more reliably when the resolve fails, rather than closing the
9154 circuit and then trying to send the cell. Also attach dummy resolve
9155 connections to a circuit *before* calling dns_resolve(), to fix
9156 a bug where cached answers would never be sent in RESOLVED cells.
9157 - When we run out of disk space, or other log writing error, don't
9158 crash. Just stop logging to that log and continue.
9159 - We were starting to daemonize before we opened our logs, so if
9160 there were any problems opening logs, we would complain to stderr,
9161 which wouldn't work, and then mysteriously exit.
9162 - Fix a rare bug where sometimes a verified OR would connect to us
9163 before he'd uploaded his descriptor, which would cause us to
9164 assign conn->nickname as though he's unverified. Now we look through
9165 the fingerprint list to see if he's there.
9166 - Fix a rare assert trigger, where routerinfos for entries in
9167 our cpath would expire while we're building the path.
9170 - Clients can ask dirservers for /dir.z to get a compressed version
9171 of the directory. Only works for servers running 0.0.9, of course.
9172 - Make clients cache directories and use them to seed their router
9173 lists at startup. This means clients have a datadir again.
9174 - Configuration infrastructure support for warning on obsolete
9176 - Respond to content-encoding headers by trying to uncompress as
9178 - Reply with a deflated directory when a client asks for "dir.z".
9179 We could use allow-encodings instead, but allow-encodings isn't
9180 specified in HTTP 1.0.
9181 - Raise the max dns workers from 50 to 100.
9182 - Discourage people from setting their dirfetchpostperiod more often
9183 than once per minute.
9184 - Protect dirservers from overzealous descriptor uploading -- wait
9185 10 seconds after directory gets dirty, before regenerating.
9188 Changes in version 0.0.8 - 2004-08-25
9189 o Port it to SunOS 5.9 / Athena
9192 Changes in version 0.0.8rc2 - 2004-08-20
9193 o Make it compile on cygwin again.
9194 o When picking unverified routers, skip those with low uptime and/or
9195 low bandwidth, depending on what properties you care about.
9198 Changes in version 0.0.8rc1 - 2004-08-18
9199 o Changes from 0.0.7.3:
9201 - Fix assert triggers: if the other side returns an address 0.0.0.0,
9202 don't put it into the client dns cache.
9203 - If a begin failed due to exit policy, but we believe the IP address
9204 should have been allowed, switch that router to exitpolicy reject *:*
9205 until we get our next directory.
9207 - Clients choose nodes proportional to advertised bandwidth.
9208 - Avoid using nodes with low uptime as introduction points.
9209 - Handle servers with dynamic IP addresses: don't replace
9210 options->Address with the resolved one at startup, and
9211 detect our address right before we make a routerinfo each time.
9212 - 'FascistFirewall' option to pick dirservers and ORs on specific
9213 ports; plus 'FirewallPorts' config option to tell FascistFirewall
9214 which ports are open. (Defaults to 80,443)
9215 - Be more aggressive about trying to make circuits when the network
9216 has changed (e.g. when you unsuspend your laptop).
9217 - Check for time skew on http headers; report date in response to
9219 - If the entrynode config line has only one node, don't pick it as
9221 - Add strict{entry|exit}nodes config options. If set to 1, then
9222 we refuse to build circuits that don't include the specified entry
9224 - OutboundBindAddress config option, to bind to a specific
9225 IP address for outgoing connect()s.
9226 - End truncated log entries (e.g. directories) with "[truncated]".
9228 o Patches to 0.0.8preX:
9230 - Patches to compile and run on win32 again (maybe)?
9231 - Fix crash when looking for ~/.torrc with no $HOME set.
9232 - Fix a race bug in the unit tests.
9233 - Handle verified/unverified name collisions better when new
9234 routerinfo's arrive in a directory.
9235 - Sometimes routers were getting entered into the stats before
9236 we'd assigned their identity_digest. Oops.
9237 - Only pick and establish intro points after we've gotten a
9240 - AllowUnverifiedNodes config option to let circuits choose no-name
9241 routers in entry,middle,exit,introduction,rendezvous positions.
9242 Allow middle and rendezvous positions by default.
9243 - Add a man page for tor-resolve.
9246 Changes in version 0.0.7.3 - 2004-08-12
9247 o Stop dnsworkers from triggering an assert failure when you
9248 ask them to resolve the host "".
9251 Changes in version 0.0.8pre3 - 2004-08-09
9252 o Changes from 0.0.7.2:
9253 - Allow multiple ORs with same nickname in routerlist -- now when
9254 people give us one identity key for a nickname, then later
9255 another, we don't constantly complain until the first expires.
9256 - Remember used bandwidth (both in and out), and publish 15-minute
9257 snapshots for the past day into our descriptor.
9258 - You can now fetch $DIRURL/running-routers to get just the
9259 running-routers line, not the whole descriptor list. (But
9260 clients don't use this yet.)
9261 - When people mistakenly use Tor as an http proxy, point them
9262 at the tor-doc.html rather than the INSTALL.
9263 - Remove our mostly unused -- and broken -- hex_encode()
9264 function. Use base16_encode() instead. (Thanks to Timo Lindfors
9265 for pointing out this bug.)
9266 - Rotate onion keys every 12 hours, not every 2 hours, so we have
9267 fewer problems with people using the wrong key.
9268 - Change the default exit policy to reject the default edonkey,
9269 kazaa, gnutella ports.
9270 - Add replace_file() to util.[ch] to handle win32's rename().
9272 o Changes from 0.0.8preX:
9273 - Fix two bugs in saving onion keys to disk when rotating, so
9274 hopefully we'll get fewer people using old onion keys.
9275 - Fix an assert error that was making SocksPolicy not work.
9276 - Be willing to expire routers that have an open dirport -- it's
9277 just the authoritative dirservers we want to not forget.
9278 - Reject tor-resolve requests for .onion addresses early, so we
9279 don't build a whole rendezvous circuit and then fail.
9280 - When you're warning a server that he's unverified, don't cry
9282 - Fix a race condition: don't try to extend onto a connection
9283 that's still handshaking.
9284 - For servers in clique mode, require the conn to be open before
9285 you'll choose it for your path.
9286 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
9287 end relay cell, etc.
9288 - Measure bandwidth capacity over the last 24 hours, not just 12
9289 - Bugfix: authoritative dirservers were making and signing a new
9290 directory for each client, rather than reusing the cached one.
9293 Changes in version 0.0.8pre2 - 2004-08-04
9294 o Changes from 0.0.7.2:
9296 - Check directory signature _before_ you decide whether you're
9297 you're running an obsolete version and should exit.
9298 - Check directory signature _before_ you parse the running-routers
9299 list to decide who's running or verified.
9300 - Bugfixes and features:
9301 - Check return value of fclose while writing to disk, so we don't
9302 end up with broken files when servers run out of disk space.
9303 - Log a warning if the user uses an unsafe socks variant, so people
9304 are more likely to learn about privoxy or socat.
9305 - Dirservers now include RFC1123-style dates in the HTTP headers,
9306 which one day we will use to better detect clock skew.
9308 o Changes from 0.0.8pre1:
9309 - Make it compile without warnings again on win32.
9310 - Log a warning if you're running an unverified server, to let you
9311 know you might want to get it verified.
9312 - Only pick a default nickname if you plan to be a server.
9315 Changes in version 0.0.8pre1 - 2004-07-23
9317 - Made our unit tests compile again on OpenBSD 3.5, and tor
9318 itself compile again on OpenBSD on a sparc64.
9319 - We were neglecting milliseconds when logging on win32, so
9320 everything appeared to happen at the beginning of each second.
9323 - 'Extend' relay cell payloads now include the digest of the
9324 intended next hop's identity key. Now we can verify that we're
9325 extending to the right router, and also extend to routers we
9326 hadn't heard of before.
9329 - Tor nodes can now act as relays (with an advertised ORPort)
9330 without being manually verified by the dirserver operators.
9331 - Uploaded descriptors of unverified routers are now accepted
9332 by the dirservers, and included in the directory.
9333 - Verified routers are listed by nickname in the running-routers
9334 list; unverified routers are listed as "$<fingerprint>".
9335 - We now use hash-of-identity-key in most places rather than
9336 nickname or addr:port, for improved security/flexibility.
9337 - To avoid Sybil attacks, paths still use only verified servers.
9338 But now we have a chance to play around with hybrid approaches.
9339 - Nodes track bandwidth usage to estimate capacity (not used yet).
9340 - ClientOnly option for nodes that never want to become servers.
9341 - Directory caching.
9342 - "AuthoritativeDir 1" option for the official dirservers.
9343 - Now other nodes (clients and servers) will cache the latest
9344 directory they've pulled down.
9345 - They can enable their DirPort to serve it to others.
9346 - Clients will pull down a directory from any node with an open
9347 DirPort, and check the signature/timestamp correctly.
9348 - Authoritative dirservers now fetch directories from other
9349 authdirservers, to stay better synced.
9350 - Running-routers list tells who's down also, along with noting
9351 if they're verified (listed by nickname) or unverified (listed
9353 - Allow dirservers to serve running-router list separately.
9354 This isn't used yet.
9355 - ORs connect-on-demand to other ORs
9356 - If you get an extend cell to an OR you're not connected to,
9357 connect, handshake, and forward the create cell.
9358 - The authoritative dirservers stay connected to everybody,
9359 and everybody stays connected to 0.0.7 servers, but otherwise
9360 clients/servers expire unused connections after 5 minutes.
9361 - When servers get a sigint, they delay 30 seconds (refusing new
9362 connections) then exit. A second sigint causes immediate exit.
9363 - File and name management:
9364 - Look for .torrc if no CONFDIR "torrc" is found.
9365 - If no datadir is defined, then choose, make, and secure ~/.tor
9367 - If torrc not found, exitpolicy reject *:*.
9368 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
9369 - If no nickname is defined, derive default from hostname.
9370 - Rename secret key files, e.g. identity.key -> secret_id_key,
9371 to discourage people from mailing their identity key to tor-ops.
9372 - Refuse to build a circuit before the directory has arrived --
9373 it won't work anyway, since you won't know the right onion keys
9375 - Try other dirservers immediately if the one you try is down. This
9376 should tolerate down dirservers better now.
9377 - Parse tor version numbers so we can do an is-newer-than check
9378 rather than an is-in-the-list check.
9379 - New socks command 'resolve', to let us shim gethostbyname()
9381 - A 'tor_resolve' script to access the socks resolve functionality.
9382 - A new socks-extensions.txt doc file to describe our
9383 interpretation and extensions to the socks protocols.
9384 - Add a ContactInfo option, which gets published in descriptor.
9385 - Publish OR uptime in descriptor (and thus in directory) too.
9386 - Write tor version at the top of each log file
9387 - New docs in the tarball:
9389 - Document that you should proxy your SSL traffic too.
9392 Changes in version 0.0.7.2 - 2004-07-07
9393 o A better fix for the 0.0.0.0 problem, that will hopefully
9394 eliminate the remaining related assertion failures.
9397 Changes in version 0.0.7.1 - 2004-07-04
9398 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
9399 since internally we use 0.0.0.0 to signify "not yet resolved".
9402 Changes in version 0.0.7 - 2004-06-07
9403 o Updated the man page to reflect the new features.
9406 Changes in version 0.0.7rc2 - 2004-06-06
9407 o Changes from 0.0.7rc1:
9408 - Make it build on Win32 again.
9409 o Changes from 0.0.6.2:
9410 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
9414 Changes in version 0.0.7rc1 - 2004-06-02
9416 - On sighup, we were adding another log without removing the first
9417 one. So log messages would get duplicated n times for n sighups.
9418 - Several cases of using a connection after we'd freed it. The
9419 problem was that connections that are pending resolve are in both
9420 the pending_resolve tree, and also the circuit's resolving_streams
9421 list. When you want to remove one, you must remove it from both.
9422 - Fix a double-mark-for-close where an end cell arrived for a
9423 resolving stream, and then the resolve failed.
9424 - Check directory signatures based on name of signer, not on whom
9425 we got the directory from. This will let us cache directories more
9428 - Crank up some of our constants to handle more users.
9431 Changes in version 0.0.7pre1 - 2004-06-02
9432 o Fixes for crashes and other obnoxious bugs:
9433 - Fix an epipe bug: sometimes when directory connections failed
9434 to connect, we would give them a chance to flush before closing
9436 - When we detached from a circuit because of resolvefailed, we
9437 would immediately try the same circuit twice more, and then
9438 give up on the resolve thinking we'd tried three different
9440 - Limit the number of intro circuits we'll attempt to build for a
9441 hidden service per 15-minute period.
9442 - Check recommended-software string *early*, before actually parsing
9443 the directory. Thus we can detect an obsolete version and exit,
9444 even if the new directory format doesn't parse.
9445 o Fixes for security bugs:
9446 - Remember which nodes are dirservers when you startup, and if a
9447 random OR enables his dirport, don't automatically assume he's
9448 a trusted dirserver.
9450 - Directory connections were asking the wrong poll socket to
9451 start writing, and not asking themselves to start writing.
9452 - When we detached from a circuit because we sent a begin but
9453 didn't get a connected, we would use it again the first time;
9454 but after that we would correctly switch to a different one.
9455 - Stop warning when the first onion decrypt attempt fails; they
9456 will sometimes legitimately fail now that we rotate keys.
9457 - Override unaligned-access-ok check when $host_cpu is ia64 or
9458 arm. Apparently they allow it but the kernel whines.
9459 - Dirservers try to reconnect periodically too, in case connections
9461 - Fix some memory leaks in directory servers.
9462 - Allow backslash in Win32 filenames.
9463 - Made Tor build complain-free on FreeBSD, hopefully without
9464 breaking other BSD builds. We'll see.
9466 - Doxygen markup on all functions and global variables.
9467 - Make directory functions update routerlist, not replace it. So
9468 now directory disagreements are not so critical a problem.
9469 - Remove the upper limit on number of descriptors in a dirserver's
9470 directory (not that we were anywhere close).
9471 - Allow multiple logfiles at different severity ranges.
9472 - Allow *BindAddress to specify ":port" rather than setting *Port
9473 separately. Allow multiple instances of each BindAddress config
9474 option, so you can bind to multiple interfaces if you want.
9475 - Allow multiple exit policy lines, which are processed in order.
9476 Now we don't need that huge line with all the commas in it.
9477 - Enable accept/reject policies on SOCKS connections, so you can bind
9478 to 0.0.0.0 but still control who can use your OP.
9481 Changes in version 0.0.6.2 - 2004-05-16
9482 o Our integrity-checking digest was checking only the most recent cell,
9483 not the previous cells like we'd thought.
9484 Thanks to Stefan Mark for finding the flaw!
9487 Changes in version 0.0.6.1 - 2004-05-06
9488 o Fix two bugs in our AES counter-mode implementation (this affected
9489 onion-level stream encryption, but not TLS-level). It turns
9490 out we were doing something much more akin to a 16-character
9491 polyalphabetic cipher. Oops.
9492 Thanks to Stefan Mark for finding the flaw!
9493 o Retire moria3 as a directory server, and add tor26 as a directory
9497 Changes in version 0.0.6 - 2004-05-02
9501 Changes in version 0.0.6rc4 - 2004-05-01
9502 o Update the built-in dirservers list to use the new directory format
9503 o Fix a rare seg fault: if a node offering a hidden service attempts
9504 to build a circuit to Alice's rendezvous point and fails before it
9505 reaches the last hop, it retries with a different circuit, but
9507 o Handle windows socket errors correctly.
9510 Changes in version 0.0.6rc3 - 2004-04-28
9511 o Don't expire non-general excess circuits (if we had enough
9512 circuits open, we were expiring rendezvous circuits -- even
9513 when they had a stream attached. oops.)
9514 o Fetch randomness from /dev/urandom better (not via fopen/fread)
9515 o Better debugging for tls errors
9516 o Some versions of openssl have an SSL_pending function that erroneously
9517 returns bytes when there is a non-application record pending.
9518 o Set Content-Type on the directory and hidserv descriptor.
9519 o Remove IVs from cipher code, since AES-ctr has none.
9520 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
9521 o We were using an array of length zero in a few places.
9522 o win32's gethostbyname can't resolve an IP to an IP.
9523 o win32's close can't close a socket.
9526 Changes in version 0.0.6rc2 - 2004-04-26
9527 o Fix a bug where we were closing tls connections intermittently.
9528 It turns out openssl keeps its errors around -- so if an error
9529 happens, and you don't ask about it, and then another openssl
9530 operation happens and succeeds, and you ask if there was an error,
9531 it tells you about the first error. Fun fun.
9532 o Fix a bug that's been lurking since 27 may 03 (!)
9533 When passing back a destroy cell, we would use the wrong circ id.
9534 'Mostly harmless', but still worth fixing.
9535 o Since we don't support truncateds much, don't bother sending them;
9536 just close the circ.
9537 o check for <machine/limits.h> so we build on NetBSD again (I hope).
9538 o don't crash if a conn that sent a begin has suddenly lost its circuit
9539 (this was quite rare).
9542 Changes in version 0.0.6rc1 - 2004-04-25
9543 o We now rotate link (tls context) keys and onion keys.
9544 o CREATE cells now include oaep padding, so you can tell
9545 if you decrypted them correctly.
9546 o Add bandwidthburst to server descriptor.
9547 o Directories now say which dirserver signed them.
9548 o Use a tor_assert macro that logs failed assertions too.
9551 Changes in version 0.0.6pre5 - 2004-04-18
9552 o changes from 0.0.6pre4:
9553 - make tor build on broken freebsd 5.2 installs
9554 - fix a failed assert when you try an intro point, get a nack, and try
9555 a second one and it works.
9556 - when alice uses a port that the hidden service doesn't accept,
9557 it now sends back an end cell (denied by exit policy). otherwise
9558 alice would just have to wait to time out.
9559 - fix another rare bug: when we had tried all the intro
9560 points for a hidden service, we fetched the descriptor
9561 again, but we left our introcirc thinking it had already
9562 sent an intro, so it kept waiting for a response...
9563 - bugfix: when you sleep your hidden-service laptop, as soon
9564 as it wakes up it tries to upload a service descriptor, but
9565 socketpair fails for some reason (localhost not up yet?).
9566 now we simply give up on that upload, and we'll try again later.
9567 i'd still like to find the bug though.
9568 - if an intro circ waiting for an ack dies before getting one, then
9570 - we were reusing stale service descriptors and refetching usable
9574 Changes in version 0.0.6pre4 - 2004-04-14
9575 o changes from 0.0.6pre3:
9576 - when bob fails to connect to the rendezvous point, and his
9577 circ didn't fail because of the rendezvous point itself, then
9578 he retries a couple of times
9579 - we expire introduction and rendezvous circs more thoroughly
9580 (sometimes they were hanging around forever)
9581 - we expire unattached rendezvous streams that have been around
9582 too long (they were sticking around forever).
9583 - fix a measly fencepost error that was crashing everybody with
9587 Changes in version 0.0.6pre3 - 2004-04-14
9588 o changes from 0.0.6pre2:
9589 - make hup work again
9590 - fix some memory leaks for dirservers
9591 - allow more skew in rendezvous descriptor timestamps, to help
9592 handle people like blanu who don't know what time it is
9593 - normal circs are 3 hops, but some rend/intro circs are 4, if
9594 the initiator doesn't get to choose the last hop
9595 - send acks for introductions, so alice can know whether to try
9597 - bob publishes intro points more correctly
9598 o changes from 0.0.5:
9599 - fix an assert trigger that's been plaguing us since the days
9600 of 0.0.2prexx (thanks weasel!)
9601 - retry stream correctly when we fail to connect because of
9602 exit-policy-reject (should try another) or can't-resolve-address
9603 (also should try another, because dns on random internet servers
9605 - when we hup a dirserver and we've *removed* a server from the
9606 approved-routers list, now we remove that server from the
9607 in-memory directories too
9610 Changes in version 0.0.6pre2 - 2004-04-08
9611 o We fixed our base32 implementation. Now it works on all architectures.
9614 Changes in version 0.0.6pre1 - 2004-04-08
9616 - Hidden services and rendezvous points are implemented. Go to
9617 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
9618 hidden services. (This only works via a socks4a proxy such as
9619 Privoxy, and currently it's quite slow.)
9622 Changes in version 0.0.5 - 2004-03-30
9626 Changes in version 0.0.5rc3 - 2004-03-29
9627 o Install torrc as torrc.sample -- we no longer clobber your
9629 o Re-enable recommendedversion checking (we broke it in rc2, oops)
9630 o Add in a 'notice' log level for things the operator should hear
9631 but that aren't warnings
9634 Changes in version 0.0.5rc2 - 2004-03-29
9635 o Hold socks connection open until reply is flushed (if possible)
9636 o Make exit nodes resolve IPs to IPs immediately, rather than asking
9637 the dns farm to do it.
9638 o Fix c99 aliasing warnings in rephist.c
9639 o Don't include server descriptors that are older than 24 hours in the
9641 o Give socks 'reject' replies their whole 15s to attempt to flush,
9642 rather than seeing the 60s timeout and assuming the flush had failed.
9643 o Clean automake droppings from the cvs repository
9646 Changes in version 0.0.5rc1 - 2004-03-28
9647 o Fix mangled-state bug in directory fetching (was causing sigpipes).
9648 o Only build circuits after we've fetched the directory: clients were
9649 using only the directory servers before they'd fetched a directory.
9650 This also means longer startup time; so it goes.
9651 o Fix an assert trigger where an OP would fail to handshake, and we'd
9652 expect it to have a nickname.
9653 o Work around a tsocks bug: do a socks reject when AP connection dies
9654 early, else tsocks goes into an infinite loop.
9657 Changes in version 0.0.4 - 2004-03-26
9658 o When connecting to a dirserver or OR and the network is down,
9662 Changes in version 0.0.3 - 2004-03-26
9663 o Warn and fail if server chose a nickname with illegal characters
9664 o Port to Solaris and Sparc:
9665 - include missing header fcntl.h
9666 - have autoconf find -lsocket -lnsl automatically
9667 - deal with hardware word alignment
9668 - make uname() work (solaris has a different return convention)
9669 - switch from using signal() to sigaction()
9670 o Preliminary work on reputation system:
9671 - Keep statistics on success/fail of connect attempts; they're published
9672 by kill -USR1 currently.
9673 - Add a RunTesting option to try to learn link state by creating test
9674 circuits, even when SocksPort is off.
9675 - Remove unused open circuits when there are too many.
9678 Changes in version 0.0.2 - 2004-03-19
9679 - Include strlcpy and strlcat for safer string ops
9680 - define INADDR_NONE so we compile (but still not run) on solaris
9683 Changes in version 0.0.2pre27 - 2004-03-14
9685 - Allow internal tor networks (we were rejecting internal IPs,
9686 now we allow them if they're set explicitly).
9687 - And fix a few endian issues.
9690 Changes in version 0.0.2pre26 - 2004-03-14
9692 - If a stream times out after 15s without a connected cell, don't
9693 try that circuit again: try a new one.
9694 - Retry streams at most 4 times. Then give up.
9695 - When a dirserver gets a descriptor from an unknown router, it
9696 logs its fingerprint (so the dirserver operator can choose to
9697 accept it even without mail from the server operator).
9698 - Inform unapproved servers when we reject their descriptors.
9699 - Make tor build on Windows again. It works as a client, who knows
9701 - Clearer instructions in the torrc for how to set up a server.
9702 - Be more efficient about reading fd's when our global token bucket
9703 (used for rate limiting) becomes empty.
9705 - Stop asserting that computers always go forward in time. It's
9707 - When we sent a cell (e.g. destroy) and then marked an OR connection
9708 expired, we might close it before finishing a flush if the other
9709 side isn't reading right then.
9710 - Don't allow dirservers to start if they haven't defined
9712 - We were caching transient dns failures. Oops.
9713 - Prevent servers from publishing an internal IP as their address.
9714 - Address a strcat vulnerability in circuit.c
9717 Changes in version 0.0.2pre25 - 2004-03-04
9719 - Put the OR's IP in its router descriptor, not its fqdn. That way
9720 we'll stop being stalled by gethostbyname for nodes with flaky dns,
9723 - If the user typed in an address that didn't resolve, the server
9727 Changes in version 0.0.2pre24 - 2004-03-03
9729 - Fix an assertion failure in dns.c, where we were trying to dequeue
9730 a pending dns resolve even if it wasn't pending
9731 - Fix a spurious socks5 warning about still trying to write after the
9732 connection is finished.
9733 - Hold certain marked_for_close connections open until they're finished
9734 flushing, rather than losing bytes by closing them too early.
9735 - Correctly report the reason for ending a stream
9736 - Remove some duplicate calls to connection_mark_for_close
9737 - Put switch_id and start_daemon earlier in the boot sequence, so it
9738 will actually try to chdir() to options.DataDirectory
9739 - Make 'make test' exit(1) if a test fails; fix some unit tests
9740 - Make tor fail when you use a config option it doesn't know about,
9741 rather than warn and continue.
9742 - Make --version work
9743 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
9746 Changes in version 0.0.2pre23 - 2004-02-29
9748 - Print a statement when the first circ is finished, so the user
9750 - If a relay cell is unrecognized at the end of the circuit,
9751 send back a destroy. (So attacks to mutate cells are more
9753 - New config option 'excludenodes' to avoid certain nodes for circuits.
9754 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
9755 so you can collect coredumps there.
9757 - Fix a bug in tls flushing where sometimes data got wedged and
9758 didn't flush until more data got sent. Hopefully this bug was
9759 a big factor in the random delays we were seeing.
9760 - Make 'connected' cells include the resolved IP, so the client
9761 dns cache actually gets populated.
9762 - Disallow changing from ORPort=0 to ORPort>0 on hup.
9763 - When we time-out on a stream and detach from the circuit, send an
9764 end cell down it first.
9765 - Only warn about an unknown router (in exitnodes, entrynodes,
9766 excludenodes) after we've fetched a directory.
9769 Changes in version 0.0.2pre22 - 2004-02-26
9771 - Servers publish less revealing uname information in descriptors.
9772 - More memory tracking and assertions, to crash more usefully when
9774 - If the default torrc isn't there, just use some default defaults.
9775 Plus provide an internal dirservers file if they don't have one.
9776 - When the user tries to use Tor as an http proxy, give them an http
9777 501 failure explaining that we're a socks proxy.
9778 - Dump a new router.desc on hup, to help confused people who change
9779 their exit policies and then wonder why router.desc doesn't reflect
9781 - Clean up the generic tor.sh init script that we ship with.
9783 - If the exit stream is pending on the resolve, and a destroy arrives,
9784 then the stream wasn't getting removed from the pending list. I
9785 think this was the one causing recent server crashes.
9786 - Use a more robust poll on OSX 10.3, since their poll is flaky.
9787 - When it couldn't resolve any dirservers, it was useless from then on.
9788 Now it reloads the RouterFile (or default dirservers) if it has no
9790 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
9791 many users don't even *have* a /usr/local/sbin/.
9794 Changes in version 0.0.2pre21 - 2004-02-18
9796 - There's a ChangeLog file that actually reflects the changelog.
9797 - There's a 'torify' wrapper script, with an accompanying
9798 tor-tsocks.conf, that simplifies the process of using tsocks for
9799 tor. It even has a man page.
9800 - The tor binary gets installed to sbin rather than bin now.
9801 - Retry streams where the connected cell hasn't arrived in 15 seconds
9802 - Clean up exit policy handling -- get the default out of the torrc,
9803 so we can update it without forcing each server operator to fix
9805 - Allow imaps and pop3s in default exit policy
9807 - Prevent picking middleman nodes as the last node in the circuit
9810 Changes in version 0.0.2pre20 - 2004-01-30
9812 - We now have a deb package, and it's in debian unstable. Go to
9814 - I've split the TotalBandwidth option into BandwidthRate (how many
9815 bytes per second you want to allow, long-term) and
9816 BandwidthBurst (how many bytes you will allow at once before the cap
9817 kicks in). This better token bucket approach lets you, say, set
9818 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
9819 performance while not exceeding your monthly bandwidth quota.
9820 - Push out a tls record's worth of data once you've got it, rather
9821 than waiting until you've read everything waiting to be read. This
9822 may improve performance by pipelining better. We'll see.
9823 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
9824 from failed circuits (if they haven't been connected yet) and attach
9826 - Expire old streams that haven't managed to connect. Some day we'll
9827 have them reattach to new circuits instead.
9830 - Fix several memory leaks that were causing servers to become bloated
9832 - Fix a few very rare assert triggers. A few more remain.
9833 - Setuid to User _before_ complaining about running as root.
9836 Changes in version 0.0.2pre19 - 2004-01-07
9838 - Fix deadlock condition in dns farm. We were telling a child to die by
9839 closing the parent's file descriptor to him. But newer children were
9840 inheriting the open file descriptor from the parent, and since they
9841 weren't closing it, the socket never closed, so the child never read
9842 eof, so he never knew to exit. Similarly, dns workers were holding
9843 open other sockets, leading to all sorts of chaos.
9844 - New cleaner daemon() code for forking and backgrounding.
9845 - If you log to a file, it now prints an entry at the top of the
9846 logfile so you know it's working.
9847 - The onionskin challenge length was 30 bytes longer than necessary.
9848 - Started to patch up the spec so it's not quite so out of date.
9851 Changes in version 0.0.2pre18 - 2004-01-02
9853 - Fix endian issues with the 'integrity' field in the relay header.
9854 - Fix a potential bug where connections in state
9855 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
9858 Changes in version 0.0.2pre17 - 2003-12-30
9860 - Made --debuglogfile (or any second log file, actually) work.
9861 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
9862 adversary could force us into an infinite loop.
9865 - Each onionskin handshake now includes a hash of the computed key,
9866 to prove the server's identity and help perfect forward secrecy.
9867 - Changed cell size from 256 to 512 bytes (working toward compatibility
9869 - Changed cell length to 2 bytes, and moved it to the relay header.
9870 - Implemented end-to-end integrity checking for the payloads of
9872 - Separated streamid from 'recognized' (otherwise circuits will get
9873 messed up when we try to have streams exit from the middle). We
9874 use the integrity-checking to confirm that a cell is addressed to
9876 - Randomize the initial circid and streamid values, so an adversary who
9877 breaks into a node can't learn how many circuits or streams have
9881 Changes in version 0.0.2pre16 - 2003-12-14
9883 - Fixed a bug that made HUP trigger an assert
9884 - Fixed a bug where a circuit that immediately failed wasn't being
9885 counted as a failed circuit in counting retries.
9888 - Now we close the circuit when we get a truncated cell: otherwise we're
9889 open to an anonymity attack where a bad node in the path truncates
9890 the circuit and then we open streams at him.
9891 - Add port ranges to exit policies
9892 - Add a conservative default exit policy
9893 - Warn if you're running tor as root
9894 - on HUP, retry OR connections and close/rebind listeners
9895 - options.EntryNodes: try these nodes first when picking the first node
9896 - options.ExitNodes: if your best choices happen to include any of
9897 your preferred exit nodes, you choose among just those preferred
9899 - options.ExcludedNodes: nodes that are never picked in path building
9902 Changes in version 0.0.2pre15 - 2003-12-03
9903 o Robustness and bugfixes:
9904 - Sometimes clients would cache incorrect DNS resolves, which would
9905 really screw things up.
9906 - An OP that goes offline would slowly leak all its sockets and stop
9908 - A wide variety of bugfixes in exit node selection, exit policy
9909 handling, and processing pending streams when a new circuit is
9911 - Pick nodes for a path only from those the directory says are up
9912 - Choose randomly from all running dirservers, not always the first one
9913 - Increase allowed http header size for directory fetch.
9914 - Stop writing to stderr (if we're daemonized it will be closed).
9915 - Enable -g always, so cores will be more useful to me.
9916 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
9919 - Wrote a man page. It lists commonly used options.
9922 - Change default loglevel to warn.
9923 - Make PidFile default to null rather than littering in your CWD.
9924 - OnionRouter config option is now obsolete. Instead it just checks
9926 - Moved to a single unified torrc file for both clients and servers.
9929 Changes in version 0.0.2pre14 - 2003-11-29
9930 o Robustness and bugfixes:
9931 - Force the admin to make the DataDirectory himself
9932 - to get ownership/permissions right
9933 - so clients no longer make a DataDirectory and then never use it
9934 - fix bug where a client who was offline for 45 minutes would never
9935 pull down a directory again
9936 - fix (or at least hide really well) the dns assert bug that was
9937 causing server crashes
9938 - warnings and improved robustness wrt clockskew for certs
9939 - use the native daemon(3) to daemonize, when available
9940 - exit if bind() fails
9941 - exit if neither socksport nor orport is defined
9942 - include our own tor_timegm (Win32 doesn't have its own)
9943 - bugfix for win32 with lots of connections
9944 - fix minor bias in PRNG
9945 - make dirserver more robust to corrupt cached directory
9948 - Wrote the design document (woo)
9950 o Circuit building and exit policies:
9951 - Circuits no longer try to use nodes that the directory has told them
9953 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
9954 bitcounts (18.0.0.0/8).
9955 - Make AP connections standby for a circuit if no suitable circuit
9956 exists, rather than failing
9957 - Circuits choose exit node based on addr/port, exit policies, and
9958 which AP connections are standing by
9959 - Bump min pathlen from 2 to 3
9960 - Relay end cells have a payload to describe why the stream ended.
9961 - If the stream failed because of exit policy, try again with a new
9963 - Clients have a dns cache to remember resolved addresses.
9964 - Notice more quickly when we have no working circuits
9967 - APPort is now called SocksPort
9968 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
9970 - RecommendedVersions is now a config variable rather than
9971 hardcoded (for dirservers)
9972 - Reloads config on HUP
9973 - Usage info on -h or --help
9974 - If you set User and Group config vars, it'll setu/gid to them.
9977 Changes in version 0.0.2pre13 - 2003-10-19
9978 o General stability:
9979 - SSL_write no longer fails when it returns WANTWRITE and the number
9980 of bytes in the buf has changed by the next SSL_write call.
9981 - Fix segfault fetching directory when network is down
9982 - Fix a variety of minor memory leaks
9983 - Dirservers reload the fingerprints file on HUP, so I don't have
9984 to take down the network when I approve a new router
9985 - Default server config file has explicit Address line to specify fqdn
9988 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
9989 - Make listener connections not ever alloc bufs
9991 o Autoconf improvements:
9992 - don't clobber an external CFLAGS in ./configure
9993 - Make install now works
9994 - create var/lib/tor on make install
9995 - autocreate a tor.sh initscript to help distribs
9996 - autocreate the torrc and sample-server-torrc with correct paths
9998 o Log files and Daemonizing now work:
9999 - If --DebugLogFile is specified, log to it at -l debug
10000 - If --LogFile is specified, use it instead of commandline
10001 - If --RunAsDaemon is set, tor forks and backgrounds on startup