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