1 Changes in version 0.2.2.13-alpha - 2010-04-24
3 - Teach relays to defend themselves from connection overload. Relays
4 now close idle circuits early if it looks like they were intended
5 for directory fetches. Relays are also more aggressive about closing
6 TLS connections that have no circuits on them. Such circuits are
7 unlikely to be re-used, and tens of thousands of them were piling
8 up at the fast relays, causing the relays to run out of sockets
9 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
10 their directory fetches over TLS).
13 - Finally get rid of the deprecated and now harmful notion of "clique
14 mode", where directory authorities maintain TLS connections to
16 - Directory authorities now do an immediate reachability check as soon
17 as they hear about a new relay. This change should slightly reduce
18 the time between setting up a relay and getting listed as running
19 in the consensus. It should also improve the time between setting
20 up a bridge and seeing use by bridge users.
21 - Directory authorities no longer launch a TLS connection to every
22 relay as they startup. Now that we have 2k+ descriptors cached,
23 the resulting network hiccup is becoming a burden. Besides,
24 authorities already avoid voting about Running for the first half
28 Changes in version 0.2.2.12-alpha - 2010-04-20
29 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
30 handle and vote on descriptors. It was causing relays to drop out of
34 - Many relays have been falling out of the consensus lately because
35 not enough authorities know about their descriptor for them to get
36 a majority of votes. When we deprecated the v2 directory protocol,
37 we got rid of the only way that v3 authorities can hear from each
38 other about other descriptors. Now authorities examine every v3
39 vote for new descriptors, and fetch them from that authority. Bugfix
41 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
42 and a warning in or.h related to bandwidth_weight_rule_t that
43 prevented clean compile on OS X. Fixes bug 1363; bugfix on
45 - Fix a segfault on relays when DirReqStatistics is enabled
46 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
50 - Demote a confusing TLS warning that relay operators might get when
51 someone tries to talk to their OrPort. It is neither the operator's
52 fault nor can they do anything about it. Fixes bug 1364; bugfix
56 Changes in version 0.2.2.11-alpha - 2010-04-15
57 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
58 libraries that was causing some relays to drop out of the consensus.
61 - Directory mirrors were fetching relay descriptors only from v2
62 directory authorities, rather than v3 authorities like they should.
63 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
64 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
65 - Fix a parsing error that made every possible value of
66 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
67 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
68 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
69 about the option without breaking older ones.
70 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
71 that claim to be earlier than 0.9.8m, but which have in reality
72 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
73 behavior. Possible fix for some cases of bug 1346.
76 - Experiment with a more aggressive approach to preventing clients
77 from making one-hop exit streams. Exit relays who want to try it
78 out can set "RefuseUnknownExits 1" in their torrc, and then look
79 for "Attempt by %s to open a stream" log messages. Let us know
81 - Add support for statically linking zlib by specifying
82 --enable-static-zlib, to go with our support for statically linking
83 openssl and libevent. Resolves bug 1358.
86 - Fix a segfault that happens whenever a Tor client that is using
87 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
89 - When we cleaned up the contrib/tor-exit-notice.html file, we left
90 out the first line. Fixes bug 1295.
91 - When building the manpage from a tarball, we required asciidoc, but
92 the asciidoc -> roff/html conversion was already done for the
93 tarball. Make 'make' complain only when we need asciidoc (either
94 because we're compiling directly from git, or because we altered
95 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
96 - When none of the directory authorities vote on any params, Tor
97 segfaulted when trying to make the consensus from the votes. We
98 didn't trigger the bug in practice, because authorities do include
99 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
102 - In the util/threads test, no longer free the test_mutex before all
103 worker threads have finished. Bugfix on 0.2.1.6-alpha.
104 - The master thread could starve the worker threads quite badly on
105 certain systems, causing them to run only partially in the allowed
106 window. This resulted in test failures. Now the master thread sleeps
107 occasionally for a few microseconds while the two worker-threads
108 compete for the mutex. Bugfix on 0.2.0.1-alpha.
111 Changes in version 0.2.2.10-alpha - 2010-03-07
112 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
113 could prevent relays from guessing their IP address correctly. It also
114 starts the groundwork for another client-side performance boost, since
115 currently we're not making efficient use of relays that have both the
116 Guard flag and the Exit flag.
119 - Fix a regression from our patch for bug 1244 that caused relays
120 to guess their IP address incorrectly if they didn't set Address
121 in their torrc and/or their address fails to resolve. Bugfix on
122 0.2.2.9-alpha; fixes bug 1269.
124 o Major features (performance):
125 - Directory authorities now compute consensus weightings that instruct
126 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
127 and no flag. Clients that use these weightings will distribute
128 network load more evenly across these different relay types. The
129 weightings are in the consensus so we can change them globally in
130 the future. Extra thanks to "outofwords" for finding some nasty
131 security bugs in the first implementation of this feature.
133 o Minor features (performance):
134 - Always perform router selections using weighted relay bandwidth,
135 even if we don't need a high capacity circuit at the time. Non-fast
136 circuits now only differ from fast ones in that they can use relays
137 not marked with the Fast flag. This "feature" could turn out to
138 be a horrible bug; we should investigate more before it goes into
142 - Allow disabling building of the manpages. Skipping the manpage
143 speeds up the build considerably.
145 o Minor bugfixes (on 0.2.2.x):
146 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
147 Bugfix on 0.2.2.9-alpha.
148 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
149 config option. Bugfix on 0.2.2.7-alpha.
150 - Ship the asciidoc-helper file in the tarball, so that people can
151 build from source if they want to, and touching the .1.txt files
152 doesn't break the build. Bugfix on 0.2.2.9-alpha.
154 o Minor bugfixes (on 0.2.1.x or earlier):
155 - Fix a dereference-then-NULL-check sequence when publishing
156 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
158 - Fix another dereference-then-NULL-check sequence. Bugfix on
159 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
160 - Make sure we treat potentially not NUL-terminated strings correctly.
161 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
163 o Code simplifications and refactoring:
164 - Fix some urls in the exit notice file and make it XHTML1.1 strict
165 compliant. Based on a patch from Christian Kujau.
166 - Don't use sed in asciidoc-helper anymore.
167 - Make the build process fail if asciidoc cannot be found and
168 building with asciidoc isn't disabled.
171 Changes in version 0.2.2.9-alpha - 2010-02-22
172 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
173 location of a directory authority, and cleans up a bunch of small bugs.
175 o Directory authority changes:
176 - Change IP address for dannenberg (v3 directory authority), and
177 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
178 service directory authority) from the list.
181 - Make Tor work again on the latest OS X: when deciding whether to
182 use strange flags to turn TLS renegotiation on, detect the OpenSSL
183 version at run-time, not compile time. We need to do this because
184 Apple doesn't update its dev-tools headers when it updates its
185 libraries in a security patch.
186 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
187 that could happen on 32-bit platforms with 64-bit time_t. Also fix
188 a memory leak when requesting a hidden service descriptor we've
189 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
191 - Authorities could be tricked into giving out the Exit flag to relays
192 that didn't allow exiting to any ports. This bug could screw
193 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
194 1238. Bug discovered by Martin Kowalczyk.
195 - When freeing a session key, zero it out completely. We only zeroed
196 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
197 patched by ekir. Fixes bug 1254.
200 - Fix static compilation by listing the openssl libraries in the right
201 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
202 - Resume handling .exit hostnames in a special way: originally we
203 stripped the .exit part and used the requested exit relay. In
204 0.2.2.1-alpha we stopped treating them in any special way, meaning
205 if you use a .exit address then Tor will pass it on to the exit
206 relay. Now we reject the .exit stream outright, since that behavior
207 might be more expected by the user. Found and diagnosed by Scott
208 Bennett and Downie on or-talk.
209 - Don't spam the controller with events when we have no file
210 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
211 for log messages was already solved from bug 748.)
212 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
214 - Make the DNSPort option work with libevent 2.x. Don't alter the
215 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
216 - Emit a GUARD DROPPED controller event for a case we missed.
217 - Make more fields in the controller protocol case-insensitive, since
218 control-spec.txt said they were.
219 - Refactor resolve_my_address() to not use gethostbyname() anymore.
220 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
221 - Fix a spec conformance issue: the network-status-version token
222 must be the first token in a v3 consensus or vote. Discovered by
223 parakeep. Bugfix on 0.2.0.3-alpha.
225 o Code simplifications and refactoring:
226 - Generate our manpage and HTML documentation using Asciidoc. This
227 change should make it easier to maintain the documentation, and
229 - Remove the --enable-iphone option. According to reports from Marco
230 Bonetti, Tor builds fine without any special tweaking on recent
232 - Removed some unnecessary files from the source distribution. The
233 AUTHORS file has now been merged into the people page on the
234 website. The roadmaps and design doc can now be found in the
235 projects directory in svn.
236 - Enabled various circuit build timeout constants to be controlled
237 by consensus parameters. Also set better defaults for these
238 parameters based on experimentation on broadband and simulated
242 - The 'EXTENDCIRCUIT' control port command can now be used with
243 a circ id of 0 and no path. This feature will cause Tor to build
244 a new 'fast' general purpose circuit using its own path selection
246 - Added a BUILDTIMEOUT_SET controller event to describe changes
247 to the circuit build timeout.
248 - Future-proof the controller protocol a bit by ignoring keyword
249 arguments we do not recognize.
250 - Expand homedirs passed to tor-checkkey. This should silence a
251 coverity complaint about passing a user-supplied string into
252 open() without checking it.
255 Changes in version 0.2.1.25 - 2010-03-16
256 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
257 prevent relays from guessing their IP address correctly. It also fixes
258 several minor potential security bugs.
261 - Fix a regression from our patch for bug 1244 that caused relays
262 to guess their IP address incorrectly if they didn't set Address
263 in their torrc and/or their address fails to resolve. Bugfix on
264 0.2.1.23; fixes bug 1269.
265 - When freeing a session key, zero it out completely. We only zeroed
266 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
267 patched by ekir. Fixes bug 1254.
270 - Fix a dereference-then-NULL-check sequence when publishing
271 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
273 - Fix another dereference-then-NULL-check sequence. Bugfix on
274 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
275 - Make sure we treat potentially not NUL-terminated strings correctly.
276 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
280 Changes in version 0.2.1.24 - 2010-02-21
281 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
285 - Work correctly out-of-the-box with even more vendor-patched versions
286 of OpenSSL. In particular, make it so Debian and OS X don't need
287 customized patches to run/build.
290 Changes in version 0.2.1.23 - 2010-02-13
291 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
292 again on the latest OS X, and updates the location of a directory
295 o Major bugfixes (performance):
296 - We were selecting our guards uniformly at random, and then weighting
297 which of our guards we'd use uniformly at random. This imbalance
298 meant that Tor clients were severely limited on throughput (and
299 probably latency too) by the first hop in their circuit. Now we
300 select guards weighted by currently advertised bandwidth. We also
301 automatically discard guards picked using the old algorithm. Fixes
302 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
305 - Make Tor work again on the latest OS X: when deciding whether to
306 use strange flags to turn TLS renegotiation on, detect the OpenSSL
307 version at run-time, not compile time. We need to do this because
308 Apple doesn't update its dev-tools headers when it updates its
309 libraries in a security patch.
310 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
311 that could happen on 32-bit platforms with 64-bit time_t. Also fix
312 a memory leak when requesting a hidden service descriptor we've
313 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
316 o Directory authority changes:
317 - Change IP address for dannenberg (v3 directory authority), and
318 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
319 service directory authority) from the list.
322 - Refactor resolve_my_address() to not use gethostbyname() anymore.
323 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
326 - Avoid a mad rush at the beginning of each month when each client
327 rotates half of its guards. Instead we spread the rotation out
328 throughout the month, but we still avoid leaving a precise timestamp
329 in the state file about when we first picked the guard. Improves
330 over the behavior introduced in 0.1.2.17.
333 Changes in version 0.2.2.8-alpha - 2010-01-26
334 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
335 causing bridge relays to disappear. If you're running a bridge,
339 - Fix a memory corruption bug on bridges that occured during the
340 inclusion of stats data in extra-info descriptors. Also fix the
341 interface for geoip_get_bridge_stats* to prevent similar bugs in
342 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
343 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
346 - Ignore OutboundBindAddress when connecting to localhost.
347 Connections to localhost need to come _from_ localhost, or else
348 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
352 Changes in version 0.2.2.7-alpha - 2010-01-19
353 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
354 as laying the groundwork for further relay-side performance fixes. It
355 also starts cleaning up client behavior with respect to the EntryNodes,
356 ExitNodes, and StrictNodes config options.
358 This release also rotates two directory authority keys, due to a
359 security breach of some of the Torproject servers.
361 o Directory authority changes:
362 - Rotate keys (both v3 identity and relay identity) for moria1
365 o Major features (performance):
366 - We were selecting our guards uniformly at random, and then weighting
367 which of our guards we'd use uniformly at random. This imbalance
368 meant that Tor clients were severely limited on throughput (and
369 probably latency too) by the first hop in their circuit. Now we
370 select guards weighted by currently advertised bandwidth. We also
371 automatically discard guards picked using the old algorithm. Fixes
372 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
373 - When choosing which cells to relay first, relays can now favor
374 circuits that have been quiet recently, to provide lower latency
375 for low-volume circuits. By default, relays enable or disable this
376 feature based on a setting in the consensus. You can override
377 this default by using the new "CircuitPriorityHalflife" config
378 option. Design and code by Ian Goldberg, Can Tang, and Chris
380 - Add separate per-conn write limiting to go with the per-conn read
381 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
382 but never per-conn write limits.
383 - New consensus params "bwconnrate" and "bwconnburst" to let us
384 rate-limit client connections as they enter the network. It's
385 controlled in the consensus so we can turn it on and off for
386 experiments. It's starting out off. Based on proposal 163.
388 o Major features (relay selection options):
389 - Switch to a StrictNodes config option, rather than the previous
390 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
391 "StrictExcludeNodes" option.
392 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
393 change during a config reload, mark and discard all our origin
394 circuits. This fix should address edge cases where we change the
395 config options and but then choose a circuit that we created before
397 - If EntryNodes or ExitNodes are set, be more willing to use an
398 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
400 - Make EntryNodes config option much more aggressive even when
401 StrictNodes is not set. Before it would prepend your requested
402 entrynodes to your list of guard nodes, but feel free to use others
403 after that. Now it chooses only from your EntryNodes if any of
404 those are available, and only falls back to others if a) they're
405 all down and b) StrictNodes is not set.
406 - Now we refresh your entry guards from EntryNodes at each consensus
407 fetch -- rather than just at startup and then they slowly rot as
411 - Stop bridge directory authorities from answering dbg-stability.txt
412 directory queries, which would let people fetch a list of all
413 bridge identities they track. Bugfix on 0.2.1.6-alpha.
416 - Log a notice when we get a new control connection. Now it's easier
417 for security-conscious users to recognize when a local application
418 is knocking on their controller door. Suggested by bug 1196.
419 - New config option "CircuitStreamTimeout" to override our internal
420 timeout schedule for how many seconds until we detach a stream from
421 a circuit and try a new circuit. If your network is particularly
422 slow, you might want to set this to a number like 60.
423 - New controller command "getinfo config-text". It returns the
424 contents that Tor would write if you send it a SAVECONF command,
425 so the controller can write the file to disk itself.
426 - New options for SafeLogging to allow scrubbing only log messages
427 generated while acting as a relay.
428 - Ship the bridges spec file in the tarball too.
429 - Avoid a mad rush at the beginning of each month when each client
430 rotates half of its guards. Instead we spread the rotation out
431 throughout the month, but we still avoid leaving a precise timestamp
432 in the state file about when we first picked the guard. Improves
433 over the behavior introduced in 0.1.2.17.
435 o Minor bugfixes (compiling):
436 - Fix compilation on OS X 10.3, which has a stub mlockall() but
437 hides it. Bugfix on 0.2.2.6-alpha.
438 - Fix compilation on Solaris by removing support for the
439 DisableAllSwap config option. Solaris doesn't have an rlimit for
440 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
443 o Minor bugfixes (crashes):
444 - Do not segfault when writing buffer stats when we haven't observed
445 a single circuit to report about. Found by Fabian Lanze. Bugfix on
447 - If we're in the pathological case where there's no exit bandwidth
448 but there is non-exit bandwidth, or no guard bandwidth but there
449 is non-guard bandwidth, don't crash during path selection. Bugfix
451 - Fix an impossible-to-actually-trigger buffer overflow in relay
452 descriptor generation. Bugfix on 0.1.0.15.
454 o Minor bugfixes (privacy):
455 - Fix an instance where a Tor directory mirror might accidentally
456 log the IP address of a misbehaving Tor client. Bugfix on
458 - Don't list Windows capabilities in relay descriptors. We never made
459 use of them, and maybe it's a bad idea to publish them. Bugfix
462 o Minor bugfixes (other):
463 - Resolve an edge case in path weighting that could make us misweight
464 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
465 - Fix statistics on client numbers by country as seen by bridges that
466 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
467 intervals instead of variable 12-to-48-hour intervals.
468 - After we free an internal connection structure, overwrite it
469 with a different memory value than we use for overwriting a freed
470 internal circuit structure. Should help with debugging. Suggested
472 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
476 - Remove the HSAuthorityRecordStats option that version 0 hidden
477 service authorities could have used to track statistics of overall
478 hidden service usage.
481 Changes in version 0.2.1.22 - 2010-01-19
482 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
483 authorities -- it would tell you its whole history of bridge descriptors
484 if you make the right directory request. This stable update also
485 rotates two of the seven v3 directory authority keys and locations.
487 o Directory authority changes:
488 - Rotate keys (both v3 identity and relay identity) for moria1
492 - Stop bridge directory authorities from answering dbg-stability.txt
493 directory queries, which would let people fetch a list of all
494 bridge identities they track. Bugfix on 0.2.1.6-alpha.
497 Changes in version 0.2.1.21 - 2009-12-21
498 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
499 library. If you use Tor on Linux / Unix and you're getting SSL
500 renegotiation errors, upgrading should help. We also recommend an
501 upgrade if you're an exit relay.
504 - Work around a security feature in OpenSSL 0.9.8l that prevents our
505 handshake from working unless we explicitly tell OpenSSL that we
506 are using SSL renegotiation safely. We are, of course, but OpenSSL
507 0.9.8l won't work unless we say we are.
508 - Avoid crashing if the client is trying to upload many bytes and the
509 circuit gets torn down at the same time, or if the flip side
510 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
513 - Do not refuse to learn about authority certs and v2 networkstatus
514 documents that are older than the latest consensus. This bug might
515 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
516 Spotted and fixed by xmux.
517 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
518 trigger platform-specific option misparsing case found by Coverity
520 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
521 trigger assert. Fixes bug 1173.
524 Changes in version 0.2.2.6-alpha - 2009-11-19
525 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
526 support for the new lower-footprint "microdescriptor" directory design,
527 future-proofing our consensus format against new hash functions or
528 other changes, and an Android port. It also makes Tor compatible with
529 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
532 - Directory authorities can now create, vote on, and serve multiple
533 parallel formats of directory data as part of their voting process.
534 Partially implements Proposal 162: "Publish the consensus in
536 - Directory authorities can now agree on and publish small summaries
537 of router information that clients can use in place of regular
538 server descriptors. This transition will eventually allow clients
539 to use far less bandwidth for downloading information about the
540 network. Begins the implementation of Proposal 158: "Clients
541 download consensus + microdescriptors".
542 - The directory voting system is now extensible to use multiple hash
543 algorithms for signatures and resource selection. Newer formats
544 are signed with SHA256, with a possibility for moving to a better
545 hash algorithm in the future.
546 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
547 current and future memory pages via mlockall(). On supported
548 platforms (modern Linux and probably BSD but not Windows or OS X),
549 this should effectively disable any and all attempts to page out
550 memory. This option requires that you start your Tor as root --
551 if you use DisableAllSwap, please consider using the User option
552 to properly reduce the privileges of your Tor.
553 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
554 to help Tor build correctly for Android phones.
557 - Work around a security feature in OpenSSL 0.9.8l that prevents our
558 handshake from working unless we explicitly tell OpenSSL that we
559 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
560 won't work unless we say we are.
563 - Fix a crash bug when trying to initialize the evdns module in
564 Libevent 2. Bugfix on 0.2.1.16-rc.
565 - Stop logging at severity 'warn' when some other Tor client tries
566 to establish a circuit with us using weak DH keys. It's a protocol
567 violation, but that doesn't mean ordinary users need to hear about
568 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
569 - Do not refuse to learn about authority certs and v2 networkstatus
570 documents that are older than the latest consensus. This bug might
571 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
572 Spotted and fixed by xmux.
573 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
574 - If all authorities restart at once right before a consensus vote,
575 nobody will vote about "Running", and clients will get a consensus
576 with no usable relays. Instead, authorities refuse to build a
577 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
578 - If your relay can't keep up with the number of incoming create
579 cells, it would log one warning per failure into your logs. Limit
580 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
581 - Bridges now use "reject *:*" as their default exit policy. Bugfix
582 on 0.2.0.3-alpha; fixes bug 1113.
583 - Fix a memory leak on directory authorities during voting that was
584 introduced in 0.2.2.1-alpha. Found via valgrind.
587 Changes in version 0.2.1.20 - 2009-10-15
588 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
589 services at once, prepares for more performance improvements, and
590 fixes a bunch of smaller bugs.
592 The Windows and OS X bundles also include a more recent Vidalia,
593 and switch from Privoxy to Polipo.
595 The OS X installers are now drag and drop. It's best to un-install
596 Tor/Vidalia and then install this new bundle, rather than upgrade. If
597 you want to upgrade, you'll need to update the paths for Tor and Polipo
598 in the Vidalia Settings window.
601 - Send circuit or stream sendme cells when our window has decreased
602 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
603 by Karsten when testing the "reduce circuit window" performance
604 patch. Bugfix on the 54th commit on Tor -- from July 2002,
605 before the release of Tor 0.0.0. This is the new winner of the
607 - Fix a remotely triggerable memory leak when a consensus document
608 contains more than one signature from the same voter. Bugfix on
610 - Avoid segfault in rare cases when finishing an introduction circuit
611 as a client and finding out that we don't have an introduction key
612 for it. Fixes bug 1073. Reported by Aaron Swartz.
615 - Tor now reads the "circwindow" parameter out of the consensus,
616 and uses that value for its circuit package window rather than the
617 default of 1000 cells. Begins the implementation of proposal 168.
619 o New directory authorities:
620 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
622 - Move moria1 and tonga to alternate IP addresses.
625 - Fix a signed/unsigned compile warning in 0.2.1.19.
626 - Fix possible segmentation fault on directory authorities. Bugfix on
628 - Fix an extremely rare infinite recursion bug that could occur if
629 we tried to log a message after shutting down the log subsystem.
630 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
631 - Fix an obscure bug where hidden services on 64-bit big-endian
632 systems might mis-read the timestamp in v3 introduce cells, and
633 refuse to connect back to the client. Discovered by "rotor".
634 Bugfix on 0.2.1.6-alpha.
635 - We were triggering a CLOCK_SKEW controller status event whenever
636 we connect via the v2 connection protocol to any relay that has
637 a wrong clock. Instead, we should only inform the controller when
638 it's a trusted authority that claims our clock is wrong. Bugfix
639 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
640 - We were telling the controller about CHECKING_REACHABILITY and
641 REACHABILITY_FAILED status events whenever we launch a testing
642 circuit or notice that one has failed. Instead, only tell the
643 controller when we want to inform the user of overall success or
644 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
646 - Don't warn when we're using a circuit that ends with a node
647 excluded in ExcludeExitNodes, but the circuit is not used to access
648 the outside world. This should help fix bug 1090. Bugfix on
650 - Work around a small memory leak in some versions of OpenSSL that
651 stopped the memory used by the hostname TLS extension from being
655 - Add a "getinfo status/accepted-server-descriptor" controller
656 command, which is the recommended way for controllers to learn
657 whether our server descriptor has been successfully received by at
658 least on directory authority. Un-recommend good-server-descriptor
659 getinfo and status events until we have a better design for them.
662 Changes in version 0.2.2.5-alpha - 2009-10-11
663 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
666 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
668 o New directory authorities:
669 - Move dizum to an alternate IP address.
672 Changes in version 0.2.2.4-alpha - 2009-10-10
673 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
674 introduces a new unit test framework, shifts directry authority
675 addresses around to reduce the impact from recent blocking events,
676 and fixes a few smaller bugs.
679 - Fix several more asserts in the circuit_build_times code, for
680 example one that causes Tor to fail to start once we have
681 accumulated 5000 build times in the state file. Bugfixes on
682 0.2.2.2-alpha; fixes bug 1108.
684 o New directory authorities:
685 - Move moria1 and Tonga to alternate IP addresses.
688 - Log SSL state transitions at debug level during handshake, and
689 include SSL states in error messages. This may help debug future
690 SSL handshake issues.
691 - Add a new "Handshake" log domain for activities that happen
692 during the TLS handshake.
693 - Revert to the "June 3 2009" ip-to-country file. The September one
694 seems to have removed most US IP addresses.
695 - Directory authorities now reject Tor relays with versions less than
696 0.1.2.14. This step cuts out four relays from the current network,
697 none of which are very big.
700 - Fix a couple of smaller issues with gathering statistics. Bugfixes
702 - Fix two memory leaks in the error case of
703 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
704 - Don't count one-hop circuits when we're estimating how long it
705 takes circuits to build on average. Otherwise we'll set our circuit
706 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
707 - Directory authorities no longer change their opinion of, or vote on,
708 whether a router is Running, unless they have themselves been
709 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
712 o Code simplifications and refactoring:
713 - Revise our unit tests to use the "tinytest" framework, so we
714 can run tests in their own processes, have smarter setup/teardown
715 code, and so on. The unit test code has moved to its own
716 subdirectory, and has been split into multiple modules.
719 Changes in version 0.2.2.3-alpha - 2009-09-23
720 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
723 - Fix an overzealous assert in our new circuit build timeout code.
724 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
727 - If the networkstatus consensus tells us that we should use a
728 negative circuit package window, ignore it. Otherwise we'll
729 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
732 Changes in version 0.2.2.2-alpha - 2009-09-21
733 Tor 0.2.2.2-alpha introduces our latest performance improvement for
734 clients: Tor tracks the average time it takes to build a circuit, and
735 avoids using circuits that take too long to build. For fast connections,
736 this feature can cut your expected latency in half. For slow or flaky
737 connections, it could ruin your Tor experience. Let us know if it does!
740 - Tor now tracks how long it takes to build client-side circuits
741 over time, and adapts its timeout to local network performance.
742 Since a circuit that takes a long time to build will also provide
743 bad performance, we get significant latency improvements by
744 discarding the slowest 20% of circuits. Specifically, Tor creates
745 circuits more aggressively than usual until it has enough data
746 points for a good timeout estimate. Implements proposal 151.
747 We are especially looking for reports (good and bad) from users with
748 both EDGE and broadband connections that can move from broadband
749 to EDGE and find out if the build-time data in the .tor/state gets
750 reset without loss of Tor usability. You should also see a notice
751 log message telling you that Tor has reset its timeout.
752 - Directory authorities can now vote on arbitary integer values as
753 part of the consensus process. This is designed to help set
754 network-wide parameters. Implements proposal 167.
755 - Tor now reads the "circwindow" parameter out of the consensus,
756 and uses that value for its circuit package window rather than the
757 default of 1000 cells. Begins the implementation of proposal 168.
760 - Fix a remotely triggerable memory leak when a consensus document
761 contains more than one signature from the same voter. Bugfix on
765 - Fix an extremely rare infinite recursion bug that could occur if
766 we tried to log a message after shutting down the log subsystem.
767 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
768 - Fix parsing for memory or time units given without a space between
769 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
770 - A networkstatus vote must contain exactly one signature. Spec
771 conformance issue. Bugfix on 0.2.0.3-alpha.
772 - Fix an obscure bug where hidden services on 64-bit big-endian
773 systems might mis-read the timestamp in v3 introduce cells, and
774 refuse to connect back to the client. Discovered by "rotor".
775 Bugfix on 0.2.1.6-alpha.
776 - We were triggering a CLOCK_SKEW controller status event whenever
777 we connect via the v2 connection protocol to any relay that has
778 a wrong clock. Instead, we should only inform the controller when
779 it's a trusted authority that claims our clock is wrong. Bugfix
780 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
781 - We were telling the controller about CHECKING_REACHABILITY and
782 REACHABILITY_FAILED status events whenever we launch a testing
783 circuit or notice that one has failed. Instead, only tell the
784 controller when we want to inform the user of overall success or
785 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
787 - Don't warn when we're using a circuit that ends with a node
788 excluded in ExcludeExitNodes, but the circuit is not used to access
789 the outside world. This should help fix bug 1090, but more problems
790 remain. Bugfix on 0.2.1.6-alpha.
791 - Work around a small memory leak in some versions of OpenSSL that
792 stopped the memory used by the hostname TLS extension from being
794 - Make our 'torify' script more portable; if we have only one of
795 'torsocks' or 'tsocks' installed, don't complain to the user;
796 and explain our warning about tsocks better.
799 - Add a "getinfo status/accepted-server-descriptor" controller
800 command, which is the recommended way for controllers to learn
801 whether our server descriptor has been successfully received by at
802 least on directory authority. Un-recommend good-server-descriptor
803 getinfo and status events until we have a better design for them.
804 - Update to the "September 4 2009" ip-to-country file.
807 Changes in version 0.2.2.1-alpha - 2009-08-26
808 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
809 Tor clients to bootstrap on networks where only port 80 is reachable,
810 makes it more straightforward to support hardware crypto accelerators,
811 and starts the groundwork for gathering stats safely at relays.
814 - Start the process of disabling ".exit" address notation, since it
815 can be used for a variety of esoteric application-level attacks
816 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
819 o New directory authorities:
820 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
824 - New AccelName and AccelDir options add support for dynamic OpenSSL
825 hardware crypto acceleration engines.
826 - Tor now supports tunneling all of its outgoing connections over
827 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
828 configuration options. Code by Christopher Davis.
831 - Send circuit or stream sendme cells when our window has decreased
832 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
833 by Karsten when testing the "reduce circuit window" performance
834 patch. Bugfix on the 54th commit on Tor -- from July 2002,
835 before the release of Tor 0.0.0. This is the new winner of the
838 o New options for gathering stats safely:
839 - Directories that set "DirReqStatistics 1" write statistics on
840 directory request to disk every 24 hours. As compared to the
841 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
842 1) stats are written to disk exactly every 24 hours; 2) estimated
843 shares of v2 and v3 requests are determined as mean values, not at
844 the end of a measurement period; 3) unresolved requests are listed
845 with country code '??'; 4) directories also measure download times.
846 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
847 number of exit streams and transferred bytes per port to disk every
849 - Relays that set "CellStatistics 1" write statistics on how long
850 cells spend in their circuit queues to disk every 24 hours.
851 - Entry nodes that set "EntryStatistics 1" write statistics on the
852 rough number and origins of connecting clients to disk every 24
854 - Relays that write any of the above statistics to disk and set
855 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
856 their extra-info documents.
859 - New --digests command-line switch to output the digests of the
860 source files Tor was built with.
861 - The "torify" script now uses torsocks where available.
862 - The memarea code now uses a sentinel value at the end of each area
863 to make sure nothing writes beyond the end of an area. This might
864 help debug some conceivable causes of bug 930.
865 - Time and memory units in the configuration file can now be set to
866 fractional units. For example, "2.5 GB" is now a valid value for
868 - Certain Tor clients (such as those behind check.torproject.org) may
869 want to fetch the consensus in an extra early manner. To enable this
870 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
871 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
872 as only certain clients who must have this information sooner should
874 - Instead of adding the svn revision to the Tor version string, report
875 the git commit (when we're building from a git checkout).
878 - If any the v3 certs we download are unparseable, we should actually
879 notice the failure so we don't retry indefinitely. Bugfix on
880 0.2.0.x; reported by "rotator".
881 - If the cached cert file is unparseable, warn but don't exit.
882 - Fix possible segmentation fault on directory authorities. Bugfix on
884 - When Tor fails to parse a descriptor of any kind, dump it to disk.
885 Might help diagnosing bug 1051.
887 o Deprecated and removed features:
888 - The controller no longer accepts the old obsolete "addr-mappings/"
889 or "unregistered-servers-" GETINFO values.
890 - Hidden services no longer publish version 0 descriptors, and clients
891 do not request or use version 0 descriptors. However, the old hidden
892 service authorities still accept and serve version 0 descriptors
893 when contacted by older hidden services/clients.
894 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
895 always on; using them is necessary for correct forward-compatible
897 - Remove support for .noconnect style addresses. Nobody was using
898 them, and they provided another avenue for detecting Tor users
899 via application-level web tricks.
902 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
903 installer bundles. See
904 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
905 for details of what's new in Vidalia 0.2.3.
906 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
907 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
908 configuration file, rather than the old Privoxy.
909 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
910 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
911 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
912 better compatibility with OS X 10.6, aka Snow Leopard.
913 - OS X Vidalia Bundle: The multi-package installer is now replaced
914 by a simple drag and drop to the /Applications folder. This change
915 occurred with the upgrade to Vidalia 0.2.3.
918 Changes in version 0.2.1.19 - 2009-07-28
919 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
920 services on Tor 0.2.1.3-alpha through 0.2.1.18.
923 - Make accessing hidden services on 0.2.1.x work right again.
924 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
925 part of patch provided by "optimist".
928 - When a relay/bridge is writing out its identity key fingerprint to
929 the "fingerprint" file and to its logs, write it without spaces. Now
930 it will look like the fingerprints in our bridges documentation,
931 and confuse fewer users.
934 - Relays no longer publish a new server descriptor if they change
935 their MaxAdvertisedBandwidth config option but it doesn't end up
936 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
937 fixes bug 1026. Patch from Sebastian.
938 - Avoid leaking memory every time we get a create cell but we have
939 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
940 fixes bug 1034. Reported by BarkerJr.
943 Changes in version 0.2.1.18 - 2009-07-24
944 Tor 0.2.1.18 lays the foundations for performance improvements,
945 adds status events to help users diagnose bootstrap problems, adds
946 optional authentication/authorization for hidden services, fixes a
947 variety of potential anonymity problems, and includes a huge pile of
948 other features and bug fixes.
951 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
954 Changes in version 0.2.1.17-rc - 2009-07-07
955 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
956 candidate for the 0.2.1.x series. It lays the groundwork for further
957 client performance improvements, and also fixes a big bug with directory
958 authorities that were causing them to assign Guard and Stable flags
961 The Windows bundles also finally include the geoip database that we
962 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
963 should actually install Torbutton rather than giving you a cryptic
964 failure message (oops).
967 - Clients now use the bandwidth values in the consensus, rather than
968 the bandwidth values in each relay descriptor. This approach opens
969 the door to more accurate bandwidth estimates once the directory
970 authorities start doing active measurements. Implements more of
974 - When Tor clients restart after 1-5 days, they discard all their
975 cached descriptors as too old, but they still use the cached
976 consensus document. This approach is good for robustness, but
977 bad for performance: since they don't know any bandwidths, they
978 end up choosing at random rather than weighting their choice by
979 speed. Fixed by the above feature of putting bandwidths in the
980 consensus. Bugfix on 0.2.0.x.
981 - Directory authorities were neglecting to mark relays down in their
982 internal histories if the relays fall off the routerlist without
983 ever being found unreachable. So there were relays in the histories
984 that haven't been seen for eight months, and are listed as being
985 up for eight months. This wreaked havoc on the "median wfu"
986 and "median mtbf" calculations, in turn making Guard and Stable
987 flags very wrong, hurting network performance. Fixes bugs 696 and
988 969. Bugfix on 0.2.0.6-alpha.
991 - Serve the DirPortFrontPage page even when we have been approaching
992 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
993 - The control port would close the connection before flushing long
994 replies, such as the network consensus, if a QUIT command was issued
995 before the reply had completed. Now, the control port flushes all
996 pending replies before closing the connection. Also fixed a spurious
997 warning when a QUIT command is issued after a malformed or rejected
998 AUTHENTICATE command, but before the connection was closed. Patch
999 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
1000 - When we can't find an intro key for a v2 hidden service descriptor,
1001 fall back to the v0 hidden service descriptor and log a bug message.
1002 Workaround for bug 1024.
1003 - Fix a log message that did not respect the SafeLogging option.
1007 - If we're a relay and we change our IP address, be more verbose
1008 about the reason that made us change. Should help track down
1009 further bugs for relays on dynamic IP addresses.
1012 Changes in version 0.2.0.35 - 2009-06-24
1014 - Avoid crashing in the presence of certain malformed descriptors.
1015 Found by lark, and by automated fuzzing.
1016 - Fix an edge case where a malicious exit relay could convince a
1017 controller that the client's DNS question resolves to an internal IP
1018 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
1021 - Finally fix the bug where dynamic-IP relays disappear when their
1022 IP address changes: directory mirrors were mistakenly telling
1023 them their old address if they asked via begin_dir, so they
1024 never got an accurate answer about their new address, so they
1025 just vanished after a day. For belt-and-suspenders, relays that
1026 don't set Address in their config now avoid using begin_dir for
1027 all direct connections. Should fix bugs 827, 883, and 900.
1028 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
1029 that would occur on some exit nodes when DNS failures and timeouts
1030 occurred in certain patterns. Fix for bug 957.
1033 - When starting with a cache over a few days old, do not leak
1034 memory for the obsolete router descriptors in it. Bugfix on
1035 0.2.0.33; fixes bug 672.
1036 - Hidden service clients didn't use a cached service descriptor that
1037 was older than 15 minutes, but wouldn't fetch a new one either,
1038 because there was already one in the cache. Now, fetch a v2
1039 descriptor unless the same descriptor was added to the cache within
1040 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
1043 Changes in version 0.2.1.16-rc - 2009-06-20
1044 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
1045 a bunch of minor bugs.
1048 - Fix an edge case where a malicious exit relay could convince a
1049 controller that the client's DNS question resolves to an internal IP
1050 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
1052 o Major performance improvements (on 0.2.0.x):
1053 - Disable and refactor some debugging checks that forced a linear scan
1054 over the whole server-side DNS cache. These accounted for over 50%
1055 of CPU time on a relatively busy exit node's gprof profile. Found
1057 - Disable some debugging checks that appeared in exit node profile
1061 - Update to the "June 3 2009" ip-to-country file.
1062 - Do not have tor-resolve automatically refuse all .onion addresses;
1063 if AutomapHostsOnResolve is set in your torrc, this will work fine.
1065 o Minor bugfixes (on 0.2.0.x):
1066 - Log correct error messages for DNS-related network errors on
1068 - Fix a race condition that could cause crashes or memory corruption
1069 when running as a server with a controller listening for log
1071 - Avoid crashing when we have a policy specified in a DirPolicy or
1072 SocksPolicy or ReachableAddresses option with ports set on it,
1073 and we re-load the policy. May fix bug 996.
1074 - Hidden service clients didn't use a cached service descriptor that
1075 was older than 15 minutes, but wouldn't fetch a new one either,
1076 because there was already one in the cache. Now, fetch a v2
1077 descriptor unless the same descriptor was added to the cache within
1078 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
1080 o Minor bugfixes (on 0.2.1.x):
1081 - Don't warn users about low port and hibernation mix when they
1082 provide a *ListenAddress directive to fix that. Bugfix on
1084 - When switching back and forth between bridge mode, do not start
1085 gathering GeoIP data until two hours have passed.
1086 - Do not complain that the user has requested an excluded node as
1087 an exit when the node is not really an exit. This could happen
1088 because the circuit was for testing, or an introduction point.
1092 Changes in version 0.2.1.15-rc - 2009-05-25
1093 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
1094 series. It fixes a major bug on fast exit relays, as well as a variety
1097 o Major bugfixes (on 0.2.0.x):
1098 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
1099 that would occur on some exit nodes when DNS failures and timeouts
1100 occurred in certain patterns. Fix for bug 957.
1102 o Minor bugfixes (on 0.2.0.x):
1103 - Actually return -1 in the error case for read_bandwidth_usage().
1104 Harmless bug, since we currently don't care about the return value
1105 anywhere. Bugfix on 0.2.0.9-alpha.
1106 - Provide a more useful log message if bug 977 (related to buffer
1107 freelists) ever reappears, and do not crash right away.
1108 - Fix an assertion failure on 64-bit platforms when we allocated
1109 memory right up to the end of a memarea, then realigned the memory
1110 one step beyond the end. Fixes a possible cause of bug 930.
1111 - Protect the count of open sockets with a mutex, so we can't
1112 corrupt it when two threads are closing or opening sockets at once.
1113 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
1114 - Don't allow a bridge to publish its router descriptor to a
1115 non-bridge directory authority. Fixes part of bug 932.
1116 - When we change to or from being a bridge, reset our counts of
1117 client usage by country. Fixes bug 932.
1118 - Fix a bug that made stream bandwidth get misreported to the
1120 - Stop using malloc_usable_size() to use more area than we had
1121 actually allocated: it was safe, but made valgrind really unhappy.
1122 - Fix a memory leak when v3 directory authorities load their keys
1123 and cert from disk. Bugfix on 0.2.0.1-alpha.
1125 o Minor bugfixes (on 0.2.1.x):
1126 - Fix use of freed memory when deciding to mark a non-addable
1127 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
1130 Changes in version 0.2.1.14-rc - 2009-04-12
1131 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
1132 series. It begins fixing some major performance problems, and also
1133 finally addresses the bug that was causing relays on dynamic IP
1134 addresses to fall out of the directory.
1137 - Clients replace entry guards that were chosen more than a few months
1138 ago. This change should significantly improve client performance,
1139 especially once more people upgrade, since relays that have been
1140 a guard for a long time are currently overloaded.
1142 o Major bugfixes (on 0.2.0):
1143 - Finally fix the bug where dynamic-IP relays disappear when their
1144 IP address changes: directory mirrors were mistakenly telling
1145 them their old address if they asked via begin_dir, so they
1146 never got an accurate answer about their new address, so they
1147 just vanished after a day. For belt-and-suspenders, relays that
1148 don't set Address in their config now avoid using begin_dir for
1149 all direct connections. Should fix bugs 827, 883, and 900.
1150 - Relays were falling out of the networkstatus consensus for
1151 part of a day if they changed their local config but the
1152 authorities discarded their new descriptor as "not sufficiently
1153 different". Now directory authorities accept a descriptor as changed
1154 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
1156 - Avoid crashing in the presence of certain malformed descriptors.
1157 Found by lark, and by automated fuzzing.
1160 - When generating circuit events with verbose nicknames for
1161 controllers, try harder to look up nicknames for routers on a
1162 circuit. (Previously, we would look in the router descriptors we had
1163 for nicknames, but not in the consensus.) Partial fix for bug 941.
1164 - If the bridge config line doesn't specify a port, assume 443.
1165 This makes bridge lines a bit smaller and easier for users to
1167 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
1168 bytes (aka 20KB/s), to match our documentation. Also update
1169 directory authorities so they always assign the Fast flag to relays
1170 with 20KB/s of capacity. Now people running relays won't suddenly
1171 find themselves not seeing any use, if the network gets faster
1173 - Update to the "April 3 2009" ip-to-country file.
1176 - Avoid trying to print raw memory to the logs when we decide to
1177 give up on downloading a given relay descriptor. Bugfix on
1179 - In tor-resolve, when the Tor client to use is specified by
1180 <hostname>:<port>, actually use the specified port rather than
1181 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
1182 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
1183 - When starting with a cache over a few days old, do not leak
1184 memory for the obsolete router descriptors in it. Bugfix on
1186 - Avoid double-free on list of successfully uploaded hidden
1187 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
1188 - Change memarea_strndup() implementation to work even when
1189 duplicating a string at the end of a page. This bug was
1190 harmless for now, but could have meant crashes later. Fix by
1191 lark. Bugfix on 0.2.1.1-alpha.
1192 - Limit uploaded directory documents to be 16M rather than 500K.
1193 The directory authorities were refusing v3 consensus votes from
1194 other authorities, since the votes are now 504K. Fixes bug 959;
1195 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
1196 - Directory authorities should never send a 503 "busy" response to
1197 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
1201 Changes in version 0.2.1.13-alpha - 2009-03-09
1202 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
1203 cleanups. We're finally getting close to a release candidate.
1206 - Correctly update the list of which countries we exclude as
1207 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
1208 lark. Bugfix on 0.2.1.6-alpha.
1210 o Minor bugfixes (on 0.2.0.x and earlier):
1211 - Automatically detect MacOSX versions earlier than 10.4.0, and
1212 disable kqueue from inside Tor when running with these versions.
1213 We previously did this from the startup script, but that was no
1214 help to people who didn't use the startup script. Resolves bug 863.
1215 - When we had picked an exit node for a connection, but marked it as
1216 "optional", and it turned out we had no onion key for the exit,
1217 stop wanting that exit and try again. This situation may not
1218 be possible now, but will probably become feasible with proposal
1219 158. Spotted by rovv. Fixes another case of bug 752.
1220 - Clients no longer cache certificates for authorities they do not
1221 recognize. Bugfix on 0.2.0.9-alpha.
1222 - When we can't transmit a DNS request due to a network error, retry
1223 it after a while, and eventually transmit a failing response to
1224 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
1225 - If the controller claimed responsibility for a stream, but that
1226 stream never finished making its connection, it would live
1227 forever in circuit_wait state. Now we close it after SocksTimeout
1228 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
1229 - Drop begin cells to a hidden service if they come from the middle
1230 of a circuit. Patch from lark.
1231 - When we erroneously receive two EXTEND cells for the same circuit
1232 ID on the same connection, drop the second. Patch from lark.
1233 - Fix a crash that occurs on exit nodes when a nameserver request
1234 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
1235 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
1237 - Do not assume that a stack-allocated character array will be
1238 64-bit aligned on platforms that demand that uint64_t access is
1239 aligned. Possible fix for bug 604.
1240 - Parse dates and IPv4 addresses in a locale- and libc-independent
1241 manner, to avoid platform-dependent behavior on malformed input.
1242 - Build correctly when configured to build outside the main source
1243 path. Patch from Michael Gold.
1244 - We were already rejecting relay begin cells with destination port
1245 of 0. Now also reject extend cells with destination port or address
1246 of 0. Suggested by lark.
1248 o Minor bugfixes (on 0.2.1.x):
1249 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
1250 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
1251 - If we're an exit node, scrub the IP address to which we are exiting
1252 in the logs. Bugfix on 0.2.1.8-alpha.
1255 - On Linux, use the prctl call to re-enable core dumps when the user
1257 - New controller event NEWCONSENSUS that lists the networkstatus
1258 lines for every recommended relay. Now controllers like Torflow
1259 can keep up-to-date on which relays they should be using.
1260 - Update to the "February 26 2009" ip-to-country file.
1263 Changes in version 0.2.0.34 - 2009-02-08
1264 Tor 0.2.0.34 features several more security-related fixes. You should
1265 upgrade, especially if you run an exit relay (remote crash) or a
1266 directory authority (remote infinite loop), or you're on an older
1267 (pre-XP) or not-recently-patched Windows (remote exploit).
1269 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
1270 have many known flaws, and nobody should be using them. You should
1271 upgrade. If you're using a Linux or BSD and its packages are obsolete,
1272 stop using those packages and upgrade anyway.
1275 - Fix an infinite-loop bug on handling corrupt votes under certain
1276 circumstances. Bugfix on 0.2.0.8-alpha.
1277 - Fix a temporary DoS vulnerability that could be performed by
1278 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
1279 - Avoid a potential crash on exit nodes when processing malformed
1280 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
1281 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
1282 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
1285 - Fix compilation on systems where time_t is a 64-bit integer.
1286 Patch from Matthias Drochner.
1287 - Don't consider expiring already-closed client connections. Fixes
1288 bug 893. Bugfix on 0.0.2pre20.
1291 Changes in version 0.2.1.12-alpha - 2009-02-08
1292 Tor 0.2.1.12-alpha features several more security-related fixes. You
1293 should upgrade, especially if you run an exit relay (remote crash) or
1294 a directory authority (remote infinite loop), or you're on an older
1295 (pre-XP) or not-recently-patched Windows (remote exploit). It also
1296 includes a big pile of minor bugfixes and cleanups.
1299 - Fix an infinite-loop bug on handling corrupt votes under certain
1300 circumstances. Bugfix on 0.2.0.8-alpha.
1301 - Fix a temporary DoS vulnerability that could be performed by
1302 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
1303 - Avoid a potential crash on exit nodes when processing malformed
1304 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
1307 - Let controllers actually ask for the "clients_seen" event for
1308 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
1309 reported by Matt Edman.
1310 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
1312 - Fix a bug in address parsing that was preventing bridges or hidden
1313 service targets from being at IPv6 addresses.
1314 - Solve a bug that kept hardware crypto acceleration from getting
1315 enabled when accounting was turned on. Fixes bug 907. Bugfix on
1317 - Remove a bash-ism from configure.in to build properly on non-Linux
1318 platforms. Bugfix on 0.2.1.1-alpha.
1319 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
1320 headers. Bugfix on 0.2.0.10-alpha.
1321 - Don't consider expiring already-closed client connections. Fixes
1322 bug 893. Bugfix on 0.0.2pre20.
1323 - Fix another interesting corner-case of bug 891 spotted by rovv:
1324 Previously, if two hosts had different amounts of clock drift, and
1325 one of them created a new connection with just the wrong timing,
1326 the other might decide to deprecate the new connection erroneously.
1327 Bugfix on 0.1.1.13-alpha.
1328 - Resolve a very rare crash bug that could occur when the user forced
1329 a nameserver reconfiguration during the middle of a nameserver
1330 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
1331 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
1332 Bugfix on 0.2.1.7-alpha.
1333 - If we're using bridges and our network goes away, be more willing
1334 to forgive our bridges and try again when we get an application
1335 request. Bugfix on 0.2.0.x.
1338 - Support platforms where time_t is 64 bits long. (Congratulations,
1339 NetBSD!) Patch from Matthias Drochner.
1340 - Add a 'getinfo status/clients-seen' controller command, in case
1341 controllers want to hear clients_seen events but connect late.
1344 - Disable GCC's strict alias optimization by default, to avoid the
1345 likelihood of its introducing subtle bugs whenever our code violates
1346 the letter of C99's alias rules.
1349 Changes in version 0.2.0.33 - 2009-01-21
1350 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
1351 useful to users. It also finally fixes a bug where a relay or client
1352 that's been off for many days would take a long time to bootstrap.
1354 This update also fixes an important security-related bug reported by
1355 Ilja van Sprundel. You should upgrade. (We'll send out more details
1356 about the bug once people have had some time to upgrade.)
1359 - Fix a heap-corruption bug that may be remotely triggerable on
1360 some platforms. Reported by Ilja van Sprundel.
1363 - When a stream at an exit relay is in state "resolving" or
1364 "connecting" and it receives an "end" relay cell, the exit relay
1365 would silently ignore the end cell and not close the stream. If
1366 the client never closes the circuit, then the exit relay never
1367 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
1369 - When sending CREATED cells back for a given circuit, use a 64-bit
1370 connection ID to find the right connection, rather than an addr:port
1371 combination. Now that we can have multiple OR connections between
1372 the same ORs, it is no longer possible to use addr:port to uniquely
1373 identify a connection.
1374 - Bridge relays that had DirPort set to 0 would stop fetching
1375 descriptors shortly after startup, and then briefly resume
1376 after a new bandwidth test and/or after publishing a new bridge
1377 descriptor. Bridge users that try to bootstrap from them would
1378 get a recent networkstatus but would get descriptors from up to
1379 18 hours earlier, meaning most of the descriptors were obsolete
1380 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
1381 - Prevent bridge relays from serving their 'extrainfo' document
1382 to anybody who asks, now that extrainfo docs include potentially
1383 sensitive aggregated client geoip summaries. Bugfix on
1385 - If the cached networkstatus consensus is more than five days old,
1386 discard it rather than trying to use it. In theory it could be
1387 useful because it lists alternate directory mirrors, but in practice
1388 it just means we spend many minutes trying directory mirrors that
1389 are long gone from the network. Also discard router descriptors as
1390 we load them if they are more than five days old, since the onion
1391 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
1394 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
1395 could make gcc generate non-functional binary search code. Bugfix
1397 - Build correctly on platforms without socklen_t.
1398 - Compile without warnings on solaris.
1399 - Avoid potential crash on internal error during signature collection.
1400 Fixes bug 864. Patch from rovv.
1401 - Correct handling of possible malformed authority signing key
1402 certificates with internal signature types. Fixes bug 880.
1403 Bugfix on 0.2.0.3-alpha.
1404 - Fix a hard-to-trigger resource leak when logging credential status.
1406 - When we can't initialize DNS because the network is down, do not
1407 automatically stop Tor from starting. Instead, we retry failed
1408 dns_init() every 10 minutes, and change the exit policy to reject
1409 *:* until one succeeds. Fixes bug 691.
1410 - Use 64 bits instead of 32 bits for connection identifiers used with
1411 the controller protocol, to greatly reduce risk of identifier reuse.
1412 - When we're choosing an exit node for a circuit, and we have
1413 no pending streams, choose a good general exit rather than one that
1414 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
1415 - Fix another case of assuming, when a specific exit is requested,
1416 that we know more than the user about what hosts it allows.
1417 Fixes one case of bug 752. Patch from rovv.
1418 - Clip the MaxCircuitDirtiness config option to a minimum of 10
1419 seconds. Warn the user if lower values are given in the
1420 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
1421 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
1422 user if lower values are given in the configuration. Bugfix on
1423 0.1.1.17-rc. Patch by Sebastian.
1424 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
1425 the cache because we already had a v0 descriptor with the same ID.
1426 Bugfix on 0.2.0.18-alpha.
1427 - Fix a race condition when freeing keys shared between main thread
1428 and CPU workers that could result in a memory leak. Bugfix on
1429 0.1.0.1-rc. Fixes bug 889.
1430 - Send a valid END cell back when a client tries to connect to a
1431 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
1432 840. Patch from rovv.
1433 - Check which hops rendezvous stream cells are associated with to
1434 prevent possible guess-the-streamid injection attacks from
1435 intermediate hops. Fixes another case of bug 446. Based on patch
1437 - If a broken client asks a non-exit router to connect somewhere,
1438 do not even do the DNS lookup before rejecting the connection.
1439 Fixes another case of bug 619. Patch from rovv.
1440 - When a relay gets a create cell it can't decrypt (e.g. because it's
1441 using the wrong onion key), we were dropping it and letting the
1442 client time out. Now actually answer with a destroy cell. Fixes
1443 bug 904. Bugfix on 0.0.2pre8.
1445 o Minor bugfixes (hidden services):
1446 - Do not throw away existing introduction points on SIGHUP. Bugfix on
1447 0.0.6pre1. Patch by Karsten. Fixes bug 874.
1450 - Report the case where all signatures in a detached set are rejected
1451 differently than the case where there is an error handling the
1453 - When we realize that another process has modified our cached
1454 descriptors, print out a more useful error message rather than
1455 triggering an assertion. Fixes bug 885. Patch from Karsten.
1456 - Implement the 0x20 hack to better resist DNS poisoning: set the
1457 case on outgoing DNS requests randomly, and reject responses that do
1458 not match the case correctly. This logic can be disabled with the
1459 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
1460 of servers that do not reliably preserve case in replies. See
1461 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
1463 - Check DNS replies for more matching fields to better resist DNS
1465 - Never use OpenSSL compression: it wastes RAM and CPU trying to
1466 compress cells, which are basically all encrypted, compressed, or
1470 Changes in version 0.2.1.11-alpha - 2009-01-20
1471 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
1472 week it will take a long time to bootstrap again" bug. It also fixes
1473 an important security-related bug reported by Ilja van Sprundel. You
1474 should upgrade. (We'll send out more details about the bug once people
1475 have had some time to upgrade.)
1478 - Fix a heap-corruption bug that may be remotely triggerable on
1479 some platforms. Reported by Ilja van Sprundel.
1482 - Discard router descriptors as we load them if they are more than
1483 five days old. Otherwise if Tor is off for a long time and then
1484 starts with cached descriptors, it will try to use the onion
1485 keys in those obsolete descriptors when building circuits. Bugfix
1486 on 0.2.0.x. Fixes bug 887.
1489 - Try to make sure that the version of Libevent we're running with
1490 is binary-compatible with the one we built with. May address bug
1492 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
1493 for bug 905. Bugfix on 0.2.1.7-alpha.
1494 - Add a new --enable-local-appdata configuration switch to change
1495 the default location of the datadir on win32 from APPDATA to
1496 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
1497 entirely. Patch from coderman.
1500 - Make outbound DNS packets respect the OutboundBindAddress setting.
1501 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
1502 - When our circuit fails at the first hop (e.g. we get a destroy
1503 cell back), avoid using that OR connection anymore, and also
1504 tell all the one-hop directory requests waiting for it that they
1505 should fail. Bugfix on 0.2.1.3-alpha.
1506 - In the torify(1) manpage, mention that tsocks will leak your
1510 Changes in version 0.2.1.10-alpha - 2009-01-06
1511 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
1512 would make the bridge relay not so useful if it had DirPort set to 0,
1513 and one that could let an attacker learn a little bit of information
1514 about the bridge's users), and a bug that would cause your Tor relay
1515 to ignore a circuit create request it can't decrypt (rather than reply
1516 with an error). It also fixes a wide variety of other bugs.
1519 - If the cached networkstatus consensus is more than five days old,
1520 discard it rather than trying to use it. In theory it could
1521 be useful because it lists alternate directory mirrors, but in
1522 practice it just means we spend many minutes trying directory
1523 mirrors that are long gone from the network. Helps bug 887 a bit;
1525 - Bridge relays that had DirPort set to 0 would stop fetching
1526 descriptors shortly after startup, and then briefly resume
1527 after a new bandwidth test and/or after publishing a new bridge
1528 descriptor. Bridge users that try to bootstrap from them would
1529 get a recent networkstatus but would get descriptors from up to
1530 18 hours earlier, meaning most of the descriptors were obsolete
1531 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
1532 - Prevent bridge relays from serving their 'extrainfo' document
1533 to anybody who asks, now that extrainfo docs include potentially
1534 sensitive aggregated client geoip summaries. Bugfix on
1538 - New controller event "clients_seen" to report a geoip-based summary
1539 of which countries we've seen clients from recently. Now controllers
1540 like Vidalia can show bridge operators that they're actually making
1542 - Build correctly against versions of OpenSSL 0.9.8 or later built
1543 without support for deprecated functions.
1544 - Update to the "December 19 2008" ip-to-country file.
1546 o Minor bugfixes (on 0.2.0.x):
1547 - Authorities now vote for the Stable flag for any router whose
1548 weighted MTBF is at least 5 days, regardless of the mean MTBF.
1549 - Do not remove routers as too old if we do not have any consensus
1550 document. Bugfix on 0.2.0.7-alpha.
1551 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
1552 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
1553 - When an exit relay resolves a stream address to a local IP address,
1554 do not just keep retrying that same exit relay over and
1555 over. Instead, just close the stream. Addresses bug 872. Bugfix
1556 on 0.2.0.32. Patch from rovv.
1557 - If a hidden service sends us an END cell, do not consider
1558 retrying the connection; just close it. Patch from rovv.
1559 - When we made bridge authorities stop serving bridge descriptors over
1560 unencrypted links, we also broke DirPort reachability testing for
1561 bridges. So bridges with a non-zero DirPort were printing spurious
1562 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
1563 - When a relay gets a create cell it can't decrypt (e.g. because it's
1564 using the wrong onion key), we were dropping it and letting the
1565 client time out. Now actually answer with a destroy cell. Fixes
1566 bug 904. Bugfix on 0.0.2pre8.
1567 - Squeeze 2-5% out of client performance (according to oprofile) by
1568 improving the implementation of some policy-manipulation functions.
1570 o Minor bugfixes (on 0.2.1.x):
1571 - Make get_interface_address() function work properly again; stop
1572 guessing the wrong parts of our address as our address.
1573 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
1574 send on that circuit. Otherwise we might violate the proposal-110
1575 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
1577 - When we're sending non-EXTEND cells to the first hop in a circuit,
1578 for example to use an encrypted directory connection, we don't need
1579 to use RELAY_EARLY cells: the first hop knows what kind of cell
1580 it is, and nobody else can even see the cell type. Conserving
1581 RELAY_EARLY cells makes it easier to cannibalize circuits like
1583 - Stop logging nameserver addresses in reverse order.
1584 - If we are retrying a directory download slowly over and over, do
1585 not automatically give up after the 254th failure. Bugfix on
1587 - Resume reporting accurate "stream end" reasons to the local control
1588 port. They were lost in the changes for Proposal 148. Bugfix on
1591 o Deprecated and removed features:
1592 - The old "tor --version --version" command, which would print out
1593 the subversion "Id" of most of the source files, is now removed. It
1594 turned out to be less useful than we'd expected, and harder to
1597 o Code simplifications and refactoring:
1598 - Change our header file guard macros to be less likely to conflict
1599 with system headers. Adam Langley noticed that we were conflicting
1600 with log.h on Android.
1601 - Tool-assisted documentation cleanup. Nearly every function or
1602 static variable in Tor should have its own documentation now.
1605 Changes in version 0.2.1.9-alpha - 2008-12-25
1606 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
1608 o New directory authorities:
1609 - gabelmoo (the authority run by Karsten Loesing) now has a new
1613 - Never use a connection with a mismatched address to extend a
1614 circuit, unless that connection is canonical. A canonical
1615 connection is one whose address is authenticated by the router's
1616 identity key, either in a NETINFO cell or in a router descriptor.
1617 - Avoid a possible memory corruption bug when receiving hidden service
1618 descriptors. Bugfix on 0.2.1.6-alpha.
1621 - Fix a logic error that would automatically reject all but the first
1622 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
1623 part of bug 813/868. Bug spotted by coderman.
1624 - When a stream at an exit relay is in state "resolving" or
1625 "connecting" and it receives an "end" relay cell, the exit relay
1626 would silently ignore the end cell and not close the stream. If
1627 the client never closes the circuit, then the exit relay never
1628 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
1630 - When we can't initialize DNS because the network is down, do not
1631 automatically stop Tor from starting. Instead, retry failed
1632 dns_init() every 10 minutes, and change the exit policy to reject
1633 *:* until one succeeds. Fixes bug 691.
1636 - Give a better error message when an overzealous init script says
1637 "sudo -u username tor --user username". Makes Bug 882 easier for
1639 - When a directory authority gives us a new guess for our IP address,
1640 log which authority we used. Hopefully this will help us debug
1641 the recent complaints about bad IP address guesses.
1642 - Detect svn revision properly when we're using git-svn.
1643 - Try not to open more than one descriptor-downloading connection
1644 to an authority at once. This should reduce load on directory
1645 authorities. Fixes bug 366.
1646 - Add cross-certification to newly generated certificates, so that
1647 a signing key is enough information to look up a certificate.
1648 Partial implementation of proposal 157.
1649 - Start serving certificates by <identity digest, signing key digest>
1650 pairs. Partial implementation of proposal 157.
1651 - Clients now never report any stream end reason except 'MISC'.
1652 Implements proposal 148.
1653 - On platforms with a maximum syslog string length, truncate syslog
1654 messages to that length ourselves, rather than relying on the
1655 system to do it for us.
1656 - Optimize out calls to time(NULL) that occur for every IO operation,
1657 or for every cell. On systems where time() is a slow syscall,
1658 this fix will be slightly helpful.
1659 - Exit servers can now answer resolve requests for ip6.arpa addresses.
1660 - When we download a descriptor that we then immediately (as
1661 a directory authority) reject, do not retry downloading it right
1662 away. Should save some bandwidth on authorities. Fix for bug
1663 888. Patch by Sebastian Hahn.
1664 - When a download gets us zero good descriptors, do not notify
1665 Tor that new directory information has arrived.
1666 - Avoid some nasty corner cases in the logic for marking connections
1667 as too old or obsolete or noncanonical for circuits. Partial
1670 o Minor features (controller):
1671 - New CONSENSUS_ARRIVED event to note when a new consensus has
1672 been fetched and validated.
1673 - When we realize that another process has modified our cached
1674 descriptors file, print out a more useful error message rather
1675 than triggering an assertion. Fixes bug 885. Patch from Karsten.
1676 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
1677 controllers to prevent SIGHUP from reloading the
1678 configuration. Fixes bug 856.
1681 - Resume using the correct "REASON=" stream when telling the
1682 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
1683 - When a canonical connection appears later in our internal list
1684 than a noncanonical one for a given OR ID, always use the
1685 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
1687 - Clip the MaxCircuitDirtiness config option to a minimum of 10
1688 seconds. Warn the user if lower values are given in the
1689 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
1690 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
1691 user if lower values are given in the configuration. Bugfix on
1692 0.1.1.17-rc. Patch by Sebastian.
1693 - Fix a race condition when freeing keys shared between main thread
1694 and CPU workers that could result in a memory leak. Bugfix on
1695 0.1.0.1-rc. Fixes bug 889.
1697 o Minor bugfixes (hidden services):
1698 - Do not throw away existing introduction points on SIGHUP (bugfix on
1699 0.0.6pre1); also, do not stall hidden services because we're
1700 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
1701 by John Brooks. Patch by Karsten. Fixes bug 874.
1702 - Fix a memory leak when we decline to add a v2 rendezvous
1703 descriptor to the cache because we already had a v0 descriptor
1704 with the same ID. Bugfix on 0.2.0.18-alpha.
1706 o Deprecated and removed features:
1707 - RedirectExits has been removed. It was deprecated since
1709 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
1710 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
1711 - Cell pools are now always enabled; --disable-cell-pools is ignored.
1713 o Code simplifications and refactoring:
1714 - Rename the confusing or_is_obsolete field to the more appropriate
1715 is_bad_for_new_circs, and move it to or_connection_t where it
1717 - Move edge-only flags from connection_t to edge_connection_t: not
1718 only is this better coding, but on machines of plausible alignment,
1719 it should save 4-8 bytes per connection_t. "Every little bit helps."
1720 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
1721 for consistency; keep old option working for backward compatibility.
1722 - Simplify the code for finding connections to use for a circuit.
1725 Changes in version 0.2.1.8-alpha - 2008-12-08
1726 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
1727 builds better on unusual platforms like Solaris and old OS X, and
1728 fixes a variety of other issues.
1731 - New DirPortFrontPage option that takes an html file and publishes
1732 it as "/" on the DirPort. Now relay operators can provide a
1733 disclaimer without needing to set up a separate webserver. There's
1734 a sample disclaimer in contrib/tor-exit-notice.html.
1737 - When the client is choosing entry guards, now it selects at most
1738 one guard from a given relay family. Otherwise we could end up with
1739 all of our entry points into the network run by the same operator.
1740 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
1743 - Fix a DOS opportunity during the voting signature collection process
1744 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
1745 - Fix a possible segfault when establishing an exit connection. Bugfix
1749 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
1751 - Made Tor a little less aggressive about deleting expired
1752 certificates. Partial fix for bug 854.
1753 - Stop doing unaligned memory access that generated bus errors on
1754 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
1755 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
1756 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
1757 - Make USR2 log-level switch take effect immediately. Bugfix on
1759 - If one win32 nameserver fails to get added, continue adding the
1760 rest, and don't automatically fail.
1761 - Use fcntl() for locking when flock() is not available. Should fix
1762 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
1763 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
1764 could make gcc generate non-functional binary search code. Bugfix
1766 - Build correctly on platforms without socklen_t.
1767 - Avoid potential crash on internal error during signature collection.
1768 Fixes bug 864. Patch from rovv.
1769 - Do not use C's stdio library for writing to log files. This will
1770 improve logging performance by a minute amount, and will stop
1771 leaking fds when our disk is full. Fixes bug 861.
1772 - Stop erroneous use of O_APPEND in cases where we did not in fact
1773 want to re-seek to the end of a file before every last write().
1774 - Correct handling of possible malformed authority signing key
1775 certificates with internal signature types. Fixes bug 880. Bugfix
1777 - Fix a hard-to-trigger resource leak when logging credential status.
1781 - Directory mirrors no longer fetch the v1 directory or
1782 running-routers files. They are obsolete, and nobody asks for them
1783 anymore. This is the first step to making v1 authorities obsolete.
1785 o Minor features (controller):
1786 - Return circuit purposes in response to GETINFO circuit-status. Fixes
1790 Changes in version 0.2.0.32 - 2008-11-20
1791 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
1792 packages (and maybe other packages) noticed by Theo de Raadt, fixes
1793 a smaller security flaw that might allow an attacker to access local
1794 services, further improves hidden service performance, and fixes a
1795 variety of other issues.
1798 - The "User" and "Group" config options did not clear the
1799 supplementary group entries for the Tor process. The "User" option
1800 is now more robust, and we now set the groups to the specified
1801 user's primary group. The "Group" option is now ignored. For more
1802 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
1803 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
1804 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
1805 - The "ClientDNSRejectInternalAddresses" config option wasn't being
1806 consistently obeyed: if an exit relay refuses a stream because its
1807 exit policy doesn't allow it, we would remember what IP address
1808 the relay said the destination address resolves to, even if it's
1809 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
1812 - Fix a DOS opportunity during the voting signature collection process
1813 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
1815 o Major bugfixes (hidden services):
1816 - When fetching v0 and v2 rendezvous service descriptors in parallel,
1817 we were failing the whole hidden service request when the v0
1818 descriptor fetch fails, even if the v2 fetch is still pending and
1819 might succeed. Similarly, if the last v2 fetch fails, we were
1820 failing the whole hidden service request even if a v0 fetch is
1821 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
1822 - When extending a circuit to a hidden service directory to upload a
1823 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
1824 requests failed, because the router descriptor has not been
1825 downloaded yet. In these cases, do not attempt to upload the
1826 rendezvous descriptor, but wait until the router descriptor is
1827 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
1828 descriptor from a hidden service directory for which the router
1829 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
1833 - Fix several infrequent memory leaks spotted by Coverity.
1834 - When testing for libevent functions, set the LDFLAGS variable
1835 correctly. Found by Riastradh.
1836 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
1837 bootstrapping with tunneled directory connections. Bugfix on
1838 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
1839 - When asked to connect to A.B.exit:80, if we don't know the IP for A
1840 and we know that server B rejects most-but-not all connections to
1841 port 80, we would previously reject the connection. Now, we assume
1842 the user knows what they were asking for. Fixes bug 752. Bugfix
1843 on 0.0.9rc5. Diagnosed by BarkerJr.
1844 - If we overrun our per-second write limits a little, count this as
1845 having used up our write allocation for the second, and choke
1846 outgoing directory writes. Previously, we had only counted this when
1847 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
1848 Bugfix on 0.2.0.x (??).
1849 - Remove the old v2 directory authority 'lefkada' from the default
1850 list. It has been gone for many months.
1851 - Stop doing unaligned memory access that generated bus errors on
1852 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
1853 - Make USR2 log-level switch take effect immediately. Bugfix on
1856 o Minor bugfixes (controller):
1857 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
1858 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
1861 Changes in version 0.2.1.7-alpha - 2008-11-08
1862 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
1863 packages (and maybe other packages) noticed by Theo de Raadt, fixes
1864 a smaller security flaw that might allow an attacker to access local
1865 services, adds better defense against DNS poisoning attacks on exit
1866 relays, further improves hidden service performance, and fixes a
1867 variety of other issues.
1870 - The "ClientDNSRejectInternalAddresses" config option wasn't being
1871 consistently obeyed: if an exit relay refuses a stream because its
1872 exit policy doesn't allow it, we would remember what IP address
1873 the relay said the destination address resolves to, even if it's
1874 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
1875 - The "User" and "Group" config options did not clear the
1876 supplementary group entries for the Tor process. The "User" option
1877 is now more robust, and we now set the groups to the specified
1878 user's primary group. The "Group" option is now ignored. For more
1879 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
1880 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
1881 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
1882 - Do not use or believe expired v3 authority certificates. Patch
1883 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
1886 - Now NodeFamily and MyFamily config options allow spaces in
1887 identity fingerprints, so it's easier to paste them in.
1888 Suggested by Lucky Green.
1889 - Implement the 0x20 hack to better resist DNS poisoning: set the
1890 case on outgoing DNS requests randomly, and reject responses that do
1891 not match the case correctly. This logic can be disabled with the
1892 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
1893 of servers that do not reliably preserve case in replies. See
1894 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
1896 - Preserve case in replies to DNSPort requests in order to support
1897 the 0x20 hack for resisting DNS poisoning attacks.
1899 o Hidden service performance improvements:
1900 - When the client launches an introduction circuit, retry with a
1901 new circuit after 30 seconds rather than 60 seconds.
1902 - Launch a second client-side introduction circuit in parallel
1903 after a delay of 15 seconds (based on work by Christian Wilms).
1904 - Hidden services start out building five intro circuits rather
1905 than three, and when the first three finish they publish a service
1906 descriptor using those. Now we publish our service descriptor much
1907 faster after restart.
1910 - Minor fix in the warning messages when you're having problems
1911 bootstrapping; also, be more forgiving of bootstrap problems when
1912 we're still making incremental progress on a given bootstrap phase.
1913 - When we're choosing an exit node for a circuit, and we have
1914 no pending streams, choose a good general exit rather than one that
1915 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
1916 - Send a valid END cell back when a client tries to connect to a
1917 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
1918 840. Patch from rovv.
1919 - If a broken client asks a non-exit router to connect somewhere,
1920 do not even do the DNS lookup before rejecting the connection.
1921 Fixes another case of bug 619. Patch from rovv.
1922 - Fix another case of assuming, when a specific exit is requested,
1923 that we know more than the user about what hosts it allows.
1924 Fixes another case of bug 752. Patch from rovv.
1925 - Check which hops rendezvous stream cells are associated with to
1926 prevent possible guess-the-streamid injection attacks from
1927 intermediate hops. Fixes another case of bug 446. Based on patch
1929 - Avoid using a negative right-shift when comparing 32-bit
1930 addresses. Possible fix for bug 845 and bug 811.
1931 - Make the assert_circuit_ok() function work correctly on circuits that
1932 have already been marked for close.
1933 - Fix read-off-the-end-of-string error in unit tests when decoding
1934 introduction points.
1935 - Fix uninitialized size field for memory area allocation: may improve
1936 memory performance during directory parsing.
1937 - Treat duplicate certificate fetches as failures, so that we do
1938 not try to re-fetch an expired certificate over and over and over.
1939 - Do not say we're fetching a certificate when we'll in fact skip it
1940 because of a pending download.
1943 Changes in version 0.2.1.6-alpha - 2008-09-30
1944 Tor 0.2.1.6-alpha further improves performance and robustness of
1945 hidden services, starts work on supporting per-country relay selection,
1946 and fixes a variety of smaller issues.
1949 - Implement proposal 121: make it possible to build hidden services
1950 that only certain clients are allowed to connect to. This is
1951 enforced at several points, so that unauthorized clients are unable
1952 to send INTRODUCE cells to the service, or even (depending on the
1953 type of authentication) to learn introduction points. This feature
1954 raises the bar for certain kinds of active attacks against hidden
1955 services. Code by Karsten Loesing.
1956 - Relays now store and serve v2 hidden service descriptors by default,
1957 i.e., the new default value for HidServDirectoryV2 is 1. This is
1958 the last step in proposal 114, which aims to make hidden service
1959 lookups more reliable.
1960 - Start work to allow node restrictions to include country codes. The
1961 syntax to exclude nodes in a country with country code XX is
1962 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
1963 refinement to decide what config options should take priority if
1964 you ask to both use a particular node and exclude it.
1965 - Allow ExitNodes list to include IP ranges and country codes, just
1966 like the Exclude*Nodes lists. Patch from Robert Hogan.
1969 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
1970 Tor to fail to start if you had it configured to use a bridge
1971 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
1972 - When extending a circuit to a hidden service directory to upload a
1973 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
1974 requests failed, because the router descriptor had not been
1975 downloaded yet. In these cases, we now wait until the router
1976 descriptor is downloaded, and then retry. Likewise, clients
1977 now skip over a hidden service directory if they don't yet have
1978 its router descriptor, rather than futilely requesting it and
1979 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
1981 - When fetching v0 and v2 rendezvous service descriptors in parallel,
1982 we were failing the whole hidden service request when the v0
1983 descriptor fetch fails, even if the v2 fetch is still pending and
1984 might succeed. Similarly, if the last v2 fetch fails, we were
1985 failing the whole hidden service request even if a v0 fetch is
1986 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
1987 - DNS replies need to have names matching their requests, but
1988 these names should be in the questions section, not necessarily
1989 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
1992 - Update to the "September 1 2008" ip-to-country file.
1993 - Allow ports 465 and 587 in the default exit policy again. We had
1994 rejected them in 0.1.0.15, because back in 2005 they were commonly
1995 misconfigured and ended up as spam targets. We hear they are better
1996 locked down these days.
1997 - Use a lockfile to make sure that two Tor processes are not
1998 simultaneously running with the same datadir.
1999 - Serve the latest v3 networkstatus consensus via the control
2000 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
2001 - Better logging about stability/reliability calculations on directory
2003 - Drop the requirement to have an open dir port for storing and
2004 serving v2 hidden service descriptors.
2005 - Directory authorities now serve a /tor/dbg-stability.txt URL to
2006 help debug WFU and MTBF calculations.
2007 - Implement most of Proposal 152: allow specialized servers to permit
2008 single-hop circuits, and clients to use those servers to build
2009 single-hop circuits when using a specialized controller. Patch
2010 from Josh Albrecht. Resolves feature request 768.
2011 - Add a -p option to tor-resolve for specifying the SOCKS port: some
2012 people find host:port too confusing.
2013 - Make TrackHostExit mappings expire a while after their last use, not
2014 after their creation. Patch from Robert Hogan.
2015 - Provide circuit purposes along with circuit events to the controller.
2018 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
2020 - Fixed some memory leaks -- some quite frequent, some almost
2021 impossible to trigger -- based on results from Coverity.
2022 - When testing for libevent functions, set the LDFLAGS variable
2023 correctly. Found by Riastradh.
2024 - Fix an assertion bug in parsing policy-related options; possible fix
2026 - Catch and report a few more bootstrapping failure cases when Tor
2027 fails to establish a TCP connection. Cleanup on 0.2.1.x.
2028 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
2029 bootstrapping with tunneled directory connections. Bugfix on
2030 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
2031 - When asked to connect to A.B.exit:80, if we don't know the IP for A
2032 and we know that server B rejects most-but-not all connections to
2033 port 80, we would previously reject the connection. Now, we assume
2034 the user knows what they were asking for. Fixes bug 752. Bugfix
2035 on 0.0.9rc5. Diagnosed by BarkerJr.
2036 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
2037 service directories if they have no advertised dir port. Bugfix
2039 - If we overrun our per-second write limits a little, count this as
2040 having used up our write allocation for the second, and choke
2041 outgoing directory writes. Previously, we had only counted this when
2042 we had met our limits precisely. Fixes bug 824. Patch by rovv.
2043 Bugfix on 0.2.0.x (??).
2044 - Avoid a "0 divided by 0" calculation when calculating router uptime
2045 at directory authorities. Bugfix on 0.2.0.8-alpha.
2046 - Make DNS resolved controller events into "CLOSED", not
2047 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
2049 - Fix a bug where an unreachable relay would establish enough
2050 reachability testing circuits to do a bandwidth test -- if
2051 we already have a connection to the middle hop of the testing
2052 circuit, then it could establish the last hop by using the existing
2053 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
2054 circuits no longer use entry guards in 0.2.1.3-alpha.
2055 - If we have correct permissions on $datadir, we complain to stdout
2056 and fail to start. But dangerous permissions on
2057 $datadir/cached-status/ would cause us to open a log and complain
2058 there. Now complain to stdout and fail to start in both cases. Fixes
2059 bug 820, reported by seeess.
2060 - Remove the old v2 directory authority 'lefkada' from the default
2061 list. It has been gone for many months.
2063 o Code simplifications and refactoring:
2064 - Revise the connection_new functions so that a more typesafe variant
2065 exists. This will work better with Coverity, and let us find any
2066 actual mistakes we're making here.
2067 - Refactor unit testing logic so that dmalloc can be used sensibly
2068 with unit tests to check for memory leaks.
2069 - Move all hidden-service related fields from connection and circuit
2070 structure to substructures: this way they won't eat so much memory.
2073 Changes in version 0.2.0.31 - 2008-09-03
2074 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
2075 a big bug we're seeing where in rare cases traffic from one Tor stream
2076 gets mixed into another stream, and fixes a variety of smaller issues.
2079 - Make sure that two circuits can never exist on the same connection
2080 with the same circuit ID, even if one is marked for close. This
2081 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
2082 - Relays now reject risky extend cells: if the extend cell includes
2083 a digest of all zeroes, or asks to extend back to the relay that
2084 sent the extend cell, tear down the circuit. Ideas suggested
2086 - If not enough of our entry guards are available so we add a new
2087 one, we might use the new one even if it overlapped with the
2088 current circuit's exit relay (or its family). Anonymity bugfix
2089 pointed out by rovv.
2092 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
2093 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
2094 - Correctly detect the presence of the linux/netfilter_ipv4.h header
2095 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
2096 - Pick size of default geoip filename string correctly on windows.
2097 Fixes bug 806. Bugfix on 0.2.0.30.
2098 - Make the autoconf script accept the obsolete --with-ssl-dir
2099 option as an alias for the actually-working --with-openssl-dir
2100 option. Fix the help documentation to recommend --with-openssl-dir.
2101 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
2102 - When using the TransPort option on OpenBSD, and using the User
2103 option to change UID and drop privileges, make sure to open
2104 /dev/pf before dropping privileges. Fixes bug 782. Patch from
2105 Christopher Davis. Bugfix on 0.1.2.1-alpha.
2106 - Try to attach connections immediately upon receiving a RENDEZVOUS2
2107 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
2108 on the client side when connecting to a hidden service. Bugfix
2109 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
2110 - When closing an application-side connection because its circuit is
2111 getting torn down, generate the stream event correctly. Bugfix on
2112 0.1.2.x. Anonymous patch.
2115 Changes in version 0.2.1.5-alpha - 2008-08-31
2116 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
2117 in a lot of the infrastructure for adding authorization to hidden
2118 services, lays the groundwork for having clients read their load
2119 balancing information out of the networkstatus consensus rather than
2120 the individual router descriptors, addresses two potential anonymity
2121 issues, and fixes a variety of smaller issues.
2124 - Convert many internal address representations to optionally hold
2126 - Generate and accept IPv6 addresses in many protocol elements.
2127 - Make resolver code handle nameservers located at ipv6 addresses.
2128 - Begin implementation of proposal 121 ("Client authorization for
2129 hidden services"): configure hidden services with client
2130 authorization, publish descriptors for them, and configure
2131 authorization data for hidden services at clients. The next
2132 step is to actually access hidden services that perform client
2134 - More progress toward proposal 141: Network status consensus
2135 documents and votes now contain bandwidth information for each
2136 router and a summary of that router's exit policy. Eventually this
2137 will be used by clients so that they do not have to download every
2138 known descriptor before building circuits.
2140 o Major bugfixes (on 0.2.0.x and before):
2141 - When sending CREATED cells back for a given circuit, use a 64-bit
2142 connection ID to find the right connection, rather than an addr:port
2143 combination. Now that we can have multiple OR connections between
2144 the same ORs, it is no longer possible to use addr:port to uniquely
2145 identify a connection.
2146 - Relays now reject risky extend cells: if the extend cell includes
2147 a digest of all zeroes, or asks to extend back to the relay that
2148 sent the extend cell, tear down the circuit. Ideas suggested
2150 - If not enough of our entry guards are available so we add a new
2151 one, we might use the new one even if it overlapped with the
2152 current circuit's exit relay (or its family). Anonymity bugfix
2153 pointed out by rovv.
2156 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
2157 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
2158 - When using the TransPort option on OpenBSD, and using the User
2159 option to change UID and drop privileges, make sure to open /dev/pf
2160 before dropping privileges. Fixes bug 782. Patch from Christopher
2161 Davis. Bugfix on 0.1.2.1-alpha.
2162 - Correctly detect the presence of the linux/netfilter_ipv4.h header
2163 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
2164 - Add a missing safe_str() call for a debug log message.
2165 - Use 64 bits instead of 32 bits for connection identifiers used with
2166 the controller protocol, to greatly reduce risk of identifier reuse.
2167 - Make the autoconf script accept the obsolete --with-ssl-dir
2168 option as an alias for the actually-working --with-openssl-dir
2169 option. Fix the help documentation to recommend --with-openssl-dir.
2170 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
2173 - Rate-limit too-many-sockets messages: when they happen, they happen
2174 a lot. Resolves bug 748.
2175 - Resist DNS poisoning a little better by making sure that names in
2176 answer sections match.
2177 - Print the SOCKS5 error message string as well as the error code
2178 when a tor-resolve request fails. Patch from Jacob.
2181 Changes in version 0.2.1.4-alpha - 2008-08-04
2182 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
2185 - The address part of exit policies was not correctly written
2186 to router descriptors. This generated router descriptors that failed
2187 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
2189 - Tor triggered a false assert when extending a circuit to a relay
2190 but we already have a connection open to that relay. Noticed by
2191 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
2194 - Fix a hidden service logging bug: in some edge cases, the router
2195 descriptor of a previously picked introduction point becomes
2196 obsolete and we need to give up on it rather than continually
2197 complaining that it has become obsolete. Observed by xiando. Bugfix
2201 - Take out the TestVia config option, since it was a workaround for
2202 a bug that was fixed in Tor 0.1.1.21.
2205 Changes in version 0.2.1.3-alpha - 2008-08-03
2206 Tor 0.2.1.3-alpha implements most of the pieces to prevent
2207 infinite-length circuit attacks (see proposal 110); fixes a bug that
2208 might cause exit relays to corrupt streams they send back; allows
2209 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
2210 ExcludeExitNodes config options; and fixes a big pile of bugs.
2212 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
2213 - Send a bootstrap problem "warn" event on the first problem if the
2214 reason is NO_ROUTE (that is, our network is down).
2217 - Implement most of proposal 110: The first K cells to be sent
2218 along a circuit are marked as special "early" cells; only K "early"
2219 cells will be allowed. Once this code is universal, we can block
2220 certain kinds of DOS attack by requiring that EXTEND commands must
2221 be sent using an "early" cell.
2224 - Try to attach connections immediately upon receiving a RENDEZVOUS2
2225 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
2226 on the client side when connecting to a hidden service. Bugfix
2227 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
2228 - Ensure that two circuits can never exist on the same connection
2229 with the same circuit ID, even if one is marked for close. This
2230 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
2233 - When relays do their initial bandwidth measurement, don't limit
2234 to just our entry guards for the test circuits. Otherwise we tend
2235 to have multiple test circuits going through a single entry guard,
2236 which makes our bandwidth test less accurate. Fixes part of bug 654;
2237 patch contributed by Josh Albrecht.
2238 - Add an ExcludeExitNodes option so users can list a set of nodes
2239 that should be be excluded from the exit node position, but
2240 allowed elsewhere. Implements proposal 151.
2241 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
2242 ExcludeNodes and ExcludeExitNodes lists.
2243 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
2244 be more efficient. Formerly it was quadratic in the number of
2245 servers; now it should be linear. Fixes bug 509.
2246 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
2247 and n_conn_id_digest fields into a separate structure that's
2248 only needed when the circuit has not yet attached to an n_conn.
2251 - Change the contrib/tor.logrotate script so it makes the new
2252 logs as "_tor:_tor" rather than the default, which is generally
2253 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
2254 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
2255 warnings (occasionally), but it can also cause the compiler to
2256 eliminate error-checking code. Suggested by Peter Gutmann.
2257 - When a hidden service is giving up on an introduction point candidate
2258 that was not included in the last published rendezvous descriptor,
2259 don't reschedule publication of the next descriptor. Fixes bug 763.
2261 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
2262 HiddenServiceExcludeNodes as obsolete: they never worked properly,
2263 and nobody claims to be using them. Fixes bug 754. Bugfix on
2264 0.1.0.1-rc. Patch from Christian Wilms.
2265 - Fix a small alignment and memory-wasting bug on buffer chunks.
2268 o Minor bugfixes (controller):
2269 - When closing an application-side connection because its circuit
2270 is getting torn down, generate the stream event correctly.
2271 Bugfix on 0.1.2.x. Anonymous patch.
2274 - Remove all backward-compatibility code to support relays running
2275 versions of Tor so old that they no longer work at all on the
2279 Changes in version 0.2.0.30 - 2008-07-15
2281 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
2282 warnings (occasionally), but it can also cause the compiler to
2283 eliminate error-checking code. Suggested by Peter Gutmann.
2286 Changes in version 0.2.0.29-rc - 2008-07-08
2287 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
2288 hidden-service performance bugs, and fixes a bunch of smaller bugs.
2291 - If you have more than one bridge but don't know their keys,
2292 you would only launch a request for the descriptor of the first one
2293 on your list. (Tor considered launching requests for the others, but
2294 found that it already had a connection on the way for $0000...0000
2295 so it didn't open another.) Bugfix on 0.2.0.x.
2296 - If you have more than one bridge but don't know their keys, and the
2297 connection to one of the bridges failed, you would cancel all
2298 pending bridge connections. (After all, they all have the same
2299 digest.) Bugfix on 0.2.0.x.
2300 - When a hidden service was trying to establish an introduction point,
2301 and Tor had built circuits preemptively for such purposes, we
2302 were ignoring all the preemptive circuits and launching a new one
2303 instead. Bugfix on 0.2.0.14-alpha.
2304 - When a hidden service was trying to establish an introduction point,
2305 and Tor *did* manage to reuse one of the preemptively built
2306 circuits, it didn't correctly remember which one it used,
2307 so it asked for another one soon after, until there were no
2308 more preemptive circuits, at which point it launched one from
2309 scratch. Bugfix on 0.0.9.x.
2310 - Make directory servers include the X-Your-Address-Is: http header in
2311 their responses even for begin_dir conns. Now clients who only
2312 ever use begin_dir connections still have a way to learn their IP
2313 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
2316 - Fix a macro/CPP interaction that was confusing some compilers:
2317 some GCCs don't like #if/#endif pairs inside macro arguments.
2319 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
2320 Fixes bug 704; fix from Steven Murdoch.
2321 - When opening /dev/null in finish_daemonize(), do not pass the
2322 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
2323 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
2324 - Correctly detect transparent proxy support on Linux hosts that
2325 require in.h to be included before netfilter_ipv4.h. Patch
2327 - Disallow session resumption attempts during the renegotiation
2328 stage of the v2 handshake protocol. Clients should never be trying
2329 session resumption at this point, but apparently some did, in
2330 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
2331 found by Geoff Goodell.
2334 Changes in version 0.2.1.2-alpha - 2008-06-20
2335 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
2336 make it easier to set up your own private Tor network; fixes several
2337 big bugs with using more than one bridge relay; fixes a big bug with
2338 offering hidden services quickly after Tor starts; and uses a better
2339 API for reporting potential bootstrapping problems to the controller.
2342 - New TestingTorNetwork config option to allow adjustment of
2343 previously constant values that, while reasonable, could slow
2344 bootstrapping. Implements proposal 135. Patch from Karsten.
2347 - If you have more than one bridge but don't know their digests,
2348 you would only learn a request for the descriptor of the first one
2349 on your list. (Tor considered launching requests for the others, but
2350 found that it already had a connection on the way for $0000...0000
2351 so it didn't open another.) Bugfix on 0.2.0.x.
2352 - If you have more than one bridge but don't know their digests,
2353 and the connection to one of the bridges failed, you would cancel
2354 all pending bridge connections. (After all, they all have the
2355 same digest.) Bugfix on 0.2.0.x.
2356 - When establishing a hidden service, introduction points that
2357 originate from cannibalized circuits are completely ignored and not
2358 included in rendezvous service descriptors. This might be another
2359 reason for delay in making a hidden service available. Bugfix
2360 from long ago (0.0.9.x?)
2363 - Allow OpenSSL to use dynamic locks if it wants.
2364 - When building a consensus, do not include routers that are down.
2365 This will cut down 30% to 40% on consensus size. Implements
2367 - In directory authorities' approved-routers files, allow
2368 fingerprints with or without space.
2369 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
2370 controller can query our current bootstrap state in case it attaches
2371 partway through and wants to catch up.
2372 - Send an initial "Starting" bootstrap status event, so we have a
2373 state to start out in.
2376 - Asking for a conditional consensus at .../consensus/<fingerprints>
2377 would crash a dirserver if it did not already have a
2378 consensus. Bugfix on 0.2.1.1-alpha.
2379 - Clean up some macro/CPP interactions: some GCC versions don't like
2380 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
2383 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
2384 - Directory authorities shouldn't complain about bootstrapping
2385 problems just because they do a lot of reachability testing and
2386 some of the connection attempts fail.
2387 - Start sending "count" and "recommendation" key/value pairs in
2388 bootstrap problem status events, so the controller can hear about
2389 problems even before Tor decides they're worth reporting for sure.
2390 - If you're using bridges, generate "bootstrap problem" warnings
2391 as soon as you run out of working bridges, rather than waiting
2392 for ten failures -- which will never happen if you have less than
2394 - If we close our OR connection because there's been a circuit
2395 pending on it for too long, we were telling our bootstrap status
2396 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
2399 Changes in version 0.2.1.1-alpha - 2008-06-13
2400 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
2401 were making the Tor process bloat especially on Linux; makes our TLS
2402 handshake blend in better; sends "bootstrap phase" status events to
2403 the controller, so it can keep the user informed of progress (and
2404 problems) fetching directory information and establishing circuits;
2405 and adds a variety of smaller features.
2408 - More work on making our TLS handshake blend in: modify the list
2409 of ciphers advertised by OpenSSL in client mode to even more
2410 closely resemble a common web browser. We cheat a little so that
2411 we can advertise ciphers that the locally installed OpenSSL doesn't
2413 - Start sending "bootstrap phase" status events to the controller,
2414 so it can keep the user informed of progress fetching directory
2415 information and establishing circuits. Also inform the controller
2416 if we think we're stuck at a particular bootstrap phase. Implements
2418 - Resume using OpenSSL's RAND_poll() for better (and more portable)
2419 cross-platform entropy collection again. We used to use it, then
2420 stopped using it because of a bug that could crash systems that
2421 called RAND_poll when they had a lot of fds open. It looks like the
2422 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
2423 at startup, and to call RAND_poll() when we reseed later only if
2424 we have a non-buggy OpenSSL version.
2427 - When we choose to abandon a new entry guard because we think our
2428 older ones might be better, close any circuits pending on that
2429 new entry guard connection. This fix should make us recover much
2430 faster when our network is down and then comes back. Bugfix on
2431 0.1.2.8-beta; found by lodger.
2433 o Memory fixes and improvements:
2434 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
2435 to avoid unused RAM in buffer chunks and memory pools.
2436 - Speed up parsing and cut down on memory fragmentation by using
2437 stack-style allocations for parsing directory objects. Previously,
2438 this accounted for over 40% of allocations from within Tor's code
2439 on a typical directory cache.
2440 - Use a Bloom filter rather than a digest-based set to track which
2441 descriptors we need to keep around when we're cleaning out old
2442 router descriptors. This speeds up the computation significantly,
2443 and may reduce fragmentation.
2444 - Reduce the default smartlist size from 32 to 16; it turns out that
2445 most smartlists hold around 8-12 elements tops.
2446 - Make dumpstats() log the fullness and size of openssl-internal
2448 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
2449 patch to their OpenSSL, turn it on to save memory on servers. This
2450 patch will (with any luck) get included in a mainline distribution
2452 - Never use OpenSSL compression: it wastes RAM and CPU trying to
2453 compress cells, which are basically all encrypted, compressed,
2457 - Stop reloading the router list from disk for no reason when we
2458 run out of reachable directory mirrors. Once upon a time reloading
2459 it would set the 'is_running' flag back to 1 for them. It hasn't
2460 done that for a long time.
2461 - In very rare situations new hidden service descriptors were
2462 published earlier than 30 seconds after the last change to the
2463 service. (We currently think that a hidden service descriptor
2464 that's been stable for 30 seconds is worth publishing.)
2467 - Allow separate log levels to be configured for different logging
2468 domains. For example, this allows one to log all notices, warnings,
2469 or errors, plus all memory management messages of level debug or
2470 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
2471 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
2472 and stop using a warning that had become unfixably verbose under
2474 - New --hush command-line option similar to --quiet. While --quiet
2475 disables all logging to the console on startup, --hush limits the
2476 output to messages of warning and error severity.
2477 - Servers support a new URL scheme for consensus downloads that
2478 allows the client to specify which authorities are trusted.
2479 The server then only sends the consensus if the client will trust
2480 it. Otherwise a 404 error is sent back. Clients use this
2481 new scheme when the server supports it (meaning it's running
2482 0.2.1.1-alpha or later). Implements proposal 134.
2483 - New configure/torrc options (--enable-geoip-stats,
2484 DirRecordUsageByCountry) to record how many IPs we've served
2485 directory info to in each country code, how many status documents
2486 total we've sent to each country code, and what share of the total
2487 directory requests we should expect to see.
2488 - Use the TLS1 hostname extension to more closely resemble browser
2490 - Lots of new unit tests.
2491 - Add a macro to implement the common pattern of iterating through
2492 two parallel lists in lockstep.
2495 Changes in version 0.2.0.28-rc - 2008-06-13
2496 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
2497 performance bug, and fixes a bunch of smaller bugs.
2500 - Fix a bug where, when we were choosing the 'end stream reason' to
2501 put in our relay end cell that we send to the exit relay, Tor
2502 clients on Windows were sometimes sending the wrong 'reason'. The
2503 anonymity problem is that exit relays may be able to guess whether
2504 the client is running Windows, thus helping partition the anonymity
2505 set. Down the road we should stop sending reasons to exit relays,
2506 or otherwise prevent future versions of this bug.
2509 - While setting up a hidden service, some valid introduction circuits
2510 were overlooked and abandoned. This might be the reason for
2511 the long delay in making a hidden service available. Bugfix on
2515 - Update to the "June 9 2008" ip-to-country file.
2516 - Run 'make test' as part of 'make dist', so we stop releasing so
2517 many development snapshots that fail their unit tests.
2520 - When we're checking if we have enough dir info for each relay
2521 to begin establishing circuits, make sure that we actually have
2522 the descriptor listed in the consensus, not just any descriptor.
2524 - Bridge relays no longer print "xx=0" in their extrainfo document
2525 for every single country code in the geoip db. Bugfix on
2527 - Only warn when we fail to load the geoip file if we were planning to
2528 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
2529 - If we change our MaxAdvertisedBandwidth and then reload torrc,
2530 Tor won't realize it should publish a new relay descriptor. Fixes
2531 bug 688, reported by mfr. Bugfix on 0.1.2.x.
2532 - When we haven't had any application requests lately, don't bother
2533 logging that we have expired a bunch of descriptors. Bugfix
2535 - Make relay cells written on a connection count as non-padding when
2536 tracking how long a connection has been in use. Bugfix on
2537 0.2.0.1-alpha. Spotted by lodger.
2538 - Fix unit tests in 0.2.0.27-rc.
2539 - Fix compile on Windows.
2542 Changes in version 0.2.0.27-rc - 2008-06-03
2543 Tor 0.2.0.27-rc adds a few features we left out of the earlier
2544 release candidates. In particular, we now include an IP-to-country
2545 GeoIP database, so controllers can easily look up what country a
2546 given relay is in, and so bridge relays can give us some sanitized
2547 summaries about which countries are making use of bridges. (See proposal
2548 126-geoip-fetching.txt for details.)
2551 - Include an IP-to-country GeoIP file in the tarball, so bridge
2552 relays can report sanitized summaries of the usage they're seeing.
2555 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
2556 Robert Hogan. Fixes the first part of bug 681.
2557 - Make bridge authorities never serve extrainfo docs.
2558 - Add support to detect Libevent versions in the 1.4.x series
2560 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
2561 - Include a new contrib/tor-exit-notice.html file that exit relay
2562 operators can put on their website to help reduce abuse queries.
2565 - When tunneling an encrypted directory connection, and its first
2566 circuit fails, do not leave it unattached and ask the controller
2567 to deal. Fixes the second part of bug 681.
2568 - Make bridge authorities correctly expire old extrainfo documents
2572 Changes in version 0.2.0.26-rc - 2008-05-13
2573 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
2574 in Debian's OpenSSL packages. All users running any 0.2.0.x version
2575 should upgrade, whether they're running Debian or not.
2577 o Major security fixes:
2578 - Use new V3 directory authority keys on the tor26, gabelmoo, and
2579 moria1 V3 directory authorities. The old keys were generated with
2580 a vulnerable version of Debian's OpenSSL package, and must be
2581 considered compromised. Other authorities' keys were not generated
2582 with an affected version of OpenSSL.
2585 - List authority signatures as "unrecognized" based on DirServer
2586 lines, not on cert cache. Bugfix on 0.2.0.x.
2589 - Add a new V3AuthUseLegacyKey option to make it easier for
2590 authorities to change their identity keys if they have to.
2593 Changes in version 0.2.0.25-rc - 2008-04-23
2594 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
2597 - Remember to initialize threading before initializing logging.
2598 Otherwise, many BSD-family implementations will crash hard on
2599 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
2602 - Authorities correctly free policies on bad servers on
2603 exit. Fixes bug 672. Bugfix on 0.2.0.x.
2606 Changes in version 0.2.0.24-rc - 2008-04-22
2607 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
2608 v3 directory authority, makes relays with dynamic IP addresses and no
2609 DirPort notice more quickly when their IP address changes, fixes a few
2610 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
2612 o New directory authorities:
2613 - Take lefkada out of the list of v3 directory authorities, since
2614 it has been down for months.
2615 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
2619 - Detect address changes more quickly on non-directory mirror
2620 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
2622 o Minor features (security):
2623 - Reject requests for reverse-dns lookup of names that are in
2624 a private address space. Patch from lodger.
2625 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
2628 o Minor bugfixes (crashes):
2629 - Avoid a rare assert that can trigger when Tor doesn't have much
2630 directory information yet and it tries to fetch a v2 hidden
2631 service descriptor. Fixes bug 651, reported by nwf.
2632 - Initialize log mutex before initializing dmalloc. Otherwise,
2633 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
2634 - Use recursive pthread mutexes in order to avoid deadlock when
2635 logging debug-level messages to a controller. Bug spotted by nwf,
2636 bugfix on 0.2.0.16-alpha.
2638 o Minor bugfixes (resource management):
2639 - Keep address policies from leaking memory: start their refcount
2640 at 1, not 2. Bugfix on 0.2.0.16-alpha.
2641 - Free authority certificates on exit, so they don't look like memory
2642 leaks. Bugfix on 0.2.0.19-alpha.
2643 - Free static hashtables for policy maps and for TLS connections on
2644 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
2645 - Avoid allocating extra space when computing consensuses on 64-bit
2646 platforms. Bug spotted by aakova.
2648 o Minor bugfixes (misc):
2649 - Do not read the configuration file when we've only been told to
2650 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
2651 based on patch from Sebastian Hahn.
2652 - Exit relays that are used as a client can now reach themselves
2653 using the .exit notation, rather than just launching an infinite
2654 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
2655 - When attempting to open a logfile fails, tell us why.
2656 - Fix a dumb bug that was preventing us from knowing that we should
2657 preemptively build circuits to handle expected directory requests.
2658 Fixes bug 660. Bugfix on 0.1.2.x.
2659 - Warn less verbosely about clock skew from netinfo cells from
2660 untrusted sources. Fixes bug 663.
2661 - Make controller stream events for DNS requests more consistent,
2662 by adding "new stream" events for DNS requests, and removing
2663 spurious "stream closed" events" for cached reverse resolves.
2664 Patch from mwenge. Fixes bug 646.
2665 - Correctly notify one-hop connections when a circuit build has
2666 failed. Possible fix for bug 669. Found by lodger.
2669 Changes in version 0.2.0.23-rc - 2008-03-24
2670 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
2671 makes bootstrapping faster if the first directory mirror you contact
2672 is down. The bundles also include the new Vidalia 0.1.2 release.
2675 - When a tunneled directory request is made to a directory server
2676 that's down, notice after 30 seconds rather than 120 seconds. Also,
2677 fail any begindir streams that are pending on it, so they can
2678 retry elsewhere. This was causing multi-minute delays on bootstrap.
2681 Changes in version 0.2.0.22-rc - 2008-03-18
2682 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
2683 enables encrypted directory connections by default for non-relays, fixes
2684 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
2685 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
2688 - Enable encrypted directory connections by default for non-relays,
2689 so censor tools that block Tor directory connections based on their
2690 plaintext patterns will no longer work. This means Tor works in
2691 certain censored countries by default again.
2694 - Make sure servers always request certificates from clients during
2695 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
2696 - Do not enter a CPU-eating loop when a connection is closed in
2697 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
2698 diagnosed by lodger; bugfix on 0.2.0.20-rc.
2699 - Fix assertion failure that could occur when a blocked circuit
2700 became unblocked, and it had pending client DNS requests. Bugfix
2701 on 0.2.0.1-alpha. Fixes bug 632.
2703 o Minor bugfixes (on 0.1.2.x):
2704 - Generate "STATUS_SERVER" events rather than misspelled
2705 "STATUS_SEVER" events. Caught by mwenge.
2706 - When counting the number of bytes written on a TLS connection,
2707 look at the BIO actually used for writing to the network, not
2708 at the BIO used (sometimes) to buffer data for the network.
2709 Looking at different BIOs could result in write counts on the
2710 order of ULONG_MAX. Fixes bug 614.
2711 - On Windows, correctly detect errors when listing the contents of
2712 a directory. Fix from lodger.
2714 o Minor bugfixes (on 0.2.0.x):
2715 - Downgrade "sslv3 alert handshake failure" message to INFO.
2716 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
2717 left BandwidthRate and BandwidthBurst at the default, we would be
2718 silently limited by those defaults. Now raise them to match the
2719 RelayBandwidth* values.
2720 - Fix the SVK version detection logic to work correctly on a branch.
2721 - Make --enable-openbsd-malloc work correctly on Linux with alpha
2722 CPUs. Fixes bug 625.
2723 - Logging functions now check that the passed severity is sane.
2724 - Use proper log levels in the testsuite call of
2725 get_interface_address6().
2726 - When using a nonstandard malloc, do not use the platform values for
2727 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
2728 - Make the openbsd malloc code use 8k pages on alpha CPUs and
2730 - Detect mismatched page sizes when using --enable-openbsd-malloc.
2731 - Avoid double-marked-for-close warning when certain kinds of invalid
2732 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
2733 for bug 617. Bugfix on 0.2.0.1-alpha.
2734 - Make sure that the "NULL-means-reject *:*" convention is followed by
2735 all the policy manipulation functions, avoiding some possible crash
2736 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
2737 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
2738 actually works, and doesn't warn about every single reverse lookup.
2739 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
2742 - Only log guard node status when guard node status has changed.
2743 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
2744 make "INFO" 75% less verbose.
2747 Changes in version 0.2.0.21-rc - 2008-03-02
2748 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
2749 makes Tor work well with Vidalia again, fixes a rare assert bug,
2750 and fixes a pair of more minor bugs. The bundles also include Vidalia
2751 0.1.0 and Torbutton 1.1.16.
2754 - The control port should declare that it requires password auth
2755 when HashedControlSessionPassword is set too. Patch from Matt Edman;
2756 bugfix on 0.2.0.20-rc. Fixes bug 615.
2757 - Downgrade assert in connection_buckets_decrement() to a log message.
2758 This may help us solve bug 614, and in any case will make its
2759 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
2760 - We were sometimes miscounting the number of bytes read from the
2761 network, causing our rate limiting to not be followed exactly.
2762 Bugfix on 0.2.0.16-alpha. Reported by lodger.
2765 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
2766 OpenSSL versions should have been working fine. Diagnosis and patch
2767 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
2768 Bugfix on 0.2.0.20-rc.
2771 Changes in version 0.2.0.20-rc - 2008-02-24
2772 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
2773 makes more progress towards normalizing Tor's TLS handshake, makes
2774 hidden services work better again, helps relays bootstrap if they don't
2775 know their IP address, adds optional support for linking in openbsd's
2776 allocator or tcmalloc, allows really fast relays to scale past 15000
2777 sockets, and fixes a bunch of minor bugs reported by Veracode.
2780 - Enable the revised TLS handshake based on the one designed by
2781 Steven Murdoch in proposal 124, as revised in proposal 130. It
2782 includes version negotiation for OR connections as described in
2783 proposal 105. The new handshake is meant to be harder for censors
2784 to fingerprint, and it adds the ability to detect certain kinds of
2785 man-in-the-middle traffic analysis attacks. The version negotiation
2786 feature will allow us to improve Tor's link protocol more safely
2788 - Choose which bridge to use proportional to its advertised bandwidth,
2789 rather than uniformly at random. This should speed up Tor for
2790 bridge users. Also do this for people who set StrictEntryNodes.
2791 - When a TrackHostExits-chosen exit fails too many times in a row,
2792 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
2795 - Resolved problems with (re-)fetching hidden service descriptors.
2796 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
2798 - If we only ever used Tor for hidden service lookups or posts, we
2799 would stop building circuits and start refusing connections after
2800 24 hours, since we falsely believed that Tor was dormant. Reported
2801 by nwf; bugfix on 0.1.2.x.
2802 - Servers that don't know their own IP address should go to the
2803 authorities for their first directory fetch, even if their DirPort
2804 is off or if they don't know they're reachable yet. This will help
2805 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
2806 - When counting the number of open sockets, count not only the number
2807 of sockets we have received from the socket() call, but also
2808 the number we've gotten from accept() and socketpair(). This bug
2809 made us fail to count all sockets that we were using for incoming
2810 connections. Bugfix on 0.2.0.x.
2811 - Fix code used to find strings within buffers, when those strings
2812 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
2813 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
2814 - Add a new __HashedControlSessionPassword option for controllers
2815 to use for one-off session password hashes that shouldn't get
2816 saved to disk by SAVECONF --- Vidalia users were accumulating a
2817 pile of HashedControlPassword lines in their torrc files, one for
2818 each time they had restarted Tor and then clicked Save. Make Tor
2819 automatically convert "HashedControlPassword" to this new option but
2820 only when it's given on the command line. Partial fix for bug 586.
2822 o Minor features (performance):
2823 - Tune parameters for cell pool allocation to minimize amount of
2825 - Add OpenBSD malloc code from phk as an optional malloc
2826 replacement on Linux: some glibc libraries do very poorly
2827 with Tor's memory allocation patterns. Pass
2828 --enable-openbsd-malloc to get the replacement malloc code.
2829 - Add a --with-tcmalloc option to the configure script to link
2830 against tcmalloc (if present). Does not yet search for
2831 non-system include paths.
2832 - Stop imposing an arbitrary maximum on the number of file descriptors
2833 used for busy servers. Bug reported by Olaf Selke; patch from
2836 o Minor features (other):
2837 - When SafeLogging is disabled, log addresses along with all TLS
2839 - When building with --enable-gcc-warnings, check for whether Apple's
2840 warning "-Wshorten-64-to-32" is available.
2841 - Add a --passphrase-fd argument to the tor-gencert command for
2844 o Minor bugfixes (memory leaks and code problems):
2845 - We were leaking a file descriptor if Tor started with a zero-length
2846 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
2847 - Detect size overflow in zlib code. Reported by Justin Ferguson and
2849 - We were comparing the raw BridgePassword entry with a base64'ed
2850 version of it, when handling a "/tor/networkstatus-bridges"
2851 directory request. Now compare correctly. Noticed by Veracode.
2852 - Recover from bad tracked-since value in MTBF-history file.
2854 - Alter the code that tries to recover from unhandled write
2855 errors, to not try to flush onto a socket that's given us
2856 unhandled errors. Bugfix on 0.1.2.x.
2857 - Make Unix controlsockets work correctly on OpenBSD. Patch from
2858 tup. Bugfix on 0.2.0.3-alpha.
2860 o Minor bugfixes (other):
2861 - If we have an extra-info document for our server, always make
2862 it available on the control port, even if we haven't gotten
2863 a copy of it from an authority yet. Patch from mwenge.
2864 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
2865 - Directory mirrors no longer include a guess at the client's IP
2866 address if the connection appears to be coming from the same /24
2867 network; it was producing too many wrong guesses.
2868 - Make the new hidden service code respect the SafeLogging setting.
2869 Bugfix on 0.2.0.x. Patch from Karsten.
2870 - When starting as an authority, do not overwrite all certificates
2871 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
2872 - If we're trying to flush the last bytes on a connection (for
2873 example, when answering a directory request), reset the
2874 time-to-give-up timeout every time we manage to write something
2875 on the socket. Bugfix on 0.1.2.x.
2876 - Change the behavior of "getinfo status/good-server-descriptor"
2877 so it doesn't return failure when any authority disappears.
2878 - Even though the man page said that "TrackHostExits ." should
2879 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
2880 - Report TLS "zero return" case as a "clean close" and "IO error"
2881 as a "close". Stop calling closes "unexpected closes": existing
2882 Tors don't use SSL_close(), so having a connection close without
2883 the TLS shutdown handshake is hardly unexpected.
2884 - Send NAMESERVER_STATUS messages for a single failed nameserver
2887 o Code simplifications and refactoring:
2888 - Remove the tor_strpartition function: its logic was confused,
2889 and it was only used for one thing that could be implemented far
2893 Changes in version 0.2.0.19-alpha - 2008-02-09
2894 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
2895 handshake, makes path selection for relays more secure and IP address
2896 guessing more robust, and generally fixes a lot of bugs in preparation
2897 for calling the 0.2.0 branch stable.
2900 - Do not include recognizeable strings in the commonname part of
2901 Tor's x509 certificates.
2904 - If we're a relay, avoid picking ourselves as an introduction point,
2905 a rendezvous point, or as the final hop for internal circuits. Bug
2906 reported by taranis and lodger. Bugfix on 0.1.2.x.
2907 - Patch from "Andrew S. Lists" to catch when we contact a directory
2908 mirror at IP address X and he says we look like we're coming from
2909 IP address X. Bugfix on 0.1.2.x.
2911 o Minor features (security):
2912 - Be more paranoid about overwriting sensitive memory on free(),
2913 as a defensive programming tactic to ensure forward secrecy.
2915 o Minor features (directory authority):
2916 - Actually validate the options passed to AuthDirReject,
2917 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
2918 - Reject router descriptors with out-of-range bandwidthcapacity or
2919 bandwidthburst values.
2921 o Minor features (controller):
2922 - Reject controller commands over 1MB in length. This keeps rogue
2923 processes from running us out of memory.
2925 o Minor features (misc):
2926 - Give more descriptive well-formedness errors for out-of-range
2927 hidden service descriptor/protocol versions.
2928 - Make memory debugging information describe more about history
2929 of cell allocation, so we can help reduce our memory use.
2931 o Deprecated features (controller):
2932 - The status/version/num-versioning and status/version/num-concurring
2933 GETINFO options are no longer useful in the v3 directory protocol:
2934 treat them as deprecated, and warn when they're used.
2937 - When our consensus networkstatus has been expired for a while, stop
2938 being willing to build circuits using it. Fixes bug 401. Bugfix
2940 - Directory caches now fetch certificates from all authorities
2941 listed in a networkstatus consensus, even when they do not
2942 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
2943 - When connecting to a bridge without specifying its key, insert
2944 the connection into the identity-to-connection map as soon as
2945 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
2946 - Detect versions of OS X where malloc_good_size() is present in the
2947 library but never actually declared. Resolves bug 587. Bugfix
2949 - Stop incorrectly truncating zlib responses to directory authority
2950 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
2951 - Stop recommending that every server operator send mail to tor-ops.
2952 Resolves bug 597. Bugfix on 0.1.2.x.
2953 - Don't trigger an assert if we start a directory authority with a
2954 private IP address (like 127.0.0.1).
2955 - Avoid possible failures when generating a directory with routers
2956 with over-long versions strings, or too many flags set. Bugfix
2958 - If an attempt to launch a DNS resolve request over the control
2959 port fails because we have overrun the limit on the number of
2960 connections, tell the controller that the request has failed.
2961 - Avoid using too little bandwidth when our clock skips a few
2962 seconds. Bugfix on 0.1.2.x.
2963 - Fix shell error when warning about missing packages in configure
2964 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
2965 - Do not become confused when receiving a spurious VERSIONS-like
2966 cell from a confused v1 client. Bugfix on 0.2.0.x.
2967 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
2968 introduction points for a hidden service have failed. Patch from
2969 Karsten Loesing. Bugfix on 0.2.0.x.
2971 o Code simplifications and refactoring:
2972 - Remove some needless generality from cpuworker code, for improved
2974 - Stop overloading the circuit_t.onionskin field for both "onionskin
2975 from a CREATE cell that we are waiting for a cpuworker to be
2976 assigned" and "onionskin from an EXTEND cell that we are going to
2977 send to an OR as soon as we are connected". Might help with bug 600.
2978 - Add an in-place version of aes_crypt() so that we can avoid doing a
2979 needless memcpy() call on each cell payload.
2982 Changes in version 0.2.0.18-alpha - 2008-01-25
2983 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
2984 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
2985 that can warn or reject connections to ports generally associated with
2986 vulnerable-plaintext protocols.
2988 o New directory authorities:
2989 - Set up dannenberg (run by CCC) as the sixth v3 directory
2993 - Fix a major memory leak when attempting to use the v2 TLS
2994 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
2995 - We accidentally enabled the under-development v2 TLS handshake
2996 code, which was causing log entries like "TLS error while
2997 renegotiating handshake". Disable it again. Resolves bug 590.
2998 - We were computing the wrong Content-Length: header for directory
2999 responses that need to be compressed on the fly, causing clients
3000 asking for those items to always fail. Bugfix on 0.2.0.x; partially
3004 - Avoid going directly to the directory authorities even if you're a
3005 relay, if you haven't found yourself reachable yet or if you've
3006 decided not to advertise your dirport yet. Addresses bug 556.
3007 - If we've gone 12 hours since our last bandwidth check, and we
3008 estimate we have less than 50KB bandwidth capacity but we could
3009 handle more, do another bandwidth test.
3010 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
3011 Tor can warn and/or refuse connections to ports commonly used with
3012 vulnerable-plaintext protocols. Currently we warn on ports 23,
3013 109, 110, and 143, but we don't reject any.
3016 - When we setconf ClientOnly to 1, close any current OR and Dir
3017 listeners. Reported by mwenge.
3018 - When we get a consensus that's been signed by more people than
3019 we expect, don't log about it; it's not a big deal. Reported
3023 - Don't answer "/tor/networkstatus-bridges" directory requests if
3024 the request isn't encrypted.
3025 - Make "ClientOnly 1" config option disable directory ports too.
3026 - Patches from Karsten Loesing to make v2 hidden services more
3027 robust: work even when there aren't enough HSDir relays available;
3028 retry when a v2 rend desc fetch fails; but don't retry if we
3029 already have a usable v0 rend desc.
3032 Changes in version 0.2.0.17-alpha - 2008-01-17
3033 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
3036 - Make the tor-gencert man page get included correctly in the tarball.
3039 Changes in version 0.2.0.16-alpha - 2008-01-17
3040 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
3041 Loesing, and generally cleans up a lot of features and minor bugs.
3043 o New directory authorities:
3044 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
3047 o Major performance improvements:
3048 - Switch our old ring buffer implementation for one more like that
3049 used by free Unix kernels. The wasted space in a buffer with 1mb
3050 of data will now be more like 8k than 1mb. The new implementation
3051 also avoids realloc();realloc(); patterns that can contribute to
3052 memory fragmentation.
3055 - Configuration files now accept C-style strings as values. This
3056 helps encode characters not allowed in the current configuration
3057 file format, such as newline or #. Addresses bug 557.
3058 - Although we fixed bug 539 (where servers would send HTTP status 503
3059 responses _and_ send a body too), there are still servers out
3060 there that haven't upgraded. Therefore, make clients parse such
3061 bodies when they receive them.
3062 - When we're not serving v2 directory information, there is no reason
3063 to actually keep any around. Remove the obsolete files and directory
3064 on startup if they are very old and we aren't going to serve them.
3066 o Minor performance improvements:
3067 - Reference-count and share copies of address policy entries; only 5%
3068 of them were actually distinct.
3069 - Never walk through the list of logs if we know that no log is
3070 interested in a given message.
3073 - When an authority has not signed a consensus, do not try to
3074 download a nonexistent "certificate with key 00000000". Bugfix
3075 on 0.2.0.x. Fixes bug 569.
3076 - Fix a rare assert error when we're closing one of our threads:
3077 use a mutex to protect the list of logs, so we never write to the
3078 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
3079 bug 575, which is kind of the revenge of bug 222.
3080 - Patch from Karsten Loesing to complain less at both the client
3081 and the relay when a relay used to have the HSDir flag but doesn't
3082 anymore, and we try to upload a hidden service descriptor.
3083 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
3085 - Do not try to download missing certificates until we have tried
3086 to check our fallback consensus. Fixes bug 583.
3087 - Make bridges round reported GeoIP stats info up to the nearest
3088 estimate, not down. Now we can distinguish between "0 people from
3089 this country" and "1 person from this country".
3090 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
3091 - Avoid possible segfault if key generation fails in
3092 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
3093 - Avoid segfault in the case where a badly behaved v2 versioning
3094 directory sends a signed networkstatus with missing client-versions.
3096 - Avoid segfaults on certain complex invocations of
3097 router_get_by_hexdigest(). Bugfix on 0.1.2.
3098 - Correct bad index on array access in parse_http_time(). Bugfix
3100 - Fix possible bug in vote generation when server versions are present
3101 but client versions are not.
3102 - Fix rare bug on REDIRECTSTREAM control command when called with no
3103 port set: it could erroneously report an error when none had
3105 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
3106 compressing large objects and find ourselves with more than 4k
3107 left over. Bugfix on 0.2.0.
3108 - Fix a small memory leak when setting up a hidden service.
3109 - Fix a few memory leaks that could in theory happen under bizarre
3111 - Fix an assert if we post a general-purpose descriptor via the
3112 control port but that descriptor isn't mentioned in our current
3113 network consensus. Bug reported by Jon McLachlan; bugfix on
3116 o Minor features (controller):
3117 - Get NS events working again. Patch from tup.
3118 - The GETCONF command now escapes and quotes configuration values
3119 that don't otherwise fit into the torrc file.
3120 - The SETCONF command now handles quoted values correctly.
3122 o Minor features (directory authorities):
3123 - New configuration options to override default maximum number of
3124 servers allowed on a single IP address. This is important for
3125 running a test network on a single host.
3126 - Actually implement the -s option to tor-gencert.
3127 - Add a manual page for tor-gencert.
3129 o Minor features (bridges):
3130 - Bridge authorities no longer serve bridge descriptors over
3131 unencrypted connections.
3133 o Minor features (other):
3134 - Add hidden services and DNSPorts to the list of things that make
3135 Tor accept that it has running ports. Change starting Tor with no
3136 ports from a fatal error to a warning; we might change it back if
3137 this turns out to confuse anybody. Fixes bug 579.
3140 Changes in version 0.1.2.19 - 2008-01-17
3141 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
3142 exit policy a little bit more conservative so it's safer to run an
3143 exit relay on a home system, and fixes a variety of smaller issues.
3146 - Exit policies now reject connections that are addressed to a
3147 relay's public (external) IP address too, unless
3148 ExitPolicyRejectPrivate is turned off. We do this because too
3149 many relays are running nearby to services that trust them based
3153 - When the clock jumps forward a lot, do not allow the bandwidth
3154 buckets to become negative. Fixes bug 544.
3155 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
3156 on every successful resolve. Reported by Mike Perry.
3157 - Purge old entries from the "rephist" database and the hidden
3158 service descriptor database even when DirPort is zero.
3159 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
3160 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
3161 crashing or mis-answering these requests.
3162 - When we decide to send a 503 response to a request for servers, do
3163 not then also send the server descriptors: this defeats the whole
3164 purpose. Fixes bug 539.
3167 - Changing the ExitPolicyRejectPrivate setting should cause us to
3168 rebuild our server descriptor.
3169 - Fix handling of hex nicknames when answering controller requests for
3170 networkstatus by name, or when deciding whether to warn about
3171 unknown routers in a config option. (Patch from mwenge.)
3172 - Fix a couple of hard-to-trigger autoconf problems that could result
3173 in really weird results on platforms whose sys/types.h files define
3174 nonstandard integer types.
3175 - Don't try to create the datadir when running --verify-config or
3176 --hash-password. Resolves bug 540.
3177 - If we were having problems getting a particular descriptor from the
3178 directory caches, and then we learned about a new descriptor for
3179 that router, we weren't resetting our failure count. Reported
3181 - Although we fixed bug 539 (where servers would send HTTP status 503
3182 responses _and_ send a body too), there are still servers out there
3183 that haven't upgraded. Therefore, make clients parse such bodies
3184 when they receive them.
3185 - Run correctly on systems where rlim_t is larger than unsigned long.
3186 This includes some 64-bit systems.
3187 - Run correctly on platforms (like some versions of OS X 10.5) where
3188 the real limit for number of open files is OPEN_FILES, not rlim_max
3189 from getrlimit(RLIMIT_NOFILES).
3190 - Avoid a spurious free on base64 failure.
3191 - Avoid segfaults on certain complex invocations of
3192 router_get_by_hexdigest().
3193 - Fix rare bug on REDIRECTSTREAM control command when called with no
3194 port set: it could erroneously report an error when none had
3198 Changes in version 0.2.0.15-alpha - 2007-12-25
3199 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
3200 features added in 0.2.0.13-alpha.
3203 - Fix several remotely triggerable asserts based on DirPort requests
3204 for a v2 or v3 networkstatus object before we were prepared. This
3205 was particularly bad for 0.2.0.13 and later bridge relays, who
3206 would never have a v2 networkstatus and would thus always crash
3207 when used. Bugfixes on 0.2.0.x.
3208 - Estimate the v3 networkstatus size more accurately, rather than
3209 estimating it at zero bytes and giving it artificially high priority
3210 compared to other directory requests. Bugfix on 0.2.0.x.
3213 - Fix configure.in logic for cross-compilation.
3214 - When we load a bridge descriptor from the cache, and it was
3215 previously unreachable, mark it as retriable so we won't just
3216 ignore it. Also, try fetching a new copy immediately. Bugfixes
3218 - The bridge GeoIP stats were counting other relays, for example
3219 self-reachability and authority-reachability tests.
3222 - Support compilation to target iPhone; patch from cjacker huang.
3223 To build for iPhone, pass the --enable-iphone option to configure.
3226 Changes in version 0.2.0.14-alpha - 2007-12-23
3228 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
3229 without a datadirectory from a previous Tor install. Reported
3231 - Fix a crash when we fetch a descriptor that turns out to be
3232 unexpected (it used to be in our networkstatus when we started
3233 fetching it, but it isn't in our current networkstatus), and we
3234 aren't using bridges. Bugfix on 0.2.0.x.
3235 - Fix a crash when accessing hidden services: it would work the first
3236 time you use a given introduction point for your service, but
3237 on subsequent requests we'd be using garbage memory. Fixed by
3238 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
3239 - Fix a crash when we load a bridge descriptor from disk but we don't
3240 currently have a Bridge line for it in our torrc. Bugfix on
3244 - If bridge authorities set BridgePassword, they will serve a
3245 snapshot of known bridge routerstatuses from their DirPort to
3246 anybody who knows that password. Unset by default.
3249 - Make the unit tests build again.
3250 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
3251 - Make PublishServerDescriptor default to 1, so the default doesn't
3252 have to change as we invent new directory protocol versions.
3253 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
3254 be included unless sys/time.h is already included. Fixes
3255 bug 553. Bugfix on 0.2.0.x.
3256 - If we receive a general-purpose descriptor and then receive an
3257 identical bridge-purpose descriptor soon after, don't discard
3258 the next one as a duplicate.
3261 - If BridgeRelay is set to 1, then the default for
3262 PublishServerDescriptor is now "bridge" rather than "v2,v3".
3263 - If the user sets RelayBandwidthRate but doesn't set
3264 RelayBandwidthBurst, then make them equal rather than erroring out.
3267 Changes in version 0.2.0.13-alpha - 2007-12-21
3268 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
3269 Goodell, fixes many more bugs, and adds a lot of infrastructure for
3272 o New directory authorities:
3273 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
3277 - Only update guard status (usable / not usable) once we have
3278 enough directory information. This was causing us to always pick
3279 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
3280 causing us to discard all our guards on startup if we hadn't been
3281 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
3282 - Purge old entries from the "rephist" database and the hidden
3283 service descriptor databases even when DirPort is zero. Bugfix
3285 - We were ignoring our RelayBandwidthRate for the first 30 seconds
3286 after opening a circuit -- even a relayed circuit. Bugfix on
3288 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
3289 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
3290 crashing or mis-answering these types of requests.
3291 - Relays were publishing their server descriptor to v1 and v2
3292 directory authorities, but they didn't try publishing to v3-only
3293 authorities. Fix this; and also stop publishing to v1 authorities.
3295 - When we were reading router descriptors from cache, we were ignoring
3296 the annotations -- so for example we were reading in bridge-purpose
3297 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
3298 - When we decided to send a 503 response to a request for servers, we
3299 were then also sending the server descriptors: this defeats the
3300 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
3303 - Bridge relays now behave like clients with respect to time
3304 intervals for downloading new consensus documents -- otherwise they
3305 stand out. Bridge users now wait until the end of the interval,
3306 so their bridge relay will be sure to have a new consensus document.
3307 - Three new config options (AlternateDirAuthority,
3308 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
3309 user selectively replace the default directory authorities by type,
3310 rather than the all-or-nothing replacement that DirServer offers.
3311 - Tor can now be configured to read a GeoIP file from disk in one
3312 of two formats. This can be used by controllers to map IP addresses
3313 to countries. Eventually, it may support exit-by-country.
3314 - When possible, bridge relays remember which countries users
3315 are coming from, and report aggregate information in their
3316 extra-info documents, so that the bridge authorities can learn
3317 where Tor is blocked.
3318 - Bridge directory authorities now do reachability testing on the
3319 bridges they know. They provide router status summaries to the
3320 controller via "getinfo ns/purpose/bridge", and also dump summaries
3321 to a file periodically.
3322 - Stop fetching directory info so aggressively if your DirPort is
3323 on but your ORPort is off; stop fetching v2 dir info entirely.
3324 You can override these choices with the new FetchDirInfoEarly
3328 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
3329 consensus documents when there are too many relays at a single
3330 IP address. Now clear it in v2 network status documents too, and
3331 also clear it in routerinfo_t when the relay is no longer listed
3332 in the relevant networkstatus document.
3333 - Don't crash if we get an unexpected value for the
3334 PublishServerDescriptor config option. Reported by Matt Edman;
3335 bugfix on 0.2.0.9-alpha.
3336 - Our new v2 hidden service descriptor format allows descriptors
3337 that have no introduction points. But Tor crashed when we tried
3338 to build a descriptor with no intro points (and it would have
3339 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
3341 - Fix building with dmalloc 5.5.2 with glibc.
3342 - Reject uploaded descriptors and extrainfo documents if they're
3343 huge. Otherwise we'll cache them all over the network and it'll
3344 clog everything up. Reported by Aljosha Judmayer.
3345 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
3346 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
3347 - When the DANGEROUS_VERSION controller status event told us we're
3348 running an obsolete version, it used the string "OLD" to describe
3349 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
3350 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
3351 - If we can't expand our list of entry guards (e.g. because we're
3352 using bridges or we have StrictEntryNodes set), don't mark relays
3353 down when they fail a directory request. Otherwise we're too quick
3354 to mark all our entry points down. Bugfix on 0.1.2.x.
3355 - Fix handling of hex nicknames when answering controller requests for
3356 networkstatus by name, or when deciding whether to warn about unknown
3357 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
3358 - Fix a couple of hard-to-trigger autoconf problems that could result
3359 in really weird results on platforms whose sys/types.h files define
3360 nonstandard integer types. Bugfix on 0.1.2.x.
3361 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
3362 - Don't crash on name lookup when we have no current consensus. Fixes
3363 bug 538; bugfix on 0.2.0.x.
3364 - Only Tors that want to mirror the v2 directory info should
3365 create the "cached-status" directory in their datadir. (All Tors
3366 used to create it.) Bugfix on 0.2.0.9-alpha.
3367 - Directory authorities should only automatically download Extra Info
3368 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
3371 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
3372 consumers. (We already do this on HUP.)
3373 - Authorities and caches fetch the v2 networkstatus documents
3374 less often, now that v3 is encouraged.
3375 - Add a new config option BridgeRelay that specifies you want to
3376 be a bridge relay. Right now the only difference is that it makes
3377 you answer begin_dir requests, and it makes you cache dir info,
3378 even if your DirPort isn't on.
3379 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
3380 ask about source, timestamp of arrival, purpose, etc. We need
3381 something like this to help Vidalia not do GeoIP lookups on bridge
3383 - Allow multiple HashedControlPassword config lines, to support
3384 multiple controller passwords.
3385 - Authorities now decide whether they're authoritative for a given
3386 router based on the router's purpose.
3387 - New config options AuthDirBadDir and AuthDirListBadDirs for
3388 authorities to mark certain relays as "bad directories" in the
3389 networkstatus documents. Also supports the "!baddir" directive in
3390 the approved-routers file.
3393 Changes in version 0.2.0.12-alpha - 2007-11-16
3394 This twelfth development snapshot fixes some more build problems as
3395 well as a few minor bugs.
3398 - Make it build on OpenBSD again. Patch from tup.
3399 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
3400 package-building for Red Hat, OS X, etc.
3402 o Minor bugfixes (on 0.1.2.x):
3403 - Changing the ExitPolicyRejectPrivate setting should cause us to
3404 rebuild our server descriptor.
3406 o Minor bugfixes (on 0.2.0.x):
3407 - When we're lacking a consensus, don't try to perform rendezvous
3408 operations. Reported by Karsten Loesing.
3409 - Fix a small memory leak whenever we decide against using a
3410 newly picked entry guard. Reported by Mike Perry.
3411 - When authorities detected more than two relays running on the same
3412 IP address, they were clearing all the status flags but forgetting
3413 to clear the "hsdir" flag. So clients were being told that a
3414 given relay was the right choice for a v2 hsdir lookup, yet they
3415 never had its descriptor because it was marked as 'not running'
3417 - If we're trying to fetch a bridge descriptor and there's no way
3418 the bridge authority could help us (for example, we don't know
3419 a digest, or there is no bridge authority), don't be so eager to
3420 fall back to asking the bridge authority.
3421 - If we're using bridges or have strictentrynodes set, and our
3422 chosen exit is in the same family as all our bridges/entry guards,
3423 then be flexible about families.
3426 - When we negotiate a v2 link-layer connection (not yet implemented),
3427 accept RELAY_EARLY cells and turn them into RELAY cells if we've
3428 negotiated a v1 connection for their next step. Initial code for
3432 Changes in version 0.2.0.11-alpha - 2007-11-12
3433 This eleventh development snapshot fixes some build problems with
3434 the previous snapshot. It also includes a more secure-by-default exit
3435 policy for relays, fixes an enormous memory leak for exit relays, and
3436 fixes another bug where servers were falling out of the directory list.
3439 - Exit policies now reject connections that are addressed to a
3440 relay's public (external) IP address too, unless
3441 ExitPolicyRejectPrivate is turned off. We do this because too
3442 many relays are running nearby to services that trust them based
3443 on network address. Bugfix on 0.1.2.x.
3446 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
3447 on every successful resolve. Reported by Mike Perry; bugfix
3449 - On authorities, never downgrade to old router descriptors simply
3450 because they're listed in the consensus. This created a catch-22
3451 where we wouldn't list a new descriptor because there was an
3452 old one in the consensus, and we couldn't get the new one in the
3453 consensus because we wouldn't list it. Possible fix for bug 548.
3454 Also, this might cause bug 543 to appear on authorities; if so,
3455 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
3457 o Packaging fixes on 0.2.0.10-alpha:
3458 - We were including instructions about what to do with the
3459 src/config/fallback-consensus file, but we weren't actually
3460 including it in the tarball. Disable all of that for now.
3463 - Allow people to say PreferTunnelledDirConns rather than
3464 PreferTunneledDirConns, for those alternate-spellers out there.
3467 - Don't reevaluate all the information from our consensus document
3468 just because we've downloaded a v2 networkstatus that we intend
3469 to cache. Fixes bug 545; bugfix on 0.2.0.x.
3472 Changes in version 0.2.0.10-alpha - 2007-11-10
3473 This tenth development snapshot adds a third v3 directory authority
3474 run by Mike Perry, adds most of Karsten Loesing's new hidden service
3475 descriptor format, fixes a bad crash bug and new bridge bugs introduced
3476 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
3477 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
3478 addresses many more minor issues.
3480 o New directory authorities:
3481 - Set up ides (run by Mike Perry) as the third v3 directory authority.
3484 - Allow tunnelled directory connections to ask for an encrypted
3485 "begin_dir" connection or an anonymized "uses a full Tor circuit"
3486 connection independently. Now we can make anonymized begin_dir
3487 connections for (e.g.) more secure hidden service posting and
3489 - More progress on proposal 114: code from Karsten Loesing to
3490 implement new hidden service descriptor format.
3491 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
3492 accommodate the growing number of servers that use the default
3493 and are reaching it.
3494 - Directory authorities use a new formula for selecting which nodes
3495 to advertise as Guards: they must be in the top 7/8 in terms of
3496 how long we have known about them, and above the median of those
3497 nodes in terms of weighted fractional uptime.
3498 - Make "not enough dir info yet" warnings describe *why* Tor feels
3499 it doesn't have enough directory info yet.
3502 - Stop servers from crashing if they set a Family option (or
3503 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
3505 - Make bridge users work again -- the move to v3 directories in
3506 0.2.0.9-alpha had introduced a number of bugs that made bridges
3507 no longer work for clients.
3508 - When the clock jumps forward a lot, do not allow the bandwidth
3509 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
3511 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
3512 - When the consensus lists a router descriptor that we previously were
3513 mirroring, but that we considered non-canonical, reload the
3514 descriptor as canonical. This fixes bug 543 where Tor servers
3515 would start complaining after a few days that they don't have
3516 enough directory information to build a circuit.
3517 - Consider replacing the current consensus when certificates arrive
3518 that make the pending consensus valid. Previously, we were only
3519 considering replacement when the new certs _didn't_ help.
3520 - Fix an assert error on startup if we didn't already have the
3521 consensus and certs cached in our datadirectory: we were caching
3522 the consensus in consensus_waiting_for_certs but then free'ing it
3524 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
3525 Request) if we need more v3 certs but we've already got pending
3526 requests for all of them.
3527 - Correctly back off from failing certificate downloads. Fixes
3529 - Authorities don't vote on the Running flag if they have been running
3530 for less than 30 minutes themselves. Fixes bug 547, where a newly
3531 started authority would vote that everyone was down.
3534 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
3535 it, it had no AES, and it hasn't seen any security patches since
3539 - Clients now hold circuitless TLS connections open for 1.5 times
3540 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
3541 rebuild a new circuit over them within that timeframe. Previously,
3542 they held them open only for KeepalivePeriod (5 minutes).
3543 - Use "If-Modified-Since" to avoid retrieving consensus
3544 networkstatuses that we already have.
3545 - When we have no consensus, check FallbackNetworkstatusFile (defaults
3546 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
3547 we start knowing some directory caches.
3548 - When we receive a consensus from the future, warn about skew.
3549 - Improve skew reporting: try to give the user a better log message
3550 about how skewed they are, and how much this matters.
3551 - When we have a certificate for an authority, believe that
3552 certificate's claims about the authority's IP address.
3553 - New --quiet command-line option to suppress the default console log.
3554 Good in combination with --hash-password.
3555 - Authorities send back an X-Descriptor-Not-New header in response to
3556 an accepted-but-discarded descriptor upload. Partially implements
3558 - Make the log message for "tls error. breaking." more useful.
3559 - Better log messages about certificate downloads, to attempt to
3560 track down the second incarnation of bug 546.
3562 o Minor features (bridges):
3563 - If bridge users set UpdateBridgesFromAuthority, but the digest
3564 they ask for is a 404 from the bridge authority, they now fall
3565 back to trying the bridge directly.
3566 - Bridges now use begin_dir to publish their server descriptor to
3567 the bridge authority, even when they haven't set TunnelDirConns.
3569 o Minor features (controller):
3570 - When reporting clock skew, and we know that the clock is _at least
3571 as skewed_ as some value, but we don't know the actual value,
3572 report the value as a "minimum skew."
3575 - Update linux-tor-prio.sh script to allow QoS based on the uid of
3576 the Tor process. Patch from Marco Bonetti with tweaks from Mike
3580 - Refuse to start if both ORPort and UseBridges are set. Bugfix
3581 on 0.2.0.x, suggested by Matt Edman.
3582 - Don't stop fetching descriptors when FetchUselessDescriptors is
3583 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
3584 reported by tup and ioerror.
3585 - Better log message on vote from unknown authority.
3586 - Don't log "Launching 0 request for 0 router" message.
3588 o Minor bugfixes (memory leaks):
3589 - Stop leaking memory every time we parse a v3 certificate. Bugfix
3591 - Stop leaking memory every time we load a v3 certificate. Bugfix
3592 on 0.2.0.1-alpha. Fixes bug 536.
3593 - Stop leaking a cached networkstatus on exit. Bugfix on
3595 - Stop leaking voter information every time we free a consensus.
3596 Bugfix on 0.2.0.3-alpha.
3597 - Stop leaking signed data every time we check a voter signature.
3598 Bugfix on 0.2.0.3-alpha.
3599 - Stop leaking a signature every time we fail to parse a consensus or
3600 a vote. Bugfix on 0.2.0.3-alpha.
3601 - Stop leaking v2_download_status_map on shutdown. Bugfix on
3603 - Stop leaking conn->nickname every time we make a connection to a
3604 Tor relay without knowing its expected identity digest (e.g. when
3605 using bridges). Bugfix on 0.2.0.3-alpha.
3607 - Minor bugfixes (portability):
3608 - Run correctly on platforms where rlim_t is larger than unsigned
3609 long, and/or where the real limit for number of open files is
3610 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
3611 particular, these may be needed for OS X 10.5.
3614 Changes in version 0.1.2.18 - 2007-10-28
3615 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
3616 hidden service introduction that were causing huge delays, and a big
3617 bug that was causing some servers to disappear from the network status
3618 lists for a few hours each day.
3620 o Major bugfixes (crashes):
3621 - If a connection is shut down abruptly because of something that
3622 happened inside connection_flushed_some(), do not call
3623 connection_finished_flushing(). Should fix bug 451:
3624 "connection_stop_writing: Assertion conn->write_event failed"
3625 Bugfix on 0.1.2.7-alpha.
3626 - Fix possible segfaults in functions called from
3627 rend_process_relay_cell().
3629 o Major bugfixes (hidden services):
3630 - Hidden services were choosing introduction points uniquely by
3631 hexdigest, but when constructing the hidden service descriptor
3632 they merely wrote the (potentially ambiguous) nickname.
3633 - Clients now use the v2 intro format for hidden service
3634 connections: they specify their chosen rendezvous point by identity
3635 digest rather than by (potentially ambiguous) nickname. These
3636 changes could speed up hidden service connections dramatically.
3638 o Major bugfixes (other):
3639 - Stop publishing a new server descriptor just because we get a
3640 HUP signal. This led (in a roundabout way) to some servers getting
3641 dropped from the networkstatus lists for a few hours each day.
3642 - When looking for a circuit to cannibalize, consider family as well
3643 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
3644 circuit cannibalization).
3645 - When a router wasn't listed in a new networkstatus, we were leaving
3646 the flags for that router alone -- meaning it remained Named,
3647 Running, etc -- even though absence from the networkstatus means
3648 that it shouldn't be considered to exist at all anymore. Now we
3649 clear all the flags for routers that fall out of the networkstatus
3650 consensus. Fixes bug 529.
3653 - Don't try to access (or alter) the state file when running
3654 --list-fingerprint or --verify-config or --hash-password. Resolves
3656 - When generating information telling us how to extend to a given
3657 router, do not try to include the nickname if it is
3658 absent. Resolves bug 467.
3659 - Fix a user-triggerable segfault in expand_filename(). (There isn't
3660 a way to trigger this remotely.)
3661 - When sending a status event to the controller telling it that an
3662 OR address is reachable, set the port correctly. (Previously we
3663 were reporting the dir port.)
3664 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
3665 command. Bugfix on 0.1.2.17.
3666 - When loading bandwidth history, do not believe any information in
3667 the future. Fixes bug 434.
3668 - When loading entry guard information, do not believe any information
3670 - When we have our clock set far in the future and generate an
3671 onion key, then re-set our clock to be correct, we should not stop
3672 the onion key from getting rotated.
3673 - On some platforms, accept() can return a broken address. Detect
3674 this more quietly, and deal accordingly. Fixes bug 483.
3675 - It's not actually an error to find a non-pending entry in the DNS
3676 cache when canceling a pending resolve. Don't log unless stuff
3677 is fishy. Resolves bug 463.
3678 - Don't reset trusted dir server list when we set a configuration
3679 option. Patch from Robert Hogan.
3680 - Don't try to create the datadir when running --verify-config or
3681 --hash-password. Resolves bug 540.
3684 Changes in version 0.2.0.9-alpha - 2007-10-24
3685 This ninth development snapshot switches clients to the new v3 directory
3686 system; allows servers to be listed in the network status even when they
3687 have the same nickname as a registered server; and fixes many other
3688 bugs including a big one that was causing some servers to disappear
3689 from the network status lists for a few hours each day.
3691 o Major features (directory system):
3692 - Clients now download v3 consensus networkstatus documents instead
3693 of v2 networkstatus documents. Clients and caches now base their
3694 opinions about routers on these consensus documents. Clients only
3695 download router descriptors listed in the consensus.
3696 - Authorities now list servers who have the same nickname as
3697 a different named server, but list them with a new flag,
3698 "Unnamed". Now we can list servers that happen to pick the same
3699 nickname as a server that registered two years ago and then
3700 disappeared. Partially implements proposal 122.
3701 - If the consensus lists a router as "Unnamed", the name is assigned
3702 to a different router: do not identify the router by that name.
3703 Partially implements proposal 122.
3704 - Authorities can now come to a consensus on which method to use to
3705 compute the consensus. This gives us forward compatibility.
3708 - Stop publishing a new server descriptor just because we HUP or
3709 when we find our DirPort to be reachable but won't actually publish
3710 it. New descriptors without any real changes are dropped by the
3711 authorities, and can screw up our "publish every 18 hours" schedule.
3713 - When a router wasn't listed in a new networkstatus, we were leaving
3714 the flags for that router alone -- meaning it remained Named,
3715 Running, etc -- even though absence from the networkstatus means
3716 that it shouldn't be considered to exist at all anymore. Now we
3717 clear all the flags for routers that fall out of the networkstatus
3718 consensus. Fixes bug 529; bugfix on 0.1.2.x.
3719 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
3720 extrainfo documents and then discard them immediately for not
3721 matching the latest router. Bugfix on 0.2.0.1-alpha.
3723 o Minor features (v3 directory protocol):
3724 - Allow tor-gencert to generate a new certificate without replacing
3726 - Allow certificates to include an address.
3727 - When we change our directory-cache settings, reschedule all voting
3728 and download operations.
3729 - Reattempt certificate downloads immediately on failure, as long as
3730 we haven't failed a threshold number of times yet.
3731 - Delay retrying consensus downloads while we're downloading
3732 certificates to verify the one we just got. Also, count getting a
3733 consensus that we already have (or one that isn't valid) as a failure,
3734 and count failing to get the certificates after 20 minutes as a
3736 - Build circuits and download descriptors even if our consensus is a
3737 little expired. (This feature will go away once authorities are
3740 o Minor features (router descriptor cache):
3741 - If we find a cached-routers file that's been sitting around for more
3742 than 28 days unmodified, then most likely it's a leftover from
3743 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
3745 - When we (as a cache) download a descriptor because it was listed
3746 in a consensus, remember when the consensus was supposed to expire,
3747 and don't expire the descriptor until then.
3749 o Minor features (performance):
3750 - Call routerlist_remove_old_routers() much less often. This should
3751 speed startup, especially on directory caches.
3752 - Don't try to launch new descriptor downloads quite so often when we
3753 already have enough directory information to build circuits.
3754 - Base64 decoding was actually showing up on our profile when parsing
3755 the initial descriptor file; switch to an in-process all-at-once
3756 implementation that's about 3.5x times faster than calling out to
3759 o Minor features (compilation):
3760 - Detect non-ASCII platforms (if any still exist) and refuse to
3761 build there: some of our code assumes that 'A' is 65 and so on.
3763 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
3764 - Make the "next period" votes into "current period" votes immediately
3765 after publishing the consensus; avoid a heisenbug that made them
3766 stick around indefinitely.
3767 - When we discard a vote as a duplicate, do not report this as
3769 - Treat missing v3 keys or certificates as an error when running as a
3770 v3 directory authority.
3771 - When we're configured to be a v3 authority, but we're only listed
3772 as a non-v3 authority in our DirServer line for ourself, correct
3774 - If an authority doesn't have a qualified hostname, just put
3775 its address in the vote. This fixes the problem where we referred to
3776 "moria on moria:9031."
3777 - Distinguish between detached signatures for the wrong period, and
3778 detached signatures for a divergent vote.
3779 - Fix a small memory leak when computing a consensus.
3780 - When there's no concensus, we were forming a vote every 30
3781 minutes, but writing the "valid-after" line in our vote based
3782 on our configured V3AuthVotingInterval: so unless the intervals
3783 matched up, we immediately rejected our own vote because it didn't
3784 start at the voting interval that caused us to construct a vote.
3786 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
3787 - Delete unverified-consensus when the real consensus is set.
3788 - Consider retrying a consensus networkstatus fetch immediately
3789 after one fails: don't wait 60 seconds to notice.
3790 - When fetching a consensus as a cache, wait until a newer consensus
3791 should exist before trying to replace the current one.
3792 - Use a more forgiving schedule for retrying failed consensus
3793 downloads than for other types.
3795 o Minor bugfixes (other directory issues):
3796 - Correct the implementation of "download votes by digest." Bugfix on
3798 - Authorities no longer send back "400 you're unreachable please fix
3799 it" errors to Tor servers that aren't online all the time. We're
3800 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
3802 o Minor bugfixes (controller):
3803 - Don't reset trusted dir server list when we set a configuration
3804 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
3805 - Respond to INT and TERM SIGNAL commands before we execute the
3806 signal, in case the signal shuts us down. We had a patch in
3807 0.1.2.1-alpha that tried to do this by queueing the response on
3808 the connection's buffer before shutting down, but that really
3809 isn't the same thing at all. Bug located by Matt Edman.
3811 o Minor bugfixes (misc):
3812 - Correctly check for bad options to the "PublishServerDescriptor"
3813 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
3814 - Stop leaking memory on failing case of base32_decode, and make
3815 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
3816 - Don't try to download extrainfo documents when we're trying to
3817 fetch enough directory info to build a circuit: having enough
3818 info should get priority. Bugfix on 0.2.0.x.
3819 - Don't complain that "your server has not managed to confirm that its
3820 ports are reachable" if we haven't been able to build any circuits
3821 yet. Bug found by spending four hours without a v3 consensus. Bugfix
3823 - Detect the reason for failing to mmap a descriptor file we just
3824 wrote, and give a more useful log message. Fixes bug 533. Bugfix
3827 o Code simplifications and refactoring:
3828 - Remove support for the old bw_accounting file: we've been storing
3829 bandwidth accounting information in the state file since
3830 0.1.2.5-alpha. This may result in bandwidth accounting errors
3831 if you try to upgrade from 0.1.1.x or earlier, or if you try to
3832 downgrade to 0.1.1.x or earlier.
3833 - New convenience code to locate a file within the DataDirectory.
3834 - Move non-authority functionality out of dirvote.c.
3835 - Refactor the arguments for router_pick_{directory_|trusteddir}server
3836 so that they all take the same named flags.
3839 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
3840 Unix users an easy way to script their Tor process (e.g. by
3841 adjusting bandwidth based on the time of the day).
3844 Changes in version 0.2.0.8-alpha - 2007-10-12
3845 This eighth development snapshot fixes a crash bug that's been bothering
3846 us since February 2007, lets bridge authorities store a list of bridge
3847 descriptors they've seen, gets v3 directory voting closer to working,
3848 starts caching v3 directory consensus documents on directory mirrors,
3849 and fixes a variety of smaller issues including some minor memory leaks.
3851 o Major features (router descriptor cache):
3852 - Store routers in a file called cached-descriptors instead of in
3853 cached-routers. Initialize cached-descriptors from cached-routers
3854 if the old format is around. The new format allows us to store
3855 annotations along with descriptors.
3856 - Use annotations to record the time we received each descriptor, its
3857 source, and its purpose.
3858 - Disable the SETROUTERPURPOSE controller command: it is now
3860 - Controllers should now specify cache=no or cache=yes when using
3861 the +POSTDESCRIPTOR command.
3862 - Bridge authorities now write bridge descriptors to disk, meaning
3863 we can export them to other programs and begin distributing them
3866 o Major features (directory authorities):
3867 - When a v3 authority is missing votes or signatures, it now tries
3869 - Directory authorities track weighted fractional uptime as well as
3870 weighted mean-time-between failures. WFU is suitable for deciding
3871 whether a node is "usually up", while MTBF is suitable for deciding
3872 whether a node is "likely to stay up." We need both, because
3873 "usually up" is a good requirement for guards, while "likely to
3874 stay up" is a good requirement for long-lived connections.
3876 o Major features (v3 directory system):
3877 - Caches now download v3 network status documents as needed,
3878 and download the descriptors listed in them.
3879 - All hosts now attempt to download and keep fresh v3 authority
3880 certificates, and re-attempt after failures.
3881 - More internal-consistency checks for vote parsing.
3883 o Major bugfixes (crashes):
3884 - If a connection is shut down abruptly because of something that
3885 happened inside connection_flushed_some(), do not call
3886 connection_finished_flushing(). Should fix bug 451. Bugfix on
3889 o Major bugfixes (performance):
3890 - Fix really bad O(n^2) performance when parsing a long list of
3891 routers: Instead of searching the entire list for an "extra-info "
3892 string which usually wasn't there, once for every routerinfo
3893 we read, just scan lines forward until we find one we like.
3895 - When we add data to a write buffer in response to the data on that
3896 write buffer getting low because of a flush, do not consider the
3897 newly added data as a candidate for immediate flushing, but rather
3898 make it wait until the next round of writing. Otherwise, we flush
3899 and refill recursively, and a single greedy TLS connection can
3900 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
3902 o Minor features (v3 authority system):
3903 - Add more ways for tools to download the votes that lead to the
3905 - Send a 503 when low on bandwidth and a vote, consensus, or
3906 certificate is requested.
3907 - If-modified-since is now implemented properly for all kinds of
3908 certificate requests.
3910 o Minor bugfixes (network statuses):
3911 - Tweak the implementation of proposal 109 slightly: allow at most
3912 two Tor servers on the same IP address, except if it's the location
3913 of a directory authority, in which case allow five. Bugfix on
3916 o Minor bugfixes (controller):
3917 - When sending a status event to the controller telling it that an
3918 OR address is reachable, set the port correctly. (Previously we
3919 were reporting the dir port.) Bugfix on 0.1.2.x.
3921 o Minor bugfixes (v3 directory system):
3922 - Fix logic to look up a cert by its signing key digest. Bugfix on
3924 - Only change the reply to a vote to "OK" if it's not already
3925 set. This gets rid of annoying "400 OK" log messages, which may
3926 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
3927 - When we get a valid consensus, recompute the voting schedule.
3928 - Base the valid-after time of a vote on the consensus voting
3929 schedule, not on our preferred schedule.
3930 - Make the return values and messages from signature uploads and
3931 downloads more sensible.
3932 - Fix a memory leak when serving votes and consensus documents, and
3933 another when serving certificates.
3935 o Minor bugfixes (performance):
3936 - Use a slightly simpler string hashing algorithm (copying Python's
3937 instead of Java's) and optimize our digest hashing algorithm to take
3938 advantage of 64-bit platforms and to remove some possibly-costly
3940 - Fix a minor memory leak whenever we parse guards from our state
3941 file. Bugfix on 0.2.0.7-alpha.
3942 - Fix a minor memory leak whenever we write out a file. Bugfix on
3944 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
3945 command. Bugfix on 0.2.0.5-alpha.
3947 o Minor bugfixes (portability):
3948 - On some platforms, accept() can return a broken address. Detect
3949 this more quietly, and deal accordingly. Fixes bug 483.
3950 - Stop calling tor_strlower() on uninitialized memory in some cases.
3951 Bugfix in 0.2.0.7-alpha.
3953 o Minor bugfixes (usability):
3954 - Treat some 403 responses from directory servers as INFO rather than
3955 WARN-severity events.
3956 - It's not actually an error to find a non-pending entry in the DNS
3957 cache when canceling a pending resolve. Don't log unless stuff is
3958 fishy. Resolves bug 463.
3960 o Minor bugfixes (anonymity):
3961 - Never report that we've used more bandwidth than we're willing to
3962 relay: it leaks how much non-relay traffic we're using. Resolves
3964 - When looking for a circuit to cannibalize, consider family as well
3965 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
3966 circuit cannibalization).
3968 o Code simplifications and refactoring:
3969 - Make a bunch of functions static. Remove some dead code.
3970 - Pull out about a third of the really big routerlist.c; put it in a
3971 new module, networkstatus.c.
3972 - Merge the extra fields in local_routerstatus_t back into
3973 routerstatus_t: we used to need one routerstatus_t for each
3974 authority's opinion, plus a local_routerstatus_t for the locally
3975 computed consensus opinion. To save space, we put the locally
3976 modified fields into local_routerstatus_t, and only the common
3977 stuff into routerstatus_t. But once v3 directories are in use,
3978 clients and caches will no longer need to hold authority opinions;
3979 thus, the rationale for keeping the types separate is now gone.
3980 - Make the code used to reschedule and reattempt downloads more
3982 - Turn all 'Are we a directory server/mirror?' logic into a call to
3984 - Remove the code to generate the oldest (v1) directory format.
3985 The code has been disabled since 0.2.0.5-alpha.
3988 Changes in version 0.2.0.7-alpha - 2007-09-21
3989 This seventh development snapshot makes bridges work again, makes bridge
3990 authorities work for the first time, fixes two huge performance flaws
3991 in hidden services, and fixes a variety of minor issues.
3993 o New directory authorities:
3994 - Set up moria1 and tor26 as the first v3 directory authorities. See
3995 doc/spec/dir-spec.txt for details on the new directory design.
3997 o Major bugfixes (crashes):
3998 - Fix possible segfaults in functions called from
3999 rend_process_relay_cell(). Bugfix on 0.1.2.x.
4001 o Major bugfixes (bridges):
4002 - Fix a bug that made servers send a "404 Not found" in response to
4003 attempts to fetch their server descriptor. This caused Tor servers
4004 to take many minutes to establish reachability for their DirPort,
4005 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
4006 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
4007 users configure that and specify a bridge with an identity
4008 fingerprint, now they will lookup the bridge descriptor at the
4009 default bridge authority via a one-hop tunnel, but once circuits
4010 are established they will switch to a three-hop tunnel for later
4011 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
4013 o Major bugfixes (hidden services):
4014 - Hidden services were choosing introduction points uniquely by
4015 hexdigest, but when constructing the hidden service descriptor
4016 they merely wrote the (potentially ambiguous) nickname.
4017 - Clients now use the v2 intro format for hidden service
4018 connections: they specify their chosen rendezvous point by identity
4019 digest rather than by (potentially ambiguous) nickname. Both
4020 are bugfixes on 0.1.2.x, and they could speed up hidden service
4021 connections dramatically. Thanks to Karsten Loesing.
4023 o Minor features (security):
4024 - As a client, do not believe any server that tells us that an
4025 address maps to an internal address space.
4026 - Make it possible to enable HashedControlPassword and
4027 CookieAuthentication at the same time.
4029 o Minor features (guard nodes):
4030 - Tag every guard node in our state file with the version that
4031 we believe added it, or with our own version if we add it. This way,
4032 if a user temporarily runs an old version of Tor and then switches
4033 back to a new one, she doesn't automatically lose her guards.
4035 o Minor features (speed):
4036 - When implementing AES counter mode, update only the portions of the
4037 counter buffer that need to change, and don't keep separate
4038 network-order and host-order counters when they are the same (i.e.,
4039 on big-endian hosts.)
4041 o Minor features (controller):
4042 - Accept LF instead of CRLF on controller, since some software has a
4043 hard time generating real Internet newlines.
4044 - Add GETINFO values for the server status events
4045 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
4049 - Routers no longer include bandwidth-history lines in their
4050 descriptors; this information is already available in extra-info
4051 documents, and including it in router descriptors took up 60%
4052 (!) of compressed router descriptor downloads. Completes
4053 implementation of proposal 104.
4054 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
4055 and TorControl.py, as they use the old v0 controller protocol,
4056 and are obsoleted by TorFlow anyway.
4057 - Drop support for v1 rendezvous descriptors, since we never used
4058 them anyway, and the code has probably rotted by now. Based on
4059 patch from Karsten Loesing.
4060 - On OSX, stop warning the user that kqueue support in libevent is
4061 "experimental", since it seems to have worked fine for ages.
4064 - When generating information telling us how to extend to a given
4065 router, do not try to include the nickname if it is absent. Fixes
4066 bug 467. Bugfix on 0.2.0.3-alpha.
4067 - Fix a user-triggerable (but not remotely-triggerable) segfault
4068 in expand_filename(). Bugfix on 0.1.2.x.
4069 - Fix a memory leak when freeing incomplete requests from DNSPort.
4070 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
4071 - Don't try to access (or alter) the state file when running
4072 --list-fingerprint or --verify-config or --hash-password. (Resolves
4073 bug 499.) Bugfix on 0.1.2.x.
4074 - Servers used to decline to publish their DirPort if their
4075 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
4076 were below a threshold. Now they only look at BandwidthRate and
4077 RelayBandwidthRate. Bugfix on 0.1.2.x.
4078 - Remove an optimization in the AES counter-mode code that assumed
4079 that the counter never exceeded 2^68. When the counter can be set
4080 arbitrarily as an IV (as it is by Karsten's new hidden services
4081 code), this assumption no longer holds. Bugfix on 0.1.2.x.
4082 - Resume listing "AUTHORITY" flag for authorities in network status.
4083 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
4085 o Code simplifications and refactoring:
4086 - Revamp file-writing logic so we don't need to have the entire
4087 contents of a file in memory at once before we write to disk. Tor,
4089 - Turn "descriptor store" into a full-fledged type.
4090 - Move all NT services code into a separate source file.
4091 - Unify all code that computes medians, percentile elements, etc.
4092 - Get rid of a needless malloc when parsing address policies.
4095 Changes in version 0.1.2.17 - 2007-08-30
4096 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
4097 X bundles. Vidalia 0.0.14 makes authentication required for the
4098 ControlPort in the default configuration, which addresses important
4099 security risks. Everybody who uses Vidalia (or another controller)
4102 In addition, this Tor update fixes major load balancing problems with
4103 path selection, which should speed things up a lot once many people
4106 o Major bugfixes (security):
4107 - We removed support for the old (v0) control protocol. It has been
4108 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
4109 become more of a headache than it's worth.
4111 o Major bugfixes (load balancing):
4112 - When choosing nodes for non-guard positions, weight guards
4113 proportionally less, since they already have enough load. Patch
4115 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
4116 will allow fast Tor servers to get more attention.
4117 - When we're upgrading from an old Tor version, forget our current
4118 guards and pick new ones according to the new weightings. These
4119 three load balancing patches could raise effective network capacity
4120 by a factor of four. Thanks to Mike Perry for measurements.
4122 o Major bugfixes (stream expiration):
4123 - Expire not-yet-successful application streams in all cases if
4124 they've been around longer than SocksTimeout. Right now there are
4125 some cases where the stream will live forever, demanding a new
4126 circuit every 15 seconds. Fixes bug 454; reported by lodger.
4128 o Minor features (controller):
4129 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
4130 is valid before any authentication has been received. It tells
4131 a controller what kind of authentication is expected, and what
4132 protocol is spoken. Implements proposal 119.
4134 o Minor bugfixes (performance):
4135 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
4136 greatly speeding up loading cached-routers from disk on startup.
4137 - Disable sentinel-based debugging for buffer code: we squashed all
4138 the bugs that this was supposed to detect a long time ago, and now
4139 its only effect is to change our buffer sizes from nice powers of
4140 two (which platform mallocs tend to like) to values slightly over
4141 powers of two (which make some platform mallocs sad).
4143 o Minor bugfixes (misc):
4144 - If exit bandwidth ever exceeds one third of total bandwidth, then
4145 use the correct formula to weight exit nodes when choosing paths.
4146 Based on patch from Mike Perry.
4147 - Choose perfectly fairly among routers when choosing by bandwidth and
4148 weighting by fraction of bandwidth provided by exits. Previously, we
4149 would choose with only approximate fairness, and correct ourselves
4150 if we ran off the end of the list.
4151 - If we require CookieAuthentication but we fail to write the
4152 cookie file, we would warn but not exit, and end up in a state
4153 where no controller could authenticate. Now we exit.
4154 - If we require CookieAuthentication, stop generating a new cookie
4155 every time we change any piece of our config.
4156 - Refuse to start with certain directory authority keys, and
4157 encourage people using them to stop.
4158 - Terminate multi-line control events properly. Original patch
4160 - Fix a minor memory leak when we fail to find enough suitable
4161 servers to choose a circuit.
4162 - Stop leaking part of the descriptor when we run into a particularly
4163 unparseable piece of it.
4166 Changes in version 0.2.0.6-alpha - 2007-08-26
4167 This sixth development snapshot features a new Vidalia version in the
4168 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
4169 the ControlPort in the default configuration, which addresses important
4172 In addition, this snapshot fixes major load balancing problems
4173 with path selection, which should speed things up a lot once many
4174 people have upgraded. The directory authorities also use a new
4175 mean-time-between-failure approach to tracking which servers are stable,
4176 rather than just looking at the most recent uptime.
4178 o New directory authorities:
4179 - Set up Tonga as the default bridge directory authority.
4182 - Directory authorities now track servers by weighted
4183 mean-times-between-failures. When we have 4 or more days of data,
4184 use measured MTBF rather than declared uptime to decide whether
4185 to call a router Stable. Implements proposal 108.
4187 o Major bugfixes (load balancing):
4188 - When choosing nodes for non-guard positions, weight guards
4189 proportionally less, since they already have enough load. Patch
4191 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
4192 will allow fast Tor servers to get more attention.
4193 - When we're upgrading from an old Tor version, forget our current
4194 guards and pick new ones according to the new weightings. These
4195 three load balancing patches could raise effective network capacity
4196 by a factor of four. Thanks to Mike Perry for measurements.
4198 o Major bugfixes (descriptor parsing):
4199 - Handle unexpected whitespace better in malformed descriptors. Bug
4200 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
4203 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
4204 GETINFO for Torstat to use until it can switch to using extrainfos.
4205 - Optionally (if built with -DEXPORTMALLINFO) export the output
4206 of mallinfo via http, as tor/mallinfo.txt. Only accessible
4210 - Do not intermix bridge routers with controller-added
4211 routers. (Bugfix on 0.2.0.x)
4212 - Do not fail with an assert when accept() returns an unexpected
4213 address family. Addresses but does not wholly fix bug 483. (Bugfix
4215 - Let directory authorities startup even when they can't generate
4216 a descriptor immediately, e.g. because they don't know their
4218 - Stop putting the authentication cookie in a file called "0"
4219 in your working directory if you don't specify anything for the
4220 new CookieAuthFile option. Reported by Matt Edman.
4221 - Make it possible to read the PROTOCOLINFO response in a way that
4222 conforms to our control-spec. Reported by Matt Edman.
4223 - Fix a minor memory leak when we fail to find enough suitable
4224 servers to choose a circuit. Bugfix on 0.1.2.x.
4225 - Stop leaking part of the descriptor when we run into a particularly
4226 unparseable piece of it. Bugfix on 0.1.2.x.
4227 - Unmap the extrainfo cache file on exit.
4230 Changes in version 0.2.0.5-alpha - 2007-08-19
4231 This fifth development snapshot fixes compilation on Windows again;
4232 fixes an obnoxious client-side bug that slowed things down and put
4233 extra load on the network; gets us closer to using the v3 directory
4234 voting scheme; makes it easier for Tor controllers to use cookie-based
4235 authentication; and fixes a variety of other bugs.
4238 - Version 1 directories are no longer generated in full. Instead,
4239 authorities generate and serve "stub" v1 directories that list
4240 no servers. This will stop Tor versions 0.1.0.x and earlier from
4241 working, but (for security reasons) nobody should be running those
4244 o Major bugfixes (compilation, 0.2.0.x):
4245 - Try to fix Win32 compilation again: improve checking for IPv6 types.
4246 - Try to fix MSVC compilation: build correctly on platforms that do
4247 not define s6_addr16 or s6_addr32.
4248 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
4251 o Major bugfixes (stream expiration):
4252 - Expire not-yet-successful application streams in all cases if
4253 they've been around longer than SocksTimeout. Right now there are
4254 some cases where the stream will live forever, demanding a new
4255 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
4258 o Minor features (directory servers):
4259 - When somebody requests a list of statuses or servers, and we have
4260 none of those, return a 404 rather than an empty 200.
4262 o Minor features (directory voting):
4263 - Store v3 consensus status consensuses on disk, and reload them
4266 o Minor features (security):
4267 - Warn about unsafe ControlPort configurations.
4268 - Refuse to start with certain directory authority keys, and
4269 encourage people using them to stop.
4271 o Minor features (controller):
4272 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
4273 is valid before any authentication has been received. It tells
4274 a controller what kind of authentication is expected, and what
4275 protocol is spoken. Implements proposal 119.
4276 - New config option CookieAuthFile to choose a new location for the
4277 cookie authentication file, and config option
4278 CookieAuthFileGroupReadable to make it group-readable.
4280 o Minor features (unit testing):
4281 - Add command-line arguments to unit-test executable so that we can
4282 invoke any chosen test from the command line rather than having
4283 to run the whole test suite at once; and so that we can turn on
4284 logging for the unit tests.
4286 o Minor bugfixes (on 0.1.2.x):
4287 - If we require CookieAuthentication but we fail to write the
4288 cookie file, we would warn but not exit, and end up in a state
4289 where no controller could authenticate. Now we exit.
4290 - If we require CookieAuthentication, stop generating a new cookie
4291 every time we change any piece of our config.
4292 - When loading bandwidth history, do not believe any information in
4293 the future. Fixes bug 434.
4294 - When loading entry guard information, do not believe any information
4296 - When we have our clock set far in the future and generate an
4297 onion key, then re-set our clock to be correct, we should not stop
4298 the onion key from getting rotated.
4299 - Clean up torrc sample config file.
4300 - Do not automatically run configure from autogen.sh. This
4301 non-standard behavior tended to annoy people who have built other
4304 o Minor bugfixes (on 0.2.0.x):
4305 - Fix a bug with AutomapHostsOnResolve that would always cause
4306 the second request to fail. Bug reported by Kate. Bugfix on
4308 - Fix a bug in ADDRMAP controller replies that would sometimes
4309 try to print a NULL. Patch from tup.
4310 - Read v3 directory authority keys from the right location.
4311 - Numerous bugfixes to directory voting code.
4314 Changes in version 0.1.2.16 - 2007-08-01
4315 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
4316 remote attacker in certain situations to rewrite the user's torrc
4317 configuration file. This can completely compromise anonymity of users
4318 in most configurations, including those running the Vidalia bundles,
4319 TorK, etc. Or worse.
4321 o Major security fixes:
4322 - Close immediately after missing authentication on control port;
4323 do not allow multiple authentication attempts.
4326 Changes in version 0.2.0.4-alpha - 2007-08-01
4327 This fourth development snapshot fixes a critical security vulnerability
4328 for most users, specifically those running Vidalia, TorK, etc. Everybody
4329 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
4331 o Major security fixes:
4332 - Close immediately after missing authentication on control port;
4333 do not allow multiple authentication attempts.
4335 o Major bugfixes (compilation):
4336 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
4339 o Minor features (performance):
4340 - Be even more aggressive about releasing RAM from small
4341 empty buffers. Thanks to our free-list code, this shouldn't be too
4342 performance-intensive.
4343 - Disable sentinel-based debugging for buffer code: we squashed all
4344 the bugs that this was supposed to detect a long time ago, and
4345 now its only effect is to change our buffer sizes from nice
4346 powers of two (which platform mallocs tend to like) to values
4347 slightly over powers of two (which make some platform mallocs sad).
4348 - Log malloc statistics from mallinfo() on platforms where it
4352 Changes in version 0.2.0.3-alpha - 2007-07-29
4353 This third development snapshot introduces new experimental
4354 blocking-resistance features and a preliminary version of the v3
4355 directory voting design, and includes many other smaller features
4359 - The first pieces of our "bridge" design for blocking-resistance
4360 are implemented. People can run bridge directory authorities;
4361 people can run bridges; and people can configure their Tor clients
4362 with a set of bridges to use as the first hop into the Tor network.
4363 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
4365 - Create listener connections before we setuid to the configured
4366 User and Group. Now non-Windows users can choose port values
4367 under 1024, start Tor as root, and have Tor bind those ports
4368 before it changes to another UID. (Windows users could already
4370 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
4371 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
4372 on "vserver" accounts. (Patch from coderman.)
4373 - Be even more aggressive about separating local traffic from relayed
4374 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
4376 o Major features (experimental):
4377 - First cut of code for "v3 dir voting": directory authorities will
4378 vote on a common network status document rather than each publishing
4379 their own opinion. This code needs more testing and more corner-case
4380 handling before it's ready for use.
4383 - Directory authorities now call routers Fast if their bandwidth is
4384 at least 100KB/s, and consider their bandwidth adequate to be a
4385 Guard if it is at least 250KB/s, no matter the medians. This fix
4386 complements proposal 107. [Bugfix on 0.1.2.x]
4387 - Directory authorities now never mark more than 3 servers per IP as
4388 Valid and Running. (Implements proposal 109, by Kevin Bauer and
4390 - Minor change to organizationName and commonName generation
4391 procedures in TLS certificates during Tor handshakes, to invalidate
4392 some earlier censorware approaches. This is not a long-term
4393 solution, but applying it will give us a bit of time to look into
4394 the epidemiology of countermeasures as they spread.
4396 o Major bugfixes (directory):
4397 - Rewrite directory tokenization code to never run off the end of
4398 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
4400 o Minor features (controller):
4401 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
4402 match requests to applications. (Patch from Robert Hogan.)
4403 - Report address and port correctly on connections to DNSPort. (Patch
4405 - Add a RESOLVE command to launch hostname lookups. (Original patch
4407 - Add GETINFO status/enough-dir-info to let controllers tell whether
4408 Tor has downloaded sufficient directory information. (Patch
4410 - You can now use the ControlSocket option to tell Tor to listen for
4411 controller connections on Unix domain sockets on systems that
4412 support them. (Patch from Peter Palfrader.)
4413 - STREAM NEW events are generated for DNSPort requests and for
4414 tunneled directory connections. (Patch from Robert Hogan.)
4415 - New "GETINFO address-mappings/*" command to get address mappings
4416 with expiry information. "addr-mappings/*" is now deprecated.
4419 o Minor features (misc):
4420 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
4422 - The tor-gencert tool for v3 directory authorities now creates all
4423 files as readable to the file creator only, and write-protects
4424 the authority identity key.
4425 - When dumping memory usage, list bytes used in buffer memory
4427 - When running with dmalloc, dump more stats on hup and on exit.
4428 - Directory authorities now fail quickly and (relatively) harmlessly
4429 if they generate a network status document that is somehow
4432 o Traffic load balancing improvements:
4433 - If exit bandwidth ever exceeds one third of total bandwidth, then
4434 use the correct formula to weight exit nodes when choosing paths.
4435 (Based on patch from Mike Perry.)
4436 - Choose perfectly fairly among routers when choosing by bandwidth and
4437 weighting by fraction of bandwidth provided by exits. Previously, we
4438 would choose with only approximate fairness, and correct ourselves
4439 if we ran off the end of the list. [Bugfix on 0.1.2.x]
4441 o Performance improvements:
4442 - Be more aggressive with freeing buffer RAM or putting it on the
4444 - Use Critical Sections rather than Mutexes for synchronizing threads
4445 on win32; Mutexes are heavier-weight, and designed for synchronizing
4448 o Deprecated and removed features:
4449 - RedirectExits is now deprecated.
4450 - Stop allowing address masks that do not correspond to bit prefixes.
4451 We have warned about these for a really long time; now it's time
4452 to reject them. (Patch from croup.)
4454 o Minor bugfixes (directory):
4455 - Fix another crash bug related to extra-info caching. (Bug found by
4456 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
4457 - Directories no longer return a "304 not modified" when they don't
4458 have the networkstatus the client asked for. Also fix a memory
4459 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
4460 - We had accidentally labelled 0.1.2.x directory servers as not
4461 suitable for begin_dir requests, and had labelled no directory
4462 servers as suitable for uploading extra-info documents. [Bugfix
4465 o Minor bugfixes (dns):
4466 - Fix a crash when DNSPort is set more than once. (Patch from Robert
4467 Hogan.) [Bugfix on 0.2.0.2-alpha]
4468 - Add DNSPort connections to the global connection list, so that we
4469 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
4471 - Fix a dangling reference that could lead to a crash when DNSPort is
4472 changed or closed (Patch from Robert Hogan.) [Bugfix on
4475 o Minor bugfixes (controller):
4476 - Provide DNS expiry times in GMT, not in local time. For backward
4477 compatibility, ADDRMAP events only provide GMT expiry in an extended
4478 field. "GETINFO address-mappings" always does the right thing.
4479 - Use CRLF line endings properly in NS events.
4480 - Terminate multi-line control events properly. (Original patch
4481 from tup.) [Bugfix on 0.1.2.x-alpha]
4482 - Do not include spaces in SOURCE_ADDR fields in STREAM
4483 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
4486 Changes in version 0.1.2.15 - 2007-07-17
4487 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
4488 problems, fixes compilation on BSD, and fixes a variety of other
4489 bugs. Everybody should upgrade.
4491 o Major bugfixes (compilation):
4492 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
4494 o Major bugfixes (crashes):
4495 - Try even harder not to dereference the first character after
4496 an mmap(). Reported by lodger.
4497 - Fix a crash bug in directory authorities when we re-number the
4498 routerlist while inserting a new router.
4499 - When the cached-routers file is an even multiple of the page size,
4500 don't run off the end and crash. (Fixes bug 455; based on idea
4502 - Fix eventdns.c behavior on Solaris: It is critical to include
4503 orconfig.h _before_ sys/types.h, so that we can get the expected
4504 definition of _FILE_OFFSET_BITS.
4506 o Major bugfixes (security):
4507 - Fix a possible buffer overrun when using BSD natd support. Bug
4509 - When sending destroy cells from a circuit's origin, don't include
4510 the reason for tearing down the circuit. The spec says we didn't,
4511 and now we actually don't. Reported by lodger.
4512 - Keep streamids from different exits on a circuit separate. This
4513 bug may have allowed other routers on a given circuit to inject
4514 cells into streams. Reported by lodger; fixes bug 446.
4515 - If there's a never-before-connected-to guard node in our list,
4516 never choose any guards past it. This way we don't expand our
4517 guard list unless we need to.
4519 o Minor bugfixes (guard nodes):
4520 - Weight guard selection by bandwidth, so that low-bandwidth nodes
4521 don't get overused as guards.
4523 o Minor bugfixes (directory):
4524 - Correctly count the number of authorities that recommend each
4525 version. Previously, we were under-counting by 1.
4526 - Fix a potential crash bug when we load many server descriptors at
4527 once and some of them make others of them obsolete. Fixes bug 458.
4529 o Minor bugfixes (hidden services):
4530 - Stop tearing down the whole circuit when the user asks for a
4531 connection to a port that the hidden service didn't configure.
4534 o Minor bugfixes (misc):
4535 - On Windows, we were preventing other processes from reading
4536 cached-routers while Tor was running. Reported by janbar.
4537 - Fix a possible (but very unlikely) bug in picking routers by
4538 bandwidth. Add a log message to confirm that it is in fact
4539 unlikely. Patch from lodger.
4540 - Backport a couple of memory leak fixes.
4541 - Backport miscellaneous cosmetic bugfixes.
4544 Changes in version 0.2.0.2-alpha - 2007-06-02
4545 o Major bugfixes on 0.2.0.1-alpha:
4546 - Fix an assertion failure related to servers without extra-info digests.
4547 Resolves bugs 441 and 442.
4549 o Minor features (directory):
4550 - Support "If-Modified-Since" when answering HTTP requests for
4551 directories, running-routers documents, and network-status documents.
4552 (There's no need to support it for router descriptors, since those
4553 are downloaded by descriptor digest.)
4555 o Minor build issues:
4556 - Clear up some MIPSPro compiler warnings.
4557 - When building from a tarball on a machine that happens to have SVK
4558 installed, report the micro-revision as whatever version existed
4559 in the tarball, not as "x".
4562 Changes in version 0.2.0.1-alpha - 2007-06-01
4563 This early development snapshot provides new features for people running
4564 Tor as both a client and a server (check out the new RelayBandwidth
4565 config options); lets Tor run as a DNS proxy; and generally moves us
4566 forward on a lot of fronts.
4568 o Major features, server usability:
4569 - New config options RelayBandwidthRate and RelayBandwidthBurst:
4570 a separate set of token buckets for relayed traffic. Right now
4571 relayed traffic is defined as answers to directory requests, and
4572 OR connections that don't have any local circuits on them.
4574 o Major features, client usability:
4575 - A client-side DNS proxy feature to replace the need for
4576 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
4577 for DNS requests on port 9999, use the Tor network to resolve them
4578 anonymously, and send the reply back like a regular DNS server.
4579 The code still only implements a subset of DNS.
4580 - Make PreferTunneledDirConns and TunnelDirConns work even when
4581 we have no cached directory info. This means Tor clients can now
4582 do all of their connections protected by TLS.
4584 o Major features, performance and efficiency:
4585 - Directory authorities accept and serve "extra info" documents for
4586 routers. These documents contain fields from router descriptors
4587 that aren't usually needed, and that use a lot of excess
4588 bandwidth. Once these fields are removed from router descriptors,
4589 the bandwidth savings should be about 60%. [Partially implements
4591 - Servers upload extra-info documents to any authority that accepts
4592 them. Authorities (and caches that have been configured to download
4593 extra-info documents) download them as needed. [Partially implements
4595 - Change the way that Tor buffers data that it is waiting to write.
4596 Instead of queueing data cells in an enormous ring buffer for each
4597 client->OR or OR->OR connection, we now queue cells on a separate
4598 queue for each circuit. This lets us use less slack memory, and
4599 will eventually let us be smarter about prioritizing different kinds
4601 - Use memory pools to allocate cells with better speed and memory
4602 efficiency, especially on platforms where malloc() is inefficient.
4603 - Stop reading on edge connections when their corresponding circuit
4604 buffers are full; start again as the circuits empty out.
4606 o Major features, other:
4607 - Add an HSAuthorityRecordStats option that hidden service authorities
4608 can use to track statistics of overall hidden service usage without
4609 logging information that would be very useful to an attacker.
4610 - Start work implementing multi-level keys for directory authorities:
4611 Add a standalone tool to generate key certificates. (Proposal 103.)
4614 - Directory authorities now call routers Stable if they have an
4615 uptime of at least 30 days, even if that's not the median uptime
4616 in the network. Implements proposal 107, suggested by Kevin Bauer
4619 o Minor fixes (resource management):
4620 - Count the number of open sockets separately from the number
4621 of active connection_t objects. This will let us avoid underusing
4622 our allocated connection limit.
4623 - We no longer use socket pairs to link an edge connection to an
4624 anonymous directory connection or a DirPort test connection.
4625 Instead, we track the link internally and transfer the data
4626 in-process. This saves two sockets per "linked" connection (at the
4627 client and at the server), and avoids the nasty Windows socketpair()
4629 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
4630 for every single inactive connection_t. Free items from the
4631 4k/16k-buffer free lists when they haven't been used for a while.
4633 o Minor features (build):
4634 - Make autoconf search for libevent, openssl, and zlib consistently.
4635 - Update deprecated macros in configure.in.
4636 - When warning about missing headers, tell the user to let us
4637 know if the compile succeeds anyway, so we can downgrade the
4639 - Include the current subversion revision as part of the version
4640 string: either fetch it directly if we're in an SVN checkout, do
4641 some magic to guess it if we're in an SVK checkout, or use
4642 the last-detected version if we're building from a .tar.gz.
4643 Use this version consistently in log messages.
4645 o Minor features (logging):
4646 - Always prepend "Bug: " to any log message about a bug.
4647 - Put a platform string (e.g. "Linux i686") in the startup log
4648 message, so when people paste just their logs, we know if it's
4649 OpenBSD or Windows or what.
4650 - When logging memory usage, break down memory used in buffers by
4653 o Minor features (directory system):
4654 - New config option V2AuthoritativeDirectory that all directory
4655 authorities should set. This will let future authorities choose
4656 not to serve V2 directory information.
4657 - Directory authorities allow multiple router descriptors and/or extra
4658 info documents to be uploaded in a single go. This will make
4659 implementing proposal 104 simpler.
4661 o Minor features (controller):
4662 - Add a new config option __DisablePredictedCircuits designed for
4663 use by the controller, when we don't want Tor to build any circuits
4665 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
4666 so we can exit from the middle of the circuit.
4667 - Implement "getinfo status/circuit-established".
4668 - Implement "getinfo status/version/..." so a controller can tell
4669 whether the current version is recommended, and whether any versions
4670 are good, and how many authorities agree. (Patch from shibz.)
4672 o Minor features (hidden services):
4673 - Allow multiple HiddenServicePort directives with the same virtual
4674 port; when they occur, the user is sent round-robin to one
4675 of the target ports chosen at random. Partially fixes bug 393 by
4676 adding limited ad-hoc round-robining.
4678 o Minor features (other):
4680 - Add a new AutomapHostsOnResolve option: when it is enabled, any
4681 resolve request for hosts matching a given pattern causes Tor to
4682 generate an internal virtual address mapping for that host. This
4683 allows DNSPort to work sensibly with hidden service users. By
4684 default, .exit and .onion addresses are remapped; the list of
4685 patterns can be reconfigured with AutomapHostsSuffixes.
4686 - Add an "-F" option to tor-resolve to force a resolve for a .onion
4687 address. Thanks to the AutomapHostsOnResolve option, this is no
4688 longer a completely silly thing to do.
4689 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
4690 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
4691 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
4692 minus 1 byte: the actual maximum declared bandwidth.
4695 - Removed support for the old binary "version 0" controller protocol.
4696 This has been deprecated since 0.1.1, and warnings have been issued
4697 since 0.1.2. When we encounter a v0 control message, we now send
4698 back an error and close the connection.
4699 - Remove the old "dns worker" server DNS code: it hasn't been default
4700 since 0.1.2.2-alpha, and all the servers seem to be using the new
4703 o Minor bugfixes (portability):
4704 - Even though Windows is equally happy with / and \ as path separators,
4705 try to use \ consistently on Windows and / consistently on Unix: it
4706 makes the log messages nicer.
4707 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
4708 - Read resolv.conf files correctly on platforms where read() returns
4709 partial results on small file reads.
4711 o Minor bugfixes (directory):
4712 - Correctly enforce that elements of directory objects do not appear
4713 more often than they are allowed to appear.
4714 - When we are reporting the DirServer line we just parsed, we were
4715 logging the second stanza of the key fingerprint, not the first.
4717 o Minor bugfixes (logging):
4718 - When we hit an EOF on a log (probably because we're shutting down),
4719 don't try to remove the log from the list: just mark it as
4720 unusable. (Bulletproofs against bug 222.)
4722 o Minor bugfixes (other):
4723 - In the exitlist script, only consider the most recently published
4724 server descriptor for each server. Also, when the user requests
4725 a list of servers that _reject_ connections to a given address,
4726 explicitly exclude the IPs that also have servers that accept
4727 connections to that address. (Resolves bug 405.)
4728 - Stop allowing hibernating servers to be "stable" or "fast".
4729 - On Windows, we were preventing other processes from reading
4730 cached-routers while Tor was running. (Reported by janbar)
4731 - Make the NodeFamilies config option work. (Reported by
4732 lodger -- it has never actually worked, even though we added it
4734 - Check return values from pthread_mutex functions.
4735 - Don't save non-general-purpose router descriptors to the disk cache,
4736 because we have no way of remembering what their purpose was when
4738 - Add even more asserts to hunt down bug 417.
4739 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
4740 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
4741 Add a log message to confirm that it is in fact unlikely.
4743 o Minor bugfixes (controller):
4744 - Make 'getinfo fingerprint' return a 551 error if we're not a
4745 server, so we match what the control spec claims we do. Reported
4747 - Fix a typo in an error message when extendcircuit fails that
4748 caused us to not follow the \r\n-based delimiter protocol. Reported
4751 o Code simplifications and refactoring:
4752 - Stop passing around circuit_t and crypt_path_t pointers that are
4753 implicit in other procedure arguments.
4754 - Drop the old code to choke directory connections when the
4755 corresponding OR connections got full: thanks to the cell queue
4756 feature, OR conns don't get full any more.
4757 - Make dns_resolve() handle attaching connections to circuits
4758 properly, so the caller doesn't have to.
4759 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
4760 - Keep the connection array as a dynamic smartlist_t, rather than as
4761 a fixed-sized array. This is important, as the number of connections
4762 is becoming increasingly decoupled from the number of sockets.
4765 Changes in version 0.1.2.14 - 2007-05-25
4766 Tor 0.1.2.14 changes the addresses of two directory authorities (this
4767 change especially affects those who serve or use hidden services),
4768 and fixes several other crash- and security-related bugs.
4770 o Directory authority changes:
4771 - Two directory authorities (moria1 and moria2) just moved to new
4772 IP addresses. This change will particularly affect those who serve
4773 or use hidden services.
4775 o Major bugfixes (crashes):
4776 - If a directory server runs out of space in the connection table
4777 as it's processing a begin_dir request, it will free the exit stream
4778 but leave it attached to the circuit, leading to unpredictable
4779 behavior. (Reported by seeess, fixes bug 425.)
4780 - Fix a bug in dirserv_remove_invalid() that would cause authorities
4781 to corrupt memory under some really unlikely scenarios.
4782 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
4783 - Avoid segfaults when reading from mmaped descriptor file. (Reported
4786 o Major bugfixes (security):
4787 - When choosing an entry guard for a circuit, avoid using guards
4788 that are in the same family as the chosen exit -- not just guards
4789 that are exactly the chosen exit. (Reported by lodger.)
4791 o Major bugfixes (resource management):
4792 - If a directory authority is down, skip it when deciding where to get
4793 networkstatus objects or descriptors. Otherwise we keep asking
4794 every 10 seconds forever. Fixes bug 384.
4795 - Count it as a failure if we fetch a valid network-status but we
4796 don't want to keep it. Otherwise we'll keep fetching it and keep
4797 not wanting to keep it. Fixes part of bug 422.
4798 - If all of our dirservers have given us bad or no networkstatuses
4799 lately, then stop hammering them once per minute even when we
4800 think they're failed. Fixes another part of bug 422.
4803 - Actually set the purpose correctly for descriptors inserted with
4805 - When we have k non-v2 authorities in our DirServer config,
4806 we ignored the last k authorities in the list when updating our
4808 - Correctly back-off from requesting router descriptors that we are
4809 having a hard time downloading.
4810 - Read resolv.conf files correctly on platforms where read() returns
4811 partial results on small file reads.
4812 - Don't rebuild the entire router store every time we get 32K of
4813 routers: rebuild it when the journal gets very large, or when
4814 the gaps in the store get very large.
4817 - When routers publish SVN revisions in their router descriptors,
4818 authorities now include those versions correctly in networkstatus
4820 - Warn when using a version of libevent before 1.3b to run a server on
4821 OSX or BSD: these versions interact badly with userspace threads.
4824 Changes in version 0.1.2.13 - 2007-04-24
4825 This release features some major anonymity fixes, such as safer path
4826 selection; better client performance; faster bootstrapping, better
4827 address detection, and better DNS support for servers; write limiting as
4828 well as read limiting to make servers easier to run; and a huge pile of
4829 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
4831 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
4832 of the Freenode IRC network, remembering his patience and vision for
4833 free speech on the Internet.
4836 - Fix a memory leak when we ask for "all" networkstatuses and we
4837 get one we don't recognize.
4838 - Add more asserts to hunt down bug 417.
4839 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
4842 Changes in version 0.1.2.12-rc - 2007-03-16
4844 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
4845 directory information requested inside Tor connections (i.e. via
4846 begin_dir cells). It only triggered when the same connection was
4847 serving other data at the same time. Reported by seeess.
4850 - When creating a circuit via the controller, send a 'launched'
4851 event when we're done, so we follow the spec better.
4854 Changes in version 0.1.2.11-rc - 2007-03-15
4855 o Minor bugfixes (controller), reported by daejees:
4856 - Correct the control spec to match how the code actually responds
4857 to 'getinfo addr-mappings/*'.
4858 - The control spec described a GUARDS event, but the code
4859 implemented a GUARD event. Standardize on GUARD, but let people
4863 Changes in version 0.1.2.10-rc - 2007-03-07
4864 o Major bugfixes (Windows):
4865 - Do not load the NT services library functions (which may not exist)
4866 just to detect if we're a service trying to shut down. Now we run
4867 on Win98 and friends again.
4869 o Minor bugfixes (other):
4870 - Clarify a couple of log messages.
4871 - Fix a misleading socks5 error number.
4874 Changes in version 0.1.2.9-rc - 2007-03-02
4875 o Major bugfixes (Windows):
4876 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
4877 of the usual GCC "%llu". This prevents a bug when saving 64-bit
4878 int configuration values: the high-order 32 bits would get
4879 truncated. In particular, we were being bitten by the default
4880 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
4881 and maybe also bug 397.)
4883 o Minor bugfixes (performance):
4884 - Use OpenSSL's AES implementation on platforms where it's faster.
4885 This could save us as much as 10% CPU usage.
4887 o Minor bugfixes (server):
4888 - Do not rotate onion key immediately after setting it for the first
4891 o Minor bugfixes (directory authorities):
4892 - Stop calling servers that have been hibernating for a long time
4893 "stable". Also, stop letting hibernating or obsolete servers affect
4894 uptime and bandwidth cutoffs.
4895 - Stop listing hibernating servers in the v1 directory.
4897 o Minor bugfixes (hidden services):
4898 - Upload hidden service descriptors slightly less often, to reduce
4899 load on authorities.
4901 o Minor bugfixes (other):
4902 - Fix an assert that could trigger if a controller quickly set then
4903 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
4904 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
4906 - Fix a potential race condition in the rpm installer. Found by
4908 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
4909 of 2 as indicating that the server is completely bad; it sometimes
4910 means that the server is just bad for the request in question. (may fix
4911 the last of bug 326.)
4912 - Disable encrypted directory connections when we don't have a server
4913 descriptor for the destination. We'll get this working again in
4917 Changes in version 0.1.2.8-beta - 2007-02-26
4918 o Major bugfixes (crashes):
4919 - Stop crashing when the controller asks us to resetconf more than
4920 one config option at once. (Vidalia 0.0.11 does this.)
4921 - Fix a crash that happened on Win98 when we're given command-line
4922 arguments: don't try to load NT service functions from advapi32.dll
4923 except when we need them. (Bug introduced in 0.1.2.7-alpha;
4925 - Fix a longstanding obscure crash bug that could occur when
4926 we run out of DNS worker processes. (Resolves bug 390.)
4928 o Major bugfixes (hidden services):
4929 - Correctly detect whether hidden service descriptor downloads are
4930 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
4932 o Major bugfixes (accounting):
4933 - When we start during an accounting interval before it's time to wake
4934 up, remember to wake up at the correct time. (May fix bug 342.)
4936 o Minor bugfixes (controller):
4937 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
4938 clear the corresponding on_circuit variable, and remember later
4939 that we don't need to send a redundant CLOSED event. (Resolves part
4941 - Report events where a resolve succeeded or where we got a socks
4942 protocol error correctly, rather than calling both of them
4944 - Change reported stream target addresses to IP consistently when
4945 we finally get the IP from an exit node.
4946 - Send log messages to the controller even if they happen to be very
4949 o Minor bugfixes (other):
4950 - Display correct results when reporting which versions are
4951 recommended, and how recommended they are. (Resolves bug 383.)
4952 - Improve our estimates for directory bandwidth to be less random:
4953 guess that an unrecognized directory will have the average bandwidth
4954 from all known directories, not that it will have the average
4955 bandwidth from those directories earlier than it on the list.
4956 - If we start a server with ClientOnly 1, then set ClientOnly to 0
4957 and hup, stop triggering an assert based on an empty onion_key.
4958 - On platforms with no working mmap() equivalent, don't warn the
4959 user when cached-routers doesn't exist.
4960 - Warn the user when mmap() [or its equivalent] fails for some reason
4961 other than file-not-found.
4962 - Don't warn the user when cached-routers.new doesn't exist: that's
4963 perfectly fine when starting up for the first time.
4964 - When EntryNodes are configured, rebuild the guard list to contain,
4965 in order: the EntryNodes that were guards before; the rest of the
4966 EntryNodes; the nodes that were guards before.
4967 - Mask out all signals in sub-threads; only the libevent signal
4968 handler should be processing them. This should prevent some crashes
4969 on some machines using pthreads. (Patch from coderman.)
4970 - Fix switched arguments on memset in the implementation of
4971 tor_munmap() for systems with no mmap() call.
4972 - When Tor receives a router descriptor that it asked for, but
4973 no longer wants (because it has received fresh networkstatuses
4974 in the meantime), do not warn the user. Cache the descriptor if
4975 we're a cache; drop it if we aren't.
4976 - Make earlier entry guards _really_ get retried when the network
4978 - On a malformed DNS reply, always give an error to the corresponding
4980 - Build with recent libevents on platforms that do not define the
4981 nonstandard types "u_int8_t" and friends.
4983 o Minor features (controller):
4984 - Warn the user when an application uses the obsolete binary v0
4985 control protocol. We're planning to remove support for it during
4986 the next development series, so it's good to give people some
4988 - Add STREAM_BW events to report per-entry-stream bandwidth
4989 use. (Patch from Robert Hogan.)
4990 - Rate-limit SIGNEWNYM signals in response to controllers that
4991 impolitely generate them for every single stream. (Patch from
4992 mwenge; closes bug 394.)
4993 - Make REMAP stream events have a SOURCE (cache or exit), and
4994 make them generated in every case where we get a successful
4995 connected or resolved cell.
4997 o Minor bugfixes (performance):
4998 - Call router_have_min_dir_info half as often. (This is showing up in
4999 some profiles, but not others.)
5000 - When using GCC, make log_debug never get called at all, and its
5001 arguments never get evaluated, when no debug logs are configured.
5002 (This is showing up in some profiles, but not others.)
5005 - Remove some never-implemented options. Mark PathlenCoinWeight as
5007 - Implement proposal 106: Stop requiring clients to have well-formed
5008 certificates; stop checking nicknames in certificates. (Clients
5009 have certificates so that they can look like Tor servers, but in
5010 the future we might want to allow them to look like regular TLS
5011 clients instead. Nicknames in certificates serve no purpose other
5012 than making our protocol easier to recognize on the wire.)
5013 - Revise messages on handshake failure again to be even more clear about
5014 which are incoming connections and which are outgoing.
5015 - Discard any v1 directory info that's over 1 month old (for
5016 directories) or over 1 week old (for running-routers lists).
5017 - Do not warn when individual nodes in the configuration's EntryNodes,
5018 ExitNodes, etc are down: warn only when all possible nodes
5019 are down. (Fixes bug 348.)
5020 - Always remove expired routers and networkstatus docs before checking
5021 whether we have enough information to build circuits. (Fixes
5023 - Put a lower-bound on MaxAdvertisedBandwidth.
5026 Changes in version 0.1.2.7-alpha - 2007-02-06
5027 o Major bugfixes (rate limiting):
5028 - Servers decline directory requests much more aggressively when
5029 they're low on bandwidth. Otherwise they end up queueing more and
5030 more directory responses, which can't be good for latency.
5031 - But never refuse directory requests from local addresses.
5032 - Fix a memory leak when sending a 503 response for a networkstatus
5034 - Be willing to read or write on local connections (e.g. controller
5035 connections) even when the global rate limiting buckets are empty.
5036 - If our system clock jumps back in time, don't publish a negative
5037 uptime in the descriptor. Also, don't let the global rate limiting
5038 buckets go absurdly negative.
5039 - Flush local controller connection buffers periodically as we're
5040 writing to them, so we avoid queueing 4+ megabytes of data before
5043 o Major bugfixes (NT services):
5044 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
5045 command-line flag so that admins can override the default by saying
5046 "tor --service install --user "SomeUser"". This will not affect
5047 existing installed services. Also, warn the user that the service
5048 will look for its configuration file in the service user's
5049 %appdata% directory. (We can't do the 'hardwire the user's appdata
5050 directory' trick any more, since we may not have read access to that
5053 o Major bugfixes (other):
5054 - Previously, we would cache up to 16 old networkstatus documents
5055 indefinitely, if they came from nontrusted authorities. Now we
5056 discard them if they are more than 10 days old.
5057 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
5059 - Detect and reject malformed DNS responses containing circular
5061 - If exits are rare enough that we're not marking exits as guards,
5062 ignore exit bandwidth when we're deciding the required bandwidth
5064 - When we're handling a directory connection tunneled over Tor,
5065 don't fill up internal memory buffers with all the data we want
5066 to tunnel; instead, only add it if the OR connection that will
5067 eventually receive it has some room for it. (This can lead to
5068 slowdowns in tunneled dir connections; a better solution will have
5071 o Minor bugfixes (dns):
5072 - Add some defensive programming to eventdns.c in an attempt to catch
5073 possible memory-stomping bugs.
5074 - Detect and reject DNS replies containing IPv4 or IPv6 records with
5075 an incorrect number of bytes. (Previously, we would ignore the
5077 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
5078 in the correct order, and doesn't crash.
5079 - Free memory held in recently-completed DNS lookup attempts on exit.
5080 This was not a memory leak, but may have been hiding memory leaks.
5081 - Handle TTL values correctly on reverse DNS lookups.
5082 - Treat failure to parse resolv.conf as an error.
5084 o Minor bugfixes (other):
5085 - Fix crash with "tor --list-fingerprint" (reported by seeess).
5086 - When computing clock skew from directory HTTP headers, consider what
5087 time it was when we finished asking for the directory, not what
5089 - Expire socks connections if they spend too long waiting for the
5090 handshake to finish. Previously we would let them sit around for
5091 days, if the connecting application didn't close them either.
5092 - And if the socks handshake hasn't started, don't send a
5093 "DNS resolve socks failed" handshake reply; just close it.
5094 - Stop using C functions that OpenBSD's linker doesn't like.
5095 - Don't launch requests for descriptors unless we have networkstatuses
5096 from at least half of the authorities. This delays the first
5097 download slightly under pathological circumstances, but can prevent
5098 us from downloading a bunch of descriptors we don't need.
5099 - Do not log IPs with TLS failures for incoming TLS
5100 connections. (Fixes bug 382.)
5101 - If the user asks to use invalid exit nodes, be willing to use
5103 - Stop using the reserved ac_cv namespace in our configure script.
5104 - Call stat() slightly less often; use fstat() when possible.
5105 - Refactor the way we handle pending circuits when an OR connection
5106 completes or fails, in an attempt to fix a rare crash bug.
5107 - Only rewrite a conn's address based on X-Forwarded-For: headers
5108 if it's a parseable public IP address; and stop adding extra quotes
5109 to the resulting address.
5112 - Weight directory requests by advertised bandwidth. Now we can
5113 let servers enable write limiting but still allow most clients to
5114 succeed at their directory requests. (We still ignore weights when
5115 choosing a directory authority; I hope this is a feature.)
5118 - Create a new file ReleaseNotes which was the old ChangeLog. The
5119 new ChangeLog file now includes the summaries for all development
5121 - Check for addresses with invalid characters at the exit as well
5122 as at the client, and warn less verbosely when they fail. You can
5123 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
5124 - Adapt a patch from goodell to let the contrib/exitlist script
5125 take arguments rather than require direct editing.
5126 - Inform the server operator when we decide not to advertise a
5127 DirPort due to AccountingMax enabled or a low BandwidthRate. It
5128 was confusing Zax, so now we're hopefully more helpful.
5129 - Bring us one step closer to being able to establish an encrypted
5130 directory tunnel without knowing a descriptor first. Still not
5131 ready yet. As part of the change, now assume we can use a
5132 create_fast cell if we don't know anything about a router.
5133 - Allow exit nodes to use nameservers running on ports other than 53.
5134 - Servers now cache reverse DNS replies.
5135 - Add an --ignore-missing-torrc command-line option so that we can
5136 get the "use sensible defaults if the configuration file doesn't
5137 exist" behavior even when specifying a torrc location on the command
5140 o Minor features (controller):
5141 - Track reasons for OR connection failure; make these reasons
5142 available via the controller interface. (Patch from Mike Perry.)
5143 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
5144 can learn when clients are sending malformed hostnames to Tor.
5145 - Clean up documentation for controller status events.
5146 - Add a REMAP status to stream events to note that a stream's
5147 address has changed because of a cached address or a MapAddress
5151 Changes in version 0.1.2.6-alpha - 2007-01-09
5153 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
5154 connection handles more than 4 gigs in either direction, we crash.
5155 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
5156 advertised exit node, somebody might try to exit from us when
5157 we're bootstrapping and before we've built our descriptor yet.
5158 Refuse the connection rather than crashing.
5161 - Warn if we (as a server) find that we've resolved an address that we
5162 weren't planning to resolve.
5163 - Warn that using select() on any libevent version before 1.1 will be
5164 unnecessarily slow (even for select()).
5165 - Flush ERR-level controller status events just like we currently
5166 flush ERR-level log events, so that a Tor shutdown doesn't prevent
5167 the controller from learning about current events.
5169 o Minor features (more controller status events):
5170 - Implement EXTERNAL_ADDRESS server status event so controllers can
5171 learn when our address changes.
5172 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
5173 can learn when directories reject our descriptor.
5174 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
5175 can learn when a client application is speaking a non-socks protocol
5177 - Implement DANGEROUS_SOCKS client status event so controllers
5178 can learn when a client application is leaking DNS addresses.
5179 - Implement BUG general status event so controllers can learn when
5180 Tor is unhappy about its internal invariants.
5181 - Implement CLOCK_SKEW general status event so controllers can learn
5182 when Tor thinks the system clock is set incorrectly.
5183 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
5184 server status events so controllers can learn when their descriptors
5185 are accepted by a directory.
5186 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
5187 server status events so controllers can learn about Tor's progress in
5188 deciding whether it's reachable from the outside.
5189 - Implement BAD_LIBEVENT general status event so controllers can learn
5190 when we have a version/method combination in libevent that needs to
5192 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
5193 and DNS_USELESS server status events so controllers can learn
5194 about changes to DNS server status.
5196 o Minor features (directory):
5197 - Authorities no longer recommend exits as guards if this would shift
5198 too much load to the exit nodes.
5201 Changes in version 0.1.2.5-alpha - 2007-01-06
5203 - Enable write limiting as well as read limiting. Now we sacrifice
5204 capacity if we're pushing out lots of directory traffic, rather
5205 than overrunning the user's intended bandwidth limits.
5206 - Include TLS overhead when counting bandwidth usage; previously, we
5207 would count only the bytes sent over TLS, but not the bytes used
5209 - Support running the Tor service with a torrc not in the same
5210 directory as tor.exe and default to using the torrc located in
5211 the %appdata%\Tor\ of the user who installed the service. Patch
5213 - Servers now check for the case when common DNS requests are going to
5214 wildcarded addresses (i.e. all getting the same answer), and change
5215 their exit policy to reject *:* if it's happening.
5216 - Implement BEGIN_DIR cells, so we can connect to the directory
5217 server via TLS to do encrypted directory requests rather than
5218 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
5219 config options if you like.
5221 o Minor features (config and docs):
5222 - Start using the state file to store bandwidth accounting data:
5223 the bw_accounting file is now obsolete. We'll keep generating it
5224 for a while for people who are still using 0.1.2.4-alpha.
5225 - Try to batch changes to the state file so that we do as few
5226 disk writes as possible while still storing important things in
5228 - The state file and the bw_accounting file get saved less often when
5229 the AvoidDiskWrites config option is set.
5230 - Make PIDFile work on Windows (untested).
5231 - Add internal descriptions for a bunch of configuration options:
5232 accessible via controller interface and in comments in saved
5234 - Reject *:563 (NNTPS) in the default exit policy. We already reject
5235 NNTP by default, so this seems like a sensible addition.
5236 - Clients now reject hostnames with invalid characters. This should
5237 avoid some inadvertent info leaks. Add an option
5238 AllowNonRFC953Hostnames to disable this behavior, in case somebody
5239 is running a private network with hosts called @, !, and #.
5240 - Add a maintainer script to tell us which options are missing
5241 documentation: "make check-docs".
5242 - Add a new address-spec.txt document to describe our special-case
5243 addresses: .exit, .onion, and .noconnnect.
5245 o Minor features (DNS):
5246 - Ongoing work on eventdns infrastructure: now it has dns server
5247 and ipv6 support. One day Tor will make use of it.
5248 - Add client-side caching for reverse DNS lookups.
5249 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
5250 - When we change nameservers or IP addresses, reset and re-launch
5251 our tests for DNS hijacking.
5253 o Minor features (directory):
5254 - Authorities now specify server versions in networkstatus. This adds
5255 about 2% to the size of compressed networkstatus docs, and allows
5256 clients to tell which servers support BEGIN_DIR and which don't.
5257 The implementation is forward-compatible with a proposed future
5258 protocol version scheme not tied to Tor versions.
5259 - DirServer configuration lines now have an orport= option so
5260 clients can open encrypted tunnels to the authorities without
5261 having downloaded their descriptors yet. Enabled for moria1,
5262 moria2, tor26, and lefkada now in the default configuration.
5263 - Directory servers are more willing to send a 503 "busy" if they
5264 are near their write limit, especially for v1 directory requests.
5265 Now they can use their limited bandwidth for actual Tor traffic.
5266 - Clients track responses with status 503 from dirservers. After a
5267 dirserver has given us a 503, we try not to use it until an hour has
5268 gone by, or until we have no dirservers that haven't given us a 503.
5269 - When we get a 503 from a directory, and we're not a server, we don't
5270 count the failure against the total number of failures allowed
5271 for the thing we're trying to download.
5272 - Report X-Your-Address-Is correctly from tunneled directory
5273 connections; don't report X-Your-Address-Is when it's an internal
5274 address; and never believe reported remote addresses when they're
5276 - Protect against an unlikely DoS attack on directory servers.
5277 - Add a BadDirectory flag to network status docs so that authorities
5278 can (eventually) tell clients about caches they believe to be
5281 o Minor features (controller):
5282 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
5283 - Reimplement GETINFO so that info/names stays in sync with the
5285 - Implement "GETINFO fingerprint".
5286 - Implement "SETEVENTS GUARD" so controllers can get updates on
5287 entry guard status as it changes.
5289 o Minor features (clean up obsolete pieces):
5290 - Remove some options that have been deprecated since at least
5291 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
5292 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
5294 - We no longer look for identity and onion keys in "identity.key" and
5295 "onion.key" -- these were replaced by secret_id_key and
5296 secret_onion_key in 0.0.8pre1.
5297 - We no longer require unrecognized directory entries to be
5300 o Major bugfixes (security):
5301 - Stop sending the HttpProxyAuthenticator string to directory
5302 servers when directory connections are tunnelled through Tor.
5303 - Clients no longer store bandwidth history in the state file.
5304 - Do not log introduction points for hidden services if SafeLogging
5306 - When generating bandwidth history, round down to the nearest
5307 1k. When storing accounting data, round up to the nearest 1k.
5308 - When we're running as a server, remember when we last rotated onion
5309 keys, so that we will rotate keys once they're a week old even if
5310 we never stay up for a week ourselves.
5312 o Major bugfixes (other):
5313 - Fix a longstanding bug in eventdns that prevented the count of
5314 timed-out resolves from ever being reset. This bug caused us to
5315 give up on a nameserver the third time it timed out, and try it
5316 10 seconds later... and to give up on it every time it timed out
5318 - Take out the '5 second' timeout from the connection retry
5319 schedule. Now the first connect attempt will wait a full 10
5320 seconds before switching to a new circuit. Perhaps this will help
5321 a lot. Based on observations from Mike Perry.
5322 - Fix a bug on the Windows implementation of tor_mmap_file() that
5323 would prevent the cached-routers file from ever loading. Reported
5327 - Fix an assert failure when a directory authority sets
5328 AuthDirRejectUnlisted and then receives a descriptor from an
5329 unlisted router. Reported by seeess.
5330 - Avoid a double-free when parsing malformed DirServer lines.
5331 - Fix a bug when a BSD-style PF socket is first used. Patch from
5333 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
5334 to resolve an address at a given exit node even when they ask for
5336 - Servers no longer ever list themselves in their "family" line,
5337 even if configured to do so. This makes it easier to configure
5338 family lists conveniently.
5339 - When running as a server, don't fall back to 127.0.0.1 when no
5340 nameservers are configured in /etc/resolv.conf; instead, make the
5341 user fix resolv.conf or specify nameservers explicitly. (Resolves
5343 - Stop accepting certain malformed ports in configured exit policies.
5344 - Don't re-write the fingerprint file every restart, unless it has
5346 - Stop warning when a single nameserver fails: only warn when _all_ of
5347 our nameservers have failed. Also, when we only have one nameserver,
5348 raise the threshold for deciding that the nameserver is dead.
5349 - Directory authorities now only decide that routers are reachable
5350 if their identity keys are as expected.
5351 - When the user uses bad syntax in the Log config line, stop
5352 suggesting other bad syntax as a replacement.
5353 - Correctly detect ipv6 DNS capability on OpenBSD.
5355 o Minor bugfixes (controller):
5356 - Report the circuit number correctly in STREAM CLOSED events. Bug
5357 reported by Mike Perry.
5358 - Do not report bizarre values for results of accounting GETINFOs
5359 when the last second's write or read exceeds the allotted bandwidth.
5360 - Report "unrecognized key" rather than an empty string when the
5361 controller tries to fetch a networkstatus that doesn't exist.
5364 Changes in version 0.1.1.26 - 2006-12-14
5365 o Security bugfixes:
5366 - Stop sending the HttpProxyAuthenticator string to directory
5367 servers when directory connections are tunnelled through Tor.
5368 - Clients no longer store bandwidth history in the state file.
5369 - Do not log introduction points for hidden services if SafeLogging
5373 - Fix an assert failure when a directory authority sets
5374 AuthDirRejectUnlisted and then receives a descriptor from an
5375 unlisted router (reported by seeess).
5378 Changes in version 0.1.2.4-alpha - 2006-12-03
5380 - Add support for using natd; this allows FreeBSDs earlier than
5381 5.1.2 to have ipfw send connections through Tor without using
5382 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
5385 - Make all connections to addresses of the form ".noconnect"
5386 immediately get closed. This lets application/controller combos
5387 successfully test whether they're talking to the same Tor by
5388 watching for STREAM events.
5389 - Make cross.sh cross-compilation script work even when autogen.sh
5390 hasn't been run. (Patch from Michael Mohr.)
5391 - Statistics dumped by -USR2 now include a breakdown of public key
5392 operations, for profiling.
5395 - Fix a major leak when directory authorities parse their
5396 approved-routers list, a minor memory leak when we fail to pick
5397 an exit node, and a few rare leaks on errors.
5398 - Handle TransPort connections even when the server sends data before
5399 the client sends data. Previously, the connection would just hang
5400 until the client sent data. (Patch from tup based on patch from
5402 - Avoid assert failure when our cached-routers file is empty on
5406 - Don't log spurious warnings when we see a circuit close reason we
5407 don't recognize; it's probably just from a newer version of Tor.
5408 - Have directory authorities allow larger amounts of drift in uptime
5409 without replacing the server descriptor: previously, a server that
5410 restarted every 30 minutes could have 48 "interesting" descriptors
5412 - Start linking to the Tor specification and Tor reference manual
5413 correctly in the Windows installer.
5414 - Add Vidalia to the OS X uninstaller script, so when we uninstall
5415 Tor/Privoxy we also uninstall Vidalia.
5416 - Resume building on Irix64, and fix a lot of warnings from its
5418 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
5419 when we're running as a client.
5422 Changes in version 0.1.1.25 - 2006-11-04
5424 - When a client asks us to resolve (rather than connect to)
5425 an address, and we have a cached answer, give them the cached
5426 answer. Previously, we would give them no answer at all.
5427 - We were building exactly the wrong circuits when we predict
5428 hidden service requirements, meaning Tor would have to build all
5429 its circuits on demand.
5430 - If none of our live entry guards have a high uptime, but we
5431 require a guard with a high uptime, try adding a new guard before
5432 we give up on the requirement. This patch should make long-lived
5433 connections more stable on average.
5434 - When testing reachability of our DirPort, don't launch new
5435 tests when there's already one in progress -- unreachable
5436 servers were stacking up dozens of testing streams.
5438 o Security bugfixes:
5439 - When the user sends a NEWNYM signal, clear the client-side DNS
5440 cache too. Otherwise we continue to act on previous information.
5443 - Avoid a memory corruption bug when creating a hash table for
5445 - Avoid possibility of controller-triggered crash when misusing
5446 certain commands from a v0 controller on platforms that do not
5447 handle printf("%s",NULL) gracefully.
5448 - Avoid infinite loop on unexpected controller input.
5449 - Don't log spurious warnings when we see a circuit close reason we
5450 don't recognize; it's probably just from a newer version of Tor.
5451 - Add Vidalia to the OS X uninstaller script, so when we uninstall
5452 Tor/Privoxy we also uninstall Vidalia.
5455 Changes in version 0.1.2.3-alpha - 2006-10-29
5457 - Prepare for servers to publish descriptors less often: never
5458 discard a descriptor simply for being too old until either it is
5459 recommended by no authorities, or until we get a better one for
5460 the same router. Make caches consider retaining old recommended
5461 routers for even longer.
5462 - If most authorities set a BadExit flag for a server, clients
5463 don't think of it as a general-purpose exit. Clients only consider
5464 authorities that advertise themselves as listing bad exits.
5465 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
5466 headers for content, so that we can work better in the presence of
5467 caching HTTP proxies.
5468 - Allow authorities to list nodes as bad exits by fingerprint or by
5471 o Minor features, controller:
5472 - Add a REASON field to CIRC events; for backward compatibility, this
5473 field is sent only to controllers that have enabled the extended
5474 event format. Also, add additional reason codes to explain why
5475 a given circuit has been destroyed or truncated. (Patches from
5477 - Add a REMOTE_REASON field to extended CIRC events to tell the
5478 controller about why a remote OR told us to close a circuit.
5479 - Stream events also now have REASON and REMOTE_REASON fields,
5480 working much like those for circuit events.
5481 - There's now a GETINFO ns/... field so that controllers can ask Tor
5482 about the current status of a router.
5483 - A new event type "NS" to inform a controller when our opinion of
5484 a router's status has changed.
5485 - Add a GETINFO events/names and GETINFO features/names so controllers
5486 can tell which events and features are supported.
5487 - A new CLEARDNSCACHE signal to allow controllers to clear the
5488 client-side DNS cache without expiring circuits.
5490 o Security bugfixes:
5491 - When the user sends a NEWNYM signal, clear the client-side DNS
5492 cache too. Otherwise we continue to act on previous information.
5495 - Avoid sending junk to controllers or segfaulting when a controller
5496 uses EVENT_NEW_DESC with verbose nicknames.
5497 - Stop triggering asserts if the controller tries to extend hidden
5498 service circuits (reported by mwenge).
5499 - Avoid infinite loop on unexpected controller input.
5500 - When the controller does a "GETINFO network-status", tell it
5501 about even those routers whose descriptors are very old, and use
5502 long nicknames where appropriate.
5503 - Change NT service functions to be loaded on demand. This lets us
5504 build with MinGW without breaking Tor for Windows 98 users.
5505 - Do DirPort reachability tests less often, since a single test
5506 chews through many circuits before giving up.
5507 - In the hidden service example in torrc.sample, stop recommending
5508 esoteric and discouraged hidden service options.
5509 - When stopping an NT service, wait up to 10 sec for it to actually
5510 stop. (Patch from Matt Edman; resolves bug 295.)
5511 - Fix handling of verbose nicknames with ORCONN controller events:
5512 make them show up exactly when requested, rather than exactly when
5514 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
5515 printing a duplicate "$" in the keys we send (reported by mwenge).
5516 - Correctly set maximum connection limit on Cygwin. (This time
5518 - Try to detect Windows correctly when cross-compiling.
5519 - Detect the size of the routers file correctly even if it is
5520 corrupted (on systems without mmap) or not page-aligned (on systems
5521 with mmap). This bug was harmless.
5522 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
5523 to open a stream fails; now we do in more cases. This should
5524 make clients able to find a good exit faster in some cases, since
5525 unhandleable requests will now get an error rather than timing out.
5526 - Resolve two memory leaks when rebuilding the on-disk router cache
5527 (reported by fookoowa).
5528 - Clean up minor code warnings suggested by the MIPSpro C compiler,
5529 and reported by some Centos users.
5530 - Controller signals now work on non-Unix platforms that don't define
5531 SIGUSR1 and SIGUSR2 the way we expect.
5532 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
5533 values before failing, and always enables eventdns.
5534 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
5535 Try to fix this in configure.in by checking for most functions
5536 before we check for libevent.
5539 Changes in version 0.1.2.2-alpha - 2006-10-07
5541 - Make our async eventdns library on-by-default for Tor servers,
5542 and plan to deprecate the separate dnsworker threads.
5543 - Add server-side support for "reverse" DNS lookups (using PTR
5544 records so clients can determine the canonical hostname for a given
5545 IPv4 address). Only supported by servers using eventdns; servers
5546 now announce in their descriptors whether they support eventdns.
5547 - Specify and implement client-side SOCKS5 interface for reverse DNS
5548 lookups (see doc/socks-extensions.txt).
5549 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
5550 connect to directory servers through Tor. Previously, clients needed
5551 to find Tor exits to make private connections to directory servers.
5552 - Avoid choosing Exit nodes for entry or middle hops when the
5553 total bandwidth available from non-Exit nodes is much higher than
5554 the total bandwidth available from Exit nodes.
5555 - Workaround for name servers (like Earthlink's) that hijack failing
5556 DNS requests and replace the no-such-server answer with a "helpful"
5557 redirect to an advertising-driven search portal. Also work around
5558 DNS hijackers who "helpfully" decline to hijack known-invalid
5559 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
5560 lets you turn it off.
5561 - Send out a burst of long-range padding cells once we've established
5562 that we're reachable. Spread them over 4 circuits, so hopefully
5563 a few will be fast. This exercises our bandwidth and bootstraps
5564 us into the directory more quickly.
5566 o New/improved config options:
5567 - Add new config option "ResolvConf" to let the server operator
5568 choose an alternate resolve.conf file when using eventdns.
5569 - Add an "EnforceDistinctSubnets" option to control our "exclude
5570 servers on the same /16" behavior. It's still on by default; this
5571 is mostly for people who want to operate private test networks with
5572 all the machines on the same subnet.
5573 - If one of our entry guards is on the ExcludeNodes list, or the
5574 directory authorities don't think it's a good guard, treat it as
5575 if it were unlisted: stop using it as a guard, and throw it off
5576 the guards list if it stays that way for a long time.
5577 - Allow directory authorities to be marked separately as authorities
5578 for the v1 directory protocol, the v2 directory protocol, and
5579 as hidden service directories, to make it easier to retire old
5580 authorities. V1 authorities should set "HSAuthoritativeDir 1"
5581 to continue being hidden service authorities too.
5582 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
5584 o Minor features, controller:
5585 - Fix CIRC controller events so that controllers can learn the
5586 identity digests of non-Named servers used in circuit paths.
5587 - Let controllers ask for more useful identifiers for servers. Instead
5588 of learning identity digests for un-Named servers and nicknames
5589 for Named servers, the new identifiers include digest, nickname,
5590 and indication of Named status. Off by default; see control-spec.txt
5591 for more information.
5592 - Add a "getinfo address" controller command so it can display Tor's
5593 best guess to the user.
5594 - New controller event to alert the controller when our server
5595 descriptor has changed.
5596 - Give more meaningful errors on controller authentication failure.
5598 o Minor features, other:
5599 - When asked to resolve a hostname, don't use non-exit servers unless
5600 requested to do so. This allows servers with broken DNS to be
5601 useful to the network.
5602 - Divide eventdns log messages into warn and info messages.
5603 - Reserve the nickname "Unnamed" for routers that can't pick
5604 a hostname: any router can call itself Unnamed; directory
5605 authorities will never allocate Unnamed to any particular router;
5606 clients won't believe that any router is the canonical Unnamed.
5607 - Only include function names in log messages for info/debug messages.
5608 For notice/warn/err, the content of the message should be clear on
5609 its own, and printing the function name only confuses users.
5610 - Avoid some false positives during reachability testing: don't try
5611 to test via a server that's on the same /24 as us.
5612 - If we fail to build a circuit to an intended enclave, and it's
5613 not mandatory that we use that enclave, stop wanting it.
5614 - When eventdns is enabled, allow multithreaded builds on NetBSD and
5615 OpenBSD. (We had previously disabled threads on these platforms
5616 because they didn't have working thread-safe resolver functions.)
5618 o Major bugfixes, anonymity/security:
5619 - If a client asked for a server by name, and there's a named server
5620 in our network-status but we don't have its descriptor yet, we
5621 could return an unnamed server instead.
5622 - Fix NetBSD bug that could allow someone to force uninitialized RAM
5623 to be sent to a server's DNS resolver. This only affects NetBSD
5624 and other platforms that do not bounds-check tolower().
5625 - Reject (most) attempts to use Tor circuits with length one. (If
5626 many people start using Tor as a one-hop proxy, exit nodes become
5627 a more attractive target for compromise.)
5628 - Just because your DirPort is open doesn't mean people should be
5629 able to remotely teach you about hidden service descriptors. Now
5630 only accept rendezvous posts if you've got HSAuthoritativeDir set.
5632 o Major bugfixes, other:
5633 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
5634 - When a client asks the server to resolve (not connect to)
5635 an address, and it has a cached answer, give them the cached answer.
5636 Previously, the server would give them no answer at all.
5637 - Allow really slow clients to not hang up five minutes into their
5638 directory downloads (suggested by Adam J. Richter).
5639 - We were building exactly the wrong circuits when we anticipated
5640 hidden service requirements, meaning Tor would have to build all
5641 its circuits on demand.
5642 - Avoid crashing when we mmap a router cache file of size 0.
5643 - When testing reachability of our DirPort, don't launch new
5644 tests when there's already one in progress -- unreachable
5645 servers were stacking up dozens of testing streams.
5647 o Minor bugfixes, correctness:
5648 - If we're a directory mirror and we ask for "all" network status
5649 documents, we would discard status documents from authorities
5651 - Avoid a memory corruption bug when creating a hash table for
5653 - Avoid controller-triggered crash when misusing certain commands
5654 from a v0 controller on platforms that do not handle
5655 printf("%s",NULL) gracefully.
5656 - Don't crash when a controller sends a third argument to an
5657 "extendcircuit" request.
5658 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
5659 response; fix error code when "getinfo dir/status/" fails.
5660 - Avoid crash when telling controller stream-status and a stream
5662 - Patch from Adam Langley to fix assert() in eventdns.c.
5663 - Fix a debug log message in eventdns to say "X resolved to Y"
5664 instead of "X resolved to X".
5665 - Make eventdns give strings for DNS errors, not just error numbers.
5666 - Track unreachable entry guards correctly: don't conflate
5667 'unreachable by us right now' with 'listed as down by the directory
5668 authorities'. With the old code, if a guard was unreachable by
5669 us but listed as running, it would clog our guard list forever.
5670 - Behave correctly in case we ever have a network with more than
5671 2GB/s total advertised capacity.
5672 - Make TrackExitHosts case-insensitive, and fix the behavior of
5673 ".suffix" TrackExitHosts items to avoid matching in the middle of
5675 - Finally fix the openssl warnings from newer gccs that believe that
5676 ignoring a return value is okay, but casting a return value and
5677 then ignoring it is a sign of madness.
5678 - Prevent the contrib/exitlist script from printing the same
5679 result more than once.
5680 - Patch from Steve Hildrey: Generate network status correctly on
5681 non-versioning dirservers.
5682 - Don't listen to the X-Your-Address-Is hint if you did the lookup
5683 via Tor; otherwise you'll think you're the exit node's IP address.
5685 o Minor bugfixes, performance:
5686 - Two small performance improvements on parsing descriptors.
5687 - Major performance improvement on inserting descriptors: change
5688 algorithm from O(n^2) to O(n).
5689 - Make the common memory allocation path faster on machines where
5690 malloc(0) returns a pointer.
5691 - Start remembering X-Your-Address-Is directory hints even if you're
5692 a client, so you can become a server more smoothly.
5693 - Avoid duplicate entries on MyFamily line in server descriptor.
5695 o Packaging, features:
5696 - Remove architecture from OS X builds. The official builds are
5697 now universal binaries.
5698 - The Debian package now uses --verify-config when (re)starting,
5699 to distinguish configuration errors from other errors.
5700 - Update RPMs to require libevent 1.1b.
5702 o Packaging, bugfixes:
5703 - Patches so Tor builds with MinGW on Windows.
5704 - Patches so Tor might run on Cygwin again.
5705 - Resume building on non-gcc compilers and ancient gcc. Resume
5706 building with the -O0 compile flag. Resume building cleanly on
5708 - Run correctly on OS X platforms with case-sensitive filesystems.
5709 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
5710 - Add autoconf checks so Tor can build on Solaris x86 again.
5713 - Documented (and renamed) ServerDNSSearchDomains and
5714 ServerDNSResolvConfFile options.
5715 - Be clearer that the *ListenAddress directives can be repeated
5719 Changes in version 0.1.1.24 - 2006-09-29
5721 - Allow really slow clients to not hang up five minutes into their
5722 directory downloads (suggested by Adam J. Richter).
5723 - Fix major performance regression from 0.1.0.x: instead of checking
5724 whether we have enough directory information every time we want to
5725 do something, only check when the directory information has changed.
5726 This should improve client CPU usage by 25-50%.
5727 - Don't crash if, after a server has been running for a while,
5728 it can't resolve its hostname.
5731 - Allow Tor to start when RunAsDaemon is set but no logs are set.
5732 - Don't crash when the controller receives a third argument to an
5733 "extendcircuit" request.
5734 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
5735 response; fix error code when "getinfo dir/status/" fails.
5736 - Fix configure.in to not produce broken configure files with
5737 more recent versions of autoconf. Thanks to Clint for his auto*
5739 - Fix security bug on NetBSD that could allow someone to force
5740 uninitialized RAM to be sent to a server's DNS resolver. This
5741 only affects NetBSD and other platforms that do not bounds-check
5743 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
5744 methods: these are known to be buggy.
5745 - If we're a directory mirror and we ask for "all" network status
5746 documents, we would discard status documents from authorities
5750 Changes in version 0.1.2.1-alpha - 2006-08-27
5752 - Add "eventdns" async dns library from Adam Langley, tweaked to
5753 build on OSX and Windows. Only enabled if you pass the
5754 --enable-eventdns argument to configure.
5755 - Allow servers with no hostname or IP address to learn their
5756 IP address by asking the directory authorities. This code only
5757 kicks in when you would normally have exited with a "no address"
5758 error. Nothing's authenticated, so use with care.
5759 - Rather than waiting a fixed amount of time between retrying
5760 application connections, we wait only 5 seconds for the first,
5761 10 seconds for the second, and 15 seconds for each retry after
5762 that. Hopefully this will improve the expected user experience.
5763 - Patch from Tup to add support for transparent AP connections:
5764 this basically bundles the functionality of trans-proxy-tor
5765 into the Tor mainline. Now hosts with compliant pf/netfilter
5766 implementations can redirect TCP connections straight to Tor
5767 without diverting through SOCKS. Needs docs.
5768 - Busy directory servers save lots of memory by spooling server
5769 descriptors, v1 directories, and v2 networkstatus docs to buffers
5770 as needed rather than en masse. Also mmap the cached-routers
5771 files, so we don't need to keep the whole thing in memory too.
5772 - Automatically avoid picking more than one node from the same
5773 /16 network when constructing a circuit.
5774 - Revise and clean up the torrc.sample that we ship with; add
5775 a section for BandwidthRate and BandwidthBurst.
5778 - Split circuit_t into origin_circuit_t and or_circuit_t, and
5779 split connection_t into edge, or, dir, control, and base structs.
5780 These will save quite a bit of memory on busy servers, and they'll
5781 also help us track down bugs in the code and bugs in the spec.
5782 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
5783 or later. Log when we are doing this, so we can diagnose it when
5784 it fails. (Also, recommend libevent 1.1b for kqueue and
5785 win32 methods; deprecate libevent 1.0b harder; make libevent
5786 recommendation system saner.)
5787 - Start being able to build universal binaries on OS X (thanks
5789 - Export the default exit policy via the control port, so controllers
5790 don't need to guess what it is / will be later.
5791 - Add a man page entry for ProtocolWarnings.
5792 - Add TestVia config option to the man page.
5793 - Remove even more protocol-related warnings from Tor server logs,
5794 such as bad TLS handshakes and malformed begin cells.
5795 - Stop fetching descriptors if you're not a dir mirror and you
5796 haven't tried to establish any circuits lately. [This currently
5797 causes some dangerous behavior, because when you start up again
5798 you'll use your ancient server descriptors.]
5799 - New DirPort behavior: if you have your dirport set, you download
5800 descriptors aggressively like a directory mirror, whether or not
5802 - Get rid of the router_retry_connections notion. Now routers
5803 no longer try to rebuild long-term connections to directory
5804 authorities, and directory authorities no longer try to rebuild
5805 long-term connections to all servers. We still don't hang up
5806 connections in these two cases though -- we need to look at it
5807 more carefully to avoid flapping, and we likely need to wait til
5808 0.1.1.x is obsolete.
5809 - Drop compatibility with obsolete Tors that permit create cells
5810 to have the wrong circ_id_type.
5811 - Re-enable per-connection rate limiting. Get rid of the "OP
5812 bandwidth" concept. Lay groundwork for "bandwidth classes" --
5813 separate global buckets that apply depending on what sort of conn
5815 - Start publishing one minute or so after we find our ORPort
5816 to be reachable. This will help reduce the number of descriptors
5817 we have for ourselves floating around, since it's quite likely
5818 other things (e.g. DirPort) will change during that minute too.
5819 - Fork the v1 directory protocol into its own spec document,
5820 and mark dir-spec.txt as the currently correct (v2) spec.
5823 - When we find our DirPort to be reachable, publish a new descriptor
5824 so we'll tell the world (reported by pnx).
5825 - Publish a new descriptor after we hup/reload. This is important
5826 if our config has changed such that we'll want to start advertising
5827 our DirPort now, etc.
5828 - Allow Tor to start when RunAsDaemon is set but no logs are set.
5829 - When we have a state file we cannot parse, tell the user and
5830 move it aside. Now we avoid situations where the user starts
5831 Tor in 1904, Tor writes a state file with that timestamp in it,
5832 the user fixes her clock, and Tor refuses to start.
5833 - Fix configure.in to not produce broken configure files with
5834 more recent versions of autoconf. Thanks to Clint for his auto*
5836 - "tor --verify-config" now exits with -1(255) or 0 depending on
5837 whether the config options are bad or good.
5838 - Resolve bug 321 when using dnsworkers: append a period to every
5839 address we resolve at the exit node, so that we do not accidentally
5840 pick up local addresses, and so that failing searches are retried
5841 in the resolver search domains. (This is already solved for
5842 eventdns.) (This breaks Blossom servers for now.)
5843 - If we are using an exit enclave and we can't connect, e.g. because
5844 its webserver is misconfigured to not listen on localhost, then
5845 back off and try connecting from somewhere else before we fail.
5848 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
5849 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
5850 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
5851 when the IP address is mapped through MapAddress to a hostname.
5852 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
5853 useless IPv6 DNS resolves.
5854 - Patch suggested by Karsten Loesing: respond to SIGNAL command
5855 before we execute the signal, in case the signal shuts us down.
5856 - Clean up AllowInvalidNodes man page entry.
5857 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
5858 - Add more asserts to track down an assert error on a windows Tor
5859 server with connection_add being called with socket == -1.
5860 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
5861 - Fix misleading log messages: an entry guard that is "unlisted",
5862 as well as not known to be "down" (because we've never heard
5863 of it), is not therefore "up".
5864 - Remove code to special-case "-cvs" ending, since it has not
5865 actually mattered since 0.0.9.
5866 - Make our socks5 handling more robust to broken socks clients:
5867 throw out everything waiting on the buffer in between socks
5868 handshake phases, since they can't possibly (so the theory
5869 goes) have predicted what we plan to respond to them.
5872 Changes in version 0.1.1.23 - 2006-07-30
5874 - Fast Tor servers, especially exit nodes, were triggering asserts
5875 due to a bug in handling the list of pending DNS resolves. Some
5876 bugs still remain here; we're hunting them.
5877 - Entry guards could crash clients by sending unexpected input.
5878 - More fixes on reachability testing: if you find yourself reachable,
5879 then don't ever make any client requests (so you stop predicting
5880 circuits), then hup or have your clock jump, then later your IP
5881 changes, you won't think circuits are working, so you won't try to
5882 test reachability, so you won't publish.
5885 - Avoid a crash if the controller does a resetconf firewallports
5886 and then a setconf fascistfirewall=1.
5887 - Avoid an integer underflow when the dir authority decides whether
5888 a router is stable: we might wrongly label it stable, and compute
5889 a slightly wrong median stability, when a descriptor is published
5891 - Fix a place where we might trigger an assert if we can't build our
5892 own server descriptor yet.
5895 Changes in version 0.1.1.22 - 2006-07-05
5897 - Fix a big bug that was causing servers to not find themselves
5898 reachable if they changed IP addresses. Since only 0.1.1.22+
5899 servers can do reachability testing correctly, now we automatically
5900 make sure to test via one of these.
5901 - Fix to allow clients and mirrors to learn directory info from
5902 descriptor downloads that get cut off partway through.
5903 - Directory authorities had a bug in deciding if a newly published
5904 descriptor was novel enough to make everybody want a copy -- a few
5905 servers seem to be publishing new descriptors many times a minute.
5907 - Fix a rare bug that was causing some servers to complain about
5908 "closing wedged cpuworkers" and skip some circuit create requests.
5909 - Make the Exit flag in directory status documents actually work.
5912 Changes in version 0.1.1.21 - 2006-06-10
5913 o Crash and assert fixes from 0.1.1.20:
5914 - Fix a rare crash on Tor servers that have enabled hibernation.
5915 - Fix a seg fault on startup for Tor networks that use only one
5916 directory authority.
5917 - Fix an assert from a race condition that occurs on Tor servers
5918 while exiting, where various threads are trying to log that they're
5919 exiting, and delete the logs, at the same time.
5920 - Make our unit tests pass again on certain obscure platforms.
5923 - Add support for building SUSE RPM packages.
5924 - Speed up initial bootstrapping for clients: if we are making our
5925 first ever connection to any entry guard, then don't mark it down
5927 - When only one Tor server in the network is labelled as a guard,
5928 and we've already picked him, we would cycle endlessly picking him
5929 again, being unhappy about it, etc. Now we specifically exclude
5930 current guards when picking a new guard.
5931 - Servers send create cells more reliably after the TLS connection
5932 is established: we were sometimes forgetting to send half of them
5933 when we had more than one pending.
5934 - If we get a create cell that asks us to extend somewhere, but the
5935 Tor server there doesn't match the expected digest, we now send
5936 a destroy cell back, rather than silently doing nothing.
5937 - Make options->RedirectExit work again.
5938 - Make cookie authentication for the controller work again.
5939 - Stop being picky about unusual characters in the arguments to
5940 mapaddress. It's none of our business.
5941 - Add a new config option "TestVia" that lets you specify preferred
5942 middle hops to use for test circuits. Perhaps this will let me
5943 debug the reachability problems better.
5945 o Log / documentation fixes:
5946 - If we're a server and some peer has a broken TLS certificate, don't
5947 log about it unless ProtocolWarnings is set, i.e., we want to hear
5948 about protocol violations by others.
5949 - Fix spelling of VirtualAddrNetwork in man page.
5950 - Add a better explanation at the top of the autogenerated torrc file
5951 about what happened to our old torrc.
5954 Changes in version 0.1.1.20 - 2006-05-23
5956 - Downgrade a log severity where servers complain that they're
5958 - Avoid a compile warning on FreeBSD.
5959 - Remove string size limit on NEWDESC messages; solve bug 291.
5960 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
5961 more thoroughly when we're running on windows.
5964 Changes in version 0.1.1.19-rc - 2006-05-03
5966 - Regenerate our local descriptor if it's dirty and we try to use
5967 it locally (e.g. if it changes during reachability detection).
5968 - If we setconf our ORPort to 0, we continued to listen on the
5969 old ORPort and receive connections.
5970 - Avoid a second warning about machine/limits.h on Debian
5972 - Be willing to add our own routerinfo into the routerlist.
5973 Now authorities will include themselves in their directories
5974 and network-statuses.
5975 - Stop trying to upload rendezvous descriptors to every
5976 directory authority: only try the v1 authorities.
5977 - Servers no longer complain when they think they're not
5978 registered with the directory authorities. There were too many
5980 - Backport dist-rpm changes so rpms can be built without errors.
5983 - Implement an option, VirtualAddrMask, to set which addresses
5984 get handed out in response to mapaddress requests. This works
5985 around a bug in tsocks where 127.0.0.0/8 is never socksified.
5988 Changes in version 0.1.1.18-rc - 2006-04-10
5990 - Work harder to download live network-statuses from all the
5991 directory authorities we know about. Improve the threshold
5992 decision logic so we're more robust to edge cases.
5993 - When fetching rendezvous descriptors, we were willing to ask
5994 v2 authorities too, which would always return 404.
5997 - Stop listing down or invalid nodes in the v1 directory. This will
5998 reduce its bulk by about 1/3, and reduce load on directory
6000 - When deciding whether a router is Fast or Guard-worthy, consider
6001 his advertised BandwidthRate and not just the BandwidthCapacity.
6002 - No longer ship INSTALL and README files -- they are useless now.
6003 - Force rpmbuild to behave and honor target_cpu.
6004 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
6005 - Start to include translated versions of the tor-doc-*.html
6006 files, along with the screenshots. Still needs more work.
6007 - Start sending back 512 and 451 errors if mapaddress fails,
6008 rather than not sending anything back at all.
6009 - When we fail to bind or listen on an incoming or outgoing
6010 socket, we should close it before failing. otherwise we just
6011 leak it. (thanks to weasel for finding.)
6012 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
6013 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
6014 - Make NoPublish (even though deprecated) work again.
6015 - Fix a minor security flaw where a versioning auth dirserver
6016 could list a recommended version many times in a row to make
6017 clients more convinced that it's recommended.
6018 - Fix crash bug if there are two unregistered servers running
6019 with the same nickname, one of them is down, and you ask for
6020 them by nickname in your EntryNodes or ExitNodes. Also, try
6021 to pick the one that's running rather than an arbitrary one.
6022 - Fix an infinite loop we could hit if we go offline for too long.
6023 - Complain when we hit WSAENOBUFS on recv() or write() too.
6024 Perhaps this will help us hunt the bug.
6025 - If you're not a versioning dirserver, don't put the string
6026 "client-versions \nserver-versions \n" in your network-status.
6027 - Lower the minimum required number of file descriptors to 1000,
6028 so we can have some overhead for Valgrind on Linux, where the
6029 default ulimit -n is 1024.
6032 - Add tor.dizum.com as the fifth authoritative directory server.
6033 - Add a new config option FetchUselessDescriptors, off by default,
6034 for when you plan to run "exitlist" on your client and you want
6035 to know about even the non-running descriptors.
6038 Changes in version 0.1.1.17-rc - 2006-03-28
6040 - Clients and servers since 0.1.1.10-alpha have been expiring
6041 connections whenever they are idle for 5 minutes and they *do*
6042 have circuits on them. Oops. With this new version, clients will
6043 discard their previous entry guard choices and avoid choosing
6044 entry guards running these flawed versions.
6045 - Fix memory leak when uncompressing concatenated zlib streams. This
6046 was causing substantial leaks over time on Tor servers.
6047 - The v1 directory was including servers as much as 48 hours old,
6048 because that's how the new routerlist->routers works. Now only
6049 include them if they're 20 hours old or less.
6052 - Resume building on irix64, netbsd 2.0, etc.
6053 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
6055 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
6056 and it is confusing some users.
6057 - Mirrors stop caching the v1 directory so often.
6058 - Make the max number of old descriptors that a cache will hold
6059 rise with the number of directory authorities, so we can scale.
6060 - Change our win32 uname() hack to be more forgiving about what
6061 win32 versions it thinks it's found.
6064 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
6066 - When the controller's *setconf commands fail, collect an error
6067 message in a string and hand it back to the controller.
6068 - Make the v2 dir's "Fast" flag based on relative capacity, just
6069 like "Stable" is based on median uptime. Name everything in the
6070 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
6071 - Log server fingerprint on startup, so new server operators don't
6072 have to go hunting around their filesystem for it.
6073 - Return a robots.txt on our dirport to discourage google indexing.
6074 - Let the controller ask for GETINFO dir/status/foo so it can ask
6075 directly rather than connecting to the dir port. Only works when
6076 dirport is set for now.
6078 o New config options rather than constants in the code:
6079 - SocksTimeout: How long do we let a socks connection wait
6080 unattached before we fail it?
6081 - CircuitBuildTimeout: Cull non-open circuits that were born
6082 at least this many seconds ago.
6083 - CircuitIdleTimeout: Cull open clean circuits that were born
6084 at least this many seconds ago.
6087 Changes in version 0.1.1.16-rc - 2006-03-18
6088 o Bugfixes on 0.1.1.15-rc:
6089 - Fix assert when the controller asks to attachstream a connect-wait
6090 or resolve-wait stream.
6091 - Now do address rewriting when the controller asks us to attach
6092 to a particular circuit too. This will let Blossom specify
6093 "moria2.exit" without having to learn what moria2's IP address is.
6094 - Make the "tor --verify-config" command-line work again, so people
6095 can automatically check if their torrc will parse.
6096 - Authoritative dirservers no longer require an open connection from
6097 a server to consider him "reachable". We need this change because
6098 when we add new auth dirservers, old servers won't know not to
6100 - Let Tor build on Sun CC again.
6101 - Fix an off-by-one buffer size in dirserv.c that magically never
6102 hit our three authorities but broke sjmurdoch's own tor network.
6103 - If we as a directory mirror don't know of any v1 directory
6104 authorities, then don't try to cache any v1 directories.
6105 - Stop warning about unknown servers in our family when they are
6106 given as hex digests.
6107 - Stop complaining as quickly to the server operator that he
6108 hasn't registered his nickname/key binding.
6109 - Various cleanups so we can add new V2 Auth Dirservers.
6110 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
6111 reflect the updated flags in our v2 dir protocol.
6112 - Resume allowing non-printable characters for exit streams (both
6113 for connecting and for resolving). Now we tolerate applications
6114 that don't follow the RFCs. But continue to block malformed names
6117 o Bugfixes on 0.1.0.x:
6118 - Fix assert bug in close_logs(): when we close and delete logs,
6119 remove them all from the global "logfiles" list.
6120 - Fix minor integer overflow in calculating when we expect to use up
6121 our bandwidth allocation before hibernating.
6122 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
6123 there are multiple SSLs installed with different versions.
6124 - When we try to be a server and Address is not explicitly set and
6125 our hostname resolves to a private IP address, try to use an
6126 interface address if it has a public address. Now Windows machines
6127 that think of themselves as localhost can work by default.
6130 - Let the controller ask for GETINFO dir/server/foo so it can ask
6131 directly rather than connecting to the dir port.
6132 - Let the controller tell us about certain router descriptors
6133 that it doesn't want Tor to use in circuits. Implement
6134 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
6135 - New config option SafeSocks to reject all application connections
6136 using unsafe socks protocols. Defaults to off.
6139 Changes in version 0.1.1.15-rc - 2006-03-11
6140 o Bugfixes and cleanups:
6141 - When we're printing strings from the network, don't try to print
6142 non-printable characters. This protects us against shell escape
6143 sequence exploits, and also against attacks to fool humans into
6144 misreading their logs.
6145 - Fix a bug where Tor would fail to establish any connections if you
6146 left it off for 24 hours and then started it: we were happy with
6147 the obsolete network statuses, but they all referred to router
6148 descriptors that were too old to fetch, so we ended up with no
6149 valid router descriptors.
6150 - Fix a seg fault in the controller's "getinfo orconn-status"
6151 command while listing status on incoming handshaking connections.
6152 Introduce a status name "NEW" for these connections.
6153 - If we get a linelist or linelist_s config option from the torrc
6154 (e.g. ExitPolicy) and it has no value, warn and skip rather than
6155 silently resetting it to its default.
6156 - Don't abandon entry guards until they've been down or gone for
6158 - Cleaner and quieter log messages.
6161 - New controller signal NEWNYM that makes new application requests
6163 - Add a new circuit purpose 'controller' to let the controller ask
6164 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
6165 controller command to let you specify the purpose if you're
6166 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
6167 command to let you change a circuit's purpose after it's been
6169 - Accept "private:*" in routerdesc exit policies; not generated yet
6170 because older Tors do not understand it.
6171 - Add BSD-style contributed startup script "rc.subr" from Peter
6175 Changes in version 0.1.1.14-alpha - 2006-02-20
6176 o Bugfixes on 0.1.1.x:
6177 - Don't die if we ask for a stdout or stderr log (even implicitly)
6178 and we're set to RunAsDaemon -- just warn.
6179 - We still had a few bugs in the OR connection rotation code that
6180 caused directory servers to slowly aggregate connections to other
6181 fast Tor servers. This time for sure!
6182 - Make log entries on Win32 include the name of the function again.
6183 - We were treating a pair of exit policies if they were equal even
6184 if one said accept and the other said reject -- causing us to
6185 not always publish a new descriptor since we thought nothing
6187 - Retry pending server downloads as well as pending networkstatus
6188 downloads when we unexpectedly get a socks request.
6189 - We were ignoring the IS_FAST flag in the directory status,
6190 meaning we were willing to pick trivial-bandwidth nodes for "fast"
6192 - If the controller's SAVECONF command fails (e.g. due to file
6193 permissions), let the controller know that it failed.
6196 - If we're trying to be a Tor server and running Windows 95/98/ME
6197 as a server, explain that we'll likely crash.
6198 - When we're a server, a client asks for an old-style directory,
6199 and our write bucket is empty, don't give it to him. This way
6200 small servers can continue to serve the directory *sometimes*,
6201 without getting overloaded.
6202 - Compress exit policies even more -- look for duplicate lines
6204 - Clients now honor the "guard" flag in the router status when
6205 picking entry guards, rather than looking at is_fast or is_stable.
6206 - Retain unrecognized lines in $DATADIR/state file, so that we can
6207 be forward-compatible.
6208 - Generate 18.0.0.0/8 address policy format in descs when we can;
6209 warn when the mask is not reducible to a bit-prefix.
6210 - Let the user set ControlListenAddress in the torrc. This can be
6211 dangerous, but there are some cases (like a secured LAN) where it
6213 - Split ReachableAddresses into ReachableDirAddresses and
6214 ReachableORAddresses, so we can restrict Dir conns to port 80
6215 and OR conns to port 443.
6216 - Now we can target arch and OS in rpm builds (contributed by
6217 Phobos). Also make the resulting dist-rpm filename match the
6219 - New config options to help controllers: FetchServerDescriptors
6220 and FetchHidServDescriptors for whether to fetch server
6221 info and hidserv info or let the controller do it, and
6222 PublishServerDescriptor and PublishHidServDescriptors.
6223 - Also let the controller set the __AllDirActionsPrivate config
6224 option if you want all directory fetches/publishes to happen via
6225 Tor (it assumes your controller bootstraps your circuits).
6228 Changes in version 0.1.0.17 - 2006-02-17
6229 o Crash bugfixes on 0.1.0.x:
6230 - When servers with a non-zero DirPort came out of hibernation,
6231 sometimes they would trigger an assert.
6233 o Other important bugfixes:
6234 - On platforms that don't have getrlimit (like Windows), we were
6235 artificially constraining ourselves to a max of 1024
6236 connections. Now just assume that we can handle as many as 15000
6237 connections. Hopefully this won't cause other problems.
6239 o Backported features:
6240 - When we're a server, a client asks for an old-style directory,
6241 and our write bucket is empty, don't give it to him. This way
6242 small servers can continue to serve the directory *sometimes*,
6243 without getting overloaded.
6244 - Whenever you get a 503 in response to a directory fetch, try
6245 once more. This will become important once servers start sending
6246 503's whenever they feel busy.
6247 - Fetch a new directory every 120 minutes, not every 40 minutes.
6248 Now that we have hundreds of thousands of users running the old
6249 directory algorithm, it's starting to hurt a lot.
6250 - Bump up the period for forcing a hidden service descriptor upload
6251 from 20 minutes to 1 hour.
6254 Changes in version 0.1.1.13-alpha - 2006-02-09
6255 o Crashes in 0.1.1.x:
6256 - When you tried to setconf ORPort via the controller, Tor would
6257 crash. So people using TorCP to become a server were sad.
6258 - Solve (I hope) the stack-smashing bug that we were seeing on fast
6259 servers. The problem appears to be something do with OpenSSL's
6260 random number generation, or how we call it, or something. Let me
6261 know if the crashes continue.
6262 - Turn crypto hardware acceleration off by default, until we find
6263 somebody smart who can test it for us. (It appears to produce
6264 seg faults in at least some cases.)
6265 - Fix a rare assert error when we've tried all intro points for
6266 a hidden service and we try fetching the service descriptor again:
6267 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
6270 - Fix a major load balance bug: we were round-robining in 16 KB
6271 chunks, and servers with bandwidthrate of 20 KB, while downloading
6272 a 600 KB directory, would starve their other connections. Now we
6273 try to be a bit more fair.
6274 - Dir authorities and mirrors were never expiring the newest
6275 descriptor for each server, causing memory and directory bloat.
6276 - Fix memory-bloating and connection-bloating bug on servers: We
6277 were never closing any connection that had ever had a circuit on
6278 it, because we were checking conn->n_circuits == 0, yet we had a
6279 bug that let it go negative.
6280 - Make Tor work using squid as your http proxy again -- squid
6281 returns an error if you ask for a URL that's too long, and it uses
6282 a really generic error message. Plus, many people are behind a
6283 transparent squid so they don't even realize it.
6284 - On platforms that don't have getrlimit (like Windows), we were
6285 artificially constraining ourselves to a max of 1024
6286 connections. Now just assume that we can handle as many as 15000
6287 connections. Hopefully this won't cause other problems.
6288 - Add a new config option ExitPolicyRejectPrivate which defaults to
6289 1. This means all exit policies will begin with rejecting private
6290 addresses, unless the server operator explicitly turns it off.
6293 - Clients no longer download descriptors for non-running
6295 - Before we add new directory authorities, we should make it
6296 clear that only v1 authorities should receive/publish hidden
6297 service descriptors.
6300 - As soon as we've fetched some more directory info, immediately
6301 try to download more server descriptors. This way we don't have
6302 a 10 second pause during initial bootstrapping.
6303 - Remove even more loud log messages that the server operator can't
6305 - When we're running an obsolete or un-recommended version, make
6306 the log message more clear about what the problem is and what
6307 versions *are* still recommended.
6308 - Provide a more useful warn message when our onion queue gets full:
6309 the CPU is too slow or the exit policy is too liberal.
6310 - Don't warn when we receive a 503 from a dirserver/cache -- this
6311 will pave the way for them being able to refuse if they're busy.
6312 - When we fail to bind a listener, try to provide a more useful
6313 log message: e.g., "Is Tor already running?"
6314 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
6315 Goldberg can prove things about our handshake protocol more
6317 - MaxConn has been obsolete for a while now. Document the ConnLimit
6318 config option, which is a *minimum* number of file descriptors
6319 that must be available else Tor refuses to start.
6320 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
6321 if you log to syslog and want something other than LOG_DAEMON.
6322 - Make dirservers generate a separate "guard" flag to mean,
6323 "would make a good entry guard". Make clients parse it and vote
6324 on it. Not used by clients yet.
6325 - Implement --with-libevent-dir option to ./configure. Also, improve
6326 search techniques to find libevent, and use those for openssl too.
6327 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
6328 - Only start testing reachability once we've established a
6329 circuit. This will make startup on dirservers less noisy.
6330 - Don't try to upload hidden service descriptors until we have
6331 established a circuit.
6332 - Fix the controller's "attachstream 0" command to treat conn like
6333 it just connected, doing address remapping, handling .exit and
6334 .onion idioms, and so on. Now we're more uniform in making sure
6335 that the controller hears about new and closing connections.
6338 Changes in version 0.1.1.12-alpha - 2006-01-11
6339 o Bugfixes on 0.1.1.x:
6340 - The fix to close duplicate server connections was closing all
6341 Tor client connections if they didn't establish a circuit
6342 quickly enough. Oops.
6343 - Fix minor memory issue (double-free) that happened on exit.
6345 o Bugfixes on 0.1.0.x:
6346 - Tor didn't warn when it failed to open a log file.
6349 Changes in version 0.1.1.11-alpha - 2006-01-10
6350 o Crashes in 0.1.1.x:
6351 - Include all the assert/crash fixes from 0.1.0.16.
6352 - If you start Tor and then quit very quickly, there were some
6353 races that tried to free things that weren't allocated yet.
6354 - Fix a rare memory stomp if you're running hidden services.
6355 - Fix segfault when specifying DirServer in config without nickname.
6356 - Fix a seg fault when you finish connecting to a server but at
6357 that moment you dump his server descriptor.
6358 - Extendcircuit and Attachstream controller commands would
6359 assert/crash if you don't give them enough arguments.
6360 - Fix an assert error when we're out of space in the connection_list
6361 and we try to post a hidden service descriptor (reported by weasel).
6362 - If you specify a relative torrc path and you set RunAsDaemon in
6363 your torrc, then it chdir()'s to the new directory. If you HUP,
6364 it tries to load the new torrc location, fails, and exits.
6365 The fix: no longer allow a relative path to torrc using -f.
6368 - Implement "entry guards": automatically choose a handful of entry
6369 nodes and stick with them for all circuits. Only pick new guards
6370 when the ones you have are unsuitable, and if the old guards
6371 become suitable again, switch back. This will increase security
6372 dramatically against certain end-point attacks. The EntryNodes
6373 config option now provides some hints about which entry guards you
6374 want to use most; and StrictEntryNodes means to only use those.
6375 - New directory logic: download by descriptor digest, not by
6376 fingerprint. Caches try to download all listed digests from
6377 authorities; clients try to download "best" digests from caches.
6378 This avoids partitioning and isolating attacks better.
6379 - Make the "stable" router flag in network-status be the median of
6380 the uptimes of running valid servers, and make clients pay
6381 attention to the network-status flags. Thus the cutoff adapts
6382 to the stability of the network as a whole, making IRC, IM, etc
6383 connections more reliable.
6386 - Tor servers with dynamic IP addresses were needing to wait 18
6387 hours before they could start doing reachability testing using
6388 the new IP address and ports. This is because they were using
6389 the internal descriptor to learn what to test, yet they were only
6390 rebuilding the descriptor once they decided they were reachable.
6391 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
6392 to download certain server descriptors, throw them away, and then
6393 fetch them again after 30 minutes. Now mirrors throw away these
6394 server descriptors so clients can't get them.
6395 - We were leaving duplicate connections to other ORs open for a week,
6396 rather than closing them once we detect a duplicate. This only
6397 really affected authdirservers, but it affected them a lot.
6398 - Spread the authdirservers' reachability testing over the entire
6399 testing interval, so we don't try to do 500 TLS's at once every
6403 - If the network is down, and we try to connect to a conn because
6404 we have a circuit in mind, and we timeout (30 seconds) because the
6405 network never answers, we were expiring the circuit, but we weren't
6406 obsoleting the connection or telling the entry_guards functions.
6407 - Some Tor servers process billions of cells per day. These statistics
6408 need to be uint64_t's.
6409 - Check for integer overflows in more places, when adding elements
6410 to smartlists. This could possibly prevent a buffer overflow
6411 on malicious huge inputs. I don't see any, but I haven't looked
6413 - ReachableAddresses kept growing new "reject *:*" lines on every
6415 - When you "setconf log" via the controller, it should remove all
6416 logs. We were automatically adding back in a "log notice stdout".
6417 - Newly bootstrapped Tor networks couldn't establish hidden service
6418 circuits until they had nodes with high uptime. Be more tolerant.
6419 - We were marking servers down when they could not answer every piece
6420 of the directory request we sent them. This was far too harsh.
6421 - Fix the torify (tsocks) config file to not use Tor for localhost
6423 - Directory authorities now go to the proper authority when asking for
6424 a networkstatus, even when they want a compressed one.
6425 - Fix a harmless bug that was causing Tor servers to log
6426 "Got an end because of misc error, but we're not an AP. Closing."
6427 - Authorities were treating their own descriptor changes as cosmetic,
6428 meaning the descriptor available in the network-status and the
6429 descriptor that clients downloaded were different.
6430 - The OS X installer was adding a symlink for tor_resolve but
6431 the binary was called tor-resolve (reported by Thomas Hardly).
6432 - Workaround a problem with some http proxies where they refuse GET
6433 requests that specify "Content-Length: 0" (reported by Adrian).
6434 - Fix wrong log message when you add a "HiddenServiceNodes" config
6435 line without any HiddenServiceDir line (reported by Chris Thomas).
6438 - Write the TorVersion into the state file so we have a prayer of
6439 keeping forward and backward compatibility.
6440 - Revive the FascistFirewall config option rather than eliminating it:
6441 now it's a synonym for ReachableAddresses *:80,*:443.
6442 - Clients choose directory servers from the network status lists,
6443 not from their internal list of router descriptors. Now they can
6444 go to caches directly rather than needing to go to authorities
6446 - Directory authorities ignore router descriptors that have only
6447 cosmetic differences: do this for 0.1.0.x servers now too.
6448 - Add a new flag to network-status indicating whether the server
6449 can answer v2 directory requests too.
6450 - Authdirs now stop whining so loudly about bad descriptors that
6451 they fetch from other dirservers. So when there's a log complaint,
6452 it's for sure from a freshly uploaded descriptor.
6453 - Reduce memory requirements in our structs by changing the order
6455 - There used to be two ways to specify your listening ports in a
6456 server descriptor: on the "router" line and with a separate "ports"
6457 line. Remove support for the "ports" line.
6458 - New config option "AuthDirRejectUnlisted" for auth dirservers as
6459 a panic button: if we get flooded with unusable servers we can
6460 revert to only listing servers in the approved-routers file.
6461 - Auth dir servers can now mark a fingerprint as "!reject" or
6462 "!invalid" in the approved-routers file (as its nickname), to
6463 refuse descriptors outright or include them but marked as invalid.
6464 - Servers store bandwidth history across restarts/crashes.
6465 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
6466 get a better idea of why their circuits failed. Not used yet.
6467 - Directory mirrors now cache up to 16 unrecognized network-status
6468 docs. Now we can add new authdirservers and they'll be cached too.
6469 - When picking a random directory, prefer non-authorities if any
6471 - New controller option "getinfo desc/all-recent" to fetch the
6472 latest server descriptor for every router that Tor knows about.
6475 Changes in version 0.1.0.16 - 2006-01-02
6476 o Crash bugfixes on 0.1.0.x:
6477 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
6478 corrupting the heap, losing FDs, or crashing when we need to resize
6479 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
6480 - It turns out sparc64 platforms crash on unaligned memory access
6481 too -- so detect and avoid this.
6482 - Handle truncated compressed data correctly (by detecting it and
6484 - Fix possible-but-unlikely free(NULL) in control.c.
6485 - When we were closing connections, there was a rare case that
6486 stomped on memory, triggering seg faults and asserts.
6487 - Avoid potential infinite recursion when building a descriptor. (We
6488 don't know that it ever happened, but better to fix it anyway.)
6489 - We were neglecting to unlink marked circuits from soon-to-close OR
6490 connections, which caused some rare scribbling on freed memory.
6491 - Fix a memory stomping race bug when closing the joining point of two
6492 rendezvous circuits.
6493 - Fix an assert in time parsing found by Steven Murdoch.
6495 o Other bugfixes on 0.1.0.x:
6496 - When we're doing reachability testing, provide more useful log
6497 messages so the operator knows what to expect.
6498 - Do not check whether DirPort is reachable when we are suppressing
6499 advertising it because of hibernation.
6500 - When building with -static or on Solaris, we sometimes needed -ldl.
6501 - When we're deciding whether a stream has enough circuits around
6502 that can handle it, count the freshly dirty ones and not the ones
6503 that are so dirty they won't be able to handle it.
6504 - When we're expiring old circuits, we had a logic error that caused
6505 us to close new rendezvous circuits rather than old ones.
6506 - Give a more helpful log message when you try to change ORPort via
6507 the controller: you should upgrade Tor if you want that to work.
6508 - We were failing to parse Tor versions that start with "Tor ".
6509 - Tolerate faulty streams better: when a stream fails for reason
6510 exitpolicy, stop assuming that the router is lying about his exit
6511 policy. When a stream fails for reason misc, allow it to retry just
6512 as if it was resolvefailed. When a stream has failed three times,
6513 reset its failure count so we can try again and get all three tries.
6516 Changes in version 0.1.1.10-alpha - 2005-12-11
6517 o Correctness bugfixes on 0.1.0.x:
6518 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
6519 corrupting the heap, losing FDs, or crashing when we need to resize
6520 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
6521 - Stop doing the complex voodoo overkill checking for insecure
6522 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
6523 - When we were closing connections, there was a rare case that
6524 stomped on memory, triggering seg faults and asserts.
6525 - We were neglecting to unlink marked circuits from soon-to-close OR
6526 connections, which caused some rare scribbling on freed memory.
6527 - When we're deciding whether a stream has enough circuits around
6528 that can handle it, count the freshly dirty ones and not the ones
6529 that are so dirty they won't be able to handle it.
6530 - Recover better from TCP connections to Tor servers that are
6531 broken but don't tell you (it happens!); and rotate TLS
6532 connections once a week.
6533 - When we're expiring old circuits, we had a logic error that caused
6534 us to close new rendezvous circuits rather than old ones.
6535 - Fix a scary-looking but apparently harmless bug where circuits
6536 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
6537 servers, and never switch to state CIRCUIT_STATE_OPEN.
6538 - When building with -static or on Solaris, we sometimes needed to
6540 - Give a useful message when people run Tor as the wrong user,
6541 rather than telling them to start chowning random directories.
6542 - We were failing to inform the controller about new .onion streams.
6544 o Security bugfixes on 0.1.0.x:
6545 - Refuse server descriptors if the fingerprint line doesn't match
6546 the included identity key. Tor doesn't care, but other apps (and
6547 humans) might actually be trusting the fingerprint line.
6548 - We used to kill the circuit when we receive a relay command we
6549 don't recognize. Now we just drop it.
6550 - Start obeying our firewall options more rigorously:
6551 . If we can't get to a dirserver directly, try going via Tor.
6552 . Don't ever try to connect (as a client) to a place our
6553 firewall options forbid.
6554 . If we specify a proxy and also firewall options, obey the
6555 firewall options even when we're using the proxy: some proxies
6556 can only proxy to certain destinations.
6557 - Fix a bug found by Lasse Overlier: when we were making internal
6558 circuits (intended to be cannibalized later for rendezvous and
6559 introduction circuits), we were picking them so that they had
6560 useful exit nodes. There was no need for this, and it actually
6561 aids some statistical attacks.
6562 - Start treating internal circuits and exit circuits separately.
6563 It's important to keep them separate because internal circuits
6564 have their last hops picked like middle hops, rather than like
6565 exit hops. So exiting on them will break the user's expectations.
6567 o Bugfixes on 0.1.1.x:
6568 - Take out the mis-feature where we tried to detect IP address
6569 flapping for people with DynDNS, and chose not to upload a new
6570 server descriptor sometimes.
6571 - Try to be compatible with OpenSSL 0.9.6 again.
6572 - Log fix: when the controller is logging about .onion addresses,
6573 sometimes it didn't include the ".onion" part of the address.
6574 - Don't try to modify options->DirServers internally -- if the
6575 user didn't specify any, just add the default ones directly to
6576 the trusted dirserver list. This fixes a bug where people running
6577 controllers would use SETCONF on some totally unrelated config
6578 option, and Tor would start yelling at them about changing their
6580 - Let the controller's redirectstream command specify a port, in
6581 case the controller wants to change that too.
6582 - When we requested a pile of server descriptors, we sometimes
6583 accidentally launched a duplicate request for the first one.
6584 - Bugfix for trackhostexits: write down the fingerprint of the
6585 chosen exit, not its nickname, because the chosen exit might not
6587 - When parsing foo.exit, if foo is unknown, and we are leaving
6588 circuits unattached, set the chosen_exit field and leave the
6589 address empty. This matters because controllers got confused
6591 - Directory authorities no longer try to download server
6592 descriptors that they know they will reject.
6594 o Features and updates:
6595 - Replace balanced trees with hash tables: this should make stuff
6596 significantly faster.
6597 - Resume using the AES counter-mode implementation that we ship,
6598 rather than OpenSSL's. Ours is significantly faster.
6599 - Many other CPU and memory improvements.
6600 - Add a new config option FastFirstHopPK (on by default) so clients
6601 do a trivial crypto handshake for their first hop, since TLS has
6602 already taken care of confidentiality and authentication.
6603 - Add a new config option TestSocks so people can see if their
6604 applications are using socks4, socks4a, socks5-with-ip, or
6605 socks5-with-hostname. This way they don't have to keep mucking
6606 with tcpdump and wondering if something got cached somewhere.
6607 - Warn when listening on a public address for socks. I suspect a
6608 lot of people are setting themselves up as open socks proxies,
6609 and they have no idea that jerks on the Internet are using them,
6610 since they simply proxy the traffic into the Tor network.
6611 - Add "private:*" as an alias in configuration for policies. Now
6612 you can simplify your exit policy rather than needing to list
6613 every single internal or nonroutable network space.
6614 - Add a new controller event type that allows controllers to get
6615 all server descriptors that were uploaded to a router in its role
6616 as authoritative dirserver.
6617 - Start shipping socks-extensions.txt, tor-doc-unix.html,
6618 tor-doc-server.html, and stylesheet.css in the tarball.
6619 - Stop shipping tor-doc.html in the tarball.
6622 Changes in version 0.1.1.9-alpha - 2005-11-15
6623 o Usability improvements:
6624 - Start calling it FooListenAddress rather than FooBindAddress,
6625 since few of our users know what it means to bind an address
6627 - Reduce clutter in server logs. We're going to try to make
6628 them actually usable now. New config option ProtocolWarnings that
6629 lets you hear about how _other Tors_ are breaking the protocol. Off
6631 - Divide log messages into logging domains. Once we put some sort
6632 of interface on this, it will let people looking at more verbose
6633 log levels specify the topics they want to hear more about.
6634 - Make directory servers return better http 404 error messages
6635 instead of a generic "Servers unavailable".
6636 - Check for even more Windows version flags when writing the platform
6637 string in server descriptors, and note any we don't recognize.
6638 - Clean up more of the OpenSSL memory when exiting, so we can detect
6639 memory leaks better.
6640 - Make directory authorities be non-versioning, non-naming by
6641 default. Now we can add new directory servers without requiring
6642 their operators to pay close attention.
6643 - When logging via syslog, include the pid whenever we provide
6644 a log entry. Suggested by Todd Fries.
6646 o Performance improvements:
6647 - Directory servers now silently throw away new descriptors that
6648 haven't changed much if the timestamps are similar. We do this to
6649 tolerate older Tor servers that upload a new descriptor every 15
6650 minutes. (It seemed like a good idea at the time.)
6651 - Inline bottleneck smartlist functions; use fast versions by default.
6652 - Add a "Map from digest to void*" abstraction digestmap_t so we
6653 can do less hex encoding/decoding. Use it in router_get_by_digest()
6654 to resolve a performance bottleneck.
6655 - Allow tor_gzip_uncompress to extract as much as possible from
6656 truncated compressed data. Try to extract as many
6657 descriptors as possible from truncated http responses (when
6658 DIR_PURPOSE_FETCH_ROUTERDESC).
6659 - Make circ->onionskin a pointer, not a static array. moria2 was using
6660 125000 circuit_t's after it had been up for a few weeks, which
6661 translates to 20+ megs of wasted space.
6662 - The private half of our EDH handshake keys are now chosen out
6663 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
6665 o Security improvements:
6666 - Start making directory caches retain old routerinfos, so soon
6667 clients can start asking by digest of descriptor rather than by
6668 fingerprint of server.
6669 - Add half our entropy from RAND_poll in OpenSSL. This knows how
6670 to use egd (if present), openbsd weirdness (if present), vms/os2
6671 weirdness (if we ever port there), and more in the future.
6673 o Bugfixes on 0.1.0.x:
6674 - Do round-robin writes of at most 16 kB per write. This might be
6675 more fair on loaded Tor servers, and it might resolve our Windows
6676 crash bug. It might also slow things down.
6677 - Our TLS handshakes were generating a single public/private
6678 keypair for the TLS context, rather than making a new one for
6679 each new connections. Oops. (But we were still rotating them
6680 periodically, so it's not so bad.)
6681 - When we were cannibalizing a circuit with a particular exit
6682 node in mind, we weren't checking to see if that exit node was
6683 already present earlier in the circuit. Oops.
6684 - When a Tor server's IP changes (e.g. from a dyndns address),
6685 upload a new descriptor so clients will learn too.
6686 - Really busy servers were keeping enough circuits open on stable
6687 connections that they were wrapping around the circuit_id
6688 space. (It's only two bytes.) This exposed a bug where we would
6689 feel free to reuse a circuit_id even if it still exists but has
6690 been marked for close. Try to fix this bug. Some bug remains.
6691 - If we would close a stream early (e.g. it asks for a .exit that
6692 we know would refuse it) but the LeaveStreamsUnattached config
6693 option is set by the controller, then don't close it.
6695 o Bugfixes on 0.1.1.8-alpha:
6696 - Fix a big pile of memory leaks, some of them serious.
6697 - Do not try to download a routerdesc if we would immediately reject
6699 - Resume inserting a newline between all router descriptors when
6700 generating (old style) signed directories, since our spec says
6702 - When providing content-type application/octet-stream for
6703 server descriptors using .z, we were leaving out the
6704 content-encoding header. Oops. (Everything tolerated this just
6705 fine, but that doesn't mean we need to be part of the problem.)
6706 - Fix a potential seg fault in getconf and getinfo using version 1
6707 of the controller protocol.
6708 - Avoid crash: do not check whether DirPort is reachable when we
6709 are suppressing it because of hibernation.
6710 - Make --hash-password not crash on exit.
6713 Changes in version 0.1.1.8-alpha - 2005-10-07
6714 o New features (major):
6715 - Clients don't download or use the directory anymore. Now they
6716 download and use network-statuses from the trusted dirservers,
6717 and fetch individual server descriptors as needed from mirrors.
6718 See dir-spec.txt for all the gory details.
6719 - Be more conservative about whether to advertise our DirPort.
6720 The main change is to not advertise if we're running at capacity
6721 and either a) we could hibernate or b) our capacity is low and
6722 we're using a default DirPort.
6723 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
6725 o New features (minor):
6726 - Try to be smart about when to retry network-status and
6727 server-descriptor fetches. Still needs some tuning.
6728 - Stop parsing, storing, or using running-routers output (but
6729 mirrors still cache and serve it).
6730 - Consider a threshold of versioning dirservers (dirservers who have
6731 an opinion about which Tor versions are still recommended) before
6732 deciding whether to warn the user that he's obsolete.
6733 - Dirservers can now reject/invalidate by key and IP, with the
6734 config options "AuthDirInvalid" and "AuthDirReject". This is
6735 useful since currently we automatically list servers as running
6736 and usable even if we know they're jerks.
6737 - Provide dire warnings to any users who set DirServer; move it out
6738 of torrc.sample and into torrc.complete.
6739 - Add MyFamily to torrc.sample in the server section.
6740 - Add nicknames to the DirServer line, so we can refer to them
6741 without requiring all our users to memorize their IP addresses.
6742 - When we get an EOF or a timeout on a directory connection, note
6743 how many bytes of serverdesc we are dropping. This will help
6744 us determine whether it is smart to parse incomplete serverdesc
6746 - Add a new function to "change pseudonyms" -- that is, to stop
6747 using any currently-dirty circuits for new streams, so we don't
6748 link new actions to old actions. Currently it's only called on
6749 HUP (or SIGNAL RELOAD).
6750 - On sighup, if UseHelperNodes changed to 1, use new circuits.
6751 - Start using RAND_bytes rather than RAND_pseudo_bytes from
6752 OpenSSL. Also, reseed our entropy every hour, not just at
6753 startup. And entropy in 512-bit chunks, not 160-bit chunks.
6755 o Fixes on 0.1.1.7-alpha:
6756 - Nobody ever implemented EVENT_ADDRMAP for control protocol
6757 version 0, so don't let version 0 controllers ask for it.
6758 - If you requested something with too many newlines via the
6759 v1 controller protocol, you could crash tor.
6760 - Fix a number of memory leaks, including some pretty serious ones.
6761 - Re-enable DirPort testing again, so Tor servers will be willing
6762 to advertise their DirPort if it's reachable.
6763 - On TLS handshake, only check the other router's nickname against
6764 its expected nickname if is_named is set.
6766 o Fixes forward-ported from 0.1.0.15:
6767 - Don't crash when we don't have any spare file descriptors and we
6768 try to spawn a dns or cpu worker.
6769 - Make the numbers in read-history and write-history into uint64s,
6770 so they don't overflow and publish negatives in the descriptor.
6773 - For the OS X package's modified privoxy config file, comment
6774 out the "logfile" line so we don't log everything passed
6776 - We were whining about using socks4 or socks5-with-local-lookup
6777 even when it's an IP in the "virtual" range we designed exactly
6779 - We were leaking some memory every time the client changes IPs.
6780 - Never call free() on tor_malloc()d memory. This will help us
6781 use dmalloc to detect memory leaks.
6782 - Check for named servers when looking them up by nickname;
6783 warn when we'recalling a non-named server by its nickname;
6784 don't warn twice about the same name.
6785 - Try to list MyFamily elements by key, not by nickname, and warn
6786 if we've not heard of the server.
6787 - Make windows platform detection (uname equivalent) smarter.
6788 - It turns out sparc64 doesn't like unaligned access either.
6791 Changes in version 0.1.0.15 - 2005-09-23
6792 o Bugfixes on 0.1.0.x:
6793 - Reject ports 465 and 587 (spam targets) in default exit policy.
6794 - Don't crash when we don't have any spare file descriptors and we
6795 try to spawn a dns or cpu worker.
6796 - Get rid of IgnoreVersion undocumented config option, and make us
6797 only warn, never exit, when we're running an obsolete version.
6798 - Don't try to print a null string when your server finds itself to
6799 be unreachable and the Address config option is empty.
6800 - Make the numbers in read-history and write-history into uint64s,
6801 so they don't overflow and publish negatives in the descriptor.
6802 - Fix a minor memory leak in smartlist_string_remove().
6803 - We were only allowing ourselves to upload a server descriptor at
6804 most every 20 minutes, even if it changed earlier than that.
6805 - Clean up log entries that pointed to old URLs.
6808 Changes in version 0.1.1.7-alpha - 2005-09-14
6809 o Fixes on 0.1.1.6-alpha:
6810 - Exit servers were crashing when people asked them to make a
6811 connection to an address not in their exit policy.
6812 - Looking up a non-existent stream for a v1 control connection would
6814 - Fix a seg fault if we ask a dirserver for a descriptor by
6815 fingerprint but he doesn't know about him.
6816 - SETCONF was appending items to linelists, not clearing them.
6817 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
6818 out and refuse the setconf if it would fail.
6819 - Downgrade the dirserver log messages when whining about
6823 - Add Peter Palfrader's check-tor script to tor/contrib/
6824 It lets you easily check whether a given server (referenced by
6825 nickname) is reachable by you.
6826 - Numerous changes to move towards client-side v2 directories. Not
6830 - If the user gave tor an odd number of command-line arguments,
6831 we were silently ignoring the last one. Now we complain and fail.
6832 [This wins the oldest-bug prize -- this bug has been present since
6833 November 2002, as released in Tor 0.0.0.]
6834 - Do not use unaligned memory access on alpha, mips, or mipsel.
6835 It *works*, but is very slow, so we treat them as if it doesn't.
6836 - Retry directory requests if we fail to get an answer we like
6837 from a given dirserver (we were retrying before, but only if
6838 we fail to connect).
6839 - When writing the RecommendedVersions line, sort them first.
6840 - When the client asked for a rendezvous port that the hidden
6841 service didn't want to provide, we were sending an IP address
6842 back along with the end cell. Fortunately, it was zero. But stop
6844 - Correct "your server is reachable" log entries to indicate that
6845 it was self-testing that told us so.
6848 Changes in version 0.1.1.6-alpha - 2005-09-09
6849 o Fixes on 0.1.1.5-alpha:
6850 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
6851 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
6852 - Fix bug with tor_memmem finding a match at the end of the string.
6853 - Make unit tests run without segfaulting.
6854 - Resolve some solaris x86 compile warnings.
6855 - Handle duplicate lines in approved-routers files without warning.
6856 - Fix bug where as soon as a server refused any requests due to his
6857 exit policy (e.g. when we ask for localhost and he tells us that's
6858 127.0.0.1 and he won't do it), we decided he wasn't obeying his
6859 exit policy using him for any exits.
6860 - Only do openssl hardware accelerator stuff if openssl version is
6863 o New controller features/fixes:
6864 - Add a "RESETCONF" command so you can set config options like
6865 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
6866 a config option in the torrc with no value, then it clears it
6867 entirely (rather than setting it to its default).
6868 - Add a "GETINFO config-file" to tell us where torrc is.
6869 - Avoid sending blank lines when GETINFO replies should be empty.
6870 - Add a QUIT command for the controller (for using it manually).
6871 - Fix a bug in SAVECONF that was adding default dirservers and
6872 other redundant entries to the torrc file.
6874 o Start on the new directory design:
6875 - Generate, publish, cache, serve new network-status format.
6876 - Publish individual descriptors (by fingerprint, by "all", and by
6878 - Publish client and server recommended versions separately.
6879 - Allow tor_gzip_uncompress() to handle multiple concatenated
6880 compressed strings. Serve compressed groups of router
6881 descriptors. The compression logic here could be more
6883 - Distinguish v1 authorities (all currently trusted directories)
6884 from v2 authorities (all trusted directories).
6885 - Change DirServers config line to note which dirs are v1 authorities.
6886 - Add configuration option "V1AuthoritativeDirectory 1" which
6887 moria1, moria2, and tor26 should set.
6888 - Remove option when getting directory cache to see whether they
6889 support running-routers; they all do now. Replace it with one
6890 to see whether caches support v2 stuff.
6893 - Dirservers now do their own external reachability testing of each
6894 Tor server, and only list them as running if they've been found to
6895 be reachable. We also send back warnings to the server's logs if
6896 it uploads a descriptor that we already believe is unreachable.
6897 - Implement exit enclaves: if we know an IP address for the
6898 destination, and there's a running Tor server at that address
6899 which allows exit to the destination, then extend the circuit to
6900 that exit first. This provides end-to-end encryption and end-to-end
6901 authentication. Also, if the user wants a .exit address or enclave,
6902 use 4 hops rather than 3, and cannibalize a general circ for it
6904 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
6905 controller. Also, rotate dns and cpu workers if the controller
6906 changes options that will affect them; and initialize the dns
6907 worker cache tree whether or not we start out as a server.
6908 - Only upload a new server descriptor when options change, 18
6909 hours have passed, uptime is reset, or bandwidth changes a lot.
6910 - Check [X-]Forwarded-For headers in HTTP requests when generating
6911 log messages. This lets people run dirservers (and caches) behind
6912 Apache but still know which IP addresses are causing warnings.
6914 o Config option changes:
6915 - Replace (Fascist)Firewall* config options with a new
6916 ReachableAddresses option that understands address policies.
6917 For example, "ReachableAddresses *:80,*:443"
6918 - Get rid of IgnoreVersion undocumented config option, and make us
6919 only warn, never exit, when we're running an obsolete version.
6920 - Make MonthlyAccountingStart config option truly obsolete now.
6923 - Reject ports 465 and 587 in the default exit policy, since
6924 people have started using them for spam too.
6925 - It turns out we couldn't bootstrap a network since we added
6926 reachability detection in 0.1.0.1-rc. Good thing the Tor network
6927 has never gone down. Add an AssumeReachable config option to let
6928 servers and dirservers bootstrap. When we're trying to build a
6929 high-uptime or high-bandwidth circuit but there aren't enough
6930 suitable servers, try being less picky rather than simply failing.
6931 - Our logic to decide if the OR we connected to was the right guy
6932 was brittle and maybe open to a mitm for unverified routers.
6933 - We weren't cannibalizing circuits correctly for
6934 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
6935 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
6936 build those from scratch. This should make hidden services faster.
6937 - Predict required circuits better, with an eye toward making hidden
6938 services faster on the service end.
6939 - Retry streams if the exit node sends back a 'misc' failure. This
6940 should result in fewer random failures. Also, after failing
6941 from resolve failed or misc, reset the num failures, so we give
6942 it a fair shake next time we try.
6943 - Clean up the rendezvous warn log msgs, and downgrade some to info.
6944 - Reduce severity on logs about dns worker spawning and culling.
6945 - When we're shutting down and we do something like try to post a
6946 server descriptor or rendezvous descriptor, don't complain that
6947 we seem to be unreachable. Of course we are, we're shutting down.
6948 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
6949 We don't use them yet, but maybe one day our DNS resolver will be
6950 able to discover them.
6951 - Make ContactInfo mandatory for authoritative directory servers.
6952 - Require server descriptors to list IPv4 addresses -- hostnames
6953 are no longer allowed. This also fixes some potential security
6954 problems with people providing hostnames as their address and then
6955 preferentially resolving them to partition users.
6956 - Change log line for unreachability to explicitly suggest /etc/hosts
6957 as the culprit. Also make it clearer what IP address and ports we're
6958 testing for reachability.
6959 - Put quotes around user-supplied strings when logging so users are
6960 more likely to realize if they add bad characters (like quotes)
6962 - Let auth dir servers start without specifying an Address config
6964 - Make unit tests (and other invocations that aren't the real Tor)
6965 run without launching listeners, creating subdirectories, and so on.
6968 Changes in version 0.1.1.5-alpha - 2005-08-08
6969 o Bugfixes included in 0.1.0.14.
6971 o Bugfixes on 0.1.0.x:
6972 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
6973 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
6974 it would silently using ignore the 6668.
6977 Changes in version 0.1.0.14 - 2005-08-08
6978 o Bugfixes on 0.1.0.x:
6979 - Fix the other half of the bug with crypto handshakes
6981 - Fix an assert trigger if you send a 'signal term' via the
6982 controller when it's listening for 'event info' messages.
6985 Changes in version 0.1.1.4-alpha - 2005-08-04
6986 o Bugfixes included in 0.1.0.13.
6989 - Improve tor_gettimeofday() granularity on windows.
6990 - Make clients regenerate their keys when their IP address changes.
6991 - Implement some more GETINFO goodness: expose helper nodes, config
6992 options, getinfo keys.
6995 Changes in version 0.1.0.13 - 2005-08-04
6996 o Bugfixes on 0.1.0.x:
6997 - Fix a critical bug in the security of our crypto handshakes.
6998 - Fix a size_t underflow in smartlist_join_strings2() that made
6999 it do bad things when you hand it an empty smartlist.
7000 - Fix Windows installer to ship Tor license (thanks to Aphex for
7001 pointing out this oversight) and put a link to the doc directory
7003 - Explicitly set no-unaligned-access for sparc: it turns out the
7004 new gcc's let you compile broken code, but that doesn't make it
7008 Changes in version 0.1.1.3-alpha - 2005-07-23
7009 o Bugfixes on 0.1.1.2-alpha:
7010 - Fix a bug in handling the controller's "post descriptor"
7012 - Fix several bugs in handling the controller's "extend circuit"
7014 - Fix a bug in handling the controller's "stream status" event.
7015 - Fix an assert failure if we have a controller listening for
7016 circuit events and we go offline.
7017 - Re-allow hidden service descriptors to publish 0 intro points.
7018 - Fix a crash when generating your hidden service descriptor if
7019 you don't have enough intro points already.
7021 o New features on 0.1.1.2-alpha:
7022 - New controller function "getinfo accounting", to ask how
7023 many bytes we've used in this time period.
7024 - Experimental support for helper nodes: a lot of the risk from
7025 a small static adversary comes because users pick new random
7026 nodes every time they rebuild a circuit. Now users will try to
7027 stick to the same small set of entry nodes if they can. Not
7028 enabled by default yet.
7030 o Bugfixes on 0.1.0.12:
7031 - If you're an auth dir server, always publish your dirport,
7032 even if you haven't yet found yourself to be reachable.
7033 - Fix a size_t underflow in smartlist_join_strings2() that made
7034 it do bad things when you hand it an empty smartlist.
7037 Changes in version 0.1.0.12 - 2005-07-18
7038 o New directory servers:
7039 - tor26 has changed IP address.
7041 o Bugfixes on 0.1.0.x:
7042 - Fix a possible double-free in tor_gzip_uncompress().
7043 - When --disable-threads is set, do not search for or link against
7045 - Don't trigger an assert if an authoritative directory server
7046 claims its dirport is 0.
7047 - Fix bug with removing Tor as an NT service: some people were
7048 getting "The service did not return an error." Thanks to Matt
7052 Changes in version 0.1.1.2-alpha - 2005-07-15
7053 o New directory servers:
7054 - tor26 has changed IP address.
7056 o Bugfixes on 0.1.0.x, crashes/leaks:
7057 - Port the servers-not-obeying-their-exit-policies fix from
7059 - Fix an fd leak in start_daemon().
7060 - On Windows, you can't always reopen a port right after you've
7061 closed it. So change retry_listeners() to only close and re-open
7062 ports that have changed.
7063 - Fix a possible double-free in tor_gzip_uncompress().
7065 o Bugfixes on 0.1.0.x, usability:
7066 - When tor_socketpair() fails in Windows, give a reasonable
7067 Windows-style errno back.
7068 - Let people type "tor --install" as well as "tor -install" when
7070 want to make it an NT service.
7071 - NT service patch from Matt Edman to improve error messages.
7072 - When the controller asks for a config option with an abbreviated
7073 name, give the full name in our response.
7074 - Correct the man page entry on TrackHostExitsExpire.
7075 - Looks like we were never delivering deflated (i.e. compressed)
7076 running-routers lists, even when asked. Oops.
7077 - When --disable-threads is set, do not search for or link against
7080 o Bugfixes on 0.1.1.x:
7081 - Fix a seg fault with autodetecting which controller version is
7085 - New hidden service descriptor format: put a version in it, and
7086 let people specify introduction/rendezvous points that aren't
7087 in "the directory" (which is subjective anyway).
7088 - Allow the DEBUG controller event to work again. Mark certain log
7089 entries as "don't tell this to controllers", so we avoid cycles.
7092 Changes in version 0.1.0.11 - 2005-06-30
7093 o Bugfixes on 0.1.0.x:
7094 - Fix major security bug: servers were disregarding their
7095 exit policies if clients behaved unexpectedly.
7096 - Make OS X init script check for missing argument, so we don't
7097 confuse users who invoke it incorrectly.
7098 - Fix a seg fault in "tor --hash-password foo".
7099 - The MAPADDRESS control command was broken.
7102 Changes in version 0.1.1.1-alpha - 2005-06-29
7104 - Make OS X init script check for missing argument, so we don't
7105 confuse users who invoke it incorrectly.
7106 - Fix a seg fault in "tor --hash-password foo".
7107 - Fix a possible way to DoS dirservers.
7108 - When we complain that your exit policy implicitly allows local or
7109 private address spaces, name them explicitly so operators can
7111 - Make the log message less scary when all the dirservers are
7112 temporarily unreachable.
7113 - We were printing the number of idle dns workers incorrectly when
7117 - Revised controller protocol (version 1) that uses ascii rather
7118 than binary. Add supporting libraries in python and java so you
7119 can use the controller from your applications without caring how
7121 - Spiffy new support for crypto hardware accelerators. Can somebody
7125 Changes in version 0.0.9.10 - 2005-06-16
7126 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
7127 - Refuse relay cells that claim to have a length larger than the
7128 maximum allowed. This prevents a potential attack that could read
7129 arbitrary memory (e.g. keys) from an exit server's process
7133 Changes in version 0.1.0.10 - 2005-06-14
7134 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
7135 libevent before 1.1a.
7138 Changes in version 0.1.0.9-rc - 2005-06-09
7140 - Reset buf->highwater every time buf_shrink() is called, not just on
7141 a successful shrink. This was causing significant memory bloat.
7142 - Fix buffer overflow when checking hashed passwords.
7143 - Security fix: if seeding the RNG on Win32 fails, quit.
7144 - Allow seeding the RNG on Win32 even when you're not running as
7146 - Disable threading on Solaris too. Something is wonky with it,
7147 cpuworkers, and reentrant libs.
7148 - Reenable the part of the code that tries to flush as soon as an
7149 OR outbuf has a full TLS record available. Perhaps this will make
7150 OR outbufs not grow as huge except in rare cases, thus saving lots
7151 of CPU time plus memory.
7152 - Reject malformed .onion addresses rather then passing them on as
7153 normal web requests.
7154 - Adapt patch from Adam Langley: fix possible memory leak in
7155 tor_lookup_hostname().
7156 - Initialize libevent later in the startup process, so the logs are
7157 already established by the time we start logging libevent warns.
7158 - Use correct errno on win32 if libevent fails.
7159 - Check and warn about known-bad/slow libevent versions.
7160 - Pay more attention to the ClientOnly config option.
7161 - Have torctl.in/tor.sh.in check for location of su binary (needed
7163 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
7164 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
7165 HttpProxyAuthenticator
7166 - Stop warning about sigpipes in the logs. We're going to
7167 pretend that getting these occassionally is normal and fine.
7168 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
7170 installer screens; and don't put stuff into StartupItems unless
7171 the user asks you to.
7172 - Require servers that use the default dirservers to have public IP
7173 addresses. We have too many servers that are configured with private
7174 IPs and their admins never notice the log entries complaining that
7175 their descriptors are being rejected.
7176 - Add OSX uninstall instructions. An actual uninstall script will
7180 Changes in version 0.1.0.8-rc - 2005-05-23
7182 - It turns out that kqueue on OS X 10.3.9 was causing kernel
7183 panics. Disable kqueue on all OS X Tors.
7184 - Fix RPM: remove duplicate line accidentally added to the rpm
7186 - Disable threads on openbsd too, since its gethostaddr is not
7188 - Tolerate libevent 0.8 since it still works, even though it's
7190 - Enable building on Red Hat 9.0 again.
7191 - Allow the middle hop of the testing circuit to be running any
7192 version, now that most of them have the bugfix to let them connect
7193 to unknown servers. This will allow reachability testing to work
7194 even when 0.0.9.7-0.0.9.9 become obsolete.
7195 - Handle relay cells with rh.length too large. This prevents
7196 a potential attack that could read arbitrary memory (maybe even
7197 keys) from the exit server's process.
7198 - We screwed up the dirport reachability testing when we don't yet
7199 have a cached version of the directory. Hopefully now fixed.
7200 - Clean up router_load_single_router() (used by the controller),
7201 so it doesn't seg fault on error.
7202 - Fix a minor memory leak when somebody establishes an introduction
7203 point at your Tor server.
7204 - If a socks connection ends because read fails, don't warn that
7205 you're not sending a socks reply back.
7208 - Add HttpProxyAuthenticator config option too, that works like
7209 the HttpsProxyAuthenticator config option.
7210 - Encode hashed controller passwords in hex instead of base64,
7211 to make it easier to write controllers.
7214 Changes in version 0.1.0.7-rc - 2005-05-17
7216 - Fix a bug in the OS X package installer that prevented it from
7217 installing on Tiger.
7218 - Fix a script bug in the OS X package installer that made it
7219 complain during installation.
7220 - Find libevent even if it's hiding in /usr/local/ and your
7221 CFLAGS and LDFLAGS don't tell you to look there.
7222 - Be able to link with libevent as a shared library (the default
7223 after 1.0d), even if it's hiding in /usr/local/lib and even
7224 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
7225 assuming you're running gcc. Otherwise fail and give a useful
7227 - Fix a bug in the RPM packager: set home directory for _tor to
7228 something more reasonable when first installing.
7229 - Free a minor amount of memory that is still reachable on exit.
7232 Changes in version 0.1.0.6-rc - 2005-05-14
7234 - Implement --disable-threads configure option. Disable threads on
7235 netbsd by default, because it appears to have no reentrant resolver
7237 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
7238 release (1.1) detects and disables kqueue if it's broken.
7239 - Append default exit policy before checking for implicit internal
7240 addresses. Now we don't log a bunch of complaints on startup
7241 when using the default exit policy.
7242 - Some people were putting "Address " in their torrc, and they had
7243 a buggy resolver that resolved " " to 0.0.0.0. Oops.
7244 - If DataDir is ~/.tor, and that expands to /.tor, then default to
7245 LOCALSTATEDIR/tor instead.
7246 - Fix fragmented-message bug in TorControl.py.
7247 - Resolve a minor bug which would prevent unreachable dirports
7248 from getting suppressed in the published descriptor.
7249 - When the controller gave us a new descriptor, we weren't resolving
7250 it immediately, so Tor would think its address was 0.0.0.0 until
7251 we fetched a new directory.
7252 - Fix an uppercase/lowercase case error in suppressing a bogus
7253 libevent warning on some Linuxes.
7256 - Begin scrubbing sensitive strings from logs by default. Turn off
7257 the config option SafeLogging if you need to do debugging.
7258 - Switch to a new buffer management algorithm, which tries to avoid
7259 reallocing and copying quite as much. In first tests it looks like
7260 it uses *more* memory on average, but less cpu.
7261 - First cut at support for "create-fast" cells. Clients can use
7262 these when extending to their first hop, since the TLS already
7263 provides forward secrecy and authentication. Not enabled on
7265 - When dirservers refuse a router descriptor, we now log its
7266 contactinfo, platform, and the poster's IP address.
7267 - Call tor_free_all instead of connections_free_all after forking, to
7268 save memory on systems that need to fork.
7269 - Whine at you if you're a server and you don't set your contactinfo.
7270 - Implement --verify-config command-line option to check if your torrc
7271 is valid without actually launching Tor.
7272 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
7273 rather than just rejecting it.
7276 Changes in version 0.1.0.5-rc - 2005-04-27
7278 - Stop trying to print a null pointer if an OR conn fails because
7279 we didn't like its cert.
7281 - Switch our internal buffers implementation to use a ring buffer,
7282 to hopefully improve performance for fast servers a lot.
7283 - Add HttpsProxyAuthenticator support (basic auth only), based
7284 on patch from Adam Langley.
7285 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
7286 the fast servers that have been joining lately.
7287 - Give hidden service accesses extra time on the first attempt,
7288 since 60 seconds is often only barely enough. This might improve
7290 - Improve performance for dirservers: stop re-parsing the whole
7291 directory every time you regenerate it.
7292 - Add more debugging info to help us find the weird dns freebsd
7293 pthreads bug; cleaner debug messages to help track future issues.
7296 Changes in version 0.0.9.9 - 2005-04-23
7297 o Bugfixes on 0.0.9.x:
7298 - If unofficial Tor clients connect and send weird TLS certs, our
7299 Tor server triggers an assert. This release contains a minimal
7300 backport from the broader fix that we put into 0.1.0.4-rc.
7303 Changes in version 0.1.0.4-rc - 2005-04-23
7305 - If unofficial Tor clients connect and send weird TLS certs, our
7306 Tor server triggers an assert. Stop asserting, and start handling
7307 TLS errors better in other situations too.
7308 - When the controller asks us to tell it about all the debug-level
7309 logs, it turns out we were generating debug-level logs while
7310 telling it about them, which turns into a bad loop. Now keep
7311 track of whether you're sending a debug log to the controller,
7312 and don't log when you are.
7313 - Fix the "postdescriptor" feature of the controller interface: on
7314 non-complete success, only say "done" once.
7316 - Clients are now willing to load balance over up to 2mB, not 1mB,
7317 of advertised bandwidth capacity.
7318 - Add a NoPublish config option, so you can be a server (e.g. for
7319 testing running Tor servers in other Tor networks) without
7320 publishing your descriptor to the primary dirservers.
7323 Changes in version 0.1.0.3-rc - 2005-04-08
7324 o Improvements on 0.1.0.2-rc:
7325 - Client now retries when streams end early for 'hibernating' or
7326 'resource limit' reasons, rather than failing them.
7327 - More automated handling for dirserver operators:
7328 - Automatically approve nodes running 0.1.0.2-rc or later,
7329 now that the the reachability detection stuff is working.
7330 - Now we allow two unverified servers with the same nickname
7331 but different keys. But if a nickname is verified, only that
7332 nickname+key are allowed.
7333 - If you're an authdirserver connecting to an address:port,
7334 and it's not the OR you were expecting, forget about that
7335 descriptor. If he *was* the one you were expecting, then forget
7336 about all other descriptors for that address:port.
7337 - Allow servers to publish descriptors from 12 hours in the future.
7338 Corollary: only whine about clock skew from the dirserver if
7339 he's a trusted dirserver (since now even verified servers could
7340 have quite wrong clocks).
7341 - Adjust maximum skew and age for rendezvous descriptors: let skew
7342 be 48 hours rather than 90 minutes.
7343 - Efficiency improvements:
7344 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
7345 it much faster to look up a circuit for each relay cell.
7346 - Remove most calls to assert_all_pending_dns_resolves_ok(),
7347 since they're eating our cpu on exit nodes.
7348 - Stop wasting time doing a case insensitive comparison for every
7349 dns name every time we do any lookup. Canonicalize the names to
7350 lowercase and be done with it.
7351 - Start sending 'truncated' cells back rather than destroy cells,
7352 if the circuit closes in front of you. This means we won't have
7353 to abandon partially built circuits.
7354 - Only warn once per nickname from add_nickname_list_to_smartlist
7355 per failure, so an entrynode or exitnode choice that's down won't
7357 - Put a note in the torrc about abuse potential with the default
7359 - Revise control spec and implementation to allow all log messages to
7360 be sent to controller with their severities intact (suggested by
7361 Matt Edman). Update TorControl to handle new log event types.
7362 - Provide better explanation messages when controller's POSTDESCRIPTOR
7364 - Stop putting nodename in the Platform string in server descriptors.
7365 It doesn't actually help, and it is confusing/upsetting some people.
7367 o Bugfixes on 0.1.0.2-rc:
7368 - We were printing the host mask wrong in exit policies in server
7369 descriptors. This isn't a critical bug though, since we were still
7370 obeying the exit policy internally.
7371 - Fix Tor when compiled with libevent but without pthreads: move
7372 connection_unregister() from _connection_free() to
7374 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
7375 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
7376 when we look through the connection array, we'll find any of the
7377 cpu/dnsworkers. This is no good.
7379 o Bugfixes on 0.0.9.8:
7380 - Fix possible bug on threading platforms (e.g. win32) which was
7381 leaking a file descriptor whenever a cpuworker or dnsworker died.
7382 - When using preferred entry or exit nodes, ignore whether the
7383 circuit wants uptime or capacity. They asked for the nodes, they
7385 - chdir() to your datadirectory at the *end* of the daemonize process,
7386 not the beginning. This was a problem because the first time you
7387 run tor, if your datadir isn't there, and you have runasdaemon set
7388 to 1, it will try to chdir to it before it tries to create it. Oops.
7389 - Handle changed router status correctly when dirserver reloads
7390 fingerprint file. We used to be dropping all unverified descriptors
7391 right then. The bug was hidden because we would immediately
7392 fetch a directory from another dirserver, which would include the
7393 descriptors we just dropped.
7394 - When we're connecting to an OR and he's got a different nickname/key
7395 than we were expecting, only complain loudly if we're an OP or a
7396 dirserver. Complaining loudly to the OR admins just confuses them.
7397 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
7398 artificially capped at 500kB.
7401 Changes in version 0.0.9.8 - 2005-04-07
7402 o Bugfixes on 0.0.9.x:
7403 - We have a bug that I haven't found yet. Sometimes, very rarely,
7404 cpuworkers get stuck in the 'busy' state, even though the cpuworker
7405 thinks of itself as idle. This meant that no new circuits ever got
7406 established. Here's a workaround to kill any cpuworker that's been
7407 busy for more than 100 seconds.
7410 Changes in version 0.1.0.2-rc - 2005-04-01
7411 o Bugfixes on 0.1.0.1-rc:
7412 - Fixes on reachability detection:
7413 - Don't check for reachability while hibernating.
7414 - If ORPort is reachable but DirPort isn't, still publish the
7415 descriptor, but zero out DirPort until it's found reachable.
7416 - When building testing circs for ORPort testing, use only
7417 high-bandwidth nodes, so fewer circuits fail.
7418 - Complain about unreachable ORPort separately from unreachable
7419 DirPort, so the user knows what's going on.
7420 - Make sure we only conclude ORPort reachability if we didn't
7421 initiate the conn. Otherwise we could falsely conclude that
7422 we're reachable just because we connected to the guy earlier
7423 and he used that same pipe to extend to us.
7424 - Authdirservers shouldn't do ORPort reachability detection,
7425 since they're in clique mode, so it will be rare to find a
7426 server not already connected to them.
7427 - When building testing circuits, always pick middle hops running
7428 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
7429 bug. (This is a kludge; it will go away when 0.0.9.x becomes
7431 - When we decide we're reachable, actually publish our descriptor
7433 - Fix bug in redirectstream in the controller.
7434 - Fix the state descriptor strings so logs don't claim edge streams
7435 are in a different state than they actually are.
7436 - Use recent libevent features when possible (this only really affects
7437 win32 and osx right now, because the new libevent with these
7438 features hasn't been released yet). Add code to suppress spurious
7440 - Prevent possible segfault in connection_close_unattached_ap().
7441 - Fix newlines on torrc in win32.
7442 - Improve error msgs when tor-resolve fails.
7444 o Improvements on 0.0.9.x:
7445 - New experimental script tor/contrib/ExerciseServer.py (needs more
7446 work) that uses the controller interface to build circuits and
7447 fetch pages over them. This will help us bootstrap servers that
7448 have lots of capacity but haven't noticed it yet.
7449 - New experimental script tor/contrib/PathDemo.py (needs more work)
7450 that uses the controller interface to let you choose whole paths
7452 "<hostname>.<path,separated by dots>.<length of path>.path"
7453 - When we've connected to an OR and handshaked but didn't like
7454 the result, we were closing the conn without sending destroy
7455 cells back for pending circuits. Now send those destroys.
7458 Changes in version 0.0.9.7 - 2005-04-01
7459 o Bugfixes on 0.0.9.x:
7460 - Fix another race crash bug (thanks to Glenn Fink for reporting).
7461 - Compare identity to identity, not to nickname, when extending to
7462 a router not already in the directory. This was preventing us from
7463 extending to unknown routers. Oops.
7464 - Make sure to create OS X Tor user in <500 range, so we aren't
7465 creating actual system users.
7466 - Note where connection-that-hasn't-sent-end was marked, and fix
7467 a few really loud instances of this harmless bug (it's fixed more
7471 Changes in version 0.1.0.1-rc - 2005-03-28
7473 - Add reachability testing. Your Tor server will automatically try
7474 to see if its ORPort and DirPort are reachable from the outside,
7475 and it won't upload its descriptor until it decides they are.
7476 - Handle unavailable hidden services better. Handle slow or busy
7477 hidden services better.
7478 - Add support for CONNECTing through https proxies, with "HttpsProxy"
7480 - New exit policy: accept most low-numbered ports, rather than
7481 rejecting most low-numbered ports.
7482 - More Tor controller support (still experimental). See
7483 http://tor.eff.org/doc/control-spec.txt for all the new features,
7484 including signals to emulate unix signals from any platform;
7485 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
7486 closestream; closecircuit; etc.
7487 - Make nt services work and start on startup on win32 (based on
7488 patch by Matt Edman).
7489 - Add a new AddressMap config directive to rewrite incoming socks
7490 addresses. This lets you, for example, declare an implicit
7491 required exit node for certain sites.
7492 - Add a new TrackHostExits config directive to trigger addressmaps
7493 for certain incoming socks addresses -- for sites that break when
7494 your exit keeps changing (based on patch by Mike Perry).
7495 - Redo the client-side dns cache so it's just an addressmap too.
7496 - Notice when our IP changes, and reset stats/uptime/reachability.
7497 - When an application is using socks5, give him the whole variety of
7498 potential socks5 responses (connect refused, host unreachable, etc),
7499 rather than just "success" or "failure".
7500 - A more sane version numbering system. See
7501 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
7502 - New contributed script "exitlist": a simple python script to
7503 parse directories and find Tor nodes that exit to listed
7505 - New contributed script "privoxy-tor-toggle" to toggle whether
7506 Privoxy uses Tor. Seems to be configured for Debian by default.
7507 - Report HTTP reasons to client when getting a response from directory
7508 servers -- so you can actually know what went wrong.
7509 - New config option MaxAdvertisedBandwidth which lets you advertise
7510 a low bandwidthrate (to not attract as many circuits) while still
7511 allowing a higher bandwidthrate in reality.
7513 o Robustness/stability fixes:
7514 - Make Tor use Niels Provos's libevent instead of its current
7515 poll-but-sometimes-select mess. This will let us use faster async
7516 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
7518 - pthread support now too. This was forced because when we forked,
7519 we ended up wasting a lot of duplicate ram over time. Also switch
7520 to foo_r versions of some library calls to allow reentry and
7522 - Better handling for heterogeneous / unreliable nodes:
7523 - Annotate circuits w/ whether they aim to contain high uptime nodes
7524 and/or high capacity nodes. When building circuits, choose
7526 - This means that every single node in an intro rend circuit,
7527 not just the last one, will have a minimum uptime.
7528 - New config option LongLivedPorts to indicate application streams
7529 that will want high uptime circuits.
7530 - Servers reset uptime when a dir fetch entirely fails. This
7531 hopefully reflects stability of the server's network connectivity.
7532 - If somebody starts his tor server in Jan 2004 and then fixes his
7533 clock, don't make his published uptime be a year.
7534 - Reset published uptime when you wake up from hibernation.
7535 - Introduce a notion of 'internal' circs, which are chosen without
7536 regard to the exit policy of the last hop. Intro and rendezvous
7537 circs must be internal circs, to avoid leaking information. Resolve
7538 and connect streams can use internal circs if they want.
7539 - New circuit pooling algorithm: make sure to have enough circs around
7540 to satisfy any predicted ports, and also make sure to have 2 internal
7541 circs around if we've required internal circs lately (and with high
7542 uptime if we've seen that lately too).
7543 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
7544 which describes how often we retry making new circuits if current
7545 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
7546 how long we're willing to make use of an already-dirty circuit.
7547 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
7548 circ as necessary, if there are any completed ones lying around
7549 when we try to launch one.
7550 - Make hidden services try to establish a rendezvous for 30 seconds,
7551 rather than for n (where n=3) attempts to build a circuit.
7552 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
7553 "ShutdownWaitLength".
7554 - Try to be more zealous about calling connection_edge_end when
7555 things go bad with edge conns in connection.c.
7556 - Revise tor-spec to add more/better stream end reasons.
7557 - Revise all calls to connection_edge_end to avoid sending "misc",
7558 and to take errno into account where possible.
7561 - Fix a race condition that can trigger an assert, when we have a
7562 pending create cell and an OR connection fails right then.
7563 - Fix several double-mark-for-close bugs, e.g. where we were finding
7564 a conn for a cell even if that conn is already marked for close.
7565 - Make sequence of log messages when starting on win32 with no config
7566 file more reasonable.
7567 - When choosing an exit node for a new non-internal circ, don't take
7568 into account whether it'll be useful for any pending x.onion
7569 addresses -- it won't.
7570 - Turn addr_policy_compare from a tristate to a quadstate; this should
7571 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
7572 for google.com" problem.
7573 - Make "platform" string in descriptor more accurate for Win32 servers,
7574 so it's not just "unknown platform".
7575 - Fix an edge case in parsing config options (thanks weasel).
7576 If they say "--" on the commandline, it's not an option.
7577 - Reject odd-looking addresses at the client (e.g. addresses that
7578 contain a colon), rather than having the server drop them because
7580 - tor-resolve requests were ignoring .exit if there was a working circuit
7581 they could use instead.
7582 - REUSEADDR on normal platforms means you can rebind to the port
7583 right after somebody else has let it go. But REUSEADDR on win32
7584 means to let you bind to the port _even when somebody else
7585 already has it bound_! So, don't do that on Win32.
7586 - Change version parsing logic: a version is "obsolete" if it is not
7587 recommended and (1) there is a newer recommended version in the
7588 same series, or (2) there are no recommended versions in the same
7589 series, but there are some recommended versions in a newer series.
7590 A version is "new" if it is newer than any recommended version in
7592 - Stop most cases of hanging up on a socks connection without sending
7596 - Require BandwidthRate to be at least 20kB/s for servers.
7597 - When a dirserver causes you to give a warn, mention which dirserver
7599 - New config option DirAllowPrivateAddresses for authdirservers.
7600 Now by default they refuse router descriptors that have non-IP or
7601 private-IP addresses.
7602 - Stop publishing socksport in the directory, since it's not
7603 actually meant to be public. For compatibility, publish a 0 there
7605 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
7606 smart" value, that is low for servers and high for clients.
7607 - If our clock jumps forward by 100 seconds or more, assume something
7608 has gone wrong with our network and abandon all not-yet-used circs.
7609 - Warn when exit policy implicitly allows local addresses.
7610 - If we get an incredibly skewed timestamp from a dirserver mirror
7611 that isn't a verified OR, don't warn -- it's probably him that's
7613 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
7614 cookies to disk and doesn't log each web request to disk. (Thanks
7615 to Brett Carrington for pointing this out.)
7616 - When a client asks us for a dir mirror and we don't have one,
7617 launch an attempt to get a fresh one.
7618 - If we're hibernating and we get a SIGINT, exit immediately.
7619 - Add --with-dmalloc ./configure option, to track memory leaks.
7620 - And try to free all memory on closing, so we can detect what
7622 - Cache local dns resolves correctly even when they're .exit
7624 - Give a better warning when some other server advertises an
7625 ORPort that is actually an apache running ssl.
7626 - Add "opt hibernating 1" to server descriptor to make it clearer
7627 whether the server is hibernating.
7630 Changes in version 0.0.9.6 - 2005-03-24
7631 o Bugfixes on 0.0.9.x (crashes and asserts):
7632 - Add new end stream reasons to maintainance branch. Fix bug where
7633 reason (8) could trigger an assert. Prevent bug from recurring.
7634 - Apparently win32 stat wants paths to not end with a slash.
7635 - Fix assert triggers in assert_cpath_layer_ok(), where we were
7636 blowing away the circuit that conn->cpath_layer points to, then
7637 checking to see if the circ is well-formed. Backport check to make
7638 sure we dont use the cpath on a closed connection.
7639 - Prevent circuit_resume_edge_reading_helper() from trying to package
7640 inbufs for marked-for-close streams.
7641 - Don't crash on hup if your options->address has become unresolvable.
7642 - Some systems (like OS X) sometimes accept() a connection and tell
7643 you the remote host is 0.0.0.0:0. If this happens, due to some
7644 other mis-features, we get confused; so refuse the conn for now.
7646 o Bugfixes on 0.0.9.x (other):
7647 - Fix harmless but scary "Unrecognized content encoding" warn message.
7648 - Add new stream error reason: TORPROTOCOL reason means "you are not
7649 speaking a version of Tor I understand; say bye-bye to your stream."
7650 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
7651 into the future, now that we are more tolerant of skew. This
7652 resolves a bug where a Tor server would refuse to cache a directory
7653 because all the directories it gets are too far in the future;
7654 yet the Tor server never logs any complaints about clock skew.
7655 - Mac packaging magic: make man pages useable, and do not overwrite
7656 existing torrc files.
7657 - Make OS X log happily to /var/log/tor/tor.log
7660 Changes in version 0.0.9.5 - 2005-02-22
7661 o Bugfixes on 0.0.9.x:
7662 - Fix an assert race at exit nodes when resolve requests fail.
7663 - Stop picking unverified dir mirrors--it only leads to misery.
7664 - Patch from Matt Edman to make NT services work better. Service
7665 support is still not compiled into the executable by default.
7666 - Patch from Dmitri Bely so the Tor service runs better under
7667 the win32 SYSTEM account.
7668 - Make tor-resolve actually work (?) on Win32.
7669 - Fix a sign bug when getrlimit claims to have 4+ billion
7670 file descriptors available.
7671 - Stop refusing to start when bandwidthburst == bandwidthrate.
7672 - When create cells have been on the onion queue more than five
7673 seconds, just send back a destroy and take them off the list.
7676 Changes in version 0.0.9.4 - 2005-02-03
7677 o Bugfixes on 0.0.9:
7678 - Fix an assert bug that took down most of our servers: when
7679 a server claims to have 1 GB of bandwidthburst, don't
7681 - Don't crash as badly if we have spawned the max allowed number
7682 of dnsworkers, or we're out of file descriptors.
7683 - Block more file-sharing ports in the default exit policy.
7684 - MaxConn is now automatically set to the hard limit of max
7685 file descriptors we're allowed (ulimit -n), minus a few for
7687 - Give a clearer message when servers need to raise their
7688 ulimit -n when they start running out of file descriptors.
7689 - SGI Compatibility patches from Jan Schaumann.
7690 - Tolerate a corrupt cached directory better.
7691 - When a dirserver hasn't approved your server, list which one.
7692 - Go into soft hibernation after 95% of the bandwidth is used,
7693 not 99%. This is especially important for daily hibernators who
7694 have a small accounting max. Hopefully it will result in fewer
7695 cut connections when the hard hibernation starts.
7696 - Load-balance better when using servers that claim more than
7697 800kB/s of capacity.
7698 - Make NT services work (experimental, only used if compiled in).
7701 Changes in version 0.0.9.3 - 2005-01-21
7702 o Bugfixes on 0.0.9:
7703 - Backport the cpu use fixes from main branch, so busy servers won't
7704 need as much processor time.
7705 - Work better when we go offline and then come back, or when we
7706 run Tor at boot before the network is up. We do this by
7707 optimistically trying to fetch a new directory whenever an
7708 application request comes in and we think we're offline -- the
7709 human is hopefully a good measure of when the network is back.
7710 - Backport some minimal hidserv bugfixes: keep rend circuits open as
7711 long as you keep using them; actually publish hidserv descriptors
7712 shortly after they change, rather than waiting 20-40 minutes.
7713 - Enable Mac startup script by default.
7714 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
7715 - When you update AllowUnverifiedNodes or FirewallPorts via the
7716 controller's setconf feature, we were always appending, never
7718 - When you update HiddenServiceDir via setconf, it was screwing up
7719 the order of reading the lines, making it fail.
7720 - Do not rewrite a cached directory back to the cache; otherwise we
7721 will think it is recent and not fetch a newer one on startup.
7722 - Workaround for webservers that lie about Content-Encoding: Tor
7723 now tries to autodetect compressed directories and compression
7724 itself. This lets us Proxypass dir fetches through apache.
7727 Changes in version 0.0.9.2 - 2005-01-04
7728 o Bugfixes on 0.0.9 (crashes and asserts):
7729 - Fix an assert on startup when the disk is full and you're logging
7731 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
7732 style address, then we'd crash.
7733 - Fix an assert trigger when the running-routers string we get from
7734 a dirserver is broken.
7735 - Make worker threads start and run on win32. Now win32 servers
7737 - Bandaid (not actually fix, but now it doesn't crash) an assert
7738 where the dns worker dies mysteriously and the main Tor process
7739 doesn't remember anything about the address it was resolving.
7741 o Bugfixes on 0.0.9 (Win32):
7742 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
7743 name out of the warning/assert messages.
7744 - Fix a superficial "unhandled error on read" bug on win32.
7745 - The win32 installer no longer requires a click-through for our
7746 license, since our Free Software license grants rights but does not
7748 - Win32: When connecting to a dirserver fails, try another one
7749 immediately. (This was already working for non-win32 Tors.)
7750 - Stop trying to parse $HOME on win32 when hunting for default
7752 - Make tor-resolve.c work on win32 by calling network_init().
7754 o Bugfixes on 0.0.9 (other):
7755 - Make 0.0.9.x build on Solaris again.
7756 - Due to a fencepost error, we were blowing away the \n when reporting
7757 confvalue items in the controller. So asking for multiple config
7758 values at once couldn't work.
7759 - When listing circuits that are pending on an opening OR connection,
7760 if we're an OR we were listing circuits that *end* at us as
7761 being pending on every listener, dns/cpu worker, etc. Stop that.
7762 - Dirservers were failing to create 'running-routers' or 'directory'
7763 strings if we had more than some threshold of routers. Fix them so
7764 they can handle any number of routers.
7765 - Fix a superficial "Duplicate mark for close" bug.
7766 - Stop checking for clock skew for OR connections, even for servers.
7767 - Fix a fencepost error that was chopping off the last letter of any
7768 nickname that is the maximum allowed nickname length.
7769 - Update URLs in log messages so they point to the new website.
7770 - Fix a potential problem in mangling server private keys while
7771 writing to disk (not triggered yet, as far as we know).
7772 - Include the licenses for other free software we include in Tor,
7773 now that we're shipping binary distributions more regularly.
7776 Changes in version 0.0.9.1 - 2004-12-15
7777 o Bugfixes on 0.0.9:
7778 - Make hibernation actually work.
7779 - Make HashedControlPassword config option work.
7780 - When we're reporting event circuit status to a controller,
7781 don't use the stream status code.
7784 Changes in version 0.0.9 - 2004-12-12
7786 - Clean up manpage and torrc.sample file.
7787 - Clean up severities and text of log warnings.
7789 - Make servers trigger an assert when they enter hibernation.
7792 Changes in version 0.0.9rc7 - 2004-12-08
7793 o Bugfixes on 0.0.9rc:
7794 - Fix a stack-trashing crash when an exit node begins hibernating.
7795 - Avoid looking at unallocated memory while considering which
7796 ports we need to build circuits to cover.
7797 - Stop a sigpipe: when an 'end' cell races with eof from the app,
7798 we shouldn't hold-open-until-flush if the eof arrived first.
7799 - Fix a bug with init_cookie_authentication() in the controller.
7800 - When recommending new-format log lines, if the upper bound is
7801 LOG_ERR, leave it implicit.
7803 o Bugfixes on 0.0.8.1:
7804 - Fix a whole slew of memory leaks.
7805 - Fix isspace() and friends so they still make Solaris happy
7806 but also so they don't trigger asserts on win32.
7807 - Fix parse_iso_time on platforms without strptime (eg win32).
7808 - win32: tolerate extra "readable" events better.
7809 - win32: when being multithreaded, leave parent fdarray open.
7810 - Make unit tests work on win32.
7813 Changes in version 0.0.9rc6 - 2004-12-06
7814 o Bugfixes on 0.0.9pre:
7815 - Clean up some more integer underflow opportunities (not exploitable
7817 - While hibernating, hup should not regrow our listeners.
7818 - Send an end to the streams we close when we hibernate, rather
7819 than just chopping them off.
7820 - React to eof immediately on non-open edge connections.
7822 o Bugfixes on 0.0.8.1:
7823 - Calculate timeout for waiting for a connected cell from the time
7824 we sent the begin cell, not from the time the stream started. If
7825 it took a long time to establish the circuit, we would time out
7826 right after sending the begin cell.
7827 - Fix router_compare_addr_to_addr_policy: it was not treating a port
7828 of * as always matching, so we were picking reject *:* nodes as
7829 exit nodes too. Oops.
7832 - New circuit building strategy: keep a list of ports that we've
7833 used in the past 6 hours, and always try to have 2 circuits open
7834 or on the way that will handle each such port. Seed us with port
7835 80 so web users won't complain that Tor is "slow to start up".
7836 - Make kill -USR1 dump more useful stats about circuits.
7837 - When warning about retrying or giving up, print the address, so
7838 the user knows which one it's talking about.
7839 - If you haven't used a clean circuit in an hour, throw it away,
7840 just to be on the safe side. (This means after 6 hours a totally
7841 unused Tor client will have no circuits open.)
7844 Changes in version 0.0.9rc5 - 2004-12-01
7845 o Bugfixes on 0.0.8.1:
7846 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
7847 - Let resolve conns retry/expire also, rather than sticking around
7849 - If we are using select, make sure we stay within FD_SETSIZE.
7851 o Bugfixes on 0.0.9pre:
7852 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
7853 but doesn't seem to be currently; thanks to Ilja van Sprundel for
7855 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
7856 instead. Impose minima and maxima for all *Period options; impose
7857 even tighter maxima for fetching if we are a caching dirserver.
7858 Clip rather than rejecting.
7859 - Fetch cached running-routers from servers that serve it (that is,
7860 authdirservers and servers running 0.0.9rc5-cvs or later.)
7863 - Accept *:706 (silc) in default exit policy.
7864 - Implement new versioning format for post 0.1.
7865 - Support "foo.nickname.exit" addresses, to let Alice request the
7866 address "foo" as viewed by exit node "nickname". Based on a patch
7868 - Make tor --version --version dump the cvs Id of every file.
7871 Changes in version 0.0.9rc4 - 2004-11-28
7872 o Bugfixes on 0.0.8.1:
7873 - Make windows sockets actually non-blocking (oops), and handle
7874 win32 socket errors better.
7876 o Bugfixes on 0.0.9rc1:
7877 - Actually catch the -USR2 signal.
7880 Changes in version 0.0.9rc3 - 2004-11-25
7881 o Bugfixes on 0.0.8.1:
7882 - Flush the log file descriptor after we print "Tor opening log file",
7883 so we don't see those messages days later.
7885 o Bugfixes on 0.0.9rc1:
7886 - Make tor-resolve work again.
7887 - Avoid infinite loop in tor-resolve if tor hangs up on it.
7888 - Fix an assert trigger for clients/servers handling resolves.
7891 Changes in version 0.0.9rc2 - 2004-11-24
7892 o Bugfixes on 0.0.9rc1:
7893 - I broke socks5 support while fixing the eof bug.
7894 - Allow unitless bandwidths and intervals; they default to bytes
7896 - New servers don't start out hibernating; they are active until
7897 they run out of bytes, so they have a better estimate of how
7898 long it takes, and so their operators can know they're working.
7901 Changes in version 0.0.9rc1 - 2004-11-23
7902 o Bugfixes on 0.0.8.1:
7903 - Finally fix a bug that's been plaguing us for a year:
7904 With high load, circuit package window was reaching 0. Whenever
7905 we got a circuit-level sendme, we were reading a lot on each
7906 socket, but only writing out a bit. So we would eventually reach
7907 eof. This would be noticed and acted on even when there were still
7908 bytes sitting in the inbuf.
7909 - When poll() is interrupted, we shouldn't believe the revents values.
7911 o Bugfixes on 0.0.9pre6:
7912 - Fix hibernate bug that caused pre6 to be broken.
7913 - Don't keep rephist info for routers that haven't had activity for
7914 24 hours. (This matters now that clients have keys, since we track
7916 - Never call close_temp_logs while validating log options.
7917 - Fix backslash-escaping on tor.sh.in and torctl.in.
7920 - Implement weekly/monthly/daily accounting: now you specify your
7921 hibernation properties by
7922 AccountingMax N bytes|KB|MB|GB|TB
7923 AccountingStart day|week|month [day] HH:MM
7924 Defaults to "month 1 0:00".
7925 - Let bandwidth and interval config options be specified as 5 bytes,
7926 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
7927 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
7928 get back to normal.)
7929 - If your requested entry or exit node has advertised bandwidth 0,
7931 - Be more greedy about filling up relay cells -- we try reading again
7932 once we've processed the stuff we read, in case enough has arrived
7933 to fill the last cell completely.
7934 - Apply NT service patch from Osamu Fujino. Still needs more work.
7937 Changes in version 0.0.9pre6 - 2004-11-15
7938 o Bugfixes on 0.0.8.1:
7939 - Fix assert failure on malformed socks4a requests.
7940 - Use identity comparison, not nickname comparison, to choose which
7941 half of circuit-ID-space each side gets to use. This is needed
7942 because sometimes we think of a router as a nickname, and sometimes
7943 as a hex ID, and we can't predict what the other side will do.
7944 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
7945 write() call will fail and we handle it there.
7946 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
7947 and smartlist_len, which are two major profiling offenders.
7949 o Bugfixes on 0.0.9pre5:
7950 - Fix a bug in read_all that was corrupting config files on windows.
7951 - When we're raising the max number of open file descriptors to
7952 'unlimited', don't log that we just raised it to '-1'.
7953 - Include event code with events, as required by control-spec.txt.
7954 - Don't give a fingerprint when clients do --list-fingerprint:
7955 it's misleading, because it will never be the same again.
7956 - Stop using strlcpy in tor_strndup, since it was slowing us
7958 - Remove warn on startup about missing cached-directory file.
7959 - Make kill -USR1 work again.
7960 - Hibernate if we start tor during the "wait for wakeup-time" phase
7961 of an accounting interval. Log our hibernation plans better.
7962 - Authoritative dirservers now also cache their directory, so they
7963 have it on start-up.
7966 - Fetch running-routers; cache running-routers; compress
7967 running-routers; serve compressed running-routers.z
7968 - Add NSI installer script contributed by J Doe.
7969 - Commit VC6 and VC7 workspace/project files.
7970 - Commit a tor.spec for making RPM files, with help from jbash.
7971 - Add contrib/torctl.in contributed by Glenn Fink.
7972 - Implement the control-spec's SAVECONF command, to write your
7973 configuration to torrc.
7974 - Get cookie authentication for the controller closer to working.
7975 - Include control-spec.txt in the tarball.
7976 - When set_conf changes our server descriptor, upload a new copy.
7977 But don't upload it too often if there are frequent changes.
7978 - Document authentication config in man page, and document signals
7980 - Clean up confusing parts of man page and torrc.sample.
7981 - Make expand_filename handle ~ and ~username.
7982 - Use autoconf to enable largefile support where necessary. Use
7983 ftello where available, since ftell can fail at 2GB.
7984 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
7985 log more informatively.
7986 - Give a slightly more useful output for "tor -h".
7987 - Refuse application socks connections to port 0.
7988 - Check clock skew for verified servers, but allow unverified
7989 servers and clients to have any clock skew.
7990 - Break DirFetchPostPeriod into:
7991 - DirFetchPeriod for fetching full directory,
7992 - StatusFetchPeriod for fetching running-routers,
7993 - DirPostPeriod for posting server descriptor,
7994 - RendPostPeriod for posting hidden service descriptors.
7995 - Make sure the hidden service descriptors are at a random offset
7996 from each other, to hinder linkability.
7999 Changes in version 0.0.9pre5 - 2004-11-09
8000 o Bugfixes on 0.0.9pre4:
8001 - Fix a seg fault in unit tests (doesn't affect main program).
8002 - Fix an assert bug where a hidden service provider would fail if
8003 the first hop of his rendezvous circuit was down.
8004 - Hidden service operators now correctly handle version 1 style
8005 INTRODUCE1 cells (nobody generates them still, so not a critical
8007 - If do_hup fails, actually notice.
8008 - Handle more errnos from accept() without closing the listener.
8009 Some OpenBSD machines were closing their listeners because
8010 they ran out of file descriptors.
8011 - Send resolve cells to exit routers that are running a new
8012 enough version of the resolve code to work right.
8013 - Better handling of winsock includes on non-MSV win32 compilers.
8014 - Some people had wrapped their tor client/server in a script
8015 that would restart it whenever it died. This did not play well
8016 with our "shut down if your version is obsolete" code. Now people
8017 don't fetch a new directory if their local cached version is
8019 - Make our autogen.sh work on ksh as well as bash.
8022 - Hibernation: New config option "AccountingMaxKB" lets you
8023 set how many KBytes per month you want to allow your server to
8024 consume. Rather than spreading those bytes out evenly over the
8025 month, we instead hibernate for some of the month and pop up
8026 at a deterministic time, work until the bytes are consumed, then
8027 hibernate again. Config option "MonthlyAccountingStart" lets you
8028 specify which day of the month your billing cycle starts on.
8029 - Control interface: a separate program can now talk to your
8030 client/server over a socket, and get/set config options, receive
8031 notifications of circuits and streams starting/finishing/dying,
8032 bandwidth used, etc. The next step is to get some GUIs working.
8033 Let us know if you want to help out. See doc/control-spec.txt .
8034 - Ship a contrib/tor-control.py as an example script to interact
8035 with the control port.
8036 - "tor --hash-password zzyxz" will output a salted password for
8037 use in authenticating to the control interface.
8038 - New log format in config:
8039 "Log minsev[-maxsev] stdout|stderr|syslog" or
8040 "Log minsev[-maxsev] file /var/foo"
8043 - DirPolicy config option, to let people reject incoming addresses
8044 from their dirserver.
8045 - "tor --list-fingerprint" will list your identity key fingerprint
8047 - Add "pass" target for RedirectExit, to make it easier to break
8048 out of a sequence of RedirectExit rules.
8049 - Clients now generate a TLS cert too, in preparation for having
8050 them act more like real nodes.
8051 - Ship src/win32/ in the tarball, so people can use it to build.
8052 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
8054 - New "router-status" line in directory, to better bind each verified
8055 nickname to its identity key.
8056 - Deprecate unofficial config option abbreviations, and abbreviations
8057 not on the command line.
8058 - Add a pure-C tor-resolve implementation.
8059 - Use getrlimit and friends to ensure we can reach MaxConn (currently
8060 1024) file descriptors.
8062 o Code security improvements, inspired by Ilja:
8063 - Replace sprintf with snprintf. (I think they were all safe, but
8065 - Replace strcpy/strncpy with strlcpy in more places.
8066 - Avoid strcat; use snprintf or strlcat instead.
8067 - snprintf wrapper with consistent (though not C99) overflow behavior.
8070 Changes in version 0.0.9pre4 - 2004-10-17
8071 o Bugfixes on 0.0.9pre3:
8072 - If the server doesn't specify an exit policy, use the real default
8073 exit policy, not reject *:*.
8074 - Ignore fascistfirewall when uploading/downloading hidden service
8075 descriptors, since we go through Tor for those; and when using
8076 an HttpProxy, since we assume it can reach them all.
8077 - When looking for an authoritative dirserver, use only the ones
8078 configured at boot. Don't bother looking in the directory.
8079 - The rest of the fix for get_default_conf_file() on older win32.
8080 - Make 'Routerfile' config option obsolete.
8083 - New 'MyFamily nick1,...' config option for a server to
8084 specify other servers that shouldn't be used in the same circuit
8085 with it. Only believed if nick1 also specifies us.
8086 - New 'NodeFamily nick1,nick2,...' config option for a client to
8087 specify nodes that it doesn't want to use in the same circuit.
8088 - New 'Redirectexit pattern address:port' config option for a
8089 server to redirect exit connections, e.g. to a local squid.
8092 Changes in version 0.0.9pre3 - 2004-10-13
8093 o Bugfixes on 0.0.8.1:
8094 - Better torrc example lines for dirbindaddress and orbindaddress.
8095 - Improved bounds checking on parsed ints (e.g. config options and
8096 the ones we find in directories.)
8097 - Better handling of size_t vs int, so we're more robust on 64
8099 - Fix the rest of the bug where a newly started OR would appear
8100 as unverified even after we've added his fingerprint and hupped
8102 - Fix a bug from 0.0.7: when read() failed on a stream, we would
8103 close it without sending back an end. So 'connection refused'
8104 would simply be ignored and the user would get no response.
8106 o Bugfixes on 0.0.9pre2:
8107 - Serving the cached-on-disk directory to people is bad. We now
8108 provide no directory until we've fetched a fresh one.
8109 - Workaround for bug on windows where cached-directories get crlf
8111 - Make get_default_conf_file() work on older windows too.
8112 - If we write a *:* exit policy line in the descriptor, don't write
8113 any more exit policy lines.
8116 - Use only 0.0.9pre1 and later servers for resolve cells.
8117 - Make the dirservers file obsolete.
8118 - Include a dir-signing-key token in directories to tell the
8119 parsing entity which key is being used to sign.
8120 - Remove the built-in bulky default dirservers string.
8121 - New config option "Dirserver %s:%d [fingerprint]", which can be
8122 repeated as many times as needed. If no dirservers specified,
8123 default to moria1,moria2,tor26.
8124 - Make moria2 advertise a dirport of 80, so people behind firewalls
8125 will be able to get a directory.
8126 - Http proxy support
8127 - Dirservers translate requests for http://%s:%d/x to /x
8128 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
8129 be routed through this host.
8130 - Clients ask for /tor/x rather than /x for new enough dirservers.
8131 This way we can one day coexist peacefully with apache.
8132 - Clients specify a "Host: %s%d" http header, to be compatible
8133 with more proxies, and so running squid on an exit node can work.
8136 Changes in version 0.0.8.1 - 2004-10-13
8138 - Fix a seg fault that can be triggered remotely for Tor
8139 clients/servers with an open dirport.
8140 - Fix a rare assert trigger, where routerinfos for entries in
8141 our cpath would expire while we're building the path.
8142 - Fix a bug in OutboundBindAddress so it (hopefully) works.
8143 - Fix a rare seg fault for people running hidden services on
8144 intermittent connections.
8145 - Fix a bug in parsing opt keywords with objects.
8146 - Fix a stale pointer assert bug when a stream detaches and
8148 - Fix a string format vulnerability (probably not exploitable)
8149 in reporting stats locally.
8150 - Fix an assert trigger: sometimes launching circuits can fail
8151 immediately, e.g. because too many circuits have failed recently.
8152 - Fix a compile warning on 64 bit platforms.
8155 Changes in version 0.0.9pre2 - 2004-10-03
8157 - Make fetching a cached directory work for 64-bit platforms too.
8158 - Make zlib.h a required header, not an optional header.
8161 Changes in version 0.0.9pre1 - 2004-10-01
8163 - Stop using separate defaults for no-config-file and
8164 empty-config-file. Now you have to explicitly turn off SocksPort,
8165 if you don't want it open.
8166 - Fix a bug in OutboundBindAddress so it (hopefully) works.
8167 - Improve man page to mention more of the 0.0.8 features.
8168 - Fix a rare seg fault for people running hidden services on
8169 intermittent connections.
8170 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
8172 - Fix more dns related bugs: send back resolve_failed and end cells
8173 more reliably when the resolve fails, rather than closing the
8174 circuit and then trying to send the cell. Also attach dummy resolve
8175 connections to a circuit *before* calling dns_resolve(), to fix
8176 a bug where cached answers would never be sent in RESOLVED cells.
8177 - When we run out of disk space, or other log writing error, don't
8178 crash. Just stop logging to that log and continue.
8179 - We were starting to daemonize before we opened our logs, so if
8180 there were any problems opening logs, we would complain to stderr,
8181 which wouldn't work, and then mysteriously exit.
8182 - Fix a rare bug where sometimes a verified OR would connect to us
8183 before he'd uploaded his descriptor, which would cause us to
8184 assign conn->nickname as though he's unverified. Now we look through
8185 the fingerprint list to see if he's there.
8186 - Fix a rare assert trigger, where routerinfos for entries in
8187 our cpath would expire while we're building the path.
8190 - Clients can ask dirservers for /dir.z to get a compressed version
8191 of the directory. Only works for servers running 0.0.9, of course.
8192 - Make clients cache directories and use them to seed their router
8193 lists at startup. This means clients have a datadir again.
8194 - Configuration infrastructure support for warning on obsolete
8196 - Respond to content-encoding headers by trying to uncompress as
8198 - Reply with a deflated directory when a client asks for "dir.z".
8199 We could use allow-encodings instead, but allow-encodings isn't
8200 specified in HTTP 1.0.
8201 - Raise the max dns workers from 50 to 100.
8202 - Discourage people from setting their dirfetchpostperiod more often
8203 than once per minute.
8204 - Protect dirservers from overzealous descriptor uploading -- wait
8205 10 seconds after directory gets dirty, before regenerating.
8208 Changes in version 0.0.8 - 2004-08-25
8209 o Port it to SunOS 5.9 / Athena
8212 Changes in version 0.0.8rc2 - 2004-08-20
8213 o Make it compile on cygwin again.
8214 o When picking unverified routers, skip those with low uptime and/or
8215 low bandwidth, depending on what properties you care about.
8218 Changes in version 0.0.8rc1 - 2004-08-18
8219 o Changes from 0.0.7.3:
8221 - Fix assert triggers: if the other side returns an address 0.0.0.0,
8222 don't put it into the client dns cache.
8223 - If a begin failed due to exit policy, but we believe the IP address
8224 should have been allowed, switch that router to exitpolicy reject *:*
8225 until we get our next directory.
8227 - Clients choose nodes proportional to advertised bandwidth.
8228 - Avoid using nodes with low uptime as introduction points.
8229 - Handle servers with dynamic IP addresses: don't replace
8230 options->Address with the resolved one at startup, and
8231 detect our address right before we make a routerinfo each time.
8232 - 'FascistFirewall' option to pick dirservers and ORs on specific
8233 ports; plus 'FirewallPorts' config option to tell FascistFirewall
8234 which ports are open. (Defaults to 80,443)
8235 - Be more aggressive about trying to make circuits when the network
8236 has changed (e.g. when you unsuspend your laptop).
8237 - Check for time skew on http headers; report date in response to
8239 - If the entrynode config line has only one node, don't pick it as
8241 - Add strict{entry|exit}nodes config options. If set to 1, then
8242 we refuse to build circuits that don't include the specified entry
8244 - OutboundBindAddress config option, to bind to a specific
8245 IP address for outgoing connect()s.
8246 - End truncated log entries (e.g. directories) with "[truncated]".
8248 o Patches to 0.0.8preX:
8250 - Patches to compile and run on win32 again (maybe)?
8251 - Fix crash when looking for ~/.torrc with no $HOME set.
8252 - Fix a race bug in the unit tests.
8253 - Handle verified/unverified name collisions better when new
8254 routerinfo's arrive in a directory.
8255 - Sometimes routers were getting entered into the stats before
8256 we'd assigned their identity_digest. Oops.
8257 - Only pick and establish intro points after we've gotten a
8260 - AllowUnverifiedNodes config option to let circuits choose no-name
8261 routers in entry,middle,exit,introduction,rendezvous positions.
8262 Allow middle and rendezvous positions by default.
8263 - Add a man page for tor-resolve.
8266 Changes in version 0.0.7.3 - 2004-08-12
8267 o Stop dnsworkers from triggering an assert failure when you
8268 ask them to resolve the host "".
8271 Changes in version 0.0.8pre3 - 2004-08-09
8272 o Changes from 0.0.7.2:
8273 - Allow multiple ORs with same nickname in routerlist -- now when
8274 people give us one identity key for a nickname, then later
8275 another, we don't constantly complain until the first expires.
8276 - Remember used bandwidth (both in and out), and publish 15-minute
8277 snapshots for the past day into our descriptor.
8278 - You can now fetch $DIRURL/running-routers to get just the
8279 running-routers line, not the whole descriptor list. (But
8280 clients don't use this yet.)
8281 - When people mistakenly use Tor as an http proxy, point them
8282 at the tor-doc.html rather than the INSTALL.
8283 - Remove our mostly unused -- and broken -- hex_encode()
8284 function. Use base16_encode() instead. (Thanks to Timo Lindfors
8285 for pointing out this bug.)
8286 - Rotate onion keys every 12 hours, not every 2 hours, so we have
8287 fewer problems with people using the wrong key.
8288 - Change the default exit policy to reject the default edonkey,
8289 kazaa, gnutella ports.
8290 - Add replace_file() to util.[ch] to handle win32's rename().
8292 o Changes from 0.0.8preX:
8293 - Fix two bugs in saving onion keys to disk when rotating, so
8294 hopefully we'll get fewer people using old onion keys.
8295 - Fix an assert error that was making SocksPolicy not work.
8296 - Be willing to expire routers that have an open dirport -- it's
8297 just the authoritative dirservers we want to not forget.
8298 - Reject tor-resolve requests for .onion addresses early, so we
8299 don't build a whole rendezvous circuit and then fail.
8300 - When you're warning a server that he's unverified, don't cry
8302 - Fix a race condition: don't try to extend onto a connection
8303 that's still handshaking.
8304 - For servers in clique mode, require the conn to be open before
8305 you'll choose it for your path.
8306 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
8307 end relay cell, etc.
8308 - Measure bandwidth capacity over the last 24 hours, not just 12
8309 - Bugfix: authoritative dirservers were making and signing a new
8310 directory for each client, rather than reusing the cached one.
8313 Changes in version 0.0.8pre2 - 2004-08-04
8314 o Changes from 0.0.7.2:
8316 - Check directory signature _before_ you decide whether you're
8317 you're running an obsolete version and should exit.
8318 - Check directory signature _before_ you parse the running-routers
8319 list to decide who's running or verified.
8320 - Bugfixes and features:
8321 - Check return value of fclose while writing to disk, so we don't
8322 end up with broken files when servers run out of disk space.
8323 - Log a warning if the user uses an unsafe socks variant, so people
8324 are more likely to learn about privoxy or socat.
8325 - Dirservers now include RFC1123-style dates in the HTTP headers,
8326 which one day we will use to better detect clock skew.
8328 o Changes from 0.0.8pre1:
8329 - Make it compile without warnings again on win32.
8330 - Log a warning if you're running an unverified server, to let you
8331 know you might want to get it verified.
8332 - Only pick a default nickname if you plan to be a server.
8335 Changes in version 0.0.8pre1 - 2004-07-23
8337 - Made our unit tests compile again on OpenBSD 3.5, and tor
8338 itself compile again on OpenBSD on a sparc64.
8339 - We were neglecting milliseconds when logging on win32, so
8340 everything appeared to happen at the beginning of each second.
8343 - 'Extend' relay cell payloads now include the digest of the
8344 intended next hop's identity key. Now we can verify that we're
8345 extending to the right router, and also extend to routers we
8346 hadn't heard of before.
8349 - Tor nodes can now act as relays (with an advertised ORPort)
8350 without being manually verified by the dirserver operators.
8351 - Uploaded descriptors of unverified routers are now accepted
8352 by the dirservers, and included in the directory.
8353 - Verified routers are listed by nickname in the running-routers
8354 list; unverified routers are listed as "$<fingerprint>".
8355 - We now use hash-of-identity-key in most places rather than
8356 nickname or addr:port, for improved security/flexibility.
8357 - To avoid Sybil attacks, paths still use only verified servers.
8358 But now we have a chance to play around with hybrid approaches.
8359 - Nodes track bandwidth usage to estimate capacity (not used yet).
8360 - ClientOnly option for nodes that never want to become servers.
8361 - Directory caching.
8362 - "AuthoritativeDir 1" option for the official dirservers.
8363 - Now other nodes (clients and servers) will cache the latest
8364 directory they've pulled down.
8365 - They can enable their DirPort to serve it to others.
8366 - Clients will pull down a directory from any node with an open
8367 DirPort, and check the signature/timestamp correctly.
8368 - Authoritative dirservers now fetch directories from other
8369 authdirservers, to stay better synced.
8370 - Running-routers list tells who's down also, along with noting
8371 if they're verified (listed by nickname) or unverified (listed
8373 - Allow dirservers to serve running-router list separately.
8374 This isn't used yet.
8375 - ORs connect-on-demand to other ORs
8376 - If you get an extend cell to an OR you're not connected to,
8377 connect, handshake, and forward the create cell.
8378 - The authoritative dirservers stay connected to everybody,
8379 and everybody stays connected to 0.0.7 servers, but otherwise
8380 clients/servers expire unused connections after 5 minutes.
8381 - When servers get a sigint, they delay 30 seconds (refusing new
8382 connections) then exit. A second sigint causes immediate exit.
8383 - File and name management:
8384 - Look for .torrc if no CONFDIR "torrc" is found.
8385 - If no datadir is defined, then choose, make, and secure ~/.tor
8387 - If torrc not found, exitpolicy reject *:*.
8388 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
8389 - If no nickname is defined, derive default from hostname.
8390 - Rename secret key files, e.g. identity.key -> secret_id_key,
8391 to discourage people from mailing their identity key to tor-ops.
8392 - Refuse to build a circuit before the directory has arrived --
8393 it won't work anyway, since you won't know the right onion keys
8395 - Try other dirservers immediately if the one you try is down. This
8396 should tolerate down dirservers better now.
8397 - Parse tor version numbers so we can do an is-newer-than check
8398 rather than an is-in-the-list check.
8399 - New socks command 'resolve', to let us shim gethostbyname()
8401 - A 'tor_resolve' script to access the socks resolve functionality.
8402 - A new socks-extensions.txt doc file to describe our
8403 interpretation and extensions to the socks protocols.
8404 - Add a ContactInfo option, which gets published in descriptor.
8405 - Publish OR uptime in descriptor (and thus in directory) too.
8406 - Write tor version at the top of each log file
8407 - New docs in the tarball:
8409 - Document that you should proxy your SSL traffic too.
8412 Changes in version 0.0.7.2 - 2004-07-07
8413 o A better fix for the 0.0.0.0 problem, that will hopefully
8414 eliminate the remaining related assertion failures.
8417 Changes in version 0.0.7.1 - 2004-07-04
8418 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
8419 since internally we use 0.0.0.0 to signify "not yet resolved".
8422 Changes in version 0.0.7 - 2004-06-07
8423 o Updated the man page to reflect the new features.
8426 Changes in version 0.0.7rc2 - 2004-06-06
8427 o Changes from 0.0.7rc1:
8428 - Make it build on Win32 again.
8429 o Changes from 0.0.6.2:
8430 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
8434 Changes in version 0.0.7rc1 - 2004-06-02
8436 - On sighup, we were adding another log without removing the first
8437 one. So log messages would get duplicated n times for n sighups.
8438 - Several cases of using a connection after we'd freed it. The
8439 problem was that connections that are pending resolve are in both
8440 the pending_resolve tree, and also the circuit's resolving_streams
8441 list. When you want to remove one, you must remove it from both.
8442 - Fix a double-mark-for-close where an end cell arrived for a
8443 resolving stream, and then the resolve failed.
8444 - Check directory signatures based on name of signer, not on whom
8445 we got the directory from. This will let us cache directories more
8448 - Crank up some of our constants to handle more users.
8451 Changes in version 0.0.7pre1 - 2004-06-02
8452 o Fixes for crashes and other obnoxious bugs:
8453 - Fix an epipe bug: sometimes when directory connections failed
8454 to connect, we would give them a chance to flush before closing
8456 - When we detached from a circuit because of resolvefailed, we
8457 would immediately try the same circuit twice more, and then
8458 give up on the resolve thinking we'd tried three different
8460 - Limit the number of intro circuits we'll attempt to build for a
8461 hidden service per 15-minute period.
8462 - Check recommended-software string *early*, before actually parsing
8463 the directory. Thus we can detect an obsolete version and exit,
8464 even if the new directory format doesn't parse.
8465 o Fixes for security bugs:
8466 - Remember which nodes are dirservers when you startup, and if a
8467 random OR enables his dirport, don't automatically assume he's
8468 a trusted dirserver.
8470 - Directory connections were asking the wrong poll socket to
8471 start writing, and not asking themselves to start writing.
8472 - When we detached from a circuit because we sent a begin but
8473 didn't get a connected, we would use it again the first time;
8474 but after that we would correctly switch to a different one.
8475 - Stop warning when the first onion decrypt attempt fails; they
8476 will sometimes legitimately fail now that we rotate keys.
8477 - Override unaligned-access-ok check when $host_cpu is ia64 or
8478 arm. Apparently they allow it but the kernel whines.
8479 - Dirservers try to reconnect periodically too, in case connections
8481 - Fix some memory leaks in directory servers.
8482 - Allow backslash in Win32 filenames.
8483 - Made Tor build complain-free on FreeBSD, hopefully without
8484 breaking other BSD builds. We'll see.
8486 - Doxygen markup on all functions and global variables.
8487 - Make directory functions update routerlist, not replace it. So
8488 now directory disagreements are not so critical a problem.
8489 - Remove the upper limit on number of descriptors in a dirserver's
8490 directory (not that we were anywhere close).
8491 - Allow multiple logfiles at different severity ranges.
8492 - Allow *BindAddress to specify ":port" rather than setting *Port
8493 separately. Allow multiple instances of each BindAddress config
8494 option, so you can bind to multiple interfaces if you want.
8495 - Allow multiple exit policy lines, which are processed in order.
8496 Now we don't need that huge line with all the commas in it.
8497 - Enable accept/reject policies on SOCKS connections, so you can bind
8498 to 0.0.0.0 but still control who can use your OP.
8501 Changes in version 0.0.6.2 - 2004-05-16
8502 o Our integrity-checking digest was checking only the most recent cell,
8503 not the previous cells like we'd thought.
8504 Thanks to Stefan Mark for finding the flaw!
8507 Changes in version 0.0.6.1 - 2004-05-06
8508 o Fix two bugs in our AES counter-mode implementation (this affected
8509 onion-level stream encryption, but not TLS-level). It turns
8510 out we were doing something much more akin to a 16-character
8511 polyalphabetic cipher. Oops.
8512 Thanks to Stefan Mark for finding the flaw!
8513 o Retire moria3 as a directory server, and add tor26 as a directory
8517 Changes in version 0.0.6 - 2004-05-02
8521 Changes in version 0.0.6rc4 - 2004-05-01
8522 o Update the built-in dirservers list to use the new directory format
8523 o Fix a rare seg fault: if a node offering a hidden service attempts
8524 to build a circuit to Alice's rendezvous point and fails before it
8525 reaches the last hop, it retries with a different circuit, but
8527 o Handle windows socket errors correctly.
8530 Changes in version 0.0.6rc3 - 2004-04-28
8531 o Don't expire non-general excess circuits (if we had enough
8532 circuits open, we were expiring rendezvous circuits -- even
8533 when they had a stream attached. oops.)
8534 o Fetch randomness from /dev/urandom better (not via fopen/fread)
8535 o Better debugging for tls errors
8536 o Some versions of openssl have an SSL_pending function that erroneously
8537 returns bytes when there is a non-application record pending.
8538 o Set Content-Type on the directory and hidserv descriptor.
8539 o Remove IVs from cipher code, since AES-ctr has none.
8540 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
8541 o We were using an array of length zero in a few places.
8542 o win32's gethostbyname can't resolve an IP to an IP.
8543 o win32's close can't close a socket.
8546 Changes in version 0.0.6rc2 - 2004-04-26
8547 o Fix a bug where we were closing tls connections intermittently.
8548 It turns out openssl keeps its errors around -- so if an error
8549 happens, and you don't ask about it, and then another openssl
8550 operation happens and succeeds, and you ask if there was an error,
8551 it tells you about the first error. Fun fun.
8552 o Fix a bug that's been lurking since 27 may 03 (!)
8553 When passing back a destroy cell, we would use the wrong circ id.
8554 'Mostly harmless', but still worth fixing.
8555 o Since we don't support truncateds much, don't bother sending them;
8556 just close the circ.
8557 o check for <machine/limits.h> so we build on NetBSD again (I hope).
8558 o don't crash if a conn that sent a begin has suddenly lost its circuit
8559 (this was quite rare).
8562 Changes in version 0.0.6rc1 - 2004-04-25
8563 o We now rotate link (tls context) keys and onion keys.
8564 o CREATE cells now include oaep padding, so you can tell
8565 if you decrypted them correctly.
8566 o Add bandwidthburst to server descriptor.
8567 o Directories now say which dirserver signed them.
8568 o Use a tor_assert macro that logs failed assertions too.
8571 Changes in version 0.0.6pre5 - 2004-04-18
8572 o changes from 0.0.6pre4:
8573 - make tor build on broken freebsd 5.2 installs
8574 - fix a failed assert when you try an intro point, get a nack, and try
8575 a second one and it works.
8576 - when alice uses a port that the hidden service doesn't accept,
8577 it now sends back an end cell (denied by exit policy). otherwise
8578 alice would just have to wait to time out.
8579 - fix another rare bug: when we had tried all the intro
8580 points for a hidden service, we fetched the descriptor
8581 again, but we left our introcirc thinking it had already
8582 sent an intro, so it kept waiting for a response...
8583 - bugfix: when you sleep your hidden-service laptop, as soon
8584 as it wakes up it tries to upload a service descriptor, but
8585 socketpair fails for some reason (localhost not up yet?).
8586 now we simply give up on that upload, and we'll try again later.
8587 i'd still like to find the bug though.
8588 - if an intro circ waiting for an ack dies before getting one, then
8590 - we were reusing stale service descriptors and refetching usable
8594 Changes in version 0.0.6pre4 - 2004-04-14
8595 o changes from 0.0.6pre3:
8596 - when bob fails to connect to the rendezvous point, and his
8597 circ didn't fail because of the rendezvous point itself, then
8598 he retries a couple of times
8599 - we expire introduction and rendezvous circs more thoroughly
8600 (sometimes they were hanging around forever)
8601 - we expire unattached rendezvous streams that have been around
8602 too long (they were sticking around forever).
8603 - fix a measly fencepost error that was crashing everybody with
8607 Changes in version 0.0.6pre3 - 2004-04-14
8608 o changes from 0.0.6pre2:
8609 - make hup work again
8610 - fix some memory leaks for dirservers
8611 - allow more skew in rendezvous descriptor timestamps, to help
8612 handle people like blanu who don't know what time it is
8613 - normal circs are 3 hops, but some rend/intro circs are 4, if
8614 the initiator doesn't get to choose the last hop
8615 - send acks for introductions, so alice can know whether to try
8617 - bob publishes intro points more correctly
8618 o changes from 0.0.5:
8619 - fix an assert trigger that's been plaguing us since the days
8620 of 0.0.2prexx (thanks weasel!)
8621 - retry stream correctly when we fail to connect because of
8622 exit-policy-reject (should try another) or can't-resolve-address
8623 (also should try another, because dns on random internet servers
8625 - when we hup a dirserver and we've *removed* a server from the
8626 approved-routers list, now we remove that server from the
8627 in-memory directories too
8630 Changes in version 0.0.6pre2 - 2004-04-08
8631 o We fixed our base32 implementation. Now it works on all architectures.
8634 Changes in version 0.0.6pre1 - 2004-04-08
8636 - Hidden services and rendezvous points are implemented. Go to
8637 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
8638 hidden services. (This only works via a socks4a proxy such as
8639 Privoxy, and currently it's quite slow.)
8642 Changes in version 0.0.5 - 2004-03-30
8646 Changes in version 0.0.5rc3 - 2004-03-29
8647 o Install torrc as torrc.sample -- we no longer clobber your
8649 o Re-enable recommendedversion checking (we broke it in rc2, oops)
8650 o Add in a 'notice' log level for things the operator should hear
8651 but that aren't warnings
8654 Changes in version 0.0.5rc2 - 2004-03-29
8655 o Hold socks connection open until reply is flushed (if possible)
8656 o Make exit nodes resolve IPs to IPs immediately, rather than asking
8657 the dns farm to do it.
8658 o Fix c99 aliasing warnings in rephist.c
8659 o Don't include server descriptors that are older than 24 hours in the
8661 o Give socks 'reject' replies their whole 15s to attempt to flush,
8662 rather than seeing the 60s timeout and assuming the flush had failed.
8663 o Clean automake droppings from the cvs repository
8666 Changes in version 0.0.5rc1 - 2004-03-28
8667 o Fix mangled-state bug in directory fetching (was causing sigpipes).
8668 o Only build circuits after we've fetched the directory: clients were
8669 using only the directory servers before they'd fetched a directory.
8670 This also means longer startup time; so it goes.
8671 o Fix an assert trigger where an OP would fail to handshake, and we'd
8672 expect it to have a nickname.
8673 o Work around a tsocks bug: do a socks reject when AP connection dies
8674 early, else tsocks goes into an infinite loop.
8677 Changes in version 0.0.4 - 2004-03-26
8678 o When connecting to a dirserver or OR and the network is down,
8682 Changes in version 0.0.3 - 2004-03-26
8683 o Warn and fail if server chose a nickname with illegal characters
8684 o Port to Solaris and Sparc:
8685 - include missing header fcntl.h
8686 - have autoconf find -lsocket -lnsl automatically
8687 - deal with hardware word alignment
8688 - make uname() work (solaris has a different return convention)
8689 - switch from using signal() to sigaction()
8690 o Preliminary work on reputation system:
8691 - Keep statistics on success/fail of connect attempts; they're published
8692 by kill -USR1 currently.
8693 - Add a RunTesting option to try to learn link state by creating test
8694 circuits, even when SocksPort is off.
8695 - Remove unused open circuits when there are too many.
8698 Changes in version 0.0.2 - 2004-03-19
8699 - Include strlcpy and strlcat for safer string ops
8700 - define INADDR_NONE so we compile (but still not run) on solaris
8703 Changes in version 0.0.2pre27 - 2004-03-14
8705 - Allow internal tor networks (we were rejecting internal IPs,
8706 now we allow them if they're set explicitly).
8707 - And fix a few endian issues.
8710 Changes in version 0.0.2pre26 - 2004-03-14
8712 - If a stream times out after 15s without a connected cell, don't
8713 try that circuit again: try a new one.
8714 - Retry streams at most 4 times. Then give up.
8715 - When a dirserver gets a descriptor from an unknown router, it
8716 logs its fingerprint (so the dirserver operator can choose to
8717 accept it even without mail from the server operator).
8718 - Inform unapproved servers when we reject their descriptors.
8719 - Make tor build on Windows again. It works as a client, who knows
8721 - Clearer instructions in the torrc for how to set up a server.
8722 - Be more efficient about reading fd's when our global token bucket
8723 (used for rate limiting) becomes empty.
8725 - Stop asserting that computers always go forward in time. It's
8727 - When we sent a cell (e.g. destroy) and then marked an OR connection
8728 expired, we might close it before finishing a flush if the other
8729 side isn't reading right then.
8730 - Don't allow dirservers to start if they haven't defined
8732 - We were caching transient dns failures. Oops.
8733 - Prevent servers from publishing an internal IP as their address.
8734 - Address a strcat vulnerability in circuit.c
8737 Changes in version 0.0.2pre25 - 2004-03-04
8739 - Put the OR's IP in its router descriptor, not its fqdn. That way
8740 we'll stop being stalled by gethostbyname for nodes with flaky dns,
8743 - If the user typed in an address that didn't resolve, the server
8747 Changes in version 0.0.2pre24 - 2004-03-03
8749 - Fix an assertion failure in dns.c, where we were trying to dequeue
8750 a pending dns resolve even if it wasn't pending
8751 - Fix a spurious socks5 warning about still trying to write after the
8752 connection is finished.
8753 - Hold certain marked_for_close connections open until they're finished
8754 flushing, rather than losing bytes by closing them too early.
8755 - Correctly report the reason for ending a stream
8756 - Remove some duplicate calls to connection_mark_for_close
8757 - Put switch_id and start_daemon earlier in the boot sequence, so it
8758 will actually try to chdir() to options.DataDirectory
8759 - Make 'make test' exit(1) if a test fails; fix some unit tests
8760 - Make tor fail when you use a config option it doesn't know about,
8761 rather than warn and continue.
8762 - Make --version work
8763 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
8766 Changes in version 0.0.2pre23 - 2004-02-29
8768 - Print a statement when the first circ is finished, so the user
8770 - If a relay cell is unrecognized at the end of the circuit,
8771 send back a destroy. (So attacks to mutate cells are more
8773 - New config option 'excludenodes' to avoid certain nodes for circuits.
8774 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
8775 so you can collect coredumps there.
8777 - Fix a bug in tls flushing where sometimes data got wedged and
8778 didn't flush until more data got sent. Hopefully this bug was
8779 a big factor in the random delays we were seeing.
8780 - Make 'connected' cells include the resolved IP, so the client
8781 dns cache actually gets populated.
8782 - Disallow changing from ORPort=0 to ORPort>0 on hup.
8783 - When we time-out on a stream and detach from the circuit, send an
8784 end cell down it first.
8785 - Only warn about an unknown router (in exitnodes, entrynodes,
8786 excludenodes) after we've fetched a directory.
8789 Changes in version 0.0.2pre22 - 2004-02-26
8791 - Servers publish less revealing uname information in descriptors.
8792 - More memory tracking and assertions, to crash more usefully when
8794 - If the default torrc isn't there, just use some default defaults.
8795 Plus provide an internal dirservers file if they don't have one.
8796 - When the user tries to use Tor as an http proxy, give them an http
8797 501 failure explaining that we're a socks proxy.
8798 - Dump a new router.desc on hup, to help confused people who change
8799 their exit policies and then wonder why router.desc doesn't reflect
8801 - Clean up the generic tor.sh init script that we ship with.
8803 - If the exit stream is pending on the resolve, and a destroy arrives,
8804 then the stream wasn't getting removed from the pending list. I
8805 think this was the one causing recent server crashes.
8806 - Use a more robust poll on OSX 10.3, since their poll is flaky.
8807 - When it couldn't resolve any dirservers, it was useless from then on.
8808 Now it reloads the RouterFile (or default dirservers) if it has no
8810 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
8811 many users don't even *have* a /usr/local/sbin/.
8814 Changes in version 0.0.2pre21 - 2004-02-18
8816 - There's a ChangeLog file that actually reflects the changelog.
8817 - There's a 'torify' wrapper script, with an accompanying
8818 tor-tsocks.conf, that simplifies the process of using tsocks for
8819 tor. It even has a man page.
8820 - The tor binary gets installed to sbin rather than bin now.
8821 - Retry streams where the connected cell hasn't arrived in 15 seconds
8822 - Clean up exit policy handling -- get the default out of the torrc,
8823 so we can update it without forcing each server operator to fix
8825 - Allow imaps and pop3s in default exit policy
8827 - Prevent picking middleman nodes as the last node in the circuit
8830 Changes in version 0.0.2pre20 - 2004-01-30
8832 - We now have a deb package, and it's in debian unstable. Go to
8834 - I've split the TotalBandwidth option into BandwidthRate (how many
8835 bytes per second you want to allow, long-term) and
8836 BandwidthBurst (how many bytes you will allow at once before the cap
8837 kicks in). This better token bucket approach lets you, say, set
8838 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
8839 performance while not exceeding your monthly bandwidth quota.
8840 - Push out a tls record's worth of data once you've got it, rather
8841 than waiting until you've read everything waiting to be read. This
8842 may improve performance by pipelining better. We'll see.
8843 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
8844 from failed circuits (if they haven't been connected yet) and attach
8846 - Expire old streams that haven't managed to connect. Some day we'll
8847 have them reattach to new circuits instead.
8850 - Fix several memory leaks that were causing servers to become bloated
8852 - Fix a few very rare assert triggers. A few more remain.
8853 - Setuid to User _before_ complaining about running as root.
8856 Changes in version 0.0.2pre19 - 2004-01-07
8858 - Fix deadlock condition in dns farm. We were telling a child to die by
8859 closing the parent's file descriptor to him. But newer children were
8860 inheriting the open file descriptor from the parent, and since they
8861 weren't closing it, the socket never closed, so the child never read
8862 eof, so he never knew to exit. Similarly, dns workers were holding
8863 open other sockets, leading to all sorts of chaos.
8864 - New cleaner daemon() code for forking and backgrounding.
8865 - If you log to a file, it now prints an entry at the top of the
8866 logfile so you know it's working.
8867 - The onionskin challenge length was 30 bytes longer than necessary.
8868 - Started to patch up the spec so it's not quite so out of date.
8871 Changes in version 0.0.2pre18 - 2004-01-02
8873 - Fix endian issues with the 'integrity' field in the relay header.
8874 - Fix a potential bug where connections in state
8875 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
8878 Changes in version 0.0.2pre17 - 2003-12-30
8880 - Made --debuglogfile (or any second log file, actually) work.
8881 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
8882 adversary could force us into an infinite loop.
8885 - Each onionskin handshake now includes a hash of the computed key,
8886 to prove the server's identity and help perfect forward secrecy.
8887 - Changed cell size from 256 to 512 bytes (working toward compatibility
8889 - Changed cell length to 2 bytes, and moved it to the relay header.
8890 - Implemented end-to-end integrity checking for the payloads of
8892 - Separated streamid from 'recognized' (otherwise circuits will get
8893 messed up when we try to have streams exit from the middle). We
8894 use the integrity-checking to confirm that a cell is addressed to
8896 - Randomize the initial circid and streamid values, so an adversary who
8897 breaks into a node can't learn how many circuits or streams have
8901 Changes in version 0.0.2pre16 - 2003-12-14
8903 - Fixed a bug that made HUP trigger an assert
8904 - Fixed a bug where a circuit that immediately failed wasn't being
8905 counted as a failed circuit in counting retries.
8908 - Now we close the circuit when we get a truncated cell: otherwise we're
8909 open to an anonymity attack where a bad node in the path truncates
8910 the circuit and then we open streams at him.
8911 - Add port ranges to exit policies
8912 - Add a conservative default exit policy
8913 - Warn if you're running tor as root
8914 - on HUP, retry OR connections and close/rebind listeners
8915 - options.EntryNodes: try these nodes first when picking the first node
8916 - options.ExitNodes: if your best choices happen to include any of
8917 your preferred exit nodes, you choose among just those preferred
8919 - options.ExcludedNodes: nodes that are never picked in path building
8922 Changes in version 0.0.2pre15 - 2003-12-03
8923 o Robustness and bugfixes:
8924 - Sometimes clients would cache incorrect DNS resolves, which would
8925 really screw things up.
8926 - An OP that goes offline would slowly leak all its sockets and stop
8928 - A wide variety of bugfixes in exit node selection, exit policy
8929 handling, and processing pending streams when a new circuit is
8931 - Pick nodes for a path only from those the directory says are up
8932 - Choose randomly from all running dirservers, not always the first one
8933 - Increase allowed http header size for directory fetch.
8934 - Stop writing to stderr (if we're daemonized it will be closed).
8935 - Enable -g always, so cores will be more useful to me.
8936 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
8939 - Wrote a man page. It lists commonly used options.
8942 - Change default loglevel to warn.
8943 - Make PidFile default to null rather than littering in your CWD.
8944 - OnionRouter config option is now obsolete. Instead it just checks
8946 - Moved to a single unified torrc file for both clients and servers.
8949 Changes in version 0.0.2pre14 - 2003-11-29
8950 o Robustness and bugfixes:
8951 - Force the admin to make the DataDirectory himself
8952 - to get ownership/permissions right
8953 - so clients no longer make a DataDirectory and then never use it
8954 - fix bug where a client who was offline for 45 minutes would never
8955 pull down a directory again
8956 - fix (or at least hide really well) the dns assert bug that was
8957 causing server crashes
8958 - warnings and improved robustness wrt clockskew for certs
8959 - use the native daemon(3) to daemonize, when available
8960 - exit if bind() fails
8961 - exit if neither socksport nor orport is defined
8962 - include our own tor_timegm (Win32 doesn't have its own)
8963 - bugfix for win32 with lots of connections
8964 - fix minor bias in PRNG
8965 - make dirserver more robust to corrupt cached directory
8968 - Wrote the design document (woo)
8970 o Circuit building and exit policies:
8971 - Circuits no longer try to use nodes that the directory has told them
8973 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
8974 bitcounts (18.0.0.0/8).
8975 - Make AP connections standby for a circuit if no suitable circuit
8976 exists, rather than failing
8977 - Circuits choose exit node based on addr/port, exit policies, and
8978 which AP connections are standing by
8979 - Bump min pathlen from 2 to 3
8980 - Relay end cells have a payload to describe why the stream ended.
8981 - If the stream failed because of exit policy, try again with a new
8983 - Clients have a dns cache to remember resolved addresses.
8984 - Notice more quickly when we have no working circuits
8987 - APPort is now called SocksPort
8988 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
8990 - RecommendedVersions is now a config variable rather than
8991 hardcoded (for dirservers)
8992 - Reloads config on HUP
8993 - Usage info on -h or --help
8994 - If you set User and Group config vars, it'll setu/gid to them.
8997 Changes in version 0.0.2pre13 - 2003-10-19
8998 o General stability:
8999 - SSL_write no longer fails when it returns WANTWRITE and the number
9000 of bytes in the buf has changed by the next SSL_write call.
9001 - Fix segfault fetching directory when network is down
9002 - Fix a variety of minor memory leaks
9003 - Dirservers reload the fingerprints file on HUP, so I don't have
9004 to take down the network when I approve a new router
9005 - Default server config file has explicit Address line to specify fqdn
9008 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
9009 - Make listener connections not ever alloc bufs
9011 o Autoconf improvements:
9012 - don't clobber an external CFLAGS in ./configure
9013 - Make install now works
9014 - create var/lib/tor on make install
9015 - autocreate a tor.sh initscript to help distribs
9016 - autocreate the torrc and sample-server-torrc with correct paths
9018 o Log files and Daemonizing now work:
9019 - If --DebugLogFile is specified, log to it at -l debug
9020 - If --LogFile is specified, use it instead of commandline
9021 - If --RunAsDaemon is set, tor forks and backgrounds on startup