1 Changes in version 0.2.5.1-alpha - 2013-10-02
2 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
3 on Linux, allows bridges that offer pluggable transports to report usage
4 statistics, fixes many issues to make testing easier, and provides
5 a pile of minor features and bugfixes that have been waiting for a
6 release of the new branch.
8 This is the first alpha release in a new series, so expect there to
9 be bugs. Users who would rather test out a more stable branch should
10 stay with 0.2.4.x for now.
12 o Major features (security):
13 - Use the seccomp2 syscall filtering facility on Linux to limit
14 which system calls Tor can invoke. This is an experimental,
15 Linux-only feature to provide defense-in-depth against unknown
16 attacks. To try turning it on, set "Sandbox 1" in your torrc
17 file. Please be ready to report bugs. We hope to add support
18 for better sandboxing in the future, including more fine-grained
19 filters, better division of responsibility, and support for more
20 platforms. This work has been done by Cristian-Matei Toader for
21 Google Summer of Code.
22 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
23 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
24 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
25 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
26 them to solve bug 6033.)
28 o Major features (other):
29 - Add support for passing arguments to managed pluggable transport
30 proxies. Implements ticket 3594.
31 - Bridges now track GeoIP information and the number of their users
32 even when pluggable transports are in use, and report usage
33 statistics in their extra-info descriptors. Resolves tickets 4773
35 - Make testing Tor networks bootstrap better: lower directory fetch
36 retry schedules and maximum interval without directory requests,
37 and raise maximum download tries. Implements ticket 6752.
38 - Add make target 'test-network' to run tests on a Chutney network.
39 Implements ticket 8530.
40 - The ntor handshake is now on-by-default, no matter what the
41 directory authorities recommend. Implements ticket 8561.
44 - Instead of writing destroy cells directly to outgoing connection
45 buffers, queue them and intersperse them with other outgoing cells.
46 This can prevent a set of resource starvation conditions where too
47 many pending destroy cells prevent data cells from actually getting
48 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
49 bugfix on 0.2.0.1-alpha.
50 - If we are unable to save a microdescriptor to the journal, do not
51 drop it from memory and then reattempt downloading it. Fixes bug
52 9645; bugfix on 0.2.2.6-alpha.
53 - The new channel code sometimes lost track of in-progress circuits,
54 causing long-running clients to stop building new circuits. The
55 fix is to always call circuit_n_chan_done(chan, 0) from
56 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
59 - Tor now builds each source file in two modes: a mode that avoids
60 exposing identifiers needlessly, and another mode that exposes
61 more identifiers for testing. This lets the compiler do better at
62 optimizing the production code, while enabling us to take more
63 radical measures to let the unit tests test things.
64 - The production builds no longer include functions used only in
65 the unit tests; all functions exposed from a module only for
66 unit-testing are now static in production builds.
67 - Add an --enable-coverage configuration option to make the unit
68 tests (and a new src/or/tor-cov target) to build with gcov test
72 - We now have rudimentary function mocking support that our unit
73 tests can use to test functions in isolation. Function mocking
74 lets the tests temporarily replace a function's dependencies with
75 stub functions, so that the tests can check the function without
76 invoking the other functions it calls.
77 - Add more unit tests for the <circid,channel>->circuit map, and
78 the destroy-cell-tracking code to fix bug 7912.
79 - Unit tests for failing cases of the TAP onion handshake.
80 - More unit tests for address-manipulation functions.
82 o Minor features (protecting client timestamps):
83 - Clients no longer send timestamps in their NETINFO cells. These were
84 not used for anything, and they provided one small way for clients
85 to be distinguished from each other as they moved from network to
86 network or behind NAT. Implements part of proposal 222.
87 - Clients now round timestamps in INTRODUCE cells down to the nearest
88 10 minutes. If a new Support022HiddenServices option is set to 0, or
89 if it's set to "auto" and the feature is disabled in the consensus,
90 the timestamp is sent as 0 instead. Implements part of proposal 222.
91 - Stop sending timestamps in AUTHENTICATE cells. This is not such
92 a big deal from a security point of view, but it achieves no actual
93 good purpose, and isn't needed. Implements part of proposal 222.
94 - Reduce down accuracy of timestamps in hidden service descriptors.
95 Implements part of proposal 222.
97 o Minor features (config options):
98 - Config (torrc) lines now handle fingerprints which are missing
99 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
100 - Support a --dump-config option to print some or all of the
101 configured options. Mainly useful for debugging the command-line
102 option parsing code. Helps resolve ticket 4647.
103 - Raise awareness of safer logging: notify user of potentially
104 unsafe config options, like logging more verbosely than severity
105 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
106 - Add a new configuration option TestingV3AuthVotingStartOffset
107 that bootstraps a network faster by changing the timing for
108 consensus votes. Addresses ticket 8532.
109 - Add a new torrc option "ServerTransportOptions" that allows
110 bridge operators to pass configuration parameters to their
111 pluggable transports. Resolves ticket 8929.
112 - The config (torrc) file now accepts bandwidth and space limits in
113 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
114 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
117 o Minor features (build):
118 - Add support for `--library-versions` flag. Implements ticket 6384.
119 - Return the "unexpected sendme" warnings to a warn severity, but make
120 them rate limited, to help diagnose ticket 8093.
121 - Detect a missing asciidoc, and warn the user about it, during
122 configure rather than at build time. Fixes issue 6506. Patch from
125 o Minor features (other):
126 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
127 sockets in a single system call. Implements ticket 5129.
128 - Log current accounting state (bytes sent and received + remaining
129 time for the current accounting period) in the relay's heartbeat
130 message. Implements ticket 5526; patch from Peter Retzlaff.
131 - Implement the TRANSPORT_LAUNCHED control port event that
132 notifies controllers about new launched pluggable
133 transports. Resolves ticket 5609.
134 - If we're using the pure-C 32-bit curve25519_donna implementation
135 of curve25519, build it with the -fomit-frame-pointer option to
136 make it go faster on register-starved hosts. This improves our
137 handshake performance by about 6% on i386 hosts without nacl.
139 - Update to the September 4 2013 Maxmind GeoLite Country database.
142 - Set the listen() backlog limit to the largest actually supported
143 on the system, not to the value in a header file. Fixes bug 9716;
144 bugfix on every released Tor.
145 - No longer accept malformed http headers when parsing urls from
146 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
148 - In munge_extrainfo_into_routerinfo(), check the return value of
149 memchr(). This would have been a serious issue if we ever passed
150 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
152 - On the chance that somebody manages to build Tor on a
153 platform where time_t is unsigned, correct the way that
154 microdesc_add_to_cache() handles negative time arguments.
155 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
156 - Reject relative control socket paths and emit a warning. Previously,
157 single-component control socket paths would be rejected, but Tor
158 would not log why it could not validate the config. Fixes bug 9258;
159 bugfix on 0.2.3.16-alpha.
161 o Minor bugfixes (command line):
162 - Use a single command-line parser for parsing torrc options on the
163 command line and for finding special command-line options to avoid
164 inconsistent behavior for torrc option arguments that have the same
165 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
167 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
168 9573; bugfix on 0.0.9pre5.
170 o Minor fixes (build, auxiliary programs):
171 - Stop preprocessing the "torify" script with autoconf, since
172 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
174 - The tor-fw-helper program now follows the standard convention and
175 exits with status code "0" on success. Fixes bug 9030; bugfix on
176 0.2.3.1-alpha. Patch by Arlo Breault.
177 - Corrected ./configure advice for what openssl dev package you should
178 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
180 o Minor code improvements:
181 - Remove constants and tests for PKCS1 padding; it's insecure and
182 shouldn't be used for anything new. Fixes bug 8792; patch
184 - Remove instances of strcpy() from the unit tests. They weren't
185 hurting anything, since they were only in the unit tests, but it's
186 embarassing to have strcpy() in the code at all, and some analysis
187 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
188 0.2.3.8-alpha. Patch from Arlo Breault.
191 - Remove migration code from when we renamed the "cached-routers"
192 file to "cached-descriptors" back in 0.2.0.8-alpha. This
193 incidentally resolves ticket 6502 by cleaning up the related code
194 a bit. Patch from Akshay Hebbar.
196 o Code simplification and refactoring:
197 - Extract the common duplicated code for creating a subdirectory
198 of the data directory and writing to a file in it. Fixes ticket
199 4282; patch from Peter Retzlaff.
200 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
201 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
202 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
203 - Add a set of accessor functions for the circuit timeout data
204 structure. Fixes ticket 6153; patch from "piet".
205 - Clean up exit paths from connection_listener_new(). Closes ticket
206 8789. Patch from Arlo Breault.
207 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
208 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
209 - Use a doubly-linked list to implement the global circuit list.
210 Resolves ticket 9108. Patch from Marek Majkowski.
211 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
214 Changes in version 0.2.4.17-rc - 2013-09-05
215 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
216 series. It adds an emergency step to help us tolerate the massive
217 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
218 circuit-level handshakes now effectively jump the queue compared to
219 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
220 big bug hindering bridge reachability tests.
223 - Relays now process the new "NTor" circuit-level handshake requests
224 with higher priority than the old "TAP" circuit-level handshake
225 requests. We still process some TAP requests to not totally starve
226 0.2.3 clients when NTor becomes popular. A new consensus parameter
227 "NumNTorsPerTAP" lets us tune the balance later if we need to.
228 Implements ticket 9574.
231 - If the circuit build timeout logic is disabled (via the consensus,
232 or because we are an authority), then don't build testing circuits.
233 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
234 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
235 previously they did not, which prevented them from receiving
236 successful connections from relays for self-test or bandwidth
237 testing. Also, when a relay is extending a circuit to a bridge,
238 it needs to send a NETINFO cell, even when the bridge hasn't sent
239 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
240 - If the time to download the next old-style networkstatus is in
241 the future, do not decline to consider whether to download the
242 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
246 - Avoid double-closing the listener socket in our socketpair()
247 replacement (used on Windows) in the case where the addresses on
248 our opened sockets don't match what we expected. Fixes bug 9400;
249 bugfix on 0.0.2pre7. Found by Coverity.
251 o Minor fixes (config options):
252 - Avoid overflows when the user sets MaxCircuitDirtiness to a
253 ridiculously high value, by imposing a (ridiculously high) 30-day
254 maximum on MaxCircuitDirtiness.
255 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
256 message is logged at notice, not at info.
257 - Warn and fail if a server is configured not to advertise any
258 ORPorts at all. (We need *something* to put in our descriptor,
259 or we just won't work.)
262 - Track how many "TAP" and "NTor" circuit handshake requests we get,
263 and how many we complete, and log it every hour to help relay
264 operators follow trends in network load. Addresses ticket 9658.
265 - Update to the August 7 2013 Maxmind GeoLite Country database.
268 Changes in version 0.2.4.16-rc - 2013-08-10
269 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
270 series. It fixes several crash bugs in the 0.2.4 branch.
273 - Fix a bug in the voting algorithm that could yield incorrect results
274 when a non-naming authority declared too many flags. Fixes bug 9200;
275 bugfix on 0.2.0.3-alpha.
276 - Fix an uninitialized read that could in some cases lead to a remote
277 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
278 Anybody running a hidden service on the experimental 0.2.4.x
279 branch should upgrade. (This is, so far as we know, unrelated to
281 - Avoid an assertion failure when processing DNS replies without the
282 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
283 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
284 0.2.4.15-rc. Found by stem integration tests.
287 - Fix an invalid memory read that occured when a pluggable
288 transport proxy failed its configuration protocol.
289 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
290 - When evaluating whether to use a connection that we haven't
291 decided is canonical using a recent link protocol version,
292 decide that it's canonical only if it used address _does_
293 match the desired address. Fixes bug 9309; bugfix on
294 0.2.4.4-alpha. Reported by skruffy.
295 - Make the default behavior of NumDirectoryGuards be to track
296 NumEntryGuards. Now a user who changes only NumEntryGuards will get
297 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
298 - Fix a spurious compilation warning with some older versions of
299 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
302 - Update to the July 3 2013 Maxmind GeoLite Country database.
305 Changes in version 0.2.4.15-rc - 2013-07-01
306 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
307 series. It fixes a few smaller bugs, but generally appears stable.
308 Please test it and let us know whether it is!
311 - When receiving a new configuration file via the control port's
312 LOADCONF command, do not treat the defaults file as absent.
313 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
316 - Issue a warning when running with the bufferevents backend enabled.
317 It's still not stable, and people should know that they're likely
318 to hit unexpected problems. Closes ticket 9147.
321 Changes in version 0.2.4.14-alpha - 2013-06-18
322 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
323 present in 0.2.4.13-alpha.
326 - When we have too much memory queued in circuits (according to a new
327 MaxMemInCellQueues option), close the circuits consuming the most
328 memory. This prevents us from running out of memory as a relay if
329 circuits fill up faster than they can be drained. Fixes bug 9063;
330 bugfix on the 54th commit of Tor. This bug is a further fix beyond
331 bug 6252, whose fix was merged into 0.2.3.21-rc.
333 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
334 where we tried to solve this issue simply by imposing an upper limit
335 on the number of queued cells for a single circuit. That approach
336 proved to be problematic, since there are ways to provoke clients to
337 send a number of cells in excess of any such reasonable limit. Fixes
338 bug 9072; bugfix on 0.2.4.13-alpha.
340 - Limit hidden service descriptors to at most ten introduction
341 points, to slow one kind of guard enumeration. Fixes bug 9002;
342 bugfix on 0.1.1.11-alpha.
345 Changes in version 0.2.4.13-alpha - 2013-06-14
346 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
347 vulnerabilities, makes socks5 username/password circuit isolation
348 actually actually work (this time for sure!), and cleans up a bunch
349 of other issues in preparation for a release candidate.
351 o Major bugfixes (robustness):
352 - Close any circuit that has too many cells queued on it. Fixes
353 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
354 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
355 - Prevent the get_freelists() function from running off the end of
356 the list of freelists if it somehow gets an unrecognized
357 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
359 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
360 when an exit connection with optimistic data succeeds immediately
361 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
363 - Fix a directory authority crash bug when building a consensus
364 using an older consensus as its basis. Fixes bug 8833. Bugfix
368 - Avoid a memory leak where we would leak a consensus body when we
369 find that a consensus which we couldn't previously verify due to
370 missing certificates is now verifiable. Fixes bug 8719; bugfix
372 - We used to always request authority certificates by identity digest,
373 meaning we'd get the newest one even when we wanted one with a
374 different signing key. Then we would complain about being given
375 a certificate we already had, and never get the one we really
376 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
377 resource to request the one we want. Fixes bug 5595; bugfix on
379 - Follow the socks5 protocol when offering username/password
380 authentication. The fix for bug 8117 exposed this bug, and it
381 turns out real-world applications like Pidgin do care. Bugfix on
382 0.2.3.2-alpha; fixes bug 8879.
383 - Prevent failures on Windows Vista and later when rebuilding the
384 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
385 bugfix on 0.2.4.12-alpha.
388 - Fix an impossible buffer overrun in the AES unit tests. Fixes
389 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
390 - If for some reason we fail to write a microdescriptor while
391 rebuilding the cache, do not let the annotations from that
392 microdescriptor linger in the cache file, and do not let the
393 microdescriptor stay recorded as present in its old location.
394 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
395 - Fix a memory leak that would occur whenever a configuration
396 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
397 - Paste the description for PathBias parameters from the man
398 page into or.h, so the code documents them too. Fixes bug 7982;
399 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
400 - Relays now treat a changed IPv6 ORPort as sufficient reason to
401 publish an updated descriptor. Fixes bug 6026; bugfix on
403 - When launching a resolve request on behalf of an AF_UNIX control
404 socket, omit the address field of the new entry connection, used in
405 subsequent controller events, rather than letting tor_dup_addr()
406 set it to "<unknown address type>". Fixes bug 8639; bugfix on
409 o Minor bugfixes (log messages):
410 - Fix a scaling issue in the path bias accounting code that
411 resulted in "Bug:" log messages from either
412 pathbias_scale_close_rates() or pathbias_count_build_success().
413 This represents a bugfix on a previous bugfix: the original fix
414 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
416 - Give a less useless error message when the user asks for an IPv4
417 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
421 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
422 to tolerate bug 8093 for now.
423 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
424 in directory authority votes to describe whether they have enough
425 measured bandwidths to ignore advertised (relay descriptor)
426 bandwidth claims. Resolves ticket 8711.
427 - Update to the June 5 2013 Maxmind GeoLite Country database.
429 o Removed documentation:
430 - Remove some of the older contents of doc/ as obsolete; move others
431 to torspec.git. Fixes bug 8965.
433 o Code simplification and refactoring:
434 - Avoid using character buffers when constructing most directory
435 objects: this approach was unwieldy and error-prone. Instead,
436 build smartlists of strings, and concatenate them when done.
439 Changes in version 0.2.4.12-alpha - 2013-04-18
440 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
441 process for lengthening the guard rotation period, makes directory
442 authority opinions in the consensus a bit less gameable, makes socks5
443 username/password circuit isolation actually work, and fixes a wide
444 variety of other issues.
447 - Raise the default time that a client keeps an entry guard from
448 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
449 2012 paper. (We would make it even longer, but we need better client
450 load balancing first.) Also, make the guard lifetime controllable
451 via a new GuardLifetime torrc option and a GuardLifetime consensus
452 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
453 - Directory authorities now prefer using measured bandwidths to
454 advertised ones when computing flags and thresholds. Resolves
456 - Directory authorities that have more than a threshold number
457 of relays with measured bandwidths now treat relays with unmeasured
458 bandwidths as having bandwidth 0. Resolves ticket 8435.
460 o Major bugfixes (assert / resource use):
461 - Avoid a bug where our response to TLS renegotiation under certain
462 network conditions could lead to a busy-loop, with 100% CPU
463 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
464 - Avoid an assertion when we discover that we'd like to write a cell
465 onto a closing connection: just discard the cell. Fixes another
466 case of bug 7350; bugfix on 0.2.4.4-alpha.
468 o Major bugfixes (client-side privacy):
469 - When we mark a circuit as unusable for new circuits, have it
470 continue to be unusable for new circuits even if MaxCircuitDirtiness
471 is increased too much at the wrong time, or the system clock jumps
472 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
473 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
474 which have resolved to internal addresses") is set, apply that
475 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
476 - When an exit relay rejects a stream with reason "exit policy", but
477 we only know an exit policy summary (e.g. from the microdesc
478 consensus) for it, do not mark the relay as useless for all exiting.
479 Instead, mark just the circuit as unsuitable for that particular
480 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
481 - Allow applications to get proper stream isolation with
482 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
483 username/password authentication also offer "no authentication". Tor
484 had previously preferred "no authentication", so the applications
485 never actually sent Tor their auth details. Now Tor selects
486 username/password authentication if it's offered. You can disable
487 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
488 bug 8117; bugfix on 0.2.3.3-alpha.
490 o Major bugfixes (other):
491 - When unable to find any working directory nodes to use as a
492 directory guard, give up rather than adding the same non-working
493 nodes to the directory guard list over and over. Fixes bug 8231;
494 bugfix on 0.2.4.8-alpha.
497 - Reject as invalid most directory objects containing a NUL.
498 Belt-and-suspender fix for bug 8037.
499 - In our testsuite, create temporary directories with a bit more
500 entropy in their name to make name collisions less likely. Fixes
502 - Add CACHED keyword to ADDRMAP events in the control protocol
503 to indicate whether a DNS result will be cached or not. Resolves
505 - Update to the April 3 2013 Maxmind GeoLite Country database.
507 o Minor features (build):
508 - Detect and reject attempts to build Tor with threading support
509 when OpenSSL has been compiled without threading support.
511 - Clarify that when autoconf is checking for nacl, it is checking
512 specifically for nacl with a fast curve25519 implementation.
514 - Warn if building on a platform with an unsigned time_t: there
515 are too many places where Tor currently assumes that time_t can
516 hold negative values. We'd like to fix them all, but probably
519 o Minor bugfixes (build):
520 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
521 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
522 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
523 - Add the old src/or/micro-revision.i filename to CLEANFILES.
524 On the off chance that somebody has one, it will go away as soon
525 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
526 - Build Tor correctly on 32-bit platforms where the compiler can build
527 but not run code using the "uint128_t" construction. Fixes bug 8587;
528 bugfix on 0.2.4.8-alpha.
529 - Fix compilation warning with some versions of clang that would
530 prefer the -Wswitch-enum compiler flag to warn about switch
531 statements with missing enum values, even if those switch
532 statements have a "default:" statement. Fixes bug 8598; bugfix
535 o Minor bugfixes (protocol):
536 - Fix the handling of a TRUNCATE cell when it arrives while the
537 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
538 - Fix a misframing issue when reading the version numbers in a
539 VERSIONS cell. Previously we would recognize [00 01 00 02] as
540 'version 1, version 2, and version 0x100', when it should have
541 only included versions 1 and 2. Fixes bug 8059; bugfix on
542 0.2.0.10-alpha. Reported pseudonymously.
543 - Make the format and order of STREAM events for DNS lookups
544 consistent among the various ways to launch DNS lookups. Fixes
545 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
546 - Correct our check for which versions of Tor support the EXTEND2
547 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
548 later, when support was really added in version 0.2.4.8-alpha.
549 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
551 o Minor bugfixes (other):
552 - Correctly store microdescriptors and extrainfo descriptors with
553 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
554 Bug reported by "cypherpunks".
555 - Increase the width of the field used to remember a connection's
556 link protocol version to two bytes. Harmless for now, since the
557 only currently recognized versions are one byte long. Reported
558 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
559 - If the state file's path bias counts are invalid (presumably from a
560 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
561 additional checks and log messages to the scaling of Path Bias
562 counts, in case there still are remaining issues with scaling.
563 Should help resolve bug 8235.
564 - Eliminate several instances where we use "Nickname=ID" to refer to
565 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
566 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
567 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
569 o Minor bugfixes (syscalls):
570 - Always check the return values of functions fcntl() and
571 setsockopt(). We don't believe these are ever actually failing in
572 practice, but better safe than sorry. Also, checking these return
573 values should please analysis tools like Coverity. Patch from
574 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
575 - Use direct writes rather than stdio when building microdescriptor
576 caches, in an attempt to mitigate bug 8031, or at least make it
579 o Minor bugfixes (config):
580 - When rejecting a configuration because we were unable to parse a
581 quoted string, log an actual error message. Fixes bug 7950; bugfix
583 - Behave correctly when the user disables LearnCircuitBuildTimeout
584 but doesn't tell us what they would like the timeout to be. Fixes
585 bug 6304; bugfix on 0.2.2.14-alpha.
586 - When autodetecting the number of CPUs, use the number of available
587 CPUs in preference to the number of configured CPUs. Inform the
588 user if this reduces the number of available CPUs. Fixes bug 8002;
589 bugfix on 0.2.3.1-alpha.
590 - Make it an error when you set EntryNodes but disable UseGuardNodes,
591 since it will (surprisingly to some users) ignore EntryNodes. Fixes
592 bug 8180; bugfix on 0.2.3.11-alpha.
593 - Allow TestingTorNetworks to override the 4096-byte minimum for
594 the Fast threshold. Otherwise they can't bootstrap until they've
595 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
596 - Fix some logic errors when the user manually overrides the
597 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
600 o Minor bugfixes (log messages to help diagnose bugs):
601 - If we fail to free a microdescriptor because of bug 7164, log
602 the filename and line number from which we tried to free it.
603 - Add another diagnostic to the heartbeat message: track and log
604 overhead that TLS is adding to the data we write. If this is
605 high, we are sending too little data to SSL_write at a time.
606 Diagnostic for bug 7707.
607 - Add more detail to a log message about relaxed timeouts, to help
609 - Warn more aggressively when flushing microdescriptors to a
610 microdescriptor cache fails, in an attempt to mitigate bug 8031,
611 or at least make it more diagnosable.
612 - Improve debugging output to help track down bug 8185 ("Bug:
613 outgoing relay cell has n_chan==NULL. Dropping.")
614 - Log the purpose of a path-bias testing circuit correctly.
615 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
617 o Minor bugfixes (0.2.4.x log messages that were too noisy):
618 - Don't attempt to relax the timeout of already opened 1-hop circuits.
619 They might never timeout. This should eliminate some/all cases of
620 the relaxed timeout log message.
621 - Use circuit creation time for network liveness evaluation. This
622 should eliminate warning log messages about liveness caused
623 by changes in timeout evaluation. Fixes bug 6572; bugfix on
625 - Reduce a path bias length check from notice to info. The message
626 is triggered when creating controller circuits. Fixes bug 8196;
627 bugfix on 0.2.4.8-alpha.
628 - Fix a path state issue that triggered a notice during relay startup.
629 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
630 - Reduce occurrences of warns about circuit purpose in
631 connection_ap_expire_building(). Fixes bug 8477; bugfix on
634 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
635 - If we encounter a write failure on a SOCKS connection before we
636 finish our SOCKS handshake, don't warn that we closed the
637 connection before we could send a SOCKS reply. Fixes bug 8427;
638 bugfix on 0.1.0.1-rc.
639 - Correctly recognize that [::1] is a loopback address. Fixes
640 bug 8377; bugfix on 0.2.1.3-alpha.
641 - Fix a directory authority warn caused when we have a large amount
642 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
643 - Don't log inappropriate heartbeat messages when hibernating: a
644 hibernating node is _expected_ to drop out of the consensus,
645 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
646 bugfix on 0.2.3.1-alpha.
647 - Don't complain about bootstrapping problems while hibernating.
648 These complaints reflect a general code problem, but not one
649 with any problematic effects (no connections are actually
650 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
652 o Documentation fixes:
653 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
654 names match. Fixes bug 7768.
655 - Make the torify manpage no longer refer to tsocks; torify hasn't
656 supported tsocks since 0.2.3.14-alpha.
657 - Make the tor manpage no longer reference tsocks.
658 - Fix the GeoIPExcludeUnknown documentation to refer to
659 ExcludeExitNodes rather than the currently nonexistent
660 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
663 - The tor-tsocks.conf is no longer distributed or installed. We
664 recommend that tsocks users use torsocks instead. Resolves
668 Changes in version 0.2.4.11-alpha - 2013-03-11
669 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
670 more robust, makes hidden service authentication work again, and
671 resolves a DPI fingerprint for Tor's SSL transport.
673 o Major features (directory authorities):
674 - Directory authorities now support a new consensus method (17)
675 where they cap the published bandwidth of servers for which
676 insufficient bandwidth measurements exist. Fixes part of bug 2286.
677 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
678 serve any v2 directory information. Now we can test disabling the
679 old deprecated v2 directory format, and see whether doing so has
680 any effect on network load. Begins to fix bug 6783.
681 - Directory authorities now include inside each vote a statement of
682 the performance thresholds they used when assigning flags.
683 Implements ticket 8151.
685 o Major bugfixes (directory authorities):
686 - Stop marking every relay as having been down for one hour every
687 time we restart a directory authority. These artificial downtimes
688 were messing with our Stable and Guard flag calculations. Fixes
689 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
691 o Major bugfixes (hidden services):
692 - Allow hidden service authentication to succeed again. When we
693 refactored the hidden service introduction code back
694 in 0.2.4.1-alpha, we didn't update the code that checks
695 whether authentication information is present, causing all
696 authentication checks to return "false". Fix for bug 8207; bugfix
697 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
699 o Minor features (relays, bridges):
700 - Make bridge relays check once a minute for whether their IP
701 address has changed, rather than only every 15 minutes. Resolves
703 - Refactor resolve_my_address() so it returns the method by which we
704 decided our public IP address (explicitly configured, resolved from
705 explicit hostname, guessed from interfaces, learned by gethostname).
706 Now we can provide more helpful log messages when a relay guesses
707 its IP address incorrectly (e.g. due to unexpected lines in
708 /etc/hosts). Resolves ticket 2267.
709 - Teach bridge-using clients to avoid 0.2.2 bridges when making
710 microdescriptor-related dir requests, and only fall back to normal
711 descriptors if none of their bridges can handle microdescriptors
712 (as opposed to the fix in ticket 4013, which caused them to fall
713 back to normal descriptors if *any* of their bridges preferred
714 them). Resolves ticket 4994.
715 - Randomize the lifetime of our SSL link certificate, so censors can't
716 use the static value for filtering Tor flows. Resolves ticket 8443;
717 related to ticket 4014 which was included in 0.2.2.33.
719 o Minor features (portability):
720 - Tweak the curve25519-donna*.c implementations to tolerate systems
721 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
722 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
723 the signs of types during autoconf. This is better than our old
724 approach, which didn't work when cross-compiling.
725 - Detect the sign of enum values, rather than assuming that MSC is the
726 only compiler where enum types are all signed. Fixes bug 7727;
727 bugfix on 0.2.4.10-alpha.
729 o Minor features (other):
730 - Say "KBytes" rather than "KB" in the man page (for various values
731 of K), to further reduce confusion about whether Tor counts in
732 units of memory or fractions of units of memory. Resolves ticket 7054.
733 - Clear the high bit on curve25519 public keys before passing them to
734 our backend, in case we ever wind up using a backend that doesn't do
735 so itself. If we used such a backend, and *didn't* clear the high bit,
736 we could wind up in a situation where users with such backends would
737 be distinguishable from users without. Fixes bug 8121; bugfix on
739 - Update to the March 6 2013 Maxmind GeoLite Country database.
741 o Minor bugfixes (clients):
742 - When we receive a RELAY_END cell with the reason DONE, or with no
743 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
744 status as "connection refused". Previously we reported these cases
745 as success but then immediately closed the connection. Fixes bug
746 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
747 - Downgrade an assertion in connection_ap_expire_beginning to an
748 LD_BUG message. The fix for bug 8024 should prevent this message
749 from displaying, but just in case, a warn that we can diagnose
750 is better than more assert crashes. Fixes bug 8065; bugfix on
752 - Lower path use bias thresholds to .80 for notice and .60 for warn.
753 Also make the rate limiting flags for the path use bias log messages
754 independent from the original path bias flags. Fixes bug 8161;
755 bugfix on 0.2.4.10-alpha.
757 o Minor bugfixes (relays):
758 - Stop trying to resolve our hostname so often (e.g. every time we
759 think about doing a directory fetch). Now we reuse the cached
760 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
761 and 2410 (bugfix on 0.1.2.2-alpha).
762 - Stop sending a stray "(null)" in some cases for the server status
763 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
765 - When choosing which stream on a formerly stalled circuit to wake
766 first, make better use of the platform's weak RNG. Previously,
767 we had been using the % ("modulo") operator to try to generate a
768 1/N chance of picking each stream, but this behaves badly with
769 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
771 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
772 Irix's random() only return 15 bits; Solaris's random() returns more
773 bits but its RAND_MAX says it only returns 15, and so on. Motivated
774 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
776 o Minor bugfixes (directory authorities):
777 - Directory authorities now use less space when formatting identical
778 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
781 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
782 - Avoid leaking memory if we fail to compute a consensus signature
783 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
784 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
786 - Fix a memory leak during safe-cookie controller authentication.
787 Bugfix on 0.2.3.13-alpha.
788 - Avoid memory leak of IPv6 policy content if we fail to format it into
789 a router descriptor. Bugfix on 0.2.4.7-alpha.
791 o Minor bugfixes (other code correctness issues):
792 - Avoid a crash if we fail to generate an extrainfo descriptor.
793 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
795 - When detecting the largest possible file descriptor (in order to
796 close all file descriptors when launching a new program), actually
797 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
798 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
800 - Fix a copy-and-paste error when adding a missing A1 to a routerset
801 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
802 Bugfix on 0.2.4.10-alpha.
803 - Fix an impossible-to-trigger integer overflow when estimating how
804 long our onionskin queue would take. (This overflow would require us
805 to accept 4 million onionskins before processing 100 of them.) Fixes
806 bug 8210; bugfix on 0.2.4.10-alpha.
808 o Code simplification and refactoring:
809 - Add a wrapper function for the common "log a message with a
813 Changes in version 0.2.4.10-alpha - 2013-02-04
814 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
815 certain attacks that flood the network with relays; changes the queue
816 for circuit create requests from a sized-based limit to a time-based
817 limit; resumes building with MSVC on Windows; and fixes a wide variety
820 o Major bugfixes (directory authority):
821 - When computing directory thresholds, ignore any rejected-as-sybil
822 nodes during the computation so that they can't influence Fast,
823 Guard, etc. (We should have done this for proposal 109.) Fixes
825 - When marking a node as a likely sybil, reset its uptime metrics
826 to zero, so that it cannot time towards getting marked as Guard,
827 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
831 - When a TLS write is partially successful but incomplete, remember
832 that the flushed part has been flushed, and notice that bytes were
833 actually written. Reported and fixed pseudonymously. Fixes bug
834 7708; bugfix on Tor 0.1.0.5-rc.
835 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
836 ID: these could be used to create unexpected streams and circuits
837 which would count as "present" to some parts of Tor but "absent"
838 to others, leading to zombie circuits and streams or to a bandwidth
839 denial-of-service. Fixes bug 7889; bugfix on every released version
840 of Tor. Reported by "oftc_must_be_destroyed".
841 - Rename all macros in our local copy of queue.h to begin with "TOR_".
842 This change seems the only good way to permanently prevent conflicts
843 with queue.h on various operating systems. Fixes bug 8107; bugfix
846 o Major features (relay):
847 - Instead of limiting the number of queued onionskins (aka circuit
848 create requests) to a fixed, hard-to-configure number, we limit
849 the size of the queue based on how many we expect to be able to
850 process in a given amount of time. We estimate the time it will
851 take to process an onionskin based on average processing time
852 of previous onionskins. Closes ticket 7291. You'll never have to
853 configure MaxOnionsPending again.
855 o Major features (portability):
856 - Resume building correctly with MSVC and Makefile.nmake. This patch
857 resolves numerous bugs and fixes reported by ultramage, including
858 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
859 - Make the ntor and curve25519 code build correctly with MSVC.
860 Fix on 0.2.4.8-alpha.
863 - When directory authorities are computing thresholds for flags,
864 never let the threshold for the Fast flag fall below 4096
865 bytes. Also, do not consider nodes with extremely low bandwidths
866 when deciding thresholds for various directory flags. This change
867 should raise our threshold for Fast relays, possibly in turn
868 improving overall network performance; see ticket 1854. Resolves
870 - The Tor client now ignores sub-domain components of a .onion
871 address. This change makes HTTP "virtual" hosting
872 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
873 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
874 hosted on the same hidden service. Implements proposal 204.
875 - We compute the overhead from passing onionskins back and forth to
876 cpuworkers, and report it when dumping statistics in response to
877 SIGUSR1. Supports ticket 7291.
879 o Minor features (path selection):
880 - When deciding whether we have enough descriptors to build circuits,
881 instead of looking at raw relay counts, look at which fraction
882 of (bandwidth-weighted) paths we're able to build. This approach
883 keeps clients from building circuits if their paths are likely to
884 stand out statistically. The default fraction of paths needed is
885 taken from the consensus directory; you can override it with the
886 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
887 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
888 and we have GeoIP information, also exclude all nodes with unknown
889 countries "??" and "A1". This behavior is controlled by the
890 new GeoIPExcludeUnknown option: you can make such nodes always
891 excluded with "GeoIPExcludeUnknown 1", and disable the feature
892 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
893 gets you the default behavior. Implements feature 7706.
894 - Path Use Bias: Perform separate accounting for successful circuit
895 use. Keep separate statistics on stream attempt rates versus stream
896 success rates for each guard. Provide configurable thresholds to
897 determine when to emit log messages or disable use of guards that
898 fail too many stream attempts. Resolves ticket 7802.
900 o Minor features (log messages):
901 - When learning a fingerprint for a bridge, log its corresponding
902 transport type. Implements ticket 7896.
903 - Improve the log message when "Bug/attack: unexpected sendme cell
904 from client" occurs, to help us track bug 8093.
907 - Remove a couple of extraneous semicolons that were upsetting the
908 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
909 bugfix on 0.2.2.1-alpha.
910 - Remove a source of rounding error during path bias count scaling;
911 don't count cannibalized circuits as used for path bias until we
912 actually try to use them; and fix a circuit_package_relay_cell()
913 warning message about n_chan==NULL. Fixes bug 7802.
914 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
915 actually link against nacl when we're configured to use it. Fixes
916 bug 7972; bugfix on 0.2.4.8-alpha.
917 - Compile correctly with the --disable-curve25519 option. Fixes
918 bug 8153; bugfix on 0.2.4.8-alpha.
920 o Build improvements:
921 - Do not report status verbosely from autogen.sh unless the -v flag
922 is specified. Fixes issue 4664. Patch from Onizuka.
923 - Replace all calls to snprintf() outside of src/ext with
924 tor_snprintf(). Also remove the #define to replace snprintf with
925 _snprintf on Windows; they have different semantics, and all of
926 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
927 - Try to detect if we are ever building on a platform where
928 memset(...,0,...) does not set the value of a double to 0.0. Such
929 platforms are permitted by the C standard, though in practice
930 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
931 currently support them, but it's better to detect them and fail
932 than to perform erroneously.
935 - Stop exporting estimates of v2 and v3 directory traffic shares
936 in extrainfo documents. They were unneeded and sometimes inaccurate.
937 Also stop exporting any v2 directory request statistics. Resolves
939 - Drop support for detecting and warning about versions of Libevent
940 before 1.3e. Nothing reasonable ships with them any longer;
941 warning the user about them shouldn't be needed. Resolves ticket
944 o Code simplifications and refactoring:
945 - Rename "isin" functions to "contains", for grammar. Resolves
947 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
948 with the natural logarithm function from the system libm. Resolves
952 Changes in version 0.2.4.9-alpha - 2013-01-15
953 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
957 - Fix backward compatibility logic when receiving an embedded ntor
958 handshake tunneled in a CREATE cell. This clears up the "Bug:
959 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
963 Changes in version 0.2.4.8-alpha - 2013-01-14
964 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
965 risks, adds a new stronger and faster circuit handshake, and offers
966 stronger and faster link encryption when both sides support it.
969 - Preliminary support for directory guards (proposal 207): when
970 possible, clients now use their entry guards for non-anonymous
971 directory requests. This can help prevent client enumeration. Note
972 that this behavior only works when we have a usable consensus
973 directory, and when options about what to download are more or less
974 standard. In the future we should re-bootstrap from our guards,
975 rather than re-bootstrapping from the preconfigured list of
976 directory sources that ships with Tor. Resolves ticket 6526.
977 - Tor relays and clients now support a better CREATE/EXTEND cell
978 format, allowing the sender to specify multiple address, identity,
979 and handshake types. Implements Robert Ransom's proposal 200;
982 o Major features (new circuit handshake):
983 - Tor now supports a new circuit extension handshake designed by Ian
984 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
985 circuit extension handshake, later called "TAP", was a bit slow
986 (especially on the relay side), had a fragile security proof, and
987 used weaker keys than we'd now prefer. The new circuit handshake
988 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
989 function, making it significantly more secure than the older
990 handshake, and significantly faster. Tor can use one of two built-in
991 pure-C curve25519-donna implementations by Adam Langley, or it
992 can link against the "nacl" library for a tuned version if present.
994 The built-in version is very fast for 64-bit systems when building
995 with GCC. The built-in 32-bit version is still faster than the
996 old TAP protocol, but using libnacl is better on most such hosts.
998 Clients don't currently use this protocol by default, since
999 comparatively few clients support it so far. To try it, set
1000 UseNTorHandshake to 1.
1002 Implements proposal 216; closes ticket 7202.
1004 o Major features (better link encryption):
1005 - Relays can now enable the ECDHE TLS ciphersuites when available
1006 and appropriate. These ciphersuites let us negotiate forward-secure
1007 TLS secret keys more safely and more efficiently than with our
1008 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
1009 public relays prefer the (faster) P224 group, and bridges prefer
1010 the (more common) P256 group; you can override this with the
1013 Enabling these ciphers was a little tricky, since for a long time,
1014 clients had been claiming to support them without actually doing
1015 so, in order to foil fingerprinting. But with the client-side
1016 implementation of proposal 198 in 0.2.3.17-beta, clients can now
1017 match the ciphers from recent Firefox versions *and* list the
1018 ciphers they actually mean, so relays can believe such clients
1019 when they advertise ECDHE support in their TLS ClientHello messages.
1021 This feature requires clients running 0.2.3.17-beta or later,
1022 and requires both sides to be running OpenSSL 1.0.0 or later
1023 with ECC support. OpenSSL 1.0.1, with the compile-time option
1024 "enable-ec_nistp_64_gcc_128", is highly recommended.
1026 Implements the relay side of proposal 198; closes ticket 7200.
1029 - Avoid crashing when, as a relay without IPv6-exit support, a
1030 client insists on getting an IPv6 address or nothing. Fixes bug
1031 7814; bugfix on 0.2.4.7-alpha.
1034 - Improve circuit build timeout handling for hidden services.
1035 In particular: adjust build timeouts more accurately depending
1036 upon the number of hop-RTTs that a particular circuit type
1037 undergoes. Additionally, launch intro circuits in parallel
1038 if they timeout, and take the first one to reply as valid.
1039 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
1040 separate error codes; or at least, don't break for that reason.
1041 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
1042 - Update to the January 2 2013 Maxmind GeoLite Country database.
1044 o Minor features (testing):
1045 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
1046 (P-256) Diffie-Hellman handshakes to src/or/bench.
1047 - Add benchmark functions to test onion handshake performance.
1049 o Minor features (path bias detection):
1050 - Alter the Path Bias log messages to be more descriptive in terms
1051 of reporting timeouts and other statistics.
1052 - Create three levels of Path Bias log messages, as opposed to just
1053 two. These are configurable via consensus as well as via the torrc
1054 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
1055 The default values are 0.70, 0.50, and 0.30 respectively.
1056 - Separate the log message levels from the decision to drop guards,
1057 which also is available via torrc option PathBiasDropGuards.
1058 PathBiasDropGuards still defaults to 0 (off).
1059 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
1060 in combination with PathBiasExtremeRate.
1061 - Increase the default values for PathBiasScaleThreshold and
1062 PathBiasCircThreshold from (200, 20) to (300, 150).
1063 - Add in circuit usage accounting to path bias. If we try to use a
1064 built circuit but fail for any reason, it counts as path bias.
1065 Certain classes of circuits where the adversary gets to pick your
1066 destination node are exempt from this accounting. Usage accounting
1067 can be specifically disabled via consensus parameter or torrc.
1068 - Convert all internal path bias state to double-precision floating
1069 point, to avoid roundoff error and other issues.
1070 - Only record path bias information for circuits that have completed
1071 *two* hops. Assuming end-to-end tagging is the attack vector, this
1072 makes us more resilient to ambient circuit failure without any
1073 detection capability loss.
1075 o Minor bugfixes (log messages):
1076 - Rate-limit the "No circuits are opened. Relaxed timeout for a
1077 circuit with channel state open..." message to once per hour to
1078 keep it from filling the notice logs. Mitigates bug 7799 but does
1079 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
1080 - Avoid spurious warnings when configuring multiple client ports of
1081 which only some are nonlocal. Previously, we had claimed that some
1082 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
1085 o Code simplifications and refactoring:
1086 - Get rid of a couple of harmless clang warnings, where we compared
1087 enums to ints. These warnings are newly introduced in clang 3.2.
1088 - Split the onion.c file into separate modules for the onion queue
1089 and the different handshakes it supports.
1090 - Remove the marshalling/unmarshalling code for sending requests to
1091 cpuworkers over a socket, and instead just send structs. The
1092 recipient will always be the same Tor binary as the sender, so
1093 any encoding is overkill.
1096 Changes in version 0.2.4.7-alpha - 2012-12-24
1097 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
1098 directory mirrors for more robust bootstrapping; fixes more issues where
1099 clients with changing network conditions refuse to make any circuits;
1100 adds initial support for exiting to IPv6 addresses; resumes being able
1101 to update our GeoIP database, and includes the geoip6 file this time;
1102 turns off the client-side DNS cache by default due to privacy risks;
1103 and fixes a variety of other issues.
1105 o Major features (client resilience):
1106 - Add a new "FallbackDir" torrc option to use when we can't use
1107 a directory mirror from the consensus (either because we lack a
1108 consensus, or because they're all down). Currently, all authorities
1109 are fallbacks by default, and there are no other default fallbacks,
1110 but that will change. This option will allow us to give clients a
1111 longer list of servers to try to get a consensus from when first
1112 connecting to the Tor network, and thereby reduce load on the
1113 directory authorities. Implements proposal 206, "Preconfigured
1114 directory sources for bootstrapping". We also removed the old
1115 "FallbackNetworkstatus" option, since we never got it working well
1116 enough to use it. Closes bug 572.
1117 - If we have no circuits open, use a relaxed timeout (the
1118 95-percentile cutoff) until a circuit succeeds. This heuristic
1119 should allow Tor to succeed at building circuits even when the
1120 network connection drastically changes. Should help with bug 3443.
1122 o Major features (IPv6):
1123 - Tor now has (alpha) support for exiting to IPv6 addresses. To
1124 enable it as an exit node, make sure that you have IPv6
1125 connectivity, then set the IPv6Exit flag to 1. Also make sure your
1126 exit policy reads as you would like: the address * applies to all
1127 address families, whereas *4 is IPv4 address only, and *6 is IPv6
1128 addresses only. On the client side, you'll need to wait until the
1129 authorities have upgraded, wait for enough exits to support IPv6,
1130 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
1131 ticket 5547, implements proposal 117 as revised in proposal 208.
1133 We DO NOT recommend that clients with actual anonymity needs start
1134 using IPv6 over Tor yet, since not enough exits support it yet.
1136 o Major features (geoip database):
1137 - Maxmind began labelling Tor relays as being in country "A1",
1138 which breaks by-country node selection inside Tor. Now we use a
1139 script to replace "A1" ("Anonymous Proxy") entries in our geoip
1140 file with real country codes. This script fixes about 90% of "A1"
1141 entries automatically and uses manual country code assignments to
1142 fix the remaining 10%. See src/config/README.geoip for details.
1143 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
1144 Country database, as modified above.
1146 o Major bugfixes (client-side DNS):
1147 - Turn off the client-side DNS cache by default. Updating and using
1148 the DNS cache is now configurable on a per-client-port
1149 level. SOCKSPort, DNSPort, etc lines may now contain
1150 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
1151 cache these types of DNS answers when we receive them from an
1152 exit node in response to an application request on this port, and
1153 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
1154 cached DNS answers of these types, we shouldn't use them. It's
1155 potentially risky to use cached DNS answers at the client, since
1156 doing so can indicate to one exit what answers we've gotten
1157 for DNS lookups in the past. With IPv6, this becomes especially
1158 problematic. Using cached DNS answers for requests on the same
1159 circuit would present less linkability risk, since all traffic
1160 on a circuit is already linkable, but it would also provide
1161 little performance benefit: the exit node caches DNS replies
1162 too. Implements a simplified version of Proposal 205. Implements
1165 o Major bugfixes (other):
1166 - Alter circuit build timeout measurement to start at the point
1167 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
1168 initialization). This should make our timeout measurements more
1169 uniform. Previously, we were sometimes including ORconn setup time
1170 in our circuit build time measurements. Should resolve bug 3443.
1171 - Fix an assertion that could trigger in hibernate_go_dormant() when
1172 closing an or_connection_t: call channel_mark_for_close() rather
1173 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
1175 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
1176 7655; bugfix on 0.2.4.6-alpha.
1179 - Add a new torrc option "ServerTransportListenAddr" to let bridge
1180 operators select the address where their pluggable transports will
1181 listen for connections. Resolves ticket 7013.
1182 - Allow an optional $ before the node identity digest in the
1183 controller command GETINFO ns/id/<identity>, for consistency with
1184 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
1185 - Log packaged cell fullness as part of the heartbeat message.
1186 Diagnosis to try to determine the extent of bug 7743.
1188 o Minor features (IPv6):
1189 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
1190 prefer to hand out virtual IPv6 addresses, since there are more of
1191 them and we can't run out. To override this behavior and make IPv4
1192 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
1193 or DNSPort you're using for resolving. Implements ticket 7571.
1194 - AutomapHostsOnResolve responses are now randomized, to avoid
1195 annoying situations where Tor is restarted and applications
1196 connect to the wrong addresses.
1197 - Never try more than 1000 times to pick a new virtual address when
1198 AutomapHostsOnResolve is set. That's good enough so long as we
1199 aren't close to handing out our entire virtual address space;
1200 if you're getting there, it's best to switch to IPv6 virtual
1204 - The ADDRMAP command can no longer generate an ill-formed error
1205 code on a failed MAPADDRESS. It now says "internal" rather than
1206 an English sentence fragment with spaces in the middle. Bugfix on
1208 - Fix log messages and comments to avoid saying "GMT" when we mean
1209 "UTC". Fixes bug 6113.
1210 - Compile on win64 using mingw64. Fixes bug 7260; patches from
1212 - Fix a crash when debugging unit tests on Windows: deallocate a
1213 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
1214 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
1217 - The DirServer option is now DirAuthority, for consistency with
1218 current naming patterns. You can still use the old DirServer form.
1220 o Code simplification and refactoring:
1221 - Move the client-side address-map/virtual-address/DNS-cache code
1222 out of connection_edge.c into a new addressmap.c module.
1223 - Remove unused code for parsing v1 directories and "running routers"
1224 documents. Fixes bug 6887.
1227 Changes in version 0.2.3.25 - 2012-11-19
1228 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
1229 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
1230 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
1231 programmer, and friend. Unstinting in his dedication to the cause of
1232 freedom, he inspired and helped many of us as we began our work on
1233 anonymity, and inspires us still. Please honor his memory by writing
1234 software to protect people's freedoms, and by helping others to do so.
1236 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
1237 significantly reduced directory overhead (via microdescriptors),
1238 enormous crypto performance improvements for fast relays on new
1239 enough hardware, a new v3 TLS handshake protocol that can better
1240 resist fingerprinting, support for protocol obfuscation plugins (aka
1241 pluggable transports), better scalability for hidden services, IPv6
1242 support for bridges, performance improvements like allowing clients
1243 to skip the first round-trip on the circuit ("optimistic data") and
1244 refilling token buckets more often, a new "stream isolation" design
1245 to isolate different applications on different circuits, and many
1246 stability, security, and privacy fixes.
1249 - Tor tries to wipe potentially sensitive data after using it, so
1250 that if some subsequent security failure exposes Tor's memory,
1251 the damage will be limited. But we had a bug where the compiler
1252 was eliminating these wipe operations when it decided that the
1253 memory was no longer visible to a (correctly running) program,
1254 hence defeating our attempt at defense in depth. We fix that
1255 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1256 is unlikely to optimize away. Future versions of Tor may use
1257 a less ridiculously heavy approach for this. Fixes bug 7352.
1258 Reported in an article by Andrey Karpov.
1261 - Fix a harmless bug when opting against publishing a relay descriptor
1262 because DisableNetwork is set. Fixes bug 7464; bugfix on
1266 Changes in version 0.2.4.6-alpha - 2012-11-13
1267 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
1268 makes our defense-in-depth memory wiping more reliable, and begins to
1269 count IPv6 addresses in bridge statistics,
1272 - Fix an assertion failure that could occur when closing a connection
1273 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
1275 - Tor tries to wipe potentially sensitive data after using it, so
1276 that if some subsequent security failure exposes Tor's memory,
1277 the damage will be limited. But we had a bug where the compiler
1278 was eliminating these wipe operations when it decided that the
1279 memory was no longer visible to a (correctly running) program,
1280 hence defeating our attempt at defense in depth. We fix that
1281 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
1282 is unlikely to optimize away. Future versions of Tor may use
1283 a less ridiculously heavy approach for this. Fixes bug 7352.
1284 Reported in an article by Andrey Karpov.
1287 - Add GeoIP database for IPv6 addresses. The new config option
1289 - Bridge statistics now count bridge clients connecting over IPv6:
1290 bridge statistics files now list "bridge-ip-versions" and
1291 extra-info documents list "geoip6-db-digest". The control protocol
1292 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
1293 implementation by "shkoo", addressing ticket 5055.
1296 - Warn when we are binding low ports when hibernation is enabled;
1297 previously we had warned when we were _advertising_ low ports with
1298 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
1299 - Fix a harmless bug when opting against publishing a relay descriptor
1300 because DisableNetwork is set. Fixes bug 7464; bugfix on
1302 - Add warning message when a managed proxy dies during configuration.
1303 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
1304 - Fix a linking error when building tor-fw-helper without miniupnp.
1305 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
1306 - Check for closing an or_connection_t without going through correct
1307 channel functions; emit a warning and then call
1308 connection_or_close_for_error() so we don't assert as in bugs 7212
1310 - Compile correctly on compilers without C99 designated initializer
1311 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
1312 - Avoid a possible assert that can occur when channel_send_destroy() is
1313 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
1314 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
1315 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
1316 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
1317 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
1319 o Code simplification and refactoring:
1320 - Start using OpenBSD's implementation of queue.h, so that we don't
1321 need to hand-roll our own pointer and list structures whenever we
1322 need them. (We can't rely on a sys/queue.h, since some operating
1323 systems don't have them, and the ones that do have them don't all
1324 present the same extensions.)
1327 Changes in version 0.2.4.5-alpha - 2012-10-25
1328 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
1329 two important security vulnerabilities that could lead to remotely
1330 triggerable relay crashes, fix a major bug that was preventing clients
1331 from choosing suitable exit nodes, and refactor some of our code.
1333 o Major bugfixes (security, also in 0.2.3.24-rc):
1334 - Fix a group of remotely triggerable assertion failures related to
1335 incorrect link protocol negotiation. Found, diagnosed, and fixed
1336 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1338 - Fix a denial of service attack by which any directory authority
1339 could crash all the others, or by which a single v2 directory
1340 authority could crash everybody downloading v2 directory
1341 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1343 o Major bugfixes (also in 0.2.3.24-rc):
1344 - When parsing exit policy summaries from microdescriptors, we had
1345 previously been ignoring the last character in each one, so that
1346 "accept 80,443,8080" would be treated by clients as indicating
1347 a node that allows access to ports 80, 443, and 808. That would
1348 lead to clients attempting connections that could never work,
1349 and ignoring exit nodes that would support their connections. Now
1350 clients parse these exit policy summaries correctly. Fixes bug 7192;
1351 bugfix on 0.2.3.1-alpha.
1353 o Minor bugfixes (also in 0.2.3.24-rc):
1354 - Clients now consider the ClientRejectInternalAddresses config option
1355 when using a microdescriptor consensus stanza to decide whether
1356 an exit relay would allow exiting to an internal address. Fixes
1357 bug 7190; bugfix on 0.2.3.1-alpha.
1360 - Only disable TLS session ticket support when running as a TLS
1361 server. Now clients will blend better with regular Firefox
1362 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
1364 o Code simplification and refactoring:
1365 - Start using OpenBSD's implementation of queue.h (originally by
1367 - Move the entry node code from circuitbuild.c to its own file.
1368 - Move the circuit build timeout tracking code from circuitbuild.c
1372 Changes in version 0.2.3.24-rc - 2012-10-25
1373 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
1374 could lead to remotely triggerable relay crashes, and fixes
1375 a major bug that was preventing clients from choosing suitable exit
1378 o Major bugfixes (security):
1379 - Fix a group of remotely triggerable assertion failures related to
1380 incorrect link protocol negotiation. Found, diagnosed, and fixed
1381 by "some guy from France". Fix for CVE-2012-2250; bugfix on
1383 - Fix a denial of service attack by which any directory authority
1384 could crash all the others, or by which a single v2 directory
1385 authority could crash everybody downloading v2 directory
1386 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
1389 - When parsing exit policy summaries from microdescriptors, we had
1390 previously been ignoring the last character in each one, so that
1391 "accept 80,443,8080" would be treated by clients as indicating
1392 a node that allows access to ports 80, 443, and 808. That would
1393 lead to clients attempting connections that could never work,
1394 and ignoring exit nodes that would support their connections. Now
1395 clients parse these exit policy summaries correctly. Fixes bug 7192;
1396 bugfix on 0.2.3.1-alpha.
1399 - Clients now consider the ClientRejectInternalAddresses config option
1400 when using a microdescriptor consensus stanza to decide whether
1401 an exit relay would allow exiting to an internal address. Fixes
1402 bug 7190; bugfix on 0.2.3.1-alpha.
1405 Changes in version 0.2.4.4-alpha - 2012-10-20
1406 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
1407 vulnerability introduced by a change in OpenSSL, fixes a remotely
1408 triggerable assert, and adds new channel_t and circuitmux_t abstractions
1409 that will make it easier to test new connection transport and cell
1410 scheduling algorithms.
1412 o New directory authorities (also in 0.2.3.23-rc):
1413 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1414 authority. Closes ticket 5749.
1416 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
1417 - Disable TLS session tickets. OpenSSL's implementation was giving
1418 our TLS session keys the lifetime of our TLS context objects, when
1419 perfect forward secrecy would want us to discard anything that
1420 could decrypt a link connection as soon as the link connection
1421 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1422 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1423 - Discard extraneous renegotiation attempts once the V3 link
1424 protocol has been initiated. Failure to do so left us open to
1425 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1426 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1428 o Internal abstraction features:
1429 - Introduce new channel_t abstraction between circuits and
1430 or_connection_t to allow for implementing alternate OR-to-OR
1431 transports. A channel_t is an abstract object which can either be a
1432 cell-bearing channel, which is responsible for authenticating and
1433 handshaking with the remote OR and transmitting cells to and from
1434 it, or a listening channel, which spawns new cell-bearing channels
1435 at the request of remote ORs. Implements part of ticket 6465.
1436 - Also new is the channel_tls_t subclass of channel_t, adapting it
1437 to the existing or_connection_t code. The V2/V3 protocol handshaking
1438 code which formerly resided in command.c has been moved below the
1439 channel_t abstraction layer and may be found in channeltls.c now.
1440 Implements the rest of ticket 6465.
1441 - Introduce new circuitmux_t storing the queue of circuits for
1442 a channel; this encapsulates and abstracts the queue logic and
1443 circuit selection policy, and allows the latter to be overridden
1444 easily by switching out a policy object. The existing EWMA behavior
1445 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
1447 o Required libraries:
1448 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
1449 strongly recommended.
1452 - Warn users who run hidden services on a Tor client with
1453 UseEntryGuards disabled that their hidden services will be
1454 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
1455 attack which motivated Tor to support entry guards in the first
1456 place). Resolves ticket 6889.
1457 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
1458 dhill. Resolves ticket 6982.
1459 - Option OutboundBindAddress can be specified multiple times and
1460 accepts IPv6 addresses. Resolves ticket 6876.
1462 o Minor bugfixes (also in 0.2.3.23-rc):
1463 - Don't serve or accept v2 hidden service descriptors over a
1464 relay's DirPort. It's never correct to do so, and disabling it
1465 might make it more annoying to exploit any bugs that turn up in the
1466 descriptor-parsing code. Fixes bug 7149.
1467 - Fix two cases in src/or/transports.c where we were calling
1468 fmt_addr() twice in a parameter list. Bug found by David
1469 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1470 - Fix memory leaks whenever we logged any message about the "path
1471 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1472 - When relays refuse a "create" cell because their queue of pending
1473 create cells is too big (typically because their cpu can't keep up
1474 with the arrival rate), send back reason "resource limit" rather
1475 than reason "internal", so network measurement scripts can get a
1476 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
1479 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
1480 - Free some more still-in-use memory at exit, to make hunting for
1481 memory leaks easier. Resolves bug 7029.
1482 - When a Tor client gets a "truncated" relay cell, the first byte of
1483 its payload specifies why the circuit was truncated. We were
1484 ignoring this 'reason' byte when tearing down the circuit, resulting
1485 in the controller not being told why the circuit closed. Now we
1486 pass the reason from the truncated cell to the controller. Bugfix
1487 on 0.1.2.3-alpha; fixes bug 7039.
1488 - Downgrade "Failed to hand off onionskin" messages to "debug"
1489 severity, since they're typically redundant with the "Your computer
1490 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
1491 - Make clients running with IPv6 bridges connect over IPv6 again,
1492 even without setting new config options ClientUseIPv6 and
1493 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
1494 - Use square brackets around IPv6 addresses in numerous places
1495 that needed them, including log messages, HTTPS CONNECT proxy
1496 requests, TransportProxy statefile entries, and pluggable transport
1497 extra-info lines. Fixes bug 7011; patch by David Fifield.
1499 o Code refactoring and cleanup:
1500 - Source files taken from other packages now reside in src/ext;
1501 previously they were scattered around the rest of Tor.
1502 - Avoid use of reserved identifiers in our C code. The C standard
1503 doesn't like us declaring anything that starts with an
1504 underscore, so let's knock it off before we get in trouble. Fix
1505 for bug 1031; bugfix on the first Tor commit.
1508 Changes in version 0.2.3.23-rc - 2012-10-20
1509 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
1510 vulnerability introduced by a change in OpenSSL, and fixes a variety
1511 of smaller bugs in preparation for the release.
1513 o New directory authorities:
1514 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
1515 authority. Closes ticket 5749.
1517 o Major bugfixes (security/privacy):
1518 - Disable TLS session tickets. OpenSSL's implementation was giving
1519 our TLS session keys the lifetime of our TLS context objects, when
1520 perfect forward secrecy would want us to discard anything that
1521 could decrypt a link connection as soon as the link connection
1522 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
1523 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
1524 - Discard extraneous renegotiation attempts once the V3 link
1525 protocol has been initiated. Failure to do so left us open to
1526 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
1527 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
1530 - Fix a possible crash bug when checking for deactivated circuits
1531 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1532 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1534 o Minor bugfixes (on 0.2.3.x):
1535 - Fix two cases in src/or/transports.c where we were calling
1536 fmt_addr() twice in a parameter list. Bug found by David
1537 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
1538 - Convert an assert in the pathbias code to a log message. The assert
1539 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1540 bugfix on 0.2.3.17-beta.
1541 - Fix memory leaks whenever we logged any message about the "path
1542 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
1544 o Minor bugfixes (on 0.2.2.x and earlier):
1545 - Don't serve or accept v2 hidden service descriptors over a relay's
1546 DirPort. It's never correct to do so, and disabling it might
1547 make it more annoying to exploit any bugs that turn up in the
1548 descriptor-parsing code. Fixes bug 7149.
1549 - When relays refuse a "create" cell because their queue of pending
1550 create cells is too big (typically because their cpu can't keep up
1551 with the arrival rate), send back reason "resource limit" rather
1552 than reason "internal", so network measurement scripts can get a
1553 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
1554 - Correct file sizes when reading binary files on Cygwin, to avoid
1555 a bug where Tor would fail to read its state file. Fixes bug 6844;
1556 bugfix on 0.1.2.7-alpha.
1557 - Avoid undefined behaviour when parsing the list of supported
1558 rendezvous/introduction protocols in a hidden service descriptor.
1559 Previously, Tor would have confused (as-yet-unused) protocol version
1560 numbers greater than 32 with lower ones on many platforms. Fixes
1561 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1563 o Documentation fixes:
1564 - Clarify that hidden services are TCP only. Fixes bug 6024.
1567 Changes in version 0.2.4.3-alpha - 2012-09-22
1568 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
1569 assertion, resumes letting relays test reachability of their DirPort,
1570 and cleans up a bunch of smaller bugs.
1573 - Fix an assertion failure in tor_timegm() that could be triggered
1574 by a badly formatted directory object. Bug found by fuzzing with
1575 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1578 - Fix a possible crash bug when checking for deactivated circuits
1579 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
1580 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
1581 - Allow routers to detect that their own DirPorts are running. When
1582 we removed support for versions_supports_begindir, we also
1583 accidentally removed the mechanism we used to self-test our
1584 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
1585 bugfix on 0.2.4.2-alpha.
1587 o Security features:
1588 - Switch to a completely time-invariant approach for picking nodes
1589 weighted by bandwidth. Our old approach would run through the
1590 part of the loop after it had made its choice slightly slower
1591 than it ran through the part of the loop before it had made its
1592 choice. Addresses ticket 6538.
1593 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
1594 by tor2web clients allows hidden services to identity tor2web
1595 clients through their repeated selection of the same rendezvous
1596 and introduction point circuit endpoints (their guards). Resolves
1600 - Enable Tor to read configuration, state, and key information from
1601 a FIFO. Previously Tor would only read from files with a positive
1602 stat.st_size. Code from meejah; fixes bug 6044.
1605 - Correct file sizes when reading binary files on Cygwin, to avoid
1606 a bug where Tor would fail to read its state file. Fixes bug 6844;
1607 bugfix on 0.1.2.7-alpha.
1608 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
1609 bugfix on 0.2.0.3-alpha.
1610 - When complaining about a client port on a public address, log
1611 which address we're complaining about. Fixes bug 4020; bugfix on
1612 0.2.3.3-alpha. Patch by Tom Fitzhenry.
1613 - Convert an assert in the pathbias code to a log message. The assert
1614 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
1615 bugfix on 0.2.3.17-beta.
1616 - Our new buildsystem was overzealous about rebuilding manpages: it
1617 would rebuild them all whenever any one of them changed. Now our
1618 dependency checking should be correct. Fixes bug 6843; bugfix on
1620 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
1621 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
1622 - Correct log printout about which address family is preferred
1623 when connecting to a bridge with both an IPv4 and IPv6 OR port.
1624 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
1626 o Minor bugfixes (code cleanliness):
1627 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
1628 with large values. This situation was untriggered, but nevertheless
1629 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
1630 - Reject consensus votes with more than 64 known-flags. We aren't even
1631 close to that limit yet, and our code doesn't handle it correctly.
1632 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
1633 - Avoid undefined behaviour when parsing the list of supported
1634 rendezvous/introduction protocols in a hidden service descriptor.
1635 Previously, Tor would have confused (as-yet-unused) protocol version
1636 numbers greater than 32 with lower ones on many platforms. Fixes
1637 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
1638 - Fix handling of rendezvous client authorization types over 8.
1639 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
1640 - Fix building with older versions of GCC (2.95, for one) that don't
1641 like preprocessor directives inside macro arguments. Found by
1642 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
1643 - Switch weighted node selection rule from using a list of doubles
1644 to using a list of int64_t. This change should make the process
1645 slightly easier to debug and maintain. Needed to finish ticket 6538.
1647 o Code simplification and refactoring:
1648 - Move the generic "config" code into a new file, and have "config.c"
1649 hold only torrc- and state-related code. Resolves ticket 6823.
1650 - Move the core of our "choose a weighted element at random" logic
1651 into its own function, and give it unit tests. Now the logic is
1652 testable, and a little less fragile too.
1653 - Removed the testing_since field of node_t, which hasn't been used
1654 for anything since 0.2.0.9-alpha.
1656 o Documentation fixes:
1657 - Clarify that hidden services are TCP only. Fixes bug 6024.
1658 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
1662 Changes in version 0.2.3.22-rc - 2012-09-11
1663 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
1667 - Fix an assertion failure in tor_timegm() that could be triggered
1668 by a badly formatted directory object. Bug found by fuzzing with
1669 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1672 - Avoid segfault when starting up having run with an extremely old
1673 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1677 Changes in version 0.2.2.39 - 2012-09-11
1678 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
1682 - Fix an assertion failure in tor_timegm() that could be triggered
1683 by a badly formatted directory object. Bug found by fuzzing with
1684 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
1685 - Do not crash when comparing an address with port value 0 to an
1686 address policy. This bug could have been used to cause a remote
1687 assertion failure by or against directory authorities, or to
1688 allow some applications to crash clients. Fixes bug 6690; bugfix
1692 Changes in version 0.2.4.2-alpha - 2012-09-10
1693 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
1694 raises the default rate limiting even more, and makes the bootstrapping
1695 log messages less noisy.
1698 - Automatically forward the TCP ports of pluggable transport
1699 proxies using tor-fw-helper if PortForwarding is enabled. Implements
1703 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
1704 to 1GB/1GB. The previous defaults were intended to be "basically
1705 infinite", but it turns out they're now limiting our 100mbit+
1706 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
1707 last time we raised it).
1710 - Detect when we're running with a version of OpenSSL other than the
1711 one we compiled with. This has occasionally given people hard-to-
1713 - Log fewer lines at level "notice" about our OpenSSL and Libevent
1714 versions and capabilities when everything is going right. Resolves
1715 part of ticket 6736.
1716 - Directory authorities no long accept descriptors for any version of
1717 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
1718 These versions are insecure, unsupported, or both. Implements
1722 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
1723 to start with a triple-underscore so the controller won't touch it.
1724 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
1725 - Avoid segfault when starting up having run with an extremely old
1726 version of Tor and parsing its state file. Fixes bug 6801; bugfix
1728 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
1729 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
1730 - Don't follow the NULL pointer if microdescriptor generation fails.
1731 (This does not appear to be triggerable, but it's best to be safe.)
1732 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
1733 - Fix mis-declared dependencies on src/common/crypto.c and
1734 src/or/tor_main.c that could break out-of-tree builds under some
1735 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
1736 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
1737 6778; bugfix on 0.2.4.1-alpha.
1738 - Fix a harmless (in this case) build warning for implicitly
1739 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
1742 - Now that all versions before 0.2.2.x are disallowed, we no longer
1743 need to work around their missing features. Thus we can remove a
1744 bunch of compatibility code.
1747 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
1748 TCP ports to forward. In the past it only accepted two ports:
1749 the ORPort and the DirPort.
1752 Changes in version 0.2.4.1-alpha - 2012-09-05
1753 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
1754 bridgedb; lets relays use IPv6 addresses and directory authorities
1755 advertise them; and switches to a cleaner build interface.
1757 This is the first alpha release in a new series, so expect there to
1758 be bugs. Users who would rather test out a more stable branch should
1759 stay with 0.2.3.x for now.
1761 o Major features (bridges):
1762 - Bridges now report the pluggable transports they support to the
1763 bridge authority, so it can pass the supported transports on to
1764 bridgedb and/or eventually do reachability testing. Implements
1767 o Major features (IPv6):
1768 - Bridge authorities now accept IPv6 bridge addresses and include
1769 them in network status documents. Implements ticket 5534.
1770 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
1771 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
1772 to happen. Implements ticket 5535.
1773 - All kind of relays, not just bridges, can now advertise an IPv6
1774 OR port. Implements ticket 6362.
1775 - Directory authorities vote on IPv6 OR ports using the new consensus
1776 method 14. Implements ticket 6363.
1778 o Major features (build):
1779 - Switch to a nonrecursive Makefile structure. Now instead of each
1780 Makefile.am invoking other Makefile.am's, there is a master
1781 Makefile.am that includes the others. This change makes our build
1782 process slightly more maintainable, and improves parallelism for
1783 building with make -j. Original patch by Stewart Smith; various
1784 fixes by Jim Meyering.
1785 - Where available, we now use automake's "silent" make rules by
1786 default, so that warnings are easier to spot. You can get the old
1787 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
1789 o Minor features (code security and spec conformance):
1790 - Clear keys and key-derived material left on the stack in
1791 rendservice.c and rendclient.c. Check return value of
1792 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
1793 These fixes should make us more forward-secure against cold-boot
1794 attacks and the like. Fixes bug 2385.
1795 - Reject EXTEND cells sent to nonexistent streams. According to the
1796 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
1797 we were only checking for stream IDs that were currently in use.
1798 Found while hunting for more instances of bug 6271. Bugfix on
1799 0.0.2pre8, which introduced incremental circuit construction.
1801 o Minor features (streamlining);
1802 - No longer include the "opt" prefix when generating routerinfos
1803 or v2 directories: it has been needless since Tor 0.1.2. Closes
1805 - Remove some now-needless code that tried to aggressively flush
1806 OR connections as data was added to them. Since 0.2.0.1-alpha, our
1807 cell queue logic has saved us from the failure mode that this code
1808 was supposed to prevent. Removing this code will limit the number
1809 of baroque control flow paths through Tor's network logic. Reported
1810 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
1812 o Minor features (controller):
1813 - Add a "GETINFO signal/names" control port command. Implements
1815 - Provide default values for all options via "GETINFO config/defaults".
1816 Implements ticket 4971.
1818 o Minor features (IPv6):
1819 - New config option "AuthDirHasIPv6Connectivity 1" that directory
1820 authorities should set if they have IPv6 connectivity and want to
1821 do reachability tests for IPv6 relays. Implements feature 5974.
1822 - A relay with an IPv6 OR port now sends that address in NETINFO
1823 cells (in addition to its other address). Implements ticket 6364.
1825 o Minor features (log messages):
1826 - Omit the first heartbeat log message, because it never has anything
1827 useful to say, and it clutters up the bootstrapping messages.
1828 Resolves ticket 6758.
1829 - Don't log about reloading the microdescriptor cache at startup. Our
1830 bootstrap warnings are supposed to tell the user when there's a
1831 problem, and our bootstrap notices say when there isn't. Resolves
1832 ticket 6759; bugfix on 0.2.2.6-alpha.
1833 - Don't log "I learned some more directory information" when we're
1834 reading cached directory information. Reserve it for when new
1835 directory information arrives in response to a fetch. Resolves
1837 - Prevent rounding error in path bias counts when scaling
1838 them down, and use the correct scale factor default. Also demote
1839 some path bias related log messages down a level and make others
1840 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
1841 - We no longer warn so much when generating manpages from their
1844 o Code simplifications and refactoring:
1845 - Enhance our internal sscanf replacement so that we can eliminate
1846 the last remaining uses of the system sscanf. (Though those uses
1847 of sscanf were safe, sscanf itself is generally error prone, so
1848 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
1850 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
1851 - Move last_reachable and testing_since from routerinfo_t to node_t.
1852 Implements ticket 5529.
1853 - Add replaycache_t structure, functions and unit tests, then refactor
1854 rend_service_introduce() to be more clear to read, improve, debug,
1855 and test. Resolves bug 6177.
1856 - Finally remove support for malloc_good_size and malloc_usable_size.
1857 We had hoped that these functions would let us eke a little more
1858 memory out of our malloc implementation. Unfortunately, the only
1859 implementations that provided these functions are also ones that
1860 are already efficient about not overallocation: they never got us
1861 more than 7 or so bytes per allocation. Removing them saves us a
1862 little code complexity and a nontrivial amount of build complexity.
1865 - Tor maintainers now require Automake version 1.9 or later to build
1866 Tor from the Git repository. (Automake is not required when building
1867 from a source distribution.)
1870 Changes in version 0.2.3.21-rc - 2012-09-05
1871 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
1872 series. It fixes a trio of potential security bugs, fixes a bug where
1873 we were leaving some of the fast relays out of the microdescriptor
1874 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
1875 and cleans up other smaller issues.
1877 o Major bugfixes (security):
1878 - Tear down the circuit if we get an unexpected SENDME cell. Clients
1879 could use this trick to make their circuits receive cells faster
1880 than our flow control would have allowed, or to gum up the network,
1881 or possibly to do targeted memory denial-of-service attacks on
1882 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
1883 from July 2002, before the release of Tor 0.0.0. We had committed
1884 this patch previously, but we had to revert it because of bug 6271.
1885 Now that 6271 is fixed, this patch appears to work.
1886 - Reject any attempt to extend to an internal address. Without
1887 this fix, a router could be used to probe addresses on an internal
1888 network to see whether they were accepting connections. Fixes bug
1889 6710; bugfix on 0.0.8pre1.
1890 - Do not crash when comparing an address with port value 0 to an
1891 address policy. This bug could have been used to cause a remote
1892 assertion failure by or against directory authorities, or to
1893 allow some applications to crash clients. Fixes bug 6690; bugfix
1897 - Remove the upper bound on microdescriptor length. We were hitting
1898 the limit for routers with complex exit policies or family
1899 declarations, causing clients to not use them. Fixes the first
1900 piece of bug 6404; fix on 0.2.2.6-alpha.
1901 - Detect "ORPort 0" as meaning, uniformly, that we're not running
1902 as a relay. Previously, some of our code would treat the presence
1903 of any ORPort line as meaning that we should act like a relay,
1904 even though our new listener code would correctly not open any
1905 ORPorts for ORPort 0. Similar bugs in other Port options are also
1906 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
1909 - Avoid a pair of double-free and use-after-mark bugs that can
1910 occur with certain timings in canceled and re-received DNS
1911 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
1912 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
1913 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
1914 - Allow one-hop directory fetching circuits the full "circuit build
1915 timeout" period, rather than just half of it, before failing them
1916 and marking the relay down. This fix should help reduce cases where
1917 clients declare relays (or worse, bridges) unreachable because
1918 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
1919 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
1921 - Authorities no longer include any router in their microdescriptor
1922 consensuses for which they couldn't generate or agree on a
1923 microdescriptor. Fixes the second piece of bug 6404; fix on
1925 - Detect and reject attempts to specify both "FooPort" and
1926 "FooPort 0" in the same configuration domain. (It's still okay
1927 to have a FooPort in your configuration file, and use "FooPort 0"
1928 on the command line to disable it.) Fixes the second half of bug
1929 6507; bugfix on 0.2.3.3-alpha.
1930 - Make wildcarded addresses (that is, ones beginning with "*.") work
1931 when provided via the controller's MapAddress command. Previously,
1932 they were accepted, but we never actually noticed that they were
1933 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
1934 - Avoid crashing on a malformed state file where EntryGuardPathBias
1935 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
1936 - Add a (probably redundant) memory clear between iterations of
1937 the router status voting loop, to prevent future coding errors
1938 where data might leak between iterations of the loop. Resolves
1941 o Minor bugfixes (log messages):
1942 - Downgrade "set buildtimeout to low value" messages to "info"
1943 severity; they were never an actual problem, there was never
1944 anything reasonable to do about them, and they tended to spam logs
1945 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
1946 - Downgrade path-bias warning messages to "info". We'll try to get
1947 them working better in 0.2.4. Add internal circuit construction
1948 state to protect against the noisy warn message "Unexpectedly high
1949 circuit_successes". Also add some additional rate-limited notice
1950 messages to help determine the root cause of the warn. Fixes bug
1951 6475. Bugfix against 0.2.3.17-beta.
1952 - Move log message when unable to find a microdesc in a routerstatus
1953 entry to parse time. Previously we'd spam this warning every time
1954 we tried to figure out which microdescriptors to download. Fixes
1955 the third piece of bug 6404; fix on 0.2.3.18-rc.
1958 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
1959 change when the authority is deciding whether to accept a newly
1960 uploaded descriptor. Implements ticket 6423.
1961 - Add missing documentation for consensus and microdesc files.
1962 Resolves ticket 6732.
1965 Changes in version 0.2.2.38 - 2012-08-12
1966 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
1967 attack that could in theory leak path information.
1970 - Avoid an uninitialized memory read when reading a vote or consensus
1971 document that has an unrecognized flavor name. This read could
1972 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1973 - Try to leak less information about what relays a client is
1974 choosing to a side-channel attacker. Previously, a Tor client would
1975 stop iterating through the list of available relays as soon as it
1976 had chosen one, thus finishing a little earlier when it picked
1977 a router earlier in the list. If an attacker can recover this
1978 timing information (nontrivial but not proven to be impossible),
1979 they could learn some coarse-grained information about which relays
1980 a client was picking (middle nodes in particular are likelier to
1981 be affected than exits). The timing attack might be mitigated by
1982 other factors (see bug 6537 for some discussion), but it's best
1983 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
1986 Changes in version 0.2.3.20-rc - 2012-08-05
1987 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
1988 series. It fixes a pair of code security bugs and a potential anonymity
1989 issue, updates our RPM spec files, and cleans up other smaller issues.
1992 - Avoid read-from-freed-memory and double-free bugs that could occur
1993 when a DNS request fails while launching it. Fixes bug 6480;
1994 bugfix on 0.2.0.1-alpha.
1995 - Avoid an uninitialized memory read when reading a vote or consensus
1996 document that has an unrecognized flavor name. This read could
1997 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
1998 - Try to leak less information about what relays a client is
1999 choosing to a side-channel attacker. Previously, a Tor client would
2000 stop iterating through the list of available relays as soon as it
2001 had chosen one, thus finishing a little earlier when it picked
2002 a router earlier in the list. If an attacker can recover this
2003 timing information (nontrivial but not proven to be impossible),
2004 they could learn some coarse-grained information about which relays
2005 a client was picking (middle nodes in particular are likelier to
2006 be affected than exits). The timing attack might be mitigated by
2007 other factors (see bug 6537 for some discussion), but it's best
2008 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
2011 - Try to make the warning when giving an obsolete SOCKSListenAddress
2012 a little more useful.
2013 - Terminate active server managed proxies if Tor stops being a
2014 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
2015 - Provide a better error message about possible OSX Asciidoc failure
2016 reasons. Fixes bug 6436.
2017 - Warn when Tor is configured to use accounting in a way that can
2018 link a hidden service to some other hidden service or public
2019 address. Resolves ticket 6490.
2022 - Check return value of fputs() when writing authority certificate
2023 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
2024 - Ignore ServerTransportPlugin lines when Tor is not configured as
2025 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
2026 - When disabling guards for having too high a proportion of failed
2027 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
2031 - Update our default RPM spec files to work with mock and rpmbuild
2032 on RHEL/Fedora. They have an updated set of dependencies and
2033 conflicts, a fix for an ancient typo when creating the "_tor"
2034 user, and better instructions. Thanks to Ondrej Mikle for the
2035 patch series. Fixes bug 6043.
2038 - Make it possible to set the TestingTorNetwork configuration
2039 option using AlternateDirAuthority and AlternateBridgeAuthority
2040 as an alternative to setting DirServer. Addresses ticket 6377.
2043 - Clarify the documentation for the Alternate*Authority options.
2045 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
2047 o Code simplification and refactoring:
2048 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
2049 10 lines. Also, don't nest them. Doing so in the past has
2050 led to hard-to-debug code. The new style is to use the
2051 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
2054 Changes in version 0.2.3.19-rc - 2012-07-06
2055 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
2056 series. It fixes the compile on Windows, reverts to a GeoIP database
2057 that isn't as broken, and fixes a flow control bug that has been around
2058 since the beginning of Tor.
2061 - Fix a bug handling SENDME cells on nonexistent streams that could
2062 result in bizarre window values. Report and patch contributed
2063 pseudonymously. Fixes part of bug 6271. This bug was introduced
2064 before the first Tor release, in svn commit r152.
2065 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
2066 June 2012 database, Maxmind marked many Tor relays as country "A1",
2067 which will cause risky behavior for clients that set EntryNodes
2068 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
2069 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
2070 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
2073 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
2074 bugfix on 0.2.1.10-alpha.
2077 Changes in version 0.2.3.18-rc - 2012-06-28
2078 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
2079 series. It fixes a few smaller bugs, but generally appears stable.
2080 Please test it and let us know whether it is!
2083 - Allow wildcarded mapaddress targets to be specified on the
2084 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
2085 - Make our linker option detection code more robust against linkers
2086 such as on FreeBSD 8, where a bad combination of options completes
2087 successfully but makes an unrunnable binary. Fixes bug 6173;
2088 bugfix on 0.2.3.17-beta.
2090 o Minor bugfixes (on 0.2.2.x and earlier):
2091 - Avoid a false positive in the util/threads unit test by increasing
2092 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
2093 - Replace "Sending publish request" log messages with "Launching
2094 upload", so that they no longer confusingly imply that we're
2095 sending something to a directory we might not even be connected
2096 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
2097 - Make sure to set *socket_error in all error cases in
2098 connection_connect(), so it can't produce a warning about
2099 errno being zero from errno_to_orconn_end_reason(). Bugfix on
2100 0.2.1.1-alpha; resolves ticket 6028.
2101 - Downgrade "Got a certificate, but we already have it" log messages
2102 from warning to info, except when we're a dirauth. Fixes bug 5238;
2103 bugfix on 0.2.1.7-alpha.
2104 - When checking for requested signatures on the latest consensus
2105 before serving it to a client, make sure to check the right
2106 consensus flavor. Bugfix on 0.2.2.6-alpha.
2107 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
2108 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
2110 o Minor bugfixes (on 0.2.3.x):
2111 - Make format_helper_exit_status() avoid unnecessary space padding
2112 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
2114 - Downgrade a message about cleaning the microdescriptor cache to
2115 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
2116 - Log a BUG message at severity INFO if we have a networkstatus with
2117 a missing entry for some microdescriptor. Continues on a patch
2119 - Improve the log message when a managed proxy fails to launch. Fixes
2120 bug 5099; bugfix on 0.2.3.6-alpha.
2121 - Don't do DNS lookups when parsing corrupted managed proxy protocol
2122 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
2123 - When formatting wildcarded address mappings for the controller,
2124 be sure to include "*." as appropriate. Partially fixes bug 6244;
2125 bugfix on 0.2.3.9-alpha.
2126 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
2127 Bugfix on 0.2.3.13-alpha.
2128 - Stop logging messages about running with circuit timeout learning
2129 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
2130 - Disable a spurious warning about reading on a marked and flushing
2131 connection. We shouldn't be doing that, but apparently we
2132 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
2133 - Fix a bug that stopped AllowDotExit from working on addresses
2134 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
2137 o Code simplification, refactoring, unit tests:
2138 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
2139 Libevent's notion of cached time when possible.
2140 - Remove duplicate code for invoking getrlimit() from control.c.
2141 - Add a unit test for the environment_variable_names_equal function.
2144 - Document the --defaults-torrc option, and the new (in 0.2.3)
2145 semantics for overriding, extending, and clearing lists of
2146 options. Closes bug 4748.
2149 Changes in version 0.2.3.17-beta - 2012-06-15
2150 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
2151 gets our TLS handshake back on track for being able to blend in with
2152 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
2153 with Vidalia, and otherwise continues to get us closer to a release
2157 - Enable gcc and ld hardening by default. Resolves ticket 5210.
2158 - Update TLS cipher list to match Firefox 8 and later. Resolves
2160 - Implement the client side of proposal 198: remove support for
2161 clients falsely claiming to support standard ciphersuites that
2162 they can actually provide. As of modern OpenSSL versions, it's not
2163 necessary to fake any standard ciphersuite, and doing so prevents
2164 us from using better ciphersuites in the future, since servers
2165 can't know whether an advertised ciphersuite is really supported or
2166 not. Some hosts -- notably, ones with very old versions of OpenSSL
2167 or where OpenSSL has been built with ECC disabled -- will stand
2168 out because of this change; TBB users should not be affected.
2171 - Change the default value for DynamicDHGroups (introduced in
2172 0.2.3.9-alpha) to 0. This feature can make Tor relays less
2173 identifiable by their use of the mod_ssl DH group, but at
2174 the cost of some usability (#4721) and bridge tracing (#6087)
2175 regressions. Resolves ticket 5598.
2176 - Send a CRLF at the end of each STATUS_* control protocol event. This
2177 bug tickled a bug in Vidalia which would make it freeze. Fixes
2178 bug 6094; bugfix on 0.2.3.16-alpha.
2181 - Disable writing on marked-for-close connections when they are
2182 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
2183 bug 5263; bugfix on 0.0.2pre13, where we first added a special
2184 case for flushing marked connections.
2185 - Detect SSL handshake even when the initial attempt to write the
2186 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
2187 - Change the AllowDotExit rules so they should actually work.
2188 We now enforce AllowDotExit only immediately after receiving an
2189 address via SOCKS or DNSPort: other sources are free to provide
2190 .exit addresses after the resolution occurs. Fixes bug 3940;
2191 bugfix on 0.2.2.1-alpha.
2192 - Fix a (harmless) integer overflow in cell statistics reported by
2193 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
2194 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
2195 right places and never depends on the consensus parameters or
2196 computes adaptive timeouts when it is disabled. Fixes bug 5049;
2197 bugfix on 0.2.2.14-alpha.
2198 - When building Tor on Windows with -DUNICODE (not default), ensure
2199 that error messages, filenames, and DNS server names are always
2200 NUL-terminated when we convert them to a single-byte encoding.
2201 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
2202 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
2203 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
2204 - Fix an edge case where TestingTorNetwork is set but the authorities
2205 and relays all have an uptime of zero, where the private Tor network
2206 could briefly lack support for hidden services. Fixes bug 3886;
2207 bugfix on 0.2.2.18-alpha.
2208 - Correct the manpage's descriptions for the default values of
2209 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
2211 - Fix the documentation for the --hush and --quiet command line
2212 options, which changed their behavior back in 0.2.3.3-alpha.
2213 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
2217 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
2218 more information to it, so that we can track it down in case it
2219 returns again. Mitigates bug 5235.
2220 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
2221 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
2222 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
2223 - Warn the user when HTTPProxy, but no other proxy type, is
2224 configured. This can cause surprising behavior: it doesn't send
2225 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
2226 directory traffic only. Resolves ticket 4663.
2227 - Issue a notice if a guard completes less than 40% of your circuits.
2228 Threshold is configurable by torrc option PathBiasNoticeRate and
2229 consensus parameter pb_noticepct. There is additional, off-by-
2230 default code to disable guards which fail too many circuits.
2231 Addresses ticket 5458.
2232 - Update to the June 6 2012 Maxmind GeoLite Country database.
2234 o Code simplifications and refactoring:
2235 - Remove validate_pluggable_transports_config(): its warning
2236 message is now handled by connection_or_connect().
2239 Changes in version 0.2.2.37 - 2012-06-06
2240 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
2241 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2245 - Work around a bug in OpenSSL that broke renegotiation with TLS
2246 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2247 the v2 Tor connection protocol when both sides were using OpenSSL
2248 1.0.1 would fail. Resolves ticket 6033.
2249 - When waiting for a client to renegotiate, don't allow it to add
2250 any bytes to the input buffer. This fixes a potential DoS issue.
2251 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2252 - Fix an edge case where if we fetch or publish a hidden service
2253 descriptor, we might build a 4-hop circuit and then use that circuit
2254 for exiting afterwards -- even if the new last hop doesn't obey our
2255 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2258 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2259 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2262 - Tell GCC and Clang to check for any errors in format strings passed
2263 to the tor_v*(print|scan)f functions.
2266 Changes in version 0.2.3.16-alpha - 2012-06-05
2267 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
2268 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
2269 currently). It also fixes a variety of smaller bugs and other cleanups
2270 that get us closer to a release candidate.
2272 o Major bugfixes (general):
2273 - Work around a bug in OpenSSL that broke renegotiation with TLS
2274 1.1 and TLS 1.2. Without this workaround, all attempts to speak
2275 the v2 Tor connection protocol when both sides were using OpenSSL
2276 1.0.1 would fail. Resolves ticket 6033.
2277 - When waiting for a client to renegotiate, don't allow it to add
2278 any bytes to the input buffer. This fixes a potential DoS issue.
2279 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
2280 - Pass correct OR address to managed proxies (like obfsproxy),
2281 even when ORListenAddress is used. Fixes bug 4865; bugfix on
2283 - The advertised platform of a router now includes only its operating
2284 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
2285 service pack level (for Windows) or its CPU architecture (for Unix).
2286 We also no longer include the "git-XYZ" tag in the version. Resolves
2289 o Major bugfixes (clients):
2290 - If we are unable to find any exit that supports our predicted ports,
2291 stop calling them predicted, so that we don't loop and build
2292 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
2293 which introduced predicted ports.
2294 - Fix an edge case where if we fetch or publish a hidden service
2295 descriptor, we might build a 4-hop circuit and then use that circuit
2296 for exiting afterwards -- even if the new last hop doesn't obey our
2297 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
2298 - Check at each new consensus whether our entry guards were picked
2299 long enough ago that we should rotate them. Previously, we only
2300 did this check at startup, which could lead to us holding a guard
2301 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
2302 - When fetching a bridge descriptor from a bridge authority,
2303 always do so anonymously, whether we have been able to open
2304 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
2305 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
2306 but we'll need to wait for bug 6010 before it's actually usable.
2308 o Major bugfixes (directory authorities):
2309 - When computing weight parameters, behave more robustly in the
2310 presence of a bad bwweightscale value. Previously, the authorities
2311 would crash if they agreed on a sufficiently broken weight_scale
2312 value: now, they use a reasonable default and carry on. Partial
2313 fix for 5786; bugfix on 0.2.2.17-alpha.
2314 - Check more thoroughly to prevent a rogue authority from
2315 double-voting on any consensus directory parameter. Previously,
2316 authorities would crash in this case if the total number of
2317 votes for any parameter exceeded the number of active voters,
2318 but would let it pass otherwise. Partial fix for bug 5786; bugfix
2322 - Rate-limit log messages when asked to connect anonymously to
2323 a private address. When these hit, they tended to hit fast and
2324 often. Also, don't bother trying to connect to addresses that we
2325 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
2326 reply makes us think we have been lied to, even when the address the
2327 client tried to connect to was "localhost." Resolves ticket 2822.
2328 - Allow packagers to insert an extra string in server descriptor
2329 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
2330 Resolves the rest of ticket 2988.
2331 - Raise the threshold of server descriptors needed (75%) and exit
2332 server descriptors needed (50%) before we will declare ourselves
2333 bootstrapped. This will make clients start building circuits a
2334 little later, but makes the initially constructed circuits less
2335 skewed and less in conflict with further directory fetches. Fixes
2337 - Close any connection that sends unrecognized junk before the
2338 handshake. Solves an issue noted in bug 4369.
2339 - Improve log messages about managed transports. Resolves ticket 5070.
2340 - Tag a bridge's descriptor as "never to be sent unencrypted".
2341 This shouldn't matter, since bridges don't open non-anonymous
2342 connections to the bridge authority and don't allow unencrypted
2343 directory connections from clients, but we might as well make
2344 sure. Closes bug 5139.
2345 - Expose our view of whether we have gone dormant to the controller,
2346 via a new "GETINFO dormant" value. Torbutton and other controllers
2347 can use this to avoid doing periodic requests through Tor while
2348 it's dormant (bug 4718). Fixes bug 5954.
2349 - Tell GCC and Clang to check for any errors in format strings passed
2350 to the tor_v*(print|scan)f functions.
2351 - Update to the May 1 2012 Maxmind GeoLite Country database.
2353 o Minor bugfixes (already included in 0.2.2.36):
2354 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2355 Fixes bug 5346; bugfix on 0.0.8pre3.
2356 - Correct parsing of certain date types in parse_http_time().
2357 Without this patch, If-Modified-Since would behave
2358 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2359 Esteban Manchado Velázques.
2360 - Make our number-parsing functions always treat too-large values
2361 as an error, even when those values exceed the width of the
2362 underlying type. Previously, if the caller provided these
2363 functions with minima or maxima set to the extreme values of the
2364 underlying integer type, these functions would return those
2365 values on overflow rather than treating overflow as an error.
2366 Fixes part of bug 5786; bugfix on 0.0.9.
2367 - If we hit the error case where routerlist_insert() replaces an
2368 existing (old) server descriptor, make sure to remove that
2369 server descriptor from the old_routers list. Fix related to bug
2370 1776. Bugfix on 0.2.2.18-alpha.
2371 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2372 circuits. Fixes issue 5259.
2374 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
2375 - Prevent a null-pointer dereference when receiving a data cell
2376 for a nonexistent stream when the circuit in question has an
2377 empty deliver window. We don't believe this is triggerable,
2378 since we don't currently allow deliver windows to become empty,
2379 but the logic is tricky enough that it's better to make the code
2380 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
2381 - Fix a memory leak when trying to launch a DNS request when the
2382 network is disabled or the nameservers are unconfigurable. Fixes
2383 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
2384 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
2385 - Don't hold a Windows file handle open for every file mapping;
2386 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
2388 - Avoid O(n^2) performance characteristics when parsing a large
2389 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
2390 - Format more doubles with %f, not %lf. Patch from grarpamp to make
2391 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
2393 - Make our replacement implementation of strtok_r() compatible with
2394 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
2395 bugfix on 0.2.2.1-alpha.
2396 - Fix a NULL-pointer dereference on a badly formed
2397 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
2398 bugfix on 0.2.2.9-alpha.
2399 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
2400 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
2401 - Defensively refactor rend_mid_rendezvous() so that protocol
2402 violations and length checks happen in the beginning. Fixes
2404 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
2405 that IPv6 stuff will compile on MSVC, and compilation issues
2406 will be easier to track down. Fixes bug 5861.
2408 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
2409 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
2410 resource exhaustion, so that clients can adjust their load to
2411 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
2412 started using END_STREAM_REASON_RESOURCELIMIT.
2413 - Don't check for whether the address we're using for outbound
2414 connections has changed until after the outbound connection has
2415 completed. On Windows, getsockname() doesn't succeed until the
2416 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
2417 - If the configuration tries to set MyFamily on a bridge, refuse to
2418 do so, and warn about the security implications. Fixes bug 4657;
2419 bugfix on 0.2.0.3-alpha.
2420 - If the client fails to set a reasonable set of ciphersuites
2421 during its v2 handshake renegotiation, allow the renegotiation to
2422 continue nevertheless (i.e. send all the required certificates).
2423 Fixes bug 4591; bugfix on 0.2.0.20-rc.
2424 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
2425 option is set to 0 (which Vidalia version 0.2.16 now does when
2426 a SAVECONF attempt fails), perform other actions that SIGHUP
2427 usually causes (like reopening the logs). Fixes bug 5095; bugfix
2429 - If we fail to write a microdescriptor to the disk cache, do not
2430 continue replacing the old microdescriptor file. Fixes bug 2954;
2431 bugfix on 0.2.2.6-alpha.
2432 - Exit nodes don't need to fetch certificates for authorities that
2433 they don't recognize; only directory authorities, bridges,
2434 and caches need to do that. Fixes part of bug 2297; bugfix on
2436 - Correctly handle checking the permissions on the parent
2437 directory of a control socket in the root directory. Bug found
2438 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
2440 - When told to add a bridge with the same digest as a preexisting
2441 bridge but a different addr:port, change the addr:port as
2442 requested. Previously we would not notice the change. Fixes half
2443 of bug 5603; fix on 0.2.2.26-beta.
2444 - End AUTHCHALLENGE error messages (in the control protocol) with
2445 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
2447 o Minor bugfixes (on 0.2.3.x):
2448 - Turn an assertion (that the number of handshakes received as a
2449 server is not < 1) into a warning. Fixes bug 4873; bugfix on
2451 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
2452 we had reversed them when the answer was cached.) Fixes bug
2453 5723; bugfix on 0.2.3.1-alpha.
2454 - Work correctly on Linux systems with accept4 support advertised in
2455 their headers, but without accept4 support in the kernel. Fix
2456 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
2457 - When told to add a bridge with the same addr:port as a preexisting
2458 bridge but a different transport, change the transport as
2459 requested. Previously we would not notice the change. Fixes half
2460 of bug 5603; fix on 0.2.3.2-alpha.
2461 - Avoid a "double-reply" warning when replying to a SOCKS request
2462 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
2463 bugfix on 0.2.3.4-alpha.
2464 - Fix a bug where a bridge authority crashes if it has seen no
2465 directory requests when it's time to write statistics to disk.
2466 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
2468 - Don't try to open non-control listeners when DisableNetwork is set.
2469 Previously, we'd open all listeners, then immediately close them.
2470 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
2471 - Don't abort the managed proxy protocol if the managed proxy
2472 sends us an unrecognized line; ignore it instead. Fixes bug
2473 5910; bugfix on 0.2.3.9-alpha.
2474 - Fix a compile warning in crypto.c when compiling with clang 3.1.
2475 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
2476 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
2477 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
2478 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
2479 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
2480 - Resolve numerous small warnings and build issues with MSVC. Resolves
2483 o Documentation fixes:
2484 - Improve the manual's documentation for the NT Service command-line
2485 options. Addresses ticket 3964.
2486 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
2487 - Document the changes to the ORPort and DirPort options, and the
2488 fact that {OR/Dir}ListenAddress is now unnecessary (and
2489 therefore deprecated). Resolves ticket 5597.
2492 - Remove the torrc.bridge file: we don't use it for anything, and
2493 it had become badly desynchronized from torrc.sample. Resolves
2497 Changes in version 0.2.2.36 - 2012-05-24
2498 Tor 0.2.2.36 updates the addresses for two of the eight directory
2499 authorities, fixes some potential anonymity and security issues,
2500 and fixes several crash bugs.
2502 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
2503 known flaws, and nobody should be using them. You should upgrade. If
2504 you're using a Linux or BSD and its packages are obsolete, stop using
2505 those packages and upgrade anyway.
2507 o Directory authority changes:
2508 - Change IP address for maatuska (v3 directory authority).
2509 - Change IP address for ides (v3 directory authority), and rename
2513 - When building or running with any version of OpenSSL earlier
2514 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2515 versions have a bug (CVE-2011-4576) in which their block cipher
2516 padding includes uninitialized data, potentially leaking sensitive
2517 information to any peer with whom they make a SSLv3 connection. Tor
2518 does not use SSL v3 by default, but a hostile client or server
2519 could force an SSLv3 connection in order to gain information that
2520 they shouldn't have been able to get. The best solution here is to
2521 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2522 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2523 to make sure that the bug can't happen.
2524 - Never use a bridge or a controller-supplied node as an exit, even
2525 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2526 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2527 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2528 - Only build circuits if we have a sufficient threshold of the total
2529 descriptors that are marked in the consensus with the "Exit"
2530 flag. This mitigates an attack proposed by wanoskarnet, in which
2531 all of a client's bridges collude to restrict the exit nodes that
2532 the client knows about. Fixes bug 5343.
2533 - Provide controllers with a safer way to implement the cookie
2534 authentication mechanism. With the old method, if another locally
2535 running program could convince a controller that it was the Tor
2536 process, then that program could trick the controller into telling
2537 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2538 authentication method uses a challenge-response approach to prevent
2539 this attack. Fixes bug 5185; implements proposal 193.
2542 - Avoid logging uninitialized data when unable to decode a hidden
2543 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2544 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2545 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2547 - Fix builds when the path to sed, openssl, or sha1sum contains
2548 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2550 - Correct our replacements for the timeradd() and timersub() functions
2551 on platforms that lack them (for example, Windows). The timersub()
2552 function is used when expiring circuits, while timeradd() is
2553 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2554 bugfix on 0.2.2.24-alpha.
2555 - Fix the SOCKET_OK test that we use to tell when socket
2556 creation fails so that it works on Win64. Fixes part of bug 4533;
2557 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2560 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
2561 Fixes bug 5346; bugfix on 0.0.8pre3.
2562 - Make our number-parsing functions always treat too-large values
2563 as an error, even when those values exceed the width of the
2564 underlying type. Previously, if the caller provided these
2565 functions with minima or maxima set to the extreme values of the
2566 underlying integer type, these functions would return those
2567 values on overflow rather than treating overflow as an error.
2568 Fixes part of bug 5786; bugfix on 0.0.9.
2569 - Older Linux kernels erroneously respond to strange nmap behavior
2570 by having accept() return successfully with a zero-length
2571 socket. When this happens, just close the connection. Previously,
2572 we would try harder to learn the remote address: but there was
2573 no such remote address to learn, and our method for trying to
2574 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
2575 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
2576 - Correct parsing of certain date types in parse_http_time().
2577 Without this patch, If-Modified-Since would behave
2578 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
2579 Esteban Manchado Velázques.
2580 - Change the BridgePassword feature (part of the "bridge community"
2581 design, which is not yet implemented) to use a time-independent
2582 comparison. The old behavior might have allowed an adversary
2583 to use timing to guess the BridgePassword value. Fixes bug 5543;
2584 bugfix on 0.2.0.14-alpha.
2585 - Detect and reject certain misformed escape sequences in
2586 configuration values. Previously, these values would cause us
2587 to crash if received in a torrc file or over an authenticated
2588 control port. Bug found by Esteban Manchado Velázquez, and
2589 independently by Robert Connolly from Matta Consulting who further
2590 noted that it allows a post-authentication heap overflow. Patch
2591 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2592 bugfix on 0.2.0.16-alpha.
2593 - Fix a compile warning when using the --enable-openbsd-malloc
2594 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2595 - During configure, detect when we're building with clang version
2596 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
2597 CFLAGS. clang doesn't support them yet.
2598 - When sending an HTTP/1.1 proxy request, include a Host header.
2599 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2600 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
2601 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
2602 - If we hit the error case where routerlist_insert() replaces an
2603 existing (old) server descriptor, make sure to remove that
2604 server descriptor from the old_routers list. Fix related to bug
2605 1776. Bugfix on 0.2.2.18-alpha.
2607 o Minor bugfixes (documentation and log messages):
2608 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
2609 Fixes bug 4856; bugfix on Tor 0.0.6.
2610 - Update "ClientOnly" man page entry to explain that there isn't
2611 really any point to messing with it. Resolves ticket 5005.
2612 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
2613 directory authority option (introduced in Tor 0.2.2.34).
2614 - Downgrade the "We're missing a certificate" message from notice
2615 to info: people kept mistaking it for a real problem, whereas it
2616 is seldom the problem even when we are failing to bootstrap. Fixes
2617 bug 5067; bugfix on 0.2.0.10-alpha.
2618 - Correctly spell "connect" in a log message on failure to create a
2619 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
2620 - Clarify the behavior of MaxCircuitDirtiness with hidden service
2621 circuits. Fixes issue 5259.
2624 - Directory authorities now reject versions of Tor older than
2625 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
2626 inclusive. These versions accounted for only a small fraction of
2627 the Tor network, and have numerous known security issues. Resolves
2629 - Update to the May 1 2012 Maxmind GeoLite Country database.
2632 - When sending or relaying a RELAY_EARLY cell, we used to convert
2633 it to a RELAY cell if the connection was using the v1 link
2634 protocol. This was a workaround for older versions of Tor, which
2635 didn't handle RELAY_EARLY cells properly. Now that all supported
2636 versions can handle RELAY_EARLY cells, and now that we're enforcing
2637 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
2638 remove this workaround. Addresses bug 4786.
2641 Changes in version 0.2.3.15-alpha - 2012-04-30
2642 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
2643 the development branch build on Windows again.
2645 o Minor bugfixes (on 0.2.2.x and earlier):
2646 - Make sure that there are no unhandled pending TLS errors before
2647 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
2648 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
2649 Bugfix on 0.1.0.5-rc; fixes bug 4528.
2650 - Fix an assert that directory authorities could trigger on sighup
2651 during some configuration state transitions. We now don't treat
2652 it as a fatal error when the new descriptor we just generated in
2653 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
2654 - After we pick a directory mirror, we would refuse to use it if
2655 it's in our ExcludeExitNodes list, resulting in mysterious failures
2656 to bootstrap for people who just wanted to avoid exiting from
2657 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
2658 - When building with --enable-static-tor on OpenBSD, do not
2659 erroneously attempt to link -lrt. Fixes bug 5103.
2661 o Minor bugfixes (on 0.2.3.x):
2662 - When Tor is built with kernel headers from a recent (last few
2663 years) Linux kernel, do not fail to run on older (pre-2.6.28
2664 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
2665 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
2667 - Fix compilation with miniupnpc version 1.6; patch from
2668 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
2669 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
2670 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
2671 - Fix compilation on platforms without unistd.h, or where environ
2672 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
2675 - Directory authorities are now a little more lenient at accepting
2676 older router descriptors, or newer router descriptors that don't
2677 make big changes. This should help ameliorate past and future
2678 issues where routers think they have uploaded valid descriptors,
2679 but the authorities don't think so. Fix for ticket 2479.
2680 - Make the code that clients use to detect an address change be
2681 IPv6-aware, so that it won't fill clients' logs with error
2682 messages when trying to get the IPv4 address of an IPv6
2683 connection. Implements ticket 5537.
2686 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
2687 authorities needed to use it for a while to keep the network working
2688 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
2689 that was six months ago. As of now, it should no longer be needed
2693 Changes in version 0.2.3.14-alpha - 2012-04-23
2694 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
2695 candidate. It also dramatically speeds up AES: fast relays should
2696 consider switching to the newer OpenSSL library.
2698 o Directory authority changes:
2699 - Change IP address for ides (v3 directory authority), and rename
2703 - Avoid logging uninitialized data when unable to decode a hidden
2704 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
2705 - Avoid a client-side assertion failure when receiving an INTRODUCE2
2706 cell on a general purpose circuit. Fixes bug 5644; bugfix on
2708 - If authorities are unable to get a v2 consensus document from other
2709 directory authorities, they no longer fall back to fetching
2710 them from regular directory caches. Fixes bug 5635; bugfix on
2711 0.2.2.26-beta, where routers stopped downloading v2 consensus
2713 - When we start a Tor client with a normal consensus already cached,
2714 be willing to download a microdescriptor consensus. Fixes bug 4011;
2715 fix on 0.2.3.1-alpha.
2717 o Major features (performance):
2718 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
2719 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
2720 vectorized AES implementations as appropriate. These can be much,
2721 much faster than other AES implementations.
2723 o Minor bugfixes (0.2.2.x and earlier):
2724 - Don't launch more than 10 service-side introduction-point circuits
2725 for a hidden service in five minutes. Previously, we would consider
2726 launching more introduction-point circuits if at least one second
2727 had passed without any introduction-point circuits failing. Fixes
2728 bug 4607; bugfix on 0.0.7pre1.
2729 - Change the BridgePassword feature (part of the "bridge community"
2730 design, which is not yet implemented) to use a time-independent
2731 comparison. The old behavior might have allowed an adversary
2732 to use timing to guess the BridgePassword value. Fixes bug 5543;
2733 bugfix on 0.2.0.14-alpha.
2734 - Enforce correct return behavior of tor_vsscanf() when the '%%'
2735 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
2736 - When sending an HTTP/1.1 proxy request, include a Host header.
2737 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
2738 - Don't log that we have "decided to publish new relay descriptor"
2739 unless we are actually publishing a descriptor. Fixes bug 3942;
2740 bugfix on 0.2.2.28-beta.
2742 o Minor bugfixes (0.2.3.x):
2743 - Fix a bug where a bridge authority crashes (on a failed assert)
2744 if it has seen no directory requests when it's time to write
2745 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
2746 - Fix bug stomping on ORPort option NoListen and ignoring option
2747 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
2748 - In the testsuite, provide a large enough buffer in the tor_sscanf
2749 unit test. Otherwise we'd overrun that buffer and crash during
2750 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
2752 - Make sure we create the keys directory if it doesn't exist and we're
2753 about to store the dynamic Diffie-Hellman parameters. Fixes bug
2754 5572; bugfix on 0.2.3.13-alpha.
2755 - Fix a small memory leak when trying to decode incorrect base16
2756 authenticator during SAFECOOKIE authentication. Found by
2757 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
2760 - Add more information to a log statement that might help track down
2761 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
2762 non-IP address" messages (or any Bug messages, for that matter!),
2763 please let us know about it.
2764 - Relays now understand an IPv6 address when they get one from a
2765 directory server. Resolves ticket 4875.
2766 - Resolve IPv6 addresses in bridge and entry statistics to country
2767 code "??" which means we at least count them. Resolves ticket 5053;
2768 improves on 0.2.3.9-alpha.
2769 - Update to the April 3 2012 Maxmind GeoLite Country database.
2770 - Begin a doc/state-contents.txt file to explain the contents of
2771 the Tor state file. Fixes bug 2987.
2773 o Default torrc changes:
2774 - Stop listing "socksport 9050" in torrc.sample. We open a socks
2775 port on 9050 by default anyway, so this should not change anything
2777 - Stop mentioning the deprecated *ListenAddress options in
2778 torrc.sample. Fixes bug 5438.
2779 - Document unit of bandwidth related options in sample torrc.
2783 - The "torify" script no longer supports the "tsocks" socksifier
2784 tool, since tsocks doesn't support DNS and UDP right for Tor.
2785 Everyone should be using torsocks instead. Fixes bugs 3530 and
2786 5180. Based on a patch by "ugh".
2789 - Change the symmetric cipher interface so that creating and
2790 initializing a stream cipher are no longer separate functions.
2791 - Remove all internal support for unpadded RSA. We never used it, and
2792 it would be a bad idea to start.
2795 Changes in version 0.2.3.13-alpha - 2012-03-26
2796 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
2797 in managed pluggable transports, as well as providing other cleanups
2798 that get us closer to a release candidate.
2800 o Directory authority changes:
2801 - Change IP address for maatuska (v3 directory authority).
2804 - Provide controllers with a safer way to implement the cookie
2805 authentication mechanism. With the old method, if another locally
2806 running program could convince a controller that it was the Tor
2807 process, then that program could trick the controller into telling
2808 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
2809 authentication method uses a challenge-response approach to prevent
2810 this attack. Fixes bug 5185, implements proposal 193.
2811 - Never use a bridge or a controller-supplied node as an exit, even
2812 if its exit policy allows it. Found by wanoskarnet. Fixes bug
2813 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
2814 and 0.2.0.3-alpha (for bridge-purpose descriptors).
2815 - Only build circuits if we have a sufficient threshold of the total
2816 descriptors that are marked in the consensus with the "Exit"
2817 flag. This mitigates an attack proposed by wanoskarnet, in which
2818 all of a client's bridges collude to restrict the exit nodes that
2819 the client knows about. Fixes bug 5343.
2821 o Major bugfixes (on Tor 0.2.3.x):
2822 - Avoid an assert when managed proxies like obfsproxy are configured,
2823 and we receive HUP signals or setconf attempts too rapidly. This
2824 situation happens most commonly when Vidalia tries to attach to
2825 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
2826 bugfix on 0.2.3.6-alpha.
2827 - Fix a relay-side pluggable transports bug where managed proxies were
2828 unreachable from the Internet, because Tor asked them to bind on
2829 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
2830 - Stop discarding command-line arguments when TestingTorNetwork
2831 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
2832 0.2.3.9-alpha, where task 4552 added support for two layers of
2834 - Resume allowing the unit tests to run in gdb. This was accidentally
2835 made impossible when the DisableDebuggerAttachment option was
2836 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
2837 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
2838 0.2.3.11-alpha. Reported by Anthony G. Basile.
2840 o Minor bugfixes (on 0.2.2.x and earlier):
2841 - Ensure we don't cannibalize circuits that are longer than three hops
2842 already, so we don't end up making circuits with 5 or more
2843 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
2844 0.1.0.1-rc which introduced cannibalization.
2845 - Detect and reject certain misformed escape sequences in
2846 configuration values. Previously, these values would cause us
2847 to crash if received in a torrc file or over an authenticated
2848 control port. Bug found by Esteban Manchado Velázquez, and
2849 independently by Robert Connolly from Matta Consulting who further
2850 noted that it allows a post-authentication heap overflow. Patch
2851 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
2852 bugfix on 0.2.0.16-alpha.
2853 - Fix a compile warning when using the --enable-openbsd-malloc
2854 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
2855 - Directory caches no longer refuse to clean out descriptors because
2856 of missing v2 networkstatus documents, unless they're configured
2857 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
2858 0.2.2.26-beta. Patch by Daniel Bryg.
2859 - Update to the latest version of the tinytest unit testing framework.
2860 This includes a couple of bugfixes that can be relevant for
2861 running forked unit tests on Windows, and removes all reserved
2864 o Minor bugfixes (on 0.2.3.x):
2865 - On a failed pipe() call, don't leak file descriptors. Fixes bug
2866 4296; bugfix on 0.2.3.1-alpha.
2867 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
2868 until after we have received a CERTS cell. Fixes bug 4361; bugfix
2869 on 0.2.3.6-alpha. Patch by "frosty".
2870 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
2871 option, so that the IP stack doesn't decide to use it for IPv4
2872 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
2873 - Ensure that variables set in Tor's environment cannot override
2874 environment variables that Tor passes to a managed
2875 pluggable-transport proxy. Previously, Tor would pass every
2876 variable in its environment to managed proxies along with the new
2877 ones, in such a way that on many operating systems, the inherited
2878 environment variables would override those which Tor tried to
2879 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
2880 bugfix on 0.2.3.9-alpha for Windows.
2883 - A wide variety of new unit tests by Esteban Manchado Velázquez.
2884 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
2885 - Update to the March 6 2012 Maxmind GeoLite Country database.
2888 Changes in version 0.2.3.12-alpha - 2012-02-13
2889 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
2890 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
2891 when Tor is configured to use a pluggable transport like obfsproxy.
2894 - Fix builds when the path to sed, openssl, or sha1sum contains
2895 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
2897 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
2898 connections. This change should allow busy exit relays to stop
2899 running out of available sockets as quickly. Fixes bug 4950;
2900 bugfix on 0.2.2.26-beta.
2901 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
2902 would ask the bridge for microdescriptors, which are only supported
2903 in 0.2.3.x, and then fail to bootstrap when it didn't get the
2904 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
2905 - Properly set up obfsproxy's environment when in managed mode. The
2906 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
2907 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
2908 5076 and 5082; bugfix on 0.2.3.6-alpha.
2911 - Use the dead_strip option when building Tor on OS X. This reduces
2912 binary size by almost 19% when linking openssl and libevent
2913 statically, which we do for Tor Browser Bundle.
2914 - Fix broken URLs in the sample torrc file, and tell readers about
2915 the OutboundBindAddress, ExitPolicyRejectPrivate, and
2916 PublishServerDescriptor options. Addresses bug 4652.
2917 - Update to the February 7 2012 Maxmind GeoLite Country database.
2920 - Downgrade the "We're missing a certificate" message from notice
2921 to info: people kept mistaking it for a real problem, whereas it
2922 is seldom the problem even when we are failing to bootstrap. Fixes
2923 bug 5067; bugfix on 0.2.0.10-alpha.
2924 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
2925 managed pluggable transport server proxy's environment.
2926 Previously, we would put it there, even though Tor doesn't
2927 implement an 'extended server port' yet, and even though Tor
2928 almost certainly isn't listening at that address. For now, we set
2929 it to an empty string to avoid crashing older obfsproxies. Bugfix
2931 - Log the heartbeat message every HeartbeatPeriod seconds, not every
2932 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
2933 0.2.3.1-alpha. Bug reported by Scott Bennett.
2934 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
2935 bugfix on 0.2.3.11-alpha.
2936 - Update "ClientOnly" man page entry to explain that there isn't
2937 really any point to messing with it. Resolves ticket 5005.
2938 - Use the correct CVE number for CVE-2011-4576 in our comments and
2939 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
2942 o Code simplifications and refactoring:
2943 - Use the _WIN32 macro throughout our code to detect Windows.
2944 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
2948 Changes in version 0.2.3.11-alpha - 2012-01-22
2949 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
2950 the last step of the plan to limit maximum circuit length, includes
2951 a wide variety of hidden service performance and correctness fixes,
2952 works around an OpenSSL security flaw if your distro is too stubborn
2953 to upgrade, and fixes a bunch of smaller issues.
2956 - Now that Tor 0.2.0.x is completely deprecated, enable the final
2957 part of "Proposal 110: Avoiding infinite length circuits" by
2958 refusing all circuit-extend requests that do not use a relay_early
2959 cell. This change helps Tor resist a class of denial-of-service
2960 attacks by limiting the maximum circuit length.
2961 - Adjust the number of introduction points that a hidden service
2962 will try to maintain based on how long its introduction points
2963 remain in use and how many introductions they handle. Fixes
2965 - Try to use system facilities for enumerating local interface
2966 addresses, before falling back to our old approach (which was
2967 binding a UDP socket, and calling getsockname() on it). That
2968 approach was scaring OS X users whose draconian firewall
2969 software warned about binding to UDP sockets, regardless of
2970 whether packets were sent. Now we try to use getifaddrs(),
2971 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
2972 system supports. Resolves ticket 1827.
2974 o Major security workaround:
2975 - When building or running with any version of OpenSSL earlier
2976 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
2977 versions have a bug (CVE-2011-4576) in which their block cipher
2978 padding includes uninitialized data, potentially leaking sensitive
2979 information to any peer with whom they make a SSLv3 connection. Tor
2980 does not use SSL v3 by default, but a hostile client or server
2981 could force an SSLv3 connection in order to gain information that
2982 they shouldn't have been able to get. The best solution here is to
2983 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
2984 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
2985 to make sure that the bug can't happen.
2988 - Fix the SOCKET_OK test that we use to tell when socket
2989 creation fails so that it works on Win64. Fixes part of bug 4533;
2990 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
2991 - Correct our replacements for the timeradd() and timersub() functions
2992 on platforms that lack them (for example, Windows). The timersub()
2993 function is used when expiring circuits, while timeradd() is
2994 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
2995 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
2996 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
2997 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
2998 bug at runtime, not compile time, because some distributions hack
2999 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
3000 on 0.2.3.9-alpha. Found by Pascal.
3002 o Minor features (controller):
3003 - Use absolute path names when reporting the torrc filename in the
3004 control protocol, so a controller can more easily find the torrc
3005 file. Resolves bug 1101.
3006 - Extend the control protocol to report flags that control a circuit's
3007 path selection in CIRC events and in replies to 'GETINFO
3008 circuit-status'. Implements part of ticket 2411.
3009 - Extend the control protocol to report the hidden service address
3010 and current state of a hidden-service-related circuit in CIRC
3011 events and in replies to 'GETINFO circuit-status'. Implements part
3013 - When reporting the path to the cookie file to the controller,
3014 give an absolute path. Resolves ticket 4881.
3015 - Allow controllers to request an event notification whenever a
3016 circuit is cannibalized or its purpose is changed. Implements
3017 part of ticket 3457.
3018 - Include the creation time of a circuit in CIRC and CIRC2
3019 control-port events and the list produced by the 'GETINFO
3020 circuit-status' control-port command.
3022 o Minor features (directory authorities):
3023 - Directory authorities now reject versions of Tor older than
3024 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
3025 inclusive. These versions accounted for only a small fraction of
3026 the Tor network, and have numerous known security issues. Resolves
3028 - Authority operators can now vote for all relays in a given
3029 set of countries to be BadDir/BadExit/Invalid/Rejected.
3030 - Provide two consensus parameters (FastFlagMinThreshold and
3031 FastFlagMaxThreshold) to control the range of allowable bandwidths
3032 for the Fast directory flag. These allow authorities to run
3033 experiments on appropriate requirements for being a "Fast" node.
3034 The AuthDirFastGuarantee config value still applies. Implements
3036 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
3037 directory authority option (introduced in Tor 0.2.2.34).
3039 o Minor features (other):
3040 - Don't disable the DirPort when we cannot exceed our AccountingMax
3041 limit during this interval because the effective bandwidthrate is
3042 low enough. This is useful in a situation where AccountMax is only
3043 used as an additional safeguard or to provide statistics.
3044 - Prepend an informative header to generated dynamic_dh_params files.
3045 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
3046 EntryNodes will have no effect. Resolves issue 2571.
3047 - Log more useful messages when we fail to disable debugger
3049 - Log which authority we're missing votes from when we go to fetch
3050 them from the other auths.
3051 - Log (at debug level) whenever a circuit's purpose is changed.
3052 - Add missing documentation for the MaxClientCircuitsPending,
3053 UseMicrodescriptors, UserspaceIOCPBuffers, and
3054 _UseFilteringSSLBufferevents options, all introduced during
3056 - Update to the January 3 2012 Maxmind GeoLite Country database.
3058 o Minor bugfixes (hidden services):
3059 - Don't close hidden service client circuits which have almost
3060 finished connecting to their destination when they reach
3061 the normal circuit-build timeout. Previously, we would close
3062 introduction circuits which are waiting for an acknowledgement
3063 from the introduction point, and rendezvous circuits which have
3064 been specified in an INTRODUCE1 cell sent to a hidden service,
3065 after the normal CBT. Now, we mark them as 'timed out', and launch
3066 another rendezvous attempt in parallel. This behavior change can
3067 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
3068 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
3069 - Don't close hidden-service-side rendezvous circuits when they
3070 reach the normal circuit-build timeout. This behaviour change can
3071 be disabled using the new
3072 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
3073 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
3074 - Make sure we never mark the wrong rendezvous circuit as having
3075 had its introduction cell acknowleged by the introduction-point
3076 relay. Previously, when we received an INTRODUCE_ACK cell on a
3077 client-side hidden-service introduction circuit, we might have
3078 marked a rendezvous circuit other than the one we specified in
3079 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
3080 a warning message and interfered with the hidden service
3081 connection-establishment process. Fixes bug 4759; bugfix on
3082 0.2.3.3-alpha, when we added the stream-isolation feature which
3083 might cause Tor to open multiple rendezvous circuits for the same
3085 - Don't trigger an assertion failure when we mark a new client-side
3086 hidden-service introduction circuit for close during the process
3087 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
3090 o Minor bugfixes (log messages):
3091 - Correctly spell "connect" in a log message on failure to create a
3092 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
3094 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
3095 Fixes bug 4856; bugfix on Tor 0.0.6.
3096 - Fix the log message describing how we work around discovering
3097 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
3098 4837; bugfix on 0.2.2.9-alpha.
3099 - When logging about a disallowed .exit name, do not also call it
3100 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
3102 o Minor bugfixes (build fixes):
3103 - During configure, detect when we're building with clang version
3104 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
3105 CFLAGS. clang doesn't support them yet.
3106 - During configure, search for library containing cos function as
3107 libm lives in libcore on some platforms (BeOS/Haiku). Linking
3108 against libm was hard-coded before. Fixes the first part of bug
3109 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
3111 - Detect attempts to build Tor on (as yet hypothetical) versions
3112 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
3113 fix for bug 4533. Bugfix on 0.2.2.28-beta.
3114 - Preprocessor directives should not be put inside the arguments
3115 of a macro. This would break compilation with GCC releases prior
3116 to version 3.3. We would never recommend such an old GCC version,
3117 but it is apparently required for binary compatibility on some
3118 platforms (namely, certain builds of Haiku). Fixes the other part
3119 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
3122 o Minor bugfixes (other):
3123 - Older Linux kernels erroneously respond to strange nmap behavior
3124 by having accept() return successfully with a zero-length
3125 socket. When this happens, just close the connection. Previously,
3126 we would try harder to learn the remote address: but there was
3127 no such remote address to learn, and our method for trying to
3128 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
3129 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
3130 - Fix null-pointer access that could occur if TLS allocation failed.
3131 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
3132 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
3133 accidentally been reverted.
3134 - Fix our implementation of crypto_random_hostname() so it can't
3135 overflow on ridiculously large inputs. (No Tor version has ever
3136 provided this kind of bad inputs, but let's be correct in depth.)
3137 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
3138 - Find more places in the code that should have been testing for
3139 invalid sockets using the SOCKET_OK macro. Required for a fix
3140 for bug 4533. Bugfix on 0.2.2.28-beta.
3141 - Fix an assertion failure when, while running with bufferevents, a
3142 connection finishes connecting after it is marked for close, but
3143 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
3144 - test_util_spawn_background_ok() hardcoded the expected value
3145 for ENOENT to 2. This isn't portable as error numbers are
3146 platform specific, and particularly the hurd has ENOENT at
3147 0x40000002. Construct expected string at runtime, using the correct
3148 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
3149 - Reject attempts to disable DisableDebuggerAttachment while Tor is
3150 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
3151 - Use an appropriate-width type for sockets in tor-fw-helper on
3152 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
3155 - When sending or relaying a RELAY_EARLY cell, we used to convert
3156 it to a RELAY cell if the connection was using the v1 link
3157 protocol. This was a workaround for older versions of Tor, which
3158 didn't handle RELAY_EARLY cells properly. Now that all supported
3159 versions can handle RELAY_EARLY cells, and now that we're enforcing
3160 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
3161 remove this workaround. Addresses bug 4786.
3163 o Code simplifications and refactoring:
3164 - Use OpenSSL's built-in SSL_state_string_long() instead of our
3165 own homebrewed ssl_state_to_string() replacement. Patch from
3166 Emile Snyder. Fixes bug 4653.
3167 - Use macros to indicate OpenSSL versions, so we don't need to worry
3168 about accidental hexadecimal bit shifts.
3169 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
3171 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
3172 - Use the smartlist_add_asprintf() alias more consistently.
3173 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
3174 invalid value, rather than just -1.
3175 - Rename a handful of old identifiers, mostly related to crypto
3176 structures and crypto functions. By convention, our "create an
3177 object" functions are called "type_new()", our "free an object"
3178 functions are called "type_free()", and our types indicate that
3179 they are types only with a final "_t". But a handful of older
3180 types and functions broke these rules, with function names like
3181 "type_create" or "subsystem_op_type", or with type names like
3185 Changes in version 0.2.3.10-alpha - 2011-12-16
3186 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
3187 Tor's buffers code. Absolutely everybody should upgrade.
3189 The bug relied on an incorrect calculation when making data continuous
3190 in one of our IO buffers, if the first chunk of the buffer was
3191 misaligned by just the wrong amount. The miscalculation would allow an
3192 attacker to overflow a piece of heap-allocated memory. To mount this
3193 attack, the attacker would need to either open a SOCKS connection to
3194 Tor's SocksPort (usually restricted to localhost), or target a Tor
3195 instance configured to make its connections through a SOCKS proxy
3196 (which Tor does not do by default).
3198 Good security practice requires that all heap-overflow bugs should be
3199 presumed to be exploitable until proven otherwise, so we are treating
3200 this as a potential code execution attack. Please upgrade immediately!
3201 This bug does not affect bufferevents-based builds of Tor. Special
3202 thanks to "Vektor" for reporting this issue to us!
3204 This release also contains a few minor bugfixes for issues discovered
3208 - Fix a heap overflow bug that could occur when trying to pull
3209 data into the first chunk of a buffer, when that chunk had
3210 already had some data drained from it. Fixes CVE-2011-2778;
3211 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3214 - If we can't attach streams to a rendezvous circuit when we
3215 finish connecting to a hidden service, clear the rendezvous
3216 circuit's stream-isolation state and try to attach streams
3217 again. Previously, we cleared rendezvous circuits' isolation
3218 state either too early (if they were freshly built) or not at all
3219 (if they had been built earlier and were cannibalized). Bugfix on
3220 0.2.3.3-alpha; fixes bug 4655.
3221 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
3222 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
3223 - Fix an assertion failure when a relay with accounting enabled
3224 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
3227 - Update to the December 6 2011 Maxmind GeoLite Country database.
3230 Changes in version 0.2.2.35 - 2011-12-16
3231 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
3232 buffers code. Absolutely everybody should upgrade.
3234 The bug relied on an incorrect calculation when making data continuous
3235 in one of our IO buffers, if the first chunk of the buffer was
3236 misaligned by just the wrong amount. The miscalculation would allow an
3237 attacker to overflow a piece of heap-allocated memory. To mount this
3238 attack, the attacker would need to either open a SOCKS connection to
3239 Tor's SocksPort (usually restricted to localhost), or target a Tor
3240 instance configured to make its connections through a SOCKS proxy
3241 (which Tor does not do by default).
3243 Good security practice requires that all heap-overflow bugs should be
3244 presumed to be exploitable until proven otherwise, so we are treating
3245 this as a potential code execution attack. Please upgrade immediately!
3246 This bug does not affect bufferevents-based builds of Tor. Special
3247 thanks to "Vektor" for reporting this issue to us!
3249 Tor 0.2.2.35 also fixes several bugs in previous versions, including
3250 crash bugs for unusual configurations, and a long-term bug that
3251 would prevent Tor from starting on Windows machines with draconian
3254 With this release, we remind everyone that 0.2.0.x has reached its
3255 formal end-of-life. Those Tor versions have many known flaws, and
3256 nobody should be using them. You should upgrade -- ideally to the
3257 0.2.2.x series. If you're using a Linux or BSD and its packages are
3258 obsolete, stop using those packages and upgrade anyway.
3260 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
3261 longer receive support after some time in early 2012.
3264 - Fix a heap overflow bug that could occur when trying to pull
3265 data into the first chunk of a buffer, when that chunk had
3266 already had some data drained from it. Fixes CVE-2011-2778;
3267 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3268 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3269 that it doesn't attempt to allocate a socketpair. This could cause
3270 some problems on Windows systems with overzealous firewalls. Fix for
3271 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3273 - If we mark an OR connection for close based on a cell we process,
3274 don't process any further cells on it. We already avoid further
3275 reads on marked-for-close connections, but now we also discard the
3276 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3277 which was the first version where we might mark a connection for
3278 close based on processing a cell on it.
3279 - Correctly sanity-check that we don't underflow on a memory
3280 allocation (and then assert) for hidden service introduction
3281 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3282 bugfix on 0.2.1.5-alpha.
3283 - Fix a memory leak when we check whether a hidden service
3284 descriptor has any usable introduction points left. Fixes bug
3285 4424. Bugfix on 0.2.2.25-alpha.
3286 - Don't crash when we're running as a relay and don't have a GeoIP
3287 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
3288 we've had in the 0.2.3.x branch already.
3289 - When running as a client, do not print a misleading (and plain
3290 wrong) log message that we're collecting "directory request"
3291 statistics: clients don't collect statistics. Also don't create a
3292 useless (because empty) stats file in the stats/ directory. Fixes
3293 bug 4353; bugfix on 0.2.2.34.
3296 - Detect failure to initialize Libevent. This fix provides better
3297 detection for future instances of bug 4457.
3298 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3299 function. This was eating up hideously large amounts of time on some
3300 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3301 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3302 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3304 - Don't warn about unused log_mutex in log.c when building with
3305 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3306 0.1.0.6-rc which introduced --disable-threads.
3307 - When configuring, starting, or stopping an NT service, stop
3308 immediately after the service configuration attempt has succeeded
3309 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3310 - When sending a NETINFO cell, include the original address
3311 received for the other side, not its canonical address. Found
3312 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3313 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
3314 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3315 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3316 occurred when a client tried to fetch a descriptor for a bridge
3317 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3318 - Backport fixes for a pair of compilation warnings on Windows.
3319 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
3320 - If we had ever tried to call tor_addr_to_str on an address of
3321 unknown type, we would have done a strdup on an uninitialized
3322 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3323 Reported by "troll_un".
3324 - Correctly detect and handle transient lookup failures from
3325 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3326 Reported by "troll_un".
3327 - Fix null-pointer access that could occur if TLS allocation failed.
3328 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3329 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3330 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3333 - Add two new config options for directory authorities:
3334 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3335 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3336 that is always sufficient to satisfy the bandwidth requirement for
3337 the Guard flag. Now it will be easier for researchers to simulate
3338 Tor networks with different values. Resolves ticket 4484.
3339 - When Tor ignores a hidden service specified in its configuration,
3340 include the hidden service's directory in the warning message.
3341 Previously, we would only tell the user that some hidden service
3342 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3343 - Update to the December 6 2011 Maxmind GeoLite Country database.
3345 o Packaging changes:
3346 - Make it easier to automate expert package builds on Windows,
3347 by removing an absolute path from makensis.exe command.
3350 Changes in version 0.2.1.32 - 2011-12-16
3351 Tor 0.2.1.32 backports important security and privacy fixes for
3352 oldstable. This release is intended only for package maintainers and
3353 others who cannot use the 0.2.2 stable series. All others should be
3354 using Tor 0.2.2.x or newer.
3356 The Tor 0.2.1.x series will reach formal end-of-life some time in
3357 early 2012; we will stop releasing patches for it then.
3359 o Major bugfixes (also included in 0.2.2.x):
3360 - Correctly sanity-check that we don't underflow on a memory
3361 allocation (and then assert) for hidden service introduction
3362 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3363 bugfix on 0.2.1.5-alpha.
3364 - Fix a heap overflow bug that could occur when trying to pull
3365 data into the first chunk of a buffer, when that chunk had
3366 already had some data drained from it. Fixes CVE-2011-2778;
3367 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
3370 - Update to the December 6 2011 Maxmind GeoLite Country database.
3373 Changes in version 0.2.3.9-alpha - 2011-12-08
3374 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
3375 a "DisableNetwork" security feature that bundles can use to avoid
3376 touching the network until bridges are configured, moves forward on
3377 the pluggable transport design, fixes a flaw in the hidden service
3378 design that unnecessarily prevented clients with wrong clocks from
3379 reaching hidden services, and fixes a wide variety of other issues.
3382 - Clients can now connect to private bridges over IPv6. Bridges
3383 still need at least one IPv4 address in order to connect to
3384 other relays. Note that we don't yet handle the case where the
3385 user has two bridge lines for the same bridge (one IPv4, one
3386 IPv6). Implements parts of proposal 186.
3387 - New "DisableNetwork" config option to prevent Tor from launching any
3388 connections or accepting any connections except on a control port.
3389 Bundles and controllers can set this option before letting Tor talk
3390 to the rest of the network, for example to prevent any connections
3391 to a non-bridge address. Packages like Orbot can also use this
3392 option to instruct Tor to save power when the network is off.
3393 - Clients and bridges can now be configured to use a separate
3394 "transport" proxy. This approach makes the censorship arms race
3395 easier by allowing bridges to use protocol obfuscation plugins. It
3396 implements the "managed proxy" part of proposal 180 (ticket 3472).
3397 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
3398 implementation. It makes AES_CTR about 7% faster than our old one
3399 (which was about 10% faster than the one OpenSSL used to provide).
3400 Resolves ticket 4526.
3401 - Add a "tor2web mode" for clients that want to connect to hidden
3402 services non-anonymously (and possibly more quickly). As a safety
3403 measure to try to keep users from turning this on without knowing
3404 what they are doing, tor2web mode must be explicitly enabled at
3405 compile time, and a copy of Tor compiled to run in tor2web mode
3406 cannot be used as a normal Tor client. Implements feature 2553.
3407 - Add experimental support for running on Windows with IOCP and no
3408 kernel-space socket buffers. This feature is controlled by a new
3409 "UserspaceIOCPBuffers" config option (off by default), which has
3410 no effect unless Tor has been built with support for bufferevents,
3411 is running on Windows, and has enabled IOCP. This may, in the long
3412 run, help solve or mitigate bug 98.
3413 - Use a more secure consensus parameter voting algorithm. Now at
3414 least three directory authorities or a majority of them must
3415 vote on a given parameter before it will be included in the
3416 consensus. Implements proposal 178.
3419 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
3420 They used to check that the timestamp was within 30 minutes
3421 of their system clock, so they could cap the size of their
3422 replay-detection cache, but that approach unnecessarily refused
3423 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
3424 the v3 intro-point protocol (the first one which sent a timestamp
3425 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
3426 - Only use the EVP interface when AES acceleration is enabled,
3427 to avoid a 5-7% performance regression. Resolves issue 4525;
3428 bugfix on 0.2.3.8-alpha.
3430 o Privacy/anonymity features (bridge detection):
3431 - Make bridge SSL certificates a bit more stealthy by using random
3432 serial numbers, in the same fashion as OpenSSL when generating
3433 self-signed certificates. Implements ticket 4584.
3434 - Introduce a new config option "DynamicDHGroups", enabled by
3435 default, which provides each bridge with a unique prime DH modulus
3436 to be used during SSL handshakes. This option attempts to help
3437 against censors who might use the Apache DH modulus as a static
3438 identifier for bridges. Addresses ticket 4548.
3440 o Minor features (new/different config options):
3441 - New configuration option "DisableDebuggerAttachment" (on by default)
3442 to prevent basic debugging attachment attempts by other processes.
3443 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
3444 - Allow MapAddress directives to specify matches against super-domains,
3445 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
3446 Implements issue 933.
3447 - Slightly change behavior of "list" options (that is, config
3448 options that can appear more than once) when they appear both in
3449 torrc and on the command line. Previously, the command-line options
3450 would be appended to the ones from torrc. Now, the command-line
3451 options override the torrc options entirely. This new behavior
3452 allows the user to override list options (like exit policies and
3453 ports to listen on) from the command line, rather than simply
3454 appending to the list.
3455 - You can get the old (appending) command-line behavior for "list"
3456 options by prefixing the option name with a "+".
3457 - You can remove all the values for a "list" option from the command
3458 line without adding any new ones by prefixing the option name
3460 - Add experimental support for a "defaults" torrc file to be parsed
3461 before the regular torrc. Torrc options override the defaults file's
3462 options in the same way that the command line overrides the torrc.
3463 The SAVECONF controller command saves only those options which
3464 differ between the current configuration and the defaults file. HUP
3465 reloads both files. (Note: This is an experimental feature; its
3466 behavior will probably be refined in future 0.2.3.x-alpha versions
3467 to better meet packagers' needs.) Implements task 4552.
3470 - Try to make the introductory warning message that Tor prints on
3471 startup more useful for actually finding help and information.
3472 Resolves ticket 2474.
3473 - Running "make version" now displays the version of Tor that
3474 we're about to build. Idea from katmagic; resolves issue 4400.
3475 - Expire old or over-used hidden service introduction points.
3476 Required by fix for bug 3460.
3477 - Move the replay-detection cache for the RSA-encrypted parts of
3478 INTRODUCE2 cells to the introduction point data structures.
3479 Previously, we would use one replay-detection cache per hidden
3480 service. Required by fix for bug 3460.
3481 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
3482 public key replay-detection cache from 60 minutes to 5 minutes. This
3483 replay-detection cache is now used only to detect multiple
3484 INTRODUCE2 cells specifying the same rendezvous point, so we can
3485 avoid launching multiple simultaneous attempts to connect to it.
3487 o Minor bugfixes (on Tor 0.2.2.x and earlier):
3488 - Resolve an integer overflow bug in smartlist_ensure_capacity().
3489 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
3491 - Fix a minor formatting issue in one of tor-gencert's error messages.
3493 - Prevent a false positive from the check-spaces script, by disabling
3494 the "whitespace between function name and (" check for functions
3496 - Fix a log message suggesting that people contact a non-existent
3497 email address. Fixes bug 3448.
3498 - Fix null-pointer access that could occur if TLS allocation failed.
3499 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
3500 - Report a real bootstrap problem to the controller on router
3501 identity mismatch. Previously we just said "foo", which probably
3502 made a lot of sense at the time. Fixes bug 4169; bugfix on
3504 - If we had ever tried to call tor_addr_to_str() on an address of
3505 unknown type, we would have done a strdup() on an uninitialized
3506 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
3507 Reported by "troll_un".
3508 - Correctly detect and handle transient lookup failures from
3509 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
3510 Reported by "troll_un".
3511 - Use tor_socket_t type for listener argument to accept(). Fixes bug
3512 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
3513 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
3514 bug 4532; found by "troll_un".
3516 o Minor bugfixes (on Tor 0.2.3.x):
3517 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
3519 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
3520 circuit for use as a hidden service client's rendezvous point.
3521 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
3522 with help from wanoskarnet.
3523 - Restore behavior of overriding SocksPort, ORPort, and similar
3524 options from the command line. Bugfix on 0.2.3.3-alpha.
3527 - Properly handle the case where the build-tree is not the same
3528 as the source tree when generating src/common/common_sha1.i,
3529 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
3530 bugfix on 0.2.0.1-alpha.
3532 o Code simplifications, cleanups, and refactorings:
3533 - Remove the pure attribute from all functions that used it
3534 previously. In many cases we assigned it incorrectly, because the
3535 functions might assert or call impure functions, and we don't have
3536 evidence that keeping the pure attribute is worthwhile. Implements
3537 changes suggested in ticket 4421.
3538 - Remove some dead code spotted by coverity. Fixes cid 432.
3539 Bugfix on 0.2.3.1-alpha, closes bug 4637.
3542 Changes in version 0.2.3.8-alpha - 2011-11-22
3543 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
3544 socketpair-related bug that has been bothering Windows users. It adds
3545 support to serve microdescriptors to controllers, so Vidalia's network
3546 map can resume listing relays (once Vidalia implements its side),
3547 and adds better support for hardware AES acceleration. Finally, it
3548 starts the process of adjusting the bandwidth cutoff for getting the
3549 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
3550 that tiny relays harm performance more than they help network capacity.
3553 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
3554 that it doesn't attempt to allocate a socketpair. This could cause
3555 some problems on Windows systems with overzealous firewalls. Fix for
3556 bug 4457; workaround for Libevent versions 2.0.1-alpha through
3558 - Correctly sanity-check that we don't underflow on a memory
3559 allocation (and then assert) for hidden service introduction
3560 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
3561 bugfix on 0.2.1.5-alpha.
3562 - Remove the artificially low cutoff of 20KB to guarantee the Fast
3563 flag. In the past few years the average relay speed has picked
3564 up, and while the "top 7/8 of the network get the Fast flag" and
3565 "all relays with 20KB or more of capacity get the Fast flag" rules
3566 used to have the same result, now the top 7/8 of the network has
3567 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
3568 - Fix a rare assertion failure when checking whether a v0 hidden
3569 service descriptor has any usable introduction points left, and
3570 we don't have enough information to build a circuit to the first
3571 intro point named in the descriptor. The HS client code in
3572 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
3573 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
3574 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
3575 - Make bridge authorities not crash when they are asked for their own
3576 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
3577 - When running as a client, do not print a misleading (and plain
3578 wrong) log message that we're collecting "directory request"
3579 statistics: clients don't collect statistics. Also don't create a
3580 useless (because empty) stats file in the stats/ directory. Fixes
3581 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
3584 - Allow Tor controllers like Vidalia to obtain the microdescriptor
3585 for a relay by identity digest or nickname. Previously,
3586 microdescriptors were only available by their own digests, so a
3587 controller would have to ask for and parse the whole microdescriptor
3588 consensus in order to look up a single relay's microdesc. Fixes
3589 bug 3832; bugfix on 0.2.3.1-alpha.
3590 - Use OpenSSL's EVP interface for AES encryption, so that all AES
3591 operations can use hardware acceleration (if present). Resolves
3594 o Minor bugfixes (on 0.2.2.x and earlier):
3595 - Detect failure to initialize Libevent. This fix provides better
3596 detection for future instances of bug 4457.
3597 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
3598 function. This was eating up hideously large amounts of time on some
3599 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
3600 - Don't warn about unused log_mutex in log.c when building with
3601 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
3602 0.1.0.6-rc which introduced --disable-threads.
3603 - Allow manual 'authenticate' commands to the controller interface
3604 from netcat (nc) as well as telnet. We were rejecting them because
3605 they didn't come with the expected whitespace at the end of the
3606 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
3607 - Fix some (not actually triggerable) buffer size checks in usage of
3608 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
3610 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
3611 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
3612 - When configuring, starting, or stopping an NT service, stop
3613 immediately after the service configuration attempt has succeeded
3614 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
3615 - When sending a NETINFO cell, include the original address
3616 received for the other side, not its canonical address. Found
3617 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
3618 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
3619 can pick them up when the tests aren't disabled. Bugfix on
3620 0.2.2.4-alpha which introduced tinytest.
3621 - Fix a memory leak when we check whether a hidden service
3622 descriptor has any usable introduction points left. Fixes bug
3623 4424. Bugfix on 0.2.2.25-alpha.
3624 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
3625 occurred when a client tried to fetch a descriptor for a bridge
3626 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
3628 o Minor bugfixes (on 0.2.3.x):
3629 - Make util unit tests build correctly with MSVC. Bugfix on
3630 0.2.3.3-alpha. Patch by Gisle Vanem.
3631 - Successfully detect AUTH_CHALLENGE cells with no recognized
3632 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
3634 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
3635 it should still send a NETINFO cell to allow the connection to
3636 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
3638 - Log less loudly when we get an invalid authentication certificate
3639 from a source other than a directory authority: it's not unusual
3640 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
3642 - Tolerate servers with more clock skew in their authentication
3643 certificates than previously. Fixes bug 4371; bugfix on
3645 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
3646 on 0.2.3.4-alpha and 0.2.3.6-alpha.
3649 - Add two new config options for directory authorities:
3650 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
3651 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
3652 that is always sufficient to satisfy the bandwidth requirement for
3653 the Guard flag. Now it will be easier for researchers to simulate
3654 Tor networks with different values. Resolves ticket 4484.
3655 - When Tor ignores a hidden service specified in its configuration,
3656 include the hidden service's directory in the warning message.
3657 Previously, we would only tell the user that some hidden service
3658 was ignored. Bugfix on 0.0.6; fixes bug 4426.
3659 - When we fail to initialize Libevent, retry with IOCP disabled so we
3660 don't need to turn on multi-threading support in Libevent, which in
3661 turn requires a working socketpair(). This is a workaround for bug
3662 4457, which affects Libevent versions from 2.0.1-alpha through
3664 - Detect when we try to build on a platform that doesn't define
3665 AF_UNSPEC to 0. We don't work there, so refuse to compile.
3666 - Update to the November 1 2011 Maxmind GeoLite Country database.
3668 o Packaging changes:
3669 - Make it easier to automate expert package builds on Windows,
3670 by removing an absolute path from makensis.exe command.
3672 o Code simplifications and refactoring:
3673 - Remove some redundant #include directives throughout the code.
3674 Patch from Andrea Gelmini.
3675 - Unconditionally use OpenSSL's AES implementation instead of our
3676 old built-in one. OpenSSL's AES has been better for a while, and
3677 relatively few servers should still be on any version of OpenSSL
3678 that doesn't have good optimized assembly AES.
3679 - Use the name "CERTS" consistently to refer to the new cell type;
3680 we were calling it CERT in some places and CERTS in others.
3683 - Numerous new unit tests for functions in util.c and address.c by
3685 - The long-disabled benchmark tests are now split into their own
3686 ./src/test/bench binary.
3687 - The benchmark tests can now use more accurate timers than
3688 gettimeofday() when such timers are available.
3691 Changes in version 0.2.3.7-alpha - 2011-10-30
3692 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
3693 the new v3 handshake. It also resolves yet another bridge address
3697 - If we mark an OR connection for close based on a cell we process,
3698 don't process any further cells on it. We already avoid further
3699 reads on marked-for-close connections, but now we also discard the
3700 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
3701 which was the first version where we might mark a connection for
3702 close based on processing a cell on it.
3703 - Fix a double-free bug that would occur when we received an invalid
3704 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
3705 bugfix on 0.2.3.6-alpha.
3706 - Bridges no longer include their address in NETINFO cells on outgoing
3707 OR connections, to allow them to blend in better with clients.
3708 Removes another avenue for enumerating bridges. Reported by
3709 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
3710 cells were introduced.
3713 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
3714 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
3717 Changes in version 0.2.3.6-alpha - 2011-10-26
3718 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
3719 anonymity vulnerability where an attacker can deanonymize Tor
3720 users. Everybody should upgrade.
3722 This release also features support for a new v3 connection handshake
3723 protocol, and fixes to make hidden service connections more robust.
3726 - Implement a new handshake protocol (v3) for authenticating Tors to
3727 each other over TLS. It should be more resistant to fingerprinting
3728 than previous protocols, and should require less TLS hacking for
3729 future Tor implementations. Implements proposal 176.
3730 - Allow variable-length padding cells to disguise the length of
3731 Tor's TLS records. Implements part of proposal 184.
3733 o Privacy/anonymity fixes (clients):
3734 - Clients and bridges no longer send TLS certificate chains on
3735 outgoing OR connections. Previously, each client or bridge would
3736 use the same cert chain for all outgoing OR connections until
3737 its IP address changes, which allowed any relay that the client
3738 or bridge contacted to determine which entry guards it is using.
3739 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3740 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3741 no longer considers that connection as suitable for satisfying a
3742 circuit EXTEND request. Now relays can protect clients from the
3743 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3744 - Directory authorities no longer assign the Guard flag to relays
3745 that haven't upgraded to the above "refuse EXTEND requests
3746 to client connections" fix. Now directory authorities can
3747 protect clients from the CVE-2011-2768 issue even if neither
3748 the clients nor the relays have upgraded yet. There's a new
3749 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3750 to let us transition smoothly, else tomorrow there would be no
3753 o Major bugfixes (hidden services):
3754 - Improve hidden service robustness: when an attempt to connect to
3755 a hidden service ends, be willing to refetch its hidden service
3756 descriptors from each of the HSDir relays responsible for them
3757 immediately. Previously, we would not consider refetching the
3758 service's descriptors from each HSDir for 15 minutes after the last
3759 fetch, which was inconvenient if the hidden service was not running
3760 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
3761 - When one of a hidden service's introduction points appears to be
3762 unreachable, stop trying it. Previously, we would keep trying
3763 to build circuits to the introduction point until we lost the
3764 descriptor, usually because the user gave up and restarted Tor.
3765 Partly fixes bug 3825.
3766 - Don't launch a useless circuit after failing to use one of a
3767 hidden service's introduction points. Previously, we would
3768 launch a new introduction circuit, but not set the hidden service
3769 which that circuit was intended to connect to, so it would never
3770 actually be used. A different piece of code would then create a
3771 new introduction circuit correctly. Bug reported by katmagic and
3772 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3774 o Major bugfixes (other):
3775 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3776 that they initiated. Relays could distinguish incoming bridge
3777 connections from client connections, creating another avenue for
3778 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3779 Found by "frosty_un".
3780 - Don't update the AccountingSoftLimitHitAt state file entry whenever
3781 tor gets started. This prevents a wrong average bandwidth
3782 estimate, which would cause relays to always start a new accounting
3783 interval at the earliest possible moment. Fixes bug 2003; bugfix
3784 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
3785 immensely in tracking this bug down.
3786 - Fix a crash bug when changing node restrictions while a DNS lookup
3787 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3790 o Minor bugfixes (on 0.2.2.x and earlier):
3791 - When a hidden service turns an extra service-side introduction
3792 circuit into a general-purpose circuit, free the rend_data and
3793 intro_key fields first, so we won't leak memory if the circuit
3794 is cannibalized for use as another service-side introduction
3795 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3796 - Rephrase the log message emitted if the TestSocks check is
3797 successful. Patch from Fabian Keil; fixes bug 4094.
3798 - Bridges now skip DNS self-tests, to act a little more stealthily.
3799 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3800 bridges. Patch by "warms0x".
3801 - Remove a confusing dollar sign from the example fingerprint in the
3802 man page, and also make the example fingerprint a valid one. Fixes
3803 bug 4309; bugfix on 0.2.1.3-alpha.
3804 - Fix internal bug-checking logic that was supposed to catch
3805 failures in digest generation so that it will fail more robustly
3806 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3807 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3808 - Report any failure in init_keys() calls launched because our
3809 IP address has changed. Spotted by Coverity Scan. Bugfix on
3810 0.1.1.4-alpha; fixes CID 484.
3812 o Minor bugfixes (on 0.2.3.x):
3813 - Fix a bug in configure.in that kept it from building a configure
3814 script with autoconf versions earlier than 2.61. Fixes bug 2430;
3815 bugfix on 0.2.3.1-alpha.
3816 - Don't warn users that they are exposing a client port to the
3817 Internet if they have specified an RFC1918 address. Previously,
3818 we would warn if the user had specified any non-loopback
3819 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
3820 - Fix memory leaks in the failing cases of the new SocksPort and
3821 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
3822 fixes coverity CIDs 485, 486, and 487.
3825 - When a hidden service's introduction point times out, consider
3826 trying it again during the next attempt to connect to the
3827 HS. Previously, we would not try it again unless a newly fetched
3828 descriptor contained it. Required by fixes for bugs 1297 and 3825.
3829 - The next version of Windows will be called Windows 8, and it has
3830 a major version of 6, minor version of 2. Correctly identify that
3831 version instead of calling it "Very recent version". Resolves
3832 ticket 4153; reported by funkstar.
3833 - The Bridge Authority now writes statistics on how many bridge
3834 descriptors it gave out in total, and how many unique descriptors
3835 it gave out. It also lists how often the most and least commonly
3836 fetched descriptors were given out, as well as the median and
3837 25th/75th percentile. Implements tickets 4200 and 4294.
3838 - Update to the October 4 2011 Maxmind GeoLite Country database.
3840 o Code simplifications and refactoring:
3841 - Remove some old code to remember statistics about which descriptors
3842 we've served as a directory mirror. The feature wasn't used and
3843 is outdated now that microdescriptors are around.
3844 - Rename Tor functions that turn strings into addresses, so that
3845 "parse" indicates that no hostname resolution occurs, and
3846 "lookup" indicates that hostname resolution may occur. This
3847 should help prevent mistakes in the future. Fixes bug 3512.
3850 Changes in version 0.2.2.34 - 2011-10-26
3851 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
3852 can deanonymize Tor users. Everybody should upgrade.
3854 The attack relies on four components: 1) Clients reuse their TLS cert
3855 when talking to different relays, so relays can recognize a user by
3856 the identity key in her cert. 2) An attacker who knows the client's
3857 identity key can probe each guard relay to see if that identity key
3858 is connected to that guard relay right now. 3) A variety of active
3859 attacks in the literature (starting from "Low-Cost Traffic Analysis
3860 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
3861 discover the guard relays that a Tor user visiting the website is using.
3862 4) Clients typically pick three guards at random, so the set of guards
3863 for a given user could well be a unique fingerprint for her. This
3864 release fixes components #1 and #2, which is enough to block the attack;
3865 the other two remain as open research problems. Special thanks to
3866 "frosty_un" for reporting the issue to us!
3868 Clients should upgrade so they are no longer recognizable by the TLS
3869 certs they present. Relays should upgrade so they no longer allow a
3870 remote attacker to probe them to test whether unpatched clients are
3871 currently connected to them.
3873 This release also fixes several vulnerabilities that allow an attacker
3874 to enumerate bridge relays. Some bridge enumeration attacks still
3875 remain; see for example proposal 188.
3877 o Privacy/anonymity fixes (clients):
3878 - Clients and bridges no longer send TLS certificate chains on
3879 outgoing OR connections. Previously, each client or bridge would
3880 use the same cert chain for all outgoing OR connections until
3881 its IP address changes, which allowed any relay that the client
3882 or bridge contacted to determine which entry guards it is using.
3883 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3884 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3885 no longer considers that connection as suitable for satisfying a
3886 circuit EXTEND request. Now relays can protect clients from the
3887 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3888 - Directory authorities no longer assign the Guard flag to relays
3889 that haven't upgraded to the above "refuse EXTEND requests
3890 to client connections" fix. Now directory authorities can
3891 protect clients from the CVE-2011-2768 issue even if neither
3892 the clients nor the relays have upgraded yet. There's a new
3893 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
3894 to let us transition smoothly, else tomorrow there would be no
3897 o Privacy/anonymity fixes (bridge enumeration):
3898 - Bridge relays now do their directory fetches inside Tor TLS
3899 connections, like all the other clients do, rather than connecting
3900 directly to the DirPort like public relays do. Removes another
3901 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
3902 - Bridges relays now build circuits for themselves in a more similar
3903 way to how clients build them. Removes another avenue for
3904 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
3905 when bridges were introduced.
3906 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3907 that they initiated. Relays could distinguish incoming bridge
3908 connections from client connections, creating another avenue for
3909 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3910 Found by "frosty_un".
3913 - Fix a crash bug when changing node restrictions while a DNS lookup
3914 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
3916 - Don't launch a useless circuit after failing to use one of a
3917 hidden service's introduction points. Previously, we would
3918 launch a new introduction circuit, but not set the hidden service
3919 which that circuit was intended to connect to, so it would never
3920 actually be used. A different piece of code would then create a
3921 new introduction circuit correctly. Bug reported by katmagic and
3922 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
3925 - Change an integer overflow check in the OpenBSD_Malloc code so
3926 that GCC is less likely to eliminate it as impossible. Patch
3927 from Mansour Moufid. Fixes bug 4059.
3928 - When a hidden service turns an extra service-side introduction
3929 circuit into a general-purpose circuit, free the rend_data and
3930 intro_key fields first, so we won't leak memory if the circuit
3931 is cannibalized for use as another service-side introduction
3932 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
3933 - Bridges now skip DNS self-tests, to act a little more stealthily.
3934 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
3935 bridges. Patch by "warms0x".
3936 - Fix internal bug-checking logic that was supposed to catch
3937 failures in digest generation so that it will fail more robustly
3938 if we ask for a nonexistent algorithm. Found by Coverity Scan.
3939 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
3940 - Report any failure in init_keys() calls launched because our
3941 IP address has changed. Spotted by Coverity Scan. Bugfix on
3942 0.1.1.4-alpha; fixes CID 484.
3944 o Minor bugfixes (log messages and documentation):
3945 - Remove a confusing dollar sign from the example fingerprint in the
3946 man page, and also make the example fingerprint a valid one. Fixes
3947 bug 4309; bugfix on 0.2.1.3-alpha.
3948 - The next version of Windows will be called Windows 8, and it has
3949 a major version of 6, minor version of 2. Correctly identify that
3950 version instead of calling it "Very recent version". Resolves
3951 ticket 4153; reported by funkstar.
3952 - Downgrade log messages about circuit timeout calibration from
3953 "notice" to "info": they don't require or suggest any human
3954 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
3955 bugfix on 0.2.2.14-alpha.
3958 - Turn on directory request statistics by default and include them in
3959 extra-info descriptors. Don't break if we have no GeoIP database.
3960 Backported from 0.2.3.1-alpha; implements ticket 3951.
3961 - Update to the October 4 2011 Maxmind GeoLite Country database.
3964 Changes in version 0.2.1.31 - 2011-10-26
3965 Tor 0.2.1.31 backports important security and privacy fixes for
3966 oldstable. This release is intended only for package maintainers and
3967 others who cannot use the 0.2.2 stable series. All others should be
3968 using Tor 0.2.2.x or newer.
3970 o Security fixes (also included in 0.2.2.x):
3971 - Replace all potentially sensitive memory comparison operations
3972 with versions whose runtime does not depend on the data being
3973 compared. This will help resist a class of attacks where an
3974 adversary can use variations in timing information to learn
3975 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3976 implementation by Robert Ransom based partially on code by DJB.)
3977 - Fix an assert in parsing router descriptors containing IPv6
3978 addresses. This one took down the directory authorities when
3979 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3981 o Privacy/anonymity fixes (also included in 0.2.2.x):
3982 - Clients and bridges no longer send TLS certificate chains on
3983 outgoing OR connections. Previously, each client or bridge would
3984 use the same cert chain for all outgoing OR connections until
3985 its IP address changes, which allowed any relay that the client
3986 or bridge contacted to determine which entry guards it is using.
3987 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
3988 - If a relay receives a CREATE_FAST cell on a TLS connection, it
3989 no longer considers that connection as suitable for satisfying a
3990 circuit EXTEND request. Now relays can protect clients from the
3991 CVE-2011-2768 issue even if the clients haven't upgraded yet.
3992 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
3993 that they initiated. Relays could distinguish incoming bridge
3994 connections from client connections, creating another avenue for
3995 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
3996 Found by "frosty_un".
3997 - When receiving a hidden service descriptor, check that it is for
3998 the hidden service we wanted. Previously, Tor would store any
3999 hidden service descriptors that a directory gave it, whether it
4000 wanted them or not. This wouldn't have let an attacker impersonate
4001 a hidden service, but it did let directories pre-seed a client
4002 with descriptors that it didn't want. Bugfix on 0.0.6.
4003 - Avoid linkability based on cached hidden service descriptors: forget
4004 all hidden service descriptors cached as a client when processing a
4005 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
4006 - Make the bridge directory authority refuse to answer directory
4007 requests for "all" descriptors. It used to include bridge
4008 descriptors in its answer, which was a major information leak.
4009 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
4010 - Don't attach new streams to old rendezvous circuits after SIGNAL
4011 NEWNYM. Previously, we would keep using an existing rendezvous
4012 circuit if it remained open (i.e. if it were kept open by a
4013 long-lived stream, or if a new stream were attached to it before
4014 Tor could notice that it was old and no longer in use). Bugfix on
4015 0.1.1.15-rc; fixes bug 3375.
4017 o Minor bugfixes (also included in 0.2.2.x):
4018 - When we restart our relay, we might get a successful connection
4019 from the outside before we've started our reachability tests,
4020 triggering a warning: "ORPort found reachable, but I have no
4021 routerinfo yet. Failing to inform controller of success." This
4022 bug was harmless unless Tor is running under a controller
4023 like Vidalia, in which case the controller would never get a
4024 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
4026 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
4027 enabled. Fixes bug 1526.
4028 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4029 anything since 0.2.1.16-rc.
4030 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
4031 None of the cases where we did this before were wrong, but by making
4032 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
4033 - Fix a rare crash bug that could occur when a client was configured
4034 with a large number of bridges. Fixes bug 2629; bugfix on
4035 0.2.1.2-alpha. Bugfix by trac user "shitlei".
4036 - Correct the warning displayed when a rendezvous descriptor exceeds
4037 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
4039 - Fix an uncommon assertion failure when running with DNSPort under
4040 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
4041 - When warning about missing zlib development packages during compile,
4042 give the correct package names. Bugfix on 0.2.0.1-alpha.
4043 - Require that introduction point keys and onion keys have public
4044 exponent 65537. Bugfix on 0.2.0.10-alpha.
4045 - Do not crash when our configuration file becomes unreadable, for
4046 example due to a permissions change, between when we start up
4047 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4049 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4051 - Always NUL-terminate the sun_path field of a sockaddr_un before
4052 passing it to the kernel. (Not a security issue: kernels are
4053 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4054 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4055 - Don't stack-allocate the list of supplementary GIDs when we're
4056 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4057 could take up to 256K, which is way too much stack. Found by
4058 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4060 o Minor bugfixes (only in 0.2.1.x):
4061 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
4062 rely on them. Bugfix on 0.2.1.30.
4063 - Use git revisions instead of svn revisions when generating our
4064 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
4066 o Minor features (also included in 0.2.2.x):
4067 - Adjust the expiration time on our SSL session certificates to
4068 better match SSL certs seen in the wild. Resolves ticket 4014.
4069 - Allow nameservers with IPv6 address. Resolves bug 2574.
4070 - Update to the October 4 2011 Maxmind GeoLite Country database.
4073 Changes in version 0.2.3.5-alpha - 2011-09-28
4074 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
4075 bridge relays; fixes an assertion error that many users started hitting
4076 today; and adds the ability to refill token buckets more often than
4077 once per second, allowing significant performance improvements.
4080 - Bridge relays now do their directory fetches inside Tor TLS
4081 connections, like all the other clients do, rather than connecting
4082 directly to the DirPort like public relays do. Removes another
4083 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
4084 - Bridges relays now build circuits for themselves in a more similar
4085 way to how clients build them. Removes another avenue for
4086 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
4087 when bridges were introduced.
4090 - Fix an "Assertion md->held_by_node == 1 failed" error that could
4091 occur when the same microdescriptor was referenced by two node_t
4092 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
4094 o Major features (networking):
4095 - Add a new TokenBucketRefillInterval option to refill token buckets
4096 more frequently than once per second. This should improve network
4097 performance, alleviate queueing problems, and make traffic less
4098 bursty. Implements proposal 183; closes ticket 3630. Design by
4099 Florian Tschorsch and Björn Scheuermann; implementation by
4103 - Change an integer overflow check in the OpenBSD_Malloc code so
4104 that GCC is less likely to eliminate it as impossible. Patch
4105 from Mansour Moufid. Fixes bug 4059.
4107 o Minor bugfixes (usability):
4108 - Downgrade log messages about circuit timeout calibration from
4109 "notice" to "info": they don't require or suggest any human
4110 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
4111 bugfix on 0.2.2.14-alpha.
4113 o Minor features (diagnostics):
4114 - When the system call to create a listener socket fails, log the
4115 error message explaining why. This may help diagnose bug 4027.
4118 Changes in version 0.2.3.4-alpha - 2011-09-13
4119 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
4120 tweak to Tor's TLS handshake that makes relays and bridges that run
4121 this new version reachable from Iran again. It also fixes a few new
4122 bugs in 0.2.3.x, and teaches relays to recognize when they're not
4123 listed in the network consensus and republish.
4125 o Major bugfixes (also part of 0.2.2.33):
4126 - Avoid an assertion failure when reloading a configuration with
4127 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4128 3923; bugfix on 0.2.2.25-alpha.
4130 o Minor features (security, also part of 0.2.2.33):
4131 - Check for replays of the public-key encrypted portion of an
4132 INTRODUCE1 cell, in addition to the current check for replays of
4133 the g^x value. This prevents a possible class of active attacks
4134 by an attacker who controls both an introduction point and a
4135 rendezvous point, and who uses the malleability of AES-CTR to
4136 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4137 that these attacks are infeasible (requiring the attacker to send
4138 on the order of zettabytes of altered cells in a short interval),
4139 but we'd rather block them off in case there are any classes of
4140 this attack that we missed. Reported by Willem Pinckaers.
4142 o Minor features (also part of 0.2.2.33):
4143 - Adjust the expiration time on our SSL session certificates to
4144 better match SSL certs seen in the wild. Resolves ticket 4014.
4145 - Change the default required uptime for a relay to be accepted as
4146 a HSDir (hidden service directory) from 24 hours to 25 hours.
4147 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4148 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4149 authorities to abstain from voting on assignment of the HSDir
4150 consensus flag. Related to bug 2649.
4151 - Update to the September 6 2011 Maxmind GeoLite Country database.
4153 o Minor bugfixes (also part of 0.2.2.33):
4154 - Demote the 'replay detected' log message emitted when a hidden
4155 service receives the same Diffie-Hellman public key in two different
4156 INTRODUCE2 cells to info level. A normal Tor client can cause that
4157 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4158 fixes part of bug 2442.
4159 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4160 level. There is nothing that a hidden service's operator can do
4161 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4163 - Clarify a log message specifying the characters permitted in
4164 HiddenServiceAuthorizeClient client names. Previously, the log
4165 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4166 given the impression that every ASCII character between "+" and "_"
4167 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4169 o Build fixes (also part of 0.2.2.33):
4170 - Clean up some code issues that prevented Tor from building on older
4171 BSDs. Fixes bug 3894; reported by "grarpamp".
4172 - Search for a platform-specific version of "ar" when cross-compiling.
4173 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4176 - Fix a bug where the SocksPort option (for example) would get
4177 ignored and replaced by the default if a SocksListenAddress
4178 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
4182 - Relays now try regenerating and uploading their descriptor more
4183 frequently if they are not listed in the consensus, or if the
4184 version of their descriptor listed in the consensus is too
4185 old. This fix should prevent situations where a server declines
4186 to re-publish itself because it has done so too recently, even
4187 though the authorities decided not to list its recent-enough
4188 descriptor. Fix for bug 3327.
4191 - Relays now include a reason for regenerating their descriptors
4192 in an HTTP header when uploading to the authorities. This will
4193 make it easier to debug descriptor-upload issues in the future.
4194 - When starting as root and then changing our UID via the User
4195 control option, and we have a ControlSocket configured, make sure
4196 that the ControlSocket is owned by the same account that Tor will
4197 run under. Implements ticket 3421; fix by Jérémy Bobbio.
4200 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
4201 utility function used in the control-port code). This shouldn't
4202 ever happen unless Tor is completely out of memory, but if it did
4203 happen and Tor somehow recovered from it, Tor could have sent a log
4204 message to a control port in the middle of a reply to a controller
4205 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
4206 - Make 'FetchUselessDescriptors' cause all descriptor types and
4207 all consensus types (including microdescriptors) to get fetched.
4208 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
4211 - Make a new "entry connection" struct as an internal subtype of "edge
4212 connection", to simplify the code and make exit connections smaller.
4215 Changes in version 0.2.2.33 - 2011-09-13
4216 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
4217 TLS handshake that makes relays and bridges that run this new version
4218 reachable from Iran again.
4221 - Avoid an assertion failure when reloading a configuration with
4222 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
4223 3923; bugfix on 0.2.2.25-alpha.
4225 o Minor features (security):
4226 - Check for replays of the public-key encrypted portion of an
4227 INTRODUCE1 cell, in addition to the current check for replays of
4228 the g^x value. This prevents a possible class of active attacks
4229 by an attacker who controls both an introduction point and a
4230 rendezvous point, and who uses the malleability of AES-CTR to
4231 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
4232 that these attacks are infeasible (requiring the attacker to send
4233 on the order of zettabytes of altered cells in a short interval),
4234 but we'd rather block them off in case there are any classes of
4235 this attack that we missed. Reported by Willem Pinckaers.
4238 - Adjust the expiration time on our SSL session certificates to
4239 better match SSL certs seen in the wild. Resolves ticket 4014.
4240 - Change the default required uptime for a relay to be accepted as
4241 a HSDir (hidden service directory) from 24 hours to 25 hours.
4242 Improves on 0.2.0.10-alpha; resolves ticket 2649.
4243 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
4244 authorities to abstain from voting on assignment of the HSDir
4245 consensus flag. Related to bug 2649.
4246 - Update to the September 6 2011 Maxmind GeoLite Country database.
4248 o Minor bugfixes (documentation and log messages):
4249 - Correct the man page to explain that HashedControlPassword and
4250 CookieAuthentication can both be set, in which case either method
4251 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4252 when we decided to allow these config options to both be set. Issue
4254 - Demote the 'replay detected' log message emitted when a hidden
4255 service receives the same Diffie-Hellman public key in two different
4256 INTRODUCE2 cells to info level. A normal Tor client can cause that
4257 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
4258 fixes part of bug 2442.
4259 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
4260 level. There is nothing that a hidden service's operator can do
4261 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
4263 - Clarify a log message specifying the characters permitted in
4264 HiddenServiceAuthorizeClient client names. Previously, the log
4265 message said that "[A-Za-z0-9+-_]" were permitted; that could have
4266 given the impression that every ASCII character between "+" and "_"
4267 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
4270 - Provide a substitute implementation of lround() for MSVC, which
4271 apparently lacks it. Patch from Gisle Vanem.
4272 - Clean up some code issues that prevented Tor from building on older
4273 BSDs. Fixes bug 3894; reported by "grarpamp".
4274 - Search for a platform-specific version of "ar" when cross-compiling.
4275 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
4278 Changes in version 0.2.3.3-alpha - 2011-09-01
4279 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
4280 security, and provides client-side support for the microdescriptor
4281 and optimistic data features introduced earlier in the 0.2.3.x
4282 series. It also includes numerous critical bugfixes in the (optional)
4283 bufferevent-based networking backend.
4285 o Major features (stream isolation):
4286 - You can now configure Tor so that streams from different
4287 applications are isolated on different circuits, to prevent an
4288 attacker who sees your streams as they leave an exit node from
4289 linking your sessions to one another. To do this, choose some way
4290 to distinguish the applications: have them connect to different
4291 SocksPorts, or have one of them use SOCKS4 while the other uses
4292 SOCKS5, or have them pass different authentication strings to the
4293 SOCKS proxy. Then, use the new SocksPort syntax to configure the
4294 degree of isolation you need. This implements Proposal 171.
4295 - There's a new syntax for specifying multiple client ports (such as
4296 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
4297 multiple *Port entries with full addr:port syntax on each.
4298 The old *ListenAddress format is still supported, but you can't
4299 mix it with the new *Port syntax.
4301 o Major features (other):
4302 - Enable microdescriptor fetching by default for clients. This allows
4303 clients to download a much smaller amount of directory information.
4304 To disable it (and go back to the old-style consensus and
4305 descriptors), set "UseMicrodescriptors 0" in your torrc file.
4306 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
4307 "PortForwarding" config option), now supports Windows.
4308 - When using an exit relay running 0.2.3.x, clients can now
4309 "optimistically" send data before the exit relay reports that
4310 the stream has opened. This saves a round trip when starting
4311 connections where the client speaks first (such as web browsing).
4312 This behavior is controlled by a consensus parameter (currently
4313 disabled). To turn it on or off manually, use the "OptimisticData"
4314 torrc option. Implements proposal 181; code by Ian Goldberg.
4316 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
4317 - When using IOCP on Windows, we need to enable Libevent windows
4319 - The IOCP backend now works even when the user has not specified
4320 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
4321 Fixes part of bug 3752.
4322 - Correctly record the bytes we've read and written when using
4323 bufferevents, so that we can include them in our bandwidth history
4324 and advertised bandwidth. Fixes bug 3803.
4325 - Apply rate-limiting only at the bottom of a chain of filtering
4326 bufferevents. This prevents us from filling up internal read
4327 buffers and violating rate-limits when filtering bufferevents
4328 are enabled. Fixes part of bug 3804.
4329 - Add high-watermarks to the output buffers for filtered
4330 bufferevents. This prevents us from filling up internal write
4331 buffers and wasting CPU cycles when filtering bufferevents are
4332 enabled. Fixes part of bug 3804.
4333 - Correctly notice when data has been written from a bufferevent
4334 without flushing it completely. Fixes bug 3805.
4335 - Fix a bug where server-side tunneled bufferevent-based directory
4336 streams would get closed prematurely. Fixes bug 3814.
4337 - Fix a use-after-free error with per-connection rate-limiting
4338 buckets. Fixes bug 3888.
4340 o Major bugfixes (also part of 0.2.2.31-rc):
4341 - If we're configured to write our ControlPorts to disk, only write
4342 them after switching UID and creating the data directory. This way,
4343 we don't fail when starting up with a nonexistent DataDirectory
4344 and a ControlPortWriteToFile setting based on that directory. Fixes
4345 bug 3747; bugfix on Tor 0.2.2.26-beta.
4348 - Added a new CONF_CHANGED event so that controllers can be notified
4349 of any configuration changes made by other controllers, or by the
4350 user. Implements ticket 1692.
4351 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
4352 leak when using bufferevents, and lets Libevent worry about how to
4353 best copy data out of a buffer.
4354 - Replace files in stats/ rather than appending to them. Now that we
4355 include statistics in extra-info descriptors, it makes no sense to
4356 keep old statistics forever. Implements ticket 2930.
4358 o Minor features (build compatibility):
4359 - Limited, experimental support for building with nmake and MSVC.
4360 - Provide a substitute implementation of lround() for MSVC, which
4361 apparently lacks it. Patch from Gisle Vanem.
4363 o Minor features (also part of 0.2.2.31-rc):
4364 - Update to the August 2 2011 Maxmind GeoLite Country database.
4366 o Minor bugfixes (on 0.2.3.x-alpha):
4367 - Fix a spurious warning when parsing SOCKS requests with
4368 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
4369 - Get rid of a harmless warning that could happen on relays running
4370 with bufferevents. The warning was caused by someone doing an http
4371 request to a relay's orport. Also don't warn for a few related
4372 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
4374 o Minor bugfixes (on 2.2.x and earlier):
4375 - Correct the man page to explain that HashedControlPassword and
4376 CookieAuthentication can both be set, in which case either method
4377 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
4378 when we decided to allow these config options to both be set. Issue
4380 - The "--quiet" and "--hush" options now apply not only to Tor's
4381 behavior before logs are configured, but also to Tor's behavior in
4382 the absense of configured logs. Fixes bug 3550; bugfix on
4385 o Minor bugfixes (also part of 0.2.2.31-rc):
4386 - Write several files in text mode, on OSes that distinguish text
4387 mode from binary mode (namely, Windows). These files are:
4388 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4389 that collect those statistics; 'client_keys' and 'hostname' for
4390 hidden services that use authentication; and (in the tor-gencert
4391 utility) newly generated identity and signing keys. Previously,
4392 we wouldn't specify text mode or binary mode, leading to an
4393 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4394 the DirRecordUsageByCountry option which would have triggered
4395 the assertion failure was added), although this assertion failure
4396 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4397 - Selectively disable deprecation warnings on OS X because Lion
4398 started deprecating the shipped copy of openssl. Fixes bug 3643.
4399 - Remove an extra pair of quotation marks around the error
4400 message in control-port STATUS_GENERAL BUG events. Bugfix on
4401 0.1.2.6-alpha; fixes bug 3732.
4402 - When unable to format an address as a string, report its value
4403 as "???" rather than reusing the last formatted address. Bugfix
4406 o Code simplifications and refactoring:
4407 - Rewrite the listener-selection logic so that parsing which ports
4408 we want to listen on is now separate from binding to the ports
4412 - Building Tor with bufferevent support now requires Libevent
4413 2.0.13-stable or later. Previous versions of Libevent had bugs in
4414 SSL-related bufferevents and related issues that would make Tor
4415 work badly with bufferevents. Requiring 2.0.13-stable also allows
4416 Tor with bufferevents to take advantage of Libevent APIs
4417 introduced after 2.0.8-rc.
4420 Changes in version 0.2.2.32 - 2011-08-27
4421 The Tor 0.2.2 release series is dedicated to the memory of Andreas
4422 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
4423 a founder of the PETS community, a leader in our field, a mentor,
4424 and a friend. He left us with these words: "I had the possibility
4425 to contribute to this world that is not as it should be. I hope I
4426 could help in some areas to make the world a better place, and that
4427 I could also encourage other people to be engaged in improving the
4428 world. Please, stay engaged. This world needs you, your love, your
4429 initiative -- now I cannot be part of that anymore."
4431 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
4432 ready. More than two years in the making, this release features improved
4433 client performance and hidden service reliability, better compatibility
4434 for Android, correct behavior for bridges that listen on more than
4435 one address, more extensible and flexible directory object handling,
4436 better reporting of network statistics, improved code security, and
4437 many many other features and bugfixes.
4440 Changes in version 0.2.2.31-rc - 2011-08-17
4441 Tor 0.2.2.31-rc is the second and hopefully final release candidate
4442 for the Tor 0.2.2.x series.
4445 - Remove an extra pair of quotation marks around the error
4446 message in control-port STATUS_GENERAL BUG events. Bugfix on
4447 0.1.2.6-alpha; fixes bug 3732.
4448 - If we're configured to write our ControlPorts to disk, only write
4449 them after switching UID and creating the data directory. This way,
4450 we don't fail when starting up with a nonexistent DataDirectory
4451 and a ControlPortWriteToFile setting based on that directory. Fixes
4452 bug 3747; bugfix on Tor 0.2.2.26-beta.
4455 - Update to the August 2 2011 Maxmind GeoLite Country database.
4458 - Allow GETINFO fingerprint to return a fingerprint even when
4459 we have not yet built a router descriptor. Fixes bug 3577;
4460 bugfix on 0.2.0.1-alpha.
4461 - Write several files in text mode, on OSes that distinguish text
4462 mode from binary mode (namely, Windows). These files are:
4463 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
4464 that collect those statistics; 'client_keys' and 'hostname' for
4465 hidden services that use authentication; and (in the tor-gencert
4466 utility) newly generated identity and signing keys. Previously,
4467 we wouldn't specify text mode or binary mode, leading to an
4468 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
4469 the DirRecordUsageByCountry option which would have triggered
4470 the assertion failure was added), although this assertion failure
4471 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
4472 - Selectively disable deprecation warnings on OS X because Lion
4473 started deprecating the shipped copy of openssl. Fixes bug 3643.
4474 - When unable to format an address as a string, report its value
4475 as "???" rather than reusing the last formatted address. Bugfix
4479 Changes in version 0.2.3.2-alpha - 2011-07-18
4480 Tor 0.2.3.2-alpha introduces two new experimental features:
4481 microdescriptors and pluggable transports. It also continues cleaning
4482 up a variety of recently introduced features.
4485 - Clients can now use microdescriptors instead of regular descriptors
4486 to build circuits. Microdescriptors are authority-generated
4487 summaries of regular descriptors' contents, designed to change
4488 very rarely (see proposal 158 for details). This feature is
4489 designed to save bandwidth, especially for clients on slow internet
4490 connections. It's off by default for now, since nearly no caches
4491 support it, but it will be on-by-default for clients in a future
4492 version. You can use the UseMicrodescriptors option to turn it on.
4493 - Tor clients using bridges can now be configured to use a separate
4494 'transport' proxy for each bridge. This approach helps to resist
4495 censorship by allowing bridges to use protocol obfuscation
4496 plugins. It implements part of proposal 180. Implements ticket 2841.
4497 - While we're trying to bootstrap, record how many TLS connections
4498 fail in each state, and report which states saw the most failures
4499 in response to any bootstrap failures. This feature may speed up
4500 diagnosis of censorship events. Implements ticket 3116.
4502 o Major bugfixes (on 0.2.3.1-alpha):
4503 - When configuring a large set of nodes in EntryNodes (as with
4504 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
4505 random subset to be guards, and choose them in random
4506 order. Fixes bug 2798.
4507 - Tor could crash when remembering a consensus in a non-used consensus
4508 flavor without having a current consensus set. Fixes bug 3361.
4509 - Comparing an unknown address to a microdescriptor's shortened exit
4510 policy would always give a "rejected" result. Fixes bug 3599.
4511 - Using microdescriptors as a client no longer prevents Tor from
4512 uploading and downloading hidden service descriptors. Fixes
4516 - Allow nameservers with IPv6 address. Resolves bug 2574.
4517 - Accept attempts to include a password authenticator in the
4518 handshake, as supported by SOCKS5. This handles SOCKS clients that
4519 don't know how to omit a password when authenticating. Resolves
4521 - When configuring a large set of nodes in EntryNodes, and there are
4522 enough of them listed as Guard so that we don't need to consider
4523 the non-guard entries, prefer the ones listed with the Guard flag.
4524 - Check for and recover from inconsistency in the microdescriptor
4525 cache. This will make it harder for us to accidentally free a
4526 microdescriptor without removing it from the appropriate data
4527 structures. Fixes issue 3135; issue noted by "wanoskarnet".
4528 - Log SSL state transitions at log level DEBUG, log domain
4529 HANDSHAKE. This can be useful for debugging censorship events.
4530 Implements ticket 3264.
4531 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
4532 implements ticket 3439.
4534 o Minor bugfixes (on 0.2.3.1-alpha):
4535 - Do not free all general-purpose regular descriptors just
4536 because microdescriptor use is enabled. Fixes bug 3113.
4537 - Correctly link libevent_openssl when --enable-static-libevent
4538 is passed to configure. Fixes bug 3118.
4539 - Bridges should not complain during their heartbeat log messages that
4540 they are unlisted in the consensus: that's more or less the point
4541 of being a bridge. Fixes bug 3183.
4542 - Report a SIGNAL event to controllers when acting on a delayed
4543 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
4544 event to the controller if we acted on a SIGNAL NEWNYM command
4545 immediately, and otherwise not report a SIGNAL event for the
4546 command at all. Fixes bug 3349.
4547 - Fix a crash when handling the SIGNAL controller command or
4548 reporting ERR-level status events with bufferevents enabled. Found
4549 by Robert Ransom. Fixes bug 3367.
4550 - Always ship the tor-fw-helper manpage in our release tarballs.
4551 Fixes bug 3389. Reported by Stephen Walker.
4552 - Fix a class of double-mark-for-close bugs when bufferevents
4553 are enabled. Fixes bug 3403.
4554 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
4555 - Add SIGNAL to the list returned by the 'GETINFO events/names'
4556 control-port command. Fixes part of bug 3465.
4557 - Prevent using negative indices during unit test runs when read_all()
4558 fails. Spotted by coverity.
4559 - Fix a rare memory leak when checking the nodelist without it being
4560 present. Found by coverity.
4561 - Only try to download a microdescriptor-flavored consensus from
4562 a directory cache that provides them.
4564 o Minor bugfixes (on 0.2.2.x and earlier):
4565 - Assert that hidden-service-related operations are not performed
4566 using single-hop circuits. Previously, Tor would assert that
4567 client-side streams are not attached to single-hop circuits,
4568 but not that other sensitive operations on the client and service
4569 side are not performed using single-hop circuits. Fixes bug 3332;
4571 - Don't publish a new relay descriptor when we reload our onion key,
4572 unless the onion key has actually changed. Fixes bug 3263 and
4573 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
4574 - Allow GETINFO fingerprint to return a fingerprint even when
4575 we have not yet built a router descriptor. Fixes bug 3577;
4576 bugfix on 0.2.0.1-alpha.
4577 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
4578 on 0.2.2.4-alpha; fixes bug 3427.
4580 o Code simplification and refactoring:
4581 - Use tor_sscanf() in place of scanf() in more places through the
4582 code. This makes us a little more locale-independent, and
4583 should help shut up code-analysis tools that can't tell
4584 a safe sscanf string from a dangerous one.
4585 - Use tt_assert(), not tor_assert(), for checking for test failures.
4586 This makes the unit tests more able to go on in the event that
4588 - Split connection_about_to_close() into separate functions for each
4592 - On Windows, we now define the _WIN32_WINNT macros only if they
4593 are not already defined. This lets the person building Tor decide,
4594 if they want, to require a later version of Windows.
4597 Changes in version 0.2.2.30-rc - 2011-07-07
4598 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
4599 series. It fixes a few smaller bugs, but generally appears stable.
4600 Please test it and let us know whether it is!
4603 - Send a SUCCEEDED stream event to the controller when a reverse
4604 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
4605 discovered by katmagic.
4606 - Always NUL-terminate the sun_path field of a sockaddr_un before
4607 passing it to the kernel. (Not a security issue: kernels are
4608 smart enough to reject bad sockaddr_uns.) Found by Coverity;
4609 CID #428. Bugfix on Tor 0.2.0.3-alpha.
4610 - Don't stack-allocate the list of supplementary GIDs when we're
4611 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
4612 could take up to 256K, which is way too much stack. Found by
4613 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
4614 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
4615 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
4616 fixes part of bug 3465.
4617 - Fix a memory leak when receiving a descriptor for a hidden
4618 service we didn't ask for. Found by Coverity; CID #30. Bugfix
4622 - Update to the July 1 2011 Maxmind GeoLite Country database.
4625 Changes in version 0.2.2.29-beta - 2011-06-20
4626 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
4627 have bridge lines in their torrc but don't want to use them; gets
4628 us closer to having the control socket feature working on Debian;
4629 and fixes a variety of smaller bugs.
4632 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
4633 When we changed the default behavior to "use bridges if any
4634 are listed in the torrc", we surprised users who had bridges
4635 in their torrc files but who didn't actually want to use them.
4636 Partial resolution for bug 3354.
4639 - Don't attach new streams to old rendezvous circuits after SIGNAL
4640 NEWNYM. Previously, we would keep using an existing rendezvous
4641 circuit if it remained open (i.e. if it were kept open by a
4642 long-lived stream, or if a new stream were attached to it before
4643 Tor could notice that it was old and no longer in use). Bugfix on
4644 0.1.1.15-rc; fixes bug 3375.
4647 - Fix a bug when using ControlSocketsGroupWritable with User. The
4648 directory's group would be checked against the current group, not
4649 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
4650 bugfix on 0.2.2.26-beta.
4651 - Make connection_printf_to_buf()'s behaviour sane. Its callers
4652 expect it to emit a CRLF iff the format string ends with CRLF;
4653 it actually emitted a CRLF iff (a) the format string ended with
4654 CRLF or (b) the resulting string was over 1023 characters long or
4655 (c) the format string did not end with CRLF *and* the resulting
4656 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
4657 fixes part of bug 3407.
4658 - Make send_control_event_impl()'s behaviour sane. Its callers
4659 expect it to always emit a CRLF at the end of the string; it
4660 might have emitted extra control characters as well. Bugfix on
4661 0.1.1.9-alpha; fixes another part of bug 3407.
4662 - Make crypto_rand_int() check the value of its input correctly.
4663 Previously, it accepted values up to UINT_MAX, but could return a
4664 negative number if given a value above INT_MAX+1. Found by George
4665 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
4666 - Avoid a segfault when reading a malformed circuit build state
4667 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
4669 - When asked about a DNS record type we don't support via a
4670 client DNSPort, reply with NOTIMPL rather than an empty
4671 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
4672 - Fix a rare memory leak during stats writing. Found by coverity.
4675 - Update to the June 1 2011 Maxmind GeoLite Country database.
4677 o Code simplifications and refactoring:
4678 - Remove some dead code as indicated by coverity.
4679 - Remove a few dead assignments during router parsing. Found by
4681 - Add some forgotten return value checks during unit tests. Found
4683 - Don't use 1-bit wide signed bit fields. Found by coverity.
4686 Changes in version 0.2.2.28-beta - 2011-06-04
4687 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
4688 fixed a big bug in whether relays stay in the consensus consistently,
4689 we moved closer to handling bridges and hidden services correctly,
4690 and we started the process of better handling the dreaded "my Vidalia
4691 died, and now my Tor demands a password when I try to reconnect to it"
4695 - Don't decide to make a new descriptor when receiving a HUP signal.
4696 This bug has caused a lot of 0.2.2.x relays to disappear from the
4697 consensus periodically. Fixes the most common case of triggering
4698 bug 1810; bugfix on 0.2.2.7-alpha.
4699 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
4700 - Don't try to build descriptors if "ORPort auto" is set and we
4701 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
4703 - Resolve a crash that occurred when setting BridgeRelay to 1 with
4704 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
4705 - Apply circuit timeouts to opened hidden-service-related circuits
4706 based on the correct start time. Previously, we would apply the
4707 circuit build timeout based on time since the circuit's creation;
4708 it was supposed to be applied based on time since the circuit
4709 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
4710 - Use the same circuit timeout for client-side introduction
4711 circuits as for other four-hop circuits, rather than the timeout
4712 for single-hop directory-fetch circuits; the shorter timeout may
4713 have been appropriate with the static circuit build timeout in
4714 0.2.1.x and earlier, but caused many hidden service access attempts
4715 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
4716 on 0.2.2.2-alpha; fixes another part of bug 1297.
4717 - In ticket 2511 we fixed a case where you could use an unconfigured
4718 bridge if you had configured it as a bridge the last time you ran
4719 Tor. Now fix another edge case: if you had configured it as a bridge
4720 but then switched to a different bridge via the controller, you
4721 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
4725 - Add an __OwningControllerProcess configuration option and a
4726 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
4727 that when it exits, Tor will shut down. Implements feature 3049.
4728 - If "UseBridges 1" is set and no bridges are configured, Tor will
4729 now refuse to build any circuits until some bridges are set.
4730 If "UseBridges auto" is set, Tor will use bridges if they are
4731 configured and we are not running as a server, but otherwise will
4732 make circuits as usual. The new default is "auto". Patch by anonym,
4733 so the Tails LiveCD can stop automatically revealing you as a Tor
4737 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
4738 - Remove a trailing asterisk from "exit-policy/default" in the
4739 output of the control port command "GETINFO info/names". Bugfix
4741 - Use a wide type to hold sockets when built for 64-bit Windows builds.
4743 - Warn when the user configures two HiddenServiceDir lines that point
4744 to the same directory. Bugfix on 0.0.6 (the version introducing
4745 HiddenServiceDir); fixes bug 3289.
4746 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
4747 part of bug 2748; bugfix on 0.2.0.10-alpha.
4748 - Log malformed requests for rendezvous descriptors as protocol
4749 warnings, not warnings. Also, use a more informative log message
4750 in case someone sees it at log level warning without prior
4751 info-level messages. Fixes the other part of bug 2748; bugfix
4753 - Clear the table recording the time of the last request for each
4754 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
4755 Previously, we would clear our HS descriptor cache on SIGNAL
4756 NEWNYM, but if we had previously retrieved a descriptor (or tried
4757 to) from every directory responsible for it, we would refuse to
4758 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
4760 - Fix a log message that said "bits" while displaying a value in
4761 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
4763 - When checking for 1024-bit keys, check for 1024 bits, not 128
4764 bytes. This allows Tor to correctly discard keys of length 1017
4765 through 1023. Bugfix on 0.0.9pre5.
4768 - Relays now log the reason for publishing a new relay descriptor,
4769 so we have a better chance of hunting down instances of bug 1810.
4770 Resolves ticket 3252.
4771 - Revise most log messages that refer to nodes by nickname to
4772 instead use the "$key=nickname at address" format. This should be
4773 more useful, especially since nicknames are less and less likely
4774 to be unique. Resolves ticket 3045.
4775 - Log (at info level) when purging pieces of hidden-service-client
4776 state because of SIGNAL NEWNYM.
4779 - Remove undocumented option "-F" from tor-resolve: it hasn't done
4780 anything since 0.2.1.16-rc.
4783 Changes in version 0.2.2.27-beta - 2011-05-18
4784 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
4785 release, and also adds a few more general bugfixes.
4788 - Fix a crash bug when changing bridges in a running Tor process.
4789 Fixes bug 3213; bugfix on 0.2.2.26-beta.
4790 - When the controller configures a new bridge, don't wait 10 to 60
4791 seconds before trying to fetch its descriptor. Bugfix on
4792 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
4795 - Require that onion keys have exponent 65537 in microdescriptors too.
4796 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
4797 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
4798 Changed the limit to 512 characters by removing base64 newlines.
4799 Fixes bug 2752. Fix by Michael Yakubovich.
4800 - When a client starts or stops using bridges, never use a circuit
4801 that was built before the configuration change. This behavior could
4802 put at risk a user who uses bridges to ensure that her traffic
4803 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
4807 Changes in version 0.2.2.26-beta - 2011-05-17
4808 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
4809 also introduces a new "socksport auto" approach that should make it
4810 easier to run multiple Tors on the same system, and does a lot of
4811 cleanup to get us closer to a release candidate.
4813 o Security/privacy fixes:
4814 - Replace all potentially sensitive memory comparison operations
4815 with versions whose runtime does not depend on the data being
4816 compared. This will help resist a class of attacks where an
4817 adversary can use variations in timing information to learn
4818 sensitive data. Fix for one case of bug 3122. (Safe memcmp
4819 implementation by Robert Ransom based partially on code by DJB.)
4820 - When receiving a hidden service descriptor, check that it is for
4821 the hidden service we wanted. Previously, Tor would store any
4822 hidden service descriptors that a directory gave it, whether it
4823 wanted them or not. This wouldn't have let an attacker impersonate
4824 a hidden service, but it did let directories pre-seed a client
4825 with descriptors that it didn't want. Bugfix on 0.0.6.
4826 - On SIGHUP, do not clear out all TrackHostExits mappings, client
4827 DNS cache entries, and virtual address mappings: that's what
4828 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
4831 - The options SocksPort, ControlPort, and so on now all accept a
4832 value "auto" that opens a socket on an OS-selected port. A
4833 new ControlPortWriteToFile option tells Tor to write its
4834 actual control port or ports to a chosen file. If the option
4835 ControlPortFileGroupReadable is set, the file is created as
4836 group-readable. Now users can run two Tor clients on the same
4837 system without needing to manually mess with parameters. Resolves
4838 part of ticket 3076.
4839 - Set SO_REUSEADDR on all sockets, not just listeners. This should
4840 help busy exit nodes avoid running out of useable ports just
4841 because all the ports have been used in the near past. Resolves
4845 - New "GETINFO net/listeners/(type)" controller command to return
4846 a list of addresses and ports that are bound for listeners for a
4847 given connection type. This is useful when the user has configured
4848 "SocksPort auto" and the controller needs to know which port got
4849 chosen. Resolves another part of ticket 3076.
4850 - Add a new ControlSocketsGroupWritable configuration option: when
4851 it is turned on, ControlSockets are group-writeable by the default
4852 group of the current user. Patch by Jérémy Bobbio; implements
4854 - Tor now refuses to create a ControlSocket in a directory that is
4855 world-readable (or group-readable if ControlSocketsGroupWritable
4856 is 0). This is necessary because some operating systems do not
4857 enforce permissions on an AF_UNIX sockets. Permissions on the
4858 directory holding the socket, however, seems to work everywhere.
4859 - Rate-limit a warning about failures to download v2 networkstatus
4860 documents. Resolves part of bug 1352.
4861 - Backport code from 0.2.3.x that allows directory authorities to
4862 clean their microdescriptor caches. Needed to resolve bug 2230.
4863 - When an HTTPS proxy reports "403 Forbidden", we now explain
4864 what it means rather than calling it an unexpected status code.
4865 Closes bug 2503. Patch from Michael Yakubovich.
4866 - Update to the May 1 2011 Maxmind GeoLite Country database.
4869 - Authorities now clean their microdesc cache periodically and when
4870 reading from disk initially, not only when adding new descriptors.
4871 This prevents a bug where we could lose microdescriptors. Bugfix
4872 on 0.2.2.6-alpha. Fixes bug 2230.
4873 - Do not crash when our configuration file becomes unreadable, for
4874 example due to a permissions change, between when we start up
4875 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
4877 - Avoid a bug that would keep us from replacing a microdescriptor
4878 cache on Windows. (We would try to replace the file while still
4879 holding it open. That's fine on Unix, but Windows doesn't let us
4880 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
4881 - Add missing explanations for the authority-related torrc options
4882 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
4883 man page. Resolves issue 2379.
4884 - As an authority, do not upload our own vote or signature set to
4885 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
4886 it would get flagged as a duplicate. Resolves bug 3026.
4887 - Accept hidden service descriptors if we think we might be a hidden
4888 service directory, regardless of what our consensus says. This
4889 helps robustness, since clients and hidden services can sometimes
4890 have a more up-to-date view of the network consensus than we do,
4891 and if they think that the directory authorities list us a HSDir,
4892 we might actually be one. Related to bug 2732; bugfix on
4894 - When a controller changes TrackHostExits, remove mappings for
4895 hosts that should no longer have their exits tracked. Bugfix on
4897 - When a controller changes VirtualAddrNetwork, remove any mappings
4898 for hosts that were automapped to the old network. Bugfix on
4900 - When a controller changes one of the AutomapHosts* options, remove
4901 any mappings for hosts that should no longer be automapped. Bugfix
4903 - Do not reset the bridge descriptor download status every time we
4904 re-parse our configuration or get a configuration change. Fixes
4905 bug 3019; bugfix on 0.2.0.3-alpha.
4907 o Minor bugfixes (code cleanup):
4908 - When loading the microdesc journal, remember its current size.
4909 In 0.2.2, this helps prevent the microdesc journal from growing
4910 without limit on authorities (who are the only ones to use it in
4911 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
4912 Fix posted by "cypherpunks."
4913 - The microdesc journal is supposed to get rebuilt only if it is
4914 at least _half_ the length of the store, not _twice_ the length
4915 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
4916 - Fix a potential null-pointer dereference while computing a
4917 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
4919 - Avoid a possible null-pointer dereference when rebuilding the mdesc
4920 cache without actually having any descriptors to cache. Bugfix on
4921 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
4922 - If we fail to compute the identity digest of a v3 legacy keypair,
4923 warn, and don't use a buffer-full of junk instead. Bugfix on
4924 0.2.1.1-alpha; fixes bug 3106.
4925 - Resolve an untriggerable issue in smartlist_string_num_isin(),
4926 where if the function had ever in the future been used to check
4927 for the presence of a too-large number, it would have given an
4928 incorrect result. (Fortunately, we only used it for 16-bit
4929 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
4930 - Require that introduction point keys and onion handshake keys
4931 have a public exponent of 65537. Starts to fix bug 3207; bugfix
4935 - Caches no longer download and serve v2 networkstatus documents
4936 unless FetchV2Networkstatus flag is set: these documents haven't
4937 haven't been used by clients or relays since 0.2.0.x. Resolves
4941 Changes in version 0.2.3.1-alpha - 2011-05-05
4942 Tor 0.2.3.1-alpha adds some new experimental features, including support
4943 for an improved network IO backend, IOCP networking on Windows,
4944 microdescriptor caching, "fast-start" support for streams, and automatic
4945 home router configuration. There are also numerous internal improvements
4946 to try to make the code easier for developers to work with.
4948 This is the first alpha release in a new series, so expect there to be
4949 bugs. Users who would rather test out a more stable branch should
4950 stay with 0.2.2.x for now.
4953 - Tor can now optionally build with the "bufferevents" buffered IO
4954 backend provided by Libevent 2. To use this feature, make sure you
4955 have the latest possible version of Libevent, and pass the
4956 --enable-bufferevents flag to configure when building Tor from
4957 source. This feature will make our networking code more flexible,
4958 let us stack layers on each other, and let us use more efficient
4959 zero-copy transports where available.
4960 - As an experimental feature, Tor can use IOCP for networking on Windows.
4961 Once this code is tuned and optimized, it promises much better
4962 performance than the select-based backend we've used in the past. To
4963 try this feature, you must build Tor with Libevent 2, configure Tor
4964 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
4965 your torrc. There are known bugs here: only try this if you can help
4966 debug it as it breaks.
4967 - The EntryNodes option can now include country codes like {de} or IP
4968 addresses or network masks. Previously we had disallowed these options
4969 because we didn't have an efficient way to keep the list up to
4970 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
4971 - Exit nodes now accept and queue data on not-yet-connected streams.
4972 Previously, the client wasn't allowed to send data until the stream was
4973 connected, which slowed down all connections. This change will enable
4974 clients to perform a "fast-start" on streams and send data without
4975 having to wait for a confirmation that the stream has opened. (Patch
4976 from Ian Goldberg; implements the server side of Proposal 174.)
4977 - Tor now has initial support for automatic port mapping on the many
4978 home routers that support NAT-PMP or UPnP. (Not yet supported on
4979 Windows). To build the support code, you'll need to have libnatpnp
4980 library and/or the libminiupnpc library, and you'll need to enable the
4981 feature specifically by passing "--enable-upnp" and/or
4982 "--enable-natpnp" to configure. To turn it on, use the new
4983 PortForwarding option.
4984 - Caches now download, cache, and serve multiple "flavors" of the
4985 consensus, including a flavor that describes microdescriptors.
4986 - Caches now download, cache, and serve microdescriptors -- small
4987 summaries of router descriptors that are authenticated by all of the
4988 directory authorities. Once enough caches are running this code,
4989 clients will be able to save significant amounts of directory bandwidth
4990 by downloading microdescriptors instead of router descriptors.
4993 - Make logging resolution configurable with a new LogTimeGranularity
4994 option, and change the default from 1 millisecond to 1 second.
4995 Implements enhancement 1668.
4996 - We log which torrc file we're using on startup. Implements ticket
4998 - Ordinarily, Tor does not count traffic from private addresses (like
4999 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
5000 There is now a new option, CountPrivateBandwidth, to disable this
5001 behavior. Patch from Daniel Cagara.
5002 - New --enable-static-tor configure option for building Tor as
5003 statically as possible. Idea, general hackery and thoughts from
5004 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
5006 - If you set the NumCPUs option to 0, Tor will now try to detect how
5007 many CPUs you have. This is the new default behavior.
5008 - Turn on directory request statistics by default and include them in
5009 extra-info descriptors. Don't break if we have no GeoIP database.
5010 - Relays that set "ConnDirectionStatistics 1" write statistics on the
5011 bidirectional use of connections to disk every 24 hours.
5012 - Add a GeoIP file digest to the extra-info descriptor. Implements
5014 - The NodeFamily option -- which let you declare that you want to
5015 consider nodes to be part of a family whether they list themselves
5016 that way or not -- now allows IP address ranges and country codes.
5017 - Add a new 'Heartbeat' log message type to periodically log a message
5018 describing Tor's status at level Notice. This feature is meant for
5019 operators who log at notice, and want to make sure that their Tor
5020 server is still working. Implementation by George Kadianakis.
5022 o Minor bugfixes (on 0.2.2.25-alpha):
5023 - When loading the microdesc journal, remember its current size.
5024 In 0.2.2, this helps prevent the microdesc journal from growing
5025 without limit on authorities (who are the only ones to use it in
5026 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
5027 Fix posted by "cypherpunks."
5028 - The microdesc journal is supposed to get rebuilt only if it is
5029 at least _half_ the length of the store, not _twice_ the length
5030 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
5031 - If as an authority we fail to compute the identity digest of a v3
5032 legacy keypair, warn, and don't use a buffer-full of junk instead.
5033 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
5034 - Authorities now clean their microdesc cache periodically and when
5035 reading from disk initially, not only when adding new descriptors.
5036 This prevents a bug where we could lose microdescriptors. Bugfix
5039 o Minor features (controller):
5040 - Add a new SIGNAL event to the controller interface so that
5041 controllers can be notified when Tor handles a signal. Resolves
5042 issue 1955. Patch by John Brooks.
5043 - Add a new GETINFO option to get total bytes read and written. Patch
5044 from pipe, revised by atagar. Resolves ticket 2345.
5045 - Implement some GETINFO controller fields to provide information about
5046 the Tor process's pid, euid, username, and resource limits.
5049 - Our build system requires automake 1.6 or later to create the
5050 Makefile.in files. Previously, you could have used 1.4.
5051 This only affects developers and people building Tor from git;
5052 people who build Tor from the source distribution without changing
5053 the Makefile.am files should be fine.
5054 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
5055 so on. This is more robust against some of the failure modes
5056 associated with running the autotools pieces on their own.
5058 o Minor packaging issues:
5059 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
5060 already created. Patch from Andreas Stieger. Fixes bug 2573.
5062 o Code simplifications and refactoring:
5063 - A major revision to our internal node-selecting and listing logic.
5064 Tor already had at least two major ways to look at the question of
5065 "which Tor servers do we know about": a list of router descriptors,
5066 and a list of entries in the current consensus. With
5067 microdescriptors, we're adding a third. Having so many systems
5068 without an abstraction layer over them was hurting the codebase.
5069 Now, we have a new "node_t" abstraction that presents a consistent
5070 interface to a client's view of a Tor node, and holds (nearly) all
5071 of the mutable state formerly in routerinfo_t and routerstatus_t.
5072 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
5073 no longer link against Libevent: they never used it, but
5074 our library structure used to force them to link it.
5077 - Remove some old code to work around even older versions of Tor that
5078 used forked processes to handle DNS requests. Such versions of Tor
5079 are no longer in use as servers.
5081 o Documentation fixes:
5082 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
5083 - Add missing documentation for the authority-related torrc options
5084 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
5088 Changes in version 0.2.2.25-alpha - 2011-04-29
5089 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
5090 robust, routers no longer overreport their bandwidth, Win7 should crash
5091 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
5092 now prevents hidden service-related activity from being linkable. It
5093 provides more information to Vidalia so you can see if your bridge is
5094 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
5095 StrictNodes configuration options to make them more reliable, more
5096 understandable, and more regularly applied. If you use those options,
5097 please see the revised documentation for them in the manual page.
5100 - Relays were publishing grossly inflated bandwidth values because
5101 they were writing their state files wrong--now they write the
5102 correct value. Also, resume reading bandwidth history from the
5103 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
5104 - Improve hidden service robustness: When we find that we have
5105 extended a hidden service's introduction circuit to a relay not
5106 listed as an introduction point in the HS descriptor we currently
5107 have, retry with an introduction point from the current
5108 descriptor. Previously we would just give up. Fixes bugs 1024 and
5109 1930; bugfix on 0.2.0.10-alpha.
5110 - Clients now stop trying to use an exit node associated with a given
5111 destination by TrackHostExits if they fail to reach that exit node.
5112 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
5113 - Fix crash bug on platforms where gmtime and localtime can return
5114 NULL. Windows 7 users were running into this one. Fixes part of bug
5115 2077. Bugfix on all versions of Tor. Found by boboper.
5117 o Security and stability fixes:
5118 - Don't double-free a parsable, but invalid, microdescriptor, even if
5119 it is followed in the blob we're parsing by an unparsable
5120 microdescriptor. Fixes an issue reported in a comment on bug 2954.
5121 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
5122 - If the Nickname configuration option isn't given, Tor would pick a
5123 nickname based on the local hostname as the nickname for a relay.
5124 Because nicknames are not very important in today's Tor and the
5125 "Unnamed" nickname has been implemented, this is now problematic
5126 behavior: It leaks information about the hostname without being
5127 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
5128 introduced the Unnamed nickname. Reported by tagnaq.
5129 - Fix an uncommon assertion failure when running with DNSPort under
5130 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
5131 - Avoid linkability based on cached hidden service descriptors: forget
5132 all hidden service descriptors cached as a client when processing a
5133 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
5136 - Export GeoIP information on bridge usage to controllers even if we
5137 have not yet been running for 24 hours. Now Vidalia bridge operators
5138 can get more accurate and immediate feedback about their
5139 contributions to the network.
5141 o Major features and bugfixes (node selection):
5142 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
5143 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
5144 options. Previously, we had been ambiguous in describing what
5145 counted as an "exit" node, and what operations exactly "StrictNodes
5146 0" would permit. This created confusion when people saw nodes built
5147 through unexpected circuits, and made it hard to tell real bugs from
5148 surprises. Now the intended behavior is:
5149 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
5150 a node that delivers user traffic outside the Tor network.
5151 . "Entry", in the context of EntryNodes, means a node used as the
5152 first hop of a multihop circuit. It doesn't include direct
5153 connections to directory servers.
5154 . "ExcludeNodes" applies to all nodes.
5155 . "StrictNodes" changes the behavior of ExcludeNodes only. When
5156 StrictNodes is set, Tor should avoid all nodes listed in
5157 ExcludeNodes, even when it will make user requests fail. When
5158 StrictNodes is *not* set, then Tor should follow ExcludeNodes
5159 whenever it can, except when it must use an excluded node to
5160 perform self-tests, connect to a hidden service, provide a
5161 hidden service, fulfill a .exit request, upload directory
5162 information, or fetch directory information.
5163 Collectively, the changes to implement the behavior fix bug 1090.
5164 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
5165 a node is listed in both, it's treated as excluded.
5166 - ExcludeNodes now applies to directory nodes -- as a preference if
5167 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
5168 Don't exclude all the directory authorities and set StrictNodes to 1
5169 unless you really want your Tor to break.
5170 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
5171 - ExcludeExitNodes now overrides .exit requests.
5172 - We don't use bridges listed in ExcludeNodes.
5173 - When StrictNodes is 1:
5174 . We now apply ExcludeNodes to hidden service introduction points
5175 and to rendezvous points selected by hidden service users. This
5176 can make your hidden service less reliable: use it with caution!
5177 . If we have used ExcludeNodes on ourself, do not try relay
5178 reachability self-tests.
5179 . If we have excluded all the directory authorities, we will not
5180 even try to upload our descriptor if we're a relay.
5181 . Do not honor .exit requests to an excluded node.
5182 - Remove a misfeature that caused us to ignore the Fast/Stable flags
5183 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
5184 - When the set of permitted nodes changes, we now remove any mappings
5185 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
5187 - We never cannibalize a circuit that had excluded nodes on it, even
5188 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
5189 - Revert a change where we would be laxer about attaching streams to
5190 circuits than when building the circuits. This was meant to prevent
5191 a set of bugs where streams were never attachable, but our improved
5192 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
5193 - Keep track of how many times we launch a new circuit to handle a
5194 given stream. Too many launches could indicate an inconsistency
5195 between our "launch a circuit to handle this stream" logic and our
5196 "attach this stream to one of the available circuits" logic.
5197 - Improve log messages related to excluded nodes.
5200 - Fix a spurious warning when moving from a short month to a long
5201 month on relays with month-based BandwidthAccounting. Bugfix on
5202 0.2.2.17-alpha; fixes bug 3020.
5203 - When a client finds that an origin circuit has run out of 16-bit
5204 stream IDs, we now mark it as unusable for new streams. Previously,
5205 we would try to close the entire circuit. Bugfix on 0.0.6.
5206 - Add a forgotten cast that caused a compile warning on OS X 10.6.
5207 Bugfix on 0.2.2.24-alpha.
5208 - Be more careful about reporting the correct error from a failed
5209 connect() system call. Under some circumstances, it was possible to
5210 look at an incorrect value for errno when sending the end reason.
5211 Bugfix on 0.1.0.1-rc.
5212 - Correctly handle an "impossible" overflow cases in connection byte
5213 counting, where we write or read more than 4GB on an edge connection
5214 in a single second. Bugfix on 0.1.2.8-beta.
5215 - Correct the warning displayed when a rendezvous descriptor exceeds
5216 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
5218 - Clients and hidden services now use HSDir-flagged relays for hidden
5219 service descriptor downloads and uploads even if the relays have no
5220 DirPort set and the client has disabled TunnelDirConns. This will
5221 eventually allow us to give the HSDir flag to relays with no
5222 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
5223 - Downgrade "no current certificates known for authority" message from
5224 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
5225 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
5226 2917. Bugfix on 0.1.1.1-alpha.
5227 - Only limit the lengths of single HS descriptors, even when multiple
5228 HS descriptors are published to an HSDir relay in a single POST
5229 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
5230 - Write the current time into the LastWritten line in our state file,
5231 rather than the time from the previous write attempt. Also, stop
5232 trying to use a time of -1 in our log statements. Fixes bug 3039;
5233 bugfix on 0.2.2.14-alpha.
5234 - Be more consistent in our treatment of file system paths. "~" should
5235 get expanded to the user's home directory in the Log config option.
5236 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
5237 feature for the -f and --DataDirectory options.
5240 - Make sure every relay writes a state file at least every 12 hours.
5241 Previously, a relay could go for weeks without writing its state
5242 file, and on a crash could lose its bandwidth history, capacity
5243 estimates, client country statistics, and so on. Addresses bug 3012.
5244 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
5245 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
5246 clients are already deprecated because of security bugs.
5247 - Don't allow v0 hidden service authorities to act as clients.
5248 Required by fix for bug 3000.
5249 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
5250 by fix for bug 3000.
5251 - Ensure that no empty [dirreq-](read|write)-history lines are added
5252 to an extrainfo document. Implements ticket 2497.
5254 o Code simplification and refactoring:
5255 - Remove workaround code to handle directory responses from servers
5256 that had bug 539 (they would send HTTP status 503 responses _and_
5257 send a body too). Since only server versions before
5258 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
5259 keep the workaround in place.
5260 - Remove the old 'fuzzy time' logic. It was supposed to be used for
5261 handling calculations where we have a known amount of clock skew and
5262 an allowed amount of unknown skew. But we only used it in three
5263 places, and we never adjusted the known/unknown skew values. This is
5264 still something we might want to do someday, but if we do, we'll
5265 want to do it differently.
5266 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5267 None of the cases where we did this before were wrong, but by making
5268 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5269 - Use GetTempDir to find the proper temporary directory location on
5270 Windows when generating temporary files for the unit tests. Patch by
5274 Changes in version 0.2.2.24-alpha - 2011-04-08
5275 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
5276 prevented Tor clients from effectively using "multihomed" bridges,
5277 that is, bridges that listen on multiple ports or IP addresses so users
5278 can continue to use some of their addresses even if others get blocked.
5281 - Fix a bug where bridge users who configure the non-canonical
5282 address of a bridge automatically switch to its canonical
5283 address. If a bridge listens at more than one address, it should be
5284 able to advertise those addresses independently and any non-blocked
5285 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
5287 - If you configured Tor to use bridge A, and then quit and
5288 configured Tor to use bridge B instead, it would happily continue
5289 to use bridge A if it's still reachable. While this behavior is
5290 a feature if your goal is connectivity, in some scenarios it's a
5291 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
5292 - Directory authorities now use data collected from their own
5293 uptime observations when choosing whether to assign the HSDir flag
5294 to relays, instead of trusting the uptime value the relay reports in
5295 its descriptor. This change helps prevent an attack where a small
5296 set of nodes with frequently-changing identity keys can blackhole
5297 a hidden service. (Only authorities need upgrade; others will be
5298 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
5301 - When we restart our relay, we might get a successful connection
5302 from the outside before we've started our reachability tests,
5303 triggering a warning: "ORPort found reachable, but I have no
5304 routerinfo yet. Failing to inform controller of success." This
5305 bug was harmless unless Tor is running under a controller
5306 like Vidalia, in which case the controller would never get a
5307 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
5309 - Make directory authorities more accurate at recording when
5310 relays that have failed several reachability tests became
5311 unreachable, so we can provide more accuracy at assigning Stable,
5312 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
5313 - Fix an issue that prevented static linking of libevent on
5314 some platforms (notably Linux). Fixes bug 2698; bugfix on
5315 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
5316 the --with-static-libevent configure option).
5317 - We now ask the other side of a stream (the client or the exit)
5318 for more data on that stream when the amount of queued data on
5319 that stream dips low enough. Previously, we wouldn't ask the
5320 other side for more data until either it sent us more data (which
5321 it wasn't supposed to do if it had exhausted its window!) or we
5322 had completely flushed all our queued data. This flow control fix
5323 should improve throughput. Fixes bug 2756; bugfix on the earliest
5324 released versions of Tor (svn commit r152).
5325 - Avoid a double-mark-for-free warning when failing to attach a
5326 transparent proxy connection. (We thought we had fixed this in
5327 0.2.2.23-alpha, but it turns out our fix was checking the wrong
5328 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
5329 bug) and 0.2.2.23-alpha (the incorrect fix).
5330 - When warning about missing zlib development packages during compile,
5331 give the correct package names. Bugfix on 0.2.0.1-alpha.
5334 - Directory authorities now log the source of a rejected POSTed v3
5336 - Make compilation with clang possible when using
5337 --enable-gcc-warnings by removing two warning options that clang
5338 hasn't implemented yet and by fixing a few warnings. Implements
5340 - When expiring circuits, use microsecond timers rather than
5341 one-second timers. This can avoid an unpleasant situation where a
5342 circuit is launched near the end of one second and expired right
5343 near the beginning of the next, and prevent fluctuations in circuit
5345 - Use computed circuit-build timeouts to decide when to launch
5346 parallel introduction circuits for hidden services. (Previously,
5347 we would retry after 15 seconds.)
5348 - Update to the April 1 2011 Maxmind GeoLite Country database.
5351 - Create the /var/run/tor directory on startup on OpenSUSE if it is
5352 not already created. Patch from Andreas Stieger. Fixes bug 2573.
5354 o Documentation changes:
5355 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
5356 - Resolve all doxygen warnings except those for missing documentation.
5358 - Add doxygen documentation for more functions, fields, and types.
5361 Changes in version 0.2.2.23-alpha - 2011-03-08
5362 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
5363 they restart they don't lose their bandwidth capacity estimate. This
5364 release also fixes a diverse set of user-facing bugs, ranging from
5365 relays overrunning their rate limiting to clients falsely warning about
5366 clock skew to bridge descriptor leaks by our bridge directory authority.
5369 - Stop sending a CLOCK_SKEW controller status event whenever
5370 we fetch directory information from a relay that has a wrong clock.
5371 Instead, only inform the controller when it's a trusted authority
5372 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5373 the rest of bug 1074.
5374 - Fix an assert in parsing router descriptors containing IPv6
5375 addresses. This one took down the directory authorities when
5376 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
5377 - Make the bridge directory authority refuse to answer directory
5378 requests for "all" descriptors. It used to include bridge
5379 descriptors in its answer, which was a major information leak.
5380 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
5381 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5382 Tor would ignore their RelayBandwidthBurst setting,
5383 potentially using more bandwidth than expected. Bugfix on
5384 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5385 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5386 hidserv" in her torrc. The 'hidserv' argument never controlled
5387 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5390 - Relays now save observed peak bandwidth throughput rates to their
5391 state file (along with total usage, which was already saved)
5392 so that they can determine their correct estimated bandwidth on
5393 restart. Resolves bug 1863, where Tor relays would reset their
5394 estimated bandwidth to 0 after restarting.
5395 - Directory authorities now take changes in router IP address and
5396 ORPort into account when determining router stability. Previously,
5397 if a router changed its IP or ORPort, the authorities would not
5398 treat it as having any downtime for the purposes of stability
5399 calculation, whereas clients would experience downtime since the
5400 change could take a while to propagate to them. Resolves issue 1035.
5401 - Enable Address Space Layout Randomization (ASLR) and Data Execution
5402 Prevention (DEP) by default on Windows to make it harder for
5403 attackers to exploit vulnerabilities. Patch from John Brooks.
5405 o Minor bugfixes (on 0.2.1.x and earlier):
5406 - Fix a rare crash bug that could occur when a client was configured
5407 with a large number of bridges. Fixes bug 2629; bugfix on
5408 0.2.1.2-alpha. Bugfix by trac user "shitlei".
5409 - Avoid a double mark-for-free warning when failing to attach a
5410 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
5412 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
5413 found by "cypherpunks". This bug was introduced before the first
5414 Tor release, in svn commit r110.
5415 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
5416 don't mention them in the manpage. Fixes bug 2450; issue
5417 spotted by keb and G-Lo.
5418 - Fix a bug in bandwidth history state parsing that could have been
5419 triggered if a future version of Tor ever changed the timing
5420 granularity at which bandwidth history is measured. Bugfix on
5422 - When a relay decides that its DNS is too broken for it to serve
5423 as an exit server, it advertised itself as a non-exit, but
5424 continued to act as an exit. This could create accidental
5425 partitioning opportunities for users. Instead, if a relay is
5426 going to advertise reject *:* as its exit policy, it should
5427 really act with exit policy "reject *:*". Fixes bug 2366.
5428 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
5429 - In the special case where you configure a public exit relay as your
5430 bridge, Tor would be willing to use that exit relay as the last
5431 hop in your circuit as well. Now we fail that circuit instead.
5432 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
5433 - Fix a bug with our locking implementation on Windows that couldn't
5434 correctly detect when a file was already locked. Fixes bug 2504,
5435 bugfix on 0.2.1.6-alpha.
5436 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
5437 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
5439 - Set target port in get_interface_address6() correctly. Bugfix
5440 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
5441 - Directory authorities are now more robust to hops back in time
5442 when calculating router stability. Previously, if a run of uptime
5443 or downtime appeared to be negative, the calculation could give
5444 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
5446 - Fix an assert that got triggered when using the TestingTorNetwork
5447 configuration option and then issuing a GETINFO config-text control
5448 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
5450 o Minor bugfixes (on 0.2.2.x):
5451 - Clients should not weight BadExit nodes as Exits in their node
5452 selection. Similarly, directory authorities should not count BadExit
5453 bandwidth as Exit bandwidth when computing bandwidth-weights.
5454 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
5455 - Correctly clear our dir_read/dir_write history when there is an
5456 error parsing any bw history value from the state file. Bugfix on
5458 - Resolve a bug in verifying signatures of directory objects
5459 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
5460 Fixes bug 2409. Found by "piebeer".
5461 - Bridge authorities no longer crash on SIGHUP when they try to
5462 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
5466 - Log less aggressively about circuit timeout changes, and improve
5467 some other circuit timeout messages. Resolves bug 2004.
5468 - Log a little more clearly about the times at which we're no longer
5469 accepting new connections. Resolves bug 2181.
5470 - Reject attempts at the client side to open connections to private
5471 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
5472 a randomly chosen exit node. Attempts to do so are always
5473 ill-defined, generally prevented by exit policies, and usually
5474 in error. This will also help to detect loops in transparent
5475 proxy configurations. You can disable this feature by setting
5476 "ClientRejectInternalAddresses 0" in your torrc.
5477 - Always treat failure to allocate an RSA key as an unrecoverable
5479 - Update to the March 1 2011 Maxmind GeoLite Country database.
5481 o Minor features (log subsystem):
5482 - Add documentation for configuring logging at different severities in
5483 different log domains. We've had this feature since 0.2.1.1-alpha,
5484 but for some reason it never made it into the manpage. Fixes
5486 - Make it simpler to specify "All log domains except for A and B".
5487 Previously you needed to say "[*,~A,~B]". Now you can just say
5489 - Add a "LogMessageDomains 1" option to include the domains of log
5490 messages along with the messages. Without this, there's no way
5491 to use log domains without reading the source or doing a lot
5494 o Packaging changes:
5495 - Stop shipping the Tor specs files and development proposal documents
5496 in the tarball. They are now in a separate git repository at
5497 git://git.torproject.org/torspec.git
5500 Changes in version 0.2.1.30 - 2011-02-23
5501 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
5502 change is a slight tweak to Tor's TLS handshake that makes relays
5503 and bridges that run this new version reachable from Iran again.
5504 We don't expect this tweak will win the arms race long-term, but it
5505 buys us time until we roll out a better solution.
5508 - Stop sending a CLOCK_SKEW controller status event whenever
5509 we fetch directory information from a relay that has a wrong clock.
5510 Instead, only inform the controller when it's a trusted authority
5511 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
5512 the rest of bug 1074.
5513 - Fix a bounds-checking error that could allow an attacker to
5514 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5516 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
5517 Tor would ignore their RelayBandwidthBurst setting,
5518 potentially using more bandwidth than expected. Bugfix on
5519 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
5520 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
5521 hidserv" in her torrc. The 'hidserv' argument never controlled
5522 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
5525 - Adjust our TLS Diffie-Hellman parameters to match those used by
5527 - Update to the February 1 2011 Maxmind GeoLite Country database.
5530 - Check for and reject overly long directory certificates and
5531 directory tokens before they have a chance to hit any assertions.
5532 Bugfix on 0.2.1.28. Found by "doorss".
5533 - Bring the logic that gathers routerinfos and assesses the
5534 acceptability of circuits into line. This prevents a Tor OP from
5535 getting locked in a cycle of choosing its local OR as an exit for a
5536 path (due to a .exit request) and then rejecting the circuit because
5537 its OR is not listed yet. It also prevents Tor clients from using an
5538 OR running in the same instance as an exit (due to a .exit request)
5539 if the OR does not meet the same requirements expected of an OR
5540 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5542 o Packaging changes:
5543 - Stop shipping the Tor specs files and development proposal documents
5544 in the tarball. They are now in a separate git repository at
5545 git://git.torproject.org/torspec.git
5546 - Do not include Git version tags as though they are SVN tags when
5547 generating a tarball from inside a repository that has switched
5548 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5551 Changes in version 0.2.2.22-alpha - 2011-01-25
5552 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
5553 main other change is a slight tweak to Tor's TLS handshake that makes
5554 relays and bridges that run this new version reachable from Iran again.
5555 We don't expect this tweak will win the arms race long-term, but it
5556 will buy us a bit more time until we roll out a better solution.
5559 - Fix a bounds-checking error that could allow an attacker to
5560 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
5562 - Don't assert when changing from bridge to relay or vice versa
5563 via the controller. The assert happened because we didn't properly
5564 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
5565 bug 2433. Reported by bastik.
5568 - Adjust our TLS Diffie-Hellman parameters to match those used by
5570 - Provide a log message stating which geoip file we're parsing
5571 instead of just stating that we're parsing the geoip file.
5572 Implements ticket 2432.
5575 - Check for and reject overly long directory certificates and
5576 directory tokens before they have a chance to hit any assertions.
5577 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
5580 Changes in version 0.2.2.21-alpha - 2011-01-15
5581 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
5582 continues our recent code security audit work. The main fix resolves
5583 a remote heap overflow vulnerability that can allow remote code
5584 execution (CVE-2011-0427). Other fixes address a variety of assert
5585 and crash bugs, most of which we think are hard to exploit remotely.
5587 o Major bugfixes (security), also included in 0.2.1.29:
5588 - Fix a heap overflow bug where an adversary could cause heap
5589 corruption. This bug probably allows remote code execution
5590 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5592 - Prevent a denial-of-service attack by disallowing any
5593 zlib-compressed data whose compression factor is implausibly
5594 high. Fixes part of bug 2324; reported by "doorss".
5595 - Zero out a few more keys in memory before freeing them. Fixes
5596 bug 2384 and part of bug 2385. These key instances found by
5597 "cypherpunks", based on Andrew Case's report about being able
5598 to find sensitive data in Tor's memory space if you have enough
5599 permissions. Bugfix on 0.0.2pre9.
5601 o Major bugfixes (crashes), also included in 0.2.1.29:
5602 - Prevent calls to Libevent from inside Libevent log handlers.
5603 This had potential to cause a nasty set of crashes, especially
5604 if running Libevent with debug logging enabled, and running
5605 Tor with a controller watching for low-severity log messages.
5606 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5607 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5608 underflow errors there too. Fixes the other part of bug 2324.
5609 - Fix a bug where we would assert if we ever had a
5610 cached-descriptors.new file (or another file read directly into
5611 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5612 on 0.2.1.25. Found by doorss.
5613 - Fix some potential asserts and parsing issues with grossly
5614 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5617 o Minor bugfixes (other), also included in 0.2.1.29:
5618 - Fix a bug with handling misformed replies to reverse DNS lookup
5619 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5620 bug reported by doorss.
5621 - Fix compilation on mingw when a pthreads compatibility library
5622 has been installed. (We don't want to use it, so we shouldn't
5623 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5624 - Fix a bug where we would declare that we had run out of virtual
5625 addresses when the address space was only half-exhausted. Bugfix
5627 - Correctly handle the case where AutomapHostsOnResolve is set but
5628 no virtual addresses are available. Fixes bug 2328; bugfix on
5629 0.1.2.1-alpha. Bug found by doorss.
5630 - Correctly handle wrapping around when we run out of virtual
5631 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
5633 o Minor features, also included in 0.2.1.29:
5634 - Update to the January 1 2011 Maxmind GeoLite Country database.
5635 - Introduce output size checks on all of our decryption functions.
5637 o Build changes, also included in 0.2.1.29:
5638 - Tor does not build packages correctly with Automake 1.6 and earlier;
5639 added a check to Makefile.am to make sure that we're building with
5640 Automake 1.7 or later.
5641 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5642 because we built it with a too-old version of automake. Thus that
5643 release broke ./configure --enable-openbsd-malloc, which is popular
5644 among really fast exit relays on Linux.
5646 o Major bugfixes, new in 0.2.2.21-alpha:
5647 - Prevent crash/heap corruption when the cbtnummodes consensus
5648 parameter is set to 0 or large values. Fixes bug 2317; bugfix
5651 o Major features, new in 0.2.2.21-alpha:
5652 - Introduce minimum/maximum values that clients will believe
5653 from the consensus. Now we'll have a better chance to avoid crashes
5654 or worse when a consensus param has a weird value.
5656 o Minor features, new in 0.2.2.21-alpha:
5657 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
5658 used on bridges, and it makes bridge scanning somewhat easier.
5659 - If writing the state file to disk fails, wait up to an hour before
5660 retrying again, rather than trying again each second. Fixes bug
5661 2346; bugfix on Tor 0.1.1.3-alpha.
5662 - Make Libevent log messages get delivered to controllers later,
5663 and not from inside the Libevent log handler. This prevents unsafe
5664 reentrant Libevent calls while still letting the log messages
5666 - Detect platforms that brokenly use a signed size_t, and refuse to
5667 build there. Found and analyzed by doorss and rransom.
5668 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
5671 o Minor bugfixes, new in 0.2.2.21-alpha:
5672 - Handle SOCKS messages longer than 128 bytes long correctly, rather
5673 than waiting forever for them to finish. Fixes bug 2330; bugfix
5674 on 0.2.0.16-alpha. Found by doorss.
5675 - Add assertions to check for overflow in arguments to
5676 base32_encode() and base32_decode(); fix a signed-unsigned
5677 comparison there too. These bugs are not actually reachable in Tor,
5678 but it's good to prevent future errors too. Found by doorss.
5679 - Correctly detect failures to create DNS requests when using Libevent
5680 versions before v2. (Before Libevent 2, we used our own evdns
5681 implementation. Its return values for Libevent's evdns_resolve_*()
5682 functions are not consistent with those from Libevent.) Fixes bug
5683 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
5685 o Documentation, new in 0.2.2.21-alpha:
5686 - Document the default socks host and port (127.0.0.1:9050) for
5690 Changes in version 0.2.1.29 - 2011-01-15
5691 Tor 0.2.1.29 continues our recent code security audit work. The main
5692 fix resolves a remote heap overflow vulnerability that can allow remote
5693 code execution. Other fixes address a variety of assert and crash bugs,
5694 most of which we think are hard to exploit remotely.
5696 o Major bugfixes (security):
5697 - Fix a heap overflow bug where an adversary could cause heap
5698 corruption. This bug probably allows remote code execution
5699 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
5701 - Prevent a denial-of-service attack by disallowing any
5702 zlib-compressed data whose compression factor is implausibly
5703 high. Fixes part of bug 2324; reported by "doorss".
5704 - Zero out a few more keys in memory before freeing them. Fixes
5705 bug 2384 and part of bug 2385. These key instances found by
5706 "cypherpunks", based on Andrew Case's report about being able
5707 to find sensitive data in Tor's memory space if you have enough
5708 permissions. Bugfix on 0.0.2pre9.
5710 o Major bugfixes (crashes):
5711 - Prevent calls to Libevent from inside Libevent log handlers.
5712 This had potential to cause a nasty set of crashes, especially
5713 if running Libevent with debug logging enabled, and running
5714 Tor with a controller watching for low-severity log messages.
5715 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
5716 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
5717 underflow errors there too. Fixes the other part of bug 2324.
5718 - Fix a bug where we would assert if we ever had a
5719 cached-descriptors.new file (or another file read directly into
5720 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
5721 on 0.2.1.25. Found by doorss.
5722 - Fix some potential asserts and parsing issues with grossly
5723 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
5726 o Minor bugfixes (other):
5727 - Fix a bug with handling misformed replies to reverse DNS lookup
5728 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
5729 bug reported by doorss.
5730 - Fix compilation on mingw when a pthreads compatibility library
5731 has been installed. (We don't want to use it, so we shouldn't
5732 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
5733 - Fix a bug where we would declare that we had run out of virtual
5734 addresses when the address space was only half-exhausted. Bugfix
5736 - Correctly handle the case where AutomapHostsOnResolve is set but
5737 no virtual addresses are available. Fixes bug 2328; bugfix on
5738 0.1.2.1-alpha. Bug found by doorss.
5739 - Correctly handle wrapping around to when we run out of virtual
5740 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
5741 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
5742 because we built it with a too-old version of automake. Thus that
5743 release broke ./configure --enable-openbsd-malloc, which is popular
5744 among really fast exit relays on Linux.
5747 - Update to the January 1 2011 Maxmind GeoLite Country database.
5748 - Introduce output size checks on all of our decryption functions.
5751 - Tor does not build packages correctly with Automake 1.6 and earlier;
5752 added a check to Makefile.am to make sure that we're building with
5753 Automake 1.7 or later.
5756 Changes in version 0.2.2.20-alpha - 2010-12-17
5757 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
5758 exploitable bugs. We also fix a variety of other significant bugs,
5759 change the IP address for one of our directory authorities, and update
5760 the minimum version that Tor relays must run to join the network.
5763 - Fix a remotely exploitable bug that could be used to crash instances
5764 of Tor remotely by overflowing on the heap. Remote-code execution
5765 hasn't been confirmed, but can't be ruled out. Everyone should
5766 upgrade. Bugfix on the 0.1.1 series and later.
5767 - Fix a bug that could break accounting on 64-bit systems with large
5768 time_t values, making them hibernate for impossibly long intervals.
5769 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
5770 - Fix a logic error in directory_fetches_from_authorities() that
5771 would cause all _non_-exits refusing single-hop-like circuits
5772 to fetch from authorities, when we wanted to have _exits_ fetch
5773 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
5775 - Fix a stream fairness bug that would cause newer streams on a given
5776 circuit to get preference when reading bytes from the origin or
5777 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
5778 introduced before the first Tor release, in svn revision r152.
5780 o Directory authority changes:
5781 - Change IP address and ports for gabelmoo (v3 directory authority).
5784 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
5785 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
5786 - Fix an off-by-one error in calculating some controller command
5787 argument lengths. Fortunately, this mistake is harmless since
5788 the controller code does redundant NUL termination too. Found by
5789 boboper. Bugfix on 0.1.1.1-alpha.
5790 - Do not dereference NULL if a bridge fails to build its
5791 extra-info descriptor. Found by an anonymous commenter on
5792 Trac. Bugfix on 0.2.2.19-alpha.
5795 - Update to the December 1 2010 Maxmind GeoLite Country database.
5796 - Directory authorities now reject relays running any versions of
5797 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
5798 known bugs that keep RELAY_EARLY cells from working on rendezvous
5799 circuits. Followup to fix for bug 2081.
5800 - Directory authorities now reject relays running any version of Tor
5801 older than 0.2.0.26-rc. That version is the earliest that fetches
5802 current directory information correctly. Fixes bug 2156.
5803 - Report only the top 10 ports in exit-port stats in order not to
5804 exceed the maximum extra-info descriptor length of 50 KB. Implements
5808 Changes in version 0.2.1.28 - 2010-12-17
5809 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
5810 exploitable bugs. We also took this opportunity to change the IP address
5811 for one of our directory authorities, and to update the geoip database
5815 - Fix a remotely exploitable bug that could be used to crash instances
5816 of Tor remotely by overflowing on the heap. Remote-code execution
5817 hasn't been confirmed, but can't be ruled out. Everyone should
5818 upgrade. Bugfix on the 0.1.1 series and later.
5820 o Directory authority changes:
5821 - Change IP address and ports for gabelmoo (v3 directory authority).
5824 - Update to the December 1 2010 Maxmind GeoLite Country database.
5827 Changes in version 0.2.1.27 - 2010-11-23
5828 Yet another OpenSSL security patch broke its compatibility with Tor:
5829 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
5830 also took this opportunity to fix several crash bugs, integrate a new
5831 directory authority, and update the bundled GeoIP database.
5834 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5835 No longer set the tlsext_host_name extension on server SSL objects;
5836 but continue to set it on client SSL objects. Our goal in setting
5837 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5838 bugfix on 0.2.1.1-alpha.
5839 - Do not log messages to the controller while shrinking buffer
5840 freelists. Doing so would sometimes make the controller connection
5841 try to allocate a buffer chunk, which would mess up the internals
5842 of the freelist and cause an assertion failure. Fixes bug 1125;
5843 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5844 - Learn our external IP address when we're a relay or bridge, even if
5845 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5846 where we introduced bridge relays that don't need to publish to
5847 be useful. Fixes bug 2050.
5848 - Do even more to reject (and not just ignore) annotations on
5849 router descriptors received anywhere but from the cache. Previously
5850 we would ignore such annotations at first, but cache them to disk
5851 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5852 - When you're using bridges and your network goes away and your
5853 bridges get marked as down, recover when you attempt a new socks
5854 connection (if the network is back), rather than waiting up to an
5855 hour to try fetching new descriptors for your bridges. Bugfix on
5856 0.2.0.3-alpha; fixes bug 1981.
5859 - Move to the November 2010 Maxmind GeoLite country db (rather
5860 than the June 2009 ip-to-country GeoIP db) for our statistics that
5861 count how many users relays are seeing from each country. Now we'll
5862 have more accurate data, especially for many African countries.
5864 o New directory authorities:
5865 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
5869 - Fix an assertion failure that could occur in directory caches or
5870 bridge users when using a very short voting interval on a testing
5871 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
5873 - Enforce multiplicity rules when parsing annotations. Bugfix on
5874 0.2.0.8-alpha. Found by piebeer.
5875 - Allow handshaking OR connections to take a full KeepalivePeriod
5876 seconds to handshake. Previously, we would close them after
5877 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
5878 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
5880 - When building with --enable-gcc-warnings on OpenBSD, disable
5881 warnings in system headers. This makes --enable-gcc-warnings
5882 pass on OpenBSD 4.8.
5885 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
5886 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
5887 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
5888 Servers can start sending this code when enough clients recognize
5889 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
5890 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
5891 Patch from mingw-san.
5894 - Remove the old debian/ directory from the main Tor distribution.
5895 The official Tor-for-debian git repository lives at the URL
5896 https://git.torproject.org/debian/tor.git
5897 - Stop shipping the old doc/website/ directory in the tarball. We
5898 changed the website format in late 2010, and what we shipped in
5899 0.2.1.26 really wasn't that useful anyway.
5902 Changes in version 0.2.2.19-alpha - 2010-11-22
5903 Yet another OpenSSL security patch broke its compatibility with Tor:
5904 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
5907 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
5908 No longer set the tlsext_host_name extension on server SSL objects;
5909 but continue to set it on client SSL objects. Our goal in setting
5910 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
5911 bugfix on 0.2.1.1-alpha.
5914 - Try harder not to exceed the maximum length of 50 KB when writing
5915 statistics to extra-info descriptors. This bug was triggered by very
5916 fast relays reporting exit-port, entry, and dirreq statistics.
5917 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
5918 - Publish a router descriptor even if generating an extra-info
5919 descriptor fails. Previously we would not publish a router
5920 descriptor without an extra-info descriptor; this can cause fast
5921 exit relays collecting exit-port statistics to drop from the
5922 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
5925 Changes in version 0.2.2.18-alpha - 2010-11-16
5926 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
5927 us lately, makes unpublished bridge relays able to detect their IP
5928 address, and fixes a wide variety of other bugs to get us much closer
5929 to a stable release.
5932 - Do even more to reject (and not just ignore) annotations on
5933 router descriptors received anywhere but from the cache. Previously
5934 we would ignore such annotations at first, but cache them to disk
5935 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
5936 - Do not log messages to the controller while shrinking buffer
5937 freelists. Doing so would sometimes make the controller connection
5938 try to allocate a buffer chunk, which would mess up the internals
5939 of the freelist and cause an assertion failure. Fixes bug 1125;
5940 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
5941 - Learn our external IP address when we're a relay or bridge, even if
5942 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
5943 where we introduced bridge relays that don't need to publish to
5944 be useful. Fixes bug 2050.
5945 - Maintain separate TLS contexts and certificates for incoming and
5946 outgoing connections in bridge relays. Previously we would use the
5947 same TLS contexts and certs for incoming and outgoing connections.
5948 Bugfix on 0.2.0.3-alpha; addresses bug 988.
5949 - Maintain separate identity keys for incoming and outgoing TLS
5950 contexts in bridge relays. Previously we would use the same
5951 identity keys for incoming and outgoing TLS contexts. Bugfix on
5952 0.2.0.3-alpha; addresses the other half of bug 988.
5953 - Avoid an assertion failure when we as an authority receive a
5954 duplicate upload of a router descriptor that we already have,
5955 but which we previously considered an obsolete descriptor.
5956 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
5957 - Avoid a crash bug triggered by looking at a dangling pointer while
5958 setting the network status consensus. Found by Robert Ransom.
5959 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
5960 - Fix a logic error where servers that _didn't_ act as exits would
5961 try to keep their server lists more aggressively up to date than
5962 exits, when it was supposed to be the other way around. Bugfix
5965 o Minor bugfixes (on Tor 0.2.1.x and earlier):
5966 - When we're trying to guess whether we know our IP address as
5967 a relay, we would log various ways that we failed to guess
5968 our address, but never log that we ended up guessing it
5969 successfully. Now add a log line to help confused and anxious
5970 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
5971 - Bring the logic that gathers routerinfos and assesses the
5972 acceptability of circuits into line. This prevents a Tor OP from
5973 getting locked in a cycle of choosing its local OR as an exit for a
5974 path (due to a .exit request) and then rejecting the circuit because
5975 its OR is not listed yet. It also prevents Tor clients from using an
5976 OR running in the same instance as an exit (due to a .exit request)
5977 if the OR does not meet the same requirements expected of an OR
5978 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
5979 - Correctly describe errors that occur when generating a TLS object.
5980 Previously we would attribute them to a failure while generating a
5981 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
5983 - Enforce multiplicity rules when parsing annotations. Bugfix on
5984 0.2.0.8-alpha. Found by piebeer.
5985 - Fix warnings that newer versions of autoconf produced during
5986 ./autogen.sh. These warnings appear to be harmless in our case,
5987 but they were extremely verbose. Fixes bug 2020.
5989 o Minor bugfixes (on Tor 0.2.2.x):
5990 - Enable protection of small arrays whenever we build with gcc
5991 hardening features, not only when also building with warnings
5992 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
5995 - Make hidden services work better in private Tor networks by not
5996 requiring any uptime to join the hidden service descriptor
5997 DHT. Implements ticket 2088.
5998 - Rate-limit the "your application is giving Tor only an IP address"
5999 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
6000 - When AllowSingleHopExits is set, print a warning to explain to the
6001 relay operator why most clients are avoiding her relay.
6002 - Update to the November 1 2010 Maxmind GeoLite Country database.
6004 o Code simplifications and refactoring:
6005 - When we fixed bug 1038 we had to put in a restriction not to send
6006 RELAY_EARLY cells on rend circuits. This was necessary as long
6007 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
6008 active. Now remove this obsolete check. Resolves bug 2081.
6009 - Some options used different conventions for uppercasing of acronyms
6010 when comparing manpage and source. Fix those in favor of the
6011 manpage, as it makes sense to capitalize acronyms.
6012 - Remove the torrc.complete file. It hasn't been kept up to date
6013 and users will have better luck checking out the manpage.
6014 - Remove the obsolete "NoPublish" option; it has been flagged
6015 as obsolete and has produced a warning since 0.1.1.18-rc.
6016 - Remove everything related to building the expert bundle for OS X.
6017 It has confused many users, doesn't work right on OS X 10.6,
6018 and is hard to get rid of once installed. Resolves bug 1274.
6021 Changes in version 0.2.2.17-alpha - 2010-09-30
6022 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
6023 to use one-hop circuits (which can put the exit relays at higher risk,
6024 plus unbalance the network); fixes a big bug in bandwidth accounting
6025 for relays that want to limit their monthly bandwidth use; fixes a
6026 big pile of bugs in how clients tolerate temporary network failure;
6027 and makes our adaptive circuit build timeout feature (which improves
6028 client performance if your network is fast while not breaking things
6029 if your network is slow) better handle bad networks.
6032 - Exit relays now try harder to block exit attempts from unknown
6033 relays, to make it harder for people to use them as one-hop proxies
6034 a la tortunnel. Controlled by the refuseunknownexits consensus
6035 parameter (currently enabled), or you can override it on your
6036 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
6038 o Major bugfixes (0.2.1.x and earlier):
6039 - Fix a bug in bandwidth accounting that could make us use twice
6040 the intended bandwidth when our interval start changes due to
6041 daylight saving time. Now we tolerate skew in stored vs computed
6042 interval starts: if the start of the period changes by no more than
6043 50% of the period's duration, we remember bytes that we transferred
6044 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
6045 - Always search the Windows system directory for system DLLs, and
6046 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
6047 - When you're using bridges and your network goes away and your
6048 bridges get marked as down, recover when you attempt a new socks
6049 connection (if the network is back), rather than waiting up to an
6050 hour to try fetching new descriptors for your bridges. Bugfix on
6051 0.2.0.3-alpha; fixes bug 1981.
6053 o Major bugfixes (on 0.2.2.x):
6054 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
6056 - Fix a segfault that could happen when operating a bridge relay with
6057 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
6058 - The consensus bandwidth-weights (used by clients to choose fast
6059 relays) entered an unexpected edge case in September where
6060 Exits were much scarcer than Guards, resulting in bad weight
6061 recommendations. Now we compute them using new constraints that
6062 should succeed in all cases. Also alter directory authorities to
6063 not include the bandwidth-weights line if they fail to produce
6064 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
6065 - When weighting bridges during path selection, we used to trust
6066 the bandwidths they provided in their descriptor, only capping them
6067 at 10MB/s. This turned out to be problematic for two reasons:
6068 Bridges could claim to handle a lot more traffic then they
6069 actually would, thus making more clients pick them and have a
6070 pretty effective DoS attack. The other issue is that new bridges
6071 that might not have a good estimate for their bw capacity yet
6072 would not get used at all unless no other bridges are available
6073 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
6075 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
6076 - Ignore cannibalized circuits when recording circuit build times.
6077 This should provide for a minor performance improvement for hidden
6078 service users using 0.2.2.14-alpha, and should remove two spurious
6079 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
6080 - Simplify the logic that causes us to decide if the network is
6081 unavailable for purposes of recording circuit build times. If we
6082 receive no cells whatsoever for the entire duration of a circuit's
6083 full measured lifetime, the network is probably down. Also ignore
6084 one-hop directory fetching circuit timeouts when calculating our
6085 circuit build times. These changes should hopefully reduce the
6086 cases where we see ridiculous circuit build timeouts for people
6087 with spotty wireless connections. Fixes part of bug 1772; bugfix
6089 - Prevent the circuit build timeout from becoming larger than
6090 the maximum build time we have ever seen. Also, prevent the time
6091 period for measurement circuits from becoming larger than twice that
6092 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
6095 - When we run out of directory information such that we can't build
6096 circuits, but then get enough that we can build circuits, log when
6097 we actually construct a circuit, so the user has a better chance of
6098 knowing what's going on. Fixes bug 1362.
6099 - Be more generous with how much bandwidth we'd use up (with
6100 accounting enabled) before entering "soft hibernation". Previously,
6101 we'd refuse new connections and circuits once we'd used up 95% of
6102 our allotment. Now, we use up 95% of our allotment, AND make sure
6103 that we have no more than 500MB (or 3 hours of expected traffic,
6104 whichever is lower) remaining before we enter soft hibernation.
6105 - If we've configured EntryNodes and our network goes away and/or all
6106 our entrynodes get marked down, optimistically retry them all when
6107 a new socks application request appears. Fixes bug 1882.
6108 - Add some more defensive programming for architectures that can't
6109 handle unaligned integer accesses. We don't know of any actual bugs
6110 right now, but that's the best time to fix them. Fixes bug 1943.
6111 - Support line continuations in the torrc config file. If a line
6112 ends with a single backslash character, the newline is ignored, and
6113 the configuration value is treated as continuing on the next line.
6116 o Minor bugfixes (on 0.2.1.x and earlier):
6117 - For bandwidth accounting, calculate our expected bandwidth rate
6118 based on the time during which we were active and not in
6119 soft-hibernation during the last interval. Previously, we were
6120 also considering the time spent in soft-hibernation. If this
6121 was a long time, we would wind up underestimating our bandwidth
6122 by a lot, and skewing our wakeup time towards the start of the
6123 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
6125 o Minor bugfixes (on 0.2.2.x):
6126 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
6127 which were disabled by the circuit build timeout changes in
6128 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
6129 - Make sure we don't warn about missing bandwidth weights when
6130 choosing bridges or other relays not in the consensus. Bugfix on
6131 0.2.2.10-alpha; fixes bug 1805.
6132 - In our logs, do not double-report signatures from unrecognized
6133 authorities both as "from unknown authority" and "not
6134 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
6137 Changes in version 0.2.2.16-alpha - 2010-09-17
6138 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
6139 evident at exit relays), and also continues to resolve all the little
6140 bugs that have been filling up trac lately.
6142 o Major bugfixes (stream-level fairness):
6143 - When receiving a circuit-level SENDME for a blocked circuit, try
6144 to package cells fairly from all the streams that had previously
6145 been blocked on that circuit. Previously, we had started with the
6146 oldest stream, and allowed each stream to potentially exhaust
6147 the circuit's package window. This gave older streams on any
6148 given circuit priority over newer ones. Fixes bug 1937. Detected
6149 originally by Camilo Viecco. This bug was introduced before the
6150 first Tor release, in svn commit r152: it is the new winner of
6151 the longest-lived bug prize.
6152 - When the exit relay got a circuit-level sendme cell, it started
6153 reading on the exit streams, even if had 500 cells queued in the
6154 circuit queue already, so the circuit queue just grew and grew in
6155 some cases. We fix this by not re-enabling reading on receipt of a
6156 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
6157 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
6159 - Newly created streams were allowed to read cells onto circuits,
6160 even if the circuit's cell queue was blocked and waiting to drain.
6161 This created potential unfairness, as older streams would be
6162 blocked, but newer streams would gladly fill the queue completely.
6163 We add code to detect this situation and prevent any stream from
6164 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
6168 - Update to the September 1 2010 Maxmind GeoLite Country database.
6169 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
6170 not. This would lead to a cookie that is still not group readable.
6171 Closes bug 1843. Suggested by katmagic.
6172 - When logging a rate-limited warning, we now mention how many messages
6173 got suppressed since the last warning.
6174 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
6175 do individual connection-level rate limiting of clients. The torrc
6176 config options with the same names trump the consensus params, if
6177 both are present. Replaces the old "bwconnrate" and "bwconnburst"
6178 consensus params which were broken from 0.2.2.7-alpha through
6179 0.2.2.14-alpha. Closes bug 1947.
6180 - When a router changes IP address or port, authorities now launch
6181 a new reachability test for it. Implements ticket 1899.
6182 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
6183 2 no signature, 4 required" messages about consensus signatures
6184 easier to read, and make sure they get logged at the same severity
6185 as the messages explaining which keys are which. Fixes bug 1290.
6186 - Don't warn when we have a consensus that we can't verify because
6187 of missing certificates, unless those certificates are ones
6188 that we have been trying and failing to download. Fixes bug 1145.
6189 - If you configure your bridge with a known identity fingerprint,
6190 and the bridge authority is unreachable (as it is in at least
6191 one country now), fall back to directly requesting the descriptor
6192 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
6194 - When building with --enable-gcc-warnings on OpenBSD, disable
6195 warnings in system headers. This makes --enable-gcc-warnings
6196 pass on OpenBSD 4.8.
6198 o Minor bugfixes (on 0.2.1.x and earlier):
6199 - Authorities will now attempt to download consensuses if their
6200 own efforts to make a live consensus have failed. This change
6201 means authorities that restart will fetch a valid consensus, and
6202 it means authorities that didn't agree with the current consensus
6203 will still fetch and serve it if it has enough signatures. Bugfix
6204 on 0.2.0.9-alpha; fixes bug 1300.
6205 - Ensure DNS requests launched by "RESOLVE" commands from the
6206 controller respect the __LeaveStreamsUnattached setconf options. The
6207 same goes for requests launched via DNSPort or transparent
6208 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
6209 - Allow handshaking OR connections to take a full KeepalivePeriod
6210 seconds to handshake. Previously, we would close them after
6211 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
6212 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
6214 - Rate-limit "Failed to hand off onionskin" warnings.
6215 - Never relay a cell for a circuit we have already destroyed.
6216 Between marking a circuit as closeable and finally closing it,
6217 it may have been possible for a few queued cells to get relayed,
6218 even though they would have been immediately dropped by the next
6219 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
6220 - Never queue a cell for a circuit that's already been marked
6222 - Never vote for a server as "Running" if we have a descriptor for
6223 it claiming to be hibernating, and that descriptor was published
6224 more recently than our last contact with the server. Bugfix on
6225 0.2.0.3-alpha; fixes bug 911.
6226 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
6229 o Minor bugfixes (on 0.2.2.x):
6230 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
6231 down if a directory fetch fails and you've configured either
6232 bridges or EntryNodes. The intent was to mark the relay as down
6233 _unless_ you're using bridges or EntryNodes, since if you are
6234 then you could quickly run out of entry points.
6235 - Fix the Windows directory-listing code. A bug introduced in
6236 0.2.2.14-alpha could make Windows directory servers forget to load
6237 some of their cached v2 networkstatus files.
6238 - Really allow clients to use relays as bridges. Fixes bug 1776;
6239 bugfix on 0.2.2.15-alpha.
6240 - Demote a warn to info that happens when the CellStatistics option
6241 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
6242 Reported by Moritz Bartl.
6243 - On Windows, build correctly either with or without Unicode support.
6244 This is necessary so that Tor can support fringe platforms like
6245 Windows 98 (which has no Unicode), or Windows CE (which has no
6246 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
6249 - Add a unit test for cross-platform directory-listing code.
6252 Changes in version 0.2.2.15-alpha - 2010-08-18
6253 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
6254 fixes a variety of other bugs that were preventing performance
6255 experiments from moving forward, fixes several bothersome memory leaks,
6256 and generally closes a lot of smaller bugs that have been filling up
6260 - Stop assigning the HSDir flag to relays that disable their
6261 DirPort (and thus will refuse to answer directory requests). This
6262 fix should dramatically improve the reachability of hidden services:
6263 hidden services and hidden service clients pick six HSDir relays
6264 to store and retrieve the hidden service descriptor, and currently
6265 about half of the HSDir relays will refuse to work. Bugfix on
6266 0.2.0.10-alpha; fixes part of bug 1693.
6267 - The PerConnBWRate and Burst config options, along with the
6268 bwconnrate and bwconnburst consensus params, initialized each conn's
6269 token bucket values only when the connection is established. Now we
6270 update them if the config options change, and update them every time
6271 we get a new consensus. Otherwise we can encounter an ugly edge
6272 case where we initialize an OR conn to client-level bandwidth,
6273 but then later the relay joins the consensus and we leave it
6274 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
6275 - Fix a regression that caused Tor to rebind its ports if it receives
6276 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
6279 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
6280 should give us approximately 40-50% more Guard-flagged nodes,
6281 improving the anonymity the Tor network can provide and also
6282 decreasing the dropoff in throughput that relays experience when
6283 they first get the Guard flag.
6284 - Allow enabling or disabling the *Statistics config options while
6288 - Update to the August 1 2010 Maxmind GeoLite Country database.
6289 - Have the controller interface give a more useful message than
6290 "Internal Error" in response to failed GETINFO requests.
6291 - Warn when the same option is provided more than once in a torrc
6292 file, on the command line, or in a single SETCONF statement, and
6293 the option is one that only accepts a single line. Closes bug 1384.
6294 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
6295 Patch from mingw-san.
6296 - Add support for the country code "{??}" in torrc options like
6297 ExcludeNodes, to indicate all routers of unknown country. Closes
6299 - Relays report the number of bytes spent on answering directory
6300 requests in extra-info descriptors similar to {read,write}-history.
6301 Implements enhancement 1790.
6303 o Minor bugfixes (on 0.2.1.x and earlier):
6304 - Complain if PublishServerDescriptor is given multiple arguments that
6305 include 0 or 1. This configuration will be rejected in the future.
6306 Bugfix on 0.2.0.1-alpha; closes bug 1107.
6307 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
6308 Bugfix on 0.2.0.13-alpha; closes bug 928.
6309 - Change "Application request when we're believed to be offline."
6310 notice to "Application request when we haven't used client
6311 functionality lately.", to clarify that it's not an error. Bugfix
6312 on 0.0.9.3; fixes bug 1222.
6313 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
6314 would return "551 Internal error" rather than "552 Unrecognized key
6315 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
6316 - Users can't configure a regular relay to be their bridge. It didn't
6317 work because when Tor fetched the bridge descriptor, it found
6318 that it already had it, and didn't realize that the purpose of the
6319 descriptor had changed. Now we replace routers with a purpose other
6320 than bridge with bridge descriptors when fetching them. Bugfix on
6321 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
6322 refetch the descriptor with router purpose 'general', disabling
6324 - Fix a rare bug in rend_fn unit tests: we would fail a test when
6325 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
6326 on 0.2.0.10-alpha; fixes bug 1808.
6327 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
6328 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
6329 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
6330 Servers can start sending this code when enough clients recognize
6331 it. Also update the spec to reflect this new reason. Bugfix on
6332 0.1.0.1-rc; fixes part of bug 1793.
6333 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
6334 when we switch from being a public relay to a bridge. Otherwise
6335 there will still be clients that see the relay in their consensus,
6336 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
6338 - Instead of giving an assertion failure on an internal mismatch
6339 on estimated freelist size, just log a BUG warning and try later.
6340 Mitigates but does not fix bug 1125.
6341 - Fix an assertion failure that could occur in caches or bridge users
6342 when using a very short voting interval on a testing network.
6343 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
6345 o Minor bugfixes (on 0.2.2.x):
6346 - Alter directory authorities to always consider Exit-flagged nodes
6347 as potential Guard nodes in their votes. The actual decision to
6348 use Exits as Guards is done in the consensus bandwidth weights.
6349 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
6350 - When the controller is reporting the purpose of circuits that
6351 didn't finish building before the circuit build timeout, it was
6352 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
6353 - Our libevent version parsing code couldn't handle versions like
6354 1.4.14b-stable and incorrectly warned the user about using an
6355 old and broken version of libevent. Treat 1.4.14b-stable like
6356 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
6358 - Don't use substitution references like $(VAR:MOD) when
6359 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
6360 '$(:x)' to 'x' rather than the empty string. This bites us in
6361 doc/ when configured with --disable-asciidoc. Bugfix on
6362 0.2.2.9-alpha; fixes bug 1773.
6363 - Remove a spurious hidden service server-side log notice about
6364 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
6366 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
6368 - Correctly report written bytes on linked connections. Found while
6369 implementing 1790. Bugfix on 0.2.2.4-alpha.
6370 - Fix three memory leaks: one in circuit_build_times_parse_state(),
6371 one in dirvote_add_signatures_to_pending_consensus(), and one every
6372 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
6373 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
6375 o Code simplifications and refactoring:
6376 - Take a first step towards making or.h smaller by splitting out
6377 function definitions for all source files in src/or/. Leave
6378 structures and defines in or.h for now.
6379 - Remove a bunch of unused function declarations as well as a block of
6380 #if 0'd code from the unit tests. Closes bug 1824.
6381 - New unit tests for exit-port history statistics; refactored exit
6382 statistics code to be more easily tested.
6383 - Remove the old debian/ directory from the main Tor distribution.
6384 The official Tor-for-debian git repository lives at the URL
6385 https://git.torproject.org/debian/tor.git
6388 Changes in version 0.2.2.14-alpha - 2010-07-12
6389 Tor 0.2.2.14-alpha greatly improves client-side handling of
6390 circuit build timeouts, which are used to estimate speed and improve
6391 performance. We also move to a much better GeoIP database, port Tor to
6392 Windows CE, introduce new compile flags that improve code security,
6393 add an eighth v3 directory authority, and address a lot of more
6397 - Tor directory authorities no longer crash when started with a
6398 cached-microdesc-consensus file in their data directory. Bugfix
6399 on 0.2.2.6-alpha; fixes bug 1532.
6400 - Treat an unset $HOME like an empty $HOME rather than triggering an
6401 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
6402 - Ignore negative and large circuit build timeout values that can
6403 happen during a suspend or hibernate. These values caused various
6404 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
6405 - Alter calculation of Pareto distribution parameter 'Xm' for
6406 Circuit Build Timeout learning to use the weighted average of the
6407 top N=3 modes (because we have three entry guards). Considering
6408 multiple modes should improve the timeout calculation in some cases,
6409 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
6411 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
6412 right censored distribution model. This approach improves over the
6413 synthetic timeout generation approach that was producing insanely
6414 high timeout values. Now we calculate build timeouts using truncated
6415 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
6416 - Do not close circuits that are under construction when they reach
6417 the circuit build timeout. Instead, leave them building (but do not
6418 use them) for up until the time corresponding to the 95th percentile
6419 on the Pareto CDF or 60 seconds, whichever is greater. This is done
6420 to provide better data for the new Pareto model. This percentile
6421 can be controlled by the consensus.
6424 - Move to the June 2010 Maxmind GeoLite country db (rather than the
6425 June 2009 ip-to-country GeoIP db) for our statistics that count
6426 how many users relays are seeing from each country. Now we have
6427 more accurate data for many African countries.
6428 - Port Tor to build and run correctly on Windows CE systems, using
6429 the wcecompat library. Contributed by Valerio Lupi.
6430 - New "--enable-gcc-hardening" ./configure flag (off by default)
6431 to turn on gcc compile time hardening options. It ensures
6432 that signed ints have defined behavior (-fwrapv), enables
6433 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
6434 with canaries (-fstack-protector-all), turns on ASLR protection if
6435 supported by the kernel (-fPIE, -pie), and adds additional security
6436 related warnings. Verified to work on Mac OS X and Debian Lenny.
6437 - New "--enable-linker-hardening" ./configure flag (off by default)
6438 to turn on ELF specific hardening features (relro, now). This does
6439 not work with Mac OS X or any other non-ELF binary format.
6441 o New directory authorities:
6442 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
6446 - New config option "WarnUnsafeSocks 0" disables the warning that
6447 occurs whenever Tor receives a socks handshake using a version of
6448 the socks protocol that can only provide an IP address (rather
6449 than a hostname). Setups that do DNS locally over Tor are fine,
6450 and we shouldn't spam the logs in that case.
6451 - Convert the HACKING file to asciidoc, and add a few new sections
6452 to it, explaining how we use Git, how we make changelogs, and
6453 what should go in a patch.
6454 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
6455 event, to give information on the current rate of circuit timeouts
6456 over our stored history.
6457 - Add ability to disable circuit build time learning via consensus
6458 parameter and via a LearnCircuitBuildTimeout config option. Also
6459 automatically disable circuit build time calculation if we are
6460 either a AuthoritativeDirectory, or if we fail to write our state
6461 file. Fixes bug 1296.
6462 - More gracefully handle corrupt state files, removing asserts
6463 in favor of saving a backup and resetting state.
6464 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
6468 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
6470 - When a2x fails, mention that the user could disable manpages instead
6471 of trying to fix their asciidoc installation.
6472 - Where available, use Libevent 2.0's periodic timers so that our
6473 once-per-second cleanup code gets called even more closely to
6474 once per second than it would otherwise. Fixes bug 943.
6475 - If you run a bridge that listens on multiple IP addresses, and
6476 some user configures a bridge address that uses a different IP
6477 address than your bridge writes in its router descriptor, and the
6478 user doesn't specify an identity key, their Tor would discard the
6479 descriptor because "it isn't one of our configured bridges", and
6480 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
6481 Bugfix on 0.2.0.3-alpha.
6482 - If OpenSSL fails to make a duplicate of a private or public key, log
6483 an error message and try to exit cleanly. May help with debugging
6484 if bug 1209 ever remanifests.
6485 - Save a couple bytes in memory allocation every time we escape
6486 certain characters in a string. Patch from Florian Zumbiehl.
6487 - Make it explicit that we don't cannibalize one-hop circuits. This
6488 happens in the wild, but doesn't turn out to be a problem because
6489 we fortunately don't use those circuits. Many thanks to outofwords
6490 for the initial analysis and to swissknife who confirmed that
6491 two-hop circuits are actually created.
6492 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
6493 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
6494 - Eliminate a case where a circuit build time warning was displayed
6495 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
6498 Changes in version 0.2.1.26 - 2010-05-02
6499 Tor 0.2.1.26 addresses the recent connection and memory overload
6500 problems we've been seeing on relays, especially relays with their
6501 DirPort open. If your relay has been crashing, or you turned it off
6502 because it used too many resources, give this release a try.
6504 This release also fixes yet another instance of broken OpenSSL libraries
6505 that was causing some relays to drop out of the consensus.
6508 - Teach relays to defend themselves from connection overload. Relays
6509 now close idle circuits early if it looks like they were intended
6510 for directory fetches. Relays are also more aggressive about closing
6511 TLS connections that have no circuits on them. Such circuits are
6512 unlikely to be re-used, and tens of thousands of them were piling
6513 up at the fast relays, causing the relays to run out of sockets
6514 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6515 their directory fetches over TLS).
6516 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6517 that claim to be earlier than 0.9.8m, but which have in reality
6518 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6519 behavior. Possible fix for some cases of bug 1346.
6520 - Directory mirrors were fetching relay descriptors only from v2
6521 directory authorities, rather than v3 authorities like they should.
6522 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6523 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6526 - Finally get rid of the deprecated and now harmful notion of "clique
6527 mode", where directory authorities maintain TLS connections to
6531 - In the util/threads test, no longer free the test_mutex before all
6532 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6533 - The master thread could starve the worker threads quite badly on
6534 certain systems, causing them to run only partially in the allowed
6535 window. This resulted in test failures. Now the master thread sleeps
6536 occasionally for a few microseconds while the two worker-threads
6537 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6540 Changes in version 0.2.2.13-alpha - 2010-04-24
6541 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
6542 problems we've been seeing on relays, especially relays with their
6543 DirPort open. If your relay has been crashing, or you turned it off
6544 because it used too many resources, give this release a try.
6547 - Teach relays to defend themselves from connection overload. Relays
6548 now close idle circuits early if it looks like they were intended
6549 for directory fetches. Relays are also more aggressive about closing
6550 TLS connections that have no circuits on them. Such circuits are
6551 unlikely to be re-used, and tens of thousands of them were piling
6552 up at the fast relays, causing the relays to run out of sockets
6553 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
6554 their directory fetches over TLS).
6557 - Finally get rid of the deprecated and now harmful notion of "clique
6558 mode", where directory authorities maintain TLS connections to
6560 - Directory authorities now do an immediate reachability check as soon
6561 as they hear about a new relay. This change should slightly reduce
6562 the time between setting up a relay and getting listed as running
6563 in the consensus. It should also improve the time between setting
6564 up a bridge and seeing use by bridge users.
6565 - Directory authorities no longer launch a TLS connection to every
6566 relay as they startup. Now that we have 2k+ descriptors cached,
6567 the resulting network hiccup is becoming a burden. Besides,
6568 authorities already avoid voting about Running for the first half
6569 hour of their uptime.
6572 Changes in version 0.2.2.12-alpha - 2010-04-20
6573 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
6574 handle and vote on descriptors. It was causing relays to drop out of
6578 - Many relays have been falling out of the consensus lately because
6579 not enough authorities know about their descriptor for them to get
6580 a majority of votes. When we deprecated the v2 directory protocol,
6581 we got rid of the only way that v3 authorities can hear from each
6582 other about other descriptors. Now authorities examine every v3
6583 vote for new descriptors, and fetch them from that authority. Bugfix
6585 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
6586 and a warning in or.h related to bandwidth_weight_rule_t that
6587 prevented clean compile on OS X. Fixes bug 1363; bugfix on
6589 - Fix a segfault on relays when DirReqStatistics is enabled
6590 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
6594 - Demote a confusing TLS warning that relay operators might get when
6595 someone tries to talk to their OrPort. It is neither the operator's
6596 fault nor can they do anything about it. Fixes bug 1364; bugfix
6600 Changes in version 0.2.2.11-alpha - 2010-04-15
6601 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
6602 libraries that was causing some relays to drop out of the consensus.
6605 - Directory mirrors were fetching relay descriptors only from v2
6606 directory authorities, rather than v3 authorities like they should.
6607 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
6608 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
6609 - Fix a parsing error that made every possible value of
6610 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
6611 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
6612 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
6613 about the option without breaking older ones.
6614 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
6615 that claim to be earlier than 0.9.8m, but which have in reality
6616 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
6617 behavior. Possible fix for some cases of bug 1346.
6620 - Experiment with a more aggressive approach to preventing clients
6621 from making one-hop exit streams. Exit relays who want to try it
6622 out can set "RefuseUnknownExits 1" in their torrc, and then look
6623 for "Attempt by %s to open a stream" log messages. Let us know
6625 - Add support for statically linking zlib by specifying
6626 --enable-static-zlib, to go with our support for statically linking
6627 openssl and libevent. Resolves bug 1358.
6630 - Fix a segfault that happens whenever a Tor client that is using
6631 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
6633 - When we cleaned up the contrib/tor-exit-notice.html file, we left
6634 out the first line. Fixes bug 1295.
6635 - When building the manpage from a tarball, we required asciidoc, but
6636 the asciidoc -> roff/html conversion was already done for the
6637 tarball. Make 'make' complain only when we need asciidoc (either
6638 because we're compiling directly from git, or because we altered
6639 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
6640 - When none of the directory authorities vote on any params, Tor
6641 segfaulted when trying to make the consensus from the votes. We
6642 didn't trigger the bug in practice, because authorities do include
6643 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
6646 - In the util/threads test, no longer free the test_mutex before all
6647 worker threads have finished. Bugfix on 0.2.1.6-alpha.
6648 - The master thread could starve the worker threads quite badly on
6649 certain systems, causing them to run only partially in the allowed
6650 window. This resulted in test failures. Now the master thread sleeps
6651 occasionally for a few microseconds while the two worker-threads
6652 compete for the mutex. Bugfix on 0.2.0.1-alpha.
6655 Changes in version 0.2.2.10-alpha - 2010-03-07
6656 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
6657 could prevent relays from guessing their IP address correctly. It also
6658 starts the groundwork for another client-side performance boost, since
6659 currently we're not making efficient use of relays that have both the
6660 Guard flag and the Exit flag.
6663 - Fix a regression from our patch for bug 1244 that caused relays
6664 to guess their IP address incorrectly if they didn't set Address
6665 in their torrc and/or their address fails to resolve. Bugfix on
6666 0.2.2.9-alpha; fixes bug 1269.
6668 o Major features (performance):
6669 - Directory authorities now compute consensus weightings that instruct
6670 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
6671 and no flag. Clients that use these weightings will distribute
6672 network load more evenly across these different relay types. The
6673 weightings are in the consensus so we can change them globally in
6674 the future. Extra thanks to "outofwords" for finding some nasty
6675 security bugs in the first implementation of this feature.
6677 o Minor features (performance):
6678 - Always perform router selections using weighted relay bandwidth,
6679 even if we don't need a high capacity circuit at the time. Non-fast
6680 circuits now only differ from fast ones in that they can use relays
6681 not marked with the Fast flag. This "feature" could turn out to
6682 be a horrible bug; we should investigate more before it goes into
6686 - Allow disabling building of the manpages. Skipping the manpage
6687 speeds up the build considerably.
6689 o Minor bugfixes (on 0.2.2.x):
6690 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
6691 Bugfix on 0.2.2.9-alpha.
6692 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
6693 config option. Bugfix on 0.2.2.7-alpha.
6694 - Ship the asciidoc-helper file in the tarball, so that people can
6695 build from source if they want to, and touching the .1.txt files
6696 doesn't break the build. Bugfix on 0.2.2.9-alpha.
6698 o Minor bugfixes (on 0.2.1.x or earlier):
6699 - Fix a dereference-then-NULL-check sequence when publishing
6700 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6702 - Fix another dereference-then-NULL-check sequence. Bugfix on
6703 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6704 - Make sure we treat potentially not NUL-terminated strings correctly.
6705 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6707 o Code simplifications and refactoring:
6708 - Fix some urls in the exit notice file and make it XHTML1.1 strict
6709 compliant. Based on a patch from Christian Kujau.
6710 - Don't use sed in asciidoc-helper anymore.
6711 - Make the build process fail if asciidoc cannot be found and
6712 building with asciidoc isn't disabled.
6715 Changes in version 0.2.2.9-alpha - 2010-02-22
6716 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
6717 location of a directory authority, and cleans up a bunch of small bugs.
6719 o Directory authority changes:
6720 - Change IP address for dannenberg (v3 directory authority), and
6721 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6722 service directory authority) from the list.
6725 - Make Tor work again on the latest OS X: when deciding whether to
6726 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6727 version at run-time, not compile time. We need to do this because
6728 Apple doesn't update its dev-tools headers when it updates its
6729 libraries in a security patch.
6730 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6731 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6732 a memory leak when requesting a hidden service descriptor we've
6733 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6735 - Authorities could be tricked into giving out the Exit flag to relays
6736 that didn't allow exiting to any ports. This bug could screw
6737 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
6738 1238. Bug discovered by Martin Kowalczyk.
6739 - When freeing a session key, zero it out completely. We only zeroed
6740 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6741 patched by ekir. Fixes bug 1254.
6744 - Fix static compilation by listing the openssl libraries in the right
6745 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
6746 - Resume handling .exit hostnames in a special way: originally we
6747 stripped the .exit part and used the requested exit relay. In
6748 0.2.2.1-alpha we stopped treating them in any special way, meaning
6749 if you use a .exit address then Tor will pass it on to the exit
6750 relay. Now we reject the .exit stream outright, since that behavior
6751 might be more expected by the user. Found and diagnosed by Scott
6752 Bennett and Downie on or-talk.
6753 - Don't spam the controller with events when we have no file
6754 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
6755 for log messages was already solved from bug 748.)
6756 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
6758 - Make the DNSPort option work with libevent 2.x. Don't alter the
6759 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
6760 - Emit a GUARD DROPPED controller event for a case we missed.
6761 - Make more fields in the controller protocol case-insensitive, since
6762 control-spec.txt said they were.
6763 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6764 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6765 - Fix a spec conformance issue: the network-status-version token
6766 must be the first token in a v3 consensus or vote. Discovered by
6767 parakeep. Bugfix on 0.2.0.3-alpha.
6769 o Code simplifications and refactoring:
6770 - Generate our manpage and HTML documentation using Asciidoc. This
6771 change should make it easier to maintain the documentation, and
6773 - Remove the --enable-iphone option. According to reports from Marco
6774 Bonetti, Tor builds fine without any special tweaking on recent
6775 iPhone SDK versions.
6776 - Removed some unnecessary files from the source distribution. The
6777 AUTHORS file has now been merged into the people page on the
6778 website. The roadmaps and design doc can now be found in the
6779 projects directory in svn.
6780 - Enabled various circuit build timeout constants to be controlled
6781 by consensus parameters. Also set better defaults for these
6782 parameters based on experimentation on broadband and simulated
6786 - The 'EXTENDCIRCUIT' control port command can now be used with
6787 a circ id of 0 and no path. This feature will cause Tor to build
6788 a new 'fast' general purpose circuit using its own path selection
6790 - Added a BUILDTIMEOUT_SET controller event to describe changes
6791 to the circuit build timeout.
6792 - Future-proof the controller protocol a bit by ignoring keyword
6793 arguments we do not recognize.
6794 - Expand homedirs passed to tor-checkkey. This should silence a
6795 coverity complaint about passing a user-supplied string into
6796 open() without checking it.
6799 Changes in version 0.2.1.25 - 2010-03-16
6800 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
6801 prevent relays from guessing their IP address correctly. It also fixes
6802 several minor potential security bugs.
6805 - Fix a regression from our patch for bug 1244 that caused relays
6806 to guess their IP address incorrectly if they didn't set Address
6807 in their torrc and/or their address fails to resolve. Bugfix on
6808 0.2.1.23; fixes bug 1269.
6809 - When freeing a session key, zero it out completely. We only zeroed
6810 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
6811 patched by ekir. Fixes bug 1254.
6814 - Fix a dereference-then-NULL-check sequence when publishing
6815 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
6817 - Fix another dereference-then-NULL-check sequence. Bugfix on
6818 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
6819 - Make sure we treat potentially not NUL-terminated strings correctly.
6820 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
6824 Changes in version 0.2.1.24 - 2010-02-21
6825 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
6829 - Work correctly out-of-the-box with even more vendor-patched versions
6830 of OpenSSL. In particular, make it so Debian and OS X don't need
6831 customized patches to run/build.
6834 Changes in version 0.2.1.23 - 2010-02-13
6835 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
6836 again on the latest OS X, and updates the location of a directory
6839 o Major bugfixes (performance):
6840 - We were selecting our guards uniformly at random, and then weighting
6841 which of our guards we'd use uniformly at random. This imbalance
6842 meant that Tor clients were severely limited on throughput (and
6843 probably latency too) by the first hop in their circuit. Now we
6844 select guards weighted by currently advertised bandwidth. We also
6845 automatically discard guards picked using the old algorithm. Fixes
6846 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6849 - Make Tor work again on the latest OS X: when deciding whether to
6850 use strange flags to turn TLS renegotiation on, detect the OpenSSL
6851 version at run-time, not compile time. We need to do this because
6852 Apple doesn't update its dev-tools headers when it updates its
6853 libraries in a security patch.
6854 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
6855 that could happen on 32-bit platforms with 64-bit time_t. Also fix
6856 a memory leak when requesting a hidden service descriptor we've
6857 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
6860 o Directory authority changes:
6861 - Change IP address for dannenberg (v3 directory authority), and
6862 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
6863 service directory authority) from the list.
6866 - Refactor resolve_my_address() to not use gethostbyname() anymore.
6867 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
6870 - Avoid a mad rush at the beginning of each month when each client
6871 rotates half of its guards. Instead we spread the rotation out
6872 throughout the month, but we still avoid leaving a precise timestamp
6873 in the state file about when we first picked the guard. Improves
6874 over the behavior introduced in 0.1.2.17.
6877 Changes in version 0.2.2.8-alpha - 2010-01-26
6878 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
6879 causing bridge relays to disappear. If you're running a bridge,
6883 - Fix a memory corruption bug on bridges that occured during the
6884 inclusion of stats data in extra-info descriptors. Also fix the
6885 interface for geoip_get_bridge_stats* to prevent similar bugs in
6886 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
6887 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
6890 - Ignore OutboundBindAddress when connecting to localhost.
6891 Connections to localhost need to come _from_ localhost, or else
6892 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
6896 Changes in version 0.2.2.7-alpha - 2010-01-19
6897 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
6898 as laying the groundwork for further relay-side performance fixes. It
6899 also starts cleaning up client behavior with respect to the EntryNodes,
6900 ExitNodes, and StrictNodes config options.
6902 This release also rotates two directory authority keys, due to a
6903 security breach of some of the Torproject servers.
6905 o Directory authority changes:
6906 - Rotate keys (both v3 identity and relay identity) for moria1
6909 o Major features (performance):
6910 - We were selecting our guards uniformly at random, and then weighting
6911 which of our guards we'd use uniformly at random. This imbalance
6912 meant that Tor clients were severely limited on throughput (and
6913 probably latency too) by the first hop in their circuit. Now we
6914 select guards weighted by currently advertised bandwidth. We also
6915 automatically discard guards picked using the old algorithm. Fixes
6916 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
6917 - When choosing which cells to relay first, relays can now favor
6918 circuits that have been quiet recently, to provide lower latency
6919 for low-volume circuits. By default, relays enable or disable this
6920 feature based on a setting in the consensus. You can override
6921 this default by using the new "CircuitPriorityHalflife" config
6922 option. Design and code by Ian Goldberg, Can Tang, and Chris
6924 - Add separate per-conn write limiting to go with the per-conn read
6925 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
6926 but never per-conn write limits.
6927 - New consensus params "bwconnrate" and "bwconnburst" to let us
6928 rate-limit client connections as they enter the network. It's
6929 controlled in the consensus so we can turn it on and off for
6930 experiments. It's starting out off. Based on proposal 163.
6932 o Major features (relay selection options):
6933 - Switch to a StrictNodes config option, rather than the previous
6934 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
6935 "StrictExcludeNodes" option.
6936 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
6937 change during a config reload, mark and discard all our origin
6938 circuits. This fix should address edge cases where we change the
6939 config options and but then choose a circuit that we created before
6941 - If EntryNodes or ExitNodes are set, be more willing to use an
6942 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
6944 - Make EntryNodes config option much more aggressive even when
6945 StrictNodes is not set. Before it would prepend your requested
6946 entrynodes to your list of guard nodes, but feel free to use others
6947 after that. Now it chooses only from your EntryNodes if any of
6948 those are available, and only falls back to others if a) they're
6949 all down and b) StrictNodes is not set.
6950 - Now we refresh your entry guards from EntryNodes at each consensus
6951 fetch -- rather than just at startup and then they slowly rot as
6952 the network changes.
6955 - Stop bridge directory authorities from answering dbg-stability.txt
6956 directory queries, which would let people fetch a list of all
6957 bridge identities they track. Bugfix on 0.2.1.6-alpha.
6960 - Log a notice when we get a new control connection. Now it's easier
6961 for security-conscious users to recognize when a local application
6962 is knocking on their controller door. Suggested by bug 1196.
6963 - New config option "CircuitStreamTimeout" to override our internal
6964 timeout schedule for how many seconds until we detach a stream from
6965 a circuit and try a new circuit. If your network is particularly
6966 slow, you might want to set this to a number like 60.
6967 - New controller command "getinfo config-text". It returns the
6968 contents that Tor would write if you send it a SAVECONF command,
6969 so the controller can write the file to disk itself.
6970 - New options for SafeLogging to allow scrubbing only log messages
6971 generated while acting as a relay.
6972 - Ship the bridges spec file in the tarball too.
6973 - Avoid a mad rush at the beginning of each month when each client
6974 rotates half of its guards. Instead we spread the rotation out
6975 throughout the month, but we still avoid leaving a precise timestamp
6976 in the state file about when we first picked the guard. Improves
6977 over the behavior introduced in 0.1.2.17.
6979 o Minor bugfixes (compiling):
6980 - Fix compilation on OS X 10.3, which has a stub mlockall() but
6981 hides it. Bugfix on 0.2.2.6-alpha.
6982 - Fix compilation on Solaris by removing support for the
6983 DisableAllSwap config option. Solaris doesn't have an rlimit for
6984 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
6987 o Minor bugfixes (crashes):
6988 - Do not segfault when writing buffer stats when we haven't observed
6989 a single circuit to report about. Found by Fabian Lanze. Bugfix on
6991 - If we're in the pathological case where there's no exit bandwidth
6992 but there is non-exit bandwidth, or no guard bandwidth but there
6993 is non-guard bandwidth, don't crash during path selection. Bugfix
6995 - Fix an impossible-to-actually-trigger buffer overflow in relay
6996 descriptor generation. Bugfix on 0.1.0.15.
6998 o Minor bugfixes (privacy):
6999 - Fix an instance where a Tor directory mirror might accidentally
7000 log the IP address of a misbehaving Tor client. Bugfix on
7002 - Don't list Windows capabilities in relay descriptors. We never made
7003 use of them, and maybe it's a bad idea to publish them. Bugfix
7006 o Minor bugfixes (other):
7007 - Resolve an edge case in path weighting that could make us misweight
7008 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
7009 - Fix statistics on client numbers by country as seen by bridges that
7010 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
7011 intervals instead of variable 12-to-48-hour intervals.
7012 - After we free an internal connection structure, overwrite it
7013 with a different memory value than we use for overwriting a freed
7014 internal circuit structure. Should help with debugging. Suggested
7016 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
7020 - Remove the HSAuthorityRecordStats option that version 0 hidden
7021 service authorities could have used to track statistics of overall
7022 hidden service usage.
7025 Changes in version 0.2.1.22 - 2010-01-19
7026 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
7027 authorities -- it would tell you its whole history of bridge descriptors
7028 if you make the right directory request. This stable update also
7029 rotates two of the seven v3 directory authority keys and locations.
7031 o Directory authority changes:
7032 - Rotate keys (both v3 identity and relay identity) for moria1
7036 - Stop bridge directory authorities from answering dbg-stability.txt
7037 directory queries, which would let people fetch a list of all
7038 bridge identities they track. Bugfix on 0.2.1.6-alpha.
7041 Changes in version 0.2.1.21 - 2009-12-21
7042 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
7043 library. If you use Tor on Linux / Unix and you're getting SSL
7044 renegotiation errors, upgrading should help. We also recommend an
7045 upgrade if you're an exit relay.
7048 - Work around a security feature in OpenSSL 0.9.8l that prevents our
7049 handshake from working unless we explicitly tell OpenSSL that we
7050 are using SSL renegotiation safely. We are, of course, but OpenSSL
7051 0.9.8l won't work unless we say we are.
7052 - Avoid crashing if the client is trying to upload many bytes and the
7053 circuit gets torn down at the same time, or if the flip side
7054 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
7057 - Do not refuse to learn about authority certs and v2 networkstatus
7058 documents that are older than the latest consensus. This bug might
7059 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
7060 Spotted and fixed by xmux.
7061 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
7062 trigger platform-specific option misparsing case found by Coverity
7064 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
7065 trigger assert. Fixes bug 1173.
7068 Changes in version 0.2.2.6-alpha - 2009-11-19
7069 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
7070 support for the new lower-footprint "microdescriptor" directory design,
7071 future-proofing our consensus format against new hash functions or
7072 other changes, and an Android port. It also makes Tor compatible with
7073 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
7076 - Directory authorities can now create, vote on, and serve multiple
7077 parallel formats of directory data as part of their voting process.
7078 Partially implements Proposal 162: "Publish the consensus in
7080 - Directory authorities can now agree on and publish small summaries
7081 of router information that clients can use in place of regular
7082 server descriptors. This transition will eventually allow clients
7083 to use far less bandwidth for downloading information about the
7084 network. Begins the implementation of Proposal 158: "Clients
7085 download consensus + microdescriptors".
7086 - The directory voting system is now extensible to use multiple hash
7087 algorithms for signatures and resource selection. Newer formats
7088 are signed with SHA256, with a possibility for moving to a better
7089 hash algorithm in the future.
7090 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
7091 current and future memory pages via mlockall(). On supported
7092 platforms (modern Linux and probably BSD but not Windows or OS X),
7093 this should effectively disable any and all attempts to page out
7094 memory. This option requires that you start your Tor as root --
7095 if you use DisableAllSwap, please consider using the User option
7096 to properly reduce the privileges of your Tor.
7097 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
7098 to help Tor build correctly for Android phones.
7101 - Work around a security feature in OpenSSL 0.9.8l that prevents our
7102 handshake from working unless we explicitly tell OpenSSL that we
7103 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
7104 won't work unless we say we are.
7107 - Fix a crash bug when trying to initialize the evdns module in
7108 Libevent 2. Bugfix on 0.2.1.16-rc.
7109 - Stop logging at severity 'warn' when some other Tor client tries
7110 to establish a circuit with us using weak DH keys. It's a protocol
7111 violation, but that doesn't mean ordinary users need to hear about
7112 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
7113 - Do not refuse to learn about authority certs and v2 networkstatus
7114 documents that are older than the latest consensus. This bug might
7115 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
7116 Spotted and fixed by xmux.
7117 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
7118 - If all authorities restart at once right before a consensus vote,
7119 nobody will vote about "Running", and clients will get a consensus
7120 with no usable relays. Instead, authorities refuse to build a
7121 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
7122 - If your relay can't keep up with the number of incoming create
7123 cells, it would log one warning per failure into your logs. Limit
7124 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
7125 - Bridges now use "reject *:*" as their default exit policy. Bugfix
7126 on 0.2.0.3-alpha; fixes bug 1113.
7127 - Fix a memory leak on directory authorities during voting that was
7128 introduced in 0.2.2.1-alpha. Found via valgrind.
7131 Changes in version 0.2.1.20 - 2009-10-15
7132 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
7133 services at once, prepares for more performance improvements, and
7134 fixes a bunch of smaller bugs.
7136 The Windows and OS X bundles also include a more recent Vidalia,
7137 and switch from Privoxy to Polipo.
7139 The OS X installers are now drag and drop. It's best to un-install
7140 Tor/Vidalia and then install this new bundle, rather than upgrade. If
7141 you want to upgrade, you'll need to update the paths for Tor and Polipo
7142 in the Vidalia Settings window.
7145 - Send circuit or stream sendme cells when our window has decreased
7146 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7147 by Karsten when testing the "reduce circuit window" performance
7148 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7149 before the release of Tor 0.0.0. This is the new winner of the
7151 - Fix a remotely triggerable memory leak when a consensus document
7152 contains more than one signature from the same voter. Bugfix on
7154 - Avoid segfault in rare cases when finishing an introduction circuit
7155 as a client and finding out that we don't have an introduction key
7156 for it. Fixes bug 1073. Reported by Aaron Swartz.
7159 - Tor now reads the "circwindow" parameter out of the consensus,
7160 and uses that value for its circuit package window rather than the
7161 default of 1000 cells. Begins the implementation of proposal 168.
7163 o New directory authorities:
7164 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7166 - Move moria1 and tonga to alternate IP addresses.
7169 - Fix a signed/unsigned compile warning in 0.2.1.19.
7170 - Fix possible segmentation fault on directory authorities. Bugfix on
7172 - Fix an extremely rare infinite recursion bug that could occur if
7173 we tried to log a message after shutting down the log subsystem.
7174 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
7175 - Fix an obscure bug where hidden services on 64-bit big-endian
7176 systems might mis-read the timestamp in v3 introduce cells, and
7177 refuse to connect back to the client. Discovered by "rotor".
7178 Bugfix on 0.2.1.6-alpha.
7179 - We were triggering a CLOCK_SKEW controller status event whenever
7180 we connect via the v2 connection protocol to any relay that has
7181 a wrong clock. Instead, we should only inform the controller when
7182 it's a trusted authority that claims our clock is wrong. Bugfix
7183 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7184 - We were telling the controller about CHECKING_REACHABILITY and
7185 REACHABILITY_FAILED status events whenever we launch a testing
7186 circuit or notice that one has failed. Instead, only tell the
7187 controller when we want to inform the user of overall success or
7188 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7190 - Don't warn when we're using a circuit that ends with a node
7191 excluded in ExcludeExitNodes, but the circuit is not used to access
7192 the outside world. This should help fix bug 1090. Bugfix on
7194 - Work around a small memory leak in some versions of OpenSSL that
7195 stopped the memory used by the hostname TLS extension from being
7199 - Add a "getinfo status/accepted-server-descriptor" controller
7200 command, which is the recommended way for controllers to learn
7201 whether our server descriptor has been successfully received by at
7202 least on directory authority. Un-recommend good-server-descriptor
7203 getinfo and status events until we have a better design for them.
7206 Changes in version 0.2.2.5-alpha - 2009-10-11
7207 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
7210 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
7212 o Directory authorities:
7213 - Temporarily (just for this release) move dizum to an alternate
7217 Changes in version 0.2.2.4-alpha - 2009-10-10
7218 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
7219 introduces a new unit test framework, shifts directry authority
7220 addresses around to reduce the impact from recent blocking events,
7221 and fixes a few smaller bugs.
7224 - Fix several more asserts in the circuit_build_times code, for
7225 example one that causes Tor to fail to start once we have
7226 accumulated 5000 build times in the state file. Bugfixes on
7227 0.2.2.2-alpha; fixes bug 1108.
7229 o New directory authorities:
7230 - Move moria1 and Tonga to alternate IP addresses.
7233 - Log SSL state transitions at debug level during handshake, and
7234 include SSL states in error messages. This may help debug future
7235 SSL handshake issues.
7236 - Add a new "Handshake" log domain for activities that happen
7237 during the TLS handshake.
7238 - Revert to the "June 3 2009" ip-to-country file. The September one
7239 seems to have removed most US IP addresses.
7240 - Directory authorities now reject Tor relays with versions less than
7241 0.1.2.14. This step cuts out four relays from the current network,
7242 none of which are very big.
7245 - Fix a couple of smaller issues with gathering statistics. Bugfixes
7247 - Fix two memory leaks in the error case of
7248 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
7249 - Don't count one-hop circuits when we're estimating how long it
7250 takes circuits to build on average. Otherwise we'll set our circuit
7251 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
7252 - Directory authorities no longer change their opinion of, or vote on,
7253 whether a router is Running, unless they have themselves been
7254 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
7257 o Code simplifications and refactoring:
7258 - Revise our unit tests to use the "tinytest" framework, so we
7259 can run tests in their own processes, have smarter setup/teardown
7260 code, and so on. The unit test code has moved to its own
7261 subdirectory, and has been split into multiple modules.
7264 Changes in version 0.2.2.3-alpha - 2009-09-23
7265 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
7268 - Fix an overzealous assert in our new circuit build timeout code.
7269 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
7272 - If the networkstatus consensus tells us that we should use a
7273 negative circuit package window, ignore it. Otherwise we'll
7274 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
7277 Changes in version 0.2.2.2-alpha - 2009-09-21
7278 Tor 0.2.2.2-alpha introduces our latest performance improvement for
7279 clients: Tor tracks the average time it takes to build a circuit, and
7280 avoids using circuits that take too long to build. For fast connections,
7281 this feature can cut your expected latency in half. For slow or flaky
7282 connections, it could ruin your Tor experience. Let us know if it does!
7285 - Tor now tracks how long it takes to build client-side circuits
7286 over time, and adapts its timeout to local network performance.
7287 Since a circuit that takes a long time to build will also provide
7288 bad performance, we get significant latency improvements by
7289 discarding the slowest 20% of circuits. Specifically, Tor creates
7290 circuits more aggressively than usual until it has enough data
7291 points for a good timeout estimate. Implements proposal 151.
7292 We are especially looking for reports (good and bad) from users with
7293 both EDGE and broadband connections that can move from broadband
7294 to EDGE and find out if the build-time data in the .tor/state gets
7295 reset without loss of Tor usability. You should also see a notice
7296 log message telling you that Tor has reset its timeout.
7297 - Directory authorities can now vote on arbitary integer values as
7298 part of the consensus process. This is designed to help set
7299 network-wide parameters. Implements proposal 167.
7300 - Tor now reads the "circwindow" parameter out of the consensus,
7301 and uses that value for its circuit package window rather than the
7302 default of 1000 cells. Begins the implementation of proposal 168.
7305 - Fix a remotely triggerable memory leak when a consensus document
7306 contains more than one signature from the same voter. Bugfix on
7310 - Fix an extremely rare infinite recursion bug that could occur if
7311 we tried to log a message after shutting down the log subsystem.
7312 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
7313 - Fix parsing for memory or time units given without a space between
7314 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
7315 - A networkstatus vote must contain exactly one signature. Spec
7316 conformance issue. Bugfix on 0.2.0.3-alpha.
7317 - Fix an obscure bug where hidden services on 64-bit big-endian
7318 systems might mis-read the timestamp in v3 introduce cells, and
7319 refuse to connect back to the client. Discovered by "rotor".
7320 Bugfix on 0.2.1.6-alpha.
7321 - We were triggering a CLOCK_SKEW controller status event whenever
7322 we connect via the v2 connection protocol to any relay that has
7323 a wrong clock. Instead, we should only inform the controller when
7324 it's a trusted authority that claims our clock is wrong. Bugfix
7325 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
7326 - We were telling the controller about CHECKING_REACHABILITY and
7327 REACHABILITY_FAILED status events whenever we launch a testing
7328 circuit or notice that one has failed. Instead, only tell the
7329 controller when we want to inform the user of overall success or
7330 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
7332 - Don't warn when we're using a circuit that ends with a node
7333 excluded in ExcludeExitNodes, but the circuit is not used to access
7334 the outside world. This should help fix bug 1090, but more problems
7335 remain. Bugfix on 0.2.1.6-alpha.
7336 - Work around a small memory leak in some versions of OpenSSL that
7337 stopped the memory used by the hostname TLS extension from being
7339 - Make our 'torify' script more portable; if we have only one of
7340 'torsocks' or 'tsocks' installed, don't complain to the user;
7341 and explain our warning about tsocks better.
7344 - Add a "getinfo status/accepted-server-descriptor" controller
7345 command, which is the recommended way for controllers to learn
7346 whether our server descriptor has been successfully received by at
7347 least on directory authority. Un-recommend good-server-descriptor
7348 getinfo and status events until we have a better design for them.
7349 - Update to the "September 4 2009" ip-to-country file.
7352 Changes in version 0.2.2.1-alpha - 2009-08-26
7353 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
7354 Tor clients to bootstrap on networks where only port 80 is reachable,
7355 makes it more straightforward to support hardware crypto accelerators,
7356 and starts the groundwork for gathering stats safely at relays.
7359 - Start the process of disabling ".exit" address notation, since it
7360 can be used for a variety of esoteric application-level attacks
7361 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
7364 o New directory authorities:
7365 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
7369 - New AccelName and AccelDir options add support for dynamic OpenSSL
7370 hardware crypto acceleration engines.
7371 - Tor now supports tunneling all of its outgoing connections over
7372 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
7373 configuration options. Code by Christopher Davis.
7376 - Send circuit or stream sendme cells when our window has decreased
7377 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
7378 by Karsten when testing the "reduce circuit window" performance
7379 patch. Bugfix on the 54th commit on Tor -- from July 2002,
7380 before the release of Tor 0.0.0. This is the new winner of the
7383 o New options for gathering stats safely:
7384 - Directory mirrors that set "DirReqStatistics 1" write statistics
7385 about directory requests to disk every 24 hours. As compared to the
7386 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
7387 1) stats are written to disk exactly every 24 hours; 2) estimated
7388 shares of v2 and v3 requests are determined as mean values, not at
7389 the end of a measurement period; 3) unresolved requests are listed
7390 with country code '??'; 4) directories also measure download times.
7391 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
7392 number of exit streams and transferred bytes per port to disk every
7394 - Relays that set "CellStatistics 1" write statistics on how long
7395 cells spend in their circuit queues to disk every 24 hours.
7396 - Entry nodes that set "EntryStatistics 1" write statistics on the
7397 rough number and origins of connecting clients to disk every 24
7399 - Relays that write any of the above statistics to disk and set
7400 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
7401 their extra-info documents.
7404 - New --digests command-line switch to output the digests of the
7405 source files Tor was built with.
7406 - The "torify" script now uses torsocks where available.
7407 - The memarea code now uses a sentinel value at the end of each area
7408 to make sure nothing writes beyond the end of an area. This might
7409 help debug some conceivable causes of bug 930.
7410 - Time and memory units in the configuration file can now be set to
7411 fractional units. For example, "2.5 GB" is now a valid value for
7413 - Certain Tor clients (such as those behind check.torproject.org) may
7414 want to fetch the consensus in an extra early manner. To enable this
7415 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
7416 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
7417 as only certain clients who must have this information sooner should
7419 - Instead of adding the svn revision to the Tor version string, report
7420 the git commit (when we're building from a git checkout).
7423 - If any of the v3 certs we download are unparseable, we should
7424 actually notice the failure so we don't retry indefinitely. Bugfix
7425 on 0.2.0.x; reported by "rotator".
7426 - If the cached cert file is unparseable, warn but don't exit.
7427 - Fix possible segmentation fault on directory authorities. Bugfix on
7429 - When Tor fails to parse a descriptor of any kind, dump it to disk.
7430 Might help diagnosing bug 1051.
7432 o Deprecated and removed features:
7433 - The controller no longer accepts the old obsolete "addr-mappings/"
7434 or "unregistered-servers-" GETINFO values.
7435 - Hidden services no longer publish version 0 descriptors, and clients
7436 do not request or use version 0 descriptors. However, the old hidden
7437 service authorities still accept and serve version 0 descriptors
7438 when contacted by older hidden services/clients.
7439 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
7440 always on; using them is necessary for correct forward-compatible
7442 - Remove support for .noconnect style addresses. Nobody was using
7443 them, and they provided another avenue for detecting Tor users
7444 via application-level web tricks.
7446 o Packaging changes:
7447 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
7448 installer bundles. See
7449 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
7450 for details of what's new in Vidalia 0.2.3.
7451 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
7452 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
7453 configuration file, rather than the old Privoxy.
7454 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
7455 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
7456 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
7457 better compatibility with OS X 10.6, aka Snow Leopard.
7458 - OS X Vidalia Bundle: The multi-package installer is now replaced
7459 by a simple drag and drop to the /Applications folder. This change
7460 occurred with the upgrade to Vidalia 0.2.3.
7463 Changes in version 0.2.1.19 - 2009-07-28
7464 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
7465 services on Tor 0.2.1.3-alpha through 0.2.1.18.
7468 - Make accessing hidden services on 0.2.1.x work right again.
7469 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
7470 part of patch provided by "optimist".
7473 - When a relay/bridge is writing out its identity key fingerprint to
7474 the "fingerprint" file and to its logs, write it without spaces. Now
7475 it will look like the fingerprints in our bridges documentation,
7476 and confuse fewer users.
7479 - Relays no longer publish a new server descriptor if they change
7480 their MaxAdvertisedBandwidth config option but it doesn't end up
7481 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
7482 fixes bug 1026. Patch from Sebastian.
7483 - Avoid leaking memory every time we get a create cell but we have
7484 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
7485 fixes bug 1034. Reported by BarkerJr.
7488 Changes in version 0.2.1.18 - 2009-07-24
7489 Tor 0.2.1.18 lays the foundations for performance improvements,
7490 adds status events to help users diagnose bootstrap problems, adds
7491 optional authentication/authorization for hidden services, fixes a
7492 variety of potential anonymity problems, and includes a huge pile of
7493 other features and bug fixes.
7496 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
7499 Changes in version 0.2.1.17-rc - 2009-07-07
7500 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
7501 candidate for the 0.2.1.x series. It lays the groundwork for further
7502 client performance improvements, and also fixes a big bug with directory
7503 authorities that were causing them to assign Guard and Stable flags
7506 The Windows bundles also finally include the geoip database that we
7507 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
7508 should actually install Torbutton rather than giving you a cryptic
7509 failure message (oops).
7512 - Clients now use the bandwidth values in the consensus, rather than
7513 the bandwidth values in each relay descriptor. This approach opens
7514 the door to more accurate bandwidth estimates once the directory
7515 authorities start doing active measurements. Implements more of
7519 - When Tor clients restart after 1-5 days, they discard all their
7520 cached descriptors as too old, but they still use the cached
7521 consensus document. This approach is good for robustness, but
7522 bad for performance: since they don't know any bandwidths, they
7523 end up choosing at random rather than weighting their choice by
7524 speed. Fixed by the above feature of putting bandwidths in the
7525 consensus. Bugfix on 0.2.0.x.
7526 - Directory authorities were neglecting to mark relays down in their
7527 internal histories if the relays fall off the routerlist without
7528 ever being found unreachable. So there were relays in the histories
7529 that haven't been seen for eight months, and are listed as being
7530 up for eight months. This wreaked havoc on the "median wfu"
7531 and "median mtbf" calculations, in turn making Guard and Stable
7532 flags very wrong, hurting network performance. Fixes bugs 696 and
7533 969. Bugfix on 0.2.0.6-alpha.
7536 - Serve the DirPortFrontPage page even when we have been approaching
7537 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
7538 - The control port would close the connection before flushing long
7539 replies, such as the network consensus, if a QUIT command was issued
7540 before the reply had completed. Now, the control port flushes all
7541 pending replies before closing the connection. Also fixed a spurious
7542 warning when a QUIT command is issued after a malformed or rejected
7543 AUTHENTICATE command, but before the connection was closed. Patch
7544 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
7545 - When we can't find an intro key for a v2 hidden service descriptor,
7546 fall back to the v0 hidden service descriptor and log a bug message.
7547 Workaround for bug 1024.
7548 - Fix a log message that did not respect the SafeLogging option.
7552 - If we're a relay and we change our IP address, be more verbose
7553 about the reason that made us change. Should help track down
7554 further bugs for relays on dynamic IP addresses.
7557 Changes in version 0.2.0.35 - 2009-06-24
7559 - Avoid crashing in the presence of certain malformed descriptors.
7560 Found by lark, and by automated fuzzing.
7561 - Fix an edge case where a malicious exit relay could convince a
7562 controller that the client's DNS question resolves to an internal IP
7563 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7566 - Finally fix the bug where dynamic-IP relays disappear when their
7567 IP address changes: directory mirrors were mistakenly telling
7568 them their old address if they asked via begin_dir, so they
7569 never got an accurate answer about their new address, so they
7570 just vanished after a day. For belt-and-suspenders, relays that
7571 don't set Address in their config now avoid using begin_dir for
7572 all direct connections. Should fix bugs 827, 883, and 900.
7573 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7574 that would occur on some exit nodes when DNS failures and timeouts
7575 occurred in certain patterns. Fix for bug 957.
7578 - When starting with a cache over a few days old, do not leak
7579 memory for the obsolete router descriptors in it. Bugfix on
7580 0.2.0.33; fixes bug 672.
7581 - Hidden service clients didn't use a cached service descriptor that
7582 was older than 15 minutes, but wouldn't fetch a new one either,
7583 because there was already one in the cache. Now, fetch a v2
7584 descriptor unless the same descriptor was added to the cache within
7585 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7588 Changes in version 0.2.1.16-rc - 2009-06-20
7589 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
7590 a bunch of minor bugs.
7593 - Fix an edge case where a malicious exit relay could convince a
7594 controller that the client's DNS question resolves to an internal IP
7595 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
7597 o Major performance improvements (on 0.2.0.x):
7598 - Disable and refactor some debugging checks that forced a linear scan
7599 over the whole server-side DNS cache. These accounted for over 50%
7600 of CPU time on a relatively busy exit node's gprof profile. Found
7602 - Disable some debugging checks that appeared in exit node profile
7606 - Update to the "June 3 2009" ip-to-country file.
7607 - Do not have tor-resolve automatically refuse all .onion addresses;
7608 if AutomapHostsOnResolve is set in your torrc, this will work fine.
7610 o Minor bugfixes (on 0.2.0.x):
7611 - Log correct error messages for DNS-related network errors on
7613 - Fix a race condition that could cause crashes or memory corruption
7614 when running as a server with a controller listening for log
7616 - Avoid crashing when we have a policy specified in a DirPolicy or
7617 SocksPolicy or ReachableAddresses option with ports set on it,
7618 and we re-load the policy. May fix bug 996.
7619 - Hidden service clients didn't use a cached service descriptor that
7620 was older than 15 minutes, but wouldn't fetch a new one either,
7621 because there was already one in the cache. Now, fetch a v2
7622 descriptor unless the same descriptor was added to the cache within
7623 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
7625 o Minor bugfixes (on 0.2.1.x):
7626 - Don't warn users about low port and hibernation mix when they
7627 provide a *ListenAddress directive to fix that. Bugfix on
7629 - When switching back and forth between bridge mode, do not start
7630 gathering GeoIP data until two hours have passed.
7631 - Do not complain that the user has requested an excluded node as
7632 an exit when the node is not really an exit. This could happen
7633 because the circuit was for testing, or an introduction point.
7637 Changes in version 0.2.1.15-rc - 2009-05-25
7638 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
7639 series. It fixes a major bug on fast exit relays, as well as a variety
7642 o Major bugfixes (on 0.2.0.x):
7643 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
7644 that would occur on some exit nodes when DNS failures and timeouts
7645 occurred in certain patterns. Fix for bug 957.
7647 o Minor bugfixes (on 0.2.0.x):
7648 - Actually return -1 in the error case for read_bandwidth_usage().
7649 Harmless bug, since we currently don't care about the return value
7650 anywhere. Bugfix on 0.2.0.9-alpha.
7651 - Provide a more useful log message if bug 977 (related to buffer
7652 freelists) ever reappears, and do not crash right away.
7653 - Fix an assertion failure on 64-bit platforms when we allocated
7654 memory right up to the end of a memarea, then realigned the memory
7655 one step beyond the end. Fixes a possible cause of bug 930.
7656 - Protect the count of open sockets with a mutex, so we can't
7657 corrupt it when two threads are closing or opening sockets at once.
7658 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
7659 - Don't allow a bridge to publish its router descriptor to a
7660 non-bridge directory authority. Fixes part of bug 932.
7661 - When we change to or from being a bridge, reset our counts of
7662 client usage by country. Fixes bug 932.
7663 - Fix a bug that made stream bandwidth get misreported to the
7665 - Stop using malloc_usable_size() to use more area than we had
7666 actually allocated: it was safe, but made valgrind really unhappy.
7667 - Fix a memory leak when v3 directory authorities load their keys
7668 and cert from disk. Bugfix on 0.2.0.1-alpha.
7670 o Minor bugfixes (on 0.2.1.x):
7671 - Fix use of freed memory when deciding to mark a non-addable
7672 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
7675 Changes in version 0.2.1.14-rc - 2009-04-12
7676 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
7677 series. It begins fixing some major performance problems, and also
7678 finally addresses the bug that was causing relays on dynamic IP
7679 addresses to fall out of the directory.
7682 - Clients replace entry guards that were chosen more than a few months
7683 ago. This change should significantly improve client performance,
7684 especially once more people upgrade, since relays that have been
7685 a guard for a long time are currently overloaded.
7687 o Major bugfixes (on 0.2.0):
7688 - Finally fix the bug where dynamic-IP relays disappear when their
7689 IP address changes: directory mirrors were mistakenly telling
7690 them their old address if they asked via begin_dir, so they
7691 never got an accurate answer about their new address, so they
7692 just vanished after a day. For belt-and-suspenders, relays that
7693 don't set Address in their config now avoid using begin_dir for
7694 all direct connections. Should fix bugs 827, 883, and 900.
7695 - Relays were falling out of the networkstatus consensus for
7696 part of a day if they changed their local config but the
7697 authorities discarded their new descriptor as "not sufficiently
7698 different". Now directory authorities accept a descriptor as changed
7699 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
7701 - Avoid crashing in the presence of certain malformed descriptors.
7702 Found by lark, and by automated fuzzing.
7705 - When generating circuit events with verbose nicknames for
7706 controllers, try harder to look up nicknames for routers on a
7707 circuit. (Previously, we would look in the router descriptors we had
7708 for nicknames, but not in the consensus.) Partial fix for bug 941.
7709 - If the bridge config line doesn't specify a port, assume 443.
7710 This makes bridge lines a bit smaller and easier for users to
7712 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
7713 bytes (aka 20KB/s), to match our documentation. Also update
7714 directory authorities so they always assign the Fast flag to relays
7715 with 20KB/s of capacity. Now people running relays won't suddenly
7716 find themselves not seeing any use, if the network gets faster
7718 - Update to the "April 3 2009" ip-to-country file.
7721 - Avoid trying to print raw memory to the logs when we decide to
7722 give up on downloading a given relay descriptor. Bugfix on
7724 - In tor-resolve, when the Tor client to use is specified by
7725 <hostname>:<port>, actually use the specified port rather than
7726 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
7727 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
7728 - When starting with a cache over a few days old, do not leak
7729 memory for the obsolete router descriptors in it. Bugfix on
7731 - Avoid double-free on list of successfully uploaded hidden
7732 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
7733 - Change memarea_strndup() implementation to work even when
7734 duplicating a string at the end of a page. This bug was
7735 harmless for now, but could have meant crashes later. Fix by
7736 lark. Bugfix on 0.2.1.1-alpha.
7737 - Limit uploaded directory documents to be 16M rather than 500K.
7738 The directory authorities were refusing v3 consensus votes from
7739 other authorities, since the votes are now 504K. Fixes bug 959;
7740 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
7741 - Directory authorities should never send a 503 "busy" response to
7742 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
7746 Changes in version 0.2.1.13-alpha - 2009-03-09
7747 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
7748 cleanups. We're finally getting close to a release candidate.
7751 - Correctly update the list of which countries we exclude as
7752 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
7753 lark. Bugfix on 0.2.1.6-alpha.
7755 o Minor bugfixes (on 0.2.0.x and earlier):
7756 - Automatically detect MacOSX versions earlier than 10.4.0, and
7757 disable kqueue from inside Tor when running with these versions.
7758 We previously did this from the startup script, but that was no
7759 help to people who didn't use the startup script. Resolves bug 863.
7760 - When we had picked an exit node for a connection, but marked it as
7761 "optional", and it turned out we had no onion key for the exit,
7762 stop wanting that exit and try again. This situation may not
7763 be possible now, but will probably become feasible with proposal
7764 158. Spotted by rovv. Fixes another case of bug 752.
7765 - Clients no longer cache certificates for authorities they do not
7766 recognize. Bugfix on 0.2.0.9-alpha.
7767 - When we can't transmit a DNS request due to a network error, retry
7768 it after a while, and eventually transmit a failing response to
7769 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
7770 - If the controller claimed responsibility for a stream, but that
7771 stream never finished making its connection, it would live
7772 forever in circuit_wait state. Now we close it after SocksTimeout
7773 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
7774 - Drop begin cells to a hidden service if they come from the middle
7775 of a circuit. Patch from lark.
7776 - When we erroneously receive two EXTEND cells for the same circuit
7777 ID on the same connection, drop the second. Patch from lark.
7778 - Fix a crash that occurs on exit nodes when a nameserver request
7779 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
7780 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
7782 - Do not assume that a stack-allocated character array will be
7783 64-bit aligned on platforms that demand that uint64_t access is
7784 aligned. Possible fix for bug 604.
7785 - Parse dates and IPv4 addresses in a locale- and libc-independent
7786 manner, to avoid platform-dependent behavior on malformed input.
7787 - Build correctly when configured to build outside the main source
7788 path. Patch from Michael Gold.
7789 - We were already rejecting relay begin cells with destination port
7790 of 0. Now also reject extend cells with destination port or address
7791 of 0. Suggested by lark.
7793 o Minor bugfixes (on 0.2.1.x):
7794 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
7795 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
7796 - If we're an exit node, scrub the IP address to which we are exiting
7797 in the logs. Bugfix on 0.2.1.8-alpha.
7800 - On Linux, use the prctl call to re-enable core dumps when the user
7802 - New controller event NEWCONSENSUS that lists the networkstatus
7803 lines for every recommended relay. Now controllers like Torflow
7804 can keep up-to-date on which relays they should be using.
7805 - Update to the "February 26 2009" ip-to-country file.
7808 Changes in version 0.2.0.34 - 2009-02-08
7809 Tor 0.2.0.34 features several more security-related fixes. You should
7810 upgrade, especially if you run an exit relay (remote crash) or a
7811 directory authority (remote infinite loop), or you're on an older
7812 (pre-XP) or not-recently-patched Windows (remote exploit).
7814 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
7815 have many known flaws, and nobody should be using them. You should
7816 upgrade. If you're using a Linux or BSD and its packages are obsolete,
7817 stop using those packages and upgrade anyway.
7820 - Fix an infinite-loop bug on handling corrupt votes under certain
7821 circumstances. Bugfix on 0.2.0.8-alpha.
7822 - Fix a temporary DoS vulnerability that could be performed by
7823 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7824 - Avoid a potential crash on exit nodes when processing malformed
7825 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
7826 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
7827 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
7830 - Fix compilation on systems where time_t is a 64-bit integer.
7831 Patch from Matthias Drochner.
7832 - Don't consider expiring already-closed client connections. Fixes
7833 bug 893. Bugfix on 0.0.2pre20.
7836 Changes in version 0.2.1.12-alpha - 2009-02-08
7837 Tor 0.2.1.12-alpha features several more security-related fixes. You
7838 should upgrade, especially if you run an exit relay (remote crash) or
7839 a directory authority (remote infinite loop), or you're on an older
7840 (pre-XP) or not-recently-patched Windows (remote exploit). It also
7841 includes a big pile of minor bugfixes and cleanups.
7844 - Fix an infinite-loop bug on handling corrupt votes under certain
7845 circumstances. Bugfix on 0.2.0.8-alpha.
7846 - Fix a temporary DoS vulnerability that could be performed by
7847 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
7848 - Avoid a potential crash on exit nodes when processing malformed
7849 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
7852 - Let controllers actually ask for the "clients_seen" event for
7853 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
7854 reported by Matt Edman.
7855 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
7857 - Fix a bug in address parsing that was preventing bridges or hidden
7858 service targets from being at IPv6 addresses.
7859 - Solve a bug that kept hardware crypto acceleration from getting
7860 enabled when accounting was turned on. Fixes bug 907. Bugfix on
7862 - Remove a bash-ism from configure.in to build properly on non-Linux
7863 platforms. Bugfix on 0.2.1.1-alpha.
7864 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
7865 headers. Bugfix on 0.2.0.10-alpha.
7866 - Don't consider expiring already-closed client connections. Fixes
7867 bug 893. Bugfix on 0.0.2pre20.
7868 - Fix another interesting corner-case of bug 891 spotted by rovv:
7869 Previously, if two hosts had different amounts of clock drift, and
7870 one of them created a new connection with just the wrong timing,
7871 the other might decide to deprecate the new connection erroneously.
7872 Bugfix on 0.1.1.13-alpha.
7873 - Resolve a very rare crash bug that could occur when the user forced
7874 a nameserver reconfiguration during the middle of a nameserver
7875 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
7876 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
7877 Bugfix on 0.2.1.7-alpha.
7878 - If we're using bridges and our network goes away, be more willing
7879 to forgive our bridges and try again when we get an application
7880 request. Bugfix on 0.2.0.x.
7883 - Support platforms where time_t is 64 bits long. (Congratulations,
7884 NetBSD!) Patch from Matthias Drochner.
7885 - Add a 'getinfo status/clients-seen' controller command, in case
7886 controllers want to hear clients_seen events but connect late.
7889 - Disable GCC's strict alias optimization by default, to avoid the
7890 likelihood of its introducing subtle bugs whenever our code violates
7891 the letter of C99's alias rules.
7894 Changes in version 0.2.0.33 - 2009-01-21
7895 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
7896 useful to users. It also finally fixes a bug where a relay or client
7897 that's been off for many days would take a long time to bootstrap.
7899 This update also fixes an important security-related bug reported by
7900 Ilja van Sprundel. You should upgrade. (We'll send out more details
7901 about the bug once people have had some time to upgrade.)
7904 - Fix a heap-corruption bug that may be remotely triggerable on
7905 some platforms. Reported by Ilja van Sprundel.
7908 - When a stream at an exit relay is in state "resolving" or
7909 "connecting" and it receives an "end" relay cell, the exit relay
7910 would silently ignore the end cell and not close the stream. If
7911 the client never closes the circuit, then the exit relay never
7912 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
7914 - When sending CREATED cells back for a given circuit, use a 64-bit
7915 connection ID to find the right connection, rather than an addr:port
7916 combination. Now that we can have multiple OR connections between
7917 the same ORs, it is no longer possible to use addr:port to uniquely
7918 identify a connection.
7919 - Bridge relays that had DirPort set to 0 would stop fetching
7920 descriptors shortly after startup, and then briefly resume
7921 after a new bandwidth test and/or after publishing a new bridge
7922 descriptor. Bridge users that try to bootstrap from them would
7923 get a recent networkstatus but would get descriptors from up to
7924 18 hours earlier, meaning most of the descriptors were obsolete
7925 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
7926 - Prevent bridge relays from serving their 'extrainfo' document
7927 to anybody who asks, now that extrainfo docs include potentially
7928 sensitive aggregated client geoip summaries. Bugfix on
7930 - If the cached networkstatus consensus is more than five days old,
7931 discard it rather than trying to use it. In theory it could be
7932 useful because it lists alternate directory mirrors, but in practice
7933 it just means we spend many minutes trying directory mirrors that
7934 are long gone from the network. Also discard router descriptors as
7935 we load them if they are more than five days old, since the onion
7936 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
7939 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
7940 could make gcc generate non-functional binary search code. Bugfix
7942 - Build correctly on platforms without socklen_t.
7943 - Compile without warnings on solaris.
7944 - Avoid potential crash on internal error during signature collection.
7945 Fixes bug 864. Patch from rovv.
7946 - Correct handling of possible malformed authority signing key
7947 certificates with internal signature types. Fixes bug 880.
7948 Bugfix on 0.2.0.3-alpha.
7949 - Fix a hard-to-trigger resource leak when logging credential status.
7951 - When we can't initialize DNS because the network is down, do not
7952 automatically stop Tor from starting. Instead, we retry failed
7953 dns_init() every 10 minutes, and change the exit policy to reject
7954 *:* until one succeeds. Fixes bug 691.
7955 - Use 64 bits instead of 32 bits for connection identifiers used with
7956 the controller protocol, to greatly reduce risk of identifier reuse.
7957 - When we're choosing an exit node for a circuit, and we have
7958 no pending streams, choose a good general exit rather than one that
7959 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
7960 - Fix another case of assuming, when a specific exit is requested,
7961 that we know more than the user about what hosts it allows.
7962 Fixes one case of bug 752. Patch from rovv.
7963 - Clip the MaxCircuitDirtiness config option to a minimum of 10
7964 seconds. Warn the user if lower values are given in the
7965 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
7966 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
7967 user if lower values are given in the configuration. Bugfix on
7968 0.1.1.17-rc. Patch by Sebastian.
7969 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
7970 the cache because we already had a v0 descriptor with the same ID.
7971 Bugfix on 0.2.0.18-alpha.
7972 - Fix a race condition when freeing keys shared between main thread
7973 and CPU workers that could result in a memory leak. Bugfix on
7974 0.1.0.1-rc. Fixes bug 889.
7975 - Send a valid END cell back when a client tries to connect to a
7976 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
7977 840. Patch from rovv.
7978 - Check which hops rendezvous stream cells are associated with to
7979 prevent possible guess-the-streamid injection attacks from
7980 intermediate hops. Fixes another case of bug 446. Based on patch
7982 - If a broken client asks a non-exit router to connect somewhere,
7983 do not even do the DNS lookup before rejecting the connection.
7984 Fixes another case of bug 619. Patch from rovv.
7985 - When a relay gets a create cell it can't decrypt (e.g. because it's
7986 using the wrong onion key), we were dropping it and letting the
7987 client time out. Now actually answer with a destroy cell. Fixes
7988 bug 904. Bugfix on 0.0.2pre8.
7990 o Minor bugfixes (hidden services):
7991 - Do not throw away existing introduction points on SIGHUP. Bugfix on
7992 0.0.6pre1. Patch by Karsten. Fixes bug 874.
7995 - Report the case where all signatures in a detached set are rejected
7996 differently than the case where there is an error handling the
7998 - When we realize that another process has modified our cached
7999 descriptors, print out a more useful error message rather than
8000 triggering an assertion. Fixes bug 885. Patch from Karsten.
8001 - Implement the 0x20 hack to better resist DNS poisoning: set the
8002 case on outgoing DNS requests randomly, and reject responses that do
8003 not match the case correctly. This logic can be disabled with the
8004 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
8005 of servers that do not reliably preserve case in replies. See
8006 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8008 - Check DNS replies for more matching fields to better resist DNS
8010 - Never use OpenSSL compression: it wastes RAM and CPU trying to
8011 compress cells, which are basically all encrypted, compressed, or
8015 Changes in version 0.2.1.11-alpha - 2009-01-20
8016 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
8017 week it will take a long time to bootstrap again" bug. It also fixes
8018 an important security-related bug reported by Ilja van Sprundel. You
8019 should upgrade. (We'll send out more details about the bug once people
8020 have had some time to upgrade.)
8023 - Fix a heap-corruption bug that may be remotely triggerable on
8024 some platforms. Reported by Ilja van Sprundel.
8027 - Discard router descriptors as we load them if they are more than
8028 five days old. Otherwise if Tor is off for a long time and then
8029 starts with cached descriptors, it will try to use the onion
8030 keys in those obsolete descriptors when building circuits. Bugfix
8031 on 0.2.0.x. Fixes bug 887.
8034 - Try to make sure that the version of Libevent we're running with
8035 is binary-compatible with the one we built with. May address bug
8037 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
8038 for bug 905. Bugfix on 0.2.1.7-alpha.
8039 - Add a new --enable-local-appdata configuration switch to change
8040 the default location of the datadir on win32 from APPDATA to
8041 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
8042 entirely. Patch from coderman.
8045 - Make outbound DNS packets respect the OutboundBindAddress setting.
8046 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
8047 - When our circuit fails at the first hop (e.g. we get a destroy
8048 cell back), avoid using that OR connection anymore, and also
8049 tell all the one-hop directory requests waiting for it that they
8050 should fail. Bugfix on 0.2.1.3-alpha.
8051 - In the torify(1) manpage, mention that tsocks will leak your
8055 Changes in version 0.2.1.10-alpha - 2009-01-06
8056 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
8057 would make the bridge relay not so useful if it had DirPort set to 0,
8058 and one that could let an attacker learn a little bit of information
8059 about the bridge's users), and a bug that would cause your Tor relay
8060 to ignore a circuit create request it can't decrypt (rather than reply
8061 with an error). It also fixes a wide variety of other bugs.
8064 - If the cached networkstatus consensus is more than five days old,
8065 discard it rather than trying to use it. In theory it could
8066 be useful because it lists alternate directory mirrors, but in
8067 practice it just means we spend many minutes trying directory
8068 mirrors that are long gone from the network. Helps bug 887 a bit;
8070 - Bridge relays that had DirPort set to 0 would stop fetching
8071 descriptors shortly after startup, and then briefly resume
8072 after a new bandwidth test and/or after publishing a new bridge
8073 descriptor. Bridge users that try to bootstrap from them would
8074 get a recent networkstatus but would get descriptors from up to
8075 18 hours earlier, meaning most of the descriptors were obsolete
8076 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
8077 - Prevent bridge relays from serving their 'extrainfo' document
8078 to anybody who asks, now that extrainfo docs include potentially
8079 sensitive aggregated client geoip summaries. Bugfix on
8083 - New controller event "clients_seen" to report a geoip-based summary
8084 of which countries we've seen clients from recently. Now controllers
8085 like Vidalia can show bridge operators that they're actually making
8087 - Build correctly against versions of OpenSSL 0.9.8 or later built
8088 without support for deprecated functions.
8089 - Update to the "December 19 2008" ip-to-country file.
8091 o Minor bugfixes (on 0.2.0.x):
8092 - Authorities now vote for the Stable flag for any router whose
8093 weighted MTBF is at least 5 days, regardless of the mean MTBF.
8094 - Do not remove routers as too old if we do not have any consensus
8095 document. Bugfix on 0.2.0.7-alpha.
8096 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
8097 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
8098 - When an exit relay resolves a stream address to a local IP address,
8099 do not just keep retrying that same exit relay over and
8100 over. Instead, just close the stream. Addresses bug 872. Bugfix
8101 on 0.2.0.32. Patch from rovv.
8102 - If a hidden service sends us an END cell, do not consider
8103 retrying the connection; just close it. Patch from rovv.
8104 - When we made bridge authorities stop serving bridge descriptors over
8105 unencrypted links, we also broke DirPort reachability testing for
8106 bridges. So bridges with a non-zero DirPort were printing spurious
8107 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
8108 - When a relay gets a create cell it can't decrypt (e.g. because it's
8109 using the wrong onion key), we were dropping it and letting the
8110 client time out. Now actually answer with a destroy cell. Fixes
8111 bug 904. Bugfix on 0.0.2pre8.
8112 - Squeeze 2-5% out of client performance (according to oprofile) by
8113 improving the implementation of some policy-manipulation functions.
8115 o Minor bugfixes (on 0.2.1.x):
8116 - Make get_interface_address() function work properly again; stop
8117 guessing the wrong parts of our address as our address.
8118 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
8119 send on that circuit. Otherwise we might violate the proposal-110
8120 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
8122 - When we're sending non-EXTEND cells to the first hop in a circuit,
8123 for example to use an encrypted directory connection, we don't need
8124 to use RELAY_EARLY cells: the first hop knows what kind of cell
8125 it is, and nobody else can even see the cell type. Conserving
8126 RELAY_EARLY cells makes it easier to cannibalize circuits like
8128 - Stop logging nameserver addresses in reverse order.
8129 - If we are retrying a directory download slowly over and over, do
8130 not automatically give up after the 254th failure. Bugfix on
8132 - Resume reporting accurate "stream end" reasons to the local control
8133 port. They were lost in the changes for Proposal 148. Bugfix on
8136 o Deprecated and removed features:
8137 - The old "tor --version --version" command, which would print out
8138 the subversion "Id" of most of the source files, is now removed. It
8139 turned out to be less useful than we'd expected, and harder to
8142 o Code simplifications and refactoring:
8143 - Change our header file guard macros to be less likely to conflict
8144 with system headers. Adam Langley noticed that we were conflicting
8145 with log.h on Android.
8146 - Tool-assisted documentation cleanup. Nearly every function or
8147 static variable in Tor should have its own documentation now.
8150 Changes in version 0.2.1.9-alpha - 2008-12-25
8151 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
8153 o New directory authorities:
8154 - gabelmoo (the authority run by Karsten Loesing) now has a new
8158 - Never use a connection with a mismatched address to extend a
8159 circuit, unless that connection is canonical. A canonical
8160 connection is one whose address is authenticated by the router's
8161 identity key, either in a NETINFO cell or in a router descriptor.
8162 - Avoid a possible memory corruption bug when receiving hidden service
8163 descriptors. Bugfix on 0.2.1.6-alpha.
8166 - Fix a logic error that would automatically reject all but the first
8167 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
8168 part of bug 813/868. Bug spotted by coderman.
8169 - When a stream at an exit relay is in state "resolving" or
8170 "connecting" and it receives an "end" relay cell, the exit relay
8171 would silently ignore the end cell and not close the stream. If
8172 the client never closes the circuit, then the exit relay never
8173 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
8175 - When we can't initialize DNS because the network is down, do not
8176 automatically stop Tor from starting. Instead, retry failed
8177 dns_init() every 10 minutes, and change the exit policy to reject
8178 *:* until one succeeds. Fixes bug 691.
8181 - Give a better error message when an overzealous init script says
8182 "sudo -u username tor --user username". Makes Bug 882 easier for
8184 - When a directory authority gives us a new guess for our IP address,
8185 log which authority we used. Hopefully this will help us debug
8186 the recent complaints about bad IP address guesses.
8187 - Detect svn revision properly when we're using git-svn.
8188 - Try not to open more than one descriptor-downloading connection
8189 to an authority at once. This should reduce load on directory
8190 authorities. Fixes bug 366.
8191 - Add cross-certification to newly generated certificates, so that
8192 a signing key is enough information to look up a certificate.
8193 Partial implementation of proposal 157.
8194 - Start serving certificates by <identity digest, signing key digest>
8195 pairs. Partial implementation of proposal 157.
8196 - Clients now never report any stream end reason except 'MISC'.
8197 Implements proposal 148.
8198 - On platforms with a maximum syslog string length, truncate syslog
8199 messages to that length ourselves, rather than relying on the
8200 system to do it for us.
8201 - Optimize out calls to time(NULL) that occur for every IO operation,
8202 or for every cell. On systems where time() is a slow syscall,
8203 this fix will be slightly helpful.
8204 - Exit servers can now answer resolve requests for ip6.arpa addresses.
8205 - When we download a descriptor that we then immediately (as
8206 a directory authority) reject, do not retry downloading it right
8207 away. Should save some bandwidth on authorities. Fix for bug
8208 888. Patch by Sebastian Hahn.
8209 - When a download gets us zero good descriptors, do not notify
8210 Tor that new directory information has arrived.
8211 - Avoid some nasty corner cases in the logic for marking connections
8212 as too old or obsolete or noncanonical for circuits. Partial
8215 o Minor features (controller):
8216 - New CONSENSUS_ARRIVED event to note when a new consensus has
8217 been fetched and validated.
8218 - When we realize that another process has modified our cached
8219 descriptors file, print out a more useful error message rather
8220 than triggering an assertion. Fixes bug 885. Patch from Karsten.
8221 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
8222 controllers to prevent SIGHUP from reloading the
8223 configuration. Fixes bug 856.
8226 - Resume using the correct "REASON=" stream when telling the
8227 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
8228 - When a canonical connection appears later in our internal list
8229 than a noncanonical one for a given OR ID, always use the
8230 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
8232 - Clip the MaxCircuitDirtiness config option to a minimum of 10
8233 seconds. Warn the user if lower values are given in the
8234 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
8235 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
8236 user if lower values are given in the configuration. Bugfix on
8237 0.1.1.17-rc. Patch by Sebastian.
8238 - Fix a race condition when freeing keys shared between main thread
8239 and CPU workers that could result in a memory leak. Bugfix on
8240 0.1.0.1-rc. Fixes bug 889.
8242 o Minor bugfixes (hidden services):
8243 - Do not throw away existing introduction points on SIGHUP (bugfix on
8244 0.0.6pre1); also, do not stall hidden services because we're
8245 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
8246 by John Brooks. Patch by Karsten. Fixes bug 874.
8247 - Fix a memory leak when we decline to add a v2 rendezvous
8248 descriptor to the cache because we already had a v0 descriptor
8249 with the same ID. Bugfix on 0.2.0.18-alpha.
8251 o Deprecated and removed features:
8252 - RedirectExits has been removed. It was deprecated since
8254 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
8255 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
8256 - Cell pools are now always enabled; --disable-cell-pools is ignored.
8258 o Code simplifications and refactoring:
8259 - Rename the confusing or_is_obsolete field to the more appropriate
8260 is_bad_for_new_circs, and move it to or_connection_t where it
8262 - Move edge-only flags from connection_t to edge_connection_t: not
8263 only is this better coding, but on machines of plausible alignment,
8264 it should save 4-8 bytes per connection_t. "Every little bit helps."
8265 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
8266 for consistency; keep old option working for backward compatibility.
8267 - Simplify the code for finding connections to use for a circuit.
8270 Changes in version 0.2.1.8-alpha - 2008-12-08
8271 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
8272 builds better on unusual platforms like Solaris and old OS X, and
8273 fixes a variety of other issues.
8276 - New DirPortFrontPage option that takes an html file and publishes
8277 it as "/" on the DirPort. Now relay operators can provide a
8278 disclaimer without needing to set up a separate webserver. There's
8279 a sample disclaimer in contrib/tor-exit-notice.html.
8282 - When the client is choosing entry guards, now it selects at most
8283 one guard from a given relay family. Otherwise we could end up with
8284 all of our entry points into the network run by the same operator.
8285 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
8288 - Fix a DOS opportunity during the voting signature collection process
8289 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8290 - Fix a possible segfault when establishing an exit connection. Bugfix
8294 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
8296 - Made Tor a little less aggressive about deleting expired
8297 certificates. Partial fix for bug 854.
8298 - Stop doing unaligned memory access that generated bus errors on
8299 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
8300 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
8301 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
8302 - Make USR2 log-level switch take effect immediately. Bugfix on
8304 - If one win32 nameserver fails to get added, continue adding the
8305 rest, and don't automatically fail.
8306 - Use fcntl() for locking when flock() is not available. Should fix
8307 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
8308 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
8309 could make gcc generate non-functional binary search code. Bugfix
8311 - Build correctly on platforms without socklen_t.
8312 - Avoid potential crash on internal error during signature collection.
8313 Fixes bug 864. Patch from rovv.
8314 - Do not use C's stdio library for writing to log files. This will
8315 improve logging performance by a minute amount, and will stop
8316 leaking fds when our disk is full. Fixes bug 861.
8317 - Stop erroneous use of O_APPEND in cases where we did not in fact
8318 want to re-seek to the end of a file before every last write().
8319 - Correct handling of possible malformed authority signing key
8320 certificates with internal signature types. Fixes bug 880. Bugfix
8322 - Fix a hard-to-trigger resource leak when logging credential status.
8326 - Directory mirrors no longer fetch the v1 directory or
8327 running-routers files. They are obsolete, and nobody asks for them
8328 anymore. This is the first step to making v1 authorities obsolete.
8330 o Minor features (controller):
8331 - Return circuit purposes in response to GETINFO circuit-status. Fixes
8335 Changes in version 0.2.0.32 - 2008-11-20
8336 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
8337 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8338 a smaller security flaw that might allow an attacker to access local
8339 services, further improves hidden service performance, and fixes a
8340 variety of other issues.
8343 - The "User" and "Group" config options did not clear the
8344 supplementary group entries for the Tor process. The "User" option
8345 is now more robust, and we now set the groups to the specified
8346 user's primary group. The "Group" option is now ignored. For more
8347 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8348 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8349 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
8350 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8351 consistently obeyed: if an exit relay refuses a stream because its
8352 exit policy doesn't allow it, we would remember what IP address
8353 the relay said the destination address resolves to, even if it's
8354 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8357 - Fix a DOS opportunity during the voting signature collection process
8358 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
8360 o Major bugfixes (hidden services):
8361 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8362 we were failing the whole hidden service request when the v0
8363 descriptor fetch fails, even if the v2 fetch is still pending and
8364 might succeed. Similarly, if the last v2 fetch fails, we were
8365 failing the whole hidden service request even if a v0 fetch is
8366 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8367 - When extending a circuit to a hidden service directory to upload a
8368 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8369 requests failed, because the router descriptor has not been
8370 downloaded yet. In these cases, do not attempt to upload the
8371 rendezvous descriptor, but wait until the router descriptor is
8372 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
8373 descriptor from a hidden service directory for which the router
8374 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
8378 - Fix several infrequent memory leaks spotted by Coverity.
8379 - When testing for libevent functions, set the LDFLAGS variable
8380 correctly. Found by Riastradh.
8381 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8382 bootstrapping with tunneled directory connections. Bugfix on
8383 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8384 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8385 and we know that server B rejects most-but-not all connections to
8386 port 80, we would previously reject the connection. Now, we assume
8387 the user knows what they were asking for. Fixes bug 752. Bugfix
8388 on 0.0.9rc5. Diagnosed by BarkerJr.
8389 - If we overrun our per-second write limits a little, count this as
8390 having used up our write allocation for the second, and choke
8391 outgoing directory writes. Previously, we had only counted this when
8392 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
8393 Bugfix on 0.2.0.x (??).
8394 - Remove the old v2 directory authority 'lefkada' from the default
8395 list. It has been gone for many months.
8396 - Stop doing unaligned memory access that generated bus errors on
8397 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
8398 - Make USR2 log-level switch take effect immediately. Bugfix on
8401 o Minor bugfixes (controller):
8402 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
8403 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
8406 Changes in version 0.2.1.7-alpha - 2008-11-08
8407 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
8408 packages (and maybe other packages) noticed by Theo de Raadt, fixes
8409 a smaller security flaw that might allow an attacker to access local
8410 services, adds better defense against DNS poisoning attacks on exit
8411 relays, further improves hidden service performance, and fixes a
8412 variety of other issues.
8415 - The "ClientDNSRejectInternalAddresses" config option wasn't being
8416 consistently obeyed: if an exit relay refuses a stream because its
8417 exit policy doesn't allow it, we would remember what IP address
8418 the relay said the destination address resolves to, even if it's
8419 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
8420 - The "User" and "Group" config options did not clear the
8421 supplementary group entries for the Tor process. The "User" option
8422 is now more robust, and we now set the groups to the specified
8423 user's primary group. The "Group" option is now ignored. For more
8424 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
8425 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
8426 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
8427 - Do not use or believe expired v3 authority certificates. Patch
8428 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
8431 - Now NodeFamily and MyFamily config options allow spaces in
8432 identity fingerprints, so it's easier to paste them in.
8433 Suggested by Lucky Green.
8434 - Implement the 0x20 hack to better resist DNS poisoning: set the
8435 case on outgoing DNS requests randomly, and reject responses that do
8436 not match the case correctly. This logic can be disabled with the
8437 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
8438 of servers that do not reliably preserve case in replies. See
8439 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
8441 - Preserve case in replies to DNSPort requests in order to support
8442 the 0x20 hack for resisting DNS poisoning attacks.
8444 o Hidden service performance improvements:
8445 - When the client launches an introduction circuit, retry with a
8446 new circuit after 30 seconds rather than 60 seconds.
8447 - Launch a second client-side introduction circuit in parallel
8448 after a delay of 15 seconds (based on work by Christian Wilms).
8449 - Hidden services start out building five intro circuits rather
8450 than three, and when the first three finish they publish a service
8451 descriptor using those. Now we publish our service descriptor much
8452 faster after restart.
8455 - Minor fix in the warning messages when you're having problems
8456 bootstrapping; also, be more forgiving of bootstrap problems when
8457 we're still making incremental progress on a given bootstrap phase.
8458 - When we're choosing an exit node for a circuit, and we have
8459 no pending streams, choose a good general exit rather than one that
8460 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
8461 - Send a valid END cell back when a client tries to connect to a
8462 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
8463 840. Patch from rovv.
8464 - If a broken client asks a non-exit router to connect somewhere,
8465 do not even do the DNS lookup before rejecting the connection.
8466 Fixes another case of bug 619. Patch from rovv.
8467 - Fix another case of assuming, when a specific exit is requested,
8468 that we know more than the user about what hosts it allows.
8469 Fixes another case of bug 752. Patch from rovv.
8470 - Check which hops rendezvous stream cells are associated with to
8471 prevent possible guess-the-streamid injection attacks from
8472 intermediate hops. Fixes another case of bug 446. Based on patch
8474 - Avoid using a negative right-shift when comparing 32-bit
8475 addresses. Possible fix for bug 845 and bug 811.
8476 - Make the assert_circuit_ok() function work correctly on circuits that
8477 have already been marked for close.
8478 - Fix read-off-the-end-of-string error in unit tests when decoding
8479 introduction points.
8480 - Fix uninitialized size field for memory area allocation: may improve
8481 memory performance during directory parsing.
8482 - Treat duplicate certificate fetches as failures, so that we do
8483 not try to re-fetch an expired certificate over and over and over.
8484 - Do not say we're fetching a certificate when we'll in fact skip it
8485 because of a pending download.
8488 Changes in version 0.2.1.6-alpha - 2008-09-30
8489 Tor 0.2.1.6-alpha further improves performance and robustness of
8490 hidden services, starts work on supporting per-country relay selection,
8491 and fixes a variety of smaller issues.
8494 - Implement proposal 121: make it possible to build hidden services
8495 that only certain clients are allowed to connect to. This is
8496 enforced at several points, so that unauthorized clients are unable
8497 to send INTRODUCE cells to the service, or even (depending on the
8498 type of authentication) to learn introduction points. This feature
8499 raises the bar for certain kinds of active attacks against hidden
8500 services. Code by Karsten Loesing.
8501 - Relays now store and serve v2 hidden service descriptors by default,
8502 i.e., the new default value for HidServDirectoryV2 is 1. This is
8503 the last step in proposal 114, which aims to make hidden service
8504 lookups more reliable.
8505 - Start work to allow node restrictions to include country codes. The
8506 syntax to exclude nodes in a country with country code XX is
8507 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
8508 refinement to decide what config options should take priority if
8509 you ask to both use a particular node and exclude it.
8510 - Allow ExitNodes list to include IP ranges and country codes, just
8511 like the Exclude*Nodes lists. Patch from Robert Hogan.
8514 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
8515 Tor to fail to start if you had it configured to use a bridge
8516 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
8517 - When extending a circuit to a hidden service directory to upload a
8518 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
8519 requests failed, because the router descriptor had not been
8520 downloaded yet. In these cases, we now wait until the router
8521 descriptor is downloaded, and then retry. Likewise, clients
8522 now skip over a hidden service directory if they don't yet have
8523 its router descriptor, rather than futilely requesting it and
8524 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
8526 - When fetching v0 and v2 rendezvous service descriptors in parallel,
8527 we were failing the whole hidden service request when the v0
8528 descriptor fetch fails, even if the v2 fetch is still pending and
8529 might succeed. Similarly, if the last v2 fetch fails, we were
8530 failing the whole hidden service request even if a v0 fetch is
8531 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
8532 - DNS replies need to have names matching their requests, but
8533 these names should be in the questions section, not necessarily
8534 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
8537 - Update to the "September 1 2008" ip-to-country file.
8538 - Allow ports 465 and 587 in the default exit policy again. We had
8539 rejected them in 0.1.0.15, because back in 2005 they were commonly
8540 misconfigured and ended up as spam targets. We hear they are better
8541 locked down these days.
8542 - Use a lockfile to make sure that two Tor processes are not
8543 simultaneously running with the same datadir.
8544 - Serve the latest v3 networkstatus consensus via the control
8545 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
8546 - Better logging about stability/reliability calculations on directory
8548 - Drop the requirement to have an open dir port for storing and
8549 serving v2 hidden service descriptors.
8550 - Directory authorities now serve a /tor/dbg-stability.txt URL to
8551 help debug WFU and MTBF calculations.
8552 - Implement most of Proposal 152: allow specialized servers to permit
8553 single-hop circuits, and clients to use those servers to build
8554 single-hop circuits when using a specialized controller. Patch
8555 from Josh Albrecht. Resolves feature request 768.
8556 - Add a -p option to tor-resolve for specifying the SOCKS port: some
8557 people find host:port too confusing.
8558 - Make TrackHostExit mappings expire a while after their last use, not
8559 after their creation. Patch from Robert Hogan.
8560 - Provide circuit purposes along with circuit events to the controller.
8563 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
8565 - Fixed some memory leaks -- some quite frequent, some almost
8566 impossible to trigger -- based on results from Coverity.
8567 - When testing for libevent functions, set the LDFLAGS variable
8568 correctly. Found by Riastradh.
8569 - Fix an assertion bug in parsing policy-related options; possible fix
8571 - Catch and report a few more bootstrapping failure cases when Tor
8572 fails to establish a TCP connection. Cleanup on 0.2.1.x.
8573 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
8574 bootstrapping with tunneled directory connections. Bugfix on
8575 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
8576 - When asked to connect to A.B.exit:80, if we don't know the IP for A
8577 and we know that server B rejects most-but-not all connections to
8578 port 80, we would previously reject the connection. Now, we assume
8579 the user knows what they were asking for. Fixes bug 752. Bugfix
8580 on 0.0.9rc5. Diagnosed by BarkerJr.
8581 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
8582 service directories if they have no advertised dir port. Bugfix
8584 - If we overrun our per-second write limits a little, count this as
8585 having used up our write allocation for the second, and choke
8586 outgoing directory writes. Previously, we had only counted this when
8587 we had met our limits precisely. Fixes bug 824. Patch by rovv.
8588 Bugfix on 0.2.0.x (??).
8589 - Avoid a "0 divided by 0" calculation when calculating router uptime
8590 at directory authorities. Bugfix on 0.2.0.8-alpha.
8591 - Make DNS resolved controller events into "CLOSED", not
8592 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
8594 - Fix a bug where an unreachable relay would establish enough
8595 reachability testing circuits to do a bandwidth test -- if
8596 we already have a connection to the middle hop of the testing
8597 circuit, then it could establish the last hop by using the existing
8598 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
8599 circuits no longer use entry guards in 0.2.1.3-alpha.
8600 - If we have correct permissions on $datadir, we complain to stdout
8601 and fail to start. But dangerous permissions on
8602 $datadir/cached-status/ would cause us to open a log and complain
8603 there. Now complain to stdout and fail to start in both cases. Fixes
8604 bug 820, reported by seeess.
8605 - Remove the old v2 directory authority 'lefkada' from the default
8606 list. It has been gone for many months.
8608 o Code simplifications and refactoring:
8609 - Revise the connection_new functions so that a more typesafe variant
8610 exists. This will work better with Coverity, and let us find any
8611 actual mistakes we're making here.
8612 - Refactor unit testing logic so that dmalloc can be used sensibly
8613 with unit tests to check for memory leaks.
8614 - Move all hidden-service related fields from connection and circuit
8615 structure to substructures: this way they won't eat so much memory.
8618 Changes in version 0.2.0.31 - 2008-09-03
8619 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
8620 a big bug we're seeing where in rare cases traffic from one Tor stream
8621 gets mixed into another stream, and fixes a variety of smaller issues.
8624 - Make sure that two circuits can never exist on the same connection
8625 with the same circuit ID, even if one is marked for close. This
8626 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
8627 - Relays now reject risky extend cells: if the extend cell includes
8628 a digest of all zeroes, or asks to extend back to the relay that
8629 sent the extend cell, tear down the circuit. Ideas suggested
8631 - If not enough of our entry guards are available so we add a new
8632 one, we might use the new one even if it overlapped with the
8633 current circuit's exit relay (or its family). Anonymity bugfix
8634 pointed out by rovv.
8637 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8638 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8639 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8640 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8641 - Pick size of default geoip filename string correctly on windows.
8642 Fixes bug 806. Bugfix on 0.2.0.30.
8643 - Make the autoconf script accept the obsolete --with-ssl-dir
8644 option as an alias for the actually-working --with-openssl-dir
8645 option. Fix the help documentation to recommend --with-openssl-dir.
8646 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8647 - When using the TransPort option on OpenBSD, and using the User
8648 option to change UID and drop privileges, make sure to open
8649 /dev/pf before dropping privileges. Fixes bug 782. Patch from
8650 Christopher Davis. Bugfix on 0.1.2.1-alpha.
8651 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8652 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8653 on the client side when connecting to a hidden service. Bugfix
8654 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8655 - When closing an application-side connection because its circuit is
8656 getting torn down, generate the stream event correctly. Bugfix on
8657 0.1.2.x. Anonymous patch.
8660 Changes in version 0.2.1.5-alpha - 2008-08-31
8661 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
8662 in a lot of the infrastructure for adding authorization to hidden
8663 services, lays the groundwork for having clients read their load
8664 balancing information out of the networkstatus consensus rather than
8665 the individual router descriptors, addresses two potential anonymity
8666 issues, and fixes a variety of smaller issues.
8669 - Convert many internal address representations to optionally hold
8671 - Generate and accept IPv6 addresses in many protocol elements.
8672 - Make resolver code handle nameservers located at ipv6 addresses.
8673 - Begin implementation of proposal 121 ("Client authorization for
8674 hidden services"): configure hidden services with client
8675 authorization, publish descriptors for them, and configure
8676 authorization data for hidden services at clients. The next
8677 step is to actually access hidden services that perform client
8679 - More progress toward proposal 141: Network status consensus
8680 documents and votes now contain bandwidth information for each
8681 router and a summary of that router's exit policy. Eventually this
8682 will be used by clients so that they do not have to download every
8683 known descriptor before building circuits.
8685 o Major bugfixes (on 0.2.0.x and before):
8686 - When sending CREATED cells back for a given circuit, use a 64-bit
8687 connection ID to find the right connection, rather than an addr:port
8688 combination. Now that we can have multiple OR connections between
8689 the same ORs, it is no longer possible to use addr:port to uniquely
8690 identify a connection.
8691 - Relays now reject risky extend cells: if the extend cell includes
8692 a digest of all zeroes, or asks to extend back to the relay that
8693 sent the extend cell, tear down the circuit. Ideas suggested
8695 - If not enough of our entry guards are available so we add a new
8696 one, we might use the new one even if it overlapped with the
8697 current circuit's exit relay (or its family). Anonymity bugfix
8698 pointed out by rovv.
8701 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
8702 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
8703 - When using the TransPort option on OpenBSD, and using the User
8704 option to change UID and drop privileges, make sure to open /dev/pf
8705 before dropping privileges. Fixes bug 782. Patch from Christopher
8706 Davis. Bugfix on 0.1.2.1-alpha.
8707 - Correctly detect the presence of the linux/netfilter_ipv4.h header
8708 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
8709 - Add a missing safe_str() call for a debug log message.
8710 - Use 64 bits instead of 32 bits for connection identifiers used with
8711 the controller protocol, to greatly reduce risk of identifier reuse.
8712 - Make the autoconf script accept the obsolete --with-ssl-dir
8713 option as an alias for the actually-working --with-openssl-dir
8714 option. Fix the help documentation to recommend --with-openssl-dir.
8715 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
8718 - Rate-limit too-many-sockets messages: when they happen, they happen
8719 a lot. Resolves bug 748.
8720 - Resist DNS poisoning a little better by making sure that names in
8721 answer sections match.
8722 - Print the SOCKS5 error message string as well as the error code
8723 when a tor-resolve request fails. Patch from Jacob.
8726 Changes in version 0.2.1.4-alpha - 2008-08-04
8727 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
8730 - The address part of exit policies was not correctly written
8731 to router descriptors. This generated router descriptors that failed
8732 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
8734 - Tor triggered a false assert when extending a circuit to a relay
8735 but we already have a connection open to that relay. Noticed by
8736 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
8739 - Fix a hidden service logging bug: in some edge cases, the router
8740 descriptor of a previously picked introduction point becomes
8741 obsolete and we need to give up on it rather than continually
8742 complaining that it has become obsolete. Observed by xiando. Bugfix
8746 - Take out the TestVia config option, since it was a workaround for
8747 a bug that was fixed in Tor 0.1.1.21.
8750 Changes in version 0.2.1.3-alpha - 2008-08-03
8751 Tor 0.2.1.3-alpha implements most of the pieces to prevent
8752 infinite-length circuit attacks (see proposal 110); fixes a bug that
8753 might cause exit relays to corrupt streams they send back; allows
8754 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
8755 ExcludeExitNodes config options; and fixes a big pile of bugs.
8757 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
8758 - Send a bootstrap problem "warn" event on the first problem if the
8759 reason is NO_ROUTE (that is, our network is down).
8762 - Implement most of proposal 110: The first K cells to be sent
8763 along a circuit are marked as special "early" cells; only K "early"
8764 cells will be allowed. Once this code is universal, we can block
8765 certain kinds of DOS attack by requiring that EXTEND commands must
8766 be sent using an "early" cell.
8769 - Try to attach connections immediately upon receiving a RENDEZVOUS2
8770 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
8771 on the client side when connecting to a hidden service. Bugfix
8772 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
8773 - Ensure that two circuits can never exist on the same connection
8774 with the same circuit ID, even if one is marked for close. This
8775 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
8778 - When relays do their initial bandwidth measurement, don't limit
8779 to just our entry guards for the test circuits. Otherwise we tend
8780 to have multiple test circuits going through a single entry guard,
8781 which makes our bandwidth test less accurate. Fixes part of bug 654;
8782 patch contributed by Josh Albrecht.
8783 - Add an ExcludeExitNodes option so users can list a set of nodes
8784 that should be be excluded from the exit node position, but
8785 allowed elsewhere. Implements proposal 151.
8786 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
8787 ExcludeNodes and ExcludeExitNodes lists.
8788 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
8789 be more efficient. Formerly it was quadratic in the number of
8790 servers; now it should be linear. Fixes bug 509.
8791 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
8792 and n_conn_id_digest fields into a separate structure that's
8793 only needed when the circuit has not yet attached to an n_conn.
8796 - Change the contrib/tor.logrotate script so it makes the new
8797 logs as "_tor:_tor" rather than the default, which is generally
8798 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
8799 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8800 warnings (occasionally), but it can also cause the compiler to
8801 eliminate error-checking code. Suggested by Peter Gutmann.
8802 - When a hidden service is giving up on an introduction point candidate
8803 that was not included in the last published rendezvous descriptor,
8804 don't reschedule publication of the next descriptor. Fixes bug 763.
8806 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
8807 HiddenServiceExcludeNodes as obsolete: they never worked properly,
8808 and nobody claims to be using them. Fixes bug 754. Bugfix on
8809 0.1.0.1-rc. Patch from Christian Wilms.
8810 - Fix a small alignment and memory-wasting bug on buffer chunks.
8813 o Minor bugfixes (controller):
8814 - When closing an application-side connection because its circuit
8815 is getting torn down, generate the stream event correctly.
8816 Bugfix on 0.1.2.x. Anonymous patch.
8819 - Remove all backward-compatibility code to support relays running
8820 versions of Tor so old that they no longer work at all on the
8824 Changes in version 0.2.0.30 - 2008-07-15
8826 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
8827 warnings (occasionally), but it can also cause the compiler to
8828 eliminate error-checking code. Suggested by Peter Gutmann.
8831 Changes in version 0.2.0.29-rc - 2008-07-08
8832 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
8833 hidden-service performance bugs, and fixes a bunch of smaller bugs.
8836 - If you have more than one bridge but don't know their keys,
8837 you would only launch a request for the descriptor of the first one
8838 on your list. (Tor considered launching requests for the others, but
8839 found that it already had a connection on the way for $0000...0000
8840 so it didn't open another.) Bugfix on 0.2.0.x.
8841 - If you have more than one bridge but don't know their keys, and the
8842 connection to one of the bridges failed, you would cancel all
8843 pending bridge connections. (After all, they all have the same
8844 digest.) Bugfix on 0.2.0.x.
8845 - When a hidden service was trying to establish an introduction point,
8846 and Tor had built circuits preemptively for such purposes, we
8847 were ignoring all the preemptive circuits and launching a new one
8848 instead. Bugfix on 0.2.0.14-alpha.
8849 - When a hidden service was trying to establish an introduction point,
8850 and Tor *did* manage to reuse one of the preemptively built
8851 circuits, it didn't correctly remember which one it used,
8852 so it asked for another one soon after, until there were no
8853 more preemptive circuits, at which point it launched one from
8854 scratch. Bugfix on 0.0.9.x.
8855 - Make directory servers include the X-Your-Address-Is: http header in
8856 their responses even for begin_dir conns. Now clients who only
8857 ever use begin_dir connections still have a way to learn their IP
8858 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
8861 - Fix a macro/CPP interaction that was confusing some compilers:
8862 some GCCs don't like #if/#endif pairs inside macro arguments.
8864 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
8865 Fixes bug 704; fix from Steven Murdoch.
8866 - When opening /dev/null in finish_daemonize(), do not pass the
8867 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
8868 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
8869 - Correctly detect transparent proxy support on Linux hosts that
8870 require in.h to be included before netfilter_ipv4.h. Patch
8872 - Disallow session resumption attempts during the renegotiation
8873 stage of the v2 handshake protocol. Clients should never be trying
8874 session resumption at this point, but apparently some did, in
8875 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
8876 found by Geoff Goodell.
8879 Changes in version 0.2.1.2-alpha - 2008-06-20
8880 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
8881 make it easier to set up your own private Tor network; fixes several
8882 big bugs with using more than one bridge relay; fixes a big bug with
8883 offering hidden services quickly after Tor starts; and uses a better
8884 API for reporting potential bootstrapping problems to the controller.
8887 - New TestingTorNetwork config option to allow adjustment of
8888 previously constant values that, while reasonable, could slow
8889 bootstrapping. Implements proposal 135. Patch from Karsten.
8892 - If you have more than one bridge but don't know their digests,
8893 you would only learn a request for the descriptor of the first one
8894 on your list. (Tor considered launching requests for the others, but
8895 found that it already had a connection on the way for $0000...0000
8896 so it didn't open another.) Bugfix on 0.2.0.x.
8897 - If you have more than one bridge but don't know their digests,
8898 and the connection to one of the bridges failed, you would cancel
8899 all pending bridge connections. (After all, they all have the
8900 same digest.) Bugfix on 0.2.0.x.
8901 - When establishing a hidden service, introduction points that
8902 originate from cannibalized circuits are completely ignored and not
8903 included in rendezvous service descriptors. This might be another
8904 reason for delay in making a hidden service available. Bugfix
8905 from long ago (0.0.9.x?)
8908 - Allow OpenSSL to use dynamic locks if it wants.
8909 - When building a consensus, do not include routers that are down.
8910 This will cut down 30% to 40% on consensus size. Implements
8912 - In directory authorities' approved-routers files, allow
8913 fingerprints with or without space.
8914 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
8915 controller can query our current bootstrap state in case it attaches
8916 partway through and wants to catch up.
8917 - Send an initial "Starting" bootstrap status event, so we have a
8918 state to start out in.
8921 - Asking for a conditional consensus at .../consensus/<fingerprints>
8922 would crash a dirserver if it did not already have a
8923 consensus. Bugfix on 0.2.1.1-alpha.
8924 - Clean up some macro/CPP interactions: some GCC versions don't like
8925 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
8928 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
8929 - Directory authorities shouldn't complain about bootstrapping
8930 problems just because they do a lot of reachability testing and
8931 some of the connection attempts fail.
8932 - Start sending "count" and "recommendation" key/value pairs in
8933 bootstrap problem status events, so the controller can hear about
8934 problems even before Tor decides they're worth reporting for sure.
8935 - If you're using bridges, generate "bootstrap problem" warnings
8936 as soon as you run out of working bridges, rather than waiting
8937 for ten failures -- which will never happen if you have less than
8939 - If we close our OR connection because there's been a circuit
8940 pending on it for too long, we were telling our bootstrap status
8941 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
8944 Changes in version 0.2.1.1-alpha - 2008-06-13
8945 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
8946 were making the Tor process bloat especially on Linux; makes our TLS
8947 handshake blend in better; sends "bootstrap phase" status events to
8948 the controller, so it can keep the user informed of progress (and
8949 problems) fetching directory information and establishing circuits;
8950 and adds a variety of smaller features.
8953 - More work on making our TLS handshake blend in: modify the list
8954 of ciphers advertised by OpenSSL in client mode to even more
8955 closely resemble a common web browser. We cheat a little so that
8956 we can advertise ciphers that the locally installed OpenSSL doesn't
8958 - Start sending "bootstrap phase" status events to the controller,
8959 so it can keep the user informed of progress fetching directory
8960 information and establishing circuits. Also inform the controller
8961 if we think we're stuck at a particular bootstrap phase. Implements
8963 - Resume using OpenSSL's RAND_poll() for better (and more portable)
8964 cross-platform entropy collection again. We used to use it, then
8965 stopped using it because of a bug that could crash systems that
8966 called RAND_poll when they had a lot of fds open. It looks like the
8967 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
8968 at startup, and to call RAND_poll() when we reseed later only if
8969 we have a non-buggy OpenSSL version.
8972 - When we choose to abandon a new entry guard because we think our
8973 older ones might be better, close any circuits pending on that
8974 new entry guard connection. This fix should make us recover much
8975 faster when our network is down and then comes back. Bugfix on
8976 0.1.2.8-beta; found by lodger.
8978 o Memory fixes and improvements:
8979 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
8980 to avoid unused RAM in buffer chunks and memory pools.
8981 - Speed up parsing and cut down on memory fragmentation by using
8982 stack-style allocations for parsing directory objects. Previously,
8983 this accounted for over 40% of allocations from within Tor's code
8984 on a typical directory cache.
8985 - Use a Bloom filter rather than a digest-based set to track which
8986 descriptors we need to keep around when we're cleaning out old
8987 router descriptors. This speeds up the computation significantly,
8988 and may reduce fragmentation.
8989 - Reduce the default smartlist size from 32 to 16; it turns out that
8990 most smartlists hold around 8-12 elements tops.
8991 - Make dumpstats() log the fullness and size of openssl-internal
8993 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
8994 patch to their OpenSSL, turn it on to save memory on servers. This
8995 patch will (with any luck) get included in a mainline distribution
8997 - Never use OpenSSL compression: it wastes RAM and CPU trying to
8998 compress cells, which are basically all encrypted, compressed,
9002 - Stop reloading the router list from disk for no reason when we
9003 run out of reachable directory mirrors. Once upon a time reloading
9004 it would set the 'is_running' flag back to 1 for them. It hasn't
9005 done that for a long time.
9006 - In very rare situations new hidden service descriptors were
9007 published earlier than 30 seconds after the last change to the
9008 service. (We currently think that a hidden service descriptor
9009 that's been stable for 30 seconds is worth publishing.)
9012 - Allow separate log levels to be configured for different logging
9013 domains. For example, this allows one to log all notices, warnings,
9014 or errors, plus all memory management messages of level debug or
9015 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
9016 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
9017 and stop using a warning that had become unfixably verbose under
9019 - New --hush command-line option similar to --quiet. While --quiet
9020 disables all logging to the console on startup, --hush limits the
9021 output to messages of warning and error severity.
9022 - Servers support a new URL scheme for consensus downloads that
9023 allows the client to specify which authorities are trusted.
9024 The server then only sends the consensus if the client will trust
9025 it. Otherwise a 404 error is sent back. Clients use this
9026 new scheme when the server supports it (meaning it's running
9027 0.2.1.1-alpha or later). Implements proposal 134.
9028 - New configure/torrc options (--enable-geoip-stats,
9029 DirRecordUsageByCountry) to record how many IPs we've served
9030 directory info to in each country code, how many status documents
9031 total we've sent to each country code, and what share of the total
9032 directory requests we should expect to see.
9033 - Use the TLS1 hostname extension to more closely resemble browser
9035 - Lots of new unit tests.
9036 - Add a macro to implement the common pattern of iterating through
9037 two parallel lists in lockstep.
9040 Changes in version 0.2.0.28-rc - 2008-06-13
9041 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
9042 performance bug, and fixes a bunch of smaller bugs.
9045 - Fix a bug where, when we were choosing the 'end stream reason' to
9046 put in our relay end cell that we send to the exit relay, Tor
9047 clients on Windows were sometimes sending the wrong 'reason'. The
9048 anonymity problem is that exit relays may be able to guess whether
9049 the client is running Windows, thus helping partition the anonymity
9050 set. Down the road we should stop sending reasons to exit relays,
9051 or otherwise prevent future versions of this bug.
9054 - While setting up a hidden service, some valid introduction circuits
9055 were overlooked and abandoned. This might be the reason for
9056 the long delay in making a hidden service available. Bugfix on
9060 - Update to the "June 9 2008" ip-to-country file.
9061 - Run 'make test' as part of 'make dist', so we stop releasing so
9062 many development snapshots that fail their unit tests.
9065 - When we're checking if we have enough dir info for each relay
9066 to begin establishing circuits, make sure that we actually have
9067 the descriptor listed in the consensus, not just any descriptor.
9069 - Bridge relays no longer print "xx=0" in their extrainfo document
9070 for every single country code in the geoip db. Bugfix on
9072 - Only warn when we fail to load the geoip file if we were planning to
9073 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
9074 - If we change our MaxAdvertisedBandwidth and then reload torrc,
9075 Tor won't realize it should publish a new relay descriptor. Fixes
9076 bug 688, reported by mfr. Bugfix on 0.1.2.x.
9077 - When we haven't had any application requests lately, don't bother
9078 logging that we have expired a bunch of descriptors. Bugfix
9080 - Make relay cells written on a connection count as non-padding when
9081 tracking how long a connection has been in use. Bugfix on
9082 0.2.0.1-alpha. Spotted by lodger.
9083 - Fix unit tests in 0.2.0.27-rc.
9084 - Fix compile on Windows.
9087 Changes in version 0.2.0.27-rc - 2008-06-03
9088 Tor 0.2.0.27-rc adds a few features we left out of the earlier
9089 release candidates. In particular, we now include an IP-to-country
9090 GeoIP database, so controllers can easily look up what country a
9091 given relay is in, and so bridge relays can give us some sanitized
9092 summaries about which countries are making use of bridges. (See proposal
9093 126-geoip-fetching.txt for details.)
9096 - Include an IP-to-country GeoIP file in the tarball, so bridge
9097 relays can report sanitized summaries of the usage they're seeing.
9100 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
9101 Robert Hogan. Fixes the first part of bug 681.
9102 - Make bridge authorities never serve extrainfo docs.
9103 - Add support to detect Libevent versions in the 1.4.x series
9105 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
9106 - Include a new contrib/tor-exit-notice.html file that exit relay
9107 operators can put on their website to help reduce abuse queries.
9110 - When tunneling an encrypted directory connection, and its first
9111 circuit fails, do not leave it unattached and ask the controller
9112 to deal. Fixes the second part of bug 681.
9113 - Make bridge authorities correctly expire old extrainfo documents
9117 Changes in version 0.2.0.26-rc - 2008-05-13
9118 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
9119 in Debian's OpenSSL packages. All users running any 0.2.0.x version
9120 should upgrade, whether they're running Debian or not.
9122 o Major security fixes:
9123 - Use new V3 directory authority keys on the tor26, gabelmoo, and
9124 moria1 V3 directory authorities. The old keys were generated with
9125 a vulnerable version of Debian's OpenSSL package, and must be
9126 considered compromised. Other authorities' keys were not generated
9127 with an affected version of OpenSSL.
9130 - List authority signatures as "unrecognized" based on DirServer
9131 lines, not on cert cache. Bugfix on 0.2.0.x.
9134 - Add a new V3AuthUseLegacyKey option to make it easier for
9135 authorities to change their identity keys if they have to.
9138 Changes in version 0.2.0.25-rc - 2008-04-23
9139 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
9142 - Remember to initialize threading before initializing logging.
9143 Otherwise, many BSD-family implementations will crash hard on
9144 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
9147 - Authorities correctly free policies on bad servers on
9148 exit. Fixes bug 672. Bugfix on 0.2.0.x.
9151 Changes in version 0.2.0.24-rc - 2008-04-22
9152 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
9153 v3 directory authority, makes relays with dynamic IP addresses and no
9154 DirPort notice more quickly when their IP address changes, fixes a few
9155 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
9157 o New directory authorities:
9158 - Take lefkada out of the list of v3 directory authorities, since
9159 it has been down for months.
9160 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
9164 - Detect address changes more quickly on non-directory mirror
9165 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
9167 o Minor features (security):
9168 - Reject requests for reverse-dns lookup of names that are in
9169 a private address space. Patch from lodger.
9170 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
9173 o Minor bugfixes (crashes):
9174 - Avoid a rare assert that can trigger when Tor doesn't have much
9175 directory information yet and it tries to fetch a v2 hidden
9176 service descriptor. Fixes bug 651, reported by nwf.
9177 - Initialize log mutex before initializing dmalloc. Otherwise,
9178 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
9179 - Use recursive pthread mutexes in order to avoid deadlock when
9180 logging debug-level messages to a controller. Bug spotted by nwf,
9181 bugfix on 0.2.0.16-alpha.
9183 o Minor bugfixes (resource management):
9184 - Keep address policies from leaking memory: start their refcount
9185 at 1, not 2. Bugfix on 0.2.0.16-alpha.
9186 - Free authority certificates on exit, so they don't look like memory
9187 leaks. Bugfix on 0.2.0.19-alpha.
9188 - Free static hashtables for policy maps and for TLS connections on
9189 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
9190 - Avoid allocating extra space when computing consensuses on 64-bit
9191 platforms. Bug spotted by aakova.
9193 o Minor bugfixes (misc):
9194 - Do not read the configuration file when we've only been told to
9195 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
9196 based on patch from Sebastian Hahn.
9197 - Exit relays that are used as a client can now reach themselves
9198 using the .exit notation, rather than just launching an infinite
9199 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
9200 - When attempting to open a logfile fails, tell us why.
9201 - Fix a dumb bug that was preventing us from knowing that we should
9202 preemptively build circuits to handle expected directory requests.
9203 Fixes bug 660. Bugfix on 0.1.2.x.
9204 - Warn less verbosely about clock skew from netinfo cells from
9205 untrusted sources. Fixes bug 663.
9206 - Make controller stream events for DNS requests more consistent,
9207 by adding "new stream" events for DNS requests, and removing
9208 spurious "stream closed" events" for cached reverse resolves.
9209 Patch from mwenge. Fixes bug 646.
9210 - Correctly notify one-hop connections when a circuit build has
9211 failed. Possible fix for bug 669. Found by lodger.
9214 Changes in version 0.2.0.23-rc - 2008-03-24
9215 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
9216 makes bootstrapping faster if the first directory mirror you contact
9217 is down. The bundles also include the new Vidalia 0.1.2 release.
9220 - When a tunneled directory request is made to a directory server
9221 that's down, notice after 30 seconds rather than 120 seconds. Also,
9222 fail any begindir streams that are pending on it, so they can
9223 retry elsewhere. This was causing multi-minute delays on bootstrap.
9226 Changes in version 0.2.0.22-rc - 2008-03-18
9227 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
9228 enables encrypted directory connections by default for non-relays, fixes
9229 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
9230 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
9233 - Enable encrypted directory connections by default for non-relays,
9234 so censor tools that block Tor directory connections based on their
9235 plaintext patterns will no longer work. This means Tor works in
9236 certain censored countries by default again.
9239 - Make sure servers always request certificates from clients during
9240 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
9241 - Do not enter a CPU-eating loop when a connection is closed in
9242 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
9243 diagnosed by lodger; bugfix on 0.2.0.20-rc.
9244 - Fix assertion failure that could occur when a blocked circuit
9245 became unblocked, and it had pending client DNS requests. Bugfix
9246 on 0.2.0.1-alpha. Fixes bug 632.
9248 o Minor bugfixes (on 0.1.2.x):
9249 - Generate "STATUS_SERVER" events rather than misspelled
9250 "STATUS_SEVER" events. Caught by mwenge.
9251 - When counting the number of bytes written on a TLS connection,
9252 look at the BIO actually used for writing to the network, not
9253 at the BIO used (sometimes) to buffer data for the network.
9254 Looking at different BIOs could result in write counts on the
9255 order of ULONG_MAX. Fixes bug 614.
9256 - On Windows, correctly detect errors when listing the contents of
9257 a directory. Fix from lodger.
9259 o Minor bugfixes (on 0.2.0.x):
9260 - Downgrade "sslv3 alert handshake failure" message to INFO.
9261 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
9262 left BandwidthRate and BandwidthBurst at the default, we would be
9263 silently limited by those defaults. Now raise them to match the
9264 RelayBandwidth* values.
9265 - Fix the SVK version detection logic to work correctly on a branch.
9266 - Make --enable-openbsd-malloc work correctly on Linux with alpha
9267 CPUs. Fixes bug 625.
9268 - Logging functions now check that the passed severity is sane.
9269 - Use proper log levels in the testsuite call of
9270 get_interface_address6().
9271 - When using a nonstandard malloc, do not use the platform values for
9272 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
9273 - Make the openbsd malloc code use 8k pages on alpha CPUs and
9275 - Detect mismatched page sizes when using --enable-openbsd-malloc.
9276 - Avoid double-marked-for-close warning when certain kinds of invalid
9277 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
9278 for bug 617. Bugfix on 0.2.0.1-alpha.
9279 - Make sure that the "NULL-means-reject *:*" convention is followed by
9280 all the policy manipulation functions, avoiding some possible crash
9281 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
9282 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
9283 actually works, and doesn't warn about every single reverse lookup.
9284 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
9287 - Only log guard node status when guard node status has changed.
9288 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
9289 make "INFO" 75% less verbose.
9292 Changes in version 0.2.0.21-rc - 2008-03-02
9293 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
9294 makes Tor work well with Vidalia again, fixes a rare assert bug,
9295 and fixes a pair of more minor bugs. The bundles also include Vidalia
9296 0.1.0 and Torbutton 1.1.16.
9299 - The control port should declare that it requires password auth
9300 when HashedControlSessionPassword is set too. Patch from Matt Edman;
9301 bugfix on 0.2.0.20-rc. Fixes bug 615.
9302 - Downgrade assert in connection_buckets_decrement() to a log message.
9303 This may help us solve bug 614, and in any case will make its
9304 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
9305 - We were sometimes miscounting the number of bytes read from the
9306 network, causing our rate limiting to not be followed exactly.
9307 Bugfix on 0.2.0.16-alpha. Reported by lodger.
9310 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
9311 OpenSSL versions should have been working fine. Diagnosis and patch
9312 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
9313 Bugfix on 0.2.0.20-rc.
9316 Changes in version 0.2.0.20-rc - 2008-02-24
9317 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
9318 makes more progress towards normalizing Tor's TLS handshake, makes
9319 hidden services work better again, helps relays bootstrap if they don't
9320 know their IP address, adds optional support for linking in openbsd's
9321 allocator or tcmalloc, allows really fast relays to scale past 15000
9322 sockets, and fixes a bunch of minor bugs reported by Veracode.
9325 - Enable the revised TLS handshake based on the one designed by
9326 Steven Murdoch in proposal 124, as revised in proposal 130. It
9327 includes version negotiation for OR connections as described in
9328 proposal 105. The new handshake is meant to be harder for censors
9329 to fingerprint, and it adds the ability to detect certain kinds of
9330 man-in-the-middle traffic analysis attacks. The version negotiation
9331 feature will allow us to improve Tor's link protocol more safely
9333 - Choose which bridge to use proportional to its advertised bandwidth,
9334 rather than uniformly at random. This should speed up Tor for
9335 bridge users. Also do this for people who set StrictEntryNodes.
9336 - When a TrackHostExits-chosen exit fails too many times in a row,
9337 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
9340 - Resolved problems with (re-)fetching hidden service descriptors.
9341 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
9343 - If we only ever used Tor for hidden service lookups or posts, we
9344 would stop building circuits and start refusing connections after
9345 24 hours, since we falsely believed that Tor was dormant. Reported
9346 by nwf; bugfix on 0.1.2.x.
9347 - Servers that don't know their own IP address should go to the
9348 authorities for their first directory fetch, even if their DirPort
9349 is off or if they don't know they're reachable yet. This will help
9350 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
9351 - When counting the number of open sockets, count not only the number
9352 of sockets we have received from the socket() call, but also
9353 the number we've gotten from accept() and socketpair(). This bug
9354 made us fail to count all sockets that we were using for incoming
9355 connections. Bugfix on 0.2.0.x.
9356 - Fix code used to find strings within buffers, when those strings
9357 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
9358 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
9359 - Add a new __HashedControlSessionPassword option for controllers
9360 to use for one-off session password hashes that shouldn't get
9361 saved to disk by SAVECONF --- Vidalia users were accumulating a
9362 pile of HashedControlPassword lines in their torrc files, one for
9363 each time they had restarted Tor and then clicked Save. Make Tor
9364 automatically convert "HashedControlPassword" to this new option but
9365 only when it's given on the command line. Partial fix for bug 586.
9367 o Minor features (performance):
9368 - Tune parameters for cell pool allocation to minimize amount of
9370 - Add OpenBSD malloc code from phk as an optional malloc
9371 replacement on Linux: some glibc libraries do very poorly
9372 with Tor's memory allocation patterns. Pass
9373 --enable-openbsd-malloc to get the replacement malloc code.
9374 - Add a --with-tcmalloc option to the configure script to link
9375 against tcmalloc (if present). Does not yet search for
9376 non-system include paths.
9377 - Stop imposing an arbitrary maximum on the number of file descriptors
9378 used for busy servers. Bug reported by Olaf Selke; patch from
9381 o Minor features (other):
9382 - When SafeLogging is disabled, log addresses along with all TLS
9384 - When building with --enable-gcc-warnings, check for whether Apple's
9385 warning "-Wshorten-64-to-32" is available.
9386 - Add a --passphrase-fd argument to the tor-gencert command for
9389 o Minor bugfixes (memory leaks and code problems):
9390 - We were leaking a file descriptor if Tor started with a zero-length
9391 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
9392 - Detect size overflow in zlib code. Reported by Justin Ferguson and
9394 - We were comparing the raw BridgePassword entry with a base64'ed
9395 version of it, when handling a "/tor/networkstatus-bridges"
9396 directory request. Now compare correctly. Noticed by Veracode.
9397 - Recover from bad tracked-since value in MTBF-history file.
9399 - Alter the code that tries to recover from unhandled write
9400 errors, to not try to flush onto a socket that's given us
9401 unhandled errors. Bugfix on 0.1.2.x.
9402 - Make Unix controlsockets work correctly on OpenBSD. Patch from
9403 tup. Bugfix on 0.2.0.3-alpha.
9405 o Minor bugfixes (other):
9406 - If we have an extra-info document for our server, always make
9407 it available on the control port, even if we haven't gotten
9408 a copy of it from an authority yet. Patch from mwenge.
9409 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
9410 - Directory mirrors no longer include a guess at the client's IP
9411 address if the connection appears to be coming from the same /24
9412 network; it was producing too many wrong guesses.
9413 - Make the new hidden service code respect the SafeLogging setting.
9414 Bugfix on 0.2.0.x. Patch from Karsten.
9415 - When starting as an authority, do not overwrite all certificates
9416 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
9417 - If we're trying to flush the last bytes on a connection (for
9418 example, when answering a directory request), reset the
9419 time-to-give-up timeout every time we manage to write something
9420 on the socket. Bugfix on 0.1.2.x.
9421 - Change the behavior of "getinfo status/good-server-descriptor"
9422 so it doesn't return failure when any authority disappears.
9423 - Even though the man page said that "TrackHostExits ." should
9424 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
9425 - Report TLS "zero return" case as a "clean close" and "IO error"
9426 as a "close". Stop calling closes "unexpected closes": existing
9427 Tors don't use SSL_close(), so having a connection close without
9428 the TLS shutdown handshake is hardly unexpected.
9429 - Send NAMESERVER_STATUS messages for a single failed nameserver
9432 o Code simplifications and refactoring:
9433 - Remove the tor_strpartition function: its logic was confused,
9434 and it was only used for one thing that could be implemented far
9438 Changes in version 0.2.0.19-alpha - 2008-02-09
9439 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
9440 handshake, makes path selection for relays more secure and IP address
9441 guessing more robust, and generally fixes a lot of bugs in preparation
9442 for calling the 0.2.0 branch stable.
9445 - Do not include recognizeable strings in the commonname part of
9446 Tor's x509 certificates.
9449 - If we're a relay, avoid picking ourselves as an introduction point,
9450 a rendezvous point, or as the final hop for internal circuits. Bug
9451 reported by taranis and lodger. Bugfix on 0.1.2.x.
9452 - Patch from "Andrew S. Lists" to catch when we contact a directory
9453 mirror at IP address X and he says we look like we're coming from
9454 IP address X. Bugfix on 0.1.2.x.
9456 o Minor features (security):
9457 - Be more paranoid about overwriting sensitive memory on free(),
9458 as a defensive programming tactic to ensure forward secrecy.
9460 o Minor features (directory authority):
9461 - Actually validate the options passed to AuthDirReject,
9462 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
9463 - Reject router descriptors with out-of-range bandwidthcapacity or
9464 bandwidthburst values.
9466 o Minor features (controller):
9467 - Reject controller commands over 1MB in length. This keeps rogue
9468 processes from running us out of memory.
9470 o Minor features (misc):
9471 - Give more descriptive well-formedness errors for out-of-range
9472 hidden service descriptor/protocol versions.
9473 - Make memory debugging information describe more about history
9474 of cell allocation, so we can help reduce our memory use.
9476 o Deprecated features (controller):
9477 - The status/version/num-versioning and status/version/num-concurring
9478 GETINFO options are no longer useful in the v3 directory protocol:
9479 treat them as deprecated, and warn when they're used.
9482 - When our consensus networkstatus has been expired for a while, stop
9483 being willing to build circuits using it. Fixes bug 401. Bugfix
9485 - Directory caches now fetch certificates from all authorities
9486 listed in a networkstatus consensus, even when they do not
9487 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
9488 - When connecting to a bridge without specifying its key, insert
9489 the connection into the identity-to-connection map as soon as
9490 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
9491 - Detect versions of OS X where malloc_good_size() is present in the
9492 library but never actually declared. Resolves bug 587. Bugfix
9494 - Stop incorrectly truncating zlib responses to directory authority
9495 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
9496 - Stop recommending that every server operator send mail to tor-ops.
9497 Resolves bug 597. Bugfix on 0.1.2.x.
9498 - Don't trigger an assert if we start a directory authority with a
9499 private IP address (like 127.0.0.1).
9500 - Avoid possible failures when generating a directory with routers
9501 with over-long versions strings, or too many flags set. Bugfix
9503 - If an attempt to launch a DNS resolve request over the control
9504 port fails because we have overrun the limit on the number of
9505 connections, tell the controller that the request has failed.
9506 - Avoid using too little bandwidth when our clock skips a few
9507 seconds. Bugfix on 0.1.2.x.
9508 - Fix shell error when warning about missing packages in configure
9509 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
9510 - Do not become confused when receiving a spurious VERSIONS-like
9511 cell from a confused v1 client. Bugfix on 0.2.0.x.
9512 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
9513 introduction points for a hidden service have failed. Patch from
9514 Karsten Loesing. Bugfix on 0.2.0.x.
9516 o Code simplifications and refactoring:
9517 - Remove some needless generality from cpuworker code, for improved
9519 - Stop overloading the circuit_t.onionskin field for both "onionskin
9520 from a CREATE cell that we are waiting for a cpuworker to be
9521 assigned" and "onionskin from an EXTEND cell that we are going to
9522 send to an OR as soon as we are connected". Might help with bug 600.
9523 - Add an in-place version of aes_crypt() so that we can avoid doing a
9524 needless memcpy() call on each cell payload.
9527 Changes in version 0.2.0.18-alpha - 2008-01-25
9528 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
9529 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
9530 that can warn or reject connections to ports generally associated with
9531 vulnerable-plaintext protocols.
9533 o New directory authorities:
9534 - Set up dannenberg (run by CCC) as the sixth v3 directory
9538 - Fix a major memory leak when attempting to use the v2 TLS
9539 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
9540 - We accidentally enabled the under-development v2 TLS handshake
9541 code, which was causing log entries like "TLS error while
9542 renegotiating handshake". Disable it again. Resolves bug 590.
9543 - We were computing the wrong Content-Length: header for directory
9544 responses that need to be compressed on the fly, causing clients
9545 asking for those items to always fail. Bugfix on 0.2.0.x; partially
9549 - Avoid going directly to the directory authorities even if you're a
9550 relay, if you haven't found yourself reachable yet or if you've
9551 decided not to advertise your dirport yet. Addresses bug 556.
9552 - If we've gone 12 hours since our last bandwidth check, and we
9553 estimate we have less than 50KB bandwidth capacity but we could
9554 handle more, do another bandwidth test.
9555 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
9556 Tor can warn and/or refuse connections to ports commonly used with
9557 vulnerable-plaintext protocols. Currently we warn on ports 23,
9558 109, 110, and 143, but we don't reject any.
9561 - When we setconf ClientOnly to 1, close any current OR and Dir
9562 listeners. Reported by mwenge.
9563 - When we get a consensus that's been signed by more people than
9564 we expect, don't log about it; it's not a big deal. Reported
9568 - Don't answer "/tor/networkstatus-bridges" directory requests if
9569 the request isn't encrypted.
9570 - Make "ClientOnly 1" config option disable directory ports too.
9571 - Patches from Karsten Loesing to make v2 hidden services more
9572 robust: work even when there aren't enough HSDir relays available;
9573 retry when a v2 rend desc fetch fails; but don't retry if we
9574 already have a usable v0 rend desc.
9577 Changes in version 0.2.0.17-alpha - 2008-01-17
9578 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
9581 - Make the tor-gencert man page get included correctly in the tarball.
9584 Changes in version 0.2.0.16-alpha - 2008-01-17
9585 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
9586 Loesing, and generally cleans up a lot of features and minor bugs.
9588 o New directory authorities:
9589 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
9592 o Major performance improvements:
9593 - Switch our old ring buffer implementation for one more like that
9594 used by free Unix kernels. The wasted space in a buffer with 1mb
9595 of data will now be more like 8k than 1mb. The new implementation
9596 also avoids realloc();realloc(); patterns that can contribute to
9597 memory fragmentation.
9600 - Configuration files now accept C-style strings as values. This
9601 helps encode characters not allowed in the current configuration
9602 file format, such as newline or #. Addresses bug 557.
9603 - Although we fixed bug 539 (where servers would send HTTP status 503
9604 responses _and_ send a body too), there are still servers out
9605 there that haven't upgraded. Therefore, make clients parse such
9606 bodies when they receive them.
9607 - When we're not serving v2 directory information, there is no reason
9608 to actually keep any around. Remove the obsolete files and directory
9609 on startup if they are very old and we aren't going to serve them.
9611 o Minor performance improvements:
9612 - Reference-count and share copies of address policy entries; only 5%
9613 of them were actually distinct.
9614 - Never walk through the list of logs if we know that no log is
9615 interested in a given message.
9618 - When an authority has not signed a consensus, do not try to
9619 download a nonexistent "certificate with key 00000000". Bugfix
9620 on 0.2.0.x. Fixes bug 569.
9621 - Fix a rare assert error when we're closing one of our threads:
9622 use a mutex to protect the list of logs, so we never write to the
9623 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
9624 bug 575, which is kind of the revenge of bug 222.
9625 - Patch from Karsten Loesing to complain less at both the client
9626 and the relay when a relay used to have the HSDir flag but doesn't
9627 anymore, and we try to upload a hidden service descriptor.
9628 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
9630 - Do not try to download missing certificates until we have tried
9631 to check our fallback consensus. Fixes bug 583.
9632 - Make bridges round reported GeoIP stats info up to the nearest
9633 estimate, not down. Now we can distinguish between "0 people from
9634 this country" and "1 person from this country".
9635 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
9636 - Avoid possible segfault if key generation fails in
9637 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
9638 - Avoid segfault in the case where a badly behaved v2 versioning
9639 directory sends a signed networkstatus with missing client-versions.
9641 - Avoid segfaults on certain complex invocations of
9642 router_get_by_hexdigest(). Bugfix on 0.1.2.
9643 - Correct bad index on array access in parse_http_time(). Bugfix
9645 - Fix possible bug in vote generation when server versions are present
9646 but client versions are not.
9647 - Fix rare bug on REDIRECTSTREAM control command when called with no
9648 port set: it could erroneously report an error when none had
9650 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
9651 compressing large objects and find ourselves with more than 4k
9652 left over. Bugfix on 0.2.0.
9653 - Fix a small memory leak when setting up a hidden service.
9654 - Fix a few memory leaks that could in theory happen under bizarre
9656 - Fix an assert if we post a general-purpose descriptor via the
9657 control port but that descriptor isn't mentioned in our current
9658 network consensus. Bug reported by Jon McLachlan; bugfix on
9661 o Minor features (controller):
9662 - Get NS events working again. Patch from tup.
9663 - The GETCONF command now escapes and quotes configuration values
9664 that don't otherwise fit into the torrc file.
9665 - The SETCONF command now handles quoted values correctly.
9667 o Minor features (directory authorities):
9668 - New configuration options to override default maximum number of
9669 servers allowed on a single IP address. This is important for
9670 running a test network on a single host.
9671 - Actually implement the -s option to tor-gencert.
9672 - Add a manual page for tor-gencert.
9674 o Minor features (bridges):
9675 - Bridge authorities no longer serve bridge descriptors over
9676 unencrypted connections.
9678 o Minor features (other):
9679 - Add hidden services and DNSPorts to the list of things that make
9680 Tor accept that it has running ports. Change starting Tor with no
9681 ports from a fatal error to a warning; we might change it back if
9682 this turns out to confuse anybody. Fixes bug 579.
9685 Changes in version 0.1.2.19 - 2008-01-17
9686 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
9687 exit policy a little bit more conservative so it's safer to run an
9688 exit relay on a home system, and fixes a variety of smaller issues.
9691 - Exit policies now reject connections that are addressed to a
9692 relay's public (external) IP address too, unless
9693 ExitPolicyRejectPrivate is turned off. We do this because too
9694 many relays are running nearby to services that trust them based
9698 - When the clock jumps forward a lot, do not allow the bandwidth
9699 buckets to become negative. Fixes bug 544.
9700 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9701 on every successful resolve. Reported by Mike Perry.
9702 - Purge old entries from the "rephist" database and the hidden
9703 service descriptor database even when DirPort is zero.
9704 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9705 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9706 crashing or mis-answering these requests.
9707 - When we decide to send a 503 response to a request for servers, do
9708 not then also send the server descriptors: this defeats the whole
9709 purpose. Fixes bug 539.
9712 - Changing the ExitPolicyRejectPrivate setting should cause us to
9713 rebuild our server descriptor.
9714 - Fix handling of hex nicknames when answering controller requests for
9715 networkstatus by name, or when deciding whether to warn about
9716 unknown routers in a config option. (Patch from mwenge.)
9717 - Fix a couple of hard-to-trigger autoconf problems that could result
9718 in really weird results on platforms whose sys/types.h files define
9719 nonstandard integer types.
9720 - Don't try to create the datadir when running --verify-config or
9721 --hash-password. Resolves bug 540.
9722 - If we were having problems getting a particular descriptor from the
9723 directory caches, and then we learned about a new descriptor for
9724 that router, we weren't resetting our failure count. Reported
9726 - Although we fixed bug 539 (where servers would send HTTP status 503
9727 responses _and_ send a body too), there are still servers out there
9728 that haven't upgraded. Therefore, make clients parse such bodies
9729 when they receive them.
9730 - Run correctly on systems where rlim_t is larger than unsigned long.
9731 This includes some 64-bit systems.
9732 - Run correctly on platforms (like some versions of OS X 10.5) where
9733 the real limit for number of open files is OPEN_FILES, not rlim_max
9734 from getrlimit(RLIMIT_NOFILES).
9735 - Avoid a spurious free on base64 failure.
9736 - Avoid segfaults on certain complex invocations of
9737 router_get_by_hexdigest().
9738 - Fix rare bug on REDIRECTSTREAM control command when called with no
9739 port set: it could erroneously report an error when none had
9743 Changes in version 0.2.0.15-alpha - 2007-12-25
9744 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
9745 features added in 0.2.0.13-alpha.
9748 - Fix several remotely triggerable asserts based on DirPort requests
9749 for a v2 or v3 networkstatus object before we were prepared. This
9750 was particularly bad for 0.2.0.13 and later bridge relays, who
9751 would never have a v2 networkstatus and would thus always crash
9752 when used. Bugfixes on 0.2.0.x.
9753 - Estimate the v3 networkstatus size more accurately, rather than
9754 estimating it at zero bytes and giving it artificially high priority
9755 compared to other directory requests. Bugfix on 0.2.0.x.
9758 - Fix configure.in logic for cross-compilation.
9759 - When we load a bridge descriptor from the cache, and it was
9760 previously unreachable, mark it as retriable so we won't just
9761 ignore it. Also, try fetching a new copy immediately. Bugfixes
9763 - The bridge GeoIP stats were counting other relays, for example
9764 self-reachability and authority-reachability tests.
9767 - Support compilation to target iPhone; patch from cjacker huang.
9768 To build for iPhone, pass the --enable-iphone option to configure.
9771 Changes in version 0.2.0.14-alpha - 2007-12-23
9773 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
9774 without a datadirectory from a previous Tor install. Reported
9776 - Fix a crash when we fetch a descriptor that turns out to be
9777 unexpected (it used to be in our networkstatus when we started
9778 fetching it, but it isn't in our current networkstatus), and we
9779 aren't using bridges. Bugfix on 0.2.0.x.
9780 - Fix a crash when accessing hidden services: it would work the first
9781 time you use a given introduction point for your service, but
9782 on subsequent requests we'd be using garbage memory. Fixed by
9783 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
9784 - Fix a crash when we load a bridge descriptor from disk but we don't
9785 currently have a Bridge line for it in our torrc. Bugfix on
9789 - If bridge authorities set BridgePassword, they will serve a
9790 snapshot of known bridge routerstatuses from their DirPort to
9791 anybody who knows that password. Unset by default.
9794 - Make the unit tests build again.
9795 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
9796 - Make PublishServerDescriptor default to 1, so the default doesn't
9797 have to change as we invent new directory protocol versions.
9798 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
9799 be included unless sys/time.h is already included. Fixes
9800 bug 553. Bugfix on 0.2.0.x.
9801 - If we receive a general-purpose descriptor and then receive an
9802 identical bridge-purpose descriptor soon after, don't discard
9803 the next one as a duplicate.
9806 - If BridgeRelay is set to 1, then the default for
9807 PublishServerDescriptor is now "bridge" rather than "v2,v3".
9808 - If the user sets RelayBandwidthRate but doesn't set
9809 RelayBandwidthBurst, then make them equal rather than erroring out.
9812 Changes in version 0.2.0.13-alpha - 2007-12-21
9813 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
9814 Goodell, fixes many more bugs, and adds a lot of infrastructure for
9817 o New directory authorities:
9818 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
9822 - Only update guard status (usable / not usable) once we have
9823 enough directory information. This was causing us to always pick
9824 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
9825 causing us to discard all our guards on startup if we hadn't been
9826 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
9827 - Purge old entries from the "rephist" database and the hidden
9828 service descriptor databases even when DirPort is zero. Bugfix
9830 - We were ignoring our RelayBandwidthRate for the first 30 seconds
9831 after opening a circuit -- even a relayed circuit. Bugfix on
9833 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
9834 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
9835 crashing or mis-answering these types of requests.
9836 - Relays were publishing their server descriptor to v1 and v2
9837 directory authorities, but they didn't try publishing to v3-only
9838 authorities. Fix this; and also stop publishing to v1 authorities.
9840 - When we were reading router descriptors from cache, we were ignoring
9841 the annotations -- so for example we were reading in bridge-purpose
9842 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
9843 - When we decided to send a 503 response to a request for servers, we
9844 were then also sending the server descriptors: this defeats the
9845 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
9848 - Bridge relays now behave like clients with respect to time
9849 intervals for downloading new consensus documents -- otherwise they
9850 stand out. Bridge users now wait until the end of the interval,
9851 so their bridge relay will be sure to have a new consensus document.
9852 - Three new config options (AlternateDirAuthority,
9853 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
9854 user selectively replace the default directory authorities by type,
9855 rather than the all-or-nothing replacement that DirServer offers.
9856 - Tor can now be configured to read a GeoIP file from disk in one
9857 of two formats. This can be used by controllers to map IP addresses
9858 to countries. Eventually, it may support exit-by-country.
9859 - When possible, bridge relays remember which countries users
9860 are coming from, and report aggregate information in their
9861 extra-info documents, so that the bridge authorities can learn
9862 where Tor is blocked.
9863 - Bridge directory authorities now do reachability testing on the
9864 bridges they know. They provide router status summaries to the
9865 controller via "getinfo ns/purpose/bridge", and also dump summaries
9866 to a file periodically.
9867 - Stop fetching directory info so aggressively if your DirPort is
9868 on but your ORPort is off; stop fetching v2 dir info entirely.
9869 You can override these choices with the new FetchDirInfoEarly
9873 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
9874 consensus documents when there are too many relays at a single
9875 IP address. Now clear it in v2 network status documents too, and
9876 also clear it in routerinfo_t when the relay is no longer listed
9877 in the relevant networkstatus document.
9878 - Don't crash if we get an unexpected value for the
9879 PublishServerDescriptor config option. Reported by Matt Edman;
9880 bugfix on 0.2.0.9-alpha.
9881 - Our new v2 hidden service descriptor format allows descriptors
9882 that have no introduction points. But Tor crashed when we tried
9883 to build a descriptor with no intro points (and it would have
9884 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
9886 - Fix building with dmalloc 5.5.2 with glibc.
9887 - Reject uploaded descriptors and extrainfo documents if they're
9888 huge. Otherwise we'll cache them all over the network and it'll
9889 clog everything up. Reported by Aljosha Judmayer.
9890 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
9891 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
9892 - When the DANGEROUS_VERSION controller status event told us we're
9893 running an obsolete version, it used the string "OLD" to describe
9894 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
9895 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
9896 - If we can't expand our list of entry guards (e.g. because we're
9897 using bridges or we have StrictEntryNodes set), don't mark relays
9898 down when they fail a directory request. Otherwise we're too quick
9899 to mark all our entry points down. Bugfix on 0.1.2.x.
9900 - Fix handling of hex nicknames when answering controller requests for
9901 networkstatus by name, or when deciding whether to warn about unknown
9902 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
9903 - Fix a couple of hard-to-trigger autoconf problems that could result
9904 in really weird results on platforms whose sys/types.h files define
9905 nonstandard integer types. Bugfix on 0.1.2.x.
9906 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
9907 - Don't crash on name lookup when we have no current consensus. Fixes
9908 bug 538; bugfix on 0.2.0.x.
9909 - Only Tors that want to mirror the v2 directory info should
9910 create the "cached-status" directory in their datadir. (All Tors
9911 used to create it.) Bugfix on 0.2.0.9-alpha.
9912 - Directory authorities should only automatically download Extra Info
9913 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
9916 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
9917 consumers. (We already do this on HUP.)
9918 - Authorities and caches fetch the v2 networkstatus documents
9919 less often, now that v3 is encouraged.
9920 - Add a new config option BridgeRelay that specifies you want to
9921 be a bridge relay. Right now the only difference is that it makes
9922 you answer begin_dir requests, and it makes you cache dir info,
9923 even if your DirPort isn't on.
9924 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
9925 ask about source, timestamp of arrival, purpose, etc. We need
9926 something like this to help Vidalia not do GeoIP lookups on bridge
9928 - Allow multiple HashedControlPassword config lines, to support
9929 multiple controller passwords.
9930 - Authorities now decide whether they're authoritative for a given
9931 router based on the router's purpose.
9932 - New config options AuthDirBadDir and AuthDirListBadDirs for
9933 authorities to mark certain relays as "bad directories" in the
9934 networkstatus documents. Also supports the "!baddir" directive in
9935 the approved-routers file.
9938 Changes in version 0.2.0.12-alpha - 2007-11-16
9939 This twelfth development snapshot fixes some more build problems as
9940 well as a few minor bugs.
9943 - Make it build on OpenBSD again. Patch from tup.
9944 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
9945 package-building for Red Hat, OS X, etc.
9947 o Minor bugfixes (on 0.1.2.x):
9948 - Changing the ExitPolicyRejectPrivate setting should cause us to
9949 rebuild our server descriptor.
9951 o Minor bugfixes (on 0.2.0.x):
9952 - When we're lacking a consensus, don't try to perform rendezvous
9953 operations. Reported by Karsten Loesing.
9954 - Fix a small memory leak whenever we decide against using a
9955 newly picked entry guard. Reported by Mike Perry.
9956 - When authorities detected more than two relays running on the same
9957 IP address, they were clearing all the status flags but forgetting
9958 to clear the "hsdir" flag. So clients were being told that a
9959 given relay was the right choice for a v2 hsdir lookup, yet they
9960 never had its descriptor because it was marked as 'not running'
9962 - If we're trying to fetch a bridge descriptor and there's no way
9963 the bridge authority could help us (for example, we don't know
9964 a digest, or there is no bridge authority), don't be so eager to
9965 fall back to asking the bridge authority.
9966 - If we're using bridges or have strictentrynodes set, and our
9967 chosen exit is in the same family as all our bridges/entry guards,
9968 then be flexible about families.
9971 - When we negotiate a v2 link-layer connection (not yet implemented),
9972 accept RELAY_EARLY cells and turn them into RELAY cells if we've
9973 negotiated a v1 connection for their next step. Initial code for
9977 Changes in version 0.2.0.11-alpha - 2007-11-12
9978 This eleventh development snapshot fixes some build problems with
9979 the previous snapshot. It also includes a more secure-by-default exit
9980 policy for relays, fixes an enormous memory leak for exit relays, and
9981 fixes another bug where servers were falling out of the directory list.
9984 - Exit policies now reject connections that are addressed to a
9985 relay's public (external) IP address too, unless
9986 ExitPolicyRejectPrivate is turned off. We do this because too
9987 many relays are running nearby to services that trust them based
9988 on network address. Bugfix on 0.1.2.x.
9991 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
9992 on every successful resolve. Reported by Mike Perry; bugfix
9994 - On authorities, never downgrade to old router descriptors simply
9995 because they're listed in the consensus. This created a catch-22
9996 where we wouldn't list a new descriptor because there was an
9997 old one in the consensus, and we couldn't get the new one in the
9998 consensus because we wouldn't list it. Possible fix for bug 548.
9999 Also, this might cause bug 543 to appear on authorities; if so,
10000 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
10002 o Packaging fixes on 0.2.0.10-alpha:
10003 - We were including instructions about what to do with the
10004 src/config/fallback-consensus file, but we weren't actually
10005 including it in the tarball. Disable all of that for now.
10008 - Allow people to say PreferTunnelledDirConns rather than
10009 PreferTunneledDirConns, for those alternate-spellers out there.
10012 - Don't reevaluate all the information from our consensus document
10013 just because we've downloaded a v2 networkstatus that we intend
10014 to cache. Fixes bug 545; bugfix on 0.2.0.x.
10017 Changes in version 0.2.0.10-alpha - 2007-11-10
10018 This tenth development snapshot adds a third v3 directory authority
10019 run by Mike Perry, adds most of Karsten Loesing's new hidden service
10020 descriptor format, fixes a bad crash bug and new bridge bugs introduced
10021 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
10022 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
10023 addresses many more minor issues.
10025 o New directory authorities:
10026 - Set up ides (run by Mike Perry) as the third v3 directory authority.
10029 - Allow tunnelled directory connections to ask for an encrypted
10030 "begin_dir" connection or an anonymized "uses a full Tor circuit"
10031 connection independently. Now we can make anonymized begin_dir
10032 connections for (e.g.) more secure hidden service posting and
10034 - More progress on proposal 114: code from Karsten Loesing to
10035 implement new hidden service descriptor format.
10036 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
10037 accommodate the growing number of servers that use the default
10038 and are reaching it.
10039 - Directory authorities use a new formula for selecting which nodes
10040 to advertise as Guards: they must be in the top 7/8 in terms of
10041 how long we have known about them, and above the median of those
10042 nodes in terms of weighted fractional uptime.
10043 - Make "not enough dir info yet" warnings describe *why* Tor feels
10044 it doesn't have enough directory info yet.
10047 - Stop servers from crashing if they set a Family option (or
10048 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
10050 - Make bridge users work again -- the move to v3 directories in
10051 0.2.0.9-alpha had introduced a number of bugs that made bridges
10052 no longer work for clients.
10053 - When the clock jumps forward a lot, do not allow the bandwidth
10054 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
10056 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
10057 - When the consensus lists a router descriptor that we previously were
10058 mirroring, but that we considered non-canonical, reload the
10059 descriptor as canonical. This fixes bug 543 where Tor servers
10060 would start complaining after a few days that they don't have
10061 enough directory information to build a circuit.
10062 - Consider replacing the current consensus when certificates arrive
10063 that make the pending consensus valid. Previously, we were only
10064 considering replacement when the new certs _didn't_ help.
10065 - Fix an assert error on startup if we didn't already have the
10066 consensus and certs cached in our datadirectory: we were caching
10067 the consensus in consensus_waiting_for_certs but then free'ing it
10069 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
10070 Request) if we need more v3 certs but we've already got pending
10071 requests for all of them.
10072 - Correctly back off from failing certificate downloads. Fixes
10074 - Authorities don't vote on the Running flag if they have been running
10075 for less than 30 minutes themselves. Fixes bug 547, where a newly
10076 started authority would vote that everyone was down.
10078 o New requirements:
10079 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
10080 it, it had no AES, and it hasn't seen any security patches since
10084 - Clients now hold circuitless TLS connections open for 1.5 times
10085 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
10086 rebuild a new circuit over them within that timeframe. Previously,
10087 they held them open only for KeepalivePeriod (5 minutes).
10088 - Use "If-Modified-Since" to avoid retrieving consensus
10089 networkstatuses that we already have.
10090 - When we have no consensus, check FallbackNetworkstatusFile (defaults
10091 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
10092 we start knowing some directory caches.
10093 - When we receive a consensus from the future, warn about skew.
10094 - Improve skew reporting: try to give the user a better log message
10095 about how skewed they are, and how much this matters.
10096 - When we have a certificate for an authority, believe that
10097 certificate's claims about the authority's IP address.
10098 - New --quiet command-line option to suppress the default console log.
10099 Good in combination with --hash-password.
10100 - Authorities send back an X-Descriptor-Not-New header in response to
10101 an accepted-but-discarded descriptor upload. Partially implements
10103 - Make the log message for "tls error. breaking." more useful.
10104 - Better log messages about certificate downloads, to attempt to
10105 track down the second incarnation of bug 546.
10107 o Minor features (bridges):
10108 - If bridge users set UpdateBridgesFromAuthority, but the digest
10109 they ask for is a 404 from the bridge authority, they now fall
10110 back to trying the bridge directly.
10111 - Bridges now use begin_dir to publish their server descriptor to
10112 the bridge authority, even when they haven't set TunnelDirConns.
10114 o Minor features (controller):
10115 - When reporting clock skew, and we know that the clock is _at least
10116 as skewed_ as some value, but we don't know the actual value,
10117 report the value as a "minimum skew."
10120 - Update linux-tor-prio.sh script to allow QoS based on the uid of
10121 the Tor process. Patch from Marco Bonetti with tweaks from Mike
10125 - Refuse to start if both ORPort and UseBridges are set. Bugfix
10126 on 0.2.0.x, suggested by Matt Edman.
10127 - Don't stop fetching descriptors when FetchUselessDescriptors is
10128 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
10129 reported by tup and ioerror.
10130 - Better log message on vote from unknown authority.
10131 - Don't log "Launching 0 request for 0 router" message.
10133 o Minor bugfixes (memory leaks):
10134 - Stop leaking memory every time we parse a v3 certificate. Bugfix
10136 - Stop leaking memory every time we load a v3 certificate. Bugfix
10137 on 0.2.0.1-alpha. Fixes bug 536.
10138 - Stop leaking a cached networkstatus on exit. Bugfix on
10140 - Stop leaking voter information every time we free a consensus.
10141 Bugfix on 0.2.0.3-alpha.
10142 - Stop leaking signed data every time we check a voter signature.
10143 Bugfix on 0.2.0.3-alpha.
10144 - Stop leaking a signature every time we fail to parse a consensus or
10145 a vote. Bugfix on 0.2.0.3-alpha.
10146 - Stop leaking v2_download_status_map on shutdown. Bugfix on
10148 - Stop leaking conn->nickname every time we make a connection to a
10149 Tor relay without knowing its expected identity digest (e.g. when
10150 using bridges). Bugfix on 0.2.0.3-alpha.
10152 - Minor bugfixes (portability):
10153 - Run correctly on platforms where rlim_t is larger than unsigned
10154 long, and/or where the real limit for number of open files is
10155 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
10156 particular, these may be needed for OS X 10.5.
10159 Changes in version 0.1.2.18 - 2007-10-28
10160 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
10161 hidden service introduction that were causing huge delays, and a big
10162 bug that was causing some servers to disappear from the network status
10163 lists for a few hours each day.
10165 o Major bugfixes (crashes):
10166 - If a connection is shut down abruptly because of something that
10167 happened inside connection_flushed_some(), do not call
10168 connection_finished_flushing(). Should fix bug 451:
10169 "connection_stop_writing: Assertion conn->write_event failed"
10170 Bugfix on 0.1.2.7-alpha.
10171 - Fix possible segfaults in functions called from
10172 rend_process_relay_cell().
10174 o Major bugfixes (hidden services):
10175 - Hidden services were choosing introduction points uniquely by
10176 hexdigest, but when constructing the hidden service descriptor
10177 they merely wrote the (potentially ambiguous) nickname.
10178 - Clients now use the v2 intro format for hidden service
10179 connections: they specify their chosen rendezvous point by identity
10180 digest rather than by (potentially ambiguous) nickname. These
10181 changes could speed up hidden service connections dramatically.
10183 o Major bugfixes (other):
10184 - Stop publishing a new server descriptor just because we get a
10185 HUP signal. This led (in a roundabout way) to some servers getting
10186 dropped from the networkstatus lists for a few hours each day.
10187 - When looking for a circuit to cannibalize, consider family as well
10188 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10189 circuit cannibalization).
10190 - When a router wasn't listed in a new networkstatus, we were leaving
10191 the flags for that router alone -- meaning it remained Named,
10192 Running, etc -- even though absence from the networkstatus means
10193 that it shouldn't be considered to exist at all anymore. Now we
10194 clear all the flags for routers that fall out of the networkstatus
10195 consensus. Fixes bug 529.
10198 - Don't try to access (or alter) the state file when running
10199 --list-fingerprint or --verify-config or --hash-password. Resolves
10201 - When generating information telling us how to extend to a given
10202 router, do not try to include the nickname if it is
10203 absent. Resolves bug 467.
10204 - Fix a user-triggerable segfault in expand_filename(). (There isn't
10205 a way to trigger this remotely.)
10206 - When sending a status event to the controller telling it that an
10207 OR address is reachable, set the port correctly. (Previously we
10208 were reporting the dir port.)
10209 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10210 command. Bugfix on 0.1.2.17.
10211 - When loading bandwidth history, do not believe any information in
10212 the future. Fixes bug 434.
10213 - When loading entry guard information, do not believe any information
10215 - When we have our clock set far in the future and generate an
10216 onion key, then re-set our clock to be correct, we should not stop
10217 the onion key from getting rotated.
10218 - On some platforms, accept() can return a broken address. Detect
10219 this more quietly, and deal accordingly. Fixes bug 483.
10220 - It's not actually an error to find a non-pending entry in the DNS
10221 cache when canceling a pending resolve. Don't log unless stuff
10222 is fishy. Resolves bug 463.
10223 - Don't reset trusted dir server list when we set a configuration
10224 option. Patch from Robert Hogan.
10225 - Don't try to create the datadir when running --verify-config or
10226 --hash-password. Resolves bug 540.
10229 Changes in version 0.2.0.9-alpha - 2007-10-24
10230 This ninth development snapshot switches clients to the new v3 directory
10231 system; allows servers to be listed in the network status even when they
10232 have the same nickname as a registered server; and fixes many other
10233 bugs including a big one that was causing some servers to disappear
10234 from the network status lists for a few hours each day.
10236 o Major features (directory system):
10237 - Clients now download v3 consensus networkstatus documents instead
10238 of v2 networkstatus documents. Clients and caches now base their
10239 opinions about routers on these consensus documents. Clients only
10240 download router descriptors listed in the consensus.
10241 - Authorities now list servers who have the same nickname as
10242 a different named server, but list them with a new flag,
10243 "Unnamed". Now we can list servers that happen to pick the same
10244 nickname as a server that registered two years ago and then
10245 disappeared. Partially implements proposal 122.
10246 - If the consensus lists a router as "Unnamed", the name is assigned
10247 to a different router: do not identify the router by that name.
10248 Partially implements proposal 122.
10249 - Authorities can now come to a consensus on which method to use to
10250 compute the consensus. This gives us forward compatibility.
10253 - Stop publishing a new server descriptor just because we HUP or
10254 when we find our DirPort to be reachable but won't actually publish
10255 it. New descriptors without any real changes are dropped by the
10256 authorities, and can screw up our "publish every 18 hours" schedule.
10258 - When a router wasn't listed in a new networkstatus, we were leaving
10259 the flags for that router alone -- meaning it remained Named,
10260 Running, etc -- even though absence from the networkstatus means
10261 that it shouldn't be considered to exist at all anymore. Now we
10262 clear all the flags for routers that fall out of the networkstatus
10263 consensus. Fixes bug 529; bugfix on 0.1.2.x.
10264 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
10265 extrainfo documents and then discard them immediately for not
10266 matching the latest router. Bugfix on 0.2.0.1-alpha.
10268 o Minor features (v3 directory protocol):
10269 - Allow tor-gencert to generate a new certificate without replacing
10271 - Allow certificates to include an address.
10272 - When we change our directory-cache settings, reschedule all voting
10273 and download operations.
10274 - Reattempt certificate downloads immediately on failure, as long as
10275 we haven't failed a threshold number of times yet.
10276 - Delay retrying consensus downloads while we're downloading
10277 certificates to verify the one we just got. Also, count getting a
10278 consensus that we already have (or one that isn't valid) as a failure,
10279 and count failing to get the certificates after 20 minutes as a
10281 - Build circuits and download descriptors even if our consensus is a
10282 little expired. (This feature will go away once authorities are
10285 o Minor features (router descriptor cache):
10286 - If we find a cached-routers file that's been sitting around for more
10287 than 28 days unmodified, then most likely it's a leftover from
10288 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
10290 - When we (as a cache) download a descriptor because it was listed
10291 in a consensus, remember when the consensus was supposed to expire,
10292 and don't expire the descriptor until then.
10294 o Minor features (performance):
10295 - Call routerlist_remove_old_routers() much less often. This should
10296 speed startup, especially on directory caches.
10297 - Don't try to launch new descriptor downloads quite so often when we
10298 already have enough directory information to build circuits.
10299 - Base64 decoding was actually showing up on our profile when parsing
10300 the initial descriptor file; switch to an in-process all-at-once
10301 implementation that's about 3.5x times faster than calling out to
10304 o Minor features (compilation):
10305 - Detect non-ASCII platforms (if any still exist) and refuse to
10306 build there: some of our code assumes that 'A' is 65 and so on.
10308 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
10309 - Make the "next period" votes into "current period" votes immediately
10310 after publishing the consensus; avoid a heisenbug that made them
10311 stick around indefinitely.
10312 - When we discard a vote as a duplicate, do not report this as
10314 - Treat missing v3 keys or certificates as an error when running as a
10315 v3 directory authority.
10316 - When we're configured to be a v3 authority, but we're only listed
10317 as a non-v3 authority in our DirServer line for ourself, correct
10319 - If an authority doesn't have a qualified hostname, just put
10320 its address in the vote. This fixes the problem where we referred to
10321 "moria on moria:9031."
10322 - Distinguish between detached signatures for the wrong period, and
10323 detached signatures for a divergent vote.
10324 - Fix a small memory leak when computing a consensus.
10325 - When there's no concensus, we were forming a vote every 30
10326 minutes, but writing the "valid-after" line in our vote based
10327 on our configured V3AuthVotingInterval: so unless the intervals
10328 matched up, we immediately rejected our own vote because it didn't
10329 start at the voting interval that caused us to construct a vote.
10331 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
10332 - Delete unverified-consensus when the real consensus is set.
10333 - Consider retrying a consensus networkstatus fetch immediately
10334 after one fails: don't wait 60 seconds to notice.
10335 - When fetching a consensus as a cache, wait until a newer consensus
10336 should exist before trying to replace the current one.
10337 - Use a more forgiving schedule for retrying failed consensus
10338 downloads than for other types.
10340 o Minor bugfixes (other directory issues):
10341 - Correct the implementation of "download votes by digest." Bugfix on
10343 - Authorities no longer send back "400 you're unreachable please fix
10344 it" errors to Tor servers that aren't online all the time. We're
10345 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
10347 o Minor bugfixes (controller):
10348 - Don't reset trusted dir server list when we set a configuration
10349 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
10350 - Respond to INT and TERM SIGNAL commands before we execute the
10351 signal, in case the signal shuts us down. We had a patch in
10352 0.1.2.1-alpha that tried to do this by queueing the response on
10353 the connection's buffer before shutting down, but that really
10354 isn't the same thing at all. Bug located by Matt Edman.
10356 o Minor bugfixes (misc):
10357 - Correctly check for bad options to the "PublishServerDescriptor"
10358 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
10359 - Stop leaking memory on failing case of base32_decode, and make
10360 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
10361 - Don't try to download extrainfo documents when we're trying to
10362 fetch enough directory info to build a circuit: having enough
10363 info should get priority. Bugfix on 0.2.0.x.
10364 - Don't complain that "your server has not managed to confirm that its
10365 ports are reachable" if we haven't been able to build any circuits
10366 yet. Bug found by spending four hours without a v3 consensus. Bugfix
10368 - Detect the reason for failing to mmap a descriptor file we just
10369 wrote, and give a more useful log message. Fixes bug 533. Bugfix
10372 o Code simplifications and refactoring:
10373 - Remove support for the old bw_accounting file: we've been storing
10374 bandwidth accounting information in the state file since
10375 0.1.2.5-alpha. This may result in bandwidth accounting errors
10376 if you try to upgrade from 0.1.1.x or earlier, or if you try to
10377 downgrade to 0.1.1.x or earlier.
10378 - New convenience code to locate a file within the DataDirectory.
10379 - Move non-authority functionality out of dirvote.c.
10380 - Refactor the arguments for router_pick_{directory_|trusteddir}server
10381 so that they all take the same named flags.
10384 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
10385 Unix users an easy way to script their Tor process (e.g. by
10386 adjusting bandwidth based on the time of the day).
10389 Changes in version 0.2.0.8-alpha - 2007-10-12
10390 This eighth development snapshot fixes a crash bug that's been bothering
10391 us since February 2007, lets bridge authorities store a list of bridge
10392 descriptors they've seen, gets v3 directory voting closer to working,
10393 starts caching v3 directory consensus documents on directory mirrors,
10394 and fixes a variety of smaller issues including some minor memory leaks.
10396 o Major features (router descriptor cache):
10397 - Store routers in a file called cached-descriptors instead of in
10398 cached-routers. Initialize cached-descriptors from cached-routers
10399 if the old format is around. The new format allows us to store
10400 annotations along with descriptors.
10401 - Use annotations to record the time we received each descriptor, its
10402 source, and its purpose.
10403 - Disable the SETROUTERPURPOSE controller command: it is now
10405 - Controllers should now specify cache=no or cache=yes when using
10406 the +POSTDESCRIPTOR command.
10407 - Bridge authorities now write bridge descriptors to disk, meaning
10408 we can export them to other programs and begin distributing them
10411 o Major features (directory authorities):
10412 - When a v3 authority is missing votes or signatures, it now tries
10414 - Directory authorities track weighted fractional uptime as well as
10415 weighted mean-time-between failures. WFU is suitable for deciding
10416 whether a node is "usually up", while MTBF is suitable for deciding
10417 whether a node is "likely to stay up." We need both, because
10418 "usually up" is a good requirement for guards, while "likely to
10419 stay up" is a good requirement for long-lived connections.
10421 o Major features (v3 directory system):
10422 - Caches now download v3 network status documents as needed,
10423 and download the descriptors listed in them.
10424 - All hosts now attempt to download and keep fresh v3 authority
10425 certificates, and re-attempt after failures.
10426 - More internal-consistency checks for vote parsing.
10428 o Major bugfixes (crashes):
10429 - If a connection is shut down abruptly because of something that
10430 happened inside connection_flushed_some(), do not call
10431 connection_finished_flushing(). Should fix bug 451. Bugfix on
10434 o Major bugfixes (performance):
10435 - Fix really bad O(n^2) performance when parsing a long list of
10436 routers: Instead of searching the entire list for an "extra-info "
10437 string which usually wasn't there, once for every routerinfo
10438 we read, just scan lines forward until we find one we like.
10440 - When we add data to a write buffer in response to the data on that
10441 write buffer getting low because of a flush, do not consider the
10442 newly added data as a candidate for immediate flushing, but rather
10443 make it wait until the next round of writing. Otherwise, we flush
10444 and refill recursively, and a single greedy TLS connection can
10445 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
10447 o Minor features (v3 authority system):
10448 - Add more ways for tools to download the votes that lead to the
10450 - Send a 503 when low on bandwidth and a vote, consensus, or
10451 certificate is requested.
10452 - If-modified-since is now implemented properly for all kinds of
10453 certificate requests.
10455 o Minor bugfixes (network statuses):
10456 - Tweak the implementation of proposal 109 slightly: allow at most
10457 two Tor servers on the same IP address, except if it's the location
10458 of a directory authority, in which case allow five. Bugfix on
10461 o Minor bugfixes (controller):
10462 - When sending a status event to the controller telling it that an
10463 OR address is reachable, set the port correctly. (Previously we
10464 were reporting the dir port.) Bugfix on 0.1.2.x.
10466 o Minor bugfixes (v3 directory system):
10467 - Fix logic to look up a cert by its signing key digest. Bugfix on
10469 - Only change the reply to a vote to "OK" if it's not already
10470 set. This gets rid of annoying "400 OK" log messages, which may
10471 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
10472 - When we get a valid consensus, recompute the voting schedule.
10473 - Base the valid-after time of a vote on the consensus voting
10474 schedule, not on our preferred schedule.
10475 - Make the return values and messages from signature uploads and
10476 downloads more sensible.
10477 - Fix a memory leak when serving votes and consensus documents, and
10478 another when serving certificates.
10480 o Minor bugfixes (performance):
10481 - Use a slightly simpler string hashing algorithm (copying Python's
10482 instead of Java's) and optimize our digest hashing algorithm to take
10483 advantage of 64-bit platforms and to remove some possibly-costly
10485 - Fix a minor memory leak whenever we parse guards from our state
10486 file. Bugfix on 0.2.0.7-alpha.
10487 - Fix a minor memory leak whenever we write out a file. Bugfix on
10489 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
10490 command. Bugfix on 0.2.0.5-alpha.
10492 o Minor bugfixes (portability):
10493 - On some platforms, accept() can return a broken address. Detect
10494 this more quietly, and deal accordingly. Fixes bug 483.
10495 - Stop calling tor_strlower() on uninitialized memory in some cases.
10496 Bugfix in 0.2.0.7-alpha.
10498 o Minor bugfixes (usability):
10499 - Treat some 403 responses from directory servers as INFO rather than
10500 WARN-severity events.
10501 - It's not actually an error to find a non-pending entry in the DNS
10502 cache when canceling a pending resolve. Don't log unless stuff is
10503 fishy. Resolves bug 463.
10505 o Minor bugfixes (anonymity):
10506 - Never report that we've used more bandwidth than we're willing to
10507 relay: it leaks how much non-relay traffic we're using. Resolves
10509 - When looking for a circuit to cannibalize, consider family as well
10510 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
10511 circuit cannibalization).
10513 o Code simplifications and refactoring:
10514 - Make a bunch of functions static. Remove some dead code.
10515 - Pull out about a third of the really big routerlist.c; put it in a
10516 new module, networkstatus.c.
10517 - Merge the extra fields in local_routerstatus_t back into
10518 routerstatus_t: we used to need one routerstatus_t for each
10519 authority's opinion, plus a local_routerstatus_t for the locally
10520 computed consensus opinion. To save space, we put the locally
10521 modified fields into local_routerstatus_t, and only the common
10522 stuff into routerstatus_t. But once v3 directories are in use,
10523 clients and caches will no longer need to hold authority opinions;
10524 thus, the rationale for keeping the types separate is now gone.
10525 - Make the code used to reschedule and reattempt downloads more
10527 - Turn all 'Are we a directory server/mirror?' logic into a call to
10529 - Remove the code to generate the oldest (v1) directory format.
10530 The code has been disabled since 0.2.0.5-alpha.
10533 Changes in version 0.2.0.7-alpha - 2007-09-21
10534 This seventh development snapshot makes bridges work again, makes bridge
10535 authorities work for the first time, fixes two huge performance flaws
10536 in hidden services, and fixes a variety of minor issues.
10538 o New directory authorities:
10539 - Set up moria1 and tor26 as the first v3 directory authorities. See
10540 doc/spec/dir-spec.txt for details on the new directory design.
10542 o Major bugfixes (crashes):
10543 - Fix possible segfaults in functions called from
10544 rend_process_relay_cell(). Bugfix on 0.1.2.x.
10546 o Major bugfixes (bridges):
10547 - Fix a bug that made servers send a "404 Not found" in response to
10548 attempts to fetch their server descriptor. This caused Tor servers
10549 to take many minutes to establish reachability for their DirPort,
10550 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
10551 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
10552 users configure that and specify a bridge with an identity
10553 fingerprint, now they will lookup the bridge descriptor at the
10554 default bridge authority via a one-hop tunnel, but once circuits
10555 are established they will switch to a three-hop tunnel for later
10556 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
10558 o Major bugfixes (hidden services):
10559 - Hidden services were choosing introduction points uniquely by
10560 hexdigest, but when constructing the hidden service descriptor
10561 they merely wrote the (potentially ambiguous) nickname.
10562 - Clients now use the v2 intro format for hidden service
10563 connections: they specify their chosen rendezvous point by identity
10564 digest rather than by (potentially ambiguous) nickname. Both
10565 are bugfixes on 0.1.2.x, and they could speed up hidden service
10566 connections dramatically. Thanks to Karsten Loesing.
10568 o Minor features (security):
10569 - As a client, do not believe any server that tells us that an
10570 address maps to an internal address space.
10571 - Make it possible to enable HashedControlPassword and
10572 CookieAuthentication at the same time.
10574 o Minor features (guard nodes):
10575 - Tag every guard node in our state file with the version that
10576 we believe added it, or with our own version if we add it. This way,
10577 if a user temporarily runs an old version of Tor and then switches
10578 back to a new one, she doesn't automatically lose her guards.
10580 o Minor features (speed):
10581 - When implementing AES counter mode, update only the portions of the
10582 counter buffer that need to change, and don't keep separate
10583 network-order and host-order counters when they are the same (i.e.,
10584 on big-endian hosts.)
10586 o Minor features (controller):
10587 - Accept LF instead of CRLF on controller, since some software has a
10588 hard time generating real Internet newlines.
10589 - Add GETINFO values for the server status events
10590 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
10593 o Removed features:
10594 - Routers no longer include bandwidth-history lines in their
10595 descriptors; this information is already available in extra-info
10596 documents, and including it in router descriptors took up 60%
10597 (!) of compressed router descriptor downloads. Completes
10598 implementation of proposal 104.
10599 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
10600 and TorControl.py, as they use the old v0 controller protocol,
10601 and are obsoleted by TorFlow anyway.
10602 - Drop support for v1 rendezvous descriptors, since we never used
10603 them anyway, and the code has probably rotted by now. Based on
10604 patch from Karsten Loesing.
10605 - On OSX, stop warning the user that kqueue support in libevent is
10606 "experimental", since it seems to have worked fine for ages.
10609 - When generating information telling us how to extend to a given
10610 router, do not try to include the nickname if it is absent. Fixes
10611 bug 467. Bugfix on 0.2.0.3-alpha.
10612 - Fix a user-triggerable (but not remotely-triggerable) segfault
10613 in expand_filename(). Bugfix on 0.1.2.x.
10614 - Fix a memory leak when freeing incomplete requests from DNSPort.
10615 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
10616 - Don't try to access (or alter) the state file when running
10617 --list-fingerprint or --verify-config or --hash-password. (Resolves
10618 bug 499.) Bugfix on 0.1.2.x.
10619 - Servers used to decline to publish their DirPort if their
10620 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
10621 were below a threshold. Now they only look at BandwidthRate and
10622 RelayBandwidthRate. Bugfix on 0.1.2.x.
10623 - Remove an optimization in the AES counter-mode code that assumed
10624 that the counter never exceeded 2^68. When the counter can be set
10625 arbitrarily as an IV (as it is by Karsten's new hidden services
10626 code), this assumption no longer holds. Bugfix on 0.1.2.x.
10627 - Resume listing "AUTHORITY" flag for authorities in network status.
10628 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
10630 o Code simplifications and refactoring:
10631 - Revamp file-writing logic so we don't need to have the entire
10632 contents of a file in memory at once before we write to disk. Tor,
10634 - Turn "descriptor store" into a full-fledged type.
10635 - Move all NT services code into a separate source file.
10636 - Unify all code that computes medians, percentile elements, etc.
10637 - Get rid of a needless malloc when parsing address policies.
10640 Changes in version 0.1.2.17 - 2007-08-30
10641 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
10642 X bundles. Vidalia 0.0.14 makes authentication required for the
10643 ControlPort in the default configuration, which addresses important
10644 security risks. Everybody who uses Vidalia (or another controller)
10647 In addition, this Tor update fixes major load balancing problems with
10648 path selection, which should speed things up a lot once many people
10651 o Major bugfixes (security):
10652 - We removed support for the old (v0) control protocol. It has been
10653 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
10654 become more of a headache than it's worth.
10656 o Major bugfixes (load balancing):
10657 - When choosing nodes for non-guard positions, weight guards
10658 proportionally less, since they already have enough load. Patch
10660 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10661 will allow fast Tor servers to get more attention.
10662 - When we're upgrading from an old Tor version, forget our current
10663 guards and pick new ones according to the new weightings. These
10664 three load balancing patches could raise effective network capacity
10665 by a factor of four. Thanks to Mike Perry for measurements.
10667 o Major bugfixes (stream expiration):
10668 - Expire not-yet-successful application streams in all cases if
10669 they've been around longer than SocksTimeout. Right now there are
10670 some cases where the stream will live forever, demanding a new
10671 circuit every 15 seconds. Fixes bug 454; reported by lodger.
10673 o Minor features (controller):
10674 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10675 is valid before any authentication has been received. It tells
10676 a controller what kind of authentication is expected, and what
10677 protocol is spoken. Implements proposal 119.
10679 o Minor bugfixes (performance):
10680 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
10681 greatly speeding up loading cached-routers from disk on startup.
10682 - Disable sentinel-based debugging for buffer code: we squashed all
10683 the bugs that this was supposed to detect a long time ago, and now
10684 its only effect is to change our buffer sizes from nice powers of
10685 two (which platform mallocs tend to like) to values slightly over
10686 powers of two (which make some platform mallocs sad).
10688 o Minor bugfixes (misc):
10689 - If exit bandwidth ever exceeds one third of total bandwidth, then
10690 use the correct formula to weight exit nodes when choosing paths.
10691 Based on patch from Mike Perry.
10692 - Choose perfectly fairly among routers when choosing by bandwidth and
10693 weighting by fraction of bandwidth provided by exits. Previously, we
10694 would choose with only approximate fairness, and correct ourselves
10695 if we ran off the end of the list.
10696 - If we require CookieAuthentication but we fail to write the
10697 cookie file, we would warn but not exit, and end up in a state
10698 where no controller could authenticate. Now we exit.
10699 - If we require CookieAuthentication, stop generating a new cookie
10700 every time we change any piece of our config.
10701 - Refuse to start with certain directory authority keys, and
10702 encourage people using them to stop.
10703 - Terminate multi-line control events properly. Original patch
10705 - Fix a minor memory leak when we fail to find enough suitable
10706 servers to choose a circuit.
10707 - Stop leaking part of the descriptor when we run into a particularly
10708 unparseable piece of it.
10711 Changes in version 0.2.0.6-alpha - 2007-08-26
10712 This sixth development snapshot features a new Vidalia version in the
10713 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
10714 the ControlPort in the default configuration, which addresses important
10717 In addition, this snapshot fixes major load balancing problems
10718 with path selection, which should speed things up a lot once many
10719 people have upgraded. The directory authorities also use a new
10720 mean-time-between-failure approach to tracking which servers are stable,
10721 rather than just looking at the most recent uptime.
10723 o New directory authorities:
10724 - Set up Tonga as the default bridge directory authority.
10727 - Directory authorities now track servers by weighted
10728 mean-times-between-failures. When we have 4 or more days of data,
10729 use measured MTBF rather than declared uptime to decide whether
10730 to call a router Stable. Implements proposal 108.
10732 o Major bugfixes (load balancing):
10733 - When choosing nodes for non-guard positions, weight guards
10734 proportionally less, since they already have enough load. Patch
10736 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
10737 will allow fast Tor servers to get more attention.
10738 - When we're upgrading from an old Tor version, forget our current
10739 guards and pick new ones according to the new weightings. These
10740 three load balancing patches could raise effective network capacity
10741 by a factor of four. Thanks to Mike Perry for measurements.
10743 o Major bugfixes (descriptor parsing):
10744 - Handle unexpected whitespace better in malformed descriptors. Bug
10745 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
10748 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
10749 GETINFO for Torstat to use until it can switch to using extrainfos.
10750 - Optionally (if built with -DEXPORTMALLINFO) export the output
10751 of mallinfo via http, as tor/mallinfo.txt. Only accessible
10755 - Do not intermix bridge routers with controller-added
10756 routers. (Bugfix on 0.2.0.x)
10757 - Do not fail with an assert when accept() returns an unexpected
10758 address family. Addresses but does not wholly fix bug 483. (Bugfix
10760 - Let directory authorities startup even when they can't generate
10761 a descriptor immediately, e.g. because they don't know their
10763 - Stop putting the authentication cookie in a file called "0"
10764 in your working directory if you don't specify anything for the
10765 new CookieAuthFile option. Reported by Matt Edman.
10766 - Make it possible to read the PROTOCOLINFO response in a way that
10767 conforms to our control-spec. Reported by Matt Edman.
10768 - Fix a minor memory leak when we fail to find enough suitable
10769 servers to choose a circuit. Bugfix on 0.1.2.x.
10770 - Stop leaking part of the descriptor when we run into a particularly
10771 unparseable piece of it. Bugfix on 0.1.2.x.
10772 - Unmap the extrainfo cache file on exit.
10775 Changes in version 0.2.0.5-alpha - 2007-08-19
10776 This fifth development snapshot fixes compilation on Windows again;
10777 fixes an obnoxious client-side bug that slowed things down and put
10778 extra load on the network; gets us closer to using the v3 directory
10779 voting scheme; makes it easier for Tor controllers to use cookie-based
10780 authentication; and fixes a variety of other bugs.
10782 o Removed features:
10783 - Version 1 directories are no longer generated in full. Instead,
10784 authorities generate and serve "stub" v1 directories that list
10785 no servers. This will stop Tor versions 0.1.0.x and earlier from
10786 working, but (for security reasons) nobody should be running those
10789 o Major bugfixes (compilation, 0.2.0.x):
10790 - Try to fix Win32 compilation again: improve checking for IPv6 types.
10791 - Try to fix MSVC compilation: build correctly on platforms that do
10792 not define s6_addr16 or s6_addr32.
10793 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
10796 o Major bugfixes (stream expiration):
10797 - Expire not-yet-successful application streams in all cases if
10798 they've been around longer than SocksTimeout. Right now there are
10799 some cases where the stream will live forever, demanding a new
10800 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
10801 reported by lodger.
10803 o Minor features (directory servers):
10804 - When somebody requests a list of statuses or servers, and we have
10805 none of those, return a 404 rather than an empty 200.
10807 o Minor features (directory voting):
10808 - Store v3 consensus status consensuses on disk, and reload them
10811 o Minor features (security):
10812 - Warn about unsafe ControlPort configurations.
10813 - Refuse to start with certain directory authority keys, and
10814 encourage people using them to stop.
10816 o Minor features (controller):
10817 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
10818 is valid before any authentication has been received. It tells
10819 a controller what kind of authentication is expected, and what
10820 protocol is spoken. Implements proposal 119.
10821 - New config option CookieAuthFile to choose a new location for the
10822 cookie authentication file, and config option
10823 CookieAuthFileGroupReadable to make it group-readable.
10825 o Minor features (unit testing):
10826 - Add command-line arguments to unit-test executable so that we can
10827 invoke any chosen test from the command line rather than having
10828 to run the whole test suite at once; and so that we can turn on
10829 logging for the unit tests.
10831 o Minor bugfixes (on 0.1.2.x):
10832 - If we require CookieAuthentication but we fail to write the
10833 cookie file, we would warn but not exit, and end up in a state
10834 where no controller could authenticate. Now we exit.
10835 - If we require CookieAuthentication, stop generating a new cookie
10836 every time we change any piece of our config.
10837 - When loading bandwidth history, do not believe any information in
10838 the future. Fixes bug 434.
10839 - When loading entry guard information, do not believe any information
10841 - When we have our clock set far in the future and generate an
10842 onion key, then re-set our clock to be correct, we should not stop
10843 the onion key from getting rotated.
10844 - Clean up torrc sample config file.
10845 - Do not automatically run configure from autogen.sh. This
10846 non-standard behavior tended to annoy people who have built other
10849 o Minor bugfixes (on 0.2.0.x):
10850 - Fix a bug with AutomapHostsOnResolve that would always cause
10851 the second request to fail. Bug reported by Kate. Bugfix on
10853 - Fix a bug in ADDRMAP controller replies that would sometimes
10854 try to print a NULL. Patch from tup.
10855 - Read v3 directory authority keys from the right location.
10856 - Numerous bugfixes to directory voting code.
10859 Changes in version 0.1.2.16 - 2007-08-01
10860 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
10861 remote attacker in certain situations to rewrite the user's torrc
10862 configuration file. This can completely compromise anonymity of users
10863 in most configurations, including those running the Vidalia bundles,
10864 TorK, etc. Or worse.
10866 o Major security fixes:
10867 - Close immediately after missing authentication on control port;
10868 do not allow multiple authentication attempts.
10871 Changes in version 0.2.0.4-alpha - 2007-08-01
10872 This fourth development snapshot fixes a critical security vulnerability
10873 for most users, specifically those running Vidalia, TorK, etc. Everybody
10874 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
10876 o Major security fixes:
10877 - Close immediately after missing authentication on control port;
10878 do not allow multiple authentication attempts.
10880 o Major bugfixes (compilation):
10881 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
10884 o Minor features (performance):
10885 - Be even more aggressive about releasing RAM from small
10886 empty buffers. Thanks to our free-list code, this shouldn't be too
10887 performance-intensive.
10888 - Disable sentinel-based debugging for buffer code: we squashed all
10889 the bugs that this was supposed to detect a long time ago, and
10890 now its only effect is to change our buffer sizes from nice
10891 powers of two (which platform mallocs tend to like) to values
10892 slightly over powers of two (which make some platform mallocs sad).
10893 - Log malloc statistics from mallinfo() on platforms where it
10897 Changes in version 0.2.0.3-alpha - 2007-07-29
10898 This third development snapshot introduces new experimental
10899 blocking-resistance features and a preliminary version of the v3
10900 directory voting design, and includes many other smaller features
10904 - The first pieces of our "bridge" design for blocking-resistance
10905 are implemented. People can run bridge directory authorities;
10906 people can run bridges; and people can configure their Tor clients
10907 with a set of bridges to use as the first hop into the Tor network.
10908 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
10910 - Create listener connections before we setuid to the configured
10911 User and Group. Now non-Windows users can choose port values
10912 under 1024, start Tor as root, and have Tor bind those ports
10913 before it changes to another UID. (Windows users could already
10915 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
10916 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
10917 on "vserver" accounts. (Patch from coderman.)
10918 - Be even more aggressive about separating local traffic from relayed
10919 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
10921 o Major features (experimental):
10922 - First cut of code for "v3 dir voting": directory authorities will
10923 vote on a common network status document rather than each publishing
10924 their own opinion. This code needs more testing and more corner-case
10925 handling before it's ready for use.
10928 - Directory authorities now call routers Fast if their bandwidth is
10929 at least 100KB/s, and consider their bandwidth adequate to be a
10930 Guard if it is at least 250KB/s, no matter the medians. This fix
10931 complements proposal 107. [Bugfix on 0.1.2.x]
10932 - Directory authorities now never mark more than 3 servers per IP as
10933 Valid and Running. (Implements proposal 109, by Kevin Bauer and
10935 - Minor change to organizationName and commonName generation
10936 procedures in TLS certificates during Tor handshakes, to invalidate
10937 some earlier censorware approaches. This is not a long-term
10938 solution, but applying it will give us a bit of time to look into
10939 the epidemiology of countermeasures as they spread.
10941 o Major bugfixes (directory):
10942 - Rewrite directory tokenization code to never run off the end of
10943 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
10945 o Minor features (controller):
10946 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
10947 match requests to applications. (Patch from Robert Hogan.)
10948 - Report address and port correctly on connections to DNSPort. (Patch
10949 from Robert Hogan.)
10950 - Add a RESOLVE command to launch hostname lookups. (Original patch
10951 from Robert Hogan.)
10952 - Add GETINFO status/enough-dir-info to let controllers tell whether
10953 Tor has downloaded sufficient directory information. (Patch
10955 - You can now use the ControlSocket option to tell Tor to listen for
10956 controller connections on Unix domain sockets on systems that
10957 support them. (Patch from Peter Palfrader.)
10958 - STREAM NEW events are generated for DNSPort requests and for
10959 tunneled directory connections. (Patch from Robert Hogan.)
10960 - New "GETINFO address-mappings/*" command to get address mappings
10961 with expiry information. "addr-mappings/*" is now deprecated.
10964 o Minor features (misc):
10965 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
10967 - The tor-gencert tool for v3 directory authorities now creates all
10968 files as readable to the file creator only, and write-protects
10969 the authority identity key.
10970 - When dumping memory usage, list bytes used in buffer memory
10972 - When running with dmalloc, dump more stats on hup and on exit.
10973 - Directory authorities now fail quickly and (relatively) harmlessly
10974 if they generate a network status document that is somehow
10977 o Traffic load balancing improvements:
10978 - If exit bandwidth ever exceeds one third of total bandwidth, then
10979 use the correct formula to weight exit nodes when choosing paths.
10980 (Based on patch from Mike Perry.)
10981 - Choose perfectly fairly among routers when choosing by bandwidth and
10982 weighting by fraction of bandwidth provided by exits. Previously, we
10983 would choose with only approximate fairness, and correct ourselves
10984 if we ran off the end of the list. [Bugfix on 0.1.2.x]
10986 o Performance improvements:
10987 - Be more aggressive with freeing buffer RAM or putting it on the
10989 - Use Critical Sections rather than Mutexes for synchronizing threads
10990 on win32; Mutexes are heavier-weight, and designed for synchronizing
10993 o Deprecated and removed features:
10994 - RedirectExits is now deprecated.
10995 - Stop allowing address masks that do not correspond to bit prefixes.
10996 We have warned about these for a really long time; now it's time
10997 to reject them. (Patch from croup.)
10999 o Minor bugfixes (directory):
11000 - Fix another crash bug related to extra-info caching. (Bug found by
11001 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
11002 - Directories no longer return a "304 not modified" when they don't
11003 have the networkstatus the client asked for. Also fix a memory
11004 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
11005 - We had accidentally labelled 0.1.2.x directory servers as not
11006 suitable for begin_dir requests, and had labelled no directory
11007 servers as suitable for uploading extra-info documents. [Bugfix
11010 o Minor bugfixes (dns):
11011 - Fix a crash when DNSPort is set more than once. (Patch from Robert
11012 Hogan.) [Bugfix on 0.2.0.2-alpha]
11013 - Add DNSPort connections to the global connection list, so that we
11014 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
11016 - Fix a dangling reference that could lead to a crash when DNSPort is
11017 changed or closed (Patch from Robert Hogan.) [Bugfix on
11020 o Minor bugfixes (controller):
11021 - Provide DNS expiry times in GMT, not in local time. For backward
11022 compatibility, ADDRMAP events only provide GMT expiry in an extended
11023 field. "GETINFO address-mappings" always does the right thing.
11024 - Use CRLF line endings properly in NS events.
11025 - Terminate multi-line control events properly. (Original patch
11026 from tup.) [Bugfix on 0.1.2.x-alpha]
11027 - Do not include spaces in SOURCE_ADDR fields in STREAM
11028 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
11031 Changes in version 0.1.2.15 - 2007-07-17
11032 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
11033 problems, fixes compilation on BSD, and fixes a variety of other
11034 bugs. Everybody should upgrade.
11036 o Major bugfixes (compilation):
11037 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
11039 o Major bugfixes (crashes):
11040 - Try even harder not to dereference the first character after
11041 an mmap(). Reported by lodger.
11042 - Fix a crash bug in directory authorities when we re-number the
11043 routerlist while inserting a new router.
11044 - When the cached-routers file is an even multiple of the page size,
11045 don't run off the end and crash. (Fixes bug 455; based on idea
11047 - Fix eventdns.c behavior on Solaris: It is critical to include
11048 orconfig.h _before_ sys/types.h, so that we can get the expected
11049 definition of _FILE_OFFSET_BITS.
11051 o Major bugfixes (security):
11052 - Fix a possible buffer overrun when using BSD natd support. Bug
11054 - When sending destroy cells from a circuit's origin, don't include
11055 the reason for tearing down the circuit. The spec says we didn't,
11056 and now we actually don't. Reported by lodger.
11057 - Keep streamids from different exits on a circuit separate. This
11058 bug may have allowed other routers on a given circuit to inject
11059 cells into streams. Reported by lodger; fixes bug 446.
11060 - If there's a never-before-connected-to guard node in our list,
11061 never choose any guards past it. This way we don't expand our
11062 guard list unless we need to.
11064 o Minor bugfixes (guard nodes):
11065 - Weight guard selection by bandwidth, so that low-bandwidth nodes
11066 don't get overused as guards.
11068 o Minor bugfixes (directory):
11069 - Correctly count the number of authorities that recommend each
11070 version. Previously, we were under-counting by 1.
11071 - Fix a potential crash bug when we load many server descriptors at
11072 once and some of them make others of them obsolete. Fixes bug 458.
11074 o Minor bugfixes (hidden services):
11075 - Stop tearing down the whole circuit when the user asks for a
11076 connection to a port that the hidden service didn't configure.
11079 o Minor bugfixes (misc):
11080 - On Windows, we were preventing other processes from reading
11081 cached-routers while Tor was running. Reported by janbar.
11082 - Fix a possible (but very unlikely) bug in picking routers by
11083 bandwidth. Add a log message to confirm that it is in fact
11084 unlikely. Patch from lodger.
11085 - Backport a couple of memory leak fixes.
11086 - Backport miscellaneous cosmetic bugfixes.
11089 Changes in version 0.2.0.2-alpha - 2007-06-02
11090 o Major bugfixes on 0.2.0.1-alpha:
11091 - Fix an assertion failure related to servers without extra-info digests.
11092 Resolves bugs 441 and 442.
11094 o Minor features (directory):
11095 - Support "If-Modified-Since" when answering HTTP requests for
11096 directories, running-routers documents, and network-status documents.
11097 (There's no need to support it for router descriptors, since those
11098 are downloaded by descriptor digest.)
11100 o Minor build issues:
11101 - Clear up some MIPSPro compiler warnings.
11102 - When building from a tarball on a machine that happens to have SVK
11103 installed, report the micro-revision as whatever version existed
11104 in the tarball, not as "x".
11107 Changes in version 0.2.0.1-alpha - 2007-06-01
11108 This early development snapshot provides new features for people running
11109 Tor as both a client and a server (check out the new RelayBandwidth
11110 config options); lets Tor run as a DNS proxy; and generally moves us
11111 forward on a lot of fronts.
11113 o Major features, server usability:
11114 - New config options RelayBandwidthRate and RelayBandwidthBurst:
11115 a separate set of token buckets for relayed traffic. Right now
11116 relayed traffic is defined as answers to directory requests, and
11117 OR connections that don't have any local circuits on them.
11119 o Major features, client usability:
11120 - A client-side DNS proxy feature to replace the need for
11121 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
11122 for DNS requests on port 9999, use the Tor network to resolve them
11123 anonymously, and send the reply back like a regular DNS server.
11124 The code still only implements a subset of DNS.
11125 - Make PreferTunneledDirConns and TunnelDirConns work even when
11126 we have no cached directory info. This means Tor clients can now
11127 do all of their connections protected by TLS.
11129 o Major features, performance and efficiency:
11130 - Directory authorities accept and serve "extra info" documents for
11131 routers. These documents contain fields from router descriptors
11132 that aren't usually needed, and that use a lot of excess
11133 bandwidth. Once these fields are removed from router descriptors,
11134 the bandwidth savings should be about 60%. [Partially implements
11136 - Servers upload extra-info documents to any authority that accepts
11137 them. Authorities (and caches that have been configured to download
11138 extra-info documents) download them as needed. [Partially implements
11140 - Change the way that Tor buffers data that it is waiting to write.
11141 Instead of queueing data cells in an enormous ring buffer for each
11142 client->OR or OR->OR connection, we now queue cells on a separate
11143 queue for each circuit. This lets us use less slack memory, and
11144 will eventually let us be smarter about prioritizing different kinds
11146 - Use memory pools to allocate cells with better speed and memory
11147 efficiency, especially on platforms where malloc() is inefficient.
11148 - Stop reading on edge connections when their corresponding circuit
11149 buffers are full; start again as the circuits empty out.
11151 o Major features, other:
11152 - Add an HSAuthorityRecordStats option that hidden service authorities
11153 can use to track statistics of overall hidden service usage without
11154 logging information that would be very useful to an attacker.
11155 - Start work implementing multi-level keys for directory authorities:
11156 Add a standalone tool to generate key certificates. (Proposal 103.)
11159 - Directory authorities now call routers Stable if they have an
11160 uptime of at least 30 days, even if that's not the median uptime
11161 in the network. Implements proposal 107, suggested by Kevin Bauer
11164 o Minor fixes (resource management):
11165 - Count the number of open sockets separately from the number
11166 of active connection_t objects. This will let us avoid underusing
11167 our allocated connection limit.
11168 - We no longer use socket pairs to link an edge connection to an
11169 anonymous directory connection or a DirPort test connection.
11170 Instead, we track the link internally and transfer the data
11171 in-process. This saves two sockets per "linked" connection (at the
11172 client and at the server), and avoids the nasty Windows socketpair()
11174 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
11175 for every single inactive connection_t. Free items from the
11176 4k/16k-buffer free lists when they haven't been used for a while.
11178 o Minor features (build):
11179 - Make autoconf search for libevent, openssl, and zlib consistently.
11180 - Update deprecated macros in configure.in.
11181 - When warning about missing headers, tell the user to let us
11182 know if the compile succeeds anyway, so we can downgrade the
11184 - Include the current subversion revision as part of the version
11185 string: either fetch it directly if we're in an SVN checkout, do
11186 some magic to guess it if we're in an SVK checkout, or use
11187 the last-detected version if we're building from a .tar.gz.
11188 Use this version consistently in log messages.
11190 o Minor features (logging):
11191 - Always prepend "Bug: " to any log message about a bug.
11192 - Put a platform string (e.g. "Linux i686") in the startup log
11193 message, so when people paste just their logs, we know if it's
11194 OpenBSD or Windows or what.
11195 - When logging memory usage, break down memory used in buffers by
11198 o Minor features (directory system):
11199 - New config option V2AuthoritativeDirectory that all directory
11200 authorities should set. This will let future authorities choose
11201 not to serve V2 directory information.
11202 - Directory authorities allow multiple router descriptors and/or extra
11203 info documents to be uploaded in a single go. This will make
11204 implementing proposal 104 simpler.
11206 o Minor features (controller):
11207 - Add a new config option __DisablePredictedCircuits designed for
11208 use by the controller, when we don't want Tor to build any circuits
11210 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
11211 so we can exit from the middle of the circuit.
11212 - Implement "getinfo status/circuit-established".
11213 - Implement "getinfo status/version/..." so a controller can tell
11214 whether the current version is recommended, and whether any versions
11215 are good, and how many authorities agree. (Patch from shibz.)
11217 o Minor features (hidden services):
11218 - Allow multiple HiddenServicePort directives with the same virtual
11219 port; when they occur, the user is sent round-robin to one
11220 of the target ports chosen at random. Partially fixes bug 393 by
11221 adding limited ad-hoc round-robining.
11223 o Minor features (other):
11225 - Add a new AutomapHostsOnResolve option: when it is enabled, any
11226 resolve request for hosts matching a given pattern causes Tor to
11227 generate an internal virtual address mapping for that host. This
11228 allows DNSPort to work sensibly with hidden service users. By
11229 default, .exit and .onion addresses are remapped; the list of
11230 patterns can be reconfigured with AutomapHostsSuffixes.
11231 - Add an "-F" option to tor-resolve to force a resolve for a .onion
11232 address. Thanks to the AutomapHostsOnResolve option, this is no
11233 longer a completely silly thing to do.
11234 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
11235 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
11236 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
11237 minus 1 byte: the actual maximum declared bandwidth.
11239 o Removed features:
11240 - Removed support for the old binary "version 0" controller protocol.
11241 This has been deprecated since 0.1.1, and warnings have been issued
11242 since 0.1.2. When we encounter a v0 control message, we now send
11243 back an error and close the connection.
11244 - Remove the old "dns worker" server DNS code: it hasn't been default
11245 since 0.1.2.2-alpha, and all the servers seem to be using the new
11248 o Minor bugfixes (portability):
11249 - Even though Windows is equally happy with / and \ as path separators,
11250 try to use \ consistently on Windows and / consistently on Unix: it
11251 makes the log messages nicer.
11252 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
11253 - Read resolv.conf files correctly on platforms where read() returns
11254 partial results on small file reads.
11256 o Minor bugfixes (directory):
11257 - Correctly enforce that elements of directory objects do not appear
11258 more often than they are allowed to appear.
11259 - When we are reporting the DirServer line we just parsed, we were
11260 logging the second stanza of the key fingerprint, not the first.
11262 o Minor bugfixes (logging):
11263 - When we hit an EOF on a log (probably because we're shutting down),
11264 don't try to remove the log from the list: just mark it as
11265 unusable. (Bulletproofs against bug 222.)
11267 o Minor bugfixes (other):
11268 - In the exitlist script, only consider the most recently published
11269 server descriptor for each server. Also, when the user requests
11270 a list of servers that _reject_ connections to a given address,
11271 explicitly exclude the IPs that also have servers that accept
11272 connections to that address. (Resolves bug 405.)
11273 - Stop allowing hibernating servers to be "stable" or "fast".
11274 - On Windows, we were preventing other processes from reading
11275 cached-routers while Tor was running. (Reported by janbar)
11276 - Make the NodeFamilies config option work. (Reported by
11277 lodger -- it has never actually worked, even though we added it
11279 - Check return values from pthread_mutex functions.
11280 - Don't save non-general-purpose router descriptors to the disk cache,
11281 because we have no way of remembering what their purpose was when
11283 - Add even more asserts to hunt down bug 417.
11284 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
11285 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
11286 Add a log message to confirm that it is in fact unlikely.
11288 o Minor bugfixes (controller):
11289 - Make 'getinfo fingerprint' return a 551 error if we're not a
11290 server, so we match what the control spec claims we do. Reported
11292 - Fix a typo in an error message when extendcircuit fails that
11293 caused us to not follow the \r\n-based delimiter protocol. Reported
11296 o Code simplifications and refactoring:
11297 - Stop passing around circuit_t and crypt_path_t pointers that are
11298 implicit in other procedure arguments.
11299 - Drop the old code to choke directory connections when the
11300 corresponding OR connections got full: thanks to the cell queue
11301 feature, OR conns don't get full any more.
11302 - Make dns_resolve() handle attaching connections to circuits
11303 properly, so the caller doesn't have to.
11304 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
11305 - Keep the connection array as a dynamic smartlist_t, rather than as
11306 a fixed-sized array. This is important, as the number of connections
11307 is becoming increasingly decoupled from the number of sockets.
11310 Changes in version 0.1.2.14 - 2007-05-25
11311 Tor 0.1.2.14 changes the addresses of two directory authorities (this
11312 change especially affects those who serve or use hidden services),
11313 and fixes several other crash- and security-related bugs.
11315 o Directory authority changes:
11316 - Two directory authorities (moria1 and moria2) just moved to new
11317 IP addresses. This change will particularly affect those who serve
11318 or use hidden services.
11320 o Major bugfixes (crashes):
11321 - If a directory server runs out of space in the connection table
11322 as it's processing a begin_dir request, it will free the exit stream
11323 but leave it attached to the circuit, leading to unpredictable
11324 behavior. (Reported by seeess, fixes bug 425.)
11325 - Fix a bug in dirserv_remove_invalid() that would cause authorities
11326 to corrupt memory under some really unlikely scenarios.
11327 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
11328 - Avoid segfaults when reading from mmaped descriptor file. (Reported
11331 o Major bugfixes (security):
11332 - When choosing an entry guard for a circuit, avoid using guards
11333 that are in the same family as the chosen exit -- not just guards
11334 that are exactly the chosen exit. (Reported by lodger.)
11336 o Major bugfixes (resource management):
11337 - If a directory authority is down, skip it when deciding where to get
11338 networkstatus objects or descriptors. Otherwise we keep asking
11339 every 10 seconds forever. Fixes bug 384.
11340 - Count it as a failure if we fetch a valid network-status but we
11341 don't want to keep it. Otherwise we'll keep fetching it and keep
11342 not wanting to keep it. Fixes part of bug 422.
11343 - If all of our dirservers have given us bad or no networkstatuses
11344 lately, then stop hammering them once per minute even when we
11345 think they're failed. Fixes another part of bug 422.
11348 - Actually set the purpose correctly for descriptors inserted with
11349 purpose=controller.
11350 - When we have k non-v2 authorities in our DirServer config,
11351 we ignored the last k authorities in the list when updating our
11353 - Correctly back-off from requesting router descriptors that we are
11354 having a hard time downloading.
11355 - Read resolv.conf files correctly on platforms where read() returns
11356 partial results on small file reads.
11357 - Don't rebuild the entire router store every time we get 32K of
11358 routers: rebuild it when the journal gets very large, or when
11359 the gaps in the store get very large.
11362 - When routers publish SVN revisions in their router descriptors,
11363 authorities now include those versions correctly in networkstatus
11365 - Warn when using a version of libevent before 1.3b to run a server on
11366 OSX or BSD: these versions interact badly with userspace threads.
11369 Changes in version 0.1.2.13 - 2007-04-24
11370 This release features some major anonymity fixes, such as safer path
11371 selection; better client performance; faster bootstrapping, better
11372 address detection, and better DNS support for servers; write limiting as
11373 well as read limiting to make servers easier to run; and a huge pile of
11374 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
11376 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
11377 of the Freenode IRC network, remembering his patience and vision for
11378 free speech on the Internet.
11381 - Fix a memory leak when we ask for "all" networkstatuses and we
11382 get one we don't recognize.
11383 - Add more asserts to hunt down bug 417.
11384 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
11387 Changes in version 0.1.2.12-rc - 2007-03-16
11389 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
11390 directory information requested inside Tor connections (i.e. via
11391 begin_dir cells). It only triggered when the same connection was
11392 serving other data at the same time. Reported by seeess.
11395 - When creating a circuit via the controller, send a 'launched'
11396 event when we're done, so we follow the spec better.
11399 Changes in version 0.1.2.11-rc - 2007-03-15
11400 o Minor bugfixes (controller), reported by daejees:
11401 - Correct the control spec to match how the code actually responds
11402 to 'getinfo addr-mappings/*'.
11403 - The control spec described a GUARDS event, but the code
11404 implemented a GUARD event. Standardize on GUARD, but let people
11405 ask for GUARDS too.
11408 Changes in version 0.1.2.10-rc - 2007-03-07
11409 o Major bugfixes (Windows):
11410 - Do not load the NT services library functions (which may not exist)
11411 just to detect if we're a service trying to shut down. Now we run
11412 on Win98 and friends again.
11414 o Minor bugfixes (other):
11415 - Clarify a couple of log messages.
11416 - Fix a misleading socks5 error number.
11419 Changes in version 0.1.2.9-rc - 2007-03-02
11420 o Major bugfixes (Windows):
11421 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
11422 of the usual GCC "%llu". This prevents a bug when saving 64-bit
11423 int configuration values: the high-order 32 bits would get
11424 truncated. In particular, we were being bitten by the default
11425 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
11426 and maybe also bug 397.)
11428 o Minor bugfixes (performance):
11429 - Use OpenSSL's AES implementation on platforms where it's faster.
11430 This could save us as much as 10% CPU usage.
11432 o Minor bugfixes (server):
11433 - Do not rotate onion key immediately after setting it for the first
11436 o Minor bugfixes (directory authorities):
11437 - Stop calling servers that have been hibernating for a long time
11438 "stable". Also, stop letting hibernating or obsolete servers affect
11439 uptime and bandwidth cutoffs.
11440 - Stop listing hibernating servers in the v1 directory.
11442 o Minor bugfixes (hidden services):
11443 - Upload hidden service descriptors slightly less often, to reduce
11444 load on authorities.
11446 o Minor bugfixes (other):
11447 - Fix an assert that could trigger if a controller quickly set then
11448 cleared EntryNodes. Bug found by Udo van den Heuvel.
11449 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
11451 - Fix a potential race condition in the rpm installer. Found by
11453 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
11454 of 2 as indicating that the server is completely bad; it sometimes
11455 means that the server is just bad for the request in question. (may fix
11456 the last of bug 326.)
11457 - Disable encrypted directory connections when we don't have a server
11458 descriptor for the destination. We'll get this working again in
11462 Changes in version 0.1.2.8-beta - 2007-02-26
11463 o Major bugfixes (crashes):
11464 - Stop crashing when the controller asks us to resetconf more than
11465 one config option at once. (Vidalia 0.0.11 does this.)
11466 - Fix a crash that happened on Win98 when we're given command-line
11467 arguments: don't try to load NT service functions from advapi32.dll
11468 except when we need them. (Bug introduced in 0.1.2.7-alpha;
11470 - Fix a longstanding obscure crash bug that could occur when
11471 we run out of DNS worker processes. (Resolves bug 390.)
11473 o Major bugfixes (hidden services):
11474 - Correctly detect whether hidden service descriptor downloads are
11475 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
11477 o Major bugfixes (accounting):
11478 - When we start during an accounting interval before it's time to wake
11479 up, remember to wake up at the correct time. (May fix bug 342.)
11481 o Minor bugfixes (controller):
11482 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
11483 clear the corresponding on_circuit variable, and remember later
11484 that we don't need to send a redundant CLOSED event. Resolves part
11486 - Report events where a resolve succeeded or where we got a socks
11487 protocol error correctly, rather than calling both of them
11489 - Change reported stream target addresses to IP consistently when
11490 we finally get the IP from an exit node.
11491 - Send log messages to the controller even if they happen to be very
11494 o Minor bugfixes (other):
11495 - Display correct results when reporting which versions are
11496 recommended, and how recommended they are. (Resolves bug 383.)
11497 - Improve our estimates for directory bandwidth to be less random:
11498 guess that an unrecognized directory will have the average bandwidth
11499 from all known directories, not that it will have the average
11500 bandwidth from those directories earlier than it on the list.
11501 - If we start a server with ClientOnly 1, then set ClientOnly to 0
11502 and hup, stop triggering an assert based on an empty onion_key.
11503 - On platforms with no working mmap() equivalent, don't warn the
11504 user when cached-routers doesn't exist.
11505 - Warn the user when mmap() [or its equivalent] fails for some reason
11506 other than file-not-found.
11507 - Don't warn the user when cached-routers.new doesn't exist: that's
11508 perfectly fine when starting up for the first time.
11509 - When EntryNodes are configured, rebuild the guard list to contain,
11510 in order: the EntryNodes that were guards before; the rest of the
11511 EntryNodes; the nodes that were guards before.
11512 - Mask out all signals in sub-threads; only the libevent signal
11513 handler should be processing them. This should prevent some crashes
11514 on some machines using pthreads. (Patch from coderman.)
11515 - Fix switched arguments on memset in the implementation of
11516 tor_munmap() for systems with no mmap() call.
11517 - When Tor receives a router descriptor that it asked for, but
11518 no longer wants (because it has received fresh networkstatuses
11519 in the meantime), do not warn the user. Cache the descriptor if
11520 we're a cache; drop it if we aren't.
11521 - Make earlier entry guards _really_ get retried when the network
11523 - On a malformed DNS reply, always give an error to the corresponding
11525 - Build with recent libevents on platforms that do not define the
11526 nonstandard types "u_int8_t" and friends.
11528 o Minor features (controller):
11529 - Warn the user when an application uses the obsolete binary v0
11530 control protocol. We're planning to remove support for it during
11531 the next development series, so it's good to give people some
11533 - Add STREAM_BW events to report per-entry-stream bandwidth
11534 use. (Patch from Robert Hogan.)
11535 - Rate-limit SIGNEWNYM signals in response to controllers that
11536 impolitely generate them for every single stream. (Patch from
11537 mwenge; closes bug 394.)
11538 - Make REMAP stream events have a SOURCE (cache or exit), and
11539 make them generated in every case where we get a successful
11540 connected or resolved cell.
11542 o Minor bugfixes (performance):
11543 - Call router_have_min_dir_info half as often. (This is showing up in
11544 some profiles, but not others.)
11545 - When using GCC, make log_debug never get called at all, and its
11546 arguments never get evaluated, when no debug logs are configured.
11547 (This is showing up in some profiles, but not others.)
11550 - Remove some never-implemented options. Mark PathlenCoinWeight as
11552 - Implement proposal 106: Stop requiring clients to have well-formed
11553 certificates; stop checking nicknames in certificates. (Clients
11554 have certificates so that they can look like Tor servers, but in
11555 the future we might want to allow them to look like regular TLS
11556 clients instead. Nicknames in certificates serve no purpose other
11557 than making our protocol easier to recognize on the wire.)
11558 - Revise messages on handshake failure again to be even more clear about
11559 which are incoming connections and which are outgoing.
11560 - Discard any v1 directory info that's over 1 month old (for
11561 directories) or over 1 week old (for running-routers lists).
11562 - Do not warn when individual nodes in the configuration's EntryNodes,
11563 ExitNodes, etc are down: warn only when all possible nodes
11564 are down. (Fixes bug 348.)
11565 - Always remove expired routers and networkstatus docs before checking
11566 whether we have enough information to build circuits. (Fixes
11568 - Put a lower-bound on MaxAdvertisedBandwidth.
11571 Changes in version 0.1.2.7-alpha - 2007-02-06
11572 o Major bugfixes (rate limiting):
11573 - Servers decline directory requests much more aggressively when
11574 they're low on bandwidth. Otherwise they end up queueing more and
11575 more directory responses, which can't be good for latency.
11576 - But never refuse directory requests from local addresses.
11577 - Fix a memory leak when sending a 503 response for a networkstatus
11579 - Be willing to read or write on local connections (e.g. controller
11580 connections) even when the global rate limiting buckets are empty.
11581 - If our system clock jumps back in time, don't publish a negative
11582 uptime in the descriptor. Also, don't let the global rate limiting
11583 buckets go absurdly negative.
11584 - Flush local controller connection buffers periodically as we're
11585 writing to them, so we avoid queueing 4+ megabytes of data before
11588 o Major bugfixes (NT services):
11589 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
11590 command-line flag so that admins can override the default by saying
11591 "tor --service install --user "SomeUser"". This will not affect
11592 existing installed services. Also, warn the user that the service
11593 will look for its configuration file in the service user's
11594 %appdata% directory. (We can't do the 'hardwire the user's appdata
11595 directory' trick any more, since we may not have read access to that
11598 o Major bugfixes (other):
11599 - Previously, we would cache up to 16 old networkstatus documents
11600 indefinitely, if they came from nontrusted authorities. Now we
11601 discard them if they are more than 10 days old.
11602 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
11604 - Detect and reject malformed DNS responses containing circular
11606 - If exits are rare enough that we're not marking exits as guards,
11607 ignore exit bandwidth when we're deciding the required bandwidth
11609 - When we're handling a directory connection tunneled over Tor,
11610 don't fill up internal memory buffers with all the data we want
11611 to tunnel; instead, only add it if the OR connection that will
11612 eventually receive it has some room for it. (This can lead to
11613 slowdowns in tunneled dir connections; a better solution will have
11614 to wait for 0.2.0.)
11616 o Minor bugfixes (dns):
11617 - Add some defensive programming to eventdns.c in an attempt to catch
11618 possible memory-stomping bugs.
11619 - Detect and reject DNS replies containing IPv4 or IPv6 records with
11620 an incorrect number of bytes. (Previously, we would ignore the
11622 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
11623 in the correct order, and doesn't crash.
11624 - Free memory held in recently-completed DNS lookup attempts on exit.
11625 This was not a memory leak, but may have been hiding memory leaks.
11626 - Handle TTL values correctly on reverse DNS lookups.
11627 - Treat failure to parse resolv.conf as an error.
11629 o Minor bugfixes (other):
11630 - Fix crash with "tor --list-fingerprint" (reported by seeess).
11631 - When computing clock skew from directory HTTP headers, consider what
11632 time it was when we finished asking for the directory, not what
11634 - Expire socks connections if they spend too long waiting for the
11635 handshake to finish. Previously we would let them sit around for
11636 days, if the connecting application didn't close them either.
11637 - And if the socks handshake hasn't started, don't send a
11638 "DNS resolve socks failed" handshake reply; just close it.
11639 - Stop using C functions that OpenBSD's linker doesn't like.
11640 - Don't launch requests for descriptors unless we have networkstatuses
11641 from at least half of the authorities. This delays the first
11642 download slightly under pathological circumstances, but can prevent
11643 us from downloading a bunch of descriptors we don't need.
11644 - Do not log IPs with TLS failures for incoming TLS
11645 connections. (Fixes bug 382.)
11646 - If the user asks to use invalid exit nodes, be willing to use
11648 - Stop using the reserved ac_cv namespace in our configure script.
11649 - Call stat() slightly less often; use fstat() when possible.
11650 - Refactor the way we handle pending circuits when an OR connection
11651 completes or fails, in an attempt to fix a rare crash bug.
11652 - Only rewrite a conn's address based on X-Forwarded-For: headers
11653 if it's a parseable public IP address; and stop adding extra quotes
11654 to the resulting address.
11657 - Weight directory requests by advertised bandwidth. Now we can
11658 let servers enable write limiting but still allow most clients to
11659 succeed at their directory requests. (We still ignore weights when
11660 choosing a directory authority; I hope this is a feature.)
11663 - Create a new file ReleaseNotes which was the old ChangeLog. The
11664 new ChangeLog file now includes the summaries for all development
11666 - Check for addresses with invalid characters at the exit as well
11667 as at the client, and warn less verbosely when they fail. You can
11668 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
11669 - Adapt a patch from goodell to let the contrib/exitlist script
11670 take arguments rather than require direct editing.
11671 - Inform the server operator when we decide not to advertise a
11672 DirPort due to AccountingMax enabled or a low BandwidthRate. It
11673 was confusing Zax, so now we're hopefully more helpful.
11674 - Bring us one step closer to being able to establish an encrypted
11675 directory tunnel without knowing a descriptor first. Still not
11676 ready yet. As part of the change, now assume we can use a
11677 create_fast cell if we don't know anything about a router.
11678 - Allow exit nodes to use nameservers running on ports other than 53.
11679 - Servers now cache reverse DNS replies.
11680 - Add an --ignore-missing-torrc command-line option so that we can
11681 get the "use sensible defaults if the configuration file doesn't
11682 exist" behavior even when specifying a torrc location on the command
11685 o Minor features (controller):
11686 - Track reasons for OR connection failure; make these reasons
11687 available via the controller interface. (Patch from Mike Perry.)
11688 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
11689 can learn when clients are sending malformed hostnames to Tor.
11690 - Clean up documentation for controller status events.
11691 - Add a REMAP status to stream events to note that a stream's
11692 address has changed because of a cached address or a MapAddress
11696 Changes in version 0.1.2.6-alpha - 2007-01-09
11698 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
11699 connection handles more than 4 gigs in either direction, we crash.
11700 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
11701 advertised exit node, somebody might try to exit from us when
11702 we're bootstrapping and before we've built our descriptor yet.
11703 Refuse the connection rather than crashing.
11706 - Warn if we (as a server) find that we've resolved an address that we
11707 weren't planning to resolve.
11708 - Warn that using select() on any libevent version before 1.1 will be
11709 unnecessarily slow (even for select()).
11710 - Flush ERR-level controller status events just like we currently
11711 flush ERR-level log events, so that a Tor shutdown doesn't prevent
11712 the controller from learning about current events.
11714 o Minor features (more controller status events):
11715 - Implement EXTERNAL_ADDRESS server status event so controllers can
11716 learn when our address changes.
11717 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
11718 can learn when directories reject our descriptor.
11719 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
11720 can learn when a client application is speaking a non-socks protocol
11722 - Implement DANGEROUS_SOCKS client status event so controllers
11723 can learn when a client application is leaking DNS addresses.
11724 - Implement BUG general status event so controllers can learn when
11725 Tor is unhappy about its internal invariants.
11726 - Implement CLOCK_SKEW general status event so controllers can learn
11727 when Tor thinks the system clock is set incorrectly.
11728 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
11729 server status events so controllers can learn when their descriptors
11730 are accepted by a directory.
11731 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
11732 server status events so controllers can learn about Tor's progress in
11733 deciding whether it's reachable from the outside.
11734 - Implement BAD_LIBEVENT general status event so controllers can learn
11735 when we have a version/method combination in libevent that needs to
11737 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
11738 and DNS_USELESS server status events so controllers can learn
11739 about changes to DNS server status.
11741 o Minor features (directory):
11742 - Authorities no longer recommend exits as guards if this would shift
11743 too much load to the exit nodes.
11746 Changes in version 0.1.2.5-alpha - 2007-01-06
11748 - Enable write limiting as well as read limiting. Now we sacrifice
11749 capacity if we're pushing out lots of directory traffic, rather
11750 than overrunning the user's intended bandwidth limits.
11751 - Include TLS overhead when counting bandwidth usage; previously, we
11752 would count only the bytes sent over TLS, but not the bytes used
11754 - Support running the Tor service with a torrc not in the same
11755 directory as tor.exe and default to using the torrc located in
11756 the %appdata%\Tor\ of the user who installed the service. Patch
11758 - Servers now check for the case when common DNS requests are going to
11759 wildcarded addresses (i.e. all getting the same answer), and change
11760 their exit policy to reject *:* if it's happening.
11761 - Implement BEGIN_DIR cells, so we can connect to the directory
11762 server via TLS to do encrypted directory requests rather than
11763 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
11764 config options if you like.
11766 o Minor features (config and docs):
11767 - Start using the state file to store bandwidth accounting data:
11768 the bw_accounting file is now obsolete. We'll keep generating it
11769 for a while for people who are still using 0.1.2.4-alpha.
11770 - Try to batch changes to the state file so that we do as few
11771 disk writes as possible while still storing important things in
11773 - The state file and the bw_accounting file get saved less often when
11774 the AvoidDiskWrites config option is set.
11775 - Make PIDFile work on Windows (untested).
11776 - Add internal descriptions for a bunch of configuration options:
11777 accessible via controller interface and in comments in saved
11779 - Reject *:563 (NNTPS) in the default exit policy. We already reject
11780 NNTP by default, so this seems like a sensible addition.
11781 - Clients now reject hostnames with invalid characters. This should
11782 avoid some inadvertent info leaks. Add an option
11783 AllowNonRFC953Hostnames to disable this behavior, in case somebody
11784 is running a private network with hosts called @, !, and #.
11785 - Add a maintainer script to tell us which options are missing
11786 documentation: "make check-docs".
11787 - Add a new address-spec.txt document to describe our special-case
11788 addresses: .exit, .onion, and .noconnnect.
11790 o Minor features (DNS):
11791 - Ongoing work on eventdns infrastructure: now it has dns server
11792 and ipv6 support. One day Tor will make use of it.
11793 - Add client-side caching for reverse DNS lookups.
11794 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
11795 - When we change nameservers or IP addresses, reset and re-launch
11796 our tests for DNS hijacking.
11798 o Minor features (directory):
11799 - Authorities now specify server versions in networkstatus. This adds
11800 about 2% to the size of compressed networkstatus docs, and allows
11801 clients to tell which servers support BEGIN_DIR and which don't.
11802 The implementation is forward-compatible with a proposed future
11803 protocol version scheme not tied to Tor versions.
11804 - DirServer configuration lines now have an orport= option so
11805 clients can open encrypted tunnels to the authorities without
11806 having downloaded their descriptors yet. Enabled for moria1,
11807 moria2, tor26, and lefkada now in the default configuration.
11808 - Directory servers are more willing to send a 503 "busy" if they
11809 are near their write limit, especially for v1 directory requests.
11810 Now they can use their limited bandwidth for actual Tor traffic.
11811 - Clients track responses with status 503 from dirservers. After a
11812 dirserver has given us a 503, we try not to use it until an hour has
11813 gone by, or until we have no dirservers that haven't given us a 503.
11814 - When we get a 503 from a directory, and we're not a server, we don't
11815 count the failure against the total number of failures allowed
11816 for the thing we're trying to download.
11817 - Report X-Your-Address-Is correctly from tunneled directory
11818 connections; don't report X-Your-Address-Is when it's an internal
11819 address; and never believe reported remote addresses when they're
11821 - Protect against an unlikely DoS attack on directory servers.
11822 - Add a BadDirectory flag to network status docs so that authorities
11823 can (eventually) tell clients about caches they believe to be
11826 o Minor features (controller):
11827 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
11828 - Reimplement GETINFO so that info/names stays in sync with the
11830 - Implement "GETINFO fingerprint".
11831 - Implement "SETEVENTS GUARD" so controllers can get updates on
11832 entry guard status as it changes.
11834 o Minor features (clean up obsolete pieces):
11835 - Remove some options that have been deprecated since at least
11836 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
11837 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
11838 to set log options.
11839 - We no longer look for identity and onion keys in "identity.key" and
11840 "onion.key" -- these were replaced by secret_id_key and
11841 secret_onion_key in 0.0.8pre1.
11842 - We no longer require unrecognized directory entries to be
11845 o Major bugfixes (security):
11846 - Stop sending the HttpProxyAuthenticator string to directory
11847 servers when directory connections are tunnelled through Tor.
11848 - Clients no longer store bandwidth history in the state file.
11849 - Do not log introduction points for hidden services if SafeLogging
11851 - When generating bandwidth history, round down to the nearest
11852 1k. When storing accounting data, round up to the nearest 1k.
11853 - When we're running as a server, remember when we last rotated onion
11854 keys, so that we will rotate keys once they're a week old even if
11855 we never stay up for a week ourselves.
11857 o Major bugfixes (other):
11858 - Fix a longstanding bug in eventdns that prevented the count of
11859 timed-out resolves from ever being reset. This bug caused us to
11860 give up on a nameserver the third time it timed out, and try it
11861 10 seconds later... and to give up on it every time it timed out
11863 - Take out the '5 second' timeout from the connection retry
11864 schedule. Now the first connect attempt will wait a full 10
11865 seconds before switching to a new circuit. Perhaps this will help
11866 a lot. Based on observations from Mike Perry.
11867 - Fix a bug on the Windows implementation of tor_mmap_file() that
11868 would prevent the cached-routers file from ever loading. Reported
11872 - Fix an assert failure when a directory authority sets
11873 AuthDirRejectUnlisted and then receives a descriptor from an
11874 unlisted router. Reported by seeess.
11875 - Avoid a double-free when parsing malformed DirServer lines.
11876 - Fix a bug when a BSD-style PF socket is first used. Patch from
11878 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
11879 to resolve an address at a given exit node even when they ask for
11881 - Servers no longer ever list themselves in their "family" line,
11882 even if configured to do so. This makes it easier to configure
11883 family lists conveniently.
11884 - When running as a server, don't fall back to 127.0.0.1 when no
11885 nameservers are configured in /etc/resolv.conf; instead, make the
11886 user fix resolv.conf or specify nameservers explicitly. (Resolves
11888 - Stop accepting certain malformed ports in configured exit policies.
11889 - Don't re-write the fingerprint file every restart, unless it has
11891 - Stop warning when a single nameserver fails: only warn when _all_ of
11892 our nameservers have failed. Also, when we only have one nameserver,
11893 raise the threshold for deciding that the nameserver is dead.
11894 - Directory authorities now only decide that routers are reachable
11895 if their identity keys are as expected.
11896 - When the user uses bad syntax in the Log config line, stop
11897 suggesting other bad syntax as a replacement.
11898 - Correctly detect ipv6 DNS capability on OpenBSD.
11900 o Minor bugfixes (controller):
11901 - Report the circuit number correctly in STREAM CLOSED events. Bug
11902 reported by Mike Perry.
11903 - Do not report bizarre values for results of accounting GETINFOs
11904 when the last second's write or read exceeds the allotted bandwidth.
11905 - Report "unrecognized key" rather than an empty string when the
11906 controller tries to fetch a networkstatus that doesn't exist.
11909 Changes in version 0.1.1.26 - 2006-12-14
11910 o Security bugfixes:
11911 - Stop sending the HttpProxyAuthenticator string to directory
11912 servers when directory connections are tunnelled through Tor.
11913 - Clients no longer store bandwidth history in the state file.
11914 - Do not log introduction points for hidden services if SafeLogging
11918 - Fix an assert failure when a directory authority sets
11919 AuthDirRejectUnlisted and then receives a descriptor from an
11920 unlisted router (reported by seeess).
11923 Changes in version 0.1.2.4-alpha - 2006-12-03
11925 - Add support for using natd; this allows FreeBSDs earlier than
11926 5.1.2 to have ipfw send connections through Tor without using
11927 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
11930 - Make all connections to addresses of the form ".noconnect"
11931 immediately get closed. This lets application/controller combos
11932 successfully test whether they're talking to the same Tor by
11933 watching for STREAM events.
11934 - Make cross.sh cross-compilation script work even when autogen.sh
11935 hasn't been run. (Patch from Michael Mohr.)
11936 - Statistics dumped by -USR2 now include a breakdown of public key
11937 operations, for profiling.
11940 - Fix a major leak when directory authorities parse their
11941 approved-routers list, a minor memory leak when we fail to pick
11942 an exit node, and a few rare leaks on errors.
11943 - Handle TransPort connections even when the server sends data before
11944 the client sends data. Previously, the connection would just hang
11945 until the client sent data. (Patch from tup based on patch from
11947 - Avoid assert failure when our cached-routers file is empty on
11951 - Don't log spurious warnings when we see a circuit close reason we
11952 don't recognize; it's probably just from a newer version of Tor.
11953 - Have directory authorities allow larger amounts of drift in uptime
11954 without replacing the server descriptor: previously, a server that
11955 restarted every 30 minutes could have 48 "interesting" descriptors
11957 - Start linking to the Tor specification and Tor reference manual
11958 correctly in the Windows installer.
11959 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11960 Tor/Privoxy we also uninstall Vidalia.
11961 - Resume building on Irix64, and fix a lot of warnings from its
11962 MIPSpro C compiler.
11963 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
11964 when we're running as a client.
11967 Changes in version 0.1.1.25 - 2006-11-04
11969 - When a client asks us to resolve (rather than connect to)
11970 an address, and we have a cached answer, give them the cached
11971 answer. Previously, we would give them no answer at all.
11972 - We were building exactly the wrong circuits when we predict
11973 hidden service requirements, meaning Tor would have to build all
11974 its circuits on demand.
11975 - If none of our live entry guards have a high uptime, but we
11976 require a guard with a high uptime, try adding a new guard before
11977 we give up on the requirement. This patch should make long-lived
11978 connections more stable on average.
11979 - When testing reachability of our DirPort, don't launch new
11980 tests when there's already one in progress -- unreachable
11981 servers were stacking up dozens of testing streams.
11983 o Security bugfixes:
11984 - When the user sends a NEWNYM signal, clear the client-side DNS
11985 cache too. Otherwise we continue to act on previous information.
11988 - Avoid a memory corruption bug when creating a hash table for
11990 - Avoid possibility of controller-triggered crash when misusing
11991 certain commands from a v0 controller on platforms that do not
11992 handle printf("%s",NULL) gracefully.
11993 - Avoid infinite loop on unexpected controller input.
11994 - Don't log spurious warnings when we see a circuit close reason we
11995 don't recognize; it's probably just from a newer version of Tor.
11996 - Add Vidalia to the OS X uninstaller script, so when we uninstall
11997 Tor/Privoxy we also uninstall Vidalia.
12000 Changes in version 0.1.2.3-alpha - 2006-10-29
12002 - Prepare for servers to publish descriptors less often: never
12003 discard a descriptor simply for being too old until either it is
12004 recommended by no authorities, or until we get a better one for
12005 the same router. Make caches consider retaining old recommended
12006 routers for even longer.
12007 - If most authorities set a BadExit flag for a server, clients
12008 don't think of it as a general-purpose exit. Clients only consider
12009 authorities that advertise themselves as listing bad exits.
12010 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
12011 headers for content, so that we can work better in the presence of
12012 caching HTTP proxies.
12013 - Allow authorities to list nodes as bad exits by fingerprint or by
12016 o Minor features, controller:
12017 - Add a REASON field to CIRC events; for backward compatibility, this
12018 field is sent only to controllers that have enabled the extended
12019 event format. Also, add additional reason codes to explain why
12020 a given circuit has been destroyed or truncated. (Patches from
12022 - Add a REMOTE_REASON field to extended CIRC events to tell the
12023 controller about why a remote OR told us to close a circuit.
12024 - Stream events also now have REASON and REMOTE_REASON fields,
12025 working much like those for circuit events.
12026 - There's now a GETINFO ns/... field so that controllers can ask Tor
12027 about the current status of a router.
12028 - A new event type "NS" to inform a controller when our opinion of
12029 a router's status has changed.
12030 - Add a GETINFO events/names and GETINFO features/names so controllers
12031 can tell which events and features are supported.
12032 - A new CLEARDNSCACHE signal to allow controllers to clear the
12033 client-side DNS cache without expiring circuits.
12035 o Security bugfixes:
12036 - When the user sends a NEWNYM signal, clear the client-side DNS
12037 cache too. Otherwise we continue to act on previous information.
12040 - Avoid sending junk to controllers or segfaulting when a controller
12041 uses EVENT_NEW_DESC with verbose nicknames.
12042 - Stop triggering asserts if the controller tries to extend hidden
12043 service circuits (reported by mwenge).
12044 - Avoid infinite loop on unexpected controller input.
12045 - When the controller does a "GETINFO network-status", tell it
12046 about even those routers whose descriptors are very old, and use
12047 long nicknames where appropriate.
12048 - Change NT service functions to be loaded on demand. This lets us
12049 build with MinGW without breaking Tor for Windows 98 users.
12050 - Do DirPort reachability tests less often, since a single test
12051 chews through many circuits before giving up.
12052 - In the hidden service example in torrc.sample, stop recommending
12053 esoteric and discouraged hidden service options.
12054 - When stopping an NT service, wait up to 10 sec for it to actually
12055 stop. Patch from Matt Edman; resolves bug 295.
12056 - Fix handling of verbose nicknames with ORCONN controller events:
12057 make them show up exactly when requested, rather than exactly when
12059 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
12060 printing a duplicate "$" in the keys we send (reported by mwenge).
12061 - Correctly set maximum connection limit on Cygwin. (This time
12063 - Try to detect Windows correctly when cross-compiling.
12064 - Detect the size of the routers file correctly even if it is
12065 corrupted (on systems without mmap) or not page-aligned (on systems
12066 with mmap). This bug was harmless.
12067 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
12068 to open a stream fails; now we do in more cases. This should
12069 make clients able to find a good exit faster in some cases, since
12070 unhandleable requests will now get an error rather than timing out.
12071 - Resolve two memory leaks when rebuilding the on-disk router cache
12072 (reported by fookoowa).
12073 - Clean up minor code warnings suggested by the MIPSpro C compiler,
12074 and reported by some Centos users.
12075 - Controller signals now work on non-Unix platforms that don't define
12076 SIGUSR1 and SIGUSR2 the way we expect.
12077 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
12078 values before failing, and always enables eventdns.
12079 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
12080 Try to fix this in configure.in by checking for most functions
12081 before we check for libevent.
12084 Changes in version 0.1.2.2-alpha - 2006-10-07
12086 - Make our async eventdns library on-by-default for Tor servers,
12087 and plan to deprecate the separate dnsworker threads.
12088 - Add server-side support for "reverse" DNS lookups (using PTR
12089 records so clients can determine the canonical hostname for a given
12090 IPv4 address). Only supported by servers using eventdns; servers
12091 now announce in their descriptors whether they support eventdns.
12092 - Specify and implement client-side SOCKS5 interface for reverse DNS
12093 lookups (see doc/socks-extensions.txt).
12094 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
12095 connect to directory servers through Tor. Previously, clients needed
12096 to find Tor exits to make private connections to directory servers.
12097 - Avoid choosing Exit nodes for entry or middle hops when the
12098 total bandwidth available from non-Exit nodes is much higher than
12099 the total bandwidth available from Exit nodes.
12100 - Workaround for name servers (like Earthlink's) that hijack failing
12101 DNS requests and replace the no-such-server answer with a "helpful"
12102 redirect to an advertising-driven search portal. Also work around
12103 DNS hijackers who "helpfully" decline to hijack known-invalid
12104 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
12105 lets you turn it off.
12106 - Send out a burst of long-range padding cells once we've established
12107 that we're reachable. Spread them over 4 circuits, so hopefully
12108 a few will be fast. This exercises our bandwidth and bootstraps
12109 us into the directory more quickly.
12111 o New/improved config options:
12112 - Add new config option "ResolvConf" to let the server operator
12113 choose an alternate resolve.conf file when using eventdns.
12114 - Add an "EnforceDistinctSubnets" option to control our "exclude
12115 servers on the same /16" behavior. It's still on by default; this
12116 is mostly for people who want to operate private test networks with
12117 all the machines on the same subnet.
12118 - If one of our entry guards is on the ExcludeNodes list, or the
12119 directory authorities don't think it's a good guard, treat it as
12120 if it were unlisted: stop using it as a guard, and throw it off
12121 the guards list if it stays that way for a long time.
12122 - Allow directory authorities to be marked separately as authorities
12123 for the v1 directory protocol, the v2 directory protocol, and
12124 as hidden service directories, to make it easier to retire old
12125 authorities. V1 authorities should set "HSAuthoritativeDir 1"
12126 to continue being hidden service authorities too.
12127 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
12129 o Minor features, controller:
12130 - Fix CIRC controller events so that controllers can learn the
12131 identity digests of non-Named servers used in circuit paths.
12132 - Let controllers ask for more useful identifiers for servers. Instead
12133 of learning identity digests for un-Named servers and nicknames
12134 for Named servers, the new identifiers include digest, nickname,
12135 and indication of Named status. Off by default; see control-spec.txt
12136 for more information.
12137 - Add a "getinfo address" controller command so it can display Tor's
12138 best guess to the user.
12139 - New controller event to alert the controller when our server
12140 descriptor has changed.
12141 - Give more meaningful errors on controller authentication failure.
12143 o Minor features, other:
12144 - When asked to resolve a hostname, don't use non-exit servers unless
12145 requested to do so. This allows servers with broken DNS to be
12146 useful to the network.
12147 - Divide eventdns log messages into warn and info messages.
12148 - Reserve the nickname "Unnamed" for routers that can't pick
12149 a hostname: any router can call itself Unnamed; directory
12150 authorities will never allocate Unnamed to any particular router;
12151 clients won't believe that any router is the canonical Unnamed.
12152 - Only include function names in log messages for info/debug messages.
12153 For notice/warn/err, the content of the message should be clear on
12154 its own, and printing the function name only confuses users.
12155 - Avoid some false positives during reachability testing: don't try
12156 to test via a server that's on the same /24 as us.
12157 - If we fail to build a circuit to an intended enclave, and it's
12158 not mandatory that we use that enclave, stop wanting it.
12159 - When eventdns is enabled, allow multithreaded builds on NetBSD and
12160 OpenBSD. (We had previously disabled threads on these platforms
12161 because they didn't have working thread-safe resolver functions.)
12163 o Major bugfixes, anonymity/security:
12164 - If a client asked for a server by name, and there's a named server
12165 in our network-status but we don't have its descriptor yet, we
12166 could return an unnamed server instead.
12167 - Fix NetBSD bug that could allow someone to force uninitialized RAM
12168 to be sent to a server's DNS resolver. This only affects NetBSD
12169 and other platforms that do not bounds-check tolower().
12170 - Reject (most) attempts to use Tor circuits with length one. (If
12171 many people start using Tor as a one-hop proxy, exit nodes become
12172 a more attractive target for compromise.)
12173 - Just because your DirPort is open doesn't mean people should be
12174 able to remotely teach you about hidden service descriptors. Now
12175 only accept rendezvous posts if you've got HSAuthoritativeDir set.
12177 o Major bugfixes, other:
12178 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
12179 - When a client asks the server to resolve (not connect to)
12180 an address, and it has a cached answer, give them the cached answer.
12181 Previously, the server would give them no answer at all.
12182 - Allow really slow clients to not hang up five minutes into their
12183 directory downloads (suggested by Adam J. Richter).
12184 - We were building exactly the wrong circuits when we anticipated
12185 hidden service requirements, meaning Tor would have to build all
12186 its circuits on demand.
12187 - Avoid crashing when we mmap a router cache file of size 0.
12188 - When testing reachability of our DirPort, don't launch new
12189 tests when there's already one in progress -- unreachable
12190 servers were stacking up dozens of testing streams.
12192 o Minor bugfixes, correctness:
12193 - If we're a directory mirror and we ask for "all" network status
12194 documents, we would discard status documents from authorities
12195 we don't recognize.
12196 - Avoid a memory corruption bug when creating a hash table for
12198 - Avoid controller-triggered crash when misusing certain commands
12199 from a v0 controller on platforms that do not handle
12200 printf("%s",NULL) gracefully.
12201 - Don't crash when a controller sends a third argument to an
12202 "extendcircuit" request.
12203 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12204 response; fix error code when "getinfo dir/status/" fails.
12205 - Avoid crash when telling controller stream-status and a stream
12207 - Patch from Adam Langley to fix assert() in eventdns.c.
12208 - Fix a debug log message in eventdns to say "X resolved to Y"
12209 instead of "X resolved to X".
12210 - Make eventdns give strings for DNS errors, not just error numbers.
12211 - Track unreachable entry guards correctly: don't conflate
12212 'unreachable by us right now' with 'listed as down by the directory
12213 authorities'. With the old code, if a guard was unreachable by
12214 us but listed as running, it would clog our guard list forever.
12215 - Behave correctly in case we ever have a network with more than
12216 2GB/s total advertised capacity.
12217 - Make TrackExitHosts case-insensitive, and fix the behavior of
12218 ".suffix" TrackExitHosts items to avoid matching in the middle of
12220 - Finally fix the openssl warnings from newer gccs that believe that
12221 ignoring a return value is okay, but casting a return value and
12222 then ignoring it is a sign of madness.
12223 - Prevent the contrib/exitlist script from printing the same
12224 result more than once.
12225 - Patch from Steve Hildrey: Generate network status correctly on
12226 non-versioning dirservers.
12227 - Don't listen to the X-Your-Address-Is hint if you did the lookup
12228 via Tor; otherwise you'll think you're the exit node's IP address.
12230 o Minor bugfixes, performance:
12231 - Two small performance improvements on parsing descriptors.
12232 - Major performance improvement on inserting descriptors: change
12233 algorithm from O(n^2) to O(n).
12234 - Make the common memory allocation path faster on machines where
12235 malloc(0) returns a pointer.
12236 - Start remembering X-Your-Address-Is directory hints even if you're
12237 a client, so you can become a server more smoothly.
12238 - Avoid duplicate entries on MyFamily line in server descriptor.
12240 o Packaging, features:
12241 - Remove architecture from OS X builds. The official builds are
12242 now universal binaries.
12243 - The Debian package now uses --verify-config when (re)starting,
12244 to distinguish configuration errors from other errors.
12245 - Update RPMs to require libevent 1.1b.
12247 o Packaging, bugfixes:
12248 - Patches so Tor builds with MinGW on Windows.
12249 - Patches so Tor might run on Cygwin again.
12250 - Resume building on non-gcc compilers and ancient gcc. Resume
12251 building with the -O0 compile flag. Resume building cleanly on
12253 - Run correctly on OS X platforms with case-sensitive filesystems.
12254 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
12255 - Add autoconf checks so Tor can build on Solaris x86 again.
12258 - Documented (and renamed) ServerDNSSearchDomains and
12259 ServerDNSResolvConfFile options.
12260 - Be clearer that the *ListenAddress directives can be repeated
12264 Changes in version 0.1.1.24 - 2006-09-29
12266 - Allow really slow clients to not hang up five minutes into their
12267 directory downloads (suggested by Adam J. Richter).
12268 - Fix major performance regression from 0.1.0.x: instead of checking
12269 whether we have enough directory information every time we want to
12270 do something, only check when the directory information has changed.
12271 This should improve client CPU usage by 25-50%.
12272 - Don't crash if, after a server has been running for a while,
12273 it can't resolve its hostname.
12276 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12277 - Don't crash when the controller receives a third argument to an
12278 "extendcircuit" request.
12279 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
12280 response; fix error code when "getinfo dir/status/" fails.
12281 - Fix configure.in to not produce broken configure files with
12282 more recent versions of autoconf. Thanks to Clint for his auto*
12284 - Fix security bug on NetBSD that could allow someone to force
12285 uninitialized RAM to be sent to a server's DNS resolver. This
12286 only affects NetBSD and other platforms that do not bounds-check
12288 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
12289 methods: these are known to be buggy.
12290 - If we're a directory mirror and we ask for "all" network status
12291 documents, we would discard status documents from authorities
12292 we don't recognize.
12295 Changes in version 0.1.2.1-alpha - 2006-08-27
12297 - Add "eventdns" async dns library from Adam Langley, tweaked to
12298 build on OSX and Windows. Only enabled if you pass the
12299 --enable-eventdns argument to configure.
12300 - Allow servers with no hostname or IP address to learn their
12301 IP address by asking the directory authorities. This code only
12302 kicks in when you would normally have exited with a "no address"
12303 error. Nothing's authenticated, so use with care.
12304 - Rather than waiting a fixed amount of time between retrying
12305 application connections, we wait only 5 seconds for the first,
12306 10 seconds for the second, and 15 seconds for each retry after
12307 that. Hopefully this will improve the expected user experience.
12308 - Patch from Tup to add support for transparent AP connections:
12309 this basically bundles the functionality of trans-proxy-tor
12310 into the Tor mainline. Now hosts with compliant pf/netfilter
12311 implementations can redirect TCP connections straight to Tor
12312 without diverting through SOCKS. Needs docs.
12313 - Busy directory servers save lots of memory by spooling server
12314 descriptors, v1 directories, and v2 networkstatus docs to buffers
12315 as needed rather than en masse. Also mmap the cached-routers
12316 files, so we don't need to keep the whole thing in memory too.
12317 - Automatically avoid picking more than one node from the same
12318 /16 network when constructing a circuit.
12319 - Revise and clean up the torrc.sample that we ship with; add
12320 a section for BandwidthRate and BandwidthBurst.
12323 - Split circuit_t into origin_circuit_t and or_circuit_t, and
12324 split connection_t into edge, or, dir, control, and base structs.
12325 These will save quite a bit of memory on busy servers, and they'll
12326 also help us track down bugs in the code and bugs in the spec.
12327 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
12328 or later. Log when we are doing this, so we can diagnose it when
12329 it fails. (Also, recommend libevent 1.1b for kqueue and
12330 win32 methods; deprecate libevent 1.0b harder; make libevent
12331 recommendation system saner.)
12332 - Start being able to build universal binaries on OS X (thanks
12334 - Export the default exit policy via the control port, so controllers
12335 don't need to guess what it is / will be later.
12336 - Add a man page entry for ProtocolWarnings.
12337 - Add TestVia config option to the man page.
12338 - Remove even more protocol-related warnings from Tor server logs,
12339 such as bad TLS handshakes and malformed begin cells.
12340 - Stop fetching descriptors if you're not a dir mirror and you
12341 haven't tried to establish any circuits lately. [This currently
12342 causes some dangerous behavior, because when you start up again
12343 you'll use your ancient server descriptors.]
12344 - New DirPort behavior: if you have your dirport set, you download
12345 descriptors aggressively like a directory mirror, whether or not
12346 your ORPort is set.
12347 - Get rid of the router_retry_connections notion. Now routers
12348 no longer try to rebuild long-term connections to directory
12349 authorities, and directory authorities no longer try to rebuild
12350 long-term connections to all servers. We still don't hang up
12351 connections in these two cases though -- we need to look at it
12352 more carefully to avoid flapping, and we likely need to wait til
12353 0.1.1.x is obsolete.
12354 - Drop compatibility with obsolete Tors that permit create cells
12355 to have the wrong circ_id_type.
12356 - Re-enable per-connection rate limiting. Get rid of the "OP
12357 bandwidth" concept. Lay groundwork for "bandwidth classes" --
12358 separate global buckets that apply depending on what sort of conn
12360 - Start publishing one minute or so after we find our ORPort
12361 to be reachable. This will help reduce the number of descriptors
12362 we have for ourselves floating around, since it's quite likely
12363 other things (e.g. DirPort) will change during that minute too.
12364 - Fork the v1 directory protocol into its own spec document,
12365 and mark dir-spec.txt as the currently correct (v2) spec.
12368 - When we find our DirPort to be reachable, publish a new descriptor
12369 so we'll tell the world (reported by pnx).
12370 - Publish a new descriptor after we hup/reload. This is important
12371 if our config has changed such that we'll want to start advertising
12372 our DirPort now, etc.
12373 - Allow Tor to start when RunAsDaemon is set but no logs are set.
12374 - When we have a state file we cannot parse, tell the user and
12375 move it aside. Now we avoid situations where the user starts
12376 Tor in 1904, Tor writes a state file with that timestamp in it,
12377 the user fixes her clock, and Tor refuses to start.
12378 - Fix configure.in to not produce broken configure files with
12379 more recent versions of autoconf. Thanks to Clint for his auto*
12381 - "tor --verify-config" now exits with -1(255) or 0 depending on
12382 whether the config options are bad or good.
12383 - Resolve bug 321 when using dnsworkers: append a period to every
12384 address we resolve at the exit node, so that we do not accidentally
12385 pick up local addresses, and so that failing searches are retried
12386 in the resolver search domains. (This is already solved for
12387 eventdns.) (This breaks Blossom servers for now.)
12388 - If we are using an exit enclave and we can't connect, e.g. because
12389 its webserver is misconfigured to not listen on localhost, then
12390 back off and try connecting from somewhere else before we fail.
12393 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
12394 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
12395 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
12396 when the IP address is mapped through MapAddress to a hostname.
12397 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
12398 useless IPv6 DNS resolves.
12399 - Patch suggested by Karsten Loesing: respond to SIGNAL command
12400 before we execute the signal, in case the signal shuts us down.
12401 - Clean up AllowInvalidNodes man page entry.
12402 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
12403 - Add more asserts to track down an assert error on a windows Tor
12404 server with connection_add being called with socket == -1.
12405 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
12406 - Fix misleading log messages: an entry guard that is "unlisted",
12407 as well as not known to be "down" (because we've never heard
12408 of it), is not therefore "up".
12409 - Remove code to special-case "-cvs" ending, since it has not
12410 actually mattered since 0.0.9.
12411 - Make our socks5 handling more robust to broken socks clients:
12412 throw out everything waiting on the buffer in between socks
12413 handshake phases, since they can't possibly (so the theory
12414 goes) have predicted what we plan to respond to them.
12417 Changes in version 0.1.1.23 - 2006-07-30
12419 - Fast Tor servers, especially exit nodes, were triggering asserts
12420 due to a bug in handling the list of pending DNS resolves. Some
12421 bugs still remain here; we're hunting them.
12422 - Entry guards could crash clients by sending unexpected input.
12423 - More fixes on reachability testing: if you find yourself reachable,
12424 then don't ever make any client requests (so you stop predicting
12425 circuits), then hup or have your clock jump, then later your IP
12426 changes, you won't think circuits are working, so you won't try to
12427 test reachability, so you won't publish.
12430 - Avoid a crash if the controller does a resetconf firewallports
12431 and then a setconf fascistfirewall=1.
12432 - Avoid an integer underflow when the dir authority decides whether
12433 a router is stable: we might wrongly label it stable, and compute
12434 a slightly wrong median stability, when a descriptor is published
12436 - Fix a place where we might trigger an assert if we can't build our
12437 own server descriptor yet.
12440 Changes in version 0.1.1.22 - 2006-07-05
12442 - Fix a big bug that was causing servers to not find themselves
12443 reachable if they changed IP addresses. Since only 0.1.1.22+
12444 servers can do reachability testing correctly, now we automatically
12445 make sure to test via one of these.
12446 - Fix to allow clients and mirrors to learn directory info from
12447 descriptor downloads that get cut off partway through.
12448 - Directory authorities had a bug in deciding if a newly published
12449 descriptor was novel enough to make everybody want a copy -- a few
12450 servers seem to be publishing new descriptors many times a minute.
12452 - Fix a rare bug that was causing some servers to complain about
12453 "closing wedged cpuworkers" and skip some circuit create requests.
12454 - Make the Exit flag in directory status documents actually work.
12457 Changes in version 0.1.1.21 - 2006-06-10
12458 o Crash and assert fixes from 0.1.1.20:
12459 - Fix a rare crash on Tor servers that have enabled hibernation.
12460 - Fix a seg fault on startup for Tor networks that use only one
12461 directory authority.
12462 - Fix an assert from a race condition that occurs on Tor servers
12463 while exiting, where various threads are trying to log that they're
12464 exiting, and delete the logs, at the same time.
12465 - Make our unit tests pass again on certain obscure platforms.
12468 - Add support for building SUSE RPM packages.
12469 - Speed up initial bootstrapping for clients: if we are making our
12470 first ever connection to any entry guard, then don't mark it down
12472 - When only one Tor server in the network is labelled as a guard,
12473 and we've already picked him, we would cycle endlessly picking him
12474 again, being unhappy about it, etc. Now we specifically exclude
12475 current guards when picking a new guard.
12476 - Servers send create cells more reliably after the TLS connection
12477 is established: we were sometimes forgetting to send half of them
12478 when we had more than one pending.
12479 - If we get a create cell that asks us to extend somewhere, but the
12480 Tor server there doesn't match the expected digest, we now send
12481 a destroy cell back, rather than silently doing nothing.
12482 - Make options->RedirectExit work again.
12483 - Make cookie authentication for the controller work again.
12484 - Stop being picky about unusual characters in the arguments to
12485 mapaddress. It's none of our business.
12486 - Add a new config option "TestVia" that lets you specify preferred
12487 middle hops to use for test circuits. Perhaps this will let me
12488 debug the reachability problems better.
12490 o Log / documentation fixes:
12491 - If we're a server and some peer has a broken TLS certificate, don't
12492 log about it unless ProtocolWarnings is set, i.e., we want to hear
12493 about protocol violations by others.
12494 - Fix spelling of VirtualAddrNetwork in man page.
12495 - Add a better explanation at the top of the autogenerated torrc file
12496 about what happened to our old torrc.
12499 Changes in version 0.1.1.20 - 2006-05-23
12501 - Downgrade a log severity where servers complain that they're
12503 - Avoid a compile warning on FreeBSD.
12504 - Remove string size limit on NEWDESC messages; solve bug 291.
12505 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
12506 more thoroughly when we're running on windows.
12509 Changes in version 0.1.1.19-rc - 2006-05-03
12511 - Regenerate our local descriptor if it's dirty and we try to use
12512 it locally (e.g. if it changes during reachability detection).
12513 - If we setconf our ORPort to 0, we continued to listen on the
12514 old ORPort and receive connections.
12515 - Avoid a second warning about machine/limits.h on Debian
12517 - Be willing to add our own routerinfo into the routerlist.
12518 Now authorities will include themselves in their directories
12519 and network-statuses.
12520 - Stop trying to upload rendezvous descriptors to every
12521 directory authority: only try the v1 authorities.
12522 - Servers no longer complain when they think they're not
12523 registered with the directory authorities. There were too many
12525 - Backport dist-rpm changes so rpms can be built without errors.
12528 - Implement an option, VirtualAddrMask, to set which addresses
12529 get handed out in response to mapaddress requests. This works
12530 around a bug in tsocks where 127.0.0.0/8 is never socksified.
12533 Changes in version 0.1.1.18-rc - 2006-04-10
12535 - Work harder to download live network-statuses from all the
12536 directory authorities we know about. Improve the threshold
12537 decision logic so we're more robust to edge cases.
12538 - When fetching rendezvous descriptors, we were willing to ask
12539 v2 authorities too, which would always return 404.
12542 - Stop listing down or invalid nodes in the v1 directory. This will
12543 reduce its bulk by about 1/3, and reduce load on directory
12545 - When deciding whether a router is Fast or Guard-worthy, consider
12546 his advertised BandwidthRate and not just the BandwidthCapacity.
12547 - No longer ship INSTALL and README files -- they are useless now.
12548 - Force rpmbuild to behave and honor target_cpu.
12549 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
12550 - Start to include translated versions of the tor-doc-*.html
12551 files, along with the screenshots. Still needs more work.
12552 - Start sending back 512 and 451 errors if mapaddress fails,
12553 rather than not sending anything back at all.
12554 - When we fail to bind or listen on an incoming or outgoing
12555 socket, we should close it before failing. otherwise we just
12556 leak it. (thanks to weasel for finding.)
12557 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
12558 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
12559 - Make NoPublish (even though deprecated) work again.
12560 - Fix a minor security flaw where a versioning auth dirserver
12561 could list a recommended version many times in a row to make
12562 clients more convinced that it's recommended.
12563 - Fix crash bug if there are two unregistered servers running
12564 with the same nickname, one of them is down, and you ask for
12565 them by nickname in your EntryNodes or ExitNodes. Also, try
12566 to pick the one that's running rather than an arbitrary one.
12567 - Fix an infinite loop we could hit if we go offline for too long.
12568 - Complain when we hit WSAENOBUFS on recv() or write() too.
12569 Perhaps this will help us hunt the bug.
12570 - If you're not a versioning dirserver, don't put the string
12571 "client-versions \nserver-versions \n" in your network-status.
12572 - Lower the minimum required number of file descriptors to 1000,
12573 so we can have some overhead for Valgrind on Linux, where the
12574 default ulimit -n is 1024.
12577 - Add tor.dizum.com as the fifth authoritative directory server.
12578 - Add a new config option FetchUselessDescriptors, off by default,
12579 for when you plan to run "exitlist" on your client and you want
12580 to know about even the non-running descriptors.
12583 Changes in version 0.1.1.17-rc - 2006-03-28
12585 - Clients and servers since 0.1.1.10-alpha have been expiring
12586 connections whenever they are idle for 5 minutes and they *do*
12587 have circuits on them. Oops. With this new version, clients will
12588 discard their previous entry guard choices and avoid choosing
12589 entry guards running these flawed versions.
12590 - Fix memory leak when uncompressing concatenated zlib streams. This
12591 was causing substantial leaks over time on Tor servers.
12592 - The v1 directory was including servers as much as 48 hours old,
12593 because that's how the new routerlist->routers works. Now only
12594 include them if they're 20 hours old or less.
12597 - Resume building on irix64, netbsd 2.0, etc.
12598 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
12600 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
12601 and it is confusing some users.
12602 - Mirrors stop caching the v1 directory so often.
12603 - Make the max number of old descriptors that a cache will hold
12604 rise with the number of directory authorities, so we can scale.
12605 - Change our win32 uname() hack to be more forgiving about what
12606 win32 versions it thinks it's found.
12609 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
12611 - When the controller's *setconf commands fail, collect an error
12612 message in a string and hand it back to the controller.
12613 - Make the v2 dir's "Fast" flag based on relative capacity, just
12614 like "Stable" is based on median uptime. Name everything in the
12615 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
12616 - Log server fingerprint on startup, so new server operators don't
12617 have to go hunting around their filesystem for it.
12618 - Return a robots.txt on our dirport to discourage google indexing.
12619 - Let the controller ask for GETINFO dir/status/foo so it can ask
12620 directly rather than connecting to the dir port. Only works when
12621 dirport is set for now.
12623 o New config options rather than constants in the code:
12624 - SocksTimeout: How long do we let a socks connection wait
12625 unattached before we fail it?
12626 - CircuitBuildTimeout: Cull non-open circuits that were born
12627 at least this many seconds ago.
12628 - CircuitIdleTimeout: Cull open clean circuits that were born
12629 at least this many seconds ago.
12632 Changes in version 0.1.1.16-rc - 2006-03-18
12633 o Bugfixes on 0.1.1.15-rc:
12634 - Fix assert when the controller asks to attachstream a connect-wait
12635 or resolve-wait stream.
12636 - Now do address rewriting when the controller asks us to attach
12637 to a particular circuit too. This will let Blossom specify
12638 "moria2.exit" without having to learn what moria2's IP address is.
12639 - Make the "tor --verify-config" command-line work again, so people
12640 can automatically check if their torrc will parse.
12641 - Authoritative dirservers no longer require an open connection from
12642 a server to consider him "reachable". We need this change because
12643 when we add new auth dirservers, old servers won't know not to
12645 - Let Tor build on Sun CC again.
12646 - Fix an off-by-one buffer size in dirserv.c that magically never
12647 hit our three authorities but broke sjmurdoch's own tor network.
12648 - If we as a directory mirror don't know of any v1 directory
12649 authorities, then don't try to cache any v1 directories.
12650 - Stop warning about unknown servers in our family when they are
12651 given as hex digests.
12652 - Stop complaining as quickly to the server operator that he
12653 hasn't registered his nickname/key binding.
12654 - Various cleanups so we can add new V2 Auth Dirservers.
12655 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
12656 reflect the updated flags in our v2 dir protocol.
12657 - Resume allowing non-printable characters for exit streams (both
12658 for connecting and for resolving). Now we tolerate applications
12659 that don't follow the RFCs. But continue to block malformed names
12662 o Bugfixes on 0.1.0.x:
12663 - Fix assert bug in close_logs(): when we close and delete logs,
12664 remove them all from the global "logfiles" list.
12665 - Fix minor integer overflow in calculating when we expect to use up
12666 our bandwidth allocation before hibernating.
12667 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
12668 there are multiple SSLs installed with different versions.
12669 - When we try to be a server and Address is not explicitly set and
12670 our hostname resolves to a private IP address, try to use an
12671 interface address if it has a public address. Now Windows machines
12672 that think of themselves as localhost can work by default.
12675 - Let the controller ask for GETINFO dir/server/foo so it can ask
12676 directly rather than connecting to the dir port.
12677 - Let the controller tell us about certain router descriptors
12678 that it doesn't want Tor to use in circuits. Implement
12679 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
12680 - New config option SafeSocks to reject all application connections
12681 using unsafe socks protocols. Defaults to off.
12684 Changes in version 0.1.1.15-rc - 2006-03-11
12685 o Bugfixes and cleanups:
12686 - When we're printing strings from the network, don't try to print
12687 non-printable characters. This protects us against shell escape
12688 sequence exploits, and also against attacks to fool humans into
12689 misreading their logs.
12690 - Fix a bug where Tor would fail to establish any connections if you
12691 left it off for 24 hours and then started it: we were happy with
12692 the obsolete network statuses, but they all referred to router
12693 descriptors that were too old to fetch, so we ended up with no
12694 valid router descriptors.
12695 - Fix a seg fault in the controller's "getinfo orconn-status"
12696 command while listing status on incoming handshaking connections.
12697 Introduce a status name "NEW" for these connections.
12698 - If we get a linelist or linelist_s config option from the torrc
12699 (e.g. ExitPolicy) and it has no value, warn and skip rather than
12700 silently resetting it to its default.
12701 - Don't abandon entry guards until they've been down or gone for
12703 - Cleaner and quieter log messages.
12706 - New controller signal NEWNYM that makes new application requests
12707 use clean circuits.
12708 - Add a new circuit purpose 'controller' to let the controller ask
12709 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
12710 controller command to let you specify the purpose if you're
12711 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
12712 command to let you change a circuit's purpose after it's been
12714 - Accept "private:*" in routerdesc exit policies; not generated yet
12715 because older Tors do not understand it.
12716 - Add BSD-style contributed startup script "rc.subr" from Peter
12720 Changes in version 0.1.1.14-alpha - 2006-02-20
12721 o Bugfixes on 0.1.1.x:
12722 - Don't die if we ask for a stdout or stderr log (even implicitly)
12723 and we're set to RunAsDaemon -- just warn.
12724 - We still had a few bugs in the OR connection rotation code that
12725 caused directory servers to slowly aggregate connections to other
12726 fast Tor servers. This time for sure!
12727 - Make log entries on Win32 include the name of the function again.
12728 - We were treating a pair of exit policies if they were equal even
12729 if one said accept and the other said reject -- causing us to
12730 not always publish a new descriptor since we thought nothing
12732 - Retry pending server downloads as well as pending networkstatus
12733 downloads when we unexpectedly get a socks request.
12734 - We were ignoring the IS_FAST flag in the directory status,
12735 meaning we were willing to pick trivial-bandwidth nodes for "fast"
12737 - If the controller's SAVECONF command fails (e.g. due to file
12738 permissions), let the controller know that it failed.
12741 - If we're trying to be a Tor server and running Windows 95/98/ME
12742 as a server, explain that we'll likely crash.
12743 - When we're a server, a client asks for an old-style directory,
12744 and our write bucket is empty, don't give it to him. This way
12745 small servers can continue to serve the directory *sometimes*,
12746 without getting overloaded.
12747 - Compress exit policies even more -- look for duplicate lines
12749 - Clients now honor the "guard" flag in the router status when
12750 picking entry guards, rather than looking at is_fast or is_stable.
12751 - Retain unrecognized lines in $DATADIR/state file, so that we can
12752 be forward-compatible.
12753 - Generate 18.0.0.0/8 address policy format in descs when we can;
12754 warn when the mask is not reducible to a bit-prefix.
12755 - Let the user set ControlListenAddress in the torrc. This can be
12756 dangerous, but there are some cases (like a secured LAN) where it
12758 - Split ReachableAddresses into ReachableDirAddresses and
12759 ReachableORAddresses, so we can restrict Dir conns to port 80
12760 and OR conns to port 443.
12761 - Now we can target arch and OS in rpm builds (contributed by
12762 Phobos). Also make the resulting dist-rpm filename match the
12764 - New config options to help controllers: FetchServerDescriptors
12765 and FetchHidServDescriptors for whether to fetch server
12766 info and hidserv info or let the controller do it, and
12767 PublishServerDescriptor and PublishHidServDescriptors.
12768 - Also let the controller set the __AllDirActionsPrivate config
12769 option if you want all directory fetches/publishes to happen via
12770 Tor (it assumes your controller bootstraps your circuits).
12773 Changes in version 0.1.0.17 - 2006-02-17
12774 o Crash bugfixes on 0.1.0.x:
12775 - When servers with a non-zero DirPort came out of hibernation,
12776 sometimes they would trigger an assert.
12778 o Other important bugfixes:
12779 - On platforms that don't have getrlimit (like Windows), we were
12780 artificially constraining ourselves to a max of 1024
12781 connections. Now just assume that we can handle as many as 15000
12782 connections. Hopefully this won't cause other problems.
12784 o Backported features:
12785 - When we're a server, a client asks for an old-style directory,
12786 and our write bucket is empty, don't give it to him. This way
12787 small servers can continue to serve the directory *sometimes*,
12788 without getting overloaded.
12789 - Whenever you get a 503 in response to a directory fetch, try
12790 once more. This will become important once servers start sending
12791 503's whenever they feel busy.
12792 - Fetch a new directory every 120 minutes, not every 40 minutes.
12793 Now that we have hundreds of thousands of users running the old
12794 directory algorithm, it's starting to hurt a lot.
12795 - Bump up the period for forcing a hidden service descriptor upload
12796 from 20 minutes to 1 hour.
12799 Changes in version 0.1.1.13-alpha - 2006-02-09
12800 o Crashes in 0.1.1.x:
12801 - When you tried to setconf ORPort via the controller, Tor would
12802 crash. So people using TorCP to become a server were sad.
12803 - Solve (I hope) the stack-smashing bug that we were seeing on fast
12804 servers. The problem appears to be something do with OpenSSL's
12805 random number generation, or how we call it, or something. Let me
12806 know if the crashes continue.
12807 - Turn crypto hardware acceleration off by default, until we find
12808 somebody smart who can test it for us. (It appears to produce
12809 seg faults in at least some cases.)
12810 - Fix a rare assert error when we've tried all intro points for
12811 a hidden service and we try fetching the service descriptor again:
12812 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
12815 - Fix a major load balance bug: we were round-robining in 16 KB
12816 chunks, and servers with bandwidthrate of 20 KB, while downloading
12817 a 600 KB directory, would starve their other connections. Now we
12818 try to be a bit more fair.
12819 - Dir authorities and mirrors were never expiring the newest
12820 descriptor for each server, causing memory and directory bloat.
12821 - Fix memory-bloating and connection-bloating bug on servers: We
12822 were never closing any connection that had ever had a circuit on
12823 it, because we were checking conn->n_circuits == 0, yet we had a
12824 bug that let it go negative.
12825 - Make Tor work using squid as your http proxy again -- squid
12826 returns an error if you ask for a URL that's too long, and it uses
12827 a really generic error message. Plus, many people are behind a
12828 transparent squid so they don't even realize it.
12829 - On platforms that don't have getrlimit (like Windows), we were
12830 artificially constraining ourselves to a max of 1024
12831 connections. Now just assume that we can handle as many as 15000
12832 connections. Hopefully this won't cause other problems.
12833 - Add a new config option ExitPolicyRejectPrivate which defaults to
12834 1. This means all exit policies will begin with rejecting private
12835 addresses, unless the server operator explicitly turns it off.
12838 - Clients no longer download descriptors for non-running
12840 - Before we add new directory authorities, we should make it
12841 clear that only v1 authorities should receive/publish hidden
12842 service descriptors.
12845 - As soon as we've fetched some more directory info, immediately
12846 try to download more server descriptors. This way we don't have
12847 a 10 second pause during initial bootstrapping.
12848 - Remove even more loud log messages that the server operator can't
12850 - When we're running an obsolete or un-recommended version, make
12851 the log message more clear about what the problem is and what
12852 versions *are* still recommended.
12853 - Provide a more useful warn message when our onion queue gets full:
12854 the CPU is too slow or the exit policy is too liberal.
12855 - Don't warn when we receive a 503 from a dirserver/cache -- this
12856 will pave the way for them being able to refuse if they're busy.
12857 - When we fail to bind a listener, try to provide a more useful
12858 log message: e.g., "Is Tor already running?"
12859 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
12860 Goldberg can prove things about our handshake protocol more
12862 - MaxConn has been obsolete for a while now. Document the ConnLimit
12863 config option, which is a *minimum* number of file descriptors
12864 that must be available else Tor refuses to start.
12865 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
12866 if you log to syslog and want something other than LOG_DAEMON.
12867 - Make dirservers generate a separate "guard" flag to mean,
12868 "would make a good entry guard". Make clients parse it and vote
12869 on it. Not used by clients yet.
12870 - Implement --with-libevent-dir option to ./configure. Also, improve
12871 search techniques to find libevent, and use those for openssl too.
12872 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
12873 - Only start testing reachability once we've established a
12874 circuit. This will make startup on dirservers less noisy.
12875 - Don't try to upload hidden service descriptors until we have
12876 established a circuit.
12877 - Fix the controller's "attachstream 0" command to treat conn like
12878 it just connected, doing address remapping, handling .exit and
12879 .onion idioms, and so on. Now we're more uniform in making sure
12880 that the controller hears about new and closing connections.
12883 Changes in version 0.1.1.12-alpha - 2006-01-11
12884 o Bugfixes on 0.1.1.x:
12885 - The fix to close duplicate server connections was closing all
12886 Tor client connections if they didn't establish a circuit
12887 quickly enough. Oops.
12888 - Fix minor memory issue (double-free) that happened on exit.
12890 o Bugfixes on 0.1.0.x:
12891 - Tor didn't warn when it failed to open a log file.
12894 Changes in version 0.1.1.11-alpha - 2006-01-10
12895 o Crashes in 0.1.1.x:
12896 - Include all the assert/crash fixes from 0.1.0.16.
12897 - If you start Tor and then quit very quickly, there were some
12898 races that tried to free things that weren't allocated yet.
12899 - Fix a rare memory stomp if you're running hidden services.
12900 - Fix segfault when specifying DirServer in config without nickname.
12901 - Fix a seg fault when you finish connecting to a server but at
12902 that moment you dump his server descriptor.
12903 - Extendcircuit and Attachstream controller commands would
12904 assert/crash if you don't give them enough arguments.
12905 - Fix an assert error when we're out of space in the connection_list
12906 and we try to post a hidden service descriptor (reported by weasel).
12907 - If you specify a relative torrc path and you set RunAsDaemon in
12908 your torrc, then it chdir()'s to the new directory. If you HUP,
12909 it tries to load the new torrc location, fails, and exits.
12910 The fix: no longer allow a relative path to torrc using -f.
12913 - Implement "entry guards": automatically choose a handful of entry
12914 nodes and stick with them for all circuits. Only pick new guards
12915 when the ones you have are unsuitable, and if the old guards
12916 become suitable again, switch back. This will increase security
12917 dramatically against certain end-point attacks. The EntryNodes
12918 config option now provides some hints about which entry guards you
12919 want to use most; and StrictEntryNodes means to only use those.
12920 - New directory logic: download by descriptor digest, not by
12921 fingerprint. Caches try to download all listed digests from
12922 authorities; clients try to download "best" digests from caches.
12923 This avoids partitioning and isolating attacks better.
12924 - Make the "stable" router flag in network-status be the median of
12925 the uptimes of running valid servers, and make clients pay
12926 attention to the network-status flags. Thus the cutoff adapts
12927 to the stability of the network as a whole, making IRC, IM, etc
12928 connections more reliable.
12931 - Tor servers with dynamic IP addresses were needing to wait 18
12932 hours before they could start doing reachability testing using
12933 the new IP address and ports. This is because they were using
12934 the internal descriptor to learn what to test, yet they were only
12935 rebuilding the descriptor once they decided they were reachable.
12936 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
12937 to download certain server descriptors, throw them away, and then
12938 fetch them again after 30 minutes. Now mirrors throw away these
12939 server descriptors so clients can't get them.
12940 - We were leaving duplicate connections to other ORs open for a week,
12941 rather than closing them once we detect a duplicate. This only
12942 really affected authdirservers, but it affected them a lot.
12943 - Spread the authdirservers' reachability testing over the entire
12944 testing interval, so we don't try to do 500 TLS's at once every
12948 - If the network is down, and we try to connect to a conn because
12949 we have a circuit in mind, and we timeout (30 seconds) because the
12950 network never answers, we were expiring the circuit, but we weren't
12951 obsoleting the connection or telling the entry_guards functions.
12952 - Some Tor servers process billions of cells per day. These statistics
12953 need to be uint64_t's.
12954 - Check for integer overflows in more places, when adding elements
12955 to smartlists. This could possibly prevent a buffer overflow
12956 on malicious huge inputs. I don't see any, but I haven't looked
12958 - ReachableAddresses kept growing new "reject *:*" lines on every
12960 - When you "setconf log" via the controller, it should remove all
12961 logs. We were automatically adding back in a "log notice stdout".
12962 - Newly bootstrapped Tor networks couldn't establish hidden service
12963 circuits until they had nodes with high uptime. Be more tolerant.
12964 - We were marking servers down when they could not answer every piece
12965 of the directory request we sent them. This was far too harsh.
12966 - Fix the torify (tsocks) config file to not use Tor for localhost
12968 - Directory authorities now go to the proper authority when asking for
12969 a networkstatus, even when they want a compressed one.
12970 - Fix a harmless bug that was causing Tor servers to log
12971 "Got an end because of misc error, but we're not an AP. Closing."
12972 - Authorities were treating their own descriptor changes as cosmetic,
12973 meaning the descriptor available in the network-status and the
12974 descriptor that clients downloaded were different.
12975 - The OS X installer was adding a symlink for tor_resolve but
12976 the binary was called tor-resolve (reported by Thomas Hardly).
12977 - Workaround a problem with some http proxies where they refuse GET
12978 requests that specify "Content-Length: 0" (reported by Adrian).
12979 - Fix wrong log message when you add a "HiddenServiceNodes" config
12980 line without any HiddenServiceDir line (reported by Chris Thomas).
12983 - Write the TorVersion into the state file so we have a prayer of
12984 keeping forward and backward compatibility.
12985 - Revive the FascistFirewall config option rather than eliminating it:
12986 now it's a synonym for ReachableAddresses *:80,*:443.
12987 - Clients choose directory servers from the network status lists,
12988 not from their internal list of router descriptors. Now they can
12989 go to caches directly rather than needing to go to authorities
12991 - Directory authorities ignore router descriptors that have only
12992 cosmetic differences: do this for 0.1.0.x servers now too.
12993 - Add a new flag to network-status indicating whether the server
12994 can answer v2 directory requests too.
12995 - Authdirs now stop whining so loudly about bad descriptors that
12996 they fetch from other dirservers. So when there's a log complaint,
12997 it's for sure from a freshly uploaded descriptor.
12998 - Reduce memory requirements in our structs by changing the order
13000 - There used to be two ways to specify your listening ports in a
13001 server descriptor: on the "router" line and with a separate "ports"
13002 line. Remove support for the "ports" line.
13003 - New config option "AuthDirRejectUnlisted" for auth dirservers as
13004 a panic button: if we get flooded with unusable servers we can
13005 revert to only listing servers in the approved-routers file.
13006 - Auth dir servers can now mark a fingerprint as "!reject" or
13007 "!invalid" in the approved-routers file (as its nickname), to
13008 refuse descriptors outright or include them but marked as invalid.
13009 - Servers store bandwidth history across restarts/crashes.
13010 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
13011 get a better idea of why their circuits failed. Not used yet.
13012 - Directory mirrors now cache up to 16 unrecognized network-status
13013 docs. Now we can add new authdirservers and they'll be cached too.
13014 - When picking a random directory, prefer non-authorities if any
13016 - New controller option "getinfo desc/all-recent" to fetch the
13017 latest server descriptor for every router that Tor knows about.
13020 Changes in version 0.1.0.16 - 2006-01-02
13021 o Crash bugfixes on 0.1.0.x:
13022 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
13023 corrupting the heap, losing FDs, or crashing when we need to resize
13024 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
13025 - It turns out sparc64 platforms crash on unaligned memory access
13026 too -- so detect and avoid this.
13027 - Handle truncated compressed data correctly (by detecting it and
13029 - Fix possible-but-unlikely free(NULL) in control.c.
13030 - When we were closing connections, there was a rare case that
13031 stomped on memory, triggering seg faults and asserts.
13032 - Avoid potential infinite recursion when building a descriptor. (We
13033 don't know that it ever happened, but better to fix it anyway.)
13034 - We were neglecting to unlink marked circuits from soon-to-close OR
13035 connections, which caused some rare scribbling on freed memory.
13036 - Fix a memory stomping race bug when closing the joining point of two
13037 rendezvous circuits.
13038 - Fix an assert in time parsing found by Steven Murdoch.
13040 o Other bugfixes on 0.1.0.x:
13041 - When we're doing reachability testing, provide more useful log
13042 messages so the operator knows what to expect.
13043 - Do not check whether DirPort is reachable when we are suppressing
13044 advertising it because of hibernation.
13045 - When building with -static or on Solaris, we sometimes needed -ldl.
13046 - When we're deciding whether a stream has enough circuits around
13047 that can handle it, count the freshly dirty ones and not the ones
13048 that are so dirty they won't be able to handle it.
13049 - When we're expiring old circuits, we had a logic error that caused
13050 us to close new rendezvous circuits rather than old ones.
13051 - Give a more helpful log message when you try to change ORPort via
13052 the controller: you should upgrade Tor if you want that to work.
13053 - We were failing to parse Tor versions that start with "Tor ".
13054 - Tolerate faulty streams better: when a stream fails for reason
13055 exitpolicy, stop assuming that the router is lying about his exit
13056 policy. When a stream fails for reason misc, allow it to retry just
13057 as if it was resolvefailed. When a stream has failed three times,
13058 reset its failure count so we can try again and get all three tries.
13061 Changes in version 0.1.1.10-alpha - 2005-12-11
13062 o Correctness bugfixes on 0.1.0.x:
13063 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
13064 corrupting the heap, losing FDs, or crashing when we need to resize
13065 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
13066 - Stop doing the complex voodoo overkill checking for insecure
13067 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
13068 - When we were closing connections, there was a rare case that
13069 stomped on memory, triggering seg faults and asserts.
13070 - We were neglecting to unlink marked circuits from soon-to-close OR
13071 connections, which caused some rare scribbling on freed memory.
13072 - When we're deciding whether a stream has enough circuits around
13073 that can handle it, count the freshly dirty ones and not the ones
13074 that are so dirty they won't be able to handle it.
13075 - Recover better from TCP connections to Tor servers that are
13076 broken but don't tell you (it happens!); and rotate TLS
13077 connections once a week.
13078 - When we're expiring old circuits, we had a logic error that caused
13079 us to close new rendezvous circuits rather than old ones.
13080 - Fix a scary-looking but apparently harmless bug where circuits
13081 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
13082 servers, and never switch to state CIRCUIT_STATE_OPEN.
13083 - When building with -static or on Solaris, we sometimes needed to
13085 - Give a useful message when people run Tor as the wrong user,
13086 rather than telling them to start chowning random directories.
13087 - We were failing to inform the controller about new .onion streams.
13089 o Security bugfixes on 0.1.0.x:
13090 - Refuse server descriptors if the fingerprint line doesn't match
13091 the included identity key. Tor doesn't care, but other apps (and
13092 humans) might actually be trusting the fingerprint line.
13093 - We used to kill the circuit when we receive a relay command we
13094 don't recognize. Now we just drop it.
13095 - Start obeying our firewall options more rigorously:
13096 . If we can't get to a dirserver directly, try going via Tor.
13097 . Don't ever try to connect (as a client) to a place our
13098 firewall options forbid.
13099 . If we specify a proxy and also firewall options, obey the
13100 firewall options even when we're using the proxy: some proxies
13101 can only proxy to certain destinations.
13102 - Fix a bug found by Lasse Overlier: when we were making internal
13103 circuits (intended to be cannibalized later for rendezvous and
13104 introduction circuits), we were picking them so that they had
13105 useful exit nodes. There was no need for this, and it actually
13106 aids some statistical attacks.
13107 - Start treating internal circuits and exit circuits separately.
13108 It's important to keep them separate because internal circuits
13109 have their last hops picked like middle hops, rather than like
13110 exit hops. So exiting on them will break the user's expectations.
13112 o Bugfixes on 0.1.1.x:
13113 - Take out the mis-feature where we tried to detect IP address
13114 flapping for people with DynDNS, and chose not to upload a new
13115 server descriptor sometimes.
13116 - Try to be compatible with OpenSSL 0.9.6 again.
13117 - Log fix: when the controller is logging about .onion addresses,
13118 sometimes it didn't include the ".onion" part of the address.
13119 - Don't try to modify options->DirServers internally -- if the
13120 user didn't specify any, just add the default ones directly to
13121 the trusted dirserver list. This fixes a bug where people running
13122 controllers would use SETCONF on some totally unrelated config
13123 option, and Tor would start yelling at them about changing their
13125 - Let the controller's redirectstream command specify a port, in
13126 case the controller wants to change that too.
13127 - When we requested a pile of server descriptors, we sometimes
13128 accidentally launched a duplicate request for the first one.
13129 - Bugfix for trackhostexits: write down the fingerprint of the
13130 chosen exit, not its nickname, because the chosen exit might not
13132 - When parsing foo.exit, if foo is unknown, and we are leaving
13133 circuits unattached, set the chosen_exit field and leave the
13134 address empty. This matters because controllers got confused
13136 - Directory authorities no longer try to download server
13137 descriptors that they know they will reject.
13139 o Features and updates:
13140 - Replace balanced trees with hash tables: this should make stuff
13141 significantly faster.
13142 - Resume using the AES counter-mode implementation that we ship,
13143 rather than OpenSSL's. Ours is significantly faster.
13144 - Many other CPU and memory improvements.
13145 - Add a new config option FastFirstHopPK (on by default) so clients
13146 do a trivial crypto handshake for their first hop, since TLS has
13147 already taken care of confidentiality and authentication.
13148 - Add a new config option TestSocks so people can see if their
13149 applications are using socks4, socks4a, socks5-with-ip, or
13150 socks5-with-hostname. This way they don't have to keep mucking
13151 with tcpdump and wondering if something got cached somewhere.
13152 - Warn when listening on a public address for socks. I suspect a
13153 lot of people are setting themselves up as open socks proxies,
13154 and they have no idea that jerks on the Internet are using them,
13155 since they simply proxy the traffic into the Tor network.
13156 - Add "private:*" as an alias in configuration for policies. Now
13157 you can simplify your exit policy rather than needing to list
13158 every single internal or nonroutable network space.
13159 - Add a new controller event type that allows controllers to get
13160 all server descriptors that were uploaded to a router in its role
13161 as authoritative dirserver.
13162 - Start shipping socks-extensions.txt, tor-doc-unix.html,
13163 tor-doc-server.html, and stylesheet.css in the tarball.
13164 - Stop shipping tor-doc.html in the tarball.
13167 Changes in version 0.1.1.9-alpha - 2005-11-15
13168 o Usability improvements:
13169 - Start calling it FooListenAddress rather than FooBindAddress,
13170 since few of our users know what it means to bind an address
13172 - Reduce clutter in server logs. We're going to try to make
13173 them actually usable now. New config option ProtocolWarnings that
13174 lets you hear about how _other Tors_ are breaking the protocol. Off
13176 - Divide log messages into logging domains. Once we put some sort
13177 of interface on this, it will let people looking at more verbose
13178 log levels specify the topics they want to hear more about.
13179 - Make directory servers return better http 404 error messages
13180 instead of a generic "Servers unavailable".
13181 - Check for even more Windows version flags when writing the platform
13182 string in server descriptors, and note any we don't recognize.
13183 - Clean up more of the OpenSSL memory when exiting, so we can detect
13184 memory leaks better.
13185 - Make directory authorities be non-versioning, non-naming by
13186 default. Now we can add new directory servers without requiring
13187 their operators to pay close attention.
13188 - When logging via syslog, include the pid whenever we provide
13189 a log entry. Suggested by Todd Fries.
13191 o Performance improvements:
13192 - Directory servers now silently throw away new descriptors that
13193 haven't changed much if the timestamps are similar. We do this to
13194 tolerate older Tor servers that upload a new descriptor every 15
13195 minutes. (It seemed like a good idea at the time.)
13196 - Inline bottleneck smartlist functions; use fast versions by default.
13197 - Add a "Map from digest to void*" abstraction digestmap_t so we
13198 can do less hex encoding/decoding. Use it in router_get_by_digest()
13199 to resolve a performance bottleneck.
13200 - Allow tor_gzip_uncompress to extract as much as possible from
13201 truncated compressed data. Try to extract as many
13202 descriptors as possible from truncated http responses (when
13203 DIR_PURPOSE_FETCH_ROUTERDESC).
13204 - Make circ->onionskin a pointer, not a static array. moria2 was using
13205 125000 circuit_t's after it had been up for a few weeks, which
13206 translates to 20+ megs of wasted space.
13207 - The private half of our EDH handshake keys are now chosen out
13208 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
13210 o Security improvements:
13211 - Start making directory caches retain old routerinfos, so soon
13212 clients can start asking by digest of descriptor rather than by
13213 fingerprint of server.
13214 - Add half our entropy from RAND_poll in OpenSSL. This knows how
13215 to use egd (if present), openbsd weirdness (if present), vms/os2
13216 weirdness (if we ever port there), and more in the future.
13218 o Bugfixes on 0.1.0.x:
13219 - Do round-robin writes of at most 16 kB per write. This might be
13220 more fair on loaded Tor servers, and it might resolve our Windows
13221 crash bug. It might also slow things down.
13222 - Our TLS handshakes were generating a single public/private
13223 keypair for the TLS context, rather than making a new one for
13224 each new connections. Oops. (But we were still rotating them
13225 periodically, so it's not so bad.)
13226 - When we were cannibalizing a circuit with a particular exit
13227 node in mind, we weren't checking to see if that exit node was
13228 already present earlier in the circuit. Oops.
13229 - When a Tor server's IP changes (e.g. from a dyndns address),
13230 upload a new descriptor so clients will learn too.
13231 - Really busy servers were keeping enough circuits open on stable
13232 connections that they were wrapping around the circuit_id
13233 space. (It's only two bytes.) This exposed a bug where we would
13234 feel free to reuse a circuit_id even if it still exists but has
13235 been marked for close. Try to fix this bug. Some bug remains.
13236 - If we would close a stream early (e.g. it asks for a .exit that
13237 we know would refuse it) but the LeaveStreamsUnattached config
13238 option is set by the controller, then don't close it.
13240 o Bugfixes on 0.1.1.8-alpha:
13241 - Fix a big pile of memory leaks, some of them serious.
13242 - Do not try to download a routerdesc if we would immediately reject
13244 - Resume inserting a newline between all router descriptors when
13245 generating (old style) signed directories, since our spec says
13247 - When providing content-type application/octet-stream for
13248 server descriptors using .z, we were leaving out the
13249 content-encoding header. Oops. (Everything tolerated this just
13250 fine, but that doesn't mean we need to be part of the problem.)
13251 - Fix a potential seg fault in getconf and getinfo using version 1
13252 of the controller protocol.
13253 - Avoid crash: do not check whether DirPort is reachable when we
13254 are suppressing it because of hibernation.
13255 - Make --hash-password not crash on exit.
13258 Changes in version 0.1.1.8-alpha - 2005-10-07
13259 o New features (major):
13260 - Clients don't download or use the directory anymore. Now they
13261 download and use network-statuses from the trusted dirservers,
13262 and fetch individual server descriptors as needed from mirrors.
13263 See dir-spec.txt for all the gory details.
13264 - Be more conservative about whether to advertise our DirPort.
13265 The main change is to not advertise if we're running at capacity
13266 and either a) we could hibernate or b) our capacity is low and
13267 we're using a default DirPort.
13268 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
13270 o New features (minor):
13271 - Try to be smart about when to retry network-status and
13272 server-descriptor fetches. Still needs some tuning.
13273 - Stop parsing, storing, or using running-routers output (but
13274 mirrors still cache and serve it).
13275 - Consider a threshold of versioning dirservers (dirservers who have
13276 an opinion about which Tor versions are still recommended) before
13277 deciding whether to warn the user that he's obsolete.
13278 - Dirservers can now reject/invalidate by key and IP, with the
13279 config options "AuthDirInvalid" and "AuthDirReject". This is
13280 useful since currently we automatically list servers as running
13281 and usable even if we know they're jerks.
13282 - Provide dire warnings to any users who set DirServer; move it out
13283 of torrc.sample and into torrc.complete.
13284 - Add MyFamily to torrc.sample in the server section.
13285 - Add nicknames to the DirServer line, so we can refer to them
13286 without requiring all our users to memorize their IP addresses.
13287 - When we get an EOF or a timeout on a directory connection, note
13288 how many bytes of serverdesc we are dropping. This will help
13289 us determine whether it is smart to parse incomplete serverdesc
13291 - Add a new function to "change pseudonyms" -- that is, to stop
13292 using any currently-dirty circuits for new streams, so we don't
13293 link new actions to old actions. Currently it's only called on
13294 HUP (or SIGNAL RELOAD).
13295 - On sighup, if UseHelperNodes changed to 1, use new circuits.
13296 - Start using RAND_bytes rather than RAND_pseudo_bytes from
13297 OpenSSL. Also, reseed our entropy every hour, not just at
13298 startup. And entropy in 512-bit chunks, not 160-bit chunks.
13300 o Fixes on 0.1.1.7-alpha:
13301 - Nobody ever implemented EVENT_ADDRMAP for control protocol
13302 version 0, so don't let version 0 controllers ask for it.
13303 - If you requested something with too many newlines via the
13304 v1 controller protocol, you could crash tor.
13305 - Fix a number of memory leaks, including some pretty serious ones.
13306 - Re-enable DirPort testing again, so Tor servers will be willing
13307 to advertise their DirPort if it's reachable.
13308 - On TLS handshake, only check the other router's nickname against
13309 its expected nickname if is_named is set.
13311 o Fixes forward-ported from 0.1.0.15:
13312 - Don't crash when we don't have any spare file descriptors and we
13313 try to spawn a dns or cpu worker.
13314 - Make the numbers in read-history and write-history into uint64s,
13315 so they don't overflow and publish negatives in the descriptor.
13317 o Fixes on 0.1.0.x:
13318 - For the OS X package's modified privoxy config file, comment
13319 out the "logfile" line so we don't log everything passed
13321 - We were whining about using socks4 or socks5-with-local-lookup
13322 even when it's an IP in the "virtual" range we designed exactly
13324 - We were leaking some memory every time the client changes IPs.
13325 - Never call free() on tor_malloc()d memory. This will help us
13326 use dmalloc to detect memory leaks.
13327 - Check for named servers when looking them up by nickname;
13328 warn when we'recalling a non-named server by its nickname;
13329 don't warn twice about the same name.
13330 - Try to list MyFamily elements by key, not by nickname, and warn
13331 if we've not heard of the server.
13332 - Make windows platform detection (uname equivalent) smarter.
13333 - It turns out sparc64 doesn't like unaligned access either.
13336 Changes in version 0.1.0.15 - 2005-09-23
13337 o Bugfixes on 0.1.0.x:
13338 - Reject ports 465 and 587 (spam targets) in default exit policy.
13339 - Don't crash when we don't have any spare file descriptors and we
13340 try to spawn a dns or cpu worker.
13341 - Get rid of IgnoreVersion undocumented config option, and make us
13342 only warn, never exit, when we're running an obsolete version.
13343 - Don't try to print a null string when your server finds itself to
13344 be unreachable and the Address config option is empty.
13345 - Make the numbers in read-history and write-history into uint64s,
13346 so they don't overflow and publish negatives in the descriptor.
13347 - Fix a minor memory leak in smartlist_string_remove().
13348 - We were only allowing ourselves to upload a server descriptor at
13349 most every 20 minutes, even if it changed earlier than that.
13350 - Clean up log entries that pointed to old URLs.
13353 Changes in version 0.1.1.7-alpha - 2005-09-14
13354 o Fixes on 0.1.1.6-alpha:
13355 - Exit servers were crashing when people asked them to make a
13356 connection to an address not in their exit policy.
13357 - Looking up a non-existent stream for a v1 control connection would
13359 - Fix a seg fault if we ask a dirserver for a descriptor by
13360 fingerprint but he doesn't know about him.
13361 - SETCONF was appending items to linelists, not clearing them.
13362 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
13363 out and refuse the setconf if it would fail.
13364 - Downgrade the dirserver log messages when whining about
13368 - Add Peter Palfrader's check-tor script to tor/contrib/
13369 It lets you easily check whether a given server (referenced by
13370 nickname) is reachable by you.
13371 - Numerous changes to move towards client-side v2 directories. Not
13374 o Fixes on 0.1.0.x:
13375 - If the user gave tor an odd number of command-line arguments,
13376 we were silently ignoring the last one. Now we complain and fail.
13377 [This wins the oldest-bug prize -- this bug has been present since
13378 November 2002, as released in Tor 0.0.0.]
13379 - Do not use unaligned memory access on alpha, mips, or mipsel.
13380 It *works*, but is very slow, so we treat them as if it doesn't.
13381 - Retry directory requests if we fail to get an answer we like
13382 from a given dirserver (we were retrying before, but only if
13383 we fail to connect).
13384 - When writing the RecommendedVersions line, sort them first.
13385 - When the client asked for a rendezvous port that the hidden
13386 service didn't want to provide, we were sending an IP address
13387 back along with the end cell. Fortunately, it was zero. But stop
13389 - Correct "your server is reachable" log entries to indicate that
13390 it was self-testing that told us so.
13393 Changes in version 0.1.1.6-alpha - 2005-09-09
13394 o Fixes on 0.1.1.5-alpha:
13395 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
13396 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
13397 - Fix bug with tor_memmem finding a match at the end of the string.
13398 - Make unit tests run without segfaulting.
13399 - Resolve some solaris x86 compile warnings.
13400 - Handle duplicate lines in approved-routers files without warning.
13401 - Fix bug where as soon as a server refused any requests due to his
13402 exit policy (e.g. when we ask for localhost and he tells us that's
13403 127.0.0.1 and he won't do it), we decided he wasn't obeying his
13404 exit policy using him for any exits.
13405 - Only do openssl hardware accelerator stuff if openssl version is
13408 o New controller features/fixes:
13409 - Add a "RESETCONF" command so you can set config options like
13410 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
13411 a config option in the torrc with no value, then it clears it
13412 entirely (rather than setting it to its default).
13413 - Add a "GETINFO config-file" to tell us where torrc is.
13414 - Avoid sending blank lines when GETINFO replies should be empty.
13415 - Add a QUIT command for the controller (for using it manually).
13416 - Fix a bug in SAVECONF that was adding default dirservers and
13417 other redundant entries to the torrc file.
13419 o Start on the new directory design:
13420 - Generate, publish, cache, serve new network-status format.
13421 - Publish individual descriptors (by fingerprint, by "all", and by
13423 - Publish client and server recommended versions separately.
13424 - Allow tor_gzip_uncompress() to handle multiple concatenated
13425 compressed strings. Serve compressed groups of router
13426 descriptors. The compression logic here could be more
13428 - Distinguish v1 authorities (all currently trusted directories)
13429 from v2 authorities (all trusted directories).
13430 - Change DirServers config line to note which dirs are v1 authorities.
13431 - Add configuration option "V1AuthoritativeDirectory 1" which
13432 moria1, moria2, and tor26 should set.
13433 - Remove option when getting directory cache to see whether they
13434 support running-routers; they all do now. Replace it with one
13435 to see whether caches support v2 stuff.
13438 - Dirservers now do their own external reachability testing of each
13439 Tor server, and only list them as running if they've been found to
13440 be reachable. We also send back warnings to the server's logs if
13441 it uploads a descriptor that we already believe is unreachable.
13442 - Implement exit enclaves: if we know an IP address for the
13443 destination, and there's a running Tor server at that address
13444 which allows exit to the destination, then extend the circuit to
13445 that exit first. This provides end-to-end encryption and end-to-end
13446 authentication. Also, if the user wants a .exit address or enclave,
13447 use 4 hops rather than 3, and cannibalize a general circ for it
13449 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
13450 controller. Also, rotate dns and cpu workers if the controller
13451 changes options that will affect them; and initialize the dns
13452 worker cache tree whether or not we start out as a server.
13453 - Only upload a new server descriptor when options change, 18
13454 hours have passed, uptime is reset, or bandwidth changes a lot.
13455 - Check [X-]Forwarded-For headers in HTTP requests when generating
13456 log messages. This lets people run dirservers (and caches) behind
13457 Apache but still know which IP addresses are causing warnings.
13459 o Config option changes:
13460 - Replace (Fascist)Firewall* config options with a new
13461 ReachableAddresses option that understands address policies.
13462 For example, "ReachableAddresses *:80,*:443"
13463 - Get rid of IgnoreVersion undocumented config option, and make us
13464 only warn, never exit, when we're running an obsolete version.
13465 - Make MonthlyAccountingStart config option truly obsolete now.
13467 o Fixes on 0.1.0.x:
13468 - Reject ports 465 and 587 in the default exit policy, since
13469 people have started using them for spam too.
13470 - It turns out we couldn't bootstrap a network since we added
13471 reachability detection in 0.1.0.1-rc. Good thing the Tor network
13472 has never gone down. Add an AssumeReachable config option to let
13473 servers and dirservers bootstrap. When we're trying to build a
13474 high-uptime or high-bandwidth circuit but there aren't enough
13475 suitable servers, try being less picky rather than simply failing.
13476 - Our logic to decide if the OR we connected to was the right guy
13477 was brittle and maybe open to a mitm for unverified routers.
13478 - We weren't cannibalizing circuits correctly for
13479 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
13480 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
13481 build those from scratch. This should make hidden services faster.
13482 - Predict required circuits better, with an eye toward making hidden
13483 services faster on the service end.
13484 - Retry streams if the exit node sends back a 'misc' failure. This
13485 should result in fewer random failures. Also, after failing
13486 from resolve failed or misc, reset the num failures, so we give
13487 it a fair shake next time we try.
13488 - Clean up the rendezvous warn log msgs, and downgrade some to info.
13489 - Reduce severity on logs about dns worker spawning and culling.
13490 - When we're shutting down and we do something like try to post a
13491 server descriptor or rendezvous descriptor, don't complain that
13492 we seem to be unreachable. Of course we are, we're shutting down.
13493 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
13494 We don't use them yet, but maybe one day our DNS resolver will be
13495 able to discover them.
13496 - Make ContactInfo mandatory for authoritative directory servers.
13497 - Require server descriptors to list IPv4 addresses -- hostnames
13498 are no longer allowed. This also fixes some potential security
13499 problems with people providing hostnames as their address and then
13500 preferentially resolving them to partition users.
13501 - Change log line for unreachability to explicitly suggest /etc/hosts
13502 as the culprit. Also make it clearer what IP address and ports we're
13503 testing for reachability.
13504 - Put quotes around user-supplied strings when logging so users are
13505 more likely to realize if they add bad characters (like quotes)
13507 - Let auth dir servers start without specifying an Address config
13509 - Make unit tests (and other invocations that aren't the real Tor)
13510 run without launching listeners, creating subdirectories, and so on.
13513 Changes in version 0.1.1.5-alpha - 2005-08-08
13514 o Bugfixes included in 0.1.0.14.
13516 o Bugfixes on 0.1.0.x:
13517 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
13518 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
13519 it would silently using ignore the 6668.
13522 Changes in version 0.1.0.14 - 2005-08-08
13523 o Bugfixes on 0.1.0.x:
13524 - Fix the other half of the bug with crypto handshakes
13526 - Fix an assert trigger if you send a 'signal term' via the
13527 controller when it's listening for 'event info' messages.
13530 Changes in version 0.1.1.4-alpha - 2005-08-04
13531 o Bugfixes included in 0.1.0.13.
13534 - Improve tor_gettimeofday() granularity on windows.
13535 - Make clients regenerate their keys when their IP address changes.
13536 - Implement some more GETINFO goodness: expose helper nodes, config
13537 options, getinfo keys.
13540 Changes in version 0.1.0.13 - 2005-08-04
13541 o Bugfixes on 0.1.0.x:
13542 - Fix a critical bug in the security of our crypto handshakes.
13543 - Fix a size_t underflow in smartlist_join_strings2() that made
13544 it do bad things when you hand it an empty smartlist.
13545 - Fix Windows installer to ship Tor license (thanks to Aphex for
13546 pointing out this oversight) and put a link to the doc directory
13548 - Explicitly set no-unaligned-access for sparc: it turns out the
13549 new gcc's let you compile broken code, but that doesn't make it
13553 Changes in version 0.1.1.3-alpha - 2005-07-23
13554 o Bugfixes on 0.1.1.2-alpha:
13555 - Fix a bug in handling the controller's "post descriptor"
13557 - Fix several bugs in handling the controller's "extend circuit"
13559 - Fix a bug in handling the controller's "stream status" event.
13560 - Fix an assert failure if we have a controller listening for
13561 circuit events and we go offline.
13562 - Re-allow hidden service descriptors to publish 0 intro points.
13563 - Fix a crash when generating your hidden service descriptor if
13564 you don't have enough intro points already.
13566 o New features on 0.1.1.2-alpha:
13567 - New controller function "getinfo accounting", to ask how
13568 many bytes we've used in this time period.
13569 - Experimental support for helper nodes: a lot of the risk from
13570 a small static adversary comes because users pick new random
13571 nodes every time they rebuild a circuit. Now users will try to
13572 stick to the same small set of entry nodes if they can. Not
13573 enabled by default yet.
13575 o Bugfixes on 0.1.0.12:
13576 - If you're an auth dir server, always publish your dirport,
13577 even if you haven't yet found yourself to be reachable.
13578 - Fix a size_t underflow in smartlist_join_strings2() that made
13579 it do bad things when you hand it an empty smartlist.
13582 Changes in version 0.1.0.12 - 2005-07-18
13583 o New directory servers:
13584 - tor26 has changed IP address.
13586 o Bugfixes on 0.1.0.x:
13587 - Fix a possible double-free in tor_gzip_uncompress().
13588 - When --disable-threads is set, do not search for or link against
13589 pthreads libraries.
13590 - Don't trigger an assert if an authoritative directory server
13591 claims its dirport is 0.
13592 - Fix bug with removing Tor as an NT service: some people were
13593 getting "The service did not return an error." Thanks to Matt
13597 Changes in version 0.1.1.2-alpha - 2005-07-15
13598 o New directory servers:
13599 - tor26 has changed IP address.
13601 o Bugfixes on 0.1.0.x, crashes/leaks:
13602 - Port the servers-not-obeying-their-exit-policies fix from
13604 - Fix an fd leak in start_daemon().
13605 - On Windows, you can't always reopen a port right after you've
13606 closed it. So change retry_listeners() to only close and re-open
13607 ports that have changed.
13608 - Fix a possible double-free in tor_gzip_uncompress().
13610 o Bugfixes on 0.1.0.x, usability:
13611 - When tor_socketpair() fails in Windows, give a reasonable
13612 Windows-style errno back.
13613 - Let people type "tor --install" as well as "tor -install" when
13615 want to make it an NT service.
13616 - NT service patch from Matt Edman to improve error messages.
13617 - When the controller asks for a config option with an abbreviated
13618 name, give the full name in our response.
13619 - Correct the man page entry on TrackHostExitsExpire.
13620 - Looks like we were never delivering deflated (i.e. compressed)
13621 running-routers lists, even when asked. Oops.
13622 - When --disable-threads is set, do not search for or link against
13623 pthreads libraries.
13625 o Bugfixes on 0.1.1.x:
13626 - Fix a seg fault with autodetecting which controller version is
13630 - New hidden service descriptor format: put a version in it, and
13631 let people specify introduction/rendezvous points that aren't
13632 in "the directory" (which is subjective anyway).
13633 - Allow the DEBUG controller event to work again. Mark certain log
13634 entries as "don't tell this to controllers", so we avoid cycles.
13637 Changes in version 0.1.0.11 - 2005-06-30
13638 o Bugfixes on 0.1.0.x:
13639 - Fix major security bug: servers were disregarding their
13640 exit policies if clients behaved unexpectedly.
13641 - Make OS X init script check for missing argument, so we don't
13642 confuse users who invoke it incorrectly.
13643 - Fix a seg fault in "tor --hash-password foo".
13644 - The MAPADDRESS control command was broken.
13647 Changes in version 0.1.1.1-alpha - 2005-06-29
13649 - Make OS X init script check for missing argument, so we don't
13650 confuse users who invoke it incorrectly.
13651 - Fix a seg fault in "tor --hash-password foo".
13652 - Fix a possible way to DoS dirservers.
13653 - When we complain that your exit policy implicitly allows local or
13654 private address spaces, name them explicitly so operators can
13656 - Make the log message less scary when all the dirservers are
13657 temporarily unreachable.
13658 - We were printing the number of idle dns workers incorrectly when
13662 - Revised controller protocol (version 1) that uses ascii rather
13663 than binary. Add supporting libraries in python and java so you
13664 can use the controller from your applications without caring how
13665 our protocol works.
13666 - Spiffy new support for crypto hardware accelerators. Can somebody
13670 Changes in version 0.0.9.10 - 2005-06-16
13671 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
13672 - Refuse relay cells that claim to have a length larger than the
13673 maximum allowed. This prevents a potential attack that could read
13674 arbitrary memory (e.g. keys) from an exit server's process
13678 Changes in version 0.1.0.10 - 2005-06-14
13679 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
13680 libevent before 1.1a.
13683 Changes in version 0.1.0.9-rc - 2005-06-09
13685 - Reset buf->highwater every time buf_shrink() is called, not just on
13686 a successful shrink. This was causing significant memory bloat.
13687 - Fix buffer overflow when checking hashed passwords.
13688 - Security fix: if seeding the RNG on Win32 fails, quit.
13689 - Allow seeding the RNG on Win32 even when you're not running as
13691 - Disable threading on Solaris too. Something is wonky with it,
13692 cpuworkers, and reentrant libs.
13693 - Reenable the part of the code that tries to flush as soon as an
13694 OR outbuf has a full TLS record available. Perhaps this will make
13695 OR outbufs not grow as huge except in rare cases, thus saving lots
13696 of CPU time plus memory.
13697 - Reject malformed .onion addresses rather then passing them on as
13698 normal web requests.
13699 - Adapt patch from Adam Langley: fix possible memory leak in
13700 tor_lookup_hostname().
13701 - Initialize libevent later in the startup process, so the logs are
13702 already established by the time we start logging libevent warns.
13703 - Use correct errno on win32 if libevent fails.
13704 - Check and warn about known-bad/slow libevent versions.
13705 - Pay more attention to the ClientOnly config option.
13706 - Have torctl.in/tor.sh.in check for location of su binary (needed
13708 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
13709 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
13710 HttpProxyAuthenticator
13711 - Stop warning about sigpipes in the logs. We're going to
13712 pretend that getting these occassionally is normal and fine.
13713 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
13715 installer screens; and don't put stuff into StartupItems unless
13716 the user asks you to.
13717 - Require servers that use the default dirservers to have public IP
13718 addresses. We have too many servers that are configured with private
13719 IPs and their admins never notice the log entries complaining that
13720 their descriptors are being rejected.
13721 - Add OSX uninstall instructions. An actual uninstall script will
13725 Changes in version 0.1.0.8-rc - 2005-05-23
13727 - It turns out that kqueue on OS X 10.3.9 was causing kernel
13728 panics. Disable kqueue on all OS X Tors.
13729 - Fix RPM: remove duplicate line accidentally added to the rpm
13731 - Disable threads on openbsd too, since its gethostaddr is not
13733 - Tolerate libevent 0.8 since it still works, even though it's
13735 - Enable building on Red Hat 9.0 again.
13736 - Allow the middle hop of the testing circuit to be running any
13737 version, now that most of them have the bugfix to let them connect
13738 to unknown servers. This will allow reachability testing to work
13739 even when 0.0.9.7-0.0.9.9 become obsolete.
13740 - Handle relay cells with rh.length too large. This prevents
13741 a potential attack that could read arbitrary memory (maybe even
13742 keys) from the exit server's process.
13743 - We screwed up the dirport reachability testing when we don't yet
13744 have a cached version of the directory. Hopefully now fixed.
13745 - Clean up router_load_single_router() (used by the controller),
13746 so it doesn't seg fault on error.
13747 - Fix a minor memory leak when somebody establishes an introduction
13748 point at your Tor server.
13749 - If a socks connection ends because read fails, don't warn that
13750 you're not sending a socks reply back.
13753 - Add HttpProxyAuthenticator config option too, that works like
13754 the HttpsProxyAuthenticator config option.
13755 - Encode hashed controller passwords in hex instead of base64,
13756 to make it easier to write controllers.
13759 Changes in version 0.1.0.7-rc - 2005-05-17
13761 - Fix a bug in the OS X package installer that prevented it from
13762 installing on Tiger.
13763 - Fix a script bug in the OS X package installer that made it
13764 complain during installation.
13765 - Find libevent even if it's hiding in /usr/local/ and your
13766 CFLAGS and LDFLAGS don't tell you to look there.
13767 - Be able to link with libevent as a shared library (the default
13768 after 1.0d), even if it's hiding in /usr/local/lib and even
13769 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
13770 assuming you're running gcc. Otherwise fail and give a useful
13772 - Fix a bug in the RPM packager: set home directory for _tor to
13773 something more reasonable when first installing.
13774 - Free a minor amount of memory that is still reachable on exit.
13777 Changes in version 0.1.0.6-rc - 2005-05-14
13779 - Implement --disable-threads configure option. Disable threads on
13780 netbsd by default, because it appears to have no reentrant resolver
13782 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
13783 release (1.1) detects and disables kqueue if it's broken.
13784 - Append default exit policy before checking for implicit internal
13785 addresses. Now we don't log a bunch of complaints on startup
13786 when using the default exit policy.
13787 - Some people were putting "Address " in their torrc, and they had
13788 a buggy resolver that resolved " " to 0.0.0.0. Oops.
13789 - If DataDir is ~/.tor, and that expands to /.tor, then default to
13790 LOCALSTATEDIR/tor instead.
13791 - Fix fragmented-message bug in TorControl.py.
13792 - Resolve a minor bug which would prevent unreachable dirports
13793 from getting suppressed in the published descriptor.
13794 - When the controller gave us a new descriptor, we weren't resolving
13795 it immediately, so Tor would think its address was 0.0.0.0 until
13796 we fetched a new directory.
13797 - Fix an uppercase/lowercase case error in suppressing a bogus
13798 libevent warning on some Linuxes.
13801 - Begin scrubbing sensitive strings from logs by default. Turn off
13802 the config option SafeLogging if you need to do debugging.
13803 - Switch to a new buffer management algorithm, which tries to avoid
13804 reallocing and copying quite as much. In first tests it looks like
13805 it uses *more* memory on average, but less cpu.
13806 - First cut at support for "create-fast" cells. Clients can use
13807 these when extending to their first hop, since the TLS already
13808 provides forward secrecy and authentication. Not enabled on
13810 - When dirservers refuse a router descriptor, we now log its
13811 contactinfo, platform, and the poster's IP address.
13812 - Call tor_free_all instead of connections_free_all after forking, to
13813 save memory on systems that need to fork.
13814 - Whine at you if you're a server and you don't set your contactinfo.
13815 - Implement --verify-config command-line option to check if your torrc
13816 is valid without actually launching Tor.
13817 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
13818 rather than just rejecting it.
13821 Changes in version 0.1.0.5-rc - 2005-04-27
13823 - Stop trying to print a null pointer if an OR conn fails because
13824 we didn't like its cert.
13826 - Switch our internal buffers implementation to use a ring buffer,
13827 to hopefully improve performance for fast servers a lot.
13828 - Add HttpsProxyAuthenticator support (basic auth only), based
13829 on patch from Adam Langley.
13830 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
13831 the fast servers that have been joining lately.
13832 - Give hidden service accesses extra time on the first attempt,
13833 since 60 seconds is often only barely enough. This might improve
13835 - Improve performance for dirservers: stop re-parsing the whole
13836 directory every time you regenerate it.
13837 - Add more debugging info to help us find the weird dns freebsd
13838 pthreads bug; cleaner debug messages to help track future issues.
13841 Changes in version 0.0.9.9 - 2005-04-23
13842 o Bugfixes on 0.0.9.x:
13843 - If unofficial Tor clients connect and send weird TLS certs, our
13844 Tor server triggers an assert. This release contains a minimal
13845 backport from the broader fix that we put into 0.1.0.4-rc.
13848 Changes in version 0.1.0.4-rc - 2005-04-23
13850 - If unofficial Tor clients connect and send weird TLS certs, our
13851 Tor server triggers an assert. Stop asserting, and start handling
13852 TLS errors better in other situations too.
13853 - When the controller asks us to tell it about all the debug-level
13854 logs, it turns out we were generating debug-level logs while
13855 telling it about them, which turns into a bad loop. Now keep
13856 track of whether you're sending a debug log to the controller,
13857 and don't log when you are.
13858 - Fix the "postdescriptor" feature of the controller interface: on
13859 non-complete success, only say "done" once.
13861 - Clients are now willing to load balance over up to 2mB, not 1mB,
13862 of advertised bandwidth capacity.
13863 - Add a NoPublish config option, so you can be a server (e.g. for
13864 testing running Tor servers in other Tor networks) without
13865 publishing your descriptor to the primary dirservers.
13868 Changes in version 0.1.0.3-rc - 2005-04-08
13869 o Improvements on 0.1.0.2-rc:
13870 - Client now retries when streams end early for 'hibernating' or
13871 'resource limit' reasons, rather than failing them.
13872 - More automated handling for dirserver operators:
13873 - Automatically approve nodes running 0.1.0.2-rc or later,
13874 now that the the reachability detection stuff is working.
13875 - Now we allow two unverified servers with the same nickname
13876 but different keys. But if a nickname is verified, only that
13877 nickname+key are allowed.
13878 - If you're an authdirserver connecting to an address:port,
13879 and it's not the OR you were expecting, forget about that
13880 descriptor. If he *was* the one you were expecting, then forget
13881 about all other descriptors for that address:port.
13882 - Allow servers to publish descriptors from 12 hours in the future.
13883 Corollary: only whine about clock skew from the dirserver if
13884 he's a trusted dirserver (since now even verified servers could
13885 have quite wrong clocks).
13886 - Adjust maximum skew and age for rendezvous descriptors: let skew
13887 be 48 hours rather than 90 minutes.
13888 - Efficiency improvements:
13889 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
13890 it much faster to look up a circuit for each relay cell.
13891 - Remove most calls to assert_all_pending_dns_resolves_ok(),
13892 since they're eating our cpu on exit nodes.
13893 - Stop wasting time doing a case insensitive comparison for every
13894 dns name every time we do any lookup. Canonicalize the names to
13895 lowercase and be done with it.
13896 - Start sending 'truncated' cells back rather than destroy cells,
13897 if the circuit closes in front of you. This means we won't have
13898 to abandon partially built circuits.
13899 - Only warn once per nickname from add_nickname_list_to_smartlist
13900 per failure, so an entrynode or exitnode choice that's down won't
13902 - Put a note in the torrc about abuse potential with the default
13904 - Revise control spec and implementation to allow all log messages to
13905 be sent to controller with their severities intact (suggested by
13906 Matt Edman). Update TorControl to handle new log event types.
13907 - Provide better explanation messages when controller's POSTDESCRIPTOR
13909 - Stop putting nodename in the Platform string in server descriptors.
13910 It doesn't actually help, and it is confusing/upsetting some people.
13912 o Bugfixes on 0.1.0.2-rc:
13913 - We were printing the host mask wrong in exit policies in server
13914 descriptors. This isn't a critical bug though, since we were still
13915 obeying the exit policy internally.
13916 - Fix Tor when compiled with libevent but without pthreads: move
13917 connection_unregister() from _connection_free() to
13919 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
13920 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
13921 when we look through the connection array, we'll find any of the
13922 cpu/dnsworkers. This is no good.
13924 o Bugfixes on 0.0.9.8:
13925 - Fix possible bug on threading platforms (e.g. win32) which was
13926 leaking a file descriptor whenever a cpuworker or dnsworker died.
13927 - When using preferred entry or exit nodes, ignore whether the
13928 circuit wants uptime or capacity. They asked for the nodes, they
13930 - chdir() to your datadirectory at the *end* of the daemonize process,
13931 not the beginning. This was a problem because the first time you
13932 run tor, if your datadir isn't there, and you have runasdaemon set
13933 to 1, it will try to chdir to it before it tries to create it. Oops.
13934 - Handle changed router status correctly when dirserver reloads
13935 fingerprint file. We used to be dropping all unverified descriptors
13936 right then. The bug was hidden because we would immediately
13937 fetch a directory from another dirserver, which would include the
13938 descriptors we just dropped.
13939 - When we're connecting to an OR and he's got a different nickname/key
13940 than we were expecting, only complain loudly if we're an OP or a
13941 dirserver. Complaining loudly to the OR admins just confuses them.
13942 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
13943 artificially capped at 500kB.
13946 Changes in version 0.0.9.8 - 2005-04-07
13947 o Bugfixes on 0.0.9.x:
13948 - We have a bug that I haven't found yet. Sometimes, very rarely,
13949 cpuworkers get stuck in the 'busy' state, even though the cpuworker
13950 thinks of itself as idle. This meant that no new circuits ever got
13951 established. Here's a workaround to kill any cpuworker that's been
13952 busy for more than 100 seconds.
13955 Changes in version 0.1.0.2-rc - 2005-04-01
13956 o Bugfixes on 0.1.0.1-rc:
13957 - Fixes on reachability detection:
13958 - Don't check for reachability while hibernating.
13959 - If ORPort is reachable but DirPort isn't, still publish the
13960 descriptor, but zero out DirPort until it's found reachable.
13961 - When building testing circs for ORPort testing, use only
13962 high-bandwidth nodes, so fewer circuits fail.
13963 - Complain about unreachable ORPort separately from unreachable
13964 DirPort, so the user knows what's going on.
13965 - Make sure we only conclude ORPort reachability if we didn't
13966 initiate the conn. Otherwise we could falsely conclude that
13967 we're reachable just because we connected to the guy earlier
13968 and he used that same pipe to extend to us.
13969 - Authdirservers shouldn't do ORPort reachability detection,
13970 since they're in clique mode, so it will be rare to find a
13971 server not already connected to them.
13972 - When building testing circuits, always pick middle hops running
13973 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
13974 bug. (This is a kludge; it will go away when 0.0.9.x becomes
13976 - When we decide we're reachable, actually publish our descriptor
13978 - Fix bug in redirectstream in the controller.
13979 - Fix the state descriptor strings so logs don't claim edge streams
13980 are in a different state than they actually are.
13981 - Use recent libevent features when possible (this only really affects
13982 win32 and osx right now, because the new libevent with these
13983 features hasn't been released yet). Add code to suppress spurious
13985 - Prevent possible segfault in connection_close_unattached_ap().
13986 - Fix newlines on torrc in win32.
13987 - Improve error msgs when tor-resolve fails.
13989 o Improvements on 0.0.9.x:
13990 - New experimental script tor/contrib/ExerciseServer.py (needs more
13991 work) that uses the controller interface to build circuits and
13992 fetch pages over them. This will help us bootstrap servers that
13993 have lots of capacity but haven't noticed it yet.
13994 - New experimental script tor/contrib/PathDemo.py (needs more work)
13995 that uses the controller interface to let you choose whole paths
13997 "<hostname>.<path,separated by dots>.<length of path>.path"
13998 - When we've connected to an OR and handshaked but didn't like
13999 the result, we were closing the conn without sending destroy
14000 cells back for pending circuits. Now send those destroys.
14003 Changes in version 0.0.9.7 - 2005-04-01
14004 o Bugfixes on 0.0.9.x:
14005 - Fix another race crash bug (thanks to Glenn Fink for reporting).
14006 - Compare identity to identity, not to nickname, when extending to
14007 a router not already in the directory. This was preventing us from
14008 extending to unknown routers. Oops.
14009 - Make sure to create OS X Tor user in <500 range, so we aren't
14010 creating actual system users.
14011 - Note where connection-that-hasn't-sent-end was marked, and fix
14012 a few really loud instances of this harmless bug (it's fixed more
14016 Changes in version 0.1.0.1-rc - 2005-03-28
14018 - Add reachability testing. Your Tor server will automatically try
14019 to see if its ORPort and DirPort are reachable from the outside,
14020 and it won't upload its descriptor until it decides they are.
14021 - Handle unavailable hidden services better. Handle slow or busy
14022 hidden services better.
14023 - Add support for CONNECTing through https proxies, with "HttpsProxy"
14025 - New exit policy: accept most low-numbered ports, rather than
14026 rejecting most low-numbered ports.
14027 - More Tor controller support (still experimental). See
14028 http://tor.eff.org/doc/control-spec.txt for all the new features,
14029 including signals to emulate unix signals from any platform;
14030 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
14031 closestream; closecircuit; etc.
14032 - Make nt services work and start on startup on win32 (based on
14033 patch by Matt Edman).
14034 - Add a new AddressMap config directive to rewrite incoming socks
14035 addresses. This lets you, for example, declare an implicit
14036 required exit node for certain sites.
14037 - Add a new TrackHostExits config directive to trigger addressmaps
14038 for certain incoming socks addresses -- for sites that break when
14039 your exit keeps changing (based on patch by Mike Perry).
14040 - Redo the client-side dns cache so it's just an addressmap too.
14041 - Notice when our IP changes, and reset stats/uptime/reachability.
14042 - When an application is using socks5, give him the whole variety of
14043 potential socks5 responses (connect refused, host unreachable, etc),
14044 rather than just "success" or "failure".
14045 - A more sane version numbering system. See
14046 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
14047 - New contributed script "exitlist": a simple python script to
14048 parse directories and find Tor nodes that exit to listed
14050 - New contributed script "privoxy-tor-toggle" to toggle whether
14051 Privoxy uses Tor. Seems to be configured for Debian by default.
14052 - Report HTTP reasons to client when getting a response from directory
14053 servers -- so you can actually know what went wrong.
14054 - New config option MaxAdvertisedBandwidth which lets you advertise
14055 a low bandwidthrate (to not attract as many circuits) while still
14056 allowing a higher bandwidthrate in reality.
14058 o Robustness/stability fixes:
14059 - Make Tor use Niels Provos's libevent instead of its current
14060 poll-but-sometimes-select mess. This will let us use faster async
14061 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
14063 - pthread support now too. This was forced because when we forked,
14064 we ended up wasting a lot of duplicate ram over time. Also switch
14065 to foo_r versions of some library calls to allow reentry and
14067 - Better handling for heterogeneous / unreliable nodes:
14068 - Annotate circuits w/ whether they aim to contain high uptime nodes
14069 and/or high capacity nodes. When building circuits, choose
14071 - This means that every single node in an intro rend circuit,
14072 not just the last one, will have a minimum uptime.
14073 - New config option LongLivedPorts to indicate application streams
14074 that will want high uptime circuits.
14075 - Servers reset uptime when a dir fetch entirely fails. This
14076 hopefully reflects stability of the server's network connectivity.
14077 - If somebody starts his tor server in Jan 2004 and then fixes his
14078 clock, don't make his published uptime be a year.
14079 - Reset published uptime when you wake up from hibernation.
14080 - Introduce a notion of 'internal' circs, which are chosen without
14081 regard to the exit policy of the last hop. Intro and rendezvous
14082 circs must be internal circs, to avoid leaking information. Resolve
14083 and connect streams can use internal circs if they want.
14084 - New circuit pooling algorithm: make sure to have enough circs around
14085 to satisfy any predicted ports, and also make sure to have 2 internal
14086 circs around if we've required internal circs lately (and with high
14087 uptime if we've seen that lately too).
14088 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
14089 which describes how often we retry making new circuits if current
14090 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
14091 how long we're willing to make use of an already-dirty circuit.
14092 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
14093 circ as necessary, if there are any completed ones lying around
14094 when we try to launch one.
14095 - Make hidden services try to establish a rendezvous for 30 seconds,
14096 rather than for n (where n=3) attempts to build a circuit.
14097 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
14098 "ShutdownWaitLength".
14099 - Try to be more zealous about calling connection_edge_end when
14100 things go bad with edge conns in connection.c.
14101 - Revise tor-spec to add more/better stream end reasons.
14102 - Revise all calls to connection_edge_end to avoid sending "misc",
14103 and to take errno into account where possible.
14106 - Fix a race condition that can trigger an assert, when we have a
14107 pending create cell and an OR connection fails right then.
14108 - Fix several double-mark-for-close bugs, e.g. where we were finding
14109 a conn for a cell even if that conn is already marked for close.
14110 - Make sequence of log messages when starting on win32 with no config
14111 file more reasonable.
14112 - When choosing an exit node for a new non-internal circ, don't take
14113 into account whether it'll be useful for any pending x.onion
14114 addresses -- it won't.
14115 - Turn addr_policy_compare from a tristate to a quadstate; this should
14116 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
14117 for google.com" problem.
14118 - Make "platform" string in descriptor more accurate for Win32 servers,
14119 so it's not just "unknown platform".
14120 - Fix an edge case in parsing config options (thanks weasel).
14121 If they say "--" on the commandline, it's not an option.
14122 - Reject odd-looking addresses at the client (e.g. addresses that
14123 contain a colon), rather than having the server drop them because
14125 - tor-resolve requests were ignoring .exit if there was a working circuit
14126 they could use instead.
14127 - REUSEADDR on normal platforms means you can rebind to the port
14128 right after somebody else has let it go. But REUSEADDR on win32
14129 means to let you bind to the port _even when somebody else
14130 already has it bound_! So, don't do that on Win32.
14131 - Change version parsing logic: a version is "obsolete" if it is not
14132 recommended and (1) there is a newer recommended version in the
14133 same series, or (2) there are no recommended versions in the same
14134 series, but there are some recommended versions in a newer series.
14135 A version is "new" if it is newer than any recommended version in
14137 - Stop most cases of hanging up on a socks connection without sending
14141 - Require BandwidthRate to be at least 20kB/s for servers.
14142 - When a dirserver causes you to give a warn, mention which dirserver
14144 - New config option DirAllowPrivateAddresses for authdirservers.
14145 Now by default they refuse router descriptors that have non-IP or
14146 private-IP addresses.
14147 - Stop publishing socksport in the directory, since it's not
14148 actually meant to be public. For compatibility, publish a 0 there
14150 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
14151 smart" value, that is low for servers and high for clients.
14152 - If our clock jumps forward by 100 seconds or more, assume something
14153 has gone wrong with our network and abandon all not-yet-used circs.
14154 - Warn when exit policy implicitly allows local addresses.
14155 - If we get an incredibly skewed timestamp from a dirserver mirror
14156 that isn't a verified OR, don't warn -- it's probably him that's
14158 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
14159 cookies to disk and doesn't log each web request to disk. (Thanks
14160 to Brett Carrington for pointing this out.)
14161 - When a client asks us for a dir mirror and we don't have one,
14162 launch an attempt to get a fresh one.
14163 - If we're hibernating and we get a SIGINT, exit immediately.
14164 - Add --with-dmalloc ./configure option, to track memory leaks.
14165 - And try to free all memory on closing, so we can detect what
14167 - Cache local dns resolves correctly even when they're .exit
14169 - Give a better warning when some other server advertises an
14170 ORPort that is actually an apache running ssl.
14171 - Add "opt hibernating 1" to server descriptor to make it clearer
14172 whether the server is hibernating.
14175 Changes in version 0.0.9.6 - 2005-03-24
14176 o Bugfixes on 0.0.9.x (crashes and asserts):
14177 - Add new end stream reasons to maintainance branch. Fix bug where
14178 reason (8) could trigger an assert. Prevent bug from recurring.
14179 - Apparently win32 stat wants paths to not end with a slash.
14180 - Fix assert triggers in assert_cpath_layer_ok(), where we were
14181 blowing away the circuit that conn->cpath_layer points to, then
14182 checking to see if the circ is well-formed. Backport check to make
14183 sure we dont use the cpath on a closed connection.
14184 - Prevent circuit_resume_edge_reading_helper() from trying to package
14185 inbufs for marked-for-close streams.
14186 - Don't crash on hup if your options->address has become unresolvable.
14187 - Some systems (like OS X) sometimes accept() a connection and tell
14188 you the remote host is 0.0.0.0:0. If this happens, due to some
14189 other mis-features, we get confused; so refuse the conn for now.
14191 o Bugfixes on 0.0.9.x (other):
14192 - Fix harmless but scary "Unrecognized content encoding" warn message.
14193 - Add new stream error reason: TORPROTOCOL reason means "you are not
14194 speaking a version of Tor I understand; say bye-bye to your stream."
14195 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
14196 into the future, now that we are more tolerant of skew. This
14197 resolves a bug where a Tor server would refuse to cache a directory
14198 because all the directories it gets are too far in the future;
14199 yet the Tor server never logs any complaints about clock skew.
14200 - Mac packaging magic: make man pages useable, and do not overwrite
14201 existing torrc files.
14202 - Make OS X log happily to /var/log/tor/tor.log
14205 Changes in version 0.0.9.5 - 2005-02-22
14206 o Bugfixes on 0.0.9.x:
14207 - Fix an assert race at exit nodes when resolve requests fail.
14208 - Stop picking unverified dir mirrors--it only leads to misery.
14209 - Patch from Matt Edman to make NT services work better. Service
14210 support is still not compiled into the executable by default.
14211 - Patch from Dmitri Bely so the Tor service runs better under
14212 the win32 SYSTEM account.
14213 - Make tor-resolve actually work (?) on Win32.
14214 - Fix a sign bug when getrlimit claims to have 4+ billion
14215 file descriptors available.
14216 - Stop refusing to start when bandwidthburst == bandwidthrate.
14217 - When create cells have been on the onion queue more than five
14218 seconds, just send back a destroy and take them off the list.
14221 Changes in version 0.0.9.4 - 2005-02-03
14222 o Bugfixes on 0.0.9:
14223 - Fix an assert bug that took down most of our servers: when
14224 a server claims to have 1 GB of bandwidthburst, don't
14226 - Don't crash as badly if we have spawned the max allowed number
14227 of dnsworkers, or we're out of file descriptors.
14228 - Block more file-sharing ports in the default exit policy.
14229 - MaxConn is now automatically set to the hard limit of max
14230 file descriptors we're allowed (ulimit -n), minus a few for
14232 - Give a clearer message when servers need to raise their
14233 ulimit -n when they start running out of file descriptors.
14234 - SGI Compatibility patches from Jan Schaumann.
14235 - Tolerate a corrupt cached directory better.
14236 - When a dirserver hasn't approved your server, list which one.
14237 - Go into soft hibernation after 95% of the bandwidth is used,
14238 not 99%. This is especially important for daily hibernators who
14239 have a small accounting max. Hopefully it will result in fewer
14240 cut connections when the hard hibernation starts.
14241 - Load-balance better when using servers that claim more than
14242 800kB/s of capacity.
14243 - Make NT services work (experimental, only used if compiled in).
14246 Changes in version 0.0.9.3 - 2005-01-21
14247 o Bugfixes on 0.0.9:
14248 - Backport the cpu use fixes from main branch, so busy servers won't
14249 need as much processor time.
14250 - Work better when we go offline and then come back, or when we
14251 run Tor at boot before the network is up. We do this by
14252 optimistically trying to fetch a new directory whenever an
14253 application request comes in and we think we're offline -- the
14254 human is hopefully a good measure of when the network is back.
14255 - Backport some minimal hidserv bugfixes: keep rend circuits open as
14256 long as you keep using them; actually publish hidserv descriptors
14257 shortly after they change, rather than waiting 20-40 minutes.
14258 - Enable Mac startup script by default.
14259 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
14260 - When you update AllowUnverifiedNodes or FirewallPorts via the
14261 controller's setconf feature, we were always appending, never
14263 - When you update HiddenServiceDir via setconf, it was screwing up
14264 the order of reading the lines, making it fail.
14265 - Do not rewrite a cached directory back to the cache; otherwise we
14266 will think it is recent and not fetch a newer one on startup.
14267 - Workaround for webservers that lie about Content-Encoding: Tor
14268 now tries to autodetect compressed directories and compression
14269 itself. This lets us Proxypass dir fetches through apache.
14272 Changes in version 0.0.9.2 - 2005-01-04
14273 o Bugfixes on 0.0.9 (crashes and asserts):
14274 - Fix an assert on startup when the disk is full and you're logging
14276 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
14277 style address, then we'd crash.
14278 - Fix an assert trigger when the running-routers string we get from
14279 a dirserver is broken.
14280 - Make worker threads start and run on win32. Now win32 servers
14282 - Bandaid (not actually fix, but now it doesn't crash) an assert
14283 where the dns worker dies mysteriously and the main Tor process
14284 doesn't remember anything about the address it was resolving.
14286 o Bugfixes on 0.0.9 (Win32):
14287 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
14288 name out of the warning/assert messages.
14289 - Fix a superficial "unhandled error on read" bug on win32.
14290 - The win32 installer no longer requires a click-through for our
14291 license, since our Free Software license grants rights but does not
14293 - Win32: When connecting to a dirserver fails, try another one
14294 immediately. (This was already working for non-win32 Tors.)
14295 - Stop trying to parse $HOME on win32 when hunting for default
14297 - Make tor-resolve.c work on win32 by calling network_init().
14299 o Bugfixes on 0.0.9 (other):
14300 - Make 0.0.9.x build on Solaris again.
14301 - Due to a fencepost error, we were blowing away the \n when reporting
14302 confvalue items in the controller. So asking for multiple config
14303 values at once couldn't work.
14304 - When listing circuits that are pending on an opening OR connection,
14305 if we're an OR we were listing circuits that *end* at us as
14306 being pending on every listener, dns/cpu worker, etc. Stop that.
14307 - Dirservers were failing to create 'running-routers' or 'directory'
14308 strings if we had more than some threshold of routers. Fix them so
14309 they can handle any number of routers.
14310 - Fix a superficial "Duplicate mark for close" bug.
14311 - Stop checking for clock skew for OR connections, even for servers.
14312 - Fix a fencepost error that was chopping off the last letter of any
14313 nickname that is the maximum allowed nickname length.
14314 - Update URLs in log messages so they point to the new website.
14315 - Fix a potential problem in mangling server private keys while
14316 writing to disk (not triggered yet, as far as we know).
14317 - Include the licenses for other free software we include in Tor,
14318 now that we're shipping binary distributions more regularly.
14321 Changes in version 0.0.9.1 - 2004-12-15
14322 o Bugfixes on 0.0.9:
14323 - Make hibernation actually work.
14324 - Make HashedControlPassword config option work.
14325 - When we're reporting event circuit status to a controller,
14326 don't use the stream status code.
14329 Changes in version 0.0.9 - 2004-12-12
14331 - Clean up manpage and torrc.sample file.
14332 - Clean up severities and text of log warnings.
14334 - Make servers trigger an assert when they enter hibernation.
14337 Changes in version 0.0.9rc7 - 2004-12-08
14338 o Bugfixes on 0.0.9rc:
14339 - Fix a stack-trashing crash when an exit node begins hibernating.
14340 - Avoid looking at unallocated memory while considering which
14341 ports we need to build circuits to cover.
14342 - Stop a sigpipe: when an 'end' cell races with eof from the app,
14343 we shouldn't hold-open-until-flush if the eof arrived first.
14344 - Fix a bug with init_cookie_authentication() in the controller.
14345 - When recommending new-format log lines, if the upper bound is
14346 LOG_ERR, leave it implicit.
14348 o Bugfixes on 0.0.8.1:
14349 - Fix a whole slew of memory leaks.
14350 - Fix isspace() and friends so they still make Solaris happy
14351 but also so they don't trigger asserts on win32.
14352 - Fix parse_iso_time on platforms without strptime (eg win32).
14353 - win32: tolerate extra "readable" events better.
14354 - win32: when being multithreaded, leave parent fdarray open.
14355 - Make unit tests work on win32.
14358 Changes in version 0.0.9rc6 - 2004-12-06
14359 o Bugfixes on 0.0.9pre:
14360 - Clean up some more integer underflow opportunities (not exploitable
14362 - While hibernating, hup should not regrow our listeners.
14363 - Send an end to the streams we close when we hibernate, rather
14364 than just chopping them off.
14365 - React to eof immediately on non-open edge connections.
14367 o Bugfixes on 0.0.8.1:
14368 - Calculate timeout for waiting for a connected cell from the time
14369 we sent the begin cell, not from the time the stream started. If
14370 it took a long time to establish the circuit, we would time out
14371 right after sending the begin cell.
14372 - Fix router_compare_addr_to_addr_policy: it was not treating a port
14373 of * as always matching, so we were picking reject *:* nodes as
14374 exit nodes too. Oops.
14377 - New circuit building strategy: keep a list of ports that we've
14378 used in the past 6 hours, and always try to have 2 circuits open
14379 or on the way that will handle each such port. Seed us with port
14380 80 so web users won't complain that Tor is "slow to start up".
14381 - Make kill -USR1 dump more useful stats about circuits.
14382 - When warning about retrying or giving up, print the address, so
14383 the user knows which one it's talking about.
14384 - If you haven't used a clean circuit in an hour, throw it away,
14385 just to be on the safe side. (This means after 6 hours a totally
14386 unused Tor client will have no circuits open.)
14389 Changes in version 0.0.9rc5 - 2004-12-01
14390 o Bugfixes on 0.0.8.1:
14391 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
14392 - Let resolve conns retry/expire also, rather than sticking around
14394 - If we are using select, make sure we stay within FD_SETSIZE.
14396 o Bugfixes on 0.0.9pre:
14397 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
14398 but doesn't seem to be currently; thanks to Ilja van Sprundel for
14400 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
14401 instead. Impose minima and maxima for all *Period options; impose
14402 even tighter maxima for fetching if we are a caching dirserver.
14403 Clip rather than rejecting.
14404 - Fetch cached running-routers from servers that serve it (that is,
14405 authdirservers and servers running 0.0.9rc5-cvs or later.)
14408 - Accept *:706 (silc) in default exit policy.
14409 - Implement new versioning format for post 0.1.
14410 - Support "foo.nickname.exit" addresses, to let Alice request the
14411 address "foo" as viewed by exit node "nickname". Based on a patch
14413 - Make tor --version --version dump the cvs Id of every file.
14416 Changes in version 0.0.9rc4 - 2004-11-28
14417 o Bugfixes on 0.0.8.1:
14418 - Make windows sockets actually non-blocking (oops), and handle
14419 win32 socket errors better.
14421 o Bugfixes on 0.0.9rc1:
14422 - Actually catch the -USR2 signal.
14425 Changes in version 0.0.9rc3 - 2004-11-25
14426 o Bugfixes on 0.0.8.1:
14427 - Flush the log file descriptor after we print "Tor opening log file",
14428 so we don't see those messages days later.
14430 o Bugfixes on 0.0.9rc1:
14431 - Make tor-resolve work again.
14432 - Avoid infinite loop in tor-resolve if tor hangs up on it.
14433 - Fix an assert trigger for clients/servers handling resolves.
14436 Changes in version 0.0.9rc2 - 2004-11-24
14437 o Bugfixes on 0.0.9rc1:
14438 - I broke socks5 support while fixing the eof bug.
14439 - Allow unitless bandwidths and intervals; they default to bytes
14441 - New servers don't start out hibernating; they are active until
14442 they run out of bytes, so they have a better estimate of how
14443 long it takes, and so their operators can know they're working.
14446 Changes in version 0.0.9rc1 - 2004-11-23
14447 o Bugfixes on 0.0.8.1:
14448 - Finally fix a bug that's been plaguing us for a year:
14449 With high load, circuit package window was reaching 0. Whenever
14450 we got a circuit-level sendme, we were reading a lot on each
14451 socket, but only writing out a bit. So we would eventually reach
14452 eof. This would be noticed and acted on even when there were still
14453 bytes sitting in the inbuf.
14454 - When poll() is interrupted, we shouldn't believe the revents values.
14456 o Bugfixes on 0.0.9pre6:
14457 - Fix hibernate bug that caused pre6 to be broken.
14458 - Don't keep rephist info for routers that haven't had activity for
14459 24 hours. (This matters now that clients have keys, since we track
14461 - Never call close_temp_logs while validating log options.
14462 - Fix backslash-escaping on tor.sh.in and torctl.in.
14465 - Implement weekly/monthly/daily accounting: now you specify your
14466 hibernation properties by
14467 AccountingMax N bytes|KB|MB|GB|TB
14468 AccountingStart day|week|month [day] HH:MM
14469 Defaults to "month 1 0:00".
14470 - Let bandwidth and interval config options be specified as 5 bytes,
14471 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
14472 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
14473 get back to normal.)
14474 - If your requested entry or exit node has advertised bandwidth 0,
14476 - Be more greedy about filling up relay cells -- we try reading again
14477 once we've processed the stuff we read, in case enough has arrived
14478 to fill the last cell completely.
14479 - Apply NT service patch from Osamu Fujino. Still needs more work.
14482 Changes in version 0.0.9pre6 - 2004-11-15
14483 o Bugfixes on 0.0.8.1:
14484 - Fix assert failure on malformed socks4a requests.
14485 - Use identity comparison, not nickname comparison, to choose which
14486 half of circuit-ID-space each side gets to use. This is needed
14487 because sometimes we think of a router as a nickname, and sometimes
14488 as a hex ID, and we can't predict what the other side will do.
14489 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
14490 write() call will fail and we handle it there.
14491 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
14492 and smartlist_len, which are two major profiling offenders.
14494 o Bugfixes on 0.0.9pre5:
14495 - Fix a bug in read_all that was corrupting config files on windows.
14496 - When we're raising the max number of open file descriptors to
14497 'unlimited', don't log that we just raised it to '-1'.
14498 - Include event code with events, as required by control-spec.txt.
14499 - Don't give a fingerprint when clients do --list-fingerprint:
14500 it's misleading, because it will never be the same again.
14501 - Stop using strlcpy in tor_strndup, since it was slowing us
14503 - Remove warn on startup about missing cached-directory file.
14504 - Make kill -USR1 work again.
14505 - Hibernate if we start tor during the "wait for wakeup-time" phase
14506 of an accounting interval. Log our hibernation plans better.
14507 - Authoritative dirservers now also cache their directory, so they
14508 have it on start-up.
14511 - Fetch running-routers; cache running-routers; compress
14512 running-routers; serve compressed running-routers.z
14513 - Add NSI installer script contributed by J Doe.
14514 - Commit VC6 and VC7 workspace/project files.
14515 - Commit a tor.spec for making RPM files, with help from jbash.
14516 - Add contrib/torctl.in contributed by Glenn Fink.
14517 - Implement the control-spec's SAVECONF command, to write your
14518 configuration to torrc.
14519 - Get cookie authentication for the controller closer to working.
14520 - Include control-spec.txt in the tarball.
14521 - When set_conf changes our server descriptor, upload a new copy.
14522 But don't upload it too often if there are frequent changes.
14523 - Document authentication config in man page, and document signals
14525 - Clean up confusing parts of man page and torrc.sample.
14526 - Make expand_filename handle ~ and ~username.
14527 - Use autoconf to enable largefile support where necessary. Use
14528 ftello where available, since ftell can fail at 2GB.
14529 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
14530 log more informatively.
14531 - Give a slightly more useful output for "tor -h".
14532 - Refuse application socks connections to port 0.
14533 - Check clock skew for verified servers, but allow unverified
14534 servers and clients to have any clock skew.
14535 - Break DirFetchPostPeriod into:
14536 - DirFetchPeriod for fetching full directory,
14537 - StatusFetchPeriod for fetching running-routers,
14538 - DirPostPeriod for posting server descriptor,
14539 - RendPostPeriod for posting hidden service descriptors.
14540 - Make sure the hidden service descriptors are at a random offset
14541 from each other, to hinder linkability.
14544 Changes in version 0.0.9pre5 - 2004-11-09
14545 o Bugfixes on 0.0.9pre4:
14546 - Fix a seg fault in unit tests (doesn't affect main program).
14547 - Fix an assert bug where a hidden service provider would fail if
14548 the first hop of his rendezvous circuit was down.
14549 - Hidden service operators now correctly handle version 1 style
14550 INTRODUCE1 cells (nobody generates them still, so not a critical
14552 - If do_hup fails, actually notice.
14553 - Handle more errnos from accept() without closing the listener.
14554 Some OpenBSD machines were closing their listeners because
14555 they ran out of file descriptors.
14556 - Send resolve cells to exit routers that are running a new
14557 enough version of the resolve code to work right.
14558 - Better handling of winsock includes on non-MSV win32 compilers.
14559 - Some people had wrapped their tor client/server in a script
14560 that would restart it whenever it died. This did not play well
14561 with our "shut down if your version is obsolete" code. Now people
14562 don't fetch a new directory if their local cached version is
14564 - Make our autogen.sh work on ksh as well as bash.
14567 - Hibernation: New config option "AccountingMaxKB" lets you
14568 set how many KBytes per month you want to allow your server to
14569 consume. Rather than spreading those bytes out evenly over the
14570 month, we instead hibernate for some of the month and pop up
14571 at a deterministic time, work until the bytes are consumed, then
14572 hibernate again. Config option "MonthlyAccountingStart" lets you
14573 specify which day of the month your billing cycle starts on.
14574 - Control interface: a separate program can now talk to your
14575 client/server over a socket, and get/set config options, receive
14576 notifications of circuits and streams starting/finishing/dying,
14577 bandwidth used, etc. The next step is to get some GUIs working.
14578 Let us know if you want to help out. See doc/control-spec.txt .
14579 - Ship a contrib/tor-control.py as an example script to interact
14580 with the control port.
14581 - "tor --hash-password zzyxz" will output a salted password for
14582 use in authenticating to the control interface.
14583 - New log format in config:
14584 "Log minsev[-maxsev] stdout|stderr|syslog" or
14585 "Log minsev[-maxsev] file /var/foo"
14588 - DirPolicy config option, to let people reject incoming addresses
14589 from their dirserver.
14590 - "tor --list-fingerprint" will list your identity key fingerprint
14592 - Add "pass" target for RedirectExit, to make it easier to break
14593 out of a sequence of RedirectExit rules.
14594 - Clients now generate a TLS cert too, in preparation for having
14595 them act more like real nodes.
14596 - Ship src/win32/ in the tarball, so people can use it to build.
14597 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
14599 - New "router-status" line in directory, to better bind each verified
14600 nickname to its identity key.
14601 - Deprecate unofficial config option abbreviations, and abbreviations
14602 not on the command line.
14603 - Add a pure-C tor-resolve implementation.
14604 - Use getrlimit and friends to ensure we can reach MaxConn (currently
14605 1024) file descriptors.
14607 o Code security improvements, inspired by Ilja:
14608 - Replace sprintf with snprintf. (I think they were all safe, but
14610 - Replace strcpy/strncpy with strlcpy in more places.
14611 - Avoid strcat; use snprintf or strlcat instead.
14612 - snprintf wrapper with consistent (though not C99) overflow behavior.
14615 Changes in version 0.0.9pre4 - 2004-10-17
14616 o Bugfixes on 0.0.9pre3:
14617 - If the server doesn't specify an exit policy, use the real default
14618 exit policy, not reject *:*.
14619 - Ignore fascistfirewall when uploading/downloading hidden service
14620 descriptors, since we go through Tor for those; and when using
14621 an HttpProxy, since we assume it can reach them all.
14622 - When looking for an authoritative dirserver, use only the ones
14623 configured at boot. Don't bother looking in the directory.
14624 - The rest of the fix for get_default_conf_file() on older win32.
14625 - Make 'Routerfile' config option obsolete.
14628 - New 'MyFamily nick1,...' config option for a server to
14629 specify other servers that shouldn't be used in the same circuit
14630 with it. Only believed if nick1 also specifies us.
14631 - New 'NodeFamily nick1,nick2,...' config option for a client to
14632 specify nodes that it doesn't want to use in the same circuit.
14633 - New 'Redirectexit pattern address:port' config option for a
14634 server to redirect exit connections, e.g. to a local squid.
14637 Changes in version 0.0.9pre3 - 2004-10-13
14638 o Bugfixes on 0.0.8.1:
14639 - Better torrc example lines for dirbindaddress and orbindaddress.
14640 - Improved bounds checking on parsed ints (e.g. config options and
14641 the ones we find in directories.)
14642 - Better handling of size_t vs int, so we're more robust on 64
14644 - Fix the rest of the bug where a newly started OR would appear
14645 as unverified even after we've added his fingerprint and hupped
14647 - Fix a bug from 0.0.7: when read() failed on a stream, we would
14648 close it without sending back an end. So 'connection refused'
14649 would simply be ignored and the user would get no response.
14651 o Bugfixes on 0.0.9pre2:
14652 - Serving the cached-on-disk directory to people is bad. We now
14653 provide no directory until we've fetched a fresh one.
14654 - Workaround for bug on windows where cached-directories get crlf
14656 - Make get_default_conf_file() work on older windows too.
14657 - If we write a *:* exit policy line in the descriptor, don't write
14658 any more exit policy lines.
14661 - Use only 0.0.9pre1 and later servers for resolve cells.
14662 - Make the dirservers file obsolete.
14663 - Include a dir-signing-key token in directories to tell the
14664 parsing entity which key is being used to sign.
14665 - Remove the built-in bulky default dirservers string.
14666 - New config option "Dirserver %s:%d [fingerprint]", which can be
14667 repeated as many times as needed. If no dirservers specified,
14668 default to moria1,moria2,tor26.
14669 - Make moria2 advertise a dirport of 80, so people behind firewalls
14670 will be able to get a directory.
14671 - Http proxy support
14672 - Dirservers translate requests for http://%s:%d/x to /x
14673 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
14674 be routed through this host.
14675 - Clients ask for /tor/x rather than /x for new enough dirservers.
14676 This way we can one day coexist peacefully with apache.
14677 - Clients specify a "Host: %s%d" http header, to be compatible
14678 with more proxies, and so running squid on an exit node can work.
14681 Changes in version 0.0.8.1 - 2004-10-13
14683 - Fix a seg fault that can be triggered remotely for Tor
14684 clients/servers with an open dirport.
14685 - Fix a rare assert trigger, where routerinfos for entries in
14686 our cpath would expire while we're building the path.
14687 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14688 - Fix a rare seg fault for people running hidden services on
14689 intermittent connections.
14690 - Fix a bug in parsing opt keywords with objects.
14691 - Fix a stale pointer assert bug when a stream detaches and
14693 - Fix a string format vulnerability (probably not exploitable)
14694 in reporting stats locally.
14695 - Fix an assert trigger: sometimes launching circuits can fail
14696 immediately, e.g. because too many circuits have failed recently.
14697 - Fix a compile warning on 64 bit platforms.
14700 Changes in version 0.0.9pre2 - 2004-10-03
14702 - Make fetching a cached directory work for 64-bit platforms too.
14703 - Make zlib.h a required header, not an optional header.
14706 Changes in version 0.0.9pre1 - 2004-10-01
14708 - Stop using separate defaults for no-config-file and
14709 empty-config-file. Now you have to explicitly turn off SocksPort,
14710 if you don't want it open.
14711 - Fix a bug in OutboundBindAddress so it (hopefully) works.
14712 - Improve man page to mention more of the 0.0.8 features.
14713 - Fix a rare seg fault for people running hidden services on
14714 intermittent connections.
14715 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
14717 - Fix more dns related bugs: send back resolve_failed and end cells
14718 more reliably when the resolve fails, rather than closing the
14719 circuit and then trying to send the cell. Also attach dummy resolve
14720 connections to a circuit *before* calling dns_resolve(), to fix
14721 a bug where cached answers would never be sent in RESOLVED cells.
14722 - When we run out of disk space, or other log writing error, don't
14723 crash. Just stop logging to that log and continue.
14724 - We were starting to daemonize before we opened our logs, so if
14725 there were any problems opening logs, we would complain to stderr,
14726 which wouldn't work, and then mysteriously exit.
14727 - Fix a rare bug where sometimes a verified OR would connect to us
14728 before he'd uploaded his descriptor, which would cause us to
14729 assign conn->nickname as though he's unverified. Now we look through
14730 the fingerprint list to see if he's there.
14731 - Fix a rare assert trigger, where routerinfos for entries in
14732 our cpath would expire while we're building the path.
14735 - Clients can ask dirservers for /dir.z to get a compressed version
14736 of the directory. Only works for servers running 0.0.9, of course.
14737 - Make clients cache directories and use them to seed their router
14738 lists at startup. This means clients have a datadir again.
14739 - Configuration infrastructure support for warning on obsolete
14741 - Respond to content-encoding headers by trying to uncompress as
14743 - Reply with a deflated directory when a client asks for "dir.z".
14744 We could use allow-encodings instead, but allow-encodings isn't
14745 specified in HTTP 1.0.
14746 - Raise the max dns workers from 50 to 100.
14747 - Discourage people from setting their dirfetchpostperiod more often
14748 than once per minute.
14749 - Protect dirservers from overzealous descriptor uploading -- wait
14750 10 seconds after directory gets dirty, before regenerating.
14753 Changes in version 0.0.8 - 2004-08-25
14754 o Port it to SunOS 5.9 / Athena
14757 Changes in version 0.0.8rc2 - 2004-08-20
14758 o Make it compile on cygwin again.
14759 o When picking unverified routers, skip those with low uptime and/or
14760 low bandwidth, depending on what properties you care about.
14763 Changes in version 0.0.8rc1 - 2004-08-18
14764 o Changes from 0.0.7.3:
14766 - Fix assert triggers: if the other side returns an address 0.0.0.0,
14767 don't put it into the client dns cache.
14768 - If a begin failed due to exit policy, but we believe the IP address
14769 should have been allowed, switch that router to exitpolicy reject *:*
14770 until we get our next directory.
14772 - Clients choose nodes proportional to advertised bandwidth.
14773 - Avoid using nodes with low uptime as introduction points.
14774 - Handle servers with dynamic IP addresses: don't replace
14775 options->Address with the resolved one at startup, and
14776 detect our address right before we make a routerinfo each time.
14777 - 'FascistFirewall' option to pick dirservers and ORs on specific
14778 ports; plus 'FirewallPorts' config option to tell FascistFirewall
14779 which ports are open. (Defaults to 80,443)
14780 - Be more aggressive about trying to make circuits when the network
14781 has changed (e.g. when you unsuspend your laptop).
14782 - Check for time skew on http headers; report date in response to
14784 - If the entrynode config line has only one node, don't pick it as
14786 - Add strict{entry|exit}nodes config options. If set to 1, then
14787 we refuse to build circuits that don't include the specified entry
14789 - OutboundBindAddress config option, to bind to a specific
14790 IP address for outgoing connect()s.
14791 - End truncated log entries (e.g. directories) with "[truncated]".
14793 o Patches to 0.0.8preX:
14795 - Patches to compile and run on win32 again (maybe)?
14796 - Fix crash when looking for ~/.torrc with no $HOME set.
14797 - Fix a race bug in the unit tests.
14798 - Handle verified/unverified name collisions better when new
14799 routerinfo's arrive in a directory.
14800 - Sometimes routers were getting entered into the stats before
14801 we'd assigned their identity_digest. Oops.
14802 - Only pick and establish intro points after we've gotten a
14805 - AllowUnverifiedNodes config option to let circuits choose no-name
14806 routers in entry,middle,exit,introduction,rendezvous positions.
14807 Allow middle and rendezvous positions by default.
14808 - Add a man page for tor-resolve.
14811 Changes in version 0.0.7.3 - 2004-08-12
14812 o Stop dnsworkers from triggering an assert failure when you
14813 ask them to resolve the host "".
14816 Changes in version 0.0.8pre3 - 2004-08-09
14817 o Changes from 0.0.7.2:
14818 - Allow multiple ORs with same nickname in routerlist -- now when
14819 people give us one identity key for a nickname, then later
14820 another, we don't constantly complain until the first expires.
14821 - Remember used bandwidth (both in and out), and publish 15-minute
14822 snapshots for the past day into our descriptor.
14823 - You can now fetch $DIRURL/running-routers to get just the
14824 running-routers line, not the whole descriptor list. (But
14825 clients don't use this yet.)
14826 - When people mistakenly use Tor as an http proxy, point them
14827 at the tor-doc.html rather than the INSTALL.
14828 - Remove our mostly unused -- and broken -- hex_encode()
14829 function. Use base16_encode() instead. (Thanks to Timo Lindfors
14830 for pointing out this bug.)
14831 - Rotate onion keys every 12 hours, not every 2 hours, so we have
14832 fewer problems with people using the wrong key.
14833 - Change the default exit policy to reject the default edonkey,
14834 kazaa, gnutella ports.
14835 - Add replace_file() to util.[ch] to handle win32's rename().
14837 o Changes from 0.0.8preX:
14838 - Fix two bugs in saving onion keys to disk when rotating, so
14839 hopefully we'll get fewer people using old onion keys.
14840 - Fix an assert error that was making SocksPolicy not work.
14841 - Be willing to expire routers that have an open dirport -- it's
14842 just the authoritative dirservers we want to not forget.
14843 - Reject tor-resolve requests for .onion addresses early, so we
14844 don't build a whole rendezvous circuit and then fail.
14845 - When you're warning a server that he's unverified, don't cry
14846 wolf unpredictably.
14847 - Fix a race condition: don't try to extend onto a connection
14848 that's still handshaking.
14849 - For servers in clique mode, require the conn to be open before
14850 you'll choose it for your path.
14851 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
14852 end relay cell, etc.
14853 - Measure bandwidth capacity over the last 24 hours, not just 12
14854 - Bugfix: authoritative dirservers were making and signing a new
14855 directory for each client, rather than reusing the cached one.
14858 Changes in version 0.0.8pre2 - 2004-08-04
14859 o Changes from 0.0.7.2:
14861 - Check directory signature _before_ you decide whether you're
14862 you're running an obsolete version and should exit.
14863 - Check directory signature _before_ you parse the running-routers
14864 list to decide who's running or verified.
14865 - Bugfixes and features:
14866 - Check return value of fclose while writing to disk, so we don't
14867 end up with broken files when servers run out of disk space.
14868 - Log a warning if the user uses an unsafe socks variant, so people
14869 are more likely to learn about privoxy or socat.
14870 - Dirservers now include RFC1123-style dates in the HTTP headers,
14871 which one day we will use to better detect clock skew.
14873 o Changes from 0.0.8pre1:
14874 - Make it compile without warnings again on win32.
14875 - Log a warning if you're running an unverified server, to let you
14876 know you might want to get it verified.
14877 - Only pick a default nickname if you plan to be a server.
14880 Changes in version 0.0.8pre1 - 2004-07-23
14882 - Made our unit tests compile again on OpenBSD 3.5, and tor
14883 itself compile again on OpenBSD on a sparc64.
14884 - We were neglecting milliseconds when logging on win32, so
14885 everything appeared to happen at the beginning of each second.
14887 o Protocol changes:
14888 - 'Extend' relay cell payloads now include the digest of the
14889 intended next hop's identity key. Now we can verify that we're
14890 extending to the right router, and also extend to routers we
14891 hadn't heard of before.
14894 - Tor nodes can now act as relays (with an advertised ORPort)
14895 without being manually verified by the dirserver operators.
14896 - Uploaded descriptors of unverified routers are now accepted
14897 by the dirservers, and included in the directory.
14898 - Verified routers are listed by nickname in the running-routers
14899 list; unverified routers are listed as "$<fingerprint>".
14900 - We now use hash-of-identity-key in most places rather than
14901 nickname or addr:port, for improved security/flexibility.
14902 - To avoid Sybil attacks, paths still use only verified servers.
14903 But now we have a chance to play around with hybrid approaches.
14904 - Nodes track bandwidth usage to estimate capacity (not used yet).
14905 - ClientOnly option for nodes that never want to become servers.
14906 - Directory caching.
14907 - "AuthoritativeDir 1" option for the official dirservers.
14908 - Now other nodes (clients and servers) will cache the latest
14909 directory they've pulled down.
14910 - They can enable their DirPort to serve it to others.
14911 - Clients will pull down a directory from any node with an open
14912 DirPort, and check the signature/timestamp correctly.
14913 - Authoritative dirservers now fetch directories from other
14914 authdirservers, to stay better synced.
14915 - Running-routers list tells who's down also, along with noting
14916 if they're verified (listed by nickname) or unverified (listed
14918 - Allow dirservers to serve running-router list separately.
14919 This isn't used yet.
14920 - ORs connect-on-demand to other ORs
14921 - If you get an extend cell to an OR you're not connected to,
14922 connect, handshake, and forward the create cell.
14923 - The authoritative dirservers stay connected to everybody,
14924 and everybody stays connected to 0.0.7 servers, but otherwise
14925 clients/servers expire unused connections after 5 minutes.
14926 - When servers get a sigint, they delay 30 seconds (refusing new
14927 connections) then exit. A second sigint causes immediate exit.
14928 - File and name management:
14929 - Look for .torrc if no CONFDIR "torrc" is found.
14930 - If no datadir is defined, then choose, make, and secure ~/.tor
14932 - If torrc not found, exitpolicy reject *:*.
14933 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
14934 - If no nickname is defined, derive default from hostname.
14935 - Rename secret key files, e.g. identity.key -> secret_id_key,
14936 to discourage people from mailing their identity key to tor-ops.
14937 - Refuse to build a circuit before the directory has arrived --
14938 it won't work anyway, since you won't know the right onion keys
14940 - Try other dirservers immediately if the one you try is down. This
14941 should tolerate down dirservers better now.
14942 - Parse tor version numbers so we can do an is-newer-than check
14943 rather than an is-in-the-list check.
14944 - New socks command 'resolve', to let us shim gethostbyname()
14946 - A 'tor_resolve' script to access the socks resolve functionality.
14947 - A new socks-extensions.txt doc file to describe our
14948 interpretation and extensions to the socks protocols.
14949 - Add a ContactInfo option, which gets published in descriptor.
14950 - Publish OR uptime in descriptor (and thus in directory) too.
14951 - Write tor version at the top of each log file
14952 - New docs in the tarball:
14954 - Document that you should proxy your SSL traffic too.
14957 Changes in version 0.0.7.2 - 2004-07-07
14958 o A better fix for the 0.0.0.0 problem, that will hopefully
14959 eliminate the remaining related assertion failures.
14962 Changes in version 0.0.7.1 - 2004-07-04
14963 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
14964 since internally we use 0.0.0.0 to signify "not yet resolved".
14967 Changes in version 0.0.7 - 2004-06-07
14968 o Updated the man page to reflect the new features.
14971 Changes in version 0.0.7rc2 - 2004-06-06
14972 o Changes from 0.0.7rc1:
14973 - Make it build on Win32 again.
14974 o Changes from 0.0.6.2:
14975 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
14979 Changes in version 0.0.7rc1 - 2004-06-02
14981 - On sighup, we were adding another log without removing the first
14982 one. So log messages would get duplicated n times for n sighups.
14983 - Several cases of using a connection after we'd freed it. The
14984 problem was that connections that are pending resolve are in both
14985 the pending_resolve tree, and also the circuit's resolving_streams
14986 list. When you want to remove one, you must remove it from both.
14987 - Fix a double-mark-for-close where an end cell arrived for a
14988 resolving stream, and then the resolve failed.
14989 - Check directory signatures based on name of signer, not on whom
14990 we got the directory from. This will let us cache directories more
14993 - Crank up some of our constants to handle more users.
14996 Changes in version 0.0.7pre1 - 2004-06-02
14997 o Fixes for crashes and other obnoxious bugs:
14998 - Fix an epipe bug: sometimes when directory connections failed
14999 to connect, we would give them a chance to flush before closing
15001 - When we detached from a circuit because of resolvefailed, we
15002 would immediately try the same circuit twice more, and then
15003 give up on the resolve thinking we'd tried three different
15005 - Limit the number of intro circuits we'll attempt to build for a
15006 hidden service per 15-minute period.
15007 - Check recommended-software string *early*, before actually parsing
15008 the directory. Thus we can detect an obsolete version and exit,
15009 even if the new directory format doesn't parse.
15010 o Fixes for security bugs:
15011 - Remember which nodes are dirservers when you startup, and if a
15012 random OR enables his dirport, don't automatically assume he's
15013 a trusted dirserver.
15015 - Directory connections were asking the wrong poll socket to
15016 start writing, and not asking themselves to start writing.
15017 - When we detached from a circuit because we sent a begin but
15018 didn't get a connected, we would use it again the first time;
15019 but after that we would correctly switch to a different one.
15020 - Stop warning when the first onion decrypt attempt fails; they
15021 will sometimes legitimately fail now that we rotate keys.
15022 - Override unaligned-access-ok check when $host_cpu is ia64 or
15023 arm. Apparently they allow it but the kernel whines.
15024 - Dirservers try to reconnect periodically too, in case connections
15026 - Fix some memory leaks in directory servers.
15027 - Allow backslash in Win32 filenames.
15028 - Made Tor build complain-free on FreeBSD, hopefully without
15029 breaking other BSD builds. We'll see.
15031 - Doxygen markup on all functions and global variables.
15032 - Make directory functions update routerlist, not replace it. So
15033 now directory disagreements are not so critical a problem.
15034 - Remove the upper limit on number of descriptors in a dirserver's
15035 directory (not that we were anywhere close).
15036 - Allow multiple logfiles at different severity ranges.
15037 - Allow *BindAddress to specify ":port" rather than setting *Port
15038 separately. Allow multiple instances of each BindAddress config
15039 option, so you can bind to multiple interfaces if you want.
15040 - Allow multiple exit policy lines, which are processed in order.
15041 Now we don't need that huge line with all the commas in it.
15042 - Enable accept/reject policies on SOCKS connections, so you can bind
15043 to 0.0.0.0 but still control who can use your OP.
15046 Changes in version 0.0.6.2 - 2004-05-16
15047 o Our integrity-checking digest was checking only the most recent cell,
15048 not the previous cells like we'd thought.
15049 Thanks to Stefan Mark for finding the flaw!
15052 Changes in version 0.0.6.1 - 2004-05-06
15053 o Fix two bugs in our AES counter-mode implementation (this affected
15054 onion-level stream encryption, but not TLS-level). It turns
15055 out we were doing something much more akin to a 16-character
15056 polyalphabetic cipher. Oops.
15057 Thanks to Stefan Mark for finding the flaw!
15058 o Retire moria3 as a directory server, and add tor26 as a directory
15062 Changes in version 0.0.6 - 2004-05-02
15063 [version bump only]
15066 Changes in version 0.0.6rc4 - 2004-05-01
15067 o Update the built-in dirservers list to use the new directory format
15068 o Fix a rare seg fault: if a node offering a hidden service attempts
15069 to build a circuit to Alice's rendezvous point and fails before it
15070 reaches the last hop, it retries with a different circuit, but
15072 o Handle windows socket errors correctly.
15075 Changes in version 0.0.6rc3 - 2004-04-28
15076 o Don't expire non-general excess circuits (if we had enough
15077 circuits open, we were expiring rendezvous circuits -- even
15078 when they had a stream attached. oops.)
15079 o Fetch randomness from /dev/urandom better (not via fopen/fread)
15080 o Better debugging for tls errors
15081 o Some versions of openssl have an SSL_pending function that erroneously
15082 returns bytes when there is a non-application record pending.
15083 o Set Content-Type on the directory and hidserv descriptor.
15084 o Remove IVs from cipher code, since AES-ctr has none.
15085 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
15086 o We were using an array of length zero in a few places.
15087 o win32's gethostbyname can't resolve an IP to an IP.
15088 o win32's close can't close a socket.
15091 Changes in version 0.0.6rc2 - 2004-04-26
15092 o Fix a bug where we were closing tls connections intermittently.
15093 It turns out openssl keeps its errors around -- so if an error
15094 happens, and you don't ask about it, and then another openssl
15095 operation happens and succeeds, and you ask if there was an error,
15096 it tells you about the first error. Fun fun.
15097 o Fix a bug that's been lurking since 27 may 03 (!)
15098 When passing back a destroy cell, we would use the wrong circ id.
15099 'Mostly harmless', but still worth fixing.
15100 o Since we don't support truncateds much, don't bother sending them;
15101 just close the circ.
15102 o check for <machine/limits.h> so we build on NetBSD again (I hope).
15103 o don't crash if a conn that sent a begin has suddenly lost its circuit
15104 (this was quite rare).
15107 Changes in version 0.0.6rc1 - 2004-04-25
15108 o We now rotate link (tls context) keys and onion keys.
15109 o CREATE cells now include oaep padding, so you can tell
15110 if you decrypted them correctly.
15111 o Add bandwidthburst to server descriptor.
15112 o Directories now say which dirserver signed them.
15113 o Use a tor_assert macro that logs failed assertions too.
15116 Changes in version 0.0.6pre5 - 2004-04-18
15117 o changes from 0.0.6pre4:
15118 - make tor build on broken freebsd 5.2 installs
15119 - fix a failed assert when you try an intro point, get a nack, and try
15120 a second one and it works.
15121 - when alice uses a port that the hidden service doesn't accept,
15122 it now sends back an end cell (denied by exit policy). otherwise
15123 alice would just have to wait to time out.
15124 - fix another rare bug: when we had tried all the intro
15125 points for a hidden service, we fetched the descriptor
15126 again, but we left our introcirc thinking it had already
15127 sent an intro, so it kept waiting for a response...
15128 - bugfix: when you sleep your hidden-service laptop, as soon
15129 as it wakes up it tries to upload a service descriptor, but
15130 socketpair fails for some reason (localhost not up yet?).
15131 now we simply give up on that upload, and we'll try again later.
15132 i'd still like to find the bug though.
15133 - if an intro circ waiting for an ack dies before getting one, then
15135 - we were reusing stale service descriptors and refetching usable
15139 Changes in version 0.0.6pre4 - 2004-04-14
15140 o changes from 0.0.6pre3:
15141 - when bob fails to connect to the rendezvous point, and his
15142 circ didn't fail because of the rendezvous point itself, then
15143 he retries a couple of times
15144 - we expire introduction and rendezvous circs more thoroughly
15145 (sometimes they were hanging around forever)
15146 - we expire unattached rendezvous streams that have been around
15147 too long (they were sticking around forever).
15148 - fix a measly fencepost error that was crashing everybody with
15152 Changes in version 0.0.6pre3 - 2004-04-14
15153 o changes from 0.0.6pre2:
15154 - make hup work again
15155 - fix some memory leaks for dirservers
15156 - allow more skew in rendezvous descriptor timestamps, to help
15157 handle people like blanu who don't know what time it is
15158 - normal circs are 3 hops, but some rend/intro circs are 4, if
15159 the initiator doesn't get to choose the last hop
15160 - send acks for introductions, so alice can know whether to try
15162 - bob publishes intro points more correctly
15163 o changes from 0.0.5:
15164 - fix an assert trigger that's been plaguing us since the days
15165 of 0.0.2prexx (thanks weasel!)
15166 - retry stream correctly when we fail to connect because of
15167 exit-policy-reject (should try another) or can't-resolve-address
15168 (also should try another, because dns on random internet servers
15170 - when we hup a dirserver and we've *removed* a server from the
15171 approved-routers list, now we remove that server from the
15172 in-memory directories too
15175 Changes in version 0.0.6pre2 - 2004-04-08
15176 o We fixed our base32 implementation. Now it works on all architectures.
15179 Changes in version 0.0.6pre1 - 2004-04-08
15181 - Hidden services and rendezvous points are implemented. Go to
15182 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
15183 hidden services. (This only works via a socks4a proxy such as
15184 Privoxy, and currently it's quite slow.)
15187 Changes in version 0.0.5 - 2004-03-30
15188 [version bump only]
15191 Changes in version 0.0.5rc3 - 2004-03-29
15192 o Install torrc as torrc.sample -- we no longer clobber your
15194 o Re-enable recommendedversion checking (we broke it in rc2, oops)
15195 o Add in a 'notice' log level for things the operator should hear
15196 but that aren't warnings
15199 Changes in version 0.0.5rc2 - 2004-03-29
15200 o Hold socks connection open until reply is flushed (if possible)
15201 o Make exit nodes resolve IPs to IPs immediately, rather than asking
15202 the dns farm to do it.
15203 o Fix c99 aliasing warnings in rephist.c
15204 o Don't include server descriptors that are older than 24 hours in the
15206 o Give socks 'reject' replies their whole 15s to attempt to flush,
15207 rather than seeing the 60s timeout and assuming the flush had failed.
15208 o Clean automake droppings from the cvs repository
15211 Changes in version 0.0.5rc1 - 2004-03-28
15212 o Fix mangled-state bug in directory fetching (was causing sigpipes).
15213 o Only build circuits after we've fetched the directory: clients were
15214 using only the directory servers before they'd fetched a directory.
15215 This also means longer startup time; so it goes.
15216 o Fix an assert trigger where an OP would fail to handshake, and we'd
15217 expect it to have a nickname.
15218 o Work around a tsocks bug: do a socks reject when AP connection dies
15219 early, else tsocks goes into an infinite loop.
15222 Changes in version 0.0.4 - 2004-03-26
15223 o When connecting to a dirserver or OR and the network is down,
15227 Changes in version 0.0.3 - 2004-03-26
15228 o Warn and fail if server chose a nickname with illegal characters
15229 o Port to Solaris and Sparc:
15230 - include missing header fcntl.h
15231 - have autoconf find -lsocket -lnsl automatically
15232 - deal with hardware word alignment
15233 - make uname() work (solaris has a different return convention)
15234 - switch from using signal() to sigaction()
15235 o Preliminary work on reputation system:
15236 - Keep statistics on success/fail of connect attempts; they're published
15237 by kill -USR1 currently.
15238 - Add a RunTesting option to try to learn link state by creating test
15239 circuits, even when SocksPort is off.
15240 - Remove unused open circuits when there are too many.
15243 Changes in version 0.0.2 - 2004-03-19
15244 - Include strlcpy and strlcat for safer string ops
15245 - define INADDR_NONE so we compile (but still not run) on solaris
15248 Changes in version 0.0.2pre27 - 2004-03-14
15250 - Allow internal tor networks (we were rejecting internal IPs,
15251 now we allow them if they're set explicitly).
15252 - And fix a few endian issues.
15255 Changes in version 0.0.2pre26 - 2004-03-14
15257 - If a stream times out after 15s without a connected cell, don't
15258 try that circuit again: try a new one.
15259 - Retry streams at most 4 times. Then give up.
15260 - When a dirserver gets a descriptor from an unknown router, it
15261 logs its fingerprint (so the dirserver operator can choose to
15262 accept it even without mail from the server operator).
15263 - Inform unapproved servers when we reject their descriptors.
15264 - Make tor build on Windows again. It works as a client, who knows
15266 - Clearer instructions in the torrc for how to set up a server.
15267 - Be more efficient about reading fd's when our global token bucket
15268 (used for rate limiting) becomes empty.
15270 - Stop asserting that computers always go forward in time. It's
15272 - When we sent a cell (e.g. destroy) and then marked an OR connection
15273 expired, we might close it before finishing a flush if the other
15274 side isn't reading right then.
15275 - Don't allow dirservers to start if they haven't defined
15276 RecommendedVersions
15277 - We were caching transient dns failures. Oops.
15278 - Prevent servers from publishing an internal IP as their address.
15279 - Address a strcat vulnerability in circuit.c
15282 Changes in version 0.0.2pre25 - 2004-03-04
15284 - Put the OR's IP in its router descriptor, not its fqdn. That way
15285 we'll stop being stalled by gethostbyname for nodes with flaky dns,
15288 - If the user typed in an address that didn't resolve, the server
15292 Changes in version 0.0.2pre24 - 2004-03-03
15294 - Fix an assertion failure in dns.c, where we were trying to dequeue
15295 a pending dns resolve even if it wasn't pending
15296 - Fix a spurious socks5 warning about still trying to write after the
15297 connection is finished.
15298 - Hold certain marked_for_close connections open until they're finished
15299 flushing, rather than losing bytes by closing them too early.
15300 - Correctly report the reason for ending a stream
15301 - Remove some duplicate calls to connection_mark_for_close
15302 - Put switch_id and start_daemon earlier in the boot sequence, so it
15303 will actually try to chdir() to options.DataDirectory
15304 - Make 'make test' exit(1) if a test fails; fix some unit tests
15305 - Make tor fail when you use a config option it doesn't know about,
15306 rather than warn and continue.
15307 - Make --version work
15308 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
15311 Changes in version 0.0.2pre23 - 2004-02-29
15313 - Print a statement when the first circ is finished, so the user
15314 knows it's working.
15315 - If a relay cell is unrecognized at the end of the circuit,
15316 send back a destroy. (So attacks to mutate cells are more
15318 - New config option 'excludenodes' to avoid certain nodes for circuits.
15319 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
15320 so you can collect coredumps there.
15322 - Fix a bug in tls flushing where sometimes data got wedged and
15323 didn't flush until more data got sent. Hopefully this bug was
15324 a big factor in the random delays we were seeing.
15325 - Make 'connected' cells include the resolved IP, so the client
15326 dns cache actually gets populated.
15327 - Disallow changing from ORPort=0 to ORPort>0 on hup.
15328 - When we time-out on a stream and detach from the circuit, send an
15329 end cell down it first.
15330 - Only warn about an unknown router (in exitnodes, entrynodes,
15331 excludenodes) after we've fetched a directory.
15334 Changes in version 0.0.2pre22 - 2004-02-26
15336 - Servers publish less revealing uname information in descriptors.
15337 - More memory tracking and assertions, to crash more usefully when
15339 - If the default torrc isn't there, just use some default defaults.
15340 Plus provide an internal dirservers file if they don't have one.
15341 - When the user tries to use Tor as an http proxy, give them an http
15342 501 failure explaining that we're a socks proxy.
15343 - Dump a new router.desc on hup, to help confused people who change
15344 their exit policies and then wonder why router.desc doesn't reflect
15346 - Clean up the generic tor.sh init script that we ship with.
15348 - If the exit stream is pending on the resolve, and a destroy arrives,
15349 then the stream wasn't getting removed from the pending list. I
15350 think this was the one causing recent server crashes.
15351 - Use a more robust poll on OSX 10.3, since their poll is flaky.
15352 - When it couldn't resolve any dirservers, it was useless from then on.
15353 Now it reloads the RouterFile (or default dirservers) if it has no
15355 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
15356 many users don't even *have* a /usr/local/sbin/.
15359 Changes in version 0.0.2pre21 - 2004-02-18
15361 - There's a ChangeLog file that actually reflects the changelog.
15362 - There's a 'torify' wrapper script, with an accompanying
15363 tor-tsocks.conf, that simplifies the process of using tsocks for
15364 tor. It even has a man page.
15365 - The tor binary gets installed to sbin rather than bin now.
15366 - Retry streams where the connected cell hasn't arrived in 15 seconds
15367 - Clean up exit policy handling -- get the default out of the torrc,
15368 so we can update it without forcing each server operator to fix
15370 - Allow imaps and pop3s in default exit policy
15372 - Prevent picking middleman nodes as the last node in the circuit
15375 Changes in version 0.0.2pre20 - 2004-01-30
15377 - We now have a deb package, and it's in debian unstable. Go to
15378 it, apt-getters. :)
15379 - I've split the TotalBandwidth option into BandwidthRate (how many
15380 bytes per second you want to allow, long-term) and
15381 BandwidthBurst (how many bytes you will allow at once before the cap
15382 kicks in). This better token bucket approach lets you, say, set
15383 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
15384 performance while not exceeding your monthly bandwidth quota.
15385 - Push out a tls record's worth of data once you've got it, rather
15386 than waiting until you've read everything waiting to be read. This
15387 may improve performance by pipelining better. We'll see.
15388 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
15389 from failed circuits (if they haven't been connected yet) and attach
15391 - Expire old streams that haven't managed to connect. Some day we'll
15392 have them reattach to new circuits instead.
15395 - Fix several memory leaks that were causing servers to become bloated
15397 - Fix a few very rare assert triggers. A few more remain.
15398 - Setuid to User _before_ complaining about running as root.
15401 Changes in version 0.0.2pre19 - 2004-01-07
15403 - Fix deadlock condition in dns farm. We were telling a child to die by
15404 closing the parent's file descriptor to him. But newer children were
15405 inheriting the open file descriptor from the parent, and since they
15406 weren't closing it, the socket never closed, so the child never read
15407 eof, so he never knew to exit. Similarly, dns workers were holding
15408 open other sockets, leading to all sorts of chaos.
15409 - New cleaner daemon() code for forking and backgrounding.
15410 - If you log to a file, it now prints an entry at the top of the
15411 logfile so you know it's working.
15412 - The onionskin challenge length was 30 bytes longer than necessary.
15413 - Started to patch up the spec so it's not quite so out of date.
15416 Changes in version 0.0.2pre18 - 2004-01-02
15418 - Fix endian issues with the 'integrity' field in the relay header.
15419 - Fix a potential bug where connections in state
15420 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
15423 Changes in version 0.0.2pre17 - 2003-12-30
15425 - Made --debuglogfile (or any second log file, actually) work.
15426 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
15427 adversary could force us into an infinite loop.
15430 - Each onionskin handshake now includes a hash of the computed key,
15431 to prove the server's identity and help perfect forward secrecy.
15432 - Changed cell size from 256 to 512 bytes (working toward compatibility
15434 - Changed cell length to 2 bytes, and moved it to the relay header.
15435 - Implemented end-to-end integrity checking for the payloads of
15437 - Separated streamid from 'recognized' (otherwise circuits will get
15438 messed up when we try to have streams exit from the middle). We
15439 use the integrity-checking to confirm that a cell is addressed to
15441 - Randomize the initial circid and streamid values, so an adversary who
15442 breaks into a node can't learn how many circuits or streams have
15446 Changes in version 0.0.2pre16 - 2003-12-14
15448 - Fixed a bug that made HUP trigger an assert
15449 - Fixed a bug where a circuit that immediately failed wasn't being
15450 counted as a failed circuit in counting retries.
15453 - Now we close the circuit when we get a truncated cell: otherwise we're
15454 open to an anonymity attack where a bad node in the path truncates
15455 the circuit and then we open streams at him.
15456 - Add port ranges to exit policies
15457 - Add a conservative default exit policy
15458 - Warn if you're running tor as root
15459 - on HUP, retry OR connections and close/rebind listeners
15460 - options.EntryNodes: try these nodes first when picking the first node
15461 - options.ExitNodes: if your best choices happen to include any of
15462 your preferred exit nodes, you choose among just those preferred
15464 - options.ExcludedNodes: nodes that are never picked in path building
15467 Changes in version 0.0.2pre15 - 2003-12-03
15468 o Robustness and bugfixes:
15469 - Sometimes clients would cache incorrect DNS resolves, which would
15470 really screw things up.
15471 - An OP that goes offline would slowly leak all its sockets and stop
15473 - A wide variety of bugfixes in exit node selection, exit policy
15474 handling, and processing pending streams when a new circuit is
15476 - Pick nodes for a path only from those the directory says are up
15477 - Choose randomly from all running dirservers, not always the first one
15478 - Increase allowed http header size for directory fetch.
15479 - Stop writing to stderr (if we're daemonized it will be closed).
15480 - Enable -g always, so cores will be more useful to me.
15481 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
15484 - Wrote a man page. It lists commonly used options.
15487 - Change default loglevel to warn.
15488 - Make PidFile default to null rather than littering in your CWD.
15489 - OnionRouter config option is now obsolete. Instead it just checks
15491 - Moved to a single unified torrc file for both clients and servers.
15494 Changes in version 0.0.2pre14 - 2003-11-29
15495 o Robustness and bugfixes:
15496 - Force the admin to make the DataDirectory himself
15497 - to get ownership/permissions right
15498 - so clients no longer make a DataDirectory and then never use it
15499 - fix bug where a client who was offline for 45 minutes would never
15500 pull down a directory again
15501 - fix (or at least hide really well) the dns assert bug that was
15502 causing server crashes
15503 - warnings and improved robustness wrt clockskew for certs
15504 - use the native daemon(3) to daemonize, when available
15505 - exit if bind() fails
15506 - exit if neither socksport nor orport is defined
15507 - include our own tor_timegm (Win32 doesn't have its own)
15508 - bugfix for win32 with lots of connections
15509 - fix minor bias in PRNG
15510 - make dirserver more robust to corrupt cached directory
15513 - Wrote the design document (woo)
15515 o Circuit building and exit policies:
15516 - Circuits no longer try to use nodes that the directory has told them
15518 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
15519 bitcounts (18.0.0.0/8).
15520 - Make AP connections standby for a circuit if no suitable circuit
15521 exists, rather than failing
15522 - Circuits choose exit node based on addr/port, exit policies, and
15523 which AP connections are standing by
15524 - Bump min pathlen from 2 to 3
15525 - Relay end cells have a payload to describe why the stream ended.
15526 - If the stream failed because of exit policy, try again with a new
15528 - Clients have a dns cache to remember resolved addresses.
15529 - Notice more quickly when we have no working circuits
15532 - APPort is now called SocksPort
15533 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
15535 - RecommendedVersions is now a config variable rather than
15536 hardcoded (for dirservers)
15537 - Reloads config on HUP
15538 - Usage info on -h or --help
15539 - If you set User and Group config vars, it'll setu/gid to them.
15542 Changes in version 0.0.2pre13 - 2003-10-19
15543 o General stability:
15544 - SSL_write no longer fails when it returns WANTWRITE and the number
15545 of bytes in the buf has changed by the next SSL_write call.
15546 - Fix segfault fetching directory when network is down
15547 - Fix a variety of minor memory leaks
15548 - Dirservers reload the fingerprints file on HUP, so I don't have
15549 to take down the network when I approve a new router
15550 - Default server config file has explicit Address line to specify fqdn
15553 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
15554 - Make listener connections not ever alloc bufs
15556 o Autoconf improvements:
15557 - don't clobber an external CFLAGS in ./configure
15558 - Make install now works
15559 - create var/lib/tor on make install
15560 - autocreate a tor.sh initscript to help distribs
15561 - autocreate the torrc and sample-server-torrc with correct paths
15563 o Log files and Daemonizing now work:
15564 - If --DebugLogFile is specified, log to it at -l debug
15565 - If --LogFile is specified, use it instead of commandline
15566 - If --RunAsDaemon is set, tor forks and backgrounds on startup