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