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