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