1 Changes in version 0.2.2.15-alpha - 2010-08-18
3 - Stop assigning the HSDir flag to relays that disable their
4 DirPort (and thus will refuse to answer directory requests). This
5 fix should dramatically improve the reachability of hidden services:
6 hidden services and hidden service clients pick six HSDir relays
7 to store and retrieve the hidden service descriptor, and currently
8 about half of the HSDir relays will refuse to work. Bugfix on
9 0.2.0.10-alpha; fixes part of bug 1693.
10 - The PerConnBWRate and Burst config options, along with the
11 bwconnrate and bwconnburst consensus params, initialized each conn's
12 token bucket values only when the connection is established. Now we
13 update them if the config options change, and update them every time
14 we get a new consensus. Otherwise we can encounter an ugly edge
15 case where we initialize an OR conn to client-level bandwidth,
16 but then later the relay joins the consensus and we leave it
17 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
18 - Fix a regression that caused Tor to rebind its ports if it receives
19 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
22 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
23 should give us approximately 40-50% more Guard-flagged nodes,
24 improving the anonymity the Tor network can provide and also
25 decreasing the dropoff in throughput that relays experience when
26 they first get the Guard flag.
27 - Allow enabling or disabling the *Statistics config options while
31 - Update to the August 1 2010 Maxmind GeoLite Country database.
32 - Have the controller interface give a more useful message than
33 "Internal Error" in response to failed GETINFO requests.
34 - Warn when the same option is provided more than once in a torrc
35 file, on the command line, or in a single SETCONF statement, and
36 the option is one that only accepts a single line. Closes bug 1384.
37 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
39 - Add support for the country code "{??}" in torrc options like
40 ExcludeNodes, to indicate all routers of unknown country. Closes
42 - Relays report the number of bytes spent on answering directory
43 requests in extra-info descriptors similar to {read,write}-history.
44 Implements enhancement 1790.
46 o Minor bugfixes (on 0.2.1.x and earlier):
47 - Complain if PublishServerDescriptor is given multiple arguments that
48 include 0 or 1. This configuration will be rejected in the future.
49 Bugfix on 0.2.0.1-alpha; closes bug 1107.
50 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
51 Bugfix on 0.2.0.13-alpha; closes bug 928.
52 - Change "Application request when we're believed to be offline."
53 notice to "Application request when we haven't used client
54 functionality lately.", to clarify that it's not an error. Bugfix
55 on 0.0.9.3; fixes bug 1222.
56 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
57 would return "551 Internal error" rather than "552 Unrecognized key
58 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
59 - Users can't configure a regular relay to be their bridge. It didn't
60 work because when Tor fetched the bridge descriptor, it found
61 that it already had it, and didn't realize that the purpose of the
62 descriptor had changed. Now we replace routers with a purpose other
63 than bridge with bridge descriptors when fetching them. Bugfix on
64 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
65 refetch the descriptor with router purpose 'general', disabling
67 - Fix a rare bug in rend_fn unit tests: we would fail a test when
68 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
69 on 0.2.0.10-alpha; fixes bug 1808.
70 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
71 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
72 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
73 Servers can start sending this code when enough clients recognize
74 it. Also update the spec to reflect this new reason. Bugfix on
75 0.1.0.1-rc; fixes part of bug 1793.
76 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
77 when we switch from being a public relay to a bridge. Otherwise
78 there will still be clients that see the relay in their consensus,
79 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
81 - Instead of giving an assertion failure on an internal mismatch
82 on estimated freelist size, just log a BUG warning and try later.
83 Mitigates but does not fix bug 1125.
84 - Fix an assertion failure that could occur in caches or bridge users
85 when using a very short voting interval on a testing network.
86 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
88 o Minor bugfixes (on 0.2.2.x):
89 - Alter directory authorities to always consider Exit-flagged nodes
90 as potential Guard nodes in their votes. The actual decision to
91 use Exits as Guards is done in the consensus bandwidth weights.
92 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
93 - When the controller is reporting the purpose of circuits that
94 didn't finish building before the circuit build timeout, it was
95 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
96 - Our libevent version parsing code couldn't handle versions like
97 1.4.14b-stable and incorrectly warned the user about using an
98 old and broken version of libevent. Treat 1.4.14b-stable like
99 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
101 - Don't use substitution references like $(VAR:MOD) when
102 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
103 '$(:x)' to 'x' rather than the empty string. This bites us in
104 doc/ when configured with --disable-asciidoc. Bugfix on
105 0.2.2.9-alpha; fixes bug 1773.
106 - Remove a spurious hidden service server-side log notice about
107 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
109 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
111 - Correctly report written bytes on linked connections. Found while
112 implementing 1790. Bugfix on 0.2.2.4-alpha.
113 - Fix three memory leaks: one in circuit_build_times_parse_state(),
114 one in dirvote_add_signatures_to_pending_consensus(), and one every
115 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
116 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
118 o Code simplifications and refactoring:
119 - Take a first step towards making or.h smaller by splitting out
120 function definitions for all source files in src/or/. Leave
121 structures and defines in or.h for now.
122 - Remove a bunch of unused function declarations as well as a block of
123 #if 0'd code from the unit tests. Closes bug 1824.
124 - New unit tests for exit-port history statistics; refactored exit
125 statistics code to be more easily tested.
126 - Remove the old debian/ directory from the main Tor distribution.
127 The official Tor-for-debian git repository lives at the URL
128 https://git.torproject.org/debian/tor.git
131 Changes in version 0.2.2.14-alpha - 2010-07-12
132 Tor 0.2.2.14-alpha greatly improves client-side handling of
133 circuit build timeouts, which are used to estimate speed and improve
134 performance. We also move to a much better GeoIP database, port Tor to
135 Windows CE, introduce new compile flags that improve code security,
136 add an eighth v3 directory authority, and address a lot of more
140 - Tor directory authorities no longer crash when started with a
141 cached-microdesc-consensus file in their data directory. Bugfix
142 on 0.2.2.6-alpha; fixes bug 1532.
143 - Treat an unset $HOME like an empty $HOME rather than triggering an
144 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
145 - Ignore negative and large circuit build timeout values that can
146 happen during a suspend or hibernate. These values caused various
147 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
148 - Alter calculation of Pareto distribution parameter 'Xm' for
149 Circuit Build Timeout learning to use the weighted average of the
150 top N=3 modes (because we have three entry guards). Considering
151 multiple modes should improve the timeout calculation in some cases,
152 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
154 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
155 right censored distribution model. This approach improves over the
156 synthetic timeout generation approach that was producing insanely
157 high timeout values. Now we calculate build timeouts using truncated
158 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
159 - Do not close circuits that are under construction when they reach
160 the circuit build timeout. Instead, leave them building (but do not
161 use them) for up until the time corresponding to the 95th percentile
162 on the Pareto CDF or 60 seconds, whichever is greater. This is done
163 to provide better data for the new Pareto model. This percentile
164 can be controlled by the consensus.
167 - Move to the June 2010 Maxmind GeoLite country db (rather than the
168 June 2009 ip-to-country GeoIP db) for our statistics that count
169 how many users relays are seeing from each country. Now we have
170 more accurate data for many African countries.
171 - Port Tor to build and run correctly on Windows CE systems, using
172 the wcecompat library. Contributed by Valerio Lupi.
173 - New "--enable-gcc-hardening" ./configure flag (off by default)
174 to turn on gcc compile time hardening options. It ensures
175 that signed ints have defined behavior (-fwrapv), enables
176 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
177 with canaries (-fstack-protector-all), turns on ASLR protection if
178 supported by the kernel (-fPIE, -pie), and adds additional security
179 related warnings. Verified to work on Mac OS X and Debian Lenny.
180 - New "--enable-linker-hardening" ./configure flag (off by default)
181 to turn on ELF specific hardening features (relro, now). This does
182 not work with Mac OS X or any other non-ELF binary format.
184 o New directory authorities:
185 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
189 - New config option "WarnUnsafeSocks 0" disables the warning that
190 occurs whenever Tor receives only an IP address instead of a
191 hostname. Setups that do DNS locally over Tor are fine, and we
192 shouldn't spam the logs in that case.
193 - Convert the HACKING file to asciidoc, and add a few new sections
194 to it, explaining how we use Git, how we make changelogs, and
195 what should go in a patch.
196 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
197 event, to give information on the current rate of circuit timeouts
198 over our stored history.
199 - Add ability to disable circuit build time learning via consensus
200 parameter and via a LearnCircuitBuildTimeout config option. Also
201 automatically disable circuit build time calculation if we are
202 either a AuthoritativeDirectory, or if we fail to write our state
203 file. Fixes bug 1296.
204 - More gracefully handle corrupt state files, removing asserts
205 in favor of saving a backup and resetting state.
206 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
210 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
212 - When a2x fails, mention that the user could disable manpages instead
213 of trying to fix their asciidoc installation.
214 - Where available, use Libevent 2.0's periodic timers so that our
215 once-per-second cleanup code gets called even more closely to
216 once per second than it would otherwise. Fixes bug 943.
217 - If you run a bridge that listens on multiple IP addresses, and
218 some user configures a bridge address that uses a different IP
219 address than your bridge writes in its router descriptor, and the
220 user doesn't specify an identity key, their Tor would discard the
221 descriptor because "it isn't one of our configured bridges", and
222 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
223 Bugfix on 0.2.0.3-alpha.
224 - If OpenSSL fails to make a duplicate of a private or public key, log
225 an error message and try to exit cleanly. May help with debugging
226 if bug 1209 ever remanifests.
227 - Save a couple bytes in memory allocation every time we escape
228 certain characters in a string. Patch from Florian Zumbiehl.
229 - Make it explicit that we don't cannibalize one-hop circuits. This
230 happens in the wild, but doesn't turn out to be a problem because
231 we fortunately don't use those circuits. Many thanks to outofwords
232 for the initial analysis and to swissknife who confirmed that
233 two-hop circuits are actually created.
234 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
235 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
236 - Eliminate a case where a circuit build time warning was displayed
237 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
240 Changes in version 0.2.1.26 - 2010-05-02
241 Tor 0.2.1.26 addresses the recent connection and memory overload
242 problems we've been seeing on relays, especially relays with their
243 DirPort open. If your relay has been crashing, or you turned it off
244 because it used too many resources, give this release a try.
246 This release also fixes yet another instance of broken OpenSSL libraries
247 that was causing some relays to drop out of the consensus.
250 - Teach relays to defend themselves from connection overload. Relays
251 now close idle circuits early if it looks like they were intended
252 for directory fetches. Relays are also more aggressive about closing
253 TLS connections that have no circuits on them. Such circuits are
254 unlikely to be re-used, and tens of thousands of them were piling
255 up at the fast relays, causing the relays to run out of sockets
256 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
257 their directory fetches over TLS).
258 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
259 that claim to be earlier than 0.9.8m, but which have in reality
260 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
261 behavior. Possible fix for some cases of bug 1346.
262 - Directory mirrors were fetching relay descriptors only from v2
263 directory authorities, rather than v3 authorities like they should.
264 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
265 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
268 - Finally get rid of the deprecated and now harmful notion of "clique
269 mode", where directory authorities maintain TLS connections to
273 - In the util/threads test, no longer free the test_mutex before all
274 worker threads have finished. Bugfix on 0.2.1.6-alpha.
275 - The master thread could starve the worker threads quite badly on
276 certain systems, causing them to run only partially in the allowed
277 window. This resulted in test failures. Now the master thread sleeps
278 occasionally for a few microseconds while the two worker-threads
279 compete for the mutex. Bugfix on 0.2.0.1-alpha.
282 Changes in version 0.2.2.13-alpha - 2010-04-24
283 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
284 problems we've been seeing on relays, especially relays with their
285 DirPort open. If your relay has been crashing, or you turned it off
286 because it used too many resources, give this release a try.
289 - Teach relays to defend themselves from connection overload. Relays
290 now close idle circuits early if it looks like they were intended
291 for directory fetches. Relays are also more aggressive about closing
292 TLS connections that have no circuits on them. Such circuits are
293 unlikely to be re-used, and tens of thousands of them were piling
294 up at the fast relays, causing the relays to run out of sockets
295 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
296 their directory fetches over TLS).
299 - Finally get rid of the deprecated and now harmful notion of "clique
300 mode", where directory authorities maintain TLS connections to
302 - Directory authorities now do an immediate reachability check as soon
303 as they hear about a new relay. This change should slightly reduce
304 the time between setting up a relay and getting listed as running
305 in the consensus. It should also improve the time between setting
306 up a bridge and seeing use by bridge users.
307 - Directory authorities no longer launch a TLS connection to every
308 relay as they startup. Now that we have 2k+ descriptors cached,
309 the resulting network hiccup is becoming a burden. Besides,
310 authorities already avoid voting about Running for the first half
311 hour of their uptime.
314 Changes in version 0.2.2.12-alpha - 2010-04-20
315 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
316 handle and vote on descriptors. It was causing relays to drop out of
320 - Many relays have been falling out of the consensus lately because
321 not enough authorities know about their descriptor for them to get
322 a majority of votes. When we deprecated the v2 directory protocol,
323 we got rid of the only way that v3 authorities can hear from each
324 other about other descriptors. Now authorities examine every v3
325 vote for new descriptors, and fetch them from that authority. Bugfix
327 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
328 and a warning in or.h related to bandwidth_weight_rule_t that
329 prevented clean compile on OS X. Fixes bug 1363; bugfix on
331 - Fix a segfault on relays when DirReqStatistics is enabled
332 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
336 - Demote a confusing TLS warning that relay operators might get when
337 someone tries to talk to their OrPort. It is neither the operator's
338 fault nor can they do anything about it. Fixes bug 1364; bugfix
342 Changes in version 0.2.2.11-alpha - 2010-04-15
343 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
344 libraries that was causing some relays to drop out of the consensus.
347 - Directory mirrors were fetching relay descriptors only from v2
348 directory authorities, rather than v3 authorities like they should.
349 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
350 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
351 - Fix a parsing error that made every possible value of
352 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
353 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
354 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
355 about the option without breaking older ones.
356 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
357 that claim to be earlier than 0.9.8m, but which have in reality
358 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
359 behavior. Possible fix for some cases of bug 1346.
362 - Experiment with a more aggressive approach to preventing clients
363 from making one-hop exit streams. Exit relays who want to try it
364 out can set "RefuseUnknownExits 1" in their torrc, and then look
365 for "Attempt by %s to open a stream" log messages. Let us know
367 - Add support for statically linking zlib by specifying
368 --enable-static-zlib, to go with our support for statically linking
369 openssl and libevent. Resolves bug 1358.
372 - Fix a segfault that happens whenever a Tor client that is using
373 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
375 - When we cleaned up the contrib/tor-exit-notice.html file, we left
376 out the first line. Fixes bug 1295.
377 - When building the manpage from a tarball, we required asciidoc, but
378 the asciidoc -> roff/html conversion was already done for the
379 tarball. Make 'make' complain only when we need asciidoc (either
380 because we're compiling directly from git, or because we altered
381 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
382 - When none of the directory authorities vote on any params, Tor
383 segfaulted when trying to make the consensus from the votes. We
384 didn't trigger the bug in practice, because authorities do include
385 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
388 - In the util/threads test, no longer free the test_mutex before all
389 worker threads have finished. Bugfix on 0.2.1.6-alpha.
390 - The master thread could starve the worker threads quite badly on
391 certain systems, causing them to run only partially in the allowed
392 window. This resulted in test failures. Now the master thread sleeps
393 occasionally for a few microseconds while the two worker-threads
394 compete for the mutex. Bugfix on 0.2.0.1-alpha.
397 Changes in version 0.2.2.10-alpha - 2010-03-07
398 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
399 could prevent relays from guessing their IP address correctly. It also
400 starts the groundwork for another client-side performance boost, since
401 currently we're not making efficient use of relays that have both the
402 Guard flag and the Exit flag.
405 - Fix a regression from our patch for bug 1244 that caused relays
406 to guess their IP address incorrectly if they didn't set Address
407 in their torrc and/or their address fails to resolve. Bugfix on
408 0.2.2.9-alpha; fixes bug 1269.
410 o Major features (performance):
411 - Directory authorities now compute consensus weightings that instruct
412 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
413 and no flag. Clients that use these weightings will distribute
414 network load more evenly across these different relay types. The
415 weightings are in the consensus so we can change them globally in
416 the future. Extra thanks to "outofwords" for finding some nasty
417 security bugs in the first implementation of this feature.
419 o Minor features (performance):
420 - Always perform router selections using weighted relay bandwidth,
421 even if we don't need a high capacity circuit at the time. Non-fast
422 circuits now only differ from fast ones in that they can use relays
423 not marked with the Fast flag. This "feature" could turn out to
424 be a horrible bug; we should investigate more before it goes into
428 - Allow disabling building of the manpages. Skipping the manpage
429 speeds up the build considerably.
431 o Minor bugfixes (on 0.2.2.x):
432 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
433 Bugfix on 0.2.2.9-alpha.
434 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
435 config option. Bugfix on 0.2.2.7-alpha.
436 - Ship the asciidoc-helper file in the tarball, so that people can
437 build from source if they want to, and touching the .1.txt files
438 doesn't break the build. Bugfix on 0.2.2.9-alpha.
440 o Minor bugfixes (on 0.2.1.x or earlier):
441 - Fix a dereference-then-NULL-check sequence when publishing
442 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
444 - Fix another dereference-then-NULL-check sequence. Bugfix on
445 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
446 - Make sure we treat potentially not NUL-terminated strings correctly.
447 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
449 o Code simplifications and refactoring:
450 - Fix some urls in the exit notice file and make it XHTML1.1 strict
451 compliant. Based on a patch from Christian Kujau.
452 - Don't use sed in asciidoc-helper anymore.
453 - Make the build process fail if asciidoc cannot be found and
454 building with asciidoc isn't disabled.
457 Changes in version 0.2.2.9-alpha - 2010-02-22
458 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
459 location of a directory authority, and cleans up a bunch of small bugs.
461 o Directory authority changes:
462 - Change IP address for dannenberg (v3 directory authority), and
463 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
464 service directory authority) from the list.
467 - Make Tor work again on the latest OS X: when deciding whether to
468 use strange flags to turn TLS renegotiation on, detect the OpenSSL
469 version at run-time, not compile time. We need to do this because
470 Apple doesn't update its dev-tools headers when it updates its
471 libraries in a security patch.
472 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
473 that could happen on 32-bit platforms with 64-bit time_t. Also fix
474 a memory leak when requesting a hidden service descriptor we've
475 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
477 - Authorities could be tricked into giving out the Exit flag to relays
478 that didn't allow exiting to any ports. This bug could screw
479 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
480 1238. Bug discovered by Martin Kowalczyk.
481 - When freeing a session key, zero it out completely. We only zeroed
482 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
483 patched by ekir. Fixes bug 1254.
486 - Fix static compilation by listing the openssl libraries in the right
487 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
488 - Resume handling .exit hostnames in a special way: originally we
489 stripped the .exit part and used the requested exit relay. In
490 0.2.2.1-alpha we stopped treating them in any special way, meaning
491 if you use a .exit address then Tor will pass it on to the exit
492 relay. Now we reject the .exit stream outright, since that behavior
493 might be more expected by the user. Found and diagnosed by Scott
494 Bennett and Downie on or-talk.
495 - Don't spam the controller with events when we have no file
496 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
497 for log messages was already solved from bug 748.)
498 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
500 - Make the DNSPort option work with libevent 2.x. Don't alter the
501 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
502 - Emit a GUARD DROPPED controller event for a case we missed.
503 - Make more fields in the controller protocol case-insensitive, since
504 control-spec.txt said they were.
505 - Refactor resolve_my_address() to not use gethostbyname() anymore.
506 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
507 - Fix a spec conformance issue: the network-status-version token
508 must be the first token in a v3 consensus or vote. Discovered by
509 parakeep. Bugfix on 0.2.0.3-alpha.
511 o Code simplifications and refactoring:
512 - Generate our manpage and HTML documentation using Asciidoc. This
513 change should make it easier to maintain the documentation, and
515 - Remove the --enable-iphone option. According to reports from Marco
516 Bonetti, Tor builds fine without any special tweaking on recent
518 - Removed some unnecessary files from the source distribution. The
519 AUTHORS file has now been merged into the people page on the
520 website. The roadmaps and design doc can now be found in the
521 projects directory in svn.
522 - Enabled various circuit build timeout constants to be controlled
523 by consensus parameters. Also set better defaults for these
524 parameters based on experimentation on broadband and simulated
528 - The 'EXTENDCIRCUIT' control port command can now be used with
529 a circ id of 0 and no path. This feature will cause Tor to build
530 a new 'fast' general purpose circuit using its own path selection
532 - Added a BUILDTIMEOUT_SET controller event to describe changes
533 to the circuit build timeout.
534 - Future-proof the controller protocol a bit by ignoring keyword
535 arguments we do not recognize.
536 - Expand homedirs passed to tor-checkkey. This should silence a
537 coverity complaint about passing a user-supplied string into
538 open() without checking it.
541 Changes in version 0.2.1.25 - 2010-03-16
542 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
543 prevent relays from guessing their IP address correctly. It also fixes
544 several minor potential security bugs.
547 - Fix a regression from our patch for bug 1244 that caused relays
548 to guess their IP address incorrectly if they didn't set Address
549 in their torrc and/or their address fails to resolve. Bugfix on
550 0.2.1.23; fixes bug 1269.
551 - When freeing a session key, zero it out completely. We only zeroed
552 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
553 patched by ekir. Fixes bug 1254.
556 - Fix a dereference-then-NULL-check sequence when publishing
557 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
559 - Fix another dereference-then-NULL-check sequence. Bugfix on
560 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
561 - Make sure we treat potentially not NUL-terminated strings correctly.
562 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
566 Changes in version 0.2.1.24 - 2010-02-21
567 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
571 - Work correctly out-of-the-box with even more vendor-patched versions
572 of OpenSSL. In particular, make it so Debian and OS X don't need
573 customized patches to run/build.
576 Changes in version 0.2.1.23 - 2010-02-13
577 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
578 again on the latest OS X, and updates the location of a directory
581 o Major bugfixes (performance):
582 - We were selecting our guards uniformly at random, and then weighting
583 which of our guards we'd use uniformly at random. This imbalance
584 meant that Tor clients were severely limited on throughput (and
585 probably latency too) by the first hop in their circuit. Now we
586 select guards weighted by currently advertised bandwidth. We also
587 automatically discard guards picked using the old algorithm. Fixes
588 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
591 - Make Tor work again on the latest OS X: when deciding whether to
592 use strange flags to turn TLS renegotiation on, detect the OpenSSL
593 version at run-time, not compile time. We need to do this because
594 Apple doesn't update its dev-tools headers when it updates its
595 libraries in a security patch.
596 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
597 that could happen on 32-bit platforms with 64-bit time_t. Also fix
598 a memory leak when requesting a hidden service descriptor we've
599 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
602 o Directory authority changes:
603 - Change IP address for dannenberg (v3 directory authority), and
604 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
605 service directory authority) from the list.
608 - Refactor resolve_my_address() to not use gethostbyname() anymore.
609 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
612 - Avoid a mad rush at the beginning of each month when each client
613 rotates half of its guards. Instead we spread the rotation out
614 throughout the month, but we still avoid leaving a precise timestamp
615 in the state file about when we first picked the guard. Improves
616 over the behavior introduced in 0.1.2.17.
619 Changes in version 0.2.2.8-alpha - 2010-01-26
620 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
621 causing bridge relays to disappear. If you're running a bridge,
625 - Fix a memory corruption bug on bridges that occured during the
626 inclusion of stats data in extra-info descriptors. Also fix the
627 interface for geoip_get_bridge_stats* to prevent similar bugs in
628 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
629 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
632 - Ignore OutboundBindAddress when connecting to localhost.
633 Connections to localhost need to come _from_ localhost, or else
634 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
638 Changes in version 0.2.2.7-alpha - 2010-01-19
639 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
640 as laying the groundwork for further relay-side performance fixes. It
641 also starts cleaning up client behavior with respect to the EntryNodes,
642 ExitNodes, and StrictNodes config options.
644 This release also rotates two directory authority keys, due to a
645 security breach of some of the Torproject servers.
647 o Directory authority changes:
648 - Rotate keys (both v3 identity and relay identity) for moria1
651 o Major features (performance):
652 - We were selecting our guards uniformly at random, and then weighting
653 which of our guards we'd use uniformly at random. This imbalance
654 meant that Tor clients were severely limited on throughput (and
655 probably latency too) by the first hop in their circuit. Now we
656 select guards weighted by currently advertised bandwidth. We also
657 automatically discard guards picked using the old algorithm. Fixes
658 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
659 - When choosing which cells to relay first, relays can now favor
660 circuits that have been quiet recently, to provide lower latency
661 for low-volume circuits. By default, relays enable or disable this
662 feature based on a setting in the consensus. You can override
663 this default by using the new "CircuitPriorityHalflife" config
664 option. Design and code by Ian Goldberg, Can Tang, and Chris
666 - Add separate per-conn write limiting to go with the per-conn read
667 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
668 but never per-conn write limits.
669 - New consensus params "bwconnrate" and "bwconnburst" to let us
670 rate-limit client connections as they enter the network. It's
671 controlled in the consensus so we can turn it on and off for
672 experiments. It's starting out off. Based on proposal 163.
674 o Major features (relay selection options):
675 - Switch to a StrictNodes config option, rather than the previous
676 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
677 "StrictExcludeNodes" option.
678 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
679 change during a config reload, mark and discard all our origin
680 circuits. This fix should address edge cases where we change the
681 config options and but then choose a circuit that we created before
683 - If EntryNodes or ExitNodes are set, be more willing to use an
684 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
686 - Make EntryNodes config option much more aggressive even when
687 StrictNodes is not set. Before it would prepend your requested
688 entrynodes to your list of guard nodes, but feel free to use others
689 after that. Now it chooses only from your EntryNodes if any of
690 those are available, and only falls back to others if a) they're
691 all down and b) StrictNodes is not set.
692 - Now we refresh your entry guards from EntryNodes at each consensus
693 fetch -- rather than just at startup and then they slowly rot as
697 - Stop bridge directory authorities from answering dbg-stability.txt
698 directory queries, which would let people fetch a list of all
699 bridge identities they track. Bugfix on 0.2.1.6-alpha.
702 - Log a notice when we get a new control connection. Now it's easier
703 for security-conscious users to recognize when a local application
704 is knocking on their controller door. Suggested by bug 1196.
705 - New config option "CircuitStreamTimeout" to override our internal
706 timeout schedule for how many seconds until we detach a stream from
707 a circuit and try a new circuit. If your network is particularly
708 slow, you might want to set this to a number like 60.
709 - New controller command "getinfo config-text". It returns the
710 contents that Tor would write if you send it a SAVECONF command,
711 so the controller can write the file to disk itself.
712 - New options for SafeLogging to allow scrubbing only log messages
713 generated while acting as a relay.
714 - Ship the bridges spec file in the tarball too.
715 - Avoid a mad rush at the beginning of each month when each client
716 rotates half of its guards. Instead we spread the rotation out
717 throughout the month, but we still avoid leaving a precise timestamp
718 in the state file about when we first picked the guard. Improves
719 over the behavior introduced in 0.1.2.17.
721 o Minor bugfixes (compiling):
722 - Fix compilation on OS X 10.3, which has a stub mlockall() but
723 hides it. Bugfix on 0.2.2.6-alpha.
724 - Fix compilation on Solaris by removing support for the
725 DisableAllSwap config option. Solaris doesn't have an rlimit for
726 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
729 o Minor bugfixes (crashes):
730 - Do not segfault when writing buffer stats when we haven't observed
731 a single circuit to report about. Found by Fabian Lanze. Bugfix on
733 - If we're in the pathological case where there's no exit bandwidth
734 but there is non-exit bandwidth, or no guard bandwidth but there
735 is non-guard bandwidth, don't crash during path selection. Bugfix
737 - Fix an impossible-to-actually-trigger buffer overflow in relay
738 descriptor generation. Bugfix on 0.1.0.15.
740 o Minor bugfixes (privacy):
741 - Fix an instance where a Tor directory mirror might accidentally
742 log the IP address of a misbehaving Tor client. Bugfix on
744 - Don't list Windows capabilities in relay descriptors. We never made
745 use of them, and maybe it's a bad idea to publish them. Bugfix
748 o Minor bugfixes (other):
749 - Resolve an edge case in path weighting that could make us misweight
750 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
751 - Fix statistics on client numbers by country as seen by bridges that
752 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
753 intervals instead of variable 12-to-48-hour intervals.
754 - After we free an internal connection structure, overwrite it
755 with a different memory value than we use for overwriting a freed
756 internal circuit structure. Should help with debugging. Suggested
758 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
762 - Remove the HSAuthorityRecordStats option that version 0 hidden
763 service authorities could have used to track statistics of overall
764 hidden service usage.
767 Changes in version 0.2.1.22 - 2010-01-19
768 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
769 authorities -- it would tell you its whole history of bridge descriptors
770 if you make the right directory request. This stable update also
771 rotates two of the seven v3 directory authority keys and locations.
773 o Directory authority changes:
774 - Rotate keys (both v3 identity and relay identity) for moria1
778 - Stop bridge directory authorities from answering dbg-stability.txt
779 directory queries, which would let people fetch a list of all
780 bridge identities they track. Bugfix on 0.2.1.6-alpha.
783 Changes in version 0.2.1.21 - 2009-12-21
784 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
785 library. If you use Tor on Linux / Unix and you're getting SSL
786 renegotiation errors, upgrading should help. We also recommend an
787 upgrade if you're an exit relay.
790 - Work around a security feature in OpenSSL 0.9.8l that prevents our
791 handshake from working unless we explicitly tell OpenSSL that we
792 are using SSL renegotiation safely. We are, of course, but OpenSSL
793 0.9.8l won't work unless we say we are.
794 - Avoid crashing if the client is trying to upload many bytes and the
795 circuit gets torn down at the same time, or if the flip side
796 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
799 - Do not refuse to learn about authority certs and v2 networkstatus
800 documents that are older than the latest consensus. This bug might
801 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
802 Spotted and fixed by xmux.
803 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
804 trigger platform-specific option misparsing case found by Coverity
806 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
807 trigger assert. Fixes bug 1173.
810 Changes in version 0.2.2.6-alpha - 2009-11-19
811 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
812 support for the new lower-footprint "microdescriptor" directory design,
813 future-proofing our consensus format against new hash functions or
814 other changes, and an Android port. It also makes Tor compatible with
815 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
818 - Directory authorities can now create, vote on, and serve multiple
819 parallel formats of directory data as part of their voting process.
820 Partially implements Proposal 162: "Publish the consensus in
822 - Directory authorities can now agree on and publish small summaries
823 of router information that clients can use in place of regular
824 server descriptors. This transition will eventually allow clients
825 to use far less bandwidth for downloading information about the
826 network. Begins the implementation of Proposal 158: "Clients
827 download consensus + microdescriptors".
828 - The directory voting system is now extensible to use multiple hash
829 algorithms for signatures and resource selection. Newer formats
830 are signed with SHA256, with a possibility for moving to a better
831 hash algorithm in the future.
832 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
833 current and future memory pages via mlockall(). On supported
834 platforms (modern Linux and probably BSD but not Windows or OS X),
835 this should effectively disable any and all attempts to page out
836 memory. This option requires that you start your Tor as root --
837 if you use DisableAllSwap, please consider using the User option
838 to properly reduce the privileges of your Tor.
839 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
840 to help Tor build correctly for Android phones.
843 - Work around a security feature in OpenSSL 0.9.8l that prevents our
844 handshake from working unless we explicitly tell OpenSSL that we
845 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
846 won't work unless we say we are.
849 - Fix a crash bug when trying to initialize the evdns module in
850 Libevent 2. Bugfix on 0.2.1.16-rc.
851 - Stop logging at severity 'warn' when some other Tor client tries
852 to establish a circuit with us using weak DH keys. It's a protocol
853 violation, but that doesn't mean ordinary users need to hear about
854 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
855 - Do not refuse to learn about authority certs and v2 networkstatus
856 documents that are older than the latest consensus. This bug might
857 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
858 Spotted and fixed by xmux.
859 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
860 - If all authorities restart at once right before a consensus vote,
861 nobody will vote about "Running", and clients will get a consensus
862 with no usable relays. Instead, authorities refuse to build a
863 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
864 - If your relay can't keep up with the number of incoming create
865 cells, it would log one warning per failure into your logs. Limit
866 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
867 - Bridges now use "reject *:*" as their default exit policy. Bugfix
868 on 0.2.0.3-alpha; fixes bug 1113.
869 - Fix a memory leak on directory authorities during voting that was
870 introduced in 0.2.2.1-alpha. Found via valgrind.
873 Changes in version 0.2.1.20 - 2009-10-15
874 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
875 services at once, prepares for more performance improvements, and
876 fixes a bunch of smaller bugs.
878 The Windows and OS X bundles also include a more recent Vidalia,
879 and switch from Privoxy to Polipo.
881 The OS X installers are now drag and drop. It's best to un-install
882 Tor/Vidalia and then install this new bundle, rather than upgrade. If
883 you want to upgrade, you'll need to update the paths for Tor and Polipo
884 in the Vidalia Settings window.
887 - Send circuit or stream sendme cells when our window has decreased
888 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
889 by Karsten when testing the "reduce circuit window" performance
890 patch. Bugfix on the 54th commit on Tor -- from July 2002,
891 before the release of Tor 0.0.0. This is the new winner of the
893 - Fix a remotely triggerable memory leak when a consensus document
894 contains more than one signature from the same voter. Bugfix on
896 - Avoid segfault in rare cases when finishing an introduction circuit
897 as a client and finding out that we don't have an introduction key
898 for it. Fixes bug 1073. Reported by Aaron Swartz.
901 - Tor now reads the "circwindow" parameter out of the consensus,
902 and uses that value for its circuit package window rather than the
903 default of 1000 cells. Begins the implementation of proposal 168.
905 o New directory authorities:
906 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
908 - Move moria1 and tonga to alternate IP addresses.
911 - Fix a signed/unsigned compile warning in 0.2.1.19.
912 - Fix possible segmentation fault on directory authorities. Bugfix on
914 - Fix an extremely rare infinite recursion bug that could occur if
915 we tried to log a message after shutting down the log subsystem.
916 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
917 - Fix an obscure bug where hidden services on 64-bit big-endian
918 systems might mis-read the timestamp in v3 introduce cells, and
919 refuse to connect back to the client. Discovered by "rotor".
920 Bugfix on 0.2.1.6-alpha.
921 - We were triggering a CLOCK_SKEW controller status event whenever
922 we connect via the v2 connection protocol to any relay that has
923 a wrong clock. Instead, we should only inform the controller when
924 it's a trusted authority that claims our clock is wrong. Bugfix
925 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
926 - We were telling the controller about CHECKING_REACHABILITY and
927 REACHABILITY_FAILED status events whenever we launch a testing
928 circuit or notice that one has failed. Instead, only tell the
929 controller when we want to inform the user of overall success or
930 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
932 - Don't warn when we're using a circuit that ends with a node
933 excluded in ExcludeExitNodes, but the circuit is not used to access
934 the outside world. This should help fix bug 1090. Bugfix on
936 - Work around a small memory leak in some versions of OpenSSL that
937 stopped the memory used by the hostname TLS extension from being
941 - Add a "getinfo status/accepted-server-descriptor" controller
942 command, which is the recommended way for controllers to learn
943 whether our server descriptor has been successfully received by at
944 least on directory authority. Un-recommend good-server-descriptor
945 getinfo and status events until we have a better design for them.
948 Changes in version 0.2.2.5-alpha - 2009-10-11
949 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
952 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
954 o New directory authorities:
955 - Move dizum to an alternate IP address.
958 Changes in version 0.2.2.4-alpha - 2009-10-10
959 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
960 introduces a new unit test framework, shifts directry authority
961 addresses around to reduce the impact from recent blocking events,
962 and fixes a few smaller bugs.
965 - Fix several more asserts in the circuit_build_times code, for
966 example one that causes Tor to fail to start once we have
967 accumulated 5000 build times in the state file. Bugfixes on
968 0.2.2.2-alpha; fixes bug 1108.
970 o New directory authorities:
971 - Move moria1 and Tonga to alternate IP addresses.
974 - Log SSL state transitions at debug level during handshake, and
975 include SSL states in error messages. This may help debug future
976 SSL handshake issues.
977 - Add a new "Handshake" log domain for activities that happen
978 during the TLS handshake.
979 - Revert to the "June 3 2009" ip-to-country file. The September one
980 seems to have removed most US IP addresses.
981 - Directory authorities now reject Tor relays with versions less than
982 0.1.2.14. This step cuts out four relays from the current network,
983 none of which are very big.
986 - Fix a couple of smaller issues with gathering statistics. Bugfixes
988 - Fix two memory leaks in the error case of
989 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
990 - Don't count one-hop circuits when we're estimating how long it
991 takes circuits to build on average. Otherwise we'll set our circuit
992 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
993 - Directory authorities no longer change their opinion of, or vote on,
994 whether a router is Running, unless they have themselves been
995 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
998 o Code simplifications and refactoring:
999 - Revise our unit tests to use the "tinytest" framework, so we
1000 can run tests in their own processes, have smarter setup/teardown
1001 code, and so on. The unit test code has moved to its own
1002 subdirectory, and has been split into multiple modules.
1005 Changes in version 0.2.2.3-alpha - 2009-09-23
1006 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
1009 - Fix an overzealous assert in our new circuit build timeout code.
1010 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
1013 - If the networkstatus consensus tells us that we should use a
1014 negative circuit package window, ignore it. Otherwise we'll
1015 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
1018 Changes in version 0.2.2.2-alpha - 2009-09-21
1019 Tor 0.2.2.2-alpha introduces our latest performance improvement for
1020 clients: Tor tracks the average time it takes to build a circuit, and
1021 avoids using circuits that take too long to build. For fast connections,
1022 this feature can cut your expected latency in half. For slow or flaky
1023 connections, it could ruin your Tor experience. Let us know if it does!
1026 - Tor now tracks how long it takes to build client-side circuits
1027 over time, and adapts its timeout to local network performance.
1028 Since a circuit that takes a long time to build will also provide
1029 bad performance, we get significant latency improvements by
1030 discarding the slowest 20% of circuits. Specifically, Tor creates
1031 circuits more aggressively than usual until it has enough data
1032 points for a good timeout estimate. Implements proposal 151.
1033 We are especially looking for reports (good and bad) from users with
1034 both EDGE and broadband connections that can move from broadband
1035 to EDGE and find out if the build-time data in the .tor/state gets
1036 reset without loss of Tor usability. You should also see a notice
1037 log message telling you that Tor has reset its timeout.
1038 - Directory authorities can now vote on arbitary integer values as
1039 part of the consensus process. This is designed to help set
1040 network-wide parameters. Implements proposal 167.
1041 - Tor now reads the "circwindow" parameter out of the consensus,
1042 and uses that value for its circuit package window rather than the
1043 default of 1000 cells. Begins the implementation of proposal 168.
1046 - Fix a remotely triggerable memory leak when a consensus document
1047 contains more than one signature from the same voter. Bugfix on
1051 - Fix an extremely rare infinite recursion bug that could occur if
1052 we tried to log a message after shutting down the log subsystem.
1053 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
1054 - Fix parsing for memory or time units given without a space between
1055 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
1056 - A networkstatus vote must contain exactly one signature. Spec
1057 conformance issue. Bugfix on 0.2.0.3-alpha.
1058 - Fix an obscure bug where hidden services on 64-bit big-endian
1059 systems might mis-read the timestamp in v3 introduce cells, and
1060 refuse to connect back to the client. Discovered by "rotor".
1061 Bugfix on 0.2.1.6-alpha.
1062 - We were triggering a CLOCK_SKEW controller status event whenever
1063 we connect via the v2 connection protocol to any relay that has
1064 a wrong clock. Instead, we should only inform the controller when
1065 it's a trusted authority that claims our clock is wrong. Bugfix
1066 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
1067 - We were telling the controller about CHECKING_REACHABILITY and
1068 REACHABILITY_FAILED status events whenever we launch a testing
1069 circuit or notice that one has failed. Instead, only tell the
1070 controller when we want to inform the user of overall success or
1071 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
1073 - Don't warn when we're using a circuit that ends with a node
1074 excluded in ExcludeExitNodes, but the circuit is not used to access
1075 the outside world. This should help fix bug 1090, but more problems
1076 remain. Bugfix on 0.2.1.6-alpha.
1077 - Work around a small memory leak in some versions of OpenSSL that
1078 stopped the memory used by the hostname TLS extension from being
1080 - Make our 'torify' script more portable; if we have only one of
1081 'torsocks' or 'tsocks' installed, don't complain to the user;
1082 and explain our warning about tsocks better.
1085 - Add a "getinfo status/accepted-server-descriptor" controller
1086 command, which is the recommended way for controllers to learn
1087 whether our server descriptor has been successfully received by at
1088 least on directory authority. Un-recommend good-server-descriptor
1089 getinfo and status events until we have a better design for them.
1090 - Update to the "September 4 2009" ip-to-country file.
1093 Changes in version 0.2.2.1-alpha - 2009-08-26
1094 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
1095 Tor clients to bootstrap on networks where only port 80 is reachable,
1096 makes it more straightforward to support hardware crypto accelerators,
1097 and starts the groundwork for gathering stats safely at relays.
1100 - Start the process of disabling ".exit" address notation, since it
1101 can be used for a variety of esoteric application-level attacks
1102 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
1105 o New directory authorities:
1106 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
1110 - New AccelName and AccelDir options add support for dynamic OpenSSL
1111 hardware crypto acceleration engines.
1112 - Tor now supports tunneling all of its outgoing connections over
1113 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
1114 configuration options. Code by Christopher Davis.
1117 - Send circuit or stream sendme cells when our window has decreased
1118 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
1119 by Karsten when testing the "reduce circuit window" performance
1120 patch. Bugfix on the 54th commit on Tor -- from July 2002,
1121 before the release of Tor 0.0.0. This is the new winner of the
1124 o New options for gathering stats safely:
1125 - Directories that set "DirReqStatistics 1" write statistics on
1126 directory request to disk every 24 hours. As compared to the
1127 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
1128 1) stats are written to disk exactly every 24 hours; 2) estimated
1129 shares of v2 and v3 requests are determined as mean values, not at
1130 the end of a measurement period; 3) unresolved requests are listed
1131 with country code '??'; 4) directories also measure download times.
1132 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
1133 number of exit streams and transferred bytes per port to disk every
1135 - Relays that set "CellStatistics 1" write statistics on how long
1136 cells spend in their circuit queues to disk every 24 hours.
1137 - Entry nodes that set "EntryStatistics 1" write statistics on the
1138 rough number and origins of connecting clients to disk every 24
1140 - Relays that write any of the above statistics to disk and set
1141 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
1142 their extra-info documents.
1145 - New --digests command-line switch to output the digests of the
1146 source files Tor was built with.
1147 - The "torify" script now uses torsocks where available.
1148 - The memarea code now uses a sentinel value at the end of each area
1149 to make sure nothing writes beyond the end of an area. This might
1150 help debug some conceivable causes of bug 930.
1151 - Time and memory units in the configuration file can now be set to
1152 fractional units. For example, "2.5 GB" is now a valid value for
1154 - Certain Tor clients (such as those behind check.torproject.org) may
1155 want to fetch the consensus in an extra early manner. To enable this
1156 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
1157 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
1158 as only certain clients who must have this information sooner should
1160 - Instead of adding the svn revision to the Tor version string, report
1161 the git commit (when we're building from a git checkout).
1164 - If any the v3 certs we download are unparseable, we should actually
1165 notice the failure so we don't retry indefinitely. Bugfix on
1166 0.2.0.x; reported by "rotator".
1167 - If the cached cert file is unparseable, warn but don't exit.
1168 - Fix possible segmentation fault on directory authorities. Bugfix on
1170 - When Tor fails to parse a descriptor of any kind, dump it to disk.
1171 Might help diagnosing bug 1051.
1173 o Deprecated and removed features:
1174 - The controller no longer accepts the old obsolete "addr-mappings/"
1175 or "unregistered-servers-" GETINFO values.
1176 - Hidden services no longer publish version 0 descriptors, and clients
1177 do not request or use version 0 descriptors. However, the old hidden
1178 service authorities still accept and serve version 0 descriptors
1179 when contacted by older hidden services/clients.
1180 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
1181 always on; using them is necessary for correct forward-compatible
1183 - Remove support for .noconnect style addresses. Nobody was using
1184 them, and they provided another avenue for detecting Tor users
1185 via application-level web tricks.
1187 o Packaging changes:
1188 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
1189 installer bundles. See
1190 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
1191 for details of what's new in Vidalia 0.2.3.
1192 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
1193 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
1194 configuration file, rather than the old Privoxy.
1195 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
1196 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
1197 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
1198 better compatibility with OS X 10.6, aka Snow Leopard.
1199 - OS X Vidalia Bundle: The multi-package installer is now replaced
1200 by a simple drag and drop to the /Applications folder. This change
1201 occurred with the upgrade to Vidalia 0.2.3.
1204 Changes in version 0.2.1.19 - 2009-07-28
1205 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
1206 services on Tor 0.2.1.3-alpha through 0.2.1.18.
1209 - Make accessing hidden services on 0.2.1.x work right again.
1210 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
1211 part of patch provided by "optimist".
1214 - When a relay/bridge is writing out its identity key fingerprint to
1215 the "fingerprint" file and to its logs, write it without spaces. Now
1216 it will look like the fingerprints in our bridges documentation,
1217 and confuse fewer users.
1220 - Relays no longer publish a new server descriptor if they change
1221 their MaxAdvertisedBandwidth config option but it doesn't end up
1222 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
1223 fixes bug 1026. Patch from Sebastian.
1224 - Avoid leaking memory every time we get a create cell but we have
1225 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
1226 fixes bug 1034. Reported by BarkerJr.
1229 Changes in version 0.2.1.18 - 2009-07-24
1230 Tor 0.2.1.18 lays the foundations for performance improvements,
1231 adds status events to help users diagnose bootstrap problems, adds
1232 optional authentication/authorization for hidden services, fixes a
1233 variety of potential anonymity problems, and includes a huge pile of
1234 other features and bug fixes.
1237 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
1240 Changes in version 0.2.1.17-rc - 2009-07-07
1241 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
1242 candidate for the 0.2.1.x series. It lays the groundwork for further
1243 client performance improvements, and also fixes a big bug with directory
1244 authorities that were causing them to assign Guard and Stable flags
1247 The Windows bundles also finally include the geoip database that we
1248 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
1249 should actually install Torbutton rather than giving you a cryptic
1250 failure message (oops).
1253 - Clients now use the bandwidth values in the consensus, rather than
1254 the bandwidth values in each relay descriptor. This approach opens
1255 the door to more accurate bandwidth estimates once the directory
1256 authorities start doing active measurements. Implements more of
1260 - When Tor clients restart after 1-5 days, they discard all their
1261 cached descriptors as too old, but they still use the cached
1262 consensus document. This approach is good for robustness, but
1263 bad for performance: since they don't know any bandwidths, they
1264 end up choosing at random rather than weighting their choice by
1265 speed. Fixed by the above feature of putting bandwidths in the
1266 consensus. Bugfix on 0.2.0.x.
1267 - Directory authorities were neglecting to mark relays down in their
1268 internal histories if the relays fall off the routerlist without
1269 ever being found unreachable. So there were relays in the histories
1270 that haven't been seen for eight months, and are listed as being
1271 up for eight months. This wreaked havoc on the "median wfu"
1272 and "median mtbf" calculations, in turn making Guard and Stable
1273 flags very wrong, hurting network performance. Fixes bugs 696 and
1274 969. Bugfix on 0.2.0.6-alpha.
1277 - Serve the DirPortFrontPage page even when we have been approaching
1278 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
1279 - The control port would close the connection before flushing long
1280 replies, such as the network consensus, if a QUIT command was issued
1281 before the reply had completed. Now, the control port flushes all
1282 pending replies before closing the connection. Also fixed a spurious
1283 warning when a QUIT command is issued after a malformed or rejected
1284 AUTHENTICATE command, but before the connection was closed. Patch
1285 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
1286 - When we can't find an intro key for a v2 hidden service descriptor,
1287 fall back to the v0 hidden service descriptor and log a bug message.
1288 Workaround for bug 1024.
1289 - Fix a log message that did not respect the SafeLogging option.
1293 - If we're a relay and we change our IP address, be more verbose
1294 about the reason that made us change. Should help track down
1295 further bugs for relays on dynamic IP addresses.
1298 Changes in version 0.2.0.35 - 2009-06-24
1300 - Avoid crashing in the presence of certain malformed descriptors.
1301 Found by lark, and by automated fuzzing.
1302 - Fix an edge case where a malicious exit relay could convince a
1303 controller that the client's DNS question resolves to an internal IP
1304 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
1307 - Finally fix the bug where dynamic-IP relays disappear when their
1308 IP address changes: directory mirrors were mistakenly telling
1309 them their old address if they asked via begin_dir, so they
1310 never got an accurate answer about their new address, so they
1311 just vanished after a day. For belt-and-suspenders, relays that
1312 don't set Address in their config now avoid using begin_dir for
1313 all direct connections. Should fix bugs 827, 883, and 900.
1314 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
1315 that would occur on some exit nodes when DNS failures and timeouts
1316 occurred in certain patterns. Fix for bug 957.
1319 - When starting with a cache over a few days old, do not leak
1320 memory for the obsolete router descriptors in it. Bugfix on
1321 0.2.0.33; fixes bug 672.
1322 - Hidden service clients didn't use a cached service descriptor that
1323 was older than 15 minutes, but wouldn't fetch a new one either,
1324 because there was already one in the cache. Now, fetch a v2
1325 descriptor unless the same descriptor was added to the cache within
1326 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
1329 Changes in version 0.2.1.16-rc - 2009-06-20
1330 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
1331 a bunch of minor bugs.
1334 - Fix an edge case where a malicious exit relay could convince a
1335 controller that the client's DNS question resolves to an internal IP
1336 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
1338 o Major performance improvements (on 0.2.0.x):
1339 - Disable and refactor some debugging checks that forced a linear scan
1340 over the whole server-side DNS cache. These accounted for over 50%
1341 of CPU time on a relatively busy exit node's gprof profile. Found
1343 - Disable some debugging checks that appeared in exit node profile
1347 - Update to the "June 3 2009" ip-to-country file.
1348 - Do not have tor-resolve automatically refuse all .onion addresses;
1349 if AutomapHostsOnResolve is set in your torrc, this will work fine.
1351 o Minor bugfixes (on 0.2.0.x):
1352 - Log correct error messages for DNS-related network errors on
1354 - Fix a race condition that could cause crashes or memory corruption
1355 when running as a server with a controller listening for log
1357 - Avoid crashing when we have a policy specified in a DirPolicy or
1358 SocksPolicy or ReachableAddresses option with ports set on it,
1359 and we re-load the policy. May fix bug 996.
1360 - Hidden service clients didn't use a cached service descriptor that
1361 was older than 15 minutes, but wouldn't fetch a new one either,
1362 because there was already one in the cache. Now, fetch a v2
1363 descriptor unless the same descriptor was added to the cache within
1364 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
1366 o Minor bugfixes (on 0.2.1.x):
1367 - Don't warn users about low port and hibernation mix when they
1368 provide a *ListenAddress directive to fix that. Bugfix on
1370 - When switching back and forth between bridge mode, do not start
1371 gathering GeoIP data until two hours have passed.
1372 - Do not complain that the user has requested an excluded node as
1373 an exit when the node is not really an exit. This could happen
1374 because the circuit was for testing, or an introduction point.
1378 Changes in version 0.2.1.15-rc - 2009-05-25
1379 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
1380 series. It fixes a major bug on fast exit relays, as well as a variety
1383 o Major bugfixes (on 0.2.0.x):
1384 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
1385 that would occur on some exit nodes when DNS failures and timeouts
1386 occurred in certain patterns. Fix for bug 957.
1388 o Minor bugfixes (on 0.2.0.x):
1389 - Actually return -1 in the error case for read_bandwidth_usage().
1390 Harmless bug, since we currently don't care about the return value
1391 anywhere. Bugfix on 0.2.0.9-alpha.
1392 - Provide a more useful log message if bug 977 (related to buffer
1393 freelists) ever reappears, and do not crash right away.
1394 - Fix an assertion failure on 64-bit platforms when we allocated
1395 memory right up to the end of a memarea, then realigned the memory
1396 one step beyond the end. Fixes a possible cause of bug 930.
1397 - Protect the count of open sockets with a mutex, so we can't
1398 corrupt it when two threads are closing or opening sockets at once.
1399 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
1400 - Don't allow a bridge to publish its router descriptor to a
1401 non-bridge directory authority. Fixes part of bug 932.
1402 - When we change to or from being a bridge, reset our counts of
1403 client usage by country. Fixes bug 932.
1404 - Fix a bug that made stream bandwidth get misreported to the
1406 - Stop using malloc_usable_size() to use more area than we had
1407 actually allocated: it was safe, but made valgrind really unhappy.
1408 - Fix a memory leak when v3 directory authorities load their keys
1409 and cert from disk. Bugfix on 0.2.0.1-alpha.
1411 o Minor bugfixes (on 0.2.1.x):
1412 - Fix use of freed memory when deciding to mark a non-addable
1413 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
1416 Changes in version 0.2.1.14-rc - 2009-04-12
1417 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
1418 series. It begins fixing some major performance problems, and also
1419 finally addresses the bug that was causing relays on dynamic IP
1420 addresses to fall out of the directory.
1423 - Clients replace entry guards that were chosen more than a few months
1424 ago. This change should significantly improve client performance,
1425 especially once more people upgrade, since relays that have been
1426 a guard for a long time are currently overloaded.
1428 o Major bugfixes (on 0.2.0):
1429 - Finally fix the bug where dynamic-IP relays disappear when their
1430 IP address changes: directory mirrors were mistakenly telling
1431 them their old address if they asked via begin_dir, so they
1432 never got an accurate answer about their new address, so they
1433 just vanished after a day. For belt-and-suspenders, relays that
1434 don't set Address in their config now avoid using begin_dir for
1435 all direct connections. Should fix bugs 827, 883, and 900.
1436 - Relays were falling out of the networkstatus consensus for
1437 part of a day if they changed their local config but the
1438 authorities discarded their new descriptor as "not sufficiently
1439 different". Now directory authorities accept a descriptor as changed
1440 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
1442 - Avoid crashing in the presence of certain malformed descriptors.
1443 Found by lark, and by automated fuzzing.
1446 - When generating circuit events with verbose nicknames for
1447 controllers, try harder to look up nicknames for routers on a
1448 circuit. (Previously, we would look in the router descriptors we had
1449 for nicknames, but not in the consensus.) Partial fix for bug 941.
1450 - If the bridge config line doesn't specify a port, assume 443.
1451 This makes bridge lines a bit smaller and easier for users to
1453 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
1454 bytes (aka 20KB/s), to match our documentation. Also update
1455 directory authorities so they always assign the Fast flag to relays
1456 with 20KB/s of capacity. Now people running relays won't suddenly
1457 find themselves not seeing any use, if the network gets faster
1459 - Update to the "April 3 2009" ip-to-country file.
1462 - Avoid trying to print raw memory to the logs when we decide to
1463 give up on downloading a given relay descriptor. Bugfix on
1465 - In tor-resolve, when the Tor client to use is specified by
1466 <hostname>:<port>, actually use the specified port rather than
1467 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
1468 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
1469 - When starting with a cache over a few days old, do not leak
1470 memory for the obsolete router descriptors in it. Bugfix on
1472 - Avoid double-free on list of successfully uploaded hidden
1473 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
1474 - Change memarea_strndup() implementation to work even when
1475 duplicating a string at the end of a page. This bug was
1476 harmless for now, but could have meant crashes later. Fix by
1477 lark. Bugfix on 0.2.1.1-alpha.
1478 - Limit uploaded directory documents to be 16M rather than 500K.
1479 The directory authorities were refusing v3 consensus votes from
1480 other authorities, since the votes are now 504K. Fixes bug 959;
1481 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
1482 - Directory authorities should never send a 503 "busy" response to
1483 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
1487 Changes in version 0.2.1.13-alpha - 2009-03-09
1488 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
1489 cleanups. We're finally getting close to a release candidate.
1492 - Correctly update the list of which countries we exclude as
1493 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
1494 lark. Bugfix on 0.2.1.6-alpha.
1496 o Minor bugfixes (on 0.2.0.x and earlier):
1497 - Automatically detect MacOSX versions earlier than 10.4.0, and
1498 disable kqueue from inside Tor when running with these versions.
1499 We previously did this from the startup script, but that was no
1500 help to people who didn't use the startup script. Resolves bug 863.
1501 - When we had picked an exit node for a connection, but marked it as
1502 "optional", and it turned out we had no onion key for the exit,
1503 stop wanting that exit and try again. This situation may not
1504 be possible now, but will probably become feasible with proposal
1505 158. Spotted by rovv. Fixes another case of bug 752.
1506 - Clients no longer cache certificates for authorities they do not
1507 recognize. Bugfix on 0.2.0.9-alpha.
1508 - When we can't transmit a DNS request due to a network error, retry
1509 it after a while, and eventually transmit a failing response to
1510 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
1511 - If the controller claimed responsibility for a stream, but that
1512 stream never finished making its connection, it would live
1513 forever in circuit_wait state. Now we close it after SocksTimeout
1514 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
1515 - Drop begin cells to a hidden service if they come from the middle
1516 of a circuit. Patch from lark.
1517 - When we erroneously receive two EXTEND cells for the same circuit
1518 ID on the same connection, drop the second. Patch from lark.
1519 - Fix a crash that occurs on exit nodes when a nameserver request
1520 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
1521 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
1523 - Do not assume that a stack-allocated character array will be
1524 64-bit aligned on platforms that demand that uint64_t access is
1525 aligned. Possible fix for bug 604.
1526 - Parse dates and IPv4 addresses in a locale- and libc-independent
1527 manner, to avoid platform-dependent behavior on malformed input.
1528 - Build correctly when configured to build outside the main source
1529 path. Patch from Michael Gold.
1530 - We were already rejecting relay begin cells with destination port
1531 of 0. Now also reject extend cells with destination port or address
1532 of 0. Suggested by lark.
1534 o Minor bugfixes (on 0.2.1.x):
1535 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
1536 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
1537 - If we're an exit node, scrub the IP address to which we are exiting
1538 in the logs. Bugfix on 0.2.1.8-alpha.
1541 - On Linux, use the prctl call to re-enable core dumps when the user
1543 - New controller event NEWCONSENSUS that lists the networkstatus
1544 lines for every recommended relay. Now controllers like Torflow
1545 can keep up-to-date on which relays they should be using.
1546 - Update to the "February 26 2009" ip-to-country file.
1549 Changes in version 0.2.0.34 - 2009-02-08
1550 Tor 0.2.0.34 features several more security-related fixes. You should
1551 upgrade, especially if you run an exit relay (remote crash) or a
1552 directory authority (remote infinite loop), or you're on an older
1553 (pre-XP) or not-recently-patched Windows (remote exploit).
1555 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
1556 have many known flaws, and nobody should be using them. You should
1557 upgrade. If you're using a Linux or BSD and its packages are obsolete,
1558 stop using those packages and upgrade anyway.
1561 - Fix an infinite-loop bug on handling corrupt votes under certain
1562 circumstances. Bugfix on 0.2.0.8-alpha.
1563 - Fix a temporary DoS vulnerability that could be performed by
1564 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
1565 - Avoid a potential crash on exit nodes when processing malformed
1566 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
1567 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
1568 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
1571 - Fix compilation on systems where time_t is a 64-bit integer.
1572 Patch from Matthias Drochner.
1573 - Don't consider expiring already-closed client connections. Fixes
1574 bug 893. Bugfix on 0.0.2pre20.
1577 Changes in version 0.2.1.12-alpha - 2009-02-08
1578 Tor 0.2.1.12-alpha features several more security-related fixes. You
1579 should upgrade, especially if you run an exit relay (remote crash) or
1580 a directory authority (remote infinite loop), or you're on an older
1581 (pre-XP) or not-recently-patched Windows (remote exploit). It also
1582 includes a big pile of minor bugfixes and cleanups.
1585 - Fix an infinite-loop bug on handling corrupt votes under certain
1586 circumstances. Bugfix on 0.2.0.8-alpha.
1587 - Fix a temporary DoS vulnerability that could be performed by
1588 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
1589 - Avoid a potential crash on exit nodes when processing malformed
1590 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
1593 - Let controllers actually ask for the "clients_seen" event for
1594 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
1595 reported by Matt Edman.
1596 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
1598 - Fix a bug in address parsing that was preventing bridges or hidden
1599 service targets from being at IPv6 addresses.
1600 - Solve a bug that kept hardware crypto acceleration from getting
1601 enabled when accounting was turned on. Fixes bug 907. Bugfix on
1603 - Remove a bash-ism from configure.in to build properly on non-Linux
1604 platforms. Bugfix on 0.2.1.1-alpha.
1605 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
1606 headers. Bugfix on 0.2.0.10-alpha.
1607 - Don't consider expiring already-closed client connections. Fixes
1608 bug 893. Bugfix on 0.0.2pre20.
1609 - Fix another interesting corner-case of bug 891 spotted by rovv:
1610 Previously, if two hosts had different amounts of clock drift, and
1611 one of them created a new connection with just the wrong timing,
1612 the other might decide to deprecate the new connection erroneously.
1613 Bugfix on 0.1.1.13-alpha.
1614 - Resolve a very rare crash bug that could occur when the user forced
1615 a nameserver reconfiguration during the middle of a nameserver
1616 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
1617 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
1618 Bugfix on 0.2.1.7-alpha.
1619 - If we're using bridges and our network goes away, be more willing
1620 to forgive our bridges and try again when we get an application
1621 request. Bugfix on 0.2.0.x.
1624 - Support platforms where time_t is 64 bits long. (Congratulations,
1625 NetBSD!) Patch from Matthias Drochner.
1626 - Add a 'getinfo status/clients-seen' controller command, in case
1627 controllers want to hear clients_seen events but connect late.
1630 - Disable GCC's strict alias optimization by default, to avoid the
1631 likelihood of its introducing subtle bugs whenever our code violates
1632 the letter of C99's alias rules.
1635 Changes in version 0.2.0.33 - 2009-01-21
1636 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
1637 useful to users. It also finally fixes a bug where a relay or client
1638 that's been off for many days would take a long time to bootstrap.
1640 This update also fixes an important security-related bug reported by
1641 Ilja van Sprundel. You should upgrade. (We'll send out more details
1642 about the bug once people have had some time to upgrade.)
1645 - Fix a heap-corruption bug that may be remotely triggerable on
1646 some platforms. Reported by Ilja van Sprundel.
1649 - When a stream at an exit relay is in state "resolving" or
1650 "connecting" and it receives an "end" relay cell, the exit relay
1651 would silently ignore the end cell and not close the stream. If
1652 the client never closes the circuit, then the exit relay never
1653 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
1655 - When sending CREATED cells back for a given circuit, use a 64-bit
1656 connection ID to find the right connection, rather than an addr:port
1657 combination. Now that we can have multiple OR connections between
1658 the same ORs, it is no longer possible to use addr:port to uniquely
1659 identify a connection.
1660 - Bridge relays that had DirPort set to 0 would stop fetching
1661 descriptors shortly after startup, and then briefly resume
1662 after a new bandwidth test and/or after publishing a new bridge
1663 descriptor. Bridge users that try to bootstrap from them would
1664 get a recent networkstatus but would get descriptors from up to
1665 18 hours earlier, meaning most of the descriptors were obsolete
1666 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
1667 - Prevent bridge relays from serving their 'extrainfo' document
1668 to anybody who asks, now that extrainfo docs include potentially
1669 sensitive aggregated client geoip summaries. Bugfix on
1671 - If the cached networkstatus consensus is more than five days old,
1672 discard it rather than trying to use it. In theory it could be
1673 useful because it lists alternate directory mirrors, but in practice
1674 it just means we spend many minutes trying directory mirrors that
1675 are long gone from the network. Also discard router descriptors as
1676 we load them if they are more than five days old, since the onion
1677 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
1680 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
1681 could make gcc generate non-functional binary search code. Bugfix
1683 - Build correctly on platforms without socklen_t.
1684 - Compile without warnings on solaris.
1685 - Avoid potential crash on internal error during signature collection.
1686 Fixes bug 864. Patch from rovv.
1687 - Correct handling of possible malformed authority signing key
1688 certificates with internal signature types. Fixes bug 880.
1689 Bugfix on 0.2.0.3-alpha.
1690 - Fix a hard-to-trigger resource leak when logging credential status.
1692 - When we can't initialize DNS because the network is down, do not
1693 automatically stop Tor from starting. Instead, we retry failed
1694 dns_init() every 10 minutes, and change the exit policy to reject
1695 *:* until one succeeds. Fixes bug 691.
1696 - Use 64 bits instead of 32 bits for connection identifiers used with
1697 the controller protocol, to greatly reduce risk of identifier reuse.
1698 - When we're choosing an exit node for a circuit, and we have
1699 no pending streams, choose a good general exit rather than one that
1700 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
1701 - Fix another case of assuming, when a specific exit is requested,
1702 that we know more than the user about what hosts it allows.
1703 Fixes one case of bug 752. Patch from rovv.
1704 - Clip the MaxCircuitDirtiness config option to a minimum of 10
1705 seconds. Warn the user if lower values are given in the
1706 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
1707 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
1708 user if lower values are given in the configuration. Bugfix on
1709 0.1.1.17-rc. Patch by Sebastian.
1710 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
1711 the cache because we already had a v0 descriptor with the same ID.
1712 Bugfix on 0.2.0.18-alpha.
1713 - Fix a race condition when freeing keys shared between main thread
1714 and CPU workers that could result in a memory leak. Bugfix on
1715 0.1.0.1-rc. Fixes bug 889.
1716 - Send a valid END cell back when a client tries to connect to a
1717 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
1718 840. Patch from rovv.
1719 - Check which hops rendezvous stream cells are associated with to
1720 prevent possible guess-the-streamid injection attacks from
1721 intermediate hops. Fixes another case of bug 446. Based on patch
1723 - If a broken client asks a non-exit router to connect somewhere,
1724 do not even do the DNS lookup before rejecting the connection.
1725 Fixes another case of bug 619. Patch from rovv.
1726 - When a relay gets a create cell it can't decrypt (e.g. because it's
1727 using the wrong onion key), we were dropping it and letting the
1728 client time out. Now actually answer with a destroy cell. Fixes
1729 bug 904. Bugfix on 0.0.2pre8.
1731 o Minor bugfixes (hidden services):
1732 - Do not throw away existing introduction points on SIGHUP. Bugfix on
1733 0.0.6pre1. Patch by Karsten. Fixes bug 874.
1736 - Report the case where all signatures in a detached set are rejected
1737 differently than the case where there is an error handling the
1739 - When we realize that another process has modified our cached
1740 descriptors, print out a more useful error message rather than
1741 triggering an assertion. Fixes bug 885. Patch from Karsten.
1742 - Implement the 0x20 hack to better resist DNS poisoning: set the
1743 case on outgoing DNS requests randomly, and reject responses that do
1744 not match the case correctly. This logic can be disabled with the
1745 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
1746 of servers that do not reliably preserve case in replies. See
1747 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
1749 - Check DNS replies for more matching fields to better resist DNS
1751 - Never use OpenSSL compression: it wastes RAM and CPU trying to
1752 compress cells, which are basically all encrypted, compressed, or
1756 Changes in version 0.2.1.11-alpha - 2009-01-20
1757 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
1758 week it will take a long time to bootstrap again" bug. It also fixes
1759 an important security-related bug reported by Ilja van Sprundel. You
1760 should upgrade. (We'll send out more details about the bug once people
1761 have had some time to upgrade.)
1764 - Fix a heap-corruption bug that may be remotely triggerable on
1765 some platforms. Reported by Ilja van Sprundel.
1768 - Discard router descriptors as we load them if they are more than
1769 five days old. Otherwise if Tor is off for a long time and then
1770 starts with cached descriptors, it will try to use the onion
1771 keys in those obsolete descriptors when building circuits. Bugfix
1772 on 0.2.0.x. Fixes bug 887.
1775 - Try to make sure that the version of Libevent we're running with
1776 is binary-compatible with the one we built with. May address bug
1778 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
1779 for bug 905. Bugfix on 0.2.1.7-alpha.
1780 - Add a new --enable-local-appdata configuration switch to change
1781 the default location of the datadir on win32 from APPDATA to
1782 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
1783 entirely. Patch from coderman.
1786 - Make outbound DNS packets respect the OutboundBindAddress setting.
1787 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
1788 - When our circuit fails at the first hop (e.g. we get a destroy
1789 cell back), avoid using that OR connection anymore, and also
1790 tell all the one-hop directory requests waiting for it that they
1791 should fail. Bugfix on 0.2.1.3-alpha.
1792 - In the torify(1) manpage, mention that tsocks will leak your
1796 Changes in version 0.2.1.10-alpha - 2009-01-06
1797 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
1798 would make the bridge relay not so useful if it had DirPort set to 0,
1799 and one that could let an attacker learn a little bit of information
1800 about the bridge's users), and a bug that would cause your Tor relay
1801 to ignore a circuit create request it can't decrypt (rather than reply
1802 with an error). It also fixes a wide variety of other bugs.
1805 - If the cached networkstatus consensus is more than five days old,
1806 discard it rather than trying to use it. In theory it could
1807 be useful because it lists alternate directory mirrors, but in
1808 practice it just means we spend many minutes trying directory
1809 mirrors that are long gone from the network. Helps bug 887 a bit;
1811 - Bridge relays that had DirPort set to 0 would stop fetching
1812 descriptors shortly after startup, and then briefly resume
1813 after a new bandwidth test and/or after publishing a new bridge
1814 descriptor. Bridge users that try to bootstrap from them would
1815 get a recent networkstatus but would get descriptors from up to
1816 18 hours earlier, meaning most of the descriptors were obsolete
1817 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
1818 - Prevent bridge relays from serving their 'extrainfo' document
1819 to anybody who asks, now that extrainfo docs include potentially
1820 sensitive aggregated client geoip summaries. Bugfix on
1824 - New controller event "clients_seen" to report a geoip-based summary
1825 of which countries we've seen clients from recently. Now controllers
1826 like Vidalia can show bridge operators that they're actually making
1828 - Build correctly against versions of OpenSSL 0.9.8 or later built
1829 without support for deprecated functions.
1830 - Update to the "December 19 2008" ip-to-country file.
1832 o Minor bugfixes (on 0.2.0.x):
1833 - Authorities now vote for the Stable flag for any router whose
1834 weighted MTBF is at least 5 days, regardless of the mean MTBF.
1835 - Do not remove routers as too old if we do not have any consensus
1836 document. Bugfix on 0.2.0.7-alpha.
1837 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
1838 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
1839 - When an exit relay resolves a stream address to a local IP address,
1840 do not just keep retrying that same exit relay over and
1841 over. Instead, just close the stream. Addresses bug 872. Bugfix
1842 on 0.2.0.32. Patch from rovv.
1843 - If a hidden service sends us an END cell, do not consider
1844 retrying the connection; just close it. Patch from rovv.
1845 - When we made bridge authorities stop serving bridge descriptors over
1846 unencrypted links, we also broke DirPort reachability testing for
1847 bridges. So bridges with a non-zero DirPort were printing spurious
1848 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
1849 - When a relay gets a create cell it can't decrypt (e.g. because it's
1850 using the wrong onion key), we were dropping it and letting the
1851 client time out. Now actually answer with a destroy cell. Fixes
1852 bug 904. Bugfix on 0.0.2pre8.
1853 - Squeeze 2-5% out of client performance (according to oprofile) by
1854 improving the implementation of some policy-manipulation functions.
1856 o Minor bugfixes (on 0.2.1.x):
1857 - Make get_interface_address() function work properly again; stop
1858 guessing the wrong parts of our address as our address.
1859 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
1860 send on that circuit. Otherwise we might violate the proposal-110
1861 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
1863 - When we're sending non-EXTEND cells to the first hop in a circuit,
1864 for example to use an encrypted directory connection, we don't need
1865 to use RELAY_EARLY cells: the first hop knows what kind of cell
1866 it is, and nobody else can even see the cell type. Conserving
1867 RELAY_EARLY cells makes it easier to cannibalize circuits like
1869 - Stop logging nameserver addresses in reverse order.
1870 - If we are retrying a directory download slowly over and over, do
1871 not automatically give up after the 254th failure. Bugfix on
1873 - Resume reporting accurate "stream end" reasons to the local control
1874 port. They were lost in the changes for Proposal 148. Bugfix on
1877 o Deprecated and removed features:
1878 - The old "tor --version --version" command, which would print out
1879 the subversion "Id" of most of the source files, is now removed. It
1880 turned out to be less useful than we'd expected, and harder to
1883 o Code simplifications and refactoring:
1884 - Change our header file guard macros to be less likely to conflict
1885 with system headers. Adam Langley noticed that we were conflicting
1886 with log.h on Android.
1887 - Tool-assisted documentation cleanup. Nearly every function or
1888 static variable in Tor should have its own documentation now.
1891 Changes in version 0.2.1.9-alpha - 2008-12-25
1892 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
1894 o New directory authorities:
1895 - gabelmoo (the authority run by Karsten Loesing) now has a new
1899 - Never use a connection with a mismatched address to extend a
1900 circuit, unless that connection is canonical. A canonical
1901 connection is one whose address is authenticated by the router's
1902 identity key, either in a NETINFO cell or in a router descriptor.
1903 - Avoid a possible memory corruption bug when receiving hidden service
1904 descriptors. Bugfix on 0.2.1.6-alpha.
1907 - Fix a logic error that would automatically reject all but the first
1908 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
1909 part of bug 813/868. Bug spotted by coderman.
1910 - When a stream at an exit relay is in state "resolving" or
1911 "connecting" and it receives an "end" relay cell, the exit relay
1912 would silently ignore the end cell and not close the stream. If
1913 the client never closes the circuit, then the exit relay never
1914 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
1916 - When we can't initialize DNS because the network is down, do not
1917 automatically stop Tor from starting. Instead, retry failed
1918 dns_init() every 10 minutes, and change the exit policy to reject
1919 *:* until one succeeds. Fixes bug 691.
1922 - Give a better error message when an overzealous init script says
1923 "sudo -u username tor --user username". Makes Bug 882 easier for
1925 - When a directory authority gives us a new guess for our IP address,
1926 log which authority we used. Hopefully this will help us debug
1927 the recent complaints about bad IP address guesses.
1928 - Detect svn revision properly when we're using git-svn.
1929 - Try not to open more than one descriptor-downloading connection
1930 to an authority at once. This should reduce load on directory
1931 authorities. Fixes bug 366.
1932 - Add cross-certification to newly generated certificates, so that
1933 a signing key is enough information to look up a certificate.
1934 Partial implementation of proposal 157.
1935 - Start serving certificates by <identity digest, signing key digest>
1936 pairs. Partial implementation of proposal 157.
1937 - Clients now never report any stream end reason except 'MISC'.
1938 Implements proposal 148.
1939 - On platforms with a maximum syslog string length, truncate syslog
1940 messages to that length ourselves, rather than relying on the
1941 system to do it for us.
1942 - Optimize out calls to time(NULL) that occur for every IO operation,
1943 or for every cell. On systems where time() is a slow syscall,
1944 this fix will be slightly helpful.
1945 - Exit servers can now answer resolve requests for ip6.arpa addresses.
1946 - When we download a descriptor that we then immediately (as
1947 a directory authority) reject, do not retry downloading it right
1948 away. Should save some bandwidth on authorities. Fix for bug
1949 888. Patch by Sebastian Hahn.
1950 - When a download gets us zero good descriptors, do not notify
1951 Tor that new directory information has arrived.
1952 - Avoid some nasty corner cases in the logic for marking connections
1953 as too old or obsolete or noncanonical for circuits. Partial
1956 o Minor features (controller):
1957 - New CONSENSUS_ARRIVED event to note when a new consensus has
1958 been fetched and validated.
1959 - When we realize that another process has modified our cached
1960 descriptors file, print out a more useful error message rather
1961 than triggering an assertion. Fixes bug 885. Patch from Karsten.
1962 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
1963 controllers to prevent SIGHUP from reloading the
1964 configuration. Fixes bug 856.
1967 - Resume using the correct "REASON=" stream when telling the
1968 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
1969 - When a canonical connection appears later in our internal list
1970 than a noncanonical one for a given OR ID, always use the
1971 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
1973 - Clip the MaxCircuitDirtiness config option to a minimum of 10
1974 seconds. Warn the user if lower values are given in the
1975 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
1976 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
1977 user if lower values are given in the configuration. Bugfix on
1978 0.1.1.17-rc. Patch by Sebastian.
1979 - Fix a race condition when freeing keys shared between main thread
1980 and CPU workers that could result in a memory leak. Bugfix on
1981 0.1.0.1-rc. Fixes bug 889.
1983 o Minor bugfixes (hidden services):
1984 - Do not throw away existing introduction points on SIGHUP (bugfix on
1985 0.0.6pre1); also, do not stall hidden services because we're
1986 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
1987 by John Brooks. Patch by Karsten. Fixes bug 874.
1988 - Fix a memory leak when we decline to add a v2 rendezvous
1989 descriptor to the cache because we already had a v0 descriptor
1990 with the same ID. Bugfix on 0.2.0.18-alpha.
1992 o Deprecated and removed features:
1993 - RedirectExits has been removed. It was deprecated since
1995 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
1996 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
1997 - Cell pools are now always enabled; --disable-cell-pools is ignored.
1999 o Code simplifications and refactoring:
2000 - Rename the confusing or_is_obsolete field to the more appropriate
2001 is_bad_for_new_circs, and move it to or_connection_t where it
2003 - Move edge-only flags from connection_t to edge_connection_t: not
2004 only is this better coding, but on machines of plausible alignment,
2005 it should save 4-8 bytes per connection_t. "Every little bit helps."
2006 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
2007 for consistency; keep old option working for backward compatibility.
2008 - Simplify the code for finding connections to use for a circuit.
2011 Changes in version 0.2.1.8-alpha - 2008-12-08
2012 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
2013 builds better on unusual platforms like Solaris and old OS X, and
2014 fixes a variety of other issues.
2017 - New DirPortFrontPage option that takes an html file and publishes
2018 it as "/" on the DirPort. Now relay operators can provide a
2019 disclaimer without needing to set up a separate webserver. There's
2020 a sample disclaimer in contrib/tor-exit-notice.html.
2023 - When the client is choosing entry guards, now it selects at most
2024 one guard from a given relay family. Otherwise we could end up with
2025 all of our entry points into the network run by the same operator.
2026 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
2029 - Fix a DOS opportunity during the voting signature collection process
2030 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
2031 - Fix a possible segfault when establishing an exit connection. Bugfix
2035 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
2037 - Made Tor a little less aggressive about deleting expired
2038 certificates. Partial fix for bug 854.
2039 - Stop doing unaligned memory access that generated bus errors on
2040 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
2041 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
2042 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
2043 - Make USR2 log-level switch take effect immediately. Bugfix on
2045 - If one win32 nameserver fails to get added, continue adding the
2046 rest, and don't automatically fail.
2047 - Use fcntl() for locking when flock() is not available. Should fix
2048 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
2049 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
2050 could make gcc generate non-functional binary search code. Bugfix
2052 - Build correctly on platforms without socklen_t.
2053 - Avoid potential crash on internal error during signature collection.
2054 Fixes bug 864. Patch from rovv.
2055 - Do not use C's stdio library for writing to log files. This will
2056 improve logging performance by a minute amount, and will stop
2057 leaking fds when our disk is full. Fixes bug 861.
2058 - Stop erroneous use of O_APPEND in cases where we did not in fact
2059 want to re-seek to the end of a file before every last write().
2060 - Correct handling of possible malformed authority signing key
2061 certificates with internal signature types. Fixes bug 880. Bugfix
2063 - Fix a hard-to-trigger resource leak when logging credential status.
2067 - Directory mirrors no longer fetch the v1 directory or
2068 running-routers files. They are obsolete, and nobody asks for them
2069 anymore. This is the first step to making v1 authorities obsolete.
2071 o Minor features (controller):
2072 - Return circuit purposes in response to GETINFO circuit-status. Fixes
2076 Changes in version 0.2.0.32 - 2008-11-20
2077 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
2078 packages (and maybe other packages) noticed by Theo de Raadt, fixes
2079 a smaller security flaw that might allow an attacker to access local
2080 services, further improves hidden service performance, and fixes a
2081 variety of other issues.
2084 - The "User" and "Group" config options did not clear the
2085 supplementary group entries for the Tor process. The "User" option
2086 is now more robust, and we now set the groups to the specified
2087 user's primary group. The "Group" option is now ignored. For more
2088 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
2089 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
2090 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
2091 - The "ClientDNSRejectInternalAddresses" config option wasn't being
2092 consistently obeyed: if an exit relay refuses a stream because its
2093 exit policy doesn't allow it, we would remember what IP address
2094 the relay said the destination address resolves to, even if it's
2095 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
2098 - Fix a DOS opportunity during the voting signature collection process
2099 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
2101 o Major bugfixes (hidden services):
2102 - When fetching v0 and v2 rendezvous service descriptors in parallel,
2103 we were failing the whole hidden service request when the v0
2104 descriptor fetch fails, even if the v2 fetch is still pending and
2105 might succeed. Similarly, if the last v2 fetch fails, we were
2106 failing the whole hidden service request even if a v0 fetch is
2107 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
2108 - When extending a circuit to a hidden service directory to upload a
2109 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
2110 requests failed, because the router descriptor has not been
2111 downloaded yet. In these cases, do not attempt to upload the
2112 rendezvous descriptor, but wait until the router descriptor is
2113 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
2114 descriptor from a hidden service directory for which the router
2115 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
2119 - Fix several infrequent memory leaks spotted by Coverity.
2120 - When testing for libevent functions, set the LDFLAGS variable
2121 correctly. Found by Riastradh.
2122 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
2123 bootstrapping with tunneled directory connections. Bugfix on
2124 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
2125 - When asked to connect to A.B.exit:80, if we don't know the IP for A
2126 and we know that server B rejects most-but-not all connections to
2127 port 80, we would previously reject the connection. Now, we assume
2128 the user knows what they were asking for. Fixes bug 752. Bugfix
2129 on 0.0.9rc5. Diagnosed by BarkerJr.
2130 - If we overrun our per-second write limits a little, count this as
2131 having used up our write allocation for the second, and choke
2132 outgoing directory writes. Previously, we had only counted this when
2133 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
2134 Bugfix on 0.2.0.x (??).
2135 - Remove the old v2 directory authority 'lefkada' from the default
2136 list. It has been gone for many months.
2137 - Stop doing unaligned memory access that generated bus errors on
2138 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
2139 - Make USR2 log-level switch take effect immediately. Bugfix on
2142 o Minor bugfixes (controller):
2143 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
2144 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
2147 Changes in version 0.2.1.7-alpha - 2008-11-08
2148 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
2149 packages (and maybe other packages) noticed by Theo de Raadt, fixes
2150 a smaller security flaw that might allow an attacker to access local
2151 services, adds better defense against DNS poisoning attacks on exit
2152 relays, further improves hidden service performance, and fixes a
2153 variety of other issues.
2156 - The "ClientDNSRejectInternalAddresses" config option wasn't being
2157 consistently obeyed: if an exit relay refuses a stream because its
2158 exit policy doesn't allow it, we would remember what IP address
2159 the relay said the destination address resolves to, even if it's
2160 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
2161 - The "User" and "Group" config options did not clear the
2162 supplementary group entries for the Tor process. The "User" option
2163 is now more robust, and we now set the groups to the specified
2164 user's primary group. The "Group" option is now ignored. For more
2165 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
2166 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
2167 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
2168 - Do not use or believe expired v3 authority certificates. Patch
2169 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
2172 - Now NodeFamily and MyFamily config options allow spaces in
2173 identity fingerprints, so it's easier to paste them in.
2174 Suggested by Lucky Green.
2175 - Implement the 0x20 hack to better resist DNS poisoning: set the
2176 case on outgoing DNS requests randomly, and reject responses that do
2177 not match the case correctly. This logic can be disabled with the
2178 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
2179 of servers that do not reliably preserve case in replies. See
2180 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
2182 - Preserve case in replies to DNSPort requests in order to support
2183 the 0x20 hack for resisting DNS poisoning attacks.
2185 o Hidden service performance improvements:
2186 - When the client launches an introduction circuit, retry with a
2187 new circuit after 30 seconds rather than 60 seconds.
2188 - Launch a second client-side introduction circuit in parallel
2189 after a delay of 15 seconds (based on work by Christian Wilms).
2190 - Hidden services start out building five intro circuits rather
2191 than three, and when the first three finish they publish a service
2192 descriptor using those. Now we publish our service descriptor much
2193 faster after restart.
2196 - Minor fix in the warning messages when you're having problems
2197 bootstrapping; also, be more forgiving of bootstrap problems when
2198 we're still making incremental progress on a given bootstrap phase.
2199 - When we're choosing an exit node for a circuit, and we have
2200 no pending streams, choose a good general exit rather than one that
2201 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
2202 - Send a valid END cell back when a client tries to connect to a
2203 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
2204 840. Patch from rovv.
2205 - If a broken client asks a non-exit router to connect somewhere,
2206 do not even do the DNS lookup before rejecting the connection.
2207 Fixes another case of bug 619. Patch from rovv.
2208 - Fix another case of assuming, when a specific exit is requested,
2209 that we know more than the user about what hosts it allows.
2210 Fixes another case of bug 752. Patch from rovv.
2211 - Check which hops rendezvous stream cells are associated with to
2212 prevent possible guess-the-streamid injection attacks from
2213 intermediate hops. Fixes another case of bug 446. Based on patch
2215 - Avoid using a negative right-shift when comparing 32-bit
2216 addresses. Possible fix for bug 845 and bug 811.
2217 - Make the assert_circuit_ok() function work correctly on circuits that
2218 have already been marked for close.
2219 - Fix read-off-the-end-of-string error in unit tests when decoding
2220 introduction points.
2221 - Fix uninitialized size field for memory area allocation: may improve
2222 memory performance during directory parsing.
2223 - Treat duplicate certificate fetches as failures, so that we do
2224 not try to re-fetch an expired certificate over and over and over.
2225 - Do not say we're fetching a certificate when we'll in fact skip it
2226 because of a pending download.
2229 Changes in version 0.2.1.6-alpha - 2008-09-30
2230 Tor 0.2.1.6-alpha further improves performance and robustness of
2231 hidden services, starts work on supporting per-country relay selection,
2232 and fixes a variety of smaller issues.
2235 - Implement proposal 121: make it possible to build hidden services
2236 that only certain clients are allowed to connect to. This is
2237 enforced at several points, so that unauthorized clients are unable
2238 to send INTRODUCE cells to the service, or even (depending on the
2239 type of authentication) to learn introduction points. This feature
2240 raises the bar for certain kinds of active attacks against hidden
2241 services. Code by Karsten Loesing.
2242 - Relays now store and serve v2 hidden service descriptors by default,
2243 i.e., the new default value for HidServDirectoryV2 is 1. This is
2244 the last step in proposal 114, which aims to make hidden service
2245 lookups more reliable.
2246 - Start work to allow node restrictions to include country codes. The
2247 syntax to exclude nodes in a country with country code XX is
2248 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
2249 refinement to decide what config options should take priority if
2250 you ask to both use a particular node and exclude it.
2251 - Allow ExitNodes list to include IP ranges and country codes, just
2252 like the Exclude*Nodes lists. Patch from Robert Hogan.
2255 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
2256 Tor to fail to start if you had it configured to use a bridge
2257 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
2258 - When extending a circuit to a hidden service directory to upload a
2259 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
2260 requests failed, because the router descriptor had not been
2261 downloaded yet. In these cases, we now wait until the router
2262 descriptor is downloaded, and then retry. Likewise, clients
2263 now skip over a hidden service directory if they don't yet have
2264 its router descriptor, rather than futilely requesting it and
2265 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
2267 - When fetching v0 and v2 rendezvous service descriptors in parallel,
2268 we were failing the whole hidden service request when the v0
2269 descriptor fetch fails, even if the v2 fetch is still pending and
2270 might succeed. Similarly, if the last v2 fetch fails, we were
2271 failing the whole hidden service request even if a v0 fetch is
2272 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
2273 - DNS replies need to have names matching their requests, but
2274 these names should be in the questions section, not necessarily
2275 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
2278 - Update to the "September 1 2008" ip-to-country file.
2279 - Allow ports 465 and 587 in the default exit policy again. We had
2280 rejected them in 0.1.0.15, because back in 2005 they were commonly
2281 misconfigured and ended up as spam targets. We hear they are better
2282 locked down these days.
2283 - Use a lockfile to make sure that two Tor processes are not
2284 simultaneously running with the same datadir.
2285 - Serve the latest v3 networkstatus consensus via the control
2286 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
2287 - Better logging about stability/reliability calculations on directory
2289 - Drop the requirement to have an open dir port for storing and
2290 serving v2 hidden service descriptors.
2291 - Directory authorities now serve a /tor/dbg-stability.txt URL to
2292 help debug WFU and MTBF calculations.
2293 - Implement most of Proposal 152: allow specialized servers to permit
2294 single-hop circuits, and clients to use those servers to build
2295 single-hop circuits when using a specialized controller. Patch
2296 from Josh Albrecht. Resolves feature request 768.
2297 - Add a -p option to tor-resolve for specifying the SOCKS port: some
2298 people find host:port too confusing.
2299 - Make TrackHostExit mappings expire a while after their last use, not
2300 after their creation. Patch from Robert Hogan.
2301 - Provide circuit purposes along with circuit events to the controller.
2304 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
2306 - Fixed some memory leaks -- some quite frequent, some almost
2307 impossible to trigger -- based on results from Coverity.
2308 - When testing for libevent functions, set the LDFLAGS variable
2309 correctly. Found by Riastradh.
2310 - Fix an assertion bug in parsing policy-related options; possible fix
2312 - Catch and report a few more bootstrapping failure cases when Tor
2313 fails to establish a TCP connection. Cleanup on 0.2.1.x.
2314 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
2315 bootstrapping with tunneled directory connections. Bugfix on
2316 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
2317 - When asked to connect to A.B.exit:80, if we don't know the IP for A
2318 and we know that server B rejects most-but-not all connections to
2319 port 80, we would previously reject the connection. Now, we assume
2320 the user knows what they were asking for. Fixes bug 752. Bugfix
2321 on 0.0.9rc5. Diagnosed by BarkerJr.
2322 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
2323 service directories if they have no advertised dir port. Bugfix
2325 - If we overrun our per-second write limits a little, count this as
2326 having used up our write allocation for the second, and choke
2327 outgoing directory writes. Previously, we had only counted this when
2328 we had met our limits precisely. Fixes bug 824. Patch by rovv.
2329 Bugfix on 0.2.0.x (??).
2330 - Avoid a "0 divided by 0" calculation when calculating router uptime
2331 at directory authorities. Bugfix on 0.2.0.8-alpha.
2332 - Make DNS resolved controller events into "CLOSED", not
2333 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
2335 - Fix a bug where an unreachable relay would establish enough
2336 reachability testing circuits to do a bandwidth test -- if
2337 we already have a connection to the middle hop of the testing
2338 circuit, then it could establish the last hop by using the existing
2339 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
2340 circuits no longer use entry guards in 0.2.1.3-alpha.
2341 - If we have correct permissions on $datadir, we complain to stdout
2342 and fail to start. But dangerous permissions on
2343 $datadir/cached-status/ would cause us to open a log and complain
2344 there. Now complain to stdout and fail to start in both cases. Fixes
2345 bug 820, reported by seeess.
2346 - Remove the old v2 directory authority 'lefkada' from the default
2347 list. It has been gone for many months.
2349 o Code simplifications and refactoring:
2350 - Revise the connection_new functions so that a more typesafe variant
2351 exists. This will work better with Coverity, and let us find any
2352 actual mistakes we're making here.
2353 - Refactor unit testing logic so that dmalloc can be used sensibly
2354 with unit tests to check for memory leaks.
2355 - Move all hidden-service related fields from connection and circuit
2356 structure to substructures: this way they won't eat so much memory.
2359 Changes in version 0.2.0.31 - 2008-09-03
2360 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
2361 a big bug we're seeing where in rare cases traffic from one Tor stream
2362 gets mixed into another stream, and fixes a variety of smaller issues.
2365 - Make sure that two circuits can never exist on the same connection
2366 with the same circuit ID, even if one is marked for close. This
2367 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
2368 - Relays now reject risky extend cells: if the extend cell includes
2369 a digest of all zeroes, or asks to extend back to the relay that
2370 sent the extend cell, tear down the circuit. Ideas suggested
2372 - If not enough of our entry guards are available so we add a new
2373 one, we might use the new one even if it overlapped with the
2374 current circuit's exit relay (or its family). Anonymity bugfix
2375 pointed out by rovv.
2378 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
2379 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
2380 - Correctly detect the presence of the linux/netfilter_ipv4.h header
2381 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
2382 - Pick size of default geoip filename string correctly on windows.
2383 Fixes bug 806. Bugfix on 0.2.0.30.
2384 - Make the autoconf script accept the obsolete --with-ssl-dir
2385 option as an alias for the actually-working --with-openssl-dir
2386 option. Fix the help documentation to recommend --with-openssl-dir.
2387 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
2388 - When using the TransPort option on OpenBSD, and using the User
2389 option to change UID and drop privileges, make sure to open
2390 /dev/pf before dropping privileges. Fixes bug 782. Patch from
2391 Christopher Davis. Bugfix on 0.1.2.1-alpha.
2392 - Try to attach connections immediately upon receiving a RENDEZVOUS2
2393 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
2394 on the client side when connecting to a hidden service. Bugfix
2395 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
2396 - When closing an application-side connection because its circuit is
2397 getting torn down, generate the stream event correctly. Bugfix on
2398 0.1.2.x. Anonymous patch.
2401 Changes in version 0.2.1.5-alpha - 2008-08-31
2402 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
2403 in a lot of the infrastructure for adding authorization to hidden
2404 services, lays the groundwork for having clients read their load
2405 balancing information out of the networkstatus consensus rather than
2406 the individual router descriptors, addresses two potential anonymity
2407 issues, and fixes a variety of smaller issues.
2410 - Convert many internal address representations to optionally hold
2412 - Generate and accept IPv6 addresses in many protocol elements.
2413 - Make resolver code handle nameservers located at ipv6 addresses.
2414 - Begin implementation of proposal 121 ("Client authorization for
2415 hidden services"): configure hidden services with client
2416 authorization, publish descriptors for them, and configure
2417 authorization data for hidden services at clients. The next
2418 step is to actually access hidden services that perform client
2420 - More progress toward proposal 141: Network status consensus
2421 documents and votes now contain bandwidth information for each
2422 router and a summary of that router's exit policy. Eventually this
2423 will be used by clients so that they do not have to download every
2424 known descriptor before building circuits.
2426 o Major bugfixes (on 0.2.0.x and before):
2427 - When sending CREATED cells back for a given circuit, use a 64-bit
2428 connection ID to find the right connection, rather than an addr:port
2429 combination. Now that we can have multiple OR connections between
2430 the same ORs, it is no longer possible to use addr:port to uniquely
2431 identify a connection.
2432 - Relays now reject risky extend cells: if the extend cell includes
2433 a digest of all zeroes, or asks to extend back to the relay that
2434 sent the extend cell, tear down the circuit. Ideas suggested
2436 - If not enough of our entry guards are available so we add a new
2437 one, we might use the new one even if it overlapped with the
2438 current circuit's exit relay (or its family). Anonymity bugfix
2439 pointed out by rovv.
2442 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
2443 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
2444 - When using the TransPort option on OpenBSD, and using the User
2445 option to change UID and drop privileges, make sure to open /dev/pf
2446 before dropping privileges. Fixes bug 782. Patch from Christopher
2447 Davis. Bugfix on 0.1.2.1-alpha.
2448 - Correctly detect the presence of the linux/netfilter_ipv4.h header
2449 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
2450 - Add a missing safe_str() call for a debug log message.
2451 - Use 64 bits instead of 32 bits for connection identifiers used with
2452 the controller protocol, to greatly reduce risk of identifier reuse.
2453 - Make the autoconf script accept the obsolete --with-ssl-dir
2454 option as an alias for the actually-working --with-openssl-dir
2455 option. Fix the help documentation to recommend --with-openssl-dir.
2456 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
2459 - Rate-limit too-many-sockets messages: when they happen, they happen
2460 a lot. Resolves bug 748.
2461 - Resist DNS poisoning a little better by making sure that names in
2462 answer sections match.
2463 - Print the SOCKS5 error message string as well as the error code
2464 when a tor-resolve request fails. Patch from Jacob.
2467 Changes in version 0.2.1.4-alpha - 2008-08-04
2468 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
2471 - The address part of exit policies was not correctly written
2472 to router descriptors. This generated router descriptors that failed
2473 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
2475 - Tor triggered a false assert when extending a circuit to a relay
2476 but we already have a connection open to that relay. Noticed by
2477 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
2480 - Fix a hidden service logging bug: in some edge cases, the router
2481 descriptor of a previously picked introduction point becomes
2482 obsolete and we need to give up on it rather than continually
2483 complaining that it has become obsolete. Observed by xiando. Bugfix
2487 - Take out the TestVia config option, since it was a workaround for
2488 a bug that was fixed in Tor 0.1.1.21.
2491 Changes in version 0.2.1.3-alpha - 2008-08-03
2492 Tor 0.2.1.3-alpha implements most of the pieces to prevent
2493 infinite-length circuit attacks (see proposal 110); fixes a bug that
2494 might cause exit relays to corrupt streams they send back; allows
2495 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
2496 ExcludeExitNodes config options; and fixes a big pile of bugs.
2498 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
2499 - Send a bootstrap problem "warn" event on the first problem if the
2500 reason is NO_ROUTE (that is, our network is down).
2503 - Implement most of proposal 110: The first K cells to be sent
2504 along a circuit are marked as special "early" cells; only K "early"
2505 cells will be allowed. Once this code is universal, we can block
2506 certain kinds of DOS attack by requiring that EXTEND commands must
2507 be sent using an "early" cell.
2510 - Try to attach connections immediately upon receiving a RENDEZVOUS2
2511 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
2512 on the client side when connecting to a hidden service. Bugfix
2513 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
2514 - Ensure that two circuits can never exist on the same connection
2515 with the same circuit ID, even if one is marked for close. This
2516 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
2519 - When relays do their initial bandwidth measurement, don't limit
2520 to just our entry guards for the test circuits. Otherwise we tend
2521 to have multiple test circuits going through a single entry guard,
2522 which makes our bandwidth test less accurate. Fixes part of bug 654;
2523 patch contributed by Josh Albrecht.
2524 - Add an ExcludeExitNodes option so users can list a set of nodes
2525 that should be be excluded from the exit node position, but
2526 allowed elsewhere. Implements proposal 151.
2527 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
2528 ExcludeNodes and ExcludeExitNodes lists.
2529 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
2530 be more efficient. Formerly it was quadratic in the number of
2531 servers; now it should be linear. Fixes bug 509.
2532 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
2533 and n_conn_id_digest fields into a separate structure that's
2534 only needed when the circuit has not yet attached to an n_conn.
2537 - Change the contrib/tor.logrotate script so it makes the new
2538 logs as "_tor:_tor" rather than the default, which is generally
2539 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
2540 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
2541 warnings (occasionally), but it can also cause the compiler to
2542 eliminate error-checking code. Suggested by Peter Gutmann.
2543 - When a hidden service is giving up on an introduction point candidate
2544 that was not included in the last published rendezvous descriptor,
2545 don't reschedule publication of the next descriptor. Fixes bug 763.
2547 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
2548 HiddenServiceExcludeNodes as obsolete: they never worked properly,
2549 and nobody claims to be using them. Fixes bug 754. Bugfix on
2550 0.1.0.1-rc. Patch from Christian Wilms.
2551 - Fix a small alignment and memory-wasting bug on buffer chunks.
2554 o Minor bugfixes (controller):
2555 - When closing an application-side connection because its circuit
2556 is getting torn down, generate the stream event correctly.
2557 Bugfix on 0.1.2.x. Anonymous patch.
2560 - Remove all backward-compatibility code to support relays running
2561 versions of Tor so old that they no longer work at all on the
2565 Changes in version 0.2.0.30 - 2008-07-15
2567 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
2568 warnings (occasionally), but it can also cause the compiler to
2569 eliminate error-checking code. Suggested by Peter Gutmann.
2572 Changes in version 0.2.0.29-rc - 2008-07-08
2573 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
2574 hidden-service performance bugs, and fixes a bunch of smaller bugs.
2577 - If you have more than one bridge but don't know their keys,
2578 you would only launch a request for the descriptor of the first one
2579 on your list. (Tor considered launching requests for the others, but
2580 found that it already had a connection on the way for $0000...0000
2581 so it didn't open another.) Bugfix on 0.2.0.x.
2582 - If you have more than one bridge but don't know their keys, and the
2583 connection to one of the bridges failed, you would cancel all
2584 pending bridge connections. (After all, they all have the same
2585 digest.) Bugfix on 0.2.0.x.
2586 - When a hidden service was trying to establish an introduction point,
2587 and Tor had built circuits preemptively for such purposes, we
2588 were ignoring all the preemptive circuits and launching a new one
2589 instead. Bugfix on 0.2.0.14-alpha.
2590 - When a hidden service was trying to establish an introduction point,
2591 and Tor *did* manage to reuse one of the preemptively built
2592 circuits, it didn't correctly remember which one it used,
2593 so it asked for another one soon after, until there were no
2594 more preemptive circuits, at which point it launched one from
2595 scratch. Bugfix on 0.0.9.x.
2596 - Make directory servers include the X-Your-Address-Is: http header in
2597 their responses even for begin_dir conns. Now clients who only
2598 ever use begin_dir connections still have a way to learn their IP
2599 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
2602 - Fix a macro/CPP interaction that was confusing some compilers:
2603 some GCCs don't like #if/#endif pairs inside macro arguments.
2605 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
2606 Fixes bug 704; fix from Steven Murdoch.
2607 - When opening /dev/null in finish_daemonize(), do not pass the
2608 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
2609 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
2610 - Correctly detect transparent proxy support on Linux hosts that
2611 require in.h to be included before netfilter_ipv4.h. Patch
2613 - Disallow session resumption attempts during the renegotiation
2614 stage of the v2 handshake protocol. Clients should never be trying
2615 session resumption at this point, but apparently some did, in
2616 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
2617 found by Geoff Goodell.
2620 Changes in version 0.2.1.2-alpha - 2008-06-20
2621 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
2622 make it easier to set up your own private Tor network; fixes several
2623 big bugs with using more than one bridge relay; fixes a big bug with
2624 offering hidden services quickly after Tor starts; and uses a better
2625 API for reporting potential bootstrapping problems to the controller.
2628 - New TestingTorNetwork config option to allow adjustment of
2629 previously constant values that, while reasonable, could slow
2630 bootstrapping. Implements proposal 135. Patch from Karsten.
2633 - If you have more than one bridge but don't know their digests,
2634 you would only learn a request for the descriptor of the first one
2635 on your list. (Tor considered launching requests for the others, but
2636 found that it already had a connection on the way for $0000...0000
2637 so it didn't open another.) Bugfix on 0.2.0.x.
2638 - If you have more than one bridge but don't know their digests,
2639 and the connection to one of the bridges failed, you would cancel
2640 all pending bridge connections. (After all, they all have the
2641 same digest.) Bugfix on 0.2.0.x.
2642 - When establishing a hidden service, introduction points that
2643 originate from cannibalized circuits are completely ignored and not
2644 included in rendezvous service descriptors. This might be another
2645 reason for delay in making a hidden service available. Bugfix
2646 from long ago (0.0.9.x?)
2649 - Allow OpenSSL to use dynamic locks if it wants.
2650 - When building a consensus, do not include routers that are down.
2651 This will cut down 30% to 40% on consensus size. Implements
2653 - In directory authorities' approved-routers files, allow
2654 fingerprints with or without space.
2655 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
2656 controller can query our current bootstrap state in case it attaches
2657 partway through and wants to catch up.
2658 - Send an initial "Starting" bootstrap status event, so we have a
2659 state to start out in.
2662 - Asking for a conditional consensus at .../consensus/<fingerprints>
2663 would crash a dirserver if it did not already have a
2664 consensus. Bugfix on 0.2.1.1-alpha.
2665 - Clean up some macro/CPP interactions: some GCC versions don't like
2666 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
2669 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
2670 - Directory authorities shouldn't complain about bootstrapping
2671 problems just because they do a lot of reachability testing and
2672 some of the connection attempts fail.
2673 - Start sending "count" and "recommendation" key/value pairs in
2674 bootstrap problem status events, so the controller can hear about
2675 problems even before Tor decides they're worth reporting for sure.
2676 - If you're using bridges, generate "bootstrap problem" warnings
2677 as soon as you run out of working bridges, rather than waiting
2678 for ten failures -- which will never happen if you have less than
2680 - If we close our OR connection because there's been a circuit
2681 pending on it for too long, we were telling our bootstrap status
2682 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
2685 Changes in version 0.2.1.1-alpha - 2008-06-13
2686 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
2687 were making the Tor process bloat especially on Linux; makes our TLS
2688 handshake blend in better; sends "bootstrap phase" status events to
2689 the controller, so it can keep the user informed of progress (and
2690 problems) fetching directory information and establishing circuits;
2691 and adds a variety of smaller features.
2694 - More work on making our TLS handshake blend in: modify the list
2695 of ciphers advertised by OpenSSL in client mode to even more
2696 closely resemble a common web browser. We cheat a little so that
2697 we can advertise ciphers that the locally installed OpenSSL doesn't
2699 - Start sending "bootstrap phase" status events to the controller,
2700 so it can keep the user informed of progress fetching directory
2701 information and establishing circuits. Also inform the controller
2702 if we think we're stuck at a particular bootstrap phase. Implements
2704 - Resume using OpenSSL's RAND_poll() for better (and more portable)
2705 cross-platform entropy collection again. We used to use it, then
2706 stopped using it because of a bug that could crash systems that
2707 called RAND_poll when they had a lot of fds open. It looks like the
2708 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
2709 at startup, and to call RAND_poll() when we reseed later only if
2710 we have a non-buggy OpenSSL version.
2713 - When we choose to abandon a new entry guard because we think our
2714 older ones might be better, close any circuits pending on that
2715 new entry guard connection. This fix should make us recover much
2716 faster when our network is down and then comes back. Bugfix on
2717 0.1.2.8-beta; found by lodger.
2719 o Memory fixes and improvements:
2720 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
2721 to avoid unused RAM in buffer chunks and memory pools.
2722 - Speed up parsing and cut down on memory fragmentation by using
2723 stack-style allocations for parsing directory objects. Previously,
2724 this accounted for over 40% of allocations from within Tor's code
2725 on a typical directory cache.
2726 - Use a Bloom filter rather than a digest-based set to track which
2727 descriptors we need to keep around when we're cleaning out old
2728 router descriptors. This speeds up the computation significantly,
2729 and may reduce fragmentation.
2730 - Reduce the default smartlist size from 32 to 16; it turns out that
2731 most smartlists hold around 8-12 elements tops.
2732 - Make dumpstats() log the fullness and size of openssl-internal
2734 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
2735 patch to their OpenSSL, turn it on to save memory on servers. This
2736 patch will (with any luck) get included in a mainline distribution
2738 - Never use OpenSSL compression: it wastes RAM and CPU trying to
2739 compress cells, which are basically all encrypted, compressed,
2743 - Stop reloading the router list from disk for no reason when we
2744 run out of reachable directory mirrors. Once upon a time reloading
2745 it would set the 'is_running' flag back to 1 for them. It hasn't
2746 done that for a long time.
2747 - In very rare situations new hidden service descriptors were
2748 published earlier than 30 seconds after the last change to the
2749 service. (We currently think that a hidden service descriptor
2750 that's been stable for 30 seconds is worth publishing.)
2753 - Allow separate log levels to be configured for different logging
2754 domains. For example, this allows one to log all notices, warnings,
2755 or errors, plus all memory management messages of level debug or
2756 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
2757 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
2758 and stop using a warning that had become unfixably verbose under
2760 - New --hush command-line option similar to --quiet. While --quiet
2761 disables all logging to the console on startup, --hush limits the
2762 output to messages of warning and error severity.
2763 - Servers support a new URL scheme for consensus downloads that
2764 allows the client to specify which authorities are trusted.
2765 The server then only sends the consensus if the client will trust
2766 it. Otherwise a 404 error is sent back. Clients use this
2767 new scheme when the server supports it (meaning it's running
2768 0.2.1.1-alpha or later). Implements proposal 134.
2769 - New configure/torrc options (--enable-geoip-stats,
2770 DirRecordUsageByCountry) to record how many IPs we've served
2771 directory info to in each country code, how many status documents
2772 total we've sent to each country code, and what share of the total
2773 directory requests we should expect to see.
2774 - Use the TLS1 hostname extension to more closely resemble browser
2776 - Lots of new unit tests.
2777 - Add a macro to implement the common pattern of iterating through
2778 two parallel lists in lockstep.
2781 Changes in version 0.2.0.28-rc - 2008-06-13
2782 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
2783 performance bug, and fixes a bunch of smaller bugs.
2786 - Fix a bug where, when we were choosing the 'end stream reason' to
2787 put in our relay end cell that we send to the exit relay, Tor
2788 clients on Windows were sometimes sending the wrong 'reason'. The
2789 anonymity problem is that exit relays may be able to guess whether
2790 the client is running Windows, thus helping partition the anonymity
2791 set. Down the road we should stop sending reasons to exit relays,
2792 or otherwise prevent future versions of this bug.
2795 - While setting up a hidden service, some valid introduction circuits
2796 were overlooked and abandoned. This might be the reason for
2797 the long delay in making a hidden service available. Bugfix on
2801 - Update to the "June 9 2008" ip-to-country file.
2802 - Run 'make test' as part of 'make dist', so we stop releasing so
2803 many development snapshots that fail their unit tests.
2806 - When we're checking if we have enough dir info for each relay
2807 to begin establishing circuits, make sure that we actually have
2808 the descriptor listed in the consensus, not just any descriptor.
2810 - Bridge relays no longer print "xx=0" in their extrainfo document
2811 for every single country code in the geoip db. Bugfix on
2813 - Only warn when we fail to load the geoip file if we were planning to
2814 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
2815 - If we change our MaxAdvertisedBandwidth and then reload torrc,
2816 Tor won't realize it should publish a new relay descriptor. Fixes
2817 bug 688, reported by mfr. Bugfix on 0.1.2.x.
2818 - When we haven't had any application requests lately, don't bother
2819 logging that we have expired a bunch of descriptors. Bugfix
2821 - Make relay cells written on a connection count as non-padding when
2822 tracking how long a connection has been in use. Bugfix on
2823 0.2.0.1-alpha. Spotted by lodger.
2824 - Fix unit tests in 0.2.0.27-rc.
2825 - Fix compile on Windows.
2828 Changes in version 0.2.0.27-rc - 2008-06-03
2829 Tor 0.2.0.27-rc adds a few features we left out of the earlier
2830 release candidates. In particular, we now include an IP-to-country
2831 GeoIP database, so controllers can easily look up what country a
2832 given relay is in, and so bridge relays can give us some sanitized
2833 summaries about which countries are making use of bridges. (See proposal
2834 126-geoip-fetching.txt for details.)
2837 - Include an IP-to-country GeoIP file in the tarball, so bridge
2838 relays can report sanitized summaries of the usage they're seeing.
2841 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
2842 Robert Hogan. Fixes the first part of bug 681.
2843 - Make bridge authorities never serve extrainfo docs.
2844 - Add support to detect Libevent versions in the 1.4.x series
2846 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
2847 - Include a new contrib/tor-exit-notice.html file that exit relay
2848 operators can put on their website to help reduce abuse queries.
2851 - When tunneling an encrypted directory connection, and its first
2852 circuit fails, do not leave it unattached and ask the controller
2853 to deal. Fixes the second part of bug 681.
2854 - Make bridge authorities correctly expire old extrainfo documents
2858 Changes in version 0.2.0.26-rc - 2008-05-13
2859 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
2860 in Debian's OpenSSL packages. All users running any 0.2.0.x version
2861 should upgrade, whether they're running Debian or not.
2863 o Major security fixes:
2864 - Use new V3 directory authority keys on the tor26, gabelmoo, and
2865 moria1 V3 directory authorities. The old keys were generated with
2866 a vulnerable version of Debian's OpenSSL package, and must be
2867 considered compromised. Other authorities' keys were not generated
2868 with an affected version of OpenSSL.
2871 - List authority signatures as "unrecognized" based on DirServer
2872 lines, not on cert cache. Bugfix on 0.2.0.x.
2875 - Add a new V3AuthUseLegacyKey option to make it easier for
2876 authorities to change their identity keys if they have to.
2879 Changes in version 0.2.0.25-rc - 2008-04-23
2880 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
2883 - Remember to initialize threading before initializing logging.
2884 Otherwise, many BSD-family implementations will crash hard on
2885 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
2888 - Authorities correctly free policies on bad servers on
2889 exit. Fixes bug 672. Bugfix on 0.2.0.x.
2892 Changes in version 0.2.0.24-rc - 2008-04-22
2893 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
2894 v3 directory authority, makes relays with dynamic IP addresses and no
2895 DirPort notice more quickly when their IP address changes, fixes a few
2896 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
2898 o New directory authorities:
2899 - Take lefkada out of the list of v3 directory authorities, since
2900 it has been down for months.
2901 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
2905 - Detect address changes more quickly on non-directory mirror
2906 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
2908 o Minor features (security):
2909 - Reject requests for reverse-dns lookup of names that are in
2910 a private address space. Patch from lodger.
2911 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
2914 o Minor bugfixes (crashes):
2915 - Avoid a rare assert that can trigger when Tor doesn't have much
2916 directory information yet and it tries to fetch a v2 hidden
2917 service descriptor. Fixes bug 651, reported by nwf.
2918 - Initialize log mutex before initializing dmalloc. Otherwise,
2919 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
2920 - Use recursive pthread mutexes in order to avoid deadlock when
2921 logging debug-level messages to a controller. Bug spotted by nwf,
2922 bugfix on 0.2.0.16-alpha.
2924 o Minor bugfixes (resource management):
2925 - Keep address policies from leaking memory: start their refcount
2926 at 1, not 2. Bugfix on 0.2.0.16-alpha.
2927 - Free authority certificates on exit, so they don't look like memory
2928 leaks. Bugfix on 0.2.0.19-alpha.
2929 - Free static hashtables for policy maps and for TLS connections on
2930 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
2931 - Avoid allocating extra space when computing consensuses on 64-bit
2932 platforms. Bug spotted by aakova.
2934 o Minor bugfixes (misc):
2935 - Do not read the configuration file when we've only been told to
2936 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
2937 based on patch from Sebastian Hahn.
2938 - Exit relays that are used as a client can now reach themselves
2939 using the .exit notation, rather than just launching an infinite
2940 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
2941 - When attempting to open a logfile fails, tell us why.
2942 - Fix a dumb bug that was preventing us from knowing that we should
2943 preemptively build circuits to handle expected directory requests.
2944 Fixes bug 660. Bugfix on 0.1.2.x.
2945 - Warn less verbosely about clock skew from netinfo cells from
2946 untrusted sources. Fixes bug 663.
2947 - Make controller stream events for DNS requests more consistent,
2948 by adding "new stream" events for DNS requests, and removing
2949 spurious "stream closed" events" for cached reverse resolves.
2950 Patch from mwenge. Fixes bug 646.
2951 - Correctly notify one-hop connections when a circuit build has
2952 failed. Possible fix for bug 669. Found by lodger.
2955 Changes in version 0.2.0.23-rc - 2008-03-24
2956 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
2957 makes bootstrapping faster if the first directory mirror you contact
2958 is down. The bundles also include the new Vidalia 0.1.2 release.
2961 - When a tunneled directory request is made to a directory server
2962 that's down, notice after 30 seconds rather than 120 seconds. Also,
2963 fail any begindir streams that are pending on it, so they can
2964 retry elsewhere. This was causing multi-minute delays on bootstrap.
2967 Changes in version 0.2.0.22-rc - 2008-03-18
2968 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
2969 enables encrypted directory connections by default for non-relays, fixes
2970 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
2971 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
2974 - Enable encrypted directory connections by default for non-relays,
2975 so censor tools that block Tor directory connections based on their
2976 plaintext patterns will no longer work. This means Tor works in
2977 certain censored countries by default again.
2980 - Make sure servers always request certificates from clients during
2981 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
2982 - Do not enter a CPU-eating loop when a connection is closed in
2983 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
2984 diagnosed by lodger; bugfix on 0.2.0.20-rc.
2985 - Fix assertion failure that could occur when a blocked circuit
2986 became unblocked, and it had pending client DNS requests. Bugfix
2987 on 0.2.0.1-alpha. Fixes bug 632.
2989 o Minor bugfixes (on 0.1.2.x):
2990 - Generate "STATUS_SERVER" events rather than misspelled
2991 "STATUS_SEVER" events. Caught by mwenge.
2992 - When counting the number of bytes written on a TLS connection,
2993 look at the BIO actually used for writing to the network, not
2994 at the BIO used (sometimes) to buffer data for the network.
2995 Looking at different BIOs could result in write counts on the
2996 order of ULONG_MAX. Fixes bug 614.
2997 - On Windows, correctly detect errors when listing the contents of
2998 a directory. Fix from lodger.
3000 o Minor bugfixes (on 0.2.0.x):
3001 - Downgrade "sslv3 alert handshake failure" message to INFO.
3002 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
3003 left BandwidthRate and BandwidthBurst at the default, we would be
3004 silently limited by those defaults. Now raise them to match the
3005 RelayBandwidth* values.
3006 - Fix the SVK version detection logic to work correctly on a branch.
3007 - Make --enable-openbsd-malloc work correctly on Linux with alpha
3008 CPUs. Fixes bug 625.
3009 - Logging functions now check that the passed severity is sane.
3010 - Use proper log levels in the testsuite call of
3011 get_interface_address6().
3012 - When using a nonstandard malloc, do not use the platform values for
3013 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
3014 - Make the openbsd malloc code use 8k pages on alpha CPUs and
3016 - Detect mismatched page sizes when using --enable-openbsd-malloc.
3017 - Avoid double-marked-for-close warning when certain kinds of invalid
3018 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
3019 for bug 617. Bugfix on 0.2.0.1-alpha.
3020 - Make sure that the "NULL-means-reject *:*" convention is followed by
3021 all the policy manipulation functions, avoiding some possible crash
3022 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
3023 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
3024 actually works, and doesn't warn about every single reverse lookup.
3025 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
3028 - Only log guard node status when guard node status has changed.
3029 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
3030 make "INFO" 75% less verbose.
3033 Changes in version 0.2.0.21-rc - 2008-03-02
3034 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
3035 makes Tor work well with Vidalia again, fixes a rare assert bug,
3036 and fixes a pair of more minor bugs. The bundles also include Vidalia
3037 0.1.0 and Torbutton 1.1.16.
3040 - The control port should declare that it requires password auth
3041 when HashedControlSessionPassword is set too. Patch from Matt Edman;
3042 bugfix on 0.2.0.20-rc. Fixes bug 615.
3043 - Downgrade assert in connection_buckets_decrement() to a log message.
3044 This may help us solve bug 614, and in any case will make its
3045 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
3046 - We were sometimes miscounting the number of bytes read from the
3047 network, causing our rate limiting to not be followed exactly.
3048 Bugfix on 0.2.0.16-alpha. Reported by lodger.
3051 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
3052 OpenSSL versions should have been working fine. Diagnosis and patch
3053 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
3054 Bugfix on 0.2.0.20-rc.
3057 Changes in version 0.2.0.20-rc - 2008-02-24
3058 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
3059 makes more progress towards normalizing Tor's TLS handshake, makes
3060 hidden services work better again, helps relays bootstrap if they don't
3061 know their IP address, adds optional support for linking in openbsd's
3062 allocator or tcmalloc, allows really fast relays to scale past 15000
3063 sockets, and fixes a bunch of minor bugs reported by Veracode.
3066 - Enable the revised TLS handshake based on the one designed by
3067 Steven Murdoch in proposal 124, as revised in proposal 130. It
3068 includes version negotiation for OR connections as described in
3069 proposal 105. The new handshake is meant to be harder for censors
3070 to fingerprint, and it adds the ability to detect certain kinds of
3071 man-in-the-middle traffic analysis attacks. The version negotiation
3072 feature will allow us to improve Tor's link protocol more safely
3074 - Choose which bridge to use proportional to its advertised bandwidth,
3075 rather than uniformly at random. This should speed up Tor for
3076 bridge users. Also do this for people who set StrictEntryNodes.
3077 - When a TrackHostExits-chosen exit fails too many times in a row,
3078 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
3081 - Resolved problems with (re-)fetching hidden service descriptors.
3082 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
3084 - If we only ever used Tor for hidden service lookups or posts, we
3085 would stop building circuits and start refusing connections after
3086 24 hours, since we falsely believed that Tor was dormant. Reported
3087 by nwf; bugfix on 0.1.2.x.
3088 - Servers that don't know their own IP address should go to the
3089 authorities for their first directory fetch, even if their DirPort
3090 is off or if they don't know they're reachable yet. This will help
3091 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
3092 - When counting the number of open sockets, count not only the number
3093 of sockets we have received from the socket() call, but also
3094 the number we've gotten from accept() and socketpair(). This bug
3095 made us fail to count all sockets that we were using for incoming
3096 connections. Bugfix on 0.2.0.x.
3097 - Fix code used to find strings within buffers, when those strings
3098 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
3099 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
3100 - Add a new __HashedControlSessionPassword option for controllers
3101 to use for one-off session password hashes that shouldn't get
3102 saved to disk by SAVECONF --- Vidalia users were accumulating a
3103 pile of HashedControlPassword lines in their torrc files, one for
3104 each time they had restarted Tor and then clicked Save. Make Tor
3105 automatically convert "HashedControlPassword" to this new option but
3106 only when it's given on the command line. Partial fix for bug 586.
3108 o Minor features (performance):
3109 - Tune parameters for cell pool allocation to minimize amount of
3111 - Add OpenBSD malloc code from phk as an optional malloc
3112 replacement on Linux: some glibc libraries do very poorly
3113 with Tor's memory allocation patterns. Pass
3114 --enable-openbsd-malloc to get the replacement malloc code.
3115 - Add a --with-tcmalloc option to the configure script to link
3116 against tcmalloc (if present). Does not yet search for
3117 non-system include paths.
3118 - Stop imposing an arbitrary maximum on the number of file descriptors
3119 used for busy servers. Bug reported by Olaf Selke; patch from
3122 o Minor features (other):
3123 - When SafeLogging is disabled, log addresses along with all TLS
3125 - When building with --enable-gcc-warnings, check for whether Apple's
3126 warning "-Wshorten-64-to-32" is available.
3127 - Add a --passphrase-fd argument to the tor-gencert command for
3130 o Minor bugfixes (memory leaks and code problems):
3131 - We were leaking a file descriptor if Tor started with a zero-length
3132 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
3133 - Detect size overflow in zlib code. Reported by Justin Ferguson and
3135 - We were comparing the raw BridgePassword entry with a base64'ed
3136 version of it, when handling a "/tor/networkstatus-bridges"
3137 directory request. Now compare correctly. Noticed by Veracode.
3138 - Recover from bad tracked-since value in MTBF-history file.
3140 - Alter the code that tries to recover from unhandled write
3141 errors, to not try to flush onto a socket that's given us
3142 unhandled errors. Bugfix on 0.1.2.x.
3143 - Make Unix controlsockets work correctly on OpenBSD. Patch from
3144 tup. Bugfix on 0.2.0.3-alpha.
3146 o Minor bugfixes (other):
3147 - If we have an extra-info document for our server, always make
3148 it available on the control port, even if we haven't gotten
3149 a copy of it from an authority yet. Patch from mwenge.
3150 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
3151 - Directory mirrors no longer include a guess at the client's IP
3152 address if the connection appears to be coming from the same /24
3153 network; it was producing too many wrong guesses.
3154 - Make the new hidden service code respect the SafeLogging setting.
3155 Bugfix on 0.2.0.x. Patch from Karsten.
3156 - When starting as an authority, do not overwrite all certificates
3157 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
3158 - If we're trying to flush the last bytes on a connection (for
3159 example, when answering a directory request), reset the
3160 time-to-give-up timeout every time we manage to write something
3161 on the socket. Bugfix on 0.1.2.x.
3162 - Change the behavior of "getinfo status/good-server-descriptor"
3163 so it doesn't return failure when any authority disappears.
3164 - Even though the man page said that "TrackHostExits ." should
3165 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
3166 - Report TLS "zero return" case as a "clean close" and "IO error"
3167 as a "close". Stop calling closes "unexpected closes": existing
3168 Tors don't use SSL_close(), so having a connection close without
3169 the TLS shutdown handshake is hardly unexpected.
3170 - Send NAMESERVER_STATUS messages for a single failed nameserver
3173 o Code simplifications and refactoring:
3174 - Remove the tor_strpartition function: its logic was confused,
3175 and it was only used for one thing that could be implemented far
3179 Changes in version 0.2.0.19-alpha - 2008-02-09
3180 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
3181 handshake, makes path selection for relays more secure and IP address
3182 guessing more robust, and generally fixes a lot of bugs in preparation
3183 for calling the 0.2.0 branch stable.
3186 - Do not include recognizeable strings in the commonname part of
3187 Tor's x509 certificates.
3190 - If we're a relay, avoid picking ourselves as an introduction point,
3191 a rendezvous point, or as the final hop for internal circuits. Bug
3192 reported by taranis and lodger. Bugfix on 0.1.2.x.
3193 - Patch from "Andrew S. Lists" to catch when we contact a directory
3194 mirror at IP address X and he says we look like we're coming from
3195 IP address X. Bugfix on 0.1.2.x.
3197 o Minor features (security):
3198 - Be more paranoid about overwriting sensitive memory on free(),
3199 as a defensive programming tactic to ensure forward secrecy.
3201 o Minor features (directory authority):
3202 - Actually validate the options passed to AuthDirReject,
3203 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
3204 - Reject router descriptors with out-of-range bandwidthcapacity or
3205 bandwidthburst values.
3207 o Minor features (controller):
3208 - Reject controller commands over 1MB in length. This keeps rogue
3209 processes from running us out of memory.
3211 o Minor features (misc):
3212 - Give more descriptive well-formedness errors for out-of-range
3213 hidden service descriptor/protocol versions.
3214 - Make memory debugging information describe more about history
3215 of cell allocation, so we can help reduce our memory use.
3217 o Deprecated features (controller):
3218 - The status/version/num-versioning and status/version/num-concurring
3219 GETINFO options are no longer useful in the v3 directory protocol:
3220 treat them as deprecated, and warn when they're used.
3223 - When our consensus networkstatus has been expired for a while, stop
3224 being willing to build circuits using it. Fixes bug 401. Bugfix
3226 - Directory caches now fetch certificates from all authorities
3227 listed in a networkstatus consensus, even when they do not
3228 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
3229 - When connecting to a bridge without specifying its key, insert
3230 the connection into the identity-to-connection map as soon as
3231 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
3232 - Detect versions of OS X where malloc_good_size() is present in the
3233 library but never actually declared. Resolves bug 587. Bugfix
3235 - Stop incorrectly truncating zlib responses to directory authority
3236 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
3237 - Stop recommending that every server operator send mail to tor-ops.
3238 Resolves bug 597. Bugfix on 0.1.2.x.
3239 - Don't trigger an assert if we start a directory authority with a
3240 private IP address (like 127.0.0.1).
3241 - Avoid possible failures when generating a directory with routers
3242 with over-long versions strings, or too many flags set. Bugfix
3244 - If an attempt to launch a DNS resolve request over the control
3245 port fails because we have overrun the limit on the number of
3246 connections, tell the controller that the request has failed.
3247 - Avoid using too little bandwidth when our clock skips a few
3248 seconds. Bugfix on 0.1.2.x.
3249 - Fix shell error when warning about missing packages in configure
3250 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
3251 - Do not become confused when receiving a spurious VERSIONS-like
3252 cell from a confused v1 client. Bugfix on 0.2.0.x.
3253 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
3254 introduction points for a hidden service have failed. Patch from
3255 Karsten Loesing. Bugfix on 0.2.0.x.
3257 o Code simplifications and refactoring:
3258 - Remove some needless generality from cpuworker code, for improved
3260 - Stop overloading the circuit_t.onionskin field for both "onionskin
3261 from a CREATE cell that we are waiting for a cpuworker to be
3262 assigned" and "onionskin from an EXTEND cell that we are going to
3263 send to an OR as soon as we are connected". Might help with bug 600.
3264 - Add an in-place version of aes_crypt() so that we can avoid doing a
3265 needless memcpy() call on each cell payload.
3268 Changes in version 0.2.0.18-alpha - 2008-01-25
3269 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
3270 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
3271 that can warn or reject connections to ports generally associated with
3272 vulnerable-plaintext protocols.
3274 o New directory authorities:
3275 - Set up dannenberg (run by CCC) as the sixth v3 directory
3279 - Fix a major memory leak when attempting to use the v2 TLS
3280 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
3281 - We accidentally enabled the under-development v2 TLS handshake
3282 code, which was causing log entries like "TLS error while
3283 renegotiating handshake". Disable it again. Resolves bug 590.
3284 - We were computing the wrong Content-Length: header for directory
3285 responses that need to be compressed on the fly, causing clients
3286 asking for those items to always fail. Bugfix on 0.2.0.x; partially
3290 - Avoid going directly to the directory authorities even if you're a
3291 relay, if you haven't found yourself reachable yet or if you've
3292 decided not to advertise your dirport yet. Addresses bug 556.
3293 - If we've gone 12 hours since our last bandwidth check, and we
3294 estimate we have less than 50KB bandwidth capacity but we could
3295 handle more, do another bandwidth test.
3296 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
3297 Tor can warn and/or refuse connections to ports commonly used with
3298 vulnerable-plaintext protocols. Currently we warn on ports 23,
3299 109, 110, and 143, but we don't reject any.
3302 - When we setconf ClientOnly to 1, close any current OR and Dir
3303 listeners. Reported by mwenge.
3304 - When we get a consensus that's been signed by more people than
3305 we expect, don't log about it; it's not a big deal. Reported
3309 - Don't answer "/tor/networkstatus-bridges" directory requests if
3310 the request isn't encrypted.
3311 - Make "ClientOnly 1" config option disable directory ports too.
3312 - Patches from Karsten Loesing to make v2 hidden services more
3313 robust: work even when there aren't enough HSDir relays available;
3314 retry when a v2 rend desc fetch fails; but don't retry if we
3315 already have a usable v0 rend desc.
3318 Changes in version 0.2.0.17-alpha - 2008-01-17
3319 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
3322 - Make the tor-gencert man page get included correctly in the tarball.
3325 Changes in version 0.2.0.16-alpha - 2008-01-17
3326 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
3327 Loesing, and generally cleans up a lot of features and minor bugs.
3329 o New directory authorities:
3330 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
3333 o Major performance improvements:
3334 - Switch our old ring buffer implementation for one more like that
3335 used by free Unix kernels. The wasted space in a buffer with 1mb
3336 of data will now be more like 8k than 1mb. The new implementation
3337 also avoids realloc();realloc(); patterns that can contribute to
3338 memory fragmentation.
3341 - Configuration files now accept C-style strings as values. This
3342 helps encode characters not allowed in the current configuration
3343 file format, such as newline or #. Addresses bug 557.
3344 - Although we fixed bug 539 (where servers would send HTTP status 503
3345 responses _and_ send a body too), there are still servers out
3346 there that haven't upgraded. Therefore, make clients parse such
3347 bodies when they receive them.
3348 - When we're not serving v2 directory information, there is no reason
3349 to actually keep any around. Remove the obsolete files and directory
3350 on startup if they are very old and we aren't going to serve them.
3352 o Minor performance improvements:
3353 - Reference-count and share copies of address policy entries; only 5%
3354 of them were actually distinct.
3355 - Never walk through the list of logs if we know that no log is
3356 interested in a given message.
3359 - When an authority has not signed a consensus, do not try to
3360 download a nonexistent "certificate with key 00000000". Bugfix
3361 on 0.2.0.x. Fixes bug 569.
3362 - Fix a rare assert error when we're closing one of our threads:
3363 use a mutex to protect the list of logs, so we never write to the
3364 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
3365 bug 575, which is kind of the revenge of bug 222.
3366 - Patch from Karsten Loesing to complain less at both the client
3367 and the relay when a relay used to have the HSDir flag but doesn't
3368 anymore, and we try to upload a hidden service descriptor.
3369 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
3371 - Do not try to download missing certificates until we have tried
3372 to check our fallback consensus. Fixes bug 583.
3373 - Make bridges round reported GeoIP stats info up to the nearest
3374 estimate, not down. Now we can distinguish between "0 people from
3375 this country" and "1 person from this country".
3376 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
3377 - Avoid possible segfault if key generation fails in
3378 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
3379 - Avoid segfault in the case where a badly behaved v2 versioning
3380 directory sends a signed networkstatus with missing client-versions.
3382 - Avoid segfaults on certain complex invocations of
3383 router_get_by_hexdigest(). Bugfix on 0.1.2.
3384 - Correct bad index on array access in parse_http_time(). Bugfix
3386 - Fix possible bug in vote generation when server versions are present
3387 but client versions are not.
3388 - Fix rare bug on REDIRECTSTREAM control command when called with no
3389 port set: it could erroneously report an error when none had
3391 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
3392 compressing large objects and find ourselves with more than 4k
3393 left over. Bugfix on 0.2.0.
3394 - Fix a small memory leak when setting up a hidden service.
3395 - Fix a few memory leaks that could in theory happen under bizarre
3397 - Fix an assert if we post a general-purpose descriptor via the
3398 control port but that descriptor isn't mentioned in our current
3399 network consensus. Bug reported by Jon McLachlan; bugfix on
3402 o Minor features (controller):
3403 - Get NS events working again. Patch from tup.
3404 - The GETCONF command now escapes and quotes configuration values
3405 that don't otherwise fit into the torrc file.
3406 - The SETCONF command now handles quoted values correctly.
3408 o Minor features (directory authorities):
3409 - New configuration options to override default maximum number of
3410 servers allowed on a single IP address. This is important for
3411 running a test network on a single host.
3412 - Actually implement the -s option to tor-gencert.
3413 - Add a manual page for tor-gencert.
3415 o Minor features (bridges):
3416 - Bridge authorities no longer serve bridge descriptors over
3417 unencrypted connections.
3419 o Minor features (other):
3420 - Add hidden services and DNSPorts to the list of things that make
3421 Tor accept that it has running ports. Change starting Tor with no
3422 ports from a fatal error to a warning; we might change it back if
3423 this turns out to confuse anybody. Fixes bug 579.
3426 Changes in version 0.1.2.19 - 2008-01-17
3427 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
3428 exit policy a little bit more conservative so it's safer to run an
3429 exit relay on a home system, and fixes a variety of smaller issues.
3432 - Exit policies now reject connections that are addressed to a
3433 relay's public (external) IP address too, unless
3434 ExitPolicyRejectPrivate is turned off. We do this because too
3435 many relays are running nearby to services that trust them based
3439 - When the clock jumps forward a lot, do not allow the bandwidth
3440 buckets to become negative. Fixes bug 544.
3441 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
3442 on every successful resolve. Reported by Mike Perry.
3443 - Purge old entries from the "rephist" database and the hidden
3444 service descriptor database even when DirPort is zero.
3445 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
3446 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
3447 crashing or mis-answering these requests.
3448 - When we decide to send a 503 response to a request for servers, do
3449 not then also send the server descriptors: this defeats the whole
3450 purpose. Fixes bug 539.
3453 - Changing the ExitPolicyRejectPrivate setting should cause us to
3454 rebuild our server descriptor.
3455 - Fix handling of hex nicknames when answering controller requests for
3456 networkstatus by name, or when deciding whether to warn about
3457 unknown routers in a config option. (Patch from mwenge.)
3458 - Fix a couple of hard-to-trigger autoconf problems that could result
3459 in really weird results on platforms whose sys/types.h files define
3460 nonstandard integer types.
3461 - Don't try to create the datadir when running --verify-config or
3462 --hash-password. Resolves bug 540.
3463 - If we were having problems getting a particular descriptor from the
3464 directory caches, and then we learned about a new descriptor for
3465 that router, we weren't resetting our failure count. Reported
3467 - Although we fixed bug 539 (where servers would send HTTP status 503
3468 responses _and_ send a body too), there are still servers out there
3469 that haven't upgraded. Therefore, make clients parse such bodies
3470 when they receive them.
3471 - Run correctly on systems where rlim_t is larger than unsigned long.
3472 This includes some 64-bit systems.
3473 - Run correctly on platforms (like some versions of OS X 10.5) where
3474 the real limit for number of open files is OPEN_FILES, not rlim_max
3475 from getrlimit(RLIMIT_NOFILES).
3476 - Avoid a spurious free on base64 failure.
3477 - Avoid segfaults on certain complex invocations of
3478 router_get_by_hexdigest().
3479 - Fix rare bug on REDIRECTSTREAM control command when called with no
3480 port set: it could erroneously report an error when none had
3484 Changes in version 0.2.0.15-alpha - 2007-12-25
3485 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
3486 features added in 0.2.0.13-alpha.
3489 - Fix several remotely triggerable asserts based on DirPort requests
3490 for a v2 or v3 networkstatus object before we were prepared. This
3491 was particularly bad for 0.2.0.13 and later bridge relays, who
3492 would never have a v2 networkstatus and would thus always crash
3493 when used. Bugfixes on 0.2.0.x.
3494 - Estimate the v3 networkstatus size more accurately, rather than
3495 estimating it at zero bytes and giving it artificially high priority
3496 compared to other directory requests. Bugfix on 0.2.0.x.
3499 - Fix configure.in logic for cross-compilation.
3500 - When we load a bridge descriptor from the cache, and it was
3501 previously unreachable, mark it as retriable so we won't just
3502 ignore it. Also, try fetching a new copy immediately. Bugfixes
3504 - The bridge GeoIP stats were counting other relays, for example
3505 self-reachability and authority-reachability tests.
3508 - Support compilation to target iPhone; patch from cjacker huang.
3509 To build for iPhone, pass the --enable-iphone option to configure.
3512 Changes in version 0.2.0.14-alpha - 2007-12-23
3514 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
3515 without a datadirectory from a previous Tor install. Reported
3517 - Fix a crash when we fetch a descriptor that turns out to be
3518 unexpected (it used to be in our networkstatus when we started
3519 fetching it, but it isn't in our current networkstatus), and we
3520 aren't using bridges. Bugfix on 0.2.0.x.
3521 - Fix a crash when accessing hidden services: it would work the first
3522 time you use a given introduction point for your service, but
3523 on subsequent requests we'd be using garbage memory. Fixed by
3524 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
3525 - Fix a crash when we load a bridge descriptor from disk but we don't
3526 currently have a Bridge line for it in our torrc. Bugfix on
3530 - If bridge authorities set BridgePassword, they will serve a
3531 snapshot of known bridge routerstatuses from their DirPort to
3532 anybody who knows that password. Unset by default.
3535 - Make the unit tests build again.
3536 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
3537 - Make PublishServerDescriptor default to 1, so the default doesn't
3538 have to change as we invent new directory protocol versions.
3539 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
3540 be included unless sys/time.h is already included. Fixes
3541 bug 553. Bugfix on 0.2.0.x.
3542 - If we receive a general-purpose descriptor and then receive an
3543 identical bridge-purpose descriptor soon after, don't discard
3544 the next one as a duplicate.
3547 - If BridgeRelay is set to 1, then the default for
3548 PublishServerDescriptor is now "bridge" rather than "v2,v3".
3549 - If the user sets RelayBandwidthRate but doesn't set
3550 RelayBandwidthBurst, then make them equal rather than erroring out.
3553 Changes in version 0.2.0.13-alpha - 2007-12-21
3554 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
3555 Goodell, fixes many more bugs, and adds a lot of infrastructure for
3558 o New directory authorities:
3559 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
3563 - Only update guard status (usable / not usable) once we have
3564 enough directory information. This was causing us to always pick
3565 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
3566 causing us to discard all our guards on startup if we hadn't been
3567 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
3568 - Purge old entries from the "rephist" database and the hidden
3569 service descriptor databases even when DirPort is zero. Bugfix
3571 - We were ignoring our RelayBandwidthRate for the first 30 seconds
3572 after opening a circuit -- even a relayed circuit. Bugfix on
3574 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
3575 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
3576 crashing or mis-answering these types of requests.
3577 - Relays were publishing their server descriptor to v1 and v2
3578 directory authorities, but they didn't try publishing to v3-only
3579 authorities. Fix this; and also stop publishing to v1 authorities.
3581 - When we were reading router descriptors from cache, we were ignoring
3582 the annotations -- so for example we were reading in bridge-purpose
3583 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
3584 - When we decided to send a 503 response to a request for servers, we
3585 were then also sending the server descriptors: this defeats the
3586 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
3589 - Bridge relays now behave like clients with respect to time
3590 intervals for downloading new consensus documents -- otherwise they
3591 stand out. Bridge users now wait until the end of the interval,
3592 so their bridge relay will be sure to have a new consensus document.
3593 - Three new config options (AlternateDirAuthority,
3594 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
3595 user selectively replace the default directory authorities by type,
3596 rather than the all-or-nothing replacement that DirServer offers.
3597 - Tor can now be configured to read a GeoIP file from disk in one
3598 of two formats. This can be used by controllers to map IP addresses
3599 to countries. Eventually, it may support exit-by-country.
3600 - When possible, bridge relays remember which countries users
3601 are coming from, and report aggregate information in their
3602 extra-info documents, so that the bridge authorities can learn
3603 where Tor is blocked.
3604 - Bridge directory authorities now do reachability testing on the
3605 bridges they know. They provide router status summaries to the
3606 controller via "getinfo ns/purpose/bridge", and also dump summaries
3607 to a file periodically.
3608 - Stop fetching directory info so aggressively if your DirPort is
3609 on but your ORPort is off; stop fetching v2 dir info entirely.
3610 You can override these choices with the new FetchDirInfoEarly
3614 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
3615 consensus documents when there are too many relays at a single
3616 IP address. Now clear it in v2 network status documents too, and
3617 also clear it in routerinfo_t when the relay is no longer listed
3618 in the relevant networkstatus document.
3619 - Don't crash if we get an unexpected value for the
3620 PublishServerDescriptor config option. Reported by Matt Edman;
3621 bugfix on 0.2.0.9-alpha.
3622 - Our new v2 hidden service descriptor format allows descriptors
3623 that have no introduction points. But Tor crashed when we tried
3624 to build a descriptor with no intro points (and it would have
3625 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
3627 - Fix building with dmalloc 5.5.2 with glibc.
3628 - Reject uploaded descriptors and extrainfo documents if they're
3629 huge. Otherwise we'll cache them all over the network and it'll
3630 clog everything up. Reported by Aljosha Judmayer.
3631 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
3632 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
3633 - When the DANGEROUS_VERSION controller status event told us we're
3634 running an obsolete version, it used the string "OLD" to describe
3635 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
3636 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
3637 - If we can't expand our list of entry guards (e.g. because we're
3638 using bridges or we have StrictEntryNodes set), don't mark relays
3639 down when they fail a directory request. Otherwise we're too quick
3640 to mark all our entry points down. Bugfix on 0.1.2.x.
3641 - Fix handling of hex nicknames when answering controller requests for
3642 networkstatus by name, or when deciding whether to warn about unknown
3643 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
3644 - Fix a couple of hard-to-trigger autoconf problems that could result
3645 in really weird results on platforms whose sys/types.h files define
3646 nonstandard integer types. Bugfix on 0.1.2.x.
3647 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
3648 - Don't crash on name lookup when we have no current consensus. Fixes
3649 bug 538; bugfix on 0.2.0.x.
3650 - Only Tors that want to mirror the v2 directory info should
3651 create the "cached-status" directory in their datadir. (All Tors
3652 used to create it.) Bugfix on 0.2.0.9-alpha.
3653 - Directory authorities should only automatically download Extra Info
3654 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
3657 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
3658 consumers. (We already do this on HUP.)
3659 - Authorities and caches fetch the v2 networkstatus documents
3660 less often, now that v3 is encouraged.
3661 - Add a new config option BridgeRelay that specifies you want to
3662 be a bridge relay. Right now the only difference is that it makes
3663 you answer begin_dir requests, and it makes you cache dir info,
3664 even if your DirPort isn't on.
3665 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
3666 ask about source, timestamp of arrival, purpose, etc. We need
3667 something like this to help Vidalia not do GeoIP lookups on bridge
3669 - Allow multiple HashedControlPassword config lines, to support
3670 multiple controller passwords.
3671 - Authorities now decide whether they're authoritative for a given
3672 router based on the router's purpose.
3673 - New config options AuthDirBadDir and AuthDirListBadDirs for
3674 authorities to mark certain relays as "bad directories" in the
3675 networkstatus documents. Also supports the "!baddir" directive in
3676 the approved-routers file.
3679 Changes in version 0.2.0.12-alpha - 2007-11-16
3680 This twelfth development snapshot fixes some more build problems as
3681 well as a few minor bugs.
3684 - Make it build on OpenBSD again. Patch from tup.
3685 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
3686 package-building for Red Hat, OS X, etc.
3688 o Minor bugfixes (on 0.1.2.x):
3689 - Changing the ExitPolicyRejectPrivate setting should cause us to
3690 rebuild our server descriptor.
3692 o Minor bugfixes (on 0.2.0.x):
3693 - When we're lacking a consensus, don't try to perform rendezvous
3694 operations. Reported by Karsten Loesing.
3695 - Fix a small memory leak whenever we decide against using a
3696 newly picked entry guard. Reported by Mike Perry.
3697 - When authorities detected more than two relays running on the same
3698 IP address, they were clearing all the status flags but forgetting
3699 to clear the "hsdir" flag. So clients were being told that a
3700 given relay was the right choice for a v2 hsdir lookup, yet they
3701 never had its descriptor because it was marked as 'not running'
3703 - If we're trying to fetch a bridge descriptor and there's no way
3704 the bridge authority could help us (for example, we don't know
3705 a digest, or there is no bridge authority), don't be so eager to
3706 fall back to asking the bridge authority.
3707 - If we're using bridges or have strictentrynodes set, and our
3708 chosen exit is in the same family as all our bridges/entry guards,
3709 then be flexible about families.
3712 - When we negotiate a v2 link-layer connection (not yet implemented),
3713 accept RELAY_EARLY cells and turn them into RELAY cells if we've
3714 negotiated a v1 connection for their next step. Initial code for
3718 Changes in version 0.2.0.11-alpha - 2007-11-12
3719 This eleventh development snapshot fixes some build problems with
3720 the previous snapshot. It also includes a more secure-by-default exit
3721 policy for relays, fixes an enormous memory leak for exit relays, and
3722 fixes another bug where servers were falling out of the directory list.
3725 - Exit policies now reject connections that are addressed to a
3726 relay's public (external) IP address too, unless
3727 ExitPolicyRejectPrivate is turned off. We do this because too
3728 many relays are running nearby to services that trust them based
3729 on network address. Bugfix on 0.1.2.x.
3732 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
3733 on every successful resolve. Reported by Mike Perry; bugfix
3735 - On authorities, never downgrade to old router descriptors simply
3736 because they're listed in the consensus. This created a catch-22
3737 where we wouldn't list a new descriptor because there was an
3738 old one in the consensus, and we couldn't get the new one in the
3739 consensus because we wouldn't list it. Possible fix for bug 548.
3740 Also, this might cause bug 543 to appear on authorities; if so,
3741 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
3743 o Packaging fixes on 0.2.0.10-alpha:
3744 - We were including instructions about what to do with the
3745 src/config/fallback-consensus file, but we weren't actually
3746 including it in the tarball. Disable all of that for now.
3749 - Allow people to say PreferTunnelledDirConns rather than
3750 PreferTunneledDirConns, for those alternate-spellers out there.
3753 - Don't reevaluate all the information from our consensus document
3754 just because we've downloaded a v2 networkstatus that we intend
3755 to cache. Fixes bug 545; bugfix on 0.2.0.x.
3758 Changes in version 0.2.0.10-alpha - 2007-11-10
3759 This tenth development snapshot adds a third v3 directory authority
3760 run by Mike Perry, adds most of Karsten Loesing's new hidden service
3761 descriptor format, fixes a bad crash bug and new bridge bugs introduced
3762 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
3763 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
3764 addresses many more minor issues.
3766 o New directory authorities:
3767 - Set up ides (run by Mike Perry) as the third v3 directory authority.
3770 - Allow tunnelled directory connections to ask for an encrypted
3771 "begin_dir" connection or an anonymized "uses a full Tor circuit"
3772 connection independently. Now we can make anonymized begin_dir
3773 connections for (e.g.) more secure hidden service posting and
3775 - More progress on proposal 114: code from Karsten Loesing to
3776 implement new hidden service descriptor format.
3777 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
3778 accommodate the growing number of servers that use the default
3779 and are reaching it.
3780 - Directory authorities use a new formula for selecting which nodes
3781 to advertise as Guards: they must be in the top 7/8 in terms of
3782 how long we have known about them, and above the median of those
3783 nodes in terms of weighted fractional uptime.
3784 - Make "not enough dir info yet" warnings describe *why* Tor feels
3785 it doesn't have enough directory info yet.
3788 - Stop servers from crashing if they set a Family option (or
3789 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
3791 - Make bridge users work again -- the move to v3 directories in
3792 0.2.0.9-alpha had introduced a number of bugs that made bridges
3793 no longer work for clients.
3794 - When the clock jumps forward a lot, do not allow the bandwidth
3795 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
3797 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
3798 - When the consensus lists a router descriptor that we previously were
3799 mirroring, but that we considered non-canonical, reload the
3800 descriptor as canonical. This fixes bug 543 where Tor servers
3801 would start complaining after a few days that they don't have
3802 enough directory information to build a circuit.
3803 - Consider replacing the current consensus when certificates arrive
3804 that make the pending consensus valid. Previously, we were only
3805 considering replacement when the new certs _didn't_ help.
3806 - Fix an assert error on startup if we didn't already have the
3807 consensus and certs cached in our datadirectory: we were caching
3808 the consensus in consensus_waiting_for_certs but then free'ing it
3810 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
3811 Request) if we need more v3 certs but we've already got pending
3812 requests for all of them.
3813 - Correctly back off from failing certificate downloads. Fixes
3815 - Authorities don't vote on the Running flag if they have been running
3816 for less than 30 minutes themselves. Fixes bug 547, where a newly
3817 started authority would vote that everyone was down.
3820 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
3821 it, it had no AES, and it hasn't seen any security patches since
3825 - Clients now hold circuitless TLS connections open for 1.5 times
3826 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
3827 rebuild a new circuit over them within that timeframe. Previously,
3828 they held them open only for KeepalivePeriod (5 minutes).
3829 - Use "If-Modified-Since" to avoid retrieving consensus
3830 networkstatuses that we already have.
3831 - When we have no consensus, check FallbackNetworkstatusFile (defaults
3832 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
3833 we start knowing some directory caches.
3834 - When we receive a consensus from the future, warn about skew.
3835 - Improve skew reporting: try to give the user a better log message
3836 about how skewed they are, and how much this matters.
3837 - When we have a certificate for an authority, believe that
3838 certificate's claims about the authority's IP address.
3839 - New --quiet command-line option to suppress the default console log.
3840 Good in combination with --hash-password.
3841 - Authorities send back an X-Descriptor-Not-New header in response to
3842 an accepted-but-discarded descriptor upload. Partially implements
3844 - Make the log message for "tls error. breaking." more useful.
3845 - Better log messages about certificate downloads, to attempt to
3846 track down the second incarnation of bug 546.
3848 o Minor features (bridges):
3849 - If bridge users set UpdateBridgesFromAuthority, but the digest
3850 they ask for is a 404 from the bridge authority, they now fall
3851 back to trying the bridge directly.
3852 - Bridges now use begin_dir to publish their server descriptor to
3853 the bridge authority, even when they haven't set TunnelDirConns.
3855 o Minor features (controller):
3856 - When reporting clock skew, and we know that the clock is _at least
3857 as skewed_ as some value, but we don't know the actual value,
3858 report the value as a "minimum skew."
3861 - Update linux-tor-prio.sh script to allow QoS based on the uid of
3862 the Tor process. Patch from Marco Bonetti with tweaks from Mike
3866 - Refuse to start if both ORPort and UseBridges are set. Bugfix
3867 on 0.2.0.x, suggested by Matt Edman.
3868 - Don't stop fetching descriptors when FetchUselessDescriptors is
3869 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
3870 reported by tup and ioerror.
3871 - Better log message on vote from unknown authority.
3872 - Don't log "Launching 0 request for 0 router" message.
3874 o Minor bugfixes (memory leaks):
3875 - Stop leaking memory every time we parse a v3 certificate. Bugfix
3877 - Stop leaking memory every time we load a v3 certificate. Bugfix
3878 on 0.2.0.1-alpha. Fixes bug 536.
3879 - Stop leaking a cached networkstatus on exit. Bugfix on
3881 - Stop leaking voter information every time we free a consensus.
3882 Bugfix on 0.2.0.3-alpha.
3883 - Stop leaking signed data every time we check a voter signature.
3884 Bugfix on 0.2.0.3-alpha.
3885 - Stop leaking a signature every time we fail to parse a consensus or
3886 a vote. Bugfix on 0.2.0.3-alpha.
3887 - Stop leaking v2_download_status_map on shutdown. Bugfix on
3889 - Stop leaking conn->nickname every time we make a connection to a
3890 Tor relay without knowing its expected identity digest (e.g. when
3891 using bridges). Bugfix on 0.2.0.3-alpha.
3893 - Minor bugfixes (portability):
3894 - Run correctly on platforms where rlim_t is larger than unsigned
3895 long, and/or where the real limit for number of open files is
3896 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
3897 particular, these may be needed for OS X 10.5.
3900 Changes in version 0.1.2.18 - 2007-10-28
3901 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
3902 hidden service introduction that were causing huge delays, and a big
3903 bug that was causing some servers to disappear from the network status
3904 lists for a few hours each day.
3906 o Major bugfixes (crashes):
3907 - If a connection is shut down abruptly because of something that
3908 happened inside connection_flushed_some(), do not call
3909 connection_finished_flushing(). Should fix bug 451:
3910 "connection_stop_writing: Assertion conn->write_event failed"
3911 Bugfix on 0.1.2.7-alpha.
3912 - Fix possible segfaults in functions called from
3913 rend_process_relay_cell().
3915 o Major bugfixes (hidden services):
3916 - Hidden services were choosing introduction points uniquely by
3917 hexdigest, but when constructing the hidden service descriptor
3918 they merely wrote the (potentially ambiguous) nickname.
3919 - Clients now use the v2 intro format for hidden service
3920 connections: they specify their chosen rendezvous point by identity
3921 digest rather than by (potentially ambiguous) nickname. These
3922 changes could speed up hidden service connections dramatically.
3924 o Major bugfixes (other):
3925 - Stop publishing a new server descriptor just because we get a
3926 HUP signal. This led (in a roundabout way) to some servers getting
3927 dropped from the networkstatus lists for a few hours each day.
3928 - When looking for a circuit to cannibalize, consider family as well
3929 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
3930 circuit cannibalization).
3931 - When a router wasn't listed in a new networkstatus, we were leaving
3932 the flags for that router alone -- meaning it remained Named,
3933 Running, etc -- even though absence from the networkstatus means
3934 that it shouldn't be considered to exist at all anymore. Now we
3935 clear all the flags for routers that fall out of the networkstatus
3936 consensus. Fixes bug 529.
3939 - Don't try to access (or alter) the state file when running
3940 --list-fingerprint or --verify-config or --hash-password. Resolves
3942 - When generating information telling us how to extend to a given
3943 router, do not try to include the nickname if it is
3944 absent. Resolves bug 467.
3945 - Fix a user-triggerable segfault in expand_filename(). (There isn't
3946 a way to trigger this remotely.)
3947 - When sending a status event to the controller telling it that an
3948 OR address is reachable, set the port correctly. (Previously we
3949 were reporting the dir port.)
3950 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
3951 command. Bugfix on 0.1.2.17.
3952 - When loading bandwidth history, do not believe any information in
3953 the future. Fixes bug 434.
3954 - When loading entry guard information, do not believe any information
3956 - When we have our clock set far in the future and generate an
3957 onion key, then re-set our clock to be correct, we should not stop
3958 the onion key from getting rotated.
3959 - On some platforms, accept() can return a broken address. Detect
3960 this more quietly, and deal accordingly. Fixes bug 483.
3961 - It's not actually an error to find a non-pending entry in the DNS
3962 cache when canceling a pending resolve. Don't log unless stuff
3963 is fishy. Resolves bug 463.
3964 - Don't reset trusted dir server list when we set a configuration
3965 option. Patch from Robert Hogan.
3966 - Don't try to create the datadir when running --verify-config or
3967 --hash-password. Resolves bug 540.
3970 Changes in version 0.2.0.9-alpha - 2007-10-24
3971 This ninth development snapshot switches clients to the new v3 directory
3972 system; allows servers to be listed in the network status even when they
3973 have the same nickname as a registered server; and fixes many other
3974 bugs including a big one that was causing some servers to disappear
3975 from the network status lists for a few hours each day.
3977 o Major features (directory system):
3978 - Clients now download v3 consensus networkstatus documents instead
3979 of v2 networkstatus documents. Clients and caches now base their
3980 opinions about routers on these consensus documents. Clients only
3981 download router descriptors listed in the consensus.
3982 - Authorities now list servers who have the same nickname as
3983 a different named server, but list them with a new flag,
3984 "Unnamed". Now we can list servers that happen to pick the same
3985 nickname as a server that registered two years ago and then
3986 disappeared. Partially implements proposal 122.
3987 - If the consensus lists a router as "Unnamed", the name is assigned
3988 to a different router: do not identify the router by that name.
3989 Partially implements proposal 122.
3990 - Authorities can now come to a consensus on which method to use to
3991 compute the consensus. This gives us forward compatibility.
3994 - Stop publishing a new server descriptor just because we HUP or
3995 when we find our DirPort to be reachable but won't actually publish
3996 it. New descriptors without any real changes are dropped by the
3997 authorities, and can screw up our "publish every 18 hours" schedule.
3999 - When a router wasn't listed in a new networkstatus, we were leaving
4000 the flags for that router alone -- meaning it remained Named,
4001 Running, etc -- even though absence from the networkstatus means
4002 that it shouldn't be considered to exist at all anymore. Now we
4003 clear all the flags for routers that fall out of the networkstatus
4004 consensus. Fixes bug 529; bugfix on 0.1.2.x.
4005 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
4006 extrainfo documents and then discard them immediately for not
4007 matching the latest router. Bugfix on 0.2.0.1-alpha.
4009 o Minor features (v3 directory protocol):
4010 - Allow tor-gencert to generate a new certificate without replacing
4012 - Allow certificates to include an address.
4013 - When we change our directory-cache settings, reschedule all voting
4014 and download operations.
4015 - Reattempt certificate downloads immediately on failure, as long as
4016 we haven't failed a threshold number of times yet.
4017 - Delay retrying consensus downloads while we're downloading
4018 certificates to verify the one we just got. Also, count getting a
4019 consensus that we already have (or one that isn't valid) as a failure,
4020 and count failing to get the certificates after 20 minutes as a
4022 - Build circuits and download descriptors even if our consensus is a
4023 little expired. (This feature will go away once authorities are
4026 o Minor features (router descriptor cache):
4027 - If we find a cached-routers file that's been sitting around for more
4028 than 28 days unmodified, then most likely it's a leftover from
4029 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
4031 - When we (as a cache) download a descriptor because it was listed
4032 in a consensus, remember when the consensus was supposed to expire,
4033 and don't expire the descriptor until then.
4035 o Minor features (performance):
4036 - Call routerlist_remove_old_routers() much less often. This should
4037 speed startup, especially on directory caches.
4038 - Don't try to launch new descriptor downloads quite so often when we
4039 already have enough directory information to build circuits.
4040 - Base64 decoding was actually showing up on our profile when parsing
4041 the initial descriptor file; switch to an in-process all-at-once
4042 implementation that's about 3.5x times faster than calling out to
4045 o Minor features (compilation):
4046 - Detect non-ASCII platforms (if any still exist) and refuse to
4047 build there: some of our code assumes that 'A' is 65 and so on.
4049 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
4050 - Make the "next period" votes into "current period" votes immediately
4051 after publishing the consensus; avoid a heisenbug that made them
4052 stick around indefinitely.
4053 - When we discard a vote as a duplicate, do not report this as
4055 - Treat missing v3 keys or certificates as an error when running as a
4056 v3 directory authority.
4057 - When we're configured to be a v3 authority, but we're only listed
4058 as a non-v3 authority in our DirServer line for ourself, correct
4060 - If an authority doesn't have a qualified hostname, just put
4061 its address in the vote. This fixes the problem where we referred to
4062 "moria on moria:9031."
4063 - Distinguish between detached signatures for the wrong period, and
4064 detached signatures for a divergent vote.
4065 - Fix a small memory leak when computing a consensus.
4066 - When there's no concensus, we were forming a vote every 30
4067 minutes, but writing the "valid-after" line in our vote based
4068 on our configured V3AuthVotingInterval: so unless the intervals
4069 matched up, we immediately rejected our own vote because it didn't
4070 start at the voting interval that caused us to construct a vote.
4072 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
4073 - Delete unverified-consensus when the real consensus is set.
4074 - Consider retrying a consensus networkstatus fetch immediately
4075 after one fails: don't wait 60 seconds to notice.
4076 - When fetching a consensus as a cache, wait until a newer consensus
4077 should exist before trying to replace the current one.
4078 - Use a more forgiving schedule for retrying failed consensus
4079 downloads than for other types.
4081 o Minor bugfixes (other directory issues):
4082 - Correct the implementation of "download votes by digest." Bugfix on
4084 - Authorities no longer send back "400 you're unreachable please fix
4085 it" errors to Tor servers that aren't online all the time. We're
4086 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
4088 o Minor bugfixes (controller):
4089 - Don't reset trusted dir server list when we set a configuration
4090 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
4091 - Respond to INT and TERM SIGNAL commands before we execute the
4092 signal, in case the signal shuts us down. We had a patch in
4093 0.1.2.1-alpha that tried to do this by queueing the response on
4094 the connection's buffer before shutting down, but that really
4095 isn't the same thing at all. Bug located by Matt Edman.
4097 o Minor bugfixes (misc):
4098 - Correctly check for bad options to the "PublishServerDescriptor"
4099 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
4100 - Stop leaking memory on failing case of base32_decode, and make
4101 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
4102 - Don't try to download extrainfo documents when we're trying to
4103 fetch enough directory info to build a circuit: having enough
4104 info should get priority. Bugfix on 0.2.0.x.
4105 - Don't complain that "your server has not managed to confirm that its
4106 ports are reachable" if we haven't been able to build any circuits
4107 yet. Bug found by spending four hours without a v3 consensus. Bugfix
4109 - Detect the reason for failing to mmap a descriptor file we just
4110 wrote, and give a more useful log message. Fixes bug 533. Bugfix
4113 o Code simplifications and refactoring:
4114 - Remove support for the old bw_accounting file: we've been storing
4115 bandwidth accounting information in the state file since
4116 0.1.2.5-alpha. This may result in bandwidth accounting errors
4117 if you try to upgrade from 0.1.1.x or earlier, or if you try to
4118 downgrade to 0.1.1.x or earlier.
4119 - New convenience code to locate a file within the DataDirectory.
4120 - Move non-authority functionality out of dirvote.c.
4121 - Refactor the arguments for router_pick_{directory_|trusteddir}server
4122 so that they all take the same named flags.
4125 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
4126 Unix users an easy way to script their Tor process (e.g. by
4127 adjusting bandwidth based on the time of the day).
4130 Changes in version 0.2.0.8-alpha - 2007-10-12
4131 This eighth development snapshot fixes a crash bug that's been bothering
4132 us since February 2007, lets bridge authorities store a list of bridge
4133 descriptors they've seen, gets v3 directory voting closer to working,
4134 starts caching v3 directory consensus documents on directory mirrors,
4135 and fixes a variety of smaller issues including some minor memory leaks.
4137 o Major features (router descriptor cache):
4138 - Store routers in a file called cached-descriptors instead of in
4139 cached-routers. Initialize cached-descriptors from cached-routers
4140 if the old format is around. The new format allows us to store
4141 annotations along with descriptors.
4142 - Use annotations to record the time we received each descriptor, its
4143 source, and its purpose.
4144 - Disable the SETROUTERPURPOSE controller command: it is now
4146 - Controllers should now specify cache=no or cache=yes when using
4147 the +POSTDESCRIPTOR command.
4148 - Bridge authorities now write bridge descriptors to disk, meaning
4149 we can export them to other programs and begin distributing them
4152 o Major features (directory authorities):
4153 - When a v3 authority is missing votes or signatures, it now tries
4155 - Directory authorities track weighted fractional uptime as well as
4156 weighted mean-time-between failures. WFU is suitable for deciding
4157 whether a node is "usually up", while MTBF is suitable for deciding
4158 whether a node is "likely to stay up." We need both, because
4159 "usually up" is a good requirement for guards, while "likely to
4160 stay up" is a good requirement for long-lived connections.
4162 o Major features (v3 directory system):
4163 - Caches now download v3 network status documents as needed,
4164 and download the descriptors listed in them.
4165 - All hosts now attempt to download and keep fresh v3 authority
4166 certificates, and re-attempt after failures.
4167 - More internal-consistency checks for vote parsing.
4169 o Major bugfixes (crashes):
4170 - If a connection is shut down abruptly because of something that
4171 happened inside connection_flushed_some(), do not call
4172 connection_finished_flushing(). Should fix bug 451. Bugfix on
4175 o Major bugfixes (performance):
4176 - Fix really bad O(n^2) performance when parsing a long list of
4177 routers: Instead of searching the entire list for an "extra-info "
4178 string which usually wasn't there, once for every routerinfo
4179 we read, just scan lines forward until we find one we like.
4181 - When we add data to a write buffer in response to the data on that
4182 write buffer getting low because of a flush, do not consider the
4183 newly added data as a candidate for immediate flushing, but rather
4184 make it wait until the next round of writing. Otherwise, we flush
4185 and refill recursively, and a single greedy TLS connection can
4186 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
4188 o Minor features (v3 authority system):
4189 - Add more ways for tools to download the votes that lead to the
4191 - Send a 503 when low on bandwidth and a vote, consensus, or
4192 certificate is requested.
4193 - If-modified-since is now implemented properly for all kinds of
4194 certificate requests.
4196 o Minor bugfixes (network statuses):
4197 - Tweak the implementation of proposal 109 slightly: allow at most
4198 two Tor servers on the same IP address, except if it's the location
4199 of a directory authority, in which case allow five. Bugfix on
4202 o Minor bugfixes (controller):
4203 - When sending a status event to the controller telling it that an
4204 OR address is reachable, set the port correctly. (Previously we
4205 were reporting the dir port.) Bugfix on 0.1.2.x.
4207 o Minor bugfixes (v3 directory system):
4208 - Fix logic to look up a cert by its signing key digest. Bugfix on
4210 - Only change the reply to a vote to "OK" if it's not already
4211 set. This gets rid of annoying "400 OK" log messages, which may
4212 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
4213 - When we get a valid consensus, recompute the voting schedule.
4214 - Base the valid-after time of a vote on the consensus voting
4215 schedule, not on our preferred schedule.
4216 - Make the return values and messages from signature uploads and
4217 downloads more sensible.
4218 - Fix a memory leak when serving votes and consensus documents, and
4219 another when serving certificates.
4221 o Minor bugfixes (performance):
4222 - Use a slightly simpler string hashing algorithm (copying Python's
4223 instead of Java's) and optimize our digest hashing algorithm to take
4224 advantage of 64-bit platforms and to remove some possibly-costly
4226 - Fix a minor memory leak whenever we parse guards from our state
4227 file. Bugfix on 0.2.0.7-alpha.
4228 - Fix a minor memory leak whenever we write out a file. Bugfix on
4230 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
4231 command. Bugfix on 0.2.0.5-alpha.
4233 o Minor bugfixes (portability):
4234 - On some platforms, accept() can return a broken address. Detect
4235 this more quietly, and deal accordingly. Fixes bug 483.
4236 - Stop calling tor_strlower() on uninitialized memory in some cases.
4237 Bugfix in 0.2.0.7-alpha.
4239 o Minor bugfixes (usability):
4240 - Treat some 403 responses from directory servers as INFO rather than
4241 WARN-severity events.
4242 - It's not actually an error to find a non-pending entry in the DNS
4243 cache when canceling a pending resolve. Don't log unless stuff is
4244 fishy. Resolves bug 463.
4246 o Minor bugfixes (anonymity):
4247 - Never report that we've used more bandwidth than we're willing to
4248 relay: it leaks how much non-relay traffic we're using. Resolves
4250 - When looking for a circuit to cannibalize, consider family as well
4251 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
4252 circuit cannibalization).
4254 o Code simplifications and refactoring:
4255 - Make a bunch of functions static. Remove some dead code.
4256 - Pull out about a third of the really big routerlist.c; put it in a
4257 new module, networkstatus.c.
4258 - Merge the extra fields in local_routerstatus_t back into
4259 routerstatus_t: we used to need one routerstatus_t for each
4260 authority's opinion, plus a local_routerstatus_t for the locally
4261 computed consensus opinion. To save space, we put the locally
4262 modified fields into local_routerstatus_t, and only the common
4263 stuff into routerstatus_t. But once v3 directories are in use,
4264 clients and caches will no longer need to hold authority opinions;
4265 thus, the rationale for keeping the types separate is now gone.
4266 - Make the code used to reschedule and reattempt downloads more
4268 - Turn all 'Are we a directory server/mirror?' logic into a call to
4270 - Remove the code to generate the oldest (v1) directory format.
4271 The code has been disabled since 0.2.0.5-alpha.
4274 Changes in version 0.2.0.7-alpha - 2007-09-21
4275 This seventh development snapshot makes bridges work again, makes bridge
4276 authorities work for the first time, fixes two huge performance flaws
4277 in hidden services, and fixes a variety of minor issues.
4279 o New directory authorities:
4280 - Set up moria1 and tor26 as the first v3 directory authorities. See
4281 doc/spec/dir-spec.txt for details on the new directory design.
4283 o Major bugfixes (crashes):
4284 - Fix possible segfaults in functions called from
4285 rend_process_relay_cell(). Bugfix on 0.1.2.x.
4287 o Major bugfixes (bridges):
4288 - Fix a bug that made servers send a "404 Not found" in response to
4289 attempts to fetch their server descriptor. This caused Tor servers
4290 to take many minutes to establish reachability for their DirPort,
4291 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
4292 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
4293 users configure that and specify a bridge with an identity
4294 fingerprint, now they will lookup the bridge descriptor at the
4295 default bridge authority via a one-hop tunnel, but once circuits
4296 are established they will switch to a three-hop tunnel for later
4297 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
4299 o Major bugfixes (hidden services):
4300 - Hidden services were choosing introduction points uniquely by
4301 hexdigest, but when constructing the hidden service descriptor
4302 they merely wrote the (potentially ambiguous) nickname.
4303 - Clients now use the v2 intro format for hidden service
4304 connections: they specify their chosen rendezvous point by identity
4305 digest rather than by (potentially ambiguous) nickname. Both
4306 are bugfixes on 0.1.2.x, and they could speed up hidden service
4307 connections dramatically. Thanks to Karsten Loesing.
4309 o Minor features (security):
4310 - As a client, do not believe any server that tells us that an
4311 address maps to an internal address space.
4312 - Make it possible to enable HashedControlPassword and
4313 CookieAuthentication at the same time.
4315 o Minor features (guard nodes):
4316 - Tag every guard node in our state file with the version that
4317 we believe added it, or with our own version if we add it. This way,
4318 if a user temporarily runs an old version of Tor and then switches
4319 back to a new one, she doesn't automatically lose her guards.
4321 o Minor features (speed):
4322 - When implementing AES counter mode, update only the portions of the
4323 counter buffer that need to change, and don't keep separate
4324 network-order and host-order counters when they are the same (i.e.,
4325 on big-endian hosts.)
4327 o Minor features (controller):
4328 - Accept LF instead of CRLF on controller, since some software has a
4329 hard time generating real Internet newlines.
4330 - Add GETINFO values for the server status events
4331 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
4335 - Routers no longer include bandwidth-history lines in their
4336 descriptors; this information is already available in extra-info
4337 documents, and including it in router descriptors took up 60%
4338 (!) of compressed router descriptor downloads. Completes
4339 implementation of proposal 104.
4340 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
4341 and TorControl.py, as they use the old v0 controller protocol,
4342 and are obsoleted by TorFlow anyway.
4343 - Drop support for v1 rendezvous descriptors, since we never used
4344 them anyway, and the code has probably rotted by now. Based on
4345 patch from Karsten Loesing.
4346 - On OSX, stop warning the user that kqueue support in libevent is
4347 "experimental", since it seems to have worked fine for ages.
4350 - When generating information telling us how to extend to a given
4351 router, do not try to include the nickname if it is absent. Fixes
4352 bug 467. Bugfix on 0.2.0.3-alpha.
4353 - Fix a user-triggerable (but not remotely-triggerable) segfault
4354 in expand_filename(). Bugfix on 0.1.2.x.
4355 - Fix a memory leak when freeing incomplete requests from DNSPort.
4356 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
4357 - Don't try to access (or alter) the state file when running
4358 --list-fingerprint or --verify-config or --hash-password. (Resolves
4359 bug 499.) Bugfix on 0.1.2.x.
4360 - Servers used to decline to publish their DirPort if their
4361 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
4362 were below a threshold. Now they only look at BandwidthRate and
4363 RelayBandwidthRate. Bugfix on 0.1.2.x.
4364 - Remove an optimization in the AES counter-mode code that assumed
4365 that the counter never exceeded 2^68. When the counter can be set
4366 arbitrarily as an IV (as it is by Karsten's new hidden services
4367 code), this assumption no longer holds. Bugfix on 0.1.2.x.
4368 - Resume listing "AUTHORITY" flag for authorities in network status.
4369 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
4371 o Code simplifications and refactoring:
4372 - Revamp file-writing logic so we don't need to have the entire
4373 contents of a file in memory at once before we write to disk. Tor,
4375 - Turn "descriptor store" into a full-fledged type.
4376 - Move all NT services code into a separate source file.
4377 - Unify all code that computes medians, percentile elements, etc.
4378 - Get rid of a needless malloc when parsing address policies.
4381 Changes in version 0.1.2.17 - 2007-08-30
4382 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
4383 X bundles. Vidalia 0.0.14 makes authentication required for the
4384 ControlPort in the default configuration, which addresses important
4385 security risks. Everybody who uses Vidalia (or another controller)
4388 In addition, this Tor update fixes major load balancing problems with
4389 path selection, which should speed things up a lot once many people
4392 o Major bugfixes (security):
4393 - We removed support for the old (v0) control protocol. It has been
4394 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
4395 become more of a headache than it's worth.
4397 o Major bugfixes (load balancing):
4398 - When choosing nodes for non-guard positions, weight guards
4399 proportionally less, since they already have enough load. Patch
4401 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
4402 will allow fast Tor servers to get more attention.
4403 - When we're upgrading from an old Tor version, forget our current
4404 guards and pick new ones according to the new weightings. These
4405 three load balancing patches could raise effective network capacity
4406 by a factor of four. Thanks to Mike Perry for measurements.
4408 o Major bugfixes (stream expiration):
4409 - Expire not-yet-successful application streams in all cases if
4410 they've been around longer than SocksTimeout. Right now there are
4411 some cases where the stream will live forever, demanding a new
4412 circuit every 15 seconds. Fixes bug 454; reported by lodger.
4414 o Minor features (controller):
4415 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
4416 is valid before any authentication has been received. It tells
4417 a controller what kind of authentication is expected, and what
4418 protocol is spoken. Implements proposal 119.
4420 o Minor bugfixes (performance):
4421 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
4422 greatly speeding up loading cached-routers from disk on startup.
4423 - Disable sentinel-based debugging for buffer code: we squashed all
4424 the bugs that this was supposed to detect a long time ago, and now
4425 its only effect is to change our buffer sizes from nice powers of
4426 two (which platform mallocs tend to like) to values slightly over
4427 powers of two (which make some platform mallocs sad).
4429 o Minor bugfixes (misc):
4430 - If exit bandwidth ever exceeds one third of total bandwidth, then
4431 use the correct formula to weight exit nodes when choosing paths.
4432 Based on patch from Mike Perry.
4433 - Choose perfectly fairly among routers when choosing by bandwidth and
4434 weighting by fraction of bandwidth provided by exits. Previously, we
4435 would choose with only approximate fairness, and correct ourselves
4436 if we ran off the end of the list.
4437 - If we require CookieAuthentication but we fail to write the
4438 cookie file, we would warn but not exit, and end up in a state
4439 where no controller could authenticate. Now we exit.
4440 - If we require CookieAuthentication, stop generating a new cookie
4441 every time we change any piece of our config.
4442 - Refuse to start with certain directory authority keys, and
4443 encourage people using them to stop.
4444 - Terminate multi-line control events properly. Original patch
4446 - Fix a minor memory leak when we fail to find enough suitable
4447 servers to choose a circuit.
4448 - Stop leaking part of the descriptor when we run into a particularly
4449 unparseable piece of it.
4452 Changes in version 0.2.0.6-alpha - 2007-08-26
4453 This sixth development snapshot features a new Vidalia version in the
4454 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
4455 the ControlPort in the default configuration, which addresses important
4458 In addition, this snapshot fixes major load balancing problems
4459 with path selection, which should speed things up a lot once many
4460 people have upgraded. The directory authorities also use a new
4461 mean-time-between-failure approach to tracking which servers are stable,
4462 rather than just looking at the most recent uptime.
4464 o New directory authorities:
4465 - Set up Tonga as the default bridge directory authority.
4468 - Directory authorities now track servers by weighted
4469 mean-times-between-failures. When we have 4 or more days of data,
4470 use measured MTBF rather than declared uptime to decide whether
4471 to call a router Stable. Implements proposal 108.
4473 o Major bugfixes (load balancing):
4474 - When choosing nodes for non-guard positions, weight guards
4475 proportionally less, since they already have enough load. Patch
4477 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
4478 will allow fast Tor servers to get more attention.
4479 - When we're upgrading from an old Tor version, forget our current
4480 guards and pick new ones according to the new weightings. These
4481 three load balancing patches could raise effective network capacity
4482 by a factor of four. Thanks to Mike Perry for measurements.
4484 o Major bugfixes (descriptor parsing):
4485 - Handle unexpected whitespace better in malformed descriptors. Bug
4486 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
4489 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
4490 GETINFO for Torstat to use until it can switch to using extrainfos.
4491 - Optionally (if built with -DEXPORTMALLINFO) export the output
4492 of mallinfo via http, as tor/mallinfo.txt. Only accessible
4496 - Do not intermix bridge routers with controller-added
4497 routers. (Bugfix on 0.2.0.x)
4498 - Do not fail with an assert when accept() returns an unexpected
4499 address family. Addresses but does not wholly fix bug 483. (Bugfix
4501 - Let directory authorities startup even when they can't generate
4502 a descriptor immediately, e.g. because they don't know their
4504 - Stop putting the authentication cookie in a file called "0"
4505 in your working directory if you don't specify anything for the
4506 new CookieAuthFile option. Reported by Matt Edman.
4507 - Make it possible to read the PROTOCOLINFO response in a way that
4508 conforms to our control-spec. Reported by Matt Edman.
4509 - Fix a minor memory leak when we fail to find enough suitable
4510 servers to choose a circuit. Bugfix on 0.1.2.x.
4511 - Stop leaking part of the descriptor when we run into a particularly
4512 unparseable piece of it. Bugfix on 0.1.2.x.
4513 - Unmap the extrainfo cache file on exit.
4516 Changes in version 0.2.0.5-alpha - 2007-08-19
4517 This fifth development snapshot fixes compilation on Windows again;
4518 fixes an obnoxious client-side bug that slowed things down and put
4519 extra load on the network; gets us closer to using the v3 directory
4520 voting scheme; makes it easier for Tor controllers to use cookie-based
4521 authentication; and fixes a variety of other bugs.
4524 - Version 1 directories are no longer generated in full. Instead,
4525 authorities generate and serve "stub" v1 directories that list
4526 no servers. This will stop Tor versions 0.1.0.x and earlier from
4527 working, but (for security reasons) nobody should be running those
4530 o Major bugfixes (compilation, 0.2.0.x):
4531 - Try to fix Win32 compilation again: improve checking for IPv6 types.
4532 - Try to fix MSVC compilation: build correctly on platforms that do
4533 not define s6_addr16 or s6_addr32.
4534 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
4537 o Major bugfixes (stream expiration):
4538 - Expire not-yet-successful application streams in all cases if
4539 they've been around longer than SocksTimeout. Right now there are
4540 some cases where the stream will live forever, demanding a new
4541 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
4544 o Minor features (directory servers):
4545 - When somebody requests a list of statuses or servers, and we have
4546 none of those, return a 404 rather than an empty 200.
4548 o Minor features (directory voting):
4549 - Store v3 consensus status consensuses on disk, and reload them
4552 o Minor features (security):
4553 - Warn about unsafe ControlPort configurations.
4554 - Refuse to start with certain directory authority keys, and
4555 encourage people using them to stop.
4557 o Minor features (controller):
4558 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
4559 is valid before any authentication has been received. It tells
4560 a controller what kind of authentication is expected, and what
4561 protocol is spoken. Implements proposal 119.
4562 - New config option CookieAuthFile to choose a new location for the
4563 cookie authentication file, and config option
4564 CookieAuthFileGroupReadable to make it group-readable.
4566 o Minor features (unit testing):
4567 - Add command-line arguments to unit-test executable so that we can
4568 invoke any chosen test from the command line rather than having
4569 to run the whole test suite at once; and so that we can turn on
4570 logging for the unit tests.
4572 o Minor bugfixes (on 0.1.2.x):
4573 - If we require CookieAuthentication but we fail to write the
4574 cookie file, we would warn but not exit, and end up in a state
4575 where no controller could authenticate. Now we exit.
4576 - If we require CookieAuthentication, stop generating a new cookie
4577 every time we change any piece of our config.
4578 - When loading bandwidth history, do not believe any information in
4579 the future. Fixes bug 434.
4580 - When loading entry guard information, do not believe any information
4582 - When we have our clock set far in the future and generate an
4583 onion key, then re-set our clock to be correct, we should not stop
4584 the onion key from getting rotated.
4585 - Clean up torrc sample config file.
4586 - Do not automatically run configure from autogen.sh. This
4587 non-standard behavior tended to annoy people who have built other
4590 o Minor bugfixes (on 0.2.0.x):
4591 - Fix a bug with AutomapHostsOnResolve that would always cause
4592 the second request to fail. Bug reported by Kate. Bugfix on
4594 - Fix a bug in ADDRMAP controller replies that would sometimes
4595 try to print a NULL. Patch from tup.
4596 - Read v3 directory authority keys from the right location.
4597 - Numerous bugfixes to directory voting code.
4600 Changes in version 0.1.2.16 - 2007-08-01
4601 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
4602 remote attacker in certain situations to rewrite the user's torrc
4603 configuration file. This can completely compromise anonymity of users
4604 in most configurations, including those running the Vidalia bundles,
4605 TorK, etc. Or worse.
4607 o Major security fixes:
4608 - Close immediately after missing authentication on control port;
4609 do not allow multiple authentication attempts.
4612 Changes in version 0.2.0.4-alpha - 2007-08-01
4613 This fourth development snapshot fixes a critical security vulnerability
4614 for most users, specifically those running Vidalia, TorK, etc. Everybody
4615 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
4617 o Major security fixes:
4618 - Close immediately after missing authentication on control port;
4619 do not allow multiple authentication attempts.
4621 o Major bugfixes (compilation):
4622 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
4625 o Minor features (performance):
4626 - Be even more aggressive about releasing RAM from small
4627 empty buffers. Thanks to our free-list code, this shouldn't be too
4628 performance-intensive.
4629 - Disable sentinel-based debugging for buffer code: we squashed all
4630 the bugs that this was supposed to detect a long time ago, and
4631 now its only effect is to change our buffer sizes from nice
4632 powers of two (which platform mallocs tend to like) to values
4633 slightly over powers of two (which make some platform mallocs sad).
4634 - Log malloc statistics from mallinfo() on platforms where it
4638 Changes in version 0.2.0.3-alpha - 2007-07-29
4639 This third development snapshot introduces new experimental
4640 blocking-resistance features and a preliminary version of the v3
4641 directory voting design, and includes many other smaller features
4645 - The first pieces of our "bridge" design for blocking-resistance
4646 are implemented. People can run bridge directory authorities;
4647 people can run bridges; and people can configure their Tor clients
4648 with a set of bridges to use as the first hop into the Tor network.
4649 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
4651 - Create listener connections before we setuid to the configured
4652 User and Group. Now non-Windows users can choose port values
4653 under 1024, start Tor as root, and have Tor bind those ports
4654 before it changes to another UID. (Windows users could already
4656 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
4657 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
4658 on "vserver" accounts. (Patch from coderman.)
4659 - Be even more aggressive about separating local traffic from relayed
4660 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
4662 o Major features (experimental):
4663 - First cut of code for "v3 dir voting": directory authorities will
4664 vote on a common network status document rather than each publishing
4665 their own opinion. This code needs more testing and more corner-case
4666 handling before it's ready for use.
4669 - Directory authorities now call routers Fast if their bandwidth is
4670 at least 100KB/s, and consider their bandwidth adequate to be a
4671 Guard if it is at least 250KB/s, no matter the medians. This fix
4672 complements proposal 107. [Bugfix on 0.1.2.x]
4673 - Directory authorities now never mark more than 3 servers per IP as
4674 Valid and Running. (Implements proposal 109, by Kevin Bauer and
4676 - Minor change to organizationName and commonName generation
4677 procedures in TLS certificates during Tor handshakes, to invalidate
4678 some earlier censorware approaches. This is not a long-term
4679 solution, but applying it will give us a bit of time to look into
4680 the epidemiology of countermeasures as they spread.
4682 o Major bugfixes (directory):
4683 - Rewrite directory tokenization code to never run off the end of
4684 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
4686 o Minor features (controller):
4687 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
4688 match requests to applications. (Patch from Robert Hogan.)
4689 - Report address and port correctly on connections to DNSPort. (Patch
4691 - Add a RESOLVE command to launch hostname lookups. (Original patch
4693 - Add GETINFO status/enough-dir-info to let controllers tell whether
4694 Tor has downloaded sufficient directory information. (Patch
4696 - You can now use the ControlSocket option to tell Tor to listen for
4697 controller connections on Unix domain sockets on systems that
4698 support them. (Patch from Peter Palfrader.)
4699 - STREAM NEW events are generated for DNSPort requests and for
4700 tunneled directory connections. (Patch from Robert Hogan.)
4701 - New "GETINFO address-mappings/*" command to get address mappings
4702 with expiry information. "addr-mappings/*" is now deprecated.
4705 o Minor features (misc):
4706 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
4708 - The tor-gencert tool for v3 directory authorities now creates all
4709 files as readable to the file creator only, and write-protects
4710 the authority identity key.
4711 - When dumping memory usage, list bytes used in buffer memory
4713 - When running with dmalloc, dump more stats on hup and on exit.
4714 - Directory authorities now fail quickly and (relatively) harmlessly
4715 if they generate a network status document that is somehow
4718 o Traffic load balancing improvements:
4719 - If exit bandwidth ever exceeds one third of total bandwidth, then
4720 use the correct formula to weight exit nodes when choosing paths.
4721 (Based on patch from Mike Perry.)
4722 - Choose perfectly fairly among routers when choosing by bandwidth and
4723 weighting by fraction of bandwidth provided by exits. Previously, we
4724 would choose with only approximate fairness, and correct ourselves
4725 if we ran off the end of the list. [Bugfix on 0.1.2.x]
4727 o Performance improvements:
4728 - Be more aggressive with freeing buffer RAM or putting it on the
4730 - Use Critical Sections rather than Mutexes for synchronizing threads
4731 on win32; Mutexes are heavier-weight, and designed for synchronizing
4734 o Deprecated and removed features:
4735 - RedirectExits is now deprecated.
4736 - Stop allowing address masks that do not correspond to bit prefixes.
4737 We have warned about these for a really long time; now it's time
4738 to reject them. (Patch from croup.)
4740 o Minor bugfixes (directory):
4741 - Fix another crash bug related to extra-info caching. (Bug found by
4742 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
4743 - Directories no longer return a "304 not modified" when they don't
4744 have the networkstatus the client asked for. Also fix a memory
4745 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
4746 - We had accidentally labelled 0.1.2.x directory servers as not
4747 suitable for begin_dir requests, and had labelled no directory
4748 servers as suitable for uploading extra-info documents. [Bugfix
4751 o Minor bugfixes (dns):
4752 - Fix a crash when DNSPort is set more than once. (Patch from Robert
4753 Hogan.) [Bugfix on 0.2.0.2-alpha]
4754 - Add DNSPort connections to the global connection list, so that we
4755 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
4757 - Fix a dangling reference that could lead to a crash when DNSPort is
4758 changed or closed (Patch from Robert Hogan.) [Bugfix on
4761 o Minor bugfixes (controller):
4762 - Provide DNS expiry times in GMT, not in local time. For backward
4763 compatibility, ADDRMAP events only provide GMT expiry in an extended
4764 field. "GETINFO address-mappings" always does the right thing.
4765 - Use CRLF line endings properly in NS events.
4766 - Terminate multi-line control events properly. (Original patch
4767 from tup.) [Bugfix on 0.1.2.x-alpha]
4768 - Do not include spaces in SOURCE_ADDR fields in STREAM
4769 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
4772 Changes in version 0.1.2.15 - 2007-07-17
4773 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
4774 problems, fixes compilation on BSD, and fixes a variety of other
4775 bugs. Everybody should upgrade.
4777 o Major bugfixes (compilation):
4778 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
4780 o Major bugfixes (crashes):
4781 - Try even harder not to dereference the first character after
4782 an mmap(). Reported by lodger.
4783 - Fix a crash bug in directory authorities when we re-number the
4784 routerlist while inserting a new router.
4785 - When the cached-routers file is an even multiple of the page size,
4786 don't run off the end and crash. (Fixes bug 455; based on idea
4788 - Fix eventdns.c behavior on Solaris: It is critical to include
4789 orconfig.h _before_ sys/types.h, so that we can get the expected
4790 definition of _FILE_OFFSET_BITS.
4792 o Major bugfixes (security):
4793 - Fix a possible buffer overrun when using BSD natd support. Bug
4795 - When sending destroy cells from a circuit's origin, don't include
4796 the reason for tearing down the circuit. The spec says we didn't,
4797 and now we actually don't. Reported by lodger.
4798 - Keep streamids from different exits on a circuit separate. This
4799 bug may have allowed other routers on a given circuit to inject
4800 cells into streams. Reported by lodger; fixes bug 446.
4801 - If there's a never-before-connected-to guard node in our list,
4802 never choose any guards past it. This way we don't expand our
4803 guard list unless we need to.
4805 o Minor bugfixes (guard nodes):
4806 - Weight guard selection by bandwidth, so that low-bandwidth nodes
4807 don't get overused as guards.
4809 o Minor bugfixes (directory):
4810 - Correctly count the number of authorities that recommend each
4811 version. Previously, we were under-counting by 1.
4812 - Fix a potential crash bug when we load many server descriptors at
4813 once and some of them make others of them obsolete. Fixes bug 458.
4815 o Minor bugfixes (hidden services):
4816 - Stop tearing down the whole circuit when the user asks for a
4817 connection to a port that the hidden service didn't configure.
4820 o Minor bugfixes (misc):
4821 - On Windows, we were preventing other processes from reading
4822 cached-routers while Tor was running. Reported by janbar.
4823 - Fix a possible (but very unlikely) bug in picking routers by
4824 bandwidth. Add a log message to confirm that it is in fact
4825 unlikely. Patch from lodger.
4826 - Backport a couple of memory leak fixes.
4827 - Backport miscellaneous cosmetic bugfixes.
4830 Changes in version 0.2.0.2-alpha - 2007-06-02
4831 o Major bugfixes on 0.2.0.1-alpha:
4832 - Fix an assertion failure related to servers without extra-info digests.
4833 Resolves bugs 441 and 442.
4835 o Minor features (directory):
4836 - Support "If-Modified-Since" when answering HTTP requests for
4837 directories, running-routers documents, and network-status documents.
4838 (There's no need to support it for router descriptors, since those
4839 are downloaded by descriptor digest.)
4841 o Minor build issues:
4842 - Clear up some MIPSPro compiler warnings.
4843 - When building from a tarball on a machine that happens to have SVK
4844 installed, report the micro-revision as whatever version existed
4845 in the tarball, not as "x".
4848 Changes in version 0.2.0.1-alpha - 2007-06-01
4849 This early development snapshot provides new features for people running
4850 Tor as both a client and a server (check out the new RelayBandwidth
4851 config options); lets Tor run as a DNS proxy; and generally moves us
4852 forward on a lot of fronts.
4854 o Major features, server usability:
4855 - New config options RelayBandwidthRate and RelayBandwidthBurst:
4856 a separate set of token buckets for relayed traffic. Right now
4857 relayed traffic is defined as answers to directory requests, and
4858 OR connections that don't have any local circuits on them.
4860 o Major features, client usability:
4861 - A client-side DNS proxy feature to replace the need for
4862 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
4863 for DNS requests on port 9999, use the Tor network to resolve them
4864 anonymously, and send the reply back like a regular DNS server.
4865 The code still only implements a subset of DNS.
4866 - Make PreferTunneledDirConns and TunnelDirConns work even when
4867 we have no cached directory info. This means Tor clients can now
4868 do all of their connections protected by TLS.
4870 o Major features, performance and efficiency:
4871 - Directory authorities accept and serve "extra info" documents for
4872 routers. These documents contain fields from router descriptors
4873 that aren't usually needed, and that use a lot of excess
4874 bandwidth. Once these fields are removed from router descriptors,
4875 the bandwidth savings should be about 60%. [Partially implements
4877 - Servers upload extra-info documents to any authority that accepts
4878 them. Authorities (and caches that have been configured to download
4879 extra-info documents) download them as needed. [Partially implements
4881 - Change the way that Tor buffers data that it is waiting to write.
4882 Instead of queueing data cells in an enormous ring buffer for each
4883 client->OR or OR->OR connection, we now queue cells on a separate
4884 queue for each circuit. This lets us use less slack memory, and
4885 will eventually let us be smarter about prioritizing different kinds
4887 - Use memory pools to allocate cells with better speed and memory
4888 efficiency, especially on platforms where malloc() is inefficient.
4889 - Stop reading on edge connections when their corresponding circuit
4890 buffers are full; start again as the circuits empty out.
4892 o Major features, other:
4893 - Add an HSAuthorityRecordStats option that hidden service authorities
4894 can use to track statistics of overall hidden service usage without
4895 logging information that would be very useful to an attacker.
4896 - Start work implementing multi-level keys for directory authorities:
4897 Add a standalone tool to generate key certificates. (Proposal 103.)
4900 - Directory authorities now call routers Stable if they have an
4901 uptime of at least 30 days, even if that's not the median uptime
4902 in the network. Implements proposal 107, suggested by Kevin Bauer
4905 o Minor fixes (resource management):
4906 - Count the number of open sockets separately from the number
4907 of active connection_t objects. This will let us avoid underusing
4908 our allocated connection limit.
4909 - We no longer use socket pairs to link an edge connection to an
4910 anonymous directory connection or a DirPort test connection.
4911 Instead, we track the link internally and transfer the data
4912 in-process. This saves two sockets per "linked" connection (at the
4913 client and at the server), and avoids the nasty Windows socketpair()
4915 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
4916 for every single inactive connection_t. Free items from the
4917 4k/16k-buffer free lists when they haven't been used for a while.
4919 o Minor features (build):
4920 - Make autoconf search for libevent, openssl, and zlib consistently.
4921 - Update deprecated macros in configure.in.
4922 - When warning about missing headers, tell the user to let us
4923 know if the compile succeeds anyway, so we can downgrade the
4925 - Include the current subversion revision as part of the version
4926 string: either fetch it directly if we're in an SVN checkout, do
4927 some magic to guess it if we're in an SVK checkout, or use
4928 the last-detected version if we're building from a .tar.gz.
4929 Use this version consistently in log messages.
4931 o Minor features (logging):
4932 - Always prepend "Bug: " to any log message about a bug.
4933 - Put a platform string (e.g. "Linux i686") in the startup log
4934 message, so when people paste just their logs, we know if it's
4935 OpenBSD or Windows or what.
4936 - When logging memory usage, break down memory used in buffers by
4939 o Minor features (directory system):
4940 - New config option V2AuthoritativeDirectory that all directory
4941 authorities should set. This will let future authorities choose
4942 not to serve V2 directory information.
4943 - Directory authorities allow multiple router descriptors and/or extra
4944 info documents to be uploaded in a single go. This will make
4945 implementing proposal 104 simpler.
4947 o Minor features (controller):
4948 - Add a new config option __DisablePredictedCircuits designed for
4949 use by the controller, when we don't want Tor to build any circuits
4951 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
4952 so we can exit from the middle of the circuit.
4953 - Implement "getinfo status/circuit-established".
4954 - Implement "getinfo status/version/..." so a controller can tell
4955 whether the current version is recommended, and whether any versions
4956 are good, and how many authorities agree. (Patch from shibz.)
4958 o Minor features (hidden services):
4959 - Allow multiple HiddenServicePort directives with the same virtual
4960 port; when they occur, the user is sent round-robin to one
4961 of the target ports chosen at random. Partially fixes bug 393 by
4962 adding limited ad-hoc round-robining.
4964 o Minor features (other):
4966 - Add a new AutomapHostsOnResolve option: when it is enabled, any
4967 resolve request for hosts matching a given pattern causes Tor to
4968 generate an internal virtual address mapping for that host. This
4969 allows DNSPort to work sensibly with hidden service users. By
4970 default, .exit and .onion addresses are remapped; the list of
4971 patterns can be reconfigured with AutomapHostsSuffixes.
4972 - Add an "-F" option to tor-resolve to force a resolve for a .onion
4973 address. Thanks to the AutomapHostsOnResolve option, this is no
4974 longer a completely silly thing to do.
4975 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
4976 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
4977 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
4978 minus 1 byte: the actual maximum declared bandwidth.
4981 - Removed support for the old binary "version 0" controller protocol.
4982 This has been deprecated since 0.1.1, and warnings have been issued
4983 since 0.1.2. When we encounter a v0 control message, we now send
4984 back an error and close the connection.
4985 - Remove the old "dns worker" server DNS code: it hasn't been default
4986 since 0.1.2.2-alpha, and all the servers seem to be using the new
4989 o Minor bugfixes (portability):
4990 - Even though Windows is equally happy with / and \ as path separators,
4991 try to use \ consistently on Windows and / consistently on Unix: it
4992 makes the log messages nicer.
4993 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
4994 - Read resolv.conf files correctly on platforms where read() returns
4995 partial results on small file reads.
4997 o Minor bugfixes (directory):
4998 - Correctly enforce that elements of directory objects do not appear
4999 more often than they are allowed to appear.
5000 - When we are reporting the DirServer line we just parsed, we were
5001 logging the second stanza of the key fingerprint, not the first.
5003 o Minor bugfixes (logging):
5004 - When we hit an EOF on a log (probably because we're shutting down),
5005 don't try to remove the log from the list: just mark it as
5006 unusable. (Bulletproofs against bug 222.)
5008 o Minor bugfixes (other):
5009 - In the exitlist script, only consider the most recently published
5010 server descriptor for each server. Also, when the user requests
5011 a list of servers that _reject_ connections to a given address,
5012 explicitly exclude the IPs that also have servers that accept
5013 connections to that address. (Resolves bug 405.)
5014 - Stop allowing hibernating servers to be "stable" or "fast".
5015 - On Windows, we were preventing other processes from reading
5016 cached-routers while Tor was running. (Reported by janbar)
5017 - Make the NodeFamilies config option work. (Reported by
5018 lodger -- it has never actually worked, even though we added it
5020 - Check return values from pthread_mutex functions.
5021 - Don't save non-general-purpose router descriptors to the disk cache,
5022 because we have no way of remembering what their purpose was when
5024 - Add even more asserts to hunt down bug 417.
5025 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
5026 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
5027 Add a log message to confirm that it is in fact unlikely.
5029 o Minor bugfixes (controller):
5030 - Make 'getinfo fingerprint' return a 551 error if we're not a
5031 server, so we match what the control spec claims we do. Reported
5033 - Fix a typo in an error message when extendcircuit fails that
5034 caused us to not follow the \r\n-based delimiter protocol. Reported
5037 o Code simplifications and refactoring:
5038 - Stop passing around circuit_t and crypt_path_t pointers that are
5039 implicit in other procedure arguments.
5040 - Drop the old code to choke directory connections when the
5041 corresponding OR connections got full: thanks to the cell queue
5042 feature, OR conns don't get full any more.
5043 - Make dns_resolve() handle attaching connections to circuits
5044 properly, so the caller doesn't have to.
5045 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
5046 - Keep the connection array as a dynamic smartlist_t, rather than as
5047 a fixed-sized array. This is important, as the number of connections
5048 is becoming increasingly decoupled from the number of sockets.
5051 Changes in version 0.1.2.14 - 2007-05-25
5052 Tor 0.1.2.14 changes the addresses of two directory authorities (this
5053 change especially affects those who serve or use hidden services),
5054 and fixes several other crash- and security-related bugs.
5056 o Directory authority changes:
5057 - Two directory authorities (moria1 and moria2) just moved to new
5058 IP addresses. This change will particularly affect those who serve
5059 or use hidden services.
5061 o Major bugfixes (crashes):
5062 - If a directory server runs out of space in the connection table
5063 as it's processing a begin_dir request, it will free the exit stream
5064 but leave it attached to the circuit, leading to unpredictable
5065 behavior. (Reported by seeess, fixes bug 425.)
5066 - Fix a bug in dirserv_remove_invalid() that would cause authorities
5067 to corrupt memory under some really unlikely scenarios.
5068 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
5069 - Avoid segfaults when reading from mmaped descriptor file. (Reported
5072 o Major bugfixes (security):
5073 - When choosing an entry guard for a circuit, avoid using guards
5074 that are in the same family as the chosen exit -- not just guards
5075 that are exactly the chosen exit. (Reported by lodger.)
5077 o Major bugfixes (resource management):
5078 - If a directory authority is down, skip it when deciding where to get
5079 networkstatus objects or descriptors. Otherwise we keep asking
5080 every 10 seconds forever. Fixes bug 384.
5081 - Count it as a failure if we fetch a valid network-status but we
5082 don't want to keep it. Otherwise we'll keep fetching it and keep
5083 not wanting to keep it. Fixes part of bug 422.
5084 - If all of our dirservers have given us bad or no networkstatuses
5085 lately, then stop hammering them once per minute even when we
5086 think they're failed. Fixes another part of bug 422.
5089 - Actually set the purpose correctly for descriptors inserted with
5091 - When we have k non-v2 authorities in our DirServer config,
5092 we ignored the last k authorities in the list when updating our
5094 - Correctly back-off from requesting router descriptors that we are
5095 having a hard time downloading.
5096 - Read resolv.conf files correctly on platforms where read() returns
5097 partial results on small file reads.
5098 - Don't rebuild the entire router store every time we get 32K of
5099 routers: rebuild it when the journal gets very large, or when
5100 the gaps in the store get very large.
5103 - When routers publish SVN revisions in their router descriptors,
5104 authorities now include those versions correctly in networkstatus
5106 - Warn when using a version of libevent before 1.3b to run a server on
5107 OSX or BSD: these versions interact badly with userspace threads.
5110 Changes in version 0.1.2.13 - 2007-04-24
5111 This release features some major anonymity fixes, such as safer path
5112 selection; better client performance; faster bootstrapping, better
5113 address detection, and better DNS support for servers; write limiting as
5114 well as read limiting to make servers easier to run; and a huge pile of
5115 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
5117 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
5118 of the Freenode IRC network, remembering his patience and vision for
5119 free speech on the Internet.
5122 - Fix a memory leak when we ask for "all" networkstatuses and we
5123 get one we don't recognize.
5124 - Add more asserts to hunt down bug 417.
5125 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
5128 Changes in version 0.1.2.12-rc - 2007-03-16
5130 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
5131 directory information requested inside Tor connections (i.e. via
5132 begin_dir cells). It only triggered when the same connection was
5133 serving other data at the same time. Reported by seeess.
5136 - When creating a circuit via the controller, send a 'launched'
5137 event when we're done, so we follow the spec better.
5140 Changes in version 0.1.2.11-rc - 2007-03-15
5141 o Minor bugfixes (controller), reported by daejees:
5142 - Correct the control spec to match how the code actually responds
5143 to 'getinfo addr-mappings/*'.
5144 - The control spec described a GUARDS event, but the code
5145 implemented a GUARD event. Standardize on GUARD, but let people
5149 Changes in version 0.1.2.10-rc - 2007-03-07
5150 o Major bugfixes (Windows):
5151 - Do not load the NT services library functions (which may not exist)
5152 just to detect if we're a service trying to shut down. Now we run
5153 on Win98 and friends again.
5155 o Minor bugfixes (other):
5156 - Clarify a couple of log messages.
5157 - Fix a misleading socks5 error number.
5160 Changes in version 0.1.2.9-rc - 2007-03-02
5161 o Major bugfixes (Windows):
5162 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
5163 of the usual GCC "%llu". This prevents a bug when saving 64-bit
5164 int configuration values: the high-order 32 bits would get
5165 truncated. In particular, we were being bitten by the default
5166 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
5167 and maybe also bug 397.)
5169 o Minor bugfixes (performance):
5170 - Use OpenSSL's AES implementation on platforms where it's faster.
5171 This could save us as much as 10% CPU usage.
5173 o Minor bugfixes (server):
5174 - Do not rotate onion key immediately after setting it for the first
5177 o Minor bugfixes (directory authorities):
5178 - Stop calling servers that have been hibernating for a long time
5179 "stable". Also, stop letting hibernating or obsolete servers affect
5180 uptime and bandwidth cutoffs.
5181 - Stop listing hibernating servers in the v1 directory.
5183 o Minor bugfixes (hidden services):
5184 - Upload hidden service descriptors slightly less often, to reduce
5185 load on authorities.
5187 o Minor bugfixes (other):
5188 - Fix an assert that could trigger if a controller quickly set then
5189 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
5190 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
5192 - Fix a potential race condition in the rpm installer. Found by
5194 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
5195 of 2 as indicating that the server is completely bad; it sometimes
5196 means that the server is just bad for the request in question. (may fix
5197 the last of bug 326.)
5198 - Disable encrypted directory connections when we don't have a server
5199 descriptor for the destination. We'll get this working again in
5203 Changes in version 0.1.2.8-beta - 2007-02-26
5204 o Major bugfixes (crashes):
5205 - Stop crashing when the controller asks us to resetconf more than
5206 one config option at once. (Vidalia 0.0.11 does this.)
5207 - Fix a crash that happened on Win98 when we're given command-line
5208 arguments: don't try to load NT service functions from advapi32.dll
5209 except when we need them. (Bug introduced in 0.1.2.7-alpha;
5211 - Fix a longstanding obscure crash bug that could occur when
5212 we run out of DNS worker processes. (Resolves bug 390.)
5214 o Major bugfixes (hidden services):
5215 - Correctly detect whether hidden service descriptor downloads are
5216 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
5218 o Major bugfixes (accounting):
5219 - When we start during an accounting interval before it's time to wake
5220 up, remember to wake up at the correct time. (May fix bug 342.)
5222 o Minor bugfixes (controller):
5223 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
5224 clear the corresponding on_circuit variable, and remember later
5225 that we don't need to send a redundant CLOSED event. (Resolves part
5227 - Report events where a resolve succeeded or where we got a socks
5228 protocol error correctly, rather than calling both of them
5230 - Change reported stream target addresses to IP consistently when
5231 we finally get the IP from an exit node.
5232 - Send log messages to the controller even if they happen to be very
5235 o Minor bugfixes (other):
5236 - Display correct results when reporting which versions are
5237 recommended, and how recommended they are. (Resolves bug 383.)
5238 - Improve our estimates for directory bandwidth to be less random:
5239 guess that an unrecognized directory will have the average bandwidth
5240 from all known directories, not that it will have the average
5241 bandwidth from those directories earlier than it on the list.
5242 - If we start a server with ClientOnly 1, then set ClientOnly to 0
5243 and hup, stop triggering an assert based on an empty onion_key.
5244 - On platforms with no working mmap() equivalent, don't warn the
5245 user when cached-routers doesn't exist.
5246 - Warn the user when mmap() [or its equivalent] fails for some reason
5247 other than file-not-found.
5248 - Don't warn the user when cached-routers.new doesn't exist: that's
5249 perfectly fine when starting up for the first time.
5250 - When EntryNodes are configured, rebuild the guard list to contain,
5251 in order: the EntryNodes that were guards before; the rest of the
5252 EntryNodes; the nodes that were guards before.
5253 - Mask out all signals in sub-threads; only the libevent signal
5254 handler should be processing them. This should prevent some crashes
5255 on some machines using pthreads. (Patch from coderman.)
5256 - Fix switched arguments on memset in the implementation of
5257 tor_munmap() for systems with no mmap() call.
5258 - When Tor receives a router descriptor that it asked for, but
5259 no longer wants (because it has received fresh networkstatuses
5260 in the meantime), do not warn the user. Cache the descriptor if
5261 we're a cache; drop it if we aren't.
5262 - Make earlier entry guards _really_ get retried when the network
5264 - On a malformed DNS reply, always give an error to the corresponding
5266 - Build with recent libevents on platforms that do not define the
5267 nonstandard types "u_int8_t" and friends.
5269 o Minor features (controller):
5270 - Warn the user when an application uses the obsolete binary v0
5271 control protocol. We're planning to remove support for it during
5272 the next development series, so it's good to give people some
5274 - Add STREAM_BW events to report per-entry-stream bandwidth
5275 use. (Patch from Robert Hogan.)
5276 - Rate-limit SIGNEWNYM signals in response to controllers that
5277 impolitely generate them for every single stream. (Patch from
5278 mwenge; closes bug 394.)
5279 - Make REMAP stream events have a SOURCE (cache or exit), and
5280 make them generated in every case where we get a successful
5281 connected or resolved cell.
5283 o Minor bugfixes (performance):
5284 - Call router_have_min_dir_info half as often. (This is showing up in
5285 some profiles, but not others.)
5286 - When using GCC, make log_debug never get called at all, and its
5287 arguments never get evaluated, when no debug logs are configured.
5288 (This is showing up in some profiles, but not others.)
5291 - Remove some never-implemented options. Mark PathlenCoinWeight as
5293 - Implement proposal 106: Stop requiring clients to have well-formed
5294 certificates; stop checking nicknames in certificates. (Clients
5295 have certificates so that they can look like Tor servers, but in
5296 the future we might want to allow them to look like regular TLS
5297 clients instead. Nicknames in certificates serve no purpose other
5298 than making our protocol easier to recognize on the wire.)
5299 - Revise messages on handshake failure again to be even more clear about
5300 which are incoming connections and which are outgoing.
5301 - Discard any v1 directory info that's over 1 month old (for
5302 directories) or over 1 week old (for running-routers lists).
5303 - Do not warn when individual nodes in the configuration's EntryNodes,
5304 ExitNodes, etc are down: warn only when all possible nodes
5305 are down. (Fixes bug 348.)
5306 - Always remove expired routers and networkstatus docs before checking
5307 whether we have enough information to build circuits. (Fixes
5309 - Put a lower-bound on MaxAdvertisedBandwidth.
5312 Changes in version 0.1.2.7-alpha - 2007-02-06
5313 o Major bugfixes (rate limiting):
5314 - Servers decline directory requests much more aggressively when
5315 they're low on bandwidth. Otherwise they end up queueing more and
5316 more directory responses, which can't be good for latency.
5317 - But never refuse directory requests from local addresses.
5318 - Fix a memory leak when sending a 503 response for a networkstatus
5320 - Be willing to read or write on local connections (e.g. controller
5321 connections) even when the global rate limiting buckets are empty.
5322 - If our system clock jumps back in time, don't publish a negative
5323 uptime in the descriptor. Also, don't let the global rate limiting
5324 buckets go absurdly negative.
5325 - Flush local controller connection buffers periodically as we're
5326 writing to them, so we avoid queueing 4+ megabytes of data before
5329 o Major bugfixes (NT services):
5330 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
5331 command-line flag so that admins can override the default by saying
5332 "tor --service install --user "SomeUser"". This will not affect
5333 existing installed services. Also, warn the user that the service
5334 will look for its configuration file in the service user's
5335 %appdata% directory. (We can't do the 'hardwire the user's appdata
5336 directory' trick any more, since we may not have read access to that
5339 o Major bugfixes (other):
5340 - Previously, we would cache up to 16 old networkstatus documents
5341 indefinitely, if they came from nontrusted authorities. Now we
5342 discard them if they are more than 10 days old.
5343 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
5345 - Detect and reject malformed DNS responses containing circular
5347 - If exits are rare enough that we're not marking exits as guards,
5348 ignore exit bandwidth when we're deciding the required bandwidth
5350 - When we're handling a directory connection tunneled over Tor,
5351 don't fill up internal memory buffers with all the data we want
5352 to tunnel; instead, only add it if the OR connection that will
5353 eventually receive it has some room for it. (This can lead to
5354 slowdowns in tunneled dir connections; a better solution will have
5357 o Minor bugfixes (dns):
5358 - Add some defensive programming to eventdns.c in an attempt to catch
5359 possible memory-stomping bugs.
5360 - Detect and reject DNS replies containing IPv4 or IPv6 records with
5361 an incorrect number of bytes. (Previously, we would ignore the
5363 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
5364 in the correct order, and doesn't crash.
5365 - Free memory held in recently-completed DNS lookup attempts on exit.
5366 This was not a memory leak, but may have been hiding memory leaks.
5367 - Handle TTL values correctly on reverse DNS lookups.
5368 - Treat failure to parse resolv.conf as an error.
5370 o Minor bugfixes (other):
5371 - Fix crash with "tor --list-fingerprint" (reported by seeess).
5372 - When computing clock skew from directory HTTP headers, consider what
5373 time it was when we finished asking for the directory, not what
5375 - Expire socks connections if they spend too long waiting for the
5376 handshake to finish. Previously we would let them sit around for
5377 days, if the connecting application didn't close them either.
5378 - And if the socks handshake hasn't started, don't send a
5379 "DNS resolve socks failed" handshake reply; just close it.
5380 - Stop using C functions that OpenBSD's linker doesn't like.
5381 - Don't launch requests for descriptors unless we have networkstatuses
5382 from at least half of the authorities. This delays the first
5383 download slightly under pathological circumstances, but can prevent
5384 us from downloading a bunch of descriptors we don't need.
5385 - Do not log IPs with TLS failures for incoming TLS
5386 connections. (Fixes bug 382.)
5387 - If the user asks to use invalid exit nodes, be willing to use
5389 - Stop using the reserved ac_cv namespace in our configure script.
5390 - Call stat() slightly less often; use fstat() when possible.
5391 - Refactor the way we handle pending circuits when an OR connection
5392 completes or fails, in an attempt to fix a rare crash bug.
5393 - Only rewrite a conn's address based on X-Forwarded-For: headers
5394 if it's a parseable public IP address; and stop adding extra quotes
5395 to the resulting address.
5398 - Weight directory requests by advertised bandwidth. Now we can
5399 let servers enable write limiting but still allow most clients to
5400 succeed at their directory requests. (We still ignore weights when
5401 choosing a directory authority; I hope this is a feature.)
5404 - Create a new file ReleaseNotes which was the old ChangeLog. The
5405 new ChangeLog file now includes the summaries for all development
5407 - Check for addresses with invalid characters at the exit as well
5408 as at the client, and warn less verbosely when they fail. You can
5409 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
5410 - Adapt a patch from goodell to let the contrib/exitlist script
5411 take arguments rather than require direct editing.
5412 - Inform the server operator when we decide not to advertise a
5413 DirPort due to AccountingMax enabled or a low BandwidthRate. It
5414 was confusing Zax, so now we're hopefully more helpful.
5415 - Bring us one step closer to being able to establish an encrypted
5416 directory tunnel without knowing a descriptor first. Still not
5417 ready yet. As part of the change, now assume we can use a
5418 create_fast cell if we don't know anything about a router.
5419 - Allow exit nodes to use nameservers running on ports other than 53.
5420 - Servers now cache reverse DNS replies.
5421 - Add an --ignore-missing-torrc command-line option so that we can
5422 get the "use sensible defaults if the configuration file doesn't
5423 exist" behavior even when specifying a torrc location on the command
5426 o Minor features (controller):
5427 - Track reasons for OR connection failure; make these reasons
5428 available via the controller interface. (Patch from Mike Perry.)
5429 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
5430 can learn when clients are sending malformed hostnames to Tor.
5431 - Clean up documentation for controller status events.
5432 - Add a REMAP status to stream events to note that a stream's
5433 address has changed because of a cached address or a MapAddress
5437 Changes in version 0.1.2.6-alpha - 2007-01-09
5439 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
5440 connection handles more than 4 gigs in either direction, we crash.
5441 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
5442 advertised exit node, somebody might try to exit from us when
5443 we're bootstrapping and before we've built our descriptor yet.
5444 Refuse the connection rather than crashing.
5447 - Warn if we (as a server) find that we've resolved an address that we
5448 weren't planning to resolve.
5449 - Warn that using select() on any libevent version before 1.1 will be
5450 unnecessarily slow (even for select()).
5451 - Flush ERR-level controller status events just like we currently
5452 flush ERR-level log events, so that a Tor shutdown doesn't prevent
5453 the controller from learning about current events.
5455 o Minor features (more controller status events):
5456 - Implement EXTERNAL_ADDRESS server status event so controllers can
5457 learn when our address changes.
5458 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
5459 can learn when directories reject our descriptor.
5460 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
5461 can learn when a client application is speaking a non-socks protocol
5463 - Implement DANGEROUS_SOCKS client status event so controllers
5464 can learn when a client application is leaking DNS addresses.
5465 - Implement BUG general status event so controllers can learn when
5466 Tor is unhappy about its internal invariants.
5467 - Implement CLOCK_SKEW general status event so controllers can learn
5468 when Tor thinks the system clock is set incorrectly.
5469 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
5470 server status events so controllers can learn when their descriptors
5471 are accepted by a directory.
5472 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
5473 server status events so controllers can learn about Tor's progress in
5474 deciding whether it's reachable from the outside.
5475 - Implement BAD_LIBEVENT general status event so controllers can learn
5476 when we have a version/method combination in libevent that needs to
5478 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
5479 and DNS_USELESS server status events so controllers can learn
5480 about changes to DNS server status.
5482 o Minor features (directory):
5483 - Authorities no longer recommend exits as guards if this would shift
5484 too much load to the exit nodes.
5487 Changes in version 0.1.2.5-alpha - 2007-01-06
5489 - Enable write limiting as well as read limiting. Now we sacrifice
5490 capacity if we're pushing out lots of directory traffic, rather
5491 than overrunning the user's intended bandwidth limits.
5492 - Include TLS overhead when counting bandwidth usage; previously, we
5493 would count only the bytes sent over TLS, but not the bytes used
5495 - Support running the Tor service with a torrc not in the same
5496 directory as tor.exe and default to using the torrc located in
5497 the %appdata%\Tor\ of the user who installed the service. Patch
5499 - Servers now check for the case when common DNS requests are going to
5500 wildcarded addresses (i.e. all getting the same answer), and change
5501 their exit policy to reject *:* if it's happening.
5502 - Implement BEGIN_DIR cells, so we can connect to the directory
5503 server via TLS to do encrypted directory requests rather than
5504 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
5505 config options if you like.
5507 o Minor features (config and docs):
5508 - Start using the state file to store bandwidth accounting data:
5509 the bw_accounting file is now obsolete. We'll keep generating it
5510 for a while for people who are still using 0.1.2.4-alpha.
5511 - Try to batch changes to the state file so that we do as few
5512 disk writes as possible while still storing important things in
5514 - The state file and the bw_accounting file get saved less often when
5515 the AvoidDiskWrites config option is set.
5516 - Make PIDFile work on Windows (untested).
5517 - Add internal descriptions for a bunch of configuration options:
5518 accessible via controller interface and in comments in saved
5520 - Reject *:563 (NNTPS) in the default exit policy. We already reject
5521 NNTP by default, so this seems like a sensible addition.
5522 - Clients now reject hostnames with invalid characters. This should
5523 avoid some inadvertent info leaks. Add an option
5524 AllowNonRFC953Hostnames to disable this behavior, in case somebody
5525 is running a private network with hosts called @, !, and #.
5526 - Add a maintainer script to tell us which options are missing
5527 documentation: "make check-docs".
5528 - Add a new address-spec.txt document to describe our special-case
5529 addresses: .exit, .onion, and .noconnnect.
5531 o Minor features (DNS):
5532 - Ongoing work on eventdns infrastructure: now it has dns server
5533 and ipv6 support. One day Tor will make use of it.
5534 - Add client-side caching for reverse DNS lookups.
5535 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
5536 - When we change nameservers or IP addresses, reset and re-launch
5537 our tests for DNS hijacking.
5539 o Minor features (directory):
5540 - Authorities now specify server versions in networkstatus. This adds
5541 about 2% to the size of compressed networkstatus docs, and allows
5542 clients to tell which servers support BEGIN_DIR and which don't.
5543 The implementation is forward-compatible with a proposed future
5544 protocol version scheme not tied to Tor versions.
5545 - DirServer configuration lines now have an orport= option so
5546 clients can open encrypted tunnels to the authorities without
5547 having downloaded their descriptors yet. Enabled for moria1,
5548 moria2, tor26, and lefkada now in the default configuration.
5549 - Directory servers are more willing to send a 503 "busy" if they
5550 are near their write limit, especially for v1 directory requests.
5551 Now they can use their limited bandwidth for actual Tor traffic.
5552 - Clients track responses with status 503 from dirservers. After a
5553 dirserver has given us a 503, we try not to use it until an hour has
5554 gone by, or until we have no dirservers that haven't given us a 503.
5555 - When we get a 503 from a directory, and we're not a server, we don't
5556 count the failure against the total number of failures allowed
5557 for the thing we're trying to download.
5558 - Report X-Your-Address-Is correctly from tunneled directory
5559 connections; don't report X-Your-Address-Is when it's an internal
5560 address; and never believe reported remote addresses when they're
5562 - Protect against an unlikely DoS attack on directory servers.
5563 - Add a BadDirectory flag to network status docs so that authorities
5564 can (eventually) tell clients about caches they believe to be
5567 o Minor features (controller):
5568 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
5569 - Reimplement GETINFO so that info/names stays in sync with the
5571 - Implement "GETINFO fingerprint".
5572 - Implement "SETEVENTS GUARD" so controllers can get updates on
5573 entry guard status as it changes.
5575 o Minor features (clean up obsolete pieces):
5576 - Remove some options that have been deprecated since at least
5577 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
5578 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
5580 - We no longer look for identity and onion keys in "identity.key" and
5581 "onion.key" -- these were replaced by secret_id_key and
5582 secret_onion_key in 0.0.8pre1.
5583 - We no longer require unrecognized directory entries to be
5586 o Major bugfixes (security):
5587 - Stop sending the HttpProxyAuthenticator string to directory
5588 servers when directory connections are tunnelled through Tor.
5589 - Clients no longer store bandwidth history in the state file.
5590 - Do not log introduction points for hidden services if SafeLogging
5592 - When generating bandwidth history, round down to the nearest
5593 1k. When storing accounting data, round up to the nearest 1k.
5594 - When we're running as a server, remember when we last rotated onion
5595 keys, so that we will rotate keys once they're a week old even if
5596 we never stay up for a week ourselves.
5598 o Major bugfixes (other):
5599 - Fix a longstanding bug in eventdns that prevented the count of
5600 timed-out resolves from ever being reset. This bug caused us to
5601 give up on a nameserver the third time it timed out, and try it
5602 10 seconds later... and to give up on it every time it timed out
5604 - Take out the '5 second' timeout from the connection retry
5605 schedule. Now the first connect attempt will wait a full 10
5606 seconds before switching to a new circuit. Perhaps this will help
5607 a lot. Based on observations from Mike Perry.
5608 - Fix a bug on the Windows implementation of tor_mmap_file() that
5609 would prevent the cached-routers file from ever loading. Reported
5613 - Fix an assert failure when a directory authority sets
5614 AuthDirRejectUnlisted and then receives a descriptor from an
5615 unlisted router. Reported by seeess.
5616 - Avoid a double-free when parsing malformed DirServer lines.
5617 - Fix a bug when a BSD-style PF socket is first used. Patch from
5619 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
5620 to resolve an address at a given exit node even when they ask for
5622 - Servers no longer ever list themselves in their "family" line,
5623 even if configured to do so. This makes it easier to configure
5624 family lists conveniently.
5625 - When running as a server, don't fall back to 127.0.0.1 when no
5626 nameservers are configured in /etc/resolv.conf; instead, make the
5627 user fix resolv.conf or specify nameservers explicitly. (Resolves
5629 - Stop accepting certain malformed ports in configured exit policies.
5630 - Don't re-write the fingerprint file every restart, unless it has
5632 - Stop warning when a single nameserver fails: only warn when _all_ of
5633 our nameservers have failed. Also, when we only have one nameserver,
5634 raise the threshold for deciding that the nameserver is dead.
5635 - Directory authorities now only decide that routers are reachable
5636 if their identity keys are as expected.
5637 - When the user uses bad syntax in the Log config line, stop
5638 suggesting other bad syntax as a replacement.
5639 - Correctly detect ipv6 DNS capability on OpenBSD.
5641 o Minor bugfixes (controller):
5642 - Report the circuit number correctly in STREAM CLOSED events. Bug
5643 reported by Mike Perry.
5644 - Do not report bizarre values for results of accounting GETINFOs
5645 when the last second's write or read exceeds the allotted bandwidth.
5646 - Report "unrecognized key" rather than an empty string when the
5647 controller tries to fetch a networkstatus that doesn't exist.
5650 Changes in version 0.1.1.26 - 2006-12-14
5651 o Security bugfixes:
5652 - Stop sending the HttpProxyAuthenticator string to directory
5653 servers when directory connections are tunnelled through Tor.
5654 - Clients no longer store bandwidth history in the state file.
5655 - Do not log introduction points for hidden services if SafeLogging
5659 - Fix an assert failure when a directory authority sets
5660 AuthDirRejectUnlisted and then receives a descriptor from an
5661 unlisted router (reported by seeess).
5664 Changes in version 0.1.2.4-alpha - 2006-12-03
5666 - Add support for using natd; this allows FreeBSDs earlier than
5667 5.1.2 to have ipfw send connections through Tor without using
5668 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
5671 - Make all connections to addresses of the form ".noconnect"
5672 immediately get closed. This lets application/controller combos
5673 successfully test whether they're talking to the same Tor by
5674 watching for STREAM events.
5675 - Make cross.sh cross-compilation script work even when autogen.sh
5676 hasn't been run. (Patch from Michael Mohr.)
5677 - Statistics dumped by -USR2 now include a breakdown of public key
5678 operations, for profiling.
5681 - Fix a major leak when directory authorities parse their
5682 approved-routers list, a minor memory leak when we fail to pick
5683 an exit node, and a few rare leaks on errors.
5684 - Handle TransPort connections even when the server sends data before
5685 the client sends data. Previously, the connection would just hang
5686 until the client sent data. (Patch from tup based on patch from
5688 - Avoid assert failure when our cached-routers file is empty on
5692 - Don't log spurious warnings when we see a circuit close reason we
5693 don't recognize; it's probably just from a newer version of Tor.
5694 - Have directory authorities allow larger amounts of drift in uptime
5695 without replacing the server descriptor: previously, a server that
5696 restarted every 30 minutes could have 48 "interesting" descriptors
5698 - Start linking to the Tor specification and Tor reference manual
5699 correctly in the Windows installer.
5700 - Add Vidalia to the OS X uninstaller script, so when we uninstall
5701 Tor/Privoxy we also uninstall Vidalia.
5702 - Resume building on Irix64, and fix a lot of warnings from its
5704 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
5705 when we're running as a client.
5708 Changes in version 0.1.1.25 - 2006-11-04
5710 - When a client asks us to resolve (rather than connect to)
5711 an address, and we have a cached answer, give them the cached
5712 answer. Previously, we would give them no answer at all.
5713 - We were building exactly the wrong circuits when we predict
5714 hidden service requirements, meaning Tor would have to build all
5715 its circuits on demand.
5716 - If none of our live entry guards have a high uptime, but we
5717 require a guard with a high uptime, try adding a new guard before
5718 we give up on the requirement. This patch should make long-lived
5719 connections more stable on average.
5720 - When testing reachability of our DirPort, don't launch new
5721 tests when there's already one in progress -- unreachable
5722 servers were stacking up dozens of testing streams.
5724 o Security bugfixes:
5725 - When the user sends a NEWNYM signal, clear the client-side DNS
5726 cache too. Otherwise we continue to act on previous information.
5729 - Avoid a memory corruption bug when creating a hash table for
5731 - Avoid possibility of controller-triggered crash when misusing
5732 certain commands from a v0 controller on platforms that do not
5733 handle printf("%s",NULL) gracefully.
5734 - Avoid infinite loop on unexpected controller input.
5735 - Don't log spurious warnings when we see a circuit close reason we
5736 don't recognize; it's probably just from a newer version of Tor.
5737 - Add Vidalia to the OS X uninstaller script, so when we uninstall
5738 Tor/Privoxy we also uninstall Vidalia.
5741 Changes in version 0.1.2.3-alpha - 2006-10-29
5743 - Prepare for servers to publish descriptors less often: never
5744 discard a descriptor simply for being too old until either it is
5745 recommended by no authorities, or until we get a better one for
5746 the same router. Make caches consider retaining old recommended
5747 routers for even longer.
5748 - If most authorities set a BadExit flag for a server, clients
5749 don't think of it as a general-purpose exit. Clients only consider
5750 authorities that advertise themselves as listing bad exits.
5751 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
5752 headers for content, so that we can work better in the presence of
5753 caching HTTP proxies.
5754 - Allow authorities to list nodes as bad exits by fingerprint or by
5757 o Minor features, controller:
5758 - Add a REASON field to CIRC events; for backward compatibility, this
5759 field is sent only to controllers that have enabled the extended
5760 event format. Also, add additional reason codes to explain why
5761 a given circuit has been destroyed or truncated. (Patches from
5763 - Add a REMOTE_REASON field to extended CIRC events to tell the
5764 controller about why a remote OR told us to close a circuit.
5765 - Stream events also now have REASON and REMOTE_REASON fields,
5766 working much like those for circuit events.
5767 - There's now a GETINFO ns/... field so that controllers can ask Tor
5768 about the current status of a router.
5769 - A new event type "NS" to inform a controller when our opinion of
5770 a router's status has changed.
5771 - Add a GETINFO events/names and GETINFO features/names so controllers
5772 can tell which events and features are supported.
5773 - A new CLEARDNSCACHE signal to allow controllers to clear the
5774 client-side DNS cache without expiring circuits.
5776 o Security bugfixes:
5777 - When the user sends a NEWNYM signal, clear the client-side DNS
5778 cache too. Otherwise we continue to act on previous information.
5781 - Avoid sending junk to controllers or segfaulting when a controller
5782 uses EVENT_NEW_DESC with verbose nicknames.
5783 - Stop triggering asserts if the controller tries to extend hidden
5784 service circuits (reported by mwenge).
5785 - Avoid infinite loop on unexpected controller input.
5786 - When the controller does a "GETINFO network-status", tell it
5787 about even those routers whose descriptors are very old, and use
5788 long nicknames where appropriate.
5789 - Change NT service functions to be loaded on demand. This lets us
5790 build with MinGW without breaking Tor for Windows 98 users.
5791 - Do DirPort reachability tests less often, since a single test
5792 chews through many circuits before giving up.
5793 - In the hidden service example in torrc.sample, stop recommending
5794 esoteric and discouraged hidden service options.
5795 - When stopping an NT service, wait up to 10 sec for it to actually
5796 stop. (Patch from Matt Edman; resolves bug 295.)
5797 - Fix handling of verbose nicknames with ORCONN controller events:
5798 make them show up exactly when requested, rather than exactly when
5800 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
5801 printing a duplicate "$" in the keys we send (reported by mwenge).
5802 - Correctly set maximum connection limit on Cygwin. (This time
5804 - Try to detect Windows correctly when cross-compiling.
5805 - Detect the size of the routers file correctly even if it is
5806 corrupted (on systems without mmap) or not page-aligned (on systems
5807 with mmap). This bug was harmless.
5808 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
5809 to open a stream fails; now we do in more cases. This should
5810 make clients able to find a good exit faster in some cases, since
5811 unhandleable requests will now get an error rather than timing out.
5812 - Resolve two memory leaks when rebuilding the on-disk router cache
5813 (reported by fookoowa).
5814 - Clean up minor code warnings suggested by the MIPSpro C compiler,
5815 and reported by some Centos users.
5816 - Controller signals now work on non-Unix platforms that don't define
5817 SIGUSR1 and SIGUSR2 the way we expect.
5818 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
5819 values before failing, and always enables eventdns.
5820 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
5821 Try to fix this in configure.in by checking for most functions
5822 before we check for libevent.
5825 Changes in version 0.1.2.2-alpha - 2006-10-07
5827 - Make our async eventdns library on-by-default for Tor servers,
5828 and plan to deprecate the separate dnsworker threads.
5829 - Add server-side support for "reverse" DNS lookups (using PTR
5830 records so clients can determine the canonical hostname for a given
5831 IPv4 address). Only supported by servers using eventdns; servers
5832 now announce in their descriptors whether they support eventdns.
5833 - Specify and implement client-side SOCKS5 interface for reverse DNS
5834 lookups (see doc/socks-extensions.txt).
5835 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
5836 connect to directory servers through Tor. Previously, clients needed
5837 to find Tor exits to make private connections to directory servers.
5838 - Avoid choosing Exit nodes for entry or middle hops when the
5839 total bandwidth available from non-Exit nodes is much higher than
5840 the total bandwidth available from Exit nodes.
5841 - Workaround for name servers (like Earthlink's) that hijack failing
5842 DNS requests and replace the no-such-server answer with a "helpful"
5843 redirect to an advertising-driven search portal. Also work around
5844 DNS hijackers who "helpfully" decline to hijack known-invalid
5845 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
5846 lets you turn it off.
5847 - Send out a burst of long-range padding cells once we've established
5848 that we're reachable. Spread them over 4 circuits, so hopefully
5849 a few will be fast. This exercises our bandwidth and bootstraps
5850 us into the directory more quickly.
5852 o New/improved config options:
5853 - Add new config option "ResolvConf" to let the server operator
5854 choose an alternate resolve.conf file when using eventdns.
5855 - Add an "EnforceDistinctSubnets" option to control our "exclude
5856 servers on the same /16" behavior. It's still on by default; this
5857 is mostly for people who want to operate private test networks with
5858 all the machines on the same subnet.
5859 - If one of our entry guards is on the ExcludeNodes list, or the
5860 directory authorities don't think it's a good guard, treat it as
5861 if it were unlisted: stop using it as a guard, and throw it off
5862 the guards list if it stays that way for a long time.
5863 - Allow directory authorities to be marked separately as authorities
5864 for the v1 directory protocol, the v2 directory protocol, and
5865 as hidden service directories, to make it easier to retire old
5866 authorities. V1 authorities should set "HSAuthoritativeDir 1"
5867 to continue being hidden service authorities too.
5868 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
5870 o Minor features, controller:
5871 - Fix CIRC controller events so that controllers can learn the
5872 identity digests of non-Named servers used in circuit paths.
5873 - Let controllers ask for more useful identifiers for servers. Instead
5874 of learning identity digests for un-Named servers and nicknames
5875 for Named servers, the new identifiers include digest, nickname,
5876 and indication of Named status. Off by default; see control-spec.txt
5877 for more information.
5878 - Add a "getinfo address" controller command so it can display Tor's
5879 best guess to the user.
5880 - New controller event to alert the controller when our server
5881 descriptor has changed.
5882 - Give more meaningful errors on controller authentication failure.
5884 o Minor features, other:
5885 - When asked to resolve a hostname, don't use non-exit servers unless
5886 requested to do so. This allows servers with broken DNS to be
5887 useful to the network.
5888 - Divide eventdns log messages into warn and info messages.
5889 - Reserve the nickname "Unnamed" for routers that can't pick
5890 a hostname: any router can call itself Unnamed; directory
5891 authorities will never allocate Unnamed to any particular router;
5892 clients won't believe that any router is the canonical Unnamed.
5893 - Only include function names in log messages for info/debug messages.
5894 For notice/warn/err, the content of the message should be clear on
5895 its own, and printing the function name only confuses users.
5896 - Avoid some false positives during reachability testing: don't try
5897 to test via a server that's on the same /24 as us.
5898 - If we fail to build a circuit to an intended enclave, and it's
5899 not mandatory that we use that enclave, stop wanting it.
5900 - When eventdns is enabled, allow multithreaded builds on NetBSD and
5901 OpenBSD. (We had previously disabled threads on these platforms
5902 because they didn't have working thread-safe resolver functions.)
5904 o Major bugfixes, anonymity/security:
5905 - If a client asked for a server by name, and there's a named server
5906 in our network-status but we don't have its descriptor yet, we
5907 could return an unnamed server instead.
5908 - Fix NetBSD bug that could allow someone to force uninitialized RAM
5909 to be sent to a server's DNS resolver. This only affects NetBSD
5910 and other platforms that do not bounds-check tolower().
5911 - Reject (most) attempts to use Tor circuits with length one. (If
5912 many people start using Tor as a one-hop proxy, exit nodes become
5913 a more attractive target for compromise.)
5914 - Just because your DirPort is open doesn't mean people should be
5915 able to remotely teach you about hidden service descriptors. Now
5916 only accept rendezvous posts if you've got HSAuthoritativeDir set.
5918 o Major bugfixes, other:
5919 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
5920 - When a client asks the server to resolve (not connect to)
5921 an address, and it has a cached answer, give them the cached answer.
5922 Previously, the server would give them no answer at all.
5923 - Allow really slow clients to not hang up five minutes into their
5924 directory downloads (suggested by Adam J. Richter).
5925 - We were building exactly the wrong circuits when we anticipated
5926 hidden service requirements, meaning Tor would have to build all
5927 its circuits on demand.
5928 - Avoid crashing when we mmap a router cache file of size 0.
5929 - When testing reachability of our DirPort, don't launch new
5930 tests when there's already one in progress -- unreachable
5931 servers were stacking up dozens of testing streams.
5933 o Minor bugfixes, correctness:
5934 - If we're a directory mirror and we ask for "all" network status
5935 documents, we would discard status documents from authorities
5937 - Avoid a memory corruption bug when creating a hash table for
5939 - Avoid controller-triggered crash when misusing certain commands
5940 from a v0 controller on platforms that do not handle
5941 printf("%s",NULL) gracefully.
5942 - Don't crash when a controller sends a third argument to an
5943 "extendcircuit" request.
5944 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
5945 response; fix error code when "getinfo dir/status/" fails.
5946 - Avoid crash when telling controller stream-status and a stream
5948 - Patch from Adam Langley to fix assert() in eventdns.c.
5949 - Fix a debug log message in eventdns to say "X resolved to Y"
5950 instead of "X resolved to X".
5951 - Make eventdns give strings for DNS errors, not just error numbers.
5952 - Track unreachable entry guards correctly: don't conflate
5953 'unreachable by us right now' with 'listed as down by the directory
5954 authorities'. With the old code, if a guard was unreachable by
5955 us but listed as running, it would clog our guard list forever.
5956 - Behave correctly in case we ever have a network with more than
5957 2GB/s total advertised capacity.
5958 - Make TrackExitHosts case-insensitive, and fix the behavior of
5959 ".suffix" TrackExitHosts items to avoid matching in the middle of
5961 - Finally fix the openssl warnings from newer gccs that believe that
5962 ignoring a return value is okay, but casting a return value and
5963 then ignoring it is a sign of madness.
5964 - Prevent the contrib/exitlist script from printing the same
5965 result more than once.
5966 - Patch from Steve Hildrey: Generate network status correctly on
5967 non-versioning dirservers.
5968 - Don't listen to the X-Your-Address-Is hint if you did the lookup
5969 via Tor; otherwise you'll think you're the exit node's IP address.
5971 o Minor bugfixes, performance:
5972 - Two small performance improvements on parsing descriptors.
5973 - Major performance improvement on inserting descriptors: change
5974 algorithm from O(n^2) to O(n).
5975 - Make the common memory allocation path faster on machines where
5976 malloc(0) returns a pointer.
5977 - Start remembering X-Your-Address-Is directory hints even if you're
5978 a client, so you can become a server more smoothly.
5979 - Avoid duplicate entries on MyFamily line in server descriptor.
5981 o Packaging, features:
5982 - Remove architecture from OS X builds. The official builds are
5983 now universal binaries.
5984 - The Debian package now uses --verify-config when (re)starting,
5985 to distinguish configuration errors from other errors.
5986 - Update RPMs to require libevent 1.1b.
5988 o Packaging, bugfixes:
5989 - Patches so Tor builds with MinGW on Windows.
5990 - Patches so Tor might run on Cygwin again.
5991 - Resume building on non-gcc compilers and ancient gcc. Resume
5992 building with the -O0 compile flag. Resume building cleanly on
5994 - Run correctly on OS X platforms with case-sensitive filesystems.
5995 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
5996 - Add autoconf checks so Tor can build on Solaris x86 again.
5999 - Documented (and renamed) ServerDNSSearchDomains and
6000 ServerDNSResolvConfFile options.
6001 - Be clearer that the *ListenAddress directives can be repeated
6005 Changes in version 0.1.1.24 - 2006-09-29
6007 - Allow really slow clients to not hang up five minutes into their
6008 directory downloads (suggested by Adam J. Richter).
6009 - Fix major performance regression from 0.1.0.x: instead of checking
6010 whether we have enough directory information every time we want to
6011 do something, only check when the directory information has changed.
6012 This should improve client CPU usage by 25-50%.
6013 - Don't crash if, after a server has been running for a while,
6014 it can't resolve its hostname.
6017 - Allow Tor to start when RunAsDaemon is set but no logs are set.
6018 - Don't crash when the controller receives a third argument to an
6019 "extendcircuit" request.
6020 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
6021 response; fix error code when "getinfo dir/status/" fails.
6022 - Fix configure.in to not produce broken configure files with
6023 more recent versions of autoconf. Thanks to Clint for his auto*
6025 - Fix security bug on NetBSD that could allow someone to force
6026 uninitialized RAM to be sent to a server's DNS resolver. This
6027 only affects NetBSD and other platforms that do not bounds-check
6029 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
6030 methods: these are known to be buggy.
6031 - If we're a directory mirror and we ask for "all" network status
6032 documents, we would discard status documents from authorities
6036 Changes in version 0.1.2.1-alpha - 2006-08-27
6038 - Add "eventdns" async dns library from Adam Langley, tweaked to
6039 build on OSX and Windows. Only enabled if you pass the
6040 --enable-eventdns argument to configure.
6041 - Allow servers with no hostname or IP address to learn their
6042 IP address by asking the directory authorities. This code only
6043 kicks in when you would normally have exited with a "no address"
6044 error. Nothing's authenticated, so use with care.
6045 - Rather than waiting a fixed amount of time between retrying
6046 application connections, we wait only 5 seconds for the first,
6047 10 seconds for the second, and 15 seconds for each retry after
6048 that. Hopefully this will improve the expected user experience.
6049 - Patch from Tup to add support for transparent AP connections:
6050 this basically bundles the functionality of trans-proxy-tor
6051 into the Tor mainline. Now hosts with compliant pf/netfilter
6052 implementations can redirect TCP connections straight to Tor
6053 without diverting through SOCKS. Needs docs.
6054 - Busy directory servers save lots of memory by spooling server
6055 descriptors, v1 directories, and v2 networkstatus docs to buffers
6056 as needed rather than en masse. Also mmap the cached-routers
6057 files, so we don't need to keep the whole thing in memory too.
6058 - Automatically avoid picking more than one node from the same
6059 /16 network when constructing a circuit.
6060 - Revise and clean up the torrc.sample that we ship with; add
6061 a section for BandwidthRate and BandwidthBurst.
6064 - Split circuit_t into origin_circuit_t and or_circuit_t, and
6065 split connection_t into edge, or, dir, control, and base structs.
6066 These will save quite a bit of memory on busy servers, and they'll
6067 also help us track down bugs in the code and bugs in the spec.
6068 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
6069 or later. Log when we are doing this, so we can diagnose it when
6070 it fails. (Also, recommend libevent 1.1b for kqueue and
6071 win32 methods; deprecate libevent 1.0b harder; make libevent
6072 recommendation system saner.)
6073 - Start being able to build universal binaries on OS X (thanks
6075 - Export the default exit policy via the control port, so controllers
6076 don't need to guess what it is / will be later.
6077 - Add a man page entry for ProtocolWarnings.
6078 - Add TestVia config option to the man page.
6079 - Remove even more protocol-related warnings from Tor server logs,
6080 such as bad TLS handshakes and malformed begin cells.
6081 - Stop fetching descriptors if you're not a dir mirror and you
6082 haven't tried to establish any circuits lately. [This currently
6083 causes some dangerous behavior, because when you start up again
6084 you'll use your ancient server descriptors.]
6085 - New DirPort behavior: if you have your dirport set, you download
6086 descriptors aggressively like a directory mirror, whether or not
6088 - Get rid of the router_retry_connections notion. Now routers
6089 no longer try to rebuild long-term connections to directory
6090 authorities, and directory authorities no longer try to rebuild
6091 long-term connections to all servers. We still don't hang up
6092 connections in these two cases though -- we need to look at it
6093 more carefully to avoid flapping, and we likely need to wait til
6094 0.1.1.x is obsolete.
6095 - Drop compatibility with obsolete Tors that permit create cells
6096 to have the wrong circ_id_type.
6097 - Re-enable per-connection rate limiting. Get rid of the "OP
6098 bandwidth" concept. Lay groundwork for "bandwidth classes" --
6099 separate global buckets that apply depending on what sort of conn
6101 - Start publishing one minute or so after we find our ORPort
6102 to be reachable. This will help reduce the number of descriptors
6103 we have for ourselves floating around, since it's quite likely
6104 other things (e.g. DirPort) will change during that minute too.
6105 - Fork the v1 directory protocol into its own spec document,
6106 and mark dir-spec.txt as the currently correct (v2) spec.
6109 - When we find our DirPort to be reachable, publish a new descriptor
6110 so we'll tell the world (reported by pnx).
6111 - Publish a new descriptor after we hup/reload. This is important
6112 if our config has changed such that we'll want to start advertising
6113 our DirPort now, etc.
6114 - Allow Tor to start when RunAsDaemon is set but no logs are set.
6115 - When we have a state file we cannot parse, tell the user and
6116 move it aside. Now we avoid situations where the user starts
6117 Tor in 1904, Tor writes a state file with that timestamp in it,
6118 the user fixes her clock, and Tor refuses to start.
6119 - Fix configure.in to not produce broken configure files with
6120 more recent versions of autoconf. Thanks to Clint for his auto*
6122 - "tor --verify-config" now exits with -1(255) or 0 depending on
6123 whether the config options are bad or good.
6124 - Resolve bug 321 when using dnsworkers: append a period to every
6125 address we resolve at the exit node, so that we do not accidentally
6126 pick up local addresses, and so that failing searches are retried
6127 in the resolver search domains. (This is already solved for
6128 eventdns.) (This breaks Blossom servers for now.)
6129 - If we are using an exit enclave and we can't connect, e.g. because
6130 its webserver is misconfigured to not listen on localhost, then
6131 back off and try connecting from somewhere else before we fail.
6134 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
6135 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
6136 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
6137 when the IP address is mapped through MapAddress to a hostname.
6138 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
6139 useless IPv6 DNS resolves.
6140 - Patch suggested by Karsten Loesing: respond to SIGNAL command
6141 before we execute the signal, in case the signal shuts us down.
6142 - Clean up AllowInvalidNodes man page entry.
6143 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
6144 - Add more asserts to track down an assert error on a windows Tor
6145 server with connection_add being called with socket == -1.
6146 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
6147 - Fix misleading log messages: an entry guard that is "unlisted",
6148 as well as not known to be "down" (because we've never heard
6149 of it), is not therefore "up".
6150 - Remove code to special-case "-cvs" ending, since it has not
6151 actually mattered since 0.0.9.
6152 - Make our socks5 handling more robust to broken socks clients:
6153 throw out everything waiting on the buffer in between socks
6154 handshake phases, since they can't possibly (so the theory
6155 goes) have predicted what we plan to respond to them.
6158 Changes in version 0.1.1.23 - 2006-07-30
6160 - Fast Tor servers, especially exit nodes, were triggering asserts
6161 due to a bug in handling the list of pending DNS resolves. Some
6162 bugs still remain here; we're hunting them.
6163 - Entry guards could crash clients by sending unexpected input.
6164 - More fixes on reachability testing: if you find yourself reachable,
6165 then don't ever make any client requests (so you stop predicting
6166 circuits), then hup or have your clock jump, then later your IP
6167 changes, you won't think circuits are working, so you won't try to
6168 test reachability, so you won't publish.
6171 - Avoid a crash if the controller does a resetconf firewallports
6172 and then a setconf fascistfirewall=1.
6173 - Avoid an integer underflow when the dir authority decides whether
6174 a router is stable: we might wrongly label it stable, and compute
6175 a slightly wrong median stability, when a descriptor is published
6177 - Fix a place where we might trigger an assert if we can't build our
6178 own server descriptor yet.
6181 Changes in version 0.1.1.22 - 2006-07-05
6183 - Fix a big bug that was causing servers to not find themselves
6184 reachable if they changed IP addresses. Since only 0.1.1.22+
6185 servers can do reachability testing correctly, now we automatically
6186 make sure to test via one of these.
6187 - Fix to allow clients and mirrors to learn directory info from
6188 descriptor downloads that get cut off partway through.
6189 - Directory authorities had a bug in deciding if a newly published
6190 descriptor was novel enough to make everybody want a copy -- a few
6191 servers seem to be publishing new descriptors many times a minute.
6193 - Fix a rare bug that was causing some servers to complain about
6194 "closing wedged cpuworkers" and skip some circuit create requests.
6195 - Make the Exit flag in directory status documents actually work.
6198 Changes in version 0.1.1.21 - 2006-06-10
6199 o Crash and assert fixes from 0.1.1.20:
6200 - Fix a rare crash on Tor servers that have enabled hibernation.
6201 - Fix a seg fault on startup for Tor networks that use only one
6202 directory authority.
6203 - Fix an assert from a race condition that occurs on Tor servers
6204 while exiting, where various threads are trying to log that they're
6205 exiting, and delete the logs, at the same time.
6206 - Make our unit tests pass again on certain obscure platforms.
6209 - Add support for building SUSE RPM packages.
6210 - Speed up initial bootstrapping for clients: if we are making our
6211 first ever connection to any entry guard, then don't mark it down
6213 - When only one Tor server in the network is labelled as a guard,
6214 and we've already picked him, we would cycle endlessly picking him
6215 again, being unhappy about it, etc. Now we specifically exclude
6216 current guards when picking a new guard.
6217 - Servers send create cells more reliably after the TLS connection
6218 is established: we were sometimes forgetting to send half of them
6219 when we had more than one pending.
6220 - If we get a create cell that asks us to extend somewhere, but the
6221 Tor server there doesn't match the expected digest, we now send
6222 a destroy cell back, rather than silently doing nothing.
6223 - Make options->RedirectExit work again.
6224 - Make cookie authentication for the controller work again.
6225 - Stop being picky about unusual characters in the arguments to
6226 mapaddress. It's none of our business.
6227 - Add a new config option "TestVia" that lets you specify preferred
6228 middle hops to use for test circuits. Perhaps this will let me
6229 debug the reachability problems better.
6231 o Log / documentation fixes:
6232 - If we're a server and some peer has a broken TLS certificate, don't
6233 log about it unless ProtocolWarnings is set, i.e., we want to hear
6234 about protocol violations by others.
6235 - Fix spelling of VirtualAddrNetwork in man page.
6236 - Add a better explanation at the top of the autogenerated torrc file
6237 about what happened to our old torrc.
6240 Changes in version 0.1.1.20 - 2006-05-23
6242 - Downgrade a log severity where servers complain that they're
6244 - Avoid a compile warning on FreeBSD.
6245 - Remove string size limit on NEWDESC messages; solve bug 291.
6246 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
6247 more thoroughly when we're running on windows.
6250 Changes in version 0.1.1.19-rc - 2006-05-03
6252 - Regenerate our local descriptor if it's dirty and we try to use
6253 it locally (e.g. if it changes during reachability detection).
6254 - If we setconf our ORPort to 0, we continued to listen on the
6255 old ORPort and receive connections.
6256 - Avoid a second warning about machine/limits.h on Debian
6258 - Be willing to add our own routerinfo into the routerlist.
6259 Now authorities will include themselves in their directories
6260 and network-statuses.
6261 - Stop trying to upload rendezvous descriptors to every
6262 directory authority: only try the v1 authorities.
6263 - Servers no longer complain when they think they're not
6264 registered with the directory authorities. There were too many
6266 - Backport dist-rpm changes so rpms can be built without errors.
6269 - Implement an option, VirtualAddrMask, to set which addresses
6270 get handed out in response to mapaddress requests. This works
6271 around a bug in tsocks where 127.0.0.0/8 is never socksified.
6274 Changes in version 0.1.1.18-rc - 2006-04-10
6276 - Work harder to download live network-statuses from all the
6277 directory authorities we know about. Improve the threshold
6278 decision logic so we're more robust to edge cases.
6279 - When fetching rendezvous descriptors, we were willing to ask
6280 v2 authorities too, which would always return 404.
6283 - Stop listing down or invalid nodes in the v1 directory. This will
6284 reduce its bulk by about 1/3, and reduce load on directory
6286 - When deciding whether a router is Fast or Guard-worthy, consider
6287 his advertised BandwidthRate and not just the BandwidthCapacity.
6288 - No longer ship INSTALL and README files -- they are useless now.
6289 - Force rpmbuild to behave and honor target_cpu.
6290 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
6291 - Start to include translated versions of the tor-doc-*.html
6292 files, along with the screenshots. Still needs more work.
6293 - Start sending back 512 and 451 errors if mapaddress fails,
6294 rather than not sending anything back at all.
6295 - When we fail to bind or listen on an incoming or outgoing
6296 socket, we should close it before failing. otherwise we just
6297 leak it. (thanks to weasel for finding.)
6298 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
6299 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
6300 - Make NoPublish (even though deprecated) work again.
6301 - Fix a minor security flaw where a versioning auth dirserver
6302 could list a recommended version many times in a row to make
6303 clients more convinced that it's recommended.
6304 - Fix crash bug if there are two unregistered servers running
6305 with the same nickname, one of them is down, and you ask for
6306 them by nickname in your EntryNodes or ExitNodes. Also, try
6307 to pick the one that's running rather than an arbitrary one.
6308 - Fix an infinite loop we could hit if we go offline for too long.
6309 - Complain when we hit WSAENOBUFS on recv() or write() too.
6310 Perhaps this will help us hunt the bug.
6311 - If you're not a versioning dirserver, don't put the string
6312 "client-versions \nserver-versions \n" in your network-status.
6313 - Lower the minimum required number of file descriptors to 1000,
6314 so we can have some overhead for Valgrind on Linux, where the
6315 default ulimit -n is 1024.
6318 - Add tor.dizum.com as the fifth authoritative directory server.
6319 - Add a new config option FetchUselessDescriptors, off by default,
6320 for when you plan to run "exitlist" on your client and you want
6321 to know about even the non-running descriptors.
6324 Changes in version 0.1.1.17-rc - 2006-03-28
6326 - Clients and servers since 0.1.1.10-alpha have been expiring
6327 connections whenever they are idle for 5 minutes and they *do*
6328 have circuits on them. Oops. With this new version, clients will
6329 discard their previous entry guard choices and avoid choosing
6330 entry guards running these flawed versions.
6331 - Fix memory leak when uncompressing concatenated zlib streams. This
6332 was causing substantial leaks over time on Tor servers.
6333 - The v1 directory was including servers as much as 48 hours old,
6334 because that's how the new routerlist->routers works. Now only
6335 include them if they're 20 hours old or less.
6338 - Resume building on irix64, netbsd 2.0, etc.
6339 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
6341 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
6342 and it is confusing some users.
6343 - Mirrors stop caching the v1 directory so often.
6344 - Make the max number of old descriptors that a cache will hold
6345 rise with the number of directory authorities, so we can scale.
6346 - Change our win32 uname() hack to be more forgiving about what
6347 win32 versions it thinks it's found.
6350 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
6352 - When the controller's *setconf commands fail, collect an error
6353 message in a string and hand it back to the controller.
6354 - Make the v2 dir's "Fast" flag based on relative capacity, just
6355 like "Stable" is based on median uptime. Name everything in the
6356 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
6357 - Log server fingerprint on startup, so new server operators don't
6358 have to go hunting around their filesystem for it.
6359 - Return a robots.txt on our dirport to discourage google indexing.
6360 - Let the controller ask for GETINFO dir/status/foo so it can ask
6361 directly rather than connecting to the dir port. Only works when
6362 dirport is set for now.
6364 o New config options rather than constants in the code:
6365 - SocksTimeout: How long do we let a socks connection wait
6366 unattached before we fail it?
6367 - CircuitBuildTimeout: Cull non-open circuits that were born
6368 at least this many seconds ago.
6369 - CircuitIdleTimeout: Cull open clean circuits that were born
6370 at least this many seconds ago.
6373 Changes in version 0.1.1.16-rc - 2006-03-18
6374 o Bugfixes on 0.1.1.15-rc:
6375 - Fix assert when the controller asks to attachstream a connect-wait
6376 or resolve-wait stream.
6377 - Now do address rewriting when the controller asks us to attach
6378 to a particular circuit too. This will let Blossom specify
6379 "moria2.exit" without having to learn what moria2's IP address is.
6380 - Make the "tor --verify-config" command-line work again, so people
6381 can automatically check if their torrc will parse.
6382 - Authoritative dirservers no longer require an open connection from
6383 a server to consider him "reachable". We need this change because
6384 when we add new auth dirservers, old servers won't know not to
6386 - Let Tor build on Sun CC again.
6387 - Fix an off-by-one buffer size in dirserv.c that magically never
6388 hit our three authorities but broke sjmurdoch's own tor network.
6389 - If we as a directory mirror don't know of any v1 directory
6390 authorities, then don't try to cache any v1 directories.
6391 - Stop warning about unknown servers in our family when they are
6392 given as hex digests.
6393 - Stop complaining as quickly to the server operator that he
6394 hasn't registered his nickname/key binding.
6395 - Various cleanups so we can add new V2 Auth Dirservers.
6396 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
6397 reflect the updated flags in our v2 dir protocol.
6398 - Resume allowing non-printable characters for exit streams (both
6399 for connecting and for resolving). Now we tolerate applications
6400 that don't follow the RFCs. But continue to block malformed names
6403 o Bugfixes on 0.1.0.x:
6404 - Fix assert bug in close_logs(): when we close and delete logs,
6405 remove them all from the global "logfiles" list.
6406 - Fix minor integer overflow in calculating when we expect to use up
6407 our bandwidth allocation before hibernating.
6408 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
6409 there are multiple SSLs installed with different versions.
6410 - When we try to be a server and Address is not explicitly set and
6411 our hostname resolves to a private IP address, try to use an
6412 interface address if it has a public address. Now Windows machines
6413 that think of themselves as localhost can work by default.
6416 - Let the controller ask for GETINFO dir/server/foo so it can ask
6417 directly rather than connecting to the dir port.
6418 - Let the controller tell us about certain router descriptors
6419 that it doesn't want Tor to use in circuits. Implement
6420 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
6421 - New config option SafeSocks to reject all application connections
6422 using unsafe socks protocols. Defaults to off.
6425 Changes in version 0.1.1.15-rc - 2006-03-11
6426 o Bugfixes and cleanups:
6427 - When we're printing strings from the network, don't try to print
6428 non-printable characters. This protects us against shell escape
6429 sequence exploits, and also against attacks to fool humans into
6430 misreading their logs.
6431 - Fix a bug where Tor would fail to establish any connections if you
6432 left it off for 24 hours and then started it: we were happy with
6433 the obsolete network statuses, but they all referred to router
6434 descriptors that were too old to fetch, so we ended up with no
6435 valid router descriptors.
6436 - Fix a seg fault in the controller's "getinfo orconn-status"
6437 command while listing status on incoming handshaking connections.
6438 Introduce a status name "NEW" for these connections.
6439 - If we get a linelist or linelist_s config option from the torrc
6440 (e.g. ExitPolicy) and it has no value, warn and skip rather than
6441 silently resetting it to its default.
6442 - Don't abandon entry guards until they've been down or gone for
6444 - Cleaner and quieter log messages.
6447 - New controller signal NEWNYM that makes new application requests
6449 - Add a new circuit purpose 'controller' to let the controller ask
6450 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
6451 controller command to let you specify the purpose if you're
6452 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
6453 command to let you change a circuit's purpose after it's been
6455 - Accept "private:*" in routerdesc exit policies; not generated yet
6456 because older Tors do not understand it.
6457 - Add BSD-style contributed startup script "rc.subr" from Peter
6461 Changes in version 0.1.1.14-alpha - 2006-02-20
6462 o Bugfixes on 0.1.1.x:
6463 - Don't die if we ask for a stdout or stderr log (even implicitly)
6464 and we're set to RunAsDaemon -- just warn.
6465 - We still had a few bugs in the OR connection rotation code that
6466 caused directory servers to slowly aggregate connections to other
6467 fast Tor servers. This time for sure!
6468 - Make log entries on Win32 include the name of the function again.
6469 - We were treating a pair of exit policies if they were equal even
6470 if one said accept and the other said reject -- causing us to
6471 not always publish a new descriptor since we thought nothing
6473 - Retry pending server downloads as well as pending networkstatus
6474 downloads when we unexpectedly get a socks request.
6475 - We were ignoring the IS_FAST flag in the directory status,
6476 meaning we were willing to pick trivial-bandwidth nodes for "fast"
6478 - If the controller's SAVECONF command fails (e.g. due to file
6479 permissions), let the controller know that it failed.
6482 - If we're trying to be a Tor server and running Windows 95/98/ME
6483 as a server, explain that we'll likely crash.
6484 - When we're a server, a client asks for an old-style directory,
6485 and our write bucket is empty, don't give it to him. This way
6486 small servers can continue to serve the directory *sometimes*,
6487 without getting overloaded.
6488 - Compress exit policies even more -- look for duplicate lines
6490 - Clients now honor the "guard" flag in the router status when
6491 picking entry guards, rather than looking at is_fast or is_stable.
6492 - Retain unrecognized lines in $DATADIR/state file, so that we can
6493 be forward-compatible.
6494 - Generate 18.0.0.0/8 address policy format in descs when we can;
6495 warn when the mask is not reducible to a bit-prefix.
6496 - Let the user set ControlListenAddress in the torrc. This can be
6497 dangerous, but there are some cases (like a secured LAN) where it
6499 - Split ReachableAddresses into ReachableDirAddresses and
6500 ReachableORAddresses, so we can restrict Dir conns to port 80
6501 and OR conns to port 443.
6502 - Now we can target arch and OS in rpm builds (contributed by
6503 Phobos). Also make the resulting dist-rpm filename match the
6505 - New config options to help controllers: FetchServerDescriptors
6506 and FetchHidServDescriptors for whether to fetch server
6507 info and hidserv info or let the controller do it, and
6508 PublishServerDescriptor and PublishHidServDescriptors.
6509 - Also let the controller set the __AllDirActionsPrivate config
6510 option if you want all directory fetches/publishes to happen via
6511 Tor (it assumes your controller bootstraps your circuits).
6514 Changes in version 0.1.0.17 - 2006-02-17
6515 o Crash bugfixes on 0.1.0.x:
6516 - When servers with a non-zero DirPort came out of hibernation,
6517 sometimes they would trigger an assert.
6519 o Other important bugfixes:
6520 - On platforms that don't have getrlimit (like Windows), we were
6521 artificially constraining ourselves to a max of 1024
6522 connections. Now just assume that we can handle as many as 15000
6523 connections. Hopefully this won't cause other problems.
6525 o Backported features:
6526 - When we're a server, a client asks for an old-style directory,
6527 and our write bucket is empty, don't give it to him. This way
6528 small servers can continue to serve the directory *sometimes*,
6529 without getting overloaded.
6530 - Whenever you get a 503 in response to a directory fetch, try
6531 once more. This will become important once servers start sending
6532 503's whenever they feel busy.
6533 - Fetch a new directory every 120 minutes, not every 40 minutes.
6534 Now that we have hundreds of thousands of users running the old
6535 directory algorithm, it's starting to hurt a lot.
6536 - Bump up the period for forcing a hidden service descriptor upload
6537 from 20 minutes to 1 hour.
6540 Changes in version 0.1.1.13-alpha - 2006-02-09
6541 o Crashes in 0.1.1.x:
6542 - When you tried to setconf ORPort via the controller, Tor would
6543 crash. So people using TorCP to become a server were sad.
6544 - Solve (I hope) the stack-smashing bug that we were seeing on fast
6545 servers. The problem appears to be something do with OpenSSL's
6546 random number generation, or how we call it, or something. Let me
6547 know if the crashes continue.
6548 - Turn crypto hardware acceleration off by default, until we find
6549 somebody smart who can test it for us. (It appears to produce
6550 seg faults in at least some cases.)
6551 - Fix a rare assert error when we've tried all intro points for
6552 a hidden service and we try fetching the service descriptor again:
6553 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
6556 - Fix a major load balance bug: we were round-robining in 16 KB
6557 chunks, and servers with bandwidthrate of 20 KB, while downloading
6558 a 600 KB directory, would starve their other connections. Now we
6559 try to be a bit more fair.
6560 - Dir authorities and mirrors were never expiring the newest
6561 descriptor for each server, causing memory and directory bloat.
6562 - Fix memory-bloating and connection-bloating bug on servers: We
6563 were never closing any connection that had ever had a circuit on
6564 it, because we were checking conn->n_circuits == 0, yet we had a
6565 bug that let it go negative.
6566 - Make Tor work using squid as your http proxy again -- squid
6567 returns an error if you ask for a URL that's too long, and it uses
6568 a really generic error message. Plus, many people are behind a
6569 transparent squid so they don't even realize it.
6570 - On platforms that don't have getrlimit (like Windows), we were
6571 artificially constraining ourselves to a max of 1024
6572 connections. Now just assume that we can handle as many as 15000
6573 connections. Hopefully this won't cause other problems.
6574 - Add a new config option ExitPolicyRejectPrivate which defaults to
6575 1. This means all exit policies will begin with rejecting private
6576 addresses, unless the server operator explicitly turns it off.
6579 - Clients no longer download descriptors for non-running
6581 - Before we add new directory authorities, we should make it
6582 clear that only v1 authorities should receive/publish hidden
6583 service descriptors.
6586 - As soon as we've fetched some more directory info, immediately
6587 try to download more server descriptors. This way we don't have
6588 a 10 second pause during initial bootstrapping.
6589 - Remove even more loud log messages that the server operator can't
6591 - When we're running an obsolete or un-recommended version, make
6592 the log message more clear about what the problem is and what
6593 versions *are* still recommended.
6594 - Provide a more useful warn message when our onion queue gets full:
6595 the CPU is too slow or the exit policy is too liberal.
6596 - Don't warn when we receive a 503 from a dirserver/cache -- this
6597 will pave the way for them being able to refuse if they're busy.
6598 - When we fail to bind a listener, try to provide a more useful
6599 log message: e.g., "Is Tor already running?"
6600 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
6601 Goldberg can prove things about our handshake protocol more
6603 - MaxConn has been obsolete for a while now. Document the ConnLimit
6604 config option, which is a *minimum* number of file descriptors
6605 that must be available else Tor refuses to start.
6606 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
6607 if you log to syslog and want something other than LOG_DAEMON.
6608 - Make dirservers generate a separate "guard" flag to mean,
6609 "would make a good entry guard". Make clients parse it and vote
6610 on it. Not used by clients yet.
6611 - Implement --with-libevent-dir option to ./configure. Also, improve
6612 search techniques to find libevent, and use those for openssl too.
6613 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
6614 - Only start testing reachability once we've established a
6615 circuit. This will make startup on dirservers less noisy.
6616 - Don't try to upload hidden service descriptors until we have
6617 established a circuit.
6618 - Fix the controller's "attachstream 0" command to treat conn like
6619 it just connected, doing address remapping, handling .exit and
6620 .onion idioms, and so on. Now we're more uniform in making sure
6621 that the controller hears about new and closing connections.
6624 Changes in version 0.1.1.12-alpha - 2006-01-11
6625 o Bugfixes on 0.1.1.x:
6626 - The fix to close duplicate server connections was closing all
6627 Tor client connections if they didn't establish a circuit
6628 quickly enough. Oops.
6629 - Fix minor memory issue (double-free) that happened on exit.
6631 o Bugfixes on 0.1.0.x:
6632 - Tor didn't warn when it failed to open a log file.
6635 Changes in version 0.1.1.11-alpha - 2006-01-10
6636 o Crashes in 0.1.1.x:
6637 - Include all the assert/crash fixes from 0.1.0.16.
6638 - If you start Tor and then quit very quickly, there were some
6639 races that tried to free things that weren't allocated yet.
6640 - Fix a rare memory stomp if you're running hidden services.
6641 - Fix segfault when specifying DirServer in config without nickname.
6642 - Fix a seg fault when you finish connecting to a server but at
6643 that moment you dump his server descriptor.
6644 - Extendcircuit and Attachstream controller commands would
6645 assert/crash if you don't give them enough arguments.
6646 - Fix an assert error when we're out of space in the connection_list
6647 and we try to post a hidden service descriptor (reported by weasel).
6648 - If you specify a relative torrc path and you set RunAsDaemon in
6649 your torrc, then it chdir()'s to the new directory. If you HUP,
6650 it tries to load the new torrc location, fails, and exits.
6651 The fix: no longer allow a relative path to torrc using -f.
6654 - Implement "entry guards": automatically choose a handful of entry
6655 nodes and stick with them for all circuits. Only pick new guards
6656 when the ones you have are unsuitable, and if the old guards
6657 become suitable again, switch back. This will increase security
6658 dramatically against certain end-point attacks. The EntryNodes
6659 config option now provides some hints about which entry guards you
6660 want to use most; and StrictEntryNodes means to only use those.
6661 - New directory logic: download by descriptor digest, not by
6662 fingerprint. Caches try to download all listed digests from
6663 authorities; clients try to download "best" digests from caches.
6664 This avoids partitioning and isolating attacks better.
6665 - Make the "stable" router flag in network-status be the median of
6666 the uptimes of running valid servers, and make clients pay
6667 attention to the network-status flags. Thus the cutoff adapts
6668 to the stability of the network as a whole, making IRC, IM, etc
6669 connections more reliable.
6672 - Tor servers with dynamic IP addresses were needing to wait 18
6673 hours before they could start doing reachability testing using
6674 the new IP address and ports. This is because they were using
6675 the internal descriptor to learn what to test, yet they were only
6676 rebuilding the descriptor once they decided they were reachable.
6677 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
6678 to download certain server descriptors, throw them away, and then
6679 fetch them again after 30 minutes. Now mirrors throw away these
6680 server descriptors so clients can't get them.
6681 - We were leaving duplicate connections to other ORs open for a week,
6682 rather than closing them once we detect a duplicate. This only
6683 really affected authdirservers, but it affected them a lot.
6684 - Spread the authdirservers' reachability testing over the entire
6685 testing interval, so we don't try to do 500 TLS's at once every
6689 - If the network is down, and we try to connect to a conn because
6690 we have a circuit in mind, and we timeout (30 seconds) because the
6691 network never answers, we were expiring the circuit, but we weren't
6692 obsoleting the connection or telling the entry_guards functions.
6693 - Some Tor servers process billions of cells per day. These statistics
6694 need to be uint64_t's.
6695 - Check for integer overflows in more places, when adding elements
6696 to smartlists. This could possibly prevent a buffer overflow
6697 on malicious huge inputs. I don't see any, but I haven't looked
6699 - ReachableAddresses kept growing new "reject *:*" lines on every
6701 - When you "setconf log" via the controller, it should remove all
6702 logs. We were automatically adding back in a "log notice stdout".
6703 - Newly bootstrapped Tor networks couldn't establish hidden service
6704 circuits until they had nodes with high uptime. Be more tolerant.
6705 - We were marking servers down when they could not answer every piece
6706 of the directory request we sent them. This was far too harsh.
6707 - Fix the torify (tsocks) config file to not use Tor for localhost
6709 - Directory authorities now go to the proper authority when asking for
6710 a networkstatus, even when they want a compressed one.
6711 - Fix a harmless bug that was causing Tor servers to log
6712 "Got an end because of misc error, but we're not an AP. Closing."
6713 - Authorities were treating their own descriptor changes as cosmetic,
6714 meaning the descriptor available in the network-status and the
6715 descriptor that clients downloaded were different.
6716 - The OS X installer was adding a symlink for tor_resolve but
6717 the binary was called tor-resolve (reported by Thomas Hardly).
6718 - Workaround a problem with some http proxies where they refuse GET
6719 requests that specify "Content-Length: 0" (reported by Adrian).
6720 - Fix wrong log message when you add a "HiddenServiceNodes" config
6721 line without any HiddenServiceDir line (reported by Chris Thomas).
6724 - Write the TorVersion into the state file so we have a prayer of
6725 keeping forward and backward compatibility.
6726 - Revive the FascistFirewall config option rather than eliminating it:
6727 now it's a synonym for ReachableAddresses *:80,*:443.
6728 - Clients choose directory servers from the network status lists,
6729 not from their internal list of router descriptors. Now they can
6730 go to caches directly rather than needing to go to authorities
6732 - Directory authorities ignore router descriptors that have only
6733 cosmetic differences: do this for 0.1.0.x servers now too.
6734 - Add a new flag to network-status indicating whether the server
6735 can answer v2 directory requests too.
6736 - Authdirs now stop whining so loudly about bad descriptors that
6737 they fetch from other dirservers. So when there's a log complaint,
6738 it's for sure from a freshly uploaded descriptor.
6739 - Reduce memory requirements in our structs by changing the order
6741 - There used to be two ways to specify your listening ports in a
6742 server descriptor: on the "router" line and with a separate "ports"
6743 line. Remove support for the "ports" line.
6744 - New config option "AuthDirRejectUnlisted" for auth dirservers as
6745 a panic button: if we get flooded with unusable servers we can
6746 revert to only listing servers in the approved-routers file.
6747 - Auth dir servers can now mark a fingerprint as "!reject" or
6748 "!invalid" in the approved-routers file (as its nickname), to
6749 refuse descriptors outright or include them but marked as invalid.
6750 - Servers store bandwidth history across restarts/crashes.
6751 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
6752 get a better idea of why their circuits failed. Not used yet.
6753 - Directory mirrors now cache up to 16 unrecognized network-status
6754 docs. Now we can add new authdirservers and they'll be cached too.
6755 - When picking a random directory, prefer non-authorities if any
6757 - New controller option "getinfo desc/all-recent" to fetch the
6758 latest server descriptor for every router that Tor knows about.
6761 Changes in version 0.1.0.16 - 2006-01-02
6762 o Crash bugfixes on 0.1.0.x:
6763 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
6764 corrupting the heap, losing FDs, or crashing when we need to resize
6765 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
6766 - It turns out sparc64 platforms crash on unaligned memory access
6767 too -- so detect and avoid this.
6768 - Handle truncated compressed data correctly (by detecting it and
6770 - Fix possible-but-unlikely free(NULL) in control.c.
6771 - When we were closing connections, there was a rare case that
6772 stomped on memory, triggering seg faults and asserts.
6773 - Avoid potential infinite recursion when building a descriptor. (We
6774 don't know that it ever happened, but better to fix it anyway.)
6775 - We were neglecting to unlink marked circuits from soon-to-close OR
6776 connections, which caused some rare scribbling on freed memory.
6777 - Fix a memory stomping race bug when closing the joining point of two
6778 rendezvous circuits.
6779 - Fix an assert in time parsing found by Steven Murdoch.
6781 o Other bugfixes on 0.1.0.x:
6782 - When we're doing reachability testing, provide more useful log
6783 messages so the operator knows what to expect.
6784 - Do not check whether DirPort is reachable when we are suppressing
6785 advertising it because of hibernation.
6786 - When building with -static or on Solaris, we sometimes needed -ldl.
6787 - When we're deciding whether a stream has enough circuits around
6788 that can handle it, count the freshly dirty ones and not the ones
6789 that are so dirty they won't be able to handle it.
6790 - When we're expiring old circuits, we had a logic error that caused
6791 us to close new rendezvous circuits rather than old ones.
6792 - Give a more helpful log message when you try to change ORPort via
6793 the controller: you should upgrade Tor if you want that to work.
6794 - We were failing to parse Tor versions that start with "Tor ".
6795 - Tolerate faulty streams better: when a stream fails for reason
6796 exitpolicy, stop assuming that the router is lying about his exit
6797 policy. When a stream fails for reason misc, allow it to retry just
6798 as if it was resolvefailed. When a stream has failed three times,
6799 reset its failure count so we can try again and get all three tries.
6802 Changes in version 0.1.1.10-alpha - 2005-12-11
6803 o Correctness bugfixes on 0.1.0.x:
6804 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
6805 corrupting the heap, losing FDs, or crashing when we need to resize
6806 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
6807 - Stop doing the complex voodoo overkill checking for insecure
6808 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
6809 - When we were closing connections, there was a rare case that
6810 stomped on memory, triggering seg faults and asserts.
6811 - We were neglecting to unlink marked circuits from soon-to-close OR
6812 connections, which caused some rare scribbling on freed memory.
6813 - When we're deciding whether a stream has enough circuits around
6814 that can handle it, count the freshly dirty ones and not the ones
6815 that are so dirty they won't be able to handle it.
6816 - Recover better from TCP connections to Tor servers that are
6817 broken but don't tell you (it happens!); and rotate TLS
6818 connections once a week.
6819 - When we're expiring old circuits, we had a logic error that caused
6820 us to close new rendezvous circuits rather than old ones.
6821 - Fix a scary-looking but apparently harmless bug where circuits
6822 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
6823 servers, and never switch to state CIRCUIT_STATE_OPEN.
6824 - When building with -static or on Solaris, we sometimes needed to
6826 - Give a useful message when people run Tor as the wrong user,
6827 rather than telling them to start chowning random directories.
6828 - We were failing to inform the controller about new .onion streams.
6830 o Security bugfixes on 0.1.0.x:
6831 - Refuse server descriptors if the fingerprint line doesn't match
6832 the included identity key. Tor doesn't care, but other apps (and
6833 humans) might actually be trusting the fingerprint line.
6834 - We used to kill the circuit when we receive a relay command we
6835 don't recognize. Now we just drop it.
6836 - Start obeying our firewall options more rigorously:
6837 . If we can't get to a dirserver directly, try going via Tor.
6838 . Don't ever try to connect (as a client) to a place our
6839 firewall options forbid.
6840 . If we specify a proxy and also firewall options, obey the
6841 firewall options even when we're using the proxy: some proxies
6842 can only proxy to certain destinations.
6843 - Fix a bug found by Lasse Overlier: when we were making internal
6844 circuits (intended to be cannibalized later for rendezvous and
6845 introduction circuits), we were picking them so that they had
6846 useful exit nodes. There was no need for this, and it actually
6847 aids some statistical attacks.
6848 - Start treating internal circuits and exit circuits separately.
6849 It's important to keep them separate because internal circuits
6850 have their last hops picked like middle hops, rather than like
6851 exit hops. So exiting on them will break the user's expectations.
6853 o Bugfixes on 0.1.1.x:
6854 - Take out the mis-feature where we tried to detect IP address
6855 flapping for people with DynDNS, and chose not to upload a new
6856 server descriptor sometimes.
6857 - Try to be compatible with OpenSSL 0.9.6 again.
6858 - Log fix: when the controller is logging about .onion addresses,
6859 sometimes it didn't include the ".onion" part of the address.
6860 - Don't try to modify options->DirServers internally -- if the
6861 user didn't specify any, just add the default ones directly to
6862 the trusted dirserver list. This fixes a bug where people running
6863 controllers would use SETCONF on some totally unrelated config
6864 option, and Tor would start yelling at them about changing their
6866 - Let the controller's redirectstream command specify a port, in
6867 case the controller wants to change that too.
6868 - When we requested a pile of server descriptors, we sometimes
6869 accidentally launched a duplicate request for the first one.
6870 - Bugfix for trackhostexits: write down the fingerprint of the
6871 chosen exit, not its nickname, because the chosen exit might not
6873 - When parsing foo.exit, if foo is unknown, and we are leaving
6874 circuits unattached, set the chosen_exit field and leave the
6875 address empty. This matters because controllers got confused
6877 - Directory authorities no longer try to download server
6878 descriptors that they know they will reject.
6880 o Features and updates:
6881 - Replace balanced trees with hash tables: this should make stuff
6882 significantly faster.
6883 - Resume using the AES counter-mode implementation that we ship,
6884 rather than OpenSSL's. Ours is significantly faster.
6885 - Many other CPU and memory improvements.
6886 - Add a new config option FastFirstHopPK (on by default) so clients
6887 do a trivial crypto handshake for their first hop, since TLS has
6888 already taken care of confidentiality and authentication.
6889 - Add a new config option TestSocks so people can see if their
6890 applications are using socks4, socks4a, socks5-with-ip, or
6891 socks5-with-hostname. This way they don't have to keep mucking
6892 with tcpdump and wondering if something got cached somewhere.
6893 - Warn when listening on a public address for socks. I suspect a
6894 lot of people are setting themselves up as open socks proxies,
6895 and they have no idea that jerks on the Internet are using them,
6896 since they simply proxy the traffic into the Tor network.
6897 - Add "private:*" as an alias in configuration for policies. Now
6898 you can simplify your exit policy rather than needing to list
6899 every single internal or nonroutable network space.
6900 - Add a new controller event type that allows controllers to get
6901 all server descriptors that were uploaded to a router in its role
6902 as authoritative dirserver.
6903 - Start shipping socks-extensions.txt, tor-doc-unix.html,
6904 tor-doc-server.html, and stylesheet.css in the tarball.
6905 - Stop shipping tor-doc.html in the tarball.
6908 Changes in version 0.1.1.9-alpha - 2005-11-15
6909 o Usability improvements:
6910 - Start calling it FooListenAddress rather than FooBindAddress,
6911 since few of our users know what it means to bind an address
6913 - Reduce clutter in server logs. We're going to try to make
6914 them actually usable now. New config option ProtocolWarnings that
6915 lets you hear about how _other Tors_ are breaking the protocol. Off
6917 - Divide log messages into logging domains. Once we put some sort
6918 of interface on this, it will let people looking at more verbose
6919 log levels specify the topics they want to hear more about.
6920 - Make directory servers return better http 404 error messages
6921 instead of a generic "Servers unavailable".
6922 - Check for even more Windows version flags when writing the platform
6923 string in server descriptors, and note any we don't recognize.
6924 - Clean up more of the OpenSSL memory when exiting, so we can detect
6925 memory leaks better.
6926 - Make directory authorities be non-versioning, non-naming by
6927 default. Now we can add new directory servers without requiring
6928 their operators to pay close attention.
6929 - When logging via syslog, include the pid whenever we provide
6930 a log entry. Suggested by Todd Fries.
6932 o Performance improvements:
6933 - Directory servers now silently throw away new descriptors that
6934 haven't changed much if the timestamps are similar. We do this to
6935 tolerate older Tor servers that upload a new descriptor every 15
6936 minutes. (It seemed like a good idea at the time.)
6937 - Inline bottleneck smartlist functions; use fast versions by default.
6938 - Add a "Map from digest to void*" abstraction digestmap_t so we
6939 can do less hex encoding/decoding. Use it in router_get_by_digest()
6940 to resolve a performance bottleneck.
6941 - Allow tor_gzip_uncompress to extract as much as possible from
6942 truncated compressed data. Try to extract as many
6943 descriptors as possible from truncated http responses (when
6944 DIR_PURPOSE_FETCH_ROUTERDESC).
6945 - Make circ->onionskin a pointer, not a static array. moria2 was using
6946 125000 circuit_t's after it had been up for a few weeks, which
6947 translates to 20+ megs of wasted space.
6948 - The private half of our EDH handshake keys are now chosen out
6949 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
6951 o Security improvements:
6952 - Start making directory caches retain old routerinfos, so soon
6953 clients can start asking by digest of descriptor rather than by
6954 fingerprint of server.
6955 - Add half our entropy from RAND_poll in OpenSSL. This knows how
6956 to use egd (if present), openbsd weirdness (if present), vms/os2
6957 weirdness (if we ever port there), and more in the future.
6959 o Bugfixes on 0.1.0.x:
6960 - Do round-robin writes of at most 16 kB per write. This might be
6961 more fair on loaded Tor servers, and it might resolve our Windows
6962 crash bug. It might also slow things down.
6963 - Our TLS handshakes were generating a single public/private
6964 keypair for the TLS context, rather than making a new one for
6965 each new connections. Oops. (But we were still rotating them
6966 periodically, so it's not so bad.)
6967 - When we were cannibalizing a circuit with a particular exit
6968 node in mind, we weren't checking to see if that exit node was
6969 already present earlier in the circuit. Oops.
6970 - When a Tor server's IP changes (e.g. from a dyndns address),
6971 upload a new descriptor so clients will learn too.
6972 - Really busy servers were keeping enough circuits open on stable
6973 connections that they were wrapping around the circuit_id
6974 space. (It's only two bytes.) This exposed a bug where we would
6975 feel free to reuse a circuit_id even if it still exists but has
6976 been marked for close. Try to fix this bug. Some bug remains.
6977 - If we would close a stream early (e.g. it asks for a .exit that
6978 we know would refuse it) but the LeaveStreamsUnattached config
6979 option is set by the controller, then don't close it.
6981 o Bugfixes on 0.1.1.8-alpha:
6982 - Fix a big pile of memory leaks, some of them serious.
6983 - Do not try to download a routerdesc if we would immediately reject
6985 - Resume inserting a newline between all router descriptors when
6986 generating (old style) signed directories, since our spec says
6988 - When providing content-type application/octet-stream for
6989 server descriptors using .z, we were leaving out the
6990 content-encoding header. Oops. (Everything tolerated this just
6991 fine, but that doesn't mean we need to be part of the problem.)
6992 - Fix a potential seg fault in getconf and getinfo using version 1
6993 of the controller protocol.
6994 - Avoid crash: do not check whether DirPort is reachable when we
6995 are suppressing it because of hibernation.
6996 - Make --hash-password not crash on exit.
6999 Changes in version 0.1.1.8-alpha - 2005-10-07
7000 o New features (major):
7001 - Clients don't download or use the directory anymore. Now they
7002 download and use network-statuses from the trusted dirservers,
7003 and fetch individual server descriptors as needed from mirrors.
7004 See dir-spec.txt for all the gory details.
7005 - Be more conservative about whether to advertise our DirPort.
7006 The main change is to not advertise if we're running at capacity
7007 and either a) we could hibernate or b) our capacity is low and
7008 we're using a default DirPort.
7009 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
7011 o New features (minor):
7012 - Try to be smart about when to retry network-status and
7013 server-descriptor fetches. Still needs some tuning.
7014 - Stop parsing, storing, or using running-routers output (but
7015 mirrors still cache and serve it).
7016 - Consider a threshold of versioning dirservers (dirservers who have
7017 an opinion about which Tor versions are still recommended) before
7018 deciding whether to warn the user that he's obsolete.
7019 - Dirservers can now reject/invalidate by key and IP, with the
7020 config options "AuthDirInvalid" and "AuthDirReject". This is
7021 useful since currently we automatically list servers as running
7022 and usable even if we know they're jerks.
7023 - Provide dire warnings to any users who set DirServer; move it out
7024 of torrc.sample and into torrc.complete.
7025 - Add MyFamily to torrc.sample in the server section.
7026 - Add nicknames to the DirServer line, so we can refer to them
7027 without requiring all our users to memorize their IP addresses.
7028 - When we get an EOF or a timeout on a directory connection, note
7029 how many bytes of serverdesc we are dropping. This will help
7030 us determine whether it is smart to parse incomplete serverdesc
7032 - Add a new function to "change pseudonyms" -- that is, to stop
7033 using any currently-dirty circuits for new streams, so we don't
7034 link new actions to old actions. Currently it's only called on
7035 HUP (or SIGNAL RELOAD).
7036 - On sighup, if UseHelperNodes changed to 1, use new circuits.
7037 - Start using RAND_bytes rather than RAND_pseudo_bytes from
7038 OpenSSL. Also, reseed our entropy every hour, not just at
7039 startup. And entropy in 512-bit chunks, not 160-bit chunks.
7041 o Fixes on 0.1.1.7-alpha:
7042 - Nobody ever implemented EVENT_ADDRMAP for control protocol
7043 version 0, so don't let version 0 controllers ask for it.
7044 - If you requested something with too many newlines via the
7045 v1 controller protocol, you could crash tor.
7046 - Fix a number of memory leaks, including some pretty serious ones.
7047 - Re-enable DirPort testing again, so Tor servers will be willing
7048 to advertise their DirPort if it's reachable.
7049 - On TLS handshake, only check the other router's nickname against
7050 its expected nickname if is_named is set.
7052 o Fixes forward-ported from 0.1.0.15:
7053 - Don't crash when we don't have any spare file descriptors and we
7054 try to spawn a dns or cpu worker.
7055 - Make the numbers in read-history and write-history into uint64s,
7056 so they don't overflow and publish negatives in the descriptor.
7059 - For the OS X package's modified privoxy config file, comment
7060 out the "logfile" line so we don't log everything passed
7062 - We were whining about using socks4 or socks5-with-local-lookup
7063 even when it's an IP in the "virtual" range we designed exactly
7065 - We were leaking some memory every time the client changes IPs.
7066 - Never call free() on tor_malloc()d memory. This will help us
7067 use dmalloc to detect memory leaks.
7068 - Check for named servers when looking them up by nickname;
7069 warn when we'recalling a non-named server by its nickname;
7070 don't warn twice about the same name.
7071 - Try to list MyFamily elements by key, not by nickname, and warn
7072 if we've not heard of the server.
7073 - Make windows platform detection (uname equivalent) smarter.
7074 - It turns out sparc64 doesn't like unaligned access either.
7077 Changes in version 0.1.0.15 - 2005-09-23
7078 o Bugfixes on 0.1.0.x:
7079 - Reject ports 465 and 587 (spam targets) in default exit policy.
7080 - Don't crash when we don't have any spare file descriptors and we
7081 try to spawn a dns or cpu worker.
7082 - Get rid of IgnoreVersion undocumented config option, and make us
7083 only warn, never exit, when we're running an obsolete version.
7084 - Don't try to print a null string when your server finds itself to
7085 be unreachable and the Address config option is empty.
7086 - Make the numbers in read-history and write-history into uint64s,
7087 so they don't overflow and publish negatives in the descriptor.
7088 - Fix a minor memory leak in smartlist_string_remove().
7089 - We were only allowing ourselves to upload a server descriptor at
7090 most every 20 minutes, even if it changed earlier than that.
7091 - Clean up log entries that pointed to old URLs.
7094 Changes in version 0.1.1.7-alpha - 2005-09-14
7095 o Fixes on 0.1.1.6-alpha:
7096 - Exit servers were crashing when people asked them to make a
7097 connection to an address not in their exit policy.
7098 - Looking up a non-existent stream for a v1 control connection would
7100 - Fix a seg fault if we ask a dirserver for a descriptor by
7101 fingerprint but he doesn't know about him.
7102 - SETCONF was appending items to linelists, not clearing them.
7103 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
7104 out and refuse the setconf if it would fail.
7105 - Downgrade the dirserver log messages when whining about
7109 - Add Peter Palfrader's check-tor script to tor/contrib/
7110 It lets you easily check whether a given server (referenced by
7111 nickname) is reachable by you.
7112 - Numerous changes to move towards client-side v2 directories. Not
7116 - If the user gave tor an odd number of command-line arguments,
7117 we were silently ignoring the last one. Now we complain and fail.
7118 [This wins the oldest-bug prize -- this bug has been present since
7119 November 2002, as released in Tor 0.0.0.]
7120 - Do not use unaligned memory access on alpha, mips, or mipsel.
7121 It *works*, but is very slow, so we treat them as if it doesn't.
7122 - Retry directory requests if we fail to get an answer we like
7123 from a given dirserver (we were retrying before, but only if
7124 we fail to connect).
7125 - When writing the RecommendedVersions line, sort them first.
7126 - When the client asked for a rendezvous port that the hidden
7127 service didn't want to provide, we were sending an IP address
7128 back along with the end cell. Fortunately, it was zero. But stop
7130 - Correct "your server is reachable" log entries to indicate that
7131 it was self-testing that told us so.
7134 Changes in version 0.1.1.6-alpha - 2005-09-09
7135 o Fixes on 0.1.1.5-alpha:
7136 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
7137 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
7138 - Fix bug with tor_memmem finding a match at the end of the string.
7139 - Make unit tests run without segfaulting.
7140 - Resolve some solaris x86 compile warnings.
7141 - Handle duplicate lines in approved-routers files without warning.
7142 - Fix bug where as soon as a server refused any requests due to his
7143 exit policy (e.g. when we ask for localhost and he tells us that's
7144 127.0.0.1 and he won't do it), we decided he wasn't obeying his
7145 exit policy using him for any exits.
7146 - Only do openssl hardware accelerator stuff if openssl version is
7149 o New controller features/fixes:
7150 - Add a "RESETCONF" command so you can set config options like
7151 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
7152 a config option in the torrc with no value, then it clears it
7153 entirely (rather than setting it to its default).
7154 - Add a "GETINFO config-file" to tell us where torrc is.
7155 - Avoid sending blank lines when GETINFO replies should be empty.
7156 - Add a QUIT command for the controller (for using it manually).
7157 - Fix a bug in SAVECONF that was adding default dirservers and
7158 other redundant entries to the torrc file.
7160 o Start on the new directory design:
7161 - Generate, publish, cache, serve new network-status format.
7162 - Publish individual descriptors (by fingerprint, by "all", and by
7164 - Publish client and server recommended versions separately.
7165 - Allow tor_gzip_uncompress() to handle multiple concatenated
7166 compressed strings. Serve compressed groups of router
7167 descriptors. The compression logic here could be more
7169 - Distinguish v1 authorities (all currently trusted directories)
7170 from v2 authorities (all trusted directories).
7171 - Change DirServers config line to note which dirs are v1 authorities.
7172 - Add configuration option "V1AuthoritativeDirectory 1" which
7173 moria1, moria2, and tor26 should set.
7174 - Remove option when getting directory cache to see whether they
7175 support running-routers; they all do now. Replace it with one
7176 to see whether caches support v2 stuff.
7179 - Dirservers now do their own external reachability testing of each
7180 Tor server, and only list them as running if they've been found to
7181 be reachable. We also send back warnings to the server's logs if
7182 it uploads a descriptor that we already believe is unreachable.
7183 - Implement exit enclaves: if we know an IP address for the
7184 destination, and there's a running Tor server at that address
7185 which allows exit to the destination, then extend the circuit to
7186 that exit first. This provides end-to-end encryption and end-to-end
7187 authentication. Also, if the user wants a .exit address or enclave,
7188 use 4 hops rather than 3, and cannibalize a general circ for it
7190 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
7191 controller. Also, rotate dns and cpu workers if the controller
7192 changes options that will affect them; and initialize the dns
7193 worker cache tree whether or not we start out as a server.
7194 - Only upload a new server descriptor when options change, 18
7195 hours have passed, uptime is reset, or bandwidth changes a lot.
7196 - Check [X-]Forwarded-For headers in HTTP requests when generating
7197 log messages. This lets people run dirservers (and caches) behind
7198 Apache but still know which IP addresses are causing warnings.
7200 o Config option changes:
7201 - Replace (Fascist)Firewall* config options with a new
7202 ReachableAddresses option that understands address policies.
7203 For example, "ReachableAddresses *:80,*:443"
7204 - Get rid of IgnoreVersion undocumented config option, and make us
7205 only warn, never exit, when we're running an obsolete version.
7206 - Make MonthlyAccountingStart config option truly obsolete now.
7209 - Reject ports 465 and 587 in the default exit policy, since
7210 people have started using them for spam too.
7211 - It turns out we couldn't bootstrap a network since we added
7212 reachability detection in 0.1.0.1-rc. Good thing the Tor network
7213 has never gone down. Add an AssumeReachable config option to let
7214 servers and dirservers bootstrap. When we're trying to build a
7215 high-uptime or high-bandwidth circuit but there aren't enough
7216 suitable servers, try being less picky rather than simply failing.
7217 - Our logic to decide if the OR we connected to was the right guy
7218 was brittle and maybe open to a mitm for unverified routers.
7219 - We weren't cannibalizing circuits correctly for
7220 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
7221 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
7222 build those from scratch. This should make hidden services faster.
7223 - Predict required circuits better, with an eye toward making hidden
7224 services faster on the service end.
7225 - Retry streams if the exit node sends back a 'misc' failure. This
7226 should result in fewer random failures. Also, after failing
7227 from resolve failed or misc, reset the num failures, so we give
7228 it a fair shake next time we try.
7229 - Clean up the rendezvous warn log msgs, and downgrade some to info.
7230 - Reduce severity on logs about dns worker spawning and culling.
7231 - When we're shutting down and we do something like try to post a
7232 server descriptor or rendezvous descriptor, don't complain that
7233 we seem to be unreachable. Of course we are, we're shutting down.
7234 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
7235 We don't use them yet, but maybe one day our DNS resolver will be
7236 able to discover them.
7237 - Make ContactInfo mandatory for authoritative directory servers.
7238 - Require server descriptors to list IPv4 addresses -- hostnames
7239 are no longer allowed. This also fixes some potential security
7240 problems with people providing hostnames as their address and then
7241 preferentially resolving them to partition users.
7242 - Change log line for unreachability to explicitly suggest /etc/hosts
7243 as the culprit. Also make it clearer what IP address and ports we're
7244 testing for reachability.
7245 - Put quotes around user-supplied strings when logging so users are
7246 more likely to realize if they add bad characters (like quotes)
7248 - Let auth dir servers start without specifying an Address config
7250 - Make unit tests (and other invocations that aren't the real Tor)
7251 run without launching listeners, creating subdirectories, and so on.
7254 Changes in version 0.1.1.5-alpha - 2005-08-08
7255 o Bugfixes included in 0.1.0.14.
7257 o Bugfixes on 0.1.0.x:
7258 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
7259 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
7260 it would silently using ignore the 6668.
7263 Changes in version 0.1.0.14 - 2005-08-08
7264 o Bugfixes on 0.1.0.x:
7265 - Fix the other half of the bug with crypto handshakes
7267 - Fix an assert trigger if you send a 'signal term' via the
7268 controller when it's listening for 'event info' messages.
7271 Changes in version 0.1.1.4-alpha - 2005-08-04
7272 o Bugfixes included in 0.1.0.13.
7275 - Improve tor_gettimeofday() granularity on windows.
7276 - Make clients regenerate their keys when their IP address changes.
7277 - Implement some more GETINFO goodness: expose helper nodes, config
7278 options, getinfo keys.
7281 Changes in version 0.1.0.13 - 2005-08-04
7282 o Bugfixes on 0.1.0.x:
7283 - Fix a critical bug in the security of our crypto handshakes.
7284 - Fix a size_t underflow in smartlist_join_strings2() that made
7285 it do bad things when you hand it an empty smartlist.
7286 - Fix Windows installer to ship Tor license (thanks to Aphex for
7287 pointing out this oversight) and put a link to the doc directory
7289 - Explicitly set no-unaligned-access for sparc: it turns out the
7290 new gcc's let you compile broken code, but that doesn't make it
7294 Changes in version 0.1.1.3-alpha - 2005-07-23
7295 o Bugfixes on 0.1.1.2-alpha:
7296 - Fix a bug in handling the controller's "post descriptor"
7298 - Fix several bugs in handling the controller's "extend circuit"
7300 - Fix a bug in handling the controller's "stream status" event.
7301 - Fix an assert failure if we have a controller listening for
7302 circuit events and we go offline.
7303 - Re-allow hidden service descriptors to publish 0 intro points.
7304 - Fix a crash when generating your hidden service descriptor if
7305 you don't have enough intro points already.
7307 o New features on 0.1.1.2-alpha:
7308 - New controller function "getinfo accounting", to ask how
7309 many bytes we've used in this time period.
7310 - Experimental support for helper nodes: a lot of the risk from
7311 a small static adversary comes because users pick new random
7312 nodes every time they rebuild a circuit. Now users will try to
7313 stick to the same small set of entry nodes if they can. Not
7314 enabled by default yet.
7316 o Bugfixes on 0.1.0.12:
7317 - If you're an auth dir server, always publish your dirport,
7318 even if you haven't yet found yourself to be reachable.
7319 - Fix a size_t underflow in smartlist_join_strings2() that made
7320 it do bad things when you hand it an empty smartlist.
7323 Changes in version 0.1.0.12 - 2005-07-18
7324 o New directory servers:
7325 - tor26 has changed IP address.
7327 o Bugfixes on 0.1.0.x:
7328 - Fix a possible double-free in tor_gzip_uncompress().
7329 - When --disable-threads is set, do not search for or link against
7331 - Don't trigger an assert if an authoritative directory server
7332 claims its dirport is 0.
7333 - Fix bug with removing Tor as an NT service: some people were
7334 getting "The service did not return an error." Thanks to Matt
7338 Changes in version 0.1.1.2-alpha - 2005-07-15
7339 o New directory servers:
7340 - tor26 has changed IP address.
7342 o Bugfixes on 0.1.0.x, crashes/leaks:
7343 - Port the servers-not-obeying-their-exit-policies fix from
7345 - Fix an fd leak in start_daemon().
7346 - On Windows, you can't always reopen a port right after you've
7347 closed it. So change retry_listeners() to only close and re-open
7348 ports that have changed.
7349 - Fix a possible double-free in tor_gzip_uncompress().
7351 o Bugfixes on 0.1.0.x, usability:
7352 - When tor_socketpair() fails in Windows, give a reasonable
7353 Windows-style errno back.
7354 - Let people type "tor --install" as well as "tor -install" when
7356 want to make it an NT service.
7357 - NT service patch from Matt Edman to improve error messages.
7358 - When the controller asks for a config option with an abbreviated
7359 name, give the full name in our response.
7360 - Correct the man page entry on TrackHostExitsExpire.
7361 - Looks like we were never delivering deflated (i.e. compressed)
7362 running-routers lists, even when asked. Oops.
7363 - When --disable-threads is set, do not search for or link against
7366 o Bugfixes on 0.1.1.x:
7367 - Fix a seg fault with autodetecting which controller version is
7371 - New hidden service descriptor format: put a version in it, and
7372 let people specify introduction/rendezvous points that aren't
7373 in "the directory" (which is subjective anyway).
7374 - Allow the DEBUG controller event to work again. Mark certain log
7375 entries as "don't tell this to controllers", so we avoid cycles.
7378 Changes in version 0.1.0.11 - 2005-06-30
7379 o Bugfixes on 0.1.0.x:
7380 - Fix major security bug: servers were disregarding their
7381 exit policies if clients behaved unexpectedly.
7382 - Make OS X init script check for missing argument, so we don't
7383 confuse users who invoke it incorrectly.
7384 - Fix a seg fault in "tor --hash-password foo".
7385 - The MAPADDRESS control command was broken.
7388 Changes in version 0.1.1.1-alpha - 2005-06-29
7390 - Make OS X init script check for missing argument, so we don't
7391 confuse users who invoke it incorrectly.
7392 - Fix a seg fault in "tor --hash-password foo".
7393 - Fix a possible way to DoS dirservers.
7394 - When we complain that your exit policy implicitly allows local or
7395 private address spaces, name them explicitly so operators can
7397 - Make the log message less scary when all the dirservers are
7398 temporarily unreachable.
7399 - We were printing the number of idle dns workers incorrectly when
7403 - Revised controller protocol (version 1) that uses ascii rather
7404 than binary. Add supporting libraries in python and java so you
7405 can use the controller from your applications without caring how
7407 - Spiffy new support for crypto hardware accelerators. Can somebody
7411 Changes in version 0.0.9.10 - 2005-06-16
7412 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
7413 - Refuse relay cells that claim to have a length larger than the
7414 maximum allowed. This prevents a potential attack that could read
7415 arbitrary memory (e.g. keys) from an exit server's process
7419 Changes in version 0.1.0.10 - 2005-06-14
7420 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
7421 libevent before 1.1a.
7424 Changes in version 0.1.0.9-rc - 2005-06-09
7426 - Reset buf->highwater every time buf_shrink() is called, not just on
7427 a successful shrink. This was causing significant memory bloat.
7428 - Fix buffer overflow when checking hashed passwords.
7429 - Security fix: if seeding the RNG on Win32 fails, quit.
7430 - Allow seeding the RNG on Win32 even when you're not running as
7432 - Disable threading on Solaris too. Something is wonky with it,
7433 cpuworkers, and reentrant libs.
7434 - Reenable the part of the code that tries to flush as soon as an
7435 OR outbuf has a full TLS record available. Perhaps this will make
7436 OR outbufs not grow as huge except in rare cases, thus saving lots
7437 of CPU time plus memory.
7438 - Reject malformed .onion addresses rather then passing them on as
7439 normal web requests.
7440 - Adapt patch from Adam Langley: fix possible memory leak in
7441 tor_lookup_hostname().
7442 - Initialize libevent later in the startup process, so the logs are
7443 already established by the time we start logging libevent warns.
7444 - Use correct errno on win32 if libevent fails.
7445 - Check and warn about known-bad/slow libevent versions.
7446 - Pay more attention to the ClientOnly config option.
7447 - Have torctl.in/tor.sh.in check for location of su binary (needed
7449 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
7450 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
7451 HttpProxyAuthenticator
7452 - Stop warning about sigpipes in the logs. We're going to
7453 pretend that getting these occassionally is normal and fine.
7454 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
7456 installer screens; and don't put stuff into StartupItems unless
7457 the user asks you to.
7458 - Require servers that use the default dirservers to have public IP
7459 addresses. We have too many servers that are configured with private
7460 IPs and their admins never notice the log entries complaining that
7461 their descriptors are being rejected.
7462 - Add OSX uninstall instructions. An actual uninstall script will
7466 Changes in version 0.1.0.8-rc - 2005-05-23
7468 - It turns out that kqueue on OS X 10.3.9 was causing kernel
7469 panics. Disable kqueue on all OS X Tors.
7470 - Fix RPM: remove duplicate line accidentally added to the rpm
7472 - Disable threads on openbsd too, since its gethostaddr is not
7474 - Tolerate libevent 0.8 since it still works, even though it's
7476 - Enable building on Red Hat 9.0 again.
7477 - Allow the middle hop of the testing circuit to be running any
7478 version, now that most of them have the bugfix to let them connect
7479 to unknown servers. This will allow reachability testing to work
7480 even when 0.0.9.7-0.0.9.9 become obsolete.
7481 - Handle relay cells with rh.length too large. This prevents
7482 a potential attack that could read arbitrary memory (maybe even
7483 keys) from the exit server's process.
7484 - We screwed up the dirport reachability testing when we don't yet
7485 have a cached version of the directory. Hopefully now fixed.
7486 - Clean up router_load_single_router() (used by the controller),
7487 so it doesn't seg fault on error.
7488 - Fix a minor memory leak when somebody establishes an introduction
7489 point at your Tor server.
7490 - If a socks connection ends because read fails, don't warn that
7491 you're not sending a socks reply back.
7494 - Add HttpProxyAuthenticator config option too, that works like
7495 the HttpsProxyAuthenticator config option.
7496 - Encode hashed controller passwords in hex instead of base64,
7497 to make it easier to write controllers.
7500 Changes in version 0.1.0.7-rc - 2005-05-17
7502 - Fix a bug in the OS X package installer that prevented it from
7503 installing on Tiger.
7504 - Fix a script bug in the OS X package installer that made it
7505 complain during installation.
7506 - Find libevent even if it's hiding in /usr/local/ and your
7507 CFLAGS and LDFLAGS don't tell you to look there.
7508 - Be able to link with libevent as a shared library (the default
7509 after 1.0d), even if it's hiding in /usr/local/lib and even
7510 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
7511 assuming you're running gcc. Otherwise fail and give a useful
7513 - Fix a bug in the RPM packager: set home directory for _tor to
7514 something more reasonable when first installing.
7515 - Free a minor amount of memory that is still reachable on exit.
7518 Changes in version 0.1.0.6-rc - 2005-05-14
7520 - Implement --disable-threads configure option. Disable threads on
7521 netbsd by default, because it appears to have no reentrant resolver
7523 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
7524 release (1.1) detects and disables kqueue if it's broken.
7525 - Append default exit policy before checking for implicit internal
7526 addresses. Now we don't log a bunch of complaints on startup
7527 when using the default exit policy.
7528 - Some people were putting "Address " in their torrc, and they had
7529 a buggy resolver that resolved " " to 0.0.0.0. Oops.
7530 - If DataDir is ~/.tor, and that expands to /.tor, then default to
7531 LOCALSTATEDIR/tor instead.
7532 - Fix fragmented-message bug in TorControl.py.
7533 - Resolve a minor bug which would prevent unreachable dirports
7534 from getting suppressed in the published descriptor.
7535 - When the controller gave us a new descriptor, we weren't resolving
7536 it immediately, so Tor would think its address was 0.0.0.0 until
7537 we fetched a new directory.
7538 - Fix an uppercase/lowercase case error in suppressing a bogus
7539 libevent warning on some Linuxes.
7542 - Begin scrubbing sensitive strings from logs by default. Turn off
7543 the config option SafeLogging if you need to do debugging.
7544 - Switch to a new buffer management algorithm, which tries to avoid
7545 reallocing and copying quite as much. In first tests it looks like
7546 it uses *more* memory on average, but less cpu.
7547 - First cut at support for "create-fast" cells. Clients can use
7548 these when extending to their first hop, since the TLS already
7549 provides forward secrecy and authentication. Not enabled on
7551 - When dirservers refuse a router descriptor, we now log its
7552 contactinfo, platform, and the poster's IP address.
7553 - Call tor_free_all instead of connections_free_all after forking, to
7554 save memory on systems that need to fork.
7555 - Whine at you if you're a server and you don't set your contactinfo.
7556 - Implement --verify-config command-line option to check if your torrc
7557 is valid without actually launching Tor.
7558 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
7559 rather than just rejecting it.
7562 Changes in version 0.1.0.5-rc - 2005-04-27
7564 - Stop trying to print a null pointer if an OR conn fails because
7565 we didn't like its cert.
7567 - Switch our internal buffers implementation to use a ring buffer,
7568 to hopefully improve performance for fast servers a lot.
7569 - Add HttpsProxyAuthenticator support (basic auth only), based
7570 on patch from Adam Langley.
7571 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
7572 the fast servers that have been joining lately.
7573 - Give hidden service accesses extra time on the first attempt,
7574 since 60 seconds is often only barely enough. This might improve
7576 - Improve performance for dirservers: stop re-parsing the whole
7577 directory every time you regenerate it.
7578 - Add more debugging info to help us find the weird dns freebsd
7579 pthreads bug; cleaner debug messages to help track future issues.
7582 Changes in version 0.0.9.9 - 2005-04-23
7583 o Bugfixes on 0.0.9.x:
7584 - If unofficial Tor clients connect and send weird TLS certs, our
7585 Tor server triggers an assert. This release contains a minimal
7586 backport from the broader fix that we put into 0.1.0.4-rc.
7589 Changes in version 0.1.0.4-rc - 2005-04-23
7591 - If unofficial Tor clients connect and send weird TLS certs, our
7592 Tor server triggers an assert. Stop asserting, and start handling
7593 TLS errors better in other situations too.
7594 - When the controller asks us to tell it about all the debug-level
7595 logs, it turns out we were generating debug-level logs while
7596 telling it about them, which turns into a bad loop. Now keep
7597 track of whether you're sending a debug log to the controller,
7598 and don't log when you are.
7599 - Fix the "postdescriptor" feature of the controller interface: on
7600 non-complete success, only say "done" once.
7602 - Clients are now willing to load balance over up to 2mB, not 1mB,
7603 of advertised bandwidth capacity.
7604 - Add a NoPublish config option, so you can be a server (e.g. for
7605 testing running Tor servers in other Tor networks) without
7606 publishing your descriptor to the primary dirservers.
7609 Changes in version 0.1.0.3-rc - 2005-04-08
7610 o Improvements on 0.1.0.2-rc:
7611 - Client now retries when streams end early for 'hibernating' or
7612 'resource limit' reasons, rather than failing them.
7613 - More automated handling for dirserver operators:
7614 - Automatically approve nodes running 0.1.0.2-rc or later,
7615 now that the the reachability detection stuff is working.
7616 - Now we allow two unverified servers with the same nickname
7617 but different keys. But if a nickname is verified, only that
7618 nickname+key are allowed.
7619 - If you're an authdirserver connecting to an address:port,
7620 and it's not the OR you were expecting, forget about that
7621 descriptor. If he *was* the one you were expecting, then forget
7622 about all other descriptors for that address:port.
7623 - Allow servers to publish descriptors from 12 hours in the future.
7624 Corollary: only whine about clock skew from the dirserver if
7625 he's a trusted dirserver (since now even verified servers could
7626 have quite wrong clocks).
7627 - Adjust maximum skew and age for rendezvous descriptors: let skew
7628 be 48 hours rather than 90 minutes.
7629 - Efficiency improvements:
7630 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
7631 it much faster to look up a circuit for each relay cell.
7632 - Remove most calls to assert_all_pending_dns_resolves_ok(),
7633 since they're eating our cpu on exit nodes.
7634 - Stop wasting time doing a case insensitive comparison for every
7635 dns name every time we do any lookup. Canonicalize the names to
7636 lowercase and be done with it.
7637 - Start sending 'truncated' cells back rather than destroy cells,
7638 if the circuit closes in front of you. This means we won't have
7639 to abandon partially built circuits.
7640 - Only warn once per nickname from add_nickname_list_to_smartlist
7641 per failure, so an entrynode or exitnode choice that's down won't
7643 - Put a note in the torrc about abuse potential with the default
7645 - Revise control spec and implementation to allow all log messages to
7646 be sent to controller with their severities intact (suggested by
7647 Matt Edman). Update TorControl to handle new log event types.
7648 - Provide better explanation messages when controller's POSTDESCRIPTOR
7650 - Stop putting nodename in the Platform string in server descriptors.
7651 It doesn't actually help, and it is confusing/upsetting some people.
7653 o Bugfixes on 0.1.0.2-rc:
7654 - We were printing the host mask wrong in exit policies in server
7655 descriptors. This isn't a critical bug though, since we were still
7656 obeying the exit policy internally.
7657 - Fix Tor when compiled with libevent but without pthreads: move
7658 connection_unregister() from _connection_free() to
7660 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
7661 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
7662 when we look through the connection array, we'll find any of the
7663 cpu/dnsworkers. This is no good.
7665 o Bugfixes on 0.0.9.8:
7666 - Fix possible bug on threading platforms (e.g. win32) which was
7667 leaking a file descriptor whenever a cpuworker or dnsworker died.
7668 - When using preferred entry or exit nodes, ignore whether the
7669 circuit wants uptime or capacity. They asked for the nodes, they
7671 - chdir() to your datadirectory at the *end* of the daemonize process,
7672 not the beginning. This was a problem because the first time you
7673 run tor, if your datadir isn't there, and you have runasdaemon set
7674 to 1, it will try to chdir to it before it tries to create it. Oops.
7675 - Handle changed router status correctly when dirserver reloads
7676 fingerprint file. We used to be dropping all unverified descriptors
7677 right then. The bug was hidden because we would immediately
7678 fetch a directory from another dirserver, which would include the
7679 descriptors we just dropped.
7680 - When we're connecting to an OR and he's got a different nickname/key
7681 than we were expecting, only complain loudly if we're an OP or a
7682 dirserver. Complaining loudly to the OR admins just confuses them.
7683 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
7684 artificially capped at 500kB.
7687 Changes in version 0.0.9.8 - 2005-04-07
7688 o Bugfixes on 0.0.9.x:
7689 - We have a bug that I haven't found yet. Sometimes, very rarely,
7690 cpuworkers get stuck in the 'busy' state, even though the cpuworker
7691 thinks of itself as idle. This meant that no new circuits ever got
7692 established. Here's a workaround to kill any cpuworker that's been
7693 busy for more than 100 seconds.
7696 Changes in version 0.1.0.2-rc - 2005-04-01
7697 o Bugfixes on 0.1.0.1-rc:
7698 - Fixes on reachability detection:
7699 - Don't check for reachability while hibernating.
7700 - If ORPort is reachable but DirPort isn't, still publish the
7701 descriptor, but zero out DirPort until it's found reachable.
7702 - When building testing circs for ORPort testing, use only
7703 high-bandwidth nodes, so fewer circuits fail.
7704 - Complain about unreachable ORPort separately from unreachable
7705 DirPort, so the user knows what's going on.
7706 - Make sure we only conclude ORPort reachability if we didn't
7707 initiate the conn. Otherwise we could falsely conclude that
7708 we're reachable just because we connected to the guy earlier
7709 and he used that same pipe to extend to us.
7710 - Authdirservers shouldn't do ORPort reachability detection,
7711 since they're in clique mode, so it will be rare to find a
7712 server not already connected to them.
7713 - When building testing circuits, always pick middle hops running
7714 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
7715 bug. (This is a kludge; it will go away when 0.0.9.x becomes
7717 - When we decide we're reachable, actually publish our descriptor
7719 - Fix bug in redirectstream in the controller.
7720 - Fix the state descriptor strings so logs don't claim edge streams
7721 are in a different state than they actually are.
7722 - Use recent libevent features when possible (this only really affects
7723 win32 and osx right now, because the new libevent with these
7724 features hasn't been released yet). Add code to suppress spurious
7726 - Prevent possible segfault in connection_close_unattached_ap().
7727 - Fix newlines on torrc in win32.
7728 - Improve error msgs when tor-resolve fails.
7730 o Improvements on 0.0.9.x:
7731 - New experimental script tor/contrib/ExerciseServer.py (needs more
7732 work) that uses the controller interface to build circuits and
7733 fetch pages over them. This will help us bootstrap servers that
7734 have lots of capacity but haven't noticed it yet.
7735 - New experimental script tor/contrib/PathDemo.py (needs more work)
7736 that uses the controller interface to let you choose whole paths
7738 "<hostname>.<path,separated by dots>.<length of path>.path"
7739 - When we've connected to an OR and handshaked but didn't like
7740 the result, we were closing the conn without sending destroy
7741 cells back for pending circuits. Now send those destroys.
7744 Changes in version 0.0.9.7 - 2005-04-01
7745 o Bugfixes on 0.0.9.x:
7746 - Fix another race crash bug (thanks to Glenn Fink for reporting).
7747 - Compare identity to identity, not to nickname, when extending to
7748 a router not already in the directory. This was preventing us from
7749 extending to unknown routers. Oops.
7750 - Make sure to create OS X Tor user in <500 range, so we aren't
7751 creating actual system users.
7752 - Note where connection-that-hasn't-sent-end was marked, and fix
7753 a few really loud instances of this harmless bug (it's fixed more
7757 Changes in version 0.1.0.1-rc - 2005-03-28
7759 - Add reachability testing. Your Tor server will automatically try
7760 to see if its ORPort and DirPort are reachable from the outside,
7761 and it won't upload its descriptor until it decides they are.
7762 - Handle unavailable hidden services better. Handle slow or busy
7763 hidden services better.
7764 - Add support for CONNECTing through https proxies, with "HttpsProxy"
7766 - New exit policy: accept most low-numbered ports, rather than
7767 rejecting most low-numbered ports.
7768 - More Tor controller support (still experimental). See
7769 http://tor.eff.org/doc/control-spec.txt for all the new features,
7770 including signals to emulate unix signals from any platform;
7771 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
7772 closestream; closecircuit; etc.
7773 - Make nt services work and start on startup on win32 (based on
7774 patch by Matt Edman).
7775 - Add a new AddressMap config directive to rewrite incoming socks
7776 addresses. This lets you, for example, declare an implicit
7777 required exit node for certain sites.
7778 - Add a new TrackHostExits config directive to trigger addressmaps
7779 for certain incoming socks addresses -- for sites that break when
7780 your exit keeps changing (based on patch by Mike Perry).
7781 - Redo the client-side dns cache so it's just an addressmap too.
7782 - Notice when our IP changes, and reset stats/uptime/reachability.
7783 - When an application is using socks5, give him the whole variety of
7784 potential socks5 responses (connect refused, host unreachable, etc),
7785 rather than just "success" or "failure".
7786 - A more sane version numbering system. See
7787 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
7788 - New contributed script "exitlist": a simple python script to
7789 parse directories and find Tor nodes that exit to listed
7791 - New contributed script "privoxy-tor-toggle" to toggle whether
7792 Privoxy uses Tor. Seems to be configured for Debian by default.
7793 - Report HTTP reasons to client when getting a response from directory
7794 servers -- so you can actually know what went wrong.
7795 - New config option MaxAdvertisedBandwidth which lets you advertise
7796 a low bandwidthrate (to not attract as many circuits) while still
7797 allowing a higher bandwidthrate in reality.
7799 o Robustness/stability fixes:
7800 - Make Tor use Niels Provos's libevent instead of its current
7801 poll-but-sometimes-select mess. This will let us use faster async
7802 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
7804 - pthread support now too. This was forced because when we forked,
7805 we ended up wasting a lot of duplicate ram over time. Also switch
7806 to foo_r versions of some library calls to allow reentry and
7808 - Better handling for heterogeneous / unreliable nodes:
7809 - Annotate circuits w/ whether they aim to contain high uptime nodes
7810 and/or high capacity nodes. When building circuits, choose
7812 - This means that every single node in an intro rend circuit,
7813 not just the last one, will have a minimum uptime.
7814 - New config option LongLivedPorts to indicate application streams
7815 that will want high uptime circuits.
7816 - Servers reset uptime when a dir fetch entirely fails. This
7817 hopefully reflects stability of the server's network connectivity.
7818 - If somebody starts his tor server in Jan 2004 and then fixes his
7819 clock, don't make his published uptime be a year.
7820 - Reset published uptime when you wake up from hibernation.
7821 - Introduce a notion of 'internal' circs, which are chosen without
7822 regard to the exit policy of the last hop. Intro and rendezvous
7823 circs must be internal circs, to avoid leaking information. Resolve
7824 and connect streams can use internal circs if they want.
7825 - New circuit pooling algorithm: make sure to have enough circs around
7826 to satisfy any predicted ports, and also make sure to have 2 internal
7827 circs around if we've required internal circs lately (and with high
7828 uptime if we've seen that lately too).
7829 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
7830 which describes how often we retry making new circuits if current
7831 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
7832 how long we're willing to make use of an already-dirty circuit.
7833 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
7834 circ as necessary, if there are any completed ones lying around
7835 when we try to launch one.
7836 - Make hidden services try to establish a rendezvous for 30 seconds,
7837 rather than for n (where n=3) attempts to build a circuit.
7838 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
7839 "ShutdownWaitLength".
7840 - Try to be more zealous about calling connection_edge_end when
7841 things go bad with edge conns in connection.c.
7842 - Revise tor-spec to add more/better stream end reasons.
7843 - Revise all calls to connection_edge_end to avoid sending "misc",
7844 and to take errno into account where possible.
7847 - Fix a race condition that can trigger an assert, when we have a
7848 pending create cell and an OR connection fails right then.
7849 - Fix several double-mark-for-close bugs, e.g. where we were finding
7850 a conn for a cell even if that conn is already marked for close.
7851 - Make sequence of log messages when starting on win32 with no config
7852 file more reasonable.
7853 - When choosing an exit node for a new non-internal circ, don't take
7854 into account whether it'll be useful for any pending x.onion
7855 addresses -- it won't.
7856 - Turn addr_policy_compare from a tristate to a quadstate; this should
7857 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
7858 for google.com" problem.
7859 - Make "platform" string in descriptor more accurate for Win32 servers,
7860 so it's not just "unknown platform".
7861 - Fix an edge case in parsing config options (thanks weasel).
7862 If they say "--" on the commandline, it's not an option.
7863 - Reject odd-looking addresses at the client (e.g. addresses that
7864 contain a colon), rather than having the server drop them because
7866 - tor-resolve requests were ignoring .exit if there was a working circuit
7867 they could use instead.
7868 - REUSEADDR on normal platforms means you can rebind to the port
7869 right after somebody else has let it go. But REUSEADDR on win32
7870 means to let you bind to the port _even when somebody else
7871 already has it bound_! So, don't do that on Win32.
7872 - Change version parsing logic: a version is "obsolete" if it is not
7873 recommended and (1) there is a newer recommended version in the
7874 same series, or (2) there are no recommended versions in the same
7875 series, but there are some recommended versions in a newer series.
7876 A version is "new" if it is newer than any recommended version in
7878 - Stop most cases of hanging up on a socks connection without sending
7882 - Require BandwidthRate to be at least 20kB/s for servers.
7883 - When a dirserver causes you to give a warn, mention which dirserver
7885 - New config option DirAllowPrivateAddresses for authdirservers.
7886 Now by default they refuse router descriptors that have non-IP or
7887 private-IP addresses.
7888 - Stop publishing socksport in the directory, since it's not
7889 actually meant to be public. For compatibility, publish a 0 there
7891 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
7892 smart" value, that is low for servers and high for clients.
7893 - If our clock jumps forward by 100 seconds or more, assume something
7894 has gone wrong with our network and abandon all not-yet-used circs.
7895 - Warn when exit policy implicitly allows local addresses.
7896 - If we get an incredibly skewed timestamp from a dirserver mirror
7897 that isn't a verified OR, don't warn -- it's probably him that's
7899 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
7900 cookies to disk and doesn't log each web request to disk. (Thanks
7901 to Brett Carrington for pointing this out.)
7902 - When a client asks us for a dir mirror and we don't have one,
7903 launch an attempt to get a fresh one.
7904 - If we're hibernating and we get a SIGINT, exit immediately.
7905 - Add --with-dmalloc ./configure option, to track memory leaks.
7906 - And try to free all memory on closing, so we can detect what
7908 - Cache local dns resolves correctly even when they're .exit
7910 - Give a better warning when some other server advertises an
7911 ORPort that is actually an apache running ssl.
7912 - Add "opt hibernating 1" to server descriptor to make it clearer
7913 whether the server is hibernating.
7916 Changes in version 0.0.9.6 - 2005-03-24
7917 o Bugfixes on 0.0.9.x (crashes and asserts):
7918 - Add new end stream reasons to maintainance branch. Fix bug where
7919 reason (8) could trigger an assert. Prevent bug from recurring.
7920 - Apparently win32 stat wants paths to not end with a slash.
7921 - Fix assert triggers in assert_cpath_layer_ok(), where we were
7922 blowing away the circuit that conn->cpath_layer points to, then
7923 checking to see if the circ is well-formed. Backport check to make
7924 sure we dont use the cpath on a closed connection.
7925 - Prevent circuit_resume_edge_reading_helper() from trying to package
7926 inbufs for marked-for-close streams.
7927 - Don't crash on hup if your options->address has become unresolvable.
7928 - Some systems (like OS X) sometimes accept() a connection and tell
7929 you the remote host is 0.0.0.0:0. If this happens, due to some
7930 other mis-features, we get confused; so refuse the conn for now.
7932 o Bugfixes on 0.0.9.x (other):
7933 - Fix harmless but scary "Unrecognized content encoding" warn message.
7934 - Add new stream error reason: TORPROTOCOL reason means "you are not
7935 speaking a version of Tor I understand; say bye-bye to your stream."
7936 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
7937 into the future, now that we are more tolerant of skew. This
7938 resolves a bug where a Tor server would refuse to cache a directory
7939 because all the directories it gets are too far in the future;
7940 yet the Tor server never logs any complaints about clock skew.
7941 - Mac packaging magic: make man pages useable, and do not overwrite
7942 existing torrc files.
7943 - Make OS X log happily to /var/log/tor/tor.log
7946 Changes in version 0.0.9.5 - 2005-02-22
7947 o Bugfixes on 0.0.9.x:
7948 - Fix an assert race at exit nodes when resolve requests fail.
7949 - Stop picking unverified dir mirrors--it only leads to misery.
7950 - Patch from Matt Edman to make NT services work better. Service
7951 support is still not compiled into the executable by default.
7952 - Patch from Dmitri Bely so the Tor service runs better under
7953 the win32 SYSTEM account.
7954 - Make tor-resolve actually work (?) on Win32.
7955 - Fix a sign bug when getrlimit claims to have 4+ billion
7956 file descriptors available.
7957 - Stop refusing to start when bandwidthburst == bandwidthrate.
7958 - When create cells have been on the onion queue more than five
7959 seconds, just send back a destroy and take them off the list.
7962 Changes in version 0.0.9.4 - 2005-02-03
7963 o Bugfixes on 0.0.9:
7964 - Fix an assert bug that took down most of our servers: when
7965 a server claims to have 1 GB of bandwidthburst, don't
7967 - Don't crash as badly if we have spawned the max allowed number
7968 of dnsworkers, or we're out of file descriptors.
7969 - Block more file-sharing ports in the default exit policy.
7970 - MaxConn is now automatically set to the hard limit of max
7971 file descriptors we're allowed (ulimit -n), minus a few for
7973 - Give a clearer message when servers need to raise their
7974 ulimit -n when they start running out of file descriptors.
7975 - SGI Compatibility patches from Jan Schaumann.
7976 - Tolerate a corrupt cached directory better.
7977 - When a dirserver hasn't approved your server, list which one.
7978 - Go into soft hibernation after 95% of the bandwidth is used,
7979 not 99%. This is especially important for daily hibernators who
7980 have a small accounting max. Hopefully it will result in fewer
7981 cut connections when the hard hibernation starts.
7982 - Load-balance better when using servers that claim more than
7983 800kB/s of capacity.
7984 - Make NT services work (experimental, only used if compiled in).
7987 Changes in version 0.0.9.3 - 2005-01-21
7988 o Bugfixes on 0.0.9:
7989 - Backport the cpu use fixes from main branch, so busy servers won't
7990 need as much processor time.
7991 - Work better when we go offline and then come back, or when we
7992 run Tor at boot before the network is up. We do this by
7993 optimistically trying to fetch a new directory whenever an
7994 application request comes in and we think we're offline -- the
7995 human is hopefully a good measure of when the network is back.
7996 - Backport some minimal hidserv bugfixes: keep rend circuits open as
7997 long as you keep using them; actually publish hidserv descriptors
7998 shortly after they change, rather than waiting 20-40 minutes.
7999 - Enable Mac startup script by default.
8000 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
8001 - When you update AllowUnverifiedNodes or FirewallPorts via the
8002 controller's setconf feature, we were always appending, never
8004 - When you update HiddenServiceDir via setconf, it was screwing up
8005 the order of reading the lines, making it fail.
8006 - Do not rewrite a cached directory back to the cache; otherwise we
8007 will think it is recent and not fetch a newer one on startup.
8008 - Workaround for webservers that lie about Content-Encoding: Tor
8009 now tries to autodetect compressed directories and compression
8010 itself. This lets us Proxypass dir fetches through apache.
8013 Changes in version 0.0.9.2 - 2005-01-04
8014 o Bugfixes on 0.0.9 (crashes and asserts):
8015 - Fix an assert on startup when the disk is full and you're logging
8017 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
8018 style address, then we'd crash.
8019 - Fix an assert trigger when the running-routers string we get from
8020 a dirserver is broken.
8021 - Make worker threads start and run on win32. Now win32 servers
8023 - Bandaid (not actually fix, but now it doesn't crash) an assert
8024 where the dns worker dies mysteriously and the main Tor process
8025 doesn't remember anything about the address it was resolving.
8027 o Bugfixes on 0.0.9 (Win32):
8028 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
8029 name out of the warning/assert messages.
8030 - Fix a superficial "unhandled error on read" bug on win32.
8031 - The win32 installer no longer requires a click-through for our
8032 license, since our Free Software license grants rights but does not
8034 - Win32: When connecting to a dirserver fails, try another one
8035 immediately. (This was already working for non-win32 Tors.)
8036 - Stop trying to parse $HOME on win32 when hunting for default
8038 - Make tor-resolve.c work on win32 by calling network_init().
8040 o Bugfixes on 0.0.9 (other):
8041 - Make 0.0.9.x build on Solaris again.
8042 - Due to a fencepost error, we were blowing away the \n when reporting
8043 confvalue items in the controller. So asking for multiple config
8044 values at once couldn't work.
8045 - When listing circuits that are pending on an opening OR connection,
8046 if we're an OR we were listing circuits that *end* at us as
8047 being pending on every listener, dns/cpu worker, etc. Stop that.
8048 - Dirservers were failing to create 'running-routers' or 'directory'
8049 strings if we had more than some threshold of routers. Fix them so
8050 they can handle any number of routers.
8051 - Fix a superficial "Duplicate mark for close" bug.
8052 - Stop checking for clock skew for OR connections, even for servers.
8053 - Fix a fencepost error that was chopping off the last letter of any
8054 nickname that is the maximum allowed nickname length.
8055 - Update URLs in log messages so they point to the new website.
8056 - Fix a potential problem in mangling server private keys while
8057 writing to disk (not triggered yet, as far as we know).
8058 - Include the licenses for other free software we include in Tor,
8059 now that we're shipping binary distributions more regularly.
8062 Changes in version 0.0.9.1 - 2004-12-15
8063 o Bugfixes on 0.0.9:
8064 - Make hibernation actually work.
8065 - Make HashedControlPassword config option work.
8066 - When we're reporting event circuit status to a controller,
8067 don't use the stream status code.
8070 Changes in version 0.0.9 - 2004-12-12
8072 - Clean up manpage and torrc.sample file.
8073 - Clean up severities and text of log warnings.
8075 - Make servers trigger an assert when they enter hibernation.
8078 Changes in version 0.0.9rc7 - 2004-12-08
8079 o Bugfixes on 0.0.9rc:
8080 - Fix a stack-trashing crash when an exit node begins hibernating.
8081 - Avoid looking at unallocated memory while considering which
8082 ports we need to build circuits to cover.
8083 - Stop a sigpipe: when an 'end' cell races with eof from the app,
8084 we shouldn't hold-open-until-flush if the eof arrived first.
8085 - Fix a bug with init_cookie_authentication() in the controller.
8086 - When recommending new-format log lines, if the upper bound is
8087 LOG_ERR, leave it implicit.
8089 o Bugfixes on 0.0.8.1:
8090 - Fix a whole slew of memory leaks.
8091 - Fix isspace() and friends so they still make Solaris happy
8092 but also so they don't trigger asserts on win32.
8093 - Fix parse_iso_time on platforms without strptime (eg win32).
8094 - win32: tolerate extra "readable" events better.
8095 - win32: when being multithreaded, leave parent fdarray open.
8096 - Make unit tests work on win32.
8099 Changes in version 0.0.9rc6 - 2004-12-06
8100 o Bugfixes on 0.0.9pre:
8101 - Clean up some more integer underflow opportunities (not exploitable
8103 - While hibernating, hup should not regrow our listeners.
8104 - Send an end to the streams we close when we hibernate, rather
8105 than just chopping them off.
8106 - React to eof immediately on non-open edge connections.
8108 o Bugfixes on 0.0.8.1:
8109 - Calculate timeout for waiting for a connected cell from the time
8110 we sent the begin cell, not from the time the stream started. If
8111 it took a long time to establish the circuit, we would time out
8112 right after sending the begin cell.
8113 - Fix router_compare_addr_to_addr_policy: it was not treating a port
8114 of * as always matching, so we were picking reject *:* nodes as
8115 exit nodes too. Oops.
8118 - New circuit building strategy: keep a list of ports that we've
8119 used in the past 6 hours, and always try to have 2 circuits open
8120 or on the way that will handle each such port. Seed us with port
8121 80 so web users won't complain that Tor is "slow to start up".
8122 - Make kill -USR1 dump more useful stats about circuits.
8123 - When warning about retrying or giving up, print the address, so
8124 the user knows which one it's talking about.
8125 - If you haven't used a clean circuit in an hour, throw it away,
8126 just to be on the safe side. (This means after 6 hours a totally
8127 unused Tor client will have no circuits open.)
8130 Changes in version 0.0.9rc5 - 2004-12-01
8131 o Bugfixes on 0.0.8.1:
8132 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
8133 - Let resolve conns retry/expire also, rather than sticking around
8135 - If we are using select, make sure we stay within FD_SETSIZE.
8137 o Bugfixes on 0.0.9pre:
8138 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
8139 but doesn't seem to be currently; thanks to Ilja van Sprundel for
8141 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
8142 instead. Impose minima and maxima for all *Period options; impose
8143 even tighter maxima for fetching if we are a caching dirserver.
8144 Clip rather than rejecting.
8145 - Fetch cached running-routers from servers that serve it (that is,
8146 authdirservers and servers running 0.0.9rc5-cvs or later.)
8149 - Accept *:706 (silc) in default exit policy.
8150 - Implement new versioning format for post 0.1.
8151 - Support "foo.nickname.exit" addresses, to let Alice request the
8152 address "foo" as viewed by exit node "nickname". Based on a patch
8154 - Make tor --version --version dump the cvs Id of every file.
8157 Changes in version 0.0.9rc4 - 2004-11-28
8158 o Bugfixes on 0.0.8.1:
8159 - Make windows sockets actually non-blocking (oops), and handle
8160 win32 socket errors better.
8162 o Bugfixes on 0.0.9rc1:
8163 - Actually catch the -USR2 signal.
8166 Changes in version 0.0.9rc3 - 2004-11-25
8167 o Bugfixes on 0.0.8.1:
8168 - Flush the log file descriptor after we print "Tor opening log file",
8169 so we don't see those messages days later.
8171 o Bugfixes on 0.0.9rc1:
8172 - Make tor-resolve work again.
8173 - Avoid infinite loop in tor-resolve if tor hangs up on it.
8174 - Fix an assert trigger for clients/servers handling resolves.
8177 Changes in version 0.0.9rc2 - 2004-11-24
8178 o Bugfixes on 0.0.9rc1:
8179 - I broke socks5 support while fixing the eof bug.
8180 - Allow unitless bandwidths and intervals; they default to bytes
8182 - New servers don't start out hibernating; they are active until
8183 they run out of bytes, so they have a better estimate of how
8184 long it takes, and so their operators can know they're working.
8187 Changes in version 0.0.9rc1 - 2004-11-23
8188 o Bugfixes on 0.0.8.1:
8189 - Finally fix a bug that's been plaguing us for a year:
8190 With high load, circuit package window was reaching 0. Whenever
8191 we got a circuit-level sendme, we were reading a lot on each
8192 socket, but only writing out a bit. So we would eventually reach
8193 eof. This would be noticed and acted on even when there were still
8194 bytes sitting in the inbuf.
8195 - When poll() is interrupted, we shouldn't believe the revents values.
8197 o Bugfixes on 0.0.9pre6:
8198 - Fix hibernate bug that caused pre6 to be broken.
8199 - Don't keep rephist info for routers that haven't had activity for
8200 24 hours. (This matters now that clients have keys, since we track
8202 - Never call close_temp_logs while validating log options.
8203 - Fix backslash-escaping on tor.sh.in and torctl.in.
8206 - Implement weekly/monthly/daily accounting: now you specify your
8207 hibernation properties by
8208 AccountingMax N bytes|KB|MB|GB|TB
8209 AccountingStart day|week|month [day] HH:MM
8210 Defaults to "month 1 0:00".
8211 - Let bandwidth and interval config options be specified as 5 bytes,
8212 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
8213 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
8214 get back to normal.)
8215 - If your requested entry or exit node has advertised bandwidth 0,
8217 - Be more greedy about filling up relay cells -- we try reading again
8218 once we've processed the stuff we read, in case enough has arrived
8219 to fill the last cell completely.
8220 - Apply NT service patch from Osamu Fujino. Still needs more work.
8223 Changes in version 0.0.9pre6 - 2004-11-15
8224 o Bugfixes on 0.0.8.1:
8225 - Fix assert failure on malformed socks4a requests.
8226 - Use identity comparison, not nickname comparison, to choose which
8227 half of circuit-ID-space each side gets to use. This is needed
8228 because sometimes we think of a router as a nickname, and sometimes
8229 as a hex ID, and we can't predict what the other side will do.
8230 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
8231 write() call will fail and we handle it there.
8232 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
8233 and smartlist_len, which are two major profiling offenders.
8235 o Bugfixes on 0.0.9pre5:
8236 - Fix a bug in read_all that was corrupting config files on windows.
8237 - When we're raising the max number of open file descriptors to
8238 'unlimited', don't log that we just raised it to '-1'.
8239 - Include event code with events, as required by control-spec.txt.
8240 - Don't give a fingerprint when clients do --list-fingerprint:
8241 it's misleading, because it will never be the same again.
8242 - Stop using strlcpy in tor_strndup, since it was slowing us
8244 - Remove warn on startup about missing cached-directory file.
8245 - Make kill -USR1 work again.
8246 - Hibernate if we start tor during the "wait for wakeup-time" phase
8247 of an accounting interval. Log our hibernation plans better.
8248 - Authoritative dirservers now also cache their directory, so they
8249 have it on start-up.
8252 - Fetch running-routers; cache running-routers; compress
8253 running-routers; serve compressed running-routers.z
8254 - Add NSI installer script contributed by J Doe.
8255 - Commit VC6 and VC7 workspace/project files.
8256 - Commit a tor.spec for making RPM files, with help from jbash.
8257 - Add contrib/torctl.in contributed by Glenn Fink.
8258 - Implement the control-spec's SAVECONF command, to write your
8259 configuration to torrc.
8260 - Get cookie authentication for the controller closer to working.
8261 - Include control-spec.txt in the tarball.
8262 - When set_conf changes our server descriptor, upload a new copy.
8263 But don't upload it too often if there are frequent changes.
8264 - Document authentication config in man page, and document signals
8266 - Clean up confusing parts of man page and torrc.sample.
8267 - Make expand_filename handle ~ and ~username.
8268 - Use autoconf to enable largefile support where necessary. Use
8269 ftello where available, since ftell can fail at 2GB.
8270 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
8271 log more informatively.
8272 - Give a slightly more useful output for "tor -h".
8273 - Refuse application socks connections to port 0.
8274 - Check clock skew for verified servers, but allow unverified
8275 servers and clients to have any clock skew.
8276 - Break DirFetchPostPeriod into:
8277 - DirFetchPeriod for fetching full directory,
8278 - StatusFetchPeriod for fetching running-routers,
8279 - DirPostPeriod for posting server descriptor,
8280 - RendPostPeriod for posting hidden service descriptors.
8281 - Make sure the hidden service descriptors are at a random offset
8282 from each other, to hinder linkability.
8285 Changes in version 0.0.9pre5 - 2004-11-09
8286 o Bugfixes on 0.0.9pre4:
8287 - Fix a seg fault in unit tests (doesn't affect main program).
8288 - Fix an assert bug where a hidden service provider would fail if
8289 the first hop of his rendezvous circuit was down.
8290 - Hidden service operators now correctly handle version 1 style
8291 INTRODUCE1 cells (nobody generates them still, so not a critical
8293 - If do_hup fails, actually notice.
8294 - Handle more errnos from accept() without closing the listener.
8295 Some OpenBSD machines were closing their listeners because
8296 they ran out of file descriptors.
8297 - Send resolve cells to exit routers that are running a new
8298 enough version of the resolve code to work right.
8299 - Better handling of winsock includes on non-MSV win32 compilers.
8300 - Some people had wrapped their tor client/server in a script
8301 that would restart it whenever it died. This did not play well
8302 with our "shut down if your version is obsolete" code. Now people
8303 don't fetch a new directory if their local cached version is
8305 - Make our autogen.sh work on ksh as well as bash.
8308 - Hibernation: New config option "AccountingMaxKB" lets you
8309 set how many KBytes per month you want to allow your server to
8310 consume. Rather than spreading those bytes out evenly over the
8311 month, we instead hibernate for some of the month and pop up
8312 at a deterministic time, work until the bytes are consumed, then
8313 hibernate again. Config option "MonthlyAccountingStart" lets you
8314 specify which day of the month your billing cycle starts on.
8315 - Control interface: a separate program can now talk to your
8316 client/server over a socket, and get/set config options, receive
8317 notifications of circuits and streams starting/finishing/dying,
8318 bandwidth used, etc. The next step is to get some GUIs working.
8319 Let us know if you want to help out. See doc/control-spec.txt .
8320 - Ship a contrib/tor-control.py as an example script to interact
8321 with the control port.
8322 - "tor --hash-password zzyxz" will output a salted password for
8323 use in authenticating to the control interface.
8324 - New log format in config:
8325 "Log minsev[-maxsev] stdout|stderr|syslog" or
8326 "Log minsev[-maxsev] file /var/foo"
8329 - DirPolicy config option, to let people reject incoming addresses
8330 from their dirserver.
8331 - "tor --list-fingerprint" will list your identity key fingerprint
8333 - Add "pass" target for RedirectExit, to make it easier to break
8334 out of a sequence of RedirectExit rules.
8335 - Clients now generate a TLS cert too, in preparation for having
8336 them act more like real nodes.
8337 - Ship src/win32/ in the tarball, so people can use it to build.
8338 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
8340 - New "router-status" line in directory, to better bind each verified
8341 nickname to its identity key.
8342 - Deprecate unofficial config option abbreviations, and abbreviations
8343 not on the command line.
8344 - Add a pure-C tor-resolve implementation.
8345 - Use getrlimit and friends to ensure we can reach MaxConn (currently
8346 1024) file descriptors.
8348 o Code security improvements, inspired by Ilja:
8349 - Replace sprintf with snprintf. (I think they were all safe, but
8351 - Replace strcpy/strncpy with strlcpy in more places.
8352 - Avoid strcat; use snprintf or strlcat instead.
8353 - snprintf wrapper with consistent (though not C99) overflow behavior.
8356 Changes in version 0.0.9pre4 - 2004-10-17
8357 o Bugfixes on 0.0.9pre3:
8358 - If the server doesn't specify an exit policy, use the real default
8359 exit policy, not reject *:*.
8360 - Ignore fascistfirewall when uploading/downloading hidden service
8361 descriptors, since we go through Tor for those; and when using
8362 an HttpProxy, since we assume it can reach them all.
8363 - When looking for an authoritative dirserver, use only the ones
8364 configured at boot. Don't bother looking in the directory.
8365 - The rest of the fix for get_default_conf_file() on older win32.
8366 - Make 'Routerfile' config option obsolete.
8369 - New 'MyFamily nick1,...' config option for a server to
8370 specify other servers that shouldn't be used in the same circuit
8371 with it. Only believed if nick1 also specifies us.
8372 - New 'NodeFamily nick1,nick2,...' config option for a client to
8373 specify nodes that it doesn't want to use in the same circuit.
8374 - New 'Redirectexit pattern address:port' config option for a
8375 server to redirect exit connections, e.g. to a local squid.
8378 Changes in version 0.0.9pre3 - 2004-10-13
8379 o Bugfixes on 0.0.8.1:
8380 - Better torrc example lines for dirbindaddress and orbindaddress.
8381 - Improved bounds checking on parsed ints (e.g. config options and
8382 the ones we find in directories.)
8383 - Better handling of size_t vs int, so we're more robust on 64
8385 - Fix the rest of the bug where a newly started OR would appear
8386 as unverified even after we've added his fingerprint and hupped
8388 - Fix a bug from 0.0.7: when read() failed on a stream, we would
8389 close it without sending back an end. So 'connection refused'
8390 would simply be ignored and the user would get no response.
8392 o Bugfixes on 0.0.9pre2:
8393 - Serving the cached-on-disk directory to people is bad. We now
8394 provide no directory until we've fetched a fresh one.
8395 - Workaround for bug on windows where cached-directories get crlf
8397 - Make get_default_conf_file() work on older windows too.
8398 - If we write a *:* exit policy line in the descriptor, don't write
8399 any more exit policy lines.
8402 - Use only 0.0.9pre1 and later servers for resolve cells.
8403 - Make the dirservers file obsolete.
8404 - Include a dir-signing-key token in directories to tell the
8405 parsing entity which key is being used to sign.
8406 - Remove the built-in bulky default dirservers string.
8407 - New config option "Dirserver %s:%d [fingerprint]", which can be
8408 repeated as many times as needed. If no dirservers specified,
8409 default to moria1,moria2,tor26.
8410 - Make moria2 advertise a dirport of 80, so people behind firewalls
8411 will be able to get a directory.
8412 - Http proxy support
8413 - Dirservers translate requests for http://%s:%d/x to /x
8414 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
8415 be routed through this host.
8416 - Clients ask for /tor/x rather than /x for new enough dirservers.
8417 This way we can one day coexist peacefully with apache.
8418 - Clients specify a "Host: %s%d" http header, to be compatible
8419 with more proxies, and so running squid on an exit node can work.
8422 Changes in version 0.0.8.1 - 2004-10-13
8424 - Fix a seg fault that can be triggered remotely for Tor
8425 clients/servers with an open dirport.
8426 - Fix a rare assert trigger, where routerinfos for entries in
8427 our cpath would expire while we're building the path.
8428 - Fix a bug in OutboundBindAddress so it (hopefully) works.
8429 - Fix a rare seg fault for people running hidden services on
8430 intermittent connections.
8431 - Fix a bug in parsing opt keywords with objects.
8432 - Fix a stale pointer assert bug when a stream detaches and
8434 - Fix a string format vulnerability (probably not exploitable)
8435 in reporting stats locally.
8436 - Fix an assert trigger: sometimes launching circuits can fail
8437 immediately, e.g. because too many circuits have failed recently.
8438 - Fix a compile warning on 64 bit platforms.
8441 Changes in version 0.0.9pre2 - 2004-10-03
8443 - Make fetching a cached directory work for 64-bit platforms too.
8444 - Make zlib.h a required header, not an optional header.
8447 Changes in version 0.0.9pre1 - 2004-10-01
8449 - Stop using separate defaults for no-config-file and
8450 empty-config-file. Now you have to explicitly turn off SocksPort,
8451 if you don't want it open.
8452 - Fix a bug in OutboundBindAddress so it (hopefully) works.
8453 - Improve man page to mention more of the 0.0.8 features.
8454 - Fix a rare seg fault for people running hidden services on
8455 intermittent connections.
8456 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
8458 - Fix more dns related bugs: send back resolve_failed and end cells
8459 more reliably when the resolve fails, rather than closing the
8460 circuit and then trying to send the cell. Also attach dummy resolve
8461 connections to a circuit *before* calling dns_resolve(), to fix
8462 a bug where cached answers would never be sent in RESOLVED cells.
8463 - When we run out of disk space, or other log writing error, don't
8464 crash. Just stop logging to that log and continue.
8465 - We were starting to daemonize before we opened our logs, so if
8466 there were any problems opening logs, we would complain to stderr,
8467 which wouldn't work, and then mysteriously exit.
8468 - Fix a rare bug where sometimes a verified OR would connect to us
8469 before he'd uploaded his descriptor, which would cause us to
8470 assign conn->nickname as though he's unverified. Now we look through
8471 the fingerprint list to see if he's there.
8472 - Fix a rare assert trigger, where routerinfos for entries in
8473 our cpath would expire while we're building the path.
8476 - Clients can ask dirservers for /dir.z to get a compressed version
8477 of the directory. Only works for servers running 0.0.9, of course.
8478 - Make clients cache directories and use them to seed their router
8479 lists at startup. This means clients have a datadir again.
8480 - Configuration infrastructure support for warning on obsolete
8482 - Respond to content-encoding headers by trying to uncompress as
8484 - Reply with a deflated directory when a client asks for "dir.z".
8485 We could use allow-encodings instead, but allow-encodings isn't
8486 specified in HTTP 1.0.
8487 - Raise the max dns workers from 50 to 100.
8488 - Discourage people from setting their dirfetchpostperiod more often
8489 than once per minute.
8490 - Protect dirservers from overzealous descriptor uploading -- wait
8491 10 seconds after directory gets dirty, before regenerating.
8494 Changes in version 0.0.8 - 2004-08-25
8495 o Port it to SunOS 5.9 / Athena
8498 Changes in version 0.0.8rc2 - 2004-08-20
8499 o Make it compile on cygwin again.
8500 o When picking unverified routers, skip those with low uptime and/or
8501 low bandwidth, depending on what properties you care about.
8504 Changes in version 0.0.8rc1 - 2004-08-18
8505 o Changes from 0.0.7.3:
8507 - Fix assert triggers: if the other side returns an address 0.0.0.0,
8508 don't put it into the client dns cache.
8509 - If a begin failed due to exit policy, but we believe the IP address
8510 should have been allowed, switch that router to exitpolicy reject *:*
8511 until we get our next directory.
8513 - Clients choose nodes proportional to advertised bandwidth.
8514 - Avoid using nodes with low uptime as introduction points.
8515 - Handle servers with dynamic IP addresses: don't replace
8516 options->Address with the resolved one at startup, and
8517 detect our address right before we make a routerinfo each time.
8518 - 'FascistFirewall' option to pick dirservers and ORs on specific
8519 ports; plus 'FirewallPorts' config option to tell FascistFirewall
8520 which ports are open. (Defaults to 80,443)
8521 - Be more aggressive about trying to make circuits when the network
8522 has changed (e.g. when you unsuspend your laptop).
8523 - Check for time skew on http headers; report date in response to
8525 - If the entrynode config line has only one node, don't pick it as
8527 - Add strict{entry|exit}nodes config options. If set to 1, then
8528 we refuse to build circuits that don't include the specified entry
8530 - OutboundBindAddress config option, to bind to a specific
8531 IP address for outgoing connect()s.
8532 - End truncated log entries (e.g. directories) with "[truncated]".
8534 o Patches to 0.0.8preX:
8536 - Patches to compile and run on win32 again (maybe)?
8537 - Fix crash when looking for ~/.torrc with no $HOME set.
8538 - Fix a race bug in the unit tests.
8539 - Handle verified/unverified name collisions better when new
8540 routerinfo's arrive in a directory.
8541 - Sometimes routers were getting entered into the stats before
8542 we'd assigned their identity_digest. Oops.
8543 - Only pick and establish intro points after we've gotten a
8546 - AllowUnverifiedNodes config option to let circuits choose no-name
8547 routers in entry,middle,exit,introduction,rendezvous positions.
8548 Allow middle and rendezvous positions by default.
8549 - Add a man page for tor-resolve.
8552 Changes in version 0.0.7.3 - 2004-08-12
8553 o Stop dnsworkers from triggering an assert failure when you
8554 ask them to resolve the host "".
8557 Changes in version 0.0.8pre3 - 2004-08-09
8558 o Changes from 0.0.7.2:
8559 - Allow multiple ORs with same nickname in routerlist -- now when
8560 people give us one identity key for a nickname, then later
8561 another, we don't constantly complain until the first expires.
8562 - Remember used bandwidth (both in and out), and publish 15-minute
8563 snapshots for the past day into our descriptor.
8564 - You can now fetch $DIRURL/running-routers to get just the
8565 running-routers line, not the whole descriptor list. (But
8566 clients don't use this yet.)
8567 - When people mistakenly use Tor as an http proxy, point them
8568 at the tor-doc.html rather than the INSTALL.
8569 - Remove our mostly unused -- and broken -- hex_encode()
8570 function. Use base16_encode() instead. (Thanks to Timo Lindfors
8571 for pointing out this bug.)
8572 - Rotate onion keys every 12 hours, not every 2 hours, so we have
8573 fewer problems with people using the wrong key.
8574 - Change the default exit policy to reject the default edonkey,
8575 kazaa, gnutella ports.
8576 - Add replace_file() to util.[ch] to handle win32's rename().
8578 o Changes from 0.0.8preX:
8579 - Fix two bugs in saving onion keys to disk when rotating, so
8580 hopefully we'll get fewer people using old onion keys.
8581 - Fix an assert error that was making SocksPolicy not work.
8582 - Be willing to expire routers that have an open dirport -- it's
8583 just the authoritative dirservers we want to not forget.
8584 - Reject tor-resolve requests for .onion addresses early, so we
8585 don't build a whole rendezvous circuit and then fail.
8586 - When you're warning a server that he's unverified, don't cry
8588 - Fix a race condition: don't try to extend onto a connection
8589 that's still handshaking.
8590 - For servers in clique mode, require the conn to be open before
8591 you'll choose it for your path.
8592 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
8593 end relay cell, etc.
8594 - Measure bandwidth capacity over the last 24 hours, not just 12
8595 - Bugfix: authoritative dirservers were making and signing a new
8596 directory for each client, rather than reusing the cached one.
8599 Changes in version 0.0.8pre2 - 2004-08-04
8600 o Changes from 0.0.7.2:
8602 - Check directory signature _before_ you decide whether you're
8603 you're running an obsolete version and should exit.
8604 - Check directory signature _before_ you parse the running-routers
8605 list to decide who's running or verified.
8606 - Bugfixes and features:
8607 - Check return value of fclose while writing to disk, so we don't
8608 end up with broken files when servers run out of disk space.
8609 - Log a warning if the user uses an unsafe socks variant, so people
8610 are more likely to learn about privoxy or socat.
8611 - Dirservers now include RFC1123-style dates in the HTTP headers,
8612 which one day we will use to better detect clock skew.
8614 o Changes from 0.0.8pre1:
8615 - Make it compile without warnings again on win32.
8616 - Log a warning if you're running an unverified server, to let you
8617 know you might want to get it verified.
8618 - Only pick a default nickname if you plan to be a server.
8621 Changes in version 0.0.8pre1 - 2004-07-23
8623 - Made our unit tests compile again on OpenBSD 3.5, and tor
8624 itself compile again on OpenBSD on a sparc64.
8625 - We were neglecting milliseconds when logging on win32, so
8626 everything appeared to happen at the beginning of each second.
8629 - 'Extend' relay cell payloads now include the digest of the
8630 intended next hop's identity key. Now we can verify that we're
8631 extending to the right router, and also extend to routers we
8632 hadn't heard of before.
8635 - Tor nodes can now act as relays (with an advertised ORPort)
8636 without being manually verified by the dirserver operators.
8637 - Uploaded descriptors of unverified routers are now accepted
8638 by the dirservers, and included in the directory.
8639 - Verified routers are listed by nickname in the running-routers
8640 list; unverified routers are listed as "$<fingerprint>".
8641 - We now use hash-of-identity-key in most places rather than
8642 nickname or addr:port, for improved security/flexibility.
8643 - To avoid Sybil attacks, paths still use only verified servers.
8644 But now we have a chance to play around with hybrid approaches.
8645 - Nodes track bandwidth usage to estimate capacity (not used yet).
8646 - ClientOnly option for nodes that never want to become servers.
8647 - Directory caching.
8648 - "AuthoritativeDir 1" option for the official dirservers.
8649 - Now other nodes (clients and servers) will cache the latest
8650 directory they've pulled down.
8651 - They can enable their DirPort to serve it to others.
8652 - Clients will pull down a directory from any node with an open
8653 DirPort, and check the signature/timestamp correctly.
8654 - Authoritative dirservers now fetch directories from other
8655 authdirservers, to stay better synced.
8656 - Running-routers list tells who's down also, along with noting
8657 if they're verified (listed by nickname) or unverified (listed
8659 - Allow dirservers to serve running-router list separately.
8660 This isn't used yet.
8661 - ORs connect-on-demand to other ORs
8662 - If you get an extend cell to an OR you're not connected to,
8663 connect, handshake, and forward the create cell.
8664 - The authoritative dirservers stay connected to everybody,
8665 and everybody stays connected to 0.0.7 servers, but otherwise
8666 clients/servers expire unused connections after 5 minutes.
8667 - When servers get a sigint, they delay 30 seconds (refusing new
8668 connections) then exit. A second sigint causes immediate exit.
8669 - File and name management:
8670 - Look for .torrc if no CONFDIR "torrc" is found.
8671 - If no datadir is defined, then choose, make, and secure ~/.tor
8673 - If torrc not found, exitpolicy reject *:*.
8674 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
8675 - If no nickname is defined, derive default from hostname.
8676 - Rename secret key files, e.g. identity.key -> secret_id_key,
8677 to discourage people from mailing their identity key to tor-ops.
8678 - Refuse to build a circuit before the directory has arrived --
8679 it won't work anyway, since you won't know the right onion keys
8681 - Try other dirservers immediately if the one you try is down. This
8682 should tolerate down dirservers better now.
8683 - Parse tor version numbers so we can do an is-newer-than check
8684 rather than an is-in-the-list check.
8685 - New socks command 'resolve', to let us shim gethostbyname()
8687 - A 'tor_resolve' script to access the socks resolve functionality.
8688 - A new socks-extensions.txt doc file to describe our
8689 interpretation and extensions to the socks protocols.
8690 - Add a ContactInfo option, which gets published in descriptor.
8691 - Publish OR uptime in descriptor (and thus in directory) too.
8692 - Write tor version at the top of each log file
8693 - New docs in the tarball:
8695 - Document that you should proxy your SSL traffic too.
8698 Changes in version 0.0.7.2 - 2004-07-07
8699 o A better fix for the 0.0.0.0 problem, that will hopefully
8700 eliminate the remaining related assertion failures.
8703 Changes in version 0.0.7.1 - 2004-07-04
8704 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
8705 since internally we use 0.0.0.0 to signify "not yet resolved".
8708 Changes in version 0.0.7 - 2004-06-07
8709 o Updated the man page to reflect the new features.
8712 Changes in version 0.0.7rc2 - 2004-06-06
8713 o Changes from 0.0.7rc1:
8714 - Make it build on Win32 again.
8715 o Changes from 0.0.6.2:
8716 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
8720 Changes in version 0.0.7rc1 - 2004-06-02
8722 - On sighup, we were adding another log without removing the first
8723 one. So log messages would get duplicated n times for n sighups.
8724 - Several cases of using a connection after we'd freed it. The
8725 problem was that connections that are pending resolve are in both
8726 the pending_resolve tree, and also the circuit's resolving_streams
8727 list. When you want to remove one, you must remove it from both.
8728 - Fix a double-mark-for-close where an end cell arrived for a
8729 resolving stream, and then the resolve failed.
8730 - Check directory signatures based on name of signer, not on whom
8731 we got the directory from. This will let us cache directories more
8734 - Crank up some of our constants to handle more users.
8737 Changes in version 0.0.7pre1 - 2004-06-02
8738 o Fixes for crashes and other obnoxious bugs:
8739 - Fix an epipe bug: sometimes when directory connections failed
8740 to connect, we would give them a chance to flush before closing
8742 - When we detached from a circuit because of resolvefailed, we
8743 would immediately try the same circuit twice more, and then
8744 give up on the resolve thinking we'd tried three different
8746 - Limit the number of intro circuits we'll attempt to build for a
8747 hidden service per 15-minute period.
8748 - Check recommended-software string *early*, before actually parsing
8749 the directory. Thus we can detect an obsolete version and exit,
8750 even if the new directory format doesn't parse.
8751 o Fixes for security bugs:
8752 - Remember which nodes are dirservers when you startup, and if a
8753 random OR enables his dirport, don't automatically assume he's
8754 a trusted dirserver.
8756 - Directory connections were asking the wrong poll socket to
8757 start writing, and not asking themselves to start writing.
8758 - When we detached from a circuit because we sent a begin but
8759 didn't get a connected, we would use it again the first time;
8760 but after that we would correctly switch to a different one.
8761 - Stop warning when the first onion decrypt attempt fails; they
8762 will sometimes legitimately fail now that we rotate keys.
8763 - Override unaligned-access-ok check when $host_cpu is ia64 or
8764 arm. Apparently they allow it but the kernel whines.
8765 - Dirservers try to reconnect periodically too, in case connections
8767 - Fix some memory leaks in directory servers.
8768 - Allow backslash in Win32 filenames.
8769 - Made Tor build complain-free on FreeBSD, hopefully without
8770 breaking other BSD builds. We'll see.
8772 - Doxygen markup on all functions and global variables.
8773 - Make directory functions update routerlist, not replace it. So
8774 now directory disagreements are not so critical a problem.
8775 - Remove the upper limit on number of descriptors in a dirserver's
8776 directory (not that we were anywhere close).
8777 - Allow multiple logfiles at different severity ranges.
8778 - Allow *BindAddress to specify ":port" rather than setting *Port
8779 separately. Allow multiple instances of each BindAddress config
8780 option, so you can bind to multiple interfaces if you want.
8781 - Allow multiple exit policy lines, which are processed in order.
8782 Now we don't need that huge line with all the commas in it.
8783 - Enable accept/reject policies on SOCKS connections, so you can bind
8784 to 0.0.0.0 but still control who can use your OP.
8787 Changes in version 0.0.6.2 - 2004-05-16
8788 o Our integrity-checking digest was checking only the most recent cell,
8789 not the previous cells like we'd thought.
8790 Thanks to Stefan Mark for finding the flaw!
8793 Changes in version 0.0.6.1 - 2004-05-06
8794 o Fix two bugs in our AES counter-mode implementation (this affected
8795 onion-level stream encryption, but not TLS-level). It turns
8796 out we were doing something much more akin to a 16-character
8797 polyalphabetic cipher. Oops.
8798 Thanks to Stefan Mark for finding the flaw!
8799 o Retire moria3 as a directory server, and add tor26 as a directory
8803 Changes in version 0.0.6 - 2004-05-02
8807 Changes in version 0.0.6rc4 - 2004-05-01
8808 o Update the built-in dirservers list to use the new directory format
8809 o Fix a rare seg fault: if a node offering a hidden service attempts
8810 to build a circuit to Alice's rendezvous point and fails before it
8811 reaches the last hop, it retries with a different circuit, but
8813 o Handle windows socket errors correctly.
8816 Changes in version 0.0.6rc3 - 2004-04-28
8817 o Don't expire non-general excess circuits (if we had enough
8818 circuits open, we were expiring rendezvous circuits -- even
8819 when they had a stream attached. oops.)
8820 o Fetch randomness from /dev/urandom better (not via fopen/fread)
8821 o Better debugging for tls errors
8822 o Some versions of openssl have an SSL_pending function that erroneously
8823 returns bytes when there is a non-application record pending.
8824 o Set Content-Type on the directory and hidserv descriptor.
8825 o Remove IVs from cipher code, since AES-ctr has none.
8826 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
8827 o We were using an array of length zero in a few places.
8828 o win32's gethostbyname can't resolve an IP to an IP.
8829 o win32's close can't close a socket.
8832 Changes in version 0.0.6rc2 - 2004-04-26
8833 o Fix a bug where we were closing tls connections intermittently.
8834 It turns out openssl keeps its errors around -- so if an error
8835 happens, and you don't ask about it, and then another openssl
8836 operation happens and succeeds, and you ask if there was an error,
8837 it tells you about the first error. Fun fun.
8838 o Fix a bug that's been lurking since 27 may 03 (!)
8839 When passing back a destroy cell, we would use the wrong circ id.
8840 'Mostly harmless', but still worth fixing.
8841 o Since we don't support truncateds much, don't bother sending them;
8842 just close the circ.
8843 o check for <machine/limits.h> so we build on NetBSD again (I hope).
8844 o don't crash if a conn that sent a begin has suddenly lost its circuit
8845 (this was quite rare).
8848 Changes in version 0.0.6rc1 - 2004-04-25
8849 o We now rotate link (tls context) keys and onion keys.
8850 o CREATE cells now include oaep padding, so you can tell
8851 if you decrypted them correctly.
8852 o Add bandwidthburst to server descriptor.
8853 o Directories now say which dirserver signed them.
8854 o Use a tor_assert macro that logs failed assertions too.
8857 Changes in version 0.0.6pre5 - 2004-04-18
8858 o changes from 0.0.6pre4:
8859 - make tor build on broken freebsd 5.2 installs
8860 - fix a failed assert when you try an intro point, get a nack, and try
8861 a second one and it works.
8862 - when alice uses a port that the hidden service doesn't accept,
8863 it now sends back an end cell (denied by exit policy). otherwise
8864 alice would just have to wait to time out.
8865 - fix another rare bug: when we had tried all the intro
8866 points for a hidden service, we fetched the descriptor
8867 again, but we left our introcirc thinking it had already
8868 sent an intro, so it kept waiting for a response...
8869 - bugfix: when you sleep your hidden-service laptop, as soon
8870 as it wakes up it tries to upload a service descriptor, but
8871 socketpair fails for some reason (localhost not up yet?).
8872 now we simply give up on that upload, and we'll try again later.
8873 i'd still like to find the bug though.
8874 - if an intro circ waiting for an ack dies before getting one, then
8876 - we were reusing stale service descriptors and refetching usable
8880 Changes in version 0.0.6pre4 - 2004-04-14
8881 o changes from 0.0.6pre3:
8882 - when bob fails to connect to the rendezvous point, and his
8883 circ didn't fail because of the rendezvous point itself, then
8884 he retries a couple of times
8885 - we expire introduction and rendezvous circs more thoroughly
8886 (sometimes they were hanging around forever)
8887 - we expire unattached rendezvous streams that have been around
8888 too long (they were sticking around forever).
8889 - fix a measly fencepost error that was crashing everybody with
8893 Changes in version 0.0.6pre3 - 2004-04-14
8894 o changes from 0.0.6pre2:
8895 - make hup work again
8896 - fix some memory leaks for dirservers
8897 - allow more skew in rendezvous descriptor timestamps, to help
8898 handle people like blanu who don't know what time it is
8899 - normal circs are 3 hops, but some rend/intro circs are 4, if
8900 the initiator doesn't get to choose the last hop
8901 - send acks for introductions, so alice can know whether to try
8903 - bob publishes intro points more correctly
8904 o changes from 0.0.5:
8905 - fix an assert trigger that's been plaguing us since the days
8906 of 0.0.2prexx (thanks weasel!)
8907 - retry stream correctly when we fail to connect because of
8908 exit-policy-reject (should try another) or can't-resolve-address
8909 (also should try another, because dns on random internet servers
8911 - when we hup a dirserver and we've *removed* a server from the
8912 approved-routers list, now we remove that server from the
8913 in-memory directories too
8916 Changes in version 0.0.6pre2 - 2004-04-08
8917 o We fixed our base32 implementation. Now it works on all architectures.
8920 Changes in version 0.0.6pre1 - 2004-04-08
8922 - Hidden services and rendezvous points are implemented. Go to
8923 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
8924 hidden services. (This only works via a socks4a proxy such as
8925 Privoxy, and currently it's quite slow.)
8928 Changes in version 0.0.5 - 2004-03-30
8932 Changes in version 0.0.5rc3 - 2004-03-29
8933 o Install torrc as torrc.sample -- we no longer clobber your
8935 o Re-enable recommendedversion checking (we broke it in rc2, oops)
8936 o Add in a 'notice' log level for things the operator should hear
8937 but that aren't warnings
8940 Changes in version 0.0.5rc2 - 2004-03-29
8941 o Hold socks connection open until reply is flushed (if possible)
8942 o Make exit nodes resolve IPs to IPs immediately, rather than asking
8943 the dns farm to do it.
8944 o Fix c99 aliasing warnings in rephist.c
8945 o Don't include server descriptors that are older than 24 hours in the
8947 o Give socks 'reject' replies their whole 15s to attempt to flush,
8948 rather than seeing the 60s timeout and assuming the flush had failed.
8949 o Clean automake droppings from the cvs repository
8952 Changes in version 0.0.5rc1 - 2004-03-28
8953 o Fix mangled-state bug in directory fetching (was causing sigpipes).
8954 o Only build circuits after we've fetched the directory: clients were
8955 using only the directory servers before they'd fetched a directory.
8956 This also means longer startup time; so it goes.
8957 o Fix an assert trigger where an OP would fail to handshake, and we'd
8958 expect it to have a nickname.
8959 o Work around a tsocks bug: do a socks reject when AP connection dies
8960 early, else tsocks goes into an infinite loop.
8963 Changes in version 0.0.4 - 2004-03-26
8964 o When connecting to a dirserver or OR and the network is down,
8968 Changes in version 0.0.3 - 2004-03-26
8969 o Warn and fail if server chose a nickname with illegal characters
8970 o Port to Solaris and Sparc:
8971 - include missing header fcntl.h
8972 - have autoconf find -lsocket -lnsl automatically
8973 - deal with hardware word alignment
8974 - make uname() work (solaris has a different return convention)
8975 - switch from using signal() to sigaction()
8976 o Preliminary work on reputation system:
8977 - Keep statistics on success/fail of connect attempts; they're published
8978 by kill -USR1 currently.
8979 - Add a RunTesting option to try to learn link state by creating test
8980 circuits, even when SocksPort is off.
8981 - Remove unused open circuits when there are too many.
8984 Changes in version 0.0.2 - 2004-03-19
8985 - Include strlcpy and strlcat for safer string ops
8986 - define INADDR_NONE so we compile (but still not run) on solaris
8989 Changes in version 0.0.2pre27 - 2004-03-14
8991 - Allow internal tor networks (we were rejecting internal IPs,
8992 now we allow them if they're set explicitly).
8993 - And fix a few endian issues.
8996 Changes in version 0.0.2pre26 - 2004-03-14
8998 - If a stream times out after 15s without a connected cell, don't
8999 try that circuit again: try a new one.
9000 - Retry streams at most 4 times. Then give up.
9001 - When a dirserver gets a descriptor from an unknown router, it
9002 logs its fingerprint (so the dirserver operator can choose to
9003 accept it even without mail from the server operator).
9004 - Inform unapproved servers when we reject their descriptors.
9005 - Make tor build on Windows again. It works as a client, who knows
9007 - Clearer instructions in the torrc for how to set up a server.
9008 - Be more efficient about reading fd's when our global token bucket
9009 (used for rate limiting) becomes empty.
9011 - Stop asserting that computers always go forward in time. It's
9013 - When we sent a cell (e.g. destroy) and then marked an OR connection
9014 expired, we might close it before finishing a flush if the other
9015 side isn't reading right then.
9016 - Don't allow dirservers to start if they haven't defined
9018 - We were caching transient dns failures. Oops.
9019 - Prevent servers from publishing an internal IP as their address.
9020 - Address a strcat vulnerability in circuit.c
9023 Changes in version 0.0.2pre25 - 2004-03-04
9025 - Put the OR's IP in its router descriptor, not its fqdn. That way
9026 we'll stop being stalled by gethostbyname for nodes with flaky dns,
9029 - If the user typed in an address that didn't resolve, the server
9033 Changes in version 0.0.2pre24 - 2004-03-03
9035 - Fix an assertion failure in dns.c, where we were trying to dequeue
9036 a pending dns resolve even if it wasn't pending
9037 - Fix a spurious socks5 warning about still trying to write after the
9038 connection is finished.
9039 - Hold certain marked_for_close connections open until they're finished
9040 flushing, rather than losing bytes by closing them too early.
9041 - Correctly report the reason for ending a stream
9042 - Remove some duplicate calls to connection_mark_for_close
9043 - Put switch_id and start_daemon earlier in the boot sequence, so it
9044 will actually try to chdir() to options.DataDirectory
9045 - Make 'make test' exit(1) if a test fails; fix some unit tests
9046 - Make tor fail when you use a config option it doesn't know about,
9047 rather than warn and continue.
9048 - Make --version work
9049 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
9052 Changes in version 0.0.2pre23 - 2004-02-29
9054 - Print a statement when the first circ is finished, so the user
9056 - If a relay cell is unrecognized at the end of the circuit,
9057 send back a destroy. (So attacks to mutate cells are more
9059 - New config option 'excludenodes' to avoid certain nodes for circuits.
9060 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
9061 so you can collect coredumps there.
9063 - Fix a bug in tls flushing where sometimes data got wedged and
9064 didn't flush until more data got sent. Hopefully this bug was
9065 a big factor in the random delays we were seeing.
9066 - Make 'connected' cells include the resolved IP, so the client
9067 dns cache actually gets populated.
9068 - Disallow changing from ORPort=0 to ORPort>0 on hup.
9069 - When we time-out on a stream and detach from the circuit, send an
9070 end cell down it first.
9071 - Only warn about an unknown router (in exitnodes, entrynodes,
9072 excludenodes) after we've fetched a directory.
9075 Changes in version 0.0.2pre22 - 2004-02-26
9077 - Servers publish less revealing uname information in descriptors.
9078 - More memory tracking and assertions, to crash more usefully when
9080 - If the default torrc isn't there, just use some default defaults.
9081 Plus provide an internal dirservers file if they don't have one.
9082 - When the user tries to use Tor as an http proxy, give them an http
9083 501 failure explaining that we're a socks proxy.
9084 - Dump a new router.desc on hup, to help confused people who change
9085 their exit policies and then wonder why router.desc doesn't reflect
9087 - Clean up the generic tor.sh init script that we ship with.
9089 - If the exit stream is pending on the resolve, and a destroy arrives,
9090 then the stream wasn't getting removed from the pending list. I
9091 think this was the one causing recent server crashes.
9092 - Use a more robust poll on OSX 10.3, since their poll is flaky.
9093 - When it couldn't resolve any dirservers, it was useless from then on.
9094 Now it reloads the RouterFile (or default dirservers) if it has no
9096 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
9097 many users don't even *have* a /usr/local/sbin/.
9100 Changes in version 0.0.2pre21 - 2004-02-18
9102 - There's a ChangeLog file that actually reflects the changelog.
9103 - There's a 'torify' wrapper script, with an accompanying
9104 tor-tsocks.conf, that simplifies the process of using tsocks for
9105 tor. It even has a man page.
9106 - The tor binary gets installed to sbin rather than bin now.
9107 - Retry streams where the connected cell hasn't arrived in 15 seconds
9108 - Clean up exit policy handling -- get the default out of the torrc,
9109 so we can update it without forcing each server operator to fix
9111 - Allow imaps and pop3s in default exit policy
9113 - Prevent picking middleman nodes as the last node in the circuit
9116 Changes in version 0.0.2pre20 - 2004-01-30
9118 - We now have a deb package, and it's in debian unstable. Go to
9120 - I've split the TotalBandwidth option into BandwidthRate (how many
9121 bytes per second you want to allow, long-term) and
9122 BandwidthBurst (how many bytes you will allow at once before the cap
9123 kicks in). This better token bucket approach lets you, say, set
9124 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
9125 performance while not exceeding your monthly bandwidth quota.
9126 - Push out a tls record's worth of data once you've got it, rather
9127 than waiting until you've read everything waiting to be read. This
9128 may improve performance by pipelining better. We'll see.
9129 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
9130 from failed circuits (if they haven't been connected yet) and attach
9132 - Expire old streams that haven't managed to connect. Some day we'll
9133 have them reattach to new circuits instead.
9136 - Fix several memory leaks that were causing servers to become bloated
9138 - Fix a few very rare assert triggers. A few more remain.
9139 - Setuid to User _before_ complaining about running as root.
9142 Changes in version 0.0.2pre19 - 2004-01-07
9144 - Fix deadlock condition in dns farm. We were telling a child to die by
9145 closing the parent's file descriptor to him. But newer children were
9146 inheriting the open file descriptor from the parent, and since they
9147 weren't closing it, the socket never closed, so the child never read
9148 eof, so he never knew to exit. Similarly, dns workers were holding
9149 open other sockets, leading to all sorts of chaos.
9150 - New cleaner daemon() code for forking and backgrounding.
9151 - If you log to a file, it now prints an entry at the top of the
9152 logfile so you know it's working.
9153 - The onionskin challenge length was 30 bytes longer than necessary.
9154 - Started to patch up the spec so it's not quite so out of date.
9157 Changes in version 0.0.2pre18 - 2004-01-02
9159 - Fix endian issues with the 'integrity' field in the relay header.
9160 - Fix a potential bug where connections in state
9161 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
9164 Changes in version 0.0.2pre17 - 2003-12-30
9166 - Made --debuglogfile (or any second log file, actually) work.
9167 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
9168 adversary could force us into an infinite loop.
9171 - Each onionskin handshake now includes a hash of the computed key,
9172 to prove the server's identity and help perfect forward secrecy.
9173 - Changed cell size from 256 to 512 bytes (working toward compatibility
9175 - Changed cell length to 2 bytes, and moved it to the relay header.
9176 - Implemented end-to-end integrity checking for the payloads of
9178 - Separated streamid from 'recognized' (otherwise circuits will get
9179 messed up when we try to have streams exit from the middle). We
9180 use the integrity-checking to confirm that a cell is addressed to
9182 - Randomize the initial circid and streamid values, so an adversary who
9183 breaks into a node can't learn how many circuits or streams have
9187 Changes in version 0.0.2pre16 - 2003-12-14
9189 - Fixed a bug that made HUP trigger an assert
9190 - Fixed a bug where a circuit that immediately failed wasn't being
9191 counted as a failed circuit in counting retries.
9194 - Now we close the circuit when we get a truncated cell: otherwise we're
9195 open to an anonymity attack where a bad node in the path truncates
9196 the circuit and then we open streams at him.
9197 - Add port ranges to exit policies
9198 - Add a conservative default exit policy
9199 - Warn if you're running tor as root
9200 - on HUP, retry OR connections and close/rebind listeners
9201 - options.EntryNodes: try these nodes first when picking the first node
9202 - options.ExitNodes: if your best choices happen to include any of
9203 your preferred exit nodes, you choose among just those preferred
9205 - options.ExcludedNodes: nodes that are never picked in path building
9208 Changes in version 0.0.2pre15 - 2003-12-03
9209 o Robustness and bugfixes:
9210 - Sometimes clients would cache incorrect DNS resolves, which would
9211 really screw things up.
9212 - An OP that goes offline would slowly leak all its sockets and stop
9214 - A wide variety of bugfixes in exit node selection, exit policy
9215 handling, and processing pending streams when a new circuit is
9217 - Pick nodes for a path only from those the directory says are up
9218 - Choose randomly from all running dirservers, not always the first one
9219 - Increase allowed http header size for directory fetch.
9220 - Stop writing to stderr (if we're daemonized it will be closed).
9221 - Enable -g always, so cores will be more useful to me.
9222 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
9225 - Wrote a man page. It lists commonly used options.
9228 - Change default loglevel to warn.
9229 - Make PidFile default to null rather than littering in your CWD.
9230 - OnionRouter config option is now obsolete. Instead it just checks
9232 - Moved to a single unified torrc file for both clients and servers.
9235 Changes in version 0.0.2pre14 - 2003-11-29
9236 o Robustness and bugfixes:
9237 - Force the admin to make the DataDirectory himself
9238 - to get ownership/permissions right
9239 - so clients no longer make a DataDirectory and then never use it
9240 - fix bug where a client who was offline for 45 minutes would never
9241 pull down a directory again
9242 - fix (or at least hide really well) the dns assert bug that was
9243 causing server crashes
9244 - warnings and improved robustness wrt clockskew for certs
9245 - use the native daemon(3) to daemonize, when available
9246 - exit if bind() fails
9247 - exit if neither socksport nor orport is defined
9248 - include our own tor_timegm (Win32 doesn't have its own)
9249 - bugfix for win32 with lots of connections
9250 - fix minor bias in PRNG
9251 - make dirserver more robust to corrupt cached directory
9254 - Wrote the design document (woo)
9256 o Circuit building and exit policies:
9257 - Circuits no longer try to use nodes that the directory has told them
9259 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
9260 bitcounts (18.0.0.0/8).
9261 - Make AP connections standby for a circuit if no suitable circuit
9262 exists, rather than failing
9263 - Circuits choose exit node based on addr/port, exit policies, and
9264 which AP connections are standing by
9265 - Bump min pathlen from 2 to 3
9266 - Relay end cells have a payload to describe why the stream ended.
9267 - If the stream failed because of exit policy, try again with a new
9269 - Clients have a dns cache to remember resolved addresses.
9270 - Notice more quickly when we have no working circuits
9273 - APPort is now called SocksPort
9274 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
9276 - RecommendedVersions is now a config variable rather than
9277 hardcoded (for dirservers)
9278 - Reloads config on HUP
9279 - Usage info on -h or --help
9280 - If you set User and Group config vars, it'll setu/gid to them.
9283 Changes in version 0.0.2pre13 - 2003-10-19
9284 o General stability:
9285 - SSL_write no longer fails when it returns WANTWRITE and the number
9286 of bytes in the buf has changed by the next SSL_write call.
9287 - Fix segfault fetching directory when network is down
9288 - Fix a variety of minor memory leaks
9289 - Dirservers reload the fingerprints file on HUP, so I don't have
9290 to take down the network when I approve a new router
9291 - Default server config file has explicit Address line to specify fqdn
9294 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
9295 - Make listener connections not ever alloc bufs
9297 o Autoconf improvements:
9298 - don't clobber an external CFLAGS in ./configure
9299 - Make install now works
9300 - create var/lib/tor on make install
9301 - autocreate a tor.sh initscript to help distribs
9302 - autocreate the torrc and sample-server-torrc with correct paths
9304 o Log files and Daemonizing now work:
9305 - If --DebugLogFile is specified, log to it at -l debug
9306 - If --LogFile is specified, use it instead of commandline
9307 - If --RunAsDaemon is set, tor forks and backgrounds on startup