1 Changes in version 0.2.4.5-alpha - 2012-10-25
2 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
3 two important security vulnerabilities that could lead to remotely
4 triggerable relay crashes, fix a major bug that was preventing clients
5 from choosing suitable exit nodes, and refactor some of our code.
7 o Major bugfixes (security, also in 0.2.3.24-rc):
8 - Fix a group of remotely triggerable assertion failures related to
9 incorrect link protocol negotiation. Found, diagnosed, and fixed
10 by "some guy from France". Fix for CVE-2012-2250; bugfix on
12 - Fix a denial of service attack by which any directory authority
13 could crash all the others, or by which a single v2 directory
14 authority could crash everybody downloading v2 directory
15 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
17 o Major bugfixes (also in 0.2.3.24-rc):
18 - When parsing exit policy summaries from microdescriptors, we had
19 previously been ignoring the last character in each one, so that
20 "accept 80,443,8080" would be treated by clients as indicating
21 a node that allows access to ports 80, 443, and 808. That would
22 lead to clients attempting connections that could never work,
23 and ignoring exit nodes that would support their connections. Now
24 clients parse these exit policy summaries correctly. Fixes bug 7192;
25 bugfix on 0.2.3.1-alpha.
27 o Minor bugfixes (also in 0.2.3.24-rc):
28 - Clients now consider the ClientRejectInternalAddresses config option
29 when using a microdescriptor consensus stanza to decide whether
30 an exit relay would allow exiting to an internal address. Fixes
31 bug 7190; bugfix on 0.2.3.1-alpha.
34 - Only disable TLS session ticket support when running as a TLS
35 server. Now clients will blend better with regular Firefox
36 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
38 o Code simplification and refactoring:
39 - Start using OpenBSD's implementation of queue.h (originally by
41 - Move the entry node code from circuitbuild.c to its own file.
42 - Move the circuit build timeout tracking code from circuitbuild.c
46 Changes in version 0.2.3.24-rc - 2012-10-25
47 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
48 could lead to remotely triggerable relay crashes, and fixes
49 a major bug that was preventing clients from choosing suitable exit
52 o Major bugfixes (security):
53 - Fix a group of remotely triggerable assertion failures related to
54 incorrect link protocol negotiation. Found, diagnosed, and fixed
55 by "some guy from France". Fix for CVE-2012-2250; bugfix on
57 - Fix a denial of service attack by which any directory authority
58 could crash all the others, or by which a single v2 directory
59 authority could crash everybody downloading v2 directory
60 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
63 - When parsing exit policy summaries from microdescriptors, we had
64 previously been ignoring the last character in each one, so that
65 "accept 80,443,8080" would be treated by clients as indicating
66 a node that allows access to ports 80, 443, and 808. That would
67 lead to clients attempting connections that could never work,
68 and ignoring exit nodes that would support their connections. Now
69 clients parse these exit policy summaries correctly. Fixes bug 7192;
70 bugfix on 0.2.3.1-alpha.
73 - Clients now consider the ClientRejectInternalAddresses config option
74 when using a microdescriptor consensus stanza to decide whether
75 an exit relay would allow exiting to an internal address. Fixes
76 bug 7190; bugfix on 0.2.3.1-alpha.
79 Changes in version 0.2.4.4-alpha - 2012-10-20
80 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
81 vulnerability introduced by a change in OpenSSL, fixes a remotely
82 triggerable assert, and adds new channel_t and circuitmux_t abstractions
83 that will make it easier to test new connection transport and cell
84 scheduling algorithms.
86 o New directory authorities (also in 0.2.3.23-rc):
87 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
88 authority. Closes ticket 5749.
90 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
91 - Disable TLS session tickets. OpenSSL's implementation was giving
92 our TLS session keys the lifetime of our TLS context objects, when
93 perfect forward secrecy would want us to discard anything that
94 could decrypt a link connection as soon as the link connection
95 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
96 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
97 - Discard extraneous renegotiation attempts once the V3 link
98 protocol has been initiated. Failure to do so left us open to
99 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
100 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
102 o Internal abstraction features:
103 - Introduce new channel_t abstraction between circuits and
104 or_connection_t to allow for implementing alternate OR-to-OR
105 transports. A channel_t is an abstract object which can either be a
106 cell-bearing channel, which is responsible for authenticating and
107 handshaking with the remote OR and transmitting cells to and from
108 it, or a listening channel, which spawns new cell-bearing channels
109 at the request of remote ORs. Implements part of ticket 6465.
110 - Also new is the channel_tls_t subclass of channel_t, adapting it
111 to the existing or_connection_t code. The V2/V3 protocol handshaking
112 code which formerly resided in command.c has been moved below the
113 channel_t abstraction layer and may be found in channeltls.c now.
114 Implements the rest of ticket 6465.
115 - Introduce new circuitmux_t storing the queue of circuits for
116 a channel; this encapsulates and abstracts the queue logic and
117 circuit selection policy, and allows the latter to be overridden
118 easily by switching out a policy object. The existing EWMA behavior
119 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
121 o Required libraries:
122 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
123 strongly recommended.
126 - Warn users who run hidden services on a Tor client with
127 UseEntryGuards disabled that their hidden services will be
128 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
129 attack which motivated Tor to support entry guards in the first
130 place). Resolves ticket 6889.
131 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
132 dhill. Resolves ticket 6982.
133 - Option OutboundBindAddress can be specified multiple times and
134 accepts IPv6 addresses. Resolves ticket 6876.
136 o Minor bugfixes (also in 0.2.3.23-rc):
137 - Don't serve or accept v2 hidden service descriptors over a
138 relay's DirPort. It's never correct to do so, and disabling it
139 might make it more annoying to exploit any bugs that turn up in the
140 descriptor-parsing code. Fixes bug 7149.
141 - Fix two cases in src/or/transports.c where we were calling
142 fmt_addr() twice in a parameter list. Bug found by David
143 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
144 - Fix memory leaks whenever we logged any message about the "path
145 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
146 - When relays refuse a "create" cell because their queue of pending
147 create cells is too big (typically because their cpu can't keep up
148 with the arrival rate), send back reason "resource limit" rather
149 than reason "internal", so network measurement scripts can get a
150 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
153 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
154 - Free some more still-in-use memory at exit, to make hunting for
155 memory leaks easier. Resolves bug 7029.
156 - When a Tor client gets a "truncated" relay cell, the first byte of
157 its payload specifies why the circuit was truncated. We were
158 ignoring this 'reason' byte when tearing down the circuit, resulting
159 in the controller not being told why the circuit closed. Now we
160 pass the reason from the truncated cell to the controller. Bugfix
161 on 0.1.2.3-alpha; fixes bug 7039.
162 - Downgrade "Failed to hand off onionskin" messages to "debug"
163 severity, since they're typically redundant with the "Your computer
164 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
165 - Make clients running with IPv6 bridges connect over IPv6 again,
166 even without setting new config options ClientUseIPv6 and
167 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
168 - Use square brackets around IPv6 addresses in numerous places
169 that needed them, including log messages, HTTPS CONNECT proxy
170 requests, TransportProxy statefile entries, and pluggable transport
171 extra-info lines. Fixes bug 7011; patch by David Fifield.
173 o Code refactoring and cleanup:
174 - Source files taken from other packages now reside in src/ext;
175 previously they were scattered around the rest of Tor.
176 - Avoid use of reserved identifiers in our C code. The C standard
177 doesn't like us declaring anything that starts with an
178 underscore, so let's knock it off before we get in trouble. Fix
179 for bug 1031; bugfix on the first Tor commit.
182 Changes in version 0.2.3.23-rc - 2012-10-20
183 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
184 vulnerability introduced by a change in OpenSSL, and fixes a variety
185 of smaller bugs in preparation for the release.
187 o New directory authorities:
188 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
189 authority. Closes ticket 5749.
191 o Major bugfixes (security/privacy):
192 - Disable TLS session tickets. OpenSSL's implementation was giving
193 our TLS session keys the lifetime of our TLS context objects, when
194 perfect forward secrecy would want us to discard anything that
195 could decrypt a link connection as soon as the link connection
196 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
197 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
198 - Discard extraneous renegotiation attempts once the V3 link
199 protocol has been initiated. Failure to do so left us open to
200 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
201 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
204 - Fix a possible crash bug when checking for deactivated circuits
205 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
206 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
208 o Minor bugfixes (on 0.2.3.x):
209 - Fix two cases in src/or/transports.c where we were calling
210 fmt_addr() twice in a parameter list. Bug found by David
211 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
212 - Convert an assert in the pathbias code to a log message. The assert
213 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
214 bugfix on 0.2.3.17-beta.
215 - Fix memory leaks whenever we logged any message about the "path
216 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
218 o Minor bugfixes (on 0.2.2.x and earlier):
219 - Don't serve or accept v2 hidden service descriptors over a relay's
220 DirPort. It's never correct to do so, and disabling it might
221 make it more annoying to exploit any bugs that turn up in the
222 descriptor-parsing code. Fixes bug 7149.
223 - When relays refuse a "create" cell because their queue of pending
224 create cells is too big (typically because their cpu can't keep up
225 with the arrival rate), send back reason "resource limit" rather
226 than reason "internal", so network measurement scripts can get a
227 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
228 - Correct file sizes when reading binary files on Cygwin, to avoid
229 a bug where Tor would fail to read its state file. Fixes bug 6844;
230 bugfix on 0.1.2.7-alpha.
231 - Avoid undefined behaviour when parsing the list of supported
232 rendezvous/introduction protocols in a hidden service descriptor.
233 Previously, Tor would have confused (as-yet-unused) protocol version
234 numbers greater than 32 with lower ones on many platforms. Fixes
235 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
237 o Documentation fixes:
238 - Clarify that hidden services are TCP only. Fixes bug 6024.
241 Changes in version 0.2.4.3-alpha - 2012-09-22
242 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
243 assertion, resumes letting relays test reachability of their DirPort,
244 and cleans up a bunch of smaller bugs.
247 - Fix an assertion failure in tor_timegm() that could be triggered
248 by a badly formatted directory object. Bug found by fuzzing with
249 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
252 - Fix a possible crash bug when checking for deactivated circuits
253 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
254 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
255 - Allow routers to detect that their own DirPorts are running. When
256 we removed support for versions_supports_begindir, we also
257 accidentally removed the mechanism we used to self-test our
258 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
259 bugfix on 0.2.4.2-alpha.
262 - Switch to a completely time-invariant approach for picking nodes
263 weighted by bandwidth. Our old approach would run through the
264 part of the loop after it had made its choice slightly slower
265 than it ran through the part of the loop before it had made its
266 choice. Addresses ticket 6538.
267 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
268 by tor2web clients allows hidden services to identity tor2web
269 clients through their repeated selection of the same rendezvous
270 and introduction point circuit endpoints (their guards). Resolves
274 - Enable Tor to read configuration, state, and key information from
275 a FIFO. Previously Tor would only read from files with a positive
276 stat.st_size. Code from meejah; fixes bug 6044.
279 - Correct file sizes when reading binary files on Cygwin, to avoid
280 a bug where Tor would fail to read its state file. Fixes bug 6844;
281 bugfix on 0.1.2.7-alpha.
282 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
283 bugfix on 0.2.0.3-alpha.
284 - When complaining about a client port on a public address, log
285 which address we're complaining about. Fixes bug 4020; bugfix on
286 0.2.3.3-alpha. Patch by Tom Fitzhenry.
287 - Convert an assert in the pathbias code to a log message. The assert
288 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
289 bugfix on 0.2.3.17-beta.
290 - Our new buildsystem was overzealous about rebuilding manpages: it
291 would rebuild them all whenever any one of them changed. Now our
292 dependency checking should be correct. Fixes bug 6843; bugfix on
294 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
295 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
296 - Correct log printout about which address family is preferred
297 when connecting to a bridge with both an IPv4 and IPv6 OR port.
298 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
300 o Minor bugfixes (code cleanliness):
301 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
302 with large values. This situation was untriggered, but nevertheless
303 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
304 - Reject consensus votes with more than 64 known-flags. We aren't even
305 close to that limit yet, and our code doesn't handle it correctly.
306 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
307 - Avoid undefined behaviour when parsing the list of supported
308 rendezvous/introduction protocols in a hidden service descriptor.
309 Previously, Tor would have confused (as-yet-unused) protocol version
310 numbers greater than 32 with lower ones on many platforms. Fixes
311 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
312 - Fix handling of rendezvous client authorization types over 8.
313 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
314 - Fix building with older versions of GCC (2.95, for one) that don't
315 like preprocessor directives inside macro arguments. Found by
316 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
317 - Switch weighted node selection rule from using a list of doubles
318 to using a list of int64_t. This change should make the process
319 slightly easier to debug and maintain. Needed to finish ticket 6538.
321 o Code simplification and refactoring:
322 - Move the generic "config" code into a new file, and have "config.c"
323 hold only torrc- and state-related code. Resolves ticket 6823.
324 - Move the core of our "choose a weighted element at random" logic
325 into its own function, and give it unit tests. Now the logic is
326 testable, and a little less fragile too.
327 - Removed the testing_since field of node_t, which hasn't been used
328 for anything since 0.2.0.9-alpha.
330 o Documentation fixes:
331 - Clarify that hidden services are TCP only. Fixes bug 6024.
332 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
336 Changes in version 0.2.3.22-rc - 2012-09-11
337 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
341 - Fix an assertion failure in tor_timegm() that could be triggered
342 by a badly formatted directory object. Bug found by fuzzing with
343 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
346 - Avoid segfault when starting up having run with an extremely old
347 version of Tor and parsing its state file. Fixes bug 6801; bugfix
351 Changes in version 0.2.2.39 - 2012-09-11
352 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
356 - Fix an assertion failure in tor_timegm() that could be triggered
357 by a badly formatted directory object. Bug found by fuzzing with
358 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
359 - Do not crash when comparing an address with port value 0 to an
360 address policy. This bug could have been used to cause a remote
361 assertion failure by or against directory authorities, or to
362 allow some applications to crash clients. Fixes bug 6690; bugfix
366 Changes in version 0.2.4.2-alpha - 2012-09-10
367 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
368 raises the default rate limiting even more, and makes the bootstrapping
369 log messages less noisy.
372 - Automatically forward the TCP ports of pluggable transport
373 proxies using tor-fw-helper if PortForwarding is enabled. Implements
377 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
378 to 1GB/1GB. The previous defaults were intended to be "basically
379 infinite", but it turns out they're now limiting our 100mbit+
380 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
381 last time we raised it).
384 - Detect when we're running with a version of OpenSSL other than the
385 one we compiled with. This has occasionally given people hard-to-
387 - Log fewer lines at level "notice" about our OpenSSL and Libevent
388 versions and capabilities when everything is going right. Resolves
390 - Directory authorities no long accept descriptors for any version of
391 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
392 These versions are insecure, unsupported, or both. Implements
396 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
397 to start with a triple-underscore so the controller won't touch it.
398 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
399 - Avoid segfault when starting up having run with an extremely old
400 version of Tor and parsing its state file. Fixes bug 6801; bugfix
402 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
403 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
404 - Don't follow the NULL pointer if microdescriptor generation fails.
405 (This does not appear to be triggerable, but it's best to be safe.)
406 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
407 - Fix mis-declared dependencies on src/common/crypto.c and
408 src/or/tor_main.c that could break out-of-tree builds under some
409 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
410 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
411 6778; bugfix on 0.2.4.1-alpha.
412 - Fix a harmless (in this case) build warning for implicitly
413 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
416 - Now that all versions before 0.2.2.x are disallowed, we no longer
417 need to work around their missing features. Thus we can remove a
418 bunch of compatibility code.
421 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
422 TCP ports to forward. In the past it only accepted two ports:
423 the ORPort and the DirPort.
426 Changes in version 0.2.4.1-alpha - 2012-09-05
427 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
428 bridgedb; lets relays use IPv6 addresses and directory authorities
429 advertise them; and switches to a cleaner build interface.
431 This is the first alpha release in a new series, so expect there to
432 be bugs. Users who would rather test out a more stable branch should
433 stay with 0.2.3.x for now.
435 o Major features (bridges):
436 - Bridges now report the pluggable transports they support to the
437 bridge authority, so it can pass the supported transports on to
438 bridgedb and/or eventually do reachability testing. Implements
441 o Major features (IPv6):
442 - Bridge authorities now accept IPv6 bridge addresses and include
443 them in network status documents. Implements ticket 5534.
444 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
445 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
446 to happen. Implements ticket 5535.
447 - All kind of relays, not just bridges, can now advertise an IPv6
448 OR port. Implements ticket 6362.
449 - Directory authorities vote on IPv6 OR ports using the new consensus
450 method 14. Implements ticket 6363.
452 o Major features (build):
453 - Switch to a nonrecursive Makefile structure. Now instead of each
454 Makefile.am invoking other Makefile.am's, there is a master
455 Makefile.am that includes the others. This change makes our build
456 process slightly more maintainable, and improves parallelism for
457 building with make -j. Original patch by Stewart Smith; various
458 fixes by Jim Meyering.
459 - Where available, we now use automake's "silent" make rules by
460 default, so that warnings are easier to spot. You can get the old
461 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
463 o Minor features (code security and spec conformance):
464 - Clear keys and key-derived material left on the stack in
465 rendservice.c and rendclient.c. Check return value of
466 crypto_pk_write_private_key_to_string() in end_service_load_keys().
467 These fixes should make us more forward-secure against cold-boot
468 attacks and the like. Fixes bug 2385.
469 - Reject EXTEND cells sent to nonexistent streams. According to the
470 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
471 we were only checking for stream IDs that were currently in use.
472 Found while hunting for more instances of bug 6271. Bugfix on
473 0.0.2pre8, which introduced incremental circuit construction.
475 o Minor features (streamlining);
476 - No longer include the "opt" prefix when generating routerinfos
477 or v2 directories: it has been needless since Tor 0.1.2. Closes
479 - Remove some now-needless code that tried to aggressively flush
480 OR connections as data was added to them. Since 0.2.0.1-alpha, our
481 cell queue logic has saved us from the failure mode that this code
482 was supposed to prevent. Removing this code will limit the number
483 of baroque control flow paths through Tor's network logic. Reported
484 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
486 o Minor features (controller):
487 - Add a "GETINFO signal/names" control port command. Implements
489 - Provide default values for all options via "GETINFO config/defaults".
490 Implements ticket 4971.
492 o Minor features (IPv6):
493 - New config option "AuthDirHasIPv6Connectivity 1" that directory
494 authorities should set if they have IPv6 connectivity and want to
495 do reachability tests for IPv6 relays. Implements feature 5974.
496 - A relay with an IPv6 OR port now sends that address in NETINFO
497 cells (in addition to its other address). Implements ticket 6364.
499 o Minor features (log messages):
500 - Omit the first heartbeat log message, because it never has anything
501 useful to say, and it clutters up the bootstrapping messages.
502 Resolves ticket 6758.
503 - Don't log about reloading the microdescriptor cache at startup. Our
504 bootstrap warnings are supposed to tell the user when there's a
505 problem, and our bootstrap notices say when there isn't. Resolves
506 ticket 6759; bugfix on 0.2.2.6-alpha.
507 - Don't log "I learned some more directory information" when we're
508 reading cached directory information. Reserve it for when new
509 directory information arrives in response to a fetch. Resolves
511 - Prevent rounding error in path bias counts when scaling
512 them down, and use the correct scale factor default. Also demote
513 some path bias related log messages down a level and make others
514 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
515 - We no longer warn so much when generating manpages from their
518 o Code simplifications and refactoring:
519 - Enhance our internal sscanf replacement so that we can eliminate
520 the last remaining uses of the system sscanf. (Though those uses
521 of sscanf were safe, sscanf itself is generally error prone, so
522 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
524 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
525 - Move last_reachable and testing_since from routerinfo_t to node_t.
526 Implements ticket 5529.
527 - Add replaycache_t structure, functions and unit tests, then refactor
528 rend_service_introduce() to be more clear to read, improve, debug,
529 and test. Resolves bug 6177.
530 - Finally remove support for malloc_good_size and malloc_usable_size.
531 We had hoped that these functions would let us eke a little more
532 memory out of our malloc implementation. Unfortunately, the only
533 implementations that provided these functions are also ones that
534 are already efficient about not overallocation: they never got us
535 more than 7 or so bytes per allocation. Removing them saves us a
536 little code complexity and a nontrivial amount of build complexity.
539 - Tor maintainers now require Automake version 1.9 or later to build
540 Tor from the Git repository. (Automake is not required when building
541 from a source distribution.)
544 Changes in version 0.2.3.21-rc - 2012-09-05
545 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
546 series. It fixes a trio of potential security bugs, fixes a bug where
547 we were leaving some of the fast relays out of the microdescriptor
548 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
549 and cleans up other smaller issues.
551 o Major bugfixes (security):
552 - Tear down the circuit if we get an unexpected SENDME cell. Clients
553 could use this trick to make their circuits receive cells faster
554 than our flow control would have allowed, or to gum up the network,
555 or possibly to do targeted memory denial-of-service attacks on
556 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
557 from July 2002, before the release of Tor 0.0.0. We had committed
558 this patch previously, but we had to revert it because of bug 6271.
559 Now that 6271 is fixed, this patch appears to work.
560 - Reject any attempt to extend to an internal address. Without
561 this fix, a router could be used to probe addresses on an internal
562 network to see whether they were accepting connections. Fixes bug
563 6710; bugfix on 0.0.8pre1.
564 - Do not crash when comparing an address with port value 0 to an
565 address policy. This bug could have been used to cause a remote
566 assertion failure by or against directory authorities, or to
567 allow some applications to crash clients. Fixes bug 6690; bugfix
571 - Remove the upper bound on microdescriptor length. We were hitting
572 the limit for routers with complex exit policies or family
573 declarations, causing clients to not use them. Fixes the first
574 piece of bug 6404; fix on 0.2.2.6-alpha.
575 - Detect "ORPort 0" as meaning, uniformly, that we're not running
576 as a relay. Previously, some of our code would treat the presence
577 of any ORPort line as meaning that we should act like a relay,
578 even though our new listener code would correctly not open any
579 ORPorts for ORPort 0. Similar bugs in other Port options are also
580 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
583 - Avoid a pair of double-free and use-after-mark bugs that can
584 occur with certain timings in canceled and re-received DNS
585 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
586 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
587 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
588 - Allow one-hop directory fetching circuits the full "circuit build
589 timeout" period, rather than just half of it, before failing them
590 and marking the relay down. This fix should help reduce cases where
591 clients declare relays (or worse, bridges) unreachable because
592 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
593 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
595 - Authorities no longer include any router in their microdescriptor
596 consensuses for which they couldn't generate or agree on a
597 microdescriptor. Fixes the second piece of bug 6404; fix on
599 - Detect and reject attempts to specify both "FooPort" and
600 "FooPort 0" in the same configuration domain. (It's still okay
601 to have a FooPort in your configuration file, and use "FooPort 0"
602 on the command line to disable it.) Fixes the second half of bug
603 6507; bugfix on 0.2.3.3-alpha.
604 - Make wildcarded addresses (that is, ones beginning with "*.") work
605 when provided via the controller's MapAddress command. Previously,
606 they were accepted, but we never actually noticed that they were
607 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
608 - Avoid crashing on a malformed state file where EntryGuardPathBias
609 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
610 - Add a (probably redundant) memory clear between iterations of
611 the router status voting loop, to prevent future coding errors
612 where data might leak between iterations of the loop. Resolves
615 o Minor bugfixes (log messages):
616 - Downgrade "set buildtimeout to low value" messages to "info"
617 severity; they were never an actual problem, there was never
618 anything reasonable to do about them, and they tended to spam logs
619 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
620 - Downgrade path-bias warning messages to "info". We'll try to get
621 them working better in 0.2.4. Add internal circuit construction
622 state to protect against the noisy warn message "Unexpectedly high
623 circuit_successes". Also add some additional rate-limited notice
624 messages to help determine the root cause of the warn. Fixes bug
625 6475. Bugfix against 0.2.3.17-beta.
626 - Move log message when unable to find a microdesc in a routerstatus
627 entry to parse time. Previously we'd spam this warning every time
628 we tried to figure out which microdescriptors to download. Fixes
629 the third piece of bug 6404; fix on 0.2.3.18-rc.
632 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
633 change when the authority is deciding whether to accept a newly
634 uploaded descriptor. Implements ticket 6423.
635 - Add missing documentation for consensus and microdesc files.
636 Resolves ticket 6732.
639 Changes in version 0.2.2.38 - 2012-08-12
640 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
641 attack that could in theory leak path information.
644 - Avoid an uninitialized memory read when reading a vote or consensus
645 document that has an unrecognized flavor name. This read could
646 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
647 - Try to leak less information about what relays a client is
648 choosing to a side-channel attacker. Previously, a Tor client would
649 stop iterating through the list of available relays as soon as it
650 had chosen one, thus finishing a little earlier when it picked
651 a router earlier in the list. If an attacker can recover this
652 timing information (nontrivial but not proven to be impossible),
653 they could learn some coarse-grained information about which relays
654 a client was picking (middle nodes in particular are likelier to
655 be affected than exits). The timing attack might be mitigated by
656 other factors (see bug 6537 for some discussion), but it's best
657 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
660 Changes in version 0.2.3.20-rc - 2012-08-05
661 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
662 series. It fixes a pair of code security bugs and a potential anonymity
663 issue, updates our RPM spec files, and cleans up other smaller issues.
666 - Avoid read-from-freed-memory and double-free bugs that could occur
667 when a DNS request fails while launching it. Fixes bug 6480;
668 bugfix on 0.2.0.1-alpha.
669 - Avoid an uninitialized memory read when reading a vote or consensus
670 document that has an unrecognized flavor name. This read could
671 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
672 - Try to leak less information about what relays a client is
673 choosing to a side-channel attacker. Previously, a Tor client would
674 stop iterating through the list of available relays as soon as it
675 had chosen one, thus finishing a little earlier when it picked
676 a router earlier in the list. If an attacker can recover this
677 timing information (nontrivial but not proven to be impossible),
678 they could learn some coarse-grained information about which relays
679 a client was picking (middle nodes in particular are likelier to
680 be affected than exits). The timing attack might be mitigated by
681 other factors (see bug 6537 for some discussion), but it's best
682 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
685 - Try to make the warning when giving an obsolete SOCKSListenAddress
686 a little more useful.
687 - Terminate active server managed proxies if Tor stops being a
688 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
689 - Provide a better error message about possible OSX Asciidoc failure
690 reasons. Fixes bug 6436.
691 - Warn when Tor is configured to use accounting in a way that can
692 link a hidden service to some other hidden service or public
693 address. Resolves ticket 6490.
696 - Check return value of fputs() when writing authority certificate
697 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
698 - Ignore ServerTransportPlugin lines when Tor is not configured as
699 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
700 - When disabling guards for having too high a proportion of failed
701 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
705 - Update our default RPM spec files to work with mock and rpmbuild
706 on RHEL/Fedora. They have an updated set of dependencies and
707 conflicts, a fix for an ancient typo when creating the "_tor"
708 user, and better instructions. Thanks to Ondrej Mikle for the
709 patch series. Fixes bug 6043.
712 - Make it possible to set the TestingTorNetwork configuration
713 option using AlternateDirAuthority and AlternateBridgeAuthority
714 as an alternative to setting DirServer. Addresses ticket 6377.
717 - Clarify the documentation for the Alternate*Authority options.
719 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
721 o Code simplification and refactoring:
722 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
723 10 lines. Also, don't nest them. Doing so in the past has
724 led to hard-to-debug code. The new style is to use the
725 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
728 Changes in version 0.2.3.19-rc - 2012-07-06
729 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
730 series. It fixes the compile on Windows, reverts to a GeoIP database
731 that isn't as broken, and fixes a flow control bug that has been around
732 since the beginning of Tor.
735 - Fix a bug handling SENDME cells on nonexistent streams that could
736 result in bizarre window values. Report and patch contributed
737 pseudonymously. Fixes part of bug 6271. This bug was introduced
738 before the first Tor release, in svn commit r152.
739 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
740 June 2012 database, Maxmind marked many Tor relays as country "A1",
741 which will cause risky behavior for clients that set EntryNodes
742 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
743 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
744 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
747 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
748 bugfix on 0.2.1.10-alpha.
751 Changes in version 0.2.3.18-rc - 2012-06-28
752 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
753 series. It fixes a few smaller bugs, but generally appears stable.
754 Please test it and let us know whether it is!
757 - Allow wildcarded mapaddress targets to be specified on the
758 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
759 - Make our linker option detection code more robust against linkers
760 such as on FreeBSD 8, where a bad combination of options completes
761 successfully but makes an unrunnable binary. Fixes bug 6173;
762 bugfix on 0.2.3.17-beta.
764 o Minor bugfixes (on 0.2.2.x and earlier):
765 - Avoid a false positive in the util/threads unit test by increasing
766 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
767 - Replace "Sending publish request" log messages with "Launching
768 upload", so that they no longer confusingly imply that we're
769 sending something to a directory we might not even be connected
770 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
771 - Make sure to set *socket_error in all error cases in
772 connection_connect(), so it can't produce a warning about
773 errno being zero from errno_to_orconn_end_reason(). Bugfix on
774 0.2.1.1-alpha; resolves ticket 6028.
775 - Downgrade "Got a certificate, but we already have it" log messages
776 from warning to info, except when we're a dirauth. Fixes bug 5238;
777 bugfix on 0.2.1.7-alpha.
778 - When checking for requested signatures on the latest consensus
779 before serving it to a client, make sure to check the right
780 consensus flavor. Bugfix on 0.2.2.6-alpha.
781 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
782 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
784 o Minor bugfixes (on 0.2.3.x):
785 - Make format_helper_exit_status() avoid unnecessary space padding
786 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
788 - Downgrade a message about cleaning the microdescriptor cache to
789 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
790 - Log a BUG message at severity INFO if we have a networkstatus with
791 a missing entry for some microdescriptor. Continues on a patch
793 - Improve the log message when a managed proxy fails to launch. Fixes
794 bug 5099; bugfix on 0.2.3.6-alpha.
795 - Don't do DNS lookups when parsing corrupted managed proxy protocol
796 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
797 - When formatting wildcarded address mappings for the controller,
798 be sure to include "*." as appropriate. Partially fixes bug 6244;
799 bugfix on 0.2.3.9-alpha.
800 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
801 Bugfix on 0.2.3.13-alpha.
802 - Stop logging messages about running with circuit timeout learning
803 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
804 - Disable a spurious warning about reading on a marked and flushing
805 connection. We shouldn't be doing that, but apparently we
806 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
807 - Fix a bug that stopped AllowDotExit from working on addresses
808 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
811 o Code simplification, refactoring, unit tests:
812 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
813 Libevent's notion of cached time when possible.
814 - Remove duplicate code for invoking getrlimit() from control.c.
815 - Add a unit test for the environment_variable_names_equal function.
818 - Document the --defaults-torrc option, and the new (in 0.2.3)
819 semantics for overriding, extending, and clearing lists of
820 options. Closes bug 4748.
823 Changes in version 0.2.3.17-beta - 2012-06-15
824 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
825 gets our TLS handshake back on track for being able to blend in with
826 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
827 with Vidalia, and otherwise continues to get us closer to a release
831 - Enable gcc and ld hardening by default. Resolves ticket 5210.
832 - Update TLS cipher list to match Firefox 8 and later. Resolves
834 - Implement the client side of proposal 198: remove support for
835 clients falsely claiming to support standard ciphersuites that
836 they can actually provide. As of modern OpenSSL versions, it's not
837 necessary to fake any standard ciphersuite, and doing so prevents
838 us from using better ciphersuites in the future, since servers
839 can't know whether an advertised ciphersuite is really supported or
840 not. Some hosts -- notably, ones with very old versions of OpenSSL
841 or where OpenSSL has been built with ECC disabled -- will stand
842 out because of this change; TBB users should not be affected.
845 - Change the default value for DynamicDHGroups (introduced in
846 0.2.3.9-alpha) to 0. This feature can make Tor relays less
847 identifiable by their use of the mod_ssl DH group, but at
848 the cost of some usability (#4721) and bridge tracing (#6087)
849 regressions. Resolves ticket 5598.
850 - Send a CRLF at the end of each STATUS_* control protocol event. This
851 bug tickled a bug in Vidalia which would make it freeze. Fixes
852 bug 6094; bugfix on 0.2.3.16-alpha.
855 - Disable writing on marked-for-close connections when they are
856 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
857 bug 5263; bugfix on 0.0.2pre13, where we first added a special
858 case for flushing marked connections.
859 - Detect SSL handshake even when the initial attempt to write the
860 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
861 - Change the AllowDotExit rules so they should actually work.
862 We now enforce AllowDotExit only immediately after receiving an
863 address via SOCKS or DNSPort: other sources are free to provide
864 .exit addresses after the resolution occurs. Fixes bug 3940;
865 bugfix on 0.2.2.1-alpha.
866 - Fix a (harmless) integer overflow in cell statistics reported by
867 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
868 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
869 right places and never depends on the consensus parameters or
870 computes adaptive timeouts when it is disabled. Fixes bug 5049;
871 bugfix on 0.2.2.14-alpha.
872 - When building Tor on Windows with -DUNICODE (not default), ensure
873 that error messages, filenames, and DNS server names are always
874 NUL-terminated when we convert them to a single-byte encoding.
875 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
876 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
877 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
878 - Fix an edge case where TestingTorNetwork is set but the authorities
879 and relays all have an uptime of zero, where the private Tor network
880 could briefly lack support for hidden services. Fixes bug 3886;
881 bugfix on 0.2.2.18-alpha.
882 - Correct the manpage's descriptions for the default values of
883 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
885 - Fix the documentation for the --hush and --quiet command line
886 options, which changed their behavior back in 0.2.3.3-alpha.
887 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
891 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
892 more information to it, so that we can track it down in case it
893 returns again. Mitigates bug 5235.
894 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
895 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
896 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
897 - Warn the user when HTTPProxy, but no other proxy type, is
898 configured. This can cause surprising behavior: it doesn't send
899 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
900 directory traffic only. Resolves ticket 4663.
901 - Issue a notice if a guard completes less than 40% of your circuits.
902 Threshold is configurable by torrc option PathBiasNoticeRate and
903 consensus parameter pb_noticepct. There is additional, off-by-
904 default code to disable guards which fail too many circuits.
905 Addresses ticket 5458.
906 - Update to the June 6 2012 Maxmind GeoLite Country database.
908 o Code simplifications and refactoring:
909 - Remove validate_pluggable_transports_config(): its warning
910 message is now handled by connection_or_connect().
913 Changes in version 0.2.2.37 - 2012-06-06
914 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
915 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
919 - Work around a bug in OpenSSL that broke renegotiation with TLS
920 1.1 and TLS 1.2. Without this workaround, all attempts to speak
921 the v2 Tor connection protocol when both sides were using OpenSSL
922 1.0.1 would fail. Resolves ticket 6033.
923 - When waiting for a client to renegotiate, don't allow it to add
924 any bytes to the input buffer. This fixes a potential DoS issue.
925 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
926 - Fix an edge case where if we fetch or publish a hidden service
927 descriptor, we might build a 4-hop circuit and then use that circuit
928 for exiting afterwards -- even if the new last hop doesn't obey our
929 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
932 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
933 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
936 - Tell GCC and Clang to check for any errors in format strings passed
937 to the tor_v*(print|scan)f functions.
940 Changes in version 0.2.3.16-alpha - 2012-06-05
941 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
942 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
943 currently). It also fixes a variety of smaller bugs and other cleanups
944 that get us closer to a release candidate.
946 o Major bugfixes (general):
947 - Work around a bug in OpenSSL that broke renegotiation with TLS
948 1.1 and TLS 1.2. Without this workaround, all attempts to speak
949 the v2 Tor connection protocol when both sides were using OpenSSL
950 1.0.1 would fail. Resolves ticket 6033.
951 - When waiting for a client to renegotiate, don't allow it to add
952 any bytes to the input buffer. This fixes a potential DoS issue.
953 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
954 - Pass correct OR address to managed proxies (like obfsproxy),
955 even when ORListenAddress is used. Fixes bug 4865; bugfix on
957 - The advertised platform of a router now includes only its operating
958 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
959 service pack level (for Windows) or its CPU architecture (for Unix).
960 We also no longer include the "git-XYZ" tag in the version. Resolves
963 o Major bugfixes (clients):
964 - If we are unable to find any exit that supports our predicted ports,
965 stop calling them predicted, so that we don't loop and build
966 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
967 which introduced predicted ports.
968 - Fix an edge case where if we fetch or publish a hidden service
969 descriptor, we might build a 4-hop circuit and then use that circuit
970 for exiting afterwards -- even if the new last hop doesn't obey our
971 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
972 - Check at each new consensus whether our entry guards were picked
973 long enough ago that we should rotate them. Previously, we only
974 did this check at startup, which could lead to us holding a guard
975 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
976 - When fetching a bridge descriptor from a bridge authority,
977 always do so anonymously, whether we have been able to open
978 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
979 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
980 but we'll need to wait for bug 6010 before it's actually usable.
982 o Major bugfixes (directory authorities):
983 - When computing weight parameters, behave more robustly in the
984 presence of a bad bwweightscale value. Previously, the authorities
985 would crash if they agreed on a sufficiently broken weight_scale
986 value: now, they use a reasonable default and carry on. Partial
987 fix for 5786; bugfix on 0.2.2.17-alpha.
988 - Check more thoroughly to prevent a rogue authority from
989 double-voting on any consensus directory parameter. Previously,
990 authorities would crash in this case if the total number of
991 votes for any parameter exceeded the number of active voters,
992 but would let it pass otherwise. Partial fix for bug 5786; bugfix
996 - Rate-limit log messages when asked to connect anonymously to
997 a private address. When these hit, they tended to hit fast and
998 often. Also, don't bother trying to connect to addresses that we
999 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
1000 reply makes us think we have been lied to, even when the address the
1001 client tried to connect to was "localhost." Resolves ticket 2822.
1002 - Allow packagers to insert an extra string in server descriptor
1003 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
1004 Resolves the rest of ticket 2988.
1005 - Raise the threshold of server descriptors needed (75%) and exit
1006 server descriptors needed (50%) before we will declare ourselves
1007 bootstrapped. This will make clients start building circuits a
1008 little later, but makes the initially constructed circuits less
1009 skewed and less in conflict with further directory fetches. Fixes
1011 - Close any connection that sends unrecognized junk before the
1012 handshake. Solves an issue noted in bug 4369.
1013 - Improve log messages about managed transports. Resolves ticket 5070.
1014 - Tag a bridge's descriptor as "never to be sent unencrypted".
1015 This shouldn't matter, since bridges don't open non-anonymous
1016 connections to the bridge authority and don't allow unencrypted
1017 directory connections from clients, but we might as well make
1018 sure. Closes bug 5139.
1019 - Expose our view of whether we have gone dormant to the controller,
1020 via a new "GETINFO dormant" value. Torbutton and other controllers
1021 can use this to avoid doing periodic requests through Tor while
1022 it's dormant (bug 4718). Fixes bug 5954.
1023 - Tell GCC and Clang to check for any errors in format strings passed
1024 to the tor_v*(print|scan)f functions.
1025 - Update to the May 1 2012 Maxmind GeoLite Country database.
1027 o Minor bugfixes (already included in 0.2.2.36):
1028 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
1029 Fixes bug 5346; bugfix on 0.0.8pre3.
1030 - Correct parsing of certain date types in parse_http_time().
1031 Without this patch, If-Modified-Since would behave
1032 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
1033 Esteban Manchado Velázques.
1034 - Make our number-parsing functions always treat too-large values
1035 as an error, even when those values exceed the width of the
1036 underlying type. Previously, if the caller provided these
1037 functions with minima or maxima set to the extreme values of the
1038 underlying integer type, these functions would return those
1039 values on overflow rather than treating overflow as an error.
1040 Fixes part of bug 5786; bugfix on 0.0.9.
1041 - If we hit the error case where routerlist_insert() replaces an
1042 existing (old) server descriptor, make sure to remove that
1043 server descriptor from the old_routers list. Fix related to bug
1044 1776. Bugfix on 0.2.2.18-alpha.
1045 - Clarify the behavior of MaxCircuitDirtiness with hidden service
1046 circuits. Fixes issue 5259.
1048 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
1049 - Prevent a null-pointer dereference when receiving a data cell
1050 for a nonexistent stream when the circuit in question has an
1051 empty deliver window. We don't believe this is triggerable,
1052 since we don't currently allow deliver windows to become empty,
1053 but the logic is tricky enough that it's better to make the code
1054 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
1055 - Fix a memory leak when trying to launch a DNS request when the
1056 network is disabled or the nameservers are unconfigurable. Fixes
1057 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
1058 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
1059 - Don't hold a Windows file handle open for every file mapping;
1060 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
1062 - Avoid O(n^2) performance characteristics when parsing a large
1063 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
1064 - Format more doubles with %f, not %lf. Patch from grarpamp to make
1065 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
1067 - Make our replacement implementation of strtok_r() compatible with
1068 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
1069 bugfix on 0.2.2.1-alpha.
1070 - Fix a NULL-pointer dereference on a badly formed
1071 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
1072 bugfix on 0.2.2.9-alpha.
1073 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
1074 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
1075 - Defensively refactor rend_mid_rendezvous() so that protocol
1076 violations and length checks happen in the beginning. Fixes
1078 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
1079 that IPv6 stuff will compile on MSVC, and compilation issues
1080 will be easier to track down. Fixes bug 5861.
1082 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
1083 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
1084 resource exhaustion, so that clients can adjust their load to
1085 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
1086 started using END_STREAM_REASON_RESOURCELIMIT.
1087 - Don't check for whether the address we're using for outbound
1088 connections has changed until after the outbound connection has
1089 completed. On Windows, getsockname() doesn't succeed until the
1090 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
1091 - If the configuration tries to set MyFamily on a bridge, refuse to
1092 do so, and warn about the security implications. Fixes bug 4657;
1093 bugfix on 0.2.0.3-alpha.
1094 - If the client fails to set a reasonable set of ciphersuites
1095 during its v2 handshake renegotiation, allow the renegotiation to
1096 continue nevertheless (i.e. send all the required certificates).
1097 Fixes bug 4591; bugfix on 0.2.0.20-rc.
1098 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
1099 option is set to 0 (which Vidalia version 0.2.16 now does when
1100 a SAVECONF attempt fails), perform other actions that SIGHUP
1101 usually causes (like reopening the logs). Fixes bug 5095; bugfix
1103 - If we fail to write a microdescriptor to the disk cache, do not
1104 continue replacing the old microdescriptor file. Fixes bug 2954;
1105 bugfix on 0.2.2.6-alpha.
1106 - Exit nodes don't need to fetch certificates for authorities that
1107 they don't recognize; only directory authorities, bridges,
1108 and caches need to do that. Fixes part of bug 2297; bugfix on
1110 - Correctly handle checking the permissions on the parent
1111 directory of a control socket in the root directory. Bug found
1112 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
1114 - When told to add a bridge with the same digest as a preexisting
1115 bridge but a different addr:port, change the addr:port as
1116 requested. Previously we would not notice the change. Fixes half
1117 of bug 5603; fix on 0.2.2.26-beta.
1118 - End AUTHCHALLENGE error messages (in the control protocol) with
1119 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
1121 o Minor bugfixes (on 0.2.3.x):
1122 - Turn an assertion (that the number of handshakes received as a
1123 server is not < 1) into a warning. Fixes bug 4873; bugfix on
1125 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
1126 we had reversed them when the answer was cached.) Fixes bug
1127 5723; bugfix on 0.2.3.1-alpha.
1128 - Work correctly on Linux systems with accept4 support advertised in
1129 their headers, but without accept4 support in the kernel. Fix
1130 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
1131 - When told to add a bridge with the same addr:port as a preexisting
1132 bridge but a different transport, change the transport as
1133 requested. Previously we would not notice the change. Fixes half
1134 of bug 5603; fix on 0.2.3.2-alpha.
1135 - Avoid a "double-reply" warning when replying to a SOCKS request
1136 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
1137 bugfix on 0.2.3.4-alpha.
1138 - Fix a bug where a bridge authority crashes if it has seen no
1139 directory requests when it's time to write statistics to disk.
1140 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
1142 - Don't try to open non-control listeners when DisableNetwork is set.
1143 Previously, we'd open all listeners, then immediately close them.
1144 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
1145 - Don't abort the managed proxy protocol if the managed proxy
1146 sends us an unrecognized line; ignore it instead. Fixes bug
1147 5910; bugfix on 0.2.3.9-alpha.
1148 - Fix a compile warning in crypto.c when compiling with clang 3.1.
1149 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
1150 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
1151 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
1152 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
1153 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
1154 - Resolve numerous small warnings and build issues with MSVC. Resolves
1157 o Documentation fixes:
1158 - Improve the manual's documentation for the NT Service command-line
1159 options. Addresses ticket 3964.
1160 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
1161 - Document the changes to the ORPort and DirPort options, and the
1162 fact that {OR/Dir}ListenAddress is now unnecessary (and
1163 therefore deprecated). Resolves ticket 5597.
1166 - Remove the torrc.bridge file: we don't use it for anything, and
1167 it had become badly desynchronized from torrc.sample. Resolves
1171 Changes in version 0.2.2.36 - 2012-05-24
1172 Tor 0.2.2.36 updates the addresses for two of the eight directory
1173 authorities, fixes some potential anonymity and security issues,
1174 and fixes several crash bugs.
1176 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
1177 known flaws, and nobody should be using them. You should upgrade. If
1178 you're using a Linux or BSD and its packages are obsolete, stop using
1179 those packages and upgrade anyway.
1181 o Directory authority changes:
1182 - Change IP address for maatuska (v3 directory authority).
1183 - Change IP address for ides (v3 directory authority), and rename
1187 - When building or running with any version of OpenSSL earlier
1188 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
1189 versions have a bug (CVE-2011-4576) in which their block cipher
1190 padding includes uninitialized data, potentially leaking sensitive
1191 information to any peer with whom they make a SSLv3 connection. Tor
1192 does not use SSL v3 by default, but a hostile client or server
1193 could force an SSLv3 connection in order to gain information that
1194 they shouldn't have been able to get. The best solution here is to
1195 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
1196 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
1197 to make sure that the bug can't happen.
1198 - Never use a bridge or a controller-supplied node as an exit, even
1199 if its exit policy allows it. Found by wanoskarnet. Fixes bug
1200 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
1201 and 0.2.0.3-alpha (for bridge-purpose descriptors).
1202 - Only build circuits if we have a sufficient threshold of the total
1203 descriptors that are marked in the consensus with the "Exit"
1204 flag. This mitigates an attack proposed by wanoskarnet, in which
1205 all of a client's bridges collude to restrict the exit nodes that
1206 the client knows about. Fixes bug 5343.
1207 - Provide controllers with a safer way to implement the cookie
1208 authentication mechanism. With the old method, if another locally
1209 running program could convince a controller that it was the Tor
1210 process, then that program could trick the controller into telling
1211 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
1212 authentication method uses a challenge-response approach to prevent
1213 this attack. Fixes bug 5185; implements proposal 193.
1216 - Avoid logging uninitialized data when unable to decode a hidden
1217 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
1218 - Avoid a client-side assertion failure when receiving an INTRODUCE2
1219 cell on a general purpose circuit. Fixes bug 5644; bugfix on
1221 - Fix builds when the path to sed, openssl, or sha1sum contains
1222 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
1224 - Correct our replacements for the timeradd() and timersub() functions
1225 on platforms that lack them (for example, Windows). The timersub()
1226 function is used when expiring circuits, while timeradd() is
1227 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
1228 bugfix on 0.2.2.24-alpha.
1229 - Fix the SOCKET_OK test that we use to tell when socket
1230 creation fails so that it works on Win64. Fixes part of bug 4533;
1231 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
1234 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
1235 Fixes bug 5346; bugfix on 0.0.8pre3.
1236 - Make our number-parsing functions always treat too-large values
1237 as an error, even when those values exceed the width of the
1238 underlying type. Previously, if the caller provided these
1239 functions with minima or maxima set to the extreme values of the
1240 underlying integer type, these functions would return those
1241 values on overflow rather than treating overflow as an error.
1242 Fixes part of bug 5786; bugfix on 0.0.9.
1243 - Older Linux kernels erroneously respond to strange nmap behavior
1244 by having accept() return successfully with a zero-length
1245 socket. When this happens, just close the connection. Previously,
1246 we would try harder to learn the remote address: but there was
1247 no such remote address to learn, and our method for trying to
1248 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
1249 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
1250 - Correct parsing of certain date types in parse_http_time().
1251 Without this patch, If-Modified-Since would behave
1252 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
1253 Esteban Manchado Velázques.
1254 - Change the BridgePassword feature (part of the "bridge community"
1255 design, which is not yet implemented) to use a time-independent
1256 comparison. The old behavior might have allowed an adversary
1257 to use timing to guess the BridgePassword value. Fixes bug 5543;
1258 bugfix on 0.2.0.14-alpha.
1259 - Detect and reject certain misformed escape sequences in
1260 configuration values. Previously, these values would cause us
1261 to crash if received in a torrc file or over an authenticated
1262 control port. Bug found by Esteban Manchado Velázquez, and
1263 independently by Robert Connolly from Matta Consulting who further
1264 noted that it allows a post-authentication heap overflow. Patch
1265 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
1266 bugfix on 0.2.0.16-alpha.
1267 - Fix a compile warning when using the --enable-openbsd-malloc
1268 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
1269 - During configure, detect when we're building with clang version
1270 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
1271 CFLAGS. clang doesn't support them yet.
1272 - When sending an HTTP/1.1 proxy request, include a Host header.
1273 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
1274 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
1275 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
1276 - If we hit the error case where routerlist_insert() replaces an
1277 existing (old) server descriptor, make sure to remove that
1278 server descriptor from the old_routers list. Fix related to bug
1279 1776. Bugfix on 0.2.2.18-alpha.
1281 o Minor bugfixes (documentation and log messages):
1282 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
1283 Fixes bug 4856; bugfix on Tor 0.0.6.
1284 - Update "ClientOnly" man page entry to explain that there isn't
1285 really any point to messing with it. Resolves ticket 5005.
1286 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
1287 directory authority option (introduced in Tor 0.2.2.34).
1288 - Downgrade the "We're missing a certificate" message from notice
1289 to info: people kept mistaking it for a real problem, whereas it
1290 is seldom the problem even when we are failing to bootstrap. Fixes
1291 bug 5067; bugfix on 0.2.0.10-alpha.
1292 - Correctly spell "connect" in a log message on failure to create a
1293 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
1294 - Clarify the behavior of MaxCircuitDirtiness with hidden service
1295 circuits. Fixes issue 5259.
1298 - Directory authorities now reject versions of Tor older than
1299 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
1300 inclusive. These versions accounted for only a small fraction of
1301 the Tor network, and have numerous known security issues. Resolves
1303 - Update to the May 1 2012 Maxmind GeoLite Country database.
1306 - When sending or relaying a RELAY_EARLY cell, we used to convert
1307 it to a RELAY cell if the connection was using the v1 link
1308 protocol. This was a workaround for older versions of Tor, which
1309 didn't handle RELAY_EARLY cells properly. Now that all supported
1310 versions can handle RELAY_EARLY cells, and now that we're enforcing
1311 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
1312 remove this workaround. Addresses bug 4786.
1315 Changes in version 0.2.3.15-alpha - 2012-04-30
1316 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
1317 the development branch build on Windows again.
1319 o Minor bugfixes (on 0.2.2.x and earlier):
1320 - Make sure that there are no unhandled pending TLS errors before
1321 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
1322 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
1323 Bugfix on 0.1.0.5-rc; fixes bug 4528.
1324 - Fix an assert that directory authorities could trigger on sighup
1325 during some configuration state transitions. We now don't treat
1326 it as a fatal error when the new descriptor we just generated in
1327 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
1328 - After we pick a directory mirror, we would refuse to use it if
1329 it's in our ExcludeExitNodes list, resulting in mysterious failures
1330 to bootstrap for people who just wanted to avoid exiting from
1331 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
1332 - When building with --enable-static-tor on OpenBSD, do not
1333 erroneously attempt to link -lrt. Fixes bug 5103.
1335 o Minor bugfixes (on 0.2.3.x):
1336 - When Tor is built with kernel headers from a recent (last few
1337 years) Linux kernel, do not fail to run on older (pre-2.6.28
1338 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
1339 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
1341 - Fix compilation with miniupnpc version 1.6; patch from
1342 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
1343 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
1344 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
1345 - Fix compilation on platforms without unistd.h, or where environ
1346 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
1349 - Directory authorities are now a little more lenient at accepting
1350 older router descriptors, or newer router descriptors that don't
1351 make big changes. This should help ameliorate past and future
1352 issues where routers think they have uploaded valid descriptors,
1353 but the authorities don't think so. Fix for ticket 2479.
1354 - Make the code that clients use to detect an address change be
1355 IPv6-aware, so that it won't fill clients' logs with error
1356 messages when trying to get the IPv4 address of an IPv6
1357 connection. Implements ticket 5537.
1360 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
1361 authorities needed to use it for a while to keep the network working
1362 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
1363 that was six months ago. As of now, it should no longer be needed
1367 Changes in version 0.2.3.14-alpha - 2012-04-23
1368 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
1369 candidate. It also dramatically speeds up AES: fast relays should
1370 consider switching to the newer OpenSSL library.
1372 o Directory authority changes:
1373 - Change IP address for ides (v3 directory authority), and rename
1377 - Avoid logging uninitialized data when unable to decode a hidden
1378 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
1379 - Avoid a client-side assertion failure when receiving an INTRODUCE2
1380 cell on a general purpose circuit. Fixes bug 5644; bugfix on
1382 - If authorities are unable to get a v2 consensus document from other
1383 directory authorities, they no longer fall back to fetching
1384 them from regular directory caches. Fixes bug 5635; bugfix on
1385 0.2.2.26-beta, where routers stopped downloading v2 consensus
1387 - When we start a Tor client with a normal consensus already cached,
1388 be willing to download a microdescriptor consensus. Fixes bug 4011;
1389 fix on 0.2.3.1-alpha.
1391 o Major features (performance):
1392 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
1393 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
1394 vectorized AES implementations as appropriate. These can be much,
1395 much faster than other AES implementations.
1397 o Minor bugfixes (0.2.2.x and earlier):
1398 - Don't launch more than 10 service-side introduction-point circuits
1399 for a hidden service in five minutes. Previously, we would consider
1400 launching more introduction-point circuits if at least one second
1401 had passed without any introduction-point circuits failing. Fixes
1402 bug 4607; bugfix on 0.0.7pre1.
1403 - Change the BridgePassword feature (part of the "bridge community"
1404 design, which is not yet implemented) to use a time-independent
1405 comparison. The old behavior might have allowed an adversary
1406 to use timing to guess the BridgePassword value. Fixes bug 5543;
1407 bugfix on 0.2.0.14-alpha.
1408 - Enforce correct return behavior of tor_vsscanf() when the '%%'
1409 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
1410 - When sending an HTTP/1.1 proxy request, include a Host header.
1411 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
1412 - Don't log that we have "decided to publish new relay descriptor"
1413 unless we are actually publishing a descriptor. Fixes bug 3942;
1414 bugfix on 0.2.2.28-beta.
1416 o Minor bugfixes (0.2.3.x):
1417 - Fix a bug where a bridge authority crashes (on a failed assert)
1418 if it has seen no directory requests when it's time to write
1419 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
1420 - Fix bug stomping on ORPort option NoListen and ignoring option
1421 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
1422 - In the testsuite, provide a large enough buffer in the tor_sscanf
1423 unit test. Otherwise we'd overrun that buffer and crash during
1424 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
1426 - Make sure we create the keys directory if it doesn't exist and we're
1427 about to store the dynamic Diffie-Hellman parameters. Fixes bug
1428 5572; bugfix on 0.2.3.13-alpha.
1429 - Fix a small memory leak when trying to decode incorrect base16
1430 authenticator during SAFECOOKIE authentication. Found by
1431 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
1434 - Add more information to a log statement that might help track down
1435 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
1436 non-IP address" messages (or any Bug messages, for that matter!),
1437 please let us know about it.
1438 - Relays now understand an IPv6 address when they get one from a
1439 directory server. Resolves ticket 4875.
1440 - Resolve IPv6 addresses in bridge and entry statistics to country
1441 code "??" which means we at least count them. Resolves ticket 5053;
1442 improves on 0.2.3.9-alpha.
1443 - Update to the April 3 2012 Maxmind GeoLite Country database.
1444 - Begin a doc/state-contents.txt file to explain the contents of
1445 the Tor state file. Fixes bug 2987.
1447 o Default torrc changes:
1448 - Stop listing "socksport 9050" in torrc.sample. We open a socks
1449 port on 9050 by default anyway, so this should not change anything
1451 - Stop mentioning the deprecated *ListenAddress options in
1452 torrc.sample. Fixes bug 5438.
1453 - Document unit of bandwidth related options in sample torrc.
1457 - The "torify" script no longer supports the "tsocks" socksifier
1458 tool, since tsocks doesn't support DNS and UDP right for Tor.
1459 Everyone should be using torsocks instead. Fixes bugs 3530 and
1460 5180. Based on a patch by "ugh".
1463 - Change the symmetric cipher interface so that creating and
1464 initializing a stream cipher are no longer separate functions.
1465 - Remove all internal support for unpadded RSA. We never used it, and
1466 it would be a bad idea to start.
1469 Changes in version 0.2.3.13-alpha - 2012-03-26
1470 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
1471 in managed pluggable transports, as well as providing other cleanups
1472 that get us closer to a release candidate.
1474 o Directory authority changes:
1475 - Change IP address for maatuska (v3 directory authority).
1478 - Provide controllers with a safer way to implement the cookie
1479 authentication mechanism. With the old method, if another locally
1480 running program could convince a controller that it was the Tor
1481 process, then that program could trick the controller into telling
1482 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
1483 authentication method uses a challenge-response approach to prevent
1484 this attack. Fixes bug 5185, implements proposal 193.
1485 - Never use a bridge or a controller-supplied node as an exit, even
1486 if its exit policy allows it. Found by wanoskarnet. Fixes bug
1487 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
1488 and 0.2.0.3-alpha (for bridge-purpose descriptors).
1489 - Only build circuits if we have a sufficient threshold of the total
1490 descriptors that are marked in the consensus with the "Exit"
1491 flag. This mitigates an attack proposed by wanoskarnet, in which
1492 all of a client's bridges collude to restrict the exit nodes that
1493 the client knows about. Fixes bug 5343.
1495 o Major bugfixes (on Tor 0.2.3.x):
1496 - Avoid an assert when managed proxies like obfsproxy are configured,
1497 and we receive HUP signals or setconf attempts too rapidly. This
1498 situation happens most commonly when Vidalia tries to attach to
1499 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
1500 bugfix on 0.2.3.6-alpha.
1501 - Fix a relay-side pluggable transports bug where managed proxies were
1502 unreachable from the Internet, because Tor asked them to bind on
1503 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
1504 - Stop discarding command-line arguments when TestingTorNetwork
1505 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
1506 0.2.3.9-alpha, where task 4552 added support for two layers of
1508 - Resume allowing the unit tests to run in gdb. This was accidentally
1509 made impossible when the DisableDebuggerAttachment option was
1510 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
1511 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
1512 0.2.3.11-alpha. Reported by Anthony G. Basile.
1514 o Minor bugfixes (on 0.2.2.x and earlier):
1515 - Ensure we don't cannibalize circuits that are longer than three hops
1516 already, so we don't end up making circuits with 5 or more
1517 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
1518 0.1.0.1-rc which introduced cannibalization.
1519 - Detect and reject certain misformed escape sequences in
1520 configuration values. Previously, these values would cause us
1521 to crash if received in a torrc file or over an authenticated
1522 control port. Bug found by Esteban Manchado Velázquez, and
1523 independently by Robert Connolly from Matta Consulting who further
1524 noted that it allows a post-authentication heap overflow. Patch
1525 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
1526 bugfix on 0.2.0.16-alpha.
1527 - Fix a compile warning when using the --enable-openbsd-malloc
1528 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
1529 - Directory caches no longer refuse to clean out descriptors because
1530 of missing v2 networkstatus documents, unless they're configured
1531 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
1532 0.2.2.26-beta. Patch by Daniel Bryg.
1533 - Update to the latest version of the tinytest unit testing framework.
1534 This includes a couple of bugfixes that can be relevant for
1535 running forked unit tests on Windows, and removes all reserved
1538 o Minor bugfixes (on 0.2.3.x):
1539 - On a failed pipe() call, don't leak file descriptors. Fixes bug
1540 4296; bugfix on 0.2.3.1-alpha.
1541 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
1542 until after we have received a CERTS cell. Fixes bug 4361; bugfix
1543 on 0.2.3.6-alpha. Patch by "frosty".
1544 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
1545 option, so that the IP stack doesn't decide to use it for IPv4
1546 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
1547 - Ensure that variables set in Tor's environment cannot override
1548 environment variables that Tor passes to a managed
1549 pluggable-transport proxy. Previously, Tor would pass every
1550 variable in its environment to managed proxies along with the new
1551 ones, in such a way that on many operating systems, the inherited
1552 environment variables would override those which Tor tried to
1553 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
1554 bugfix on 0.2.3.9-alpha for Windows.
1557 - A wide variety of new unit tests by Esteban Manchado Velázquez.
1558 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
1559 - Update to the March 6 2012 Maxmind GeoLite Country database.
1562 Changes in version 0.2.3.12-alpha - 2012-02-13
1563 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
1564 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
1565 when Tor is configured to use a pluggable transport like obfsproxy.
1568 - Fix builds when the path to sed, openssl, or sha1sum contains
1569 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
1571 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
1572 connections. This change should allow busy exit relays to stop
1573 running out of available sockets as quickly. Fixes bug 4950;
1574 bugfix on 0.2.2.26-beta.
1575 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
1576 would ask the bridge for microdescriptors, which are only supported
1577 in 0.2.3.x, and then fail to bootstrap when it didn't get the
1578 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
1579 - Properly set up obfsproxy's environment when in managed mode. The
1580 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
1581 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
1582 5076 and 5082; bugfix on 0.2.3.6-alpha.
1585 - Use the dead_strip option when building Tor on OS X. This reduces
1586 binary size by almost 19% when linking openssl and libevent
1587 statically, which we do for Tor Browser Bundle.
1588 - Fix broken URLs in the sample torrc file, and tell readers about
1589 the OutboundBindAddress, ExitPolicyRejectPrivate, and
1590 PublishServerDescriptor options. Addresses bug 4652.
1591 - Update to the February 7 2012 Maxmind GeoLite Country database.
1594 - Downgrade the "We're missing a certificate" message from notice
1595 to info: people kept mistaking it for a real problem, whereas it
1596 is seldom the problem even when we are failing to bootstrap. Fixes
1597 bug 5067; bugfix on 0.2.0.10-alpha.
1598 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
1599 managed pluggable transport server proxy's environment.
1600 Previously, we would put it there, even though Tor doesn't
1601 implement an 'extended server port' yet, and even though Tor
1602 almost certainly isn't listening at that address. For now, we set
1603 it to an empty string to avoid crashing older obfsproxies. Bugfix
1605 - Log the heartbeat message every HeartbeatPeriod seconds, not every
1606 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
1607 0.2.3.1-alpha. Bug reported by Scott Bennett.
1608 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
1609 bugfix on 0.2.3.11-alpha.
1610 - Update "ClientOnly" man page entry to explain that there isn't
1611 really any point to messing with it. Resolves ticket 5005.
1612 - Use the correct CVE number for CVE-2011-4576 in our comments and
1613 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
1616 o Code simplifications and refactoring:
1617 - Use the _WIN32 macro throughout our code to detect Windows.
1618 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
1622 Changes in version 0.2.3.11-alpha - 2012-01-22
1623 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
1624 the last step of the plan to limit maximum circuit length, includes
1625 a wide variety of hidden service performance and correctness fixes,
1626 works around an OpenSSL security flaw if your distro is too stubborn
1627 to upgrade, and fixes a bunch of smaller issues.
1630 - Now that Tor 0.2.0.x is completely deprecated, enable the final
1631 part of "Proposal 110: Avoiding infinite length circuits" by
1632 refusing all circuit-extend requests that do not use a relay_early
1633 cell. This change helps Tor resist a class of denial-of-service
1634 attacks by limiting the maximum circuit length.
1635 - Adjust the number of introduction points that a hidden service
1636 will try to maintain based on how long its introduction points
1637 remain in use and how many introductions they handle. Fixes
1639 - Try to use system facilities for enumerating local interface
1640 addresses, before falling back to our old approach (which was
1641 binding a UDP socket, and calling getsockname() on it). That
1642 approach was scaring OS X users whose draconian firewall
1643 software warned about binding to UDP sockets, regardless of
1644 whether packets were sent. Now we try to use getifaddrs(),
1645 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
1646 system supports. Resolves ticket 1827.
1648 o Major security workaround:
1649 - When building or running with any version of OpenSSL earlier
1650 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
1651 versions have a bug (CVE-2011-4576) in which their block cipher
1652 padding includes uninitialized data, potentially leaking sensitive
1653 information to any peer with whom they make a SSLv3 connection. Tor
1654 does not use SSL v3 by default, but a hostile client or server
1655 could force an SSLv3 connection in order to gain information that
1656 they shouldn't have been able to get. The best solution here is to
1657 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
1658 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
1659 to make sure that the bug can't happen.
1662 - Fix the SOCKET_OK test that we use to tell when socket
1663 creation fails so that it works on Win64. Fixes part of bug 4533;
1664 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
1665 - Correct our replacements for the timeradd() and timersub() functions
1666 on platforms that lack them (for example, Windows). The timersub()
1667 function is used when expiring circuits, while timeradd() is
1668 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
1669 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
1670 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
1671 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
1672 bug at runtime, not compile time, because some distributions hack
1673 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
1674 on 0.2.3.9-alpha. Found by Pascal.
1676 o Minor features (controller):
1677 - Use absolute path names when reporting the torrc filename in the
1678 control protocol, so a controller can more easily find the torrc
1679 file. Resolves bug 1101.
1680 - Extend the control protocol to report flags that control a circuit's
1681 path selection in CIRC events and in replies to 'GETINFO
1682 circuit-status'. Implements part of ticket 2411.
1683 - Extend the control protocol to report the hidden service address
1684 and current state of a hidden-service-related circuit in CIRC
1685 events and in replies to 'GETINFO circuit-status'. Implements part
1687 - When reporting the path to the cookie file to the controller,
1688 give an absolute path. Resolves ticket 4881.
1689 - Allow controllers to request an event notification whenever a
1690 circuit is cannibalized or its purpose is changed. Implements
1691 part of ticket 3457.
1692 - Include the creation time of a circuit in CIRC and CIRC2
1693 control-port events and the list produced by the 'GETINFO
1694 circuit-status' control-port command.
1696 o Minor features (directory authorities):
1697 - Directory authorities now reject versions of Tor older than
1698 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
1699 inclusive. These versions accounted for only a small fraction of
1700 the Tor network, and have numerous known security issues. Resolves
1702 - Authority operators can now vote for all relays in a given
1703 set of countries to be BadDir/BadExit/Invalid/Rejected.
1704 - Provide two consensus parameters (FastFlagMinThreshold and
1705 FastFlagMaxThreshold) to control the range of allowable bandwidths
1706 for the Fast directory flag. These allow authorities to run
1707 experiments on appropriate requirements for being a "Fast" node.
1708 The AuthDirFastGuarantee config value still applies. Implements
1710 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
1711 directory authority option (introduced in Tor 0.2.2.34).
1713 o Minor features (other):
1714 - Don't disable the DirPort when we cannot exceed our AccountingMax
1715 limit during this interval because the effective bandwidthrate is
1716 low enough. This is useful in a situation where AccountMax is only
1717 used as an additional safeguard or to provide statistics.
1718 - Prepend an informative header to generated dynamic_dh_params files.
1719 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
1720 EntryNodes will have no effect. Resolves issue 2571.
1721 - Log more useful messages when we fail to disable debugger
1723 - Log which authority we're missing votes from when we go to fetch
1724 them from the other auths.
1725 - Log (at debug level) whenever a circuit's purpose is changed.
1726 - Add missing documentation for the MaxClientCircuitsPending,
1727 UseMicrodescriptors, UserspaceIOCPBuffers, and
1728 _UseFilteringSSLBufferevents options, all introduced during
1730 - Update to the January 3 2012 Maxmind GeoLite Country database.
1732 o Minor bugfixes (hidden services):
1733 - Don't close hidden service client circuits which have almost
1734 finished connecting to their destination when they reach
1735 the normal circuit-build timeout. Previously, we would close
1736 introduction circuits which are waiting for an acknowledgement
1737 from the introduction point, and rendezvous circuits which have
1738 been specified in an INTRODUCE1 cell sent to a hidden service,
1739 after the normal CBT. Now, we mark them as 'timed out', and launch
1740 another rendezvous attempt in parallel. This behavior change can
1741 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
1742 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
1743 - Don't close hidden-service-side rendezvous circuits when they
1744 reach the normal circuit-build timeout. This behaviour change can
1745 be disabled using the new
1746 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
1747 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
1748 - Make sure we never mark the wrong rendezvous circuit as having
1749 had its introduction cell acknowleged by the introduction-point
1750 relay. Previously, when we received an INTRODUCE_ACK cell on a
1751 client-side hidden-service introduction circuit, we might have
1752 marked a rendezvous circuit other than the one we specified in
1753 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
1754 a warning message and interfered with the hidden service
1755 connection-establishment process. Fixes bug 4759; bugfix on
1756 0.2.3.3-alpha, when we added the stream-isolation feature which
1757 might cause Tor to open multiple rendezvous circuits for the same
1759 - Don't trigger an assertion failure when we mark a new client-side
1760 hidden-service introduction circuit for close during the process
1761 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
1764 o Minor bugfixes (log messages):
1765 - Correctly spell "connect" in a log message on failure to create a
1766 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
1768 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
1769 Fixes bug 4856; bugfix on Tor 0.0.6.
1770 - Fix the log message describing how we work around discovering
1771 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
1772 4837; bugfix on 0.2.2.9-alpha.
1773 - When logging about a disallowed .exit name, do not also call it
1774 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
1776 o Minor bugfixes (build fixes):
1777 - During configure, detect when we're building with clang version
1778 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
1779 CFLAGS. clang doesn't support them yet.
1780 - During configure, search for library containing cos function as
1781 libm lives in libcore on some platforms (BeOS/Haiku). Linking
1782 against libm was hard-coded before. Fixes the first part of bug
1783 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
1785 - Detect attempts to build Tor on (as yet hypothetical) versions
1786 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
1787 fix for bug 4533. Bugfix on 0.2.2.28-beta.
1788 - Preprocessor directives should not be put inside the arguments
1789 of a macro. This would break compilation with GCC releases prior
1790 to version 3.3. We would never recommend such an old GCC version,
1791 but it is apparently required for binary compatibility on some
1792 platforms (namely, certain builds of Haiku). Fixes the other part
1793 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
1796 o Minor bugfixes (other):
1797 - Older Linux kernels erroneously respond to strange nmap behavior
1798 by having accept() return successfully with a zero-length
1799 socket. When this happens, just close the connection. Previously,
1800 we would try harder to learn the remote address: but there was
1801 no such remote address to learn, and our method for trying to
1802 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
1803 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
1804 - Fix null-pointer access that could occur if TLS allocation failed.
1805 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
1806 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
1807 accidentally been reverted.
1808 - Fix our implementation of crypto_random_hostname() so it can't
1809 overflow on ridiculously large inputs. (No Tor version has ever
1810 provided this kind of bad inputs, but let's be correct in depth.)
1811 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
1812 - Find more places in the code that should have been testing for
1813 invalid sockets using the SOCKET_OK macro. Required for a fix
1814 for bug 4533. Bugfix on 0.2.2.28-beta.
1815 - Fix an assertion failure when, while running with bufferevents, a
1816 connection finishes connecting after it is marked for close, but
1817 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
1818 - test_util_spawn_background_ok() hardcoded the expected value
1819 for ENOENT to 2. This isn't portable as error numbers are
1820 platform specific, and particularly the hurd has ENOENT at
1821 0x40000002. Construct expected string at runtime, using the correct
1822 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
1823 - Reject attempts to disable DisableDebuggerAttachment while Tor is
1824 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
1825 - Use an appropriate-width type for sockets in tor-fw-helper on
1826 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
1829 - When sending or relaying a RELAY_EARLY cell, we used to convert
1830 it to a RELAY cell if the connection was using the v1 link
1831 protocol. This was a workaround for older versions of Tor, which
1832 didn't handle RELAY_EARLY cells properly. Now that all supported
1833 versions can handle RELAY_EARLY cells, and now that we're enforcing
1834 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
1835 remove this workaround. Addresses bug 4786.
1837 o Code simplifications and refactoring:
1838 - Use OpenSSL's built-in SSL_state_string_long() instead of our
1839 own homebrewed ssl_state_to_string() replacement. Patch from
1840 Emile Snyder. Fixes bug 4653.
1841 - Use macros to indicate OpenSSL versions, so we don't need to worry
1842 about accidental hexadecimal bit shifts.
1843 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
1845 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
1846 - Use the smartlist_add_asprintf() alias more consistently.
1847 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
1848 invalid value, rather than just -1.
1849 - Rename a handful of old identifiers, mostly related to crypto
1850 structures and crypto functions. By convention, our "create an
1851 object" functions are called "type_new()", our "free an object"
1852 functions are called "type_free()", and our types indicate that
1853 they are types only with a final "_t". But a handful of older
1854 types and functions broke these rules, with function names like
1855 "type_create" or "subsystem_op_type", or with type names like
1859 Changes in version 0.2.3.10-alpha - 2011-12-16
1860 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
1861 Tor's buffers code. Absolutely everybody should upgrade.
1863 The bug relied on an incorrect calculation when making data continuous
1864 in one of our IO buffers, if the first chunk of the buffer was
1865 misaligned by just the wrong amount. The miscalculation would allow an
1866 attacker to overflow a piece of heap-allocated memory. To mount this
1867 attack, the attacker would need to either open a SOCKS connection to
1868 Tor's SocksPort (usually restricted to localhost), or target a Tor
1869 instance configured to make its connections through a SOCKS proxy
1870 (which Tor does not do by default).
1872 Good security practice requires that all heap-overflow bugs should be
1873 presumed to be exploitable until proven otherwise, so we are treating
1874 this as a potential code execution attack. Please upgrade immediately!
1875 This bug does not affect bufferevents-based builds of Tor. Special
1876 thanks to "Vektor" for reporting this issue to us!
1878 This release also contains a few minor bugfixes for issues discovered
1882 - Fix a heap overflow bug that could occur when trying to pull
1883 data into the first chunk of a buffer, when that chunk had
1884 already had some data drained from it. Fixes CVE-2011-2778;
1885 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1888 - If we can't attach streams to a rendezvous circuit when we
1889 finish connecting to a hidden service, clear the rendezvous
1890 circuit's stream-isolation state and try to attach streams
1891 again. Previously, we cleared rendezvous circuits' isolation
1892 state either too early (if they were freshly built) or not at all
1893 (if they had been built earlier and were cannibalized). Bugfix on
1894 0.2.3.3-alpha; fixes bug 4655.
1895 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
1896 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
1897 - Fix an assertion failure when a relay with accounting enabled
1898 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
1901 - Update to the December 6 2011 Maxmind GeoLite Country database.
1904 Changes in version 0.2.2.35 - 2011-12-16
1905 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
1906 buffers code. Absolutely everybody should upgrade.
1908 The bug relied on an incorrect calculation when making data continuous
1909 in one of our IO buffers, if the first chunk of the buffer was
1910 misaligned by just the wrong amount. The miscalculation would allow an
1911 attacker to overflow a piece of heap-allocated memory. To mount this
1912 attack, the attacker would need to either open a SOCKS connection to
1913 Tor's SocksPort (usually restricted to localhost), or target a Tor
1914 instance configured to make its connections through a SOCKS proxy
1915 (which Tor does not do by default).
1917 Good security practice requires that all heap-overflow bugs should be
1918 presumed to be exploitable until proven otherwise, so we are treating
1919 this as a potential code execution attack. Please upgrade immediately!
1920 This bug does not affect bufferevents-based builds of Tor. Special
1921 thanks to "Vektor" for reporting this issue to us!
1923 Tor 0.2.2.35 also fixes several bugs in previous versions, including
1924 crash bugs for unusual configurations, and a long-term bug that
1925 would prevent Tor from starting on Windows machines with draconian
1928 With this release, we remind everyone that 0.2.0.x has reached its
1929 formal end-of-life. Those Tor versions have many known flaws, and
1930 nobody should be using them. You should upgrade -- ideally to the
1931 0.2.2.x series. If you're using a Linux or BSD and its packages are
1932 obsolete, stop using those packages and upgrade anyway.
1934 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
1935 longer receive support after some time in early 2012.
1938 - Fix a heap overflow bug that could occur when trying to pull
1939 data into the first chunk of a buffer, when that chunk had
1940 already had some data drained from it. Fixes CVE-2011-2778;
1941 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1942 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
1943 that it doesn't attempt to allocate a socketpair. This could cause
1944 some problems on Windows systems with overzealous firewalls. Fix for
1945 bug 4457; workaround for Libevent versions 2.0.1-alpha through
1947 - If we mark an OR connection for close based on a cell we process,
1948 don't process any further cells on it. We already avoid further
1949 reads on marked-for-close connections, but now we also discard the
1950 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
1951 which was the first version where we might mark a connection for
1952 close based on processing a cell on it.
1953 - Correctly sanity-check that we don't underflow on a memory
1954 allocation (and then assert) for hidden service introduction
1955 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1956 bugfix on 0.2.1.5-alpha.
1957 - Fix a memory leak when we check whether a hidden service
1958 descriptor has any usable introduction points left. Fixes bug
1959 4424. Bugfix on 0.2.2.25-alpha.
1960 - Don't crash when we're running as a relay and don't have a GeoIP
1961 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
1962 we've had in the 0.2.3.x branch already.
1963 - When running as a client, do not print a misleading (and plain
1964 wrong) log message that we're collecting "directory request"
1965 statistics: clients don't collect statistics. Also don't create a
1966 useless (because empty) stats file in the stats/ directory. Fixes
1967 bug 4353; bugfix on 0.2.2.34.
1970 - Detect failure to initialize Libevent. This fix provides better
1971 detection for future instances of bug 4457.
1972 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
1973 function. This was eating up hideously large amounts of time on some
1974 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
1975 - Resolve an integer overflow bug in smartlist_ensure_capacity().
1976 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
1978 - Don't warn about unused log_mutex in log.c when building with
1979 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
1980 0.1.0.6-rc which introduced --disable-threads.
1981 - When configuring, starting, or stopping an NT service, stop
1982 immediately after the service configuration attempt has succeeded
1983 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
1984 - When sending a NETINFO cell, include the original address
1985 received for the other side, not its canonical address. Found
1986 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
1987 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
1988 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1989 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
1990 occurred when a client tried to fetch a descriptor for a bridge
1991 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
1992 - Backport fixes for a pair of compilation warnings on Windows.
1993 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
1994 - If we had ever tried to call tor_addr_to_str on an address of
1995 unknown type, we would have done a strdup on an uninitialized
1996 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
1997 Reported by "troll_un".
1998 - Correctly detect and handle transient lookup failures from
1999 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
2000 Reported by "troll_un".
2001 - Fix null-pointer access that could occur if TLS allocation failed.
2002 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
2003 - Use tor_socket_t type for listener argument to accept(). Fixes bug
2004 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
2007 - Add two new config options for directory authorities:
2008 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
2009 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
2010 that is always sufficient to satisfy the bandwidth requirement for
2011 the Guard flag. Now it will be easier for researchers to simulate
2012 Tor networks with different values. Resolves ticket 4484.
2013 - When Tor ignores a hidden service specified in its configuration,
2014 include the hidden service's directory in the warning message.
2015 Previously, we would only tell the user that some hidden service
2016 was ignored. Bugfix on 0.0.6; fixes bug 4426.
2017 - Update to the December 6 2011 Maxmind GeoLite Country database.
2019 o Packaging changes:
2020 - Make it easier to automate expert package builds on Windows,
2021 by removing an absolute path from makensis.exe command.
2024 Changes in version 0.2.1.32 - 2011-12-16
2025 Tor 0.2.1.32 backports important security and privacy fixes for
2026 oldstable. This release is intended only for package maintainers and
2027 others who cannot use the 0.2.2 stable series. All others should be
2028 using Tor 0.2.2.x or newer.
2030 The Tor 0.2.1.x series will reach formal end-of-life some time in
2031 early 2012; we will stop releasing patches for it then.
2033 o Major bugfixes (also included in 0.2.2.x):
2034 - Correctly sanity-check that we don't underflow on a memory
2035 allocation (and then assert) for hidden service introduction
2036 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2037 bugfix on 0.2.1.5-alpha.
2038 - Fix a heap overflow bug that could occur when trying to pull
2039 data into the first chunk of a buffer, when that chunk had
2040 already had some data drained from it. Fixes CVE-2011-2778;
2041 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
2044 - Update to the December 6 2011 Maxmind GeoLite Country database.
2047 Changes in version 0.2.3.9-alpha - 2011-12-08
2048 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
2049 a "DisableNetwork" security feature that bundles can use to avoid
2050 touching the network until bridges are configured, moves forward on
2051 the pluggable transport design, fixes a flaw in the hidden service
2052 design that unnecessarily prevented clients with wrong clocks from
2053 reaching hidden services, and fixes a wide variety of other issues.
2056 - Clients can now connect to private bridges over IPv6. Bridges
2057 still need at least one IPv4 address in order to connect to
2058 other relays. Note that we don't yet handle the case where the
2059 user has two bridge lines for the same bridge (one IPv4, one
2060 IPv6). Implements parts of proposal 186.
2061 - New "DisableNetwork" config option to prevent Tor from launching any
2062 connections or accepting any connections except on a control port.
2063 Bundles and controllers can set this option before letting Tor talk
2064 to the rest of the network, for example to prevent any connections
2065 to a non-bridge address. Packages like Orbot can also use this
2066 option to instruct Tor to save power when the network is off.
2067 - Clients and bridges can now be configured to use a separate
2068 "transport" proxy. This approach makes the censorship arms race
2069 easier by allowing bridges to use protocol obfuscation plugins. It
2070 implements the "managed proxy" part of proposal 180 (ticket 3472).
2071 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
2072 implementation. It makes AES_CTR about 7% faster than our old one
2073 (which was about 10% faster than the one OpenSSL used to provide).
2074 Resolves ticket 4526.
2075 - Add a "tor2web mode" for clients that want to connect to hidden
2076 services non-anonymously (and possibly more quickly). As a safety
2077 measure to try to keep users from turning this on without knowing
2078 what they are doing, tor2web mode must be explicitly enabled at
2079 compile time, and a copy of Tor compiled to run in tor2web mode
2080 cannot be used as a normal Tor client. Implements feature 2553.
2081 - Add experimental support for running on Windows with IOCP and no
2082 kernel-space socket buffers. This feature is controlled by a new
2083 "UserspaceIOCPBuffers" config option (off by default), which has
2084 no effect unless Tor has been built with support for bufferevents,
2085 is running on Windows, and has enabled IOCP. This may, in the long
2086 run, help solve or mitigate bug 98.
2087 - Use a more secure consensus parameter voting algorithm. Now at
2088 least three directory authorities or a majority of them must
2089 vote on a given parameter before it will be included in the
2090 consensus. Implements proposal 178.
2093 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
2094 They used to check that the timestamp was within 30 minutes
2095 of their system clock, so they could cap the size of their
2096 replay-detection cache, but that approach unnecessarily refused
2097 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
2098 the v3 intro-point protocol (the first one which sent a timestamp
2099 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
2100 - Only use the EVP interface when AES acceleration is enabled,
2101 to avoid a 5-7% performance regression. Resolves issue 4525;
2102 bugfix on 0.2.3.8-alpha.
2104 o Privacy/anonymity features (bridge detection):
2105 - Make bridge SSL certificates a bit more stealthy by using random
2106 serial numbers, in the same fashion as OpenSSL when generating
2107 self-signed certificates. Implements ticket 4584.
2108 - Introduce a new config option "DynamicDHGroups", enabled by
2109 default, which provides each bridge with a unique prime DH modulus
2110 to be used during SSL handshakes. This option attempts to help
2111 against censors who might use the Apache DH modulus as a static
2112 identifier for bridges. Addresses ticket 4548.
2114 o Minor features (new/different config options):
2115 - New configuration option "DisableDebuggerAttachment" (on by default)
2116 to prevent basic debugging attachment attempts by other processes.
2117 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
2118 - Allow MapAddress directives to specify matches against super-domains,
2119 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
2120 Implements issue 933.
2121 - Slightly change behavior of "list" options (that is, config
2122 options that can appear more than once) when they appear both in
2123 torrc and on the command line. Previously, the command-line options
2124 would be appended to the ones from torrc. Now, the command-line
2125 options override the torrc options entirely. This new behavior
2126 allows the user to override list options (like exit policies and
2127 ports to listen on) from the command line, rather than simply
2128 appending to the list.
2129 - You can get the old (appending) command-line behavior for "list"
2130 options by prefixing the option name with a "+".
2131 - You can remove all the values for a "list" option from the command
2132 line without adding any new ones by prefixing the option name
2134 - Add experimental support for a "defaults" torrc file to be parsed
2135 before the regular torrc. Torrc options override the defaults file's
2136 options in the same way that the command line overrides the torrc.
2137 The SAVECONF controller command saves only those options which
2138 differ between the current configuration and the defaults file. HUP
2139 reloads both files. (Note: This is an experimental feature; its
2140 behavior will probably be refined in future 0.2.3.x-alpha versions
2141 to better meet packagers' needs.) Implements task 4552.
2144 - Try to make the introductory warning message that Tor prints on
2145 startup more useful for actually finding help and information.
2146 Resolves ticket 2474.
2147 - Running "make version" now displays the version of Tor that
2148 we're about to build. Idea from katmagic; resolves issue 4400.
2149 - Expire old or over-used hidden service introduction points.
2150 Required by fix for bug 3460.
2151 - Move the replay-detection cache for the RSA-encrypted parts of
2152 INTRODUCE2 cells to the introduction point data structures.
2153 Previously, we would use one replay-detection cache per hidden
2154 service. Required by fix for bug 3460.
2155 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
2156 public key replay-detection cache from 60 minutes to 5 minutes. This
2157 replay-detection cache is now used only to detect multiple
2158 INTRODUCE2 cells specifying the same rendezvous point, so we can
2159 avoid launching multiple simultaneous attempts to connect to it.
2161 o Minor bugfixes (on Tor 0.2.2.x and earlier):
2162 - Resolve an integer overflow bug in smartlist_ensure_capacity().
2163 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
2165 - Fix a minor formatting issue in one of tor-gencert's error messages.
2167 - Prevent a false positive from the check-spaces script, by disabling
2168 the "whitespace between function name and (" check for functions
2170 - Fix a log message suggesting that people contact a non-existent
2171 email address. Fixes bug 3448.
2172 - Fix null-pointer access that could occur if TLS allocation failed.
2173 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
2174 - Report a real bootstrap problem to the controller on router
2175 identity mismatch. Previously we just said "foo", which probably
2176 made a lot of sense at the time. Fixes bug 4169; bugfix on
2178 - If we had ever tried to call tor_addr_to_str() on an address of
2179 unknown type, we would have done a strdup() on an uninitialized
2180 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
2181 Reported by "troll_un".
2182 - Correctly detect and handle transient lookup failures from
2183 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
2184 Reported by "troll_un".
2185 - Use tor_socket_t type for listener argument to accept(). Fixes bug
2186 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
2187 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
2188 bug 4532; found by "troll_un".
2190 o Minor bugfixes (on Tor 0.2.3.x):
2191 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
2193 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
2194 circuit for use as a hidden service client's rendezvous point.
2195 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
2196 with help from wanoskarnet.
2197 - Restore behavior of overriding SocksPort, ORPort, and similar
2198 options from the command line. Bugfix on 0.2.3.3-alpha.
2201 - Properly handle the case where the build-tree is not the same
2202 as the source tree when generating src/common/common_sha1.i,
2203 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
2204 bugfix on 0.2.0.1-alpha.
2206 o Code simplifications, cleanups, and refactorings:
2207 - Remove the pure attribute from all functions that used it
2208 previously. In many cases we assigned it incorrectly, because the
2209 functions might assert or call impure functions, and we don't have
2210 evidence that keeping the pure attribute is worthwhile. Implements
2211 changes suggested in ticket 4421.
2212 - Remove some dead code spotted by coverity. Fixes cid 432.
2213 Bugfix on 0.2.3.1-alpha, closes bug 4637.
2216 Changes in version 0.2.3.8-alpha - 2011-11-22
2217 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
2218 socketpair-related bug that has been bothering Windows users. It adds
2219 support to serve microdescriptors to controllers, so Vidalia's network
2220 map can resume listing relays (once Vidalia implements its side),
2221 and adds better support for hardware AES acceleration. Finally, it
2222 starts the process of adjusting the bandwidth cutoff for getting the
2223 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
2224 that tiny relays harm performance more than they help network capacity.
2227 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
2228 that it doesn't attempt to allocate a socketpair. This could cause
2229 some problems on Windows systems with overzealous firewalls. Fix for
2230 bug 4457; workaround for Libevent versions 2.0.1-alpha through
2232 - Correctly sanity-check that we don't underflow on a memory
2233 allocation (and then assert) for hidden service introduction
2234 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
2235 bugfix on 0.2.1.5-alpha.
2236 - Remove the artificially low cutoff of 20KB to guarantee the Fast
2237 flag. In the past few years the average relay speed has picked
2238 up, and while the "top 7/8 of the network get the Fast flag" and
2239 "all relays with 20KB or more of capacity get the Fast flag" rules
2240 used to have the same result, now the top 7/8 of the network has
2241 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
2242 - Fix a rare assertion failure when checking whether a v0 hidden
2243 service descriptor has any usable introduction points left, and
2244 we don't have enough information to build a circuit to the first
2245 intro point named in the descriptor. The HS client code in
2246 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
2247 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
2248 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
2249 - Make bridge authorities not crash when they are asked for their own
2250 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
2251 - When running as a client, do not print a misleading (and plain
2252 wrong) log message that we're collecting "directory request"
2253 statistics: clients don't collect statistics. Also don't create a
2254 useless (because empty) stats file in the stats/ directory. Fixes
2255 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
2258 - Allow Tor controllers like Vidalia to obtain the microdescriptor
2259 for a relay by identity digest or nickname. Previously,
2260 microdescriptors were only available by their own digests, so a
2261 controller would have to ask for and parse the whole microdescriptor
2262 consensus in order to look up a single relay's microdesc. Fixes
2263 bug 3832; bugfix on 0.2.3.1-alpha.
2264 - Use OpenSSL's EVP interface for AES encryption, so that all AES
2265 operations can use hardware acceleration (if present). Resolves
2268 o Minor bugfixes (on 0.2.2.x and earlier):
2269 - Detect failure to initialize Libevent. This fix provides better
2270 detection for future instances of bug 4457.
2271 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
2272 function. This was eating up hideously large amounts of time on some
2273 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
2274 - Don't warn about unused log_mutex in log.c when building with
2275 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
2276 0.1.0.6-rc which introduced --disable-threads.
2277 - Allow manual 'authenticate' commands to the controller interface
2278 from netcat (nc) as well as telnet. We were rejecting them because
2279 they didn't come with the expected whitespace at the end of the
2280 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
2281 - Fix some (not actually triggerable) buffer size checks in usage of
2282 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
2284 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
2285 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
2286 - When configuring, starting, or stopping an NT service, stop
2287 immediately after the service configuration attempt has succeeded
2288 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
2289 - When sending a NETINFO cell, include the original address
2290 received for the other side, not its canonical address. Found
2291 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
2292 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
2293 can pick them up when the tests aren't disabled. Bugfix on
2294 0.2.2.4-alpha which introduced tinytest.
2295 - Fix a memory leak when we check whether a hidden service
2296 descriptor has any usable introduction points left. Fixes bug
2297 4424. Bugfix on 0.2.2.25-alpha.
2298 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
2299 occurred when a client tried to fetch a descriptor for a bridge
2300 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
2302 o Minor bugfixes (on 0.2.3.x):
2303 - Make util unit tests build correctly with MSVC. Bugfix on
2304 0.2.3.3-alpha. Patch by Gisle Vanem.
2305 - Successfully detect AUTH_CHALLENGE cells with no recognized
2306 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
2308 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
2309 it should still send a NETINFO cell to allow the connection to
2310 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
2312 - Log less loudly when we get an invalid authentication certificate
2313 from a source other than a directory authority: it's not unusual
2314 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
2316 - Tolerate servers with more clock skew in their authentication
2317 certificates than previously. Fixes bug 4371; bugfix on
2319 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
2320 on 0.2.3.4-alpha and 0.2.3.6-alpha.
2323 - Add two new config options for directory authorities:
2324 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
2325 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
2326 that is always sufficient to satisfy the bandwidth requirement for
2327 the Guard flag. Now it will be easier for researchers to simulate
2328 Tor networks with different values. Resolves ticket 4484.
2329 - When Tor ignores a hidden service specified in its configuration,
2330 include the hidden service's directory in the warning message.
2331 Previously, we would only tell the user that some hidden service
2332 was ignored. Bugfix on 0.0.6; fixes bug 4426.
2333 - When we fail to initialize Libevent, retry with IOCP disabled so we
2334 don't need to turn on multi-threading support in Libevent, which in
2335 turn requires a working socketpair(). This is a workaround for bug
2336 4457, which affects Libevent versions from 2.0.1-alpha through
2338 - Detect when we try to build on a platform that doesn't define
2339 AF_UNSPEC to 0. We don't work there, so refuse to compile.
2340 - Update to the November 1 2011 Maxmind GeoLite Country database.
2342 o Packaging changes:
2343 - Make it easier to automate expert package builds on Windows,
2344 by removing an absolute path from makensis.exe command.
2346 o Code simplifications and refactoring:
2347 - Remove some redundant #include directives throughout the code.
2348 Patch from Andrea Gelmini.
2349 - Unconditionally use OpenSSL's AES implementation instead of our
2350 old built-in one. OpenSSL's AES has been better for a while, and
2351 relatively few servers should still be on any version of OpenSSL
2352 that doesn't have good optimized assembly AES.
2353 - Use the name "CERTS" consistently to refer to the new cell type;
2354 we were calling it CERT in some places and CERTS in others.
2357 - Numerous new unit tests for functions in util.c and address.c by
2359 - The long-disabled benchmark tests are now split into their own
2360 ./src/test/bench binary.
2361 - The benchmark tests can now use more accurate timers than
2362 gettimeofday() when such timers are available.
2365 Changes in version 0.2.3.7-alpha - 2011-10-30
2366 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
2367 the new v3 handshake. It also resolves yet another bridge address
2371 - If we mark an OR connection for close based on a cell we process,
2372 don't process any further cells on it. We already avoid further
2373 reads on marked-for-close connections, but now we also discard the
2374 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
2375 which was the first version where we might mark a connection for
2376 close based on processing a cell on it.
2377 - Fix a double-free bug that would occur when we received an invalid
2378 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
2379 bugfix on 0.2.3.6-alpha.
2380 - Bridges no longer include their address in NETINFO cells on outgoing
2381 OR connections, to allow them to blend in better with clients.
2382 Removes another avenue for enumerating bridges. Reported by
2383 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
2384 cells were introduced.
2387 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
2388 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
2391 Changes in version 0.2.3.6-alpha - 2011-10-26
2392 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
2393 anonymity vulnerability where an attacker can deanonymize Tor
2394 users. Everybody should upgrade.
2396 This release also features support for a new v3 connection handshake
2397 protocol, and fixes to make hidden service connections more robust.
2400 - Implement a new handshake protocol (v3) for authenticating Tors to
2401 each other over TLS. It should be more resistant to fingerprinting
2402 than previous protocols, and should require less TLS hacking for
2403 future Tor implementations. Implements proposal 176.
2404 - Allow variable-length padding cells to disguise the length of
2405 Tor's TLS records. Implements part of proposal 184.
2407 o Privacy/anonymity fixes (clients):
2408 - Clients and bridges no longer send TLS certificate chains on
2409 outgoing OR connections. Previously, each client or bridge would
2410 use the same cert chain for all outgoing OR connections until
2411 its IP address changes, which allowed any relay that the client
2412 or bridge contacted to determine which entry guards it is using.
2413 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2414 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2415 no longer considers that connection as suitable for satisfying a
2416 circuit EXTEND request. Now relays can protect clients from the
2417 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2418 - Directory authorities no longer assign the Guard flag to relays
2419 that haven't upgraded to the above "refuse EXTEND requests
2420 to client connections" fix. Now directory authorities can
2421 protect clients from the CVE-2011-2768 issue even if neither
2422 the clients nor the relays have upgraded yet. There's a new
2423 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
2424 to let us transition smoothly, else tomorrow there would be no
2427 o Major bugfixes (hidden services):
2428 - Improve hidden service robustness: when an attempt to connect to
2429 a hidden service ends, be willing to refetch its hidden service
2430 descriptors from each of the HSDir relays responsible for them
2431 immediately. Previously, we would not consider refetching the
2432 service's descriptors from each HSDir for 15 minutes after the last
2433 fetch, which was inconvenient if the hidden service was not running
2434 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
2435 - When one of a hidden service's introduction points appears to be
2436 unreachable, stop trying it. Previously, we would keep trying
2437 to build circuits to the introduction point until we lost the
2438 descriptor, usually because the user gave up and restarted Tor.
2439 Partly fixes bug 3825.
2440 - Don't launch a useless circuit after failing to use one of a
2441 hidden service's introduction points. Previously, we would
2442 launch a new introduction circuit, but not set the hidden service
2443 which that circuit was intended to connect to, so it would never
2444 actually be used. A different piece of code would then create a
2445 new introduction circuit correctly. Bug reported by katmagic and
2446 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
2448 o Major bugfixes (other):
2449 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2450 that they initiated. Relays could distinguish incoming bridge
2451 connections from client connections, creating another avenue for
2452 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2453 Found by "frosty_un".
2454 - Don't update the AccountingSoftLimitHitAt state file entry whenever
2455 tor gets started. This prevents a wrong average bandwidth
2456 estimate, which would cause relays to always start a new accounting
2457 interval at the earliest possible moment. Fixes bug 2003; bugfix
2458 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
2459 immensely in tracking this bug down.
2460 - Fix a crash bug when changing node restrictions while a DNS lookup
2461 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
2464 o Minor bugfixes (on 0.2.2.x and earlier):
2465 - When a hidden service turns an extra service-side introduction
2466 circuit into a general-purpose circuit, free the rend_data and
2467 intro_key fields first, so we won't leak memory if the circuit
2468 is cannibalized for use as another service-side introduction
2469 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
2470 - Rephrase the log message emitted if the TestSocks check is
2471 successful. Patch from Fabian Keil; fixes bug 4094.
2472 - Bridges now skip DNS self-tests, to act a little more stealthily.
2473 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
2474 bridges. Patch by "warms0x".
2475 - Remove a confusing dollar sign from the example fingerprint in the
2476 man page, and also make the example fingerprint a valid one. Fixes
2477 bug 4309; bugfix on 0.2.1.3-alpha.
2478 - Fix internal bug-checking logic that was supposed to catch
2479 failures in digest generation so that it will fail more robustly
2480 if we ask for a nonexistent algorithm. Found by Coverity Scan.
2481 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
2482 - Report any failure in init_keys() calls launched because our
2483 IP address has changed. Spotted by Coverity Scan. Bugfix on
2484 0.1.1.4-alpha; fixes CID 484.
2486 o Minor bugfixes (on 0.2.3.x):
2487 - Fix a bug in configure.in that kept it from building a configure
2488 script with autoconf versions earlier than 2.61. Fixes bug 2430;
2489 bugfix on 0.2.3.1-alpha.
2490 - Don't warn users that they are exposing a client port to the
2491 Internet if they have specified an RFC1918 address. Previously,
2492 we would warn if the user had specified any non-loopback
2493 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
2494 - Fix memory leaks in the failing cases of the new SocksPort and
2495 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
2496 fixes coverity CIDs 485, 486, and 487.
2499 - When a hidden service's introduction point times out, consider
2500 trying it again during the next attempt to connect to the
2501 HS. Previously, we would not try it again unless a newly fetched
2502 descriptor contained it. Required by fixes for bugs 1297 and 3825.
2503 - The next version of Windows will be called Windows 8, and it has
2504 a major version of 6, minor version of 2. Correctly identify that
2505 version instead of calling it "Very recent version". Resolves
2506 ticket 4153; reported by funkstar.
2507 - The Bridge Authority now writes statistics on how many bridge
2508 descriptors it gave out in total, and how many unique descriptors
2509 it gave out. It also lists how often the most and least commonly
2510 fetched descriptors were given out, as well as the median and
2511 25th/75th percentile. Implements tickets 4200 and 4294.
2512 - Update to the October 4 2011 Maxmind GeoLite Country database.
2514 o Code simplifications and refactoring:
2515 - Remove some old code to remember statistics about which descriptors
2516 we've served as a directory mirror. The feature wasn't used and
2517 is outdated now that microdescriptors are around.
2518 - Rename Tor functions that turn strings into addresses, so that
2519 "parse" indicates that no hostname resolution occurs, and
2520 "lookup" indicates that hostname resolution may occur. This
2521 should help prevent mistakes in the future. Fixes bug 3512.
2524 Changes in version 0.2.2.34 - 2011-10-26
2525 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
2526 can deanonymize Tor users. Everybody should upgrade.
2528 The attack relies on four components: 1) Clients reuse their TLS cert
2529 when talking to different relays, so relays can recognize a user by
2530 the identity key in her cert. 2) An attacker who knows the client's
2531 identity key can probe each guard relay to see if that identity key
2532 is connected to that guard relay right now. 3) A variety of active
2533 attacks in the literature (starting from "Low-Cost Traffic Analysis
2534 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
2535 discover the guard relays that a Tor user visiting the website is using.
2536 4) Clients typically pick three guards at random, so the set of guards
2537 for a given user could well be a unique fingerprint for her. This
2538 release fixes components #1 and #2, which is enough to block the attack;
2539 the other two remain as open research problems. Special thanks to
2540 "frosty_un" for reporting the issue to us!
2542 Clients should upgrade so they are no longer recognizable by the TLS
2543 certs they present. Relays should upgrade so they no longer allow a
2544 remote attacker to probe them to test whether unpatched clients are
2545 currently connected to them.
2547 This release also fixes several vulnerabilities that allow an attacker
2548 to enumerate bridge relays. Some bridge enumeration attacks still
2549 remain; see for example proposal 188.
2551 o Privacy/anonymity fixes (clients):
2552 - Clients and bridges no longer send TLS certificate chains on
2553 outgoing OR connections. Previously, each client or bridge would
2554 use the same cert chain for all outgoing OR connections until
2555 its IP address changes, which allowed any relay that the client
2556 or bridge contacted to determine which entry guards it is using.
2557 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2558 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2559 no longer considers that connection as suitable for satisfying a
2560 circuit EXTEND request. Now relays can protect clients from the
2561 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2562 - Directory authorities no longer assign the Guard flag to relays
2563 that haven't upgraded to the above "refuse EXTEND requests
2564 to client connections" fix. Now directory authorities can
2565 protect clients from the CVE-2011-2768 issue even if neither
2566 the clients nor the relays have upgraded yet. There's a new
2567 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
2568 to let us transition smoothly, else tomorrow there would be no
2571 o Privacy/anonymity fixes (bridge enumeration):
2572 - Bridge relays now do their directory fetches inside Tor TLS
2573 connections, like all the other clients do, rather than connecting
2574 directly to the DirPort like public relays do. Removes another
2575 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
2576 - Bridges relays now build circuits for themselves in a more similar
2577 way to how clients build them. Removes another avenue for
2578 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
2579 when bridges were introduced.
2580 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2581 that they initiated. Relays could distinguish incoming bridge
2582 connections from client connections, creating another avenue for
2583 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2584 Found by "frosty_un".
2587 - Fix a crash bug when changing node restrictions while a DNS lookup
2588 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
2590 - Don't launch a useless circuit after failing to use one of a
2591 hidden service's introduction points. Previously, we would
2592 launch a new introduction circuit, but not set the hidden service
2593 which that circuit was intended to connect to, so it would never
2594 actually be used. A different piece of code would then create a
2595 new introduction circuit correctly. Bug reported by katmagic and
2596 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
2599 - Change an integer overflow check in the OpenBSD_Malloc code so
2600 that GCC is less likely to eliminate it as impossible. Patch
2601 from Mansour Moufid. Fixes bug 4059.
2602 - When a hidden service turns an extra service-side introduction
2603 circuit into a general-purpose circuit, free the rend_data and
2604 intro_key fields first, so we won't leak memory if the circuit
2605 is cannibalized for use as another service-side introduction
2606 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
2607 - Bridges now skip DNS self-tests, to act a little more stealthily.
2608 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
2609 bridges. Patch by "warms0x".
2610 - Fix internal bug-checking logic that was supposed to catch
2611 failures in digest generation so that it will fail more robustly
2612 if we ask for a nonexistent algorithm. Found by Coverity Scan.
2613 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
2614 - Report any failure in init_keys() calls launched because our
2615 IP address has changed. Spotted by Coverity Scan. Bugfix on
2616 0.1.1.4-alpha; fixes CID 484.
2618 o Minor bugfixes (log messages and documentation):
2619 - Remove a confusing dollar sign from the example fingerprint in the
2620 man page, and also make the example fingerprint a valid one. Fixes
2621 bug 4309; bugfix on 0.2.1.3-alpha.
2622 - The next version of Windows will be called Windows 8, and it has
2623 a major version of 6, minor version of 2. Correctly identify that
2624 version instead of calling it "Very recent version". Resolves
2625 ticket 4153; reported by funkstar.
2626 - Downgrade log messages about circuit timeout calibration from
2627 "notice" to "info": they don't require or suggest any human
2628 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
2629 bugfix on 0.2.2.14-alpha.
2632 - Turn on directory request statistics by default and include them in
2633 extra-info descriptors. Don't break if we have no GeoIP database.
2634 Backported from 0.2.3.1-alpha; implements ticket 3951.
2635 - Update to the October 4 2011 Maxmind GeoLite Country database.
2638 Changes in version 0.2.1.31 - 2011-10-26
2639 Tor 0.2.1.31 backports important security and privacy fixes for
2640 oldstable. This release is intended only for package maintainers and
2641 others who cannot use the 0.2.2 stable series. All others should be
2642 using Tor 0.2.2.x or newer.
2644 o Security fixes (also included in 0.2.2.x):
2645 - Replace all potentially sensitive memory comparison operations
2646 with versions whose runtime does not depend on the data being
2647 compared. This will help resist a class of attacks where an
2648 adversary can use variations in timing information to learn
2649 sensitive data. Fix for one case of bug 3122. (Safe memcmp
2650 implementation by Robert Ransom based partially on code by DJB.)
2651 - Fix an assert in parsing router descriptors containing IPv6
2652 addresses. This one took down the directory authorities when
2653 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
2655 o Privacy/anonymity fixes (also included in 0.2.2.x):
2656 - Clients and bridges no longer send TLS certificate chains on
2657 outgoing OR connections. Previously, each client or bridge would
2658 use the same cert chain for all outgoing OR connections until
2659 its IP address changes, which allowed any relay that the client
2660 or bridge contacted to determine which entry guards it is using.
2661 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2662 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2663 no longer considers that connection as suitable for satisfying a
2664 circuit EXTEND request. Now relays can protect clients from the
2665 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2666 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2667 that they initiated. Relays could distinguish incoming bridge
2668 connections from client connections, creating another avenue for
2669 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2670 Found by "frosty_un".
2671 - When receiving a hidden service descriptor, check that it is for
2672 the hidden service we wanted. Previously, Tor would store any
2673 hidden service descriptors that a directory gave it, whether it
2674 wanted them or not. This wouldn't have let an attacker impersonate
2675 a hidden service, but it did let directories pre-seed a client
2676 with descriptors that it didn't want. Bugfix on 0.0.6.
2677 - Avoid linkability based on cached hidden service descriptors: forget
2678 all hidden service descriptors cached as a client when processing a
2679 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
2680 - Make the bridge directory authority refuse to answer directory
2681 requests for "all" descriptors. It used to include bridge
2682 descriptors in its answer, which was a major information leak.
2683 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
2684 - Don't attach new streams to old rendezvous circuits after SIGNAL
2685 NEWNYM. Previously, we would keep using an existing rendezvous
2686 circuit if it remained open (i.e. if it were kept open by a
2687 long-lived stream, or if a new stream were attached to it before
2688 Tor could notice that it was old and no longer in use). Bugfix on
2689 0.1.1.15-rc; fixes bug 3375.
2691 o Minor bugfixes (also included in 0.2.2.x):
2692 - When we restart our relay, we might get a successful connection
2693 from the outside before we've started our reachability tests,
2694 triggering a warning: "ORPort found reachable, but I have no
2695 routerinfo yet. Failing to inform controller of success." This
2696 bug was harmless unless Tor is running under a controller
2697 like Vidalia, in which case the controller would never get a
2698 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
2700 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
2701 enabled. Fixes bug 1526.
2702 - Remove undocumented option "-F" from tor-resolve: it hasn't done
2703 anything since 0.2.1.16-rc.
2704 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
2705 None of the cases where we did this before were wrong, but by making
2706 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
2707 - Fix a rare crash bug that could occur when a client was configured
2708 with a large number of bridges. Fixes bug 2629; bugfix on
2709 0.2.1.2-alpha. Bugfix by trac user "shitlei".
2710 - Correct the warning displayed when a rendezvous descriptor exceeds
2711 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
2713 - Fix an uncommon assertion failure when running with DNSPort under
2714 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
2715 - When warning about missing zlib development packages during compile,
2716 give the correct package names. Bugfix on 0.2.0.1-alpha.
2717 - Require that introduction point keys and onion keys have public
2718 exponent 65537. Bugfix on 0.2.0.10-alpha.
2719 - Do not crash when our configuration file becomes unreadable, for
2720 example due to a permissions change, between when we start up
2721 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2723 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2725 - Always NUL-terminate the sun_path field of a sockaddr_un before
2726 passing it to the kernel. (Not a security issue: kernels are
2727 smart enough to reject bad sockaddr_uns.) Found by Coverity;
2728 CID #428. Bugfix on Tor 0.2.0.3-alpha.
2729 - Don't stack-allocate the list of supplementary GIDs when we're
2730 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
2731 could take up to 256K, which is way too much stack. Found by
2732 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
2734 o Minor bugfixes (only in 0.2.1.x):
2735 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
2736 rely on them. Bugfix on 0.2.1.30.
2737 - Use git revisions instead of svn revisions when generating our
2738 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
2740 o Minor features (also included in 0.2.2.x):
2741 - Adjust the expiration time on our SSL session certificates to
2742 better match SSL certs seen in the wild. Resolves ticket 4014.
2743 - Allow nameservers with IPv6 address. Resolves bug 2574.
2744 - Update to the October 4 2011 Maxmind GeoLite Country database.
2747 Changes in version 0.2.3.5-alpha - 2011-09-28
2748 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
2749 bridge relays; fixes an assertion error that many users started hitting
2750 today; and adds the ability to refill token buckets more often than
2751 once per second, allowing significant performance improvements.
2754 - Bridge relays now do their directory fetches inside Tor TLS
2755 connections, like all the other clients do, rather than connecting
2756 directly to the DirPort like public relays do. Removes another
2757 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
2758 - Bridges relays now build circuits for themselves in a more similar
2759 way to how clients build them. Removes another avenue for
2760 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
2761 when bridges were introduced.
2764 - Fix an "Assertion md->held_by_node == 1 failed" error that could
2765 occur when the same microdescriptor was referenced by two node_t
2766 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
2768 o Major features (networking):
2769 - Add a new TokenBucketRefillInterval option to refill token buckets
2770 more frequently than once per second. This should improve network
2771 performance, alleviate queueing problems, and make traffic less
2772 bursty. Implements proposal 183; closes ticket 3630. Design by
2773 Florian Tschorsch and Björn Scheuermann; implementation by
2777 - Change an integer overflow check in the OpenBSD_Malloc code so
2778 that GCC is less likely to eliminate it as impossible. Patch
2779 from Mansour Moufid. Fixes bug 4059.
2781 o Minor bugfixes (usability):
2782 - Downgrade log messages about circuit timeout calibration from
2783 "notice" to "info": they don't require or suggest any human
2784 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
2785 bugfix on 0.2.2.14-alpha.
2787 o Minor features (diagnostics):
2788 - When the system call to create a listener socket fails, log the
2789 error message explaining why. This may help diagnose bug 4027.
2792 Changes in version 0.2.3.4-alpha - 2011-09-13
2793 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
2794 tweak to Tor's TLS handshake that makes relays and bridges that run
2795 this new version reachable from Iran again. It also fixes a few new
2796 bugs in 0.2.3.x, and teaches relays to recognize when they're not
2797 listed in the network consensus and republish.
2799 o Major bugfixes (also part of 0.2.2.33):
2800 - Avoid an assertion failure when reloading a configuration with
2801 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
2802 3923; bugfix on 0.2.2.25-alpha.
2804 o Minor features (security, also part of 0.2.2.33):
2805 - Check for replays of the public-key encrypted portion of an
2806 INTRODUCE1 cell, in addition to the current check for replays of
2807 the g^x value. This prevents a possible class of active attacks
2808 by an attacker who controls both an introduction point and a
2809 rendezvous point, and who uses the malleability of AES-CTR to
2810 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
2811 that these attacks is infeasible (requiring the attacker to send
2812 on the order of zettabytes of altered cells in a short interval),
2813 but we'd rather block them off in case there are any classes of
2814 this attack that we missed. Reported by Willem Pinckaers.
2816 o Minor features (also part of 0.2.2.33):
2817 - Adjust the expiration time on our SSL session certificates to
2818 better match SSL certs seen in the wild. Resolves ticket 4014.
2819 - Change the default required uptime for a relay to be accepted as
2820 a HSDir (hidden service directory) from 24 hours to 25 hours.
2821 Improves on 0.2.0.10-alpha; resolves ticket 2649.
2822 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
2823 authorities to abstain from voting on assignment of the HSDir
2824 consensus flag. Related to bug 2649.
2825 - Update to the September 6 2011 Maxmind GeoLite Country database.
2827 o Minor bugfixes (also part of 0.2.2.33):
2828 - Demote the 'replay detected' log message emitted when a hidden
2829 service receives the same Diffie-Hellman public key in two different
2830 INTRODUCE2 cells to info level. A normal Tor client can cause that
2831 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
2832 fixes part of bug 2442.
2833 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
2834 level. There is nothing that a hidden service's operator can do
2835 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
2837 - Clarify a log message specifying the characters permitted in
2838 HiddenServiceAuthorizeClient client names. Previously, the log
2839 message said that "[A-Za-z0-9+-_]" were permitted; that could have
2840 given the impression that every ASCII character between "+" and "_"
2841 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
2843 o Build fixes (also part of 0.2.2.33):
2844 - Clean up some code issues that prevented Tor from building on older
2845 BSDs. Fixes bug 3894; reported by "grarpamp".
2846 - Search for a platform-specific version of "ar" when cross-compiling.
2847 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
2850 - Fix a bug where the SocksPort option (for example) would get
2851 ignored and replaced by the default if a SocksListenAddress
2852 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
2856 - Relays now try regenerating and uploading their descriptor more
2857 frequently if they are not listed in the consensus, or if the
2858 version of their descriptor listed in the consensus is too
2859 old. This fix should prevent situations where a server declines
2860 to re-publish itself because it has done so too recently, even
2861 though the authorities decided not to list its recent-enough
2862 descriptor. Fix for bug 3327.
2865 - Relays now include a reason for regenerating their descriptors
2866 in an HTTP header when uploading to the authorities. This will
2867 make it easier to debug descriptor-upload issues in the future.
2868 - When starting as root and then changing our UID via the User
2869 control option, and we have a ControlSocket configured, make sure
2870 that the ControlSocket is owned by the same account that Tor will
2871 run under. Implements ticket 3421; fix by Jérémy Bobbio.
2874 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
2875 utility function used in the control-port code). This shouldn't
2876 ever happen unless Tor is completely out of memory, but if it did
2877 happen and Tor somehow recovered from it, Tor could have sent a log
2878 message to a control port in the middle of a reply to a controller
2879 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
2880 - Make 'FetchUselessDescriptors' cause all descriptor types and
2881 all consensus types (including microdescriptors) to get fetched.
2882 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
2885 - Make a new "entry connection" struct as an internal subtype of "edge
2886 connection", to simplify the code and make exit connections smaller.
2889 Changes in version 0.2.2.33 - 2011-09-13
2890 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
2891 TLS handshake that makes relays and bridges that run this new version
2892 reachable from Iran again.
2895 - Avoid an assertion failure when reloading a configuration with
2896 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
2897 3923; bugfix on 0.2.2.25-alpha.
2899 o Minor features (security):
2900 - Check for replays of the public-key encrypted portion of an
2901 INTRODUCE1 cell, in addition to the current check for replays of
2902 the g^x value. This prevents a possible class of active attacks
2903 by an attacker who controls both an introduction point and a
2904 rendezvous point, and who uses the malleability of AES-CTR to
2905 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
2906 that these attacks are infeasible (requiring the attacker to send
2907 on the order of zettabytes of altered cells in a short interval),
2908 but we'd rather block them off in case there are any classes of
2909 this attack that we missed. Reported by Willem Pinckaers.
2912 - Adjust the expiration time on our SSL session certificates to
2913 better match SSL certs seen in the wild. Resolves ticket 4014.
2914 - Change the default required uptime for a relay to be accepted as
2915 a HSDir (hidden service directory) from 24 hours to 25 hours.
2916 Improves on 0.2.0.10-alpha; resolves ticket 2649.
2917 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
2918 authorities to abstain from voting on assignment of the HSDir
2919 consensus flag. Related to bug 2649.
2920 - Update to the September 6 2011 Maxmind GeoLite Country database.
2922 o Minor bugfixes (documentation and log messages):
2923 - Correct the man page to explain that HashedControlPassword and
2924 CookieAuthentication can both be set, in which case either method
2925 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
2926 when we decided to allow these config options to both be set. Issue
2928 - Demote the 'replay detected' log message emitted when a hidden
2929 service receives the same Diffie-Hellman public key in two different
2930 INTRODUCE2 cells to info level. A normal Tor client can cause that
2931 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
2932 fixes part of bug 2442.
2933 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
2934 level. There is nothing that a hidden service's operator can do
2935 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
2937 - Clarify a log message specifying the characters permitted in
2938 HiddenServiceAuthorizeClient client names. Previously, the log
2939 message said that "[A-Za-z0-9+-_]" were permitted; that could have
2940 given the impression that every ASCII character between "+" and "_"
2941 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
2944 - Provide a substitute implementation of lround() for MSVC, which
2945 apparently lacks it. Patch from Gisle Vanem.
2946 - Clean up some code issues that prevented Tor from building on older
2947 BSDs. Fixes bug 3894; reported by "grarpamp".
2948 - Search for a platform-specific version of "ar" when cross-compiling.
2949 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
2952 Changes in version 0.2.3.3-alpha - 2011-09-01
2953 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
2954 security, and provides client-side support for the microdescriptor
2955 and optimistic data features introduced earlier in the 0.2.3.x
2956 series. It also includes numerous critical bugfixes in the (optional)
2957 bufferevent-based networking backend.
2959 o Major features (stream isolation):
2960 - You can now configure Tor so that streams from different
2961 applications are isolated on different circuits, to prevent an
2962 attacker who sees your streams as they leave an exit node from
2963 linking your sessions to one another. To do this, choose some way
2964 to distinguish the applications: have them connect to different
2965 SocksPorts, or have one of them use SOCKS4 while the other uses
2966 SOCKS5, or have them pass different authentication strings to the
2967 SOCKS proxy. Then, use the new SocksPort syntax to configure the
2968 degree of isolation you need. This implements Proposal 171.
2969 - There's a new syntax for specifying multiple client ports (such as
2970 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
2971 multiple *Port entries with full addr:port syntax on each.
2972 The old *ListenAddress format is still supported, but you can't
2973 mix it with the new *Port syntax.
2975 o Major features (other):
2976 - Enable microdescriptor fetching by default for clients. This allows
2977 clients to download a much smaller amount of directory information.
2978 To disable it (and go back to the old-style consensus and
2979 descriptors), set "UseMicrodescriptors 0" in your torrc file.
2980 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
2981 "PortForwarding" config option), now supports Windows.
2982 - When using an exit relay running 0.2.3.x, clients can now
2983 "optimistically" send data before the exit relay reports that
2984 the stream has opened. This saves a round trip when starting
2985 connections where the client speaks first (such as web browsing).
2986 This behavior is controlled by a consensus parameter (currently
2987 disabled). To turn it on or off manually, use the "OptimisticData"
2988 torrc option. Implements proposal 181; code by Ian Goldberg.
2990 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
2991 - When using IOCP on Windows, we need to enable Libevent windows
2993 - The IOCP backend now works even when the user has not specified
2994 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
2995 Fixes part of bug 3752.
2996 - Correctly record the bytes we've read and written when using
2997 bufferevents, so that we can include them in our bandwidth history
2998 and advertised bandwidth. Fixes bug 3803.
2999 - Apply rate-limiting only at the bottom of a chain of filtering
3000 bufferevents. This prevents us from filling up internal read
3001 buffers and violating rate-limits when filtering bufferevents
3002 are enabled. Fixes part of bug 3804.
3003 - Add high-watermarks to the output buffers for filtered
3004 bufferevents. This prevents us from filling up internal write
3005 buffers and wasting CPU cycles when filtering bufferevents are
3006 enabled. Fixes part of bug 3804.
3007 - Correctly notice when data has been written from a bufferevent
3008 without flushing it completely. Fixes bug 3805.
3009 - Fix a bug where server-side tunneled bufferevent-based directory
3010 streams would get closed prematurely. Fixes bug 3814.
3011 - Fix a use-after-free error with per-connection rate-limiting
3012 buckets. Fixes bug 3888.
3014 o Major bugfixes (also part of 0.2.2.31-rc):
3015 - If we're configured to write our ControlPorts to disk, only write
3016 them after switching UID and creating the data directory. This way,
3017 we don't fail when starting up with a nonexistent DataDirectory
3018 and a ControlPortWriteToFile setting based on that directory. Fixes
3019 bug 3747; bugfix on Tor 0.2.2.26-beta.
3022 - Added a new CONF_CHANGED event so that controllers can be notified
3023 of any configuration changes made by other controllers, or by the
3024 user. Implements ticket 1692.
3025 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
3026 leak when using bufferevents, and lets Libevent worry about how to
3027 best copy data out of a buffer.
3028 - Replace files in stats/ rather than appending to them. Now that we
3029 include statistics in extra-info descriptors, it makes no sense to
3030 keep old statistics forever. Implements ticket 2930.
3032 o Minor features (build compatibility):
3033 - Limited, experimental support for building with nmake and MSVC.
3034 - Provide a substitute implementation of lround() for MSVC, which
3035 apparently lacks it. Patch from Gisle Vanem.
3037 o Minor features (also part of 0.2.2.31-rc):
3038 - Update to the August 2 2011 Maxmind GeoLite Country database.
3040 o Minor bugfixes (on 0.2.3.x-alpha):
3041 - Fix a spurious warning when parsing SOCKS requests with
3042 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
3043 - Get rid of a harmless warning that could happen on relays running
3044 with bufferevents. The warning was caused by someone doing an http
3045 request to a relay's orport. Also don't warn for a few related
3046 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
3048 o Minor bugfixes (on 2.2.x and earlier):
3049 - Correct the man page to explain that HashedControlPassword and
3050 CookieAuthentication can both be set, in which case either method
3051 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
3052 when we decided to allow these config options to both be set. Issue
3054 - The "--quiet" and "--hush" options now apply not only to Tor's
3055 behavior before logs are configured, but also to Tor's behavior in
3056 the absense of configured logs. Fixes bug 3550; bugfix on
3059 o Minor bugfixes (also part of 0.2.2.31-rc):
3060 - Write several files in text mode, on OSes that distinguish text
3061 mode from binary mode (namely, Windows). These files are:
3062 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
3063 that collect those statistics; 'client_keys' and 'hostname' for
3064 hidden services that use authentication; and (in the tor-gencert
3065 utility) newly generated identity and signing keys. Previously,
3066 we wouldn't specify text mode or binary mode, leading to an
3067 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
3068 the DirRecordUsageByCountry option which would have triggered
3069 the assertion failure was added), although this assertion failure
3070 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
3071 - Selectively disable deprecation warnings on OS X because Lion
3072 started deprecating the shipped copy of openssl. Fixes bug 3643.
3073 - Remove an extra pair of quotation marks around the error
3074 message in control-port STATUS_GENERAL BUG events. Bugfix on
3075 0.1.2.6-alpha; fixes bug 3732.
3076 - When unable to format an address as a string, report its value
3077 as "???" rather than reusing the last formatted address. Bugfix
3080 o Code simplifications and refactoring:
3081 - Rewrite the listener-selection logic so that parsing which ports
3082 we want to listen on is now separate from binding to the ports
3086 - Building Tor with bufferevent support now requires Libevent
3087 2.0.13-stable or later. Previous versions of Libevent had bugs in
3088 SSL-related bufferevents and related issues that would make Tor
3089 work badly with bufferevents. Requiring 2.0.13-stable also allows
3090 Tor with bufferevents to take advantage of Libevent APIs
3091 introduced after 2.0.8-rc.
3094 Changes in version 0.2.2.32 - 2011-08-27
3095 The Tor 0.2.2 release series is dedicated to the memory of Andreas
3096 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
3097 a founder of the PETS community, a leader in our field, a mentor,
3098 and a friend. He left us with these words: "I had the possibility
3099 to contribute to this world that is not as it should be. I hope I
3100 could help in some areas to make the world a better place, and that
3101 I could also encourage other people to be engaged in improving the
3102 world. Please, stay engaged. This world needs you, your love, your
3103 initiative -- now I cannot be part of that anymore."
3105 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
3106 ready. More than two years in the making, this release features improved
3107 client performance and hidden service reliability, better compatibility
3108 for Android, correct behavior for bridges that listen on more than
3109 one address, more extensible and flexible directory object handling,
3110 better reporting of network statistics, improved code security, and
3111 many many other features and bugfixes.
3114 Changes in version 0.2.2.31-rc - 2011-08-17
3115 Tor 0.2.2.31-rc is the second and hopefully final release candidate
3116 for the Tor 0.2.2.x series.
3119 - Remove an extra pair of quotation marks around the error
3120 message in control-port STATUS_GENERAL BUG events. Bugfix on
3121 0.1.2.6-alpha; fixes bug 3732.
3122 - If we're configured to write our ControlPorts to disk, only write
3123 them after switching UID and creating the data directory. This way,
3124 we don't fail when starting up with a nonexistent DataDirectory
3125 and a ControlPortWriteToFile setting based on that directory. Fixes
3126 bug 3747; bugfix on Tor 0.2.2.26-beta.
3129 - Update to the August 2 2011 Maxmind GeoLite Country database.
3132 - Allow GETINFO fingerprint to return a fingerprint even when
3133 we have not yet built a router descriptor. Fixes bug 3577;
3134 bugfix on 0.2.0.1-alpha.
3135 - Write several files in text mode, on OSes that distinguish text
3136 mode from binary mode (namely, Windows). These files are:
3137 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
3138 that collect those statistics; 'client_keys' and 'hostname' for
3139 hidden services that use authentication; and (in the tor-gencert
3140 utility) newly generated identity and signing keys. Previously,
3141 we wouldn't specify text mode or binary mode, leading to an
3142 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
3143 the DirRecordUsageByCountry option which would have triggered
3144 the assertion failure was added), although this assertion failure
3145 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
3146 - Selectively disable deprecation warnings on OS X because Lion
3147 started deprecating the shipped copy of openssl. Fixes bug 3643.
3148 - When unable to format an address as a string, report its value
3149 as "???" rather than reusing the last formatted address. Bugfix
3153 Changes in version 0.2.3.2-alpha - 2011-07-18
3154 Tor 0.2.3.2-alpha introduces two new experimental features:
3155 microdescriptors and pluggable transports. It also continues cleaning
3156 up a variety of recently introduced features.
3159 - Clients can now use microdescriptors instead of regular descriptors
3160 to build circuits. Microdescriptors are authority-generated
3161 summaries of regular descriptors' contents, designed to change
3162 very rarely (see proposal 158 for details). This feature is
3163 designed to save bandwidth, especially for clients on slow internet
3164 connections. It's off by default for now, since nearly no caches
3165 support it, but it will be on-by-default for clients in a future
3166 version. You can use the UseMicrodescriptors option to turn it on.
3167 - Tor clients using bridges can now be configured to use a separate
3168 'transport' proxy for each bridge. This approach helps to resist
3169 censorship by allowing bridges to use protocol obfuscation
3170 plugins. It implements part of proposal 180. Implements ticket 2841.
3171 - While we're trying to bootstrap, record how many TLS connections
3172 fail in each state, and report which states saw the most failures
3173 in response to any bootstrap failures. This feature may speed up
3174 diagnosis of censorship events. Implements ticket 3116.
3176 o Major bugfixes (on 0.2.3.1-alpha):
3177 - When configuring a large set of nodes in EntryNodes (as with
3178 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
3179 random subset to be guards, and choose them in random
3180 order. Fixes bug 2798.
3181 - Tor could crash when remembering a consensus in a non-used consensus
3182 flavor without having a current consensus set. Fixes bug 3361.
3183 - Comparing an unknown address to a microdescriptor's shortened exit
3184 policy would always give a "rejected" result. Fixes bug 3599.
3185 - Using microdescriptors as a client no longer prevents Tor from
3186 uploading and downloading hidden service descriptors. Fixes
3190 - Allow nameservers with IPv6 address. Resolves bug 2574.
3191 - Accept attempts to include a password authenticator in the
3192 handshake, as supported by SOCKS5. This handles SOCKS clients that
3193 don't know how to omit a password when authenticating. Resolves
3195 - When configuring a large set of nodes in EntryNodes, and there are
3196 enough of them listed as Guard so that we don't need to consider
3197 the non-guard entries, prefer the ones listed with the Guard flag.
3198 - Check for and recover from inconsistency in the microdescriptor
3199 cache. This will make it harder for us to accidentally free a
3200 microdescriptor without removing it from the appropriate data
3201 structures. Fixes issue 3135; issue noted by "wanoskarnet".
3202 - Log SSL state transitions at log level DEBUG, log domain
3203 HANDSHAKE. This can be useful for debugging censorship events.
3204 Implements ticket 3264.
3205 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
3206 implements ticket 3439.
3208 o Minor bugfixes (on 0.2.3.1-alpha):
3209 - Do not free all general-purpose regular descriptors just
3210 because microdescriptor use is enabled. Fixes bug 3113.
3211 - Correctly link libevent_openssl when --enable-static-libevent
3212 is passed to configure. Fixes bug 3118.
3213 - Bridges should not complain during their heartbeat log messages that
3214 they are unlisted in the consensus: that's more or less the point
3215 of being a bridge. Fixes bug 3183.
3216 - Report a SIGNAL event to controllers when acting on a delayed
3217 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
3218 event to the controller if we acted on a SIGNAL NEWNYM command
3219 immediately, and otherwise not report a SIGNAL event for the
3220 command at all. Fixes bug 3349.
3221 - Fix a crash when handling the SIGNAL controller command or
3222 reporting ERR-level status events with bufferevents enabled. Found
3223 by Robert Ransom. Fixes bug 3367.
3224 - Always ship the tor-fw-helper manpage in our release tarballs.
3225 Fixes bug 3389. Reported by Stephen Walker.
3226 - Fix a class of double-mark-for-close bugs when bufferevents
3227 are enabled. Fixes bug 3403.
3228 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
3229 - Add SIGNAL to the list returned by the 'GETINFO events/names'
3230 control-port command. Fixes part of bug 3465.
3231 - Prevent using negative indices during unit test runs when read_all()
3232 fails. Spotted by coverity.
3233 - Fix a rare memory leak when checking the nodelist without it being
3234 present. Found by coverity.
3235 - Only try to download a microdescriptor-flavored consensus from
3236 a directory cache that provides them.
3238 o Minor bugfixes (on 0.2.2.x and earlier):
3239 - Assert that hidden-service-related operations are not performed
3240 using single-hop circuits. Previously, Tor would assert that
3241 client-side streams are not attached to single-hop circuits,
3242 but not that other sensitive operations on the client and service
3243 side are not performed using single-hop circuits. Fixes bug 3332;
3245 - Don't publish a new relay descriptor when we reload our onion key,
3246 unless the onion key has actually changed. Fixes bug 3263 and
3247 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
3248 - Allow GETINFO fingerprint to return a fingerprint even when
3249 we have not yet built a router descriptor. Fixes bug 3577;
3250 bugfix on 0.2.0.1-alpha.
3251 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
3252 on 0.2.2.4-alpha; fixes bug 3427.
3254 o Code simplification and refactoring:
3255 - Use tor_sscanf() in place of scanf() in more places through the
3256 code. This makes us a little more locale-independent, and
3257 should help shut up code-analysis tools that can't tell
3258 a safe sscanf string from a dangerous one.
3259 - Use tt_assert(), not tor_assert(), for checking for test failures.
3260 This makes the unit tests more able to go on in the event that
3262 - Split connection_about_to_close() into separate functions for each
3266 - On Windows, we now define the _WIN32_WINNT macros only if they
3267 are not already defined. This lets the person building Tor decide,
3268 if they want, to require a later version of Windows.
3271 Changes in version 0.2.2.30-rc - 2011-07-07
3272 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
3273 series. It fixes a few smaller bugs, but generally appears stable.
3274 Please test it and let us know whether it is!
3277 - Send a SUCCEEDED stream event to the controller when a reverse
3278 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
3279 discovered by katmagic.
3280 - Always NUL-terminate the sun_path field of a sockaddr_un before
3281 passing it to the kernel. (Not a security issue: kernels are
3282 smart enough to reject bad sockaddr_uns.) Found by Coverity;
3283 CID #428. Bugfix on Tor 0.2.0.3-alpha.
3284 - Don't stack-allocate the list of supplementary GIDs when we're
3285 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
3286 could take up to 256K, which is way too much stack. Found by
3287 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
3288 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
3289 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
3290 fixes part of bug 3465.
3291 - Fix a memory leak when receiving a descriptor for a hidden
3292 service we didn't ask for. Found by Coverity; CID #30. Bugfix
3296 - Update to the July 1 2011 Maxmind GeoLite Country database.
3299 Changes in version 0.2.2.29-beta - 2011-06-20
3300 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
3301 have bridge lines in their torrc but don't want to use them; gets
3302 us closer to having the control socket feature working on Debian;
3303 and fixes a variety of smaller bugs.
3306 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
3307 When we changed the default behavior to "use bridges if any
3308 are listed in the torrc", we surprised users who had bridges
3309 in their torrc files but who didn't actually want to use them.
3310 Partial resolution for bug 3354.
3313 - Don't attach new streams to old rendezvous circuits after SIGNAL
3314 NEWNYM. Previously, we would keep using an existing rendezvous
3315 circuit if it remained open (i.e. if it were kept open by a
3316 long-lived stream, or if a new stream were attached to it before
3317 Tor could notice that it was old and no longer in use). Bugfix on
3318 0.1.1.15-rc; fixes bug 3375.
3321 - Fix a bug when using ControlSocketsGroupWritable with User. The
3322 directory's group would be checked against the current group, not
3323 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
3324 bugfix on 0.2.2.26-beta.
3325 - Make connection_printf_to_buf()'s behaviour sane. Its callers
3326 expect it to emit a CRLF iff the format string ends with CRLF;
3327 it actually emitted a CRLF iff (a) the format string ended with
3328 CRLF or (b) the resulting string was over 1023 characters long or
3329 (c) the format string did not end with CRLF *and* the resulting
3330 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
3331 fixes part of bug 3407.
3332 - Make send_control_event_impl()'s behaviour sane. Its callers
3333 expect it to always emit a CRLF at the end of the string; it
3334 might have emitted extra control characters as well. Bugfix on
3335 0.1.1.9-alpha; fixes another part of bug 3407.
3336 - Make crypto_rand_int() check the value of its input correctly.
3337 Previously, it accepted values up to UINT_MAX, but could return a
3338 negative number if given a value above INT_MAX+1. Found by George
3339 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
3340 - Avoid a segfault when reading a malformed circuit build state
3341 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
3343 - When asked about a DNS record type we don't support via a
3344 client DNSPort, reply with NOTIMPL rather than an empty
3345 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
3346 - Fix a rare memory leak during stats writing. Found by coverity.
3349 - Update to the June 1 2011 Maxmind GeoLite Country database.
3351 o Code simplifications and refactoring:
3352 - Remove some dead code as indicated by coverity.
3353 - Remove a few dead assignments during router parsing. Found by
3355 - Add some forgotten return value checks during unit tests. Found
3357 - Don't use 1-bit wide signed bit fields. Found by coverity.
3360 Changes in version 0.2.2.28-beta - 2011-06-04
3361 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
3362 fixed a big bug in whether relays stay in the consensus consistently,
3363 we moved closer to handling bridges and hidden services correctly,
3364 and we started the process of better handling the dreaded "my Vidalia
3365 died, and now my Tor demands a password when I try to reconnect to it"
3369 - Don't decide to make a new descriptor when receiving a HUP signal.
3370 This bug has caused a lot of 0.2.2.x relays to disappear from the
3371 consensus periodically. Fixes the most common case of triggering
3372 bug 1810; bugfix on 0.2.2.7-alpha.
3373 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
3374 - Don't try to build descriptors if "ORPort auto" is set and we
3375 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
3377 - Resolve a crash that occurred when setting BridgeRelay to 1 with
3378 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
3379 - Apply circuit timeouts to opened hidden-service-related circuits
3380 based on the correct start time. Previously, we would apply the
3381 circuit build timeout based on time since the circuit's creation;
3382 it was supposed to be applied based on time since the circuit
3383 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
3384 - Use the same circuit timeout for client-side introduction
3385 circuits as for other four-hop circuits, rather than the timeout
3386 for single-hop directory-fetch circuits; the shorter timeout may
3387 have been appropriate with the static circuit build timeout in
3388 0.2.1.x and earlier, but caused many hidden service access attempts
3389 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
3390 on 0.2.2.2-alpha; fixes another part of bug 1297.
3391 - In ticket 2511 we fixed a case where you could use an unconfigured
3392 bridge if you had configured it as a bridge the last time you ran
3393 Tor. Now fix another edge case: if you had configured it as a bridge
3394 but then switched to a different bridge via the controller, you
3395 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
3399 - Add an __OwningControllerProcess configuration option and a
3400 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
3401 that when it exits, Tor will shut down. Implements feature 3049.
3402 - If "UseBridges 1" is set and no bridges are configured, Tor will
3403 now refuse to build any circuits until some bridges are set.
3404 If "UseBridges auto" is set, Tor will use bridges if they are
3405 configured and we are not running as a server, but otherwise will
3406 make circuits as usual. The new default is "auto". Patch by anonym,
3407 so the Tails LiveCD can stop automatically revealing you as a Tor
3411 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
3412 - Remove a trailing asterisk from "exit-policy/default" in the
3413 output of the control port command "GETINFO info/names". Bugfix
3415 - Use a wide type to hold sockets when built for 64-bit Windows builds.
3417 - Warn when the user configures two HiddenServiceDir lines that point
3418 to the same directory. Bugfix on 0.0.6 (the version introducing
3419 HiddenServiceDir); fixes bug 3289.
3420 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
3421 part of bug 2748; bugfix on 0.2.0.10-alpha.
3422 - Log malformed requests for rendezvous descriptors as protocol
3423 warnings, not warnings. Also, use a more informative log message
3424 in case someone sees it at log level warning without prior
3425 info-level messages. Fixes the other part of bug 2748; bugfix
3427 - Clear the table recording the time of the last request for each
3428 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
3429 Previously, we would clear our HS descriptor cache on SIGNAL
3430 NEWNYM, but if we had previously retrieved a descriptor (or tried
3431 to) from every directory responsible for it, we would refuse to
3432 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
3434 - Fix a log message that said "bits" while displaying a value in
3435 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
3437 - When checking for 1024-bit keys, check for 1024 bits, not 128
3438 bytes. This allows Tor to correctly discard keys of length 1017
3439 through 1023. Bugfix on 0.0.9pre5.
3442 - Relays now log the reason for publishing a new relay descriptor,
3443 so we have a better chance of hunting down instances of bug 1810.
3444 Resolves ticket 3252.
3445 - Revise most log messages that refer to nodes by nickname to
3446 instead use the "$key=nickname at address" format. This should be
3447 more useful, especially since nicknames are less and less likely
3448 to be unique. Resolves ticket 3045.
3449 - Log (at info level) when purging pieces of hidden-service-client
3450 state because of SIGNAL NEWNYM.
3453 - Remove undocumented option "-F" from tor-resolve: it hasn't done
3454 anything since 0.2.1.16-rc.
3457 Changes in version 0.2.2.27-beta - 2011-05-18
3458 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
3459 release, and also adds a few more general bugfixes.
3462 - Fix a crash bug when changing bridges in a running Tor process.
3463 Fixes bug 3213; bugfix on 0.2.2.26-beta.
3464 - When the controller configures a new bridge, don't wait 10 to 60
3465 seconds before trying to fetch its descriptor. Bugfix on
3466 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
3469 - Require that onion keys have exponent 65537 in microdescriptors too.
3470 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
3471 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
3472 Changed the limit to 512 characters by removing base64 newlines.
3473 Fixes bug 2752. Fix by Michael Yakubovich.
3474 - When a client starts or stops using bridges, never use a circuit
3475 that was built before the configuration change. This behavior could
3476 put at risk a user who uses bridges to ensure that her traffic
3477 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
3481 Changes in version 0.2.2.26-beta - 2011-05-17
3482 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
3483 also introduces a new "socksport auto" approach that should make it
3484 easier to run multiple Tors on the same system, and does a lot of
3485 cleanup to get us closer to a release candidate.
3487 o Security/privacy fixes:
3488 - Replace all potentially sensitive memory comparison operations
3489 with versions whose runtime does not depend on the data being
3490 compared. This will help resist a class of attacks where an
3491 adversary can use variations in timing information to learn
3492 sensitive data. Fix for one case of bug 3122. (Safe memcmp
3493 implementation by Robert Ransom based partially on code by DJB.)
3494 - When receiving a hidden service descriptor, check that it is for
3495 the hidden service we wanted. Previously, Tor would store any
3496 hidden service descriptors that a directory gave it, whether it
3497 wanted them or not. This wouldn't have let an attacker impersonate
3498 a hidden service, but it did let directories pre-seed a client
3499 with descriptors that it didn't want. Bugfix on 0.0.6.
3500 - On SIGHUP, do not clear out all TrackHostExits mappings, client
3501 DNS cache entries, and virtual address mappings: that's what
3502 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
3505 - The options SocksPort, ControlPort, and so on now all accept a
3506 value "auto" that opens a socket on an OS-selected port. A
3507 new ControlPortWriteToFile option tells Tor to write its
3508 actual control port or ports to a chosen file. If the option
3509 ControlPortFileGroupReadable is set, the file is created as
3510 group-readable. Now users can run two Tor clients on the same
3511 system without needing to manually mess with parameters. Resolves
3512 part of ticket 3076.
3513 - Set SO_REUSEADDR on all sockets, not just listeners. This should
3514 help busy exit nodes avoid running out of useable ports just
3515 because all the ports have been used in the near past. Resolves
3519 - New "GETINFO net/listeners/(type)" controller command to return
3520 a list of addresses and ports that are bound for listeners for a
3521 given connection type. This is useful when the user has configured
3522 "SocksPort auto" and the controller needs to know which port got
3523 chosen. Resolves another part of ticket 3076.
3524 - Add a new ControlSocketsGroupWritable configuration option: when
3525 it is turned on, ControlSockets are group-writeable by the default
3526 group of the current user. Patch by Jérémy Bobbio; implements
3528 - Tor now refuses to create a ControlSocket in a directory that is
3529 world-readable (or group-readable if ControlSocketsGroupWritable
3530 is 0). This is necessary because some operating systems do not
3531 enforce permissions on an AF_UNIX sockets. Permissions on the
3532 directory holding the socket, however, seems to work everywhere.
3533 - Rate-limit a warning about failures to download v2 networkstatus
3534 documents. Resolves part of bug 1352.
3535 - Backport code from 0.2.3.x that allows directory authorities to
3536 clean their microdescriptor caches. Needed to resolve bug 2230.
3537 - When an HTTPS proxy reports "403 Forbidden", we now explain
3538 what it means rather than calling it an unexpected status code.
3539 Closes bug 2503. Patch from Michael Yakubovich.
3540 - Update to the May 1 2011 Maxmind GeoLite Country database.
3543 - Authorities now clean their microdesc cache periodically and when
3544 reading from disk initially, not only when adding new descriptors.
3545 This prevents a bug where we could lose microdescriptors. Bugfix
3546 on 0.2.2.6-alpha. Fixes bug 2230.
3547 - Do not crash when our configuration file becomes unreadable, for
3548 example due to a permissions change, between when we start up
3549 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
3551 - Avoid a bug that would keep us from replacing a microdescriptor
3552 cache on Windows. (We would try to replace the file while still
3553 holding it open. That's fine on Unix, but Windows doesn't let us
3554 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
3555 - Add missing explanations for the authority-related torrc options
3556 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
3557 man page. Resolves issue 2379.
3558 - As an authority, do not upload our own vote or signature set to
3559 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
3560 it would get flagged as a duplicate. Resolves bug 3026.
3561 - Accept hidden service descriptors if we think we might be a hidden
3562 service directory, regardless of what our consensus says. This
3563 helps robustness, since clients and hidden services can sometimes
3564 have a more up-to-date view of the network consensus than we do,
3565 and if they think that the directory authorities list us a HSDir,
3566 we might actually be one. Related to bug 2732; bugfix on
3568 - When a controller changes TrackHostExits, remove mappings for
3569 hosts that should no longer have their exits tracked. Bugfix on
3571 - When a controller changes VirtualAddrNetwork, remove any mappings
3572 for hosts that were automapped to the old network. Bugfix on
3574 - When a controller changes one of the AutomapHosts* options, remove
3575 any mappings for hosts that should no longer be automapped. Bugfix
3577 - Do not reset the bridge descriptor download status every time we
3578 re-parse our configuration or get a configuration change. Fixes
3579 bug 3019; bugfix on 0.2.0.3-alpha.
3581 o Minor bugfixes (code cleanup):
3582 - When loading the microdesc journal, remember its current size.
3583 In 0.2.2, this helps prevent the microdesc journal from growing
3584 without limit on authorities (who are the only ones to use it in
3585 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
3586 Fix posted by "cypherpunks."
3587 - The microdesc journal is supposed to get rebuilt only if it is
3588 at least _half_ the length of the store, not _twice_ the length
3589 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
3590 - Fix a potential null-pointer dereference while computing a
3591 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
3593 - Avoid a possible null-pointer dereference when rebuilding the mdesc
3594 cache without actually having any descriptors to cache. Bugfix on
3595 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
3596 - If we fail to compute the identity digest of a v3 legacy keypair,
3597 warn, and don't use a buffer-full of junk instead. Bugfix on
3598 0.2.1.1-alpha; fixes bug 3106.
3599 - Resolve an untriggerable issue in smartlist_string_num_isin(),
3600 where if the function had ever in the future been used to check
3601 for the presence of a too-large number, it would have given an
3602 incorrect result. (Fortunately, we only used it for 16-bit
3603 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
3604 - Require that introduction point keys and onion handshake keys
3605 have a public exponent of 65537. Starts to fix bug 3207; bugfix
3609 - Caches no longer download and serve v2 networkstatus documents
3610 unless FetchV2Networkstatus flag is set: these documents haven't
3611 haven't been used by clients or relays since 0.2.0.x. Resolves
3615 Changes in version 0.2.3.1-alpha - 2011-05-05
3616 Tor 0.2.3.1-alpha adds some new experimental features, including support
3617 for an improved network IO backend, IOCP networking on Windows,
3618 microdescriptor caching, "fast-start" support for streams, and automatic
3619 home router configuration. There are also numerous internal improvements
3620 to try to make the code easier for developers to work with.
3622 This is the first alpha release in a new series, so expect there to be
3623 bugs. Users who would rather test out a more stable branch should
3624 stay with 0.2.2.x for now.
3627 - Tor can now optionally build with the "bufferevents" buffered IO
3628 backend provided by Libevent 2. To use this feature, make sure you
3629 have the latest possible version of Libevent, and pass the
3630 --enable-bufferevents flag to configure when building Tor from
3631 source. This feature will make our networking code more flexible,
3632 let us stack layers on each other, and let us use more efficient
3633 zero-copy transports where available.
3634 - As an experimental feature, Tor can use IOCP for networking on Windows.
3635 Once this code is tuned and optimized, it promises much better
3636 performance than the select-based backend we've used in the past. To
3637 try this feature, you must build Tor with Libevent 2, configure Tor
3638 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
3639 your torrc. There are known bugs here: only try this if you can help
3640 debug it as it breaks.
3641 - The EntryNodes option can now include country codes like {de} or IP
3642 addresses or network masks. Previously we had disallowed these options
3643 because we didn't have an efficient way to keep the list up to
3644 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
3645 - Exit nodes now accept and queue data on not-yet-connected streams.
3646 Previously, the client wasn't allowed to send data until the stream was
3647 connected, which slowed down all connections. This change will enable
3648 clients to perform a "fast-start" on streams and send data without
3649 having to wait for a confirmation that the stream has opened. (Patch
3650 from Ian Goldberg; implements the server side of Proposal 174.)
3651 - Tor now has initial support for automatic port mapping on the many
3652 home routers that support NAT-PMP or UPnP. (Not yet supported on
3653 Windows). To build the support code, you'll need to have libnatpnp
3654 library and/or the libminiupnpc library, and you'll need to enable the
3655 feature specifically by passing "--enable-upnp" and/or
3656 "--enable-natpnp" to configure. To turn it on, use the new
3657 PortForwarding option.
3658 - Caches now download, cache, and serve multiple "flavors" of the
3659 consensus, including a flavor that describes microdescriptors.
3660 - Caches now download, cache, and serve microdescriptors -- small
3661 summaries of router descriptors that are authenticated by all of the
3662 directory authorities. Once enough caches are running this code,
3663 clients will be able to save significant amounts of directory bandwidth
3664 by downloading microdescriptors instead of router descriptors.
3667 - Make logging resolution configurable with a new LogTimeGranularity
3668 option, and change the default from 1 millisecond to 1 second.
3669 Implements enhancement 1668.
3670 - We log which torrc file we're using on startup. Implements ticket
3672 - Ordinarily, Tor does not count traffic from private addresses (like
3673 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
3674 There is now a new option, CountPrivateBandwidth, to disable this
3675 behavior. Patch from Daniel Cagara.
3676 - New --enable-static-tor configure option for building Tor as
3677 statically as possible. Idea, general hackery and thoughts from
3678 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
3680 - If you set the NumCPUs option to 0, Tor will now try to detect how
3681 many CPUs you have. This is the new default behavior.
3682 - Turn on directory request statistics by default and include them in
3683 extra-info descriptors. Don't break if we have no GeoIP database.
3684 - Relays that set "ConnDirectionStatistics 1" write statistics on the
3685 bidirectional use of connections to disk every 24 hours.
3686 - Add a GeoIP file digest to the extra-info descriptor. Implements
3688 - The NodeFamily option -- which let you declare that you want to
3689 consider nodes to be part of a family whether they list themselves
3690 that way or not -- now allows IP address ranges and country codes.
3691 - Add a new 'Heartbeat' log message type to periodically log a message
3692 describing Tor's status at level Notice. This feature is meant for
3693 operators who log at notice, and want to make sure that their Tor
3694 server is still working. Implementation by George Kadianakis.
3696 o Minor bugfixes (on 0.2.2.25-alpha):
3697 - When loading the microdesc journal, remember its current size.
3698 In 0.2.2, this helps prevent the microdesc journal from growing
3699 without limit on authorities (who are the only ones to use it in
3700 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
3701 Fix posted by "cypherpunks."
3702 - The microdesc journal is supposed to get rebuilt only if it is
3703 at least _half_ the length of the store, not _twice_ the length
3704 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
3705 - If as an authority we fail to compute the identity digest of a v3
3706 legacy keypair, warn, and don't use a buffer-full of junk instead.
3707 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
3708 - Authorities now clean their microdesc cache periodically and when
3709 reading from disk initially, not only when adding new descriptors.
3710 This prevents a bug where we could lose microdescriptors. Bugfix
3713 o Minor features (controller):
3714 - Add a new SIGNAL event to the controller interface so that
3715 controllers can be notified when Tor handles a signal. Resolves
3716 issue 1955. Patch by John Brooks.
3717 - Add a new GETINFO option to get total bytes read and written. Patch
3718 from pipe, revised by atagar. Resolves ticket 2345.
3719 - Implement some GETINFO controller fields to provide information about
3720 the Tor process's pid, euid, username, and resource limits.
3723 - Our build system requires automake 1.6 or later to create the
3724 Makefile.in files. Previously, you could have used 1.4.
3725 This only affects developers and people building Tor from git;
3726 people who build Tor from the source distribution without changing
3727 the Makefile.am files should be fine.
3728 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
3729 so on. This is more robust against some of the failure modes
3730 associated with running the autotools pieces on their own.
3732 o Minor packaging issues:
3733 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
3734 already created. Patch from Andreas Stieger. Fixes bug 2573.
3736 o Code simplifications and refactoring:
3737 - A major revision to our internal node-selecting and listing logic.
3738 Tor already had at least two major ways to look at the question of
3739 "which Tor servers do we know about": a list of router descriptors,
3740 and a list of entries in the current consensus. With
3741 microdescriptors, we're adding a third. Having so many systems
3742 without an abstraction layer over them was hurting the codebase.
3743 Now, we have a new "node_t" abstraction that presents a consistent
3744 interface to a client's view of a Tor node, and holds (nearly) all
3745 of the mutable state formerly in routerinfo_t and routerstatus_t.
3746 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
3747 no longer link against Libevent: they never used it, but
3748 our library structure used to force them to link it.
3751 - Remove some old code to work around even older versions of Tor that
3752 used forked processes to handle DNS requests. Such versions of Tor
3753 are no longer in use as servers.
3755 o Documentation fixes:
3756 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
3757 - Add missing documentation for the authority-related torrc options
3758 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
3762 Changes in version 0.2.2.25-alpha - 2011-04-29
3763 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
3764 robust, routers no longer overreport their bandwidth, Win7 should crash
3765 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
3766 now prevents hidden service-related activity from being linkable. It
3767 provides more information to Vidalia so you can see if your bridge is
3768 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
3769 StrictNodes configuration options to make them more reliable, more
3770 understandable, and more regularly applied. If you use those options,
3771 please see the revised documentation for them in the manual page.
3774 - Relays were publishing grossly inflated bandwidth values because
3775 they were writing their state files wrong--now they write the
3776 correct value. Also, resume reading bandwidth history from the
3777 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
3778 - Improve hidden service robustness: When we find that we have
3779 extended a hidden service's introduction circuit to a relay not
3780 listed as an introduction point in the HS descriptor we currently
3781 have, retry with an introduction point from the current
3782 descriptor. Previously we would just give up. Fixes bugs 1024 and
3783 1930; bugfix on 0.2.0.10-alpha.
3784 - Clients now stop trying to use an exit node associated with a given
3785 destination by TrackHostExits if they fail to reach that exit node.
3786 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
3787 - Fix crash bug on platforms where gmtime and localtime can return
3788 NULL. Windows 7 users were running into this one. Fixes part of bug
3789 2077. Bugfix on all versions of Tor. Found by boboper.
3791 o Security and stability fixes:
3792 - Don't double-free a parsable, but invalid, microdescriptor, even if
3793 it is followed in the blob we're parsing by an unparsable
3794 microdescriptor. Fixes an issue reported in a comment on bug 2954.
3795 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
3796 - If the Nickname configuration option isn't given, Tor would pick a
3797 nickname based on the local hostname as the nickname for a relay.
3798 Because nicknames are not very important in today's Tor and the
3799 "Unnamed" nickname has been implemented, this is now problematic
3800 behavior: It leaks information about the hostname without being
3801 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
3802 introduced the Unnamed nickname. Reported by tagnaq.
3803 - Fix an uncommon assertion failure when running with DNSPort under
3804 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3805 - Avoid linkability based on cached hidden service descriptors: forget
3806 all hidden service descriptors cached as a client when processing a
3807 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3810 - Export GeoIP information on bridge usage to controllers even if we
3811 have not yet been running for 24 hours. Now Vidalia bridge operators
3812 can get more accurate and immediate feedback about their
3813 contributions to the network.
3815 o Major features and bugfixes (node selection):
3816 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
3817 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
3818 options. Previously, we had been ambiguous in describing what
3819 counted as an "exit" node, and what operations exactly "StrictNodes
3820 0" would permit. This created confusion when people saw nodes built
3821 through unexpected circuits, and made it hard to tell real bugs from
3822 surprises. Now the intended behavior is:
3823 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
3824 a node that delivers user traffic outside the Tor network.
3825 . "Entry", in the context of EntryNodes, means a node used as the
3826 first hop of a multihop circuit. It doesn't include direct
3827 connections to directory servers.
3828 . "ExcludeNodes" applies to all nodes.
3829 . "StrictNodes" changes the behavior of ExcludeNodes only. When
3830 StrictNodes is set, Tor should avoid all nodes listed in
3831 ExcludeNodes, even when it will make user requests fail. When
3832 StrictNodes is *not* set, then Tor should follow ExcludeNodes
3833 whenever it can, except when it must use an excluded node to
3834 perform self-tests, connect to a hidden service, provide a
3835 hidden service, fulfill a .exit request, upload directory
3836 information, or fetch directory information.
3837 Collectively, the changes to implement the behavior fix bug 1090.
3838 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
3839 a node is listed in both, it's treated as excluded.
3840 - ExcludeNodes now applies to directory nodes -- as a preference if
3841 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
3842 Don't exclude all the directory authorities and set StrictNodes to 1
3843 unless you really want your Tor to break.
3844 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
3845 - ExcludeExitNodes now overrides .exit requests.
3846 - We don't use bridges listed in ExcludeNodes.
3847 - When StrictNodes is 1:
3848 . We now apply ExcludeNodes to hidden service introduction points
3849 and to rendezvous points selected by hidden service users. This
3850 can make your hidden service less reliable: use it with caution!
3851 . If we have used ExcludeNodes on ourself, do not try relay
3852 reachability self-tests.
3853 . If we have excluded all the directory authorities, we will not
3854 even try to upload our descriptor if we're a relay.
3855 . Do not honor .exit requests to an excluded node.
3856 - Remove a misfeature that caused us to ignore the Fast/Stable flags
3857 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
3858 - When the set of permitted nodes changes, we now remove any mappings
3859 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
3861 - We never cannibalize a circuit that had excluded nodes on it, even
3862 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
3863 - Revert a change where we would be laxer about attaching streams to
3864 circuits than when building the circuits. This was meant to prevent
3865 a set of bugs where streams were never attachable, but our improved
3866 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
3867 - Keep track of how many times we launch a new circuit to handle a
3868 given stream. Too many launches could indicate an inconsistency
3869 between our "launch a circuit to handle this stream" logic and our
3870 "attach this stream to one of the available circuits" logic.
3871 - Improve log messages related to excluded nodes.
3874 - Fix a spurious warning when moving from a short month to a long
3875 month on relays with month-based BandwidthAccounting. Bugfix on
3876 0.2.2.17-alpha; fixes bug 3020.
3877 - When a client finds that an origin circuit has run out of 16-bit
3878 stream IDs, we now mark it as unusable for new streams. Previously,
3879 we would try to close the entire circuit. Bugfix on 0.0.6.
3880 - Add a forgotten cast that caused a compile warning on OS X 10.6.
3881 Bugfix on 0.2.2.24-alpha.
3882 - Be more careful about reporting the correct error from a failed
3883 connect() system call. Under some circumstances, it was possible to
3884 look at an incorrect value for errno when sending the end reason.
3885 Bugfix on 0.1.0.1-rc.
3886 - Correctly handle an "impossible" overflow cases in connection byte
3887 counting, where we write or read more than 4GB on an edge connection
3888 in a single second. Bugfix on 0.1.2.8-beta.
3889 - Correct the warning displayed when a rendezvous descriptor exceeds
3890 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3892 - Clients and hidden services now use HSDir-flagged relays for hidden
3893 service descriptor downloads and uploads even if the relays have no
3894 DirPort set and the client has disabled TunnelDirConns. This will
3895 eventually allow us to give the HSDir flag to relays with no
3896 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
3897 - Downgrade "no current certificates known for authority" message from
3898 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
3899 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
3900 2917. Bugfix on 0.1.1.1-alpha.
3901 - Only limit the lengths of single HS descriptors, even when multiple
3902 HS descriptors are published to an HSDir relay in a single POST
3903 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
3904 - Write the current time into the LastWritten line in our state file,
3905 rather than the time from the previous write attempt. Also, stop
3906 trying to use a time of -1 in our log statements. Fixes bug 3039;
3907 bugfix on 0.2.2.14-alpha.
3908 - Be more consistent in our treatment of file system paths. "~" should
3909 get expanded to the user's home directory in the Log config option.
3910 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
3911 feature for the -f and --DataDirectory options.
3914 - Make sure every relay writes a state file at least every 12 hours.
3915 Previously, a relay could go for weeks without writing its state
3916 file, and on a crash could lose its bandwidth history, capacity
3917 estimates, client country statistics, and so on. Addresses bug 3012.
3918 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
3919 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
3920 clients are already deprecated because of security bugs.
3921 - Don't allow v0 hidden service authorities to act as clients.
3922 Required by fix for bug 3000.
3923 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
3924 by fix for bug 3000.
3925 - Ensure that no empty [dirreq-](read|write)-history lines are added
3926 to an extrainfo document. Implements ticket 2497.
3928 o Code simplification and refactoring:
3929 - Remove workaround code to handle directory responses from servers
3930 that had bug 539 (they would send HTTP status 503 responses _and_
3931 send a body too). Since only server versions before
3932 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
3933 keep the workaround in place.
3934 - Remove the old 'fuzzy time' logic. It was supposed to be used for
3935 handling calculations where we have a known amount of clock skew and
3936 an allowed amount of unknown skew. But we only used it in three
3937 places, and we never adjusted the known/unknown skew values. This is
3938 still something we might want to do someday, but if we do, we'll
3939 want to do it differently.
3940 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3941 None of the cases where we did this before were wrong, but by making
3942 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3943 - Use GetTempDir to find the proper temporary directory location on
3944 Windows when generating temporary files for the unit tests. Patch by
3948 Changes in version 0.2.2.24-alpha - 2011-04-08
3949 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
3950 prevented Tor clients from effectively using "multihomed" bridges,
3951 that is, bridges that listen on multiple ports or IP addresses so users
3952 can continue to use some of their addresses even if others get blocked.
3955 - Fix a bug where bridge users who configure the non-canonical
3956 address of a bridge automatically switch to its canonical
3957 address. If a bridge listens at more than one address, it should be
3958 able to advertise those addresses independently and any non-blocked
3959 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
3961 - If you configured Tor to use bridge A, and then quit and
3962 configured Tor to use bridge B instead, it would happily continue
3963 to use bridge A if it's still reachable. While this behavior is
3964 a feature if your goal is connectivity, in some scenarios it's a
3965 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
3966 - Directory authorities now use data collected from their own
3967 uptime observations when choosing whether to assign the HSDir flag
3968 to relays, instead of trusting the uptime value the relay reports in
3969 its descriptor. This change helps prevent an attack where a small
3970 set of nodes with frequently-changing identity keys can blackhole
3971 a hidden service. (Only authorities need upgrade; others will be
3972 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
3975 - When we restart our relay, we might get a successful connection
3976 from the outside before we've started our reachability tests,
3977 triggering a warning: "ORPort found reachable, but I have no
3978 routerinfo yet. Failing to inform controller of success." This
3979 bug was harmless unless Tor is running under a controller
3980 like Vidalia, in which case the controller would never get a
3981 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3983 - Make directory authorities more accurate at recording when
3984 relays that have failed several reachability tests became
3985 unreachable, so we can provide more accuracy at assigning Stable,
3986 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
3987 - Fix an issue that prevented static linking of libevent on
3988 some platforms (notably Linux). Fixes bug 2698; bugfix on
3989 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
3990 the --with-static-libevent configure option).
3991 - We now ask the other side of a stream (the client or the exit)
3992 for more data on that stream when the amount of queued data on
3993 that stream dips low enough. Previously, we wouldn't ask the
3994 other side for more data until either it sent us more data (which
3995 it wasn't supposed to do if it had exhausted its window!) or we
3996 had completely flushed all our queued data. This flow control fix
3997 should improve throughput. Fixes bug 2756; bugfix on the earliest
3998 released versions of Tor (svn commit r152).
3999 - Avoid a double-mark-for-free warning when failing to attach a
4000 transparent proxy connection. (We thought we had fixed this in
4001 0.2.2.23-alpha, but it turns out our fix was checking the wrong
4002 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
4003 bug) and 0.2.2.23-alpha (the incorrect fix).
4004 - When warning about missing zlib development packages during compile,
4005 give the correct package names. Bugfix on 0.2.0.1-alpha.
4008 - Directory authorities now log the source of a rejected POSTed v3
4010 - Make compilation with clang possible when using
4011 --enable-gcc-warnings by removing two warning options that clang
4012 hasn't implemented yet and by fixing a few warnings. Implements
4014 - When expiring circuits, use microsecond timers rather than
4015 one-second timers. This can avoid an unpleasant situation where a
4016 circuit is launched near the end of one second and expired right
4017 near the beginning of the next, and prevent fluctuations in circuit
4019 - Use computed circuit-build timeouts to decide when to launch
4020 parallel introduction circuits for hidden services. (Previously,
4021 we would retry after 15 seconds.)
4022 - Update to the April 1 2011 Maxmind GeoLite Country database.
4025 - Create the /var/run/tor directory on startup on OpenSUSE if it is
4026 not already created. Patch from Andreas Stieger. Fixes bug 2573.
4028 o Documentation changes:
4029 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
4030 - Resolve all doxygen warnings except those for missing documentation.
4032 - Add doxygen documentation for more functions, fields, and types.
4035 Changes in version 0.2.2.23-alpha - 2011-03-08
4036 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
4037 they restart they don't lose their bandwidth capacity estimate. This
4038 release also fixes a diverse set of user-facing bugs, ranging from
4039 relays overrunning their rate limiting to clients falsely warning about
4040 clock skew to bridge descriptor leaks by our bridge directory authority.
4043 - Stop sending a CLOCK_SKEW controller status event whenever
4044 we fetch directory information from a relay that has a wrong clock.
4045 Instead, only inform the controller when it's a trusted authority
4046 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
4047 the rest of bug 1074.
4048 - Fix an assert in parsing router descriptors containing IPv6
4049 addresses. This one took down the directory authorities when
4050 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
4051 - Make the bridge directory authority refuse to answer directory
4052 requests for "all" descriptors. It used to include bridge
4053 descriptors in its answer, which was a major information leak.
4054 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
4055 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
4056 Tor would ignore their RelayBandwidthBurst setting,
4057 potentially using more bandwidth than expected. Bugfix on
4058 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
4059 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
4060 hidserv" in her torrc. The 'hidserv' argument never controlled
4061 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
4064 - Relays now save observed peak bandwidth throughput rates to their
4065 state file (along with total usage, which was already saved)
4066 so that they can determine their correct estimated bandwidth on
4067 restart. Resolves bug 1863, where Tor relays would reset their
4068 estimated bandwidth to 0 after restarting.
4069 - Directory authorities now take changes in router IP address and
4070 ORPort into account when determining router stability. Previously,
4071 if a router changed its IP or ORPort, the authorities would not
4072 treat it as having any downtime for the purposes of stability
4073 calculation, whereas clients would experience downtime since the
4074 change could take a while to propagate to them. Resolves issue 1035.
4075 - Enable Address Space Layout Randomization (ASLR) and Data Execution
4076 Prevention (DEP) by default on Windows to make it harder for
4077 attackers to exploit vulnerabilities. Patch from John Brooks.
4079 o Minor bugfixes (on 0.2.1.x and earlier):
4080 - Fix a rare crash bug that could occur when a client was configured
4081 with a large number of bridges. Fixes bug 2629; bugfix on
4082 0.2.1.2-alpha. Bugfix by trac user "shitlei".
4083 - Avoid a double mark-for-free warning when failing to attach a
4084 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
4086 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
4087 found by "cypherpunks". This bug was introduced before the first
4088 Tor release, in svn commit r110.
4089 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
4090 don't mention them in the manpage. Fixes bug 2450; issue
4091 spotted by keb and G-Lo.
4092 - Fix a bug in bandwidth history state parsing that could have been
4093 triggered if a future version of Tor ever changed the timing
4094 granularity at which bandwidth history is measured. Bugfix on
4096 - When a relay decides that its DNS is too broken for it to serve
4097 as an exit server, it advertised itself as a non-exit, but
4098 continued to act as an exit. This could create accidental
4099 partitioning opportunities for users. Instead, if a relay is
4100 going to advertise reject *:* as its exit policy, it should
4101 really act with exit policy "reject *:*". Fixes bug 2366.
4102 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
4103 - In the special case where you configure a public exit relay as your
4104 bridge, Tor would be willing to use that exit relay as the last
4105 hop in your circuit as well. Now we fail that circuit instead.
4106 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
4107 - Fix a bug with our locking implementation on Windows that couldn't
4108 correctly detect when a file was already locked. Fixes bug 2504,
4109 bugfix on 0.2.1.6-alpha.
4110 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
4111 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
4113 - Set target port in get_interface_address6() correctly. Bugfix
4114 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
4115 - Directory authorities are now more robust to hops back in time
4116 when calculating router stability. Previously, if a run of uptime
4117 or downtime appeared to be negative, the calculation could give
4118 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
4120 - Fix an assert that got triggered when using the TestingTorNetwork
4121 configuration option and then issuing a GETINFO config-text control
4122 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
4124 o Minor bugfixes (on 0.2.2.x):
4125 - Clients should not weight BadExit nodes as Exits in their node
4126 selection. Similarly, directory authorities should not count BadExit
4127 bandwidth as Exit bandwidth when computing bandwidth-weights.
4128 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
4129 - Correctly clear our dir_read/dir_write history when there is an
4130 error parsing any bw history value from the state file. Bugfix on
4132 - Resolve a bug in verifying signatures of directory objects
4133 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
4134 Fixes bug 2409. Found by "piebeer".
4135 - Bridge authorities no longer crash on SIGHUP when they try to
4136 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
4140 - Log less aggressively about circuit timeout changes, and improve
4141 some other circuit timeout messages. Resolves bug 2004.
4142 - Log a little more clearly about the times at which we're no longer
4143 accepting new connections. Resolves bug 2181.
4144 - Reject attempts at the client side to open connections to private
4145 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
4146 a randomly chosen exit node. Attempts to do so are always
4147 ill-defined, generally prevented by exit policies, and usually
4148 in error. This will also help to detect loops in transparent
4149 proxy configurations. You can disable this feature by setting
4150 "ClientRejectInternalAddresses 0" in your torrc.
4151 - Always treat failure to allocate an RSA key as an unrecoverable
4153 - Update to the March 1 2011 Maxmind GeoLite Country database.
4155 o Minor features (log subsystem):
4156 - Add documentation for configuring logging at different severities in
4157 different log domains. We've had this feature since 0.2.1.1-alpha,
4158 but for some reason it never made it into the manpage. Fixes
4160 - Make it simpler to specify "All log domains except for A and B".
4161 Previously you needed to say "[*,~A,~B]". Now you can just say
4163 - Add a "LogMessageDomains 1" option to include the domains of log
4164 messages along with the messages. Without this, there's no way
4165 to use log domains without reading the source or doing a lot
4168 o Packaging changes:
4169 - Stop shipping the Tor specs files and development proposal documents
4170 in the tarball. They are now in a separate git repository at
4171 git://git.torproject.org/torspec.git
4174 Changes in version 0.2.1.30 - 2011-02-23
4175 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
4176 change is a slight tweak to Tor's TLS handshake that makes relays
4177 and bridges that run this new version reachable from Iran again.
4178 We don't expect this tweak will win the arms race long-term, but it
4179 buys us time until we roll out a better solution.
4182 - Stop sending a CLOCK_SKEW controller status event whenever
4183 we fetch directory information from a relay that has a wrong clock.
4184 Instead, only inform the controller when it's a trusted authority
4185 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
4186 the rest of bug 1074.
4187 - Fix a bounds-checking error that could allow an attacker to
4188 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
4190 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
4191 Tor would ignore their RelayBandwidthBurst setting,
4192 potentially using more bandwidth than expected. Bugfix on
4193 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
4194 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
4195 hidserv" in her torrc. The 'hidserv' argument never controlled
4196 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
4199 - Adjust our TLS Diffie-Hellman parameters to match those used by
4201 - Update to the February 1 2011 Maxmind GeoLite Country database.
4204 - Check for and reject overly long directory certificates and
4205 directory tokens before they have a chance to hit any assertions.
4206 Bugfix on 0.2.1.28. Found by "doorss".
4207 - Bring the logic that gathers routerinfos and assesses the
4208 acceptability of circuits into line. This prevents a Tor OP from
4209 getting locked in a cycle of choosing its local OR as an exit for a
4210 path (due to a .exit request) and then rejecting the circuit because
4211 its OR is not listed yet. It also prevents Tor clients from using an
4212 OR running in the same instance as an exit (due to a .exit request)
4213 if the OR does not meet the same requirements expected of an OR
4214 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
4216 o Packaging changes:
4217 - Stop shipping the Tor specs files and development proposal documents
4218 in the tarball. They are now in a separate git repository at
4219 git://git.torproject.org/torspec.git
4220 - Do not include Git version tags as though they are SVN tags when
4221 generating a tarball from inside a repository that has switched
4222 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
4225 Changes in version 0.2.2.22-alpha - 2011-01-25
4226 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
4227 main other change is a slight tweak to Tor's TLS handshake that makes
4228 relays and bridges that run this new version reachable from Iran again.
4229 We don't expect this tweak will win the arms race long-term, but it
4230 will buy us a bit more time until we roll out a better solution.
4233 - Fix a bounds-checking error that could allow an attacker to
4234 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
4236 - Don't assert when changing from bridge to relay or vice versa
4237 via the controller. The assert happened because we didn't properly
4238 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
4239 bug 2433. Reported by bastik.
4242 - Adjust our TLS Diffie-Hellman parameters to match those used by
4244 - Provide a log message stating which geoip file we're parsing
4245 instead of just stating that we're parsing the geoip file.
4246 Implements ticket 2432.
4249 - Check for and reject overly long directory certificates and
4250 directory tokens before they have a chance to hit any assertions.
4251 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
4254 Changes in version 0.2.2.21-alpha - 2011-01-15
4255 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
4256 continues our recent code security audit work. The main fix resolves
4257 a remote heap overflow vulnerability that can allow remote code
4258 execution (CVE-2011-0427). Other fixes address a variety of assert
4259 and crash bugs, most of which we think are hard to exploit remotely.
4261 o Major bugfixes (security), also included in 0.2.1.29:
4262 - Fix a heap overflow bug where an adversary could cause heap
4263 corruption. This bug probably allows remote code execution
4264 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
4266 - Prevent a denial-of-service attack by disallowing any
4267 zlib-compressed data whose compression factor is implausibly
4268 high. Fixes part of bug 2324; reported by "doorss".
4269 - Zero out a few more keys in memory before freeing them. Fixes
4270 bug 2384 and part of bug 2385. These key instances found by
4271 "cypherpunks", based on Andrew Case's report about being able
4272 to find sensitive data in Tor's memory space if you have enough
4273 permissions. Bugfix on 0.0.2pre9.
4275 o Major bugfixes (crashes), also included in 0.2.1.29:
4276 - Prevent calls to Libevent from inside Libevent log handlers.
4277 This had potential to cause a nasty set of crashes, especially
4278 if running Libevent with debug logging enabled, and running
4279 Tor with a controller watching for low-severity log messages.
4280 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
4281 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
4282 underflow errors there too. Fixes the other part of bug 2324.
4283 - Fix a bug where we would assert if we ever had a
4284 cached-descriptors.new file (or another file read directly into
4285 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
4286 on 0.2.1.25. Found by doorss.
4287 - Fix some potential asserts and parsing issues with grossly
4288 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
4291 o Minor bugfixes (other), also included in 0.2.1.29:
4292 - Fix a bug with handling misformed replies to reverse DNS lookup
4293 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
4294 bug reported by doorss.
4295 - Fix compilation on mingw when a pthreads compatibility library
4296 has been installed. (We don't want to use it, so we shouldn't
4297 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
4298 - Fix a bug where we would declare that we had run out of virtual
4299 addresses when the address space was only half-exhausted. Bugfix
4301 - Correctly handle the case where AutomapHostsOnResolve is set but
4302 no virtual addresses are available. Fixes bug 2328; bugfix on
4303 0.1.2.1-alpha. Bug found by doorss.
4304 - Correctly handle wrapping around when we run out of virtual
4305 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
4307 o Minor features, also included in 0.2.1.29:
4308 - Update to the January 1 2011 Maxmind GeoLite Country database.
4309 - Introduce output size checks on all of our decryption functions.
4311 o Build changes, also included in 0.2.1.29:
4312 - Tor does not build packages correctly with Automake 1.6 and earlier;
4313 added a check to Makefile.am to make sure that we're building with
4314 Automake 1.7 or later.
4315 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
4316 because we built it with a too-old version of automake. Thus that
4317 release broke ./configure --enable-openbsd-malloc, which is popular
4318 among really fast exit relays on Linux.
4320 o Major bugfixes, new in 0.2.2.21-alpha:
4321 - Prevent crash/heap corruption when the cbtnummodes consensus
4322 parameter is set to 0 or large values. Fixes bug 2317; bugfix
4325 o Major features, new in 0.2.2.21-alpha:
4326 - Introduce minimum/maximum values that clients will believe
4327 from the consensus. Now we'll have a better chance to avoid crashes
4328 or worse when a consensus param has a weird value.
4330 o Minor features, new in 0.2.2.21-alpha:
4331 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
4332 used on bridges, and it makes bridge scanning somewhat easier.
4333 - If writing the state file to disk fails, wait up to an hour before
4334 retrying again, rather than trying again each second. Fixes bug
4335 2346; bugfix on Tor 0.1.1.3-alpha.
4336 - Make Libevent log messages get delivered to controllers later,
4337 and not from inside the Libevent log handler. This prevents unsafe
4338 reentrant Libevent calls while still letting the log messages
4340 - Detect platforms that brokenly use a signed size_t, and refuse to
4341 build there. Found and analyzed by doorss and rransom.
4342 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
4345 o Minor bugfixes, new in 0.2.2.21-alpha:
4346 - Handle SOCKS messages longer than 128 bytes long correctly, rather
4347 than waiting forever for them to finish. Fixes bug 2330; bugfix
4348 on 0.2.0.16-alpha. Found by doorss.
4349 - Add assertions to check for overflow in arguments to
4350 base32_encode() and base32_decode(); fix a signed-unsigned
4351 comparison there too. These bugs are not actually reachable in Tor,
4352 but it's good to prevent future errors too. Found by doorss.
4353 - Correctly detect failures to create DNS requests when using Libevent
4354 versions before v2. (Before Libevent 2, we used our own evdns
4355 implementation. Its return values for Libevent's evdns_resolve_*()
4356 functions are not consistent with those from Libevent.) Fixes bug
4357 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
4359 o Documentation, new in 0.2.2.21-alpha:
4360 - Document the default socks host and port (127.0.0.1:9050) for
4364 Changes in version 0.2.1.29 - 2011-01-15
4365 Tor 0.2.1.29 continues our recent code security audit work. The main
4366 fix resolves a remote heap overflow vulnerability that can allow remote
4367 code execution. Other fixes address a variety of assert and crash bugs,
4368 most of which we think are hard to exploit remotely.
4370 o Major bugfixes (security):
4371 - Fix a heap overflow bug where an adversary could cause heap
4372 corruption. This bug probably allows remote code execution
4373 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
4375 - Prevent a denial-of-service attack by disallowing any
4376 zlib-compressed data whose compression factor is implausibly
4377 high. Fixes part of bug 2324; reported by "doorss".
4378 - Zero out a few more keys in memory before freeing them. Fixes
4379 bug 2384 and part of bug 2385. These key instances found by
4380 "cypherpunks", based on Andrew Case's report about being able
4381 to find sensitive data in Tor's memory space if you have enough
4382 permissions. Bugfix on 0.0.2pre9.
4384 o Major bugfixes (crashes):
4385 - Prevent calls to Libevent from inside Libevent log handlers.
4386 This had potential to cause a nasty set of crashes, especially
4387 if running Libevent with debug logging enabled, and running
4388 Tor with a controller watching for low-severity log messages.
4389 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
4390 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
4391 underflow errors there too. Fixes the other part of bug 2324.
4392 - Fix a bug where we would assert if we ever had a
4393 cached-descriptors.new file (or another file read directly into
4394 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
4395 on 0.2.1.25. Found by doorss.
4396 - Fix some potential asserts and parsing issues with grossly
4397 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
4400 o Minor bugfixes (other):
4401 - Fix a bug with handling misformed replies to reverse DNS lookup
4402 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
4403 bug reported by doorss.
4404 - Fix compilation on mingw when a pthreads compatibility library
4405 has been installed. (We don't want to use it, so we shouldn't
4406 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
4407 - Fix a bug where we would declare that we had run out of virtual
4408 addresses when the address space was only half-exhausted. Bugfix
4410 - Correctly handle the case where AutomapHostsOnResolve is set but
4411 no virtual addresses are available. Fixes bug 2328; bugfix on
4412 0.1.2.1-alpha. Bug found by doorss.
4413 - Correctly handle wrapping around to when we run out of virtual
4414 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
4415 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
4416 because we built it with a too-old version of automake. Thus that
4417 release broke ./configure --enable-openbsd-malloc, which is popular
4418 among really fast exit relays on Linux.
4421 - Update to the January 1 2011 Maxmind GeoLite Country database.
4422 - Introduce output size checks on all of our decryption functions.
4425 - Tor does not build packages correctly with Automake 1.6 and earlier;
4426 added a check to Makefile.am to make sure that we're building with
4427 Automake 1.7 or later.
4430 Changes in version 0.2.2.20-alpha - 2010-12-17
4431 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
4432 exploitable bugs. We also fix a variety of other significant bugs,
4433 change the IP address for one of our directory authorities, and update
4434 the minimum version that Tor relays must run to join the network.
4437 - Fix a remotely exploitable bug that could be used to crash instances
4438 of Tor remotely by overflowing on the heap. Remote-code execution
4439 hasn't been confirmed, but can't be ruled out. Everyone should
4440 upgrade. Bugfix on the 0.1.1 series and later.
4441 - Fix a bug that could break accounting on 64-bit systems with large
4442 time_t values, making them hibernate for impossibly long intervals.
4443 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
4444 - Fix a logic error in directory_fetches_from_authorities() that
4445 would cause all _non_-exits refusing single-hop-like circuits
4446 to fetch from authorities, when we wanted to have _exits_ fetch
4447 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
4449 - Fix a stream fairness bug that would cause newer streams on a given
4450 circuit to get preference when reading bytes from the origin or
4451 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
4452 introduced before the first Tor release, in svn revision r152.
4454 o Directory authority changes:
4455 - Change IP address and ports for gabelmoo (v3 directory authority).
4458 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
4459 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
4460 - Fix an off-by-one error in calculating some controller command
4461 argument lengths. Fortunately, this mistake is harmless since
4462 the controller code does redundant NUL termination too. Found by
4463 boboper. Bugfix on 0.1.1.1-alpha.
4464 - Do not dereference NULL if a bridge fails to build its
4465 extra-info descriptor. Found by an anonymous commenter on
4466 Trac. Bugfix on 0.2.2.19-alpha.
4469 - Update to the December 1 2010 Maxmind GeoLite Country database.
4470 - Directory authorities now reject relays running any versions of
4471 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
4472 known bugs that keep RELAY_EARLY cells from working on rendezvous
4473 circuits. Followup to fix for bug 2081.
4474 - Directory authorities now reject relays running any version of Tor
4475 older than 0.2.0.26-rc. That version is the earliest that fetches
4476 current directory information correctly. Fixes bug 2156.
4477 - Report only the top 10 ports in exit-port stats in order not to
4478 exceed the maximum extra-info descriptor length of 50 KB. Implements
4482 Changes in version 0.2.1.28 - 2010-12-17
4483 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
4484 exploitable bugs. We also took this opportunity to change the IP address
4485 for one of our directory authorities, and to update the geoip database
4489 - Fix a remotely exploitable bug that could be used to crash instances
4490 of Tor remotely by overflowing on the heap. Remote-code execution
4491 hasn't been confirmed, but can't be ruled out. Everyone should
4492 upgrade. Bugfix on the 0.1.1 series and later.
4494 o Directory authority changes:
4495 - Change IP address and ports for gabelmoo (v3 directory authority).
4498 - Update to the December 1 2010 Maxmind GeoLite Country database.
4501 Changes in version 0.2.1.27 - 2010-11-23
4502 Yet another OpenSSL security patch broke its compatibility with Tor:
4503 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
4504 also took this opportunity to fix several crash bugs, integrate a new
4505 directory authority, and update the bundled GeoIP database.
4508 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
4509 No longer set the tlsext_host_name extension on server SSL objects;
4510 but continue to set it on client SSL objects. Our goal in setting
4511 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
4512 bugfix on 0.2.1.1-alpha.
4513 - Do not log messages to the controller while shrinking buffer
4514 freelists. Doing so would sometimes make the controller connection
4515 try to allocate a buffer chunk, which would mess up the internals
4516 of the freelist and cause an assertion failure. Fixes bug 1125;
4517 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
4518 - Learn our external IP address when we're a relay or bridge, even if
4519 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
4520 where we introduced bridge relays that don't need to publish to
4521 be useful. Fixes bug 2050.
4522 - Do even more to reject (and not just ignore) annotations on
4523 router descriptors received anywhere but from the cache. Previously
4524 we would ignore such annotations at first, but cache them to disk
4525 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
4526 - When you're using bridges and your network goes away and your
4527 bridges get marked as down, recover when you attempt a new socks
4528 connection (if the network is back), rather than waiting up to an
4529 hour to try fetching new descriptors for your bridges. Bugfix on
4530 0.2.0.3-alpha; fixes bug 1981.
4533 - Move to the November 2010 Maxmind GeoLite country db (rather
4534 than the June 2009 ip-to-country GeoIP db) for our statistics that
4535 count how many users relays are seeing from each country. Now we'll
4536 have more accurate data, especially for many African countries.
4538 o New directory authorities:
4539 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
4543 - Fix an assertion failure that could occur in directory caches or
4544 bridge users when using a very short voting interval on a testing
4545 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
4547 - Enforce multiplicity rules when parsing annotations. Bugfix on
4548 0.2.0.8-alpha. Found by piebeer.
4549 - Allow handshaking OR connections to take a full KeepalivePeriod
4550 seconds to handshake. Previously, we would close them after
4551 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
4552 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
4554 - When building with --enable-gcc-warnings on OpenBSD, disable
4555 warnings in system headers. This makes --enable-gcc-warnings
4556 pass on OpenBSD 4.8.
4559 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
4560 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
4561 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
4562 Servers can start sending this code when enough clients recognize
4563 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
4564 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
4565 Patch from mingw-san.
4568 - Remove the old debian/ directory from the main Tor distribution.
4569 The official Tor-for-debian git repository lives at the URL
4570 https://git.torproject.org/debian/tor.git
4571 - Stop shipping the old doc/website/ directory in the tarball. We
4572 changed the website format in late 2010, and what we shipped in
4573 0.2.1.26 really wasn't that useful anyway.
4576 Changes in version 0.2.2.19-alpha - 2010-11-22
4577 Yet another OpenSSL security patch broke its compatibility with Tor:
4578 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
4581 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
4582 No longer set the tlsext_host_name extension on server SSL objects;
4583 but continue to set it on client SSL objects. Our goal in setting
4584 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
4585 bugfix on 0.2.1.1-alpha.
4588 - Try harder not to exceed the maximum length of 50 KB when writing
4589 statistics to extra-info descriptors. This bug was triggered by very
4590 fast relays reporting exit-port, entry, and dirreq statistics.
4591 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
4592 - Publish a router descriptor even if generating an extra-info
4593 descriptor fails. Previously we would not publish a router
4594 descriptor without an extra-info descriptor; this can cause fast
4595 exit relays collecting exit-port statistics to drop from the
4596 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
4599 Changes in version 0.2.2.18-alpha - 2010-11-16
4600 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
4601 us lately, makes unpublished bridge relays able to detect their IP
4602 address, and fixes a wide variety of other bugs to get us much closer
4603 to a stable release.
4606 - Do even more to reject (and not just ignore) annotations on
4607 router descriptors received anywhere but from the cache. Previously
4608 we would ignore such annotations at first, but cache them to disk
4609 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
4610 - Do not log messages to the controller while shrinking buffer
4611 freelists. Doing so would sometimes make the controller connection
4612 try to allocate a buffer chunk, which would mess up the internals
4613 of the freelist and cause an assertion failure. Fixes bug 1125;
4614 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
4615 - Learn our external IP address when we're a relay or bridge, even if
4616 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
4617 where we introduced bridge relays that don't need to publish to
4618 be useful. Fixes bug 2050.
4619 - Maintain separate TLS contexts and certificates for incoming and
4620 outgoing connections in bridge relays. Previously we would use the
4621 same TLS contexts and certs for incoming and outgoing connections.
4622 Bugfix on 0.2.0.3-alpha; addresses bug 988.
4623 - Maintain separate identity keys for incoming and outgoing TLS
4624 contexts in bridge relays. Previously we would use the same
4625 identity keys for incoming and outgoing TLS contexts. Bugfix on
4626 0.2.0.3-alpha; addresses the other half of bug 988.
4627 - Avoid an assertion failure when we as an authority receive a
4628 duplicate upload of a router descriptor that we already have,
4629 but which we previously considered an obsolete descriptor.
4630 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
4631 - Avoid a crash bug triggered by looking at a dangling pointer while
4632 setting the network status consensus. Found by Robert Ransom.
4633 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
4634 - Fix a logic error where servers that _didn't_ act as exits would
4635 try to keep their server lists more aggressively up to date than
4636 exits, when it was supposed to be the other way around. Bugfix
4639 o Minor bugfixes (on Tor 0.2.1.x and earlier):
4640 - When we're trying to guess whether we know our IP address as
4641 a relay, we would log various ways that we failed to guess
4642 our address, but never log that we ended up guessing it
4643 successfully. Now add a log line to help confused and anxious
4644 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
4645 - Bring the logic that gathers routerinfos and assesses the
4646 acceptability of circuits into line. This prevents a Tor OP from
4647 getting locked in a cycle of choosing its local OR as an exit for a
4648 path (due to a .exit request) and then rejecting the circuit because
4649 its OR is not listed yet. It also prevents Tor clients from using an
4650 OR running in the same instance as an exit (due to a .exit request)
4651 if the OR does not meet the same requirements expected of an OR
4652 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
4653 - Correctly describe errors that occur when generating a TLS object.
4654 Previously we would attribute them to a failure while generating a
4655 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
4657 - Enforce multiplicity rules when parsing annotations. Bugfix on
4658 0.2.0.8-alpha. Found by piebeer.
4659 - Fix warnings that newer versions of autoconf produced during
4660 ./autogen.sh. These warnings appear to be harmless in our case,
4661 but they were extremely verbose. Fixes bug 2020.
4663 o Minor bugfixes (on Tor 0.2.2.x):
4664 - Enable protection of small arrays whenever we build with gcc
4665 hardening features, not only when also building with warnings
4666 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
4669 - Make hidden services work better in private Tor networks by not
4670 requiring any uptime to join the hidden service descriptor
4671 DHT. Implements ticket 2088.
4672 - Rate-limit the "your application is giving Tor only an IP address"
4673 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
4674 - When AllowSingleHopExits is set, print a warning to explain to the
4675 relay operator why most clients are avoiding her relay.
4676 - Update to the November 1 2010 Maxmind GeoLite Country database.
4678 o Code simplifications and refactoring:
4679 - When we fixed bug 1038 we had to put in a restriction not to send
4680 RELAY_EARLY cells on rend circuits. This was necessary as long
4681 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
4682 active. Now remove this obsolete check. Resolves bug 2081.
4683 - Some options used different conventions for uppercasing of acronyms
4684 when comparing manpage and source. Fix those in favor of the
4685 manpage, as it makes sense to capitalize acronyms.
4686 - Remove the torrc.complete file. It hasn't been kept up to date
4687 and users will have better luck checking out the manpage.
4688 - Remove the obsolete "NoPublish" option; it has been flagged
4689 as obsolete and has produced a warning since 0.1.1.18-rc.
4690 - Remove everything related to building the expert bundle for OS X.
4691 It has confused many users, doesn't work right on OS X 10.6,
4692 and is hard to get rid of once installed. Resolves bug 1274.
4695 Changes in version 0.2.2.17-alpha - 2010-09-30
4696 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
4697 to use one-hop circuits (which can put the exit relays at higher risk,
4698 plus unbalance the network); fixes a big bug in bandwidth accounting
4699 for relays that want to limit their monthly bandwidth use; fixes a
4700 big pile of bugs in how clients tolerate temporary network failure;
4701 and makes our adaptive circuit build timeout feature (which improves
4702 client performance if your network is fast while not breaking things
4703 if your network is slow) better handle bad networks.
4706 - Exit relays now try harder to block exit attempts from unknown
4707 relays, to make it harder for people to use them as one-hop proxies
4708 a la tortunnel. Controlled by the refuseunknownexits consensus
4709 parameter (currently enabled), or you can override it on your
4710 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
4712 o Major bugfixes (0.2.1.x and earlier):
4713 - Fix a bug in bandwidth accounting that could make us use twice
4714 the intended bandwidth when our interval start changes due to
4715 daylight saving time. Now we tolerate skew in stored vs computed
4716 interval starts: if the start of the period changes by no more than
4717 50% of the period's duration, we remember bytes that we transferred
4718 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
4719 - Always search the Windows system directory for system DLLs, and
4720 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
4721 - When you're using bridges and your network goes away and your
4722 bridges get marked as down, recover when you attempt a new socks
4723 connection (if the network is back), rather than waiting up to an
4724 hour to try fetching new descriptors for your bridges. Bugfix on
4725 0.2.0.3-alpha; fixes bug 1981.
4727 o Major bugfixes (on 0.2.2.x):
4728 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
4730 - Fix a segfault that could happen when operating a bridge relay with
4731 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
4732 - The consensus bandwidth-weights (used by clients to choose fast
4733 relays) entered an unexpected edge case in September where
4734 Exits were much scarcer than Guards, resulting in bad weight
4735 recommendations. Now we compute them using new constraints that
4736 should succeed in all cases. Also alter directory authorities to
4737 not include the bandwidth-weights line if they fail to produce
4738 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
4739 - When weighting bridges during path selection, we used to trust
4740 the bandwidths they provided in their descriptor, only capping them
4741 at 10MB/s. This turned out to be problematic for two reasons:
4742 Bridges could claim to handle a lot more traffic then they
4743 actually would, thus making more clients pick them and have a
4744 pretty effective DoS attack. The other issue is that new bridges
4745 that might not have a good estimate for their bw capacity yet
4746 would not get used at all unless no other bridges are available
4747 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
4749 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
4750 - Ignore cannibalized circuits when recording circuit build times.
4751 This should provide for a minor performance improvement for hidden
4752 service users using 0.2.2.14-alpha, and should remove two spurious
4753 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
4754 - Simplify the logic that causes us to decide if the network is
4755 unavailable for purposes of recording circuit build times. If we
4756 receive no cells whatsoever for the entire duration of a circuit's
4757 full measured lifetime, the network is probably down. Also ignore
4758 one-hop directory fetching circuit timeouts when calculating our
4759 circuit build times. These changes should hopefully reduce the
4760 cases where we see ridiculous circuit build timeouts for people
4761 with spotty wireless connections. Fixes part of bug 1772; bugfix
4763 - Prevent the circuit build timeout from becoming larger than
4764 the maximum build time we have ever seen. Also, prevent the time
4765 period for measurement circuits from becoming larger than twice that
4766 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
4769 - When we run out of directory information such that we can't build
4770 circuits, but then get enough that we can build circuits, log when
4771 we actually construct a circuit, so the user has a better chance of
4772 knowing what's going on. Fixes bug 1362.
4773 - Be more generous with how much bandwidth we'd use up (with
4774 accounting enabled) before entering "soft hibernation". Previously,
4775 we'd refuse new connections and circuits once we'd used up 95% of
4776 our allotment. Now, we use up 95% of our allotment, AND make sure
4777 that we have no more than 500MB (or 3 hours of expected traffic,
4778 whichever is lower) remaining before we enter soft hibernation.
4779 - If we've configured EntryNodes and our network goes away and/or all
4780 our entrynodes get marked down, optimistically retry them all when
4781 a new socks application request appears. Fixes bug 1882.
4782 - Add some more defensive programming for architectures that can't
4783 handle unaligned integer accesses. We don't know of any actual bugs
4784 right now, but that's the best time to fix them. Fixes bug 1943.
4785 - Support line continuations in the torrc config file. If a line
4786 ends with a single backslash character, the newline is ignored, and
4787 the configuration value is treated as continuing on the next line.
4790 o Minor bugfixes (on 0.2.1.x and earlier):
4791 - For bandwidth accounting, calculate our expected bandwidth rate
4792 based on the time during which we were active and not in
4793 soft-hibernation during the last interval. Previously, we were
4794 also considering the time spent in soft-hibernation. If this
4795 was a long time, we would wind up underestimating our bandwidth
4796 by a lot, and skewing our wakeup time towards the start of the
4797 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
4799 o Minor bugfixes (on 0.2.2.x):
4800 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
4801 which were disabled by the circuit build timeout changes in
4802 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
4803 - Make sure we don't warn about missing bandwidth weights when
4804 choosing bridges or other relays not in the consensus. Bugfix on
4805 0.2.2.10-alpha; fixes bug 1805.
4806 - In our logs, do not double-report signatures from unrecognized
4807 authorities both as "from unknown authority" and "not
4808 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
4811 Changes in version 0.2.2.16-alpha - 2010-09-17
4812 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
4813 evident at exit relays), and also continues to resolve all the little
4814 bugs that have been filling up trac lately.
4816 o Major bugfixes (stream-level fairness):
4817 - When receiving a circuit-level SENDME for a blocked circuit, try
4818 to package cells fairly from all the streams that had previously
4819 been blocked on that circuit. Previously, we had started with the
4820 oldest stream, and allowed each stream to potentially exhaust
4821 the circuit's package window. This gave older streams on any
4822 given circuit priority over newer ones. Fixes bug 1937. Detected
4823 originally by Camilo Viecco. This bug was introduced before the
4824 first Tor release, in svn commit r152: it is the new winner of
4825 the longest-lived bug prize.
4826 - When the exit relay got a circuit-level sendme cell, it started
4827 reading on the exit streams, even if had 500 cells queued in the
4828 circuit queue already, so the circuit queue just grew and grew in
4829 some cases. We fix this by not re-enabling reading on receipt of a
4830 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
4831 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
4833 - Newly created streams were allowed to read cells onto circuits,
4834 even if the circuit's cell queue was blocked and waiting to drain.
4835 This created potential unfairness, as older streams would be
4836 blocked, but newer streams would gladly fill the queue completely.
4837 We add code to detect this situation and prevent any stream from
4838 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
4842 - Update to the September 1 2010 Maxmind GeoLite Country database.
4843 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
4844 not. This would lead to a cookie that is still not group readable.
4845 Closes bug 1843. Suggested by katmagic.
4846 - When logging a rate-limited warning, we now mention how many messages
4847 got suppressed since the last warning.
4848 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
4849 do individual connection-level rate limiting of clients. The torrc
4850 config options with the same names trump the consensus params, if
4851 both are present. Replaces the old "bwconnrate" and "bwconnburst"
4852 consensus params which were broken from 0.2.2.7-alpha through
4853 0.2.2.14-alpha. Closes bug 1947.
4854 - When a router changes IP address or port, authorities now launch
4855 a new reachability test for it. Implements ticket 1899.
4856 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
4857 2 no signature, 4 required" messages about consensus signatures
4858 easier to read, and make sure they get logged at the same severity
4859 as the messages explaining which keys are which. Fixes bug 1290.
4860 - Don't warn when we have a consensus that we can't verify because
4861 of missing certificates, unless those certificates are ones
4862 that we have been trying and failing to download. Fixes bug 1145.
4863 - If you configure your bridge with a known identity fingerprint,
4864 and the bridge authority is unreachable (as it is in at least
4865 one country now), fall back to directly requesting the descriptor
4866 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
4868 - When building with --enable-gcc-warnings on OpenBSD, disable
4869 warnings in system headers. This makes --enable-gcc-warnings
4870 pass on OpenBSD 4.8.
4872 o Minor bugfixes (on 0.2.1.x and earlier):
4873 - Authorities will now attempt to download consensuses if their
4874 own efforts to make a live consensus have failed. This change
4875 means authorities that restart will fetch a valid consensus, and
4876 it means authorities that didn't agree with the current consensus
4877 will still fetch and serve it if it has enough signatures. Bugfix
4878 on 0.2.0.9-alpha; fixes bug 1300.
4879 - Ensure DNS requests launched by "RESOLVE" commands from the
4880 controller respect the __LeaveStreamsUnattached setconf options. The
4881 same goes for requests launched via DNSPort or transparent
4882 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
4883 - Allow handshaking OR connections to take a full KeepalivePeriod
4884 seconds to handshake. Previously, we would close them after
4885 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
4886 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
4888 - Rate-limit "Failed to hand off onionskin" warnings.
4889 - Never relay a cell for a circuit we have already destroyed.
4890 Between marking a circuit as closeable and finally closing it,
4891 it may have been possible for a few queued cells to get relayed,
4892 even though they would have been immediately dropped by the next
4893 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
4894 - Never queue a cell for a circuit that's already been marked
4896 - Never vote for a server as "Running" if we have a descriptor for
4897 it claiming to be hibernating, and that descriptor was published
4898 more recently than our last contact with the server. Bugfix on
4899 0.2.0.3-alpha; fixes bug 911.
4900 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
4903 o Minor bugfixes (on 0.2.2.x):
4904 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
4905 down if a directory fetch fails and you've configured either
4906 bridges or EntryNodes. The intent was to mark the relay as down
4907 _unless_ you're using bridges or EntryNodes, since if you are
4908 then you could quickly run out of entry points.
4909 - Fix the Windows directory-listing code. A bug introduced in
4910 0.2.2.14-alpha could make Windows directory servers forget to load
4911 some of their cached v2 networkstatus files.
4912 - Really allow clients to use relays as bridges. Fixes bug 1776;
4913 bugfix on 0.2.2.15-alpha.
4914 - Demote a warn to info that happens when the CellStatistics option
4915 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
4916 Reported by Moritz Bartl.
4917 - On Windows, build correctly either with or without Unicode support.
4918 This is necessary so that Tor can support fringe platforms like
4919 Windows 98 (which has no Unicode), or Windows CE (which has no
4920 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
4923 - Add a unit test for cross-platform directory-listing code.
4926 Changes in version 0.2.2.15-alpha - 2010-08-18
4927 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
4928 fixes a variety of other bugs that were preventing performance
4929 experiments from moving forward, fixes several bothersome memory leaks,
4930 and generally closes a lot of smaller bugs that have been filling up
4934 - Stop assigning the HSDir flag to relays that disable their
4935 DirPort (and thus will refuse to answer directory requests). This
4936 fix should dramatically improve the reachability of hidden services:
4937 hidden services and hidden service clients pick six HSDir relays
4938 to store and retrieve the hidden service descriptor, and currently
4939 about half of the HSDir relays will refuse to work. Bugfix on
4940 0.2.0.10-alpha; fixes part of bug 1693.
4941 - The PerConnBWRate and Burst config options, along with the
4942 bwconnrate and bwconnburst consensus params, initialized each conn's
4943 token bucket values only when the connection is established. Now we
4944 update them if the config options change, and update them every time
4945 we get a new consensus. Otherwise we can encounter an ugly edge
4946 case where we initialize an OR conn to client-level bandwidth,
4947 but then later the relay joins the consensus and we leave it
4948 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
4949 - Fix a regression that caused Tor to rebind its ports if it receives
4950 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
4953 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
4954 should give us approximately 40-50% more Guard-flagged nodes,
4955 improving the anonymity the Tor network can provide and also
4956 decreasing the dropoff in throughput that relays experience when
4957 they first get the Guard flag.
4958 - Allow enabling or disabling the *Statistics config options while
4962 - Update to the August 1 2010 Maxmind GeoLite Country database.
4963 - Have the controller interface give a more useful message than
4964 "Internal Error" in response to failed GETINFO requests.
4965 - Warn when the same option is provided more than once in a torrc
4966 file, on the command line, or in a single SETCONF statement, and
4967 the option is one that only accepts a single line. Closes bug 1384.
4968 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
4969 Patch from mingw-san.
4970 - Add support for the country code "{??}" in torrc options like
4971 ExcludeNodes, to indicate all routers of unknown country. Closes
4973 - Relays report the number of bytes spent on answering directory
4974 requests in extra-info descriptors similar to {read,write}-history.
4975 Implements enhancement 1790.
4977 o Minor bugfixes (on 0.2.1.x and earlier):
4978 - Complain if PublishServerDescriptor is given multiple arguments that
4979 include 0 or 1. This configuration will be rejected in the future.
4980 Bugfix on 0.2.0.1-alpha; closes bug 1107.
4981 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
4982 Bugfix on 0.2.0.13-alpha; closes bug 928.
4983 - Change "Application request when we're believed to be offline."
4984 notice to "Application request when we haven't used client
4985 functionality lately.", to clarify that it's not an error. Bugfix
4986 on 0.0.9.3; fixes bug 1222.
4987 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
4988 would return "551 Internal error" rather than "552 Unrecognized key
4989 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
4990 - Users can't configure a regular relay to be their bridge. It didn't
4991 work because when Tor fetched the bridge descriptor, it found
4992 that it already had it, and didn't realize that the purpose of the
4993 descriptor had changed. Now we replace routers with a purpose other
4994 than bridge with bridge descriptors when fetching them. Bugfix on
4995 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
4996 refetch the descriptor with router purpose 'general', disabling
4998 - Fix a rare bug in rend_fn unit tests: we would fail a test when
4999 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
5000 on 0.2.0.10-alpha; fixes bug 1808.
5001 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
5002 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
5003 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
5004 Servers can start sending this code when enough clients recognize
5005 it. Also update the spec to reflect this new reason. Bugfix on
5006 0.1.0.1-rc; fixes part of bug 1793.
5007 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
5008 when we switch from being a public relay to a bridge. Otherwise
5009 there will still be clients that see the relay in their consensus,
5010 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
5012 - Instead of giving an assertion failure on an internal mismatch
5013 on estimated freelist size, just log a BUG warning and try later.
5014 Mitigates but does not fix bug 1125.
5015 - Fix an assertion failure that could occur in caches or bridge users
5016 when using a very short voting interval on a testing network.
5017 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
5019 o Minor bugfixes (on 0.2.2.x):
5020 - Alter directory authorities to always consider Exit-flagged nodes
5021 as potential Guard nodes in their votes. The actual decision to
5022 use Exits as Guards is done in the consensus bandwidth weights.
5023 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
5024 - When the controller is reporting the purpose of circuits that
5025 didn't finish building before the circuit build timeout, it was
5026 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
5027 - Our libevent version parsing code couldn't handle versions like
5028 1.4.14b-stable and incorrectly warned the user about using an
5029 old and broken version of libevent. Treat 1.4.14b-stable like
5030 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
5032 - Don't use substitution references like $(VAR:MOD) when
5033 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
5034 '$(:x)' to 'x' rather than the empty string. This bites us in
5035 doc/ when configured with --disable-asciidoc. Bugfix on
5036 0.2.2.9-alpha; fixes bug 1773.
5037 - Remove a spurious hidden service server-side log notice about
5038 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
5040 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
5042 - Correctly report written bytes on linked connections. Found while
5043 implementing 1790. Bugfix on 0.2.2.4-alpha.
5044 - Fix three memory leaks: one in circuit_build_times_parse_state(),
5045 one in dirvote_add_signatures_to_pending_consensus(), and one every
5046 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
5047 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
5049 o Code simplifications and refactoring:
5050 - Take a first step towards making or.h smaller by splitting out
5051 function definitions for all source files in src/or/. Leave
5052 structures and defines in or.h for now.
5053 - Remove a bunch of unused function declarations as well as a block of
5054 #if 0'd code from the unit tests. Closes bug 1824.
5055 - New unit tests for exit-port history statistics; refactored exit
5056 statistics code to be more easily tested.
5057 - Remove the old debian/ directory from the main Tor distribution.
5058 The official Tor-for-debian git repository lives at the URL
5059 https://git.torproject.org/debian/tor.git
5062 Changes in version 0.2.2.14-alpha - 2010-07-12
5063 Tor 0.2.2.14-alpha greatly improves client-side handling of
5064 circuit build timeouts, which are used to estimate speed and improve
5065 performance. We also move to a much better GeoIP database, port Tor to
5066 Windows CE, introduce new compile flags that improve code security,
5067 add an eighth v3 directory authority, and address a lot of more
5071 - Tor directory authorities no longer crash when started with a
5072 cached-microdesc-consensus file in their data directory. Bugfix
5073 on 0.2.2.6-alpha; fixes bug 1532.
5074 - Treat an unset $HOME like an empty $HOME rather than triggering an
5075 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
5076 - Ignore negative and large circuit build timeout values that can
5077 happen during a suspend or hibernate. These values caused various
5078 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
5079 - Alter calculation of Pareto distribution parameter 'Xm' for
5080 Circuit Build Timeout learning to use the weighted average of the
5081 top N=3 modes (because we have three entry guards). Considering
5082 multiple modes should improve the timeout calculation in some cases,
5083 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
5085 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
5086 right censored distribution model. This approach improves over the
5087 synthetic timeout generation approach that was producing insanely
5088 high timeout values. Now we calculate build timeouts using truncated
5089 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
5090 - Do not close circuits that are under construction when they reach
5091 the circuit build timeout. Instead, leave them building (but do not
5092 use them) for up until the time corresponding to the 95th percentile
5093 on the Pareto CDF or 60 seconds, whichever is greater. This is done
5094 to provide better data for the new Pareto model. This percentile
5095 can be controlled by the consensus.
5098 - Move to the June 2010 Maxmind GeoLite country db (rather than the
5099 June 2009 ip-to-country GeoIP db) for our statistics that count
5100 how many users relays are seeing from each country. Now we have
5101 more accurate data for many African countries.
5102 - Port Tor to build and run correctly on Windows CE systems, using
5103 the wcecompat library. Contributed by Valerio Lupi.
5104 - New "--enable-gcc-hardening" ./configure flag (off by default)
5105 to turn on gcc compile time hardening options. It ensures
5106 that signed ints have defined behavior (-fwrapv), enables
5107 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
5108 with canaries (-fstack-protector-all), turns on ASLR protection if
5109 supported by the kernel (-fPIE, -pie), and adds additional security
5110 related warnings. Verified to work on Mac OS X and Debian Lenny.
5111 - New "--enable-linker-hardening" ./configure flag (off by default)
5112 to turn on ELF specific hardening features (relro, now). This does
5113 not work with Mac OS X or any other non-ELF binary format.
5115 o New directory authorities:
5116 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
5120 - New config option "WarnUnsafeSocks 0" disables the warning that
5121 occurs whenever Tor receives a socks handshake using a version of
5122 the socks protocol that can only provide an IP address (rather
5123 than a hostname). Setups that do DNS locally over Tor are fine,
5124 and we shouldn't spam the logs in that case.
5125 - Convert the HACKING file to asciidoc, and add a few new sections
5126 to it, explaining how we use Git, how we make changelogs, and
5127 what should go in a patch.
5128 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
5129 event, to give information on the current rate of circuit timeouts
5130 over our stored history.
5131 - Add ability to disable circuit build time learning via consensus
5132 parameter and via a LearnCircuitBuildTimeout config option. Also
5133 automatically disable circuit build time calculation if we are
5134 either a AuthoritativeDirectory, or if we fail to write our state
5135 file. Fixes bug 1296.
5136 - More gracefully handle corrupt state files, removing asserts
5137 in favor of saving a backup and resetting state.
5138 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
5142 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
5144 - When a2x fails, mention that the user could disable manpages instead
5145 of trying to fix their asciidoc installation.
5146 - Where available, use Libevent 2.0's periodic timers so that our
5147 once-per-second cleanup code gets called even more closely to
5148 once per second than it would otherwise. Fixes bug 943.
5149 - If you run a bridge that listens on multiple IP addresses, and
5150 some user configures a bridge address that uses a different IP
5151 address than your bridge writes in its router descriptor, and the
5152 user doesn't specify an identity key, their Tor would discard the
5153 descriptor because "it isn't one of our configured bridges", and
5154 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
5155 Bugfix on 0.2.0.3-alpha.
5156 - If OpenSSL fails to make a duplicate of a private or public key, log
5157 an error message and try to exit cleanly. May help with debugging
5158 if bug 1209 ever remanifests.
5159 - Save a couple bytes in memory allocation every time we escape
5160 certain characters in a string. Patch from Florian Zumbiehl.
5161 - Make it explicit that we don't cannibalize one-hop circuits. This
5162 happens in the wild, but doesn't turn out to be a problem because
5163 we fortunately don't use those circuits. Many thanks to outofwords
5164 for the initial analysis and to swissknife who confirmed that
5165 two-hop circuits are actually created.
5166 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
5167 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
5168 - Eliminate a case where a circuit build time warning was displayed
5169 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
5172 Changes in version 0.2.1.26 - 2010-05-02
5173 Tor 0.2.1.26 addresses the recent connection and memory overload
5174 problems we've been seeing on relays, especially relays with their
5175 DirPort open. If your relay has been crashing, or you turned it off
5176 because it used too many resources, give this release a try.
5178 This release also fixes yet another instance of broken OpenSSL libraries
5179 that was causing some relays to drop out of the consensus.
5182 - Teach relays to defend themselves from connection overload. Relays
5183 now close idle circuits early if it looks like they were intended
5184 for directory fetches. Relays are also more aggressive about closing
5185 TLS connections that have no circuits on them. Such circuits are
5186 unlikely to be re-used, and tens of thousands of them were piling
5187 up at the fast relays, causing the relays to run out of sockets
5188 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
5189 their directory fetches over TLS).
5190 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
5191 that claim to be earlier than 0.9.8m, but which have in reality
5192 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
5193 behavior. Possible fix for some cases of bug 1346.
5194 - Directory mirrors were fetching relay descriptors only from v2
5195 directory authorities, rather than v3 authorities like they should.
5196 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
5197 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
5200 - Finally get rid of the deprecated and now harmful notion of "clique
5201 mode", where directory authorities maintain TLS connections to
5205 - In the util/threads test, no longer free the test_mutex before all
5206 worker threads have finished. Bugfix on 0.2.1.6-alpha.
5207 - The master thread could starve the worker threads quite badly on
5208 certain systems, causing them to run only partially in the allowed
5209 window. This resulted in test failures. Now the master thread sleeps
5210 occasionally for a few microseconds while the two worker-threads
5211 compete for the mutex. Bugfix on 0.2.0.1-alpha.
5214 Changes in version 0.2.2.13-alpha - 2010-04-24
5215 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
5216 problems we've been seeing on relays, especially relays with their
5217 DirPort open. If your relay has been crashing, or you turned it off
5218 because it used too many resources, give this release a try.
5221 - Teach relays to defend themselves from connection overload. Relays
5222 now close idle circuits early if it looks like they were intended
5223 for directory fetches. Relays are also more aggressive about closing
5224 TLS connections that have no circuits on them. Such circuits are
5225 unlikely to be re-used, and tens of thousands of them were piling
5226 up at the fast relays, causing the relays to run out of sockets
5227 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
5228 their directory fetches over TLS).
5231 - Finally get rid of the deprecated and now harmful notion of "clique
5232 mode", where directory authorities maintain TLS connections to
5234 - Directory authorities now do an immediate reachability check as soon
5235 as they hear about a new relay. This change should slightly reduce
5236 the time between setting up a relay and getting listed as running
5237 in the consensus. It should also improve the time between setting
5238 up a bridge and seeing use by bridge users.
5239 - Directory authorities no longer launch a TLS connection to every
5240 relay as they startup. Now that we have 2k+ descriptors cached,
5241 the resulting network hiccup is becoming a burden. Besides,
5242 authorities already avoid voting about Running for the first half
5243 hour of their uptime.
5246 Changes in version 0.2.2.12-alpha - 2010-04-20
5247 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
5248 handle and vote on descriptors. It was causing relays to drop out of
5252 - Many relays have been falling out of the consensus lately because
5253 not enough authorities know about their descriptor for them to get
5254 a majority of votes. When we deprecated the v2 directory protocol,
5255 we got rid of the only way that v3 authorities can hear from each
5256 other about other descriptors. Now authorities examine every v3
5257 vote for new descriptors, and fetch them from that authority. Bugfix
5259 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
5260 and a warning in or.h related to bandwidth_weight_rule_t that
5261 prevented clean compile on OS X. Fixes bug 1363; bugfix on
5263 - Fix a segfault on relays when DirReqStatistics is enabled
5264 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
5268 - Demote a confusing TLS warning that relay operators might get when
5269 someone tries to talk to their OrPort. It is neither the operator's
5270 fault nor can they do anything about it. Fixes bug 1364; bugfix
5274 Changes in version 0.2.2.11-alpha - 2010-04-15
5275 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
5276 libraries that was causing some relays to drop out of the consensus.
5279 - Directory mirrors were fetching relay descriptors only from v2
5280 directory authorities, rather than v3 authorities like they should.
5281 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
5282 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
5283 - Fix a parsing error that made every possible value of
5284 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
5285 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
5286 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
5287 about the option without breaking older ones.
5288 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
5289 that claim to be earlier than 0.9.8m, but which have in reality
5290 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
5291 behavior. Possible fix for some cases of bug 1346.
5294 - Experiment with a more aggressive approach to preventing clients
5295 from making one-hop exit streams. Exit relays who want to try it
5296 out can set "RefuseUnknownExits 1" in their torrc, and then look
5297 for "Attempt by %s to open a stream" log messages. Let us know
5299 - Add support for statically linking zlib by specifying
5300 --enable-static-zlib, to go with our support for statically linking
5301 openssl and libevent. Resolves bug 1358.
5304 - Fix a segfault that happens whenever a Tor client that is using
5305 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
5307 - When we cleaned up the contrib/tor-exit-notice.html file, we left
5308 out the first line. Fixes bug 1295.
5309 - When building the manpage from a tarball, we required asciidoc, but
5310 the asciidoc -> roff/html conversion was already done for the
5311 tarball. Make 'make' complain only when we need asciidoc (either
5312 because we're compiling directly from git, or because we altered
5313 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
5314 - When none of the directory authorities vote on any params, Tor
5315 segfaulted when trying to make the consensus from the votes. We
5316 didn't trigger the bug in practice, because authorities do include
5317 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
5320 - In the util/threads test, no longer free the test_mutex before all
5321 worker threads have finished. Bugfix on 0.2.1.6-alpha.
5322 - The master thread could starve the worker threads quite badly on
5323 certain systems, causing them to run only partially in the allowed
5324 window. This resulted in test failures. Now the master thread sleeps
5325 occasionally for a few microseconds while the two worker-threads
5326 compete for the mutex. Bugfix on 0.2.0.1-alpha.
5329 Changes in version 0.2.2.10-alpha - 2010-03-07
5330 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
5331 could prevent relays from guessing their IP address correctly. It also
5332 starts the groundwork for another client-side performance boost, since
5333 currently we're not making efficient use of relays that have both the
5334 Guard flag and the Exit flag.
5337 - Fix a regression from our patch for bug 1244 that caused relays
5338 to guess their IP address incorrectly if they didn't set Address
5339 in their torrc and/or their address fails to resolve. Bugfix on
5340 0.2.2.9-alpha; fixes bug 1269.
5342 o Major features (performance):
5343 - Directory authorities now compute consensus weightings that instruct
5344 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
5345 and no flag. Clients that use these weightings will distribute
5346 network load more evenly across these different relay types. The
5347 weightings are in the consensus so we can change them globally in
5348 the future. Extra thanks to "outofwords" for finding some nasty
5349 security bugs in the first implementation of this feature.
5351 o Minor features (performance):
5352 - Always perform router selections using weighted relay bandwidth,
5353 even if we don't need a high capacity circuit at the time. Non-fast
5354 circuits now only differ from fast ones in that they can use relays
5355 not marked with the Fast flag. This "feature" could turn out to
5356 be a horrible bug; we should investigate more before it goes into
5360 - Allow disabling building of the manpages. Skipping the manpage
5361 speeds up the build considerably.
5363 o Minor bugfixes (on 0.2.2.x):
5364 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
5365 Bugfix on 0.2.2.9-alpha.
5366 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
5367 config option. Bugfix on 0.2.2.7-alpha.
5368 - Ship the asciidoc-helper file in the tarball, so that people can
5369 build from source if they want to, and touching the .1.txt files
5370 doesn't break the build. Bugfix on 0.2.2.9-alpha.
5372 o Minor bugfixes (on 0.2.1.x or earlier):
5373 - Fix a dereference-then-NULL-check sequence when publishing
5374 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
5376 - Fix another dereference-then-NULL-check sequence. Bugfix on
5377 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
5378 - Make sure we treat potentially not NUL-terminated strings correctly.
5379 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
5381 o Code simplifications and refactoring:
5382 - Fix some urls in the exit notice file and make it XHTML1.1 strict
5383 compliant. Based on a patch from Christian Kujau.
5384 - Don't use sed in asciidoc-helper anymore.
5385 - Make the build process fail if asciidoc cannot be found and
5386 building with asciidoc isn't disabled.
5389 Changes in version 0.2.2.9-alpha - 2010-02-22
5390 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
5391 location of a directory authority, and cleans up a bunch of small bugs.
5393 o Directory authority changes:
5394 - Change IP address for dannenberg (v3 directory authority), and
5395 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
5396 service directory authority) from the list.
5399 - Make Tor work again on the latest OS X: when deciding whether to
5400 use strange flags to turn TLS renegotiation on, detect the OpenSSL
5401 version at run-time, not compile time. We need to do this because
5402 Apple doesn't update its dev-tools headers when it updates its
5403 libraries in a security patch.
5404 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
5405 that could happen on 32-bit platforms with 64-bit time_t. Also fix
5406 a memory leak when requesting a hidden service descriptor we've
5407 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
5409 - Authorities could be tricked into giving out the Exit flag to relays
5410 that didn't allow exiting to any ports. This bug could screw
5411 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
5412 1238. Bug discovered by Martin Kowalczyk.
5413 - When freeing a session key, zero it out completely. We only zeroed
5414 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
5415 patched by ekir. Fixes bug 1254.
5418 - Fix static compilation by listing the openssl libraries in the right
5419 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
5420 - Resume handling .exit hostnames in a special way: originally we
5421 stripped the .exit part and used the requested exit relay. In
5422 0.2.2.1-alpha we stopped treating them in any special way, meaning
5423 if you use a .exit address then Tor will pass it on to the exit
5424 relay. Now we reject the .exit stream outright, since that behavior
5425 might be more expected by the user. Found and diagnosed by Scott
5426 Bennett and Downie on or-talk.
5427 - Don't spam the controller with events when we have no file
5428 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
5429 for log messages was already solved from bug 748.)
5430 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
5432 - Make the DNSPort option work with libevent 2.x. Don't alter the
5433 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
5434 - Emit a GUARD DROPPED controller event for a case we missed.
5435 - Make more fields in the controller protocol case-insensitive, since
5436 control-spec.txt said they were.
5437 - Refactor resolve_my_address() to not use gethostbyname() anymore.
5438 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
5439 - Fix a spec conformance issue: the network-status-version token
5440 must be the first token in a v3 consensus or vote. Discovered by
5441 parakeep. Bugfix on 0.2.0.3-alpha.
5443 o Code simplifications and refactoring:
5444 - Generate our manpage and HTML documentation using Asciidoc. This
5445 change should make it easier to maintain the documentation, and
5447 - Remove the --enable-iphone option. According to reports from Marco
5448 Bonetti, Tor builds fine without any special tweaking on recent
5449 iPhone SDK versions.
5450 - Removed some unnecessary files from the source distribution. The
5451 AUTHORS file has now been merged into the people page on the
5452 website. The roadmaps and design doc can now be found in the
5453 projects directory in svn.
5454 - Enabled various circuit build timeout constants to be controlled
5455 by consensus parameters. Also set better defaults for these
5456 parameters based on experimentation on broadband and simulated
5460 - The 'EXTENDCIRCUIT' control port command can now be used with
5461 a circ id of 0 and no path. This feature will cause Tor to build
5462 a new 'fast' general purpose circuit using its own path selection
5464 - Added a BUILDTIMEOUT_SET controller event to describe changes
5465 to the circuit build timeout.
5466 - Future-proof the controller protocol a bit by ignoring keyword
5467 arguments we do not recognize.
5468 - Expand homedirs passed to tor-checkkey. This should silence a
5469 coverity complaint about passing a user-supplied string into
5470 open() without checking it.
5473 Changes in version 0.2.1.25 - 2010-03-16
5474 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
5475 prevent relays from guessing their IP address correctly. It also fixes
5476 several minor potential security bugs.
5479 - Fix a regression from our patch for bug 1244 that caused relays
5480 to guess their IP address incorrectly if they didn't set Address
5481 in their torrc and/or their address fails to resolve. Bugfix on
5482 0.2.1.23; fixes bug 1269.
5483 - When freeing a session key, zero it out completely. We only zeroed
5484 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
5485 patched by ekir. Fixes bug 1254.
5488 - Fix a dereference-then-NULL-check sequence when publishing
5489 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
5491 - Fix another dereference-then-NULL-check sequence. Bugfix on
5492 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
5493 - Make sure we treat potentially not NUL-terminated strings correctly.
5494 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
5498 Changes in version 0.2.1.24 - 2010-02-21
5499 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
5503 - Work correctly out-of-the-box with even more vendor-patched versions
5504 of OpenSSL. In particular, make it so Debian and OS X don't need
5505 customized patches to run/build.
5508 Changes in version 0.2.1.23 - 2010-02-13
5509 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
5510 again on the latest OS X, and updates the location of a directory
5513 o Major bugfixes (performance):
5514 - We were selecting our guards uniformly at random, and then weighting
5515 which of our guards we'd use uniformly at random. This imbalance
5516 meant that Tor clients were severely limited on throughput (and
5517 probably latency too) by the first hop in their circuit. Now we
5518 select guards weighted by currently advertised bandwidth. We also
5519 automatically discard guards picked using the old algorithm. Fixes
5520 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
5523 - Make Tor work again on the latest OS X: when deciding whether to
5524 use strange flags to turn TLS renegotiation on, detect the OpenSSL
5525 version at run-time, not compile time. We need to do this because
5526 Apple doesn't update its dev-tools headers when it updates its
5527 libraries in a security patch.
5528 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
5529 that could happen on 32-bit platforms with 64-bit time_t. Also fix
5530 a memory leak when requesting a hidden service descriptor we've
5531 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
5534 o Directory authority changes:
5535 - Change IP address for dannenberg (v3 directory authority), and
5536 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
5537 service directory authority) from the list.
5540 - Refactor resolve_my_address() to not use gethostbyname() anymore.
5541 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
5544 - Avoid a mad rush at the beginning of each month when each client
5545 rotates half of its guards. Instead we spread the rotation out
5546 throughout the month, but we still avoid leaving a precise timestamp
5547 in the state file about when we first picked the guard. Improves
5548 over the behavior introduced in 0.1.2.17.
5551 Changes in version 0.2.2.8-alpha - 2010-01-26
5552 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
5553 causing bridge relays to disappear. If you're running a bridge,
5557 - Fix a memory corruption bug on bridges that occured during the
5558 inclusion of stats data in extra-info descriptors. Also fix the
5559 interface for geoip_get_bridge_stats* to prevent similar bugs in
5560 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
5561 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
5564 - Ignore OutboundBindAddress when connecting to localhost.
5565 Connections to localhost need to come _from_ localhost, or else
5566 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
5570 Changes in version 0.2.2.7-alpha - 2010-01-19
5571 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
5572 as laying the groundwork for further relay-side performance fixes. It
5573 also starts cleaning up client behavior with respect to the EntryNodes,
5574 ExitNodes, and StrictNodes config options.
5576 This release also rotates two directory authority keys, due to a
5577 security breach of some of the Torproject servers.
5579 o Directory authority changes:
5580 - Rotate keys (both v3 identity and relay identity) for moria1
5583 o Major features (performance):
5584 - We were selecting our guards uniformly at random, and then weighting
5585 which of our guards we'd use uniformly at random. This imbalance
5586 meant that Tor clients were severely limited on throughput (and
5587 probably latency too) by the first hop in their circuit. Now we
5588 select guards weighted by currently advertised bandwidth. We also
5589 automatically discard guards picked using the old algorithm. Fixes
5590 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
5591 - When choosing which cells to relay first, relays can now favor
5592 circuits that have been quiet recently, to provide lower latency
5593 for low-volume circuits. By default, relays enable or disable this
5594 feature based on a setting in the consensus. You can override
5595 this default by using the new "CircuitPriorityHalflife" config
5596 option. Design and code by Ian Goldberg, Can Tang, and Chris
5598 - Add separate per-conn write limiting to go with the per-conn read
5599 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
5600 but never per-conn write limits.
5601 - New consensus params "bwconnrate" and "bwconnburst" to let us
5602 rate-limit client connections as they enter the network. It's
5603 controlled in the consensus so we can turn it on and off for
5604 experiments. It's starting out off. Based on proposal 163.
5606 o Major features (relay selection options):
5607 - Switch to a StrictNodes config option, rather than the previous
5608 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
5609 "StrictExcludeNodes" option.
5610 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
5611 change during a config reload, mark and discard all our origin
5612 circuits. This fix should address edge cases where we change the
5613 config options and but then choose a circuit that we created before
5615 - If EntryNodes or ExitNodes are set, be more willing to use an
5616 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
5618 - Make EntryNodes config option much more aggressive even when
5619 StrictNodes is not set. Before it would prepend your requested
5620 entrynodes to your list of guard nodes, but feel free to use others
5621 after that. Now it chooses only from your EntryNodes if any of
5622 those are available, and only falls back to others if a) they're
5623 all down and b) StrictNodes is not set.
5624 - Now we refresh your entry guards from EntryNodes at each consensus
5625 fetch -- rather than just at startup and then they slowly rot as
5626 the network changes.
5629 - Stop bridge directory authorities from answering dbg-stability.txt
5630 directory queries, which would let people fetch a list of all
5631 bridge identities they track. Bugfix on 0.2.1.6-alpha.
5634 - Log a notice when we get a new control connection. Now it's easier
5635 for security-conscious users to recognize when a local application
5636 is knocking on their controller door. Suggested by bug 1196.
5637 - New config option "CircuitStreamTimeout" to override our internal
5638 timeout schedule for how many seconds until we detach a stream from
5639 a circuit and try a new circuit. If your network is particularly
5640 slow, you might want to set this to a number like 60.
5641 - New controller command "getinfo config-text". It returns the
5642 contents that Tor would write if you send it a SAVECONF command,
5643 so the controller can write the file to disk itself.
5644 - New options for SafeLogging to allow scrubbing only log messages
5645 generated while acting as a relay.
5646 - Ship the bridges spec file in the tarball too.
5647 - Avoid a mad rush at the beginning of each month when each client
5648 rotates half of its guards. Instead we spread the rotation out
5649 throughout the month, but we still avoid leaving a precise timestamp
5650 in the state file about when we first picked the guard. Improves
5651 over the behavior introduced in 0.1.2.17.
5653 o Minor bugfixes (compiling):
5654 - Fix compilation on OS X 10.3, which has a stub mlockall() but
5655 hides it. Bugfix on 0.2.2.6-alpha.
5656 - Fix compilation on Solaris by removing support for the
5657 DisableAllSwap config option. Solaris doesn't have an rlimit for
5658 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
5661 o Minor bugfixes (crashes):
5662 - Do not segfault when writing buffer stats when we haven't observed
5663 a single circuit to report about. Found by Fabian Lanze. Bugfix on
5665 - If we're in the pathological case where there's no exit bandwidth
5666 but there is non-exit bandwidth, or no guard bandwidth but there
5667 is non-guard bandwidth, don't crash during path selection. Bugfix
5669 - Fix an impossible-to-actually-trigger buffer overflow in relay
5670 descriptor generation. Bugfix on 0.1.0.15.
5672 o Minor bugfixes (privacy):
5673 - Fix an instance where a Tor directory mirror might accidentally
5674 log the IP address of a misbehaving Tor client. Bugfix on
5676 - Don't list Windows capabilities in relay descriptors. We never made
5677 use of them, and maybe it's a bad idea to publish them. Bugfix
5680 o Minor bugfixes (other):
5681 - Resolve an edge case in path weighting that could make us misweight
5682 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
5683 - Fix statistics on client numbers by country as seen by bridges that
5684 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
5685 intervals instead of variable 12-to-48-hour intervals.
5686 - After we free an internal connection structure, overwrite it
5687 with a different memory value than we use for overwriting a freed
5688 internal circuit structure. Should help with debugging. Suggested
5690 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
5694 - Remove the HSAuthorityRecordStats option that version 0 hidden
5695 service authorities could have used to track statistics of overall
5696 hidden service usage.
5699 Changes in version 0.2.1.22 - 2010-01-19
5700 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
5701 authorities -- it would tell you its whole history of bridge descriptors
5702 if you make the right directory request. This stable update also
5703 rotates two of the seven v3 directory authority keys and locations.
5705 o Directory authority changes:
5706 - Rotate keys (both v3 identity and relay identity) for moria1
5710 - Stop bridge directory authorities from answering dbg-stability.txt
5711 directory queries, which would let people fetch a list of all
5712 bridge identities they track. Bugfix on 0.2.1.6-alpha.
5715 Changes in version 0.2.1.21 - 2009-12-21
5716 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
5717 library. If you use Tor on Linux / Unix and you're getting SSL
5718 renegotiation errors, upgrading should help. We also recommend an
5719 upgrade if you're an exit relay.
5722 - Work around a security feature in OpenSSL 0.9.8l that prevents our
5723 handshake from working unless we explicitly tell OpenSSL that we
5724 are using SSL renegotiation safely. We are, of course, but OpenSSL
5725 0.9.8l won't work unless we say we are.
5726 - Avoid crashing if the client is trying to upload many bytes and the
5727 circuit gets torn down at the same time, or if the flip side
5728 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
5731 - Do not refuse to learn about authority certs and v2 networkstatus
5732 documents that are older than the latest consensus. This bug might
5733 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
5734 Spotted and fixed by xmux.
5735 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
5736 trigger platform-specific option misparsing case found by Coverity
5738 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
5739 trigger assert. Fixes bug 1173.
5742 Changes in version 0.2.2.6-alpha - 2009-11-19
5743 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
5744 support for the new lower-footprint "microdescriptor" directory design,
5745 future-proofing our consensus format against new hash functions or
5746 other changes, and an Android port. It also makes Tor compatible with
5747 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
5750 - Directory authorities can now create, vote on, and serve multiple
5751 parallel formats of directory data as part of their voting process.
5752 Partially implements Proposal 162: "Publish the consensus in
5754 - Directory authorities can now agree on and publish small summaries
5755 of router information that clients can use in place of regular
5756 server descriptors. This transition will eventually allow clients
5757 to use far less bandwidth for downloading information about the
5758 network. Begins the implementation of Proposal 158: "Clients
5759 download consensus + microdescriptors".
5760 - The directory voting system is now extensible to use multiple hash
5761 algorithms for signatures and resource selection. Newer formats
5762 are signed with SHA256, with a possibility for moving to a better
5763 hash algorithm in the future.
5764 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
5765 current and future memory pages via mlockall(). On supported
5766 platforms (modern Linux and probably BSD but not Windows or OS X),
5767 this should effectively disable any and all attempts to page out
5768 memory. This option requires that you start your Tor as root --
5769 if you use DisableAllSwap, please consider using the User option
5770 to properly reduce the privileges of your Tor.
5771 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
5772 to help Tor build correctly for Android phones.
5775 - Work around a security feature in OpenSSL 0.9.8l that prevents our
5776 handshake from working unless we explicitly tell OpenSSL that we
5777 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
5778 won't work unless we say we are.
5781 - Fix a crash bug when trying to initialize the evdns module in
5782 Libevent 2. Bugfix on 0.2.1.16-rc.
5783 - Stop logging at severity 'warn' when some other Tor client tries
5784 to establish a circuit with us using weak DH keys. It's a protocol
5785 violation, but that doesn't mean ordinary users need to hear about
5786 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
5787 - Do not refuse to learn about authority certs and v2 networkstatus
5788 documents that are older than the latest consensus. This bug might
5789 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
5790 Spotted and fixed by xmux.
5791 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
5792 - If all authorities restart at once right before a consensus vote,
5793 nobody will vote about "Running", and clients will get a consensus
5794 with no usable relays. Instead, authorities refuse to build a
5795 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
5796 - If your relay can't keep up with the number of incoming create
5797 cells, it would log one warning per failure into your logs. Limit
5798 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
5799 - Bridges now use "reject *:*" as their default exit policy. Bugfix
5800 on 0.2.0.3-alpha; fixes bug 1113.
5801 - Fix a memory leak on directory authorities during voting that was
5802 introduced in 0.2.2.1-alpha. Found via valgrind.
5805 Changes in version 0.2.1.20 - 2009-10-15
5806 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
5807 services at once, prepares for more performance improvements, and
5808 fixes a bunch of smaller bugs.
5810 The Windows and OS X bundles also include a more recent Vidalia,
5811 and switch from Privoxy to Polipo.
5813 The OS X installers are now drag and drop. It's best to un-install
5814 Tor/Vidalia and then install this new bundle, rather than upgrade. If
5815 you want to upgrade, you'll need to update the paths for Tor and Polipo
5816 in the Vidalia Settings window.
5819 - Send circuit or stream sendme cells when our window has decreased
5820 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
5821 by Karsten when testing the "reduce circuit window" performance
5822 patch. Bugfix on the 54th commit on Tor -- from July 2002,
5823 before the release of Tor 0.0.0. This is the new winner of the
5825 - Fix a remotely triggerable memory leak when a consensus document
5826 contains more than one signature from the same voter. Bugfix on
5828 - Avoid segfault in rare cases when finishing an introduction circuit
5829 as a client and finding out that we don't have an introduction key
5830 for it. Fixes bug 1073. Reported by Aaron Swartz.
5833 - Tor now reads the "circwindow" parameter out of the consensus,
5834 and uses that value for its circuit package window rather than the
5835 default of 1000 cells. Begins the implementation of proposal 168.
5837 o New directory authorities:
5838 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
5840 - Move moria1 and tonga to alternate IP addresses.
5843 - Fix a signed/unsigned compile warning in 0.2.1.19.
5844 - Fix possible segmentation fault on directory authorities. Bugfix on
5846 - Fix an extremely rare infinite recursion bug that could occur if
5847 we tried to log a message after shutting down the log subsystem.
5848 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
5849 - Fix an obscure bug where hidden services on 64-bit big-endian
5850 systems might mis-read the timestamp in v3 introduce cells, and
5851 refuse to connect back to the client. Discovered by "rotor".
5852 Bugfix on 0.2.1.6-alpha.
5853 - We were triggering a CLOCK_SKEW controller status event whenever
5854 we connect via the v2 connection protocol to any relay that has
5855 a wrong clock. Instead, we should only inform the controller when
5856 it's a trusted authority that claims our clock is wrong. Bugfix
5857 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
5858 - We were telling the controller about CHECKING_REACHABILITY and
5859 REACHABILITY_FAILED status events whenever we launch a testing
5860 circuit or notice that one has failed. Instead, only tell the
5861 controller when we want to inform the user of overall success or
5862 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5864 - Don't warn when we're using a circuit that ends with a node
5865 excluded in ExcludeExitNodes, but the circuit is not used to access
5866 the outside world. This should help fix bug 1090. Bugfix on
5868 - Work around a small memory leak in some versions of OpenSSL that
5869 stopped the memory used by the hostname TLS extension from being
5873 - Add a "getinfo status/accepted-server-descriptor" controller
5874 command, which is the recommended way for controllers to learn
5875 whether our server descriptor has been successfully received by at
5876 least on directory authority. Un-recommend good-server-descriptor
5877 getinfo and status events until we have a better design for them.
5880 Changes in version 0.2.2.5-alpha - 2009-10-11
5881 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
5884 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
5886 o Directory authorities:
5887 - Temporarily (just for this release) move dizum to an alternate
5891 Changes in version 0.2.2.4-alpha - 2009-10-10
5892 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
5893 introduces a new unit test framework, shifts directry authority
5894 addresses around to reduce the impact from recent blocking events,
5895 and fixes a few smaller bugs.
5898 - Fix several more asserts in the circuit_build_times code, for
5899 example one that causes Tor to fail to start once we have
5900 accumulated 5000 build times in the state file. Bugfixes on
5901 0.2.2.2-alpha; fixes bug 1108.
5903 o New directory authorities:
5904 - Move moria1 and Tonga to alternate IP addresses.
5907 - Log SSL state transitions at debug level during handshake, and
5908 include SSL states in error messages. This may help debug future
5909 SSL handshake issues.
5910 - Add a new "Handshake" log domain for activities that happen
5911 during the TLS handshake.
5912 - Revert to the "June 3 2009" ip-to-country file. The September one
5913 seems to have removed most US IP addresses.
5914 - Directory authorities now reject Tor relays with versions less than
5915 0.1.2.14. This step cuts out four relays from the current network,
5916 none of which are very big.
5919 - Fix a couple of smaller issues with gathering statistics. Bugfixes
5921 - Fix two memory leaks in the error case of
5922 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
5923 - Don't count one-hop circuits when we're estimating how long it
5924 takes circuits to build on average. Otherwise we'll set our circuit
5925 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
5926 - Directory authorities no longer change their opinion of, or vote on,
5927 whether a router is Running, unless they have themselves been
5928 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
5931 o Code simplifications and refactoring:
5932 - Revise our unit tests to use the "tinytest" framework, so we
5933 can run tests in their own processes, have smarter setup/teardown
5934 code, and so on. The unit test code has moved to its own
5935 subdirectory, and has been split into multiple modules.
5938 Changes in version 0.2.2.3-alpha - 2009-09-23
5939 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
5942 - Fix an overzealous assert in our new circuit build timeout code.
5943 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
5946 - If the networkstatus consensus tells us that we should use a
5947 negative circuit package window, ignore it. Otherwise we'll
5948 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
5951 Changes in version 0.2.2.2-alpha - 2009-09-21
5952 Tor 0.2.2.2-alpha introduces our latest performance improvement for
5953 clients: Tor tracks the average time it takes to build a circuit, and
5954 avoids using circuits that take too long to build. For fast connections,
5955 this feature can cut your expected latency in half. For slow or flaky
5956 connections, it could ruin your Tor experience. Let us know if it does!
5959 - Tor now tracks how long it takes to build client-side circuits
5960 over time, and adapts its timeout to local network performance.
5961 Since a circuit that takes a long time to build will also provide
5962 bad performance, we get significant latency improvements by
5963 discarding the slowest 20% of circuits. Specifically, Tor creates
5964 circuits more aggressively than usual until it has enough data
5965 points for a good timeout estimate. Implements proposal 151.
5966 We are especially looking for reports (good and bad) from users with
5967 both EDGE and broadband connections that can move from broadband
5968 to EDGE and find out if the build-time data in the .tor/state gets
5969 reset without loss of Tor usability. You should also see a notice
5970 log message telling you that Tor has reset its timeout.
5971 - Directory authorities can now vote on arbitary integer values as
5972 part of the consensus process. This is designed to help set
5973 network-wide parameters. Implements proposal 167.
5974 - Tor now reads the "circwindow" parameter out of the consensus,
5975 and uses that value for its circuit package window rather than the
5976 default of 1000 cells. Begins the implementation of proposal 168.
5979 - Fix a remotely triggerable memory leak when a consensus document
5980 contains more than one signature from the same voter. Bugfix on
5984 - Fix an extremely rare infinite recursion bug that could occur if
5985 we tried to log a message after shutting down the log subsystem.
5986 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
5987 - Fix parsing for memory or time units given without a space between
5988 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
5989 - A networkstatus vote must contain exactly one signature. Spec
5990 conformance issue. Bugfix on 0.2.0.3-alpha.
5991 - Fix an obscure bug where hidden services on 64-bit big-endian
5992 systems might mis-read the timestamp in v3 introduce cells, and
5993 refuse to connect back to the client. Discovered by "rotor".
5994 Bugfix on 0.2.1.6-alpha.
5995 - We were triggering a CLOCK_SKEW controller status event whenever
5996 we connect via the v2 connection protocol to any relay that has
5997 a wrong clock. Instead, we should only inform the controller when
5998 it's a trusted authority that claims our clock is wrong. Bugfix
5999 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
6000 - We were telling the controller about CHECKING_REACHABILITY and
6001 REACHABILITY_FAILED status events whenever we launch a testing
6002 circuit or notice that one has failed. Instead, only tell the
6003 controller when we want to inform the user of overall success or
6004 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
6006 - Don't warn when we're using a circuit that ends with a node
6007 excluded in ExcludeExitNodes, but the circuit is not used to access
6008 the outside world. This should help fix bug 1090, but more problems
6009 remain. Bugfix on 0.2.1.6-alpha.
6010 - Work around a small memory leak in some versions of OpenSSL that
6011 stopped the memory used by the hostname TLS extension from being
6013 - Make our 'torify' script more portable; if we have only one of
6014 'torsocks' or 'tsocks' installed, don't complain to the user;
6015 and explain our warning about tsocks better.
6018 - Add a "getinfo status/accepted-server-descriptor" controller
6019 command, which is the recommended way for controllers to learn
6020 whether our server descriptor has been successfully received by at
6021 least on directory authority. Un-recommend good-server-descriptor
6022 getinfo and status events until we have a better design for them.
6023 - Update to the "September 4 2009" ip-to-country file.
6026 Changes in version 0.2.2.1-alpha - 2009-08-26
6027 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
6028 Tor clients to bootstrap on networks where only port 80 is reachable,
6029 makes it more straightforward to support hardware crypto accelerators,
6030 and starts the groundwork for gathering stats safely at relays.
6033 - Start the process of disabling ".exit" address notation, since it
6034 can be used for a variety of esoteric application-level attacks
6035 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
6038 o New directory authorities:
6039 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
6043 - New AccelName and AccelDir options add support for dynamic OpenSSL
6044 hardware crypto acceleration engines.
6045 - Tor now supports tunneling all of its outgoing connections over
6046 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
6047 configuration options. Code by Christopher Davis.
6050 - Send circuit or stream sendme cells when our window has decreased
6051 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
6052 by Karsten when testing the "reduce circuit window" performance
6053 patch. Bugfix on the 54th commit on Tor -- from July 2002,
6054 before the release of Tor 0.0.0. This is the new winner of the
6057 o New options for gathering stats safely:
6058 - Directory mirrors that set "DirReqStatistics 1" write statistics
6059 about directory requests to disk every 24 hours. As compared to the
6060 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
6061 1) stats are written to disk exactly every 24 hours; 2) estimated
6062 shares of v2 and v3 requests are determined as mean values, not at
6063 the end of a measurement period; 3) unresolved requests are listed
6064 with country code '??'; 4) directories also measure download times.
6065 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
6066 number of exit streams and transferred bytes per port to disk every
6068 - Relays that set "CellStatistics 1" write statistics on how long
6069 cells spend in their circuit queues to disk every 24 hours.
6070 - Entry nodes that set "EntryStatistics 1" write statistics on the
6071 rough number and origins of connecting clients to disk every 24
6073 - Relays that write any of the above statistics to disk and set
6074 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
6075 their extra-info documents.
6078 - New --digests command-line switch to output the digests of the
6079 source files Tor was built with.
6080 - The "torify" script now uses torsocks where available.
6081 - The memarea code now uses a sentinel value at the end of each area
6082 to make sure nothing writes beyond the end of an area. This might
6083 help debug some conceivable causes of bug 930.
6084 - Time and memory units in the configuration file can now be set to
6085 fractional units. For example, "2.5 GB" is now a valid value for
6087 - Certain Tor clients (such as those behind check.torproject.org) may
6088 want to fetch the consensus in an extra early manner. To enable this
6089 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
6090 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
6091 as only certain clients who must have this information sooner should
6093 - Instead of adding the svn revision to the Tor version string, report
6094 the git commit (when we're building from a git checkout).
6097 - If any of the v3 certs we download are unparseable, we should
6098 actually notice the failure so we don't retry indefinitely. Bugfix
6099 on 0.2.0.x; reported by "rotator".
6100 - If the cached cert file is unparseable, warn but don't exit.
6101 - Fix possible segmentation fault on directory authorities. Bugfix on
6103 - When Tor fails to parse a descriptor of any kind, dump it to disk.
6104 Might help diagnosing bug 1051.
6106 o Deprecated and removed features:
6107 - The controller no longer accepts the old obsolete "addr-mappings/"
6108 or "unregistered-servers-" GETINFO values.
6109 - Hidden services no longer publish version 0 descriptors, and clients
6110 do not request or use version 0 descriptors. However, the old hidden
6111 service authorities still accept and serve version 0 descriptors
6112 when contacted by older hidden services/clients.
6113 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
6114 always on; using them is necessary for correct forward-compatible
6116 - Remove support for .noconnect style addresses. Nobody was using
6117 them, and they provided another avenue for detecting Tor users
6118 via application-level web tricks.
6120 o Packaging changes:
6121 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
6122 installer bundles. See
6123 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
6124 for details of what's new in Vidalia 0.2.3.
6125 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
6126 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
6127 configuration file, rather than the old Privoxy.
6128 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
6129 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
6130 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
6131 better compatibility with OS X 10.6, aka Snow Leopard.
6132 - OS X Vidalia Bundle: The multi-package installer is now replaced
6133 by a simple drag and drop to the /Applications folder. This change
6134 occurred with the upgrade to Vidalia 0.2.3.
6137 Changes in version 0.2.1.19 - 2009-07-28
6138 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
6139 services on Tor 0.2.1.3-alpha through 0.2.1.18.
6142 - Make accessing hidden services on 0.2.1.x work right again.
6143 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
6144 part of patch provided by "optimist".
6147 - When a relay/bridge is writing out its identity key fingerprint to
6148 the "fingerprint" file and to its logs, write it without spaces. Now
6149 it will look like the fingerprints in our bridges documentation,
6150 and confuse fewer users.
6153 - Relays no longer publish a new server descriptor if they change
6154 their MaxAdvertisedBandwidth config option but it doesn't end up
6155 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
6156 fixes bug 1026. Patch from Sebastian.
6157 - Avoid leaking memory every time we get a create cell but we have
6158 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
6159 fixes bug 1034. Reported by BarkerJr.
6162 Changes in version 0.2.1.18 - 2009-07-24
6163 Tor 0.2.1.18 lays the foundations for performance improvements,
6164 adds status events to help users diagnose bootstrap problems, adds
6165 optional authentication/authorization for hidden services, fixes a
6166 variety of potential anonymity problems, and includes a huge pile of
6167 other features and bug fixes.
6170 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
6173 Changes in version 0.2.1.17-rc - 2009-07-07
6174 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
6175 candidate for the 0.2.1.x series. It lays the groundwork for further
6176 client performance improvements, and also fixes a big bug with directory
6177 authorities that were causing them to assign Guard and Stable flags
6180 The Windows bundles also finally include the geoip database that we
6181 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
6182 should actually install Torbutton rather than giving you a cryptic
6183 failure message (oops).
6186 - Clients now use the bandwidth values in the consensus, rather than
6187 the bandwidth values in each relay descriptor. This approach opens
6188 the door to more accurate bandwidth estimates once the directory
6189 authorities start doing active measurements. Implements more of
6193 - When Tor clients restart after 1-5 days, they discard all their
6194 cached descriptors as too old, but they still use the cached
6195 consensus document. This approach is good for robustness, but
6196 bad for performance: since they don't know any bandwidths, they
6197 end up choosing at random rather than weighting their choice by
6198 speed. Fixed by the above feature of putting bandwidths in the
6199 consensus. Bugfix on 0.2.0.x.
6200 - Directory authorities were neglecting to mark relays down in their
6201 internal histories if the relays fall off the routerlist without
6202 ever being found unreachable. So there were relays in the histories
6203 that haven't been seen for eight months, and are listed as being
6204 up for eight months. This wreaked havoc on the "median wfu"
6205 and "median mtbf" calculations, in turn making Guard and Stable
6206 flags very wrong, hurting network performance. Fixes bugs 696 and
6207 969. Bugfix on 0.2.0.6-alpha.
6210 - Serve the DirPortFrontPage page even when we have been approaching
6211 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
6212 - The control port would close the connection before flushing long
6213 replies, such as the network consensus, if a QUIT command was issued
6214 before the reply had completed. Now, the control port flushes all
6215 pending replies before closing the connection. Also fixed a spurious
6216 warning when a QUIT command is issued after a malformed or rejected
6217 AUTHENTICATE command, but before the connection was closed. Patch
6218 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
6219 - When we can't find an intro key for a v2 hidden service descriptor,
6220 fall back to the v0 hidden service descriptor and log a bug message.
6221 Workaround for bug 1024.
6222 - Fix a log message that did not respect the SafeLogging option.
6226 - If we're a relay and we change our IP address, be more verbose
6227 about the reason that made us change. Should help track down
6228 further bugs for relays on dynamic IP addresses.
6231 Changes in version 0.2.0.35 - 2009-06-24
6233 - Avoid crashing in the presence of certain malformed descriptors.
6234 Found by lark, and by automated fuzzing.
6235 - Fix an edge case where a malicious exit relay could convince a
6236 controller that the client's DNS question resolves to an internal IP
6237 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
6240 - Finally fix the bug where dynamic-IP relays disappear when their
6241 IP address changes: directory mirrors were mistakenly telling
6242 them their old address if they asked via begin_dir, so they
6243 never got an accurate answer about their new address, so they
6244 just vanished after a day. For belt-and-suspenders, relays that
6245 don't set Address in their config now avoid using begin_dir for
6246 all direct connections. Should fix bugs 827, 883, and 900.
6247 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
6248 that would occur on some exit nodes when DNS failures and timeouts
6249 occurred in certain patterns. Fix for bug 957.
6252 - When starting with a cache over a few days old, do not leak
6253 memory for the obsolete router descriptors in it. Bugfix on
6254 0.2.0.33; fixes bug 672.
6255 - Hidden service clients didn't use a cached service descriptor that
6256 was older than 15 minutes, but wouldn't fetch a new one either,
6257 because there was already one in the cache. Now, fetch a v2
6258 descriptor unless the same descriptor was added to the cache within
6259 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
6262 Changes in version 0.2.1.16-rc - 2009-06-20
6263 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
6264 a bunch of minor bugs.
6267 - Fix an edge case where a malicious exit relay could convince a
6268 controller that the client's DNS question resolves to an internal IP
6269 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
6271 o Major performance improvements (on 0.2.0.x):
6272 - Disable and refactor some debugging checks that forced a linear scan
6273 over the whole server-side DNS cache. These accounted for over 50%
6274 of CPU time on a relatively busy exit node's gprof profile. Found
6276 - Disable some debugging checks that appeared in exit node profile
6280 - Update to the "June 3 2009" ip-to-country file.
6281 - Do not have tor-resolve automatically refuse all .onion addresses;
6282 if AutomapHostsOnResolve is set in your torrc, this will work fine.
6284 o Minor bugfixes (on 0.2.0.x):
6285 - Log correct error messages for DNS-related network errors on
6287 - Fix a race condition that could cause crashes or memory corruption
6288 when running as a server with a controller listening for log
6290 - Avoid crashing when we have a policy specified in a DirPolicy or
6291 SocksPolicy or ReachableAddresses option with ports set on it,
6292 and we re-load the policy. May fix bug 996.
6293 - Hidden service clients didn't use a cached service descriptor that
6294 was older than 15 minutes, but wouldn't fetch a new one either,
6295 because there was already one in the cache. Now, fetch a v2
6296 descriptor unless the same descriptor was added to the cache within
6297 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
6299 o Minor bugfixes (on 0.2.1.x):
6300 - Don't warn users about low port and hibernation mix when they
6301 provide a *ListenAddress directive to fix that. Bugfix on
6303 - When switching back and forth between bridge mode, do not start
6304 gathering GeoIP data until two hours have passed.
6305 - Do not complain that the user has requested an excluded node as
6306 an exit when the node is not really an exit. This could happen
6307 because the circuit was for testing, or an introduction point.
6311 Changes in version 0.2.1.15-rc - 2009-05-25
6312 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
6313 series. It fixes a major bug on fast exit relays, as well as a variety
6316 o Major bugfixes (on 0.2.0.x):
6317 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
6318 that would occur on some exit nodes when DNS failures and timeouts
6319 occurred in certain patterns. Fix for bug 957.
6321 o Minor bugfixes (on 0.2.0.x):
6322 - Actually return -1 in the error case for read_bandwidth_usage().
6323 Harmless bug, since we currently don't care about the return value
6324 anywhere. Bugfix on 0.2.0.9-alpha.
6325 - Provide a more useful log message if bug 977 (related to buffer
6326 freelists) ever reappears, and do not crash right away.
6327 - Fix an assertion failure on 64-bit platforms when we allocated
6328 memory right up to the end of a memarea, then realigned the memory
6329 one step beyond the end. Fixes a possible cause of bug 930.
6330 - Protect the count of open sockets with a mutex, so we can't
6331 corrupt it when two threads are closing or opening sockets at once.
6332 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
6333 - Don't allow a bridge to publish its router descriptor to a
6334 non-bridge directory authority. Fixes part of bug 932.
6335 - When we change to or from being a bridge, reset our counts of
6336 client usage by country. Fixes bug 932.
6337 - Fix a bug that made stream bandwidth get misreported to the
6339 - Stop using malloc_usable_size() to use more area than we had
6340 actually allocated: it was safe, but made valgrind really unhappy.
6341 - Fix a memory leak when v3 directory authorities load their keys
6342 and cert from disk. Bugfix on 0.2.0.1-alpha.
6344 o Minor bugfixes (on 0.2.1.x):
6345 - Fix use of freed memory when deciding to mark a non-addable
6346 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
6349 Changes in version 0.2.1.14-rc - 2009-04-12
6350 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
6351 series. It begins fixing some major performance problems, and also
6352 finally addresses the bug that was causing relays on dynamic IP
6353 addresses to fall out of the directory.
6356 - Clients replace entry guards that were chosen more than a few months
6357 ago. This change should significantly improve client performance,
6358 especially once more people upgrade, since relays that have been
6359 a guard for a long time are currently overloaded.
6361 o Major bugfixes (on 0.2.0):
6362 - Finally fix the bug where dynamic-IP relays disappear when their
6363 IP address changes: directory mirrors were mistakenly telling
6364 them their old address if they asked via begin_dir, so they
6365 never got an accurate answer about their new address, so they
6366 just vanished after a day. For belt-and-suspenders, relays that
6367 don't set Address in their config now avoid using begin_dir for
6368 all direct connections. Should fix bugs 827, 883, and 900.
6369 - Relays were falling out of the networkstatus consensus for
6370 part of a day if they changed their local config but the
6371 authorities discarded their new descriptor as "not sufficiently
6372 different". Now directory authorities accept a descriptor as changed
6373 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
6375 - Avoid crashing in the presence of certain malformed descriptors.
6376 Found by lark, and by automated fuzzing.
6379 - When generating circuit events with verbose nicknames for
6380 controllers, try harder to look up nicknames for routers on a
6381 circuit. (Previously, we would look in the router descriptors we had
6382 for nicknames, but not in the consensus.) Partial fix for bug 941.
6383 - If the bridge config line doesn't specify a port, assume 443.
6384 This makes bridge lines a bit smaller and easier for users to
6386 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
6387 bytes (aka 20KB/s), to match our documentation. Also update
6388 directory authorities so they always assign the Fast flag to relays
6389 with 20KB/s of capacity. Now people running relays won't suddenly
6390 find themselves not seeing any use, if the network gets faster
6392 - Update to the "April 3 2009" ip-to-country file.
6395 - Avoid trying to print raw memory to the logs when we decide to
6396 give up on downloading a given relay descriptor. Bugfix on
6398 - In tor-resolve, when the Tor client to use is specified by
6399 <hostname>:<port>, actually use the specified port rather than
6400 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
6401 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
6402 - When starting with a cache over a few days old, do not leak
6403 memory for the obsolete router descriptors in it. Bugfix on
6405 - Avoid double-free on list of successfully uploaded hidden
6406 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
6407 - Change memarea_strndup() implementation to work even when
6408 duplicating a string at the end of a page. This bug was
6409 harmless for now, but could have meant crashes later. Fix by
6410 lark. Bugfix on 0.2.1.1-alpha.
6411 - Limit uploaded directory documents to be 16M rather than 500K.
6412 The directory authorities were refusing v3 consensus votes from
6413 other authorities, since the votes are now 504K. Fixes bug 959;
6414 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
6415 - Directory authorities should never send a 503 "busy" response to
6416 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
6420 Changes in version 0.2.1.13-alpha - 2009-03-09
6421 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
6422 cleanups. We're finally getting close to a release candidate.
6425 - Correctly update the list of which countries we exclude as
6426 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
6427 lark. Bugfix on 0.2.1.6-alpha.
6429 o Minor bugfixes (on 0.2.0.x and earlier):
6430 - Automatically detect MacOSX versions earlier than 10.4.0, and
6431 disable kqueue from inside Tor when running with these versions.
6432 We previously did this from the startup script, but that was no
6433 help to people who didn't use the startup script. Resolves bug 863.
6434 - When we had picked an exit node for a connection, but marked it as
6435 "optional", and it turned out we had no onion key for the exit,
6436 stop wanting that exit and try again. This situation may not
6437 be possible now, but will probably become feasible with proposal
6438 158. Spotted by rovv. Fixes another case of bug 752.
6439 - Clients no longer cache certificates for authorities they do not
6440 recognize. Bugfix on 0.2.0.9-alpha.
6441 - When we can't transmit a DNS request due to a network error, retry
6442 it after a while, and eventually transmit a failing response to
6443 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
6444 - If the controller claimed responsibility for a stream, but that
6445 stream never finished making its connection, it would live
6446 forever in circuit_wait state. Now we close it after SocksTimeout
6447 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
6448 - Drop begin cells to a hidden service if they come from the middle
6449 of a circuit. Patch from lark.
6450 - When we erroneously receive two EXTEND cells for the same circuit
6451 ID on the same connection, drop the second. Patch from lark.
6452 - Fix a crash that occurs on exit nodes when a nameserver request
6453 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
6454 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
6456 - Do not assume that a stack-allocated character array will be
6457 64-bit aligned on platforms that demand that uint64_t access is
6458 aligned. Possible fix for bug 604.
6459 - Parse dates and IPv4 addresses in a locale- and libc-independent
6460 manner, to avoid platform-dependent behavior on malformed input.
6461 - Build correctly when configured to build outside the main source
6462 path. Patch from Michael Gold.
6463 - We were already rejecting relay begin cells with destination port
6464 of 0. Now also reject extend cells with destination port or address
6465 of 0. Suggested by lark.
6467 o Minor bugfixes (on 0.2.1.x):
6468 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
6469 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
6470 - If we're an exit node, scrub the IP address to which we are exiting
6471 in the logs. Bugfix on 0.2.1.8-alpha.
6474 - On Linux, use the prctl call to re-enable core dumps when the user
6476 - New controller event NEWCONSENSUS that lists the networkstatus
6477 lines for every recommended relay. Now controllers like Torflow
6478 can keep up-to-date on which relays they should be using.
6479 - Update to the "February 26 2009" ip-to-country file.
6482 Changes in version 0.2.0.34 - 2009-02-08
6483 Tor 0.2.0.34 features several more security-related fixes. You should
6484 upgrade, especially if you run an exit relay (remote crash) or a
6485 directory authority (remote infinite loop), or you're on an older
6486 (pre-XP) or not-recently-patched Windows (remote exploit).
6488 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
6489 have many known flaws, and nobody should be using them. You should
6490 upgrade. If you're using a Linux or BSD and its packages are obsolete,
6491 stop using those packages and upgrade anyway.
6494 - Fix an infinite-loop bug on handling corrupt votes under certain
6495 circumstances. Bugfix on 0.2.0.8-alpha.
6496 - Fix a temporary DoS vulnerability that could be performed by
6497 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
6498 - Avoid a potential crash on exit nodes when processing malformed
6499 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
6500 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
6501 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
6504 - Fix compilation on systems where time_t is a 64-bit integer.
6505 Patch from Matthias Drochner.
6506 - Don't consider expiring already-closed client connections. Fixes
6507 bug 893. Bugfix on 0.0.2pre20.
6510 Changes in version 0.2.1.12-alpha - 2009-02-08
6511 Tor 0.2.1.12-alpha features several more security-related fixes. You
6512 should upgrade, especially if you run an exit relay (remote crash) or
6513 a directory authority (remote infinite loop), or you're on an older
6514 (pre-XP) or not-recently-patched Windows (remote exploit). It also
6515 includes a big pile of minor bugfixes and cleanups.
6518 - Fix an infinite-loop bug on handling corrupt votes under certain
6519 circumstances. Bugfix on 0.2.0.8-alpha.
6520 - Fix a temporary DoS vulnerability that could be performed by
6521 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
6522 - Avoid a potential crash on exit nodes when processing malformed
6523 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
6526 - Let controllers actually ask for the "clients_seen" event for
6527 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
6528 reported by Matt Edman.
6529 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
6531 - Fix a bug in address parsing that was preventing bridges or hidden
6532 service targets from being at IPv6 addresses.
6533 - Solve a bug that kept hardware crypto acceleration from getting
6534 enabled when accounting was turned on. Fixes bug 907. Bugfix on
6536 - Remove a bash-ism from configure.in to build properly on non-Linux
6537 platforms. Bugfix on 0.2.1.1-alpha.
6538 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
6539 headers. Bugfix on 0.2.0.10-alpha.
6540 - Don't consider expiring already-closed client connections. Fixes
6541 bug 893. Bugfix on 0.0.2pre20.
6542 - Fix another interesting corner-case of bug 891 spotted by rovv:
6543 Previously, if two hosts had different amounts of clock drift, and
6544 one of them created a new connection with just the wrong timing,
6545 the other might decide to deprecate the new connection erroneously.
6546 Bugfix on 0.1.1.13-alpha.
6547 - Resolve a very rare crash bug that could occur when the user forced
6548 a nameserver reconfiguration during the middle of a nameserver
6549 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
6550 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
6551 Bugfix on 0.2.1.7-alpha.
6552 - If we're using bridges and our network goes away, be more willing
6553 to forgive our bridges and try again when we get an application
6554 request. Bugfix on 0.2.0.x.
6557 - Support platforms where time_t is 64 bits long. (Congratulations,
6558 NetBSD!) Patch from Matthias Drochner.
6559 - Add a 'getinfo status/clients-seen' controller command, in case
6560 controllers want to hear clients_seen events but connect late.
6563 - Disable GCC's strict alias optimization by default, to avoid the
6564 likelihood of its introducing subtle bugs whenever our code violates
6565 the letter of C99's alias rules.
6568 Changes in version 0.2.0.33 - 2009-01-21
6569 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
6570 useful to users. It also finally fixes a bug where a relay or client
6571 that's been off for many days would take a long time to bootstrap.
6573 This update also fixes an important security-related bug reported by
6574 Ilja van Sprundel. You should upgrade. (We'll send out more details
6575 about the bug once people have had some time to upgrade.)
6578 - Fix a heap-corruption bug that may be remotely triggerable on
6579 some platforms. Reported by Ilja van Sprundel.
6582 - When a stream at an exit relay is in state "resolving" or
6583 "connecting" and it receives an "end" relay cell, the exit relay
6584 would silently ignore the end cell and not close the stream. If
6585 the client never closes the circuit, then the exit relay never
6586 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
6588 - When sending CREATED cells back for a given circuit, use a 64-bit
6589 connection ID to find the right connection, rather than an addr:port
6590 combination. Now that we can have multiple OR connections between
6591 the same ORs, it is no longer possible to use addr:port to uniquely
6592 identify a connection.
6593 - Bridge relays that had DirPort set to 0 would stop fetching
6594 descriptors shortly after startup, and then briefly resume
6595 after a new bandwidth test and/or after publishing a new bridge
6596 descriptor. Bridge users that try to bootstrap from them would
6597 get a recent networkstatus but would get descriptors from up to
6598 18 hours earlier, meaning most of the descriptors were obsolete
6599 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
6600 - Prevent bridge relays from serving their 'extrainfo' document
6601 to anybody who asks, now that extrainfo docs include potentially
6602 sensitive aggregated client geoip summaries. Bugfix on
6604 - If the cached networkstatus consensus is more than five days old,
6605 discard it rather than trying to use it. In theory it could be
6606 useful because it lists alternate directory mirrors, but in practice
6607 it just means we spend many minutes trying directory mirrors that
6608 are long gone from the network. Also discard router descriptors as
6609 we load them if they are more than five days old, since the onion
6610 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
6613 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
6614 could make gcc generate non-functional binary search code. Bugfix
6616 - Build correctly on platforms without socklen_t.
6617 - Compile without warnings on solaris.
6618 - Avoid potential crash on internal error during signature collection.
6619 Fixes bug 864. Patch from rovv.
6620 - Correct handling of possible malformed authority signing key
6621 certificates with internal signature types. Fixes bug 880.
6622 Bugfix on 0.2.0.3-alpha.
6623 - Fix a hard-to-trigger resource leak when logging credential status.
6625 - When we can't initialize DNS because the network is down, do not
6626 automatically stop Tor from starting. Instead, we retry failed
6627 dns_init() every 10 minutes, and change the exit policy to reject
6628 *:* until one succeeds. Fixes bug 691.
6629 - Use 64 bits instead of 32 bits for connection identifiers used with
6630 the controller protocol, to greatly reduce risk of identifier reuse.
6631 - When we're choosing an exit node for a circuit, and we have
6632 no pending streams, choose a good general exit rather than one that
6633 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
6634 - Fix another case of assuming, when a specific exit is requested,
6635 that we know more than the user about what hosts it allows.
6636 Fixes one case of bug 752. Patch from rovv.
6637 - Clip the MaxCircuitDirtiness config option to a minimum of 10
6638 seconds. Warn the user if lower values are given in the
6639 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
6640 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
6641 user if lower values are given in the configuration. Bugfix on
6642 0.1.1.17-rc. Patch by Sebastian.
6643 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
6644 the cache because we already had a v0 descriptor with the same ID.
6645 Bugfix on 0.2.0.18-alpha.
6646 - Fix a race condition when freeing keys shared between main thread
6647 and CPU workers that could result in a memory leak. Bugfix on
6648 0.1.0.1-rc. Fixes bug 889.
6649 - Send a valid END cell back when a client tries to connect to a
6650 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
6651 840. Patch from rovv.
6652 - Check which hops rendezvous stream cells are associated with to
6653 prevent possible guess-the-streamid injection attacks from
6654 intermediate hops. Fixes another case of bug 446. Based on patch
6656 - If a broken client asks a non-exit router to connect somewhere,
6657 do not even do the DNS lookup before rejecting the connection.
6658 Fixes another case of bug 619. Patch from rovv.
6659 - When a relay gets a create cell it can't decrypt (e.g. because it's
6660 using the wrong onion key), we were dropping it and letting the
6661 client time out. Now actually answer with a destroy cell. Fixes
6662 bug 904. Bugfix on 0.0.2pre8.
6664 o Minor bugfixes (hidden services):
6665 - Do not throw away existing introduction points on SIGHUP. Bugfix on
6666 0.0.6pre1. Patch by Karsten. Fixes bug 874.
6669 - Report the case where all signatures in a detached set are rejected
6670 differently than the case where there is an error handling the
6672 - When we realize that another process has modified our cached
6673 descriptors, print out a more useful error message rather than
6674 triggering an assertion. Fixes bug 885. Patch from Karsten.
6675 - Implement the 0x20 hack to better resist DNS poisoning: set the
6676 case on outgoing DNS requests randomly, and reject responses that do
6677 not match the case correctly. This logic can be disabled with the
6678 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
6679 of servers that do not reliably preserve case in replies. See
6680 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
6682 - Check DNS replies for more matching fields to better resist DNS
6684 - Never use OpenSSL compression: it wastes RAM and CPU trying to
6685 compress cells, which are basically all encrypted, compressed, or
6689 Changes in version 0.2.1.11-alpha - 2009-01-20
6690 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
6691 week it will take a long time to bootstrap again" bug. It also fixes
6692 an important security-related bug reported by Ilja van Sprundel. You
6693 should upgrade. (We'll send out more details about the bug once people
6694 have had some time to upgrade.)
6697 - Fix a heap-corruption bug that may be remotely triggerable on
6698 some platforms. Reported by Ilja van Sprundel.
6701 - Discard router descriptors as we load them if they are more than
6702 five days old. Otherwise if Tor is off for a long time and then
6703 starts with cached descriptors, it will try to use the onion
6704 keys in those obsolete descriptors when building circuits. Bugfix
6705 on 0.2.0.x. Fixes bug 887.
6708 - Try to make sure that the version of Libevent we're running with
6709 is binary-compatible with the one we built with. May address bug
6711 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
6712 for bug 905. Bugfix on 0.2.1.7-alpha.
6713 - Add a new --enable-local-appdata configuration switch to change
6714 the default location of the datadir on win32 from APPDATA to
6715 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
6716 entirely. Patch from coderman.
6719 - Make outbound DNS packets respect the OutboundBindAddress setting.
6720 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
6721 - When our circuit fails at the first hop (e.g. we get a destroy
6722 cell back), avoid using that OR connection anymore, and also
6723 tell all the one-hop directory requests waiting for it that they
6724 should fail. Bugfix on 0.2.1.3-alpha.
6725 - In the torify(1) manpage, mention that tsocks will leak your
6729 Changes in version 0.2.1.10-alpha - 2009-01-06
6730 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
6731 would make the bridge relay not so useful if it had DirPort set to 0,
6732 and one that could let an attacker learn a little bit of information
6733 about the bridge's users), and a bug that would cause your Tor relay
6734 to ignore a circuit create request it can't decrypt (rather than reply
6735 with an error). It also fixes a wide variety of other bugs.
6738 - If the cached networkstatus consensus is more than five days old,
6739 discard it rather than trying to use it. In theory it could
6740 be useful because it lists alternate directory mirrors, but in
6741 practice it just means we spend many minutes trying directory
6742 mirrors that are long gone from the network. Helps bug 887 a bit;
6744 - Bridge relays that had DirPort set to 0 would stop fetching
6745 descriptors shortly after startup, and then briefly resume
6746 after a new bandwidth test and/or after publishing a new bridge
6747 descriptor. Bridge users that try to bootstrap from them would
6748 get a recent networkstatus but would get descriptors from up to
6749 18 hours earlier, meaning most of the descriptors were obsolete
6750 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
6751 - Prevent bridge relays from serving their 'extrainfo' document
6752 to anybody who asks, now that extrainfo docs include potentially
6753 sensitive aggregated client geoip summaries. Bugfix on
6757 - New controller event "clients_seen" to report a geoip-based summary
6758 of which countries we've seen clients from recently. Now controllers
6759 like Vidalia can show bridge operators that they're actually making
6761 - Build correctly against versions of OpenSSL 0.9.8 or later built
6762 without support for deprecated functions.
6763 - Update to the "December 19 2008" ip-to-country file.
6765 o Minor bugfixes (on 0.2.0.x):
6766 - Authorities now vote for the Stable flag for any router whose
6767 weighted MTBF is at least 5 days, regardless of the mean MTBF.
6768 - Do not remove routers as too old if we do not have any consensus
6769 document. Bugfix on 0.2.0.7-alpha.
6770 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
6771 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
6772 - When an exit relay resolves a stream address to a local IP address,
6773 do not just keep retrying that same exit relay over and
6774 over. Instead, just close the stream. Addresses bug 872. Bugfix
6775 on 0.2.0.32. Patch from rovv.
6776 - If a hidden service sends us an END cell, do not consider
6777 retrying the connection; just close it. Patch from rovv.
6778 - When we made bridge authorities stop serving bridge descriptors over
6779 unencrypted links, we also broke DirPort reachability testing for
6780 bridges. So bridges with a non-zero DirPort were printing spurious
6781 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
6782 - When a relay gets a create cell it can't decrypt (e.g. because it's
6783 using the wrong onion key), we were dropping it and letting the
6784 client time out. Now actually answer with a destroy cell. Fixes
6785 bug 904. Bugfix on 0.0.2pre8.
6786 - Squeeze 2-5% out of client performance (according to oprofile) by
6787 improving the implementation of some policy-manipulation functions.
6789 o Minor bugfixes (on 0.2.1.x):
6790 - Make get_interface_address() function work properly again; stop
6791 guessing the wrong parts of our address as our address.
6792 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
6793 send on that circuit. Otherwise we might violate the proposal-110
6794 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
6796 - When we're sending non-EXTEND cells to the first hop in a circuit,
6797 for example to use an encrypted directory connection, we don't need
6798 to use RELAY_EARLY cells: the first hop knows what kind of cell
6799 it is, and nobody else can even see the cell type. Conserving
6800 RELAY_EARLY cells makes it easier to cannibalize circuits like
6802 - Stop logging nameserver addresses in reverse order.
6803 - If we are retrying a directory download slowly over and over, do
6804 not automatically give up after the 254th failure. Bugfix on
6806 - Resume reporting accurate "stream end" reasons to the local control
6807 port. They were lost in the changes for Proposal 148. Bugfix on
6810 o Deprecated and removed features:
6811 - The old "tor --version --version" command, which would print out
6812 the subversion "Id" of most of the source files, is now removed. It
6813 turned out to be less useful than we'd expected, and harder to
6816 o Code simplifications and refactoring:
6817 - Change our header file guard macros to be less likely to conflict
6818 with system headers. Adam Langley noticed that we were conflicting
6819 with log.h on Android.
6820 - Tool-assisted documentation cleanup. Nearly every function or
6821 static variable in Tor should have its own documentation now.
6824 Changes in version 0.2.1.9-alpha - 2008-12-25
6825 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
6827 o New directory authorities:
6828 - gabelmoo (the authority run by Karsten Loesing) now has a new
6832 - Never use a connection with a mismatched address to extend a
6833 circuit, unless that connection is canonical. A canonical
6834 connection is one whose address is authenticated by the router's
6835 identity key, either in a NETINFO cell or in a router descriptor.
6836 - Avoid a possible memory corruption bug when receiving hidden service
6837 descriptors. Bugfix on 0.2.1.6-alpha.
6840 - Fix a logic error that would automatically reject all but the first
6841 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
6842 part of bug 813/868. Bug spotted by coderman.
6843 - When a stream at an exit relay is in state "resolving" or
6844 "connecting" and it receives an "end" relay cell, the exit relay
6845 would silently ignore the end cell and not close the stream. If
6846 the client never closes the circuit, then the exit relay never
6847 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
6849 - When we can't initialize DNS because the network is down, do not
6850 automatically stop Tor from starting. Instead, retry failed
6851 dns_init() every 10 minutes, and change the exit policy to reject
6852 *:* until one succeeds. Fixes bug 691.
6855 - Give a better error message when an overzealous init script says
6856 "sudo -u username tor --user username". Makes Bug 882 easier for
6858 - When a directory authority gives us a new guess for our IP address,
6859 log which authority we used. Hopefully this will help us debug
6860 the recent complaints about bad IP address guesses.
6861 - Detect svn revision properly when we're using git-svn.
6862 - Try not to open more than one descriptor-downloading connection
6863 to an authority at once. This should reduce load on directory
6864 authorities. Fixes bug 366.
6865 - Add cross-certification to newly generated certificates, so that
6866 a signing key is enough information to look up a certificate.
6867 Partial implementation of proposal 157.
6868 - Start serving certificates by <identity digest, signing key digest>
6869 pairs. Partial implementation of proposal 157.
6870 - Clients now never report any stream end reason except 'MISC'.
6871 Implements proposal 148.
6872 - On platforms with a maximum syslog string length, truncate syslog
6873 messages to that length ourselves, rather than relying on the
6874 system to do it for us.
6875 - Optimize out calls to time(NULL) that occur for every IO operation,
6876 or for every cell. On systems where time() is a slow syscall,
6877 this fix will be slightly helpful.
6878 - Exit servers can now answer resolve requests for ip6.arpa addresses.
6879 - When we download a descriptor that we then immediately (as
6880 a directory authority) reject, do not retry downloading it right
6881 away. Should save some bandwidth on authorities. Fix for bug
6882 888. Patch by Sebastian Hahn.
6883 - When a download gets us zero good descriptors, do not notify
6884 Tor that new directory information has arrived.
6885 - Avoid some nasty corner cases in the logic for marking connections
6886 as too old or obsolete or noncanonical for circuits. Partial
6889 o Minor features (controller):
6890 - New CONSENSUS_ARRIVED event to note when a new consensus has
6891 been fetched and validated.
6892 - When we realize that another process has modified our cached
6893 descriptors file, print out a more useful error message rather
6894 than triggering an assertion. Fixes bug 885. Patch from Karsten.
6895 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
6896 controllers to prevent SIGHUP from reloading the
6897 configuration. Fixes bug 856.
6900 - Resume using the correct "REASON=" stream when telling the
6901 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
6902 - When a canonical connection appears later in our internal list
6903 than a noncanonical one for a given OR ID, always use the
6904 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
6906 - Clip the MaxCircuitDirtiness config option to a minimum of 10
6907 seconds. Warn the user if lower values are given in the
6908 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
6909 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
6910 user if lower values are given in the configuration. Bugfix on
6911 0.1.1.17-rc. Patch by Sebastian.
6912 - Fix a race condition when freeing keys shared between main thread
6913 and CPU workers that could result in a memory leak. Bugfix on
6914 0.1.0.1-rc. Fixes bug 889.
6916 o Minor bugfixes (hidden services):
6917 - Do not throw away existing introduction points on SIGHUP (bugfix on
6918 0.0.6pre1); also, do not stall hidden services because we're
6919 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
6920 by John Brooks. Patch by Karsten. Fixes bug 874.
6921 - Fix a memory leak when we decline to add a v2 rendezvous
6922 descriptor to the cache because we already had a v0 descriptor
6923 with the same ID. Bugfix on 0.2.0.18-alpha.
6925 o Deprecated and removed features:
6926 - RedirectExits has been removed. It was deprecated since
6928 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
6929 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
6930 - Cell pools are now always enabled; --disable-cell-pools is ignored.
6932 o Code simplifications and refactoring:
6933 - Rename the confusing or_is_obsolete field to the more appropriate
6934 is_bad_for_new_circs, and move it to or_connection_t where it
6936 - Move edge-only flags from connection_t to edge_connection_t: not
6937 only is this better coding, but on machines of plausible alignment,
6938 it should save 4-8 bytes per connection_t. "Every little bit helps."
6939 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
6940 for consistency; keep old option working for backward compatibility.
6941 - Simplify the code for finding connections to use for a circuit.
6944 Changes in version 0.2.1.8-alpha - 2008-12-08
6945 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
6946 builds better on unusual platforms like Solaris and old OS X, and
6947 fixes a variety of other issues.
6950 - New DirPortFrontPage option that takes an html file and publishes
6951 it as "/" on the DirPort. Now relay operators can provide a
6952 disclaimer without needing to set up a separate webserver. There's
6953 a sample disclaimer in contrib/tor-exit-notice.html.
6956 - When the client is choosing entry guards, now it selects at most
6957 one guard from a given relay family. Otherwise we could end up with
6958 all of our entry points into the network run by the same operator.
6959 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
6962 - Fix a DOS opportunity during the voting signature collection process
6963 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
6964 - Fix a possible segfault when establishing an exit connection. Bugfix
6968 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
6970 - Made Tor a little less aggressive about deleting expired
6971 certificates. Partial fix for bug 854.
6972 - Stop doing unaligned memory access that generated bus errors on
6973 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
6974 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
6975 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
6976 - Make USR2 log-level switch take effect immediately. Bugfix on
6978 - If one win32 nameserver fails to get added, continue adding the
6979 rest, and don't automatically fail.
6980 - Use fcntl() for locking when flock() is not available. Should fix
6981 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
6982 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
6983 could make gcc generate non-functional binary search code. Bugfix
6985 - Build correctly on platforms without socklen_t.
6986 - Avoid potential crash on internal error during signature collection.
6987 Fixes bug 864. Patch from rovv.
6988 - Do not use C's stdio library for writing to log files. This will
6989 improve logging performance by a minute amount, and will stop
6990 leaking fds when our disk is full. Fixes bug 861.
6991 - Stop erroneous use of O_APPEND in cases where we did not in fact
6992 want to re-seek to the end of a file before every last write().
6993 - Correct handling of possible malformed authority signing key
6994 certificates with internal signature types. Fixes bug 880. Bugfix
6996 - Fix a hard-to-trigger resource leak when logging credential status.
7000 - Directory mirrors no longer fetch the v1 directory or
7001 running-routers files. They are obsolete, and nobody asks for them
7002 anymore. This is the first step to making v1 authorities obsolete.
7004 o Minor features (controller):
7005 - Return circuit purposes in response to GETINFO circuit-status. Fixes
7009 Changes in version 0.2.0.32 - 2008-11-20
7010 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
7011 packages (and maybe other packages) noticed by Theo de Raadt, fixes
7012 a smaller security flaw that might allow an attacker to access local
7013 services, further improves hidden service performance, and fixes a
7014 variety of other issues.
7017 - The "User" and "Group" config options did not clear the
7018 supplementary group entries for the Tor process. The "User" option
7019 is now more robust, and we now set the groups to the specified
7020 user's primary group. The "Group" option is now ignored. For more
7021 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
7022 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
7023 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
7024 - The "ClientDNSRejectInternalAddresses" config option wasn't being
7025 consistently obeyed: if an exit relay refuses a stream because its
7026 exit policy doesn't allow it, we would remember what IP address
7027 the relay said the destination address resolves to, even if it's
7028 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
7031 - Fix a DOS opportunity during the voting signature collection process
7032 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
7034 o Major bugfixes (hidden services):
7035 - When fetching v0 and v2 rendezvous service descriptors in parallel,
7036 we were failing the whole hidden service request when the v0
7037 descriptor fetch fails, even if the v2 fetch is still pending and
7038 might succeed. Similarly, if the last v2 fetch fails, we were
7039 failing the whole hidden service request even if a v0 fetch is
7040 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
7041 - When extending a circuit to a hidden service directory to upload a
7042 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
7043 requests failed, because the router descriptor has not been
7044 downloaded yet. In these cases, do not attempt to upload the
7045 rendezvous descriptor, but wait until the router descriptor is
7046 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
7047 descriptor from a hidden service directory for which the router
7048 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
7052 - Fix several infrequent memory leaks spotted by Coverity.
7053 - When testing for libevent functions, set the LDFLAGS variable
7054 correctly. Found by Riastradh.
7055 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
7056 bootstrapping with tunneled directory connections. Bugfix on
7057 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
7058 - When asked to connect to A.B.exit:80, if we don't know the IP for A
7059 and we know that server B rejects most-but-not all connections to
7060 port 80, we would previously reject the connection. Now, we assume
7061 the user knows what they were asking for. Fixes bug 752. Bugfix
7062 on 0.0.9rc5. Diagnosed by BarkerJr.
7063 - If we overrun our per-second write limits a little, count this as
7064 having used up our write allocation for the second, and choke
7065 outgoing directory writes. Previously, we had only counted this when
7066 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
7067 Bugfix on 0.2.0.x (??).
7068 - Remove the old v2 directory authority 'lefkada' from the default
7069 list. It has been gone for many months.
7070 - Stop doing unaligned memory access that generated bus errors on
7071 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
7072 - Make USR2 log-level switch take effect immediately. Bugfix on
7075 o Minor bugfixes (controller):
7076 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
7077 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
7080 Changes in version 0.2.1.7-alpha - 2008-11-08
7081 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
7082 packages (and maybe other packages) noticed by Theo de Raadt, fixes
7083 a smaller security flaw that might allow an attacker to access local
7084 services, adds better defense against DNS poisoning attacks on exit
7085 relays, further improves hidden service performance, and fixes a
7086 variety of other issues.
7089 - The "ClientDNSRejectInternalAddresses" config option wasn't being
7090 consistently obeyed: if an exit relay refuses a stream because its
7091 exit policy doesn't allow it, we would remember what IP address
7092 the relay said the destination address resolves to, even if it's
7093 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
7094 - The "User" and "Group" config options did not clear the
7095 supplementary group entries for the Tor process. The "User" option
7096 is now more robust, and we now set the groups to the specified
7097 user's primary group. The "Group" option is now ignored. For more
7098 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
7099 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
7100 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
7101 - Do not use or believe expired v3 authority certificates. Patch
7102 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
7105 - Now NodeFamily and MyFamily config options allow spaces in
7106 identity fingerprints, so it's easier to paste them in.
7107 Suggested by Lucky Green.
7108 - Implement the 0x20 hack to better resist DNS poisoning: set the
7109 case on outgoing DNS requests randomly, and reject responses that do
7110 not match the case correctly. This logic can be disabled with the
7111 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
7112 of servers that do not reliably preserve case in replies. See
7113 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
7115 - Preserve case in replies to DNSPort requests in order to support
7116 the 0x20 hack for resisting DNS poisoning attacks.
7118 o Hidden service performance improvements:
7119 - When the client launches an introduction circuit, retry with a
7120 new circuit after 30 seconds rather than 60 seconds.
7121 - Launch a second client-side introduction circuit in parallel
7122 after a delay of 15 seconds (based on work by Christian Wilms).
7123 - Hidden services start out building five intro circuits rather
7124 than three, and when the first three finish they publish a service
7125 descriptor using those. Now we publish our service descriptor much
7126 faster after restart.
7129 - Minor fix in the warning messages when you're having problems
7130 bootstrapping; also, be more forgiving of bootstrap problems when
7131 we're still making incremental progress on a given bootstrap phase.
7132 - When we're choosing an exit node for a circuit, and we have
7133 no pending streams, choose a good general exit rather than one that
7134 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
7135 - Send a valid END cell back when a client tries to connect to a
7136 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
7137 840. Patch from rovv.
7138 - If a broken client asks a non-exit router to connect somewhere,
7139 do not even do the DNS lookup before rejecting the connection.
7140 Fixes another case of bug 619. Patch from rovv.
7141 - Fix another case of assuming, when a specific exit is requested,
7142 that we know more than the user about what hosts it allows.
7143 Fixes another case of bug 752. Patch from rovv.
7144 - Check which hops rendezvous stream cells are associated with to
7145 prevent possible guess-the-streamid injection attacks from
7146 intermediate hops. Fixes another case of bug 446. Based on patch
7148 - Avoid using a negative right-shift when comparing 32-bit
7149 addresses. Possible fix for bug 845 and bug 811.
7150 - Make the assert_circuit_ok() function work correctly on circuits that
7151 have already been marked for close.
7152 - Fix read-off-the-end-of-string error in unit tests when decoding
7153 introduction points.
7154 - Fix uninitialized size field for memory area allocation: may improve
7155 memory performance during directory parsing.
7156 - Treat duplicate certificate fetches as failures, so that we do
7157 not try to re-fetch an expired certificate over and over and over.
7158 - Do not say we're fetching a certificate when we'll in fact skip it
7159 because of a pending download.
7162 Changes in version 0.2.1.6-alpha - 2008-09-30
7163 Tor 0.2.1.6-alpha further improves performance and robustness of
7164 hidden services, starts work on supporting per-country relay selection,
7165 and fixes a variety of smaller issues.
7168 - Implement proposal 121: make it possible to build hidden services
7169 that only certain clients are allowed to connect to. This is
7170 enforced at several points, so that unauthorized clients are unable
7171 to send INTRODUCE cells to the service, or even (depending on the
7172 type of authentication) to learn introduction points. This feature
7173 raises the bar for certain kinds of active attacks against hidden
7174 services. Code by Karsten Loesing.
7175 - Relays now store and serve v2 hidden service descriptors by default,
7176 i.e., the new default value for HidServDirectoryV2 is 1. This is
7177 the last step in proposal 114, which aims to make hidden service
7178 lookups more reliable.
7179 - Start work to allow node restrictions to include country codes. The
7180 syntax to exclude nodes in a country with country code XX is
7181 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
7182 refinement to decide what config options should take priority if
7183 you ask to both use a particular node and exclude it.
7184 - Allow ExitNodes list to include IP ranges and country codes, just
7185 like the Exclude*Nodes lists. Patch from Robert Hogan.
7188 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
7189 Tor to fail to start if you had it configured to use a bridge
7190 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
7191 - When extending a circuit to a hidden service directory to upload a
7192 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
7193 requests failed, because the router descriptor had not been
7194 downloaded yet. In these cases, we now wait until the router
7195 descriptor is downloaded, and then retry. Likewise, clients
7196 now skip over a hidden service directory if they don't yet have
7197 its router descriptor, rather than futilely requesting it and
7198 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
7200 - When fetching v0 and v2 rendezvous service descriptors in parallel,
7201 we were failing the whole hidden service request when the v0
7202 descriptor fetch fails, even if the v2 fetch is still pending and
7203 might succeed. Similarly, if the last v2 fetch fails, we were
7204 failing the whole hidden service request even if a v0 fetch is
7205 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
7206 - DNS replies need to have names matching their requests, but
7207 these names should be in the questions section, not necessarily
7208 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
7211 - Update to the "September 1 2008" ip-to-country file.
7212 - Allow ports 465 and 587 in the default exit policy again. We had
7213 rejected them in 0.1.0.15, because back in 2005 they were commonly
7214 misconfigured and ended up as spam targets. We hear they are better
7215 locked down these days.
7216 - Use a lockfile to make sure that two Tor processes are not
7217 simultaneously running with the same datadir.
7218 - Serve the latest v3 networkstatus consensus via the control
7219 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
7220 - Better logging about stability/reliability calculations on directory
7222 - Drop the requirement to have an open dir port for storing and
7223 serving v2 hidden service descriptors.
7224 - Directory authorities now serve a /tor/dbg-stability.txt URL to
7225 help debug WFU and MTBF calculations.
7226 - Implement most of Proposal 152: allow specialized servers to permit
7227 single-hop circuits, and clients to use those servers to build
7228 single-hop circuits when using a specialized controller. Patch
7229 from Josh Albrecht. Resolves feature request 768.
7230 - Add a -p option to tor-resolve for specifying the SOCKS port: some
7231 people find host:port too confusing.
7232 - Make TrackHostExit mappings expire a while after their last use, not
7233 after their creation. Patch from Robert Hogan.
7234 - Provide circuit purposes along with circuit events to the controller.
7237 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
7239 - Fixed some memory leaks -- some quite frequent, some almost
7240 impossible to trigger -- based on results from Coverity.
7241 - When testing for libevent functions, set the LDFLAGS variable
7242 correctly. Found by Riastradh.
7243 - Fix an assertion bug in parsing policy-related options; possible fix
7245 - Catch and report a few more bootstrapping failure cases when Tor
7246 fails to establish a TCP connection. Cleanup on 0.2.1.x.
7247 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
7248 bootstrapping with tunneled directory connections. Bugfix on
7249 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
7250 - When asked to connect to A.B.exit:80, if we don't know the IP for A
7251 and we know that server B rejects most-but-not all connections to
7252 port 80, we would previously reject the connection. Now, we assume
7253 the user knows what they were asking for. Fixes bug 752. Bugfix
7254 on 0.0.9rc5. Diagnosed by BarkerJr.
7255 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
7256 service directories if they have no advertised dir port. Bugfix
7258 - If we overrun our per-second write limits a little, count this as
7259 having used up our write allocation for the second, and choke
7260 outgoing directory writes. Previously, we had only counted this when
7261 we had met our limits precisely. Fixes bug 824. Patch by rovv.
7262 Bugfix on 0.2.0.x (??).
7263 - Avoid a "0 divided by 0" calculation when calculating router uptime
7264 at directory authorities. Bugfix on 0.2.0.8-alpha.
7265 - Make DNS resolved controller events into "CLOSED", not
7266 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
7268 - Fix a bug where an unreachable relay would establish enough
7269 reachability testing circuits to do a bandwidth test -- if
7270 we already have a connection to the middle hop of the testing
7271 circuit, then it could establish the last hop by using the existing
7272 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
7273 circuits no longer use entry guards in 0.2.1.3-alpha.
7274 - If we have correct permissions on $datadir, we complain to stdout
7275 and fail to start. But dangerous permissions on
7276 $datadir/cached-status/ would cause us to open a log and complain
7277 there. Now complain to stdout and fail to start in both cases. Fixes
7278 bug 820, reported by seeess.
7279 - Remove the old v2 directory authority 'lefkada' from the default
7280 list. It has been gone for many months.
7282 o Code simplifications and refactoring:
7283 - Revise the connection_new functions so that a more typesafe variant
7284 exists. This will work better with Coverity, and let us find any
7285 actual mistakes we're making here.
7286 - Refactor unit testing logic so that dmalloc can be used sensibly
7287 with unit tests to check for memory leaks.
7288 - Move all hidden-service related fields from connection and circuit
7289 structure to substructures: this way they won't eat so much memory.
7292 Changes in version 0.2.0.31 - 2008-09-03
7293 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
7294 a big bug we're seeing where in rare cases traffic from one Tor stream
7295 gets mixed into another stream, and fixes a variety of smaller issues.
7298 - Make sure that two circuits can never exist on the same connection
7299 with the same circuit ID, even if one is marked for close. This
7300 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
7301 - Relays now reject risky extend cells: if the extend cell includes
7302 a digest of all zeroes, or asks to extend back to the relay that
7303 sent the extend cell, tear down the circuit. Ideas suggested
7305 - If not enough of our entry guards are available so we add a new
7306 one, we might use the new one even if it overlapped with the
7307 current circuit's exit relay (or its family). Anonymity bugfix
7308 pointed out by rovv.
7311 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
7312 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
7313 - Correctly detect the presence of the linux/netfilter_ipv4.h header
7314 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
7315 - Pick size of default geoip filename string correctly on windows.
7316 Fixes bug 806. Bugfix on 0.2.0.30.
7317 - Make the autoconf script accept the obsolete --with-ssl-dir
7318 option as an alias for the actually-working --with-openssl-dir
7319 option. Fix the help documentation to recommend --with-openssl-dir.
7320 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
7321 - When using the TransPort option on OpenBSD, and using the User
7322 option to change UID and drop privileges, make sure to open
7323 /dev/pf before dropping privileges. Fixes bug 782. Patch from
7324 Christopher Davis. Bugfix on 0.1.2.1-alpha.
7325 - Try to attach connections immediately upon receiving a RENDEZVOUS2
7326 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
7327 on the client side when connecting to a hidden service. Bugfix
7328 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
7329 - When closing an application-side connection because its circuit is
7330 getting torn down, generate the stream event correctly. Bugfix on
7331 0.1.2.x. Anonymous patch.
7334 Changes in version 0.2.1.5-alpha - 2008-08-31
7335 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
7336 in a lot of the infrastructure for adding authorization to hidden
7337 services, lays the groundwork for having clients read their load
7338 balancing information out of the networkstatus consensus rather than
7339 the individual router descriptors, addresses two potential anonymity
7340 issues, and fixes a variety of smaller issues.
7343 - Convert many internal address representations to optionally hold
7345 - Generate and accept IPv6 addresses in many protocol elements.
7346 - Make resolver code handle nameservers located at ipv6 addresses.
7347 - Begin implementation of proposal 121 ("Client authorization for
7348 hidden services"): configure hidden services with client
7349 authorization, publish descriptors for them, and configure
7350 authorization data for hidden services at clients. The next
7351 step is to actually access hidden services that perform client
7353 - More progress toward proposal 141: Network status consensus
7354 documents and votes now contain bandwidth information for each
7355 router and a summary of that router's exit policy. Eventually this
7356 will be used by clients so that they do not have to download every
7357 known descriptor before building circuits.
7359 o Major bugfixes (on 0.2.0.x and before):
7360 - When sending CREATED cells back for a given circuit, use a 64-bit
7361 connection ID to find the right connection, rather than an addr:port
7362 combination. Now that we can have multiple OR connections between
7363 the same ORs, it is no longer possible to use addr:port to uniquely
7364 identify a connection.
7365 - Relays now reject risky extend cells: if the extend cell includes
7366 a digest of all zeroes, or asks to extend back to the relay that
7367 sent the extend cell, tear down the circuit. Ideas suggested
7369 - If not enough of our entry guards are available so we add a new
7370 one, we might use the new one even if it overlapped with the
7371 current circuit's exit relay (or its family). Anonymity bugfix
7372 pointed out by rovv.
7375 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
7376 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
7377 - When using the TransPort option on OpenBSD, and using the User
7378 option to change UID and drop privileges, make sure to open /dev/pf
7379 before dropping privileges. Fixes bug 782. Patch from Christopher
7380 Davis. Bugfix on 0.1.2.1-alpha.
7381 - Correctly detect the presence of the linux/netfilter_ipv4.h header
7382 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
7383 - Add a missing safe_str() call for a debug log message.
7384 - Use 64 bits instead of 32 bits for connection identifiers used with
7385 the controller protocol, to greatly reduce risk of identifier reuse.
7386 - Make the autoconf script accept the obsolete --with-ssl-dir
7387 option as an alias for the actually-working --with-openssl-dir
7388 option. Fix the help documentation to recommend --with-openssl-dir.
7389 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
7392 - Rate-limit too-many-sockets messages: when they happen, they happen
7393 a lot. Resolves bug 748.
7394 - Resist DNS poisoning a little better by making sure that names in
7395 answer sections match.
7396 - Print the SOCKS5 error message string as well as the error code
7397 when a tor-resolve request fails. Patch from Jacob.
7400 Changes in version 0.2.1.4-alpha - 2008-08-04
7401 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
7404 - The address part of exit policies was not correctly written
7405 to router descriptors. This generated router descriptors that failed
7406 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
7408 - Tor triggered a false assert when extending a circuit to a relay
7409 but we already have a connection open to that relay. Noticed by
7410 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
7413 - Fix a hidden service logging bug: in some edge cases, the router
7414 descriptor of a previously picked introduction point becomes
7415 obsolete and we need to give up on it rather than continually
7416 complaining that it has become obsolete. Observed by xiando. Bugfix
7420 - Take out the TestVia config option, since it was a workaround for
7421 a bug that was fixed in Tor 0.1.1.21.
7424 Changes in version 0.2.1.3-alpha - 2008-08-03
7425 Tor 0.2.1.3-alpha implements most of the pieces to prevent
7426 infinite-length circuit attacks (see proposal 110); fixes a bug that
7427 might cause exit relays to corrupt streams they send back; allows
7428 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
7429 ExcludeExitNodes config options; and fixes a big pile of bugs.
7431 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
7432 - Send a bootstrap problem "warn" event on the first problem if the
7433 reason is NO_ROUTE (that is, our network is down).
7436 - Implement most of proposal 110: The first K cells to be sent
7437 along a circuit are marked as special "early" cells; only K "early"
7438 cells will be allowed. Once this code is universal, we can block
7439 certain kinds of DOS attack by requiring that EXTEND commands must
7440 be sent using an "early" cell.
7443 - Try to attach connections immediately upon receiving a RENDEZVOUS2
7444 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
7445 on the client side when connecting to a hidden service. Bugfix
7446 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
7447 - Ensure that two circuits can never exist on the same connection
7448 with the same circuit ID, even if one is marked for close. This
7449 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
7452 - When relays do their initial bandwidth measurement, don't limit
7453 to just our entry guards for the test circuits. Otherwise we tend
7454 to have multiple test circuits going through a single entry guard,
7455 which makes our bandwidth test less accurate. Fixes part of bug 654;
7456 patch contributed by Josh Albrecht.
7457 - Add an ExcludeExitNodes option so users can list a set of nodes
7458 that should be be excluded from the exit node position, but
7459 allowed elsewhere. Implements proposal 151.
7460 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
7461 ExcludeNodes and ExcludeExitNodes lists.
7462 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
7463 be more efficient. Formerly it was quadratic in the number of
7464 servers; now it should be linear. Fixes bug 509.
7465 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
7466 and n_conn_id_digest fields into a separate structure that's
7467 only needed when the circuit has not yet attached to an n_conn.
7470 - Change the contrib/tor.logrotate script so it makes the new
7471 logs as "_tor:_tor" rather than the default, which is generally
7472 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
7473 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
7474 warnings (occasionally), but it can also cause the compiler to
7475 eliminate error-checking code. Suggested by Peter Gutmann.
7476 - When a hidden service is giving up on an introduction point candidate
7477 that was not included in the last published rendezvous descriptor,
7478 don't reschedule publication of the next descriptor. Fixes bug 763.
7480 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
7481 HiddenServiceExcludeNodes as obsolete: they never worked properly,
7482 and nobody claims to be using them. Fixes bug 754. Bugfix on
7483 0.1.0.1-rc. Patch from Christian Wilms.
7484 - Fix a small alignment and memory-wasting bug on buffer chunks.
7487 o Minor bugfixes (controller):
7488 - When closing an application-side connection because its circuit
7489 is getting torn down, generate the stream event correctly.
7490 Bugfix on 0.1.2.x. Anonymous patch.
7493 - Remove all backward-compatibility code to support relays running
7494 versions of Tor so old that they no longer work at all on the
7498 Changes in version 0.2.0.30 - 2008-07-15
7500 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
7501 warnings (occasionally), but it can also cause the compiler to
7502 eliminate error-checking code. Suggested by Peter Gutmann.
7505 Changes in version 0.2.0.29-rc - 2008-07-08
7506 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
7507 hidden-service performance bugs, and fixes a bunch of smaller bugs.
7510 - If you have more than one bridge but don't know their keys,
7511 you would only launch a request for the descriptor of the first one
7512 on your list. (Tor considered launching requests for the others, but
7513 found that it already had a connection on the way for $0000...0000
7514 so it didn't open another.) Bugfix on 0.2.0.x.
7515 - If you have more than one bridge but don't know their keys, and the
7516 connection to one of the bridges failed, you would cancel all
7517 pending bridge connections. (After all, they all have the same
7518 digest.) Bugfix on 0.2.0.x.
7519 - When a hidden service was trying to establish an introduction point,
7520 and Tor had built circuits preemptively for such purposes, we
7521 were ignoring all the preemptive circuits and launching a new one
7522 instead. Bugfix on 0.2.0.14-alpha.
7523 - When a hidden service was trying to establish an introduction point,
7524 and Tor *did* manage to reuse one of the preemptively built
7525 circuits, it didn't correctly remember which one it used,
7526 so it asked for another one soon after, until there were no
7527 more preemptive circuits, at which point it launched one from
7528 scratch. Bugfix on 0.0.9.x.
7529 - Make directory servers include the X-Your-Address-Is: http header in
7530 their responses even for begin_dir conns. Now clients who only
7531 ever use begin_dir connections still have a way to learn their IP
7532 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
7535 - Fix a macro/CPP interaction that was confusing some compilers:
7536 some GCCs don't like #if/#endif pairs inside macro arguments.
7538 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
7539 Fixes bug 704; fix from Steven Murdoch.
7540 - When opening /dev/null in finish_daemonize(), do not pass the
7541 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
7542 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
7543 - Correctly detect transparent proxy support on Linux hosts that
7544 require in.h to be included before netfilter_ipv4.h. Patch
7546 - Disallow session resumption attempts during the renegotiation
7547 stage of the v2 handshake protocol. Clients should never be trying
7548 session resumption at this point, but apparently some did, in
7549 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
7550 found by Geoff Goodell.
7553 Changes in version 0.2.1.2-alpha - 2008-06-20
7554 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
7555 make it easier to set up your own private Tor network; fixes several
7556 big bugs with using more than one bridge relay; fixes a big bug with
7557 offering hidden services quickly after Tor starts; and uses a better
7558 API for reporting potential bootstrapping problems to the controller.
7561 - New TestingTorNetwork config option to allow adjustment of
7562 previously constant values that, while reasonable, could slow
7563 bootstrapping. Implements proposal 135. Patch from Karsten.
7566 - If you have more than one bridge but don't know their digests,
7567 you would only learn a request for the descriptor of the first one
7568 on your list. (Tor considered launching requests for the others, but
7569 found that it already had a connection on the way for $0000...0000
7570 so it didn't open another.) Bugfix on 0.2.0.x.
7571 - If you have more than one bridge but don't know their digests,
7572 and the connection to one of the bridges failed, you would cancel
7573 all pending bridge connections. (After all, they all have the
7574 same digest.) Bugfix on 0.2.0.x.
7575 - When establishing a hidden service, introduction points that
7576 originate from cannibalized circuits are completely ignored and not
7577 included in rendezvous service descriptors. This might be another
7578 reason for delay in making a hidden service available. Bugfix
7579 from long ago (0.0.9.x?)
7582 - Allow OpenSSL to use dynamic locks if it wants.
7583 - When building a consensus, do not include routers that are down.
7584 This will cut down 30% to 40% on consensus size. Implements
7586 - In directory authorities' approved-routers files, allow
7587 fingerprints with or without space.
7588 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
7589 controller can query our current bootstrap state in case it attaches
7590 partway through and wants to catch up.
7591 - Send an initial "Starting" bootstrap status event, so we have a
7592 state to start out in.
7595 - Asking for a conditional consensus at .../consensus/<fingerprints>
7596 would crash a dirserver if it did not already have a
7597 consensus. Bugfix on 0.2.1.1-alpha.
7598 - Clean up some macro/CPP interactions: some GCC versions don't like
7599 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
7602 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
7603 - Directory authorities shouldn't complain about bootstrapping
7604 problems just because they do a lot of reachability testing and
7605 some of the connection attempts fail.
7606 - Start sending "count" and "recommendation" key/value pairs in
7607 bootstrap problem status events, so the controller can hear about
7608 problems even before Tor decides they're worth reporting for sure.
7609 - If you're using bridges, generate "bootstrap problem" warnings
7610 as soon as you run out of working bridges, rather than waiting
7611 for ten failures -- which will never happen if you have less than
7613 - If we close our OR connection because there's been a circuit
7614 pending on it for too long, we were telling our bootstrap status
7615 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
7618 Changes in version 0.2.1.1-alpha - 2008-06-13
7619 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
7620 were making the Tor process bloat especially on Linux; makes our TLS
7621 handshake blend in better; sends "bootstrap phase" status events to
7622 the controller, so it can keep the user informed of progress (and
7623 problems) fetching directory information and establishing circuits;
7624 and adds a variety of smaller features.
7627 - More work on making our TLS handshake blend in: modify the list
7628 of ciphers advertised by OpenSSL in client mode to even more
7629 closely resemble a common web browser. We cheat a little so that
7630 we can advertise ciphers that the locally installed OpenSSL doesn't
7632 - Start sending "bootstrap phase" status events to the controller,
7633 so it can keep the user informed of progress fetching directory
7634 information and establishing circuits. Also inform the controller
7635 if we think we're stuck at a particular bootstrap phase. Implements
7637 - Resume using OpenSSL's RAND_poll() for better (and more portable)
7638 cross-platform entropy collection again. We used to use it, then
7639 stopped using it because of a bug that could crash systems that
7640 called RAND_poll when they had a lot of fds open. It looks like the
7641 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
7642 at startup, and to call RAND_poll() when we reseed later only if
7643 we have a non-buggy OpenSSL version.
7646 - When we choose to abandon a new entry guard because we think our
7647 older ones might be better, close any circuits pending on that
7648 new entry guard connection. This fix should make us recover much
7649 faster when our network is down and then comes back. Bugfix on
7650 0.1.2.8-beta; found by lodger.
7652 o Memory fixes and improvements:
7653 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
7654 to avoid unused RAM in buffer chunks and memory pools.
7655 - Speed up parsing and cut down on memory fragmentation by using
7656 stack-style allocations for parsing directory objects. Previously,
7657 this accounted for over 40% of allocations from within Tor's code
7658 on a typical directory cache.
7659 - Use a Bloom filter rather than a digest-based set to track which
7660 descriptors we need to keep around when we're cleaning out old
7661 router descriptors. This speeds up the computation significantly,
7662 and may reduce fragmentation.
7663 - Reduce the default smartlist size from 32 to 16; it turns out that
7664 most smartlists hold around 8-12 elements tops.
7665 - Make dumpstats() log the fullness and size of openssl-internal
7667 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
7668 patch to their OpenSSL, turn it on to save memory on servers. This
7669 patch will (with any luck) get included in a mainline distribution
7671 - Never use OpenSSL compression: it wastes RAM and CPU trying to
7672 compress cells, which are basically all encrypted, compressed,
7676 - Stop reloading the router list from disk for no reason when we
7677 run out of reachable directory mirrors. Once upon a time reloading
7678 it would set the 'is_running' flag back to 1 for them. It hasn't
7679 done that for a long time.
7680 - In very rare situations new hidden service descriptors were
7681 published earlier than 30 seconds after the last change to the
7682 service. (We currently think that a hidden service descriptor
7683 that's been stable for 30 seconds is worth publishing.)
7686 - Allow separate log levels to be configured for different logging
7687 domains. For example, this allows one to log all notices, warnings,
7688 or errors, plus all memory management messages of level debug or
7689 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
7690 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
7691 and stop using a warning that had become unfixably verbose under
7693 - New --hush command-line option similar to --quiet. While --quiet
7694 disables all logging to the console on startup, --hush limits the
7695 output to messages of warning and error severity.
7696 - Servers support a new URL scheme for consensus downloads that
7697 allows the client to specify which authorities are trusted.
7698 The server then only sends the consensus if the client will trust
7699 it. Otherwise a 404 error is sent back. Clients use this
7700 new scheme when the server supports it (meaning it's running
7701 0.2.1.1-alpha or later). Implements proposal 134.
7702 - New configure/torrc options (--enable-geoip-stats,
7703 DirRecordUsageByCountry) to record how many IPs we've served
7704 directory info to in each country code, how many status documents
7705 total we've sent to each country code, and what share of the total
7706 directory requests we should expect to see.
7707 - Use the TLS1 hostname extension to more closely resemble browser
7709 - Lots of new unit tests.
7710 - Add a macro to implement the common pattern of iterating through
7711 two parallel lists in lockstep.
7714 Changes in version 0.2.0.28-rc - 2008-06-13
7715 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
7716 performance bug, and fixes a bunch of smaller bugs.
7719 - Fix a bug where, when we were choosing the 'end stream reason' to
7720 put in our relay end cell that we send to the exit relay, Tor
7721 clients on Windows were sometimes sending the wrong 'reason'. The
7722 anonymity problem is that exit relays may be able to guess whether
7723 the client is running Windows, thus helping partition the anonymity
7724 set. Down the road we should stop sending reasons to exit relays,
7725 or otherwise prevent future versions of this bug.
7728 - While setting up a hidden service, some valid introduction circuits
7729 were overlooked and abandoned. This might be the reason for
7730 the long delay in making a hidden service available. Bugfix on
7734 - Update to the "June 9 2008" ip-to-country file.
7735 - Run 'make test' as part of 'make dist', so we stop releasing so
7736 many development snapshots that fail their unit tests.
7739 - When we're checking if we have enough dir info for each relay
7740 to begin establishing circuits, make sure that we actually have
7741 the descriptor listed in the consensus, not just any descriptor.
7743 - Bridge relays no longer print "xx=0" in their extrainfo document
7744 for every single country code in the geoip db. Bugfix on
7746 - Only warn when we fail to load the geoip file if we were planning to
7747 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
7748 - If we change our MaxAdvertisedBandwidth and then reload torrc,
7749 Tor won't realize it should publish a new relay descriptor. Fixes
7750 bug 688, reported by mfr. Bugfix on 0.1.2.x.
7751 - When we haven't had any application requests lately, don't bother
7752 logging that we have expired a bunch of descriptors. Bugfix
7754 - Make relay cells written on a connection count as non-padding when
7755 tracking how long a connection has been in use. Bugfix on
7756 0.2.0.1-alpha. Spotted by lodger.
7757 - Fix unit tests in 0.2.0.27-rc.
7758 - Fix compile on Windows.
7761 Changes in version 0.2.0.27-rc - 2008-06-03
7762 Tor 0.2.0.27-rc adds a few features we left out of the earlier
7763 release candidates. In particular, we now include an IP-to-country
7764 GeoIP database, so controllers can easily look up what country a
7765 given relay is in, and so bridge relays can give us some sanitized
7766 summaries about which countries are making use of bridges. (See proposal
7767 126-geoip-fetching.txt for details.)
7770 - Include an IP-to-country GeoIP file in the tarball, so bridge
7771 relays can report sanitized summaries of the usage they're seeing.
7774 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
7775 Robert Hogan. Fixes the first part of bug 681.
7776 - Make bridge authorities never serve extrainfo docs.
7777 - Add support to detect Libevent versions in the 1.4.x series
7779 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
7780 - Include a new contrib/tor-exit-notice.html file that exit relay
7781 operators can put on their website to help reduce abuse queries.
7784 - When tunneling an encrypted directory connection, and its first
7785 circuit fails, do not leave it unattached and ask the controller
7786 to deal. Fixes the second part of bug 681.
7787 - Make bridge authorities correctly expire old extrainfo documents
7791 Changes in version 0.2.0.26-rc - 2008-05-13
7792 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
7793 in Debian's OpenSSL packages. All users running any 0.2.0.x version
7794 should upgrade, whether they're running Debian or not.
7796 o Major security fixes:
7797 - Use new V3 directory authority keys on the tor26, gabelmoo, and
7798 moria1 V3 directory authorities. The old keys were generated with
7799 a vulnerable version of Debian's OpenSSL package, and must be
7800 considered compromised. Other authorities' keys were not generated
7801 with an affected version of OpenSSL.
7804 - List authority signatures as "unrecognized" based on DirServer
7805 lines, not on cert cache. Bugfix on 0.2.0.x.
7808 - Add a new V3AuthUseLegacyKey option to make it easier for
7809 authorities to change their identity keys if they have to.
7812 Changes in version 0.2.0.25-rc - 2008-04-23
7813 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
7816 - Remember to initialize threading before initializing logging.
7817 Otherwise, many BSD-family implementations will crash hard on
7818 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
7821 - Authorities correctly free policies on bad servers on
7822 exit. Fixes bug 672. Bugfix on 0.2.0.x.
7825 Changes in version 0.2.0.24-rc - 2008-04-22
7826 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
7827 v3 directory authority, makes relays with dynamic IP addresses and no
7828 DirPort notice more quickly when their IP address changes, fixes a few
7829 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
7831 o New directory authorities:
7832 - Take lefkada out of the list of v3 directory authorities, since
7833 it has been down for months.
7834 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
7838 - Detect address changes more quickly on non-directory mirror
7839 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
7841 o Minor features (security):
7842 - Reject requests for reverse-dns lookup of names that are in
7843 a private address space. Patch from lodger.
7844 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
7847 o Minor bugfixes (crashes):
7848 - Avoid a rare assert that can trigger when Tor doesn't have much
7849 directory information yet and it tries to fetch a v2 hidden
7850 service descriptor. Fixes bug 651, reported by nwf.
7851 - Initialize log mutex before initializing dmalloc. Otherwise,
7852 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
7853 - Use recursive pthread mutexes in order to avoid deadlock when
7854 logging debug-level messages to a controller. Bug spotted by nwf,
7855 bugfix on 0.2.0.16-alpha.
7857 o Minor bugfixes (resource management):
7858 - Keep address policies from leaking memory: start their refcount
7859 at 1, not 2. Bugfix on 0.2.0.16-alpha.
7860 - Free authority certificates on exit, so they don't look like memory
7861 leaks. Bugfix on 0.2.0.19-alpha.
7862 - Free static hashtables for policy maps and for TLS connections on
7863 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
7864 - Avoid allocating extra space when computing consensuses on 64-bit
7865 platforms. Bug spotted by aakova.
7867 o Minor bugfixes (misc):
7868 - Do not read the configuration file when we've only been told to
7869 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
7870 based on patch from Sebastian Hahn.
7871 - Exit relays that are used as a client can now reach themselves
7872 using the .exit notation, rather than just launching an infinite
7873 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
7874 - When attempting to open a logfile fails, tell us why.
7875 - Fix a dumb bug that was preventing us from knowing that we should
7876 preemptively build circuits to handle expected directory requests.
7877 Fixes bug 660. Bugfix on 0.1.2.x.
7878 - Warn less verbosely about clock skew from netinfo cells from
7879 untrusted sources. Fixes bug 663.
7880 - Make controller stream events for DNS requests more consistent,
7881 by adding "new stream" events for DNS requests, and removing
7882 spurious "stream closed" events" for cached reverse resolves.
7883 Patch from mwenge. Fixes bug 646.
7884 - Correctly notify one-hop connections when a circuit build has
7885 failed. Possible fix for bug 669. Found by lodger.
7888 Changes in version 0.2.0.23-rc - 2008-03-24
7889 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
7890 makes bootstrapping faster if the first directory mirror you contact
7891 is down. The bundles also include the new Vidalia 0.1.2 release.
7894 - When a tunneled directory request is made to a directory server
7895 that's down, notice after 30 seconds rather than 120 seconds. Also,
7896 fail any begindir streams that are pending on it, so they can
7897 retry elsewhere. This was causing multi-minute delays on bootstrap.
7900 Changes in version 0.2.0.22-rc - 2008-03-18
7901 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
7902 enables encrypted directory connections by default for non-relays, fixes
7903 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
7904 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
7907 - Enable encrypted directory connections by default for non-relays,
7908 so censor tools that block Tor directory connections based on their
7909 plaintext patterns will no longer work. This means Tor works in
7910 certain censored countries by default again.
7913 - Make sure servers always request certificates from clients during
7914 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
7915 - Do not enter a CPU-eating loop when a connection is closed in
7916 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
7917 diagnosed by lodger; bugfix on 0.2.0.20-rc.
7918 - Fix assertion failure that could occur when a blocked circuit
7919 became unblocked, and it had pending client DNS requests. Bugfix
7920 on 0.2.0.1-alpha. Fixes bug 632.
7922 o Minor bugfixes (on 0.1.2.x):
7923 - Generate "STATUS_SERVER" events rather than misspelled
7924 "STATUS_SEVER" events. Caught by mwenge.
7925 - When counting the number of bytes written on a TLS connection,
7926 look at the BIO actually used for writing to the network, not
7927 at the BIO used (sometimes) to buffer data for the network.
7928 Looking at different BIOs could result in write counts on the
7929 order of ULONG_MAX. Fixes bug 614.
7930 - On Windows, correctly detect errors when listing the contents of
7931 a directory. Fix from lodger.
7933 o Minor bugfixes (on 0.2.0.x):
7934 - Downgrade "sslv3 alert handshake failure" message to INFO.
7935 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
7936 left BandwidthRate and BandwidthBurst at the default, we would be
7937 silently limited by those defaults. Now raise them to match the
7938 RelayBandwidth* values.
7939 - Fix the SVK version detection logic to work correctly on a branch.
7940 - Make --enable-openbsd-malloc work correctly on Linux with alpha
7941 CPUs. Fixes bug 625.
7942 - Logging functions now check that the passed severity is sane.
7943 - Use proper log levels in the testsuite call of
7944 get_interface_address6().
7945 - When using a nonstandard malloc, do not use the platform values for
7946 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
7947 - Make the openbsd malloc code use 8k pages on alpha CPUs and
7949 - Detect mismatched page sizes when using --enable-openbsd-malloc.
7950 - Avoid double-marked-for-close warning when certain kinds of invalid
7951 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
7952 for bug 617. Bugfix on 0.2.0.1-alpha.
7953 - Make sure that the "NULL-means-reject *:*" convention is followed by
7954 all the policy manipulation functions, avoiding some possible crash
7955 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
7956 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
7957 actually works, and doesn't warn about every single reverse lookup.
7958 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
7961 - Only log guard node status when guard node status has changed.
7962 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
7963 make "INFO" 75% less verbose.
7966 Changes in version 0.2.0.21-rc - 2008-03-02
7967 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
7968 makes Tor work well with Vidalia again, fixes a rare assert bug,
7969 and fixes a pair of more minor bugs. The bundles also include Vidalia
7970 0.1.0 and Torbutton 1.1.16.
7973 - The control port should declare that it requires password auth
7974 when HashedControlSessionPassword is set too. Patch from Matt Edman;
7975 bugfix on 0.2.0.20-rc. Fixes bug 615.
7976 - Downgrade assert in connection_buckets_decrement() to a log message.
7977 This may help us solve bug 614, and in any case will make its
7978 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
7979 - We were sometimes miscounting the number of bytes read from the
7980 network, causing our rate limiting to not be followed exactly.
7981 Bugfix on 0.2.0.16-alpha. Reported by lodger.
7984 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
7985 OpenSSL versions should have been working fine. Diagnosis and patch
7986 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
7987 Bugfix on 0.2.0.20-rc.
7990 Changes in version 0.2.0.20-rc - 2008-02-24
7991 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
7992 makes more progress towards normalizing Tor's TLS handshake, makes
7993 hidden services work better again, helps relays bootstrap if they don't
7994 know their IP address, adds optional support for linking in openbsd's
7995 allocator or tcmalloc, allows really fast relays to scale past 15000
7996 sockets, and fixes a bunch of minor bugs reported by Veracode.
7999 - Enable the revised TLS handshake based on the one designed by
8000 Steven Murdoch in proposal 124, as revised in proposal 130. It
8001 includes version negotiation for OR connections as described in
8002 proposal 105. The new handshake is meant to be harder for censors
8003 to fingerprint, and it adds the ability to detect certain kinds of
8004 man-in-the-middle traffic analysis attacks. The version negotiation
8005 feature will allow us to improve Tor's link protocol more safely
8007 - Choose which bridge to use proportional to its advertised bandwidth,
8008 rather than uniformly at random. This should speed up Tor for
8009 bridge users. Also do this for people who set StrictEntryNodes.
8010 - When a TrackHostExits-chosen exit fails too many times in a row,
8011 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
8014 - Resolved problems with (re-)fetching hidden service descriptors.
8015 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
8017 - If we only ever used Tor for hidden service lookups or posts, we
8018 would stop building circuits and start refusing connections after
8019 24 hours, since we falsely believed that Tor was dormant. Reported
8020 by nwf; bugfix on 0.1.2.x.
8021 - Servers that don't know their own IP address should go to the
8022 authorities for their first directory fetch, even if their DirPort
8023 is off or if they don't know they're reachable yet. This will help
8024 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
8025 - When counting the number of open sockets, count not only the number
8026 of sockets we have received from the socket() call, but also
8027 the number we've gotten from accept() and socketpair(). This bug
8028 made us fail to count all sockets that we were using for incoming
8029 connections. Bugfix on 0.2.0.x.
8030 - Fix code used to find strings within buffers, when those strings
8031 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
8032 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
8033 - Add a new __HashedControlSessionPassword option for controllers
8034 to use for one-off session password hashes that shouldn't get
8035 saved to disk by SAVECONF --- Vidalia users were accumulating a
8036 pile of HashedControlPassword lines in their torrc files, one for
8037 each time they had restarted Tor and then clicked Save. Make Tor
8038 automatically convert "HashedControlPassword" to this new option but
8039 only when it's given on the command line. Partial fix for bug 586.
8041 o Minor features (performance):
8042 - Tune parameters for cell pool allocation to minimize amount of
8044 - Add OpenBSD malloc code from phk as an optional malloc
8045 replacement on Linux: some glibc libraries do very poorly
8046 with Tor's memory allocation patterns. Pass
8047 --enable-openbsd-malloc to get the replacement malloc code.
8048 - Add a --with-tcmalloc option to the configure script to link
8049 against tcmalloc (if present). Does not yet search for
8050 non-system include paths.
8051 - Stop imposing an arbitrary maximum on the number of file descriptors
8052 used for busy servers. Bug reported by Olaf Selke; patch from
8055 o Minor features (other):
8056 - When SafeLogging is disabled, log addresses along with all TLS
8058 - When building with --enable-gcc-warnings, check for whether Apple's
8059 warning "-Wshorten-64-to-32" is available.
8060 - Add a --passphrase-fd argument to the tor-gencert command for
8063 o Minor bugfixes (memory leaks and code problems):
8064 - We were leaking a file descriptor if Tor started with a zero-length
8065 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
8066 - Detect size overflow in zlib code. Reported by Justin Ferguson and
8068 - We were comparing the raw BridgePassword entry with a base64'ed
8069 version of it, when handling a "/tor/networkstatus-bridges"
8070 directory request. Now compare correctly. Noticed by Veracode.
8071 - Recover from bad tracked-since value in MTBF-history file.
8073 - Alter the code that tries to recover from unhandled write
8074 errors, to not try to flush onto a socket that's given us
8075 unhandled errors. Bugfix on 0.1.2.x.
8076 - Make Unix controlsockets work correctly on OpenBSD. Patch from
8077 tup. Bugfix on 0.2.0.3-alpha.
8079 o Minor bugfixes (other):
8080 - If we have an extra-info document for our server, always make
8081 it available on the control port, even if we haven't gotten
8082 a copy of it from an authority yet. Patch from mwenge.
8083 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
8084 - Directory mirrors no longer include a guess at the client's IP
8085 address if the connection appears to be coming from the same /24
8086 network; it was producing too many wrong guesses.
8087 - Make the new hidden service code respect the SafeLogging setting.
8088 Bugfix on 0.2.0.x. Patch from Karsten.
8089 - When starting as an authority, do not overwrite all certificates
8090 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
8091 - If we're trying to flush the last bytes on a connection (for
8092 example, when answering a directory request), reset the
8093 time-to-give-up timeout every time we manage to write something
8094 on the socket. Bugfix on 0.1.2.x.
8095 - Change the behavior of "getinfo status/good-server-descriptor"
8096 so it doesn't return failure when any authority disappears.
8097 - Even though the man page said that "TrackHostExits ." should
8098 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
8099 - Report TLS "zero return" case as a "clean close" and "IO error"
8100 as a "close". Stop calling closes "unexpected closes": existing
8101 Tors don't use SSL_close(), so having a connection close without
8102 the TLS shutdown handshake is hardly unexpected.
8103 - Send NAMESERVER_STATUS messages for a single failed nameserver
8106 o Code simplifications and refactoring:
8107 - Remove the tor_strpartition function: its logic was confused,
8108 and it was only used for one thing that could be implemented far
8112 Changes in version 0.2.0.19-alpha - 2008-02-09
8113 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
8114 handshake, makes path selection for relays more secure and IP address
8115 guessing more robust, and generally fixes a lot of bugs in preparation
8116 for calling the 0.2.0 branch stable.
8119 - Do not include recognizeable strings in the commonname part of
8120 Tor's x509 certificates.
8123 - If we're a relay, avoid picking ourselves as an introduction point,
8124 a rendezvous point, or as the final hop for internal circuits. Bug
8125 reported by taranis and lodger. Bugfix on 0.1.2.x.
8126 - Patch from "Andrew S. Lists" to catch when we contact a directory
8127 mirror at IP address X and he says we look like we're coming from
8128 IP address X. Bugfix on 0.1.2.x.
8130 o Minor features (security):
8131 - Be more paranoid about overwriting sensitive memory on free(),
8132 as a defensive programming tactic to ensure forward secrecy.
8134 o Minor features (directory authority):
8135 - Actually validate the options passed to AuthDirReject,
8136 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
8137 - Reject router descriptors with out-of-range bandwidthcapacity or
8138 bandwidthburst values.
8140 o Minor features (controller):
8141 - Reject controller commands over 1MB in length. This keeps rogue
8142 processes from running us out of memory.
8144 o Minor features (misc):
8145 - Give more descriptive well-formedness errors for out-of-range
8146 hidden service descriptor/protocol versions.
8147 - Make memory debugging information describe more about history
8148 of cell allocation, so we can help reduce our memory use.
8150 o Deprecated features (controller):
8151 - The status/version/num-versioning and status/version/num-concurring
8152 GETINFO options are no longer useful in the v3 directory protocol:
8153 treat them as deprecated, and warn when they're used.
8156 - When our consensus networkstatus has been expired for a while, stop
8157 being willing to build circuits using it. Fixes bug 401. Bugfix
8159 - Directory caches now fetch certificates from all authorities
8160 listed in a networkstatus consensus, even when they do not
8161 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
8162 - When connecting to a bridge without specifying its key, insert
8163 the connection into the identity-to-connection map as soon as
8164 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
8165 - Detect versions of OS X where malloc_good_size() is present in the
8166 library but never actually declared. Resolves bug 587. Bugfix
8168 - Stop incorrectly truncating zlib responses to directory authority
8169 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
8170 - Stop recommending that every server operator send mail to tor-ops.
8171 Resolves bug 597. Bugfix on 0.1.2.x.
8172 - Don't trigger an assert if we start a directory authority with a
8173 private IP address (like 127.0.0.1).
8174 - Avoid possible failures when generating a directory with routers
8175 with over-long versions strings, or too many flags set. Bugfix
8177 - If an attempt to launch a DNS resolve request over the control
8178 port fails because we have overrun the limit on the number of
8179 connections, tell the controller that the request has failed.
8180 - Avoid using too little bandwidth when our clock skips a few
8181 seconds. Bugfix on 0.1.2.x.
8182 - Fix shell error when warning about missing packages in configure
8183 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
8184 - Do not become confused when receiving a spurious VERSIONS-like
8185 cell from a confused v1 client. Bugfix on 0.2.0.x.
8186 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
8187 introduction points for a hidden service have failed. Patch from
8188 Karsten Loesing. Bugfix on 0.2.0.x.
8190 o Code simplifications and refactoring:
8191 - Remove some needless generality from cpuworker code, for improved
8193 - Stop overloading the circuit_t.onionskin field for both "onionskin
8194 from a CREATE cell that we are waiting for a cpuworker to be
8195 assigned" and "onionskin from an EXTEND cell that we are going to
8196 send to an OR as soon as we are connected". Might help with bug 600.
8197 - Add an in-place version of aes_crypt() so that we can avoid doing a
8198 needless memcpy() call on each cell payload.
8201 Changes in version 0.2.0.18-alpha - 2008-01-25
8202 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
8203 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
8204 that can warn or reject connections to ports generally associated with
8205 vulnerable-plaintext protocols.
8207 o New directory authorities:
8208 - Set up dannenberg (run by CCC) as the sixth v3 directory
8212 - Fix a major memory leak when attempting to use the v2 TLS
8213 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
8214 - We accidentally enabled the under-development v2 TLS handshake
8215 code, which was causing log entries like "TLS error while
8216 renegotiating handshake". Disable it again. Resolves bug 590.
8217 - We were computing the wrong Content-Length: header for directory
8218 responses that need to be compressed on the fly, causing clients
8219 asking for those items to always fail. Bugfix on 0.2.0.x; partially
8223 - Avoid going directly to the directory authorities even if you're a
8224 relay, if you haven't found yourself reachable yet or if you've
8225 decided not to advertise your dirport yet. Addresses bug 556.
8226 - If we've gone 12 hours since our last bandwidth check, and we
8227 estimate we have less than 50KB bandwidth capacity but we could
8228 handle more, do another bandwidth test.
8229 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
8230 Tor can warn and/or refuse connections to ports commonly used with
8231 vulnerable-plaintext protocols. Currently we warn on ports 23,
8232 109, 110, and 143, but we don't reject any.
8235 - When we setconf ClientOnly to 1, close any current OR and Dir
8236 listeners. Reported by mwenge.
8237 - When we get a consensus that's been signed by more people than
8238 we expect, don't log about it; it's not a big deal. Reported
8242 - Don't answer "/tor/networkstatus-bridges" directory requests if
8243 the request isn't encrypted.
8244 - Make "ClientOnly 1" config option disable directory ports too.
8245 - Patches from Karsten Loesing to make v2 hidden services more
8246 robust: work even when there aren't enough HSDir relays available;
8247 retry when a v2 rend desc fetch fails; but don't retry if we
8248 already have a usable v0 rend desc.
8251 Changes in version 0.2.0.17-alpha - 2008-01-17
8252 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
8255 - Make the tor-gencert man page get included correctly in the tarball.
8258 Changes in version 0.2.0.16-alpha - 2008-01-17
8259 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
8260 Loesing, and generally cleans up a lot of features and minor bugs.
8262 o New directory authorities:
8263 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
8266 o Major performance improvements:
8267 - Switch our old ring buffer implementation for one more like that
8268 used by free Unix kernels. The wasted space in a buffer with 1mb
8269 of data will now be more like 8k than 1mb. The new implementation
8270 also avoids realloc();realloc(); patterns that can contribute to
8271 memory fragmentation.
8274 - Configuration files now accept C-style strings as values. This
8275 helps encode characters not allowed in the current configuration
8276 file format, such as newline or #. Addresses bug 557.
8277 - Although we fixed bug 539 (where servers would send HTTP status 503
8278 responses _and_ send a body too), there are still servers out
8279 there that haven't upgraded. Therefore, make clients parse such
8280 bodies when they receive them.
8281 - When we're not serving v2 directory information, there is no reason
8282 to actually keep any around. Remove the obsolete files and directory
8283 on startup if they are very old and we aren't going to serve them.
8285 o Minor performance improvements:
8286 - Reference-count and share copies of address policy entries; only 5%
8287 of them were actually distinct.
8288 - Never walk through the list of logs if we know that no log is
8289 interested in a given message.
8292 - When an authority has not signed a consensus, do not try to
8293 download a nonexistent "certificate with key 00000000". Bugfix
8294 on 0.2.0.x. Fixes bug 569.
8295 - Fix a rare assert error when we're closing one of our threads:
8296 use a mutex to protect the list of logs, so we never write to the
8297 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
8298 bug 575, which is kind of the revenge of bug 222.
8299 - Patch from Karsten Loesing to complain less at both the client
8300 and the relay when a relay used to have the HSDir flag but doesn't
8301 anymore, and we try to upload a hidden service descriptor.
8302 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
8304 - Do not try to download missing certificates until we have tried
8305 to check our fallback consensus. Fixes bug 583.
8306 - Make bridges round reported GeoIP stats info up to the nearest
8307 estimate, not down. Now we can distinguish between "0 people from
8308 this country" and "1 person from this country".
8309 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
8310 - Avoid possible segfault if key generation fails in
8311 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
8312 - Avoid segfault in the case where a badly behaved v2 versioning
8313 directory sends a signed networkstatus with missing client-versions.
8315 - Avoid segfaults on certain complex invocations of
8316 router_get_by_hexdigest(). Bugfix on 0.1.2.
8317 - Correct bad index on array access in parse_http_time(). Bugfix
8319 - Fix possible bug in vote generation when server versions are present
8320 but client versions are not.
8321 - Fix rare bug on REDIRECTSTREAM control command when called with no
8322 port set: it could erroneously report an error when none had
8324 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
8325 compressing large objects and find ourselves with more than 4k
8326 left over. Bugfix on 0.2.0.
8327 - Fix a small memory leak when setting up a hidden service.
8328 - Fix a few memory leaks that could in theory happen under bizarre
8330 - Fix an assert if we post a general-purpose descriptor via the
8331 control port but that descriptor isn't mentioned in our current
8332 network consensus. Bug reported by Jon McLachlan; bugfix on
8335 o Minor features (controller):
8336 - Get NS events working again. Patch from tup.
8337 - The GETCONF command now escapes and quotes configuration values
8338 that don't otherwise fit into the torrc file.
8339 - The SETCONF command now handles quoted values correctly.
8341 o Minor features (directory authorities):
8342 - New configuration options to override default maximum number of
8343 servers allowed on a single IP address. This is important for
8344 running a test network on a single host.
8345 - Actually implement the -s option to tor-gencert.
8346 - Add a manual page for tor-gencert.
8348 o Minor features (bridges):
8349 - Bridge authorities no longer serve bridge descriptors over
8350 unencrypted connections.
8352 o Minor features (other):
8353 - Add hidden services and DNSPorts to the list of things that make
8354 Tor accept that it has running ports. Change starting Tor with no
8355 ports from a fatal error to a warning; we might change it back if
8356 this turns out to confuse anybody. Fixes bug 579.
8359 Changes in version 0.1.2.19 - 2008-01-17
8360 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
8361 exit policy a little bit more conservative so it's safer to run an
8362 exit relay on a home system, and fixes a variety of smaller issues.
8365 - Exit policies now reject connections that are addressed to a
8366 relay's public (external) IP address too, unless
8367 ExitPolicyRejectPrivate is turned off. We do this because too
8368 many relays are running nearby to services that trust them based
8372 - When the clock jumps forward a lot, do not allow the bandwidth
8373 buckets to become negative. Fixes bug 544.
8374 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
8375 on every successful resolve. Reported by Mike Perry.
8376 - Purge old entries from the "rephist" database and the hidden
8377 service descriptor database even when DirPort is zero.
8378 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
8379 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
8380 crashing or mis-answering these requests.
8381 - When we decide to send a 503 response to a request for servers, do
8382 not then also send the server descriptors: this defeats the whole
8383 purpose. Fixes bug 539.
8386 - Changing the ExitPolicyRejectPrivate setting should cause us to
8387 rebuild our server descriptor.
8388 - Fix handling of hex nicknames when answering controller requests for
8389 networkstatus by name, or when deciding whether to warn about
8390 unknown routers in a config option. (Patch from mwenge.)
8391 - Fix a couple of hard-to-trigger autoconf problems that could result
8392 in really weird results on platforms whose sys/types.h files define
8393 nonstandard integer types.
8394 - Don't try to create the datadir when running --verify-config or
8395 --hash-password. Resolves bug 540.
8396 - If we were having problems getting a particular descriptor from the
8397 directory caches, and then we learned about a new descriptor for
8398 that router, we weren't resetting our failure count. Reported
8400 - Although we fixed bug 539 (where servers would send HTTP status 503
8401 responses _and_ send a body too), there are still servers out there
8402 that haven't upgraded. Therefore, make clients parse such bodies
8403 when they receive them.
8404 - Run correctly on systems where rlim_t is larger than unsigned long.
8405 This includes some 64-bit systems.
8406 - Run correctly on platforms (like some versions of OS X 10.5) where
8407 the real limit for number of open files is OPEN_FILES, not rlim_max
8408 from getrlimit(RLIMIT_NOFILES).
8409 - Avoid a spurious free on base64 failure.
8410 - Avoid segfaults on certain complex invocations of
8411 router_get_by_hexdigest().
8412 - Fix rare bug on REDIRECTSTREAM control command when called with no
8413 port set: it could erroneously report an error when none had
8417 Changes in version 0.2.0.15-alpha - 2007-12-25
8418 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
8419 features added in 0.2.0.13-alpha.
8422 - Fix several remotely triggerable asserts based on DirPort requests
8423 for a v2 or v3 networkstatus object before we were prepared. This
8424 was particularly bad for 0.2.0.13 and later bridge relays, who
8425 would never have a v2 networkstatus and would thus always crash
8426 when used. Bugfixes on 0.2.0.x.
8427 - Estimate the v3 networkstatus size more accurately, rather than
8428 estimating it at zero bytes and giving it artificially high priority
8429 compared to other directory requests. Bugfix on 0.2.0.x.
8432 - Fix configure.in logic for cross-compilation.
8433 - When we load a bridge descriptor from the cache, and it was
8434 previously unreachable, mark it as retriable so we won't just
8435 ignore it. Also, try fetching a new copy immediately. Bugfixes
8437 - The bridge GeoIP stats were counting other relays, for example
8438 self-reachability and authority-reachability tests.
8441 - Support compilation to target iPhone; patch from cjacker huang.
8442 To build for iPhone, pass the --enable-iphone option to configure.
8445 Changes in version 0.2.0.14-alpha - 2007-12-23
8447 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
8448 without a datadirectory from a previous Tor install. Reported
8450 - Fix a crash when we fetch a descriptor that turns out to be
8451 unexpected (it used to be in our networkstatus when we started
8452 fetching it, but it isn't in our current networkstatus), and we
8453 aren't using bridges. Bugfix on 0.2.0.x.
8454 - Fix a crash when accessing hidden services: it would work the first
8455 time you use a given introduction point for your service, but
8456 on subsequent requests we'd be using garbage memory. Fixed by
8457 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
8458 - Fix a crash when we load a bridge descriptor from disk but we don't
8459 currently have a Bridge line for it in our torrc. Bugfix on
8463 - If bridge authorities set BridgePassword, they will serve a
8464 snapshot of known bridge routerstatuses from their DirPort to
8465 anybody who knows that password. Unset by default.
8468 - Make the unit tests build again.
8469 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
8470 - Make PublishServerDescriptor default to 1, so the default doesn't
8471 have to change as we invent new directory protocol versions.
8472 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
8473 be included unless sys/time.h is already included. Fixes
8474 bug 553. Bugfix on 0.2.0.x.
8475 - If we receive a general-purpose descriptor and then receive an
8476 identical bridge-purpose descriptor soon after, don't discard
8477 the next one as a duplicate.
8480 - If BridgeRelay is set to 1, then the default for
8481 PublishServerDescriptor is now "bridge" rather than "v2,v3".
8482 - If the user sets RelayBandwidthRate but doesn't set
8483 RelayBandwidthBurst, then make them equal rather than erroring out.
8486 Changes in version 0.2.0.13-alpha - 2007-12-21
8487 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
8488 Goodell, fixes many more bugs, and adds a lot of infrastructure for
8491 o New directory authorities:
8492 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
8496 - Only update guard status (usable / not usable) once we have
8497 enough directory information. This was causing us to always pick
8498 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
8499 causing us to discard all our guards on startup if we hadn't been
8500 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
8501 - Purge old entries from the "rephist" database and the hidden
8502 service descriptor databases even when DirPort is zero. Bugfix
8504 - We were ignoring our RelayBandwidthRate for the first 30 seconds
8505 after opening a circuit -- even a relayed circuit. Bugfix on
8507 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
8508 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
8509 crashing or mis-answering these types of requests.
8510 - Relays were publishing their server descriptor to v1 and v2
8511 directory authorities, but they didn't try publishing to v3-only
8512 authorities. Fix this; and also stop publishing to v1 authorities.
8514 - When we were reading router descriptors from cache, we were ignoring
8515 the annotations -- so for example we were reading in bridge-purpose
8516 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
8517 - When we decided to send a 503 response to a request for servers, we
8518 were then also sending the server descriptors: this defeats the
8519 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
8522 - Bridge relays now behave like clients with respect to time
8523 intervals for downloading new consensus documents -- otherwise they
8524 stand out. Bridge users now wait until the end of the interval,
8525 so their bridge relay will be sure to have a new consensus document.
8526 - Three new config options (AlternateDirAuthority,
8527 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
8528 user selectively replace the default directory authorities by type,
8529 rather than the all-or-nothing replacement that DirServer offers.
8530 - Tor can now be configured to read a GeoIP file from disk in one
8531 of two formats. This can be used by controllers to map IP addresses
8532 to countries. Eventually, it may support exit-by-country.
8533 - When possible, bridge relays remember which countries users
8534 are coming from, and report aggregate information in their
8535 extra-info documents, so that the bridge authorities can learn
8536 where Tor is blocked.
8537 - Bridge directory authorities now do reachability testing on the
8538 bridges they know. They provide router status summaries to the
8539 controller via "getinfo ns/purpose/bridge", and also dump summaries
8540 to a file periodically.
8541 - Stop fetching directory info so aggressively if your DirPort is
8542 on but your ORPort is off; stop fetching v2 dir info entirely.
8543 You can override these choices with the new FetchDirInfoEarly
8547 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
8548 consensus documents when there are too many relays at a single
8549 IP address. Now clear it in v2 network status documents too, and
8550 also clear it in routerinfo_t when the relay is no longer listed
8551 in the relevant networkstatus document.
8552 - Don't crash if we get an unexpected value for the
8553 PublishServerDescriptor config option. Reported by Matt Edman;
8554 bugfix on 0.2.0.9-alpha.
8555 - Our new v2 hidden service descriptor format allows descriptors
8556 that have no introduction points. But Tor crashed when we tried
8557 to build a descriptor with no intro points (and it would have
8558 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
8560 - Fix building with dmalloc 5.5.2 with glibc.
8561 - Reject uploaded descriptors and extrainfo documents if they're
8562 huge. Otherwise we'll cache them all over the network and it'll
8563 clog everything up. Reported by Aljosha Judmayer.
8564 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
8565 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
8566 - When the DANGEROUS_VERSION controller status event told us we're
8567 running an obsolete version, it used the string "OLD" to describe
8568 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
8569 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
8570 - If we can't expand our list of entry guards (e.g. because we're
8571 using bridges or we have StrictEntryNodes set), don't mark relays
8572 down when they fail a directory request. Otherwise we're too quick
8573 to mark all our entry points down. Bugfix on 0.1.2.x.
8574 - Fix handling of hex nicknames when answering controller requests for
8575 networkstatus by name, or when deciding whether to warn about unknown
8576 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
8577 - Fix a couple of hard-to-trigger autoconf problems that could result
8578 in really weird results on platforms whose sys/types.h files define
8579 nonstandard integer types. Bugfix on 0.1.2.x.
8580 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
8581 - Don't crash on name lookup when we have no current consensus. Fixes
8582 bug 538; bugfix on 0.2.0.x.
8583 - Only Tors that want to mirror the v2 directory info should
8584 create the "cached-status" directory in their datadir. (All Tors
8585 used to create it.) Bugfix on 0.2.0.9-alpha.
8586 - Directory authorities should only automatically download Extra Info
8587 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
8590 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
8591 consumers. (We already do this on HUP.)
8592 - Authorities and caches fetch the v2 networkstatus documents
8593 less often, now that v3 is encouraged.
8594 - Add a new config option BridgeRelay that specifies you want to
8595 be a bridge relay. Right now the only difference is that it makes
8596 you answer begin_dir requests, and it makes you cache dir info,
8597 even if your DirPort isn't on.
8598 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
8599 ask about source, timestamp of arrival, purpose, etc. We need
8600 something like this to help Vidalia not do GeoIP lookups on bridge
8602 - Allow multiple HashedControlPassword config lines, to support
8603 multiple controller passwords.
8604 - Authorities now decide whether they're authoritative for a given
8605 router based on the router's purpose.
8606 - New config options AuthDirBadDir and AuthDirListBadDirs for
8607 authorities to mark certain relays as "bad directories" in the
8608 networkstatus documents. Also supports the "!baddir" directive in
8609 the approved-routers file.
8612 Changes in version 0.2.0.12-alpha - 2007-11-16
8613 This twelfth development snapshot fixes some more build problems as
8614 well as a few minor bugs.
8617 - Make it build on OpenBSD again. Patch from tup.
8618 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
8619 package-building for Red Hat, OS X, etc.
8621 o Minor bugfixes (on 0.1.2.x):
8622 - Changing the ExitPolicyRejectPrivate setting should cause us to
8623 rebuild our server descriptor.
8625 o Minor bugfixes (on 0.2.0.x):
8626 - When we're lacking a consensus, don't try to perform rendezvous
8627 operations. Reported by Karsten Loesing.
8628 - Fix a small memory leak whenever we decide against using a
8629 newly picked entry guard. Reported by Mike Perry.
8630 - When authorities detected more than two relays running on the same
8631 IP address, they were clearing all the status flags but forgetting
8632 to clear the "hsdir" flag. So clients were being told that a
8633 given relay was the right choice for a v2 hsdir lookup, yet they
8634 never had its descriptor because it was marked as 'not running'
8636 - If we're trying to fetch a bridge descriptor and there's no way
8637 the bridge authority could help us (for example, we don't know
8638 a digest, or there is no bridge authority), don't be so eager to
8639 fall back to asking the bridge authority.
8640 - If we're using bridges or have strictentrynodes set, and our
8641 chosen exit is in the same family as all our bridges/entry guards,
8642 then be flexible about families.
8645 - When we negotiate a v2 link-layer connection (not yet implemented),
8646 accept RELAY_EARLY cells and turn them into RELAY cells if we've
8647 negotiated a v1 connection for their next step. Initial code for
8651 Changes in version 0.2.0.11-alpha - 2007-11-12
8652 This eleventh development snapshot fixes some build problems with
8653 the previous snapshot. It also includes a more secure-by-default exit
8654 policy for relays, fixes an enormous memory leak for exit relays, and
8655 fixes another bug where servers were falling out of the directory list.
8658 - Exit policies now reject connections that are addressed to a
8659 relay's public (external) IP address too, unless
8660 ExitPolicyRejectPrivate is turned off. We do this because too
8661 many relays are running nearby to services that trust them based
8662 on network address. Bugfix on 0.1.2.x.
8665 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
8666 on every successful resolve. Reported by Mike Perry; bugfix
8668 - On authorities, never downgrade to old router descriptors simply
8669 because they're listed in the consensus. This created a catch-22
8670 where we wouldn't list a new descriptor because there was an
8671 old one in the consensus, and we couldn't get the new one in the
8672 consensus because we wouldn't list it. Possible fix for bug 548.
8673 Also, this might cause bug 543 to appear on authorities; if so,
8674 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
8676 o Packaging fixes on 0.2.0.10-alpha:
8677 - We were including instructions about what to do with the
8678 src/config/fallback-consensus file, but we weren't actually
8679 including it in the tarball. Disable all of that for now.
8682 - Allow people to say PreferTunnelledDirConns rather than
8683 PreferTunneledDirConns, for those alternate-spellers out there.
8686 - Don't reevaluate all the information from our consensus document
8687 just because we've downloaded a v2 networkstatus that we intend
8688 to cache. Fixes bug 545; bugfix on 0.2.0.x.
8691 Changes in version 0.2.0.10-alpha - 2007-11-10
8692 This tenth development snapshot adds a third v3 directory authority
8693 run by Mike Perry, adds most of Karsten Loesing's new hidden service
8694 descriptor format, fixes a bad crash bug and new bridge bugs introduced
8695 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
8696 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
8697 addresses many more minor issues.
8699 o New directory authorities:
8700 - Set up ides (run by Mike Perry) as the third v3 directory authority.
8703 - Allow tunnelled directory connections to ask for an encrypted
8704 "begin_dir" connection or an anonymized "uses a full Tor circuit"
8705 connection independently. Now we can make anonymized begin_dir
8706 connections for (e.g.) more secure hidden service posting and
8708 - More progress on proposal 114: code from Karsten Loesing to
8709 implement new hidden service descriptor format.
8710 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
8711 accommodate the growing number of servers that use the default
8712 and are reaching it.
8713 - Directory authorities use a new formula for selecting which nodes
8714 to advertise as Guards: they must be in the top 7/8 in terms of
8715 how long we have known about them, and above the median of those
8716 nodes in terms of weighted fractional uptime.
8717 - Make "not enough dir info yet" warnings describe *why* Tor feels
8718 it doesn't have enough directory info yet.
8721 - Stop servers from crashing if they set a Family option (or
8722 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
8724 - Make bridge users work again -- the move to v3 directories in
8725 0.2.0.9-alpha had introduced a number of bugs that made bridges
8726 no longer work for clients.
8727 - When the clock jumps forward a lot, do not allow the bandwidth
8728 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
8730 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
8731 - When the consensus lists a router descriptor that we previously were
8732 mirroring, but that we considered non-canonical, reload the
8733 descriptor as canonical. This fixes bug 543 where Tor servers
8734 would start complaining after a few days that they don't have
8735 enough directory information to build a circuit.
8736 - Consider replacing the current consensus when certificates arrive
8737 that make the pending consensus valid. Previously, we were only
8738 considering replacement when the new certs _didn't_ help.
8739 - Fix an assert error on startup if we didn't already have the
8740 consensus and certs cached in our datadirectory: we were caching
8741 the consensus in consensus_waiting_for_certs but then free'ing it
8743 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
8744 Request) if we need more v3 certs but we've already got pending
8745 requests for all of them.
8746 - Correctly back off from failing certificate downloads. Fixes
8748 - Authorities don't vote on the Running flag if they have been running
8749 for less than 30 minutes themselves. Fixes bug 547, where a newly
8750 started authority would vote that everyone was down.
8753 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
8754 it, it had no AES, and it hasn't seen any security patches since
8758 - Clients now hold circuitless TLS connections open for 1.5 times
8759 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
8760 rebuild a new circuit over them within that timeframe. Previously,
8761 they held them open only for KeepalivePeriod (5 minutes).
8762 - Use "If-Modified-Since" to avoid retrieving consensus
8763 networkstatuses that we already have.
8764 - When we have no consensus, check FallbackNetworkstatusFile (defaults
8765 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
8766 we start knowing some directory caches.
8767 - When we receive a consensus from the future, warn about skew.
8768 - Improve skew reporting: try to give the user a better log message
8769 about how skewed they are, and how much this matters.
8770 - When we have a certificate for an authority, believe that
8771 certificate's claims about the authority's IP address.
8772 - New --quiet command-line option to suppress the default console log.
8773 Good in combination with --hash-password.
8774 - Authorities send back an X-Descriptor-Not-New header in response to
8775 an accepted-but-discarded descriptor upload. Partially implements
8777 - Make the log message for "tls error. breaking." more useful.
8778 - Better log messages about certificate downloads, to attempt to
8779 track down the second incarnation of bug 546.
8781 o Minor features (bridges):
8782 - If bridge users set UpdateBridgesFromAuthority, but the digest
8783 they ask for is a 404 from the bridge authority, they now fall
8784 back to trying the bridge directly.
8785 - Bridges now use begin_dir to publish their server descriptor to
8786 the bridge authority, even when they haven't set TunnelDirConns.
8788 o Minor features (controller):
8789 - When reporting clock skew, and we know that the clock is _at least
8790 as skewed_ as some value, but we don't know the actual value,
8791 report the value as a "minimum skew."
8794 - Update linux-tor-prio.sh script to allow QoS based on the uid of
8795 the Tor process. Patch from Marco Bonetti with tweaks from Mike
8799 - Refuse to start if both ORPort and UseBridges are set. Bugfix
8800 on 0.2.0.x, suggested by Matt Edman.
8801 - Don't stop fetching descriptors when FetchUselessDescriptors is
8802 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
8803 reported by tup and ioerror.
8804 - Better log message on vote from unknown authority.
8805 - Don't log "Launching 0 request for 0 router" message.
8807 o Minor bugfixes (memory leaks):
8808 - Stop leaking memory every time we parse a v3 certificate. Bugfix
8810 - Stop leaking memory every time we load a v3 certificate. Bugfix
8811 on 0.2.0.1-alpha. Fixes bug 536.
8812 - Stop leaking a cached networkstatus on exit. Bugfix on
8814 - Stop leaking voter information every time we free a consensus.
8815 Bugfix on 0.2.0.3-alpha.
8816 - Stop leaking signed data every time we check a voter signature.
8817 Bugfix on 0.2.0.3-alpha.
8818 - Stop leaking a signature every time we fail to parse a consensus or
8819 a vote. Bugfix on 0.2.0.3-alpha.
8820 - Stop leaking v2_download_status_map on shutdown. Bugfix on
8822 - Stop leaking conn->nickname every time we make a connection to a
8823 Tor relay without knowing its expected identity digest (e.g. when
8824 using bridges). Bugfix on 0.2.0.3-alpha.
8826 - Minor bugfixes (portability):
8827 - Run correctly on platforms where rlim_t is larger than unsigned
8828 long, and/or where the real limit for number of open files is
8829 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
8830 particular, these may be needed for OS X 10.5.
8833 Changes in version 0.1.2.18 - 2007-10-28
8834 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
8835 hidden service introduction that were causing huge delays, and a big
8836 bug that was causing some servers to disappear from the network status
8837 lists for a few hours each day.
8839 o Major bugfixes (crashes):
8840 - If a connection is shut down abruptly because of something that
8841 happened inside connection_flushed_some(), do not call
8842 connection_finished_flushing(). Should fix bug 451:
8843 "connection_stop_writing: Assertion conn->write_event failed"
8844 Bugfix on 0.1.2.7-alpha.
8845 - Fix possible segfaults in functions called from
8846 rend_process_relay_cell().
8848 o Major bugfixes (hidden services):
8849 - Hidden services were choosing introduction points uniquely by
8850 hexdigest, but when constructing the hidden service descriptor
8851 they merely wrote the (potentially ambiguous) nickname.
8852 - Clients now use the v2 intro format for hidden service
8853 connections: they specify their chosen rendezvous point by identity
8854 digest rather than by (potentially ambiguous) nickname. These
8855 changes could speed up hidden service connections dramatically.
8857 o Major bugfixes (other):
8858 - Stop publishing a new server descriptor just because we get a
8859 HUP signal. This led (in a roundabout way) to some servers getting
8860 dropped from the networkstatus lists for a few hours each day.
8861 - When looking for a circuit to cannibalize, consider family as well
8862 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
8863 circuit cannibalization).
8864 - When a router wasn't listed in a new networkstatus, we were leaving
8865 the flags for that router alone -- meaning it remained Named,
8866 Running, etc -- even though absence from the networkstatus means
8867 that it shouldn't be considered to exist at all anymore. Now we
8868 clear all the flags for routers that fall out of the networkstatus
8869 consensus. Fixes bug 529.
8872 - Don't try to access (or alter) the state file when running
8873 --list-fingerprint or --verify-config or --hash-password. Resolves
8875 - When generating information telling us how to extend to a given
8876 router, do not try to include the nickname if it is
8877 absent. Resolves bug 467.
8878 - Fix a user-triggerable segfault in expand_filename(). (There isn't
8879 a way to trigger this remotely.)
8880 - When sending a status event to the controller telling it that an
8881 OR address is reachable, set the port correctly. (Previously we
8882 were reporting the dir port.)
8883 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
8884 command. Bugfix on 0.1.2.17.
8885 - When loading bandwidth history, do not believe any information in
8886 the future. Fixes bug 434.
8887 - When loading entry guard information, do not believe any information
8889 - When we have our clock set far in the future and generate an
8890 onion key, then re-set our clock to be correct, we should not stop
8891 the onion key from getting rotated.
8892 - On some platforms, accept() can return a broken address. Detect
8893 this more quietly, and deal accordingly. Fixes bug 483.
8894 - It's not actually an error to find a non-pending entry in the DNS
8895 cache when canceling a pending resolve. Don't log unless stuff
8896 is fishy. Resolves bug 463.
8897 - Don't reset trusted dir server list when we set a configuration
8898 option. Patch from Robert Hogan.
8899 - Don't try to create the datadir when running --verify-config or
8900 --hash-password. Resolves bug 540.
8903 Changes in version 0.2.0.9-alpha - 2007-10-24
8904 This ninth development snapshot switches clients to the new v3 directory
8905 system; allows servers to be listed in the network status even when they
8906 have the same nickname as a registered server; and fixes many other
8907 bugs including a big one that was causing some servers to disappear
8908 from the network status lists for a few hours each day.
8910 o Major features (directory system):
8911 - Clients now download v3 consensus networkstatus documents instead
8912 of v2 networkstatus documents. Clients and caches now base their
8913 opinions about routers on these consensus documents. Clients only
8914 download router descriptors listed in the consensus.
8915 - Authorities now list servers who have the same nickname as
8916 a different named server, but list them with a new flag,
8917 "Unnamed". Now we can list servers that happen to pick the same
8918 nickname as a server that registered two years ago and then
8919 disappeared. Partially implements proposal 122.
8920 - If the consensus lists a router as "Unnamed", the name is assigned
8921 to a different router: do not identify the router by that name.
8922 Partially implements proposal 122.
8923 - Authorities can now come to a consensus on which method to use to
8924 compute the consensus. This gives us forward compatibility.
8927 - Stop publishing a new server descriptor just because we HUP or
8928 when we find our DirPort to be reachable but won't actually publish
8929 it. New descriptors without any real changes are dropped by the
8930 authorities, and can screw up our "publish every 18 hours" schedule.
8932 - When a router wasn't listed in a new networkstatus, we were leaving
8933 the flags for that router alone -- meaning it remained Named,
8934 Running, etc -- even though absence from the networkstatus means
8935 that it shouldn't be considered to exist at all anymore. Now we
8936 clear all the flags for routers that fall out of the networkstatus
8937 consensus. Fixes bug 529; bugfix on 0.1.2.x.
8938 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
8939 extrainfo documents and then discard them immediately for not
8940 matching the latest router. Bugfix on 0.2.0.1-alpha.
8942 o Minor features (v3 directory protocol):
8943 - Allow tor-gencert to generate a new certificate without replacing
8945 - Allow certificates to include an address.
8946 - When we change our directory-cache settings, reschedule all voting
8947 and download operations.
8948 - Reattempt certificate downloads immediately on failure, as long as
8949 we haven't failed a threshold number of times yet.
8950 - Delay retrying consensus downloads while we're downloading
8951 certificates to verify the one we just got. Also, count getting a
8952 consensus that we already have (or one that isn't valid) as a failure,
8953 and count failing to get the certificates after 20 minutes as a
8955 - Build circuits and download descriptors even if our consensus is a
8956 little expired. (This feature will go away once authorities are
8959 o Minor features (router descriptor cache):
8960 - If we find a cached-routers file that's been sitting around for more
8961 than 28 days unmodified, then most likely it's a leftover from
8962 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
8964 - When we (as a cache) download a descriptor because it was listed
8965 in a consensus, remember when the consensus was supposed to expire,
8966 and don't expire the descriptor until then.
8968 o Minor features (performance):
8969 - Call routerlist_remove_old_routers() much less often. This should
8970 speed startup, especially on directory caches.
8971 - Don't try to launch new descriptor downloads quite so often when we
8972 already have enough directory information to build circuits.
8973 - Base64 decoding was actually showing up on our profile when parsing
8974 the initial descriptor file; switch to an in-process all-at-once
8975 implementation that's about 3.5x times faster than calling out to
8978 o Minor features (compilation):
8979 - Detect non-ASCII platforms (if any still exist) and refuse to
8980 build there: some of our code assumes that 'A' is 65 and so on.
8982 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
8983 - Make the "next period" votes into "current period" votes immediately
8984 after publishing the consensus; avoid a heisenbug that made them
8985 stick around indefinitely.
8986 - When we discard a vote as a duplicate, do not report this as
8988 - Treat missing v3 keys or certificates as an error when running as a
8989 v3 directory authority.
8990 - When we're configured to be a v3 authority, but we're only listed
8991 as a non-v3 authority in our DirServer line for ourself, correct
8993 - If an authority doesn't have a qualified hostname, just put
8994 its address in the vote. This fixes the problem where we referred to
8995 "moria on moria:9031."
8996 - Distinguish between detached signatures for the wrong period, and
8997 detached signatures for a divergent vote.
8998 - Fix a small memory leak when computing a consensus.
8999 - When there's no concensus, we were forming a vote every 30
9000 minutes, but writing the "valid-after" line in our vote based
9001 on our configured V3AuthVotingInterval: so unless the intervals
9002 matched up, we immediately rejected our own vote because it didn't
9003 start at the voting interval that caused us to construct a vote.
9005 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
9006 - Delete unverified-consensus when the real consensus is set.
9007 - Consider retrying a consensus networkstatus fetch immediately
9008 after one fails: don't wait 60 seconds to notice.
9009 - When fetching a consensus as a cache, wait until a newer consensus
9010 should exist before trying to replace the current one.
9011 - Use a more forgiving schedule for retrying failed consensus
9012 downloads than for other types.
9014 o Minor bugfixes (other directory issues):
9015 - Correct the implementation of "download votes by digest." Bugfix on
9017 - Authorities no longer send back "400 you're unreachable please fix
9018 it" errors to Tor servers that aren't online all the time. We're
9019 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
9021 o Minor bugfixes (controller):
9022 - Don't reset trusted dir server list when we set a configuration
9023 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
9024 - Respond to INT and TERM SIGNAL commands before we execute the
9025 signal, in case the signal shuts us down. We had a patch in
9026 0.1.2.1-alpha that tried to do this by queueing the response on
9027 the connection's buffer before shutting down, but that really
9028 isn't the same thing at all. Bug located by Matt Edman.
9030 o Minor bugfixes (misc):
9031 - Correctly check for bad options to the "PublishServerDescriptor"
9032 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
9033 - Stop leaking memory on failing case of base32_decode, and make
9034 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
9035 - Don't try to download extrainfo documents when we're trying to
9036 fetch enough directory info to build a circuit: having enough
9037 info should get priority. Bugfix on 0.2.0.x.
9038 - Don't complain that "your server has not managed to confirm that its
9039 ports are reachable" if we haven't been able to build any circuits
9040 yet. Bug found by spending four hours without a v3 consensus. Bugfix
9042 - Detect the reason for failing to mmap a descriptor file we just
9043 wrote, and give a more useful log message. Fixes bug 533. Bugfix
9046 o Code simplifications and refactoring:
9047 - Remove support for the old bw_accounting file: we've been storing
9048 bandwidth accounting information in the state file since
9049 0.1.2.5-alpha. This may result in bandwidth accounting errors
9050 if you try to upgrade from 0.1.1.x or earlier, or if you try to
9051 downgrade to 0.1.1.x or earlier.
9052 - New convenience code to locate a file within the DataDirectory.
9053 - Move non-authority functionality out of dirvote.c.
9054 - Refactor the arguments for router_pick_{directory_|trusteddir}server
9055 so that they all take the same named flags.
9058 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
9059 Unix users an easy way to script their Tor process (e.g. by
9060 adjusting bandwidth based on the time of the day).
9063 Changes in version 0.2.0.8-alpha - 2007-10-12
9064 This eighth development snapshot fixes a crash bug that's been bothering
9065 us since February 2007, lets bridge authorities store a list of bridge
9066 descriptors they've seen, gets v3 directory voting closer to working,
9067 starts caching v3 directory consensus documents on directory mirrors,
9068 and fixes a variety of smaller issues including some minor memory leaks.
9070 o Major features (router descriptor cache):
9071 - Store routers in a file called cached-descriptors instead of in
9072 cached-routers. Initialize cached-descriptors from cached-routers
9073 if the old format is around. The new format allows us to store
9074 annotations along with descriptors.
9075 - Use annotations to record the time we received each descriptor, its
9076 source, and its purpose.
9077 - Disable the SETROUTERPURPOSE controller command: it is now
9079 - Controllers should now specify cache=no or cache=yes when using
9080 the +POSTDESCRIPTOR command.
9081 - Bridge authorities now write bridge descriptors to disk, meaning
9082 we can export them to other programs and begin distributing them
9085 o Major features (directory authorities):
9086 - When a v3 authority is missing votes or signatures, it now tries
9088 - Directory authorities track weighted fractional uptime as well as
9089 weighted mean-time-between failures. WFU is suitable for deciding
9090 whether a node is "usually up", while MTBF is suitable for deciding
9091 whether a node is "likely to stay up." We need both, because
9092 "usually up" is a good requirement for guards, while "likely to
9093 stay up" is a good requirement for long-lived connections.
9095 o Major features (v3 directory system):
9096 - Caches now download v3 network status documents as needed,
9097 and download the descriptors listed in them.
9098 - All hosts now attempt to download and keep fresh v3 authority
9099 certificates, and re-attempt after failures.
9100 - More internal-consistency checks for vote parsing.
9102 o Major bugfixes (crashes):
9103 - If a connection is shut down abruptly because of something that
9104 happened inside connection_flushed_some(), do not call
9105 connection_finished_flushing(). Should fix bug 451. Bugfix on
9108 o Major bugfixes (performance):
9109 - Fix really bad O(n^2) performance when parsing a long list of
9110 routers: Instead of searching the entire list for an "extra-info "
9111 string which usually wasn't there, once for every routerinfo
9112 we read, just scan lines forward until we find one we like.
9114 - When we add data to a write buffer in response to the data on that
9115 write buffer getting low because of a flush, do not consider the
9116 newly added data as a candidate for immediate flushing, but rather
9117 make it wait until the next round of writing. Otherwise, we flush
9118 and refill recursively, and a single greedy TLS connection can
9119 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
9121 o Minor features (v3 authority system):
9122 - Add more ways for tools to download the votes that lead to the
9124 - Send a 503 when low on bandwidth and a vote, consensus, or
9125 certificate is requested.
9126 - If-modified-since is now implemented properly for all kinds of
9127 certificate requests.
9129 o Minor bugfixes (network statuses):
9130 - Tweak the implementation of proposal 109 slightly: allow at most
9131 two Tor servers on the same IP address, except if it's the location
9132 of a directory authority, in which case allow five. Bugfix on
9135 o Minor bugfixes (controller):
9136 - When sending a status event to the controller telling it that an
9137 OR address is reachable, set the port correctly. (Previously we
9138 were reporting the dir port.) Bugfix on 0.1.2.x.
9140 o Minor bugfixes (v3 directory system):
9141 - Fix logic to look up a cert by its signing key digest. Bugfix on
9143 - Only change the reply to a vote to "OK" if it's not already
9144 set. This gets rid of annoying "400 OK" log messages, which may
9145 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
9146 - When we get a valid consensus, recompute the voting schedule.
9147 - Base the valid-after time of a vote on the consensus voting
9148 schedule, not on our preferred schedule.
9149 - Make the return values and messages from signature uploads and
9150 downloads more sensible.
9151 - Fix a memory leak when serving votes and consensus documents, and
9152 another when serving certificates.
9154 o Minor bugfixes (performance):
9155 - Use a slightly simpler string hashing algorithm (copying Python's
9156 instead of Java's) and optimize our digest hashing algorithm to take
9157 advantage of 64-bit platforms and to remove some possibly-costly
9159 - Fix a minor memory leak whenever we parse guards from our state
9160 file. Bugfix on 0.2.0.7-alpha.
9161 - Fix a minor memory leak whenever we write out a file. Bugfix on
9163 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
9164 command. Bugfix on 0.2.0.5-alpha.
9166 o Minor bugfixes (portability):
9167 - On some platforms, accept() can return a broken address. Detect
9168 this more quietly, and deal accordingly. Fixes bug 483.
9169 - Stop calling tor_strlower() on uninitialized memory in some cases.
9170 Bugfix in 0.2.0.7-alpha.
9172 o Minor bugfixes (usability):
9173 - Treat some 403 responses from directory servers as INFO rather than
9174 WARN-severity events.
9175 - It's not actually an error to find a non-pending entry in the DNS
9176 cache when canceling a pending resolve. Don't log unless stuff is
9177 fishy. Resolves bug 463.
9179 o Minor bugfixes (anonymity):
9180 - Never report that we've used more bandwidth than we're willing to
9181 relay: it leaks how much non-relay traffic we're using. Resolves
9183 - When looking for a circuit to cannibalize, consider family as well
9184 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
9185 circuit cannibalization).
9187 o Code simplifications and refactoring:
9188 - Make a bunch of functions static. Remove some dead code.
9189 - Pull out about a third of the really big routerlist.c; put it in a
9190 new module, networkstatus.c.
9191 - Merge the extra fields in local_routerstatus_t back into
9192 routerstatus_t: we used to need one routerstatus_t for each
9193 authority's opinion, plus a local_routerstatus_t for the locally
9194 computed consensus opinion. To save space, we put the locally
9195 modified fields into local_routerstatus_t, and only the common
9196 stuff into routerstatus_t. But once v3 directories are in use,
9197 clients and caches will no longer need to hold authority opinions;
9198 thus, the rationale for keeping the types separate is now gone.
9199 - Make the code used to reschedule and reattempt downloads more
9201 - Turn all 'Are we a directory server/mirror?' logic into a call to
9203 - Remove the code to generate the oldest (v1) directory format.
9204 The code has been disabled since 0.2.0.5-alpha.
9207 Changes in version 0.2.0.7-alpha - 2007-09-21
9208 This seventh development snapshot makes bridges work again, makes bridge
9209 authorities work for the first time, fixes two huge performance flaws
9210 in hidden services, and fixes a variety of minor issues.
9212 o New directory authorities:
9213 - Set up moria1 and tor26 as the first v3 directory authorities. See
9214 doc/spec/dir-spec.txt for details on the new directory design.
9216 o Major bugfixes (crashes):
9217 - Fix possible segfaults in functions called from
9218 rend_process_relay_cell(). Bugfix on 0.1.2.x.
9220 o Major bugfixes (bridges):
9221 - Fix a bug that made servers send a "404 Not found" in response to
9222 attempts to fetch their server descriptor. This caused Tor servers
9223 to take many minutes to establish reachability for their DirPort,
9224 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
9225 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
9226 users configure that and specify a bridge with an identity
9227 fingerprint, now they will lookup the bridge descriptor at the
9228 default bridge authority via a one-hop tunnel, but once circuits
9229 are established they will switch to a three-hop tunnel for later
9230 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
9232 o Major bugfixes (hidden services):
9233 - Hidden services were choosing introduction points uniquely by
9234 hexdigest, but when constructing the hidden service descriptor
9235 they merely wrote the (potentially ambiguous) nickname.
9236 - Clients now use the v2 intro format for hidden service
9237 connections: they specify their chosen rendezvous point by identity
9238 digest rather than by (potentially ambiguous) nickname. Both
9239 are bugfixes on 0.1.2.x, and they could speed up hidden service
9240 connections dramatically. Thanks to Karsten Loesing.
9242 o Minor features (security):
9243 - As a client, do not believe any server that tells us that an
9244 address maps to an internal address space.
9245 - Make it possible to enable HashedControlPassword and
9246 CookieAuthentication at the same time.
9248 o Minor features (guard nodes):
9249 - Tag every guard node in our state file with the version that
9250 we believe added it, or with our own version if we add it. This way,
9251 if a user temporarily runs an old version of Tor and then switches
9252 back to a new one, she doesn't automatically lose her guards.
9254 o Minor features (speed):
9255 - When implementing AES counter mode, update only the portions of the
9256 counter buffer that need to change, and don't keep separate
9257 network-order and host-order counters when they are the same (i.e.,
9258 on big-endian hosts.)
9260 o Minor features (controller):
9261 - Accept LF instead of CRLF on controller, since some software has a
9262 hard time generating real Internet newlines.
9263 - Add GETINFO values for the server status events
9264 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
9268 - Routers no longer include bandwidth-history lines in their
9269 descriptors; this information is already available in extra-info
9270 documents, and including it in router descriptors took up 60%
9271 (!) of compressed router descriptor downloads. Completes
9272 implementation of proposal 104.
9273 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
9274 and TorControl.py, as they use the old v0 controller protocol,
9275 and are obsoleted by TorFlow anyway.
9276 - Drop support for v1 rendezvous descriptors, since we never used
9277 them anyway, and the code has probably rotted by now. Based on
9278 patch from Karsten Loesing.
9279 - On OSX, stop warning the user that kqueue support in libevent is
9280 "experimental", since it seems to have worked fine for ages.
9283 - When generating information telling us how to extend to a given
9284 router, do not try to include the nickname if it is absent. Fixes
9285 bug 467. Bugfix on 0.2.0.3-alpha.
9286 - Fix a user-triggerable (but not remotely-triggerable) segfault
9287 in expand_filename(). Bugfix on 0.1.2.x.
9288 - Fix a memory leak when freeing incomplete requests from DNSPort.
9289 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
9290 - Don't try to access (or alter) the state file when running
9291 --list-fingerprint or --verify-config or --hash-password. (Resolves
9292 bug 499.) Bugfix on 0.1.2.x.
9293 - Servers used to decline to publish their DirPort if their
9294 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
9295 were below a threshold. Now they only look at BandwidthRate and
9296 RelayBandwidthRate. Bugfix on 0.1.2.x.
9297 - Remove an optimization in the AES counter-mode code that assumed
9298 that the counter never exceeded 2^68. When the counter can be set
9299 arbitrarily as an IV (as it is by Karsten's new hidden services
9300 code), this assumption no longer holds. Bugfix on 0.1.2.x.
9301 - Resume listing "AUTHORITY" flag for authorities in network status.
9302 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
9304 o Code simplifications and refactoring:
9305 - Revamp file-writing logic so we don't need to have the entire
9306 contents of a file in memory at once before we write to disk. Tor,
9308 - Turn "descriptor store" into a full-fledged type.
9309 - Move all NT services code into a separate source file.
9310 - Unify all code that computes medians, percentile elements, etc.
9311 - Get rid of a needless malloc when parsing address policies.
9314 Changes in version 0.1.2.17 - 2007-08-30
9315 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
9316 X bundles. Vidalia 0.0.14 makes authentication required for the
9317 ControlPort in the default configuration, which addresses important
9318 security risks. Everybody who uses Vidalia (or another controller)
9321 In addition, this Tor update fixes major load balancing problems with
9322 path selection, which should speed things up a lot once many people
9325 o Major bugfixes (security):
9326 - We removed support for the old (v0) control protocol. It has been
9327 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
9328 become more of a headache than it's worth.
9330 o Major bugfixes (load balancing):
9331 - When choosing nodes for non-guard positions, weight guards
9332 proportionally less, since they already have enough load. Patch
9334 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
9335 will allow fast Tor servers to get more attention.
9336 - When we're upgrading from an old Tor version, forget our current
9337 guards and pick new ones according to the new weightings. These
9338 three load balancing patches could raise effective network capacity
9339 by a factor of four. Thanks to Mike Perry for measurements.
9341 o Major bugfixes (stream expiration):
9342 - Expire not-yet-successful application streams in all cases if
9343 they've been around longer than SocksTimeout. Right now there are
9344 some cases where the stream will live forever, demanding a new
9345 circuit every 15 seconds. Fixes bug 454; reported by lodger.
9347 o Minor features (controller):
9348 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
9349 is valid before any authentication has been received. It tells
9350 a controller what kind of authentication is expected, and what
9351 protocol is spoken. Implements proposal 119.
9353 o Minor bugfixes (performance):
9354 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
9355 greatly speeding up loading cached-routers from disk on startup.
9356 - Disable sentinel-based debugging for buffer code: we squashed all
9357 the bugs that this was supposed to detect a long time ago, and now
9358 its only effect is to change our buffer sizes from nice powers of
9359 two (which platform mallocs tend to like) to values slightly over
9360 powers of two (which make some platform mallocs sad).
9362 o Minor bugfixes (misc):
9363 - If exit bandwidth ever exceeds one third of total bandwidth, then
9364 use the correct formula to weight exit nodes when choosing paths.
9365 Based on patch from Mike Perry.
9366 - Choose perfectly fairly among routers when choosing by bandwidth and
9367 weighting by fraction of bandwidth provided by exits. Previously, we
9368 would choose with only approximate fairness, and correct ourselves
9369 if we ran off the end of the list.
9370 - If we require CookieAuthentication but we fail to write the
9371 cookie file, we would warn but not exit, and end up in a state
9372 where no controller could authenticate. Now we exit.
9373 - If we require CookieAuthentication, stop generating a new cookie
9374 every time we change any piece of our config.
9375 - Refuse to start with certain directory authority keys, and
9376 encourage people using them to stop.
9377 - Terminate multi-line control events properly. Original patch
9379 - Fix a minor memory leak when we fail to find enough suitable
9380 servers to choose a circuit.
9381 - Stop leaking part of the descriptor when we run into a particularly
9382 unparseable piece of it.
9385 Changes in version 0.2.0.6-alpha - 2007-08-26
9386 This sixth development snapshot features a new Vidalia version in the
9387 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
9388 the ControlPort in the default configuration, which addresses important
9391 In addition, this snapshot fixes major load balancing problems
9392 with path selection, which should speed things up a lot once many
9393 people have upgraded. The directory authorities also use a new
9394 mean-time-between-failure approach to tracking which servers are stable,
9395 rather than just looking at the most recent uptime.
9397 o New directory authorities:
9398 - Set up Tonga as the default bridge directory authority.
9401 - Directory authorities now track servers by weighted
9402 mean-times-between-failures. When we have 4 or more days of data,
9403 use measured MTBF rather than declared uptime to decide whether
9404 to call a router Stable. Implements proposal 108.
9406 o Major bugfixes (load balancing):
9407 - When choosing nodes for non-guard positions, weight guards
9408 proportionally less, since they already have enough load. Patch
9410 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
9411 will allow fast Tor servers to get more attention.
9412 - When we're upgrading from an old Tor version, forget our current
9413 guards and pick new ones according to the new weightings. These
9414 three load balancing patches could raise effective network capacity
9415 by a factor of four. Thanks to Mike Perry for measurements.
9417 o Major bugfixes (descriptor parsing):
9418 - Handle unexpected whitespace better in malformed descriptors. Bug
9419 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
9422 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
9423 GETINFO for Torstat to use until it can switch to using extrainfos.
9424 - Optionally (if built with -DEXPORTMALLINFO) export the output
9425 of mallinfo via http, as tor/mallinfo.txt. Only accessible
9429 - Do not intermix bridge routers with controller-added
9430 routers. (Bugfix on 0.2.0.x)
9431 - Do not fail with an assert when accept() returns an unexpected
9432 address family. Addresses but does not wholly fix bug 483. (Bugfix
9434 - Let directory authorities startup even when they can't generate
9435 a descriptor immediately, e.g. because they don't know their
9437 - Stop putting the authentication cookie in a file called "0"
9438 in your working directory if you don't specify anything for the
9439 new CookieAuthFile option. Reported by Matt Edman.
9440 - Make it possible to read the PROTOCOLINFO response in a way that
9441 conforms to our control-spec. Reported by Matt Edman.
9442 - Fix a minor memory leak when we fail to find enough suitable
9443 servers to choose a circuit. Bugfix on 0.1.2.x.
9444 - Stop leaking part of the descriptor when we run into a particularly
9445 unparseable piece of it. Bugfix on 0.1.2.x.
9446 - Unmap the extrainfo cache file on exit.
9449 Changes in version 0.2.0.5-alpha - 2007-08-19
9450 This fifth development snapshot fixes compilation on Windows again;
9451 fixes an obnoxious client-side bug that slowed things down and put
9452 extra load on the network; gets us closer to using the v3 directory
9453 voting scheme; makes it easier for Tor controllers to use cookie-based
9454 authentication; and fixes a variety of other bugs.
9457 - Version 1 directories are no longer generated in full. Instead,
9458 authorities generate and serve "stub" v1 directories that list
9459 no servers. This will stop Tor versions 0.1.0.x and earlier from
9460 working, but (for security reasons) nobody should be running those
9463 o Major bugfixes (compilation, 0.2.0.x):
9464 - Try to fix Win32 compilation again: improve checking for IPv6 types.
9465 - Try to fix MSVC compilation: build correctly on platforms that do
9466 not define s6_addr16 or s6_addr32.
9467 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
9470 o Major bugfixes (stream expiration):
9471 - Expire not-yet-successful application streams in all cases if
9472 they've been around longer than SocksTimeout. Right now there are
9473 some cases where the stream will live forever, demanding a new
9474 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
9477 o Minor features (directory servers):
9478 - When somebody requests a list of statuses or servers, and we have
9479 none of those, return a 404 rather than an empty 200.
9481 o Minor features (directory voting):
9482 - Store v3 consensus status consensuses on disk, and reload them
9485 o Minor features (security):
9486 - Warn about unsafe ControlPort configurations.
9487 - Refuse to start with certain directory authority keys, and
9488 encourage people using them to stop.
9490 o Minor features (controller):
9491 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
9492 is valid before any authentication has been received. It tells
9493 a controller what kind of authentication is expected, and what
9494 protocol is spoken. Implements proposal 119.
9495 - New config option CookieAuthFile to choose a new location for the
9496 cookie authentication file, and config option
9497 CookieAuthFileGroupReadable to make it group-readable.
9499 o Minor features (unit testing):
9500 - Add command-line arguments to unit-test executable so that we can
9501 invoke any chosen test from the command line rather than having
9502 to run the whole test suite at once; and so that we can turn on
9503 logging for the unit tests.
9505 o Minor bugfixes (on 0.1.2.x):
9506 - If we require CookieAuthentication but we fail to write the
9507 cookie file, we would warn but not exit, and end up in a state
9508 where no controller could authenticate. Now we exit.
9509 - If we require CookieAuthentication, stop generating a new cookie
9510 every time we change any piece of our config.
9511 - When loading bandwidth history, do not believe any information in
9512 the future. Fixes bug 434.
9513 - When loading entry guard information, do not believe any information
9515 - When we have our clock set far in the future and generate an
9516 onion key, then re-set our clock to be correct, we should not stop
9517 the onion key from getting rotated.
9518 - Clean up torrc sample config file.
9519 - Do not automatically run configure from autogen.sh. This
9520 non-standard behavior tended to annoy people who have built other
9523 o Minor bugfixes (on 0.2.0.x):
9524 - Fix a bug with AutomapHostsOnResolve that would always cause
9525 the second request to fail. Bug reported by Kate. Bugfix on
9527 - Fix a bug in ADDRMAP controller replies that would sometimes
9528 try to print a NULL. Patch from tup.
9529 - Read v3 directory authority keys from the right location.
9530 - Numerous bugfixes to directory voting code.
9533 Changes in version 0.1.2.16 - 2007-08-01
9534 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
9535 remote attacker in certain situations to rewrite the user's torrc
9536 configuration file. This can completely compromise anonymity of users
9537 in most configurations, including those running the Vidalia bundles,
9538 TorK, etc. Or worse.
9540 o Major security fixes:
9541 - Close immediately after missing authentication on control port;
9542 do not allow multiple authentication attempts.
9545 Changes in version 0.2.0.4-alpha - 2007-08-01
9546 This fourth development snapshot fixes a critical security vulnerability
9547 for most users, specifically those running Vidalia, TorK, etc. Everybody
9548 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
9550 o Major security fixes:
9551 - Close immediately after missing authentication on control port;
9552 do not allow multiple authentication attempts.
9554 o Major bugfixes (compilation):
9555 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
9558 o Minor features (performance):
9559 - Be even more aggressive about releasing RAM from small
9560 empty buffers. Thanks to our free-list code, this shouldn't be too
9561 performance-intensive.
9562 - Disable sentinel-based debugging for buffer code: we squashed all
9563 the bugs that this was supposed to detect a long time ago, and
9564 now its only effect is to change our buffer sizes from nice
9565 powers of two (which platform mallocs tend to like) to values
9566 slightly over powers of two (which make some platform mallocs sad).
9567 - Log malloc statistics from mallinfo() on platforms where it
9571 Changes in version 0.2.0.3-alpha - 2007-07-29
9572 This third development snapshot introduces new experimental
9573 blocking-resistance features and a preliminary version of the v3
9574 directory voting design, and includes many other smaller features
9578 - The first pieces of our "bridge" design for blocking-resistance
9579 are implemented. People can run bridge directory authorities;
9580 people can run bridges; and people can configure their Tor clients
9581 with a set of bridges to use as the first hop into the Tor network.
9582 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
9584 - Create listener connections before we setuid to the configured
9585 User and Group. Now non-Windows users can choose port values
9586 under 1024, start Tor as root, and have Tor bind those ports
9587 before it changes to another UID. (Windows users could already
9589 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
9590 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
9591 on "vserver" accounts. (Patch from coderman.)
9592 - Be even more aggressive about separating local traffic from relayed
9593 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
9595 o Major features (experimental):
9596 - First cut of code for "v3 dir voting": directory authorities will
9597 vote on a common network status document rather than each publishing
9598 their own opinion. This code needs more testing and more corner-case
9599 handling before it's ready for use.
9602 - Directory authorities now call routers Fast if their bandwidth is
9603 at least 100KB/s, and consider their bandwidth adequate to be a
9604 Guard if it is at least 250KB/s, no matter the medians. This fix
9605 complements proposal 107. [Bugfix on 0.1.2.x]
9606 - Directory authorities now never mark more than 3 servers per IP as
9607 Valid and Running. (Implements proposal 109, by Kevin Bauer and
9609 - Minor change to organizationName and commonName generation
9610 procedures in TLS certificates during Tor handshakes, to invalidate
9611 some earlier censorware approaches. This is not a long-term
9612 solution, but applying it will give us a bit of time to look into
9613 the epidemiology of countermeasures as they spread.
9615 o Major bugfixes (directory):
9616 - Rewrite directory tokenization code to never run off the end of
9617 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
9619 o Minor features (controller):
9620 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
9621 match requests to applications. (Patch from Robert Hogan.)
9622 - Report address and port correctly on connections to DNSPort. (Patch
9624 - Add a RESOLVE command to launch hostname lookups. (Original patch
9626 - Add GETINFO status/enough-dir-info to let controllers tell whether
9627 Tor has downloaded sufficient directory information. (Patch
9629 - You can now use the ControlSocket option to tell Tor to listen for
9630 controller connections on Unix domain sockets on systems that
9631 support them. (Patch from Peter Palfrader.)
9632 - STREAM NEW events are generated for DNSPort requests and for
9633 tunneled directory connections. (Patch from Robert Hogan.)
9634 - New "GETINFO address-mappings/*" command to get address mappings
9635 with expiry information. "addr-mappings/*" is now deprecated.
9638 o Minor features (misc):
9639 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
9641 - The tor-gencert tool for v3 directory authorities now creates all
9642 files as readable to the file creator only, and write-protects
9643 the authority identity key.
9644 - When dumping memory usage, list bytes used in buffer memory
9646 - When running with dmalloc, dump more stats on hup and on exit.
9647 - Directory authorities now fail quickly and (relatively) harmlessly
9648 if they generate a network status document that is somehow
9651 o Traffic load balancing improvements:
9652 - If exit bandwidth ever exceeds one third of total bandwidth, then
9653 use the correct formula to weight exit nodes when choosing paths.
9654 (Based on patch from Mike Perry.)
9655 - Choose perfectly fairly among routers when choosing by bandwidth and
9656 weighting by fraction of bandwidth provided by exits. Previously, we
9657 would choose with only approximate fairness, and correct ourselves
9658 if we ran off the end of the list. [Bugfix on 0.1.2.x]
9660 o Performance improvements:
9661 - Be more aggressive with freeing buffer RAM or putting it on the
9663 - Use Critical Sections rather than Mutexes for synchronizing threads
9664 on win32; Mutexes are heavier-weight, and designed for synchronizing
9667 o Deprecated and removed features:
9668 - RedirectExits is now deprecated.
9669 - Stop allowing address masks that do not correspond to bit prefixes.
9670 We have warned about these for a really long time; now it's time
9671 to reject them. (Patch from croup.)
9673 o Minor bugfixes (directory):
9674 - Fix another crash bug related to extra-info caching. (Bug found by
9675 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
9676 - Directories no longer return a "304 not modified" when they don't
9677 have the networkstatus the client asked for. Also fix a memory
9678 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
9679 - We had accidentally labelled 0.1.2.x directory servers as not
9680 suitable for begin_dir requests, and had labelled no directory
9681 servers as suitable for uploading extra-info documents. [Bugfix
9684 o Minor bugfixes (dns):
9685 - Fix a crash when DNSPort is set more than once. (Patch from Robert
9686 Hogan.) [Bugfix on 0.2.0.2-alpha]
9687 - Add DNSPort connections to the global connection list, so that we
9688 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
9690 - Fix a dangling reference that could lead to a crash when DNSPort is
9691 changed or closed (Patch from Robert Hogan.) [Bugfix on
9694 o Minor bugfixes (controller):
9695 - Provide DNS expiry times in GMT, not in local time. For backward
9696 compatibility, ADDRMAP events only provide GMT expiry in an extended
9697 field. "GETINFO address-mappings" always does the right thing.
9698 - Use CRLF line endings properly in NS events.
9699 - Terminate multi-line control events properly. (Original patch
9700 from tup.) [Bugfix on 0.1.2.x-alpha]
9701 - Do not include spaces in SOURCE_ADDR fields in STREAM
9702 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
9705 Changes in version 0.1.2.15 - 2007-07-17
9706 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
9707 problems, fixes compilation on BSD, and fixes a variety of other
9708 bugs. Everybody should upgrade.
9710 o Major bugfixes (compilation):
9711 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
9713 o Major bugfixes (crashes):
9714 - Try even harder not to dereference the first character after
9715 an mmap(). Reported by lodger.
9716 - Fix a crash bug in directory authorities when we re-number the
9717 routerlist while inserting a new router.
9718 - When the cached-routers file is an even multiple of the page size,
9719 don't run off the end and crash. (Fixes bug 455; based on idea
9721 - Fix eventdns.c behavior on Solaris: It is critical to include
9722 orconfig.h _before_ sys/types.h, so that we can get the expected
9723 definition of _FILE_OFFSET_BITS.
9725 o Major bugfixes (security):
9726 - Fix a possible buffer overrun when using BSD natd support. Bug
9728 - When sending destroy cells from a circuit's origin, don't include
9729 the reason for tearing down the circuit. The spec says we didn't,
9730 and now we actually don't. Reported by lodger.
9731 - Keep streamids from different exits on a circuit separate. This
9732 bug may have allowed other routers on a given circuit to inject
9733 cells into streams. Reported by lodger; fixes bug 446.
9734 - If there's a never-before-connected-to guard node in our list,
9735 never choose any guards past it. This way we don't expand our
9736 guard list unless we need to.
9738 o Minor bugfixes (guard nodes):
9739 - Weight guard selection by bandwidth, so that low-bandwidth nodes
9740 don't get overused as guards.
9742 o Minor bugfixes (directory):
9743 - Correctly count the number of authorities that recommend each
9744 version. Previously, we were under-counting by 1.
9745 - Fix a potential crash bug when we load many server descriptors at
9746 once and some of them make others of them obsolete. Fixes bug 458.
9748 o Minor bugfixes (hidden services):
9749 - Stop tearing down the whole circuit when the user asks for a
9750 connection to a port that the hidden service didn't configure.
9753 o Minor bugfixes (misc):
9754 - On Windows, we were preventing other processes from reading
9755 cached-routers while Tor was running. Reported by janbar.
9756 - Fix a possible (but very unlikely) bug in picking routers by
9757 bandwidth. Add a log message to confirm that it is in fact
9758 unlikely. Patch from lodger.
9759 - Backport a couple of memory leak fixes.
9760 - Backport miscellaneous cosmetic bugfixes.
9763 Changes in version 0.2.0.2-alpha - 2007-06-02
9764 o Major bugfixes on 0.2.0.1-alpha:
9765 - Fix an assertion failure related to servers without extra-info digests.
9766 Resolves bugs 441 and 442.
9768 o Minor features (directory):
9769 - Support "If-Modified-Since" when answering HTTP requests for
9770 directories, running-routers documents, and network-status documents.
9771 (There's no need to support it for router descriptors, since those
9772 are downloaded by descriptor digest.)
9774 o Minor build issues:
9775 - Clear up some MIPSPro compiler warnings.
9776 - When building from a tarball on a machine that happens to have SVK
9777 installed, report the micro-revision as whatever version existed
9778 in the tarball, not as "x".
9781 Changes in version 0.2.0.1-alpha - 2007-06-01
9782 This early development snapshot provides new features for people running
9783 Tor as both a client and a server (check out the new RelayBandwidth
9784 config options); lets Tor run as a DNS proxy; and generally moves us
9785 forward on a lot of fronts.
9787 o Major features, server usability:
9788 - New config options RelayBandwidthRate and RelayBandwidthBurst:
9789 a separate set of token buckets for relayed traffic. Right now
9790 relayed traffic is defined as answers to directory requests, and
9791 OR connections that don't have any local circuits on them.
9793 o Major features, client usability:
9794 - A client-side DNS proxy feature to replace the need for
9795 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
9796 for DNS requests on port 9999, use the Tor network to resolve them
9797 anonymously, and send the reply back like a regular DNS server.
9798 The code still only implements a subset of DNS.
9799 - Make PreferTunneledDirConns and TunnelDirConns work even when
9800 we have no cached directory info. This means Tor clients can now
9801 do all of their connections protected by TLS.
9803 o Major features, performance and efficiency:
9804 - Directory authorities accept and serve "extra info" documents for
9805 routers. These documents contain fields from router descriptors
9806 that aren't usually needed, and that use a lot of excess
9807 bandwidth. Once these fields are removed from router descriptors,
9808 the bandwidth savings should be about 60%. [Partially implements
9810 - Servers upload extra-info documents to any authority that accepts
9811 them. Authorities (and caches that have been configured to download
9812 extra-info documents) download them as needed. [Partially implements
9814 - Change the way that Tor buffers data that it is waiting to write.
9815 Instead of queueing data cells in an enormous ring buffer for each
9816 client->OR or OR->OR connection, we now queue cells on a separate
9817 queue for each circuit. This lets us use less slack memory, and
9818 will eventually let us be smarter about prioritizing different kinds
9820 - Use memory pools to allocate cells with better speed and memory
9821 efficiency, especially on platforms where malloc() is inefficient.
9822 - Stop reading on edge connections when their corresponding circuit
9823 buffers are full; start again as the circuits empty out.
9825 o Major features, other:
9826 - Add an HSAuthorityRecordStats option that hidden service authorities
9827 can use to track statistics of overall hidden service usage without
9828 logging information that would be very useful to an attacker.
9829 - Start work implementing multi-level keys for directory authorities:
9830 Add a standalone tool to generate key certificates. (Proposal 103.)
9833 - Directory authorities now call routers Stable if they have an
9834 uptime of at least 30 days, even if that's not the median uptime
9835 in the network. Implements proposal 107, suggested by Kevin Bauer
9838 o Minor fixes (resource management):
9839 - Count the number of open sockets separately from the number
9840 of active connection_t objects. This will let us avoid underusing
9841 our allocated connection limit.
9842 - We no longer use socket pairs to link an edge connection to an
9843 anonymous directory connection or a DirPort test connection.
9844 Instead, we track the link internally and transfer the data
9845 in-process. This saves two sockets per "linked" connection (at the
9846 client and at the server), and avoids the nasty Windows socketpair()
9848 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
9849 for every single inactive connection_t. Free items from the
9850 4k/16k-buffer free lists when they haven't been used for a while.
9852 o Minor features (build):
9853 - Make autoconf search for libevent, openssl, and zlib consistently.
9854 - Update deprecated macros in configure.in.
9855 - When warning about missing headers, tell the user to let us
9856 know if the compile succeeds anyway, so we can downgrade the
9858 - Include the current subversion revision as part of the version
9859 string: either fetch it directly if we're in an SVN checkout, do
9860 some magic to guess it if we're in an SVK checkout, or use
9861 the last-detected version if we're building from a .tar.gz.
9862 Use this version consistently in log messages.
9864 o Minor features (logging):
9865 - Always prepend "Bug: " to any log message about a bug.
9866 - Put a platform string (e.g. "Linux i686") in the startup log
9867 message, so when people paste just their logs, we know if it's
9868 OpenBSD or Windows or what.
9869 - When logging memory usage, break down memory used in buffers by
9872 o Minor features (directory system):
9873 - New config option V2AuthoritativeDirectory that all directory
9874 authorities should set. This will let future authorities choose
9875 not to serve V2 directory information.
9876 - Directory authorities allow multiple router descriptors and/or extra
9877 info documents to be uploaded in a single go. This will make
9878 implementing proposal 104 simpler.
9880 o Minor features (controller):
9881 - Add a new config option __DisablePredictedCircuits designed for
9882 use by the controller, when we don't want Tor to build any circuits
9884 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
9885 so we can exit from the middle of the circuit.
9886 - Implement "getinfo status/circuit-established".
9887 - Implement "getinfo status/version/..." so a controller can tell
9888 whether the current version is recommended, and whether any versions
9889 are good, and how many authorities agree. (Patch from shibz.)
9891 o Minor features (hidden services):
9892 - Allow multiple HiddenServicePort directives with the same virtual
9893 port; when they occur, the user is sent round-robin to one
9894 of the target ports chosen at random. Partially fixes bug 393 by
9895 adding limited ad-hoc round-robining.
9897 o Minor features (other):
9899 - Add a new AutomapHostsOnResolve option: when it is enabled, any
9900 resolve request for hosts matching a given pattern causes Tor to
9901 generate an internal virtual address mapping for that host. This
9902 allows DNSPort to work sensibly with hidden service users. By
9903 default, .exit and .onion addresses are remapped; the list of
9904 patterns can be reconfigured with AutomapHostsSuffixes.
9905 - Add an "-F" option to tor-resolve to force a resolve for a .onion
9906 address. Thanks to the AutomapHostsOnResolve option, this is no
9907 longer a completely silly thing to do.
9908 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
9909 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
9910 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
9911 minus 1 byte: the actual maximum declared bandwidth.
9914 - Removed support for the old binary "version 0" controller protocol.
9915 This has been deprecated since 0.1.1, and warnings have been issued
9916 since 0.1.2. When we encounter a v0 control message, we now send
9917 back an error and close the connection.
9918 - Remove the old "dns worker" server DNS code: it hasn't been default
9919 since 0.1.2.2-alpha, and all the servers seem to be using the new
9922 o Minor bugfixes (portability):
9923 - Even though Windows is equally happy with / and \ as path separators,
9924 try to use \ consistently on Windows and / consistently on Unix: it
9925 makes the log messages nicer.
9926 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
9927 - Read resolv.conf files correctly on platforms where read() returns
9928 partial results on small file reads.
9930 o Minor bugfixes (directory):
9931 - Correctly enforce that elements of directory objects do not appear
9932 more often than they are allowed to appear.
9933 - When we are reporting the DirServer line we just parsed, we were
9934 logging the second stanza of the key fingerprint, not the first.
9936 o Minor bugfixes (logging):
9937 - When we hit an EOF on a log (probably because we're shutting down),
9938 don't try to remove the log from the list: just mark it as
9939 unusable. (Bulletproofs against bug 222.)
9941 o Minor bugfixes (other):
9942 - In the exitlist script, only consider the most recently published
9943 server descriptor for each server. Also, when the user requests
9944 a list of servers that _reject_ connections to a given address,
9945 explicitly exclude the IPs that also have servers that accept
9946 connections to that address. (Resolves bug 405.)
9947 - Stop allowing hibernating servers to be "stable" or "fast".
9948 - On Windows, we were preventing other processes from reading
9949 cached-routers while Tor was running. (Reported by janbar)
9950 - Make the NodeFamilies config option work. (Reported by
9951 lodger -- it has never actually worked, even though we added it
9953 - Check return values from pthread_mutex functions.
9954 - Don't save non-general-purpose router descriptors to the disk cache,
9955 because we have no way of remembering what their purpose was when
9957 - Add even more asserts to hunt down bug 417.
9958 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
9959 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
9960 Add a log message to confirm that it is in fact unlikely.
9962 o Minor bugfixes (controller):
9963 - Make 'getinfo fingerprint' return a 551 error if we're not a
9964 server, so we match what the control spec claims we do. Reported
9966 - Fix a typo in an error message when extendcircuit fails that
9967 caused us to not follow the \r\n-based delimiter protocol. Reported
9970 o Code simplifications and refactoring:
9971 - Stop passing around circuit_t and crypt_path_t pointers that are
9972 implicit in other procedure arguments.
9973 - Drop the old code to choke directory connections when the
9974 corresponding OR connections got full: thanks to the cell queue
9975 feature, OR conns don't get full any more.
9976 - Make dns_resolve() handle attaching connections to circuits
9977 properly, so the caller doesn't have to.
9978 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
9979 - Keep the connection array as a dynamic smartlist_t, rather than as
9980 a fixed-sized array. This is important, as the number of connections
9981 is becoming increasingly decoupled from the number of sockets.
9984 Changes in version 0.1.2.14 - 2007-05-25
9985 Tor 0.1.2.14 changes the addresses of two directory authorities (this
9986 change especially affects those who serve or use hidden services),
9987 and fixes several other crash- and security-related bugs.
9989 o Directory authority changes:
9990 - Two directory authorities (moria1 and moria2) just moved to new
9991 IP addresses. This change will particularly affect those who serve
9992 or use hidden services.
9994 o Major bugfixes (crashes):
9995 - If a directory server runs out of space in the connection table
9996 as it's processing a begin_dir request, it will free the exit stream
9997 but leave it attached to the circuit, leading to unpredictable
9998 behavior. (Reported by seeess, fixes bug 425.)
9999 - Fix a bug in dirserv_remove_invalid() that would cause authorities
10000 to corrupt memory under some really unlikely scenarios.
10001 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
10002 - Avoid segfaults when reading from mmaped descriptor file. (Reported
10005 o Major bugfixes (security):
10006 - When choosing an entry guard for a circuit, avoid using guards
10007 that are in the same family as the chosen exit -- not just guards
10008 that are exactly the chosen exit. (Reported by lodger.)
10010 o Major bugfixes (resource management):
10011 - If a directory authority is down, skip it when deciding where to get
10012 networkstatus objects or descriptors. Otherwise we keep asking
10013 every 10 seconds forever. Fixes bug 384.
10014 - Count it as a failure if we fetch a valid network-status but we
10015 don't want to keep it. Otherwise we'll keep fetching it and keep
10016 not wanting to keep it. Fixes part of bug 422.
10017 - If all of our dirservers have given us bad or no networkstatuses
10018 lately, then stop hammering them once per minute even when we
10019 think they're failed. Fixes another part of bug 422.
10022 - Actually set the purpose correctly for descriptors inserted with
10023 purpose=controller.
10024 - When we have k non-v2 authorities in our DirServer config,
10025 we ignored the last k authorities in the list when updating our
10027 - Correctly back-off from requesting router descriptors that we are
10028 having a hard time downloading.
10029 - Read resolv.conf files correctly on platforms where read() returns
10030 partial results on small file reads.
10031 - Don't rebuild the entire router store every time we get 32K of
10032 routers: rebuild it when the journal gets very large, or when
10033 the gaps in the store get very large.
10036 - When routers publish SVN revisions in their router descriptors,
10037 authorities now include those versions correctly in networkstatus
10039 - Warn when using a version of libevent before 1.3b to run a server on
10040 OSX or BSD: these versions interact badly with userspace threads.
10043 Changes in version 0.1.2.13 - 2007-04-24
10044 This release features some major anonymity fixes, such as safer path
10045 selection; better client performance; faster bootstrapping, better
10046 address detection, and better DNS support for servers; write limiting as
10047 well as read limiting to make servers easier to run; and a huge pile of
10048 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
10050 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
10051 of the Freenode IRC network, remembering his patience and vision for
10052 free speech on the Internet.
10055 - Fix a memory leak when we ask for "all" networkstatuses and we
10056 get one we don't recognize.
10057 - Add more asserts to hunt down bug 417.
10058 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
10061 Changes in version 0.1.2.12-rc - 2007-03-16
10063 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
10064 directory information requested inside Tor connections (i.e. via
10065 begin_dir cells). It only triggered when the same connection was
10066 serving other data at the same time. Reported by seeess.
10069 - When creating a circuit via the controller, send a 'launched'
10070 event when we're done, so we follow the spec better.
10073 Changes in version 0.1.2.11-rc - 2007-03-15
10074 o Minor bugfixes (controller), reported by daejees:
10075 - Correct the control spec to match how the code actually responds
10076 to 'getinfo addr-mappings/*'.
10077 - The control spec described a GUARDS event, but the code
10078 implemented a GUARD event. Standardize on GUARD, but let people
10079 ask for GUARDS too.
10082 Changes in version 0.1.2.10-rc - 2007-03-07
10083 o Major bugfixes (Windows):
10084 - Do not load the NT services library functions (which may not exist)
10085 just to detect if we're a service trying to shut down. Now we run
10086 on Win98 and friends again.
10088 o Minor bugfixes (other):
10089 - Clarify a couple of log messages.
10090 - Fix a misleading socks5 error number.
10093 Changes in version 0.1.2.9-rc - 2007-03-02
10094 o Major bugfixes (Windows):
10095 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
10096 of the usual GCC "%llu". This prevents a bug when saving 64-bit
10097 int configuration values: the high-order 32 bits would get
10098 truncated. In particular, we were being bitten by the default
10099 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
10100 and maybe also bug 397.)
10102 o Minor bugfixes (performance):
10103 - Use OpenSSL's AES implementation on platforms where it's faster.
10104 This could save us as much as 10% CPU usage.
10106 o Minor bugfixes (server):
10107 - Do not rotate onion key immediately after setting it for the first
10110 o Minor bugfixes (directory authorities):
10111 - Stop calling servers that have been hibernating for a long time
10112 "stable". Also, stop letting hibernating or obsolete servers affect
10113 uptime and bandwidth cutoffs.
10114 - Stop listing hibernating servers in the v1 directory.
10116 o Minor bugfixes (hidden services):
10117 - Upload hidden service descriptors slightly less often, to reduce
10118 load on authorities.
10120 o Minor bugfixes (other):
10121 - Fix an assert that could trigger if a controller quickly set then
10122 cleared EntryNodes. Bug found by Udo van den Heuvel.
10123 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
10125 - Fix a potential race condition in the rpm installer. Found by
10127 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
10128 of 2 as indicating that the server is completely bad; it sometimes
10129 means that the server is just bad for the request in question. (may fix
10130 the last of bug 326.)
10131 - Disable encrypted directory connections when we don't have a server
10132 descriptor for the destination. We'll get this working again in
10136 Changes in version 0.1.2.8-beta - 2007-02-26
10137 o Major bugfixes (crashes):
10138 - Stop crashing when the controller asks us to resetconf more than
10139 one config option at once. (Vidalia 0.0.11 does this.)
10140 - Fix a crash that happened on Win98 when we're given command-line
10141 arguments: don't try to load NT service functions from advapi32.dll
10142 except when we need them. (Bug introduced in 0.1.2.7-alpha;
10144 - Fix a longstanding obscure crash bug that could occur when
10145 we run out of DNS worker processes. (Resolves bug 390.)
10147 o Major bugfixes (hidden services):
10148 - Correctly detect whether hidden service descriptor downloads are
10149 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
10151 o Major bugfixes (accounting):
10152 - When we start during an accounting interval before it's time to wake
10153 up, remember to wake up at the correct time. (May fix bug 342.)
10155 o Minor bugfixes (controller):
10156 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
10157 clear the corresponding on_circuit variable, and remember later
10158 that we don't need to send a redundant CLOSED event. Resolves part
10160 - Report events where a resolve succeeded or where we got a socks
10161 protocol error correctly, rather than calling both of them
10163 - Change reported stream target addresses to IP consistently when
10164 we finally get the IP from an exit node.
10165 - Send log messages to the controller even if they happen to be very
10168 o Minor bugfixes (other):
10169 - Display correct results when reporting which versions are
10170 recommended, and how recommended they are. (Resolves bug 383.)
10171 - Improve our estimates for directory bandwidth to be less random:
10172 guess that an unrecognized directory will have the average bandwidth
10173 from all known directories, not that it will have the average
10174 bandwidth from those directories earlier than it on the list.
10175 - If we start a server with ClientOnly 1, then set ClientOnly to 0
10176 and hup, stop triggering an assert based on an empty onion_key.
10177 - On platforms with no working mmap() equivalent, don't warn the
10178 user when cached-routers doesn't exist.
10179 - Warn the user when mmap() [or its equivalent] fails for some reason
10180 other than file-not-found.
10181 - Don't warn the user when cached-routers.new doesn't exist: that's
10182 perfectly fine when starting up for the first time.
10183 - When EntryNodes are configured, rebuild the guard list to contain,
10184 in order: the EntryNodes that were guards before; the rest of the
10185 EntryNodes; the nodes that were guards before.
10186 - Mask out all signals in sub-threads; only the libevent signal
10187 handler should be processing them. This should prevent some crashes
10188 on some machines using pthreads. (Patch from coderman.)
10189 - Fix switched arguments on memset in the implementation of
10190 tor_munmap() for systems with no mmap() call.
10191 - When Tor receives a router descriptor that it asked for, but
10192 no longer wants (because it has received fresh networkstatuses
10193 in the meantime), do not warn the user. Cache the descriptor if
10194 we're a cache; drop it if we aren't.
10195 - Make earlier entry guards _really_ get retried when the network
10197 - On a malformed DNS reply, always give an error to the corresponding
10199 - Build with recent libevents on platforms that do not define the
10200 nonstandard types "u_int8_t" and friends.
10202 o Minor features (controller):
10203 - Warn the user when an application uses the obsolete binary v0
10204 control protocol. We're planning to remove support for it during
10205 the next development series, so it's good to give people some
10207 - Add STREAM_BW events to report per-entry-stream bandwidth
10208 use. (Patch from Robert Hogan.)
10209 - Rate-limit SIGNEWNYM signals in response to controllers that
10210 impolitely generate them for every single stream. (Patch from
10211 mwenge; closes bug 394.)
10212 - Make REMAP stream events have a SOURCE (cache or exit), and
10213 make them generated in every case where we get a successful
10214 connected or resolved cell.
10216 o Minor bugfixes (performance):
10217 - Call router_have_min_dir_info half as often. (This is showing up in
10218 some profiles, but not others.)
10219 - When using GCC, make log_debug never get called at all, and its
10220 arguments never get evaluated, when no debug logs are configured.
10221 (This is showing up in some profiles, but not others.)
10224 - Remove some never-implemented options. Mark PathlenCoinWeight as
10226 - Implement proposal 106: Stop requiring clients to have well-formed
10227 certificates; stop checking nicknames in certificates. (Clients
10228 have certificates so that they can look like Tor servers, but in
10229 the future we might want to allow them to look like regular TLS
10230 clients instead. Nicknames in certificates serve no purpose other
10231 than making our protocol easier to recognize on the wire.)
10232 - Revise messages on handshake failure again to be even more clear about
10233 which are incoming connections and which are outgoing.
10234 - Discard any v1 directory info that's over 1 month old (for
10235 directories) or over 1 week old (for running-routers lists).
10236 - Do not warn when individual nodes in the configuration's EntryNodes,
10237 ExitNodes, etc are down: warn only when all possible nodes
10238 are down. (Fixes bug 348.)
10239 - Always remove expired routers and networkstatus docs before checking
10240 whether we have enough information to build circuits. (Fixes
10242 - Put a lower-bound on MaxAdvertisedBandwidth.
10245 Changes in version 0.1.2.7-alpha - 2007-02-06
10246 o Major bugfixes (rate limiting):
10247 - Servers decline directory requests much more aggressively when
10248 they're low on bandwidth. Otherwise they end up queueing more and
10249 more directory responses, which can't be good for latency.
10250 - But never refuse directory requests from local addresses.
10251 - Fix a memory leak when sending a 503 response for a networkstatus
10253 - Be willing to read or write on local connections (e.g. controller
10254 connections) even when the global rate limiting buckets are empty.
10255 - If our system clock jumps back in time, don't publish a negative
10256 uptime in the descriptor. Also, don't let the global rate limiting
10257 buckets go absurdly negative.
10258 - Flush local controller connection buffers periodically as we're
10259 writing to them, so we avoid queueing 4+ megabytes of data before
10262 o Major bugfixes (NT services):
10263 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
10264 command-line flag so that admins can override the default by saying
10265 "tor --service install --user "SomeUser"". This will not affect
10266 existing installed services. Also, warn the user that the service
10267 will look for its configuration file in the service user's
10268 %appdata% directory. (We can't do the 'hardwire the user's appdata
10269 directory' trick any more, since we may not have read access to that
10272 o Major bugfixes (other):
10273 - Previously, we would cache up to 16 old networkstatus documents
10274 indefinitely, if they came from nontrusted authorities. Now we
10275 discard them if they are more than 10 days old.
10276 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
10278 - Detect and reject malformed DNS responses containing circular
10280 - If exits are rare enough that we're not marking exits as guards,
10281 ignore exit bandwidth when we're deciding the required bandwidth
10283 - When we're handling a directory connection tunneled over Tor,
10284 don't fill up internal memory buffers with all the data we want
10285 to tunnel; instead, only add it if the OR connection that will
10286 eventually receive it has some room for it. (This can lead to
10287 slowdowns in tunneled dir connections; a better solution will have
10288 to wait for 0.2.0.)
10290 o Minor bugfixes (dns):
10291 - Add some defensive programming to eventdns.c in an attempt to catch
10292 possible memory-stomping bugs.
10293 - Detect and reject DNS replies containing IPv4 or IPv6 records with
10294 an incorrect number of bytes. (Previously, we would ignore the
10296 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
10297 in the correct order, and doesn't crash.
10298 - Free memory held in recently-completed DNS lookup attempts on exit.
10299 This was not a memory leak, but may have been hiding memory leaks.
10300 - Handle TTL values correctly on reverse DNS lookups.
10301 - Treat failure to parse resolv.conf as an error.
10303 o Minor bugfixes (other):
10304 - Fix crash with "tor --list-fingerprint" (reported by seeess).
10305 - When computing clock skew from directory HTTP headers, consider what
10306 time it was when we finished asking for the directory, not what
10308 - Expire socks connections if they spend too long waiting for the
10309 handshake to finish. Previously we would let them sit around for
10310 days, if the connecting application didn't close them either.
10311 - And if the socks handshake hasn't started, don't send a
10312 "DNS resolve socks failed" handshake reply; just close it.
10313 - Stop using C functions that OpenBSD's linker doesn't like.
10314 - Don't launch requests for descriptors unless we have networkstatuses
10315 from at least half of the authorities. This delays the first
10316 download slightly under pathological circumstances, but can prevent
10317 us from downloading a bunch of descriptors we don't need.
10318 - Do not log IPs with TLS failures for incoming TLS
10319 connections. (Fixes bug 382.)
10320 - If the user asks to use invalid exit nodes, be willing to use
10322 - Stop using the reserved ac_cv namespace in our configure script.
10323 - Call stat() slightly less often; use fstat() when possible.
10324 - Refactor the way we handle pending circuits when an OR connection
10325 completes or fails, in an attempt to fix a rare crash bug.
10326 - Only rewrite a conn's address based on X-Forwarded-For: headers
10327 if it's a parseable public IP address; and stop adding extra quotes
10328 to the resulting address.
10331 - Weight directory requests by advertised bandwidth. Now we can
10332 let servers enable write limiting but still allow most clients to
10333 succeed at their directory requests. (We still ignore weights when
10334 choosing a directory authority; I hope this is a feature.)
10337 - Create a new file ReleaseNotes which was the old ChangeLog. The
10338 new ChangeLog file now includes the summaries for all development
10340 - Check for addresses with invalid characters at the exit as well
10341 as at the client, and warn less verbosely when they fail. You can
10342 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
10343 - Adapt a patch from goodell to let the contrib/exitlist script
10344 take arguments rather than require direct editing.
10345 - Inform the server operator when we decide not to advertise a
10346 DirPort due to AccountingMax enabled or a low BandwidthRate. It
10347 was confusing Zax, so now we're hopefully more helpful.
10348 - Bring us one step closer to being able to establish an encrypted
10349 directory tunnel without knowing a descriptor first. Still not
10350 ready yet. As part of the change, now assume we can use a
10351 create_fast cell if we don't know anything about a router.
10352 - Allow exit nodes to use nameservers running on ports other than 53.
10353 - Servers now cache reverse DNS replies.
10354 - Add an --ignore-missing-torrc command-line option so that we can
10355 get the "use sensible defaults if the configuration file doesn't
10356 exist" behavior even when specifying a torrc location on the command
10359 o Minor features (controller):
10360 - Track reasons for OR connection failure; make these reasons
10361 available via the controller interface. (Patch from Mike Perry.)
10362 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
10363 can learn when clients are sending malformed hostnames to Tor.
10364 - Clean up documentation for controller status events.
10365 - Add a REMAP status to stream events to note that a stream's
10366 address has changed because of a cached address or a MapAddress
10370 Changes in version 0.1.2.6-alpha - 2007-01-09
10372 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
10373 connection handles more than 4 gigs in either direction, we crash.
10374 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
10375 advertised exit node, somebody might try to exit from us when
10376 we're bootstrapping and before we've built our descriptor yet.
10377 Refuse the connection rather than crashing.
10380 - Warn if we (as a server) find that we've resolved an address that we
10381 weren't planning to resolve.
10382 - Warn that using select() on any libevent version before 1.1 will be
10383 unnecessarily slow (even for select()).
10384 - Flush ERR-level controller status events just like we currently
10385 flush ERR-level log events, so that a Tor shutdown doesn't prevent
10386 the controller from learning about current events.
10388 o Minor features (more controller status events):
10389 - Implement EXTERNAL_ADDRESS server status event so controllers can
10390 learn when our address changes.
10391 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
10392 can learn when directories reject our descriptor.
10393 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
10394 can learn when a client application is speaking a non-socks protocol
10396 - Implement DANGEROUS_SOCKS client status event so controllers
10397 can learn when a client application is leaking DNS addresses.
10398 - Implement BUG general status event so controllers can learn when
10399 Tor is unhappy about its internal invariants.
10400 - Implement CLOCK_SKEW general status event so controllers can learn
10401 when Tor thinks the system clock is set incorrectly.
10402 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
10403 server status events so controllers can learn when their descriptors
10404 are accepted by a directory.
10405 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
10406 server status events so controllers can learn about Tor's progress in
10407 deciding whether it's reachable from the outside.
10408 - Implement BAD_LIBEVENT general status event so controllers can learn
10409 when we have a version/method combination in libevent that needs to
10411 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
10412 and DNS_USELESS server status events so controllers can learn
10413 about changes to DNS server status.
10415 o Minor features (directory):
10416 - Authorities no longer recommend exits as guards if this would shift
10417 too much load to the exit nodes.
10420 Changes in version 0.1.2.5-alpha - 2007-01-06
10422 - Enable write limiting as well as read limiting. Now we sacrifice
10423 capacity if we're pushing out lots of directory traffic, rather
10424 than overrunning the user's intended bandwidth limits.
10425 - Include TLS overhead when counting bandwidth usage; previously, we
10426 would count only the bytes sent over TLS, but not the bytes used
10428 - Support running the Tor service with a torrc not in the same
10429 directory as tor.exe and default to using the torrc located in
10430 the %appdata%\Tor\ of the user who installed the service. Patch
10432 - Servers now check for the case when common DNS requests are going to
10433 wildcarded addresses (i.e. all getting the same answer), and change
10434 their exit policy to reject *:* if it's happening.
10435 - Implement BEGIN_DIR cells, so we can connect to the directory
10436 server via TLS to do encrypted directory requests rather than
10437 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
10438 config options if you like.
10440 o Minor features (config and docs):
10441 - Start using the state file to store bandwidth accounting data:
10442 the bw_accounting file is now obsolete. We'll keep generating it
10443 for a while for people who are still using 0.1.2.4-alpha.
10444 - Try to batch changes to the state file so that we do as few
10445 disk writes as possible while still storing important things in
10447 - The state file and the bw_accounting file get saved less often when
10448 the AvoidDiskWrites config option is set.
10449 - Make PIDFile work on Windows (untested).
10450 - Add internal descriptions for a bunch of configuration options:
10451 accessible via controller interface and in comments in saved
10453 - Reject *:563 (NNTPS) in the default exit policy. We already reject
10454 NNTP by default, so this seems like a sensible addition.
10455 - Clients now reject hostnames with invalid characters. This should
10456 avoid some inadvertent info leaks. Add an option
10457 AllowNonRFC953Hostnames to disable this behavior, in case somebody
10458 is running a private network with hosts called @, !, and #.
10459 - Add a maintainer script to tell us which options are missing
10460 documentation: "make check-docs".
10461 - Add a new address-spec.txt document to describe our special-case
10462 addresses: .exit, .onion, and .noconnnect.
10464 o Minor features (DNS):
10465 - Ongoing work on eventdns infrastructure: now it has dns server
10466 and ipv6 support. One day Tor will make use of it.
10467 - Add client-side caching for reverse DNS lookups.
10468 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
10469 - When we change nameservers or IP addresses, reset and re-launch
10470 our tests for DNS hijacking.
10472 o Minor features (directory):
10473 - Authorities now specify server versions in networkstatus. This adds
10474 about 2% to the size of compressed networkstatus docs, and allows
10475 clients to tell which servers support BEGIN_DIR and which don't.
10476 The implementation is forward-compatible with a proposed future
10477 protocol version scheme not tied to Tor versions.
10478 - DirServer configuration lines now have an orport= option so
10479 clients can open encrypted tunnels to the authorities without
10480 having downloaded their descriptors yet. Enabled for moria1,
10481 moria2, tor26, and lefkada now in the default configuration.
10482 - Directory servers are more willing to send a 503 "busy" if they
10483 are near their write limit, especially for v1 directory requests.
10484 Now they can use their limited bandwidth for actual Tor traffic.
10485 - Clients track responses with status 503 from dirservers. After a
10486 dirserver has given us a 503, we try not to use it until an hour has
10487 gone by, or until we have no dirservers that haven't given us a 503.
10488 - When we get a 503 from a directory, and we're not a server, we don't
10489 count the failure against the total number of failures allowed
10490 for the thing we're trying to download.
10491 - Report X-Your-Address-Is correctly from tunneled directory
10492 connections; don't report X-Your-Address-Is when it's an internal
10493 address; and never believe reported remote addresses when they're
10495 - Protect against an unlikely DoS attack on directory servers.
10496 - Add a BadDirectory flag to network status docs so that authorities
10497 can (eventually) tell clients about caches they believe to be
10500 o Minor features (controller):
10501 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
10502 - Reimplement GETINFO so that info/names stays in sync with the
10504 - Implement "GETINFO fingerprint".
10505 - Implement "SETEVENTS GUARD" so controllers can get updates on
10506 entry guard status as it changes.
10508 o Minor features (clean up obsolete pieces):
10509 - Remove some options that have been deprecated since at least
10510 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
10511 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
10512 to set log options.
10513 - We no longer look for identity and onion keys in "identity.key" and
10514 "onion.key" -- these were replaced by secret_id_key and
10515 secret_onion_key in 0.0.8pre1.
10516 - We no longer require unrecognized directory entries to be
10519 o Major bugfixes (security):
10520 - Stop sending the HttpProxyAuthenticator string to directory
10521 servers when directory connections are tunnelled through Tor.
10522 - Clients no longer store bandwidth history in the state file.
10523 - Do not log introduction points for hidden services if SafeLogging
10525 - When generating bandwidth history, round down to the nearest
10526 1k. When storing accounting data, round up to the nearest 1k.
10527 - When we're running as a server, remember when we last rotated onion
10528 keys, so that we will rotate keys once they're a week old even if
10529 we never stay up for a week ourselves.
10531 o Major bugfixes (other):
10532 - Fix a longstanding bug in eventdns that prevented the count of
10533 timed-out resolves from ever being reset. This bug caused us to
10534 give up on a nameserver the third time it timed out, and try it
10535 10 seconds later... and to give up on it every time it timed out
10537 - Take out the '5 second' timeout from the connection retry
10538 schedule. Now the first connect attempt will wait a full 10
10539 seconds before switching to a new circuit. Perhaps this will help
10540 a lot. Based on observations from Mike Perry.
10541 - Fix a bug on the Windows implementation of tor_mmap_file() that
10542 would prevent the cached-routers file from ever loading. Reported
10546 - Fix an assert failure when a directory authority sets
10547 AuthDirRejectUnlisted and then receives a descriptor from an
10548 unlisted router. Reported by seeess.
10549 - Avoid a double-free when parsing malformed DirServer lines.
10550 - Fix a bug when a BSD-style PF socket is first used. Patch from
10552 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
10553 to resolve an address at a given exit node even when they ask for
10555 - Servers no longer ever list themselves in their "family" line,
10556 even if configured to do so. This makes it easier to configure
10557 family lists conveniently.
10558 - When running as a server, don't fall back to 127.0.0.1 when no
10559 nameservers are configured in /etc/resolv.conf; instead, make the
10560 user fix resolv.conf or specify nameservers explicitly. (Resolves
10562 - Stop accepting certain malformed ports in configured exit policies.
10563 - Don't re-write the fingerprint file every restart, unless it has
10565 - Stop warning when a single nameserver fails: only warn when _all_ of
10566 our nameservers have failed. Also, when we only have one nameserver,
10567 raise the threshold for deciding that the nameserver is dead.
10568 - Directory authorities now only decide that routers are reachable
10569 if their identity keys are as expected.
10570 - When the user uses bad syntax in the Log config line, stop
10571 suggesting other bad syntax as a replacement.
10572 - Correctly detect ipv6 DNS capability on OpenBSD.
10574 o Minor bugfixes (controller):
10575 - Report the circuit number correctly in STREAM CLOSED events. Bug
10576 reported by Mike Perry.
10577 - Do not report bizarre values for results of accounting GETINFOs
10578 when the last second's write or read exceeds the allotted bandwidth.
10579 - Report "unrecognized key" rather than an empty string when the
10580 controller tries to fetch a networkstatus that doesn't exist.
10583 Changes in version 0.1.1.26 - 2006-12-14
10584 o Security bugfixes:
10585 - Stop sending the HttpProxyAuthenticator string to directory
10586 servers when directory connections are tunnelled through Tor.
10587 - Clients no longer store bandwidth history in the state file.
10588 - Do not log introduction points for hidden services if SafeLogging
10592 - Fix an assert failure when a directory authority sets
10593 AuthDirRejectUnlisted and then receives a descriptor from an
10594 unlisted router (reported by seeess).
10597 Changes in version 0.1.2.4-alpha - 2006-12-03
10599 - Add support for using natd; this allows FreeBSDs earlier than
10600 5.1.2 to have ipfw send connections through Tor without using
10601 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
10604 - Make all connections to addresses of the form ".noconnect"
10605 immediately get closed. This lets application/controller combos
10606 successfully test whether they're talking to the same Tor by
10607 watching for STREAM events.
10608 - Make cross.sh cross-compilation script work even when autogen.sh
10609 hasn't been run. (Patch from Michael Mohr.)
10610 - Statistics dumped by -USR2 now include a breakdown of public key
10611 operations, for profiling.
10614 - Fix a major leak when directory authorities parse their
10615 approved-routers list, a minor memory leak when we fail to pick
10616 an exit node, and a few rare leaks on errors.
10617 - Handle TransPort connections even when the server sends data before
10618 the client sends data. Previously, the connection would just hang
10619 until the client sent data. (Patch from tup based on patch from
10621 - Avoid assert failure when our cached-routers file is empty on
10625 - Don't log spurious warnings when we see a circuit close reason we
10626 don't recognize; it's probably just from a newer version of Tor.
10627 - Have directory authorities allow larger amounts of drift in uptime
10628 without replacing the server descriptor: previously, a server that
10629 restarted every 30 minutes could have 48 "interesting" descriptors
10631 - Start linking to the Tor specification and Tor reference manual
10632 correctly in the Windows installer.
10633 - Add Vidalia to the OS X uninstaller script, so when we uninstall
10634 Tor/Privoxy we also uninstall Vidalia.
10635 - Resume building on Irix64, and fix a lot of warnings from its
10636 MIPSpro C compiler.
10637 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
10638 when we're running as a client.
10641 Changes in version 0.1.1.25 - 2006-11-04
10643 - When a client asks us to resolve (rather than connect to)
10644 an address, and we have a cached answer, give them the cached
10645 answer. Previously, we would give them no answer at all.
10646 - We were building exactly the wrong circuits when we predict
10647 hidden service requirements, meaning Tor would have to build all
10648 its circuits on demand.
10649 - If none of our live entry guards have a high uptime, but we
10650 require a guard with a high uptime, try adding a new guard before
10651 we give up on the requirement. This patch should make long-lived
10652 connections more stable on average.
10653 - When testing reachability of our DirPort, don't launch new
10654 tests when there's already one in progress -- unreachable
10655 servers were stacking up dozens of testing streams.
10657 o Security bugfixes:
10658 - When the user sends a NEWNYM signal, clear the client-side DNS
10659 cache too. Otherwise we continue to act on previous information.
10662 - Avoid a memory corruption bug when creating a hash table for
10664 - Avoid possibility of controller-triggered crash when misusing
10665 certain commands from a v0 controller on platforms that do not
10666 handle printf("%s",NULL) gracefully.
10667 - Avoid infinite loop on unexpected controller input.
10668 - Don't log spurious warnings when we see a circuit close reason we
10669 don't recognize; it's probably just from a newer version of Tor.
10670 - Add Vidalia to the OS X uninstaller script, so when we uninstall
10671 Tor/Privoxy we also uninstall Vidalia.
10674 Changes in version 0.1.2.3-alpha - 2006-10-29
10676 - Prepare for servers to publish descriptors less often: never
10677 discard a descriptor simply for being too old until either it is
10678 recommended by no authorities, or until we get a better one for
10679 the same router. Make caches consider retaining old recommended
10680 routers for even longer.
10681 - If most authorities set a BadExit flag for a server, clients
10682 don't think of it as a general-purpose exit. Clients only consider
10683 authorities that advertise themselves as listing bad exits.
10684 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
10685 headers for content, so that we can work better in the presence of
10686 caching HTTP proxies.
10687 - Allow authorities to list nodes as bad exits by fingerprint or by
10690 o Minor features, controller:
10691 - Add a REASON field to CIRC events; for backward compatibility, this
10692 field is sent only to controllers that have enabled the extended
10693 event format. Also, add additional reason codes to explain why
10694 a given circuit has been destroyed or truncated. (Patches from
10696 - Add a REMOTE_REASON field to extended CIRC events to tell the
10697 controller about why a remote OR told us to close a circuit.
10698 - Stream events also now have REASON and REMOTE_REASON fields,
10699 working much like those for circuit events.
10700 - There's now a GETINFO ns/... field so that controllers can ask Tor
10701 about the current status of a router.
10702 - A new event type "NS" to inform a controller when our opinion of
10703 a router's status has changed.
10704 - Add a GETINFO events/names and GETINFO features/names so controllers
10705 can tell which events and features are supported.
10706 - A new CLEARDNSCACHE signal to allow controllers to clear the
10707 client-side DNS cache without expiring circuits.
10709 o Security bugfixes:
10710 - When the user sends a NEWNYM signal, clear the client-side DNS
10711 cache too. Otherwise we continue to act on previous information.
10714 - Avoid sending junk to controllers or segfaulting when a controller
10715 uses EVENT_NEW_DESC with verbose nicknames.
10716 - Stop triggering asserts if the controller tries to extend hidden
10717 service circuits (reported by mwenge).
10718 - Avoid infinite loop on unexpected controller input.
10719 - When the controller does a "GETINFO network-status", tell it
10720 about even those routers whose descriptors are very old, and use
10721 long nicknames where appropriate.
10722 - Change NT service functions to be loaded on demand. This lets us
10723 build with MinGW without breaking Tor for Windows 98 users.
10724 - Do DirPort reachability tests less often, since a single test
10725 chews through many circuits before giving up.
10726 - In the hidden service example in torrc.sample, stop recommending
10727 esoteric and discouraged hidden service options.
10728 - When stopping an NT service, wait up to 10 sec for it to actually
10729 stop. Patch from Matt Edman; resolves bug 295.
10730 - Fix handling of verbose nicknames with ORCONN controller events:
10731 make them show up exactly when requested, rather than exactly when
10733 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
10734 printing a duplicate "$" in the keys we send (reported by mwenge).
10735 - Correctly set maximum connection limit on Cygwin. (This time
10737 - Try to detect Windows correctly when cross-compiling.
10738 - Detect the size of the routers file correctly even if it is
10739 corrupted (on systems without mmap) or not page-aligned (on systems
10740 with mmap). This bug was harmless.
10741 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
10742 to open a stream fails; now we do in more cases. This should
10743 make clients able to find a good exit faster in some cases, since
10744 unhandleable requests will now get an error rather than timing out.
10745 - Resolve two memory leaks when rebuilding the on-disk router cache
10746 (reported by fookoowa).
10747 - Clean up minor code warnings suggested by the MIPSpro C compiler,
10748 and reported by some Centos users.
10749 - Controller signals now work on non-Unix platforms that don't define
10750 SIGUSR1 and SIGUSR2 the way we expect.
10751 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
10752 values before failing, and always enables eventdns.
10753 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
10754 Try to fix this in configure.in by checking for most functions
10755 before we check for libevent.
10758 Changes in version 0.1.2.2-alpha - 2006-10-07
10760 - Make our async eventdns library on-by-default for Tor servers,
10761 and plan to deprecate the separate dnsworker threads.
10762 - Add server-side support for "reverse" DNS lookups (using PTR
10763 records so clients can determine the canonical hostname for a given
10764 IPv4 address). Only supported by servers using eventdns; servers
10765 now announce in their descriptors whether they support eventdns.
10766 - Specify and implement client-side SOCKS5 interface for reverse DNS
10767 lookups (see doc/socks-extensions.txt).
10768 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
10769 connect to directory servers through Tor. Previously, clients needed
10770 to find Tor exits to make private connections to directory servers.
10771 - Avoid choosing Exit nodes for entry or middle hops when the
10772 total bandwidth available from non-Exit nodes is much higher than
10773 the total bandwidth available from Exit nodes.
10774 - Workaround for name servers (like Earthlink's) that hijack failing
10775 DNS requests and replace the no-such-server answer with a "helpful"
10776 redirect to an advertising-driven search portal. Also work around
10777 DNS hijackers who "helpfully" decline to hijack known-invalid
10778 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
10779 lets you turn it off.
10780 - Send out a burst of long-range padding cells once we've established
10781 that we're reachable. Spread them over 4 circuits, so hopefully
10782 a few will be fast. This exercises our bandwidth and bootstraps
10783 us into the directory more quickly.
10785 o New/improved config options:
10786 - Add new config option "ResolvConf" to let the server operator
10787 choose an alternate resolve.conf file when using eventdns.
10788 - Add an "EnforceDistinctSubnets" option to control our "exclude
10789 servers on the same /16" behavior. It's still on by default; this
10790 is mostly for people who want to operate private test networks with
10791 all the machines on the same subnet.
10792 - If one of our entry guards is on the ExcludeNodes list, or the
10793 directory authorities don't think it's a good guard, treat it as
10794 if it were unlisted: stop using it as a guard, and throw it off
10795 the guards list if it stays that way for a long time.
10796 - Allow directory authorities to be marked separately as authorities
10797 for the v1 directory protocol, the v2 directory protocol, and
10798 as hidden service directories, to make it easier to retire old
10799 authorities. V1 authorities should set "HSAuthoritativeDir 1"
10800 to continue being hidden service authorities too.
10801 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
10803 o Minor features, controller:
10804 - Fix CIRC controller events so that controllers can learn the
10805 identity digests of non-Named servers used in circuit paths.
10806 - Let controllers ask for more useful identifiers for servers. Instead
10807 of learning identity digests for un-Named servers and nicknames
10808 for Named servers, the new identifiers include digest, nickname,
10809 and indication of Named status. Off by default; see control-spec.txt
10810 for more information.
10811 - Add a "getinfo address" controller command so it can display Tor's
10812 best guess to the user.
10813 - New controller event to alert the controller when our server
10814 descriptor has changed.
10815 - Give more meaningful errors on controller authentication failure.
10817 o Minor features, other:
10818 - When asked to resolve a hostname, don't use non-exit servers unless
10819 requested to do so. This allows servers with broken DNS to be
10820 useful to the network.
10821 - Divide eventdns log messages into warn and info messages.
10822 - Reserve the nickname "Unnamed" for routers that can't pick
10823 a hostname: any router can call itself Unnamed; directory
10824 authorities will never allocate Unnamed to any particular router;
10825 clients won't believe that any router is the canonical Unnamed.
10826 - Only include function names in log messages for info/debug messages.
10827 For notice/warn/err, the content of the message should be clear on
10828 its own, and printing the function name only confuses users.
10829 - Avoid some false positives during reachability testing: don't try
10830 to test via a server that's on the same /24 as us.
10831 - If we fail to build a circuit to an intended enclave, and it's
10832 not mandatory that we use that enclave, stop wanting it.
10833 - When eventdns is enabled, allow multithreaded builds on NetBSD and
10834 OpenBSD. (We had previously disabled threads on these platforms
10835 because they didn't have working thread-safe resolver functions.)
10837 o Major bugfixes, anonymity/security:
10838 - If a client asked for a server by name, and there's a named server
10839 in our network-status but we don't have its descriptor yet, we
10840 could return an unnamed server instead.
10841 - Fix NetBSD bug that could allow someone to force uninitialized RAM
10842 to be sent to a server's DNS resolver. This only affects NetBSD
10843 and other platforms that do not bounds-check tolower().
10844 - Reject (most) attempts to use Tor circuits with length one. (If
10845 many people start using Tor as a one-hop proxy, exit nodes become
10846 a more attractive target for compromise.)
10847 - Just because your DirPort is open doesn't mean people should be
10848 able to remotely teach you about hidden service descriptors. Now
10849 only accept rendezvous posts if you've got HSAuthoritativeDir set.
10851 o Major bugfixes, other:
10852 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
10853 - When a client asks the server to resolve (not connect to)
10854 an address, and it has a cached answer, give them the cached answer.
10855 Previously, the server would give them no answer at all.
10856 - Allow really slow clients to not hang up five minutes into their
10857 directory downloads (suggested by Adam J. Richter).
10858 - We were building exactly the wrong circuits when we anticipated
10859 hidden service requirements, meaning Tor would have to build all
10860 its circuits on demand.
10861 - Avoid crashing when we mmap a router cache file of size 0.
10862 - When testing reachability of our DirPort, don't launch new
10863 tests when there's already one in progress -- unreachable
10864 servers were stacking up dozens of testing streams.
10866 o Minor bugfixes, correctness:
10867 - If we're a directory mirror and we ask for "all" network status
10868 documents, we would discard status documents from authorities
10869 we don't recognize.
10870 - Avoid a memory corruption bug when creating a hash table for
10872 - Avoid controller-triggered crash when misusing certain commands
10873 from a v0 controller on platforms that do not handle
10874 printf("%s",NULL) gracefully.
10875 - Don't crash when a controller sends a third argument to an
10876 "extendcircuit" request.
10877 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
10878 response; fix error code when "getinfo dir/status/" fails.
10879 - Avoid crash when telling controller stream-status and a stream
10881 - Patch from Adam Langley to fix assert() in eventdns.c.
10882 - Fix a debug log message in eventdns to say "X resolved to Y"
10883 instead of "X resolved to X".
10884 - Make eventdns give strings for DNS errors, not just error numbers.
10885 - Track unreachable entry guards correctly: don't conflate
10886 'unreachable by us right now' with 'listed as down by the directory
10887 authorities'. With the old code, if a guard was unreachable by
10888 us but listed as running, it would clog our guard list forever.
10889 - Behave correctly in case we ever have a network with more than
10890 2GB/s total advertised capacity.
10891 - Make TrackExitHosts case-insensitive, and fix the behavior of
10892 ".suffix" TrackExitHosts items to avoid matching in the middle of
10894 - Finally fix the openssl warnings from newer gccs that believe that
10895 ignoring a return value is okay, but casting a return value and
10896 then ignoring it is a sign of madness.
10897 - Prevent the contrib/exitlist script from printing the same
10898 result more than once.
10899 - Patch from Steve Hildrey: Generate network status correctly on
10900 non-versioning dirservers.
10901 - Don't listen to the X-Your-Address-Is hint if you did the lookup
10902 via Tor; otherwise you'll think you're the exit node's IP address.
10904 o Minor bugfixes, performance:
10905 - Two small performance improvements on parsing descriptors.
10906 - Major performance improvement on inserting descriptors: change
10907 algorithm from O(n^2) to O(n).
10908 - Make the common memory allocation path faster on machines where
10909 malloc(0) returns a pointer.
10910 - Start remembering X-Your-Address-Is directory hints even if you're
10911 a client, so you can become a server more smoothly.
10912 - Avoid duplicate entries on MyFamily line in server descriptor.
10914 o Packaging, features:
10915 - Remove architecture from OS X builds. The official builds are
10916 now universal binaries.
10917 - The Debian package now uses --verify-config when (re)starting,
10918 to distinguish configuration errors from other errors.
10919 - Update RPMs to require libevent 1.1b.
10921 o Packaging, bugfixes:
10922 - Patches so Tor builds with MinGW on Windows.
10923 - Patches so Tor might run on Cygwin again.
10924 - Resume building on non-gcc compilers and ancient gcc. Resume
10925 building with the -O0 compile flag. Resume building cleanly on
10927 - Run correctly on OS X platforms with case-sensitive filesystems.
10928 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
10929 - Add autoconf checks so Tor can build on Solaris x86 again.
10932 - Documented (and renamed) ServerDNSSearchDomains and
10933 ServerDNSResolvConfFile options.
10934 - Be clearer that the *ListenAddress directives can be repeated
10938 Changes in version 0.1.1.24 - 2006-09-29
10940 - Allow really slow clients to not hang up five minutes into their
10941 directory downloads (suggested by Adam J. Richter).
10942 - Fix major performance regression from 0.1.0.x: instead of checking
10943 whether we have enough directory information every time we want to
10944 do something, only check when the directory information has changed.
10945 This should improve client CPU usage by 25-50%.
10946 - Don't crash if, after a server has been running for a while,
10947 it can't resolve its hostname.
10950 - Allow Tor to start when RunAsDaemon is set but no logs are set.
10951 - Don't crash when the controller receives a third argument to an
10952 "extendcircuit" request.
10953 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
10954 response; fix error code when "getinfo dir/status/" fails.
10955 - Fix configure.in to not produce broken configure files with
10956 more recent versions of autoconf. Thanks to Clint for his auto*
10958 - Fix security bug on NetBSD that could allow someone to force
10959 uninitialized RAM to be sent to a server's DNS resolver. This
10960 only affects NetBSD and other platforms that do not bounds-check
10962 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
10963 methods: these are known to be buggy.
10964 - If we're a directory mirror and we ask for "all" network status
10965 documents, we would discard status documents from authorities
10966 we don't recognize.
10969 Changes in version 0.1.2.1-alpha - 2006-08-27
10971 - Add "eventdns" async dns library from Adam Langley, tweaked to
10972 build on OSX and Windows. Only enabled if you pass the
10973 --enable-eventdns argument to configure.
10974 - Allow servers with no hostname or IP address to learn their
10975 IP address by asking the directory authorities. This code only
10976 kicks in when you would normally have exited with a "no address"
10977 error. Nothing's authenticated, so use with care.
10978 - Rather than waiting a fixed amount of time between retrying
10979 application connections, we wait only 5 seconds for the first,
10980 10 seconds for the second, and 15 seconds for each retry after
10981 that. Hopefully this will improve the expected user experience.
10982 - Patch from Tup to add support for transparent AP connections:
10983 this basically bundles the functionality of trans-proxy-tor
10984 into the Tor mainline. Now hosts with compliant pf/netfilter
10985 implementations can redirect TCP connections straight to Tor
10986 without diverting through SOCKS. Needs docs.
10987 - Busy directory servers save lots of memory by spooling server
10988 descriptors, v1 directories, and v2 networkstatus docs to buffers
10989 as needed rather than en masse. Also mmap the cached-routers
10990 files, so we don't need to keep the whole thing in memory too.
10991 - Automatically avoid picking more than one node from the same
10992 /16 network when constructing a circuit.
10993 - Revise and clean up the torrc.sample that we ship with; add
10994 a section for BandwidthRate and BandwidthBurst.
10997 - Split circuit_t into origin_circuit_t and or_circuit_t, and
10998 split connection_t into edge, or, dir, control, and base structs.
10999 These will save quite a bit of memory on busy servers, and they'll
11000 also help us track down bugs in the code and bugs in the spec.
11001 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
11002 or later. Log when we are doing this, so we can diagnose it when
11003 it fails. (Also, recommend libevent 1.1b for kqueue and
11004 win32 methods; deprecate libevent 1.0b harder; make libevent
11005 recommendation system saner.)
11006 - Start being able to build universal binaries on OS X (thanks
11008 - Export the default exit policy via the control port, so controllers
11009 don't need to guess what it is / will be later.
11010 - Add a man page entry for ProtocolWarnings.
11011 - Add TestVia config option to the man page.
11012 - Remove even more protocol-related warnings from Tor server logs,
11013 such as bad TLS handshakes and malformed begin cells.
11014 - Stop fetching descriptors if you're not a dir mirror and you
11015 haven't tried to establish any circuits lately. [This currently
11016 causes some dangerous behavior, because when you start up again
11017 you'll use your ancient server descriptors.]
11018 - New DirPort behavior: if you have your dirport set, you download
11019 descriptors aggressively like a directory mirror, whether or not
11020 your ORPort is set.
11021 - Get rid of the router_retry_connections notion. Now routers
11022 no longer try to rebuild long-term connections to directory
11023 authorities, and directory authorities no longer try to rebuild
11024 long-term connections to all servers. We still don't hang up
11025 connections in these two cases though -- we need to look at it
11026 more carefully to avoid flapping, and we likely need to wait til
11027 0.1.1.x is obsolete.
11028 - Drop compatibility with obsolete Tors that permit create cells
11029 to have the wrong circ_id_type.
11030 - Re-enable per-connection rate limiting. Get rid of the "OP
11031 bandwidth" concept. Lay groundwork for "bandwidth classes" --
11032 separate global buckets that apply depending on what sort of conn
11034 - Start publishing one minute or so after we find our ORPort
11035 to be reachable. This will help reduce the number of descriptors
11036 we have for ourselves floating around, since it's quite likely
11037 other things (e.g. DirPort) will change during that minute too.
11038 - Fork the v1 directory protocol into its own spec document,
11039 and mark dir-spec.txt as the currently correct (v2) spec.
11042 - When we find our DirPort to be reachable, publish a new descriptor
11043 so we'll tell the world (reported by pnx).
11044 - Publish a new descriptor after we hup/reload. This is important
11045 if our config has changed such that we'll want to start advertising
11046 our DirPort now, etc.
11047 - Allow Tor to start when RunAsDaemon is set but no logs are set.
11048 - When we have a state file we cannot parse, tell the user and
11049 move it aside. Now we avoid situations where the user starts
11050 Tor in 1904, Tor writes a state file with that timestamp in it,
11051 the user fixes her clock, and Tor refuses to start.
11052 - Fix configure.in to not produce broken configure files with
11053 more recent versions of autoconf. Thanks to Clint for his auto*
11055 - "tor --verify-config" now exits with -1(255) or 0 depending on
11056 whether the config options are bad or good.
11057 - Resolve bug 321 when using dnsworkers: append a period to every
11058 address we resolve at the exit node, so that we do not accidentally
11059 pick up local addresses, and so that failing searches are retried
11060 in the resolver search domains. (This is already solved for
11061 eventdns.) (This breaks Blossom servers for now.)
11062 - If we are using an exit enclave and we can't connect, e.g. because
11063 its webserver is misconfigured to not listen on localhost, then
11064 back off and try connecting from somewhere else before we fail.
11067 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
11068 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
11069 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
11070 when the IP address is mapped through MapAddress to a hostname.
11071 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
11072 useless IPv6 DNS resolves.
11073 - Patch suggested by Karsten Loesing: respond to SIGNAL command
11074 before we execute the signal, in case the signal shuts us down.
11075 - Clean up AllowInvalidNodes man page entry.
11076 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
11077 - Add more asserts to track down an assert error on a windows Tor
11078 server with connection_add being called with socket == -1.
11079 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
11080 - Fix misleading log messages: an entry guard that is "unlisted",
11081 as well as not known to be "down" (because we've never heard
11082 of it), is not therefore "up".
11083 - Remove code to special-case "-cvs" ending, since it has not
11084 actually mattered since 0.0.9.
11085 - Make our socks5 handling more robust to broken socks clients:
11086 throw out everything waiting on the buffer in between socks
11087 handshake phases, since they can't possibly (so the theory
11088 goes) have predicted what we plan to respond to them.
11091 Changes in version 0.1.1.23 - 2006-07-30
11093 - Fast Tor servers, especially exit nodes, were triggering asserts
11094 due to a bug in handling the list of pending DNS resolves. Some
11095 bugs still remain here; we're hunting them.
11096 - Entry guards could crash clients by sending unexpected input.
11097 - More fixes on reachability testing: if you find yourself reachable,
11098 then don't ever make any client requests (so you stop predicting
11099 circuits), then hup or have your clock jump, then later your IP
11100 changes, you won't think circuits are working, so you won't try to
11101 test reachability, so you won't publish.
11104 - Avoid a crash if the controller does a resetconf firewallports
11105 and then a setconf fascistfirewall=1.
11106 - Avoid an integer underflow when the dir authority decides whether
11107 a router is stable: we might wrongly label it stable, and compute
11108 a slightly wrong median stability, when a descriptor is published
11110 - Fix a place where we might trigger an assert if we can't build our
11111 own server descriptor yet.
11114 Changes in version 0.1.1.22 - 2006-07-05
11116 - Fix a big bug that was causing servers to not find themselves
11117 reachable if they changed IP addresses. Since only 0.1.1.22+
11118 servers can do reachability testing correctly, now we automatically
11119 make sure to test via one of these.
11120 - Fix to allow clients and mirrors to learn directory info from
11121 descriptor downloads that get cut off partway through.
11122 - Directory authorities had a bug in deciding if a newly published
11123 descriptor was novel enough to make everybody want a copy -- a few
11124 servers seem to be publishing new descriptors many times a minute.
11126 - Fix a rare bug that was causing some servers to complain about
11127 "closing wedged cpuworkers" and skip some circuit create requests.
11128 - Make the Exit flag in directory status documents actually work.
11131 Changes in version 0.1.1.21 - 2006-06-10
11132 o Crash and assert fixes from 0.1.1.20:
11133 - Fix a rare crash on Tor servers that have enabled hibernation.
11134 - Fix a seg fault on startup for Tor networks that use only one
11135 directory authority.
11136 - Fix an assert from a race condition that occurs on Tor servers
11137 while exiting, where various threads are trying to log that they're
11138 exiting, and delete the logs, at the same time.
11139 - Make our unit tests pass again on certain obscure platforms.
11142 - Add support for building SUSE RPM packages.
11143 - Speed up initial bootstrapping for clients: if we are making our
11144 first ever connection to any entry guard, then don't mark it down
11146 - When only one Tor server in the network is labelled as a guard,
11147 and we've already picked him, we would cycle endlessly picking him
11148 again, being unhappy about it, etc. Now we specifically exclude
11149 current guards when picking a new guard.
11150 - Servers send create cells more reliably after the TLS connection
11151 is established: we were sometimes forgetting to send half of them
11152 when we had more than one pending.
11153 - If we get a create cell that asks us to extend somewhere, but the
11154 Tor server there doesn't match the expected digest, we now send
11155 a destroy cell back, rather than silently doing nothing.
11156 - Make options->RedirectExit work again.
11157 - Make cookie authentication for the controller work again.
11158 - Stop being picky about unusual characters in the arguments to
11159 mapaddress. It's none of our business.
11160 - Add a new config option "TestVia" that lets you specify preferred
11161 middle hops to use for test circuits. Perhaps this will let me
11162 debug the reachability problems better.
11164 o Log / documentation fixes:
11165 - If we're a server and some peer has a broken TLS certificate, don't
11166 log about it unless ProtocolWarnings is set, i.e., we want to hear
11167 about protocol violations by others.
11168 - Fix spelling of VirtualAddrNetwork in man page.
11169 - Add a better explanation at the top of the autogenerated torrc file
11170 about what happened to our old torrc.
11173 Changes in version 0.1.1.20 - 2006-05-23
11175 - Downgrade a log severity where servers complain that they're
11177 - Avoid a compile warning on FreeBSD.
11178 - Remove string size limit on NEWDESC messages; solve bug 291.
11179 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
11180 more thoroughly when we're running on windows.
11183 Changes in version 0.1.1.19-rc - 2006-05-03
11185 - Regenerate our local descriptor if it's dirty and we try to use
11186 it locally (e.g. if it changes during reachability detection).
11187 - If we setconf our ORPort to 0, we continued to listen on the
11188 old ORPort and receive connections.
11189 - Avoid a second warning about machine/limits.h on Debian
11191 - Be willing to add our own routerinfo into the routerlist.
11192 Now authorities will include themselves in their directories
11193 and network-statuses.
11194 - Stop trying to upload rendezvous descriptors to every
11195 directory authority: only try the v1 authorities.
11196 - Servers no longer complain when they think they're not
11197 registered with the directory authorities. There were too many
11199 - Backport dist-rpm changes so rpms can be built without errors.
11202 - Implement an option, VirtualAddrMask, to set which addresses
11203 get handed out in response to mapaddress requests. This works
11204 around a bug in tsocks where 127.0.0.0/8 is never socksified.
11207 Changes in version 0.1.1.18-rc - 2006-04-10
11209 - Work harder to download live network-statuses from all the
11210 directory authorities we know about. Improve the threshold
11211 decision logic so we're more robust to edge cases.
11212 - When fetching rendezvous descriptors, we were willing to ask
11213 v2 authorities too, which would always return 404.
11216 - Stop listing down or invalid nodes in the v1 directory. This will
11217 reduce its bulk by about 1/3, and reduce load on directory
11219 - When deciding whether a router is Fast or Guard-worthy, consider
11220 his advertised BandwidthRate and not just the BandwidthCapacity.
11221 - No longer ship INSTALL and README files -- they are useless now.
11222 - Force rpmbuild to behave and honor target_cpu.
11223 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
11224 - Start to include translated versions of the tor-doc-*.html
11225 files, along with the screenshots. Still needs more work.
11226 - Start sending back 512 and 451 errors if mapaddress fails,
11227 rather than not sending anything back at all.
11228 - When we fail to bind or listen on an incoming or outgoing
11229 socket, we should close it before failing. otherwise we just
11230 leak it. (thanks to weasel for finding.)
11231 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
11232 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
11233 - Make NoPublish (even though deprecated) work again.
11234 - Fix a minor security flaw where a versioning auth dirserver
11235 could list a recommended version many times in a row to make
11236 clients more convinced that it's recommended.
11237 - Fix crash bug if there are two unregistered servers running
11238 with the same nickname, one of them is down, and you ask for
11239 them by nickname in your EntryNodes or ExitNodes. Also, try
11240 to pick the one that's running rather than an arbitrary one.
11241 - Fix an infinite loop we could hit if we go offline for too long.
11242 - Complain when we hit WSAENOBUFS on recv() or write() too.
11243 Perhaps this will help us hunt the bug.
11244 - If you're not a versioning dirserver, don't put the string
11245 "client-versions \nserver-versions \n" in your network-status.
11246 - Lower the minimum required number of file descriptors to 1000,
11247 so we can have some overhead for Valgrind on Linux, where the
11248 default ulimit -n is 1024.
11251 - Add tor.dizum.com as the fifth authoritative directory server.
11252 - Add a new config option FetchUselessDescriptors, off by default,
11253 for when you plan to run "exitlist" on your client and you want
11254 to know about even the non-running descriptors.
11257 Changes in version 0.1.1.17-rc - 2006-03-28
11259 - Clients and servers since 0.1.1.10-alpha have been expiring
11260 connections whenever they are idle for 5 minutes and they *do*
11261 have circuits on them. Oops. With this new version, clients will
11262 discard their previous entry guard choices and avoid choosing
11263 entry guards running these flawed versions.
11264 - Fix memory leak when uncompressing concatenated zlib streams. This
11265 was causing substantial leaks over time on Tor servers.
11266 - The v1 directory was including servers as much as 48 hours old,
11267 because that's how the new routerlist->routers works. Now only
11268 include them if they're 20 hours old or less.
11271 - Resume building on irix64, netbsd 2.0, etc.
11272 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
11274 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
11275 and it is confusing some users.
11276 - Mirrors stop caching the v1 directory so often.
11277 - Make the max number of old descriptors that a cache will hold
11278 rise with the number of directory authorities, so we can scale.
11279 - Change our win32 uname() hack to be more forgiving about what
11280 win32 versions it thinks it's found.
11283 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
11285 - When the controller's *setconf commands fail, collect an error
11286 message in a string and hand it back to the controller.
11287 - Make the v2 dir's "Fast" flag based on relative capacity, just
11288 like "Stable" is based on median uptime. Name everything in the
11289 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
11290 - Log server fingerprint on startup, so new server operators don't
11291 have to go hunting around their filesystem for it.
11292 - Return a robots.txt on our dirport to discourage google indexing.
11293 - Let the controller ask for GETINFO dir/status/foo so it can ask
11294 directly rather than connecting to the dir port. Only works when
11295 dirport is set for now.
11297 o New config options rather than constants in the code:
11298 - SocksTimeout: How long do we let a socks connection wait
11299 unattached before we fail it?
11300 - CircuitBuildTimeout: Cull non-open circuits that were born
11301 at least this many seconds ago.
11302 - CircuitIdleTimeout: Cull open clean circuits that were born
11303 at least this many seconds ago.
11306 Changes in version 0.1.1.16-rc - 2006-03-18
11307 o Bugfixes on 0.1.1.15-rc:
11308 - Fix assert when the controller asks to attachstream a connect-wait
11309 or resolve-wait stream.
11310 - Now do address rewriting when the controller asks us to attach
11311 to a particular circuit too. This will let Blossom specify
11312 "moria2.exit" without having to learn what moria2's IP address is.
11313 - Make the "tor --verify-config" command-line work again, so people
11314 can automatically check if their torrc will parse.
11315 - Authoritative dirservers no longer require an open connection from
11316 a server to consider him "reachable". We need this change because
11317 when we add new auth dirservers, old servers won't know not to
11319 - Let Tor build on Sun CC again.
11320 - Fix an off-by-one buffer size in dirserv.c that magically never
11321 hit our three authorities but broke sjmurdoch's own tor network.
11322 - If we as a directory mirror don't know of any v1 directory
11323 authorities, then don't try to cache any v1 directories.
11324 - Stop warning about unknown servers in our family when they are
11325 given as hex digests.
11326 - Stop complaining as quickly to the server operator that he
11327 hasn't registered his nickname/key binding.
11328 - Various cleanups so we can add new V2 Auth Dirservers.
11329 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
11330 reflect the updated flags in our v2 dir protocol.
11331 - Resume allowing non-printable characters for exit streams (both
11332 for connecting and for resolving). Now we tolerate applications
11333 that don't follow the RFCs. But continue to block malformed names
11336 o Bugfixes on 0.1.0.x:
11337 - Fix assert bug in close_logs(): when we close and delete logs,
11338 remove them all from the global "logfiles" list.
11339 - Fix minor integer overflow in calculating when we expect to use up
11340 our bandwidth allocation before hibernating.
11341 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
11342 there are multiple SSLs installed with different versions.
11343 - When we try to be a server and Address is not explicitly set and
11344 our hostname resolves to a private IP address, try to use an
11345 interface address if it has a public address. Now Windows machines
11346 that think of themselves as localhost can work by default.
11349 - Let the controller ask for GETINFO dir/server/foo so it can ask
11350 directly rather than connecting to the dir port.
11351 - Let the controller tell us about certain router descriptors
11352 that it doesn't want Tor to use in circuits. Implement
11353 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
11354 - New config option SafeSocks to reject all application connections
11355 using unsafe socks protocols. Defaults to off.
11358 Changes in version 0.1.1.15-rc - 2006-03-11
11359 o Bugfixes and cleanups:
11360 - When we're printing strings from the network, don't try to print
11361 non-printable characters. This protects us against shell escape
11362 sequence exploits, and also against attacks to fool humans into
11363 misreading their logs.
11364 - Fix a bug where Tor would fail to establish any connections if you
11365 left it off for 24 hours and then started it: we were happy with
11366 the obsolete network statuses, but they all referred to router
11367 descriptors that were too old to fetch, so we ended up with no
11368 valid router descriptors.
11369 - Fix a seg fault in the controller's "getinfo orconn-status"
11370 command while listing status on incoming handshaking connections.
11371 Introduce a status name "NEW" for these connections.
11372 - If we get a linelist or linelist_s config option from the torrc
11373 (e.g. ExitPolicy) and it has no value, warn and skip rather than
11374 silently resetting it to its default.
11375 - Don't abandon entry guards until they've been down or gone for
11377 - Cleaner and quieter log messages.
11380 - New controller signal NEWNYM that makes new application requests
11381 use clean circuits.
11382 - Add a new circuit purpose 'controller' to let the controller ask
11383 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
11384 controller command to let you specify the purpose if you're
11385 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
11386 command to let you change a circuit's purpose after it's been
11388 - Accept "private:*" in routerdesc exit policies; not generated yet
11389 because older Tors do not understand it.
11390 - Add BSD-style contributed startup script "rc.subr" from Peter
11394 Changes in version 0.1.1.14-alpha - 2006-02-20
11395 o Bugfixes on 0.1.1.x:
11396 - Don't die if we ask for a stdout or stderr log (even implicitly)
11397 and we're set to RunAsDaemon -- just warn.
11398 - We still had a few bugs in the OR connection rotation code that
11399 caused directory servers to slowly aggregate connections to other
11400 fast Tor servers. This time for sure!
11401 - Make log entries on Win32 include the name of the function again.
11402 - We were treating a pair of exit policies if they were equal even
11403 if one said accept and the other said reject -- causing us to
11404 not always publish a new descriptor since we thought nothing
11406 - Retry pending server downloads as well as pending networkstatus
11407 downloads when we unexpectedly get a socks request.
11408 - We were ignoring the IS_FAST flag in the directory status,
11409 meaning we were willing to pick trivial-bandwidth nodes for "fast"
11411 - If the controller's SAVECONF command fails (e.g. due to file
11412 permissions), let the controller know that it failed.
11415 - If we're trying to be a Tor server and running Windows 95/98/ME
11416 as a server, explain that we'll likely crash.
11417 - When we're a server, a client asks for an old-style directory,
11418 and our write bucket is empty, don't give it to him. This way
11419 small servers can continue to serve the directory *sometimes*,
11420 without getting overloaded.
11421 - Compress exit policies even more -- look for duplicate lines
11423 - Clients now honor the "guard" flag in the router status when
11424 picking entry guards, rather than looking at is_fast or is_stable.
11425 - Retain unrecognized lines in $DATADIR/state file, so that we can
11426 be forward-compatible.
11427 - Generate 18.0.0.0/8 address policy format in descs when we can;
11428 warn when the mask is not reducible to a bit-prefix.
11429 - Let the user set ControlListenAddress in the torrc. This can be
11430 dangerous, but there are some cases (like a secured LAN) where it
11432 - Split ReachableAddresses into ReachableDirAddresses and
11433 ReachableORAddresses, so we can restrict Dir conns to port 80
11434 and OR conns to port 443.
11435 - Now we can target arch and OS in rpm builds (contributed by
11436 Phobos). Also make the resulting dist-rpm filename match the
11438 - New config options to help controllers: FetchServerDescriptors
11439 and FetchHidServDescriptors for whether to fetch server
11440 info and hidserv info or let the controller do it, and
11441 PublishServerDescriptor and PublishHidServDescriptors.
11442 - Also let the controller set the __AllDirActionsPrivate config
11443 option if you want all directory fetches/publishes to happen via
11444 Tor (it assumes your controller bootstraps your circuits).
11447 Changes in version 0.1.0.17 - 2006-02-17
11448 o Crash bugfixes on 0.1.0.x:
11449 - When servers with a non-zero DirPort came out of hibernation,
11450 sometimes they would trigger an assert.
11452 o Other important bugfixes:
11453 - On platforms that don't have getrlimit (like Windows), we were
11454 artificially constraining ourselves to a max of 1024
11455 connections. Now just assume that we can handle as many as 15000
11456 connections. Hopefully this won't cause other problems.
11458 o Backported features:
11459 - When we're a server, a client asks for an old-style directory,
11460 and our write bucket is empty, don't give it to him. This way
11461 small servers can continue to serve the directory *sometimes*,
11462 without getting overloaded.
11463 - Whenever you get a 503 in response to a directory fetch, try
11464 once more. This will become important once servers start sending
11465 503's whenever they feel busy.
11466 - Fetch a new directory every 120 minutes, not every 40 minutes.
11467 Now that we have hundreds of thousands of users running the old
11468 directory algorithm, it's starting to hurt a lot.
11469 - Bump up the period for forcing a hidden service descriptor upload
11470 from 20 minutes to 1 hour.
11473 Changes in version 0.1.1.13-alpha - 2006-02-09
11474 o Crashes in 0.1.1.x:
11475 - When you tried to setconf ORPort via the controller, Tor would
11476 crash. So people using TorCP to become a server were sad.
11477 - Solve (I hope) the stack-smashing bug that we were seeing on fast
11478 servers. The problem appears to be something do with OpenSSL's
11479 random number generation, or how we call it, or something. Let me
11480 know if the crashes continue.
11481 - Turn crypto hardware acceleration off by default, until we find
11482 somebody smart who can test it for us. (It appears to produce
11483 seg faults in at least some cases.)
11484 - Fix a rare assert error when we've tried all intro points for
11485 a hidden service and we try fetching the service descriptor again:
11486 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
11489 - Fix a major load balance bug: we were round-robining in 16 KB
11490 chunks, and servers with bandwidthrate of 20 KB, while downloading
11491 a 600 KB directory, would starve their other connections. Now we
11492 try to be a bit more fair.
11493 - Dir authorities and mirrors were never expiring the newest
11494 descriptor for each server, causing memory and directory bloat.
11495 - Fix memory-bloating and connection-bloating bug on servers: We
11496 were never closing any connection that had ever had a circuit on
11497 it, because we were checking conn->n_circuits == 0, yet we had a
11498 bug that let it go negative.
11499 - Make Tor work using squid as your http proxy again -- squid
11500 returns an error if you ask for a URL that's too long, and it uses
11501 a really generic error message. Plus, many people are behind a
11502 transparent squid so they don't even realize it.
11503 - On platforms that don't have getrlimit (like Windows), we were
11504 artificially constraining ourselves to a max of 1024
11505 connections. Now just assume that we can handle as many as 15000
11506 connections. Hopefully this won't cause other problems.
11507 - Add a new config option ExitPolicyRejectPrivate which defaults to
11508 1. This means all exit policies will begin with rejecting private
11509 addresses, unless the server operator explicitly turns it off.
11512 - Clients no longer download descriptors for non-running
11514 - Before we add new directory authorities, we should make it
11515 clear that only v1 authorities should receive/publish hidden
11516 service descriptors.
11519 - As soon as we've fetched some more directory info, immediately
11520 try to download more server descriptors. This way we don't have
11521 a 10 second pause during initial bootstrapping.
11522 - Remove even more loud log messages that the server operator can't
11524 - When we're running an obsolete or un-recommended version, make
11525 the log message more clear about what the problem is and what
11526 versions *are* still recommended.
11527 - Provide a more useful warn message when our onion queue gets full:
11528 the CPU is too slow or the exit policy is too liberal.
11529 - Don't warn when we receive a 503 from a dirserver/cache -- this
11530 will pave the way for them being able to refuse if they're busy.
11531 - When we fail to bind a listener, try to provide a more useful
11532 log message: e.g., "Is Tor already running?"
11533 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
11534 Goldberg can prove things about our handshake protocol more
11536 - MaxConn has been obsolete for a while now. Document the ConnLimit
11537 config option, which is a *minimum* number of file descriptors
11538 that must be available else Tor refuses to start.
11539 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
11540 if you log to syslog and want something other than LOG_DAEMON.
11541 - Make dirservers generate a separate "guard" flag to mean,
11542 "would make a good entry guard". Make clients parse it and vote
11543 on it. Not used by clients yet.
11544 - Implement --with-libevent-dir option to ./configure. Also, improve
11545 search techniques to find libevent, and use those for openssl too.
11546 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
11547 - Only start testing reachability once we've established a
11548 circuit. This will make startup on dirservers less noisy.
11549 - Don't try to upload hidden service descriptors until we have
11550 established a circuit.
11551 - Fix the controller's "attachstream 0" command to treat conn like
11552 it just connected, doing address remapping, handling .exit and
11553 .onion idioms, and so on. Now we're more uniform in making sure
11554 that the controller hears about new and closing connections.
11557 Changes in version 0.1.1.12-alpha - 2006-01-11
11558 o Bugfixes on 0.1.1.x:
11559 - The fix to close duplicate server connections was closing all
11560 Tor client connections if they didn't establish a circuit
11561 quickly enough. Oops.
11562 - Fix minor memory issue (double-free) that happened on exit.
11564 o Bugfixes on 0.1.0.x:
11565 - Tor didn't warn when it failed to open a log file.
11568 Changes in version 0.1.1.11-alpha - 2006-01-10
11569 o Crashes in 0.1.1.x:
11570 - Include all the assert/crash fixes from 0.1.0.16.
11571 - If you start Tor and then quit very quickly, there were some
11572 races that tried to free things that weren't allocated yet.
11573 - Fix a rare memory stomp if you're running hidden services.
11574 - Fix segfault when specifying DirServer in config without nickname.
11575 - Fix a seg fault when you finish connecting to a server but at
11576 that moment you dump his server descriptor.
11577 - Extendcircuit and Attachstream controller commands would
11578 assert/crash if you don't give them enough arguments.
11579 - Fix an assert error when we're out of space in the connection_list
11580 and we try to post a hidden service descriptor (reported by weasel).
11581 - If you specify a relative torrc path and you set RunAsDaemon in
11582 your torrc, then it chdir()'s to the new directory. If you HUP,
11583 it tries to load the new torrc location, fails, and exits.
11584 The fix: no longer allow a relative path to torrc using -f.
11587 - Implement "entry guards": automatically choose a handful of entry
11588 nodes and stick with them for all circuits. Only pick new guards
11589 when the ones you have are unsuitable, and if the old guards
11590 become suitable again, switch back. This will increase security
11591 dramatically against certain end-point attacks. The EntryNodes
11592 config option now provides some hints about which entry guards you
11593 want to use most; and StrictEntryNodes means to only use those.
11594 - New directory logic: download by descriptor digest, not by
11595 fingerprint. Caches try to download all listed digests from
11596 authorities; clients try to download "best" digests from caches.
11597 This avoids partitioning and isolating attacks better.
11598 - Make the "stable" router flag in network-status be the median of
11599 the uptimes of running valid servers, and make clients pay
11600 attention to the network-status flags. Thus the cutoff adapts
11601 to the stability of the network as a whole, making IRC, IM, etc
11602 connections more reliable.
11605 - Tor servers with dynamic IP addresses were needing to wait 18
11606 hours before they could start doing reachability testing using
11607 the new IP address and ports. This is because they were using
11608 the internal descriptor to learn what to test, yet they were only
11609 rebuilding the descriptor once they decided they were reachable.
11610 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
11611 to download certain server descriptors, throw them away, and then
11612 fetch them again after 30 minutes. Now mirrors throw away these
11613 server descriptors so clients can't get them.
11614 - We were leaving duplicate connections to other ORs open for a week,
11615 rather than closing them once we detect a duplicate. This only
11616 really affected authdirservers, but it affected them a lot.
11617 - Spread the authdirservers' reachability testing over the entire
11618 testing interval, so we don't try to do 500 TLS's at once every
11622 - If the network is down, and we try to connect to a conn because
11623 we have a circuit in mind, and we timeout (30 seconds) because the
11624 network never answers, we were expiring the circuit, but we weren't
11625 obsoleting the connection or telling the entry_guards functions.
11626 - Some Tor servers process billions of cells per day. These statistics
11627 need to be uint64_t's.
11628 - Check for integer overflows in more places, when adding elements
11629 to smartlists. This could possibly prevent a buffer overflow
11630 on malicious huge inputs. I don't see any, but I haven't looked
11632 - ReachableAddresses kept growing new "reject *:*" lines on every
11634 - When you "setconf log" via the controller, it should remove all
11635 logs. We were automatically adding back in a "log notice stdout".
11636 - Newly bootstrapped Tor networks couldn't establish hidden service
11637 circuits until they had nodes with high uptime. Be more tolerant.
11638 - We were marking servers down when they could not answer every piece
11639 of the directory request we sent them. This was far too harsh.
11640 - Fix the torify (tsocks) config file to not use Tor for localhost
11642 - Directory authorities now go to the proper authority when asking for
11643 a networkstatus, even when they want a compressed one.
11644 - Fix a harmless bug that was causing Tor servers to log
11645 "Got an end because of misc error, but we're not an AP. Closing."
11646 - Authorities were treating their own descriptor changes as cosmetic,
11647 meaning the descriptor available in the network-status and the
11648 descriptor that clients downloaded were different.
11649 - The OS X installer was adding a symlink for tor_resolve but
11650 the binary was called tor-resolve (reported by Thomas Hardly).
11651 - Workaround a problem with some http proxies where they refuse GET
11652 requests that specify "Content-Length: 0" (reported by Adrian).
11653 - Fix wrong log message when you add a "HiddenServiceNodes" config
11654 line without any HiddenServiceDir line (reported by Chris Thomas).
11657 - Write the TorVersion into the state file so we have a prayer of
11658 keeping forward and backward compatibility.
11659 - Revive the FascistFirewall config option rather than eliminating it:
11660 now it's a synonym for ReachableAddresses *:80,*:443.
11661 - Clients choose directory servers from the network status lists,
11662 not from their internal list of router descriptors. Now they can
11663 go to caches directly rather than needing to go to authorities
11665 - Directory authorities ignore router descriptors that have only
11666 cosmetic differences: do this for 0.1.0.x servers now too.
11667 - Add a new flag to network-status indicating whether the server
11668 can answer v2 directory requests too.
11669 - Authdirs now stop whining so loudly about bad descriptors that
11670 they fetch from other dirservers. So when there's a log complaint,
11671 it's for sure from a freshly uploaded descriptor.
11672 - Reduce memory requirements in our structs by changing the order
11674 - There used to be two ways to specify your listening ports in a
11675 server descriptor: on the "router" line and with a separate "ports"
11676 line. Remove support for the "ports" line.
11677 - New config option "AuthDirRejectUnlisted" for auth dirservers as
11678 a panic button: if we get flooded with unusable servers we can
11679 revert to only listing servers in the approved-routers file.
11680 - Auth dir servers can now mark a fingerprint as "!reject" or
11681 "!invalid" in the approved-routers file (as its nickname), to
11682 refuse descriptors outright or include them but marked as invalid.
11683 - Servers store bandwidth history across restarts/crashes.
11684 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
11685 get a better idea of why their circuits failed. Not used yet.
11686 - Directory mirrors now cache up to 16 unrecognized network-status
11687 docs. Now we can add new authdirservers and they'll be cached too.
11688 - When picking a random directory, prefer non-authorities if any
11690 - New controller option "getinfo desc/all-recent" to fetch the
11691 latest server descriptor for every router that Tor knows about.
11694 Changes in version 0.1.0.16 - 2006-01-02
11695 o Crash bugfixes on 0.1.0.x:
11696 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
11697 corrupting the heap, losing FDs, or crashing when we need to resize
11698 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
11699 - It turns out sparc64 platforms crash on unaligned memory access
11700 too -- so detect and avoid this.
11701 - Handle truncated compressed data correctly (by detecting it and
11703 - Fix possible-but-unlikely free(NULL) in control.c.
11704 - When we were closing connections, there was a rare case that
11705 stomped on memory, triggering seg faults and asserts.
11706 - Avoid potential infinite recursion when building a descriptor. (We
11707 don't know that it ever happened, but better to fix it anyway.)
11708 - We were neglecting to unlink marked circuits from soon-to-close OR
11709 connections, which caused some rare scribbling on freed memory.
11710 - Fix a memory stomping race bug when closing the joining point of two
11711 rendezvous circuits.
11712 - Fix an assert in time parsing found by Steven Murdoch.
11714 o Other bugfixes on 0.1.0.x:
11715 - When we're doing reachability testing, provide more useful log
11716 messages so the operator knows what to expect.
11717 - Do not check whether DirPort is reachable when we are suppressing
11718 advertising it because of hibernation.
11719 - When building with -static or on Solaris, we sometimes needed -ldl.
11720 - When we're deciding whether a stream has enough circuits around
11721 that can handle it, count the freshly dirty ones and not the ones
11722 that are so dirty they won't be able to handle it.
11723 - When we're expiring old circuits, we had a logic error that caused
11724 us to close new rendezvous circuits rather than old ones.
11725 - Give a more helpful log message when you try to change ORPort via
11726 the controller: you should upgrade Tor if you want that to work.
11727 - We were failing to parse Tor versions that start with "Tor ".
11728 - Tolerate faulty streams better: when a stream fails for reason
11729 exitpolicy, stop assuming that the router is lying about his exit
11730 policy. When a stream fails for reason misc, allow it to retry just
11731 as if it was resolvefailed. When a stream has failed three times,
11732 reset its failure count so we can try again and get all three tries.
11735 Changes in version 0.1.1.10-alpha - 2005-12-11
11736 o Correctness bugfixes on 0.1.0.x:
11737 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
11738 corrupting the heap, losing FDs, or crashing when we need to resize
11739 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
11740 - Stop doing the complex voodoo overkill checking for insecure
11741 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
11742 - When we were closing connections, there was a rare case that
11743 stomped on memory, triggering seg faults and asserts.
11744 - We were neglecting to unlink marked circuits from soon-to-close OR
11745 connections, which caused some rare scribbling on freed memory.
11746 - When we're deciding whether a stream has enough circuits around
11747 that can handle it, count the freshly dirty ones and not the ones
11748 that are so dirty they won't be able to handle it.
11749 - Recover better from TCP connections to Tor servers that are
11750 broken but don't tell you (it happens!); and rotate TLS
11751 connections once a week.
11752 - When we're expiring old circuits, we had a logic error that caused
11753 us to close new rendezvous circuits rather than old ones.
11754 - Fix a scary-looking but apparently harmless bug where circuits
11755 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
11756 servers, and never switch to state CIRCUIT_STATE_OPEN.
11757 - When building with -static or on Solaris, we sometimes needed to
11759 - Give a useful message when people run Tor as the wrong user,
11760 rather than telling them to start chowning random directories.
11761 - We were failing to inform the controller about new .onion streams.
11763 o Security bugfixes on 0.1.0.x:
11764 - Refuse server descriptors if the fingerprint line doesn't match
11765 the included identity key. Tor doesn't care, but other apps (and
11766 humans) might actually be trusting the fingerprint line.
11767 - We used to kill the circuit when we receive a relay command we
11768 don't recognize. Now we just drop it.
11769 - Start obeying our firewall options more rigorously:
11770 . If we can't get to a dirserver directly, try going via Tor.
11771 . Don't ever try to connect (as a client) to a place our
11772 firewall options forbid.
11773 . If we specify a proxy and also firewall options, obey the
11774 firewall options even when we're using the proxy: some proxies
11775 can only proxy to certain destinations.
11776 - Fix a bug found by Lasse Overlier: when we were making internal
11777 circuits (intended to be cannibalized later for rendezvous and
11778 introduction circuits), we were picking them so that they had
11779 useful exit nodes. There was no need for this, and it actually
11780 aids some statistical attacks.
11781 - Start treating internal circuits and exit circuits separately.
11782 It's important to keep them separate because internal circuits
11783 have their last hops picked like middle hops, rather than like
11784 exit hops. So exiting on them will break the user's expectations.
11786 o Bugfixes on 0.1.1.x:
11787 - Take out the mis-feature where we tried to detect IP address
11788 flapping for people with DynDNS, and chose not to upload a new
11789 server descriptor sometimes.
11790 - Try to be compatible with OpenSSL 0.9.6 again.
11791 - Log fix: when the controller is logging about .onion addresses,
11792 sometimes it didn't include the ".onion" part of the address.
11793 - Don't try to modify options->DirServers internally -- if the
11794 user didn't specify any, just add the default ones directly to
11795 the trusted dirserver list. This fixes a bug where people running
11796 controllers would use SETCONF on some totally unrelated config
11797 option, and Tor would start yelling at them about changing their
11799 - Let the controller's redirectstream command specify a port, in
11800 case the controller wants to change that too.
11801 - When we requested a pile of server descriptors, we sometimes
11802 accidentally launched a duplicate request for the first one.
11803 - Bugfix for trackhostexits: write down the fingerprint of the
11804 chosen exit, not its nickname, because the chosen exit might not
11806 - When parsing foo.exit, if foo is unknown, and we are leaving
11807 circuits unattached, set the chosen_exit field and leave the
11808 address empty. This matters because controllers got confused
11810 - Directory authorities no longer try to download server
11811 descriptors that they know they will reject.
11813 o Features and updates:
11814 - Replace balanced trees with hash tables: this should make stuff
11815 significantly faster.
11816 - Resume using the AES counter-mode implementation that we ship,
11817 rather than OpenSSL's. Ours is significantly faster.
11818 - Many other CPU and memory improvements.
11819 - Add a new config option FastFirstHopPK (on by default) so clients
11820 do a trivial crypto handshake for their first hop, since TLS has
11821 already taken care of confidentiality and authentication.
11822 - Add a new config option TestSocks so people can see if their
11823 applications are using socks4, socks4a, socks5-with-ip, or
11824 socks5-with-hostname. This way they don't have to keep mucking
11825 with tcpdump and wondering if something got cached somewhere.
11826 - Warn when listening on a public address for socks. I suspect a
11827 lot of people are setting themselves up as open socks proxies,
11828 and they have no idea that jerks on the Internet are using them,
11829 since they simply proxy the traffic into the Tor network.
11830 - Add "private:*" as an alias in configuration for policies. Now
11831 you can simplify your exit policy rather than needing to list
11832 every single internal or nonroutable network space.
11833 - Add a new controller event type that allows controllers to get
11834 all server descriptors that were uploaded to a router in its role
11835 as authoritative dirserver.
11836 - Start shipping socks-extensions.txt, tor-doc-unix.html,
11837 tor-doc-server.html, and stylesheet.css in the tarball.
11838 - Stop shipping tor-doc.html in the tarball.
11841 Changes in version 0.1.1.9-alpha - 2005-11-15
11842 o Usability improvements:
11843 - Start calling it FooListenAddress rather than FooBindAddress,
11844 since few of our users know what it means to bind an address
11846 - Reduce clutter in server logs. We're going to try to make
11847 them actually usable now. New config option ProtocolWarnings that
11848 lets you hear about how _other Tors_ are breaking the protocol. Off
11850 - Divide log messages into logging domains. Once we put some sort
11851 of interface on this, it will let people looking at more verbose
11852 log levels specify the topics they want to hear more about.
11853 - Make directory servers return better http 404 error messages
11854 instead of a generic "Servers unavailable".
11855 - Check for even more Windows version flags when writing the platform
11856 string in server descriptors, and note any we don't recognize.
11857 - Clean up more of the OpenSSL memory when exiting, so we can detect
11858 memory leaks better.
11859 - Make directory authorities be non-versioning, non-naming by
11860 default. Now we can add new directory servers without requiring
11861 their operators to pay close attention.
11862 - When logging via syslog, include the pid whenever we provide
11863 a log entry. Suggested by Todd Fries.
11865 o Performance improvements:
11866 - Directory servers now silently throw away new descriptors that
11867 haven't changed much if the timestamps are similar. We do this to
11868 tolerate older Tor servers that upload a new descriptor every 15
11869 minutes. (It seemed like a good idea at the time.)
11870 - Inline bottleneck smartlist functions; use fast versions by default.
11871 - Add a "Map from digest to void*" abstraction digestmap_t so we
11872 can do less hex encoding/decoding. Use it in router_get_by_digest()
11873 to resolve a performance bottleneck.
11874 - Allow tor_gzip_uncompress to extract as much as possible from
11875 truncated compressed data. Try to extract as many
11876 descriptors as possible from truncated http responses (when
11877 DIR_PURPOSE_FETCH_ROUTERDESC).
11878 - Make circ->onionskin a pointer, not a static array. moria2 was using
11879 125000 circuit_t's after it had been up for a few weeks, which
11880 translates to 20+ megs of wasted space.
11881 - The private half of our EDH handshake keys are now chosen out
11882 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
11884 o Security improvements:
11885 - Start making directory caches retain old routerinfos, so soon
11886 clients can start asking by digest of descriptor rather than by
11887 fingerprint of server.
11888 - Add half our entropy from RAND_poll in OpenSSL. This knows how
11889 to use egd (if present), openbsd weirdness (if present), vms/os2
11890 weirdness (if we ever port there), and more in the future.
11892 o Bugfixes on 0.1.0.x:
11893 - Do round-robin writes of at most 16 kB per write. This might be
11894 more fair on loaded Tor servers, and it might resolve our Windows
11895 crash bug. It might also slow things down.
11896 - Our TLS handshakes were generating a single public/private
11897 keypair for the TLS context, rather than making a new one for
11898 each new connections. Oops. (But we were still rotating them
11899 periodically, so it's not so bad.)
11900 - When we were cannibalizing a circuit with a particular exit
11901 node in mind, we weren't checking to see if that exit node was
11902 already present earlier in the circuit. Oops.
11903 - When a Tor server's IP changes (e.g. from a dyndns address),
11904 upload a new descriptor so clients will learn too.
11905 - Really busy servers were keeping enough circuits open on stable
11906 connections that they were wrapping around the circuit_id
11907 space. (It's only two bytes.) This exposed a bug where we would
11908 feel free to reuse a circuit_id even if it still exists but has
11909 been marked for close. Try to fix this bug. Some bug remains.
11910 - If we would close a stream early (e.g. it asks for a .exit that
11911 we know would refuse it) but the LeaveStreamsUnattached config
11912 option is set by the controller, then don't close it.
11914 o Bugfixes on 0.1.1.8-alpha:
11915 - Fix a big pile of memory leaks, some of them serious.
11916 - Do not try to download a routerdesc if we would immediately reject
11918 - Resume inserting a newline between all router descriptors when
11919 generating (old style) signed directories, since our spec says
11921 - When providing content-type application/octet-stream for
11922 server descriptors using .z, we were leaving out the
11923 content-encoding header. Oops. (Everything tolerated this just
11924 fine, but that doesn't mean we need to be part of the problem.)
11925 - Fix a potential seg fault in getconf and getinfo using version 1
11926 of the controller protocol.
11927 - Avoid crash: do not check whether DirPort is reachable when we
11928 are suppressing it because of hibernation.
11929 - Make --hash-password not crash on exit.
11932 Changes in version 0.1.1.8-alpha - 2005-10-07
11933 o New features (major):
11934 - Clients don't download or use the directory anymore. Now they
11935 download and use network-statuses from the trusted dirservers,
11936 and fetch individual server descriptors as needed from mirrors.
11937 See dir-spec.txt for all the gory details.
11938 - Be more conservative about whether to advertise our DirPort.
11939 The main change is to not advertise if we're running at capacity
11940 and either a) we could hibernate or b) our capacity is low and
11941 we're using a default DirPort.
11942 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
11944 o New features (minor):
11945 - Try to be smart about when to retry network-status and
11946 server-descriptor fetches. Still needs some tuning.
11947 - Stop parsing, storing, or using running-routers output (but
11948 mirrors still cache and serve it).
11949 - Consider a threshold of versioning dirservers (dirservers who have
11950 an opinion about which Tor versions are still recommended) before
11951 deciding whether to warn the user that he's obsolete.
11952 - Dirservers can now reject/invalidate by key and IP, with the
11953 config options "AuthDirInvalid" and "AuthDirReject". This is
11954 useful since currently we automatically list servers as running
11955 and usable even if we know they're jerks.
11956 - Provide dire warnings to any users who set DirServer; move it out
11957 of torrc.sample and into torrc.complete.
11958 - Add MyFamily to torrc.sample in the server section.
11959 - Add nicknames to the DirServer line, so we can refer to them
11960 without requiring all our users to memorize their IP addresses.
11961 - When we get an EOF or a timeout on a directory connection, note
11962 how many bytes of serverdesc we are dropping. This will help
11963 us determine whether it is smart to parse incomplete serverdesc
11965 - Add a new function to "change pseudonyms" -- that is, to stop
11966 using any currently-dirty circuits for new streams, so we don't
11967 link new actions to old actions. Currently it's only called on
11968 HUP (or SIGNAL RELOAD).
11969 - On sighup, if UseHelperNodes changed to 1, use new circuits.
11970 - Start using RAND_bytes rather than RAND_pseudo_bytes from
11971 OpenSSL. Also, reseed our entropy every hour, not just at
11972 startup. And entropy in 512-bit chunks, not 160-bit chunks.
11974 o Fixes on 0.1.1.7-alpha:
11975 - Nobody ever implemented EVENT_ADDRMAP for control protocol
11976 version 0, so don't let version 0 controllers ask for it.
11977 - If you requested something with too many newlines via the
11978 v1 controller protocol, you could crash tor.
11979 - Fix a number of memory leaks, including some pretty serious ones.
11980 - Re-enable DirPort testing again, so Tor servers will be willing
11981 to advertise their DirPort if it's reachable.
11982 - On TLS handshake, only check the other router's nickname against
11983 its expected nickname if is_named is set.
11985 o Fixes forward-ported from 0.1.0.15:
11986 - Don't crash when we don't have any spare file descriptors and we
11987 try to spawn a dns or cpu worker.
11988 - Make the numbers in read-history and write-history into uint64s,
11989 so they don't overflow and publish negatives in the descriptor.
11991 o Fixes on 0.1.0.x:
11992 - For the OS X package's modified privoxy config file, comment
11993 out the "logfile" line so we don't log everything passed
11995 - We were whining about using socks4 or socks5-with-local-lookup
11996 even when it's an IP in the "virtual" range we designed exactly
11998 - We were leaking some memory every time the client changes IPs.
11999 - Never call free() on tor_malloc()d memory. This will help us
12000 use dmalloc to detect memory leaks.
12001 - Check for named servers when looking them up by nickname;
12002 warn when we'recalling a non-named server by its nickname;
12003 don't warn twice about the same name.
12004 - Try to list MyFamily elements by key, not by nickname, and warn
12005 if we've not heard of the server.
12006 - Make windows platform detection (uname equivalent) smarter.
12007 - It turns out sparc64 doesn't like unaligned access either.
12010 Changes in version 0.1.0.15 - 2005-09-23
12011 o Bugfixes on 0.1.0.x:
12012 - Reject ports 465 and 587 (spam targets) in default exit policy.
12013 - Don't crash when we don't have any spare file descriptors and we
12014 try to spawn a dns or cpu worker.
12015 - Get rid of IgnoreVersion undocumented config option, and make us
12016 only warn, never exit, when we're running an obsolete version.
12017 - Don't try to print a null string when your server finds itself to
12018 be unreachable and the Address config option is empty.
12019 - Make the numbers in read-history and write-history into uint64s,
12020 so they don't overflow and publish negatives in the descriptor.
12021 - Fix a minor memory leak in smartlist_string_remove().
12022 - We were only allowing ourselves to upload a server descriptor at
12023 most every 20 minutes, even if it changed earlier than that.
12024 - Clean up log entries that pointed to old URLs.
12027 Changes in version 0.1.1.7-alpha - 2005-09-14
12028 o Fixes on 0.1.1.6-alpha:
12029 - Exit servers were crashing when people asked them to make a
12030 connection to an address not in their exit policy.
12031 - Looking up a non-existent stream for a v1 control connection would
12033 - Fix a seg fault if we ask a dirserver for a descriptor by
12034 fingerprint but he doesn't know about him.
12035 - SETCONF was appending items to linelists, not clearing them.
12036 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
12037 out and refuse the setconf if it would fail.
12038 - Downgrade the dirserver log messages when whining about
12042 - Add Peter Palfrader's check-tor script to tor/contrib/
12043 It lets you easily check whether a given server (referenced by
12044 nickname) is reachable by you.
12045 - Numerous changes to move towards client-side v2 directories. Not
12048 o Fixes on 0.1.0.x:
12049 - If the user gave tor an odd number of command-line arguments,
12050 we were silently ignoring the last one. Now we complain and fail.
12051 [This wins the oldest-bug prize -- this bug has been present since
12052 November 2002, as released in Tor 0.0.0.]
12053 - Do not use unaligned memory access on alpha, mips, or mipsel.
12054 It *works*, but is very slow, so we treat them as if it doesn't.
12055 - Retry directory requests if we fail to get an answer we like
12056 from a given dirserver (we were retrying before, but only if
12057 we fail to connect).
12058 - When writing the RecommendedVersions line, sort them first.
12059 - When the client asked for a rendezvous port that the hidden
12060 service didn't want to provide, we were sending an IP address
12061 back along with the end cell. Fortunately, it was zero. But stop
12063 - Correct "your server is reachable" log entries to indicate that
12064 it was self-testing that told us so.
12067 Changes in version 0.1.1.6-alpha - 2005-09-09
12068 o Fixes on 0.1.1.5-alpha:
12069 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
12070 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
12071 - Fix bug with tor_memmem finding a match at the end of the string.
12072 - Make unit tests run without segfaulting.
12073 - Resolve some solaris x86 compile warnings.
12074 - Handle duplicate lines in approved-routers files without warning.
12075 - Fix bug where as soon as a server refused any requests due to his
12076 exit policy (e.g. when we ask for localhost and he tells us that's
12077 127.0.0.1 and he won't do it), we decided he wasn't obeying his
12078 exit policy using him for any exits.
12079 - Only do openssl hardware accelerator stuff if openssl version is
12082 o New controller features/fixes:
12083 - Add a "RESETCONF" command so you can set config options like
12084 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
12085 a config option in the torrc with no value, then it clears it
12086 entirely (rather than setting it to its default).
12087 - Add a "GETINFO config-file" to tell us where torrc is.
12088 - Avoid sending blank lines when GETINFO replies should be empty.
12089 - Add a QUIT command for the controller (for using it manually).
12090 - Fix a bug in SAVECONF that was adding default dirservers and
12091 other redundant entries to the torrc file.
12093 o Start on the new directory design:
12094 - Generate, publish, cache, serve new network-status format.
12095 - Publish individual descriptors (by fingerprint, by "all", and by
12097 - Publish client and server recommended versions separately.
12098 - Allow tor_gzip_uncompress() to handle multiple concatenated
12099 compressed strings. Serve compressed groups of router
12100 descriptors. The compression logic here could be more
12102 - Distinguish v1 authorities (all currently trusted directories)
12103 from v2 authorities (all trusted directories).
12104 - Change DirServers config line to note which dirs are v1 authorities.
12105 - Add configuration option "V1AuthoritativeDirectory 1" which
12106 moria1, moria2, and tor26 should set.
12107 - Remove option when getting directory cache to see whether they
12108 support running-routers; they all do now. Replace it with one
12109 to see whether caches support v2 stuff.
12112 - Dirservers now do their own external reachability testing of each
12113 Tor server, and only list them as running if they've been found to
12114 be reachable. We also send back warnings to the server's logs if
12115 it uploads a descriptor that we already believe is unreachable.
12116 - Implement exit enclaves: if we know an IP address for the
12117 destination, and there's a running Tor server at that address
12118 which allows exit to the destination, then extend the circuit to
12119 that exit first. This provides end-to-end encryption and end-to-end
12120 authentication. Also, if the user wants a .exit address or enclave,
12121 use 4 hops rather than 3, and cannibalize a general circ for it
12123 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
12124 controller. Also, rotate dns and cpu workers if the controller
12125 changes options that will affect them; and initialize the dns
12126 worker cache tree whether or not we start out as a server.
12127 - Only upload a new server descriptor when options change, 18
12128 hours have passed, uptime is reset, or bandwidth changes a lot.
12129 - Check [X-]Forwarded-For headers in HTTP requests when generating
12130 log messages. This lets people run dirservers (and caches) behind
12131 Apache but still know which IP addresses are causing warnings.
12133 o Config option changes:
12134 - Replace (Fascist)Firewall* config options with a new
12135 ReachableAddresses option that understands address policies.
12136 For example, "ReachableAddresses *:80,*:443"
12137 - Get rid of IgnoreVersion undocumented config option, and make us
12138 only warn, never exit, when we're running an obsolete version.
12139 - Make MonthlyAccountingStart config option truly obsolete now.
12141 o Fixes on 0.1.0.x:
12142 - Reject ports 465 and 587 in the default exit policy, since
12143 people have started using them for spam too.
12144 - It turns out we couldn't bootstrap a network since we added
12145 reachability detection in 0.1.0.1-rc. Good thing the Tor network
12146 has never gone down. Add an AssumeReachable config option to let
12147 servers and dirservers bootstrap. When we're trying to build a
12148 high-uptime or high-bandwidth circuit but there aren't enough
12149 suitable servers, try being less picky rather than simply failing.
12150 - Our logic to decide if the OR we connected to was the right guy
12151 was brittle and maybe open to a mitm for unverified routers.
12152 - We weren't cannibalizing circuits correctly for
12153 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
12154 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
12155 build those from scratch. This should make hidden services faster.
12156 - Predict required circuits better, with an eye toward making hidden
12157 services faster on the service end.
12158 - Retry streams if the exit node sends back a 'misc' failure. This
12159 should result in fewer random failures. Also, after failing
12160 from resolve failed or misc, reset the num failures, so we give
12161 it a fair shake next time we try.
12162 - Clean up the rendezvous warn log msgs, and downgrade some to info.
12163 - Reduce severity on logs about dns worker spawning and culling.
12164 - When we're shutting down and we do something like try to post a
12165 server descriptor or rendezvous descriptor, don't complain that
12166 we seem to be unreachable. Of course we are, we're shutting down.
12167 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
12168 We don't use them yet, but maybe one day our DNS resolver will be
12169 able to discover them.
12170 - Make ContactInfo mandatory for authoritative directory servers.
12171 - Require server descriptors to list IPv4 addresses -- hostnames
12172 are no longer allowed. This also fixes some potential security
12173 problems with people providing hostnames as their address and then
12174 preferentially resolving them to partition users.
12175 - Change log line for unreachability to explicitly suggest /etc/hosts
12176 as the culprit. Also make it clearer what IP address and ports we're
12177 testing for reachability.
12178 - Put quotes around user-supplied strings when logging so users are
12179 more likely to realize if they add bad characters (like quotes)
12181 - Let auth dir servers start without specifying an Address config
12183 - Make unit tests (and other invocations that aren't the real Tor)
12184 run without launching listeners, creating subdirectories, and so on.
12187 Changes in version 0.1.1.5-alpha - 2005-08-08
12188 o Bugfixes included in 0.1.0.14.
12190 o Bugfixes on 0.1.0.x:
12191 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
12192 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
12193 it would silently using ignore the 6668.
12196 Changes in version 0.1.0.14 - 2005-08-08
12197 o Bugfixes on 0.1.0.x:
12198 - Fix the other half of the bug with crypto handshakes
12200 - Fix an assert trigger if you send a 'signal term' via the
12201 controller when it's listening for 'event info' messages.
12204 Changes in version 0.1.1.4-alpha - 2005-08-04
12205 o Bugfixes included in 0.1.0.13.
12208 - Improve tor_gettimeofday() granularity on windows.
12209 - Make clients regenerate their keys when their IP address changes.
12210 - Implement some more GETINFO goodness: expose helper nodes, config
12211 options, getinfo keys.
12214 Changes in version 0.1.0.13 - 2005-08-04
12215 o Bugfixes on 0.1.0.x:
12216 - Fix a critical bug in the security of our crypto handshakes.
12217 - Fix a size_t underflow in smartlist_join_strings2() that made
12218 it do bad things when you hand it an empty smartlist.
12219 - Fix Windows installer to ship Tor license (thanks to Aphex for
12220 pointing out this oversight) and put a link to the doc directory
12222 - Explicitly set no-unaligned-access for sparc: it turns out the
12223 new gcc's let you compile broken code, but that doesn't make it
12227 Changes in version 0.1.1.3-alpha - 2005-07-23
12228 o Bugfixes on 0.1.1.2-alpha:
12229 - Fix a bug in handling the controller's "post descriptor"
12231 - Fix several bugs in handling the controller's "extend circuit"
12233 - Fix a bug in handling the controller's "stream status" event.
12234 - Fix an assert failure if we have a controller listening for
12235 circuit events and we go offline.
12236 - Re-allow hidden service descriptors to publish 0 intro points.
12237 - Fix a crash when generating your hidden service descriptor if
12238 you don't have enough intro points already.
12240 o New features on 0.1.1.2-alpha:
12241 - New controller function "getinfo accounting", to ask how
12242 many bytes we've used in this time period.
12243 - Experimental support for helper nodes: a lot of the risk from
12244 a small static adversary comes because users pick new random
12245 nodes every time they rebuild a circuit. Now users will try to
12246 stick to the same small set of entry nodes if they can. Not
12247 enabled by default yet.
12249 o Bugfixes on 0.1.0.12:
12250 - If you're an auth dir server, always publish your dirport,
12251 even if you haven't yet found yourself to be reachable.
12252 - Fix a size_t underflow in smartlist_join_strings2() that made
12253 it do bad things when you hand it an empty smartlist.
12256 Changes in version 0.1.0.12 - 2005-07-18
12257 o New directory servers:
12258 - tor26 has changed IP address.
12260 o Bugfixes on 0.1.0.x:
12261 - Fix a possible double-free in tor_gzip_uncompress().
12262 - When --disable-threads is set, do not search for or link against
12263 pthreads libraries.
12264 - Don't trigger an assert if an authoritative directory server
12265 claims its dirport is 0.
12266 - Fix bug with removing Tor as an NT service: some people were
12267 getting "The service did not return an error." Thanks to Matt
12271 Changes in version 0.1.1.2-alpha - 2005-07-15
12272 o New directory servers:
12273 - tor26 has changed IP address.
12275 o Bugfixes on 0.1.0.x, crashes/leaks:
12276 - Port the servers-not-obeying-their-exit-policies fix from
12278 - Fix an fd leak in start_daemon().
12279 - On Windows, you can't always reopen a port right after you've
12280 closed it. So change retry_listeners() to only close and re-open
12281 ports that have changed.
12282 - Fix a possible double-free in tor_gzip_uncompress().
12284 o Bugfixes on 0.1.0.x, usability:
12285 - When tor_socketpair() fails in Windows, give a reasonable
12286 Windows-style errno back.
12287 - Let people type "tor --install" as well as "tor -install" when
12289 want to make it an NT service.
12290 - NT service patch from Matt Edman to improve error messages.
12291 - When the controller asks for a config option with an abbreviated
12292 name, give the full name in our response.
12293 - Correct the man page entry on TrackHostExitsExpire.
12294 - Looks like we were never delivering deflated (i.e. compressed)
12295 running-routers lists, even when asked. Oops.
12296 - When --disable-threads is set, do not search for or link against
12297 pthreads libraries.
12299 o Bugfixes on 0.1.1.x:
12300 - Fix a seg fault with autodetecting which controller version is
12304 - New hidden service descriptor format: put a version in it, and
12305 let people specify introduction/rendezvous points that aren't
12306 in "the directory" (which is subjective anyway).
12307 - Allow the DEBUG controller event to work again. Mark certain log
12308 entries as "don't tell this to controllers", so we avoid cycles.
12311 Changes in version 0.1.0.11 - 2005-06-30
12312 o Bugfixes on 0.1.0.x:
12313 - Fix major security bug: servers were disregarding their
12314 exit policies if clients behaved unexpectedly.
12315 - Make OS X init script check for missing argument, so we don't
12316 confuse users who invoke it incorrectly.
12317 - Fix a seg fault in "tor --hash-password foo".
12318 - The MAPADDRESS control command was broken.
12321 Changes in version 0.1.1.1-alpha - 2005-06-29
12323 - Make OS X init script check for missing argument, so we don't
12324 confuse users who invoke it incorrectly.
12325 - Fix a seg fault in "tor --hash-password foo".
12326 - Fix a possible way to DoS dirservers.
12327 - When we complain that your exit policy implicitly allows local or
12328 private address spaces, name them explicitly so operators can
12330 - Make the log message less scary when all the dirservers are
12331 temporarily unreachable.
12332 - We were printing the number of idle dns workers incorrectly when
12336 - Revised controller protocol (version 1) that uses ascii rather
12337 than binary. Add supporting libraries in python and java so you
12338 can use the controller from your applications without caring how
12339 our protocol works.
12340 - Spiffy new support for crypto hardware accelerators. Can somebody
12344 Changes in version 0.0.9.10 - 2005-06-16
12345 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
12346 - Refuse relay cells that claim to have a length larger than the
12347 maximum allowed. This prevents a potential attack that could read
12348 arbitrary memory (e.g. keys) from an exit server's process
12352 Changes in version 0.1.0.10 - 2005-06-14
12353 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
12354 libevent before 1.1a.
12357 Changes in version 0.1.0.9-rc - 2005-06-09
12359 - Reset buf->highwater every time buf_shrink() is called, not just on
12360 a successful shrink. This was causing significant memory bloat.
12361 - Fix buffer overflow when checking hashed passwords.
12362 - Security fix: if seeding the RNG on Win32 fails, quit.
12363 - Allow seeding the RNG on Win32 even when you're not running as
12365 - Disable threading on Solaris too. Something is wonky with it,
12366 cpuworkers, and reentrant libs.
12367 - Reenable the part of the code that tries to flush as soon as an
12368 OR outbuf has a full TLS record available. Perhaps this will make
12369 OR outbufs not grow as huge except in rare cases, thus saving lots
12370 of CPU time plus memory.
12371 - Reject malformed .onion addresses rather then passing them on as
12372 normal web requests.
12373 - Adapt patch from Adam Langley: fix possible memory leak in
12374 tor_lookup_hostname().
12375 - Initialize libevent later in the startup process, so the logs are
12376 already established by the time we start logging libevent warns.
12377 - Use correct errno on win32 if libevent fails.
12378 - Check and warn about known-bad/slow libevent versions.
12379 - Pay more attention to the ClientOnly config option.
12380 - Have torctl.in/tor.sh.in check for location of su binary (needed
12382 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
12383 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
12384 HttpProxyAuthenticator
12385 - Stop warning about sigpipes in the logs. We're going to
12386 pretend that getting these occassionally is normal and fine.
12387 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
12389 installer screens; and don't put stuff into StartupItems unless
12390 the user asks you to.
12391 - Require servers that use the default dirservers to have public IP
12392 addresses. We have too many servers that are configured with private
12393 IPs and their admins never notice the log entries complaining that
12394 their descriptors are being rejected.
12395 - Add OSX uninstall instructions. An actual uninstall script will
12399 Changes in version 0.1.0.8-rc - 2005-05-23
12401 - It turns out that kqueue on OS X 10.3.9 was causing kernel
12402 panics. Disable kqueue on all OS X Tors.
12403 - Fix RPM: remove duplicate line accidentally added to the rpm
12405 - Disable threads on openbsd too, since its gethostaddr is not
12407 - Tolerate libevent 0.8 since it still works, even though it's
12409 - Enable building on Red Hat 9.0 again.
12410 - Allow the middle hop of the testing circuit to be running any
12411 version, now that most of them have the bugfix to let them connect
12412 to unknown servers. This will allow reachability testing to work
12413 even when 0.0.9.7-0.0.9.9 become obsolete.
12414 - Handle relay cells with rh.length too large. This prevents
12415 a potential attack that could read arbitrary memory (maybe even
12416 keys) from the exit server's process.
12417 - We screwed up the dirport reachability testing when we don't yet
12418 have a cached version of the directory. Hopefully now fixed.
12419 - Clean up router_load_single_router() (used by the controller),
12420 so it doesn't seg fault on error.
12421 - Fix a minor memory leak when somebody establishes an introduction
12422 point at your Tor server.
12423 - If a socks connection ends because read fails, don't warn that
12424 you're not sending a socks reply back.
12427 - Add HttpProxyAuthenticator config option too, that works like
12428 the HttpsProxyAuthenticator config option.
12429 - Encode hashed controller passwords in hex instead of base64,
12430 to make it easier to write controllers.
12433 Changes in version 0.1.0.7-rc - 2005-05-17
12435 - Fix a bug in the OS X package installer that prevented it from
12436 installing on Tiger.
12437 - Fix a script bug in the OS X package installer that made it
12438 complain during installation.
12439 - Find libevent even if it's hiding in /usr/local/ and your
12440 CFLAGS and LDFLAGS don't tell you to look there.
12441 - Be able to link with libevent as a shared library (the default
12442 after 1.0d), even if it's hiding in /usr/local/lib and even
12443 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
12444 assuming you're running gcc. Otherwise fail and give a useful
12446 - Fix a bug in the RPM packager: set home directory for _tor to
12447 something more reasonable when first installing.
12448 - Free a minor amount of memory that is still reachable on exit.
12451 Changes in version 0.1.0.6-rc - 2005-05-14
12453 - Implement --disable-threads configure option. Disable threads on
12454 netbsd by default, because it appears to have no reentrant resolver
12456 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
12457 release (1.1) detects and disables kqueue if it's broken.
12458 - Append default exit policy before checking for implicit internal
12459 addresses. Now we don't log a bunch of complaints on startup
12460 when using the default exit policy.
12461 - Some people were putting "Address " in their torrc, and they had
12462 a buggy resolver that resolved " " to 0.0.0.0. Oops.
12463 - If DataDir is ~/.tor, and that expands to /.tor, then default to
12464 LOCALSTATEDIR/tor instead.
12465 - Fix fragmented-message bug in TorControl.py.
12466 - Resolve a minor bug which would prevent unreachable dirports
12467 from getting suppressed in the published descriptor.
12468 - When the controller gave us a new descriptor, we weren't resolving
12469 it immediately, so Tor would think its address was 0.0.0.0 until
12470 we fetched a new directory.
12471 - Fix an uppercase/lowercase case error in suppressing a bogus
12472 libevent warning on some Linuxes.
12475 - Begin scrubbing sensitive strings from logs by default. Turn off
12476 the config option SafeLogging if you need to do debugging.
12477 - Switch to a new buffer management algorithm, which tries to avoid
12478 reallocing and copying quite as much. In first tests it looks like
12479 it uses *more* memory on average, but less cpu.
12480 - First cut at support for "create-fast" cells. Clients can use
12481 these when extending to their first hop, since the TLS already
12482 provides forward secrecy and authentication. Not enabled on
12484 - When dirservers refuse a router descriptor, we now log its
12485 contactinfo, platform, and the poster's IP address.
12486 - Call tor_free_all instead of connections_free_all after forking, to
12487 save memory on systems that need to fork.
12488 - Whine at you if you're a server and you don't set your contactinfo.
12489 - Implement --verify-config command-line option to check if your torrc
12490 is valid without actually launching Tor.
12491 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
12492 rather than just rejecting it.
12495 Changes in version 0.1.0.5-rc - 2005-04-27
12497 - Stop trying to print a null pointer if an OR conn fails because
12498 we didn't like its cert.
12500 - Switch our internal buffers implementation to use a ring buffer,
12501 to hopefully improve performance for fast servers a lot.
12502 - Add HttpsProxyAuthenticator support (basic auth only), based
12503 on patch from Adam Langley.
12504 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
12505 the fast servers that have been joining lately.
12506 - Give hidden service accesses extra time on the first attempt,
12507 since 60 seconds is often only barely enough. This might improve
12509 - Improve performance for dirservers: stop re-parsing the whole
12510 directory every time you regenerate it.
12511 - Add more debugging info to help us find the weird dns freebsd
12512 pthreads bug; cleaner debug messages to help track future issues.
12515 Changes in version 0.0.9.9 - 2005-04-23
12516 o Bugfixes on 0.0.9.x:
12517 - If unofficial Tor clients connect and send weird TLS certs, our
12518 Tor server triggers an assert. This release contains a minimal
12519 backport from the broader fix that we put into 0.1.0.4-rc.
12522 Changes in version 0.1.0.4-rc - 2005-04-23
12524 - If unofficial Tor clients connect and send weird TLS certs, our
12525 Tor server triggers an assert. Stop asserting, and start handling
12526 TLS errors better in other situations too.
12527 - When the controller asks us to tell it about all the debug-level
12528 logs, it turns out we were generating debug-level logs while
12529 telling it about them, which turns into a bad loop. Now keep
12530 track of whether you're sending a debug log to the controller,
12531 and don't log when you are.
12532 - Fix the "postdescriptor" feature of the controller interface: on
12533 non-complete success, only say "done" once.
12535 - Clients are now willing to load balance over up to 2mB, not 1mB,
12536 of advertised bandwidth capacity.
12537 - Add a NoPublish config option, so you can be a server (e.g. for
12538 testing running Tor servers in other Tor networks) without
12539 publishing your descriptor to the primary dirservers.
12542 Changes in version 0.1.0.3-rc - 2005-04-08
12543 o Improvements on 0.1.0.2-rc:
12544 - Client now retries when streams end early for 'hibernating' or
12545 'resource limit' reasons, rather than failing them.
12546 - More automated handling for dirserver operators:
12547 - Automatically approve nodes running 0.1.0.2-rc or later,
12548 now that the the reachability detection stuff is working.
12549 - Now we allow two unverified servers with the same nickname
12550 but different keys. But if a nickname is verified, only that
12551 nickname+key are allowed.
12552 - If you're an authdirserver connecting to an address:port,
12553 and it's not the OR you were expecting, forget about that
12554 descriptor. If he *was* the one you were expecting, then forget
12555 about all other descriptors for that address:port.
12556 - Allow servers to publish descriptors from 12 hours in the future.
12557 Corollary: only whine about clock skew from the dirserver if
12558 he's a trusted dirserver (since now even verified servers could
12559 have quite wrong clocks).
12560 - Adjust maximum skew and age for rendezvous descriptors: let skew
12561 be 48 hours rather than 90 minutes.
12562 - Efficiency improvements:
12563 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
12564 it much faster to look up a circuit for each relay cell.
12565 - Remove most calls to assert_all_pending_dns_resolves_ok(),
12566 since they're eating our cpu on exit nodes.
12567 - Stop wasting time doing a case insensitive comparison for every
12568 dns name every time we do any lookup. Canonicalize the names to
12569 lowercase and be done with it.
12570 - Start sending 'truncated' cells back rather than destroy cells,
12571 if the circuit closes in front of you. This means we won't have
12572 to abandon partially built circuits.
12573 - Only warn once per nickname from add_nickname_list_to_smartlist
12574 per failure, so an entrynode or exitnode choice that's down won't
12576 - Put a note in the torrc about abuse potential with the default
12578 - Revise control spec and implementation to allow all log messages to
12579 be sent to controller with their severities intact (suggested by
12580 Matt Edman). Update TorControl to handle new log event types.
12581 - Provide better explanation messages when controller's POSTDESCRIPTOR
12583 - Stop putting nodename in the Platform string in server descriptors.
12584 It doesn't actually help, and it is confusing/upsetting some people.
12586 o Bugfixes on 0.1.0.2-rc:
12587 - We were printing the host mask wrong in exit policies in server
12588 descriptors. This isn't a critical bug though, since we were still
12589 obeying the exit policy internally.
12590 - Fix Tor when compiled with libevent but without pthreads: move
12591 connection_unregister() from _connection_free() to
12593 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
12594 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
12595 when we look through the connection array, we'll find any of the
12596 cpu/dnsworkers. This is no good.
12598 o Bugfixes on 0.0.9.8:
12599 - Fix possible bug on threading platforms (e.g. win32) which was
12600 leaking a file descriptor whenever a cpuworker or dnsworker died.
12601 - When using preferred entry or exit nodes, ignore whether the
12602 circuit wants uptime or capacity. They asked for the nodes, they
12604 - chdir() to your datadirectory at the *end* of the daemonize process,
12605 not the beginning. This was a problem because the first time you
12606 run tor, if your datadir isn't there, and you have runasdaemon set
12607 to 1, it will try to chdir to it before it tries to create it. Oops.
12608 - Handle changed router status correctly when dirserver reloads
12609 fingerprint file. We used to be dropping all unverified descriptors
12610 right then. The bug was hidden because we would immediately
12611 fetch a directory from another dirserver, which would include the
12612 descriptors we just dropped.
12613 - When we're connecting to an OR and he's got a different nickname/key
12614 than we were expecting, only complain loudly if we're an OP or a
12615 dirserver. Complaining loudly to the OR admins just confuses them.
12616 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
12617 artificially capped at 500kB.
12620 Changes in version 0.0.9.8 - 2005-04-07
12621 o Bugfixes on 0.0.9.x:
12622 - We have a bug that I haven't found yet. Sometimes, very rarely,
12623 cpuworkers get stuck in the 'busy' state, even though the cpuworker
12624 thinks of itself as idle. This meant that no new circuits ever got
12625 established. Here's a workaround to kill any cpuworker that's been
12626 busy for more than 100 seconds.
12629 Changes in version 0.1.0.2-rc - 2005-04-01
12630 o Bugfixes on 0.1.0.1-rc:
12631 - Fixes on reachability detection:
12632 - Don't check for reachability while hibernating.
12633 - If ORPort is reachable but DirPort isn't, still publish the
12634 descriptor, but zero out DirPort until it's found reachable.
12635 - When building testing circs for ORPort testing, use only
12636 high-bandwidth nodes, so fewer circuits fail.
12637 - Complain about unreachable ORPort separately from unreachable
12638 DirPort, so the user knows what's going on.
12639 - Make sure we only conclude ORPort reachability if we didn't
12640 initiate the conn. Otherwise we could falsely conclude that
12641 we're reachable just because we connected to the guy earlier
12642 and he used that same pipe to extend to us.
12643 - Authdirservers shouldn't do ORPort reachability detection,
12644 since they're in clique mode, so it will be rare to find a
12645 server not already connected to them.
12646 - When building testing circuits, always pick middle hops running
12647 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
12648 bug. (This is a kludge; it will go away when 0.0.9.x becomes
12650 - When we decide we're reachable, actually publish our descriptor
12652 - Fix bug in redirectstream in the controller.
12653 - Fix the state descriptor strings so logs don't claim edge streams
12654 are in a different state than they actually are.
12655 - Use recent libevent features when possible (this only really affects
12656 win32 and osx right now, because the new libevent with these
12657 features hasn't been released yet). Add code to suppress spurious
12659 - Prevent possible segfault in connection_close_unattached_ap().
12660 - Fix newlines on torrc in win32.
12661 - Improve error msgs when tor-resolve fails.
12663 o Improvements on 0.0.9.x:
12664 - New experimental script tor/contrib/ExerciseServer.py (needs more
12665 work) that uses the controller interface to build circuits and
12666 fetch pages over them. This will help us bootstrap servers that
12667 have lots of capacity but haven't noticed it yet.
12668 - New experimental script tor/contrib/PathDemo.py (needs more work)
12669 that uses the controller interface to let you choose whole paths
12671 "<hostname>.<path,separated by dots>.<length of path>.path"
12672 - When we've connected to an OR and handshaked but didn't like
12673 the result, we were closing the conn without sending destroy
12674 cells back for pending circuits. Now send those destroys.
12677 Changes in version 0.0.9.7 - 2005-04-01
12678 o Bugfixes on 0.0.9.x:
12679 - Fix another race crash bug (thanks to Glenn Fink for reporting).
12680 - Compare identity to identity, not to nickname, when extending to
12681 a router not already in the directory. This was preventing us from
12682 extending to unknown routers. Oops.
12683 - Make sure to create OS X Tor user in <500 range, so we aren't
12684 creating actual system users.
12685 - Note where connection-that-hasn't-sent-end was marked, and fix
12686 a few really loud instances of this harmless bug (it's fixed more
12690 Changes in version 0.1.0.1-rc - 2005-03-28
12692 - Add reachability testing. Your Tor server will automatically try
12693 to see if its ORPort and DirPort are reachable from the outside,
12694 and it won't upload its descriptor until it decides they are.
12695 - Handle unavailable hidden services better. Handle slow or busy
12696 hidden services better.
12697 - Add support for CONNECTing through https proxies, with "HttpsProxy"
12699 - New exit policy: accept most low-numbered ports, rather than
12700 rejecting most low-numbered ports.
12701 - More Tor controller support (still experimental). See
12702 http://tor.eff.org/doc/control-spec.txt for all the new features,
12703 including signals to emulate unix signals from any platform;
12704 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
12705 closestream; closecircuit; etc.
12706 - Make nt services work and start on startup on win32 (based on
12707 patch by Matt Edman).
12708 - Add a new AddressMap config directive to rewrite incoming socks
12709 addresses. This lets you, for example, declare an implicit
12710 required exit node for certain sites.
12711 - Add a new TrackHostExits config directive to trigger addressmaps
12712 for certain incoming socks addresses -- for sites that break when
12713 your exit keeps changing (based on patch by Mike Perry).
12714 - Redo the client-side dns cache so it's just an addressmap too.
12715 - Notice when our IP changes, and reset stats/uptime/reachability.
12716 - When an application is using socks5, give him the whole variety of
12717 potential socks5 responses (connect refused, host unreachable, etc),
12718 rather than just "success" or "failure".
12719 - A more sane version numbering system. See
12720 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
12721 - New contributed script "exitlist": a simple python script to
12722 parse directories and find Tor nodes that exit to listed
12724 - New contributed script "privoxy-tor-toggle" to toggle whether
12725 Privoxy uses Tor. Seems to be configured for Debian by default.
12726 - Report HTTP reasons to client when getting a response from directory
12727 servers -- so you can actually know what went wrong.
12728 - New config option MaxAdvertisedBandwidth which lets you advertise
12729 a low bandwidthrate (to not attract as many circuits) while still
12730 allowing a higher bandwidthrate in reality.
12732 o Robustness/stability fixes:
12733 - Make Tor use Niels Provos's libevent instead of its current
12734 poll-but-sometimes-select mess. This will let us use faster async
12735 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
12737 - pthread support now too. This was forced because when we forked,
12738 we ended up wasting a lot of duplicate ram over time. Also switch
12739 to foo_r versions of some library calls to allow reentry and
12741 - Better handling for heterogeneous / unreliable nodes:
12742 - Annotate circuits w/ whether they aim to contain high uptime nodes
12743 and/or high capacity nodes. When building circuits, choose
12745 - This means that every single node in an intro rend circuit,
12746 not just the last one, will have a minimum uptime.
12747 - New config option LongLivedPorts to indicate application streams
12748 that will want high uptime circuits.
12749 - Servers reset uptime when a dir fetch entirely fails. This
12750 hopefully reflects stability of the server's network connectivity.
12751 - If somebody starts his tor server in Jan 2004 and then fixes his
12752 clock, don't make his published uptime be a year.
12753 - Reset published uptime when you wake up from hibernation.
12754 - Introduce a notion of 'internal' circs, which are chosen without
12755 regard to the exit policy of the last hop. Intro and rendezvous
12756 circs must be internal circs, to avoid leaking information. Resolve
12757 and connect streams can use internal circs if they want.
12758 - New circuit pooling algorithm: make sure to have enough circs around
12759 to satisfy any predicted ports, and also make sure to have 2 internal
12760 circs around if we've required internal circs lately (and with high
12761 uptime if we've seen that lately too).
12762 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
12763 which describes how often we retry making new circuits if current
12764 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
12765 how long we're willing to make use of an already-dirty circuit.
12766 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
12767 circ as necessary, if there are any completed ones lying around
12768 when we try to launch one.
12769 - Make hidden services try to establish a rendezvous for 30 seconds,
12770 rather than for n (where n=3) attempts to build a circuit.
12771 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
12772 "ShutdownWaitLength".
12773 - Try to be more zealous about calling connection_edge_end when
12774 things go bad with edge conns in connection.c.
12775 - Revise tor-spec to add more/better stream end reasons.
12776 - Revise all calls to connection_edge_end to avoid sending "misc",
12777 and to take errno into account where possible.
12780 - Fix a race condition that can trigger an assert, when we have a
12781 pending create cell and an OR connection fails right then.
12782 - Fix several double-mark-for-close bugs, e.g. where we were finding
12783 a conn for a cell even if that conn is already marked for close.
12784 - Make sequence of log messages when starting on win32 with no config
12785 file more reasonable.
12786 - When choosing an exit node for a new non-internal circ, don't take
12787 into account whether it'll be useful for any pending x.onion
12788 addresses -- it won't.
12789 - Turn addr_policy_compare from a tristate to a quadstate; this should
12790 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
12791 for google.com" problem.
12792 - Make "platform" string in descriptor more accurate for Win32 servers,
12793 so it's not just "unknown platform".
12794 - Fix an edge case in parsing config options (thanks weasel).
12795 If they say "--" on the commandline, it's not an option.
12796 - Reject odd-looking addresses at the client (e.g. addresses that
12797 contain a colon), rather than having the server drop them because
12799 - tor-resolve requests were ignoring .exit if there was a working circuit
12800 they could use instead.
12801 - REUSEADDR on normal platforms means you can rebind to the port
12802 right after somebody else has let it go. But REUSEADDR on win32
12803 means to let you bind to the port _even when somebody else
12804 already has it bound_! So, don't do that on Win32.
12805 - Change version parsing logic: a version is "obsolete" if it is not
12806 recommended and (1) there is a newer recommended version in the
12807 same series, or (2) there are no recommended versions in the same
12808 series, but there are some recommended versions in a newer series.
12809 A version is "new" if it is newer than any recommended version in
12811 - Stop most cases of hanging up on a socks connection without sending
12815 - Require BandwidthRate to be at least 20kB/s for servers.
12816 - When a dirserver causes you to give a warn, mention which dirserver
12818 - New config option DirAllowPrivateAddresses for authdirservers.
12819 Now by default they refuse router descriptors that have non-IP or
12820 private-IP addresses.
12821 - Stop publishing socksport in the directory, since it's not
12822 actually meant to be public. For compatibility, publish a 0 there
12824 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
12825 smart" value, that is low for servers and high for clients.
12826 - If our clock jumps forward by 100 seconds or more, assume something
12827 has gone wrong with our network and abandon all not-yet-used circs.
12828 - Warn when exit policy implicitly allows local addresses.
12829 - If we get an incredibly skewed timestamp from a dirserver mirror
12830 that isn't a verified OR, don't warn -- it's probably him that's
12832 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
12833 cookies to disk and doesn't log each web request to disk. (Thanks
12834 to Brett Carrington for pointing this out.)
12835 - When a client asks us for a dir mirror and we don't have one,
12836 launch an attempt to get a fresh one.
12837 - If we're hibernating and we get a SIGINT, exit immediately.
12838 - Add --with-dmalloc ./configure option, to track memory leaks.
12839 - And try to free all memory on closing, so we can detect what
12841 - Cache local dns resolves correctly even when they're .exit
12843 - Give a better warning when some other server advertises an
12844 ORPort that is actually an apache running ssl.
12845 - Add "opt hibernating 1" to server descriptor to make it clearer
12846 whether the server is hibernating.
12849 Changes in version 0.0.9.6 - 2005-03-24
12850 o Bugfixes on 0.0.9.x (crashes and asserts):
12851 - Add new end stream reasons to maintainance branch. Fix bug where
12852 reason (8) could trigger an assert. Prevent bug from recurring.
12853 - Apparently win32 stat wants paths to not end with a slash.
12854 - Fix assert triggers in assert_cpath_layer_ok(), where we were
12855 blowing away the circuit that conn->cpath_layer points to, then
12856 checking to see if the circ is well-formed. Backport check to make
12857 sure we dont use the cpath on a closed connection.
12858 - Prevent circuit_resume_edge_reading_helper() from trying to package
12859 inbufs for marked-for-close streams.
12860 - Don't crash on hup if your options->address has become unresolvable.
12861 - Some systems (like OS X) sometimes accept() a connection and tell
12862 you the remote host is 0.0.0.0:0. If this happens, due to some
12863 other mis-features, we get confused; so refuse the conn for now.
12865 o Bugfixes on 0.0.9.x (other):
12866 - Fix harmless but scary "Unrecognized content encoding" warn message.
12867 - Add new stream error reason: TORPROTOCOL reason means "you are not
12868 speaking a version of Tor I understand; say bye-bye to your stream."
12869 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
12870 into the future, now that we are more tolerant of skew. This
12871 resolves a bug where a Tor server would refuse to cache a directory
12872 because all the directories it gets are too far in the future;
12873 yet the Tor server never logs any complaints about clock skew.
12874 - Mac packaging magic: make man pages useable, and do not overwrite
12875 existing torrc files.
12876 - Make OS X log happily to /var/log/tor/tor.log
12879 Changes in version 0.0.9.5 - 2005-02-22
12880 o Bugfixes on 0.0.9.x:
12881 - Fix an assert race at exit nodes when resolve requests fail.
12882 - Stop picking unverified dir mirrors--it only leads to misery.
12883 - Patch from Matt Edman to make NT services work better. Service
12884 support is still not compiled into the executable by default.
12885 - Patch from Dmitri Bely so the Tor service runs better under
12886 the win32 SYSTEM account.
12887 - Make tor-resolve actually work (?) on Win32.
12888 - Fix a sign bug when getrlimit claims to have 4+ billion
12889 file descriptors available.
12890 - Stop refusing to start when bandwidthburst == bandwidthrate.
12891 - When create cells have been on the onion queue more than five
12892 seconds, just send back a destroy and take them off the list.
12895 Changes in version 0.0.9.4 - 2005-02-03
12896 o Bugfixes on 0.0.9:
12897 - Fix an assert bug that took down most of our servers: when
12898 a server claims to have 1 GB of bandwidthburst, don't
12900 - Don't crash as badly if we have spawned the max allowed number
12901 of dnsworkers, or we're out of file descriptors.
12902 - Block more file-sharing ports in the default exit policy.
12903 - MaxConn is now automatically set to the hard limit of max
12904 file descriptors we're allowed (ulimit -n), minus a few for
12906 - Give a clearer message when servers need to raise their
12907 ulimit -n when they start running out of file descriptors.
12908 - SGI Compatibility patches from Jan Schaumann.
12909 - Tolerate a corrupt cached directory better.
12910 - When a dirserver hasn't approved your server, list which one.
12911 - Go into soft hibernation after 95% of the bandwidth is used,
12912 not 99%. This is especially important for daily hibernators who
12913 have a small accounting max. Hopefully it will result in fewer
12914 cut connections when the hard hibernation starts.
12915 - Load-balance better when using servers that claim more than
12916 800kB/s of capacity.
12917 - Make NT services work (experimental, only used if compiled in).
12920 Changes in version 0.0.9.3 - 2005-01-21
12921 o Bugfixes on 0.0.9:
12922 - Backport the cpu use fixes from main branch, so busy servers won't
12923 need as much processor time.
12924 - Work better when we go offline and then come back, or when we
12925 run Tor at boot before the network is up. We do this by
12926 optimistically trying to fetch a new directory whenever an
12927 application request comes in and we think we're offline -- the
12928 human is hopefully a good measure of when the network is back.
12929 - Backport some minimal hidserv bugfixes: keep rend circuits open as
12930 long as you keep using them; actually publish hidserv descriptors
12931 shortly after they change, rather than waiting 20-40 minutes.
12932 - Enable Mac startup script by default.
12933 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
12934 - When you update AllowUnverifiedNodes or FirewallPorts via the
12935 controller's setconf feature, we were always appending, never
12937 - When you update HiddenServiceDir via setconf, it was screwing up
12938 the order of reading the lines, making it fail.
12939 - Do not rewrite a cached directory back to the cache; otherwise we
12940 will think it is recent and not fetch a newer one on startup.
12941 - Workaround for webservers that lie about Content-Encoding: Tor
12942 now tries to autodetect compressed directories and compression
12943 itself. This lets us Proxypass dir fetches through apache.
12946 Changes in version 0.0.9.2 - 2005-01-04
12947 o Bugfixes on 0.0.9 (crashes and asserts):
12948 - Fix an assert on startup when the disk is full and you're logging
12950 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
12951 style address, then we'd crash.
12952 - Fix an assert trigger when the running-routers string we get from
12953 a dirserver is broken.
12954 - Make worker threads start and run on win32. Now win32 servers
12956 - Bandaid (not actually fix, but now it doesn't crash) an assert
12957 where the dns worker dies mysteriously and the main Tor process
12958 doesn't remember anything about the address it was resolving.
12960 o Bugfixes on 0.0.9 (Win32):
12961 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
12962 name out of the warning/assert messages.
12963 - Fix a superficial "unhandled error on read" bug on win32.
12964 - The win32 installer no longer requires a click-through for our
12965 license, since our Free Software license grants rights but does not
12967 - Win32: When connecting to a dirserver fails, try another one
12968 immediately. (This was already working for non-win32 Tors.)
12969 - Stop trying to parse $HOME on win32 when hunting for default
12971 - Make tor-resolve.c work on win32 by calling network_init().
12973 o Bugfixes on 0.0.9 (other):
12974 - Make 0.0.9.x build on Solaris again.
12975 - Due to a fencepost error, we were blowing away the \n when reporting
12976 confvalue items in the controller. So asking for multiple config
12977 values at once couldn't work.
12978 - When listing circuits that are pending on an opening OR connection,
12979 if we're an OR we were listing circuits that *end* at us as
12980 being pending on every listener, dns/cpu worker, etc. Stop that.
12981 - Dirservers were failing to create 'running-routers' or 'directory'
12982 strings if we had more than some threshold of routers. Fix them so
12983 they can handle any number of routers.
12984 - Fix a superficial "Duplicate mark for close" bug.
12985 - Stop checking for clock skew for OR connections, even for servers.
12986 - Fix a fencepost error that was chopping off the last letter of any
12987 nickname that is the maximum allowed nickname length.
12988 - Update URLs in log messages so they point to the new website.
12989 - Fix a potential problem in mangling server private keys while
12990 writing to disk (not triggered yet, as far as we know).
12991 - Include the licenses for other free software we include in Tor,
12992 now that we're shipping binary distributions more regularly.
12995 Changes in version 0.0.9.1 - 2004-12-15
12996 o Bugfixes on 0.0.9:
12997 - Make hibernation actually work.
12998 - Make HashedControlPassword config option work.
12999 - When we're reporting event circuit status to a controller,
13000 don't use the stream status code.
13003 Changes in version 0.0.9 - 2004-12-12
13005 - Clean up manpage and torrc.sample file.
13006 - Clean up severities and text of log warnings.
13008 - Make servers trigger an assert when they enter hibernation.
13011 Changes in version 0.0.9rc7 - 2004-12-08
13012 o Bugfixes on 0.0.9rc:
13013 - Fix a stack-trashing crash when an exit node begins hibernating.
13014 - Avoid looking at unallocated memory while considering which
13015 ports we need to build circuits to cover.
13016 - Stop a sigpipe: when an 'end' cell races with eof from the app,
13017 we shouldn't hold-open-until-flush if the eof arrived first.
13018 - Fix a bug with init_cookie_authentication() in the controller.
13019 - When recommending new-format log lines, if the upper bound is
13020 LOG_ERR, leave it implicit.
13022 o Bugfixes on 0.0.8.1:
13023 - Fix a whole slew of memory leaks.
13024 - Fix isspace() and friends so they still make Solaris happy
13025 but also so they don't trigger asserts on win32.
13026 - Fix parse_iso_time on platforms without strptime (eg win32).
13027 - win32: tolerate extra "readable" events better.
13028 - win32: when being multithreaded, leave parent fdarray open.
13029 - Make unit tests work on win32.
13032 Changes in version 0.0.9rc6 - 2004-12-06
13033 o Bugfixes on 0.0.9pre:
13034 - Clean up some more integer underflow opportunities (not exploitable
13036 - While hibernating, hup should not regrow our listeners.
13037 - Send an end to the streams we close when we hibernate, rather
13038 than just chopping them off.
13039 - React to eof immediately on non-open edge connections.
13041 o Bugfixes on 0.0.8.1:
13042 - Calculate timeout for waiting for a connected cell from the time
13043 we sent the begin cell, not from the time the stream started. If
13044 it took a long time to establish the circuit, we would time out
13045 right after sending the begin cell.
13046 - Fix router_compare_addr_to_addr_policy: it was not treating a port
13047 of * as always matching, so we were picking reject *:* nodes as
13048 exit nodes too. Oops.
13051 - New circuit building strategy: keep a list of ports that we've
13052 used in the past 6 hours, and always try to have 2 circuits open
13053 or on the way that will handle each such port. Seed us with port
13054 80 so web users won't complain that Tor is "slow to start up".
13055 - Make kill -USR1 dump more useful stats about circuits.
13056 - When warning about retrying or giving up, print the address, so
13057 the user knows which one it's talking about.
13058 - If you haven't used a clean circuit in an hour, throw it away,
13059 just to be on the safe side. (This means after 6 hours a totally
13060 unused Tor client will have no circuits open.)
13063 Changes in version 0.0.9rc5 - 2004-12-01
13064 o Bugfixes on 0.0.8.1:
13065 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
13066 - Let resolve conns retry/expire also, rather than sticking around
13068 - If we are using select, make sure we stay within FD_SETSIZE.
13070 o Bugfixes on 0.0.9pre:
13071 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
13072 but doesn't seem to be currently; thanks to Ilja van Sprundel for
13074 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
13075 instead. Impose minima and maxima for all *Period options; impose
13076 even tighter maxima for fetching if we are a caching dirserver.
13077 Clip rather than rejecting.
13078 - Fetch cached running-routers from servers that serve it (that is,
13079 authdirservers and servers running 0.0.9rc5-cvs or later.)
13082 - Accept *:706 (silc) in default exit policy.
13083 - Implement new versioning format for post 0.1.
13084 - Support "foo.nickname.exit" addresses, to let Alice request the
13085 address "foo" as viewed by exit node "nickname". Based on a patch
13087 - Make tor --version --version dump the cvs Id of every file.
13090 Changes in version 0.0.9rc4 - 2004-11-28
13091 o Bugfixes on 0.0.8.1:
13092 - Make windows sockets actually non-blocking (oops), and handle
13093 win32 socket errors better.
13095 o Bugfixes on 0.0.9rc1:
13096 - Actually catch the -USR2 signal.
13099 Changes in version 0.0.9rc3 - 2004-11-25
13100 o Bugfixes on 0.0.8.1:
13101 - Flush the log file descriptor after we print "Tor opening log file",
13102 so we don't see those messages days later.
13104 o Bugfixes on 0.0.9rc1:
13105 - Make tor-resolve work again.
13106 - Avoid infinite loop in tor-resolve if tor hangs up on it.
13107 - Fix an assert trigger for clients/servers handling resolves.
13110 Changes in version 0.0.9rc2 - 2004-11-24
13111 o Bugfixes on 0.0.9rc1:
13112 - I broke socks5 support while fixing the eof bug.
13113 - Allow unitless bandwidths and intervals; they default to bytes
13115 - New servers don't start out hibernating; they are active until
13116 they run out of bytes, so they have a better estimate of how
13117 long it takes, and so their operators can know they're working.
13120 Changes in version 0.0.9rc1 - 2004-11-23
13121 o Bugfixes on 0.0.8.1:
13122 - Finally fix a bug that's been plaguing us for a year:
13123 With high load, circuit package window was reaching 0. Whenever
13124 we got a circuit-level sendme, we were reading a lot on each
13125 socket, but only writing out a bit. So we would eventually reach
13126 eof. This would be noticed and acted on even when there were still
13127 bytes sitting in the inbuf.
13128 - When poll() is interrupted, we shouldn't believe the revents values.
13130 o Bugfixes on 0.0.9pre6:
13131 - Fix hibernate bug that caused pre6 to be broken.
13132 - Don't keep rephist info for routers that haven't had activity for
13133 24 hours. (This matters now that clients have keys, since we track
13135 - Never call close_temp_logs while validating log options.
13136 - Fix backslash-escaping on tor.sh.in and torctl.in.
13139 - Implement weekly/monthly/daily accounting: now you specify your
13140 hibernation properties by
13141 AccountingMax N bytes|KB|MB|GB|TB
13142 AccountingStart day|week|month [day] HH:MM
13143 Defaults to "month 1 0:00".
13144 - Let bandwidth and interval config options be specified as 5 bytes,
13145 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
13146 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
13147 get back to normal.)
13148 - If your requested entry or exit node has advertised bandwidth 0,
13150 - Be more greedy about filling up relay cells -- we try reading again
13151 once we've processed the stuff we read, in case enough has arrived
13152 to fill the last cell completely.
13153 - Apply NT service patch from Osamu Fujino. Still needs more work.
13156 Changes in version 0.0.9pre6 - 2004-11-15
13157 o Bugfixes on 0.0.8.1:
13158 - Fix assert failure on malformed socks4a requests.
13159 - Use identity comparison, not nickname comparison, to choose which
13160 half of circuit-ID-space each side gets to use. This is needed
13161 because sometimes we think of a router as a nickname, and sometimes
13162 as a hex ID, and we can't predict what the other side will do.
13163 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
13164 write() call will fail and we handle it there.
13165 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
13166 and smartlist_len, which are two major profiling offenders.
13168 o Bugfixes on 0.0.9pre5:
13169 - Fix a bug in read_all that was corrupting config files on windows.
13170 - When we're raising the max number of open file descriptors to
13171 'unlimited', don't log that we just raised it to '-1'.
13172 - Include event code with events, as required by control-spec.txt.
13173 - Don't give a fingerprint when clients do --list-fingerprint:
13174 it's misleading, because it will never be the same again.
13175 - Stop using strlcpy in tor_strndup, since it was slowing us
13177 - Remove warn on startup about missing cached-directory file.
13178 - Make kill -USR1 work again.
13179 - Hibernate if we start tor during the "wait for wakeup-time" phase
13180 of an accounting interval. Log our hibernation plans better.
13181 - Authoritative dirservers now also cache their directory, so they
13182 have it on start-up.
13185 - Fetch running-routers; cache running-routers; compress
13186 running-routers; serve compressed running-routers.z
13187 - Add NSI installer script contributed by J Doe.
13188 - Commit VC6 and VC7 workspace/project files.
13189 - Commit a tor.spec for making RPM files, with help from jbash.
13190 - Add contrib/torctl.in contributed by Glenn Fink.
13191 - Implement the control-spec's SAVECONF command, to write your
13192 configuration to torrc.
13193 - Get cookie authentication for the controller closer to working.
13194 - Include control-spec.txt in the tarball.
13195 - When set_conf changes our server descriptor, upload a new copy.
13196 But don't upload it too often if there are frequent changes.
13197 - Document authentication config in man page, and document signals
13199 - Clean up confusing parts of man page and torrc.sample.
13200 - Make expand_filename handle ~ and ~username.
13201 - Use autoconf to enable largefile support where necessary. Use
13202 ftello where available, since ftell can fail at 2GB.
13203 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
13204 log more informatively.
13205 - Give a slightly more useful output for "tor -h".
13206 - Refuse application socks connections to port 0.
13207 - Check clock skew for verified servers, but allow unverified
13208 servers and clients to have any clock skew.
13209 - Break DirFetchPostPeriod into:
13210 - DirFetchPeriod for fetching full directory,
13211 - StatusFetchPeriod for fetching running-routers,
13212 - DirPostPeriod for posting server descriptor,
13213 - RendPostPeriod for posting hidden service descriptors.
13214 - Make sure the hidden service descriptors are at a random offset
13215 from each other, to hinder linkability.
13218 Changes in version 0.0.9pre5 - 2004-11-09
13219 o Bugfixes on 0.0.9pre4:
13220 - Fix a seg fault in unit tests (doesn't affect main program).
13221 - Fix an assert bug where a hidden service provider would fail if
13222 the first hop of his rendezvous circuit was down.
13223 - Hidden service operators now correctly handle version 1 style
13224 INTRODUCE1 cells (nobody generates them still, so not a critical
13226 - If do_hup fails, actually notice.
13227 - Handle more errnos from accept() without closing the listener.
13228 Some OpenBSD machines were closing their listeners because
13229 they ran out of file descriptors.
13230 - Send resolve cells to exit routers that are running a new
13231 enough version of the resolve code to work right.
13232 - Better handling of winsock includes on non-MSV win32 compilers.
13233 - Some people had wrapped their tor client/server in a script
13234 that would restart it whenever it died. This did not play well
13235 with our "shut down if your version is obsolete" code. Now people
13236 don't fetch a new directory if their local cached version is
13238 - Make our autogen.sh work on ksh as well as bash.
13241 - Hibernation: New config option "AccountingMaxKB" lets you
13242 set how many KBytes per month you want to allow your server to
13243 consume. Rather than spreading those bytes out evenly over the
13244 month, we instead hibernate for some of the month and pop up
13245 at a deterministic time, work until the bytes are consumed, then
13246 hibernate again. Config option "MonthlyAccountingStart" lets you
13247 specify which day of the month your billing cycle starts on.
13248 - Control interface: a separate program can now talk to your
13249 client/server over a socket, and get/set config options, receive
13250 notifications of circuits and streams starting/finishing/dying,
13251 bandwidth used, etc. The next step is to get some GUIs working.
13252 Let us know if you want to help out. See doc/control-spec.txt .
13253 - Ship a contrib/tor-control.py as an example script to interact
13254 with the control port.
13255 - "tor --hash-password zzyxz" will output a salted password for
13256 use in authenticating to the control interface.
13257 - New log format in config:
13258 "Log minsev[-maxsev] stdout|stderr|syslog" or
13259 "Log minsev[-maxsev] file /var/foo"
13262 - DirPolicy config option, to let people reject incoming addresses
13263 from their dirserver.
13264 - "tor --list-fingerprint" will list your identity key fingerprint
13266 - Add "pass" target for RedirectExit, to make it easier to break
13267 out of a sequence of RedirectExit rules.
13268 - Clients now generate a TLS cert too, in preparation for having
13269 them act more like real nodes.
13270 - Ship src/win32/ in the tarball, so people can use it to build.
13271 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
13273 - New "router-status" line in directory, to better bind each verified
13274 nickname to its identity key.
13275 - Deprecate unofficial config option abbreviations, and abbreviations
13276 not on the command line.
13277 - Add a pure-C tor-resolve implementation.
13278 - Use getrlimit and friends to ensure we can reach MaxConn (currently
13279 1024) file descriptors.
13281 o Code security improvements, inspired by Ilja:
13282 - Replace sprintf with snprintf. (I think they were all safe, but
13284 - Replace strcpy/strncpy with strlcpy in more places.
13285 - Avoid strcat; use snprintf or strlcat instead.
13286 - snprintf wrapper with consistent (though not C99) overflow behavior.
13289 Changes in version 0.0.9pre4 - 2004-10-17
13290 o Bugfixes on 0.0.9pre3:
13291 - If the server doesn't specify an exit policy, use the real default
13292 exit policy, not reject *:*.
13293 - Ignore fascistfirewall when uploading/downloading hidden service
13294 descriptors, since we go through Tor for those; and when using
13295 an HttpProxy, since we assume it can reach them all.
13296 - When looking for an authoritative dirserver, use only the ones
13297 configured at boot. Don't bother looking in the directory.
13298 - The rest of the fix for get_default_conf_file() on older win32.
13299 - Make 'Routerfile' config option obsolete.
13302 - New 'MyFamily nick1,...' config option for a server to
13303 specify other servers that shouldn't be used in the same circuit
13304 with it. Only believed if nick1 also specifies us.
13305 - New 'NodeFamily nick1,nick2,...' config option for a client to
13306 specify nodes that it doesn't want to use in the same circuit.
13307 - New 'Redirectexit pattern address:port' config option for a
13308 server to redirect exit connections, e.g. to a local squid.
13311 Changes in version 0.0.9pre3 - 2004-10-13
13312 o Bugfixes on 0.0.8.1:
13313 - Better torrc example lines for dirbindaddress and orbindaddress.
13314 - Improved bounds checking on parsed ints (e.g. config options and
13315 the ones we find in directories.)
13316 - Better handling of size_t vs int, so we're more robust on 64
13318 - Fix the rest of the bug where a newly started OR would appear
13319 as unverified even after we've added his fingerprint and hupped
13321 - Fix a bug from 0.0.7: when read() failed on a stream, we would
13322 close it without sending back an end. So 'connection refused'
13323 would simply be ignored and the user would get no response.
13325 o Bugfixes on 0.0.9pre2:
13326 - Serving the cached-on-disk directory to people is bad. We now
13327 provide no directory until we've fetched a fresh one.
13328 - Workaround for bug on windows where cached-directories get crlf
13330 - Make get_default_conf_file() work on older windows too.
13331 - If we write a *:* exit policy line in the descriptor, don't write
13332 any more exit policy lines.
13335 - Use only 0.0.9pre1 and later servers for resolve cells.
13336 - Make the dirservers file obsolete.
13337 - Include a dir-signing-key token in directories to tell the
13338 parsing entity which key is being used to sign.
13339 - Remove the built-in bulky default dirservers string.
13340 - New config option "Dirserver %s:%d [fingerprint]", which can be
13341 repeated as many times as needed. If no dirservers specified,
13342 default to moria1,moria2,tor26.
13343 - Make moria2 advertise a dirport of 80, so people behind firewalls
13344 will be able to get a directory.
13345 - Http proxy support
13346 - Dirservers translate requests for http://%s:%d/x to /x
13347 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
13348 be routed through this host.
13349 - Clients ask for /tor/x rather than /x for new enough dirservers.
13350 This way we can one day coexist peacefully with apache.
13351 - Clients specify a "Host: %s%d" http header, to be compatible
13352 with more proxies, and so running squid on an exit node can work.
13355 Changes in version 0.0.8.1 - 2004-10-13
13357 - Fix a seg fault that can be triggered remotely for Tor
13358 clients/servers with an open dirport.
13359 - Fix a rare assert trigger, where routerinfos for entries in
13360 our cpath would expire while we're building the path.
13361 - Fix a bug in OutboundBindAddress so it (hopefully) works.
13362 - Fix a rare seg fault for people running hidden services on
13363 intermittent connections.
13364 - Fix a bug in parsing opt keywords with objects.
13365 - Fix a stale pointer assert bug when a stream detaches and
13367 - Fix a string format vulnerability (probably not exploitable)
13368 in reporting stats locally.
13369 - Fix an assert trigger: sometimes launching circuits can fail
13370 immediately, e.g. because too many circuits have failed recently.
13371 - Fix a compile warning on 64 bit platforms.
13374 Changes in version 0.0.9pre2 - 2004-10-03
13376 - Make fetching a cached directory work for 64-bit platforms too.
13377 - Make zlib.h a required header, not an optional header.
13380 Changes in version 0.0.9pre1 - 2004-10-01
13382 - Stop using separate defaults for no-config-file and
13383 empty-config-file. Now you have to explicitly turn off SocksPort,
13384 if you don't want it open.
13385 - Fix a bug in OutboundBindAddress so it (hopefully) works.
13386 - Improve man page to mention more of the 0.0.8 features.
13387 - Fix a rare seg fault for people running hidden services on
13388 intermittent connections.
13389 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
13391 - Fix more dns related bugs: send back resolve_failed and end cells
13392 more reliably when the resolve fails, rather than closing the
13393 circuit and then trying to send the cell. Also attach dummy resolve
13394 connections to a circuit *before* calling dns_resolve(), to fix
13395 a bug where cached answers would never be sent in RESOLVED cells.
13396 - When we run out of disk space, or other log writing error, don't
13397 crash. Just stop logging to that log and continue.
13398 - We were starting to daemonize before we opened our logs, so if
13399 there were any problems opening logs, we would complain to stderr,
13400 which wouldn't work, and then mysteriously exit.
13401 - Fix a rare bug where sometimes a verified OR would connect to us
13402 before he'd uploaded his descriptor, which would cause us to
13403 assign conn->nickname as though he's unverified. Now we look through
13404 the fingerprint list to see if he's there.
13405 - Fix a rare assert trigger, where routerinfos for entries in
13406 our cpath would expire while we're building the path.
13409 - Clients can ask dirservers for /dir.z to get a compressed version
13410 of the directory. Only works for servers running 0.0.9, of course.
13411 - Make clients cache directories and use them to seed their router
13412 lists at startup. This means clients have a datadir again.
13413 - Configuration infrastructure support for warning on obsolete
13415 - Respond to content-encoding headers by trying to uncompress as
13417 - Reply with a deflated directory when a client asks for "dir.z".
13418 We could use allow-encodings instead, but allow-encodings isn't
13419 specified in HTTP 1.0.
13420 - Raise the max dns workers from 50 to 100.
13421 - Discourage people from setting their dirfetchpostperiod more often
13422 than once per minute.
13423 - Protect dirservers from overzealous descriptor uploading -- wait
13424 10 seconds after directory gets dirty, before regenerating.
13427 Changes in version 0.0.8 - 2004-08-25
13428 o Port it to SunOS 5.9 / Athena
13431 Changes in version 0.0.8rc2 - 2004-08-20
13432 o Make it compile on cygwin again.
13433 o When picking unverified routers, skip those with low uptime and/or
13434 low bandwidth, depending on what properties you care about.
13437 Changes in version 0.0.8rc1 - 2004-08-18
13438 o Changes from 0.0.7.3:
13440 - Fix assert triggers: if the other side returns an address 0.0.0.0,
13441 don't put it into the client dns cache.
13442 - If a begin failed due to exit policy, but we believe the IP address
13443 should have been allowed, switch that router to exitpolicy reject *:*
13444 until we get our next directory.
13446 - Clients choose nodes proportional to advertised bandwidth.
13447 - Avoid using nodes with low uptime as introduction points.
13448 - Handle servers with dynamic IP addresses: don't replace
13449 options->Address with the resolved one at startup, and
13450 detect our address right before we make a routerinfo each time.
13451 - 'FascistFirewall' option to pick dirservers and ORs on specific
13452 ports; plus 'FirewallPorts' config option to tell FascistFirewall
13453 which ports are open. (Defaults to 80,443)
13454 - Be more aggressive about trying to make circuits when the network
13455 has changed (e.g. when you unsuspend your laptop).
13456 - Check for time skew on http headers; report date in response to
13458 - If the entrynode config line has only one node, don't pick it as
13460 - Add strict{entry|exit}nodes config options. If set to 1, then
13461 we refuse to build circuits that don't include the specified entry
13463 - OutboundBindAddress config option, to bind to a specific
13464 IP address for outgoing connect()s.
13465 - End truncated log entries (e.g. directories) with "[truncated]".
13467 o Patches to 0.0.8preX:
13469 - Patches to compile and run on win32 again (maybe)?
13470 - Fix crash when looking for ~/.torrc with no $HOME set.
13471 - Fix a race bug in the unit tests.
13472 - Handle verified/unverified name collisions better when new
13473 routerinfo's arrive in a directory.
13474 - Sometimes routers were getting entered into the stats before
13475 we'd assigned their identity_digest. Oops.
13476 - Only pick and establish intro points after we've gotten a
13479 - AllowUnverifiedNodes config option to let circuits choose no-name
13480 routers in entry,middle,exit,introduction,rendezvous positions.
13481 Allow middle and rendezvous positions by default.
13482 - Add a man page for tor-resolve.
13485 Changes in version 0.0.7.3 - 2004-08-12
13486 o Stop dnsworkers from triggering an assert failure when you
13487 ask them to resolve the host "".
13490 Changes in version 0.0.8pre3 - 2004-08-09
13491 o Changes from 0.0.7.2:
13492 - Allow multiple ORs with same nickname in routerlist -- now when
13493 people give us one identity key for a nickname, then later
13494 another, we don't constantly complain until the first expires.
13495 - Remember used bandwidth (both in and out), and publish 15-minute
13496 snapshots for the past day into our descriptor.
13497 - You can now fetch $DIRURL/running-routers to get just the
13498 running-routers line, not the whole descriptor list. (But
13499 clients don't use this yet.)
13500 - When people mistakenly use Tor as an http proxy, point them
13501 at the tor-doc.html rather than the INSTALL.
13502 - Remove our mostly unused -- and broken -- hex_encode()
13503 function. Use base16_encode() instead. (Thanks to Timo Lindfors
13504 for pointing out this bug.)
13505 - Rotate onion keys every 12 hours, not every 2 hours, so we have
13506 fewer problems with people using the wrong key.
13507 - Change the default exit policy to reject the default edonkey,
13508 kazaa, gnutella ports.
13509 - Add replace_file() to util.[ch] to handle win32's rename().
13511 o Changes from 0.0.8preX:
13512 - Fix two bugs in saving onion keys to disk when rotating, so
13513 hopefully we'll get fewer people using old onion keys.
13514 - Fix an assert error that was making SocksPolicy not work.
13515 - Be willing to expire routers that have an open dirport -- it's
13516 just the authoritative dirservers we want to not forget.
13517 - Reject tor-resolve requests for .onion addresses early, so we
13518 don't build a whole rendezvous circuit and then fail.
13519 - When you're warning a server that he's unverified, don't cry
13520 wolf unpredictably.
13521 - Fix a race condition: don't try to extend onto a connection
13522 that's still handshaking.
13523 - For servers in clique mode, require the conn to be open before
13524 you'll choose it for your path.
13525 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
13526 end relay cell, etc.
13527 - Measure bandwidth capacity over the last 24 hours, not just 12
13528 - Bugfix: authoritative dirservers were making and signing a new
13529 directory for each client, rather than reusing the cached one.
13532 Changes in version 0.0.8pre2 - 2004-08-04
13533 o Changes from 0.0.7.2:
13535 - Check directory signature _before_ you decide whether you're
13536 you're running an obsolete version and should exit.
13537 - Check directory signature _before_ you parse the running-routers
13538 list to decide who's running or verified.
13539 - Bugfixes and features:
13540 - Check return value of fclose while writing to disk, so we don't
13541 end up with broken files when servers run out of disk space.
13542 - Log a warning if the user uses an unsafe socks variant, so people
13543 are more likely to learn about privoxy or socat.
13544 - Dirservers now include RFC1123-style dates in the HTTP headers,
13545 which one day we will use to better detect clock skew.
13547 o Changes from 0.0.8pre1:
13548 - Make it compile without warnings again on win32.
13549 - Log a warning if you're running an unverified server, to let you
13550 know you might want to get it verified.
13551 - Only pick a default nickname if you plan to be a server.
13554 Changes in version 0.0.8pre1 - 2004-07-23
13556 - Made our unit tests compile again on OpenBSD 3.5, and tor
13557 itself compile again on OpenBSD on a sparc64.
13558 - We were neglecting milliseconds when logging on win32, so
13559 everything appeared to happen at the beginning of each second.
13561 o Protocol changes:
13562 - 'Extend' relay cell payloads now include the digest of the
13563 intended next hop's identity key. Now we can verify that we're
13564 extending to the right router, and also extend to routers we
13565 hadn't heard of before.
13568 - Tor nodes can now act as relays (with an advertised ORPort)
13569 without being manually verified by the dirserver operators.
13570 - Uploaded descriptors of unverified routers are now accepted
13571 by the dirservers, and included in the directory.
13572 - Verified routers are listed by nickname in the running-routers
13573 list; unverified routers are listed as "$<fingerprint>".
13574 - We now use hash-of-identity-key in most places rather than
13575 nickname or addr:port, for improved security/flexibility.
13576 - To avoid Sybil attacks, paths still use only verified servers.
13577 But now we have a chance to play around with hybrid approaches.
13578 - Nodes track bandwidth usage to estimate capacity (not used yet).
13579 - ClientOnly option for nodes that never want to become servers.
13580 - Directory caching.
13581 - "AuthoritativeDir 1" option for the official dirservers.
13582 - Now other nodes (clients and servers) will cache the latest
13583 directory they've pulled down.
13584 - They can enable their DirPort to serve it to others.
13585 - Clients will pull down a directory from any node with an open
13586 DirPort, and check the signature/timestamp correctly.
13587 - Authoritative dirservers now fetch directories from other
13588 authdirservers, to stay better synced.
13589 - Running-routers list tells who's down also, along with noting
13590 if they're verified (listed by nickname) or unverified (listed
13592 - Allow dirservers to serve running-router list separately.
13593 This isn't used yet.
13594 - ORs connect-on-demand to other ORs
13595 - If you get an extend cell to an OR you're not connected to,
13596 connect, handshake, and forward the create cell.
13597 - The authoritative dirservers stay connected to everybody,
13598 and everybody stays connected to 0.0.7 servers, but otherwise
13599 clients/servers expire unused connections after 5 minutes.
13600 - When servers get a sigint, they delay 30 seconds (refusing new
13601 connections) then exit. A second sigint causes immediate exit.
13602 - File and name management:
13603 - Look for .torrc if no CONFDIR "torrc" is found.
13604 - If no datadir is defined, then choose, make, and secure ~/.tor
13606 - If torrc not found, exitpolicy reject *:*.
13607 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
13608 - If no nickname is defined, derive default from hostname.
13609 - Rename secret key files, e.g. identity.key -> secret_id_key,
13610 to discourage people from mailing their identity key to tor-ops.
13611 - Refuse to build a circuit before the directory has arrived --
13612 it won't work anyway, since you won't know the right onion keys
13614 - Try other dirservers immediately if the one you try is down. This
13615 should tolerate down dirservers better now.
13616 - Parse tor version numbers so we can do an is-newer-than check
13617 rather than an is-in-the-list check.
13618 - New socks command 'resolve', to let us shim gethostbyname()
13620 - A 'tor_resolve' script to access the socks resolve functionality.
13621 - A new socks-extensions.txt doc file to describe our
13622 interpretation and extensions to the socks protocols.
13623 - Add a ContactInfo option, which gets published in descriptor.
13624 - Publish OR uptime in descriptor (and thus in directory) too.
13625 - Write tor version at the top of each log file
13626 - New docs in the tarball:
13628 - Document that you should proxy your SSL traffic too.
13631 Changes in version 0.0.7.2 - 2004-07-07
13632 o A better fix for the 0.0.0.0 problem, that will hopefully
13633 eliminate the remaining related assertion failures.
13636 Changes in version 0.0.7.1 - 2004-07-04
13637 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
13638 since internally we use 0.0.0.0 to signify "not yet resolved".
13641 Changes in version 0.0.7 - 2004-06-07
13642 o Updated the man page to reflect the new features.
13645 Changes in version 0.0.7rc2 - 2004-06-06
13646 o Changes from 0.0.7rc1:
13647 - Make it build on Win32 again.
13648 o Changes from 0.0.6.2:
13649 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
13653 Changes in version 0.0.7rc1 - 2004-06-02
13655 - On sighup, we were adding another log without removing the first
13656 one. So log messages would get duplicated n times for n sighups.
13657 - Several cases of using a connection after we'd freed it. The
13658 problem was that connections that are pending resolve are in both
13659 the pending_resolve tree, and also the circuit's resolving_streams
13660 list. When you want to remove one, you must remove it from both.
13661 - Fix a double-mark-for-close where an end cell arrived for a
13662 resolving stream, and then the resolve failed.
13663 - Check directory signatures based on name of signer, not on whom
13664 we got the directory from. This will let us cache directories more
13667 - Crank up some of our constants to handle more users.
13670 Changes in version 0.0.7pre1 - 2004-06-02
13671 o Fixes for crashes and other obnoxious bugs:
13672 - Fix an epipe bug: sometimes when directory connections failed
13673 to connect, we would give them a chance to flush before closing
13675 - When we detached from a circuit because of resolvefailed, we
13676 would immediately try the same circuit twice more, and then
13677 give up on the resolve thinking we'd tried three different
13679 - Limit the number of intro circuits we'll attempt to build for a
13680 hidden service per 15-minute period.
13681 - Check recommended-software string *early*, before actually parsing
13682 the directory. Thus we can detect an obsolete version and exit,
13683 even if the new directory format doesn't parse.
13684 o Fixes for security bugs:
13685 - Remember which nodes are dirservers when you startup, and if a
13686 random OR enables his dirport, don't automatically assume he's
13687 a trusted dirserver.
13689 - Directory connections were asking the wrong poll socket to
13690 start writing, and not asking themselves to start writing.
13691 - When we detached from a circuit because we sent a begin but
13692 didn't get a connected, we would use it again the first time;
13693 but after that we would correctly switch to a different one.
13694 - Stop warning when the first onion decrypt attempt fails; they
13695 will sometimes legitimately fail now that we rotate keys.
13696 - Override unaligned-access-ok check when $host_cpu is ia64 or
13697 arm. Apparently they allow it but the kernel whines.
13698 - Dirservers try to reconnect periodically too, in case connections
13700 - Fix some memory leaks in directory servers.
13701 - Allow backslash in Win32 filenames.
13702 - Made Tor build complain-free on FreeBSD, hopefully without
13703 breaking other BSD builds. We'll see.
13705 - Doxygen markup on all functions and global variables.
13706 - Make directory functions update routerlist, not replace it. So
13707 now directory disagreements are not so critical a problem.
13708 - Remove the upper limit on number of descriptors in a dirserver's
13709 directory (not that we were anywhere close).
13710 - Allow multiple logfiles at different severity ranges.
13711 - Allow *BindAddress to specify ":port" rather than setting *Port
13712 separately. Allow multiple instances of each BindAddress config
13713 option, so you can bind to multiple interfaces if you want.
13714 - Allow multiple exit policy lines, which are processed in order.
13715 Now we don't need that huge line with all the commas in it.
13716 - Enable accept/reject policies on SOCKS connections, so you can bind
13717 to 0.0.0.0 but still control who can use your OP.
13720 Changes in version 0.0.6.2 - 2004-05-16
13721 o Our integrity-checking digest was checking only the most recent cell,
13722 not the previous cells like we'd thought.
13723 Thanks to Stefan Mark for finding the flaw!
13726 Changes in version 0.0.6.1 - 2004-05-06
13727 o Fix two bugs in our AES counter-mode implementation (this affected
13728 onion-level stream encryption, but not TLS-level). It turns
13729 out we were doing something much more akin to a 16-character
13730 polyalphabetic cipher. Oops.
13731 Thanks to Stefan Mark for finding the flaw!
13732 o Retire moria3 as a directory server, and add tor26 as a directory
13736 Changes in version 0.0.6 - 2004-05-02
13737 [version bump only]
13740 Changes in version 0.0.6rc4 - 2004-05-01
13741 o Update the built-in dirservers list to use the new directory format
13742 o Fix a rare seg fault: if a node offering a hidden service attempts
13743 to build a circuit to Alice's rendezvous point and fails before it
13744 reaches the last hop, it retries with a different circuit, but
13746 o Handle windows socket errors correctly.
13749 Changes in version 0.0.6rc3 - 2004-04-28
13750 o Don't expire non-general excess circuits (if we had enough
13751 circuits open, we were expiring rendezvous circuits -- even
13752 when they had a stream attached. oops.)
13753 o Fetch randomness from /dev/urandom better (not via fopen/fread)
13754 o Better debugging for tls errors
13755 o Some versions of openssl have an SSL_pending function that erroneously
13756 returns bytes when there is a non-application record pending.
13757 o Set Content-Type on the directory and hidserv descriptor.
13758 o Remove IVs from cipher code, since AES-ctr has none.
13759 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
13760 o We were using an array of length zero in a few places.
13761 o win32's gethostbyname can't resolve an IP to an IP.
13762 o win32's close can't close a socket.
13765 Changes in version 0.0.6rc2 - 2004-04-26
13766 o Fix a bug where we were closing tls connections intermittently.
13767 It turns out openssl keeps its errors around -- so if an error
13768 happens, and you don't ask about it, and then another openssl
13769 operation happens and succeeds, and you ask if there was an error,
13770 it tells you about the first error. Fun fun.
13771 o Fix a bug that's been lurking since 27 may 03 (!)
13772 When passing back a destroy cell, we would use the wrong circ id.
13773 'Mostly harmless', but still worth fixing.
13774 o Since we don't support truncateds much, don't bother sending them;
13775 just close the circ.
13776 o check for <machine/limits.h> so we build on NetBSD again (I hope).
13777 o don't crash if a conn that sent a begin has suddenly lost its circuit
13778 (this was quite rare).
13781 Changes in version 0.0.6rc1 - 2004-04-25
13782 o We now rotate link (tls context) keys and onion keys.
13783 o CREATE cells now include oaep padding, so you can tell
13784 if you decrypted them correctly.
13785 o Add bandwidthburst to server descriptor.
13786 o Directories now say which dirserver signed them.
13787 o Use a tor_assert macro that logs failed assertions too.
13790 Changes in version 0.0.6pre5 - 2004-04-18
13791 o changes from 0.0.6pre4:
13792 - make tor build on broken freebsd 5.2 installs
13793 - fix a failed assert when you try an intro point, get a nack, and try
13794 a second one and it works.
13795 - when alice uses a port that the hidden service doesn't accept,
13796 it now sends back an end cell (denied by exit policy). otherwise
13797 alice would just have to wait to time out.
13798 - fix another rare bug: when we had tried all the intro
13799 points for a hidden service, we fetched the descriptor
13800 again, but we left our introcirc thinking it had already
13801 sent an intro, so it kept waiting for a response...
13802 - bugfix: when you sleep your hidden-service laptop, as soon
13803 as it wakes up it tries to upload a service descriptor, but
13804 socketpair fails for some reason (localhost not up yet?).
13805 now we simply give up on that upload, and we'll try again later.
13806 i'd still like to find the bug though.
13807 - if an intro circ waiting for an ack dies before getting one, then
13809 - we were reusing stale service descriptors and refetching usable
13813 Changes in version 0.0.6pre4 - 2004-04-14
13814 o changes from 0.0.6pre3:
13815 - when bob fails to connect to the rendezvous point, and his
13816 circ didn't fail because of the rendezvous point itself, then
13817 he retries a couple of times
13818 - we expire introduction and rendezvous circs more thoroughly
13819 (sometimes they were hanging around forever)
13820 - we expire unattached rendezvous streams that have been around
13821 too long (they were sticking around forever).
13822 - fix a measly fencepost error that was crashing everybody with
13826 Changes in version 0.0.6pre3 - 2004-04-14
13827 o changes from 0.0.6pre2:
13828 - make hup work again
13829 - fix some memory leaks for dirservers
13830 - allow more skew in rendezvous descriptor timestamps, to help
13831 handle people like blanu who don't know what time it is
13832 - normal circs are 3 hops, but some rend/intro circs are 4, if
13833 the initiator doesn't get to choose the last hop
13834 - send acks for introductions, so alice can know whether to try
13836 - bob publishes intro points more correctly
13837 o changes from 0.0.5:
13838 - fix an assert trigger that's been plaguing us since the days
13839 of 0.0.2prexx (thanks weasel!)
13840 - retry stream correctly when we fail to connect because of
13841 exit-policy-reject (should try another) or can't-resolve-address
13842 (also should try another, because dns on random internet servers
13844 - when we hup a dirserver and we've *removed* a server from the
13845 approved-routers list, now we remove that server from the
13846 in-memory directories too
13849 Changes in version 0.0.6pre2 - 2004-04-08
13850 o We fixed our base32 implementation. Now it works on all architectures.
13853 Changes in version 0.0.6pre1 - 2004-04-08
13855 - Hidden services and rendezvous points are implemented. Go to
13856 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
13857 hidden services. (This only works via a socks4a proxy such as
13858 Privoxy, and currently it's quite slow.)
13861 Changes in version 0.0.5 - 2004-03-30
13862 [version bump only]
13865 Changes in version 0.0.5rc3 - 2004-03-29
13866 o Install torrc as torrc.sample -- we no longer clobber your
13868 o Re-enable recommendedversion checking (we broke it in rc2, oops)
13869 o Add in a 'notice' log level for things the operator should hear
13870 but that aren't warnings
13873 Changes in version 0.0.5rc2 - 2004-03-29
13874 o Hold socks connection open until reply is flushed (if possible)
13875 o Make exit nodes resolve IPs to IPs immediately, rather than asking
13876 the dns farm to do it.
13877 o Fix c99 aliasing warnings in rephist.c
13878 o Don't include server descriptors that are older than 24 hours in the
13880 o Give socks 'reject' replies their whole 15s to attempt to flush,
13881 rather than seeing the 60s timeout and assuming the flush had failed.
13882 o Clean automake droppings from the cvs repository
13885 Changes in version 0.0.5rc1 - 2004-03-28
13886 o Fix mangled-state bug in directory fetching (was causing sigpipes).
13887 o Only build circuits after we've fetched the directory: clients were
13888 using only the directory servers before they'd fetched a directory.
13889 This also means longer startup time; so it goes.
13890 o Fix an assert trigger where an OP would fail to handshake, and we'd
13891 expect it to have a nickname.
13892 o Work around a tsocks bug: do a socks reject when AP connection dies
13893 early, else tsocks goes into an infinite loop.
13896 Changes in version 0.0.4 - 2004-03-26
13897 o When connecting to a dirserver or OR and the network is down,
13901 Changes in version 0.0.3 - 2004-03-26
13902 o Warn and fail if server chose a nickname with illegal characters
13903 o Port to Solaris and Sparc:
13904 - include missing header fcntl.h
13905 - have autoconf find -lsocket -lnsl automatically
13906 - deal with hardware word alignment
13907 - make uname() work (solaris has a different return convention)
13908 - switch from using signal() to sigaction()
13909 o Preliminary work on reputation system:
13910 - Keep statistics on success/fail of connect attempts; they're published
13911 by kill -USR1 currently.
13912 - Add a RunTesting option to try to learn link state by creating test
13913 circuits, even when SocksPort is off.
13914 - Remove unused open circuits when there are too many.
13917 Changes in version 0.0.2 - 2004-03-19
13918 - Include strlcpy and strlcat for safer string ops
13919 - define INADDR_NONE so we compile (but still not run) on solaris
13922 Changes in version 0.0.2pre27 - 2004-03-14
13924 - Allow internal tor networks (we were rejecting internal IPs,
13925 now we allow them if they're set explicitly).
13926 - And fix a few endian issues.
13929 Changes in version 0.0.2pre26 - 2004-03-14
13931 - If a stream times out after 15s without a connected cell, don't
13932 try that circuit again: try a new one.
13933 - Retry streams at most 4 times. Then give up.
13934 - When a dirserver gets a descriptor from an unknown router, it
13935 logs its fingerprint (so the dirserver operator can choose to
13936 accept it even without mail from the server operator).
13937 - Inform unapproved servers when we reject their descriptors.
13938 - Make tor build on Windows again. It works as a client, who knows
13940 - Clearer instructions in the torrc for how to set up a server.
13941 - Be more efficient about reading fd's when our global token bucket
13942 (used for rate limiting) becomes empty.
13944 - Stop asserting that computers always go forward in time. It's
13946 - When we sent a cell (e.g. destroy) and then marked an OR connection
13947 expired, we might close it before finishing a flush if the other
13948 side isn't reading right then.
13949 - Don't allow dirservers to start if they haven't defined
13950 RecommendedVersions
13951 - We were caching transient dns failures. Oops.
13952 - Prevent servers from publishing an internal IP as their address.
13953 - Address a strcat vulnerability in circuit.c
13956 Changes in version 0.0.2pre25 - 2004-03-04
13958 - Put the OR's IP in its router descriptor, not its fqdn. That way
13959 we'll stop being stalled by gethostbyname for nodes with flaky dns,
13962 - If the user typed in an address that didn't resolve, the server
13966 Changes in version 0.0.2pre24 - 2004-03-03
13968 - Fix an assertion failure in dns.c, where we were trying to dequeue
13969 a pending dns resolve even if it wasn't pending
13970 - Fix a spurious socks5 warning about still trying to write after the
13971 connection is finished.
13972 - Hold certain marked_for_close connections open until they're finished
13973 flushing, rather than losing bytes by closing them too early.
13974 - Correctly report the reason for ending a stream
13975 - Remove some duplicate calls to connection_mark_for_close
13976 - Put switch_id and start_daemon earlier in the boot sequence, so it
13977 will actually try to chdir() to options.DataDirectory
13978 - Make 'make test' exit(1) if a test fails; fix some unit tests
13979 - Make tor fail when you use a config option it doesn't know about,
13980 rather than warn and continue.
13981 - Make --version work
13982 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
13985 Changes in version 0.0.2pre23 - 2004-02-29
13987 - Print a statement when the first circ is finished, so the user
13988 knows it's working.
13989 - If a relay cell is unrecognized at the end of the circuit,
13990 send back a destroy. (So attacks to mutate cells are more
13992 - New config option 'excludenodes' to avoid certain nodes for circuits.
13993 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
13994 so you can collect coredumps there.
13996 - Fix a bug in tls flushing where sometimes data got wedged and
13997 didn't flush until more data got sent. Hopefully this bug was
13998 a big factor in the random delays we were seeing.
13999 - Make 'connected' cells include the resolved IP, so the client
14000 dns cache actually gets populated.
14001 - Disallow changing from ORPort=0 to ORPort>0 on hup.
14002 - When we time-out on a stream and detach from the circuit, send an
14003 end cell down it first.
14004 - Only warn about an unknown router (in exitnodes, entrynodes,
14005 excludenodes) after we've fetched a directory.
14008 Changes in version 0.0.2pre22 - 2004-02-26
14010 - Servers publish less revealing uname information in descriptors.
14011 - More memory tracking and assertions, to crash more usefully when
14013 - If the default torrc isn't there, just use some default defaults.
14014 Plus provide an internal dirservers file if they don't have one.
14015 - When the user tries to use Tor as an http proxy, give them an http
14016 501 failure explaining that we're a socks proxy.
14017 - Dump a new router.desc on hup, to help confused people who change
14018 their exit policies and then wonder why router.desc doesn't reflect
14020 - Clean up the generic tor.sh init script that we ship with.
14022 - If the exit stream is pending on the resolve, and a destroy arrives,
14023 then the stream wasn't getting removed from the pending list. I
14024 think this was the one causing recent server crashes.
14025 - Use a more robust poll on OSX 10.3, since their poll is flaky.
14026 - When it couldn't resolve any dirservers, it was useless from then on.
14027 Now it reloads the RouterFile (or default dirservers) if it has no
14029 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
14030 many users don't even *have* a /usr/local/sbin/.
14033 Changes in version 0.0.2pre21 - 2004-02-18
14035 - There's a ChangeLog file that actually reflects the changelog.
14036 - There's a 'torify' wrapper script, with an accompanying
14037 tor-tsocks.conf, that simplifies the process of using tsocks for
14038 tor. It even has a man page.
14039 - The tor binary gets installed to sbin rather than bin now.
14040 - Retry streams where the connected cell hasn't arrived in 15 seconds
14041 - Clean up exit policy handling -- get the default out of the torrc,
14042 so we can update it without forcing each server operator to fix
14044 - Allow imaps and pop3s in default exit policy
14046 - Prevent picking middleman nodes as the last node in the circuit
14049 Changes in version 0.0.2pre20 - 2004-01-30
14051 - We now have a deb package, and it's in debian unstable. Go to
14052 it, apt-getters. :)
14053 - I've split the TotalBandwidth option into BandwidthRate (how many
14054 bytes per second you want to allow, long-term) and
14055 BandwidthBurst (how many bytes you will allow at once before the cap
14056 kicks in). This better token bucket approach lets you, say, set
14057 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
14058 performance while not exceeding your monthly bandwidth quota.
14059 - Push out a tls record's worth of data once you've got it, rather
14060 than waiting until you've read everything waiting to be read. This
14061 may improve performance by pipelining better. We'll see.
14062 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
14063 from failed circuits (if they haven't been connected yet) and attach
14065 - Expire old streams that haven't managed to connect. Some day we'll
14066 have them reattach to new circuits instead.
14069 - Fix several memory leaks that were causing servers to become bloated
14071 - Fix a few very rare assert triggers. A few more remain.
14072 - Setuid to User _before_ complaining about running as root.
14075 Changes in version 0.0.2pre19 - 2004-01-07
14077 - Fix deadlock condition in dns farm. We were telling a child to die by
14078 closing the parent's file descriptor to him. But newer children were
14079 inheriting the open file descriptor from the parent, and since they
14080 weren't closing it, the socket never closed, so the child never read
14081 eof, so he never knew to exit. Similarly, dns workers were holding
14082 open other sockets, leading to all sorts of chaos.
14083 - New cleaner daemon() code for forking and backgrounding.
14084 - If you log to a file, it now prints an entry at the top of the
14085 logfile so you know it's working.
14086 - The onionskin challenge length was 30 bytes longer than necessary.
14087 - Started to patch up the spec so it's not quite so out of date.
14090 Changes in version 0.0.2pre18 - 2004-01-02
14092 - Fix endian issues with the 'integrity' field in the relay header.
14093 - Fix a potential bug where connections in state
14094 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
14097 Changes in version 0.0.2pre17 - 2003-12-30
14099 - Made --debuglogfile (or any second log file, actually) work.
14100 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
14101 adversary could force us into an infinite loop.
14104 - Each onionskin handshake now includes a hash of the computed key,
14105 to prove the server's identity and help perfect forward secrecy.
14106 - Changed cell size from 256 to 512 bytes (working toward compatibility
14108 - Changed cell length to 2 bytes, and moved it to the relay header.
14109 - Implemented end-to-end integrity checking for the payloads of
14111 - Separated streamid from 'recognized' (otherwise circuits will get
14112 messed up when we try to have streams exit from the middle). We
14113 use the integrity-checking to confirm that a cell is addressed to
14115 - Randomize the initial circid and streamid values, so an adversary who
14116 breaks into a node can't learn how many circuits or streams have
14120 Changes in version 0.0.2pre16 - 2003-12-14
14122 - Fixed a bug that made HUP trigger an assert
14123 - Fixed a bug where a circuit that immediately failed wasn't being
14124 counted as a failed circuit in counting retries.
14127 - Now we close the circuit when we get a truncated cell: otherwise we're
14128 open to an anonymity attack where a bad node in the path truncates
14129 the circuit and then we open streams at him.
14130 - Add port ranges to exit policies
14131 - Add a conservative default exit policy
14132 - Warn if you're running tor as root
14133 - on HUP, retry OR connections and close/rebind listeners
14134 - options.EntryNodes: try these nodes first when picking the first node
14135 - options.ExitNodes: if your best choices happen to include any of
14136 your preferred exit nodes, you choose among just those preferred
14138 - options.ExcludedNodes: nodes that are never picked in path building
14141 Changes in version 0.0.2pre15 - 2003-12-03
14142 o Robustness and bugfixes:
14143 - Sometimes clients would cache incorrect DNS resolves, which would
14144 really screw things up.
14145 - An OP that goes offline would slowly leak all its sockets and stop
14147 - A wide variety of bugfixes in exit node selection, exit policy
14148 handling, and processing pending streams when a new circuit is
14150 - Pick nodes for a path only from those the directory says are up
14151 - Choose randomly from all running dirservers, not always the first one
14152 - Increase allowed http header size for directory fetch.
14153 - Stop writing to stderr (if we're daemonized it will be closed).
14154 - Enable -g always, so cores will be more useful to me.
14155 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
14158 - Wrote a man page. It lists commonly used options.
14161 - Change default loglevel to warn.
14162 - Make PidFile default to null rather than littering in your CWD.
14163 - OnionRouter config option is now obsolete. Instead it just checks
14165 - Moved to a single unified torrc file for both clients and servers.
14168 Changes in version 0.0.2pre14 - 2003-11-29
14169 o Robustness and bugfixes:
14170 - Force the admin to make the DataDirectory himself
14171 - to get ownership/permissions right
14172 - so clients no longer make a DataDirectory and then never use it
14173 - fix bug where a client who was offline for 45 minutes would never
14174 pull down a directory again
14175 - fix (or at least hide really well) the dns assert bug that was
14176 causing server crashes
14177 - warnings and improved robustness wrt clockskew for certs
14178 - use the native daemon(3) to daemonize, when available
14179 - exit if bind() fails
14180 - exit if neither socksport nor orport is defined
14181 - include our own tor_timegm (Win32 doesn't have its own)
14182 - bugfix for win32 with lots of connections
14183 - fix minor bias in PRNG
14184 - make dirserver more robust to corrupt cached directory
14187 - Wrote the design document (woo)
14189 o Circuit building and exit policies:
14190 - Circuits no longer try to use nodes that the directory has told them
14192 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
14193 bitcounts (18.0.0.0/8).
14194 - Make AP connections standby for a circuit if no suitable circuit
14195 exists, rather than failing
14196 - Circuits choose exit node based on addr/port, exit policies, and
14197 which AP connections are standing by
14198 - Bump min pathlen from 2 to 3
14199 - Relay end cells have a payload to describe why the stream ended.
14200 - If the stream failed because of exit policy, try again with a new
14202 - Clients have a dns cache to remember resolved addresses.
14203 - Notice more quickly when we have no working circuits
14206 - APPort is now called SocksPort
14207 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
14209 - RecommendedVersions is now a config variable rather than
14210 hardcoded (for dirservers)
14211 - Reloads config on HUP
14212 - Usage info on -h or --help
14213 - If you set User and Group config vars, it'll setu/gid to them.
14216 Changes in version 0.0.2pre13 - 2003-10-19
14217 o General stability:
14218 - SSL_write no longer fails when it returns WANTWRITE and the number
14219 of bytes in the buf has changed by the next SSL_write call.
14220 - Fix segfault fetching directory when network is down
14221 - Fix a variety of minor memory leaks
14222 - Dirservers reload the fingerprints file on HUP, so I don't have
14223 to take down the network when I approve a new router
14224 - Default server config file has explicit Address line to specify fqdn
14227 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
14228 - Make listener connections not ever alloc bufs
14230 o Autoconf improvements:
14231 - don't clobber an external CFLAGS in ./configure
14232 - Make install now works
14233 - create var/lib/tor on make install
14234 - autocreate a tor.sh initscript to help distribs
14235 - autocreate the torrc and sample-server-torrc with correct paths
14237 o Log files and Daemonizing now work:
14238 - If --DebugLogFile is specified, log to it at -l debug
14239 - If --LogFile is specified, use it instead of commandline
14240 - If --RunAsDaemon is set, tor forks and backgrounds on startup