1 Changes in version 0.2.1.20 - 2009-??-??
3 - Send circuit or stream sendme cells when our window has decreased
4 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
5 by Karsten when testing the "reduce circuit window" performance
6 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7 before the release of Tor 0.0.0. This is the new winner of the
10 o New directory authorities:
11 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
15 - Fix a signed/unsigned compile warning in 0.2.1.19.
16 - Fix possible segmentation fault on directory authorities. Bugfix on
18 - Fix an extremely rare infinite recursion bug that could occur if
19 we tried to log a message after shutting down the log subsystem.
20 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
21 - Fix an obscure bug where hidden services on 64-bit big-endian
22 systems might mis-read the timestamp in v3 introduce cells, and
23 refuse to connect back to the client. Discovered by "rotor".
24 Bugfix on 0.2.1.6-alpha.
25 - We were triggering a CLOCK_SKEW controller status event whenever
26 we connect via the v2 connection protocol to any relay that has
27 a wrong clock. Instead, we should only inform the controller when
28 it's a trusted authority that claims our clock is wrong. Bugfix
29 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
30 - We were telling the controller about CHECKING_REACHABILITY and
31 REACHABILITY_FAILED status events whenever we launch a testing
32 circuit or notice that one has failed. Instead, only tell the
33 controller when we want to inform the user of overall success or
34 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
36 - Don't warn when we're using a circuit that ends with a node
37 excluded in ExcludeExitNodes, but the circuit is not used to access
38 the outside world. This should help fix bug 1090. Bugfix on
42 - Add a "getinfo status/accepted-server-descriptor" controller
43 command, which is the recommended way for controllers to learn
44 whether our server descriptor has been successfully received by at
45 least on directory authority. Un-recommend good-server-descriptor
46 getinfo and status events until we have a better design for them.
49 Changes in version 0.2.1.19 - 2009-07-28
50 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
51 services on Tor 0.2.1.3-alpha through 0.2.1.18.
54 - Make accessing hidden services on 0.2.1.x work right again.
55 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
56 part of patch provided by "optimist".
59 - When a relay/bridge is writing out its identity key fingerprint to
60 the "fingerprint" file and to its logs, write it without spaces. Now
61 it will look like the fingerprints in our bridges documentation,
62 and confuse fewer users.
65 - Relays no longer publish a new server descriptor if they change
66 their MaxAdvertisedBandwidth config option but it doesn't end up
67 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
68 fixes bug 1026. Patch from Sebastian.
69 - Avoid leaking memory every time we get a create cell but we have
70 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
71 fixes bug 1034. Reported by BarkerJr.
74 Changes in version 0.2.1.18 - 2009-07-24
75 Tor 0.2.1.18 lays the foundations for performance improvements,
76 adds status events to help users diagnose bootstrap problems, adds
77 optional authentication/authorization for hidden services, fixes a
78 variety of potential anonymity problems, and includes a huge pile of
79 other features and bug fixes.
82 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
85 Changes in version 0.2.1.17-rc - 2009-07-07
86 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
87 candidate for the 0.2.1.x series. It lays the groundwork for further
88 client performance improvements, and also fixes a big bug with directory
89 authorities that were causing them to assign Guard and Stable flags
92 The Windows bundles also finally include the geoip database that we
93 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
94 should actually install Torbutton rather than giving you a cryptic
95 failure message (oops).
98 - Clients now use the bandwidth values in the consensus, rather than
99 the bandwidth values in each relay descriptor. This approach opens
100 the door to more accurate bandwidth estimates once the directory
101 authorities start doing active measurements. Implements more of
105 - When Tor clients restart after 1-5 days, they discard all their
106 cached descriptors as too old, but they still use the cached
107 consensus document. This approach is good for robustness, but
108 bad for performance: since they don't know any bandwidths, they
109 end up choosing at random rather than weighting their choice by
110 speed. Fixed by the above feature of putting bandwidths in the
111 consensus. Bugfix on 0.2.0.x.
112 - Directory authorities were neglecting to mark relays down in their
113 internal histories if the relays fall off the routerlist without
114 ever being found unreachable. So there were relays in the histories
115 that haven't been seen for eight months, and are listed as being
116 up for eight months. This wreaked havoc on the "median wfu"
117 and "median mtbf" calculations, in turn making Guard and Stable
118 flags very wrong, hurting network performance. Fixes bugs 696 and
119 969. Bugfix on 0.2.0.6-alpha.
122 - Serve the DirPortFrontPage page even when we have been approaching
123 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
124 - The control port would close the connection before flushing long
125 replies, such as the network consensus, if a QUIT command was issued
126 before the reply had completed. Now, the control port flushes all
127 pending replies before closing the connection. Also fixed a spurious
128 warning when a QUIT command is issued after a malformed or rejected
129 AUTHENTICATE command, but before the connection was closed. Patch
130 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
131 - When we can't find an intro key for a v2 hidden service descriptor,
132 fall back to the v0 hidden service descriptor and log a bug message.
133 Workaround for bug 1024.
134 - Fix a log message that did not respect the SafeLogging option.
138 - If we're a relay and we change our IP address, be more verbose
139 about the reason that made us change. Should help track down
140 further bugs for relays on dynamic IP addresses.
143 Changes in version 0.2.0.35 - 2009-06-24
145 - Avoid crashing in the presence of certain malformed descriptors.
146 Found by lark, and by automated fuzzing.
147 - Fix an edge case where a malicious exit relay could convince a
148 controller that the client's DNS question resolves to an internal IP
149 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
152 - Finally fix the bug where dynamic-IP relays disappear when their
153 IP address changes: directory mirrors were mistakenly telling
154 them their old address if they asked via begin_dir, so they
155 never got an accurate answer about their new address, so they
156 just vanished after a day. For belt-and-suspenders, relays that
157 don't set Address in their config now avoid using begin_dir for
158 all direct connections. Should fix bugs 827, 883, and 900.
159 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
160 that would occur on some exit nodes when DNS failures and timeouts
161 occurred in certain patterns. Fix for bug 957.
164 - When starting with a cache over a few days old, do not leak
165 memory for the obsolete router descriptors in it. Bugfix on
166 0.2.0.33; fixes bug 672.
167 - Hidden service clients didn't use a cached service descriptor that
168 was older than 15 minutes, but wouldn't fetch a new one either,
169 because there was already one in the cache. Now, fetch a v2
170 descriptor unless the same descriptor was added to the cache within
171 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
174 Changes in version 0.2.1.16-rc - 2009-06-20
175 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
176 a bunch of minor bugs.
179 - Fix an edge case where a malicious exit relay could convince a
180 controller that the client's DNS question resolves to an internal IP
181 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
183 o Major performance improvements (on 0.2.0.x):
184 - Disable and refactor some debugging checks that forced a linear scan
185 over the whole server-side DNS cache. These accounted for over 50%
186 of CPU time on a relatively busy exit node's gprof profile. Found
188 - Disable some debugging checks that appeared in exit node profile
192 - Update to the "June 3 2009" ip-to-country file.
193 - Do not have tor-resolve automatically refuse all .onion addresses;
194 if AutomapHostsOnResolve is set in your torrc, this will work fine.
196 o Minor bugfixes (on 0.2.0.x):
197 - Log correct error messages for DNS-related network errors on
199 - Fix a race condition that could cause crashes or memory corruption
200 when running as a server with a controller listening for log
202 - Avoid crashing when we have a policy specified in a DirPolicy or
203 SocksPolicy or ReachableAddresses option with ports set on it,
204 and we re-load the policy. May fix bug 996.
205 - Hidden service clients didn't use a cached service descriptor that
206 was older than 15 minutes, but wouldn't fetch a new one either,
207 because there was already one in the cache. Now, fetch a v2
208 descriptor unless the same descriptor was added to the cache within
209 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
211 o Minor bugfixes (on 0.2.1.x):
212 - Don't warn users about low port and hibernation mix when they
213 provide a *ListenAddress directive to fix that. Bugfix on
215 - When switching back and forth between bridge mode, do not start
216 gathering GeoIP data until two hours have passed.
217 - Do not complain that the user has requested an excluded node as
218 an exit when the node is not really an exit. This could happen
219 because the circuit was for testing, or an introduction point.
223 Changes in version 0.2.1.15-rc - 2009-05-25
224 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
225 series. It fixes a major bug on fast exit relays, as well as a variety
228 o Major bugfixes (on 0.2.0.x):
229 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
230 that would occur on some exit nodes when DNS failures and timeouts
231 occurred in certain patterns. Fix for bug 957.
233 o Minor bugfixes (on 0.2.0.x):
234 - Actually return -1 in the error case for read_bandwidth_usage().
235 Harmless bug, since we currently don't care about the return value
236 anywhere. Bugfix on 0.2.0.9-alpha.
237 - Provide a more useful log message if bug 977 (related to buffer
238 freelists) ever reappears, and do not crash right away.
239 - Fix an assertion failure on 64-bit platforms when we allocated
240 memory right up to the end of a memarea, then realigned the memory
241 one step beyond the end. Fixes a possible cause of bug 930.
242 - Protect the count of open sockets with a mutex, so we can't
243 corrupt it when two threads are closing or opening sockets at once.
244 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
245 - Don't allow a bridge to publish its router descriptor to a
246 non-bridge directory authority. Fixes part of bug 932.
247 - When we change to or from being a bridge, reset our counts of
248 client usage by country. Fixes bug 932.
249 - Fix a bug that made stream bandwidth get misreported to the
251 - Stop using malloc_usable_size() to use more area than we had
252 actually allocated: it was safe, but made valgrind really unhappy.
253 - Fix a memory leak when v3 directory authorities load their keys
254 and cert from disk. Bugfix on 0.2.0.1-alpha.
256 o Minor bugfixes (on 0.2.1.x):
257 - Fix use of freed memory when deciding to mark a non-addable
258 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
261 Changes in version 0.2.1.14-rc - 2009-04-12
262 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
263 series. It begins fixing some major performance problems, and also
264 finally addresses the bug that was causing relays on dynamic IP
265 addresses to fall out of the directory.
268 - Clients replace entry guards that were chosen more than a few months
269 ago. This change should significantly improve client performance,
270 especially once more people upgrade, since relays that have been
271 a guard for a long time are currently overloaded.
273 o Major bugfixes (on 0.2.0):
274 - Finally fix the bug where dynamic-IP relays disappear when their
275 IP address changes: directory mirrors were mistakenly telling
276 them their old address if they asked via begin_dir, so they
277 never got an accurate answer about their new address, so they
278 just vanished after a day. For belt-and-suspenders, relays that
279 don't set Address in their config now avoid using begin_dir for
280 all direct connections. Should fix bugs 827, 883, and 900.
281 - Relays were falling out of the networkstatus consensus for
282 part of a day if they changed their local config but the
283 authorities discarded their new descriptor as "not sufficiently
284 different". Now directory authorities accept a descriptor as changed
285 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
287 - Avoid crashing in the presence of certain malformed descriptors.
288 Found by lark, and by automated fuzzing.
291 - When generating circuit events with verbose nicknames for
292 controllers, try harder to look up nicknames for routers on a
293 circuit. (Previously, we would look in the router descriptors we had
294 for nicknames, but not in the consensus.) Partial fix for bug 941.
295 - If the bridge config line doesn't specify a port, assume 443.
296 This makes bridge lines a bit smaller and easier for users to
298 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
299 bytes (aka 20KB/s), to match our documentation. Also update
300 directory authorities so they always assign the Fast flag to relays
301 with 20KB/s of capacity. Now people running relays won't suddenly
302 find themselves not seeing any use, if the network gets faster
304 - Update to the "April 3 2009" ip-to-country file.
307 - Avoid trying to print raw memory to the logs when we decide to
308 give up on downloading a given relay descriptor. Bugfix on
310 - In tor-resolve, when the Tor client to use is specified by
311 <hostname>:<port>, actually use the specified port rather than
312 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
313 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
314 - When starting with a cache over a few days old, do not leak
315 memory for the obsolete router descriptors in it. Bugfix on
317 - Avoid double-free on list of successfully uploaded hidden
318 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
319 - Change memarea_strndup() implementation to work even when
320 duplicating a string at the end of a page. This bug was
321 harmless for now, but could have meant crashes later. Fix by
322 lark. Bugfix on 0.2.1.1-alpha.
323 - Limit uploaded directory documents to be 16M rather than 500K.
324 The directory authorities were refusing v3 consensus votes from
325 other authorities, since the votes are now 504K. Fixes bug 959;
326 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
327 - Directory authorities should never send a 503 "busy" response to
328 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
332 Changes in version 0.2.1.13-alpha - 2009-03-09
333 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
334 cleanups. We're finally getting close to a release candidate.
337 - Correctly update the list of which countries we exclude as
338 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
339 lark. Bugfix on 0.2.1.6-alpha.
341 o Minor bugfixes (on 0.2.0.x and earlier):
342 - Automatically detect MacOSX versions earlier than 10.4.0, and
343 disable kqueue from inside Tor when running with these versions.
344 We previously did this from the startup script, but that was no
345 help to people who didn't use the startup script. Resolves bug 863.
346 - When we had picked an exit node for a connection, but marked it as
347 "optional", and it turned out we had no onion key for the exit,
348 stop wanting that exit and try again. This situation may not
349 be possible now, but will probably become feasible with proposal
350 158. Spotted by rovv. Fixes another case of bug 752.
351 - Clients no longer cache certificates for authorities they do not
352 recognize. Bugfix on 0.2.0.9-alpha.
353 - When we can't transmit a DNS request due to a network error, retry
354 it after a while, and eventually transmit a failing response to
355 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
356 - If the controller claimed responsibility for a stream, but that
357 stream never finished making its connection, it would live
358 forever in circuit_wait state. Now we close it after SocksTimeout
359 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
360 - Drop begin cells to a hidden service if they come from the middle
361 of a circuit. Patch from lark.
362 - When we erroneously receive two EXTEND cells for the same circuit
363 ID on the same connection, drop the second. Patch from lark.
364 - Fix a crash that occurs on exit nodes when a nameserver request
365 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
366 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
368 - Do not assume that a stack-allocated character array will be
369 64-bit aligned on platforms that demand that uint64_t access is
370 aligned. Possible fix for bug 604.
371 - Parse dates and IPv4 addresses in a locale- and libc-independent
372 manner, to avoid platform-dependent behavior on malformed input.
373 - Build correctly when configured to build outside the main source
374 path. Patch from Michael Gold.
375 - We were already rejecting relay begin cells with destination port
376 of 0. Now also reject extend cells with destination port or address
377 of 0. Suggested by lark.
379 o Minor bugfixes (on 0.2.1.x):
380 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
381 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
382 - If we're an exit node, scrub the IP address to which we are exiting
383 in the logs. Bugfix on 0.2.1.8-alpha.
386 - On Linux, use the prctl call to re-enable core dumps when the user
388 - New controller event NEWCONSENSUS that lists the networkstatus
389 lines for every recommended relay. Now controllers like Torflow
390 can keep up-to-date on which relays they should be using.
391 - Update to the "February 26 2009" ip-to-country file.
394 Changes in version 0.2.0.34 - 2009-02-08
395 Tor 0.2.0.34 features several more security-related fixes. You should
396 upgrade, especially if you run an exit relay (remote crash) or a
397 directory authority (remote infinite loop), or you're on an older
398 (pre-XP) or not-recently-patched Windows (remote exploit).
400 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
401 have many known flaws, and nobody should be using them. You should
402 upgrade. If you're using a Linux or BSD and its packages are obsolete,
403 stop using those packages and upgrade anyway.
406 - Fix an infinite-loop bug on handling corrupt votes under certain
407 circumstances. Bugfix on 0.2.0.8-alpha.
408 - Fix a temporary DoS vulnerability that could be performed by
409 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
410 - Avoid a potential crash on exit nodes when processing malformed
411 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
412 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
413 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
416 - Fix compilation on systems where time_t is a 64-bit integer.
417 Patch from Matthias Drochner.
418 - Don't consider expiring already-closed client connections. Fixes
419 bug 893. Bugfix on 0.0.2pre20.
422 Changes in version 0.2.1.12-alpha - 2009-02-08
423 Tor 0.2.1.12-alpha features several more security-related fixes. You
424 should upgrade, especially if you run an exit relay (remote crash) or
425 a directory authority (remote infinite loop), or you're on an older
426 (pre-XP) or not-recently-patched Windows (remote exploit). It also
427 includes a big pile of minor bugfixes and cleanups.
430 - Fix an infinite-loop bug on handling corrupt votes under certain
431 circumstances. Bugfix on 0.2.0.8-alpha.
432 - Fix a temporary DoS vulnerability that could be performed by
433 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
434 - Avoid a potential crash on exit nodes when processing malformed
435 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
438 - Let controllers actually ask for the "clients_seen" event for
439 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
440 reported by Matt Edman.
441 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
443 - Fix a bug in address parsing that was preventing bridges or hidden
444 service targets from being at IPv6 addresses.
445 - Solve a bug that kept hardware crypto acceleration from getting
446 enabled when accounting was turned on. Fixes bug 907. Bugfix on
448 - Remove a bash-ism from configure.in to build properly on non-Linux
449 platforms. Bugfix on 0.2.1.1-alpha.
450 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
451 headers. Bugfix on 0.2.0.10-alpha.
452 - Don't consider expiring already-closed client connections. Fixes
453 bug 893. Bugfix on 0.0.2pre20.
454 - Fix another interesting corner-case of bug 891 spotted by rovv:
455 Previously, if two hosts had different amounts of clock drift, and
456 one of them created a new connection with just the wrong timing,
457 the other might decide to deprecate the new connection erroneously.
458 Bugfix on 0.1.1.13-alpha.
459 - Resolve a very rare crash bug that could occur when the user forced
460 a nameserver reconfiguration during the middle of a nameserver
461 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
462 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
463 Bugfix on 0.2.1.7-alpha.
464 - If we're using bridges and our network goes away, be more willing
465 to forgive our bridges and try again when we get an application
466 request. Bugfix on 0.2.0.x.
469 - Support platforms where time_t is 64 bits long. (Congratulations,
470 NetBSD!) Patch from Matthias Drochner.
471 - Add a 'getinfo status/clients-seen' controller command, in case
472 controllers want to hear clients_seen events but connect late.
475 - Disable GCC's strict alias optimization by default, to avoid the
476 likelihood of its introducing subtle bugs whenever our code violates
477 the letter of C99's alias rules.
480 Changes in version 0.2.0.33 - 2009-01-21
481 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
482 useful to users. It also finally fixes a bug where a relay or client
483 that's been off for many days would take a long time to bootstrap.
485 This update also fixes an important security-related bug reported by
486 Ilja van Sprundel. You should upgrade. (We'll send out more details
487 about the bug once people have had some time to upgrade.)
490 - Fix a heap-corruption bug that may be remotely triggerable on
491 some platforms. Reported by Ilja van Sprundel.
494 - When a stream at an exit relay is in state "resolving" or
495 "connecting" and it receives an "end" relay cell, the exit relay
496 would silently ignore the end cell and not close the stream. If
497 the client never closes the circuit, then the exit relay never
498 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
500 - When sending CREATED cells back for a given circuit, use a 64-bit
501 connection ID to find the right connection, rather than an addr:port
502 combination. Now that we can have multiple OR connections between
503 the same ORs, it is no longer possible to use addr:port to uniquely
504 identify a connection.
505 - Bridge relays that had DirPort set to 0 would stop fetching
506 descriptors shortly after startup, and then briefly resume
507 after a new bandwidth test and/or after publishing a new bridge
508 descriptor. Bridge users that try to bootstrap from them would
509 get a recent networkstatus but would get descriptors from up to
510 18 hours earlier, meaning most of the descriptors were obsolete
511 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
512 - Prevent bridge relays from serving their 'extrainfo' document
513 to anybody who asks, now that extrainfo docs include potentially
514 sensitive aggregated client geoip summaries. Bugfix on
516 - If the cached networkstatus consensus is more than five days old,
517 discard it rather than trying to use it. In theory it could be
518 useful because it lists alternate directory mirrors, but in practice
519 it just means we spend many minutes trying directory mirrors that
520 are long gone from the network. Also discard router descriptors as
521 we load them if they are more than five days old, since the onion
522 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
525 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
526 could make gcc generate non-functional binary search code. Bugfix
528 - Build correctly on platforms without socklen_t.
529 - Compile without warnings on solaris.
530 - Avoid potential crash on internal error during signature collection.
531 Fixes bug 864. Patch from rovv.
532 - Correct handling of possible malformed authority signing key
533 certificates with internal signature types. Fixes bug 880.
534 Bugfix on 0.2.0.3-alpha.
535 - Fix a hard-to-trigger resource leak when logging credential status.
537 - When we can't initialize DNS because the network is down, do not
538 automatically stop Tor from starting. Instead, we retry failed
539 dns_init() every 10 minutes, and change the exit policy to reject
540 *:* until one succeeds. Fixes bug 691.
541 - Use 64 bits instead of 32 bits for connection identifiers used with
542 the controller protocol, to greatly reduce risk of identifier reuse.
543 - When we're choosing an exit node for a circuit, and we have
544 no pending streams, choose a good general exit rather than one that
545 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
546 - Fix another case of assuming, when a specific exit is requested,
547 that we know more than the user about what hosts it allows.
548 Fixes one case of bug 752. Patch from rovv.
549 - Clip the MaxCircuitDirtiness config option to a minimum of 10
550 seconds. Warn the user if lower values are given in the
551 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
552 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
553 user if lower values are given in the configuration. Bugfix on
554 0.1.1.17-rc. Patch by Sebastian.
555 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
556 the cache because we already had a v0 descriptor with the same ID.
557 Bugfix on 0.2.0.18-alpha.
558 - Fix a race condition when freeing keys shared between main thread
559 and CPU workers that could result in a memory leak. Bugfix on
560 0.1.0.1-rc. Fixes bug 889.
561 - Send a valid END cell back when a client tries to connect to a
562 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
563 840. Patch from rovv.
564 - Check which hops rendezvous stream cells are associated with to
565 prevent possible guess-the-streamid injection attacks from
566 intermediate hops. Fixes another case of bug 446. Based on patch
568 - If a broken client asks a non-exit router to connect somewhere,
569 do not even do the DNS lookup before rejecting the connection.
570 Fixes another case of bug 619. Patch from rovv.
571 - When a relay gets a create cell it can't decrypt (e.g. because it's
572 using the wrong onion key), we were dropping it and letting the
573 client time out. Now actually answer with a destroy cell. Fixes
574 bug 904. Bugfix on 0.0.2pre8.
576 o Minor bugfixes (hidden services):
577 - Do not throw away existing introduction points on SIGHUP. Bugfix on
578 0.0.6pre1. Patch by Karsten. Fixes bug 874.
581 - Report the case where all signatures in a detached set are rejected
582 differently than the case where there is an error handling the
584 - When we realize that another process has modified our cached
585 descriptors, print out a more useful error message rather than
586 triggering an assertion. Fixes bug 885. Patch from Karsten.
587 - Implement the 0x20 hack to better resist DNS poisoning: set the
588 case on outgoing DNS requests randomly, and reject responses that do
589 not match the case correctly. This logic can be disabled with the
590 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
591 of servers that do not reliably preserve case in replies. See
592 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
594 - Check DNS replies for more matching fields to better resist DNS
596 - Never use OpenSSL compression: it wastes RAM and CPU trying to
597 compress cells, which are basically all encrypted, compressed, or
601 Changes in version 0.2.1.11-alpha - 2009-01-20
602 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
603 week it will take a long time to bootstrap again" bug. It also fixes
604 an important security-related bug reported by Ilja van Sprundel. You
605 should upgrade. (We'll send out more details about the bug once people
606 have had some time to upgrade.)
609 - Fix a heap-corruption bug that may be remotely triggerable on
610 some platforms. Reported by Ilja van Sprundel.
613 - Discard router descriptors as we load them if they are more than
614 five days old. Otherwise if Tor is off for a long time and then
615 starts with cached descriptors, it will try to use the onion
616 keys in those obsolete descriptors when building circuits. Bugfix
617 on 0.2.0.x. Fixes bug 887.
620 - Try to make sure that the version of Libevent we're running with
621 is binary-compatible with the one we built with. May address bug
623 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
624 for bug 905. Bugfix on 0.2.1.7-alpha.
625 - Add a new --enable-local-appdata configuration switch to change
626 the default location of the datadir on win32 from APPDATA to
627 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
628 entirely. Patch from coderman.
631 - Make outbound DNS packets respect the OutboundBindAddress setting.
632 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
633 - When our circuit fails at the first hop (e.g. we get a destroy
634 cell back), avoid using that OR connection anymore, and also
635 tell all the one-hop directory requests waiting for it that they
636 should fail. Bugfix on 0.2.1.3-alpha.
637 - In the torify(1) manpage, mention that tsocks will leak your
641 Changes in version 0.2.1.10-alpha - 2009-01-06
642 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
643 would make the bridge relay not so useful if it had DirPort set to 0,
644 and one that could let an attacker learn a little bit of information
645 about the bridge's users), and a bug that would cause your Tor relay
646 to ignore a circuit create request it can't decrypt (rather than reply
647 with an error). It also fixes a wide variety of other bugs.
650 - If the cached networkstatus consensus is more than five days old,
651 discard it rather than trying to use it. In theory it could
652 be useful because it lists alternate directory mirrors, but in
653 practice it just means we spend many minutes trying directory
654 mirrors that are long gone from the network. Helps bug 887 a bit;
656 - Bridge relays that had DirPort set to 0 would stop fetching
657 descriptors shortly after startup, and then briefly resume
658 after a new bandwidth test and/or after publishing a new bridge
659 descriptor. Bridge users that try to bootstrap from them would
660 get a recent networkstatus but would get descriptors from up to
661 18 hours earlier, meaning most of the descriptors were obsolete
662 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
663 - Prevent bridge relays from serving their 'extrainfo' document
664 to anybody who asks, now that extrainfo docs include potentially
665 sensitive aggregated client geoip summaries. Bugfix on
669 - New controller event "clients_seen" to report a geoip-based summary
670 of which countries we've seen clients from recently. Now controllers
671 like Vidalia can show bridge operators that they're actually making
673 - Build correctly against versions of OpenSSL 0.9.8 or later built
674 without support for deprecated functions.
675 - Update to the "December 19 2008" ip-to-country file.
677 o Minor bugfixes (on 0.2.0.x):
678 - Authorities now vote for the Stable flag for any router whose
679 weighted MTBF is at least 5 days, regardless of the mean MTBF.
680 - Do not remove routers as too old if we do not have any consensus
681 document. Bugfix on 0.2.0.7-alpha.
682 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
683 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
684 - When an exit relay resolves a stream address to a local IP address,
685 do not just keep retrying that same exit relay over and
686 over. Instead, just close the stream. Addresses bug 872. Bugfix
687 on 0.2.0.32. Patch from rovv.
688 - If a hidden service sends us an END cell, do not consider
689 retrying the connection; just close it. Patch from rovv.
690 - When we made bridge authorities stop serving bridge descriptors over
691 unencrypted links, we also broke DirPort reachability testing for
692 bridges. So bridges with a non-zero DirPort were printing spurious
693 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
694 - When a relay gets a create cell it can't decrypt (e.g. because it's
695 using the wrong onion key), we were dropping it and letting the
696 client time out. Now actually answer with a destroy cell. Fixes
697 bug 904. Bugfix on 0.0.2pre8.
698 - Squeeze 2-5% out of client performance (according to oprofile) by
699 improving the implementation of some policy-manipulation functions.
701 o Minor bugfixes (on 0.2.1.x):
702 - Make get_interface_address() function work properly again; stop
703 guessing the wrong parts of our address as our address.
704 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
705 send on that circuit. Otherwise we might violate the proposal-110
706 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
708 - When we're sending non-EXTEND cells to the first hop in a circuit,
709 for example to use an encrypted directory connection, we don't need
710 to use RELAY_EARLY cells: the first hop knows what kind of cell
711 it is, and nobody else can even see the cell type. Conserving
712 RELAY_EARLY cells makes it easier to cannibalize circuits like
714 - Stop logging nameserver addresses in reverse order.
715 - If we are retrying a directory download slowly over and over, do
716 not automatically give up after the 254th failure. Bugfix on
718 - Resume reporting accurate "stream end" reasons to the local control
719 port. They were lost in the changes for Proposal 148. Bugfix on
722 o Deprecated and removed features:
723 - The old "tor --version --version" command, which would print out
724 the subversion "Id" of most of the source files, is now removed. It
725 turned out to be less useful than we'd expected, and harder to
728 o Code simplifications and refactoring:
729 - Change our header file guard macros to be less likely to conflict
730 with system headers. Adam Langley noticed that we were conflicting
731 with log.h on Android.
732 - Tool-assisted documentation cleanup. Nearly every function or
733 static variable in Tor should have its own documentation now.
736 Changes in version 0.2.1.9-alpha - 2008-12-25
737 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
739 o New directory authorities:
740 - gabelmoo (the authority run by Karsten Loesing) now has a new
744 - Never use a connection with a mismatched address to extend a
745 circuit, unless that connection is canonical. A canonical
746 connection is one whose address is authenticated by the router's
747 identity key, either in a NETINFO cell or in a router descriptor.
748 - Avoid a possible memory corruption bug when receiving hidden service
749 descriptors. Bugfix on 0.2.1.6-alpha.
752 - Fix a logic error that would automatically reject all but the first
753 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
754 part of bug 813/868. Bug spotted by coderman.
755 - When a stream at an exit relay is in state "resolving" or
756 "connecting" and it receives an "end" relay cell, the exit relay
757 would silently ignore the end cell and not close the stream. If
758 the client never closes the circuit, then the exit relay never
759 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
761 - When we can't initialize DNS because the network is down, do not
762 automatically stop Tor from starting. Instead, retry failed
763 dns_init() every 10 minutes, and change the exit policy to reject
764 *:* until one succeeds. Fixes bug 691.
767 - Give a better error message when an overzealous init script says
768 "sudo -u username tor --user username". Makes Bug 882 easier for
770 - When a directory authority gives us a new guess for our IP address,
771 log which authority we used. Hopefully this will help us debug
772 the recent complaints about bad IP address guesses.
773 - Detect svn revision properly when we're using git-svn.
774 - Try not to open more than one descriptor-downloading connection
775 to an authority at once. This should reduce load on directory
776 authorities. Fixes bug 366.
777 - Add cross-certification to newly generated certificates, so that
778 a signing key is enough information to look up a certificate.
779 Partial implementation of proposal 157.
780 - Start serving certificates by <identity digest, signing key digest>
781 pairs. Partial implementation of proposal 157.
782 - Clients now never report any stream end reason except 'MISC'.
783 Implements proposal 148.
784 - On platforms with a maximum syslog string length, truncate syslog
785 messages to that length ourselves, rather than relying on the
786 system to do it for us.
787 - Optimize out calls to time(NULL) that occur for every IO operation,
788 or for every cell. On systems where time() is a slow syscall,
789 this fix will be slightly helpful.
790 - Exit servers can now answer resolve requests for ip6.arpa addresses.
791 - When we download a descriptor that we then immediately (as
792 a directory authority) reject, do not retry downloading it right
793 away. Should save some bandwidth on authorities. Fix for bug
794 888. Patch by Sebastian Hahn.
795 - When a download gets us zero good descriptors, do not notify
796 Tor that new directory information has arrived.
797 - Avoid some nasty corner cases in the logic for marking connections
798 as too old or obsolete or noncanonical for circuits. Partial
801 o Minor features (controller):
802 - New CONSENSUS_ARRIVED event to note when a new consensus has
803 been fetched and validated.
804 - When we realize that another process has modified our cached
805 descriptors file, print out a more useful error message rather
806 than triggering an assertion. Fixes bug 885. Patch from Karsten.
807 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
808 controllers to prevent SIGHUP from reloading the
809 configuration. Fixes bug 856.
812 - Resume using the correct "REASON=" stream when telling the
813 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
814 - When a canonical connection appears later in our internal list
815 than a noncanonical one for a given OR ID, always use the
816 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
818 - Clip the MaxCircuitDirtiness config option to a minimum of 10
819 seconds. Warn the user if lower values are given in the
820 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
821 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
822 user if lower values are given in the configuration. Bugfix on
823 0.1.1.17-rc. Patch by Sebastian.
824 - Fix a race condition when freeing keys shared between main thread
825 and CPU workers that could result in a memory leak. Bugfix on
826 0.1.0.1-rc. Fixes bug 889.
828 o Minor bugfixes (hidden services):
829 - Do not throw away existing introduction points on SIGHUP (bugfix on
830 0.0.6pre1); also, do not stall hidden services because we're
831 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
832 by John Brooks. Patch by Karsten. Fixes bug 874.
833 - Fix a memory leak when we decline to add a v2 rendezvous
834 descriptor to the cache because we already had a v0 descriptor
835 with the same ID. Bugfix on 0.2.0.18-alpha.
837 o Deprecated and removed features:
838 - RedirectExits has been removed. It was deprecated since
840 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
841 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
842 - Cell pools are now always enabled; --disable-cell-pools is ignored.
844 o Code simplifications and refactoring:
845 - Rename the confusing or_is_obsolete field to the more appropriate
846 is_bad_for_new_circs, and move it to or_connection_t where it
848 - Move edge-only flags from connection_t to edge_connection_t: not
849 only is this better coding, but on machines of plausible alignment,
850 it should save 4-8 bytes per connection_t. "Every little bit helps."
851 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
852 for consistency; keep old option working for backward compatibility.
853 - Simplify the code for finding connections to use for a circuit.
856 Changes in version 0.2.1.8-alpha - 2008-12-08
857 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
858 builds better on unusual platforms like Solaris and old OS X, and
859 fixes a variety of other issues.
862 - New DirPortFrontPage option that takes an html file and publishes
863 it as "/" on the DirPort. Now relay operators can provide a
864 disclaimer without needing to set up a separate webserver. There's
865 a sample disclaimer in contrib/tor-exit-notice.html.
868 - When the client is choosing entry guards, now it selects at most
869 one guard from a given relay family. Otherwise we could end up with
870 all of our entry points into the network run by the same operator.
871 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
874 - Fix a DOS opportunity during the voting signature collection process
875 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
876 - Fix a possible segfault when establishing an exit connection. Bugfix
880 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
882 - Made Tor a little less aggressive about deleting expired
883 certificates. Partial fix for bug 854.
884 - Stop doing unaligned memory access that generated bus errors on
885 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
886 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
887 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
888 - Make USR2 log-level switch take effect immediately. Bugfix on
890 - If one win32 nameserver fails to get added, continue adding the
891 rest, and don't automatically fail.
892 - Use fcntl() for locking when flock() is not available. Should fix
893 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
894 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
895 could make gcc generate non-functional binary search code. Bugfix
897 - Build correctly on platforms without socklen_t.
898 - Avoid potential crash on internal error during signature collection.
899 Fixes bug 864. Patch from rovv.
900 - Do not use C's stdio library for writing to log files. This will
901 improve logging performance by a minute amount, and will stop
902 leaking fds when our disk is full. Fixes bug 861.
903 - Stop erroneous use of O_APPEND in cases where we did not in fact
904 want to re-seek to the end of a file before every last write().
905 - Correct handling of possible malformed authority signing key
906 certificates with internal signature types. Fixes bug 880. Bugfix
908 - Fix a hard-to-trigger resource leak when logging credential status.
912 - Directory mirrors no longer fetch the v1 directory or
913 running-routers files. They are obsolete, and nobody asks for them
914 anymore. This is the first step to making v1 authorities obsolete.
916 o Minor features (controller):
917 - Return circuit purposes in response to GETINFO circuit-status. Fixes
921 Changes in version 0.2.0.32 - 2008-11-20
922 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
923 packages (and maybe other packages) noticed by Theo de Raadt, fixes
924 a smaller security flaw that might allow an attacker to access local
925 services, further improves hidden service performance, and fixes a
926 variety of other issues.
929 - The "User" and "Group" config options did not clear the
930 supplementary group entries for the Tor process. The "User" option
931 is now more robust, and we now set the groups to the specified
932 user's primary group. The "Group" option is now ignored. For more
933 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
934 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
935 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
936 - The "ClientDNSRejectInternalAddresses" config option wasn't being
937 consistently obeyed: if an exit relay refuses a stream because its
938 exit policy doesn't allow it, we would remember what IP address
939 the relay said the destination address resolves to, even if it's
940 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
943 - Fix a DOS opportunity during the voting signature collection process
944 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
946 o Major bugfixes (hidden services):
947 - When fetching v0 and v2 rendezvous service descriptors in parallel,
948 we were failing the whole hidden service request when the v0
949 descriptor fetch fails, even if the v2 fetch is still pending and
950 might succeed. Similarly, if the last v2 fetch fails, we were
951 failing the whole hidden service request even if a v0 fetch is
952 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
953 - When extending a circuit to a hidden service directory to upload a
954 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
955 requests failed, because the router descriptor has not been
956 downloaded yet. In these cases, do not attempt to upload the
957 rendezvous descriptor, but wait until the router descriptor is
958 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
959 descriptor from a hidden service directory for which the router
960 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
964 - Fix several infrequent memory leaks spotted by Coverity.
965 - When testing for libevent functions, set the LDFLAGS variable
966 correctly. Found by Riastradh.
967 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
968 bootstrapping with tunneled directory connections. Bugfix on
969 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
970 - When asked to connect to A.B.exit:80, if we don't know the IP for A
971 and we know that server B rejects most-but-not all connections to
972 port 80, we would previously reject the connection. Now, we assume
973 the user knows what they were asking for. Fixes bug 752. Bugfix
974 on 0.0.9rc5. Diagnosed by BarkerJr.
975 - If we overrun our per-second write limits a little, count this as
976 having used up our write allocation for the second, and choke
977 outgoing directory writes. Previously, we had only counted this when
978 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
979 Bugfix on 0.2.0.x (??).
980 - Remove the old v2 directory authority 'lefkada' from the default
981 list. It has been gone for many months.
982 - Stop doing unaligned memory access that generated bus errors on
983 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
984 - Make USR2 log-level switch take effect immediately. Bugfix on
987 o Minor bugfixes (controller):
988 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
989 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
992 Changes in version 0.2.1.7-alpha - 2008-11-08
993 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
994 packages (and maybe other packages) noticed by Theo de Raadt, fixes
995 a smaller security flaw that might allow an attacker to access local
996 services, adds better defense against DNS poisoning attacks on exit
997 relays, further improves hidden service performance, and fixes a
998 variety of other issues.
1001 - The "ClientDNSRejectInternalAddresses" config option wasn't being
1002 consistently obeyed: if an exit relay refuses a stream because its
1003 exit policy doesn't allow it, we would remember what IP address
1004 the relay said the destination address resolves to, even if it's
1005 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
1006 - The "User" and "Group" config options did not clear the
1007 supplementary group entries for the Tor process. The "User" option
1008 is now more robust, and we now set the groups to the specified
1009 user's primary group. The "Group" option is now ignored. For more
1010 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
1011 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
1012 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
1013 - Do not use or believe expired v3 authority certificates. Patch
1014 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
1017 - Now NodeFamily and MyFamily config options allow spaces in
1018 identity fingerprints, so it's easier to paste them in.
1019 Suggested by Lucky Green.
1020 - Implement the 0x20 hack to better resist DNS poisoning: set the
1021 case on outgoing DNS requests randomly, and reject responses that do
1022 not match the case correctly. This logic can be disabled with the
1023 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
1024 of servers that do not reliably preserve case in replies. See
1025 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
1027 - Preserve case in replies to DNSPort requests in order to support
1028 the 0x20 hack for resisting DNS poisoning attacks.
1030 o Hidden service performance improvements:
1031 - When the client launches an introduction circuit, retry with a
1032 new circuit after 30 seconds rather than 60 seconds.
1033 - Launch a second client-side introduction circuit in parallel
1034 after a delay of 15 seconds (based on work by Christian Wilms).
1035 - Hidden services start out building five intro circuits rather
1036 than three, and when the first three finish they publish a service
1037 descriptor using those. Now we publish our service descriptor much
1038 faster after restart.
1041 - Minor fix in the warning messages when you're having problems
1042 bootstrapping; also, be more forgiving of bootstrap problems when
1043 we're still making incremental progress on a given bootstrap phase.
1044 - When we're choosing an exit node for a circuit, and we have
1045 no pending streams, choose a good general exit rather than one that
1046 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
1047 - Send a valid END cell back when a client tries to connect to a
1048 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
1049 840. Patch from rovv.
1050 - If a broken client asks a non-exit router to connect somewhere,
1051 do not even do the DNS lookup before rejecting the connection.
1052 Fixes another case of bug 619. Patch from rovv.
1053 - Fix another case of assuming, when a specific exit is requested,
1054 that we know more than the user about what hosts it allows.
1055 Fixes another case of bug 752. Patch from rovv.
1056 - Check which hops rendezvous stream cells are associated with to
1057 prevent possible guess-the-streamid injection attacks from
1058 intermediate hops. Fixes another case of bug 446. Based on patch
1060 - Avoid using a negative right-shift when comparing 32-bit
1061 addresses. Possible fix for bug 845 and bug 811.
1062 - Make the assert_circuit_ok() function work correctly on circuits that
1063 have already been marked for close.
1064 - Fix read-off-the-end-of-string error in unit tests when decoding
1065 introduction points.
1066 - Fix uninitialized size field for memory area allocation: may improve
1067 memory performance during directory parsing.
1068 - Treat duplicate certificate fetches as failures, so that we do
1069 not try to re-fetch an expired certificate over and over and over.
1070 - Do not say we're fetching a certificate when we'll in fact skip it
1071 because of a pending download.
1074 Changes in version 0.2.1.6-alpha - 2008-09-30
1075 Tor 0.2.1.6-alpha further improves performance and robustness of
1076 hidden services, starts work on supporting per-country relay selection,
1077 and fixes a variety of smaller issues.
1080 - Implement proposal 121: make it possible to build hidden services
1081 that only certain clients are allowed to connect to. This is
1082 enforced at several points, so that unauthorized clients are unable
1083 to send INTRODUCE cells to the service, or even (depending on the
1084 type of authentication) to learn introduction points. This feature
1085 raises the bar for certain kinds of active attacks against hidden
1086 services. Code by Karsten Loesing.
1087 - Relays now store and serve v2 hidden service descriptors by default,
1088 i.e., the new default value for HidServDirectoryV2 is 1. This is
1089 the last step in proposal 114, which aims to make hidden service
1090 lookups more reliable.
1091 - Start work to allow node restrictions to include country codes. The
1092 syntax to exclude nodes in a country with country code XX is
1093 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
1094 refinement to decide what config options should take priority if
1095 you ask to both use a particular node and exclude it.
1096 - Allow ExitNodes list to include IP ranges and country codes, just
1097 like the Exclude*Nodes lists. Patch from Robert Hogan.
1100 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
1101 Tor to fail to start if you had it configured to use a bridge
1102 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
1103 - When extending a circuit to a hidden service directory to upload a
1104 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
1105 requests failed, because the router descriptor had not been
1106 downloaded yet. In these cases, we now wait until the router
1107 descriptor is downloaded, and then retry. Likewise, clients
1108 now skip over a hidden service directory if they don't yet have
1109 its router descriptor, rather than futilely requesting it and
1110 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
1112 - When fetching v0 and v2 rendezvous service descriptors in parallel,
1113 we were failing the whole hidden service request when the v0
1114 descriptor fetch fails, even if the v2 fetch is still pending and
1115 might succeed. Similarly, if the last v2 fetch fails, we were
1116 failing the whole hidden service request even if a v0 fetch is
1117 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
1118 - DNS replies need to have names matching their requests, but
1119 these names should be in the questions section, not necessarily
1120 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
1123 - Update to the "September 1 2008" ip-to-country file.
1124 - Allow ports 465 and 587 in the default exit policy again. We had
1125 rejected them in 0.1.0.15, because back in 2005 they were commonly
1126 misconfigured and ended up as spam targets. We hear they are better
1127 locked down these days.
1128 - Use a lockfile to make sure that two Tor processes are not
1129 simultaneously running with the same datadir.
1130 - Serve the latest v3 networkstatus consensus via the control
1131 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
1132 - Better logging about stability/reliability calculations on directory
1134 - Drop the requirement to have an open dir port for storing and
1135 serving v2 hidden service descriptors.
1136 - Directory authorities now serve a /tor/dbg-stability.txt URL to
1137 help debug WFU and MTBF calculations.
1138 - Implement most of Proposal 152: allow specialized servers to permit
1139 single-hop circuits, and clients to use those servers to build
1140 single-hop circuits when using a specialized controller. Patch
1141 from Josh Albrecht. Resolves feature request 768.
1142 - Add a -p option to tor-resolve for specifying the SOCKS port: some
1143 people find host:port too confusing.
1144 - Make TrackHostExit mappings expire a while after their last use, not
1145 after their creation. Patch from Robert Hogan.
1146 - Provide circuit purposes along with circuit events to the controller.
1149 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
1151 - Fixed some memory leaks -- some quite frequent, some almost
1152 impossible to trigger -- based on results from Coverity.
1153 - When testing for libevent functions, set the LDFLAGS variable
1154 correctly. Found by Riastradh.
1155 - Fix an assertion bug in parsing policy-related options; possible fix
1157 - Catch and report a few more bootstrapping failure cases when Tor
1158 fails to establish a TCP connection. Cleanup on 0.2.1.x.
1159 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
1160 bootstrapping with tunneled directory connections. Bugfix on
1161 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
1162 - When asked to connect to A.B.exit:80, if we don't know the IP for A
1163 and we know that server B rejects most-but-not all connections to
1164 port 80, we would previously reject the connection. Now, we assume
1165 the user knows what they were asking for. Fixes bug 752. Bugfix
1166 on 0.0.9rc5. Diagnosed by BarkerJr.
1167 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
1168 service directories if they have no advertised dir port. Bugfix
1170 - If we overrun our per-second write limits a little, count this as
1171 having used up our write allocation for the second, and choke
1172 outgoing directory writes. Previously, we had only counted this when
1173 we had met our limits precisely. Fixes bug 824. Patch by rovv.
1174 Bugfix on 0.2.0.x (??).
1175 - Avoid a "0 divided by 0" calculation when calculating router uptime
1176 at directory authorities. Bugfix on 0.2.0.8-alpha.
1177 - Make DNS resolved controller events into "CLOSED", not
1178 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
1180 - Fix a bug where an unreachable relay would establish enough
1181 reachability testing circuits to do a bandwidth test -- if
1182 we already have a connection to the middle hop of the testing
1183 circuit, then it could establish the last hop by using the existing
1184 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
1185 circuits no longer use entry guards in 0.2.1.3-alpha.
1186 - If we have correct permissions on $datadir, we complain to stdout
1187 and fail to start. But dangerous permissions on
1188 $datadir/cached-status/ would cause us to open a log and complain
1189 there. Now complain to stdout and fail to start in both cases. Fixes
1190 bug 820, reported by seeess.
1191 - Remove the old v2 directory authority 'lefkada' from the default
1192 list. It has been gone for many months.
1194 o Code simplifications and refactoring:
1195 - Revise the connection_new functions so that a more typesafe variant
1196 exists. This will work better with Coverity, and let us find any
1197 actual mistakes we're making here.
1198 - Refactor unit testing logic so that dmalloc can be used sensibly
1199 with unit tests to check for memory leaks.
1200 - Move all hidden-service related fields from connection and circuit
1201 structure to substructures: this way they won't eat so much memory.
1204 Changes in version 0.2.0.31 - 2008-09-03
1205 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
1206 a big bug we're seeing where in rare cases traffic from one Tor stream
1207 gets mixed into another stream, and fixes a variety of smaller issues.
1210 - Make sure that two circuits can never exist on the same connection
1211 with the same circuit ID, even if one is marked for close. This
1212 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
1213 - Relays now reject risky extend cells: if the extend cell includes
1214 a digest of all zeroes, or asks to extend back to the relay that
1215 sent the extend cell, tear down the circuit. Ideas suggested
1217 - If not enough of our entry guards are available so we add a new
1218 one, we might use the new one even if it overlapped with the
1219 current circuit's exit relay (or its family). Anonymity bugfix
1220 pointed out by rovv.
1223 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
1224 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
1225 - Correctly detect the presence of the linux/netfilter_ipv4.h header
1226 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
1227 - Pick size of default geoip filename string correctly on windows.
1228 Fixes bug 806. Bugfix on 0.2.0.30.
1229 - Make the autoconf script accept the obsolete --with-ssl-dir
1230 option as an alias for the actually-working --with-openssl-dir
1231 option. Fix the help documentation to recommend --with-openssl-dir.
1232 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
1233 - When using the TransPort option on OpenBSD, and using the User
1234 option to change UID and drop privileges, make sure to open
1235 /dev/pf before dropping privileges. Fixes bug 782. Patch from
1236 Christopher Davis. Bugfix on 0.1.2.1-alpha.
1237 - Try to attach connections immediately upon receiving a RENDEZVOUS2
1238 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
1239 on the client side when connecting to a hidden service. Bugfix
1240 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
1241 - When closing an application-side connection because its circuit is
1242 getting torn down, generate the stream event correctly. Bugfix on
1243 0.1.2.x. Anonymous patch.
1246 Changes in version 0.2.1.5-alpha - 2008-08-31
1247 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
1248 in a lot of the infrastructure for adding authorization to hidden
1249 services, lays the groundwork for having clients read their load
1250 balancing information out of the networkstatus consensus rather than
1251 the individual router descriptors, addresses two potential anonymity
1252 issues, and fixes a variety of smaller issues.
1255 - Convert many internal address representations to optionally hold
1257 - Generate and accept IPv6 addresses in many protocol elements.
1258 - Make resolver code handle nameservers located at ipv6 addresses.
1259 - Begin implementation of proposal 121 ("Client authorization for
1260 hidden services"): configure hidden services with client
1261 authorization, publish descriptors for them, and configure
1262 authorization data for hidden services at clients. The next
1263 step is to actually access hidden services that perform client
1265 - More progress toward proposal 141: Network status consensus
1266 documents and votes now contain bandwidth information for each
1267 router and a summary of that router's exit policy. Eventually this
1268 will be used by clients so that they do not have to download every
1269 known descriptor before building circuits.
1271 o Major bugfixes (on 0.2.0.x and before):
1272 - When sending CREATED cells back for a given circuit, use a 64-bit
1273 connection ID to find the right connection, rather than an addr:port
1274 combination. Now that we can have multiple OR connections between
1275 the same ORs, it is no longer possible to use addr:port to uniquely
1276 identify a connection.
1277 - Relays now reject risky extend cells: if the extend cell includes
1278 a digest of all zeroes, or asks to extend back to the relay that
1279 sent the extend cell, tear down the circuit. Ideas suggested
1281 - If not enough of our entry guards are available so we add a new
1282 one, we might use the new one even if it overlapped with the
1283 current circuit's exit relay (or its family). Anonymity bugfix
1284 pointed out by rovv.
1287 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
1288 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
1289 - When using the TransPort option on OpenBSD, and using the User
1290 option to change UID and drop privileges, make sure to open /dev/pf
1291 before dropping privileges. Fixes bug 782. Patch from Christopher
1292 Davis. Bugfix on 0.1.2.1-alpha.
1293 - Correctly detect the presence of the linux/netfilter_ipv4.h header
1294 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
1295 - Add a missing safe_str() call for a debug log message.
1296 - Use 64 bits instead of 32 bits for connection identifiers used with
1297 the controller protocol, to greatly reduce risk of identifier reuse.
1298 - Make the autoconf script accept the obsolete --with-ssl-dir
1299 option as an alias for the actually-working --with-openssl-dir
1300 option. Fix the help documentation to recommend --with-openssl-dir.
1301 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
1304 - Rate-limit too-many-sockets messages: when they happen, they happen
1305 a lot. Resolves bug 748.
1306 - Resist DNS poisoning a little better by making sure that names in
1307 answer sections match.
1308 - Print the SOCKS5 error message string as well as the error code
1309 when a tor-resolve request fails. Patch from Jacob.
1312 Changes in version 0.2.1.4-alpha - 2008-08-04
1313 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
1316 - The address part of exit policies was not correctly written
1317 to router descriptors. This generated router descriptors that failed
1318 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
1320 - Tor triggered a false assert when extending a circuit to a relay
1321 but we already have a connection open to that relay. Noticed by
1322 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
1325 - Fix a hidden service logging bug: in some edge cases, the router
1326 descriptor of a previously picked introduction point becomes
1327 obsolete and we need to give up on it rather than continually
1328 complaining that it has become obsolete. Observed by xiando. Bugfix
1332 - Take out the TestVia config option, since it was a workaround for
1333 a bug that was fixed in Tor 0.1.1.21.
1336 Changes in version 0.2.1.3-alpha - 2008-08-03
1337 Tor 0.2.1.3-alpha implements most of the pieces to prevent
1338 infinite-length circuit attacks (see proposal 110); fixes a bug that
1339 might cause exit relays to corrupt streams they send back; allows
1340 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
1341 ExcludeExitNodes config options; and fixes a big pile of bugs.
1343 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
1344 - Send a bootstrap problem "warn" event on the first problem if the
1345 reason is NO_ROUTE (that is, our network is down).
1348 - Implement most of proposal 110: The first K cells to be sent
1349 along a circuit are marked as special "early" cells; only K "early"
1350 cells will be allowed. Once this code is universal, we can block
1351 certain kinds of DOS attack by requiring that EXTEND commands must
1352 be sent using an "early" cell.
1355 - Try to attach connections immediately upon receiving a RENDEZVOUS2
1356 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
1357 on the client side when connecting to a hidden service. Bugfix
1358 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
1359 - Ensure that two circuits can never exist on the same connection
1360 with the same circuit ID, even if one is marked for close. This
1361 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
1364 - When relays do their initial bandwidth measurement, don't limit
1365 to just our entry guards for the test circuits. Otherwise we tend
1366 to have multiple test circuits going through a single entry guard,
1367 which makes our bandwidth test less accurate. Fixes part of bug 654;
1368 patch contributed by Josh Albrecht.
1369 - Add an ExcludeExitNodes option so users can list a set of nodes
1370 that should be be excluded from the exit node position, but
1371 allowed elsewhere. Implements proposal 151.
1372 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
1373 ExcludeNodes and ExcludeExitNodes lists.
1374 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
1375 be more efficient. Formerly it was quadratic in the number of
1376 servers; now it should be linear. Fixes bug 509.
1377 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
1378 and n_conn_id_digest fields into a separate structure that's
1379 only needed when the circuit has not yet attached to an n_conn.
1382 - Change the contrib/tor.logrotate script so it makes the new
1383 logs as "_tor:_tor" rather than the default, which is generally
1384 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
1385 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
1386 warnings (occasionally), but it can also cause the compiler to
1387 eliminate error-checking code. Suggested by Peter Gutmann.
1388 - When a hidden service is giving up on an introduction point candidate
1389 that was not included in the last published rendezvous descriptor,
1390 don't reschedule publication of the next descriptor. Fixes bug 763.
1392 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
1393 HiddenServiceExcludeNodes as obsolete: they never worked properly,
1394 and nobody claims to be using them. Fixes bug 754. Bugfix on
1395 0.1.0.1-rc. Patch from Christian Wilms.
1396 - Fix a small alignment and memory-wasting bug on buffer chunks.
1399 o Minor bugfixes (controller):
1400 - When closing an application-side connection because its circuit
1401 is getting torn down, generate the stream event correctly.
1402 Bugfix on 0.1.2.x. Anonymous patch.
1405 - Remove all backward-compatibility code to support relays running
1406 versions of Tor so old that they no longer work at all on the
1410 Changes in version 0.2.0.30 - 2008-07-15
1412 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
1413 warnings (occasionally), but it can also cause the compiler to
1414 eliminate error-checking code. Suggested by Peter Gutmann.
1417 Changes in version 0.2.0.29-rc - 2008-07-08
1418 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
1419 hidden-service performance bugs, and fixes a bunch of smaller bugs.
1422 - If you have more than one bridge but don't know their keys,
1423 you would only launch a request for the descriptor of the first one
1424 on your list. (Tor considered launching requests for the others, but
1425 found that it already had a connection on the way for $0000...0000
1426 so it didn't open another.) Bugfix on 0.2.0.x.
1427 - If you have more than one bridge but don't know their keys, and the
1428 connection to one of the bridges failed, you would cancel all
1429 pending bridge connections. (After all, they all have the same
1430 digest.) Bugfix on 0.2.0.x.
1431 - When a hidden service was trying to establish an introduction point,
1432 and Tor had built circuits preemptively for such purposes, we
1433 were ignoring all the preemptive circuits and launching a new one
1434 instead. Bugfix on 0.2.0.14-alpha.
1435 - When a hidden service was trying to establish an introduction point,
1436 and Tor *did* manage to reuse one of the preemptively built
1437 circuits, it didn't correctly remember which one it used,
1438 so it asked for another one soon after, until there were no
1439 more preemptive circuits, at which point it launched one from
1440 scratch. Bugfix on 0.0.9.x.
1441 - Make directory servers include the X-Your-Address-Is: http header in
1442 their responses even for begin_dir conns. Now clients who only
1443 ever use begin_dir connections still have a way to learn their IP
1444 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
1447 - Fix a macro/CPP interaction that was confusing some compilers:
1448 some GCCs don't like #if/#endif pairs inside macro arguments.
1450 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
1451 Fixes bug 704; fix from Steven Murdoch.
1452 - When opening /dev/null in finish_daemonize(), do not pass the
1453 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
1454 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
1455 - Correctly detect transparent proxy support on Linux hosts that
1456 require in.h to be included before netfilter_ipv4.h. Patch
1458 - Disallow session resumption attempts during the renegotiation
1459 stage of the v2 handshake protocol. Clients should never be trying
1460 session resumption at this point, but apparently some did, in
1461 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
1462 found by Geoff Goodell.
1465 Changes in version 0.2.1.2-alpha - 2008-06-20
1466 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
1467 make it easier to set up your own private Tor network; fixes several
1468 big bugs with using more than one bridge relay; fixes a big bug with
1469 offering hidden services quickly after Tor starts; and uses a better
1470 API for reporting potential bootstrapping problems to the controller.
1473 - New TestingTorNetwork config option to allow adjustment of
1474 previously constant values that, while reasonable, could slow
1475 bootstrapping. Implements proposal 135. Patch from Karsten.
1478 - If you have more than one bridge but don't know their digests,
1479 you would only learn a request for the descriptor of the first one
1480 on your list. (Tor considered launching requests for the others, but
1481 found that it already had a connection on the way for $0000...0000
1482 so it didn't open another.) Bugfix on 0.2.0.x.
1483 - If you have more than one bridge but don't know their digests,
1484 and the connection to one of the bridges failed, you would cancel
1485 all pending bridge connections. (After all, they all have the
1486 same digest.) Bugfix on 0.2.0.x.
1487 - When establishing a hidden service, introduction points that
1488 originate from cannibalized circuits are completely ignored and not
1489 included in rendezvous service descriptors. This might be another
1490 reason for delay in making a hidden service available. Bugfix
1491 from long ago (0.0.9.x?)
1494 - Allow OpenSSL to use dynamic locks if it wants.
1495 - When building a consensus, do not include routers that are down.
1496 This will cut down 30% to 40% on consensus size. Implements
1498 - In directory authorities' approved-routers files, allow
1499 fingerprints with or without space.
1500 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
1501 controller can query our current bootstrap state in case it attaches
1502 partway through and wants to catch up.
1503 - Send an initial "Starting" bootstrap status event, so we have a
1504 state to start out in.
1507 - Asking for a conditional consensus at .../consensus/<fingerprints>
1508 would crash a dirserver if it did not already have a
1509 consensus. Bugfix on 0.2.1.1-alpha.
1510 - Clean up some macro/CPP interactions: some GCC versions don't like
1511 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
1514 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
1515 - Directory authorities shouldn't complain about bootstrapping
1516 problems just because they do a lot of reachability testing and
1517 some of the connection attempts fail.
1518 - Start sending "count" and "recommendation" key/value pairs in
1519 bootstrap problem status events, so the controller can hear about
1520 problems even before Tor decides they're worth reporting for sure.
1521 - If you're using bridges, generate "bootstrap problem" warnings
1522 as soon as you run out of working bridges, rather than waiting
1523 for ten failures -- which will never happen if you have less than
1525 - If we close our OR connection because there's been a circuit
1526 pending on it for too long, we were telling our bootstrap status
1527 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
1530 Changes in version 0.2.1.1-alpha - 2008-06-13
1531 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
1532 were making the Tor process bloat especially on Linux; makes our TLS
1533 handshake blend in better; sends "bootstrap phase" status events to
1534 the controller, so it can keep the user informed of progress (and
1535 problems) fetching directory information and establishing circuits;
1536 and adds a variety of smaller features.
1539 - More work on making our TLS handshake blend in: modify the list
1540 of ciphers advertised by OpenSSL in client mode to even more
1541 closely resemble a common web browser. We cheat a little so that
1542 we can advertise ciphers that the locally installed OpenSSL doesn't
1544 - Start sending "bootstrap phase" status events to the controller,
1545 so it can keep the user informed of progress fetching directory
1546 information and establishing circuits. Also inform the controller
1547 if we think we're stuck at a particular bootstrap phase. Implements
1549 - Resume using OpenSSL's RAND_poll() for better (and more portable)
1550 cross-platform entropy collection again. We used to use it, then
1551 stopped using it because of a bug that could crash systems that
1552 called RAND_poll when they had a lot of fds open. It looks like the
1553 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
1554 at startup, and to call RAND_poll() when we reseed later only if
1555 we have a non-buggy OpenSSL version.
1558 - When we choose to abandon a new entry guard because we think our
1559 older ones might be better, close any circuits pending on that
1560 new entry guard connection. This fix should make us recover much
1561 faster when our network is down and then comes back. Bugfix on
1562 0.1.2.8-beta; found by lodger.
1564 o Memory fixes and improvements:
1565 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
1566 to avoid unused RAM in buffer chunks and memory pools.
1567 - Speed up parsing and cut down on memory fragmentation by using
1568 stack-style allocations for parsing directory objects. Previously,
1569 this accounted for over 40% of allocations from within Tor's code
1570 on a typical directory cache.
1571 - Use a Bloom filter rather than a digest-based set to track which
1572 descriptors we need to keep around when we're cleaning out old
1573 router descriptors. This speeds up the computation significantly,
1574 and may reduce fragmentation.
1575 - Reduce the default smartlist size from 32 to 16; it turns out that
1576 most smartlists hold around 8-12 elements tops.
1577 - Make dumpstats() log the fullness and size of openssl-internal
1579 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
1580 patch to their OpenSSL, turn it on to save memory on servers. This
1581 patch will (with any luck) get included in a mainline distribution
1583 - Never use OpenSSL compression: it wastes RAM and CPU trying to
1584 compress cells, which are basically all encrypted, compressed,
1588 - Stop reloading the router list from disk for no reason when we
1589 run out of reachable directory mirrors. Once upon a time reloading
1590 it would set the 'is_running' flag back to 1 for them. It hasn't
1591 done that for a long time.
1592 - In very rare situations new hidden service descriptors were
1593 published earlier than 30 seconds after the last change to the
1594 service. (We currently think that a hidden service descriptor
1595 that's been stable for 30 seconds is worth publishing.)
1598 - Allow separate log levels to be configured for different logging
1599 domains. For example, this allows one to log all notices, warnings,
1600 or errors, plus all memory management messages of level debug or
1601 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
1602 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
1603 and stop using a warning that had become unfixably verbose under
1605 - New --hush command-line option similar to --quiet. While --quiet
1606 disables all logging to the console on startup, --hush limits the
1607 output to messages of warning and error severity.
1608 - Servers support a new URL scheme for consensus downloads that
1609 allows the client to specify which authorities are trusted.
1610 The server then only sends the consensus if the client will trust
1611 it. Otherwise a 404 error is sent back. Clients use this
1612 new scheme when the server supports it (meaning it's running
1613 0.2.1.1-alpha or later). Implements proposal 134.
1614 - New configure/torrc options (--enable-geoip-stats,
1615 DirRecordUsageByCountry) to record how many IPs we've served
1616 directory info to in each country code, how many status documents
1617 total we've sent to each country code, and what share of the total
1618 directory requests we should expect to see.
1619 - Use the TLS1 hostname extension to more closely resemble browser
1621 - Lots of new unit tests.
1622 - Add a macro to implement the common pattern of iterating through
1623 two parallel lists in lockstep.
1626 Changes in version 0.2.0.28-rc - 2008-06-13
1627 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
1628 performance bug, and fixes a bunch of smaller bugs.
1631 - Fix a bug where, when we were choosing the 'end stream reason' to
1632 put in our relay end cell that we send to the exit relay, Tor
1633 clients on Windows were sometimes sending the wrong 'reason'. The
1634 anonymity problem is that exit relays may be able to guess whether
1635 the client is running Windows, thus helping partition the anonymity
1636 set. Down the road we should stop sending reasons to exit relays,
1637 or otherwise prevent future versions of this bug.
1640 - While setting up a hidden service, some valid introduction circuits
1641 were overlooked and abandoned. This might be the reason for
1642 the long delay in making a hidden service available. Bugfix on
1646 - Update to the "June 9 2008" ip-to-country file.
1647 - Run 'make test' as part of 'make dist', so we stop releasing so
1648 many development snapshots that fail their unit tests.
1651 - When we're checking if we have enough dir info for each relay
1652 to begin establishing circuits, make sure that we actually have
1653 the descriptor listed in the consensus, not just any descriptor.
1655 - Bridge relays no longer print "xx=0" in their extrainfo document
1656 for every single country code in the geoip db. Bugfix on
1658 - Only warn when we fail to load the geoip file if we were planning to
1659 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
1660 - If we change our MaxAdvertisedBandwidth and then reload torrc,
1661 Tor won't realize it should publish a new relay descriptor. Fixes
1662 bug 688, reported by mfr. Bugfix on 0.1.2.x.
1663 - When we haven't had any application requests lately, don't bother
1664 logging that we have expired a bunch of descriptors. Bugfix
1666 - Make relay cells written on a connection count as non-padding when
1667 tracking how long a connection has been in use. Bugfix on
1668 0.2.0.1-alpha. Spotted by lodger.
1669 - Fix unit tests in 0.2.0.27-rc.
1670 - Fix compile on Windows.
1673 Changes in version 0.2.0.27-rc - 2008-06-03
1674 Tor 0.2.0.27-rc adds a few features we left out of the earlier
1675 release candidates. In particular, we now include an IP-to-country
1676 GeoIP database, so controllers can easily look up what country a
1677 given relay is in, and so bridge relays can give us some sanitized
1678 summaries about which countries are making use of bridges. (See proposal
1679 126-geoip-fetching.txt for details.)
1682 - Include an IP-to-country GeoIP file in the tarball, so bridge
1683 relays can report sanitized summaries of the usage they're seeing.
1686 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
1687 Robert Hogan. Fixes the first part of bug 681.
1688 - Make bridge authorities never serve extrainfo docs.
1689 - Add support to detect Libevent versions in the 1.4.x series
1691 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
1692 - Include a new contrib/tor-exit-notice.html file that exit relay
1693 operators can put on their website to help reduce abuse queries.
1696 - When tunneling an encrypted directory connection, and its first
1697 circuit fails, do not leave it unattached and ask the controller
1698 to deal. Fixes the second part of bug 681.
1699 - Make bridge authorities correctly expire old extrainfo documents
1703 Changes in version 0.2.0.26-rc - 2008-05-13
1704 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
1705 in Debian's OpenSSL packages. All users running any 0.2.0.x version
1706 should upgrade, whether they're running Debian or not.
1708 o Major security fixes:
1709 - Use new V3 directory authority keys on the tor26, gabelmoo, and
1710 moria1 V3 directory authorities. The old keys were generated with
1711 a vulnerable version of Debian's OpenSSL package, and must be
1712 considered compromised. Other authorities' keys were not generated
1713 with an affected version of OpenSSL.
1716 - List authority signatures as "unrecognized" based on DirServer
1717 lines, not on cert cache. Bugfix on 0.2.0.x.
1720 - Add a new V3AuthUseLegacyKey option to make it easier for
1721 authorities to change their identity keys if they have to.
1724 Changes in version 0.2.0.25-rc - 2008-04-23
1725 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
1728 - Remember to initialize threading before initializing logging.
1729 Otherwise, many BSD-family implementations will crash hard on
1730 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
1733 - Authorities correctly free policies on bad servers on
1734 exit. Fixes bug 672. Bugfix on 0.2.0.x.
1737 Changes in version 0.2.0.24-rc - 2008-04-22
1738 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
1739 v3 directory authority, makes relays with dynamic IP addresses and no
1740 DirPort notice more quickly when their IP address changes, fixes a few
1741 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
1743 o New directory authorities:
1744 - Take lefkada out of the list of v3 directory authorities, since
1745 it has been down for months.
1746 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
1750 - Detect address changes more quickly on non-directory mirror
1751 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
1753 o Minor features (security):
1754 - Reject requests for reverse-dns lookup of names that are in
1755 a private address space. Patch from lodger.
1756 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
1759 o Minor bugfixes (crashes):
1760 - Avoid a rare assert that can trigger when Tor doesn't have much
1761 directory information yet and it tries to fetch a v2 hidden
1762 service descriptor. Fixes bug 651, reported by nwf.
1763 - Initialize log mutex before initializing dmalloc. Otherwise,
1764 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
1765 - Use recursive pthread mutexes in order to avoid deadlock when
1766 logging debug-level messages to a controller. Bug spotted by nwf,
1767 bugfix on 0.2.0.16-alpha.
1769 o Minor bugfixes (resource management):
1770 - Keep address policies from leaking memory: start their refcount
1771 at 1, not 2. Bugfix on 0.2.0.16-alpha.
1772 - Free authority certificates on exit, so they don't look like memory
1773 leaks. Bugfix on 0.2.0.19-alpha.
1774 - Free static hashtables for policy maps and for TLS connections on
1775 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
1776 - Avoid allocating extra space when computing consensuses on 64-bit
1777 platforms. Bug spotted by aakova.
1779 o Minor bugfixes (misc):
1780 - Do not read the configuration file when we've only been told to
1781 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
1782 based on patch from Sebastian Hahn.
1783 - Exit relays that are used as a client can now reach themselves
1784 using the .exit notation, rather than just launching an infinite
1785 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
1786 - When attempting to open a logfile fails, tell us why.
1787 - Fix a dumb bug that was preventing us from knowing that we should
1788 preemptively build circuits to handle expected directory requests.
1789 Fixes bug 660. Bugfix on 0.1.2.x.
1790 - Warn less verbosely about clock skew from netinfo cells from
1791 untrusted sources. Fixes bug 663.
1792 - Make controller stream events for DNS requests more consistent,
1793 by adding "new stream" events for DNS requests, and removing
1794 spurious "stream closed" events" for cached reverse resolves.
1795 Patch from mwenge. Fixes bug 646.
1796 - Correctly notify one-hop connections when a circuit build has
1797 failed. Possible fix for bug 669. Found by lodger.
1800 Changes in version 0.2.0.23-rc - 2008-03-24
1801 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
1802 makes bootstrapping faster if the first directory mirror you contact
1803 is down. The bundles also include the new Vidalia 0.1.2 release.
1806 - When a tunneled directory request is made to a directory server
1807 that's down, notice after 30 seconds rather than 120 seconds. Also,
1808 fail any begindir streams that are pending on it, so they can
1809 retry elsewhere. This was causing multi-minute delays on bootstrap.
1812 Changes in version 0.2.0.22-rc - 2008-03-18
1813 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
1814 enables encrypted directory connections by default for non-relays, fixes
1815 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
1816 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
1819 - Enable encrypted directory connections by default for non-relays,
1820 so censor tools that block Tor directory connections based on their
1821 plaintext patterns will no longer work. This means Tor works in
1822 certain censored countries by default again.
1825 - Make sure servers always request certificates from clients during
1826 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
1827 - Do not enter a CPU-eating loop when a connection is closed in
1828 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
1829 diagnosed by lodger; bugfix on 0.2.0.20-rc.
1830 - Fix assertion failure that could occur when a blocked circuit
1831 became unblocked, and it had pending client DNS requests. Bugfix
1832 on 0.2.0.1-alpha. Fixes bug 632.
1834 o Minor bugfixes (on 0.1.2.x):
1835 - Generate "STATUS_SERVER" events rather than misspelled
1836 "STATUS_SEVER" events. Caught by mwenge.
1837 - When counting the number of bytes written on a TLS connection,
1838 look at the BIO actually used for writing to the network, not
1839 at the BIO used (sometimes) to buffer data for the network.
1840 Looking at different BIOs could result in write counts on the
1841 order of ULONG_MAX. Fixes bug 614.
1842 - On Windows, correctly detect errors when listing the contents of
1843 a directory. Fix from lodger.
1845 o Minor bugfixes (on 0.2.0.x):
1846 - Downgrade "sslv3 alert handshake failure" message to INFO.
1847 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
1848 left BandwidthRate and BandwidthBurst at the default, we would be
1849 silently limited by those defaults. Now raise them to match the
1850 RelayBandwidth* values.
1851 - Fix the SVK version detection logic to work correctly on a branch.
1852 - Make --enable-openbsd-malloc work correctly on Linux with alpha
1853 CPUs. Fixes bug 625.
1854 - Logging functions now check that the passed severity is sane.
1855 - Use proper log levels in the testsuite call of
1856 get_interface_address6().
1857 - When using a nonstandard malloc, do not use the platform values for
1858 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
1859 - Make the openbsd malloc code use 8k pages on alpha CPUs and
1861 - Detect mismatched page sizes when using --enable-openbsd-malloc.
1862 - Avoid double-marked-for-close warning when certain kinds of invalid
1863 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
1864 for bug 617. Bugfix on 0.2.0.1-alpha.
1865 - Make sure that the "NULL-means-reject *:*" convention is followed by
1866 all the policy manipulation functions, avoiding some possible crash
1867 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
1868 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
1869 actually works, and doesn't warn about every single reverse lookup.
1870 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
1873 - Only log guard node status when guard node status has changed.
1874 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
1875 make "INFO" 75% less verbose.
1878 Changes in version 0.2.0.21-rc - 2008-03-02
1879 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
1880 makes Tor work well with Vidalia again, fixes a rare assert bug,
1881 and fixes a pair of more minor bugs. The bundles also include Vidalia
1882 0.1.0 and Torbutton 1.1.16.
1885 - The control port should declare that it requires password auth
1886 when HashedControlSessionPassword is set too. Patch from Matt Edman;
1887 bugfix on 0.2.0.20-rc. Fixes bug 615.
1888 - Downgrade assert in connection_buckets_decrement() to a log message.
1889 This may help us solve bug 614, and in any case will make its
1890 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
1891 - We were sometimes miscounting the number of bytes read from the
1892 network, causing our rate limiting to not be followed exactly.
1893 Bugfix on 0.2.0.16-alpha. Reported by lodger.
1896 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
1897 OpenSSL versions should have been working fine. Diagnosis and patch
1898 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
1899 Bugfix on 0.2.0.20-rc.
1902 Changes in version 0.2.0.20-rc - 2008-02-24
1903 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
1904 makes more progress towards normalizing Tor's TLS handshake, makes
1905 hidden services work better again, helps relays bootstrap if they don't
1906 know their IP address, adds optional support for linking in openbsd's
1907 allocator or tcmalloc, allows really fast relays to scale past 15000
1908 sockets, and fixes a bunch of minor bugs reported by Veracode.
1911 - Enable the revised TLS handshake based on the one designed by
1912 Steven Murdoch in proposal 124, as revised in proposal 130. It
1913 includes version negotiation for OR connections as described in
1914 proposal 105. The new handshake is meant to be harder for censors
1915 to fingerprint, and it adds the ability to detect certain kinds of
1916 man-in-the-middle traffic analysis attacks. The version negotiation
1917 feature will allow us to improve Tor's link protocol more safely
1919 - Choose which bridge to use proportional to its advertised bandwidth,
1920 rather than uniformly at random. This should speed up Tor for
1921 bridge users. Also do this for people who set StrictEntryNodes.
1922 - When a TrackHostExits-chosen exit fails too many times in a row,
1923 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
1926 - Resolved problems with (re-)fetching hidden service descriptors.
1927 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
1929 - If we only ever used Tor for hidden service lookups or posts, we
1930 would stop building circuits and start refusing connections after
1931 24 hours, since we falsely believed that Tor was dormant. Reported
1932 by nwf; bugfix on 0.1.2.x.
1933 - Servers that don't know their own IP address should go to the
1934 authorities for their first directory fetch, even if their DirPort
1935 is off or if they don't know they're reachable yet. This will help
1936 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
1937 - When counting the number of open sockets, count not only the number
1938 of sockets we have received from the socket() call, but also
1939 the number we've gotten from accept() and socketpair(). This bug
1940 made us fail to count all sockets that we were using for incoming
1941 connections. Bugfix on 0.2.0.x.
1942 - Fix code used to find strings within buffers, when those strings
1943 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
1944 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
1945 - Add a new __HashedControlSessionPassword option for controllers
1946 to use for one-off session password hashes that shouldn't get
1947 saved to disk by SAVECONF --- Vidalia users were accumulating a
1948 pile of HashedControlPassword lines in their torrc files, one for
1949 each time they had restarted Tor and then clicked Save. Make Tor
1950 automatically convert "HashedControlPassword" to this new option but
1951 only when it's given on the command line. Partial fix for bug 586.
1953 o Minor features (performance):
1954 - Tune parameters for cell pool allocation to minimize amount of
1956 - Add OpenBSD malloc code from phk as an optional malloc
1957 replacement on Linux: some glibc libraries do very poorly
1958 with Tor's memory allocation patterns. Pass
1959 --enable-openbsd-malloc to get the replacement malloc code.
1960 - Add a --with-tcmalloc option to the configure script to link
1961 against tcmalloc (if present). Does not yet search for
1962 non-system include paths.
1963 - Stop imposing an arbitrary maximum on the number of file descriptors
1964 used for busy servers. Bug reported by Olaf Selke; patch from
1967 o Minor features (other):
1968 - When SafeLogging is disabled, log addresses along with all TLS
1970 - When building with --enable-gcc-warnings, check for whether Apple's
1971 warning "-Wshorten-64-to-32" is available.
1972 - Add a --passphrase-fd argument to the tor-gencert command for
1975 o Minor bugfixes (memory leaks and code problems):
1976 - We were leaking a file descriptor if Tor started with a zero-length
1977 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
1978 - Detect size overflow in zlib code. Reported by Justin Ferguson and
1980 - We were comparing the raw BridgePassword entry with a base64'ed
1981 version of it, when handling a "/tor/networkstatus-bridges"
1982 directory request. Now compare correctly. Noticed by Veracode.
1983 - Recover from bad tracked-since value in MTBF-history file.
1985 - Alter the code that tries to recover from unhandled write
1986 errors, to not try to flush onto a socket that's given us
1987 unhandled errors. Bugfix on 0.1.2.x.
1988 - Make Unix controlsockets work correctly on OpenBSD. Patch from
1989 tup. Bugfix on 0.2.0.3-alpha.
1991 o Minor bugfixes (other):
1992 - If we have an extra-info document for our server, always make
1993 it available on the control port, even if we haven't gotten
1994 a copy of it from an authority yet. Patch from mwenge.
1995 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
1996 - Directory mirrors no longer include a guess at the client's IP
1997 address if the connection appears to be coming from the same /24
1998 network; it was producing too many wrong guesses.
1999 - Make the new hidden service code respect the SafeLogging setting.
2000 Bugfix on 0.2.0.x. Patch from Karsten.
2001 - When starting as an authority, do not overwrite all certificates
2002 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
2003 - If we're trying to flush the last bytes on a connection (for
2004 example, when answering a directory request), reset the
2005 time-to-give-up timeout every time we manage to write something
2006 on the socket. Bugfix on 0.1.2.x.
2007 - Change the behavior of "getinfo status/good-server-descriptor"
2008 so it doesn't return failure when any authority disappears.
2009 - Even though the man page said that "TrackHostExits ." should
2010 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
2011 - Report TLS "zero return" case as a "clean close" and "IO error"
2012 as a "close". Stop calling closes "unexpected closes": existing
2013 Tors don't use SSL_close(), so having a connection close without
2014 the TLS shutdown handshake is hardly unexpected.
2015 - Send NAMESERVER_STATUS messages for a single failed nameserver
2018 o Code simplifications and refactoring:
2019 - Remove the tor_strpartition function: its logic was confused,
2020 and it was only used for one thing that could be implemented far
2024 Changes in version 0.2.0.19-alpha - 2008-02-09
2025 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
2026 handshake, makes path selection for relays more secure and IP address
2027 guessing more robust, and generally fixes a lot of bugs in preparation
2028 for calling the 0.2.0 branch stable.
2031 - Do not include recognizeable strings in the commonname part of
2032 Tor's x509 certificates.
2035 - If we're a relay, avoid picking ourselves as an introduction point,
2036 a rendezvous point, or as the final hop for internal circuits. Bug
2037 reported by taranis and lodger. Bugfix on 0.1.2.x.
2038 - Patch from "Andrew S. Lists" to catch when we contact a directory
2039 mirror at IP address X and he says we look like we're coming from
2040 IP address X. Bugfix on 0.1.2.x.
2042 o Minor features (security):
2043 - Be more paranoid about overwriting sensitive memory on free(),
2044 as a defensive programming tactic to ensure forward secrecy.
2046 o Minor features (directory authority):
2047 - Actually validate the options passed to AuthDirReject,
2048 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
2049 - Reject router descriptors with out-of-range bandwidthcapacity or
2050 bandwidthburst values.
2052 o Minor features (controller):
2053 - Reject controller commands over 1MB in length. This keeps rogue
2054 processes from running us out of memory.
2056 o Minor features (misc):
2057 - Give more descriptive well-formedness errors for out-of-range
2058 hidden service descriptor/protocol versions.
2059 - Make memory debugging information describe more about history
2060 of cell allocation, so we can help reduce our memory use.
2062 o Deprecated features (controller):
2063 - The status/version/num-versioning and status/version/num-concurring
2064 GETINFO options are no longer useful in the v3 directory protocol:
2065 treat them as deprecated, and warn when they're used.
2068 - When our consensus networkstatus has been expired for a while, stop
2069 being willing to build circuits using it. Fixes bug 401. Bugfix
2071 - Directory caches now fetch certificates from all authorities
2072 listed in a networkstatus consensus, even when they do not
2073 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
2074 - When connecting to a bridge without specifying its key, insert
2075 the connection into the identity-to-connection map as soon as
2076 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
2077 - Detect versions of OS X where malloc_good_size() is present in the
2078 library but never actually declared. Resolves bug 587. Bugfix
2080 - Stop incorrectly truncating zlib responses to directory authority
2081 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
2082 - Stop recommending that every server operator send mail to tor-ops.
2083 Resolves bug 597. Bugfix on 0.1.2.x.
2084 - Don't trigger an assert if we start a directory authority with a
2085 private IP address (like 127.0.0.1).
2086 - Avoid possible failures when generating a directory with routers
2087 with over-long versions strings, or too many flags set. Bugfix
2089 - If an attempt to launch a DNS resolve request over the control
2090 port fails because we have overrun the limit on the number of
2091 connections, tell the controller that the request has failed.
2092 - Avoid using too little bandwidth when our clock skips a few
2093 seconds. Bugfix on 0.1.2.x.
2094 - Fix shell error when warning about missing packages in configure
2095 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
2096 - Do not become confused when receiving a spurious VERSIONS-like
2097 cell from a confused v1 client. Bugfix on 0.2.0.x.
2098 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
2099 introduction points for a hidden service have failed. Patch from
2100 Karsten Loesing. Bugfix on 0.2.0.x.
2102 o Code simplifications and refactoring:
2103 - Remove some needless generality from cpuworker code, for improved
2105 - Stop overloading the circuit_t.onionskin field for both "onionskin
2106 from a CREATE cell that we are waiting for a cpuworker to be
2107 assigned" and "onionskin from an EXTEND cell that we are going to
2108 send to an OR as soon as we are connected". Might help with bug 600.
2109 - Add an in-place version of aes_crypt() so that we can avoid doing a
2110 needless memcpy() call on each cell payload.
2113 Changes in version 0.2.0.18-alpha - 2008-01-25
2114 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
2115 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
2116 that can warn or reject connections to ports generally associated with
2117 vulnerable-plaintext protocols.
2119 o New directory authorities:
2120 - Set up dannenberg (run by CCC) as the sixth v3 directory
2124 - Fix a major memory leak when attempting to use the v2 TLS
2125 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
2126 - We accidentally enabled the under-development v2 TLS handshake
2127 code, which was causing log entries like "TLS error while
2128 renegotiating handshake". Disable it again. Resolves bug 590.
2129 - We were computing the wrong Content-Length: header for directory
2130 responses that need to be compressed on the fly, causing clients
2131 asking for those items to always fail. Bugfix on 0.2.0.x; partially
2135 - Avoid going directly to the directory authorities even if you're a
2136 relay, if you haven't found yourself reachable yet or if you've
2137 decided not to advertise your dirport yet. Addresses bug 556.
2138 - If we've gone 12 hours since our last bandwidth check, and we
2139 estimate we have less than 50KB bandwidth capacity but we could
2140 handle more, do another bandwidth test.
2141 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
2142 Tor can warn and/or refuse connections to ports commonly used with
2143 vulnerable-plaintext protocols. Currently we warn on ports 23,
2144 109, 110, and 143, but we don't reject any.
2147 - When we setconf ClientOnly to 1, close any current OR and Dir
2148 listeners. Reported by mwenge.
2149 - When we get a consensus that's been signed by more people than
2150 we expect, don't log about it; it's not a big deal. Reported
2154 - Don't answer "/tor/networkstatus-bridges" directory requests if
2155 the request isn't encrypted.
2156 - Make "ClientOnly 1" config option disable directory ports too.
2157 - Patches from Karsten Loesing to make v2 hidden services more
2158 robust: work even when there aren't enough HSDir relays available;
2159 retry when a v2 rend desc fetch fails; but don't retry if we
2160 already have a usable v0 rend desc.
2163 Changes in version 0.2.0.17-alpha - 2008-01-17
2164 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
2167 - Make the tor-gencert man page get included correctly in the tarball.
2170 Changes in version 0.2.0.16-alpha - 2008-01-17
2171 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
2172 Loesing, and generally cleans up a lot of features and minor bugs.
2174 o New directory authorities:
2175 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
2178 o Major performance improvements:
2179 - Switch our old ring buffer implementation for one more like that
2180 used by free Unix kernels. The wasted space in a buffer with 1mb
2181 of data will now be more like 8k than 1mb. The new implementation
2182 also avoids realloc();realloc(); patterns that can contribute to
2183 memory fragmentation.
2186 - Configuration files now accept C-style strings as values. This
2187 helps encode characters not allowed in the current configuration
2188 file format, such as newline or #. Addresses bug 557.
2189 - Although we fixed bug 539 (where servers would send HTTP status 503
2190 responses _and_ send a body too), there are still servers out
2191 there that haven't upgraded. Therefore, make clients parse such
2192 bodies when they receive them.
2193 - When we're not serving v2 directory information, there is no reason
2194 to actually keep any around. Remove the obsolete files and directory
2195 on startup if they are very old and we aren't going to serve them.
2197 o Minor performance improvements:
2198 - Reference-count and share copies of address policy entries; only 5%
2199 of them were actually distinct.
2200 - Never walk through the list of logs if we know that no log is
2201 interested in a given message.
2204 - When an authority has not signed a consensus, do not try to
2205 download a nonexistent "certificate with key 00000000". Bugfix
2206 on 0.2.0.x. Fixes bug 569.
2207 - Fix a rare assert error when we're closing one of our threads:
2208 use a mutex to protect the list of logs, so we never write to the
2209 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
2210 bug 575, which is kind of the revenge of bug 222.
2211 - Patch from Karsten Loesing to complain less at both the client
2212 and the relay when a relay used to have the HSDir flag but doesn't
2213 anymore, and we try to upload a hidden service descriptor.
2214 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
2216 - Do not try to download missing certificates until we have tried
2217 to check our fallback consensus. Fixes bug 583.
2218 - Make bridges round reported GeoIP stats info up to the nearest
2219 estimate, not down. Now we can distinguish between "0 people from
2220 this country" and "1 person from this country".
2221 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
2222 - Avoid possible segfault if key generation fails in
2223 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
2224 - Avoid segfault in the case where a badly behaved v2 versioning
2225 directory sends a signed networkstatus with missing client-versions.
2227 - Avoid segfaults on certain complex invocations of
2228 router_get_by_hexdigest(). Bugfix on 0.1.2.
2229 - Correct bad index on array access in parse_http_time(). Bugfix
2231 - Fix possible bug in vote generation when server versions are present
2232 but client versions are not.
2233 - Fix rare bug on REDIRECTSTREAM control command when called with no
2234 port set: it could erroneously report an error when none had
2236 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
2237 compressing large objects and find ourselves with more than 4k
2238 left over. Bugfix on 0.2.0.
2239 - Fix a small memory leak when setting up a hidden service.
2240 - Fix a few memory leaks that could in theory happen under bizarre
2242 - Fix an assert if we post a general-purpose descriptor via the
2243 control port but that descriptor isn't mentioned in our current
2244 network consensus. Bug reported by Jon McLachlan; bugfix on
2247 o Minor features (controller):
2248 - Get NS events working again. Patch from tup.
2249 - The GETCONF command now escapes and quotes configuration values
2250 that don't otherwise fit into the torrc file.
2251 - The SETCONF command now handles quoted values correctly.
2253 o Minor features (directory authorities):
2254 - New configuration options to override default maximum number of
2255 servers allowed on a single IP address. This is important for
2256 running a test network on a single host.
2257 - Actually implement the -s option to tor-gencert.
2258 - Add a manual page for tor-gencert.
2260 o Minor features (bridges):
2261 - Bridge authorities no longer serve bridge descriptors over
2262 unencrypted connections.
2264 o Minor features (other):
2265 - Add hidden services and DNSPorts to the list of things that make
2266 Tor accept that it has running ports. Change starting Tor with no
2267 ports from a fatal error to a warning; we might change it back if
2268 this turns out to confuse anybody. Fixes bug 579.
2271 Changes in version 0.1.2.19 - 2008-01-17
2272 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
2273 exit policy a little bit more conservative so it's safer to run an
2274 exit relay on a home system, and fixes a variety of smaller issues.
2277 - Exit policies now reject connections that are addressed to a
2278 relay's public (external) IP address too, unless
2279 ExitPolicyRejectPrivate is turned off. We do this because too
2280 many relays are running nearby to services that trust them based
2284 - When the clock jumps forward a lot, do not allow the bandwidth
2285 buckets to become negative. Fixes bug 544.
2286 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
2287 on every successful resolve. Reported by Mike Perry.
2288 - Purge old entries from the "rephist" database and the hidden
2289 service descriptor database even when DirPort is zero.
2290 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
2291 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
2292 crashing or mis-answering these requests.
2293 - When we decide to send a 503 response to a request for servers, do
2294 not then also send the server descriptors: this defeats the whole
2295 purpose. Fixes bug 539.
2298 - Changing the ExitPolicyRejectPrivate setting should cause us to
2299 rebuild our server descriptor.
2300 - Fix handling of hex nicknames when answering controller requests for
2301 networkstatus by name, or when deciding whether to warn about
2302 unknown routers in a config option. (Patch from mwenge.)
2303 - Fix a couple of hard-to-trigger autoconf problems that could result
2304 in really weird results on platforms whose sys/types.h files define
2305 nonstandard integer types.
2306 - Don't try to create the datadir when running --verify-config or
2307 --hash-password. Resolves bug 540.
2308 - If we were having problems getting a particular descriptor from the
2309 directory caches, and then we learned about a new descriptor for
2310 that router, we weren't resetting our failure count. Reported
2312 - Although we fixed bug 539 (where servers would send HTTP status 503
2313 responses _and_ send a body too), there are still servers out there
2314 that haven't upgraded. Therefore, make clients parse such bodies
2315 when they receive them.
2316 - Run correctly on systems where rlim_t is larger than unsigned long.
2317 This includes some 64-bit systems.
2318 - Run correctly on platforms (like some versions of OS X 10.5) where
2319 the real limit for number of open files is OPEN_FILES, not rlim_max
2320 from getrlimit(RLIMIT_NOFILES).
2321 - Avoid a spurious free on base64 failure.
2322 - Avoid segfaults on certain complex invocations of
2323 router_get_by_hexdigest().
2324 - Fix rare bug on REDIRECTSTREAM control command when called with no
2325 port set: it could erroneously report an error when none had
2329 Changes in version 0.2.0.15-alpha - 2007-12-25
2330 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
2331 features added in 0.2.0.13-alpha.
2334 - Fix several remotely triggerable asserts based on DirPort requests
2335 for a v2 or v3 networkstatus object before we were prepared. This
2336 was particularly bad for 0.2.0.13 and later bridge relays, who
2337 would never have a v2 networkstatus and would thus always crash
2338 when used. Bugfixes on 0.2.0.x.
2339 - Estimate the v3 networkstatus size more accurately, rather than
2340 estimating it at zero bytes and giving it artificially high priority
2341 compared to other directory requests. Bugfix on 0.2.0.x.
2344 - Fix configure.in logic for cross-compilation.
2345 - When we load a bridge descriptor from the cache, and it was
2346 previously unreachable, mark it as retriable so we won't just
2347 ignore it. Also, try fetching a new copy immediately. Bugfixes
2349 - The bridge GeoIP stats were counting other relays, for example
2350 self-reachability and authority-reachability tests.
2353 - Support compilation to target iPhone; patch from cjacker huang.
2354 To build for iPhone, pass the --enable-iphone option to configure.
2357 Changes in version 0.2.0.14-alpha - 2007-12-23
2359 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
2360 without a datadirectory from a previous Tor install. Reported
2362 - Fix a crash when we fetch a descriptor that turns out to be
2363 unexpected (it used to be in our networkstatus when we started
2364 fetching it, but it isn't in our current networkstatus), and we
2365 aren't using bridges. Bugfix on 0.2.0.x.
2366 - Fix a crash when accessing hidden services: it would work the first
2367 time you use a given introduction point for your service, but
2368 on subsequent requests we'd be using garbage memory. Fixed by
2369 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
2370 - Fix a crash when we load a bridge descriptor from disk but we don't
2371 currently have a Bridge line for it in our torrc. Bugfix on
2375 - If bridge authorities set BridgePassword, they will serve a
2376 snapshot of known bridge routerstatuses from their DirPort to
2377 anybody who knows that password. Unset by default.
2380 - Make the unit tests build again.
2381 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
2382 - Make PublishServerDescriptor default to 1, so the default doesn't
2383 have to change as we invent new directory protocol versions.
2384 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
2385 be included unless sys/time.h is already included. Fixes
2386 bug 553. Bugfix on 0.2.0.x.
2387 - If we receive a general-purpose descriptor and then receive an
2388 identical bridge-purpose descriptor soon after, don't discard
2389 the next one as a duplicate.
2392 - If BridgeRelay is set to 1, then the default for
2393 PublishServerDescriptor is now "bridge" rather than "v2,v3".
2394 - If the user sets RelayBandwidthRate but doesn't set
2395 RelayBandwidthBurst, then make them equal rather than erroring out.
2398 Changes in version 0.2.0.13-alpha - 2007-12-21
2399 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
2400 Goodell, fixes many more bugs, and adds a lot of infrastructure for
2403 o New directory authorities:
2404 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
2408 - Only update guard status (usable / not usable) once we have
2409 enough directory information. This was causing us to always pick
2410 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
2411 causing us to discard all our guards on startup if we hadn't been
2412 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
2413 - Purge old entries from the "rephist" database and the hidden
2414 service descriptor databases even when DirPort is zero. Bugfix
2416 - We were ignoring our RelayBandwidthRate for the first 30 seconds
2417 after opening a circuit -- even a relayed circuit. Bugfix on
2419 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
2420 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
2421 crashing or mis-answering these types of requests.
2422 - Relays were publishing their server descriptor to v1 and v2
2423 directory authorities, but they didn't try publishing to v3-only
2424 authorities. Fix this; and also stop publishing to v1 authorities.
2426 - When we were reading router descriptors from cache, we were ignoring
2427 the annotations -- so for example we were reading in bridge-purpose
2428 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
2429 - When we decided to send a 503 response to a request for servers, we
2430 were then also sending the server descriptors: this defeats the
2431 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
2434 - Bridge relays now behave like clients with respect to time
2435 intervals for downloading new consensus documents -- otherwise they
2436 stand out. Bridge users now wait until the end of the interval,
2437 so their bridge relay will be sure to have a new consensus document.
2438 - Three new config options (AlternateDirAuthority,
2439 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
2440 user selectively replace the default directory authorities by type,
2441 rather than the all-or-nothing replacement that DirServer offers.
2442 - Tor can now be configured to read a GeoIP file from disk in one
2443 of two formats. This can be used by controllers to map IP addresses
2444 to countries. Eventually, it may support exit-by-country.
2445 - When possible, bridge relays remember which countries users
2446 are coming from, and report aggregate information in their
2447 extra-info documents, so that the bridge authorities can learn
2448 where Tor is blocked.
2449 - Bridge directory authorities now do reachability testing on the
2450 bridges they know. They provide router status summaries to the
2451 controller via "getinfo ns/purpose/bridge", and also dump summaries
2452 to a file periodically.
2453 - Stop fetching directory info so aggressively if your DirPort is
2454 on but your ORPort is off; stop fetching v2 dir info entirely.
2455 You can override these choices with the new FetchDirInfoEarly
2459 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
2460 consensus documents when there are too many relays at a single
2461 IP address. Now clear it in v2 network status documents too, and
2462 also clear it in routerinfo_t when the relay is no longer listed
2463 in the relevant networkstatus document.
2464 - Don't crash if we get an unexpected value for the
2465 PublishServerDescriptor config option. Reported by Matt Edman;
2466 bugfix on 0.2.0.9-alpha.
2467 - Our new v2 hidden service descriptor format allows descriptors
2468 that have no introduction points. But Tor crashed when we tried
2469 to build a descriptor with no intro points (and it would have
2470 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
2472 - Fix building with dmalloc 5.5.2 with glibc.
2473 - Reject uploaded descriptors and extrainfo documents if they're
2474 huge. Otherwise we'll cache them all over the network and it'll
2475 clog everything up. Reported by Aljosha Judmayer.
2476 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
2477 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
2478 - When the DANGEROUS_VERSION controller status event told us we're
2479 running an obsolete version, it used the string "OLD" to describe
2480 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
2481 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
2482 - If we can't expand our list of entry guards (e.g. because we're
2483 using bridges or we have StrictEntryNodes set), don't mark relays
2484 down when they fail a directory request. Otherwise we're too quick
2485 to mark all our entry points down. Bugfix on 0.1.2.x.
2486 - Fix handling of hex nicknames when answering controller requests for
2487 networkstatus by name, or when deciding whether to warn about unknown
2488 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
2489 - Fix a couple of hard-to-trigger autoconf problems that could result
2490 in really weird results on platforms whose sys/types.h files define
2491 nonstandard integer types. Bugfix on 0.1.2.x.
2492 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
2493 - Don't crash on name lookup when we have no current consensus. Fixes
2494 bug 538; bugfix on 0.2.0.x.
2495 - Only Tors that want to mirror the v2 directory info should
2496 create the "cached-status" directory in their datadir. (All Tors
2497 used to create it.) Bugfix on 0.2.0.9-alpha.
2498 - Directory authorities should only automatically download Extra Info
2499 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
2502 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
2503 consumers. (We already do this on HUP.)
2504 - Authorities and caches fetch the v2 networkstatus documents
2505 less often, now that v3 is encouraged.
2506 - Add a new config option BridgeRelay that specifies you want to
2507 be a bridge relay. Right now the only difference is that it makes
2508 you answer begin_dir requests, and it makes you cache dir info,
2509 even if your DirPort isn't on.
2510 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
2511 ask about source, timestamp of arrival, purpose, etc. We need
2512 something like this to help Vidalia not do GeoIP lookups on bridge
2514 - Allow multiple HashedControlPassword config lines, to support
2515 multiple controller passwords.
2516 - Authorities now decide whether they're authoritative for a given
2517 router based on the router's purpose.
2518 - New config options AuthDirBadDir and AuthDirListBadDirs for
2519 authorities to mark certain relays as "bad directories" in the
2520 networkstatus documents. Also supports the "!baddir" directive in
2521 the approved-routers file.
2524 Changes in version 0.2.0.12-alpha - 2007-11-16
2525 This twelfth development snapshot fixes some more build problems as
2526 well as a few minor bugs.
2529 - Make it build on OpenBSD again. Patch from tup.
2530 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
2531 package-building for Red Hat, OS X, etc.
2533 o Minor bugfixes (on 0.1.2.x):
2534 - Changing the ExitPolicyRejectPrivate setting should cause us to
2535 rebuild our server descriptor.
2537 o Minor bugfixes (on 0.2.0.x):
2538 - When we're lacking a consensus, don't try to perform rendezvous
2539 operations. Reported by Karsten Loesing.
2540 - Fix a small memory leak whenever we decide against using a
2541 newly picked entry guard. Reported by Mike Perry.
2542 - When authorities detected more than two relays running on the same
2543 IP address, they were clearing all the status flags but forgetting
2544 to clear the "hsdir" flag. So clients were being told that a
2545 given relay was the right choice for a v2 hsdir lookup, yet they
2546 never had its descriptor because it was marked as 'not running'
2548 - If we're trying to fetch a bridge descriptor and there's no way
2549 the bridge authority could help us (for example, we don't know
2550 a digest, or there is no bridge authority), don't be so eager to
2551 fall back to asking the bridge authority.
2552 - If we're using bridges or have strictentrynodes set, and our
2553 chosen exit is in the same family as all our bridges/entry guards,
2554 then be flexible about families.
2557 - When we negotiate a v2 link-layer connection (not yet implemented),
2558 accept RELAY_EARLY cells and turn them into RELAY cells if we've
2559 negotiated a v1 connection for their next step. Initial code for
2563 Changes in version 0.2.0.11-alpha - 2007-11-12
2564 This eleventh development snapshot fixes some build problems with
2565 the previous snapshot. It also includes a more secure-by-default exit
2566 policy for relays, fixes an enormous memory leak for exit relays, and
2567 fixes another bug where servers were falling out of the directory list.
2570 - Exit policies now reject connections that are addressed to a
2571 relay's public (external) IP address too, unless
2572 ExitPolicyRejectPrivate is turned off. We do this because too
2573 many relays are running nearby to services that trust them based
2574 on network address. Bugfix on 0.1.2.x.
2577 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
2578 on every successful resolve. Reported by Mike Perry; bugfix
2580 - On authorities, never downgrade to old router descriptors simply
2581 because they're listed in the consensus. This created a catch-22
2582 where we wouldn't list a new descriptor because there was an
2583 old one in the consensus, and we couldn't get the new one in the
2584 consensus because we wouldn't list it. Possible fix for bug 548.
2585 Also, this might cause bug 543 to appear on authorities; if so,
2586 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
2588 o Packaging fixes on 0.2.0.10-alpha:
2589 - We were including instructions about what to do with the
2590 src/config/fallback-consensus file, but we weren't actually
2591 including it in the tarball. Disable all of that for now.
2594 - Allow people to say PreferTunnelledDirConns rather than
2595 PreferTunneledDirConns, for those alternate-spellers out there.
2598 - Don't reevaluate all the information from our consensus document
2599 just because we've downloaded a v2 networkstatus that we intend
2600 to cache. Fixes bug 545; bugfix on 0.2.0.x.
2603 Changes in version 0.2.0.10-alpha - 2007-11-10
2604 This tenth development snapshot adds a third v3 directory authority
2605 run by Mike Perry, adds most of Karsten Loesing's new hidden service
2606 descriptor format, fixes a bad crash bug and new bridge bugs introduced
2607 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
2608 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
2609 addresses many more minor issues.
2611 o New directory authorities:
2612 - Set up ides (run by Mike Perry) as the third v3 directory authority.
2615 - Allow tunnelled directory connections to ask for an encrypted
2616 "begin_dir" connection or an anonymized "uses a full Tor circuit"
2617 connection independently. Now we can make anonymized begin_dir
2618 connections for (e.g.) more secure hidden service posting and
2620 - More progress on proposal 114: code from Karsten Loesing to
2621 implement new hidden service descriptor format.
2622 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
2623 accommodate the growing number of servers that use the default
2624 and are reaching it.
2625 - Directory authorities use a new formula for selecting which nodes
2626 to advertise as Guards: they must be in the top 7/8 in terms of
2627 how long we have known about them, and above the median of those
2628 nodes in terms of weighted fractional uptime.
2629 - Make "not enough dir info yet" warnings describe *why* Tor feels
2630 it doesn't have enough directory info yet.
2633 - Stop servers from crashing if they set a Family option (or
2634 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
2636 - Make bridge users work again -- the move to v3 directories in
2637 0.2.0.9-alpha had introduced a number of bugs that made bridges
2638 no longer work for clients.
2639 - When the clock jumps forward a lot, do not allow the bandwidth
2640 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
2642 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
2643 - When the consensus lists a router descriptor that we previously were
2644 mirroring, but that we considered non-canonical, reload the
2645 descriptor as canonical. This fixes bug 543 where Tor servers
2646 would start complaining after a few days that they don't have
2647 enough directory information to build a circuit.
2648 - Consider replacing the current consensus when certificates arrive
2649 that make the pending consensus valid. Previously, we were only
2650 considering replacement when the new certs _didn't_ help.
2651 - Fix an assert error on startup if we didn't already have the
2652 consensus and certs cached in our datadirectory: we were caching
2653 the consensus in consensus_waiting_for_certs but then free'ing it
2655 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
2656 Request) if we need more v3 certs but we've already got pending
2657 requests for all of them.
2658 - Correctly back off from failing certificate downloads. Fixes
2660 - Authorities don't vote on the Running flag if they have been running
2661 for less than 30 minutes themselves. Fixes bug 547, where a newly
2662 started authority would vote that everyone was down.
2665 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
2666 it, it had no AES, and it hasn't seen any security patches since
2670 - Clients now hold circuitless TLS connections open for 1.5 times
2671 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
2672 rebuild a new circuit over them within that timeframe. Previously,
2673 they held them open only for KeepalivePeriod (5 minutes).
2674 - Use "If-Modified-Since" to avoid retrieving consensus
2675 networkstatuses that we already have.
2676 - When we have no consensus, check FallbackNetworkstatusFile (defaults
2677 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
2678 we start knowing some directory caches.
2679 - When we receive a consensus from the future, warn about skew.
2680 - Improve skew reporting: try to give the user a better log message
2681 about how skewed they are, and how much this matters.
2682 - When we have a certificate for an authority, believe that
2683 certificate's claims about the authority's IP address.
2684 - New --quiet command-line option to suppress the default console log.
2685 Good in combination with --hash-password.
2686 - Authorities send back an X-Descriptor-Not-New header in response to
2687 an accepted-but-discarded descriptor upload. Partially implements
2689 - Make the log message for "tls error. breaking." more useful.
2690 - Better log messages about certificate downloads, to attempt to
2691 track down the second incarnation of bug 546.
2693 o Minor features (bridges):
2694 - If bridge users set UpdateBridgesFromAuthority, but the digest
2695 they ask for is a 404 from the bridge authority, they now fall
2696 back to trying the bridge directly.
2697 - Bridges now use begin_dir to publish their server descriptor to
2698 the bridge authority, even when they haven't set TunnelDirConns.
2700 o Minor features (controller):
2701 - When reporting clock skew, and we know that the clock is _at least
2702 as skewed_ as some value, but we don't know the actual value,
2703 report the value as a "minimum skew."
2706 - Update linux-tor-prio.sh script to allow QoS based on the uid of
2707 the Tor process. Patch from Marco Bonetti with tweaks from Mike
2711 - Refuse to start if both ORPort and UseBridges are set. Bugfix
2712 on 0.2.0.x, suggested by Matt Edman.
2713 - Don't stop fetching descriptors when FetchUselessDescriptors is
2714 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
2715 reported by tup and ioerror.
2716 - Better log message on vote from unknown authority.
2717 - Don't log "Launching 0 request for 0 router" message.
2719 o Minor bugfixes (memory leaks):
2720 - Stop leaking memory every time we parse a v3 certificate. Bugfix
2722 - Stop leaking memory every time we load a v3 certificate. Bugfix
2723 on 0.2.0.1-alpha. Fixes bug 536.
2724 - Stop leaking a cached networkstatus on exit. Bugfix on
2726 - Stop leaking voter information every time we free a consensus.
2727 Bugfix on 0.2.0.3-alpha.
2728 - Stop leaking signed data every time we check a voter signature.
2729 Bugfix on 0.2.0.3-alpha.
2730 - Stop leaking a signature every time we fail to parse a consensus or
2731 a vote. Bugfix on 0.2.0.3-alpha.
2732 - Stop leaking v2_download_status_map on shutdown. Bugfix on
2734 - Stop leaking conn->nickname every time we make a connection to a
2735 Tor relay without knowing its expected identity digest (e.g. when
2736 using bridges). Bugfix on 0.2.0.3-alpha.
2738 - Minor bugfixes (portability):
2739 - Run correctly on platforms where rlim_t is larger than unsigned
2740 long, and/or where the real limit for number of open files is
2741 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
2742 particular, these may be needed for OS X 10.5.
2745 Changes in version 0.1.2.18 - 2007-10-28
2746 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
2747 hidden service introduction that were causing huge delays, and a big
2748 bug that was causing some servers to disappear from the network status
2749 lists for a few hours each day.
2751 o Major bugfixes (crashes):
2752 - If a connection is shut down abruptly because of something that
2753 happened inside connection_flushed_some(), do not call
2754 connection_finished_flushing(). Should fix bug 451:
2755 "connection_stop_writing: Assertion conn->write_event failed"
2756 Bugfix on 0.1.2.7-alpha.
2757 - Fix possible segfaults in functions called from
2758 rend_process_relay_cell().
2760 o Major bugfixes (hidden services):
2761 - Hidden services were choosing introduction points uniquely by
2762 hexdigest, but when constructing the hidden service descriptor
2763 they merely wrote the (potentially ambiguous) nickname.
2764 - Clients now use the v2 intro format for hidden service
2765 connections: they specify their chosen rendezvous point by identity
2766 digest rather than by (potentially ambiguous) nickname. These
2767 changes could speed up hidden service connections dramatically.
2769 o Major bugfixes (other):
2770 - Stop publishing a new server descriptor just because we get a
2771 HUP signal. This led (in a roundabout way) to some servers getting
2772 dropped from the networkstatus lists for a few hours each day.
2773 - When looking for a circuit to cannibalize, consider family as well
2774 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
2775 circuit cannibalization).
2776 - When a router wasn't listed in a new networkstatus, we were leaving
2777 the flags for that router alone -- meaning it remained Named,
2778 Running, etc -- even though absence from the networkstatus means
2779 that it shouldn't be considered to exist at all anymore. Now we
2780 clear all the flags for routers that fall out of the networkstatus
2781 consensus. Fixes bug 529.
2784 - Don't try to access (or alter) the state file when running
2785 --list-fingerprint or --verify-config or --hash-password. Resolves
2787 - When generating information telling us how to extend to a given
2788 router, do not try to include the nickname if it is
2789 absent. Resolves bug 467.
2790 - Fix a user-triggerable segfault in expand_filename(). (There isn't
2791 a way to trigger this remotely.)
2792 - When sending a status event to the controller telling it that an
2793 OR address is reachable, set the port correctly. (Previously we
2794 were reporting the dir port.)
2795 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
2796 command. Bugfix on 0.1.2.17.
2797 - When loading bandwidth history, do not believe any information in
2798 the future. Fixes bug 434.
2799 - When loading entry guard information, do not believe any information
2801 - When we have our clock set far in the future and generate an
2802 onion key, then re-set our clock to be correct, we should not stop
2803 the onion key from getting rotated.
2804 - On some platforms, accept() can return a broken address. Detect
2805 this more quietly, and deal accordingly. Fixes bug 483.
2806 - It's not actually an error to find a non-pending entry in the DNS
2807 cache when canceling a pending resolve. Don't log unless stuff
2808 is fishy. Resolves bug 463.
2809 - Don't reset trusted dir server list when we set a configuration
2810 option. Patch from Robert Hogan.
2811 - Don't try to create the datadir when running --verify-config or
2812 --hash-password. Resolves bug 540.
2815 Changes in version 0.2.0.9-alpha - 2007-10-24
2816 This ninth development snapshot switches clients to the new v3 directory
2817 system; allows servers to be listed in the network status even when they
2818 have the same nickname as a registered server; and fixes many other
2819 bugs including a big one that was causing some servers to disappear
2820 from the network status lists for a few hours each day.
2822 o Major features (directory system):
2823 - Clients now download v3 consensus networkstatus documents instead
2824 of v2 networkstatus documents. Clients and caches now base their
2825 opinions about routers on these consensus documents. Clients only
2826 download router descriptors listed in the consensus.
2827 - Authorities now list servers who have the same nickname as
2828 a different named server, but list them with a new flag,
2829 "Unnamed". Now we can list servers that happen to pick the same
2830 nickname as a server that registered two years ago and then
2831 disappeared. Partially implements proposal 122.
2832 - If the consensus lists a router as "Unnamed", the name is assigned
2833 to a different router: do not identify the router by that name.
2834 Partially implements proposal 122.
2835 - Authorities can now come to a consensus on which method to use to
2836 compute the consensus. This gives us forward compatibility.
2839 - Stop publishing a new server descriptor just because we HUP or
2840 when we find our DirPort to be reachable but won't actually publish
2841 it. New descriptors without any real changes are dropped by the
2842 authorities, and can screw up our "publish every 18 hours" schedule.
2844 - When a router wasn't listed in a new networkstatus, we were leaving
2845 the flags for that router alone -- meaning it remained Named,
2846 Running, etc -- even though absence from the networkstatus means
2847 that it shouldn't be considered to exist at all anymore. Now we
2848 clear all the flags for routers that fall out of the networkstatus
2849 consensus. Fixes bug 529; bugfix on 0.1.2.x.
2850 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
2851 extrainfo documents and then discard them immediately for not
2852 matching the latest router. Bugfix on 0.2.0.1-alpha.
2854 o Minor features (v3 directory protocol):
2855 - Allow tor-gencert to generate a new certificate without replacing
2857 - Allow certificates to include an address.
2858 - When we change our directory-cache settings, reschedule all voting
2859 and download operations.
2860 - Reattempt certificate downloads immediately on failure, as long as
2861 we haven't failed a threshold number of times yet.
2862 - Delay retrying consensus downloads while we're downloading
2863 certificates to verify the one we just got. Also, count getting a
2864 consensus that we already have (or one that isn't valid) as a failure,
2865 and count failing to get the certificates after 20 minutes as a
2867 - Build circuits and download descriptors even if our consensus is a
2868 little expired. (This feature will go away once authorities are
2871 o Minor features (router descriptor cache):
2872 - If we find a cached-routers file that's been sitting around for more
2873 than 28 days unmodified, then most likely it's a leftover from
2874 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
2876 - When we (as a cache) download a descriptor because it was listed
2877 in a consensus, remember when the consensus was supposed to expire,
2878 and don't expire the descriptor until then.
2880 o Minor features (performance):
2881 - Call routerlist_remove_old_routers() much less often. This should
2882 speed startup, especially on directory caches.
2883 - Don't try to launch new descriptor downloads quite so often when we
2884 already have enough directory information to build circuits.
2885 - Base64 decoding was actually showing up on our profile when parsing
2886 the initial descriptor file; switch to an in-process all-at-once
2887 implementation that's about 3.5x times faster than calling out to
2890 o Minor features (compilation):
2891 - Detect non-ASCII platforms (if any still exist) and refuse to
2892 build there: some of our code assumes that 'A' is 65 and so on.
2894 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
2895 - Make the "next period" votes into "current period" votes immediately
2896 after publishing the consensus; avoid a heisenbug that made them
2897 stick around indefinitely.
2898 - When we discard a vote as a duplicate, do not report this as
2900 - Treat missing v3 keys or certificates as an error when running as a
2901 v3 directory authority.
2902 - When we're configured to be a v3 authority, but we're only listed
2903 as a non-v3 authority in our DirServer line for ourself, correct
2905 - If an authority doesn't have a qualified hostname, just put
2906 its address in the vote. This fixes the problem where we referred to
2907 "moria on moria:9031."
2908 - Distinguish between detached signatures for the wrong period, and
2909 detached signatures for a divergent vote.
2910 - Fix a small memory leak when computing a consensus.
2911 - When there's no concensus, we were forming a vote every 30
2912 minutes, but writing the "valid-after" line in our vote based
2913 on our configured V3AuthVotingInterval: so unless the intervals
2914 matched up, we immediately rejected our own vote because it didn't
2915 start at the voting interval that caused us to construct a vote.
2917 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
2918 - Delete unverified-consensus when the real consensus is set.
2919 - Consider retrying a consensus networkstatus fetch immediately
2920 after one fails: don't wait 60 seconds to notice.
2921 - When fetching a consensus as a cache, wait until a newer consensus
2922 should exist before trying to replace the current one.
2923 - Use a more forgiving schedule for retrying failed consensus
2924 downloads than for other types.
2926 o Minor bugfixes (other directory issues):
2927 - Correct the implementation of "download votes by digest." Bugfix on
2929 - Authorities no longer send back "400 you're unreachable please fix
2930 it" errors to Tor servers that aren't online all the time. We're
2931 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
2933 o Minor bugfixes (controller):
2934 - Don't reset trusted dir server list when we set a configuration
2935 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
2936 - Respond to INT and TERM SIGNAL commands before we execute the
2937 signal, in case the signal shuts us down. We had a patch in
2938 0.1.2.1-alpha that tried to do this by queueing the response on
2939 the connection's buffer before shutting down, but that really
2940 isn't the same thing at all. Bug located by Matt Edman.
2942 o Minor bugfixes (misc):
2943 - Correctly check for bad options to the "PublishServerDescriptor"
2944 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
2945 - Stop leaking memory on failing case of base32_decode, and make
2946 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
2947 - Don't try to download extrainfo documents when we're trying to
2948 fetch enough directory info to build a circuit: having enough
2949 info should get priority. Bugfix on 0.2.0.x.
2950 - Don't complain that "your server has not managed to confirm that its
2951 ports are reachable" if we haven't been able to build any circuits
2952 yet. Bug found by spending four hours without a v3 consensus. Bugfix
2954 - Detect the reason for failing to mmap a descriptor file we just
2955 wrote, and give a more useful log message. Fixes bug 533. Bugfix
2958 o Code simplifications and refactoring:
2959 - Remove support for the old bw_accounting file: we've been storing
2960 bandwidth accounting information in the state file since
2961 0.1.2.5-alpha. This may result in bandwidth accounting errors
2962 if you try to upgrade from 0.1.1.x or earlier, or if you try to
2963 downgrade to 0.1.1.x or earlier.
2964 - New convenience code to locate a file within the DataDirectory.
2965 - Move non-authority functionality out of dirvote.c.
2966 - Refactor the arguments for router_pick_{directory_|trusteddir}server
2967 so that they all take the same named flags.
2970 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
2971 Unix users an easy way to script their Tor process (e.g. by
2972 adjusting bandwidth based on the time of the day).
2975 Changes in version 0.2.0.8-alpha - 2007-10-12
2976 This eighth development snapshot fixes a crash bug that's been bothering
2977 us since February 2007, lets bridge authorities store a list of bridge
2978 descriptors they've seen, gets v3 directory voting closer to working,
2979 starts caching v3 directory consensus documents on directory mirrors,
2980 and fixes a variety of smaller issues including some minor memory leaks.
2982 o Major features (router descriptor cache):
2983 - Store routers in a file called cached-descriptors instead of in
2984 cached-routers. Initialize cached-descriptors from cached-routers
2985 if the old format is around. The new format allows us to store
2986 annotations along with descriptors.
2987 - Use annotations to record the time we received each descriptor, its
2988 source, and its purpose.
2989 - Disable the SETROUTERPURPOSE controller command: it is now
2991 - Controllers should now specify cache=no or cache=yes when using
2992 the +POSTDESCRIPTOR command.
2993 - Bridge authorities now write bridge descriptors to disk, meaning
2994 we can export them to other programs and begin distributing them
2997 o Major features (directory authorities):
2998 - When a v3 authority is missing votes or signatures, it now tries
3000 - Directory authorities track weighted fractional uptime as well as
3001 weighted mean-time-between failures. WFU is suitable for deciding
3002 whether a node is "usually up", while MTBF is suitable for deciding
3003 whether a node is "likely to stay up." We need both, because
3004 "usually up" is a good requirement for guards, while "likely to
3005 stay up" is a good requirement for long-lived connections.
3007 o Major features (v3 directory system):
3008 - Caches now download v3 network status documents as needed,
3009 and download the descriptors listed in them.
3010 - All hosts now attempt to download and keep fresh v3 authority
3011 certificates, and re-attempt after failures.
3012 - More internal-consistency checks for vote parsing.
3014 o Major bugfixes (crashes):
3015 - If a connection is shut down abruptly because of something that
3016 happened inside connection_flushed_some(), do not call
3017 connection_finished_flushing(). Should fix bug 451. Bugfix on
3020 o Major bugfixes (performance):
3021 - Fix really bad O(n^2) performance when parsing a long list of
3022 routers: Instead of searching the entire list for an "extra-info "
3023 string which usually wasn't there, once for every routerinfo
3024 we read, just scan lines forward until we find one we like.
3026 - When we add data to a write buffer in response to the data on that
3027 write buffer getting low because of a flush, do not consider the
3028 newly added data as a candidate for immediate flushing, but rather
3029 make it wait until the next round of writing. Otherwise, we flush
3030 and refill recursively, and a single greedy TLS connection can
3031 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
3033 o Minor features (v3 authority system):
3034 - Add more ways for tools to download the votes that lead to the
3036 - Send a 503 when low on bandwidth and a vote, consensus, or
3037 certificate is requested.
3038 - If-modified-since is now implemented properly for all kinds of
3039 certificate requests.
3041 o Minor bugfixes (network statuses):
3042 - Tweak the implementation of proposal 109 slightly: allow at most
3043 two Tor servers on the same IP address, except if it's the location
3044 of a directory authority, in which case allow five. Bugfix on
3047 o Minor bugfixes (controller):
3048 - When sending a status event to the controller telling it that an
3049 OR address is reachable, set the port correctly. (Previously we
3050 were reporting the dir port.) Bugfix on 0.1.2.x.
3052 o Minor bugfixes (v3 directory system):
3053 - Fix logic to look up a cert by its signing key digest. Bugfix on
3055 - Only change the reply to a vote to "OK" if it's not already
3056 set. This gets rid of annoying "400 OK" log messages, which may
3057 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
3058 - When we get a valid consensus, recompute the voting schedule.
3059 - Base the valid-after time of a vote on the consensus voting
3060 schedule, not on our preferred schedule.
3061 - Make the return values and messages from signature uploads and
3062 downloads more sensible.
3063 - Fix a memory leak when serving votes and consensus documents, and
3064 another when serving certificates.
3066 o Minor bugfixes (performance):
3067 - Use a slightly simpler string hashing algorithm (copying Python's
3068 instead of Java's) and optimize our digest hashing algorithm to take
3069 advantage of 64-bit platforms and to remove some possibly-costly
3071 - Fix a minor memory leak whenever we parse guards from our state
3072 file. Bugfix on 0.2.0.7-alpha.
3073 - Fix a minor memory leak whenever we write out a file. Bugfix on
3075 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
3076 command. Bugfix on 0.2.0.5-alpha.
3078 o Minor bugfixes (portability):
3079 - On some platforms, accept() can return a broken address. Detect
3080 this more quietly, and deal accordingly. Fixes bug 483.
3081 - Stop calling tor_strlower() on uninitialized memory in some cases.
3082 Bugfix in 0.2.0.7-alpha.
3084 o Minor bugfixes (usability):
3085 - Treat some 403 responses from directory servers as INFO rather than
3086 WARN-severity events.
3087 - It's not actually an error to find a non-pending entry in the DNS
3088 cache when canceling a pending resolve. Don't log unless stuff is
3089 fishy. Resolves bug 463.
3091 o Minor bugfixes (anonymity):
3092 - Never report that we've used more bandwidth than we're willing to
3093 relay: it leaks how much non-relay traffic we're using. Resolves
3095 - When looking for a circuit to cannibalize, consider family as well
3096 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
3097 circuit cannibalization).
3099 o Code simplifications and refactoring:
3100 - Make a bunch of functions static. Remove some dead code.
3101 - Pull out about a third of the really big routerlist.c; put it in a
3102 new module, networkstatus.c.
3103 - Merge the extra fields in local_routerstatus_t back into
3104 routerstatus_t: we used to need one routerstatus_t for each
3105 authority's opinion, plus a local_routerstatus_t for the locally
3106 computed consensus opinion. To save space, we put the locally
3107 modified fields into local_routerstatus_t, and only the common
3108 stuff into routerstatus_t. But once v3 directories are in use,
3109 clients and caches will no longer need to hold authority opinions;
3110 thus, the rationale for keeping the types separate is now gone.
3111 - Make the code used to reschedule and reattempt downloads more
3113 - Turn all 'Are we a directory server/mirror?' logic into a call to
3115 - Remove the code to generate the oldest (v1) directory format.
3116 The code has been disabled since 0.2.0.5-alpha.
3119 Changes in version 0.2.0.7-alpha - 2007-09-21
3120 This seventh development snapshot makes bridges work again, makes bridge
3121 authorities work for the first time, fixes two huge performance flaws
3122 in hidden services, and fixes a variety of minor issues.
3124 o New directory authorities:
3125 - Set up moria1 and tor26 as the first v3 directory authorities. See
3126 doc/spec/dir-spec.txt for details on the new directory design.
3128 o Major bugfixes (crashes):
3129 - Fix possible segfaults in functions called from
3130 rend_process_relay_cell(). Bugfix on 0.1.2.x.
3132 o Major bugfixes (bridges):
3133 - Fix a bug that made servers send a "404 Not found" in response to
3134 attempts to fetch their server descriptor. This caused Tor servers
3135 to take many minutes to establish reachability for their DirPort,
3136 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
3137 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
3138 users configure that and specify a bridge with an identity
3139 fingerprint, now they will lookup the bridge descriptor at the
3140 default bridge authority via a one-hop tunnel, but once circuits
3141 are established they will switch to a three-hop tunnel for later
3142 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
3144 o Major bugfixes (hidden services):
3145 - Hidden services were choosing introduction points uniquely by
3146 hexdigest, but when constructing the hidden service descriptor
3147 they merely wrote the (potentially ambiguous) nickname.
3148 - Clients now use the v2 intro format for hidden service
3149 connections: they specify their chosen rendezvous point by identity
3150 digest rather than by (potentially ambiguous) nickname. Both
3151 are bugfixes on 0.1.2.x, and they could speed up hidden service
3152 connections dramatically. Thanks to Karsten Loesing.
3154 o Minor features (security):
3155 - As a client, do not believe any server that tells us that an
3156 address maps to an internal address space.
3157 - Make it possible to enable HashedControlPassword and
3158 CookieAuthentication at the same time.
3160 o Minor features (guard nodes):
3161 - Tag every guard node in our state file with the version that
3162 we believe added it, or with our own version if we add it. This way,
3163 if a user temporarily runs an old version of Tor and then switches
3164 back to a new one, she doesn't automatically lose her guards.
3166 o Minor features (speed):
3167 - When implementing AES counter mode, update only the portions of the
3168 counter buffer that need to change, and don't keep separate
3169 network-order and host-order counters when they are the same (i.e.,
3170 on big-endian hosts.)
3172 o Minor features (controller):
3173 - Accept LF instead of CRLF on controller, since some software has a
3174 hard time generating real Internet newlines.
3175 - Add GETINFO values for the server status events
3176 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
3180 - Routers no longer include bandwidth-history lines in their
3181 descriptors; this information is already available in extra-info
3182 documents, and including it in router descriptors took up 60%
3183 (!) of compressed router descriptor downloads. Completes
3184 implementation of proposal 104.
3185 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
3186 and TorControl.py, as they use the old v0 controller protocol,
3187 and are obsoleted by TorFlow anyway.
3188 - Drop support for v1 rendezvous descriptors, since we never used
3189 them anyway, and the code has probably rotted by now. Based on
3190 patch from Karsten Loesing.
3191 - On OSX, stop warning the user that kqueue support in libevent is
3192 "experimental", since it seems to have worked fine for ages.
3195 - When generating information telling us how to extend to a given
3196 router, do not try to include the nickname if it is absent. Fixes
3197 bug 467. Bugfix on 0.2.0.3-alpha.
3198 - Fix a user-triggerable (but not remotely-triggerable) segfault
3199 in expand_filename(). Bugfix on 0.1.2.x.
3200 - Fix a memory leak when freeing incomplete requests from DNSPort.
3201 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
3202 - Don't try to access (or alter) the state file when running
3203 --list-fingerprint or --verify-config or --hash-password. (Resolves
3204 bug 499.) Bugfix on 0.1.2.x.
3205 - Servers used to decline to publish their DirPort if their
3206 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
3207 were below a threshold. Now they only look at BandwidthRate and
3208 RelayBandwidthRate. Bugfix on 0.1.2.x.
3209 - Remove an optimization in the AES counter-mode code that assumed
3210 that the counter never exceeded 2^68. When the counter can be set
3211 arbitrarily as an IV (as it is by Karsten's new hidden services
3212 code), this assumption no longer holds. Bugfix on 0.1.2.x.
3213 - Resume listing "AUTHORITY" flag for authorities in network status.
3214 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
3216 o Code simplifications and refactoring:
3217 - Revamp file-writing logic so we don't need to have the entire
3218 contents of a file in memory at once before we write to disk. Tor,
3220 - Turn "descriptor store" into a full-fledged type.
3221 - Move all NT services code into a separate source file.
3222 - Unify all code that computes medians, percentile elements, etc.
3223 - Get rid of a needless malloc when parsing address policies.
3226 Changes in version 0.1.2.17 - 2007-08-30
3227 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
3228 X bundles. Vidalia 0.0.14 makes authentication required for the
3229 ControlPort in the default configuration, which addresses important
3230 security risks. Everybody who uses Vidalia (or another controller)
3233 In addition, this Tor update fixes major load balancing problems with
3234 path selection, which should speed things up a lot once many people
3237 o Major bugfixes (security):
3238 - We removed support for the old (v0) control protocol. It has been
3239 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
3240 become more of a headache than it's worth.
3242 o Major bugfixes (load balancing):
3243 - When choosing nodes for non-guard positions, weight guards
3244 proportionally less, since they already have enough load. Patch
3246 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
3247 will allow fast Tor servers to get more attention.
3248 - When we're upgrading from an old Tor version, forget our current
3249 guards and pick new ones according to the new weightings. These
3250 three load balancing patches could raise effective network capacity
3251 by a factor of four. Thanks to Mike Perry for measurements.
3253 o Major bugfixes (stream expiration):
3254 - Expire not-yet-successful application streams in all cases if
3255 they've been around longer than SocksTimeout. Right now there are
3256 some cases where the stream will live forever, demanding a new
3257 circuit every 15 seconds. Fixes bug 454; reported by lodger.
3259 o Minor features (controller):
3260 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
3261 is valid before any authentication has been received. It tells
3262 a controller what kind of authentication is expected, and what
3263 protocol is spoken. Implements proposal 119.
3265 o Minor bugfixes (performance):
3266 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
3267 greatly speeding up loading cached-routers from disk on startup.
3268 - Disable sentinel-based debugging for buffer code: we squashed all
3269 the bugs that this was supposed to detect a long time ago, and now
3270 its only effect is to change our buffer sizes from nice powers of
3271 two (which platform mallocs tend to like) to values slightly over
3272 powers of two (which make some platform mallocs sad).
3274 o Minor bugfixes (misc):
3275 - If exit bandwidth ever exceeds one third of total bandwidth, then
3276 use the correct formula to weight exit nodes when choosing paths.
3277 Based on patch from Mike Perry.
3278 - Choose perfectly fairly among routers when choosing by bandwidth and
3279 weighting by fraction of bandwidth provided by exits. Previously, we
3280 would choose with only approximate fairness, and correct ourselves
3281 if we ran off the end of the list.
3282 - If we require CookieAuthentication but we fail to write the
3283 cookie file, we would warn but not exit, and end up in a state
3284 where no controller could authenticate. Now we exit.
3285 - If we require CookieAuthentication, stop generating a new cookie
3286 every time we change any piece of our config.
3287 - Refuse to start with certain directory authority keys, and
3288 encourage people using them to stop.
3289 - Terminate multi-line control events properly. Original patch
3291 - Fix a minor memory leak when we fail to find enough suitable
3292 servers to choose a circuit.
3293 - Stop leaking part of the descriptor when we run into a particularly
3294 unparseable piece of it.
3297 Changes in version 0.2.0.6-alpha - 2007-08-26
3298 This sixth development snapshot features a new Vidalia version in the
3299 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
3300 the ControlPort in the default configuration, which addresses important
3303 In addition, this snapshot fixes major load balancing problems
3304 with path selection, which should speed things up a lot once many
3305 people have upgraded. The directory authorities also use a new
3306 mean-time-between-failure approach to tracking which servers are stable,
3307 rather than just looking at the most recent uptime.
3309 o New directory authorities:
3310 - Set up Tonga as the default bridge directory authority.
3313 - Directory authorities now track servers by weighted
3314 mean-times-between-failures. When we have 4 or more days of data,
3315 use measured MTBF rather than declared uptime to decide whether
3316 to call a router Stable. Implements proposal 108.
3318 o Major bugfixes (load balancing):
3319 - When choosing nodes for non-guard positions, weight guards
3320 proportionally less, since they already have enough load. Patch
3322 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
3323 will allow fast Tor servers to get more attention.
3324 - When we're upgrading from an old Tor version, forget our current
3325 guards and pick new ones according to the new weightings. These
3326 three load balancing patches could raise effective network capacity
3327 by a factor of four. Thanks to Mike Perry for measurements.
3329 o Major bugfixes (descriptor parsing):
3330 - Handle unexpected whitespace better in malformed descriptors. Bug
3331 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
3334 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
3335 GETINFO for Torstat to use until it can switch to using extrainfos.
3336 - Optionally (if built with -DEXPORTMALLINFO) export the output
3337 of mallinfo via http, as tor/mallinfo.txt. Only accessible
3341 - Do not intermix bridge routers with controller-added
3342 routers. (Bugfix on 0.2.0.x)
3343 - Do not fail with an assert when accept() returns an unexpected
3344 address family. Addresses but does not wholly fix bug 483. (Bugfix
3346 - Let directory authorities startup even when they can't generate
3347 a descriptor immediately, e.g. because they don't know their
3349 - Stop putting the authentication cookie in a file called "0"
3350 in your working directory if you don't specify anything for the
3351 new CookieAuthFile option. Reported by Matt Edman.
3352 - Make it possible to read the PROTOCOLINFO response in a way that
3353 conforms to our control-spec. Reported by Matt Edman.
3354 - Fix a minor memory leak when we fail to find enough suitable
3355 servers to choose a circuit. Bugfix on 0.1.2.x.
3356 - Stop leaking part of the descriptor when we run into a particularly
3357 unparseable piece of it. Bugfix on 0.1.2.x.
3358 - Unmap the extrainfo cache file on exit.
3361 Changes in version 0.2.0.5-alpha - 2007-08-19
3362 This fifth development snapshot fixes compilation on Windows again;
3363 fixes an obnoxious client-side bug that slowed things down and put
3364 extra load on the network; gets us closer to using the v3 directory
3365 voting scheme; makes it easier for Tor controllers to use cookie-based
3366 authentication; and fixes a variety of other bugs.
3369 - Version 1 directories are no longer generated in full. Instead,
3370 authorities generate and serve "stub" v1 directories that list
3371 no servers. This will stop Tor versions 0.1.0.x and earlier from
3372 working, but (for security reasons) nobody should be running those
3375 o Major bugfixes (compilation, 0.2.0.x):
3376 - Try to fix Win32 compilation again: improve checking for IPv6 types.
3377 - Try to fix MSVC compilation: build correctly on platforms that do
3378 not define s6_addr16 or s6_addr32.
3379 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
3382 o Major bugfixes (stream expiration):
3383 - Expire not-yet-successful application streams in all cases if
3384 they've been around longer than SocksTimeout. Right now there are
3385 some cases where the stream will live forever, demanding a new
3386 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
3389 o Minor features (directory servers):
3390 - When somebody requests a list of statuses or servers, and we have
3391 none of those, return a 404 rather than an empty 200.
3393 o Minor features (directory voting):
3394 - Store v3 consensus status consensuses on disk, and reload them
3397 o Minor features (security):
3398 - Warn about unsafe ControlPort configurations.
3399 - Refuse to start with certain directory authority keys, and
3400 encourage people using them to stop.
3402 o Minor features (controller):
3403 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
3404 is valid before any authentication has been received. It tells
3405 a controller what kind of authentication is expected, and what
3406 protocol is spoken. Implements proposal 119.
3407 - New config option CookieAuthFile to choose a new location for the
3408 cookie authentication file, and config option
3409 CookieAuthFileGroupReadable to make it group-readable.
3411 o Minor features (unit testing):
3412 - Add command-line arguments to unit-test executable so that we can
3413 invoke any chosen test from the command line rather than having
3414 to run the whole test suite at once; and so that we can turn on
3415 logging for the unit tests.
3417 o Minor bugfixes (on 0.1.2.x):
3418 - If we require CookieAuthentication but we fail to write the
3419 cookie file, we would warn but not exit, and end up in a state
3420 where no controller could authenticate. Now we exit.
3421 - If we require CookieAuthentication, stop generating a new cookie
3422 every time we change any piece of our config.
3423 - When loading bandwidth history, do not believe any information in
3424 the future. Fixes bug 434.
3425 - When loading entry guard information, do not believe any information
3427 - When we have our clock set far in the future and generate an
3428 onion key, then re-set our clock to be correct, we should not stop
3429 the onion key from getting rotated.
3430 - Clean up torrc sample config file.
3431 - Do not automatically run configure from autogen.sh. This
3432 non-standard behavior tended to annoy people who have built other
3435 o Minor bugfixes (on 0.2.0.x):
3436 - Fix a bug with AutomapHostsOnResolve that would always cause
3437 the second request to fail. Bug reported by Kate. Bugfix on
3439 - Fix a bug in ADDRMAP controller replies that would sometimes
3440 try to print a NULL. Patch from tup.
3441 - Read v3 directory authority keys from the right location.
3442 - Numerous bugfixes to directory voting code.
3445 Changes in version 0.1.2.16 - 2007-08-01
3446 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
3447 remote attacker in certain situations to rewrite the user's torrc
3448 configuration file. This can completely compromise anonymity of users
3449 in most configurations, including those running the Vidalia bundles,
3450 TorK, etc. Or worse.
3452 o Major security fixes:
3453 - Close immediately after missing authentication on control port;
3454 do not allow multiple authentication attempts.
3457 Changes in version 0.2.0.4-alpha - 2007-08-01
3458 This fourth development snapshot fixes a critical security vulnerability
3459 for most users, specifically those running Vidalia, TorK, etc. Everybody
3460 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
3462 o Major security fixes:
3463 - Close immediately after missing authentication on control port;
3464 do not allow multiple authentication attempts.
3466 o Major bugfixes (compilation):
3467 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
3470 o Minor features (performance):
3471 - Be even more aggressive about releasing RAM from small
3472 empty buffers. Thanks to our free-list code, this shouldn't be too
3473 performance-intensive.
3474 - Disable sentinel-based debugging for buffer code: we squashed all
3475 the bugs that this was supposed to detect a long time ago, and
3476 now its only effect is to change our buffer sizes from nice
3477 powers of two (which platform mallocs tend to like) to values
3478 slightly over powers of two (which make some platform mallocs sad).
3479 - Log malloc statistics from mallinfo() on platforms where it
3483 Changes in version 0.2.0.3-alpha - 2007-07-29
3484 This third development snapshot introduces new experimental
3485 blocking-resistance features and a preliminary version of the v3
3486 directory voting design, and includes many other smaller features
3490 - The first pieces of our "bridge" design for blocking-resistance
3491 are implemented. People can run bridge directory authorities;
3492 people can run bridges; and people can configure their Tor clients
3493 with a set of bridges to use as the first hop into the Tor network.
3494 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
3496 - Create listener connections before we setuid to the configured
3497 User and Group. Now non-Windows users can choose port values
3498 under 1024, start Tor as root, and have Tor bind those ports
3499 before it changes to another UID. (Windows users could already
3501 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
3502 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
3503 on "vserver" accounts. (Patch from coderman.)
3504 - Be even more aggressive about separating local traffic from relayed
3505 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
3507 o Major features (experimental):
3508 - First cut of code for "v3 dir voting": directory authorities will
3509 vote on a common network status document rather than each publishing
3510 their own opinion. This code needs more testing and more corner-case
3511 handling before it's ready for use.
3514 - Directory authorities now call routers Fast if their bandwidth is
3515 at least 100KB/s, and consider their bandwidth adequate to be a
3516 Guard if it is at least 250KB/s, no matter the medians. This fix
3517 complements proposal 107. [Bugfix on 0.1.2.x]
3518 - Directory authorities now never mark more than 3 servers per IP as
3519 Valid and Running. (Implements proposal 109, by Kevin Bauer and
3521 - Minor change to organizationName and commonName generation
3522 procedures in TLS certificates during Tor handshakes, to invalidate
3523 some earlier censorware approaches. This is not a long-term
3524 solution, but applying it will give us a bit of time to look into
3525 the epidemiology of countermeasures as they spread.
3527 o Major bugfixes (directory):
3528 - Rewrite directory tokenization code to never run off the end of
3529 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
3531 o Minor features (controller):
3532 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
3533 match requests to applications. (Patch from Robert Hogan.)
3534 - Report address and port correctly on connections to DNSPort. (Patch
3536 - Add a RESOLVE command to launch hostname lookups. (Original patch
3538 - Add GETINFO status/enough-dir-info to let controllers tell whether
3539 Tor has downloaded sufficient directory information. (Patch
3541 - You can now use the ControlSocket option to tell Tor to listen for
3542 controller connections on Unix domain sockets on systems that
3543 support them. (Patch from Peter Palfrader.)
3544 - STREAM NEW events are generated for DNSPort requests and for
3545 tunneled directory connections. (Patch from Robert Hogan.)
3546 - New "GETINFO address-mappings/*" command to get address mappings
3547 with expiry information. "addr-mappings/*" is now deprecated.
3550 o Minor features (misc):
3551 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
3553 - The tor-gencert tool for v3 directory authorities now creates all
3554 files as readable to the file creator only, and write-protects
3555 the authority identity key.
3556 - When dumping memory usage, list bytes used in buffer memory
3558 - When running with dmalloc, dump more stats on hup and on exit.
3559 - Directory authorities now fail quickly and (relatively) harmlessly
3560 if they generate a network status document that is somehow
3563 o Traffic load balancing improvements:
3564 - If exit bandwidth ever exceeds one third of total bandwidth, then
3565 use the correct formula to weight exit nodes when choosing paths.
3566 (Based on patch from Mike Perry.)
3567 - Choose perfectly fairly among routers when choosing by bandwidth and
3568 weighting by fraction of bandwidth provided by exits. Previously, we
3569 would choose with only approximate fairness, and correct ourselves
3570 if we ran off the end of the list. [Bugfix on 0.1.2.x]
3572 o Performance improvements:
3573 - Be more aggressive with freeing buffer RAM or putting it on the
3575 - Use Critical Sections rather than Mutexes for synchronizing threads
3576 on win32; Mutexes are heavier-weight, and designed for synchronizing
3579 o Deprecated and removed features:
3580 - RedirectExits is now deprecated.
3581 - Stop allowing address masks that do not correspond to bit prefixes.
3582 We have warned about these for a really long time; now it's time
3583 to reject them. (Patch from croup.)
3585 o Minor bugfixes (directory):
3586 - Fix another crash bug related to extra-info caching. (Bug found by
3587 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
3588 - Directories no longer return a "304 not modified" when they don't
3589 have the networkstatus the client asked for. Also fix a memory
3590 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
3591 - We had accidentally labelled 0.1.2.x directory servers as not
3592 suitable for begin_dir requests, and had labelled no directory
3593 servers as suitable for uploading extra-info documents. [Bugfix
3596 o Minor bugfixes (dns):
3597 - Fix a crash when DNSPort is set more than once. (Patch from Robert
3598 Hogan.) [Bugfix on 0.2.0.2-alpha]
3599 - Add DNSPort connections to the global connection list, so that we
3600 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
3602 - Fix a dangling reference that could lead to a crash when DNSPort is
3603 changed or closed (Patch from Robert Hogan.) [Bugfix on
3606 o Minor bugfixes (controller):
3607 - Provide DNS expiry times in GMT, not in local time. For backward
3608 compatibility, ADDRMAP events only provide GMT expiry in an extended
3609 field. "GETINFO address-mappings" always does the right thing.
3610 - Use CRLF line endings properly in NS events.
3611 - Terminate multi-line control events properly. (Original patch
3612 from tup.) [Bugfix on 0.1.2.x-alpha]
3613 - Do not include spaces in SOURCE_ADDR fields in STREAM
3614 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
3617 Changes in version 0.1.2.15 - 2007-07-17
3618 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
3619 problems, fixes compilation on BSD, and fixes a variety of other
3620 bugs. Everybody should upgrade.
3622 o Major bugfixes (compilation):
3623 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
3625 o Major bugfixes (crashes):
3626 - Try even harder not to dereference the first character after
3627 an mmap(). Reported by lodger.
3628 - Fix a crash bug in directory authorities when we re-number the
3629 routerlist while inserting a new router.
3630 - When the cached-routers file is an even multiple of the page size,
3631 don't run off the end and crash. (Fixes bug 455; based on idea
3633 - Fix eventdns.c behavior on Solaris: It is critical to include
3634 orconfig.h _before_ sys/types.h, so that we can get the expected
3635 definition of _FILE_OFFSET_BITS.
3637 o Major bugfixes (security):
3638 - Fix a possible buffer overrun when using BSD natd support. Bug
3640 - When sending destroy cells from a circuit's origin, don't include
3641 the reason for tearing down the circuit. The spec says we didn't,
3642 and now we actually don't. Reported by lodger.
3643 - Keep streamids from different exits on a circuit separate. This
3644 bug may have allowed other routers on a given circuit to inject
3645 cells into streams. Reported by lodger; fixes bug 446.
3646 - If there's a never-before-connected-to guard node in our list,
3647 never choose any guards past it. This way we don't expand our
3648 guard list unless we need to.
3650 o Minor bugfixes (guard nodes):
3651 - Weight guard selection by bandwidth, so that low-bandwidth nodes
3652 don't get overused as guards.
3654 o Minor bugfixes (directory):
3655 - Correctly count the number of authorities that recommend each
3656 version. Previously, we were under-counting by 1.
3657 - Fix a potential crash bug when we load many server descriptors at
3658 once and some of them make others of them obsolete. Fixes bug 458.
3660 o Minor bugfixes (hidden services):
3661 - Stop tearing down the whole circuit when the user asks for a
3662 connection to a port that the hidden service didn't configure.
3665 o Minor bugfixes (misc):
3666 - On Windows, we were preventing other processes from reading
3667 cached-routers while Tor was running. Reported by janbar.
3668 - Fix a possible (but very unlikely) bug in picking routers by
3669 bandwidth. Add a log message to confirm that it is in fact
3670 unlikely. Patch from lodger.
3671 - Backport a couple of memory leak fixes.
3672 - Backport miscellaneous cosmetic bugfixes.
3675 Changes in version 0.2.0.2-alpha - 2007-06-02
3676 o Major bugfixes on 0.2.0.1-alpha:
3677 - Fix an assertion failure related to servers without extra-info digests.
3678 Resolves bugs 441 and 442.
3680 o Minor features (directory):
3681 - Support "If-Modified-Since" when answering HTTP requests for
3682 directories, running-routers documents, and network-status documents.
3683 (There's no need to support it for router descriptors, since those
3684 are downloaded by descriptor digest.)
3686 o Minor build issues:
3687 - Clear up some MIPSPro compiler warnings.
3688 - When building from a tarball on a machine that happens to have SVK
3689 installed, report the micro-revision as whatever version existed
3690 in the tarball, not as "x".
3693 Changes in version 0.2.0.1-alpha - 2007-06-01
3694 This early development snapshot provides new features for people running
3695 Tor as both a client and a server (check out the new RelayBandwidth
3696 config options); lets Tor run as a DNS proxy; and generally moves us
3697 forward on a lot of fronts.
3699 o Major features, server usability:
3700 - New config options RelayBandwidthRate and RelayBandwidthBurst:
3701 a separate set of token buckets for relayed traffic. Right now
3702 relayed traffic is defined as answers to directory requests, and
3703 OR connections that don't have any local circuits on them.
3705 o Major features, client usability:
3706 - A client-side DNS proxy feature to replace the need for
3707 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
3708 for DNS requests on port 9999, use the Tor network to resolve them
3709 anonymously, and send the reply back like a regular DNS server.
3710 The code still only implements a subset of DNS.
3711 - Make PreferTunneledDirConns and TunnelDirConns work even when
3712 we have no cached directory info. This means Tor clients can now
3713 do all of their connections protected by TLS.
3715 o Major features, performance and efficiency:
3716 - Directory authorities accept and serve "extra info" documents for
3717 routers. These documents contain fields from router descriptors
3718 that aren't usually needed, and that use a lot of excess
3719 bandwidth. Once these fields are removed from router descriptors,
3720 the bandwidth savings should be about 60%. [Partially implements
3722 - Servers upload extra-info documents to any authority that accepts
3723 them. Authorities (and caches that have been configured to download
3724 extra-info documents) download them as needed. [Partially implements
3726 - Change the way that Tor buffers data that it is waiting to write.
3727 Instead of queueing data cells in an enormous ring buffer for each
3728 client->OR or OR->OR connection, we now queue cells on a separate
3729 queue for each circuit. This lets us use less slack memory, and
3730 will eventually let us be smarter about prioritizing different kinds
3732 - Use memory pools to allocate cells with better speed and memory
3733 efficiency, especially on platforms where malloc() is inefficient.
3734 - Stop reading on edge connections when their corresponding circuit
3735 buffers are full; start again as the circuits empty out.
3737 o Major features, other:
3738 - Add an HSAuthorityRecordStats option that hidden service authorities
3739 can use to track statistics of overall hidden service usage without
3740 logging information that would be very useful to an attacker.
3741 - Start work implementing multi-level keys for directory authorities:
3742 Add a standalone tool to generate key certificates. (Proposal 103.)
3745 - Directory authorities now call routers Stable if they have an
3746 uptime of at least 30 days, even if that's not the median uptime
3747 in the network. Implements proposal 107, suggested by Kevin Bauer
3750 o Minor fixes (resource management):
3751 - Count the number of open sockets separately from the number
3752 of active connection_t objects. This will let us avoid underusing
3753 our allocated connection limit.
3754 - We no longer use socket pairs to link an edge connection to an
3755 anonymous directory connection or a DirPort test connection.
3756 Instead, we track the link internally and transfer the data
3757 in-process. This saves two sockets per "linked" connection (at the
3758 client and at the server), and avoids the nasty Windows socketpair()
3760 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
3761 for every single inactive connection_t. Free items from the
3762 4k/16k-buffer free lists when they haven't been used for a while.
3764 o Minor features (build):
3765 - Make autoconf search for libevent, openssl, and zlib consistently.
3766 - Update deprecated macros in configure.in.
3767 - When warning about missing headers, tell the user to let us
3768 know if the compile succeeds anyway, so we can downgrade the
3770 - Include the current subversion revision as part of the version
3771 string: either fetch it directly if we're in an SVN checkout, do
3772 some magic to guess it if we're in an SVK checkout, or use
3773 the last-detected version if we're building from a .tar.gz.
3774 Use this version consistently in log messages.
3776 o Minor features (logging):
3777 - Always prepend "Bug: " to any log message about a bug.
3778 - Put a platform string (e.g. "Linux i686") in the startup log
3779 message, so when people paste just their logs, we know if it's
3780 OpenBSD or Windows or what.
3781 - When logging memory usage, break down memory used in buffers by
3784 o Minor features (directory system):
3785 - New config option V2AuthoritativeDirectory that all directory
3786 authorities should set. This will let future authorities choose
3787 not to serve V2 directory information.
3788 - Directory authorities allow multiple router descriptors and/or extra
3789 info documents to be uploaded in a single go. This will make
3790 implementing proposal 104 simpler.
3792 o Minor features (controller):
3793 - Add a new config option __DisablePredictedCircuits designed for
3794 use by the controller, when we don't want Tor to build any circuits
3796 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
3797 so we can exit from the middle of the circuit.
3798 - Implement "getinfo status/circuit-established".
3799 - Implement "getinfo status/version/..." so a controller can tell
3800 whether the current version is recommended, and whether any versions
3801 are good, and how many authorities agree. (Patch from shibz.)
3803 o Minor features (hidden services):
3804 - Allow multiple HiddenServicePort directives with the same virtual
3805 port; when they occur, the user is sent round-robin to one
3806 of the target ports chosen at random. Partially fixes bug 393 by
3807 adding limited ad-hoc round-robining.
3809 o Minor features (other):
3811 - Add a new AutomapHostsOnResolve option: when it is enabled, any
3812 resolve request for hosts matching a given pattern causes Tor to
3813 generate an internal virtual address mapping for that host. This
3814 allows DNSPort to work sensibly with hidden service users. By
3815 default, .exit and .onion addresses are remapped; the list of
3816 patterns can be reconfigured with AutomapHostsSuffixes.
3817 - Add an "-F" option to tor-resolve to force a resolve for a .onion
3818 address. Thanks to the AutomapHostsOnResolve option, this is no
3819 longer a completely silly thing to do.
3820 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
3821 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
3822 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
3823 minus 1 byte: the actual maximum declared bandwidth.
3826 - Removed support for the old binary "version 0" controller protocol.
3827 This has been deprecated since 0.1.1, and warnings have been issued
3828 since 0.1.2. When we encounter a v0 control message, we now send
3829 back an error and close the connection.
3830 - Remove the old "dns worker" server DNS code: it hasn't been default
3831 since 0.1.2.2-alpha, and all the servers seem to be using the new
3834 o Minor bugfixes (portability):
3835 - Even though Windows is equally happy with / and \ as path separators,
3836 try to use \ consistently on Windows and / consistently on Unix: it
3837 makes the log messages nicer.
3838 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
3839 - Read resolv.conf files correctly on platforms where read() returns
3840 partial results on small file reads.
3842 o Minor bugfixes (directory):
3843 - Correctly enforce that elements of directory objects do not appear
3844 more often than they are allowed to appear.
3845 - When we are reporting the DirServer line we just parsed, we were
3846 logging the second stanza of the key fingerprint, not the first.
3848 o Minor bugfixes (logging):
3849 - When we hit an EOF on a log (probably because we're shutting down),
3850 don't try to remove the log from the list: just mark it as
3851 unusable. (Bulletproofs against bug 222.)
3853 o Minor bugfixes (other):
3854 - In the exitlist script, only consider the most recently published
3855 server descriptor for each server. Also, when the user requests
3856 a list of servers that _reject_ connections to a given address,
3857 explicitly exclude the IPs that also have servers that accept
3858 connections to that address. (Resolves bug 405.)
3859 - Stop allowing hibernating servers to be "stable" or "fast".
3860 - On Windows, we were preventing other processes from reading
3861 cached-routers while Tor was running. (Reported by janbar)
3862 - Make the NodeFamilies config option work. (Reported by
3863 lodger -- it has never actually worked, even though we added it
3865 - Check return values from pthread_mutex functions.
3866 - Don't save non-general-purpose router descriptors to the disk cache,
3867 because we have no way of remembering what their purpose was when
3869 - Add even more asserts to hunt down bug 417.
3870 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
3871 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
3872 Add a log message to confirm that it is in fact unlikely.
3874 o Minor bugfixes (controller):
3875 - Make 'getinfo fingerprint' return a 551 error if we're not a
3876 server, so we match what the control spec claims we do. Reported
3878 - Fix a typo in an error message when extendcircuit fails that
3879 caused us to not follow the \r\n-based delimiter protocol. Reported
3882 o Code simplifications and refactoring:
3883 - Stop passing around circuit_t and crypt_path_t pointers that are
3884 implicit in other procedure arguments.
3885 - Drop the old code to choke directory connections when the
3886 corresponding OR connections got full: thanks to the cell queue
3887 feature, OR conns don't get full any more.
3888 - Make dns_resolve() handle attaching connections to circuits
3889 properly, so the caller doesn't have to.
3890 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
3891 - Keep the connection array as a dynamic smartlist_t, rather than as
3892 a fixed-sized array. This is important, as the number of connections
3893 is becoming increasingly decoupled from the number of sockets.
3896 Changes in version 0.1.2.14 - 2007-05-25
3897 Tor 0.1.2.14 changes the addresses of two directory authorities (this
3898 change especially affects those who serve or use hidden services),
3899 and fixes several other crash- and security-related bugs.
3901 o Directory authority changes:
3902 - Two directory authorities (moria1 and moria2) just moved to new
3903 IP addresses. This change will particularly affect those who serve
3904 or use hidden services.
3906 o Major bugfixes (crashes):
3907 - If a directory server runs out of space in the connection table
3908 as it's processing a begin_dir request, it will free the exit stream
3909 but leave it attached to the circuit, leading to unpredictable
3910 behavior. (Reported by seeess, fixes bug 425.)
3911 - Fix a bug in dirserv_remove_invalid() that would cause authorities
3912 to corrupt memory under some really unlikely scenarios.
3913 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
3914 - Avoid segfaults when reading from mmaped descriptor file. (Reported
3917 o Major bugfixes (security):
3918 - When choosing an entry guard for a circuit, avoid using guards
3919 that are in the same family as the chosen exit -- not just guards
3920 that are exactly the chosen exit. (Reported by lodger.)
3922 o Major bugfixes (resource management):
3923 - If a directory authority is down, skip it when deciding where to get
3924 networkstatus objects or descriptors. Otherwise we keep asking
3925 every 10 seconds forever. Fixes bug 384.
3926 - Count it as a failure if we fetch a valid network-status but we
3927 don't want to keep it. Otherwise we'll keep fetching it and keep
3928 not wanting to keep it. Fixes part of bug 422.
3929 - If all of our dirservers have given us bad or no networkstatuses
3930 lately, then stop hammering them once per minute even when we
3931 think they're failed. Fixes another part of bug 422.
3934 - Actually set the purpose correctly for descriptors inserted with
3936 - When we have k non-v2 authorities in our DirServer config,
3937 we ignored the last k authorities in the list when updating our
3939 - Correctly back-off from requesting router descriptors that we are
3940 having a hard time downloading.
3941 - Read resolv.conf files correctly on platforms where read() returns
3942 partial results on small file reads.
3943 - Don't rebuild the entire router store every time we get 32K of
3944 routers: rebuild it when the journal gets very large, or when
3945 the gaps in the store get very large.
3948 - When routers publish SVN revisions in their router descriptors,
3949 authorities now include those versions correctly in networkstatus
3951 - Warn when using a version of libevent before 1.3b to run a server on
3952 OSX or BSD: these versions interact badly with userspace threads.
3955 Changes in version 0.1.2.13 - 2007-04-24
3956 This release features some major anonymity fixes, such as safer path
3957 selection; better client performance; faster bootstrapping, better
3958 address detection, and better DNS support for servers; write limiting as
3959 well as read limiting to make servers easier to run; and a huge pile of
3960 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
3962 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
3963 of the Freenode IRC network, remembering his patience and vision for
3964 free speech on the Internet.
3967 - Fix a memory leak when we ask for "all" networkstatuses and we
3968 get one we don't recognize.
3969 - Add more asserts to hunt down bug 417.
3970 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
3973 Changes in version 0.1.2.12-rc - 2007-03-16
3975 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
3976 directory information requested inside Tor connections (i.e. via
3977 begin_dir cells). It only triggered when the same connection was
3978 serving other data at the same time. Reported by seeess.
3981 - When creating a circuit via the controller, send a 'launched'
3982 event when we're done, so we follow the spec better.
3985 Changes in version 0.1.2.11-rc - 2007-03-15
3986 o Minor bugfixes (controller), reported by daejees:
3987 - Correct the control spec to match how the code actually responds
3988 to 'getinfo addr-mappings/*'.
3989 - The control spec described a GUARDS event, but the code
3990 implemented a GUARD event. Standardize on GUARD, but let people
3994 Changes in version 0.1.2.10-rc - 2007-03-07
3995 o Major bugfixes (Windows):
3996 - Do not load the NT services library functions (which may not exist)
3997 just to detect if we're a service trying to shut down. Now we run
3998 on Win98 and friends again.
4000 o Minor bugfixes (other):
4001 - Clarify a couple of log messages.
4002 - Fix a misleading socks5 error number.
4005 Changes in version 0.1.2.9-rc - 2007-03-02
4006 o Major bugfixes (Windows):
4007 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
4008 of the usual GCC "%llu". This prevents a bug when saving 64-bit
4009 int configuration values: the high-order 32 bits would get
4010 truncated. In particular, we were being bitten by the default
4011 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
4012 and maybe also bug 397.)
4014 o Minor bugfixes (performance):
4015 - Use OpenSSL's AES implementation on platforms where it's faster.
4016 This could save us as much as 10% CPU usage.
4018 o Minor bugfixes (server):
4019 - Do not rotate onion key immediately after setting it for the first
4022 o Minor bugfixes (directory authorities):
4023 - Stop calling servers that have been hibernating for a long time
4024 "stable". Also, stop letting hibernating or obsolete servers affect
4025 uptime and bandwidth cutoffs.
4026 - Stop listing hibernating servers in the v1 directory.
4028 o Minor bugfixes (hidden services):
4029 - Upload hidden service descriptors slightly less often, to reduce
4030 load on authorities.
4032 o Minor bugfixes (other):
4033 - Fix an assert that could trigger if a controller quickly set then
4034 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
4035 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
4037 - Fix a potential race condition in the rpm installer. Found by
4039 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
4040 of 2 as indicating that the server is completely bad; it sometimes
4041 means that the server is just bad for the request in question. (may fix
4042 the last of bug 326.)
4043 - Disable encrypted directory connections when we don't have a server
4044 descriptor for the destination. We'll get this working again in
4048 Changes in version 0.1.2.8-beta - 2007-02-26
4049 o Major bugfixes (crashes):
4050 - Stop crashing when the controller asks us to resetconf more than
4051 one config option at once. (Vidalia 0.0.11 does this.)
4052 - Fix a crash that happened on Win98 when we're given command-line
4053 arguments: don't try to load NT service functions from advapi32.dll
4054 except when we need them. (Bug introduced in 0.1.2.7-alpha;
4056 - Fix a longstanding obscure crash bug that could occur when
4057 we run out of DNS worker processes. (Resolves bug 390.)
4059 o Major bugfixes (hidden services):
4060 - Correctly detect whether hidden service descriptor downloads are
4061 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
4063 o Major bugfixes (accounting):
4064 - When we start during an accounting interval before it's time to wake
4065 up, remember to wake up at the correct time. (May fix bug 342.)
4067 o Minor bugfixes (controller):
4068 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
4069 clear the corresponding on_circuit variable, and remember later
4070 that we don't need to send a redundant CLOSED event. (Resolves part
4072 - Report events where a resolve succeeded or where we got a socks
4073 protocol error correctly, rather than calling both of them
4075 - Change reported stream target addresses to IP consistently when
4076 we finally get the IP from an exit node.
4077 - Send log messages to the controller even if they happen to be very
4080 o Minor bugfixes (other):
4081 - Display correct results when reporting which versions are
4082 recommended, and how recommended they are. (Resolves bug 383.)
4083 - Improve our estimates for directory bandwidth to be less random:
4084 guess that an unrecognized directory will have the average bandwidth
4085 from all known directories, not that it will have the average
4086 bandwidth from those directories earlier than it on the list.
4087 - If we start a server with ClientOnly 1, then set ClientOnly to 0
4088 and hup, stop triggering an assert based on an empty onion_key.
4089 - On platforms with no working mmap() equivalent, don't warn the
4090 user when cached-routers doesn't exist.
4091 - Warn the user when mmap() [or its equivalent] fails for some reason
4092 other than file-not-found.
4093 - Don't warn the user when cached-routers.new doesn't exist: that's
4094 perfectly fine when starting up for the first time.
4095 - When EntryNodes are configured, rebuild the guard list to contain,
4096 in order: the EntryNodes that were guards before; the rest of the
4097 EntryNodes; the nodes that were guards before.
4098 - Mask out all signals in sub-threads; only the libevent signal
4099 handler should be processing them. This should prevent some crashes
4100 on some machines using pthreads. (Patch from coderman.)
4101 - Fix switched arguments on memset in the implementation of
4102 tor_munmap() for systems with no mmap() call.
4103 - When Tor receives a router descriptor that it asked for, but
4104 no longer wants (because it has received fresh networkstatuses
4105 in the meantime), do not warn the user. Cache the descriptor if
4106 we're a cache; drop it if we aren't.
4107 - Make earlier entry guards _really_ get retried when the network
4109 - On a malformed DNS reply, always give an error to the corresponding
4111 - Build with recent libevents on platforms that do not define the
4112 nonstandard types "u_int8_t" and friends.
4114 o Minor features (controller):
4115 - Warn the user when an application uses the obsolete binary v0
4116 control protocol. We're planning to remove support for it during
4117 the next development series, so it's good to give people some
4119 - Add STREAM_BW events to report per-entry-stream bandwidth
4120 use. (Patch from Robert Hogan.)
4121 - Rate-limit SIGNEWNYM signals in response to controllers that
4122 impolitely generate them for every single stream. (Patch from
4123 mwenge; closes bug 394.)
4124 - Make REMAP stream events have a SOURCE (cache or exit), and
4125 make them generated in every case where we get a successful
4126 connected or resolved cell.
4128 o Minor bugfixes (performance):
4129 - Call router_have_min_dir_info half as often. (This is showing up in
4130 some profiles, but not others.)
4131 - When using GCC, make log_debug never get called at all, and its
4132 arguments never get evaluated, when no debug logs are configured.
4133 (This is showing up in some profiles, but not others.)
4136 - Remove some never-implemented options. Mark PathlenCoinWeight as
4138 - Implement proposal 106: Stop requiring clients to have well-formed
4139 certificates; stop checking nicknames in certificates. (Clients
4140 have certificates so that they can look like Tor servers, but in
4141 the future we might want to allow them to look like regular TLS
4142 clients instead. Nicknames in certificates serve no purpose other
4143 than making our protocol easier to recognize on the wire.)
4144 - Revise messages on handshake failure again to be even more clear about
4145 which are incoming connections and which are outgoing.
4146 - Discard any v1 directory info that's over 1 month old (for
4147 directories) or over 1 week old (for running-routers lists).
4148 - Do not warn when individual nodes in the configuration's EntryNodes,
4149 ExitNodes, etc are down: warn only when all possible nodes
4150 are down. (Fixes bug 348.)
4151 - Always remove expired routers and networkstatus docs before checking
4152 whether we have enough information to build circuits. (Fixes
4154 - Put a lower-bound on MaxAdvertisedBandwidth.
4157 Changes in version 0.1.2.7-alpha - 2007-02-06
4158 o Major bugfixes (rate limiting):
4159 - Servers decline directory requests much more aggressively when
4160 they're low on bandwidth. Otherwise they end up queueing more and
4161 more directory responses, which can't be good for latency.
4162 - But never refuse directory requests from local addresses.
4163 - Fix a memory leak when sending a 503 response for a networkstatus
4165 - Be willing to read or write on local connections (e.g. controller
4166 connections) even when the global rate limiting buckets are empty.
4167 - If our system clock jumps back in time, don't publish a negative
4168 uptime in the descriptor. Also, don't let the global rate limiting
4169 buckets go absurdly negative.
4170 - Flush local controller connection buffers periodically as we're
4171 writing to them, so we avoid queueing 4+ megabytes of data before
4174 o Major bugfixes (NT services):
4175 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
4176 command-line flag so that admins can override the default by saying
4177 "tor --service install --user "SomeUser"". This will not affect
4178 existing installed services. Also, warn the user that the service
4179 will look for its configuration file in the service user's
4180 %appdata% directory. (We can't do the 'hardwire the user's appdata
4181 directory' trick any more, since we may not have read access to that
4184 o Major bugfixes (other):
4185 - Previously, we would cache up to 16 old networkstatus documents
4186 indefinitely, if they came from nontrusted authorities. Now we
4187 discard them if they are more than 10 days old.
4188 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
4190 - Detect and reject malformed DNS responses containing circular
4192 - If exits are rare enough that we're not marking exits as guards,
4193 ignore exit bandwidth when we're deciding the required bandwidth
4195 - When we're handling a directory connection tunneled over Tor,
4196 don't fill up internal memory buffers with all the data we want
4197 to tunnel; instead, only add it if the OR connection that will
4198 eventually receive it has some room for it. (This can lead to
4199 slowdowns in tunneled dir connections; a better solution will have
4202 o Minor bugfixes (dns):
4203 - Add some defensive programming to eventdns.c in an attempt to catch
4204 possible memory-stomping bugs.
4205 - Detect and reject DNS replies containing IPv4 or IPv6 records with
4206 an incorrect number of bytes. (Previously, we would ignore the
4208 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
4209 in the correct order, and doesn't crash.
4210 - Free memory held in recently-completed DNS lookup attempts on exit.
4211 This was not a memory leak, but may have been hiding memory leaks.
4212 - Handle TTL values correctly on reverse DNS lookups.
4213 - Treat failure to parse resolv.conf as an error.
4215 o Minor bugfixes (other):
4216 - Fix crash with "tor --list-fingerprint" (reported by seeess).
4217 - When computing clock skew from directory HTTP headers, consider what
4218 time it was when we finished asking for the directory, not what
4220 - Expire socks connections if they spend too long waiting for the
4221 handshake to finish. Previously we would let them sit around for
4222 days, if the connecting application didn't close them either.
4223 - And if the socks handshake hasn't started, don't send a
4224 "DNS resolve socks failed" handshake reply; just close it.
4225 - Stop using C functions that OpenBSD's linker doesn't like.
4226 - Don't launch requests for descriptors unless we have networkstatuses
4227 from at least half of the authorities. This delays the first
4228 download slightly under pathological circumstances, but can prevent
4229 us from downloading a bunch of descriptors we don't need.
4230 - Do not log IPs with TLS failures for incoming TLS
4231 connections. (Fixes bug 382.)
4232 - If the user asks to use invalid exit nodes, be willing to use
4234 - Stop using the reserved ac_cv namespace in our configure script.
4235 - Call stat() slightly less often; use fstat() when possible.
4236 - Refactor the way we handle pending circuits when an OR connection
4237 completes or fails, in an attempt to fix a rare crash bug.
4238 - Only rewrite a conn's address based on X-Forwarded-For: headers
4239 if it's a parseable public IP address; and stop adding extra quotes
4240 to the resulting address.
4243 - Weight directory requests by advertised bandwidth. Now we can
4244 let servers enable write limiting but still allow most clients to
4245 succeed at their directory requests. (We still ignore weights when
4246 choosing a directory authority; I hope this is a feature.)
4249 - Create a new file ReleaseNotes which was the old ChangeLog. The
4250 new ChangeLog file now includes the summaries for all development
4252 - Check for addresses with invalid characters at the exit as well
4253 as at the client, and warn less verbosely when they fail. You can
4254 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
4255 - Adapt a patch from goodell to let the contrib/exitlist script
4256 take arguments rather than require direct editing.
4257 - Inform the server operator when we decide not to advertise a
4258 DirPort due to AccountingMax enabled or a low BandwidthRate. It
4259 was confusing Zax, so now we're hopefully more helpful.
4260 - Bring us one step closer to being able to establish an encrypted
4261 directory tunnel without knowing a descriptor first. Still not
4262 ready yet. As part of the change, now assume we can use a
4263 create_fast cell if we don't know anything about a router.
4264 - Allow exit nodes to use nameservers running on ports other than 53.
4265 - Servers now cache reverse DNS replies.
4266 - Add an --ignore-missing-torrc command-line option so that we can
4267 get the "use sensible defaults if the configuration file doesn't
4268 exist" behavior even when specifying a torrc location on the command
4271 o Minor features (controller):
4272 - Track reasons for OR connection failure; make these reasons
4273 available via the controller interface. (Patch from Mike Perry.)
4274 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
4275 can learn when clients are sending malformed hostnames to Tor.
4276 - Clean up documentation for controller status events.
4277 - Add a REMAP status to stream events to note that a stream's
4278 address has changed because of a cached address or a MapAddress
4282 Changes in version 0.1.2.6-alpha - 2007-01-09
4284 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
4285 connection handles more than 4 gigs in either direction, we crash.
4286 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
4287 advertised exit node, somebody might try to exit from us when
4288 we're bootstrapping and before we've built our descriptor yet.
4289 Refuse the connection rather than crashing.
4292 - Warn if we (as a server) find that we've resolved an address that we
4293 weren't planning to resolve.
4294 - Warn that using select() on any libevent version before 1.1 will be
4295 unnecessarily slow (even for select()).
4296 - Flush ERR-level controller status events just like we currently
4297 flush ERR-level log events, so that a Tor shutdown doesn't prevent
4298 the controller from learning about current events.
4300 o Minor features (more controller status events):
4301 - Implement EXTERNAL_ADDRESS server status event so controllers can
4302 learn when our address changes.
4303 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
4304 can learn when directories reject our descriptor.
4305 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
4306 can learn when a client application is speaking a non-socks protocol
4308 - Implement DANGEROUS_SOCKS client status event so controllers
4309 can learn when a client application is leaking DNS addresses.
4310 - Implement BUG general status event so controllers can learn when
4311 Tor is unhappy about its internal invariants.
4312 - Implement CLOCK_SKEW general status event so controllers can learn
4313 when Tor thinks the system clock is set incorrectly.
4314 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
4315 server status events so controllers can learn when their descriptors
4316 are accepted by a directory.
4317 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
4318 server status events so controllers can learn about Tor's progress in
4319 deciding whether it's reachable from the outside.
4320 - Implement BAD_LIBEVENT general status event so controllers can learn
4321 when we have a version/method combination in libevent that needs to
4323 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
4324 and DNS_USELESS server status events so controllers can learn
4325 about changes to DNS server status.
4327 o Minor features (directory):
4328 - Authorities no longer recommend exits as guards if this would shift
4329 too much load to the exit nodes.
4332 Changes in version 0.1.2.5-alpha - 2007-01-06
4334 - Enable write limiting as well as read limiting. Now we sacrifice
4335 capacity if we're pushing out lots of directory traffic, rather
4336 than overrunning the user's intended bandwidth limits.
4337 - Include TLS overhead when counting bandwidth usage; previously, we
4338 would count only the bytes sent over TLS, but not the bytes used
4340 - Support running the Tor service with a torrc not in the same
4341 directory as tor.exe and default to using the torrc located in
4342 the %appdata%\Tor\ of the user who installed the service. Patch
4344 - Servers now check for the case when common DNS requests are going to
4345 wildcarded addresses (i.e. all getting the same answer), and change
4346 their exit policy to reject *:* if it's happening.
4347 - Implement BEGIN_DIR cells, so we can connect to the directory
4348 server via TLS to do encrypted directory requests rather than
4349 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
4350 config options if you like.
4352 o Minor features (config and docs):
4353 - Start using the state file to store bandwidth accounting data:
4354 the bw_accounting file is now obsolete. We'll keep generating it
4355 for a while for people who are still using 0.1.2.4-alpha.
4356 - Try to batch changes to the state file so that we do as few
4357 disk writes as possible while still storing important things in
4359 - The state file and the bw_accounting file get saved less often when
4360 the AvoidDiskWrites config option is set.
4361 - Make PIDFile work on Windows (untested).
4362 - Add internal descriptions for a bunch of configuration options:
4363 accessible via controller interface and in comments in saved
4365 - Reject *:563 (NNTPS) in the default exit policy. We already reject
4366 NNTP by default, so this seems like a sensible addition.
4367 - Clients now reject hostnames with invalid characters. This should
4368 avoid some inadvertent info leaks. Add an option
4369 AllowNonRFC953Hostnames to disable this behavior, in case somebody
4370 is running a private network with hosts called @, !, and #.
4371 - Add a maintainer script to tell us which options are missing
4372 documentation: "make check-docs".
4373 - Add a new address-spec.txt document to describe our special-case
4374 addresses: .exit, .onion, and .noconnnect.
4376 o Minor features (DNS):
4377 - Ongoing work on eventdns infrastructure: now it has dns server
4378 and ipv6 support. One day Tor will make use of it.
4379 - Add client-side caching for reverse DNS lookups.
4380 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
4381 - When we change nameservers or IP addresses, reset and re-launch
4382 our tests for DNS hijacking.
4384 o Minor features (directory):
4385 - Authorities now specify server versions in networkstatus. This adds
4386 about 2% to the size of compressed networkstatus docs, and allows
4387 clients to tell which servers support BEGIN_DIR and which don't.
4388 The implementation is forward-compatible with a proposed future
4389 protocol version scheme not tied to Tor versions.
4390 - DirServer configuration lines now have an orport= option so
4391 clients can open encrypted tunnels to the authorities without
4392 having downloaded their descriptors yet. Enabled for moria1,
4393 moria2, tor26, and lefkada now in the default configuration.
4394 - Directory servers are more willing to send a 503 "busy" if they
4395 are near their write limit, especially for v1 directory requests.
4396 Now they can use their limited bandwidth for actual Tor traffic.
4397 - Clients track responses with status 503 from dirservers. After a
4398 dirserver has given us a 503, we try not to use it until an hour has
4399 gone by, or until we have no dirservers that haven't given us a 503.
4400 - When we get a 503 from a directory, and we're not a server, we don't
4401 count the failure against the total number of failures allowed
4402 for the thing we're trying to download.
4403 - Report X-Your-Address-Is correctly from tunneled directory
4404 connections; don't report X-Your-Address-Is when it's an internal
4405 address; and never believe reported remote addresses when they're
4407 - Protect against an unlikely DoS attack on directory servers.
4408 - Add a BadDirectory flag to network status docs so that authorities
4409 can (eventually) tell clients about caches they believe to be
4412 o Minor features (controller):
4413 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
4414 - Reimplement GETINFO so that info/names stays in sync with the
4416 - Implement "GETINFO fingerprint".
4417 - Implement "SETEVENTS GUARD" so controllers can get updates on
4418 entry guard status as it changes.
4420 o Minor features (clean up obsolete pieces):
4421 - Remove some options that have been deprecated since at least
4422 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
4423 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
4425 - We no longer look for identity and onion keys in "identity.key" and
4426 "onion.key" -- these were replaced by secret_id_key and
4427 secret_onion_key in 0.0.8pre1.
4428 - We no longer require unrecognized directory entries to be
4431 o Major bugfixes (security):
4432 - Stop sending the HttpProxyAuthenticator string to directory
4433 servers when directory connections are tunnelled through Tor.
4434 - Clients no longer store bandwidth history in the state file.
4435 - Do not log introduction points for hidden services if SafeLogging
4437 - When generating bandwidth history, round down to the nearest
4438 1k. When storing accounting data, round up to the nearest 1k.
4439 - When we're running as a server, remember when we last rotated onion
4440 keys, so that we will rotate keys once they're a week old even if
4441 we never stay up for a week ourselves.
4443 o Major bugfixes (other):
4444 - Fix a longstanding bug in eventdns that prevented the count of
4445 timed-out resolves from ever being reset. This bug caused us to
4446 give up on a nameserver the third time it timed out, and try it
4447 10 seconds later... and to give up on it every time it timed out
4449 - Take out the '5 second' timeout from the connection retry
4450 schedule. Now the first connect attempt will wait a full 10
4451 seconds before switching to a new circuit. Perhaps this will help
4452 a lot. Based on observations from Mike Perry.
4453 - Fix a bug on the Windows implementation of tor_mmap_file() that
4454 would prevent the cached-routers file from ever loading. Reported
4458 - Fix an assert failure when a directory authority sets
4459 AuthDirRejectUnlisted and then receives a descriptor from an
4460 unlisted router. Reported by seeess.
4461 - Avoid a double-free when parsing malformed DirServer lines.
4462 - Fix a bug when a BSD-style PF socket is first used. Patch from
4464 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
4465 to resolve an address at a given exit node even when they ask for
4467 - Servers no longer ever list themselves in their "family" line,
4468 even if configured to do so. This makes it easier to configure
4469 family lists conveniently.
4470 - When running as a server, don't fall back to 127.0.0.1 when no
4471 nameservers are configured in /etc/resolv.conf; instead, make the
4472 user fix resolv.conf or specify nameservers explicitly. (Resolves
4474 - Stop accepting certain malformed ports in configured exit policies.
4475 - Don't re-write the fingerprint file every restart, unless it has
4477 - Stop warning when a single nameserver fails: only warn when _all_ of
4478 our nameservers have failed. Also, when we only have one nameserver,
4479 raise the threshold for deciding that the nameserver is dead.
4480 - Directory authorities now only decide that routers are reachable
4481 if their identity keys are as expected.
4482 - When the user uses bad syntax in the Log config line, stop
4483 suggesting other bad syntax as a replacement.
4484 - Correctly detect ipv6 DNS capability on OpenBSD.
4486 o Minor bugfixes (controller):
4487 - Report the circuit number correctly in STREAM CLOSED events. Bug
4488 reported by Mike Perry.
4489 - Do not report bizarre values for results of accounting GETINFOs
4490 when the last second's write or read exceeds the allotted bandwidth.
4491 - Report "unrecognized key" rather than an empty string when the
4492 controller tries to fetch a networkstatus that doesn't exist.
4495 Changes in version 0.1.1.26 - 2006-12-14
4496 o Security bugfixes:
4497 - Stop sending the HttpProxyAuthenticator string to directory
4498 servers when directory connections are tunnelled through Tor.
4499 - Clients no longer store bandwidth history in the state file.
4500 - Do not log introduction points for hidden services if SafeLogging
4504 - Fix an assert failure when a directory authority sets
4505 AuthDirRejectUnlisted and then receives a descriptor from an
4506 unlisted router (reported by seeess).
4509 Changes in version 0.1.2.4-alpha - 2006-12-03
4511 - Add support for using natd; this allows FreeBSDs earlier than
4512 5.1.2 to have ipfw send connections through Tor without using
4513 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
4516 - Make all connections to addresses of the form ".noconnect"
4517 immediately get closed. This lets application/controller combos
4518 successfully test whether they're talking to the same Tor by
4519 watching for STREAM events.
4520 - Make cross.sh cross-compilation script work even when autogen.sh
4521 hasn't been run. (Patch from Michael Mohr.)
4522 - Statistics dumped by -USR2 now include a breakdown of public key
4523 operations, for profiling.
4526 - Fix a major leak when directory authorities parse their
4527 approved-routers list, a minor memory leak when we fail to pick
4528 an exit node, and a few rare leaks on errors.
4529 - Handle TransPort connections even when the server sends data before
4530 the client sends data. Previously, the connection would just hang
4531 until the client sent data. (Patch from tup based on patch from
4533 - Avoid assert failure when our cached-routers file is empty on
4537 - Don't log spurious warnings when we see a circuit close reason we
4538 don't recognize; it's probably just from a newer version of Tor.
4539 - Have directory authorities allow larger amounts of drift in uptime
4540 without replacing the server descriptor: previously, a server that
4541 restarted every 30 minutes could have 48 "interesting" descriptors
4543 - Start linking to the Tor specification and Tor reference manual
4544 correctly in the Windows installer.
4545 - Add Vidalia to the OS X uninstaller script, so when we uninstall
4546 Tor/Privoxy we also uninstall Vidalia.
4547 - Resume building on Irix64, and fix a lot of warnings from its
4549 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
4550 when we're running as a client.
4553 Changes in version 0.1.1.25 - 2006-11-04
4555 - When a client asks us to resolve (rather than connect to)
4556 an address, and we have a cached answer, give them the cached
4557 answer. Previously, we would give them no answer at all.
4558 - We were building exactly the wrong circuits when we predict
4559 hidden service requirements, meaning Tor would have to build all
4560 its circuits on demand.
4561 - If none of our live entry guards have a high uptime, but we
4562 require a guard with a high uptime, try adding a new guard before
4563 we give up on the requirement. This patch should make long-lived
4564 connections more stable on average.
4565 - When testing reachability of our DirPort, don't launch new
4566 tests when there's already one in progress -- unreachable
4567 servers were stacking up dozens of testing streams.
4569 o Security bugfixes:
4570 - When the user sends a NEWNYM signal, clear the client-side DNS
4571 cache too. Otherwise we continue to act on previous information.
4574 - Avoid a memory corruption bug when creating a hash table for
4576 - Avoid possibility of controller-triggered crash when misusing
4577 certain commands from a v0 controller on platforms that do not
4578 handle printf("%s",NULL) gracefully.
4579 - Avoid infinite loop on unexpected controller input.
4580 - Don't log spurious warnings when we see a circuit close reason we
4581 don't recognize; it's probably just from a newer version of Tor.
4582 - Add Vidalia to the OS X uninstaller script, so when we uninstall
4583 Tor/Privoxy we also uninstall Vidalia.
4586 Changes in version 0.1.2.3-alpha - 2006-10-29
4588 - Prepare for servers to publish descriptors less often: never
4589 discard a descriptor simply for being too old until either it is
4590 recommended by no authorities, or until we get a better one for
4591 the same router. Make caches consider retaining old recommended
4592 routers for even longer.
4593 - If most authorities set a BadExit flag for a server, clients
4594 don't think of it as a general-purpose exit. Clients only consider
4595 authorities that advertise themselves as listing bad exits.
4596 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
4597 headers for content, so that we can work better in the presence of
4598 caching HTTP proxies.
4599 - Allow authorities to list nodes as bad exits by fingerprint or by
4602 o Minor features, controller:
4603 - Add a REASON field to CIRC events; for backward compatibility, this
4604 field is sent only to controllers that have enabled the extended
4605 event format. Also, add additional reason codes to explain why
4606 a given circuit has been destroyed or truncated. (Patches from
4608 - Add a REMOTE_REASON field to extended CIRC events to tell the
4609 controller about why a remote OR told us to close a circuit.
4610 - Stream events also now have REASON and REMOTE_REASON fields,
4611 working much like those for circuit events.
4612 - There's now a GETINFO ns/... field so that controllers can ask Tor
4613 about the current status of a router.
4614 - A new event type "NS" to inform a controller when our opinion of
4615 a router's status has changed.
4616 - Add a GETINFO events/names and GETINFO features/names so controllers
4617 can tell which events and features are supported.
4618 - A new CLEARDNSCACHE signal to allow controllers to clear the
4619 client-side DNS cache without expiring circuits.
4621 o Security bugfixes:
4622 - When the user sends a NEWNYM signal, clear the client-side DNS
4623 cache too. Otherwise we continue to act on previous information.
4626 - Avoid sending junk to controllers or segfaulting when a controller
4627 uses EVENT_NEW_DESC with verbose nicknames.
4628 - Stop triggering asserts if the controller tries to extend hidden
4629 service circuits (reported by mwenge).
4630 - Avoid infinite loop on unexpected controller input.
4631 - When the controller does a "GETINFO network-status", tell it
4632 about even those routers whose descriptors are very old, and use
4633 long nicknames where appropriate.
4634 - Change NT service functions to be loaded on demand. This lets us
4635 build with MinGW without breaking Tor for Windows 98 users.
4636 - Do DirPort reachability tests less often, since a single test
4637 chews through many circuits before giving up.
4638 - In the hidden service example in torrc.sample, stop recommending
4639 esoteric and discouraged hidden service options.
4640 - When stopping an NT service, wait up to 10 sec for it to actually
4641 stop. (Patch from Matt Edman; resolves bug 295.)
4642 - Fix handling of verbose nicknames with ORCONN controller events:
4643 make them show up exactly when requested, rather than exactly when
4645 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
4646 printing a duplicate "$" in the keys we send (reported by mwenge).
4647 - Correctly set maximum connection limit on Cygwin. (This time
4649 - Try to detect Windows correctly when cross-compiling.
4650 - Detect the size of the routers file correctly even if it is
4651 corrupted (on systems without mmap) or not page-aligned (on systems
4652 with mmap). This bug was harmless.
4653 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
4654 to open a stream fails; now we do in more cases. This should
4655 make clients able to find a good exit faster in some cases, since
4656 unhandleable requests will now get an error rather than timing out.
4657 - Resolve two memory leaks when rebuilding the on-disk router cache
4658 (reported by fookoowa).
4659 - Clean up minor code warnings suggested by the MIPSpro C compiler,
4660 and reported by some Centos users.
4661 - Controller signals now work on non-Unix platforms that don't define
4662 SIGUSR1 and SIGUSR2 the way we expect.
4663 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
4664 values before failing, and always enables eventdns.
4665 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
4666 Try to fix this in configure.in by checking for most functions
4667 before we check for libevent.
4670 Changes in version 0.1.2.2-alpha - 2006-10-07
4672 - Make our async eventdns library on-by-default for Tor servers,
4673 and plan to deprecate the separate dnsworker threads.
4674 - Add server-side support for "reverse" DNS lookups (using PTR
4675 records so clients can determine the canonical hostname for a given
4676 IPv4 address). Only supported by servers using eventdns; servers
4677 now announce in their descriptors whether they support eventdns.
4678 - Specify and implement client-side SOCKS5 interface for reverse DNS
4679 lookups (see doc/socks-extensions.txt).
4680 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
4681 connect to directory servers through Tor. Previously, clients needed
4682 to find Tor exits to make private connections to directory servers.
4683 - Avoid choosing Exit nodes for entry or middle hops when the
4684 total bandwidth available from non-Exit nodes is much higher than
4685 the total bandwidth available from Exit nodes.
4686 - Workaround for name servers (like Earthlink's) that hijack failing
4687 DNS requests and replace the no-such-server answer with a "helpful"
4688 redirect to an advertising-driven search portal. Also work around
4689 DNS hijackers who "helpfully" decline to hijack known-invalid
4690 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
4691 lets you turn it off.
4692 - Send out a burst of long-range padding cells once we've established
4693 that we're reachable. Spread them over 4 circuits, so hopefully
4694 a few will be fast. This exercises our bandwidth and bootstraps
4695 us into the directory more quickly.
4697 o New/improved config options:
4698 - Add new config option "ResolvConf" to let the server operator
4699 choose an alternate resolve.conf file when using eventdns.
4700 - Add an "EnforceDistinctSubnets" option to control our "exclude
4701 servers on the same /16" behavior. It's still on by default; this
4702 is mostly for people who want to operate private test networks with
4703 all the machines on the same subnet.
4704 - If one of our entry guards is on the ExcludeNodes list, or the
4705 directory authorities don't think it's a good guard, treat it as
4706 if it were unlisted: stop using it as a guard, and throw it off
4707 the guards list if it stays that way for a long time.
4708 - Allow directory authorities to be marked separately as authorities
4709 for the v1 directory protocol, the v2 directory protocol, and
4710 as hidden service directories, to make it easier to retire old
4711 authorities. V1 authorities should set "HSAuthoritativeDir 1"
4712 to continue being hidden service authorities too.
4713 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
4715 o Minor features, controller:
4716 - Fix CIRC controller events so that controllers can learn the
4717 identity digests of non-Named servers used in circuit paths.
4718 - Let controllers ask for more useful identifiers for servers. Instead
4719 of learning identity digests for un-Named servers and nicknames
4720 for Named servers, the new identifiers include digest, nickname,
4721 and indication of Named status. Off by default; see control-spec.txt
4722 for more information.
4723 - Add a "getinfo address" controller command so it can display Tor's
4724 best guess to the user.
4725 - New controller event to alert the controller when our server
4726 descriptor has changed.
4727 - Give more meaningful errors on controller authentication failure.
4729 o Minor features, other:
4730 - When asked to resolve a hostname, don't use non-exit servers unless
4731 requested to do so. This allows servers with broken DNS to be
4732 useful to the network.
4733 - Divide eventdns log messages into warn and info messages.
4734 - Reserve the nickname "Unnamed" for routers that can't pick
4735 a hostname: any router can call itself Unnamed; directory
4736 authorities will never allocate Unnamed to any particular router;
4737 clients won't believe that any router is the canonical Unnamed.
4738 - Only include function names in log messages for info/debug messages.
4739 For notice/warn/err, the content of the message should be clear on
4740 its own, and printing the function name only confuses users.
4741 - Avoid some false positives during reachability testing: don't try
4742 to test via a server that's on the same /24 as us.
4743 - If we fail to build a circuit to an intended enclave, and it's
4744 not mandatory that we use that enclave, stop wanting it.
4745 - When eventdns is enabled, allow multithreaded builds on NetBSD and
4746 OpenBSD. (We had previously disabled threads on these platforms
4747 because they didn't have working thread-safe resolver functions.)
4749 o Major bugfixes, anonymity/security:
4750 - If a client asked for a server by name, and there's a named server
4751 in our network-status but we don't have its descriptor yet, we
4752 could return an unnamed server instead.
4753 - Fix NetBSD bug that could allow someone to force uninitialized RAM
4754 to be sent to a server's DNS resolver. This only affects NetBSD
4755 and other platforms that do not bounds-check tolower().
4756 - Reject (most) attempts to use Tor circuits with length one. (If
4757 many people start using Tor as a one-hop proxy, exit nodes become
4758 a more attractive target for compromise.)
4759 - Just because your DirPort is open doesn't mean people should be
4760 able to remotely teach you about hidden service descriptors. Now
4761 only accept rendezvous posts if you've got HSAuthoritativeDir set.
4763 o Major bugfixes, other:
4764 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
4765 - When a client asks the server to resolve (not connect to)
4766 an address, and it has a cached answer, give them the cached answer.
4767 Previously, the server would give them no answer at all.
4768 - Allow really slow clients to not hang up five minutes into their
4769 directory downloads (suggested by Adam J. Richter).
4770 - We were building exactly the wrong circuits when we anticipated
4771 hidden service requirements, meaning Tor would have to build all
4772 its circuits on demand.
4773 - Avoid crashing when we mmap a router cache file of size 0.
4774 - When testing reachability of our DirPort, don't launch new
4775 tests when there's already one in progress -- unreachable
4776 servers were stacking up dozens of testing streams.
4778 o Minor bugfixes, correctness:
4779 - If we're a directory mirror and we ask for "all" network status
4780 documents, we would discard status documents from authorities
4782 - Avoid a memory corruption bug when creating a hash table for
4784 - Avoid controller-triggered crash when misusing certain commands
4785 from a v0 controller on platforms that do not handle
4786 printf("%s",NULL) gracefully.
4787 - Don't crash when a controller sends a third argument to an
4788 "extendcircuit" request.
4789 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
4790 response; fix error code when "getinfo dir/status/" fails.
4791 - Avoid crash when telling controller stream-status and a stream
4793 - Patch from Adam Langley to fix assert() in eventdns.c.
4794 - Fix a debug log message in eventdns to say "X resolved to Y"
4795 instead of "X resolved to X".
4796 - Make eventdns give strings for DNS errors, not just error numbers.
4797 - Track unreachable entry guards correctly: don't conflate
4798 'unreachable by us right now' with 'listed as down by the directory
4799 authorities'. With the old code, if a guard was unreachable by
4800 us but listed as running, it would clog our guard list forever.
4801 - Behave correctly in case we ever have a network with more than
4802 2GB/s total advertised capacity.
4803 - Make TrackExitHosts case-insensitive, and fix the behavior of
4804 ".suffix" TrackExitHosts items to avoid matching in the middle of
4806 - Finally fix the openssl warnings from newer gccs that believe that
4807 ignoring a return value is okay, but casting a return value and
4808 then ignoring it is a sign of madness.
4809 - Prevent the contrib/exitlist script from printing the same
4810 result more than once.
4811 - Patch from Steve Hildrey: Generate network status correctly on
4812 non-versioning dirservers.
4813 - Don't listen to the X-Your-Address-Is hint if you did the lookup
4814 via Tor; otherwise you'll think you're the exit node's IP address.
4816 o Minor bugfixes, performance:
4817 - Two small performance improvements on parsing descriptors.
4818 - Major performance improvement on inserting descriptors: change
4819 algorithm from O(n^2) to O(n).
4820 - Make the common memory allocation path faster on machines where
4821 malloc(0) returns a pointer.
4822 - Start remembering X-Your-Address-Is directory hints even if you're
4823 a client, so you can become a server more smoothly.
4824 - Avoid duplicate entries on MyFamily line in server descriptor.
4826 o Packaging, features:
4827 - Remove architecture from OS X builds. The official builds are
4828 now universal binaries.
4829 - The Debian package now uses --verify-config when (re)starting,
4830 to distinguish configuration errors from other errors.
4831 - Update RPMs to require libevent 1.1b.
4833 o Packaging, bugfixes:
4834 - Patches so Tor builds with MinGW on Windows.
4835 - Patches so Tor might run on Cygwin again.
4836 - Resume building on non-gcc compilers and ancient gcc. Resume
4837 building with the -O0 compile flag. Resume building cleanly on
4839 - Run correctly on OS X platforms with case-sensitive filesystems.
4840 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
4841 - Add autoconf checks so Tor can build on Solaris x86 again.
4844 - Documented (and renamed) ServerDNSSearchDomains and
4845 ServerDNSResolvConfFile options.
4846 - Be clearer that the *ListenAddress directives can be repeated
4850 Changes in version 0.1.1.24 - 2006-09-29
4852 - Allow really slow clients to not hang up five minutes into their
4853 directory downloads (suggested by Adam J. Richter).
4854 - Fix major performance regression from 0.1.0.x: instead of checking
4855 whether we have enough directory information every time we want to
4856 do something, only check when the directory information has changed.
4857 This should improve client CPU usage by 25-50%.
4858 - Don't crash if, after a server has been running for a while,
4859 it can't resolve its hostname.
4862 - Allow Tor to start when RunAsDaemon is set but no logs are set.
4863 - Don't crash when the controller receives a third argument to an
4864 "extendcircuit" request.
4865 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
4866 response; fix error code when "getinfo dir/status/" fails.
4867 - Fix configure.in to not produce broken configure files with
4868 more recent versions of autoconf. Thanks to Clint for his auto*
4870 - Fix security bug on NetBSD that could allow someone to force
4871 uninitialized RAM to be sent to a server's DNS resolver. This
4872 only affects NetBSD and other platforms that do not bounds-check
4874 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
4875 methods: these are known to be buggy.
4876 - If we're a directory mirror and we ask for "all" network status
4877 documents, we would discard status documents from authorities
4881 Changes in version 0.1.2.1-alpha - 2006-08-27
4883 - Add "eventdns" async dns library from Adam Langley, tweaked to
4884 build on OSX and Windows. Only enabled if you pass the
4885 --enable-eventdns argument to configure.
4886 - Allow servers with no hostname or IP address to learn their
4887 IP address by asking the directory authorities. This code only
4888 kicks in when you would normally have exited with a "no address"
4889 error. Nothing's authenticated, so use with care.
4890 - Rather than waiting a fixed amount of time between retrying
4891 application connections, we wait only 5 seconds for the first,
4892 10 seconds for the second, and 15 seconds for each retry after
4893 that. Hopefully this will improve the expected user experience.
4894 - Patch from Tup to add support for transparent AP connections:
4895 this basically bundles the functionality of trans-proxy-tor
4896 into the Tor mainline. Now hosts with compliant pf/netfilter
4897 implementations can redirect TCP connections straight to Tor
4898 without diverting through SOCKS. Needs docs.
4899 - Busy directory servers save lots of memory by spooling server
4900 descriptors, v1 directories, and v2 networkstatus docs to buffers
4901 as needed rather than en masse. Also mmap the cached-routers
4902 files, so we don't need to keep the whole thing in memory too.
4903 - Automatically avoid picking more than one node from the same
4904 /16 network when constructing a circuit.
4905 - Revise and clean up the torrc.sample that we ship with; add
4906 a section for BandwidthRate and BandwidthBurst.
4909 - Split circuit_t into origin_circuit_t and or_circuit_t, and
4910 split connection_t into edge, or, dir, control, and base structs.
4911 These will save quite a bit of memory on busy servers, and they'll
4912 also help us track down bugs in the code and bugs in the spec.
4913 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
4914 or later. Log when we are doing this, so we can diagnose it when
4915 it fails. (Also, recommend libevent 1.1b for kqueue and
4916 win32 methods; deprecate libevent 1.0b harder; make libevent
4917 recommendation system saner.)
4918 - Start being able to build universal binaries on OS X (thanks
4920 - Export the default exit policy via the control port, so controllers
4921 don't need to guess what it is / will be later.
4922 - Add a man page entry for ProtocolWarnings.
4923 - Add TestVia config option to the man page.
4924 - Remove even more protocol-related warnings from Tor server logs,
4925 such as bad TLS handshakes and malformed begin cells.
4926 - Stop fetching descriptors if you're not a dir mirror and you
4927 haven't tried to establish any circuits lately. [This currently
4928 causes some dangerous behavior, because when you start up again
4929 you'll use your ancient server descriptors.]
4930 - New DirPort behavior: if you have your dirport set, you download
4931 descriptors aggressively like a directory mirror, whether or not
4933 - Get rid of the router_retry_connections notion. Now routers
4934 no longer try to rebuild long-term connections to directory
4935 authorities, and directory authorities no longer try to rebuild
4936 long-term connections to all servers. We still don't hang up
4937 connections in these two cases though -- we need to look at it
4938 more carefully to avoid flapping, and we likely need to wait til
4939 0.1.1.x is obsolete.
4940 - Drop compatibility with obsolete Tors that permit create cells
4941 to have the wrong circ_id_type.
4942 - Re-enable per-connection rate limiting. Get rid of the "OP
4943 bandwidth" concept. Lay groundwork for "bandwidth classes" --
4944 separate global buckets that apply depending on what sort of conn
4946 - Start publishing one minute or so after we find our ORPort
4947 to be reachable. This will help reduce the number of descriptors
4948 we have for ourselves floating around, since it's quite likely
4949 other things (e.g. DirPort) will change during that minute too.
4950 - Fork the v1 directory protocol into its own spec document,
4951 and mark dir-spec.txt as the currently correct (v2) spec.
4954 - When we find our DirPort to be reachable, publish a new descriptor
4955 so we'll tell the world (reported by pnx).
4956 - Publish a new descriptor after we hup/reload. This is important
4957 if our config has changed such that we'll want to start advertising
4958 our DirPort now, etc.
4959 - Allow Tor to start when RunAsDaemon is set but no logs are set.
4960 - When we have a state file we cannot parse, tell the user and
4961 move it aside. Now we avoid situations where the user starts
4962 Tor in 1904, Tor writes a state file with that timestamp in it,
4963 the user fixes her clock, and Tor refuses to start.
4964 - Fix configure.in to not produce broken configure files with
4965 more recent versions of autoconf. Thanks to Clint for his auto*
4967 - "tor --verify-config" now exits with -1(255) or 0 depending on
4968 whether the config options are bad or good.
4969 - Resolve bug 321 when using dnsworkers: append a period to every
4970 address we resolve at the exit node, so that we do not accidentally
4971 pick up local addresses, and so that failing searches are retried
4972 in the resolver search domains. (This is already solved for
4973 eventdns.) (This breaks Blossom servers for now.)
4974 - If we are using an exit enclave and we can't connect, e.g. because
4975 its webserver is misconfigured to not listen on localhost, then
4976 back off and try connecting from somewhere else before we fail.
4979 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
4980 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
4981 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
4982 when the IP address is mapped through MapAddress to a hostname.
4983 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
4984 useless IPv6 DNS resolves.
4985 - Patch suggested by Karsten Loesing: respond to SIGNAL command
4986 before we execute the signal, in case the signal shuts us down.
4987 - Clean up AllowInvalidNodes man page entry.
4988 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
4989 - Add more asserts to track down an assert error on a windows Tor
4990 server with connection_add being called with socket == -1.
4991 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
4992 - Fix misleading log messages: an entry guard that is "unlisted",
4993 as well as not known to be "down" (because we've never heard
4994 of it), is not therefore "up".
4995 - Remove code to special-case "-cvs" ending, since it has not
4996 actually mattered since 0.0.9.
4997 - Make our socks5 handling more robust to broken socks clients:
4998 throw out everything waiting on the buffer in between socks
4999 handshake phases, since they can't possibly (so the theory
5000 goes) have predicted what we plan to respond to them.
5003 Changes in version 0.1.1.23 - 2006-07-30
5005 - Fast Tor servers, especially exit nodes, were triggering asserts
5006 due to a bug in handling the list of pending DNS resolves. Some
5007 bugs still remain here; we're hunting them.
5008 - Entry guards could crash clients by sending unexpected input.
5009 - More fixes on reachability testing: if you find yourself reachable,
5010 then don't ever make any client requests (so you stop predicting
5011 circuits), then hup or have your clock jump, then later your IP
5012 changes, you won't think circuits are working, so you won't try to
5013 test reachability, so you won't publish.
5016 - Avoid a crash if the controller does a resetconf firewallports
5017 and then a setconf fascistfirewall=1.
5018 - Avoid an integer underflow when the dir authority decides whether
5019 a router is stable: we might wrongly label it stable, and compute
5020 a slightly wrong median stability, when a descriptor is published
5022 - Fix a place where we might trigger an assert if we can't build our
5023 own server descriptor yet.
5026 Changes in version 0.1.1.22 - 2006-07-05
5028 - Fix a big bug that was causing servers to not find themselves
5029 reachable if they changed IP addresses. Since only 0.1.1.22+
5030 servers can do reachability testing correctly, now we automatically
5031 make sure to test via one of these.
5032 - Fix to allow clients and mirrors to learn directory info from
5033 descriptor downloads that get cut off partway through.
5034 - Directory authorities had a bug in deciding if a newly published
5035 descriptor was novel enough to make everybody want a copy -- a few
5036 servers seem to be publishing new descriptors many times a minute.
5038 - Fix a rare bug that was causing some servers to complain about
5039 "closing wedged cpuworkers" and skip some circuit create requests.
5040 - Make the Exit flag in directory status documents actually work.
5043 Changes in version 0.1.1.21 - 2006-06-10
5044 o Crash and assert fixes from 0.1.1.20:
5045 - Fix a rare crash on Tor servers that have enabled hibernation.
5046 - Fix a seg fault on startup for Tor networks that use only one
5047 directory authority.
5048 - Fix an assert from a race condition that occurs on Tor servers
5049 while exiting, where various threads are trying to log that they're
5050 exiting, and delete the logs, at the same time.
5051 - Make our unit tests pass again on certain obscure platforms.
5054 - Add support for building SUSE RPM packages.
5055 - Speed up initial bootstrapping for clients: if we are making our
5056 first ever connection to any entry guard, then don't mark it down
5058 - When only one Tor server in the network is labelled as a guard,
5059 and we've already picked him, we would cycle endlessly picking him
5060 again, being unhappy about it, etc. Now we specifically exclude
5061 current guards when picking a new guard.
5062 - Servers send create cells more reliably after the TLS connection
5063 is established: we were sometimes forgetting to send half of them
5064 when we had more than one pending.
5065 - If we get a create cell that asks us to extend somewhere, but the
5066 Tor server there doesn't match the expected digest, we now send
5067 a destroy cell back, rather than silently doing nothing.
5068 - Make options->RedirectExit work again.
5069 - Make cookie authentication for the controller work again.
5070 - Stop being picky about unusual characters in the arguments to
5071 mapaddress. It's none of our business.
5072 - Add a new config option "TestVia" that lets you specify preferred
5073 middle hops to use for test circuits. Perhaps this will let me
5074 debug the reachability problems better.
5076 o Log / documentation fixes:
5077 - If we're a server and some peer has a broken TLS certificate, don't
5078 log about it unless ProtocolWarnings is set, i.e., we want to hear
5079 about protocol violations by others.
5080 - Fix spelling of VirtualAddrNetwork in man page.
5081 - Add a better explanation at the top of the autogenerated torrc file
5082 about what happened to our old torrc.
5085 Changes in version 0.1.1.20 - 2006-05-23
5087 - Downgrade a log severity where servers complain that they're
5089 - Avoid a compile warning on FreeBSD.
5090 - Remove string size limit on NEWDESC messages; solve bug 291.
5091 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
5092 more thoroughly when we're running on windows.
5095 Changes in version 0.1.1.19-rc - 2006-05-03
5097 - Regenerate our local descriptor if it's dirty and we try to use
5098 it locally (e.g. if it changes during reachability detection).
5099 - If we setconf our ORPort to 0, we continued to listen on the
5100 old ORPort and receive connections.
5101 - Avoid a second warning about machine/limits.h on Debian
5103 - Be willing to add our own routerinfo into the routerlist.
5104 Now authorities will include themselves in their directories
5105 and network-statuses.
5106 - Stop trying to upload rendezvous descriptors to every
5107 directory authority: only try the v1 authorities.
5108 - Servers no longer complain when they think they're not
5109 registered with the directory authorities. There were too many
5111 - Backport dist-rpm changes so rpms can be built without errors.
5114 - Implement an option, VirtualAddrMask, to set which addresses
5115 get handed out in response to mapaddress requests. This works
5116 around a bug in tsocks where 127.0.0.0/8 is never socksified.
5119 Changes in version 0.1.1.18-rc - 2006-04-10
5121 - Work harder to download live network-statuses from all the
5122 directory authorities we know about. Improve the threshold
5123 decision logic so we're more robust to edge cases.
5124 - When fetching rendezvous descriptors, we were willing to ask
5125 v2 authorities too, which would always return 404.
5128 - Stop listing down or invalid nodes in the v1 directory. This will
5129 reduce its bulk by about 1/3, and reduce load on directory
5131 - When deciding whether a router is Fast or Guard-worthy, consider
5132 his advertised BandwidthRate and not just the BandwidthCapacity.
5133 - No longer ship INSTALL and README files -- they are useless now.
5134 - Force rpmbuild to behave and honor target_cpu.
5135 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
5136 - Start to include translated versions of the tor-doc-*.html
5137 files, along with the screenshots. Still needs more work.
5138 - Start sending back 512 and 451 errors if mapaddress fails,
5139 rather than not sending anything back at all.
5140 - When we fail to bind or listen on an incoming or outgoing
5141 socket, we should close it before failing. otherwise we just
5142 leak it. (thanks to weasel for finding.)
5143 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
5144 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
5145 - Make NoPublish (even though deprecated) work again.
5146 - Fix a minor security flaw where a versioning auth dirserver
5147 could list a recommended version many times in a row to make
5148 clients more convinced that it's recommended.
5149 - Fix crash bug if there are two unregistered servers running
5150 with the same nickname, one of them is down, and you ask for
5151 them by nickname in your EntryNodes or ExitNodes. Also, try
5152 to pick the one that's running rather than an arbitrary one.
5153 - Fix an infinite loop we could hit if we go offline for too long.
5154 - Complain when we hit WSAENOBUFS on recv() or write() too.
5155 Perhaps this will help us hunt the bug.
5156 - If you're not a versioning dirserver, don't put the string
5157 "client-versions \nserver-versions \n" in your network-status.
5158 - Lower the minimum required number of file descriptors to 1000,
5159 so we can have some overhead for Valgrind on Linux, where the
5160 default ulimit -n is 1024.
5163 - Add tor.dizum.com as the fifth authoritative directory server.
5164 - Add a new config option FetchUselessDescriptors, off by default,
5165 for when you plan to run "exitlist" on your client and you want
5166 to know about even the non-running descriptors.
5169 Changes in version 0.1.1.17-rc - 2006-03-28
5171 - Clients and servers since 0.1.1.10-alpha have been expiring
5172 connections whenever they are idle for 5 minutes and they *do*
5173 have circuits on them. Oops. With this new version, clients will
5174 discard their previous entry guard choices and avoid choosing
5175 entry guards running these flawed versions.
5176 - Fix memory leak when uncompressing concatenated zlib streams. This
5177 was causing substantial leaks over time on Tor servers.
5178 - The v1 directory was including servers as much as 48 hours old,
5179 because that's how the new routerlist->routers works. Now only
5180 include them if they're 20 hours old or less.
5183 - Resume building on irix64, netbsd 2.0, etc.
5184 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
5186 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
5187 and it is confusing some users.
5188 - Mirrors stop caching the v1 directory so often.
5189 - Make the max number of old descriptors that a cache will hold
5190 rise with the number of directory authorities, so we can scale.
5191 - Change our win32 uname() hack to be more forgiving about what
5192 win32 versions it thinks it's found.
5195 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
5197 - When the controller's *setconf commands fail, collect an error
5198 message in a string and hand it back to the controller.
5199 - Make the v2 dir's "Fast" flag based on relative capacity, just
5200 like "Stable" is based on median uptime. Name everything in the
5201 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
5202 - Log server fingerprint on startup, so new server operators don't
5203 have to go hunting around their filesystem for it.
5204 - Return a robots.txt on our dirport to discourage google indexing.
5205 - Let the controller ask for GETINFO dir/status/foo so it can ask
5206 directly rather than connecting to the dir port. Only works when
5207 dirport is set for now.
5209 o New config options rather than constants in the code:
5210 - SocksTimeout: How long do we let a socks connection wait
5211 unattached before we fail it?
5212 - CircuitBuildTimeout: Cull non-open circuits that were born
5213 at least this many seconds ago.
5214 - CircuitIdleTimeout: Cull open clean circuits that were born
5215 at least this many seconds ago.
5218 Changes in version 0.1.1.16-rc - 2006-03-18
5219 o Bugfixes on 0.1.1.15-rc:
5220 - Fix assert when the controller asks to attachstream a connect-wait
5221 or resolve-wait stream.
5222 - Now do address rewriting when the controller asks us to attach
5223 to a particular circuit too. This will let Blossom specify
5224 "moria2.exit" without having to learn what moria2's IP address is.
5225 - Make the "tor --verify-config" command-line work again, so people
5226 can automatically check if their torrc will parse.
5227 - Authoritative dirservers no longer require an open connection from
5228 a server to consider him "reachable". We need this change because
5229 when we add new auth dirservers, old servers won't know not to
5231 - Let Tor build on Sun CC again.
5232 - Fix an off-by-one buffer size in dirserv.c that magically never
5233 hit our three authorities but broke sjmurdoch's own tor network.
5234 - If we as a directory mirror don't know of any v1 directory
5235 authorities, then don't try to cache any v1 directories.
5236 - Stop warning about unknown servers in our family when they are
5237 given as hex digests.
5238 - Stop complaining as quickly to the server operator that he
5239 hasn't registered his nickname/key binding.
5240 - Various cleanups so we can add new V2 Auth Dirservers.
5241 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
5242 reflect the updated flags in our v2 dir protocol.
5243 - Resume allowing non-printable characters for exit streams (both
5244 for connecting and for resolving). Now we tolerate applications
5245 that don't follow the RFCs. But continue to block malformed names
5248 o Bugfixes on 0.1.0.x:
5249 - Fix assert bug in close_logs(): when we close and delete logs,
5250 remove them all from the global "logfiles" list.
5251 - Fix minor integer overflow in calculating when we expect to use up
5252 our bandwidth allocation before hibernating.
5253 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
5254 there are multiple SSLs installed with different versions.
5255 - When we try to be a server and Address is not explicitly set and
5256 our hostname resolves to a private IP address, try to use an
5257 interface address if it has a public address. Now Windows machines
5258 that think of themselves as localhost can work by default.
5261 - Let the controller ask for GETINFO dir/server/foo so it can ask
5262 directly rather than connecting to the dir port.
5263 - Let the controller tell us about certain router descriptors
5264 that it doesn't want Tor to use in circuits. Implement
5265 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
5266 - New config option SafeSocks to reject all application connections
5267 using unsafe socks protocols. Defaults to off.
5270 Changes in version 0.1.1.15-rc - 2006-03-11
5271 o Bugfixes and cleanups:
5272 - When we're printing strings from the network, don't try to print
5273 non-printable characters. This protects us against shell escape
5274 sequence exploits, and also against attacks to fool humans into
5275 misreading their logs.
5276 - Fix a bug where Tor would fail to establish any connections if you
5277 left it off for 24 hours and then started it: we were happy with
5278 the obsolete network statuses, but they all referred to router
5279 descriptors that were too old to fetch, so we ended up with no
5280 valid router descriptors.
5281 - Fix a seg fault in the controller's "getinfo orconn-status"
5282 command while listing status on incoming handshaking connections.
5283 Introduce a status name "NEW" for these connections.
5284 - If we get a linelist or linelist_s config option from the torrc
5285 (e.g. ExitPolicy) and it has no value, warn and skip rather than
5286 silently resetting it to its default.
5287 - Don't abandon entry guards until they've been down or gone for
5289 - Cleaner and quieter log messages.
5292 - New controller signal NEWNYM that makes new application requests
5294 - Add a new circuit purpose 'controller' to let the controller ask
5295 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
5296 controller command to let you specify the purpose if you're
5297 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
5298 command to let you change a circuit's purpose after it's been
5300 - Accept "private:*" in routerdesc exit policies; not generated yet
5301 because older Tors do not understand it.
5302 - Add BSD-style contributed startup script "rc.subr" from Peter
5306 Changes in version 0.1.1.14-alpha - 2006-02-20
5307 o Bugfixes on 0.1.1.x:
5308 - Don't die if we ask for a stdout or stderr log (even implicitly)
5309 and we're set to RunAsDaemon -- just warn.
5310 - We still had a few bugs in the OR connection rotation code that
5311 caused directory servers to slowly aggregate connections to other
5312 fast Tor servers. This time for sure!
5313 - Make log entries on Win32 include the name of the function again.
5314 - We were treating a pair of exit policies if they were equal even
5315 if one said accept and the other said reject -- causing us to
5316 not always publish a new descriptor since we thought nothing
5318 - Retry pending server downloads as well as pending networkstatus
5319 downloads when we unexpectedly get a socks request.
5320 - We were ignoring the IS_FAST flag in the directory status,
5321 meaning we were willing to pick trivial-bandwidth nodes for "fast"
5323 - If the controller's SAVECONF command fails (e.g. due to file
5324 permissions), let the controller know that it failed.
5327 - If we're trying to be a Tor server and running Windows 95/98/ME
5328 as a server, explain that we'll likely crash.
5329 - When we're a server, a client asks for an old-style directory,
5330 and our write bucket is empty, don't give it to him. This way
5331 small servers can continue to serve the directory *sometimes*,
5332 without getting overloaded.
5333 - Compress exit policies even more -- look for duplicate lines
5335 - Clients now honor the "guard" flag in the router status when
5336 picking entry guards, rather than looking at is_fast or is_stable.
5337 - Retain unrecognized lines in $DATADIR/state file, so that we can
5338 be forward-compatible.
5339 - Generate 18.0.0.0/8 address policy format in descs when we can;
5340 warn when the mask is not reducible to a bit-prefix.
5341 - Let the user set ControlListenAddress in the torrc. This can be
5342 dangerous, but there are some cases (like a secured LAN) where it
5344 - Split ReachableAddresses into ReachableDirAddresses and
5345 ReachableORAddresses, so we can restrict Dir conns to port 80
5346 and OR conns to port 443.
5347 - Now we can target arch and OS in rpm builds (contributed by
5348 Phobos). Also make the resulting dist-rpm filename match the
5350 - New config options to help controllers: FetchServerDescriptors
5351 and FetchHidServDescriptors for whether to fetch server
5352 info and hidserv info or let the controller do it, and
5353 PublishServerDescriptor and PublishHidServDescriptors.
5354 - Also let the controller set the __AllDirActionsPrivate config
5355 option if you want all directory fetches/publishes to happen via
5356 Tor (it assumes your controller bootstraps your circuits).
5359 Changes in version 0.1.0.17 - 2006-02-17
5360 o Crash bugfixes on 0.1.0.x:
5361 - When servers with a non-zero DirPort came out of hibernation,
5362 sometimes they would trigger an assert.
5364 o Other important bugfixes:
5365 - On platforms that don't have getrlimit (like Windows), we were
5366 artificially constraining ourselves to a max of 1024
5367 connections. Now just assume that we can handle as many as 15000
5368 connections. Hopefully this won't cause other problems.
5370 o Backported features:
5371 - When we're a server, a client asks for an old-style directory,
5372 and our write bucket is empty, don't give it to him. This way
5373 small servers can continue to serve the directory *sometimes*,
5374 without getting overloaded.
5375 - Whenever you get a 503 in response to a directory fetch, try
5376 once more. This will become important once servers start sending
5377 503's whenever they feel busy.
5378 - Fetch a new directory every 120 minutes, not every 40 minutes.
5379 Now that we have hundreds of thousands of users running the old
5380 directory algorithm, it's starting to hurt a lot.
5381 - Bump up the period for forcing a hidden service descriptor upload
5382 from 20 minutes to 1 hour.
5385 Changes in version 0.1.1.13-alpha - 2006-02-09
5386 o Crashes in 0.1.1.x:
5387 - When you tried to setconf ORPort via the controller, Tor would
5388 crash. So people using TorCP to become a server were sad.
5389 - Solve (I hope) the stack-smashing bug that we were seeing on fast
5390 servers. The problem appears to be something do with OpenSSL's
5391 random number generation, or how we call it, or something. Let me
5392 know if the crashes continue.
5393 - Turn crypto hardware acceleration off by default, until we find
5394 somebody smart who can test it for us. (It appears to produce
5395 seg faults in at least some cases.)
5396 - Fix a rare assert error when we've tried all intro points for
5397 a hidden service and we try fetching the service descriptor again:
5398 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
5401 - Fix a major load balance bug: we were round-robining in 16 KB
5402 chunks, and servers with bandwidthrate of 20 KB, while downloading
5403 a 600 KB directory, would starve their other connections. Now we
5404 try to be a bit more fair.
5405 - Dir authorities and mirrors were never expiring the newest
5406 descriptor for each server, causing memory and directory bloat.
5407 - Fix memory-bloating and connection-bloating bug on servers: We
5408 were never closing any connection that had ever had a circuit on
5409 it, because we were checking conn->n_circuits == 0, yet we had a
5410 bug that let it go negative.
5411 - Make Tor work using squid as your http proxy again -- squid
5412 returns an error if you ask for a URL that's too long, and it uses
5413 a really generic error message. Plus, many people are behind a
5414 transparent squid so they don't even realize it.
5415 - On platforms that don't have getrlimit (like Windows), we were
5416 artificially constraining ourselves to a max of 1024
5417 connections. Now just assume that we can handle as many as 15000
5418 connections. Hopefully this won't cause other problems.
5419 - Add a new config option ExitPolicyRejectPrivate which defaults to
5420 1. This means all exit policies will begin with rejecting private
5421 addresses, unless the server operator explicitly turns it off.
5424 - Clients no longer download descriptors for non-running
5426 - Before we add new directory authorities, we should make it
5427 clear that only v1 authorities should receive/publish hidden
5428 service descriptors.
5431 - As soon as we've fetched some more directory info, immediately
5432 try to download more server descriptors. This way we don't have
5433 a 10 second pause during initial bootstrapping.
5434 - Remove even more loud log messages that the server operator can't
5436 - When we're running an obsolete or un-recommended version, make
5437 the log message more clear about what the problem is and what
5438 versions *are* still recommended.
5439 - Provide a more useful warn message when our onion queue gets full:
5440 the CPU is too slow or the exit policy is too liberal.
5441 - Don't warn when we receive a 503 from a dirserver/cache -- this
5442 will pave the way for them being able to refuse if they're busy.
5443 - When we fail to bind a listener, try to provide a more useful
5444 log message: e.g., "Is Tor already running?"
5445 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
5446 Goldberg can prove things about our handshake protocol more
5448 - MaxConn has been obsolete for a while now. Document the ConnLimit
5449 config option, which is a *minimum* number of file descriptors
5450 that must be available else Tor refuses to start.
5451 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
5452 if you log to syslog and want something other than LOG_DAEMON.
5453 - Make dirservers generate a separate "guard" flag to mean,
5454 "would make a good entry guard". Make clients parse it and vote
5455 on it. Not used by clients yet.
5456 - Implement --with-libevent-dir option to ./configure. Also, improve
5457 search techniques to find libevent, and use those for openssl too.
5458 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
5459 - Only start testing reachability once we've established a
5460 circuit. This will make startup on dirservers less noisy.
5461 - Don't try to upload hidden service descriptors until we have
5462 established a circuit.
5463 - Fix the controller's "attachstream 0" command to treat conn like
5464 it just connected, doing address remapping, handling .exit and
5465 .onion idioms, and so on. Now we're more uniform in making sure
5466 that the controller hears about new and closing connections.
5469 Changes in version 0.1.1.12-alpha - 2006-01-11
5470 o Bugfixes on 0.1.1.x:
5471 - The fix to close duplicate server connections was closing all
5472 Tor client connections if they didn't establish a circuit
5473 quickly enough. Oops.
5474 - Fix minor memory issue (double-free) that happened on exit.
5476 o Bugfixes on 0.1.0.x:
5477 - Tor didn't warn when it failed to open a log file.
5480 Changes in version 0.1.1.11-alpha - 2006-01-10
5481 o Crashes in 0.1.1.x:
5482 - Include all the assert/crash fixes from 0.1.0.16.
5483 - If you start Tor and then quit very quickly, there were some
5484 races that tried to free things that weren't allocated yet.
5485 - Fix a rare memory stomp if you're running hidden services.
5486 - Fix segfault when specifying DirServer in config without nickname.
5487 - Fix a seg fault when you finish connecting to a server but at
5488 that moment you dump his server descriptor.
5489 - Extendcircuit and Attachstream controller commands would
5490 assert/crash if you don't give them enough arguments.
5491 - Fix an assert error when we're out of space in the connection_list
5492 and we try to post a hidden service descriptor (reported by weasel).
5493 - If you specify a relative torrc path and you set RunAsDaemon in
5494 your torrc, then it chdir()'s to the new directory. If you HUP,
5495 it tries to load the new torrc location, fails, and exits.
5496 The fix: no longer allow a relative path to torrc using -f.
5499 - Implement "entry guards": automatically choose a handful of entry
5500 nodes and stick with them for all circuits. Only pick new guards
5501 when the ones you have are unsuitable, and if the old guards
5502 become suitable again, switch back. This will increase security
5503 dramatically against certain end-point attacks. The EntryNodes
5504 config option now provides some hints about which entry guards you
5505 want to use most; and StrictEntryNodes means to only use those.
5506 - New directory logic: download by descriptor digest, not by
5507 fingerprint. Caches try to download all listed digests from
5508 authorities; clients try to download "best" digests from caches.
5509 This avoids partitioning and isolating attacks better.
5510 - Make the "stable" router flag in network-status be the median of
5511 the uptimes of running valid servers, and make clients pay
5512 attention to the network-status flags. Thus the cutoff adapts
5513 to the stability of the network as a whole, making IRC, IM, etc
5514 connections more reliable.
5517 - Tor servers with dynamic IP addresses were needing to wait 18
5518 hours before they could start doing reachability testing using
5519 the new IP address and ports. This is because they were using
5520 the internal descriptor to learn what to test, yet they were only
5521 rebuilding the descriptor once they decided they were reachable.
5522 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
5523 to download certain server descriptors, throw them away, and then
5524 fetch them again after 30 minutes. Now mirrors throw away these
5525 server descriptors so clients can't get them.
5526 - We were leaving duplicate connections to other ORs open for a week,
5527 rather than closing them once we detect a duplicate. This only
5528 really affected authdirservers, but it affected them a lot.
5529 - Spread the authdirservers' reachability testing over the entire
5530 testing interval, so we don't try to do 500 TLS's at once every
5534 - If the network is down, and we try to connect to a conn because
5535 we have a circuit in mind, and we timeout (30 seconds) because the
5536 network never answers, we were expiring the circuit, but we weren't
5537 obsoleting the connection or telling the entry_guards functions.
5538 - Some Tor servers process billions of cells per day. These statistics
5539 need to be uint64_t's.
5540 - Check for integer overflows in more places, when adding elements
5541 to smartlists. This could possibly prevent a buffer overflow
5542 on malicious huge inputs. I don't see any, but I haven't looked
5544 - ReachableAddresses kept growing new "reject *:*" lines on every
5546 - When you "setconf log" via the controller, it should remove all
5547 logs. We were automatically adding back in a "log notice stdout".
5548 - Newly bootstrapped Tor networks couldn't establish hidden service
5549 circuits until they had nodes with high uptime. Be more tolerant.
5550 - We were marking servers down when they could not answer every piece
5551 of the directory request we sent them. This was far too harsh.
5552 - Fix the torify (tsocks) config file to not use Tor for localhost
5554 - Directory authorities now go to the proper authority when asking for
5555 a networkstatus, even when they want a compressed one.
5556 - Fix a harmless bug that was causing Tor servers to log
5557 "Got an end because of misc error, but we're not an AP. Closing."
5558 - Authorities were treating their own descriptor changes as cosmetic,
5559 meaning the descriptor available in the network-status and the
5560 descriptor that clients downloaded were different.
5561 - The OS X installer was adding a symlink for tor_resolve but
5562 the binary was called tor-resolve (reported by Thomas Hardly).
5563 - Workaround a problem with some http proxies where they refuse GET
5564 requests that specify "Content-Length: 0" (reported by Adrian).
5565 - Fix wrong log message when you add a "HiddenServiceNodes" config
5566 line without any HiddenServiceDir line (reported by Chris Thomas).
5569 - Write the TorVersion into the state file so we have a prayer of
5570 keeping forward and backward compatibility.
5571 - Revive the FascistFirewall config option rather than eliminating it:
5572 now it's a synonym for ReachableAddresses *:80,*:443.
5573 - Clients choose directory servers from the network status lists,
5574 not from their internal list of router descriptors. Now they can
5575 go to caches directly rather than needing to go to authorities
5577 - Directory authorities ignore router descriptors that have only
5578 cosmetic differences: do this for 0.1.0.x servers now too.
5579 - Add a new flag to network-status indicating whether the server
5580 can answer v2 directory requests too.
5581 - Authdirs now stop whining so loudly about bad descriptors that
5582 they fetch from other dirservers. So when there's a log complaint,
5583 it's for sure from a freshly uploaded descriptor.
5584 - Reduce memory requirements in our structs by changing the order
5586 - There used to be two ways to specify your listening ports in a
5587 server descriptor: on the "router" line and with a separate "ports"
5588 line. Remove support for the "ports" line.
5589 - New config option "AuthDirRejectUnlisted" for auth dirservers as
5590 a panic button: if we get flooded with unusable servers we can
5591 revert to only listing servers in the approved-routers file.
5592 - Auth dir servers can now mark a fingerprint as "!reject" or
5593 "!invalid" in the approved-routers file (as its nickname), to
5594 refuse descriptors outright or include them but marked as invalid.
5595 - Servers store bandwidth history across restarts/crashes.
5596 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
5597 get a better idea of why their circuits failed. Not used yet.
5598 - Directory mirrors now cache up to 16 unrecognized network-status
5599 docs. Now we can add new authdirservers and they'll be cached too.
5600 - When picking a random directory, prefer non-authorities if any
5602 - New controller option "getinfo desc/all-recent" to fetch the
5603 latest server descriptor for every router that Tor knows about.
5606 Changes in version 0.1.0.16 - 2006-01-02
5607 o Crash bugfixes on 0.1.0.x:
5608 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
5609 corrupting the heap, losing FDs, or crashing when we need to resize
5610 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
5611 - It turns out sparc64 platforms crash on unaligned memory access
5612 too -- so detect and avoid this.
5613 - Handle truncated compressed data correctly (by detecting it and
5615 - Fix possible-but-unlikely free(NULL) in control.c.
5616 - When we were closing connections, there was a rare case that
5617 stomped on memory, triggering seg faults and asserts.
5618 - Avoid potential infinite recursion when building a descriptor. (We
5619 don't know that it ever happened, but better to fix it anyway.)
5620 - We were neglecting to unlink marked circuits from soon-to-close OR
5621 connections, which caused some rare scribbling on freed memory.
5622 - Fix a memory stomping race bug when closing the joining point of two
5623 rendezvous circuits.
5624 - Fix an assert in time parsing found by Steven Murdoch.
5626 o Other bugfixes on 0.1.0.x:
5627 - When we're doing reachability testing, provide more useful log
5628 messages so the operator knows what to expect.
5629 - Do not check whether DirPort is reachable when we are suppressing
5630 advertising it because of hibernation.
5631 - When building with -static or on Solaris, we sometimes needed -ldl.
5632 - When we're deciding whether a stream has enough circuits around
5633 that can handle it, count the freshly dirty ones and not the ones
5634 that are so dirty they won't be able to handle it.
5635 - When we're expiring old circuits, we had a logic error that caused
5636 us to close new rendezvous circuits rather than old ones.
5637 - Give a more helpful log message when you try to change ORPort via
5638 the controller: you should upgrade Tor if you want that to work.
5639 - We were failing to parse Tor versions that start with "Tor ".
5640 - Tolerate faulty streams better: when a stream fails for reason
5641 exitpolicy, stop assuming that the router is lying about his exit
5642 policy. When a stream fails for reason misc, allow it to retry just
5643 as if it was resolvefailed. When a stream has failed three times,
5644 reset its failure count so we can try again and get all three tries.
5647 Changes in version 0.1.1.10-alpha - 2005-12-11
5648 o Correctness bugfixes on 0.1.0.x:
5649 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
5650 corrupting the heap, losing FDs, or crashing when we need to resize
5651 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
5652 - Stop doing the complex voodoo overkill checking for insecure
5653 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
5654 - When we were closing connections, there was a rare case that
5655 stomped on memory, triggering seg faults and asserts.
5656 - We were neglecting to unlink marked circuits from soon-to-close OR
5657 connections, which caused some rare scribbling on freed memory.
5658 - When we're deciding whether a stream has enough circuits around
5659 that can handle it, count the freshly dirty ones and not the ones
5660 that are so dirty they won't be able to handle it.
5661 - Recover better from TCP connections to Tor servers that are
5662 broken but don't tell you (it happens!); and rotate TLS
5663 connections once a week.
5664 - When we're expiring old circuits, we had a logic error that caused
5665 us to close new rendezvous circuits rather than old ones.
5666 - Fix a scary-looking but apparently harmless bug where circuits
5667 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
5668 servers, and never switch to state CIRCUIT_STATE_OPEN.
5669 - When building with -static or on Solaris, we sometimes needed to
5671 - Give a useful message when people run Tor as the wrong user,
5672 rather than telling them to start chowning random directories.
5673 - We were failing to inform the controller about new .onion streams.
5675 o Security bugfixes on 0.1.0.x:
5676 - Refuse server descriptors if the fingerprint line doesn't match
5677 the included identity key. Tor doesn't care, but other apps (and
5678 humans) might actually be trusting the fingerprint line.
5679 - We used to kill the circuit when we receive a relay command we
5680 don't recognize. Now we just drop it.
5681 - Start obeying our firewall options more rigorously:
5682 . If we can't get to a dirserver directly, try going via Tor.
5683 . Don't ever try to connect (as a client) to a place our
5684 firewall options forbid.
5685 . If we specify a proxy and also firewall options, obey the
5686 firewall options even when we're using the proxy: some proxies
5687 can only proxy to certain destinations.
5688 - Fix a bug found by Lasse Overlier: when we were making internal
5689 circuits (intended to be cannibalized later for rendezvous and
5690 introduction circuits), we were picking them so that they had
5691 useful exit nodes. There was no need for this, and it actually
5692 aids some statistical attacks.
5693 - Start treating internal circuits and exit circuits separately.
5694 It's important to keep them separate because internal circuits
5695 have their last hops picked like middle hops, rather than like
5696 exit hops. So exiting on them will break the user's expectations.
5698 o Bugfixes on 0.1.1.x:
5699 - Take out the mis-feature where we tried to detect IP address
5700 flapping for people with DynDNS, and chose not to upload a new
5701 server descriptor sometimes.
5702 - Try to be compatible with OpenSSL 0.9.6 again.
5703 - Log fix: when the controller is logging about .onion addresses,
5704 sometimes it didn't include the ".onion" part of the address.
5705 - Don't try to modify options->DirServers internally -- if the
5706 user didn't specify any, just add the default ones directly to
5707 the trusted dirserver list. This fixes a bug where people running
5708 controllers would use SETCONF on some totally unrelated config
5709 option, and Tor would start yelling at them about changing their
5711 - Let the controller's redirectstream command specify a port, in
5712 case the controller wants to change that too.
5713 - When we requested a pile of server descriptors, we sometimes
5714 accidentally launched a duplicate request for the first one.
5715 - Bugfix for trackhostexits: write down the fingerprint of the
5716 chosen exit, not its nickname, because the chosen exit might not
5718 - When parsing foo.exit, if foo is unknown, and we are leaving
5719 circuits unattached, set the chosen_exit field and leave the
5720 address empty. This matters because controllers got confused
5722 - Directory authorities no longer try to download server
5723 descriptors that they know they will reject.
5725 o Features and updates:
5726 - Replace balanced trees with hash tables: this should make stuff
5727 significantly faster.
5728 - Resume using the AES counter-mode implementation that we ship,
5729 rather than OpenSSL's. Ours is significantly faster.
5730 - Many other CPU and memory improvements.
5731 - Add a new config option FastFirstHopPK (on by default) so clients
5732 do a trivial crypto handshake for their first hop, since TLS has
5733 already taken care of confidentiality and authentication.
5734 - Add a new config option TestSocks so people can see if their
5735 applications are using socks4, socks4a, socks5-with-ip, or
5736 socks5-with-hostname. This way they don't have to keep mucking
5737 with tcpdump and wondering if something got cached somewhere.
5738 - Warn when listening on a public address for socks. I suspect a
5739 lot of people are setting themselves up as open socks proxies,
5740 and they have no idea that jerks on the Internet are using them,
5741 since they simply proxy the traffic into the Tor network.
5742 - Add "private:*" as an alias in configuration for policies. Now
5743 you can simplify your exit policy rather than needing to list
5744 every single internal or nonroutable network space.
5745 - Add a new controller event type that allows controllers to get
5746 all server descriptors that were uploaded to a router in its role
5747 as authoritative dirserver.
5748 - Start shipping socks-extensions.txt, tor-doc-unix.html,
5749 tor-doc-server.html, and stylesheet.css in the tarball.
5750 - Stop shipping tor-doc.html in the tarball.
5753 Changes in version 0.1.1.9-alpha - 2005-11-15
5754 o Usability improvements:
5755 - Start calling it FooListenAddress rather than FooBindAddress,
5756 since few of our users know what it means to bind an address
5758 - Reduce clutter in server logs. We're going to try to make
5759 them actually usable now. New config option ProtocolWarnings that
5760 lets you hear about how _other Tors_ are breaking the protocol. Off
5762 - Divide log messages into logging domains. Once we put some sort
5763 of interface on this, it will let people looking at more verbose
5764 log levels specify the topics they want to hear more about.
5765 - Make directory servers return better http 404 error messages
5766 instead of a generic "Servers unavailable".
5767 - Check for even more Windows version flags when writing the platform
5768 string in server descriptors, and note any we don't recognize.
5769 - Clean up more of the OpenSSL memory when exiting, so we can detect
5770 memory leaks better.
5771 - Make directory authorities be non-versioning, non-naming by
5772 default. Now we can add new directory servers without requiring
5773 their operators to pay close attention.
5774 - When logging via syslog, include the pid whenever we provide
5775 a log entry. Suggested by Todd Fries.
5777 o Performance improvements:
5778 - Directory servers now silently throw away new descriptors that
5779 haven't changed much if the timestamps are similar. We do this to
5780 tolerate older Tor servers that upload a new descriptor every 15
5781 minutes. (It seemed like a good idea at the time.)
5782 - Inline bottleneck smartlist functions; use fast versions by default.
5783 - Add a "Map from digest to void*" abstraction digestmap_t so we
5784 can do less hex encoding/decoding. Use it in router_get_by_digest()
5785 to resolve a performance bottleneck.
5786 - Allow tor_gzip_uncompress to extract as much as possible from
5787 truncated compressed data. Try to extract as many
5788 descriptors as possible from truncated http responses (when
5789 DIR_PURPOSE_FETCH_ROUTERDESC).
5790 - Make circ->onionskin a pointer, not a static array. moria2 was using
5791 125000 circuit_t's after it had been up for a few weeks, which
5792 translates to 20+ megs of wasted space.
5793 - The private half of our EDH handshake keys are now chosen out
5794 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
5796 o Security improvements:
5797 - Start making directory caches retain old routerinfos, so soon
5798 clients can start asking by digest of descriptor rather than by
5799 fingerprint of server.
5800 - Add half our entropy from RAND_poll in OpenSSL. This knows how
5801 to use egd (if present), openbsd weirdness (if present), vms/os2
5802 weirdness (if we ever port there), and more in the future.
5804 o Bugfixes on 0.1.0.x:
5805 - Do round-robin writes of at most 16 kB per write. This might be
5806 more fair on loaded Tor servers, and it might resolve our Windows
5807 crash bug. It might also slow things down.
5808 - Our TLS handshakes were generating a single public/private
5809 keypair for the TLS context, rather than making a new one for
5810 each new connections. Oops. (But we were still rotating them
5811 periodically, so it's not so bad.)
5812 - When we were cannibalizing a circuit with a particular exit
5813 node in mind, we weren't checking to see if that exit node was
5814 already present earlier in the circuit. Oops.
5815 - When a Tor server's IP changes (e.g. from a dyndns address),
5816 upload a new descriptor so clients will learn too.
5817 - Really busy servers were keeping enough circuits open on stable
5818 connections that they were wrapping around the circuit_id
5819 space. (It's only two bytes.) This exposed a bug where we would
5820 feel free to reuse a circuit_id even if it still exists but has
5821 been marked for close. Try to fix this bug. Some bug remains.
5822 - If we would close a stream early (e.g. it asks for a .exit that
5823 we know would refuse it) but the LeaveStreamsUnattached config
5824 option is set by the controller, then don't close it.
5826 o Bugfixes on 0.1.1.8-alpha:
5827 - Fix a big pile of memory leaks, some of them serious.
5828 - Do not try to download a routerdesc if we would immediately reject
5830 - Resume inserting a newline between all router descriptors when
5831 generating (old style) signed directories, since our spec says
5833 - When providing content-type application/octet-stream for
5834 server descriptors using .z, we were leaving out the
5835 content-encoding header. Oops. (Everything tolerated this just
5836 fine, but that doesn't mean we need to be part of the problem.)
5837 - Fix a potential seg fault in getconf and getinfo using version 1
5838 of the controller protocol.
5839 - Avoid crash: do not check whether DirPort is reachable when we
5840 are suppressing it because of hibernation.
5841 - Make --hash-password not crash on exit.
5844 Changes in version 0.1.1.8-alpha - 2005-10-07
5845 o New features (major):
5846 - Clients don't download or use the directory anymore. Now they
5847 download and use network-statuses from the trusted dirservers,
5848 and fetch individual server descriptors as needed from mirrors.
5849 See dir-spec.txt for all the gory details.
5850 - Be more conservative about whether to advertise our DirPort.
5851 The main change is to not advertise if we're running at capacity
5852 and either a) we could hibernate or b) our capacity is low and
5853 we're using a default DirPort.
5854 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
5856 o New features (minor):
5857 - Try to be smart about when to retry network-status and
5858 server-descriptor fetches. Still needs some tuning.
5859 - Stop parsing, storing, or using running-routers output (but
5860 mirrors still cache and serve it).
5861 - Consider a threshold of versioning dirservers (dirservers who have
5862 an opinion about which Tor versions are still recommended) before
5863 deciding whether to warn the user that he's obsolete.
5864 - Dirservers can now reject/invalidate by key and IP, with the
5865 config options "AuthDirInvalid" and "AuthDirReject". This is
5866 useful since currently we automatically list servers as running
5867 and usable even if we know they're jerks.
5868 - Provide dire warnings to any users who set DirServer; move it out
5869 of torrc.sample and into torrc.complete.
5870 - Add MyFamily to torrc.sample in the server section.
5871 - Add nicknames to the DirServer line, so we can refer to them
5872 without requiring all our users to memorize their IP addresses.
5873 - When we get an EOF or a timeout on a directory connection, note
5874 how many bytes of serverdesc we are dropping. This will help
5875 us determine whether it is smart to parse incomplete serverdesc
5877 - Add a new function to "change pseudonyms" -- that is, to stop
5878 using any currently-dirty circuits for new streams, so we don't
5879 link new actions to old actions. Currently it's only called on
5880 HUP (or SIGNAL RELOAD).
5881 - On sighup, if UseHelperNodes changed to 1, use new circuits.
5882 - Start using RAND_bytes rather than RAND_pseudo_bytes from
5883 OpenSSL. Also, reseed our entropy every hour, not just at
5884 startup. And entropy in 512-bit chunks, not 160-bit chunks.
5886 o Fixes on 0.1.1.7-alpha:
5887 - Nobody ever implemented EVENT_ADDRMAP for control protocol
5888 version 0, so don't let version 0 controllers ask for it.
5889 - If you requested something with too many newlines via the
5890 v1 controller protocol, you could crash tor.
5891 - Fix a number of memory leaks, including some pretty serious ones.
5892 - Re-enable DirPort testing again, so Tor servers will be willing
5893 to advertise their DirPort if it's reachable.
5894 - On TLS handshake, only check the other router's nickname against
5895 its expected nickname if is_named is set.
5897 o Fixes forward-ported from 0.1.0.15:
5898 - Don't crash when we don't have any spare file descriptors and we
5899 try to spawn a dns or cpu worker.
5900 - Make the numbers in read-history and write-history into uint64s,
5901 so they don't overflow and publish negatives in the descriptor.
5904 - For the OS X package's modified privoxy config file, comment
5905 out the "logfile" line so we don't log everything passed
5907 - We were whining about using socks4 or socks5-with-local-lookup
5908 even when it's an IP in the "virtual" range we designed exactly
5910 - We were leaking some memory every time the client changes IPs.
5911 - Never call free() on tor_malloc()d memory. This will help us
5912 use dmalloc to detect memory leaks.
5913 - Check for named servers when looking them up by nickname;
5914 warn when we'recalling a non-named server by its nickname;
5915 don't warn twice about the same name.
5916 - Try to list MyFamily elements by key, not by nickname, and warn
5917 if we've not heard of the server.
5918 - Make windows platform detection (uname equivalent) smarter.
5919 - It turns out sparc64 doesn't like unaligned access either.
5922 Changes in version 0.1.0.15 - 2005-09-23
5923 o Bugfixes on 0.1.0.x:
5924 - Reject ports 465 and 587 (spam targets) in default exit policy.
5925 - Don't crash when we don't have any spare file descriptors and we
5926 try to spawn a dns or cpu worker.
5927 - Get rid of IgnoreVersion undocumented config option, and make us
5928 only warn, never exit, when we're running an obsolete version.
5929 - Don't try to print a null string when your server finds itself to
5930 be unreachable and the Address config option is empty.
5931 - Make the numbers in read-history and write-history into uint64s,
5932 so they don't overflow and publish negatives in the descriptor.
5933 - Fix a minor memory leak in smartlist_string_remove().
5934 - We were only allowing ourselves to upload a server descriptor at
5935 most every 20 minutes, even if it changed earlier than that.
5936 - Clean up log entries that pointed to old URLs.
5939 Changes in version 0.1.1.7-alpha - 2005-09-14
5940 o Fixes on 0.1.1.6-alpha:
5941 - Exit servers were crashing when people asked them to make a
5942 connection to an address not in their exit policy.
5943 - Looking up a non-existent stream for a v1 control connection would
5945 - Fix a seg fault if we ask a dirserver for a descriptor by
5946 fingerprint but he doesn't know about him.
5947 - SETCONF was appending items to linelists, not clearing them.
5948 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
5949 out and refuse the setconf if it would fail.
5950 - Downgrade the dirserver log messages when whining about
5954 - Add Peter Palfrader's check-tor script to tor/contrib/
5955 It lets you easily check whether a given server (referenced by
5956 nickname) is reachable by you.
5957 - Numerous changes to move towards client-side v2 directories. Not
5961 - If the user gave tor an odd number of command-line arguments,
5962 we were silently ignoring the last one. Now we complain and fail.
5963 [This wins the oldest-bug prize -- this bug has been present since
5964 November 2002, as released in Tor 0.0.0.]
5965 - Do not use unaligned memory access on alpha, mips, or mipsel.
5966 It *works*, but is very slow, so we treat them as if it doesn't.
5967 - Retry directory requests if we fail to get an answer we like
5968 from a given dirserver (we were retrying before, but only if
5969 we fail to connect).
5970 - When writing the RecommendedVersions line, sort them first.
5971 - When the client asked for a rendezvous port that the hidden
5972 service didn't want to provide, we were sending an IP address
5973 back along with the end cell. Fortunately, it was zero. But stop
5975 - Correct "your server is reachable" log entries to indicate that
5976 it was self-testing that told us so.
5979 Changes in version 0.1.1.6-alpha - 2005-09-09
5980 o Fixes on 0.1.1.5-alpha:
5981 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
5982 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
5983 - Fix bug with tor_memmem finding a match at the end of the string.
5984 - Make unit tests run without segfaulting.
5985 - Resolve some solaris x86 compile warnings.
5986 - Handle duplicate lines in approved-routers files without warning.
5987 - Fix bug where as soon as a server refused any requests due to his
5988 exit policy (e.g. when we ask for localhost and he tells us that's
5989 127.0.0.1 and he won't do it), we decided he wasn't obeying his
5990 exit policy using him for any exits.
5991 - Only do openssl hardware accelerator stuff if openssl version is
5994 o New controller features/fixes:
5995 - Add a "RESETCONF" command so you can set config options like
5996 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
5997 a config option in the torrc with no value, then it clears it
5998 entirely (rather than setting it to its default).
5999 - Add a "GETINFO config-file" to tell us where torrc is.
6000 - Avoid sending blank lines when GETINFO replies should be empty.
6001 - Add a QUIT command for the controller (for using it manually).
6002 - Fix a bug in SAVECONF that was adding default dirservers and
6003 other redundant entries to the torrc file.
6005 o Start on the new directory design:
6006 - Generate, publish, cache, serve new network-status format.
6007 - Publish individual descriptors (by fingerprint, by "all", and by
6009 - Publish client and server recommended versions separately.
6010 - Allow tor_gzip_uncompress() to handle multiple concatenated
6011 compressed strings. Serve compressed groups of router
6012 descriptors. The compression logic here could be more
6014 - Distinguish v1 authorities (all currently trusted directories)
6015 from v2 authorities (all trusted directories).
6016 - Change DirServers config line to note which dirs are v1 authorities.
6017 - Add configuration option "V1AuthoritativeDirectory 1" which
6018 moria1, moria2, and tor26 should set.
6019 - Remove option when getting directory cache to see whether they
6020 support running-routers; they all do now. Replace it with one
6021 to see whether caches support v2 stuff.
6024 - Dirservers now do their own external reachability testing of each
6025 Tor server, and only list them as running if they've been found to
6026 be reachable. We also send back warnings to the server's logs if
6027 it uploads a descriptor that we already believe is unreachable.
6028 - Implement exit enclaves: if we know an IP address for the
6029 destination, and there's a running Tor server at that address
6030 which allows exit to the destination, then extend the circuit to
6031 that exit first. This provides end-to-end encryption and end-to-end
6032 authentication. Also, if the user wants a .exit address or enclave,
6033 use 4 hops rather than 3, and cannibalize a general circ for it
6035 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
6036 controller. Also, rotate dns and cpu workers if the controller
6037 changes options that will affect them; and initialize the dns
6038 worker cache tree whether or not we start out as a server.
6039 - Only upload a new server descriptor when options change, 18
6040 hours have passed, uptime is reset, or bandwidth changes a lot.
6041 - Check [X-]Forwarded-For headers in HTTP requests when generating
6042 log messages. This lets people run dirservers (and caches) behind
6043 Apache but still know which IP addresses are causing warnings.
6045 o Config option changes:
6046 - Replace (Fascist)Firewall* config options with a new
6047 ReachableAddresses option that understands address policies.
6048 For example, "ReachableAddresses *:80,*:443"
6049 - Get rid of IgnoreVersion undocumented config option, and make us
6050 only warn, never exit, when we're running an obsolete version.
6051 - Make MonthlyAccountingStart config option truly obsolete now.
6054 - Reject ports 465 and 587 in the default exit policy, since
6055 people have started using them for spam too.
6056 - It turns out we couldn't bootstrap a network since we added
6057 reachability detection in 0.1.0.1-rc. Good thing the Tor network
6058 has never gone down. Add an AssumeReachable config option to let
6059 servers and dirservers bootstrap. When we're trying to build a
6060 high-uptime or high-bandwidth circuit but there aren't enough
6061 suitable servers, try being less picky rather than simply failing.
6062 - Our logic to decide if the OR we connected to was the right guy
6063 was brittle and maybe open to a mitm for unverified routers.
6064 - We weren't cannibalizing circuits correctly for
6065 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
6066 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
6067 build those from scratch. This should make hidden services faster.
6068 - Predict required circuits better, with an eye toward making hidden
6069 services faster on the service end.
6070 - Retry streams if the exit node sends back a 'misc' failure. This
6071 should result in fewer random failures. Also, after failing
6072 from resolve failed or misc, reset the num failures, so we give
6073 it a fair shake next time we try.
6074 - Clean up the rendezvous warn log msgs, and downgrade some to info.
6075 - Reduce severity on logs about dns worker spawning and culling.
6076 - When we're shutting down and we do something like try to post a
6077 server descriptor or rendezvous descriptor, don't complain that
6078 we seem to be unreachable. Of course we are, we're shutting down.
6079 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
6080 We don't use them yet, but maybe one day our DNS resolver will be
6081 able to discover them.
6082 - Make ContactInfo mandatory for authoritative directory servers.
6083 - Require server descriptors to list IPv4 addresses -- hostnames
6084 are no longer allowed. This also fixes some potential security
6085 problems with people providing hostnames as their address and then
6086 preferentially resolving them to partition users.
6087 - Change log line for unreachability to explicitly suggest /etc/hosts
6088 as the culprit. Also make it clearer what IP address and ports we're
6089 testing for reachability.
6090 - Put quotes around user-supplied strings when logging so users are
6091 more likely to realize if they add bad characters (like quotes)
6093 - Let auth dir servers start without specifying an Address config
6095 - Make unit tests (and other invocations that aren't the real Tor)
6096 run without launching listeners, creating subdirectories, and so on.
6099 Changes in version 0.1.1.5-alpha - 2005-08-08
6100 o Bugfixes included in 0.1.0.14.
6102 o Bugfixes on 0.1.0.x:
6103 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
6104 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
6105 it would silently using ignore the 6668.
6108 Changes in version 0.1.0.14 - 2005-08-08
6109 o Bugfixes on 0.1.0.x:
6110 - Fix the other half of the bug with crypto handshakes
6112 - Fix an assert trigger if you send a 'signal term' via the
6113 controller when it's listening for 'event info' messages.
6116 Changes in version 0.1.1.4-alpha - 2005-08-04
6117 o Bugfixes included in 0.1.0.13.
6120 - Improve tor_gettimeofday() granularity on windows.
6121 - Make clients regenerate their keys when their IP address changes.
6122 - Implement some more GETINFO goodness: expose helper nodes, config
6123 options, getinfo keys.
6126 Changes in version 0.1.0.13 - 2005-08-04
6127 o Bugfixes on 0.1.0.x:
6128 - Fix a critical bug in the security of our crypto handshakes.
6129 - Fix a size_t underflow in smartlist_join_strings2() that made
6130 it do bad things when you hand it an empty smartlist.
6131 - Fix Windows installer to ship Tor license (thanks to Aphex for
6132 pointing out this oversight) and put a link to the doc directory
6134 - Explicitly set no-unaligned-access for sparc: it turns out the
6135 new gcc's let you compile broken code, but that doesn't make it
6139 Changes in version 0.1.1.3-alpha - 2005-07-23
6140 o Bugfixes on 0.1.1.2-alpha:
6141 - Fix a bug in handling the controller's "post descriptor"
6143 - Fix several bugs in handling the controller's "extend circuit"
6145 - Fix a bug in handling the controller's "stream status" event.
6146 - Fix an assert failure if we have a controller listening for
6147 circuit events and we go offline.
6148 - Re-allow hidden service descriptors to publish 0 intro points.
6149 - Fix a crash when generating your hidden service descriptor if
6150 you don't have enough intro points already.
6152 o New features on 0.1.1.2-alpha:
6153 - New controller function "getinfo accounting", to ask how
6154 many bytes we've used in this time period.
6155 - Experimental support for helper nodes: a lot of the risk from
6156 a small static adversary comes because users pick new random
6157 nodes every time they rebuild a circuit. Now users will try to
6158 stick to the same small set of entry nodes if they can. Not
6159 enabled by default yet.
6161 o Bugfixes on 0.1.0.12:
6162 - If you're an auth dir server, always publish your dirport,
6163 even if you haven't yet found yourself to be reachable.
6164 - Fix a size_t underflow in smartlist_join_strings2() that made
6165 it do bad things when you hand it an empty smartlist.
6168 Changes in version 0.1.0.12 - 2005-07-18
6169 o New directory servers:
6170 - tor26 has changed IP address.
6172 o Bugfixes on 0.1.0.x:
6173 - Fix a possible double-free in tor_gzip_uncompress().
6174 - When --disable-threads is set, do not search for or link against
6176 - Don't trigger an assert if an authoritative directory server
6177 claims its dirport is 0.
6178 - Fix bug with removing Tor as an NT service: some people were
6179 getting "The service did not return an error." Thanks to Matt
6183 Changes in version 0.1.1.2-alpha - 2005-07-15
6184 o New directory servers:
6185 - tor26 has changed IP address.
6187 o Bugfixes on 0.1.0.x, crashes/leaks:
6188 - Port the servers-not-obeying-their-exit-policies fix from
6190 - Fix an fd leak in start_daemon().
6191 - On Windows, you can't always reopen a port right after you've
6192 closed it. So change retry_listeners() to only close and re-open
6193 ports that have changed.
6194 - Fix a possible double-free in tor_gzip_uncompress().
6196 o Bugfixes on 0.1.0.x, usability:
6197 - When tor_socketpair() fails in Windows, give a reasonable
6198 Windows-style errno back.
6199 - Let people type "tor --install" as well as "tor -install" when
6201 want to make it an NT service.
6202 - NT service patch from Matt Edman to improve error messages.
6203 - When the controller asks for a config option with an abbreviated
6204 name, give the full name in our response.
6205 - Correct the man page entry on TrackHostExitsExpire.
6206 - Looks like we were never delivering deflated (i.e. compressed)
6207 running-routers lists, even when asked. Oops.
6208 - When --disable-threads is set, do not search for or link against
6211 o Bugfixes on 0.1.1.x:
6212 - Fix a seg fault with autodetecting which controller version is
6216 - New hidden service descriptor format: put a version in it, and
6217 let people specify introduction/rendezvous points that aren't
6218 in "the directory" (which is subjective anyway).
6219 - Allow the DEBUG controller event to work again. Mark certain log
6220 entries as "don't tell this to controllers", so we avoid cycles.
6223 Changes in version 0.1.0.11 - 2005-06-30
6224 o Bugfixes on 0.1.0.x:
6225 - Fix major security bug: servers were disregarding their
6226 exit policies if clients behaved unexpectedly.
6227 - Make OS X init script check for missing argument, so we don't
6228 confuse users who invoke it incorrectly.
6229 - Fix a seg fault in "tor --hash-password foo".
6230 - The MAPADDRESS control command was broken.
6233 Changes in version 0.1.1.1-alpha - 2005-06-29
6235 - Make OS X init script check for missing argument, so we don't
6236 confuse users who invoke it incorrectly.
6237 - Fix a seg fault in "tor --hash-password foo".
6238 - Fix a possible way to DoS dirservers.
6239 - When we complain that your exit policy implicitly allows local or
6240 private address spaces, name them explicitly so operators can
6242 - Make the log message less scary when all the dirservers are
6243 temporarily unreachable.
6244 - We were printing the number of idle dns workers incorrectly when
6248 - Revised controller protocol (version 1) that uses ascii rather
6249 than binary. Add supporting libraries in python and java so you
6250 can use the controller from your applications without caring how
6252 - Spiffy new support for crypto hardware accelerators. Can somebody
6256 Changes in version 0.0.9.10 - 2005-06-16
6257 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
6258 - Refuse relay cells that claim to have a length larger than the
6259 maximum allowed. This prevents a potential attack that could read
6260 arbitrary memory (e.g. keys) from an exit server's process
6264 Changes in version 0.1.0.10 - 2005-06-14
6265 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
6266 libevent before 1.1a.
6269 Changes in version 0.1.0.9-rc - 2005-06-09
6271 - Reset buf->highwater every time buf_shrink() is called, not just on
6272 a successful shrink. This was causing significant memory bloat.
6273 - Fix buffer overflow when checking hashed passwords.
6274 - Security fix: if seeding the RNG on Win32 fails, quit.
6275 - Allow seeding the RNG on Win32 even when you're not running as
6277 - Disable threading on Solaris too. Something is wonky with it,
6278 cpuworkers, and reentrant libs.
6279 - Reenable the part of the code that tries to flush as soon as an
6280 OR outbuf has a full TLS record available. Perhaps this will make
6281 OR outbufs not grow as huge except in rare cases, thus saving lots
6282 of CPU time plus memory.
6283 - Reject malformed .onion addresses rather then passing them on as
6284 normal web requests.
6285 - Adapt patch from Adam Langley: fix possible memory leak in
6286 tor_lookup_hostname().
6287 - Initialize libevent later in the startup process, so the logs are
6288 already established by the time we start logging libevent warns.
6289 - Use correct errno on win32 if libevent fails.
6290 - Check and warn about known-bad/slow libevent versions.
6291 - Pay more attention to the ClientOnly config option.
6292 - Have torctl.in/tor.sh.in check for location of su binary (needed
6294 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
6295 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
6296 HttpProxyAuthenticator
6297 - Stop warning about sigpipes in the logs. We're going to
6298 pretend that getting these occassionally is normal and fine.
6299 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
6301 installer screens; and don't put stuff into StartupItems unless
6302 the user asks you to.
6303 - Require servers that use the default dirservers to have public IP
6304 addresses. We have too many servers that are configured with private
6305 IPs and their admins never notice the log entries complaining that
6306 their descriptors are being rejected.
6307 - Add OSX uninstall instructions. An actual uninstall script will
6311 Changes in version 0.1.0.8-rc - 2005-05-23
6313 - It turns out that kqueue on OS X 10.3.9 was causing kernel
6314 panics. Disable kqueue on all OS X Tors.
6315 - Fix RPM: remove duplicate line accidentally added to the rpm
6317 - Disable threads on openbsd too, since its gethostaddr is not
6319 - Tolerate libevent 0.8 since it still works, even though it's
6321 - Enable building on Red Hat 9.0 again.
6322 - Allow the middle hop of the testing circuit to be running any
6323 version, now that most of them have the bugfix to let them connect
6324 to unknown servers. This will allow reachability testing to work
6325 even when 0.0.9.7-0.0.9.9 become obsolete.
6326 - Handle relay cells with rh.length too large. This prevents
6327 a potential attack that could read arbitrary memory (maybe even
6328 keys) from the exit server's process.
6329 - We screwed up the dirport reachability testing when we don't yet
6330 have a cached version of the directory. Hopefully now fixed.
6331 - Clean up router_load_single_router() (used by the controller),
6332 so it doesn't seg fault on error.
6333 - Fix a minor memory leak when somebody establishes an introduction
6334 point at your Tor server.
6335 - If a socks connection ends because read fails, don't warn that
6336 you're not sending a socks reply back.
6339 - Add HttpProxyAuthenticator config option too, that works like
6340 the HttpsProxyAuthenticator config option.
6341 - Encode hashed controller passwords in hex instead of base64,
6342 to make it easier to write controllers.
6345 Changes in version 0.1.0.7-rc - 2005-05-17
6347 - Fix a bug in the OS X package installer that prevented it from
6348 installing on Tiger.
6349 - Fix a script bug in the OS X package installer that made it
6350 complain during installation.
6351 - Find libevent even if it's hiding in /usr/local/ and your
6352 CFLAGS and LDFLAGS don't tell you to look there.
6353 - Be able to link with libevent as a shared library (the default
6354 after 1.0d), even if it's hiding in /usr/local/lib and even
6355 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
6356 assuming you're running gcc. Otherwise fail and give a useful
6358 - Fix a bug in the RPM packager: set home directory for _tor to
6359 something more reasonable when first installing.
6360 - Free a minor amount of memory that is still reachable on exit.
6363 Changes in version 0.1.0.6-rc - 2005-05-14
6365 - Implement --disable-threads configure option. Disable threads on
6366 netbsd by default, because it appears to have no reentrant resolver
6368 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
6369 release (1.1) detects and disables kqueue if it's broken.
6370 - Append default exit policy before checking for implicit internal
6371 addresses. Now we don't log a bunch of complaints on startup
6372 when using the default exit policy.
6373 - Some people were putting "Address " in their torrc, and they had
6374 a buggy resolver that resolved " " to 0.0.0.0. Oops.
6375 - If DataDir is ~/.tor, and that expands to /.tor, then default to
6376 LOCALSTATEDIR/tor instead.
6377 - Fix fragmented-message bug in TorControl.py.
6378 - Resolve a minor bug which would prevent unreachable dirports
6379 from getting suppressed in the published descriptor.
6380 - When the controller gave us a new descriptor, we weren't resolving
6381 it immediately, so Tor would think its address was 0.0.0.0 until
6382 we fetched a new directory.
6383 - Fix an uppercase/lowercase case error in suppressing a bogus
6384 libevent warning on some Linuxes.
6387 - Begin scrubbing sensitive strings from logs by default. Turn off
6388 the config option SafeLogging if you need to do debugging.
6389 - Switch to a new buffer management algorithm, which tries to avoid
6390 reallocing and copying quite as much. In first tests it looks like
6391 it uses *more* memory on average, but less cpu.
6392 - First cut at support for "create-fast" cells. Clients can use
6393 these when extending to their first hop, since the TLS already
6394 provides forward secrecy and authentication. Not enabled on
6396 - When dirservers refuse a router descriptor, we now log its
6397 contactinfo, platform, and the poster's IP address.
6398 - Call tor_free_all instead of connections_free_all after forking, to
6399 save memory on systems that need to fork.
6400 - Whine at you if you're a server and you don't set your contactinfo.
6401 - Implement --verify-config command-line option to check if your torrc
6402 is valid without actually launching Tor.
6403 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
6404 rather than just rejecting it.
6407 Changes in version 0.1.0.5-rc - 2005-04-27
6409 - Stop trying to print a null pointer if an OR conn fails because
6410 we didn't like its cert.
6412 - Switch our internal buffers implementation to use a ring buffer,
6413 to hopefully improve performance for fast servers a lot.
6414 - Add HttpsProxyAuthenticator support (basic auth only), based
6415 on patch from Adam Langley.
6416 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
6417 the fast servers that have been joining lately.
6418 - Give hidden service accesses extra time on the first attempt,
6419 since 60 seconds is often only barely enough. This might improve
6421 - Improve performance for dirservers: stop re-parsing the whole
6422 directory every time you regenerate it.
6423 - Add more debugging info to help us find the weird dns freebsd
6424 pthreads bug; cleaner debug messages to help track future issues.
6427 Changes in version 0.0.9.9 - 2005-04-23
6428 o Bugfixes on 0.0.9.x:
6429 - If unofficial Tor clients connect and send weird TLS certs, our
6430 Tor server triggers an assert. This release contains a minimal
6431 backport from the broader fix that we put into 0.1.0.4-rc.
6434 Changes in version 0.1.0.4-rc - 2005-04-23
6436 - If unofficial Tor clients connect and send weird TLS certs, our
6437 Tor server triggers an assert. Stop asserting, and start handling
6438 TLS errors better in other situations too.
6439 - When the controller asks us to tell it about all the debug-level
6440 logs, it turns out we were generating debug-level logs while
6441 telling it about them, which turns into a bad loop. Now keep
6442 track of whether you're sending a debug log to the controller,
6443 and don't log when you are.
6444 - Fix the "postdescriptor" feature of the controller interface: on
6445 non-complete success, only say "done" once.
6447 - Clients are now willing to load balance over up to 2mB, not 1mB,
6448 of advertised bandwidth capacity.
6449 - Add a NoPublish config option, so you can be a server (e.g. for
6450 testing running Tor servers in other Tor networks) without
6451 publishing your descriptor to the primary dirservers.
6454 Changes in version 0.1.0.3-rc - 2005-04-08
6455 o Improvements on 0.1.0.2-rc:
6456 - Client now retries when streams end early for 'hibernating' or
6457 'resource limit' reasons, rather than failing them.
6458 - More automated handling for dirserver operators:
6459 - Automatically approve nodes running 0.1.0.2-rc or later,
6460 now that the the reachability detection stuff is working.
6461 - Now we allow two unverified servers with the same nickname
6462 but different keys. But if a nickname is verified, only that
6463 nickname+key are allowed.
6464 - If you're an authdirserver connecting to an address:port,
6465 and it's not the OR you were expecting, forget about that
6466 descriptor. If he *was* the one you were expecting, then forget
6467 about all other descriptors for that address:port.
6468 - Allow servers to publish descriptors from 12 hours in the future.
6469 Corollary: only whine about clock skew from the dirserver if
6470 he's a trusted dirserver (since now even verified servers could
6471 have quite wrong clocks).
6472 - Adjust maximum skew and age for rendezvous descriptors: let skew
6473 be 48 hours rather than 90 minutes.
6474 - Efficiency improvements:
6475 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
6476 it much faster to look up a circuit for each relay cell.
6477 - Remove most calls to assert_all_pending_dns_resolves_ok(),
6478 since they're eating our cpu on exit nodes.
6479 - Stop wasting time doing a case insensitive comparison for every
6480 dns name every time we do any lookup. Canonicalize the names to
6481 lowercase and be done with it.
6482 - Start sending 'truncated' cells back rather than destroy cells,
6483 if the circuit closes in front of you. This means we won't have
6484 to abandon partially built circuits.
6485 - Only warn once per nickname from add_nickname_list_to_smartlist
6486 per failure, so an entrynode or exitnode choice that's down won't
6488 - Put a note in the torrc about abuse potential with the default
6490 - Revise control spec and implementation to allow all log messages to
6491 be sent to controller with their severities intact (suggested by
6492 Matt Edman). Update TorControl to handle new log event types.
6493 - Provide better explanation messages when controller's POSTDESCRIPTOR
6495 - Stop putting nodename in the Platform string in server descriptors.
6496 It doesn't actually help, and it is confusing/upsetting some people.
6498 o Bugfixes on 0.1.0.2-rc:
6499 - We were printing the host mask wrong in exit policies in server
6500 descriptors. This isn't a critical bug though, since we were still
6501 obeying the exit policy internally.
6502 - Fix Tor when compiled with libevent but without pthreads: move
6503 connection_unregister() from _connection_free() to
6505 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
6506 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
6507 when we look through the connection array, we'll find any of the
6508 cpu/dnsworkers. This is no good.
6510 o Bugfixes on 0.0.9.8:
6511 - Fix possible bug on threading platforms (e.g. win32) which was
6512 leaking a file descriptor whenever a cpuworker or dnsworker died.
6513 - When using preferred entry or exit nodes, ignore whether the
6514 circuit wants uptime or capacity. They asked for the nodes, they
6516 - chdir() to your datadirectory at the *end* of the daemonize process,
6517 not the beginning. This was a problem because the first time you
6518 run tor, if your datadir isn't there, and you have runasdaemon set
6519 to 1, it will try to chdir to it before it tries to create it. Oops.
6520 - Handle changed router status correctly when dirserver reloads
6521 fingerprint file. We used to be dropping all unverified descriptors
6522 right then. The bug was hidden because we would immediately
6523 fetch a directory from another dirserver, which would include the
6524 descriptors we just dropped.
6525 - When we're connecting to an OR and he's got a different nickname/key
6526 than we were expecting, only complain loudly if we're an OP or a
6527 dirserver. Complaining loudly to the OR admins just confuses them.
6528 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
6529 artificially capped at 500kB.
6532 Changes in version 0.0.9.8 - 2005-04-07
6533 o Bugfixes on 0.0.9.x:
6534 - We have a bug that I haven't found yet. Sometimes, very rarely,
6535 cpuworkers get stuck in the 'busy' state, even though the cpuworker
6536 thinks of itself as idle. This meant that no new circuits ever got
6537 established. Here's a workaround to kill any cpuworker that's been
6538 busy for more than 100 seconds.
6541 Changes in version 0.1.0.2-rc - 2005-04-01
6542 o Bugfixes on 0.1.0.1-rc:
6543 - Fixes on reachability detection:
6544 - Don't check for reachability while hibernating.
6545 - If ORPort is reachable but DirPort isn't, still publish the
6546 descriptor, but zero out DirPort until it's found reachable.
6547 - When building testing circs for ORPort testing, use only
6548 high-bandwidth nodes, so fewer circuits fail.
6549 - Complain about unreachable ORPort separately from unreachable
6550 DirPort, so the user knows what's going on.
6551 - Make sure we only conclude ORPort reachability if we didn't
6552 initiate the conn. Otherwise we could falsely conclude that
6553 we're reachable just because we connected to the guy earlier
6554 and he used that same pipe to extend to us.
6555 - Authdirservers shouldn't do ORPort reachability detection,
6556 since they're in clique mode, so it will be rare to find a
6557 server not already connected to them.
6558 - When building testing circuits, always pick middle hops running
6559 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
6560 bug. (This is a kludge; it will go away when 0.0.9.x becomes
6562 - When we decide we're reachable, actually publish our descriptor
6564 - Fix bug in redirectstream in the controller.
6565 - Fix the state descriptor strings so logs don't claim edge streams
6566 are in a different state than they actually are.
6567 - Use recent libevent features when possible (this only really affects
6568 win32 and osx right now, because the new libevent with these
6569 features hasn't been released yet). Add code to suppress spurious
6571 - Prevent possible segfault in connection_close_unattached_ap().
6572 - Fix newlines on torrc in win32.
6573 - Improve error msgs when tor-resolve fails.
6575 o Improvements on 0.0.9.x:
6576 - New experimental script tor/contrib/ExerciseServer.py (needs more
6577 work) that uses the controller interface to build circuits and
6578 fetch pages over them. This will help us bootstrap servers that
6579 have lots of capacity but haven't noticed it yet.
6580 - New experimental script tor/contrib/PathDemo.py (needs more work)
6581 that uses the controller interface to let you choose whole paths
6583 "<hostname>.<path,separated by dots>.<length of path>.path"
6584 - When we've connected to an OR and handshaked but didn't like
6585 the result, we were closing the conn without sending destroy
6586 cells back for pending circuits. Now send those destroys.
6589 Changes in version 0.0.9.7 - 2005-04-01
6590 o Bugfixes on 0.0.9.x:
6591 - Fix another race crash bug (thanks to Glenn Fink for reporting).
6592 - Compare identity to identity, not to nickname, when extending to
6593 a router not already in the directory. This was preventing us from
6594 extending to unknown routers. Oops.
6595 - Make sure to create OS X Tor user in <500 range, so we aren't
6596 creating actual system users.
6597 - Note where connection-that-hasn't-sent-end was marked, and fix
6598 a few really loud instances of this harmless bug (it's fixed more
6602 Changes in version 0.1.0.1-rc - 2005-03-28
6604 - Add reachability testing. Your Tor server will automatically try
6605 to see if its ORPort and DirPort are reachable from the outside,
6606 and it won't upload its descriptor until it decides they are.
6607 - Handle unavailable hidden services better. Handle slow or busy
6608 hidden services better.
6609 - Add support for CONNECTing through https proxies, with "HttpsProxy"
6611 - New exit policy: accept most low-numbered ports, rather than
6612 rejecting most low-numbered ports.
6613 - More Tor controller support (still experimental). See
6614 http://tor.eff.org/doc/control-spec.txt for all the new features,
6615 including signals to emulate unix signals from any platform;
6616 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
6617 closestream; closecircuit; etc.
6618 - Make nt services work and start on startup on win32 (based on
6619 patch by Matt Edman).
6620 - Add a new AddressMap config directive to rewrite incoming socks
6621 addresses. This lets you, for example, declare an implicit
6622 required exit node for certain sites.
6623 - Add a new TrackHostExits config directive to trigger addressmaps
6624 for certain incoming socks addresses -- for sites that break when
6625 your exit keeps changing (based on patch by Mike Perry).
6626 - Redo the client-side dns cache so it's just an addressmap too.
6627 - Notice when our IP changes, and reset stats/uptime/reachability.
6628 - When an application is using socks5, give him the whole variety of
6629 potential socks5 responses (connect refused, host unreachable, etc),
6630 rather than just "success" or "failure".
6631 - A more sane version numbering system. See
6632 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
6633 - New contributed script "exitlist": a simple python script to
6634 parse directories and find Tor nodes that exit to listed
6636 - New contributed script "privoxy-tor-toggle" to toggle whether
6637 Privoxy uses Tor. Seems to be configured for Debian by default.
6638 - Report HTTP reasons to client when getting a response from directory
6639 servers -- so you can actually know what went wrong.
6640 - New config option MaxAdvertisedBandwidth which lets you advertise
6641 a low bandwidthrate (to not attract as many circuits) while still
6642 allowing a higher bandwidthrate in reality.
6644 o Robustness/stability fixes:
6645 - Make Tor use Niels Provos's libevent instead of its current
6646 poll-but-sometimes-select mess. This will let us use faster async
6647 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
6649 - pthread support now too. This was forced because when we forked,
6650 we ended up wasting a lot of duplicate ram over time. Also switch
6651 to foo_r versions of some library calls to allow reentry and
6653 - Better handling for heterogeneous / unreliable nodes:
6654 - Annotate circuits w/ whether they aim to contain high uptime nodes
6655 and/or high capacity nodes. When building circuits, choose
6657 - This means that every single node in an intro rend circuit,
6658 not just the last one, will have a minimum uptime.
6659 - New config option LongLivedPorts to indicate application streams
6660 that will want high uptime circuits.
6661 - Servers reset uptime when a dir fetch entirely fails. This
6662 hopefully reflects stability of the server's network connectivity.
6663 - If somebody starts his tor server in Jan 2004 and then fixes his
6664 clock, don't make his published uptime be a year.
6665 - Reset published uptime when you wake up from hibernation.
6666 - Introduce a notion of 'internal' circs, which are chosen without
6667 regard to the exit policy of the last hop. Intro and rendezvous
6668 circs must be internal circs, to avoid leaking information. Resolve
6669 and connect streams can use internal circs if they want.
6670 - New circuit pooling algorithm: make sure to have enough circs around
6671 to satisfy any predicted ports, and also make sure to have 2 internal
6672 circs around if we've required internal circs lately (and with high
6673 uptime if we've seen that lately too).
6674 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
6675 which describes how often we retry making new circuits if current
6676 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
6677 how long we're willing to make use of an already-dirty circuit.
6678 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
6679 circ as necessary, if there are any completed ones lying around
6680 when we try to launch one.
6681 - Make hidden services try to establish a rendezvous for 30 seconds,
6682 rather than for n (where n=3) attempts to build a circuit.
6683 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
6684 "ShutdownWaitLength".
6685 - Try to be more zealous about calling connection_edge_end when
6686 things go bad with edge conns in connection.c.
6687 - Revise tor-spec to add more/better stream end reasons.
6688 - Revise all calls to connection_edge_end to avoid sending "misc",
6689 and to take errno into account where possible.
6692 - Fix a race condition that can trigger an assert, when we have a
6693 pending create cell and an OR connection fails right then.
6694 - Fix several double-mark-for-close bugs, e.g. where we were finding
6695 a conn for a cell even if that conn is already marked for close.
6696 - Make sequence of log messages when starting on win32 with no config
6697 file more reasonable.
6698 - When choosing an exit node for a new non-internal circ, don't take
6699 into account whether it'll be useful for any pending x.onion
6700 addresses -- it won't.
6701 - Turn addr_policy_compare from a tristate to a quadstate; this should
6702 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
6703 for google.com" problem.
6704 - Make "platform" string in descriptor more accurate for Win32 servers,
6705 so it's not just "unknown platform".
6706 - Fix an edge case in parsing config options (thanks weasel).
6707 If they say "--" on the commandline, it's not an option.
6708 - Reject odd-looking addresses at the client (e.g. addresses that
6709 contain a colon), rather than having the server drop them because
6711 - tor-resolve requests were ignoring .exit if there was a working circuit
6712 they could use instead.
6713 - REUSEADDR on normal platforms means you can rebind to the port
6714 right after somebody else has let it go. But REUSEADDR on win32
6715 means to let you bind to the port _even when somebody else
6716 already has it bound_! So, don't do that on Win32.
6717 - Change version parsing logic: a version is "obsolete" if it is not
6718 recommended and (1) there is a newer recommended version in the
6719 same series, or (2) there are no recommended versions in the same
6720 series, but there are some recommended versions in a newer series.
6721 A version is "new" if it is newer than any recommended version in
6723 - Stop most cases of hanging up on a socks connection without sending
6727 - Require BandwidthRate to be at least 20kB/s for servers.
6728 - When a dirserver causes you to give a warn, mention which dirserver
6730 - New config option DirAllowPrivateAddresses for authdirservers.
6731 Now by default they refuse router descriptors that have non-IP or
6732 private-IP addresses.
6733 - Stop publishing socksport in the directory, since it's not
6734 actually meant to be public. For compatibility, publish a 0 there
6736 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
6737 smart" value, that is low for servers and high for clients.
6738 - If our clock jumps forward by 100 seconds or more, assume something
6739 has gone wrong with our network and abandon all not-yet-used circs.
6740 - Warn when exit policy implicitly allows local addresses.
6741 - If we get an incredibly skewed timestamp from a dirserver mirror
6742 that isn't a verified OR, don't warn -- it's probably him that's
6744 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
6745 cookies to disk and doesn't log each web request to disk. (Thanks
6746 to Brett Carrington for pointing this out.)
6747 - When a client asks us for a dir mirror and we don't have one,
6748 launch an attempt to get a fresh one.
6749 - If we're hibernating and we get a SIGINT, exit immediately.
6750 - Add --with-dmalloc ./configure option, to track memory leaks.
6751 - And try to free all memory on closing, so we can detect what
6753 - Cache local dns resolves correctly even when they're .exit
6755 - Give a better warning when some other server advertises an
6756 ORPort that is actually an apache running ssl.
6757 - Add "opt hibernating 1" to server descriptor to make it clearer
6758 whether the server is hibernating.
6761 Changes in version 0.0.9.6 - 2005-03-24
6762 o Bugfixes on 0.0.9.x (crashes and asserts):
6763 - Add new end stream reasons to maintainance branch. Fix bug where
6764 reason (8) could trigger an assert. Prevent bug from recurring.
6765 - Apparently win32 stat wants paths to not end with a slash.
6766 - Fix assert triggers in assert_cpath_layer_ok(), where we were
6767 blowing away the circuit that conn->cpath_layer points to, then
6768 checking to see if the circ is well-formed. Backport check to make
6769 sure we dont use the cpath on a closed connection.
6770 - Prevent circuit_resume_edge_reading_helper() from trying to package
6771 inbufs for marked-for-close streams.
6772 - Don't crash on hup if your options->address has become unresolvable.
6773 - Some systems (like OS X) sometimes accept() a connection and tell
6774 you the remote host is 0.0.0.0:0. If this happens, due to some
6775 other mis-features, we get confused; so refuse the conn for now.
6777 o Bugfixes on 0.0.9.x (other):
6778 - Fix harmless but scary "Unrecognized content encoding" warn message.
6779 - Add new stream error reason: TORPROTOCOL reason means "you are not
6780 speaking a version of Tor I understand; say bye-bye to your stream."
6781 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
6782 into the future, now that we are more tolerant of skew. This
6783 resolves a bug where a Tor server would refuse to cache a directory
6784 because all the directories it gets are too far in the future;
6785 yet the Tor server never logs any complaints about clock skew.
6786 - Mac packaging magic: make man pages useable, and do not overwrite
6787 existing torrc files.
6788 - Make OS X log happily to /var/log/tor/tor.log
6791 Changes in version 0.0.9.5 - 2005-02-22
6792 o Bugfixes on 0.0.9.x:
6793 - Fix an assert race at exit nodes when resolve requests fail.
6794 - Stop picking unverified dir mirrors--it only leads to misery.
6795 - Patch from Matt Edman to make NT services work better. Service
6796 support is still not compiled into the executable by default.
6797 - Patch from Dmitri Bely so the Tor service runs better under
6798 the win32 SYSTEM account.
6799 - Make tor-resolve actually work (?) on Win32.
6800 - Fix a sign bug when getrlimit claims to have 4+ billion
6801 file descriptors available.
6802 - Stop refusing to start when bandwidthburst == bandwidthrate.
6803 - When create cells have been on the onion queue more than five
6804 seconds, just send back a destroy and take them off the list.
6807 Changes in version 0.0.9.4 - 2005-02-03
6808 o Bugfixes on 0.0.9:
6809 - Fix an assert bug that took down most of our servers: when
6810 a server claims to have 1 GB of bandwidthburst, don't
6812 - Don't crash as badly if we have spawned the max allowed number
6813 of dnsworkers, or we're out of file descriptors.
6814 - Block more file-sharing ports in the default exit policy.
6815 - MaxConn is now automatically set to the hard limit of max
6816 file descriptors we're allowed (ulimit -n), minus a few for
6818 - Give a clearer message when servers need to raise their
6819 ulimit -n when they start running out of file descriptors.
6820 - SGI Compatibility patches from Jan Schaumann.
6821 - Tolerate a corrupt cached directory better.
6822 - When a dirserver hasn't approved your server, list which one.
6823 - Go into soft hibernation after 95% of the bandwidth is used,
6824 not 99%. This is especially important for daily hibernators who
6825 have a small accounting max. Hopefully it will result in fewer
6826 cut connections when the hard hibernation starts.
6827 - Load-balance better when using servers that claim more than
6828 800kB/s of capacity.
6829 - Make NT services work (experimental, only used if compiled in).
6832 Changes in version 0.0.9.3 - 2005-01-21
6833 o Bugfixes on 0.0.9:
6834 - Backport the cpu use fixes from main branch, so busy servers won't
6835 need as much processor time.
6836 - Work better when we go offline and then come back, or when we
6837 run Tor at boot before the network is up. We do this by
6838 optimistically trying to fetch a new directory whenever an
6839 application request comes in and we think we're offline -- the
6840 human is hopefully a good measure of when the network is back.
6841 - Backport some minimal hidserv bugfixes: keep rend circuits open as
6842 long as you keep using them; actually publish hidserv descriptors
6843 shortly after they change, rather than waiting 20-40 minutes.
6844 - Enable Mac startup script by default.
6845 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
6846 - When you update AllowUnverifiedNodes or FirewallPorts via the
6847 controller's setconf feature, we were always appending, never
6849 - When you update HiddenServiceDir via setconf, it was screwing up
6850 the order of reading the lines, making it fail.
6851 - Do not rewrite a cached directory back to the cache; otherwise we
6852 will think it is recent and not fetch a newer one on startup.
6853 - Workaround for webservers that lie about Content-Encoding: Tor
6854 now tries to autodetect compressed directories and compression
6855 itself. This lets us Proxypass dir fetches through apache.
6858 Changes in version 0.0.9.2 - 2005-01-04
6859 o Bugfixes on 0.0.9 (crashes and asserts):
6860 - Fix an assert on startup when the disk is full and you're logging
6862 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
6863 style address, then we'd crash.
6864 - Fix an assert trigger when the running-routers string we get from
6865 a dirserver is broken.
6866 - Make worker threads start and run on win32. Now win32 servers
6868 - Bandaid (not actually fix, but now it doesn't crash) an assert
6869 where the dns worker dies mysteriously and the main Tor process
6870 doesn't remember anything about the address it was resolving.
6872 o Bugfixes on 0.0.9 (Win32):
6873 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
6874 name out of the warning/assert messages.
6875 - Fix a superficial "unhandled error on read" bug on win32.
6876 - The win32 installer no longer requires a click-through for our
6877 license, since our Free Software license grants rights but does not
6879 - Win32: When connecting to a dirserver fails, try another one
6880 immediately. (This was already working for non-win32 Tors.)
6881 - Stop trying to parse $HOME on win32 when hunting for default
6883 - Make tor-resolve.c work on win32 by calling network_init().
6885 o Bugfixes on 0.0.9 (other):
6886 - Make 0.0.9.x build on Solaris again.
6887 - Due to a fencepost error, we were blowing away the \n when reporting
6888 confvalue items in the controller. So asking for multiple config
6889 values at once couldn't work.
6890 - When listing circuits that are pending on an opening OR connection,
6891 if we're an OR we were listing circuits that *end* at us as
6892 being pending on every listener, dns/cpu worker, etc. Stop that.
6893 - Dirservers were failing to create 'running-routers' or 'directory'
6894 strings if we had more than some threshold of routers. Fix them so
6895 they can handle any number of routers.
6896 - Fix a superficial "Duplicate mark for close" bug.
6897 - Stop checking for clock skew for OR connections, even for servers.
6898 - Fix a fencepost error that was chopping off the last letter of any
6899 nickname that is the maximum allowed nickname length.
6900 - Update URLs in log messages so they point to the new website.
6901 - Fix a potential problem in mangling server private keys while
6902 writing to disk (not triggered yet, as far as we know).
6903 - Include the licenses for other free software we include in Tor,
6904 now that we're shipping binary distributions more regularly.
6907 Changes in version 0.0.9.1 - 2004-12-15
6908 o Bugfixes on 0.0.9:
6909 - Make hibernation actually work.
6910 - Make HashedControlPassword config option work.
6911 - When we're reporting event circuit status to a controller,
6912 don't use the stream status code.
6915 Changes in version 0.0.9 - 2004-12-12
6917 - Clean up manpage and torrc.sample file.
6918 - Clean up severities and text of log warnings.
6920 - Make servers trigger an assert when they enter hibernation.
6923 Changes in version 0.0.9rc7 - 2004-12-08
6924 o Bugfixes on 0.0.9rc:
6925 - Fix a stack-trashing crash when an exit node begins hibernating.
6926 - Avoid looking at unallocated memory while considering which
6927 ports we need to build circuits to cover.
6928 - Stop a sigpipe: when an 'end' cell races with eof from the app,
6929 we shouldn't hold-open-until-flush if the eof arrived first.
6930 - Fix a bug with init_cookie_authentication() in the controller.
6931 - When recommending new-format log lines, if the upper bound is
6932 LOG_ERR, leave it implicit.
6934 o Bugfixes on 0.0.8.1:
6935 - Fix a whole slew of memory leaks.
6936 - Fix isspace() and friends so they still make Solaris happy
6937 but also so they don't trigger asserts on win32.
6938 - Fix parse_iso_time on platforms without strptime (eg win32).
6939 - win32: tolerate extra "readable" events better.
6940 - win32: when being multithreaded, leave parent fdarray open.
6941 - Make unit tests work on win32.
6944 Changes in version 0.0.9rc6 - 2004-12-06
6945 o Bugfixes on 0.0.9pre:
6946 - Clean up some more integer underflow opportunities (not exploitable
6948 - While hibernating, hup should not regrow our listeners.
6949 - Send an end to the streams we close when we hibernate, rather
6950 than just chopping them off.
6951 - React to eof immediately on non-open edge connections.
6953 o Bugfixes on 0.0.8.1:
6954 - Calculate timeout for waiting for a connected cell from the time
6955 we sent the begin cell, not from the time the stream started. If
6956 it took a long time to establish the circuit, we would time out
6957 right after sending the begin cell.
6958 - Fix router_compare_addr_to_addr_policy: it was not treating a port
6959 of * as always matching, so we were picking reject *:* nodes as
6960 exit nodes too. Oops.
6963 - New circuit building strategy: keep a list of ports that we've
6964 used in the past 6 hours, and always try to have 2 circuits open
6965 or on the way that will handle each such port. Seed us with port
6966 80 so web users won't complain that Tor is "slow to start up".
6967 - Make kill -USR1 dump more useful stats about circuits.
6968 - When warning about retrying or giving up, print the address, so
6969 the user knows which one it's talking about.
6970 - If you haven't used a clean circuit in an hour, throw it away,
6971 just to be on the safe side. (This means after 6 hours a totally
6972 unused Tor client will have no circuits open.)
6975 Changes in version 0.0.9rc5 - 2004-12-01
6976 o Bugfixes on 0.0.8.1:
6977 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
6978 - Let resolve conns retry/expire also, rather than sticking around
6980 - If we are using select, make sure we stay within FD_SETSIZE.
6982 o Bugfixes on 0.0.9pre:
6983 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
6984 but doesn't seem to be currently; thanks to Ilja van Sprundel for
6986 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
6987 instead. Impose minima and maxima for all *Period options; impose
6988 even tighter maxima for fetching if we are a caching dirserver.
6989 Clip rather than rejecting.
6990 - Fetch cached running-routers from servers that serve it (that is,
6991 authdirservers and servers running 0.0.9rc5-cvs or later.)
6994 - Accept *:706 (silc) in default exit policy.
6995 - Implement new versioning format for post 0.1.
6996 - Support "foo.nickname.exit" addresses, to let Alice request the
6997 address "foo" as viewed by exit node "nickname". Based on a patch
6999 - Make tor --version --version dump the cvs Id of every file.
7002 Changes in version 0.0.9rc4 - 2004-11-28
7003 o Bugfixes on 0.0.8.1:
7004 - Make windows sockets actually non-blocking (oops), and handle
7005 win32 socket errors better.
7007 o Bugfixes on 0.0.9rc1:
7008 - Actually catch the -USR2 signal.
7011 Changes in version 0.0.9rc3 - 2004-11-25
7012 o Bugfixes on 0.0.8.1:
7013 - Flush the log file descriptor after we print "Tor opening log file",
7014 so we don't see those messages days later.
7016 o Bugfixes on 0.0.9rc1:
7017 - Make tor-resolve work again.
7018 - Avoid infinite loop in tor-resolve if tor hangs up on it.
7019 - Fix an assert trigger for clients/servers handling resolves.
7022 Changes in version 0.0.9rc2 - 2004-11-24
7023 o Bugfixes on 0.0.9rc1:
7024 - I broke socks5 support while fixing the eof bug.
7025 - Allow unitless bandwidths and intervals; they default to bytes
7027 - New servers don't start out hibernating; they are active until
7028 they run out of bytes, so they have a better estimate of how
7029 long it takes, and so their operators can know they're working.
7032 Changes in version 0.0.9rc1 - 2004-11-23
7033 o Bugfixes on 0.0.8.1:
7034 - Finally fix a bug that's been plaguing us for a year:
7035 With high load, circuit package window was reaching 0. Whenever
7036 we got a circuit-level sendme, we were reading a lot on each
7037 socket, but only writing out a bit. So we would eventually reach
7038 eof. This would be noticed and acted on even when there were still
7039 bytes sitting in the inbuf.
7040 - When poll() is interrupted, we shouldn't believe the revents values.
7042 o Bugfixes on 0.0.9pre6:
7043 - Fix hibernate bug that caused pre6 to be broken.
7044 - Don't keep rephist info for routers that haven't had activity for
7045 24 hours. (This matters now that clients have keys, since we track
7047 - Never call close_temp_logs while validating log options.
7048 - Fix backslash-escaping on tor.sh.in and torctl.in.
7051 - Implement weekly/monthly/daily accounting: now you specify your
7052 hibernation properties by
7053 AccountingMax N bytes|KB|MB|GB|TB
7054 AccountingStart day|week|month [day] HH:MM
7055 Defaults to "month 1 0:00".
7056 - Let bandwidth and interval config options be specified as 5 bytes,
7057 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
7058 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
7059 get back to normal.)
7060 - If your requested entry or exit node has advertised bandwidth 0,
7062 - Be more greedy about filling up relay cells -- we try reading again
7063 once we've processed the stuff we read, in case enough has arrived
7064 to fill the last cell completely.
7065 - Apply NT service patch from Osamu Fujino. Still needs more work.
7068 Changes in version 0.0.9pre6 - 2004-11-15
7069 o Bugfixes on 0.0.8.1:
7070 - Fix assert failure on malformed socks4a requests.
7071 - Use identity comparison, not nickname comparison, to choose which
7072 half of circuit-ID-space each side gets to use. This is needed
7073 because sometimes we think of a router as a nickname, and sometimes
7074 as a hex ID, and we can't predict what the other side will do.
7075 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
7076 write() call will fail and we handle it there.
7077 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
7078 and smartlist_len, which are two major profiling offenders.
7080 o Bugfixes on 0.0.9pre5:
7081 - Fix a bug in read_all that was corrupting config files on windows.
7082 - When we're raising the max number of open file descriptors to
7083 'unlimited', don't log that we just raised it to '-1'.
7084 - Include event code with events, as required by control-spec.txt.
7085 - Don't give a fingerprint when clients do --list-fingerprint:
7086 it's misleading, because it will never be the same again.
7087 - Stop using strlcpy in tor_strndup, since it was slowing us
7089 - Remove warn on startup about missing cached-directory file.
7090 - Make kill -USR1 work again.
7091 - Hibernate if we start tor during the "wait for wakeup-time" phase
7092 of an accounting interval. Log our hibernation plans better.
7093 - Authoritative dirservers now also cache their directory, so they
7094 have it on start-up.
7097 - Fetch running-routers; cache running-routers; compress
7098 running-routers; serve compressed running-routers.z
7099 - Add NSI installer script contributed by J Doe.
7100 - Commit VC6 and VC7 workspace/project files.
7101 - Commit a tor.spec for making RPM files, with help from jbash.
7102 - Add contrib/torctl.in contributed by Glenn Fink.
7103 - Implement the control-spec's SAVECONF command, to write your
7104 configuration to torrc.
7105 - Get cookie authentication for the controller closer to working.
7106 - Include control-spec.txt in the tarball.
7107 - When set_conf changes our server descriptor, upload a new copy.
7108 But don't upload it too often if there are frequent changes.
7109 - Document authentication config in man page, and document signals
7111 - Clean up confusing parts of man page and torrc.sample.
7112 - Make expand_filename handle ~ and ~username.
7113 - Use autoconf to enable largefile support where necessary. Use
7114 ftello where available, since ftell can fail at 2GB.
7115 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
7116 log more informatively.
7117 - Give a slightly more useful output for "tor -h".
7118 - Refuse application socks connections to port 0.
7119 - Check clock skew for verified servers, but allow unverified
7120 servers and clients to have any clock skew.
7121 - Break DirFetchPostPeriod into:
7122 - DirFetchPeriod for fetching full directory,
7123 - StatusFetchPeriod for fetching running-routers,
7124 - DirPostPeriod for posting server descriptor,
7125 - RendPostPeriod for posting hidden service descriptors.
7126 - Make sure the hidden service descriptors are at a random offset
7127 from each other, to hinder linkability.
7130 Changes in version 0.0.9pre5 - 2004-11-09
7131 o Bugfixes on 0.0.9pre4:
7132 - Fix a seg fault in unit tests (doesn't affect main program).
7133 - Fix an assert bug where a hidden service provider would fail if
7134 the first hop of his rendezvous circuit was down.
7135 - Hidden service operators now correctly handle version 1 style
7136 INTRODUCE1 cells (nobody generates them still, so not a critical
7138 - If do_hup fails, actually notice.
7139 - Handle more errnos from accept() without closing the listener.
7140 Some OpenBSD machines were closing their listeners because
7141 they ran out of file descriptors.
7142 - Send resolve cells to exit routers that are running a new
7143 enough version of the resolve code to work right.
7144 - Better handling of winsock includes on non-MSV win32 compilers.
7145 - Some people had wrapped their tor client/server in a script
7146 that would restart it whenever it died. This did not play well
7147 with our "shut down if your version is obsolete" code. Now people
7148 don't fetch a new directory if their local cached version is
7150 - Make our autogen.sh work on ksh as well as bash.
7153 - Hibernation: New config option "AccountingMaxKB" lets you
7154 set how many KBytes per month you want to allow your server to
7155 consume. Rather than spreading those bytes out evenly over the
7156 month, we instead hibernate for some of the month and pop up
7157 at a deterministic time, work until the bytes are consumed, then
7158 hibernate again. Config option "MonthlyAccountingStart" lets you
7159 specify which day of the month your billing cycle starts on.
7160 - Control interface: a separate program can now talk to your
7161 client/server over a socket, and get/set config options, receive
7162 notifications of circuits and streams starting/finishing/dying,
7163 bandwidth used, etc. The next step is to get some GUIs working.
7164 Let us know if you want to help out. See doc/control-spec.txt .
7165 - Ship a contrib/tor-control.py as an example script to interact
7166 with the control port.
7167 - "tor --hash-password zzyxz" will output a salted password for
7168 use in authenticating to the control interface.
7169 - New log format in config:
7170 "Log minsev[-maxsev] stdout|stderr|syslog" or
7171 "Log minsev[-maxsev] file /var/foo"
7174 - DirPolicy config option, to let people reject incoming addresses
7175 from their dirserver.
7176 - "tor --list-fingerprint" will list your identity key fingerprint
7178 - Add "pass" target for RedirectExit, to make it easier to break
7179 out of a sequence of RedirectExit rules.
7180 - Clients now generate a TLS cert too, in preparation for having
7181 them act more like real nodes.
7182 - Ship src/win32/ in the tarball, so people can use it to build.
7183 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
7185 - New "router-status" line in directory, to better bind each verified
7186 nickname to its identity key.
7187 - Deprecate unofficial config option abbreviations, and abbreviations
7188 not on the command line.
7189 - Add a pure-C tor-resolve implementation.
7190 - Use getrlimit and friends to ensure we can reach MaxConn (currently
7191 1024) file descriptors.
7193 o Code security improvements, inspired by Ilja:
7194 - Replace sprintf with snprintf. (I think they were all safe, but
7196 - Replace strcpy/strncpy with strlcpy in more places.
7197 - Avoid strcat; use snprintf or strlcat instead.
7198 - snprintf wrapper with consistent (though not C99) overflow behavior.
7201 Changes in version 0.0.9pre4 - 2004-10-17
7202 o Bugfixes on 0.0.9pre3:
7203 - If the server doesn't specify an exit policy, use the real default
7204 exit policy, not reject *:*.
7205 - Ignore fascistfirewall when uploading/downloading hidden service
7206 descriptors, since we go through Tor for those; and when using
7207 an HttpProxy, since we assume it can reach them all.
7208 - When looking for an authoritative dirserver, use only the ones
7209 configured at boot. Don't bother looking in the directory.
7210 - The rest of the fix for get_default_conf_file() on older win32.
7211 - Make 'Routerfile' config option obsolete.
7214 - New 'MyFamily nick1,...' config option for a server to
7215 specify other servers that shouldn't be used in the same circuit
7216 with it. Only believed if nick1 also specifies us.
7217 - New 'NodeFamily nick1,nick2,...' config option for a client to
7218 specify nodes that it doesn't want to use in the same circuit.
7219 - New 'Redirectexit pattern address:port' config option for a
7220 server to redirect exit connections, e.g. to a local squid.
7223 Changes in version 0.0.9pre3 - 2004-10-13
7224 o Bugfixes on 0.0.8.1:
7225 - Better torrc example lines for dirbindaddress and orbindaddress.
7226 - Improved bounds checking on parsed ints (e.g. config options and
7227 the ones we find in directories.)
7228 - Better handling of size_t vs int, so we're more robust on 64
7230 - Fix the rest of the bug where a newly started OR would appear
7231 as unverified even after we've added his fingerprint and hupped
7233 - Fix a bug from 0.0.7: when read() failed on a stream, we would
7234 close it without sending back an end. So 'connection refused'
7235 would simply be ignored and the user would get no response.
7237 o Bugfixes on 0.0.9pre2:
7238 - Serving the cached-on-disk directory to people is bad. We now
7239 provide no directory until we've fetched a fresh one.
7240 - Workaround for bug on windows where cached-directories get crlf
7242 - Make get_default_conf_file() work on older windows too.
7243 - If we write a *:* exit policy line in the descriptor, don't write
7244 any more exit policy lines.
7247 - Use only 0.0.9pre1 and later servers for resolve cells.
7248 - Make the dirservers file obsolete.
7249 - Include a dir-signing-key token in directories to tell the
7250 parsing entity which key is being used to sign.
7251 - Remove the built-in bulky default dirservers string.
7252 - New config option "Dirserver %s:%d [fingerprint]", which can be
7253 repeated as many times as needed. If no dirservers specified,
7254 default to moria1,moria2,tor26.
7255 - Make moria2 advertise a dirport of 80, so people behind firewalls
7256 will be able to get a directory.
7257 - Http proxy support
7258 - Dirservers translate requests for http://%s:%d/x to /x
7259 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
7260 be routed through this host.
7261 - Clients ask for /tor/x rather than /x for new enough dirservers.
7262 This way we can one day coexist peacefully with apache.
7263 - Clients specify a "Host: %s%d" http header, to be compatible
7264 with more proxies, and so running squid on an exit node can work.
7267 Changes in version 0.0.8.1 - 2004-10-13
7269 - Fix a seg fault that can be triggered remotely for Tor
7270 clients/servers with an open dirport.
7271 - Fix a rare assert trigger, where routerinfos for entries in
7272 our cpath would expire while we're building the path.
7273 - Fix a bug in OutboundBindAddress so it (hopefully) works.
7274 - Fix a rare seg fault for people running hidden services on
7275 intermittent connections.
7276 - Fix a bug in parsing opt keywords with objects.
7277 - Fix a stale pointer assert bug when a stream detaches and
7279 - Fix a string format vulnerability (probably not exploitable)
7280 in reporting stats locally.
7281 - Fix an assert trigger: sometimes launching circuits can fail
7282 immediately, e.g. because too many circuits have failed recently.
7283 - Fix a compile warning on 64 bit platforms.
7286 Changes in version 0.0.9pre2 - 2004-10-03
7288 - Make fetching a cached directory work for 64-bit platforms too.
7289 - Make zlib.h a required header, not an optional header.
7292 Changes in version 0.0.9pre1 - 2004-10-01
7294 - Stop using separate defaults for no-config-file and
7295 empty-config-file. Now you have to explicitly turn off SocksPort,
7296 if you don't want it open.
7297 - Fix a bug in OutboundBindAddress so it (hopefully) works.
7298 - Improve man page to mention more of the 0.0.8 features.
7299 - Fix a rare seg fault for people running hidden services on
7300 intermittent connections.
7301 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
7303 - Fix more dns related bugs: send back resolve_failed and end cells
7304 more reliably when the resolve fails, rather than closing the
7305 circuit and then trying to send the cell. Also attach dummy resolve
7306 connections to a circuit *before* calling dns_resolve(), to fix
7307 a bug where cached answers would never be sent in RESOLVED cells.
7308 - When we run out of disk space, or other log writing error, don't
7309 crash. Just stop logging to that log and continue.
7310 - We were starting to daemonize before we opened our logs, so if
7311 there were any problems opening logs, we would complain to stderr,
7312 which wouldn't work, and then mysteriously exit.
7313 - Fix a rare bug where sometimes a verified OR would connect to us
7314 before he'd uploaded his descriptor, which would cause us to
7315 assign conn->nickname as though he's unverified. Now we look through
7316 the fingerprint list to see if he's there.
7317 - Fix a rare assert trigger, where routerinfos for entries in
7318 our cpath would expire while we're building the path.
7321 - Clients can ask dirservers for /dir.z to get a compressed version
7322 of the directory. Only works for servers running 0.0.9, of course.
7323 - Make clients cache directories and use them to seed their router
7324 lists at startup. This means clients have a datadir again.
7325 - Configuration infrastructure support for warning on obsolete
7327 - Respond to content-encoding headers by trying to uncompress as
7329 - Reply with a deflated directory when a client asks for "dir.z".
7330 We could use allow-encodings instead, but allow-encodings isn't
7331 specified in HTTP 1.0.
7332 - Raise the max dns workers from 50 to 100.
7333 - Discourage people from setting their dirfetchpostperiod more often
7334 than once per minute.
7335 - Protect dirservers from overzealous descriptor uploading -- wait
7336 10 seconds after directory gets dirty, before regenerating.
7339 Changes in version 0.0.8 - 2004-08-25
7340 o Port it to SunOS 5.9 / Athena
7343 Changes in version 0.0.8rc2 - 2004-08-20
7344 o Make it compile on cygwin again.
7345 o When picking unverified routers, skip those with low uptime and/or
7346 low bandwidth, depending on what properties you care about.
7349 Changes in version 0.0.8rc1 - 2004-08-18
7350 o Changes from 0.0.7.3:
7352 - Fix assert triggers: if the other side returns an address 0.0.0.0,
7353 don't put it into the client dns cache.
7354 - If a begin failed due to exit policy, but we believe the IP address
7355 should have been allowed, switch that router to exitpolicy reject *:*
7356 until we get our next directory.
7358 - Clients choose nodes proportional to advertised bandwidth.
7359 - Avoid using nodes with low uptime as introduction points.
7360 - Handle servers with dynamic IP addresses: don't replace
7361 options->Address with the resolved one at startup, and
7362 detect our address right before we make a routerinfo each time.
7363 - 'FascistFirewall' option to pick dirservers and ORs on specific
7364 ports; plus 'FirewallPorts' config option to tell FascistFirewall
7365 which ports are open. (Defaults to 80,443)
7366 - Be more aggressive about trying to make circuits when the network
7367 has changed (e.g. when you unsuspend your laptop).
7368 - Check for time skew on http headers; report date in response to
7370 - If the entrynode config line has only one node, don't pick it as
7372 - Add strict{entry|exit}nodes config options. If set to 1, then
7373 we refuse to build circuits that don't include the specified entry
7375 - OutboundBindAddress config option, to bind to a specific
7376 IP address for outgoing connect()s.
7377 - End truncated log entries (e.g. directories) with "[truncated]".
7379 o Patches to 0.0.8preX:
7381 - Patches to compile and run on win32 again (maybe)?
7382 - Fix crash when looking for ~/.torrc with no $HOME set.
7383 - Fix a race bug in the unit tests.
7384 - Handle verified/unverified name collisions better when new
7385 routerinfo's arrive in a directory.
7386 - Sometimes routers were getting entered into the stats before
7387 we'd assigned their identity_digest. Oops.
7388 - Only pick and establish intro points after we've gotten a
7391 - AllowUnverifiedNodes config option to let circuits choose no-name
7392 routers in entry,middle,exit,introduction,rendezvous positions.
7393 Allow middle and rendezvous positions by default.
7394 - Add a man page for tor-resolve.
7397 Changes in version 0.0.7.3 - 2004-08-12
7398 o Stop dnsworkers from triggering an assert failure when you
7399 ask them to resolve the host "".
7402 Changes in version 0.0.8pre3 - 2004-08-09
7403 o Changes from 0.0.7.2:
7404 - Allow multiple ORs with same nickname in routerlist -- now when
7405 people give us one identity key for a nickname, then later
7406 another, we don't constantly complain until the first expires.
7407 - Remember used bandwidth (both in and out), and publish 15-minute
7408 snapshots for the past day into our descriptor.
7409 - You can now fetch $DIRURL/running-routers to get just the
7410 running-routers line, not the whole descriptor list. (But
7411 clients don't use this yet.)
7412 - When people mistakenly use Tor as an http proxy, point them
7413 at the tor-doc.html rather than the INSTALL.
7414 - Remove our mostly unused -- and broken -- hex_encode()
7415 function. Use base16_encode() instead. (Thanks to Timo Lindfors
7416 for pointing out this bug.)
7417 - Rotate onion keys every 12 hours, not every 2 hours, so we have
7418 fewer problems with people using the wrong key.
7419 - Change the default exit policy to reject the default edonkey,
7420 kazaa, gnutella ports.
7421 - Add replace_file() to util.[ch] to handle win32's rename().
7423 o Changes from 0.0.8preX:
7424 - Fix two bugs in saving onion keys to disk when rotating, so
7425 hopefully we'll get fewer people using old onion keys.
7426 - Fix an assert error that was making SocksPolicy not work.
7427 - Be willing to expire routers that have an open dirport -- it's
7428 just the authoritative dirservers we want to not forget.
7429 - Reject tor-resolve requests for .onion addresses early, so we
7430 don't build a whole rendezvous circuit and then fail.
7431 - When you're warning a server that he's unverified, don't cry
7433 - Fix a race condition: don't try to extend onto a connection
7434 that's still handshaking.
7435 - For servers in clique mode, require the conn to be open before
7436 you'll choose it for your path.
7437 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
7438 end relay cell, etc.
7439 - Measure bandwidth capacity over the last 24 hours, not just 12
7440 - Bugfix: authoritative dirservers were making and signing a new
7441 directory for each client, rather than reusing the cached one.
7444 Changes in version 0.0.8pre2 - 2004-08-04
7445 o Changes from 0.0.7.2:
7447 - Check directory signature _before_ you decide whether you're
7448 you're running an obsolete version and should exit.
7449 - Check directory signature _before_ you parse the running-routers
7450 list to decide who's running or verified.
7451 - Bugfixes and features:
7452 - Check return value of fclose while writing to disk, so we don't
7453 end up with broken files when servers run out of disk space.
7454 - Log a warning if the user uses an unsafe socks variant, so people
7455 are more likely to learn about privoxy or socat.
7456 - Dirservers now include RFC1123-style dates in the HTTP headers,
7457 which one day we will use to better detect clock skew.
7459 o Changes from 0.0.8pre1:
7460 - Make it compile without warnings again on win32.
7461 - Log a warning if you're running an unverified server, to let you
7462 know you might want to get it verified.
7463 - Only pick a default nickname if you plan to be a server.
7466 Changes in version 0.0.8pre1 - 2004-07-23
7468 - Made our unit tests compile again on OpenBSD 3.5, and tor
7469 itself compile again on OpenBSD on a sparc64.
7470 - We were neglecting milliseconds when logging on win32, so
7471 everything appeared to happen at the beginning of each second.
7474 - 'Extend' relay cell payloads now include the digest of the
7475 intended next hop's identity key. Now we can verify that we're
7476 extending to the right router, and also extend to routers we
7477 hadn't heard of before.
7480 - Tor nodes can now act as relays (with an advertised ORPort)
7481 without being manually verified by the dirserver operators.
7482 - Uploaded descriptors of unverified routers are now accepted
7483 by the dirservers, and included in the directory.
7484 - Verified routers are listed by nickname in the running-routers
7485 list; unverified routers are listed as "$<fingerprint>".
7486 - We now use hash-of-identity-key in most places rather than
7487 nickname or addr:port, for improved security/flexibility.
7488 - To avoid Sybil attacks, paths still use only verified servers.
7489 But now we have a chance to play around with hybrid approaches.
7490 - Nodes track bandwidth usage to estimate capacity (not used yet).
7491 - ClientOnly option for nodes that never want to become servers.
7492 - Directory caching.
7493 - "AuthoritativeDir 1" option for the official dirservers.
7494 - Now other nodes (clients and servers) will cache the latest
7495 directory they've pulled down.
7496 - They can enable their DirPort to serve it to others.
7497 - Clients will pull down a directory from any node with an open
7498 DirPort, and check the signature/timestamp correctly.
7499 - Authoritative dirservers now fetch directories from other
7500 authdirservers, to stay better synced.
7501 - Running-routers list tells who's down also, along with noting
7502 if they're verified (listed by nickname) or unverified (listed
7504 - Allow dirservers to serve running-router list separately.
7505 This isn't used yet.
7506 - ORs connect-on-demand to other ORs
7507 - If you get an extend cell to an OR you're not connected to,
7508 connect, handshake, and forward the create cell.
7509 - The authoritative dirservers stay connected to everybody,
7510 and everybody stays connected to 0.0.7 servers, but otherwise
7511 clients/servers expire unused connections after 5 minutes.
7512 - When servers get a sigint, they delay 30 seconds (refusing new
7513 connections) then exit. A second sigint causes immediate exit.
7514 - File and name management:
7515 - Look for .torrc if no CONFDIR "torrc" is found.
7516 - If no datadir is defined, then choose, make, and secure ~/.tor
7518 - If torrc not found, exitpolicy reject *:*.
7519 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
7520 - If no nickname is defined, derive default from hostname.
7521 - Rename secret key files, e.g. identity.key -> secret_id_key,
7522 to discourage people from mailing their identity key to tor-ops.
7523 - Refuse to build a circuit before the directory has arrived --
7524 it won't work anyway, since you won't know the right onion keys
7526 - Try other dirservers immediately if the one you try is down. This
7527 should tolerate down dirservers better now.
7528 - Parse tor version numbers so we can do an is-newer-than check
7529 rather than an is-in-the-list check.
7530 - New socks command 'resolve', to let us shim gethostbyname()
7532 - A 'tor_resolve' script to access the socks resolve functionality.
7533 - A new socks-extensions.txt doc file to describe our
7534 interpretation and extensions to the socks protocols.
7535 - Add a ContactInfo option, which gets published in descriptor.
7536 - Publish OR uptime in descriptor (and thus in directory) too.
7537 - Write tor version at the top of each log file
7538 - New docs in the tarball:
7540 - Document that you should proxy your SSL traffic too.
7543 Changes in version 0.0.7.2 - 2004-07-07
7544 o A better fix for the 0.0.0.0 problem, that will hopefully
7545 eliminate the remaining related assertion failures.
7548 Changes in version 0.0.7.1 - 2004-07-04
7549 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
7550 since internally we use 0.0.0.0 to signify "not yet resolved".
7553 Changes in version 0.0.7 - 2004-06-07
7554 o Updated the man page to reflect the new features.
7557 Changes in version 0.0.7rc2 - 2004-06-06
7558 o Changes from 0.0.7rc1:
7559 - Make it build on Win32 again.
7560 o Changes from 0.0.6.2:
7561 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
7565 Changes in version 0.0.7rc1 - 2004-06-02
7567 - On sighup, we were adding another log without removing the first
7568 one. So log messages would get duplicated n times for n sighups.
7569 - Several cases of using a connection after we'd freed it. The
7570 problem was that connections that are pending resolve are in both
7571 the pending_resolve tree, and also the circuit's resolving_streams
7572 list. When you want to remove one, you must remove it from both.
7573 - Fix a double-mark-for-close where an end cell arrived for a
7574 resolving stream, and then the resolve failed.
7575 - Check directory signatures based on name of signer, not on whom
7576 we got the directory from. This will let us cache directories more
7579 - Crank up some of our constants to handle more users.
7582 Changes in version 0.0.7pre1 - 2004-06-02
7583 o Fixes for crashes and other obnoxious bugs:
7584 - Fix an epipe bug: sometimes when directory connections failed
7585 to connect, we would give them a chance to flush before closing
7587 - When we detached from a circuit because of resolvefailed, we
7588 would immediately try the same circuit twice more, and then
7589 give up on the resolve thinking we'd tried three different
7591 - Limit the number of intro circuits we'll attempt to build for a
7592 hidden service per 15-minute period.
7593 - Check recommended-software string *early*, before actually parsing
7594 the directory. Thus we can detect an obsolete version and exit,
7595 even if the new directory format doesn't parse.
7596 o Fixes for security bugs:
7597 - Remember which nodes are dirservers when you startup, and if a
7598 random OR enables his dirport, don't automatically assume he's
7599 a trusted dirserver.
7601 - Directory connections were asking the wrong poll socket to
7602 start writing, and not asking themselves to start writing.
7603 - When we detached from a circuit because we sent a begin but
7604 didn't get a connected, we would use it again the first time;
7605 but after that we would correctly switch to a different one.
7606 - Stop warning when the first onion decrypt attempt fails; they
7607 will sometimes legitimately fail now that we rotate keys.
7608 - Override unaligned-access-ok check when $host_cpu is ia64 or
7609 arm. Apparently they allow it but the kernel whines.
7610 - Dirservers try to reconnect periodically too, in case connections
7612 - Fix some memory leaks in directory servers.
7613 - Allow backslash in Win32 filenames.
7614 - Made Tor build complain-free on FreeBSD, hopefully without
7615 breaking other BSD builds. We'll see.
7617 - Doxygen markup on all functions and global variables.
7618 - Make directory functions update routerlist, not replace it. So
7619 now directory disagreements are not so critical a problem.
7620 - Remove the upper limit on number of descriptors in a dirserver's
7621 directory (not that we were anywhere close).
7622 - Allow multiple logfiles at different severity ranges.
7623 - Allow *BindAddress to specify ":port" rather than setting *Port
7624 separately. Allow multiple instances of each BindAddress config
7625 option, so you can bind to multiple interfaces if you want.
7626 - Allow multiple exit policy lines, which are processed in order.
7627 Now we don't need that huge line with all the commas in it.
7628 - Enable accept/reject policies on SOCKS connections, so you can bind
7629 to 0.0.0.0 but still control who can use your OP.
7632 Changes in version 0.0.6.2 - 2004-05-16
7633 o Our integrity-checking digest was checking only the most recent cell,
7634 not the previous cells like we'd thought.
7635 Thanks to Stefan Mark for finding the flaw!
7638 Changes in version 0.0.6.1 - 2004-05-06
7639 o Fix two bugs in our AES counter-mode implementation (this affected
7640 onion-level stream encryption, but not TLS-level). It turns
7641 out we were doing something much more akin to a 16-character
7642 polyalphabetic cipher. Oops.
7643 Thanks to Stefan Mark for finding the flaw!
7644 o Retire moria3 as a directory server, and add tor26 as a directory
7648 Changes in version 0.0.6 - 2004-05-02
7652 Changes in version 0.0.6rc4 - 2004-05-01
7653 o Update the built-in dirservers list to use the new directory format
7654 o Fix a rare seg fault: if a node offering a hidden service attempts
7655 to build a circuit to Alice's rendezvous point and fails before it
7656 reaches the last hop, it retries with a different circuit, but
7658 o Handle windows socket errors correctly.
7661 Changes in version 0.0.6rc3 - 2004-04-28
7662 o Don't expire non-general excess circuits (if we had enough
7663 circuits open, we were expiring rendezvous circuits -- even
7664 when they had a stream attached. oops.)
7665 o Fetch randomness from /dev/urandom better (not via fopen/fread)
7666 o Better debugging for tls errors
7667 o Some versions of openssl have an SSL_pending function that erroneously
7668 returns bytes when there is a non-application record pending.
7669 o Set Content-Type on the directory and hidserv descriptor.
7670 o Remove IVs from cipher code, since AES-ctr has none.
7671 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
7672 o We were using an array of length zero in a few places.
7673 o win32's gethostbyname can't resolve an IP to an IP.
7674 o win32's close can't close a socket.
7677 Changes in version 0.0.6rc2 - 2004-04-26
7678 o Fix a bug where we were closing tls connections intermittently.
7679 It turns out openssl keeps its errors around -- so if an error
7680 happens, and you don't ask about it, and then another openssl
7681 operation happens and succeeds, and you ask if there was an error,
7682 it tells you about the first error. Fun fun.
7683 o Fix a bug that's been lurking since 27 may 03 (!)
7684 When passing back a destroy cell, we would use the wrong circ id.
7685 'Mostly harmless', but still worth fixing.
7686 o Since we don't support truncateds much, don't bother sending them;
7687 just close the circ.
7688 o check for <machine/limits.h> so we build on NetBSD again (I hope).
7689 o don't crash if a conn that sent a begin has suddenly lost its circuit
7690 (this was quite rare).
7693 Changes in version 0.0.6rc1 - 2004-04-25
7694 o We now rotate link (tls context) keys and onion keys.
7695 o CREATE cells now include oaep padding, so you can tell
7696 if you decrypted them correctly.
7697 o Add bandwidthburst to server descriptor.
7698 o Directories now say which dirserver signed them.
7699 o Use a tor_assert macro that logs failed assertions too.
7702 Changes in version 0.0.6pre5 - 2004-04-18
7703 o changes from 0.0.6pre4:
7704 - make tor build on broken freebsd 5.2 installs
7705 - fix a failed assert when you try an intro point, get a nack, and try
7706 a second one and it works.
7707 - when alice uses a port that the hidden service doesn't accept,
7708 it now sends back an end cell (denied by exit policy). otherwise
7709 alice would just have to wait to time out.
7710 - fix another rare bug: when we had tried all the intro
7711 points for a hidden service, we fetched the descriptor
7712 again, but we left our introcirc thinking it had already
7713 sent an intro, so it kept waiting for a response...
7714 - bugfix: when you sleep your hidden-service laptop, as soon
7715 as it wakes up it tries to upload a service descriptor, but
7716 socketpair fails for some reason (localhost not up yet?).
7717 now we simply give up on that upload, and we'll try again later.
7718 i'd still like to find the bug though.
7719 - if an intro circ waiting for an ack dies before getting one, then
7721 - we were reusing stale service descriptors and refetching usable
7725 Changes in version 0.0.6pre4 - 2004-04-14
7726 o changes from 0.0.6pre3:
7727 - when bob fails to connect to the rendezvous point, and his
7728 circ didn't fail because of the rendezvous point itself, then
7729 he retries a couple of times
7730 - we expire introduction and rendezvous circs more thoroughly
7731 (sometimes they were hanging around forever)
7732 - we expire unattached rendezvous streams that have been around
7733 too long (they were sticking around forever).
7734 - fix a measly fencepost error that was crashing everybody with
7738 Changes in version 0.0.6pre3 - 2004-04-14
7739 o changes from 0.0.6pre2:
7740 - make hup work again
7741 - fix some memory leaks for dirservers
7742 - allow more skew in rendezvous descriptor timestamps, to help
7743 handle people like blanu who don't know what time it is
7744 - normal circs are 3 hops, but some rend/intro circs are 4, if
7745 the initiator doesn't get to choose the last hop
7746 - send acks for introductions, so alice can know whether to try
7748 - bob publishes intro points more correctly
7749 o changes from 0.0.5:
7750 - fix an assert trigger that's been plaguing us since the days
7751 of 0.0.2prexx (thanks weasel!)
7752 - retry stream correctly when we fail to connect because of
7753 exit-policy-reject (should try another) or can't-resolve-address
7754 (also should try another, because dns on random internet servers
7756 - when we hup a dirserver and we've *removed* a server from the
7757 approved-routers list, now we remove that server from the
7758 in-memory directories too
7761 Changes in version 0.0.6pre2 - 2004-04-08
7762 o We fixed our base32 implementation. Now it works on all architectures.
7765 Changes in version 0.0.6pre1 - 2004-04-08
7767 - Hidden services and rendezvous points are implemented. Go to
7768 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
7769 hidden services. (This only works via a socks4a proxy such as
7770 Privoxy, and currently it's quite slow.)
7773 Changes in version 0.0.5 - 2004-03-30
7777 Changes in version 0.0.5rc3 - 2004-03-29
7778 o Install torrc as torrc.sample -- we no longer clobber your
7780 o Re-enable recommendedversion checking (we broke it in rc2, oops)
7781 o Add in a 'notice' log level for things the operator should hear
7782 but that aren't warnings
7785 Changes in version 0.0.5rc2 - 2004-03-29
7786 o Hold socks connection open until reply is flushed (if possible)
7787 o Make exit nodes resolve IPs to IPs immediately, rather than asking
7788 the dns farm to do it.
7789 o Fix c99 aliasing warnings in rephist.c
7790 o Don't include server descriptors that are older than 24 hours in the
7792 o Give socks 'reject' replies their whole 15s to attempt to flush,
7793 rather than seeing the 60s timeout and assuming the flush had failed.
7794 o Clean automake droppings from the cvs repository
7797 Changes in version 0.0.5rc1 - 2004-03-28
7798 o Fix mangled-state bug in directory fetching (was causing sigpipes).
7799 o Only build circuits after we've fetched the directory: clients were
7800 using only the directory servers before they'd fetched a directory.
7801 This also means longer startup time; so it goes.
7802 o Fix an assert trigger where an OP would fail to handshake, and we'd
7803 expect it to have a nickname.
7804 o Work around a tsocks bug: do a socks reject when AP connection dies
7805 early, else tsocks goes into an infinite loop.
7808 Changes in version 0.0.4 - 2004-03-26
7809 o When connecting to a dirserver or OR and the network is down,
7813 Changes in version 0.0.3 - 2004-03-26
7814 o Warn and fail if server chose a nickname with illegal characters
7815 o Port to Solaris and Sparc:
7816 - include missing header fcntl.h
7817 - have autoconf find -lsocket -lnsl automatically
7818 - deal with hardware word alignment
7819 - make uname() work (solaris has a different return convention)
7820 - switch from using signal() to sigaction()
7821 o Preliminary work on reputation system:
7822 - Keep statistics on success/fail of connect attempts; they're published
7823 by kill -USR1 currently.
7824 - Add a RunTesting option to try to learn link state by creating test
7825 circuits, even when SocksPort is off.
7826 - Remove unused open circuits when there are too many.
7829 Changes in version 0.0.2 - 2004-03-19
7830 - Include strlcpy and strlcat for safer string ops
7831 - define INADDR_NONE so we compile (but still not run) on solaris
7834 Changes in version 0.0.2pre27 - 2004-03-14
7836 - Allow internal tor networks (we were rejecting internal IPs,
7837 now we allow them if they're set explicitly).
7838 - And fix a few endian issues.
7841 Changes in version 0.0.2pre26 - 2004-03-14
7843 - If a stream times out after 15s without a connected cell, don't
7844 try that circuit again: try a new one.
7845 - Retry streams at most 4 times. Then give up.
7846 - When a dirserver gets a descriptor from an unknown router, it
7847 logs its fingerprint (so the dirserver operator can choose to
7848 accept it even without mail from the server operator).
7849 - Inform unapproved servers when we reject their descriptors.
7850 - Make tor build on Windows again. It works as a client, who knows
7852 - Clearer instructions in the torrc for how to set up a server.
7853 - Be more efficient about reading fd's when our global token bucket
7854 (used for rate limiting) becomes empty.
7856 - Stop asserting that computers always go forward in time. It's
7858 - When we sent a cell (e.g. destroy) and then marked an OR connection
7859 expired, we might close it before finishing a flush if the other
7860 side isn't reading right then.
7861 - Don't allow dirservers to start if they haven't defined
7863 - We were caching transient dns failures. Oops.
7864 - Prevent servers from publishing an internal IP as their address.
7865 - Address a strcat vulnerability in circuit.c
7868 Changes in version 0.0.2pre25 - 2004-03-04
7870 - Put the OR's IP in its router descriptor, not its fqdn. That way
7871 we'll stop being stalled by gethostbyname for nodes with flaky dns,
7874 - If the user typed in an address that didn't resolve, the server
7878 Changes in version 0.0.2pre24 - 2004-03-03
7880 - Fix an assertion failure in dns.c, where we were trying to dequeue
7881 a pending dns resolve even if it wasn't pending
7882 - Fix a spurious socks5 warning about still trying to write after the
7883 connection is finished.
7884 - Hold certain marked_for_close connections open until they're finished
7885 flushing, rather than losing bytes by closing them too early.
7886 - Correctly report the reason for ending a stream
7887 - Remove some duplicate calls to connection_mark_for_close
7888 - Put switch_id and start_daemon earlier in the boot sequence, so it
7889 will actually try to chdir() to options.DataDirectory
7890 - Make 'make test' exit(1) if a test fails; fix some unit tests
7891 - Make tor fail when you use a config option it doesn't know about,
7892 rather than warn and continue.
7893 - Make --version work
7894 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
7897 Changes in version 0.0.2pre23 - 2004-02-29
7899 - Print a statement when the first circ is finished, so the user
7901 - If a relay cell is unrecognized at the end of the circuit,
7902 send back a destroy. (So attacks to mutate cells are more
7904 - New config option 'excludenodes' to avoid certain nodes for circuits.
7905 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
7906 so you can collect coredumps there.
7908 - Fix a bug in tls flushing where sometimes data got wedged and
7909 didn't flush until more data got sent. Hopefully this bug was
7910 a big factor in the random delays we were seeing.
7911 - Make 'connected' cells include the resolved IP, so the client
7912 dns cache actually gets populated.
7913 - Disallow changing from ORPort=0 to ORPort>0 on hup.
7914 - When we time-out on a stream and detach from the circuit, send an
7915 end cell down it first.
7916 - Only warn about an unknown router (in exitnodes, entrynodes,
7917 excludenodes) after we've fetched a directory.
7920 Changes in version 0.0.2pre22 - 2004-02-26
7922 - Servers publish less revealing uname information in descriptors.
7923 - More memory tracking and assertions, to crash more usefully when
7925 - If the default torrc isn't there, just use some default defaults.
7926 Plus provide an internal dirservers file if they don't have one.
7927 - When the user tries to use Tor as an http proxy, give them an http
7928 501 failure explaining that we're a socks proxy.
7929 - Dump a new router.desc on hup, to help confused people who change
7930 their exit policies and then wonder why router.desc doesn't reflect
7932 - Clean up the generic tor.sh init script that we ship with.
7934 - If the exit stream is pending on the resolve, and a destroy arrives,
7935 then the stream wasn't getting removed from the pending list. I
7936 think this was the one causing recent server crashes.
7937 - Use a more robust poll on OSX 10.3, since their poll is flaky.
7938 - When it couldn't resolve any dirservers, it was useless from then on.
7939 Now it reloads the RouterFile (or default dirservers) if it has no
7941 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
7942 many users don't even *have* a /usr/local/sbin/.
7945 Changes in version 0.0.2pre21 - 2004-02-18
7947 - There's a ChangeLog file that actually reflects the changelog.
7948 - There's a 'torify' wrapper script, with an accompanying
7949 tor-tsocks.conf, that simplifies the process of using tsocks for
7950 tor. It even has a man page.
7951 - The tor binary gets installed to sbin rather than bin now.
7952 - Retry streams where the connected cell hasn't arrived in 15 seconds
7953 - Clean up exit policy handling -- get the default out of the torrc,
7954 so we can update it without forcing each server operator to fix
7956 - Allow imaps and pop3s in default exit policy
7958 - Prevent picking middleman nodes as the last node in the circuit
7961 Changes in version 0.0.2pre20 - 2004-01-30
7963 - We now have a deb package, and it's in debian unstable. Go to
7965 - I've split the TotalBandwidth option into BandwidthRate (how many
7966 bytes per second you want to allow, long-term) and
7967 BandwidthBurst (how many bytes you will allow at once before the cap
7968 kicks in). This better token bucket approach lets you, say, set
7969 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
7970 performance while not exceeding your monthly bandwidth quota.
7971 - Push out a tls record's worth of data once you've got it, rather
7972 than waiting until you've read everything waiting to be read. This
7973 may improve performance by pipelining better. We'll see.
7974 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
7975 from failed circuits (if they haven't been connected yet) and attach
7977 - Expire old streams that haven't managed to connect. Some day we'll
7978 have them reattach to new circuits instead.
7981 - Fix several memory leaks that were causing servers to become bloated
7983 - Fix a few very rare assert triggers. A few more remain.
7984 - Setuid to User _before_ complaining about running as root.
7987 Changes in version 0.0.2pre19 - 2004-01-07
7989 - Fix deadlock condition in dns farm. We were telling a child to die by
7990 closing the parent's file descriptor to him. But newer children were
7991 inheriting the open file descriptor from the parent, and since they
7992 weren't closing it, the socket never closed, so the child never read
7993 eof, so he never knew to exit. Similarly, dns workers were holding
7994 open other sockets, leading to all sorts of chaos.
7995 - New cleaner daemon() code for forking and backgrounding.
7996 - If you log to a file, it now prints an entry at the top of the
7997 logfile so you know it's working.
7998 - The onionskin challenge length was 30 bytes longer than necessary.
7999 - Started to patch up the spec so it's not quite so out of date.
8002 Changes in version 0.0.2pre18 - 2004-01-02
8004 - Fix endian issues with the 'integrity' field in the relay header.
8005 - Fix a potential bug where connections in state
8006 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
8009 Changes in version 0.0.2pre17 - 2003-12-30
8011 - Made --debuglogfile (or any second log file, actually) work.
8012 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
8013 adversary could force us into an infinite loop.
8016 - Each onionskin handshake now includes a hash of the computed key,
8017 to prove the server's identity and help perfect forward secrecy.
8018 - Changed cell size from 256 to 512 bytes (working toward compatibility
8020 - Changed cell length to 2 bytes, and moved it to the relay header.
8021 - Implemented end-to-end integrity checking for the payloads of
8023 - Separated streamid from 'recognized' (otherwise circuits will get
8024 messed up when we try to have streams exit from the middle). We
8025 use the integrity-checking to confirm that a cell is addressed to
8027 - Randomize the initial circid and streamid values, so an adversary who
8028 breaks into a node can't learn how many circuits or streams have
8032 Changes in version 0.0.2pre16 - 2003-12-14
8034 - Fixed a bug that made HUP trigger an assert
8035 - Fixed a bug where a circuit that immediately failed wasn't being
8036 counted as a failed circuit in counting retries.
8039 - Now we close the circuit when we get a truncated cell: otherwise we're
8040 open to an anonymity attack where a bad node in the path truncates
8041 the circuit and then we open streams at him.
8042 - Add port ranges to exit policies
8043 - Add a conservative default exit policy
8044 - Warn if you're running tor as root
8045 - on HUP, retry OR connections and close/rebind listeners
8046 - options.EntryNodes: try these nodes first when picking the first node
8047 - options.ExitNodes: if your best choices happen to include any of
8048 your preferred exit nodes, you choose among just those preferred
8050 - options.ExcludedNodes: nodes that are never picked in path building
8053 Changes in version 0.0.2pre15 - 2003-12-03
8054 o Robustness and bugfixes:
8055 - Sometimes clients would cache incorrect DNS resolves, which would
8056 really screw things up.
8057 - An OP that goes offline would slowly leak all its sockets and stop
8059 - A wide variety of bugfixes in exit node selection, exit policy
8060 handling, and processing pending streams when a new circuit is
8062 - Pick nodes for a path only from those the directory says are up
8063 - Choose randomly from all running dirservers, not always the first one
8064 - Increase allowed http header size for directory fetch.
8065 - Stop writing to stderr (if we're daemonized it will be closed).
8066 - Enable -g always, so cores will be more useful to me.
8067 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
8070 - Wrote a man page. It lists commonly used options.
8073 - Change default loglevel to warn.
8074 - Make PidFile default to null rather than littering in your CWD.
8075 - OnionRouter config option is now obsolete. Instead it just checks
8077 - Moved to a single unified torrc file for both clients and servers.
8080 Changes in version 0.0.2pre14 - 2003-11-29
8081 o Robustness and bugfixes:
8082 - Force the admin to make the DataDirectory himself
8083 - to get ownership/permissions right
8084 - so clients no longer make a DataDirectory and then never use it
8085 - fix bug where a client who was offline for 45 minutes would never
8086 pull down a directory again
8087 - fix (or at least hide really well) the dns assert bug that was
8088 causing server crashes
8089 - warnings and improved robustness wrt clockskew for certs
8090 - use the native daemon(3) to daemonize, when available
8091 - exit if bind() fails
8092 - exit if neither socksport nor orport is defined
8093 - include our own tor_timegm (Win32 doesn't have its own)
8094 - bugfix for win32 with lots of connections
8095 - fix minor bias in PRNG
8096 - make dirserver more robust to corrupt cached directory
8099 - Wrote the design document (woo)
8101 o Circuit building and exit policies:
8102 - Circuits no longer try to use nodes that the directory has told them
8104 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
8105 bitcounts (18.0.0.0/8).
8106 - Make AP connections standby for a circuit if no suitable circuit
8107 exists, rather than failing
8108 - Circuits choose exit node based on addr/port, exit policies, and
8109 which AP connections are standing by
8110 - Bump min pathlen from 2 to 3
8111 - Relay end cells have a payload to describe why the stream ended.
8112 - If the stream failed because of exit policy, try again with a new
8114 - Clients have a dns cache to remember resolved addresses.
8115 - Notice more quickly when we have no working circuits
8118 - APPort is now called SocksPort
8119 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
8121 - RecommendedVersions is now a config variable rather than
8122 hardcoded (for dirservers)
8123 - Reloads config on HUP
8124 - Usage info on -h or --help
8125 - If you set User and Group config vars, it'll setu/gid to them.
8128 Changes in version 0.0.2pre13 - 2003-10-19
8129 o General stability:
8130 - SSL_write no longer fails when it returns WANTWRITE and the number
8131 of bytes in the buf has changed by the next SSL_write call.
8132 - Fix segfault fetching directory when network is down
8133 - Fix a variety of minor memory leaks
8134 - Dirservers reload the fingerprints file on HUP, so I don't have
8135 to take down the network when I approve a new router
8136 - Default server config file has explicit Address line to specify fqdn
8139 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
8140 - Make listener connections not ever alloc bufs
8142 o Autoconf improvements:
8143 - don't clobber an external CFLAGS in ./configure
8144 - Make install now works
8145 - create var/lib/tor on make install
8146 - autocreate a tor.sh initscript to help distribs
8147 - autocreate the torrc and sample-server-torrc with correct paths
8149 o Log files and Daemonizing now work:
8150 - If --DebugLogFile is specified, log to it at -l debug
8151 - If --LogFile is specified, use it instead of commandline
8152 - If --RunAsDaemon is set, tor forks and backgrounds on startup