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