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