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