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