1 Changes in version 0.2.3.11-alpha - 201?-??-??
4 Changes in version 0.2.3.10-alpha - 2011-12-16
5 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
6 Tor's buffers code. Absolutely everybody should upgrade.
8 The bug relied on an incorrect calculation when making data continuous
9 in one of our IO buffers, if the first chunk of the buffer was
10 misaligned by just the wrong amount. The miscalculation would allow an
11 attacker to overflow a piece of heap-allocated memory. To mount this
12 attack, the attacker would need to either open a SOCKS connection to
13 Tor's SocksPort (usually restricted to localhost), or target a Tor
14 instance configured to make its connections through a SOCKS proxy
15 (which Tor does not do by default).
17 Good security practice requires that all heap-overflow bugs should be
18 presumed to be exploitable until proven otherwise, so we are treating
19 this as a potential code execution attack. Please upgrade immediately!
20 This bug does not affect bufferevents-based builds of Tor. Special
21 thanks to "Vektor" for reporting this issue to us!
23 This release also contains a few minor bugfixes for issues discovered
27 - Fix a heap overflow bug that could occur when trying to pull
28 data into the first chunk of a buffer, when that chunk had
29 already had some data drained from it. Fixes CVE-2011-2778;
30 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
33 - If we can't attach streams to a rendezvous circuit when we
34 finish connecting to a hidden service, clear the rendezvous
35 circuit's stream-isolation state and try to attach streams
36 again. Previously, we cleared rendezvous circuits' isolation
37 state either too early (if they were freshly built) or not at all
38 (if they had been built earlier and were cannibalized). Bugfix on
39 0.2.3.3-alpha; fixes bug 4655.
40 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
41 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
42 - Fix an assertion failure when a relay with accounting enabled
43 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
46 - Update to the December 6 2011 Maxmind GeoLite Country database.
49 Changes in version 0.2.2.35 - 2011-12-16
50 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
51 buffers code. Absolutely everybody should upgrade.
53 The bug relied on an incorrect calculation when making data continuous
54 in one of our IO buffers, if the first chunk of the buffer was
55 misaligned by just the wrong amount. The miscalculation would allow an
56 attacker to overflow a piece of heap-allocated memory. To mount this
57 attack, the attacker would need to either open a SOCKS connection to
58 Tor's SocksPort (usually restricted to localhost), or target a Tor
59 instance configured to make its connections through a SOCKS proxy
60 (which Tor does not do by default).
62 Good security practice requires that all heap-overflow bugs should be
63 presumed to be exploitable until proven otherwise, so we are treating
64 this as a potential code execution attack. Please upgrade immediately!
65 This bug does not affect bufferevents-based builds of Tor. Special
66 thanks to "Vektor" for reporting this issue to us!
68 Tor 0.2.2.35 also fixes several bugs in previous versions, including
69 crash bugs for unusual configurations, and a long-term bug that
70 would prevent Tor from starting on Windows machines with draconian
73 With this release, we remind everyone that 0.2.0.x has reached its
74 formal end-of-life. Those Tor versions have many known flaws, and
75 nobody should be using them. You should upgrade -- ideally to the
76 0.2.2.x series. If you're using a Linux or BSD and its packages are
77 obsolete, stop using those packages and upgrade anyway.
79 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
80 longer receive support after some time in early 2012.
83 - Fix a heap overflow bug that could occur when trying to pull
84 data into the first chunk of a buffer, when that chunk had
85 already had some data drained from it. Fixes CVE-2011-2778;
86 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
87 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
88 that it doesn't attempt to allocate a socketpair. This could cause
89 some problems on Windows systems with overzealous firewalls. Fix for
90 bug 4457; workaround for Libevent versions 2.0.1-alpha through
92 - If we mark an OR connection for close based on a cell we process,
93 don't process any further cells on it. We already avoid further
94 reads on marked-for-close connections, but now we also discard the
95 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
96 which was the first version where we might mark a connection for
97 close based on processing a cell on it.
98 - Correctly sanity-check that we don't underflow on a memory
99 allocation (and then assert) for hidden service introduction
100 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
101 bugfix on 0.2.1.5-alpha.
102 - Fix a memory leak when we check whether a hidden service
103 descriptor has any usable introduction points left. Fixes bug
104 4424. Bugfix on 0.2.2.25-alpha.
105 - Don't crash when we're running as a relay and don't have a GeoIP
106 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
107 we've had in the 0.2.3.x branch already.
108 - When running as a client, do not print a misleading (and plain
109 wrong) log message that we're collecting "directory request"
110 statistics: clients don't collect statistics. Also don't create a
111 useless (because empty) stats file in the stats/ directory. Fixes
112 bug 4353; bugfix on 0.2.2.34.
115 - Detect failure to initialize Libevent. This fix provides better
116 detection for future instances of bug 4457.
117 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
118 function. This was eating up hideously large amounts of time on some
119 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
120 - Resolve an integer overflow bug in smartlist_ensure_capacity().
121 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
123 - Don't warn about unused log_mutex in log.c when building with
124 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
125 0.1.0.6-rc which introduced --disable-threads.
126 - When configuring, starting, or stopping an NT service, stop
127 immediately after the service configuration attempt has succeeded
128 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
129 - When sending a NETINFO cell, include the original address
130 received for the other side, not its canonical address. Found
131 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
132 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
133 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
134 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
135 occurred when a client tried to fetch a descriptor for a bridge
136 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
137 - Backport fixes for a pair of compilation warnings on Windows.
138 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
139 - If we had ever tried to call tor_addr_to_str on an address of
140 unknown type, we would have done a strdup on an uninitialized
141 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
142 Reported by "troll_un".
143 - Correctly detect and handle transient lookup failures from
144 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
145 Reported by "troll_un".
146 - Fix null-pointer access that could occur if TLS allocation failed.
147 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
148 - Use tor_socket_t type for listener argument to accept(). Fixes bug
149 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
152 - Add two new config options for directory authorities:
153 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
154 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
155 that is always sufficient to satisfy the bandwidth requirement for
156 the Guard flag. Now it will be easier for researchers to simulate
157 Tor networks with different values. Resolves ticket 4484.
158 - When Tor ignores a hidden service specified in its configuration,
159 include the hidden service's directory in the warning message.
160 Previously, we would only tell the user that some hidden service
161 was ignored. Bugfix on 0.0.6; fixes bug 4426.
162 - Update to the December 6 2011 Maxmind GeoLite Country database.
165 - Make it easier to automate expert package builds on Windows,
166 by removing an absolute path from makensis.exe command.
169 Changes in version 0.2.3.9-alpha - 2011-12-08
170 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
171 a "DisableNetwork" security feature that bundles can use to avoid
172 touching the network until bridges are configured, moves forward on
173 the pluggable transport design, fixes a flaw in the hidden service
174 design that unnecessarily prevented clients with wrong clocks from
175 reaching hidden services, and fixes a wide variety of other issues.
178 - Clients can now connect to private bridges over IPv6. Bridges
179 still need at least one IPv4 address in order to connect to
180 other relays. Note that we don't yet handle the case where the
181 user has two bridge lines for the same bridge (one IPv4, one
182 IPv6). Implements parts of proposal 186.
183 - New "DisableNetwork" config option to prevent Tor from launching any
184 connections or accepting any connections except on a control port.
185 Bundles and controllers can set this option before letting Tor talk
186 to the rest of the network, for example to prevent any connections
187 to a non-bridge address. Packages like Orbot can also use this
188 option to instruct Tor to save power when the network is off.
189 - Clients and bridges can now be configured to use a separate
190 "transport" proxy. This approach makes the censorship arms race
191 easier by allowing bridges to use protocol obfuscation plugins. It
192 implements the "managed proxy" part of proposal 180 (ticket 3472).
193 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
194 implementation. It makes AES_CTR about 7% faster than our old one
195 (which was about 10% faster than the one OpenSSL used to provide).
196 Resolves ticket 4526.
197 - Add a "tor2web mode" for clients that want to connect to hidden
198 services non-anonymously (and possibly more quickly). As a safety
199 measure to try to keep users from turning this on without knowing
200 what they are doing, tor2web mode must be explicitly enabled at
201 compile time, and a copy of Tor compiled to run in tor2web mode
202 cannot be used as a normal Tor client. Implements feature 2553.
203 - Add experimental support for running on Windows with IOCP and no
204 kernel-space socket buffers. This feature is controlled by a new
205 "UserspaceIOCPBuffers" config option (off by default), which has
206 no effect unless Tor has been built with support for bufferevents,
207 is running on Windows, and has enabled IOCP. This may, in the long
208 run, help solve or mitigate bug 98.
209 - Use a more secure consensus parameter voting algorithm. Now at
210 least three directory authorities or a majority of them must
211 vote on a given parameter before it will be included in the
212 consensus. Implements proposal 178.
215 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
216 They used to check that the timestamp was within 30 minutes
217 of their system clock, so they could cap the size of their
218 replay-detection cache, but that approach unnecessarily refused
219 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
220 the v3 intro-point protocol (the first one which sent a timestamp
221 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
222 - Only use the EVP interface when AES acceleration is enabled,
223 to avoid a 5-7% performance regression. Resolves issue 4525;
224 bugfix on 0.2.3.8-alpha.
226 o Privacy/anonymity features (bridge detection):
227 - Make bridge SSL certificates a bit more stealthy by using random
228 serial numbers, in the same fashion as OpenSSL when generating
229 self-signed certificates. Implements ticket 4584.
230 - Introduce a new config option "DynamicDHGroups", enabled by
231 default, which provides each bridge with a unique prime DH modulus
232 to be used during SSL handshakes. This option attempts to help
233 against censors who might use the Apache DH modulus as a static
234 identifier for bridges. Addresses ticket 4548.
236 o Minor features (new/different config options):
237 - New configuration option "DisableDebuggerAttachment" (on by default)
238 to prevent basic debugging attachment attempts by other processes.
239 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
240 - Allow MapAddress directives to specify matches against super-domains,
241 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
242 Implements issue 933.
243 - Slightly change behavior of "list" options (that is, config
244 options that can appear more than once) when they appear both in
245 torrc and on the command line. Previously, the command-line options
246 would be appended to the ones from torrc. Now, the command-line
247 options override the torrc options entirely. This new behavior
248 allows the user to override list options (like exit policies and
249 ports to listen on) from the command line, rather than simply
250 appending to the list.
251 - You can get the old (appending) command-line behavior for "list"
252 options by prefixing the option name with a "+".
253 - You can remove all the values for a "list" option from the command
254 line without adding any new ones by prefixing the option name
256 - Add experimental support for a "defaults" torrc file to be parsed
257 before the regular torrc. Torrc options override the defaults file's
258 options in the same way that the command line overrides the torrc.
259 The SAVECONF controller command saves only those options which
260 differ between the current configuration and the defaults file. HUP
261 reloads both files. (Note: This is an experimental feature; its
262 behavior will probably be refined in future 0.2.3.x-alpha versions
263 to better meet packagers' needs.)
266 - Try to make the introductory warning message that Tor prints on
267 startup more useful for actually finding help and information.
268 Resolves ticket 2474.
269 - Running "make version" now displays the version of Tor that
270 we're about to build. Idea from katmagic; resolves issue 4400.
271 - Expire old or over-used hidden service introduction points.
272 Required by fix for bug 3460.
273 - Move the replay-detection cache for the RSA-encrypted parts of
274 INTRODUCE2 cells to the introduction point data structures.
275 Previously, we would use one replay-detection cache per hidden
276 service. Required by fix for bug 3460.
277 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
278 public key replay-detection cache from 60 minutes to 5 minutes. This
279 replay-detection cache is now used only to detect multiple
280 INTRODUCE2 cells specifying the same rendezvous point, so we can
281 avoid launching multiple simultaneous attempts to connect to it.
283 o Minor bugfixes (on Tor 0.2.2.x and earlier):
284 - Resolve an integer overflow bug in smartlist_ensure_capacity().
285 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
287 - Fix a minor formatting issue in one of tor-gencert's error messages.
289 - Prevent a false positive from the check-spaces script, by disabling
290 the "whitespace between function name and (" check for functions
292 - Fix a log message suggesting that people contact a non-existent
293 email address. Fixes bug 3448.
294 - Fix null-pointer access that could occur if TLS allocation failed.
295 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
296 - Report a real bootstrap problem to the controller on router
297 identity mismatch. Previously we just said "foo", which probably
298 made a lot of sense at the time. Fixes bug 4169; bugfix on
300 - If we had ever tried to call tor_addr_to_str() on an address of
301 unknown type, we would have done a strdup() on an uninitialized
302 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
303 Reported by "troll_un".
304 - Correctly detect and handle transient lookup failures from
305 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
306 Reported by "troll_un".
307 - Use tor_socket_t type for listener argument to accept(). Fixes bug
308 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
309 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
310 bug 4532; found by "troll_un".
312 o Minor bugfixes (on Tor 0.2.3.x):
313 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
315 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
316 circuit for use as a hidden service client's rendezvous point.
317 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
318 with help from wanoskarnet.
319 - Restore behavior of overriding SocksPort, ORPort, and similar
320 options from the command line. Bugfix on 0.2.3.3-alpha.
323 - Properly handle the case where the build-tree is not the same
324 as the source tree when generating src/common/common_sha1.i,
325 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
326 bugfix on 0.2.0.1-alpha.
328 o Code simplifications, cleanups, and refactorings:
329 - Remove the pure attribute from all functions that used it
330 previously. In many cases we assigned it incorrectly, because the
331 functions might assert or call impure functions, and we don't have
332 evidence that keeping the pure attribute is worthwhile. Implements
333 changes suggested in ticket 4421.
334 - Remove some dead code spotted by coverity. Fixes cid 432.
335 Bugfix on 0.2.3.1-alpha, closes bug 4637.
338 Changes in version 0.2.3.8-alpha - 2011-11-22
339 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
340 socketpair-related bug that has been bothering Windows users. It adds
341 support to serve microdescriptors to controllers, so Vidalia's network
342 map can resume listing relays (once Vidalia implements its side),
343 and adds better support for hardware AES acceleration. Finally, it
344 starts the process of adjusting the bandwidth cutoff for getting the
345 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
346 that tiny relays harm performance more than they help network capacity.
349 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
350 that it doesn't attempt to allocate a socketpair. This could cause
351 some problems on Windows systems with overzealous firewalls. Fix for
352 bug 4457; workaround for Libevent versions 2.0.1-alpha through
354 - Correctly sanity-check that we don't underflow on a memory
355 allocation (and then assert) for hidden service introduction
356 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
357 bugfix on 0.2.1.5-alpha.
358 - Remove the artificially low cutoff of 20KB to guarantee the Fast
359 flag. In the past few years the average relay speed has picked
360 up, and while the "top 7/8 of the network get the Fast flag" and
361 "all relays with 20KB or more of capacity get the Fast flag" rules
362 used to have the same result, now the top 7/8 of the network has
363 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
364 - Fix a rare assertion failure when checking whether a v0 hidden
365 service descriptor has any usable introduction points left, and
366 we don't have enough information to build a circuit to the first
367 intro point named in the descriptor. The HS client code in
368 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
369 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
370 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
371 - Make bridge authorities not crash when they are asked for their own
372 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
373 - When running as a client, do not print a misleading (and plain
374 wrong) log message that we're collecting "directory request"
375 statistics: clients don't collect statistics. Also don't create a
376 useless (because empty) stats file in the stats/ directory. Fixes
377 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
380 - Allow Tor controllers like Vidalia to obtain the microdescriptor
381 for a relay by identity digest or nickname. Previously,
382 microdescriptors were only available by their own digests, so a
383 controller would have to ask for and parse the whole microdescriptor
384 consensus in order to look up a single relay's microdesc. Fixes
385 bug 3832; bugfix on 0.2.3.1-alpha.
386 - Use OpenSSL's EVP interface for AES encryption, so that all AES
387 operations can use hardware acceleration (if present). Resolves
390 o Minor bugfixes (on 0.2.2.x and earlier):
391 - Detect failure to initialize Libevent. This fix provides better
392 detection for future instances of bug 4457.
393 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
394 function. This was eating up hideously large amounts of time on some
395 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
396 - Don't warn about unused log_mutex in log.c when building with
397 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
398 0.1.0.6-rc which introduced --disable-threads.
399 - Allow manual 'authenticate' commands to the controller interface
400 from netcat (nc) as well as telnet. We were rejecting them because
401 they didn't come with the expected whitespace at the end of the
402 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
403 - Fix some (not actually triggerable) buffer size checks in usage of
404 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
406 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
407 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
408 - When configuring, starting, or stopping an NT service, stop
409 immediately after the service configuration attempt has succeeded
410 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
411 - When sending a NETINFO cell, include the original address
412 received for the other side, not its canonical address. Found
413 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
414 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
415 can pick them up when the tests aren't disabled. Bugfix on
416 0.2.2.4-alpha which introduced tinytest.
417 - Fix a memory leak when we check whether a hidden service
418 descriptor has any usable introduction points left. Fixes bug
419 4424. Bugfix on 0.2.2.25-alpha.
420 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
421 occurred when a client tried to fetch a descriptor for a bridge
422 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
424 o Minor bugfixes (on 0.2.3.x):
425 - Make util unit tests build correctly with MSVC. Bugfix on
426 0.2.3.3-alpha. Patch by Gisle Vanem.
427 - Successfully detect AUTH_CHALLENGE cells with no recognized
428 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
430 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
431 it should still send a NETINFO cell to allow the connection to
432 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
434 - Log less loudly when we get an invalid authentication certificate
435 from a source other than a directory authority: it's not unusual
436 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
438 - Tolerate servers with more clock skew in their authentication
439 certificates than previously. Fixes bug 4371; bugfix on
441 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
442 on 0.2.3.4-alpha and 0.2.3.6-alpha.
445 - Add two new config options for directory authorities:
446 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
447 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
448 that is always sufficient to satisfy the bandwidth requirement for
449 the Guard flag. Now it will be easier for researchers to simulate
450 Tor networks with different values. Resolves ticket 4484.
451 - When Tor ignores a hidden service specified in its configuration,
452 include the hidden service's directory in the warning message.
453 Previously, we would only tell the user that some hidden service
454 was ignored. Bugfix on 0.0.6; fixes bug 4426.
455 - When we fail to initialize Libevent, retry with IOCP disabled so we
456 don't need to turn on multi-threading support in Libevent, which in
457 turn requires a working socketpair(). This is a workaround for bug
458 4457, which affects Libevent versions from 2.0.1-alpha through
460 - Detect when we try to build on a platform that doesn't define
461 AF_UNSPEC to 0. We don't work there, so refuse to compile.
462 - Update to the November 1 2011 Maxmind GeoLite Country database.
465 - Make it easier to automate expert package builds on Windows,
466 by removing an absolute path from makensis.exe command.
468 o Code simplifications and refactoring:
469 - Remove some redundant #include directives throughout the code.
470 Patch from Andrea Gelmini.
471 - Unconditionally use OpenSSL's AES implementation instead of our
472 old built-in one. OpenSSL's AES has been better for a while, and
473 relatively few servers should still be on any version of OpenSSL
474 that doesn't have good optimized assembly AES.
475 - Use the name "CERTS" consistently to refer to the new cell type;
476 we were calling it CERT in some places and CERTS in others.
479 - Numerous new unit tests for functions in util.c and address.c by
481 - The long-disabled benchmark tests are now split into their own
482 ./src/test/bench binary.
483 - The benchmark tests can now use more accurate timers than
484 gettimeofday() when such timers are available.
487 Changes in version 0.2.3.7-alpha - 2011-10-30
488 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
489 the new v3 handshake. It also resolves yet another bridge address
493 - If we mark an OR connection for close based on a cell we process,
494 don't process any further cells on it. We already avoid further
495 reads on marked-for-close connections, but now we also discard the
496 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
497 which was the first version where we might mark a connection for
498 close based on processing a cell on it.
499 - Fix a double-free bug that would occur when we received an invalid
500 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
501 bugfix on 0.2.3.6-alpha.
502 - Bridges no longer include their address in NETINFO cells on outgoing
503 OR connections, to allow them to blend in better with clients.
504 Removes another avenue for enumerating bridges. Reported by
505 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
506 cells were introduced.
509 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
510 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
513 Changes in version 0.2.3.6-alpha - 2011-10-26
514 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
515 anonymity vulnerability where an attacker can deanonymize Tor
516 users. Everybody should upgrade.
518 This release also features support for a new v3 connection handshake
519 protocol, and fixes to make hidden service connections more robust.
522 - Implement a new handshake protocol (v3) for authenticating Tors to
523 each other over TLS. It should be more resistant to fingerprinting
524 than previous protocols, and should require less TLS hacking for
525 future Tor implementations. Implements proposal 176.
526 - Allow variable-length padding cells to disguise the length of
527 Tor's TLS records. Implements part of proposal 184.
529 o Privacy/anonymity fixes (clients):
530 - Clients and bridges no longer send TLS certificate chains on
531 outgoing OR connections. Previously, each client or bridge would
532 use the same cert chain for all outgoing OR connections until
533 its IP address changes, which allowed any relay that the client
534 or bridge contacted to determine which entry guards it is using.
535 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
536 - If a relay receives a CREATE_FAST cell on a TLS connection, it
537 no longer considers that connection as suitable for satisfying a
538 circuit EXTEND request. Now relays can protect clients from the
539 CVE-2011-2768 issue even if the clients haven't upgraded yet.
540 - Directory authorities no longer assign the Guard flag to relays
541 that haven't upgraded to the above "refuse EXTEND requests
542 to client connections" fix. Now directory authorities can
543 protect clients from the CVE-2011-2768 issue even if neither
544 the clients nor the relays have upgraded yet. There's a new
545 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
546 to let us transition smoothly, else tomorrow there would be no
549 o Major bugfixes (hidden services):
550 - Improve hidden service robustness: when an attempt to connect to
551 a hidden service ends, be willing to refetch its hidden service
552 descriptors from each of the HSDir relays responsible for them
553 immediately. Previously, we would not consider refetching the
554 service's descriptors from each HSDir for 15 minutes after the last
555 fetch, which was inconvenient if the hidden service was not running
556 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
557 - When one of a hidden service's introduction points appears to be
558 unreachable, stop trying it. Previously, we would keep trying
559 to build circuits to the introduction point until we lost the
560 descriptor, usually because the user gave up and restarted Tor.
561 Partly fixes bug 3825.
562 - Don't launch a useless circuit after failing to use one of a
563 hidden service's introduction points. Previously, we would
564 launch a new introduction circuit, but not set the hidden service
565 which that circuit was intended to connect to, so it would never
566 actually be used. A different piece of code would then create a
567 new introduction circuit correctly. Bug reported by katmagic and
568 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
570 o Major bugfixes (other):
571 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
572 that they initiated. Relays could distinguish incoming bridge
573 connections from client connections, creating another avenue for
574 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
575 Found by "frosty_un".
576 - Don't update the AccountingSoftLimitHitAt state file entry whenever
577 tor gets started. This prevents a wrong average bandwidth
578 estimate, which would cause relays to always start a new accounting
579 interval at the earliest possible moment. Fixes bug 2003; bugfix
580 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
581 immensely in tracking this bug down.
582 - Fix a crash bug when changing node restrictions while a DNS lookup
583 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
586 o Minor bugfixes (on 0.2.2.x and earlier):
587 - When a hidden service turns an extra service-side introduction
588 circuit into a general-purpose circuit, free the rend_data and
589 intro_key fields first, so we won't leak memory if the circuit
590 is cannibalized for use as another service-side introduction
591 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
592 - Rephrase the log message emitted if the TestSocks check is
593 successful. Patch from Fabian Keil; fixes bug 4094.
594 - Bridges now skip DNS self-tests, to act a little more stealthily.
595 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
596 bridges. Patch by "warms0x".
597 - Remove a confusing dollar sign from the example fingerprint in the
598 man page, and also make the example fingerprint a valid one. Fixes
599 bug 4309; bugfix on 0.2.1.3-alpha.
600 - Fix internal bug-checking logic that was supposed to catch
601 failures in digest generation so that it will fail more robustly
602 if we ask for a nonexistent algorithm. Found by Coverity Scan.
603 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
604 - Report any failure in init_keys() calls launched because our
605 IP address has changed. Spotted by Coverity Scan. Bugfix on
606 0.1.1.4-alpha; fixes CID 484.
608 o Minor bugfixes (on 0.2.3.x):
609 - Fix a bug in configure.in that kept it from building a configure
610 script with autoconf versions earlier than 2.61. Fixes bug 2430;
611 bugfix on 0.2.3.1-alpha.
612 - Don't warn users that they are exposing a client port to the
613 Internet if they have specified an RFC1918 address. Previously,
614 we would warn if the user had specified any non-loopback
615 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
616 - Fix memory leaks in the failing cases of the new SocksPort and
617 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
618 fixes coverity CIDs 485, 486, and 487.
621 - When a hidden service's introduction point times out, consider
622 trying it again during the next attempt to connect to the
623 HS. Previously, we would not try it again unless a newly fetched
624 descriptor contained it. Required by fixes for bugs 1297 and 3825.
625 - The next version of Windows will be called Windows 8, and it has
626 a major version of 6, minor version of 2. Correctly identify that
627 version instead of calling it "Very recent version". Resolves
628 ticket 4153; reported by funkstar.
629 - The Bridge Authority now writes statistics on how many bridge
630 descriptors it gave out in total, and how many unique descriptors
631 it gave out. It also lists how often the most and least commonly
632 fetched descriptors were given out, as well as the median and
633 25th/75th percentile. Implements tickets 4200 and 4294.
634 - Update to the October 4 2011 Maxmind GeoLite Country database.
636 o Code simplifications and refactoring:
637 - Remove some old code to remember statistics about which descriptors
638 we've served as a directory mirror. The feature wasn't used and
639 is outdated now that microdescriptors are around.
640 - Rename Tor functions that turn strings into addresses, so that
641 "parse" indicates that no hostname resolution occurs, and
642 "lookup" indicates that hostname resolution may occur. This
643 should help prevent mistakes in the future. Fixes bug 3512.
646 Changes in version 0.2.2.34 - 2011-10-26
647 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
648 can deanonymize Tor users. Everybody should upgrade.
650 The attack relies on four components: 1) Clients reuse their TLS cert
651 when talking to different relays, so relays can recognize a user by
652 the identity key in her cert. 2) An attacker who knows the client's
653 identity key can probe each guard relay to see if that identity key
654 is connected to that guard relay right now. 3) A variety of active
655 attacks in the literature (starting from "Low-Cost Traffic Analysis
656 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
657 discover the guard relays that a Tor user visiting the website is using.
658 4) Clients typically pick three guards at random, so the set of guards
659 for a given user could well be a unique fingerprint for her. This
660 release fixes components #1 and #2, which is enough to block the attack;
661 the other two remain as open research problems. Special thanks to
662 "frosty_un" for reporting the issue to us!
664 Clients should upgrade so they are no longer recognizable by the TLS
665 certs they present. Relays should upgrade so they no longer allow a
666 remote attacker to probe them to test whether unpatched clients are
667 currently connected to them.
669 This release also fixes several vulnerabilities that allow an attacker
670 to enumerate bridge relays. Some bridge enumeration attacks still
671 remain; see for example proposal 188.
673 o Privacy/anonymity fixes (clients):
674 - Clients and bridges no longer send TLS certificate chains on
675 outgoing OR connections. Previously, each client or bridge would
676 use the same cert chain for all outgoing OR connections until
677 its IP address changes, which allowed any relay that the client
678 or bridge contacted to determine which entry guards it is using.
679 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
680 - If a relay receives a CREATE_FAST cell on a TLS connection, it
681 no longer considers that connection as suitable for satisfying a
682 circuit EXTEND request. Now relays can protect clients from the
683 CVE-2011-2768 issue even if the clients haven't upgraded yet.
684 - Directory authorities no longer assign the Guard flag to relays
685 that haven't upgraded to the above "refuse EXTEND requests
686 to client connections" fix. Now directory authorities can
687 protect clients from the CVE-2011-2768 issue even if neither
688 the clients nor the relays have upgraded yet. There's a new
689 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
690 to let us transition smoothly, else tomorrow there would be no
693 o Privacy/anonymity fixes (bridge enumeration):
694 - Bridge relays now do their directory fetches inside Tor TLS
695 connections, like all the other clients do, rather than connecting
696 directly to the DirPort like public relays do. Removes another
697 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
698 - Bridges relays now build circuits for themselves in a more similar
699 way to how clients build them. Removes another avenue for
700 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
701 when bridges were introduced.
702 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
703 that they initiated. Relays could distinguish incoming bridge
704 connections from client connections, creating another avenue for
705 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
706 Found by "frosty_un".
709 - Fix a crash bug when changing node restrictions while a DNS lookup
710 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
712 - Don't launch a useless circuit after failing to use one of a
713 hidden service's introduction points. Previously, we would
714 launch a new introduction circuit, but not set the hidden service
715 which that circuit was intended to connect to, so it would never
716 actually be used. A different piece of code would then create a
717 new introduction circuit correctly. Bug reported by katmagic and
718 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
721 - Change an integer overflow check in the OpenBSD_Malloc code so
722 that GCC is less likely to eliminate it as impossible. Patch
723 from Mansour Moufid. Fixes bug 4059.
724 - When a hidden service turns an extra service-side introduction
725 circuit into a general-purpose circuit, free the rend_data and
726 intro_key fields first, so we won't leak memory if the circuit
727 is cannibalized for use as another service-side introduction
728 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
729 - Bridges now skip DNS self-tests, to act a little more stealthily.
730 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
731 bridges. Patch by "warms0x".
732 - Fix internal bug-checking logic that was supposed to catch
733 failures in digest generation so that it will fail more robustly
734 if we ask for a nonexistent algorithm. Found by Coverity Scan.
735 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
736 - Report any failure in init_keys() calls launched because our
737 IP address has changed. Spotted by Coverity Scan. Bugfix on
738 0.1.1.4-alpha; fixes CID 484.
740 o Minor bugfixes (log messages and documentation):
741 - Remove a confusing dollar sign from the example fingerprint in the
742 man page, and also make the example fingerprint a valid one. Fixes
743 bug 4309; bugfix on 0.2.1.3-alpha.
744 - The next version of Windows will be called Windows 8, and it has
745 a major version of 6, minor version of 2. Correctly identify that
746 version instead of calling it "Very recent version". Resolves
747 ticket 4153; reported by funkstar.
748 - Downgrade log messages about circuit timeout calibration from
749 "notice" to "info": they don't require or suggest any human
750 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
751 bugfix on 0.2.2.14-alpha.
754 - Turn on directory request statistics by default and include them in
755 extra-info descriptors. Don't break if we have no GeoIP database.
756 Backported from 0.2.3.1-alpha; implements ticket 3951.
757 - Update to the October 4 2011 Maxmind GeoLite Country database.
760 Changes in version 0.2.1.31 - 2011-10-26
761 Tor 0.2.1.31 backports important security and privacy fixes for
762 oldstable. This release is intended only for package maintainers and
763 others who cannot use the 0.2.2 stable series. All others should be
764 using Tor 0.2.2.x or newer.
766 o Security fixes (also included in 0.2.2.x):
767 - Replace all potentially sensitive memory comparison operations
768 with versions whose runtime does not depend on the data being
769 compared. This will help resist a class of attacks where an
770 adversary can use variations in timing information to learn
771 sensitive data. Fix for one case of bug 3122. (Safe memcmp
772 implementation by Robert Ransom based partially on code by DJB.)
773 - Fix an assert in parsing router descriptors containing IPv6
774 addresses. This one took down the directory authorities when
775 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
777 o Privacy/anonymity fixes (also included in 0.2.2.x):
778 - Clients and bridges no longer send TLS certificate chains on
779 outgoing OR connections. Previously, each client or bridge would
780 use the same cert chain for all outgoing OR connections until
781 its IP address changes, which allowed any relay that the client
782 or bridge contacted to determine which entry guards it is using.
783 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
784 - If a relay receives a CREATE_FAST cell on a TLS connection, it
785 no longer considers that connection as suitable for satisfying a
786 circuit EXTEND request. Now relays can protect clients from the
787 CVE-2011-2768 issue even if the clients haven't upgraded yet.
788 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
789 that they initiated. Relays could distinguish incoming bridge
790 connections from client connections, creating another avenue for
791 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
792 Found by "frosty_un".
793 - When receiving a hidden service descriptor, check that it is for
794 the hidden service we wanted. Previously, Tor would store any
795 hidden service descriptors that a directory gave it, whether it
796 wanted them or not. This wouldn't have let an attacker impersonate
797 a hidden service, but it did let directories pre-seed a client
798 with descriptors that it didn't want. Bugfix on 0.0.6.
799 - Avoid linkability based on cached hidden service descriptors: forget
800 all hidden service descriptors cached as a client when processing a
801 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
802 - Make the bridge directory authority refuse to answer directory
803 requests for "all" descriptors. It used to include bridge
804 descriptors in its answer, which was a major information leak.
805 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
806 - Don't attach new streams to old rendezvous circuits after SIGNAL
807 NEWNYM. Previously, we would keep using an existing rendezvous
808 circuit if it remained open (i.e. if it were kept open by a
809 long-lived stream, or if a new stream were attached to it before
810 Tor could notice that it was old and no longer in use). Bugfix on
811 0.1.1.15-rc; fixes bug 3375.
813 o Minor bugfixes (also included in 0.2.2.x):
814 - When we restart our relay, we might get a successful connection
815 from the outside before we've started our reachability tests,
816 triggering a warning: "ORPort found reachable, but I have no
817 routerinfo yet. Failing to inform controller of success." This
818 bug was harmless unless Tor is running under a controller
819 like Vidalia, in which case the controller would never get a
820 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
822 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
823 enabled. Fixes bug 1526.
824 - Remove undocumented option "-F" from tor-resolve: it hasn't done
825 anything since 0.2.1.16-rc.
826 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
827 None of the cases where we did this before were wrong, but by making
828 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
829 - Fix a rare crash bug that could occur when a client was configured
830 with a large number of bridges. Fixes bug 2629; bugfix on
831 0.2.1.2-alpha. Bugfix by trac user "shitlei".
832 - Correct the warning displayed when a rendezvous descriptor exceeds
833 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
835 - Fix an uncommon assertion failure when running with DNSPort under
836 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
837 - When warning about missing zlib development packages during compile,
838 give the correct package names. Bugfix on 0.2.0.1-alpha.
839 - Require that introduction point keys and onion keys have public
840 exponent 65537. Bugfix on 0.2.0.10-alpha.
841 - Do not crash when our configuration file becomes unreadable, for
842 example due to a permissions change, between when we start up
843 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
845 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
847 - Always NUL-terminate the sun_path field of a sockaddr_un before
848 passing it to the kernel. (Not a security issue: kernels are
849 smart enough to reject bad sockaddr_uns.) Found by Coverity;
850 CID #428. Bugfix on Tor 0.2.0.3-alpha.
851 - Don't stack-allocate the list of supplementary GIDs when we're
852 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
853 could take up to 256K, which is way too much stack. Found by
854 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
856 o Minor bugfixes (only in 0.2.1.x):
857 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
858 rely on them. Bugfix on 0.2.1.30.
859 - Use git revisions instead of svn revisions when generating our
860 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
862 o Minor features (also included in 0.2.2.x):
863 - Adjust the expiration time on our SSL session certificates to
864 better match SSL certs seen in the wild. Resolves ticket 4014.
865 - Allow nameservers with IPv6 address. Resolves bug 2574.
866 - Update to the October 4 2011 Maxmind GeoLite Country database.
869 Changes in version 0.2.3.5-alpha - 2011-09-28
870 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
871 bridge relays; fixes an assertion error that many users started hitting
872 today; and adds the ability to refill token buckets more often than
873 once per second, allowing significant performance improvements.
876 - Bridge relays now do their directory fetches inside Tor TLS
877 connections, like all the other clients do, rather than connecting
878 directly to the DirPort like public relays do. Removes another
879 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
880 - Bridges relays now build circuits for themselves in a more similar
881 way to how clients build them. Removes another avenue for
882 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
883 when bridges were introduced.
886 - Fix an "Assertion md->held_by_node == 1 failed" error that could
887 occur when the same microdescriptor was referenced by two node_t
888 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
890 o Major features (networking):
891 - Add a new TokenBucketRefillInterval option to refill token buckets
892 more frequently than once per second. This should improve network
893 performance, alleviate queueing problems, and make traffic less
894 bursty. Implements proposal 183; closes ticket 3630. Design by
895 Florian Tschorsch and Björn Scheuermann; implementation by
899 - Change an integer overflow check in the OpenBSD_Malloc code so
900 that GCC is less likely to eliminate it as impossible. Patch
901 from Mansour Moufid. Fixes bug 4059.
903 o Minor bugfixes (usability):
904 - Downgrade log messages about circuit timeout calibration from
905 "notice" to "info": they don't require or suggest any human
906 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
907 bugfix on 0.2.2.14-alpha.
909 o Minor features (diagnostics):
910 - When the system call to create a listener socket fails, log the
911 error message explaining why. This may help diagnose bug 4027.
914 Changes in version 0.2.3.4-alpha - 2011-09-13
915 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
916 tweak to Tor's TLS handshake that makes relays and bridges that run
917 this new version reachable from Iran again. It also fixes a few new
918 bugs in 0.2.3.x, and teaches relays to recognize when they're not
919 listed in the network consensus and republish.
921 o Major bugfixes (also part of 0.2.2.33):
922 - Avoid an assertion failure when reloading a configuration with
923 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
924 3923; bugfix on 0.2.2.25-alpha.
926 o Minor features (security, also part of 0.2.2.33):
927 - Check for replays of the public-key encrypted portion of an
928 INTRODUCE1 cell, in addition to the current check for replays of
929 the g^x value. This prevents a possible class of active attacks
930 by an attacker who controls both an introduction point and a
931 rendezvous point, and who uses the malleability of AES-CTR to
932 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
933 that these attacks is infeasible (requiring the attacker to send
934 on the order of zettabytes of altered cells in a short interval),
935 but we'd rather block them off in case there are any classes of
936 this attack that we missed. Reported by Willem Pinckaers.
938 o Minor features (also part of 0.2.2.33):
939 - Adjust the expiration time on our SSL session certificates to
940 better match SSL certs seen in the wild. Resolves ticket 4014.
941 - Change the default required uptime for a relay to be accepted as
942 a HSDir (hidden service directory) from 24 hours to 25 hours.
943 Improves on 0.2.0.10-alpha; resolves ticket 2649.
944 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
945 authorities to abstain from voting on assignment of the HSDir
946 consensus flag. Related to bug 2649.
947 - Update to the September 6 2011 Maxmind GeoLite Country database.
949 o Minor bugfixes (also part of 0.2.2.33):
950 - Demote the 'replay detected' log message emitted when a hidden
951 service receives the same Diffie-Hellman public key in two different
952 INTRODUCE2 cells to info level. A normal Tor client can cause that
953 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
954 fixes part of bug 2442.
955 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
956 level. There is nothing that a hidden service's operator can do
957 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
959 - Clarify a log message specifying the characters permitted in
960 HiddenServiceAuthorizeClient client names. Previously, the log
961 message said that "[A-Za-z0-9+-_]" were permitted; that could have
962 given the impression that every ASCII character between "+" and "_"
963 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
965 o Build fixes (also part of 0.2.2.33):
966 - Clean up some code issues that prevented Tor from building on older
967 BSDs. Fixes bug 3894; reported by "grarpamp".
968 - Search for a platform-specific version of "ar" when cross-compiling.
969 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
972 - Fix a bug where the SocksPort option (for example) would get
973 ignored and replaced by the default if a SocksListenAddress
974 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
978 - Relays now try regenerating and uploading their descriptor more
979 frequently if they are not listed in the consensus, or if the
980 version of their descriptor listed in the consensus is too
981 old. This fix should prevent situations where a server declines
982 to re-publish itself because it has done so too recently, even
983 though the authorities decided not to list its recent-enough
984 descriptor. Fix for bug 3327.
987 - Relays now include a reason for regenerating their descriptors
988 in an HTTP header when uploading to the authorities. This will
989 make it easier to debug descriptor-upload issues in the future.
990 - When starting as root and then changing our UID via the User
991 control option, and we have a ControlSocket configured, make sure
992 that the ControlSocket is owned by the same account that Tor will
993 run under. Implements ticket 3421; fix by Jérémy Bobbio.
996 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
997 utility function used in the control-port code). This shouldn't
998 ever happen unless Tor is completely out of memory, but if it did
999 happen and Tor somehow recovered from it, Tor could have sent a log
1000 message to a control port in the middle of a reply to a controller
1001 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
1002 - Make 'FetchUselessDescriptors' cause all descriptor types and
1003 all consensus types (including microdescriptors) to get fetched.
1004 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
1007 - Make a new "entry connection" struct as an internal subtype of "edge
1008 connection", to simplify the code and make exit connections smaller.
1011 Changes in version 0.2.2.33 - 2011-09-13
1012 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
1013 TLS handshake that makes relays and bridges that run this new version
1014 reachable from Iran again.
1017 - Avoid an assertion failure when reloading a configuration with
1018 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
1019 3923; bugfix on 0.2.2.25-alpha.
1021 o Minor features (security):
1022 - Check for replays of the public-key encrypted portion of an
1023 INTRODUCE1 cell, in addition to the current check for replays of
1024 the g^x value. This prevents a possible class of active attacks
1025 by an attacker who controls both an introduction point and a
1026 rendezvous point, and who uses the malleability of AES-CTR to
1027 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
1028 that these attacks are infeasible (requiring the attacker to send
1029 on the order of zettabytes of altered cells in a short interval),
1030 but we'd rather block them off in case there are any classes of
1031 this attack that we missed. Reported by Willem Pinckaers.
1034 - Adjust the expiration time on our SSL session certificates to
1035 better match SSL certs seen in the wild. Resolves ticket 4014.
1036 - Change the default required uptime for a relay to be accepted as
1037 a HSDir (hidden service directory) from 24 hours to 25 hours.
1038 Improves on 0.2.0.10-alpha; resolves ticket 2649.
1039 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
1040 authorities to abstain from voting on assignment of the HSDir
1041 consensus flag. Related to bug 2649.
1042 - Update to the September 6 2011 Maxmind GeoLite Country database.
1044 o Minor bugfixes (documentation and log messages):
1045 - Correct the man page to explain that HashedControlPassword and
1046 CookieAuthentication can both be set, in which case either method
1047 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
1048 when we decided to allow these config options to both be set. Issue
1050 - Demote the 'replay detected' log message emitted when a hidden
1051 service receives the same Diffie-Hellman public key in two different
1052 INTRODUCE2 cells to info level. A normal Tor client can cause that
1053 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
1054 fixes part of bug 2442.
1055 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
1056 level. There is nothing that a hidden service's operator can do
1057 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
1059 - Clarify a log message specifying the characters permitted in
1060 HiddenServiceAuthorizeClient client names. Previously, the log
1061 message said that "[A-Za-z0-9+-_]" were permitted; that could have
1062 given the impression that every ASCII character between "+" and "_"
1063 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
1066 - Provide a substitute implementation of lround() for MSVC, which
1067 apparently lacks it. Patch from Gisle Vanem.
1068 - Clean up some code issues that prevented Tor from building on older
1069 BSDs. Fixes bug 3894; reported by "grarpamp".
1070 - Search for a platform-specific version of "ar" when cross-compiling.
1071 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
1074 Changes in version 0.2.3.3-alpha - 2011-09-01
1075 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
1076 security, and provides client-side support for the microdescriptor
1077 and optimistic data features introduced earlier in the 0.2.3.x
1078 series. It also includes numerous critical bugfixes in the (optional)
1079 bufferevent-based networking backend.
1081 o Major features (stream isolation):
1082 - You can now configure Tor so that streams from different
1083 applications are isolated on different circuits, to prevent an
1084 attacker who sees your streams as they leave an exit node from
1085 linking your sessions to one another. To do this, choose some way
1086 to distinguish the applications: have them connect to different
1087 SocksPorts, or have one of them use SOCKS4 while the other uses
1088 SOCKS5, or have them pass different authentication strings to the
1089 SOCKS proxy. Then, use the new SocksPort syntax to configure the
1090 degree of isolation you need. This implements Proposal 171.
1091 - There's a new syntax for specifying multiple client ports (such as
1092 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
1093 multiple *Port entries with full addr:port syntax on each.
1094 The old *ListenAddress format is still supported, but you can't
1095 mix it with the new *Port syntax.
1097 o Major features (other):
1098 - Enable microdescriptor fetching by default for clients. This allows
1099 clients to download a much smaller amount of directory information.
1100 To disable it (and go back to the old-style consensus and
1101 descriptors), set "UseMicrodescriptors 0" in your torrc file.
1102 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
1103 "PortForwarding" config option), now supports Windows.
1104 - When using an exit relay running 0.2.3.x, clients can now
1105 "optimistically" send data before the exit relay reports that
1106 the stream has opened. This saves a round trip when starting
1107 connections where the client speaks first (such as web browsing).
1108 This behavior is controlled by a consensus parameter (currently
1109 disabled). To turn it on or off manually, use the "OptimisticData"
1110 torrc option. Implements proposal 181; code by Ian Goldberg.
1112 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
1113 - When using IOCP on Windows, we need to enable Libevent windows
1115 - The IOCP backend now works even when the user has not specified
1116 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
1117 Fixes part of bug 3752.
1118 - Correctly record the bytes we've read and written when using
1119 bufferevents, so that we can include them in our bandwidth history
1120 and advertised bandwidth. Fixes bug 3803.
1121 - Apply rate-limiting only at the bottom of a chain of filtering
1122 bufferevents. This prevents us from filling up internal read
1123 buffers and violating rate-limits when filtering bufferevents
1124 are enabled. Fixes part of bug 3804.
1125 - Add high-watermarks to the output buffers for filtered
1126 bufferevents. This prevents us from filling up internal write
1127 buffers and wasting CPU cycles when filtering bufferevents are
1128 enabled. Fixes part of bug 3804.
1129 - Correctly notice when data has been written from a bufferevent
1130 without flushing it completely. Fixes bug 3805.
1131 - Fix a bug where server-side tunneled bufferevent-based directory
1132 streams would get closed prematurely. Fixes bug 3814.
1133 - Fix a use-after-free error with per-connection rate-limiting
1134 buckets. Fixes bug 3888.
1136 o Major bugfixes (also part of 0.2.2.31-rc):
1137 - If we're configured to write our ControlPorts to disk, only write
1138 them after switching UID and creating the data directory. This way,
1139 we don't fail when starting up with a nonexistent DataDirectory
1140 and a ControlPortWriteToFile setting based on that directory. Fixes
1141 bug 3747; bugfix on Tor 0.2.2.26-beta.
1144 - Added a new CONF_CHANGED event so that controllers can be notified
1145 of any configuration changes made by other controllers, or by the
1146 user. Implements ticket 1692.
1147 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
1148 leak when using bufferevents, and lets Libevent worry about how to
1149 best copy data out of a buffer.
1150 - Replace files in stats/ rather than appending to them. Now that we
1151 include statistics in extra-info descriptors, it makes no sense to
1152 keep old statistics forever. Implements ticket 2930.
1154 o Minor features (build compatibility):
1155 - Limited, experimental support for building with nmake and MSVC.
1156 - Provide a substitute implementation of lround() for MSVC, which
1157 apparently lacks it. Patch from Gisle Vanem.
1159 o Minor features (also part of 0.2.2.31-rc):
1160 - Update to the August 2 2011 Maxmind GeoLite Country database.
1162 o Minor bugfixes (on 0.2.3.x-alpha):
1163 - Fix a spurious warning when parsing SOCKS requests with
1164 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
1165 - Get rid of a harmless warning that could happen on relays running
1166 with bufferevents. The warning was caused by someone doing an http
1167 request to a relay's orport. Also don't warn for a few related
1168 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
1170 o Minor bugfixes (on 2.2.x and earlier):
1171 - Correct the man page to explain that HashedControlPassword and
1172 CookieAuthentication can both be set, in which case either method
1173 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
1174 when we decided to allow these config options to both be set. Issue
1176 - The "--quiet" and "--hush" options now apply not only to Tor's
1177 behavior before logs are configured, but also to Tor's behavior in
1178 the absense of configured logs. Fixes bug 3550; bugfix on
1181 o Minor bugfixes (also part of 0.2.2.31-rc):
1182 - Write several files in text mode, on OSes that distinguish text
1183 mode from binary mode (namely, Windows). These files are:
1184 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
1185 that collect those statistics; 'client_keys' and 'hostname' for
1186 hidden services that use authentication; and (in the tor-gencert
1187 utility) newly generated identity and signing keys. Previously,
1188 we wouldn't specify text mode or binary mode, leading to an
1189 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
1190 the DirRecordUsageByCountry option which would have triggered
1191 the assertion failure was added), although this assertion failure
1192 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
1193 - Selectively disable deprecation warnings on OS X because Lion
1194 started deprecating the shipped copy of openssl. Fixes bug 3643.
1195 - Remove an extra pair of quotation marks around the error
1196 message in control-port STATUS_GENERAL BUG events. Bugfix on
1197 0.1.2.6-alpha; fixes bug 3732.
1198 - When unable to format an address as a string, report its value
1199 as "???" rather than reusing the last formatted address. Bugfix
1202 o Code simplifications and refactoring:
1203 - Rewrite the listener-selection logic so that parsing which ports
1204 we want to listen on is now separate from binding to the ports
1208 - Building Tor with bufferevent support now requires Libevent
1209 2.0.13-stable or later. Previous versions of Libevent had bugs in
1210 SSL-related bufferevents and related issues that would make Tor
1211 work badly with bufferevents. Requiring 2.0.13-stable also allows
1212 Tor with bufferevents to take advantage of Libevent APIs
1213 introduced after 2.0.8-rc.
1216 Changes in version 0.2.2.32 - 2011-08-27
1217 The Tor 0.2.2 release series is dedicated to the memory of Andreas
1218 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
1219 a founder of the PETS community, a leader in our field, a mentor,
1220 and a friend. He left us with these words: "I had the possibility
1221 to contribute to this world that is not as it should be. I hope I
1222 could help in some areas to make the world a better place, and that
1223 I could also encourage other people to be engaged in improving the
1224 world. Please, stay engaged. This world needs you, your love, your
1225 initiative -- now I cannot be part of that anymore."
1227 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
1228 ready. More than two years in the making, this release features improved
1229 client performance and hidden service reliability, better compatibility
1230 for Android, correct behavior for bridges that listen on more than
1231 one address, more extensible and flexible directory object handling,
1232 better reporting of network statistics, improved code security, and
1233 many many other features and bugfixes.
1236 Changes in version 0.2.2.31-rc - 2011-08-17
1237 Tor 0.2.2.31-rc is the second and hopefully final release candidate
1238 for the Tor 0.2.2.x series.
1241 - Remove an extra pair of quotation marks around the error
1242 message in control-port STATUS_GENERAL BUG events. Bugfix on
1243 0.1.2.6-alpha; fixes bug 3732.
1244 - If we're configured to write our ControlPorts to disk, only write
1245 them after switching UID and creating the data directory. This way,
1246 we don't fail when starting up with a nonexistent DataDirectory
1247 and a ControlPortWriteToFile setting based on that directory. Fixes
1248 bug 3747; bugfix on Tor 0.2.2.26-beta.
1251 - Update to the August 2 2011 Maxmind GeoLite Country database.
1254 - Allow GETINFO fingerprint to return a fingerprint even when
1255 we have not yet built a router descriptor. Fixes bug 3577;
1256 bugfix on 0.2.0.1-alpha.
1257 - Write several files in text mode, on OSes that distinguish text
1258 mode from binary mode (namely, Windows). These files are:
1259 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
1260 that collect those statistics; 'client_keys' and 'hostname' for
1261 hidden services that use authentication; and (in the tor-gencert
1262 utility) newly generated identity and signing keys. Previously,
1263 we wouldn't specify text mode or binary mode, leading to an
1264 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
1265 the DirRecordUsageByCountry option which would have triggered
1266 the assertion failure was added), although this assertion failure
1267 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
1268 - Selectively disable deprecation warnings on OS X because Lion
1269 started deprecating the shipped copy of openssl. Fixes bug 3643.
1270 - When unable to format an address as a string, report its value
1271 as "???" rather than reusing the last formatted address. Bugfix
1275 Changes in version 0.2.3.2-alpha - 2011-07-18
1276 Tor 0.2.3.2-alpha introduces two new experimental features:
1277 microdescriptors and pluggable transports. It also continues cleaning
1278 up a variety of recently introduced features.
1281 - Clients can now use microdescriptors instead of regular descriptors
1282 to build circuits. Microdescriptors are authority-generated
1283 summaries of regular descriptors' contents, designed to change
1284 very rarely (see proposal 158 for details). This feature is
1285 designed to save bandwidth, especially for clients on slow internet
1286 connections. It's off by default for now, since nearly no caches
1287 support it, but it will be on-by-default for clients in a future
1288 version. You can use the UseMicrodescriptors option to turn it on.
1289 - Tor clients using bridges can now be configured to use a separate
1290 'transport' proxy for each bridge. This approach helps to resist
1291 censorship by allowing bridges to use protocol obfuscation
1292 plugins. It implements part of proposal 180. Implements ticket 2841.
1293 - While we're trying to bootstrap, record how many TLS connections
1294 fail in each state, and report which states saw the most failures
1295 in response to any bootstrap failures. This feature may speed up
1296 diagnosis of censorship events. Implements ticket 3116.
1298 o Major bugfixes (on 0.2.3.1-alpha):
1299 - When configuring a large set of nodes in EntryNodes (as with
1300 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
1301 random subset to be guards, and choose them in random
1302 order. Fixes bug 2798.
1303 - Tor could crash when remembering a consensus in a non-used consensus
1304 flavor without having a current consensus set. Fixes bug 3361.
1305 - Comparing an unknown address to a microdescriptor's shortened exit
1306 policy would always give a "rejected" result. Fixes bug 3599.
1307 - Using microdescriptors as a client no longer prevents Tor from
1308 uploading and downloading hidden service descriptors. Fixes
1312 - Allow nameservers with IPv6 address. Resolves bug 2574.
1313 - Accept attempts to include a password authenticator in the
1314 handshake, as supported by SOCKS5. This handles SOCKS clients that
1315 don't know how to omit a password when authenticating. Resolves
1317 - When configuring a large set of nodes in EntryNodes, and there are
1318 enough of them listed as Guard so that we don't need to consider
1319 the non-guard entries, prefer the ones listed with the Guard flag.
1320 - Check for and recover from inconsistency in the microdescriptor
1321 cache. This will make it harder for us to accidentally free a
1322 microdescriptor without removing it from the appropriate data
1323 structures. Fixes issue 3135; issue noted by "wanoskarnet".
1324 - Log SSL state transitions at log level DEBUG, log domain
1325 HANDSHAKE. This can be useful for debugging censorship events.
1326 Implements ticket 3264.
1327 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
1328 implements ticket 3439.
1330 o Minor bugfixes (on 0.2.3.1-alpha):
1331 - Do not free all general-purpose regular descriptors just
1332 because microdescriptor use is enabled. Fixes bug 3113.
1333 - Correctly link libevent_openssl when --enable-static-libevent
1334 is passed to configure. Fixes bug 3118.
1335 - Bridges should not complain during their heartbeat log messages that
1336 they are unlisted in the consensus: that's more or less the point
1337 of being a bridge. Fixes bug 3183.
1338 - Report a SIGNAL event to controllers when acting on a delayed
1339 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
1340 event to the controller if we acted on a SIGNAL NEWNYM command
1341 immediately, and otherwise not report a SIGNAL event for the
1342 command at all. Fixes bug 3349.
1343 - Fix a crash when handling the SIGNAL controller command or
1344 reporting ERR-level status events with bufferevents enabled. Found
1345 by Robert Ransom. Fixes bug 3367.
1346 - Always ship the tor-fw-helper manpage in our release tarballs.
1347 Fixes bug 3389. Reported by Stephen Walker.
1348 - Fix a class of double-mark-for-close bugs when bufferevents
1349 are enabled. Fixes bug 3403.
1350 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
1351 - Add SIGNAL to the list returned by the 'GETINFO events/names'
1352 control-port command. Fixes part of bug 3465.
1353 - Prevent using negative indices during unit test runs when read_all()
1354 fails. Spotted by coverity.
1355 - Fix a rare memory leak when checking the nodelist without it being
1356 present. Found by coverity.
1357 - Only try to download a microdescriptor-flavored consensus from
1358 a directory cache that provides them.
1360 o Minor bugfixes (on 0.2.2.x and earlier):
1361 - Assert that hidden-service-related operations are not performed
1362 using single-hop circuits. Previously, Tor would assert that
1363 client-side streams are not attached to single-hop circuits,
1364 but not that other sensitive operations on the client and service
1365 side are not performed using single-hop circuits. Fixes bug 3332;
1367 - Don't publish a new relay descriptor when we reload our onion key,
1368 unless the onion key has actually changed. Fixes bug 3263 and
1369 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
1370 - Allow GETINFO fingerprint to return a fingerprint even when
1371 we have not yet built a router descriptor. Fixes bug 3577;
1372 bugfix on 0.2.0.1-alpha.
1373 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
1374 on 0.2.2.4-alpha; fixes bug 3427.
1376 o Code simplification and refactoring:
1377 - Use tor_sscanf() in place of scanf() in more places through the
1378 code. This makes us a little more locale-independent, and
1379 should help shut up code-analysis tools that can't tell
1380 a safe sscanf string from a dangerous one.
1381 - Use tt_assert(), not tor_assert(), for checking for test failures.
1382 This makes the unit tests more able to go on in the event that
1384 - Split connection_about_to_close() into separate functions for each
1388 - On Windows, we now define the _WIN32_WINNT macros only if they
1389 are not already defined. This lets the person building Tor decide,
1390 if they want, to require a later version of Windows.
1393 Changes in version 0.2.2.30-rc - 2011-07-07
1394 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
1395 series. It fixes a few smaller bugs, but generally appears stable.
1396 Please test it and let us know whether it is!
1399 - Send a SUCCEEDED stream event to the controller when a reverse
1400 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
1401 discovered by katmagic.
1402 - Always NUL-terminate the sun_path field of a sockaddr_un before
1403 passing it to the kernel. (Not a security issue: kernels are
1404 smart enough to reject bad sockaddr_uns.) Found by Coverity;
1405 CID #428. Bugfix on Tor 0.2.0.3-alpha.
1406 - Don't stack-allocate the list of supplementary GIDs when we're
1407 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
1408 could take up to 256K, which is way too much stack. Found by
1409 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
1410 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
1411 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
1412 fixes part of bug 3465.
1413 - Fix a memory leak when receiving a descriptor for a hidden
1414 service we didn't ask for. Found by Coverity; CID #30. Bugfix
1418 - Update to the July 1 2011 Maxmind GeoLite Country database.
1421 Changes in version 0.2.2.29-beta - 2011-06-20
1422 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
1423 have bridge lines in their torrc but don't want to use them; gets
1424 us closer to having the control socket feature working on Debian;
1425 and fixes a variety of smaller bugs.
1428 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
1429 When we changed the default behavior to "use bridges if any
1430 are listed in the torrc", we surprised users who had bridges
1431 in their torrc files but who didn't actually want to use them.
1432 Partial resolution for bug 3354.
1435 - Don't attach new streams to old rendezvous circuits after SIGNAL
1436 NEWNYM. Previously, we would keep using an existing rendezvous
1437 circuit if it remained open (i.e. if it were kept open by a
1438 long-lived stream, or if a new stream were attached to it before
1439 Tor could notice that it was old and no longer in use). Bugfix on
1440 0.1.1.15-rc; fixes bug 3375.
1443 - Fix a bug when using ControlSocketsGroupWritable with User. The
1444 directory's group would be checked against the current group, not
1445 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
1446 bugfix on 0.2.2.26-beta.
1447 - Make connection_printf_to_buf()'s behaviour sane. Its callers
1448 expect it to emit a CRLF iff the format string ends with CRLF;
1449 it actually emitted a CRLF iff (a) the format string ended with
1450 CRLF or (b) the resulting string was over 1023 characters long or
1451 (c) the format string did not end with CRLF *and* the resulting
1452 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
1453 fixes part of bug 3407.
1454 - Make send_control_event_impl()'s behaviour sane. Its callers
1455 expect it to always emit a CRLF at the end of the string; it
1456 might have emitted extra control characters as well. Bugfix on
1457 0.1.1.9-alpha; fixes another part of bug 3407.
1458 - Make crypto_rand_int() check the value of its input correctly.
1459 Previously, it accepted values up to UINT_MAX, but could return a
1460 negative number if given a value above INT_MAX+1. Found by George
1461 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
1462 - Avoid a segfault when reading a malformed circuit build state
1463 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
1465 - When asked about a DNS record type we don't support via a
1466 client DNSPort, reply with NOTIMPL rather than an empty
1467 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
1468 - Fix a rare memory leak during stats writing. Found by coverity.
1471 - Update to the June 1 2011 Maxmind GeoLite Country database.
1473 o Code simplifications and refactoring:
1474 - Remove some dead code as indicated by coverity.
1475 - Remove a few dead assignments during router parsing. Found by
1477 - Add some forgotten return value checks during unit tests. Found
1479 - Don't use 1-bit wide signed bit fields. Found by coverity.
1482 Changes in version 0.2.2.28-beta - 2011-06-04
1483 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
1484 fixed a big bug in whether relays stay in the consensus consistently,
1485 we moved closer to handling bridges and hidden services correctly,
1486 and we started the process of better handling the dreaded "my Vidalia
1487 died, and now my Tor demands a password when I try to reconnect to it"
1491 - Don't decide to make a new descriptor when receiving a HUP signal.
1492 This bug has caused a lot of 0.2.2.x relays to disappear from the
1493 consensus periodically. Fixes the most common case of triggering
1494 bug 1810; bugfix on 0.2.2.7-alpha.
1495 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
1496 - Don't try to build descriptors if "ORPort auto" is set and we
1497 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
1499 - Resolve a crash that occurred when setting BridgeRelay to 1 with
1500 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
1501 - Apply circuit timeouts to opened hidden-service-related circuits
1502 based on the correct start time. Previously, we would apply the
1503 circuit build timeout based on time since the circuit's creation;
1504 it was supposed to be applied based on time since the circuit
1505 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
1506 - Use the same circuit timeout for client-side introduction
1507 circuits as for other four-hop circuits, rather than the timeout
1508 for single-hop directory-fetch circuits; the shorter timeout may
1509 have been appropriate with the static circuit build timeout in
1510 0.2.1.x and earlier, but caused many hidden service access attempts
1511 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
1512 on 0.2.2.2-alpha; fixes another part of bug 1297.
1513 - In ticket 2511 we fixed a case where you could use an unconfigured
1514 bridge if you had configured it as a bridge the last time you ran
1515 Tor. Now fix another edge case: if you had configured it as a bridge
1516 but then switched to a different bridge via the controller, you
1517 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
1521 - Add an __OwningControllerProcess configuration option and a
1522 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
1523 that when it exits, Tor will shut down. Implements feature 3049.
1524 - If "UseBridges 1" is set and no bridges are configured, Tor will
1525 now refuse to build any circuits until some bridges are set.
1526 If "UseBridges auto" is set, Tor will use bridges if they are
1527 configured and we are not running as a server, but otherwise will
1528 make circuits as usual. The new default is "auto". Patch by anonym,
1529 so the Tails LiveCD can stop automatically revealing you as a Tor
1533 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
1534 - Remove a trailing asterisk from "exit-policy/default" in the
1535 output of the control port command "GETINFO info/names". Bugfix
1537 - Use a wide type to hold sockets when built for 64-bit Windows builds.
1539 - Warn when the user configures two HiddenServiceDir lines that point
1540 to the same directory. Bugfix on 0.0.6 (the version introducing
1541 HiddenServiceDir); fixes bug 3289.
1542 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
1543 part of bug 2748; bugfix on 0.2.0.10-alpha.
1544 - Log malformed requests for rendezvous descriptors as protocol
1545 warnings, not warnings. Also, use a more informative log message
1546 in case someone sees it at log level warning without prior
1547 info-level messages. Fixes the other part of bug 2748; bugfix
1549 - Clear the table recording the time of the last request for each
1550 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
1551 Previously, we would clear our HS descriptor cache on SIGNAL
1552 NEWNYM, but if we had previously retrieved a descriptor (or tried
1553 to) from every directory responsible for it, we would refuse to
1554 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
1556 - Fix a log message that said "bits" while displaying a value in
1557 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
1559 - When checking for 1024-bit keys, check for 1024 bits, not 128
1560 bytes. This allows Tor to correctly discard keys of length 1017
1561 through 1023. Bugfix on 0.0.9pre5.
1564 - Relays now log the reason for publishing a new relay descriptor,
1565 so we have a better chance of hunting down instances of bug 1810.
1566 Resolves ticket 3252.
1567 - Revise most log messages that refer to nodes by nickname to
1568 instead use the "$key=nickname at address" format. This should be
1569 more useful, especially since nicknames are less and less likely
1570 to be unique. Resolves ticket 3045.
1571 - Log (at info level) when purging pieces of hidden-service-client
1572 state because of SIGNAL NEWNYM.
1575 - Remove undocumented option "-F" from tor-resolve: it hasn't done
1576 anything since 0.2.1.16-rc.
1579 Changes in version 0.2.2.27-beta - 2011-05-18
1580 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
1581 release, and also adds a few more general bugfixes.
1584 - Fix a crash bug when changing bridges in a running Tor process.
1585 Fixes bug 3213; bugfix on 0.2.2.26-beta.
1586 - When the controller configures a new bridge, don't wait 10 to 60
1587 seconds before trying to fetch its descriptor. Bugfix on
1588 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
1591 - Require that onion keys have exponent 65537 in microdescriptors too.
1592 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
1593 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
1594 Changed the limit to 512 characters by removing base64 newlines.
1595 Fixes bug 2752. Fix by Michael Yakubovich.
1596 - When a client starts or stops using bridges, never use a circuit
1597 that was built before the configuration change. This behavior could
1598 put at risk a user who uses bridges to ensure that her traffic
1599 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
1603 Changes in version 0.2.2.26-beta - 2011-05-17
1604 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
1605 also introduces a new "socksport auto" approach that should make it
1606 easier to run multiple Tors on the same system, and does a lot of
1607 cleanup to get us closer to a release candidate.
1609 o Security/privacy fixes:
1610 - Replace all potentially sensitive memory comparison operations
1611 with versions whose runtime does not depend on the data being
1612 compared. This will help resist a class of attacks where an
1613 adversary can use variations in timing information to learn
1614 sensitive data. Fix for one case of bug 3122. (Safe memcmp
1615 implementation by Robert Ransom based partially on code by DJB.)
1616 - When receiving a hidden service descriptor, check that it is for
1617 the hidden service we wanted. Previously, Tor would store any
1618 hidden service descriptors that a directory gave it, whether it
1619 wanted them or not. This wouldn't have let an attacker impersonate
1620 a hidden service, but it did let directories pre-seed a client
1621 with descriptors that it didn't want. Bugfix on 0.0.6.
1622 - On SIGHUP, do not clear out all TrackHostExits mappings, client
1623 DNS cache entries, and virtual address mappings: that's what
1624 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
1627 - The options SocksPort, ControlPort, and so on now all accept a
1628 value "auto" that opens a socket on an OS-selected port. A
1629 new ControlPortWriteToFile option tells Tor to write its
1630 actual control port or ports to a chosen file. If the option
1631 ControlPortFileGroupReadable is set, the file is created as
1632 group-readable. Now users can run two Tor clients on the same
1633 system without needing to manually mess with parameters. Resolves
1634 part of ticket 3076.
1635 - Set SO_REUSEADDR on all sockets, not just listeners. This should
1636 help busy exit nodes avoid running out of useable ports just
1637 because all the ports have been used in the near past. Resolves
1641 - New "GETINFO net/listeners/(type)" controller command to return
1642 a list of addresses and ports that are bound for listeners for a
1643 given connection type. This is useful when the user has configured
1644 "SocksPort auto" and the controller needs to know which port got
1645 chosen. Resolves another part of ticket 3076.
1646 - Add a new ControlSocketsGroupWritable configuration option: when
1647 it is turned on, ControlSockets are group-writeable by the default
1648 group of the current user. Patch by Jérémy Bobbio; implements
1650 - Tor now refuses to create a ControlSocket in a directory that is
1651 world-readable (or group-readable if ControlSocketsGroupWritable
1652 is 0). This is necessary because some operating systems do not
1653 enforce permissions on an AF_UNIX sockets. Permissions on the
1654 directory holding the socket, however, seems to work everywhere.
1655 - Rate-limit a warning about failures to download v2 networkstatus
1656 documents. Resolves part of bug 1352.
1657 - Backport code from 0.2.3.x that allows directory authorities to
1658 clean their microdescriptor caches. Needed to resolve bug 2230.
1659 - When an HTTPS proxy reports "403 Forbidden", we now explain
1660 what it means rather than calling it an unexpected status code.
1661 Closes bug 2503. Patch from Michael Yakubovich.
1662 - Update to the May 1 2011 Maxmind GeoLite Country database.
1665 - Authorities now clean their microdesc cache periodically and when
1666 reading from disk initially, not only when adding new descriptors.
1667 This prevents a bug where we could lose microdescriptors. Bugfix
1668 on 0.2.2.6-alpha. Fixes bug 2230.
1669 - Do not crash when our configuration file becomes unreadable, for
1670 example due to a permissions change, between when we start up
1671 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
1673 - Avoid a bug that would keep us from replacing a microdescriptor
1674 cache on Windows. (We would try to replace the file while still
1675 holding it open. That's fine on Unix, but Windows doesn't let us
1676 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
1677 - Add missing explanations for the authority-related torrc options
1678 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
1679 man page. Resolves issue 2379.
1680 - As an authority, do not upload our own vote or signature set to
1681 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
1682 it would get flagged as a duplicate. Resolves bug 3026.
1683 - Accept hidden service descriptors if we think we might be a hidden
1684 service directory, regardless of what our consensus says. This
1685 helps robustness, since clients and hidden services can sometimes
1686 have a more up-to-date view of the network consensus than we do,
1687 and if they think that the directory authorities list us a HSDir,
1688 we might actually be one. Related to bug 2732; bugfix on
1690 - When a controller changes TrackHostExits, remove mappings for
1691 hosts that should no longer have their exits tracked. Bugfix on
1693 - When a controller changes VirtualAddrNetwork, remove any mappings
1694 for hosts that were automapped to the old network. Bugfix on
1696 - When a controller changes one of the AutomapHosts* options, remove
1697 any mappings for hosts that should no longer be automapped. Bugfix
1699 - Do not reset the bridge descriptor download status every time we
1700 re-parse our configuration or get a configuration change. Fixes
1701 bug 3019; bugfix on 0.2.0.3-alpha.
1703 o Minor bugfixes (code cleanup):
1704 - When loading the microdesc journal, remember its current size.
1705 In 0.2.2, this helps prevent the microdesc journal from growing
1706 without limit on authorities (who are the only ones to use it in
1707 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
1708 Fix posted by "cypherpunks."
1709 - The microdesc journal is supposed to get rebuilt only if it is
1710 at least _half_ the length of the store, not _twice_ the length
1711 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
1712 - Fix a potential null-pointer dereference while computing a
1713 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
1715 - Avoid a possible null-pointer dereference when rebuilding the mdesc
1716 cache without actually having any descriptors to cache. Bugfix on
1717 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
1718 - If we fail to compute the identity digest of a v3 legacy keypair,
1719 warn, and don't use a buffer-full of junk instead. Bugfix on
1720 0.2.1.1-alpha; fixes bug 3106.
1721 - Resolve an untriggerable issue in smartlist_string_num_isin(),
1722 where if the function had ever in the future been used to check
1723 for the presence of a too-large number, it would have given an
1724 incorrect result. (Fortunately, we only used it for 16-bit
1725 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
1726 - Require that introduction point keys and onion handshake keys
1727 have a public exponent of 65537. Starts to fix bug 3207; bugfix
1731 - Caches no longer download and serve v2 networkstatus documents
1732 unless FetchV2Networkstatus flag is set: these documents haven't
1733 haven't been used by clients or relays since 0.2.0.x. Resolves
1737 Changes in version 0.2.3.1-alpha - 2011-05-05
1738 Tor 0.2.3.1-alpha adds some new experimental features, including support
1739 for an improved network IO backend, IOCP networking on Windows,
1740 microdescriptor caching, "fast-start" support for streams, and automatic
1741 home router configuration. There are also numerous internal improvements
1742 to try to make the code easier for developers to work with.
1744 This is the first alpha release in a new series, so expect there to be
1745 bugs. Users who would rather test out a more stable branch should
1746 stay with 0.2.2.x for now.
1749 - Tor can now optionally build with the "bufferevents" buffered IO
1750 backend provided by Libevent 2. To use this feature, make sure you
1751 have the latest possible version of Libevent, and pass the
1752 --enable-bufferevents flag to configure when building Tor from
1753 source. This feature will make our networking code more flexible,
1754 let us stack layers on each other, and let us use more efficient
1755 zero-copy transports where available.
1756 - As an experimental feature, Tor can use IOCP for networking on Windows.
1757 Once this code is tuned and optimized, it promises much better
1758 performance than the select-based backend we've used in the past. To
1759 try this feature, you must build Tor with Libevent 2, configure Tor
1760 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
1761 your torrc. There are known bugs here: only try this if you can help
1762 debug it as it breaks.
1763 - The EntryNodes option can now include country codes like {de} or IP
1764 addresses or network masks. Previously we had disallowed these options
1765 because we didn't have an efficient way to keep the list up to
1766 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
1767 - Exit nodes now accept and queue data on not-yet-connected streams.
1768 Previously, the client wasn't allowed to send data until the stream was
1769 connected, which slowed down all connections. This change will enable
1770 clients to perform a "fast-start" on streams and send data without
1771 having to wait for a confirmation that the stream has opened. (Patch
1772 from Ian Goldberg; implements the server side of Proposal 174.)
1773 - Tor now has initial support for automatic port mapping on the many
1774 home routers that support NAT-PMP or UPnP. (Not yet supported on
1775 Windows). To build the support code, you'll need to have libnatpnp
1776 library and/or the libminiupnpc library, and you'll need to enable the
1777 feature specifically by passing "--enable-upnp" and/or
1778 "--enable-natpnp" to configure. To turn it on, use the new
1779 PortForwarding option.
1780 - Caches now download, cache, and serve multiple "flavors" of the
1781 consensus, including a flavor that describes microdescriptors.
1782 - Caches now download, cache, and serve microdescriptors -- small
1783 summaries of router descriptors that are authenticated by all of the
1784 directory authorities. Once enough caches are running this code,
1785 clients will be able to save significant amounts of directory bandwidth
1786 by downloading microdescriptors instead of router descriptors.
1789 - Make logging resolution configurable with a new LogTimeGranularity
1790 option, and change the default from 1 millisecond to 1 second.
1791 Implements enhancement 1668.
1792 - We log which torrc file we're using on startup. Implements ticket
1794 - Ordinarily, Tor does not count traffic from private addresses (like
1795 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
1796 There is now a new option, CountPrivateBandwidth, to disable this
1797 behavior. Patch from Daniel Cagara.
1798 - New --enable-static-tor configure option for building Tor as
1799 statically as possible. Idea, general hackery and thoughts from
1800 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
1802 - If you set the NumCPUs option to 0, Tor will now try to detect how
1803 many CPUs you have. This is the new default behavior.
1804 - Turn on directory request statistics by default and include them in
1805 extra-info descriptors. Don't break if we have no GeoIP database.
1806 - Relays that set "ConnDirectionStatistics 1" write statistics on the
1807 bidirectional use of connections to disk every 24 hours.
1808 - Add a GeoIP file digest to the extra-info descriptor. Implements
1810 - The NodeFamily option -- which let you declare that you want to
1811 consider nodes to be part of a family whether they list themselves
1812 that way or not -- now allows IP address ranges and country codes.
1813 - Add a new 'Heartbeat' log message type to periodically log a message
1814 describing Tor's status at level Notice. This feature is meant for
1815 operators who log at notice, and want to make sure that their Tor
1816 server is still working. Implementation by George Kadianakis.
1818 o Minor bugfixes (on 0.2.2.25-alpha):
1819 - When loading the microdesc journal, remember its current size.
1820 In 0.2.2, this helps prevent the microdesc journal from growing
1821 without limit on authorities (who are the only ones to use it in
1822 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
1823 Fix posted by "cypherpunks."
1824 - The microdesc journal is supposed to get rebuilt only if it is
1825 at least _half_ the length of the store, not _twice_ the length
1826 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
1827 - If as an authority we fail to compute the identity digest of a v3
1828 legacy keypair, warn, and don't use a buffer-full of junk instead.
1829 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
1830 - Authorities now clean their microdesc cache periodically and when
1831 reading from disk initially, not only when adding new descriptors.
1832 This prevents a bug where we could lose microdescriptors. Bugfix
1835 o Minor features (controller):
1836 - Add a new SIGNAL event to the controller interface so that
1837 controllers can be notified when Tor handles a signal. Resolves
1838 issue 1955. Patch by John Brooks.
1839 - Add a new GETINFO option to get total bytes read and written. Patch
1840 from pipe, revised by atagar. Resolves ticket 2345.
1841 - Implement some GETINFO controller fields to provide information about
1842 the Tor process's pid, euid, username, and resource limits.
1845 - Our build system requires automake 1.6 or later to create the
1846 Makefile.in files. Previously, you could have used 1.4.
1847 This only affects developers and people building Tor from git;
1848 people who build Tor from the source distribution without changing
1849 the Makefile.am files should be fine.
1850 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
1851 so on. This is more robust against some of the failure modes
1852 associated with running the autotools pieces on their own.
1854 o Minor packaging issues:
1855 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
1856 already created. Patch from Andreas Stieger. Fixes bug 2573.
1858 o Code simplifications and refactoring:
1859 - A major revision to our internal node-selecting and listing logic.
1860 Tor already had at least two major ways to look at the question of
1861 "which Tor servers do we know about": a list of router descriptors,
1862 and a list of entries in the current consensus. With
1863 microdescriptors, we're adding a third. Having so many systems
1864 without an abstraction layer over them was hurting the codebase.
1865 Now, we have a new "node_t" abstraction that presents a consistent
1866 interface to a client's view of a Tor node, and holds (nearly) all
1867 of the mutable state formerly in routerinfo_t and routerstatus_t.
1868 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
1869 no longer link against Libevent: they never used it, but
1870 our library structure used to force them to link it.
1873 - Remove some old code to work around even older versions of Tor that
1874 used forked processes to handle DNS requests. Such versions of Tor
1875 are no longer in use as servers.
1877 o Documentation fixes:
1878 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
1879 - Add missing documentation for the authority-related torrc options
1880 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
1884 Changes in version 0.2.2.25-alpha - 2011-04-29
1885 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
1886 robust, routers no longer overreport their bandwidth, Win7 should crash
1887 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
1888 now prevents hidden service-related activity from being linkable. It
1889 provides more information to Vidalia so you can see if your bridge is
1890 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
1891 StrictNodes configuration options to make them more reliable, more
1892 understandable, and more regularly applied. If you use those options,
1893 please see the revised documentation for them in the manual page.
1896 - Relays were publishing grossly inflated bandwidth values because
1897 they were writing their state files wrong--now they write the
1898 correct value. Also, resume reading bandwidth history from the
1899 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
1900 - Improve hidden service robustness: When we find that we have
1901 extended a hidden service's introduction circuit to a relay not
1902 listed as an introduction point in the HS descriptor we currently
1903 have, retry with an introduction point from the current
1904 descriptor. Previously we would just give up. Fixes bugs 1024 and
1905 1930; bugfix on 0.2.0.10-alpha.
1906 - Clients now stop trying to use an exit node associated with a given
1907 destination by TrackHostExits if they fail to reach that exit node.
1908 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
1909 - Fix crash bug on platforms where gmtime and localtime can return
1910 NULL. Windows 7 users were running into this one. Fixes part of bug
1911 2077. Bugfix on all versions of Tor. Found by boboper.
1913 o Security and stability fixes:
1914 - Don't double-free a parsable, but invalid, microdescriptor, even if
1915 it is followed in the blob we're parsing by an unparsable
1916 microdescriptor. Fixes an issue reported in a comment on bug 2954.
1917 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
1918 - If the Nickname configuration option isn't given, Tor would pick a
1919 nickname based on the local hostname as the nickname for a relay.
1920 Because nicknames are not very important in today's Tor and the
1921 "Unnamed" nickname has been implemented, this is now problematic
1922 behavior: It leaks information about the hostname without being
1923 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
1924 introduced the Unnamed nickname. Reported by tagnaq.
1925 - Fix an uncommon assertion failure when running with DNSPort under
1926 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
1927 - Avoid linkability based on cached hidden service descriptors: forget
1928 all hidden service descriptors cached as a client when processing a
1929 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
1932 - Export GeoIP information on bridge usage to controllers even if we
1933 have not yet been running for 24 hours. Now Vidalia bridge operators
1934 can get more accurate and immediate feedback about their
1935 contributions to the network.
1937 o Major features and bugfixes (node selection):
1938 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
1939 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
1940 options. Previously, we had been ambiguous in describing what
1941 counted as an "exit" node, and what operations exactly "StrictNodes
1942 0" would permit. This created confusion when people saw nodes built
1943 through unexpected circuits, and made it hard to tell real bugs from
1944 surprises. Now the intended behavior is:
1945 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
1946 a node that delivers user traffic outside the Tor network.
1947 . "Entry", in the context of EntryNodes, means a node used as the
1948 first hop of a multihop circuit. It doesn't include direct
1949 connections to directory servers.
1950 . "ExcludeNodes" applies to all nodes.
1951 . "StrictNodes" changes the behavior of ExcludeNodes only. When
1952 StrictNodes is set, Tor should avoid all nodes listed in
1953 ExcludeNodes, even when it will make user requests fail. When
1954 StrictNodes is *not* set, then Tor should follow ExcludeNodes
1955 whenever it can, except when it must use an excluded node to
1956 perform self-tests, connect to a hidden service, provide a
1957 hidden service, fulfill a .exit request, upload directory
1958 information, or fetch directory information.
1959 Collectively, the changes to implement the behavior fix bug 1090.
1960 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
1961 a node is listed in both, it's treated as excluded.
1962 - ExcludeNodes now applies to directory nodes -- as a preference if
1963 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
1964 Don't exclude all the directory authorities and set StrictNodes to 1
1965 unless you really want your Tor to break.
1966 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
1967 - ExcludeExitNodes now overrides .exit requests.
1968 - We don't use bridges listed in ExcludeNodes.
1969 - When StrictNodes is 1:
1970 . We now apply ExcludeNodes to hidden service introduction points
1971 and to rendezvous points selected by hidden service users. This
1972 can make your hidden service less reliable: use it with caution!
1973 . If we have used ExcludeNodes on ourself, do not try relay
1974 reachability self-tests.
1975 . If we have excluded all the directory authorities, we will not
1976 even try to upload our descriptor if we're a relay.
1977 . Do not honor .exit requests to an excluded node.
1978 - Remove a misfeature that caused us to ignore the Fast/Stable flags
1979 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
1980 - When the set of permitted nodes changes, we now remove any mappings
1981 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
1983 - We never cannibalize a circuit that had excluded nodes on it, even
1984 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
1985 - Revert a change where we would be laxer about attaching streams to
1986 circuits than when building the circuits. This was meant to prevent
1987 a set of bugs where streams were never attachable, but our improved
1988 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
1989 - Keep track of how many times we launch a new circuit to handle a
1990 given stream. Too many launches could indicate an inconsistency
1991 between our "launch a circuit to handle this stream" logic and our
1992 "attach this stream to one of the available circuits" logic.
1993 - Improve log messages related to excluded nodes.
1996 - Fix a spurious warning when moving from a short month to a long
1997 month on relays with month-based BandwidthAccounting. Bugfix on
1998 0.2.2.17-alpha; fixes bug 3020.
1999 - When a client finds that an origin circuit has run out of 16-bit
2000 stream IDs, we now mark it as unusable for new streams. Previously,
2001 we would try to close the entire circuit. Bugfix on 0.0.6.
2002 - Add a forgotten cast that caused a compile warning on OS X 10.6.
2003 Bugfix on 0.2.2.24-alpha.
2004 - Be more careful about reporting the correct error from a failed
2005 connect() system call. Under some circumstances, it was possible to
2006 look at an incorrect value for errno when sending the end reason.
2007 Bugfix on 0.1.0.1-rc.
2008 - Correctly handle an "impossible" overflow cases in connection byte
2009 counting, where we write or read more than 4GB on an edge connection
2010 in a single second. Bugfix on 0.1.2.8-beta.
2011 - Correct the warning displayed when a rendezvous descriptor exceeds
2012 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
2014 - Clients and hidden services now use HSDir-flagged relays for hidden
2015 service descriptor downloads and uploads even if the relays have no
2016 DirPort set and the client has disabled TunnelDirConns. This will
2017 eventually allow us to give the HSDir flag to relays with no
2018 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
2019 - Downgrade "no current certificates known for authority" message from
2020 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
2021 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
2022 2917. Bugfix on 0.1.1.1-alpha.
2023 - Only limit the lengths of single HS descriptors, even when multiple
2024 HS descriptors are published to an HSDir relay in a single POST
2025 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
2026 - Write the current time into the LastWritten line in our state file,
2027 rather than the time from the previous write attempt. Also, stop
2028 trying to use a time of -1 in our log statements. Fixes bug 3039;
2029 bugfix on 0.2.2.14-alpha.
2030 - Be more consistent in our treatment of file system paths. "~" should
2031 get expanded to the user's home directory in the Log config option.
2032 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
2033 feature for the -f and --DataDirectory options.
2036 - Make sure every relay writes a state file at least every 12 hours.
2037 Previously, a relay could go for weeks without writing its state
2038 file, and on a crash could lose its bandwidth history, capacity
2039 estimates, client country statistics, and so on. Addresses bug 3012.
2040 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
2041 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
2042 clients are already deprecated because of security bugs.
2043 - Don't allow v0 hidden service authorities to act as clients.
2044 Required by fix for bug 3000.
2045 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
2046 by fix for bug 3000.
2047 - Ensure that no empty [dirreq-](read|write)-history lines are added
2048 to an extrainfo document. Implements ticket 2497.
2050 o Code simplification and refactoring:
2051 - Remove workaround code to handle directory responses from servers
2052 that had bug 539 (they would send HTTP status 503 responses _and_
2053 send a body too). Since only server versions before
2054 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
2055 keep the workaround in place.
2056 - Remove the old 'fuzzy time' logic. It was supposed to be used for
2057 handling calculations where we have a known amount of clock skew and
2058 an allowed amount of unknown skew. But we only used it in three
2059 places, and we never adjusted the known/unknown skew values. This is
2060 still something we might want to do someday, but if we do, we'll
2061 want to do it differently.
2062 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
2063 None of the cases where we did this before were wrong, but by making
2064 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
2065 - Use GetTempDir to find the proper temporary directory location on
2066 Windows when generating temporary files for the unit tests. Patch by
2070 Changes in version 0.2.2.24-alpha - 2011-04-08
2071 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
2072 prevented Tor clients from effectively using "multihomed" bridges,
2073 that is, bridges that listen on multiple ports or IP addresses so users
2074 can continue to use some of their addresses even if others get blocked.
2077 - Fix a bug where bridge users who configure the non-canonical
2078 address of a bridge automatically switch to its canonical
2079 address. If a bridge listens at more than one address, it should be
2080 able to advertise those addresses independently and any non-blocked
2081 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
2083 - If you configured Tor to use bridge A, and then quit and
2084 configured Tor to use bridge B instead, it would happily continue
2085 to use bridge A if it's still reachable. While this behavior is
2086 a feature if your goal is connectivity, in some scenarios it's a
2087 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
2088 - Directory authorities now use data collected from their own
2089 uptime observations when choosing whether to assign the HSDir flag
2090 to relays, instead of trusting the uptime value the relay reports in
2091 its descriptor. This change helps prevent an attack where a small
2092 set of nodes with frequently-changing identity keys can blackhole
2093 a hidden service. (Only authorities need upgrade; others will be
2094 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
2097 - When we restart our relay, we might get a successful connection
2098 from the outside before we've started our reachability tests,
2099 triggering a warning: "ORPort found reachable, but I have no
2100 routerinfo yet. Failing to inform controller of success." This
2101 bug was harmless unless Tor is running under a controller
2102 like Vidalia, in which case the controller would never get a
2103 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
2105 - Make directory authorities more accurate at recording when
2106 relays that have failed several reachability tests became
2107 unreachable, so we can provide more accuracy at assigning Stable,
2108 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
2109 - Fix an issue that prevented static linking of libevent on
2110 some platforms (notably Linux). Fixes bug 2698; bugfix on
2111 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
2112 the --with-static-libevent configure option).
2113 - We now ask the other side of a stream (the client or the exit)
2114 for more data on that stream when the amount of queued data on
2115 that stream dips low enough. Previously, we wouldn't ask the
2116 other side for more data until either it sent us more data (which
2117 it wasn't supposed to do if it had exhausted its window!) or we
2118 had completely flushed all our queued data. This flow control fix
2119 should improve throughput. Fixes bug 2756; bugfix on the earliest
2120 released versions of Tor (svn commit r152).
2121 - Avoid a double-mark-for-free warning when failing to attach a
2122 transparent proxy connection. (We thought we had fixed this in
2123 0.2.2.23-alpha, but it turns out our fix was checking the wrong
2124 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
2125 bug) and 0.2.2.23-alpha (the incorrect fix).
2126 - When warning about missing zlib development packages during compile,
2127 give the correct package names. Bugfix on 0.2.0.1-alpha.
2130 - Directory authorities now log the source of a rejected POSTed v3
2132 - Make compilation with clang possible when using
2133 --enable-gcc-warnings by removing two warning options that clang
2134 hasn't implemented yet and by fixing a few warnings. Implements
2136 - When expiring circuits, use microsecond timers rather than
2137 one-second timers. This can avoid an unpleasant situation where a
2138 circuit is launched near the end of one second and expired right
2139 near the beginning of the next, and prevent fluctuations in circuit
2141 - Use computed circuit-build timeouts to decide when to launch
2142 parallel introduction circuits for hidden services. (Previously,
2143 we would retry after 15 seconds.)
2144 - Update to the April 1 2011 Maxmind GeoLite Country database.
2147 - Create the /var/run/tor directory on startup on OpenSUSE if it is
2148 not already created. Patch from Andreas Stieger. Fixes bug 2573.
2150 o Documentation changes:
2151 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
2152 - Resolve all doxygen warnings except those for missing documentation.
2154 - Add doxygen documentation for more functions, fields, and types.
2157 Changes in version 0.2.2.23-alpha - 2011-03-08
2158 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
2159 they restart they don't lose their bandwidth capacity estimate. This
2160 release also fixes a diverse set of user-facing bugs, ranging from
2161 relays overrunning their rate limiting to clients falsely warning about
2162 clock skew to bridge descriptor leaks by our bridge directory authority.
2165 - Stop sending a CLOCK_SKEW controller status event whenever
2166 we fetch directory information from a relay that has a wrong clock.
2167 Instead, only inform the controller when it's a trusted authority
2168 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
2169 the rest of bug 1074.
2170 - Fix an assert in parsing router descriptors containing IPv6
2171 addresses. This one took down the directory authorities when
2172 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
2173 - Make the bridge directory authority refuse to answer directory
2174 requests for "all" descriptors. It used to include bridge
2175 descriptors in its answer, which was a major information leak.
2176 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
2177 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
2178 Tor would ignore their RelayBandwidthBurst setting,
2179 potentially using more bandwidth than expected. Bugfix on
2180 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
2181 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
2182 hidserv" in her torrc. The 'hidserv' argument never controlled
2183 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
2186 - Relays now save observed peak bandwidth throughput rates to their
2187 state file (along with total usage, which was already saved)
2188 so that they can determine their correct estimated bandwidth on
2189 restart. Resolves bug 1863, where Tor relays would reset their
2190 estimated bandwidth to 0 after restarting.
2191 - Directory authorities now take changes in router IP address and
2192 ORPort into account when determining router stability. Previously,
2193 if a router changed its IP or ORPort, the authorities would not
2194 treat it as having any downtime for the purposes of stability
2195 calculation, whereas clients would experience downtime since the
2196 change could take a while to propagate to them. Resolves issue 1035.
2197 - Enable Address Space Layout Randomization (ASLR) and Data Execution
2198 Prevention (DEP) by default on Windows to make it harder for
2199 attackers to exploit vulnerabilities. Patch from John Brooks.
2201 o Minor bugfixes (on 0.2.1.x and earlier):
2202 - Fix a rare crash bug that could occur when a client was configured
2203 with a large number of bridges. Fixes bug 2629; bugfix on
2204 0.2.1.2-alpha. Bugfix by trac user "shitlei".
2205 - Avoid a double mark-for-free warning when failing to attach a
2206 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
2208 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
2209 found by "cypherpunks". This bug was introduced before the first
2210 Tor release, in svn commit r110.
2211 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
2212 don't mention them in the manpage. Fixes bug 2450; issue
2213 spotted by keb and G-Lo.
2214 - Fix a bug in bandwidth history state parsing that could have been
2215 triggered if a future version of Tor ever changed the timing
2216 granularity at which bandwidth history is measured. Bugfix on
2218 - When a relay decides that its DNS is too broken for it to serve
2219 as an exit server, it advertised itself as a non-exit, but
2220 continued to act as an exit. This could create accidental
2221 partitioning opportunities for users. Instead, if a relay is
2222 going to advertise reject *:* as its exit policy, it should
2223 really act with exit policy "reject *:*". Fixes bug 2366.
2224 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
2225 - In the special case where you configure a public exit relay as your
2226 bridge, Tor would be willing to use that exit relay as the last
2227 hop in your circuit as well. Now we fail that circuit instead.
2228 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
2229 - Fix a bug with our locking implementation on Windows that couldn't
2230 correctly detect when a file was already locked. Fixes bug 2504,
2231 bugfix on 0.2.1.6-alpha.
2232 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
2233 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
2235 - Set target port in get_interface_address6() correctly. Bugfix
2236 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
2237 - Directory authorities are now more robust to hops back in time
2238 when calculating router stability. Previously, if a run of uptime
2239 or downtime appeared to be negative, the calculation could give
2240 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
2242 - Fix an assert that got triggered when using the TestingTorNetwork
2243 configuration option and then issuing a GETINFO config-text control
2244 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
2246 o Minor bugfixes (on 0.2.2.x):
2247 - Clients should not weight BadExit nodes as Exits in their node
2248 selection. Similarly, directory authorities should not count BadExit
2249 bandwidth as Exit bandwidth when computing bandwidth-weights.
2250 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
2251 - Correctly clear our dir_read/dir_write history when there is an
2252 error parsing any bw history value from the state file. Bugfix on
2254 - Resolve a bug in verifying signatures of directory objects
2255 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
2256 Fixes bug 2409. Found by "piebeer".
2257 - Bridge authorities no longer crash on SIGHUP when they try to
2258 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
2262 - Log less aggressively about circuit timeout changes, and improve
2263 some other circuit timeout messages. Resolves bug 2004.
2264 - Log a little more clearly about the times at which we're no longer
2265 accepting new connections. Resolves bug 2181.
2266 - Reject attempts at the client side to open connections to private
2267 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
2268 a randomly chosen exit node. Attempts to do so are always
2269 ill-defined, generally prevented by exit policies, and usually
2270 in error. This will also help to detect loops in transparent
2271 proxy configurations. You can disable this feature by setting
2272 "ClientRejectInternalAddresses 0" in your torrc.
2273 - Always treat failure to allocate an RSA key as an unrecoverable
2275 - Update to the March 1 2011 Maxmind GeoLite Country database.
2277 o Minor features (log subsystem):
2278 - Add documentation for configuring logging at different severities in
2279 different log domains. We've had this feature since 0.2.1.1-alpha,
2280 but for some reason it never made it into the manpage. Fixes
2282 - Make it simpler to specify "All log domains except for A and B".
2283 Previously you needed to say "[*,~A,~B]". Now you can just say
2285 - Add a "LogMessageDomains 1" option to include the domains of log
2286 messages along with the messages. Without this, there's no way
2287 to use log domains without reading the source or doing a lot
2290 o Packaging changes:
2291 - Stop shipping the Tor specs files and development proposal documents
2292 in the tarball. They are now in a separate git repository at
2293 git://git.torproject.org/torspec.git
2296 Changes in version 0.2.1.30 - 2011-02-23
2297 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
2298 change is a slight tweak to Tor's TLS handshake that makes relays
2299 and bridges that run this new version reachable from Iran again.
2300 We don't expect this tweak will win the arms race long-term, but it
2301 buys us time until we roll out a better solution.
2304 - Stop sending a CLOCK_SKEW controller status event whenever
2305 we fetch directory information from a relay that has a wrong clock.
2306 Instead, only inform the controller when it's a trusted authority
2307 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
2308 the rest of bug 1074.
2309 - Fix a bounds-checking error that could allow an attacker to
2310 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
2312 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
2313 Tor would ignore their RelayBandwidthBurst setting,
2314 potentially using more bandwidth than expected. Bugfix on
2315 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
2316 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
2317 hidserv" in her torrc. The 'hidserv' argument never controlled
2318 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
2321 - Adjust our TLS Diffie-Hellman parameters to match those used by
2323 - Update to the February 1 2011 Maxmind GeoLite Country database.
2326 - Check for and reject overly long directory certificates and
2327 directory tokens before they have a chance to hit any assertions.
2328 Bugfix on 0.2.1.28. Found by "doorss".
2329 - Bring the logic that gathers routerinfos and assesses the
2330 acceptability of circuits into line. This prevents a Tor OP from
2331 getting locked in a cycle of choosing its local OR as an exit for a
2332 path (due to a .exit request) and then rejecting the circuit because
2333 its OR is not listed yet. It also prevents Tor clients from using an
2334 OR running in the same instance as an exit (due to a .exit request)
2335 if the OR does not meet the same requirements expected of an OR
2336 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
2338 o Packaging changes:
2339 - Stop shipping the Tor specs files and development proposal documents
2340 in the tarball. They are now in a separate git repository at
2341 git://git.torproject.org/torspec.git
2342 - Do not include Git version tags as though they are SVN tags when
2343 generating a tarball from inside a repository that has switched
2344 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
2347 Changes in version 0.2.2.22-alpha - 2011-01-25
2348 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
2349 main other change is a slight tweak to Tor's TLS handshake that makes
2350 relays and bridges that run this new version reachable from Iran again.
2351 We don't expect this tweak will win the arms race long-term, but it
2352 will buy us a bit more time until we roll out a better solution.
2355 - Fix a bounds-checking error that could allow an attacker to
2356 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
2358 - Don't assert when changing from bridge to relay or vice versa
2359 via the controller. The assert happened because we didn't properly
2360 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
2361 bug 2433. Reported by bastik.
2364 - Adjust our TLS Diffie-Hellman parameters to match those used by
2366 - Provide a log message stating which geoip file we're parsing
2367 instead of just stating that we're parsing the geoip file.
2368 Implements ticket 2432.
2371 - Check for and reject overly long directory certificates and
2372 directory tokens before they have a chance to hit any assertions.
2373 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
2376 Changes in version 0.2.2.21-alpha - 2011-01-15
2377 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
2378 continues our recent code security audit work. The main fix resolves
2379 a remote heap overflow vulnerability that can allow remote code
2380 execution (CVE-2011-0427). Other fixes address a variety of assert
2381 and crash bugs, most of which we think are hard to exploit remotely.
2383 o Major bugfixes (security), also included in 0.2.1.29:
2384 - Fix a heap overflow bug where an adversary could cause heap
2385 corruption. This bug probably allows remote code execution
2386 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
2388 - Prevent a denial-of-service attack by disallowing any
2389 zlib-compressed data whose compression factor is implausibly
2390 high. Fixes part of bug 2324; reported by "doorss".
2391 - Zero out a few more keys in memory before freeing them. Fixes
2392 bug 2384 and part of bug 2385. These key instances found by
2393 "cypherpunks", based on Andrew Case's report about being able
2394 to find sensitive data in Tor's memory space if you have enough
2395 permissions. Bugfix on 0.0.2pre9.
2397 o Major bugfixes (crashes), also included in 0.2.1.29:
2398 - Prevent calls to Libevent from inside Libevent log handlers.
2399 This had potential to cause a nasty set of crashes, especially
2400 if running Libevent with debug logging enabled, and running
2401 Tor with a controller watching for low-severity log messages.
2402 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
2403 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
2404 underflow errors there too. Fixes the other part of bug 2324.
2405 - Fix a bug where we would assert if we ever had a
2406 cached-descriptors.new file (or another file read directly into
2407 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
2408 on 0.2.1.25. Found by doorss.
2409 - Fix some potential asserts and parsing issues with grossly
2410 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
2413 o Minor bugfixes (other), also included in 0.2.1.29:
2414 - Fix a bug with handling misformed replies to reverse DNS lookup
2415 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
2416 bug reported by doorss.
2417 - Fix compilation on mingw when a pthreads compatibility library
2418 has been installed. (We don't want to use it, so we shouldn't
2419 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
2420 - Fix a bug where we would declare that we had run out of virtual
2421 addresses when the address space was only half-exhausted. Bugfix
2423 - Correctly handle the case where AutomapHostsOnResolve is set but
2424 no virtual addresses are available. Fixes bug 2328; bugfix on
2425 0.1.2.1-alpha. Bug found by doorss.
2426 - Correctly handle wrapping around when we run out of virtual
2427 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
2429 o Minor features, also included in 0.2.1.29:
2430 - Update to the January 1 2011 Maxmind GeoLite Country database.
2431 - Introduce output size checks on all of our decryption functions.
2433 o Build changes, also included in 0.2.1.29:
2434 - Tor does not build packages correctly with Automake 1.6 and earlier;
2435 added a check to Makefile.am to make sure that we're building with
2436 Automake 1.7 or later.
2437 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
2438 because we built it with a too-old version of automake. Thus that
2439 release broke ./configure --enable-openbsd-malloc, which is popular
2440 among really fast exit relays on Linux.
2442 o Major bugfixes, new in 0.2.2.21-alpha:
2443 - Prevent crash/heap corruption when the cbtnummodes consensus
2444 parameter is set to 0 or large values. Fixes bug 2317; bugfix
2447 o Major features, new in 0.2.2.21-alpha:
2448 - Introduce minimum/maximum values that clients will believe
2449 from the consensus. Now we'll have a better chance to avoid crashes
2450 or worse when a consensus param has a weird value.
2452 o Minor features, new in 0.2.2.21-alpha:
2453 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
2454 used on bridges, and it makes bridge scanning somewhat easier.
2455 - If writing the state file to disk fails, wait up to an hour before
2456 retrying again, rather than trying again each second. Fixes bug
2457 2346; bugfix on Tor 0.1.1.3-alpha.
2458 - Make Libevent log messages get delivered to controllers later,
2459 and not from inside the Libevent log handler. This prevents unsafe
2460 reentrant Libevent calls while still letting the log messages
2462 - Detect platforms that brokenly use a signed size_t, and refuse to
2463 build there. Found and analyzed by doorss and rransom.
2464 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
2467 o Minor bugfixes, new in 0.2.2.21-alpha:
2468 - Handle SOCKS messages longer than 128 bytes long correctly, rather
2469 than waiting forever for them to finish. Fixes bug 2330; bugfix
2470 on 0.2.0.16-alpha. Found by doorss.
2471 - Add assertions to check for overflow in arguments to
2472 base32_encode() and base32_decode(); fix a signed-unsigned
2473 comparison there too. These bugs are not actually reachable in Tor,
2474 but it's good to prevent future errors too. Found by doorss.
2475 - Correctly detect failures to create DNS requests when using Libevent
2476 versions before v2. (Before Libevent 2, we used our own evdns
2477 implementation. Its return values for Libevent's evdns_resolve_*()
2478 functions are not consistent with those from Libevent.) Fixes bug
2479 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
2481 o Documentation, new in 0.2.2.21-alpha:
2482 - Document the default socks host and port (127.0.0.1:9050) for
2486 Changes in version 0.2.1.29 - 2011-01-15
2487 Tor 0.2.1.29 continues our recent code security audit work. The main
2488 fix resolves a remote heap overflow vulnerability that can allow remote
2489 code execution. Other fixes address a variety of assert and crash bugs,
2490 most of which we think are hard to exploit remotely.
2492 o Major bugfixes (security):
2493 - Fix a heap overflow bug where an adversary could cause heap
2494 corruption. This bug probably allows remote code execution
2495 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
2497 - Prevent a denial-of-service attack by disallowing any
2498 zlib-compressed data whose compression factor is implausibly
2499 high. Fixes part of bug 2324; reported by "doorss".
2500 - Zero out a few more keys in memory before freeing them. Fixes
2501 bug 2384 and part of bug 2385. These key instances found by
2502 "cypherpunks", based on Andrew Case's report about being able
2503 to find sensitive data in Tor's memory space if you have enough
2504 permissions. Bugfix on 0.0.2pre9.
2506 o Major bugfixes (crashes):
2507 - Prevent calls to Libevent from inside Libevent log handlers.
2508 This had potential to cause a nasty set of crashes, especially
2509 if running Libevent with debug logging enabled, and running
2510 Tor with a controller watching for low-severity log messages.
2511 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
2512 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
2513 underflow errors there too. Fixes the other part of bug 2324.
2514 - Fix a bug where we would assert if we ever had a
2515 cached-descriptors.new file (or another file read directly into
2516 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
2517 on 0.2.1.25. Found by doorss.
2518 - Fix some potential asserts and parsing issues with grossly
2519 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
2522 o Minor bugfixes (other):
2523 - Fix a bug with handling misformed replies to reverse DNS lookup
2524 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
2525 bug reported by doorss.
2526 - Fix compilation on mingw when a pthreads compatibility library
2527 has been installed. (We don't want to use it, so we shouldn't
2528 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
2529 - Fix a bug where we would declare that we had run out of virtual
2530 addresses when the address space was only half-exhausted. Bugfix
2532 - Correctly handle the case where AutomapHostsOnResolve is set but
2533 no virtual addresses are available. Fixes bug 2328; bugfix on
2534 0.1.2.1-alpha. Bug found by doorss.
2535 - Correctly handle wrapping around to when we run out of virtual
2536 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
2537 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
2538 because we built it with a too-old version of automake. Thus that
2539 release broke ./configure --enable-openbsd-malloc, which is popular
2540 among really fast exit relays on Linux.
2543 - Update to the January 1 2011 Maxmind GeoLite Country database.
2544 - Introduce output size checks on all of our decryption functions.
2547 - Tor does not build packages correctly with Automake 1.6 and earlier;
2548 added a check to Makefile.am to make sure that we're building with
2549 Automake 1.7 or later.
2552 Changes in version 0.2.2.20-alpha - 2010-12-17
2553 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
2554 exploitable bugs. We also fix a variety of other significant bugs,
2555 change the IP address for one of our directory authorities, and update
2556 the minimum version that Tor relays must run to join the network.
2559 - Fix a remotely exploitable bug that could be used to crash instances
2560 of Tor remotely by overflowing on the heap. Remote-code execution
2561 hasn't been confirmed, but can't be ruled out. Everyone should
2562 upgrade. Bugfix on the 0.1.1 series and later.
2563 - Fix a bug that could break accounting on 64-bit systems with large
2564 time_t values, making them hibernate for impossibly long intervals.
2565 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
2566 - Fix a logic error in directory_fetches_from_authorities() that
2567 would cause all _non_-exits refusing single-hop-like circuits
2568 to fetch from authorities, when we wanted to have _exits_ fetch
2569 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
2571 - Fix a stream fairness bug that would cause newer streams on a given
2572 circuit to get preference when reading bytes from the origin or
2573 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
2574 introduced before the first Tor release, in svn revision r152.
2576 o Directory authority changes:
2577 - Change IP address and ports for gabelmoo (v3 directory authority).
2580 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
2581 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
2582 - Fix an off-by-one error in calculating some controller command
2583 argument lengths. Fortunately, this mistake is harmless since
2584 the controller code does redundant NUL termination too. Found by
2585 boboper. Bugfix on 0.1.1.1-alpha.
2586 - Do not dereference NULL if a bridge fails to build its
2587 extra-info descriptor. Found by an anonymous commenter on
2588 Trac. Bugfix on 0.2.2.19-alpha.
2591 - Update to the December 1 2010 Maxmind GeoLite Country database.
2592 - Directory authorities now reject relays running any versions of
2593 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
2594 known bugs that keep RELAY_EARLY cells from working on rendezvous
2595 circuits. Followup to fix for bug 2081.
2596 - Directory authorities now reject relays running any version of Tor
2597 older than 0.2.0.26-rc. That version is the earliest that fetches
2598 current directory information correctly. Fixes bug 2156.
2599 - Report only the top 10 ports in exit-port stats in order not to
2600 exceed the maximum extra-info descriptor length of 50 KB. Implements
2604 Changes in version 0.2.1.28 - 2010-12-17
2605 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
2606 exploitable bugs. We also took this opportunity to change the IP address
2607 for one of our directory authorities, and to update the geoip database
2611 - Fix a remotely exploitable bug that could be used to crash instances
2612 of Tor remotely by overflowing on the heap. Remote-code execution
2613 hasn't been confirmed, but can't be ruled out. Everyone should
2614 upgrade. Bugfix on the 0.1.1 series and later.
2616 o Directory authority changes:
2617 - Change IP address and ports for gabelmoo (v3 directory authority).
2620 - Update to the December 1 2010 Maxmind GeoLite Country database.
2623 Changes in version 0.2.1.27 - 2010-11-23
2624 Yet another OpenSSL security patch broke its compatibility with Tor:
2625 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
2626 also took this opportunity to fix several crash bugs, integrate a new
2627 directory authority, and update the bundled GeoIP database.
2630 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
2631 No longer set the tlsext_host_name extension on server SSL objects;
2632 but continue to set it on client SSL objects. Our goal in setting
2633 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
2634 bugfix on 0.2.1.1-alpha.
2635 - Do not log messages to the controller while shrinking buffer
2636 freelists. Doing so would sometimes make the controller connection
2637 try to allocate a buffer chunk, which would mess up the internals
2638 of the freelist and cause an assertion failure. Fixes bug 1125;
2639 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
2640 - Learn our external IP address when we're a relay or bridge, even if
2641 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
2642 where we introduced bridge relays that don't need to publish to
2643 be useful. Fixes bug 2050.
2644 - Do even more to reject (and not just ignore) annotations on
2645 router descriptors received anywhere but from the cache. Previously
2646 we would ignore such annotations at first, but cache them to disk
2647 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
2648 - When you're using bridges and your network goes away and your
2649 bridges get marked as down, recover when you attempt a new socks
2650 connection (if the network is back), rather than waiting up to an
2651 hour to try fetching new descriptors for your bridges. Bugfix on
2652 0.2.0.3-alpha; fixes bug 1981.
2655 - Move to the November 2010 Maxmind GeoLite country db (rather
2656 than the June 2009 ip-to-country GeoIP db) for our statistics that
2657 count how many users relays are seeing from each country. Now we'll
2658 have more accurate data, especially for many African countries.
2660 o New directory authorities:
2661 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
2665 - Fix an assertion failure that could occur in directory caches or
2666 bridge users when using a very short voting interval on a testing
2667 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
2669 - Enforce multiplicity rules when parsing annotations. Bugfix on
2670 0.2.0.8-alpha. Found by piebeer.
2671 - Allow handshaking OR connections to take a full KeepalivePeriod
2672 seconds to handshake. Previously, we would close them after
2673 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
2674 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
2676 - When building with --enable-gcc-warnings on OpenBSD, disable
2677 warnings in system headers. This makes --enable-gcc-warnings
2678 pass on OpenBSD 4.8.
2681 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
2682 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
2683 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
2684 Servers can start sending this code when enough clients recognize
2685 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
2686 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
2687 Patch from mingw-san.
2690 - Remove the old debian/ directory from the main Tor distribution.
2691 The official Tor-for-debian git repository lives at the URL
2692 https://git.torproject.org/debian/tor.git
2693 - Stop shipping the old doc/website/ directory in the tarball. We
2694 changed the website format in late 2010, and what we shipped in
2695 0.2.1.26 really wasn't that useful anyway.
2698 Changes in version 0.2.2.19-alpha - 2010-11-22
2699 Yet another OpenSSL security patch broke its compatibility with Tor:
2700 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
2703 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
2704 No longer set the tlsext_host_name extension on server SSL objects;
2705 but continue to set it on client SSL objects. Our goal in setting
2706 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
2707 bugfix on 0.2.1.1-alpha.
2710 - Try harder not to exceed the maximum length of 50 KB when writing
2711 statistics to extra-info descriptors. This bug was triggered by very
2712 fast relays reporting exit-port, entry, and dirreq statistics.
2713 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
2714 - Publish a router descriptor even if generating an extra-info
2715 descriptor fails. Previously we would not publish a router
2716 descriptor without an extra-info descriptor; this can cause fast
2717 exit relays collecting exit-port statistics to drop from the
2718 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
2721 Changes in version 0.2.2.18-alpha - 2010-11-16
2722 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
2723 us lately, makes unpublished bridge relays able to detect their IP
2724 address, and fixes a wide variety of other bugs to get us much closer
2725 to a stable release.
2728 - Do even more to reject (and not just ignore) annotations on
2729 router descriptors received anywhere but from the cache. Previously
2730 we would ignore such annotations at first, but cache them to disk
2731 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
2732 - Do not log messages to the controller while shrinking buffer
2733 freelists. Doing so would sometimes make the controller connection
2734 try to allocate a buffer chunk, which would mess up the internals
2735 of the freelist and cause an assertion failure. Fixes bug 1125;
2736 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
2737 - Learn our external IP address when we're a relay or bridge, even if
2738 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
2739 where we introduced bridge relays that don't need to publish to
2740 be useful. Fixes bug 2050.
2741 - Maintain separate TLS contexts and certificates for incoming and
2742 outgoing connections in bridge relays. Previously we would use the
2743 same TLS contexts and certs for incoming and outgoing connections.
2744 Bugfix on 0.2.0.3-alpha; addresses bug 988.
2745 - Maintain separate identity keys for incoming and outgoing TLS
2746 contexts in bridge relays. Previously we would use the same
2747 identity keys for incoming and outgoing TLS contexts. Bugfix on
2748 0.2.0.3-alpha; addresses the other half of bug 988.
2749 - Avoid an assertion failure when we as an authority receive a
2750 duplicate upload of a router descriptor that we already have,
2751 but which we previously considered an obsolete descriptor.
2752 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
2753 - Avoid a crash bug triggered by looking at a dangling pointer while
2754 setting the network status consensus. Found by Robert Ransom.
2755 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
2756 - Fix a logic error where servers that _didn't_ act as exits would
2757 try to keep their server lists more aggressively up to date than
2758 exits, when it was supposed to be the other way around. Bugfix
2761 o Minor bugfixes (on Tor 0.2.1.x and earlier):
2762 - When we're trying to guess whether we know our IP address as
2763 a relay, we would log various ways that we failed to guess
2764 our address, but never log that we ended up guessing it
2765 successfully. Now add a log line to help confused and anxious
2766 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
2767 - Bring the logic that gathers routerinfos and assesses the
2768 acceptability of circuits into line. This prevents a Tor OP from
2769 getting locked in a cycle of choosing its local OR as an exit for a
2770 path (due to a .exit request) and then rejecting the circuit because
2771 its OR is not listed yet. It also prevents Tor clients from using an
2772 OR running in the same instance as an exit (due to a .exit request)
2773 if the OR does not meet the same requirements expected of an OR
2774 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
2775 - Correctly describe errors that occur when generating a TLS object.
2776 Previously we would attribute them to a failure while generating a
2777 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
2779 - Enforce multiplicity rules when parsing annotations. Bugfix on
2780 0.2.0.8-alpha. Found by piebeer.
2781 - Fix warnings that newer versions of autoconf produced during
2782 ./autogen.sh. These warnings appear to be harmless in our case,
2783 but they were extremely verbose. Fixes bug 2020.
2785 o Minor bugfixes (on Tor 0.2.2.x):
2786 - Enable protection of small arrays whenever we build with gcc
2787 hardening features, not only when also building with warnings
2788 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
2791 - Make hidden services work better in private Tor networks by not
2792 requiring any uptime to join the hidden service descriptor
2793 DHT. Implements ticket 2088.
2794 - Rate-limit the "your application is giving Tor only an IP address"
2795 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
2796 - When AllowSingleHopExits is set, print a warning to explain to the
2797 relay operator why most clients are avoiding her relay.
2798 - Update to the November 1 2010 Maxmind GeoLite Country database.
2800 o Code simplifications and refactoring:
2801 - When we fixed bug 1038 we had to put in a restriction not to send
2802 RELAY_EARLY cells on rend circuits. This was necessary as long
2803 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
2804 active. Now remove this obsolete check. Resolves bug 2081.
2805 - Some options used different conventions for uppercasing of acronyms
2806 when comparing manpage and source. Fix those in favor of the
2807 manpage, as it makes sense to capitalize acronyms.
2808 - Remove the torrc.complete file. It hasn't been kept up to date
2809 and users will have better luck checking out the manpage.
2810 - Remove the obsolete "NoPublish" option; it has been flagged
2811 as obsolete and has produced a warning since 0.1.1.18-rc.
2812 - Remove everything related to building the expert bundle for OS X.
2813 It has confused many users, doesn't work right on OS X 10.6,
2814 and is hard to get rid of once installed. Resolves bug 1274.
2817 Changes in version 0.2.2.17-alpha - 2010-09-30
2818 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
2819 to use one-hop circuits (which can put the exit relays at higher risk,
2820 plus unbalance the network); fixes a big bug in bandwidth accounting
2821 for relays that want to limit their monthly bandwidth use; fixes a
2822 big pile of bugs in how clients tolerate temporary network failure;
2823 and makes our adaptive circuit build timeout feature (which improves
2824 client performance if your network is fast while not breaking things
2825 if your network is slow) better handle bad networks.
2828 - Exit relays now try harder to block exit attempts from unknown
2829 relays, to make it harder for people to use them as one-hop proxies
2830 a la tortunnel. Controlled by the refuseunknownexits consensus
2831 parameter (currently enabled), or you can override it on your
2832 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
2834 o Major bugfixes (0.2.1.x and earlier):
2835 - Fix a bug in bandwidth accounting that could make us use twice
2836 the intended bandwidth when our interval start changes due to
2837 daylight saving time. Now we tolerate skew in stored vs computed
2838 interval starts: if the start of the period changes by no more than
2839 50% of the period's duration, we remember bytes that we transferred
2840 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
2841 - Always search the Windows system directory for system DLLs, and
2842 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
2843 - When you're using bridges and your network goes away and your
2844 bridges get marked as down, recover when you attempt a new socks
2845 connection (if the network is back), rather than waiting up to an
2846 hour to try fetching new descriptors for your bridges. Bugfix on
2847 0.2.0.3-alpha; fixes bug 1981.
2849 o Major bugfixes (on 0.2.2.x):
2850 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
2852 - Fix a segfault that could happen when operating a bridge relay with
2853 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
2854 - The consensus bandwidth-weights (used by clients to choose fast
2855 relays) entered an unexpected edge case in September where
2856 Exits were much scarcer than Guards, resulting in bad weight
2857 recommendations. Now we compute them using new constraints that
2858 should succeed in all cases. Also alter directory authorities to
2859 not include the bandwidth-weights line if they fail to produce
2860 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
2861 - When weighting bridges during path selection, we used to trust
2862 the bandwidths they provided in their descriptor, only capping them
2863 at 10MB/s. This turned out to be problematic for two reasons:
2864 Bridges could claim to handle a lot more traffic then they
2865 actually would, thus making more clients pick them and have a
2866 pretty effective DoS attack. The other issue is that new bridges
2867 that might not have a good estimate for their bw capacity yet
2868 would not get used at all unless no other bridges are available
2869 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
2871 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
2872 - Ignore cannibalized circuits when recording circuit build times.
2873 This should provide for a minor performance improvement for hidden
2874 service users using 0.2.2.14-alpha, and should remove two spurious
2875 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
2876 - Simplify the logic that causes us to decide if the network is
2877 unavailable for purposes of recording circuit build times. If we
2878 receive no cells whatsoever for the entire duration of a circuit's
2879 full measured lifetime, the network is probably down. Also ignore
2880 one-hop directory fetching circuit timeouts when calculating our
2881 circuit build times. These changes should hopefully reduce the
2882 cases where we see ridiculous circuit build timeouts for people
2883 with spotty wireless connections. Fixes part of bug 1772; bugfix
2885 - Prevent the circuit build timeout from becoming larger than
2886 the maximum build time we have ever seen. Also, prevent the time
2887 period for measurement circuits from becoming larger than twice that
2888 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
2891 - When we run out of directory information such that we can't build
2892 circuits, but then get enough that we can build circuits, log when
2893 we actually construct a circuit, so the user has a better chance of
2894 knowing what's going on. Fixes bug 1362.
2895 - Be more generous with how much bandwidth we'd use up (with
2896 accounting enabled) before entering "soft hibernation". Previously,
2897 we'd refuse new connections and circuits once we'd used up 95% of
2898 our allotment. Now, we use up 95% of our allotment, AND make sure
2899 that we have no more than 500MB (or 3 hours of expected traffic,
2900 whichever is lower) remaining before we enter soft hibernation.
2901 - If we've configured EntryNodes and our network goes away and/or all
2902 our entrynodes get marked down, optimistically retry them all when
2903 a new socks application request appears. Fixes bug 1882.
2904 - Add some more defensive programming for architectures that can't
2905 handle unaligned integer accesses. We don't know of any actual bugs
2906 right now, but that's the best time to fix them. Fixes bug 1943.
2907 - Support line continuations in the torrc config file. If a line
2908 ends with a single backslash character, the newline is ignored, and
2909 the configuration value is treated as continuing on the next line.
2912 o Minor bugfixes (on 0.2.1.x and earlier):
2913 - For bandwidth accounting, calculate our expected bandwidth rate
2914 based on the time during which we were active and not in
2915 soft-hibernation during the last interval. Previously, we were
2916 also considering the time spent in soft-hibernation. If this
2917 was a long time, we would wind up underestimating our bandwidth
2918 by a lot, and skewing our wakeup time towards the start of the
2919 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
2921 o Minor bugfixes (on 0.2.2.x):
2922 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
2923 which were disabled by the circuit build timeout changes in
2924 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
2925 - Make sure we don't warn about missing bandwidth weights when
2926 choosing bridges or other relays not in the consensus. Bugfix on
2927 0.2.2.10-alpha; fixes bug 1805.
2928 - In our logs, do not double-report signatures from unrecognized
2929 authorities both as "from unknown authority" and "not
2930 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
2933 Changes in version 0.2.2.16-alpha - 2010-09-17
2934 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
2935 evident at exit relays), and also continues to resolve all the little
2936 bugs that have been filling up trac lately.
2938 o Major bugfixes (stream-level fairness):
2939 - When receiving a circuit-level SENDME for a blocked circuit, try
2940 to package cells fairly from all the streams that had previously
2941 been blocked on that circuit. Previously, we had started with the
2942 oldest stream, and allowed each stream to potentially exhaust
2943 the circuit's package window. This gave older streams on any
2944 given circuit priority over newer ones. Fixes bug 1937. Detected
2945 originally by Camilo Viecco. This bug was introduced before the
2946 first Tor release, in svn commit r152: it is the new winner of
2947 the longest-lived bug prize.
2948 - When the exit relay got a circuit-level sendme cell, it started
2949 reading on the exit streams, even if had 500 cells queued in the
2950 circuit queue already, so the circuit queue just grew and grew in
2951 some cases. We fix this by not re-enabling reading on receipt of a
2952 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
2953 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
2955 - Newly created streams were allowed to read cells onto circuits,
2956 even if the circuit's cell queue was blocked and waiting to drain.
2957 This created potential unfairness, as older streams would be
2958 blocked, but newer streams would gladly fill the queue completely.
2959 We add code to detect this situation and prevent any stream from
2960 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
2964 - Update to the September 1 2010 Maxmind GeoLite Country database.
2965 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
2966 not. This would lead to a cookie that is still not group readable.
2967 Closes bug 1843. Suggested by katmagic.
2968 - When logging a rate-limited warning, we now mention how many messages
2969 got suppressed since the last warning.
2970 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
2971 do individual connection-level rate limiting of clients. The torrc
2972 config options with the same names trump the consensus params, if
2973 both are present. Replaces the old "bwconnrate" and "bwconnburst"
2974 consensus params which were broken from 0.2.2.7-alpha through
2975 0.2.2.14-alpha. Closes bug 1947.
2976 - When a router changes IP address or port, authorities now launch
2977 a new reachability test for it. Implements ticket 1899.
2978 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
2979 2 no signature, 4 required" messages about consensus signatures
2980 easier to read, and make sure they get logged at the same severity
2981 as the messages explaining which keys are which. Fixes bug 1290.
2982 - Don't warn when we have a consensus that we can't verify because
2983 of missing certificates, unless those certificates are ones
2984 that we have been trying and failing to download. Fixes bug 1145.
2985 - If you configure your bridge with a known identity fingerprint,
2986 and the bridge authority is unreachable (as it is in at least
2987 one country now), fall back to directly requesting the descriptor
2988 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
2990 - When building with --enable-gcc-warnings on OpenBSD, disable
2991 warnings in system headers. This makes --enable-gcc-warnings
2992 pass on OpenBSD 4.8.
2994 o Minor bugfixes (on 0.2.1.x and earlier):
2995 - Authorities will now attempt to download consensuses if their
2996 own efforts to make a live consensus have failed. This change
2997 means authorities that restart will fetch a valid consensus, and
2998 it means authorities that didn't agree with the current consensus
2999 will still fetch and serve it if it has enough signatures. Bugfix
3000 on 0.2.0.9-alpha; fixes bug 1300.
3001 - Ensure DNS requests launched by "RESOLVE" commands from the
3002 controller respect the __LeaveStreamsUnattached setconf options. The
3003 same goes for requests launched via DNSPort or transparent
3004 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
3005 - Allow handshaking OR connections to take a full KeepalivePeriod
3006 seconds to handshake. Previously, we would close them after
3007 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
3008 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
3010 - Rate-limit "Failed to hand off onionskin" warnings.
3011 - Never relay a cell for a circuit we have already destroyed.
3012 Between marking a circuit as closeable and finally closing it,
3013 it may have been possible for a few queued cells to get relayed,
3014 even though they would have been immediately dropped by the next
3015 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
3016 - Never queue a cell for a circuit that's already been marked
3018 - Never vote for a server as "Running" if we have a descriptor for
3019 it claiming to be hibernating, and that descriptor was published
3020 more recently than our last contact with the server. Bugfix on
3021 0.2.0.3-alpha; fixes bug 911.
3022 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
3025 o Minor bugfixes (on 0.2.2.x):
3026 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
3027 down if a directory fetch fails and you've configured either
3028 bridges or EntryNodes. The intent was to mark the relay as down
3029 _unless_ you're using bridges or EntryNodes, since if you are
3030 then you could quickly run out of entry points.
3031 - Fix the Windows directory-listing code. A bug introduced in
3032 0.2.2.14-alpha could make Windows directory servers forget to load
3033 some of their cached v2 networkstatus files.
3034 - Really allow clients to use relays as bridges. Fixes bug 1776;
3035 bugfix on 0.2.2.15-alpha.
3036 - Demote a warn to info that happens when the CellStatistics option
3037 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
3038 Reported by Moritz Bartl.
3039 - On Windows, build correctly either with or without Unicode support.
3040 This is necessary so that Tor can support fringe platforms like
3041 Windows 98 (which has no Unicode), or Windows CE (which has no
3042 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
3045 - Add a unit test for cross-platform directory-listing code.
3048 Changes in version 0.2.2.15-alpha - 2010-08-18
3049 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
3050 fixes a variety of other bugs that were preventing performance
3051 experiments from moving forward, fixes several bothersome memory leaks,
3052 and generally closes a lot of smaller bugs that have been filling up
3056 - Stop assigning the HSDir flag to relays that disable their
3057 DirPort (and thus will refuse to answer directory requests). This
3058 fix should dramatically improve the reachability of hidden services:
3059 hidden services and hidden service clients pick six HSDir relays
3060 to store and retrieve the hidden service descriptor, and currently
3061 about half of the HSDir relays will refuse to work. Bugfix on
3062 0.2.0.10-alpha; fixes part of bug 1693.
3063 - The PerConnBWRate and Burst config options, along with the
3064 bwconnrate and bwconnburst consensus params, initialized each conn's
3065 token bucket values only when the connection is established. Now we
3066 update them if the config options change, and update them every time
3067 we get a new consensus. Otherwise we can encounter an ugly edge
3068 case where we initialize an OR conn to client-level bandwidth,
3069 but then later the relay joins the consensus and we leave it
3070 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
3071 - Fix a regression that caused Tor to rebind its ports if it receives
3072 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
3075 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
3076 should give us approximately 40-50% more Guard-flagged nodes,
3077 improving the anonymity the Tor network can provide and also
3078 decreasing the dropoff in throughput that relays experience when
3079 they first get the Guard flag.
3080 - Allow enabling or disabling the *Statistics config options while
3084 - Update to the August 1 2010 Maxmind GeoLite Country database.
3085 - Have the controller interface give a more useful message than
3086 "Internal Error" in response to failed GETINFO requests.
3087 - Warn when the same option is provided more than once in a torrc
3088 file, on the command line, or in a single SETCONF statement, and
3089 the option is one that only accepts a single line. Closes bug 1384.
3090 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
3091 Patch from mingw-san.
3092 - Add support for the country code "{??}" in torrc options like
3093 ExcludeNodes, to indicate all routers of unknown country. Closes
3095 - Relays report the number of bytes spent on answering directory
3096 requests in extra-info descriptors similar to {read,write}-history.
3097 Implements enhancement 1790.
3099 o Minor bugfixes (on 0.2.1.x and earlier):
3100 - Complain if PublishServerDescriptor is given multiple arguments that
3101 include 0 or 1. This configuration will be rejected in the future.
3102 Bugfix on 0.2.0.1-alpha; closes bug 1107.
3103 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
3104 Bugfix on 0.2.0.13-alpha; closes bug 928.
3105 - Change "Application request when we're believed to be offline."
3106 notice to "Application request when we haven't used client
3107 functionality lately.", to clarify that it's not an error. Bugfix
3108 on 0.0.9.3; fixes bug 1222.
3109 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
3110 would return "551 Internal error" rather than "552 Unrecognized key
3111 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
3112 - Users can't configure a regular relay to be their bridge. It didn't
3113 work because when Tor fetched the bridge descriptor, it found
3114 that it already had it, and didn't realize that the purpose of the
3115 descriptor had changed. Now we replace routers with a purpose other
3116 than bridge with bridge descriptors when fetching them. Bugfix on
3117 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
3118 refetch the descriptor with router purpose 'general', disabling
3120 - Fix a rare bug in rend_fn unit tests: we would fail a test when
3121 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
3122 on 0.2.0.10-alpha; fixes bug 1808.
3123 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
3124 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
3125 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
3126 Servers can start sending this code when enough clients recognize
3127 it. Also update the spec to reflect this new reason. Bugfix on
3128 0.1.0.1-rc; fixes part of bug 1793.
3129 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
3130 when we switch from being a public relay to a bridge. Otherwise
3131 there will still be clients that see the relay in their consensus,
3132 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
3134 - Instead of giving an assertion failure on an internal mismatch
3135 on estimated freelist size, just log a BUG warning and try later.
3136 Mitigates but does not fix bug 1125.
3137 - Fix an assertion failure that could occur in caches or bridge users
3138 when using a very short voting interval on a testing network.
3139 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
3141 o Minor bugfixes (on 0.2.2.x):
3142 - Alter directory authorities to always consider Exit-flagged nodes
3143 as potential Guard nodes in their votes. The actual decision to
3144 use Exits as Guards is done in the consensus bandwidth weights.
3145 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
3146 - When the controller is reporting the purpose of circuits that
3147 didn't finish building before the circuit build timeout, it was
3148 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
3149 - Our libevent version parsing code couldn't handle versions like
3150 1.4.14b-stable and incorrectly warned the user about using an
3151 old and broken version of libevent. Treat 1.4.14b-stable like
3152 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
3154 - Don't use substitution references like $(VAR:MOD) when
3155 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
3156 '$(:x)' to 'x' rather than the empty string. This bites us in
3157 doc/ when configured with --disable-asciidoc. Bugfix on
3158 0.2.2.9-alpha; fixes bug 1773.
3159 - Remove a spurious hidden service server-side log notice about
3160 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
3162 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
3164 - Correctly report written bytes on linked connections. Found while
3165 implementing 1790. Bugfix on 0.2.2.4-alpha.
3166 - Fix three memory leaks: one in circuit_build_times_parse_state(),
3167 one in dirvote_add_signatures_to_pending_consensus(), and one every
3168 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
3169 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
3171 o Code simplifications and refactoring:
3172 - Take a first step towards making or.h smaller by splitting out
3173 function definitions for all source files in src/or/. Leave
3174 structures and defines in or.h for now.
3175 - Remove a bunch of unused function declarations as well as a block of
3176 #if 0'd code from the unit tests. Closes bug 1824.
3177 - New unit tests for exit-port history statistics; refactored exit
3178 statistics code to be more easily tested.
3179 - Remove the old debian/ directory from the main Tor distribution.
3180 The official Tor-for-debian git repository lives at the URL
3181 https://git.torproject.org/debian/tor.git
3184 Changes in version 0.2.2.14-alpha - 2010-07-12
3185 Tor 0.2.2.14-alpha greatly improves client-side handling of
3186 circuit build timeouts, which are used to estimate speed and improve
3187 performance. We also move to a much better GeoIP database, port Tor to
3188 Windows CE, introduce new compile flags that improve code security,
3189 add an eighth v3 directory authority, and address a lot of more
3193 - Tor directory authorities no longer crash when started with a
3194 cached-microdesc-consensus file in their data directory. Bugfix
3195 on 0.2.2.6-alpha; fixes bug 1532.
3196 - Treat an unset $HOME like an empty $HOME rather than triggering an
3197 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
3198 - Ignore negative and large circuit build timeout values that can
3199 happen during a suspend or hibernate. These values caused various
3200 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
3201 - Alter calculation of Pareto distribution parameter 'Xm' for
3202 Circuit Build Timeout learning to use the weighted average of the
3203 top N=3 modes (because we have three entry guards). Considering
3204 multiple modes should improve the timeout calculation in some cases,
3205 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
3207 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
3208 right censored distribution model. This approach improves over the
3209 synthetic timeout generation approach that was producing insanely
3210 high timeout values. Now we calculate build timeouts using truncated
3211 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
3212 - Do not close circuits that are under construction when they reach
3213 the circuit build timeout. Instead, leave them building (but do not
3214 use them) for up until the time corresponding to the 95th percentile
3215 on the Pareto CDF or 60 seconds, whichever is greater. This is done
3216 to provide better data for the new Pareto model. This percentile
3217 can be controlled by the consensus.
3220 - Move to the June 2010 Maxmind GeoLite country db (rather than the
3221 June 2009 ip-to-country GeoIP db) for our statistics that count
3222 how many users relays are seeing from each country. Now we have
3223 more accurate data for many African countries.
3224 - Port Tor to build and run correctly on Windows CE systems, using
3225 the wcecompat library. Contributed by Valerio Lupi.
3226 - New "--enable-gcc-hardening" ./configure flag (off by default)
3227 to turn on gcc compile time hardening options. It ensures
3228 that signed ints have defined behavior (-fwrapv), enables
3229 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
3230 with canaries (-fstack-protector-all), turns on ASLR protection if
3231 supported by the kernel (-fPIE, -pie), and adds additional security
3232 related warnings. Verified to work on Mac OS X and Debian Lenny.
3233 - New "--enable-linker-hardening" ./configure flag (off by default)
3234 to turn on ELF specific hardening features (relro, now). This does
3235 not work with Mac OS X or any other non-ELF binary format.
3237 o New directory authorities:
3238 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
3242 - New config option "WarnUnsafeSocks 0" disables the warning that
3243 occurs whenever Tor receives a socks handshake using a version of
3244 the socks protocol that can only provide an IP address (rather
3245 than a hostname). Setups that do DNS locally over Tor are fine,
3246 and we shouldn't spam the logs in that case.
3247 - Convert the HACKING file to asciidoc, and add a few new sections
3248 to it, explaining how we use Git, how we make changelogs, and
3249 what should go in a patch.
3250 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
3251 event, to give information on the current rate of circuit timeouts
3252 over our stored history.
3253 - Add ability to disable circuit build time learning via consensus
3254 parameter and via a LearnCircuitBuildTimeout config option. Also
3255 automatically disable circuit build time calculation if we are
3256 either a AuthoritativeDirectory, or if we fail to write our state
3257 file. Fixes bug 1296.
3258 - More gracefully handle corrupt state files, removing asserts
3259 in favor of saving a backup and resetting state.
3260 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
3264 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
3266 - When a2x fails, mention that the user could disable manpages instead
3267 of trying to fix their asciidoc installation.
3268 - Where available, use Libevent 2.0's periodic timers so that our
3269 once-per-second cleanup code gets called even more closely to
3270 once per second than it would otherwise. Fixes bug 943.
3271 - If you run a bridge that listens on multiple IP addresses, and
3272 some user configures a bridge address that uses a different IP
3273 address than your bridge writes in its router descriptor, and the
3274 user doesn't specify an identity key, their Tor would discard the
3275 descriptor because "it isn't one of our configured bridges", and
3276 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
3277 Bugfix on 0.2.0.3-alpha.
3278 - If OpenSSL fails to make a duplicate of a private or public key, log
3279 an error message and try to exit cleanly. May help with debugging
3280 if bug 1209 ever remanifests.
3281 - Save a couple bytes in memory allocation every time we escape
3282 certain characters in a string. Patch from Florian Zumbiehl.
3283 - Make it explicit that we don't cannibalize one-hop circuits. This
3284 happens in the wild, but doesn't turn out to be a problem because
3285 we fortunately don't use those circuits. Many thanks to outofwords
3286 for the initial analysis and to swissknife who confirmed that
3287 two-hop circuits are actually created.
3288 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
3289 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
3290 - Eliminate a case where a circuit build time warning was displayed
3291 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
3294 Changes in version 0.2.1.26 - 2010-05-02
3295 Tor 0.2.1.26 addresses the recent connection and memory overload
3296 problems we've been seeing on relays, especially relays with their
3297 DirPort open. If your relay has been crashing, or you turned it off
3298 because it used too many resources, give this release a try.
3300 This release also fixes yet another instance of broken OpenSSL libraries
3301 that was causing some relays to drop out of the consensus.
3304 - Teach relays to defend themselves from connection overload. Relays
3305 now close idle circuits early if it looks like they were intended
3306 for directory fetches. Relays are also more aggressive about closing
3307 TLS connections that have no circuits on them. Such circuits are
3308 unlikely to be re-used, and tens of thousands of them were piling
3309 up at the fast relays, causing the relays to run out of sockets
3310 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
3311 their directory fetches over TLS).
3312 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
3313 that claim to be earlier than 0.9.8m, but which have in reality
3314 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
3315 behavior. Possible fix for some cases of bug 1346.
3316 - Directory mirrors were fetching relay descriptors only from v2
3317 directory authorities, rather than v3 authorities like they should.
3318 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
3319 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
3322 - Finally get rid of the deprecated and now harmful notion of "clique
3323 mode", where directory authorities maintain TLS connections to
3327 - In the util/threads test, no longer free the test_mutex before all
3328 worker threads have finished. Bugfix on 0.2.1.6-alpha.
3329 - The master thread could starve the worker threads quite badly on
3330 certain systems, causing them to run only partially in the allowed
3331 window. This resulted in test failures. Now the master thread sleeps
3332 occasionally for a few microseconds while the two worker-threads
3333 compete for the mutex. Bugfix on 0.2.0.1-alpha.
3336 Changes in version 0.2.2.13-alpha - 2010-04-24
3337 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
3338 problems we've been seeing on relays, especially relays with their
3339 DirPort open. If your relay has been crashing, or you turned it off
3340 because it used too many resources, give this release a try.
3343 - Teach relays to defend themselves from connection overload. Relays
3344 now close idle circuits early if it looks like they were intended
3345 for directory fetches. Relays are also more aggressive about closing
3346 TLS connections that have no circuits on them. Such circuits are
3347 unlikely to be re-used, and tens of thousands of them were piling
3348 up at the fast relays, causing the relays to run out of sockets
3349 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
3350 their directory fetches over TLS).
3353 - Finally get rid of the deprecated and now harmful notion of "clique
3354 mode", where directory authorities maintain TLS connections to
3356 - Directory authorities now do an immediate reachability check as soon
3357 as they hear about a new relay. This change should slightly reduce
3358 the time between setting up a relay and getting listed as running
3359 in the consensus. It should also improve the time between setting
3360 up a bridge and seeing use by bridge users.
3361 - Directory authorities no longer launch a TLS connection to every
3362 relay as they startup. Now that we have 2k+ descriptors cached,
3363 the resulting network hiccup is becoming a burden. Besides,
3364 authorities already avoid voting about Running for the first half
3365 hour of their uptime.
3368 Changes in version 0.2.2.12-alpha - 2010-04-20
3369 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
3370 handle and vote on descriptors. It was causing relays to drop out of
3374 - Many relays have been falling out of the consensus lately because
3375 not enough authorities know about their descriptor for them to get
3376 a majority of votes. When we deprecated the v2 directory protocol,
3377 we got rid of the only way that v3 authorities can hear from each
3378 other about other descriptors. Now authorities examine every v3
3379 vote for new descriptors, and fetch them from that authority. Bugfix
3381 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
3382 and a warning in or.h related to bandwidth_weight_rule_t that
3383 prevented clean compile on OS X. Fixes bug 1363; bugfix on
3385 - Fix a segfault on relays when DirReqStatistics is enabled
3386 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
3390 - Demote a confusing TLS warning that relay operators might get when
3391 someone tries to talk to their OrPort. It is neither the operator's
3392 fault nor can they do anything about it. Fixes bug 1364; bugfix
3396 Changes in version 0.2.2.11-alpha - 2010-04-15
3397 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
3398 libraries that was causing some relays to drop out of the consensus.
3401 - Directory mirrors were fetching relay descriptors only from v2
3402 directory authorities, rather than v3 authorities like they should.
3403 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
3404 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
3405 - Fix a parsing error that made every possible value of
3406 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
3407 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
3408 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
3409 about the option without breaking older ones.
3410 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
3411 that claim to be earlier than 0.9.8m, but which have in reality
3412 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
3413 behavior. Possible fix for some cases of bug 1346.
3416 - Experiment with a more aggressive approach to preventing clients
3417 from making one-hop exit streams. Exit relays who want to try it
3418 out can set "RefuseUnknownExits 1" in their torrc, and then look
3419 for "Attempt by %s to open a stream" log messages. Let us know
3421 - Add support for statically linking zlib by specifying
3422 --enable-static-zlib, to go with our support for statically linking
3423 openssl and libevent. Resolves bug 1358.
3426 - Fix a segfault that happens whenever a Tor client that is using
3427 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
3429 - When we cleaned up the contrib/tor-exit-notice.html file, we left
3430 out the first line. Fixes bug 1295.
3431 - When building the manpage from a tarball, we required asciidoc, but
3432 the asciidoc -> roff/html conversion was already done for the
3433 tarball. Make 'make' complain only when we need asciidoc (either
3434 because we're compiling directly from git, or because we altered
3435 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
3436 - When none of the directory authorities vote on any params, Tor
3437 segfaulted when trying to make the consensus from the votes. We
3438 didn't trigger the bug in practice, because authorities do include
3439 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
3442 - In the util/threads test, no longer free the test_mutex before all
3443 worker threads have finished. Bugfix on 0.2.1.6-alpha.
3444 - The master thread could starve the worker threads quite badly on
3445 certain systems, causing them to run only partially in the allowed
3446 window. This resulted in test failures. Now the master thread sleeps
3447 occasionally for a few microseconds while the two worker-threads
3448 compete for the mutex. Bugfix on 0.2.0.1-alpha.
3451 Changes in version 0.2.2.10-alpha - 2010-03-07
3452 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
3453 could prevent relays from guessing their IP address correctly. It also
3454 starts the groundwork for another client-side performance boost, since
3455 currently we're not making efficient use of relays that have both the
3456 Guard flag and the Exit flag.
3459 - Fix a regression from our patch for bug 1244 that caused relays
3460 to guess their IP address incorrectly if they didn't set Address
3461 in their torrc and/or their address fails to resolve. Bugfix on
3462 0.2.2.9-alpha; fixes bug 1269.
3464 o Major features (performance):
3465 - Directory authorities now compute consensus weightings that instruct
3466 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
3467 and no flag. Clients that use these weightings will distribute
3468 network load more evenly across these different relay types. The
3469 weightings are in the consensus so we can change them globally in
3470 the future. Extra thanks to "outofwords" for finding some nasty
3471 security bugs in the first implementation of this feature.
3473 o Minor features (performance):
3474 - Always perform router selections using weighted relay bandwidth,
3475 even if we don't need a high capacity circuit at the time. Non-fast
3476 circuits now only differ from fast ones in that they can use relays
3477 not marked with the Fast flag. This "feature" could turn out to
3478 be a horrible bug; we should investigate more before it goes into
3482 - Allow disabling building of the manpages. Skipping the manpage
3483 speeds up the build considerably.
3485 o Minor bugfixes (on 0.2.2.x):
3486 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
3487 Bugfix on 0.2.2.9-alpha.
3488 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
3489 config option. Bugfix on 0.2.2.7-alpha.
3490 - Ship the asciidoc-helper file in the tarball, so that people can
3491 build from source if they want to, and touching the .1.txt files
3492 doesn't break the build. Bugfix on 0.2.2.9-alpha.
3494 o Minor bugfixes (on 0.2.1.x or earlier):
3495 - Fix a dereference-then-NULL-check sequence when publishing
3496 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
3498 - Fix another dereference-then-NULL-check sequence. Bugfix on
3499 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
3500 - Make sure we treat potentially not NUL-terminated strings correctly.
3501 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
3503 o Code simplifications and refactoring:
3504 - Fix some urls in the exit notice file and make it XHTML1.1 strict
3505 compliant. Based on a patch from Christian Kujau.
3506 - Don't use sed in asciidoc-helper anymore.
3507 - Make the build process fail if asciidoc cannot be found and
3508 building with asciidoc isn't disabled.
3511 Changes in version 0.2.2.9-alpha - 2010-02-22
3512 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
3513 location of a directory authority, and cleans up a bunch of small bugs.
3515 o Directory authority changes:
3516 - Change IP address for dannenberg (v3 directory authority), and
3517 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
3518 service directory authority) from the list.
3521 - Make Tor work again on the latest OS X: when deciding whether to
3522 use strange flags to turn TLS renegotiation on, detect the OpenSSL
3523 version at run-time, not compile time. We need to do this because
3524 Apple doesn't update its dev-tools headers when it updates its
3525 libraries in a security patch.
3526 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
3527 that could happen on 32-bit platforms with 64-bit time_t. Also fix
3528 a memory leak when requesting a hidden service descriptor we've
3529 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
3531 - Authorities could be tricked into giving out the Exit flag to relays
3532 that didn't allow exiting to any ports. This bug could screw
3533 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
3534 1238. Bug discovered by Martin Kowalczyk.
3535 - When freeing a session key, zero it out completely. We only zeroed
3536 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
3537 patched by ekir. Fixes bug 1254.
3540 - Fix static compilation by listing the openssl libraries in the right
3541 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
3542 - Resume handling .exit hostnames in a special way: originally we
3543 stripped the .exit part and used the requested exit relay. In
3544 0.2.2.1-alpha we stopped treating them in any special way, meaning
3545 if you use a .exit address then Tor will pass it on to the exit
3546 relay. Now we reject the .exit stream outright, since that behavior
3547 might be more expected by the user. Found and diagnosed by Scott
3548 Bennett and Downie on or-talk.
3549 - Don't spam the controller with events when we have no file
3550 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
3551 for log messages was already solved from bug 748.)
3552 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
3554 - Make the DNSPort option work with libevent 2.x. Don't alter the
3555 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
3556 - Emit a GUARD DROPPED controller event for a case we missed.
3557 - Make more fields in the controller protocol case-insensitive, since
3558 control-spec.txt said they were.
3559 - Refactor resolve_my_address() to not use gethostbyname() anymore.
3560 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
3561 - Fix a spec conformance issue: the network-status-version token
3562 must be the first token in a v3 consensus or vote. Discovered by
3563 parakeep. Bugfix on 0.2.0.3-alpha.
3565 o Code simplifications and refactoring:
3566 - Generate our manpage and HTML documentation using Asciidoc. This
3567 change should make it easier to maintain the documentation, and
3569 - Remove the --enable-iphone option. According to reports from Marco
3570 Bonetti, Tor builds fine without any special tweaking on recent
3571 iPhone SDK versions.
3572 - Removed some unnecessary files from the source distribution. The
3573 AUTHORS file has now been merged into the people page on the
3574 website. The roadmaps and design doc can now be found in the
3575 projects directory in svn.
3576 - Enabled various circuit build timeout constants to be controlled
3577 by consensus parameters. Also set better defaults for these
3578 parameters based on experimentation on broadband and simulated
3582 - The 'EXTENDCIRCUIT' control port command can now be used with
3583 a circ id of 0 and no path. This feature will cause Tor to build
3584 a new 'fast' general purpose circuit using its own path selection
3586 - Added a BUILDTIMEOUT_SET controller event to describe changes
3587 to the circuit build timeout.
3588 - Future-proof the controller protocol a bit by ignoring keyword
3589 arguments we do not recognize.
3590 - Expand homedirs passed to tor-checkkey. This should silence a
3591 coverity complaint about passing a user-supplied string into
3592 open() without checking it.
3595 Changes in version 0.2.1.25 - 2010-03-16
3596 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
3597 prevent relays from guessing their IP address correctly. It also fixes
3598 several minor potential security bugs.
3601 - Fix a regression from our patch for bug 1244 that caused relays
3602 to guess their IP address incorrectly if they didn't set Address
3603 in their torrc and/or their address fails to resolve. Bugfix on
3604 0.2.1.23; fixes bug 1269.
3605 - When freeing a session key, zero it out completely. We only zeroed
3606 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
3607 patched by ekir. Fixes bug 1254.
3610 - Fix a dereference-then-NULL-check sequence when publishing
3611 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
3613 - Fix another dereference-then-NULL-check sequence. Bugfix on
3614 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
3615 - Make sure we treat potentially not NUL-terminated strings correctly.
3616 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
3620 Changes in version 0.2.1.24 - 2010-02-21
3621 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
3625 - Work correctly out-of-the-box with even more vendor-patched versions
3626 of OpenSSL. In particular, make it so Debian and OS X don't need
3627 customized patches to run/build.
3630 Changes in version 0.2.1.23 - 2010-02-13
3631 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
3632 again on the latest OS X, and updates the location of a directory
3635 o Major bugfixes (performance):
3636 - We were selecting our guards uniformly at random, and then weighting
3637 which of our guards we'd use uniformly at random. This imbalance
3638 meant that Tor clients were severely limited on throughput (and
3639 probably latency too) by the first hop in their circuit. Now we
3640 select guards weighted by currently advertised bandwidth. We also
3641 automatically discard guards picked using the old algorithm. Fixes
3642 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
3645 - Make Tor work again on the latest OS X: when deciding whether to
3646 use strange flags to turn TLS renegotiation on, detect the OpenSSL
3647 version at run-time, not compile time. We need to do this because
3648 Apple doesn't update its dev-tools headers when it updates its
3649 libraries in a security patch.
3650 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
3651 that could happen on 32-bit platforms with 64-bit time_t. Also fix
3652 a memory leak when requesting a hidden service descriptor we've
3653 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
3656 o Directory authority changes:
3657 - Change IP address for dannenberg (v3 directory authority), and
3658 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
3659 service directory authority) from the list.
3662 - Refactor resolve_my_address() to not use gethostbyname() anymore.
3663 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
3666 - Avoid a mad rush at the beginning of each month when each client
3667 rotates half of its guards. Instead we spread the rotation out
3668 throughout the month, but we still avoid leaving a precise timestamp
3669 in the state file about when we first picked the guard. Improves
3670 over the behavior introduced in 0.1.2.17.
3673 Changes in version 0.2.2.8-alpha - 2010-01-26
3674 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
3675 causing bridge relays to disappear. If you're running a bridge,
3679 - Fix a memory corruption bug on bridges that occured during the
3680 inclusion of stats data in extra-info descriptors. Also fix the
3681 interface for geoip_get_bridge_stats* to prevent similar bugs in
3682 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
3683 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
3686 - Ignore OutboundBindAddress when connecting to localhost.
3687 Connections to localhost need to come _from_ localhost, or else
3688 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
3692 Changes in version 0.2.2.7-alpha - 2010-01-19
3693 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
3694 as laying the groundwork for further relay-side performance fixes. It
3695 also starts cleaning up client behavior with respect to the EntryNodes,
3696 ExitNodes, and StrictNodes config options.
3698 This release also rotates two directory authority keys, due to a
3699 security breach of some of the Torproject servers.
3701 o Directory authority changes:
3702 - Rotate keys (both v3 identity and relay identity) for moria1
3705 o Major features (performance):
3706 - We were selecting our guards uniformly at random, and then weighting
3707 which of our guards we'd use uniformly at random. This imbalance
3708 meant that Tor clients were severely limited on throughput (and
3709 probably latency too) by the first hop in their circuit. Now we
3710 select guards weighted by currently advertised bandwidth. We also
3711 automatically discard guards picked using the old algorithm. Fixes
3712 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
3713 - When choosing which cells to relay first, relays can now favor
3714 circuits that have been quiet recently, to provide lower latency
3715 for low-volume circuits. By default, relays enable or disable this
3716 feature based on a setting in the consensus. You can override
3717 this default by using the new "CircuitPriorityHalflife" config
3718 option. Design and code by Ian Goldberg, Can Tang, and Chris
3720 - Add separate per-conn write limiting to go with the per-conn read
3721 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
3722 but never per-conn write limits.
3723 - New consensus params "bwconnrate" and "bwconnburst" to let us
3724 rate-limit client connections as they enter the network. It's
3725 controlled in the consensus so we can turn it on and off for
3726 experiments. It's starting out off. Based on proposal 163.
3728 o Major features (relay selection options):
3729 - Switch to a StrictNodes config option, rather than the previous
3730 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
3731 "StrictExcludeNodes" option.
3732 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
3733 change during a config reload, mark and discard all our origin
3734 circuits. This fix should address edge cases where we change the
3735 config options and but then choose a circuit that we created before
3737 - If EntryNodes or ExitNodes are set, be more willing to use an
3738 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
3740 - Make EntryNodes config option much more aggressive even when
3741 StrictNodes is not set. Before it would prepend your requested
3742 entrynodes to your list of guard nodes, but feel free to use others
3743 after that. Now it chooses only from your EntryNodes if any of
3744 those are available, and only falls back to others if a) they're
3745 all down and b) StrictNodes is not set.
3746 - Now we refresh your entry guards from EntryNodes at each consensus
3747 fetch -- rather than just at startup and then they slowly rot as
3748 the network changes.
3751 - Stop bridge directory authorities from answering dbg-stability.txt
3752 directory queries, which would let people fetch a list of all
3753 bridge identities they track. Bugfix on 0.2.1.6-alpha.
3756 - Log a notice when we get a new control connection. Now it's easier
3757 for security-conscious users to recognize when a local application
3758 is knocking on their controller door. Suggested by bug 1196.
3759 - New config option "CircuitStreamTimeout" to override our internal
3760 timeout schedule for how many seconds until we detach a stream from
3761 a circuit and try a new circuit. If your network is particularly
3762 slow, you might want to set this to a number like 60.
3763 - New controller command "getinfo config-text". It returns the
3764 contents that Tor would write if you send it a SAVECONF command,
3765 so the controller can write the file to disk itself.
3766 - New options for SafeLogging to allow scrubbing only log messages
3767 generated while acting as a relay.
3768 - Ship the bridges spec file in the tarball too.
3769 - Avoid a mad rush at the beginning of each month when each client
3770 rotates half of its guards. Instead we spread the rotation out
3771 throughout the month, but we still avoid leaving a precise timestamp
3772 in the state file about when we first picked the guard. Improves
3773 over the behavior introduced in 0.1.2.17.
3775 o Minor bugfixes (compiling):
3776 - Fix compilation on OS X 10.3, which has a stub mlockall() but
3777 hides it. Bugfix on 0.2.2.6-alpha.
3778 - Fix compilation on Solaris by removing support for the
3779 DisableAllSwap config option. Solaris doesn't have an rlimit for
3780 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
3783 o Minor bugfixes (crashes):
3784 - Do not segfault when writing buffer stats when we haven't observed
3785 a single circuit to report about. Found by Fabian Lanze. Bugfix on
3787 - If we're in the pathological case where there's no exit bandwidth
3788 but there is non-exit bandwidth, or no guard bandwidth but there
3789 is non-guard bandwidth, don't crash during path selection. Bugfix
3791 - Fix an impossible-to-actually-trigger buffer overflow in relay
3792 descriptor generation. Bugfix on 0.1.0.15.
3794 o Minor bugfixes (privacy):
3795 - Fix an instance where a Tor directory mirror might accidentally
3796 log the IP address of a misbehaving Tor client. Bugfix on
3798 - Don't list Windows capabilities in relay descriptors. We never made
3799 use of them, and maybe it's a bad idea to publish them. Bugfix
3802 o Minor bugfixes (other):
3803 - Resolve an edge case in path weighting that could make us misweight
3804 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
3805 - Fix statistics on client numbers by country as seen by bridges that
3806 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
3807 intervals instead of variable 12-to-48-hour intervals.
3808 - After we free an internal connection structure, overwrite it
3809 with a different memory value than we use for overwriting a freed
3810 internal circuit structure. Should help with debugging. Suggested
3812 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
3816 - Remove the HSAuthorityRecordStats option that version 0 hidden
3817 service authorities could have used to track statistics of overall
3818 hidden service usage.
3821 Changes in version 0.2.1.22 - 2010-01-19
3822 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
3823 authorities -- it would tell you its whole history of bridge descriptors
3824 if you make the right directory request. This stable update also
3825 rotates two of the seven v3 directory authority keys and locations.
3827 o Directory authority changes:
3828 - Rotate keys (both v3 identity and relay identity) for moria1
3832 - Stop bridge directory authorities from answering dbg-stability.txt
3833 directory queries, which would let people fetch a list of all
3834 bridge identities they track. Bugfix on 0.2.1.6-alpha.
3837 Changes in version 0.2.1.21 - 2009-12-21
3838 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
3839 library. If you use Tor on Linux / Unix and you're getting SSL
3840 renegotiation errors, upgrading should help. We also recommend an
3841 upgrade if you're an exit relay.
3844 - Work around a security feature in OpenSSL 0.9.8l that prevents our
3845 handshake from working unless we explicitly tell OpenSSL that we
3846 are using SSL renegotiation safely. We are, of course, but OpenSSL
3847 0.9.8l won't work unless we say we are.
3848 - Avoid crashing if the client is trying to upload many bytes and the
3849 circuit gets torn down at the same time, or if the flip side
3850 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
3853 - Do not refuse to learn about authority certs and v2 networkstatus
3854 documents that are older than the latest consensus. This bug might
3855 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
3856 Spotted and fixed by xmux.
3857 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
3858 trigger platform-specific option misparsing case found by Coverity
3860 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
3861 trigger assert. Fixes bug 1173.
3864 Changes in version 0.2.2.6-alpha - 2009-11-19
3865 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
3866 support for the new lower-footprint "microdescriptor" directory design,
3867 future-proofing our consensus format against new hash functions or
3868 other changes, and an Android port. It also makes Tor compatible with
3869 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
3872 - Directory authorities can now create, vote on, and serve multiple
3873 parallel formats of directory data as part of their voting process.
3874 Partially implements Proposal 162: "Publish the consensus in
3876 - Directory authorities can now agree on and publish small summaries
3877 of router information that clients can use in place of regular
3878 server descriptors. This transition will eventually allow clients
3879 to use far less bandwidth for downloading information about the
3880 network. Begins the implementation of Proposal 158: "Clients
3881 download consensus + microdescriptors".
3882 - The directory voting system is now extensible to use multiple hash
3883 algorithms for signatures and resource selection. Newer formats
3884 are signed with SHA256, with a possibility for moving to a better
3885 hash algorithm in the future.
3886 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
3887 current and future memory pages via mlockall(). On supported
3888 platforms (modern Linux and probably BSD but not Windows or OS X),
3889 this should effectively disable any and all attempts to page out
3890 memory. This option requires that you start your Tor as root --
3891 if you use DisableAllSwap, please consider using the User option
3892 to properly reduce the privileges of your Tor.
3893 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
3894 to help Tor build correctly for Android phones.
3897 - Work around a security feature in OpenSSL 0.9.8l that prevents our
3898 handshake from working unless we explicitly tell OpenSSL that we
3899 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
3900 won't work unless we say we are.
3903 - Fix a crash bug when trying to initialize the evdns module in
3904 Libevent 2. Bugfix on 0.2.1.16-rc.
3905 - Stop logging at severity 'warn' when some other Tor client tries
3906 to establish a circuit with us using weak DH keys. It's a protocol
3907 violation, but that doesn't mean ordinary users need to hear about
3908 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
3909 - Do not refuse to learn about authority certs and v2 networkstatus
3910 documents that are older than the latest consensus. This bug might
3911 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
3912 Spotted and fixed by xmux.
3913 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
3914 - If all authorities restart at once right before a consensus vote,
3915 nobody will vote about "Running", and clients will get a consensus
3916 with no usable relays. Instead, authorities refuse to build a
3917 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
3918 - If your relay can't keep up with the number of incoming create
3919 cells, it would log one warning per failure into your logs. Limit
3920 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
3921 - Bridges now use "reject *:*" as their default exit policy. Bugfix
3922 on 0.2.0.3-alpha; fixes bug 1113.
3923 - Fix a memory leak on directory authorities during voting that was
3924 introduced in 0.2.2.1-alpha. Found via valgrind.
3927 Changes in version 0.2.1.20 - 2009-10-15
3928 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
3929 services at once, prepares for more performance improvements, and
3930 fixes a bunch of smaller bugs.
3932 The Windows and OS X bundles also include a more recent Vidalia,
3933 and switch from Privoxy to Polipo.
3935 The OS X installers are now drag and drop. It's best to un-install
3936 Tor/Vidalia and then install this new bundle, rather than upgrade. If
3937 you want to upgrade, you'll need to update the paths for Tor and Polipo
3938 in the Vidalia Settings window.
3941 - Send circuit or stream sendme cells when our window has decreased
3942 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
3943 by Karsten when testing the "reduce circuit window" performance
3944 patch. Bugfix on the 54th commit on Tor -- from July 2002,
3945 before the release of Tor 0.0.0. This is the new winner of the
3947 - Fix a remotely triggerable memory leak when a consensus document
3948 contains more than one signature from the same voter. Bugfix on
3950 - Avoid segfault in rare cases when finishing an introduction circuit
3951 as a client and finding out that we don't have an introduction key
3952 for it. Fixes bug 1073. Reported by Aaron Swartz.
3955 - Tor now reads the "circwindow" parameter out of the consensus,
3956 and uses that value for its circuit package window rather than the
3957 default of 1000 cells. Begins the implementation of proposal 168.
3959 o New directory authorities:
3960 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
3962 - Move moria1 and tonga to alternate IP addresses.
3965 - Fix a signed/unsigned compile warning in 0.2.1.19.
3966 - Fix possible segmentation fault on directory authorities. Bugfix on
3968 - Fix an extremely rare infinite recursion bug that could occur if
3969 we tried to log a message after shutting down the log subsystem.
3970 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
3971 - Fix an obscure bug where hidden services on 64-bit big-endian
3972 systems might mis-read the timestamp in v3 introduce cells, and
3973 refuse to connect back to the client. Discovered by "rotor".
3974 Bugfix on 0.2.1.6-alpha.
3975 - We were triggering a CLOCK_SKEW controller status event whenever
3976 we connect via the v2 connection protocol to any relay that has
3977 a wrong clock. Instead, we should only inform the controller when
3978 it's a trusted authority that claims our clock is wrong. Bugfix
3979 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
3980 - We were telling the controller about CHECKING_REACHABILITY and
3981 REACHABILITY_FAILED status events whenever we launch a testing
3982 circuit or notice that one has failed. Instead, only tell the
3983 controller when we want to inform the user of overall success or
3984 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
3986 - Don't warn when we're using a circuit that ends with a node
3987 excluded in ExcludeExitNodes, but the circuit is not used to access
3988 the outside world. This should help fix bug 1090. Bugfix on
3990 - Work around a small memory leak in some versions of OpenSSL that
3991 stopped the memory used by the hostname TLS extension from being
3995 - Add a "getinfo status/accepted-server-descriptor" controller
3996 command, which is the recommended way for controllers to learn
3997 whether our server descriptor has been successfully received by at
3998 least on directory authority. Un-recommend good-server-descriptor
3999 getinfo and status events until we have a better design for them.
4002 Changes in version 0.2.2.5-alpha - 2009-10-11
4003 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
4006 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
4008 o Directory authorities:
4009 - Temporarily (just for this release) move dizum to an alternate
4013 Changes in version 0.2.2.4-alpha - 2009-10-10
4014 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
4015 introduces a new unit test framework, shifts directry authority
4016 addresses around to reduce the impact from recent blocking events,
4017 and fixes a few smaller bugs.
4020 - Fix several more asserts in the circuit_build_times code, for
4021 example one that causes Tor to fail to start once we have
4022 accumulated 5000 build times in the state file. Bugfixes on
4023 0.2.2.2-alpha; fixes bug 1108.
4025 o New directory authorities:
4026 - Move moria1 and Tonga to alternate IP addresses.
4029 - Log SSL state transitions at debug level during handshake, and
4030 include SSL states in error messages. This may help debug future
4031 SSL handshake issues.
4032 - Add a new "Handshake" log domain for activities that happen
4033 during the TLS handshake.
4034 - Revert to the "June 3 2009" ip-to-country file. The September one
4035 seems to have removed most US IP addresses.
4036 - Directory authorities now reject Tor relays with versions less than
4037 0.1.2.14. This step cuts out four relays from the current network,
4038 none of which are very big.
4041 - Fix a couple of smaller issues with gathering statistics. Bugfixes
4043 - Fix two memory leaks in the error case of
4044 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
4045 - Don't count one-hop circuits when we're estimating how long it
4046 takes circuits to build on average. Otherwise we'll set our circuit
4047 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
4048 - Directory authorities no longer change their opinion of, or vote on,
4049 whether a router is Running, unless they have themselves been
4050 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
4053 o Code simplifications and refactoring:
4054 - Revise our unit tests to use the "tinytest" framework, so we
4055 can run tests in their own processes, have smarter setup/teardown
4056 code, and so on. The unit test code has moved to its own
4057 subdirectory, and has been split into multiple modules.
4060 Changes in version 0.2.2.3-alpha - 2009-09-23
4061 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
4064 - Fix an overzealous assert in our new circuit build timeout code.
4065 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
4068 - If the networkstatus consensus tells us that we should use a
4069 negative circuit package window, ignore it. Otherwise we'll
4070 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
4073 Changes in version 0.2.2.2-alpha - 2009-09-21
4074 Tor 0.2.2.2-alpha introduces our latest performance improvement for
4075 clients: Tor tracks the average time it takes to build a circuit, and
4076 avoids using circuits that take too long to build. For fast connections,
4077 this feature can cut your expected latency in half. For slow or flaky
4078 connections, it could ruin your Tor experience. Let us know if it does!
4081 - Tor now tracks how long it takes to build client-side circuits
4082 over time, and adapts its timeout to local network performance.
4083 Since a circuit that takes a long time to build will also provide
4084 bad performance, we get significant latency improvements by
4085 discarding the slowest 20% of circuits. Specifically, Tor creates
4086 circuits more aggressively than usual until it has enough data
4087 points for a good timeout estimate. Implements proposal 151.
4088 We are especially looking for reports (good and bad) from users with
4089 both EDGE and broadband connections that can move from broadband
4090 to EDGE and find out if the build-time data in the .tor/state gets
4091 reset without loss of Tor usability. You should also see a notice
4092 log message telling you that Tor has reset its timeout.
4093 - Directory authorities can now vote on arbitary integer values as
4094 part of the consensus process. This is designed to help set
4095 network-wide parameters. Implements proposal 167.
4096 - Tor now reads the "circwindow" parameter out of the consensus,
4097 and uses that value for its circuit package window rather than the
4098 default of 1000 cells. Begins the implementation of proposal 168.
4101 - Fix a remotely triggerable memory leak when a consensus document
4102 contains more than one signature from the same voter. Bugfix on
4106 - Fix an extremely rare infinite recursion bug that could occur if
4107 we tried to log a message after shutting down the log subsystem.
4108 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
4109 - Fix parsing for memory or time units given without a space between
4110 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
4111 - A networkstatus vote must contain exactly one signature. Spec
4112 conformance issue. Bugfix on 0.2.0.3-alpha.
4113 - Fix an obscure bug where hidden services on 64-bit big-endian
4114 systems might mis-read the timestamp in v3 introduce cells, and
4115 refuse to connect back to the client. Discovered by "rotor".
4116 Bugfix on 0.2.1.6-alpha.
4117 - We were triggering a CLOCK_SKEW controller status event whenever
4118 we connect via the v2 connection protocol to any relay that has
4119 a wrong clock. Instead, we should only inform the controller when
4120 it's a trusted authority that claims our clock is wrong. Bugfix
4121 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
4122 - We were telling the controller about CHECKING_REACHABILITY and
4123 REACHABILITY_FAILED status events whenever we launch a testing
4124 circuit or notice that one has failed. Instead, only tell the
4125 controller when we want to inform the user of overall success or
4126 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
4128 - Don't warn when we're using a circuit that ends with a node
4129 excluded in ExcludeExitNodes, but the circuit is not used to access
4130 the outside world. This should help fix bug 1090, but more problems
4131 remain. Bugfix on 0.2.1.6-alpha.
4132 - Work around a small memory leak in some versions of OpenSSL that
4133 stopped the memory used by the hostname TLS extension from being
4135 - Make our 'torify' script more portable; if we have only one of
4136 'torsocks' or 'tsocks' installed, don't complain to the user;
4137 and explain our warning about tsocks better.
4140 - Add a "getinfo status/accepted-server-descriptor" controller
4141 command, which is the recommended way for controllers to learn
4142 whether our server descriptor has been successfully received by at
4143 least on directory authority. Un-recommend good-server-descriptor
4144 getinfo and status events until we have a better design for them.
4145 - Update to the "September 4 2009" ip-to-country file.
4148 Changes in version 0.2.2.1-alpha - 2009-08-26
4149 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
4150 Tor clients to bootstrap on networks where only port 80 is reachable,
4151 makes it more straightforward to support hardware crypto accelerators,
4152 and starts the groundwork for gathering stats safely at relays.
4155 - Start the process of disabling ".exit" address notation, since it
4156 can be used for a variety of esoteric application-level attacks
4157 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
4160 o New directory authorities:
4161 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
4165 - New AccelName and AccelDir options add support for dynamic OpenSSL
4166 hardware crypto acceleration engines.
4167 - Tor now supports tunneling all of its outgoing connections over
4168 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
4169 configuration options. Code by Christopher Davis.
4172 - Send circuit or stream sendme cells when our window has decreased
4173 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
4174 by Karsten when testing the "reduce circuit window" performance
4175 patch. Bugfix on the 54th commit on Tor -- from July 2002,
4176 before the release of Tor 0.0.0. This is the new winner of the
4179 o New options for gathering stats safely:
4180 - Directory mirrors that set "DirReqStatistics 1" write statistics
4181 about directory requests to disk every 24 hours. As compared to the
4182 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
4183 1) stats are written to disk exactly every 24 hours; 2) estimated
4184 shares of v2 and v3 requests are determined as mean values, not at
4185 the end of a measurement period; 3) unresolved requests are listed
4186 with country code '??'; 4) directories also measure download times.
4187 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
4188 number of exit streams and transferred bytes per port to disk every
4190 - Relays that set "CellStatistics 1" write statistics on how long
4191 cells spend in their circuit queues to disk every 24 hours.
4192 - Entry nodes that set "EntryStatistics 1" write statistics on the
4193 rough number and origins of connecting clients to disk every 24
4195 - Relays that write any of the above statistics to disk and set
4196 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
4197 their extra-info documents.
4200 - New --digests command-line switch to output the digests of the
4201 source files Tor was built with.
4202 - The "torify" script now uses torsocks where available.
4203 - The memarea code now uses a sentinel value at the end of each area
4204 to make sure nothing writes beyond the end of an area. This might
4205 help debug some conceivable causes of bug 930.
4206 - Time and memory units in the configuration file can now be set to
4207 fractional units. For example, "2.5 GB" is now a valid value for
4209 - Certain Tor clients (such as those behind check.torproject.org) may
4210 want to fetch the consensus in an extra early manner. To enable this
4211 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
4212 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
4213 as only certain clients who must have this information sooner should
4215 - Instead of adding the svn revision to the Tor version string, report
4216 the git commit (when we're building from a git checkout).
4219 - If any of the v3 certs we download are unparseable, we should
4220 actually notice the failure so we don't retry indefinitely. Bugfix
4221 on 0.2.0.x; reported by "rotator".
4222 - If the cached cert file is unparseable, warn but don't exit.
4223 - Fix possible segmentation fault on directory authorities. Bugfix on
4225 - When Tor fails to parse a descriptor of any kind, dump it to disk.
4226 Might help diagnosing bug 1051.
4228 o Deprecated and removed features:
4229 - The controller no longer accepts the old obsolete "addr-mappings/"
4230 or "unregistered-servers-" GETINFO values.
4231 - Hidden services no longer publish version 0 descriptors, and clients
4232 do not request or use version 0 descriptors. However, the old hidden
4233 service authorities still accept and serve version 0 descriptors
4234 when contacted by older hidden services/clients.
4235 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
4236 always on; using them is necessary for correct forward-compatible
4238 - Remove support for .noconnect style addresses. Nobody was using
4239 them, and they provided another avenue for detecting Tor users
4240 via application-level web tricks.
4242 o Packaging changes:
4243 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
4244 installer bundles. See
4245 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
4246 for details of what's new in Vidalia 0.2.3.
4247 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
4248 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
4249 configuration file, rather than the old Privoxy.
4250 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
4251 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
4252 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
4253 better compatibility with OS X 10.6, aka Snow Leopard.
4254 - OS X Vidalia Bundle: The multi-package installer is now replaced
4255 by a simple drag and drop to the /Applications folder. This change
4256 occurred with the upgrade to Vidalia 0.2.3.
4259 Changes in version 0.2.1.19 - 2009-07-28
4260 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
4261 services on Tor 0.2.1.3-alpha through 0.2.1.18.
4264 - Make accessing hidden services on 0.2.1.x work right again.
4265 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
4266 part of patch provided by "optimist".
4269 - When a relay/bridge is writing out its identity key fingerprint to
4270 the "fingerprint" file and to its logs, write it without spaces. Now
4271 it will look like the fingerprints in our bridges documentation,
4272 and confuse fewer users.
4275 - Relays no longer publish a new server descriptor if they change
4276 their MaxAdvertisedBandwidth config option but it doesn't end up
4277 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
4278 fixes bug 1026. Patch from Sebastian.
4279 - Avoid leaking memory every time we get a create cell but we have
4280 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
4281 fixes bug 1034. Reported by BarkerJr.
4284 Changes in version 0.2.1.18 - 2009-07-24
4285 Tor 0.2.1.18 lays the foundations for performance improvements,
4286 adds status events to help users diagnose bootstrap problems, adds
4287 optional authentication/authorization for hidden services, fixes a
4288 variety of potential anonymity problems, and includes a huge pile of
4289 other features and bug fixes.
4292 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
4295 Changes in version 0.2.1.17-rc - 2009-07-07
4296 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
4297 candidate for the 0.2.1.x series. It lays the groundwork for further
4298 client performance improvements, and also fixes a big bug with directory
4299 authorities that were causing them to assign Guard and Stable flags
4302 The Windows bundles also finally include the geoip database that we
4303 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
4304 should actually install Torbutton rather than giving you a cryptic
4305 failure message (oops).
4308 - Clients now use the bandwidth values in the consensus, rather than
4309 the bandwidth values in each relay descriptor. This approach opens
4310 the door to more accurate bandwidth estimates once the directory
4311 authorities start doing active measurements. Implements more of
4315 - When Tor clients restart after 1-5 days, they discard all their
4316 cached descriptors as too old, but they still use the cached
4317 consensus document. This approach is good for robustness, but
4318 bad for performance: since they don't know any bandwidths, they
4319 end up choosing at random rather than weighting their choice by
4320 speed. Fixed by the above feature of putting bandwidths in the
4321 consensus. Bugfix on 0.2.0.x.
4322 - Directory authorities were neglecting to mark relays down in their
4323 internal histories if the relays fall off the routerlist without
4324 ever being found unreachable. So there were relays in the histories
4325 that haven't been seen for eight months, and are listed as being
4326 up for eight months. This wreaked havoc on the "median wfu"
4327 and "median mtbf" calculations, in turn making Guard and Stable
4328 flags very wrong, hurting network performance. Fixes bugs 696 and
4329 969. Bugfix on 0.2.0.6-alpha.
4332 - Serve the DirPortFrontPage page even when we have been approaching
4333 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
4334 - The control port would close the connection before flushing long
4335 replies, such as the network consensus, if a QUIT command was issued
4336 before the reply had completed. Now, the control port flushes all
4337 pending replies before closing the connection. Also fixed a spurious
4338 warning when a QUIT command is issued after a malformed or rejected
4339 AUTHENTICATE command, but before the connection was closed. Patch
4340 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
4341 - When we can't find an intro key for a v2 hidden service descriptor,
4342 fall back to the v0 hidden service descriptor and log a bug message.
4343 Workaround for bug 1024.
4344 - Fix a log message that did not respect the SafeLogging option.
4348 - If we're a relay and we change our IP address, be more verbose
4349 about the reason that made us change. Should help track down
4350 further bugs for relays on dynamic IP addresses.
4353 Changes in version 0.2.0.35 - 2009-06-24
4355 - Avoid crashing in the presence of certain malformed descriptors.
4356 Found by lark, and by automated fuzzing.
4357 - Fix an edge case where a malicious exit relay could convince a
4358 controller that the client's DNS question resolves to an internal IP
4359 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
4362 - Finally fix the bug where dynamic-IP relays disappear when their
4363 IP address changes: directory mirrors were mistakenly telling
4364 them their old address if they asked via begin_dir, so they
4365 never got an accurate answer about their new address, so they
4366 just vanished after a day. For belt-and-suspenders, relays that
4367 don't set Address in their config now avoid using begin_dir for
4368 all direct connections. Should fix bugs 827, 883, and 900.
4369 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
4370 that would occur on some exit nodes when DNS failures and timeouts
4371 occurred in certain patterns. Fix for bug 957.
4374 - When starting with a cache over a few days old, do not leak
4375 memory for the obsolete router descriptors in it. Bugfix on
4376 0.2.0.33; fixes bug 672.
4377 - Hidden service clients didn't use a cached service descriptor that
4378 was older than 15 minutes, but wouldn't fetch a new one either,
4379 because there was already one in the cache. Now, fetch a v2
4380 descriptor unless the same descriptor was added to the cache within
4381 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
4384 Changes in version 0.2.1.16-rc - 2009-06-20
4385 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
4386 a bunch of minor bugs.
4389 - Fix an edge case where a malicious exit relay could convince a
4390 controller that the client's DNS question resolves to an internal IP
4391 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
4393 o Major performance improvements (on 0.2.0.x):
4394 - Disable and refactor some debugging checks that forced a linear scan
4395 over the whole server-side DNS cache. These accounted for over 50%
4396 of CPU time on a relatively busy exit node's gprof profile. Found
4398 - Disable some debugging checks that appeared in exit node profile
4402 - Update to the "June 3 2009" ip-to-country file.
4403 - Do not have tor-resolve automatically refuse all .onion addresses;
4404 if AutomapHostsOnResolve is set in your torrc, this will work fine.
4406 o Minor bugfixes (on 0.2.0.x):
4407 - Log correct error messages for DNS-related network errors on
4409 - Fix a race condition that could cause crashes or memory corruption
4410 when running as a server with a controller listening for log
4412 - Avoid crashing when we have a policy specified in a DirPolicy or
4413 SocksPolicy or ReachableAddresses option with ports set on it,
4414 and we re-load the policy. May fix bug 996.
4415 - Hidden service clients didn't use a cached service descriptor that
4416 was older than 15 minutes, but wouldn't fetch a new one either,
4417 because there was already one in the cache. Now, fetch a v2
4418 descriptor unless the same descriptor was added to the cache within
4419 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
4421 o Minor bugfixes (on 0.2.1.x):
4422 - Don't warn users about low port and hibernation mix when they
4423 provide a *ListenAddress directive to fix that. Bugfix on
4425 - When switching back and forth between bridge mode, do not start
4426 gathering GeoIP data until two hours have passed.
4427 - Do not complain that the user has requested an excluded node as
4428 an exit when the node is not really an exit. This could happen
4429 because the circuit was for testing, or an introduction point.
4433 Changes in version 0.2.1.15-rc - 2009-05-25
4434 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
4435 series. It fixes a major bug on fast exit relays, as well as a variety
4438 o Major bugfixes (on 0.2.0.x):
4439 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
4440 that would occur on some exit nodes when DNS failures and timeouts
4441 occurred in certain patterns. Fix for bug 957.
4443 o Minor bugfixes (on 0.2.0.x):
4444 - Actually return -1 in the error case for read_bandwidth_usage().
4445 Harmless bug, since we currently don't care about the return value
4446 anywhere. Bugfix on 0.2.0.9-alpha.
4447 - Provide a more useful log message if bug 977 (related to buffer
4448 freelists) ever reappears, and do not crash right away.
4449 - Fix an assertion failure on 64-bit platforms when we allocated
4450 memory right up to the end of a memarea, then realigned the memory
4451 one step beyond the end. Fixes a possible cause of bug 930.
4452 - Protect the count of open sockets with a mutex, so we can't
4453 corrupt it when two threads are closing or opening sockets at once.
4454 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
4455 - Don't allow a bridge to publish its router descriptor to a
4456 non-bridge directory authority. Fixes part of bug 932.
4457 - When we change to or from being a bridge, reset our counts of
4458 client usage by country. Fixes bug 932.
4459 - Fix a bug that made stream bandwidth get misreported to the
4461 - Stop using malloc_usable_size() to use more area than we had
4462 actually allocated: it was safe, but made valgrind really unhappy.
4463 - Fix a memory leak when v3 directory authorities load their keys
4464 and cert from disk. Bugfix on 0.2.0.1-alpha.
4466 o Minor bugfixes (on 0.2.1.x):
4467 - Fix use of freed memory when deciding to mark a non-addable
4468 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
4471 Changes in version 0.2.1.14-rc - 2009-04-12
4472 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
4473 series. It begins fixing some major performance problems, and also
4474 finally addresses the bug that was causing relays on dynamic IP
4475 addresses to fall out of the directory.
4478 - Clients replace entry guards that were chosen more than a few months
4479 ago. This change should significantly improve client performance,
4480 especially once more people upgrade, since relays that have been
4481 a guard for a long time are currently overloaded.
4483 o Major bugfixes (on 0.2.0):
4484 - Finally fix the bug where dynamic-IP relays disappear when their
4485 IP address changes: directory mirrors were mistakenly telling
4486 them their old address if they asked via begin_dir, so they
4487 never got an accurate answer about their new address, so they
4488 just vanished after a day. For belt-and-suspenders, relays that
4489 don't set Address in their config now avoid using begin_dir for
4490 all direct connections. Should fix bugs 827, 883, and 900.
4491 - Relays were falling out of the networkstatus consensus for
4492 part of a day if they changed their local config but the
4493 authorities discarded their new descriptor as "not sufficiently
4494 different". Now directory authorities accept a descriptor as changed
4495 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
4497 - Avoid crashing in the presence of certain malformed descriptors.
4498 Found by lark, and by automated fuzzing.
4501 - When generating circuit events with verbose nicknames for
4502 controllers, try harder to look up nicknames for routers on a
4503 circuit. (Previously, we would look in the router descriptors we had
4504 for nicknames, but not in the consensus.) Partial fix for bug 941.
4505 - If the bridge config line doesn't specify a port, assume 443.
4506 This makes bridge lines a bit smaller and easier for users to
4508 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
4509 bytes (aka 20KB/s), to match our documentation. Also update
4510 directory authorities so they always assign the Fast flag to relays
4511 with 20KB/s of capacity. Now people running relays won't suddenly
4512 find themselves not seeing any use, if the network gets faster
4514 - Update to the "April 3 2009" ip-to-country file.
4517 - Avoid trying to print raw memory to the logs when we decide to
4518 give up on downloading a given relay descriptor. Bugfix on
4520 - In tor-resolve, when the Tor client to use is specified by
4521 <hostname>:<port>, actually use the specified port rather than
4522 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
4523 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
4524 - When starting with a cache over a few days old, do not leak
4525 memory for the obsolete router descriptors in it. Bugfix on
4527 - Avoid double-free on list of successfully uploaded hidden
4528 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
4529 - Change memarea_strndup() implementation to work even when
4530 duplicating a string at the end of a page. This bug was
4531 harmless for now, but could have meant crashes later. Fix by
4532 lark. Bugfix on 0.2.1.1-alpha.
4533 - Limit uploaded directory documents to be 16M rather than 500K.
4534 The directory authorities were refusing v3 consensus votes from
4535 other authorities, since the votes are now 504K. Fixes bug 959;
4536 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
4537 - Directory authorities should never send a 503 "busy" response to
4538 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
4542 Changes in version 0.2.1.13-alpha - 2009-03-09
4543 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
4544 cleanups. We're finally getting close to a release candidate.
4547 - Correctly update the list of which countries we exclude as
4548 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
4549 lark. Bugfix on 0.2.1.6-alpha.
4551 o Minor bugfixes (on 0.2.0.x and earlier):
4552 - Automatically detect MacOSX versions earlier than 10.4.0, and
4553 disable kqueue from inside Tor when running with these versions.
4554 We previously did this from the startup script, but that was no
4555 help to people who didn't use the startup script. Resolves bug 863.
4556 - When we had picked an exit node for a connection, but marked it as
4557 "optional", and it turned out we had no onion key for the exit,
4558 stop wanting that exit and try again. This situation may not
4559 be possible now, but will probably become feasible with proposal
4560 158. Spotted by rovv. Fixes another case of bug 752.
4561 - Clients no longer cache certificates for authorities they do not
4562 recognize. Bugfix on 0.2.0.9-alpha.
4563 - When we can't transmit a DNS request due to a network error, retry
4564 it after a while, and eventually transmit a failing response to
4565 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
4566 - If the controller claimed responsibility for a stream, but that
4567 stream never finished making its connection, it would live
4568 forever in circuit_wait state. Now we close it after SocksTimeout
4569 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
4570 - Drop begin cells to a hidden service if they come from the middle
4571 of a circuit. Patch from lark.
4572 - When we erroneously receive two EXTEND cells for the same circuit
4573 ID on the same connection, drop the second. Patch from lark.
4574 - Fix a crash that occurs on exit nodes when a nameserver request
4575 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
4576 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
4578 - Do not assume that a stack-allocated character array will be
4579 64-bit aligned on platforms that demand that uint64_t access is
4580 aligned. Possible fix for bug 604.
4581 - Parse dates and IPv4 addresses in a locale- and libc-independent
4582 manner, to avoid platform-dependent behavior on malformed input.
4583 - Build correctly when configured to build outside the main source
4584 path. Patch from Michael Gold.
4585 - We were already rejecting relay begin cells with destination port
4586 of 0. Now also reject extend cells with destination port or address
4587 of 0. Suggested by lark.
4589 o Minor bugfixes (on 0.2.1.x):
4590 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
4591 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
4592 - If we're an exit node, scrub the IP address to which we are exiting
4593 in the logs. Bugfix on 0.2.1.8-alpha.
4596 - On Linux, use the prctl call to re-enable core dumps when the user
4598 - New controller event NEWCONSENSUS that lists the networkstatus
4599 lines for every recommended relay. Now controllers like Torflow
4600 can keep up-to-date on which relays they should be using.
4601 - Update to the "February 26 2009" ip-to-country file.
4604 Changes in version 0.2.0.34 - 2009-02-08
4605 Tor 0.2.0.34 features several more security-related fixes. You should
4606 upgrade, especially if you run an exit relay (remote crash) or a
4607 directory authority (remote infinite loop), or you're on an older
4608 (pre-XP) or not-recently-patched Windows (remote exploit).
4610 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
4611 have many known flaws, and nobody should be using them. You should
4612 upgrade. If you're using a Linux or BSD and its packages are obsolete,
4613 stop using those packages and upgrade anyway.
4616 - Fix an infinite-loop bug on handling corrupt votes under certain
4617 circumstances. Bugfix on 0.2.0.8-alpha.
4618 - Fix a temporary DoS vulnerability that could be performed by
4619 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
4620 - Avoid a potential crash on exit nodes when processing malformed
4621 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
4622 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
4623 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
4626 - Fix compilation on systems where time_t is a 64-bit integer.
4627 Patch from Matthias Drochner.
4628 - Don't consider expiring already-closed client connections. Fixes
4629 bug 893. Bugfix on 0.0.2pre20.
4632 Changes in version 0.2.1.12-alpha - 2009-02-08
4633 Tor 0.2.1.12-alpha features several more security-related fixes. You
4634 should upgrade, especially if you run an exit relay (remote crash) or
4635 a directory authority (remote infinite loop), or you're on an older
4636 (pre-XP) or not-recently-patched Windows (remote exploit). It also
4637 includes a big pile of minor bugfixes and cleanups.
4640 - Fix an infinite-loop bug on handling corrupt votes under certain
4641 circumstances. Bugfix on 0.2.0.8-alpha.
4642 - Fix a temporary DoS vulnerability that could be performed by
4643 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
4644 - Avoid a potential crash on exit nodes when processing malformed
4645 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
4648 - Let controllers actually ask for the "clients_seen" event for
4649 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
4650 reported by Matt Edman.
4651 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
4653 - Fix a bug in address parsing that was preventing bridges or hidden
4654 service targets from being at IPv6 addresses.
4655 - Solve a bug that kept hardware crypto acceleration from getting
4656 enabled when accounting was turned on. Fixes bug 907. Bugfix on
4658 - Remove a bash-ism from configure.in to build properly on non-Linux
4659 platforms. Bugfix on 0.2.1.1-alpha.
4660 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
4661 headers. Bugfix on 0.2.0.10-alpha.
4662 - Don't consider expiring already-closed client connections. Fixes
4663 bug 893. Bugfix on 0.0.2pre20.
4664 - Fix another interesting corner-case of bug 891 spotted by rovv:
4665 Previously, if two hosts had different amounts of clock drift, and
4666 one of them created a new connection with just the wrong timing,
4667 the other might decide to deprecate the new connection erroneously.
4668 Bugfix on 0.1.1.13-alpha.
4669 - Resolve a very rare crash bug that could occur when the user forced
4670 a nameserver reconfiguration during the middle of a nameserver
4671 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
4672 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
4673 Bugfix on 0.2.1.7-alpha.
4674 - If we're using bridges and our network goes away, be more willing
4675 to forgive our bridges and try again when we get an application
4676 request. Bugfix on 0.2.0.x.
4679 - Support platforms where time_t is 64 bits long. (Congratulations,
4680 NetBSD!) Patch from Matthias Drochner.
4681 - Add a 'getinfo status/clients-seen' controller command, in case
4682 controllers want to hear clients_seen events but connect late.
4685 - Disable GCC's strict alias optimization by default, to avoid the
4686 likelihood of its introducing subtle bugs whenever our code violates
4687 the letter of C99's alias rules.
4690 Changes in version 0.2.0.33 - 2009-01-21
4691 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
4692 useful to users. It also finally fixes a bug where a relay or client
4693 that's been off for many days would take a long time to bootstrap.
4695 This update also fixes an important security-related bug reported by
4696 Ilja van Sprundel. You should upgrade. (We'll send out more details
4697 about the bug once people have had some time to upgrade.)
4700 - Fix a heap-corruption bug that may be remotely triggerable on
4701 some platforms. Reported by Ilja van Sprundel.
4704 - When a stream at an exit relay is in state "resolving" or
4705 "connecting" and it receives an "end" relay cell, the exit relay
4706 would silently ignore the end cell and not close the stream. If
4707 the client never closes the circuit, then the exit relay never
4708 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
4710 - When sending CREATED cells back for a given circuit, use a 64-bit
4711 connection ID to find the right connection, rather than an addr:port
4712 combination. Now that we can have multiple OR connections between
4713 the same ORs, it is no longer possible to use addr:port to uniquely
4714 identify a connection.
4715 - Bridge relays that had DirPort set to 0 would stop fetching
4716 descriptors shortly after startup, and then briefly resume
4717 after a new bandwidth test and/or after publishing a new bridge
4718 descriptor. Bridge users that try to bootstrap from them would
4719 get a recent networkstatus but would get descriptors from up to
4720 18 hours earlier, meaning most of the descriptors were obsolete
4721 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
4722 - Prevent bridge relays from serving their 'extrainfo' document
4723 to anybody who asks, now that extrainfo docs include potentially
4724 sensitive aggregated client geoip summaries. Bugfix on
4726 - If the cached networkstatus consensus is more than five days old,
4727 discard it rather than trying to use it. In theory it could be
4728 useful because it lists alternate directory mirrors, but in practice
4729 it just means we spend many minutes trying directory mirrors that
4730 are long gone from the network. Also discard router descriptors as
4731 we load them if they are more than five days old, since the onion
4732 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
4735 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
4736 could make gcc generate non-functional binary search code. Bugfix
4738 - Build correctly on platforms without socklen_t.
4739 - Compile without warnings on solaris.
4740 - Avoid potential crash on internal error during signature collection.
4741 Fixes bug 864. Patch from rovv.
4742 - Correct handling of possible malformed authority signing key
4743 certificates with internal signature types. Fixes bug 880.
4744 Bugfix on 0.2.0.3-alpha.
4745 - Fix a hard-to-trigger resource leak when logging credential status.
4747 - When we can't initialize DNS because the network is down, do not
4748 automatically stop Tor from starting. Instead, we retry failed
4749 dns_init() every 10 minutes, and change the exit policy to reject
4750 *:* until one succeeds. Fixes bug 691.
4751 - Use 64 bits instead of 32 bits for connection identifiers used with
4752 the controller protocol, to greatly reduce risk of identifier reuse.
4753 - When we're choosing an exit node for a circuit, and we have
4754 no pending streams, choose a good general exit rather than one that
4755 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
4756 - Fix another case of assuming, when a specific exit is requested,
4757 that we know more than the user about what hosts it allows.
4758 Fixes one case of bug 752. Patch from rovv.
4759 - Clip the MaxCircuitDirtiness config option to a minimum of 10
4760 seconds. Warn the user if lower values are given in the
4761 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
4762 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
4763 user if lower values are given in the configuration. Bugfix on
4764 0.1.1.17-rc. Patch by Sebastian.
4765 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
4766 the cache because we already had a v0 descriptor with the same ID.
4767 Bugfix on 0.2.0.18-alpha.
4768 - Fix a race condition when freeing keys shared between main thread
4769 and CPU workers that could result in a memory leak. Bugfix on
4770 0.1.0.1-rc. Fixes bug 889.
4771 - Send a valid END cell back when a client tries to connect to a
4772 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
4773 840. Patch from rovv.
4774 - Check which hops rendezvous stream cells are associated with to
4775 prevent possible guess-the-streamid injection attacks from
4776 intermediate hops. Fixes another case of bug 446. Based on patch
4778 - If a broken client asks a non-exit router to connect somewhere,
4779 do not even do the DNS lookup before rejecting the connection.
4780 Fixes another case of bug 619. Patch from rovv.
4781 - When a relay gets a create cell it can't decrypt (e.g. because it's
4782 using the wrong onion key), we were dropping it and letting the
4783 client time out. Now actually answer with a destroy cell. Fixes
4784 bug 904. Bugfix on 0.0.2pre8.
4786 o Minor bugfixes (hidden services):
4787 - Do not throw away existing introduction points on SIGHUP. Bugfix on
4788 0.0.6pre1. Patch by Karsten. Fixes bug 874.
4791 - Report the case where all signatures in a detached set are rejected
4792 differently than the case where there is an error handling the
4794 - When we realize that another process has modified our cached
4795 descriptors, print out a more useful error message rather than
4796 triggering an assertion. Fixes bug 885. Patch from Karsten.
4797 - Implement the 0x20 hack to better resist DNS poisoning: set the
4798 case on outgoing DNS requests randomly, and reject responses that do
4799 not match the case correctly. This logic can be disabled with the
4800 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
4801 of servers that do not reliably preserve case in replies. See
4802 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
4804 - Check DNS replies for more matching fields to better resist DNS
4806 - Never use OpenSSL compression: it wastes RAM and CPU trying to
4807 compress cells, which are basically all encrypted, compressed, or
4811 Changes in version 0.2.1.11-alpha - 2009-01-20
4812 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
4813 week it will take a long time to bootstrap again" bug. It also fixes
4814 an important security-related bug reported by Ilja van Sprundel. You
4815 should upgrade. (We'll send out more details about the bug once people
4816 have had some time to upgrade.)
4819 - Fix a heap-corruption bug that may be remotely triggerable on
4820 some platforms. Reported by Ilja van Sprundel.
4823 - Discard router descriptors as we load them if they are more than
4824 five days old. Otherwise if Tor is off for a long time and then
4825 starts with cached descriptors, it will try to use the onion
4826 keys in those obsolete descriptors when building circuits. Bugfix
4827 on 0.2.0.x. Fixes bug 887.
4830 - Try to make sure that the version of Libevent we're running with
4831 is binary-compatible with the one we built with. May address bug
4833 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
4834 for bug 905. Bugfix on 0.2.1.7-alpha.
4835 - Add a new --enable-local-appdata configuration switch to change
4836 the default location of the datadir on win32 from APPDATA to
4837 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
4838 entirely. Patch from coderman.
4841 - Make outbound DNS packets respect the OutboundBindAddress setting.
4842 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
4843 - When our circuit fails at the first hop (e.g. we get a destroy
4844 cell back), avoid using that OR connection anymore, and also
4845 tell all the one-hop directory requests waiting for it that they
4846 should fail. Bugfix on 0.2.1.3-alpha.
4847 - In the torify(1) manpage, mention that tsocks will leak your
4851 Changes in version 0.2.1.10-alpha - 2009-01-06
4852 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
4853 would make the bridge relay not so useful if it had DirPort set to 0,
4854 and one that could let an attacker learn a little bit of information
4855 about the bridge's users), and a bug that would cause your Tor relay
4856 to ignore a circuit create request it can't decrypt (rather than reply
4857 with an error). It also fixes a wide variety of other bugs.
4860 - If the cached networkstatus consensus is more than five days old,
4861 discard it rather than trying to use it. In theory it could
4862 be useful because it lists alternate directory mirrors, but in
4863 practice it just means we spend many minutes trying directory
4864 mirrors that are long gone from the network. Helps bug 887 a bit;
4866 - Bridge relays that had DirPort set to 0 would stop fetching
4867 descriptors shortly after startup, and then briefly resume
4868 after a new bandwidth test and/or after publishing a new bridge
4869 descriptor. Bridge users that try to bootstrap from them would
4870 get a recent networkstatus but would get descriptors from up to
4871 18 hours earlier, meaning most of the descriptors were obsolete
4872 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
4873 - Prevent bridge relays from serving their 'extrainfo' document
4874 to anybody who asks, now that extrainfo docs include potentially
4875 sensitive aggregated client geoip summaries. Bugfix on
4879 - New controller event "clients_seen" to report a geoip-based summary
4880 of which countries we've seen clients from recently. Now controllers
4881 like Vidalia can show bridge operators that they're actually making
4883 - Build correctly against versions of OpenSSL 0.9.8 or later built
4884 without support for deprecated functions.
4885 - Update to the "December 19 2008" ip-to-country file.
4887 o Minor bugfixes (on 0.2.0.x):
4888 - Authorities now vote for the Stable flag for any router whose
4889 weighted MTBF is at least 5 days, regardless of the mean MTBF.
4890 - Do not remove routers as too old if we do not have any consensus
4891 document. Bugfix on 0.2.0.7-alpha.
4892 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
4893 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
4894 - When an exit relay resolves a stream address to a local IP address,
4895 do not just keep retrying that same exit relay over and
4896 over. Instead, just close the stream. Addresses bug 872. Bugfix
4897 on 0.2.0.32. Patch from rovv.
4898 - If a hidden service sends us an END cell, do not consider
4899 retrying the connection; just close it. Patch from rovv.
4900 - When we made bridge authorities stop serving bridge descriptors over
4901 unencrypted links, we also broke DirPort reachability testing for
4902 bridges. So bridges with a non-zero DirPort were printing spurious
4903 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
4904 - When a relay gets a create cell it can't decrypt (e.g. because it's
4905 using the wrong onion key), we were dropping it and letting the
4906 client time out. Now actually answer with a destroy cell. Fixes
4907 bug 904. Bugfix on 0.0.2pre8.
4908 - Squeeze 2-5% out of client performance (according to oprofile) by
4909 improving the implementation of some policy-manipulation functions.
4911 o Minor bugfixes (on 0.2.1.x):
4912 - Make get_interface_address() function work properly again; stop
4913 guessing the wrong parts of our address as our address.
4914 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
4915 send on that circuit. Otherwise we might violate the proposal-110
4916 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
4918 - When we're sending non-EXTEND cells to the first hop in a circuit,
4919 for example to use an encrypted directory connection, we don't need
4920 to use RELAY_EARLY cells: the first hop knows what kind of cell
4921 it is, and nobody else can even see the cell type. Conserving
4922 RELAY_EARLY cells makes it easier to cannibalize circuits like
4924 - Stop logging nameserver addresses in reverse order.
4925 - If we are retrying a directory download slowly over and over, do
4926 not automatically give up after the 254th failure. Bugfix on
4928 - Resume reporting accurate "stream end" reasons to the local control
4929 port. They were lost in the changes for Proposal 148. Bugfix on
4932 o Deprecated and removed features:
4933 - The old "tor --version --version" command, which would print out
4934 the subversion "Id" of most of the source files, is now removed. It
4935 turned out to be less useful than we'd expected, and harder to
4938 o Code simplifications and refactoring:
4939 - Change our header file guard macros to be less likely to conflict
4940 with system headers. Adam Langley noticed that we were conflicting
4941 with log.h on Android.
4942 - Tool-assisted documentation cleanup. Nearly every function or
4943 static variable in Tor should have its own documentation now.
4946 Changes in version 0.2.1.9-alpha - 2008-12-25
4947 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
4949 o New directory authorities:
4950 - gabelmoo (the authority run by Karsten Loesing) now has a new
4954 - Never use a connection with a mismatched address to extend a
4955 circuit, unless that connection is canonical. A canonical
4956 connection is one whose address is authenticated by the router's
4957 identity key, either in a NETINFO cell or in a router descriptor.
4958 - Avoid a possible memory corruption bug when receiving hidden service
4959 descriptors. Bugfix on 0.2.1.6-alpha.
4962 - Fix a logic error that would automatically reject all but the first
4963 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
4964 part of bug 813/868. Bug spotted by coderman.
4965 - When a stream at an exit relay is in state "resolving" or
4966 "connecting" and it receives an "end" relay cell, the exit relay
4967 would silently ignore the end cell and not close the stream. If
4968 the client never closes the circuit, then the exit relay never
4969 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
4971 - When we can't initialize DNS because the network is down, do not
4972 automatically stop Tor from starting. Instead, retry failed
4973 dns_init() every 10 minutes, and change the exit policy to reject
4974 *:* until one succeeds. Fixes bug 691.
4977 - Give a better error message when an overzealous init script says
4978 "sudo -u username tor --user username". Makes Bug 882 easier for
4980 - When a directory authority gives us a new guess for our IP address,
4981 log which authority we used. Hopefully this will help us debug
4982 the recent complaints about bad IP address guesses.
4983 - Detect svn revision properly when we're using git-svn.
4984 - Try not to open more than one descriptor-downloading connection
4985 to an authority at once. This should reduce load on directory
4986 authorities. Fixes bug 366.
4987 - Add cross-certification to newly generated certificates, so that
4988 a signing key is enough information to look up a certificate.
4989 Partial implementation of proposal 157.
4990 - Start serving certificates by <identity digest, signing key digest>
4991 pairs. Partial implementation of proposal 157.
4992 - Clients now never report any stream end reason except 'MISC'.
4993 Implements proposal 148.
4994 - On platforms with a maximum syslog string length, truncate syslog
4995 messages to that length ourselves, rather than relying on the
4996 system to do it for us.
4997 - Optimize out calls to time(NULL) that occur for every IO operation,
4998 or for every cell. On systems where time() is a slow syscall,
4999 this fix will be slightly helpful.
5000 - Exit servers can now answer resolve requests for ip6.arpa addresses.
5001 - When we download a descriptor that we then immediately (as
5002 a directory authority) reject, do not retry downloading it right
5003 away. Should save some bandwidth on authorities. Fix for bug
5004 888. Patch by Sebastian Hahn.
5005 - When a download gets us zero good descriptors, do not notify
5006 Tor that new directory information has arrived.
5007 - Avoid some nasty corner cases in the logic for marking connections
5008 as too old or obsolete or noncanonical for circuits. Partial
5011 o Minor features (controller):
5012 - New CONSENSUS_ARRIVED event to note when a new consensus has
5013 been fetched and validated.
5014 - When we realize that another process has modified our cached
5015 descriptors file, print out a more useful error message rather
5016 than triggering an assertion. Fixes bug 885. Patch from Karsten.
5017 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
5018 controllers to prevent SIGHUP from reloading the
5019 configuration. Fixes bug 856.
5022 - Resume using the correct "REASON=" stream when telling the
5023 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
5024 - When a canonical connection appears later in our internal list
5025 than a noncanonical one for a given OR ID, always use the
5026 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
5028 - Clip the MaxCircuitDirtiness config option to a minimum of 10
5029 seconds. Warn the user if lower values are given in the
5030 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
5031 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
5032 user if lower values are given in the configuration. Bugfix on
5033 0.1.1.17-rc. Patch by Sebastian.
5034 - Fix a race condition when freeing keys shared between main thread
5035 and CPU workers that could result in a memory leak. Bugfix on
5036 0.1.0.1-rc. Fixes bug 889.
5038 o Minor bugfixes (hidden services):
5039 - Do not throw away existing introduction points on SIGHUP (bugfix on
5040 0.0.6pre1); also, do not stall hidden services because we're
5041 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
5042 by John Brooks. Patch by Karsten. Fixes bug 874.
5043 - Fix a memory leak when we decline to add a v2 rendezvous
5044 descriptor to the cache because we already had a v0 descriptor
5045 with the same ID. Bugfix on 0.2.0.18-alpha.
5047 o Deprecated and removed features:
5048 - RedirectExits has been removed. It was deprecated since
5050 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
5051 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
5052 - Cell pools are now always enabled; --disable-cell-pools is ignored.
5054 o Code simplifications and refactoring:
5055 - Rename the confusing or_is_obsolete field to the more appropriate
5056 is_bad_for_new_circs, and move it to or_connection_t where it
5058 - Move edge-only flags from connection_t to edge_connection_t: not
5059 only is this better coding, but on machines of plausible alignment,
5060 it should save 4-8 bytes per connection_t. "Every little bit helps."
5061 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
5062 for consistency; keep old option working for backward compatibility.
5063 - Simplify the code for finding connections to use for a circuit.
5066 Changes in version 0.2.1.8-alpha - 2008-12-08
5067 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
5068 builds better on unusual platforms like Solaris and old OS X, and
5069 fixes a variety of other issues.
5072 - New DirPortFrontPage option that takes an html file and publishes
5073 it as "/" on the DirPort. Now relay operators can provide a
5074 disclaimer without needing to set up a separate webserver. There's
5075 a sample disclaimer in contrib/tor-exit-notice.html.
5078 - When the client is choosing entry guards, now it selects at most
5079 one guard from a given relay family. Otherwise we could end up with
5080 all of our entry points into the network run by the same operator.
5081 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
5084 - Fix a DOS opportunity during the voting signature collection process
5085 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
5086 - Fix a possible segfault when establishing an exit connection. Bugfix
5090 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
5092 - Made Tor a little less aggressive about deleting expired
5093 certificates. Partial fix for bug 854.
5094 - Stop doing unaligned memory access that generated bus errors on
5095 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
5096 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
5097 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
5098 - Make USR2 log-level switch take effect immediately. Bugfix on
5100 - If one win32 nameserver fails to get added, continue adding the
5101 rest, and don't automatically fail.
5102 - Use fcntl() for locking when flock() is not available. Should fix
5103 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
5104 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
5105 could make gcc generate non-functional binary search code. Bugfix
5107 - Build correctly on platforms without socklen_t.
5108 - Avoid potential crash on internal error during signature collection.
5109 Fixes bug 864. Patch from rovv.
5110 - Do not use C's stdio library for writing to log files. This will
5111 improve logging performance by a minute amount, and will stop
5112 leaking fds when our disk is full. Fixes bug 861.
5113 - Stop erroneous use of O_APPEND in cases where we did not in fact
5114 want to re-seek to the end of a file before every last write().
5115 - Correct handling of possible malformed authority signing key
5116 certificates with internal signature types. Fixes bug 880. Bugfix
5118 - Fix a hard-to-trigger resource leak when logging credential status.
5122 - Directory mirrors no longer fetch the v1 directory or
5123 running-routers files. They are obsolete, and nobody asks for them
5124 anymore. This is the first step to making v1 authorities obsolete.
5126 o Minor features (controller):
5127 - Return circuit purposes in response to GETINFO circuit-status. Fixes
5131 Changes in version 0.2.0.32 - 2008-11-20
5132 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
5133 packages (and maybe other packages) noticed by Theo de Raadt, fixes
5134 a smaller security flaw that might allow an attacker to access local
5135 services, further improves hidden service performance, and fixes a
5136 variety of other issues.
5139 - The "User" and "Group" config options did not clear the
5140 supplementary group entries for the Tor process. The "User" option
5141 is now more robust, and we now set the groups to the specified
5142 user's primary group. The "Group" option is now ignored. For more
5143 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
5144 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
5145 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
5146 - The "ClientDNSRejectInternalAddresses" config option wasn't being
5147 consistently obeyed: if an exit relay refuses a stream because its
5148 exit policy doesn't allow it, we would remember what IP address
5149 the relay said the destination address resolves to, even if it's
5150 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
5153 - Fix a DOS opportunity during the voting signature collection process
5154 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
5156 o Major bugfixes (hidden services):
5157 - When fetching v0 and v2 rendezvous service descriptors in parallel,
5158 we were failing the whole hidden service request when the v0
5159 descriptor fetch fails, even if the v2 fetch is still pending and
5160 might succeed. Similarly, if the last v2 fetch fails, we were
5161 failing the whole hidden service request even if a v0 fetch is
5162 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
5163 - When extending a circuit to a hidden service directory to upload a
5164 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
5165 requests failed, because the router descriptor has not been
5166 downloaded yet. In these cases, do not attempt to upload the
5167 rendezvous descriptor, but wait until the router descriptor is
5168 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
5169 descriptor from a hidden service directory for which the router
5170 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
5174 - Fix several infrequent memory leaks spotted by Coverity.
5175 - When testing for libevent functions, set the LDFLAGS variable
5176 correctly. Found by Riastradh.
5177 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
5178 bootstrapping with tunneled directory connections. Bugfix on
5179 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
5180 - When asked to connect to A.B.exit:80, if we don't know the IP for A
5181 and we know that server B rejects most-but-not all connections to
5182 port 80, we would previously reject the connection. Now, we assume
5183 the user knows what they were asking for. Fixes bug 752. Bugfix
5184 on 0.0.9rc5. Diagnosed by BarkerJr.
5185 - If we overrun our per-second write limits a little, count this as
5186 having used up our write allocation for the second, and choke
5187 outgoing directory writes. Previously, we had only counted this when
5188 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
5189 Bugfix on 0.2.0.x (??).
5190 - Remove the old v2 directory authority 'lefkada' from the default
5191 list. It has been gone for many months.
5192 - Stop doing unaligned memory access that generated bus errors on
5193 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
5194 - Make USR2 log-level switch take effect immediately. Bugfix on
5197 o Minor bugfixes (controller):
5198 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
5199 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
5202 Changes in version 0.2.1.7-alpha - 2008-11-08
5203 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
5204 packages (and maybe other packages) noticed by Theo de Raadt, fixes
5205 a smaller security flaw that might allow an attacker to access local
5206 services, adds better defense against DNS poisoning attacks on exit
5207 relays, further improves hidden service performance, and fixes a
5208 variety of other issues.
5211 - The "ClientDNSRejectInternalAddresses" config option wasn't being
5212 consistently obeyed: if an exit relay refuses a stream because its
5213 exit policy doesn't allow it, we would remember what IP address
5214 the relay said the destination address resolves to, even if it's
5215 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
5216 - The "User" and "Group" config options did not clear the
5217 supplementary group entries for the Tor process. The "User" option
5218 is now more robust, and we now set the groups to the specified
5219 user's primary group. The "Group" option is now ignored. For more
5220 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
5221 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
5222 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
5223 - Do not use or believe expired v3 authority certificates. Patch
5224 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
5227 - Now NodeFamily and MyFamily config options allow spaces in
5228 identity fingerprints, so it's easier to paste them in.
5229 Suggested by Lucky Green.
5230 - Implement the 0x20 hack to better resist DNS poisoning: set the
5231 case on outgoing DNS requests randomly, and reject responses that do
5232 not match the case correctly. This logic can be disabled with the
5233 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
5234 of servers that do not reliably preserve case in replies. See
5235 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
5237 - Preserve case in replies to DNSPort requests in order to support
5238 the 0x20 hack for resisting DNS poisoning attacks.
5240 o Hidden service performance improvements:
5241 - When the client launches an introduction circuit, retry with a
5242 new circuit after 30 seconds rather than 60 seconds.
5243 - Launch a second client-side introduction circuit in parallel
5244 after a delay of 15 seconds (based on work by Christian Wilms).
5245 - Hidden services start out building five intro circuits rather
5246 than three, and when the first three finish they publish a service
5247 descriptor using those. Now we publish our service descriptor much
5248 faster after restart.
5251 - Minor fix in the warning messages when you're having problems
5252 bootstrapping; also, be more forgiving of bootstrap problems when
5253 we're still making incremental progress on a given bootstrap phase.
5254 - When we're choosing an exit node for a circuit, and we have
5255 no pending streams, choose a good general exit rather than one that
5256 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
5257 - Send a valid END cell back when a client tries to connect to a
5258 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
5259 840. Patch from rovv.
5260 - If a broken client asks a non-exit router to connect somewhere,
5261 do not even do the DNS lookup before rejecting the connection.
5262 Fixes another case of bug 619. Patch from rovv.
5263 - Fix another case of assuming, when a specific exit is requested,
5264 that we know more than the user about what hosts it allows.
5265 Fixes another case of bug 752. Patch from rovv.
5266 - Check which hops rendezvous stream cells are associated with to
5267 prevent possible guess-the-streamid injection attacks from
5268 intermediate hops. Fixes another case of bug 446. Based on patch
5270 - Avoid using a negative right-shift when comparing 32-bit
5271 addresses. Possible fix for bug 845 and bug 811.
5272 - Make the assert_circuit_ok() function work correctly on circuits that
5273 have already been marked for close.
5274 - Fix read-off-the-end-of-string error in unit tests when decoding
5275 introduction points.
5276 - Fix uninitialized size field for memory area allocation: may improve
5277 memory performance during directory parsing.
5278 - Treat duplicate certificate fetches as failures, so that we do
5279 not try to re-fetch an expired certificate over and over and over.
5280 - Do not say we're fetching a certificate when we'll in fact skip it
5281 because of a pending download.
5284 Changes in version 0.2.1.6-alpha - 2008-09-30
5285 Tor 0.2.1.6-alpha further improves performance and robustness of
5286 hidden services, starts work on supporting per-country relay selection,
5287 and fixes a variety of smaller issues.
5290 - Implement proposal 121: make it possible to build hidden services
5291 that only certain clients are allowed to connect to. This is
5292 enforced at several points, so that unauthorized clients are unable
5293 to send INTRODUCE cells to the service, or even (depending on the
5294 type of authentication) to learn introduction points. This feature
5295 raises the bar for certain kinds of active attacks against hidden
5296 services. Code by Karsten Loesing.
5297 - Relays now store and serve v2 hidden service descriptors by default,
5298 i.e., the new default value for HidServDirectoryV2 is 1. This is
5299 the last step in proposal 114, which aims to make hidden service
5300 lookups more reliable.
5301 - Start work to allow node restrictions to include country codes. The
5302 syntax to exclude nodes in a country with country code XX is
5303 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
5304 refinement to decide what config options should take priority if
5305 you ask to both use a particular node and exclude it.
5306 - Allow ExitNodes list to include IP ranges and country codes, just
5307 like the Exclude*Nodes lists. Patch from Robert Hogan.
5310 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
5311 Tor to fail to start if you had it configured to use a bridge
5312 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
5313 - When extending a circuit to a hidden service directory to upload a
5314 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
5315 requests failed, because the router descriptor had not been
5316 downloaded yet. In these cases, we now wait until the router
5317 descriptor is downloaded, and then retry. Likewise, clients
5318 now skip over a hidden service directory if they don't yet have
5319 its router descriptor, rather than futilely requesting it and
5320 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
5322 - When fetching v0 and v2 rendezvous service descriptors in parallel,
5323 we were failing the whole hidden service request when the v0
5324 descriptor fetch fails, even if the v2 fetch is still pending and
5325 might succeed. Similarly, if the last v2 fetch fails, we were
5326 failing the whole hidden service request even if a v0 fetch is
5327 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
5328 - DNS replies need to have names matching their requests, but
5329 these names should be in the questions section, not necessarily
5330 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
5333 - Update to the "September 1 2008" ip-to-country file.
5334 - Allow ports 465 and 587 in the default exit policy again. We had
5335 rejected them in 0.1.0.15, because back in 2005 they were commonly
5336 misconfigured and ended up as spam targets. We hear they are better
5337 locked down these days.
5338 - Use a lockfile to make sure that two Tor processes are not
5339 simultaneously running with the same datadir.
5340 - Serve the latest v3 networkstatus consensus via the control
5341 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
5342 - Better logging about stability/reliability calculations on directory
5344 - Drop the requirement to have an open dir port for storing and
5345 serving v2 hidden service descriptors.
5346 - Directory authorities now serve a /tor/dbg-stability.txt URL to
5347 help debug WFU and MTBF calculations.
5348 - Implement most of Proposal 152: allow specialized servers to permit
5349 single-hop circuits, and clients to use those servers to build
5350 single-hop circuits when using a specialized controller. Patch
5351 from Josh Albrecht. Resolves feature request 768.
5352 - Add a -p option to tor-resolve for specifying the SOCKS port: some
5353 people find host:port too confusing.
5354 - Make TrackHostExit mappings expire a while after their last use, not
5355 after their creation. Patch from Robert Hogan.
5356 - Provide circuit purposes along with circuit events to the controller.
5359 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
5361 - Fixed some memory leaks -- some quite frequent, some almost
5362 impossible to trigger -- based on results from Coverity.
5363 - When testing for libevent functions, set the LDFLAGS variable
5364 correctly. Found by Riastradh.
5365 - Fix an assertion bug in parsing policy-related options; possible fix
5367 - Catch and report a few more bootstrapping failure cases when Tor
5368 fails to establish a TCP connection. Cleanup on 0.2.1.x.
5369 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
5370 bootstrapping with tunneled directory connections. Bugfix on
5371 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
5372 - When asked to connect to A.B.exit:80, if we don't know the IP for A
5373 and we know that server B rejects most-but-not all connections to
5374 port 80, we would previously reject the connection. Now, we assume
5375 the user knows what they were asking for. Fixes bug 752. Bugfix
5376 on 0.0.9rc5. Diagnosed by BarkerJr.
5377 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
5378 service directories if they have no advertised dir port. Bugfix
5380 - If we overrun our per-second write limits a little, count this as
5381 having used up our write allocation for the second, and choke
5382 outgoing directory writes. Previously, we had only counted this when
5383 we had met our limits precisely. Fixes bug 824. Patch by rovv.
5384 Bugfix on 0.2.0.x (??).
5385 - Avoid a "0 divided by 0" calculation when calculating router uptime
5386 at directory authorities. Bugfix on 0.2.0.8-alpha.
5387 - Make DNS resolved controller events into "CLOSED", not
5388 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
5390 - Fix a bug where an unreachable relay would establish enough
5391 reachability testing circuits to do a bandwidth test -- if
5392 we already have a connection to the middle hop of the testing
5393 circuit, then it could establish the last hop by using the existing
5394 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
5395 circuits no longer use entry guards in 0.2.1.3-alpha.
5396 - If we have correct permissions on $datadir, we complain to stdout
5397 and fail to start. But dangerous permissions on
5398 $datadir/cached-status/ would cause us to open a log and complain
5399 there. Now complain to stdout and fail to start in both cases. Fixes
5400 bug 820, reported by seeess.
5401 - Remove the old v2 directory authority 'lefkada' from the default
5402 list. It has been gone for many months.
5404 o Code simplifications and refactoring:
5405 - Revise the connection_new functions so that a more typesafe variant
5406 exists. This will work better with Coverity, and let us find any
5407 actual mistakes we're making here.
5408 - Refactor unit testing logic so that dmalloc can be used sensibly
5409 with unit tests to check for memory leaks.
5410 - Move all hidden-service related fields from connection and circuit
5411 structure to substructures: this way they won't eat so much memory.
5414 Changes in version 0.2.0.31 - 2008-09-03
5415 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
5416 a big bug we're seeing where in rare cases traffic from one Tor stream
5417 gets mixed into another stream, and fixes a variety of smaller issues.
5420 - Make sure that two circuits can never exist on the same connection
5421 with the same circuit ID, even if one is marked for close. This
5422 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
5423 - Relays now reject risky extend cells: if the extend cell includes
5424 a digest of all zeroes, or asks to extend back to the relay that
5425 sent the extend cell, tear down the circuit. Ideas suggested
5427 - If not enough of our entry guards are available so we add a new
5428 one, we might use the new one even if it overlapped with the
5429 current circuit's exit relay (or its family). Anonymity bugfix
5430 pointed out by rovv.
5433 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
5434 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
5435 - Correctly detect the presence of the linux/netfilter_ipv4.h header
5436 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
5437 - Pick size of default geoip filename string correctly on windows.
5438 Fixes bug 806. Bugfix on 0.2.0.30.
5439 - Make the autoconf script accept the obsolete --with-ssl-dir
5440 option as an alias for the actually-working --with-openssl-dir
5441 option. Fix the help documentation to recommend --with-openssl-dir.
5442 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
5443 - When using the TransPort option on OpenBSD, and using the User
5444 option to change UID and drop privileges, make sure to open
5445 /dev/pf before dropping privileges. Fixes bug 782. Patch from
5446 Christopher Davis. Bugfix on 0.1.2.1-alpha.
5447 - Try to attach connections immediately upon receiving a RENDEZVOUS2
5448 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
5449 on the client side when connecting to a hidden service. Bugfix
5450 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
5451 - When closing an application-side connection because its circuit is
5452 getting torn down, generate the stream event correctly. Bugfix on
5453 0.1.2.x. Anonymous patch.
5456 Changes in version 0.2.1.5-alpha - 2008-08-31
5457 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
5458 in a lot of the infrastructure for adding authorization to hidden
5459 services, lays the groundwork for having clients read their load
5460 balancing information out of the networkstatus consensus rather than
5461 the individual router descriptors, addresses two potential anonymity
5462 issues, and fixes a variety of smaller issues.
5465 - Convert many internal address representations to optionally hold
5467 - Generate and accept IPv6 addresses in many protocol elements.
5468 - Make resolver code handle nameservers located at ipv6 addresses.
5469 - Begin implementation of proposal 121 ("Client authorization for
5470 hidden services"): configure hidden services with client
5471 authorization, publish descriptors for them, and configure
5472 authorization data for hidden services at clients. The next
5473 step is to actually access hidden services that perform client
5475 - More progress toward proposal 141: Network status consensus
5476 documents and votes now contain bandwidth information for each
5477 router and a summary of that router's exit policy. Eventually this
5478 will be used by clients so that they do not have to download every
5479 known descriptor before building circuits.
5481 o Major bugfixes (on 0.2.0.x and before):
5482 - When sending CREATED cells back for a given circuit, use a 64-bit
5483 connection ID to find the right connection, rather than an addr:port
5484 combination. Now that we can have multiple OR connections between
5485 the same ORs, it is no longer possible to use addr:port to uniquely
5486 identify a connection.
5487 - Relays now reject risky extend cells: if the extend cell includes
5488 a digest of all zeroes, or asks to extend back to the relay that
5489 sent the extend cell, tear down the circuit. Ideas suggested
5491 - If not enough of our entry guards are available so we add a new
5492 one, we might use the new one even if it overlapped with the
5493 current circuit's exit relay (or its family). Anonymity bugfix
5494 pointed out by rovv.
5497 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
5498 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
5499 - When using the TransPort option on OpenBSD, and using the User
5500 option to change UID and drop privileges, make sure to open /dev/pf
5501 before dropping privileges. Fixes bug 782. Patch from Christopher
5502 Davis. Bugfix on 0.1.2.1-alpha.
5503 - Correctly detect the presence of the linux/netfilter_ipv4.h header
5504 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
5505 - Add a missing safe_str() call for a debug log message.
5506 - Use 64 bits instead of 32 bits for connection identifiers used with
5507 the controller protocol, to greatly reduce risk of identifier reuse.
5508 - Make the autoconf script accept the obsolete --with-ssl-dir
5509 option as an alias for the actually-working --with-openssl-dir
5510 option. Fix the help documentation to recommend --with-openssl-dir.
5511 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
5514 - Rate-limit too-many-sockets messages: when they happen, they happen
5515 a lot. Resolves bug 748.
5516 - Resist DNS poisoning a little better by making sure that names in
5517 answer sections match.
5518 - Print the SOCKS5 error message string as well as the error code
5519 when a tor-resolve request fails. Patch from Jacob.
5522 Changes in version 0.2.1.4-alpha - 2008-08-04
5523 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
5526 - The address part of exit policies was not correctly written
5527 to router descriptors. This generated router descriptors that failed
5528 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
5530 - Tor triggered a false assert when extending a circuit to a relay
5531 but we already have a connection open to that relay. Noticed by
5532 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
5535 - Fix a hidden service logging bug: in some edge cases, the router
5536 descriptor of a previously picked introduction point becomes
5537 obsolete and we need to give up on it rather than continually
5538 complaining that it has become obsolete. Observed by xiando. Bugfix
5542 - Take out the TestVia config option, since it was a workaround for
5543 a bug that was fixed in Tor 0.1.1.21.
5546 Changes in version 0.2.1.3-alpha - 2008-08-03
5547 Tor 0.2.1.3-alpha implements most of the pieces to prevent
5548 infinite-length circuit attacks (see proposal 110); fixes a bug that
5549 might cause exit relays to corrupt streams they send back; allows
5550 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
5551 ExcludeExitNodes config options; and fixes a big pile of bugs.
5553 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
5554 - Send a bootstrap problem "warn" event on the first problem if the
5555 reason is NO_ROUTE (that is, our network is down).
5558 - Implement most of proposal 110: The first K cells to be sent
5559 along a circuit are marked as special "early" cells; only K "early"
5560 cells will be allowed. Once this code is universal, we can block
5561 certain kinds of DOS attack by requiring that EXTEND commands must
5562 be sent using an "early" cell.
5565 - Try to attach connections immediately upon receiving a RENDEZVOUS2
5566 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
5567 on the client side when connecting to a hidden service. Bugfix
5568 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
5569 - Ensure that two circuits can never exist on the same connection
5570 with the same circuit ID, even if one is marked for close. This
5571 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
5574 - When relays do their initial bandwidth measurement, don't limit
5575 to just our entry guards for the test circuits. Otherwise we tend
5576 to have multiple test circuits going through a single entry guard,
5577 which makes our bandwidth test less accurate. Fixes part of bug 654;
5578 patch contributed by Josh Albrecht.
5579 - Add an ExcludeExitNodes option so users can list a set of nodes
5580 that should be be excluded from the exit node position, but
5581 allowed elsewhere. Implements proposal 151.
5582 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
5583 ExcludeNodes and ExcludeExitNodes lists.
5584 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
5585 be more efficient. Formerly it was quadratic in the number of
5586 servers; now it should be linear. Fixes bug 509.
5587 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
5588 and n_conn_id_digest fields into a separate structure that's
5589 only needed when the circuit has not yet attached to an n_conn.
5592 - Change the contrib/tor.logrotate script so it makes the new
5593 logs as "_tor:_tor" rather than the default, which is generally
5594 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
5595 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
5596 warnings (occasionally), but it can also cause the compiler to
5597 eliminate error-checking code. Suggested by Peter Gutmann.
5598 - When a hidden service is giving up on an introduction point candidate
5599 that was not included in the last published rendezvous descriptor,
5600 don't reschedule publication of the next descriptor. Fixes bug 763.
5602 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
5603 HiddenServiceExcludeNodes as obsolete: they never worked properly,
5604 and nobody claims to be using them. Fixes bug 754. Bugfix on
5605 0.1.0.1-rc. Patch from Christian Wilms.
5606 - Fix a small alignment and memory-wasting bug on buffer chunks.
5609 o Minor bugfixes (controller):
5610 - When closing an application-side connection because its circuit
5611 is getting torn down, generate the stream event correctly.
5612 Bugfix on 0.1.2.x. Anonymous patch.
5615 - Remove all backward-compatibility code to support relays running
5616 versions of Tor so old that they no longer work at all on the
5620 Changes in version 0.2.0.30 - 2008-07-15
5622 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
5623 warnings (occasionally), but it can also cause the compiler to
5624 eliminate error-checking code. Suggested by Peter Gutmann.
5627 Changes in version 0.2.0.29-rc - 2008-07-08
5628 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
5629 hidden-service performance bugs, and fixes a bunch of smaller bugs.
5632 - If you have more than one bridge but don't know their keys,
5633 you would only launch a request for the descriptor of the first one
5634 on your list. (Tor considered launching requests for the others, but
5635 found that it already had a connection on the way for $0000...0000
5636 so it didn't open another.) Bugfix on 0.2.0.x.
5637 - If you have more than one bridge but don't know their keys, and the
5638 connection to one of the bridges failed, you would cancel all
5639 pending bridge connections. (After all, they all have the same
5640 digest.) Bugfix on 0.2.0.x.
5641 - When a hidden service was trying to establish an introduction point,
5642 and Tor had built circuits preemptively for such purposes, we
5643 were ignoring all the preemptive circuits and launching a new one
5644 instead. Bugfix on 0.2.0.14-alpha.
5645 - When a hidden service was trying to establish an introduction point,
5646 and Tor *did* manage to reuse one of the preemptively built
5647 circuits, it didn't correctly remember which one it used,
5648 so it asked for another one soon after, until there were no
5649 more preemptive circuits, at which point it launched one from
5650 scratch. Bugfix on 0.0.9.x.
5651 - Make directory servers include the X-Your-Address-Is: http header in
5652 their responses even for begin_dir conns. Now clients who only
5653 ever use begin_dir connections still have a way to learn their IP
5654 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
5657 - Fix a macro/CPP interaction that was confusing some compilers:
5658 some GCCs don't like #if/#endif pairs inside macro arguments.
5660 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
5661 Fixes bug 704; fix from Steven Murdoch.
5662 - When opening /dev/null in finish_daemonize(), do not pass the
5663 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
5664 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
5665 - Correctly detect transparent proxy support on Linux hosts that
5666 require in.h to be included before netfilter_ipv4.h. Patch
5668 - Disallow session resumption attempts during the renegotiation
5669 stage of the v2 handshake protocol. Clients should never be trying
5670 session resumption at this point, but apparently some did, in
5671 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
5672 found by Geoff Goodell.
5675 Changes in version 0.2.1.2-alpha - 2008-06-20
5676 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
5677 make it easier to set up your own private Tor network; fixes several
5678 big bugs with using more than one bridge relay; fixes a big bug with
5679 offering hidden services quickly after Tor starts; and uses a better
5680 API for reporting potential bootstrapping problems to the controller.
5683 - New TestingTorNetwork config option to allow adjustment of
5684 previously constant values that, while reasonable, could slow
5685 bootstrapping. Implements proposal 135. Patch from Karsten.
5688 - If you have more than one bridge but don't know their digests,
5689 you would only learn a request for the descriptor of the first one
5690 on your list. (Tor considered launching requests for the others, but
5691 found that it already had a connection on the way for $0000...0000
5692 so it didn't open another.) Bugfix on 0.2.0.x.
5693 - If you have more than one bridge but don't know their digests,
5694 and the connection to one of the bridges failed, you would cancel
5695 all pending bridge connections. (After all, they all have the
5696 same digest.) Bugfix on 0.2.0.x.
5697 - When establishing a hidden service, introduction points that
5698 originate from cannibalized circuits are completely ignored and not
5699 included in rendezvous service descriptors. This might be another
5700 reason for delay in making a hidden service available. Bugfix
5701 from long ago (0.0.9.x?)
5704 - Allow OpenSSL to use dynamic locks if it wants.
5705 - When building a consensus, do not include routers that are down.
5706 This will cut down 30% to 40% on consensus size. Implements
5708 - In directory authorities' approved-routers files, allow
5709 fingerprints with or without space.
5710 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
5711 controller can query our current bootstrap state in case it attaches
5712 partway through and wants to catch up.
5713 - Send an initial "Starting" bootstrap status event, so we have a
5714 state to start out in.
5717 - Asking for a conditional consensus at .../consensus/<fingerprints>
5718 would crash a dirserver if it did not already have a
5719 consensus. Bugfix on 0.2.1.1-alpha.
5720 - Clean up some macro/CPP interactions: some GCC versions don't like
5721 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
5724 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
5725 - Directory authorities shouldn't complain about bootstrapping
5726 problems just because they do a lot of reachability testing and
5727 some of the connection attempts fail.
5728 - Start sending "count" and "recommendation" key/value pairs in
5729 bootstrap problem status events, so the controller can hear about
5730 problems even before Tor decides they're worth reporting for sure.
5731 - If you're using bridges, generate "bootstrap problem" warnings
5732 as soon as you run out of working bridges, rather than waiting
5733 for ten failures -- which will never happen if you have less than
5735 - If we close our OR connection because there's been a circuit
5736 pending on it for too long, we were telling our bootstrap status
5737 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
5740 Changes in version 0.2.1.1-alpha - 2008-06-13
5741 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
5742 were making the Tor process bloat especially on Linux; makes our TLS
5743 handshake blend in better; sends "bootstrap phase" status events to
5744 the controller, so it can keep the user informed of progress (and
5745 problems) fetching directory information and establishing circuits;
5746 and adds a variety of smaller features.
5749 - More work on making our TLS handshake blend in: modify the list
5750 of ciphers advertised by OpenSSL in client mode to even more
5751 closely resemble a common web browser. We cheat a little so that
5752 we can advertise ciphers that the locally installed OpenSSL doesn't
5754 - Start sending "bootstrap phase" status events to the controller,
5755 so it can keep the user informed of progress fetching directory
5756 information and establishing circuits. Also inform the controller
5757 if we think we're stuck at a particular bootstrap phase. Implements
5759 - Resume using OpenSSL's RAND_poll() for better (and more portable)
5760 cross-platform entropy collection again. We used to use it, then
5761 stopped using it because of a bug that could crash systems that
5762 called RAND_poll when they had a lot of fds open. It looks like the
5763 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
5764 at startup, and to call RAND_poll() when we reseed later only if
5765 we have a non-buggy OpenSSL version.
5768 - When we choose to abandon a new entry guard because we think our
5769 older ones might be better, close any circuits pending on that
5770 new entry guard connection. This fix should make us recover much
5771 faster when our network is down and then comes back. Bugfix on
5772 0.1.2.8-beta; found by lodger.
5774 o Memory fixes and improvements:
5775 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
5776 to avoid unused RAM in buffer chunks and memory pools.
5777 - Speed up parsing and cut down on memory fragmentation by using
5778 stack-style allocations for parsing directory objects. Previously,
5779 this accounted for over 40% of allocations from within Tor's code
5780 on a typical directory cache.
5781 - Use a Bloom filter rather than a digest-based set to track which
5782 descriptors we need to keep around when we're cleaning out old
5783 router descriptors. This speeds up the computation significantly,
5784 and may reduce fragmentation.
5785 - Reduce the default smartlist size from 32 to 16; it turns out that
5786 most smartlists hold around 8-12 elements tops.
5787 - Make dumpstats() log the fullness and size of openssl-internal
5789 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
5790 patch to their OpenSSL, turn it on to save memory on servers. This
5791 patch will (with any luck) get included in a mainline distribution
5793 - Never use OpenSSL compression: it wastes RAM and CPU trying to
5794 compress cells, which are basically all encrypted, compressed,
5798 - Stop reloading the router list from disk for no reason when we
5799 run out of reachable directory mirrors. Once upon a time reloading
5800 it would set the 'is_running' flag back to 1 for them. It hasn't
5801 done that for a long time.
5802 - In very rare situations new hidden service descriptors were
5803 published earlier than 30 seconds after the last change to the
5804 service. (We currently think that a hidden service descriptor
5805 that's been stable for 30 seconds is worth publishing.)
5808 - Allow separate log levels to be configured for different logging
5809 domains. For example, this allows one to log all notices, warnings,
5810 or errors, plus all memory management messages of level debug or
5811 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
5812 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
5813 and stop using a warning that had become unfixably verbose under
5815 - New --hush command-line option similar to --quiet. While --quiet
5816 disables all logging to the console on startup, --hush limits the
5817 output to messages of warning and error severity.
5818 - Servers support a new URL scheme for consensus downloads that
5819 allows the client to specify which authorities are trusted.
5820 The server then only sends the consensus if the client will trust
5821 it. Otherwise a 404 error is sent back. Clients use this
5822 new scheme when the server supports it (meaning it's running
5823 0.2.1.1-alpha or later). Implements proposal 134.
5824 - New configure/torrc options (--enable-geoip-stats,
5825 DirRecordUsageByCountry) to record how many IPs we've served
5826 directory info to in each country code, how many status documents
5827 total we've sent to each country code, and what share of the total
5828 directory requests we should expect to see.
5829 - Use the TLS1 hostname extension to more closely resemble browser
5831 - Lots of new unit tests.
5832 - Add a macro to implement the common pattern of iterating through
5833 two parallel lists in lockstep.
5836 Changes in version 0.2.0.28-rc - 2008-06-13
5837 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
5838 performance bug, and fixes a bunch of smaller bugs.
5841 - Fix a bug where, when we were choosing the 'end stream reason' to
5842 put in our relay end cell that we send to the exit relay, Tor
5843 clients on Windows were sometimes sending the wrong 'reason'. The
5844 anonymity problem is that exit relays may be able to guess whether
5845 the client is running Windows, thus helping partition the anonymity
5846 set. Down the road we should stop sending reasons to exit relays,
5847 or otherwise prevent future versions of this bug.
5850 - While setting up a hidden service, some valid introduction circuits
5851 were overlooked and abandoned. This might be the reason for
5852 the long delay in making a hidden service available. Bugfix on
5856 - Update to the "June 9 2008" ip-to-country file.
5857 - Run 'make test' as part of 'make dist', so we stop releasing so
5858 many development snapshots that fail their unit tests.
5861 - When we're checking if we have enough dir info for each relay
5862 to begin establishing circuits, make sure that we actually have
5863 the descriptor listed in the consensus, not just any descriptor.
5865 - Bridge relays no longer print "xx=0" in their extrainfo document
5866 for every single country code in the geoip db. Bugfix on
5868 - Only warn when we fail to load the geoip file if we were planning to
5869 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
5870 - If we change our MaxAdvertisedBandwidth and then reload torrc,
5871 Tor won't realize it should publish a new relay descriptor. Fixes
5872 bug 688, reported by mfr. Bugfix on 0.1.2.x.
5873 - When we haven't had any application requests lately, don't bother
5874 logging that we have expired a bunch of descriptors. Bugfix
5876 - Make relay cells written on a connection count as non-padding when
5877 tracking how long a connection has been in use. Bugfix on
5878 0.2.0.1-alpha. Spotted by lodger.
5879 - Fix unit tests in 0.2.0.27-rc.
5880 - Fix compile on Windows.
5883 Changes in version 0.2.0.27-rc - 2008-06-03
5884 Tor 0.2.0.27-rc adds a few features we left out of the earlier
5885 release candidates. In particular, we now include an IP-to-country
5886 GeoIP database, so controllers can easily look up what country a
5887 given relay is in, and so bridge relays can give us some sanitized
5888 summaries about which countries are making use of bridges. (See proposal
5889 126-geoip-fetching.txt for details.)
5892 - Include an IP-to-country GeoIP file in the tarball, so bridge
5893 relays can report sanitized summaries of the usage they're seeing.
5896 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
5897 Robert Hogan. Fixes the first part of bug 681.
5898 - Make bridge authorities never serve extrainfo docs.
5899 - Add support to detect Libevent versions in the 1.4.x series
5901 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
5902 - Include a new contrib/tor-exit-notice.html file that exit relay
5903 operators can put on their website to help reduce abuse queries.
5906 - When tunneling an encrypted directory connection, and its first
5907 circuit fails, do not leave it unattached and ask the controller
5908 to deal. Fixes the second part of bug 681.
5909 - Make bridge authorities correctly expire old extrainfo documents
5913 Changes in version 0.2.0.26-rc - 2008-05-13
5914 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
5915 in Debian's OpenSSL packages. All users running any 0.2.0.x version
5916 should upgrade, whether they're running Debian or not.
5918 o Major security fixes:
5919 - Use new V3 directory authority keys on the tor26, gabelmoo, and
5920 moria1 V3 directory authorities. The old keys were generated with
5921 a vulnerable version of Debian's OpenSSL package, and must be
5922 considered compromised. Other authorities' keys were not generated
5923 with an affected version of OpenSSL.
5926 - List authority signatures as "unrecognized" based on DirServer
5927 lines, not on cert cache. Bugfix on 0.2.0.x.
5930 - Add a new V3AuthUseLegacyKey option to make it easier for
5931 authorities to change their identity keys if they have to.
5934 Changes in version 0.2.0.25-rc - 2008-04-23
5935 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
5938 - Remember to initialize threading before initializing logging.
5939 Otherwise, many BSD-family implementations will crash hard on
5940 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
5943 - Authorities correctly free policies on bad servers on
5944 exit. Fixes bug 672. Bugfix on 0.2.0.x.
5947 Changes in version 0.2.0.24-rc - 2008-04-22
5948 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
5949 v3 directory authority, makes relays with dynamic IP addresses and no
5950 DirPort notice more quickly when their IP address changes, fixes a few
5951 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
5953 o New directory authorities:
5954 - Take lefkada out of the list of v3 directory authorities, since
5955 it has been down for months.
5956 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
5960 - Detect address changes more quickly on non-directory mirror
5961 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
5963 o Minor features (security):
5964 - Reject requests for reverse-dns lookup of names that are in
5965 a private address space. Patch from lodger.
5966 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
5969 o Minor bugfixes (crashes):
5970 - Avoid a rare assert that can trigger when Tor doesn't have much
5971 directory information yet and it tries to fetch a v2 hidden
5972 service descriptor. Fixes bug 651, reported by nwf.
5973 - Initialize log mutex before initializing dmalloc. Otherwise,
5974 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
5975 - Use recursive pthread mutexes in order to avoid deadlock when
5976 logging debug-level messages to a controller. Bug spotted by nwf,
5977 bugfix on 0.2.0.16-alpha.
5979 o Minor bugfixes (resource management):
5980 - Keep address policies from leaking memory: start their refcount
5981 at 1, not 2. Bugfix on 0.2.0.16-alpha.
5982 - Free authority certificates on exit, so they don't look like memory
5983 leaks. Bugfix on 0.2.0.19-alpha.
5984 - Free static hashtables for policy maps and for TLS connections on
5985 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
5986 - Avoid allocating extra space when computing consensuses on 64-bit
5987 platforms. Bug spotted by aakova.
5989 o Minor bugfixes (misc):
5990 - Do not read the configuration file when we've only been told to
5991 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
5992 based on patch from Sebastian Hahn.
5993 - Exit relays that are used as a client can now reach themselves
5994 using the .exit notation, rather than just launching an infinite
5995 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
5996 - When attempting to open a logfile fails, tell us why.
5997 - Fix a dumb bug that was preventing us from knowing that we should
5998 preemptively build circuits to handle expected directory requests.
5999 Fixes bug 660. Bugfix on 0.1.2.x.
6000 - Warn less verbosely about clock skew from netinfo cells from
6001 untrusted sources. Fixes bug 663.
6002 - Make controller stream events for DNS requests more consistent,
6003 by adding "new stream" events for DNS requests, and removing
6004 spurious "stream closed" events" for cached reverse resolves.
6005 Patch from mwenge. Fixes bug 646.
6006 - Correctly notify one-hop connections when a circuit build has
6007 failed. Possible fix for bug 669. Found by lodger.
6010 Changes in version 0.2.0.23-rc - 2008-03-24
6011 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
6012 makes bootstrapping faster if the first directory mirror you contact
6013 is down. The bundles also include the new Vidalia 0.1.2 release.
6016 - When a tunneled directory request is made to a directory server
6017 that's down, notice after 30 seconds rather than 120 seconds. Also,
6018 fail any begindir streams that are pending on it, so they can
6019 retry elsewhere. This was causing multi-minute delays on bootstrap.
6022 Changes in version 0.2.0.22-rc - 2008-03-18
6023 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
6024 enables encrypted directory connections by default for non-relays, fixes
6025 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
6026 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
6029 - Enable encrypted directory connections by default for non-relays,
6030 so censor tools that block Tor directory connections based on their
6031 plaintext patterns will no longer work. This means Tor works in
6032 certain censored countries by default again.
6035 - Make sure servers always request certificates from clients during
6036 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
6037 - Do not enter a CPU-eating loop when a connection is closed in
6038 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
6039 diagnosed by lodger; bugfix on 0.2.0.20-rc.
6040 - Fix assertion failure that could occur when a blocked circuit
6041 became unblocked, and it had pending client DNS requests. Bugfix
6042 on 0.2.0.1-alpha. Fixes bug 632.
6044 o Minor bugfixes (on 0.1.2.x):
6045 - Generate "STATUS_SERVER" events rather than misspelled
6046 "STATUS_SEVER" events. Caught by mwenge.
6047 - When counting the number of bytes written on a TLS connection,
6048 look at the BIO actually used for writing to the network, not
6049 at the BIO used (sometimes) to buffer data for the network.
6050 Looking at different BIOs could result in write counts on the
6051 order of ULONG_MAX. Fixes bug 614.
6052 - On Windows, correctly detect errors when listing the contents of
6053 a directory. Fix from lodger.
6055 o Minor bugfixes (on 0.2.0.x):
6056 - Downgrade "sslv3 alert handshake failure" message to INFO.
6057 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
6058 left BandwidthRate and BandwidthBurst at the default, we would be
6059 silently limited by those defaults. Now raise them to match the
6060 RelayBandwidth* values.
6061 - Fix the SVK version detection logic to work correctly on a branch.
6062 - Make --enable-openbsd-malloc work correctly on Linux with alpha
6063 CPUs. Fixes bug 625.
6064 - Logging functions now check that the passed severity is sane.
6065 - Use proper log levels in the testsuite call of
6066 get_interface_address6().
6067 - When using a nonstandard malloc, do not use the platform values for
6068 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
6069 - Make the openbsd malloc code use 8k pages on alpha CPUs and
6071 - Detect mismatched page sizes when using --enable-openbsd-malloc.
6072 - Avoid double-marked-for-close warning when certain kinds of invalid
6073 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
6074 for bug 617. Bugfix on 0.2.0.1-alpha.
6075 - Make sure that the "NULL-means-reject *:*" convention is followed by
6076 all the policy manipulation functions, avoiding some possible crash
6077 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
6078 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
6079 actually works, and doesn't warn about every single reverse lookup.
6080 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
6083 - Only log guard node status when guard node status has changed.
6084 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
6085 make "INFO" 75% less verbose.
6088 Changes in version 0.2.0.21-rc - 2008-03-02
6089 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
6090 makes Tor work well with Vidalia again, fixes a rare assert bug,
6091 and fixes a pair of more minor bugs. The bundles also include Vidalia
6092 0.1.0 and Torbutton 1.1.16.
6095 - The control port should declare that it requires password auth
6096 when HashedControlSessionPassword is set too. Patch from Matt Edman;
6097 bugfix on 0.2.0.20-rc. Fixes bug 615.
6098 - Downgrade assert in connection_buckets_decrement() to a log message.
6099 This may help us solve bug 614, and in any case will make its
6100 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
6101 - We were sometimes miscounting the number of bytes read from the
6102 network, causing our rate limiting to not be followed exactly.
6103 Bugfix on 0.2.0.16-alpha. Reported by lodger.
6106 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
6107 OpenSSL versions should have been working fine. Diagnosis and patch
6108 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
6109 Bugfix on 0.2.0.20-rc.
6112 Changes in version 0.2.0.20-rc - 2008-02-24
6113 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
6114 makes more progress towards normalizing Tor's TLS handshake, makes
6115 hidden services work better again, helps relays bootstrap if they don't
6116 know their IP address, adds optional support for linking in openbsd's
6117 allocator or tcmalloc, allows really fast relays to scale past 15000
6118 sockets, and fixes a bunch of minor bugs reported by Veracode.
6121 - Enable the revised TLS handshake based on the one designed by
6122 Steven Murdoch in proposal 124, as revised in proposal 130. It
6123 includes version negotiation for OR connections as described in
6124 proposal 105. The new handshake is meant to be harder for censors
6125 to fingerprint, and it adds the ability to detect certain kinds of
6126 man-in-the-middle traffic analysis attacks. The version negotiation
6127 feature will allow us to improve Tor's link protocol more safely
6129 - Choose which bridge to use proportional to its advertised bandwidth,
6130 rather than uniformly at random. This should speed up Tor for
6131 bridge users. Also do this for people who set StrictEntryNodes.
6132 - When a TrackHostExits-chosen exit fails too many times in a row,
6133 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
6136 - Resolved problems with (re-)fetching hidden service descriptors.
6137 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
6139 - If we only ever used Tor for hidden service lookups or posts, we
6140 would stop building circuits and start refusing connections after
6141 24 hours, since we falsely believed that Tor was dormant. Reported
6142 by nwf; bugfix on 0.1.2.x.
6143 - Servers that don't know their own IP address should go to the
6144 authorities for their first directory fetch, even if their DirPort
6145 is off or if they don't know they're reachable yet. This will help
6146 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
6147 - When counting the number of open sockets, count not only the number
6148 of sockets we have received from the socket() call, but also
6149 the number we've gotten from accept() and socketpair(). This bug
6150 made us fail to count all sockets that we were using for incoming
6151 connections. Bugfix on 0.2.0.x.
6152 - Fix code used to find strings within buffers, when those strings
6153 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
6154 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
6155 - Add a new __HashedControlSessionPassword option for controllers
6156 to use for one-off session password hashes that shouldn't get
6157 saved to disk by SAVECONF --- Vidalia users were accumulating a
6158 pile of HashedControlPassword lines in their torrc files, one for
6159 each time they had restarted Tor and then clicked Save. Make Tor
6160 automatically convert "HashedControlPassword" to this new option but
6161 only when it's given on the command line. Partial fix for bug 586.
6163 o Minor features (performance):
6164 - Tune parameters for cell pool allocation to minimize amount of
6166 - Add OpenBSD malloc code from phk as an optional malloc
6167 replacement on Linux: some glibc libraries do very poorly
6168 with Tor's memory allocation patterns. Pass
6169 --enable-openbsd-malloc to get the replacement malloc code.
6170 - Add a --with-tcmalloc option to the configure script to link
6171 against tcmalloc (if present). Does not yet search for
6172 non-system include paths.
6173 - Stop imposing an arbitrary maximum on the number of file descriptors
6174 used for busy servers. Bug reported by Olaf Selke; patch from
6177 o Minor features (other):
6178 - When SafeLogging is disabled, log addresses along with all TLS
6180 - When building with --enable-gcc-warnings, check for whether Apple's
6181 warning "-Wshorten-64-to-32" is available.
6182 - Add a --passphrase-fd argument to the tor-gencert command for
6185 o Minor bugfixes (memory leaks and code problems):
6186 - We were leaking a file descriptor if Tor started with a zero-length
6187 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
6188 - Detect size overflow in zlib code. Reported by Justin Ferguson and
6190 - We were comparing the raw BridgePassword entry with a base64'ed
6191 version of it, when handling a "/tor/networkstatus-bridges"
6192 directory request. Now compare correctly. Noticed by Veracode.
6193 - Recover from bad tracked-since value in MTBF-history file.
6195 - Alter the code that tries to recover from unhandled write
6196 errors, to not try to flush onto a socket that's given us
6197 unhandled errors. Bugfix on 0.1.2.x.
6198 - Make Unix controlsockets work correctly on OpenBSD. Patch from
6199 tup. Bugfix on 0.2.0.3-alpha.
6201 o Minor bugfixes (other):
6202 - If we have an extra-info document for our server, always make
6203 it available on the control port, even if we haven't gotten
6204 a copy of it from an authority yet. Patch from mwenge.
6205 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
6206 - Directory mirrors no longer include a guess at the client's IP
6207 address if the connection appears to be coming from the same /24
6208 network; it was producing too many wrong guesses.
6209 - Make the new hidden service code respect the SafeLogging setting.
6210 Bugfix on 0.2.0.x. Patch from Karsten.
6211 - When starting as an authority, do not overwrite all certificates
6212 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
6213 - If we're trying to flush the last bytes on a connection (for
6214 example, when answering a directory request), reset the
6215 time-to-give-up timeout every time we manage to write something
6216 on the socket. Bugfix on 0.1.2.x.
6217 - Change the behavior of "getinfo status/good-server-descriptor"
6218 so it doesn't return failure when any authority disappears.
6219 - Even though the man page said that "TrackHostExits ." should
6220 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
6221 - Report TLS "zero return" case as a "clean close" and "IO error"
6222 as a "close". Stop calling closes "unexpected closes": existing
6223 Tors don't use SSL_close(), so having a connection close without
6224 the TLS shutdown handshake is hardly unexpected.
6225 - Send NAMESERVER_STATUS messages for a single failed nameserver
6228 o Code simplifications and refactoring:
6229 - Remove the tor_strpartition function: its logic was confused,
6230 and it was only used for one thing that could be implemented far
6234 Changes in version 0.2.0.19-alpha - 2008-02-09
6235 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
6236 handshake, makes path selection for relays more secure and IP address
6237 guessing more robust, and generally fixes a lot of bugs in preparation
6238 for calling the 0.2.0 branch stable.
6241 - Do not include recognizeable strings in the commonname part of
6242 Tor's x509 certificates.
6245 - If we're a relay, avoid picking ourselves as an introduction point,
6246 a rendezvous point, or as the final hop for internal circuits. Bug
6247 reported by taranis and lodger. Bugfix on 0.1.2.x.
6248 - Patch from "Andrew S. Lists" to catch when we contact a directory
6249 mirror at IP address X and he says we look like we're coming from
6250 IP address X. Bugfix on 0.1.2.x.
6252 o Minor features (security):
6253 - Be more paranoid about overwriting sensitive memory on free(),
6254 as a defensive programming tactic to ensure forward secrecy.
6256 o Minor features (directory authority):
6257 - Actually validate the options passed to AuthDirReject,
6258 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
6259 - Reject router descriptors with out-of-range bandwidthcapacity or
6260 bandwidthburst values.
6262 o Minor features (controller):
6263 - Reject controller commands over 1MB in length. This keeps rogue
6264 processes from running us out of memory.
6266 o Minor features (misc):
6267 - Give more descriptive well-formedness errors for out-of-range
6268 hidden service descriptor/protocol versions.
6269 - Make memory debugging information describe more about history
6270 of cell allocation, so we can help reduce our memory use.
6272 o Deprecated features (controller):
6273 - The status/version/num-versioning and status/version/num-concurring
6274 GETINFO options are no longer useful in the v3 directory protocol:
6275 treat them as deprecated, and warn when they're used.
6278 - When our consensus networkstatus has been expired for a while, stop
6279 being willing to build circuits using it. Fixes bug 401. Bugfix
6281 - Directory caches now fetch certificates from all authorities
6282 listed in a networkstatus consensus, even when they do not
6283 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
6284 - When connecting to a bridge without specifying its key, insert
6285 the connection into the identity-to-connection map as soon as
6286 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
6287 - Detect versions of OS X where malloc_good_size() is present in the
6288 library but never actually declared. Resolves bug 587. Bugfix
6290 - Stop incorrectly truncating zlib responses to directory authority
6291 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
6292 - Stop recommending that every server operator send mail to tor-ops.
6293 Resolves bug 597. Bugfix on 0.1.2.x.
6294 - Don't trigger an assert if we start a directory authority with a
6295 private IP address (like 127.0.0.1).
6296 - Avoid possible failures when generating a directory with routers
6297 with over-long versions strings, or too many flags set. Bugfix
6299 - If an attempt to launch a DNS resolve request over the control
6300 port fails because we have overrun the limit on the number of
6301 connections, tell the controller that the request has failed.
6302 - Avoid using too little bandwidth when our clock skips a few
6303 seconds. Bugfix on 0.1.2.x.
6304 - Fix shell error when warning about missing packages in configure
6305 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
6306 - Do not become confused when receiving a spurious VERSIONS-like
6307 cell from a confused v1 client. Bugfix on 0.2.0.x.
6308 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
6309 introduction points for a hidden service have failed. Patch from
6310 Karsten Loesing. Bugfix on 0.2.0.x.
6312 o Code simplifications and refactoring:
6313 - Remove some needless generality from cpuworker code, for improved
6315 - Stop overloading the circuit_t.onionskin field for both "onionskin
6316 from a CREATE cell that we are waiting for a cpuworker to be
6317 assigned" and "onionskin from an EXTEND cell that we are going to
6318 send to an OR as soon as we are connected". Might help with bug 600.
6319 - Add an in-place version of aes_crypt() so that we can avoid doing a
6320 needless memcpy() call on each cell payload.
6323 Changes in version 0.2.0.18-alpha - 2008-01-25
6324 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
6325 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
6326 that can warn or reject connections to ports generally associated with
6327 vulnerable-plaintext protocols.
6329 o New directory authorities:
6330 - Set up dannenberg (run by CCC) as the sixth v3 directory
6334 - Fix a major memory leak when attempting to use the v2 TLS
6335 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
6336 - We accidentally enabled the under-development v2 TLS handshake
6337 code, which was causing log entries like "TLS error while
6338 renegotiating handshake". Disable it again. Resolves bug 590.
6339 - We were computing the wrong Content-Length: header for directory
6340 responses that need to be compressed on the fly, causing clients
6341 asking for those items to always fail. Bugfix on 0.2.0.x; partially
6345 - Avoid going directly to the directory authorities even if you're a
6346 relay, if you haven't found yourself reachable yet or if you've
6347 decided not to advertise your dirport yet. Addresses bug 556.
6348 - If we've gone 12 hours since our last bandwidth check, and we
6349 estimate we have less than 50KB bandwidth capacity but we could
6350 handle more, do another bandwidth test.
6351 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
6352 Tor can warn and/or refuse connections to ports commonly used with
6353 vulnerable-plaintext protocols. Currently we warn on ports 23,
6354 109, 110, and 143, but we don't reject any.
6357 - When we setconf ClientOnly to 1, close any current OR and Dir
6358 listeners. Reported by mwenge.
6359 - When we get a consensus that's been signed by more people than
6360 we expect, don't log about it; it's not a big deal. Reported
6364 - Don't answer "/tor/networkstatus-bridges" directory requests if
6365 the request isn't encrypted.
6366 - Make "ClientOnly 1" config option disable directory ports too.
6367 - Patches from Karsten Loesing to make v2 hidden services more
6368 robust: work even when there aren't enough HSDir relays available;
6369 retry when a v2 rend desc fetch fails; but don't retry if we
6370 already have a usable v0 rend desc.
6373 Changes in version 0.2.0.17-alpha - 2008-01-17
6374 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
6377 - Make the tor-gencert man page get included correctly in the tarball.
6380 Changes in version 0.2.0.16-alpha - 2008-01-17
6381 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
6382 Loesing, and generally cleans up a lot of features and minor bugs.
6384 o New directory authorities:
6385 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
6388 o Major performance improvements:
6389 - Switch our old ring buffer implementation for one more like that
6390 used by free Unix kernels. The wasted space in a buffer with 1mb
6391 of data will now be more like 8k than 1mb. The new implementation
6392 also avoids realloc();realloc(); patterns that can contribute to
6393 memory fragmentation.
6396 - Configuration files now accept C-style strings as values. This
6397 helps encode characters not allowed in the current configuration
6398 file format, such as newline or #. Addresses bug 557.
6399 - Although we fixed bug 539 (where servers would send HTTP status 503
6400 responses _and_ send a body too), there are still servers out
6401 there that haven't upgraded. Therefore, make clients parse such
6402 bodies when they receive them.
6403 - When we're not serving v2 directory information, there is no reason
6404 to actually keep any around. Remove the obsolete files and directory
6405 on startup if they are very old and we aren't going to serve them.
6407 o Minor performance improvements:
6408 - Reference-count and share copies of address policy entries; only 5%
6409 of them were actually distinct.
6410 - Never walk through the list of logs if we know that no log is
6411 interested in a given message.
6414 - When an authority has not signed a consensus, do not try to
6415 download a nonexistent "certificate with key 00000000". Bugfix
6416 on 0.2.0.x. Fixes bug 569.
6417 - Fix a rare assert error when we're closing one of our threads:
6418 use a mutex to protect the list of logs, so we never write to the
6419 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
6420 bug 575, which is kind of the revenge of bug 222.
6421 - Patch from Karsten Loesing to complain less at both the client
6422 and the relay when a relay used to have the HSDir flag but doesn't
6423 anymore, and we try to upload a hidden service descriptor.
6424 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
6426 - Do not try to download missing certificates until we have tried
6427 to check our fallback consensus. Fixes bug 583.
6428 - Make bridges round reported GeoIP stats info up to the nearest
6429 estimate, not down. Now we can distinguish between "0 people from
6430 this country" and "1 person from this country".
6431 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
6432 - Avoid possible segfault if key generation fails in
6433 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
6434 - Avoid segfault in the case where a badly behaved v2 versioning
6435 directory sends a signed networkstatus with missing client-versions.
6437 - Avoid segfaults on certain complex invocations of
6438 router_get_by_hexdigest(). Bugfix on 0.1.2.
6439 - Correct bad index on array access in parse_http_time(). Bugfix
6441 - Fix possible bug in vote generation when server versions are present
6442 but client versions are not.
6443 - Fix rare bug on REDIRECTSTREAM control command when called with no
6444 port set: it could erroneously report an error when none had
6446 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
6447 compressing large objects and find ourselves with more than 4k
6448 left over. Bugfix on 0.2.0.
6449 - Fix a small memory leak when setting up a hidden service.
6450 - Fix a few memory leaks that could in theory happen under bizarre
6452 - Fix an assert if we post a general-purpose descriptor via the
6453 control port but that descriptor isn't mentioned in our current
6454 network consensus. Bug reported by Jon McLachlan; bugfix on
6457 o Minor features (controller):
6458 - Get NS events working again. Patch from tup.
6459 - The GETCONF command now escapes and quotes configuration values
6460 that don't otherwise fit into the torrc file.
6461 - The SETCONF command now handles quoted values correctly.
6463 o Minor features (directory authorities):
6464 - New configuration options to override default maximum number of
6465 servers allowed on a single IP address. This is important for
6466 running a test network on a single host.
6467 - Actually implement the -s option to tor-gencert.
6468 - Add a manual page for tor-gencert.
6470 o Minor features (bridges):
6471 - Bridge authorities no longer serve bridge descriptors over
6472 unencrypted connections.
6474 o Minor features (other):
6475 - Add hidden services and DNSPorts to the list of things that make
6476 Tor accept that it has running ports. Change starting Tor with no
6477 ports from a fatal error to a warning; we might change it back if
6478 this turns out to confuse anybody. Fixes bug 579.
6481 Changes in version 0.1.2.19 - 2008-01-17
6482 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
6483 exit policy a little bit more conservative so it's safer to run an
6484 exit relay on a home system, and fixes a variety of smaller issues.
6487 - Exit policies now reject connections that are addressed to a
6488 relay's public (external) IP address too, unless
6489 ExitPolicyRejectPrivate is turned off. We do this because too
6490 many relays are running nearby to services that trust them based
6494 - When the clock jumps forward a lot, do not allow the bandwidth
6495 buckets to become negative. Fixes bug 544.
6496 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
6497 on every successful resolve. Reported by Mike Perry.
6498 - Purge old entries from the "rephist" database and the hidden
6499 service descriptor database even when DirPort is zero.
6500 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
6501 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
6502 crashing or mis-answering these requests.
6503 - When we decide to send a 503 response to a request for servers, do
6504 not then also send the server descriptors: this defeats the whole
6505 purpose. Fixes bug 539.
6508 - Changing the ExitPolicyRejectPrivate setting should cause us to
6509 rebuild our server descriptor.
6510 - Fix handling of hex nicknames when answering controller requests for
6511 networkstatus by name, or when deciding whether to warn about
6512 unknown routers in a config option. (Patch from mwenge.)
6513 - Fix a couple of hard-to-trigger autoconf problems that could result
6514 in really weird results on platforms whose sys/types.h files define
6515 nonstandard integer types.
6516 - Don't try to create the datadir when running --verify-config or
6517 --hash-password. Resolves bug 540.
6518 - If we were having problems getting a particular descriptor from the
6519 directory caches, and then we learned about a new descriptor for
6520 that router, we weren't resetting our failure count. Reported
6522 - Although we fixed bug 539 (where servers would send HTTP status 503
6523 responses _and_ send a body too), there are still servers out there
6524 that haven't upgraded. Therefore, make clients parse such bodies
6525 when they receive them.
6526 - Run correctly on systems where rlim_t is larger than unsigned long.
6527 This includes some 64-bit systems.
6528 - Run correctly on platforms (like some versions of OS X 10.5) where
6529 the real limit for number of open files is OPEN_FILES, not rlim_max
6530 from getrlimit(RLIMIT_NOFILES).
6531 - Avoid a spurious free on base64 failure.
6532 - Avoid segfaults on certain complex invocations of
6533 router_get_by_hexdigest().
6534 - Fix rare bug on REDIRECTSTREAM control command when called with no
6535 port set: it could erroneously report an error when none had
6539 Changes in version 0.2.0.15-alpha - 2007-12-25
6540 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
6541 features added in 0.2.0.13-alpha.
6544 - Fix several remotely triggerable asserts based on DirPort requests
6545 for a v2 or v3 networkstatus object before we were prepared. This
6546 was particularly bad for 0.2.0.13 and later bridge relays, who
6547 would never have a v2 networkstatus and would thus always crash
6548 when used. Bugfixes on 0.2.0.x.
6549 - Estimate the v3 networkstatus size more accurately, rather than
6550 estimating it at zero bytes and giving it artificially high priority
6551 compared to other directory requests. Bugfix on 0.2.0.x.
6554 - Fix configure.in logic for cross-compilation.
6555 - When we load a bridge descriptor from the cache, and it was
6556 previously unreachable, mark it as retriable so we won't just
6557 ignore it. Also, try fetching a new copy immediately. Bugfixes
6559 - The bridge GeoIP stats were counting other relays, for example
6560 self-reachability and authority-reachability tests.
6563 - Support compilation to target iPhone; patch from cjacker huang.
6564 To build for iPhone, pass the --enable-iphone option to configure.
6567 Changes in version 0.2.0.14-alpha - 2007-12-23
6569 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
6570 without a datadirectory from a previous Tor install. Reported
6572 - Fix a crash when we fetch a descriptor that turns out to be
6573 unexpected (it used to be in our networkstatus when we started
6574 fetching it, but it isn't in our current networkstatus), and we
6575 aren't using bridges. Bugfix on 0.2.0.x.
6576 - Fix a crash when accessing hidden services: it would work the first
6577 time you use a given introduction point for your service, but
6578 on subsequent requests we'd be using garbage memory. Fixed by
6579 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
6580 - Fix a crash when we load a bridge descriptor from disk but we don't
6581 currently have a Bridge line for it in our torrc. Bugfix on
6585 - If bridge authorities set BridgePassword, they will serve a
6586 snapshot of known bridge routerstatuses from their DirPort to
6587 anybody who knows that password. Unset by default.
6590 - Make the unit tests build again.
6591 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
6592 - Make PublishServerDescriptor default to 1, so the default doesn't
6593 have to change as we invent new directory protocol versions.
6594 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
6595 be included unless sys/time.h is already included. Fixes
6596 bug 553. Bugfix on 0.2.0.x.
6597 - If we receive a general-purpose descriptor and then receive an
6598 identical bridge-purpose descriptor soon after, don't discard
6599 the next one as a duplicate.
6602 - If BridgeRelay is set to 1, then the default for
6603 PublishServerDescriptor is now "bridge" rather than "v2,v3".
6604 - If the user sets RelayBandwidthRate but doesn't set
6605 RelayBandwidthBurst, then make them equal rather than erroring out.
6608 Changes in version 0.2.0.13-alpha - 2007-12-21
6609 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
6610 Goodell, fixes many more bugs, and adds a lot of infrastructure for
6613 o New directory authorities:
6614 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
6618 - Only update guard status (usable / not usable) once we have
6619 enough directory information. This was causing us to always pick
6620 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
6621 causing us to discard all our guards on startup if we hadn't been
6622 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
6623 - Purge old entries from the "rephist" database and the hidden
6624 service descriptor databases even when DirPort is zero. Bugfix
6626 - We were ignoring our RelayBandwidthRate for the first 30 seconds
6627 after opening a circuit -- even a relayed circuit. Bugfix on
6629 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
6630 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
6631 crashing or mis-answering these types of requests.
6632 - Relays were publishing their server descriptor to v1 and v2
6633 directory authorities, but they didn't try publishing to v3-only
6634 authorities. Fix this; and also stop publishing to v1 authorities.
6636 - When we were reading router descriptors from cache, we were ignoring
6637 the annotations -- so for example we were reading in bridge-purpose
6638 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
6639 - When we decided to send a 503 response to a request for servers, we
6640 were then also sending the server descriptors: this defeats the
6641 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
6644 - Bridge relays now behave like clients with respect to time
6645 intervals for downloading new consensus documents -- otherwise they
6646 stand out. Bridge users now wait until the end of the interval,
6647 so their bridge relay will be sure to have a new consensus document.
6648 - Three new config options (AlternateDirAuthority,
6649 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
6650 user selectively replace the default directory authorities by type,
6651 rather than the all-or-nothing replacement that DirServer offers.
6652 - Tor can now be configured to read a GeoIP file from disk in one
6653 of two formats. This can be used by controllers to map IP addresses
6654 to countries. Eventually, it may support exit-by-country.
6655 - When possible, bridge relays remember which countries users
6656 are coming from, and report aggregate information in their
6657 extra-info documents, so that the bridge authorities can learn
6658 where Tor is blocked.
6659 - Bridge directory authorities now do reachability testing on the
6660 bridges they know. They provide router status summaries to the
6661 controller via "getinfo ns/purpose/bridge", and also dump summaries
6662 to a file periodically.
6663 - Stop fetching directory info so aggressively if your DirPort is
6664 on but your ORPort is off; stop fetching v2 dir info entirely.
6665 You can override these choices with the new FetchDirInfoEarly
6669 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
6670 consensus documents when there are too many relays at a single
6671 IP address. Now clear it in v2 network status documents too, and
6672 also clear it in routerinfo_t when the relay is no longer listed
6673 in the relevant networkstatus document.
6674 - Don't crash if we get an unexpected value for the
6675 PublishServerDescriptor config option. Reported by Matt Edman;
6676 bugfix on 0.2.0.9-alpha.
6677 - Our new v2 hidden service descriptor format allows descriptors
6678 that have no introduction points. But Tor crashed when we tried
6679 to build a descriptor with no intro points (and it would have
6680 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
6682 - Fix building with dmalloc 5.5.2 with glibc.
6683 - Reject uploaded descriptors and extrainfo documents if they're
6684 huge. Otherwise we'll cache them all over the network and it'll
6685 clog everything up. Reported by Aljosha Judmayer.
6686 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
6687 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
6688 - When the DANGEROUS_VERSION controller status event told us we're
6689 running an obsolete version, it used the string "OLD" to describe
6690 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
6691 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
6692 - If we can't expand our list of entry guards (e.g. because we're
6693 using bridges or we have StrictEntryNodes set), don't mark relays
6694 down when they fail a directory request. Otherwise we're too quick
6695 to mark all our entry points down. Bugfix on 0.1.2.x.
6696 - Fix handling of hex nicknames when answering controller requests for
6697 networkstatus by name, or when deciding whether to warn about unknown
6698 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
6699 - Fix a couple of hard-to-trigger autoconf problems that could result
6700 in really weird results on platforms whose sys/types.h files define
6701 nonstandard integer types. Bugfix on 0.1.2.x.
6702 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
6703 - Don't crash on name lookup when we have no current consensus. Fixes
6704 bug 538; bugfix on 0.2.0.x.
6705 - Only Tors that want to mirror the v2 directory info should
6706 create the "cached-status" directory in their datadir. (All Tors
6707 used to create it.) Bugfix on 0.2.0.9-alpha.
6708 - Directory authorities should only automatically download Extra Info
6709 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
6712 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
6713 consumers. (We already do this on HUP.)
6714 - Authorities and caches fetch the v2 networkstatus documents
6715 less often, now that v3 is encouraged.
6716 - Add a new config option BridgeRelay that specifies you want to
6717 be a bridge relay. Right now the only difference is that it makes
6718 you answer begin_dir requests, and it makes you cache dir info,
6719 even if your DirPort isn't on.
6720 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
6721 ask about source, timestamp of arrival, purpose, etc. We need
6722 something like this to help Vidalia not do GeoIP lookups on bridge
6724 - Allow multiple HashedControlPassword config lines, to support
6725 multiple controller passwords.
6726 - Authorities now decide whether they're authoritative for a given
6727 router based on the router's purpose.
6728 - New config options AuthDirBadDir and AuthDirListBadDirs for
6729 authorities to mark certain relays as "bad directories" in the
6730 networkstatus documents. Also supports the "!baddir" directive in
6731 the approved-routers file.
6734 Changes in version 0.2.0.12-alpha - 2007-11-16
6735 This twelfth development snapshot fixes some more build problems as
6736 well as a few minor bugs.
6739 - Make it build on OpenBSD again. Patch from tup.
6740 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
6741 package-building for Red Hat, OS X, etc.
6743 o Minor bugfixes (on 0.1.2.x):
6744 - Changing the ExitPolicyRejectPrivate setting should cause us to
6745 rebuild our server descriptor.
6747 o Minor bugfixes (on 0.2.0.x):
6748 - When we're lacking a consensus, don't try to perform rendezvous
6749 operations. Reported by Karsten Loesing.
6750 - Fix a small memory leak whenever we decide against using a
6751 newly picked entry guard. Reported by Mike Perry.
6752 - When authorities detected more than two relays running on the same
6753 IP address, they were clearing all the status flags but forgetting
6754 to clear the "hsdir" flag. So clients were being told that a
6755 given relay was the right choice for a v2 hsdir lookup, yet they
6756 never had its descriptor because it was marked as 'not running'
6758 - If we're trying to fetch a bridge descriptor and there's no way
6759 the bridge authority could help us (for example, we don't know
6760 a digest, or there is no bridge authority), don't be so eager to
6761 fall back to asking the bridge authority.
6762 - If we're using bridges or have strictentrynodes set, and our
6763 chosen exit is in the same family as all our bridges/entry guards,
6764 then be flexible about families.
6767 - When we negotiate a v2 link-layer connection (not yet implemented),
6768 accept RELAY_EARLY cells and turn them into RELAY cells if we've
6769 negotiated a v1 connection for their next step. Initial code for
6773 Changes in version 0.2.0.11-alpha - 2007-11-12
6774 This eleventh development snapshot fixes some build problems with
6775 the previous snapshot. It also includes a more secure-by-default exit
6776 policy for relays, fixes an enormous memory leak for exit relays, and
6777 fixes another bug where servers were falling out of the directory list.
6780 - Exit policies now reject connections that are addressed to a
6781 relay's public (external) IP address too, unless
6782 ExitPolicyRejectPrivate is turned off. We do this because too
6783 many relays are running nearby to services that trust them based
6784 on network address. Bugfix on 0.1.2.x.
6787 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
6788 on every successful resolve. Reported by Mike Perry; bugfix
6790 - On authorities, never downgrade to old router descriptors simply
6791 because they're listed in the consensus. This created a catch-22
6792 where we wouldn't list a new descriptor because there was an
6793 old one in the consensus, and we couldn't get the new one in the
6794 consensus because we wouldn't list it. Possible fix for bug 548.
6795 Also, this might cause bug 543 to appear on authorities; if so,
6796 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
6798 o Packaging fixes on 0.2.0.10-alpha:
6799 - We were including instructions about what to do with the
6800 src/config/fallback-consensus file, but we weren't actually
6801 including it in the tarball. Disable all of that for now.
6804 - Allow people to say PreferTunnelledDirConns rather than
6805 PreferTunneledDirConns, for those alternate-spellers out there.
6808 - Don't reevaluate all the information from our consensus document
6809 just because we've downloaded a v2 networkstatus that we intend
6810 to cache. Fixes bug 545; bugfix on 0.2.0.x.
6813 Changes in version 0.2.0.10-alpha - 2007-11-10
6814 This tenth development snapshot adds a third v3 directory authority
6815 run by Mike Perry, adds most of Karsten Loesing's new hidden service
6816 descriptor format, fixes a bad crash bug and new bridge bugs introduced
6817 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
6818 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
6819 addresses many more minor issues.
6821 o New directory authorities:
6822 - Set up ides (run by Mike Perry) as the third v3 directory authority.
6825 - Allow tunnelled directory connections to ask for an encrypted
6826 "begin_dir" connection or an anonymized "uses a full Tor circuit"
6827 connection independently. Now we can make anonymized begin_dir
6828 connections for (e.g.) more secure hidden service posting and
6830 - More progress on proposal 114: code from Karsten Loesing to
6831 implement new hidden service descriptor format.
6832 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
6833 accommodate the growing number of servers that use the default
6834 and are reaching it.
6835 - Directory authorities use a new formula for selecting which nodes
6836 to advertise as Guards: they must be in the top 7/8 in terms of
6837 how long we have known about them, and above the median of those
6838 nodes in terms of weighted fractional uptime.
6839 - Make "not enough dir info yet" warnings describe *why* Tor feels
6840 it doesn't have enough directory info yet.
6843 - Stop servers from crashing if they set a Family option (or
6844 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
6846 - Make bridge users work again -- the move to v3 directories in
6847 0.2.0.9-alpha had introduced a number of bugs that made bridges
6848 no longer work for clients.
6849 - When the clock jumps forward a lot, do not allow the bandwidth
6850 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
6852 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
6853 - When the consensus lists a router descriptor that we previously were
6854 mirroring, but that we considered non-canonical, reload the
6855 descriptor as canonical. This fixes bug 543 where Tor servers
6856 would start complaining after a few days that they don't have
6857 enough directory information to build a circuit.
6858 - Consider replacing the current consensus when certificates arrive
6859 that make the pending consensus valid. Previously, we were only
6860 considering replacement when the new certs _didn't_ help.
6861 - Fix an assert error on startup if we didn't already have the
6862 consensus and certs cached in our datadirectory: we were caching
6863 the consensus in consensus_waiting_for_certs but then free'ing it
6865 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
6866 Request) if we need more v3 certs but we've already got pending
6867 requests for all of them.
6868 - Correctly back off from failing certificate downloads. Fixes
6870 - Authorities don't vote on the Running flag if they have been running
6871 for less than 30 minutes themselves. Fixes bug 547, where a newly
6872 started authority would vote that everyone was down.
6875 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
6876 it, it had no AES, and it hasn't seen any security patches since
6880 - Clients now hold circuitless TLS connections open for 1.5 times
6881 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
6882 rebuild a new circuit over them within that timeframe. Previously,
6883 they held them open only for KeepalivePeriod (5 minutes).
6884 - Use "If-Modified-Since" to avoid retrieving consensus
6885 networkstatuses that we already have.
6886 - When we have no consensus, check FallbackNetworkstatusFile (defaults
6887 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
6888 we start knowing some directory caches.
6889 - When we receive a consensus from the future, warn about skew.
6890 - Improve skew reporting: try to give the user a better log message
6891 about how skewed they are, and how much this matters.
6892 - When we have a certificate for an authority, believe that
6893 certificate's claims about the authority's IP address.
6894 - New --quiet command-line option to suppress the default console log.
6895 Good in combination with --hash-password.
6896 - Authorities send back an X-Descriptor-Not-New header in response to
6897 an accepted-but-discarded descriptor upload. Partially implements
6899 - Make the log message for "tls error. breaking." more useful.
6900 - Better log messages about certificate downloads, to attempt to
6901 track down the second incarnation of bug 546.
6903 o Minor features (bridges):
6904 - If bridge users set UpdateBridgesFromAuthority, but the digest
6905 they ask for is a 404 from the bridge authority, they now fall
6906 back to trying the bridge directly.
6907 - Bridges now use begin_dir to publish their server descriptor to
6908 the bridge authority, even when they haven't set TunnelDirConns.
6910 o Minor features (controller):
6911 - When reporting clock skew, and we know that the clock is _at least
6912 as skewed_ as some value, but we don't know the actual value,
6913 report the value as a "minimum skew."
6916 - Update linux-tor-prio.sh script to allow QoS based on the uid of
6917 the Tor process. Patch from Marco Bonetti with tweaks from Mike
6921 - Refuse to start if both ORPort and UseBridges are set. Bugfix
6922 on 0.2.0.x, suggested by Matt Edman.
6923 - Don't stop fetching descriptors when FetchUselessDescriptors is
6924 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
6925 reported by tup and ioerror.
6926 - Better log message on vote from unknown authority.
6927 - Don't log "Launching 0 request for 0 router" message.
6929 o Minor bugfixes (memory leaks):
6930 - Stop leaking memory every time we parse a v3 certificate. Bugfix
6932 - Stop leaking memory every time we load a v3 certificate. Bugfix
6933 on 0.2.0.1-alpha. Fixes bug 536.
6934 - Stop leaking a cached networkstatus on exit. Bugfix on
6936 - Stop leaking voter information every time we free a consensus.
6937 Bugfix on 0.2.0.3-alpha.
6938 - Stop leaking signed data every time we check a voter signature.
6939 Bugfix on 0.2.0.3-alpha.
6940 - Stop leaking a signature every time we fail to parse a consensus or
6941 a vote. Bugfix on 0.2.0.3-alpha.
6942 - Stop leaking v2_download_status_map on shutdown. Bugfix on
6944 - Stop leaking conn->nickname every time we make a connection to a
6945 Tor relay without knowing its expected identity digest (e.g. when
6946 using bridges). Bugfix on 0.2.0.3-alpha.
6948 - Minor bugfixes (portability):
6949 - Run correctly on platforms where rlim_t is larger than unsigned
6950 long, and/or where the real limit for number of open files is
6951 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
6952 particular, these may be needed for OS X 10.5.
6955 Changes in version 0.1.2.18 - 2007-10-28
6956 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
6957 hidden service introduction that were causing huge delays, and a big
6958 bug that was causing some servers to disappear from the network status
6959 lists for a few hours each day.
6961 o Major bugfixes (crashes):
6962 - If a connection is shut down abruptly because of something that
6963 happened inside connection_flushed_some(), do not call
6964 connection_finished_flushing(). Should fix bug 451:
6965 "connection_stop_writing: Assertion conn->write_event failed"
6966 Bugfix on 0.1.2.7-alpha.
6967 - Fix possible segfaults in functions called from
6968 rend_process_relay_cell().
6970 o Major bugfixes (hidden services):
6971 - Hidden services were choosing introduction points uniquely by
6972 hexdigest, but when constructing the hidden service descriptor
6973 they merely wrote the (potentially ambiguous) nickname.
6974 - Clients now use the v2 intro format for hidden service
6975 connections: they specify their chosen rendezvous point by identity
6976 digest rather than by (potentially ambiguous) nickname. These
6977 changes could speed up hidden service connections dramatically.
6979 o Major bugfixes (other):
6980 - Stop publishing a new server descriptor just because we get a
6981 HUP signal. This led (in a roundabout way) to some servers getting
6982 dropped from the networkstatus lists for a few hours each day.
6983 - When looking for a circuit to cannibalize, consider family as well
6984 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
6985 circuit cannibalization).
6986 - When a router wasn't listed in a new networkstatus, we were leaving
6987 the flags for that router alone -- meaning it remained Named,
6988 Running, etc -- even though absence from the networkstatus means
6989 that it shouldn't be considered to exist at all anymore. Now we
6990 clear all the flags for routers that fall out of the networkstatus
6991 consensus. Fixes bug 529.
6994 - Don't try to access (or alter) the state file when running
6995 --list-fingerprint or --verify-config or --hash-password. Resolves
6997 - When generating information telling us how to extend to a given
6998 router, do not try to include the nickname if it is
6999 absent. Resolves bug 467.
7000 - Fix a user-triggerable segfault in expand_filename(). (There isn't
7001 a way to trigger this remotely.)
7002 - When sending a status event to the controller telling it that an
7003 OR address is reachable, set the port correctly. (Previously we
7004 were reporting the dir port.)
7005 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
7006 command. Bugfix on 0.1.2.17.
7007 - When loading bandwidth history, do not believe any information in
7008 the future. Fixes bug 434.
7009 - When loading entry guard information, do not believe any information
7011 - When we have our clock set far in the future and generate an
7012 onion key, then re-set our clock to be correct, we should not stop
7013 the onion key from getting rotated.
7014 - On some platforms, accept() can return a broken address. Detect
7015 this more quietly, and deal accordingly. Fixes bug 483.
7016 - It's not actually an error to find a non-pending entry in the DNS
7017 cache when canceling a pending resolve. Don't log unless stuff
7018 is fishy. Resolves bug 463.
7019 - Don't reset trusted dir server list when we set a configuration
7020 option. Patch from Robert Hogan.
7021 - Don't try to create the datadir when running --verify-config or
7022 --hash-password. Resolves bug 540.
7025 Changes in version 0.2.0.9-alpha - 2007-10-24
7026 This ninth development snapshot switches clients to the new v3 directory
7027 system; allows servers to be listed in the network status even when they
7028 have the same nickname as a registered server; and fixes many other
7029 bugs including a big one that was causing some servers to disappear
7030 from the network status lists for a few hours each day.
7032 o Major features (directory system):
7033 - Clients now download v3 consensus networkstatus documents instead
7034 of v2 networkstatus documents. Clients and caches now base their
7035 opinions about routers on these consensus documents. Clients only
7036 download router descriptors listed in the consensus.
7037 - Authorities now list servers who have the same nickname as
7038 a different named server, but list them with a new flag,
7039 "Unnamed". Now we can list servers that happen to pick the same
7040 nickname as a server that registered two years ago and then
7041 disappeared. Partially implements proposal 122.
7042 - If the consensus lists a router as "Unnamed", the name is assigned
7043 to a different router: do not identify the router by that name.
7044 Partially implements proposal 122.
7045 - Authorities can now come to a consensus on which method to use to
7046 compute the consensus. This gives us forward compatibility.
7049 - Stop publishing a new server descriptor just because we HUP or
7050 when we find our DirPort to be reachable but won't actually publish
7051 it. New descriptors without any real changes are dropped by the
7052 authorities, and can screw up our "publish every 18 hours" schedule.
7054 - When a router wasn't listed in a new networkstatus, we were leaving
7055 the flags for that router alone -- meaning it remained Named,
7056 Running, etc -- even though absence from the networkstatus means
7057 that it shouldn't be considered to exist at all anymore. Now we
7058 clear all the flags for routers that fall out of the networkstatus
7059 consensus. Fixes bug 529; bugfix on 0.1.2.x.
7060 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
7061 extrainfo documents and then discard them immediately for not
7062 matching the latest router. Bugfix on 0.2.0.1-alpha.
7064 o Minor features (v3 directory protocol):
7065 - Allow tor-gencert to generate a new certificate without replacing
7067 - Allow certificates to include an address.
7068 - When we change our directory-cache settings, reschedule all voting
7069 and download operations.
7070 - Reattempt certificate downloads immediately on failure, as long as
7071 we haven't failed a threshold number of times yet.
7072 - Delay retrying consensus downloads while we're downloading
7073 certificates to verify the one we just got. Also, count getting a
7074 consensus that we already have (or one that isn't valid) as a failure,
7075 and count failing to get the certificates after 20 minutes as a
7077 - Build circuits and download descriptors even if our consensus is a
7078 little expired. (This feature will go away once authorities are
7081 o Minor features (router descriptor cache):
7082 - If we find a cached-routers file that's been sitting around for more
7083 than 28 days unmodified, then most likely it's a leftover from
7084 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
7086 - When we (as a cache) download a descriptor because it was listed
7087 in a consensus, remember when the consensus was supposed to expire,
7088 and don't expire the descriptor until then.
7090 o Minor features (performance):
7091 - Call routerlist_remove_old_routers() much less often. This should
7092 speed startup, especially on directory caches.
7093 - Don't try to launch new descriptor downloads quite so often when we
7094 already have enough directory information to build circuits.
7095 - Base64 decoding was actually showing up on our profile when parsing
7096 the initial descriptor file; switch to an in-process all-at-once
7097 implementation that's about 3.5x times faster than calling out to
7100 o Minor features (compilation):
7101 - Detect non-ASCII platforms (if any still exist) and refuse to
7102 build there: some of our code assumes that 'A' is 65 and so on.
7104 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
7105 - Make the "next period" votes into "current period" votes immediately
7106 after publishing the consensus; avoid a heisenbug that made them
7107 stick around indefinitely.
7108 - When we discard a vote as a duplicate, do not report this as
7110 - Treat missing v3 keys or certificates as an error when running as a
7111 v3 directory authority.
7112 - When we're configured to be a v3 authority, but we're only listed
7113 as a non-v3 authority in our DirServer line for ourself, correct
7115 - If an authority doesn't have a qualified hostname, just put
7116 its address in the vote. This fixes the problem where we referred to
7117 "moria on moria:9031."
7118 - Distinguish between detached signatures for the wrong period, and
7119 detached signatures for a divergent vote.
7120 - Fix a small memory leak when computing a consensus.
7121 - When there's no concensus, we were forming a vote every 30
7122 minutes, but writing the "valid-after" line in our vote based
7123 on our configured V3AuthVotingInterval: so unless the intervals
7124 matched up, we immediately rejected our own vote because it didn't
7125 start at the voting interval that caused us to construct a vote.
7127 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
7128 - Delete unverified-consensus when the real consensus is set.
7129 - Consider retrying a consensus networkstatus fetch immediately
7130 after one fails: don't wait 60 seconds to notice.
7131 - When fetching a consensus as a cache, wait until a newer consensus
7132 should exist before trying to replace the current one.
7133 - Use a more forgiving schedule for retrying failed consensus
7134 downloads than for other types.
7136 o Minor bugfixes (other directory issues):
7137 - Correct the implementation of "download votes by digest." Bugfix on
7139 - Authorities no longer send back "400 you're unreachable please fix
7140 it" errors to Tor servers that aren't online all the time. We're
7141 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
7143 o Minor bugfixes (controller):
7144 - Don't reset trusted dir server list when we set a configuration
7145 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
7146 - Respond to INT and TERM SIGNAL commands before we execute the
7147 signal, in case the signal shuts us down. We had a patch in
7148 0.1.2.1-alpha that tried to do this by queueing the response on
7149 the connection's buffer before shutting down, but that really
7150 isn't the same thing at all. Bug located by Matt Edman.
7152 o Minor bugfixes (misc):
7153 - Correctly check for bad options to the "PublishServerDescriptor"
7154 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
7155 - Stop leaking memory on failing case of base32_decode, and make
7156 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
7157 - Don't try to download extrainfo documents when we're trying to
7158 fetch enough directory info to build a circuit: having enough
7159 info should get priority. Bugfix on 0.2.0.x.
7160 - Don't complain that "your server has not managed to confirm that its
7161 ports are reachable" if we haven't been able to build any circuits
7162 yet. Bug found by spending four hours without a v3 consensus. Bugfix
7164 - Detect the reason for failing to mmap a descriptor file we just
7165 wrote, and give a more useful log message. Fixes bug 533. Bugfix
7168 o Code simplifications and refactoring:
7169 - Remove support for the old bw_accounting file: we've been storing
7170 bandwidth accounting information in the state file since
7171 0.1.2.5-alpha. This may result in bandwidth accounting errors
7172 if you try to upgrade from 0.1.1.x or earlier, or if you try to
7173 downgrade to 0.1.1.x or earlier.
7174 - New convenience code to locate a file within the DataDirectory.
7175 - Move non-authority functionality out of dirvote.c.
7176 - Refactor the arguments for router_pick_{directory_|trusteddir}server
7177 so that they all take the same named flags.
7180 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
7181 Unix users an easy way to script their Tor process (e.g. by
7182 adjusting bandwidth based on the time of the day).
7185 Changes in version 0.2.0.8-alpha - 2007-10-12
7186 This eighth development snapshot fixes a crash bug that's been bothering
7187 us since February 2007, lets bridge authorities store a list of bridge
7188 descriptors they've seen, gets v3 directory voting closer to working,
7189 starts caching v3 directory consensus documents on directory mirrors,
7190 and fixes a variety of smaller issues including some minor memory leaks.
7192 o Major features (router descriptor cache):
7193 - Store routers in a file called cached-descriptors instead of in
7194 cached-routers. Initialize cached-descriptors from cached-routers
7195 if the old format is around. The new format allows us to store
7196 annotations along with descriptors.
7197 - Use annotations to record the time we received each descriptor, its
7198 source, and its purpose.
7199 - Disable the SETROUTERPURPOSE controller command: it is now
7201 - Controllers should now specify cache=no or cache=yes when using
7202 the +POSTDESCRIPTOR command.
7203 - Bridge authorities now write bridge descriptors to disk, meaning
7204 we can export them to other programs and begin distributing them
7207 o Major features (directory authorities):
7208 - When a v3 authority is missing votes or signatures, it now tries
7210 - Directory authorities track weighted fractional uptime as well as
7211 weighted mean-time-between failures. WFU is suitable for deciding
7212 whether a node is "usually up", while MTBF is suitable for deciding
7213 whether a node is "likely to stay up." We need both, because
7214 "usually up" is a good requirement for guards, while "likely to
7215 stay up" is a good requirement for long-lived connections.
7217 o Major features (v3 directory system):
7218 - Caches now download v3 network status documents as needed,
7219 and download the descriptors listed in them.
7220 - All hosts now attempt to download and keep fresh v3 authority
7221 certificates, and re-attempt after failures.
7222 - More internal-consistency checks for vote parsing.
7224 o Major bugfixes (crashes):
7225 - If a connection is shut down abruptly because of something that
7226 happened inside connection_flushed_some(), do not call
7227 connection_finished_flushing(). Should fix bug 451. Bugfix on
7230 o Major bugfixes (performance):
7231 - Fix really bad O(n^2) performance when parsing a long list of
7232 routers: Instead of searching the entire list for an "extra-info "
7233 string which usually wasn't there, once for every routerinfo
7234 we read, just scan lines forward until we find one we like.
7236 - When we add data to a write buffer in response to the data on that
7237 write buffer getting low because of a flush, do not consider the
7238 newly added data as a candidate for immediate flushing, but rather
7239 make it wait until the next round of writing. Otherwise, we flush
7240 and refill recursively, and a single greedy TLS connection can
7241 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
7243 o Minor features (v3 authority system):
7244 - Add more ways for tools to download the votes that lead to the
7246 - Send a 503 when low on bandwidth and a vote, consensus, or
7247 certificate is requested.
7248 - If-modified-since is now implemented properly for all kinds of
7249 certificate requests.
7251 o Minor bugfixes (network statuses):
7252 - Tweak the implementation of proposal 109 slightly: allow at most
7253 two Tor servers on the same IP address, except if it's the location
7254 of a directory authority, in which case allow five. Bugfix on
7257 o Minor bugfixes (controller):
7258 - When sending a status event to the controller telling it that an
7259 OR address is reachable, set the port correctly. (Previously we
7260 were reporting the dir port.) Bugfix on 0.1.2.x.
7262 o Minor bugfixes (v3 directory system):
7263 - Fix logic to look up a cert by its signing key digest. Bugfix on
7265 - Only change the reply to a vote to "OK" if it's not already
7266 set. This gets rid of annoying "400 OK" log messages, which may
7267 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
7268 - When we get a valid consensus, recompute the voting schedule.
7269 - Base the valid-after time of a vote on the consensus voting
7270 schedule, not on our preferred schedule.
7271 - Make the return values and messages from signature uploads and
7272 downloads more sensible.
7273 - Fix a memory leak when serving votes and consensus documents, and
7274 another when serving certificates.
7276 o Minor bugfixes (performance):
7277 - Use a slightly simpler string hashing algorithm (copying Python's
7278 instead of Java's) and optimize our digest hashing algorithm to take
7279 advantage of 64-bit platforms and to remove some possibly-costly
7281 - Fix a minor memory leak whenever we parse guards from our state
7282 file. Bugfix on 0.2.0.7-alpha.
7283 - Fix a minor memory leak whenever we write out a file. Bugfix on
7285 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
7286 command. Bugfix on 0.2.0.5-alpha.
7288 o Minor bugfixes (portability):
7289 - On some platforms, accept() can return a broken address. Detect
7290 this more quietly, and deal accordingly. Fixes bug 483.
7291 - Stop calling tor_strlower() on uninitialized memory in some cases.
7292 Bugfix in 0.2.0.7-alpha.
7294 o Minor bugfixes (usability):
7295 - Treat some 403 responses from directory servers as INFO rather than
7296 WARN-severity events.
7297 - It's not actually an error to find a non-pending entry in the DNS
7298 cache when canceling a pending resolve. Don't log unless stuff is
7299 fishy. Resolves bug 463.
7301 o Minor bugfixes (anonymity):
7302 - Never report that we've used more bandwidth than we're willing to
7303 relay: it leaks how much non-relay traffic we're using. Resolves
7305 - When looking for a circuit to cannibalize, consider family as well
7306 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
7307 circuit cannibalization).
7309 o Code simplifications and refactoring:
7310 - Make a bunch of functions static. Remove some dead code.
7311 - Pull out about a third of the really big routerlist.c; put it in a
7312 new module, networkstatus.c.
7313 - Merge the extra fields in local_routerstatus_t back into
7314 routerstatus_t: we used to need one routerstatus_t for each
7315 authority's opinion, plus a local_routerstatus_t for the locally
7316 computed consensus opinion. To save space, we put the locally
7317 modified fields into local_routerstatus_t, and only the common
7318 stuff into routerstatus_t. But once v3 directories are in use,
7319 clients and caches will no longer need to hold authority opinions;
7320 thus, the rationale for keeping the types separate is now gone.
7321 - Make the code used to reschedule and reattempt downloads more
7323 - Turn all 'Are we a directory server/mirror?' logic into a call to
7325 - Remove the code to generate the oldest (v1) directory format.
7326 The code has been disabled since 0.2.0.5-alpha.
7329 Changes in version 0.2.0.7-alpha - 2007-09-21
7330 This seventh development snapshot makes bridges work again, makes bridge
7331 authorities work for the first time, fixes two huge performance flaws
7332 in hidden services, and fixes a variety of minor issues.
7334 o New directory authorities:
7335 - Set up moria1 and tor26 as the first v3 directory authorities. See
7336 doc/spec/dir-spec.txt for details on the new directory design.
7338 o Major bugfixes (crashes):
7339 - Fix possible segfaults in functions called from
7340 rend_process_relay_cell(). Bugfix on 0.1.2.x.
7342 o Major bugfixes (bridges):
7343 - Fix a bug that made servers send a "404 Not found" in response to
7344 attempts to fetch their server descriptor. This caused Tor servers
7345 to take many minutes to establish reachability for their DirPort,
7346 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
7347 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
7348 users configure that and specify a bridge with an identity
7349 fingerprint, now they will lookup the bridge descriptor at the
7350 default bridge authority via a one-hop tunnel, but once circuits
7351 are established they will switch to a three-hop tunnel for later
7352 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
7354 o Major bugfixes (hidden services):
7355 - Hidden services were choosing introduction points uniquely by
7356 hexdigest, but when constructing the hidden service descriptor
7357 they merely wrote the (potentially ambiguous) nickname.
7358 - Clients now use the v2 intro format for hidden service
7359 connections: they specify their chosen rendezvous point by identity
7360 digest rather than by (potentially ambiguous) nickname. Both
7361 are bugfixes on 0.1.2.x, and they could speed up hidden service
7362 connections dramatically. Thanks to Karsten Loesing.
7364 o Minor features (security):
7365 - As a client, do not believe any server that tells us that an
7366 address maps to an internal address space.
7367 - Make it possible to enable HashedControlPassword and
7368 CookieAuthentication at the same time.
7370 o Minor features (guard nodes):
7371 - Tag every guard node in our state file with the version that
7372 we believe added it, or with our own version if we add it. This way,
7373 if a user temporarily runs an old version of Tor and then switches
7374 back to a new one, she doesn't automatically lose her guards.
7376 o Minor features (speed):
7377 - When implementing AES counter mode, update only the portions of the
7378 counter buffer that need to change, and don't keep separate
7379 network-order and host-order counters when they are the same (i.e.,
7380 on big-endian hosts.)
7382 o Minor features (controller):
7383 - Accept LF instead of CRLF on controller, since some software has a
7384 hard time generating real Internet newlines.
7385 - Add GETINFO values for the server status events
7386 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
7390 - Routers no longer include bandwidth-history lines in their
7391 descriptors; this information is already available in extra-info
7392 documents, and including it in router descriptors took up 60%
7393 (!) of compressed router descriptor downloads. Completes
7394 implementation of proposal 104.
7395 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
7396 and TorControl.py, as they use the old v0 controller protocol,
7397 and are obsoleted by TorFlow anyway.
7398 - Drop support for v1 rendezvous descriptors, since we never used
7399 them anyway, and the code has probably rotted by now. Based on
7400 patch from Karsten Loesing.
7401 - On OSX, stop warning the user that kqueue support in libevent is
7402 "experimental", since it seems to have worked fine for ages.
7405 - When generating information telling us how to extend to a given
7406 router, do not try to include the nickname if it is absent. Fixes
7407 bug 467. Bugfix on 0.2.0.3-alpha.
7408 - Fix a user-triggerable (but not remotely-triggerable) segfault
7409 in expand_filename(). Bugfix on 0.1.2.x.
7410 - Fix a memory leak when freeing incomplete requests from DNSPort.
7411 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
7412 - Don't try to access (or alter) the state file when running
7413 --list-fingerprint or --verify-config or --hash-password. (Resolves
7414 bug 499.) Bugfix on 0.1.2.x.
7415 - Servers used to decline to publish their DirPort if their
7416 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
7417 were below a threshold. Now they only look at BandwidthRate and
7418 RelayBandwidthRate. Bugfix on 0.1.2.x.
7419 - Remove an optimization in the AES counter-mode code that assumed
7420 that the counter never exceeded 2^68. When the counter can be set
7421 arbitrarily as an IV (as it is by Karsten's new hidden services
7422 code), this assumption no longer holds. Bugfix on 0.1.2.x.
7423 - Resume listing "AUTHORITY" flag for authorities in network status.
7424 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
7426 o Code simplifications and refactoring:
7427 - Revamp file-writing logic so we don't need to have the entire
7428 contents of a file in memory at once before we write to disk. Tor,
7430 - Turn "descriptor store" into a full-fledged type.
7431 - Move all NT services code into a separate source file.
7432 - Unify all code that computes medians, percentile elements, etc.
7433 - Get rid of a needless malloc when parsing address policies.
7436 Changes in version 0.1.2.17 - 2007-08-30
7437 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
7438 X bundles. Vidalia 0.0.14 makes authentication required for the
7439 ControlPort in the default configuration, which addresses important
7440 security risks. Everybody who uses Vidalia (or another controller)
7443 In addition, this Tor update fixes major load balancing problems with
7444 path selection, which should speed things up a lot once many people
7447 o Major bugfixes (security):
7448 - We removed support for the old (v0) control protocol. It has been
7449 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
7450 become more of a headache than it's worth.
7452 o Major bugfixes (load balancing):
7453 - When choosing nodes for non-guard positions, weight guards
7454 proportionally less, since they already have enough load. Patch
7456 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
7457 will allow fast Tor servers to get more attention.
7458 - When we're upgrading from an old Tor version, forget our current
7459 guards and pick new ones according to the new weightings. These
7460 three load balancing patches could raise effective network capacity
7461 by a factor of four. Thanks to Mike Perry for measurements.
7463 o Major bugfixes (stream expiration):
7464 - Expire not-yet-successful application streams in all cases if
7465 they've been around longer than SocksTimeout. Right now there are
7466 some cases where the stream will live forever, demanding a new
7467 circuit every 15 seconds. Fixes bug 454; reported by lodger.
7469 o Minor features (controller):
7470 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
7471 is valid before any authentication has been received. It tells
7472 a controller what kind of authentication is expected, and what
7473 protocol is spoken. Implements proposal 119.
7475 o Minor bugfixes (performance):
7476 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
7477 greatly speeding up loading cached-routers from disk on startup.
7478 - Disable sentinel-based debugging for buffer code: we squashed all
7479 the bugs that this was supposed to detect a long time ago, and now
7480 its only effect is to change our buffer sizes from nice powers of
7481 two (which platform mallocs tend to like) to values slightly over
7482 powers of two (which make some platform mallocs sad).
7484 o Minor bugfixes (misc):
7485 - If exit bandwidth ever exceeds one third of total bandwidth, then
7486 use the correct formula to weight exit nodes when choosing paths.
7487 Based on patch from Mike Perry.
7488 - Choose perfectly fairly among routers when choosing by bandwidth and
7489 weighting by fraction of bandwidth provided by exits. Previously, we
7490 would choose with only approximate fairness, and correct ourselves
7491 if we ran off the end of the list.
7492 - If we require CookieAuthentication but we fail to write the
7493 cookie file, we would warn but not exit, and end up in a state
7494 where no controller could authenticate. Now we exit.
7495 - If we require CookieAuthentication, stop generating a new cookie
7496 every time we change any piece of our config.
7497 - Refuse to start with certain directory authority keys, and
7498 encourage people using them to stop.
7499 - Terminate multi-line control events properly. Original patch
7501 - Fix a minor memory leak when we fail to find enough suitable
7502 servers to choose a circuit.
7503 - Stop leaking part of the descriptor when we run into a particularly
7504 unparseable piece of it.
7507 Changes in version 0.2.0.6-alpha - 2007-08-26
7508 This sixth development snapshot features a new Vidalia version in the
7509 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
7510 the ControlPort in the default configuration, which addresses important
7513 In addition, this snapshot fixes major load balancing problems
7514 with path selection, which should speed things up a lot once many
7515 people have upgraded. The directory authorities also use a new
7516 mean-time-between-failure approach to tracking which servers are stable,
7517 rather than just looking at the most recent uptime.
7519 o New directory authorities:
7520 - Set up Tonga as the default bridge directory authority.
7523 - Directory authorities now track servers by weighted
7524 mean-times-between-failures. When we have 4 or more days of data,
7525 use measured MTBF rather than declared uptime to decide whether
7526 to call a router Stable. Implements proposal 108.
7528 o Major bugfixes (load balancing):
7529 - When choosing nodes for non-guard positions, weight guards
7530 proportionally less, since they already have enough load. Patch
7532 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
7533 will allow fast Tor servers to get more attention.
7534 - When we're upgrading from an old Tor version, forget our current
7535 guards and pick new ones according to the new weightings. These
7536 three load balancing patches could raise effective network capacity
7537 by a factor of four. Thanks to Mike Perry for measurements.
7539 o Major bugfixes (descriptor parsing):
7540 - Handle unexpected whitespace better in malformed descriptors. Bug
7541 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
7544 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
7545 GETINFO for Torstat to use until it can switch to using extrainfos.
7546 - Optionally (if built with -DEXPORTMALLINFO) export the output
7547 of mallinfo via http, as tor/mallinfo.txt. Only accessible
7551 - Do not intermix bridge routers with controller-added
7552 routers. (Bugfix on 0.2.0.x)
7553 - Do not fail with an assert when accept() returns an unexpected
7554 address family. Addresses but does not wholly fix bug 483. (Bugfix
7556 - Let directory authorities startup even when they can't generate
7557 a descriptor immediately, e.g. because they don't know their
7559 - Stop putting the authentication cookie in a file called "0"
7560 in your working directory if you don't specify anything for the
7561 new CookieAuthFile option. Reported by Matt Edman.
7562 - Make it possible to read the PROTOCOLINFO response in a way that
7563 conforms to our control-spec. Reported by Matt Edman.
7564 - Fix a minor memory leak when we fail to find enough suitable
7565 servers to choose a circuit. Bugfix on 0.1.2.x.
7566 - Stop leaking part of the descriptor when we run into a particularly
7567 unparseable piece of it. Bugfix on 0.1.2.x.
7568 - Unmap the extrainfo cache file on exit.
7571 Changes in version 0.2.0.5-alpha - 2007-08-19
7572 This fifth development snapshot fixes compilation on Windows again;
7573 fixes an obnoxious client-side bug that slowed things down and put
7574 extra load on the network; gets us closer to using the v3 directory
7575 voting scheme; makes it easier for Tor controllers to use cookie-based
7576 authentication; and fixes a variety of other bugs.
7579 - Version 1 directories are no longer generated in full. Instead,
7580 authorities generate and serve "stub" v1 directories that list
7581 no servers. This will stop Tor versions 0.1.0.x and earlier from
7582 working, but (for security reasons) nobody should be running those
7585 o Major bugfixes (compilation, 0.2.0.x):
7586 - Try to fix Win32 compilation again: improve checking for IPv6 types.
7587 - Try to fix MSVC compilation: build correctly on platforms that do
7588 not define s6_addr16 or s6_addr32.
7589 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
7592 o Major bugfixes (stream expiration):
7593 - Expire not-yet-successful application streams in all cases if
7594 they've been around longer than SocksTimeout. Right now there are
7595 some cases where the stream will live forever, demanding a new
7596 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
7599 o Minor features (directory servers):
7600 - When somebody requests a list of statuses or servers, and we have
7601 none of those, return a 404 rather than an empty 200.
7603 o Minor features (directory voting):
7604 - Store v3 consensus status consensuses on disk, and reload them
7607 o Minor features (security):
7608 - Warn about unsafe ControlPort configurations.
7609 - Refuse to start with certain directory authority keys, and
7610 encourage people using them to stop.
7612 o Minor features (controller):
7613 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
7614 is valid before any authentication has been received. It tells
7615 a controller what kind of authentication is expected, and what
7616 protocol is spoken. Implements proposal 119.
7617 - New config option CookieAuthFile to choose a new location for the
7618 cookie authentication file, and config option
7619 CookieAuthFileGroupReadable to make it group-readable.
7621 o Minor features (unit testing):
7622 - Add command-line arguments to unit-test executable so that we can
7623 invoke any chosen test from the command line rather than having
7624 to run the whole test suite at once; and so that we can turn on
7625 logging for the unit tests.
7627 o Minor bugfixes (on 0.1.2.x):
7628 - If we require CookieAuthentication but we fail to write the
7629 cookie file, we would warn but not exit, and end up in a state
7630 where no controller could authenticate. Now we exit.
7631 - If we require CookieAuthentication, stop generating a new cookie
7632 every time we change any piece of our config.
7633 - When loading bandwidth history, do not believe any information in
7634 the future. Fixes bug 434.
7635 - When loading entry guard information, do not believe any information
7637 - When we have our clock set far in the future and generate an
7638 onion key, then re-set our clock to be correct, we should not stop
7639 the onion key from getting rotated.
7640 - Clean up torrc sample config file.
7641 - Do not automatically run configure from autogen.sh. This
7642 non-standard behavior tended to annoy people who have built other
7645 o Minor bugfixes (on 0.2.0.x):
7646 - Fix a bug with AutomapHostsOnResolve that would always cause
7647 the second request to fail. Bug reported by Kate. Bugfix on
7649 - Fix a bug in ADDRMAP controller replies that would sometimes
7650 try to print a NULL. Patch from tup.
7651 - Read v3 directory authority keys from the right location.
7652 - Numerous bugfixes to directory voting code.
7655 Changes in version 0.1.2.16 - 2007-08-01
7656 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
7657 remote attacker in certain situations to rewrite the user's torrc
7658 configuration file. This can completely compromise anonymity of users
7659 in most configurations, including those running the Vidalia bundles,
7660 TorK, etc. Or worse.
7662 o Major security fixes:
7663 - Close immediately after missing authentication on control port;
7664 do not allow multiple authentication attempts.
7667 Changes in version 0.2.0.4-alpha - 2007-08-01
7668 This fourth development snapshot fixes a critical security vulnerability
7669 for most users, specifically those running Vidalia, TorK, etc. Everybody
7670 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
7672 o Major security fixes:
7673 - Close immediately after missing authentication on control port;
7674 do not allow multiple authentication attempts.
7676 o Major bugfixes (compilation):
7677 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
7680 o Minor features (performance):
7681 - Be even more aggressive about releasing RAM from small
7682 empty buffers. Thanks to our free-list code, this shouldn't be too
7683 performance-intensive.
7684 - Disable sentinel-based debugging for buffer code: we squashed all
7685 the bugs that this was supposed to detect a long time ago, and
7686 now its only effect is to change our buffer sizes from nice
7687 powers of two (which platform mallocs tend to like) to values
7688 slightly over powers of two (which make some platform mallocs sad).
7689 - Log malloc statistics from mallinfo() on platforms where it
7693 Changes in version 0.2.0.3-alpha - 2007-07-29
7694 This third development snapshot introduces new experimental
7695 blocking-resistance features and a preliminary version of the v3
7696 directory voting design, and includes many other smaller features
7700 - The first pieces of our "bridge" design for blocking-resistance
7701 are implemented. People can run bridge directory authorities;
7702 people can run bridges; and people can configure their Tor clients
7703 with a set of bridges to use as the first hop into the Tor network.
7704 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
7706 - Create listener connections before we setuid to the configured
7707 User and Group. Now non-Windows users can choose port values
7708 under 1024, start Tor as root, and have Tor bind those ports
7709 before it changes to another UID. (Windows users could already
7711 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
7712 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
7713 on "vserver" accounts. (Patch from coderman.)
7714 - Be even more aggressive about separating local traffic from relayed
7715 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
7717 o Major features (experimental):
7718 - First cut of code for "v3 dir voting": directory authorities will
7719 vote on a common network status document rather than each publishing
7720 their own opinion. This code needs more testing and more corner-case
7721 handling before it's ready for use.
7724 - Directory authorities now call routers Fast if their bandwidth is
7725 at least 100KB/s, and consider their bandwidth adequate to be a
7726 Guard if it is at least 250KB/s, no matter the medians. This fix
7727 complements proposal 107. [Bugfix on 0.1.2.x]
7728 - Directory authorities now never mark more than 3 servers per IP as
7729 Valid and Running. (Implements proposal 109, by Kevin Bauer and
7731 - Minor change to organizationName and commonName generation
7732 procedures in TLS certificates during Tor handshakes, to invalidate
7733 some earlier censorware approaches. This is not a long-term
7734 solution, but applying it will give us a bit of time to look into
7735 the epidemiology of countermeasures as they spread.
7737 o Major bugfixes (directory):
7738 - Rewrite directory tokenization code to never run off the end of
7739 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
7741 o Minor features (controller):
7742 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
7743 match requests to applications. (Patch from Robert Hogan.)
7744 - Report address and port correctly on connections to DNSPort. (Patch
7746 - Add a RESOLVE command to launch hostname lookups. (Original patch
7748 - Add GETINFO status/enough-dir-info to let controllers tell whether
7749 Tor has downloaded sufficient directory information. (Patch
7751 - You can now use the ControlSocket option to tell Tor to listen for
7752 controller connections on Unix domain sockets on systems that
7753 support them. (Patch from Peter Palfrader.)
7754 - STREAM NEW events are generated for DNSPort requests and for
7755 tunneled directory connections. (Patch from Robert Hogan.)
7756 - New "GETINFO address-mappings/*" command to get address mappings
7757 with expiry information. "addr-mappings/*" is now deprecated.
7760 o Minor features (misc):
7761 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
7763 - The tor-gencert tool for v3 directory authorities now creates all
7764 files as readable to the file creator only, and write-protects
7765 the authority identity key.
7766 - When dumping memory usage, list bytes used in buffer memory
7768 - When running with dmalloc, dump more stats on hup and on exit.
7769 - Directory authorities now fail quickly and (relatively) harmlessly
7770 if they generate a network status document that is somehow
7773 o Traffic load balancing improvements:
7774 - If exit bandwidth ever exceeds one third of total bandwidth, then
7775 use the correct formula to weight exit nodes when choosing paths.
7776 (Based on patch from Mike Perry.)
7777 - Choose perfectly fairly among routers when choosing by bandwidth and
7778 weighting by fraction of bandwidth provided by exits. Previously, we
7779 would choose with only approximate fairness, and correct ourselves
7780 if we ran off the end of the list. [Bugfix on 0.1.2.x]
7782 o Performance improvements:
7783 - Be more aggressive with freeing buffer RAM or putting it on the
7785 - Use Critical Sections rather than Mutexes for synchronizing threads
7786 on win32; Mutexes are heavier-weight, and designed for synchronizing
7789 o Deprecated and removed features:
7790 - RedirectExits is now deprecated.
7791 - Stop allowing address masks that do not correspond to bit prefixes.
7792 We have warned about these for a really long time; now it's time
7793 to reject them. (Patch from croup.)
7795 o Minor bugfixes (directory):
7796 - Fix another crash bug related to extra-info caching. (Bug found by
7797 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
7798 - Directories no longer return a "304 not modified" when they don't
7799 have the networkstatus the client asked for. Also fix a memory
7800 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
7801 - We had accidentally labelled 0.1.2.x directory servers as not
7802 suitable for begin_dir requests, and had labelled no directory
7803 servers as suitable for uploading extra-info documents. [Bugfix
7806 o Minor bugfixes (dns):
7807 - Fix a crash when DNSPort is set more than once. (Patch from Robert
7808 Hogan.) [Bugfix on 0.2.0.2-alpha]
7809 - Add DNSPort connections to the global connection list, so that we
7810 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
7812 - Fix a dangling reference that could lead to a crash when DNSPort is
7813 changed or closed (Patch from Robert Hogan.) [Bugfix on
7816 o Minor bugfixes (controller):
7817 - Provide DNS expiry times in GMT, not in local time. For backward
7818 compatibility, ADDRMAP events only provide GMT expiry in an extended
7819 field. "GETINFO address-mappings" always does the right thing.
7820 - Use CRLF line endings properly in NS events.
7821 - Terminate multi-line control events properly. (Original patch
7822 from tup.) [Bugfix on 0.1.2.x-alpha]
7823 - Do not include spaces in SOURCE_ADDR fields in STREAM
7824 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
7827 Changes in version 0.1.2.15 - 2007-07-17
7828 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
7829 problems, fixes compilation on BSD, and fixes a variety of other
7830 bugs. Everybody should upgrade.
7832 o Major bugfixes (compilation):
7833 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
7835 o Major bugfixes (crashes):
7836 - Try even harder not to dereference the first character after
7837 an mmap(). Reported by lodger.
7838 - Fix a crash bug in directory authorities when we re-number the
7839 routerlist while inserting a new router.
7840 - When the cached-routers file is an even multiple of the page size,
7841 don't run off the end and crash. (Fixes bug 455; based on idea
7843 - Fix eventdns.c behavior on Solaris: It is critical to include
7844 orconfig.h _before_ sys/types.h, so that we can get the expected
7845 definition of _FILE_OFFSET_BITS.
7847 o Major bugfixes (security):
7848 - Fix a possible buffer overrun when using BSD natd support. Bug
7850 - When sending destroy cells from a circuit's origin, don't include
7851 the reason for tearing down the circuit. The spec says we didn't,
7852 and now we actually don't. Reported by lodger.
7853 - Keep streamids from different exits on a circuit separate. This
7854 bug may have allowed other routers on a given circuit to inject
7855 cells into streams. Reported by lodger; fixes bug 446.
7856 - If there's a never-before-connected-to guard node in our list,
7857 never choose any guards past it. This way we don't expand our
7858 guard list unless we need to.
7860 o Minor bugfixes (guard nodes):
7861 - Weight guard selection by bandwidth, so that low-bandwidth nodes
7862 don't get overused as guards.
7864 o Minor bugfixes (directory):
7865 - Correctly count the number of authorities that recommend each
7866 version. Previously, we were under-counting by 1.
7867 - Fix a potential crash bug when we load many server descriptors at
7868 once and some of them make others of them obsolete. Fixes bug 458.
7870 o Minor bugfixes (hidden services):
7871 - Stop tearing down the whole circuit when the user asks for a
7872 connection to a port that the hidden service didn't configure.
7875 o Minor bugfixes (misc):
7876 - On Windows, we were preventing other processes from reading
7877 cached-routers while Tor was running. Reported by janbar.
7878 - Fix a possible (but very unlikely) bug in picking routers by
7879 bandwidth. Add a log message to confirm that it is in fact
7880 unlikely. Patch from lodger.
7881 - Backport a couple of memory leak fixes.
7882 - Backport miscellaneous cosmetic bugfixes.
7885 Changes in version 0.2.0.2-alpha - 2007-06-02
7886 o Major bugfixes on 0.2.0.1-alpha:
7887 - Fix an assertion failure related to servers without extra-info digests.
7888 Resolves bugs 441 and 442.
7890 o Minor features (directory):
7891 - Support "If-Modified-Since" when answering HTTP requests for
7892 directories, running-routers documents, and network-status documents.
7893 (There's no need to support it for router descriptors, since those
7894 are downloaded by descriptor digest.)
7896 o Minor build issues:
7897 - Clear up some MIPSPro compiler warnings.
7898 - When building from a tarball on a machine that happens to have SVK
7899 installed, report the micro-revision as whatever version existed
7900 in the tarball, not as "x".
7903 Changes in version 0.2.0.1-alpha - 2007-06-01
7904 This early development snapshot provides new features for people running
7905 Tor as both a client and a server (check out the new RelayBandwidth
7906 config options); lets Tor run as a DNS proxy; and generally moves us
7907 forward on a lot of fronts.
7909 o Major features, server usability:
7910 - New config options RelayBandwidthRate and RelayBandwidthBurst:
7911 a separate set of token buckets for relayed traffic. Right now
7912 relayed traffic is defined as answers to directory requests, and
7913 OR connections that don't have any local circuits on them.
7915 o Major features, client usability:
7916 - A client-side DNS proxy feature to replace the need for
7917 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
7918 for DNS requests on port 9999, use the Tor network to resolve them
7919 anonymously, and send the reply back like a regular DNS server.
7920 The code still only implements a subset of DNS.
7921 - Make PreferTunneledDirConns and TunnelDirConns work even when
7922 we have no cached directory info. This means Tor clients can now
7923 do all of their connections protected by TLS.
7925 o Major features, performance and efficiency:
7926 - Directory authorities accept and serve "extra info" documents for
7927 routers. These documents contain fields from router descriptors
7928 that aren't usually needed, and that use a lot of excess
7929 bandwidth. Once these fields are removed from router descriptors,
7930 the bandwidth savings should be about 60%. [Partially implements
7932 - Servers upload extra-info documents to any authority that accepts
7933 them. Authorities (and caches that have been configured to download
7934 extra-info documents) download them as needed. [Partially implements
7936 - Change the way that Tor buffers data that it is waiting to write.
7937 Instead of queueing data cells in an enormous ring buffer for each
7938 client->OR or OR->OR connection, we now queue cells on a separate
7939 queue for each circuit. This lets us use less slack memory, and
7940 will eventually let us be smarter about prioritizing different kinds
7942 - Use memory pools to allocate cells with better speed and memory
7943 efficiency, especially on platforms where malloc() is inefficient.
7944 - Stop reading on edge connections when their corresponding circuit
7945 buffers are full; start again as the circuits empty out.
7947 o Major features, other:
7948 - Add an HSAuthorityRecordStats option that hidden service authorities
7949 can use to track statistics of overall hidden service usage without
7950 logging information that would be very useful to an attacker.
7951 - Start work implementing multi-level keys for directory authorities:
7952 Add a standalone tool to generate key certificates. (Proposal 103.)
7955 - Directory authorities now call routers Stable if they have an
7956 uptime of at least 30 days, even if that's not the median uptime
7957 in the network. Implements proposal 107, suggested by Kevin Bauer
7960 o Minor fixes (resource management):
7961 - Count the number of open sockets separately from the number
7962 of active connection_t objects. This will let us avoid underusing
7963 our allocated connection limit.
7964 - We no longer use socket pairs to link an edge connection to an
7965 anonymous directory connection or a DirPort test connection.
7966 Instead, we track the link internally and transfer the data
7967 in-process. This saves two sockets per "linked" connection (at the
7968 client and at the server), and avoids the nasty Windows socketpair()
7970 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
7971 for every single inactive connection_t. Free items from the
7972 4k/16k-buffer free lists when they haven't been used for a while.
7974 o Minor features (build):
7975 - Make autoconf search for libevent, openssl, and zlib consistently.
7976 - Update deprecated macros in configure.in.
7977 - When warning about missing headers, tell the user to let us
7978 know if the compile succeeds anyway, so we can downgrade the
7980 - Include the current subversion revision as part of the version
7981 string: either fetch it directly if we're in an SVN checkout, do
7982 some magic to guess it if we're in an SVK checkout, or use
7983 the last-detected version if we're building from a .tar.gz.
7984 Use this version consistently in log messages.
7986 o Minor features (logging):
7987 - Always prepend "Bug: " to any log message about a bug.
7988 - Put a platform string (e.g. "Linux i686") in the startup log
7989 message, so when people paste just their logs, we know if it's
7990 OpenBSD or Windows or what.
7991 - When logging memory usage, break down memory used in buffers by
7994 o Minor features (directory system):
7995 - New config option V2AuthoritativeDirectory that all directory
7996 authorities should set. This will let future authorities choose
7997 not to serve V2 directory information.
7998 - Directory authorities allow multiple router descriptors and/or extra
7999 info documents to be uploaded in a single go. This will make
8000 implementing proposal 104 simpler.
8002 o Minor features (controller):
8003 - Add a new config option __DisablePredictedCircuits designed for
8004 use by the controller, when we don't want Tor to build any circuits
8006 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
8007 so we can exit from the middle of the circuit.
8008 - Implement "getinfo status/circuit-established".
8009 - Implement "getinfo status/version/..." so a controller can tell
8010 whether the current version is recommended, and whether any versions
8011 are good, and how many authorities agree. (Patch from shibz.)
8013 o Minor features (hidden services):
8014 - Allow multiple HiddenServicePort directives with the same virtual
8015 port; when they occur, the user is sent round-robin to one
8016 of the target ports chosen at random. Partially fixes bug 393 by
8017 adding limited ad-hoc round-robining.
8019 o Minor features (other):
8021 - Add a new AutomapHostsOnResolve option: when it is enabled, any
8022 resolve request for hosts matching a given pattern causes Tor to
8023 generate an internal virtual address mapping for that host. This
8024 allows DNSPort to work sensibly with hidden service users. By
8025 default, .exit and .onion addresses are remapped; the list of
8026 patterns can be reconfigured with AutomapHostsSuffixes.
8027 - Add an "-F" option to tor-resolve to force a resolve for a .onion
8028 address. Thanks to the AutomapHostsOnResolve option, this is no
8029 longer a completely silly thing to do.
8030 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
8031 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
8032 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
8033 minus 1 byte: the actual maximum declared bandwidth.
8036 - Removed support for the old binary "version 0" controller protocol.
8037 This has been deprecated since 0.1.1, and warnings have been issued
8038 since 0.1.2. When we encounter a v0 control message, we now send
8039 back an error and close the connection.
8040 - Remove the old "dns worker" server DNS code: it hasn't been default
8041 since 0.1.2.2-alpha, and all the servers seem to be using the new
8044 o Minor bugfixes (portability):
8045 - Even though Windows is equally happy with / and \ as path separators,
8046 try to use \ consistently on Windows and / consistently on Unix: it
8047 makes the log messages nicer.
8048 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
8049 - Read resolv.conf files correctly on platforms where read() returns
8050 partial results on small file reads.
8052 o Minor bugfixes (directory):
8053 - Correctly enforce that elements of directory objects do not appear
8054 more often than they are allowed to appear.
8055 - When we are reporting the DirServer line we just parsed, we were
8056 logging the second stanza of the key fingerprint, not the first.
8058 o Minor bugfixes (logging):
8059 - When we hit an EOF on a log (probably because we're shutting down),
8060 don't try to remove the log from the list: just mark it as
8061 unusable. (Bulletproofs against bug 222.)
8063 o Minor bugfixes (other):
8064 - In the exitlist script, only consider the most recently published
8065 server descriptor for each server. Also, when the user requests
8066 a list of servers that _reject_ connections to a given address,
8067 explicitly exclude the IPs that also have servers that accept
8068 connections to that address. (Resolves bug 405.)
8069 - Stop allowing hibernating servers to be "stable" or "fast".
8070 - On Windows, we were preventing other processes from reading
8071 cached-routers while Tor was running. (Reported by janbar)
8072 - Make the NodeFamilies config option work. (Reported by
8073 lodger -- it has never actually worked, even though we added it
8075 - Check return values from pthread_mutex functions.
8076 - Don't save non-general-purpose router descriptors to the disk cache,
8077 because we have no way of remembering what their purpose was when
8079 - Add even more asserts to hunt down bug 417.
8080 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
8081 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
8082 Add a log message to confirm that it is in fact unlikely.
8084 o Minor bugfixes (controller):
8085 - Make 'getinfo fingerprint' return a 551 error if we're not a
8086 server, so we match what the control spec claims we do. Reported
8088 - Fix a typo in an error message when extendcircuit fails that
8089 caused us to not follow the \r\n-based delimiter protocol. Reported
8092 o Code simplifications and refactoring:
8093 - Stop passing around circuit_t and crypt_path_t pointers that are
8094 implicit in other procedure arguments.
8095 - Drop the old code to choke directory connections when the
8096 corresponding OR connections got full: thanks to the cell queue
8097 feature, OR conns don't get full any more.
8098 - Make dns_resolve() handle attaching connections to circuits
8099 properly, so the caller doesn't have to.
8100 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
8101 - Keep the connection array as a dynamic smartlist_t, rather than as
8102 a fixed-sized array. This is important, as the number of connections
8103 is becoming increasingly decoupled from the number of sockets.
8106 Changes in version 0.1.2.14 - 2007-05-25
8107 Tor 0.1.2.14 changes the addresses of two directory authorities (this
8108 change especially affects those who serve or use hidden services),
8109 and fixes several other crash- and security-related bugs.
8111 o Directory authority changes:
8112 - Two directory authorities (moria1 and moria2) just moved to new
8113 IP addresses. This change will particularly affect those who serve
8114 or use hidden services.
8116 o Major bugfixes (crashes):
8117 - If a directory server runs out of space in the connection table
8118 as it's processing a begin_dir request, it will free the exit stream
8119 but leave it attached to the circuit, leading to unpredictable
8120 behavior. (Reported by seeess, fixes bug 425.)
8121 - Fix a bug in dirserv_remove_invalid() that would cause authorities
8122 to corrupt memory under some really unlikely scenarios.
8123 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
8124 - Avoid segfaults when reading from mmaped descriptor file. (Reported
8127 o Major bugfixes (security):
8128 - When choosing an entry guard for a circuit, avoid using guards
8129 that are in the same family as the chosen exit -- not just guards
8130 that are exactly the chosen exit. (Reported by lodger.)
8132 o Major bugfixes (resource management):
8133 - If a directory authority is down, skip it when deciding where to get
8134 networkstatus objects or descriptors. Otherwise we keep asking
8135 every 10 seconds forever. Fixes bug 384.
8136 - Count it as a failure if we fetch a valid network-status but we
8137 don't want to keep it. Otherwise we'll keep fetching it and keep
8138 not wanting to keep it. Fixes part of bug 422.
8139 - If all of our dirservers have given us bad or no networkstatuses
8140 lately, then stop hammering them once per minute even when we
8141 think they're failed. Fixes another part of bug 422.
8144 - Actually set the purpose correctly for descriptors inserted with
8146 - When we have k non-v2 authorities in our DirServer config,
8147 we ignored the last k authorities in the list when updating our
8149 - Correctly back-off from requesting router descriptors that we are
8150 having a hard time downloading.
8151 - Read resolv.conf files correctly on platforms where read() returns
8152 partial results on small file reads.
8153 - Don't rebuild the entire router store every time we get 32K of
8154 routers: rebuild it when the journal gets very large, or when
8155 the gaps in the store get very large.
8158 - When routers publish SVN revisions in their router descriptors,
8159 authorities now include those versions correctly in networkstatus
8161 - Warn when using a version of libevent before 1.3b to run a server on
8162 OSX or BSD: these versions interact badly with userspace threads.
8165 Changes in version 0.1.2.13 - 2007-04-24
8166 This release features some major anonymity fixes, such as safer path
8167 selection; better client performance; faster bootstrapping, better
8168 address detection, and better DNS support for servers; write limiting as
8169 well as read limiting to make servers easier to run; and a huge pile of
8170 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
8172 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
8173 of the Freenode IRC network, remembering his patience and vision for
8174 free speech on the Internet.
8177 - Fix a memory leak when we ask for "all" networkstatuses and we
8178 get one we don't recognize.
8179 - Add more asserts to hunt down bug 417.
8180 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
8183 Changes in version 0.1.2.12-rc - 2007-03-16
8185 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
8186 directory information requested inside Tor connections (i.e. via
8187 begin_dir cells). It only triggered when the same connection was
8188 serving other data at the same time. Reported by seeess.
8191 - When creating a circuit via the controller, send a 'launched'
8192 event when we're done, so we follow the spec better.
8195 Changes in version 0.1.2.11-rc - 2007-03-15
8196 o Minor bugfixes (controller), reported by daejees:
8197 - Correct the control spec to match how the code actually responds
8198 to 'getinfo addr-mappings/*'.
8199 - The control spec described a GUARDS event, but the code
8200 implemented a GUARD event. Standardize on GUARD, but let people
8204 Changes in version 0.1.2.10-rc - 2007-03-07
8205 o Major bugfixes (Windows):
8206 - Do not load the NT services library functions (which may not exist)
8207 just to detect if we're a service trying to shut down. Now we run
8208 on Win98 and friends again.
8210 o Minor bugfixes (other):
8211 - Clarify a couple of log messages.
8212 - Fix a misleading socks5 error number.
8215 Changes in version 0.1.2.9-rc - 2007-03-02
8216 o Major bugfixes (Windows):
8217 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
8218 of the usual GCC "%llu". This prevents a bug when saving 64-bit
8219 int configuration values: the high-order 32 bits would get
8220 truncated. In particular, we were being bitten by the default
8221 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
8222 and maybe also bug 397.)
8224 o Minor bugfixes (performance):
8225 - Use OpenSSL's AES implementation on platforms where it's faster.
8226 This could save us as much as 10% CPU usage.
8228 o Minor bugfixes (server):
8229 - Do not rotate onion key immediately after setting it for the first
8232 o Minor bugfixes (directory authorities):
8233 - Stop calling servers that have been hibernating for a long time
8234 "stable". Also, stop letting hibernating or obsolete servers affect
8235 uptime and bandwidth cutoffs.
8236 - Stop listing hibernating servers in the v1 directory.
8238 o Minor bugfixes (hidden services):
8239 - Upload hidden service descriptors slightly less often, to reduce
8240 load on authorities.
8242 o Minor bugfixes (other):
8243 - Fix an assert that could trigger if a controller quickly set then
8244 cleared EntryNodes. (Bug found by Udo van den Heuvel.)
8245 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
8247 - Fix a potential race condition in the rpm installer. Found by
8249 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
8250 of 2 as indicating that the server is completely bad; it sometimes
8251 means that the server is just bad for the request in question. (may fix
8252 the last of bug 326.)
8253 - Disable encrypted directory connections when we don't have a server
8254 descriptor for the destination. We'll get this working again in
8258 Changes in version 0.1.2.8-beta - 2007-02-26
8259 o Major bugfixes (crashes):
8260 - Stop crashing when the controller asks us to resetconf more than
8261 one config option at once. (Vidalia 0.0.11 does this.)
8262 - Fix a crash that happened on Win98 when we're given command-line
8263 arguments: don't try to load NT service functions from advapi32.dll
8264 except when we need them. (Bug introduced in 0.1.2.7-alpha;
8266 - Fix a longstanding obscure crash bug that could occur when
8267 we run out of DNS worker processes. (Resolves bug 390.)
8269 o Major bugfixes (hidden services):
8270 - Correctly detect whether hidden service descriptor downloads are
8271 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
8273 o Major bugfixes (accounting):
8274 - When we start during an accounting interval before it's time to wake
8275 up, remember to wake up at the correct time. (May fix bug 342.)
8277 o Minor bugfixes (controller):
8278 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
8279 clear the corresponding on_circuit variable, and remember later
8280 that we don't need to send a redundant CLOSED event. (Resolves part
8282 - Report events where a resolve succeeded or where we got a socks
8283 protocol error correctly, rather than calling both of them
8285 - Change reported stream target addresses to IP consistently when
8286 we finally get the IP from an exit node.
8287 - Send log messages to the controller even if they happen to be very
8290 o Minor bugfixes (other):
8291 - Display correct results when reporting which versions are
8292 recommended, and how recommended they are. (Resolves bug 383.)
8293 - Improve our estimates for directory bandwidth to be less random:
8294 guess that an unrecognized directory will have the average bandwidth
8295 from all known directories, not that it will have the average
8296 bandwidth from those directories earlier than it on the list.
8297 - If we start a server with ClientOnly 1, then set ClientOnly to 0
8298 and hup, stop triggering an assert based on an empty onion_key.
8299 - On platforms with no working mmap() equivalent, don't warn the
8300 user when cached-routers doesn't exist.
8301 - Warn the user when mmap() [or its equivalent] fails for some reason
8302 other than file-not-found.
8303 - Don't warn the user when cached-routers.new doesn't exist: that's
8304 perfectly fine when starting up for the first time.
8305 - When EntryNodes are configured, rebuild the guard list to contain,
8306 in order: the EntryNodes that were guards before; the rest of the
8307 EntryNodes; the nodes that were guards before.
8308 - Mask out all signals in sub-threads; only the libevent signal
8309 handler should be processing them. This should prevent some crashes
8310 on some machines using pthreads. (Patch from coderman.)
8311 - Fix switched arguments on memset in the implementation of
8312 tor_munmap() for systems with no mmap() call.
8313 - When Tor receives a router descriptor that it asked for, but
8314 no longer wants (because it has received fresh networkstatuses
8315 in the meantime), do not warn the user. Cache the descriptor if
8316 we're a cache; drop it if we aren't.
8317 - Make earlier entry guards _really_ get retried when the network
8319 - On a malformed DNS reply, always give an error to the corresponding
8321 - Build with recent libevents on platforms that do not define the
8322 nonstandard types "u_int8_t" and friends.
8324 o Minor features (controller):
8325 - Warn the user when an application uses the obsolete binary v0
8326 control protocol. We're planning to remove support for it during
8327 the next development series, so it's good to give people some
8329 - Add STREAM_BW events to report per-entry-stream bandwidth
8330 use. (Patch from Robert Hogan.)
8331 - Rate-limit SIGNEWNYM signals in response to controllers that
8332 impolitely generate them for every single stream. (Patch from
8333 mwenge; closes bug 394.)
8334 - Make REMAP stream events have a SOURCE (cache or exit), and
8335 make them generated in every case where we get a successful
8336 connected or resolved cell.
8338 o Minor bugfixes (performance):
8339 - Call router_have_min_dir_info half as often. (This is showing up in
8340 some profiles, but not others.)
8341 - When using GCC, make log_debug never get called at all, and its
8342 arguments never get evaluated, when no debug logs are configured.
8343 (This is showing up in some profiles, but not others.)
8346 - Remove some never-implemented options. Mark PathlenCoinWeight as
8348 - Implement proposal 106: Stop requiring clients to have well-formed
8349 certificates; stop checking nicknames in certificates. (Clients
8350 have certificates so that they can look like Tor servers, but in
8351 the future we might want to allow them to look like regular TLS
8352 clients instead. Nicknames in certificates serve no purpose other
8353 than making our protocol easier to recognize on the wire.)
8354 - Revise messages on handshake failure again to be even more clear about
8355 which are incoming connections and which are outgoing.
8356 - Discard any v1 directory info that's over 1 month old (for
8357 directories) or over 1 week old (for running-routers lists).
8358 - Do not warn when individual nodes in the configuration's EntryNodes,
8359 ExitNodes, etc are down: warn only when all possible nodes
8360 are down. (Fixes bug 348.)
8361 - Always remove expired routers and networkstatus docs before checking
8362 whether we have enough information to build circuits. (Fixes
8364 - Put a lower-bound on MaxAdvertisedBandwidth.
8367 Changes in version 0.1.2.7-alpha - 2007-02-06
8368 o Major bugfixes (rate limiting):
8369 - Servers decline directory requests much more aggressively when
8370 they're low on bandwidth. Otherwise they end up queueing more and
8371 more directory responses, which can't be good for latency.
8372 - But never refuse directory requests from local addresses.
8373 - Fix a memory leak when sending a 503 response for a networkstatus
8375 - Be willing to read or write on local connections (e.g. controller
8376 connections) even when the global rate limiting buckets are empty.
8377 - If our system clock jumps back in time, don't publish a negative
8378 uptime in the descriptor. Also, don't let the global rate limiting
8379 buckets go absurdly negative.
8380 - Flush local controller connection buffers periodically as we're
8381 writing to them, so we avoid queueing 4+ megabytes of data before
8384 o Major bugfixes (NT services):
8385 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
8386 command-line flag so that admins can override the default by saying
8387 "tor --service install --user "SomeUser"". This will not affect
8388 existing installed services. Also, warn the user that the service
8389 will look for its configuration file in the service user's
8390 %appdata% directory. (We can't do the 'hardwire the user's appdata
8391 directory' trick any more, since we may not have read access to that
8394 o Major bugfixes (other):
8395 - Previously, we would cache up to 16 old networkstatus documents
8396 indefinitely, if they came from nontrusted authorities. Now we
8397 discard them if they are more than 10 days old.
8398 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
8400 - Detect and reject malformed DNS responses containing circular
8402 - If exits are rare enough that we're not marking exits as guards,
8403 ignore exit bandwidth when we're deciding the required bandwidth
8405 - When we're handling a directory connection tunneled over Tor,
8406 don't fill up internal memory buffers with all the data we want
8407 to tunnel; instead, only add it if the OR connection that will
8408 eventually receive it has some room for it. (This can lead to
8409 slowdowns in tunneled dir connections; a better solution will have
8412 o Minor bugfixes (dns):
8413 - Add some defensive programming to eventdns.c in an attempt to catch
8414 possible memory-stomping bugs.
8415 - Detect and reject DNS replies containing IPv4 or IPv6 records with
8416 an incorrect number of bytes. (Previously, we would ignore the
8418 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
8419 in the correct order, and doesn't crash.
8420 - Free memory held in recently-completed DNS lookup attempts on exit.
8421 This was not a memory leak, but may have been hiding memory leaks.
8422 - Handle TTL values correctly on reverse DNS lookups.
8423 - Treat failure to parse resolv.conf as an error.
8425 o Minor bugfixes (other):
8426 - Fix crash with "tor --list-fingerprint" (reported by seeess).
8427 - When computing clock skew from directory HTTP headers, consider what
8428 time it was when we finished asking for the directory, not what
8430 - Expire socks connections if they spend too long waiting for the
8431 handshake to finish. Previously we would let them sit around for
8432 days, if the connecting application didn't close them either.
8433 - And if the socks handshake hasn't started, don't send a
8434 "DNS resolve socks failed" handshake reply; just close it.
8435 - Stop using C functions that OpenBSD's linker doesn't like.
8436 - Don't launch requests for descriptors unless we have networkstatuses
8437 from at least half of the authorities. This delays the first
8438 download slightly under pathological circumstances, but can prevent
8439 us from downloading a bunch of descriptors we don't need.
8440 - Do not log IPs with TLS failures for incoming TLS
8441 connections. (Fixes bug 382.)
8442 - If the user asks to use invalid exit nodes, be willing to use
8444 - Stop using the reserved ac_cv namespace in our configure script.
8445 - Call stat() slightly less often; use fstat() when possible.
8446 - Refactor the way we handle pending circuits when an OR connection
8447 completes or fails, in an attempt to fix a rare crash bug.
8448 - Only rewrite a conn's address based on X-Forwarded-For: headers
8449 if it's a parseable public IP address; and stop adding extra quotes
8450 to the resulting address.
8453 - Weight directory requests by advertised bandwidth. Now we can
8454 let servers enable write limiting but still allow most clients to
8455 succeed at their directory requests. (We still ignore weights when
8456 choosing a directory authority; I hope this is a feature.)
8459 - Create a new file ReleaseNotes which was the old ChangeLog. The
8460 new ChangeLog file now includes the summaries for all development
8462 - Check for addresses with invalid characters at the exit as well
8463 as at the client, and warn less verbosely when they fail. You can
8464 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
8465 - Adapt a patch from goodell to let the contrib/exitlist script
8466 take arguments rather than require direct editing.
8467 - Inform the server operator when we decide not to advertise a
8468 DirPort due to AccountingMax enabled or a low BandwidthRate. It
8469 was confusing Zax, so now we're hopefully more helpful.
8470 - Bring us one step closer to being able to establish an encrypted
8471 directory tunnel without knowing a descriptor first. Still not
8472 ready yet. As part of the change, now assume we can use a
8473 create_fast cell if we don't know anything about a router.
8474 - Allow exit nodes to use nameservers running on ports other than 53.
8475 - Servers now cache reverse DNS replies.
8476 - Add an --ignore-missing-torrc command-line option so that we can
8477 get the "use sensible defaults if the configuration file doesn't
8478 exist" behavior even when specifying a torrc location on the command
8481 o Minor features (controller):
8482 - Track reasons for OR connection failure; make these reasons
8483 available via the controller interface. (Patch from Mike Perry.)
8484 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
8485 can learn when clients are sending malformed hostnames to Tor.
8486 - Clean up documentation for controller status events.
8487 - Add a REMAP status to stream events to note that a stream's
8488 address has changed because of a cached address or a MapAddress
8492 Changes in version 0.1.2.6-alpha - 2007-01-09
8494 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
8495 connection handles more than 4 gigs in either direction, we crash.
8496 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
8497 advertised exit node, somebody might try to exit from us when
8498 we're bootstrapping and before we've built our descriptor yet.
8499 Refuse the connection rather than crashing.
8502 - Warn if we (as a server) find that we've resolved an address that we
8503 weren't planning to resolve.
8504 - Warn that using select() on any libevent version before 1.1 will be
8505 unnecessarily slow (even for select()).
8506 - Flush ERR-level controller status events just like we currently
8507 flush ERR-level log events, so that a Tor shutdown doesn't prevent
8508 the controller from learning about current events.
8510 o Minor features (more controller status events):
8511 - Implement EXTERNAL_ADDRESS server status event so controllers can
8512 learn when our address changes.
8513 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
8514 can learn when directories reject our descriptor.
8515 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
8516 can learn when a client application is speaking a non-socks protocol
8518 - Implement DANGEROUS_SOCKS client status event so controllers
8519 can learn when a client application is leaking DNS addresses.
8520 - Implement BUG general status event so controllers can learn when
8521 Tor is unhappy about its internal invariants.
8522 - Implement CLOCK_SKEW general status event so controllers can learn
8523 when Tor thinks the system clock is set incorrectly.
8524 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
8525 server status events so controllers can learn when their descriptors
8526 are accepted by a directory.
8527 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
8528 server status events so controllers can learn about Tor's progress in
8529 deciding whether it's reachable from the outside.
8530 - Implement BAD_LIBEVENT general status event so controllers can learn
8531 when we have a version/method combination in libevent that needs to
8533 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
8534 and DNS_USELESS server status events so controllers can learn
8535 about changes to DNS server status.
8537 o Minor features (directory):
8538 - Authorities no longer recommend exits as guards if this would shift
8539 too much load to the exit nodes.
8542 Changes in version 0.1.2.5-alpha - 2007-01-06
8544 - Enable write limiting as well as read limiting. Now we sacrifice
8545 capacity if we're pushing out lots of directory traffic, rather
8546 than overrunning the user's intended bandwidth limits.
8547 - Include TLS overhead when counting bandwidth usage; previously, we
8548 would count only the bytes sent over TLS, but not the bytes used
8550 - Support running the Tor service with a torrc not in the same
8551 directory as tor.exe and default to using the torrc located in
8552 the %appdata%\Tor\ of the user who installed the service. Patch
8554 - Servers now check for the case when common DNS requests are going to
8555 wildcarded addresses (i.e. all getting the same answer), and change
8556 their exit policy to reject *:* if it's happening.
8557 - Implement BEGIN_DIR cells, so we can connect to the directory
8558 server via TLS to do encrypted directory requests rather than
8559 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
8560 config options if you like.
8562 o Minor features (config and docs):
8563 - Start using the state file to store bandwidth accounting data:
8564 the bw_accounting file is now obsolete. We'll keep generating it
8565 for a while for people who are still using 0.1.2.4-alpha.
8566 - Try to batch changes to the state file so that we do as few
8567 disk writes as possible while still storing important things in
8569 - The state file and the bw_accounting file get saved less often when
8570 the AvoidDiskWrites config option is set.
8571 - Make PIDFile work on Windows (untested).
8572 - Add internal descriptions for a bunch of configuration options:
8573 accessible via controller interface and in comments in saved
8575 - Reject *:563 (NNTPS) in the default exit policy. We already reject
8576 NNTP by default, so this seems like a sensible addition.
8577 - Clients now reject hostnames with invalid characters. This should
8578 avoid some inadvertent info leaks. Add an option
8579 AllowNonRFC953Hostnames to disable this behavior, in case somebody
8580 is running a private network with hosts called @, !, and #.
8581 - Add a maintainer script to tell us which options are missing
8582 documentation: "make check-docs".
8583 - Add a new address-spec.txt document to describe our special-case
8584 addresses: .exit, .onion, and .noconnnect.
8586 o Minor features (DNS):
8587 - Ongoing work on eventdns infrastructure: now it has dns server
8588 and ipv6 support. One day Tor will make use of it.
8589 - Add client-side caching for reverse DNS lookups.
8590 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
8591 - When we change nameservers or IP addresses, reset and re-launch
8592 our tests for DNS hijacking.
8594 o Minor features (directory):
8595 - Authorities now specify server versions in networkstatus. This adds
8596 about 2% to the size of compressed networkstatus docs, and allows
8597 clients to tell which servers support BEGIN_DIR and which don't.
8598 The implementation is forward-compatible with a proposed future
8599 protocol version scheme not tied to Tor versions.
8600 - DirServer configuration lines now have an orport= option so
8601 clients can open encrypted tunnels to the authorities without
8602 having downloaded their descriptors yet. Enabled for moria1,
8603 moria2, tor26, and lefkada now in the default configuration.
8604 - Directory servers are more willing to send a 503 "busy" if they
8605 are near their write limit, especially for v1 directory requests.
8606 Now they can use their limited bandwidth for actual Tor traffic.
8607 - Clients track responses with status 503 from dirservers. After a
8608 dirserver has given us a 503, we try not to use it until an hour has
8609 gone by, or until we have no dirservers that haven't given us a 503.
8610 - When we get a 503 from a directory, and we're not a server, we don't
8611 count the failure against the total number of failures allowed
8612 for the thing we're trying to download.
8613 - Report X-Your-Address-Is correctly from tunneled directory
8614 connections; don't report X-Your-Address-Is when it's an internal
8615 address; and never believe reported remote addresses when they're
8617 - Protect against an unlikely DoS attack on directory servers.
8618 - Add a BadDirectory flag to network status docs so that authorities
8619 can (eventually) tell clients about caches they believe to be
8622 o Minor features (controller):
8623 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
8624 - Reimplement GETINFO so that info/names stays in sync with the
8626 - Implement "GETINFO fingerprint".
8627 - Implement "SETEVENTS GUARD" so controllers can get updates on
8628 entry guard status as it changes.
8630 o Minor features (clean up obsolete pieces):
8631 - Remove some options that have been deprecated since at least
8632 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
8633 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
8635 - We no longer look for identity and onion keys in "identity.key" and
8636 "onion.key" -- these were replaced by secret_id_key and
8637 secret_onion_key in 0.0.8pre1.
8638 - We no longer require unrecognized directory entries to be
8641 o Major bugfixes (security):
8642 - Stop sending the HttpProxyAuthenticator string to directory
8643 servers when directory connections are tunnelled through Tor.
8644 - Clients no longer store bandwidth history in the state file.
8645 - Do not log introduction points for hidden services if SafeLogging
8647 - When generating bandwidth history, round down to the nearest
8648 1k. When storing accounting data, round up to the nearest 1k.
8649 - When we're running as a server, remember when we last rotated onion
8650 keys, so that we will rotate keys once they're a week old even if
8651 we never stay up for a week ourselves.
8653 o Major bugfixes (other):
8654 - Fix a longstanding bug in eventdns that prevented the count of
8655 timed-out resolves from ever being reset. This bug caused us to
8656 give up on a nameserver the third time it timed out, and try it
8657 10 seconds later... and to give up on it every time it timed out
8659 - Take out the '5 second' timeout from the connection retry
8660 schedule. Now the first connect attempt will wait a full 10
8661 seconds before switching to a new circuit. Perhaps this will help
8662 a lot. Based on observations from Mike Perry.
8663 - Fix a bug on the Windows implementation of tor_mmap_file() that
8664 would prevent the cached-routers file from ever loading. Reported
8668 - Fix an assert failure when a directory authority sets
8669 AuthDirRejectUnlisted and then receives a descriptor from an
8670 unlisted router. Reported by seeess.
8671 - Avoid a double-free when parsing malformed DirServer lines.
8672 - Fix a bug when a BSD-style PF socket is first used. Patch from
8674 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
8675 to resolve an address at a given exit node even when they ask for
8677 - Servers no longer ever list themselves in their "family" line,
8678 even if configured to do so. This makes it easier to configure
8679 family lists conveniently.
8680 - When running as a server, don't fall back to 127.0.0.1 when no
8681 nameservers are configured in /etc/resolv.conf; instead, make the
8682 user fix resolv.conf or specify nameservers explicitly. (Resolves
8684 - Stop accepting certain malformed ports in configured exit policies.
8685 - Don't re-write the fingerprint file every restart, unless it has
8687 - Stop warning when a single nameserver fails: only warn when _all_ of
8688 our nameservers have failed. Also, when we only have one nameserver,
8689 raise the threshold for deciding that the nameserver is dead.
8690 - Directory authorities now only decide that routers are reachable
8691 if their identity keys are as expected.
8692 - When the user uses bad syntax in the Log config line, stop
8693 suggesting other bad syntax as a replacement.
8694 - Correctly detect ipv6 DNS capability on OpenBSD.
8696 o Minor bugfixes (controller):
8697 - Report the circuit number correctly in STREAM CLOSED events. Bug
8698 reported by Mike Perry.
8699 - Do not report bizarre values for results of accounting GETINFOs
8700 when the last second's write or read exceeds the allotted bandwidth.
8701 - Report "unrecognized key" rather than an empty string when the
8702 controller tries to fetch a networkstatus that doesn't exist.
8705 Changes in version 0.1.1.26 - 2006-12-14
8706 o Security bugfixes:
8707 - Stop sending the HttpProxyAuthenticator string to directory
8708 servers when directory connections are tunnelled through Tor.
8709 - Clients no longer store bandwidth history in the state file.
8710 - Do not log introduction points for hidden services if SafeLogging
8714 - Fix an assert failure when a directory authority sets
8715 AuthDirRejectUnlisted and then receives a descriptor from an
8716 unlisted router (reported by seeess).
8719 Changes in version 0.1.2.4-alpha - 2006-12-03
8721 - Add support for using natd; this allows FreeBSDs earlier than
8722 5.1.2 to have ipfw send connections through Tor without using
8723 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
8726 - Make all connections to addresses of the form ".noconnect"
8727 immediately get closed. This lets application/controller combos
8728 successfully test whether they're talking to the same Tor by
8729 watching for STREAM events.
8730 - Make cross.sh cross-compilation script work even when autogen.sh
8731 hasn't been run. (Patch from Michael Mohr.)
8732 - Statistics dumped by -USR2 now include a breakdown of public key
8733 operations, for profiling.
8736 - Fix a major leak when directory authorities parse their
8737 approved-routers list, a minor memory leak when we fail to pick
8738 an exit node, and a few rare leaks on errors.
8739 - Handle TransPort connections even when the server sends data before
8740 the client sends data. Previously, the connection would just hang
8741 until the client sent data. (Patch from tup based on patch from
8743 - Avoid assert failure when our cached-routers file is empty on
8747 - Don't log spurious warnings when we see a circuit close reason we
8748 don't recognize; it's probably just from a newer version of Tor.
8749 - Have directory authorities allow larger amounts of drift in uptime
8750 without replacing the server descriptor: previously, a server that
8751 restarted every 30 minutes could have 48 "interesting" descriptors
8753 - Start linking to the Tor specification and Tor reference manual
8754 correctly in the Windows installer.
8755 - Add Vidalia to the OS X uninstaller script, so when we uninstall
8756 Tor/Privoxy we also uninstall Vidalia.
8757 - Resume building on Irix64, and fix a lot of warnings from its
8759 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
8760 when we're running as a client.
8763 Changes in version 0.1.1.25 - 2006-11-04
8765 - When a client asks us to resolve (rather than connect to)
8766 an address, and we have a cached answer, give them the cached
8767 answer. Previously, we would give them no answer at all.
8768 - We were building exactly the wrong circuits when we predict
8769 hidden service requirements, meaning Tor would have to build all
8770 its circuits on demand.
8771 - If none of our live entry guards have a high uptime, but we
8772 require a guard with a high uptime, try adding a new guard before
8773 we give up on the requirement. This patch should make long-lived
8774 connections more stable on average.
8775 - When testing reachability of our DirPort, don't launch new
8776 tests when there's already one in progress -- unreachable
8777 servers were stacking up dozens of testing streams.
8779 o Security bugfixes:
8780 - When the user sends a NEWNYM signal, clear the client-side DNS
8781 cache too. Otherwise we continue to act on previous information.
8784 - Avoid a memory corruption bug when creating a hash table for
8786 - Avoid possibility of controller-triggered crash when misusing
8787 certain commands from a v0 controller on platforms that do not
8788 handle printf("%s",NULL) gracefully.
8789 - Avoid infinite loop on unexpected controller input.
8790 - Don't log spurious warnings when we see a circuit close reason we
8791 don't recognize; it's probably just from a newer version of Tor.
8792 - Add Vidalia to the OS X uninstaller script, so when we uninstall
8793 Tor/Privoxy we also uninstall Vidalia.
8796 Changes in version 0.1.2.3-alpha - 2006-10-29
8798 - Prepare for servers to publish descriptors less often: never
8799 discard a descriptor simply for being too old until either it is
8800 recommended by no authorities, or until we get a better one for
8801 the same router. Make caches consider retaining old recommended
8802 routers for even longer.
8803 - If most authorities set a BadExit flag for a server, clients
8804 don't think of it as a general-purpose exit. Clients only consider
8805 authorities that advertise themselves as listing bad exits.
8806 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
8807 headers for content, so that we can work better in the presence of
8808 caching HTTP proxies.
8809 - Allow authorities to list nodes as bad exits by fingerprint or by
8812 o Minor features, controller:
8813 - Add a REASON field to CIRC events; for backward compatibility, this
8814 field is sent only to controllers that have enabled the extended
8815 event format. Also, add additional reason codes to explain why
8816 a given circuit has been destroyed or truncated. (Patches from
8818 - Add a REMOTE_REASON field to extended CIRC events to tell the
8819 controller about why a remote OR told us to close a circuit.
8820 - Stream events also now have REASON and REMOTE_REASON fields,
8821 working much like those for circuit events.
8822 - There's now a GETINFO ns/... field so that controllers can ask Tor
8823 about the current status of a router.
8824 - A new event type "NS" to inform a controller when our opinion of
8825 a router's status has changed.
8826 - Add a GETINFO events/names and GETINFO features/names so controllers
8827 can tell which events and features are supported.
8828 - A new CLEARDNSCACHE signal to allow controllers to clear the
8829 client-side DNS cache without expiring circuits.
8831 o Security bugfixes:
8832 - When the user sends a NEWNYM signal, clear the client-side DNS
8833 cache too. Otherwise we continue to act on previous information.
8836 - Avoid sending junk to controllers or segfaulting when a controller
8837 uses EVENT_NEW_DESC with verbose nicknames.
8838 - Stop triggering asserts if the controller tries to extend hidden
8839 service circuits (reported by mwenge).
8840 - Avoid infinite loop on unexpected controller input.
8841 - When the controller does a "GETINFO network-status", tell it
8842 about even those routers whose descriptors are very old, and use
8843 long nicknames where appropriate.
8844 - Change NT service functions to be loaded on demand. This lets us
8845 build with MinGW without breaking Tor for Windows 98 users.
8846 - Do DirPort reachability tests less often, since a single test
8847 chews through many circuits before giving up.
8848 - In the hidden service example in torrc.sample, stop recommending
8849 esoteric and discouraged hidden service options.
8850 - When stopping an NT service, wait up to 10 sec for it to actually
8851 stop. (Patch from Matt Edman; resolves bug 295.)
8852 - Fix handling of verbose nicknames with ORCONN controller events:
8853 make them show up exactly when requested, rather than exactly when
8855 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
8856 printing a duplicate "$" in the keys we send (reported by mwenge).
8857 - Correctly set maximum connection limit on Cygwin. (This time
8859 - Try to detect Windows correctly when cross-compiling.
8860 - Detect the size of the routers file correctly even if it is
8861 corrupted (on systems without mmap) or not page-aligned (on systems
8862 with mmap). This bug was harmless.
8863 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
8864 to open a stream fails; now we do in more cases. This should
8865 make clients able to find a good exit faster in some cases, since
8866 unhandleable requests will now get an error rather than timing out.
8867 - Resolve two memory leaks when rebuilding the on-disk router cache
8868 (reported by fookoowa).
8869 - Clean up minor code warnings suggested by the MIPSpro C compiler,
8870 and reported by some Centos users.
8871 - Controller signals now work on non-Unix platforms that don't define
8872 SIGUSR1 and SIGUSR2 the way we expect.
8873 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
8874 values before failing, and always enables eventdns.
8875 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
8876 Try to fix this in configure.in by checking for most functions
8877 before we check for libevent.
8880 Changes in version 0.1.2.2-alpha - 2006-10-07
8882 - Make our async eventdns library on-by-default for Tor servers,
8883 and plan to deprecate the separate dnsworker threads.
8884 - Add server-side support for "reverse" DNS lookups (using PTR
8885 records so clients can determine the canonical hostname for a given
8886 IPv4 address). Only supported by servers using eventdns; servers
8887 now announce in their descriptors whether they support eventdns.
8888 - Specify and implement client-side SOCKS5 interface for reverse DNS
8889 lookups (see doc/socks-extensions.txt).
8890 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
8891 connect to directory servers through Tor. Previously, clients needed
8892 to find Tor exits to make private connections to directory servers.
8893 - Avoid choosing Exit nodes for entry or middle hops when the
8894 total bandwidth available from non-Exit nodes is much higher than
8895 the total bandwidth available from Exit nodes.
8896 - Workaround for name servers (like Earthlink's) that hijack failing
8897 DNS requests and replace the no-such-server answer with a "helpful"
8898 redirect to an advertising-driven search portal. Also work around
8899 DNS hijackers who "helpfully" decline to hijack known-invalid
8900 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
8901 lets you turn it off.
8902 - Send out a burst of long-range padding cells once we've established
8903 that we're reachable. Spread them over 4 circuits, so hopefully
8904 a few will be fast. This exercises our bandwidth and bootstraps
8905 us into the directory more quickly.
8907 o New/improved config options:
8908 - Add new config option "ResolvConf" to let the server operator
8909 choose an alternate resolve.conf file when using eventdns.
8910 - Add an "EnforceDistinctSubnets" option to control our "exclude
8911 servers on the same /16" behavior. It's still on by default; this
8912 is mostly for people who want to operate private test networks with
8913 all the machines on the same subnet.
8914 - If one of our entry guards is on the ExcludeNodes list, or the
8915 directory authorities don't think it's a good guard, treat it as
8916 if it were unlisted: stop using it as a guard, and throw it off
8917 the guards list if it stays that way for a long time.
8918 - Allow directory authorities to be marked separately as authorities
8919 for the v1 directory protocol, the v2 directory protocol, and
8920 as hidden service directories, to make it easier to retire old
8921 authorities. V1 authorities should set "HSAuthoritativeDir 1"
8922 to continue being hidden service authorities too.
8923 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
8925 o Minor features, controller:
8926 - Fix CIRC controller events so that controllers can learn the
8927 identity digests of non-Named servers used in circuit paths.
8928 - Let controllers ask for more useful identifiers for servers. Instead
8929 of learning identity digests for un-Named servers and nicknames
8930 for Named servers, the new identifiers include digest, nickname,
8931 and indication of Named status. Off by default; see control-spec.txt
8932 for more information.
8933 - Add a "getinfo address" controller command so it can display Tor's
8934 best guess to the user.
8935 - New controller event to alert the controller when our server
8936 descriptor has changed.
8937 - Give more meaningful errors on controller authentication failure.
8939 o Minor features, other:
8940 - When asked to resolve a hostname, don't use non-exit servers unless
8941 requested to do so. This allows servers with broken DNS to be
8942 useful to the network.
8943 - Divide eventdns log messages into warn and info messages.
8944 - Reserve the nickname "Unnamed" for routers that can't pick
8945 a hostname: any router can call itself Unnamed; directory
8946 authorities will never allocate Unnamed to any particular router;
8947 clients won't believe that any router is the canonical Unnamed.
8948 - Only include function names in log messages for info/debug messages.
8949 For notice/warn/err, the content of the message should be clear on
8950 its own, and printing the function name only confuses users.
8951 - Avoid some false positives during reachability testing: don't try
8952 to test via a server that's on the same /24 as us.
8953 - If we fail to build a circuit to an intended enclave, and it's
8954 not mandatory that we use that enclave, stop wanting it.
8955 - When eventdns is enabled, allow multithreaded builds on NetBSD and
8956 OpenBSD. (We had previously disabled threads on these platforms
8957 because they didn't have working thread-safe resolver functions.)
8959 o Major bugfixes, anonymity/security:
8960 - If a client asked for a server by name, and there's a named server
8961 in our network-status but we don't have its descriptor yet, we
8962 could return an unnamed server instead.
8963 - Fix NetBSD bug that could allow someone to force uninitialized RAM
8964 to be sent to a server's DNS resolver. This only affects NetBSD
8965 and other platforms that do not bounds-check tolower().
8966 - Reject (most) attempts to use Tor circuits with length one. (If
8967 many people start using Tor as a one-hop proxy, exit nodes become
8968 a more attractive target for compromise.)
8969 - Just because your DirPort is open doesn't mean people should be
8970 able to remotely teach you about hidden service descriptors. Now
8971 only accept rendezvous posts if you've got HSAuthoritativeDir set.
8973 o Major bugfixes, other:
8974 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
8975 - When a client asks the server to resolve (not connect to)
8976 an address, and it has a cached answer, give them the cached answer.
8977 Previously, the server would give them no answer at all.
8978 - Allow really slow clients to not hang up five minutes into their
8979 directory downloads (suggested by Adam J. Richter).
8980 - We were building exactly the wrong circuits when we anticipated
8981 hidden service requirements, meaning Tor would have to build all
8982 its circuits on demand.
8983 - Avoid crashing when we mmap a router cache file of size 0.
8984 - When testing reachability of our DirPort, don't launch new
8985 tests when there's already one in progress -- unreachable
8986 servers were stacking up dozens of testing streams.
8988 o Minor bugfixes, correctness:
8989 - If we're a directory mirror and we ask for "all" network status
8990 documents, we would discard status documents from authorities
8992 - Avoid a memory corruption bug when creating a hash table for
8994 - Avoid controller-triggered crash when misusing certain commands
8995 from a v0 controller on platforms that do not handle
8996 printf("%s",NULL) gracefully.
8997 - Don't crash when a controller sends a third argument to an
8998 "extendcircuit" request.
8999 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
9000 response; fix error code when "getinfo dir/status/" fails.
9001 - Avoid crash when telling controller stream-status and a stream
9003 - Patch from Adam Langley to fix assert() in eventdns.c.
9004 - Fix a debug log message in eventdns to say "X resolved to Y"
9005 instead of "X resolved to X".
9006 - Make eventdns give strings for DNS errors, not just error numbers.
9007 - Track unreachable entry guards correctly: don't conflate
9008 'unreachable by us right now' with 'listed as down by the directory
9009 authorities'. With the old code, if a guard was unreachable by
9010 us but listed as running, it would clog our guard list forever.
9011 - Behave correctly in case we ever have a network with more than
9012 2GB/s total advertised capacity.
9013 - Make TrackExitHosts case-insensitive, and fix the behavior of
9014 ".suffix" TrackExitHosts items to avoid matching in the middle of
9016 - Finally fix the openssl warnings from newer gccs that believe that
9017 ignoring a return value is okay, but casting a return value and
9018 then ignoring it is a sign of madness.
9019 - Prevent the contrib/exitlist script from printing the same
9020 result more than once.
9021 - Patch from Steve Hildrey: Generate network status correctly on
9022 non-versioning dirservers.
9023 - Don't listen to the X-Your-Address-Is hint if you did the lookup
9024 via Tor; otherwise you'll think you're the exit node's IP address.
9026 o Minor bugfixes, performance:
9027 - Two small performance improvements on parsing descriptors.
9028 - Major performance improvement on inserting descriptors: change
9029 algorithm from O(n^2) to O(n).
9030 - Make the common memory allocation path faster on machines where
9031 malloc(0) returns a pointer.
9032 - Start remembering X-Your-Address-Is directory hints even if you're
9033 a client, so you can become a server more smoothly.
9034 - Avoid duplicate entries on MyFamily line in server descriptor.
9036 o Packaging, features:
9037 - Remove architecture from OS X builds. The official builds are
9038 now universal binaries.
9039 - The Debian package now uses --verify-config when (re)starting,
9040 to distinguish configuration errors from other errors.
9041 - Update RPMs to require libevent 1.1b.
9043 o Packaging, bugfixes:
9044 - Patches so Tor builds with MinGW on Windows.
9045 - Patches so Tor might run on Cygwin again.
9046 - Resume building on non-gcc compilers and ancient gcc. Resume
9047 building with the -O0 compile flag. Resume building cleanly on
9049 - Run correctly on OS X platforms with case-sensitive filesystems.
9050 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
9051 - Add autoconf checks so Tor can build on Solaris x86 again.
9054 - Documented (and renamed) ServerDNSSearchDomains and
9055 ServerDNSResolvConfFile options.
9056 - Be clearer that the *ListenAddress directives can be repeated
9060 Changes in version 0.1.1.24 - 2006-09-29
9062 - Allow really slow clients to not hang up five minutes into their
9063 directory downloads (suggested by Adam J. Richter).
9064 - Fix major performance regression from 0.1.0.x: instead of checking
9065 whether we have enough directory information every time we want to
9066 do something, only check when the directory information has changed.
9067 This should improve client CPU usage by 25-50%.
9068 - Don't crash if, after a server has been running for a while,
9069 it can't resolve its hostname.
9072 - Allow Tor to start when RunAsDaemon is set but no logs are set.
9073 - Don't crash when the controller receives a third argument to an
9074 "extendcircuit" request.
9075 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
9076 response; fix error code when "getinfo dir/status/" fails.
9077 - Fix configure.in to not produce broken configure files with
9078 more recent versions of autoconf. Thanks to Clint for his auto*
9080 - Fix security bug on NetBSD that could allow someone to force
9081 uninitialized RAM to be sent to a server's DNS resolver. This
9082 only affects NetBSD and other platforms that do not bounds-check
9084 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
9085 methods: these are known to be buggy.
9086 - If we're a directory mirror and we ask for "all" network status
9087 documents, we would discard status documents from authorities
9091 Changes in version 0.1.2.1-alpha - 2006-08-27
9093 - Add "eventdns" async dns library from Adam Langley, tweaked to
9094 build on OSX and Windows. Only enabled if you pass the
9095 --enable-eventdns argument to configure.
9096 - Allow servers with no hostname or IP address to learn their
9097 IP address by asking the directory authorities. This code only
9098 kicks in when you would normally have exited with a "no address"
9099 error. Nothing's authenticated, so use with care.
9100 - Rather than waiting a fixed amount of time between retrying
9101 application connections, we wait only 5 seconds for the first,
9102 10 seconds for the second, and 15 seconds for each retry after
9103 that. Hopefully this will improve the expected user experience.
9104 - Patch from Tup to add support for transparent AP connections:
9105 this basically bundles the functionality of trans-proxy-tor
9106 into the Tor mainline. Now hosts with compliant pf/netfilter
9107 implementations can redirect TCP connections straight to Tor
9108 without diverting through SOCKS. Needs docs.
9109 - Busy directory servers save lots of memory by spooling server
9110 descriptors, v1 directories, and v2 networkstatus docs to buffers
9111 as needed rather than en masse. Also mmap the cached-routers
9112 files, so we don't need to keep the whole thing in memory too.
9113 - Automatically avoid picking more than one node from the same
9114 /16 network when constructing a circuit.
9115 - Revise and clean up the torrc.sample that we ship with; add
9116 a section for BandwidthRate and BandwidthBurst.
9119 - Split circuit_t into origin_circuit_t and or_circuit_t, and
9120 split connection_t into edge, or, dir, control, and base structs.
9121 These will save quite a bit of memory on busy servers, and they'll
9122 also help us track down bugs in the code and bugs in the spec.
9123 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
9124 or later. Log when we are doing this, so we can diagnose it when
9125 it fails. (Also, recommend libevent 1.1b for kqueue and
9126 win32 methods; deprecate libevent 1.0b harder; make libevent
9127 recommendation system saner.)
9128 - Start being able to build universal binaries on OS X (thanks
9130 - Export the default exit policy via the control port, so controllers
9131 don't need to guess what it is / will be later.
9132 - Add a man page entry for ProtocolWarnings.
9133 - Add TestVia config option to the man page.
9134 - Remove even more protocol-related warnings from Tor server logs,
9135 such as bad TLS handshakes and malformed begin cells.
9136 - Stop fetching descriptors if you're not a dir mirror and you
9137 haven't tried to establish any circuits lately. [This currently
9138 causes some dangerous behavior, because when you start up again
9139 you'll use your ancient server descriptors.]
9140 - New DirPort behavior: if you have your dirport set, you download
9141 descriptors aggressively like a directory mirror, whether or not
9143 - Get rid of the router_retry_connections notion. Now routers
9144 no longer try to rebuild long-term connections to directory
9145 authorities, and directory authorities no longer try to rebuild
9146 long-term connections to all servers. We still don't hang up
9147 connections in these two cases though -- we need to look at it
9148 more carefully to avoid flapping, and we likely need to wait til
9149 0.1.1.x is obsolete.
9150 - Drop compatibility with obsolete Tors that permit create cells
9151 to have the wrong circ_id_type.
9152 - Re-enable per-connection rate limiting. Get rid of the "OP
9153 bandwidth" concept. Lay groundwork for "bandwidth classes" --
9154 separate global buckets that apply depending on what sort of conn
9156 - Start publishing one minute or so after we find our ORPort
9157 to be reachable. This will help reduce the number of descriptors
9158 we have for ourselves floating around, since it's quite likely
9159 other things (e.g. DirPort) will change during that minute too.
9160 - Fork the v1 directory protocol into its own spec document,
9161 and mark dir-spec.txt as the currently correct (v2) spec.
9164 - When we find our DirPort to be reachable, publish a new descriptor
9165 so we'll tell the world (reported by pnx).
9166 - Publish a new descriptor after we hup/reload. This is important
9167 if our config has changed such that we'll want to start advertising
9168 our DirPort now, etc.
9169 - Allow Tor to start when RunAsDaemon is set but no logs are set.
9170 - When we have a state file we cannot parse, tell the user and
9171 move it aside. Now we avoid situations where the user starts
9172 Tor in 1904, Tor writes a state file with that timestamp in it,
9173 the user fixes her clock, and Tor refuses to start.
9174 - Fix configure.in to not produce broken configure files with
9175 more recent versions of autoconf. Thanks to Clint for his auto*
9177 - "tor --verify-config" now exits with -1(255) or 0 depending on
9178 whether the config options are bad or good.
9179 - Resolve bug 321 when using dnsworkers: append a period to every
9180 address we resolve at the exit node, so that we do not accidentally
9181 pick up local addresses, and so that failing searches are retried
9182 in the resolver search domains. (This is already solved for
9183 eventdns.) (This breaks Blossom servers for now.)
9184 - If we are using an exit enclave and we can't connect, e.g. because
9185 its webserver is misconfigured to not listen on localhost, then
9186 back off and try connecting from somewhere else before we fail.
9189 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
9190 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
9191 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
9192 when the IP address is mapped through MapAddress to a hostname.
9193 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
9194 useless IPv6 DNS resolves.
9195 - Patch suggested by Karsten Loesing: respond to SIGNAL command
9196 before we execute the signal, in case the signal shuts us down.
9197 - Clean up AllowInvalidNodes man page entry.
9198 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
9199 - Add more asserts to track down an assert error on a windows Tor
9200 server with connection_add being called with socket == -1.
9201 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
9202 - Fix misleading log messages: an entry guard that is "unlisted",
9203 as well as not known to be "down" (because we've never heard
9204 of it), is not therefore "up".
9205 - Remove code to special-case "-cvs" ending, since it has not
9206 actually mattered since 0.0.9.
9207 - Make our socks5 handling more robust to broken socks clients:
9208 throw out everything waiting on the buffer in between socks
9209 handshake phases, since they can't possibly (so the theory
9210 goes) have predicted what we plan to respond to them.
9213 Changes in version 0.1.1.23 - 2006-07-30
9215 - Fast Tor servers, especially exit nodes, were triggering asserts
9216 due to a bug in handling the list of pending DNS resolves. Some
9217 bugs still remain here; we're hunting them.
9218 - Entry guards could crash clients by sending unexpected input.
9219 - More fixes on reachability testing: if you find yourself reachable,
9220 then don't ever make any client requests (so you stop predicting
9221 circuits), then hup or have your clock jump, then later your IP
9222 changes, you won't think circuits are working, so you won't try to
9223 test reachability, so you won't publish.
9226 - Avoid a crash if the controller does a resetconf firewallports
9227 and then a setconf fascistfirewall=1.
9228 - Avoid an integer underflow when the dir authority decides whether
9229 a router is stable: we might wrongly label it stable, and compute
9230 a slightly wrong median stability, when a descriptor is published
9232 - Fix a place where we might trigger an assert if we can't build our
9233 own server descriptor yet.
9236 Changes in version 0.1.1.22 - 2006-07-05
9238 - Fix a big bug that was causing servers to not find themselves
9239 reachable if they changed IP addresses. Since only 0.1.1.22+
9240 servers can do reachability testing correctly, now we automatically
9241 make sure to test via one of these.
9242 - Fix to allow clients and mirrors to learn directory info from
9243 descriptor downloads that get cut off partway through.
9244 - Directory authorities had a bug in deciding if a newly published
9245 descriptor was novel enough to make everybody want a copy -- a few
9246 servers seem to be publishing new descriptors many times a minute.
9248 - Fix a rare bug that was causing some servers to complain about
9249 "closing wedged cpuworkers" and skip some circuit create requests.
9250 - Make the Exit flag in directory status documents actually work.
9253 Changes in version 0.1.1.21 - 2006-06-10
9254 o Crash and assert fixes from 0.1.1.20:
9255 - Fix a rare crash on Tor servers that have enabled hibernation.
9256 - Fix a seg fault on startup for Tor networks that use only one
9257 directory authority.
9258 - Fix an assert from a race condition that occurs on Tor servers
9259 while exiting, where various threads are trying to log that they're
9260 exiting, and delete the logs, at the same time.
9261 - Make our unit tests pass again on certain obscure platforms.
9264 - Add support for building SUSE RPM packages.
9265 - Speed up initial bootstrapping for clients: if we are making our
9266 first ever connection to any entry guard, then don't mark it down
9268 - When only one Tor server in the network is labelled as a guard,
9269 and we've already picked him, we would cycle endlessly picking him
9270 again, being unhappy about it, etc. Now we specifically exclude
9271 current guards when picking a new guard.
9272 - Servers send create cells more reliably after the TLS connection
9273 is established: we were sometimes forgetting to send half of them
9274 when we had more than one pending.
9275 - If we get a create cell that asks us to extend somewhere, but the
9276 Tor server there doesn't match the expected digest, we now send
9277 a destroy cell back, rather than silently doing nothing.
9278 - Make options->RedirectExit work again.
9279 - Make cookie authentication for the controller work again.
9280 - Stop being picky about unusual characters in the arguments to
9281 mapaddress. It's none of our business.
9282 - Add a new config option "TestVia" that lets you specify preferred
9283 middle hops to use for test circuits. Perhaps this will let me
9284 debug the reachability problems better.
9286 o Log / documentation fixes:
9287 - If we're a server and some peer has a broken TLS certificate, don't
9288 log about it unless ProtocolWarnings is set, i.e., we want to hear
9289 about protocol violations by others.
9290 - Fix spelling of VirtualAddrNetwork in man page.
9291 - Add a better explanation at the top of the autogenerated torrc file
9292 about what happened to our old torrc.
9295 Changes in version 0.1.1.20 - 2006-05-23
9297 - Downgrade a log severity where servers complain that they're
9299 - Avoid a compile warning on FreeBSD.
9300 - Remove string size limit on NEWDESC messages; solve bug 291.
9301 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
9302 more thoroughly when we're running on windows.
9305 Changes in version 0.1.1.19-rc - 2006-05-03
9307 - Regenerate our local descriptor if it's dirty and we try to use
9308 it locally (e.g. if it changes during reachability detection).
9309 - If we setconf our ORPort to 0, we continued to listen on the
9310 old ORPort and receive connections.
9311 - Avoid a second warning about machine/limits.h on Debian
9313 - Be willing to add our own routerinfo into the routerlist.
9314 Now authorities will include themselves in their directories
9315 and network-statuses.
9316 - Stop trying to upload rendezvous descriptors to every
9317 directory authority: only try the v1 authorities.
9318 - Servers no longer complain when they think they're not
9319 registered with the directory authorities. There were too many
9321 - Backport dist-rpm changes so rpms can be built without errors.
9324 - Implement an option, VirtualAddrMask, to set which addresses
9325 get handed out in response to mapaddress requests. This works
9326 around a bug in tsocks where 127.0.0.0/8 is never socksified.
9329 Changes in version 0.1.1.18-rc - 2006-04-10
9331 - Work harder to download live network-statuses from all the
9332 directory authorities we know about. Improve the threshold
9333 decision logic so we're more robust to edge cases.
9334 - When fetching rendezvous descriptors, we were willing to ask
9335 v2 authorities too, which would always return 404.
9338 - Stop listing down or invalid nodes in the v1 directory. This will
9339 reduce its bulk by about 1/3, and reduce load on directory
9341 - When deciding whether a router is Fast or Guard-worthy, consider
9342 his advertised BandwidthRate and not just the BandwidthCapacity.
9343 - No longer ship INSTALL and README files -- they are useless now.
9344 - Force rpmbuild to behave and honor target_cpu.
9345 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
9346 - Start to include translated versions of the tor-doc-*.html
9347 files, along with the screenshots. Still needs more work.
9348 - Start sending back 512 and 451 errors if mapaddress fails,
9349 rather than not sending anything back at all.
9350 - When we fail to bind or listen on an incoming or outgoing
9351 socket, we should close it before failing. otherwise we just
9352 leak it. (thanks to weasel for finding.)
9353 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
9354 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
9355 - Make NoPublish (even though deprecated) work again.
9356 - Fix a minor security flaw where a versioning auth dirserver
9357 could list a recommended version many times in a row to make
9358 clients more convinced that it's recommended.
9359 - Fix crash bug if there are two unregistered servers running
9360 with the same nickname, one of them is down, and you ask for
9361 them by nickname in your EntryNodes or ExitNodes. Also, try
9362 to pick the one that's running rather than an arbitrary one.
9363 - Fix an infinite loop we could hit if we go offline for too long.
9364 - Complain when we hit WSAENOBUFS on recv() or write() too.
9365 Perhaps this will help us hunt the bug.
9366 - If you're not a versioning dirserver, don't put the string
9367 "client-versions \nserver-versions \n" in your network-status.
9368 - Lower the minimum required number of file descriptors to 1000,
9369 so we can have some overhead for Valgrind on Linux, where the
9370 default ulimit -n is 1024.
9373 - Add tor.dizum.com as the fifth authoritative directory server.
9374 - Add a new config option FetchUselessDescriptors, off by default,
9375 for when you plan to run "exitlist" on your client and you want
9376 to know about even the non-running descriptors.
9379 Changes in version 0.1.1.17-rc - 2006-03-28
9381 - Clients and servers since 0.1.1.10-alpha have been expiring
9382 connections whenever they are idle for 5 minutes and they *do*
9383 have circuits on them. Oops. With this new version, clients will
9384 discard their previous entry guard choices and avoid choosing
9385 entry guards running these flawed versions.
9386 - Fix memory leak when uncompressing concatenated zlib streams. This
9387 was causing substantial leaks over time on Tor servers.
9388 - The v1 directory was including servers as much as 48 hours old,
9389 because that's how the new routerlist->routers works. Now only
9390 include them if they're 20 hours old or less.
9393 - Resume building on irix64, netbsd 2.0, etc.
9394 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
9396 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
9397 and it is confusing some users.
9398 - Mirrors stop caching the v1 directory so often.
9399 - Make the max number of old descriptors that a cache will hold
9400 rise with the number of directory authorities, so we can scale.
9401 - Change our win32 uname() hack to be more forgiving about what
9402 win32 versions it thinks it's found.
9405 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
9407 - When the controller's *setconf commands fail, collect an error
9408 message in a string and hand it back to the controller.
9409 - Make the v2 dir's "Fast" flag based on relative capacity, just
9410 like "Stable" is based on median uptime. Name everything in the
9411 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
9412 - Log server fingerprint on startup, so new server operators don't
9413 have to go hunting around their filesystem for it.
9414 - Return a robots.txt on our dirport to discourage google indexing.
9415 - Let the controller ask for GETINFO dir/status/foo so it can ask
9416 directly rather than connecting to the dir port. Only works when
9417 dirport is set for now.
9419 o New config options rather than constants in the code:
9420 - SocksTimeout: How long do we let a socks connection wait
9421 unattached before we fail it?
9422 - CircuitBuildTimeout: Cull non-open circuits that were born
9423 at least this many seconds ago.
9424 - CircuitIdleTimeout: Cull open clean circuits that were born
9425 at least this many seconds ago.
9428 Changes in version 0.1.1.16-rc - 2006-03-18
9429 o Bugfixes on 0.1.1.15-rc:
9430 - Fix assert when the controller asks to attachstream a connect-wait
9431 or resolve-wait stream.
9432 - Now do address rewriting when the controller asks us to attach
9433 to a particular circuit too. This will let Blossom specify
9434 "moria2.exit" without having to learn what moria2's IP address is.
9435 - Make the "tor --verify-config" command-line work again, so people
9436 can automatically check if their torrc will parse.
9437 - Authoritative dirservers no longer require an open connection from
9438 a server to consider him "reachable". We need this change because
9439 when we add new auth dirservers, old servers won't know not to
9441 - Let Tor build on Sun CC again.
9442 - Fix an off-by-one buffer size in dirserv.c that magically never
9443 hit our three authorities but broke sjmurdoch's own tor network.
9444 - If we as a directory mirror don't know of any v1 directory
9445 authorities, then don't try to cache any v1 directories.
9446 - Stop warning about unknown servers in our family when they are
9447 given as hex digests.
9448 - Stop complaining as quickly to the server operator that he
9449 hasn't registered his nickname/key binding.
9450 - Various cleanups so we can add new V2 Auth Dirservers.
9451 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
9452 reflect the updated flags in our v2 dir protocol.
9453 - Resume allowing non-printable characters for exit streams (both
9454 for connecting and for resolving). Now we tolerate applications
9455 that don't follow the RFCs. But continue to block malformed names
9458 o Bugfixes on 0.1.0.x:
9459 - Fix assert bug in close_logs(): when we close and delete logs,
9460 remove them all from the global "logfiles" list.
9461 - Fix minor integer overflow in calculating when we expect to use up
9462 our bandwidth allocation before hibernating.
9463 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
9464 there are multiple SSLs installed with different versions.
9465 - When we try to be a server and Address is not explicitly set and
9466 our hostname resolves to a private IP address, try to use an
9467 interface address if it has a public address. Now Windows machines
9468 that think of themselves as localhost can work by default.
9471 - Let the controller ask for GETINFO dir/server/foo so it can ask
9472 directly rather than connecting to the dir port.
9473 - Let the controller tell us about certain router descriptors
9474 that it doesn't want Tor to use in circuits. Implement
9475 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
9476 - New config option SafeSocks to reject all application connections
9477 using unsafe socks protocols. Defaults to off.
9480 Changes in version 0.1.1.15-rc - 2006-03-11
9481 o Bugfixes and cleanups:
9482 - When we're printing strings from the network, don't try to print
9483 non-printable characters. This protects us against shell escape
9484 sequence exploits, and also against attacks to fool humans into
9485 misreading their logs.
9486 - Fix a bug where Tor would fail to establish any connections if you
9487 left it off for 24 hours and then started it: we were happy with
9488 the obsolete network statuses, but they all referred to router
9489 descriptors that were too old to fetch, so we ended up with no
9490 valid router descriptors.
9491 - Fix a seg fault in the controller's "getinfo orconn-status"
9492 command while listing status on incoming handshaking connections.
9493 Introduce a status name "NEW" for these connections.
9494 - If we get a linelist or linelist_s config option from the torrc
9495 (e.g. ExitPolicy) and it has no value, warn and skip rather than
9496 silently resetting it to its default.
9497 - Don't abandon entry guards until they've been down or gone for
9499 - Cleaner and quieter log messages.
9502 - New controller signal NEWNYM that makes new application requests
9504 - Add a new circuit purpose 'controller' to let the controller ask
9505 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
9506 controller command to let you specify the purpose if you're
9507 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
9508 command to let you change a circuit's purpose after it's been
9510 - Accept "private:*" in routerdesc exit policies; not generated yet
9511 because older Tors do not understand it.
9512 - Add BSD-style contributed startup script "rc.subr" from Peter
9516 Changes in version 0.1.1.14-alpha - 2006-02-20
9517 o Bugfixes on 0.1.1.x:
9518 - Don't die if we ask for a stdout or stderr log (even implicitly)
9519 and we're set to RunAsDaemon -- just warn.
9520 - We still had a few bugs in the OR connection rotation code that
9521 caused directory servers to slowly aggregate connections to other
9522 fast Tor servers. This time for sure!
9523 - Make log entries on Win32 include the name of the function again.
9524 - We were treating a pair of exit policies if they were equal even
9525 if one said accept and the other said reject -- causing us to
9526 not always publish a new descriptor since we thought nothing
9528 - Retry pending server downloads as well as pending networkstatus
9529 downloads when we unexpectedly get a socks request.
9530 - We were ignoring the IS_FAST flag in the directory status,
9531 meaning we were willing to pick trivial-bandwidth nodes for "fast"
9533 - If the controller's SAVECONF command fails (e.g. due to file
9534 permissions), let the controller know that it failed.
9537 - If we're trying to be a Tor server and running Windows 95/98/ME
9538 as a server, explain that we'll likely crash.
9539 - When we're a server, a client asks for an old-style directory,
9540 and our write bucket is empty, don't give it to him. This way
9541 small servers can continue to serve the directory *sometimes*,
9542 without getting overloaded.
9543 - Compress exit policies even more -- look for duplicate lines
9545 - Clients now honor the "guard" flag in the router status when
9546 picking entry guards, rather than looking at is_fast or is_stable.
9547 - Retain unrecognized lines in $DATADIR/state file, so that we can
9548 be forward-compatible.
9549 - Generate 18.0.0.0/8 address policy format in descs when we can;
9550 warn when the mask is not reducible to a bit-prefix.
9551 - Let the user set ControlListenAddress in the torrc. This can be
9552 dangerous, but there are some cases (like a secured LAN) where it
9554 - Split ReachableAddresses into ReachableDirAddresses and
9555 ReachableORAddresses, so we can restrict Dir conns to port 80
9556 and OR conns to port 443.
9557 - Now we can target arch and OS in rpm builds (contributed by
9558 Phobos). Also make the resulting dist-rpm filename match the
9560 - New config options to help controllers: FetchServerDescriptors
9561 and FetchHidServDescriptors for whether to fetch server
9562 info and hidserv info or let the controller do it, and
9563 PublishServerDescriptor and PublishHidServDescriptors.
9564 - Also let the controller set the __AllDirActionsPrivate config
9565 option if you want all directory fetches/publishes to happen via
9566 Tor (it assumes your controller bootstraps your circuits).
9569 Changes in version 0.1.0.17 - 2006-02-17
9570 o Crash bugfixes on 0.1.0.x:
9571 - When servers with a non-zero DirPort came out of hibernation,
9572 sometimes they would trigger an assert.
9574 o Other important bugfixes:
9575 - On platforms that don't have getrlimit (like Windows), we were
9576 artificially constraining ourselves to a max of 1024
9577 connections. Now just assume that we can handle as many as 15000
9578 connections. Hopefully this won't cause other problems.
9580 o Backported features:
9581 - When we're a server, a client asks for an old-style directory,
9582 and our write bucket is empty, don't give it to him. This way
9583 small servers can continue to serve the directory *sometimes*,
9584 without getting overloaded.
9585 - Whenever you get a 503 in response to a directory fetch, try
9586 once more. This will become important once servers start sending
9587 503's whenever they feel busy.
9588 - Fetch a new directory every 120 minutes, not every 40 minutes.
9589 Now that we have hundreds of thousands of users running the old
9590 directory algorithm, it's starting to hurt a lot.
9591 - Bump up the period for forcing a hidden service descriptor upload
9592 from 20 minutes to 1 hour.
9595 Changes in version 0.1.1.13-alpha - 2006-02-09
9596 o Crashes in 0.1.1.x:
9597 - When you tried to setconf ORPort via the controller, Tor would
9598 crash. So people using TorCP to become a server were sad.
9599 - Solve (I hope) the stack-smashing bug that we were seeing on fast
9600 servers. The problem appears to be something do with OpenSSL's
9601 random number generation, or how we call it, or something. Let me
9602 know if the crashes continue.
9603 - Turn crypto hardware acceleration off by default, until we find
9604 somebody smart who can test it for us. (It appears to produce
9605 seg faults in at least some cases.)
9606 - Fix a rare assert error when we've tried all intro points for
9607 a hidden service and we try fetching the service descriptor again:
9608 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
9611 - Fix a major load balance bug: we were round-robining in 16 KB
9612 chunks, and servers with bandwidthrate of 20 KB, while downloading
9613 a 600 KB directory, would starve their other connections. Now we
9614 try to be a bit more fair.
9615 - Dir authorities and mirrors were never expiring the newest
9616 descriptor for each server, causing memory and directory bloat.
9617 - Fix memory-bloating and connection-bloating bug on servers: We
9618 were never closing any connection that had ever had a circuit on
9619 it, because we were checking conn->n_circuits == 0, yet we had a
9620 bug that let it go negative.
9621 - Make Tor work using squid as your http proxy again -- squid
9622 returns an error if you ask for a URL that's too long, and it uses
9623 a really generic error message. Plus, many people are behind a
9624 transparent squid so they don't even realize it.
9625 - On platforms that don't have getrlimit (like Windows), we were
9626 artificially constraining ourselves to a max of 1024
9627 connections. Now just assume that we can handle as many as 15000
9628 connections. Hopefully this won't cause other problems.
9629 - Add a new config option ExitPolicyRejectPrivate which defaults to
9630 1. This means all exit policies will begin with rejecting private
9631 addresses, unless the server operator explicitly turns it off.
9634 - Clients no longer download descriptors for non-running
9636 - Before we add new directory authorities, we should make it
9637 clear that only v1 authorities should receive/publish hidden
9638 service descriptors.
9641 - As soon as we've fetched some more directory info, immediately
9642 try to download more server descriptors. This way we don't have
9643 a 10 second pause during initial bootstrapping.
9644 - Remove even more loud log messages that the server operator can't
9646 - When we're running an obsolete or un-recommended version, make
9647 the log message more clear about what the problem is and what
9648 versions *are* still recommended.
9649 - Provide a more useful warn message when our onion queue gets full:
9650 the CPU is too slow or the exit policy is too liberal.
9651 - Don't warn when we receive a 503 from a dirserver/cache -- this
9652 will pave the way for them being able to refuse if they're busy.
9653 - When we fail to bind a listener, try to provide a more useful
9654 log message: e.g., "Is Tor already running?"
9655 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
9656 Goldberg can prove things about our handshake protocol more
9658 - MaxConn has been obsolete for a while now. Document the ConnLimit
9659 config option, which is a *minimum* number of file descriptors
9660 that must be available else Tor refuses to start.
9661 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
9662 if you log to syslog and want something other than LOG_DAEMON.
9663 - Make dirservers generate a separate "guard" flag to mean,
9664 "would make a good entry guard". Make clients parse it and vote
9665 on it. Not used by clients yet.
9666 - Implement --with-libevent-dir option to ./configure. Also, improve
9667 search techniques to find libevent, and use those for openssl too.
9668 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
9669 - Only start testing reachability once we've established a
9670 circuit. This will make startup on dirservers less noisy.
9671 - Don't try to upload hidden service descriptors until we have
9672 established a circuit.
9673 - Fix the controller's "attachstream 0" command to treat conn like
9674 it just connected, doing address remapping, handling .exit and
9675 .onion idioms, and so on. Now we're more uniform in making sure
9676 that the controller hears about new and closing connections.
9679 Changes in version 0.1.1.12-alpha - 2006-01-11
9680 o Bugfixes on 0.1.1.x:
9681 - The fix to close duplicate server connections was closing all
9682 Tor client connections if they didn't establish a circuit
9683 quickly enough. Oops.
9684 - Fix minor memory issue (double-free) that happened on exit.
9686 o Bugfixes on 0.1.0.x:
9687 - Tor didn't warn when it failed to open a log file.
9690 Changes in version 0.1.1.11-alpha - 2006-01-10
9691 o Crashes in 0.1.1.x:
9692 - Include all the assert/crash fixes from 0.1.0.16.
9693 - If you start Tor and then quit very quickly, there were some
9694 races that tried to free things that weren't allocated yet.
9695 - Fix a rare memory stomp if you're running hidden services.
9696 - Fix segfault when specifying DirServer in config without nickname.
9697 - Fix a seg fault when you finish connecting to a server but at
9698 that moment you dump his server descriptor.
9699 - Extendcircuit and Attachstream controller commands would
9700 assert/crash if you don't give them enough arguments.
9701 - Fix an assert error when we're out of space in the connection_list
9702 and we try to post a hidden service descriptor (reported by weasel).
9703 - If you specify a relative torrc path and you set RunAsDaemon in
9704 your torrc, then it chdir()'s to the new directory. If you HUP,
9705 it tries to load the new torrc location, fails, and exits.
9706 The fix: no longer allow a relative path to torrc using -f.
9709 - Implement "entry guards": automatically choose a handful of entry
9710 nodes and stick with them for all circuits. Only pick new guards
9711 when the ones you have are unsuitable, and if the old guards
9712 become suitable again, switch back. This will increase security
9713 dramatically against certain end-point attacks. The EntryNodes
9714 config option now provides some hints about which entry guards you
9715 want to use most; and StrictEntryNodes means to only use those.
9716 - New directory logic: download by descriptor digest, not by
9717 fingerprint. Caches try to download all listed digests from
9718 authorities; clients try to download "best" digests from caches.
9719 This avoids partitioning and isolating attacks better.
9720 - Make the "stable" router flag in network-status be the median of
9721 the uptimes of running valid servers, and make clients pay
9722 attention to the network-status flags. Thus the cutoff adapts
9723 to the stability of the network as a whole, making IRC, IM, etc
9724 connections more reliable.
9727 - Tor servers with dynamic IP addresses were needing to wait 18
9728 hours before they could start doing reachability testing using
9729 the new IP address and ports. This is because they were using
9730 the internal descriptor to learn what to test, yet they were only
9731 rebuilding the descriptor once they decided they were reachable.
9732 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
9733 to download certain server descriptors, throw them away, and then
9734 fetch them again after 30 minutes. Now mirrors throw away these
9735 server descriptors so clients can't get them.
9736 - We were leaving duplicate connections to other ORs open for a week,
9737 rather than closing them once we detect a duplicate. This only
9738 really affected authdirservers, but it affected them a lot.
9739 - Spread the authdirservers' reachability testing over the entire
9740 testing interval, so we don't try to do 500 TLS's at once every
9744 - If the network is down, and we try to connect to a conn because
9745 we have a circuit in mind, and we timeout (30 seconds) because the
9746 network never answers, we were expiring the circuit, but we weren't
9747 obsoleting the connection or telling the entry_guards functions.
9748 - Some Tor servers process billions of cells per day. These statistics
9749 need to be uint64_t's.
9750 - Check for integer overflows in more places, when adding elements
9751 to smartlists. This could possibly prevent a buffer overflow
9752 on malicious huge inputs. I don't see any, but I haven't looked
9754 - ReachableAddresses kept growing new "reject *:*" lines on every
9756 - When you "setconf log" via the controller, it should remove all
9757 logs. We were automatically adding back in a "log notice stdout".
9758 - Newly bootstrapped Tor networks couldn't establish hidden service
9759 circuits until they had nodes with high uptime. Be more tolerant.
9760 - We were marking servers down when they could not answer every piece
9761 of the directory request we sent them. This was far too harsh.
9762 - Fix the torify (tsocks) config file to not use Tor for localhost
9764 - Directory authorities now go to the proper authority when asking for
9765 a networkstatus, even when they want a compressed one.
9766 - Fix a harmless bug that was causing Tor servers to log
9767 "Got an end because of misc error, but we're not an AP. Closing."
9768 - Authorities were treating their own descriptor changes as cosmetic,
9769 meaning the descriptor available in the network-status and the
9770 descriptor that clients downloaded were different.
9771 - The OS X installer was adding a symlink for tor_resolve but
9772 the binary was called tor-resolve (reported by Thomas Hardly).
9773 - Workaround a problem with some http proxies where they refuse GET
9774 requests that specify "Content-Length: 0" (reported by Adrian).
9775 - Fix wrong log message when you add a "HiddenServiceNodes" config
9776 line without any HiddenServiceDir line (reported by Chris Thomas).
9779 - Write the TorVersion into the state file so we have a prayer of
9780 keeping forward and backward compatibility.
9781 - Revive the FascistFirewall config option rather than eliminating it:
9782 now it's a synonym for ReachableAddresses *:80,*:443.
9783 - Clients choose directory servers from the network status lists,
9784 not from their internal list of router descriptors. Now they can
9785 go to caches directly rather than needing to go to authorities
9787 - Directory authorities ignore router descriptors that have only
9788 cosmetic differences: do this for 0.1.0.x servers now too.
9789 - Add a new flag to network-status indicating whether the server
9790 can answer v2 directory requests too.
9791 - Authdirs now stop whining so loudly about bad descriptors that
9792 they fetch from other dirservers. So when there's a log complaint,
9793 it's for sure from a freshly uploaded descriptor.
9794 - Reduce memory requirements in our structs by changing the order
9796 - There used to be two ways to specify your listening ports in a
9797 server descriptor: on the "router" line and with a separate "ports"
9798 line. Remove support for the "ports" line.
9799 - New config option "AuthDirRejectUnlisted" for auth dirservers as
9800 a panic button: if we get flooded with unusable servers we can
9801 revert to only listing servers in the approved-routers file.
9802 - Auth dir servers can now mark a fingerprint as "!reject" or
9803 "!invalid" in the approved-routers file (as its nickname), to
9804 refuse descriptors outright or include them but marked as invalid.
9805 - Servers store bandwidth history across restarts/crashes.
9806 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
9807 get a better idea of why their circuits failed. Not used yet.
9808 - Directory mirrors now cache up to 16 unrecognized network-status
9809 docs. Now we can add new authdirservers and they'll be cached too.
9810 - When picking a random directory, prefer non-authorities if any
9812 - New controller option "getinfo desc/all-recent" to fetch the
9813 latest server descriptor for every router that Tor knows about.
9816 Changes in version 0.1.0.16 - 2006-01-02
9817 o Crash bugfixes on 0.1.0.x:
9818 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
9819 corrupting the heap, losing FDs, or crashing when we need to resize
9820 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
9821 - It turns out sparc64 platforms crash on unaligned memory access
9822 too -- so detect and avoid this.
9823 - Handle truncated compressed data correctly (by detecting it and
9825 - Fix possible-but-unlikely free(NULL) in control.c.
9826 - When we were closing connections, there was a rare case that
9827 stomped on memory, triggering seg faults and asserts.
9828 - Avoid potential infinite recursion when building a descriptor. (We
9829 don't know that it ever happened, but better to fix it anyway.)
9830 - We were neglecting to unlink marked circuits from soon-to-close OR
9831 connections, which caused some rare scribbling on freed memory.
9832 - Fix a memory stomping race bug when closing the joining point of two
9833 rendezvous circuits.
9834 - Fix an assert in time parsing found by Steven Murdoch.
9836 o Other bugfixes on 0.1.0.x:
9837 - When we're doing reachability testing, provide more useful log
9838 messages so the operator knows what to expect.
9839 - Do not check whether DirPort is reachable when we are suppressing
9840 advertising it because of hibernation.
9841 - When building with -static or on Solaris, we sometimes needed -ldl.
9842 - When we're deciding whether a stream has enough circuits around
9843 that can handle it, count the freshly dirty ones and not the ones
9844 that are so dirty they won't be able to handle it.
9845 - When we're expiring old circuits, we had a logic error that caused
9846 us to close new rendezvous circuits rather than old ones.
9847 - Give a more helpful log message when you try to change ORPort via
9848 the controller: you should upgrade Tor if you want that to work.
9849 - We were failing to parse Tor versions that start with "Tor ".
9850 - Tolerate faulty streams better: when a stream fails for reason
9851 exitpolicy, stop assuming that the router is lying about his exit
9852 policy. When a stream fails for reason misc, allow it to retry just
9853 as if it was resolvefailed. When a stream has failed three times,
9854 reset its failure count so we can try again and get all three tries.
9857 Changes in version 0.1.1.10-alpha - 2005-12-11
9858 o Correctness bugfixes on 0.1.0.x:
9859 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
9860 corrupting the heap, losing FDs, or crashing when we need to resize
9861 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
9862 - Stop doing the complex voodoo overkill checking for insecure
9863 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
9864 - When we were closing connections, there was a rare case that
9865 stomped on memory, triggering seg faults and asserts.
9866 - We were neglecting to unlink marked circuits from soon-to-close OR
9867 connections, which caused some rare scribbling on freed memory.
9868 - When we're deciding whether a stream has enough circuits around
9869 that can handle it, count the freshly dirty ones and not the ones
9870 that are so dirty they won't be able to handle it.
9871 - Recover better from TCP connections to Tor servers that are
9872 broken but don't tell you (it happens!); and rotate TLS
9873 connections once a week.
9874 - When we're expiring old circuits, we had a logic error that caused
9875 us to close new rendezvous circuits rather than old ones.
9876 - Fix a scary-looking but apparently harmless bug where circuits
9877 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
9878 servers, and never switch to state CIRCUIT_STATE_OPEN.
9879 - When building with -static or on Solaris, we sometimes needed to
9881 - Give a useful message when people run Tor as the wrong user,
9882 rather than telling them to start chowning random directories.
9883 - We were failing to inform the controller about new .onion streams.
9885 o Security bugfixes on 0.1.0.x:
9886 - Refuse server descriptors if the fingerprint line doesn't match
9887 the included identity key. Tor doesn't care, but other apps (and
9888 humans) might actually be trusting the fingerprint line.
9889 - We used to kill the circuit when we receive a relay command we
9890 don't recognize. Now we just drop it.
9891 - Start obeying our firewall options more rigorously:
9892 . If we can't get to a dirserver directly, try going via Tor.
9893 . Don't ever try to connect (as a client) to a place our
9894 firewall options forbid.
9895 . If we specify a proxy and also firewall options, obey the
9896 firewall options even when we're using the proxy: some proxies
9897 can only proxy to certain destinations.
9898 - Fix a bug found by Lasse Overlier: when we were making internal
9899 circuits (intended to be cannibalized later for rendezvous and
9900 introduction circuits), we were picking them so that they had
9901 useful exit nodes. There was no need for this, and it actually
9902 aids some statistical attacks.
9903 - Start treating internal circuits and exit circuits separately.
9904 It's important to keep them separate because internal circuits
9905 have their last hops picked like middle hops, rather than like
9906 exit hops. So exiting on them will break the user's expectations.
9908 o Bugfixes on 0.1.1.x:
9909 - Take out the mis-feature where we tried to detect IP address
9910 flapping for people with DynDNS, and chose not to upload a new
9911 server descriptor sometimes.
9912 - Try to be compatible with OpenSSL 0.9.6 again.
9913 - Log fix: when the controller is logging about .onion addresses,
9914 sometimes it didn't include the ".onion" part of the address.
9915 - Don't try to modify options->DirServers internally -- if the
9916 user didn't specify any, just add the default ones directly to
9917 the trusted dirserver list. This fixes a bug where people running
9918 controllers would use SETCONF on some totally unrelated config
9919 option, and Tor would start yelling at them about changing their
9921 - Let the controller's redirectstream command specify a port, in
9922 case the controller wants to change that too.
9923 - When we requested a pile of server descriptors, we sometimes
9924 accidentally launched a duplicate request for the first one.
9925 - Bugfix for trackhostexits: write down the fingerprint of the
9926 chosen exit, not its nickname, because the chosen exit might not
9928 - When parsing foo.exit, if foo is unknown, and we are leaving
9929 circuits unattached, set the chosen_exit field and leave the
9930 address empty. This matters because controllers got confused
9932 - Directory authorities no longer try to download server
9933 descriptors that they know they will reject.
9935 o Features and updates:
9936 - Replace balanced trees with hash tables: this should make stuff
9937 significantly faster.
9938 - Resume using the AES counter-mode implementation that we ship,
9939 rather than OpenSSL's. Ours is significantly faster.
9940 - Many other CPU and memory improvements.
9941 - Add a new config option FastFirstHopPK (on by default) so clients
9942 do a trivial crypto handshake for their first hop, since TLS has
9943 already taken care of confidentiality and authentication.
9944 - Add a new config option TestSocks so people can see if their
9945 applications are using socks4, socks4a, socks5-with-ip, or
9946 socks5-with-hostname. This way they don't have to keep mucking
9947 with tcpdump and wondering if something got cached somewhere.
9948 - Warn when listening on a public address for socks. I suspect a
9949 lot of people are setting themselves up as open socks proxies,
9950 and they have no idea that jerks on the Internet are using them,
9951 since they simply proxy the traffic into the Tor network.
9952 - Add "private:*" as an alias in configuration for policies. Now
9953 you can simplify your exit policy rather than needing to list
9954 every single internal or nonroutable network space.
9955 - Add a new controller event type that allows controllers to get
9956 all server descriptors that were uploaded to a router in its role
9957 as authoritative dirserver.
9958 - Start shipping socks-extensions.txt, tor-doc-unix.html,
9959 tor-doc-server.html, and stylesheet.css in the tarball.
9960 - Stop shipping tor-doc.html in the tarball.
9963 Changes in version 0.1.1.9-alpha - 2005-11-15
9964 o Usability improvements:
9965 - Start calling it FooListenAddress rather than FooBindAddress,
9966 since few of our users know what it means to bind an address
9968 - Reduce clutter in server logs. We're going to try to make
9969 them actually usable now. New config option ProtocolWarnings that
9970 lets you hear about how _other Tors_ are breaking the protocol. Off
9972 - Divide log messages into logging domains. Once we put some sort
9973 of interface on this, it will let people looking at more verbose
9974 log levels specify the topics they want to hear more about.
9975 - Make directory servers return better http 404 error messages
9976 instead of a generic "Servers unavailable".
9977 - Check for even more Windows version flags when writing the platform
9978 string in server descriptors, and note any we don't recognize.
9979 - Clean up more of the OpenSSL memory when exiting, so we can detect
9980 memory leaks better.
9981 - Make directory authorities be non-versioning, non-naming by
9982 default. Now we can add new directory servers without requiring
9983 their operators to pay close attention.
9984 - When logging via syslog, include the pid whenever we provide
9985 a log entry. Suggested by Todd Fries.
9987 o Performance improvements:
9988 - Directory servers now silently throw away new descriptors that
9989 haven't changed much if the timestamps are similar. We do this to
9990 tolerate older Tor servers that upload a new descriptor every 15
9991 minutes. (It seemed like a good idea at the time.)
9992 - Inline bottleneck smartlist functions; use fast versions by default.
9993 - Add a "Map from digest to void*" abstraction digestmap_t so we
9994 can do less hex encoding/decoding. Use it in router_get_by_digest()
9995 to resolve a performance bottleneck.
9996 - Allow tor_gzip_uncompress to extract as much as possible from
9997 truncated compressed data. Try to extract as many
9998 descriptors as possible from truncated http responses (when
9999 DIR_PURPOSE_FETCH_ROUTERDESC).
10000 - Make circ->onionskin a pointer, not a static array. moria2 was using
10001 125000 circuit_t's after it had been up for a few weeks, which
10002 translates to 20+ megs of wasted space.
10003 - The private half of our EDH handshake keys are now chosen out
10004 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
10006 o Security improvements:
10007 - Start making directory caches retain old routerinfos, so soon
10008 clients can start asking by digest of descriptor rather than by
10009 fingerprint of server.
10010 - Add half our entropy from RAND_poll in OpenSSL. This knows how
10011 to use egd (if present), openbsd weirdness (if present), vms/os2
10012 weirdness (if we ever port there), and more in the future.
10014 o Bugfixes on 0.1.0.x:
10015 - Do round-robin writes of at most 16 kB per write. This might be
10016 more fair on loaded Tor servers, and it might resolve our Windows
10017 crash bug. It might also slow things down.
10018 - Our TLS handshakes were generating a single public/private
10019 keypair for the TLS context, rather than making a new one for
10020 each new connections. Oops. (But we were still rotating them
10021 periodically, so it's not so bad.)
10022 - When we were cannibalizing a circuit with a particular exit
10023 node in mind, we weren't checking to see if that exit node was
10024 already present earlier in the circuit. Oops.
10025 - When a Tor server's IP changes (e.g. from a dyndns address),
10026 upload a new descriptor so clients will learn too.
10027 - Really busy servers were keeping enough circuits open on stable
10028 connections that they were wrapping around the circuit_id
10029 space. (It's only two bytes.) This exposed a bug where we would
10030 feel free to reuse a circuit_id even if it still exists but has
10031 been marked for close. Try to fix this bug. Some bug remains.
10032 - If we would close a stream early (e.g. it asks for a .exit that
10033 we know would refuse it) but the LeaveStreamsUnattached config
10034 option is set by the controller, then don't close it.
10036 o Bugfixes on 0.1.1.8-alpha:
10037 - Fix a big pile of memory leaks, some of them serious.
10038 - Do not try to download a routerdesc if we would immediately reject
10040 - Resume inserting a newline between all router descriptors when
10041 generating (old style) signed directories, since our spec says
10043 - When providing content-type application/octet-stream for
10044 server descriptors using .z, we were leaving out the
10045 content-encoding header. Oops. (Everything tolerated this just
10046 fine, but that doesn't mean we need to be part of the problem.)
10047 - Fix a potential seg fault in getconf and getinfo using version 1
10048 of the controller protocol.
10049 - Avoid crash: do not check whether DirPort is reachable when we
10050 are suppressing it because of hibernation.
10051 - Make --hash-password not crash on exit.
10054 Changes in version 0.1.1.8-alpha - 2005-10-07
10055 o New features (major):
10056 - Clients don't download or use the directory anymore. Now they
10057 download and use network-statuses from the trusted dirservers,
10058 and fetch individual server descriptors as needed from mirrors.
10059 See dir-spec.txt for all the gory details.
10060 - Be more conservative about whether to advertise our DirPort.
10061 The main change is to not advertise if we're running at capacity
10062 and either a) we could hibernate or b) our capacity is low and
10063 we're using a default DirPort.
10064 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
10066 o New features (minor):
10067 - Try to be smart about when to retry network-status and
10068 server-descriptor fetches. Still needs some tuning.
10069 - Stop parsing, storing, or using running-routers output (but
10070 mirrors still cache and serve it).
10071 - Consider a threshold of versioning dirservers (dirservers who have
10072 an opinion about which Tor versions are still recommended) before
10073 deciding whether to warn the user that he's obsolete.
10074 - Dirservers can now reject/invalidate by key and IP, with the
10075 config options "AuthDirInvalid" and "AuthDirReject". This is
10076 useful since currently we automatically list servers as running
10077 and usable even if we know they're jerks.
10078 - Provide dire warnings to any users who set DirServer; move it out
10079 of torrc.sample and into torrc.complete.
10080 - Add MyFamily to torrc.sample in the server section.
10081 - Add nicknames to the DirServer line, so we can refer to them
10082 without requiring all our users to memorize their IP addresses.
10083 - When we get an EOF or a timeout on a directory connection, note
10084 how many bytes of serverdesc we are dropping. This will help
10085 us determine whether it is smart to parse incomplete serverdesc
10087 - Add a new function to "change pseudonyms" -- that is, to stop
10088 using any currently-dirty circuits for new streams, so we don't
10089 link new actions to old actions. Currently it's only called on
10090 HUP (or SIGNAL RELOAD).
10091 - On sighup, if UseHelperNodes changed to 1, use new circuits.
10092 - Start using RAND_bytes rather than RAND_pseudo_bytes from
10093 OpenSSL. Also, reseed our entropy every hour, not just at
10094 startup. And entropy in 512-bit chunks, not 160-bit chunks.
10096 o Fixes on 0.1.1.7-alpha:
10097 - Nobody ever implemented EVENT_ADDRMAP for control protocol
10098 version 0, so don't let version 0 controllers ask for it.
10099 - If you requested something with too many newlines via the
10100 v1 controller protocol, you could crash tor.
10101 - Fix a number of memory leaks, including some pretty serious ones.
10102 - Re-enable DirPort testing again, so Tor servers will be willing
10103 to advertise their DirPort if it's reachable.
10104 - On TLS handshake, only check the other router's nickname against
10105 its expected nickname if is_named is set.
10107 o Fixes forward-ported from 0.1.0.15:
10108 - Don't crash when we don't have any spare file descriptors and we
10109 try to spawn a dns or cpu worker.
10110 - Make the numbers in read-history and write-history into uint64s,
10111 so they don't overflow and publish negatives in the descriptor.
10113 o Fixes on 0.1.0.x:
10114 - For the OS X package's modified privoxy config file, comment
10115 out the "logfile" line so we don't log everything passed
10117 - We were whining about using socks4 or socks5-with-local-lookup
10118 even when it's an IP in the "virtual" range we designed exactly
10120 - We were leaking some memory every time the client changes IPs.
10121 - Never call free() on tor_malloc()d memory. This will help us
10122 use dmalloc to detect memory leaks.
10123 - Check for named servers when looking them up by nickname;
10124 warn when we'recalling a non-named server by its nickname;
10125 don't warn twice about the same name.
10126 - Try to list MyFamily elements by key, not by nickname, and warn
10127 if we've not heard of the server.
10128 - Make windows platform detection (uname equivalent) smarter.
10129 - It turns out sparc64 doesn't like unaligned access either.
10132 Changes in version 0.1.0.15 - 2005-09-23
10133 o Bugfixes on 0.1.0.x:
10134 - Reject ports 465 and 587 (spam targets) in default exit policy.
10135 - Don't crash when we don't have any spare file descriptors and we
10136 try to spawn a dns or cpu worker.
10137 - Get rid of IgnoreVersion undocumented config option, and make us
10138 only warn, never exit, when we're running an obsolete version.
10139 - Don't try to print a null string when your server finds itself to
10140 be unreachable and the Address config option is empty.
10141 - Make the numbers in read-history and write-history into uint64s,
10142 so they don't overflow and publish negatives in the descriptor.
10143 - Fix a minor memory leak in smartlist_string_remove().
10144 - We were only allowing ourselves to upload a server descriptor at
10145 most every 20 minutes, even if it changed earlier than that.
10146 - Clean up log entries that pointed to old URLs.
10149 Changes in version 0.1.1.7-alpha - 2005-09-14
10150 o Fixes on 0.1.1.6-alpha:
10151 - Exit servers were crashing when people asked them to make a
10152 connection to an address not in their exit policy.
10153 - Looking up a non-existent stream for a v1 control connection would
10155 - Fix a seg fault if we ask a dirserver for a descriptor by
10156 fingerprint but he doesn't know about him.
10157 - SETCONF was appending items to linelists, not clearing them.
10158 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
10159 out and refuse the setconf if it would fail.
10160 - Downgrade the dirserver log messages when whining about
10164 - Add Peter Palfrader's check-tor script to tor/contrib/
10165 It lets you easily check whether a given server (referenced by
10166 nickname) is reachable by you.
10167 - Numerous changes to move towards client-side v2 directories. Not
10170 o Fixes on 0.1.0.x:
10171 - If the user gave tor an odd number of command-line arguments,
10172 we were silently ignoring the last one. Now we complain and fail.
10173 [This wins the oldest-bug prize -- this bug has been present since
10174 November 2002, as released in Tor 0.0.0.]
10175 - Do not use unaligned memory access on alpha, mips, or mipsel.
10176 It *works*, but is very slow, so we treat them as if it doesn't.
10177 - Retry directory requests if we fail to get an answer we like
10178 from a given dirserver (we were retrying before, but only if
10179 we fail to connect).
10180 - When writing the RecommendedVersions line, sort them first.
10181 - When the client asked for a rendezvous port that the hidden
10182 service didn't want to provide, we were sending an IP address
10183 back along with the end cell. Fortunately, it was zero. But stop
10185 - Correct "your server is reachable" log entries to indicate that
10186 it was self-testing that told us so.
10189 Changes in version 0.1.1.6-alpha - 2005-09-09
10190 o Fixes on 0.1.1.5-alpha:
10191 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
10192 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
10193 - Fix bug with tor_memmem finding a match at the end of the string.
10194 - Make unit tests run without segfaulting.
10195 - Resolve some solaris x86 compile warnings.
10196 - Handle duplicate lines in approved-routers files without warning.
10197 - Fix bug where as soon as a server refused any requests due to his
10198 exit policy (e.g. when we ask for localhost and he tells us that's
10199 127.0.0.1 and he won't do it), we decided he wasn't obeying his
10200 exit policy using him for any exits.
10201 - Only do openssl hardware accelerator stuff if openssl version is
10204 o New controller features/fixes:
10205 - Add a "RESETCONF" command so you can set config options like
10206 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
10207 a config option in the torrc with no value, then it clears it
10208 entirely (rather than setting it to its default).
10209 - Add a "GETINFO config-file" to tell us where torrc is.
10210 - Avoid sending blank lines when GETINFO replies should be empty.
10211 - Add a QUIT command for the controller (for using it manually).
10212 - Fix a bug in SAVECONF that was adding default dirservers and
10213 other redundant entries to the torrc file.
10215 o Start on the new directory design:
10216 - Generate, publish, cache, serve new network-status format.
10217 - Publish individual descriptors (by fingerprint, by "all", and by
10219 - Publish client and server recommended versions separately.
10220 - Allow tor_gzip_uncompress() to handle multiple concatenated
10221 compressed strings. Serve compressed groups of router
10222 descriptors. The compression logic here could be more
10224 - Distinguish v1 authorities (all currently trusted directories)
10225 from v2 authorities (all trusted directories).
10226 - Change DirServers config line to note which dirs are v1 authorities.
10227 - Add configuration option "V1AuthoritativeDirectory 1" which
10228 moria1, moria2, and tor26 should set.
10229 - Remove option when getting directory cache to see whether they
10230 support running-routers; they all do now. Replace it with one
10231 to see whether caches support v2 stuff.
10234 - Dirservers now do their own external reachability testing of each
10235 Tor server, and only list them as running if they've been found to
10236 be reachable. We also send back warnings to the server's logs if
10237 it uploads a descriptor that we already believe is unreachable.
10238 - Implement exit enclaves: if we know an IP address for the
10239 destination, and there's a running Tor server at that address
10240 which allows exit to the destination, then extend the circuit to
10241 that exit first. This provides end-to-end encryption and end-to-end
10242 authentication. Also, if the user wants a .exit address or enclave,
10243 use 4 hops rather than 3, and cannibalize a general circ for it
10245 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
10246 controller. Also, rotate dns and cpu workers if the controller
10247 changes options that will affect them; and initialize the dns
10248 worker cache tree whether or not we start out as a server.
10249 - Only upload a new server descriptor when options change, 18
10250 hours have passed, uptime is reset, or bandwidth changes a lot.
10251 - Check [X-]Forwarded-For headers in HTTP requests when generating
10252 log messages. This lets people run dirservers (and caches) behind
10253 Apache but still know which IP addresses are causing warnings.
10255 o Config option changes:
10256 - Replace (Fascist)Firewall* config options with a new
10257 ReachableAddresses option that understands address policies.
10258 For example, "ReachableAddresses *:80,*:443"
10259 - Get rid of IgnoreVersion undocumented config option, and make us
10260 only warn, never exit, when we're running an obsolete version.
10261 - Make MonthlyAccountingStart config option truly obsolete now.
10263 o Fixes on 0.1.0.x:
10264 - Reject ports 465 and 587 in the default exit policy, since
10265 people have started using them for spam too.
10266 - It turns out we couldn't bootstrap a network since we added
10267 reachability detection in 0.1.0.1-rc. Good thing the Tor network
10268 has never gone down. Add an AssumeReachable config option to let
10269 servers and dirservers bootstrap. When we're trying to build a
10270 high-uptime or high-bandwidth circuit but there aren't enough
10271 suitable servers, try being less picky rather than simply failing.
10272 - Our logic to decide if the OR we connected to was the right guy
10273 was brittle and maybe open to a mitm for unverified routers.
10274 - We weren't cannibalizing circuits correctly for
10275 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
10276 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
10277 build those from scratch. This should make hidden services faster.
10278 - Predict required circuits better, with an eye toward making hidden
10279 services faster on the service end.
10280 - Retry streams if the exit node sends back a 'misc' failure. This
10281 should result in fewer random failures. Also, after failing
10282 from resolve failed or misc, reset the num failures, so we give
10283 it a fair shake next time we try.
10284 - Clean up the rendezvous warn log msgs, and downgrade some to info.
10285 - Reduce severity on logs about dns worker spawning and culling.
10286 - When we're shutting down and we do something like try to post a
10287 server descriptor or rendezvous descriptor, don't complain that
10288 we seem to be unreachable. Of course we are, we're shutting down.
10289 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
10290 We don't use them yet, but maybe one day our DNS resolver will be
10291 able to discover them.
10292 - Make ContactInfo mandatory for authoritative directory servers.
10293 - Require server descriptors to list IPv4 addresses -- hostnames
10294 are no longer allowed. This also fixes some potential security
10295 problems with people providing hostnames as their address and then
10296 preferentially resolving them to partition users.
10297 - Change log line for unreachability to explicitly suggest /etc/hosts
10298 as the culprit. Also make it clearer what IP address and ports we're
10299 testing for reachability.
10300 - Put quotes around user-supplied strings when logging so users are
10301 more likely to realize if they add bad characters (like quotes)
10303 - Let auth dir servers start without specifying an Address config
10305 - Make unit tests (and other invocations that aren't the real Tor)
10306 run without launching listeners, creating subdirectories, and so on.
10309 Changes in version 0.1.1.5-alpha - 2005-08-08
10310 o Bugfixes included in 0.1.0.14.
10312 o Bugfixes on 0.1.0.x:
10313 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
10314 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
10315 it would silently using ignore the 6668.
10318 Changes in version 0.1.0.14 - 2005-08-08
10319 o Bugfixes on 0.1.0.x:
10320 - Fix the other half of the bug with crypto handshakes
10322 - Fix an assert trigger if you send a 'signal term' via the
10323 controller when it's listening for 'event info' messages.
10326 Changes in version 0.1.1.4-alpha - 2005-08-04
10327 o Bugfixes included in 0.1.0.13.
10330 - Improve tor_gettimeofday() granularity on windows.
10331 - Make clients regenerate their keys when their IP address changes.
10332 - Implement some more GETINFO goodness: expose helper nodes, config
10333 options, getinfo keys.
10336 Changes in version 0.1.0.13 - 2005-08-04
10337 o Bugfixes on 0.1.0.x:
10338 - Fix a critical bug in the security of our crypto handshakes.
10339 - Fix a size_t underflow in smartlist_join_strings2() that made
10340 it do bad things when you hand it an empty smartlist.
10341 - Fix Windows installer to ship Tor license (thanks to Aphex for
10342 pointing out this oversight) and put a link to the doc directory
10344 - Explicitly set no-unaligned-access for sparc: it turns out the
10345 new gcc's let you compile broken code, but that doesn't make it
10349 Changes in version 0.1.1.3-alpha - 2005-07-23
10350 o Bugfixes on 0.1.1.2-alpha:
10351 - Fix a bug in handling the controller's "post descriptor"
10353 - Fix several bugs in handling the controller's "extend circuit"
10355 - Fix a bug in handling the controller's "stream status" event.
10356 - Fix an assert failure if we have a controller listening for
10357 circuit events and we go offline.
10358 - Re-allow hidden service descriptors to publish 0 intro points.
10359 - Fix a crash when generating your hidden service descriptor if
10360 you don't have enough intro points already.
10362 o New features on 0.1.1.2-alpha:
10363 - New controller function "getinfo accounting", to ask how
10364 many bytes we've used in this time period.
10365 - Experimental support for helper nodes: a lot of the risk from
10366 a small static adversary comes because users pick new random
10367 nodes every time they rebuild a circuit. Now users will try to
10368 stick to the same small set of entry nodes if they can. Not
10369 enabled by default yet.
10371 o Bugfixes on 0.1.0.12:
10372 - If you're an auth dir server, always publish your dirport,
10373 even if you haven't yet found yourself to be reachable.
10374 - Fix a size_t underflow in smartlist_join_strings2() that made
10375 it do bad things when you hand it an empty smartlist.
10378 Changes in version 0.1.0.12 - 2005-07-18
10379 o New directory servers:
10380 - tor26 has changed IP address.
10382 o Bugfixes on 0.1.0.x:
10383 - Fix a possible double-free in tor_gzip_uncompress().
10384 - When --disable-threads is set, do not search for or link against
10385 pthreads libraries.
10386 - Don't trigger an assert if an authoritative directory server
10387 claims its dirport is 0.
10388 - Fix bug with removing Tor as an NT service: some people were
10389 getting "The service did not return an error." Thanks to Matt
10393 Changes in version 0.1.1.2-alpha - 2005-07-15
10394 o New directory servers:
10395 - tor26 has changed IP address.
10397 o Bugfixes on 0.1.0.x, crashes/leaks:
10398 - Port the servers-not-obeying-their-exit-policies fix from
10400 - Fix an fd leak in start_daemon().
10401 - On Windows, you can't always reopen a port right after you've
10402 closed it. So change retry_listeners() to only close and re-open
10403 ports that have changed.
10404 - Fix a possible double-free in tor_gzip_uncompress().
10406 o Bugfixes on 0.1.0.x, usability:
10407 - When tor_socketpair() fails in Windows, give a reasonable
10408 Windows-style errno back.
10409 - Let people type "tor --install" as well as "tor -install" when
10411 want to make it an NT service.
10412 - NT service patch from Matt Edman to improve error messages.
10413 - When the controller asks for a config option with an abbreviated
10414 name, give the full name in our response.
10415 - Correct the man page entry on TrackHostExitsExpire.
10416 - Looks like we were never delivering deflated (i.e. compressed)
10417 running-routers lists, even when asked. Oops.
10418 - When --disable-threads is set, do not search for or link against
10419 pthreads libraries.
10421 o Bugfixes on 0.1.1.x:
10422 - Fix a seg fault with autodetecting which controller version is
10426 - New hidden service descriptor format: put a version in it, and
10427 let people specify introduction/rendezvous points that aren't
10428 in "the directory" (which is subjective anyway).
10429 - Allow the DEBUG controller event to work again. Mark certain log
10430 entries as "don't tell this to controllers", so we avoid cycles.
10433 Changes in version 0.1.0.11 - 2005-06-30
10434 o Bugfixes on 0.1.0.x:
10435 - Fix major security bug: servers were disregarding their
10436 exit policies if clients behaved unexpectedly.
10437 - Make OS X init script check for missing argument, so we don't
10438 confuse users who invoke it incorrectly.
10439 - Fix a seg fault in "tor --hash-password foo".
10440 - The MAPADDRESS control command was broken.
10443 Changes in version 0.1.1.1-alpha - 2005-06-29
10445 - Make OS X init script check for missing argument, so we don't
10446 confuse users who invoke it incorrectly.
10447 - Fix a seg fault in "tor --hash-password foo".
10448 - Fix a possible way to DoS dirservers.
10449 - When we complain that your exit policy implicitly allows local or
10450 private address spaces, name them explicitly so operators can
10452 - Make the log message less scary when all the dirservers are
10453 temporarily unreachable.
10454 - We were printing the number of idle dns workers incorrectly when
10458 - Revised controller protocol (version 1) that uses ascii rather
10459 than binary. Add supporting libraries in python and java so you
10460 can use the controller from your applications without caring how
10461 our protocol works.
10462 - Spiffy new support for crypto hardware accelerators. Can somebody
10466 Changes in version 0.0.9.10 - 2005-06-16
10467 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
10468 - Refuse relay cells that claim to have a length larger than the
10469 maximum allowed. This prevents a potential attack that could read
10470 arbitrary memory (e.g. keys) from an exit server's process
10474 Changes in version 0.1.0.10 - 2005-06-14
10475 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
10476 libevent before 1.1a.
10479 Changes in version 0.1.0.9-rc - 2005-06-09
10481 - Reset buf->highwater every time buf_shrink() is called, not just on
10482 a successful shrink. This was causing significant memory bloat.
10483 - Fix buffer overflow when checking hashed passwords.
10484 - Security fix: if seeding the RNG on Win32 fails, quit.
10485 - Allow seeding the RNG on Win32 even when you're not running as
10487 - Disable threading on Solaris too. Something is wonky with it,
10488 cpuworkers, and reentrant libs.
10489 - Reenable the part of the code that tries to flush as soon as an
10490 OR outbuf has a full TLS record available. Perhaps this will make
10491 OR outbufs not grow as huge except in rare cases, thus saving lots
10492 of CPU time plus memory.
10493 - Reject malformed .onion addresses rather then passing them on as
10494 normal web requests.
10495 - Adapt patch from Adam Langley: fix possible memory leak in
10496 tor_lookup_hostname().
10497 - Initialize libevent later in the startup process, so the logs are
10498 already established by the time we start logging libevent warns.
10499 - Use correct errno on win32 if libevent fails.
10500 - Check and warn about known-bad/slow libevent versions.
10501 - Pay more attention to the ClientOnly config option.
10502 - Have torctl.in/tor.sh.in check for location of su binary (needed
10504 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
10505 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
10506 HttpProxyAuthenticator
10507 - Stop warning about sigpipes in the logs. We're going to
10508 pretend that getting these occassionally is normal and fine.
10509 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
10511 installer screens; and don't put stuff into StartupItems unless
10512 the user asks you to.
10513 - Require servers that use the default dirservers to have public IP
10514 addresses. We have too many servers that are configured with private
10515 IPs and their admins never notice the log entries complaining that
10516 their descriptors are being rejected.
10517 - Add OSX uninstall instructions. An actual uninstall script will
10521 Changes in version 0.1.0.8-rc - 2005-05-23
10523 - It turns out that kqueue on OS X 10.3.9 was causing kernel
10524 panics. Disable kqueue on all OS X Tors.
10525 - Fix RPM: remove duplicate line accidentally added to the rpm
10527 - Disable threads on openbsd too, since its gethostaddr is not
10529 - Tolerate libevent 0.8 since it still works, even though it's
10531 - Enable building on Red Hat 9.0 again.
10532 - Allow the middle hop of the testing circuit to be running any
10533 version, now that most of them have the bugfix to let them connect
10534 to unknown servers. This will allow reachability testing to work
10535 even when 0.0.9.7-0.0.9.9 become obsolete.
10536 - Handle relay cells with rh.length too large. This prevents
10537 a potential attack that could read arbitrary memory (maybe even
10538 keys) from the exit server's process.
10539 - We screwed up the dirport reachability testing when we don't yet
10540 have a cached version of the directory. Hopefully now fixed.
10541 - Clean up router_load_single_router() (used by the controller),
10542 so it doesn't seg fault on error.
10543 - Fix a minor memory leak when somebody establishes an introduction
10544 point at your Tor server.
10545 - If a socks connection ends because read fails, don't warn that
10546 you're not sending a socks reply back.
10549 - Add HttpProxyAuthenticator config option too, that works like
10550 the HttpsProxyAuthenticator config option.
10551 - Encode hashed controller passwords in hex instead of base64,
10552 to make it easier to write controllers.
10555 Changes in version 0.1.0.7-rc - 2005-05-17
10557 - Fix a bug in the OS X package installer that prevented it from
10558 installing on Tiger.
10559 - Fix a script bug in the OS X package installer that made it
10560 complain during installation.
10561 - Find libevent even if it's hiding in /usr/local/ and your
10562 CFLAGS and LDFLAGS don't tell you to look there.
10563 - Be able to link with libevent as a shared library (the default
10564 after 1.0d), even if it's hiding in /usr/local/lib and even
10565 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
10566 assuming you're running gcc. Otherwise fail and give a useful
10568 - Fix a bug in the RPM packager: set home directory for _tor to
10569 something more reasonable when first installing.
10570 - Free a minor amount of memory that is still reachable on exit.
10573 Changes in version 0.1.0.6-rc - 2005-05-14
10575 - Implement --disable-threads configure option. Disable threads on
10576 netbsd by default, because it appears to have no reentrant resolver
10578 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
10579 release (1.1) detects and disables kqueue if it's broken.
10580 - Append default exit policy before checking for implicit internal
10581 addresses. Now we don't log a bunch of complaints on startup
10582 when using the default exit policy.
10583 - Some people were putting "Address " in their torrc, and they had
10584 a buggy resolver that resolved " " to 0.0.0.0. Oops.
10585 - If DataDir is ~/.tor, and that expands to /.tor, then default to
10586 LOCALSTATEDIR/tor instead.
10587 - Fix fragmented-message bug in TorControl.py.
10588 - Resolve a minor bug which would prevent unreachable dirports
10589 from getting suppressed in the published descriptor.
10590 - When the controller gave us a new descriptor, we weren't resolving
10591 it immediately, so Tor would think its address was 0.0.0.0 until
10592 we fetched a new directory.
10593 - Fix an uppercase/lowercase case error in suppressing a bogus
10594 libevent warning on some Linuxes.
10597 - Begin scrubbing sensitive strings from logs by default. Turn off
10598 the config option SafeLogging if you need to do debugging.
10599 - Switch to a new buffer management algorithm, which tries to avoid
10600 reallocing and copying quite as much. In first tests it looks like
10601 it uses *more* memory on average, but less cpu.
10602 - First cut at support for "create-fast" cells. Clients can use
10603 these when extending to their first hop, since the TLS already
10604 provides forward secrecy and authentication. Not enabled on
10606 - When dirservers refuse a router descriptor, we now log its
10607 contactinfo, platform, and the poster's IP address.
10608 - Call tor_free_all instead of connections_free_all after forking, to
10609 save memory on systems that need to fork.
10610 - Whine at you if you're a server and you don't set your contactinfo.
10611 - Implement --verify-config command-line option to check if your torrc
10612 is valid without actually launching Tor.
10613 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
10614 rather than just rejecting it.
10617 Changes in version 0.1.0.5-rc - 2005-04-27
10619 - Stop trying to print a null pointer if an OR conn fails because
10620 we didn't like its cert.
10622 - Switch our internal buffers implementation to use a ring buffer,
10623 to hopefully improve performance for fast servers a lot.
10624 - Add HttpsProxyAuthenticator support (basic auth only), based
10625 on patch from Adam Langley.
10626 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
10627 the fast servers that have been joining lately.
10628 - Give hidden service accesses extra time on the first attempt,
10629 since 60 seconds is often only barely enough. This might improve
10631 - Improve performance for dirservers: stop re-parsing the whole
10632 directory every time you regenerate it.
10633 - Add more debugging info to help us find the weird dns freebsd
10634 pthreads bug; cleaner debug messages to help track future issues.
10637 Changes in version 0.0.9.9 - 2005-04-23
10638 o Bugfixes on 0.0.9.x:
10639 - If unofficial Tor clients connect and send weird TLS certs, our
10640 Tor server triggers an assert. This release contains a minimal
10641 backport from the broader fix that we put into 0.1.0.4-rc.
10644 Changes in version 0.1.0.4-rc - 2005-04-23
10646 - If unofficial Tor clients connect and send weird TLS certs, our
10647 Tor server triggers an assert. Stop asserting, and start handling
10648 TLS errors better in other situations too.
10649 - When the controller asks us to tell it about all the debug-level
10650 logs, it turns out we were generating debug-level logs while
10651 telling it about them, which turns into a bad loop. Now keep
10652 track of whether you're sending a debug log to the controller,
10653 and don't log when you are.
10654 - Fix the "postdescriptor" feature of the controller interface: on
10655 non-complete success, only say "done" once.
10657 - Clients are now willing to load balance over up to 2mB, not 1mB,
10658 of advertised bandwidth capacity.
10659 - Add a NoPublish config option, so you can be a server (e.g. for
10660 testing running Tor servers in other Tor networks) without
10661 publishing your descriptor to the primary dirservers.
10664 Changes in version 0.1.0.3-rc - 2005-04-08
10665 o Improvements on 0.1.0.2-rc:
10666 - Client now retries when streams end early for 'hibernating' or
10667 'resource limit' reasons, rather than failing them.
10668 - More automated handling for dirserver operators:
10669 - Automatically approve nodes running 0.1.0.2-rc or later,
10670 now that the the reachability detection stuff is working.
10671 - Now we allow two unverified servers with the same nickname
10672 but different keys. But if a nickname is verified, only that
10673 nickname+key are allowed.
10674 - If you're an authdirserver connecting to an address:port,
10675 and it's not the OR you were expecting, forget about that
10676 descriptor. If he *was* the one you were expecting, then forget
10677 about all other descriptors for that address:port.
10678 - Allow servers to publish descriptors from 12 hours in the future.
10679 Corollary: only whine about clock skew from the dirserver if
10680 he's a trusted dirserver (since now even verified servers could
10681 have quite wrong clocks).
10682 - Adjust maximum skew and age for rendezvous descriptors: let skew
10683 be 48 hours rather than 90 minutes.
10684 - Efficiency improvements:
10685 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
10686 it much faster to look up a circuit for each relay cell.
10687 - Remove most calls to assert_all_pending_dns_resolves_ok(),
10688 since they're eating our cpu on exit nodes.
10689 - Stop wasting time doing a case insensitive comparison for every
10690 dns name every time we do any lookup. Canonicalize the names to
10691 lowercase and be done with it.
10692 - Start sending 'truncated' cells back rather than destroy cells,
10693 if the circuit closes in front of you. This means we won't have
10694 to abandon partially built circuits.
10695 - Only warn once per nickname from add_nickname_list_to_smartlist
10696 per failure, so an entrynode or exitnode choice that's down won't
10698 - Put a note in the torrc about abuse potential with the default
10700 - Revise control spec and implementation to allow all log messages to
10701 be sent to controller with their severities intact (suggested by
10702 Matt Edman). Update TorControl to handle new log event types.
10703 - Provide better explanation messages when controller's POSTDESCRIPTOR
10705 - Stop putting nodename in the Platform string in server descriptors.
10706 It doesn't actually help, and it is confusing/upsetting some people.
10708 o Bugfixes on 0.1.0.2-rc:
10709 - We were printing the host mask wrong in exit policies in server
10710 descriptors. This isn't a critical bug though, since we were still
10711 obeying the exit policy internally.
10712 - Fix Tor when compiled with libevent but without pthreads: move
10713 connection_unregister() from _connection_free() to
10715 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
10716 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
10717 when we look through the connection array, we'll find any of the
10718 cpu/dnsworkers. This is no good.
10720 o Bugfixes on 0.0.9.8:
10721 - Fix possible bug on threading platforms (e.g. win32) which was
10722 leaking a file descriptor whenever a cpuworker or dnsworker died.
10723 - When using preferred entry or exit nodes, ignore whether the
10724 circuit wants uptime or capacity. They asked for the nodes, they
10726 - chdir() to your datadirectory at the *end* of the daemonize process,
10727 not the beginning. This was a problem because the first time you
10728 run tor, if your datadir isn't there, and you have runasdaemon set
10729 to 1, it will try to chdir to it before it tries to create it. Oops.
10730 - Handle changed router status correctly when dirserver reloads
10731 fingerprint file. We used to be dropping all unverified descriptors
10732 right then. The bug was hidden because we would immediately
10733 fetch a directory from another dirserver, which would include the
10734 descriptors we just dropped.
10735 - When we're connecting to an OR and he's got a different nickname/key
10736 than we were expecting, only complain loudly if we're an OP or a
10737 dirserver. Complaining loudly to the OR admins just confuses them.
10738 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
10739 artificially capped at 500kB.
10742 Changes in version 0.0.9.8 - 2005-04-07
10743 o Bugfixes on 0.0.9.x:
10744 - We have a bug that I haven't found yet. Sometimes, very rarely,
10745 cpuworkers get stuck in the 'busy' state, even though the cpuworker
10746 thinks of itself as idle. This meant that no new circuits ever got
10747 established. Here's a workaround to kill any cpuworker that's been
10748 busy for more than 100 seconds.
10751 Changes in version 0.1.0.2-rc - 2005-04-01
10752 o Bugfixes on 0.1.0.1-rc:
10753 - Fixes on reachability detection:
10754 - Don't check for reachability while hibernating.
10755 - If ORPort is reachable but DirPort isn't, still publish the
10756 descriptor, but zero out DirPort until it's found reachable.
10757 - When building testing circs for ORPort testing, use only
10758 high-bandwidth nodes, so fewer circuits fail.
10759 - Complain about unreachable ORPort separately from unreachable
10760 DirPort, so the user knows what's going on.
10761 - Make sure we only conclude ORPort reachability if we didn't
10762 initiate the conn. Otherwise we could falsely conclude that
10763 we're reachable just because we connected to the guy earlier
10764 and he used that same pipe to extend to us.
10765 - Authdirservers shouldn't do ORPort reachability detection,
10766 since they're in clique mode, so it will be rare to find a
10767 server not already connected to them.
10768 - When building testing circuits, always pick middle hops running
10769 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
10770 bug. (This is a kludge; it will go away when 0.0.9.x becomes
10772 - When we decide we're reachable, actually publish our descriptor
10774 - Fix bug in redirectstream in the controller.
10775 - Fix the state descriptor strings so logs don't claim edge streams
10776 are in a different state than they actually are.
10777 - Use recent libevent features when possible (this only really affects
10778 win32 and osx right now, because the new libevent with these
10779 features hasn't been released yet). Add code to suppress spurious
10781 - Prevent possible segfault in connection_close_unattached_ap().
10782 - Fix newlines on torrc in win32.
10783 - Improve error msgs when tor-resolve fails.
10785 o Improvements on 0.0.9.x:
10786 - New experimental script tor/contrib/ExerciseServer.py (needs more
10787 work) that uses the controller interface to build circuits and
10788 fetch pages over them. This will help us bootstrap servers that
10789 have lots of capacity but haven't noticed it yet.
10790 - New experimental script tor/contrib/PathDemo.py (needs more work)
10791 that uses the controller interface to let you choose whole paths
10793 "<hostname>.<path,separated by dots>.<length of path>.path"
10794 - When we've connected to an OR and handshaked but didn't like
10795 the result, we were closing the conn without sending destroy
10796 cells back for pending circuits. Now send those destroys.
10799 Changes in version 0.0.9.7 - 2005-04-01
10800 o Bugfixes on 0.0.9.x:
10801 - Fix another race crash bug (thanks to Glenn Fink for reporting).
10802 - Compare identity to identity, not to nickname, when extending to
10803 a router not already in the directory. This was preventing us from
10804 extending to unknown routers. Oops.
10805 - Make sure to create OS X Tor user in <500 range, so we aren't
10806 creating actual system users.
10807 - Note where connection-that-hasn't-sent-end was marked, and fix
10808 a few really loud instances of this harmless bug (it's fixed more
10812 Changes in version 0.1.0.1-rc - 2005-03-28
10814 - Add reachability testing. Your Tor server will automatically try
10815 to see if its ORPort and DirPort are reachable from the outside,
10816 and it won't upload its descriptor until it decides they are.
10817 - Handle unavailable hidden services better. Handle slow or busy
10818 hidden services better.
10819 - Add support for CONNECTing through https proxies, with "HttpsProxy"
10821 - New exit policy: accept most low-numbered ports, rather than
10822 rejecting most low-numbered ports.
10823 - More Tor controller support (still experimental). See
10824 http://tor.eff.org/doc/control-spec.txt for all the new features,
10825 including signals to emulate unix signals from any platform;
10826 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
10827 closestream; closecircuit; etc.
10828 - Make nt services work and start on startup on win32 (based on
10829 patch by Matt Edman).
10830 - Add a new AddressMap config directive to rewrite incoming socks
10831 addresses. This lets you, for example, declare an implicit
10832 required exit node for certain sites.
10833 - Add a new TrackHostExits config directive to trigger addressmaps
10834 for certain incoming socks addresses -- for sites that break when
10835 your exit keeps changing (based on patch by Mike Perry).
10836 - Redo the client-side dns cache so it's just an addressmap too.
10837 - Notice when our IP changes, and reset stats/uptime/reachability.
10838 - When an application is using socks5, give him the whole variety of
10839 potential socks5 responses (connect refused, host unreachable, etc),
10840 rather than just "success" or "failure".
10841 - A more sane version numbering system. See
10842 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
10843 - New contributed script "exitlist": a simple python script to
10844 parse directories and find Tor nodes that exit to listed
10846 - New contributed script "privoxy-tor-toggle" to toggle whether
10847 Privoxy uses Tor. Seems to be configured for Debian by default.
10848 - Report HTTP reasons to client when getting a response from directory
10849 servers -- so you can actually know what went wrong.
10850 - New config option MaxAdvertisedBandwidth which lets you advertise
10851 a low bandwidthrate (to not attract as many circuits) while still
10852 allowing a higher bandwidthrate in reality.
10854 o Robustness/stability fixes:
10855 - Make Tor use Niels Provos's libevent instead of its current
10856 poll-but-sometimes-select mess. This will let us use faster async
10857 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
10859 - pthread support now too. This was forced because when we forked,
10860 we ended up wasting a lot of duplicate ram over time. Also switch
10861 to foo_r versions of some library calls to allow reentry and
10863 - Better handling for heterogeneous / unreliable nodes:
10864 - Annotate circuits w/ whether they aim to contain high uptime nodes
10865 and/or high capacity nodes. When building circuits, choose
10867 - This means that every single node in an intro rend circuit,
10868 not just the last one, will have a minimum uptime.
10869 - New config option LongLivedPorts to indicate application streams
10870 that will want high uptime circuits.
10871 - Servers reset uptime when a dir fetch entirely fails. This
10872 hopefully reflects stability of the server's network connectivity.
10873 - If somebody starts his tor server in Jan 2004 and then fixes his
10874 clock, don't make his published uptime be a year.
10875 - Reset published uptime when you wake up from hibernation.
10876 - Introduce a notion of 'internal' circs, which are chosen without
10877 regard to the exit policy of the last hop. Intro and rendezvous
10878 circs must be internal circs, to avoid leaking information. Resolve
10879 and connect streams can use internal circs if they want.
10880 - New circuit pooling algorithm: make sure to have enough circs around
10881 to satisfy any predicted ports, and also make sure to have 2 internal
10882 circs around if we've required internal circs lately (and with high
10883 uptime if we've seen that lately too).
10884 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
10885 which describes how often we retry making new circuits if current
10886 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
10887 how long we're willing to make use of an already-dirty circuit.
10888 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
10889 circ as necessary, if there are any completed ones lying around
10890 when we try to launch one.
10891 - Make hidden services try to establish a rendezvous for 30 seconds,
10892 rather than for n (where n=3) attempts to build a circuit.
10893 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
10894 "ShutdownWaitLength".
10895 - Try to be more zealous about calling connection_edge_end when
10896 things go bad with edge conns in connection.c.
10897 - Revise tor-spec to add more/better stream end reasons.
10898 - Revise all calls to connection_edge_end to avoid sending "misc",
10899 and to take errno into account where possible.
10902 - Fix a race condition that can trigger an assert, when we have a
10903 pending create cell and an OR connection fails right then.
10904 - Fix several double-mark-for-close bugs, e.g. where we were finding
10905 a conn for a cell even if that conn is already marked for close.
10906 - Make sequence of log messages when starting on win32 with no config
10907 file more reasonable.
10908 - When choosing an exit node for a new non-internal circ, don't take
10909 into account whether it'll be useful for any pending x.onion
10910 addresses -- it won't.
10911 - Turn addr_policy_compare from a tristate to a quadstate; this should
10912 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
10913 for google.com" problem.
10914 - Make "platform" string in descriptor more accurate for Win32 servers,
10915 so it's not just "unknown platform".
10916 - Fix an edge case in parsing config options (thanks weasel).
10917 If they say "--" on the commandline, it's not an option.
10918 - Reject odd-looking addresses at the client (e.g. addresses that
10919 contain a colon), rather than having the server drop them because
10921 - tor-resolve requests were ignoring .exit if there was a working circuit
10922 they could use instead.
10923 - REUSEADDR on normal platforms means you can rebind to the port
10924 right after somebody else has let it go. But REUSEADDR on win32
10925 means to let you bind to the port _even when somebody else
10926 already has it bound_! So, don't do that on Win32.
10927 - Change version parsing logic: a version is "obsolete" if it is not
10928 recommended and (1) there is a newer recommended version in the
10929 same series, or (2) there are no recommended versions in the same
10930 series, but there are some recommended versions in a newer series.
10931 A version is "new" if it is newer than any recommended version in
10933 - Stop most cases of hanging up on a socks connection without sending
10937 - Require BandwidthRate to be at least 20kB/s for servers.
10938 - When a dirserver causes you to give a warn, mention which dirserver
10940 - New config option DirAllowPrivateAddresses for authdirservers.
10941 Now by default they refuse router descriptors that have non-IP or
10942 private-IP addresses.
10943 - Stop publishing socksport in the directory, since it's not
10944 actually meant to be public. For compatibility, publish a 0 there
10946 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
10947 smart" value, that is low for servers and high for clients.
10948 - If our clock jumps forward by 100 seconds or more, assume something
10949 has gone wrong with our network and abandon all not-yet-used circs.
10950 - Warn when exit policy implicitly allows local addresses.
10951 - If we get an incredibly skewed timestamp from a dirserver mirror
10952 that isn't a verified OR, don't warn -- it's probably him that's
10954 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
10955 cookies to disk and doesn't log each web request to disk. (Thanks
10956 to Brett Carrington for pointing this out.)
10957 - When a client asks us for a dir mirror and we don't have one,
10958 launch an attempt to get a fresh one.
10959 - If we're hibernating and we get a SIGINT, exit immediately.
10960 - Add --with-dmalloc ./configure option, to track memory leaks.
10961 - And try to free all memory on closing, so we can detect what
10963 - Cache local dns resolves correctly even when they're .exit
10965 - Give a better warning when some other server advertises an
10966 ORPort that is actually an apache running ssl.
10967 - Add "opt hibernating 1" to server descriptor to make it clearer
10968 whether the server is hibernating.
10971 Changes in version 0.0.9.6 - 2005-03-24
10972 o Bugfixes on 0.0.9.x (crashes and asserts):
10973 - Add new end stream reasons to maintainance branch. Fix bug where
10974 reason (8) could trigger an assert. Prevent bug from recurring.
10975 - Apparently win32 stat wants paths to not end with a slash.
10976 - Fix assert triggers in assert_cpath_layer_ok(), where we were
10977 blowing away the circuit that conn->cpath_layer points to, then
10978 checking to see if the circ is well-formed. Backport check to make
10979 sure we dont use the cpath on a closed connection.
10980 - Prevent circuit_resume_edge_reading_helper() from trying to package
10981 inbufs for marked-for-close streams.
10982 - Don't crash on hup if your options->address has become unresolvable.
10983 - Some systems (like OS X) sometimes accept() a connection and tell
10984 you the remote host is 0.0.0.0:0. If this happens, due to some
10985 other mis-features, we get confused; so refuse the conn for now.
10987 o Bugfixes on 0.0.9.x (other):
10988 - Fix harmless but scary "Unrecognized content encoding" warn message.
10989 - Add new stream error reason: TORPROTOCOL reason means "you are not
10990 speaking a version of Tor I understand; say bye-bye to your stream."
10991 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
10992 into the future, now that we are more tolerant of skew. This
10993 resolves a bug where a Tor server would refuse to cache a directory
10994 because all the directories it gets are too far in the future;
10995 yet the Tor server never logs any complaints about clock skew.
10996 - Mac packaging magic: make man pages useable, and do not overwrite
10997 existing torrc files.
10998 - Make OS X log happily to /var/log/tor/tor.log
11001 Changes in version 0.0.9.5 - 2005-02-22
11002 o Bugfixes on 0.0.9.x:
11003 - Fix an assert race at exit nodes when resolve requests fail.
11004 - Stop picking unverified dir mirrors--it only leads to misery.
11005 - Patch from Matt Edman to make NT services work better. Service
11006 support is still not compiled into the executable by default.
11007 - Patch from Dmitri Bely so the Tor service runs better under
11008 the win32 SYSTEM account.
11009 - Make tor-resolve actually work (?) on Win32.
11010 - Fix a sign bug when getrlimit claims to have 4+ billion
11011 file descriptors available.
11012 - Stop refusing to start when bandwidthburst == bandwidthrate.
11013 - When create cells have been on the onion queue more than five
11014 seconds, just send back a destroy and take them off the list.
11017 Changes in version 0.0.9.4 - 2005-02-03
11018 o Bugfixes on 0.0.9:
11019 - Fix an assert bug that took down most of our servers: when
11020 a server claims to have 1 GB of bandwidthburst, don't
11022 - Don't crash as badly if we have spawned the max allowed number
11023 of dnsworkers, or we're out of file descriptors.
11024 - Block more file-sharing ports in the default exit policy.
11025 - MaxConn is now automatically set to the hard limit of max
11026 file descriptors we're allowed (ulimit -n), minus a few for
11028 - Give a clearer message when servers need to raise their
11029 ulimit -n when they start running out of file descriptors.
11030 - SGI Compatibility patches from Jan Schaumann.
11031 - Tolerate a corrupt cached directory better.
11032 - When a dirserver hasn't approved your server, list which one.
11033 - Go into soft hibernation after 95% of the bandwidth is used,
11034 not 99%. This is especially important for daily hibernators who
11035 have a small accounting max. Hopefully it will result in fewer
11036 cut connections when the hard hibernation starts.
11037 - Load-balance better when using servers that claim more than
11038 800kB/s of capacity.
11039 - Make NT services work (experimental, only used if compiled in).
11042 Changes in version 0.0.9.3 - 2005-01-21
11043 o Bugfixes on 0.0.9:
11044 - Backport the cpu use fixes from main branch, so busy servers won't
11045 need as much processor time.
11046 - Work better when we go offline and then come back, or when we
11047 run Tor at boot before the network is up. We do this by
11048 optimistically trying to fetch a new directory whenever an
11049 application request comes in and we think we're offline -- the
11050 human is hopefully a good measure of when the network is back.
11051 - Backport some minimal hidserv bugfixes: keep rend circuits open as
11052 long as you keep using them; actually publish hidserv descriptors
11053 shortly after they change, rather than waiting 20-40 minutes.
11054 - Enable Mac startup script by default.
11055 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
11056 - When you update AllowUnverifiedNodes or FirewallPorts via the
11057 controller's setconf feature, we were always appending, never
11059 - When you update HiddenServiceDir via setconf, it was screwing up
11060 the order of reading the lines, making it fail.
11061 - Do not rewrite a cached directory back to the cache; otherwise we
11062 will think it is recent and not fetch a newer one on startup.
11063 - Workaround for webservers that lie about Content-Encoding: Tor
11064 now tries to autodetect compressed directories and compression
11065 itself. This lets us Proxypass dir fetches through apache.
11068 Changes in version 0.0.9.2 - 2005-01-04
11069 o Bugfixes on 0.0.9 (crashes and asserts):
11070 - Fix an assert on startup when the disk is full and you're logging
11072 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
11073 style address, then we'd crash.
11074 - Fix an assert trigger when the running-routers string we get from
11075 a dirserver is broken.
11076 - Make worker threads start and run on win32. Now win32 servers
11078 - Bandaid (not actually fix, but now it doesn't crash) an assert
11079 where the dns worker dies mysteriously and the main Tor process
11080 doesn't remember anything about the address it was resolving.
11082 o Bugfixes on 0.0.9 (Win32):
11083 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
11084 name out of the warning/assert messages.
11085 - Fix a superficial "unhandled error on read" bug on win32.
11086 - The win32 installer no longer requires a click-through for our
11087 license, since our Free Software license grants rights but does not
11089 - Win32: When connecting to a dirserver fails, try another one
11090 immediately. (This was already working for non-win32 Tors.)
11091 - Stop trying to parse $HOME on win32 when hunting for default
11093 - Make tor-resolve.c work on win32 by calling network_init().
11095 o Bugfixes on 0.0.9 (other):
11096 - Make 0.0.9.x build on Solaris again.
11097 - Due to a fencepost error, we were blowing away the \n when reporting
11098 confvalue items in the controller. So asking for multiple config
11099 values at once couldn't work.
11100 - When listing circuits that are pending on an opening OR connection,
11101 if we're an OR we were listing circuits that *end* at us as
11102 being pending on every listener, dns/cpu worker, etc. Stop that.
11103 - Dirservers were failing to create 'running-routers' or 'directory'
11104 strings if we had more than some threshold of routers. Fix them so
11105 they can handle any number of routers.
11106 - Fix a superficial "Duplicate mark for close" bug.
11107 - Stop checking for clock skew for OR connections, even for servers.
11108 - Fix a fencepost error that was chopping off the last letter of any
11109 nickname that is the maximum allowed nickname length.
11110 - Update URLs in log messages so they point to the new website.
11111 - Fix a potential problem in mangling server private keys while
11112 writing to disk (not triggered yet, as far as we know).
11113 - Include the licenses for other free software we include in Tor,
11114 now that we're shipping binary distributions more regularly.
11117 Changes in version 0.0.9.1 - 2004-12-15
11118 o Bugfixes on 0.0.9:
11119 - Make hibernation actually work.
11120 - Make HashedControlPassword config option work.
11121 - When we're reporting event circuit status to a controller,
11122 don't use the stream status code.
11125 Changes in version 0.0.9 - 2004-12-12
11127 - Clean up manpage and torrc.sample file.
11128 - Clean up severities and text of log warnings.
11130 - Make servers trigger an assert when they enter hibernation.
11133 Changes in version 0.0.9rc7 - 2004-12-08
11134 o Bugfixes on 0.0.9rc:
11135 - Fix a stack-trashing crash when an exit node begins hibernating.
11136 - Avoid looking at unallocated memory while considering which
11137 ports we need to build circuits to cover.
11138 - Stop a sigpipe: when an 'end' cell races with eof from the app,
11139 we shouldn't hold-open-until-flush if the eof arrived first.
11140 - Fix a bug with init_cookie_authentication() in the controller.
11141 - When recommending new-format log lines, if the upper bound is
11142 LOG_ERR, leave it implicit.
11144 o Bugfixes on 0.0.8.1:
11145 - Fix a whole slew of memory leaks.
11146 - Fix isspace() and friends so they still make Solaris happy
11147 but also so they don't trigger asserts on win32.
11148 - Fix parse_iso_time on platforms without strptime (eg win32).
11149 - win32: tolerate extra "readable" events better.
11150 - win32: when being multithreaded, leave parent fdarray open.
11151 - Make unit tests work on win32.
11154 Changes in version 0.0.9rc6 - 2004-12-06
11155 o Bugfixes on 0.0.9pre:
11156 - Clean up some more integer underflow opportunities (not exploitable
11158 - While hibernating, hup should not regrow our listeners.
11159 - Send an end to the streams we close when we hibernate, rather
11160 than just chopping them off.
11161 - React to eof immediately on non-open edge connections.
11163 o Bugfixes on 0.0.8.1:
11164 - Calculate timeout for waiting for a connected cell from the time
11165 we sent the begin cell, not from the time the stream started. If
11166 it took a long time to establish the circuit, we would time out
11167 right after sending the begin cell.
11168 - Fix router_compare_addr_to_addr_policy: it was not treating a port
11169 of * as always matching, so we were picking reject *:* nodes as
11170 exit nodes too. Oops.
11173 - New circuit building strategy: keep a list of ports that we've
11174 used in the past 6 hours, and always try to have 2 circuits open
11175 or on the way that will handle each such port. Seed us with port
11176 80 so web users won't complain that Tor is "slow to start up".
11177 - Make kill -USR1 dump more useful stats about circuits.
11178 - When warning about retrying or giving up, print the address, so
11179 the user knows which one it's talking about.
11180 - If you haven't used a clean circuit in an hour, throw it away,
11181 just to be on the safe side. (This means after 6 hours a totally
11182 unused Tor client will have no circuits open.)
11185 Changes in version 0.0.9rc5 - 2004-12-01
11186 o Bugfixes on 0.0.8.1:
11187 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
11188 - Let resolve conns retry/expire also, rather than sticking around
11190 - If we are using select, make sure we stay within FD_SETSIZE.
11192 o Bugfixes on 0.0.9pre:
11193 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
11194 but doesn't seem to be currently; thanks to Ilja van Sprundel for
11196 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
11197 instead. Impose minima and maxima for all *Period options; impose
11198 even tighter maxima for fetching if we are a caching dirserver.
11199 Clip rather than rejecting.
11200 - Fetch cached running-routers from servers that serve it (that is,
11201 authdirservers and servers running 0.0.9rc5-cvs or later.)
11204 - Accept *:706 (silc) in default exit policy.
11205 - Implement new versioning format for post 0.1.
11206 - Support "foo.nickname.exit" addresses, to let Alice request the
11207 address "foo" as viewed by exit node "nickname". Based on a patch
11209 - Make tor --version --version dump the cvs Id of every file.
11212 Changes in version 0.0.9rc4 - 2004-11-28
11213 o Bugfixes on 0.0.8.1:
11214 - Make windows sockets actually non-blocking (oops), and handle
11215 win32 socket errors better.
11217 o Bugfixes on 0.0.9rc1:
11218 - Actually catch the -USR2 signal.
11221 Changes in version 0.0.9rc3 - 2004-11-25
11222 o Bugfixes on 0.0.8.1:
11223 - Flush the log file descriptor after we print "Tor opening log file",
11224 so we don't see those messages days later.
11226 o Bugfixes on 0.0.9rc1:
11227 - Make tor-resolve work again.
11228 - Avoid infinite loop in tor-resolve if tor hangs up on it.
11229 - Fix an assert trigger for clients/servers handling resolves.
11232 Changes in version 0.0.9rc2 - 2004-11-24
11233 o Bugfixes on 0.0.9rc1:
11234 - I broke socks5 support while fixing the eof bug.
11235 - Allow unitless bandwidths and intervals; they default to bytes
11237 - New servers don't start out hibernating; they are active until
11238 they run out of bytes, so they have a better estimate of how
11239 long it takes, and so their operators can know they're working.
11242 Changes in version 0.0.9rc1 - 2004-11-23
11243 o Bugfixes on 0.0.8.1:
11244 - Finally fix a bug that's been plaguing us for a year:
11245 With high load, circuit package window was reaching 0. Whenever
11246 we got a circuit-level sendme, we were reading a lot on each
11247 socket, but only writing out a bit. So we would eventually reach
11248 eof. This would be noticed and acted on even when there were still
11249 bytes sitting in the inbuf.
11250 - When poll() is interrupted, we shouldn't believe the revents values.
11252 o Bugfixes on 0.0.9pre6:
11253 - Fix hibernate bug that caused pre6 to be broken.
11254 - Don't keep rephist info for routers that haven't had activity for
11255 24 hours. (This matters now that clients have keys, since we track
11257 - Never call close_temp_logs while validating log options.
11258 - Fix backslash-escaping on tor.sh.in and torctl.in.
11261 - Implement weekly/monthly/daily accounting: now you specify your
11262 hibernation properties by
11263 AccountingMax N bytes|KB|MB|GB|TB
11264 AccountingStart day|week|month [day] HH:MM
11265 Defaults to "month 1 0:00".
11266 - Let bandwidth and interval config options be specified as 5 bytes,
11267 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
11268 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
11269 get back to normal.)
11270 - If your requested entry or exit node has advertised bandwidth 0,
11272 - Be more greedy about filling up relay cells -- we try reading again
11273 once we've processed the stuff we read, in case enough has arrived
11274 to fill the last cell completely.
11275 - Apply NT service patch from Osamu Fujino. Still needs more work.
11278 Changes in version 0.0.9pre6 - 2004-11-15
11279 o Bugfixes on 0.0.8.1:
11280 - Fix assert failure on malformed socks4a requests.
11281 - Use identity comparison, not nickname comparison, to choose which
11282 half of circuit-ID-space each side gets to use. This is needed
11283 because sometimes we think of a router as a nickname, and sometimes
11284 as a hex ID, and we can't predict what the other side will do.
11285 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
11286 write() call will fail and we handle it there.
11287 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
11288 and smartlist_len, which are two major profiling offenders.
11290 o Bugfixes on 0.0.9pre5:
11291 - Fix a bug in read_all that was corrupting config files on windows.
11292 - When we're raising the max number of open file descriptors to
11293 'unlimited', don't log that we just raised it to '-1'.
11294 - Include event code with events, as required by control-spec.txt.
11295 - Don't give a fingerprint when clients do --list-fingerprint:
11296 it's misleading, because it will never be the same again.
11297 - Stop using strlcpy in tor_strndup, since it was slowing us
11299 - Remove warn on startup about missing cached-directory file.
11300 - Make kill -USR1 work again.
11301 - Hibernate if we start tor during the "wait for wakeup-time" phase
11302 of an accounting interval. Log our hibernation plans better.
11303 - Authoritative dirservers now also cache their directory, so they
11304 have it on start-up.
11307 - Fetch running-routers; cache running-routers; compress
11308 running-routers; serve compressed running-routers.z
11309 - Add NSI installer script contributed by J Doe.
11310 - Commit VC6 and VC7 workspace/project files.
11311 - Commit a tor.spec for making RPM files, with help from jbash.
11312 - Add contrib/torctl.in contributed by Glenn Fink.
11313 - Implement the control-spec's SAVECONF command, to write your
11314 configuration to torrc.
11315 - Get cookie authentication for the controller closer to working.
11316 - Include control-spec.txt in the tarball.
11317 - When set_conf changes our server descriptor, upload a new copy.
11318 But don't upload it too often if there are frequent changes.
11319 - Document authentication config in man page, and document signals
11321 - Clean up confusing parts of man page and torrc.sample.
11322 - Make expand_filename handle ~ and ~username.
11323 - Use autoconf to enable largefile support where necessary. Use
11324 ftello where available, since ftell can fail at 2GB.
11325 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
11326 log more informatively.
11327 - Give a slightly more useful output for "tor -h".
11328 - Refuse application socks connections to port 0.
11329 - Check clock skew for verified servers, but allow unverified
11330 servers and clients to have any clock skew.
11331 - Break DirFetchPostPeriod into:
11332 - DirFetchPeriod for fetching full directory,
11333 - StatusFetchPeriod for fetching running-routers,
11334 - DirPostPeriod for posting server descriptor,
11335 - RendPostPeriod for posting hidden service descriptors.
11336 - Make sure the hidden service descriptors are at a random offset
11337 from each other, to hinder linkability.
11340 Changes in version 0.0.9pre5 - 2004-11-09
11341 o Bugfixes on 0.0.9pre4:
11342 - Fix a seg fault in unit tests (doesn't affect main program).
11343 - Fix an assert bug where a hidden service provider would fail if
11344 the first hop of his rendezvous circuit was down.
11345 - Hidden service operators now correctly handle version 1 style
11346 INTRODUCE1 cells (nobody generates them still, so not a critical
11348 - If do_hup fails, actually notice.
11349 - Handle more errnos from accept() without closing the listener.
11350 Some OpenBSD machines were closing their listeners because
11351 they ran out of file descriptors.
11352 - Send resolve cells to exit routers that are running a new
11353 enough version of the resolve code to work right.
11354 - Better handling of winsock includes on non-MSV win32 compilers.
11355 - Some people had wrapped their tor client/server in a script
11356 that would restart it whenever it died. This did not play well
11357 with our "shut down if your version is obsolete" code. Now people
11358 don't fetch a new directory if their local cached version is
11360 - Make our autogen.sh work on ksh as well as bash.
11363 - Hibernation: New config option "AccountingMaxKB" lets you
11364 set how many KBytes per month you want to allow your server to
11365 consume. Rather than spreading those bytes out evenly over the
11366 month, we instead hibernate for some of the month and pop up
11367 at a deterministic time, work until the bytes are consumed, then
11368 hibernate again. Config option "MonthlyAccountingStart" lets you
11369 specify which day of the month your billing cycle starts on.
11370 - Control interface: a separate program can now talk to your
11371 client/server over a socket, and get/set config options, receive
11372 notifications of circuits and streams starting/finishing/dying,
11373 bandwidth used, etc. The next step is to get some GUIs working.
11374 Let us know if you want to help out. See doc/control-spec.txt .
11375 - Ship a contrib/tor-control.py as an example script to interact
11376 with the control port.
11377 - "tor --hash-password zzyxz" will output a salted password for
11378 use in authenticating to the control interface.
11379 - New log format in config:
11380 "Log minsev[-maxsev] stdout|stderr|syslog" or
11381 "Log minsev[-maxsev] file /var/foo"
11384 - DirPolicy config option, to let people reject incoming addresses
11385 from their dirserver.
11386 - "tor --list-fingerprint" will list your identity key fingerprint
11388 - Add "pass" target for RedirectExit, to make it easier to break
11389 out of a sequence of RedirectExit rules.
11390 - Clients now generate a TLS cert too, in preparation for having
11391 them act more like real nodes.
11392 - Ship src/win32/ in the tarball, so people can use it to build.
11393 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
11395 - New "router-status" line in directory, to better bind each verified
11396 nickname to its identity key.
11397 - Deprecate unofficial config option abbreviations, and abbreviations
11398 not on the command line.
11399 - Add a pure-C tor-resolve implementation.
11400 - Use getrlimit and friends to ensure we can reach MaxConn (currently
11401 1024) file descriptors.
11403 o Code security improvements, inspired by Ilja:
11404 - Replace sprintf with snprintf. (I think they were all safe, but
11406 - Replace strcpy/strncpy with strlcpy in more places.
11407 - Avoid strcat; use snprintf or strlcat instead.
11408 - snprintf wrapper with consistent (though not C99) overflow behavior.
11411 Changes in version 0.0.9pre4 - 2004-10-17
11412 o Bugfixes on 0.0.9pre3:
11413 - If the server doesn't specify an exit policy, use the real default
11414 exit policy, not reject *:*.
11415 - Ignore fascistfirewall when uploading/downloading hidden service
11416 descriptors, since we go through Tor for those; and when using
11417 an HttpProxy, since we assume it can reach them all.
11418 - When looking for an authoritative dirserver, use only the ones
11419 configured at boot. Don't bother looking in the directory.
11420 - The rest of the fix for get_default_conf_file() on older win32.
11421 - Make 'Routerfile' config option obsolete.
11424 - New 'MyFamily nick1,...' config option for a server to
11425 specify other servers that shouldn't be used in the same circuit
11426 with it. Only believed if nick1 also specifies us.
11427 - New 'NodeFamily nick1,nick2,...' config option for a client to
11428 specify nodes that it doesn't want to use in the same circuit.
11429 - New 'Redirectexit pattern address:port' config option for a
11430 server to redirect exit connections, e.g. to a local squid.
11433 Changes in version 0.0.9pre3 - 2004-10-13
11434 o Bugfixes on 0.0.8.1:
11435 - Better torrc example lines for dirbindaddress and orbindaddress.
11436 - Improved bounds checking on parsed ints (e.g. config options and
11437 the ones we find in directories.)
11438 - Better handling of size_t vs int, so we're more robust on 64
11440 - Fix the rest of the bug where a newly started OR would appear
11441 as unverified even after we've added his fingerprint and hupped
11443 - Fix a bug from 0.0.7: when read() failed on a stream, we would
11444 close it without sending back an end. So 'connection refused'
11445 would simply be ignored and the user would get no response.
11447 o Bugfixes on 0.0.9pre2:
11448 - Serving the cached-on-disk directory to people is bad. We now
11449 provide no directory until we've fetched a fresh one.
11450 - Workaround for bug on windows where cached-directories get crlf
11452 - Make get_default_conf_file() work on older windows too.
11453 - If we write a *:* exit policy line in the descriptor, don't write
11454 any more exit policy lines.
11457 - Use only 0.0.9pre1 and later servers for resolve cells.
11458 - Make the dirservers file obsolete.
11459 - Include a dir-signing-key token in directories to tell the
11460 parsing entity which key is being used to sign.
11461 - Remove the built-in bulky default dirservers string.
11462 - New config option "Dirserver %s:%d [fingerprint]", which can be
11463 repeated as many times as needed. If no dirservers specified,
11464 default to moria1,moria2,tor26.
11465 - Make moria2 advertise a dirport of 80, so people behind firewalls
11466 will be able to get a directory.
11467 - Http proxy support
11468 - Dirservers translate requests for http://%s:%d/x to /x
11469 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
11470 be routed through this host.
11471 - Clients ask for /tor/x rather than /x for new enough dirservers.
11472 This way we can one day coexist peacefully with apache.
11473 - Clients specify a "Host: %s%d" http header, to be compatible
11474 with more proxies, and so running squid on an exit node can work.
11477 Changes in version 0.0.8.1 - 2004-10-13
11479 - Fix a seg fault that can be triggered remotely for Tor
11480 clients/servers with an open dirport.
11481 - Fix a rare assert trigger, where routerinfos for entries in
11482 our cpath would expire while we're building the path.
11483 - Fix a bug in OutboundBindAddress so it (hopefully) works.
11484 - Fix a rare seg fault for people running hidden services on
11485 intermittent connections.
11486 - Fix a bug in parsing opt keywords with objects.
11487 - Fix a stale pointer assert bug when a stream detaches and
11489 - Fix a string format vulnerability (probably not exploitable)
11490 in reporting stats locally.
11491 - Fix an assert trigger: sometimes launching circuits can fail
11492 immediately, e.g. because too many circuits have failed recently.
11493 - Fix a compile warning on 64 bit platforms.
11496 Changes in version 0.0.9pre2 - 2004-10-03
11498 - Make fetching a cached directory work for 64-bit platforms too.
11499 - Make zlib.h a required header, not an optional header.
11502 Changes in version 0.0.9pre1 - 2004-10-01
11504 - Stop using separate defaults for no-config-file and
11505 empty-config-file. Now you have to explicitly turn off SocksPort,
11506 if you don't want it open.
11507 - Fix a bug in OutboundBindAddress so it (hopefully) works.
11508 - Improve man page to mention more of the 0.0.8 features.
11509 - Fix a rare seg fault for people running hidden services on
11510 intermittent connections.
11511 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
11513 - Fix more dns related bugs: send back resolve_failed and end cells
11514 more reliably when the resolve fails, rather than closing the
11515 circuit and then trying to send the cell. Also attach dummy resolve
11516 connections to a circuit *before* calling dns_resolve(), to fix
11517 a bug where cached answers would never be sent in RESOLVED cells.
11518 - When we run out of disk space, or other log writing error, don't
11519 crash. Just stop logging to that log and continue.
11520 - We were starting to daemonize before we opened our logs, so if
11521 there were any problems opening logs, we would complain to stderr,
11522 which wouldn't work, and then mysteriously exit.
11523 - Fix a rare bug where sometimes a verified OR would connect to us
11524 before he'd uploaded his descriptor, which would cause us to
11525 assign conn->nickname as though he's unverified. Now we look through
11526 the fingerprint list to see if he's there.
11527 - Fix a rare assert trigger, where routerinfos for entries in
11528 our cpath would expire while we're building the path.
11531 - Clients can ask dirservers for /dir.z to get a compressed version
11532 of the directory. Only works for servers running 0.0.9, of course.
11533 - Make clients cache directories and use them to seed their router
11534 lists at startup. This means clients have a datadir again.
11535 - Configuration infrastructure support for warning on obsolete
11537 - Respond to content-encoding headers by trying to uncompress as
11539 - Reply with a deflated directory when a client asks for "dir.z".
11540 We could use allow-encodings instead, but allow-encodings isn't
11541 specified in HTTP 1.0.
11542 - Raise the max dns workers from 50 to 100.
11543 - Discourage people from setting their dirfetchpostperiod more often
11544 than once per minute.
11545 - Protect dirservers from overzealous descriptor uploading -- wait
11546 10 seconds after directory gets dirty, before regenerating.
11549 Changes in version 0.0.8 - 2004-08-25
11550 o Port it to SunOS 5.9 / Athena
11553 Changes in version 0.0.8rc2 - 2004-08-20
11554 o Make it compile on cygwin again.
11555 o When picking unverified routers, skip those with low uptime and/or
11556 low bandwidth, depending on what properties you care about.
11559 Changes in version 0.0.8rc1 - 2004-08-18
11560 o Changes from 0.0.7.3:
11562 - Fix assert triggers: if the other side returns an address 0.0.0.0,
11563 don't put it into the client dns cache.
11564 - If a begin failed due to exit policy, but we believe the IP address
11565 should have been allowed, switch that router to exitpolicy reject *:*
11566 until we get our next directory.
11568 - Clients choose nodes proportional to advertised bandwidth.
11569 - Avoid using nodes with low uptime as introduction points.
11570 - Handle servers with dynamic IP addresses: don't replace
11571 options->Address with the resolved one at startup, and
11572 detect our address right before we make a routerinfo each time.
11573 - 'FascistFirewall' option to pick dirservers and ORs on specific
11574 ports; plus 'FirewallPorts' config option to tell FascistFirewall
11575 which ports are open. (Defaults to 80,443)
11576 - Be more aggressive about trying to make circuits when the network
11577 has changed (e.g. when you unsuspend your laptop).
11578 - Check for time skew on http headers; report date in response to
11580 - If the entrynode config line has only one node, don't pick it as
11582 - Add strict{entry|exit}nodes config options. If set to 1, then
11583 we refuse to build circuits that don't include the specified entry
11585 - OutboundBindAddress config option, to bind to a specific
11586 IP address for outgoing connect()s.
11587 - End truncated log entries (e.g. directories) with "[truncated]".
11589 o Patches to 0.0.8preX:
11591 - Patches to compile and run on win32 again (maybe)?
11592 - Fix crash when looking for ~/.torrc with no $HOME set.
11593 - Fix a race bug in the unit tests.
11594 - Handle verified/unverified name collisions better when new
11595 routerinfo's arrive in a directory.
11596 - Sometimes routers were getting entered into the stats before
11597 we'd assigned their identity_digest. Oops.
11598 - Only pick and establish intro points after we've gotten a
11601 - AllowUnverifiedNodes config option to let circuits choose no-name
11602 routers in entry,middle,exit,introduction,rendezvous positions.
11603 Allow middle and rendezvous positions by default.
11604 - Add a man page for tor-resolve.
11607 Changes in version 0.0.7.3 - 2004-08-12
11608 o Stop dnsworkers from triggering an assert failure when you
11609 ask them to resolve the host "".
11612 Changes in version 0.0.8pre3 - 2004-08-09
11613 o Changes from 0.0.7.2:
11614 - Allow multiple ORs with same nickname in routerlist -- now when
11615 people give us one identity key for a nickname, then later
11616 another, we don't constantly complain until the first expires.
11617 - Remember used bandwidth (both in and out), and publish 15-minute
11618 snapshots for the past day into our descriptor.
11619 - You can now fetch $DIRURL/running-routers to get just the
11620 running-routers line, not the whole descriptor list. (But
11621 clients don't use this yet.)
11622 - When people mistakenly use Tor as an http proxy, point them
11623 at the tor-doc.html rather than the INSTALL.
11624 - Remove our mostly unused -- and broken -- hex_encode()
11625 function. Use base16_encode() instead. (Thanks to Timo Lindfors
11626 for pointing out this bug.)
11627 - Rotate onion keys every 12 hours, not every 2 hours, so we have
11628 fewer problems with people using the wrong key.
11629 - Change the default exit policy to reject the default edonkey,
11630 kazaa, gnutella ports.
11631 - Add replace_file() to util.[ch] to handle win32's rename().
11633 o Changes from 0.0.8preX:
11634 - Fix two bugs in saving onion keys to disk when rotating, so
11635 hopefully we'll get fewer people using old onion keys.
11636 - Fix an assert error that was making SocksPolicy not work.
11637 - Be willing to expire routers that have an open dirport -- it's
11638 just the authoritative dirservers we want to not forget.
11639 - Reject tor-resolve requests for .onion addresses early, so we
11640 don't build a whole rendezvous circuit and then fail.
11641 - When you're warning a server that he's unverified, don't cry
11642 wolf unpredictably.
11643 - Fix a race condition: don't try to extend onto a connection
11644 that's still handshaking.
11645 - For servers in clique mode, require the conn to be open before
11646 you'll choose it for your path.
11647 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
11648 end relay cell, etc.
11649 - Measure bandwidth capacity over the last 24 hours, not just 12
11650 - Bugfix: authoritative dirservers were making and signing a new
11651 directory for each client, rather than reusing the cached one.
11654 Changes in version 0.0.8pre2 - 2004-08-04
11655 o Changes from 0.0.7.2:
11657 - Check directory signature _before_ you decide whether you're
11658 you're running an obsolete version and should exit.
11659 - Check directory signature _before_ you parse the running-routers
11660 list to decide who's running or verified.
11661 - Bugfixes and features:
11662 - Check return value of fclose while writing to disk, so we don't
11663 end up with broken files when servers run out of disk space.
11664 - Log a warning if the user uses an unsafe socks variant, so people
11665 are more likely to learn about privoxy or socat.
11666 - Dirservers now include RFC1123-style dates in the HTTP headers,
11667 which one day we will use to better detect clock skew.
11669 o Changes from 0.0.8pre1:
11670 - Make it compile without warnings again on win32.
11671 - Log a warning if you're running an unverified server, to let you
11672 know you might want to get it verified.
11673 - Only pick a default nickname if you plan to be a server.
11676 Changes in version 0.0.8pre1 - 2004-07-23
11678 - Made our unit tests compile again on OpenBSD 3.5, and tor
11679 itself compile again on OpenBSD on a sparc64.
11680 - We were neglecting milliseconds when logging on win32, so
11681 everything appeared to happen at the beginning of each second.
11683 o Protocol changes:
11684 - 'Extend' relay cell payloads now include the digest of the
11685 intended next hop's identity key. Now we can verify that we're
11686 extending to the right router, and also extend to routers we
11687 hadn't heard of before.
11690 - Tor nodes can now act as relays (with an advertised ORPort)
11691 without being manually verified by the dirserver operators.
11692 - Uploaded descriptors of unverified routers are now accepted
11693 by the dirservers, and included in the directory.
11694 - Verified routers are listed by nickname in the running-routers
11695 list; unverified routers are listed as "$<fingerprint>".
11696 - We now use hash-of-identity-key in most places rather than
11697 nickname or addr:port, for improved security/flexibility.
11698 - To avoid Sybil attacks, paths still use only verified servers.
11699 But now we have a chance to play around with hybrid approaches.
11700 - Nodes track bandwidth usage to estimate capacity (not used yet).
11701 - ClientOnly option for nodes that never want to become servers.
11702 - Directory caching.
11703 - "AuthoritativeDir 1" option for the official dirservers.
11704 - Now other nodes (clients and servers) will cache the latest
11705 directory they've pulled down.
11706 - They can enable their DirPort to serve it to others.
11707 - Clients will pull down a directory from any node with an open
11708 DirPort, and check the signature/timestamp correctly.
11709 - Authoritative dirservers now fetch directories from other
11710 authdirservers, to stay better synced.
11711 - Running-routers list tells who's down also, along with noting
11712 if they're verified (listed by nickname) or unverified (listed
11714 - Allow dirservers to serve running-router list separately.
11715 This isn't used yet.
11716 - ORs connect-on-demand to other ORs
11717 - If you get an extend cell to an OR you're not connected to,
11718 connect, handshake, and forward the create cell.
11719 - The authoritative dirservers stay connected to everybody,
11720 and everybody stays connected to 0.0.7 servers, but otherwise
11721 clients/servers expire unused connections after 5 minutes.
11722 - When servers get a sigint, they delay 30 seconds (refusing new
11723 connections) then exit. A second sigint causes immediate exit.
11724 - File and name management:
11725 - Look for .torrc if no CONFDIR "torrc" is found.
11726 - If no datadir is defined, then choose, make, and secure ~/.tor
11728 - If torrc not found, exitpolicy reject *:*.
11729 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
11730 - If no nickname is defined, derive default from hostname.
11731 - Rename secret key files, e.g. identity.key -> secret_id_key,
11732 to discourage people from mailing their identity key to tor-ops.
11733 - Refuse to build a circuit before the directory has arrived --
11734 it won't work anyway, since you won't know the right onion keys
11736 - Try other dirservers immediately if the one you try is down. This
11737 should tolerate down dirservers better now.
11738 - Parse tor version numbers so we can do an is-newer-than check
11739 rather than an is-in-the-list check.
11740 - New socks command 'resolve', to let us shim gethostbyname()
11742 - A 'tor_resolve' script to access the socks resolve functionality.
11743 - A new socks-extensions.txt doc file to describe our
11744 interpretation and extensions to the socks protocols.
11745 - Add a ContactInfo option, which gets published in descriptor.
11746 - Publish OR uptime in descriptor (and thus in directory) too.
11747 - Write tor version at the top of each log file
11748 - New docs in the tarball:
11750 - Document that you should proxy your SSL traffic too.
11753 Changes in version 0.0.7.2 - 2004-07-07
11754 o A better fix for the 0.0.0.0 problem, that will hopefully
11755 eliminate the remaining related assertion failures.
11758 Changes in version 0.0.7.1 - 2004-07-04
11759 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
11760 since internally we use 0.0.0.0 to signify "not yet resolved".
11763 Changes in version 0.0.7 - 2004-06-07
11764 o Updated the man page to reflect the new features.
11767 Changes in version 0.0.7rc2 - 2004-06-06
11768 o Changes from 0.0.7rc1:
11769 - Make it build on Win32 again.
11770 o Changes from 0.0.6.2:
11771 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
11775 Changes in version 0.0.7rc1 - 2004-06-02
11777 - On sighup, we were adding another log without removing the first
11778 one. So log messages would get duplicated n times for n sighups.
11779 - Several cases of using a connection after we'd freed it. The
11780 problem was that connections that are pending resolve are in both
11781 the pending_resolve tree, and also the circuit's resolving_streams
11782 list. When you want to remove one, you must remove it from both.
11783 - Fix a double-mark-for-close where an end cell arrived for a
11784 resolving stream, and then the resolve failed.
11785 - Check directory signatures based on name of signer, not on whom
11786 we got the directory from. This will let us cache directories more
11789 - Crank up some of our constants to handle more users.
11792 Changes in version 0.0.7pre1 - 2004-06-02
11793 o Fixes for crashes and other obnoxious bugs:
11794 - Fix an epipe bug: sometimes when directory connections failed
11795 to connect, we would give them a chance to flush before closing
11797 - When we detached from a circuit because of resolvefailed, we
11798 would immediately try the same circuit twice more, and then
11799 give up on the resolve thinking we'd tried three different
11801 - Limit the number of intro circuits we'll attempt to build for a
11802 hidden service per 15-minute period.
11803 - Check recommended-software string *early*, before actually parsing
11804 the directory. Thus we can detect an obsolete version and exit,
11805 even if the new directory format doesn't parse.
11806 o Fixes for security bugs:
11807 - Remember which nodes are dirservers when you startup, and if a
11808 random OR enables his dirport, don't automatically assume he's
11809 a trusted dirserver.
11811 - Directory connections were asking the wrong poll socket to
11812 start writing, and not asking themselves to start writing.
11813 - When we detached from a circuit because we sent a begin but
11814 didn't get a connected, we would use it again the first time;
11815 but after that we would correctly switch to a different one.
11816 - Stop warning when the first onion decrypt attempt fails; they
11817 will sometimes legitimately fail now that we rotate keys.
11818 - Override unaligned-access-ok check when $host_cpu is ia64 or
11819 arm. Apparently they allow it but the kernel whines.
11820 - Dirservers try to reconnect periodically too, in case connections
11822 - Fix some memory leaks in directory servers.
11823 - Allow backslash in Win32 filenames.
11824 - Made Tor build complain-free on FreeBSD, hopefully without
11825 breaking other BSD builds. We'll see.
11827 - Doxygen markup on all functions and global variables.
11828 - Make directory functions update routerlist, not replace it. So
11829 now directory disagreements are not so critical a problem.
11830 - Remove the upper limit on number of descriptors in a dirserver's
11831 directory (not that we were anywhere close).
11832 - Allow multiple logfiles at different severity ranges.
11833 - Allow *BindAddress to specify ":port" rather than setting *Port
11834 separately. Allow multiple instances of each BindAddress config
11835 option, so you can bind to multiple interfaces if you want.
11836 - Allow multiple exit policy lines, which are processed in order.
11837 Now we don't need that huge line with all the commas in it.
11838 - Enable accept/reject policies on SOCKS connections, so you can bind
11839 to 0.0.0.0 but still control who can use your OP.
11842 Changes in version 0.0.6.2 - 2004-05-16
11843 o Our integrity-checking digest was checking only the most recent cell,
11844 not the previous cells like we'd thought.
11845 Thanks to Stefan Mark for finding the flaw!
11848 Changes in version 0.0.6.1 - 2004-05-06
11849 o Fix two bugs in our AES counter-mode implementation (this affected
11850 onion-level stream encryption, but not TLS-level). It turns
11851 out we were doing something much more akin to a 16-character
11852 polyalphabetic cipher. Oops.
11853 Thanks to Stefan Mark for finding the flaw!
11854 o Retire moria3 as a directory server, and add tor26 as a directory
11858 Changes in version 0.0.6 - 2004-05-02
11859 [version bump only]
11862 Changes in version 0.0.6rc4 - 2004-05-01
11863 o Update the built-in dirservers list to use the new directory format
11864 o Fix a rare seg fault: if a node offering a hidden service attempts
11865 to build a circuit to Alice's rendezvous point and fails before it
11866 reaches the last hop, it retries with a different circuit, but
11868 o Handle windows socket errors correctly.
11871 Changes in version 0.0.6rc3 - 2004-04-28
11872 o Don't expire non-general excess circuits (if we had enough
11873 circuits open, we were expiring rendezvous circuits -- even
11874 when they had a stream attached. oops.)
11875 o Fetch randomness from /dev/urandom better (not via fopen/fread)
11876 o Better debugging for tls errors
11877 o Some versions of openssl have an SSL_pending function that erroneously
11878 returns bytes when there is a non-application record pending.
11879 o Set Content-Type on the directory and hidserv descriptor.
11880 o Remove IVs from cipher code, since AES-ctr has none.
11881 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
11882 o We were using an array of length zero in a few places.
11883 o win32's gethostbyname can't resolve an IP to an IP.
11884 o win32's close can't close a socket.
11887 Changes in version 0.0.6rc2 - 2004-04-26
11888 o Fix a bug where we were closing tls connections intermittently.
11889 It turns out openssl keeps its errors around -- so if an error
11890 happens, and you don't ask about it, and then another openssl
11891 operation happens and succeeds, and you ask if there was an error,
11892 it tells you about the first error. Fun fun.
11893 o Fix a bug that's been lurking since 27 may 03 (!)
11894 When passing back a destroy cell, we would use the wrong circ id.
11895 'Mostly harmless', but still worth fixing.
11896 o Since we don't support truncateds much, don't bother sending them;
11897 just close the circ.
11898 o check for <machine/limits.h> so we build on NetBSD again (I hope).
11899 o don't crash if a conn that sent a begin has suddenly lost its circuit
11900 (this was quite rare).
11903 Changes in version 0.0.6rc1 - 2004-04-25
11904 o We now rotate link (tls context) keys and onion keys.
11905 o CREATE cells now include oaep padding, so you can tell
11906 if you decrypted them correctly.
11907 o Add bandwidthburst to server descriptor.
11908 o Directories now say which dirserver signed them.
11909 o Use a tor_assert macro that logs failed assertions too.
11912 Changes in version 0.0.6pre5 - 2004-04-18
11913 o changes from 0.0.6pre4:
11914 - make tor build on broken freebsd 5.2 installs
11915 - fix a failed assert when you try an intro point, get a nack, and try
11916 a second one and it works.
11917 - when alice uses a port that the hidden service doesn't accept,
11918 it now sends back an end cell (denied by exit policy). otherwise
11919 alice would just have to wait to time out.
11920 - fix another rare bug: when we had tried all the intro
11921 points for a hidden service, we fetched the descriptor
11922 again, but we left our introcirc thinking it had already
11923 sent an intro, so it kept waiting for a response...
11924 - bugfix: when you sleep your hidden-service laptop, as soon
11925 as it wakes up it tries to upload a service descriptor, but
11926 socketpair fails for some reason (localhost not up yet?).
11927 now we simply give up on that upload, and we'll try again later.
11928 i'd still like to find the bug though.
11929 - if an intro circ waiting for an ack dies before getting one, then
11931 - we were reusing stale service descriptors and refetching usable
11935 Changes in version 0.0.6pre4 - 2004-04-14
11936 o changes from 0.0.6pre3:
11937 - when bob fails to connect to the rendezvous point, and his
11938 circ didn't fail because of the rendezvous point itself, then
11939 he retries a couple of times
11940 - we expire introduction and rendezvous circs more thoroughly
11941 (sometimes they were hanging around forever)
11942 - we expire unattached rendezvous streams that have been around
11943 too long (they were sticking around forever).
11944 - fix a measly fencepost error that was crashing everybody with
11948 Changes in version 0.0.6pre3 - 2004-04-14
11949 o changes from 0.0.6pre2:
11950 - make hup work again
11951 - fix some memory leaks for dirservers
11952 - allow more skew in rendezvous descriptor timestamps, to help
11953 handle people like blanu who don't know what time it is
11954 - normal circs are 3 hops, but some rend/intro circs are 4, if
11955 the initiator doesn't get to choose the last hop
11956 - send acks for introductions, so alice can know whether to try
11958 - bob publishes intro points more correctly
11959 o changes from 0.0.5:
11960 - fix an assert trigger that's been plaguing us since the days
11961 of 0.0.2prexx (thanks weasel!)
11962 - retry stream correctly when we fail to connect because of
11963 exit-policy-reject (should try another) or can't-resolve-address
11964 (also should try another, because dns on random internet servers
11966 - when we hup a dirserver and we've *removed* a server from the
11967 approved-routers list, now we remove that server from the
11968 in-memory directories too
11971 Changes in version 0.0.6pre2 - 2004-04-08
11972 o We fixed our base32 implementation. Now it works on all architectures.
11975 Changes in version 0.0.6pre1 - 2004-04-08
11977 - Hidden services and rendezvous points are implemented. Go to
11978 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
11979 hidden services. (This only works via a socks4a proxy such as
11980 Privoxy, and currently it's quite slow.)
11983 Changes in version 0.0.5 - 2004-03-30
11984 [version bump only]
11987 Changes in version 0.0.5rc3 - 2004-03-29
11988 o Install torrc as torrc.sample -- we no longer clobber your
11990 o Re-enable recommendedversion checking (we broke it in rc2, oops)
11991 o Add in a 'notice' log level for things the operator should hear
11992 but that aren't warnings
11995 Changes in version 0.0.5rc2 - 2004-03-29
11996 o Hold socks connection open until reply is flushed (if possible)
11997 o Make exit nodes resolve IPs to IPs immediately, rather than asking
11998 the dns farm to do it.
11999 o Fix c99 aliasing warnings in rephist.c
12000 o Don't include server descriptors that are older than 24 hours in the
12002 o Give socks 'reject' replies their whole 15s to attempt to flush,
12003 rather than seeing the 60s timeout and assuming the flush had failed.
12004 o Clean automake droppings from the cvs repository
12007 Changes in version 0.0.5rc1 - 2004-03-28
12008 o Fix mangled-state bug in directory fetching (was causing sigpipes).
12009 o Only build circuits after we've fetched the directory: clients were
12010 using only the directory servers before they'd fetched a directory.
12011 This also means longer startup time; so it goes.
12012 o Fix an assert trigger where an OP would fail to handshake, and we'd
12013 expect it to have a nickname.
12014 o Work around a tsocks bug: do a socks reject when AP connection dies
12015 early, else tsocks goes into an infinite loop.
12018 Changes in version 0.0.4 - 2004-03-26
12019 o When connecting to a dirserver or OR and the network is down,
12023 Changes in version 0.0.3 - 2004-03-26
12024 o Warn and fail if server chose a nickname with illegal characters
12025 o Port to Solaris and Sparc:
12026 - include missing header fcntl.h
12027 - have autoconf find -lsocket -lnsl automatically
12028 - deal with hardware word alignment
12029 - make uname() work (solaris has a different return convention)
12030 - switch from using signal() to sigaction()
12031 o Preliminary work on reputation system:
12032 - Keep statistics on success/fail of connect attempts; they're published
12033 by kill -USR1 currently.
12034 - Add a RunTesting option to try to learn link state by creating test
12035 circuits, even when SocksPort is off.
12036 - Remove unused open circuits when there are too many.
12039 Changes in version 0.0.2 - 2004-03-19
12040 - Include strlcpy and strlcat for safer string ops
12041 - define INADDR_NONE so we compile (but still not run) on solaris
12044 Changes in version 0.0.2pre27 - 2004-03-14
12046 - Allow internal tor networks (we were rejecting internal IPs,
12047 now we allow them if they're set explicitly).
12048 - And fix a few endian issues.
12051 Changes in version 0.0.2pre26 - 2004-03-14
12053 - If a stream times out after 15s without a connected cell, don't
12054 try that circuit again: try a new one.
12055 - Retry streams at most 4 times. Then give up.
12056 - When a dirserver gets a descriptor from an unknown router, it
12057 logs its fingerprint (so the dirserver operator can choose to
12058 accept it even without mail from the server operator).
12059 - Inform unapproved servers when we reject their descriptors.
12060 - Make tor build on Windows again. It works as a client, who knows
12062 - Clearer instructions in the torrc for how to set up a server.
12063 - Be more efficient about reading fd's when our global token bucket
12064 (used for rate limiting) becomes empty.
12066 - Stop asserting that computers always go forward in time. It's
12068 - When we sent a cell (e.g. destroy) and then marked an OR connection
12069 expired, we might close it before finishing a flush if the other
12070 side isn't reading right then.
12071 - Don't allow dirservers to start if they haven't defined
12072 RecommendedVersions
12073 - We were caching transient dns failures. Oops.
12074 - Prevent servers from publishing an internal IP as their address.
12075 - Address a strcat vulnerability in circuit.c
12078 Changes in version 0.0.2pre25 - 2004-03-04
12080 - Put the OR's IP in its router descriptor, not its fqdn. That way
12081 we'll stop being stalled by gethostbyname for nodes with flaky dns,
12084 - If the user typed in an address that didn't resolve, the server
12088 Changes in version 0.0.2pre24 - 2004-03-03
12090 - Fix an assertion failure in dns.c, where we were trying to dequeue
12091 a pending dns resolve even if it wasn't pending
12092 - Fix a spurious socks5 warning about still trying to write after the
12093 connection is finished.
12094 - Hold certain marked_for_close connections open until they're finished
12095 flushing, rather than losing bytes by closing them too early.
12096 - Correctly report the reason for ending a stream
12097 - Remove some duplicate calls to connection_mark_for_close
12098 - Put switch_id and start_daemon earlier in the boot sequence, so it
12099 will actually try to chdir() to options.DataDirectory
12100 - Make 'make test' exit(1) if a test fails; fix some unit tests
12101 - Make tor fail when you use a config option it doesn't know about,
12102 rather than warn and continue.
12103 - Make --version work
12104 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
12107 Changes in version 0.0.2pre23 - 2004-02-29
12109 - Print a statement when the first circ is finished, so the user
12110 knows it's working.
12111 - If a relay cell is unrecognized at the end of the circuit,
12112 send back a destroy. (So attacks to mutate cells are more
12114 - New config option 'excludenodes' to avoid certain nodes for circuits.
12115 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
12116 so you can collect coredumps there.
12118 - Fix a bug in tls flushing where sometimes data got wedged and
12119 didn't flush until more data got sent. Hopefully this bug was
12120 a big factor in the random delays we were seeing.
12121 - Make 'connected' cells include the resolved IP, so the client
12122 dns cache actually gets populated.
12123 - Disallow changing from ORPort=0 to ORPort>0 on hup.
12124 - When we time-out on a stream and detach from the circuit, send an
12125 end cell down it first.
12126 - Only warn about an unknown router (in exitnodes, entrynodes,
12127 excludenodes) after we've fetched a directory.
12130 Changes in version 0.0.2pre22 - 2004-02-26
12132 - Servers publish less revealing uname information in descriptors.
12133 - More memory tracking and assertions, to crash more usefully when
12135 - If the default torrc isn't there, just use some default defaults.
12136 Plus provide an internal dirservers file if they don't have one.
12137 - When the user tries to use Tor as an http proxy, give them an http
12138 501 failure explaining that we're a socks proxy.
12139 - Dump a new router.desc on hup, to help confused people who change
12140 their exit policies and then wonder why router.desc doesn't reflect
12142 - Clean up the generic tor.sh init script that we ship with.
12144 - If the exit stream is pending on the resolve, and a destroy arrives,
12145 then the stream wasn't getting removed from the pending list. I
12146 think this was the one causing recent server crashes.
12147 - Use a more robust poll on OSX 10.3, since their poll is flaky.
12148 - When it couldn't resolve any dirservers, it was useless from then on.
12149 Now it reloads the RouterFile (or default dirservers) if it has no
12151 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
12152 many users don't even *have* a /usr/local/sbin/.
12155 Changes in version 0.0.2pre21 - 2004-02-18
12157 - There's a ChangeLog file that actually reflects the changelog.
12158 - There's a 'torify' wrapper script, with an accompanying
12159 tor-tsocks.conf, that simplifies the process of using tsocks for
12160 tor. It even has a man page.
12161 - The tor binary gets installed to sbin rather than bin now.
12162 - Retry streams where the connected cell hasn't arrived in 15 seconds
12163 - Clean up exit policy handling -- get the default out of the torrc,
12164 so we can update it without forcing each server operator to fix
12166 - Allow imaps and pop3s in default exit policy
12168 - Prevent picking middleman nodes as the last node in the circuit
12171 Changes in version 0.0.2pre20 - 2004-01-30
12173 - We now have a deb package, and it's in debian unstable. Go to
12174 it, apt-getters. :)
12175 - I've split the TotalBandwidth option into BandwidthRate (how many
12176 bytes per second you want to allow, long-term) and
12177 BandwidthBurst (how many bytes you will allow at once before the cap
12178 kicks in). This better token bucket approach lets you, say, set
12179 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
12180 performance while not exceeding your monthly bandwidth quota.
12181 - Push out a tls record's worth of data once you've got it, rather
12182 than waiting until you've read everything waiting to be read. This
12183 may improve performance by pipelining better. We'll see.
12184 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
12185 from failed circuits (if they haven't been connected yet) and attach
12187 - Expire old streams that haven't managed to connect. Some day we'll
12188 have them reattach to new circuits instead.
12191 - Fix several memory leaks that were causing servers to become bloated
12193 - Fix a few very rare assert triggers. A few more remain.
12194 - Setuid to User _before_ complaining about running as root.
12197 Changes in version 0.0.2pre19 - 2004-01-07
12199 - Fix deadlock condition in dns farm. We were telling a child to die by
12200 closing the parent's file descriptor to him. But newer children were
12201 inheriting the open file descriptor from the parent, and since they
12202 weren't closing it, the socket never closed, so the child never read
12203 eof, so he never knew to exit. Similarly, dns workers were holding
12204 open other sockets, leading to all sorts of chaos.
12205 - New cleaner daemon() code for forking and backgrounding.
12206 - If you log to a file, it now prints an entry at the top of the
12207 logfile so you know it's working.
12208 - The onionskin challenge length was 30 bytes longer than necessary.
12209 - Started to patch up the spec so it's not quite so out of date.
12212 Changes in version 0.0.2pre18 - 2004-01-02
12214 - Fix endian issues with the 'integrity' field in the relay header.
12215 - Fix a potential bug where connections in state
12216 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
12219 Changes in version 0.0.2pre17 - 2003-12-30
12221 - Made --debuglogfile (or any second log file, actually) work.
12222 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
12223 adversary could force us into an infinite loop.
12226 - Each onionskin handshake now includes a hash of the computed key,
12227 to prove the server's identity and help perfect forward secrecy.
12228 - Changed cell size from 256 to 512 bytes (working toward compatibility
12230 - Changed cell length to 2 bytes, and moved it to the relay header.
12231 - Implemented end-to-end integrity checking for the payloads of
12233 - Separated streamid from 'recognized' (otherwise circuits will get
12234 messed up when we try to have streams exit from the middle). We
12235 use the integrity-checking to confirm that a cell is addressed to
12237 - Randomize the initial circid and streamid values, so an adversary who
12238 breaks into a node can't learn how many circuits or streams have
12242 Changes in version 0.0.2pre16 - 2003-12-14
12244 - Fixed a bug that made HUP trigger an assert
12245 - Fixed a bug where a circuit that immediately failed wasn't being
12246 counted as a failed circuit in counting retries.
12249 - Now we close the circuit when we get a truncated cell: otherwise we're
12250 open to an anonymity attack where a bad node in the path truncates
12251 the circuit and then we open streams at him.
12252 - Add port ranges to exit policies
12253 - Add a conservative default exit policy
12254 - Warn if you're running tor as root
12255 - on HUP, retry OR connections and close/rebind listeners
12256 - options.EntryNodes: try these nodes first when picking the first node
12257 - options.ExitNodes: if your best choices happen to include any of
12258 your preferred exit nodes, you choose among just those preferred
12260 - options.ExcludedNodes: nodes that are never picked in path building
12263 Changes in version 0.0.2pre15 - 2003-12-03
12264 o Robustness and bugfixes:
12265 - Sometimes clients would cache incorrect DNS resolves, which would
12266 really screw things up.
12267 - An OP that goes offline would slowly leak all its sockets and stop
12269 - A wide variety of bugfixes in exit node selection, exit policy
12270 handling, and processing pending streams when a new circuit is
12272 - Pick nodes for a path only from those the directory says are up
12273 - Choose randomly from all running dirservers, not always the first one
12274 - Increase allowed http header size for directory fetch.
12275 - Stop writing to stderr (if we're daemonized it will be closed).
12276 - Enable -g always, so cores will be more useful to me.
12277 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
12280 - Wrote a man page. It lists commonly used options.
12283 - Change default loglevel to warn.
12284 - Make PidFile default to null rather than littering in your CWD.
12285 - OnionRouter config option is now obsolete. Instead it just checks
12287 - Moved to a single unified torrc file for both clients and servers.
12290 Changes in version 0.0.2pre14 - 2003-11-29
12291 o Robustness and bugfixes:
12292 - Force the admin to make the DataDirectory himself
12293 - to get ownership/permissions right
12294 - so clients no longer make a DataDirectory and then never use it
12295 - fix bug where a client who was offline for 45 minutes would never
12296 pull down a directory again
12297 - fix (or at least hide really well) the dns assert bug that was
12298 causing server crashes
12299 - warnings and improved robustness wrt clockskew for certs
12300 - use the native daemon(3) to daemonize, when available
12301 - exit if bind() fails
12302 - exit if neither socksport nor orport is defined
12303 - include our own tor_timegm (Win32 doesn't have its own)
12304 - bugfix for win32 with lots of connections
12305 - fix minor bias in PRNG
12306 - make dirserver more robust to corrupt cached directory
12309 - Wrote the design document (woo)
12311 o Circuit building and exit policies:
12312 - Circuits no longer try to use nodes that the directory has told them
12314 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
12315 bitcounts (18.0.0.0/8).
12316 - Make AP connections standby for a circuit if no suitable circuit
12317 exists, rather than failing
12318 - Circuits choose exit node based on addr/port, exit policies, and
12319 which AP connections are standing by
12320 - Bump min pathlen from 2 to 3
12321 - Relay end cells have a payload to describe why the stream ended.
12322 - If the stream failed because of exit policy, try again with a new
12324 - Clients have a dns cache to remember resolved addresses.
12325 - Notice more quickly when we have no working circuits
12328 - APPort is now called SocksPort
12329 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
12331 - RecommendedVersions is now a config variable rather than
12332 hardcoded (for dirservers)
12333 - Reloads config on HUP
12334 - Usage info on -h or --help
12335 - If you set User and Group config vars, it'll setu/gid to them.
12338 Changes in version 0.0.2pre13 - 2003-10-19
12339 o General stability:
12340 - SSL_write no longer fails when it returns WANTWRITE and the number
12341 of bytes in the buf has changed by the next SSL_write call.
12342 - Fix segfault fetching directory when network is down
12343 - Fix a variety of minor memory leaks
12344 - Dirservers reload the fingerprints file on HUP, so I don't have
12345 to take down the network when I approve a new router
12346 - Default server config file has explicit Address line to specify fqdn
12349 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
12350 - Make listener connections not ever alloc bufs
12352 o Autoconf improvements:
12353 - don't clobber an external CFLAGS in ./configure
12354 - Make install now works
12355 - create var/lib/tor on make install
12356 - autocreate a tor.sh initscript to help distribs
12357 - autocreate the torrc and sample-server-torrc with correct paths
12359 o Log files and Daemonizing now work:
12360 - If --DebugLogFile is specified, log to it at -l debug
12361 - If --LogFile is specified, use it instead of commandline
12362 - If --RunAsDaemon is set, tor forks and backgrounds on startup