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