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