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