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