1 Changes in version 0.2.2.15-alpha - 2010-07-2?
3 - Stop assigning the HSDir flag to relays that disable their
4 DirPort (and thus will refuse to answer directory requests). This
5 fix should dramatically improve the reachability of hidden services:
6 hidden services and hidden service clients pick three HSDir relays
7 to store and retrieve the hidden service descriptor, and currently
8 about half of the HSDir relays will refuse to work. Bugfix on
9 0.2.0.10-alpha; fixes part of bug 1693.
12 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
13 should give us approximately 40-50% more Guard-flagged nodes,
14 improving the anonymity the Tor network can provide and also
15 decreasing the dropoff in throughput that relays experience when
16 they first get the Guard flag.
19 - Have the controller interface give a more useful message than
20 "Internal Error" in response to failed GETINFO requests.
23 - Alter directory authorities to always consider Exit-flagged nodes
24 as potential Guard nodes in their votes. The actual decision to
25 use Exits as Guards is done in the consensus bandwidth weights.
26 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
27 - When the controller is reporting the purpose of circuits that
28 didn't finish building before the circuit build timeout, it was
29 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
30 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
31 would return "551 Internal error" rather than "552 Unrecognized key
35 Changes in version 0.2.2.14-alpha - 2010-07-12
36 Tor 0.2.2.14-alpha greatly improves client-side handling of
37 circuit build timeouts, which are used to estimate speed and improve
38 performance. We also move to a much better GeoIP database, port Tor to
39 Windows CE, introduce new compile flags that improve code security,
40 add an eighth v3 directory authority, and address a lot of more
44 - Tor directory authorities no longer crash when started with a
45 cached-microdesc-consensus file in their data directory. Bugfix
46 on 0.2.2.6-alpha; fixes bug 1532.
47 - Treat an unset $HOME like an empty $HOME rather than triggering an
48 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
49 - Ignore negative and large circuit build timeout values that can
50 happen during a suspend or hibernate. These values caused various
51 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
52 - Alter calculation of Pareto distribution parameter 'Xm' for
53 Circuit Build Timeout learning to use the weighted average of the
54 top N=3 modes (because we have three entry guards). Considering
55 multiple modes should improve the timeout calculation in some cases,
56 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
58 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
59 right censored distribution model. This approach improves over the
60 synthetic timeout generation approach that was producing insanely
61 high timeout values. Now we calculate build timeouts using truncated
62 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
63 - Do not close circuits that are under construction when they reach
64 the circuit build timeout. Instead, leave them building (but do not
65 use them) for up until the time corresponding to the 95th percentile
66 on the Pareto CDF or 60 seconds, whichever is greater. This is done
67 to provide better data for the new Pareto model. This percentile
68 can be controlled by the consensus.
71 - Move to the June 2010 Maxmind GeoLite country db (rather than the
72 June 2009 ip-to-country GeoIP db) for our statistics that count
73 how many users relays are seeing from each country. Now we have
74 more accurate data for many African countries.
75 - Port Tor to build and run correctly on Windows CE systems, using
76 the wcecompat library. Contributed by Valerio Lupi.
77 - New "--enable-gcc-hardening" ./configure flag (off by default)
78 to turn on gcc compile time hardening options. It ensures
79 that signed ints have defined behavior (-fwrapv), enables
80 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
81 with canaries (-fstack-protector-all), turns on ASLR protection if
82 supported by the kernel (-fPIE, -pie), and adds additional security
83 related warnings. Verified to work on Mac OS X and Debian Lenny.
84 - New "--enable-linker-hardening" ./configure flag (off by default)
85 to turn on ELF specific hardening features (relro, now). This does
86 not work with Mac OS X or any other non-ELF binary format.
88 o New directory authorities:
89 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
93 - New config option "WarnUnsafeSocks 0" disables the warning that
94 occurs whenever Tor receives only an IP address instead of a
95 hostname. Setups that do DNS locally over Tor are fine, and we
96 shouldn't spam the logs in that case.
97 - Convert the HACKING file to asciidoc, and add a few new sections
98 to it, explaining how we use Git, how we make changelogs, and
99 what should go in a patch.
100 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
101 event, to give information on the current rate of circuit timeouts
102 over our stored history.
103 - Add ability to disable circuit build time learning via consensus
104 parameter and via a LearnCircuitBuildTimeout config option. Also
105 automatically disable circuit build time calculation if we are
106 either a AuthoritativeDirectory, or if we fail to write our state
107 file. Fixes bug 1296.
108 - More gracefully handle corrupt state files, removing asserts
109 in favor of saving a backup and resetting state.
110 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
114 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
116 - When a2x fails, mention that the user could disable manpages instead
117 of trying to fix their asciidoc installation.
118 - Where available, use Libevent 2.0's periodic timers so that our
119 once-per-second cleanup code gets called even more closely to
120 once per second than it would otherwise. Fixes bug 943.
121 - If you run a bridge that listens on multiple IP addresses, and
122 some user configures a bridge address that uses a different IP
123 address than your bridge writes in its router descriptor, and the
124 user doesn't specify an identity key, their Tor would discard the
125 descriptor because "it isn't one of our configured bridges", and
126 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
127 Bugfix on 0.2.0.3-alpha.
128 - If OpenSSL fails to make a duplicate of a private or public key, log
129 an error message and try to exit cleanly. May help with debugging
130 if bug 1209 ever remanifests.
131 - Save a couple bytes in memory allocation every time we escape
132 certain characters in a string. Patch from Florian Zumbiehl.
133 - Make it explicit that we don't cannibalize one-hop circuits. This
134 happens in the wild, but doesn't turn out to be a problem because
135 we fortunately don't use those circuits. Many thanks to outofwords
136 for the initial analysis and to swissknife who confirmed that
137 two-hop circuits are actually created.
138 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
139 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
140 - Eliminate a case where a circuit build time warning was displayed
141 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
144 Changes in version 0.2.1.26 - 2010-05-02
145 Tor 0.2.1.26 addresses the recent connection and memory overload
146 problems we've been seeing on relays, especially relays with their
147 DirPort open. If your relay has been crashing, or you turned it off
148 because it used too many resources, give this release a try.
150 This release also fixes yet another instance of broken OpenSSL libraries
151 that was causing some relays to drop out of the consensus.
154 - Teach relays to defend themselves from connection overload. Relays
155 now close idle circuits early if it looks like they were intended
156 for directory fetches. Relays are also more aggressive about closing
157 TLS connections that have no circuits on them. Such circuits are
158 unlikely to be re-used, and tens of thousands of them were piling
159 up at the fast relays, causing the relays to run out of sockets
160 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
161 their directory fetches over TLS).
162 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
163 that claim to be earlier than 0.9.8m, but which have in reality
164 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
165 behavior. Possible fix for some cases of bug 1346.
166 - Directory mirrors were fetching relay descriptors only from v2
167 directory authorities, rather than v3 authorities like they should.
168 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
169 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
172 - Finally get rid of the deprecated and now harmful notion of "clique
173 mode", where directory authorities maintain TLS connections to
177 - In the util/threads test, no longer free the test_mutex before all
178 worker threads have finished. Bugfix on 0.2.1.6-alpha.
179 - The master thread could starve the worker threads quite badly on
180 certain systems, causing them to run only partially in the allowed
181 window. This resulted in test failures. Now the master thread sleeps
182 occasionally for a few microseconds while the two worker-threads
183 compete for the mutex. Bugfix on 0.2.0.1-alpha.
186 Changes in version 0.2.2.13-alpha - 2010-04-24
187 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
188 problems we've been seeing on relays, especially relays with their
189 DirPort open. If your relay has been crashing, or you turned it off
190 because it used too many resources, give this release a try.
193 - Teach relays to defend themselves from connection overload. Relays
194 now close idle circuits early if it looks like they were intended
195 for directory fetches. Relays are also more aggressive about closing
196 TLS connections that have no circuits on them. Such circuits are
197 unlikely to be re-used, and tens of thousands of them were piling
198 up at the fast relays, causing the relays to run out of sockets
199 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
200 their directory fetches over TLS).
203 - Finally get rid of the deprecated and now harmful notion of "clique
204 mode", where directory authorities maintain TLS connections to
206 - Directory authorities now do an immediate reachability check as soon
207 as they hear about a new relay. This change should slightly reduce
208 the time between setting up a relay and getting listed as running
209 in the consensus. It should also improve the time between setting
210 up a bridge and seeing use by bridge users.
211 - Directory authorities no longer launch a TLS connection to every
212 relay as they startup. Now that we have 2k+ descriptors cached,
213 the resulting network hiccup is becoming a burden. Besides,
214 authorities already avoid voting about Running for the first half
215 hour of their uptime.
218 Changes in version 0.2.2.12-alpha - 2010-04-20
219 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
220 handle and vote on descriptors. It was causing relays to drop out of
224 - Many relays have been falling out of the consensus lately because
225 not enough authorities know about their descriptor for them to get
226 a majority of votes. When we deprecated the v2 directory protocol,
227 we got rid of the only way that v3 authorities can hear from each
228 other about other descriptors. Now authorities examine every v3
229 vote for new descriptors, and fetch them from that authority. Bugfix
231 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
232 and a warning in or.h related to bandwidth_weight_rule_t that
233 prevented clean compile on OS X. Fixes bug 1363; bugfix on
235 - Fix a segfault on relays when DirReqStatistics is enabled
236 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
240 - Demote a confusing TLS warning that relay operators might get when
241 someone tries to talk to their OrPort. It is neither the operator's
242 fault nor can they do anything about it. Fixes bug 1364; bugfix
246 Changes in version 0.2.2.11-alpha - 2010-04-15
247 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
248 libraries that was causing some relays to drop out of the consensus.
251 - Directory mirrors were fetching relay descriptors only from v2
252 directory authorities, rather than v3 authorities like they should.
253 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
254 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
255 - Fix a parsing error that made every possible value of
256 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
257 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
258 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
259 about the option without breaking older ones.
260 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
261 that claim to be earlier than 0.9.8m, but which have in reality
262 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
263 behavior. Possible fix for some cases of bug 1346.
266 - Experiment with a more aggressive approach to preventing clients
267 from making one-hop exit streams. Exit relays who want to try it
268 out can set "RefuseUnknownExits 1" in their torrc, and then look
269 for "Attempt by %s to open a stream" log messages. Let us know
271 - Add support for statically linking zlib by specifying
272 --enable-static-zlib, to go with our support for statically linking
273 openssl and libevent. Resolves bug 1358.
276 - Fix a segfault that happens whenever a Tor client that is using
277 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
279 - When we cleaned up the contrib/tor-exit-notice.html file, we left
280 out the first line. Fixes bug 1295.
281 - When building the manpage from a tarball, we required asciidoc, but
282 the asciidoc -> roff/html conversion was already done for the
283 tarball. Make 'make' complain only when we need asciidoc (either
284 because we're compiling directly from git, or because we altered
285 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
286 - When none of the directory authorities vote on any params, Tor
287 segfaulted when trying to make the consensus from the votes. We
288 didn't trigger the bug in practice, because authorities do include
289 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
292 - In the util/threads test, no longer free the test_mutex before all
293 worker threads have finished. Bugfix on 0.2.1.6-alpha.
294 - The master thread could starve the worker threads quite badly on
295 certain systems, causing them to run only partially in the allowed
296 window. This resulted in test failures. Now the master thread sleeps
297 occasionally for a few microseconds while the two worker-threads
298 compete for the mutex. Bugfix on 0.2.0.1-alpha.
301 Changes in version 0.2.2.10-alpha - 2010-03-07
302 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
303 could prevent relays from guessing their IP address correctly. It also
304 starts the groundwork for another client-side performance boost, since
305 currently we're not making efficient use of relays that have both the
306 Guard flag and the Exit flag.
309 - Fix a regression from our patch for bug 1244 that caused relays
310 to guess their IP address incorrectly if they didn't set Address
311 in their torrc and/or their address fails to resolve. Bugfix on
312 0.2.2.9-alpha; fixes bug 1269.
314 o Major features (performance):
315 - Directory authorities now compute consensus weightings that instruct
316 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
317 and no flag. Clients that use these weightings will distribute
318 network load more evenly across these different relay types. The
319 weightings are in the consensus so we can change them globally in
320 the future. Extra thanks to "outofwords" for finding some nasty
321 security bugs in the first implementation of this feature.
323 o Minor features (performance):
324 - Always perform router selections using weighted relay bandwidth,
325 even if we don't need a high capacity circuit at the time. Non-fast
326 circuits now only differ from fast ones in that they can use relays
327 not marked with the Fast flag. This "feature" could turn out to
328 be a horrible bug; we should investigate more before it goes into
332 - Allow disabling building of the manpages. Skipping the manpage
333 speeds up the build considerably.
335 o Minor bugfixes (on 0.2.2.x):
336 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
337 Bugfix on 0.2.2.9-alpha.
338 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
339 config option. Bugfix on 0.2.2.7-alpha.
340 - Ship the asciidoc-helper file in the tarball, so that people can
341 build from source if they want to, and touching the .1.txt files
342 doesn't break the build. Bugfix on 0.2.2.9-alpha.
344 o Minor bugfixes (on 0.2.1.x or earlier):
345 - Fix a dereference-then-NULL-check sequence when publishing
346 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
348 - Fix another dereference-then-NULL-check sequence. Bugfix on
349 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
350 - Make sure we treat potentially not NUL-terminated strings correctly.
351 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
353 o Code simplifications and refactoring:
354 - Fix some urls in the exit notice file and make it XHTML1.1 strict
355 compliant. Based on a patch from Christian Kujau.
356 - Don't use sed in asciidoc-helper anymore.
357 - Make the build process fail if asciidoc cannot be found and
358 building with asciidoc isn't disabled.
361 Changes in version 0.2.2.9-alpha - 2010-02-22
362 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
363 location of a directory authority, and cleans up a bunch of small bugs.
365 o Directory authority changes:
366 - Change IP address for dannenberg (v3 directory authority), and
367 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
368 service directory authority) from the list.
371 - Make Tor work again on the latest OS X: when deciding whether to
372 use strange flags to turn TLS renegotiation on, detect the OpenSSL
373 version at run-time, not compile time. We need to do this because
374 Apple doesn't update its dev-tools headers when it updates its
375 libraries in a security patch.
376 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
377 that could happen on 32-bit platforms with 64-bit time_t. Also fix
378 a memory leak when requesting a hidden service descriptor we've
379 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
381 - Authorities could be tricked into giving out the Exit flag to relays
382 that didn't allow exiting to any ports. This bug could screw
383 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
384 1238. Bug discovered by Martin Kowalczyk.
385 - When freeing a session key, zero it out completely. We only zeroed
386 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
387 patched by ekir. Fixes bug 1254.
390 - Fix static compilation by listing the openssl libraries in the right
391 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
392 - Resume handling .exit hostnames in a special way: originally we
393 stripped the .exit part and used the requested exit relay. In
394 0.2.2.1-alpha we stopped treating them in any special way, meaning
395 if you use a .exit address then Tor will pass it on to the exit
396 relay. Now we reject the .exit stream outright, since that behavior
397 might be more expected by the user. Found and diagnosed by Scott
398 Bennett and Downie on or-talk.
399 - Don't spam the controller with events when we have no file
400 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
401 for log messages was already solved from bug 748.)
402 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
404 - Make the DNSPort option work with libevent 2.x. Don't alter the
405 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
406 - Emit a GUARD DROPPED controller event for a case we missed.
407 - Make more fields in the controller protocol case-insensitive, since
408 control-spec.txt said they were.
409 - Refactor resolve_my_address() to not use gethostbyname() anymore.
410 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
411 - Fix a spec conformance issue: the network-status-version token
412 must be the first token in a v3 consensus or vote. Discovered by
413 parakeep. Bugfix on 0.2.0.3-alpha.
415 o Code simplifications and refactoring:
416 - Generate our manpage and HTML documentation using Asciidoc. This
417 change should make it easier to maintain the documentation, and
419 - Remove the --enable-iphone option. According to reports from Marco
420 Bonetti, Tor builds fine without any special tweaking on recent
422 - Removed some unnecessary files from the source distribution. The
423 AUTHORS file has now been merged into the people page on the
424 website. The roadmaps and design doc can now be found in the
425 projects directory in svn.
426 - Enabled various circuit build timeout constants to be controlled
427 by consensus parameters. Also set better defaults for these
428 parameters based on experimentation on broadband and simulated
432 - The 'EXTENDCIRCUIT' control port command can now be used with
433 a circ id of 0 and no path. This feature will cause Tor to build
434 a new 'fast' general purpose circuit using its own path selection
436 - Added a BUILDTIMEOUT_SET controller event to describe changes
437 to the circuit build timeout.
438 - Future-proof the controller protocol a bit by ignoring keyword
439 arguments we do not recognize.
440 - Expand homedirs passed to tor-checkkey. This should silence a
441 coverity complaint about passing a user-supplied string into
442 open() without checking it.
445 Changes in version 0.2.1.25 - 2010-03-16
446 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
447 prevent relays from guessing their IP address correctly. It also fixes
448 several minor potential security bugs.
451 - Fix a regression from our patch for bug 1244 that caused relays
452 to guess their IP address incorrectly if they didn't set Address
453 in their torrc and/or their address fails to resolve. Bugfix on
454 0.2.1.23; fixes bug 1269.
455 - When freeing a session key, zero it out completely. We only zeroed
456 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
457 patched by ekir. Fixes bug 1254.
460 - Fix a dereference-then-NULL-check sequence when publishing
461 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
463 - Fix another dereference-then-NULL-check sequence. Bugfix on
464 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
465 - Make sure we treat potentially not NUL-terminated strings correctly.
466 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
470 Changes in version 0.2.1.24 - 2010-02-21
471 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
475 - Work correctly out-of-the-box with even more vendor-patched versions
476 of OpenSSL. In particular, make it so Debian and OS X don't need
477 customized patches to run/build.
480 Changes in version 0.2.1.23 - 2010-02-13
481 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
482 again on the latest OS X, and updates the location of a directory
485 o Major bugfixes (performance):
486 - We were selecting our guards uniformly at random, and then weighting
487 which of our guards we'd use uniformly at random. This imbalance
488 meant that Tor clients were severely limited on throughput (and
489 probably latency too) by the first hop in their circuit. Now we
490 select guards weighted by currently advertised bandwidth. We also
491 automatically discard guards picked using the old algorithm. Fixes
492 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
495 - Make Tor work again on the latest OS X: when deciding whether to
496 use strange flags to turn TLS renegotiation on, detect the OpenSSL
497 version at run-time, not compile time. We need to do this because
498 Apple doesn't update its dev-tools headers when it updates its
499 libraries in a security patch.
500 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
501 that could happen on 32-bit platforms with 64-bit time_t. Also fix
502 a memory leak when requesting a hidden service descriptor we've
503 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
506 o Directory authority changes:
507 - Change IP address for dannenberg (v3 directory authority), and
508 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
509 service directory authority) from the list.
512 - Refactor resolve_my_address() to not use gethostbyname() anymore.
513 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
516 - Avoid a mad rush at the beginning of each month when each client
517 rotates half of its guards. Instead we spread the rotation out
518 throughout the month, but we still avoid leaving a precise timestamp
519 in the state file about when we first picked the guard. Improves
520 over the behavior introduced in 0.1.2.17.
523 Changes in version 0.2.2.8-alpha - 2010-01-26
524 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
525 causing bridge relays to disappear. If you're running a bridge,
529 - Fix a memory corruption bug on bridges that occured during the
530 inclusion of stats data in extra-info descriptors. Also fix the
531 interface for geoip_get_bridge_stats* to prevent similar bugs in
532 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
533 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
536 - Ignore OutboundBindAddress when connecting to localhost.
537 Connections to localhost need to come _from_ localhost, or else
538 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
542 Changes in version 0.2.2.7-alpha - 2010-01-19
543 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
544 as laying the groundwork for further relay-side performance fixes. It
545 also starts cleaning up client behavior with respect to the EntryNodes,
546 ExitNodes, and StrictNodes config options.
548 This release also rotates two directory authority keys, due to a
549 security breach of some of the Torproject servers.
551 o Directory authority changes:
552 - Rotate keys (both v3 identity and relay identity) for moria1
555 o Major features (performance):
556 - We were selecting our guards uniformly at random, and then weighting
557 which of our guards we'd use uniformly at random. This imbalance
558 meant that Tor clients were severely limited on throughput (and
559 probably latency too) by the first hop in their circuit. Now we
560 select guards weighted by currently advertised bandwidth. We also
561 automatically discard guards picked using the old algorithm. Fixes
562 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
563 - When choosing which cells to relay first, relays can now favor
564 circuits that have been quiet recently, to provide lower latency
565 for low-volume circuits. By default, relays enable or disable this
566 feature based on a setting in the consensus. You can override
567 this default by using the new "CircuitPriorityHalflife" config
568 option. Design and code by Ian Goldberg, Can Tang, and Chris
570 - Add separate per-conn write limiting to go with the per-conn read
571 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
572 but never per-conn write limits.
573 - New consensus params "bwconnrate" and "bwconnburst" to let us
574 rate-limit client connections as they enter the network. It's
575 controlled in the consensus so we can turn it on and off for
576 experiments. It's starting out off. Based on proposal 163.
578 o Major features (relay selection options):
579 - Switch to a StrictNodes config option, rather than the previous
580 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
581 "StrictExcludeNodes" option.
582 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
583 change during a config reload, mark and discard all our origin
584 circuits. This fix should address edge cases where we change the
585 config options and but then choose a circuit that we created before
587 - If EntryNodes or ExitNodes are set, be more willing to use an
588 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
590 - Make EntryNodes config option much more aggressive even when
591 StrictNodes is not set. Before it would prepend your requested
592 entrynodes to your list of guard nodes, but feel free to use others
593 after that. Now it chooses only from your EntryNodes if any of
594 those are available, and only falls back to others if a) they're
595 all down and b) StrictNodes is not set.
596 - Now we refresh your entry guards from EntryNodes at each consensus
597 fetch -- rather than just at startup and then they slowly rot as
601 - Stop bridge directory authorities from answering dbg-stability.txt
602 directory queries, which would let people fetch a list of all
603 bridge identities they track. Bugfix on 0.2.1.6-alpha.
606 - Log a notice when we get a new control connection. Now it's easier
607 for security-conscious users to recognize when a local application
608 is knocking on their controller door. Suggested by bug 1196.
609 - New config option "CircuitStreamTimeout" to override our internal
610 timeout schedule for how many seconds until we detach a stream from
611 a circuit and try a new circuit. If your network is particularly
612 slow, you might want to set this to a number like 60.
613 - New controller command "getinfo config-text". It returns the
614 contents that Tor would write if you send it a SAVECONF command,
615 so the controller can write the file to disk itself.
616 - New options for SafeLogging to allow scrubbing only log messages
617 generated while acting as a relay.
618 - Ship the bridges spec file in the tarball too.
619 - Avoid a mad rush at the beginning of each month when each client
620 rotates half of its guards. Instead we spread the rotation out
621 throughout the month, but we still avoid leaving a precise timestamp
622 in the state file about when we first picked the guard. Improves
623 over the behavior introduced in 0.1.2.17.
625 o Minor bugfixes (compiling):
626 - Fix compilation on OS X 10.3, which has a stub mlockall() but
627 hides it. Bugfix on 0.2.2.6-alpha.
628 - Fix compilation on Solaris by removing support for the
629 DisableAllSwap config option. Solaris doesn't have an rlimit for
630 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
633 o Minor bugfixes (crashes):
634 - Do not segfault when writing buffer stats when we haven't observed
635 a single circuit to report about. Found by Fabian Lanze. Bugfix on
637 - If we're in the pathological case where there's no exit bandwidth
638 but there is non-exit bandwidth, or no guard bandwidth but there
639 is non-guard bandwidth, don't crash during path selection. Bugfix
641 - Fix an impossible-to-actually-trigger buffer overflow in relay
642 descriptor generation. Bugfix on 0.1.0.15.
644 o Minor bugfixes (privacy):
645 - Fix an instance where a Tor directory mirror might accidentally
646 log the IP address of a misbehaving Tor client. Bugfix on
648 - Don't list Windows capabilities in relay descriptors. We never made
649 use of them, and maybe it's a bad idea to publish them. Bugfix
652 o Minor bugfixes (other):
653 - Resolve an edge case in path weighting that could make us misweight
654 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
655 - Fix statistics on client numbers by country as seen by bridges that
656 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
657 intervals instead of variable 12-to-48-hour intervals.
658 - After we free an internal connection structure, overwrite it
659 with a different memory value than we use for overwriting a freed
660 internal circuit structure. Should help with debugging. Suggested
662 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
666 - Remove the HSAuthorityRecordStats option that version 0 hidden
667 service authorities could have used to track statistics of overall
668 hidden service usage.
671 Changes in version 0.2.1.22 - 2010-01-19
672 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
673 authorities -- it would tell you its whole history of bridge descriptors
674 if you make the right directory request. This stable update also
675 rotates two of the seven v3 directory authority keys and locations.
677 o Directory authority changes:
678 - Rotate keys (both v3 identity and relay identity) for moria1
682 - Stop bridge directory authorities from answering dbg-stability.txt
683 directory queries, which would let people fetch a list of all
684 bridge identities they track. Bugfix on 0.2.1.6-alpha.
687 Changes in version 0.2.1.21 - 2009-12-21
688 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
689 library. If you use Tor on Linux / Unix and you're getting SSL
690 renegotiation errors, upgrading should help. We also recommend an
691 upgrade if you're an exit relay.
694 - Work around a security feature in OpenSSL 0.9.8l that prevents our
695 handshake from working unless we explicitly tell OpenSSL that we
696 are using SSL renegotiation safely. We are, of course, but OpenSSL
697 0.9.8l won't work unless we say we are.
698 - Avoid crashing if the client is trying to upload many bytes and the
699 circuit gets torn down at the same time, or if the flip side
700 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
703 - Do not refuse to learn about authority certs and v2 networkstatus
704 documents that are older than the latest consensus. This bug might
705 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
706 Spotted and fixed by xmux.
707 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
708 trigger platform-specific option misparsing case found by Coverity
710 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
711 trigger assert. Fixes bug 1173.
714 Changes in version 0.2.2.6-alpha - 2009-11-19
715 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
716 support for the new lower-footprint "microdescriptor" directory design,
717 future-proofing our consensus format against new hash functions or
718 other changes, and an Android port. It also makes Tor compatible with
719 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
722 - Directory authorities can now create, vote on, and serve multiple
723 parallel formats of directory data as part of their voting process.
724 Partially implements Proposal 162: "Publish the consensus in
726 - Directory authorities can now agree on and publish small summaries
727 of router information that clients can use in place of regular
728 server descriptors. This transition will eventually allow clients
729 to use far less bandwidth for downloading information about the
730 network. Begins the implementation of Proposal 158: "Clients
731 download consensus + microdescriptors".
732 - The directory voting system is now extensible to use multiple hash
733 algorithms for signatures and resource selection. Newer formats
734 are signed with SHA256, with a possibility for moving to a better
735 hash algorithm in the future.
736 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
737 current and future memory pages via mlockall(). On supported
738 platforms (modern Linux and probably BSD but not Windows or OS X),
739 this should effectively disable any and all attempts to page out
740 memory. This option requires that you start your Tor as root --
741 if you use DisableAllSwap, please consider using the User option
742 to properly reduce the privileges of your Tor.
743 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
744 to help Tor build correctly for Android phones.
747 - Work around a security feature in OpenSSL 0.9.8l that prevents our
748 handshake from working unless we explicitly tell OpenSSL that we
749 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
750 won't work unless we say we are.
753 - Fix a crash bug when trying to initialize the evdns module in
754 Libevent 2. Bugfix on 0.2.1.16-rc.
755 - Stop logging at severity 'warn' when some other Tor client tries
756 to establish a circuit with us using weak DH keys. It's a protocol
757 violation, but that doesn't mean ordinary users need to hear about
758 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
759 - Do not refuse to learn about authority certs and v2 networkstatus
760 documents that are older than the latest consensus. This bug might
761 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
762 Spotted and fixed by xmux.
763 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
764 - If all authorities restart at once right before a consensus vote,
765 nobody will vote about "Running", and clients will get a consensus
766 with no usable relays. Instead, authorities refuse to build a
767 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
768 - If your relay can't keep up with the number of incoming create
769 cells, it would log one warning per failure into your logs. Limit
770 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
771 - Bridges now use "reject *:*" as their default exit policy. Bugfix
772 on 0.2.0.3-alpha; fixes bug 1113.
773 - Fix a memory leak on directory authorities during voting that was
774 introduced in 0.2.2.1-alpha. Found via valgrind.
777 Changes in version 0.2.1.20 - 2009-10-15
778 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
779 services at once, prepares for more performance improvements, and
780 fixes a bunch of smaller bugs.
782 The Windows and OS X bundles also include a more recent Vidalia,
783 and switch from Privoxy to Polipo.
785 The OS X installers are now drag and drop. It's best to un-install
786 Tor/Vidalia and then install this new bundle, rather than upgrade. If
787 you want to upgrade, you'll need to update the paths for Tor and Polipo
788 in the Vidalia Settings window.
791 - Send circuit or stream sendme cells when our window has decreased
792 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
793 by Karsten when testing the "reduce circuit window" performance
794 patch. Bugfix on the 54th commit on Tor -- from July 2002,
795 before the release of Tor 0.0.0. This is the new winner of the
797 - Fix a remotely triggerable memory leak when a consensus document
798 contains more than one signature from the same voter. Bugfix on
800 - Avoid segfault in rare cases when finishing an introduction circuit
801 as a client and finding out that we don't have an introduction key
802 for it. Fixes bug 1073. Reported by Aaron Swartz.
805 - Tor now reads the "circwindow" parameter out of the consensus,
806 and uses that value for its circuit package window rather than the
807 default of 1000 cells. Begins the implementation of proposal 168.
809 o New directory authorities:
810 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
812 - Move moria1 and tonga to alternate IP addresses.
815 - Fix a signed/unsigned compile warning in 0.2.1.19.
816 - Fix possible segmentation fault on directory authorities. Bugfix on
818 - Fix an extremely rare infinite recursion bug that could occur if
819 we tried to log a message after shutting down the log subsystem.
820 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
821 - Fix an obscure bug where hidden services on 64-bit big-endian
822 systems might mis-read the timestamp in v3 introduce cells, and
823 refuse to connect back to the client. Discovered by "rotor".
824 Bugfix on 0.2.1.6-alpha.
825 - We were triggering a CLOCK_SKEW controller status event whenever
826 we connect via the v2 connection protocol to any relay that has
827 a wrong clock. Instead, we should only inform the controller when
828 it's a trusted authority that claims our clock is wrong. Bugfix
829 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
830 - We were telling the controller about CHECKING_REACHABILITY and
831 REACHABILITY_FAILED status events whenever we launch a testing
832 circuit or notice that one has failed. Instead, only tell the
833 controller when we want to inform the user of overall success or
834 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
836 - Don't warn when we're using a circuit that ends with a node
837 excluded in ExcludeExitNodes, but the circuit is not used to access
838 the outside world. This should help fix bug 1090. Bugfix on
840 - Work around a small memory leak in some versions of OpenSSL that
841 stopped the memory used by the hostname TLS extension from being
845 - Add a "getinfo status/accepted-server-descriptor" controller
846 command, which is the recommended way for controllers to learn
847 whether our server descriptor has been successfully received by at
848 least on directory authority. Un-recommend good-server-descriptor
849 getinfo and status events until we have a better design for them.
852 Changes in version 0.2.2.5-alpha - 2009-10-11
853 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
856 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
858 o New directory authorities:
859 - Move dizum to an alternate IP address.
862 Changes in version 0.2.2.4-alpha - 2009-10-10
863 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
864 introduces a new unit test framework, shifts directry authority
865 addresses around to reduce the impact from recent blocking events,
866 and fixes a few smaller bugs.
869 - Fix several more asserts in the circuit_build_times code, for
870 example one that causes Tor to fail to start once we have
871 accumulated 5000 build times in the state file. Bugfixes on
872 0.2.2.2-alpha; fixes bug 1108.
874 o New directory authorities:
875 - Move moria1 and Tonga to alternate IP addresses.
878 - Log SSL state transitions at debug level during handshake, and
879 include SSL states in error messages. This may help debug future
880 SSL handshake issues.
881 - Add a new "Handshake" log domain for activities that happen
882 during the TLS handshake.
883 - Revert to the "June 3 2009" ip-to-country file. The September one
884 seems to have removed most US IP addresses.
885 - Directory authorities now reject Tor relays with versions less than
886 0.1.2.14. This step cuts out four relays from the current network,
887 none of which are very big.
890 - Fix a couple of smaller issues with gathering statistics. Bugfixes
892 - Fix two memory leaks in the error case of
893 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
894 - Don't count one-hop circuits when we're estimating how long it
895 takes circuits to build on average. Otherwise we'll set our circuit
896 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
897 - Directory authorities no longer change their opinion of, or vote on,
898 whether a router is Running, unless they have themselves been
899 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
902 o Code simplifications and refactoring:
903 - Revise our unit tests to use the "tinytest" framework, so we
904 can run tests in their own processes, have smarter setup/teardown
905 code, and so on. The unit test code has moved to its own
906 subdirectory, and has been split into multiple modules.
909 Changes in version 0.2.2.3-alpha - 2009-09-23
910 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
913 - Fix an overzealous assert in our new circuit build timeout code.
914 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
917 - If the networkstatus consensus tells us that we should use a
918 negative circuit package window, ignore it. Otherwise we'll
919 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
922 Changes in version 0.2.2.2-alpha - 2009-09-21
923 Tor 0.2.2.2-alpha introduces our latest performance improvement for
924 clients: Tor tracks the average time it takes to build a circuit, and
925 avoids using circuits that take too long to build. For fast connections,
926 this feature can cut your expected latency in half. For slow or flaky
927 connections, it could ruin your Tor experience. Let us know if it does!
930 - Tor now tracks how long it takes to build client-side circuits
931 over time, and adapts its timeout to local network performance.
932 Since a circuit that takes a long time to build will also provide
933 bad performance, we get significant latency improvements by
934 discarding the slowest 20% of circuits. Specifically, Tor creates
935 circuits more aggressively than usual until it has enough data
936 points for a good timeout estimate. Implements proposal 151.
937 We are especially looking for reports (good and bad) from users with
938 both EDGE and broadband connections that can move from broadband
939 to EDGE and find out if the build-time data in the .tor/state gets
940 reset without loss of Tor usability. You should also see a notice
941 log message telling you that Tor has reset its timeout.
942 - Directory authorities can now vote on arbitary integer values as
943 part of the consensus process. This is designed to help set
944 network-wide parameters. Implements proposal 167.
945 - Tor now reads the "circwindow" parameter out of the consensus,
946 and uses that value for its circuit package window rather than the
947 default of 1000 cells. Begins the implementation of proposal 168.
950 - Fix a remotely triggerable memory leak when a consensus document
951 contains more than one signature from the same voter. Bugfix on
955 - Fix an extremely rare infinite recursion bug that could occur if
956 we tried to log a message after shutting down the log subsystem.
957 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
958 - Fix parsing for memory or time units given without a space between
959 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
960 - A networkstatus vote must contain exactly one signature. Spec
961 conformance issue. Bugfix on 0.2.0.3-alpha.
962 - Fix an obscure bug where hidden services on 64-bit big-endian
963 systems might mis-read the timestamp in v3 introduce cells, and
964 refuse to connect back to the client. Discovered by "rotor".
965 Bugfix on 0.2.1.6-alpha.
966 - We were triggering a CLOCK_SKEW controller status event whenever
967 we connect via the v2 connection protocol to any relay that has
968 a wrong clock. Instead, we should only inform the controller when
969 it's a trusted authority that claims our clock is wrong. Bugfix
970 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
971 - We were telling the controller about CHECKING_REACHABILITY and
972 REACHABILITY_FAILED status events whenever we launch a testing
973 circuit or notice that one has failed. Instead, only tell the
974 controller when we want to inform the user of overall success or
975 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
977 - Don't warn when we're using a circuit that ends with a node
978 excluded in ExcludeExitNodes, but the circuit is not used to access
979 the outside world. This should help fix bug 1090, but more problems
980 remain. Bugfix on 0.2.1.6-alpha.
981 - Work around a small memory leak in some versions of OpenSSL that
982 stopped the memory used by the hostname TLS extension from being
984 - Make our 'torify' script more portable; if we have only one of
985 'torsocks' or 'tsocks' installed, don't complain to the user;
986 and explain our warning about tsocks better.
989 - Add a "getinfo status/accepted-server-descriptor" controller
990 command, which is the recommended way for controllers to learn
991 whether our server descriptor has been successfully received by at
992 least on directory authority. Un-recommend good-server-descriptor
993 getinfo and status events until we have a better design for them.
994 - Update to the "September 4 2009" ip-to-country file.
997 Changes in version 0.2.2.1-alpha - 2009-08-26
998 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
999 Tor clients to bootstrap on networks where only port 80 is reachable,
1000 makes it more straightforward to support hardware crypto accelerators,
1001 and starts the groundwork for gathering stats safely at relays.
1004 - Start the process of disabling ".exit" address notation, since it
1005 can be used for a variety of esoteric application-level attacks
1006 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
1009 o New directory authorities:
1010 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
1014 - New AccelName and AccelDir options add support for dynamic OpenSSL
1015 hardware crypto acceleration engines.
1016 - Tor now supports tunneling all of its outgoing connections over
1017 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
1018 configuration options. Code by Christopher Davis.
1021 - Send circuit or stream sendme cells when our window has decreased
1022 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
1023 by Karsten when testing the "reduce circuit window" performance
1024 patch. Bugfix on the 54th commit on Tor -- from July 2002,
1025 before the release of Tor 0.0.0. This is the new winner of the
1028 o New options for gathering stats safely:
1029 - Directories that set "DirReqStatistics 1" write statistics on
1030 directory request to disk every 24 hours. As compared to the
1031 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
1032 1) stats are written to disk exactly every 24 hours; 2) estimated
1033 shares of v2 and v3 requests are determined as mean values, not at
1034 the end of a measurement period; 3) unresolved requests are listed
1035 with country code '??'; 4) directories also measure download times.
1036 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
1037 number of exit streams and transferred bytes per port to disk every
1039 - Relays that set "CellStatistics 1" write statistics on how long
1040 cells spend in their circuit queues to disk every 24 hours.
1041 - Entry nodes that set "EntryStatistics 1" write statistics on the
1042 rough number and origins of connecting clients to disk every 24
1044 - Relays that write any of the above statistics to disk and set
1045 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
1046 their extra-info documents.
1049 - New --digests command-line switch to output the digests of the
1050 source files Tor was built with.
1051 - The "torify" script now uses torsocks where available.
1052 - The memarea code now uses a sentinel value at the end of each area
1053 to make sure nothing writes beyond the end of an area. This might
1054 help debug some conceivable causes of bug 930.
1055 - Time and memory units in the configuration file can now be set to
1056 fractional units. For example, "2.5 GB" is now a valid value for
1058 - Certain Tor clients (such as those behind check.torproject.org) may
1059 want to fetch the consensus in an extra early manner. To enable this
1060 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
1061 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
1062 as only certain clients who must have this information sooner should
1064 - Instead of adding the svn revision to the Tor version string, report
1065 the git commit (when we're building from a git checkout).
1068 - If any the v3 certs we download are unparseable, we should actually
1069 notice the failure so we don't retry indefinitely. Bugfix on
1070 0.2.0.x; reported by "rotator".
1071 - If the cached cert file is unparseable, warn but don't exit.
1072 - Fix possible segmentation fault on directory authorities. Bugfix on
1074 - When Tor fails to parse a descriptor of any kind, dump it to disk.
1075 Might help diagnosing bug 1051.
1077 o Deprecated and removed features:
1078 - The controller no longer accepts the old obsolete "addr-mappings/"
1079 or "unregistered-servers-" GETINFO values.
1080 - Hidden services no longer publish version 0 descriptors, and clients
1081 do not request or use version 0 descriptors. However, the old hidden
1082 service authorities still accept and serve version 0 descriptors
1083 when contacted by older hidden services/clients.
1084 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
1085 always on; using them is necessary for correct forward-compatible
1087 - Remove support for .noconnect style addresses. Nobody was using
1088 them, and they provided another avenue for detecting Tor users
1089 via application-level web tricks.
1091 o Packaging changes:
1092 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
1093 installer bundles. See
1094 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
1095 for details of what's new in Vidalia 0.2.3.
1096 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
1097 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
1098 configuration file, rather than the old Privoxy.
1099 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
1100 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
1101 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
1102 better compatibility with OS X 10.6, aka Snow Leopard.
1103 - OS X Vidalia Bundle: The multi-package installer is now replaced
1104 by a simple drag and drop to the /Applications folder. This change
1105 occurred with the upgrade to Vidalia 0.2.3.
1108 Changes in version 0.2.1.19 - 2009-07-28
1109 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
1110 services on Tor 0.2.1.3-alpha through 0.2.1.18.
1113 - Make accessing hidden services on 0.2.1.x work right again.
1114 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
1115 part of patch provided by "optimist".
1118 - When a relay/bridge is writing out its identity key fingerprint to
1119 the "fingerprint" file and to its logs, write it without spaces. Now
1120 it will look like the fingerprints in our bridges documentation,
1121 and confuse fewer users.
1124 - Relays no longer publish a new server descriptor if they change
1125 their MaxAdvertisedBandwidth config option but it doesn't end up
1126 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
1127 fixes bug 1026. Patch from Sebastian.
1128 - Avoid leaking memory every time we get a create cell but we have
1129 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
1130 fixes bug 1034. Reported by BarkerJr.
1133 Changes in version 0.2.1.18 - 2009-07-24
1134 Tor 0.2.1.18 lays the foundations for performance improvements,
1135 adds status events to help users diagnose bootstrap problems, adds
1136 optional authentication/authorization for hidden services, fixes a
1137 variety of potential anonymity problems, and includes a huge pile of
1138 other features and bug fixes.
1141 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
1144 Changes in version 0.2.1.17-rc - 2009-07-07
1145 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
1146 candidate for the 0.2.1.x series. It lays the groundwork for further
1147 client performance improvements, and also fixes a big bug with directory
1148 authorities that were causing them to assign Guard and Stable flags
1151 The Windows bundles also finally include the geoip database that we
1152 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
1153 should actually install Torbutton rather than giving you a cryptic
1154 failure message (oops).
1157 - Clients now use the bandwidth values in the consensus, rather than
1158 the bandwidth values in each relay descriptor. This approach opens
1159 the door to more accurate bandwidth estimates once the directory
1160 authorities start doing active measurements. Implements more of
1164 - When Tor clients restart after 1-5 days, they discard all their
1165 cached descriptors as too old, but they still use the cached
1166 consensus document. This approach is good for robustness, but
1167 bad for performance: since they don't know any bandwidths, they
1168 end up choosing at random rather than weighting their choice by
1169 speed. Fixed by the above feature of putting bandwidths in the
1170 consensus. Bugfix on 0.2.0.x.
1171 - Directory authorities were neglecting to mark relays down in their
1172 internal histories if the relays fall off the routerlist without
1173 ever being found unreachable. So there were relays in the histories
1174 that haven't been seen for eight months, and are listed as being
1175 up for eight months. This wreaked havoc on the "median wfu"
1176 and "median mtbf" calculations, in turn making Guard and Stable
1177 flags very wrong, hurting network performance. Fixes bugs 696 and
1178 969. Bugfix on 0.2.0.6-alpha.
1181 - Serve the DirPortFrontPage page even when we have been approaching
1182 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
1183 - The control port would close the connection before flushing long
1184 replies, such as the network consensus, if a QUIT command was issued
1185 before the reply had completed. Now, the control port flushes all
1186 pending replies before closing the connection. Also fixed a spurious
1187 warning when a QUIT command is issued after a malformed or rejected
1188 AUTHENTICATE command, but before the connection was closed. Patch
1189 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
1190 - When we can't find an intro key for a v2 hidden service descriptor,
1191 fall back to the v0 hidden service descriptor and log a bug message.
1192 Workaround for bug 1024.
1193 - Fix a log message that did not respect the SafeLogging option.
1197 - If we're a relay and we change our IP address, be more verbose
1198 about the reason that made us change. Should help track down
1199 further bugs for relays on dynamic IP addresses.
1202 Changes in version 0.2.0.35 - 2009-06-24
1204 - Avoid crashing in the presence of certain malformed descriptors.
1205 Found by lark, and by automated fuzzing.
1206 - Fix an edge case where a malicious exit relay could convince a
1207 controller that the client's DNS question resolves to an internal IP
1208 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
1211 - Finally fix the bug where dynamic-IP relays disappear when their
1212 IP address changes: directory mirrors were mistakenly telling
1213 them their old address if they asked via begin_dir, so they
1214 never got an accurate answer about their new address, so they
1215 just vanished after a day. For belt-and-suspenders, relays that
1216 don't set Address in their config now avoid using begin_dir for
1217 all direct connections. Should fix bugs 827, 883, and 900.
1218 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
1219 that would occur on some exit nodes when DNS failures and timeouts
1220 occurred in certain patterns. Fix for bug 957.
1223 - When starting with a cache over a few days old, do not leak
1224 memory for the obsolete router descriptors in it. Bugfix on
1225 0.2.0.33; fixes bug 672.
1226 - Hidden service clients didn't use a cached service descriptor that
1227 was older than 15 minutes, but wouldn't fetch a new one either,
1228 because there was already one in the cache. Now, fetch a v2
1229 descriptor unless the same descriptor was added to the cache within
1230 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
1233 Changes in version 0.2.1.16-rc - 2009-06-20
1234 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
1235 a bunch of minor bugs.
1238 - Fix an edge case where a malicious exit relay could convince a
1239 controller that the client's DNS question resolves to an internal IP
1240 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
1242 o Major performance improvements (on 0.2.0.x):
1243 - Disable and refactor some debugging checks that forced a linear scan
1244 over the whole server-side DNS cache. These accounted for over 50%
1245 of CPU time on a relatively busy exit node's gprof profile. Found
1247 - Disable some debugging checks that appeared in exit node profile
1251 - Update to the "June 3 2009" ip-to-country file.
1252 - Do not have tor-resolve automatically refuse all .onion addresses;
1253 if AutomapHostsOnResolve is set in your torrc, this will work fine.
1255 o Minor bugfixes (on 0.2.0.x):
1256 - Log correct error messages for DNS-related network errors on
1258 - Fix a race condition that could cause crashes or memory corruption
1259 when running as a server with a controller listening for log
1261 - Avoid crashing when we have a policy specified in a DirPolicy or
1262 SocksPolicy or ReachableAddresses option with ports set on it,
1263 and we re-load the policy. May fix bug 996.
1264 - Hidden service clients didn't use a cached service descriptor that
1265 was older than 15 minutes, but wouldn't fetch a new one either,
1266 because there was already one in the cache. Now, fetch a v2
1267 descriptor unless the same descriptor was added to the cache within
1268 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
1270 o Minor bugfixes (on 0.2.1.x):
1271 - Don't warn users about low port and hibernation mix when they
1272 provide a *ListenAddress directive to fix that. Bugfix on
1274 - When switching back and forth between bridge mode, do not start
1275 gathering GeoIP data until two hours have passed.
1276 - Do not complain that the user has requested an excluded node as
1277 an exit when the node is not really an exit. This could happen
1278 because the circuit was for testing, or an introduction point.
1282 Changes in version 0.2.1.15-rc - 2009-05-25
1283 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
1284 series. It fixes a major bug on fast exit relays, as well as a variety
1287 o Major bugfixes (on 0.2.0.x):
1288 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
1289 that would occur on some exit nodes when DNS failures and timeouts
1290 occurred in certain patterns. Fix for bug 957.
1292 o Minor bugfixes (on 0.2.0.x):
1293 - Actually return -1 in the error case for read_bandwidth_usage().
1294 Harmless bug, since we currently don't care about the return value
1295 anywhere. Bugfix on 0.2.0.9-alpha.
1296 - Provide a more useful log message if bug 977 (related to buffer
1297 freelists) ever reappears, and do not crash right away.
1298 - Fix an assertion failure on 64-bit platforms when we allocated
1299 memory right up to the end of a memarea, then realigned the memory
1300 one step beyond the end. Fixes a possible cause of bug 930.
1301 - Protect the count of open sockets with a mutex, so we can't
1302 corrupt it when two threads are closing or opening sockets at once.
1303 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
1304 - Don't allow a bridge to publish its router descriptor to a
1305 non-bridge directory authority. Fixes part of bug 932.
1306 - When we change to or from being a bridge, reset our counts of
1307 client usage by country. Fixes bug 932.
1308 - Fix a bug that made stream bandwidth get misreported to the
1310 - Stop using malloc_usable_size() to use more area than we had
1311 actually allocated: it was safe, but made valgrind really unhappy.
1312 - Fix a memory leak when v3 directory authorities load their keys
1313 and cert from disk. Bugfix on 0.2.0.1-alpha.
1315 o Minor bugfixes (on 0.2.1.x):
1316 - Fix use of freed memory when deciding to mark a non-addable
1317 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
1320 Changes in version 0.2.1.14-rc - 2009-04-12
1321 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
1322 series. It begins fixing some major performance problems, and also
1323 finally addresses the bug that was causing relays on dynamic IP
1324 addresses to fall out of the directory.
1327 - Clients replace entry guards that were chosen more than a few months
1328 ago. This change should significantly improve client performance,
1329 especially once more people upgrade, since relays that have been
1330 a guard for a long time are currently overloaded.
1332 o Major bugfixes (on 0.2.0):
1333 - Finally fix the bug where dynamic-IP relays disappear when their
1334 IP address changes: directory mirrors were mistakenly telling
1335 them their old address if they asked via begin_dir, so they
1336 never got an accurate answer about their new address, so they
1337 just vanished after a day. For belt-and-suspenders, relays that
1338 don't set Address in their config now avoid using begin_dir for
1339 all direct connections. Should fix bugs 827, 883, and 900.
1340 - Relays were falling out of the networkstatus consensus for
1341 part of a day if they changed their local config but the
1342 authorities discarded their new descriptor as "not sufficiently
1343 different". Now directory authorities accept a descriptor as changed
1344 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
1346 - Avoid crashing in the presence of certain malformed descriptors.
1347 Found by lark, and by automated fuzzing.
1350 - When generating circuit events with verbose nicknames for
1351 controllers, try harder to look up nicknames for routers on a
1352 circuit. (Previously, we would look in the router descriptors we had
1353 for nicknames, but not in the consensus.) Partial fix for bug 941.
1354 - If the bridge config line doesn't specify a port, assume 443.
1355 This makes bridge lines a bit smaller and easier for users to
1357 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
1358 bytes (aka 20KB/s), to match our documentation. Also update
1359 directory authorities so they always assign the Fast flag to relays
1360 with 20KB/s of capacity. Now people running relays won't suddenly
1361 find themselves not seeing any use, if the network gets faster
1363 - Update to the "April 3 2009" ip-to-country file.
1366 - Avoid trying to print raw memory to the logs when we decide to
1367 give up on downloading a given relay descriptor. Bugfix on
1369 - In tor-resolve, when the Tor client to use is specified by
1370 <hostname>:<port>, actually use the specified port rather than
1371 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
1372 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
1373 - When starting with a cache over a few days old, do not leak
1374 memory for the obsolete router descriptors in it. Bugfix on
1376 - Avoid double-free on list of successfully uploaded hidden
1377 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
1378 - Change memarea_strndup() implementation to work even when
1379 duplicating a string at the end of a page. This bug was
1380 harmless for now, but could have meant crashes later. Fix by
1381 lark. Bugfix on 0.2.1.1-alpha.
1382 - Limit uploaded directory documents to be 16M rather than 500K.
1383 The directory authorities were refusing v3 consensus votes from
1384 other authorities, since the votes are now 504K. Fixes bug 959;
1385 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
1386 - Directory authorities should never send a 503 "busy" response to
1387 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
1391 Changes in version 0.2.1.13-alpha - 2009-03-09
1392 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
1393 cleanups. We're finally getting close to a release candidate.
1396 - Correctly update the list of which countries we exclude as
1397 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
1398 lark. Bugfix on 0.2.1.6-alpha.
1400 o Minor bugfixes (on 0.2.0.x and earlier):
1401 - Automatically detect MacOSX versions earlier than 10.4.0, and
1402 disable kqueue from inside Tor when running with these versions.
1403 We previously did this from the startup script, but that was no
1404 help to people who didn't use the startup script. Resolves bug 863.
1405 - When we had picked an exit node for a connection, but marked it as
1406 "optional", and it turned out we had no onion key for the exit,
1407 stop wanting that exit and try again. This situation may not
1408 be possible now, but will probably become feasible with proposal
1409 158. Spotted by rovv. Fixes another case of bug 752.
1410 - Clients no longer cache certificates for authorities they do not
1411 recognize. Bugfix on 0.2.0.9-alpha.
1412 - When we can't transmit a DNS request due to a network error, retry
1413 it after a while, and eventually transmit a failing response to
1414 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
1415 - If the controller claimed responsibility for a stream, but that
1416 stream never finished making its connection, it would live
1417 forever in circuit_wait state. Now we close it after SocksTimeout
1418 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
1419 - Drop begin cells to a hidden service if they come from the middle
1420 of a circuit. Patch from lark.
1421 - When we erroneously receive two EXTEND cells for the same circuit
1422 ID on the same connection, drop the second. Patch from lark.
1423 - Fix a crash that occurs on exit nodes when a nameserver request
1424 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
1425 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
1427 - Do not assume that a stack-allocated character array will be
1428 64-bit aligned on platforms that demand that uint64_t access is
1429 aligned. Possible fix for bug 604.
1430 - Parse dates and IPv4 addresses in a locale- and libc-independent
1431 manner, to avoid platform-dependent behavior on malformed input.
1432 - Build correctly when configured to build outside the main source
1433 path. Patch from Michael Gold.
1434 - We were already rejecting relay begin cells with destination port
1435 of 0. Now also reject extend cells with destination port or address
1436 of 0. Suggested by lark.
1438 o Minor bugfixes (on 0.2.1.x):
1439 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
1440 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
1441 - If we're an exit node, scrub the IP address to which we are exiting
1442 in the logs. Bugfix on 0.2.1.8-alpha.
1445 - On Linux, use the prctl call to re-enable core dumps when the user
1447 - New controller event NEWCONSENSUS that lists the networkstatus
1448 lines for every recommended relay. Now controllers like Torflow
1449 can keep up-to-date on which relays they should be using.
1450 - Update to the "February 26 2009" ip-to-country file.
1453 Changes in version 0.2.0.34 - 2009-02-08
1454 Tor 0.2.0.34 features several more security-related fixes. You should
1455 upgrade, especially if you run an exit relay (remote crash) or a
1456 directory authority (remote infinite loop), or you're on an older
1457 (pre-XP) or not-recently-patched Windows (remote exploit).
1459 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
1460 have many known flaws, and nobody should be using them. You should
1461 upgrade. If you're using a Linux or BSD and its packages are obsolete,
1462 stop using those packages and upgrade anyway.
1465 - Fix an infinite-loop bug on handling corrupt votes under certain
1466 circumstances. Bugfix on 0.2.0.8-alpha.
1467 - Fix a temporary DoS vulnerability that could be performed by
1468 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
1469 - Avoid a potential crash on exit nodes when processing malformed
1470 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
1471 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
1472 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
1475 - Fix compilation on systems where time_t is a 64-bit integer.
1476 Patch from Matthias Drochner.
1477 - Don't consider expiring already-closed client connections. Fixes
1478 bug 893. Bugfix on 0.0.2pre20.
1481 Changes in version 0.2.1.12-alpha - 2009-02-08
1482 Tor 0.2.1.12-alpha features several more security-related fixes. You
1483 should upgrade, especially if you run an exit relay (remote crash) or
1484 a directory authority (remote infinite loop), or you're on an older
1485 (pre-XP) or not-recently-patched Windows (remote exploit). It also
1486 includes a big pile of minor bugfixes and cleanups.
1489 - Fix an infinite-loop bug on handling corrupt votes under certain
1490 circumstances. Bugfix on 0.2.0.8-alpha.
1491 - Fix a temporary DoS vulnerability that could be performed by
1492 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
1493 - Avoid a potential crash on exit nodes when processing malformed
1494 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
1497 - Let controllers actually ask for the "clients_seen" event for
1498 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
1499 reported by Matt Edman.
1500 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
1502 - Fix a bug in address parsing that was preventing bridges or hidden
1503 service targets from being at IPv6 addresses.
1504 - Solve a bug that kept hardware crypto acceleration from getting
1505 enabled when accounting was turned on. Fixes bug 907. Bugfix on
1507 - Remove a bash-ism from configure.in to build properly on non-Linux
1508 platforms. Bugfix on 0.2.1.1-alpha.
1509 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
1510 headers. Bugfix on 0.2.0.10-alpha.
1511 - Don't consider expiring already-closed client connections. Fixes
1512 bug 893. Bugfix on 0.0.2pre20.
1513 - Fix another interesting corner-case of bug 891 spotted by rovv:
1514 Previously, if two hosts had different amounts of clock drift, and
1515 one of them created a new connection with just the wrong timing,
1516 the other might decide to deprecate the new connection erroneously.
1517 Bugfix on 0.1.1.13-alpha.
1518 - Resolve a very rare crash bug that could occur when the user forced
1519 a nameserver reconfiguration during the middle of a nameserver
1520 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
1521 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
1522 Bugfix on 0.2.1.7-alpha.
1523 - If we're using bridges and our network goes away, be more willing
1524 to forgive our bridges and try again when we get an application
1525 request. Bugfix on 0.2.0.x.
1528 - Support platforms where time_t is 64 bits long. (Congratulations,
1529 NetBSD!) Patch from Matthias Drochner.
1530 - Add a 'getinfo status/clients-seen' controller command, in case
1531 controllers want to hear clients_seen events but connect late.
1534 - Disable GCC's strict alias optimization by default, to avoid the
1535 likelihood of its introducing subtle bugs whenever our code violates
1536 the letter of C99's alias rules.
1539 Changes in version 0.2.0.33 - 2009-01-21
1540 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
1541 useful to users. It also finally fixes a bug where a relay or client
1542 that's been off for many days would take a long time to bootstrap.
1544 This update also fixes an important security-related bug reported by
1545 Ilja van Sprundel. You should upgrade. (We'll send out more details
1546 about the bug once people have had some time to upgrade.)
1549 - Fix a heap-corruption bug that may be remotely triggerable on
1550 some platforms. Reported by Ilja van Sprundel.
1553 - When a stream at an exit relay is in state "resolving" or
1554 "connecting" and it receives an "end" relay cell, the exit relay
1555 would silently ignore the end cell and not close the stream. If
1556 the client never closes the circuit, then the exit relay never
1557 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
1559 - When sending CREATED cells back for a given circuit, use a 64-bit
1560 connection ID to find the right connection, rather than an addr:port
1561 combination. Now that we can have multiple OR connections between
1562 the same ORs, it is no longer possible to use addr:port to uniquely
1563 identify a connection.
1564 - Bridge relays that had DirPort set to 0 would stop fetching
1565 descriptors shortly after startup, and then briefly resume
1566 after a new bandwidth test and/or after publishing a new bridge
1567 descriptor. Bridge users that try to bootstrap from them would
1568 get a recent networkstatus but would get descriptors from up to
1569 18 hours earlier, meaning most of the descriptors were obsolete
1570 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
1571 - Prevent bridge relays from serving their 'extrainfo' document
1572 to anybody who asks, now that extrainfo docs include potentially
1573 sensitive aggregated client geoip summaries. Bugfix on
1575 - If the cached networkstatus consensus is more than five days old,
1576 discard it rather than trying to use it. In theory it could be
1577 useful because it lists alternate directory mirrors, but in practice
1578 it just means we spend many minutes trying directory mirrors that
1579 are long gone from the network. Also discard router descriptors as
1580 we load them if they are more than five days old, since the onion
1581 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
1584 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
1585 could make gcc generate non-functional binary search code. Bugfix
1587 - Build correctly on platforms without socklen_t.
1588 - Compile without warnings on solaris.
1589 - Avoid potential crash on internal error during signature collection.
1590 Fixes bug 864. Patch from rovv.
1591 - Correct handling of possible malformed authority signing key
1592 certificates with internal signature types. Fixes bug 880.
1593 Bugfix on 0.2.0.3-alpha.
1594 - Fix a hard-to-trigger resource leak when logging credential status.
1596 - When we can't initialize DNS because the network is down, do not
1597 automatically stop Tor from starting. Instead, we retry failed
1598 dns_init() every 10 minutes, and change the exit policy to reject
1599 *:* until one succeeds. Fixes bug 691.
1600 - Use 64 bits instead of 32 bits for connection identifiers used with
1601 the controller protocol, to greatly reduce risk of identifier reuse.
1602 - When we're choosing an exit node for a circuit, and we have
1603 no pending streams, choose a good general exit rather than one that
1604 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
1605 - Fix another case of assuming, when a specific exit is requested,
1606 that we know more than the user about what hosts it allows.
1607 Fixes one case of bug 752. Patch from rovv.
1608 - Clip the MaxCircuitDirtiness config option to a minimum of 10
1609 seconds. Warn the user if lower values are given in the
1610 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
1611 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
1612 user if lower values are given in the configuration. Bugfix on
1613 0.1.1.17-rc. Patch by Sebastian.
1614 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
1615 the cache because we already had a v0 descriptor with the same ID.
1616 Bugfix on 0.2.0.18-alpha.
1617 - Fix a race condition when freeing keys shared between main thread
1618 and CPU workers that could result in a memory leak. Bugfix on
1619 0.1.0.1-rc. Fixes bug 889.
1620 - Send a valid END cell back when a client tries to connect to a
1621 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
1622 840. Patch from rovv.
1623 - Check which hops rendezvous stream cells are associated with to
1624 prevent possible guess-the-streamid injection attacks from
1625 intermediate hops. Fixes another case of bug 446. Based on patch
1627 - If a broken client asks a non-exit router to connect somewhere,
1628 do not even do the DNS lookup before rejecting the connection.
1629 Fixes another case of bug 619. Patch from rovv.
1630 - When a relay gets a create cell it can't decrypt (e.g. because it's
1631 using the wrong onion key), we were dropping it and letting the
1632 client time out. Now actually answer with a destroy cell. Fixes
1633 bug 904. Bugfix on 0.0.2pre8.
1635 o Minor bugfixes (hidden services):
1636 - Do not throw away existing introduction points on SIGHUP. Bugfix on
1637 0.0.6pre1. Patch by Karsten. Fixes bug 874.
1640 - Report the case where all signatures in a detached set are rejected
1641 differently than the case where there is an error handling the
1643 - When we realize that another process has modified our cached
1644 descriptors, print out a more useful error message rather than
1645 triggering an assertion. Fixes bug 885. Patch from Karsten.
1646 - Implement the 0x20 hack to better resist DNS poisoning: set the
1647 case on outgoing DNS requests randomly, and reject responses that do
1648 not match the case correctly. This logic can be disabled with the
1649 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
1650 of servers that do not reliably preserve case in replies. See
1651 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
1653 - Check DNS replies for more matching fields to better resist DNS
1655 - Never use OpenSSL compression: it wastes RAM and CPU trying to
1656 compress cells, which are basically all encrypted, compressed, or
1660 Changes in version 0.2.1.11-alpha - 2009-01-20
1661 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
1662 week it will take a long time to bootstrap again" bug. It also fixes
1663 an important security-related bug reported by Ilja van Sprundel. You
1664 should upgrade. (We'll send out more details about the bug once people
1665 have had some time to upgrade.)
1668 - Fix a heap-corruption bug that may be remotely triggerable on
1669 some platforms. Reported by Ilja van Sprundel.
1672 - Discard router descriptors as we load them if they are more than
1673 five days old. Otherwise if Tor is off for a long time and then
1674 starts with cached descriptors, it will try to use the onion
1675 keys in those obsolete descriptors when building circuits. Bugfix
1676 on 0.2.0.x. Fixes bug 887.
1679 - Try to make sure that the version of Libevent we're running with
1680 is binary-compatible with the one we built with. May address bug
1682 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
1683 for bug 905. Bugfix on 0.2.1.7-alpha.
1684 - Add a new --enable-local-appdata configuration switch to change
1685 the default location of the datadir on win32 from APPDATA to
1686 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
1687 entirely. Patch from coderman.
1690 - Make outbound DNS packets respect the OutboundBindAddress setting.
1691 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
1692 - When our circuit fails at the first hop (e.g. we get a destroy
1693 cell back), avoid using that OR connection anymore, and also
1694 tell all the one-hop directory requests waiting for it that they
1695 should fail. Bugfix on 0.2.1.3-alpha.
1696 - In the torify(1) manpage, mention that tsocks will leak your
1700 Changes in version 0.2.1.10-alpha - 2009-01-06
1701 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
1702 would make the bridge relay not so useful if it had DirPort set to 0,
1703 and one that could let an attacker learn a little bit of information
1704 about the bridge's users), and a bug that would cause your Tor relay
1705 to ignore a circuit create request it can't decrypt (rather than reply
1706 with an error). It also fixes a wide variety of other bugs.
1709 - If the cached networkstatus consensus is more than five days old,
1710 discard it rather than trying to use it. In theory it could
1711 be useful because it lists alternate directory mirrors, but in
1712 practice it just means we spend many minutes trying directory
1713 mirrors that are long gone from the network. Helps bug 887 a bit;
1715 - Bridge relays that had DirPort set to 0 would stop fetching
1716 descriptors shortly after startup, and then briefly resume
1717 after a new bandwidth test and/or after publishing a new bridge
1718 descriptor. Bridge users that try to bootstrap from them would
1719 get a recent networkstatus but would get descriptors from up to
1720 18 hours earlier, meaning most of the descriptors were obsolete
1721 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
1722 - Prevent bridge relays from serving their 'extrainfo' document
1723 to anybody who asks, now that extrainfo docs include potentially
1724 sensitive aggregated client geoip summaries. Bugfix on
1728 - New controller event "clients_seen" to report a geoip-based summary
1729 of which countries we've seen clients from recently. Now controllers
1730 like Vidalia can show bridge operators that they're actually making
1732 - Build correctly against versions of OpenSSL 0.9.8 or later built
1733 without support for deprecated functions.
1734 - Update to the "December 19 2008" ip-to-country file.
1736 o Minor bugfixes (on 0.2.0.x):
1737 - Authorities now vote for the Stable flag for any router whose
1738 weighted MTBF is at least 5 days, regardless of the mean MTBF.
1739 - Do not remove routers as too old if we do not have any consensus
1740 document. Bugfix on 0.2.0.7-alpha.
1741 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
1742 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
1743 - When an exit relay resolves a stream address to a local IP address,
1744 do not just keep retrying that same exit relay over and
1745 over. Instead, just close the stream. Addresses bug 872. Bugfix
1746 on 0.2.0.32. Patch from rovv.
1747 - If a hidden service sends us an END cell, do not consider
1748 retrying the connection; just close it. Patch from rovv.
1749 - When we made bridge authorities stop serving bridge descriptors over
1750 unencrypted links, we also broke DirPort reachability testing for
1751 bridges. So bridges with a non-zero DirPort were printing spurious
1752 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
1753 - When a relay gets a create cell it can't decrypt (e.g. because it's
1754 using the wrong onion key), we were dropping it and letting the
1755 client time out. Now actually answer with a destroy cell. Fixes
1756 bug 904. Bugfix on 0.0.2pre8.
1757 - Squeeze 2-5% out of client performance (according to oprofile) by
1758 improving the implementation of some policy-manipulation functions.
1760 o Minor bugfixes (on 0.2.1.x):
1761 - Make get_interface_address() function work properly again; stop
1762 guessing the wrong parts of our address as our address.
1763 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
1764 send on that circuit. Otherwise we might violate the proposal-110
1765 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
1767 - When we're sending non-EXTEND cells to the first hop in a circuit,
1768 for example to use an encrypted directory connection, we don't need
1769 to use RELAY_EARLY cells: the first hop knows what kind of cell
1770 it is, and nobody else can even see the cell type. Conserving
1771 RELAY_EARLY cells makes it easier to cannibalize circuits like
1773 - Stop logging nameserver addresses in reverse order.
1774 - If we are retrying a directory download slowly over and over, do
1775 not automatically give up after the 254th failure. Bugfix on
1777 - Resume reporting accurate "stream end" reasons to the local control
1778 port. They were lost in the changes for Proposal 148. Bugfix on
1781 o Deprecated and removed features:
1782 - The old "tor --version --version" command, which would print out
1783 the subversion "Id" of most of the source files, is now removed. It
1784 turned out to be less useful than we'd expected, and harder to
1787 o Code simplifications and refactoring:
1788 - Change our header file guard macros to be less likely to conflict
1789 with system headers. Adam Langley noticed that we were conflicting
1790 with log.h on Android.
1791 - Tool-assisted documentation cleanup. Nearly every function or
1792 static variable in Tor should have its own documentation now.
1795 Changes in version 0.2.1.9-alpha - 2008-12-25
1796 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
1798 o New directory authorities:
1799 - gabelmoo (the authority run by Karsten Loesing) now has a new
1803 - Never use a connection with a mismatched address to extend a
1804 circuit, unless that connection is canonical. A canonical
1805 connection is one whose address is authenticated by the router's
1806 identity key, either in a NETINFO cell or in a router descriptor.
1807 - Avoid a possible memory corruption bug when receiving hidden service
1808 descriptors. Bugfix on 0.2.1.6-alpha.
1811 - Fix a logic error that would automatically reject all but the first
1812 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
1813 part of bug 813/868. Bug spotted by coderman.
1814 - When a stream at an exit relay is in state "resolving" or
1815 "connecting" and it receives an "end" relay cell, the exit relay
1816 would silently ignore the end cell and not close the stream. If
1817 the client never closes the circuit, then the exit relay never
1818 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
1820 - When we can't initialize DNS because the network is down, do not
1821 automatically stop Tor from starting. Instead, retry failed
1822 dns_init() every 10 minutes, and change the exit policy to reject
1823 *:* until one succeeds. Fixes bug 691.
1826 - Give a better error message when an overzealous init script says
1827 "sudo -u username tor --user username". Makes Bug 882 easier for
1829 - When a directory authority gives us a new guess for our IP address,
1830 log which authority we used. Hopefully this will help us debug
1831 the recent complaints about bad IP address guesses.
1832 - Detect svn revision properly when we're using git-svn.
1833 - Try not to open more than one descriptor-downloading connection
1834 to an authority at once. This should reduce load on directory
1835 authorities. Fixes bug 366.
1836 - Add cross-certification to newly generated certificates, so that
1837 a signing key is enough information to look up a certificate.
1838 Partial implementation of proposal 157.
1839 - Start serving certificates by <identity digest, signing key digest>
1840 pairs. Partial implementation of proposal 157.
1841 - Clients now never report any stream end reason except 'MISC'.
1842 Implements proposal 148.
1843 - On platforms with a maximum syslog string length, truncate syslog
1844 messages to that length ourselves, rather than relying on the
1845 system to do it for us.
1846 - Optimize out calls to time(NULL) that occur for every IO operation,
1847 or for every cell. On systems where time() is a slow syscall,
1848 this fix will be slightly helpful.
1849 - Exit servers can now answer resolve requests for ip6.arpa addresses.
1850 - When we download a descriptor that we then immediately (as
1851 a directory authority) reject, do not retry downloading it right
1852 away. Should save some bandwidth on authorities. Fix for bug
1853 888. Patch by Sebastian Hahn.
1854 - When a download gets us zero good descriptors, do not notify
1855 Tor that new directory information has arrived.
1856 - Avoid some nasty corner cases in the logic for marking connections
1857 as too old or obsolete or noncanonical for circuits. Partial
1860 o Minor features (controller):
1861 - New CONSENSUS_ARRIVED event to note when a new consensus has
1862 been fetched and validated.
1863 - When we realize that another process has modified our cached
1864 descriptors file, print out a more useful error message rather
1865 than triggering an assertion. Fixes bug 885. Patch from Karsten.
1866 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
1867 controllers to prevent SIGHUP from reloading the
1868 configuration. Fixes bug 856.
1871 - Resume using the correct "REASON=" stream when telling the
1872 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
1873 - When a canonical connection appears later in our internal list
1874 than a noncanonical one for a given OR ID, always use the
1875 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
1877 - Clip the MaxCircuitDirtiness config option to a minimum of 10
1878 seconds. Warn the user if lower values are given in the
1879 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
1880 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
1881 user if lower values are given in the configuration. Bugfix on
1882 0.1.1.17-rc. Patch by Sebastian.
1883 - Fix a race condition when freeing keys shared between main thread
1884 and CPU workers that could result in a memory leak. Bugfix on
1885 0.1.0.1-rc. Fixes bug 889.
1887 o Minor bugfixes (hidden services):
1888 - Do not throw away existing introduction points on SIGHUP (bugfix on
1889 0.0.6pre1); also, do not stall hidden services because we're
1890 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
1891 by John Brooks. Patch by Karsten. Fixes bug 874.
1892 - Fix a memory leak when we decline to add a v2 rendezvous
1893 descriptor to the cache because we already had a v0 descriptor
1894 with the same ID. Bugfix on 0.2.0.18-alpha.
1896 o Deprecated and removed features:
1897 - RedirectExits has been removed. It was deprecated since
1899 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
1900 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
1901 - Cell pools are now always enabled; --disable-cell-pools is ignored.
1903 o Code simplifications and refactoring:
1904 - Rename the confusing or_is_obsolete field to the more appropriate
1905 is_bad_for_new_circs, and move it to or_connection_t where it
1907 - Move edge-only flags from connection_t to edge_connection_t: not
1908 only is this better coding, but on machines of plausible alignment,
1909 it should save 4-8 bytes per connection_t. "Every little bit helps."
1910 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
1911 for consistency; keep old option working for backward compatibility.
1912 - Simplify the code for finding connections to use for a circuit.
1915 Changes in version 0.2.1.8-alpha - 2008-12-08
1916 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
1917 builds better on unusual platforms like Solaris and old OS X, and
1918 fixes a variety of other issues.
1921 - New DirPortFrontPage option that takes an html file and publishes
1922 it as "/" on the DirPort. Now relay operators can provide a
1923 disclaimer without needing to set up a separate webserver. There's
1924 a sample disclaimer in contrib/tor-exit-notice.html.
1927 - When the client is choosing entry guards, now it selects at most
1928 one guard from a given relay family. Otherwise we could end up with
1929 all of our entry points into the network run by the same operator.
1930 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
1933 - Fix a DOS opportunity during the voting signature collection process
1934 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
1935 - Fix a possible segfault when establishing an exit connection. Bugfix
1939 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
1941 - Made Tor a little less aggressive about deleting expired
1942 certificates. Partial fix for bug 854.
1943 - Stop doing unaligned memory access that generated bus errors on
1944 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
1945 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
1946 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
1947 - Make USR2 log-level switch take effect immediately. Bugfix on
1949 - If one win32 nameserver fails to get added, continue adding the
1950 rest, and don't automatically fail.
1951 - Use fcntl() for locking when flock() is not available. Should fix
1952 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
1953 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
1954 could make gcc generate non-functional binary search code. Bugfix
1956 - Build correctly on platforms without socklen_t.
1957 - Avoid potential crash on internal error during signature collection.
1958 Fixes bug 864. Patch from rovv.
1959 - Do not use C's stdio library for writing to log files. This will
1960 improve logging performance by a minute amount, and will stop
1961 leaking fds when our disk is full. Fixes bug 861.
1962 - Stop erroneous use of O_APPEND in cases where we did not in fact
1963 want to re-seek to the end of a file before every last write().
1964 - Correct handling of possible malformed authority signing key
1965 certificates with internal signature types. Fixes bug 880. Bugfix
1967 - Fix a hard-to-trigger resource leak when logging credential status.
1971 - Directory mirrors no longer fetch the v1 directory or
1972 running-routers files. They are obsolete, and nobody asks for them
1973 anymore. This is the first step to making v1 authorities obsolete.
1975 o Minor features (controller):
1976 - Return circuit purposes in response to GETINFO circuit-status. Fixes
1980 Changes in version 0.2.0.32 - 2008-11-20
1981 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
1982 packages (and maybe other packages) noticed by Theo de Raadt, fixes
1983 a smaller security flaw that might allow an attacker to access local
1984 services, further improves hidden service performance, and fixes a
1985 variety of other issues.
1988 - The "User" and "Group" config options did not clear the
1989 supplementary group entries for the Tor process. The "User" option
1990 is now more robust, and we now set the groups to the specified
1991 user's primary group. The "Group" option is now ignored. For more
1992 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
1993 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
1994 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
1995 - The "ClientDNSRejectInternalAddresses" config option wasn't being
1996 consistently obeyed: if an exit relay refuses a stream because its
1997 exit policy doesn't allow it, we would remember what IP address
1998 the relay said the destination address resolves to, even if it's
1999 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
2002 - Fix a DOS opportunity during the voting signature collection process
2003 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
2005 o Major bugfixes (hidden services):
2006 - When fetching v0 and v2 rendezvous service descriptors in parallel,
2007 we were failing the whole hidden service request when the v0
2008 descriptor fetch fails, even if the v2 fetch is still pending and
2009 might succeed. Similarly, if the last v2 fetch fails, we were
2010 failing the whole hidden service request even if a v0 fetch is
2011 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
2012 - When extending a circuit to a hidden service directory to upload a
2013 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
2014 requests failed, because the router descriptor has not been
2015 downloaded yet. In these cases, do not attempt to upload the
2016 rendezvous descriptor, but wait until the router descriptor is
2017 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
2018 descriptor from a hidden service directory for which the router
2019 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
2023 - Fix several infrequent memory leaks spotted by Coverity.
2024 - When testing for libevent functions, set the LDFLAGS variable
2025 correctly. Found by Riastradh.
2026 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
2027 bootstrapping with tunneled directory connections. Bugfix on
2028 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
2029 - When asked to connect to A.B.exit:80, if we don't know the IP for A
2030 and we know that server B rejects most-but-not all connections to
2031 port 80, we would previously reject the connection. Now, we assume
2032 the user knows what they were asking for. Fixes bug 752. Bugfix
2033 on 0.0.9rc5. Diagnosed by BarkerJr.
2034 - If we overrun our per-second write limits a little, count this as
2035 having used up our write allocation for the second, and choke
2036 outgoing directory writes. Previously, we had only counted this when
2037 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
2038 Bugfix on 0.2.0.x (??).
2039 - Remove the old v2 directory authority 'lefkada' from the default
2040 list. It has been gone for many months.
2041 - Stop doing unaligned memory access that generated bus errors on
2042 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
2043 - Make USR2 log-level switch take effect immediately. Bugfix on
2046 o Minor bugfixes (controller):
2047 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
2048 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
2051 Changes in version 0.2.1.7-alpha - 2008-11-08
2052 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
2053 packages (and maybe other packages) noticed by Theo de Raadt, fixes
2054 a smaller security flaw that might allow an attacker to access local
2055 services, adds better defense against DNS poisoning attacks on exit
2056 relays, further improves hidden service performance, and fixes a
2057 variety of other issues.
2060 - The "ClientDNSRejectInternalAddresses" config option wasn't being
2061 consistently obeyed: if an exit relay refuses a stream because its
2062 exit policy doesn't allow it, we would remember what IP address
2063 the relay said the destination address resolves to, even if it's
2064 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
2065 - The "User" and "Group" config options did not clear the
2066 supplementary group entries for the Tor process. The "User" option
2067 is now more robust, and we now set the groups to the specified
2068 user's primary group. The "Group" option is now ignored. For more
2069 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
2070 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
2071 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
2072 - Do not use or believe expired v3 authority certificates. Patch
2073 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
2076 - Now NodeFamily and MyFamily config options allow spaces in
2077 identity fingerprints, so it's easier to paste them in.
2078 Suggested by Lucky Green.
2079 - Implement the 0x20 hack to better resist DNS poisoning: set the
2080 case on outgoing DNS requests randomly, and reject responses that do
2081 not match the case correctly. This logic can be disabled with the
2082 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
2083 of servers that do not reliably preserve case in replies. See
2084 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
2086 - Preserve case in replies to DNSPort requests in order to support
2087 the 0x20 hack for resisting DNS poisoning attacks.
2089 o Hidden service performance improvements:
2090 - When the client launches an introduction circuit, retry with a
2091 new circuit after 30 seconds rather than 60 seconds.
2092 - Launch a second client-side introduction circuit in parallel
2093 after a delay of 15 seconds (based on work by Christian Wilms).
2094 - Hidden services start out building five intro circuits rather
2095 than three, and when the first three finish they publish a service
2096 descriptor using those. Now we publish our service descriptor much
2097 faster after restart.
2100 - Minor fix in the warning messages when you're having problems
2101 bootstrapping; also, be more forgiving of bootstrap problems when
2102 we're still making incremental progress on a given bootstrap phase.
2103 - When we're choosing an exit node for a circuit, and we have
2104 no pending streams, choose a good general exit rather than one that
2105 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
2106 - Send a valid END cell back when a client tries to connect to a
2107 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
2108 840. Patch from rovv.
2109 - If a broken client asks a non-exit router to connect somewhere,
2110 do not even do the DNS lookup before rejecting the connection.
2111 Fixes another case of bug 619. Patch from rovv.
2112 - Fix another case of assuming, when a specific exit is requested,
2113 that we know more than the user about what hosts it allows.
2114 Fixes another case of bug 752. Patch from rovv.
2115 - Check which hops rendezvous stream cells are associated with to
2116 prevent possible guess-the-streamid injection attacks from
2117 intermediate hops. Fixes another case of bug 446. Based on patch
2119 - Avoid using a negative right-shift when comparing 32-bit
2120 addresses. Possible fix for bug 845 and bug 811.
2121 - Make the assert_circuit_ok() function work correctly on circuits that
2122 have already been marked for close.
2123 - Fix read-off-the-end-of-string error in unit tests when decoding
2124 introduction points.
2125 - Fix uninitialized size field for memory area allocation: may improve
2126 memory performance during directory parsing.
2127 - Treat duplicate certificate fetches as failures, so that we do
2128 not try to re-fetch an expired certificate over and over and over.
2129 - Do not say we're fetching a certificate when we'll in fact skip it
2130 because of a pending download.
2133 Changes in version 0.2.1.6-alpha - 2008-09-30
2134 Tor 0.2.1.6-alpha further improves performance and robustness of
2135 hidden services, starts work on supporting per-country relay selection,
2136 and fixes a variety of smaller issues.
2139 - Implement proposal 121: make it possible to build hidden services
2140 that only certain clients are allowed to connect to. This is
2141 enforced at several points, so that unauthorized clients are unable
2142 to send INTRODUCE cells to the service, or even (depending on the
2143 type of authentication) to learn introduction points. This feature
2144 raises the bar for certain kinds of active attacks against hidden
2145 services. Code by Karsten Loesing.
2146 - Relays now store and serve v2 hidden service descriptors by default,
2147 i.e., the new default value for HidServDirectoryV2 is 1. This is
2148 the last step in proposal 114, which aims to make hidden service
2149 lookups more reliable.
2150 - Start work to allow node restrictions to include country codes. The
2151 syntax to exclude nodes in a country with country code XX is
2152 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
2153 refinement to decide what config options should take priority if
2154 you ask to both use a particular node and exclude it.
2155 - Allow ExitNodes list to include IP ranges and country codes, just
2156 like the Exclude*Nodes lists. Patch from Robert Hogan.
2159 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
2160 Tor to fail to start if you had it configured to use a bridge
2161 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
2162 - When extending a circuit to a hidden service directory to upload a
2163 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
2164 requests failed, because the router descriptor had not been
2165 downloaded yet. In these cases, we now wait until the router
2166 descriptor is downloaded, and then retry. Likewise, clients
2167 now skip over a hidden service directory if they don't yet have
2168 its router descriptor, rather than futilely requesting it and
2169 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
2171 - When fetching v0 and v2 rendezvous service descriptors in parallel,
2172 we were failing the whole hidden service request when the v0
2173 descriptor fetch fails, even if the v2 fetch is still pending and
2174 might succeed. Similarly, if the last v2 fetch fails, we were
2175 failing the whole hidden service request even if a v0 fetch is
2176 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
2177 - DNS replies need to have names matching their requests, but
2178 these names should be in the questions section, not necessarily
2179 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
2182 - Update to the "September 1 2008" ip-to-country file.
2183 - Allow ports 465 and 587 in the default exit policy again. We had
2184 rejected them in 0.1.0.15, because back in 2005 they were commonly
2185 misconfigured and ended up as spam targets. We hear they are better
2186 locked down these days.
2187 - Use a lockfile to make sure that two Tor processes are not
2188 simultaneously running with the same datadir.
2189 - Serve the latest v3 networkstatus consensus via the control
2190 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
2191 - Better logging about stability/reliability calculations on directory
2193 - Drop the requirement to have an open dir port for storing and
2194 serving v2 hidden service descriptors.
2195 - Directory authorities now serve a /tor/dbg-stability.txt URL to
2196 help debug WFU and MTBF calculations.
2197 - Implement most of Proposal 152: allow specialized servers to permit
2198 single-hop circuits, and clients to use those servers to build
2199 single-hop circuits when using a specialized controller. Patch
2200 from Josh Albrecht. Resolves feature request 768.
2201 - Add a -p option to tor-resolve for specifying the SOCKS port: some
2202 people find host:port too confusing.
2203 - Make TrackHostExit mappings expire a while after their last use, not
2204 after their creation. Patch from Robert Hogan.
2205 - Provide circuit purposes along with circuit events to the controller.
2208 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
2210 - Fixed some memory leaks -- some quite frequent, some almost
2211 impossible to trigger -- based on results from Coverity.
2212 - When testing for libevent functions, set the LDFLAGS variable
2213 correctly. Found by Riastradh.
2214 - Fix an assertion bug in parsing policy-related options; possible fix
2216 - Catch and report a few more bootstrapping failure cases when Tor
2217 fails to establish a TCP connection. Cleanup on 0.2.1.x.
2218 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
2219 bootstrapping with tunneled directory connections. Bugfix on
2220 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
2221 - When asked to connect to A.B.exit:80, if we don't know the IP for A
2222 and we know that server B rejects most-but-not all connections to
2223 port 80, we would previously reject the connection. Now, we assume
2224 the user knows what they were asking for. Fixes bug 752. Bugfix
2225 on 0.0.9rc5. Diagnosed by BarkerJr.
2226 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
2227 service directories if they have no advertised dir port. Bugfix
2229 - If we overrun our per-second write limits a little, count this as
2230 having used up our write allocation for the second, and choke
2231 outgoing directory writes. Previously, we had only counted this when
2232 we had met our limits precisely. Fixes bug 824. Patch by rovv.
2233 Bugfix on 0.2.0.x (??).
2234 - Avoid a "0 divided by 0" calculation when calculating router uptime
2235 at directory authorities. Bugfix on 0.2.0.8-alpha.
2236 - Make DNS resolved controller events into "CLOSED", not
2237 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
2239 - Fix a bug where an unreachable relay would establish enough
2240 reachability testing circuits to do a bandwidth test -- if
2241 we already have a connection to the middle hop of the testing
2242 circuit, then it could establish the last hop by using the existing
2243 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
2244 circuits no longer use entry guards in 0.2.1.3-alpha.
2245 - If we have correct permissions on $datadir, we complain to stdout
2246 and fail to start. But dangerous permissions on
2247 $datadir/cached-status/ would cause us to open a log and complain
2248 there. Now complain to stdout and fail to start in both cases. Fixes
2249 bug 820, reported by seeess.
2250 - Remove the old v2 directory authority 'lefkada' from the default
2251 list. It has been gone for many months.
2253 o Code simplifications and refactoring:
2254 - Revise the connection_new functions so that a more typesafe variant
2255 exists. This will work better with Coverity, and let us find any
2256 actual mistakes we're making here.
2257 - Refactor unit testing logic so that dmalloc can be used sensibly
2258 with unit tests to check for memory leaks.
2259 - Move all hidden-service related fields from connection and circuit
2260 structure to substructures: this way they won't eat so much memory.
2263 Changes in version 0.2.0.31 - 2008-09-03
2264 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
2265 a big bug we're seeing where in rare cases traffic from one Tor stream
2266 gets mixed into another stream, and fixes a variety of smaller issues.
2269 - Make sure that two circuits can never exist on the same connection
2270 with the same circuit ID, even if one is marked for close. This
2271 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
2272 - Relays now reject risky extend cells: if the extend cell includes
2273 a digest of all zeroes, or asks to extend back to the relay that
2274 sent the extend cell, tear down the circuit. Ideas suggested
2276 - If not enough of our entry guards are available so we add a new
2277 one, we might use the new one even if it overlapped with the
2278 current circuit's exit relay (or its family). Anonymity bugfix
2279 pointed out by rovv.
2282 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
2283 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
2284 - Correctly detect the presence of the linux/netfilter_ipv4.h header
2285 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
2286 - Pick size of default geoip filename string correctly on windows.
2287 Fixes bug 806. Bugfix on 0.2.0.30.
2288 - Make the autoconf script accept the obsolete --with-ssl-dir
2289 option as an alias for the actually-working --with-openssl-dir
2290 option. Fix the help documentation to recommend --with-openssl-dir.
2291 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
2292 - When using the TransPort option on OpenBSD, and using the User
2293 option to change UID and drop privileges, make sure to open
2294 /dev/pf before dropping privileges. Fixes bug 782. Patch from
2295 Christopher Davis. Bugfix on 0.1.2.1-alpha.
2296 - Try to attach connections immediately upon receiving a RENDEZVOUS2
2297 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
2298 on the client side when connecting to a hidden service. Bugfix
2299 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
2300 - When closing an application-side connection because its circuit is
2301 getting torn down, generate the stream event correctly. Bugfix on
2302 0.1.2.x. Anonymous patch.
2305 Changes in version 0.2.1.5-alpha - 2008-08-31
2306 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
2307 in a lot of the infrastructure for adding authorization to hidden
2308 services, lays the groundwork for having clients read their load
2309 balancing information out of the networkstatus consensus rather than
2310 the individual router descriptors, addresses two potential anonymity
2311 issues, and fixes a variety of smaller issues.
2314 - Convert many internal address representations to optionally hold
2316 - Generate and accept IPv6 addresses in many protocol elements.
2317 - Make resolver code handle nameservers located at ipv6 addresses.
2318 - Begin implementation of proposal 121 ("Client authorization for
2319 hidden services"): configure hidden services with client
2320 authorization, publish descriptors for them, and configure
2321 authorization data for hidden services at clients. The next
2322 step is to actually access hidden services that perform client
2324 - More progress toward proposal 141: Network status consensus
2325 documents and votes now contain bandwidth information for each
2326 router and a summary of that router's exit policy. Eventually this
2327 will be used by clients so that they do not have to download every
2328 known descriptor before building circuits.
2330 o Major bugfixes (on 0.2.0.x and before):
2331 - When sending CREATED cells back for a given circuit, use a 64-bit
2332 connection ID to find the right connection, rather than an addr:port
2333 combination. Now that we can have multiple OR connections between
2334 the same ORs, it is no longer possible to use addr:port to uniquely
2335 identify a connection.
2336 - Relays now reject risky extend cells: if the extend cell includes
2337 a digest of all zeroes, or asks to extend back to the relay that
2338 sent the extend cell, tear down the circuit. Ideas suggested
2340 - If not enough of our entry guards are available so we add a new
2341 one, we might use the new one even if it overlapped with the
2342 current circuit's exit relay (or its family). Anonymity bugfix
2343 pointed out by rovv.
2346 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
2347 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
2348 - When using the TransPort option on OpenBSD, and using the User
2349 option to change UID and drop privileges, make sure to open /dev/pf
2350 before dropping privileges. Fixes bug 782. Patch from Christopher
2351 Davis. Bugfix on 0.1.2.1-alpha.
2352 - Correctly detect the presence of the linux/netfilter_ipv4.h header
2353 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
2354 - Add a missing safe_str() call for a debug log message.
2355 - Use 64 bits instead of 32 bits for connection identifiers used with
2356 the controller protocol, to greatly reduce risk of identifier reuse.
2357 - Make the autoconf script accept the obsolete --with-ssl-dir
2358 option as an alias for the actually-working --with-openssl-dir
2359 option. Fix the help documentation to recommend --with-openssl-dir.
2360 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
2363 - Rate-limit too-many-sockets messages: when they happen, they happen
2364 a lot. Resolves bug 748.
2365 - Resist DNS poisoning a little better by making sure that names in
2366 answer sections match.
2367 - Print the SOCKS5 error message string as well as the error code
2368 when a tor-resolve request fails. Patch from Jacob.
2371 Changes in version 0.2.1.4-alpha - 2008-08-04
2372 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
2375 - The address part of exit policies was not correctly written
2376 to router descriptors. This generated router descriptors that failed
2377 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
2379 - Tor triggered a false assert when extending a circuit to a relay
2380 but we already have a connection open to that relay. Noticed by
2381 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
2384 - Fix a hidden service logging bug: in some edge cases, the router
2385 descriptor of a previously picked introduction point becomes
2386 obsolete and we need to give up on it rather than continually
2387 complaining that it has become obsolete. Observed by xiando. Bugfix
2391 - Take out the TestVia config option, since it was a workaround for
2392 a bug that was fixed in Tor 0.1.1.21.
2395 Changes in version 0.2.1.3-alpha - 2008-08-03
2396 Tor 0.2.1.3-alpha implements most of the pieces to prevent
2397 infinite-length circuit attacks (see proposal 110); fixes a bug that
2398 might cause exit relays to corrupt streams they send back; allows
2399 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
2400 ExcludeExitNodes config options; and fixes a big pile of bugs.
2402 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
2403 - Send a bootstrap problem "warn" event on the first problem if the
2404 reason is NO_ROUTE (that is, our network is down).
2407 - Implement most of proposal 110: The first K cells to be sent
2408 along a circuit are marked as special "early" cells; only K "early"
2409 cells will be allowed. Once this code is universal, we can block
2410 certain kinds of DOS attack by requiring that EXTEND commands must
2411 be sent using an "early" cell.
2414 - Try to attach connections immediately upon receiving a RENDEZVOUS2
2415 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
2416 on the client side when connecting to a hidden service. Bugfix
2417 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
2418 - Ensure that two circuits can never exist on the same connection
2419 with the same circuit ID, even if one is marked for close. This
2420 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
2423 - When relays do their initial bandwidth measurement, don't limit
2424 to just our entry guards for the test circuits. Otherwise we tend
2425 to have multiple test circuits going through a single entry guard,
2426 which makes our bandwidth test less accurate. Fixes part of bug 654;
2427 patch contributed by Josh Albrecht.
2428 - Add an ExcludeExitNodes option so users can list a set of nodes
2429 that should be be excluded from the exit node position, but
2430 allowed elsewhere. Implements proposal 151.
2431 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
2432 ExcludeNodes and ExcludeExitNodes lists.
2433 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
2434 be more efficient. Formerly it was quadratic in the number of
2435 servers; now it should be linear. Fixes bug 509.
2436 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
2437 and n_conn_id_digest fields into a separate structure that's
2438 only needed when the circuit has not yet attached to an n_conn.
2441 - Change the contrib/tor.logrotate script so it makes the new
2442 logs as "_tor:_tor" rather than the default, which is generally
2443 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
2444 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
2445 warnings (occasionally), but it can also cause the compiler to
2446 eliminate error-checking code. Suggested by Peter Gutmann.
2447 - When a hidden service is giving up on an introduction point candidate
2448 that was not included in the last published rendezvous descriptor,
2449 don't reschedule publication of the next descriptor. Fixes bug 763.
2451 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
2452 HiddenServiceExcludeNodes as obsolete: they never worked properly,
2453 and nobody claims to be using them. Fixes bug 754. Bugfix on
2454 0.1.0.1-rc. Patch from Christian Wilms.
2455 - Fix a small alignment and memory-wasting bug on buffer chunks.
2458 o Minor bugfixes (controller):
2459 - When closing an application-side connection because its circuit
2460 is getting torn down, generate the stream event correctly.
2461 Bugfix on 0.1.2.x. Anonymous patch.
2464 - Remove all backward-compatibility code to support relays running
2465 versions of Tor so old that they no longer work at all on the
2469 Changes in version 0.2.0.30 - 2008-07-15
2471 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
2472 warnings (occasionally), but it can also cause the compiler to
2473 eliminate error-checking code. Suggested by Peter Gutmann.
2476 Changes in version 0.2.0.29-rc - 2008-07-08
2477 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
2478 hidden-service performance bugs, and fixes a bunch of smaller bugs.
2481 - If you have more than one bridge but don't know their keys,
2482 you would only launch a request for the descriptor of the first one
2483 on your list. (Tor considered launching requests for the others, but
2484 found that it already had a connection on the way for $0000...0000
2485 so it didn't open another.) Bugfix on 0.2.0.x.
2486 - If you have more than one bridge but don't know their keys, and the
2487 connection to one of the bridges failed, you would cancel all
2488 pending bridge connections. (After all, they all have the same
2489 digest.) Bugfix on 0.2.0.x.
2490 - When a hidden service was trying to establish an introduction point,
2491 and Tor had built circuits preemptively for such purposes, we
2492 were ignoring all the preemptive circuits and launching a new one
2493 instead. Bugfix on 0.2.0.14-alpha.
2494 - When a hidden service was trying to establish an introduction point,
2495 and Tor *did* manage to reuse one of the preemptively built
2496 circuits, it didn't correctly remember which one it used,
2497 so it asked for another one soon after, until there were no
2498 more preemptive circuits, at which point it launched one from
2499 scratch. Bugfix on 0.0.9.x.
2500 - Make directory servers include the X-Your-Address-Is: http header in
2501 their responses even for begin_dir conns. Now clients who only
2502 ever use begin_dir connections still have a way to learn their IP
2503 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
2506 - Fix a macro/CPP interaction that was confusing some compilers:
2507 some GCCs don't like #if/#endif pairs inside macro arguments.
2509 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
2510 Fixes bug 704; fix from Steven Murdoch.
2511 - When opening /dev/null in finish_daemonize(), do not pass the
2512 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
2513 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
2514 - Correctly detect transparent proxy support on Linux hosts that
2515 require in.h to be included before netfilter_ipv4.h. Patch
2517 - Disallow session resumption attempts during the renegotiation
2518 stage of the v2 handshake protocol. Clients should never be trying
2519 session resumption at this point, but apparently some did, in
2520 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
2521 found by Geoff Goodell.
2524 Changes in version 0.2.1.2-alpha - 2008-06-20
2525 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
2526 make it easier to set up your own private Tor network; fixes several
2527 big bugs with using more than one bridge relay; fixes a big bug with
2528 offering hidden services quickly after Tor starts; and uses a better
2529 API for reporting potential bootstrapping problems to the controller.
2532 - New TestingTorNetwork config option to allow adjustment of
2533 previously constant values that, while reasonable, could slow
2534 bootstrapping. Implements proposal 135. Patch from Karsten.
2537 - If you have more than one bridge but don't know their digests,
2538 you would only learn a request for the descriptor of the first one
2539 on your list. (Tor considered launching requests for the others, but
2540 found that it already had a connection on the way for $0000...0000
2541 so it didn't open another.) Bugfix on 0.2.0.x.
2542 - If you have more than one bridge but don't know their digests,
2543 and the connection to one of the bridges failed, you would cancel
2544 all pending bridge connections. (After all, they all have the
2545 same digest.) Bugfix on 0.2.0.x.
2546 - When establishing a hidden service, introduction points that
2547 originate from cannibalized circuits are completely ignored and not
2548 included in rendezvous service descriptors. This might be another
2549 reason for delay in making a hidden service available. Bugfix
2550 from long ago (0.0.9.x?)
2553 - Allow OpenSSL to use dynamic locks if it wants.
2554 - When building a consensus, do not include routers that are down.
2555 This will cut down 30% to 40% on consensus size. Implements
2557 - In directory authorities' approved-routers files, allow
2558 fingerprints with or without space.
2559 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
2560 controller can query our current bootstrap state in case it attaches
2561 partway through and wants to catch up.
2562 - Send an initial "Starting" bootstrap status event, so we have a
2563 state to start out in.
2566 - Asking for a conditional consensus at .../consensus/<fingerprints>
2567 would crash a dirserver if it did not already have a
2568 consensus. Bugfix on 0.2.1.1-alpha.
2569 - Clean up some macro/CPP interactions: some GCC versions don't like
2570 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
2573 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
2574 - Directory authorities shouldn't complain about bootstrapping
2575 problems just because they do a lot of reachability testing and
2576 some of the connection attempts fail.
2577 - Start sending "count" and "recommendation" key/value pairs in
2578 bootstrap problem status events, so the controller can hear about
2579 problems even before Tor decides they're worth reporting for sure.
2580 - If you're using bridges, generate "bootstrap problem" warnings
2581 as soon as you run out of working bridges, rather than waiting
2582 for ten failures -- which will never happen if you have less than
2584 - If we close our OR connection because there's been a circuit
2585 pending on it for too long, we were telling our bootstrap status
2586 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
2589 Changes in version 0.2.1.1-alpha - 2008-06-13
2590 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
2591 were making the Tor process bloat especially on Linux; makes our TLS
2592 handshake blend in better; sends "bootstrap phase" status events to
2593 the controller, so it can keep the user informed of progress (and
2594 problems) fetching directory information and establishing circuits;
2595 and adds a variety of smaller features.
2598 - More work on making our TLS handshake blend in: modify the list
2599 of ciphers advertised by OpenSSL in client mode to even more
2600 closely resemble a common web browser. We cheat a little so that
2601 we can advertise ciphers that the locally installed OpenSSL doesn't
2603 - Start sending "bootstrap phase" status events to the controller,
2604 so it can keep the user informed of progress fetching directory
2605 information and establishing circuits. Also inform the controller
2606 if we think we're stuck at a particular bootstrap phase. Implements
2608 - Resume using OpenSSL's RAND_poll() for better (and more portable)
2609 cross-platform entropy collection again. We used to use it, then
2610 stopped using it because of a bug that could crash systems that
2611 called RAND_poll when they had a lot of fds open. It looks like the
2612 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
2613 at startup, and to call RAND_poll() when we reseed later only if
2614 we have a non-buggy OpenSSL version.
2617 - When we choose to abandon a new entry guard because we think our
2618 older ones might be better, close any circuits pending on that
2619 new entry guard connection. This fix should make us recover much
2620 faster when our network is down and then comes back. Bugfix on
2621 0.1.2.8-beta; found by lodger.
2623 o Memory fixes and improvements:
2624 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
2625 to avoid unused RAM in buffer chunks and memory pools.
2626 - Speed up parsing and cut down on memory fragmentation by using
2627 stack-style allocations for parsing directory objects. Previously,
2628 this accounted for over 40% of allocations from within Tor's code
2629 on a typical directory cache.
2630 - Use a Bloom filter rather than a digest-based set to track which
2631 descriptors we need to keep around when we're cleaning out old
2632 router descriptors. This speeds up the computation significantly,
2633 and may reduce fragmentation.
2634 - Reduce the default smartlist size from 32 to 16; it turns out that
2635 most smartlists hold around 8-12 elements tops.
2636 - Make dumpstats() log the fullness and size of openssl-internal
2638 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
2639 patch to their OpenSSL, turn it on to save memory on servers. This
2640 patch will (with any luck) get included in a mainline distribution
2642 - Never use OpenSSL compression: it wastes RAM and CPU trying to
2643 compress cells, which are basically all encrypted, compressed,
2647 - Stop reloading the router list from disk for no reason when we
2648 run out of reachable directory mirrors. Once upon a time reloading
2649 it would set the 'is_running' flag back to 1 for them. It hasn't
2650 done that for a long time.
2651 - In very rare situations new hidden service descriptors were
2652 published earlier than 30 seconds after the last change to the
2653 service. (We currently think that a hidden service descriptor
2654 that's been stable for 30 seconds is worth publishing.)
2657 - Allow separate log levels to be configured for different logging
2658 domains. For example, this allows one to log all notices, warnings,
2659 or errors, plus all memory management messages of level debug or
2660 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
2661 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
2662 and stop using a warning that had become unfixably verbose under
2664 - New --hush command-line option similar to --quiet. While --quiet
2665 disables all logging to the console on startup, --hush limits the
2666 output to messages of warning and error severity.
2667 - Servers support a new URL scheme for consensus downloads that
2668 allows the client to specify which authorities are trusted.
2669 The server then only sends the consensus if the client will trust
2670 it. Otherwise a 404 error is sent back. Clients use this
2671 new scheme when the server supports it (meaning it's running
2672 0.2.1.1-alpha or later). Implements proposal 134.
2673 - New configure/torrc options (--enable-geoip-stats,
2674 DirRecordUsageByCountry) to record how many IPs we've served
2675 directory info to in each country code, how many status documents
2676 total we've sent to each country code, and what share of the total
2677 directory requests we should expect to see.
2678 - Use the TLS1 hostname extension to more closely resemble browser
2680 - Lots of new unit tests.
2681 - Add a macro to implement the common pattern of iterating through
2682 two parallel lists in lockstep.
2685 Changes in version 0.2.0.28-rc - 2008-06-13
2686 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
2687 performance bug, and fixes a bunch of smaller bugs.
2690 - Fix a bug where, when we were choosing the 'end stream reason' to
2691 put in our relay end cell that we send to the exit relay, Tor
2692 clients on Windows were sometimes sending the wrong 'reason'. The
2693 anonymity problem is that exit relays may be able to guess whether
2694 the client is running Windows, thus helping partition the anonymity
2695 set. Down the road we should stop sending reasons to exit relays,
2696 or otherwise prevent future versions of this bug.
2699 - While setting up a hidden service, some valid introduction circuits
2700 were overlooked and abandoned. This might be the reason for
2701 the long delay in making a hidden service available. Bugfix on
2705 - Update to the "June 9 2008" ip-to-country file.
2706 - Run 'make test' as part of 'make dist', so we stop releasing so
2707 many development snapshots that fail their unit tests.
2710 - When we're checking if we have enough dir info for each relay
2711 to begin establishing circuits, make sure that we actually have
2712 the descriptor listed in the consensus, not just any descriptor.
2714 - Bridge relays no longer print "xx=0" in their extrainfo document
2715 for every single country code in the geoip db. Bugfix on
2717 - Only warn when we fail to load the geoip file if we were planning to
2718 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
2719 - If we change our MaxAdvertisedBandwidth and then reload torrc,
2720 Tor won't realize it should publish a new relay descriptor. Fixes
2721 bug 688, reported by mfr. Bugfix on 0.1.2.x.
2722 - When we haven't had any application requests lately, don't bother
2723 logging that we have expired a bunch of descriptors. Bugfix
2725 - Make relay cells written on a connection count as non-padding when
2726 tracking how long a connection has been in use. Bugfix on
2727 0.2.0.1-alpha. Spotted by lodger.
2728 - Fix unit tests in 0.2.0.27-rc.
2729 - Fix compile on Windows.
2732 Changes in version 0.2.0.27-rc - 2008-06-03
2733 Tor 0.2.0.27-rc adds a few features we left out of the earlier
2734 release candidates. In particular, we now include an IP-to-country
2735 GeoIP database, so controllers can easily look up what country a
2736 given relay is in, and so bridge relays can give us some sanitized
2737 summaries about which countries are making use of bridges. (See proposal
2738 126-geoip-fetching.txt for details.)
2741 - Include an IP-to-country GeoIP file in the tarball, so bridge
2742 relays can report sanitized summaries of the usage they're seeing.
2745 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
2746 Robert Hogan. Fixes the first part of bug 681.
2747 - Make bridge authorities never serve extrainfo docs.
2748 - Add support to detect Libevent versions in the 1.4.x series
2750 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
2751 - Include a new contrib/tor-exit-notice.html file that exit relay
2752 operators can put on their website to help reduce abuse queries.
2755 - When tunneling an encrypted directory connection, and its first
2756 circuit fails, do not leave it unattached and ask the controller
2757 to deal. Fixes the second part of bug 681.
2758 - Make bridge authorities correctly expire old extrainfo documents
2762 Changes in version 0.2.0.26-rc - 2008-05-13
2763 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
2764 in Debian's OpenSSL packages. All users running any 0.2.0.x version
2765 should upgrade, whether they're running Debian or not.
2767 o Major security fixes:
2768 - Use new V3 directory authority keys on the tor26, gabelmoo, and
2769 moria1 V3 directory authorities. The old keys were generated with
2770 a vulnerable version of Debian's OpenSSL package, and must be
2771 considered compromised. Other authorities' keys were not generated
2772 with an affected version of OpenSSL.
2775 - List authority signatures as "unrecognized" based on DirServer
2776 lines, not on cert cache. Bugfix on 0.2.0.x.
2779 - Add a new V3AuthUseLegacyKey option to make it easier for
2780 authorities to change their identity keys if they have to.
2783 Changes in version 0.2.0.25-rc - 2008-04-23
2784 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
2787 - Remember to initialize threading before initializing logging.
2788 Otherwise, many BSD-family implementations will crash hard on
2789 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
2792 - Authorities correctly free policies on bad servers on
2793 exit. Fixes bug 672. Bugfix on 0.2.0.x.
2796 Changes in version 0.2.0.24-rc - 2008-04-22
2797 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
2798 v3 directory authority, makes relays with dynamic IP addresses and no
2799 DirPort notice more quickly when their IP address changes, fixes a few
2800 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
2802 o New directory authorities:
2803 - Take lefkada out of the list of v3 directory authorities, since
2804 it has been down for months.
2805 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
2809 - Detect address changes more quickly on non-directory mirror
2810 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
2812 o Minor features (security):
2813 - Reject requests for reverse-dns lookup of names that are in
2814 a private address space. Patch from lodger.
2815 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
2818 o Minor bugfixes (crashes):
2819 - Avoid a rare assert that can trigger when Tor doesn't have much
2820 directory information yet and it tries to fetch a v2 hidden
2821 service descriptor. Fixes bug 651, reported by nwf.
2822 - Initialize log mutex before initializing dmalloc. Otherwise,
2823 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
2824 - Use recursive pthread mutexes in order to avoid deadlock when
2825 logging debug-level messages to a controller. Bug spotted by nwf,
2826 bugfix on 0.2.0.16-alpha.
2828 o Minor bugfixes (resource management):
2829 - Keep address policies from leaking memory: start their refcount
2830 at 1, not 2. Bugfix on 0.2.0.16-alpha.
2831 - Free authority certificates on exit, so they don't look like memory
2832 leaks. Bugfix on 0.2.0.19-alpha.
2833 - Free static hashtables for policy maps and for TLS connections on
2834 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
2835 - Avoid allocating extra space when computing consensuses on 64-bit
2836 platforms. Bug spotted by aakova.
2838 o Minor bugfixes (misc):
2839 - Do not read the configuration file when we've only been told to
2840 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
2841 based on patch from Sebastian Hahn.
2842 - Exit relays that are used as a client can now reach themselves
2843 using the .exit notation, rather than just launching an infinite
2844 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
2845 - When attempting to open a logfile fails, tell us why.
2846 - Fix a dumb bug that was preventing us from knowing that we should
2847 preemptively build circuits to handle expected directory requests.
2848 Fixes bug 660. Bugfix on 0.1.2.x.
2849 - Warn less verbosely about clock skew from netinfo cells from
2850 untrusted sources. Fixes bug 663.
2851 - Make controller stream events for DNS requests more consistent,
2852 by adding "new stream" events for DNS requests, and removing
2853 spurious "stream closed" events" for cached reverse resolves.
2854 Patch from mwenge. Fixes bug 646.
2855 - Correctly notify one-hop connections when a circuit build has
2856 failed. Possible fix for bug 669. Found by lodger.
2859 Changes in version 0.2.0.23-rc - 2008-03-24
2860 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
2861 makes bootstrapping faster if the first directory mirror you contact
2862 is down. The bundles also include the new Vidalia 0.1.2 release.
2865 - When a tunneled directory request is made to a directory server
2866 that's down, notice after 30 seconds rather than 120 seconds. Also,
2867 fail any begindir streams that are pending on it, so they can
2868 retry elsewhere. This was causing multi-minute delays on bootstrap.
2871 Changes in version 0.2.0.22-rc - 2008-03-18
2872 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
2873 enables encrypted directory connections by default for non-relays, fixes
2874 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
2875 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
2878 - Enable encrypted directory connections by default for non-relays,
2879 so censor tools that block Tor directory connections based on their
2880 plaintext patterns will no longer work. This means Tor works in
2881 certain censored countries by default again.
2884 - Make sure servers always request certificates from clients during
2885 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
2886 - Do not enter a CPU-eating loop when a connection is closed in
2887 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
2888 diagnosed by lodger; bugfix on 0.2.0.20-rc.
2889 - Fix assertion failure that could occur when a blocked circuit
2890 became unblocked, and it had pending client DNS requests. Bugfix
2891 on 0.2.0.1-alpha. Fixes bug 632.
2893 o Minor bugfixes (on 0.1.2.x):
2894 - Generate "STATUS_SERVER" events rather than misspelled
2895 "STATUS_SEVER" events. Caught by mwenge.
2896 - When counting the number of bytes written on a TLS connection,
2897 look at the BIO actually used for writing to the network, not
2898 at the BIO used (sometimes) to buffer data for the network.
2899 Looking at different BIOs could result in write counts on the
2900 order of ULONG_MAX. Fixes bug 614.
2901 - On Windows, correctly detect errors when listing the contents of
2902 a directory. Fix from lodger.
2904 o Minor bugfixes (on 0.2.0.x):
2905 - Downgrade "sslv3 alert handshake failure" message to INFO.
2906 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
2907 left BandwidthRate and BandwidthBurst at the default, we would be
2908 silently limited by those defaults. Now raise them to match the
2909 RelayBandwidth* values.
2910 - Fix the SVK version detection logic to work correctly on a branch.
2911 - Make --enable-openbsd-malloc work correctly on Linux with alpha
2912 CPUs. Fixes bug 625.
2913 - Logging functions now check that the passed severity is sane.
2914 - Use proper log levels in the testsuite call of
2915 get_interface_address6().
2916 - When using a nonstandard malloc, do not use the platform values for
2917 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
2918 - Make the openbsd malloc code use 8k pages on alpha CPUs and
2920 - Detect mismatched page sizes when using --enable-openbsd-malloc.
2921 - Avoid double-marked-for-close warning when certain kinds of invalid
2922 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
2923 for bug 617. Bugfix on 0.2.0.1-alpha.
2924 - Make sure that the "NULL-means-reject *:*" convention is followed by
2925 all the policy manipulation functions, avoiding some possible crash
2926 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
2927 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
2928 actually works, and doesn't warn about every single reverse lookup.
2929 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
2932 - Only log guard node status when guard node status has changed.
2933 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
2934 make "INFO" 75% less verbose.
2937 Changes in version 0.2.0.21-rc - 2008-03-02
2938 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
2939 makes Tor work well with Vidalia again, fixes a rare assert bug,
2940 and fixes a pair of more minor bugs. The bundles also include Vidalia
2941 0.1.0 and Torbutton 1.1.16.
2944 - The control port should declare that it requires password auth
2945 when HashedControlSessionPassword is set too. Patch from Matt Edman;
2946 bugfix on 0.2.0.20-rc. Fixes bug 615.
2947 - Downgrade assert in connection_buckets_decrement() to a log message.
2948 This may help us solve bug 614, and in any case will make its
2949 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
2950 - We were sometimes miscounting the number of bytes read from the
2951 network, causing our rate limiting to not be followed exactly.
2952 Bugfix on 0.2.0.16-alpha. Reported by lodger.
2955 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
2956 OpenSSL versions should have been working fine. Diagnosis and patch
2957 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
2958 Bugfix on 0.2.0.20-rc.
2961 Changes in version 0.2.0.20-rc - 2008-02-24
2962 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
2963 makes more progress towards normalizing Tor's TLS handshake, makes
2964 hidden services work better again, helps relays bootstrap if they don't
2965 know their IP address, adds optional support for linking in openbsd's
2966 allocator or tcmalloc, allows really fast relays to scale past 15000
2967 sockets, and fixes a bunch of minor bugs reported by Veracode.
2970 - Enable the revised TLS handshake based on the one designed by
2971 Steven Murdoch in proposal 124, as revised in proposal 130. It
2972 includes version negotiation for OR connections as described in
2973 proposal 105. The new handshake is meant to be harder for censors
2974 to fingerprint, and it adds the ability to detect certain kinds of
2975 man-in-the-middle traffic analysis attacks. The version negotiation
2976 feature will allow us to improve Tor's link protocol more safely
2978 - Choose which bridge to use proportional to its advertised bandwidth,
2979 rather than uniformly at random. This should speed up Tor for
2980 bridge users. Also do this for people who set StrictEntryNodes.
2981 - When a TrackHostExits-chosen exit fails too many times in a row,
2982 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
2985 - Resolved problems with (re-)fetching hidden service descriptors.
2986 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
2988 - If we only ever used Tor for hidden service lookups or posts, we
2989 would stop building circuits and start refusing connections after
2990 24 hours, since we falsely believed that Tor was dormant. Reported
2991 by nwf; bugfix on 0.1.2.x.
2992 - Servers that don't know their own IP address should go to the
2993 authorities for their first directory fetch, even if their DirPort
2994 is off or if they don't know they're reachable yet. This will help
2995 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
2996 - When counting the number of open sockets, count not only the number
2997 of sockets we have received from the socket() call, but also
2998 the number we've gotten from accept() and socketpair(). This bug
2999 made us fail to count all sockets that we were using for incoming
3000 connections. Bugfix on 0.2.0.x.
3001 - Fix code used to find strings within buffers, when those strings
3002 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
3003 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
3004 - Add a new __HashedControlSessionPassword option for controllers
3005 to use for one-off session password hashes that shouldn't get
3006 saved to disk by SAVECONF --- Vidalia users were accumulating a
3007 pile of HashedControlPassword lines in their torrc files, one for
3008 each time they had restarted Tor and then clicked Save. Make Tor
3009 automatically convert "HashedControlPassword" to this new option but
3010 only when it's given on the command line. Partial fix for bug 586.
3012 o Minor features (performance):
3013 - Tune parameters for cell pool allocation to minimize amount of
3015 - Add OpenBSD malloc code from phk as an optional malloc
3016 replacement on Linux: some glibc libraries do very poorly
3017 with Tor's memory allocation patterns. Pass
3018 --enable-openbsd-malloc to get the replacement malloc code.
3019 - Add a --with-tcmalloc option to the configure script to link
3020 against tcmalloc (if present). Does not yet search for
3021 non-system include paths.
3022 - Stop imposing an arbitrary maximum on the number of file descriptors
3023 used for busy servers. Bug reported by Olaf Selke; patch from
3026 o Minor features (other):
3027 - When SafeLogging is disabled, log addresses along with all TLS
3029 - When building with --enable-gcc-warnings, check for whether Apple's
3030 warning "-Wshorten-64-to-32" is available.
3031 - Add a --passphrase-fd argument to the tor-gencert command for
3034 o Minor bugfixes (memory leaks and code problems):
3035 - We were leaking a file descriptor if Tor started with a zero-length
3036 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
3037 - Detect size overflow in zlib code. Reported by Justin Ferguson and
3039 - We were comparing the raw BridgePassword entry with a base64'ed
3040 version of it, when handling a "/tor/networkstatus-bridges"
3041 directory request. Now compare correctly. Noticed by Veracode.
3042 - Recover from bad tracked-since value in MTBF-history file.
3044 - Alter the code that tries to recover from unhandled write
3045 errors, to not try to flush onto a socket that's given us
3046 unhandled errors. Bugfix on 0.1.2.x.
3047 - Make Unix controlsockets work correctly on OpenBSD. Patch from
3048 tup. Bugfix on 0.2.0.3-alpha.
3050 o Minor bugfixes (other):
3051 - If we have an extra-info document for our server, always make
3052 it available on the control port, even if we haven't gotten
3053 a copy of it from an authority yet. Patch from mwenge.
3054 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
3055 - Directory mirrors no longer include a guess at the client's IP
3056 address if the connection appears to be coming from the same /24
3057 network; it was producing too many wrong guesses.
3058 - Make the new hidden service code respect the SafeLogging setting.
3059 Bugfix on 0.2.0.x. Patch from Karsten.
3060 - When starting as an authority, do not overwrite all certificates
3061 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
3062 - If we're trying to flush the last bytes on a connection (for
3063 example, when answering a directory request), reset the
3064 time-to-give-up timeout every time we manage to write something
3065 on the socket. Bugfix on 0.1.2.x.
3066 - Change the behavior of "getinfo status/good-server-descriptor"
3067 so it doesn't return failure when any authority disappears.
3068 - Even though the man page said that "TrackHostExits ." should
3069 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
3070 - Report TLS "zero return" case as a "clean close" and "IO error"
3071 as a "close". Stop calling closes "unexpected closes": existing
3072 Tors don't use SSL_close(), so having a connection close without
3073 the TLS shutdown handshake is hardly unexpected.
3074 - Send NAMESERVER_STATUS messages for a single failed nameserver
3077 o Code simplifications and refactoring:
3078 - Remove the tor_strpartition function: its logic was confused,
3079 and it was only used for one thing that could be implemented far
3083 Changes in version 0.2.0.19-alpha - 2008-02-09
3084 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
3085 handshake, makes path selection for relays more secure and IP address
3086 guessing more robust, and generally fixes a lot of bugs in preparation
3087 for calling the 0.2.0 branch stable.
3090 - Do not include recognizeable strings in the commonname part of
3091 Tor's x509 certificates.
3094 - If we're a relay, avoid picking ourselves as an introduction point,
3095 a rendezvous point, or as the final hop for internal circuits. Bug
3096 reported by taranis and lodger. Bugfix on 0.1.2.x.
3097 - Patch from "Andrew S. Lists" to catch when we contact a directory
3098 mirror at IP address X and he says we look like we're coming from
3099 IP address X. Bugfix on 0.1.2.x.
3101 o Minor features (security):
3102 - Be more paranoid about overwriting sensitive memory on free(),
3103 as a defensive programming tactic to ensure forward secrecy.
3105 o Minor features (directory authority):
3106 - Actually validate the options passed to AuthDirReject,
3107 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
3108 - Reject router descriptors with out-of-range bandwidthcapacity or
3109 bandwidthburst values.
3111 o Minor features (controller):
3112 - Reject controller commands over 1MB in length. This keeps rogue
3113 processes from running us out of memory.
3115 o Minor features (misc):
3116 - Give more descriptive well-formedness errors for out-of-range
3117 hidden service descriptor/protocol versions.
3118 - Make memory debugging information describe more about history
3119 of cell allocation, so we can help reduce our memory use.
3121 o Deprecated features (controller):
3122 - The status/version/num-versioning and status/version/num-concurring
3123 GETINFO options are no longer useful in the v3 directory protocol:
3124 treat them as deprecated, and warn when they're used.
3127 - When our consensus networkstatus has been expired for a while, stop
3128 being willing to build circuits using it. Fixes bug 401. Bugfix
3130 - Directory caches now fetch certificates from all authorities
3131 listed in a networkstatus consensus, even when they do not
3132 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
3133 - When connecting to a bridge without specifying its key, insert
3134 the connection into the identity-to-connection map as soon as
3135 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
3136 - Detect versions of OS X where malloc_good_size() is present in the
3137 library but never actually declared. Resolves bug 587. Bugfix
3139 - Stop incorrectly truncating zlib responses to directory authority
3140 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
3141 - Stop recommending that every server operator send mail to tor-ops.
3142 Resolves bug 597. Bugfix on 0.1.2.x.
3143 - Don't trigger an assert if we start a directory authority with a
3144 private IP address (like 127.0.0.1).
3145 - Avoid possible failures when generating a directory with routers
3146 with over-long versions strings, or too many flags set. Bugfix
3148 - If an attempt to launch a DNS resolve request over the control
3149 port fails because we have overrun the limit on the number of
3150 connections, tell the controller that the request has failed.
3151 - Avoid using too little bandwidth when our clock skips a few
3152 seconds. Bugfix on 0.1.2.x.
3153 - Fix shell error when warning about missing packages in configure
3154 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
3155 - Do not become confused when receiving a spurious VERSIONS-like
3156 cell from a confused v1 client. Bugfix on 0.2.0.x.
3157 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
3158 introduction points for a hidden service have failed. Patch from
3159 Karsten Loesing. Bugfix on 0.2.0.x.
3161 o Code simplifications and refactoring:
3162 - Remove some needless generality from cpuworker code, for improved
3164 - Stop overloading the circuit_t.onionskin field for both "onionskin
3165 from a CREATE cell that we are waiting for a cpuworker to be
3166 assigned" and "onionskin from an EXTEND cell that we are going to
3167 send to an OR as soon as we are connected". Might help with bug 600.
3168 - Add an in-place version of aes_crypt() so that we can avoid doing a
3169 needless memcpy() call on each cell payload.
3172 Changes in version 0.2.0.18-alpha - 2008-01-25
3173 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
3174 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
3175 that can warn or reject connections to ports generally associated with
3176 vulnerable-plaintext protocols.
3178 o New directory authorities:
3179 - Set up dannenberg (run by CCC) as the sixth v3 directory
3183 - Fix a major memory leak when attempting to use the v2 TLS
3184 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
3185 - We accidentally enabled the under-development v2 TLS handshake
3186 code, which was causing log entries like "TLS error while
3187 renegotiating handshake". Disable it again. Resolves bug 590.
3188 - We were computing the wrong Content-Length: header for directory
3189 responses that need to be compressed on the fly, causing clients
3190 asking for those items to always fail. Bugfix on 0.2.0.x; partially
3194 - Avoid going directly to the directory authorities even if you're a
3195 relay, if you haven't found yourself reachable yet or if you've
3196 decided not to advertise your dirport yet. Addresses bug 556.
3197 - If we've gone 12 hours since our last bandwidth check, and we
3198 estimate we have less than 50KB bandwidth capacity but we could
3199 handle more, do another bandwidth test.
3200 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
3201 Tor can warn and/or refuse connections to ports commonly used with
3202 vulnerable-plaintext protocols. Currently we warn on ports 23,
3203 109, 110, and 143, but we don't reject any.
3206 - When we setconf ClientOnly to 1, close any current OR and Dir
3207 listeners. Reported by mwenge.
3208 - When we get a consensus that's been signed by more people than
3209 we expect, don't log about it; it's not a big deal. Reported
3213 - Don't answer "/tor/networkstatus-bridges" directory requests if
3214 the request isn't encrypted.
3215 - Make "ClientOnly 1" config option disable directory ports too.
3216 - Patches from Karsten Loesing to make v2 hidden services more
3217 robust: work even when there aren't enough HSDir relays available;
3218 retry when a v2 rend desc fetch fails; but don't retry if we
3219 already have a usable v0 rend desc.
3222 Changes in version 0.2.0.17-alpha - 2008-01-17
3223 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
3226 - Make the tor-gencert man page get included correctly in the tarball.
3229 Changes in version 0.2.0.16-alpha - 2008-01-17
3230 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
3231 Loesing, and generally cleans up a lot of features and minor bugs.
3233 o New directory authorities:
3234 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
3237 o Major performance improvements:
3238 - Switch our old ring buffer implementation for one more like that
3239 used by free Unix kernels. The wasted space in a buffer with 1mb
3240 of data will now be more like 8k than 1mb. The new implementation
3241 also avoids realloc();realloc(); patterns that can contribute to
3242 memory fragmentation.
3245 - Configuration files now accept C-style strings as values. This
3246 helps encode characters not allowed in the current configuration
3247 file format, such as newline or #. Addresses bug 557.
3248 - Although we fixed bug 539 (where servers would send HTTP status 503
3249 responses _and_ send a body too), there are still servers out
3250 there that haven't upgraded. Therefore, make clients parse such
3251 bodies when they receive them.
3252 - When we're not serving v2 directory information, there is no reason
3253 to actually keep any around. Remove the obsolete files and directory
3254 on startup if they are very old and we aren't going to serve them.
3256 o Minor performance improvements:
3257 - Reference-count and share copies of address policy entries; only 5%
3258 of them were actually distinct.
3259 - Never walk through the list of logs if we know that no log is
3260 interested in a given message.
3263 - When an authority has not signed a consensus, do not try to
3264 download a nonexistent "certificate with key 00000000". Bugfix
3265 on 0.2.0.x. Fixes bug 569.
3266 - Fix a rare assert error when we're closing one of our threads:
3267 use a mutex to protect the list of logs, so we never write to the
3268 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
3269 bug 575, which is kind of the revenge of bug 222.
3270 - Patch from Karsten Loesing to complain less at both the client
3271 and the relay when a relay used to have the HSDir flag but doesn't
3272 anymore, and we try to upload a hidden service descriptor.
3273 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
3275 - Do not try to download missing certificates until we have tried
3276 to check our fallback consensus. Fixes bug 583.
3277 - Make bridges round reported GeoIP stats info up to the nearest
3278 estimate, not down. Now we can distinguish between "0 people from
3279 this country" and "1 person from this country".
3280 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
3281 - Avoid possible segfault if key generation fails in
3282 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
3283 - Avoid segfault in the case where a badly behaved v2 versioning
3284 directory sends a signed networkstatus with missing client-versions.
3286 - Avoid segfaults on certain complex invocations of
3287 router_get_by_hexdigest(). Bugfix on 0.1.2.
3288 - Correct bad index on array access in parse_http_time(). Bugfix
3290 - Fix possible bug in vote generation when server versions are present
3291 but client versions are not.
3292 - Fix rare bug on REDIRECTSTREAM control command when called with no
3293 port set: it could erroneously report an error when none had
3295 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
3296 compressing large objects and find ourselves with more than 4k
3297 left over. Bugfix on 0.2.0.
3298 - Fix a small memory leak when setting up a hidden service.
3299 - Fix a few memory leaks that could in theory happen under bizarre
3301 - Fix an assert if we post a general-purpose descriptor via the
3302 control port but that descriptor isn't mentioned in our current
3303 network consensus. Bug reported by Jon McLachlan; bugfix on
3306 o Minor features (controller):
3307 - Get NS events working again. Patch from tup.
3308 - The GETCONF command now escapes and quotes configuration values
3309 that don't otherwise fit into the torrc file.
3310 - The SETCONF command now handles quoted values correctly.
3312 o Minor features (directory authorities):
3313 - New configuration options to override default maximum number of
3314 servers allowed on a single IP address. This is important for
3315 running a test network on a single host.
3316 - Actually implement the -s option to tor-gencert.
3317 - Add a manual page for tor-gencert.
3319 o Minor features (bridges):
3320 - Bridge authorities no longer serve bridge descriptors over
3321 unencrypted connections.
3323 o Minor features (other):
3324 - Add hidden services and DNSPorts to the list of things that make
3325 Tor accept that it has running ports. Change starting Tor with no
3326 ports from a fatal error to a warning; we might change it back if
3327 this turns out to confuse anybody. Fixes bug 579.
3330 Changes in version 0.1.2.19 - 2008-01-17
3331 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
3332 exit policy a little bit more conservative so it's safer to run an
3333 exit relay on a home system, and fixes a variety of smaller issues.
3336 - Exit policies now reject connections that are addressed to a
3337 relay's public (external) IP address too, unless
3338 ExitPolicyRejectPrivate is turned off. We do this because too
3339 many relays are running nearby to services that trust them based
3343 - When the clock jumps forward a lot, do not allow the bandwidth
3344 buckets to become negative. Fixes bug 544.
3345 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
3346 on every successful resolve. Reported by Mike Perry.
3347 - Purge old entries from the "rephist" database and the hidden
3348 service descriptor database even when DirPort is zero.
3349 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
3350 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
3351 crashing or mis-answering these requests.
3352 - When we decide to send a 503 response to a request for servers, do
3353 not then also send the server descriptors: this defeats the whole
3354 purpose. Fixes bug 539.
3357 - Changing the ExitPolicyRejectPrivate setting should cause us to
3358 rebuild our server descriptor.
3359 - Fix handling of hex nicknames when answering controller requests for
3360 networkstatus by name, or when deciding whether to warn about
3361 unknown routers in a config option. (Patch from mwenge.)
3362 - Fix a couple of hard-to-trigger autoconf problems that could result
3363 in really weird results on platforms whose sys/types.h files define
3364 nonstandard integer types.
3365 - Don't try to create the datadir when running --verify-config or
3366 --hash-password. Resolves bug 540.
3367 - If we were having problems getting a particular descriptor from the
3368 directory caches, and then we learned about a new descriptor for
3369 that router, we weren't resetting our failure count. Reported
3371 - Although we fixed bug 539 (where servers would send HTTP status 503
3372 responses _and_ send a body too), there are still servers out there
3373 that haven't upgraded. Therefore, make clients parse such bodies
3374 when they receive them.
3375 - Run correctly on systems where rlim_t is larger than unsigned long.
3376 This includes some 64-bit systems.
3377 - Run correctly on platforms (like some versions of OS X 10.5) where
3378 the real limit for number of open files is OPEN_FILES, not rlim_max
3379 from getrlimit(RLIMIT_NOFILES).
3380 - Avoid a spurious free on base64 failure.
3381 - Avoid segfaults on certain complex invocations of
3382 router_get_by_hexdigest().
3383 - Fix rare bug on REDIRECTSTREAM control command when called with no
3384 port set: it could erroneously report an error when none had
3388 Changes in version 0.2.0.15-alpha - 2007-12-25
3389 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
3390 features added in 0.2.0.13-alpha.
3393 - Fix several remotely triggerable asserts based on DirPort requests
3394 for a v2 or v3 networkstatus object before we were prepared. This
3395 was particularly bad for 0.2.0.13 and later bridge relays, who
3396 would never have a v2 networkstatus and would thus always crash
3397 when used. Bugfixes on 0.2.0.x.
3398 - Estimate the v3 networkstatus size more accurately, rather than
3399 estimating it at zero bytes and giving it artificially high priority
3400 compared to other directory requests. Bugfix on 0.2.0.x.
3403 - Fix configure.in logic for cross-compilation.
3404 - When we load a bridge descriptor from the cache, and it was
3405 previously unreachable, mark it as retriable so we won't just
3406 ignore it. Also, try fetching a new copy immediately. Bugfixes
3408 - The bridge GeoIP stats were counting other relays, for example
3409 self-reachability and authority-reachability tests.
3412 - Support compilation to target iPhone; patch from cjacker huang.
3413 To build for iPhone, pass the --enable-iphone option to configure.
3416 Changes in version 0.2.0.14-alpha - 2007-12-23
3418 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
3419 without a datadirectory from a previous Tor install. Reported
3421 - Fix a crash when we fetch a descriptor that turns out to be
3422 unexpected (it used to be in our networkstatus when we started
3423 fetching it, but it isn't in our current networkstatus), and we
3424 aren't using bridges. Bugfix on 0.2.0.x.
3425 - Fix a crash when accessing hidden services: it would work the first
3426 time you use a given introduction point for your service, but
3427 on subsequent requests we'd be using garbage memory. Fixed by
3428 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
3429 - Fix a crash when we load a bridge descriptor from disk but we don't
3430 currently have a Bridge line for it in our torrc. Bugfix on
3434 - If bridge authorities set BridgePassword, they will serve a
3435 snapshot of known bridge routerstatuses from their DirPort to
3436 anybody who knows that password. Unset by default.
3439 - Make the unit tests build again.
3440 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
3441 - Make PublishServerDescriptor default to 1, so the default doesn't
3442 have to change as we invent new directory protocol versions.
3443 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
3444 be included unless sys/time.h is already included. Fixes
3445 bug 553. Bugfix on 0.2.0.x.
3446 - If we receive a general-purpose descriptor and then receive an
3447 identical bridge-purpose descriptor soon after, don't discard
3448 the next one as a duplicate.
3451 - If BridgeRelay is set to 1, then the default for
3452 PublishServerDescriptor is now "bridge" rather than "v2,v3".
3453 - If the user sets RelayBandwidthRate but doesn't set
3454 RelayBandwidthBurst, then make them equal rather than erroring out.
3457 Changes in version 0.2.0.13-alpha - 2007-12-21
3458 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
3459 Goodell, fixes many more bugs, and adds a lot of infrastructure for
3462 o New directory authorities:
3463 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
3467 - Only update guard status (usable / not usable) once we have
3468 enough directory information. This was causing us to always pick
3469 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
3470 causing us to discard all our guards on startup if we hadn't been
3471 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
3472 - Purge old entries from the "rephist" database and the hidden
3473 service descriptor databases even when DirPort is zero. Bugfix
3475 - We were ignoring our RelayBandwidthRate for the first 30 seconds
3476 after opening a circuit -- even a relayed circuit. Bugfix on
3478 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
3479 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
3480 crashing or mis-answering these types of requests.
3481 - Relays were publishing their server descriptor to v1 and v2
3482 directory authorities, but they didn't try publishing to v3-only
3483 authorities. Fix this; and also stop publishing to v1 authorities.
3485 - When we were reading router descriptors from cache, we were ignoring
3486 the annotations -- so for example we were reading in bridge-purpose
3487 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
3488 - When we decided to send a 503 response to a request for servers, we
3489 were then also sending the server descriptors: this defeats the
3490 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
3493 - Bridge relays now behave like clients with respect to time
3494 intervals for downloading new consensus documents -- otherwise they
3495 stand out. Bridge users now wait until the end of the interval,
3496 so their bridge relay will be sure to have a new consensus document.
3497 - Three new config options (AlternateDirAuthority,
3498 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
3499 user selectively replace the default directory authorities by type,
3500 rather than the all-or-nothing replacement that DirServer offers.
3501 - Tor can now be configured to read a GeoIP file from disk in one
3502 of two formats. This can be used by controllers to map IP addresses
3503 to countries. Eventually, it may support exit-by-country.
3504 - When possible, bridge relays remember which countries users
3505 are coming from, and report aggregate information in their
3506 extra-info documents, so that the bridge authorities can learn
3507 where Tor is blocked.
3508 - Bridge directory authorities now do reachability testing on the
3509 bridges they know. They provide router status summaries to the
3510 controller via "getinfo ns/purpose/bridge", and also dump summaries
3511 to a file periodically.
3512 - Stop fetching directory info so aggressively if your DirPort is
3513 on but your ORPort is off; stop fetching v2 dir info entirely.
3514 You can override these choices with the new FetchDirInfoEarly
3518 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
3519 consensus documents when there are too many relays at a single
3520 IP address. Now clear it in v2 network status documents too, and
3521 also clear it in routerinfo_t when the relay is no longer listed
3522 in the relevant networkstatus document.
3523 - Don't crash if we get an unexpected value for the
3524 PublishServerDescriptor config option. Reported by Matt Edman;
3525 bugfix on 0.2.0.9-alpha.
3526 - Our new v2 hidden service descriptor format allows descriptors
3527 that have no introduction points. But Tor crashed when we tried
3528 to build a descriptor with no intro points (and it would have
3529 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
3531 - Fix building with dmalloc 5.5.2 with glibc.
3532 - Reject uploaded descriptors and extrainfo documents if they're
3533 huge. Otherwise we'll cache them all over the network and it'll
3534 clog everything up. Reported by Aljosha Judmayer.
3535 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
3536 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
3537 - When the DANGEROUS_VERSION controller status event told us we're
3538 running an obsolete version, it used the string "OLD" to describe
3539 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
3540 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
3541 - If we can't expand our list of entry guards (e.g. because we're
3542 using bridges or we have StrictEntryNodes set), don't mark relays
3543 down when they fail a directory request. Otherwise we're too quick
3544 to mark all our entry points down. Bugfix on 0.1.2.x.
3545 - Fix handling of hex nicknames when answering controller requests for
3546 networkstatus by name, or when deciding whether to warn about unknown
3547 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
3548 - Fix a couple of hard-to-trigger autoconf problems that could result
3549 in really weird results on platforms whose sys/types.h files define
3550 nonstandard integer types. Bugfix on 0.1.2.x.
3551 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
3552 - Don't crash on name lookup when we have no current consensus. Fixes
3553 bug 538; bugfix on 0.2.0.x.
3554 - Only Tors that want to mirror the v2 directory info should
3555 create the "cached-status" directory in their datadir. (All Tors
3556 used to create it.) Bugfix on 0.2.0.9-alpha.
3557 - Directory authorities should only automatically download Extra Info
3558 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
3561 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
3562 consumers. (We already do this on HUP.)
3563 - Authorities and caches fetch the v2 networkstatus documents
3564 less often, now that v3 is encouraged.
3565 - Add a new config option BridgeRelay that specifies you want to
3566 be a bridge relay. Right now the only difference is that it makes
3567 you answer begin_dir requests, and it makes you cache dir info,
3568 even if your DirPort isn't on.
3569 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
3570 ask about source, timestamp of arrival, purpose, etc. We need
3571 something like this to help Vidalia not do GeoIP lookups on bridge
3573 - Allow multiple HashedControlPassword config lines, to support
3574 multiple controller passwords.
3575 - Authorities now decide whether they're authoritative for a given
3576 router based on the router's purpose.
3577 - New config options AuthDirBadDir and AuthDirListBadDirs for
3578 authorities to mark certain relays as "bad directories" in the
3579 networkstatus documents. Also supports the "!baddir" directive in
3580 the approved-routers file.
3583 Changes in version 0.2.0.12-alpha - 2007-11-16
3584 This twelfth development snapshot fixes some more build problems as
3585 well as a few minor bugs.
3588 - Make it build on OpenBSD again. Patch from tup.
3589 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
3590 package-building for Red Hat, OS X, etc.
3592 o Minor bugfixes (on 0.1.2.x):
3593 - Changing the ExitPolicyRejectPrivate setting should cause us to
3594 rebuild our server descriptor.
3596 o Minor bugfixes (on 0.2.0.x):
3597 - When we're lacking a consensus, don't try to perform rendezvous
3598 operations. Reported by Karsten Loesing.
3599 - Fix a small memory leak whenever we decide against using a
3600 newly picked entry guard. Reported by Mike Perry.
3601 - When authorities detected more than two relays running on the same
3602 IP address, they were clearing all the status flags but forgetting
3603 to clear the "hsdir" flag. So clients were being told that a
3604 given relay was the right choice for a v2 hsdir lookup, yet they
3605 never had its descriptor because it was marked as 'not running'
3607 - If we're trying to fetch a bridge descriptor and there's no way
3608 the bridge authority could help us (for example, we don't know
3609 a digest, or there is no bridge authority), don't be so eager to
3610 fall back to asking the bridge authority.
3611 - If we're using bridges or have strictentrynodes set, and our
3612 chosen exit is in the same family as all our bridges/entry guards,
3613 then be flexible about families.
3616 - When we negotiate a v2 link-layer connection (not yet implemented),
3617 accept RELAY_EARLY cells and turn them into RELAY cells if we've
3618 negotiated a v1 connection for their next step. Initial code for
3622 Changes in version 0.2.0.11-alpha - 2007-11-12
3623 This eleventh development snapshot fixes some build problems with
3624 the previous snapshot. It also includes a more secure-by-default exit
3625 policy for relays, fixes an enormous memory leak for exit relays, and
3626 fixes another bug where servers were falling out of the directory list.
3629 - Exit policies now reject connections that are addressed to a
3630 relay's public (external) IP address too, unless
3631 ExitPolicyRejectPrivate is turned off. We do this because too
3632 many relays are running nearby to services that trust them based
3633 on network address. Bugfix on 0.1.2.x.
3636 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
3637 on every successful resolve. Reported by Mike Perry; bugfix
3639 - On authorities, never downgrade to old router descriptors simply
3640 because they're listed in the consensus. This created a catch-22
3641 where we wouldn't list a new descriptor because there was an
3642 old one in the consensus, and we couldn't get the new one in the
3643 consensus because we wouldn't list it. Possible fix for bug 548.
3644 Also, this might cause bug 543 to appear on authorities; if so,
3645 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
3647 o Packaging fixes on 0.2.0.10-alpha:
3648 - We were including instructions about what to do with the
3649 src/config/fallback-consensus file, but we weren't actually
3650 including it in the tarball. Disable all of that for now.
3653 - Allow people to say PreferTunnelledDirConns rather than
3654 PreferTunneledDirConns, for those alternate-spellers out there.
3657 - Don't reevaluate all the information from our consensus document
3658 just because we've downloaded a v2 networkstatus that we intend
3659 to cache. Fixes bug 545; bugfix on 0.2.0.x.
3662 Changes in version 0.2.0.10-alpha - 2007-11-10
3663 This tenth development snapshot adds a third v3 directory authority
3664 run by Mike Perry, adds most of Karsten Loesing's new hidden service
3665 descriptor format, fixes a bad crash bug and new bridge bugs introduced
3666 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
3667 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
3668 addresses many more minor issues.
3670 o New directory authorities:
3671 - Set up ides (run by Mike Perry) as the third v3 directory authority.
3674 - Allow tunnelled directory connections to ask for an encrypted
3675 "begin_dir" connection or an anonymized "uses a full Tor circuit"
3676 connection independently. Now we can make anonymized begin_dir
3677 connections for (e.g.) more secure hidden service posting and
3679 - More progress on proposal 114: code from Karsten Loesing to
3680 implement new hidden service descriptor format.
3681 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
3682 accommodate the growing number of servers that use the default
3683 and are reaching it.
3684 - Directory authorities use a new formula for selecting which nodes
3685 to advertise as Guards: they must be in the top 7/8 in terms of
3686 how long we have known about them, and above the median of those
3687 nodes in terms of weighted fractional uptime.
3688 - Make "not enough dir info yet" warnings describe *why* Tor feels
3689 it doesn't have enough directory info yet.
3692 - Stop servers from crashing if they set a Family option (or
3693 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
3695 - Make bridge users work again -- the move to v3 directories in
3696 0.2.0.9-alpha had introduced a number of bugs that made bridges
3697 no longer work for clients.
3698 - When the clock jumps forward a lot, do not allow the bandwidth
3699 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
3701 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
3702 - When the consensus lists a router descriptor that we previously were
3703 mirroring, but that we considered non-canonical, reload the
3704 descriptor as canonical. This fixes bug 543 where Tor servers
3705 would start complaining after a few days that they don't have
3706 enough directory information to build a circuit.
3707 - Consider replacing the current consensus when certificates arrive
3708 that make the pending consensus valid. Previously, we were only
3709 considering replacement when the new certs _didn't_ help.
3710 - Fix an assert error on startup if we didn't already have the
3711 consensus and certs cached in our datadirectory: we were caching
3712 the consensus in consensus_waiting_for_certs but then free'ing it
3714 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
3715 Request) if we need more v3 certs but we've already got pending
3716 requests for all of them.
3717 - Correctly back off from failing certificate downloads. Fixes
3719 - Authorities don't vote on the Running flag if they have been running
3720 for less than 30 minutes themselves. Fixes bug 547, where a newly
3721 started authority would vote that everyone was down.
3724 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
3725 it, it had no AES, and it hasn't seen any security patches since
3729 - Clients now hold circuitless TLS connections open for 1.5 times
3730 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
3731 rebuild a new circuit over them within that timeframe. Previously,
3732 they held them open only for KeepalivePeriod (5 minutes).
3733 - Use "If-Modified-Since" to avoid retrieving consensus
3734 networkstatuses that we already have.
3735 - When we have no consensus, check FallbackNetworkstatusFile (defaults
3736 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
3737 we start knowing some directory caches.
3738 - When we receive a consensus from the future, warn about skew.
3739 - Improve skew reporting: try to give the user a better log message
3740 about how skewed they are, and how much this matters.
3741 - When we have a certificate for an authority, believe that
3742 certificate's claims about the authority's IP address.
3743 - New --quiet command-line option to suppress the default console log.
3744 Good in combination with --hash-password.
3745 - Authorities send back an X-Descriptor-Not-New header in response to
3746 an accepted-but-discarded descriptor upload. Partially implements
3748 - Make the log message for "tls error. breaking." more useful.
3749 - Better log messages about certificate downloads, to attempt to
3750 track down the second incarnation of bug 546.
3752 o Minor features (bridges):
3753 - If bridge users set UpdateBridgesFromAuthority, but the digest
3754 they ask for is a 404 from the bridge authority, they now fall
3755 back to trying the bridge directly.
3756 - Bridges now use begin_dir to publish their server descriptor to
3757 the bridge authority, even when they haven't set TunnelDirConns.
3759 o Minor features (controller):
3760 - When reporting clock skew, and we know that the clock is _at least
3761 as skewed_ as some value, but we don't know the actual value,
3762 report the value as a "minimum skew."
3765 - Update linux-tor-prio.sh script to allow QoS based on the uid of
3766 the Tor process. Patch from Marco Bonetti with tweaks from Mike
3770 - Refuse to start if both ORPort and UseBridges are set. Bugfix
3771 on 0.2.0.x, suggested by Matt Edman.
3772 - Don't stop fetching descriptors when FetchUselessDescriptors is
3773 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
3774 reported by tup and ioerror.
3775 - Better log message on vote from unknown authority.
3776 - Don't log "Launching 0 request for 0 router" message.
3778 o Minor bugfixes (memory leaks):
3779 - Stop leaking memory every time we parse a v3 certificate. Bugfix
3781 - Stop leaking memory every time we load a v3 certificate. Bugfix
3782 on 0.2.0.1-alpha. Fixes bug 536.
3783 - Stop leaking a cached networkstatus on exit. Bugfix on
3785 - Stop leaking voter information every time we free a consensus.
3786 Bugfix on 0.2.0.3-alpha.
3787 - Stop leaking signed data every time we check a voter signature.
3788 Bugfix on 0.2.0.3-alpha.
3789 - Stop leaking a signature every time we fail to parse a consensus or
3790 a vote. Bugfix on 0.2.0.3-alpha.
3791 - Stop leaking v2_download_status_map on shutdown. Bugfix on
3793 - Stop leaking conn->nickname every time we make a connection to a
3794 Tor relay without knowing its expected identity digest (e.g. when
3795 using bridges). Bugfix on 0.2.0.3-alpha.
3797 - Minor bugfixes (portability):
3798 - Run correctly on platforms where rlim_t is larger than unsigned
3799 long, and/or where the real limit for number of open files is
3800 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
3801 particular, these may be needed for OS X 10.5.
3804 Changes in version 0.1.2.18 - 2007-10-28
3805 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
3806 hidden service introduction that were causing huge delays, and a big
3807 bug that was causing some servers to disappear from the network status
3808 lists for a few hours each day.
3810 o Major bugfixes (crashes):
3811 - If a connection is shut down abruptly because of something that
3812 happened inside connection_flushed_some(), do not call
3813 connection_finished_flushing(). Should fix bug 451:
3814 "connection_stop_writing: Assertion conn->write_event failed"
3815 Bugfix on 0.1.2.7-alpha.
3816 - Fix possible segfaults in functions called from
3817 rend_process_relay_cell().
3819 o Major bugfixes (hidden services):
3820 - Hidden services were choosing introduction points uniquely by
3821 hexdigest, but when constructing the hidden service descriptor
3822 they merely wrote the (potentially ambiguous) nickname.
3823 - Clients now use the v2 intro format for hidden service
3824 connections: they specify their chosen rendezvous point by identity
3825 digest rather than by (potentially ambiguous) nickname. These
3826 changes could speed up hidden service connections dramatically.
3828 o Major bugfixes (other):
3829 - Stop publishing a new server descriptor just because we get a
3830 HUP signal. This led (in a roundabout way) to some servers getting
3831 dropped from the networkstatus lists for a few hours each day.
3832 - When looking for a circuit to cannibalize, consider family as well
3833 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
3834 circuit cannibalization).
3835 - When a router wasn't listed in a new networkstatus, we were leaving
3836 the flags for that router alone -- meaning it remained Named,
3837 Running, etc -- even though absence from the networkstatus means
3838 that it shouldn't be considered to exist at all anymore. Now we
3839 clear all the flags for routers that fall out of the networkstatus
3840 consensus. Fixes bug 529.
3843 - Don't try to access (or alter) the state file when running
3844 --list-fingerprint or --verify-config or --hash-password. Resolves
3846 - When generating information telling us how to extend to a given
3847 router, do not try to include the nickname if it is
3848 absent. Resolves bug 467.
3849 - Fix a user-triggerable segfault in expand_filename(). (There isn't
3850 a way to trigger this remotely.)
3851 - When sending a status event to the controller telling it that an
3852 OR address is reachable, set the port correctly. (Previously we
3853 were reporting the dir port.)
3854 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
3855 command. Bugfix on 0.1.2.17.
3856 - When loading bandwidth history, do not believe any information in
3857 the future. Fixes bug 434.
3858 - When loading entry guard information, do not believe any information
3860 - When we have our clock set far in the future and generate an
3861 onion key, then re-set our clock to be correct, we should not stop
3862 the onion key from getting rotated.
3863 - On some platforms, accept() can return a broken address. Detect
3864 this more quietly, and deal accordingly. Fixes bug 483.
3865 - It's not actually an error to find a non-pending entry in the DNS
3866 cache when canceling a pending resolve. Don't log unless stuff
3867 is fishy. Resolves bug 463.
3868 - Don't reset trusted dir server list when we set a configuration
3869 option. Patch from Robert Hogan.
3870 - Don't try to create the datadir when running --verify-config or
3871 --hash-password. Resolves bug 540.
3874 Changes in version 0.2.0.9-alpha - 2007-10-24
3875 This ninth development snapshot switches clients to the new v3 directory
3876 system; allows servers to be listed in the network status even when they
3877 have the same nickname as a registered server; and fixes many other
3878 bugs including a big one that was causing some servers to disappear
3879 from the network status lists for a few hours each day.
3881 o Major features (directory system):
3882 - Clients now download v3 consensus networkstatus documents instead
3883 of v2 networkstatus documents. Clients and caches now base their
3884 opinions about routers on these consensus documents. Clients only
3885 download router descriptors listed in the consensus.
3886 - Authorities now list servers who have the same nickname as
3887 a different named server, but list them with a new flag,
3888 "Unnamed". Now we can list servers that happen to pick the same
3889 nickname as a server that registered two years ago and then
3890 disappeared. Partially implements proposal 122.
3891 - If the consensus lists a router as "Unnamed", the name is assigned
3892 to a different router: do not identify the router by that name.
3893 Partially implements proposal 122.
3894 - Authorities can now come to a consensus on which method to use to
3895 compute the consensus. This gives us forward compatibility.
3898 - Stop publishing a new server descriptor just because we HUP or
3899 when we find our DirPort to be reachable but won't actually publish
3900 it. New descriptors without any real changes are dropped by the
3901 authorities, and can screw up our "publish every 18 hours" schedule.
3903 - When a router wasn't listed in a new networkstatus, we were leaving
3904 the flags for that router alone -- meaning it remained Named,
3905 Running, etc -- even though absence from the networkstatus means
3906 that it shouldn't be considered to exist at all anymore. Now we
3907 clear all the flags for routers that fall out of the networkstatus
3908 consensus. Fixes bug 529; bugfix on 0.1.2.x.
3909 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
3910 extrainfo documents and then discard them immediately for not
3911 matching the latest router. Bugfix on 0.2.0.1-alpha.
3913 o Minor features (v3 directory protocol):
3914 - Allow tor-gencert to generate a new certificate without replacing
3916 - Allow certificates to include an address.
3917 - When we change our directory-cache settings, reschedule all voting
3918 and download operations.
3919 - Reattempt certificate downloads immediately on failure, as long as
3920 we haven't failed a threshold number of times yet.
3921 - Delay retrying consensus downloads while we're downloading
3922 certificates to verify the one we just got. Also, count getting a
3923 consensus that we already have (or one that isn't valid) as a failure,
3924 and count failing to get the certificates after 20 minutes as a
3926 - Build circuits and download descriptors even if our consensus is a
3927 little expired. (This feature will go away once authorities are
3930 o Minor features (router descriptor cache):
3931 - If we find a cached-routers file that's been sitting around for more
3932 than 28 days unmodified, then most likely it's a leftover from
3933 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
3935 - When we (as a cache) download a descriptor because it was listed
3936 in a consensus, remember when the consensus was supposed to expire,
3937 and don't expire the descriptor until then.
3939 o Minor features (performance):
3940 - Call routerlist_remove_old_routers() much less often. This should
3941 speed startup, especially on directory caches.
3942 - Don't try to launch new descriptor downloads quite so often when we
3943 already have enough directory information to build circuits.
3944 - Base64 decoding was actually showing up on our profile when parsing
3945 the initial descriptor file; switch to an in-process all-at-once
3946 implementation that's about 3.5x times faster than calling out to
3949 o Minor features (compilation):
3950 - Detect non-ASCII platforms (if any still exist) and refuse to
3951 build there: some of our code assumes that 'A' is 65 and so on.
3953 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
3954 - Make the "next period" votes into "current period" votes immediately
3955 after publishing the consensus; avoid a heisenbug that made them
3956 stick around indefinitely.
3957 - When we discard a vote as a duplicate, do not report this as
3959 - Treat missing v3 keys or certificates as an error when running as a
3960 v3 directory authority.
3961 - When we're configured to be a v3 authority, but we're only listed
3962 as a non-v3 authority in our DirServer line for ourself, correct
3964 - If an authority doesn't have a qualified hostname, just put
3965 its address in the vote. This fixes the problem where we referred to
3966 "moria on moria:9031."
3967 - Distinguish between detached signatures for the wrong period, and
3968 detached signatures for a divergent vote.
3969 - Fix a small memory leak when computing a consensus.
3970 - When there's no concensus, we were forming a vote every 30
3971 minutes, but writing the "valid-after" line in our vote based
3972 on our configured V3AuthVotingInterval: so unless the intervals
3973 matched up, we immediately rejected our own vote because it didn't
3974 start at the voting interval that caused us to construct a vote.
3976 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
3977 - Delete unverified-consensus when the real consensus is set.
3978 - Consider retrying a consensus networkstatus fetch immediately
3979 after one fails: don't wait 60 seconds to notice.
3980 - When fetching a consensus as a cache, wait until a newer consensus
3981 should exist before trying to replace the current one.
3982 - Use a more forgiving schedule for retrying failed consensus
3983 downloads than for other types.
3985 o Minor bugfixes (other directory issues):
3986 - Correct the implementation of "download votes by digest." Bugfix on
3988 - Authorities no longer send back "400 you're unreachable please fix
3989 it" errors to Tor servers that aren't online all the time. We're
3990 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
3992 o Minor bugfixes (controller):
3993 - Don't reset trusted dir server list when we set a configuration
3994 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
3995 - Respond to INT and TERM SIGNAL commands before we execute the
3996 signal, in case the signal shuts us down. We had a patch in
3997 0.1.2.1-alpha that tried to do this by queueing the response on
3998 the connection's buffer before shutting down, but that really
3999 isn't the same thing at all. Bug located by Matt Edman.
4001 o Minor bugfixes (misc):
4002 - Correctly check for bad options to the "PublishServerDescriptor"
4003 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
4004 - Stop leaking memory on failing case of base32_decode, and make
4005 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
4006 - Don't try to download extrainfo documents when we're trying to
4007 fetch enough directory info to build a circuit: having enough
4008 info should get priority. Bugfix on 0.2.0.x.
4009 - Don't complain that "your server has not managed to confirm that its
4010 ports are reachable" if we haven't been able to build any circuits
4011 yet. Bug found by spending four hours without a v3 consensus. Bugfix
4013 - Detect the reason for failing to mmap a descriptor file we just
4014 wrote, and give a more useful log message. Fixes bug 533. Bugfix
4017 o Code simplifications and refactoring:
4018 - Remove support for the old bw_accounting file: we've been storing
4019 bandwidth accounting information in the state file since
4020 0.1.2.5-alpha. This may result in bandwidth accounting errors
4021 if you try to upgrade from 0.1.1.x or earlier, or if you try to
4022 downgrade to 0.1.1.x or earlier.
4023 - New convenience code to locate a file within the DataDirectory.
4024 - Move non-authority functionality out of dirvote.c.
4025 - Refactor the arguments for router_pick_{directory_|trusteddir}server
4026 so that they all take the same named flags.
4029 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
4030 Unix users an easy way to script their Tor process (e.g. by
4031 adjusting bandwidth based on the time of the day).
4034 Changes in version 0.2.0.8-alpha - 2007-10-12
4035 This eighth development snapshot fixes a crash bug that's been bothering
4036 us since February 2007, lets bridge authorities store a list of bridge
4037 descriptors they've seen, gets v3 directory voting closer to working,
4038 starts caching v3 directory consensus documents on directory mirrors,
4039 and fixes a variety of smaller issues including some minor memory leaks.
4041 o Major features (router descriptor cache):
4042 - Store routers in a file called cached-descriptors instead of in
4043 cached-routers. Initialize cached-descriptors from cached-routers
4044 if the old format is around. The new format allows us to store
4045 annotations along with descriptors.
4046 - Use annotations to record the time we received each descriptor, its
4047 source, and its purpose.
4048 - Disable the SETROUTERPURPOSE controller command: it is now
4050 - Controllers should now specify cache=no or cache=yes when using
4051 the +POSTDESCRIPTOR command.
4052 - Bridge authorities now write bridge descriptors to disk, meaning
4053 we can export them to other programs and begin distributing them
4056 o Major features (directory authorities):
4057 - When a v3 authority is missing votes or signatures, it now tries
4059 - Directory authorities track weighted fractional uptime as well as
4060 weighted mean-time-between failures. WFU is suitable for deciding
4061 whether a node is "usually up", while MTBF is suitable for deciding
4062 whether a node is "likely to stay up." We need both, because
4063 "usually up" is a good requirement for guards, while "likely to
4064 stay up" is a good requirement for long-lived connections.
4066 o Major features (v3 directory system):
4067 - Caches now download v3 network status documents as needed,
4068 and download the descriptors listed in them.
4069 - All hosts now attempt to download and keep fresh v3 authority
4070 certificates, and re-attempt after failures.
4071 - More internal-consistency checks for vote parsing.
4073 o Major bugfixes (crashes):
4074 - If a connection is shut down abruptly because of something that
4075 happened inside connection_flushed_some(), do not call
4076 connection_finished_flushing(). Should fix bug 451. Bugfix on
4079 o Major bugfixes (performance):
4080 - Fix really bad O(n^2) performance when parsing a long list of
4081 routers: Instead of searching the entire list for an "extra-info "
4082 string which usually wasn't there, once for every routerinfo
4083 we read, just scan lines forward until we find one we like.
4085 - When we add data to a write buffer in response to the data on that
4086 write buffer getting low because of a flush, do not consider the
4087 newly added data as a candidate for immediate flushing, but rather
4088 make it wait until the next round of writing. Otherwise, we flush
4089 and refill recursively, and a single greedy TLS connection can
4090 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
4092 o Minor features (v3 authority system):
4093 - Add more ways for tools to download the votes that lead to the
4095 - Send a 503 when low on bandwidth and a vote, consensus, or
4096 certificate is requested.
4097 - If-modified-since is now implemented properly for all kinds of
4098 certificate requests.
4100 o Minor bugfixes (network statuses):
4101 - Tweak the implementation of proposal 109 slightly: allow at most
4102 two Tor servers on the same IP address, except if it's the location
4103 of a directory authority, in which case allow five. Bugfix on
4106 o Minor bugfixes (controller):
4107 - When sending a status event to the controller telling it that an
4108 OR address is reachable, set the port correctly. (Previously we
4109 were reporting the dir port.) Bugfix on 0.1.2.x.
4111 o Minor bugfixes (v3 directory system):
4112 - Fix logic to look up a cert by its signing key digest. Bugfix on
4114 - Only change the reply to a vote to "OK" if it's not already
4115 set. This gets rid of annoying "400 OK" log messages, which may
4116 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
4117 - When we get a valid consensus, recompute the voting schedule.
4118 - Base the valid-after time of a vote on the consensus voting
4119 schedule, not on our preferred schedule.
4120 - Make the return values and messages from signature uploads and
4121 downloads more sensible.
4122 - Fix a memory leak when serving votes and consensus documents, and
4123 another when serving certificates.
4125 o Minor bugfixes (performance):
4126 - Use a slightly simpler string hashing algorithm (copying Python's
4127 instead of Java's) and optimize our digest hashing algorithm to take
4128 advantage of 64-bit platforms and to remove some possibly-costly
4130 - Fix a minor memory leak whenever we parse guards from our state
4131 file. Bugfix on 0.2.0.7-alpha.
4132 - Fix a minor memory leak whenever we write out a file. Bugfix on
4134 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
4135 command. Bugfix on 0.2.0.5-alpha.
4137 o Minor bugfixes (portability):
4138 - On some platforms, accept() can return a broken address. Detect
4139 this more quietly, and deal accordingly. Fixes bug 483.
4140 - Stop calling tor_strlower() on uninitialized memory in some cases.
4141 Bugfix in 0.2.0.7-alpha.
4143 o Minor bugfixes (usability):
4144 - Treat some 403 responses from directory servers as INFO rather than
4145 WARN-severity events.
4146 - It's not actually an error to find a non-pending entry in the DNS
4147 cache when canceling a pending resolve. Don't log unless stuff is
4148 fishy. Resolves bug 463.
4150 o Minor bugfixes (anonymity):
4151 - Never report that we've used more bandwidth than we're willing to
4152 relay: it leaks how much non-relay traffic we're using. Resolves
4154 - When looking for a circuit to cannibalize, consider family as well
4155 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
4156 circuit cannibalization).
4158 o Code simplifications and refactoring:
4159 - Make a bunch of functions static. Remove some dead code.
4160 - Pull out about a third of the really big routerlist.c; put it in a
4161 new module, networkstatus.c.
4162 - Merge the extra fields in local_routerstatus_t back into
4163 routerstatus_t: we used to need one routerstatus_t for each
4164 authority's opinion, plus a local_routerstatus_t for the locally
4165 computed consensus opinion. To save space, we put the locally
4166 modified fields into local_routerstatus_t, and only the common
4167 stuff into routerstatus_t. But once v3 directories are in use,
4168 clients and caches will no longer need to hold authority opinions;
4169 thus, the rationale for keeping the types separate is now gone.
4170 - Make the code used to reschedule and reattempt downloads more
4172 - Turn all 'Are we a directory server/mirror?' logic into a call to
4174 - Remove the code to generate the oldest (v1) directory format.
4175 The code has been disabled since 0.2.0.5-alpha.
4178 Changes in version 0.2.0.7-alpha - 2007-09-21
4179 This seventh development snapshot makes bridges work again, makes bridge
4180 authorities work for the first time, fixes two huge performance flaws
4181 in hidden services, and fixes a variety of minor issues.
4183 o New directory authorities:
4184 - Set up moria1 and tor26 as the first v3 directory authorities. See
4185 doc/spec/dir-spec.txt for details on the new directory design.
4187 o Major bugfixes (crashes):
4188 - Fix possible segfaults in functions called from
4189 rend_process_relay_cell(). Bugfix on 0.1.2.x.
4191 o Major bugfixes (bridges):
4192 - Fix a bug that made servers send a "404 Not found" in response to
4193 attempts to fetch their server descriptor. This caused Tor servers
4194 to take many minutes to establish reachability for their DirPort,
4195 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
4196 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
4197 users configure that and specify a bridge with an identity
4198 fingerprint, now they will lookup the bridge descriptor at the
4199 default bridge authority via a one-hop tunnel, but once circuits
4200 are established they will switch to a three-hop tunnel for later
4201 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
4203 o Major bugfixes (hidden services):
4204 - Hidden services were choosing introduction points uniquely by
4205 hexdigest, but when constructing the hidden service descriptor
4206 they merely wrote the (potentially ambiguous) nickname.
4207 - Clients now use the v2 intro format for hidden service
4208 connections: they specify their chosen rendezvous point by identity
4209 digest rather than by (potentially ambiguous) nickname. Both
4210 are bugfixes on 0.1.2.x, and they could speed up hidden service
4211 connections dramatically. Thanks to Karsten Loesing.
4213 o Minor features (security):
4214 - As a client, do not believe any server that tells us that an
4215 address maps to an internal address space.
4216 - Make it possible to enable HashedControlPassword and
4217 CookieAuthentication at the same time.
4219 o Minor features (guard nodes):
4220 - Tag every guard node in our state file with the version that
4221 we believe added it, or with our own version if we add it. This way,
4222 if a user temporarily runs an old version of Tor and then switches
4223 back to a new one, she doesn't automatically lose her guards.
4225 o Minor features (speed):
4226 - When implementing AES counter mode, update only the portions of the
4227 counter buffer that need to change, and don't keep separate
4228 network-order and host-order counters when they are the same (i.e.,
4229 on big-endian hosts.)
4231 o Minor features (controller):
4232 - Accept LF instead of CRLF on controller, since some software has a
4233 hard time generating real Internet newlines.
4234 - Add GETINFO values for the server status events
4235 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
4239 - Routers no longer include bandwidth-history lines in their
4240 descriptors; this information is already available in extra-info
4241 documents, and including it in router descriptors took up 60%
4242 (!) of compressed router descriptor downloads. Completes
4243 implementation of proposal 104.
4244 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
4245 and TorControl.py, as they use the old v0 controller protocol,
4246 and are obsoleted by TorFlow anyway.
4247 - Drop support for v1 rendezvous descriptors, since we never used
4248 them anyway, and the code has probably rotted by now. Based on
4249 patch from Karsten Loesing.
4250 - On OSX, stop warning the user that kqueue support in libevent is
4251 "experimental", since it seems to have worked fine for ages.
4254 - When generating information telling us how to extend to a given
4255 router, do not try to include the nickname if it is absent. Fixes
4256 bug 467. Bugfix on 0.2.0.3-alpha.
4257 - Fix a user-triggerable (but not remotely-triggerable) segfault
4258 in expand_filename(). Bugfix on 0.1.2.x.
4259 - Fix a memory leak when freeing incomplete requests from DNSPort.
4260 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
4261 - Don't try to access (or alter) the state file when running
4262 --list-fingerprint or --verify-config or --hash-password. (Resolves
4263 bug 499.) Bugfix on 0.1.2.x.
4264 - Servers used to decline to publish their DirPort if their
4265 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
4266 were below a threshold. Now they only look at BandwidthRate and
4267 RelayBandwidthRate. Bugfix on 0.1.2.x.
4268 - Remove an optimization in the AES counter-mode code that assumed
4269 that the counter never exceeded 2^68. When the counter can be set
4270 arbitrarily as an IV (as it is by Karsten's new hidden services
4271 code), this assumption no longer holds. Bugfix on 0.1.2.x.
4272 - Resume listing "AUTHORITY" flag for authorities in network status.
4273 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
4275 o Code simplifications and refactoring:
4276 - Revamp file-writing logic so we don't need to have the entire
4277 contents of a file in memory at once before we write to disk. Tor,
4279 - Turn "descriptor store" into a full-fledged type.
4280 - Move all NT services code into a separate source file.
4281 - Unify all code that computes medians, percentile elements, etc.
4282 - Get rid of a needless malloc when parsing address policies.
4285 Changes in version 0.1.2.17 - 2007-08-30
4286 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
4287 X bundles. Vidalia 0.0.14 makes authentication required for the
4288 ControlPort in the default configuration, which addresses important
4289 security risks. Everybody who uses Vidalia (or another controller)
4292 In addition, this Tor update fixes major load balancing problems with
4293 path selection, which should speed things up a lot once many people
4296 o Major bugfixes (security):
4297 - We removed support for the old (v0) control protocol. It has been
4298 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
4299 become more of a headache than it's worth.
4301 o Major bugfixes (load balancing):
4302 - When choosing nodes for non-guard positions, weight guards
4303 proportionally less, since they already have enough load. Patch
4305 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
4306 will allow fast Tor servers to get more attention.
4307 - When we're upgrading from an old Tor version, forget our current
4308 guards and pick new ones according to the new weightings. These
4309 three load balancing patches could raise effective network capacity
4310 by a factor of four. Thanks to Mike Perry for measurements.
4312 o Major bugfixes (stream expiration):
4313 - Expire not-yet-successful application streams in all cases if
4314 they've been around longer than SocksTimeout. Right now there are
4315 some cases where the stream will live forever, demanding a new
4316 circuit every 15 seconds. Fixes bug 454; reported by lodger.
4318 o Minor features (controller):
4319 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
4320 is valid before any authentication has been received. It tells
4321 a controller what kind of authentication is expected, and what
4322 protocol is spoken. Implements proposal 119.
4324 o Minor bugfixes (performance):
4325 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
4326 greatly speeding up loading cached-routers from disk on startup.
4327 - Disable sentinel-based debugging for buffer code: we squashed all
4328 the bugs that this was supposed to detect a long time ago, and now
4329 its only effect is to change our buffer sizes from nice powers of
4330 two (which platform mallocs tend to like) to values slightly over
4331 powers of two (which make some platform mallocs sad).
4333 o Minor bugfixes (misc):
4334 - If exit bandwidth ever exceeds one third of total bandwidth, then
4335 use the correct formula to weight exit nodes when choosing paths.
4336 Based on patch from Mike Perry.
4337 - Choose perfectly fairly among routers when choosing by bandwidth and
4338 weighting by fraction of bandwidth provided by exits. Previously, we
4339 would choose with only approximate fairness, and correct ourselves
4340 if we ran off the end of the list.
4341 - If we require CookieAuthentication but we fail to write the
4342 cookie file, we would warn but not exit, and end up in a state
4343 where no controller could authenticate. Now we exit.
4344 - If we require CookieAuthentication, stop generating a new cookie
4345 every time we change any piece of our config.
4346 - Refuse to start with certain directory authority keys, and
4347 encourage people using them to stop.
4348 - Terminate multi-line control events properly. Original patch
4350 - Fix a minor memory leak when we fail to find enough suitable
4351 servers to choose a circuit.
4352 - Stop leaking part of the descriptor when we run into a particularly
4353 unparseable piece of it.
4356 Changes in version 0.2.0.6-alpha - 2007-08-26
4357 This sixth development snapshot features a new Vidalia version in the
4358 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
4359 the ControlPort in the default configuration, which addresses important
4362 In addition, this snapshot fixes major load balancing problems
4363 with path selection, which should speed things up a lot once many
4364 people have upgraded. The directory authorities also use a new
4365 mean-time-between-failure approach to tracking which servers are stable,
4366 rather than just looking at the most recent uptime.
4368 o New directory authorities:
4369 - Set up Tonga as the default bridge directory authority.
4372 - Directory authorities now track servers by weighted
4373 mean-times-between-failures. When we have 4 or more days of data,
4374 use measured MTBF rather than declared uptime to decide whether
4375 to call a router Stable. Implements proposal 108.
4377 o Major bugfixes (load balancing):
4378 - When choosing nodes for non-guard positions, weight guards
4379 proportionally less, since they already have enough load. Patch
4381 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
4382 will allow fast Tor servers to get more attention.
4383 - When we're upgrading from an old Tor version, forget our current
4384 guards and pick new ones according to the new weightings. These
4385 three load balancing patches could raise effective network capacity
4386 by a factor of four. Thanks to Mike Perry for measurements.
4388 o Major bugfixes (descriptor parsing):
4389 - Handle unexpected whitespace better in malformed descriptors. Bug
4390 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
4393 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
4394 GETINFO for Torstat to use until it can switch to using extrainfos.
4395 - Optionally (if built with -DEXPORTMALLINFO) export the output
4396 of mallinfo via http, as tor/mallinfo.txt. Only accessible
4400 - Do not intermix bridge routers with controller-added
4401 routers. (Bugfix on 0.2.0.x)
4402 - Do not fail with an assert when accept() returns an unexpected
4403 address family. Addresses but does not wholly fix bug 483. (Bugfix
4405 - Let directory authorities startup even when they can't generate
4406 a descriptor immediately, e.g. because they don't know their
4408 - Stop putting the authentication cookie in a file called "0"
4409 in your working directory if you don't specify anything for the
4410 new CookieAuthFile option. Reported by Matt Edman.
4411 - Make it possible to read the PROTOCOLINFO response in a way that
4412 conforms to our control-spec. Reported by Matt Edman.
4413 - Fix a minor memory leak when we fail to find enough suitable
4414 servers to choose a circuit. Bugfix on 0.1.2.x.
4415 - Stop leaking part of the descriptor when we run into a particularly
4416 unparseable piece of it. Bugfix on 0.1.2.x.
4417 - Unmap the extrainfo cache file on exit.
4420 Changes in version 0.2.0.5-alpha - 2007-08-19
4421 This fifth development snapshot fixes compilation on Windows again;
4422 fixes an obnoxious client-side bug that slowed things down and put
4423 extra load on the network; gets us closer to using the v3 directory
4424 voting scheme; makes it easier for Tor controllers to use cookie-based
4425 authentication; and fixes a variety of other bugs.
4428 - Version 1 directories are no longer generated in full. Instead,
4429 authorities generate and serve "stub" v1 directories that list
4430 no servers. This will stop Tor versions 0.1.0.x and earlier from
4431 working, but (for security reasons) nobody should be running those
4434 o Major bugfixes (compilation, 0.2.0.x):
4435 - Try to fix Win32 compilation again: improve checking for IPv6 types.
4436 - Try to fix MSVC compilation: build correctly on platforms that do
4437 not define s6_addr16 or s6_addr32.
4438 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
4441 o Major bugfixes (stream expiration):
4442 - Expire not-yet-successful application streams in all cases if
4443 they've been around longer than SocksTimeout. Right now there are
4444 some cases where the stream will live forever, demanding a new
4445 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
4448 o Minor features (directory servers):
4449 - When somebody requests a list of statuses or servers, and we have
4450 none of those, return a 404 rather than an empty 200.
4452 o Minor features (directory voting):
4453 - Store v3 consensus status consensuses on disk, and reload them
4456 o Minor features (security):
4457 - Warn about unsafe ControlPort configurations.
4458 - Refuse to start with certain directory authority keys, and
4459 encourage people using them to stop.
4461 o Minor features (controller):
4462 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
4463 is valid before any authentication has been received. It tells
4464 a controller what kind of authentication is expected, and what
4465 protocol is spoken. Implements proposal 119.
4466 - New config option CookieAuthFile to choose a new location for the
4467 cookie authentication file, and config option
4468 CookieAuthFileGroupReadable to make it group-readable.
4470 o Minor features (unit testing):
4471 - Add command-line arguments to unit-test executable so that we can
4472 invoke any chosen test from the command line rather than having
4473 to run the whole test suite at once; and so that we can turn on
4474 logging for the unit tests.
4476 o Minor bugfixes (on 0.1.2.x):
4477 - If we require CookieAuthentication but we fail to write the
4478 cookie file, we would warn but not exit, and end up in a state
4479 where no controller could authenticate. Now we exit.
4480 - If we require CookieAuthentication, stop generating a new cookie
4481 every time we change any piece of our config.
4482 - When loading bandwidth history, do not believe any information in
4483 the future. Fixes bug 434.
4484 - When loading entry guard information, do not believe any information
4486 - When we have our clock set far in the future and generate an
4487 onion key, then re-set our clock to be correct, we should not stop
4488 the onion key from getting rotated.
4489 - Clean up torrc sample config file.
4490 - Do not automatically run configure from autogen.sh. This
4491 non-standard behavior tended to annoy people who have built other
4494 o Minor bugfixes (on 0.2.0.x):
4495 - Fix a bug with AutomapHostsOnResolve that would always cause
4496 the second request to fail. Bug reported by Kate. Bugfix on
4498 - Fix a bug in ADDRMAP controller replies that would sometimes
4499 try to print a NULL. Patch from tup.
4500 - Read v3 directory authority keys from the right location.
4501 - Numerous bugfixes to directory voting code.
4504 Changes in version 0.1.2.16 - 2007-08-01
4505 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
4506 remote attacker in certain situations to rewrite the user's torrc
4507 configuration file. This can completely compromise anonymity of users
4508 in most configurations, including those running the Vidalia bundles,
4509 TorK, etc. Or worse.
4511 o Major security fixes:
4512 - Close immediately after missing authentication on control port;
4513 do not allow multiple authentication attempts.
4516 Changes in version 0.2.0.4-alpha - 2007-08-01
4517 This fourth development snapshot fixes a critical security vulnerability
4518 for most users, specifically those running Vidalia, TorK, etc. Everybody
4519 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
4521 o Major security fixes:
4522 - Close immediately after missing authentication on control port;
4523 do not allow multiple authentication attempts.
4525 o Major bugfixes (compilation):
4526 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
4529 o Minor features (performance):
4530 - Be even more aggressive about releasing RAM from small
4531 empty buffers. Thanks to our free-list code, this shouldn't be too
4532 performance-intensive.
4533 - Disable sentinel-based debugging for buffer code: we squashed all
4534 the bugs that this was supposed to detect a long time ago, and
4535 now its only effect is to change our buffer sizes from nice
4536 powers of two (which platform mallocs tend to like) to values
4537 slightly over powers of two (which make some platform mallocs sad).
4538 - Log malloc statistics from mallinfo() on platforms where it
4542 Changes in version 0.2.0.3-alpha - 2007-07-29
4543 This third development snapshot introduces new experimental
4544 blocking-resistance features and a preliminary version of the v3
4545 directory voting design, and includes many other smaller features
4549 - The first pieces of our "bridge" design for blocking-resistance
4550 are implemented. People can run bridge directory authorities;
4551 people can run bridges; and people can configure their Tor clients
4552 with a set of bridges to use as the first hop into the Tor network.
4553 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
4555 - Create listener connections before we setuid to the configured
4556 User and Group. Now non-Windows users can choose port values
4557 under 1024, start Tor as root, and have Tor bind those ports
4558 before it changes to another UID. (Windows users could already
4560 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
4561 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
4562 on "vserver" accounts. (Patch from coderman.)
4563 - Be even more aggressive about separating local traffic from relayed
4564 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
4566 o Major features (experimental):
4567 - First cut of code for "v3 dir voting": directory authorities will
4568 vote on a common network status document rather than each publishing
4569 their own opinion. This code needs more testing and more corner-case
4570 handling before it's ready for use.
4573 - Directory authorities now call routers Fast if their bandwidth is
4574 at least 100KB/s, and consider their bandwidth adequate to be a
4575 Guard if it is at least 250KB/s, no matter the medians. This fix
4576 complements proposal 107. [Bugfix on 0.1.2.x]
4577 - Directory authorities now never mark more than 3 servers per IP as
4578 Valid and Running. (Implements proposal 109, by Kevin Bauer and
4580 - Minor change to organizationName and commonName generation
4581 procedures in TLS certificates during Tor handshakes, to invalidate
4582 some earlier censorware approaches. This is not a long-term
4583 solution, but applying it will give us a bit of time to look into
4584 the epidemiology of countermeasures as they spread.
4586 o Major bugfixes (directory):
4587 - Rewrite directory tokenization code to never run off the end of
4588 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
4590 o Minor features (controller):
4591 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
4592 match requests to applications. (Patch from Robert Hogan.)
4593 - Report address and port correctly on connections to DNSPort. (Patch
4595 - Add a RESOLVE command to launch hostname lookups. (Original patch
4597 - Add GETINFO status/enough-dir-info to let controllers tell whether
4598 Tor has downloaded sufficient directory information. (Patch
4600 - You can now use the ControlSocket option to tell Tor to listen for
4601 controller connections on Unix domain sockets on systems that
4602 support them. (Patch from Peter Palfrader.)
4603 - STREAM NEW events are generated for DNSPort requests and for
4604 tunneled directory connections. (Patch from Robert Hogan.)
4605 - New "GETINFO address-mappings/*" command to get address mappings
4606 with expiry information. "addr-mappings/*" is now deprecated.
4609 o Minor features (misc):
4610 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
4612 - The tor-gencert tool for v3 directory authorities now creates all
4613 files as readable to the file creator only, and write-protects
4614 the authority identity key.
4615 - When dumping memory usage, list bytes used in buffer memory
4617 - When running with dmalloc, dump more stats on hup and on exit.
4618 - Directory authorities now fail quickly and (relatively) harmlessly
4619 if they generate a network status document that is somehow
4622 o Traffic load balancing improvements:
4623 - If exit bandwidth ever exceeds one third of total bandwidth, then
4624 use the correct formula to weight exit nodes when choosing paths.
4625 (Based on patch from Mike Perry.)
4626 - Choose perfectly fairly among routers when choosing by bandwidth and
4627 weighting by fraction of bandwidth provided by exits. Previously, we
4628 would choose with only approximate fairness, and correct ourselves
4629 if we ran off the end of the list. [Bugfix on 0.1.2.x]
4631 o Performance improvements:
4632 - Be more aggressive with freeing buffer RAM or putting it on the
4634 - Use Critical Sections rather than Mutexes for synchronizing threads
4635 on win32; Mutexes are heavier-weight, and designed for synchronizing
4638 o Deprecated and removed features:
4639 - RedirectExits is now deprecated.
4640 - Stop allowing address masks that do not correspond to bit prefixes.
4641 We have warned about these for a really long time; now it's time
4642 to reject them. (Patch from croup.)
4644 o Minor bugfixes (directory):
4645 - Fix another crash bug related to extra-info caching. (Bug found by
4646 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
4647 - Directories no longer return a "304 not modified" when they don't
4648 have the networkstatus the client asked for. Also fix a memory
4649 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
4650 - We had accidentally labelled 0.1.2.x directory servers as not
4651 suitable for begin_dir requests, and had labelled no directory
4652 servers as suitable for uploading extra-info documents. [Bugfix
4655 o Minor bugfixes (dns):
4656 - Fix a crash when DNSPort is set more than once. (Patch from Robert
4657 Hogan.) [Bugfix on 0.2.0.2-alpha]
4658 - Add DNSPort connections to the global connection list, so that we
4659 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
4661 - Fix a dangling reference that could lead to a crash when DNSPort is
4662 changed or closed (Patch from Robert Hogan.) [Bugfix on
4665 o Minor bugfixes (controller):
4666 - Provide DNS expiry times in GMT, not in local time. For backward
4667 compatibility, ADDRMAP events only provide GMT expiry in an extended
4668 field. "GETINFO address-mappings" always does the right thing.
4669 - Use CRLF line endings properly in NS events.
4670 - Terminate multi-line control events properly. (Original patch
4671 from tup.) [Bugfix on 0.1.2.x-alpha]
4672 - Do not include spaces in SOURCE_ADDR fields in STREAM
4673 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
4676 Changes in version 0.1.2.15 - 2007-07-17
4677 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
4678 problems, fixes compilation on BSD, and fixes a variety of other
4679 bugs. Everybody should upgrade.
4681 o Major bugfixes (compilation):
4682 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
4684 o Major bugfixes (crashes):
4685 - Try even harder not to dereference the first character after
4686 an mmap(). Reported by lodger.
4687 - Fix a crash bug in directory authorities when we re-number the
4688 routerlist while inserting a new router.
4689 - When the cached-routers file is an even multiple of the page size,
4690 don't run off the end and crash. (Fixes bug 455; based on idea
4692 - Fix eventdns.c behavior on Solaris: It is critical to include
4693 orconfig.h _before_ sys/types.h, so that we can get the expected
4694 definition of _FILE_OFFSET_BITS.
4696 o Major bugfixes (security):
4697 - Fix a possible buffer overrun when using BSD natd support. Bug
4699 - When sending destroy cells from a circuit's origin, don't include
4700 the reason for tearing down the circuit. The spec says we didn't,
4701 and now we actually don't. Reported by lodger.
4702 - Keep streamids from different exits on a circuit separate. This
4703 bug may have allowed other routers on a given circuit to inject
4704 cells into streams. Reported by lodger; fixes bug 446.
4705 - If there's a never-before-connected-to guard node in our list,
4706 never choose any guards past it. This way we don't expand our
4707 guard list unless we need to.
4709 o Minor bugfixes (guard nodes):
4710 - Weight guard selection by bandwidth, so that low-bandwidth nodes
4711 don't get overused as guards.
4713 o Minor bugfixes (directory):
4714 - Correctly count the number of authorities that recommend each
4715 version. Previously, we were under-counting by 1.
4716 - Fix a potential crash bug when we load many server descriptors at
4717 once and some of them make others of them obsolete. Fixes bug 458.
4719 o Minor bugfixes (hidden services):
4720 - Stop tearing down the whole circuit when the user asks for a
4721 connection to a port that the hidden service didn't configure.
4724 o Minor bugfixes (misc):
4725 - On Windows, we were preventing other processes from reading
4726 cached-routers while Tor was running. Reported by janbar.
4727 - Fix a possible (but very unlikely) bug in picking routers by
4728 bandwidth. Add a log message to confirm that it is in fact
4729 unlikely. Patch from lodger.
4730 - Backport a couple of memory leak fixes.
4731 - Backport miscellaneous cosmetic bugfixes.
4734 Changes in version 0.2.0.2-alpha - 2007-06-02
4735 o Major bugfixes on 0.2.0.1-alpha:
4736 - Fix an assertion failure related to servers without extra-info digests.
4737 Resolves bugs 441 and 442.
4739 o Minor features (directory):
4740 - Support "If-Modified-Since" when answering HTTP requests for
4741 directories, running-routers documents, and network-status documents.
4742 (There's no need to support it for router descriptors, since those
4743 are downloaded by descriptor digest.)
4745 o Minor build issues:
4746 - Clear up some MIPSPro compiler warnings.
4747 - When building from a tarball on a machine that happens to have SVK
4748 installed, report the micro-revision as whatever version existed
4749 in the tarball, not as "x".
4752 Changes in version 0.2.0.1-alpha - 2007-06-01
4753 This early development snapshot provides new features for people running
4754 Tor as both a client and a server (check out the new RelayBandwidth
4755 config options); lets Tor run as a DNS proxy; and generally moves us
4756 forward on a lot of fronts.
4758 o Major features, server usability:
4759 - New config options RelayBandwidthRate and RelayBandwidthBurst:
4760 a separate set of token buckets for relayed traffic. Right now
4761 relayed traffic is defined as answers to directory requests, and
4762 OR connections that don't have any local circuits on them.
4764 o Major features, client usability:
4765 - A client-side DNS proxy feature to replace the need for
4766 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
4767 for DNS requests on port 9999, use the Tor network to resolve them
4768 anonymously, and send the reply back like a regular DNS server.
4769 The code still only implements a subset of DNS.
4770 - Make PreferTunneledDirConns and TunnelDirConns work even when
4771 we have no cached directory info. This means Tor clients can now
4772 do all of their connections protected by TLS.
4774 o Major features, performance and efficiency:
4775 - Directory authorities accept and serve "extra info" documents for
4776 routers. These documents contain fields from router descriptors
4777 that aren't usually needed, and that use a lot of excess
4778 bandwidth. Once these fields are removed from router descriptors,
4779 the bandwidth savings should be about 60%. [Partially implements
4781 - Servers upload extra-info documents to any authority that accepts
4782 them. Authorities (and caches that have been configured to download
4783 extra-info documents) download them as needed. [Partially implements
4785 - Change the way that Tor buffers data that it is waiting to write.
4786 Instead of queueing data cells in an enormous ring buffer for each
4787 client->OR or OR->OR connection, we now queue cells on a separate
4788 queue for each circuit. This lets us use less slack memory, and
4789 will eventually let us be smarter about prioritizing different kinds
4791 - Use memory pools to allocate cells with better speed and memory
4792 efficiency, especially on platforms where malloc() is inefficient.
4793 - Stop reading on edge connections when their corresponding circuit
4794 buffers are full; start again as the circuits empty out.
4796 o Major features, other:
4797 - Add an HSAuthorityRecordStats option that hidden service authorities
4798 can use to track statistics of overall hidden service usage without
4799 logging information that would be very useful to an attacker.
4800 - Start work implementing multi-level keys for directory authorities:
4801 Add a standalone tool to generate key certificates. (Proposal 103.)
4804 - Directory authorities now call routers Stable if they have an
4805 uptime of at least 30 days, even if that's not the median uptime
4806 in the network. Implements proposal 107, suggested by Kevin Bauer
4809 o Minor fixes (resource management):
4810 - Count the number of open sockets separately from the number
4811 of active connection_t objects. This will let us avoid underusing
4812 our allocated connection limit.
4813 - We no longer use socket pairs to link an edge connection to an
4814 anonymous directory connection or a DirPort test connection.
4815 Instead, we track the link internally and transfer the data
4816 in-process. This saves two sockets per "linked" connection (at the
4817 client and at the server), and avoids the nasty Windows socketpair()
4819 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
4820 for every single inactive connection_t. Free items from the
4821 4k/16k-buffer free lists when they haven't been used for a while.
4823 o Minor features (build):
4824 - Make autoconf search for libevent, openssl, and zlib consistently.
4825 - Update deprecated macros in configure.in.
4826 - When warning about missing headers, tell the user to let us
4827 know if the compile succeeds anyway, so we can downgrade the
4829 - Include the current subversion revision as part of the version
4830 string: either fetch it directly if we're in an SVN checkout, do
4831 some magic to guess it if we're in an SVK checkout, or use
4832 the last-detected version if we're building from a .tar.gz.
4833 Use this version consistently in log messages.
4835 o Minor features (logging):
4836 - Always prepend "Bug: " to any log message about a bug.
4837 - Put a platform string (e.g. "Linux i686") in the startup log
4838 message, so when people paste just their logs, we know if it's
4839 OpenBSD or Windows or what.
4840 - When logging memory usage, break down memory used in buffers by
4843 o Minor features (directory system):
4844 - New config option V2AuthoritativeDirectory that all directory
4845 authorities should set. This will let future authorities choose
4846 not to serve V2 directory information.
4847 - Directory authorities allow multiple router descriptors and/or extra
4848 info documents to be uploaded in a single go. This will make
4849 implementing proposal 104 simpler.
4851 o Minor features (controller):
4852 - Add a new config option __DisablePredictedCircuits designed for
4853 use by the controller, when we don't want Tor to build any circuits
4855 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
4856 so we can exit from the middle of the circuit.
4857 - Implement "getinfo status/circuit-established".
4858 - Implement "getinfo status/version/..." so a controller can tell
4859 whether the current version is recommended, and whether any versions
4860 are good, and how many authorities agree. (Patch from shibz.)
4862 o Minor features (hidden services):
4863 - Allow multiple HiddenServicePort directives with the same virtual
4864 port; when they occur, the user is sent round-robin to one
4865 of the target ports chosen at random. Partially fixes bug 393 by
4866 adding limited ad-hoc round-robining.
4868 o Minor features (other):
4870 - Add a new AutomapHostsOnResolve option: when it is enabled, any
4871 resolve request for hosts matching a given pattern causes Tor to
4872 generate an internal virtual address mapping for that host. This
4873 allows DNSPort to work sensibly with hidden service users. By
4874 default, .exit and .onion addresses are remapped; the list of
4875 patterns can be reconfigured with AutomapHostsSuffixes.
4876 - Add an "-F" option to tor-resolve to force a resolve for a .onion
4877 address. Thanks to the AutomapHostsOnResolve option, this is no
4878 longer a completely silly thing to do.
4879 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
4880 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
4881 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
4882 minus 1 byte: the actual maximum declared bandwidth.
4885 - Removed support for the old binary "version 0" controller protocol.
4886 This has been deprecated since 0.1.1, and warnings have been issued
4887 since 0.1.2. When we encounter a v0 control message, we now send
4888 back an error and close the connection.
4889 - Remove the old "dns worker" server DNS code: it hasn't been default
4890 since 0.1.2.2-alpha, and all the servers seem to be using the new
4893 o Minor bugfixes (portability):
4894 - Even though Windows is equally happy with / and \ as path separators,
4895 try to use \ consistently on Windows and / consistently on Unix: it
4896 makes the log messages nicer.
4897 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
4898 - Read resolv.conf files correctly on platforms where read() returns
4899 partial results on small file reads.
4901 o Minor bugfixes (directory):
4902 - Correctly enforce that elements of directory objects do not appear
4903 more often than they are allowed to appear.
4904 - When we are reporting the DirServer line we just parsed, we were
4905 logging the second stanza of the key fingerprint, not the first.
4907 o Minor bugfixes (logging):
4908 - When we hit an EOF on a log (probably because we're shutting down),
4909 don't try to remove the log from the list: just mark it as
4910 unusable. (Bulletproofs against bug 222.)
4912 o Minor bugfixes (other):
4913 - In the exitlist script, only consider the most recently published
4914 server descriptor for each server. Also, when the user requests
4915 a list of servers that _reject_ connections to a given address,
4916 explicitly exclude the IPs that also have servers that accept
4917 connections to that address. (Resolves bug 405.)
4918 - Stop allowing hibernating servers to be "stable" or "fast".
4919 - On Windows, we were preventing other processes from reading
4920 cached-routers while Tor was running. (Reported by janbar)
4921 - Make the NodeFamilies config option work. (Reported by
4922 lodger -- it has never actually worked, even though we added it
4924 - Check return values from pthread_mutex functions.
4925 - Don't save non-general-purpose router descriptors to the disk cache,
4926 because we have no way of remembering what their purpose was when
4928 - Add even more asserts to hunt down bug 417.
4929 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
4930 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
4931 Add a log message to confirm that it is in fact unlikely.
4933 o Minor bugfixes (controller):
4934 - Make 'getinfo fingerprint' return a 551 error if we're not a
4935 server, so we match what the control spec claims we do. Reported
4937 - Fix a typo in an error message when extendcircuit fails that
4938 caused us to not follow the \r\n-based delimiter protocol. Reported
4941 o Code simplifications and refactoring:
4942 - Stop passing around circuit_t and crypt_path_t pointers that are
4943 implicit in other procedure arguments.
4944 - Drop the old code to choke directory connections when the
4945 corresponding OR connections got full: thanks to the cell queue
4946 feature, OR conns don't get full any more.
4947 - Make dns_resolve() handle attaching connections to circuits
4948 properly, so the caller doesn't have to.
4949 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
4950 - Keep the connection array as a dynamic smartlist_t, rather than as
4951 a fixed-sized array. This is important, as the number of connections
4952 is becoming increasingly decoupled from the number of sockets.
4955 Changes in version 0.1.2.14 - 2007-05-25
4956 Tor 0.1.2.14 changes the addresses of two directory authorities (this
4957 change especially affects those who serve or use hidden services),
4958 and fixes several other crash- and security-related bugs.
4960 o Directory authority changes:
4961 - Two directory authorities (moria1 and moria2) just moved to new
4962 IP addresses. This change will particularly affect those who serve
4963 or use hidden services.
4965 o Major bugfixes (crashes):
4966 - If a directory server runs out of space in the connection table
4967 as it's processing a begin_dir request, it will free the exit stream
4968 but leave it attached to the circuit, leading to unpredictable
4969 behavior. (Reported by seeess, fixes bug 425.)
4970 - Fix a bug in dirserv_remove_invalid() that would cause authorities
4971 to corrupt memory under some really unlikely scenarios.
4972 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
4973 - Avoid segfaults when reading from mmaped descriptor file. (Reported
4976 o Major bugfixes (security):
4977 - When choosing an entry guard for a circuit, avoid using guards
4978 that are in the same family as the chosen exit -- not just guards
4979 that are exactly the chosen exit. (Reported by lodger.)
4981 o Major bugfixes (resource management):
4982 - If a directory authority is down, skip it when deciding where to get
4983 networkstatus objects or descriptors. Otherwise we keep asking
4984 every 10 seconds forever. Fixes bug 384.
4985 - Count it as a failure if we fetch a valid network-status but we
4986 don't want to keep it. Otherwise we'll keep fetching it and keep
4987 not wanting to keep it. Fixes part of bug 422.
4988 - If all of our dirservers have given us bad or no networkstatuses
4989 lately, then stop hammering them once per minute even when we
4990 think they're failed. Fixes another part of bug 422.
4993 - Actually set the purpose correctly for descriptors inserted with
4995 - When we have k non-v2 authorities in our DirServer config,
4996 we ignored the last k authorities in the list when updating our
4998 - Correctly back-off from requesting router descriptors that we are
4999 having a hard time downloading.
5000 - Read resolv.conf files correctly on platforms where read() returns
5001 partial results on small file reads.
5002 - Don't rebuild the entire router store every time we get 32K of
5003 routers: rebuild it when the journal gets very large, or when
5004 the gaps in the store get very large.
5007 - When routers publish SVN revisions in their router descriptors,
5008 authorities now include those versions correctly in networkstatus
5010 - Warn when using a version of libevent before 1.3b to run a server on
5011 OSX or BSD: these versions interact badly with userspace threads.
5014 Changes in version 0.1.2.13 - 2007-04-24
5015 This release features some major anonymity fixes, such as safer path
5016 selection; better client performance; faster bootstrapping, better
5017 address detection, and better DNS support for servers; write limiting as
5018 well as read limiting to make servers easier to run; and a huge pile of
5019 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
5021 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
5022 of the Freenode IRC network, remembering his patience and vision for
5023 free speech on the Internet.
5026 - Fix a memory leak when we ask for "all" networkstatuses and we
5027 get one we don't recognize.
5028 - Add more asserts to hunt down bug 417.
5029 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
5032 Changes in version 0.1.2.12-rc - 2007-03-16
5034 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
5035 directory information requested inside Tor connections (i.e. via
5036 begin_dir cells). It only triggered when the same connection was
5037 serving other data at the same time. Reported by seeess.
5040 - When creating a circuit via the controller, send a 'launched'
5041 event when we're done, so we follow the spec better.
5044 Changes in version 0.1.2.11-rc - 2007-03-15
5045 o Minor bugfixes (controller), reported by daejees:
5046 - Correct the control spec to match how the code actually responds
5047 to 'getinfo addr-mappings/*'.
5048 - The control spec described a GUARDS event, but the code
5049 implemented a GUARD event. Standardize on GUARD, but let people
5053 Changes in version 0.1.2.10-rc - 2007-03-07
5054 o Major bugfixes (Windows):
5055 - Do not load the NT services library functions (which may not exist)
5056 just to detect if we're a service trying to shut down. Now we run
5057 on Win98 and friends again.
5059 o Minor bugfixes (other):
5060 - Clarify a couple of log messages.
5061 - Fix a misleading socks5 error number.
5064 Changes in version 0.1.2.9-rc - 2007-03-02
5065 o Major bugfixes (Windows):
5066 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
5067 of the usual GCC "%llu". This prevents a bug when saving 64-bit
5068 int configuration values: the high-order 32 bits would get
5069 truncated. In particular, we were being bitten by the default
5070 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
5071 and maybe also bug 397.)
5073 o Minor bugfixes (performance):
5074 - Use OpenSSL's AES implementation on platforms where it's faster.
5075 This could save us as much as 10% CPU usage.
5077 o Minor bugfixes (server):
5078 - Do not rotate onion key immediately after setting it for the first
5081 o Minor bugfixes (directory authorities):
5082 - Stop calling servers that have been hibernating for a long time
5083 "stable". Also, stop letting hibernating or obsolete servers affect
5084 uptime and bandwidth cutoffs.
5085 - Stop listing hibernating servers in the v1 directory.
5087 o Minor bugfixes (hidden services):
5088 - Upload hidden service descriptors slightly less often, to reduce
5089 load on authorities.
5091 o Minor bugfixes (other):
5092 - Fix an assert that could trigger if a controller quickly set then
5093 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
5094 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
5096 - Fix a potential race condition in the rpm installer. Found by
5098 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
5099 of 2 as indicating that the server is completely bad; it sometimes
5100 means that the server is just bad for the request in question. (may fix
5101 the last of bug 326.)
5102 - Disable encrypted directory connections when we don't have a server
5103 descriptor for the destination. We'll get this working again in
5107 Changes in version 0.1.2.8-beta - 2007-02-26
5108 o Major bugfixes (crashes):
5109 - Stop crashing when the controller asks us to resetconf more than
5110 one config option at once. (Vidalia 0.0.11 does this.)
5111 - Fix a crash that happened on Win98 when we're given command-line
5112 arguments: don't try to load NT service functions from advapi32.dll
5113 except when we need them. (Bug introduced in 0.1.2.7-alpha;
5115 - Fix a longstanding obscure crash bug that could occur when
5116 we run out of DNS worker processes. (Resolves bug 390.)
5118 o Major bugfixes (hidden services):
5119 - Correctly detect whether hidden service descriptor downloads are
5120 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
5122 o Major bugfixes (accounting):
5123 - When we start during an accounting interval before it's time to wake
5124 up, remember to wake up at the correct time. (May fix bug 342.)
5126 o Minor bugfixes (controller):
5127 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
5128 clear the corresponding on_circuit variable, and remember later
5129 that we don't need to send a redundant CLOSED event. (Resolves part
5131 - Report events where a resolve succeeded or where we got a socks
5132 protocol error correctly, rather than calling both of them
5134 - Change reported stream target addresses to IP consistently when
5135 we finally get the IP from an exit node.
5136 - Send log messages to the controller even if they happen to be very
5139 o Minor bugfixes (other):
5140 - Display correct results when reporting which versions are
5141 recommended, and how recommended they are. (Resolves bug 383.)
5142 - Improve our estimates for directory bandwidth to be less random:
5143 guess that an unrecognized directory will have the average bandwidth
5144 from all known directories, not that it will have the average
5145 bandwidth from those directories earlier than it on the list.
5146 - If we start a server with ClientOnly 1, then set ClientOnly to 0
5147 and hup, stop triggering an assert based on an empty onion_key.
5148 - On platforms with no working mmap() equivalent, don't warn the
5149 user when cached-routers doesn't exist.
5150 - Warn the user when mmap() [or its equivalent] fails for some reason
5151 other than file-not-found.
5152 - Don't warn the user when cached-routers.new doesn't exist: that's
5153 perfectly fine when starting up for the first time.
5154 - When EntryNodes are configured, rebuild the guard list to contain,
5155 in order: the EntryNodes that were guards before; the rest of the
5156 EntryNodes; the nodes that were guards before.
5157 - Mask out all signals in sub-threads; only the libevent signal
5158 handler should be processing them. This should prevent some crashes
5159 on some machines using pthreads. (Patch from coderman.)
5160 - Fix switched arguments on memset in the implementation of
5161 tor_munmap() for systems with no mmap() call.
5162 - When Tor receives a router descriptor that it asked for, but
5163 no longer wants (because it has received fresh networkstatuses
5164 in the meantime), do not warn the user. Cache the descriptor if
5165 we're a cache; drop it if we aren't.
5166 - Make earlier entry guards _really_ get retried when the network
5168 - On a malformed DNS reply, always give an error to the corresponding
5170 - Build with recent libevents on platforms that do not define the
5171 nonstandard types "u_int8_t" and friends.
5173 o Minor features (controller):
5174 - Warn the user when an application uses the obsolete binary v0
5175 control protocol. We're planning to remove support for it during
5176 the next development series, so it's good to give people some
5178 - Add STREAM_BW events to report per-entry-stream bandwidth
5179 use. (Patch from Robert Hogan.)
5180 - Rate-limit SIGNEWNYM signals in response to controllers that
5181 impolitely generate them for every single stream. (Patch from
5182 mwenge; closes bug 394.)
5183 - Make REMAP stream events have a SOURCE (cache or exit), and
5184 make them generated in every case where we get a successful
5185 connected or resolved cell.
5187 o Minor bugfixes (performance):
5188 - Call router_have_min_dir_info half as often. (This is showing up in
5189 some profiles, but not others.)
5190 - When using GCC, make log_debug never get called at all, and its
5191 arguments never get evaluated, when no debug logs are configured.
5192 (This is showing up in some profiles, but not others.)
5195 - Remove some never-implemented options. Mark PathlenCoinWeight as
5197 - Implement proposal 106: Stop requiring clients to have well-formed
5198 certificates; stop checking nicknames in certificates. (Clients
5199 have certificates so that they can look like Tor servers, but in
5200 the future we might want to allow them to look like regular TLS
5201 clients instead. Nicknames in certificates serve no purpose other
5202 than making our protocol easier to recognize on the wire.)
5203 - Revise messages on handshake failure again to be even more clear about
5204 which are incoming connections and which are outgoing.
5205 - Discard any v1 directory info that's over 1 month old (for
5206 directories) or over 1 week old (for running-routers lists).
5207 - Do not warn when individual nodes in the configuration's EntryNodes,
5208 ExitNodes, etc are down: warn only when all possible nodes
5209 are down. (Fixes bug 348.)
5210 - Always remove expired routers and networkstatus docs before checking
5211 whether we have enough information to build circuits. (Fixes
5213 - Put a lower-bound on MaxAdvertisedBandwidth.
5216 Changes in version 0.1.2.7-alpha - 2007-02-06
5217 o Major bugfixes (rate limiting):
5218 - Servers decline directory requests much more aggressively when
5219 they're low on bandwidth. Otherwise they end up queueing more and
5220 more directory responses, which can't be good for latency.
5221 - But never refuse directory requests from local addresses.
5222 - Fix a memory leak when sending a 503 response for a networkstatus
5224 - Be willing to read or write on local connections (e.g. controller
5225 connections) even when the global rate limiting buckets are empty.
5226 - If our system clock jumps back in time, don't publish a negative
5227 uptime in the descriptor. Also, don't let the global rate limiting
5228 buckets go absurdly negative.
5229 - Flush local controller connection buffers periodically as we're
5230 writing to them, so we avoid queueing 4+ megabytes of data before
5233 o Major bugfixes (NT services):
5234 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
5235 command-line flag so that admins can override the default by saying
5236 "tor --service install --user "SomeUser"". This will not affect
5237 existing installed services. Also, warn the user that the service
5238 will look for its configuration file in the service user's
5239 %appdata% directory. (We can't do the 'hardwire the user's appdata
5240 directory' trick any more, since we may not have read access to that
5243 o Major bugfixes (other):
5244 - Previously, we would cache up to 16 old networkstatus documents
5245 indefinitely, if they came from nontrusted authorities. Now we
5246 discard them if they are more than 10 days old.
5247 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
5249 - Detect and reject malformed DNS responses containing circular
5251 - If exits are rare enough that we're not marking exits as guards,
5252 ignore exit bandwidth when we're deciding the required bandwidth
5254 - When we're handling a directory connection tunneled over Tor,
5255 don't fill up internal memory buffers with all the data we want
5256 to tunnel; instead, only add it if the OR connection that will
5257 eventually receive it has some room for it. (This can lead to
5258 slowdowns in tunneled dir connections; a better solution will have
5261 o Minor bugfixes (dns):
5262 - Add some defensive programming to eventdns.c in an attempt to catch
5263 possible memory-stomping bugs.
5264 - Detect and reject DNS replies containing IPv4 or IPv6 records with
5265 an incorrect number of bytes. (Previously, we would ignore the
5267 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
5268 in the correct order, and doesn't crash.
5269 - Free memory held in recently-completed DNS lookup attempts on exit.
5270 This was not a memory leak, but may have been hiding memory leaks.
5271 - Handle TTL values correctly on reverse DNS lookups.
5272 - Treat failure to parse resolv.conf as an error.
5274 o Minor bugfixes (other):
5275 - Fix crash with "tor --list-fingerprint" (reported by seeess).
5276 - When computing clock skew from directory HTTP headers, consider what
5277 time it was when we finished asking for the directory, not what
5279 - Expire socks connections if they spend too long waiting for the
5280 handshake to finish. Previously we would let them sit around for
5281 days, if the connecting application didn't close them either.
5282 - And if the socks handshake hasn't started, don't send a
5283 "DNS resolve socks failed" handshake reply; just close it.
5284 - Stop using C functions that OpenBSD's linker doesn't like.
5285 - Don't launch requests for descriptors unless we have networkstatuses
5286 from at least half of the authorities. This delays the first
5287 download slightly under pathological circumstances, but can prevent
5288 us from downloading a bunch of descriptors we don't need.
5289 - Do not log IPs with TLS failures for incoming TLS
5290 connections. (Fixes bug 382.)
5291 - If the user asks to use invalid exit nodes, be willing to use
5293 - Stop using the reserved ac_cv namespace in our configure script.
5294 - Call stat() slightly less often; use fstat() when possible.
5295 - Refactor the way we handle pending circuits when an OR connection
5296 completes or fails, in an attempt to fix a rare crash bug.
5297 - Only rewrite a conn's address based on X-Forwarded-For: headers
5298 if it's a parseable public IP address; and stop adding extra quotes
5299 to the resulting address.
5302 - Weight directory requests by advertised bandwidth. Now we can
5303 let servers enable write limiting but still allow most clients to
5304 succeed at their directory requests. (We still ignore weights when
5305 choosing a directory authority; I hope this is a feature.)
5308 - Create a new file ReleaseNotes which was the old ChangeLog. The
5309 new ChangeLog file now includes the summaries for all development
5311 - Check for addresses with invalid characters at the exit as well
5312 as at the client, and warn less verbosely when they fail. You can
5313 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
5314 - Adapt a patch from goodell to let the contrib/exitlist script
5315 take arguments rather than require direct editing.
5316 - Inform the server operator when we decide not to advertise a
5317 DirPort due to AccountingMax enabled or a low BandwidthRate. It
5318 was confusing Zax, so now we're hopefully more helpful.
5319 - Bring us one step closer to being able to establish an encrypted
5320 directory tunnel without knowing a descriptor first. Still not
5321 ready yet. As part of the change, now assume we can use a
5322 create_fast cell if we don't know anything about a router.
5323 - Allow exit nodes to use nameservers running on ports other than 53.
5324 - Servers now cache reverse DNS replies.
5325 - Add an --ignore-missing-torrc command-line option so that we can
5326 get the "use sensible defaults if the configuration file doesn't
5327 exist" behavior even when specifying a torrc location on the command
5330 o Minor features (controller):
5331 - Track reasons for OR connection failure; make these reasons
5332 available via the controller interface. (Patch from Mike Perry.)
5333 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
5334 can learn when clients are sending malformed hostnames to Tor.
5335 - Clean up documentation for controller status events.
5336 - Add a REMAP status to stream events to note that a stream's
5337 address has changed because of a cached address or a MapAddress
5341 Changes in version 0.1.2.6-alpha - 2007-01-09
5343 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
5344 connection handles more than 4 gigs in either direction, we crash.
5345 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
5346 advertised exit node, somebody might try to exit from us when
5347 we're bootstrapping and before we've built our descriptor yet.
5348 Refuse the connection rather than crashing.
5351 - Warn if we (as a server) find that we've resolved an address that we
5352 weren't planning to resolve.
5353 - Warn that using select() on any libevent version before 1.1 will be
5354 unnecessarily slow (even for select()).
5355 - Flush ERR-level controller status events just like we currently
5356 flush ERR-level log events, so that a Tor shutdown doesn't prevent
5357 the controller from learning about current events.
5359 o Minor features (more controller status events):
5360 - Implement EXTERNAL_ADDRESS server status event so controllers can
5361 learn when our address changes.
5362 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
5363 can learn when directories reject our descriptor.
5364 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
5365 can learn when a client application is speaking a non-socks protocol
5367 - Implement DANGEROUS_SOCKS client status event so controllers
5368 can learn when a client application is leaking DNS addresses.
5369 - Implement BUG general status event so controllers can learn when
5370 Tor is unhappy about its internal invariants.
5371 - Implement CLOCK_SKEW general status event so controllers can learn
5372 when Tor thinks the system clock is set incorrectly.
5373 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
5374 server status events so controllers can learn when their descriptors
5375 are accepted by a directory.
5376 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
5377 server status events so controllers can learn about Tor's progress in
5378 deciding whether it's reachable from the outside.
5379 - Implement BAD_LIBEVENT general status event so controllers can learn
5380 when we have a version/method combination in libevent that needs to
5382 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
5383 and DNS_USELESS server status events so controllers can learn
5384 about changes to DNS server status.
5386 o Minor features (directory):
5387 - Authorities no longer recommend exits as guards if this would shift
5388 too much load to the exit nodes.
5391 Changes in version 0.1.2.5-alpha - 2007-01-06
5393 - Enable write limiting as well as read limiting. Now we sacrifice
5394 capacity if we're pushing out lots of directory traffic, rather
5395 than overrunning the user's intended bandwidth limits.
5396 - Include TLS overhead when counting bandwidth usage; previously, we
5397 would count only the bytes sent over TLS, but not the bytes used
5399 - Support running the Tor service with a torrc not in the same
5400 directory as tor.exe and default to using the torrc located in
5401 the %appdata%\Tor\ of the user who installed the service. Patch
5403 - Servers now check for the case when common DNS requests are going to
5404 wildcarded addresses (i.e. all getting the same answer), and change
5405 their exit policy to reject *:* if it's happening.
5406 - Implement BEGIN_DIR cells, so we can connect to the directory
5407 server via TLS to do encrypted directory requests rather than
5408 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
5409 config options if you like.
5411 o Minor features (config and docs):
5412 - Start using the state file to store bandwidth accounting data:
5413 the bw_accounting file is now obsolete. We'll keep generating it
5414 for a while for people who are still using 0.1.2.4-alpha.
5415 - Try to batch changes to the state file so that we do as few
5416 disk writes as possible while still storing important things in
5418 - The state file and the bw_accounting file get saved less often when
5419 the AvoidDiskWrites config option is set.
5420 - Make PIDFile work on Windows (untested).
5421 - Add internal descriptions for a bunch of configuration options:
5422 accessible via controller interface and in comments in saved
5424 - Reject *:563 (NNTPS) in the default exit policy. We already reject
5425 NNTP by default, so this seems like a sensible addition.
5426 - Clients now reject hostnames with invalid characters. This should
5427 avoid some inadvertent info leaks. Add an option
5428 AllowNonRFC953Hostnames to disable this behavior, in case somebody
5429 is running a private network with hosts called @, !, and #.
5430 - Add a maintainer script to tell us which options are missing
5431 documentation: "make check-docs".
5432 - Add a new address-spec.txt document to describe our special-case
5433 addresses: .exit, .onion, and .noconnnect.
5435 o Minor features (DNS):
5436 - Ongoing work on eventdns infrastructure: now it has dns server
5437 and ipv6 support. One day Tor will make use of it.
5438 - Add client-side caching for reverse DNS lookups.
5439 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
5440 - When we change nameservers or IP addresses, reset and re-launch
5441 our tests for DNS hijacking.
5443 o Minor features (directory):
5444 - Authorities now specify server versions in networkstatus. This adds
5445 about 2% to the size of compressed networkstatus docs, and allows
5446 clients to tell which servers support BEGIN_DIR and which don't.
5447 The implementation is forward-compatible with a proposed future
5448 protocol version scheme not tied to Tor versions.
5449 - DirServer configuration lines now have an orport= option so
5450 clients can open encrypted tunnels to the authorities without
5451 having downloaded their descriptors yet. Enabled for moria1,
5452 moria2, tor26, and lefkada now in the default configuration.
5453 - Directory servers are more willing to send a 503 "busy" if they
5454 are near their write limit, especially for v1 directory requests.
5455 Now they can use their limited bandwidth for actual Tor traffic.
5456 - Clients track responses with status 503 from dirservers. After a
5457 dirserver has given us a 503, we try not to use it until an hour has
5458 gone by, or until we have no dirservers that haven't given us a 503.
5459 - When we get a 503 from a directory, and we're not a server, we don't
5460 count the failure against the total number of failures allowed
5461 for the thing we're trying to download.
5462 - Report X-Your-Address-Is correctly from tunneled directory
5463 connections; don't report X-Your-Address-Is when it's an internal
5464 address; and never believe reported remote addresses when they're
5466 - Protect against an unlikely DoS attack on directory servers.
5467 - Add a BadDirectory flag to network status docs so that authorities
5468 can (eventually) tell clients about caches they believe to be
5471 o Minor features (controller):
5472 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
5473 - Reimplement GETINFO so that info/names stays in sync with the
5475 - Implement "GETINFO fingerprint".
5476 - Implement "SETEVENTS GUARD" so controllers can get updates on
5477 entry guard status as it changes.
5479 o Minor features (clean up obsolete pieces):
5480 - Remove some options that have been deprecated since at least
5481 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
5482 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
5484 - We no longer look for identity and onion keys in "identity.key" and
5485 "onion.key" -- these were replaced by secret_id_key and
5486 secret_onion_key in 0.0.8pre1.
5487 - We no longer require unrecognized directory entries to be
5490 o Major bugfixes (security):
5491 - Stop sending the HttpProxyAuthenticator string to directory
5492 servers when directory connections are tunnelled through Tor.
5493 - Clients no longer store bandwidth history in the state file.
5494 - Do not log introduction points for hidden services if SafeLogging
5496 - When generating bandwidth history, round down to the nearest
5497 1k. When storing accounting data, round up to the nearest 1k.
5498 - When we're running as a server, remember when we last rotated onion
5499 keys, so that we will rotate keys once they're a week old even if
5500 we never stay up for a week ourselves.
5502 o Major bugfixes (other):
5503 - Fix a longstanding bug in eventdns that prevented the count of
5504 timed-out resolves from ever being reset. This bug caused us to
5505 give up on a nameserver the third time it timed out, and try it
5506 10 seconds later... and to give up on it every time it timed out
5508 - Take out the '5 second' timeout from the connection retry
5509 schedule. Now the first connect attempt will wait a full 10
5510 seconds before switching to a new circuit. Perhaps this will help
5511 a lot. Based on observations from Mike Perry.
5512 - Fix a bug on the Windows implementation of tor_mmap_file() that
5513 would prevent the cached-routers file from ever loading. Reported
5517 - Fix an assert failure when a directory authority sets
5518 AuthDirRejectUnlisted and then receives a descriptor from an
5519 unlisted router. Reported by seeess.
5520 - Avoid a double-free when parsing malformed DirServer lines.
5521 - Fix a bug when a BSD-style PF socket is first used. Patch from
5523 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
5524 to resolve an address at a given exit node even when they ask for
5526 - Servers no longer ever list themselves in their "family" line,
5527 even if configured to do so. This makes it easier to configure
5528 family lists conveniently.
5529 - When running as a server, don't fall back to 127.0.0.1 when no
5530 nameservers are configured in /etc/resolv.conf; instead, make the
5531 user fix resolv.conf or specify nameservers explicitly. (Resolves
5533 - Stop accepting certain malformed ports in configured exit policies.
5534 - Don't re-write the fingerprint file every restart, unless it has
5536 - Stop warning when a single nameserver fails: only warn when _all_ of
5537 our nameservers have failed. Also, when we only have one nameserver,
5538 raise the threshold for deciding that the nameserver is dead.
5539 - Directory authorities now only decide that routers are reachable
5540 if their identity keys are as expected.
5541 - When the user uses bad syntax in the Log config line, stop
5542 suggesting other bad syntax as a replacement.
5543 - Correctly detect ipv6 DNS capability on OpenBSD.
5545 o Minor bugfixes (controller):
5546 - Report the circuit number correctly in STREAM CLOSED events. Bug
5547 reported by Mike Perry.
5548 - Do not report bizarre values for results of accounting GETINFOs
5549 when the last second's write or read exceeds the allotted bandwidth.
5550 - Report "unrecognized key" rather than an empty string when the
5551 controller tries to fetch a networkstatus that doesn't exist.
5554 Changes in version 0.1.1.26 - 2006-12-14
5555 o Security bugfixes:
5556 - Stop sending the HttpProxyAuthenticator string to directory
5557 servers when directory connections are tunnelled through Tor.
5558 - Clients no longer store bandwidth history in the state file.
5559 - Do not log introduction points for hidden services if SafeLogging
5563 - Fix an assert failure when a directory authority sets
5564 AuthDirRejectUnlisted and then receives a descriptor from an
5565 unlisted router (reported by seeess).
5568 Changes in version 0.1.2.4-alpha - 2006-12-03
5570 - Add support for using natd; this allows FreeBSDs earlier than
5571 5.1.2 to have ipfw send connections through Tor without using
5572 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
5575 - Make all connections to addresses of the form ".noconnect"
5576 immediately get closed. This lets application/controller combos
5577 successfully test whether they're talking to the same Tor by
5578 watching for STREAM events.
5579 - Make cross.sh cross-compilation script work even when autogen.sh
5580 hasn't been run. (Patch from Michael Mohr.)
5581 - Statistics dumped by -USR2 now include a breakdown of public key
5582 operations, for profiling.
5585 - Fix a major leak when directory authorities parse their
5586 approved-routers list, a minor memory leak when we fail to pick
5587 an exit node, and a few rare leaks on errors.
5588 - Handle TransPort connections even when the server sends data before
5589 the client sends data. Previously, the connection would just hang
5590 until the client sent data. (Patch from tup based on patch from
5592 - Avoid assert failure when our cached-routers file is empty on
5596 - Don't log spurious warnings when we see a circuit close reason we
5597 don't recognize; it's probably just from a newer version of Tor.
5598 - Have directory authorities allow larger amounts of drift in uptime
5599 without replacing the server descriptor: previously, a server that
5600 restarted every 30 minutes could have 48 "interesting" descriptors
5602 - Start linking to the Tor specification and Tor reference manual
5603 correctly in the Windows installer.
5604 - Add Vidalia to the OS X uninstaller script, so when we uninstall
5605 Tor/Privoxy we also uninstall Vidalia.
5606 - Resume building on Irix64, and fix a lot of warnings from its
5608 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
5609 when we're running as a client.
5612 Changes in version 0.1.1.25 - 2006-11-04
5614 - When a client asks us to resolve (rather than connect to)
5615 an address, and we have a cached answer, give them the cached
5616 answer. Previously, we would give them no answer at all.
5617 - We were building exactly the wrong circuits when we predict
5618 hidden service requirements, meaning Tor would have to build all
5619 its circuits on demand.
5620 - If none of our live entry guards have a high uptime, but we
5621 require a guard with a high uptime, try adding a new guard before
5622 we give up on the requirement. This patch should make long-lived
5623 connections more stable on average.
5624 - When testing reachability of our DirPort, don't launch new
5625 tests when there's already one in progress -- unreachable
5626 servers were stacking up dozens of testing streams.
5628 o Security bugfixes:
5629 - When the user sends a NEWNYM signal, clear the client-side DNS
5630 cache too. Otherwise we continue to act on previous information.
5633 - Avoid a memory corruption bug when creating a hash table for
5635 - Avoid possibility of controller-triggered crash when misusing
5636 certain commands from a v0 controller on platforms that do not
5637 handle printf("%s",NULL) gracefully.
5638 - Avoid infinite loop on unexpected controller input.
5639 - Don't log spurious warnings when we see a circuit close reason we
5640 don't recognize; it's probably just from a newer version of Tor.
5641 - Add Vidalia to the OS X uninstaller script, so when we uninstall
5642 Tor/Privoxy we also uninstall Vidalia.
5645 Changes in version 0.1.2.3-alpha - 2006-10-29
5647 - Prepare for servers to publish descriptors less often: never
5648 discard a descriptor simply for being too old until either it is
5649 recommended by no authorities, or until we get a better one for
5650 the same router. Make caches consider retaining old recommended
5651 routers for even longer.
5652 - If most authorities set a BadExit flag for a server, clients
5653 don't think of it as a general-purpose exit. Clients only consider
5654 authorities that advertise themselves as listing bad exits.
5655 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
5656 headers for content, so that we can work better in the presence of
5657 caching HTTP proxies.
5658 - Allow authorities to list nodes as bad exits by fingerprint or by
5661 o Minor features, controller:
5662 - Add a REASON field to CIRC events; for backward compatibility, this
5663 field is sent only to controllers that have enabled the extended
5664 event format. Also, add additional reason codes to explain why
5665 a given circuit has been destroyed or truncated. (Patches from
5667 - Add a REMOTE_REASON field to extended CIRC events to tell the
5668 controller about why a remote OR told us to close a circuit.
5669 - Stream events also now have REASON and REMOTE_REASON fields,
5670 working much like those for circuit events.
5671 - There's now a GETINFO ns/... field so that controllers can ask Tor
5672 about the current status of a router.
5673 - A new event type "NS" to inform a controller when our opinion of
5674 a router's status has changed.
5675 - Add a GETINFO events/names and GETINFO features/names so controllers
5676 can tell which events and features are supported.
5677 - A new CLEARDNSCACHE signal to allow controllers to clear the
5678 client-side DNS cache without expiring circuits.
5680 o Security bugfixes:
5681 - When the user sends a NEWNYM signal, clear the client-side DNS
5682 cache too. Otherwise we continue to act on previous information.
5685 - Avoid sending junk to controllers or segfaulting when a controller
5686 uses EVENT_NEW_DESC with verbose nicknames.
5687 - Stop triggering asserts if the controller tries to extend hidden
5688 service circuits (reported by mwenge).
5689 - Avoid infinite loop on unexpected controller input.
5690 - When the controller does a "GETINFO network-status", tell it
5691 about even those routers whose descriptors are very old, and use
5692 long nicknames where appropriate.
5693 - Change NT service functions to be loaded on demand. This lets us
5694 build with MinGW without breaking Tor for Windows 98 users.
5695 - Do DirPort reachability tests less often, since a single test
5696 chews through many circuits before giving up.
5697 - In the hidden service example in torrc.sample, stop recommending
5698 esoteric and discouraged hidden service options.
5699 - When stopping an NT service, wait up to 10 sec for it to actually
5700 stop. (Patch from Matt Edman; resolves bug 295.)
5701 - Fix handling of verbose nicknames with ORCONN controller events:
5702 make them show up exactly when requested, rather than exactly when
5704 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
5705 printing a duplicate "$" in the keys we send (reported by mwenge).
5706 - Correctly set maximum connection limit on Cygwin. (This time
5708 - Try to detect Windows correctly when cross-compiling.
5709 - Detect the size of the routers file correctly even if it is
5710 corrupted (on systems without mmap) or not page-aligned (on systems
5711 with mmap). This bug was harmless.
5712 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
5713 to open a stream fails; now we do in more cases. This should
5714 make clients able to find a good exit faster in some cases, since
5715 unhandleable requests will now get an error rather than timing out.
5716 - Resolve two memory leaks when rebuilding the on-disk router cache
5717 (reported by fookoowa).
5718 - Clean up minor code warnings suggested by the MIPSpro C compiler,
5719 and reported by some Centos users.
5720 - Controller signals now work on non-Unix platforms that don't define
5721 SIGUSR1 and SIGUSR2 the way we expect.
5722 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
5723 values before failing, and always enables eventdns.
5724 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
5725 Try to fix this in configure.in by checking for most functions
5726 before we check for libevent.
5729 Changes in version 0.1.2.2-alpha - 2006-10-07
5731 - Make our async eventdns library on-by-default for Tor servers,
5732 and plan to deprecate the separate dnsworker threads.
5733 - Add server-side support for "reverse" DNS lookups (using PTR
5734 records so clients can determine the canonical hostname for a given
5735 IPv4 address). Only supported by servers using eventdns; servers
5736 now announce in their descriptors whether they support eventdns.
5737 - Specify and implement client-side SOCKS5 interface for reverse DNS
5738 lookups (see doc/socks-extensions.txt).
5739 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
5740 connect to directory servers through Tor. Previously, clients needed
5741 to find Tor exits to make private connections to directory servers.
5742 - Avoid choosing Exit nodes for entry or middle hops when the
5743 total bandwidth available from non-Exit nodes is much higher than
5744 the total bandwidth available from Exit nodes.
5745 - Workaround for name servers (like Earthlink's) that hijack failing
5746 DNS requests and replace the no-such-server answer with a "helpful"
5747 redirect to an advertising-driven search portal. Also work around
5748 DNS hijackers who "helpfully" decline to hijack known-invalid
5749 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
5750 lets you turn it off.
5751 - Send out a burst of long-range padding cells once we've established
5752 that we're reachable. Spread them over 4 circuits, so hopefully
5753 a few will be fast. This exercises our bandwidth and bootstraps
5754 us into the directory more quickly.
5756 o New/improved config options:
5757 - Add new config option "ResolvConf" to let the server operator
5758 choose an alternate resolve.conf file when using eventdns.
5759 - Add an "EnforceDistinctSubnets" option to control our "exclude
5760 servers on the same /16" behavior. It's still on by default; this
5761 is mostly for people who want to operate private test networks with
5762 all the machines on the same subnet.
5763 - If one of our entry guards is on the ExcludeNodes list, or the
5764 directory authorities don't think it's a good guard, treat it as
5765 if it were unlisted: stop using it as a guard, and throw it off
5766 the guards list if it stays that way for a long time.
5767 - Allow directory authorities to be marked separately as authorities
5768 for the v1 directory protocol, the v2 directory protocol, and
5769 as hidden service directories, to make it easier to retire old
5770 authorities. V1 authorities should set "HSAuthoritativeDir 1"
5771 to continue being hidden service authorities too.
5772 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
5774 o Minor features, controller:
5775 - Fix CIRC controller events so that controllers can learn the
5776 identity digests of non-Named servers used in circuit paths.
5777 - Let controllers ask for more useful identifiers for servers. Instead
5778 of learning identity digests for un-Named servers and nicknames
5779 for Named servers, the new identifiers include digest, nickname,
5780 and indication of Named status. Off by default; see control-spec.txt
5781 for more information.
5782 - Add a "getinfo address" controller command so it can display Tor's
5783 best guess to the user.
5784 - New controller event to alert the controller when our server
5785 descriptor has changed.
5786 - Give more meaningful errors on controller authentication failure.
5788 o Minor features, other:
5789 - When asked to resolve a hostname, don't use non-exit servers unless
5790 requested to do so. This allows servers with broken DNS to be
5791 useful to the network.
5792 - Divide eventdns log messages into warn and info messages.
5793 - Reserve the nickname "Unnamed" for routers that can't pick
5794 a hostname: any router can call itself Unnamed; directory
5795 authorities will never allocate Unnamed to any particular router;
5796 clients won't believe that any router is the canonical Unnamed.
5797 - Only include function names in log messages for info/debug messages.
5798 For notice/warn/err, the content of the message should be clear on
5799 its own, and printing the function name only confuses users.
5800 - Avoid some false positives during reachability testing: don't try
5801 to test via a server that's on the same /24 as us.
5802 - If we fail to build a circuit to an intended enclave, and it's
5803 not mandatory that we use that enclave, stop wanting it.
5804 - When eventdns is enabled, allow multithreaded builds on NetBSD and
5805 OpenBSD. (We had previously disabled threads on these platforms
5806 because they didn't have working thread-safe resolver functions.)
5808 o Major bugfixes, anonymity/security:
5809 - If a client asked for a server by name, and there's a named server
5810 in our network-status but we don't have its descriptor yet, we
5811 could return an unnamed server instead.
5812 - Fix NetBSD bug that could allow someone to force uninitialized RAM
5813 to be sent to a server's DNS resolver. This only affects NetBSD
5814 and other platforms that do not bounds-check tolower().
5815 - Reject (most) attempts to use Tor circuits with length one. (If
5816 many people start using Tor as a one-hop proxy, exit nodes become
5817 a more attractive target for compromise.)
5818 - Just because your DirPort is open doesn't mean people should be
5819 able to remotely teach you about hidden service descriptors. Now
5820 only accept rendezvous posts if you've got HSAuthoritativeDir set.
5822 o Major bugfixes, other:
5823 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
5824 - When a client asks the server to resolve (not connect to)
5825 an address, and it has a cached answer, give them the cached answer.
5826 Previously, the server would give them no answer at all.
5827 - Allow really slow clients to not hang up five minutes into their
5828 directory downloads (suggested by Adam J. Richter).
5829 - We were building exactly the wrong circuits when we anticipated
5830 hidden service requirements, meaning Tor would have to build all
5831 its circuits on demand.
5832 - Avoid crashing when we mmap a router cache file of size 0.
5833 - When testing reachability of our DirPort, don't launch new
5834 tests when there's already one in progress -- unreachable
5835 servers were stacking up dozens of testing streams.
5837 o Minor bugfixes, correctness:
5838 - If we're a directory mirror and we ask for "all" network status
5839 documents, we would discard status documents from authorities
5841 - Avoid a memory corruption bug when creating a hash table for
5843 - Avoid controller-triggered crash when misusing certain commands
5844 from a v0 controller on platforms that do not handle
5845 printf("%s",NULL) gracefully.
5846 - Don't crash when a controller sends a third argument to an
5847 "extendcircuit" request.
5848 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
5849 response; fix error code when "getinfo dir/status/" fails.
5850 - Avoid crash when telling controller stream-status and a stream
5852 - Patch from Adam Langley to fix assert() in eventdns.c.
5853 - Fix a debug log message in eventdns to say "X resolved to Y"
5854 instead of "X resolved to X".
5855 - Make eventdns give strings for DNS errors, not just error numbers.
5856 - Track unreachable entry guards correctly: don't conflate
5857 'unreachable by us right now' with 'listed as down by the directory
5858 authorities'. With the old code, if a guard was unreachable by
5859 us but listed as running, it would clog our guard list forever.
5860 - Behave correctly in case we ever have a network with more than
5861 2GB/s total advertised capacity.
5862 - Make TrackExitHosts case-insensitive, and fix the behavior of
5863 ".suffix" TrackExitHosts items to avoid matching in the middle of
5865 - Finally fix the openssl warnings from newer gccs that believe that
5866 ignoring a return value is okay, but casting a return value and
5867 then ignoring it is a sign of madness.
5868 - Prevent the contrib/exitlist script from printing the same
5869 result more than once.
5870 - Patch from Steve Hildrey: Generate network status correctly on
5871 non-versioning dirservers.
5872 - Don't listen to the X-Your-Address-Is hint if you did the lookup
5873 via Tor; otherwise you'll think you're the exit node's IP address.
5875 o Minor bugfixes, performance:
5876 - Two small performance improvements on parsing descriptors.
5877 - Major performance improvement on inserting descriptors: change
5878 algorithm from O(n^2) to O(n).
5879 - Make the common memory allocation path faster on machines where
5880 malloc(0) returns a pointer.
5881 - Start remembering X-Your-Address-Is directory hints even if you're
5882 a client, so you can become a server more smoothly.
5883 - Avoid duplicate entries on MyFamily line in server descriptor.
5885 o Packaging, features:
5886 - Remove architecture from OS X builds. The official builds are
5887 now universal binaries.
5888 - The Debian package now uses --verify-config when (re)starting,
5889 to distinguish configuration errors from other errors.
5890 - Update RPMs to require libevent 1.1b.
5892 o Packaging, bugfixes:
5893 - Patches so Tor builds with MinGW on Windows.
5894 - Patches so Tor might run on Cygwin again.
5895 - Resume building on non-gcc compilers and ancient gcc. Resume
5896 building with the -O0 compile flag. Resume building cleanly on
5898 - Run correctly on OS X platforms with case-sensitive filesystems.
5899 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
5900 - Add autoconf checks so Tor can build on Solaris x86 again.
5903 - Documented (and renamed) ServerDNSSearchDomains and
5904 ServerDNSResolvConfFile options.
5905 - Be clearer that the *ListenAddress directives can be repeated
5909 Changes in version 0.1.1.24 - 2006-09-29
5911 - Allow really slow clients to not hang up five minutes into their
5912 directory downloads (suggested by Adam J. Richter).
5913 - Fix major performance regression from 0.1.0.x: instead of checking
5914 whether we have enough directory information every time we want to
5915 do something, only check when the directory information has changed.
5916 This should improve client CPU usage by 25-50%.
5917 - Don't crash if, after a server has been running for a while,
5918 it can't resolve its hostname.
5921 - Allow Tor to start when RunAsDaemon is set but no logs are set.
5922 - Don't crash when the controller receives a third argument to an
5923 "extendcircuit" request.
5924 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
5925 response; fix error code when "getinfo dir/status/" fails.
5926 - Fix configure.in to not produce broken configure files with
5927 more recent versions of autoconf. Thanks to Clint for his auto*
5929 - Fix security bug on NetBSD that could allow someone to force
5930 uninitialized RAM to be sent to a server's DNS resolver. This
5931 only affects NetBSD and other platforms that do not bounds-check
5933 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
5934 methods: these are known to be buggy.
5935 - If we're a directory mirror and we ask for "all" network status
5936 documents, we would discard status documents from authorities
5940 Changes in version 0.1.2.1-alpha - 2006-08-27
5942 - Add "eventdns" async dns library from Adam Langley, tweaked to
5943 build on OSX and Windows. Only enabled if you pass the
5944 --enable-eventdns argument to configure.
5945 - Allow servers with no hostname or IP address to learn their
5946 IP address by asking the directory authorities. This code only
5947 kicks in when you would normally have exited with a "no address"
5948 error. Nothing's authenticated, so use with care.
5949 - Rather than waiting a fixed amount of time between retrying
5950 application connections, we wait only 5 seconds for the first,
5951 10 seconds for the second, and 15 seconds for each retry after
5952 that. Hopefully this will improve the expected user experience.
5953 - Patch from Tup to add support for transparent AP connections:
5954 this basically bundles the functionality of trans-proxy-tor
5955 into the Tor mainline. Now hosts with compliant pf/netfilter
5956 implementations can redirect TCP connections straight to Tor
5957 without diverting through SOCKS. Needs docs.
5958 - Busy directory servers save lots of memory by spooling server
5959 descriptors, v1 directories, and v2 networkstatus docs to buffers
5960 as needed rather than en masse. Also mmap the cached-routers
5961 files, so we don't need to keep the whole thing in memory too.
5962 - Automatically avoid picking more than one node from the same
5963 /16 network when constructing a circuit.
5964 - Revise and clean up the torrc.sample that we ship with; add
5965 a section for BandwidthRate and BandwidthBurst.
5968 - Split circuit_t into origin_circuit_t and or_circuit_t, and
5969 split connection_t into edge, or, dir, control, and base structs.
5970 These will save quite a bit of memory on busy servers, and they'll
5971 also help us track down bugs in the code and bugs in the spec.
5972 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
5973 or later. Log when we are doing this, so we can diagnose it when
5974 it fails. (Also, recommend libevent 1.1b for kqueue and
5975 win32 methods; deprecate libevent 1.0b harder; make libevent
5976 recommendation system saner.)
5977 - Start being able to build universal binaries on OS X (thanks
5979 - Export the default exit policy via the control port, so controllers
5980 don't need to guess what it is / will be later.
5981 - Add a man page entry for ProtocolWarnings.
5982 - Add TestVia config option to the man page.
5983 - Remove even more protocol-related warnings from Tor server logs,
5984 such as bad TLS handshakes and malformed begin cells.
5985 - Stop fetching descriptors if you're not a dir mirror and you
5986 haven't tried to establish any circuits lately. [This currently
5987 causes some dangerous behavior, because when you start up again
5988 you'll use your ancient server descriptors.]
5989 - New DirPort behavior: if you have your dirport set, you download
5990 descriptors aggressively like a directory mirror, whether or not
5992 - Get rid of the router_retry_connections notion. Now routers
5993 no longer try to rebuild long-term connections to directory
5994 authorities, and directory authorities no longer try to rebuild
5995 long-term connections to all servers. We still don't hang up
5996 connections in these two cases though -- we need to look at it
5997 more carefully to avoid flapping, and we likely need to wait til
5998 0.1.1.x is obsolete.
5999 - Drop compatibility with obsolete Tors that permit create cells
6000 to have the wrong circ_id_type.
6001 - Re-enable per-connection rate limiting. Get rid of the "OP
6002 bandwidth" concept. Lay groundwork for "bandwidth classes" --
6003 separate global buckets that apply depending on what sort of conn
6005 - Start publishing one minute or so after we find our ORPort
6006 to be reachable. This will help reduce the number of descriptors
6007 we have for ourselves floating around, since it's quite likely
6008 other things (e.g. DirPort) will change during that minute too.
6009 - Fork the v1 directory protocol into its own spec document,
6010 and mark dir-spec.txt as the currently correct (v2) spec.
6013 - When we find our DirPort to be reachable, publish a new descriptor
6014 so we'll tell the world (reported by pnx).
6015 - Publish a new descriptor after we hup/reload. This is important
6016 if our config has changed such that we'll want to start advertising
6017 our DirPort now, etc.
6018 - Allow Tor to start when RunAsDaemon is set but no logs are set.
6019 - When we have a state file we cannot parse, tell the user and
6020 move it aside. Now we avoid situations where the user starts
6021 Tor in 1904, Tor writes a state file with that timestamp in it,
6022 the user fixes her clock, and Tor refuses to start.
6023 - Fix configure.in to not produce broken configure files with
6024 more recent versions of autoconf. Thanks to Clint for his auto*
6026 - "tor --verify-config" now exits with -1(255) or 0 depending on
6027 whether the config options are bad or good.
6028 - Resolve bug 321 when using dnsworkers: append a period to every
6029 address we resolve at the exit node, so that we do not accidentally
6030 pick up local addresses, and so that failing searches are retried
6031 in the resolver search domains. (This is already solved for
6032 eventdns.) (This breaks Blossom servers for now.)
6033 - If we are using an exit enclave and we can't connect, e.g. because
6034 its webserver is misconfigured to not listen on localhost, then
6035 back off and try connecting from somewhere else before we fail.
6038 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
6039 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
6040 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
6041 when the IP address is mapped through MapAddress to a hostname.
6042 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
6043 useless IPv6 DNS resolves.
6044 - Patch suggested by Karsten Loesing: respond to SIGNAL command
6045 before we execute the signal, in case the signal shuts us down.
6046 - Clean up AllowInvalidNodes man page entry.
6047 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
6048 - Add more asserts to track down an assert error on a windows Tor
6049 server with connection_add being called with socket == -1.
6050 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
6051 - Fix misleading log messages: an entry guard that is "unlisted",
6052 as well as not known to be "down" (because we've never heard
6053 of it), is not therefore "up".
6054 - Remove code to special-case "-cvs" ending, since it has not
6055 actually mattered since 0.0.9.
6056 - Make our socks5 handling more robust to broken socks clients:
6057 throw out everything waiting on the buffer in between socks
6058 handshake phases, since they can't possibly (so the theory
6059 goes) have predicted what we plan to respond to them.
6062 Changes in version 0.1.1.23 - 2006-07-30
6064 - Fast Tor servers, especially exit nodes, were triggering asserts
6065 due to a bug in handling the list of pending DNS resolves. Some
6066 bugs still remain here; we're hunting them.
6067 - Entry guards could crash clients by sending unexpected input.
6068 - More fixes on reachability testing: if you find yourself reachable,
6069 then don't ever make any client requests (so you stop predicting
6070 circuits), then hup or have your clock jump, then later your IP
6071 changes, you won't think circuits are working, so you won't try to
6072 test reachability, so you won't publish.
6075 - Avoid a crash if the controller does a resetconf firewallports
6076 and then a setconf fascistfirewall=1.
6077 - Avoid an integer underflow when the dir authority decides whether
6078 a router is stable: we might wrongly label it stable, and compute
6079 a slightly wrong median stability, when a descriptor is published
6081 - Fix a place where we might trigger an assert if we can't build our
6082 own server descriptor yet.
6085 Changes in version 0.1.1.22 - 2006-07-05
6087 - Fix a big bug that was causing servers to not find themselves
6088 reachable if they changed IP addresses. Since only 0.1.1.22+
6089 servers can do reachability testing correctly, now we automatically
6090 make sure to test via one of these.
6091 - Fix to allow clients and mirrors to learn directory info from
6092 descriptor downloads that get cut off partway through.
6093 - Directory authorities had a bug in deciding if a newly published
6094 descriptor was novel enough to make everybody want a copy -- a few
6095 servers seem to be publishing new descriptors many times a minute.
6097 - Fix a rare bug that was causing some servers to complain about
6098 "closing wedged cpuworkers" and skip some circuit create requests.
6099 - Make the Exit flag in directory status documents actually work.
6102 Changes in version 0.1.1.21 - 2006-06-10
6103 o Crash and assert fixes from 0.1.1.20:
6104 - Fix a rare crash on Tor servers that have enabled hibernation.
6105 - Fix a seg fault on startup for Tor networks that use only one
6106 directory authority.
6107 - Fix an assert from a race condition that occurs on Tor servers
6108 while exiting, where various threads are trying to log that they're
6109 exiting, and delete the logs, at the same time.
6110 - Make our unit tests pass again on certain obscure platforms.
6113 - Add support for building SUSE RPM packages.
6114 - Speed up initial bootstrapping for clients: if we are making our
6115 first ever connection to any entry guard, then don't mark it down
6117 - When only one Tor server in the network is labelled as a guard,
6118 and we've already picked him, we would cycle endlessly picking him
6119 again, being unhappy about it, etc. Now we specifically exclude
6120 current guards when picking a new guard.
6121 - Servers send create cells more reliably after the TLS connection
6122 is established: we were sometimes forgetting to send half of them
6123 when we had more than one pending.
6124 - If we get a create cell that asks us to extend somewhere, but the
6125 Tor server there doesn't match the expected digest, we now send
6126 a destroy cell back, rather than silently doing nothing.
6127 - Make options->RedirectExit work again.
6128 - Make cookie authentication for the controller work again.
6129 - Stop being picky about unusual characters in the arguments to
6130 mapaddress. It's none of our business.
6131 - Add a new config option "TestVia" that lets you specify preferred
6132 middle hops to use for test circuits. Perhaps this will let me
6133 debug the reachability problems better.
6135 o Log / documentation fixes:
6136 - If we're a server and some peer has a broken TLS certificate, don't
6137 log about it unless ProtocolWarnings is set, i.e., we want to hear
6138 about protocol violations by others.
6139 - Fix spelling of VirtualAddrNetwork in man page.
6140 - Add a better explanation at the top of the autogenerated torrc file
6141 about what happened to our old torrc.
6144 Changes in version 0.1.1.20 - 2006-05-23
6146 - Downgrade a log severity where servers complain that they're
6148 - Avoid a compile warning on FreeBSD.
6149 - Remove string size limit on NEWDESC messages; solve bug 291.
6150 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
6151 more thoroughly when we're running on windows.
6154 Changes in version 0.1.1.19-rc - 2006-05-03
6156 - Regenerate our local descriptor if it's dirty and we try to use
6157 it locally (e.g. if it changes during reachability detection).
6158 - If we setconf our ORPort to 0, we continued to listen on the
6159 old ORPort and receive connections.
6160 - Avoid a second warning about machine/limits.h on Debian
6162 - Be willing to add our own routerinfo into the routerlist.
6163 Now authorities will include themselves in their directories
6164 and network-statuses.
6165 - Stop trying to upload rendezvous descriptors to every
6166 directory authority: only try the v1 authorities.
6167 - Servers no longer complain when they think they're not
6168 registered with the directory authorities. There were too many
6170 - Backport dist-rpm changes so rpms can be built without errors.
6173 - Implement an option, VirtualAddrMask, to set which addresses
6174 get handed out in response to mapaddress requests. This works
6175 around a bug in tsocks where 127.0.0.0/8 is never socksified.
6178 Changes in version 0.1.1.18-rc - 2006-04-10
6180 - Work harder to download live network-statuses from all the
6181 directory authorities we know about. Improve the threshold
6182 decision logic so we're more robust to edge cases.
6183 - When fetching rendezvous descriptors, we were willing to ask
6184 v2 authorities too, which would always return 404.
6187 - Stop listing down or invalid nodes in the v1 directory. This will
6188 reduce its bulk by about 1/3, and reduce load on directory
6190 - When deciding whether a router is Fast or Guard-worthy, consider
6191 his advertised BandwidthRate and not just the BandwidthCapacity.
6192 - No longer ship INSTALL and README files -- they are useless now.
6193 - Force rpmbuild to behave and honor target_cpu.
6194 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
6195 - Start to include translated versions of the tor-doc-*.html
6196 files, along with the screenshots. Still needs more work.
6197 - Start sending back 512 and 451 errors if mapaddress fails,
6198 rather than not sending anything back at all.
6199 - When we fail to bind or listen on an incoming or outgoing
6200 socket, we should close it before failing. otherwise we just
6201 leak it. (thanks to weasel for finding.)
6202 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
6203 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
6204 - Make NoPublish (even though deprecated) work again.
6205 - Fix a minor security flaw where a versioning auth dirserver
6206 could list a recommended version many times in a row to make
6207 clients more convinced that it's recommended.
6208 - Fix crash bug if there are two unregistered servers running
6209 with the same nickname, one of them is down, and you ask for
6210 them by nickname in your EntryNodes or ExitNodes. Also, try
6211 to pick the one that's running rather than an arbitrary one.
6212 - Fix an infinite loop we could hit if we go offline for too long.
6213 - Complain when we hit WSAENOBUFS on recv() or write() too.
6214 Perhaps this will help us hunt the bug.
6215 - If you're not a versioning dirserver, don't put the string
6216 "client-versions \nserver-versions \n" in your network-status.
6217 - Lower the minimum required number of file descriptors to 1000,
6218 so we can have some overhead for Valgrind on Linux, where the
6219 default ulimit -n is 1024.
6222 - Add tor.dizum.com as the fifth authoritative directory server.
6223 - Add a new config option FetchUselessDescriptors, off by default,
6224 for when you plan to run "exitlist" on your client and you want
6225 to know about even the non-running descriptors.
6228 Changes in version 0.1.1.17-rc - 2006-03-28
6230 - Clients and servers since 0.1.1.10-alpha have been expiring
6231 connections whenever they are idle for 5 minutes and they *do*
6232 have circuits on them. Oops. With this new version, clients will
6233 discard their previous entry guard choices and avoid choosing
6234 entry guards running these flawed versions.
6235 - Fix memory leak when uncompressing concatenated zlib streams. This
6236 was causing substantial leaks over time on Tor servers.
6237 - The v1 directory was including servers as much as 48 hours old,
6238 because that's how the new routerlist->routers works. Now only
6239 include them if they're 20 hours old or less.
6242 - Resume building on irix64, netbsd 2.0, etc.
6243 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
6245 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
6246 and it is confusing some users.
6247 - Mirrors stop caching the v1 directory so often.
6248 - Make the max number of old descriptors that a cache will hold
6249 rise with the number of directory authorities, so we can scale.
6250 - Change our win32 uname() hack to be more forgiving about what
6251 win32 versions it thinks it's found.
6254 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
6256 - When the controller's *setconf commands fail, collect an error
6257 message in a string and hand it back to the controller.
6258 - Make the v2 dir's "Fast" flag based on relative capacity, just
6259 like "Stable" is based on median uptime. Name everything in the
6260 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
6261 - Log server fingerprint on startup, so new server operators don't
6262 have to go hunting around their filesystem for it.
6263 - Return a robots.txt on our dirport to discourage google indexing.
6264 - Let the controller ask for GETINFO dir/status/foo so it can ask
6265 directly rather than connecting to the dir port. Only works when
6266 dirport is set for now.
6268 o New config options rather than constants in the code:
6269 - SocksTimeout: How long do we let a socks connection wait
6270 unattached before we fail it?
6271 - CircuitBuildTimeout: Cull non-open circuits that were born
6272 at least this many seconds ago.
6273 - CircuitIdleTimeout: Cull open clean circuits that were born
6274 at least this many seconds ago.
6277 Changes in version 0.1.1.16-rc - 2006-03-18
6278 o Bugfixes on 0.1.1.15-rc:
6279 - Fix assert when the controller asks to attachstream a connect-wait
6280 or resolve-wait stream.
6281 - Now do address rewriting when the controller asks us to attach
6282 to a particular circuit too. This will let Blossom specify
6283 "moria2.exit" without having to learn what moria2's IP address is.
6284 - Make the "tor --verify-config" command-line work again, so people
6285 can automatically check if their torrc will parse.
6286 - Authoritative dirservers no longer require an open connection from
6287 a server to consider him "reachable". We need this change because
6288 when we add new auth dirservers, old servers won't know not to
6290 - Let Tor build on Sun CC again.
6291 - Fix an off-by-one buffer size in dirserv.c that magically never
6292 hit our three authorities but broke sjmurdoch's own tor network.
6293 - If we as a directory mirror don't know of any v1 directory
6294 authorities, then don't try to cache any v1 directories.
6295 - Stop warning about unknown servers in our family when they are
6296 given as hex digests.
6297 - Stop complaining as quickly to the server operator that he
6298 hasn't registered his nickname/key binding.
6299 - Various cleanups so we can add new V2 Auth Dirservers.
6300 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
6301 reflect the updated flags in our v2 dir protocol.
6302 - Resume allowing non-printable characters for exit streams (both
6303 for connecting and for resolving). Now we tolerate applications
6304 that don't follow the RFCs. But continue to block malformed names
6307 o Bugfixes on 0.1.0.x:
6308 - Fix assert bug in close_logs(): when we close and delete logs,
6309 remove them all from the global "logfiles" list.
6310 - Fix minor integer overflow in calculating when we expect to use up
6311 our bandwidth allocation before hibernating.
6312 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
6313 there are multiple SSLs installed with different versions.
6314 - When we try to be a server and Address is not explicitly set and
6315 our hostname resolves to a private IP address, try to use an
6316 interface address if it has a public address. Now Windows machines
6317 that think of themselves as localhost can work by default.
6320 - Let the controller ask for GETINFO dir/server/foo so it can ask
6321 directly rather than connecting to the dir port.
6322 - Let the controller tell us about certain router descriptors
6323 that it doesn't want Tor to use in circuits. Implement
6324 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
6325 - New config option SafeSocks to reject all application connections
6326 using unsafe socks protocols. Defaults to off.
6329 Changes in version 0.1.1.15-rc - 2006-03-11
6330 o Bugfixes and cleanups:
6331 - When we're printing strings from the network, don't try to print
6332 non-printable characters. This protects us against shell escape
6333 sequence exploits, and also against attacks to fool humans into
6334 misreading their logs.
6335 - Fix a bug where Tor would fail to establish any connections if you
6336 left it off for 24 hours and then started it: we were happy with
6337 the obsolete network statuses, but they all referred to router
6338 descriptors that were too old to fetch, so we ended up with no
6339 valid router descriptors.
6340 - Fix a seg fault in the controller's "getinfo orconn-status"
6341 command while listing status on incoming handshaking connections.
6342 Introduce a status name "NEW" for these connections.
6343 - If we get a linelist or linelist_s config option from the torrc
6344 (e.g. ExitPolicy) and it has no value, warn and skip rather than
6345 silently resetting it to its default.
6346 - Don't abandon entry guards until they've been down or gone for
6348 - Cleaner and quieter log messages.
6351 - New controller signal NEWNYM that makes new application requests
6353 - Add a new circuit purpose 'controller' to let the controller ask
6354 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
6355 controller command to let you specify the purpose if you're
6356 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
6357 command to let you change a circuit's purpose after it's been
6359 - Accept "private:*" in routerdesc exit policies; not generated yet
6360 because older Tors do not understand it.
6361 - Add BSD-style contributed startup script "rc.subr" from Peter
6365 Changes in version 0.1.1.14-alpha - 2006-02-20
6366 o Bugfixes on 0.1.1.x:
6367 - Don't die if we ask for a stdout or stderr log (even implicitly)
6368 and we're set to RunAsDaemon -- just warn.
6369 - We still had a few bugs in the OR connection rotation code that
6370 caused directory servers to slowly aggregate connections to other
6371 fast Tor servers. This time for sure!
6372 - Make log entries on Win32 include the name of the function again.
6373 - We were treating a pair of exit policies if they were equal even
6374 if one said accept and the other said reject -- causing us to
6375 not always publish a new descriptor since we thought nothing
6377 - Retry pending server downloads as well as pending networkstatus
6378 downloads when we unexpectedly get a socks request.
6379 - We were ignoring the IS_FAST flag in the directory status,
6380 meaning we were willing to pick trivial-bandwidth nodes for "fast"
6382 - If the controller's SAVECONF command fails (e.g. due to file
6383 permissions), let the controller know that it failed.
6386 - If we're trying to be a Tor server and running Windows 95/98/ME
6387 as a server, explain that we'll likely crash.
6388 - When we're a server, a client asks for an old-style directory,
6389 and our write bucket is empty, don't give it to him. This way
6390 small servers can continue to serve the directory *sometimes*,
6391 without getting overloaded.
6392 - Compress exit policies even more -- look for duplicate lines
6394 - Clients now honor the "guard" flag in the router status when
6395 picking entry guards, rather than looking at is_fast or is_stable.
6396 - Retain unrecognized lines in $DATADIR/state file, so that we can
6397 be forward-compatible.
6398 - Generate 18.0.0.0/8 address policy format in descs when we can;
6399 warn when the mask is not reducible to a bit-prefix.
6400 - Let the user set ControlListenAddress in the torrc. This can be
6401 dangerous, but there are some cases (like a secured LAN) where it
6403 - Split ReachableAddresses into ReachableDirAddresses and
6404 ReachableORAddresses, so we can restrict Dir conns to port 80
6405 and OR conns to port 443.
6406 - Now we can target arch and OS in rpm builds (contributed by
6407 Phobos). Also make the resulting dist-rpm filename match the
6409 - New config options to help controllers: FetchServerDescriptors
6410 and FetchHidServDescriptors for whether to fetch server
6411 info and hidserv info or let the controller do it, and
6412 PublishServerDescriptor and PublishHidServDescriptors.
6413 - Also let the controller set the __AllDirActionsPrivate config
6414 option if you want all directory fetches/publishes to happen via
6415 Tor (it assumes your controller bootstraps your circuits).
6418 Changes in version 0.1.0.17 - 2006-02-17
6419 o Crash bugfixes on 0.1.0.x:
6420 - When servers with a non-zero DirPort came out of hibernation,
6421 sometimes they would trigger an assert.
6423 o Other important bugfixes:
6424 - On platforms that don't have getrlimit (like Windows), we were
6425 artificially constraining ourselves to a max of 1024
6426 connections. Now just assume that we can handle as many as 15000
6427 connections. Hopefully this won't cause other problems.
6429 o Backported features:
6430 - When we're a server, a client asks for an old-style directory,
6431 and our write bucket is empty, don't give it to him. This way
6432 small servers can continue to serve the directory *sometimes*,
6433 without getting overloaded.
6434 - Whenever you get a 503 in response to a directory fetch, try
6435 once more. This will become important once servers start sending
6436 503's whenever they feel busy.
6437 - Fetch a new directory every 120 minutes, not every 40 minutes.
6438 Now that we have hundreds of thousands of users running the old
6439 directory algorithm, it's starting to hurt a lot.
6440 - Bump up the period for forcing a hidden service descriptor upload
6441 from 20 minutes to 1 hour.
6444 Changes in version 0.1.1.13-alpha - 2006-02-09
6445 o Crashes in 0.1.1.x:
6446 - When you tried to setconf ORPort via the controller, Tor would
6447 crash. So people using TorCP to become a server were sad.
6448 - Solve (I hope) the stack-smashing bug that we were seeing on fast
6449 servers. The problem appears to be something do with OpenSSL's
6450 random number generation, or how we call it, or something. Let me
6451 know if the crashes continue.
6452 - Turn crypto hardware acceleration off by default, until we find
6453 somebody smart who can test it for us. (It appears to produce
6454 seg faults in at least some cases.)
6455 - Fix a rare assert error when we've tried all intro points for
6456 a hidden service and we try fetching the service descriptor again:
6457 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
6460 - Fix a major load balance bug: we were round-robining in 16 KB
6461 chunks, and servers with bandwidthrate of 20 KB, while downloading
6462 a 600 KB directory, would starve their other connections. Now we
6463 try to be a bit more fair.
6464 - Dir authorities and mirrors were never expiring the newest
6465 descriptor for each server, causing memory and directory bloat.
6466 - Fix memory-bloating and connection-bloating bug on servers: We
6467 were never closing any connection that had ever had a circuit on
6468 it, because we were checking conn->n_circuits == 0, yet we had a
6469 bug that let it go negative.
6470 - Make Tor work using squid as your http proxy again -- squid
6471 returns an error if you ask for a URL that's too long, and it uses
6472 a really generic error message. Plus, many people are behind a
6473 transparent squid so they don't even realize it.
6474 - On platforms that don't have getrlimit (like Windows), we were
6475 artificially constraining ourselves to a max of 1024
6476 connections. Now just assume that we can handle as many as 15000
6477 connections. Hopefully this won't cause other problems.
6478 - Add a new config option ExitPolicyRejectPrivate which defaults to
6479 1. This means all exit policies will begin with rejecting private
6480 addresses, unless the server operator explicitly turns it off.
6483 - Clients no longer download descriptors for non-running
6485 - Before we add new directory authorities, we should make it
6486 clear that only v1 authorities should receive/publish hidden
6487 service descriptors.
6490 - As soon as we've fetched some more directory info, immediately
6491 try to download more server descriptors. This way we don't have
6492 a 10 second pause during initial bootstrapping.
6493 - Remove even more loud log messages that the server operator can't
6495 - When we're running an obsolete or un-recommended version, make
6496 the log message more clear about what the problem is and what
6497 versions *are* still recommended.
6498 - Provide a more useful warn message when our onion queue gets full:
6499 the CPU is too slow or the exit policy is too liberal.
6500 - Don't warn when we receive a 503 from a dirserver/cache -- this
6501 will pave the way for them being able to refuse if they're busy.
6502 - When we fail to bind a listener, try to provide a more useful
6503 log message: e.g., "Is Tor already running?"
6504 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
6505 Goldberg can prove things about our handshake protocol more
6507 - MaxConn has been obsolete for a while now. Document the ConnLimit
6508 config option, which is a *minimum* number of file descriptors
6509 that must be available else Tor refuses to start.
6510 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
6511 if you log to syslog and want something other than LOG_DAEMON.
6512 - Make dirservers generate a separate "guard" flag to mean,
6513 "would make a good entry guard". Make clients parse it and vote
6514 on it. Not used by clients yet.
6515 - Implement --with-libevent-dir option to ./configure. Also, improve
6516 search techniques to find libevent, and use those for openssl too.
6517 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
6518 - Only start testing reachability once we've established a
6519 circuit. This will make startup on dirservers less noisy.
6520 - Don't try to upload hidden service descriptors until we have
6521 established a circuit.
6522 - Fix the controller's "attachstream 0" command to treat conn like
6523 it just connected, doing address remapping, handling .exit and
6524 .onion idioms, and so on. Now we're more uniform in making sure
6525 that the controller hears about new and closing connections.
6528 Changes in version 0.1.1.12-alpha - 2006-01-11
6529 o Bugfixes on 0.1.1.x:
6530 - The fix to close duplicate server connections was closing all
6531 Tor client connections if they didn't establish a circuit
6532 quickly enough. Oops.
6533 - Fix minor memory issue (double-free) that happened on exit.
6535 o Bugfixes on 0.1.0.x:
6536 - Tor didn't warn when it failed to open a log file.
6539 Changes in version 0.1.1.11-alpha - 2006-01-10
6540 o Crashes in 0.1.1.x:
6541 - Include all the assert/crash fixes from 0.1.0.16.
6542 - If you start Tor and then quit very quickly, there were some
6543 races that tried to free things that weren't allocated yet.
6544 - Fix a rare memory stomp if you're running hidden services.
6545 - Fix segfault when specifying DirServer in config without nickname.
6546 - Fix a seg fault when you finish connecting to a server but at
6547 that moment you dump his server descriptor.
6548 - Extendcircuit and Attachstream controller commands would
6549 assert/crash if you don't give them enough arguments.
6550 - Fix an assert error when we're out of space in the connection_list
6551 and we try to post a hidden service descriptor (reported by weasel).
6552 - If you specify a relative torrc path and you set RunAsDaemon in
6553 your torrc, then it chdir()'s to the new directory. If you HUP,
6554 it tries to load the new torrc location, fails, and exits.
6555 The fix: no longer allow a relative path to torrc using -f.
6558 - Implement "entry guards": automatically choose a handful of entry
6559 nodes and stick with them for all circuits. Only pick new guards
6560 when the ones you have are unsuitable, and if the old guards
6561 become suitable again, switch back. This will increase security
6562 dramatically against certain end-point attacks. The EntryNodes
6563 config option now provides some hints about which entry guards you
6564 want to use most; and StrictEntryNodes means to only use those.
6565 - New directory logic: download by descriptor digest, not by
6566 fingerprint. Caches try to download all listed digests from
6567 authorities; clients try to download "best" digests from caches.
6568 This avoids partitioning and isolating attacks better.
6569 - Make the "stable" router flag in network-status be the median of
6570 the uptimes of running valid servers, and make clients pay
6571 attention to the network-status flags. Thus the cutoff adapts
6572 to the stability of the network as a whole, making IRC, IM, etc
6573 connections more reliable.
6576 - Tor servers with dynamic IP addresses were needing to wait 18
6577 hours before they could start doing reachability testing using
6578 the new IP address and ports. This is because they were using
6579 the internal descriptor to learn what to test, yet they were only
6580 rebuilding the descriptor once they decided they were reachable.
6581 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
6582 to download certain server descriptors, throw them away, and then
6583 fetch them again after 30 minutes. Now mirrors throw away these
6584 server descriptors so clients can't get them.
6585 - We were leaving duplicate connections to other ORs open for a week,
6586 rather than closing them once we detect a duplicate. This only
6587 really affected authdirservers, but it affected them a lot.
6588 - Spread the authdirservers' reachability testing over the entire
6589 testing interval, so we don't try to do 500 TLS's at once every
6593 - If the network is down, and we try to connect to a conn because
6594 we have a circuit in mind, and we timeout (30 seconds) because the
6595 network never answers, we were expiring the circuit, but we weren't
6596 obsoleting the connection or telling the entry_guards functions.
6597 - Some Tor servers process billions of cells per day. These statistics
6598 need to be uint64_t's.
6599 - Check for integer overflows in more places, when adding elements
6600 to smartlists. This could possibly prevent a buffer overflow
6601 on malicious huge inputs. I don't see any, but I haven't looked
6603 - ReachableAddresses kept growing new "reject *:*" lines on every
6605 - When you "setconf log" via the controller, it should remove all
6606 logs. We were automatically adding back in a "log notice stdout".
6607 - Newly bootstrapped Tor networks couldn't establish hidden service
6608 circuits until they had nodes with high uptime. Be more tolerant.
6609 - We were marking servers down when they could not answer every piece
6610 of the directory request we sent them. This was far too harsh.
6611 - Fix the torify (tsocks) config file to not use Tor for localhost
6613 - Directory authorities now go to the proper authority when asking for
6614 a networkstatus, even when they want a compressed one.
6615 - Fix a harmless bug that was causing Tor servers to log
6616 "Got an end because of misc error, but we're not an AP. Closing."
6617 - Authorities were treating their own descriptor changes as cosmetic,
6618 meaning the descriptor available in the network-status and the
6619 descriptor that clients downloaded were different.
6620 - The OS X installer was adding a symlink for tor_resolve but
6621 the binary was called tor-resolve (reported by Thomas Hardly).
6622 - Workaround a problem with some http proxies where they refuse GET
6623 requests that specify "Content-Length: 0" (reported by Adrian).
6624 - Fix wrong log message when you add a "HiddenServiceNodes" config
6625 line without any HiddenServiceDir line (reported by Chris Thomas).
6628 - Write the TorVersion into the state file so we have a prayer of
6629 keeping forward and backward compatibility.
6630 - Revive the FascistFirewall config option rather than eliminating it:
6631 now it's a synonym for ReachableAddresses *:80,*:443.
6632 - Clients choose directory servers from the network status lists,
6633 not from their internal list of router descriptors. Now they can
6634 go to caches directly rather than needing to go to authorities
6636 - Directory authorities ignore router descriptors that have only
6637 cosmetic differences: do this for 0.1.0.x servers now too.
6638 - Add a new flag to network-status indicating whether the server
6639 can answer v2 directory requests too.
6640 - Authdirs now stop whining so loudly about bad descriptors that
6641 they fetch from other dirservers. So when there's a log complaint,
6642 it's for sure from a freshly uploaded descriptor.
6643 - Reduce memory requirements in our structs by changing the order
6645 - There used to be two ways to specify your listening ports in a
6646 server descriptor: on the "router" line and with a separate "ports"
6647 line. Remove support for the "ports" line.
6648 - New config option "AuthDirRejectUnlisted" for auth dirservers as
6649 a panic button: if we get flooded with unusable servers we can
6650 revert to only listing servers in the approved-routers file.
6651 - Auth dir servers can now mark a fingerprint as "!reject" or
6652 "!invalid" in the approved-routers file (as its nickname), to
6653 refuse descriptors outright or include them but marked as invalid.
6654 - Servers store bandwidth history across restarts/crashes.
6655 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
6656 get a better idea of why their circuits failed. Not used yet.
6657 - Directory mirrors now cache up to 16 unrecognized network-status
6658 docs. Now we can add new authdirservers and they'll be cached too.
6659 - When picking a random directory, prefer non-authorities if any
6661 - New controller option "getinfo desc/all-recent" to fetch the
6662 latest server descriptor for every router that Tor knows about.
6665 Changes in version 0.1.0.16 - 2006-01-02
6666 o Crash bugfixes on 0.1.0.x:
6667 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
6668 corrupting the heap, losing FDs, or crashing when we need to resize
6669 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
6670 - It turns out sparc64 platforms crash on unaligned memory access
6671 too -- so detect and avoid this.
6672 - Handle truncated compressed data correctly (by detecting it and
6674 - Fix possible-but-unlikely free(NULL) in control.c.
6675 - When we were closing connections, there was a rare case that
6676 stomped on memory, triggering seg faults and asserts.
6677 - Avoid potential infinite recursion when building a descriptor. (We
6678 don't know that it ever happened, but better to fix it anyway.)
6679 - We were neglecting to unlink marked circuits from soon-to-close OR
6680 connections, which caused some rare scribbling on freed memory.
6681 - Fix a memory stomping race bug when closing the joining point of two
6682 rendezvous circuits.
6683 - Fix an assert in time parsing found by Steven Murdoch.
6685 o Other bugfixes on 0.1.0.x:
6686 - When we're doing reachability testing, provide more useful log
6687 messages so the operator knows what to expect.
6688 - Do not check whether DirPort is reachable when we are suppressing
6689 advertising it because of hibernation.
6690 - When building with -static or on Solaris, we sometimes needed -ldl.
6691 - When we're deciding whether a stream has enough circuits around
6692 that can handle it, count the freshly dirty ones and not the ones
6693 that are so dirty they won't be able to handle it.
6694 - When we're expiring old circuits, we had a logic error that caused
6695 us to close new rendezvous circuits rather than old ones.
6696 - Give a more helpful log message when you try to change ORPort via
6697 the controller: you should upgrade Tor if you want that to work.
6698 - We were failing to parse Tor versions that start with "Tor ".
6699 - Tolerate faulty streams better: when a stream fails for reason
6700 exitpolicy, stop assuming that the router is lying about his exit
6701 policy. When a stream fails for reason misc, allow it to retry just
6702 as if it was resolvefailed. When a stream has failed three times,
6703 reset its failure count so we can try again and get all three tries.
6706 Changes in version 0.1.1.10-alpha - 2005-12-11
6707 o Correctness bugfixes on 0.1.0.x:
6708 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
6709 corrupting the heap, losing FDs, or crashing when we need to resize
6710 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
6711 - Stop doing the complex voodoo overkill checking for insecure
6712 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
6713 - When we were closing connections, there was a rare case that
6714 stomped on memory, triggering seg faults and asserts.
6715 - We were neglecting to unlink marked circuits from soon-to-close OR
6716 connections, which caused some rare scribbling on freed memory.
6717 - When we're deciding whether a stream has enough circuits around
6718 that can handle it, count the freshly dirty ones and not the ones
6719 that are so dirty they won't be able to handle it.
6720 - Recover better from TCP connections to Tor servers that are
6721 broken but don't tell you (it happens!); and rotate TLS
6722 connections once a week.
6723 - When we're expiring old circuits, we had a logic error that caused
6724 us to close new rendezvous circuits rather than old ones.
6725 - Fix a scary-looking but apparently harmless bug where circuits
6726 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
6727 servers, and never switch to state CIRCUIT_STATE_OPEN.
6728 - When building with -static or on Solaris, we sometimes needed to
6730 - Give a useful message when people run Tor as the wrong user,
6731 rather than telling them to start chowning random directories.
6732 - We were failing to inform the controller about new .onion streams.
6734 o Security bugfixes on 0.1.0.x:
6735 - Refuse server descriptors if the fingerprint line doesn't match
6736 the included identity key. Tor doesn't care, but other apps (and
6737 humans) might actually be trusting the fingerprint line.
6738 - We used to kill the circuit when we receive a relay command we
6739 don't recognize. Now we just drop it.
6740 - Start obeying our firewall options more rigorously:
6741 . If we can't get to a dirserver directly, try going via Tor.
6742 . Don't ever try to connect (as a client) to a place our
6743 firewall options forbid.
6744 . If we specify a proxy and also firewall options, obey the
6745 firewall options even when we're using the proxy: some proxies
6746 can only proxy to certain destinations.
6747 - Fix a bug found by Lasse Overlier: when we were making internal
6748 circuits (intended to be cannibalized later for rendezvous and
6749 introduction circuits), we were picking them so that they had
6750 useful exit nodes. There was no need for this, and it actually
6751 aids some statistical attacks.
6752 - Start treating internal circuits and exit circuits separately.
6753 It's important to keep them separate because internal circuits
6754 have their last hops picked like middle hops, rather than like
6755 exit hops. So exiting on them will break the user's expectations.
6757 o Bugfixes on 0.1.1.x:
6758 - Take out the mis-feature where we tried to detect IP address
6759 flapping for people with DynDNS, and chose not to upload a new
6760 server descriptor sometimes.
6761 - Try to be compatible with OpenSSL 0.9.6 again.
6762 - Log fix: when the controller is logging about .onion addresses,
6763 sometimes it didn't include the ".onion" part of the address.
6764 - Don't try to modify options->DirServers internally -- if the
6765 user didn't specify any, just add the default ones directly to
6766 the trusted dirserver list. This fixes a bug where people running
6767 controllers would use SETCONF on some totally unrelated config
6768 option, and Tor would start yelling at them about changing their
6770 - Let the controller's redirectstream command specify a port, in
6771 case the controller wants to change that too.
6772 - When we requested a pile of server descriptors, we sometimes
6773 accidentally launched a duplicate request for the first one.
6774 - Bugfix for trackhostexits: write down the fingerprint of the
6775 chosen exit, not its nickname, because the chosen exit might not
6777 - When parsing foo.exit, if foo is unknown, and we are leaving
6778 circuits unattached, set the chosen_exit field and leave the
6779 address empty. This matters because controllers got confused
6781 - Directory authorities no longer try to download server
6782 descriptors that they know they will reject.
6784 o Features and updates:
6785 - Replace balanced trees with hash tables: this should make stuff
6786 significantly faster.
6787 - Resume using the AES counter-mode implementation that we ship,
6788 rather than OpenSSL's. Ours is significantly faster.
6789 - Many other CPU and memory improvements.
6790 - Add a new config option FastFirstHopPK (on by default) so clients
6791 do a trivial crypto handshake for their first hop, since TLS has
6792 already taken care of confidentiality and authentication.
6793 - Add a new config option TestSocks so people can see if their
6794 applications are using socks4, socks4a, socks5-with-ip, or
6795 socks5-with-hostname. This way they don't have to keep mucking
6796 with tcpdump and wondering if something got cached somewhere.
6797 - Warn when listening on a public address for socks. I suspect a
6798 lot of people are setting themselves up as open socks proxies,
6799 and they have no idea that jerks on the Internet are using them,
6800 since they simply proxy the traffic into the Tor network.
6801 - Add "private:*" as an alias in configuration for policies. Now
6802 you can simplify your exit policy rather than needing to list
6803 every single internal or nonroutable network space.
6804 - Add a new controller event type that allows controllers to get
6805 all server descriptors that were uploaded to a router in its role
6806 as authoritative dirserver.
6807 - Start shipping socks-extensions.txt, tor-doc-unix.html,
6808 tor-doc-server.html, and stylesheet.css in the tarball.
6809 - Stop shipping tor-doc.html in the tarball.
6812 Changes in version 0.1.1.9-alpha - 2005-11-15
6813 o Usability improvements:
6814 - Start calling it FooListenAddress rather than FooBindAddress,
6815 since few of our users know what it means to bind an address
6817 - Reduce clutter in server logs. We're going to try to make
6818 them actually usable now. New config option ProtocolWarnings that
6819 lets you hear about how _other Tors_ are breaking the protocol. Off
6821 - Divide log messages into logging domains. Once we put some sort
6822 of interface on this, it will let people looking at more verbose
6823 log levels specify the topics they want to hear more about.
6824 - Make directory servers return better http 404 error messages
6825 instead of a generic "Servers unavailable".
6826 - Check for even more Windows version flags when writing the platform
6827 string in server descriptors, and note any we don't recognize.
6828 - Clean up more of the OpenSSL memory when exiting, so we can detect
6829 memory leaks better.
6830 - Make directory authorities be non-versioning, non-naming by
6831 default. Now we can add new directory servers without requiring
6832 their operators to pay close attention.
6833 - When logging via syslog, include the pid whenever we provide
6834 a log entry. Suggested by Todd Fries.
6836 o Performance improvements:
6837 - Directory servers now silently throw away new descriptors that
6838 haven't changed much if the timestamps are similar. We do this to
6839 tolerate older Tor servers that upload a new descriptor every 15
6840 minutes. (It seemed like a good idea at the time.)
6841 - Inline bottleneck smartlist functions; use fast versions by default.
6842 - Add a "Map from digest to void*" abstraction digestmap_t so we
6843 can do less hex encoding/decoding. Use it in router_get_by_digest()
6844 to resolve a performance bottleneck.
6845 - Allow tor_gzip_uncompress to extract as much as possible from
6846 truncated compressed data. Try to extract as many
6847 descriptors as possible from truncated http responses (when
6848 DIR_PURPOSE_FETCH_ROUTERDESC).
6849 - Make circ->onionskin a pointer, not a static array. moria2 was using
6850 125000 circuit_t's after it had been up for a few weeks, which
6851 translates to 20+ megs of wasted space.
6852 - The private half of our EDH handshake keys are now chosen out
6853 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
6855 o Security improvements:
6856 - Start making directory caches retain old routerinfos, so soon
6857 clients can start asking by digest of descriptor rather than by
6858 fingerprint of server.
6859 - Add half our entropy from RAND_poll in OpenSSL. This knows how
6860 to use egd (if present), openbsd weirdness (if present), vms/os2
6861 weirdness (if we ever port there), and more in the future.
6863 o Bugfixes on 0.1.0.x:
6864 - Do round-robin writes of at most 16 kB per write. This might be
6865 more fair on loaded Tor servers, and it might resolve our Windows
6866 crash bug. It might also slow things down.
6867 - Our TLS handshakes were generating a single public/private
6868 keypair for the TLS context, rather than making a new one for
6869 each new connections. Oops. (But we were still rotating them
6870 periodically, so it's not so bad.)
6871 - When we were cannibalizing a circuit with a particular exit
6872 node in mind, we weren't checking to see if that exit node was
6873 already present earlier in the circuit. Oops.
6874 - When a Tor server's IP changes (e.g. from a dyndns address),
6875 upload a new descriptor so clients will learn too.
6876 - Really busy servers were keeping enough circuits open on stable
6877 connections that they were wrapping around the circuit_id
6878 space. (It's only two bytes.) This exposed a bug where we would
6879 feel free to reuse a circuit_id even if it still exists but has
6880 been marked for close. Try to fix this bug. Some bug remains.
6881 - If we would close a stream early (e.g. it asks for a .exit that
6882 we know would refuse it) but the LeaveStreamsUnattached config
6883 option is set by the controller, then don't close it.
6885 o Bugfixes on 0.1.1.8-alpha:
6886 - Fix a big pile of memory leaks, some of them serious.
6887 - Do not try to download a routerdesc if we would immediately reject
6889 - Resume inserting a newline between all router descriptors when
6890 generating (old style) signed directories, since our spec says
6892 - When providing content-type application/octet-stream for
6893 server descriptors using .z, we were leaving out the
6894 content-encoding header. Oops. (Everything tolerated this just
6895 fine, but that doesn't mean we need to be part of the problem.)
6896 - Fix a potential seg fault in getconf and getinfo using version 1
6897 of the controller protocol.
6898 - Avoid crash: do not check whether DirPort is reachable when we
6899 are suppressing it because of hibernation.
6900 - Make --hash-password not crash on exit.
6903 Changes in version 0.1.1.8-alpha - 2005-10-07
6904 o New features (major):
6905 - Clients don't download or use the directory anymore. Now they
6906 download and use network-statuses from the trusted dirservers,
6907 and fetch individual server descriptors as needed from mirrors.
6908 See dir-spec.txt for all the gory details.
6909 - Be more conservative about whether to advertise our DirPort.
6910 The main change is to not advertise if we're running at capacity
6911 and either a) we could hibernate or b) our capacity is low and
6912 we're using a default DirPort.
6913 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
6915 o New features (minor):
6916 - Try to be smart about when to retry network-status and
6917 server-descriptor fetches. Still needs some tuning.
6918 - Stop parsing, storing, or using running-routers output (but
6919 mirrors still cache and serve it).
6920 - Consider a threshold of versioning dirservers (dirservers who have
6921 an opinion about which Tor versions are still recommended) before
6922 deciding whether to warn the user that he's obsolete.
6923 - Dirservers can now reject/invalidate by key and IP, with the
6924 config options "AuthDirInvalid" and "AuthDirReject". This is
6925 useful since currently we automatically list servers as running
6926 and usable even if we know they're jerks.
6927 - Provide dire warnings to any users who set DirServer; move it out
6928 of torrc.sample and into torrc.complete.
6929 - Add MyFamily to torrc.sample in the server section.
6930 - Add nicknames to the DirServer line, so we can refer to them
6931 without requiring all our users to memorize their IP addresses.
6932 - When we get an EOF or a timeout on a directory connection, note
6933 how many bytes of serverdesc we are dropping. This will help
6934 us determine whether it is smart to parse incomplete serverdesc
6936 - Add a new function to "change pseudonyms" -- that is, to stop
6937 using any currently-dirty circuits for new streams, so we don't
6938 link new actions to old actions. Currently it's only called on
6939 HUP (or SIGNAL RELOAD).
6940 - On sighup, if UseHelperNodes changed to 1, use new circuits.
6941 - Start using RAND_bytes rather than RAND_pseudo_bytes from
6942 OpenSSL. Also, reseed our entropy every hour, not just at
6943 startup. And entropy in 512-bit chunks, not 160-bit chunks.
6945 o Fixes on 0.1.1.7-alpha:
6946 - Nobody ever implemented EVENT_ADDRMAP for control protocol
6947 version 0, so don't let version 0 controllers ask for it.
6948 - If you requested something with too many newlines via the
6949 v1 controller protocol, you could crash tor.
6950 - Fix a number of memory leaks, including some pretty serious ones.
6951 - Re-enable DirPort testing again, so Tor servers will be willing
6952 to advertise their DirPort if it's reachable.
6953 - On TLS handshake, only check the other router's nickname against
6954 its expected nickname if is_named is set.
6956 o Fixes forward-ported from 0.1.0.15:
6957 - Don't crash when we don't have any spare file descriptors and we
6958 try to spawn a dns or cpu worker.
6959 - Make the numbers in read-history and write-history into uint64s,
6960 so they don't overflow and publish negatives in the descriptor.
6963 - For the OS X package's modified privoxy config file, comment
6964 out the "logfile" line so we don't log everything passed
6966 - We were whining about using socks4 or socks5-with-local-lookup
6967 even when it's an IP in the "virtual" range we designed exactly
6969 - We were leaking some memory every time the client changes IPs.
6970 - Never call free() on tor_malloc()d memory. This will help us
6971 use dmalloc to detect memory leaks.
6972 - Check for named servers when looking them up by nickname;
6973 warn when we'recalling a non-named server by its nickname;
6974 don't warn twice about the same name.
6975 - Try to list MyFamily elements by key, not by nickname, and warn
6976 if we've not heard of the server.
6977 - Make windows platform detection (uname equivalent) smarter.
6978 - It turns out sparc64 doesn't like unaligned access either.
6981 Changes in version 0.1.0.15 - 2005-09-23
6982 o Bugfixes on 0.1.0.x:
6983 - Reject ports 465 and 587 (spam targets) in default exit policy.
6984 - Don't crash when we don't have any spare file descriptors and we
6985 try to spawn a dns or cpu worker.
6986 - Get rid of IgnoreVersion undocumented config option, and make us
6987 only warn, never exit, when we're running an obsolete version.
6988 - Don't try to print a null string when your server finds itself to
6989 be unreachable and the Address config option is empty.
6990 - Make the numbers in read-history and write-history into uint64s,
6991 so they don't overflow and publish negatives in the descriptor.
6992 - Fix a minor memory leak in smartlist_string_remove().
6993 - We were only allowing ourselves to upload a server descriptor at
6994 most every 20 minutes, even if it changed earlier than that.
6995 - Clean up log entries that pointed to old URLs.
6998 Changes in version 0.1.1.7-alpha - 2005-09-14
6999 o Fixes on 0.1.1.6-alpha:
7000 - Exit servers were crashing when people asked them to make a
7001 connection to an address not in their exit policy.
7002 - Looking up a non-existent stream for a v1 control connection would
7004 - Fix a seg fault if we ask a dirserver for a descriptor by
7005 fingerprint but he doesn't know about him.
7006 - SETCONF was appending items to linelists, not clearing them.
7007 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
7008 out and refuse the setconf if it would fail.
7009 - Downgrade the dirserver log messages when whining about
7013 - Add Peter Palfrader's check-tor script to tor/contrib/
7014 It lets you easily check whether a given server (referenced by
7015 nickname) is reachable by you.
7016 - Numerous changes to move towards client-side v2 directories. Not
7020 - If the user gave tor an odd number of command-line arguments,
7021 we were silently ignoring the last one. Now we complain and fail.
7022 [This wins the oldest-bug prize -- this bug has been present since
7023 November 2002, as released in Tor 0.0.0.]
7024 - Do not use unaligned memory access on alpha, mips, or mipsel.
7025 It *works*, but is very slow, so we treat them as if it doesn't.
7026 - Retry directory requests if we fail to get an answer we like
7027 from a given dirserver (we were retrying before, but only if
7028 we fail to connect).
7029 - When writing the RecommendedVersions line, sort them first.
7030 - When the client asked for a rendezvous port that the hidden
7031 service didn't want to provide, we were sending an IP address
7032 back along with the end cell. Fortunately, it was zero. But stop
7034 - Correct "your server is reachable" log entries to indicate that
7035 it was self-testing that told us so.
7038 Changes in version 0.1.1.6-alpha - 2005-09-09
7039 o Fixes on 0.1.1.5-alpha:
7040 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
7041 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
7042 - Fix bug with tor_memmem finding a match at the end of the string.
7043 - Make unit tests run without segfaulting.
7044 - Resolve some solaris x86 compile warnings.
7045 - Handle duplicate lines in approved-routers files without warning.
7046 - Fix bug where as soon as a server refused any requests due to his
7047 exit policy (e.g. when we ask for localhost and he tells us that's
7048 127.0.0.1 and he won't do it), we decided he wasn't obeying his
7049 exit policy using him for any exits.
7050 - Only do openssl hardware accelerator stuff if openssl version is
7053 o New controller features/fixes:
7054 - Add a "RESETCONF" command so you can set config options like
7055 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
7056 a config option in the torrc with no value, then it clears it
7057 entirely (rather than setting it to its default).
7058 - Add a "GETINFO config-file" to tell us where torrc is.
7059 - Avoid sending blank lines when GETINFO replies should be empty.
7060 - Add a QUIT command for the controller (for using it manually).
7061 - Fix a bug in SAVECONF that was adding default dirservers and
7062 other redundant entries to the torrc file.
7064 o Start on the new directory design:
7065 - Generate, publish, cache, serve new network-status format.
7066 - Publish individual descriptors (by fingerprint, by "all", and by
7068 - Publish client and server recommended versions separately.
7069 - Allow tor_gzip_uncompress() to handle multiple concatenated
7070 compressed strings. Serve compressed groups of router
7071 descriptors. The compression logic here could be more
7073 - Distinguish v1 authorities (all currently trusted directories)
7074 from v2 authorities (all trusted directories).
7075 - Change DirServers config line to note which dirs are v1 authorities.
7076 - Add configuration option "V1AuthoritativeDirectory 1" which
7077 moria1, moria2, and tor26 should set.
7078 - Remove option when getting directory cache to see whether they
7079 support running-routers; they all do now. Replace it with one
7080 to see whether caches support v2 stuff.
7083 - Dirservers now do their own external reachability testing of each
7084 Tor server, and only list them as running if they've been found to
7085 be reachable. We also send back warnings to the server's logs if
7086 it uploads a descriptor that we already believe is unreachable.
7087 - Implement exit enclaves: if we know an IP address for the
7088 destination, and there's a running Tor server at that address
7089 which allows exit to the destination, then extend the circuit to
7090 that exit first. This provides end-to-end encryption and end-to-end
7091 authentication. Also, if the user wants a .exit address or enclave,
7092 use 4 hops rather than 3, and cannibalize a general circ for it
7094 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
7095 controller. Also, rotate dns and cpu workers if the controller
7096 changes options that will affect them; and initialize the dns
7097 worker cache tree whether or not we start out as a server.
7098 - Only upload a new server descriptor when options change, 18
7099 hours have passed, uptime is reset, or bandwidth changes a lot.
7100 - Check [X-]Forwarded-For headers in HTTP requests when generating
7101 log messages. This lets people run dirservers (and caches) behind
7102 Apache but still know which IP addresses are causing warnings.
7104 o Config option changes:
7105 - Replace (Fascist)Firewall* config options with a new
7106 ReachableAddresses option that understands address policies.
7107 For example, "ReachableAddresses *:80,*:443"
7108 - Get rid of IgnoreVersion undocumented config option, and make us
7109 only warn, never exit, when we're running an obsolete version.
7110 - Make MonthlyAccountingStart config option truly obsolete now.
7113 - Reject ports 465 and 587 in the default exit policy, since
7114 people have started using them for spam too.
7115 - It turns out we couldn't bootstrap a network since we added
7116 reachability detection in 0.1.0.1-rc. Good thing the Tor network
7117 has never gone down. Add an AssumeReachable config option to let
7118 servers and dirservers bootstrap. When we're trying to build a
7119 high-uptime or high-bandwidth circuit but there aren't enough
7120 suitable servers, try being less picky rather than simply failing.
7121 - Our logic to decide if the OR we connected to was the right guy
7122 was brittle and maybe open to a mitm for unverified routers.
7123 - We weren't cannibalizing circuits correctly for
7124 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
7125 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
7126 build those from scratch. This should make hidden services faster.
7127 - Predict required circuits better, with an eye toward making hidden
7128 services faster on the service end.
7129 - Retry streams if the exit node sends back a 'misc' failure. This
7130 should result in fewer random failures. Also, after failing
7131 from resolve failed or misc, reset the num failures, so we give
7132 it a fair shake next time we try.
7133 - Clean up the rendezvous warn log msgs, and downgrade some to info.
7134 - Reduce severity on logs about dns worker spawning and culling.
7135 - When we're shutting down and we do something like try to post a
7136 server descriptor or rendezvous descriptor, don't complain that
7137 we seem to be unreachable. Of course we are, we're shutting down.
7138 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
7139 We don't use them yet, but maybe one day our DNS resolver will be
7140 able to discover them.
7141 - Make ContactInfo mandatory for authoritative directory servers.
7142 - Require server descriptors to list IPv4 addresses -- hostnames
7143 are no longer allowed. This also fixes some potential security
7144 problems with people providing hostnames as their address and then
7145 preferentially resolving them to partition users.
7146 - Change log line for unreachability to explicitly suggest /etc/hosts
7147 as the culprit. Also make it clearer what IP address and ports we're
7148 testing for reachability.
7149 - Put quotes around user-supplied strings when logging so users are
7150 more likely to realize if they add bad characters (like quotes)
7152 - Let auth dir servers start without specifying an Address config
7154 - Make unit tests (and other invocations that aren't the real Tor)
7155 run without launching listeners, creating subdirectories, and so on.
7158 Changes in version 0.1.1.5-alpha - 2005-08-08
7159 o Bugfixes included in 0.1.0.14.
7161 o Bugfixes on 0.1.0.x:
7162 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
7163 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
7164 it would silently using ignore the 6668.
7167 Changes in version 0.1.0.14 - 2005-08-08
7168 o Bugfixes on 0.1.0.x:
7169 - Fix the other half of the bug with crypto handshakes
7171 - Fix an assert trigger if you send a 'signal term' via the
7172 controller when it's listening for 'event info' messages.
7175 Changes in version 0.1.1.4-alpha - 2005-08-04
7176 o Bugfixes included in 0.1.0.13.
7179 - Improve tor_gettimeofday() granularity on windows.
7180 - Make clients regenerate their keys when their IP address changes.
7181 - Implement some more GETINFO goodness: expose helper nodes, config
7182 options, getinfo keys.
7185 Changes in version 0.1.0.13 - 2005-08-04
7186 o Bugfixes on 0.1.0.x:
7187 - Fix a critical bug in the security of our crypto handshakes.
7188 - Fix a size_t underflow in smartlist_join_strings2() that made
7189 it do bad things when you hand it an empty smartlist.
7190 - Fix Windows installer to ship Tor license (thanks to Aphex for
7191 pointing out this oversight) and put a link to the doc directory
7193 - Explicitly set no-unaligned-access for sparc: it turns out the
7194 new gcc's let you compile broken code, but that doesn't make it
7198 Changes in version 0.1.1.3-alpha - 2005-07-23
7199 o Bugfixes on 0.1.1.2-alpha:
7200 - Fix a bug in handling the controller's "post descriptor"
7202 - Fix several bugs in handling the controller's "extend circuit"
7204 - Fix a bug in handling the controller's "stream status" event.
7205 - Fix an assert failure if we have a controller listening for
7206 circuit events and we go offline.
7207 - Re-allow hidden service descriptors to publish 0 intro points.
7208 - Fix a crash when generating your hidden service descriptor if
7209 you don't have enough intro points already.
7211 o New features on 0.1.1.2-alpha:
7212 - New controller function "getinfo accounting", to ask how
7213 many bytes we've used in this time period.
7214 - Experimental support for helper nodes: a lot of the risk from
7215 a small static adversary comes because users pick new random
7216 nodes every time they rebuild a circuit. Now users will try to
7217 stick to the same small set of entry nodes if they can. Not
7218 enabled by default yet.
7220 o Bugfixes on 0.1.0.12:
7221 - If you're an auth dir server, always publish your dirport,
7222 even if you haven't yet found yourself to be reachable.
7223 - Fix a size_t underflow in smartlist_join_strings2() that made
7224 it do bad things when you hand it an empty smartlist.
7227 Changes in version 0.1.0.12 - 2005-07-18
7228 o New directory servers:
7229 - tor26 has changed IP address.
7231 o Bugfixes on 0.1.0.x:
7232 - Fix a possible double-free in tor_gzip_uncompress().
7233 - When --disable-threads is set, do not search for or link against
7235 - Don't trigger an assert if an authoritative directory server
7236 claims its dirport is 0.
7237 - Fix bug with removing Tor as an NT service: some people were
7238 getting "The service did not return an error." Thanks to Matt
7242 Changes in version 0.1.1.2-alpha - 2005-07-15
7243 o New directory servers:
7244 - tor26 has changed IP address.
7246 o Bugfixes on 0.1.0.x, crashes/leaks:
7247 - Port the servers-not-obeying-their-exit-policies fix from
7249 - Fix an fd leak in start_daemon().
7250 - On Windows, you can't always reopen a port right after you've
7251 closed it. So change retry_listeners() to only close and re-open
7252 ports that have changed.
7253 - Fix a possible double-free in tor_gzip_uncompress().
7255 o Bugfixes on 0.1.0.x, usability:
7256 - When tor_socketpair() fails in Windows, give a reasonable
7257 Windows-style errno back.
7258 - Let people type "tor --install" as well as "tor -install" when
7260 want to make it an NT service.
7261 - NT service patch from Matt Edman to improve error messages.
7262 - When the controller asks for a config option with an abbreviated
7263 name, give the full name in our response.
7264 - Correct the man page entry on TrackHostExitsExpire.
7265 - Looks like we were never delivering deflated (i.e. compressed)
7266 running-routers lists, even when asked. Oops.
7267 - When --disable-threads is set, do not search for or link against
7270 o Bugfixes on 0.1.1.x:
7271 - Fix a seg fault with autodetecting which controller version is
7275 - New hidden service descriptor format: put a version in it, and
7276 let people specify introduction/rendezvous points that aren't
7277 in "the directory" (which is subjective anyway).
7278 - Allow the DEBUG controller event to work again. Mark certain log
7279 entries as "don't tell this to controllers", so we avoid cycles.
7282 Changes in version 0.1.0.11 - 2005-06-30
7283 o Bugfixes on 0.1.0.x:
7284 - Fix major security bug: servers were disregarding their
7285 exit policies if clients behaved unexpectedly.
7286 - Make OS X init script check for missing argument, so we don't
7287 confuse users who invoke it incorrectly.
7288 - Fix a seg fault in "tor --hash-password foo".
7289 - The MAPADDRESS control command was broken.
7292 Changes in version 0.1.1.1-alpha - 2005-06-29
7294 - Make OS X init script check for missing argument, so we don't
7295 confuse users who invoke it incorrectly.
7296 - Fix a seg fault in "tor --hash-password foo".
7297 - Fix a possible way to DoS dirservers.
7298 - When we complain that your exit policy implicitly allows local or
7299 private address spaces, name them explicitly so operators can
7301 - Make the log message less scary when all the dirservers are
7302 temporarily unreachable.
7303 - We were printing the number of idle dns workers incorrectly when
7307 - Revised controller protocol (version 1) that uses ascii rather
7308 than binary. Add supporting libraries in python and java so you
7309 can use the controller from your applications without caring how
7311 - Spiffy new support for crypto hardware accelerators. Can somebody
7315 Changes in version 0.0.9.10 - 2005-06-16
7316 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
7317 - Refuse relay cells that claim to have a length larger than the
7318 maximum allowed. This prevents a potential attack that could read
7319 arbitrary memory (e.g. keys) from an exit server's process
7323 Changes in version 0.1.0.10 - 2005-06-14
7324 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
7325 libevent before 1.1a.
7328 Changes in version 0.1.0.9-rc - 2005-06-09
7330 - Reset buf->highwater every time buf_shrink() is called, not just on
7331 a successful shrink. This was causing significant memory bloat.
7332 - Fix buffer overflow when checking hashed passwords.
7333 - Security fix: if seeding the RNG on Win32 fails, quit.
7334 - Allow seeding the RNG on Win32 even when you're not running as
7336 - Disable threading on Solaris too. Something is wonky with it,
7337 cpuworkers, and reentrant libs.
7338 - Reenable the part of the code that tries to flush as soon as an
7339 OR outbuf has a full TLS record available. Perhaps this will make
7340 OR outbufs not grow as huge except in rare cases, thus saving lots
7341 of CPU time plus memory.
7342 - Reject malformed .onion addresses rather then passing them on as
7343 normal web requests.
7344 - Adapt patch from Adam Langley: fix possible memory leak in
7345 tor_lookup_hostname().
7346 - Initialize libevent later in the startup process, so the logs are
7347 already established by the time we start logging libevent warns.
7348 - Use correct errno on win32 if libevent fails.
7349 - Check and warn about known-bad/slow libevent versions.
7350 - Pay more attention to the ClientOnly config option.
7351 - Have torctl.in/tor.sh.in check for location of su binary (needed
7353 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
7354 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
7355 HttpProxyAuthenticator
7356 - Stop warning about sigpipes in the logs. We're going to
7357 pretend that getting these occassionally is normal and fine.
7358 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
7360 installer screens; and don't put stuff into StartupItems unless
7361 the user asks you to.
7362 - Require servers that use the default dirservers to have public IP
7363 addresses. We have too many servers that are configured with private
7364 IPs and their admins never notice the log entries complaining that
7365 their descriptors are being rejected.
7366 - Add OSX uninstall instructions. An actual uninstall script will
7370 Changes in version 0.1.0.8-rc - 2005-05-23
7372 - It turns out that kqueue on OS X 10.3.9 was causing kernel
7373 panics. Disable kqueue on all OS X Tors.
7374 - Fix RPM: remove duplicate line accidentally added to the rpm
7376 - Disable threads on openbsd too, since its gethostaddr is not
7378 - Tolerate libevent 0.8 since it still works, even though it's
7380 - Enable building on Red Hat 9.0 again.
7381 - Allow the middle hop of the testing circuit to be running any
7382 version, now that most of them have the bugfix to let them connect
7383 to unknown servers. This will allow reachability testing to work
7384 even when 0.0.9.7-0.0.9.9 become obsolete.
7385 - Handle relay cells with rh.length too large. This prevents
7386 a potential attack that could read arbitrary memory (maybe even
7387 keys) from the exit server's process.
7388 - We screwed up the dirport reachability testing when we don't yet
7389 have a cached version of the directory. Hopefully now fixed.
7390 - Clean up router_load_single_router() (used by the controller),
7391 so it doesn't seg fault on error.
7392 - Fix a minor memory leak when somebody establishes an introduction
7393 point at your Tor server.
7394 - If a socks connection ends because read fails, don't warn that
7395 you're not sending a socks reply back.
7398 - Add HttpProxyAuthenticator config option too, that works like
7399 the HttpsProxyAuthenticator config option.
7400 - Encode hashed controller passwords in hex instead of base64,
7401 to make it easier to write controllers.
7404 Changes in version 0.1.0.7-rc - 2005-05-17
7406 - Fix a bug in the OS X package installer that prevented it from
7407 installing on Tiger.
7408 - Fix a script bug in the OS X package installer that made it
7409 complain during installation.
7410 - Find libevent even if it's hiding in /usr/local/ and your
7411 CFLAGS and LDFLAGS don't tell you to look there.
7412 - Be able to link with libevent as a shared library (the default
7413 after 1.0d), even if it's hiding in /usr/local/lib and even
7414 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
7415 assuming you're running gcc. Otherwise fail and give a useful
7417 - Fix a bug in the RPM packager: set home directory for _tor to
7418 something more reasonable when first installing.
7419 - Free a minor amount of memory that is still reachable on exit.
7422 Changes in version 0.1.0.6-rc - 2005-05-14
7424 - Implement --disable-threads configure option. Disable threads on
7425 netbsd by default, because it appears to have no reentrant resolver
7427 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
7428 release (1.1) detects and disables kqueue if it's broken.
7429 - Append default exit policy before checking for implicit internal
7430 addresses. Now we don't log a bunch of complaints on startup
7431 when using the default exit policy.
7432 - Some people were putting "Address " in their torrc, and they had
7433 a buggy resolver that resolved " " to 0.0.0.0. Oops.
7434 - If DataDir is ~/.tor, and that expands to /.tor, then default to
7435 LOCALSTATEDIR/tor instead.
7436 - Fix fragmented-message bug in TorControl.py.
7437 - Resolve a minor bug which would prevent unreachable dirports
7438 from getting suppressed in the published descriptor.
7439 - When the controller gave us a new descriptor, we weren't resolving
7440 it immediately, so Tor would think its address was 0.0.0.0 until
7441 we fetched a new directory.
7442 - Fix an uppercase/lowercase case error in suppressing a bogus
7443 libevent warning on some Linuxes.
7446 - Begin scrubbing sensitive strings from logs by default. Turn off
7447 the config option SafeLogging if you need to do debugging.
7448 - Switch to a new buffer management algorithm, which tries to avoid
7449 reallocing and copying quite as much. In first tests it looks like
7450 it uses *more* memory on average, but less cpu.
7451 - First cut at support for "create-fast" cells. Clients can use
7452 these when extending to their first hop, since the TLS already
7453 provides forward secrecy and authentication. Not enabled on
7455 - When dirservers refuse a router descriptor, we now log its
7456 contactinfo, platform, and the poster's IP address.
7457 - Call tor_free_all instead of connections_free_all after forking, to
7458 save memory on systems that need to fork.
7459 - Whine at you if you're a server and you don't set your contactinfo.
7460 - Implement --verify-config command-line option to check if your torrc
7461 is valid without actually launching Tor.
7462 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
7463 rather than just rejecting it.
7466 Changes in version 0.1.0.5-rc - 2005-04-27
7468 - Stop trying to print a null pointer if an OR conn fails because
7469 we didn't like its cert.
7471 - Switch our internal buffers implementation to use a ring buffer,
7472 to hopefully improve performance for fast servers a lot.
7473 - Add HttpsProxyAuthenticator support (basic auth only), based
7474 on patch from Adam Langley.
7475 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
7476 the fast servers that have been joining lately.
7477 - Give hidden service accesses extra time on the first attempt,
7478 since 60 seconds is often only barely enough. This might improve
7480 - Improve performance for dirservers: stop re-parsing the whole
7481 directory every time you regenerate it.
7482 - Add more debugging info to help us find the weird dns freebsd
7483 pthreads bug; cleaner debug messages to help track future issues.
7486 Changes in version 0.0.9.9 - 2005-04-23
7487 o Bugfixes on 0.0.9.x:
7488 - If unofficial Tor clients connect and send weird TLS certs, our
7489 Tor server triggers an assert. This release contains a minimal
7490 backport from the broader fix that we put into 0.1.0.4-rc.
7493 Changes in version 0.1.0.4-rc - 2005-04-23
7495 - If unofficial Tor clients connect and send weird TLS certs, our
7496 Tor server triggers an assert. Stop asserting, and start handling
7497 TLS errors better in other situations too.
7498 - When the controller asks us to tell it about all the debug-level
7499 logs, it turns out we were generating debug-level logs while
7500 telling it about them, which turns into a bad loop. Now keep
7501 track of whether you're sending a debug log to the controller,
7502 and don't log when you are.
7503 - Fix the "postdescriptor" feature of the controller interface: on
7504 non-complete success, only say "done" once.
7506 - Clients are now willing to load balance over up to 2mB, not 1mB,
7507 of advertised bandwidth capacity.
7508 - Add a NoPublish config option, so you can be a server (e.g. for
7509 testing running Tor servers in other Tor networks) without
7510 publishing your descriptor to the primary dirservers.
7513 Changes in version 0.1.0.3-rc - 2005-04-08
7514 o Improvements on 0.1.0.2-rc:
7515 - Client now retries when streams end early for 'hibernating' or
7516 'resource limit' reasons, rather than failing them.
7517 - More automated handling for dirserver operators:
7518 - Automatically approve nodes running 0.1.0.2-rc or later,
7519 now that the the reachability detection stuff is working.
7520 - Now we allow two unverified servers with the same nickname
7521 but different keys. But if a nickname is verified, only that
7522 nickname+key are allowed.
7523 - If you're an authdirserver connecting to an address:port,
7524 and it's not the OR you were expecting, forget about that
7525 descriptor. If he *was* the one you were expecting, then forget
7526 about all other descriptors for that address:port.
7527 - Allow servers to publish descriptors from 12 hours in the future.
7528 Corollary: only whine about clock skew from the dirserver if
7529 he's a trusted dirserver (since now even verified servers could
7530 have quite wrong clocks).
7531 - Adjust maximum skew and age for rendezvous descriptors: let skew
7532 be 48 hours rather than 90 minutes.
7533 - Efficiency improvements:
7534 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
7535 it much faster to look up a circuit for each relay cell.
7536 - Remove most calls to assert_all_pending_dns_resolves_ok(),
7537 since they're eating our cpu on exit nodes.
7538 - Stop wasting time doing a case insensitive comparison for every
7539 dns name every time we do any lookup. Canonicalize the names to
7540 lowercase and be done with it.
7541 - Start sending 'truncated' cells back rather than destroy cells,
7542 if the circuit closes in front of you. This means we won't have
7543 to abandon partially built circuits.
7544 - Only warn once per nickname from add_nickname_list_to_smartlist
7545 per failure, so an entrynode or exitnode choice that's down won't
7547 - Put a note in the torrc about abuse potential with the default
7549 - Revise control spec and implementation to allow all log messages to
7550 be sent to controller with their severities intact (suggested by
7551 Matt Edman). Update TorControl to handle new log event types.
7552 - Provide better explanation messages when controller's POSTDESCRIPTOR
7554 - Stop putting nodename in the Platform string in server descriptors.
7555 It doesn't actually help, and it is confusing/upsetting some people.
7557 o Bugfixes on 0.1.0.2-rc:
7558 - We were printing the host mask wrong in exit policies in server
7559 descriptors. This isn't a critical bug though, since we were still
7560 obeying the exit policy internally.
7561 - Fix Tor when compiled with libevent but without pthreads: move
7562 connection_unregister() from _connection_free() to
7564 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
7565 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
7566 when we look through the connection array, we'll find any of the
7567 cpu/dnsworkers. This is no good.
7569 o Bugfixes on 0.0.9.8:
7570 - Fix possible bug on threading platforms (e.g. win32) which was
7571 leaking a file descriptor whenever a cpuworker or dnsworker died.
7572 - When using preferred entry or exit nodes, ignore whether the
7573 circuit wants uptime or capacity. They asked for the nodes, they
7575 - chdir() to your datadirectory at the *end* of the daemonize process,
7576 not the beginning. This was a problem because the first time you
7577 run tor, if your datadir isn't there, and you have runasdaemon set
7578 to 1, it will try to chdir to it before it tries to create it. Oops.
7579 - Handle changed router status correctly when dirserver reloads
7580 fingerprint file. We used to be dropping all unverified descriptors
7581 right then. The bug was hidden because we would immediately
7582 fetch a directory from another dirserver, which would include the
7583 descriptors we just dropped.
7584 - When we're connecting to an OR and he's got a different nickname/key
7585 than we were expecting, only complain loudly if we're an OP or a
7586 dirserver. Complaining loudly to the OR admins just confuses them.
7587 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
7588 artificially capped at 500kB.
7591 Changes in version 0.0.9.8 - 2005-04-07
7592 o Bugfixes on 0.0.9.x:
7593 - We have a bug that I haven't found yet. Sometimes, very rarely,
7594 cpuworkers get stuck in the 'busy' state, even though the cpuworker
7595 thinks of itself as idle. This meant that no new circuits ever got
7596 established. Here's a workaround to kill any cpuworker that's been
7597 busy for more than 100 seconds.
7600 Changes in version 0.1.0.2-rc - 2005-04-01
7601 o Bugfixes on 0.1.0.1-rc:
7602 - Fixes on reachability detection:
7603 - Don't check for reachability while hibernating.
7604 - If ORPort is reachable but DirPort isn't, still publish the
7605 descriptor, but zero out DirPort until it's found reachable.
7606 - When building testing circs for ORPort testing, use only
7607 high-bandwidth nodes, so fewer circuits fail.
7608 - Complain about unreachable ORPort separately from unreachable
7609 DirPort, so the user knows what's going on.
7610 - Make sure we only conclude ORPort reachability if we didn't
7611 initiate the conn. Otherwise we could falsely conclude that
7612 we're reachable just because we connected to the guy earlier
7613 and he used that same pipe to extend to us.
7614 - Authdirservers shouldn't do ORPort reachability detection,
7615 since they're in clique mode, so it will be rare to find a
7616 server not already connected to them.
7617 - When building testing circuits, always pick middle hops running
7618 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
7619 bug. (This is a kludge; it will go away when 0.0.9.x becomes
7621 - When we decide we're reachable, actually publish our descriptor
7623 - Fix bug in redirectstream in the controller.
7624 - Fix the state descriptor strings so logs don't claim edge streams
7625 are in a different state than they actually are.
7626 - Use recent libevent features when possible (this only really affects
7627 win32 and osx right now, because the new libevent with these
7628 features hasn't been released yet). Add code to suppress spurious
7630 - Prevent possible segfault in connection_close_unattached_ap().
7631 - Fix newlines on torrc in win32.
7632 - Improve error msgs when tor-resolve fails.
7634 o Improvements on 0.0.9.x:
7635 - New experimental script tor/contrib/ExerciseServer.py (needs more
7636 work) that uses the controller interface to build circuits and
7637 fetch pages over them. This will help us bootstrap servers that
7638 have lots of capacity but haven't noticed it yet.
7639 - New experimental script tor/contrib/PathDemo.py (needs more work)
7640 that uses the controller interface to let you choose whole paths
7642 "<hostname>.<path,separated by dots>.<length of path>.path"
7643 - When we've connected to an OR and handshaked but didn't like
7644 the result, we were closing the conn without sending destroy
7645 cells back for pending circuits. Now send those destroys.
7648 Changes in version 0.0.9.7 - 2005-04-01
7649 o Bugfixes on 0.0.9.x:
7650 - Fix another race crash bug (thanks to Glenn Fink for reporting).
7651 - Compare identity to identity, not to nickname, when extending to
7652 a router not already in the directory. This was preventing us from
7653 extending to unknown routers. Oops.
7654 - Make sure to create OS X Tor user in <500 range, so we aren't
7655 creating actual system users.
7656 - Note where connection-that-hasn't-sent-end was marked, and fix
7657 a few really loud instances of this harmless bug (it's fixed more
7661 Changes in version 0.1.0.1-rc - 2005-03-28
7663 - Add reachability testing. Your Tor server will automatically try
7664 to see if its ORPort and DirPort are reachable from the outside,
7665 and it won't upload its descriptor until it decides they are.
7666 - Handle unavailable hidden services better. Handle slow or busy
7667 hidden services better.
7668 - Add support for CONNECTing through https proxies, with "HttpsProxy"
7670 - New exit policy: accept most low-numbered ports, rather than
7671 rejecting most low-numbered ports.
7672 - More Tor controller support (still experimental). See
7673 http://tor.eff.org/doc/control-spec.txt for all the new features,
7674 including signals to emulate unix signals from any platform;
7675 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
7676 closestream; closecircuit; etc.
7677 - Make nt services work and start on startup on win32 (based on
7678 patch by Matt Edman).
7679 - Add a new AddressMap config directive to rewrite incoming socks
7680 addresses. This lets you, for example, declare an implicit
7681 required exit node for certain sites.
7682 - Add a new TrackHostExits config directive to trigger addressmaps
7683 for certain incoming socks addresses -- for sites that break when
7684 your exit keeps changing (based on patch by Mike Perry).
7685 - Redo the client-side dns cache so it's just an addressmap too.
7686 - Notice when our IP changes, and reset stats/uptime/reachability.
7687 - When an application is using socks5, give him the whole variety of
7688 potential socks5 responses (connect refused, host unreachable, etc),
7689 rather than just "success" or "failure".
7690 - A more sane version numbering system. See
7691 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
7692 - New contributed script "exitlist": a simple python script to
7693 parse directories and find Tor nodes that exit to listed
7695 - New contributed script "privoxy-tor-toggle" to toggle whether
7696 Privoxy uses Tor. Seems to be configured for Debian by default.
7697 - Report HTTP reasons to client when getting a response from directory
7698 servers -- so you can actually know what went wrong.
7699 - New config option MaxAdvertisedBandwidth which lets you advertise
7700 a low bandwidthrate (to not attract as many circuits) while still
7701 allowing a higher bandwidthrate in reality.
7703 o Robustness/stability fixes:
7704 - Make Tor use Niels Provos's libevent instead of its current
7705 poll-but-sometimes-select mess. This will let us use faster async
7706 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
7708 - pthread support now too. This was forced because when we forked,
7709 we ended up wasting a lot of duplicate ram over time. Also switch
7710 to foo_r versions of some library calls to allow reentry and
7712 - Better handling for heterogeneous / unreliable nodes:
7713 - Annotate circuits w/ whether they aim to contain high uptime nodes
7714 and/or high capacity nodes. When building circuits, choose
7716 - This means that every single node in an intro rend circuit,
7717 not just the last one, will have a minimum uptime.
7718 - New config option LongLivedPorts to indicate application streams
7719 that will want high uptime circuits.
7720 - Servers reset uptime when a dir fetch entirely fails. This
7721 hopefully reflects stability of the server's network connectivity.
7722 - If somebody starts his tor server in Jan 2004 and then fixes his
7723 clock, don't make his published uptime be a year.
7724 - Reset published uptime when you wake up from hibernation.
7725 - Introduce a notion of 'internal' circs, which are chosen without
7726 regard to the exit policy of the last hop. Intro and rendezvous
7727 circs must be internal circs, to avoid leaking information. Resolve
7728 and connect streams can use internal circs if they want.
7729 - New circuit pooling algorithm: make sure to have enough circs around
7730 to satisfy any predicted ports, and also make sure to have 2 internal
7731 circs around if we've required internal circs lately (and with high
7732 uptime if we've seen that lately too).
7733 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
7734 which describes how often we retry making new circuits if current
7735 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
7736 how long we're willing to make use of an already-dirty circuit.
7737 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
7738 circ as necessary, if there are any completed ones lying around
7739 when we try to launch one.
7740 - Make hidden services try to establish a rendezvous for 30 seconds,
7741 rather than for n (where n=3) attempts to build a circuit.
7742 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
7743 "ShutdownWaitLength".
7744 - Try to be more zealous about calling connection_edge_end when
7745 things go bad with edge conns in connection.c.
7746 - Revise tor-spec to add more/better stream end reasons.
7747 - Revise all calls to connection_edge_end to avoid sending "misc",
7748 and to take errno into account where possible.
7751 - Fix a race condition that can trigger an assert, when we have a
7752 pending create cell and an OR connection fails right then.
7753 - Fix several double-mark-for-close bugs, e.g. where we were finding
7754 a conn for a cell even if that conn is already marked for close.
7755 - Make sequence of log messages when starting on win32 with no config
7756 file more reasonable.
7757 - When choosing an exit node for a new non-internal circ, don't take
7758 into account whether it'll be useful for any pending x.onion
7759 addresses -- it won't.
7760 - Turn addr_policy_compare from a tristate to a quadstate; this should
7761 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
7762 for google.com" problem.
7763 - Make "platform" string in descriptor more accurate for Win32 servers,
7764 so it's not just "unknown platform".
7765 - Fix an edge case in parsing config options (thanks weasel).
7766 If they say "--" on the commandline, it's not an option.
7767 - Reject odd-looking addresses at the client (e.g. addresses that
7768 contain a colon), rather than having the server drop them because
7770 - tor-resolve requests were ignoring .exit if there was a working circuit
7771 they could use instead.
7772 - REUSEADDR on normal platforms means you can rebind to the port
7773 right after somebody else has let it go. But REUSEADDR on win32
7774 means to let you bind to the port _even when somebody else
7775 already has it bound_! So, don't do that on Win32.
7776 - Change version parsing logic: a version is "obsolete" if it is not
7777 recommended and (1) there is a newer recommended version in the
7778 same series, or (2) there are no recommended versions in the same
7779 series, but there are some recommended versions in a newer series.
7780 A version is "new" if it is newer than any recommended version in
7782 - Stop most cases of hanging up on a socks connection without sending
7786 - Require BandwidthRate to be at least 20kB/s for servers.
7787 - When a dirserver causes you to give a warn, mention which dirserver
7789 - New config option DirAllowPrivateAddresses for authdirservers.
7790 Now by default they refuse router descriptors that have non-IP or
7791 private-IP addresses.
7792 - Stop publishing socksport in the directory, since it's not
7793 actually meant to be public. For compatibility, publish a 0 there
7795 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
7796 smart" value, that is low for servers and high for clients.
7797 - If our clock jumps forward by 100 seconds or more, assume something
7798 has gone wrong with our network and abandon all not-yet-used circs.
7799 - Warn when exit policy implicitly allows local addresses.
7800 - If we get an incredibly skewed timestamp from a dirserver mirror
7801 that isn't a verified OR, don't warn -- it's probably him that's
7803 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
7804 cookies to disk and doesn't log each web request to disk. (Thanks
7805 to Brett Carrington for pointing this out.)
7806 - When a client asks us for a dir mirror and we don't have one,
7807 launch an attempt to get a fresh one.
7808 - If we're hibernating and we get a SIGINT, exit immediately.
7809 - Add --with-dmalloc ./configure option, to track memory leaks.
7810 - And try to free all memory on closing, so we can detect what
7812 - Cache local dns resolves correctly even when they're .exit
7814 - Give a better warning when some other server advertises an
7815 ORPort that is actually an apache running ssl.
7816 - Add "opt hibernating 1" to server descriptor to make it clearer
7817 whether the server is hibernating.
7820 Changes in version 0.0.9.6 - 2005-03-24
7821 o Bugfixes on 0.0.9.x (crashes and asserts):
7822 - Add new end stream reasons to maintainance branch. Fix bug where
7823 reason (8) could trigger an assert. Prevent bug from recurring.
7824 - Apparently win32 stat wants paths to not end with a slash.
7825 - Fix assert triggers in assert_cpath_layer_ok(), where we were
7826 blowing away the circuit that conn->cpath_layer points to, then
7827 checking to see if the circ is well-formed. Backport check to make
7828 sure we dont use the cpath on a closed connection.
7829 - Prevent circuit_resume_edge_reading_helper() from trying to package
7830 inbufs for marked-for-close streams.
7831 - Don't crash on hup if your options->address has become unresolvable.
7832 - Some systems (like OS X) sometimes accept() a connection and tell
7833 you the remote host is 0.0.0.0:0. If this happens, due to some
7834 other mis-features, we get confused; so refuse the conn for now.
7836 o Bugfixes on 0.0.9.x (other):
7837 - Fix harmless but scary "Unrecognized content encoding" warn message.
7838 - Add new stream error reason: TORPROTOCOL reason means "you are not
7839 speaking a version of Tor I understand; say bye-bye to your stream."
7840 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
7841 into the future, now that we are more tolerant of skew. This
7842 resolves a bug where a Tor server would refuse to cache a directory
7843 because all the directories it gets are too far in the future;
7844 yet the Tor server never logs any complaints about clock skew.
7845 - Mac packaging magic: make man pages useable, and do not overwrite
7846 existing torrc files.
7847 - Make OS X log happily to /var/log/tor/tor.log
7850 Changes in version 0.0.9.5 - 2005-02-22
7851 o Bugfixes on 0.0.9.x:
7852 - Fix an assert race at exit nodes when resolve requests fail.
7853 - Stop picking unverified dir mirrors--it only leads to misery.
7854 - Patch from Matt Edman to make NT services work better. Service
7855 support is still not compiled into the executable by default.
7856 - Patch from Dmitri Bely so the Tor service runs better under
7857 the win32 SYSTEM account.
7858 - Make tor-resolve actually work (?) on Win32.
7859 - Fix a sign bug when getrlimit claims to have 4+ billion
7860 file descriptors available.
7861 - Stop refusing to start when bandwidthburst == bandwidthrate.
7862 - When create cells have been on the onion queue more than five
7863 seconds, just send back a destroy and take them off the list.
7866 Changes in version 0.0.9.4 - 2005-02-03
7867 o Bugfixes on 0.0.9:
7868 - Fix an assert bug that took down most of our servers: when
7869 a server claims to have 1 GB of bandwidthburst, don't
7871 - Don't crash as badly if we have spawned the max allowed number
7872 of dnsworkers, or we're out of file descriptors.
7873 - Block more file-sharing ports in the default exit policy.
7874 - MaxConn is now automatically set to the hard limit of max
7875 file descriptors we're allowed (ulimit -n), minus a few for
7877 - Give a clearer message when servers need to raise their
7878 ulimit -n when they start running out of file descriptors.
7879 - SGI Compatibility patches from Jan Schaumann.
7880 - Tolerate a corrupt cached directory better.
7881 - When a dirserver hasn't approved your server, list which one.
7882 - Go into soft hibernation after 95% of the bandwidth is used,
7883 not 99%. This is especially important for daily hibernators who
7884 have a small accounting max. Hopefully it will result in fewer
7885 cut connections when the hard hibernation starts.
7886 - Load-balance better when using servers that claim more than
7887 800kB/s of capacity.
7888 - Make NT services work (experimental, only used if compiled in).
7891 Changes in version 0.0.9.3 - 2005-01-21
7892 o Bugfixes on 0.0.9:
7893 - Backport the cpu use fixes from main branch, so busy servers won't
7894 need as much processor time.
7895 - Work better when we go offline and then come back, or when we
7896 run Tor at boot before the network is up. We do this by
7897 optimistically trying to fetch a new directory whenever an
7898 application request comes in and we think we're offline -- the
7899 human is hopefully a good measure of when the network is back.
7900 - Backport some minimal hidserv bugfixes: keep rend circuits open as
7901 long as you keep using them; actually publish hidserv descriptors
7902 shortly after they change, rather than waiting 20-40 minutes.
7903 - Enable Mac startup script by default.
7904 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
7905 - When you update AllowUnverifiedNodes or FirewallPorts via the
7906 controller's setconf feature, we were always appending, never
7908 - When you update HiddenServiceDir via setconf, it was screwing up
7909 the order of reading the lines, making it fail.
7910 - Do not rewrite a cached directory back to the cache; otherwise we
7911 will think it is recent and not fetch a newer one on startup.
7912 - Workaround for webservers that lie about Content-Encoding: Tor
7913 now tries to autodetect compressed directories and compression
7914 itself. This lets us Proxypass dir fetches through apache.
7917 Changes in version 0.0.9.2 - 2005-01-04
7918 o Bugfixes on 0.0.9 (crashes and asserts):
7919 - Fix an assert on startup when the disk is full and you're logging
7921 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
7922 style address, then we'd crash.
7923 - Fix an assert trigger when the running-routers string we get from
7924 a dirserver is broken.
7925 - Make worker threads start and run on win32. Now win32 servers
7927 - Bandaid (not actually fix, but now it doesn't crash) an assert
7928 where the dns worker dies mysteriously and the main Tor process
7929 doesn't remember anything about the address it was resolving.
7931 o Bugfixes on 0.0.9 (Win32):
7932 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
7933 name out of the warning/assert messages.
7934 - Fix a superficial "unhandled error on read" bug on win32.
7935 - The win32 installer no longer requires a click-through for our
7936 license, since our Free Software license grants rights but does not
7938 - Win32: When connecting to a dirserver fails, try another one
7939 immediately. (This was already working for non-win32 Tors.)
7940 - Stop trying to parse $HOME on win32 when hunting for default
7942 - Make tor-resolve.c work on win32 by calling network_init().
7944 o Bugfixes on 0.0.9 (other):
7945 - Make 0.0.9.x build on Solaris again.
7946 - Due to a fencepost error, we were blowing away the \n when reporting
7947 confvalue items in the controller. So asking for multiple config
7948 values at once couldn't work.
7949 - When listing circuits that are pending on an opening OR connection,
7950 if we're an OR we were listing circuits that *end* at us as
7951 being pending on every listener, dns/cpu worker, etc. Stop that.
7952 - Dirservers were failing to create 'running-routers' or 'directory'
7953 strings if we had more than some threshold of routers. Fix them so
7954 they can handle any number of routers.
7955 - Fix a superficial "Duplicate mark for close" bug.
7956 - Stop checking for clock skew for OR connections, even for servers.
7957 - Fix a fencepost error that was chopping off the last letter of any
7958 nickname that is the maximum allowed nickname length.
7959 - Update URLs in log messages so they point to the new website.
7960 - Fix a potential problem in mangling server private keys while
7961 writing to disk (not triggered yet, as far as we know).
7962 - Include the licenses for other free software we include in Tor,
7963 now that we're shipping binary distributions more regularly.
7966 Changes in version 0.0.9.1 - 2004-12-15
7967 o Bugfixes on 0.0.9:
7968 - Make hibernation actually work.
7969 - Make HashedControlPassword config option work.
7970 - When we're reporting event circuit status to a controller,
7971 don't use the stream status code.
7974 Changes in version 0.0.9 - 2004-12-12
7976 - Clean up manpage and torrc.sample file.
7977 - Clean up severities and text of log warnings.
7979 - Make servers trigger an assert when they enter hibernation.
7982 Changes in version 0.0.9rc7 - 2004-12-08
7983 o Bugfixes on 0.0.9rc:
7984 - Fix a stack-trashing crash when an exit node begins hibernating.
7985 - Avoid looking at unallocated memory while considering which
7986 ports we need to build circuits to cover.
7987 - Stop a sigpipe: when an 'end' cell races with eof from the app,
7988 we shouldn't hold-open-until-flush if the eof arrived first.
7989 - Fix a bug with init_cookie_authentication() in the controller.
7990 - When recommending new-format log lines, if the upper bound is
7991 LOG_ERR, leave it implicit.
7993 o Bugfixes on 0.0.8.1:
7994 - Fix a whole slew of memory leaks.
7995 - Fix isspace() and friends so they still make Solaris happy
7996 but also so they don't trigger asserts on win32.
7997 - Fix parse_iso_time on platforms without strptime (eg win32).
7998 - win32: tolerate extra "readable" events better.
7999 - win32: when being multithreaded, leave parent fdarray open.
8000 - Make unit tests work on win32.
8003 Changes in version 0.0.9rc6 - 2004-12-06
8004 o Bugfixes on 0.0.9pre:
8005 - Clean up some more integer underflow opportunities (not exploitable
8007 - While hibernating, hup should not regrow our listeners.
8008 - Send an end to the streams we close when we hibernate, rather
8009 than just chopping them off.
8010 - React to eof immediately on non-open edge connections.
8012 o Bugfixes on 0.0.8.1:
8013 - Calculate timeout for waiting for a connected cell from the time
8014 we sent the begin cell, not from the time the stream started. If
8015 it took a long time to establish the circuit, we would time out
8016 right after sending the begin cell.
8017 - Fix router_compare_addr_to_addr_policy: it was not treating a port
8018 of * as always matching, so we were picking reject *:* nodes as
8019 exit nodes too. Oops.
8022 - New circuit building strategy: keep a list of ports that we've
8023 used in the past 6 hours, and always try to have 2 circuits open
8024 or on the way that will handle each such port. Seed us with port
8025 80 so web users won't complain that Tor is "slow to start up".
8026 - Make kill -USR1 dump more useful stats about circuits.
8027 - When warning about retrying or giving up, print the address, so
8028 the user knows which one it's talking about.
8029 - If you haven't used a clean circuit in an hour, throw it away,
8030 just to be on the safe side. (This means after 6 hours a totally
8031 unused Tor client will have no circuits open.)
8034 Changes in version 0.0.9rc5 - 2004-12-01
8035 o Bugfixes on 0.0.8.1:
8036 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
8037 - Let resolve conns retry/expire also, rather than sticking around
8039 - If we are using select, make sure we stay within FD_SETSIZE.
8041 o Bugfixes on 0.0.9pre:
8042 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
8043 but doesn't seem to be currently; thanks to Ilja van Sprundel for
8045 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
8046 instead. Impose minima and maxima for all *Period options; impose
8047 even tighter maxima for fetching if we are a caching dirserver.
8048 Clip rather than rejecting.
8049 - Fetch cached running-routers from servers that serve it (that is,
8050 authdirservers and servers running 0.0.9rc5-cvs or later.)
8053 - Accept *:706 (silc) in default exit policy.
8054 - Implement new versioning format for post 0.1.
8055 - Support "foo.nickname.exit" addresses, to let Alice request the
8056 address "foo" as viewed by exit node "nickname". Based on a patch
8058 - Make tor --version --version dump the cvs Id of every file.
8061 Changes in version 0.0.9rc4 - 2004-11-28
8062 o Bugfixes on 0.0.8.1:
8063 - Make windows sockets actually non-blocking (oops), and handle
8064 win32 socket errors better.
8066 o Bugfixes on 0.0.9rc1:
8067 - Actually catch the -USR2 signal.
8070 Changes in version 0.0.9rc3 - 2004-11-25
8071 o Bugfixes on 0.0.8.1:
8072 - Flush the log file descriptor after we print "Tor opening log file",
8073 so we don't see those messages days later.
8075 o Bugfixes on 0.0.9rc1:
8076 - Make tor-resolve work again.
8077 - Avoid infinite loop in tor-resolve if tor hangs up on it.
8078 - Fix an assert trigger for clients/servers handling resolves.
8081 Changes in version 0.0.9rc2 - 2004-11-24
8082 o Bugfixes on 0.0.9rc1:
8083 - I broke socks5 support while fixing the eof bug.
8084 - Allow unitless bandwidths and intervals; they default to bytes
8086 - New servers don't start out hibernating; they are active until
8087 they run out of bytes, so they have a better estimate of how
8088 long it takes, and so their operators can know they're working.
8091 Changes in version 0.0.9rc1 - 2004-11-23
8092 o Bugfixes on 0.0.8.1:
8093 - Finally fix a bug that's been plaguing us for a year:
8094 With high load, circuit package window was reaching 0. Whenever
8095 we got a circuit-level sendme, we were reading a lot on each
8096 socket, but only writing out a bit. So we would eventually reach
8097 eof. This would be noticed and acted on even when there were still
8098 bytes sitting in the inbuf.
8099 - When poll() is interrupted, we shouldn't believe the revents values.
8101 o Bugfixes on 0.0.9pre6:
8102 - Fix hibernate bug that caused pre6 to be broken.
8103 - Don't keep rephist info for routers that haven't had activity for
8104 24 hours. (This matters now that clients have keys, since we track
8106 - Never call close_temp_logs while validating log options.
8107 - Fix backslash-escaping on tor.sh.in and torctl.in.
8110 - Implement weekly/monthly/daily accounting: now you specify your
8111 hibernation properties by
8112 AccountingMax N bytes|KB|MB|GB|TB
8113 AccountingStart day|week|month [day] HH:MM
8114 Defaults to "month 1 0:00".
8115 - Let bandwidth and interval config options be specified as 5 bytes,
8116 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
8117 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
8118 get back to normal.)
8119 - If your requested entry or exit node has advertised bandwidth 0,
8121 - Be more greedy about filling up relay cells -- we try reading again
8122 once we've processed the stuff we read, in case enough has arrived
8123 to fill the last cell completely.
8124 - Apply NT service patch from Osamu Fujino. Still needs more work.
8127 Changes in version 0.0.9pre6 - 2004-11-15
8128 o Bugfixes on 0.0.8.1:
8129 - Fix assert failure on malformed socks4a requests.
8130 - Use identity comparison, not nickname comparison, to choose which
8131 half of circuit-ID-space each side gets to use. This is needed
8132 because sometimes we think of a router as a nickname, and sometimes
8133 as a hex ID, and we can't predict what the other side will do.
8134 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
8135 write() call will fail and we handle it there.
8136 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
8137 and smartlist_len, which are two major profiling offenders.
8139 o Bugfixes on 0.0.9pre5:
8140 - Fix a bug in read_all that was corrupting config files on windows.
8141 - When we're raising the max number of open file descriptors to
8142 'unlimited', don't log that we just raised it to '-1'.
8143 - Include event code with events, as required by control-spec.txt.
8144 - Don't give a fingerprint when clients do --list-fingerprint:
8145 it's misleading, because it will never be the same again.
8146 - Stop using strlcpy in tor_strndup, since it was slowing us
8148 - Remove warn on startup about missing cached-directory file.
8149 - Make kill -USR1 work again.
8150 - Hibernate if we start tor during the "wait for wakeup-time" phase
8151 of an accounting interval. Log our hibernation plans better.
8152 - Authoritative dirservers now also cache their directory, so they
8153 have it on start-up.
8156 - Fetch running-routers; cache running-routers; compress
8157 running-routers; serve compressed running-routers.z
8158 - Add NSI installer script contributed by J Doe.
8159 - Commit VC6 and VC7 workspace/project files.
8160 - Commit a tor.spec for making RPM files, with help from jbash.
8161 - Add contrib/torctl.in contributed by Glenn Fink.
8162 - Implement the control-spec's SAVECONF command, to write your
8163 configuration to torrc.
8164 - Get cookie authentication for the controller closer to working.
8165 - Include control-spec.txt in the tarball.
8166 - When set_conf changes our server descriptor, upload a new copy.
8167 But don't upload it too often if there are frequent changes.
8168 - Document authentication config in man page, and document signals
8170 - Clean up confusing parts of man page and torrc.sample.
8171 - Make expand_filename handle ~ and ~username.
8172 - Use autoconf to enable largefile support where necessary. Use
8173 ftello where available, since ftell can fail at 2GB.
8174 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
8175 log more informatively.
8176 - Give a slightly more useful output for "tor -h".
8177 - Refuse application socks connections to port 0.
8178 - Check clock skew for verified servers, but allow unverified
8179 servers and clients to have any clock skew.
8180 - Break DirFetchPostPeriod into:
8181 - DirFetchPeriod for fetching full directory,
8182 - StatusFetchPeriod for fetching running-routers,
8183 - DirPostPeriod for posting server descriptor,
8184 - RendPostPeriod for posting hidden service descriptors.
8185 - Make sure the hidden service descriptors are at a random offset
8186 from each other, to hinder linkability.
8189 Changes in version 0.0.9pre5 - 2004-11-09
8190 o Bugfixes on 0.0.9pre4:
8191 - Fix a seg fault in unit tests (doesn't affect main program).
8192 - Fix an assert bug where a hidden service provider would fail if
8193 the first hop of his rendezvous circuit was down.
8194 - Hidden service operators now correctly handle version 1 style
8195 INTRODUCE1 cells (nobody generates them still, so not a critical
8197 - If do_hup fails, actually notice.
8198 - Handle more errnos from accept() without closing the listener.
8199 Some OpenBSD machines were closing their listeners because
8200 they ran out of file descriptors.
8201 - Send resolve cells to exit routers that are running a new
8202 enough version of the resolve code to work right.
8203 - Better handling of winsock includes on non-MSV win32 compilers.
8204 - Some people had wrapped their tor client/server in a script
8205 that would restart it whenever it died. This did not play well
8206 with our "shut down if your version is obsolete" code. Now people
8207 don't fetch a new directory if their local cached version is
8209 - Make our autogen.sh work on ksh as well as bash.
8212 - Hibernation: New config option "AccountingMaxKB" lets you
8213 set how many KBytes per month you want to allow your server to
8214 consume. Rather than spreading those bytes out evenly over the
8215 month, we instead hibernate for some of the month and pop up
8216 at a deterministic time, work until the bytes are consumed, then
8217 hibernate again. Config option "MonthlyAccountingStart" lets you
8218 specify which day of the month your billing cycle starts on.
8219 - Control interface: a separate program can now talk to your
8220 client/server over a socket, and get/set config options, receive
8221 notifications of circuits and streams starting/finishing/dying,
8222 bandwidth used, etc. The next step is to get some GUIs working.
8223 Let us know if you want to help out. See doc/control-spec.txt .
8224 - Ship a contrib/tor-control.py as an example script to interact
8225 with the control port.
8226 - "tor --hash-password zzyxz" will output a salted password for
8227 use in authenticating to the control interface.
8228 - New log format in config:
8229 "Log minsev[-maxsev] stdout|stderr|syslog" or
8230 "Log minsev[-maxsev] file /var/foo"
8233 - DirPolicy config option, to let people reject incoming addresses
8234 from their dirserver.
8235 - "tor --list-fingerprint" will list your identity key fingerprint
8237 - Add "pass" target for RedirectExit, to make it easier to break
8238 out of a sequence of RedirectExit rules.
8239 - Clients now generate a TLS cert too, in preparation for having
8240 them act more like real nodes.
8241 - Ship src/win32/ in the tarball, so people can use it to build.
8242 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
8244 - New "router-status" line in directory, to better bind each verified
8245 nickname to its identity key.
8246 - Deprecate unofficial config option abbreviations, and abbreviations
8247 not on the command line.
8248 - Add a pure-C tor-resolve implementation.
8249 - Use getrlimit and friends to ensure we can reach MaxConn (currently
8250 1024) file descriptors.
8252 o Code security improvements, inspired by Ilja:
8253 - Replace sprintf with snprintf. (I think they were all safe, but
8255 - Replace strcpy/strncpy with strlcpy in more places.
8256 - Avoid strcat; use snprintf or strlcat instead.
8257 - snprintf wrapper with consistent (though not C99) overflow behavior.
8260 Changes in version 0.0.9pre4 - 2004-10-17
8261 o Bugfixes on 0.0.9pre3:
8262 - If the server doesn't specify an exit policy, use the real default
8263 exit policy, not reject *:*.
8264 - Ignore fascistfirewall when uploading/downloading hidden service
8265 descriptors, since we go through Tor for those; and when using
8266 an HttpProxy, since we assume it can reach them all.
8267 - When looking for an authoritative dirserver, use only the ones
8268 configured at boot. Don't bother looking in the directory.
8269 - The rest of the fix for get_default_conf_file() on older win32.
8270 - Make 'Routerfile' config option obsolete.
8273 - New 'MyFamily nick1,...' config option for a server to
8274 specify other servers that shouldn't be used in the same circuit
8275 with it. Only believed if nick1 also specifies us.
8276 - New 'NodeFamily nick1,nick2,...' config option for a client to
8277 specify nodes that it doesn't want to use in the same circuit.
8278 - New 'Redirectexit pattern address:port' config option for a
8279 server to redirect exit connections, e.g. to a local squid.
8282 Changes in version 0.0.9pre3 - 2004-10-13
8283 o Bugfixes on 0.0.8.1:
8284 - Better torrc example lines for dirbindaddress and orbindaddress.
8285 - Improved bounds checking on parsed ints (e.g. config options and
8286 the ones we find in directories.)
8287 - Better handling of size_t vs int, so we're more robust on 64
8289 - Fix the rest of the bug where a newly started OR would appear
8290 as unverified even after we've added his fingerprint and hupped
8292 - Fix a bug from 0.0.7: when read() failed on a stream, we would
8293 close it without sending back an end. So 'connection refused'
8294 would simply be ignored and the user would get no response.
8296 o Bugfixes on 0.0.9pre2:
8297 - Serving the cached-on-disk directory to people is bad. We now
8298 provide no directory until we've fetched a fresh one.
8299 - Workaround for bug on windows where cached-directories get crlf
8301 - Make get_default_conf_file() work on older windows too.
8302 - If we write a *:* exit policy line in the descriptor, don't write
8303 any more exit policy lines.
8306 - Use only 0.0.9pre1 and later servers for resolve cells.
8307 - Make the dirservers file obsolete.
8308 - Include a dir-signing-key token in directories to tell the
8309 parsing entity which key is being used to sign.
8310 - Remove the built-in bulky default dirservers string.
8311 - New config option "Dirserver %s:%d [fingerprint]", which can be
8312 repeated as many times as needed. If no dirservers specified,
8313 default to moria1,moria2,tor26.
8314 - Make moria2 advertise a dirport of 80, so people behind firewalls
8315 will be able to get a directory.
8316 - Http proxy support
8317 - Dirservers translate requests for http://%s:%d/x to /x
8318 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
8319 be routed through this host.
8320 - Clients ask for /tor/x rather than /x for new enough dirservers.
8321 This way we can one day coexist peacefully with apache.
8322 - Clients specify a "Host: %s%d" http header, to be compatible
8323 with more proxies, and so running squid on an exit node can work.
8326 Changes in version 0.0.8.1 - 2004-10-13
8328 - Fix a seg fault that can be triggered remotely for Tor
8329 clients/servers with an open dirport.
8330 - Fix a rare assert trigger, where routerinfos for entries in
8331 our cpath would expire while we're building the path.
8332 - Fix a bug in OutboundBindAddress so it (hopefully) works.
8333 - Fix a rare seg fault for people running hidden services on
8334 intermittent connections.
8335 - Fix a bug in parsing opt keywords with objects.
8336 - Fix a stale pointer assert bug when a stream detaches and
8338 - Fix a string format vulnerability (probably not exploitable)
8339 in reporting stats locally.
8340 - Fix an assert trigger: sometimes launching circuits can fail
8341 immediately, e.g. because too many circuits have failed recently.
8342 - Fix a compile warning on 64 bit platforms.
8345 Changes in version 0.0.9pre2 - 2004-10-03
8347 - Make fetching a cached directory work for 64-bit platforms too.
8348 - Make zlib.h a required header, not an optional header.
8351 Changes in version 0.0.9pre1 - 2004-10-01
8353 - Stop using separate defaults for no-config-file and
8354 empty-config-file. Now you have to explicitly turn off SocksPort,
8355 if you don't want it open.
8356 - Fix a bug in OutboundBindAddress so it (hopefully) works.
8357 - Improve man page to mention more of the 0.0.8 features.
8358 - Fix a rare seg fault for people running hidden services on
8359 intermittent connections.
8360 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
8362 - Fix more dns related bugs: send back resolve_failed and end cells
8363 more reliably when the resolve fails, rather than closing the
8364 circuit and then trying to send the cell. Also attach dummy resolve
8365 connections to a circuit *before* calling dns_resolve(), to fix
8366 a bug where cached answers would never be sent in RESOLVED cells.
8367 - When we run out of disk space, or other log writing error, don't
8368 crash. Just stop logging to that log and continue.
8369 - We were starting to daemonize before we opened our logs, so if
8370 there were any problems opening logs, we would complain to stderr,
8371 which wouldn't work, and then mysteriously exit.
8372 - Fix a rare bug where sometimes a verified OR would connect to us
8373 before he'd uploaded his descriptor, which would cause us to
8374 assign conn->nickname as though he's unverified. Now we look through
8375 the fingerprint list to see if he's there.
8376 - Fix a rare assert trigger, where routerinfos for entries in
8377 our cpath would expire while we're building the path.
8380 - Clients can ask dirservers for /dir.z to get a compressed version
8381 of the directory. Only works for servers running 0.0.9, of course.
8382 - Make clients cache directories and use them to seed their router
8383 lists at startup. This means clients have a datadir again.
8384 - Configuration infrastructure support for warning on obsolete
8386 - Respond to content-encoding headers by trying to uncompress as
8388 - Reply with a deflated directory when a client asks for "dir.z".
8389 We could use allow-encodings instead, but allow-encodings isn't
8390 specified in HTTP 1.0.
8391 - Raise the max dns workers from 50 to 100.
8392 - Discourage people from setting their dirfetchpostperiod more often
8393 than once per minute.
8394 - Protect dirservers from overzealous descriptor uploading -- wait
8395 10 seconds after directory gets dirty, before regenerating.
8398 Changes in version 0.0.8 - 2004-08-25
8399 o Port it to SunOS 5.9 / Athena
8402 Changes in version 0.0.8rc2 - 2004-08-20
8403 o Make it compile on cygwin again.
8404 o When picking unverified routers, skip those with low uptime and/or
8405 low bandwidth, depending on what properties you care about.
8408 Changes in version 0.0.8rc1 - 2004-08-18
8409 o Changes from 0.0.7.3:
8411 - Fix assert triggers: if the other side returns an address 0.0.0.0,
8412 don't put it into the client dns cache.
8413 - If a begin failed due to exit policy, but we believe the IP address
8414 should have been allowed, switch that router to exitpolicy reject *:*
8415 until we get our next directory.
8417 - Clients choose nodes proportional to advertised bandwidth.
8418 - Avoid using nodes with low uptime as introduction points.
8419 - Handle servers with dynamic IP addresses: don't replace
8420 options->Address with the resolved one at startup, and
8421 detect our address right before we make a routerinfo each time.
8422 - 'FascistFirewall' option to pick dirservers and ORs on specific
8423 ports; plus 'FirewallPorts' config option to tell FascistFirewall
8424 which ports are open. (Defaults to 80,443)
8425 - Be more aggressive about trying to make circuits when the network
8426 has changed (e.g. when you unsuspend your laptop).
8427 - Check for time skew on http headers; report date in response to
8429 - If the entrynode config line has only one node, don't pick it as
8431 - Add strict{entry|exit}nodes config options. If set to 1, then
8432 we refuse to build circuits that don't include the specified entry
8434 - OutboundBindAddress config option, to bind to a specific
8435 IP address for outgoing connect()s.
8436 - End truncated log entries (e.g. directories) with "[truncated]".
8438 o Patches to 0.0.8preX:
8440 - Patches to compile and run on win32 again (maybe)?
8441 - Fix crash when looking for ~/.torrc with no $HOME set.
8442 - Fix a race bug in the unit tests.
8443 - Handle verified/unverified name collisions better when new
8444 routerinfo's arrive in a directory.
8445 - Sometimes routers were getting entered into the stats before
8446 we'd assigned their identity_digest. Oops.
8447 - Only pick and establish intro points after we've gotten a
8450 - AllowUnverifiedNodes config option to let circuits choose no-name
8451 routers in entry,middle,exit,introduction,rendezvous positions.
8452 Allow middle and rendezvous positions by default.
8453 - Add a man page for tor-resolve.
8456 Changes in version 0.0.7.3 - 2004-08-12
8457 o Stop dnsworkers from triggering an assert failure when you
8458 ask them to resolve the host "".
8461 Changes in version 0.0.8pre3 - 2004-08-09
8462 o Changes from 0.0.7.2:
8463 - Allow multiple ORs with same nickname in routerlist -- now when
8464 people give us one identity key for a nickname, then later
8465 another, we don't constantly complain until the first expires.
8466 - Remember used bandwidth (both in and out), and publish 15-minute
8467 snapshots for the past day into our descriptor.
8468 - You can now fetch $DIRURL/running-routers to get just the
8469 running-routers line, not the whole descriptor list. (But
8470 clients don't use this yet.)
8471 - When people mistakenly use Tor as an http proxy, point them
8472 at the tor-doc.html rather than the INSTALL.
8473 - Remove our mostly unused -- and broken -- hex_encode()
8474 function. Use base16_encode() instead. (Thanks to Timo Lindfors
8475 for pointing out this bug.)
8476 - Rotate onion keys every 12 hours, not every 2 hours, so we have
8477 fewer problems with people using the wrong key.
8478 - Change the default exit policy to reject the default edonkey,
8479 kazaa, gnutella ports.
8480 - Add replace_file() to util.[ch] to handle win32's rename().
8482 o Changes from 0.0.8preX:
8483 - Fix two bugs in saving onion keys to disk when rotating, so
8484 hopefully we'll get fewer people using old onion keys.
8485 - Fix an assert error that was making SocksPolicy not work.
8486 - Be willing to expire routers that have an open dirport -- it's
8487 just the authoritative dirservers we want to not forget.
8488 - Reject tor-resolve requests for .onion addresses early, so we
8489 don't build a whole rendezvous circuit and then fail.
8490 - When you're warning a server that he's unverified, don't cry
8492 - Fix a race condition: don't try to extend onto a connection
8493 that's still handshaking.
8494 - For servers in clique mode, require the conn to be open before
8495 you'll choose it for your path.
8496 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
8497 end relay cell, etc.
8498 - Measure bandwidth capacity over the last 24 hours, not just 12
8499 - Bugfix: authoritative dirservers were making and signing a new
8500 directory for each client, rather than reusing the cached one.
8503 Changes in version 0.0.8pre2 - 2004-08-04
8504 o Changes from 0.0.7.2:
8506 - Check directory signature _before_ you decide whether you're
8507 you're running an obsolete version and should exit.
8508 - Check directory signature _before_ you parse the running-routers
8509 list to decide who's running or verified.
8510 - Bugfixes and features:
8511 - Check return value of fclose while writing to disk, so we don't
8512 end up with broken files when servers run out of disk space.
8513 - Log a warning if the user uses an unsafe socks variant, so people
8514 are more likely to learn about privoxy or socat.
8515 - Dirservers now include RFC1123-style dates in the HTTP headers,
8516 which one day we will use to better detect clock skew.
8518 o Changes from 0.0.8pre1:
8519 - Make it compile without warnings again on win32.
8520 - Log a warning if you're running an unverified server, to let you
8521 know you might want to get it verified.
8522 - Only pick a default nickname if you plan to be a server.
8525 Changes in version 0.0.8pre1 - 2004-07-23
8527 - Made our unit tests compile again on OpenBSD 3.5, and tor
8528 itself compile again on OpenBSD on a sparc64.
8529 - We were neglecting milliseconds when logging on win32, so
8530 everything appeared to happen at the beginning of each second.
8533 - 'Extend' relay cell payloads now include the digest of the
8534 intended next hop's identity key. Now we can verify that we're
8535 extending to the right router, and also extend to routers we
8536 hadn't heard of before.
8539 - Tor nodes can now act as relays (with an advertised ORPort)
8540 without being manually verified by the dirserver operators.
8541 - Uploaded descriptors of unverified routers are now accepted
8542 by the dirservers, and included in the directory.
8543 - Verified routers are listed by nickname in the running-routers
8544 list; unverified routers are listed as "$<fingerprint>".
8545 - We now use hash-of-identity-key in most places rather than
8546 nickname or addr:port, for improved security/flexibility.
8547 - To avoid Sybil attacks, paths still use only verified servers.
8548 But now we have a chance to play around with hybrid approaches.
8549 - Nodes track bandwidth usage to estimate capacity (not used yet).
8550 - ClientOnly option for nodes that never want to become servers.
8551 - Directory caching.
8552 - "AuthoritativeDir 1" option for the official dirservers.
8553 - Now other nodes (clients and servers) will cache the latest
8554 directory they've pulled down.
8555 - They can enable their DirPort to serve it to others.
8556 - Clients will pull down a directory from any node with an open
8557 DirPort, and check the signature/timestamp correctly.
8558 - Authoritative dirservers now fetch directories from other
8559 authdirservers, to stay better synced.
8560 - Running-routers list tells who's down also, along with noting
8561 if they're verified (listed by nickname) or unverified (listed
8563 - Allow dirservers to serve running-router list separately.
8564 This isn't used yet.
8565 - ORs connect-on-demand to other ORs
8566 - If you get an extend cell to an OR you're not connected to,
8567 connect, handshake, and forward the create cell.
8568 - The authoritative dirservers stay connected to everybody,
8569 and everybody stays connected to 0.0.7 servers, but otherwise
8570 clients/servers expire unused connections after 5 minutes.
8571 - When servers get a sigint, they delay 30 seconds (refusing new
8572 connections) then exit. A second sigint causes immediate exit.
8573 - File and name management:
8574 - Look for .torrc if no CONFDIR "torrc" is found.
8575 - If no datadir is defined, then choose, make, and secure ~/.tor
8577 - If torrc not found, exitpolicy reject *:*.
8578 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
8579 - If no nickname is defined, derive default from hostname.
8580 - Rename secret key files, e.g. identity.key -> secret_id_key,
8581 to discourage people from mailing their identity key to tor-ops.
8582 - Refuse to build a circuit before the directory has arrived --
8583 it won't work anyway, since you won't know the right onion keys
8585 - Try other dirservers immediately if the one you try is down. This
8586 should tolerate down dirservers better now.
8587 - Parse tor version numbers so we can do an is-newer-than check
8588 rather than an is-in-the-list check.
8589 - New socks command 'resolve', to let us shim gethostbyname()
8591 - A 'tor_resolve' script to access the socks resolve functionality.
8592 - A new socks-extensions.txt doc file to describe our
8593 interpretation and extensions to the socks protocols.
8594 - Add a ContactInfo option, which gets published in descriptor.
8595 - Publish OR uptime in descriptor (and thus in directory) too.
8596 - Write tor version at the top of each log file
8597 - New docs in the tarball:
8599 - Document that you should proxy your SSL traffic too.
8602 Changes in version 0.0.7.2 - 2004-07-07
8603 o A better fix for the 0.0.0.0 problem, that will hopefully
8604 eliminate the remaining related assertion failures.
8607 Changes in version 0.0.7.1 - 2004-07-04
8608 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
8609 since internally we use 0.0.0.0 to signify "not yet resolved".
8612 Changes in version 0.0.7 - 2004-06-07
8613 o Updated the man page to reflect the new features.
8616 Changes in version 0.0.7rc2 - 2004-06-06
8617 o Changes from 0.0.7rc1:
8618 - Make it build on Win32 again.
8619 o Changes from 0.0.6.2:
8620 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
8624 Changes in version 0.0.7rc1 - 2004-06-02
8626 - On sighup, we were adding another log without removing the first
8627 one. So log messages would get duplicated n times for n sighups.
8628 - Several cases of using a connection after we'd freed it. The
8629 problem was that connections that are pending resolve are in both
8630 the pending_resolve tree, and also the circuit's resolving_streams
8631 list. When you want to remove one, you must remove it from both.
8632 - Fix a double-mark-for-close where an end cell arrived for a
8633 resolving stream, and then the resolve failed.
8634 - Check directory signatures based on name of signer, not on whom
8635 we got the directory from. This will let us cache directories more
8638 - Crank up some of our constants to handle more users.
8641 Changes in version 0.0.7pre1 - 2004-06-02
8642 o Fixes for crashes and other obnoxious bugs:
8643 - Fix an epipe bug: sometimes when directory connections failed
8644 to connect, we would give them a chance to flush before closing
8646 - When we detached from a circuit because of resolvefailed, we
8647 would immediately try the same circuit twice more, and then
8648 give up on the resolve thinking we'd tried three different
8650 - Limit the number of intro circuits we'll attempt to build for a
8651 hidden service per 15-minute period.
8652 - Check recommended-software string *early*, before actually parsing
8653 the directory. Thus we can detect an obsolete version and exit,
8654 even if the new directory format doesn't parse.
8655 o Fixes for security bugs:
8656 - Remember which nodes are dirservers when you startup, and if a
8657 random OR enables his dirport, don't automatically assume he's
8658 a trusted dirserver.
8660 - Directory connections were asking the wrong poll socket to
8661 start writing, and not asking themselves to start writing.
8662 - When we detached from a circuit because we sent a begin but
8663 didn't get a connected, we would use it again the first time;
8664 but after that we would correctly switch to a different one.
8665 - Stop warning when the first onion decrypt attempt fails; they
8666 will sometimes legitimately fail now that we rotate keys.
8667 - Override unaligned-access-ok check when $host_cpu is ia64 or
8668 arm. Apparently they allow it but the kernel whines.
8669 - Dirservers try to reconnect periodically too, in case connections
8671 - Fix some memory leaks in directory servers.
8672 - Allow backslash in Win32 filenames.
8673 - Made Tor build complain-free on FreeBSD, hopefully without
8674 breaking other BSD builds. We'll see.
8676 - Doxygen markup on all functions and global variables.
8677 - Make directory functions update routerlist, not replace it. So
8678 now directory disagreements are not so critical a problem.
8679 - Remove the upper limit on number of descriptors in a dirserver's
8680 directory (not that we were anywhere close).
8681 - Allow multiple logfiles at different severity ranges.
8682 - Allow *BindAddress to specify ":port" rather than setting *Port
8683 separately. Allow multiple instances of each BindAddress config
8684 option, so you can bind to multiple interfaces if you want.
8685 - Allow multiple exit policy lines, which are processed in order.
8686 Now we don't need that huge line with all the commas in it.
8687 - Enable accept/reject policies on SOCKS connections, so you can bind
8688 to 0.0.0.0 but still control who can use your OP.
8691 Changes in version 0.0.6.2 - 2004-05-16
8692 o Our integrity-checking digest was checking only the most recent cell,
8693 not the previous cells like we'd thought.
8694 Thanks to Stefan Mark for finding the flaw!
8697 Changes in version 0.0.6.1 - 2004-05-06
8698 o Fix two bugs in our AES counter-mode implementation (this affected
8699 onion-level stream encryption, but not TLS-level). It turns
8700 out we were doing something much more akin to a 16-character
8701 polyalphabetic cipher. Oops.
8702 Thanks to Stefan Mark for finding the flaw!
8703 o Retire moria3 as a directory server, and add tor26 as a directory
8707 Changes in version 0.0.6 - 2004-05-02
8711 Changes in version 0.0.6rc4 - 2004-05-01
8712 o Update the built-in dirservers list to use the new directory format
8713 o Fix a rare seg fault: if a node offering a hidden service attempts
8714 to build a circuit to Alice's rendezvous point and fails before it
8715 reaches the last hop, it retries with a different circuit, but
8717 o Handle windows socket errors correctly.
8720 Changes in version 0.0.6rc3 - 2004-04-28
8721 o Don't expire non-general excess circuits (if we had enough
8722 circuits open, we were expiring rendezvous circuits -- even
8723 when they had a stream attached. oops.)
8724 o Fetch randomness from /dev/urandom better (not via fopen/fread)
8725 o Better debugging for tls errors
8726 o Some versions of openssl have an SSL_pending function that erroneously
8727 returns bytes when there is a non-application record pending.
8728 o Set Content-Type on the directory and hidserv descriptor.
8729 o Remove IVs from cipher code, since AES-ctr has none.
8730 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
8731 o We were using an array of length zero in a few places.
8732 o win32's gethostbyname can't resolve an IP to an IP.
8733 o win32's close can't close a socket.
8736 Changes in version 0.0.6rc2 - 2004-04-26
8737 o Fix a bug where we were closing tls connections intermittently.
8738 It turns out openssl keeps its errors around -- so if an error
8739 happens, and you don't ask about it, and then another openssl
8740 operation happens and succeeds, and you ask if there was an error,
8741 it tells you about the first error. Fun fun.
8742 o Fix a bug that's been lurking since 27 may 03 (!)
8743 When passing back a destroy cell, we would use the wrong circ id.
8744 'Mostly harmless', but still worth fixing.
8745 o Since we don't support truncateds much, don't bother sending them;
8746 just close the circ.
8747 o check for <machine/limits.h> so we build on NetBSD again (I hope).
8748 o don't crash if a conn that sent a begin has suddenly lost its circuit
8749 (this was quite rare).
8752 Changes in version 0.0.6rc1 - 2004-04-25
8753 o We now rotate link (tls context) keys and onion keys.
8754 o CREATE cells now include oaep padding, so you can tell
8755 if you decrypted them correctly.
8756 o Add bandwidthburst to server descriptor.
8757 o Directories now say which dirserver signed them.
8758 o Use a tor_assert macro that logs failed assertions too.
8761 Changes in version 0.0.6pre5 - 2004-04-18
8762 o changes from 0.0.6pre4:
8763 - make tor build on broken freebsd 5.2 installs
8764 - fix a failed assert when you try an intro point, get a nack, and try
8765 a second one and it works.
8766 - when alice uses a port that the hidden service doesn't accept,
8767 it now sends back an end cell (denied by exit policy). otherwise
8768 alice would just have to wait to time out.
8769 - fix another rare bug: when we had tried all the intro
8770 points for a hidden service, we fetched the descriptor
8771 again, but we left our introcirc thinking it had already
8772 sent an intro, so it kept waiting for a response...
8773 - bugfix: when you sleep your hidden-service laptop, as soon
8774 as it wakes up it tries to upload a service descriptor, but
8775 socketpair fails for some reason (localhost not up yet?).
8776 now we simply give up on that upload, and we'll try again later.
8777 i'd still like to find the bug though.
8778 - if an intro circ waiting for an ack dies before getting one, then
8780 - we were reusing stale service descriptors and refetching usable
8784 Changes in version 0.0.6pre4 - 2004-04-14
8785 o changes from 0.0.6pre3:
8786 - when bob fails to connect to the rendezvous point, and his
8787 circ didn't fail because of the rendezvous point itself, then
8788 he retries a couple of times
8789 - we expire introduction and rendezvous circs more thoroughly
8790 (sometimes they were hanging around forever)
8791 - we expire unattached rendezvous streams that have been around
8792 too long (they were sticking around forever).
8793 - fix a measly fencepost error that was crashing everybody with
8797 Changes in version 0.0.6pre3 - 2004-04-14
8798 o changes from 0.0.6pre2:
8799 - make hup work again
8800 - fix some memory leaks for dirservers
8801 - allow more skew in rendezvous descriptor timestamps, to help
8802 handle people like blanu who don't know what time it is
8803 - normal circs are 3 hops, but some rend/intro circs are 4, if
8804 the initiator doesn't get to choose the last hop
8805 - send acks for introductions, so alice can know whether to try
8807 - bob publishes intro points more correctly
8808 o changes from 0.0.5:
8809 - fix an assert trigger that's been plaguing us since the days
8810 of 0.0.2prexx (thanks weasel!)
8811 - retry stream correctly when we fail to connect because of
8812 exit-policy-reject (should try another) or can't-resolve-address
8813 (also should try another, because dns on random internet servers
8815 - when we hup a dirserver and we've *removed* a server from the
8816 approved-routers list, now we remove that server from the
8817 in-memory directories too
8820 Changes in version 0.0.6pre2 - 2004-04-08
8821 o We fixed our base32 implementation. Now it works on all architectures.
8824 Changes in version 0.0.6pre1 - 2004-04-08
8826 - Hidden services and rendezvous points are implemented. Go to
8827 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
8828 hidden services. (This only works via a socks4a proxy such as
8829 Privoxy, and currently it's quite slow.)
8832 Changes in version 0.0.5 - 2004-03-30
8836 Changes in version 0.0.5rc3 - 2004-03-29
8837 o Install torrc as torrc.sample -- we no longer clobber your
8839 o Re-enable recommendedversion checking (we broke it in rc2, oops)
8840 o Add in a 'notice' log level for things the operator should hear
8841 but that aren't warnings
8844 Changes in version 0.0.5rc2 - 2004-03-29
8845 o Hold socks connection open until reply is flushed (if possible)
8846 o Make exit nodes resolve IPs to IPs immediately, rather than asking
8847 the dns farm to do it.
8848 o Fix c99 aliasing warnings in rephist.c
8849 o Don't include server descriptors that are older than 24 hours in the
8851 o Give socks 'reject' replies their whole 15s to attempt to flush,
8852 rather than seeing the 60s timeout and assuming the flush had failed.
8853 o Clean automake droppings from the cvs repository
8856 Changes in version 0.0.5rc1 - 2004-03-28
8857 o Fix mangled-state bug in directory fetching (was causing sigpipes).
8858 o Only build circuits after we've fetched the directory: clients were
8859 using only the directory servers before they'd fetched a directory.
8860 This also means longer startup time; so it goes.
8861 o Fix an assert trigger where an OP would fail to handshake, and we'd
8862 expect it to have a nickname.
8863 o Work around a tsocks bug: do a socks reject when AP connection dies
8864 early, else tsocks goes into an infinite loop.
8867 Changes in version 0.0.4 - 2004-03-26
8868 o When connecting to a dirserver or OR and the network is down,
8872 Changes in version 0.0.3 - 2004-03-26
8873 o Warn and fail if server chose a nickname with illegal characters
8874 o Port to Solaris and Sparc:
8875 - include missing header fcntl.h
8876 - have autoconf find -lsocket -lnsl automatically
8877 - deal with hardware word alignment
8878 - make uname() work (solaris has a different return convention)
8879 - switch from using signal() to sigaction()
8880 o Preliminary work on reputation system:
8881 - Keep statistics on success/fail of connect attempts; they're published
8882 by kill -USR1 currently.
8883 - Add a RunTesting option to try to learn link state by creating test
8884 circuits, even when SocksPort is off.
8885 - Remove unused open circuits when there are too many.
8888 Changes in version 0.0.2 - 2004-03-19
8889 - Include strlcpy and strlcat for safer string ops
8890 - define INADDR_NONE so we compile (but still not run) on solaris
8893 Changes in version 0.0.2pre27 - 2004-03-14
8895 - Allow internal tor networks (we were rejecting internal IPs,
8896 now we allow them if they're set explicitly).
8897 - And fix a few endian issues.
8900 Changes in version 0.0.2pre26 - 2004-03-14
8902 - If a stream times out after 15s without a connected cell, don't
8903 try that circuit again: try a new one.
8904 - Retry streams at most 4 times. Then give up.
8905 - When a dirserver gets a descriptor from an unknown router, it
8906 logs its fingerprint (so the dirserver operator can choose to
8907 accept it even without mail from the server operator).
8908 - Inform unapproved servers when we reject their descriptors.
8909 - Make tor build on Windows again. It works as a client, who knows
8911 - Clearer instructions in the torrc for how to set up a server.
8912 - Be more efficient about reading fd's when our global token bucket
8913 (used for rate limiting) becomes empty.
8915 - Stop asserting that computers always go forward in time. It's
8917 - When we sent a cell (e.g. destroy) and then marked an OR connection
8918 expired, we might close it before finishing a flush if the other
8919 side isn't reading right then.
8920 - Don't allow dirservers to start if they haven't defined
8922 - We were caching transient dns failures. Oops.
8923 - Prevent servers from publishing an internal IP as their address.
8924 - Address a strcat vulnerability in circuit.c
8927 Changes in version 0.0.2pre25 - 2004-03-04
8929 - Put the OR's IP in its router descriptor, not its fqdn. That way
8930 we'll stop being stalled by gethostbyname for nodes with flaky dns,
8933 - If the user typed in an address that didn't resolve, the server
8937 Changes in version 0.0.2pre24 - 2004-03-03
8939 - Fix an assertion failure in dns.c, where we were trying to dequeue
8940 a pending dns resolve even if it wasn't pending
8941 - Fix a spurious socks5 warning about still trying to write after the
8942 connection is finished.
8943 - Hold certain marked_for_close connections open until they're finished
8944 flushing, rather than losing bytes by closing them too early.
8945 - Correctly report the reason for ending a stream
8946 - Remove some duplicate calls to connection_mark_for_close
8947 - Put switch_id and start_daemon earlier in the boot sequence, so it
8948 will actually try to chdir() to options.DataDirectory
8949 - Make 'make test' exit(1) if a test fails; fix some unit tests
8950 - Make tor fail when you use a config option it doesn't know about,
8951 rather than warn and continue.
8952 - Make --version work
8953 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
8956 Changes in version 0.0.2pre23 - 2004-02-29
8958 - Print a statement when the first circ is finished, so the user
8960 - If a relay cell is unrecognized at the end of the circuit,
8961 send back a destroy. (So attacks to mutate cells are more
8963 - New config option 'excludenodes' to avoid certain nodes for circuits.
8964 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
8965 so you can collect coredumps there.
8967 - Fix a bug in tls flushing where sometimes data got wedged and
8968 didn't flush until more data got sent. Hopefully this bug was
8969 a big factor in the random delays we were seeing.
8970 - Make 'connected' cells include the resolved IP, so the client
8971 dns cache actually gets populated.
8972 - Disallow changing from ORPort=0 to ORPort>0 on hup.
8973 - When we time-out on a stream and detach from the circuit, send an
8974 end cell down it first.
8975 - Only warn about an unknown router (in exitnodes, entrynodes,
8976 excludenodes) after we've fetched a directory.
8979 Changes in version 0.0.2pre22 - 2004-02-26
8981 - Servers publish less revealing uname information in descriptors.
8982 - More memory tracking and assertions, to crash more usefully when
8984 - If the default torrc isn't there, just use some default defaults.
8985 Plus provide an internal dirservers file if they don't have one.
8986 - When the user tries to use Tor as an http proxy, give them an http
8987 501 failure explaining that we're a socks proxy.
8988 - Dump a new router.desc on hup, to help confused people who change
8989 their exit policies and then wonder why router.desc doesn't reflect
8991 - Clean up the generic tor.sh init script that we ship with.
8993 - If the exit stream is pending on the resolve, and a destroy arrives,
8994 then the stream wasn't getting removed from the pending list. I
8995 think this was the one causing recent server crashes.
8996 - Use a more robust poll on OSX 10.3, since their poll is flaky.
8997 - When it couldn't resolve any dirservers, it was useless from then on.
8998 Now it reloads the RouterFile (or default dirservers) if it has no
9000 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
9001 many users don't even *have* a /usr/local/sbin/.
9004 Changes in version 0.0.2pre21 - 2004-02-18
9006 - There's a ChangeLog file that actually reflects the changelog.
9007 - There's a 'torify' wrapper script, with an accompanying
9008 tor-tsocks.conf, that simplifies the process of using tsocks for
9009 tor. It even has a man page.
9010 - The tor binary gets installed to sbin rather than bin now.
9011 - Retry streams where the connected cell hasn't arrived in 15 seconds
9012 - Clean up exit policy handling -- get the default out of the torrc,
9013 so we can update it without forcing each server operator to fix
9015 - Allow imaps and pop3s in default exit policy
9017 - Prevent picking middleman nodes as the last node in the circuit
9020 Changes in version 0.0.2pre20 - 2004-01-30
9022 - We now have a deb package, and it's in debian unstable. Go to
9024 - I've split the TotalBandwidth option into BandwidthRate (how many
9025 bytes per second you want to allow, long-term) and
9026 BandwidthBurst (how many bytes you will allow at once before the cap
9027 kicks in). This better token bucket approach lets you, say, set
9028 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
9029 performance while not exceeding your monthly bandwidth quota.
9030 - Push out a tls record's worth of data once you've got it, rather
9031 than waiting until you've read everything waiting to be read. This
9032 may improve performance by pipelining better. We'll see.
9033 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
9034 from failed circuits (if they haven't been connected yet) and attach
9036 - Expire old streams that haven't managed to connect. Some day we'll
9037 have them reattach to new circuits instead.
9040 - Fix several memory leaks that were causing servers to become bloated
9042 - Fix a few very rare assert triggers. A few more remain.
9043 - Setuid to User _before_ complaining about running as root.
9046 Changes in version 0.0.2pre19 - 2004-01-07
9048 - Fix deadlock condition in dns farm. We were telling a child to die by
9049 closing the parent's file descriptor to him. But newer children were
9050 inheriting the open file descriptor from the parent, and since they
9051 weren't closing it, the socket never closed, so the child never read
9052 eof, so he never knew to exit. Similarly, dns workers were holding
9053 open other sockets, leading to all sorts of chaos.
9054 - New cleaner daemon() code for forking and backgrounding.
9055 - If you log to a file, it now prints an entry at the top of the
9056 logfile so you know it's working.
9057 - The onionskin challenge length was 30 bytes longer than necessary.
9058 - Started to patch up the spec so it's not quite so out of date.
9061 Changes in version 0.0.2pre18 - 2004-01-02
9063 - Fix endian issues with the 'integrity' field in the relay header.
9064 - Fix a potential bug where connections in state
9065 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
9068 Changes in version 0.0.2pre17 - 2003-12-30
9070 - Made --debuglogfile (or any second log file, actually) work.
9071 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
9072 adversary could force us into an infinite loop.
9075 - Each onionskin handshake now includes a hash of the computed key,
9076 to prove the server's identity and help perfect forward secrecy.
9077 - Changed cell size from 256 to 512 bytes (working toward compatibility
9079 - Changed cell length to 2 bytes, and moved it to the relay header.
9080 - Implemented end-to-end integrity checking for the payloads of
9082 - Separated streamid from 'recognized' (otherwise circuits will get
9083 messed up when we try to have streams exit from the middle). We
9084 use the integrity-checking to confirm that a cell is addressed to
9086 - Randomize the initial circid and streamid values, so an adversary who
9087 breaks into a node can't learn how many circuits or streams have
9091 Changes in version 0.0.2pre16 - 2003-12-14
9093 - Fixed a bug that made HUP trigger an assert
9094 - Fixed a bug where a circuit that immediately failed wasn't being
9095 counted as a failed circuit in counting retries.
9098 - Now we close the circuit when we get a truncated cell: otherwise we're
9099 open to an anonymity attack where a bad node in the path truncates
9100 the circuit and then we open streams at him.
9101 - Add port ranges to exit policies
9102 - Add a conservative default exit policy
9103 - Warn if you're running tor as root
9104 - on HUP, retry OR connections and close/rebind listeners
9105 - options.EntryNodes: try these nodes first when picking the first node
9106 - options.ExitNodes: if your best choices happen to include any of
9107 your preferred exit nodes, you choose among just those preferred
9109 - options.ExcludedNodes: nodes that are never picked in path building
9112 Changes in version 0.0.2pre15 - 2003-12-03
9113 o Robustness and bugfixes:
9114 - Sometimes clients would cache incorrect DNS resolves, which would
9115 really screw things up.
9116 - An OP that goes offline would slowly leak all its sockets and stop
9118 - A wide variety of bugfixes in exit node selection, exit policy
9119 handling, and processing pending streams when a new circuit is
9121 - Pick nodes for a path only from those the directory says are up
9122 - Choose randomly from all running dirservers, not always the first one
9123 - Increase allowed http header size for directory fetch.
9124 - Stop writing to stderr (if we're daemonized it will be closed).
9125 - Enable -g always, so cores will be more useful to me.
9126 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
9129 - Wrote a man page. It lists commonly used options.
9132 - Change default loglevel to warn.
9133 - Make PidFile default to null rather than littering in your CWD.
9134 - OnionRouter config option is now obsolete. Instead it just checks
9136 - Moved to a single unified torrc file for both clients and servers.
9139 Changes in version 0.0.2pre14 - 2003-11-29
9140 o Robustness and bugfixes:
9141 - Force the admin to make the DataDirectory himself
9142 - to get ownership/permissions right
9143 - so clients no longer make a DataDirectory and then never use it
9144 - fix bug where a client who was offline for 45 minutes would never
9145 pull down a directory again
9146 - fix (or at least hide really well) the dns assert bug that was
9147 causing server crashes
9148 - warnings and improved robustness wrt clockskew for certs
9149 - use the native daemon(3) to daemonize, when available
9150 - exit if bind() fails
9151 - exit if neither socksport nor orport is defined
9152 - include our own tor_timegm (Win32 doesn't have its own)
9153 - bugfix for win32 with lots of connections
9154 - fix minor bias in PRNG
9155 - make dirserver more robust to corrupt cached directory
9158 - Wrote the design document (woo)
9160 o Circuit building and exit policies:
9161 - Circuits no longer try to use nodes that the directory has told them
9163 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
9164 bitcounts (18.0.0.0/8).
9165 - Make AP connections standby for a circuit if no suitable circuit
9166 exists, rather than failing
9167 - Circuits choose exit node based on addr/port, exit policies, and
9168 which AP connections are standing by
9169 - Bump min pathlen from 2 to 3
9170 - Relay end cells have a payload to describe why the stream ended.
9171 - If the stream failed because of exit policy, try again with a new
9173 - Clients have a dns cache to remember resolved addresses.
9174 - Notice more quickly when we have no working circuits
9177 - APPort is now called SocksPort
9178 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
9180 - RecommendedVersions is now a config variable rather than
9181 hardcoded (for dirservers)
9182 - Reloads config on HUP
9183 - Usage info on -h or --help
9184 - If you set User and Group config vars, it'll setu/gid to them.
9187 Changes in version 0.0.2pre13 - 2003-10-19
9188 o General stability:
9189 - SSL_write no longer fails when it returns WANTWRITE and the number
9190 of bytes in the buf has changed by the next SSL_write call.
9191 - Fix segfault fetching directory when network is down
9192 - Fix a variety of minor memory leaks
9193 - Dirservers reload the fingerprints file on HUP, so I don't have
9194 to take down the network when I approve a new router
9195 - Default server config file has explicit Address line to specify fqdn
9198 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
9199 - Make listener connections not ever alloc bufs
9201 o Autoconf improvements:
9202 - don't clobber an external CFLAGS in ./configure
9203 - Make install now works
9204 - create var/lib/tor on make install
9205 - autocreate a tor.sh initscript to help distribs
9206 - autocreate the torrc and sample-server-torrc with correct paths
9208 o Log files and Daemonizing now work:
9209 - If --DebugLogFile is specified, log to it at -l debug
9210 - If --LogFile is specified, use it instead of commandline
9211 - If --RunAsDaemon is set, tor forks and backgrounds on startup