1 Changes in version 0.2.2.14-alpha - 2010-06-30
3 - Tor directory authorities no longer crash when started with a
4 cached-microdesc-consensus file in their data directory. Bugfix on
5 0.2.2.6-alpha, fixes bug 1532.
6 - Treat an unset $HOME like an empty $HOME rather than triggering an
7 assert. Fixes bug 1522; bugfix on tor-0.0.8pre1.
10 - Move to the June 2010 Maxmind GeoLite country db (rather than the
11 June 2009 ip-to-country GeoIP db) for our statistics that count
12 how many users relays are seeing from each country. Now we have
13 more accurate data for many African countries.
14 - Port Tor to build and run correctly on Windows CE systems, using
15 the wcecompat library. Contributed by Valerio Lupi.
16 - New "--enable-gcc-hardening" ./configure flag to turn on gcc
17 compile time hardening options. It ensures that signed ints have
18 defined behavior (-fwrapv), -D_FORTIFY_SOURCE=2 is enabled
19 (requiring -O2), stack smashing protection with canaries
20 (-fstack-protector-all), ASLR protection if supported by the
21 kernel (-fPIE, -pie). Additional security related warnings are
22 enabled. Verified to work on Mac OS X and Debian Lenny.
23 - New "--enable-linker-hardening" ./configure flag to turn on ELF
24 specific hardening features (relro, now). This does not work with
25 Mac OS X or any other non-ELF binary format.
27 o New directory authorities:
28 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
32 - New config option "WarnUnsafeSocks 0" disables the warning that
33 occurs whenever Tor receives only an IP address instead of a
34 hostname. Setups that do DNS locally over Tor are fine, and we
35 shouldn't spam the logs in that case.
36 - Convert the HACKING file to asciidoc, and add a few new sections
37 to it, explaining how we use Git, how we make changelogs, and
38 what should go in a patch.
41 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
43 - When a2x fails, mention that the user could disable manpages instead
44 of trying to fix their asciidoc installation.
45 - Where available, use Libevent 2.0's periodic timers so that our
46 once-per-second cleanup code gets called even more closely to
47 once per second than it would otherwise. Fixes bug 943.
48 - If you run a bridge that listens on multiple IP addresses, and
49 some user configures a bridge address that uses a different IP
50 address than your bridge writes in its router descriptor, and the
51 user doesn't specify an identity key, their Tor would discard the
52 descriptor because "it isn't one of our configured bridges", and
53 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
54 Bugfix on 0.2.0.3-alpha.
55 - If OpenSSL fails to make a duplicate of a private or public key, log
56 an error message and try to exit cleanly. May help with debugging
57 if bug 1209 ever remanifests.
58 - Save a couple bytes in memory allocation every time we escape
59 certain characters in a string. Patch from Florian Zumbiehl.
60 - Make it explicit that we don't cannibalize one-hop circuits. This
61 happens in the wild, but doesn't turn out to be a problem because
62 we fortunately don't use those circuits. Many thanks to outofwords
63 for the initial analysis and to swissknife who confirmed that
64 two-hop circuits are actually created.
67 Changes in version 0.2.1.26 - 2010-05-02
68 Tor 0.2.1.26 addresses the recent connection and memory overload
69 problems we've been seeing on relays, especially relays with their
70 DirPort open. If your relay has been crashing, or you turned it off
71 because it used too many resources, give this release a try.
73 This release also fixes yet another instance of broken OpenSSL libraries
74 that was causing some relays to drop out of the consensus.
77 - Teach relays to defend themselves from connection overload. Relays
78 now close idle circuits early if it looks like they were intended
79 for directory fetches. Relays are also more aggressive about closing
80 TLS connections that have no circuits on them. Such circuits are
81 unlikely to be re-used, and tens of thousands of them were piling
82 up at the fast relays, causing the relays to run out of sockets
83 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
84 their directory fetches over TLS).
85 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
86 that claim to be earlier than 0.9.8m, but which have in reality
87 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
88 behavior. Possible fix for some cases of bug 1346.
89 - Directory mirrors were fetching relay descriptors only from v2
90 directory authorities, rather than v3 authorities like they should.
91 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
92 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
95 - Finally get rid of the deprecated and now harmful notion of "clique
96 mode", where directory authorities maintain TLS connections to
100 - In the util/threads test, no longer free the test_mutex before all
101 worker threads have finished. Bugfix on 0.2.1.6-alpha.
102 - The master thread could starve the worker threads quite badly on
103 certain systems, causing them to run only partially in the allowed
104 window. This resulted in test failures. Now the master thread sleeps
105 occasionally for a few microseconds while the two worker-threads
106 compete for the mutex. Bugfix on 0.2.0.1-alpha.
109 Changes in version 0.2.2.13-alpha - 2010-04-24
110 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
111 problems we've been seeing on relays, especially relays with their
112 DirPort open. If your relay has been crashing, or you turned it off
113 because it used too many resources, give this release a try.
116 - Teach relays to defend themselves from connection overload. Relays
117 now close idle circuits early if it looks like they were intended
118 for directory fetches. Relays are also more aggressive about closing
119 TLS connections that have no circuits on them. Such circuits are
120 unlikely to be re-used, and tens of thousands of them were piling
121 up at the fast relays, causing the relays to run out of sockets
122 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
123 their directory fetches over TLS).
126 - Finally get rid of the deprecated and now harmful notion of "clique
127 mode", where directory authorities maintain TLS connections to
129 - Directory authorities now do an immediate reachability check as soon
130 as they hear about a new relay. This change should slightly reduce
131 the time between setting up a relay and getting listed as running
132 in the consensus. It should also improve the time between setting
133 up a bridge and seeing use by bridge users.
134 - Directory authorities no longer launch a TLS connection to every
135 relay as they startup. Now that we have 2k+ descriptors cached,
136 the resulting network hiccup is becoming a burden. Besides,
137 authorities already avoid voting about Running for the first half
138 hour of their uptime.
141 Changes in version 0.2.2.12-alpha - 2010-04-20
142 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
143 handle and vote on descriptors. It was causing relays to drop out of
147 - Many relays have been falling out of the consensus lately because
148 not enough authorities know about their descriptor for them to get
149 a majority of votes. When we deprecated the v2 directory protocol,
150 we got rid of the only way that v3 authorities can hear from each
151 other about other descriptors. Now authorities examine every v3
152 vote for new descriptors, and fetch them from that authority. Bugfix
154 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
155 and a warning in or.h related to bandwidth_weight_rule_t that
156 prevented clean compile on OS X. Fixes bug 1363; bugfix on
158 - Fix a segfault on relays when DirReqStatistics is enabled
159 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
163 - Demote a confusing TLS warning that relay operators might get when
164 someone tries to talk to their OrPort. It is neither the operator's
165 fault nor can they do anything about it. Fixes bug 1364; bugfix
169 Changes in version 0.2.2.11-alpha - 2010-04-15
170 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
171 libraries that was causing some relays to drop out of the consensus.
174 - Directory mirrors were fetching relay descriptors only from v2
175 directory authorities, rather than v3 authorities like they should.
176 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
177 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
178 - Fix a parsing error that made every possible value of
179 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
180 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
181 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
182 about the option without breaking older ones.
183 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
184 that claim to be earlier than 0.9.8m, but which have in reality
185 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
186 behavior. Possible fix for some cases of bug 1346.
189 - Experiment with a more aggressive approach to preventing clients
190 from making one-hop exit streams. Exit relays who want to try it
191 out can set "RefuseUnknownExits 1" in their torrc, and then look
192 for "Attempt by %s to open a stream" log messages. Let us know
194 - Add support for statically linking zlib by specifying
195 --enable-static-zlib, to go with our support for statically linking
196 openssl and libevent. Resolves bug 1358.
199 - Fix a segfault that happens whenever a Tor client that is using
200 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
202 - When we cleaned up the contrib/tor-exit-notice.html file, we left
203 out the first line. Fixes bug 1295.
204 - When building the manpage from a tarball, we required asciidoc, but
205 the asciidoc -> roff/html conversion was already done for the
206 tarball. Make 'make' complain only when we need asciidoc (either
207 because we're compiling directly from git, or because we altered
208 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
209 - When none of the directory authorities vote on any params, Tor
210 segfaulted when trying to make the consensus from the votes. We
211 didn't trigger the bug in practice, because authorities do include
212 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
215 - In the util/threads test, no longer free the test_mutex before all
216 worker threads have finished. Bugfix on 0.2.1.6-alpha.
217 - The master thread could starve the worker threads quite badly on
218 certain systems, causing them to run only partially in the allowed
219 window. This resulted in test failures. Now the master thread sleeps
220 occasionally for a few microseconds while the two worker-threads
221 compete for the mutex. Bugfix on 0.2.0.1-alpha.
224 Changes in version 0.2.2.10-alpha - 2010-03-07
225 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
226 could prevent relays from guessing their IP address correctly. It also
227 starts the groundwork for another client-side performance boost, since
228 currently we're not making efficient use of relays that have both the
229 Guard flag and the Exit flag.
232 - Fix a regression from our patch for bug 1244 that caused relays
233 to guess their IP address incorrectly if they didn't set Address
234 in their torrc and/or their address fails to resolve. Bugfix on
235 0.2.2.9-alpha; fixes bug 1269.
237 o Major features (performance):
238 - Directory authorities now compute consensus weightings that instruct
239 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
240 and no flag. Clients that use these weightings will distribute
241 network load more evenly across these different relay types. The
242 weightings are in the consensus so we can change them globally in
243 the future. Extra thanks to "outofwords" for finding some nasty
244 security bugs in the first implementation of this feature.
246 o Minor features (performance):
247 - Always perform router selections using weighted relay bandwidth,
248 even if we don't need a high capacity circuit at the time. Non-fast
249 circuits now only differ from fast ones in that they can use relays
250 not marked with the Fast flag. This "feature" could turn out to
251 be a horrible bug; we should investigate more before it goes into
255 - Allow disabling building of the manpages. Skipping the manpage
256 speeds up the build considerably.
258 o Minor bugfixes (on 0.2.2.x):
259 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
260 Bugfix on 0.2.2.9-alpha.
261 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
262 config option. Bugfix on 0.2.2.7-alpha.
263 - Ship the asciidoc-helper file in the tarball, so that people can
264 build from source if they want to, and touching the .1.txt files
265 doesn't break the build. Bugfix on 0.2.2.9-alpha.
267 o Minor bugfixes (on 0.2.1.x or earlier):
268 - Fix a dereference-then-NULL-check sequence when publishing
269 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
271 - Fix another dereference-then-NULL-check sequence. Bugfix on
272 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
273 - Make sure we treat potentially not NUL-terminated strings correctly.
274 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
276 o Code simplifications and refactoring:
277 - Fix some urls in the exit notice file and make it XHTML1.1 strict
278 compliant. Based on a patch from Christian Kujau.
279 - Don't use sed in asciidoc-helper anymore.
280 - Make the build process fail if asciidoc cannot be found and
281 building with asciidoc isn't disabled.
284 Changes in version 0.2.2.9-alpha - 2010-02-22
285 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
286 location of a directory authority, and cleans up a bunch of small bugs.
288 o Directory authority changes:
289 - Change IP address for dannenberg (v3 directory authority), and
290 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
291 service directory authority) from the list.
294 - Make Tor work again on the latest OS X: when deciding whether to
295 use strange flags to turn TLS renegotiation on, detect the OpenSSL
296 version at run-time, not compile time. We need to do this because
297 Apple doesn't update its dev-tools headers when it updates its
298 libraries in a security patch.
299 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
300 that could happen on 32-bit platforms with 64-bit time_t. Also fix
301 a memory leak when requesting a hidden service descriptor we've
302 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
304 - Authorities could be tricked into giving out the Exit flag to relays
305 that didn't allow exiting to any ports. This bug could screw
306 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
307 1238. Bug discovered by Martin Kowalczyk.
308 - When freeing a session key, zero it out completely. We only zeroed
309 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
310 patched by ekir. Fixes bug 1254.
313 - Fix static compilation by listing the openssl libraries in the right
314 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
315 - Resume handling .exit hostnames in a special way: originally we
316 stripped the .exit part and used the requested exit relay. In
317 0.2.2.1-alpha we stopped treating them in any special way, meaning
318 if you use a .exit address then Tor will pass it on to the exit
319 relay. Now we reject the .exit stream outright, since that behavior
320 might be more expected by the user. Found and diagnosed by Scott
321 Bennett and Downie on or-talk.
322 - Don't spam the controller with events when we have no file
323 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
324 for log messages was already solved from bug 748.)
325 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
327 - Make the DNSPort option work with libevent 2.x. Don't alter the
328 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
329 - Emit a GUARD DROPPED controller event for a case we missed.
330 - Make more fields in the controller protocol case-insensitive, since
331 control-spec.txt said they were.
332 - Refactor resolve_my_address() to not use gethostbyname() anymore.
333 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
334 - Fix a spec conformance issue: the network-status-version token
335 must be the first token in a v3 consensus or vote. Discovered by
336 parakeep. Bugfix on 0.2.0.3-alpha.
338 o Code simplifications and refactoring:
339 - Generate our manpage and HTML documentation using Asciidoc. This
340 change should make it easier to maintain the documentation, and
342 - Remove the --enable-iphone option. According to reports from Marco
343 Bonetti, Tor builds fine without any special tweaking on recent
345 - Removed some unnecessary files from the source distribution. The
346 AUTHORS file has now been merged into the people page on the
347 website. The roadmaps and design doc can now be found in the
348 projects directory in svn.
349 - Enabled various circuit build timeout constants to be controlled
350 by consensus parameters. Also set better defaults for these
351 parameters based on experimentation on broadband and simulated
355 - The 'EXTENDCIRCUIT' control port command can now be used with
356 a circ id of 0 and no path. This feature will cause Tor to build
357 a new 'fast' general purpose circuit using its own path selection
359 - Added a BUILDTIMEOUT_SET controller event to describe changes
360 to the circuit build timeout.
361 - Future-proof the controller protocol a bit by ignoring keyword
362 arguments we do not recognize.
363 - Expand homedirs passed to tor-checkkey. This should silence a
364 coverity complaint about passing a user-supplied string into
365 open() without checking it.
368 Changes in version 0.2.1.25 - 2010-03-16
369 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
370 prevent relays from guessing their IP address correctly. It also fixes
371 several minor potential security bugs.
374 - Fix a regression from our patch for bug 1244 that caused relays
375 to guess their IP address incorrectly if they didn't set Address
376 in their torrc and/or their address fails to resolve. Bugfix on
377 0.2.1.23; fixes bug 1269.
378 - When freeing a session key, zero it out completely. We only zeroed
379 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
380 patched by ekir. Fixes bug 1254.
383 - Fix a dereference-then-NULL-check sequence when publishing
384 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
386 - Fix another dereference-then-NULL-check sequence. Bugfix on
387 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
388 - Make sure we treat potentially not NUL-terminated strings correctly.
389 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
393 Changes in version 0.2.1.24 - 2010-02-21
394 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
398 - Work correctly out-of-the-box with even more vendor-patched versions
399 of OpenSSL. In particular, make it so Debian and OS X don't need
400 customized patches to run/build.
403 Changes in version 0.2.1.23 - 2010-02-13
404 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
405 again on the latest OS X, and updates the location of a directory
408 o Major bugfixes (performance):
409 - We were selecting our guards uniformly at random, and then weighting
410 which of our guards we'd use uniformly at random. This imbalance
411 meant that Tor clients were severely limited on throughput (and
412 probably latency too) by the first hop in their circuit. Now we
413 select guards weighted by currently advertised bandwidth. We also
414 automatically discard guards picked using the old algorithm. Fixes
415 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
418 - Make Tor work again on the latest OS X: when deciding whether to
419 use strange flags to turn TLS renegotiation on, detect the OpenSSL
420 version at run-time, not compile time. We need to do this because
421 Apple doesn't update its dev-tools headers when it updates its
422 libraries in a security patch.
423 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
424 that could happen on 32-bit platforms with 64-bit time_t. Also fix
425 a memory leak when requesting a hidden service descriptor we've
426 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
429 o Directory authority changes:
430 - Change IP address for dannenberg (v3 directory authority), and
431 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
432 service directory authority) from the list.
435 - Refactor resolve_my_address() to not use gethostbyname() anymore.
436 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
439 - Avoid a mad rush at the beginning of each month when each client
440 rotates half of its guards. Instead we spread the rotation out
441 throughout the month, but we still avoid leaving a precise timestamp
442 in the state file about when we first picked the guard. Improves
443 over the behavior introduced in 0.1.2.17.
446 Changes in version 0.2.2.8-alpha - 2010-01-26
447 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
448 causing bridge relays to disappear. If you're running a bridge,
452 - Fix a memory corruption bug on bridges that occured during the
453 inclusion of stats data in extra-info descriptors. Also fix the
454 interface for geoip_get_bridge_stats* to prevent similar bugs in
455 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
456 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
459 - Ignore OutboundBindAddress when connecting to localhost.
460 Connections to localhost need to come _from_ localhost, or else
461 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
465 Changes in version 0.2.2.7-alpha - 2010-01-19
466 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
467 as laying the groundwork for further relay-side performance fixes. It
468 also starts cleaning up client behavior with respect to the EntryNodes,
469 ExitNodes, and StrictNodes config options.
471 This release also rotates two directory authority keys, due to a
472 security breach of some of the Torproject servers.
474 o Directory authority changes:
475 - Rotate keys (both v3 identity and relay identity) for moria1
478 o Major features (performance):
479 - We were selecting our guards uniformly at random, and then weighting
480 which of our guards we'd use uniformly at random. This imbalance
481 meant that Tor clients were severely limited on throughput (and
482 probably latency too) by the first hop in their circuit. Now we
483 select guards weighted by currently advertised bandwidth. We also
484 automatically discard guards picked using the old algorithm. Fixes
485 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
486 - When choosing which cells to relay first, relays can now favor
487 circuits that have been quiet recently, to provide lower latency
488 for low-volume circuits. By default, relays enable or disable this
489 feature based on a setting in the consensus. You can override
490 this default by using the new "CircuitPriorityHalflife" config
491 option. Design and code by Ian Goldberg, Can Tang, and Chris
493 - Add separate per-conn write limiting to go with the per-conn read
494 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
495 but never per-conn write limits.
496 - New consensus params "bwconnrate" and "bwconnburst" to let us
497 rate-limit client connections as they enter the network. It's
498 controlled in the consensus so we can turn it on and off for
499 experiments. It's starting out off. Based on proposal 163.
501 o Major features (relay selection options):
502 - Switch to a StrictNodes config option, rather than the previous
503 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
504 "StrictExcludeNodes" option.
505 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
506 change during a config reload, mark and discard all our origin
507 circuits. This fix should address edge cases where we change the
508 config options and but then choose a circuit that we created before
510 - If EntryNodes or ExitNodes are set, be more willing to use an
511 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
513 - Make EntryNodes config option much more aggressive even when
514 StrictNodes is not set. Before it would prepend your requested
515 entrynodes to your list of guard nodes, but feel free to use others
516 after that. Now it chooses only from your EntryNodes if any of
517 those are available, and only falls back to others if a) they're
518 all down and b) StrictNodes is not set.
519 - Now we refresh your entry guards from EntryNodes at each consensus
520 fetch -- rather than just at startup and then they slowly rot as
524 - Stop bridge directory authorities from answering dbg-stability.txt
525 directory queries, which would let people fetch a list of all
526 bridge identities they track. Bugfix on 0.2.1.6-alpha.
529 - Log a notice when we get a new control connection. Now it's easier
530 for security-conscious users to recognize when a local application
531 is knocking on their controller door. Suggested by bug 1196.
532 - New config option "CircuitStreamTimeout" to override our internal
533 timeout schedule for how many seconds until we detach a stream from
534 a circuit and try a new circuit. If your network is particularly
535 slow, you might want to set this to a number like 60.
536 - New controller command "getinfo config-text". It returns the
537 contents that Tor would write if you send it a SAVECONF command,
538 so the controller can write the file to disk itself.
539 - New options for SafeLogging to allow scrubbing only log messages
540 generated while acting as a relay.
541 - Ship the bridges spec file in the tarball too.
542 - Avoid a mad rush at the beginning of each month when each client
543 rotates half of its guards. Instead we spread the rotation out
544 throughout the month, but we still avoid leaving a precise timestamp
545 in the state file about when we first picked the guard. Improves
546 over the behavior introduced in 0.1.2.17.
548 o Minor bugfixes (compiling):
549 - Fix compilation on OS X 10.3, which has a stub mlockall() but
550 hides it. Bugfix on 0.2.2.6-alpha.
551 - Fix compilation on Solaris by removing support for the
552 DisableAllSwap config option. Solaris doesn't have an rlimit for
553 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
556 o Minor bugfixes (crashes):
557 - Do not segfault when writing buffer stats when we haven't observed
558 a single circuit to report about. Found by Fabian Lanze. Bugfix on
560 - If we're in the pathological case where there's no exit bandwidth
561 but there is non-exit bandwidth, or no guard bandwidth but there
562 is non-guard bandwidth, don't crash during path selection. Bugfix
564 - Fix an impossible-to-actually-trigger buffer overflow in relay
565 descriptor generation. Bugfix on 0.1.0.15.
567 o Minor bugfixes (privacy):
568 - Fix an instance where a Tor directory mirror might accidentally
569 log the IP address of a misbehaving Tor client. Bugfix on
571 - Don't list Windows capabilities in relay descriptors. We never made
572 use of them, and maybe it's a bad idea to publish them. Bugfix
575 o Minor bugfixes (other):
576 - Resolve an edge case in path weighting that could make us misweight
577 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
578 - Fix statistics on client numbers by country as seen by bridges that
579 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
580 intervals instead of variable 12-to-48-hour intervals.
581 - After we free an internal connection structure, overwrite it
582 with a different memory value than we use for overwriting a freed
583 internal circuit structure. Should help with debugging. Suggested
585 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
589 - Remove the HSAuthorityRecordStats option that version 0 hidden
590 service authorities could have used to track statistics of overall
591 hidden service usage.
594 Changes in version 0.2.1.22 - 2010-01-19
595 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
596 authorities -- it would tell you its whole history of bridge descriptors
597 if you make the right directory request. This stable update also
598 rotates two of the seven v3 directory authority keys and locations.
600 o Directory authority changes:
601 - Rotate keys (both v3 identity and relay identity) for moria1
605 - Stop bridge directory authorities from answering dbg-stability.txt
606 directory queries, which would let people fetch a list of all
607 bridge identities they track. Bugfix on 0.2.1.6-alpha.
610 Changes in version 0.2.1.21 - 2009-12-21
611 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
612 library. If you use Tor on Linux / Unix and you're getting SSL
613 renegotiation errors, upgrading should help. We also recommend an
614 upgrade if you're an exit relay.
617 - Work around a security feature in OpenSSL 0.9.8l that prevents our
618 handshake from working unless we explicitly tell OpenSSL that we
619 are using SSL renegotiation safely. We are, of course, but OpenSSL
620 0.9.8l won't work unless we say we are.
621 - Avoid crashing if the client is trying to upload many bytes and the
622 circuit gets torn down at the same time, or if the flip side
623 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
626 - Do not refuse to learn about authority certs and v2 networkstatus
627 documents that are older than the latest consensus. This bug might
628 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
629 Spotted and fixed by xmux.
630 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
631 trigger platform-specific option misparsing case found by Coverity
633 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
634 trigger assert. Fixes bug 1173.
637 Changes in version 0.2.2.6-alpha - 2009-11-19
638 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
639 support for the new lower-footprint "microdescriptor" directory design,
640 future-proofing our consensus format against new hash functions or
641 other changes, and an Android port. It also makes Tor compatible with
642 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
645 - Directory authorities can now create, vote on, and serve multiple
646 parallel formats of directory data as part of their voting process.
647 Partially implements Proposal 162: "Publish the consensus in
649 - Directory authorities can now agree on and publish small summaries
650 of router information that clients can use in place of regular
651 server descriptors. This transition will eventually allow clients
652 to use far less bandwidth for downloading information about the
653 network. Begins the implementation of Proposal 158: "Clients
654 download consensus + microdescriptors".
655 - The directory voting system is now extensible to use multiple hash
656 algorithms for signatures and resource selection. Newer formats
657 are signed with SHA256, with a possibility for moving to a better
658 hash algorithm in the future.
659 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
660 current and future memory pages via mlockall(). On supported
661 platforms (modern Linux and probably BSD but not Windows or OS X),
662 this should effectively disable any and all attempts to page out
663 memory. This option requires that you start your Tor as root --
664 if you use DisableAllSwap, please consider using the User option
665 to properly reduce the privileges of your Tor.
666 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
667 to help Tor build correctly for Android phones.
670 - Work around a security feature in OpenSSL 0.9.8l that prevents our
671 handshake from working unless we explicitly tell OpenSSL that we
672 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
673 won't work unless we say we are.
676 - Fix a crash bug when trying to initialize the evdns module in
677 Libevent 2. Bugfix on 0.2.1.16-rc.
678 - Stop logging at severity 'warn' when some other Tor client tries
679 to establish a circuit with us using weak DH keys. It's a protocol
680 violation, but that doesn't mean ordinary users need to hear about
681 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
682 - Do not refuse to learn about authority certs and v2 networkstatus
683 documents that are older than the latest consensus. This bug might
684 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
685 Spotted and fixed by xmux.
686 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
687 - If all authorities restart at once right before a consensus vote,
688 nobody will vote about "Running", and clients will get a consensus
689 with no usable relays. Instead, authorities refuse to build a
690 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
691 - If your relay can't keep up with the number of incoming create
692 cells, it would log one warning per failure into your logs. Limit
693 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
694 - Bridges now use "reject *:*" as their default exit policy. Bugfix
695 on 0.2.0.3-alpha; fixes bug 1113.
696 - Fix a memory leak on directory authorities during voting that was
697 introduced in 0.2.2.1-alpha. Found via valgrind.
700 Changes in version 0.2.1.20 - 2009-10-15
701 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
702 services at once, prepares for more performance improvements, and
703 fixes a bunch of smaller bugs.
705 The Windows and OS X bundles also include a more recent Vidalia,
706 and switch from Privoxy to Polipo.
708 The OS X installers are now drag and drop. It's best to un-install
709 Tor/Vidalia and then install this new bundle, rather than upgrade. If
710 you want to upgrade, you'll need to update the paths for Tor and Polipo
711 in the Vidalia Settings window.
714 - Send circuit or stream sendme cells when our window has decreased
715 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
716 by Karsten when testing the "reduce circuit window" performance
717 patch. Bugfix on the 54th commit on Tor -- from July 2002,
718 before the release of Tor 0.0.0. This is the new winner of the
720 - Fix a remotely triggerable memory leak when a consensus document
721 contains more than one signature from the same voter. Bugfix on
723 - Avoid segfault in rare cases when finishing an introduction circuit
724 as a client and finding out that we don't have an introduction key
725 for it. Fixes bug 1073. Reported by Aaron Swartz.
728 - Tor now reads the "circwindow" parameter out of the consensus,
729 and uses that value for its circuit package window rather than the
730 default of 1000 cells. Begins the implementation of proposal 168.
732 o New directory authorities:
733 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
735 - Move moria1 and tonga to alternate IP addresses.
738 - Fix a signed/unsigned compile warning in 0.2.1.19.
739 - Fix possible segmentation fault on directory authorities. Bugfix on
741 - Fix an extremely rare infinite recursion bug that could occur if
742 we tried to log a message after shutting down the log subsystem.
743 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
744 - Fix an obscure bug where hidden services on 64-bit big-endian
745 systems might mis-read the timestamp in v3 introduce cells, and
746 refuse to connect back to the client. Discovered by "rotor".
747 Bugfix on 0.2.1.6-alpha.
748 - We were triggering a CLOCK_SKEW controller status event whenever
749 we connect via the v2 connection protocol to any relay that has
750 a wrong clock. Instead, we should only inform the controller when
751 it's a trusted authority that claims our clock is wrong. Bugfix
752 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
753 - We were telling the controller about CHECKING_REACHABILITY and
754 REACHABILITY_FAILED status events whenever we launch a testing
755 circuit or notice that one has failed. Instead, only tell the
756 controller when we want to inform the user of overall success or
757 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
759 - Don't warn when we're using a circuit that ends with a node
760 excluded in ExcludeExitNodes, but the circuit is not used to access
761 the outside world. This should help fix bug 1090. Bugfix on
763 - Work around a small memory leak in some versions of OpenSSL that
764 stopped the memory used by the hostname TLS extension from being
768 - Add a "getinfo status/accepted-server-descriptor" controller
769 command, which is the recommended way for controllers to learn
770 whether our server descriptor has been successfully received by at
771 least on directory authority. Un-recommend good-server-descriptor
772 getinfo and status events until we have a better design for them.
775 Changes in version 0.2.2.5-alpha - 2009-10-11
776 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
779 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
781 o New directory authorities:
782 - Move dizum to an alternate IP address.
785 Changes in version 0.2.2.4-alpha - 2009-10-10
786 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
787 introduces a new unit test framework, shifts directry authority
788 addresses around to reduce the impact from recent blocking events,
789 and fixes a few smaller bugs.
792 - Fix several more asserts in the circuit_build_times code, for
793 example one that causes Tor to fail to start once we have
794 accumulated 5000 build times in the state file. Bugfixes on
795 0.2.2.2-alpha; fixes bug 1108.
797 o New directory authorities:
798 - Move moria1 and Tonga to alternate IP addresses.
801 - Log SSL state transitions at debug level during handshake, and
802 include SSL states in error messages. This may help debug future
803 SSL handshake issues.
804 - Add a new "Handshake" log domain for activities that happen
805 during the TLS handshake.
806 - Revert to the "June 3 2009" ip-to-country file. The September one
807 seems to have removed most US IP addresses.
808 - Directory authorities now reject Tor relays with versions less than
809 0.1.2.14. This step cuts out four relays from the current network,
810 none of which are very big.
813 - Fix a couple of smaller issues with gathering statistics. Bugfixes
815 - Fix two memory leaks in the error case of
816 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
817 - Don't count one-hop circuits when we're estimating how long it
818 takes circuits to build on average. Otherwise we'll set our circuit
819 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
820 - Directory authorities no longer change their opinion of, or vote on,
821 whether a router is Running, unless they have themselves been
822 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
825 o Code simplifications and refactoring:
826 - Revise our unit tests to use the "tinytest" framework, so we
827 can run tests in their own processes, have smarter setup/teardown
828 code, and so on. The unit test code has moved to its own
829 subdirectory, and has been split into multiple modules.
832 Changes in version 0.2.2.3-alpha - 2009-09-23
833 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
836 - Fix an overzealous assert in our new circuit build timeout code.
837 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
840 - If the networkstatus consensus tells us that we should use a
841 negative circuit package window, ignore it. Otherwise we'll
842 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
845 Changes in version 0.2.2.2-alpha - 2009-09-21
846 Tor 0.2.2.2-alpha introduces our latest performance improvement for
847 clients: Tor tracks the average time it takes to build a circuit, and
848 avoids using circuits that take too long to build. For fast connections,
849 this feature can cut your expected latency in half. For slow or flaky
850 connections, it could ruin your Tor experience. Let us know if it does!
853 - Tor now tracks how long it takes to build client-side circuits
854 over time, and adapts its timeout to local network performance.
855 Since a circuit that takes a long time to build will also provide
856 bad performance, we get significant latency improvements by
857 discarding the slowest 20% of circuits. Specifically, Tor creates
858 circuits more aggressively than usual until it has enough data
859 points for a good timeout estimate. Implements proposal 151.
860 We are especially looking for reports (good and bad) from users with
861 both EDGE and broadband connections that can move from broadband
862 to EDGE and find out if the build-time data in the .tor/state gets
863 reset without loss of Tor usability. You should also see a notice
864 log message telling you that Tor has reset its timeout.
865 - Directory authorities can now vote on arbitary integer values as
866 part of the consensus process. This is designed to help set
867 network-wide parameters. Implements proposal 167.
868 - Tor now reads the "circwindow" parameter out of the consensus,
869 and uses that value for its circuit package window rather than the
870 default of 1000 cells. Begins the implementation of proposal 168.
873 - Fix a remotely triggerable memory leak when a consensus document
874 contains more than one signature from the same voter. Bugfix on
878 - Fix an extremely rare infinite recursion bug that could occur if
879 we tried to log a message after shutting down the log subsystem.
880 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
881 - Fix parsing for memory or time units given without a space between
882 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
883 - A networkstatus vote must contain exactly one signature. Spec
884 conformance issue. Bugfix on 0.2.0.3-alpha.
885 - Fix an obscure bug where hidden services on 64-bit big-endian
886 systems might mis-read the timestamp in v3 introduce cells, and
887 refuse to connect back to the client. Discovered by "rotor".
888 Bugfix on 0.2.1.6-alpha.
889 - We were triggering a CLOCK_SKEW controller status event whenever
890 we connect via the v2 connection protocol to any relay that has
891 a wrong clock. Instead, we should only inform the controller when
892 it's a trusted authority that claims our clock is wrong. Bugfix
893 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
894 - We were telling the controller about CHECKING_REACHABILITY and
895 REACHABILITY_FAILED status events whenever we launch a testing
896 circuit or notice that one has failed. Instead, only tell the
897 controller when we want to inform the user of overall success or
898 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
900 - Don't warn when we're using a circuit that ends with a node
901 excluded in ExcludeExitNodes, but the circuit is not used to access
902 the outside world. This should help fix bug 1090, but more problems
903 remain. Bugfix on 0.2.1.6-alpha.
904 - Work around a small memory leak in some versions of OpenSSL that
905 stopped the memory used by the hostname TLS extension from being
907 - Make our 'torify' script more portable; if we have only one of
908 'torsocks' or 'tsocks' installed, don't complain to the user;
909 and explain our warning about tsocks better.
912 - Add a "getinfo status/accepted-server-descriptor" controller
913 command, which is the recommended way for controllers to learn
914 whether our server descriptor has been successfully received by at
915 least on directory authority. Un-recommend good-server-descriptor
916 getinfo and status events until we have a better design for them.
917 - Update to the "September 4 2009" ip-to-country file.
920 Changes in version 0.2.2.1-alpha - 2009-08-26
921 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
922 Tor clients to bootstrap on networks where only port 80 is reachable,
923 makes it more straightforward to support hardware crypto accelerators,
924 and starts the groundwork for gathering stats safely at relays.
927 - Start the process of disabling ".exit" address notation, since it
928 can be used for a variety of esoteric application-level attacks
929 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
932 o New directory authorities:
933 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
937 - New AccelName and AccelDir options add support for dynamic OpenSSL
938 hardware crypto acceleration engines.
939 - Tor now supports tunneling all of its outgoing connections over
940 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
941 configuration options. Code by Christopher Davis.
944 - Send circuit or stream sendme cells when our window has decreased
945 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
946 by Karsten when testing the "reduce circuit window" performance
947 patch. Bugfix on the 54th commit on Tor -- from July 2002,
948 before the release of Tor 0.0.0. This is the new winner of the
951 o New options for gathering stats safely:
952 - Directories that set "DirReqStatistics 1" write statistics on
953 directory request to disk every 24 hours. As compared to the
954 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
955 1) stats are written to disk exactly every 24 hours; 2) estimated
956 shares of v2 and v3 requests are determined as mean values, not at
957 the end of a measurement period; 3) unresolved requests are listed
958 with country code '??'; 4) directories also measure download times.
959 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
960 number of exit streams and transferred bytes per port to disk every
962 - Relays that set "CellStatistics 1" write statistics on how long
963 cells spend in their circuit queues to disk every 24 hours.
964 - Entry nodes that set "EntryStatistics 1" write statistics on the
965 rough number and origins of connecting clients to disk every 24
967 - Relays that write any of the above statistics to disk and set
968 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
969 their extra-info documents.
972 - New --digests command-line switch to output the digests of the
973 source files Tor was built with.
974 - The "torify" script now uses torsocks where available.
975 - The memarea code now uses a sentinel value at the end of each area
976 to make sure nothing writes beyond the end of an area. This might
977 help debug some conceivable causes of bug 930.
978 - Time and memory units in the configuration file can now be set to
979 fractional units. For example, "2.5 GB" is now a valid value for
981 - Certain Tor clients (such as those behind check.torproject.org) may
982 want to fetch the consensus in an extra early manner. To enable this
983 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
984 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
985 as only certain clients who must have this information sooner should
987 - Instead of adding the svn revision to the Tor version string, report
988 the git commit (when we're building from a git checkout).
991 - If any the v3 certs we download are unparseable, we should actually
992 notice the failure so we don't retry indefinitely. Bugfix on
993 0.2.0.x; reported by "rotator".
994 - If the cached cert file is unparseable, warn but don't exit.
995 - Fix possible segmentation fault on directory authorities. Bugfix on
997 - When Tor fails to parse a descriptor of any kind, dump it to disk.
998 Might help diagnosing bug 1051.
1000 o Deprecated and removed features:
1001 - The controller no longer accepts the old obsolete "addr-mappings/"
1002 or "unregistered-servers-" GETINFO values.
1003 - Hidden services no longer publish version 0 descriptors, and clients
1004 do not request or use version 0 descriptors. However, the old hidden
1005 service authorities still accept and serve version 0 descriptors
1006 when contacted by older hidden services/clients.
1007 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
1008 always on; using them is necessary for correct forward-compatible
1010 - Remove support for .noconnect style addresses. Nobody was using
1011 them, and they provided another avenue for detecting Tor users
1012 via application-level web tricks.
1014 o Packaging changes:
1015 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
1016 installer bundles. See
1017 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
1018 for details of what's new in Vidalia 0.2.3.
1019 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
1020 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
1021 configuration file, rather than the old Privoxy.
1022 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
1023 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
1024 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
1025 better compatibility with OS X 10.6, aka Snow Leopard.
1026 - OS X Vidalia Bundle: The multi-package installer is now replaced
1027 by a simple drag and drop to the /Applications folder. This change
1028 occurred with the upgrade to Vidalia 0.2.3.
1031 Changes in version 0.2.1.19 - 2009-07-28
1032 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
1033 services on Tor 0.2.1.3-alpha through 0.2.1.18.
1036 - Make accessing hidden services on 0.2.1.x work right again.
1037 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
1038 part of patch provided by "optimist".
1041 - When a relay/bridge is writing out its identity key fingerprint to
1042 the "fingerprint" file and to its logs, write it without spaces. Now
1043 it will look like the fingerprints in our bridges documentation,
1044 and confuse fewer users.
1047 - Relays no longer publish a new server descriptor if they change
1048 their MaxAdvertisedBandwidth config option but it doesn't end up
1049 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
1050 fixes bug 1026. Patch from Sebastian.
1051 - Avoid leaking memory every time we get a create cell but we have
1052 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
1053 fixes bug 1034. Reported by BarkerJr.
1056 Changes in version 0.2.1.18 - 2009-07-24
1057 Tor 0.2.1.18 lays the foundations for performance improvements,
1058 adds status events to help users diagnose bootstrap problems, adds
1059 optional authentication/authorization for hidden services, fixes a
1060 variety of potential anonymity problems, and includes a huge pile of
1061 other features and bug fixes.
1064 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
1067 Changes in version 0.2.1.17-rc - 2009-07-07
1068 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
1069 candidate for the 0.2.1.x series. It lays the groundwork for further
1070 client performance improvements, and also fixes a big bug with directory
1071 authorities that were causing them to assign Guard and Stable flags
1074 The Windows bundles also finally include the geoip database that we
1075 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
1076 should actually install Torbutton rather than giving you a cryptic
1077 failure message (oops).
1080 - Clients now use the bandwidth values in the consensus, rather than
1081 the bandwidth values in each relay descriptor. This approach opens
1082 the door to more accurate bandwidth estimates once the directory
1083 authorities start doing active measurements. Implements more of
1087 - When Tor clients restart after 1-5 days, they discard all their
1088 cached descriptors as too old, but they still use the cached
1089 consensus document. This approach is good for robustness, but
1090 bad for performance: since they don't know any bandwidths, they
1091 end up choosing at random rather than weighting their choice by
1092 speed. Fixed by the above feature of putting bandwidths in the
1093 consensus. Bugfix on 0.2.0.x.
1094 - Directory authorities were neglecting to mark relays down in their
1095 internal histories if the relays fall off the routerlist without
1096 ever being found unreachable. So there were relays in the histories
1097 that haven't been seen for eight months, and are listed as being
1098 up for eight months. This wreaked havoc on the "median wfu"
1099 and "median mtbf" calculations, in turn making Guard and Stable
1100 flags very wrong, hurting network performance. Fixes bugs 696 and
1101 969. Bugfix on 0.2.0.6-alpha.
1104 - Serve the DirPortFrontPage page even when we have been approaching
1105 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
1106 - The control port would close the connection before flushing long
1107 replies, such as the network consensus, if a QUIT command was issued
1108 before the reply had completed. Now, the control port flushes all
1109 pending replies before closing the connection. Also fixed a spurious
1110 warning when a QUIT command is issued after a malformed or rejected
1111 AUTHENTICATE command, but before the connection was closed. Patch
1112 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
1113 - When we can't find an intro key for a v2 hidden service descriptor,
1114 fall back to the v0 hidden service descriptor and log a bug message.
1115 Workaround for bug 1024.
1116 - Fix a log message that did not respect the SafeLogging option.
1120 - If we're a relay and we change our IP address, be more verbose
1121 about the reason that made us change. Should help track down
1122 further bugs for relays on dynamic IP addresses.
1125 Changes in version 0.2.0.35 - 2009-06-24
1127 - Avoid crashing in the presence of certain malformed descriptors.
1128 Found by lark, and by automated fuzzing.
1129 - Fix an edge case where a malicious exit relay could convince a
1130 controller that the client's DNS question resolves to an internal IP
1131 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
1134 - Finally fix the bug where dynamic-IP relays disappear when their
1135 IP address changes: directory mirrors were mistakenly telling
1136 them their old address if they asked via begin_dir, so they
1137 never got an accurate answer about their new address, so they
1138 just vanished after a day. For belt-and-suspenders, relays that
1139 don't set Address in their config now avoid using begin_dir for
1140 all direct connections. Should fix bugs 827, 883, and 900.
1141 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
1142 that would occur on some exit nodes when DNS failures and timeouts
1143 occurred in certain patterns. Fix for bug 957.
1146 - When starting with a cache over a few days old, do not leak
1147 memory for the obsolete router descriptors in it. Bugfix on
1148 0.2.0.33; fixes bug 672.
1149 - Hidden service clients didn't use a cached service descriptor that
1150 was older than 15 minutes, but wouldn't fetch a new one either,
1151 because there was already one in the cache. Now, fetch a v2
1152 descriptor unless the same descriptor was added to the cache within
1153 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
1156 Changes in version 0.2.1.16-rc - 2009-06-20
1157 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
1158 a bunch of minor bugs.
1161 - Fix an edge case where a malicious exit relay could convince a
1162 controller that the client's DNS question resolves to an internal IP
1163 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
1165 o Major performance improvements (on 0.2.0.x):
1166 - Disable and refactor some debugging checks that forced a linear scan
1167 over the whole server-side DNS cache. These accounted for over 50%
1168 of CPU time on a relatively busy exit node's gprof profile. Found
1170 - Disable some debugging checks that appeared in exit node profile
1174 - Update to the "June 3 2009" ip-to-country file.
1175 - Do not have tor-resolve automatically refuse all .onion addresses;
1176 if AutomapHostsOnResolve is set in your torrc, this will work fine.
1178 o Minor bugfixes (on 0.2.0.x):
1179 - Log correct error messages for DNS-related network errors on
1181 - Fix a race condition that could cause crashes or memory corruption
1182 when running as a server with a controller listening for log
1184 - Avoid crashing when we have a policy specified in a DirPolicy or
1185 SocksPolicy or ReachableAddresses option with ports set on it,
1186 and we re-load the policy. May fix bug 996.
1187 - Hidden service clients didn't use a cached service descriptor that
1188 was older than 15 minutes, but wouldn't fetch a new one either,
1189 because there was already one in the cache. Now, fetch a v2
1190 descriptor unless the same descriptor was added to the cache within
1191 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
1193 o Minor bugfixes (on 0.2.1.x):
1194 - Don't warn users about low port and hibernation mix when they
1195 provide a *ListenAddress directive to fix that. Bugfix on
1197 - When switching back and forth between bridge mode, do not start
1198 gathering GeoIP data until two hours have passed.
1199 - Do not complain that the user has requested an excluded node as
1200 an exit when the node is not really an exit. This could happen
1201 because the circuit was for testing, or an introduction point.
1205 Changes in version 0.2.1.15-rc - 2009-05-25
1206 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
1207 series. It fixes a major bug on fast exit relays, as well as a variety
1210 o Major bugfixes (on 0.2.0.x):
1211 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
1212 that would occur on some exit nodes when DNS failures and timeouts
1213 occurred in certain patterns. Fix for bug 957.
1215 o Minor bugfixes (on 0.2.0.x):
1216 - Actually return -1 in the error case for read_bandwidth_usage().
1217 Harmless bug, since we currently don't care about the return value
1218 anywhere. Bugfix on 0.2.0.9-alpha.
1219 - Provide a more useful log message if bug 977 (related to buffer
1220 freelists) ever reappears, and do not crash right away.
1221 - Fix an assertion failure on 64-bit platforms when we allocated
1222 memory right up to the end of a memarea, then realigned the memory
1223 one step beyond the end. Fixes a possible cause of bug 930.
1224 - Protect the count of open sockets with a mutex, so we can't
1225 corrupt it when two threads are closing or opening sockets at once.
1226 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
1227 - Don't allow a bridge to publish its router descriptor to a
1228 non-bridge directory authority. Fixes part of bug 932.
1229 - When we change to or from being a bridge, reset our counts of
1230 client usage by country. Fixes bug 932.
1231 - Fix a bug that made stream bandwidth get misreported to the
1233 - Stop using malloc_usable_size() to use more area than we had
1234 actually allocated: it was safe, but made valgrind really unhappy.
1235 - Fix a memory leak when v3 directory authorities load their keys
1236 and cert from disk. Bugfix on 0.2.0.1-alpha.
1238 o Minor bugfixes (on 0.2.1.x):
1239 - Fix use of freed memory when deciding to mark a non-addable
1240 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
1243 Changes in version 0.2.1.14-rc - 2009-04-12
1244 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
1245 series. It begins fixing some major performance problems, and also
1246 finally addresses the bug that was causing relays on dynamic IP
1247 addresses to fall out of the directory.
1250 - Clients replace entry guards that were chosen more than a few months
1251 ago. This change should significantly improve client performance,
1252 especially once more people upgrade, since relays that have been
1253 a guard for a long time are currently overloaded.
1255 o Major bugfixes (on 0.2.0):
1256 - Finally fix the bug where dynamic-IP relays disappear when their
1257 IP address changes: directory mirrors were mistakenly telling
1258 them their old address if they asked via begin_dir, so they
1259 never got an accurate answer about their new address, so they
1260 just vanished after a day. For belt-and-suspenders, relays that
1261 don't set Address in their config now avoid using begin_dir for
1262 all direct connections. Should fix bugs 827, 883, and 900.
1263 - Relays were falling out of the networkstatus consensus for
1264 part of a day if they changed their local config but the
1265 authorities discarded their new descriptor as "not sufficiently
1266 different". Now directory authorities accept a descriptor as changed
1267 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
1269 - Avoid crashing in the presence of certain malformed descriptors.
1270 Found by lark, and by automated fuzzing.
1273 - When generating circuit events with verbose nicknames for
1274 controllers, try harder to look up nicknames for routers on a
1275 circuit. (Previously, we would look in the router descriptors we had
1276 for nicknames, but not in the consensus.) Partial fix for bug 941.
1277 - If the bridge config line doesn't specify a port, assume 443.
1278 This makes bridge lines a bit smaller and easier for users to
1280 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
1281 bytes (aka 20KB/s), to match our documentation. Also update
1282 directory authorities so they always assign the Fast flag to relays
1283 with 20KB/s of capacity. Now people running relays won't suddenly
1284 find themselves not seeing any use, if the network gets faster
1286 - Update to the "April 3 2009" ip-to-country file.
1289 - Avoid trying to print raw memory to the logs when we decide to
1290 give up on downloading a given relay descriptor. Bugfix on
1292 - In tor-resolve, when the Tor client to use is specified by
1293 <hostname>:<port>, actually use the specified port rather than
1294 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
1295 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
1296 - When starting with a cache over a few days old, do not leak
1297 memory for the obsolete router descriptors in it. Bugfix on
1299 - Avoid double-free on list of successfully uploaded hidden
1300 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
1301 - Change memarea_strndup() implementation to work even when
1302 duplicating a string at the end of a page. This bug was
1303 harmless for now, but could have meant crashes later. Fix by
1304 lark. Bugfix on 0.2.1.1-alpha.
1305 - Limit uploaded directory documents to be 16M rather than 500K.
1306 The directory authorities were refusing v3 consensus votes from
1307 other authorities, since the votes are now 504K. Fixes bug 959;
1308 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
1309 - Directory authorities should never send a 503 "busy" response to
1310 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
1314 Changes in version 0.2.1.13-alpha - 2009-03-09
1315 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
1316 cleanups. We're finally getting close to a release candidate.
1319 - Correctly update the list of which countries we exclude as
1320 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
1321 lark. Bugfix on 0.2.1.6-alpha.
1323 o Minor bugfixes (on 0.2.0.x and earlier):
1324 - Automatically detect MacOSX versions earlier than 10.4.0, and
1325 disable kqueue from inside Tor when running with these versions.
1326 We previously did this from the startup script, but that was no
1327 help to people who didn't use the startup script. Resolves bug 863.
1328 - When we had picked an exit node for a connection, but marked it as
1329 "optional", and it turned out we had no onion key for the exit,
1330 stop wanting that exit and try again. This situation may not
1331 be possible now, but will probably become feasible with proposal
1332 158. Spotted by rovv. Fixes another case of bug 752.
1333 - Clients no longer cache certificates for authorities they do not
1334 recognize. Bugfix on 0.2.0.9-alpha.
1335 - When we can't transmit a DNS request due to a network error, retry
1336 it after a while, and eventually transmit a failing response to
1337 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
1338 - If the controller claimed responsibility for a stream, but that
1339 stream never finished making its connection, it would live
1340 forever in circuit_wait state. Now we close it after SocksTimeout
1341 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
1342 - Drop begin cells to a hidden service if they come from the middle
1343 of a circuit. Patch from lark.
1344 - When we erroneously receive two EXTEND cells for the same circuit
1345 ID on the same connection, drop the second. Patch from lark.
1346 - Fix a crash that occurs on exit nodes when a nameserver request
1347 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
1348 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
1350 - Do not assume that a stack-allocated character array will be
1351 64-bit aligned on platforms that demand that uint64_t access is
1352 aligned. Possible fix for bug 604.
1353 - Parse dates and IPv4 addresses in a locale- and libc-independent
1354 manner, to avoid platform-dependent behavior on malformed input.
1355 - Build correctly when configured to build outside the main source
1356 path. Patch from Michael Gold.
1357 - We were already rejecting relay begin cells with destination port
1358 of 0. Now also reject extend cells with destination port or address
1359 of 0. Suggested by lark.
1361 o Minor bugfixes (on 0.2.1.x):
1362 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
1363 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
1364 - If we're an exit node, scrub the IP address to which we are exiting
1365 in the logs. Bugfix on 0.2.1.8-alpha.
1368 - On Linux, use the prctl call to re-enable core dumps when the user
1370 - New controller event NEWCONSENSUS that lists the networkstatus
1371 lines for every recommended relay. Now controllers like Torflow
1372 can keep up-to-date on which relays they should be using.
1373 - Update to the "February 26 2009" ip-to-country file.
1376 Changes in version 0.2.0.34 - 2009-02-08
1377 Tor 0.2.0.34 features several more security-related fixes. You should
1378 upgrade, especially if you run an exit relay (remote crash) or a
1379 directory authority (remote infinite loop), or you're on an older
1380 (pre-XP) or not-recently-patched Windows (remote exploit).
1382 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
1383 have many known flaws, and nobody should be using them. You should
1384 upgrade. If you're using a Linux or BSD and its packages are obsolete,
1385 stop using those packages and upgrade anyway.
1388 - Fix an infinite-loop bug on handling corrupt votes under certain
1389 circumstances. Bugfix on 0.2.0.8-alpha.
1390 - Fix a temporary DoS vulnerability that could be performed by
1391 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
1392 - Avoid a potential crash on exit nodes when processing malformed
1393 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
1394 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
1395 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
1398 - Fix compilation on systems where time_t is a 64-bit integer.
1399 Patch from Matthias Drochner.
1400 - Don't consider expiring already-closed client connections. Fixes
1401 bug 893. Bugfix on 0.0.2pre20.
1404 Changes in version 0.2.1.12-alpha - 2009-02-08
1405 Tor 0.2.1.12-alpha features several more security-related fixes. You
1406 should upgrade, especially if you run an exit relay (remote crash) or
1407 a directory authority (remote infinite loop), or you're on an older
1408 (pre-XP) or not-recently-patched Windows (remote exploit). It also
1409 includes a big pile of minor bugfixes and cleanups.
1412 - Fix an infinite-loop bug on handling corrupt votes under certain
1413 circumstances. Bugfix on 0.2.0.8-alpha.
1414 - Fix a temporary DoS vulnerability that could be performed by
1415 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
1416 - Avoid a potential crash on exit nodes when processing malformed
1417 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
1420 - Let controllers actually ask for the "clients_seen" event for
1421 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
1422 reported by Matt Edman.
1423 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
1425 - Fix a bug in address parsing that was preventing bridges or hidden
1426 service targets from being at IPv6 addresses.
1427 - Solve a bug that kept hardware crypto acceleration from getting
1428 enabled when accounting was turned on. Fixes bug 907. Bugfix on
1430 - Remove a bash-ism from configure.in to build properly on non-Linux
1431 platforms. Bugfix on 0.2.1.1-alpha.
1432 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
1433 headers. Bugfix on 0.2.0.10-alpha.
1434 - Don't consider expiring already-closed client connections. Fixes
1435 bug 893. Bugfix on 0.0.2pre20.
1436 - Fix another interesting corner-case of bug 891 spotted by rovv:
1437 Previously, if two hosts had different amounts of clock drift, and
1438 one of them created a new connection with just the wrong timing,
1439 the other might decide to deprecate the new connection erroneously.
1440 Bugfix on 0.1.1.13-alpha.
1441 - Resolve a very rare crash bug that could occur when the user forced
1442 a nameserver reconfiguration during the middle of a nameserver
1443 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
1444 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
1445 Bugfix on 0.2.1.7-alpha.
1446 - If we're using bridges and our network goes away, be more willing
1447 to forgive our bridges and try again when we get an application
1448 request. Bugfix on 0.2.0.x.
1451 - Support platforms where time_t is 64 bits long. (Congratulations,
1452 NetBSD!) Patch from Matthias Drochner.
1453 - Add a 'getinfo status/clients-seen' controller command, in case
1454 controllers want to hear clients_seen events but connect late.
1457 - Disable GCC's strict alias optimization by default, to avoid the
1458 likelihood of its introducing subtle bugs whenever our code violates
1459 the letter of C99's alias rules.
1462 Changes in version 0.2.0.33 - 2009-01-21
1463 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
1464 useful to users. It also finally fixes a bug where a relay or client
1465 that's been off for many days would take a long time to bootstrap.
1467 This update also fixes an important security-related bug reported by
1468 Ilja van Sprundel. You should upgrade. (We'll send out more details
1469 about the bug once people have had some time to upgrade.)
1472 - Fix a heap-corruption bug that may be remotely triggerable on
1473 some platforms. Reported by Ilja van Sprundel.
1476 - When a stream at an exit relay is in state "resolving" or
1477 "connecting" and it receives an "end" relay cell, the exit relay
1478 would silently ignore the end cell and not close the stream. If
1479 the client never closes the circuit, then the exit relay never
1480 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
1482 - When sending CREATED cells back for a given circuit, use a 64-bit
1483 connection ID to find the right connection, rather than an addr:port
1484 combination. Now that we can have multiple OR connections between
1485 the same ORs, it is no longer possible to use addr:port to uniquely
1486 identify a connection.
1487 - Bridge relays that had DirPort set to 0 would stop fetching
1488 descriptors shortly after startup, and then briefly resume
1489 after a new bandwidth test and/or after publishing a new bridge
1490 descriptor. Bridge users that try to bootstrap from them would
1491 get a recent networkstatus but would get descriptors from up to
1492 18 hours earlier, meaning most of the descriptors were obsolete
1493 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
1494 - Prevent bridge relays from serving their 'extrainfo' document
1495 to anybody who asks, now that extrainfo docs include potentially
1496 sensitive aggregated client geoip summaries. Bugfix on
1498 - If the cached networkstatus consensus is more than five days old,
1499 discard it rather than trying to use it. In theory it could be
1500 useful because it lists alternate directory mirrors, but in practice
1501 it just means we spend many minutes trying directory mirrors that
1502 are long gone from the network. Also discard router descriptors as
1503 we load them if they are more than five days old, since the onion
1504 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
1507 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
1508 could make gcc generate non-functional binary search code. Bugfix
1510 - Build correctly on platforms without socklen_t.
1511 - Compile without warnings on solaris.
1512 - Avoid potential crash on internal error during signature collection.
1513 Fixes bug 864. Patch from rovv.
1514 - Correct handling of possible malformed authority signing key
1515 certificates with internal signature types. Fixes bug 880.
1516 Bugfix on 0.2.0.3-alpha.
1517 - Fix a hard-to-trigger resource leak when logging credential status.
1519 - When we can't initialize DNS because the network is down, do not
1520 automatically stop Tor from starting. Instead, we retry failed
1521 dns_init() every 10 minutes, and change the exit policy to reject
1522 *:* until one succeeds. Fixes bug 691.
1523 - Use 64 bits instead of 32 bits for connection identifiers used with
1524 the controller protocol, to greatly reduce risk of identifier reuse.
1525 - When we're choosing an exit node for a circuit, and we have
1526 no pending streams, choose a good general exit rather than one that
1527 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
1528 - Fix another case of assuming, when a specific exit is requested,
1529 that we know more than the user about what hosts it allows.
1530 Fixes one case of bug 752. Patch from rovv.
1531 - Clip the MaxCircuitDirtiness config option to a minimum of 10
1532 seconds. Warn the user if lower values are given in the
1533 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
1534 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
1535 user if lower values are given in the configuration. Bugfix on
1536 0.1.1.17-rc. Patch by Sebastian.
1537 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
1538 the cache because we already had a v0 descriptor with the same ID.
1539 Bugfix on 0.2.0.18-alpha.
1540 - Fix a race condition when freeing keys shared between main thread
1541 and CPU workers that could result in a memory leak. Bugfix on
1542 0.1.0.1-rc. Fixes bug 889.
1543 - Send a valid END cell back when a client tries to connect to a
1544 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
1545 840. Patch from rovv.
1546 - Check which hops rendezvous stream cells are associated with to
1547 prevent possible guess-the-streamid injection attacks from
1548 intermediate hops. Fixes another case of bug 446. Based on patch
1550 - If a broken client asks a non-exit router to connect somewhere,
1551 do not even do the DNS lookup before rejecting the connection.
1552 Fixes another case of bug 619. Patch from rovv.
1553 - When a relay gets a create cell it can't decrypt (e.g. because it's
1554 using the wrong onion key), we were dropping it and letting the
1555 client time out. Now actually answer with a destroy cell. Fixes
1556 bug 904. Bugfix on 0.0.2pre8.
1558 o Minor bugfixes (hidden services):
1559 - Do not throw away existing introduction points on SIGHUP. Bugfix on
1560 0.0.6pre1. Patch by Karsten. Fixes bug 874.
1563 - Report the case where all signatures in a detached set are rejected
1564 differently than the case where there is an error handling the
1566 - When we realize that another process has modified our cached
1567 descriptors, print out a more useful error message rather than
1568 triggering an assertion. Fixes bug 885. Patch from Karsten.
1569 - Implement the 0x20 hack to better resist DNS poisoning: set the
1570 case on outgoing DNS requests randomly, and reject responses that do
1571 not match the case correctly. This logic can be disabled with the
1572 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
1573 of servers that do not reliably preserve case in replies. See
1574 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
1576 - Check DNS replies for more matching fields to better resist DNS
1578 - Never use OpenSSL compression: it wastes RAM and CPU trying to
1579 compress cells, which are basically all encrypted, compressed, or
1583 Changes in version 0.2.1.11-alpha - 2009-01-20
1584 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
1585 week it will take a long time to bootstrap again" bug. It also fixes
1586 an important security-related bug reported by Ilja van Sprundel. You
1587 should upgrade. (We'll send out more details about the bug once people
1588 have had some time to upgrade.)
1591 - Fix a heap-corruption bug that may be remotely triggerable on
1592 some platforms. Reported by Ilja van Sprundel.
1595 - Discard router descriptors as we load them if they are more than
1596 five days old. Otherwise if Tor is off for a long time and then
1597 starts with cached descriptors, it will try to use the onion
1598 keys in those obsolete descriptors when building circuits. Bugfix
1599 on 0.2.0.x. Fixes bug 887.
1602 - Try to make sure that the version of Libevent we're running with
1603 is binary-compatible with the one we built with. May address bug
1605 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
1606 for bug 905. Bugfix on 0.2.1.7-alpha.
1607 - Add a new --enable-local-appdata configuration switch to change
1608 the default location of the datadir on win32 from APPDATA to
1609 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
1610 entirely. Patch from coderman.
1613 - Make outbound DNS packets respect the OutboundBindAddress setting.
1614 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
1615 - When our circuit fails at the first hop (e.g. we get a destroy
1616 cell back), avoid using that OR connection anymore, and also
1617 tell all the one-hop directory requests waiting for it that they
1618 should fail. Bugfix on 0.2.1.3-alpha.
1619 - In the torify(1) manpage, mention that tsocks will leak your
1623 Changes in version 0.2.1.10-alpha - 2009-01-06
1624 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
1625 would make the bridge relay not so useful if it had DirPort set to 0,
1626 and one that could let an attacker learn a little bit of information
1627 about the bridge's users), and a bug that would cause your Tor relay
1628 to ignore a circuit create request it can't decrypt (rather than reply
1629 with an error). It also fixes a wide variety of other bugs.
1632 - If the cached networkstatus consensus is more than five days old,
1633 discard it rather than trying to use it. In theory it could
1634 be useful because it lists alternate directory mirrors, but in
1635 practice it just means we spend many minutes trying directory
1636 mirrors that are long gone from the network. Helps bug 887 a bit;
1638 - Bridge relays that had DirPort set to 0 would stop fetching
1639 descriptors shortly after startup, and then briefly resume
1640 after a new bandwidth test and/or after publishing a new bridge
1641 descriptor. Bridge users that try to bootstrap from them would
1642 get a recent networkstatus but would get descriptors from up to
1643 18 hours earlier, meaning most of the descriptors were obsolete
1644 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
1645 - Prevent bridge relays from serving their 'extrainfo' document
1646 to anybody who asks, now that extrainfo docs include potentially
1647 sensitive aggregated client geoip summaries. Bugfix on
1651 - New controller event "clients_seen" to report a geoip-based summary
1652 of which countries we've seen clients from recently. Now controllers
1653 like Vidalia can show bridge operators that they're actually making
1655 - Build correctly against versions of OpenSSL 0.9.8 or later built
1656 without support for deprecated functions.
1657 - Update to the "December 19 2008" ip-to-country file.
1659 o Minor bugfixes (on 0.2.0.x):
1660 - Authorities now vote for the Stable flag for any router whose
1661 weighted MTBF is at least 5 days, regardless of the mean MTBF.
1662 - Do not remove routers as too old if we do not have any consensus
1663 document. Bugfix on 0.2.0.7-alpha.
1664 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
1665 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
1666 - When an exit relay resolves a stream address to a local IP address,
1667 do not just keep retrying that same exit relay over and
1668 over. Instead, just close the stream. Addresses bug 872. Bugfix
1669 on 0.2.0.32. Patch from rovv.
1670 - If a hidden service sends us an END cell, do not consider
1671 retrying the connection; just close it. Patch from rovv.
1672 - When we made bridge authorities stop serving bridge descriptors over
1673 unencrypted links, we also broke DirPort reachability testing for
1674 bridges. So bridges with a non-zero DirPort were printing spurious
1675 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
1676 - When a relay gets a create cell it can't decrypt (e.g. because it's
1677 using the wrong onion key), we were dropping it and letting the
1678 client time out. Now actually answer with a destroy cell. Fixes
1679 bug 904. Bugfix on 0.0.2pre8.
1680 - Squeeze 2-5% out of client performance (according to oprofile) by
1681 improving the implementation of some policy-manipulation functions.
1683 o Minor bugfixes (on 0.2.1.x):
1684 - Make get_interface_address() function work properly again; stop
1685 guessing the wrong parts of our address as our address.
1686 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
1687 send on that circuit. Otherwise we might violate the proposal-110
1688 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
1690 - When we're sending non-EXTEND cells to the first hop in a circuit,
1691 for example to use an encrypted directory connection, we don't need
1692 to use RELAY_EARLY cells: the first hop knows what kind of cell
1693 it is, and nobody else can even see the cell type. Conserving
1694 RELAY_EARLY cells makes it easier to cannibalize circuits like
1696 - Stop logging nameserver addresses in reverse order.
1697 - If we are retrying a directory download slowly over and over, do
1698 not automatically give up after the 254th failure. Bugfix on
1700 - Resume reporting accurate "stream end" reasons to the local control
1701 port. They were lost in the changes for Proposal 148. Bugfix on
1704 o Deprecated and removed features:
1705 - The old "tor --version --version" command, which would print out
1706 the subversion "Id" of most of the source files, is now removed. It
1707 turned out to be less useful than we'd expected, and harder to
1710 o Code simplifications and refactoring:
1711 - Change our header file guard macros to be less likely to conflict
1712 with system headers. Adam Langley noticed that we were conflicting
1713 with log.h on Android.
1714 - Tool-assisted documentation cleanup. Nearly every function or
1715 static variable in Tor should have its own documentation now.
1718 Changes in version 0.2.1.9-alpha - 2008-12-25
1719 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
1721 o New directory authorities:
1722 - gabelmoo (the authority run by Karsten Loesing) now has a new
1726 - Never use a connection with a mismatched address to extend a
1727 circuit, unless that connection is canonical. A canonical
1728 connection is one whose address is authenticated by the router's
1729 identity key, either in a NETINFO cell or in a router descriptor.
1730 - Avoid a possible memory corruption bug when receiving hidden service
1731 descriptors. Bugfix on 0.2.1.6-alpha.
1734 - Fix a logic error that would automatically reject all but the first
1735 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
1736 part of bug 813/868. Bug spotted by coderman.
1737 - When a stream at an exit relay is in state "resolving" or
1738 "connecting" and it receives an "end" relay cell, the exit relay
1739 would silently ignore the end cell and not close the stream. If
1740 the client never closes the circuit, then the exit relay never
1741 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
1743 - When we can't initialize DNS because the network is down, do not
1744 automatically stop Tor from starting. Instead, retry failed
1745 dns_init() every 10 minutes, and change the exit policy to reject
1746 *:* until one succeeds. Fixes bug 691.
1749 - Give a better error message when an overzealous init script says
1750 "sudo -u username tor --user username". Makes Bug 882 easier for
1752 - When a directory authority gives us a new guess for our IP address,
1753 log which authority we used. Hopefully this will help us debug
1754 the recent complaints about bad IP address guesses.
1755 - Detect svn revision properly when we're using git-svn.
1756 - Try not to open more than one descriptor-downloading connection
1757 to an authority at once. This should reduce load on directory
1758 authorities. Fixes bug 366.
1759 - Add cross-certification to newly generated certificates, so that
1760 a signing key is enough information to look up a certificate.
1761 Partial implementation of proposal 157.
1762 - Start serving certificates by <identity digest, signing key digest>
1763 pairs. Partial implementation of proposal 157.
1764 - Clients now never report any stream end reason except 'MISC'.
1765 Implements proposal 148.
1766 - On platforms with a maximum syslog string length, truncate syslog
1767 messages to that length ourselves, rather than relying on the
1768 system to do it for us.
1769 - Optimize out calls to time(NULL) that occur for every IO operation,
1770 or for every cell. On systems where time() is a slow syscall,
1771 this fix will be slightly helpful.
1772 - Exit servers can now answer resolve requests for ip6.arpa addresses.
1773 - When we download a descriptor that we then immediately (as
1774 a directory authority) reject, do not retry downloading it right
1775 away. Should save some bandwidth on authorities. Fix for bug
1776 888. Patch by Sebastian Hahn.
1777 - When a download gets us zero good descriptors, do not notify
1778 Tor that new directory information has arrived.
1779 - Avoid some nasty corner cases in the logic for marking connections
1780 as too old or obsolete or noncanonical for circuits. Partial
1783 o Minor features (controller):
1784 - New CONSENSUS_ARRIVED event to note when a new consensus has
1785 been fetched and validated.
1786 - When we realize that another process has modified our cached
1787 descriptors file, print out a more useful error message rather
1788 than triggering an assertion. Fixes bug 885. Patch from Karsten.
1789 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
1790 controllers to prevent SIGHUP from reloading the
1791 configuration. Fixes bug 856.
1794 - Resume using the correct "REASON=" stream when telling the
1795 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
1796 - When a canonical connection appears later in our internal list
1797 than a noncanonical one for a given OR ID, always use the
1798 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
1800 - Clip the MaxCircuitDirtiness config option to a minimum of 10
1801 seconds. Warn the user if lower values are given in the
1802 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
1803 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
1804 user if lower values are given in the configuration. Bugfix on
1805 0.1.1.17-rc. Patch by Sebastian.
1806 - Fix a race condition when freeing keys shared between main thread
1807 and CPU workers that could result in a memory leak. Bugfix on
1808 0.1.0.1-rc. Fixes bug 889.
1810 o Minor bugfixes (hidden services):
1811 - Do not throw away existing introduction points on SIGHUP (bugfix on
1812 0.0.6pre1); also, do not stall hidden services because we're
1813 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
1814 by John Brooks. Patch by Karsten. Fixes bug 874.
1815 - Fix a memory leak when we decline to add a v2 rendezvous
1816 descriptor to the cache because we already had a v0 descriptor
1817 with the same ID. Bugfix on 0.2.0.18-alpha.
1819 o Deprecated and removed features:
1820 - RedirectExits has been removed. It was deprecated since
1822 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
1823 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
1824 - Cell pools are now always enabled; --disable-cell-pools is ignored.
1826 o Code simplifications and refactoring:
1827 - Rename the confusing or_is_obsolete field to the more appropriate
1828 is_bad_for_new_circs, and move it to or_connection_t where it
1830 - Move edge-only flags from connection_t to edge_connection_t: not
1831 only is this better coding, but on machines of plausible alignment,
1832 it should save 4-8 bytes per connection_t. "Every little bit helps."
1833 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
1834 for consistency; keep old option working for backward compatibility.
1835 - Simplify the code for finding connections to use for a circuit.
1838 Changes in version 0.2.1.8-alpha - 2008-12-08
1839 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
1840 builds better on unusual platforms like Solaris and old OS X, and
1841 fixes a variety of other issues.
1844 - New DirPortFrontPage option that takes an html file and publishes
1845 it as "/" on the DirPort. Now relay operators can provide a
1846 disclaimer without needing to set up a separate webserver. There's
1847 a sample disclaimer in contrib/tor-exit-notice.html.
1850 - When the client is choosing entry guards, now it selects at most
1851 one guard from a given relay family. Otherwise we could end up with
1852 all of our entry points into the network run by the same operator.
1853 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
1856 - Fix a DOS opportunity during the voting signature collection process
1857 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
1858 - Fix a possible segfault when establishing an exit connection. Bugfix
1862 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
1864 - Made Tor a little less aggressive about deleting expired
1865 certificates. Partial fix for bug 854.
1866 - Stop doing unaligned memory access that generated bus errors on
1867 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
1868 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
1869 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
1870 - Make USR2 log-level switch take effect immediately. Bugfix on
1872 - If one win32 nameserver fails to get added, continue adding the
1873 rest, and don't automatically fail.
1874 - Use fcntl() for locking when flock() is not available. Should fix
1875 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
1876 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
1877 could make gcc generate non-functional binary search code. Bugfix
1879 - Build correctly on platforms without socklen_t.
1880 - Avoid potential crash on internal error during signature collection.
1881 Fixes bug 864. Patch from rovv.
1882 - Do not use C's stdio library for writing to log files. This will
1883 improve logging performance by a minute amount, and will stop
1884 leaking fds when our disk is full. Fixes bug 861.
1885 - Stop erroneous use of O_APPEND in cases where we did not in fact
1886 want to re-seek to the end of a file before every last write().
1887 - Correct handling of possible malformed authority signing key
1888 certificates with internal signature types. Fixes bug 880. Bugfix
1890 - Fix a hard-to-trigger resource leak when logging credential status.
1894 - Directory mirrors no longer fetch the v1 directory or
1895 running-routers files. They are obsolete, and nobody asks for them
1896 anymore. This is the first step to making v1 authorities obsolete.
1898 o Minor features (controller):
1899 - Return circuit purposes in response to GETINFO circuit-status. Fixes
1903 Changes in version 0.2.0.32 - 2008-11-20
1904 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
1905 packages (and maybe other packages) noticed by Theo de Raadt, fixes
1906 a smaller security flaw that might allow an attacker to access local
1907 services, further improves hidden service performance, and fixes a
1908 variety of other issues.
1911 - The "User" and "Group" config options did not clear the
1912 supplementary group entries for the Tor process. The "User" option
1913 is now more robust, and we now set the groups to the specified
1914 user's primary group. The "Group" option is now ignored. For more
1915 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
1916 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
1917 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
1918 - The "ClientDNSRejectInternalAddresses" config option wasn't being
1919 consistently obeyed: if an exit relay refuses a stream because its
1920 exit policy doesn't allow it, we would remember what IP address
1921 the relay said the destination address resolves to, even if it's
1922 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
1925 - Fix a DOS opportunity during the voting signature collection process
1926 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
1928 o Major bugfixes (hidden services):
1929 - When fetching v0 and v2 rendezvous service descriptors in parallel,
1930 we were failing the whole hidden service request when the v0
1931 descriptor fetch fails, even if the v2 fetch is still pending and
1932 might succeed. Similarly, if the last v2 fetch fails, we were
1933 failing the whole hidden service request even if a v0 fetch is
1934 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
1935 - When extending a circuit to a hidden service directory to upload a
1936 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
1937 requests failed, because the router descriptor has not been
1938 downloaded yet. In these cases, do not attempt to upload the
1939 rendezvous descriptor, but wait until the router descriptor is
1940 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
1941 descriptor from a hidden service directory for which the router
1942 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
1946 - Fix several infrequent memory leaks spotted by Coverity.
1947 - When testing for libevent functions, set the LDFLAGS variable
1948 correctly. Found by Riastradh.
1949 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
1950 bootstrapping with tunneled directory connections. Bugfix on
1951 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
1952 - When asked to connect to A.B.exit:80, if we don't know the IP for A
1953 and we know that server B rejects most-but-not all connections to
1954 port 80, we would previously reject the connection. Now, we assume
1955 the user knows what they were asking for. Fixes bug 752. Bugfix
1956 on 0.0.9rc5. Diagnosed by BarkerJr.
1957 - If we overrun our per-second write limits a little, count this as
1958 having used up our write allocation for the second, and choke
1959 outgoing directory writes. Previously, we had only counted this when
1960 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
1961 Bugfix on 0.2.0.x (??).
1962 - Remove the old v2 directory authority 'lefkada' from the default
1963 list. It has been gone for many months.
1964 - Stop doing unaligned memory access that generated bus errors on
1965 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
1966 - Make USR2 log-level switch take effect immediately. Bugfix on
1969 o Minor bugfixes (controller):
1970 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
1971 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
1974 Changes in version 0.2.1.7-alpha - 2008-11-08
1975 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
1976 packages (and maybe other packages) noticed by Theo de Raadt, fixes
1977 a smaller security flaw that might allow an attacker to access local
1978 services, adds better defense against DNS poisoning attacks on exit
1979 relays, further improves hidden service performance, and fixes a
1980 variety of other issues.
1983 - The "ClientDNSRejectInternalAddresses" config option wasn't being
1984 consistently obeyed: if an exit relay refuses a stream because its
1985 exit policy doesn't allow it, we would remember what IP address
1986 the relay said the destination address resolves to, even if it's
1987 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
1988 - The "User" and "Group" config options did not clear the
1989 supplementary group entries for the Tor process. The "User" option
1990 is now more robust, and we now set the groups to the specified
1991 user's primary group. The "Group" option is now ignored. For more
1992 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
1993 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
1994 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
1995 - Do not use or believe expired v3 authority certificates. Patch
1996 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
1999 - Now NodeFamily and MyFamily config options allow spaces in
2000 identity fingerprints, so it's easier to paste them in.
2001 Suggested by Lucky Green.
2002 - Implement the 0x20 hack to better resist DNS poisoning: set the
2003 case on outgoing DNS requests randomly, and reject responses that do
2004 not match the case correctly. This logic can be disabled with the
2005 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
2006 of servers that do not reliably preserve case in replies. See
2007 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
2009 - Preserve case in replies to DNSPort requests in order to support
2010 the 0x20 hack for resisting DNS poisoning attacks.
2012 o Hidden service performance improvements:
2013 - When the client launches an introduction circuit, retry with a
2014 new circuit after 30 seconds rather than 60 seconds.
2015 - Launch a second client-side introduction circuit in parallel
2016 after a delay of 15 seconds (based on work by Christian Wilms).
2017 - Hidden services start out building five intro circuits rather
2018 than three, and when the first three finish they publish a service
2019 descriptor using those. Now we publish our service descriptor much
2020 faster after restart.
2023 - Minor fix in the warning messages when you're having problems
2024 bootstrapping; also, be more forgiving of bootstrap problems when
2025 we're still making incremental progress on a given bootstrap phase.
2026 - When we're choosing an exit node for a circuit, and we have
2027 no pending streams, choose a good general exit rather than one that
2028 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
2029 - Send a valid END cell back when a client tries to connect to a
2030 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
2031 840. Patch from rovv.
2032 - If a broken client asks a non-exit router to connect somewhere,
2033 do not even do the DNS lookup before rejecting the connection.
2034 Fixes another case of bug 619. Patch from rovv.
2035 - Fix another case of assuming, when a specific exit is requested,
2036 that we know more than the user about what hosts it allows.
2037 Fixes another case of bug 752. Patch from rovv.
2038 - Check which hops rendezvous stream cells are associated with to
2039 prevent possible guess-the-streamid injection attacks from
2040 intermediate hops. Fixes another case of bug 446. Based on patch
2042 - Avoid using a negative right-shift when comparing 32-bit
2043 addresses. Possible fix for bug 845 and bug 811.
2044 - Make the assert_circuit_ok() function work correctly on circuits that
2045 have already been marked for close.
2046 - Fix read-off-the-end-of-string error in unit tests when decoding
2047 introduction points.
2048 - Fix uninitialized size field for memory area allocation: may improve
2049 memory performance during directory parsing.
2050 - Treat duplicate certificate fetches as failures, so that we do
2051 not try to re-fetch an expired certificate over and over and over.
2052 - Do not say we're fetching a certificate when we'll in fact skip it
2053 because of a pending download.
2056 Changes in version 0.2.1.6-alpha - 2008-09-30
2057 Tor 0.2.1.6-alpha further improves performance and robustness of
2058 hidden services, starts work on supporting per-country relay selection,
2059 and fixes a variety of smaller issues.
2062 - Implement proposal 121: make it possible to build hidden services
2063 that only certain clients are allowed to connect to. This is
2064 enforced at several points, so that unauthorized clients are unable
2065 to send INTRODUCE cells to the service, or even (depending on the
2066 type of authentication) to learn introduction points. This feature
2067 raises the bar for certain kinds of active attacks against hidden
2068 services. Code by Karsten Loesing.
2069 - Relays now store and serve v2 hidden service descriptors by default,
2070 i.e., the new default value for HidServDirectoryV2 is 1. This is
2071 the last step in proposal 114, which aims to make hidden service
2072 lookups more reliable.
2073 - Start work to allow node restrictions to include country codes. The
2074 syntax to exclude nodes in a country with country code XX is
2075 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
2076 refinement to decide what config options should take priority if
2077 you ask to both use a particular node and exclude it.
2078 - Allow ExitNodes list to include IP ranges and country codes, just
2079 like the Exclude*Nodes lists. Patch from Robert Hogan.
2082 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
2083 Tor to fail to start if you had it configured to use a bridge
2084 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
2085 - When extending a circuit to a hidden service directory to upload a
2086 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
2087 requests failed, because the router descriptor had not been
2088 downloaded yet. In these cases, we now wait until the router
2089 descriptor is downloaded, and then retry. Likewise, clients
2090 now skip over a hidden service directory if they don't yet have
2091 its router descriptor, rather than futilely requesting it and
2092 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
2094 - When fetching v0 and v2 rendezvous service descriptors in parallel,
2095 we were failing the whole hidden service request when the v0
2096 descriptor fetch fails, even if the v2 fetch is still pending and
2097 might succeed. Similarly, if the last v2 fetch fails, we were
2098 failing the whole hidden service request even if a v0 fetch is
2099 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
2100 - DNS replies need to have names matching their requests, but
2101 these names should be in the questions section, not necessarily
2102 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
2105 - Update to the "September 1 2008" ip-to-country file.
2106 - Allow ports 465 and 587 in the default exit policy again. We had
2107 rejected them in 0.1.0.15, because back in 2005 they were commonly
2108 misconfigured and ended up as spam targets. We hear they are better
2109 locked down these days.
2110 - Use a lockfile to make sure that two Tor processes are not
2111 simultaneously running with the same datadir.
2112 - Serve the latest v3 networkstatus consensus via the control
2113 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
2114 - Better logging about stability/reliability calculations on directory
2116 - Drop the requirement to have an open dir port for storing and
2117 serving v2 hidden service descriptors.
2118 - Directory authorities now serve a /tor/dbg-stability.txt URL to
2119 help debug WFU and MTBF calculations.
2120 - Implement most of Proposal 152: allow specialized servers to permit
2121 single-hop circuits, and clients to use those servers to build
2122 single-hop circuits when using a specialized controller. Patch
2123 from Josh Albrecht. Resolves feature request 768.
2124 - Add a -p option to tor-resolve for specifying the SOCKS port: some
2125 people find host:port too confusing.
2126 - Make TrackHostExit mappings expire a while after their last use, not
2127 after their creation. Patch from Robert Hogan.
2128 - Provide circuit purposes along with circuit events to the controller.
2131 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
2133 - Fixed some memory leaks -- some quite frequent, some almost
2134 impossible to trigger -- based on results from Coverity.
2135 - When testing for libevent functions, set the LDFLAGS variable
2136 correctly. Found by Riastradh.
2137 - Fix an assertion bug in parsing policy-related options; possible fix
2139 - Catch and report a few more bootstrapping failure cases when Tor
2140 fails to establish a TCP connection. Cleanup on 0.2.1.x.
2141 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
2142 bootstrapping with tunneled directory connections. Bugfix on
2143 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
2144 - When asked to connect to A.B.exit:80, if we don't know the IP for A
2145 and we know that server B rejects most-but-not all connections to
2146 port 80, we would previously reject the connection. Now, we assume
2147 the user knows what they were asking for. Fixes bug 752. Bugfix
2148 on 0.0.9rc5. Diagnosed by BarkerJr.
2149 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
2150 service directories if they have no advertised dir port. Bugfix
2152 - If we overrun our per-second write limits a little, count this as
2153 having used up our write allocation for the second, and choke
2154 outgoing directory writes. Previously, we had only counted this when
2155 we had met our limits precisely. Fixes bug 824. Patch by rovv.
2156 Bugfix on 0.2.0.x (??).
2157 - Avoid a "0 divided by 0" calculation when calculating router uptime
2158 at directory authorities. Bugfix on 0.2.0.8-alpha.
2159 - Make DNS resolved controller events into "CLOSED", not
2160 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
2162 - Fix a bug where an unreachable relay would establish enough
2163 reachability testing circuits to do a bandwidth test -- if
2164 we already have a connection to the middle hop of the testing
2165 circuit, then it could establish the last hop by using the existing
2166 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
2167 circuits no longer use entry guards in 0.2.1.3-alpha.
2168 - If we have correct permissions on $datadir, we complain to stdout
2169 and fail to start. But dangerous permissions on
2170 $datadir/cached-status/ would cause us to open a log and complain
2171 there. Now complain to stdout and fail to start in both cases. Fixes
2172 bug 820, reported by seeess.
2173 - Remove the old v2 directory authority 'lefkada' from the default
2174 list. It has been gone for many months.
2176 o Code simplifications and refactoring:
2177 - Revise the connection_new functions so that a more typesafe variant
2178 exists. This will work better with Coverity, and let us find any
2179 actual mistakes we're making here.
2180 - Refactor unit testing logic so that dmalloc can be used sensibly
2181 with unit tests to check for memory leaks.
2182 - Move all hidden-service related fields from connection and circuit
2183 structure to substructures: this way they won't eat so much memory.
2186 Changes in version 0.2.0.31 - 2008-09-03
2187 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
2188 a big bug we're seeing where in rare cases traffic from one Tor stream
2189 gets mixed into another stream, and fixes a variety of smaller issues.
2192 - Make sure that two circuits can never exist on the same connection
2193 with the same circuit ID, even if one is marked for close. This
2194 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
2195 - Relays now reject risky extend cells: if the extend cell includes
2196 a digest of all zeroes, or asks to extend back to the relay that
2197 sent the extend cell, tear down the circuit. Ideas suggested
2199 - If not enough of our entry guards are available so we add a new
2200 one, we might use the new one even if it overlapped with the
2201 current circuit's exit relay (or its family). Anonymity bugfix
2202 pointed out by rovv.
2205 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
2206 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
2207 - Correctly detect the presence of the linux/netfilter_ipv4.h header
2208 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
2209 - Pick size of default geoip filename string correctly on windows.
2210 Fixes bug 806. Bugfix on 0.2.0.30.
2211 - Make the autoconf script accept the obsolete --with-ssl-dir
2212 option as an alias for the actually-working --with-openssl-dir
2213 option. Fix the help documentation to recommend --with-openssl-dir.
2214 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
2215 - When using the TransPort option on OpenBSD, and using the User
2216 option to change UID and drop privileges, make sure to open
2217 /dev/pf before dropping privileges. Fixes bug 782. Patch from
2218 Christopher Davis. Bugfix on 0.1.2.1-alpha.
2219 - Try to attach connections immediately upon receiving a RENDEZVOUS2
2220 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
2221 on the client side when connecting to a hidden service. Bugfix
2222 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
2223 - When closing an application-side connection because its circuit is
2224 getting torn down, generate the stream event correctly. Bugfix on
2225 0.1.2.x. Anonymous patch.
2228 Changes in version 0.2.1.5-alpha - 2008-08-31
2229 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
2230 in a lot of the infrastructure for adding authorization to hidden
2231 services, lays the groundwork for having clients read their load
2232 balancing information out of the networkstatus consensus rather than
2233 the individual router descriptors, addresses two potential anonymity
2234 issues, and fixes a variety of smaller issues.
2237 - Convert many internal address representations to optionally hold
2239 - Generate and accept IPv6 addresses in many protocol elements.
2240 - Make resolver code handle nameservers located at ipv6 addresses.
2241 - Begin implementation of proposal 121 ("Client authorization for
2242 hidden services"): configure hidden services with client
2243 authorization, publish descriptors for them, and configure
2244 authorization data for hidden services at clients. The next
2245 step is to actually access hidden services that perform client
2247 - More progress toward proposal 141: Network status consensus
2248 documents and votes now contain bandwidth information for each
2249 router and a summary of that router's exit policy. Eventually this
2250 will be used by clients so that they do not have to download every
2251 known descriptor before building circuits.
2253 o Major bugfixes (on 0.2.0.x and before):
2254 - When sending CREATED cells back for a given circuit, use a 64-bit
2255 connection ID to find the right connection, rather than an addr:port
2256 combination. Now that we can have multiple OR connections between
2257 the same ORs, it is no longer possible to use addr:port to uniquely
2258 identify a connection.
2259 - Relays now reject risky extend cells: if the extend cell includes
2260 a digest of all zeroes, or asks to extend back to the relay that
2261 sent the extend cell, tear down the circuit. Ideas suggested
2263 - If not enough of our entry guards are available so we add a new
2264 one, we might use the new one even if it overlapped with the
2265 current circuit's exit relay (or its family). Anonymity bugfix
2266 pointed out by rovv.
2269 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
2270 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
2271 - When using the TransPort option on OpenBSD, and using the User
2272 option to change UID and drop privileges, make sure to open /dev/pf
2273 before dropping privileges. Fixes bug 782. Patch from Christopher
2274 Davis. Bugfix on 0.1.2.1-alpha.
2275 - Correctly detect the presence of the linux/netfilter_ipv4.h header
2276 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
2277 - Add a missing safe_str() call for a debug log message.
2278 - Use 64 bits instead of 32 bits for connection identifiers used with
2279 the controller protocol, to greatly reduce risk of identifier reuse.
2280 - Make the autoconf script accept the obsolete --with-ssl-dir
2281 option as an alias for the actually-working --with-openssl-dir
2282 option. Fix the help documentation to recommend --with-openssl-dir.
2283 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
2286 - Rate-limit too-many-sockets messages: when they happen, they happen
2287 a lot. Resolves bug 748.
2288 - Resist DNS poisoning a little better by making sure that names in
2289 answer sections match.
2290 - Print the SOCKS5 error message string as well as the error code
2291 when a tor-resolve request fails. Patch from Jacob.
2294 Changes in version 0.2.1.4-alpha - 2008-08-04
2295 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
2298 - The address part of exit policies was not correctly written
2299 to router descriptors. This generated router descriptors that failed
2300 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
2302 - Tor triggered a false assert when extending a circuit to a relay
2303 but we already have a connection open to that relay. Noticed by
2304 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
2307 - Fix a hidden service logging bug: in some edge cases, the router
2308 descriptor of a previously picked introduction point becomes
2309 obsolete and we need to give up on it rather than continually
2310 complaining that it has become obsolete. Observed by xiando. Bugfix
2314 - Take out the TestVia config option, since it was a workaround for
2315 a bug that was fixed in Tor 0.1.1.21.
2318 Changes in version 0.2.1.3-alpha - 2008-08-03
2319 Tor 0.2.1.3-alpha implements most of the pieces to prevent
2320 infinite-length circuit attacks (see proposal 110); fixes a bug that
2321 might cause exit relays to corrupt streams they send back; allows
2322 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
2323 ExcludeExitNodes config options; and fixes a big pile of bugs.
2325 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
2326 - Send a bootstrap problem "warn" event on the first problem if the
2327 reason is NO_ROUTE (that is, our network is down).
2330 - Implement most of proposal 110: The first K cells to be sent
2331 along a circuit are marked as special "early" cells; only K "early"
2332 cells will be allowed. Once this code is universal, we can block
2333 certain kinds of DOS attack by requiring that EXTEND commands must
2334 be sent using an "early" cell.
2337 - Try to attach connections immediately upon receiving a RENDEZVOUS2
2338 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
2339 on the client side when connecting to a hidden service. Bugfix
2340 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
2341 - Ensure that two circuits can never exist on the same connection
2342 with the same circuit ID, even if one is marked for close. This
2343 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
2346 - When relays do their initial bandwidth measurement, don't limit
2347 to just our entry guards for the test circuits. Otherwise we tend
2348 to have multiple test circuits going through a single entry guard,
2349 which makes our bandwidth test less accurate. Fixes part of bug 654;
2350 patch contributed by Josh Albrecht.
2351 - Add an ExcludeExitNodes option so users can list a set of nodes
2352 that should be be excluded from the exit node position, but
2353 allowed elsewhere. Implements proposal 151.
2354 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
2355 ExcludeNodes and ExcludeExitNodes lists.
2356 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
2357 be more efficient. Formerly it was quadratic in the number of
2358 servers; now it should be linear. Fixes bug 509.
2359 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
2360 and n_conn_id_digest fields into a separate structure that's
2361 only needed when the circuit has not yet attached to an n_conn.
2364 - Change the contrib/tor.logrotate script so it makes the new
2365 logs as "_tor:_tor" rather than the default, which is generally
2366 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
2367 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
2368 warnings (occasionally), but it can also cause the compiler to
2369 eliminate error-checking code. Suggested by Peter Gutmann.
2370 - When a hidden service is giving up on an introduction point candidate
2371 that was not included in the last published rendezvous descriptor,
2372 don't reschedule publication of the next descriptor. Fixes bug 763.
2374 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
2375 HiddenServiceExcludeNodes as obsolete: they never worked properly,
2376 and nobody claims to be using them. Fixes bug 754. Bugfix on
2377 0.1.0.1-rc. Patch from Christian Wilms.
2378 - Fix a small alignment and memory-wasting bug on buffer chunks.
2381 o Minor bugfixes (controller):
2382 - When closing an application-side connection because its circuit
2383 is getting torn down, generate the stream event correctly.
2384 Bugfix on 0.1.2.x. Anonymous patch.
2387 - Remove all backward-compatibility code to support relays running
2388 versions of Tor so old that they no longer work at all on the
2392 Changes in version 0.2.0.30 - 2008-07-15
2394 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
2395 warnings (occasionally), but it can also cause the compiler to
2396 eliminate error-checking code. Suggested by Peter Gutmann.
2399 Changes in version 0.2.0.29-rc - 2008-07-08
2400 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
2401 hidden-service performance bugs, and fixes a bunch of smaller bugs.
2404 - If you have more than one bridge but don't know their keys,
2405 you would only launch a request for the descriptor of the first one
2406 on your list. (Tor considered launching requests for the others, but
2407 found that it already had a connection on the way for $0000...0000
2408 so it didn't open another.) Bugfix on 0.2.0.x.
2409 - If you have more than one bridge but don't know their keys, and the
2410 connection to one of the bridges failed, you would cancel all
2411 pending bridge connections. (After all, they all have the same
2412 digest.) Bugfix on 0.2.0.x.
2413 - When a hidden service was trying to establish an introduction point,
2414 and Tor had built circuits preemptively for such purposes, we
2415 were ignoring all the preemptive circuits and launching a new one
2416 instead. Bugfix on 0.2.0.14-alpha.
2417 - When a hidden service was trying to establish an introduction point,
2418 and Tor *did* manage to reuse one of the preemptively built
2419 circuits, it didn't correctly remember which one it used,
2420 so it asked for another one soon after, until there were no
2421 more preemptive circuits, at which point it launched one from
2422 scratch. Bugfix on 0.0.9.x.
2423 - Make directory servers include the X-Your-Address-Is: http header in
2424 their responses even for begin_dir conns. Now clients who only
2425 ever use begin_dir connections still have a way to learn their IP
2426 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
2429 - Fix a macro/CPP interaction that was confusing some compilers:
2430 some GCCs don't like #if/#endif pairs inside macro arguments.
2432 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
2433 Fixes bug 704; fix from Steven Murdoch.
2434 - When opening /dev/null in finish_daemonize(), do not pass the
2435 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
2436 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
2437 - Correctly detect transparent proxy support on Linux hosts that
2438 require in.h to be included before netfilter_ipv4.h. Patch
2440 - Disallow session resumption attempts during the renegotiation
2441 stage of the v2 handshake protocol. Clients should never be trying
2442 session resumption at this point, but apparently some did, in
2443 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
2444 found by Geoff Goodell.
2447 Changes in version 0.2.1.2-alpha - 2008-06-20
2448 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
2449 make it easier to set up your own private Tor network; fixes several
2450 big bugs with using more than one bridge relay; fixes a big bug with
2451 offering hidden services quickly after Tor starts; and uses a better
2452 API for reporting potential bootstrapping problems to the controller.
2455 - New TestingTorNetwork config option to allow adjustment of
2456 previously constant values that, while reasonable, could slow
2457 bootstrapping. Implements proposal 135. Patch from Karsten.
2460 - If you have more than one bridge but don't know their digests,
2461 you would only learn a request for the descriptor of the first one
2462 on your list. (Tor considered launching requests for the others, but
2463 found that it already had a connection on the way for $0000...0000
2464 so it didn't open another.) Bugfix on 0.2.0.x.
2465 - If you have more than one bridge but don't know their digests,
2466 and the connection to one of the bridges failed, you would cancel
2467 all pending bridge connections. (After all, they all have the
2468 same digest.) Bugfix on 0.2.0.x.
2469 - When establishing a hidden service, introduction points that
2470 originate from cannibalized circuits are completely ignored and not
2471 included in rendezvous service descriptors. This might be another
2472 reason for delay in making a hidden service available. Bugfix
2473 from long ago (0.0.9.x?)
2476 - Allow OpenSSL to use dynamic locks if it wants.
2477 - When building a consensus, do not include routers that are down.
2478 This will cut down 30% to 40% on consensus size. Implements
2480 - In directory authorities' approved-routers files, allow
2481 fingerprints with or without space.
2482 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
2483 controller can query our current bootstrap state in case it attaches
2484 partway through and wants to catch up.
2485 - Send an initial "Starting" bootstrap status event, so we have a
2486 state to start out in.
2489 - Asking for a conditional consensus at .../consensus/<fingerprints>
2490 would crash a dirserver if it did not already have a
2491 consensus. Bugfix on 0.2.1.1-alpha.
2492 - Clean up some macro/CPP interactions: some GCC versions don't like
2493 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
2496 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
2497 - Directory authorities shouldn't complain about bootstrapping
2498 problems just because they do a lot of reachability testing and
2499 some of the connection attempts fail.
2500 - Start sending "count" and "recommendation" key/value pairs in
2501 bootstrap problem status events, so the controller can hear about
2502 problems even before Tor decides they're worth reporting for sure.
2503 - If you're using bridges, generate "bootstrap problem" warnings
2504 as soon as you run out of working bridges, rather than waiting
2505 for ten failures -- which will never happen if you have less than
2507 - If we close our OR connection because there's been a circuit
2508 pending on it for too long, we were telling our bootstrap status
2509 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
2512 Changes in version 0.2.1.1-alpha - 2008-06-13
2513 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
2514 were making the Tor process bloat especially on Linux; makes our TLS
2515 handshake blend in better; sends "bootstrap phase" status events to
2516 the controller, so it can keep the user informed of progress (and
2517 problems) fetching directory information and establishing circuits;
2518 and adds a variety of smaller features.
2521 - More work on making our TLS handshake blend in: modify the list
2522 of ciphers advertised by OpenSSL in client mode to even more
2523 closely resemble a common web browser. We cheat a little so that
2524 we can advertise ciphers that the locally installed OpenSSL doesn't
2526 - Start sending "bootstrap phase" status events to the controller,
2527 so it can keep the user informed of progress fetching directory
2528 information and establishing circuits. Also inform the controller
2529 if we think we're stuck at a particular bootstrap phase. Implements
2531 - Resume using OpenSSL's RAND_poll() for better (and more portable)
2532 cross-platform entropy collection again. We used to use it, then
2533 stopped using it because of a bug that could crash systems that
2534 called RAND_poll when they had a lot of fds open. It looks like the
2535 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
2536 at startup, and to call RAND_poll() when we reseed later only if
2537 we have a non-buggy OpenSSL version.
2540 - When we choose to abandon a new entry guard because we think our
2541 older ones might be better, close any circuits pending on that
2542 new entry guard connection. This fix should make us recover much
2543 faster when our network is down and then comes back. Bugfix on
2544 0.1.2.8-beta; found by lodger.
2546 o Memory fixes and improvements:
2547 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
2548 to avoid unused RAM in buffer chunks and memory pools.
2549 - Speed up parsing and cut down on memory fragmentation by using
2550 stack-style allocations for parsing directory objects. Previously,
2551 this accounted for over 40% of allocations from within Tor's code
2552 on a typical directory cache.
2553 - Use a Bloom filter rather than a digest-based set to track which
2554 descriptors we need to keep around when we're cleaning out old
2555 router descriptors. This speeds up the computation significantly,
2556 and may reduce fragmentation.
2557 - Reduce the default smartlist size from 32 to 16; it turns out that
2558 most smartlists hold around 8-12 elements tops.
2559 - Make dumpstats() log the fullness and size of openssl-internal
2561 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
2562 patch to their OpenSSL, turn it on to save memory on servers. This
2563 patch will (with any luck) get included in a mainline distribution
2565 - Never use OpenSSL compression: it wastes RAM and CPU trying to
2566 compress cells, which are basically all encrypted, compressed,
2570 - Stop reloading the router list from disk for no reason when we
2571 run out of reachable directory mirrors. Once upon a time reloading
2572 it would set the 'is_running' flag back to 1 for them. It hasn't
2573 done that for a long time.
2574 - In very rare situations new hidden service descriptors were
2575 published earlier than 30 seconds after the last change to the
2576 service. (We currently think that a hidden service descriptor
2577 that's been stable for 30 seconds is worth publishing.)
2580 - Allow separate log levels to be configured for different logging
2581 domains. For example, this allows one to log all notices, warnings,
2582 or errors, plus all memory management messages of level debug or
2583 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
2584 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
2585 and stop using a warning that had become unfixably verbose under
2587 - New --hush command-line option similar to --quiet. While --quiet
2588 disables all logging to the console on startup, --hush limits the
2589 output to messages of warning and error severity.
2590 - Servers support a new URL scheme for consensus downloads that
2591 allows the client to specify which authorities are trusted.
2592 The server then only sends the consensus if the client will trust
2593 it. Otherwise a 404 error is sent back. Clients use this
2594 new scheme when the server supports it (meaning it's running
2595 0.2.1.1-alpha or later). Implements proposal 134.
2596 - New configure/torrc options (--enable-geoip-stats,
2597 DirRecordUsageByCountry) to record how many IPs we've served
2598 directory info to in each country code, how many status documents
2599 total we've sent to each country code, and what share of the total
2600 directory requests we should expect to see.
2601 - Use the TLS1 hostname extension to more closely resemble browser
2603 - Lots of new unit tests.
2604 - Add a macro to implement the common pattern of iterating through
2605 two parallel lists in lockstep.
2608 Changes in version 0.2.0.28-rc - 2008-06-13
2609 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
2610 performance bug, and fixes a bunch of smaller bugs.
2613 - Fix a bug where, when we were choosing the 'end stream reason' to
2614 put in our relay end cell that we send to the exit relay, Tor
2615 clients on Windows were sometimes sending the wrong 'reason'. The
2616 anonymity problem is that exit relays may be able to guess whether
2617 the client is running Windows, thus helping partition the anonymity
2618 set. Down the road we should stop sending reasons to exit relays,
2619 or otherwise prevent future versions of this bug.
2622 - While setting up a hidden service, some valid introduction circuits
2623 were overlooked and abandoned. This might be the reason for
2624 the long delay in making a hidden service available. Bugfix on
2628 - Update to the "June 9 2008" ip-to-country file.
2629 - Run 'make test' as part of 'make dist', so we stop releasing so
2630 many development snapshots that fail their unit tests.
2633 - When we're checking if we have enough dir info for each relay
2634 to begin establishing circuits, make sure that we actually have
2635 the descriptor listed in the consensus, not just any descriptor.
2637 - Bridge relays no longer print "xx=0" in their extrainfo document
2638 for every single country code in the geoip db. Bugfix on
2640 - Only warn when we fail to load the geoip file if we were planning to
2641 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
2642 - If we change our MaxAdvertisedBandwidth and then reload torrc,
2643 Tor won't realize it should publish a new relay descriptor. Fixes
2644 bug 688, reported by mfr. Bugfix on 0.1.2.x.
2645 - When we haven't had any application requests lately, don't bother
2646 logging that we have expired a bunch of descriptors. Bugfix
2648 - Make relay cells written on a connection count as non-padding when
2649 tracking how long a connection has been in use. Bugfix on
2650 0.2.0.1-alpha. Spotted by lodger.
2651 - Fix unit tests in 0.2.0.27-rc.
2652 - Fix compile on Windows.
2655 Changes in version 0.2.0.27-rc - 2008-06-03
2656 Tor 0.2.0.27-rc adds a few features we left out of the earlier
2657 release candidates. In particular, we now include an IP-to-country
2658 GeoIP database, so controllers can easily look up what country a
2659 given relay is in, and so bridge relays can give us some sanitized
2660 summaries about which countries are making use of bridges. (See proposal
2661 126-geoip-fetching.txt for details.)
2664 - Include an IP-to-country GeoIP file in the tarball, so bridge
2665 relays can report sanitized summaries of the usage they're seeing.
2668 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
2669 Robert Hogan. Fixes the first part of bug 681.
2670 - Make bridge authorities never serve extrainfo docs.
2671 - Add support to detect Libevent versions in the 1.4.x series
2673 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
2674 - Include a new contrib/tor-exit-notice.html file that exit relay
2675 operators can put on their website to help reduce abuse queries.
2678 - When tunneling an encrypted directory connection, and its first
2679 circuit fails, do not leave it unattached and ask the controller
2680 to deal. Fixes the second part of bug 681.
2681 - Make bridge authorities correctly expire old extrainfo documents
2685 Changes in version 0.2.0.26-rc - 2008-05-13
2686 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
2687 in Debian's OpenSSL packages. All users running any 0.2.0.x version
2688 should upgrade, whether they're running Debian or not.
2690 o Major security fixes:
2691 - Use new V3 directory authority keys on the tor26, gabelmoo, and
2692 moria1 V3 directory authorities. The old keys were generated with
2693 a vulnerable version of Debian's OpenSSL package, and must be
2694 considered compromised. Other authorities' keys were not generated
2695 with an affected version of OpenSSL.
2698 - List authority signatures as "unrecognized" based on DirServer
2699 lines, not on cert cache. Bugfix on 0.2.0.x.
2702 - Add a new V3AuthUseLegacyKey option to make it easier for
2703 authorities to change their identity keys if they have to.
2706 Changes in version 0.2.0.25-rc - 2008-04-23
2707 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
2710 - Remember to initialize threading before initializing logging.
2711 Otherwise, many BSD-family implementations will crash hard on
2712 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
2715 - Authorities correctly free policies on bad servers on
2716 exit. Fixes bug 672. Bugfix on 0.2.0.x.
2719 Changes in version 0.2.0.24-rc - 2008-04-22
2720 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
2721 v3 directory authority, makes relays with dynamic IP addresses and no
2722 DirPort notice more quickly when their IP address changes, fixes a few
2723 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
2725 o New directory authorities:
2726 - Take lefkada out of the list of v3 directory authorities, since
2727 it has been down for months.
2728 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
2732 - Detect address changes more quickly on non-directory mirror
2733 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
2735 o Minor features (security):
2736 - Reject requests for reverse-dns lookup of names that are in
2737 a private address space. Patch from lodger.
2738 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
2741 o Minor bugfixes (crashes):
2742 - Avoid a rare assert that can trigger when Tor doesn't have much
2743 directory information yet and it tries to fetch a v2 hidden
2744 service descriptor. Fixes bug 651, reported by nwf.
2745 - Initialize log mutex before initializing dmalloc. Otherwise,
2746 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
2747 - Use recursive pthread mutexes in order to avoid deadlock when
2748 logging debug-level messages to a controller. Bug spotted by nwf,
2749 bugfix on 0.2.0.16-alpha.
2751 o Minor bugfixes (resource management):
2752 - Keep address policies from leaking memory: start their refcount
2753 at 1, not 2. Bugfix on 0.2.0.16-alpha.
2754 - Free authority certificates on exit, so they don't look like memory
2755 leaks. Bugfix on 0.2.0.19-alpha.
2756 - Free static hashtables for policy maps and for TLS connections on
2757 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
2758 - Avoid allocating extra space when computing consensuses on 64-bit
2759 platforms. Bug spotted by aakova.
2761 o Minor bugfixes (misc):
2762 - Do not read the configuration file when we've only been told to
2763 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
2764 based on patch from Sebastian Hahn.
2765 - Exit relays that are used as a client can now reach themselves
2766 using the .exit notation, rather than just launching an infinite
2767 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
2768 - When attempting to open a logfile fails, tell us why.
2769 - Fix a dumb bug that was preventing us from knowing that we should
2770 preemptively build circuits to handle expected directory requests.
2771 Fixes bug 660. Bugfix on 0.1.2.x.
2772 - Warn less verbosely about clock skew from netinfo cells from
2773 untrusted sources. Fixes bug 663.
2774 - Make controller stream events for DNS requests more consistent,
2775 by adding "new stream" events for DNS requests, and removing
2776 spurious "stream closed" events" for cached reverse resolves.
2777 Patch from mwenge. Fixes bug 646.
2778 - Correctly notify one-hop connections when a circuit build has
2779 failed. Possible fix for bug 669. Found by lodger.
2782 Changes in version 0.2.0.23-rc - 2008-03-24
2783 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
2784 makes bootstrapping faster if the first directory mirror you contact
2785 is down. The bundles also include the new Vidalia 0.1.2 release.
2788 - When a tunneled directory request is made to a directory server
2789 that's down, notice after 30 seconds rather than 120 seconds. Also,
2790 fail any begindir streams that are pending on it, so they can
2791 retry elsewhere. This was causing multi-minute delays on bootstrap.
2794 Changes in version 0.2.0.22-rc - 2008-03-18
2795 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
2796 enables encrypted directory connections by default for non-relays, fixes
2797 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
2798 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
2801 - Enable encrypted directory connections by default for non-relays,
2802 so censor tools that block Tor directory connections based on their
2803 plaintext patterns will no longer work. This means Tor works in
2804 certain censored countries by default again.
2807 - Make sure servers always request certificates from clients during
2808 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
2809 - Do not enter a CPU-eating loop when a connection is closed in
2810 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
2811 diagnosed by lodger; bugfix on 0.2.0.20-rc.
2812 - Fix assertion failure that could occur when a blocked circuit
2813 became unblocked, and it had pending client DNS requests. Bugfix
2814 on 0.2.0.1-alpha. Fixes bug 632.
2816 o Minor bugfixes (on 0.1.2.x):
2817 - Generate "STATUS_SERVER" events rather than misspelled
2818 "STATUS_SEVER" events. Caught by mwenge.
2819 - When counting the number of bytes written on a TLS connection,
2820 look at the BIO actually used for writing to the network, not
2821 at the BIO used (sometimes) to buffer data for the network.
2822 Looking at different BIOs could result in write counts on the
2823 order of ULONG_MAX. Fixes bug 614.
2824 - On Windows, correctly detect errors when listing the contents of
2825 a directory. Fix from lodger.
2827 o Minor bugfixes (on 0.2.0.x):
2828 - Downgrade "sslv3 alert handshake failure" message to INFO.
2829 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
2830 left BandwidthRate and BandwidthBurst at the default, we would be
2831 silently limited by those defaults. Now raise them to match the
2832 RelayBandwidth* values.
2833 - Fix the SVK version detection logic to work correctly on a branch.
2834 - Make --enable-openbsd-malloc work correctly on Linux with alpha
2835 CPUs. Fixes bug 625.
2836 - Logging functions now check that the passed severity is sane.
2837 - Use proper log levels in the testsuite call of
2838 get_interface_address6().
2839 - When using a nonstandard malloc, do not use the platform values for
2840 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
2841 - Make the openbsd malloc code use 8k pages on alpha CPUs and
2843 - Detect mismatched page sizes when using --enable-openbsd-malloc.
2844 - Avoid double-marked-for-close warning when certain kinds of invalid
2845 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
2846 for bug 617. Bugfix on 0.2.0.1-alpha.
2847 - Make sure that the "NULL-means-reject *:*" convention is followed by
2848 all the policy manipulation functions, avoiding some possible crash
2849 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
2850 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
2851 actually works, and doesn't warn about every single reverse lookup.
2852 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
2855 - Only log guard node status when guard node status has changed.
2856 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
2857 make "INFO" 75% less verbose.
2860 Changes in version 0.2.0.21-rc - 2008-03-02
2861 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
2862 makes Tor work well with Vidalia again, fixes a rare assert bug,
2863 and fixes a pair of more minor bugs. The bundles also include Vidalia
2864 0.1.0 and Torbutton 1.1.16.
2867 - The control port should declare that it requires password auth
2868 when HashedControlSessionPassword is set too. Patch from Matt Edman;
2869 bugfix on 0.2.0.20-rc. Fixes bug 615.
2870 - Downgrade assert in connection_buckets_decrement() to a log message.
2871 This may help us solve bug 614, and in any case will make its
2872 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
2873 - We were sometimes miscounting the number of bytes read from the
2874 network, causing our rate limiting to not be followed exactly.
2875 Bugfix on 0.2.0.16-alpha. Reported by lodger.
2878 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
2879 OpenSSL versions should have been working fine. Diagnosis and patch
2880 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
2881 Bugfix on 0.2.0.20-rc.
2884 Changes in version 0.2.0.20-rc - 2008-02-24
2885 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
2886 makes more progress towards normalizing Tor's TLS handshake, makes
2887 hidden services work better again, helps relays bootstrap if they don't
2888 know their IP address, adds optional support for linking in openbsd's
2889 allocator or tcmalloc, allows really fast relays to scale past 15000
2890 sockets, and fixes a bunch of minor bugs reported by Veracode.
2893 - Enable the revised TLS handshake based on the one designed by
2894 Steven Murdoch in proposal 124, as revised in proposal 130. It
2895 includes version negotiation for OR connections as described in
2896 proposal 105. The new handshake is meant to be harder for censors
2897 to fingerprint, and it adds the ability to detect certain kinds of
2898 man-in-the-middle traffic analysis attacks. The version negotiation
2899 feature will allow us to improve Tor's link protocol more safely
2901 - Choose which bridge to use proportional to its advertised bandwidth,
2902 rather than uniformly at random. This should speed up Tor for
2903 bridge users. Also do this for people who set StrictEntryNodes.
2904 - When a TrackHostExits-chosen exit fails too many times in a row,
2905 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
2908 - Resolved problems with (re-)fetching hidden service descriptors.
2909 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
2911 - If we only ever used Tor for hidden service lookups or posts, we
2912 would stop building circuits and start refusing connections after
2913 24 hours, since we falsely believed that Tor was dormant. Reported
2914 by nwf; bugfix on 0.1.2.x.
2915 - Servers that don't know their own IP address should go to the
2916 authorities for their first directory fetch, even if their DirPort
2917 is off or if they don't know they're reachable yet. This will help
2918 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
2919 - When counting the number of open sockets, count not only the number
2920 of sockets we have received from the socket() call, but also
2921 the number we've gotten from accept() and socketpair(). This bug
2922 made us fail to count all sockets that we were using for incoming
2923 connections. Bugfix on 0.2.0.x.
2924 - Fix code used to find strings within buffers, when those strings
2925 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
2926 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
2927 - Add a new __HashedControlSessionPassword option for controllers
2928 to use for one-off session password hashes that shouldn't get
2929 saved to disk by SAVECONF --- Vidalia users were accumulating a
2930 pile of HashedControlPassword lines in their torrc files, one for
2931 each time they had restarted Tor and then clicked Save. Make Tor
2932 automatically convert "HashedControlPassword" to this new option but
2933 only when it's given on the command line. Partial fix for bug 586.
2935 o Minor features (performance):
2936 - Tune parameters for cell pool allocation to minimize amount of
2938 - Add OpenBSD malloc code from phk as an optional malloc
2939 replacement on Linux: some glibc libraries do very poorly
2940 with Tor's memory allocation patterns. Pass
2941 --enable-openbsd-malloc to get the replacement malloc code.
2942 - Add a --with-tcmalloc option to the configure script to link
2943 against tcmalloc (if present). Does not yet search for
2944 non-system include paths.
2945 - Stop imposing an arbitrary maximum on the number of file descriptors
2946 used for busy servers. Bug reported by Olaf Selke; patch from
2949 o Minor features (other):
2950 - When SafeLogging is disabled, log addresses along with all TLS
2952 - When building with --enable-gcc-warnings, check for whether Apple's
2953 warning "-Wshorten-64-to-32" is available.
2954 - Add a --passphrase-fd argument to the tor-gencert command for
2957 o Minor bugfixes (memory leaks and code problems):
2958 - We were leaking a file descriptor if Tor started with a zero-length
2959 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
2960 - Detect size overflow in zlib code. Reported by Justin Ferguson and
2962 - We were comparing the raw BridgePassword entry with a base64'ed
2963 version of it, when handling a "/tor/networkstatus-bridges"
2964 directory request. Now compare correctly. Noticed by Veracode.
2965 - Recover from bad tracked-since value in MTBF-history file.
2967 - Alter the code that tries to recover from unhandled write
2968 errors, to not try to flush onto a socket that's given us
2969 unhandled errors. Bugfix on 0.1.2.x.
2970 - Make Unix controlsockets work correctly on OpenBSD. Patch from
2971 tup. Bugfix on 0.2.0.3-alpha.
2973 o Minor bugfixes (other):
2974 - If we have an extra-info document for our server, always make
2975 it available on the control port, even if we haven't gotten
2976 a copy of it from an authority yet. Patch from mwenge.
2977 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
2978 - Directory mirrors no longer include a guess at the client's IP
2979 address if the connection appears to be coming from the same /24
2980 network; it was producing too many wrong guesses.
2981 - Make the new hidden service code respect the SafeLogging setting.
2982 Bugfix on 0.2.0.x. Patch from Karsten.
2983 - When starting as an authority, do not overwrite all certificates
2984 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
2985 - If we're trying to flush the last bytes on a connection (for
2986 example, when answering a directory request), reset the
2987 time-to-give-up timeout every time we manage to write something
2988 on the socket. Bugfix on 0.1.2.x.
2989 - Change the behavior of "getinfo status/good-server-descriptor"
2990 so it doesn't return failure when any authority disappears.
2991 - Even though the man page said that "TrackHostExits ." should
2992 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
2993 - Report TLS "zero return" case as a "clean close" and "IO error"
2994 as a "close". Stop calling closes "unexpected closes": existing
2995 Tors don't use SSL_close(), so having a connection close without
2996 the TLS shutdown handshake is hardly unexpected.
2997 - Send NAMESERVER_STATUS messages for a single failed nameserver
3000 o Code simplifications and refactoring:
3001 - Remove the tor_strpartition function: its logic was confused,
3002 and it was only used for one thing that could be implemented far
3006 Changes in version 0.2.0.19-alpha - 2008-02-09
3007 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
3008 handshake, makes path selection for relays more secure and IP address
3009 guessing more robust, and generally fixes a lot of bugs in preparation
3010 for calling the 0.2.0 branch stable.
3013 - Do not include recognizeable strings in the commonname part of
3014 Tor's x509 certificates.
3017 - If we're a relay, avoid picking ourselves as an introduction point,
3018 a rendezvous point, or as the final hop for internal circuits. Bug
3019 reported by taranis and lodger. Bugfix on 0.1.2.x.
3020 - Patch from "Andrew S. Lists" to catch when we contact a directory
3021 mirror at IP address X and he says we look like we're coming from
3022 IP address X. Bugfix on 0.1.2.x.
3024 o Minor features (security):
3025 - Be more paranoid about overwriting sensitive memory on free(),
3026 as a defensive programming tactic to ensure forward secrecy.
3028 o Minor features (directory authority):
3029 - Actually validate the options passed to AuthDirReject,
3030 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
3031 - Reject router descriptors with out-of-range bandwidthcapacity or
3032 bandwidthburst values.
3034 o Minor features (controller):
3035 - Reject controller commands over 1MB in length. This keeps rogue
3036 processes from running us out of memory.
3038 o Minor features (misc):
3039 - Give more descriptive well-formedness errors for out-of-range
3040 hidden service descriptor/protocol versions.
3041 - Make memory debugging information describe more about history
3042 of cell allocation, so we can help reduce our memory use.
3044 o Deprecated features (controller):
3045 - The status/version/num-versioning and status/version/num-concurring
3046 GETINFO options are no longer useful in the v3 directory protocol:
3047 treat them as deprecated, and warn when they're used.
3050 - When our consensus networkstatus has been expired for a while, stop
3051 being willing to build circuits using it. Fixes bug 401. Bugfix
3053 - Directory caches now fetch certificates from all authorities
3054 listed in a networkstatus consensus, even when they do not
3055 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
3056 - When connecting to a bridge without specifying its key, insert
3057 the connection into the identity-to-connection map as soon as
3058 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
3059 - Detect versions of OS X where malloc_good_size() is present in the
3060 library but never actually declared. Resolves bug 587. Bugfix
3062 - Stop incorrectly truncating zlib responses to directory authority
3063 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
3064 - Stop recommending that every server operator send mail to tor-ops.
3065 Resolves bug 597. Bugfix on 0.1.2.x.
3066 - Don't trigger an assert if we start a directory authority with a
3067 private IP address (like 127.0.0.1).
3068 - Avoid possible failures when generating a directory with routers
3069 with over-long versions strings, or too many flags set. Bugfix
3071 - If an attempt to launch a DNS resolve request over the control
3072 port fails because we have overrun the limit on the number of
3073 connections, tell the controller that the request has failed.
3074 - Avoid using too little bandwidth when our clock skips a few
3075 seconds. Bugfix on 0.1.2.x.
3076 - Fix shell error when warning about missing packages in configure
3077 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
3078 - Do not become confused when receiving a spurious VERSIONS-like
3079 cell from a confused v1 client. Bugfix on 0.2.0.x.
3080 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
3081 introduction points for a hidden service have failed. Patch from
3082 Karsten Loesing. Bugfix on 0.2.0.x.
3084 o Code simplifications and refactoring:
3085 - Remove some needless generality from cpuworker code, for improved
3087 - Stop overloading the circuit_t.onionskin field for both "onionskin
3088 from a CREATE cell that we are waiting for a cpuworker to be
3089 assigned" and "onionskin from an EXTEND cell that we are going to
3090 send to an OR as soon as we are connected". Might help with bug 600.
3091 - Add an in-place version of aes_crypt() so that we can avoid doing a
3092 needless memcpy() call on each cell payload.
3095 Changes in version 0.2.0.18-alpha - 2008-01-25
3096 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
3097 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
3098 that can warn or reject connections to ports generally associated with
3099 vulnerable-plaintext protocols.
3101 o New directory authorities:
3102 - Set up dannenberg (run by CCC) as the sixth v3 directory
3106 - Fix a major memory leak when attempting to use the v2 TLS
3107 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
3108 - We accidentally enabled the under-development v2 TLS handshake
3109 code, which was causing log entries like "TLS error while
3110 renegotiating handshake". Disable it again. Resolves bug 590.
3111 - We were computing the wrong Content-Length: header for directory
3112 responses that need to be compressed on the fly, causing clients
3113 asking for those items to always fail. Bugfix on 0.2.0.x; partially
3117 - Avoid going directly to the directory authorities even if you're a
3118 relay, if you haven't found yourself reachable yet or if you've
3119 decided not to advertise your dirport yet. Addresses bug 556.
3120 - If we've gone 12 hours since our last bandwidth check, and we
3121 estimate we have less than 50KB bandwidth capacity but we could
3122 handle more, do another bandwidth test.
3123 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
3124 Tor can warn and/or refuse connections to ports commonly used with
3125 vulnerable-plaintext protocols. Currently we warn on ports 23,
3126 109, 110, and 143, but we don't reject any.
3129 - When we setconf ClientOnly to 1, close any current OR and Dir
3130 listeners. Reported by mwenge.
3131 - When we get a consensus that's been signed by more people than
3132 we expect, don't log about it; it's not a big deal. Reported
3136 - Don't answer "/tor/networkstatus-bridges" directory requests if
3137 the request isn't encrypted.
3138 - Make "ClientOnly 1" config option disable directory ports too.
3139 - Patches from Karsten Loesing to make v2 hidden services more
3140 robust: work even when there aren't enough HSDir relays available;
3141 retry when a v2 rend desc fetch fails; but don't retry if we
3142 already have a usable v0 rend desc.
3145 Changes in version 0.2.0.17-alpha - 2008-01-17
3146 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
3149 - Make the tor-gencert man page get included correctly in the tarball.
3152 Changes in version 0.2.0.16-alpha - 2008-01-17
3153 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
3154 Loesing, and generally cleans up a lot of features and minor bugs.
3156 o New directory authorities:
3157 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
3160 o Major performance improvements:
3161 - Switch our old ring buffer implementation for one more like that
3162 used by free Unix kernels. The wasted space in a buffer with 1mb
3163 of data will now be more like 8k than 1mb. The new implementation
3164 also avoids realloc();realloc(); patterns that can contribute to
3165 memory fragmentation.
3168 - Configuration files now accept C-style strings as values. This
3169 helps encode characters not allowed in the current configuration
3170 file format, such as newline or #. Addresses bug 557.
3171 - Although we fixed bug 539 (where servers would send HTTP status 503
3172 responses _and_ send a body too), there are still servers out
3173 there that haven't upgraded. Therefore, make clients parse such
3174 bodies when they receive them.
3175 - When we're not serving v2 directory information, there is no reason
3176 to actually keep any around. Remove the obsolete files and directory
3177 on startup if they are very old and we aren't going to serve them.
3179 o Minor performance improvements:
3180 - Reference-count and share copies of address policy entries; only 5%
3181 of them were actually distinct.
3182 - Never walk through the list of logs if we know that no log is
3183 interested in a given message.
3186 - When an authority has not signed a consensus, do not try to
3187 download a nonexistent "certificate with key 00000000". Bugfix
3188 on 0.2.0.x. Fixes bug 569.
3189 - Fix a rare assert error when we're closing one of our threads:
3190 use a mutex to protect the list of logs, so we never write to the
3191 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
3192 bug 575, which is kind of the revenge of bug 222.
3193 - Patch from Karsten Loesing to complain less at both the client
3194 and the relay when a relay used to have the HSDir flag but doesn't
3195 anymore, and we try to upload a hidden service descriptor.
3196 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
3198 - Do not try to download missing certificates until we have tried
3199 to check our fallback consensus. Fixes bug 583.
3200 - Make bridges round reported GeoIP stats info up to the nearest
3201 estimate, not down. Now we can distinguish between "0 people from
3202 this country" and "1 person from this country".
3203 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
3204 - Avoid possible segfault if key generation fails in
3205 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
3206 - Avoid segfault in the case where a badly behaved v2 versioning
3207 directory sends a signed networkstatus with missing client-versions.
3209 - Avoid segfaults on certain complex invocations of
3210 router_get_by_hexdigest(). Bugfix on 0.1.2.
3211 - Correct bad index on array access in parse_http_time(). Bugfix
3213 - Fix possible bug in vote generation when server versions are present
3214 but client versions are not.
3215 - Fix rare bug on REDIRECTSTREAM control command when called with no
3216 port set: it could erroneously report an error when none had
3218 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
3219 compressing large objects and find ourselves with more than 4k
3220 left over. Bugfix on 0.2.0.
3221 - Fix a small memory leak when setting up a hidden service.
3222 - Fix a few memory leaks that could in theory happen under bizarre
3224 - Fix an assert if we post a general-purpose descriptor via the
3225 control port but that descriptor isn't mentioned in our current
3226 network consensus. Bug reported by Jon McLachlan; bugfix on
3229 o Minor features (controller):
3230 - Get NS events working again. Patch from tup.
3231 - The GETCONF command now escapes and quotes configuration values
3232 that don't otherwise fit into the torrc file.
3233 - The SETCONF command now handles quoted values correctly.
3235 o Minor features (directory authorities):
3236 - New configuration options to override default maximum number of
3237 servers allowed on a single IP address. This is important for
3238 running a test network on a single host.
3239 - Actually implement the -s option to tor-gencert.
3240 - Add a manual page for tor-gencert.
3242 o Minor features (bridges):
3243 - Bridge authorities no longer serve bridge descriptors over
3244 unencrypted connections.
3246 o Minor features (other):
3247 - Add hidden services and DNSPorts to the list of things that make
3248 Tor accept that it has running ports. Change starting Tor with no
3249 ports from a fatal error to a warning; we might change it back if
3250 this turns out to confuse anybody. Fixes bug 579.
3253 Changes in version 0.1.2.19 - 2008-01-17
3254 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
3255 exit policy a little bit more conservative so it's safer to run an
3256 exit relay on a home system, and fixes a variety of smaller issues.
3259 - Exit policies now reject connections that are addressed to a
3260 relay's public (external) IP address too, unless
3261 ExitPolicyRejectPrivate is turned off. We do this because too
3262 many relays are running nearby to services that trust them based
3266 - When the clock jumps forward a lot, do not allow the bandwidth
3267 buckets to become negative. Fixes bug 544.
3268 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
3269 on every successful resolve. Reported by Mike Perry.
3270 - Purge old entries from the "rephist" database and the hidden
3271 service descriptor database even when DirPort is zero.
3272 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
3273 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
3274 crashing or mis-answering these requests.
3275 - When we decide to send a 503 response to a request for servers, do
3276 not then also send the server descriptors: this defeats the whole
3277 purpose. Fixes bug 539.
3280 - Changing the ExitPolicyRejectPrivate setting should cause us to
3281 rebuild our server descriptor.
3282 - Fix handling of hex nicknames when answering controller requests for
3283 networkstatus by name, or when deciding whether to warn about
3284 unknown routers in a config option. (Patch from mwenge.)
3285 - Fix a couple of hard-to-trigger autoconf problems that could result
3286 in really weird results on platforms whose sys/types.h files define
3287 nonstandard integer types.
3288 - Don't try to create the datadir when running --verify-config or
3289 --hash-password. Resolves bug 540.
3290 - If we were having problems getting a particular descriptor from the
3291 directory caches, and then we learned about a new descriptor for
3292 that router, we weren't resetting our failure count. Reported
3294 - Although we fixed bug 539 (where servers would send HTTP status 503
3295 responses _and_ send a body too), there are still servers out there
3296 that haven't upgraded. Therefore, make clients parse such bodies
3297 when they receive them.
3298 - Run correctly on systems where rlim_t is larger than unsigned long.
3299 This includes some 64-bit systems.
3300 - Run correctly on platforms (like some versions of OS X 10.5) where
3301 the real limit for number of open files is OPEN_FILES, not rlim_max
3302 from getrlimit(RLIMIT_NOFILES).
3303 - Avoid a spurious free on base64 failure.
3304 - Avoid segfaults on certain complex invocations of
3305 router_get_by_hexdigest().
3306 - Fix rare bug on REDIRECTSTREAM control command when called with no
3307 port set: it could erroneously report an error when none had
3311 Changes in version 0.2.0.15-alpha - 2007-12-25
3312 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
3313 features added in 0.2.0.13-alpha.
3316 - Fix several remotely triggerable asserts based on DirPort requests
3317 for a v2 or v3 networkstatus object before we were prepared. This
3318 was particularly bad for 0.2.0.13 and later bridge relays, who
3319 would never have a v2 networkstatus and would thus always crash
3320 when used. Bugfixes on 0.2.0.x.
3321 - Estimate the v3 networkstatus size more accurately, rather than
3322 estimating it at zero bytes and giving it artificially high priority
3323 compared to other directory requests. Bugfix on 0.2.0.x.
3326 - Fix configure.in logic for cross-compilation.
3327 - When we load a bridge descriptor from the cache, and it was
3328 previously unreachable, mark it as retriable so we won't just
3329 ignore it. Also, try fetching a new copy immediately. Bugfixes
3331 - The bridge GeoIP stats were counting other relays, for example
3332 self-reachability and authority-reachability tests.
3335 - Support compilation to target iPhone; patch from cjacker huang.
3336 To build for iPhone, pass the --enable-iphone option to configure.
3339 Changes in version 0.2.0.14-alpha - 2007-12-23
3341 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
3342 without a datadirectory from a previous Tor install. Reported
3344 - Fix a crash when we fetch a descriptor that turns out to be
3345 unexpected (it used to be in our networkstatus when we started
3346 fetching it, but it isn't in our current networkstatus), and we
3347 aren't using bridges. Bugfix on 0.2.0.x.
3348 - Fix a crash when accessing hidden services: it would work the first
3349 time you use a given introduction point for your service, but
3350 on subsequent requests we'd be using garbage memory. Fixed by
3351 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
3352 - Fix a crash when we load a bridge descriptor from disk but we don't
3353 currently have a Bridge line for it in our torrc. Bugfix on
3357 - If bridge authorities set BridgePassword, they will serve a
3358 snapshot of known bridge routerstatuses from their DirPort to
3359 anybody who knows that password. Unset by default.
3362 - Make the unit tests build again.
3363 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
3364 - Make PublishServerDescriptor default to 1, so the default doesn't
3365 have to change as we invent new directory protocol versions.
3366 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
3367 be included unless sys/time.h is already included. Fixes
3368 bug 553. Bugfix on 0.2.0.x.
3369 - If we receive a general-purpose descriptor and then receive an
3370 identical bridge-purpose descriptor soon after, don't discard
3371 the next one as a duplicate.
3374 - If BridgeRelay is set to 1, then the default for
3375 PublishServerDescriptor is now "bridge" rather than "v2,v3".
3376 - If the user sets RelayBandwidthRate but doesn't set
3377 RelayBandwidthBurst, then make them equal rather than erroring out.
3380 Changes in version 0.2.0.13-alpha - 2007-12-21
3381 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
3382 Goodell, fixes many more bugs, and adds a lot of infrastructure for
3385 o New directory authorities:
3386 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
3390 - Only update guard status (usable / not usable) once we have
3391 enough directory information. This was causing us to always pick
3392 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
3393 causing us to discard all our guards on startup if we hadn't been
3394 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
3395 - Purge old entries from the "rephist" database and the hidden
3396 service descriptor databases even when DirPort is zero. Bugfix
3398 - We were ignoring our RelayBandwidthRate for the first 30 seconds
3399 after opening a circuit -- even a relayed circuit. Bugfix on
3401 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
3402 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
3403 crashing or mis-answering these types of requests.
3404 - Relays were publishing their server descriptor to v1 and v2
3405 directory authorities, but they didn't try publishing to v3-only
3406 authorities. Fix this; and also stop publishing to v1 authorities.
3408 - When we were reading router descriptors from cache, we were ignoring
3409 the annotations -- so for example we were reading in bridge-purpose
3410 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
3411 - When we decided to send a 503 response to a request for servers, we
3412 were then also sending the server descriptors: this defeats the
3413 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
3416 - Bridge relays now behave like clients with respect to time
3417 intervals for downloading new consensus documents -- otherwise they
3418 stand out. Bridge users now wait until the end of the interval,
3419 so their bridge relay will be sure to have a new consensus document.
3420 - Three new config options (AlternateDirAuthority,
3421 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
3422 user selectively replace the default directory authorities by type,
3423 rather than the all-or-nothing replacement that DirServer offers.
3424 - Tor can now be configured to read a GeoIP file from disk in one
3425 of two formats. This can be used by controllers to map IP addresses
3426 to countries. Eventually, it may support exit-by-country.
3427 - When possible, bridge relays remember which countries users
3428 are coming from, and report aggregate information in their
3429 extra-info documents, so that the bridge authorities can learn
3430 where Tor is blocked.
3431 - Bridge directory authorities now do reachability testing on the
3432 bridges they know. They provide router status summaries to the
3433 controller via "getinfo ns/purpose/bridge", and also dump summaries
3434 to a file periodically.
3435 - Stop fetching directory info so aggressively if your DirPort is
3436 on but your ORPort is off; stop fetching v2 dir info entirely.
3437 You can override these choices with the new FetchDirInfoEarly
3441 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
3442 consensus documents when there are too many relays at a single
3443 IP address. Now clear it in v2 network status documents too, and
3444 also clear it in routerinfo_t when the relay is no longer listed
3445 in the relevant networkstatus document.
3446 - Don't crash if we get an unexpected value for the
3447 PublishServerDescriptor config option. Reported by Matt Edman;
3448 bugfix on 0.2.0.9-alpha.
3449 - Our new v2 hidden service descriptor format allows descriptors
3450 that have no introduction points. But Tor crashed when we tried
3451 to build a descriptor with no intro points (and it would have
3452 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
3454 - Fix building with dmalloc 5.5.2 with glibc.
3455 - Reject uploaded descriptors and extrainfo documents if they're
3456 huge. Otherwise we'll cache them all over the network and it'll
3457 clog everything up. Reported by Aljosha Judmayer.
3458 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
3459 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
3460 - When the DANGEROUS_VERSION controller status event told us we're
3461 running an obsolete version, it used the string "OLD" to describe
3462 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
3463 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
3464 - If we can't expand our list of entry guards (e.g. because we're
3465 using bridges or we have StrictEntryNodes set), don't mark relays
3466 down when they fail a directory request. Otherwise we're too quick
3467 to mark all our entry points down. Bugfix on 0.1.2.x.
3468 - Fix handling of hex nicknames when answering controller requests for
3469 networkstatus by name, or when deciding whether to warn about unknown
3470 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
3471 - Fix a couple of hard-to-trigger autoconf problems that could result
3472 in really weird results on platforms whose sys/types.h files define
3473 nonstandard integer types. Bugfix on 0.1.2.x.
3474 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
3475 - Don't crash on name lookup when we have no current consensus. Fixes
3476 bug 538; bugfix on 0.2.0.x.
3477 - Only Tors that want to mirror the v2 directory info should
3478 create the "cached-status" directory in their datadir. (All Tors
3479 used to create it.) Bugfix on 0.2.0.9-alpha.
3480 - Directory authorities should only automatically download Extra Info
3481 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
3484 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
3485 consumers. (We already do this on HUP.)
3486 - Authorities and caches fetch the v2 networkstatus documents
3487 less often, now that v3 is encouraged.
3488 - Add a new config option BridgeRelay that specifies you want to
3489 be a bridge relay. Right now the only difference is that it makes
3490 you answer begin_dir requests, and it makes you cache dir info,
3491 even if your DirPort isn't on.
3492 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
3493 ask about source, timestamp of arrival, purpose, etc. We need
3494 something like this to help Vidalia not do GeoIP lookups on bridge
3496 - Allow multiple HashedControlPassword config lines, to support
3497 multiple controller passwords.
3498 - Authorities now decide whether they're authoritative for a given
3499 router based on the router's purpose.
3500 - New config options AuthDirBadDir and AuthDirListBadDirs for
3501 authorities to mark certain relays as "bad directories" in the
3502 networkstatus documents. Also supports the "!baddir" directive in
3503 the approved-routers file.
3506 Changes in version 0.2.0.12-alpha - 2007-11-16
3507 This twelfth development snapshot fixes some more build problems as
3508 well as a few minor bugs.
3511 - Make it build on OpenBSD again. Patch from tup.
3512 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
3513 package-building for Red Hat, OS X, etc.
3515 o Minor bugfixes (on 0.1.2.x):
3516 - Changing the ExitPolicyRejectPrivate setting should cause us to
3517 rebuild our server descriptor.
3519 o Minor bugfixes (on 0.2.0.x):
3520 - When we're lacking a consensus, don't try to perform rendezvous
3521 operations. Reported by Karsten Loesing.
3522 - Fix a small memory leak whenever we decide against using a
3523 newly picked entry guard. Reported by Mike Perry.
3524 - When authorities detected more than two relays running on the same
3525 IP address, they were clearing all the status flags but forgetting
3526 to clear the "hsdir" flag. So clients were being told that a
3527 given relay was the right choice for a v2 hsdir lookup, yet they
3528 never had its descriptor because it was marked as 'not running'
3530 - If we're trying to fetch a bridge descriptor and there's no way
3531 the bridge authority could help us (for example, we don't know
3532 a digest, or there is no bridge authority), don't be so eager to
3533 fall back to asking the bridge authority.
3534 - If we're using bridges or have strictentrynodes set, and our
3535 chosen exit is in the same family as all our bridges/entry guards,
3536 then be flexible about families.
3539 - When we negotiate a v2 link-layer connection (not yet implemented),
3540 accept RELAY_EARLY cells and turn them into RELAY cells if we've
3541 negotiated a v1 connection for their next step. Initial code for
3545 Changes in version 0.2.0.11-alpha - 2007-11-12
3546 This eleventh development snapshot fixes some build problems with
3547 the previous snapshot. It also includes a more secure-by-default exit
3548 policy for relays, fixes an enormous memory leak for exit relays, and
3549 fixes another bug where servers were falling out of the directory list.
3552 - Exit policies now reject connections that are addressed to a
3553 relay's public (external) IP address too, unless
3554 ExitPolicyRejectPrivate is turned off. We do this because too
3555 many relays are running nearby to services that trust them based
3556 on network address. Bugfix on 0.1.2.x.
3559 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
3560 on every successful resolve. Reported by Mike Perry; bugfix
3562 - On authorities, never downgrade to old router descriptors simply
3563 because they're listed in the consensus. This created a catch-22
3564 where we wouldn't list a new descriptor because there was an
3565 old one in the consensus, and we couldn't get the new one in the
3566 consensus because we wouldn't list it. Possible fix for bug 548.
3567 Also, this might cause bug 543 to appear on authorities; if so,
3568 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
3570 o Packaging fixes on 0.2.0.10-alpha:
3571 - We were including instructions about what to do with the
3572 src/config/fallback-consensus file, but we weren't actually
3573 including it in the tarball. Disable all of that for now.
3576 - Allow people to say PreferTunnelledDirConns rather than
3577 PreferTunneledDirConns, for those alternate-spellers out there.
3580 - Don't reevaluate all the information from our consensus document
3581 just because we've downloaded a v2 networkstatus that we intend
3582 to cache. Fixes bug 545; bugfix on 0.2.0.x.
3585 Changes in version 0.2.0.10-alpha - 2007-11-10
3586 This tenth development snapshot adds a third v3 directory authority
3587 run by Mike Perry, adds most of Karsten Loesing's new hidden service
3588 descriptor format, fixes a bad crash bug and new bridge bugs introduced
3589 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
3590 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
3591 addresses many more minor issues.
3593 o New directory authorities:
3594 - Set up ides (run by Mike Perry) as the third v3 directory authority.
3597 - Allow tunnelled directory connections to ask for an encrypted
3598 "begin_dir" connection or an anonymized "uses a full Tor circuit"
3599 connection independently. Now we can make anonymized begin_dir
3600 connections for (e.g.) more secure hidden service posting and
3602 - More progress on proposal 114: code from Karsten Loesing to
3603 implement new hidden service descriptor format.
3604 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
3605 accommodate the growing number of servers that use the default
3606 and are reaching it.
3607 - Directory authorities use a new formula for selecting which nodes
3608 to advertise as Guards: they must be in the top 7/8 in terms of
3609 how long we have known about them, and above the median of those
3610 nodes in terms of weighted fractional uptime.
3611 - Make "not enough dir info yet" warnings describe *why* Tor feels
3612 it doesn't have enough directory info yet.
3615 - Stop servers from crashing if they set a Family option (or
3616 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
3618 - Make bridge users work again -- the move to v3 directories in
3619 0.2.0.9-alpha had introduced a number of bugs that made bridges
3620 no longer work for clients.
3621 - When the clock jumps forward a lot, do not allow the bandwidth
3622 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
3624 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
3625 - When the consensus lists a router descriptor that we previously were
3626 mirroring, but that we considered non-canonical, reload the
3627 descriptor as canonical. This fixes bug 543 where Tor servers
3628 would start complaining after a few days that they don't have
3629 enough directory information to build a circuit.
3630 - Consider replacing the current consensus when certificates arrive
3631 that make the pending consensus valid. Previously, we were only
3632 considering replacement when the new certs _didn't_ help.
3633 - Fix an assert error on startup if we didn't already have the
3634 consensus and certs cached in our datadirectory: we were caching
3635 the consensus in consensus_waiting_for_certs but then free'ing it
3637 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
3638 Request) if we need more v3 certs but we've already got pending
3639 requests for all of them.
3640 - Correctly back off from failing certificate downloads. Fixes
3642 - Authorities don't vote on the Running flag if they have been running
3643 for less than 30 minutes themselves. Fixes bug 547, where a newly
3644 started authority would vote that everyone was down.
3647 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
3648 it, it had no AES, and it hasn't seen any security patches since
3652 - Clients now hold circuitless TLS connections open for 1.5 times
3653 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
3654 rebuild a new circuit over them within that timeframe. Previously,
3655 they held them open only for KeepalivePeriod (5 minutes).
3656 - Use "If-Modified-Since" to avoid retrieving consensus
3657 networkstatuses that we already have.
3658 - When we have no consensus, check FallbackNetworkstatusFile (defaults
3659 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
3660 we start knowing some directory caches.
3661 - When we receive a consensus from the future, warn about skew.
3662 - Improve skew reporting: try to give the user a better log message
3663 about how skewed they are, and how much this matters.
3664 - When we have a certificate for an authority, believe that
3665 certificate's claims about the authority's IP address.
3666 - New --quiet command-line option to suppress the default console log.
3667 Good in combination with --hash-password.
3668 - Authorities send back an X-Descriptor-Not-New header in response to
3669 an accepted-but-discarded descriptor upload. Partially implements
3671 - Make the log message for "tls error. breaking." more useful.
3672 - Better log messages about certificate downloads, to attempt to
3673 track down the second incarnation of bug 546.
3675 o Minor features (bridges):
3676 - If bridge users set UpdateBridgesFromAuthority, but the digest
3677 they ask for is a 404 from the bridge authority, they now fall
3678 back to trying the bridge directly.
3679 - Bridges now use begin_dir to publish their server descriptor to
3680 the bridge authority, even when they haven't set TunnelDirConns.
3682 o Minor features (controller):
3683 - When reporting clock skew, and we know that the clock is _at least
3684 as skewed_ as some value, but we don't know the actual value,
3685 report the value as a "minimum skew."
3688 - Update linux-tor-prio.sh script to allow QoS based on the uid of
3689 the Tor process. Patch from Marco Bonetti with tweaks from Mike
3693 - Refuse to start if both ORPort and UseBridges are set. Bugfix
3694 on 0.2.0.x, suggested by Matt Edman.
3695 - Don't stop fetching descriptors when FetchUselessDescriptors is
3696 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
3697 reported by tup and ioerror.
3698 - Better log message on vote from unknown authority.
3699 - Don't log "Launching 0 request for 0 router" message.
3701 o Minor bugfixes (memory leaks):
3702 - Stop leaking memory every time we parse a v3 certificate. Bugfix
3704 - Stop leaking memory every time we load a v3 certificate. Bugfix
3705 on 0.2.0.1-alpha. Fixes bug 536.
3706 - Stop leaking a cached networkstatus on exit. Bugfix on
3708 - Stop leaking voter information every time we free a consensus.
3709 Bugfix on 0.2.0.3-alpha.
3710 - Stop leaking signed data every time we check a voter signature.
3711 Bugfix on 0.2.0.3-alpha.
3712 - Stop leaking a signature every time we fail to parse a consensus or
3713 a vote. Bugfix on 0.2.0.3-alpha.
3714 - Stop leaking v2_download_status_map on shutdown. Bugfix on
3716 - Stop leaking conn->nickname every time we make a connection to a
3717 Tor relay without knowing its expected identity digest (e.g. when
3718 using bridges). Bugfix on 0.2.0.3-alpha.
3720 - Minor bugfixes (portability):
3721 - Run correctly on platforms where rlim_t is larger than unsigned
3722 long, and/or where the real limit for number of open files is
3723 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
3724 particular, these may be needed for OS X 10.5.
3727 Changes in version 0.1.2.18 - 2007-10-28
3728 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
3729 hidden service introduction that were causing huge delays, and a big
3730 bug that was causing some servers to disappear from the network status
3731 lists for a few hours each day.
3733 o Major bugfixes (crashes):
3734 - If a connection is shut down abruptly because of something that
3735 happened inside connection_flushed_some(), do not call
3736 connection_finished_flushing(). Should fix bug 451:
3737 "connection_stop_writing: Assertion conn->write_event failed"
3738 Bugfix on 0.1.2.7-alpha.
3739 - Fix possible segfaults in functions called from
3740 rend_process_relay_cell().
3742 o Major bugfixes (hidden services):
3743 - Hidden services were choosing introduction points uniquely by
3744 hexdigest, but when constructing the hidden service descriptor
3745 they merely wrote the (potentially ambiguous) nickname.
3746 - Clients now use the v2 intro format for hidden service
3747 connections: they specify their chosen rendezvous point by identity
3748 digest rather than by (potentially ambiguous) nickname. These
3749 changes could speed up hidden service connections dramatically.
3751 o Major bugfixes (other):
3752 - Stop publishing a new server descriptor just because we get a
3753 HUP signal. This led (in a roundabout way) to some servers getting
3754 dropped from the networkstatus lists for a few hours each day.
3755 - When looking for a circuit to cannibalize, consider family as well
3756 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
3757 circuit cannibalization).
3758 - When a router wasn't listed in a new networkstatus, we were leaving
3759 the flags for that router alone -- meaning it remained Named,
3760 Running, etc -- even though absence from the networkstatus means
3761 that it shouldn't be considered to exist at all anymore. Now we
3762 clear all the flags for routers that fall out of the networkstatus
3763 consensus. Fixes bug 529.
3766 - Don't try to access (or alter) the state file when running
3767 --list-fingerprint or --verify-config or --hash-password. Resolves
3769 - When generating information telling us how to extend to a given
3770 router, do not try to include the nickname if it is
3771 absent. Resolves bug 467.
3772 - Fix a user-triggerable segfault in expand_filename(). (There isn't
3773 a way to trigger this remotely.)
3774 - When sending a status event to the controller telling it that an
3775 OR address is reachable, set the port correctly. (Previously we
3776 were reporting the dir port.)
3777 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
3778 command. Bugfix on 0.1.2.17.
3779 - When loading bandwidth history, do not believe any information in
3780 the future. Fixes bug 434.
3781 - When loading entry guard information, do not believe any information
3783 - When we have our clock set far in the future and generate an
3784 onion key, then re-set our clock to be correct, we should not stop
3785 the onion key from getting rotated.
3786 - On some platforms, accept() can return a broken address. Detect
3787 this more quietly, and deal accordingly. Fixes bug 483.
3788 - It's not actually an error to find a non-pending entry in the DNS
3789 cache when canceling a pending resolve. Don't log unless stuff
3790 is fishy. Resolves bug 463.
3791 - Don't reset trusted dir server list when we set a configuration
3792 option. Patch from Robert Hogan.
3793 - Don't try to create the datadir when running --verify-config or
3794 --hash-password. Resolves bug 540.
3797 Changes in version 0.2.0.9-alpha - 2007-10-24
3798 This ninth development snapshot switches clients to the new v3 directory
3799 system; allows servers to be listed in the network status even when they
3800 have the same nickname as a registered server; and fixes many other
3801 bugs including a big one that was causing some servers to disappear
3802 from the network status lists for a few hours each day.
3804 o Major features (directory system):
3805 - Clients now download v3 consensus networkstatus documents instead
3806 of v2 networkstatus documents. Clients and caches now base their
3807 opinions about routers on these consensus documents. Clients only
3808 download router descriptors listed in the consensus.
3809 - Authorities now list servers who have the same nickname as
3810 a different named server, but list them with a new flag,
3811 "Unnamed". Now we can list servers that happen to pick the same
3812 nickname as a server that registered two years ago and then
3813 disappeared. Partially implements proposal 122.
3814 - If the consensus lists a router as "Unnamed", the name is assigned
3815 to a different router: do not identify the router by that name.
3816 Partially implements proposal 122.
3817 - Authorities can now come to a consensus on which method to use to
3818 compute the consensus. This gives us forward compatibility.
3821 - Stop publishing a new server descriptor just because we HUP or
3822 when we find our DirPort to be reachable but won't actually publish
3823 it. New descriptors without any real changes are dropped by the
3824 authorities, and can screw up our "publish every 18 hours" schedule.
3826 - When a router wasn't listed in a new networkstatus, we were leaving
3827 the flags for that router alone -- meaning it remained Named,
3828 Running, etc -- even though absence from the networkstatus means
3829 that it shouldn't be considered to exist at all anymore. Now we
3830 clear all the flags for routers that fall out of the networkstatus
3831 consensus. Fixes bug 529; bugfix on 0.1.2.x.
3832 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
3833 extrainfo documents and then discard them immediately for not
3834 matching the latest router. Bugfix on 0.2.0.1-alpha.
3836 o Minor features (v3 directory protocol):
3837 - Allow tor-gencert to generate a new certificate without replacing
3839 - Allow certificates to include an address.
3840 - When we change our directory-cache settings, reschedule all voting
3841 and download operations.
3842 - Reattempt certificate downloads immediately on failure, as long as
3843 we haven't failed a threshold number of times yet.
3844 - Delay retrying consensus downloads while we're downloading
3845 certificates to verify the one we just got. Also, count getting a
3846 consensus that we already have (or one that isn't valid) as a failure,
3847 and count failing to get the certificates after 20 minutes as a
3849 - Build circuits and download descriptors even if our consensus is a
3850 little expired. (This feature will go away once authorities are
3853 o Minor features (router descriptor cache):
3854 - If we find a cached-routers file that's been sitting around for more
3855 than 28 days unmodified, then most likely it's a leftover from
3856 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
3858 - When we (as a cache) download a descriptor because it was listed
3859 in a consensus, remember when the consensus was supposed to expire,
3860 and don't expire the descriptor until then.
3862 o Minor features (performance):
3863 - Call routerlist_remove_old_routers() much less often. This should
3864 speed startup, especially on directory caches.
3865 - Don't try to launch new descriptor downloads quite so often when we
3866 already have enough directory information to build circuits.
3867 - Base64 decoding was actually showing up on our profile when parsing
3868 the initial descriptor file; switch to an in-process all-at-once
3869 implementation that's about 3.5x times faster than calling out to
3872 o Minor features (compilation):
3873 - Detect non-ASCII platforms (if any still exist) and refuse to
3874 build there: some of our code assumes that 'A' is 65 and so on.
3876 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
3877 - Make the "next period" votes into "current period" votes immediately
3878 after publishing the consensus; avoid a heisenbug that made them
3879 stick around indefinitely.
3880 - When we discard a vote as a duplicate, do not report this as
3882 - Treat missing v3 keys or certificates as an error when running as a
3883 v3 directory authority.
3884 - When we're configured to be a v3 authority, but we're only listed
3885 as a non-v3 authority in our DirServer line for ourself, correct
3887 - If an authority doesn't have a qualified hostname, just put
3888 its address in the vote. This fixes the problem where we referred to
3889 "moria on moria:9031."
3890 - Distinguish between detached signatures for the wrong period, and
3891 detached signatures for a divergent vote.
3892 - Fix a small memory leak when computing a consensus.
3893 - When there's no concensus, we were forming a vote every 30
3894 minutes, but writing the "valid-after" line in our vote based
3895 on our configured V3AuthVotingInterval: so unless the intervals
3896 matched up, we immediately rejected our own vote because it didn't
3897 start at the voting interval that caused us to construct a vote.
3899 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
3900 - Delete unverified-consensus when the real consensus is set.
3901 - Consider retrying a consensus networkstatus fetch immediately
3902 after one fails: don't wait 60 seconds to notice.
3903 - When fetching a consensus as a cache, wait until a newer consensus
3904 should exist before trying to replace the current one.
3905 - Use a more forgiving schedule for retrying failed consensus
3906 downloads than for other types.
3908 o Minor bugfixes (other directory issues):
3909 - Correct the implementation of "download votes by digest." Bugfix on
3911 - Authorities no longer send back "400 you're unreachable please fix
3912 it" errors to Tor servers that aren't online all the time. We're
3913 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
3915 o Minor bugfixes (controller):
3916 - Don't reset trusted dir server list when we set a configuration
3917 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
3918 - Respond to INT and TERM SIGNAL commands before we execute the
3919 signal, in case the signal shuts us down. We had a patch in
3920 0.1.2.1-alpha that tried to do this by queueing the response on
3921 the connection's buffer before shutting down, but that really
3922 isn't the same thing at all. Bug located by Matt Edman.
3924 o Minor bugfixes (misc):
3925 - Correctly check for bad options to the "PublishServerDescriptor"
3926 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
3927 - Stop leaking memory on failing case of base32_decode, and make
3928 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
3929 - Don't try to download extrainfo documents when we're trying to
3930 fetch enough directory info to build a circuit: having enough
3931 info should get priority. Bugfix on 0.2.0.x.
3932 - Don't complain that "your server has not managed to confirm that its
3933 ports are reachable" if we haven't been able to build any circuits
3934 yet. Bug found by spending four hours without a v3 consensus. Bugfix
3936 - Detect the reason for failing to mmap a descriptor file we just
3937 wrote, and give a more useful log message. Fixes bug 533. Bugfix
3940 o Code simplifications and refactoring:
3941 - Remove support for the old bw_accounting file: we've been storing
3942 bandwidth accounting information in the state file since
3943 0.1.2.5-alpha. This may result in bandwidth accounting errors
3944 if you try to upgrade from 0.1.1.x or earlier, or if you try to
3945 downgrade to 0.1.1.x or earlier.
3946 - New convenience code to locate a file within the DataDirectory.
3947 - Move non-authority functionality out of dirvote.c.
3948 - Refactor the arguments for router_pick_{directory_|trusteddir}server
3949 so that they all take the same named flags.
3952 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
3953 Unix users an easy way to script their Tor process (e.g. by
3954 adjusting bandwidth based on the time of the day).
3957 Changes in version 0.2.0.8-alpha - 2007-10-12
3958 This eighth development snapshot fixes a crash bug that's been bothering
3959 us since February 2007, lets bridge authorities store a list of bridge
3960 descriptors they've seen, gets v3 directory voting closer to working,
3961 starts caching v3 directory consensus documents on directory mirrors,
3962 and fixes a variety of smaller issues including some minor memory leaks.
3964 o Major features (router descriptor cache):
3965 - Store routers in a file called cached-descriptors instead of in
3966 cached-routers. Initialize cached-descriptors from cached-routers
3967 if the old format is around. The new format allows us to store
3968 annotations along with descriptors.
3969 - Use annotations to record the time we received each descriptor, its
3970 source, and its purpose.
3971 - Disable the SETROUTERPURPOSE controller command: it is now
3973 - Controllers should now specify cache=no or cache=yes when using
3974 the +POSTDESCRIPTOR command.
3975 - Bridge authorities now write bridge descriptors to disk, meaning
3976 we can export them to other programs and begin distributing them
3979 o Major features (directory authorities):
3980 - When a v3 authority is missing votes or signatures, it now tries
3982 - Directory authorities track weighted fractional uptime as well as
3983 weighted mean-time-between failures. WFU is suitable for deciding
3984 whether a node is "usually up", while MTBF is suitable for deciding
3985 whether a node is "likely to stay up." We need both, because
3986 "usually up" is a good requirement for guards, while "likely to
3987 stay up" is a good requirement for long-lived connections.
3989 o Major features (v3 directory system):
3990 - Caches now download v3 network status documents as needed,
3991 and download the descriptors listed in them.
3992 - All hosts now attempt to download and keep fresh v3 authority
3993 certificates, and re-attempt after failures.
3994 - More internal-consistency checks for vote parsing.
3996 o Major bugfixes (crashes):
3997 - If a connection is shut down abruptly because of something that
3998 happened inside connection_flushed_some(), do not call
3999 connection_finished_flushing(). Should fix bug 451. Bugfix on
4002 o Major bugfixes (performance):
4003 - Fix really bad O(n^2) performance when parsing a long list of
4004 routers: Instead of searching the entire list for an "extra-info "
4005 string which usually wasn't there, once for every routerinfo
4006 we read, just scan lines forward until we find one we like.
4008 - When we add data to a write buffer in response to the data on that
4009 write buffer getting low because of a flush, do not consider the
4010 newly added data as a candidate for immediate flushing, but rather
4011 make it wait until the next round of writing. Otherwise, we flush
4012 and refill recursively, and a single greedy TLS connection can
4013 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
4015 o Minor features (v3 authority system):
4016 - Add more ways for tools to download the votes that lead to the
4018 - Send a 503 when low on bandwidth and a vote, consensus, or
4019 certificate is requested.
4020 - If-modified-since is now implemented properly for all kinds of
4021 certificate requests.
4023 o Minor bugfixes (network statuses):
4024 - Tweak the implementation of proposal 109 slightly: allow at most
4025 two Tor servers on the same IP address, except if it's the location
4026 of a directory authority, in which case allow five. Bugfix on
4029 o Minor bugfixes (controller):
4030 - When sending a status event to the controller telling it that an
4031 OR address is reachable, set the port correctly. (Previously we
4032 were reporting the dir port.) Bugfix on 0.1.2.x.
4034 o Minor bugfixes (v3 directory system):
4035 - Fix logic to look up a cert by its signing key digest. Bugfix on
4037 - Only change the reply to a vote to "OK" if it's not already
4038 set. This gets rid of annoying "400 OK" log messages, which may
4039 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
4040 - When we get a valid consensus, recompute the voting schedule.
4041 - Base the valid-after time of a vote on the consensus voting
4042 schedule, not on our preferred schedule.
4043 - Make the return values and messages from signature uploads and
4044 downloads more sensible.
4045 - Fix a memory leak when serving votes and consensus documents, and
4046 another when serving certificates.
4048 o Minor bugfixes (performance):
4049 - Use a slightly simpler string hashing algorithm (copying Python's
4050 instead of Java's) and optimize our digest hashing algorithm to take
4051 advantage of 64-bit platforms and to remove some possibly-costly
4053 - Fix a minor memory leak whenever we parse guards from our state
4054 file. Bugfix on 0.2.0.7-alpha.
4055 - Fix a minor memory leak whenever we write out a file. Bugfix on
4057 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
4058 command. Bugfix on 0.2.0.5-alpha.
4060 o Minor bugfixes (portability):
4061 - On some platforms, accept() can return a broken address. Detect
4062 this more quietly, and deal accordingly. Fixes bug 483.
4063 - Stop calling tor_strlower() on uninitialized memory in some cases.
4064 Bugfix in 0.2.0.7-alpha.
4066 o Minor bugfixes (usability):
4067 - Treat some 403 responses from directory servers as INFO rather than
4068 WARN-severity events.
4069 - It's not actually an error to find a non-pending entry in the DNS
4070 cache when canceling a pending resolve. Don't log unless stuff is
4071 fishy. Resolves bug 463.
4073 o Minor bugfixes (anonymity):
4074 - Never report that we've used more bandwidth than we're willing to
4075 relay: it leaks how much non-relay traffic we're using. Resolves
4077 - When looking for a circuit to cannibalize, consider family as well
4078 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
4079 circuit cannibalization).
4081 o Code simplifications and refactoring:
4082 - Make a bunch of functions static. Remove some dead code.
4083 - Pull out about a third of the really big routerlist.c; put it in a
4084 new module, networkstatus.c.
4085 - Merge the extra fields in local_routerstatus_t back into
4086 routerstatus_t: we used to need one routerstatus_t for each
4087 authority's opinion, plus a local_routerstatus_t for the locally
4088 computed consensus opinion. To save space, we put the locally
4089 modified fields into local_routerstatus_t, and only the common
4090 stuff into routerstatus_t. But once v3 directories are in use,
4091 clients and caches will no longer need to hold authority opinions;
4092 thus, the rationale for keeping the types separate is now gone.
4093 - Make the code used to reschedule and reattempt downloads more
4095 - Turn all 'Are we a directory server/mirror?' logic into a call to
4097 - Remove the code to generate the oldest (v1) directory format.
4098 The code has been disabled since 0.2.0.5-alpha.
4101 Changes in version 0.2.0.7-alpha - 2007-09-21
4102 This seventh development snapshot makes bridges work again, makes bridge
4103 authorities work for the first time, fixes two huge performance flaws
4104 in hidden services, and fixes a variety of minor issues.
4106 o New directory authorities:
4107 - Set up moria1 and tor26 as the first v3 directory authorities. See
4108 doc/spec/dir-spec.txt for details on the new directory design.
4110 o Major bugfixes (crashes):
4111 - Fix possible segfaults in functions called from
4112 rend_process_relay_cell(). Bugfix on 0.1.2.x.
4114 o Major bugfixes (bridges):
4115 - Fix a bug that made servers send a "404 Not found" in response to
4116 attempts to fetch their server descriptor. This caused Tor servers
4117 to take many minutes to establish reachability for their DirPort,
4118 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
4119 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
4120 users configure that and specify a bridge with an identity
4121 fingerprint, now they will lookup the bridge descriptor at the
4122 default bridge authority via a one-hop tunnel, but once circuits
4123 are established they will switch to a three-hop tunnel for later
4124 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
4126 o Major bugfixes (hidden services):
4127 - Hidden services were choosing introduction points uniquely by
4128 hexdigest, but when constructing the hidden service descriptor
4129 they merely wrote the (potentially ambiguous) nickname.
4130 - Clients now use the v2 intro format for hidden service
4131 connections: they specify their chosen rendezvous point by identity
4132 digest rather than by (potentially ambiguous) nickname. Both
4133 are bugfixes on 0.1.2.x, and they could speed up hidden service
4134 connections dramatically. Thanks to Karsten Loesing.
4136 o Minor features (security):
4137 - As a client, do not believe any server that tells us that an
4138 address maps to an internal address space.
4139 - Make it possible to enable HashedControlPassword and
4140 CookieAuthentication at the same time.
4142 o Minor features (guard nodes):
4143 - Tag every guard node in our state file with the version that
4144 we believe added it, or with our own version if we add it. This way,
4145 if a user temporarily runs an old version of Tor and then switches
4146 back to a new one, she doesn't automatically lose her guards.
4148 o Minor features (speed):
4149 - When implementing AES counter mode, update only the portions of the
4150 counter buffer that need to change, and don't keep separate
4151 network-order and host-order counters when they are the same (i.e.,
4152 on big-endian hosts.)
4154 o Minor features (controller):
4155 - Accept LF instead of CRLF on controller, since some software has a
4156 hard time generating real Internet newlines.
4157 - Add GETINFO values for the server status events
4158 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
4162 - Routers no longer include bandwidth-history lines in their
4163 descriptors; this information is already available in extra-info
4164 documents, and including it in router descriptors took up 60%
4165 (!) of compressed router descriptor downloads. Completes
4166 implementation of proposal 104.
4167 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
4168 and TorControl.py, as they use the old v0 controller protocol,
4169 and are obsoleted by TorFlow anyway.
4170 - Drop support for v1 rendezvous descriptors, since we never used
4171 them anyway, and the code has probably rotted by now. Based on
4172 patch from Karsten Loesing.
4173 - On OSX, stop warning the user that kqueue support in libevent is
4174 "experimental", since it seems to have worked fine for ages.
4177 - When generating information telling us how to extend to a given
4178 router, do not try to include the nickname if it is absent. Fixes
4179 bug 467. Bugfix on 0.2.0.3-alpha.
4180 - Fix a user-triggerable (but not remotely-triggerable) segfault
4181 in expand_filename(). Bugfix on 0.1.2.x.
4182 - Fix a memory leak when freeing incomplete requests from DNSPort.
4183 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
4184 - Don't try to access (or alter) the state file when running
4185 --list-fingerprint or --verify-config or --hash-password. (Resolves
4186 bug 499.) Bugfix on 0.1.2.x.
4187 - Servers used to decline to publish their DirPort if their
4188 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
4189 were below a threshold. Now they only look at BandwidthRate and
4190 RelayBandwidthRate. Bugfix on 0.1.2.x.
4191 - Remove an optimization in the AES counter-mode code that assumed
4192 that the counter never exceeded 2^68. When the counter can be set
4193 arbitrarily as an IV (as it is by Karsten's new hidden services
4194 code), this assumption no longer holds. Bugfix on 0.1.2.x.
4195 - Resume listing "AUTHORITY" flag for authorities in network status.
4196 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
4198 o Code simplifications and refactoring:
4199 - Revamp file-writing logic so we don't need to have the entire
4200 contents of a file in memory at once before we write to disk. Tor,
4202 - Turn "descriptor store" into a full-fledged type.
4203 - Move all NT services code into a separate source file.
4204 - Unify all code that computes medians, percentile elements, etc.
4205 - Get rid of a needless malloc when parsing address policies.
4208 Changes in version 0.1.2.17 - 2007-08-30
4209 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
4210 X bundles. Vidalia 0.0.14 makes authentication required for the
4211 ControlPort in the default configuration, which addresses important
4212 security risks. Everybody who uses Vidalia (or another controller)
4215 In addition, this Tor update fixes major load balancing problems with
4216 path selection, which should speed things up a lot once many people
4219 o Major bugfixes (security):
4220 - We removed support for the old (v0) control protocol. It has been
4221 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
4222 become more of a headache than it's worth.
4224 o Major bugfixes (load balancing):
4225 - When choosing nodes for non-guard positions, weight guards
4226 proportionally less, since they already have enough load. Patch
4228 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
4229 will allow fast Tor servers to get more attention.
4230 - When we're upgrading from an old Tor version, forget our current
4231 guards and pick new ones according to the new weightings. These
4232 three load balancing patches could raise effective network capacity
4233 by a factor of four. Thanks to Mike Perry for measurements.
4235 o Major bugfixes (stream expiration):
4236 - Expire not-yet-successful application streams in all cases if
4237 they've been around longer than SocksTimeout. Right now there are
4238 some cases where the stream will live forever, demanding a new
4239 circuit every 15 seconds. Fixes bug 454; reported by lodger.
4241 o Minor features (controller):
4242 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
4243 is valid before any authentication has been received. It tells
4244 a controller what kind of authentication is expected, and what
4245 protocol is spoken. Implements proposal 119.
4247 o Minor bugfixes (performance):
4248 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
4249 greatly speeding up loading cached-routers from disk on startup.
4250 - Disable sentinel-based debugging for buffer code: we squashed all
4251 the bugs that this was supposed to detect a long time ago, and now
4252 its only effect is to change our buffer sizes from nice powers of
4253 two (which platform mallocs tend to like) to values slightly over
4254 powers of two (which make some platform mallocs sad).
4256 o Minor bugfixes (misc):
4257 - If exit bandwidth ever exceeds one third of total bandwidth, then
4258 use the correct formula to weight exit nodes when choosing paths.
4259 Based on patch from Mike Perry.
4260 - Choose perfectly fairly among routers when choosing by bandwidth and
4261 weighting by fraction of bandwidth provided by exits. Previously, we
4262 would choose with only approximate fairness, and correct ourselves
4263 if we ran off the end of the list.
4264 - If we require CookieAuthentication but we fail to write the
4265 cookie file, we would warn but not exit, and end up in a state
4266 where no controller could authenticate. Now we exit.
4267 - If we require CookieAuthentication, stop generating a new cookie
4268 every time we change any piece of our config.
4269 - Refuse to start with certain directory authority keys, and
4270 encourage people using them to stop.
4271 - Terminate multi-line control events properly. Original patch
4273 - Fix a minor memory leak when we fail to find enough suitable
4274 servers to choose a circuit.
4275 - Stop leaking part of the descriptor when we run into a particularly
4276 unparseable piece of it.
4279 Changes in version 0.2.0.6-alpha - 2007-08-26
4280 This sixth development snapshot features a new Vidalia version in the
4281 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
4282 the ControlPort in the default configuration, which addresses important
4285 In addition, this snapshot fixes major load balancing problems
4286 with path selection, which should speed things up a lot once many
4287 people have upgraded. The directory authorities also use a new
4288 mean-time-between-failure approach to tracking which servers are stable,
4289 rather than just looking at the most recent uptime.
4291 o New directory authorities:
4292 - Set up Tonga as the default bridge directory authority.
4295 - Directory authorities now track servers by weighted
4296 mean-times-between-failures. When we have 4 or more days of data,
4297 use measured MTBF rather than declared uptime to decide whether
4298 to call a router Stable. Implements proposal 108.
4300 o Major bugfixes (load balancing):
4301 - When choosing nodes for non-guard positions, weight guards
4302 proportionally less, since they already have enough load. Patch
4304 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
4305 will allow fast Tor servers to get more attention.
4306 - When we're upgrading from an old Tor version, forget our current
4307 guards and pick new ones according to the new weightings. These
4308 three load balancing patches could raise effective network capacity
4309 by a factor of four. Thanks to Mike Perry for measurements.
4311 o Major bugfixes (descriptor parsing):
4312 - Handle unexpected whitespace better in malformed descriptors. Bug
4313 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
4316 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
4317 GETINFO for Torstat to use until it can switch to using extrainfos.
4318 - Optionally (if built with -DEXPORTMALLINFO) export the output
4319 of mallinfo via http, as tor/mallinfo.txt. Only accessible
4323 - Do not intermix bridge routers with controller-added
4324 routers. (Bugfix on 0.2.0.x)
4325 - Do not fail with an assert when accept() returns an unexpected
4326 address family. Addresses but does not wholly fix bug 483. (Bugfix
4328 - Let directory authorities startup even when they can't generate
4329 a descriptor immediately, e.g. because they don't know their
4331 - Stop putting the authentication cookie in a file called "0"
4332 in your working directory if you don't specify anything for the
4333 new CookieAuthFile option. Reported by Matt Edman.
4334 - Make it possible to read the PROTOCOLINFO response in a way that
4335 conforms to our control-spec. Reported by Matt Edman.
4336 - Fix a minor memory leak when we fail to find enough suitable
4337 servers to choose a circuit. Bugfix on 0.1.2.x.
4338 - Stop leaking part of the descriptor when we run into a particularly
4339 unparseable piece of it. Bugfix on 0.1.2.x.
4340 - Unmap the extrainfo cache file on exit.
4343 Changes in version 0.2.0.5-alpha - 2007-08-19
4344 This fifth development snapshot fixes compilation on Windows again;
4345 fixes an obnoxious client-side bug that slowed things down and put
4346 extra load on the network; gets us closer to using the v3 directory
4347 voting scheme; makes it easier for Tor controllers to use cookie-based
4348 authentication; and fixes a variety of other bugs.
4351 - Version 1 directories are no longer generated in full. Instead,
4352 authorities generate and serve "stub" v1 directories that list
4353 no servers. This will stop Tor versions 0.1.0.x and earlier from
4354 working, but (for security reasons) nobody should be running those
4357 o Major bugfixes (compilation, 0.2.0.x):
4358 - Try to fix Win32 compilation again: improve checking for IPv6 types.
4359 - Try to fix MSVC compilation: build correctly on platforms that do
4360 not define s6_addr16 or s6_addr32.
4361 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
4364 o Major bugfixes (stream expiration):
4365 - Expire not-yet-successful application streams in all cases if
4366 they've been around longer than SocksTimeout. Right now there are
4367 some cases where the stream will live forever, demanding a new
4368 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
4371 o Minor features (directory servers):
4372 - When somebody requests a list of statuses or servers, and we have
4373 none of those, return a 404 rather than an empty 200.
4375 o Minor features (directory voting):
4376 - Store v3 consensus status consensuses on disk, and reload them
4379 o Minor features (security):
4380 - Warn about unsafe ControlPort configurations.
4381 - Refuse to start with certain directory authority keys, and
4382 encourage people using them to stop.
4384 o Minor features (controller):
4385 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
4386 is valid before any authentication has been received. It tells
4387 a controller what kind of authentication is expected, and what
4388 protocol is spoken. Implements proposal 119.
4389 - New config option CookieAuthFile to choose a new location for the
4390 cookie authentication file, and config option
4391 CookieAuthFileGroupReadable to make it group-readable.
4393 o Minor features (unit testing):
4394 - Add command-line arguments to unit-test executable so that we can
4395 invoke any chosen test from the command line rather than having
4396 to run the whole test suite at once; and so that we can turn on
4397 logging for the unit tests.
4399 o Minor bugfixes (on 0.1.2.x):
4400 - If we require CookieAuthentication but we fail to write the
4401 cookie file, we would warn but not exit, and end up in a state
4402 where no controller could authenticate. Now we exit.
4403 - If we require CookieAuthentication, stop generating a new cookie
4404 every time we change any piece of our config.
4405 - When loading bandwidth history, do not believe any information in
4406 the future. Fixes bug 434.
4407 - When loading entry guard information, do not believe any information
4409 - When we have our clock set far in the future and generate an
4410 onion key, then re-set our clock to be correct, we should not stop
4411 the onion key from getting rotated.
4412 - Clean up torrc sample config file.
4413 - Do not automatically run configure from autogen.sh. This
4414 non-standard behavior tended to annoy people who have built other
4417 o Minor bugfixes (on 0.2.0.x):
4418 - Fix a bug with AutomapHostsOnResolve that would always cause
4419 the second request to fail. Bug reported by Kate. Bugfix on
4421 - Fix a bug in ADDRMAP controller replies that would sometimes
4422 try to print a NULL. Patch from tup.
4423 - Read v3 directory authority keys from the right location.
4424 - Numerous bugfixes to directory voting code.
4427 Changes in version 0.1.2.16 - 2007-08-01
4428 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
4429 remote attacker in certain situations to rewrite the user's torrc
4430 configuration file. This can completely compromise anonymity of users
4431 in most configurations, including those running the Vidalia bundles,
4432 TorK, etc. Or worse.
4434 o Major security fixes:
4435 - Close immediately after missing authentication on control port;
4436 do not allow multiple authentication attempts.
4439 Changes in version 0.2.0.4-alpha - 2007-08-01
4440 This fourth development snapshot fixes a critical security vulnerability
4441 for most users, specifically those running Vidalia, TorK, etc. Everybody
4442 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
4444 o Major security fixes:
4445 - Close immediately after missing authentication on control port;
4446 do not allow multiple authentication attempts.
4448 o Major bugfixes (compilation):
4449 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
4452 o Minor features (performance):
4453 - Be even more aggressive about releasing RAM from small
4454 empty buffers. Thanks to our free-list code, this shouldn't be too
4455 performance-intensive.
4456 - Disable sentinel-based debugging for buffer code: we squashed all
4457 the bugs that this was supposed to detect a long time ago, and
4458 now its only effect is to change our buffer sizes from nice
4459 powers of two (which platform mallocs tend to like) to values
4460 slightly over powers of two (which make some platform mallocs sad).
4461 - Log malloc statistics from mallinfo() on platforms where it
4465 Changes in version 0.2.0.3-alpha - 2007-07-29
4466 This third development snapshot introduces new experimental
4467 blocking-resistance features and a preliminary version of the v3
4468 directory voting design, and includes many other smaller features
4472 - The first pieces of our "bridge" design for blocking-resistance
4473 are implemented. People can run bridge directory authorities;
4474 people can run bridges; and people can configure their Tor clients
4475 with a set of bridges to use as the first hop into the Tor network.
4476 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
4478 - Create listener connections before we setuid to the configured
4479 User and Group. Now non-Windows users can choose port values
4480 under 1024, start Tor as root, and have Tor bind those ports
4481 before it changes to another UID. (Windows users could already
4483 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
4484 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
4485 on "vserver" accounts. (Patch from coderman.)
4486 - Be even more aggressive about separating local traffic from relayed
4487 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
4489 o Major features (experimental):
4490 - First cut of code for "v3 dir voting": directory authorities will
4491 vote on a common network status document rather than each publishing
4492 their own opinion. This code needs more testing and more corner-case
4493 handling before it's ready for use.
4496 - Directory authorities now call routers Fast if their bandwidth is
4497 at least 100KB/s, and consider their bandwidth adequate to be a
4498 Guard if it is at least 250KB/s, no matter the medians. This fix
4499 complements proposal 107. [Bugfix on 0.1.2.x]
4500 - Directory authorities now never mark more than 3 servers per IP as
4501 Valid and Running. (Implements proposal 109, by Kevin Bauer and
4503 - Minor change to organizationName and commonName generation
4504 procedures in TLS certificates during Tor handshakes, to invalidate
4505 some earlier censorware approaches. This is not a long-term
4506 solution, but applying it will give us a bit of time to look into
4507 the epidemiology of countermeasures as they spread.
4509 o Major bugfixes (directory):
4510 - Rewrite directory tokenization code to never run off the end of
4511 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
4513 o Minor features (controller):
4514 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
4515 match requests to applications. (Patch from Robert Hogan.)
4516 - Report address and port correctly on connections to DNSPort. (Patch
4518 - Add a RESOLVE command to launch hostname lookups. (Original patch
4520 - Add GETINFO status/enough-dir-info to let controllers tell whether
4521 Tor has downloaded sufficient directory information. (Patch
4523 - You can now use the ControlSocket option to tell Tor to listen for
4524 controller connections on Unix domain sockets on systems that
4525 support them. (Patch from Peter Palfrader.)
4526 - STREAM NEW events are generated for DNSPort requests and for
4527 tunneled directory connections. (Patch from Robert Hogan.)
4528 - New "GETINFO address-mappings/*" command to get address mappings
4529 with expiry information. "addr-mappings/*" is now deprecated.
4532 o Minor features (misc):
4533 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
4535 - The tor-gencert tool for v3 directory authorities now creates all
4536 files as readable to the file creator only, and write-protects
4537 the authority identity key.
4538 - When dumping memory usage, list bytes used in buffer memory
4540 - When running with dmalloc, dump more stats on hup and on exit.
4541 - Directory authorities now fail quickly and (relatively) harmlessly
4542 if they generate a network status document that is somehow
4545 o Traffic load balancing improvements:
4546 - If exit bandwidth ever exceeds one third of total bandwidth, then
4547 use the correct formula to weight exit nodes when choosing paths.
4548 (Based on patch from Mike Perry.)
4549 - Choose perfectly fairly among routers when choosing by bandwidth and
4550 weighting by fraction of bandwidth provided by exits. Previously, we
4551 would choose with only approximate fairness, and correct ourselves
4552 if we ran off the end of the list. [Bugfix on 0.1.2.x]
4554 o Performance improvements:
4555 - Be more aggressive with freeing buffer RAM or putting it on the
4557 - Use Critical Sections rather than Mutexes for synchronizing threads
4558 on win32; Mutexes are heavier-weight, and designed for synchronizing
4561 o Deprecated and removed features:
4562 - RedirectExits is now deprecated.
4563 - Stop allowing address masks that do not correspond to bit prefixes.
4564 We have warned about these for a really long time; now it's time
4565 to reject them. (Patch from croup.)
4567 o Minor bugfixes (directory):
4568 - Fix another crash bug related to extra-info caching. (Bug found by
4569 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
4570 - Directories no longer return a "304 not modified" when they don't
4571 have the networkstatus the client asked for. Also fix a memory
4572 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
4573 - We had accidentally labelled 0.1.2.x directory servers as not
4574 suitable for begin_dir requests, and had labelled no directory
4575 servers as suitable for uploading extra-info documents. [Bugfix
4578 o Minor bugfixes (dns):
4579 - Fix a crash when DNSPort is set more than once. (Patch from Robert
4580 Hogan.) [Bugfix on 0.2.0.2-alpha]
4581 - Add DNSPort connections to the global connection list, so that we
4582 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
4584 - Fix a dangling reference that could lead to a crash when DNSPort is
4585 changed or closed (Patch from Robert Hogan.) [Bugfix on
4588 o Minor bugfixes (controller):
4589 - Provide DNS expiry times in GMT, not in local time. For backward
4590 compatibility, ADDRMAP events only provide GMT expiry in an extended
4591 field. "GETINFO address-mappings" always does the right thing.
4592 - Use CRLF line endings properly in NS events.
4593 - Terminate multi-line control events properly. (Original patch
4594 from tup.) [Bugfix on 0.1.2.x-alpha]
4595 - Do not include spaces in SOURCE_ADDR fields in STREAM
4596 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
4599 Changes in version 0.1.2.15 - 2007-07-17
4600 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
4601 problems, fixes compilation on BSD, and fixes a variety of other
4602 bugs. Everybody should upgrade.
4604 o Major bugfixes (compilation):
4605 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
4607 o Major bugfixes (crashes):
4608 - Try even harder not to dereference the first character after
4609 an mmap(). Reported by lodger.
4610 - Fix a crash bug in directory authorities when we re-number the
4611 routerlist while inserting a new router.
4612 - When the cached-routers file is an even multiple of the page size,
4613 don't run off the end and crash. (Fixes bug 455; based on idea
4615 - Fix eventdns.c behavior on Solaris: It is critical to include
4616 orconfig.h _before_ sys/types.h, so that we can get the expected
4617 definition of _FILE_OFFSET_BITS.
4619 o Major bugfixes (security):
4620 - Fix a possible buffer overrun when using BSD natd support. Bug
4622 - When sending destroy cells from a circuit's origin, don't include
4623 the reason for tearing down the circuit. The spec says we didn't,
4624 and now we actually don't. Reported by lodger.
4625 - Keep streamids from different exits on a circuit separate. This
4626 bug may have allowed other routers on a given circuit to inject
4627 cells into streams. Reported by lodger; fixes bug 446.
4628 - If there's a never-before-connected-to guard node in our list,
4629 never choose any guards past it. This way we don't expand our
4630 guard list unless we need to.
4632 o Minor bugfixes (guard nodes):
4633 - Weight guard selection by bandwidth, so that low-bandwidth nodes
4634 don't get overused as guards.
4636 o Minor bugfixes (directory):
4637 - Correctly count the number of authorities that recommend each
4638 version. Previously, we were under-counting by 1.
4639 - Fix a potential crash bug when we load many server descriptors at
4640 once and some of them make others of them obsolete. Fixes bug 458.
4642 o Minor bugfixes (hidden services):
4643 - Stop tearing down the whole circuit when the user asks for a
4644 connection to a port that the hidden service didn't configure.
4647 o Minor bugfixes (misc):
4648 - On Windows, we were preventing other processes from reading
4649 cached-routers while Tor was running. Reported by janbar.
4650 - Fix a possible (but very unlikely) bug in picking routers by
4651 bandwidth. Add a log message to confirm that it is in fact
4652 unlikely. Patch from lodger.
4653 - Backport a couple of memory leak fixes.
4654 - Backport miscellaneous cosmetic bugfixes.
4657 Changes in version 0.2.0.2-alpha - 2007-06-02
4658 o Major bugfixes on 0.2.0.1-alpha:
4659 - Fix an assertion failure related to servers without extra-info digests.
4660 Resolves bugs 441 and 442.
4662 o Minor features (directory):
4663 - Support "If-Modified-Since" when answering HTTP requests for
4664 directories, running-routers documents, and network-status documents.
4665 (There's no need to support it for router descriptors, since those
4666 are downloaded by descriptor digest.)
4668 o Minor build issues:
4669 - Clear up some MIPSPro compiler warnings.
4670 - When building from a tarball on a machine that happens to have SVK
4671 installed, report the micro-revision as whatever version existed
4672 in the tarball, not as "x".
4675 Changes in version 0.2.0.1-alpha - 2007-06-01
4676 This early development snapshot provides new features for people running
4677 Tor as both a client and a server (check out the new RelayBandwidth
4678 config options); lets Tor run as a DNS proxy; and generally moves us
4679 forward on a lot of fronts.
4681 o Major features, server usability:
4682 - New config options RelayBandwidthRate and RelayBandwidthBurst:
4683 a separate set of token buckets for relayed traffic. Right now
4684 relayed traffic is defined as answers to directory requests, and
4685 OR connections that don't have any local circuits on them.
4687 o Major features, client usability:
4688 - A client-side DNS proxy feature to replace the need for
4689 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
4690 for DNS requests on port 9999, use the Tor network to resolve them
4691 anonymously, and send the reply back like a regular DNS server.
4692 The code still only implements a subset of DNS.
4693 - Make PreferTunneledDirConns and TunnelDirConns work even when
4694 we have no cached directory info. This means Tor clients can now
4695 do all of their connections protected by TLS.
4697 o Major features, performance and efficiency:
4698 - Directory authorities accept and serve "extra info" documents for
4699 routers. These documents contain fields from router descriptors
4700 that aren't usually needed, and that use a lot of excess
4701 bandwidth. Once these fields are removed from router descriptors,
4702 the bandwidth savings should be about 60%. [Partially implements
4704 - Servers upload extra-info documents to any authority that accepts
4705 them. Authorities (and caches that have been configured to download
4706 extra-info documents) download them as needed. [Partially implements
4708 - Change the way that Tor buffers data that it is waiting to write.
4709 Instead of queueing data cells in an enormous ring buffer for each
4710 client->OR or OR->OR connection, we now queue cells on a separate
4711 queue for each circuit. This lets us use less slack memory, and
4712 will eventually let us be smarter about prioritizing different kinds
4714 - Use memory pools to allocate cells with better speed and memory
4715 efficiency, especially on platforms where malloc() is inefficient.
4716 - Stop reading on edge connections when their corresponding circuit
4717 buffers are full; start again as the circuits empty out.
4719 o Major features, other:
4720 - Add an HSAuthorityRecordStats option that hidden service authorities
4721 can use to track statistics of overall hidden service usage without
4722 logging information that would be very useful to an attacker.
4723 - Start work implementing multi-level keys for directory authorities:
4724 Add a standalone tool to generate key certificates. (Proposal 103.)
4727 - Directory authorities now call routers Stable if they have an
4728 uptime of at least 30 days, even if that's not the median uptime
4729 in the network. Implements proposal 107, suggested by Kevin Bauer
4732 o Minor fixes (resource management):
4733 - Count the number of open sockets separately from the number
4734 of active connection_t objects. This will let us avoid underusing
4735 our allocated connection limit.
4736 - We no longer use socket pairs to link an edge connection to an
4737 anonymous directory connection or a DirPort test connection.
4738 Instead, we track the link internally and transfer the data
4739 in-process. This saves two sockets per "linked" connection (at the
4740 client and at the server), and avoids the nasty Windows socketpair()
4742 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
4743 for every single inactive connection_t. Free items from the
4744 4k/16k-buffer free lists when they haven't been used for a while.
4746 o Minor features (build):
4747 - Make autoconf search for libevent, openssl, and zlib consistently.
4748 - Update deprecated macros in configure.in.
4749 - When warning about missing headers, tell the user to let us
4750 know if the compile succeeds anyway, so we can downgrade the
4752 - Include the current subversion revision as part of the version
4753 string: either fetch it directly if we're in an SVN checkout, do
4754 some magic to guess it if we're in an SVK checkout, or use
4755 the last-detected version if we're building from a .tar.gz.
4756 Use this version consistently in log messages.
4758 o Minor features (logging):
4759 - Always prepend "Bug: " to any log message about a bug.
4760 - Put a platform string (e.g. "Linux i686") in the startup log
4761 message, so when people paste just their logs, we know if it's
4762 OpenBSD or Windows or what.
4763 - When logging memory usage, break down memory used in buffers by
4766 o Minor features (directory system):
4767 - New config option V2AuthoritativeDirectory that all directory
4768 authorities should set. This will let future authorities choose
4769 not to serve V2 directory information.
4770 - Directory authorities allow multiple router descriptors and/or extra
4771 info documents to be uploaded in a single go. This will make
4772 implementing proposal 104 simpler.
4774 o Minor features (controller):
4775 - Add a new config option __DisablePredictedCircuits designed for
4776 use by the controller, when we don't want Tor to build any circuits
4778 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
4779 so we can exit from the middle of the circuit.
4780 - Implement "getinfo status/circuit-established".
4781 - Implement "getinfo status/version/..." so a controller can tell
4782 whether the current version is recommended, and whether any versions
4783 are good, and how many authorities agree. (Patch from shibz.)
4785 o Minor features (hidden services):
4786 - Allow multiple HiddenServicePort directives with the same virtual
4787 port; when they occur, the user is sent round-robin to one
4788 of the target ports chosen at random. Partially fixes bug 393 by
4789 adding limited ad-hoc round-robining.
4791 o Minor features (other):
4793 - Add a new AutomapHostsOnResolve option: when it is enabled, any
4794 resolve request for hosts matching a given pattern causes Tor to
4795 generate an internal virtual address mapping for that host. This
4796 allows DNSPort to work sensibly with hidden service users. By
4797 default, .exit and .onion addresses are remapped; the list of
4798 patterns can be reconfigured with AutomapHostsSuffixes.
4799 - Add an "-F" option to tor-resolve to force a resolve for a .onion
4800 address. Thanks to the AutomapHostsOnResolve option, this is no
4801 longer a completely silly thing to do.
4802 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
4803 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
4804 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
4805 minus 1 byte: the actual maximum declared bandwidth.
4808 - Removed support for the old binary "version 0" controller protocol.
4809 This has been deprecated since 0.1.1, and warnings have been issued
4810 since 0.1.2. When we encounter a v0 control message, we now send
4811 back an error and close the connection.
4812 - Remove the old "dns worker" server DNS code: it hasn't been default
4813 since 0.1.2.2-alpha, and all the servers seem to be using the new
4816 o Minor bugfixes (portability):
4817 - Even though Windows is equally happy with / and \ as path separators,
4818 try to use \ consistently on Windows and / consistently on Unix: it
4819 makes the log messages nicer.
4820 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
4821 - Read resolv.conf files correctly on platforms where read() returns
4822 partial results on small file reads.
4824 o Minor bugfixes (directory):
4825 - Correctly enforce that elements of directory objects do not appear
4826 more often than they are allowed to appear.
4827 - When we are reporting the DirServer line we just parsed, we were
4828 logging the second stanza of the key fingerprint, not the first.
4830 o Minor bugfixes (logging):
4831 - When we hit an EOF on a log (probably because we're shutting down),
4832 don't try to remove the log from the list: just mark it as
4833 unusable. (Bulletproofs against bug 222.)
4835 o Minor bugfixes (other):
4836 - In the exitlist script, only consider the most recently published
4837 server descriptor for each server. Also, when the user requests
4838 a list of servers that _reject_ connections to a given address,
4839 explicitly exclude the IPs that also have servers that accept
4840 connections to that address. (Resolves bug 405.)
4841 - Stop allowing hibernating servers to be "stable" or "fast".
4842 - On Windows, we were preventing other processes from reading
4843 cached-routers while Tor was running. (Reported by janbar)
4844 - Make the NodeFamilies config option work. (Reported by
4845 lodger -- it has never actually worked, even though we added it
4847 - Check return values from pthread_mutex functions.
4848 - Don't save non-general-purpose router descriptors to the disk cache,
4849 because we have no way of remembering what their purpose was when
4851 - Add even more asserts to hunt down bug 417.
4852 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
4853 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
4854 Add a log message to confirm that it is in fact unlikely.
4856 o Minor bugfixes (controller):
4857 - Make 'getinfo fingerprint' return a 551 error if we're not a
4858 server, so we match what the control spec claims we do. Reported
4860 - Fix a typo in an error message when extendcircuit fails that
4861 caused us to not follow the \r\n-based delimiter protocol. Reported
4864 o Code simplifications and refactoring:
4865 - Stop passing around circuit_t and crypt_path_t pointers that are
4866 implicit in other procedure arguments.
4867 - Drop the old code to choke directory connections when the
4868 corresponding OR connections got full: thanks to the cell queue
4869 feature, OR conns don't get full any more.
4870 - Make dns_resolve() handle attaching connections to circuits
4871 properly, so the caller doesn't have to.
4872 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
4873 - Keep the connection array as a dynamic smartlist_t, rather than as
4874 a fixed-sized array. This is important, as the number of connections
4875 is becoming increasingly decoupled from the number of sockets.
4878 Changes in version 0.1.2.14 - 2007-05-25
4879 Tor 0.1.2.14 changes the addresses of two directory authorities (this
4880 change especially affects those who serve or use hidden services),
4881 and fixes several other crash- and security-related bugs.
4883 o Directory authority changes:
4884 - Two directory authorities (moria1 and moria2) just moved to new
4885 IP addresses. This change will particularly affect those who serve
4886 or use hidden services.
4888 o Major bugfixes (crashes):
4889 - If a directory server runs out of space in the connection table
4890 as it's processing a begin_dir request, it will free the exit stream
4891 but leave it attached to the circuit, leading to unpredictable
4892 behavior. (Reported by seeess, fixes bug 425.)
4893 - Fix a bug in dirserv_remove_invalid() that would cause authorities
4894 to corrupt memory under some really unlikely scenarios.
4895 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
4896 - Avoid segfaults when reading from mmaped descriptor file. (Reported
4899 o Major bugfixes (security):
4900 - When choosing an entry guard for a circuit, avoid using guards
4901 that are in the same family as the chosen exit -- not just guards
4902 that are exactly the chosen exit. (Reported by lodger.)
4904 o Major bugfixes (resource management):
4905 - If a directory authority is down, skip it when deciding where to get
4906 networkstatus objects or descriptors. Otherwise we keep asking
4907 every 10 seconds forever. Fixes bug 384.
4908 - Count it as a failure if we fetch a valid network-status but we
4909 don't want to keep it. Otherwise we'll keep fetching it and keep
4910 not wanting to keep it. Fixes part of bug 422.
4911 - If all of our dirservers have given us bad or no networkstatuses
4912 lately, then stop hammering them once per minute even when we
4913 think they're failed. Fixes another part of bug 422.
4916 - Actually set the purpose correctly for descriptors inserted with
4918 - When we have k non-v2 authorities in our DirServer config,
4919 we ignored the last k authorities in the list when updating our
4921 - Correctly back-off from requesting router descriptors that we are
4922 having a hard time downloading.
4923 - Read resolv.conf files correctly on platforms where read() returns
4924 partial results on small file reads.
4925 - Don't rebuild the entire router store every time we get 32K of
4926 routers: rebuild it when the journal gets very large, or when
4927 the gaps in the store get very large.
4930 - When routers publish SVN revisions in their router descriptors,
4931 authorities now include those versions correctly in networkstatus
4933 - Warn when using a version of libevent before 1.3b to run a server on
4934 OSX or BSD: these versions interact badly with userspace threads.
4937 Changes in version 0.1.2.13 - 2007-04-24
4938 This release features some major anonymity fixes, such as safer path
4939 selection; better client performance; faster bootstrapping, better
4940 address detection, and better DNS support for servers; write limiting as
4941 well as read limiting to make servers easier to run; and a huge pile of
4942 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
4944 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
4945 of the Freenode IRC network, remembering his patience and vision for
4946 free speech on the Internet.
4949 - Fix a memory leak when we ask for "all" networkstatuses and we
4950 get one we don't recognize.
4951 - Add more asserts to hunt down bug 417.
4952 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
4955 Changes in version 0.1.2.12-rc - 2007-03-16
4957 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
4958 directory information requested inside Tor connections (i.e. via
4959 begin_dir cells). It only triggered when the same connection was
4960 serving other data at the same time. Reported by seeess.
4963 - When creating a circuit via the controller, send a 'launched'
4964 event when we're done, so we follow the spec better.
4967 Changes in version 0.1.2.11-rc - 2007-03-15
4968 o Minor bugfixes (controller), reported by daejees:
4969 - Correct the control spec to match how the code actually responds
4970 to 'getinfo addr-mappings/*'.
4971 - The control spec described a GUARDS event, but the code
4972 implemented a GUARD event. Standardize on GUARD, but let people
4976 Changes in version 0.1.2.10-rc - 2007-03-07
4977 o Major bugfixes (Windows):
4978 - Do not load the NT services library functions (which may not exist)
4979 just to detect if we're a service trying to shut down. Now we run
4980 on Win98 and friends again.
4982 o Minor bugfixes (other):
4983 - Clarify a couple of log messages.
4984 - Fix a misleading socks5 error number.
4987 Changes in version 0.1.2.9-rc - 2007-03-02
4988 o Major bugfixes (Windows):
4989 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
4990 of the usual GCC "%llu". This prevents a bug when saving 64-bit
4991 int configuration values: the high-order 32 bits would get
4992 truncated. In particular, we were being bitten by the default
4993 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
4994 and maybe also bug 397.)
4996 o Minor bugfixes (performance):
4997 - Use OpenSSL's AES implementation on platforms where it's faster.
4998 This could save us as much as 10% CPU usage.
5000 o Minor bugfixes (server):
5001 - Do not rotate onion key immediately after setting it for the first
5004 o Minor bugfixes (directory authorities):
5005 - Stop calling servers that have been hibernating for a long time
5006 "stable". Also, stop letting hibernating or obsolete servers affect
5007 uptime and bandwidth cutoffs.
5008 - Stop listing hibernating servers in the v1 directory.
5010 o Minor bugfixes (hidden services):
5011 - Upload hidden service descriptors slightly less often, to reduce
5012 load on authorities.
5014 o Minor bugfixes (other):
5015 - Fix an assert that could trigger if a controller quickly set then
5016 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
5017 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
5019 - Fix a potential race condition in the rpm installer. Found by
5021 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
5022 of 2 as indicating that the server is completely bad; it sometimes
5023 means that the server is just bad for the request in question. (may fix
5024 the last of bug 326.)
5025 - Disable encrypted directory connections when we don't have a server
5026 descriptor for the destination. We'll get this working again in
5030 Changes in version 0.1.2.8-beta - 2007-02-26
5031 o Major bugfixes (crashes):
5032 - Stop crashing when the controller asks us to resetconf more than
5033 one config option at once. (Vidalia 0.0.11 does this.)
5034 - Fix a crash that happened on Win98 when we're given command-line
5035 arguments: don't try to load NT service functions from advapi32.dll
5036 except when we need them. (Bug introduced in 0.1.2.7-alpha;
5038 - Fix a longstanding obscure crash bug that could occur when
5039 we run out of DNS worker processes. (Resolves bug 390.)
5041 o Major bugfixes (hidden services):
5042 - Correctly detect whether hidden service descriptor downloads are
5043 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
5045 o Major bugfixes (accounting):
5046 - When we start during an accounting interval before it's time to wake
5047 up, remember to wake up at the correct time. (May fix bug 342.)
5049 o Minor bugfixes (controller):
5050 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
5051 clear the corresponding on_circuit variable, and remember later
5052 that we don't need to send a redundant CLOSED event. (Resolves part
5054 - Report events where a resolve succeeded or where we got a socks
5055 protocol error correctly, rather than calling both of them
5057 - Change reported stream target addresses to IP consistently when
5058 we finally get the IP from an exit node.
5059 - Send log messages to the controller even if they happen to be very
5062 o Minor bugfixes (other):
5063 - Display correct results when reporting which versions are
5064 recommended, and how recommended they are. (Resolves bug 383.)
5065 - Improve our estimates for directory bandwidth to be less random:
5066 guess that an unrecognized directory will have the average bandwidth
5067 from all known directories, not that it will have the average
5068 bandwidth from those directories earlier than it on the list.
5069 - If we start a server with ClientOnly 1, then set ClientOnly to 0
5070 and hup, stop triggering an assert based on an empty onion_key.
5071 - On platforms with no working mmap() equivalent, don't warn the
5072 user when cached-routers doesn't exist.
5073 - Warn the user when mmap() [or its equivalent] fails for some reason
5074 other than file-not-found.
5075 - Don't warn the user when cached-routers.new doesn't exist: that's
5076 perfectly fine when starting up for the first time.
5077 - When EntryNodes are configured, rebuild the guard list to contain,
5078 in order: the EntryNodes that were guards before; the rest of the
5079 EntryNodes; the nodes that were guards before.
5080 - Mask out all signals in sub-threads; only the libevent signal
5081 handler should be processing them. This should prevent some crashes
5082 on some machines using pthreads. (Patch from coderman.)
5083 - Fix switched arguments on memset in the implementation of
5084 tor_munmap() for systems with no mmap() call.
5085 - When Tor receives a router descriptor that it asked for, but
5086 no longer wants (because it has received fresh networkstatuses
5087 in the meantime), do not warn the user. Cache the descriptor if
5088 we're a cache; drop it if we aren't.
5089 - Make earlier entry guards _really_ get retried when the network
5091 - On a malformed DNS reply, always give an error to the corresponding
5093 - Build with recent libevents on platforms that do not define the
5094 nonstandard types "u_int8_t" and friends.
5096 o Minor features (controller):
5097 - Warn the user when an application uses the obsolete binary v0
5098 control protocol. We're planning to remove support for it during
5099 the next development series, so it's good to give people some
5101 - Add STREAM_BW events to report per-entry-stream bandwidth
5102 use. (Patch from Robert Hogan.)
5103 - Rate-limit SIGNEWNYM signals in response to controllers that
5104 impolitely generate them for every single stream. (Patch from
5105 mwenge; closes bug 394.)
5106 - Make REMAP stream events have a SOURCE (cache or exit), and
5107 make them generated in every case where we get a successful
5108 connected or resolved cell.
5110 o Minor bugfixes (performance):
5111 - Call router_have_min_dir_info half as often. (This is showing up in
5112 some profiles, but not others.)
5113 - When using GCC, make log_debug never get called at all, and its
5114 arguments never get evaluated, when no debug logs are configured.
5115 (This is showing up in some profiles, but not others.)
5118 - Remove some never-implemented options. Mark PathlenCoinWeight as
5120 - Implement proposal 106: Stop requiring clients to have well-formed
5121 certificates; stop checking nicknames in certificates. (Clients
5122 have certificates so that they can look like Tor servers, but in
5123 the future we might want to allow them to look like regular TLS
5124 clients instead. Nicknames in certificates serve no purpose other
5125 than making our protocol easier to recognize on the wire.)
5126 - Revise messages on handshake failure again to be even more clear about
5127 which are incoming connections and which are outgoing.
5128 - Discard any v1 directory info that's over 1 month old (for
5129 directories) or over 1 week old (for running-routers lists).
5130 - Do not warn when individual nodes in the configuration's EntryNodes,
5131 ExitNodes, etc are down: warn only when all possible nodes
5132 are down. (Fixes bug 348.)
5133 - Always remove expired routers and networkstatus docs before checking
5134 whether we have enough information to build circuits. (Fixes
5136 - Put a lower-bound on MaxAdvertisedBandwidth.
5139 Changes in version 0.1.2.7-alpha - 2007-02-06
5140 o Major bugfixes (rate limiting):
5141 - Servers decline directory requests much more aggressively when
5142 they're low on bandwidth. Otherwise they end up queueing more and
5143 more directory responses, which can't be good for latency.
5144 - But never refuse directory requests from local addresses.
5145 - Fix a memory leak when sending a 503 response for a networkstatus
5147 - Be willing to read or write on local connections (e.g. controller
5148 connections) even when the global rate limiting buckets are empty.
5149 - If our system clock jumps back in time, don't publish a negative
5150 uptime in the descriptor. Also, don't let the global rate limiting
5151 buckets go absurdly negative.
5152 - Flush local controller connection buffers periodically as we're
5153 writing to them, so we avoid queueing 4+ megabytes of data before
5156 o Major bugfixes (NT services):
5157 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
5158 command-line flag so that admins can override the default by saying
5159 "tor --service install --user "SomeUser"". This will not affect
5160 existing installed services. Also, warn the user that the service
5161 will look for its configuration file in the service user's
5162 %appdata% directory. (We can't do the 'hardwire the user's appdata
5163 directory' trick any more, since we may not have read access to that
5166 o Major bugfixes (other):
5167 - Previously, we would cache up to 16 old networkstatus documents
5168 indefinitely, if they came from nontrusted authorities. Now we
5169 discard them if they are more than 10 days old.
5170 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
5172 - Detect and reject malformed DNS responses containing circular
5174 - If exits are rare enough that we're not marking exits as guards,
5175 ignore exit bandwidth when we're deciding the required bandwidth
5177 - When we're handling a directory connection tunneled over Tor,
5178 don't fill up internal memory buffers with all the data we want
5179 to tunnel; instead, only add it if the OR connection that will
5180 eventually receive it has some room for it. (This can lead to
5181 slowdowns in tunneled dir connections; a better solution will have
5184 o Minor bugfixes (dns):
5185 - Add some defensive programming to eventdns.c in an attempt to catch
5186 possible memory-stomping bugs.
5187 - Detect and reject DNS replies containing IPv4 or IPv6 records with
5188 an incorrect number of bytes. (Previously, we would ignore the
5190 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
5191 in the correct order, and doesn't crash.
5192 - Free memory held in recently-completed DNS lookup attempts on exit.
5193 This was not a memory leak, but may have been hiding memory leaks.
5194 - Handle TTL values correctly on reverse DNS lookups.
5195 - Treat failure to parse resolv.conf as an error.
5197 o Minor bugfixes (other):
5198 - Fix crash with "tor --list-fingerprint" (reported by seeess).
5199 - When computing clock skew from directory HTTP headers, consider what
5200 time it was when we finished asking for the directory, not what
5202 - Expire socks connections if they spend too long waiting for the
5203 handshake to finish. Previously we would let them sit around for
5204 days, if the connecting application didn't close them either.
5205 - And if the socks handshake hasn't started, don't send a
5206 "DNS resolve socks failed" handshake reply; just close it.
5207 - Stop using C functions that OpenBSD's linker doesn't like.
5208 - Don't launch requests for descriptors unless we have networkstatuses
5209 from at least half of the authorities. This delays the first
5210 download slightly under pathological circumstances, but can prevent
5211 us from downloading a bunch of descriptors we don't need.
5212 - Do not log IPs with TLS failures for incoming TLS
5213 connections. (Fixes bug 382.)
5214 - If the user asks to use invalid exit nodes, be willing to use
5216 - Stop using the reserved ac_cv namespace in our configure script.
5217 - Call stat() slightly less often; use fstat() when possible.
5218 - Refactor the way we handle pending circuits when an OR connection
5219 completes or fails, in an attempt to fix a rare crash bug.
5220 - Only rewrite a conn's address based on X-Forwarded-For: headers
5221 if it's a parseable public IP address; and stop adding extra quotes
5222 to the resulting address.
5225 - Weight directory requests by advertised bandwidth. Now we can
5226 let servers enable write limiting but still allow most clients to
5227 succeed at their directory requests. (We still ignore weights when
5228 choosing a directory authority; I hope this is a feature.)
5231 - Create a new file ReleaseNotes which was the old ChangeLog. The
5232 new ChangeLog file now includes the summaries for all development
5234 - Check for addresses with invalid characters at the exit as well
5235 as at the client, and warn less verbosely when they fail. You can
5236 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
5237 - Adapt a patch from goodell to let the contrib/exitlist script
5238 take arguments rather than require direct editing.
5239 - Inform the server operator when we decide not to advertise a
5240 DirPort due to AccountingMax enabled or a low BandwidthRate. It
5241 was confusing Zax, so now we're hopefully more helpful.
5242 - Bring us one step closer to being able to establish an encrypted
5243 directory tunnel without knowing a descriptor first. Still not
5244 ready yet. As part of the change, now assume we can use a
5245 create_fast cell if we don't know anything about a router.
5246 - Allow exit nodes to use nameservers running on ports other than 53.
5247 - Servers now cache reverse DNS replies.
5248 - Add an --ignore-missing-torrc command-line option so that we can
5249 get the "use sensible defaults if the configuration file doesn't
5250 exist" behavior even when specifying a torrc location on the command
5253 o Minor features (controller):
5254 - Track reasons for OR connection failure; make these reasons
5255 available via the controller interface. (Patch from Mike Perry.)
5256 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
5257 can learn when clients are sending malformed hostnames to Tor.
5258 - Clean up documentation for controller status events.
5259 - Add a REMAP status to stream events to note that a stream's
5260 address has changed because of a cached address or a MapAddress
5264 Changes in version 0.1.2.6-alpha - 2007-01-09
5266 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
5267 connection handles more than 4 gigs in either direction, we crash.
5268 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
5269 advertised exit node, somebody might try to exit from us when
5270 we're bootstrapping and before we've built our descriptor yet.
5271 Refuse the connection rather than crashing.
5274 - Warn if we (as a server) find that we've resolved an address that we
5275 weren't planning to resolve.
5276 - Warn that using select() on any libevent version before 1.1 will be
5277 unnecessarily slow (even for select()).
5278 - Flush ERR-level controller status events just like we currently
5279 flush ERR-level log events, so that a Tor shutdown doesn't prevent
5280 the controller from learning about current events.
5282 o Minor features (more controller status events):
5283 - Implement EXTERNAL_ADDRESS server status event so controllers can
5284 learn when our address changes.
5285 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
5286 can learn when directories reject our descriptor.
5287 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
5288 can learn when a client application is speaking a non-socks protocol
5290 - Implement DANGEROUS_SOCKS client status event so controllers
5291 can learn when a client application is leaking DNS addresses.
5292 - Implement BUG general status event so controllers can learn when
5293 Tor is unhappy about its internal invariants.
5294 - Implement CLOCK_SKEW general status event so controllers can learn
5295 when Tor thinks the system clock is set incorrectly.
5296 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
5297 server status events so controllers can learn when their descriptors
5298 are accepted by a directory.
5299 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
5300 server status events so controllers can learn about Tor's progress in
5301 deciding whether it's reachable from the outside.
5302 - Implement BAD_LIBEVENT general status event so controllers can learn
5303 when we have a version/method combination in libevent that needs to
5305 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
5306 and DNS_USELESS server status events so controllers can learn
5307 about changes to DNS server status.
5309 o Minor features (directory):
5310 - Authorities no longer recommend exits as guards if this would shift
5311 too much load to the exit nodes.
5314 Changes in version 0.1.2.5-alpha - 2007-01-06
5316 - Enable write limiting as well as read limiting. Now we sacrifice
5317 capacity if we're pushing out lots of directory traffic, rather
5318 than overrunning the user's intended bandwidth limits.
5319 - Include TLS overhead when counting bandwidth usage; previously, we
5320 would count only the bytes sent over TLS, but not the bytes used
5322 - Support running the Tor service with a torrc not in the same
5323 directory as tor.exe and default to using the torrc located in
5324 the %appdata%\Tor\ of the user who installed the service. Patch
5326 - Servers now check for the case when common DNS requests are going to
5327 wildcarded addresses (i.e. all getting the same answer), and change
5328 their exit policy to reject *:* if it's happening.
5329 - Implement BEGIN_DIR cells, so we can connect to the directory
5330 server via TLS to do encrypted directory requests rather than
5331 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
5332 config options if you like.
5334 o Minor features (config and docs):
5335 - Start using the state file to store bandwidth accounting data:
5336 the bw_accounting file is now obsolete. We'll keep generating it
5337 for a while for people who are still using 0.1.2.4-alpha.
5338 - Try to batch changes to the state file so that we do as few
5339 disk writes as possible while still storing important things in
5341 - The state file and the bw_accounting file get saved less often when
5342 the AvoidDiskWrites config option is set.
5343 - Make PIDFile work on Windows (untested).
5344 - Add internal descriptions for a bunch of configuration options:
5345 accessible via controller interface and in comments in saved
5347 - Reject *:563 (NNTPS) in the default exit policy. We already reject
5348 NNTP by default, so this seems like a sensible addition.
5349 - Clients now reject hostnames with invalid characters. This should
5350 avoid some inadvertent info leaks. Add an option
5351 AllowNonRFC953Hostnames to disable this behavior, in case somebody
5352 is running a private network with hosts called @, !, and #.
5353 - Add a maintainer script to tell us which options are missing
5354 documentation: "make check-docs".
5355 - Add a new address-spec.txt document to describe our special-case
5356 addresses: .exit, .onion, and .noconnnect.
5358 o Minor features (DNS):
5359 - Ongoing work on eventdns infrastructure: now it has dns server
5360 and ipv6 support. One day Tor will make use of it.
5361 - Add client-side caching for reverse DNS lookups.
5362 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
5363 - When we change nameservers or IP addresses, reset and re-launch
5364 our tests for DNS hijacking.
5366 o Minor features (directory):
5367 - Authorities now specify server versions in networkstatus. This adds
5368 about 2% to the size of compressed networkstatus docs, and allows
5369 clients to tell which servers support BEGIN_DIR and which don't.
5370 The implementation is forward-compatible with a proposed future
5371 protocol version scheme not tied to Tor versions.
5372 - DirServer configuration lines now have an orport= option so
5373 clients can open encrypted tunnels to the authorities without
5374 having downloaded their descriptors yet. Enabled for moria1,
5375 moria2, tor26, and lefkada now in the default configuration.
5376 - Directory servers are more willing to send a 503 "busy" if they
5377 are near their write limit, especially for v1 directory requests.
5378 Now they can use their limited bandwidth for actual Tor traffic.
5379 - Clients track responses with status 503 from dirservers. After a
5380 dirserver has given us a 503, we try not to use it until an hour has
5381 gone by, or until we have no dirservers that haven't given us a 503.
5382 - When we get a 503 from a directory, and we're not a server, we don't
5383 count the failure against the total number of failures allowed
5384 for the thing we're trying to download.
5385 - Report X-Your-Address-Is correctly from tunneled directory
5386 connections; don't report X-Your-Address-Is when it's an internal
5387 address; and never believe reported remote addresses when they're
5389 - Protect against an unlikely DoS attack on directory servers.
5390 - Add a BadDirectory flag to network status docs so that authorities
5391 can (eventually) tell clients about caches they believe to be
5394 o Minor features (controller):
5395 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
5396 - Reimplement GETINFO so that info/names stays in sync with the
5398 - Implement "GETINFO fingerprint".
5399 - Implement "SETEVENTS GUARD" so controllers can get updates on
5400 entry guard status as it changes.
5402 o Minor features (clean up obsolete pieces):
5403 - Remove some options that have been deprecated since at least
5404 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
5405 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
5407 - We no longer look for identity and onion keys in "identity.key" and
5408 "onion.key" -- these were replaced by secret_id_key and
5409 secret_onion_key in 0.0.8pre1.
5410 - We no longer require unrecognized directory entries to be
5413 o Major bugfixes (security):
5414 - Stop sending the HttpProxyAuthenticator string to directory
5415 servers when directory connections are tunnelled through Tor.
5416 - Clients no longer store bandwidth history in the state file.
5417 - Do not log introduction points for hidden services if SafeLogging
5419 - When generating bandwidth history, round down to the nearest
5420 1k. When storing accounting data, round up to the nearest 1k.
5421 - When we're running as a server, remember when we last rotated onion
5422 keys, so that we will rotate keys once they're a week old even if
5423 we never stay up for a week ourselves.
5425 o Major bugfixes (other):
5426 - Fix a longstanding bug in eventdns that prevented the count of
5427 timed-out resolves from ever being reset. This bug caused us to
5428 give up on a nameserver the third time it timed out, and try it
5429 10 seconds later... and to give up on it every time it timed out
5431 - Take out the '5 second' timeout from the connection retry
5432 schedule. Now the first connect attempt will wait a full 10
5433 seconds before switching to a new circuit. Perhaps this will help
5434 a lot. Based on observations from Mike Perry.
5435 - Fix a bug on the Windows implementation of tor_mmap_file() that
5436 would prevent the cached-routers file from ever loading. Reported
5440 - Fix an assert failure when a directory authority sets
5441 AuthDirRejectUnlisted and then receives a descriptor from an
5442 unlisted router. Reported by seeess.
5443 - Avoid a double-free when parsing malformed DirServer lines.
5444 - Fix a bug when a BSD-style PF socket is first used. Patch from
5446 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
5447 to resolve an address at a given exit node even when they ask for
5449 - Servers no longer ever list themselves in their "family" line,
5450 even if configured to do so. This makes it easier to configure
5451 family lists conveniently.
5452 - When running as a server, don't fall back to 127.0.0.1 when no
5453 nameservers are configured in /etc/resolv.conf; instead, make the
5454 user fix resolv.conf or specify nameservers explicitly. (Resolves
5456 - Stop accepting certain malformed ports in configured exit policies.
5457 - Don't re-write the fingerprint file every restart, unless it has
5459 - Stop warning when a single nameserver fails: only warn when _all_ of
5460 our nameservers have failed. Also, when we only have one nameserver,
5461 raise the threshold for deciding that the nameserver is dead.
5462 - Directory authorities now only decide that routers are reachable
5463 if their identity keys are as expected.
5464 - When the user uses bad syntax in the Log config line, stop
5465 suggesting other bad syntax as a replacement.
5466 - Correctly detect ipv6 DNS capability on OpenBSD.
5468 o Minor bugfixes (controller):
5469 - Report the circuit number correctly in STREAM CLOSED events. Bug
5470 reported by Mike Perry.
5471 - Do not report bizarre values for results of accounting GETINFOs
5472 when the last second's write or read exceeds the allotted bandwidth.
5473 - Report "unrecognized key" rather than an empty string when the
5474 controller tries to fetch a networkstatus that doesn't exist.
5477 Changes in version 0.1.1.26 - 2006-12-14
5478 o Security bugfixes:
5479 - Stop sending the HttpProxyAuthenticator string to directory
5480 servers when directory connections are tunnelled through Tor.
5481 - Clients no longer store bandwidth history in the state file.
5482 - Do not log introduction points for hidden services if SafeLogging
5486 - Fix an assert failure when a directory authority sets
5487 AuthDirRejectUnlisted and then receives a descriptor from an
5488 unlisted router (reported by seeess).
5491 Changes in version 0.1.2.4-alpha - 2006-12-03
5493 - Add support for using natd; this allows FreeBSDs earlier than
5494 5.1.2 to have ipfw send connections through Tor without using
5495 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
5498 - Make all connections to addresses of the form ".noconnect"
5499 immediately get closed. This lets application/controller combos
5500 successfully test whether they're talking to the same Tor by
5501 watching for STREAM events.
5502 - Make cross.sh cross-compilation script work even when autogen.sh
5503 hasn't been run. (Patch from Michael Mohr.)
5504 - Statistics dumped by -USR2 now include a breakdown of public key
5505 operations, for profiling.
5508 - Fix a major leak when directory authorities parse their
5509 approved-routers list, a minor memory leak when we fail to pick
5510 an exit node, and a few rare leaks on errors.
5511 - Handle TransPort connections even when the server sends data before
5512 the client sends data. Previously, the connection would just hang
5513 until the client sent data. (Patch from tup based on patch from
5515 - Avoid assert failure when our cached-routers file is empty on
5519 - Don't log spurious warnings when we see a circuit close reason we
5520 don't recognize; it's probably just from a newer version of Tor.
5521 - Have directory authorities allow larger amounts of drift in uptime
5522 without replacing the server descriptor: previously, a server that
5523 restarted every 30 minutes could have 48 "interesting" descriptors
5525 - Start linking to the Tor specification and Tor reference manual
5526 correctly in the Windows installer.
5527 - Add Vidalia to the OS X uninstaller script, so when we uninstall
5528 Tor/Privoxy we also uninstall Vidalia.
5529 - Resume building on Irix64, and fix a lot of warnings from its
5531 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
5532 when we're running as a client.
5535 Changes in version 0.1.1.25 - 2006-11-04
5537 - When a client asks us to resolve (rather than connect to)
5538 an address, and we have a cached answer, give them the cached
5539 answer. Previously, we would give them no answer at all.
5540 - We were building exactly the wrong circuits when we predict
5541 hidden service requirements, meaning Tor would have to build all
5542 its circuits on demand.
5543 - If none of our live entry guards have a high uptime, but we
5544 require a guard with a high uptime, try adding a new guard before
5545 we give up on the requirement. This patch should make long-lived
5546 connections more stable on average.
5547 - When testing reachability of our DirPort, don't launch new
5548 tests when there's already one in progress -- unreachable
5549 servers were stacking up dozens of testing streams.
5551 o Security bugfixes:
5552 - When the user sends a NEWNYM signal, clear the client-side DNS
5553 cache too. Otherwise we continue to act on previous information.
5556 - Avoid a memory corruption bug when creating a hash table for
5558 - Avoid possibility of controller-triggered crash when misusing
5559 certain commands from a v0 controller on platforms that do not
5560 handle printf("%s",NULL) gracefully.
5561 - Avoid infinite loop on unexpected controller input.
5562 - Don't log spurious warnings when we see a circuit close reason we
5563 don't recognize; it's probably just from a newer version of Tor.
5564 - Add Vidalia to the OS X uninstaller script, so when we uninstall
5565 Tor/Privoxy we also uninstall Vidalia.
5568 Changes in version 0.1.2.3-alpha - 2006-10-29
5570 - Prepare for servers to publish descriptors less often: never
5571 discard a descriptor simply for being too old until either it is
5572 recommended by no authorities, or until we get a better one for
5573 the same router. Make caches consider retaining old recommended
5574 routers for even longer.
5575 - If most authorities set a BadExit flag for a server, clients
5576 don't think of it as a general-purpose exit. Clients only consider
5577 authorities that advertise themselves as listing bad exits.
5578 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
5579 headers for content, so that we can work better in the presence of
5580 caching HTTP proxies.
5581 - Allow authorities to list nodes as bad exits by fingerprint or by
5584 o Minor features, controller:
5585 - Add a REASON field to CIRC events; for backward compatibility, this
5586 field is sent only to controllers that have enabled the extended
5587 event format. Also, add additional reason codes to explain why
5588 a given circuit has been destroyed or truncated. (Patches from
5590 - Add a REMOTE_REASON field to extended CIRC events to tell the
5591 controller about why a remote OR told us to close a circuit.
5592 - Stream events also now have REASON and REMOTE_REASON fields,
5593 working much like those for circuit events.
5594 - There's now a GETINFO ns/... field so that controllers can ask Tor
5595 about the current status of a router.
5596 - A new event type "NS" to inform a controller when our opinion of
5597 a router's status has changed.
5598 - Add a GETINFO events/names and GETINFO features/names so controllers
5599 can tell which events and features are supported.
5600 - A new CLEARDNSCACHE signal to allow controllers to clear the
5601 client-side DNS cache without expiring circuits.
5603 o Security bugfixes:
5604 - When the user sends a NEWNYM signal, clear the client-side DNS
5605 cache too. Otherwise we continue to act on previous information.
5608 - Avoid sending junk to controllers or segfaulting when a controller
5609 uses EVENT_NEW_DESC with verbose nicknames.
5610 - Stop triggering asserts if the controller tries to extend hidden
5611 service circuits (reported by mwenge).
5612 - Avoid infinite loop on unexpected controller input.
5613 - When the controller does a "GETINFO network-status", tell it
5614 about even those routers whose descriptors are very old, and use
5615 long nicknames where appropriate.
5616 - Change NT service functions to be loaded on demand. This lets us
5617 build with MinGW without breaking Tor for Windows 98 users.
5618 - Do DirPort reachability tests less often, since a single test
5619 chews through many circuits before giving up.
5620 - In the hidden service example in torrc.sample, stop recommending
5621 esoteric and discouraged hidden service options.
5622 - When stopping an NT service, wait up to 10 sec for it to actually
5623 stop. (Patch from Matt Edman; resolves bug 295.)
5624 - Fix handling of verbose nicknames with ORCONN controller events:
5625 make them show up exactly when requested, rather than exactly when
5627 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
5628 printing a duplicate "$" in the keys we send (reported by mwenge).
5629 - Correctly set maximum connection limit on Cygwin. (This time
5631 - Try to detect Windows correctly when cross-compiling.
5632 - Detect the size of the routers file correctly even if it is
5633 corrupted (on systems without mmap) or not page-aligned (on systems
5634 with mmap). This bug was harmless.
5635 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
5636 to open a stream fails; now we do in more cases. This should
5637 make clients able to find a good exit faster in some cases, since
5638 unhandleable requests will now get an error rather than timing out.
5639 - Resolve two memory leaks when rebuilding the on-disk router cache
5640 (reported by fookoowa).
5641 - Clean up minor code warnings suggested by the MIPSpro C compiler,
5642 and reported by some Centos users.
5643 - Controller signals now work on non-Unix platforms that don't define
5644 SIGUSR1 and SIGUSR2 the way we expect.
5645 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
5646 values before failing, and always enables eventdns.
5647 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
5648 Try to fix this in configure.in by checking for most functions
5649 before we check for libevent.
5652 Changes in version 0.1.2.2-alpha - 2006-10-07
5654 - Make our async eventdns library on-by-default for Tor servers,
5655 and plan to deprecate the separate dnsworker threads.
5656 - Add server-side support for "reverse" DNS lookups (using PTR
5657 records so clients can determine the canonical hostname for a given
5658 IPv4 address). Only supported by servers using eventdns; servers
5659 now announce in their descriptors whether they support eventdns.
5660 - Specify and implement client-side SOCKS5 interface for reverse DNS
5661 lookups (see doc/socks-extensions.txt).
5662 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
5663 connect to directory servers through Tor. Previously, clients needed
5664 to find Tor exits to make private connections to directory servers.
5665 - Avoid choosing Exit nodes for entry or middle hops when the
5666 total bandwidth available from non-Exit nodes is much higher than
5667 the total bandwidth available from Exit nodes.
5668 - Workaround for name servers (like Earthlink's) that hijack failing
5669 DNS requests and replace the no-such-server answer with a "helpful"
5670 redirect to an advertising-driven search portal. Also work around
5671 DNS hijackers who "helpfully" decline to hijack known-invalid
5672 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
5673 lets you turn it off.
5674 - Send out a burst of long-range padding cells once we've established
5675 that we're reachable. Spread them over 4 circuits, so hopefully
5676 a few will be fast. This exercises our bandwidth and bootstraps
5677 us into the directory more quickly.
5679 o New/improved config options:
5680 - Add new config option "ResolvConf" to let the server operator
5681 choose an alternate resolve.conf file when using eventdns.
5682 - Add an "EnforceDistinctSubnets" option to control our "exclude
5683 servers on the same /16" behavior. It's still on by default; this
5684 is mostly for people who want to operate private test networks with
5685 all the machines on the same subnet.
5686 - If one of our entry guards is on the ExcludeNodes list, or the
5687 directory authorities don't think it's a good guard, treat it as
5688 if it were unlisted: stop using it as a guard, and throw it off
5689 the guards list if it stays that way for a long time.
5690 - Allow directory authorities to be marked separately as authorities
5691 for the v1 directory protocol, the v2 directory protocol, and
5692 as hidden service directories, to make it easier to retire old
5693 authorities. V1 authorities should set "HSAuthoritativeDir 1"
5694 to continue being hidden service authorities too.
5695 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
5697 o Minor features, controller:
5698 - Fix CIRC controller events so that controllers can learn the
5699 identity digests of non-Named servers used in circuit paths.
5700 - Let controllers ask for more useful identifiers for servers. Instead
5701 of learning identity digests for un-Named servers and nicknames
5702 for Named servers, the new identifiers include digest, nickname,
5703 and indication of Named status. Off by default; see control-spec.txt
5704 for more information.
5705 - Add a "getinfo address" controller command so it can display Tor's
5706 best guess to the user.
5707 - New controller event to alert the controller when our server
5708 descriptor has changed.
5709 - Give more meaningful errors on controller authentication failure.
5711 o Minor features, other:
5712 - When asked to resolve a hostname, don't use non-exit servers unless
5713 requested to do so. This allows servers with broken DNS to be
5714 useful to the network.
5715 - Divide eventdns log messages into warn and info messages.
5716 - Reserve the nickname "Unnamed" for routers that can't pick
5717 a hostname: any router can call itself Unnamed; directory
5718 authorities will never allocate Unnamed to any particular router;
5719 clients won't believe that any router is the canonical Unnamed.
5720 - Only include function names in log messages for info/debug messages.
5721 For notice/warn/err, the content of the message should be clear on
5722 its own, and printing the function name only confuses users.
5723 - Avoid some false positives during reachability testing: don't try
5724 to test via a server that's on the same /24 as us.
5725 - If we fail to build a circuit to an intended enclave, and it's
5726 not mandatory that we use that enclave, stop wanting it.
5727 - When eventdns is enabled, allow multithreaded builds on NetBSD and
5728 OpenBSD. (We had previously disabled threads on these platforms
5729 because they didn't have working thread-safe resolver functions.)
5731 o Major bugfixes, anonymity/security:
5732 - If a client asked for a server by name, and there's a named server
5733 in our network-status but we don't have its descriptor yet, we
5734 could return an unnamed server instead.
5735 - Fix NetBSD bug that could allow someone to force uninitialized RAM
5736 to be sent to a server's DNS resolver. This only affects NetBSD
5737 and other platforms that do not bounds-check tolower().
5738 - Reject (most) attempts to use Tor circuits with length one. (If
5739 many people start using Tor as a one-hop proxy, exit nodes become
5740 a more attractive target for compromise.)
5741 - Just because your DirPort is open doesn't mean people should be
5742 able to remotely teach you about hidden service descriptors. Now
5743 only accept rendezvous posts if you've got HSAuthoritativeDir set.
5745 o Major bugfixes, other:
5746 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
5747 - When a client asks the server to resolve (not connect to)
5748 an address, and it has a cached answer, give them the cached answer.
5749 Previously, the server would give them no answer at all.
5750 - Allow really slow clients to not hang up five minutes into their
5751 directory downloads (suggested by Adam J. Richter).
5752 - We were building exactly the wrong circuits when we anticipated
5753 hidden service requirements, meaning Tor would have to build all
5754 its circuits on demand.
5755 - Avoid crashing when we mmap a router cache file of size 0.
5756 - When testing reachability of our DirPort, don't launch new
5757 tests when there's already one in progress -- unreachable
5758 servers were stacking up dozens of testing streams.
5760 o Minor bugfixes, correctness:
5761 - If we're a directory mirror and we ask for "all" network status
5762 documents, we would discard status documents from authorities
5764 - Avoid a memory corruption bug when creating a hash table for
5766 - Avoid controller-triggered crash when misusing certain commands
5767 from a v0 controller on platforms that do not handle
5768 printf("%s",NULL) gracefully.
5769 - Don't crash when a controller sends a third argument to an
5770 "extendcircuit" request.
5771 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
5772 response; fix error code when "getinfo dir/status/" fails.
5773 - Avoid crash when telling controller stream-status and a stream
5775 - Patch from Adam Langley to fix assert() in eventdns.c.
5776 - Fix a debug log message in eventdns to say "X resolved to Y"
5777 instead of "X resolved to X".
5778 - Make eventdns give strings for DNS errors, not just error numbers.
5779 - Track unreachable entry guards correctly: don't conflate
5780 'unreachable by us right now' with 'listed as down by the directory
5781 authorities'. With the old code, if a guard was unreachable by
5782 us but listed as running, it would clog our guard list forever.
5783 - Behave correctly in case we ever have a network with more than
5784 2GB/s total advertised capacity.
5785 - Make TrackExitHosts case-insensitive, and fix the behavior of
5786 ".suffix" TrackExitHosts items to avoid matching in the middle of
5788 - Finally fix the openssl warnings from newer gccs that believe that
5789 ignoring a return value is okay, but casting a return value and
5790 then ignoring it is a sign of madness.
5791 - Prevent the contrib/exitlist script from printing the same
5792 result more than once.
5793 - Patch from Steve Hildrey: Generate network status correctly on
5794 non-versioning dirservers.
5795 - Don't listen to the X-Your-Address-Is hint if you did the lookup
5796 via Tor; otherwise you'll think you're the exit node's IP address.
5798 o Minor bugfixes, performance:
5799 - Two small performance improvements on parsing descriptors.
5800 - Major performance improvement on inserting descriptors: change
5801 algorithm from O(n^2) to O(n).
5802 - Make the common memory allocation path faster on machines where
5803 malloc(0) returns a pointer.
5804 - Start remembering X-Your-Address-Is directory hints even if you're
5805 a client, so you can become a server more smoothly.
5806 - Avoid duplicate entries on MyFamily line in server descriptor.
5808 o Packaging, features:
5809 - Remove architecture from OS X builds. The official builds are
5810 now universal binaries.
5811 - The Debian package now uses --verify-config when (re)starting,
5812 to distinguish configuration errors from other errors.
5813 - Update RPMs to require libevent 1.1b.
5815 o Packaging, bugfixes:
5816 - Patches so Tor builds with MinGW on Windows.
5817 - Patches so Tor might run on Cygwin again.
5818 - Resume building on non-gcc compilers and ancient gcc. Resume
5819 building with the -O0 compile flag. Resume building cleanly on
5821 - Run correctly on OS X platforms with case-sensitive filesystems.
5822 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
5823 - Add autoconf checks so Tor can build on Solaris x86 again.
5826 - Documented (and renamed) ServerDNSSearchDomains and
5827 ServerDNSResolvConfFile options.
5828 - Be clearer that the *ListenAddress directives can be repeated
5832 Changes in version 0.1.1.24 - 2006-09-29
5834 - Allow really slow clients to not hang up five minutes into their
5835 directory downloads (suggested by Adam J. Richter).
5836 - Fix major performance regression from 0.1.0.x: instead of checking
5837 whether we have enough directory information every time we want to
5838 do something, only check when the directory information has changed.
5839 This should improve client CPU usage by 25-50%.
5840 - Don't crash if, after a server has been running for a while,
5841 it can't resolve its hostname.
5844 - Allow Tor to start when RunAsDaemon is set but no logs are set.
5845 - Don't crash when the controller receives a third argument to an
5846 "extendcircuit" request.
5847 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
5848 response; fix error code when "getinfo dir/status/" fails.
5849 - Fix configure.in to not produce broken configure files with
5850 more recent versions of autoconf. Thanks to Clint for his auto*
5852 - Fix security bug on NetBSD that could allow someone to force
5853 uninitialized RAM to be sent to a server's DNS resolver. This
5854 only affects NetBSD and other platforms that do not bounds-check
5856 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
5857 methods: these are known to be buggy.
5858 - If we're a directory mirror and we ask for "all" network status
5859 documents, we would discard status documents from authorities
5863 Changes in version 0.1.2.1-alpha - 2006-08-27
5865 - Add "eventdns" async dns library from Adam Langley, tweaked to
5866 build on OSX and Windows. Only enabled if you pass the
5867 --enable-eventdns argument to configure.
5868 - Allow servers with no hostname or IP address to learn their
5869 IP address by asking the directory authorities. This code only
5870 kicks in when you would normally have exited with a "no address"
5871 error. Nothing's authenticated, so use with care.
5872 - Rather than waiting a fixed amount of time between retrying
5873 application connections, we wait only 5 seconds for the first,
5874 10 seconds for the second, and 15 seconds for each retry after
5875 that. Hopefully this will improve the expected user experience.
5876 - Patch from Tup to add support for transparent AP connections:
5877 this basically bundles the functionality of trans-proxy-tor
5878 into the Tor mainline. Now hosts with compliant pf/netfilter
5879 implementations can redirect TCP connections straight to Tor
5880 without diverting through SOCKS. Needs docs.
5881 - Busy directory servers save lots of memory by spooling server
5882 descriptors, v1 directories, and v2 networkstatus docs to buffers
5883 as needed rather than en masse. Also mmap the cached-routers
5884 files, so we don't need to keep the whole thing in memory too.
5885 - Automatically avoid picking more than one node from the same
5886 /16 network when constructing a circuit.
5887 - Revise and clean up the torrc.sample that we ship with; add
5888 a section for BandwidthRate and BandwidthBurst.
5891 - Split circuit_t into origin_circuit_t and or_circuit_t, and
5892 split connection_t into edge, or, dir, control, and base structs.
5893 These will save quite a bit of memory on busy servers, and they'll
5894 also help us track down bugs in the code and bugs in the spec.
5895 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
5896 or later. Log when we are doing this, so we can diagnose it when
5897 it fails. (Also, recommend libevent 1.1b for kqueue and
5898 win32 methods; deprecate libevent 1.0b harder; make libevent
5899 recommendation system saner.)
5900 - Start being able to build universal binaries on OS X (thanks
5902 - Export the default exit policy via the control port, so controllers
5903 don't need to guess what it is / will be later.
5904 - Add a man page entry for ProtocolWarnings.
5905 - Add TestVia config option to the man page.
5906 - Remove even more protocol-related warnings from Tor server logs,
5907 such as bad TLS handshakes and malformed begin cells.
5908 - Stop fetching descriptors if you're not a dir mirror and you
5909 haven't tried to establish any circuits lately. [This currently
5910 causes some dangerous behavior, because when you start up again
5911 you'll use your ancient server descriptors.]
5912 - New DirPort behavior: if you have your dirport set, you download
5913 descriptors aggressively like a directory mirror, whether or not
5915 - Get rid of the router_retry_connections notion. Now routers
5916 no longer try to rebuild long-term connections to directory
5917 authorities, and directory authorities no longer try to rebuild
5918 long-term connections to all servers. We still don't hang up
5919 connections in these two cases though -- we need to look at it
5920 more carefully to avoid flapping, and we likely need to wait til
5921 0.1.1.x is obsolete.
5922 - Drop compatibility with obsolete Tors that permit create cells
5923 to have the wrong circ_id_type.
5924 - Re-enable per-connection rate limiting. Get rid of the "OP
5925 bandwidth" concept. Lay groundwork for "bandwidth classes" --
5926 separate global buckets that apply depending on what sort of conn
5928 - Start publishing one minute or so after we find our ORPort
5929 to be reachable. This will help reduce the number of descriptors
5930 we have for ourselves floating around, since it's quite likely
5931 other things (e.g. DirPort) will change during that minute too.
5932 - Fork the v1 directory protocol into its own spec document,
5933 and mark dir-spec.txt as the currently correct (v2) spec.
5936 - When we find our DirPort to be reachable, publish a new descriptor
5937 so we'll tell the world (reported by pnx).
5938 - Publish a new descriptor after we hup/reload. This is important
5939 if our config has changed such that we'll want to start advertising
5940 our DirPort now, etc.
5941 - Allow Tor to start when RunAsDaemon is set but no logs are set.
5942 - When we have a state file we cannot parse, tell the user and
5943 move it aside. Now we avoid situations where the user starts
5944 Tor in 1904, Tor writes a state file with that timestamp in it,
5945 the user fixes her clock, and Tor refuses to start.
5946 - Fix configure.in to not produce broken configure files with
5947 more recent versions of autoconf. Thanks to Clint for his auto*
5949 - "tor --verify-config" now exits with -1(255) or 0 depending on
5950 whether the config options are bad or good.
5951 - Resolve bug 321 when using dnsworkers: append a period to every
5952 address we resolve at the exit node, so that we do not accidentally
5953 pick up local addresses, and so that failing searches are retried
5954 in the resolver search domains. (This is already solved for
5955 eventdns.) (This breaks Blossom servers for now.)
5956 - If we are using an exit enclave and we can't connect, e.g. because
5957 its webserver is misconfigured to not listen on localhost, then
5958 back off and try connecting from somewhere else before we fail.
5961 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
5962 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
5963 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
5964 when the IP address is mapped through MapAddress to a hostname.
5965 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
5966 useless IPv6 DNS resolves.
5967 - Patch suggested by Karsten Loesing: respond to SIGNAL command
5968 before we execute the signal, in case the signal shuts us down.
5969 - Clean up AllowInvalidNodes man page entry.
5970 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
5971 - Add more asserts to track down an assert error on a windows Tor
5972 server with connection_add being called with socket == -1.
5973 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
5974 - Fix misleading log messages: an entry guard that is "unlisted",
5975 as well as not known to be "down" (because we've never heard
5976 of it), is not therefore "up".
5977 - Remove code to special-case "-cvs" ending, since it has not
5978 actually mattered since 0.0.9.
5979 - Make our socks5 handling more robust to broken socks clients:
5980 throw out everything waiting on the buffer in between socks
5981 handshake phases, since they can't possibly (so the theory
5982 goes) have predicted what we plan to respond to them.
5985 Changes in version 0.1.1.23 - 2006-07-30
5987 - Fast Tor servers, especially exit nodes, were triggering asserts
5988 due to a bug in handling the list of pending DNS resolves. Some
5989 bugs still remain here; we're hunting them.
5990 - Entry guards could crash clients by sending unexpected input.
5991 - More fixes on reachability testing: if you find yourself reachable,
5992 then don't ever make any client requests (so you stop predicting
5993 circuits), then hup or have your clock jump, then later your IP
5994 changes, you won't think circuits are working, so you won't try to
5995 test reachability, so you won't publish.
5998 - Avoid a crash if the controller does a resetconf firewallports
5999 and then a setconf fascistfirewall=1.
6000 - Avoid an integer underflow when the dir authority decides whether
6001 a router is stable: we might wrongly label it stable, and compute
6002 a slightly wrong median stability, when a descriptor is published
6004 - Fix a place where we might trigger an assert if we can't build our
6005 own server descriptor yet.
6008 Changes in version 0.1.1.22 - 2006-07-05
6010 - Fix a big bug that was causing servers to not find themselves
6011 reachable if they changed IP addresses. Since only 0.1.1.22+
6012 servers can do reachability testing correctly, now we automatically
6013 make sure to test via one of these.
6014 - Fix to allow clients and mirrors to learn directory info from
6015 descriptor downloads that get cut off partway through.
6016 - Directory authorities had a bug in deciding if a newly published
6017 descriptor was novel enough to make everybody want a copy -- a few
6018 servers seem to be publishing new descriptors many times a minute.
6020 - Fix a rare bug that was causing some servers to complain about
6021 "closing wedged cpuworkers" and skip some circuit create requests.
6022 - Make the Exit flag in directory status documents actually work.
6025 Changes in version 0.1.1.21 - 2006-06-10
6026 o Crash and assert fixes from 0.1.1.20:
6027 - Fix a rare crash on Tor servers that have enabled hibernation.
6028 - Fix a seg fault on startup for Tor networks that use only one
6029 directory authority.
6030 - Fix an assert from a race condition that occurs on Tor servers
6031 while exiting, where various threads are trying to log that they're
6032 exiting, and delete the logs, at the same time.
6033 - Make our unit tests pass again on certain obscure platforms.
6036 - Add support for building SUSE RPM packages.
6037 - Speed up initial bootstrapping for clients: if we are making our
6038 first ever connection to any entry guard, then don't mark it down
6040 - When only one Tor server in the network is labelled as a guard,
6041 and we've already picked him, we would cycle endlessly picking him
6042 again, being unhappy about it, etc. Now we specifically exclude
6043 current guards when picking a new guard.
6044 - Servers send create cells more reliably after the TLS connection
6045 is established: we were sometimes forgetting to send half of them
6046 when we had more than one pending.
6047 - If we get a create cell that asks us to extend somewhere, but the
6048 Tor server there doesn't match the expected digest, we now send
6049 a destroy cell back, rather than silently doing nothing.
6050 - Make options->RedirectExit work again.
6051 - Make cookie authentication for the controller work again.
6052 - Stop being picky about unusual characters in the arguments to
6053 mapaddress. It's none of our business.
6054 - Add a new config option "TestVia" that lets you specify preferred
6055 middle hops to use for test circuits. Perhaps this will let me
6056 debug the reachability problems better.
6058 o Log / documentation fixes:
6059 - If we're a server and some peer has a broken TLS certificate, don't
6060 log about it unless ProtocolWarnings is set, i.e., we want to hear
6061 about protocol violations by others.
6062 - Fix spelling of VirtualAddrNetwork in man page.
6063 - Add a better explanation at the top of the autogenerated torrc file
6064 about what happened to our old torrc.
6067 Changes in version 0.1.1.20 - 2006-05-23
6069 - Downgrade a log severity where servers complain that they're
6071 - Avoid a compile warning on FreeBSD.
6072 - Remove string size limit on NEWDESC messages; solve bug 291.
6073 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
6074 more thoroughly when we're running on windows.
6077 Changes in version 0.1.1.19-rc - 2006-05-03
6079 - Regenerate our local descriptor if it's dirty and we try to use
6080 it locally (e.g. if it changes during reachability detection).
6081 - If we setconf our ORPort to 0, we continued to listen on the
6082 old ORPort and receive connections.
6083 - Avoid a second warning about machine/limits.h on Debian
6085 - Be willing to add our own routerinfo into the routerlist.
6086 Now authorities will include themselves in their directories
6087 and network-statuses.
6088 - Stop trying to upload rendezvous descriptors to every
6089 directory authority: only try the v1 authorities.
6090 - Servers no longer complain when they think they're not
6091 registered with the directory authorities. There were too many
6093 - Backport dist-rpm changes so rpms can be built without errors.
6096 - Implement an option, VirtualAddrMask, to set which addresses
6097 get handed out in response to mapaddress requests. This works
6098 around a bug in tsocks where 127.0.0.0/8 is never socksified.
6101 Changes in version 0.1.1.18-rc - 2006-04-10
6103 - Work harder to download live network-statuses from all the
6104 directory authorities we know about. Improve the threshold
6105 decision logic so we're more robust to edge cases.
6106 - When fetching rendezvous descriptors, we were willing to ask
6107 v2 authorities too, which would always return 404.
6110 - Stop listing down or invalid nodes in the v1 directory. This will
6111 reduce its bulk by about 1/3, and reduce load on directory
6113 - When deciding whether a router is Fast or Guard-worthy, consider
6114 his advertised BandwidthRate and not just the BandwidthCapacity.
6115 - No longer ship INSTALL and README files -- they are useless now.
6116 - Force rpmbuild to behave and honor target_cpu.
6117 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
6118 - Start to include translated versions of the tor-doc-*.html
6119 files, along with the screenshots. Still needs more work.
6120 - Start sending back 512 and 451 errors if mapaddress fails,
6121 rather than not sending anything back at all.
6122 - When we fail to bind or listen on an incoming or outgoing
6123 socket, we should close it before failing. otherwise we just
6124 leak it. (thanks to weasel for finding.)
6125 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
6126 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
6127 - Make NoPublish (even though deprecated) work again.
6128 - Fix a minor security flaw where a versioning auth dirserver
6129 could list a recommended version many times in a row to make
6130 clients more convinced that it's recommended.
6131 - Fix crash bug if there are two unregistered servers running
6132 with the same nickname, one of them is down, and you ask for
6133 them by nickname in your EntryNodes or ExitNodes. Also, try
6134 to pick the one that's running rather than an arbitrary one.
6135 - Fix an infinite loop we could hit if we go offline for too long.
6136 - Complain when we hit WSAENOBUFS on recv() or write() too.
6137 Perhaps this will help us hunt the bug.
6138 - If you're not a versioning dirserver, don't put the string
6139 "client-versions \nserver-versions \n" in your network-status.
6140 - Lower the minimum required number of file descriptors to 1000,
6141 so we can have some overhead for Valgrind on Linux, where the
6142 default ulimit -n is 1024.
6145 - Add tor.dizum.com as the fifth authoritative directory server.
6146 - Add a new config option FetchUselessDescriptors, off by default,
6147 for when you plan to run "exitlist" on your client and you want
6148 to know about even the non-running descriptors.
6151 Changes in version 0.1.1.17-rc - 2006-03-28
6153 - Clients and servers since 0.1.1.10-alpha have been expiring
6154 connections whenever they are idle for 5 minutes and they *do*
6155 have circuits on them. Oops. With this new version, clients will
6156 discard their previous entry guard choices and avoid choosing
6157 entry guards running these flawed versions.
6158 - Fix memory leak when uncompressing concatenated zlib streams. This
6159 was causing substantial leaks over time on Tor servers.
6160 - The v1 directory was including servers as much as 48 hours old,
6161 because that's how the new routerlist->routers works. Now only
6162 include them if they're 20 hours old or less.
6165 - Resume building on irix64, netbsd 2.0, etc.
6166 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
6168 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
6169 and it is confusing some users.
6170 - Mirrors stop caching the v1 directory so often.
6171 - Make the max number of old descriptors that a cache will hold
6172 rise with the number of directory authorities, so we can scale.
6173 - Change our win32 uname() hack to be more forgiving about what
6174 win32 versions it thinks it's found.
6177 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
6179 - When the controller's *setconf commands fail, collect an error
6180 message in a string and hand it back to the controller.
6181 - Make the v2 dir's "Fast" flag based on relative capacity, just
6182 like "Stable" is based on median uptime. Name everything in the
6183 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
6184 - Log server fingerprint on startup, so new server operators don't
6185 have to go hunting around their filesystem for it.
6186 - Return a robots.txt on our dirport to discourage google indexing.
6187 - Let the controller ask for GETINFO dir/status/foo so it can ask
6188 directly rather than connecting to the dir port. Only works when
6189 dirport is set for now.
6191 o New config options rather than constants in the code:
6192 - SocksTimeout: How long do we let a socks connection wait
6193 unattached before we fail it?
6194 - CircuitBuildTimeout: Cull non-open circuits that were born
6195 at least this many seconds ago.
6196 - CircuitIdleTimeout: Cull open clean circuits that were born
6197 at least this many seconds ago.
6200 Changes in version 0.1.1.16-rc - 2006-03-18
6201 o Bugfixes on 0.1.1.15-rc:
6202 - Fix assert when the controller asks to attachstream a connect-wait
6203 or resolve-wait stream.
6204 - Now do address rewriting when the controller asks us to attach
6205 to a particular circuit too. This will let Blossom specify
6206 "moria2.exit" without having to learn what moria2's IP address is.
6207 - Make the "tor --verify-config" command-line work again, so people
6208 can automatically check if their torrc will parse.
6209 - Authoritative dirservers no longer require an open connection from
6210 a server to consider him "reachable". We need this change because
6211 when we add new auth dirservers, old servers won't know not to
6213 - Let Tor build on Sun CC again.
6214 - Fix an off-by-one buffer size in dirserv.c that magically never
6215 hit our three authorities but broke sjmurdoch's own tor network.
6216 - If we as a directory mirror don't know of any v1 directory
6217 authorities, then don't try to cache any v1 directories.
6218 - Stop warning about unknown servers in our family when they are
6219 given as hex digests.
6220 - Stop complaining as quickly to the server operator that he
6221 hasn't registered his nickname/key binding.
6222 - Various cleanups so we can add new V2 Auth Dirservers.
6223 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
6224 reflect the updated flags in our v2 dir protocol.
6225 - Resume allowing non-printable characters for exit streams (both
6226 for connecting and for resolving). Now we tolerate applications
6227 that don't follow the RFCs. But continue to block malformed names
6230 o Bugfixes on 0.1.0.x:
6231 - Fix assert bug in close_logs(): when we close and delete logs,
6232 remove them all from the global "logfiles" list.
6233 - Fix minor integer overflow in calculating when we expect to use up
6234 our bandwidth allocation before hibernating.
6235 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
6236 there are multiple SSLs installed with different versions.
6237 - When we try to be a server and Address is not explicitly set and
6238 our hostname resolves to a private IP address, try to use an
6239 interface address if it has a public address. Now Windows machines
6240 that think of themselves as localhost can work by default.
6243 - Let the controller ask for GETINFO dir/server/foo so it can ask
6244 directly rather than connecting to the dir port.
6245 - Let the controller tell us about certain router descriptors
6246 that it doesn't want Tor to use in circuits. Implement
6247 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
6248 - New config option SafeSocks to reject all application connections
6249 using unsafe socks protocols. Defaults to off.
6252 Changes in version 0.1.1.15-rc - 2006-03-11
6253 o Bugfixes and cleanups:
6254 - When we're printing strings from the network, don't try to print
6255 non-printable characters. This protects us against shell escape
6256 sequence exploits, and also against attacks to fool humans into
6257 misreading their logs.
6258 - Fix a bug where Tor would fail to establish any connections if you
6259 left it off for 24 hours and then started it: we were happy with
6260 the obsolete network statuses, but they all referred to router
6261 descriptors that were too old to fetch, so we ended up with no
6262 valid router descriptors.
6263 - Fix a seg fault in the controller's "getinfo orconn-status"
6264 command while listing status on incoming handshaking connections.
6265 Introduce a status name "NEW" for these connections.
6266 - If we get a linelist or linelist_s config option from the torrc
6267 (e.g. ExitPolicy) and it has no value, warn and skip rather than
6268 silently resetting it to its default.
6269 - Don't abandon entry guards until they've been down or gone for
6271 - Cleaner and quieter log messages.
6274 - New controller signal NEWNYM that makes new application requests
6276 - Add a new circuit purpose 'controller' to let the controller ask
6277 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
6278 controller command to let you specify the purpose if you're
6279 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
6280 command to let you change a circuit's purpose after it's been
6282 - Accept "private:*" in routerdesc exit policies; not generated yet
6283 because older Tors do not understand it.
6284 - Add BSD-style contributed startup script "rc.subr" from Peter
6288 Changes in version 0.1.1.14-alpha - 2006-02-20
6289 o Bugfixes on 0.1.1.x:
6290 - Don't die if we ask for a stdout or stderr log (even implicitly)
6291 and we're set to RunAsDaemon -- just warn.
6292 - We still had a few bugs in the OR connection rotation code that
6293 caused directory servers to slowly aggregate connections to other
6294 fast Tor servers. This time for sure!
6295 - Make log entries on Win32 include the name of the function again.
6296 - We were treating a pair of exit policies if they were equal even
6297 if one said accept and the other said reject -- causing us to
6298 not always publish a new descriptor since we thought nothing
6300 - Retry pending server downloads as well as pending networkstatus
6301 downloads when we unexpectedly get a socks request.
6302 - We were ignoring the IS_FAST flag in the directory status,
6303 meaning we were willing to pick trivial-bandwidth nodes for "fast"
6305 - If the controller's SAVECONF command fails (e.g. due to file
6306 permissions), let the controller know that it failed.
6309 - If we're trying to be a Tor server and running Windows 95/98/ME
6310 as a server, explain that we'll likely crash.
6311 - When we're a server, a client asks for an old-style directory,
6312 and our write bucket is empty, don't give it to him. This way
6313 small servers can continue to serve the directory *sometimes*,
6314 without getting overloaded.
6315 - Compress exit policies even more -- look for duplicate lines
6317 - Clients now honor the "guard" flag in the router status when
6318 picking entry guards, rather than looking at is_fast or is_stable.
6319 - Retain unrecognized lines in $DATADIR/state file, so that we can
6320 be forward-compatible.
6321 - Generate 18.0.0.0/8 address policy format in descs when we can;
6322 warn when the mask is not reducible to a bit-prefix.
6323 - Let the user set ControlListenAddress in the torrc. This can be
6324 dangerous, but there are some cases (like a secured LAN) where it
6326 - Split ReachableAddresses into ReachableDirAddresses and
6327 ReachableORAddresses, so we can restrict Dir conns to port 80
6328 and OR conns to port 443.
6329 - Now we can target arch and OS in rpm builds (contributed by
6330 Phobos). Also make the resulting dist-rpm filename match the
6332 - New config options to help controllers: FetchServerDescriptors
6333 and FetchHidServDescriptors for whether to fetch server
6334 info and hidserv info or let the controller do it, and
6335 PublishServerDescriptor and PublishHidServDescriptors.
6336 - Also let the controller set the __AllDirActionsPrivate config
6337 option if you want all directory fetches/publishes to happen via
6338 Tor (it assumes your controller bootstraps your circuits).
6341 Changes in version 0.1.0.17 - 2006-02-17
6342 o Crash bugfixes on 0.1.0.x:
6343 - When servers with a non-zero DirPort came out of hibernation,
6344 sometimes they would trigger an assert.
6346 o Other important bugfixes:
6347 - On platforms that don't have getrlimit (like Windows), we were
6348 artificially constraining ourselves to a max of 1024
6349 connections. Now just assume that we can handle as many as 15000
6350 connections. Hopefully this won't cause other problems.
6352 o Backported features:
6353 - When we're a server, a client asks for an old-style directory,
6354 and our write bucket is empty, don't give it to him. This way
6355 small servers can continue to serve the directory *sometimes*,
6356 without getting overloaded.
6357 - Whenever you get a 503 in response to a directory fetch, try
6358 once more. This will become important once servers start sending
6359 503's whenever they feel busy.
6360 - Fetch a new directory every 120 minutes, not every 40 minutes.
6361 Now that we have hundreds of thousands of users running the old
6362 directory algorithm, it's starting to hurt a lot.
6363 - Bump up the period for forcing a hidden service descriptor upload
6364 from 20 minutes to 1 hour.
6367 Changes in version 0.1.1.13-alpha - 2006-02-09
6368 o Crashes in 0.1.1.x:
6369 - When you tried to setconf ORPort via the controller, Tor would
6370 crash. So people using TorCP to become a server were sad.
6371 - Solve (I hope) the stack-smashing bug that we were seeing on fast
6372 servers. The problem appears to be something do with OpenSSL's
6373 random number generation, or how we call it, or something. Let me
6374 know if the crashes continue.
6375 - Turn crypto hardware acceleration off by default, until we find
6376 somebody smart who can test it for us. (It appears to produce
6377 seg faults in at least some cases.)
6378 - Fix a rare assert error when we've tried all intro points for
6379 a hidden service and we try fetching the service descriptor again:
6380 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
6383 - Fix a major load balance bug: we were round-robining in 16 KB
6384 chunks, and servers with bandwidthrate of 20 KB, while downloading
6385 a 600 KB directory, would starve their other connections. Now we
6386 try to be a bit more fair.
6387 - Dir authorities and mirrors were never expiring the newest
6388 descriptor for each server, causing memory and directory bloat.
6389 - Fix memory-bloating and connection-bloating bug on servers: We
6390 were never closing any connection that had ever had a circuit on
6391 it, because we were checking conn->n_circuits == 0, yet we had a
6392 bug that let it go negative.
6393 - Make Tor work using squid as your http proxy again -- squid
6394 returns an error if you ask for a URL that's too long, and it uses
6395 a really generic error message. Plus, many people are behind a
6396 transparent squid so they don't even realize it.
6397 - On platforms that don't have getrlimit (like Windows), we were
6398 artificially constraining ourselves to a max of 1024
6399 connections. Now just assume that we can handle as many as 15000
6400 connections. Hopefully this won't cause other problems.
6401 - Add a new config option ExitPolicyRejectPrivate which defaults to
6402 1. This means all exit policies will begin with rejecting private
6403 addresses, unless the server operator explicitly turns it off.
6406 - Clients no longer download descriptors for non-running
6408 - Before we add new directory authorities, we should make it
6409 clear that only v1 authorities should receive/publish hidden
6410 service descriptors.
6413 - As soon as we've fetched some more directory info, immediately
6414 try to download more server descriptors. This way we don't have
6415 a 10 second pause during initial bootstrapping.
6416 - Remove even more loud log messages that the server operator can't
6418 - When we're running an obsolete or un-recommended version, make
6419 the log message more clear about what the problem is and what
6420 versions *are* still recommended.
6421 - Provide a more useful warn message when our onion queue gets full:
6422 the CPU is too slow or the exit policy is too liberal.
6423 - Don't warn when we receive a 503 from a dirserver/cache -- this
6424 will pave the way for them being able to refuse if they're busy.
6425 - When we fail to bind a listener, try to provide a more useful
6426 log message: e.g., "Is Tor already running?"
6427 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
6428 Goldberg can prove things about our handshake protocol more
6430 - MaxConn has been obsolete for a while now. Document the ConnLimit
6431 config option, which is a *minimum* number of file descriptors
6432 that must be available else Tor refuses to start.
6433 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
6434 if you log to syslog and want something other than LOG_DAEMON.
6435 - Make dirservers generate a separate "guard" flag to mean,
6436 "would make a good entry guard". Make clients parse it and vote
6437 on it. Not used by clients yet.
6438 - Implement --with-libevent-dir option to ./configure. Also, improve
6439 search techniques to find libevent, and use those for openssl too.
6440 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
6441 - Only start testing reachability once we've established a
6442 circuit. This will make startup on dirservers less noisy.
6443 - Don't try to upload hidden service descriptors until we have
6444 established a circuit.
6445 - Fix the controller's "attachstream 0" command to treat conn like
6446 it just connected, doing address remapping, handling .exit and
6447 .onion idioms, and so on. Now we're more uniform in making sure
6448 that the controller hears about new and closing connections.
6451 Changes in version 0.1.1.12-alpha - 2006-01-11
6452 o Bugfixes on 0.1.1.x:
6453 - The fix to close duplicate server connections was closing all
6454 Tor client connections if they didn't establish a circuit
6455 quickly enough. Oops.
6456 - Fix minor memory issue (double-free) that happened on exit.
6458 o Bugfixes on 0.1.0.x:
6459 - Tor didn't warn when it failed to open a log file.
6462 Changes in version 0.1.1.11-alpha - 2006-01-10
6463 o Crashes in 0.1.1.x:
6464 - Include all the assert/crash fixes from 0.1.0.16.
6465 - If you start Tor and then quit very quickly, there were some
6466 races that tried to free things that weren't allocated yet.
6467 - Fix a rare memory stomp if you're running hidden services.
6468 - Fix segfault when specifying DirServer in config without nickname.
6469 - Fix a seg fault when you finish connecting to a server but at
6470 that moment you dump his server descriptor.
6471 - Extendcircuit and Attachstream controller commands would
6472 assert/crash if you don't give them enough arguments.
6473 - Fix an assert error when we're out of space in the connection_list
6474 and we try to post a hidden service descriptor (reported by weasel).
6475 - If you specify a relative torrc path and you set RunAsDaemon in
6476 your torrc, then it chdir()'s to the new directory. If you HUP,
6477 it tries to load the new torrc location, fails, and exits.
6478 The fix: no longer allow a relative path to torrc using -f.
6481 - Implement "entry guards": automatically choose a handful of entry
6482 nodes and stick with them for all circuits. Only pick new guards
6483 when the ones you have are unsuitable, and if the old guards
6484 become suitable again, switch back. This will increase security
6485 dramatically against certain end-point attacks. The EntryNodes
6486 config option now provides some hints about which entry guards you
6487 want to use most; and StrictEntryNodes means to only use those.
6488 - New directory logic: download by descriptor digest, not by
6489 fingerprint. Caches try to download all listed digests from
6490 authorities; clients try to download "best" digests from caches.
6491 This avoids partitioning and isolating attacks better.
6492 - Make the "stable" router flag in network-status be the median of
6493 the uptimes of running valid servers, and make clients pay
6494 attention to the network-status flags. Thus the cutoff adapts
6495 to the stability of the network as a whole, making IRC, IM, etc
6496 connections more reliable.
6499 - Tor servers with dynamic IP addresses were needing to wait 18
6500 hours before they could start doing reachability testing using
6501 the new IP address and ports. This is because they were using
6502 the internal descriptor to learn what to test, yet they were only
6503 rebuilding the descriptor once they decided they were reachable.
6504 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
6505 to download certain server descriptors, throw them away, and then
6506 fetch them again after 30 minutes. Now mirrors throw away these
6507 server descriptors so clients can't get them.
6508 - We were leaving duplicate connections to other ORs open for a week,
6509 rather than closing them once we detect a duplicate. This only
6510 really affected authdirservers, but it affected them a lot.
6511 - Spread the authdirservers' reachability testing over the entire
6512 testing interval, so we don't try to do 500 TLS's at once every
6516 - If the network is down, and we try to connect to a conn because
6517 we have a circuit in mind, and we timeout (30 seconds) because the
6518 network never answers, we were expiring the circuit, but we weren't
6519 obsoleting the connection or telling the entry_guards functions.
6520 - Some Tor servers process billions of cells per day. These statistics
6521 need to be uint64_t's.
6522 - Check for integer overflows in more places, when adding elements
6523 to smartlists. This could possibly prevent a buffer overflow
6524 on malicious huge inputs. I don't see any, but I haven't looked
6526 - ReachableAddresses kept growing new "reject *:*" lines on every
6528 - When you "setconf log" via the controller, it should remove all
6529 logs. We were automatically adding back in a "log notice stdout".
6530 - Newly bootstrapped Tor networks couldn't establish hidden service
6531 circuits until they had nodes with high uptime. Be more tolerant.
6532 - We were marking servers down when they could not answer every piece
6533 of the directory request we sent them. This was far too harsh.
6534 - Fix the torify (tsocks) config file to not use Tor for localhost
6536 - Directory authorities now go to the proper authority when asking for
6537 a networkstatus, even when they want a compressed one.
6538 - Fix a harmless bug that was causing Tor servers to log
6539 "Got an end because of misc error, but we're not an AP. Closing."
6540 - Authorities were treating their own descriptor changes as cosmetic,
6541 meaning the descriptor available in the network-status and the
6542 descriptor that clients downloaded were different.
6543 - The OS X installer was adding a symlink for tor_resolve but
6544 the binary was called tor-resolve (reported by Thomas Hardly).
6545 - Workaround a problem with some http proxies where they refuse GET
6546 requests that specify "Content-Length: 0" (reported by Adrian).
6547 - Fix wrong log message when you add a "HiddenServiceNodes" config
6548 line without any HiddenServiceDir line (reported by Chris Thomas).
6551 - Write the TorVersion into the state file so we have a prayer of
6552 keeping forward and backward compatibility.
6553 - Revive the FascistFirewall config option rather than eliminating it:
6554 now it's a synonym for ReachableAddresses *:80,*:443.
6555 - Clients choose directory servers from the network status lists,
6556 not from their internal list of router descriptors. Now they can
6557 go to caches directly rather than needing to go to authorities
6559 - Directory authorities ignore router descriptors that have only
6560 cosmetic differences: do this for 0.1.0.x servers now too.
6561 - Add a new flag to network-status indicating whether the server
6562 can answer v2 directory requests too.
6563 - Authdirs now stop whining so loudly about bad descriptors that
6564 they fetch from other dirservers. So when there's a log complaint,
6565 it's for sure from a freshly uploaded descriptor.
6566 - Reduce memory requirements in our structs by changing the order
6568 - There used to be two ways to specify your listening ports in a
6569 server descriptor: on the "router" line and with a separate "ports"
6570 line. Remove support for the "ports" line.
6571 - New config option "AuthDirRejectUnlisted" for auth dirservers as
6572 a panic button: if we get flooded with unusable servers we can
6573 revert to only listing servers in the approved-routers file.
6574 - Auth dir servers can now mark a fingerprint as "!reject" or
6575 "!invalid" in the approved-routers file (as its nickname), to
6576 refuse descriptors outright or include them but marked as invalid.
6577 - Servers store bandwidth history across restarts/crashes.
6578 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
6579 get a better idea of why their circuits failed. Not used yet.
6580 - Directory mirrors now cache up to 16 unrecognized network-status
6581 docs. Now we can add new authdirservers and they'll be cached too.
6582 - When picking a random directory, prefer non-authorities if any
6584 - New controller option "getinfo desc/all-recent" to fetch the
6585 latest server descriptor for every router that Tor knows about.
6588 Changes in version 0.1.0.16 - 2006-01-02
6589 o Crash bugfixes on 0.1.0.x:
6590 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
6591 corrupting the heap, losing FDs, or crashing when we need to resize
6592 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
6593 - It turns out sparc64 platforms crash on unaligned memory access
6594 too -- so detect and avoid this.
6595 - Handle truncated compressed data correctly (by detecting it and
6597 - Fix possible-but-unlikely free(NULL) in control.c.
6598 - When we were closing connections, there was a rare case that
6599 stomped on memory, triggering seg faults and asserts.
6600 - Avoid potential infinite recursion when building a descriptor. (We
6601 don't know that it ever happened, but better to fix it anyway.)
6602 - We were neglecting to unlink marked circuits from soon-to-close OR
6603 connections, which caused some rare scribbling on freed memory.
6604 - Fix a memory stomping race bug when closing the joining point of two
6605 rendezvous circuits.
6606 - Fix an assert in time parsing found by Steven Murdoch.
6608 o Other bugfixes on 0.1.0.x:
6609 - When we're doing reachability testing, provide more useful log
6610 messages so the operator knows what to expect.
6611 - Do not check whether DirPort is reachable when we are suppressing
6612 advertising it because of hibernation.
6613 - When building with -static or on Solaris, we sometimes needed -ldl.
6614 - When we're deciding whether a stream has enough circuits around
6615 that can handle it, count the freshly dirty ones and not the ones
6616 that are so dirty they won't be able to handle it.
6617 - When we're expiring old circuits, we had a logic error that caused
6618 us to close new rendezvous circuits rather than old ones.
6619 - Give a more helpful log message when you try to change ORPort via
6620 the controller: you should upgrade Tor if you want that to work.
6621 - We were failing to parse Tor versions that start with "Tor ".
6622 - Tolerate faulty streams better: when a stream fails for reason
6623 exitpolicy, stop assuming that the router is lying about his exit
6624 policy. When a stream fails for reason misc, allow it to retry just
6625 as if it was resolvefailed. When a stream has failed three times,
6626 reset its failure count so we can try again and get all three tries.
6629 Changes in version 0.1.1.10-alpha - 2005-12-11
6630 o Correctness bugfixes on 0.1.0.x:
6631 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
6632 corrupting the heap, losing FDs, or crashing when we need to resize
6633 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
6634 - Stop doing the complex voodoo overkill checking for insecure
6635 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
6636 - When we were closing connections, there was a rare case that
6637 stomped on memory, triggering seg faults and asserts.
6638 - We were neglecting to unlink marked circuits from soon-to-close OR
6639 connections, which caused some rare scribbling on freed memory.
6640 - When we're deciding whether a stream has enough circuits around
6641 that can handle it, count the freshly dirty ones and not the ones
6642 that are so dirty they won't be able to handle it.
6643 - Recover better from TCP connections to Tor servers that are
6644 broken but don't tell you (it happens!); and rotate TLS
6645 connections once a week.
6646 - When we're expiring old circuits, we had a logic error that caused
6647 us to close new rendezvous circuits rather than old ones.
6648 - Fix a scary-looking but apparently harmless bug where circuits
6649 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
6650 servers, and never switch to state CIRCUIT_STATE_OPEN.
6651 - When building with -static or on Solaris, we sometimes needed to
6653 - Give a useful message when people run Tor as the wrong user,
6654 rather than telling them to start chowning random directories.
6655 - We were failing to inform the controller about new .onion streams.
6657 o Security bugfixes on 0.1.0.x:
6658 - Refuse server descriptors if the fingerprint line doesn't match
6659 the included identity key. Tor doesn't care, but other apps (and
6660 humans) might actually be trusting the fingerprint line.
6661 - We used to kill the circuit when we receive a relay command we
6662 don't recognize. Now we just drop it.
6663 - Start obeying our firewall options more rigorously:
6664 . If we can't get to a dirserver directly, try going via Tor.
6665 . Don't ever try to connect (as a client) to a place our
6666 firewall options forbid.
6667 . If we specify a proxy and also firewall options, obey the
6668 firewall options even when we're using the proxy: some proxies
6669 can only proxy to certain destinations.
6670 - Fix a bug found by Lasse Overlier: when we were making internal
6671 circuits (intended to be cannibalized later for rendezvous and
6672 introduction circuits), we were picking them so that they had
6673 useful exit nodes. There was no need for this, and it actually
6674 aids some statistical attacks.
6675 - Start treating internal circuits and exit circuits separately.
6676 It's important to keep them separate because internal circuits
6677 have their last hops picked like middle hops, rather than like
6678 exit hops. So exiting on them will break the user's expectations.
6680 o Bugfixes on 0.1.1.x:
6681 - Take out the mis-feature where we tried to detect IP address
6682 flapping for people with DynDNS, and chose not to upload a new
6683 server descriptor sometimes.
6684 - Try to be compatible with OpenSSL 0.9.6 again.
6685 - Log fix: when the controller is logging about .onion addresses,
6686 sometimes it didn't include the ".onion" part of the address.
6687 - Don't try to modify options->DirServers internally -- if the
6688 user didn't specify any, just add the default ones directly to
6689 the trusted dirserver list. This fixes a bug where people running
6690 controllers would use SETCONF on some totally unrelated config
6691 option, and Tor would start yelling at them about changing their
6693 - Let the controller's redirectstream command specify a port, in
6694 case the controller wants to change that too.
6695 - When we requested a pile of server descriptors, we sometimes
6696 accidentally launched a duplicate request for the first one.
6697 - Bugfix for trackhostexits: write down the fingerprint of the
6698 chosen exit, not its nickname, because the chosen exit might not
6700 - When parsing foo.exit, if foo is unknown, and we are leaving
6701 circuits unattached, set the chosen_exit field and leave the
6702 address empty. This matters because controllers got confused
6704 - Directory authorities no longer try to download server
6705 descriptors that they know they will reject.
6707 o Features and updates:
6708 - Replace balanced trees with hash tables: this should make stuff
6709 significantly faster.
6710 - Resume using the AES counter-mode implementation that we ship,
6711 rather than OpenSSL's. Ours is significantly faster.
6712 - Many other CPU and memory improvements.
6713 - Add a new config option FastFirstHopPK (on by default) so clients
6714 do a trivial crypto handshake for their first hop, since TLS has
6715 already taken care of confidentiality and authentication.
6716 - Add a new config option TestSocks so people can see if their
6717 applications are using socks4, socks4a, socks5-with-ip, or
6718 socks5-with-hostname. This way they don't have to keep mucking
6719 with tcpdump and wondering if something got cached somewhere.
6720 - Warn when listening on a public address for socks. I suspect a
6721 lot of people are setting themselves up as open socks proxies,
6722 and they have no idea that jerks on the Internet are using them,
6723 since they simply proxy the traffic into the Tor network.
6724 - Add "private:*" as an alias in configuration for policies. Now
6725 you can simplify your exit policy rather than needing to list
6726 every single internal or nonroutable network space.
6727 - Add a new controller event type that allows controllers to get
6728 all server descriptors that were uploaded to a router in its role
6729 as authoritative dirserver.
6730 - Start shipping socks-extensions.txt, tor-doc-unix.html,
6731 tor-doc-server.html, and stylesheet.css in the tarball.
6732 - Stop shipping tor-doc.html in the tarball.
6735 Changes in version 0.1.1.9-alpha - 2005-11-15
6736 o Usability improvements:
6737 - Start calling it FooListenAddress rather than FooBindAddress,
6738 since few of our users know what it means to bind an address
6740 - Reduce clutter in server logs. We're going to try to make
6741 them actually usable now. New config option ProtocolWarnings that
6742 lets you hear about how _other Tors_ are breaking the protocol. Off
6744 - Divide log messages into logging domains. Once we put some sort
6745 of interface on this, it will let people looking at more verbose
6746 log levels specify the topics they want to hear more about.
6747 - Make directory servers return better http 404 error messages
6748 instead of a generic "Servers unavailable".
6749 - Check for even more Windows version flags when writing the platform
6750 string in server descriptors, and note any we don't recognize.
6751 - Clean up more of the OpenSSL memory when exiting, so we can detect
6752 memory leaks better.
6753 - Make directory authorities be non-versioning, non-naming by
6754 default. Now we can add new directory servers without requiring
6755 their operators to pay close attention.
6756 - When logging via syslog, include the pid whenever we provide
6757 a log entry. Suggested by Todd Fries.
6759 o Performance improvements:
6760 - Directory servers now silently throw away new descriptors that
6761 haven't changed much if the timestamps are similar. We do this to
6762 tolerate older Tor servers that upload a new descriptor every 15
6763 minutes. (It seemed like a good idea at the time.)
6764 - Inline bottleneck smartlist functions; use fast versions by default.
6765 - Add a "Map from digest to void*" abstraction digestmap_t so we
6766 can do less hex encoding/decoding. Use it in router_get_by_digest()
6767 to resolve a performance bottleneck.
6768 - Allow tor_gzip_uncompress to extract as much as possible from
6769 truncated compressed data. Try to extract as many
6770 descriptors as possible from truncated http responses (when
6771 DIR_PURPOSE_FETCH_ROUTERDESC).
6772 - Make circ->onionskin a pointer, not a static array. moria2 was using
6773 125000 circuit_t's after it had been up for a few weeks, which
6774 translates to 20+ megs of wasted space.
6775 - The private half of our EDH handshake keys are now chosen out
6776 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
6778 o Security improvements:
6779 - Start making directory caches retain old routerinfos, so soon
6780 clients can start asking by digest of descriptor rather than by
6781 fingerprint of server.
6782 - Add half our entropy from RAND_poll in OpenSSL. This knows how
6783 to use egd (if present), openbsd weirdness (if present), vms/os2
6784 weirdness (if we ever port there), and more in the future.
6786 o Bugfixes on 0.1.0.x:
6787 - Do round-robin writes of at most 16 kB per write. This might be
6788 more fair on loaded Tor servers, and it might resolve our Windows
6789 crash bug. It might also slow things down.
6790 - Our TLS handshakes were generating a single public/private
6791 keypair for the TLS context, rather than making a new one for
6792 each new connections. Oops. (But we were still rotating them
6793 periodically, so it's not so bad.)
6794 - When we were cannibalizing a circuit with a particular exit
6795 node in mind, we weren't checking to see if that exit node was
6796 already present earlier in the circuit. Oops.
6797 - When a Tor server's IP changes (e.g. from a dyndns address),
6798 upload a new descriptor so clients will learn too.
6799 - Really busy servers were keeping enough circuits open on stable
6800 connections that they were wrapping around the circuit_id
6801 space. (It's only two bytes.) This exposed a bug where we would
6802 feel free to reuse a circuit_id even if it still exists but has
6803 been marked for close. Try to fix this bug. Some bug remains.
6804 - If we would close a stream early (e.g. it asks for a .exit that
6805 we know would refuse it) but the LeaveStreamsUnattached config
6806 option is set by the controller, then don't close it.
6808 o Bugfixes on 0.1.1.8-alpha:
6809 - Fix a big pile of memory leaks, some of them serious.
6810 - Do not try to download a routerdesc if we would immediately reject
6812 - Resume inserting a newline between all router descriptors when
6813 generating (old style) signed directories, since our spec says
6815 - When providing content-type application/octet-stream for
6816 server descriptors using .z, we were leaving out the
6817 content-encoding header. Oops. (Everything tolerated this just
6818 fine, but that doesn't mean we need to be part of the problem.)
6819 - Fix a potential seg fault in getconf and getinfo using version 1
6820 of the controller protocol.
6821 - Avoid crash: do not check whether DirPort is reachable when we
6822 are suppressing it because of hibernation.
6823 - Make --hash-password not crash on exit.
6826 Changes in version 0.1.1.8-alpha - 2005-10-07
6827 o New features (major):
6828 - Clients don't download or use the directory anymore. Now they
6829 download and use network-statuses from the trusted dirservers,
6830 and fetch individual server descriptors as needed from mirrors.
6831 See dir-spec.txt for all the gory details.
6832 - Be more conservative about whether to advertise our DirPort.
6833 The main change is to not advertise if we're running at capacity
6834 and either a) we could hibernate or b) our capacity is low and
6835 we're using a default DirPort.
6836 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
6838 o New features (minor):
6839 - Try to be smart about when to retry network-status and
6840 server-descriptor fetches. Still needs some tuning.
6841 - Stop parsing, storing, or using running-routers output (but
6842 mirrors still cache and serve it).
6843 - Consider a threshold of versioning dirservers (dirservers who have
6844 an opinion about which Tor versions are still recommended) before
6845 deciding whether to warn the user that he's obsolete.
6846 - Dirservers can now reject/invalidate by key and IP, with the
6847 config options "AuthDirInvalid" and "AuthDirReject". This is
6848 useful since currently we automatically list servers as running
6849 and usable even if we know they're jerks.
6850 - Provide dire warnings to any users who set DirServer; move it out
6851 of torrc.sample and into torrc.complete.
6852 - Add MyFamily to torrc.sample in the server section.
6853 - Add nicknames to the DirServer line, so we can refer to them
6854 without requiring all our users to memorize their IP addresses.
6855 - When we get an EOF or a timeout on a directory connection, note
6856 how many bytes of serverdesc we are dropping. This will help
6857 us determine whether it is smart to parse incomplete serverdesc
6859 - Add a new function to "change pseudonyms" -- that is, to stop
6860 using any currently-dirty circuits for new streams, so we don't
6861 link new actions to old actions. Currently it's only called on
6862 HUP (or SIGNAL RELOAD).
6863 - On sighup, if UseHelperNodes changed to 1, use new circuits.
6864 - Start using RAND_bytes rather than RAND_pseudo_bytes from
6865 OpenSSL. Also, reseed our entropy every hour, not just at
6866 startup. And entropy in 512-bit chunks, not 160-bit chunks.
6868 o Fixes on 0.1.1.7-alpha:
6869 - Nobody ever implemented EVENT_ADDRMAP for control protocol
6870 version 0, so don't let version 0 controllers ask for it.
6871 - If you requested something with too many newlines via the
6872 v1 controller protocol, you could crash tor.
6873 - Fix a number of memory leaks, including some pretty serious ones.
6874 - Re-enable DirPort testing again, so Tor servers will be willing
6875 to advertise their DirPort if it's reachable.
6876 - On TLS handshake, only check the other router's nickname against
6877 its expected nickname if is_named is set.
6879 o Fixes forward-ported from 0.1.0.15:
6880 - Don't crash when we don't have any spare file descriptors and we
6881 try to spawn a dns or cpu worker.
6882 - Make the numbers in read-history and write-history into uint64s,
6883 so they don't overflow and publish negatives in the descriptor.
6886 - For the OS X package's modified privoxy config file, comment
6887 out the "logfile" line so we don't log everything passed
6889 - We were whining about using socks4 or socks5-with-local-lookup
6890 even when it's an IP in the "virtual" range we designed exactly
6892 - We were leaking some memory every time the client changes IPs.
6893 - Never call free() on tor_malloc()d memory. This will help us
6894 use dmalloc to detect memory leaks.
6895 - Check for named servers when looking them up by nickname;
6896 warn when we'recalling a non-named server by its nickname;
6897 don't warn twice about the same name.
6898 - Try to list MyFamily elements by key, not by nickname, and warn
6899 if we've not heard of the server.
6900 - Make windows platform detection (uname equivalent) smarter.
6901 - It turns out sparc64 doesn't like unaligned access either.
6904 Changes in version 0.1.0.15 - 2005-09-23
6905 o Bugfixes on 0.1.0.x:
6906 - Reject ports 465 and 587 (spam targets) in default exit policy.
6907 - Don't crash when we don't have any spare file descriptors and we
6908 try to spawn a dns or cpu worker.
6909 - Get rid of IgnoreVersion undocumented config option, and make us
6910 only warn, never exit, when we're running an obsolete version.
6911 - Don't try to print a null string when your server finds itself to
6912 be unreachable and the Address config option is empty.
6913 - Make the numbers in read-history and write-history into uint64s,
6914 so they don't overflow and publish negatives in the descriptor.
6915 - Fix a minor memory leak in smartlist_string_remove().
6916 - We were only allowing ourselves to upload a server descriptor at
6917 most every 20 minutes, even if it changed earlier than that.
6918 - Clean up log entries that pointed to old URLs.
6921 Changes in version 0.1.1.7-alpha - 2005-09-14
6922 o Fixes on 0.1.1.6-alpha:
6923 - Exit servers were crashing when people asked them to make a
6924 connection to an address not in their exit policy.
6925 - Looking up a non-existent stream for a v1 control connection would
6927 - Fix a seg fault if we ask a dirserver for a descriptor by
6928 fingerprint but he doesn't know about him.
6929 - SETCONF was appending items to linelists, not clearing them.
6930 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
6931 out and refuse the setconf if it would fail.
6932 - Downgrade the dirserver log messages when whining about
6936 - Add Peter Palfrader's check-tor script to tor/contrib/
6937 It lets you easily check whether a given server (referenced by
6938 nickname) is reachable by you.
6939 - Numerous changes to move towards client-side v2 directories. Not
6943 - If the user gave tor an odd number of command-line arguments,
6944 we were silently ignoring the last one. Now we complain and fail.
6945 [This wins the oldest-bug prize -- this bug has been present since
6946 November 2002, as released in Tor 0.0.0.]
6947 - Do not use unaligned memory access on alpha, mips, or mipsel.
6948 It *works*, but is very slow, so we treat them as if it doesn't.
6949 - Retry directory requests if we fail to get an answer we like
6950 from a given dirserver (we were retrying before, but only if
6951 we fail to connect).
6952 - When writing the RecommendedVersions line, sort them first.
6953 - When the client asked for a rendezvous port that the hidden
6954 service didn't want to provide, we were sending an IP address
6955 back along with the end cell. Fortunately, it was zero. But stop
6957 - Correct "your server is reachable" log entries to indicate that
6958 it was self-testing that told us so.
6961 Changes in version 0.1.1.6-alpha - 2005-09-09
6962 o Fixes on 0.1.1.5-alpha:
6963 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
6964 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
6965 - Fix bug with tor_memmem finding a match at the end of the string.
6966 - Make unit tests run without segfaulting.
6967 - Resolve some solaris x86 compile warnings.
6968 - Handle duplicate lines in approved-routers files without warning.
6969 - Fix bug where as soon as a server refused any requests due to his
6970 exit policy (e.g. when we ask for localhost and he tells us that's
6971 127.0.0.1 and he won't do it), we decided he wasn't obeying his
6972 exit policy using him for any exits.
6973 - Only do openssl hardware accelerator stuff if openssl version is
6976 o New controller features/fixes:
6977 - Add a "RESETCONF" command so you can set config options like
6978 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
6979 a config option in the torrc with no value, then it clears it
6980 entirely (rather than setting it to its default).
6981 - Add a "GETINFO config-file" to tell us where torrc is.
6982 - Avoid sending blank lines when GETINFO replies should be empty.
6983 - Add a QUIT command for the controller (for using it manually).
6984 - Fix a bug in SAVECONF that was adding default dirservers and
6985 other redundant entries to the torrc file.
6987 o Start on the new directory design:
6988 - Generate, publish, cache, serve new network-status format.
6989 - Publish individual descriptors (by fingerprint, by "all", and by
6991 - Publish client and server recommended versions separately.
6992 - Allow tor_gzip_uncompress() to handle multiple concatenated
6993 compressed strings. Serve compressed groups of router
6994 descriptors. The compression logic here could be more
6996 - Distinguish v1 authorities (all currently trusted directories)
6997 from v2 authorities (all trusted directories).
6998 - Change DirServers config line to note which dirs are v1 authorities.
6999 - Add configuration option "V1AuthoritativeDirectory 1" which
7000 moria1, moria2, and tor26 should set.
7001 - Remove option when getting directory cache to see whether they
7002 support running-routers; they all do now. Replace it with one
7003 to see whether caches support v2 stuff.
7006 - Dirservers now do their own external reachability testing of each
7007 Tor server, and only list them as running if they've been found to
7008 be reachable. We also send back warnings to the server's logs if
7009 it uploads a descriptor that we already believe is unreachable.
7010 - Implement exit enclaves: if we know an IP address for the
7011 destination, and there's a running Tor server at that address
7012 which allows exit to the destination, then extend the circuit to
7013 that exit first. This provides end-to-end encryption and end-to-end
7014 authentication. Also, if the user wants a .exit address or enclave,
7015 use 4 hops rather than 3, and cannibalize a general circ for it
7017 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
7018 controller. Also, rotate dns and cpu workers if the controller
7019 changes options that will affect them; and initialize the dns
7020 worker cache tree whether or not we start out as a server.
7021 - Only upload a new server descriptor when options change, 18
7022 hours have passed, uptime is reset, or bandwidth changes a lot.
7023 - Check [X-]Forwarded-For headers in HTTP requests when generating
7024 log messages. This lets people run dirservers (and caches) behind
7025 Apache but still know which IP addresses are causing warnings.
7027 o Config option changes:
7028 - Replace (Fascist)Firewall* config options with a new
7029 ReachableAddresses option that understands address policies.
7030 For example, "ReachableAddresses *:80,*:443"
7031 - Get rid of IgnoreVersion undocumented config option, and make us
7032 only warn, never exit, when we're running an obsolete version.
7033 - Make MonthlyAccountingStart config option truly obsolete now.
7036 - Reject ports 465 and 587 in the default exit policy, since
7037 people have started using them for spam too.
7038 - It turns out we couldn't bootstrap a network since we added
7039 reachability detection in 0.1.0.1-rc. Good thing the Tor network
7040 has never gone down. Add an AssumeReachable config option to let
7041 servers and dirservers bootstrap. When we're trying to build a
7042 high-uptime or high-bandwidth circuit but there aren't enough
7043 suitable servers, try being less picky rather than simply failing.
7044 - Our logic to decide if the OR we connected to was the right guy
7045 was brittle and maybe open to a mitm for unverified routers.
7046 - We weren't cannibalizing circuits correctly for
7047 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
7048 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
7049 build those from scratch. This should make hidden services faster.
7050 - Predict required circuits better, with an eye toward making hidden
7051 services faster on the service end.
7052 - Retry streams if the exit node sends back a 'misc' failure. This
7053 should result in fewer random failures. Also, after failing
7054 from resolve failed or misc, reset the num failures, so we give
7055 it a fair shake next time we try.
7056 - Clean up the rendezvous warn log msgs, and downgrade some to info.
7057 - Reduce severity on logs about dns worker spawning and culling.
7058 - When we're shutting down and we do something like try to post a
7059 server descriptor or rendezvous descriptor, don't complain that
7060 we seem to be unreachable. Of course we are, we're shutting down.
7061 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
7062 We don't use them yet, but maybe one day our DNS resolver will be
7063 able to discover them.
7064 - Make ContactInfo mandatory for authoritative directory servers.
7065 - Require server descriptors to list IPv4 addresses -- hostnames
7066 are no longer allowed. This also fixes some potential security
7067 problems with people providing hostnames as their address and then
7068 preferentially resolving them to partition users.
7069 - Change log line for unreachability to explicitly suggest /etc/hosts
7070 as the culprit. Also make it clearer what IP address and ports we're
7071 testing for reachability.
7072 - Put quotes around user-supplied strings when logging so users are
7073 more likely to realize if they add bad characters (like quotes)
7075 - Let auth dir servers start without specifying an Address config
7077 - Make unit tests (and other invocations that aren't the real Tor)
7078 run without launching listeners, creating subdirectories, and so on.
7081 Changes in version 0.1.1.5-alpha - 2005-08-08
7082 o Bugfixes included in 0.1.0.14.
7084 o Bugfixes on 0.1.0.x:
7085 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
7086 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
7087 it would silently using ignore the 6668.
7090 Changes in version 0.1.0.14 - 2005-08-08
7091 o Bugfixes on 0.1.0.x:
7092 - Fix the other half of the bug with crypto handshakes
7094 - Fix an assert trigger if you send a 'signal term' via the
7095 controller when it's listening for 'event info' messages.
7098 Changes in version 0.1.1.4-alpha - 2005-08-04
7099 o Bugfixes included in 0.1.0.13.
7102 - Improve tor_gettimeofday() granularity on windows.
7103 - Make clients regenerate their keys when their IP address changes.
7104 - Implement some more GETINFO goodness: expose helper nodes, config
7105 options, getinfo keys.
7108 Changes in version 0.1.0.13 - 2005-08-04
7109 o Bugfixes on 0.1.0.x:
7110 - Fix a critical bug in the security of our crypto handshakes.
7111 - Fix a size_t underflow in smartlist_join_strings2() that made
7112 it do bad things when you hand it an empty smartlist.
7113 - Fix Windows installer to ship Tor license (thanks to Aphex for
7114 pointing out this oversight) and put a link to the doc directory
7116 - Explicitly set no-unaligned-access for sparc: it turns out the
7117 new gcc's let you compile broken code, but that doesn't make it
7121 Changes in version 0.1.1.3-alpha - 2005-07-23
7122 o Bugfixes on 0.1.1.2-alpha:
7123 - Fix a bug in handling the controller's "post descriptor"
7125 - Fix several bugs in handling the controller's "extend circuit"
7127 - Fix a bug in handling the controller's "stream status" event.
7128 - Fix an assert failure if we have a controller listening for
7129 circuit events and we go offline.
7130 - Re-allow hidden service descriptors to publish 0 intro points.
7131 - Fix a crash when generating your hidden service descriptor if
7132 you don't have enough intro points already.
7134 o New features on 0.1.1.2-alpha:
7135 - New controller function "getinfo accounting", to ask how
7136 many bytes we've used in this time period.
7137 - Experimental support for helper nodes: a lot of the risk from
7138 a small static adversary comes because users pick new random
7139 nodes every time they rebuild a circuit. Now users will try to
7140 stick to the same small set of entry nodes if they can. Not
7141 enabled by default yet.
7143 o Bugfixes on 0.1.0.12:
7144 - If you're an auth dir server, always publish your dirport,
7145 even if you haven't yet found yourself to be reachable.
7146 - Fix a size_t underflow in smartlist_join_strings2() that made
7147 it do bad things when you hand it an empty smartlist.
7150 Changes in version 0.1.0.12 - 2005-07-18
7151 o New directory servers:
7152 - tor26 has changed IP address.
7154 o Bugfixes on 0.1.0.x:
7155 - Fix a possible double-free in tor_gzip_uncompress().
7156 - When --disable-threads is set, do not search for or link against
7158 - Don't trigger an assert if an authoritative directory server
7159 claims its dirport is 0.
7160 - Fix bug with removing Tor as an NT service: some people were
7161 getting "The service did not return an error." Thanks to Matt
7165 Changes in version 0.1.1.2-alpha - 2005-07-15
7166 o New directory servers:
7167 - tor26 has changed IP address.
7169 o Bugfixes on 0.1.0.x, crashes/leaks:
7170 - Port the servers-not-obeying-their-exit-policies fix from
7172 - Fix an fd leak in start_daemon().
7173 - On Windows, you can't always reopen a port right after you've
7174 closed it. So change retry_listeners() to only close and re-open
7175 ports that have changed.
7176 - Fix a possible double-free in tor_gzip_uncompress().
7178 o Bugfixes on 0.1.0.x, usability:
7179 - When tor_socketpair() fails in Windows, give a reasonable
7180 Windows-style errno back.
7181 - Let people type "tor --install" as well as "tor -install" when
7183 want to make it an NT service.
7184 - NT service patch from Matt Edman to improve error messages.
7185 - When the controller asks for a config option with an abbreviated
7186 name, give the full name in our response.
7187 - Correct the man page entry on TrackHostExitsExpire.
7188 - Looks like we were never delivering deflated (i.e. compressed)
7189 running-routers lists, even when asked. Oops.
7190 - When --disable-threads is set, do not search for or link against
7193 o Bugfixes on 0.1.1.x:
7194 - Fix a seg fault with autodetecting which controller version is
7198 - New hidden service descriptor format: put a version in it, and
7199 let people specify introduction/rendezvous points that aren't
7200 in "the directory" (which is subjective anyway).
7201 - Allow the DEBUG controller event to work again. Mark certain log
7202 entries as "don't tell this to controllers", so we avoid cycles.
7205 Changes in version 0.1.0.11 - 2005-06-30
7206 o Bugfixes on 0.1.0.x:
7207 - Fix major security bug: servers were disregarding their
7208 exit policies if clients behaved unexpectedly.
7209 - Make OS X init script check for missing argument, so we don't
7210 confuse users who invoke it incorrectly.
7211 - Fix a seg fault in "tor --hash-password foo".
7212 - The MAPADDRESS control command was broken.
7215 Changes in version 0.1.1.1-alpha - 2005-06-29
7217 - Make OS X init script check for missing argument, so we don't
7218 confuse users who invoke it incorrectly.
7219 - Fix a seg fault in "tor --hash-password foo".
7220 - Fix a possible way to DoS dirservers.
7221 - When we complain that your exit policy implicitly allows local or
7222 private address spaces, name them explicitly so operators can
7224 - Make the log message less scary when all the dirservers are
7225 temporarily unreachable.
7226 - We were printing the number of idle dns workers incorrectly when
7230 - Revised controller protocol (version 1) that uses ascii rather
7231 than binary. Add supporting libraries in python and java so you
7232 can use the controller from your applications without caring how
7234 - Spiffy new support for crypto hardware accelerators. Can somebody
7238 Changes in version 0.0.9.10 - 2005-06-16
7239 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
7240 - Refuse relay cells that claim to have a length larger than the
7241 maximum allowed. This prevents a potential attack that could read
7242 arbitrary memory (e.g. keys) from an exit server's process
7246 Changes in version 0.1.0.10 - 2005-06-14
7247 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
7248 libevent before 1.1a.
7251 Changes in version 0.1.0.9-rc - 2005-06-09
7253 - Reset buf->highwater every time buf_shrink() is called, not just on
7254 a successful shrink. This was causing significant memory bloat.
7255 - Fix buffer overflow when checking hashed passwords.
7256 - Security fix: if seeding the RNG on Win32 fails, quit.
7257 - Allow seeding the RNG on Win32 even when you're not running as
7259 - Disable threading on Solaris too. Something is wonky with it,
7260 cpuworkers, and reentrant libs.
7261 - Reenable the part of the code that tries to flush as soon as an
7262 OR outbuf has a full TLS record available. Perhaps this will make
7263 OR outbufs not grow as huge except in rare cases, thus saving lots
7264 of CPU time plus memory.
7265 - Reject malformed .onion addresses rather then passing them on as
7266 normal web requests.
7267 - Adapt patch from Adam Langley: fix possible memory leak in
7268 tor_lookup_hostname().
7269 - Initialize libevent later in the startup process, so the logs are
7270 already established by the time we start logging libevent warns.
7271 - Use correct errno on win32 if libevent fails.
7272 - Check and warn about known-bad/slow libevent versions.
7273 - Pay more attention to the ClientOnly config option.
7274 - Have torctl.in/tor.sh.in check for location of su binary (needed
7276 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
7277 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
7278 HttpProxyAuthenticator
7279 - Stop warning about sigpipes in the logs. We're going to
7280 pretend that getting these occassionally is normal and fine.
7281 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
7283 installer screens; and don't put stuff into StartupItems unless
7284 the user asks you to.
7285 - Require servers that use the default dirservers to have public IP
7286 addresses. We have too many servers that are configured with private
7287 IPs and their admins never notice the log entries complaining that
7288 their descriptors are being rejected.
7289 - Add OSX uninstall instructions. An actual uninstall script will
7293 Changes in version 0.1.0.8-rc - 2005-05-23
7295 - It turns out that kqueue on OS X 10.3.9 was causing kernel
7296 panics. Disable kqueue on all OS X Tors.
7297 - Fix RPM: remove duplicate line accidentally added to the rpm
7299 - Disable threads on openbsd too, since its gethostaddr is not
7301 - Tolerate libevent 0.8 since it still works, even though it's
7303 - Enable building on Red Hat 9.0 again.
7304 - Allow the middle hop of the testing circuit to be running any
7305 version, now that most of them have the bugfix to let them connect
7306 to unknown servers. This will allow reachability testing to work
7307 even when 0.0.9.7-0.0.9.9 become obsolete.
7308 - Handle relay cells with rh.length too large. This prevents
7309 a potential attack that could read arbitrary memory (maybe even
7310 keys) from the exit server's process.
7311 - We screwed up the dirport reachability testing when we don't yet
7312 have a cached version of the directory. Hopefully now fixed.
7313 - Clean up router_load_single_router() (used by the controller),
7314 so it doesn't seg fault on error.
7315 - Fix a minor memory leak when somebody establishes an introduction
7316 point at your Tor server.
7317 - If a socks connection ends because read fails, don't warn that
7318 you're not sending a socks reply back.
7321 - Add HttpProxyAuthenticator config option too, that works like
7322 the HttpsProxyAuthenticator config option.
7323 - Encode hashed controller passwords in hex instead of base64,
7324 to make it easier to write controllers.
7327 Changes in version 0.1.0.7-rc - 2005-05-17
7329 - Fix a bug in the OS X package installer that prevented it from
7330 installing on Tiger.
7331 - Fix a script bug in the OS X package installer that made it
7332 complain during installation.
7333 - Find libevent even if it's hiding in /usr/local/ and your
7334 CFLAGS and LDFLAGS don't tell you to look there.
7335 - Be able to link with libevent as a shared library (the default
7336 after 1.0d), even if it's hiding in /usr/local/lib and even
7337 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
7338 assuming you're running gcc. Otherwise fail and give a useful
7340 - Fix a bug in the RPM packager: set home directory for _tor to
7341 something more reasonable when first installing.
7342 - Free a minor amount of memory that is still reachable on exit.
7345 Changes in version 0.1.0.6-rc - 2005-05-14
7347 - Implement --disable-threads configure option. Disable threads on
7348 netbsd by default, because it appears to have no reentrant resolver
7350 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
7351 release (1.1) detects and disables kqueue if it's broken.
7352 - Append default exit policy before checking for implicit internal
7353 addresses. Now we don't log a bunch of complaints on startup
7354 when using the default exit policy.
7355 - Some people were putting "Address " in their torrc, and they had
7356 a buggy resolver that resolved " " to 0.0.0.0. Oops.
7357 - If DataDir is ~/.tor, and that expands to /.tor, then default to
7358 LOCALSTATEDIR/tor instead.
7359 - Fix fragmented-message bug in TorControl.py.
7360 - Resolve a minor bug which would prevent unreachable dirports
7361 from getting suppressed in the published descriptor.
7362 - When the controller gave us a new descriptor, we weren't resolving
7363 it immediately, so Tor would think its address was 0.0.0.0 until
7364 we fetched a new directory.
7365 - Fix an uppercase/lowercase case error in suppressing a bogus
7366 libevent warning on some Linuxes.
7369 - Begin scrubbing sensitive strings from logs by default. Turn off
7370 the config option SafeLogging if you need to do debugging.
7371 - Switch to a new buffer management algorithm, which tries to avoid
7372 reallocing and copying quite as much. In first tests it looks like
7373 it uses *more* memory on average, but less cpu.
7374 - First cut at support for "create-fast" cells. Clients can use
7375 these when extending to their first hop, since the TLS already
7376 provides forward secrecy and authentication. Not enabled on
7378 - When dirservers refuse a router descriptor, we now log its
7379 contactinfo, platform, and the poster's IP address.
7380 - Call tor_free_all instead of connections_free_all after forking, to
7381 save memory on systems that need to fork.
7382 - Whine at you if you're a server and you don't set your contactinfo.
7383 - Implement --verify-config command-line option to check if your torrc
7384 is valid without actually launching Tor.
7385 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
7386 rather than just rejecting it.
7389 Changes in version 0.1.0.5-rc - 2005-04-27
7391 - Stop trying to print a null pointer if an OR conn fails because
7392 we didn't like its cert.
7394 - Switch our internal buffers implementation to use a ring buffer,
7395 to hopefully improve performance for fast servers a lot.
7396 - Add HttpsProxyAuthenticator support (basic auth only), based
7397 on patch from Adam Langley.
7398 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
7399 the fast servers that have been joining lately.
7400 - Give hidden service accesses extra time on the first attempt,
7401 since 60 seconds is often only barely enough. This might improve
7403 - Improve performance for dirservers: stop re-parsing the whole
7404 directory every time you regenerate it.
7405 - Add more debugging info to help us find the weird dns freebsd
7406 pthreads bug; cleaner debug messages to help track future issues.
7409 Changes in version 0.0.9.9 - 2005-04-23
7410 o Bugfixes on 0.0.9.x:
7411 - If unofficial Tor clients connect and send weird TLS certs, our
7412 Tor server triggers an assert. This release contains a minimal
7413 backport from the broader fix that we put into 0.1.0.4-rc.
7416 Changes in version 0.1.0.4-rc - 2005-04-23
7418 - If unofficial Tor clients connect and send weird TLS certs, our
7419 Tor server triggers an assert. Stop asserting, and start handling
7420 TLS errors better in other situations too.
7421 - When the controller asks us to tell it about all the debug-level
7422 logs, it turns out we were generating debug-level logs while
7423 telling it about them, which turns into a bad loop. Now keep
7424 track of whether you're sending a debug log to the controller,
7425 and don't log when you are.
7426 - Fix the "postdescriptor" feature of the controller interface: on
7427 non-complete success, only say "done" once.
7429 - Clients are now willing to load balance over up to 2mB, not 1mB,
7430 of advertised bandwidth capacity.
7431 - Add a NoPublish config option, so you can be a server (e.g. for
7432 testing running Tor servers in other Tor networks) without
7433 publishing your descriptor to the primary dirservers.
7436 Changes in version 0.1.0.3-rc - 2005-04-08
7437 o Improvements on 0.1.0.2-rc:
7438 - Client now retries when streams end early for 'hibernating' or
7439 'resource limit' reasons, rather than failing them.
7440 - More automated handling for dirserver operators:
7441 - Automatically approve nodes running 0.1.0.2-rc or later,
7442 now that the the reachability detection stuff is working.
7443 - Now we allow two unverified servers with the same nickname
7444 but different keys. But if a nickname is verified, only that
7445 nickname+key are allowed.
7446 - If you're an authdirserver connecting to an address:port,
7447 and it's not the OR you were expecting, forget about that
7448 descriptor. If he *was* the one you were expecting, then forget
7449 about all other descriptors for that address:port.
7450 - Allow servers to publish descriptors from 12 hours in the future.
7451 Corollary: only whine about clock skew from the dirserver if
7452 he's a trusted dirserver (since now even verified servers could
7453 have quite wrong clocks).
7454 - Adjust maximum skew and age for rendezvous descriptors: let skew
7455 be 48 hours rather than 90 minutes.
7456 - Efficiency improvements:
7457 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
7458 it much faster to look up a circuit for each relay cell.
7459 - Remove most calls to assert_all_pending_dns_resolves_ok(),
7460 since they're eating our cpu on exit nodes.
7461 - Stop wasting time doing a case insensitive comparison for every
7462 dns name every time we do any lookup. Canonicalize the names to
7463 lowercase and be done with it.
7464 - Start sending 'truncated' cells back rather than destroy cells,
7465 if the circuit closes in front of you. This means we won't have
7466 to abandon partially built circuits.
7467 - Only warn once per nickname from add_nickname_list_to_smartlist
7468 per failure, so an entrynode or exitnode choice that's down won't
7470 - Put a note in the torrc about abuse potential with the default
7472 - Revise control spec and implementation to allow all log messages to
7473 be sent to controller with their severities intact (suggested by
7474 Matt Edman). Update TorControl to handle new log event types.
7475 - Provide better explanation messages when controller's POSTDESCRIPTOR
7477 - Stop putting nodename in the Platform string in server descriptors.
7478 It doesn't actually help, and it is confusing/upsetting some people.
7480 o Bugfixes on 0.1.0.2-rc:
7481 - We were printing the host mask wrong in exit policies in server
7482 descriptors. This isn't a critical bug though, since we were still
7483 obeying the exit policy internally.
7484 - Fix Tor when compiled with libevent but without pthreads: move
7485 connection_unregister() from _connection_free() to
7487 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
7488 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
7489 when we look through the connection array, we'll find any of the
7490 cpu/dnsworkers. This is no good.
7492 o Bugfixes on 0.0.9.8:
7493 - Fix possible bug on threading platforms (e.g. win32) which was
7494 leaking a file descriptor whenever a cpuworker or dnsworker died.
7495 - When using preferred entry or exit nodes, ignore whether the
7496 circuit wants uptime or capacity. They asked for the nodes, they
7498 - chdir() to your datadirectory at the *end* of the daemonize process,
7499 not the beginning. This was a problem because the first time you
7500 run tor, if your datadir isn't there, and you have runasdaemon set
7501 to 1, it will try to chdir to it before it tries to create it. Oops.
7502 - Handle changed router status correctly when dirserver reloads
7503 fingerprint file. We used to be dropping all unverified descriptors
7504 right then. The bug was hidden because we would immediately
7505 fetch a directory from another dirserver, which would include the
7506 descriptors we just dropped.
7507 - When we're connecting to an OR and he's got a different nickname/key
7508 than we were expecting, only complain loudly if we're an OP or a
7509 dirserver. Complaining loudly to the OR admins just confuses them.
7510 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
7511 artificially capped at 500kB.
7514 Changes in version 0.0.9.8 - 2005-04-07
7515 o Bugfixes on 0.0.9.x:
7516 - We have a bug that I haven't found yet. Sometimes, very rarely,
7517 cpuworkers get stuck in the 'busy' state, even though the cpuworker
7518 thinks of itself as idle. This meant that no new circuits ever got
7519 established. Here's a workaround to kill any cpuworker that's been
7520 busy for more than 100 seconds.
7523 Changes in version 0.1.0.2-rc - 2005-04-01
7524 o Bugfixes on 0.1.0.1-rc:
7525 - Fixes on reachability detection:
7526 - Don't check for reachability while hibernating.
7527 - If ORPort is reachable but DirPort isn't, still publish the
7528 descriptor, but zero out DirPort until it's found reachable.
7529 - When building testing circs for ORPort testing, use only
7530 high-bandwidth nodes, so fewer circuits fail.
7531 - Complain about unreachable ORPort separately from unreachable
7532 DirPort, so the user knows what's going on.
7533 - Make sure we only conclude ORPort reachability if we didn't
7534 initiate the conn. Otherwise we could falsely conclude that
7535 we're reachable just because we connected to the guy earlier
7536 and he used that same pipe to extend to us.
7537 - Authdirservers shouldn't do ORPort reachability detection,
7538 since they're in clique mode, so it will be rare to find a
7539 server not already connected to them.
7540 - When building testing circuits, always pick middle hops running
7541 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
7542 bug. (This is a kludge; it will go away when 0.0.9.x becomes
7544 - When we decide we're reachable, actually publish our descriptor
7546 - Fix bug in redirectstream in the controller.
7547 - Fix the state descriptor strings so logs don't claim edge streams
7548 are in a different state than they actually are.
7549 - Use recent libevent features when possible (this only really affects
7550 win32 and osx right now, because the new libevent with these
7551 features hasn't been released yet). Add code to suppress spurious
7553 - Prevent possible segfault in connection_close_unattached_ap().
7554 - Fix newlines on torrc in win32.
7555 - Improve error msgs when tor-resolve fails.
7557 o Improvements on 0.0.9.x:
7558 - New experimental script tor/contrib/ExerciseServer.py (needs more
7559 work) that uses the controller interface to build circuits and
7560 fetch pages over them. This will help us bootstrap servers that
7561 have lots of capacity but haven't noticed it yet.
7562 - New experimental script tor/contrib/PathDemo.py (needs more work)
7563 that uses the controller interface to let you choose whole paths
7565 "<hostname>.<path,separated by dots>.<length of path>.path"
7566 - When we've connected to an OR and handshaked but didn't like
7567 the result, we were closing the conn without sending destroy
7568 cells back for pending circuits. Now send those destroys.
7571 Changes in version 0.0.9.7 - 2005-04-01
7572 o Bugfixes on 0.0.9.x:
7573 - Fix another race crash bug (thanks to Glenn Fink for reporting).
7574 - Compare identity to identity, not to nickname, when extending to
7575 a router not already in the directory. This was preventing us from
7576 extending to unknown routers. Oops.
7577 - Make sure to create OS X Tor user in <500 range, so we aren't
7578 creating actual system users.
7579 - Note where connection-that-hasn't-sent-end was marked, and fix
7580 a few really loud instances of this harmless bug (it's fixed more
7584 Changes in version 0.1.0.1-rc - 2005-03-28
7586 - Add reachability testing. Your Tor server will automatically try
7587 to see if its ORPort and DirPort are reachable from the outside,
7588 and it won't upload its descriptor until it decides they are.
7589 - Handle unavailable hidden services better. Handle slow or busy
7590 hidden services better.
7591 - Add support for CONNECTing through https proxies, with "HttpsProxy"
7593 - New exit policy: accept most low-numbered ports, rather than
7594 rejecting most low-numbered ports.
7595 - More Tor controller support (still experimental). See
7596 http://tor.eff.org/doc/control-spec.txt for all the new features,
7597 including signals to emulate unix signals from any platform;
7598 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
7599 closestream; closecircuit; etc.
7600 - Make nt services work and start on startup on win32 (based on
7601 patch by Matt Edman).
7602 - Add a new AddressMap config directive to rewrite incoming socks
7603 addresses. This lets you, for example, declare an implicit
7604 required exit node for certain sites.
7605 - Add a new TrackHostExits config directive to trigger addressmaps
7606 for certain incoming socks addresses -- for sites that break when
7607 your exit keeps changing (based on patch by Mike Perry).
7608 - Redo the client-side dns cache so it's just an addressmap too.
7609 - Notice when our IP changes, and reset stats/uptime/reachability.
7610 - When an application is using socks5, give him the whole variety of
7611 potential socks5 responses (connect refused, host unreachable, etc),
7612 rather than just "success" or "failure".
7613 - A more sane version numbering system. See
7614 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
7615 - New contributed script "exitlist": a simple python script to
7616 parse directories and find Tor nodes that exit to listed
7618 - New contributed script "privoxy-tor-toggle" to toggle whether
7619 Privoxy uses Tor. Seems to be configured for Debian by default.
7620 - Report HTTP reasons to client when getting a response from directory
7621 servers -- so you can actually know what went wrong.
7622 - New config option MaxAdvertisedBandwidth which lets you advertise
7623 a low bandwidthrate (to not attract as many circuits) while still
7624 allowing a higher bandwidthrate in reality.
7626 o Robustness/stability fixes:
7627 - Make Tor use Niels Provos's libevent instead of its current
7628 poll-but-sometimes-select mess. This will let us use faster async
7629 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
7631 - pthread support now too. This was forced because when we forked,
7632 we ended up wasting a lot of duplicate ram over time. Also switch
7633 to foo_r versions of some library calls to allow reentry and
7635 - Better handling for heterogeneous / unreliable nodes:
7636 - Annotate circuits w/ whether they aim to contain high uptime nodes
7637 and/or high capacity nodes. When building circuits, choose
7639 - This means that every single node in an intro rend circuit,
7640 not just the last one, will have a minimum uptime.
7641 - New config option LongLivedPorts to indicate application streams
7642 that will want high uptime circuits.
7643 - Servers reset uptime when a dir fetch entirely fails. This
7644 hopefully reflects stability of the server's network connectivity.
7645 - If somebody starts his tor server in Jan 2004 and then fixes his
7646 clock, don't make his published uptime be a year.
7647 - Reset published uptime when you wake up from hibernation.
7648 - Introduce a notion of 'internal' circs, which are chosen without
7649 regard to the exit policy of the last hop. Intro and rendezvous
7650 circs must be internal circs, to avoid leaking information. Resolve
7651 and connect streams can use internal circs if they want.
7652 - New circuit pooling algorithm: make sure to have enough circs around
7653 to satisfy any predicted ports, and also make sure to have 2 internal
7654 circs around if we've required internal circs lately (and with high
7655 uptime if we've seen that lately too).
7656 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
7657 which describes how often we retry making new circuits if current
7658 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
7659 how long we're willing to make use of an already-dirty circuit.
7660 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
7661 circ as necessary, if there are any completed ones lying around
7662 when we try to launch one.
7663 - Make hidden services try to establish a rendezvous for 30 seconds,
7664 rather than for n (where n=3) attempts to build a circuit.
7665 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
7666 "ShutdownWaitLength".
7667 - Try to be more zealous about calling connection_edge_end when
7668 things go bad with edge conns in connection.c.
7669 - Revise tor-spec to add more/better stream end reasons.
7670 - Revise all calls to connection_edge_end to avoid sending "misc",
7671 and to take errno into account where possible.
7674 - Fix a race condition that can trigger an assert, when we have a
7675 pending create cell and an OR connection fails right then.
7676 - Fix several double-mark-for-close bugs, e.g. where we were finding
7677 a conn for a cell even if that conn is already marked for close.
7678 - Make sequence of log messages when starting on win32 with no config
7679 file more reasonable.
7680 - When choosing an exit node for a new non-internal circ, don't take
7681 into account whether it'll be useful for any pending x.onion
7682 addresses -- it won't.
7683 - Turn addr_policy_compare from a tristate to a quadstate; this should
7684 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
7685 for google.com" problem.
7686 - Make "platform" string in descriptor more accurate for Win32 servers,
7687 so it's not just "unknown platform".
7688 - Fix an edge case in parsing config options (thanks weasel).
7689 If they say "--" on the commandline, it's not an option.
7690 - Reject odd-looking addresses at the client (e.g. addresses that
7691 contain a colon), rather than having the server drop them because
7693 - tor-resolve requests were ignoring .exit if there was a working circuit
7694 they could use instead.
7695 - REUSEADDR on normal platforms means you can rebind to the port
7696 right after somebody else has let it go. But REUSEADDR on win32
7697 means to let you bind to the port _even when somebody else
7698 already has it bound_! So, don't do that on Win32.
7699 - Change version parsing logic: a version is "obsolete" if it is not
7700 recommended and (1) there is a newer recommended version in the
7701 same series, or (2) there are no recommended versions in the same
7702 series, but there are some recommended versions in a newer series.
7703 A version is "new" if it is newer than any recommended version in
7705 - Stop most cases of hanging up on a socks connection without sending
7709 - Require BandwidthRate to be at least 20kB/s for servers.
7710 - When a dirserver causes you to give a warn, mention which dirserver
7712 - New config option DirAllowPrivateAddresses for authdirservers.
7713 Now by default they refuse router descriptors that have non-IP or
7714 private-IP addresses.
7715 - Stop publishing socksport in the directory, since it's not
7716 actually meant to be public. For compatibility, publish a 0 there
7718 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
7719 smart" value, that is low for servers and high for clients.
7720 - If our clock jumps forward by 100 seconds or more, assume something
7721 has gone wrong with our network and abandon all not-yet-used circs.
7722 - Warn when exit policy implicitly allows local addresses.
7723 - If we get an incredibly skewed timestamp from a dirserver mirror
7724 that isn't a verified OR, don't warn -- it's probably him that's
7726 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
7727 cookies to disk and doesn't log each web request to disk. (Thanks
7728 to Brett Carrington for pointing this out.)
7729 - When a client asks us for a dir mirror and we don't have one,
7730 launch an attempt to get a fresh one.
7731 - If we're hibernating and we get a SIGINT, exit immediately.
7732 - Add --with-dmalloc ./configure option, to track memory leaks.
7733 - And try to free all memory on closing, so we can detect what
7735 - Cache local dns resolves correctly even when they're .exit
7737 - Give a better warning when some other server advertises an
7738 ORPort that is actually an apache running ssl.
7739 - Add "opt hibernating 1" to server descriptor to make it clearer
7740 whether the server is hibernating.
7743 Changes in version 0.0.9.6 - 2005-03-24
7744 o Bugfixes on 0.0.9.x (crashes and asserts):
7745 - Add new end stream reasons to maintainance branch. Fix bug where
7746 reason (8) could trigger an assert. Prevent bug from recurring.
7747 - Apparently win32 stat wants paths to not end with a slash.
7748 - Fix assert triggers in assert_cpath_layer_ok(), where we were
7749 blowing away the circuit that conn->cpath_layer points to, then
7750 checking to see if the circ is well-formed. Backport check to make
7751 sure we dont use the cpath on a closed connection.
7752 - Prevent circuit_resume_edge_reading_helper() from trying to package
7753 inbufs for marked-for-close streams.
7754 - Don't crash on hup if your options->address has become unresolvable.
7755 - Some systems (like OS X) sometimes accept() a connection and tell
7756 you the remote host is 0.0.0.0:0. If this happens, due to some
7757 other mis-features, we get confused; so refuse the conn for now.
7759 o Bugfixes on 0.0.9.x (other):
7760 - Fix harmless but scary "Unrecognized content encoding" warn message.
7761 - Add new stream error reason: TORPROTOCOL reason means "you are not
7762 speaking a version of Tor I understand; say bye-bye to your stream."
7763 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
7764 into the future, now that we are more tolerant of skew. This
7765 resolves a bug where a Tor server would refuse to cache a directory
7766 because all the directories it gets are too far in the future;
7767 yet the Tor server never logs any complaints about clock skew.
7768 - Mac packaging magic: make man pages useable, and do not overwrite
7769 existing torrc files.
7770 - Make OS X log happily to /var/log/tor/tor.log
7773 Changes in version 0.0.9.5 - 2005-02-22
7774 o Bugfixes on 0.0.9.x:
7775 - Fix an assert race at exit nodes when resolve requests fail.
7776 - Stop picking unverified dir mirrors--it only leads to misery.
7777 - Patch from Matt Edman to make NT services work better. Service
7778 support is still not compiled into the executable by default.
7779 - Patch from Dmitri Bely so the Tor service runs better under
7780 the win32 SYSTEM account.
7781 - Make tor-resolve actually work (?) on Win32.
7782 - Fix a sign bug when getrlimit claims to have 4+ billion
7783 file descriptors available.
7784 - Stop refusing to start when bandwidthburst == bandwidthrate.
7785 - When create cells have been on the onion queue more than five
7786 seconds, just send back a destroy and take them off the list.
7789 Changes in version 0.0.9.4 - 2005-02-03
7790 o Bugfixes on 0.0.9:
7791 - Fix an assert bug that took down most of our servers: when
7792 a server claims to have 1 GB of bandwidthburst, don't
7794 - Don't crash as badly if we have spawned the max allowed number
7795 of dnsworkers, or we're out of file descriptors.
7796 - Block more file-sharing ports in the default exit policy.
7797 - MaxConn is now automatically set to the hard limit of max
7798 file descriptors we're allowed (ulimit -n), minus a few for
7800 - Give a clearer message when servers need to raise their
7801 ulimit -n when they start running out of file descriptors.
7802 - SGI Compatibility patches from Jan Schaumann.
7803 - Tolerate a corrupt cached directory better.
7804 - When a dirserver hasn't approved your server, list which one.
7805 - Go into soft hibernation after 95% of the bandwidth is used,
7806 not 99%. This is especially important for daily hibernators who
7807 have a small accounting max. Hopefully it will result in fewer
7808 cut connections when the hard hibernation starts.
7809 - Load-balance better when using servers that claim more than
7810 800kB/s of capacity.
7811 - Make NT services work (experimental, only used if compiled in).
7814 Changes in version 0.0.9.3 - 2005-01-21
7815 o Bugfixes on 0.0.9:
7816 - Backport the cpu use fixes from main branch, so busy servers won't
7817 need as much processor time.
7818 - Work better when we go offline and then come back, or when we
7819 run Tor at boot before the network is up. We do this by
7820 optimistically trying to fetch a new directory whenever an
7821 application request comes in and we think we're offline -- the
7822 human is hopefully a good measure of when the network is back.
7823 - Backport some minimal hidserv bugfixes: keep rend circuits open as
7824 long as you keep using them; actually publish hidserv descriptors
7825 shortly after they change, rather than waiting 20-40 minutes.
7826 - Enable Mac startup script by default.
7827 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
7828 - When you update AllowUnverifiedNodes or FirewallPorts via the
7829 controller's setconf feature, we were always appending, never
7831 - When you update HiddenServiceDir via setconf, it was screwing up
7832 the order of reading the lines, making it fail.
7833 - Do not rewrite a cached directory back to the cache; otherwise we
7834 will think it is recent and not fetch a newer one on startup.
7835 - Workaround for webservers that lie about Content-Encoding: Tor
7836 now tries to autodetect compressed directories and compression
7837 itself. This lets us Proxypass dir fetches through apache.
7840 Changes in version 0.0.9.2 - 2005-01-04
7841 o Bugfixes on 0.0.9 (crashes and asserts):
7842 - Fix an assert on startup when the disk is full and you're logging
7844 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
7845 style address, then we'd crash.
7846 - Fix an assert trigger when the running-routers string we get from
7847 a dirserver is broken.
7848 - Make worker threads start and run on win32. Now win32 servers
7850 - Bandaid (not actually fix, but now it doesn't crash) an assert
7851 where the dns worker dies mysteriously and the main Tor process
7852 doesn't remember anything about the address it was resolving.
7854 o Bugfixes on 0.0.9 (Win32):
7855 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
7856 name out of the warning/assert messages.
7857 - Fix a superficial "unhandled error on read" bug on win32.
7858 - The win32 installer no longer requires a click-through for our
7859 license, since our Free Software license grants rights but does not
7861 - Win32: When connecting to a dirserver fails, try another one
7862 immediately. (This was already working for non-win32 Tors.)
7863 - Stop trying to parse $HOME on win32 when hunting for default
7865 - Make tor-resolve.c work on win32 by calling network_init().
7867 o Bugfixes on 0.0.9 (other):
7868 - Make 0.0.9.x build on Solaris again.
7869 - Due to a fencepost error, we were blowing away the \n when reporting
7870 confvalue items in the controller. So asking for multiple config
7871 values at once couldn't work.
7872 - When listing circuits that are pending on an opening OR connection,
7873 if we're an OR we were listing circuits that *end* at us as
7874 being pending on every listener, dns/cpu worker, etc. Stop that.
7875 - Dirservers were failing to create 'running-routers' or 'directory'
7876 strings if we had more than some threshold of routers. Fix them so
7877 they can handle any number of routers.
7878 - Fix a superficial "Duplicate mark for close" bug.
7879 - Stop checking for clock skew for OR connections, even for servers.
7880 - Fix a fencepost error that was chopping off the last letter of any
7881 nickname that is the maximum allowed nickname length.
7882 - Update URLs in log messages so they point to the new website.
7883 - Fix a potential problem in mangling server private keys while
7884 writing to disk (not triggered yet, as far as we know).
7885 - Include the licenses for other free software we include in Tor,
7886 now that we're shipping binary distributions more regularly.
7889 Changes in version 0.0.9.1 - 2004-12-15
7890 o Bugfixes on 0.0.9:
7891 - Make hibernation actually work.
7892 - Make HashedControlPassword config option work.
7893 - When we're reporting event circuit status to a controller,
7894 don't use the stream status code.
7897 Changes in version 0.0.9 - 2004-12-12
7899 - Clean up manpage and torrc.sample file.
7900 - Clean up severities and text of log warnings.
7902 - Make servers trigger an assert when they enter hibernation.
7905 Changes in version 0.0.9rc7 - 2004-12-08
7906 o Bugfixes on 0.0.9rc:
7907 - Fix a stack-trashing crash when an exit node begins hibernating.
7908 - Avoid looking at unallocated memory while considering which
7909 ports we need to build circuits to cover.
7910 - Stop a sigpipe: when an 'end' cell races with eof from the app,
7911 we shouldn't hold-open-until-flush if the eof arrived first.
7912 - Fix a bug with init_cookie_authentication() in the controller.
7913 - When recommending new-format log lines, if the upper bound is
7914 LOG_ERR, leave it implicit.
7916 o Bugfixes on 0.0.8.1:
7917 - Fix a whole slew of memory leaks.
7918 - Fix isspace() and friends so they still make Solaris happy
7919 but also so they don't trigger asserts on win32.
7920 - Fix parse_iso_time on platforms without strptime (eg win32).
7921 - win32: tolerate extra "readable" events better.
7922 - win32: when being multithreaded, leave parent fdarray open.
7923 - Make unit tests work on win32.
7926 Changes in version 0.0.9rc6 - 2004-12-06
7927 o Bugfixes on 0.0.9pre:
7928 - Clean up some more integer underflow opportunities (not exploitable
7930 - While hibernating, hup should not regrow our listeners.
7931 - Send an end to the streams we close when we hibernate, rather
7932 than just chopping them off.
7933 - React to eof immediately on non-open edge connections.
7935 o Bugfixes on 0.0.8.1:
7936 - Calculate timeout for waiting for a connected cell from the time
7937 we sent the begin cell, not from the time the stream started. If
7938 it took a long time to establish the circuit, we would time out
7939 right after sending the begin cell.
7940 - Fix router_compare_addr_to_addr_policy: it was not treating a port
7941 of * as always matching, so we were picking reject *:* nodes as
7942 exit nodes too. Oops.
7945 - New circuit building strategy: keep a list of ports that we've
7946 used in the past 6 hours, and always try to have 2 circuits open
7947 or on the way that will handle each such port. Seed us with port
7948 80 so web users won't complain that Tor is "slow to start up".
7949 - Make kill -USR1 dump more useful stats about circuits.
7950 - When warning about retrying or giving up, print the address, so
7951 the user knows which one it's talking about.
7952 - If you haven't used a clean circuit in an hour, throw it away,
7953 just to be on the safe side. (This means after 6 hours a totally
7954 unused Tor client will have no circuits open.)
7957 Changes in version 0.0.9rc5 - 2004-12-01
7958 o Bugfixes on 0.0.8.1:
7959 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
7960 - Let resolve conns retry/expire also, rather than sticking around
7962 - If we are using select, make sure we stay within FD_SETSIZE.
7964 o Bugfixes on 0.0.9pre:
7965 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
7966 but doesn't seem to be currently; thanks to Ilja van Sprundel for
7968 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
7969 instead. Impose minima and maxima for all *Period options; impose
7970 even tighter maxima for fetching if we are a caching dirserver.
7971 Clip rather than rejecting.
7972 - Fetch cached running-routers from servers that serve it (that is,
7973 authdirservers and servers running 0.0.9rc5-cvs or later.)
7976 - Accept *:706 (silc) in default exit policy.
7977 - Implement new versioning format for post 0.1.
7978 - Support "foo.nickname.exit" addresses, to let Alice request the
7979 address "foo" as viewed by exit node "nickname". Based on a patch
7981 - Make tor --version --version dump the cvs Id of every file.
7984 Changes in version 0.0.9rc4 - 2004-11-28
7985 o Bugfixes on 0.0.8.1:
7986 - Make windows sockets actually non-blocking (oops), and handle
7987 win32 socket errors better.
7989 o Bugfixes on 0.0.9rc1:
7990 - Actually catch the -USR2 signal.
7993 Changes in version 0.0.9rc3 - 2004-11-25
7994 o Bugfixes on 0.0.8.1:
7995 - Flush the log file descriptor after we print "Tor opening log file",
7996 so we don't see those messages days later.
7998 o Bugfixes on 0.0.9rc1:
7999 - Make tor-resolve work again.
8000 - Avoid infinite loop in tor-resolve if tor hangs up on it.
8001 - Fix an assert trigger for clients/servers handling resolves.
8004 Changes in version 0.0.9rc2 - 2004-11-24
8005 o Bugfixes on 0.0.9rc1:
8006 - I broke socks5 support while fixing the eof bug.
8007 - Allow unitless bandwidths and intervals; they default to bytes
8009 - New servers don't start out hibernating; they are active until
8010 they run out of bytes, so they have a better estimate of how
8011 long it takes, and so their operators can know they're working.
8014 Changes in version 0.0.9rc1 - 2004-11-23
8015 o Bugfixes on 0.0.8.1:
8016 - Finally fix a bug that's been plaguing us for a year:
8017 With high load, circuit package window was reaching 0. Whenever
8018 we got a circuit-level sendme, we were reading a lot on each
8019 socket, but only writing out a bit. So we would eventually reach
8020 eof. This would be noticed and acted on even when there were still
8021 bytes sitting in the inbuf.
8022 - When poll() is interrupted, we shouldn't believe the revents values.
8024 o Bugfixes on 0.0.9pre6:
8025 - Fix hibernate bug that caused pre6 to be broken.
8026 - Don't keep rephist info for routers that haven't had activity for
8027 24 hours. (This matters now that clients have keys, since we track
8029 - Never call close_temp_logs while validating log options.
8030 - Fix backslash-escaping on tor.sh.in and torctl.in.
8033 - Implement weekly/monthly/daily accounting: now you specify your
8034 hibernation properties by
8035 AccountingMax N bytes|KB|MB|GB|TB
8036 AccountingStart day|week|month [day] HH:MM
8037 Defaults to "month 1 0:00".
8038 - Let bandwidth and interval config options be specified as 5 bytes,
8039 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
8040 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
8041 get back to normal.)
8042 - If your requested entry or exit node has advertised bandwidth 0,
8044 - Be more greedy about filling up relay cells -- we try reading again
8045 once we've processed the stuff we read, in case enough has arrived
8046 to fill the last cell completely.
8047 - Apply NT service patch from Osamu Fujino. Still needs more work.
8050 Changes in version 0.0.9pre6 - 2004-11-15
8051 o Bugfixes on 0.0.8.1:
8052 - Fix assert failure on malformed socks4a requests.
8053 - Use identity comparison, not nickname comparison, to choose which
8054 half of circuit-ID-space each side gets to use. This is needed
8055 because sometimes we think of a router as a nickname, and sometimes
8056 as a hex ID, and we can't predict what the other side will do.
8057 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
8058 write() call will fail and we handle it there.
8059 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
8060 and smartlist_len, which are two major profiling offenders.
8062 o Bugfixes on 0.0.9pre5:
8063 - Fix a bug in read_all that was corrupting config files on windows.
8064 - When we're raising the max number of open file descriptors to
8065 'unlimited', don't log that we just raised it to '-1'.
8066 - Include event code with events, as required by control-spec.txt.
8067 - Don't give a fingerprint when clients do --list-fingerprint:
8068 it's misleading, because it will never be the same again.
8069 - Stop using strlcpy in tor_strndup, since it was slowing us
8071 - Remove warn on startup about missing cached-directory file.
8072 - Make kill -USR1 work again.
8073 - Hibernate if we start tor during the "wait for wakeup-time" phase
8074 of an accounting interval. Log our hibernation plans better.
8075 - Authoritative dirservers now also cache their directory, so they
8076 have it on start-up.
8079 - Fetch running-routers; cache running-routers; compress
8080 running-routers; serve compressed running-routers.z
8081 - Add NSI installer script contributed by J Doe.
8082 - Commit VC6 and VC7 workspace/project files.
8083 - Commit a tor.spec for making RPM files, with help from jbash.
8084 - Add contrib/torctl.in contributed by Glenn Fink.
8085 - Implement the control-spec's SAVECONF command, to write your
8086 configuration to torrc.
8087 - Get cookie authentication for the controller closer to working.
8088 - Include control-spec.txt in the tarball.
8089 - When set_conf changes our server descriptor, upload a new copy.
8090 But don't upload it too often if there are frequent changes.
8091 - Document authentication config in man page, and document signals
8093 - Clean up confusing parts of man page and torrc.sample.
8094 - Make expand_filename handle ~ and ~username.
8095 - Use autoconf to enable largefile support where necessary. Use
8096 ftello where available, since ftell can fail at 2GB.
8097 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
8098 log more informatively.
8099 - Give a slightly more useful output for "tor -h".
8100 - Refuse application socks connections to port 0.
8101 - Check clock skew for verified servers, but allow unverified
8102 servers and clients to have any clock skew.
8103 - Break DirFetchPostPeriod into:
8104 - DirFetchPeriod for fetching full directory,
8105 - StatusFetchPeriod for fetching running-routers,
8106 - DirPostPeriod for posting server descriptor,
8107 - RendPostPeriod for posting hidden service descriptors.
8108 - Make sure the hidden service descriptors are at a random offset
8109 from each other, to hinder linkability.
8112 Changes in version 0.0.9pre5 - 2004-11-09
8113 o Bugfixes on 0.0.9pre4:
8114 - Fix a seg fault in unit tests (doesn't affect main program).
8115 - Fix an assert bug where a hidden service provider would fail if
8116 the first hop of his rendezvous circuit was down.
8117 - Hidden service operators now correctly handle version 1 style
8118 INTRODUCE1 cells (nobody generates them still, so not a critical
8120 - If do_hup fails, actually notice.
8121 - Handle more errnos from accept() without closing the listener.
8122 Some OpenBSD machines were closing their listeners because
8123 they ran out of file descriptors.
8124 - Send resolve cells to exit routers that are running a new
8125 enough version of the resolve code to work right.
8126 - Better handling of winsock includes on non-MSV win32 compilers.
8127 - Some people had wrapped their tor client/server in a script
8128 that would restart it whenever it died. This did not play well
8129 with our "shut down if your version is obsolete" code. Now people
8130 don't fetch a new directory if their local cached version is
8132 - Make our autogen.sh work on ksh as well as bash.
8135 - Hibernation: New config option "AccountingMaxKB" lets you
8136 set how many KBytes per month you want to allow your server to
8137 consume. Rather than spreading those bytes out evenly over the
8138 month, we instead hibernate for some of the month and pop up
8139 at a deterministic time, work until the bytes are consumed, then
8140 hibernate again. Config option "MonthlyAccountingStart" lets you
8141 specify which day of the month your billing cycle starts on.
8142 - Control interface: a separate program can now talk to your
8143 client/server over a socket, and get/set config options, receive
8144 notifications of circuits and streams starting/finishing/dying,
8145 bandwidth used, etc. The next step is to get some GUIs working.
8146 Let us know if you want to help out. See doc/control-spec.txt .
8147 - Ship a contrib/tor-control.py as an example script to interact
8148 with the control port.
8149 - "tor --hash-password zzyxz" will output a salted password for
8150 use in authenticating to the control interface.
8151 - New log format in config:
8152 "Log minsev[-maxsev] stdout|stderr|syslog" or
8153 "Log minsev[-maxsev] file /var/foo"
8156 - DirPolicy config option, to let people reject incoming addresses
8157 from their dirserver.
8158 - "tor --list-fingerprint" will list your identity key fingerprint
8160 - Add "pass" target for RedirectExit, to make it easier to break
8161 out of a sequence of RedirectExit rules.
8162 - Clients now generate a TLS cert too, in preparation for having
8163 them act more like real nodes.
8164 - Ship src/win32/ in the tarball, so people can use it to build.
8165 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
8167 - New "router-status" line in directory, to better bind each verified
8168 nickname to its identity key.
8169 - Deprecate unofficial config option abbreviations, and abbreviations
8170 not on the command line.
8171 - Add a pure-C tor-resolve implementation.
8172 - Use getrlimit and friends to ensure we can reach MaxConn (currently
8173 1024) file descriptors.
8175 o Code security improvements, inspired by Ilja:
8176 - Replace sprintf with snprintf. (I think they were all safe, but
8178 - Replace strcpy/strncpy with strlcpy in more places.
8179 - Avoid strcat; use snprintf or strlcat instead.
8180 - snprintf wrapper with consistent (though not C99) overflow behavior.
8183 Changes in version 0.0.9pre4 - 2004-10-17
8184 o Bugfixes on 0.0.9pre3:
8185 - If the server doesn't specify an exit policy, use the real default
8186 exit policy, not reject *:*.
8187 - Ignore fascistfirewall when uploading/downloading hidden service
8188 descriptors, since we go through Tor for those; and when using
8189 an HttpProxy, since we assume it can reach them all.
8190 - When looking for an authoritative dirserver, use only the ones
8191 configured at boot. Don't bother looking in the directory.
8192 - The rest of the fix for get_default_conf_file() on older win32.
8193 - Make 'Routerfile' config option obsolete.
8196 - New 'MyFamily nick1,...' config option for a server to
8197 specify other servers that shouldn't be used in the same circuit
8198 with it. Only believed if nick1 also specifies us.
8199 - New 'NodeFamily nick1,nick2,...' config option for a client to
8200 specify nodes that it doesn't want to use in the same circuit.
8201 - New 'Redirectexit pattern address:port' config option for a
8202 server to redirect exit connections, e.g. to a local squid.
8205 Changes in version 0.0.9pre3 - 2004-10-13
8206 o Bugfixes on 0.0.8.1:
8207 - Better torrc example lines for dirbindaddress and orbindaddress.
8208 - Improved bounds checking on parsed ints (e.g. config options and
8209 the ones we find in directories.)
8210 - Better handling of size_t vs int, so we're more robust on 64
8212 - Fix the rest of the bug where a newly started OR would appear
8213 as unverified even after we've added his fingerprint and hupped
8215 - Fix a bug from 0.0.7: when read() failed on a stream, we would
8216 close it without sending back an end. So 'connection refused'
8217 would simply be ignored and the user would get no response.
8219 o Bugfixes on 0.0.9pre2:
8220 - Serving the cached-on-disk directory to people is bad. We now
8221 provide no directory until we've fetched a fresh one.
8222 - Workaround for bug on windows where cached-directories get crlf
8224 - Make get_default_conf_file() work on older windows too.
8225 - If we write a *:* exit policy line in the descriptor, don't write
8226 any more exit policy lines.
8229 - Use only 0.0.9pre1 and later servers for resolve cells.
8230 - Make the dirservers file obsolete.
8231 - Include a dir-signing-key token in directories to tell the
8232 parsing entity which key is being used to sign.
8233 - Remove the built-in bulky default dirservers string.
8234 - New config option "Dirserver %s:%d [fingerprint]", which can be
8235 repeated as many times as needed. If no dirservers specified,
8236 default to moria1,moria2,tor26.
8237 - Make moria2 advertise a dirport of 80, so people behind firewalls
8238 will be able to get a directory.
8239 - Http proxy support
8240 - Dirservers translate requests for http://%s:%d/x to /x
8241 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
8242 be routed through this host.
8243 - Clients ask for /tor/x rather than /x for new enough dirservers.
8244 This way we can one day coexist peacefully with apache.
8245 - Clients specify a "Host: %s%d" http header, to be compatible
8246 with more proxies, and so running squid on an exit node can work.
8249 Changes in version 0.0.8.1 - 2004-10-13
8251 - Fix a seg fault that can be triggered remotely for Tor
8252 clients/servers with an open dirport.
8253 - Fix a rare assert trigger, where routerinfos for entries in
8254 our cpath would expire while we're building the path.
8255 - Fix a bug in OutboundBindAddress so it (hopefully) works.
8256 - Fix a rare seg fault for people running hidden services on
8257 intermittent connections.
8258 - Fix a bug in parsing opt keywords with objects.
8259 - Fix a stale pointer assert bug when a stream detaches and
8261 - Fix a string format vulnerability (probably not exploitable)
8262 in reporting stats locally.
8263 - Fix an assert trigger: sometimes launching circuits can fail
8264 immediately, e.g. because too many circuits have failed recently.
8265 - Fix a compile warning on 64 bit platforms.
8268 Changes in version 0.0.9pre2 - 2004-10-03
8270 - Make fetching a cached directory work for 64-bit platforms too.
8271 - Make zlib.h a required header, not an optional header.
8274 Changes in version 0.0.9pre1 - 2004-10-01
8276 - Stop using separate defaults for no-config-file and
8277 empty-config-file. Now you have to explicitly turn off SocksPort,
8278 if you don't want it open.
8279 - Fix a bug in OutboundBindAddress so it (hopefully) works.
8280 - Improve man page to mention more of the 0.0.8 features.
8281 - Fix a rare seg fault for people running hidden services on
8282 intermittent connections.
8283 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
8285 - Fix more dns related bugs: send back resolve_failed and end cells
8286 more reliably when the resolve fails, rather than closing the
8287 circuit and then trying to send the cell. Also attach dummy resolve
8288 connections to a circuit *before* calling dns_resolve(), to fix
8289 a bug where cached answers would never be sent in RESOLVED cells.
8290 - When we run out of disk space, or other log writing error, don't
8291 crash. Just stop logging to that log and continue.
8292 - We were starting to daemonize before we opened our logs, so if
8293 there were any problems opening logs, we would complain to stderr,
8294 which wouldn't work, and then mysteriously exit.
8295 - Fix a rare bug where sometimes a verified OR would connect to us
8296 before he'd uploaded his descriptor, which would cause us to
8297 assign conn->nickname as though he's unverified. Now we look through
8298 the fingerprint list to see if he's there.
8299 - Fix a rare assert trigger, where routerinfos for entries in
8300 our cpath would expire while we're building the path.
8303 - Clients can ask dirservers for /dir.z to get a compressed version
8304 of the directory. Only works for servers running 0.0.9, of course.
8305 - Make clients cache directories and use them to seed their router
8306 lists at startup. This means clients have a datadir again.
8307 - Configuration infrastructure support for warning on obsolete
8309 - Respond to content-encoding headers by trying to uncompress as
8311 - Reply with a deflated directory when a client asks for "dir.z".
8312 We could use allow-encodings instead, but allow-encodings isn't
8313 specified in HTTP 1.0.
8314 - Raise the max dns workers from 50 to 100.
8315 - Discourage people from setting their dirfetchpostperiod more often
8316 than once per minute.
8317 - Protect dirservers from overzealous descriptor uploading -- wait
8318 10 seconds after directory gets dirty, before regenerating.
8321 Changes in version 0.0.8 - 2004-08-25
8322 o Port it to SunOS 5.9 / Athena
8325 Changes in version 0.0.8rc2 - 2004-08-20
8326 o Make it compile on cygwin again.
8327 o When picking unverified routers, skip those with low uptime and/or
8328 low bandwidth, depending on what properties you care about.
8331 Changes in version 0.0.8rc1 - 2004-08-18
8332 o Changes from 0.0.7.3:
8334 - Fix assert triggers: if the other side returns an address 0.0.0.0,
8335 don't put it into the client dns cache.
8336 - If a begin failed due to exit policy, but we believe the IP address
8337 should have been allowed, switch that router to exitpolicy reject *:*
8338 until we get our next directory.
8340 - Clients choose nodes proportional to advertised bandwidth.
8341 - Avoid using nodes with low uptime as introduction points.
8342 - Handle servers with dynamic IP addresses: don't replace
8343 options->Address with the resolved one at startup, and
8344 detect our address right before we make a routerinfo each time.
8345 - 'FascistFirewall' option to pick dirservers and ORs on specific
8346 ports; plus 'FirewallPorts' config option to tell FascistFirewall
8347 which ports are open. (Defaults to 80,443)
8348 - Be more aggressive about trying to make circuits when the network
8349 has changed (e.g. when you unsuspend your laptop).
8350 - Check for time skew on http headers; report date in response to
8352 - If the entrynode config line has only one node, don't pick it as
8354 - Add strict{entry|exit}nodes config options. If set to 1, then
8355 we refuse to build circuits that don't include the specified entry
8357 - OutboundBindAddress config option, to bind to a specific
8358 IP address for outgoing connect()s.
8359 - End truncated log entries (e.g. directories) with "[truncated]".
8361 o Patches to 0.0.8preX:
8363 - Patches to compile and run on win32 again (maybe)?
8364 - Fix crash when looking for ~/.torrc with no $HOME set.
8365 - Fix a race bug in the unit tests.
8366 - Handle verified/unverified name collisions better when new
8367 routerinfo's arrive in a directory.
8368 - Sometimes routers were getting entered into the stats before
8369 we'd assigned their identity_digest. Oops.
8370 - Only pick and establish intro points after we've gotten a
8373 - AllowUnverifiedNodes config option to let circuits choose no-name
8374 routers in entry,middle,exit,introduction,rendezvous positions.
8375 Allow middle and rendezvous positions by default.
8376 - Add a man page for tor-resolve.
8379 Changes in version 0.0.7.3 - 2004-08-12
8380 o Stop dnsworkers from triggering an assert failure when you
8381 ask them to resolve the host "".
8384 Changes in version 0.0.8pre3 - 2004-08-09
8385 o Changes from 0.0.7.2:
8386 - Allow multiple ORs with same nickname in routerlist -- now when
8387 people give us one identity key for a nickname, then later
8388 another, we don't constantly complain until the first expires.
8389 - Remember used bandwidth (both in and out), and publish 15-minute
8390 snapshots for the past day into our descriptor.
8391 - You can now fetch $DIRURL/running-routers to get just the
8392 running-routers line, not the whole descriptor list. (But
8393 clients don't use this yet.)
8394 - When people mistakenly use Tor as an http proxy, point them
8395 at the tor-doc.html rather than the INSTALL.
8396 - Remove our mostly unused -- and broken -- hex_encode()
8397 function. Use base16_encode() instead. (Thanks to Timo Lindfors
8398 for pointing out this bug.)
8399 - Rotate onion keys every 12 hours, not every 2 hours, so we have
8400 fewer problems with people using the wrong key.
8401 - Change the default exit policy to reject the default edonkey,
8402 kazaa, gnutella ports.
8403 - Add replace_file() to util.[ch] to handle win32's rename().
8405 o Changes from 0.0.8preX:
8406 - Fix two bugs in saving onion keys to disk when rotating, so
8407 hopefully we'll get fewer people using old onion keys.
8408 - Fix an assert error that was making SocksPolicy not work.
8409 - Be willing to expire routers that have an open dirport -- it's
8410 just the authoritative dirservers we want to not forget.
8411 - Reject tor-resolve requests for .onion addresses early, so we
8412 don't build a whole rendezvous circuit and then fail.
8413 - When you're warning a server that he's unverified, don't cry
8415 - Fix a race condition: don't try to extend onto a connection
8416 that's still handshaking.
8417 - For servers in clique mode, require the conn to be open before
8418 you'll choose it for your path.
8419 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
8420 end relay cell, etc.
8421 - Measure bandwidth capacity over the last 24 hours, not just 12
8422 - Bugfix: authoritative dirservers were making and signing a new
8423 directory for each client, rather than reusing the cached one.
8426 Changes in version 0.0.8pre2 - 2004-08-04
8427 o Changes from 0.0.7.2:
8429 - Check directory signature _before_ you decide whether you're
8430 you're running an obsolete version and should exit.
8431 - Check directory signature _before_ you parse the running-routers
8432 list to decide who's running or verified.
8433 - Bugfixes and features:
8434 - Check return value of fclose while writing to disk, so we don't
8435 end up with broken files when servers run out of disk space.
8436 - Log a warning if the user uses an unsafe socks variant, so people
8437 are more likely to learn about privoxy or socat.
8438 - Dirservers now include RFC1123-style dates in the HTTP headers,
8439 which one day we will use to better detect clock skew.
8441 o Changes from 0.0.8pre1:
8442 - Make it compile without warnings again on win32.
8443 - Log a warning if you're running an unverified server, to let you
8444 know you might want to get it verified.
8445 - Only pick a default nickname if you plan to be a server.
8448 Changes in version 0.0.8pre1 - 2004-07-23
8450 - Made our unit tests compile again on OpenBSD 3.5, and tor
8451 itself compile again on OpenBSD on a sparc64.
8452 - We were neglecting milliseconds when logging on win32, so
8453 everything appeared to happen at the beginning of each second.
8456 - 'Extend' relay cell payloads now include the digest of the
8457 intended next hop's identity key. Now we can verify that we're
8458 extending to the right router, and also extend to routers we
8459 hadn't heard of before.
8462 - Tor nodes can now act as relays (with an advertised ORPort)
8463 without being manually verified by the dirserver operators.
8464 - Uploaded descriptors of unverified routers are now accepted
8465 by the dirservers, and included in the directory.
8466 - Verified routers are listed by nickname in the running-routers
8467 list; unverified routers are listed as "$<fingerprint>".
8468 - We now use hash-of-identity-key in most places rather than
8469 nickname or addr:port, for improved security/flexibility.
8470 - To avoid Sybil attacks, paths still use only verified servers.
8471 But now we have a chance to play around with hybrid approaches.
8472 - Nodes track bandwidth usage to estimate capacity (not used yet).
8473 - ClientOnly option for nodes that never want to become servers.
8474 - Directory caching.
8475 - "AuthoritativeDir 1" option for the official dirservers.
8476 - Now other nodes (clients and servers) will cache the latest
8477 directory they've pulled down.
8478 - They can enable their DirPort to serve it to others.
8479 - Clients will pull down a directory from any node with an open
8480 DirPort, and check the signature/timestamp correctly.
8481 - Authoritative dirservers now fetch directories from other
8482 authdirservers, to stay better synced.
8483 - Running-routers list tells who's down also, along with noting
8484 if they're verified (listed by nickname) or unverified (listed
8486 - Allow dirservers to serve running-router list separately.
8487 This isn't used yet.
8488 - ORs connect-on-demand to other ORs
8489 - If you get an extend cell to an OR you're not connected to,
8490 connect, handshake, and forward the create cell.
8491 - The authoritative dirservers stay connected to everybody,
8492 and everybody stays connected to 0.0.7 servers, but otherwise
8493 clients/servers expire unused connections after 5 minutes.
8494 - When servers get a sigint, they delay 30 seconds (refusing new
8495 connections) then exit. A second sigint causes immediate exit.
8496 - File and name management:
8497 - Look for .torrc if no CONFDIR "torrc" is found.
8498 - If no datadir is defined, then choose, make, and secure ~/.tor
8500 - If torrc not found, exitpolicy reject *:*.
8501 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
8502 - If no nickname is defined, derive default from hostname.
8503 - Rename secret key files, e.g. identity.key -> secret_id_key,
8504 to discourage people from mailing their identity key to tor-ops.
8505 - Refuse to build a circuit before the directory has arrived --
8506 it won't work anyway, since you won't know the right onion keys
8508 - Try other dirservers immediately if the one you try is down. This
8509 should tolerate down dirservers better now.
8510 - Parse tor version numbers so we can do an is-newer-than check
8511 rather than an is-in-the-list check.
8512 - New socks command 'resolve', to let us shim gethostbyname()
8514 - A 'tor_resolve' script to access the socks resolve functionality.
8515 - A new socks-extensions.txt doc file to describe our
8516 interpretation and extensions to the socks protocols.
8517 - Add a ContactInfo option, which gets published in descriptor.
8518 - Publish OR uptime in descriptor (and thus in directory) too.
8519 - Write tor version at the top of each log file
8520 - New docs in the tarball:
8522 - Document that you should proxy your SSL traffic too.
8525 Changes in version 0.0.7.2 - 2004-07-07
8526 o A better fix for the 0.0.0.0 problem, that will hopefully
8527 eliminate the remaining related assertion failures.
8530 Changes in version 0.0.7.1 - 2004-07-04
8531 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
8532 since internally we use 0.0.0.0 to signify "not yet resolved".
8535 Changes in version 0.0.7 - 2004-06-07
8536 o Updated the man page to reflect the new features.
8539 Changes in version 0.0.7rc2 - 2004-06-06
8540 o Changes from 0.0.7rc1:
8541 - Make it build on Win32 again.
8542 o Changes from 0.0.6.2:
8543 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
8547 Changes in version 0.0.7rc1 - 2004-06-02
8549 - On sighup, we were adding another log without removing the first
8550 one. So log messages would get duplicated n times for n sighups.
8551 - Several cases of using a connection after we'd freed it. The
8552 problem was that connections that are pending resolve are in both
8553 the pending_resolve tree, and also the circuit's resolving_streams
8554 list. When you want to remove one, you must remove it from both.
8555 - Fix a double-mark-for-close where an end cell arrived for a
8556 resolving stream, and then the resolve failed.
8557 - Check directory signatures based on name of signer, not on whom
8558 we got the directory from. This will let us cache directories more
8561 - Crank up some of our constants to handle more users.
8564 Changes in version 0.0.7pre1 - 2004-06-02
8565 o Fixes for crashes and other obnoxious bugs:
8566 - Fix an epipe bug: sometimes when directory connections failed
8567 to connect, we would give them a chance to flush before closing
8569 - When we detached from a circuit because of resolvefailed, we
8570 would immediately try the same circuit twice more, and then
8571 give up on the resolve thinking we'd tried three different
8573 - Limit the number of intro circuits we'll attempt to build for a
8574 hidden service per 15-minute period.
8575 - Check recommended-software string *early*, before actually parsing
8576 the directory. Thus we can detect an obsolete version and exit,
8577 even if the new directory format doesn't parse.
8578 o Fixes for security bugs:
8579 - Remember which nodes are dirservers when you startup, and if a
8580 random OR enables his dirport, don't automatically assume he's
8581 a trusted dirserver.
8583 - Directory connections were asking the wrong poll socket to
8584 start writing, and not asking themselves to start writing.
8585 - When we detached from a circuit because we sent a begin but
8586 didn't get a connected, we would use it again the first time;
8587 but after that we would correctly switch to a different one.
8588 - Stop warning when the first onion decrypt attempt fails; they
8589 will sometimes legitimately fail now that we rotate keys.
8590 - Override unaligned-access-ok check when $host_cpu is ia64 or
8591 arm. Apparently they allow it but the kernel whines.
8592 - Dirservers try to reconnect periodically too, in case connections
8594 - Fix some memory leaks in directory servers.
8595 - Allow backslash in Win32 filenames.
8596 - Made Tor build complain-free on FreeBSD, hopefully without
8597 breaking other BSD builds. We'll see.
8599 - Doxygen markup on all functions and global variables.
8600 - Make directory functions update routerlist, not replace it. So
8601 now directory disagreements are not so critical a problem.
8602 - Remove the upper limit on number of descriptors in a dirserver's
8603 directory (not that we were anywhere close).
8604 - Allow multiple logfiles at different severity ranges.
8605 - Allow *BindAddress to specify ":port" rather than setting *Port
8606 separately. Allow multiple instances of each BindAddress config
8607 option, so you can bind to multiple interfaces if you want.
8608 - Allow multiple exit policy lines, which are processed in order.
8609 Now we don't need that huge line with all the commas in it.
8610 - Enable accept/reject policies on SOCKS connections, so you can bind
8611 to 0.0.0.0 but still control who can use your OP.
8614 Changes in version 0.0.6.2 - 2004-05-16
8615 o Our integrity-checking digest was checking only the most recent cell,
8616 not the previous cells like we'd thought.
8617 Thanks to Stefan Mark for finding the flaw!
8620 Changes in version 0.0.6.1 - 2004-05-06
8621 o Fix two bugs in our AES counter-mode implementation (this affected
8622 onion-level stream encryption, but not TLS-level). It turns
8623 out we were doing something much more akin to a 16-character
8624 polyalphabetic cipher. Oops.
8625 Thanks to Stefan Mark for finding the flaw!
8626 o Retire moria3 as a directory server, and add tor26 as a directory
8630 Changes in version 0.0.6 - 2004-05-02
8634 Changes in version 0.0.6rc4 - 2004-05-01
8635 o Update the built-in dirservers list to use the new directory format
8636 o Fix a rare seg fault: if a node offering a hidden service attempts
8637 to build a circuit to Alice's rendezvous point and fails before it
8638 reaches the last hop, it retries with a different circuit, but
8640 o Handle windows socket errors correctly.
8643 Changes in version 0.0.6rc3 - 2004-04-28
8644 o Don't expire non-general excess circuits (if we had enough
8645 circuits open, we were expiring rendezvous circuits -- even
8646 when they had a stream attached. oops.)
8647 o Fetch randomness from /dev/urandom better (not via fopen/fread)
8648 o Better debugging for tls errors
8649 o Some versions of openssl have an SSL_pending function that erroneously
8650 returns bytes when there is a non-application record pending.
8651 o Set Content-Type on the directory and hidserv descriptor.
8652 o Remove IVs from cipher code, since AES-ctr has none.
8653 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
8654 o We were using an array of length zero in a few places.
8655 o win32's gethostbyname can't resolve an IP to an IP.
8656 o win32's close can't close a socket.
8659 Changes in version 0.0.6rc2 - 2004-04-26
8660 o Fix a bug where we were closing tls connections intermittently.
8661 It turns out openssl keeps its errors around -- so if an error
8662 happens, and you don't ask about it, and then another openssl
8663 operation happens and succeeds, and you ask if there was an error,
8664 it tells you about the first error. Fun fun.
8665 o Fix a bug that's been lurking since 27 may 03 (!)
8666 When passing back a destroy cell, we would use the wrong circ id.
8667 'Mostly harmless', but still worth fixing.
8668 o Since we don't support truncateds much, don't bother sending them;
8669 just close the circ.
8670 o check for <machine/limits.h> so we build on NetBSD again (I hope).
8671 o don't crash if a conn that sent a begin has suddenly lost its circuit
8672 (this was quite rare).
8675 Changes in version 0.0.6rc1 - 2004-04-25
8676 o We now rotate link (tls context) keys and onion keys.
8677 o CREATE cells now include oaep padding, so you can tell
8678 if you decrypted them correctly.
8679 o Add bandwidthburst to server descriptor.
8680 o Directories now say which dirserver signed them.
8681 o Use a tor_assert macro that logs failed assertions too.
8684 Changes in version 0.0.6pre5 - 2004-04-18
8685 o changes from 0.0.6pre4:
8686 - make tor build on broken freebsd 5.2 installs
8687 - fix a failed assert when you try an intro point, get a nack, and try
8688 a second one and it works.
8689 - when alice uses a port that the hidden service doesn't accept,
8690 it now sends back an end cell (denied by exit policy). otherwise
8691 alice would just have to wait to time out.
8692 - fix another rare bug: when we had tried all the intro
8693 points for a hidden service, we fetched the descriptor
8694 again, but we left our introcirc thinking it had already
8695 sent an intro, so it kept waiting for a response...
8696 - bugfix: when you sleep your hidden-service laptop, as soon
8697 as it wakes up it tries to upload a service descriptor, but
8698 socketpair fails for some reason (localhost not up yet?).
8699 now we simply give up on that upload, and we'll try again later.
8700 i'd still like to find the bug though.
8701 - if an intro circ waiting for an ack dies before getting one, then
8703 - we were reusing stale service descriptors and refetching usable
8707 Changes in version 0.0.6pre4 - 2004-04-14
8708 o changes from 0.0.6pre3:
8709 - when bob fails to connect to the rendezvous point, and his
8710 circ didn't fail because of the rendezvous point itself, then
8711 he retries a couple of times
8712 - we expire introduction and rendezvous circs more thoroughly
8713 (sometimes they were hanging around forever)
8714 - we expire unattached rendezvous streams that have been around
8715 too long (they were sticking around forever).
8716 - fix a measly fencepost error that was crashing everybody with
8720 Changes in version 0.0.6pre3 - 2004-04-14
8721 o changes from 0.0.6pre2:
8722 - make hup work again
8723 - fix some memory leaks for dirservers
8724 - allow more skew in rendezvous descriptor timestamps, to help
8725 handle people like blanu who don't know what time it is
8726 - normal circs are 3 hops, but some rend/intro circs are 4, if
8727 the initiator doesn't get to choose the last hop
8728 - send acks for introductions, so alice can know whether to try
8730 - bob publishes intro points more correctly
8731 o changes from 0.0.5:
8732 - fix an assert trigger that's been plaguing us since the days
8733 of 0.0.2prexx (thanks weasel!)
8734 - retry stream correctly when we fail to connect because of
8735 exit-policy-reject (should try another) or can't-resolve-address
8736 (also should try another, because dns on random internet servers
8738 - when we hup a dirserver and we've *removed* a server from the
8739 approved-routers list, now we remove that server from the
8740 in-memory directories too
8743 Changes in version 0.0.6pre2 - 2004-04-08
8744 o We fixed our base32 implementation. Now it works on all architectures.
8747 Changes in version 0.0.6pre1 - 2004-04-08
8749 - Hidden services and rendezvous points are implemented. Go to
8750 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
8751 hidden services. (This only works via a socks4a proxy such as
8752 Privoxy, and currently it's quite slow.)
8755 Changes in version 0.0.5 - 2004-03-30
8759 Changes in version 0.0.5rc3 - 2004-03-29
8760 o Install torrc as torrc.sample -- we no longer clobber your
8762 o Re-enable recommendedversion checking (we broke it in rc2, oops)
8763 o Add in a 'notice' log level for things the operator should hear
8764 but that aren't warnings
8767 Changes in version 0.0.5rc2 - 2004-03-29
8768 o Hold socks connection open until reply is flushed (if possible)
8769 o Make exit nodes resolve IPs to IPs immediately, rather than asking
8770 the dns farm to do it.
8771 o Fix c99 aliasing warnings in rephist.c
8772 o Don't include server descriptors that are older than 24 hours in the
8774 o Give socks 'reject' replies their whole 15s to attempt to flush,
8775 rather than seeing the 60s timeout and assuming the flush had failed.
8776 o Clean automake droppings from the cvs repository
8779 Changes in version 0.0.5rc1 - 2004-03-28
8780 o Fix mangled-state bug in directory fetching (was causing sigpipes).
8781 o Only build circuits after we've fetched the directory: clients were
8782 using only the directory servers before they'd fetched a directory.
8783 This also means longer startup time; so it goes.
8784 o Fix an assert trigger where an OP would fail to handshake, and we'd
8785 expect it to have a nickname.
8786 o Work around a tsocks bug: do a socks reject when AP connection dies
8787 early, else tsocks goes into an infinite loop.
8790 Changes in version 0.0.4 - 2004-03-26
8791 o When connecting to a dirserver or OR and the network is down,
8795 Changes in version 0.0.3 - 2004-03-26
8796 o Warn and fail if server chose a nickname with illegal characters
8797 o Port to Solaris and Sparc:
8798 - include missing header fcntl.h
8799 - have autoconf find -lsocket -lnsl automatically
8800 - deal with hardware word alignment
8801 - make uname() work (solaris has a different return convention)
8802 - switch from using signal() to sigaction()
8803 o Preliminary work on reputation system:
8804 - Keep statistics on success/fail of connect attempts; they're published
8805 by kill -USR1 currently.
8806 - Add a RunTesting option to try to learn link state by creating test
8807 circuits, even when SocksPort is off.
8808 - Remove unused open circuits when there are too many.
8811 Changes in version 0.0.2 - 2004-03-19
8812 - Include strlcpy and strlcat for safer string ops
8813 - define INADDR_NONE so we compile (but still not run) on solaris
8816 Changes in version 0.0.2pre27 - 2004-03-14
8818 - Allow internal tor networks (we were rejecting internal IPs,
8819 now we allow them if they're set explicitly).
8820 - And fix a few endian issues.
8823 Changes in version 0.0.2pre26 - 2004-03-14
8825 - If a stream times out after 15s without a connected cell, don't
8826 try that circuit again: try a new one.
8827 - Retry streams at most 4 times. Then give up.
8828 - When a dirserver gets a descriptor from an unknown router, it
8829 logs its fingerprint (so the dirserver operator can choose to
8830 accept it even without mail from the server operator).
8831 - Inform unapproved servers when we reject their descriptors.
8832 - Make tor build on Windows again. It works as a client, who knows
8834 - Clearer instructions in the torrc for how to set up a server.
8835 - Be more efficient about reading fd's when our global token bucket
8836 (used for rate limiting) becomes empty.
8838 - Stop asserting that computers always go forward in time. It's
8840 - When we sent a cell (e.g. destroy) and then marked an OR connection
8841 expired, we might close it before finishing a flush if the other
8842 side isn't reading right then.
8843 - Don't allow dirservers to start if they haven't defined
8845 - We were caching transient dns failures. Oops.
8846 - Prevent servers from publishing an internal IP as their address.
8847 - Address a strcat vulnerability in circuit.c
8850 Changes in version 0.0.2pre25 - 2004-03-04
8852 - Put the OR's IP in its router descriptor, not its fqdn. That way
8853 we'll stop being stalled by gethostbyname for nodes with flaky dns,
8856 - If the user typed in an address that didn't resolve, the server
8860 Changes in version 0.0.2pre24 - 2004-03-03
8862 - Fix an assertion failure in dns.c, where we were trying to dequeue
8863 a pending dns resolve even if it wasn't pending
8864 - Fix a spurious socks5 warning about still trying to write after the
8865 connection is finished.
8866 - Hold certain marked_for_close connections open until they're finished
8867 flushing, rather than losing bytes by closing them too early.
8868 - Correctly report the reason for ending a stream
8869 - Remove some duplicate calls to connection_mark_for_close
8870 - Put switch_id and start_daemon earlier in the boot sequence, so it
8871 will actually try to chdir() to options.DataDirectory
8872 - Make 'make test' exit(1) if a test fails; fix some unit tests
8873 - Make tor fail when you use a config option it doesn't know about,
8874 rather than warn and continue.
8875 - Make --version work
8876 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
8879 Changes in version 0.0.2pre23 - 2004-02-29
8881 - Print a statement when the first circ is finished, so the user
8883 - If a relay cell is unrecognized at the end of the circuit,
8884 send back a destroy. (So attacks to mutate cells are more
8886 - New config option 'excludenodes' to avoid certain nodes for circuits.
8887 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
8888 so you can collect coredumps there.
8890 - Fix a bug in tls flushing where sometimes data got wedged and
8891 didn't flush until more data got sent. Hopefully this bug was
8892 a big factor in the random delays we were seeing.
8893 - Make 'connected' cells include the resolved IP, so the client
8894 dns cache actually gets populated.
8895 - Disallow changing from ORPort=0 to ORPort>0 on hup.
8896 - When we time-out on a stream and detach from the circuit, send an
8897 end cell down it first.
8898 - Only warn about an unknown router (in exitnodes, entrynodes,
8899 excludenodes) after we've fetched a directory.
8902 Changes in version 0.0.2pre22 - 2004-02-26
8904 - Servers publish less revealing uname information in descriptors.
8905 - More memory tracking and assertions, to crash more usefully when
8907 - If the default torrc isn't there, just use some default defaults.
8908 Plus provide an internal dirservers file if they don't have one.
8909 - When the user tries to use Tor as an http proxy, give them an http
8910 501 failure explaining that we're a socks proxy.
8911 - Dump a new router.desc on hup, to help confused people who change
8912 their exit policies and then wonder why router.desc doesn't reflect
8914 - Clean up the generic tor.sh init script that we ship with.
8916 - If the exit stream is pending on the resolve, and a destroy arrives,
8917 then the stream wasn't getting removed from the pending list. I
8918 think this was the one causing recent server crashes.
8919 - Use a more robust poll on OSX 10.3, since their poll is flaky.
8920 - When it couldn't resolve any dirservers, it was useless from then on.
8921 Now it reloads the RouterFile (or default dirservers) if it has no
8923 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
8924 many users don't even *have* a /usr/local/sbin/.
8927 Changes in version 0.0.2pre21 - 2004-02-18
8929 - There's a ChangeLog file that actually reflects the changelog.
8930 - There's a 'torify' wrapper script, with an accompanying
8931 tor-tsocks.conf, that simplifies the process of using tsocks for
8932 tor. It even has a man page.
8933 - The tor binary gets installed to sbin rather than bin now.
8934 - Retry streams where the connected cell hasn't arrived in 15 seconds
8935 - Clean up exit policy handling -- get the default out of the torrc,
8936 so we can update it without forcing each server operator to fix
8938 - Allow imaps and pop3s in default exit policy
8940 - Prevent picking middleman nodes as the last node in the circuit
8943 Changes in version 0.0.2pre20 - 2004-01-30
8945 - We now have a deb package, and it's in debian unstable. Go to
8947 - I've split the TotalBandwidth option into BandwidthRate (how many
8948 bytes per second you want to allow, long-term) and
8949 BandwidthBurst (how many bytes you will allow at once before the cap
8950 kicks in). This better token bucket approach lets you, say, set
8951 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
8952 performance while not exceeding your monthly bandwidth quota.
8953 - Push out a tls record's worth of data once you've got it, rather
8954 than waiting until you've read everything waiting to be read. This
8955 may improve performance by pipelining better. We'll see.
8956 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
8957 from failed circuits (if they haven't been connected yet) and attach
8959 - Expire old streams that haven't managed to connect. Some day we'll
8960 have them reattach to new circuits instead.
8963 - Fix several memory leaks that were causing servers to become bloated
8965 - Fix a few very rare assert triggers. A few more remain.
8966 - Setuid to User _before_ complaining about running as root.
8969 Changes in version 0.0.2pre19 - 2004-01-07
8971 - Fix deadlock condition in dns farm. We were telling a child to die by
8972 closing the parent's file descriptor to him. But newer children were
8973 inheriting the open file descriptor from the parent, and since they
8974 weren't closing it, the socket never closed, so the child never read
8975 eof, so he never knew to exit. Similarly, dns workers were holding
8976 open other sockets, leading to all sorts of chaos.
8977 - New cleaner daemon() code for forking and backgrounding.
8978 - If you log to a file, it now prints an entry at the top of the
8979 logfile so you know it's working.
8980 - The onionskin challenge length was 30 bytes longer than necessary.
8981 - Started to patch up the spec so it's not quite so out of date.
8984 Changes in version 0.0.2pre18 - 2004-01-02
8986 - Fix endian issues with the 'integrity' field in the relay header.
8987 - Fix a potential bug where connections in state
8988 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
8991 Changes in version 0.0.2pre17 - 2003-12-30
8993 - Made --debuglogfile (or any second log file, actually) work.
8994 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
8995 adversary could force us into an infinite loop.
8998 - Each onionskin handshake now includes a hash of the computed key,
8999 to prove the server's identity and help perfect forward secrecy.
9000 - Changed cell size from 256 to 512 bytes (working toward compatibility
9002 - Changed cell length to 2 bytes, and moved it to the relay header.
9003 - Implemented end-to-end integrity checking for the payloads of
9005 - Separated streamid from 'recognized' (otherwise circuits will get
9006 messed up when we try to have streams exit from the middle). We
9007 use the integrity-checking to confirm that a cell is addressed to
9009 - Randomize the initial circid and streamid values, so an adversary who
9010 breaks into a node can't learn how many circuits or streams have
9014 Changes in version 0.0.2pre16 - 2003-12-14
9016 - Fixed a bug that made HUP trigger an assert
9017 - Fixed a bug where a circuit that immediately failed wasn't being
9018 counted as a failed circuit in counting retries.
9021 - Now we close the circuit when we get a truncated cell: otherwise we're
9022 open to an anonymity attack where a bad node in the path truncates
9023 the circuit and then we open streams at him.
9024 - Add port ranges to exit policies
9025 - Add a conservative default exit policy
9026 - Warn if you're running tor as root
9027 - on HUP, retry OR connections and close/rebind listeners
9028 - options.EntryNodes: try these nodes first when picking the first node
9029 - options.ExitNodes: if your best choices happen to include any of
9030 your preferred exit nodes, you choose among just those preferred
9032 - options.ExcludedNodes: nodes that are never picked in path building
9035 Changes in version 0.0.2pre15 - 2003-12-03
9036 o Robustness and bugfixes:
9037 - Sometimes clients would cache incorrect DNS resolves, which would
9038 really screw things up.
9039 - An OP that goes offline would slowly leak all its sockets and stop
9041 - A wide variety of bugfixes in exit node selection, exit policy
9042 handling, and processing pending streams when a new circuit is
9044 - Pick nodes for a path only from those the directory says are up
9045 - Choose randomly from all running dirservers, not always the first one
9046 - Increase allowed http header size for directory fetch.
9047 - Stop writing to stderr (if we're daemonized it will be closed).
9048 - Enable -g always, so cores will be more useful to me.
9049 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
9052 - Wrote a man page. It lists commonly used options.
9055 - Change default loglevel to warn.
9056 - Make PidFile default to null rather than littering in your CWD.
9057 - OnionRouter config option is now obsolete. Instead it just checks
9059 - Moved to a single unified torrc file for both clients and servers.
9062 Changes in version 0.0.2pre14 - 2003-11-29
9063 o Robustness and bugfixes:
9064 - Force the admin to make the DataDirectory himself
9065 - to get ownership/permissions right
9066 - so clients no longer make a DataDirectory and then never use it
9067 - fix bug where a client who was offline for 45 minutes would never
9068 pull down a directory again
9069 - fix (or at least hide really well) the dns assert bug that was
9070 causing server crashes
9071 - warnings and improved robustness wrt clockskew for certs
9072 - use the native daemon(3) to daemonize, when available
9073 - exit if bind() fails
9074 - exit if neither socksport nor orport is defined
9075 - include our own tor_timegm (Win32 doesn't have its own)
9076 - bugfix for win32 with lots of connections
9077 - fix minor bias in PRNG
9078 - make dirserver more robust to corrupt cached directory
9081 - Wrote the design document (woo)
9083 o Circuit building and exit policies:
9084 - Circuits no longer try to use nodes that the directory has told them
9086 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
9087 bitcounts (18.0.0.0/8).
9088 - Make AP connections standby for a circuit if no suitable circuit
9089 exists, rather than failing
9090 - Circuits choose exit node based on addr/port, exit policies, and
9091 which AP connections are standing by
9092 - Bump min pathlen from 2 to 3
9093 - Relay end cells have a payload to describe why the stream ended.
9094 - If the stream failed because of exit policy, try again with a new
9096 - Clients have a dns cache to remember resolved addresses.
9097 - Notice more quickly when we have no working circuits
9100 - APPort is now called SocksPort
9101 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
9103 - RecommendedVersions is now a config variable rather than
9104 hardcoded (for dirservers)
9105 - Reloads config on HUP
9106 - Usage info on -h or --help
9107 - If you set User and Group config vars, it'll setu/gid to them.
9110 Changes in version 0.0.2pre13 - 2003-10-19
9111 o General stability:
9112 - SSL_write no longer fails when it returns WANTWRITE and the number
9113 of bytes in the buf has changed by the next SSL_write call.
9114 - Fix segfault fetching directory when network is down
9115 - Fix a variety of minor memory leaks
9116 - Dirservers reload the fingerprints file on HUP, so I don't have
9117 to take down the network when I approve a new router
9118 - Default server config file has explicit Address line to specify fqdn
9121 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
9122 - Make listener connections not ever alloc bufs
9124 o Autoconf improvements:
9125 - don't clobber an external CFLAGS in ./configure
9126 - Make install now works
9127 - create var/lib/tor on make install
9128 - autocreate a tor.sh initscript to help distribs
9129 - autocreate the torrc and sample-server-torrc with correct paths
9131 o Log files and Daemonizing now work:
9132 - If --DebugLogFile is specified, log to it at -l debug
9133 - If --LogFile is specified, use it instead of commandline
9134 - If --RunAsDaemon is set, tor forks and backgrounds on startup