1 Changes in version 0.3.1.6-rc - 2017-09-05
2 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
3 release series, including a bug that produced weird behavior on
4 Windows directory caches.
6 This is the first release candidate in the Tor 0.3.1 series. If we
7 find no new bugs or regressions here, the first stable 0.3.1 release
8 will be nearly identical to it.
10 o Major bugfixes (windows, directory cache):
11 - On Windows, do not try to delete cached consensus documents and
12 diffs before they are unmapped from memory--Windows won't allow
13 that. Instead, allow the consensus cache directory to grow larger,
14 to hold files that might need to stay around longer. Fixes bug
15 22752; bugfix on 0.3.1.1-alpha.
17 o Minor features (directory authority):
18 - Improve the message that authorities report to relays that present
19 RSA/Ed25519 keypairs that conflict with previously pinned keys.
22 o Minor features (geoip):
23 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
26 o Minor features (testing):
27 - Add more tests for compression backend initialization. Closes
30 o Minor bugfixes (directory cache):
31 - Fix a memory leak when recovering space in the consensus cache.
32 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
34 o Minor bugfixes (hidden service):
35 - Increase the number of circuits that a service is allowed to
36 open over a specific period of time. The value was lower than it
37 should be (8 vs 12) in the normal case of 3 introduction points.
38 Fixes bug 22159; bugfix on 0.3.0.5-rc.
39 - Fix a BUG warning during HSv3 descriptor decoding that could be
40 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
41 on 0.3.0.1-alpha. Bug found by "haxxpop".
42 - Rate-limit the log messages if we exceed the maximum number of
43 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
45 o Minor bugfixes (logging, relay):
46 - Remove a forgotten debugging message when an introduction point
47 successfully establishes a hidden service prop224 circuit with
49 - Change three other log_warn() for an introduction point to
50 protocol warnings, because they can be failure from the network
51 and are not relevant to the operator. Fixes bug 23078; bugfix on
52 0.3.0.1-alpha and 0.3.0.2-alpha.
54 o Minor bugfixes (relay):
55 - When a relay is not running as a directory cache, it will no
56 longer generate compressed consensuses and consensus diff
57 information. Previously, this was a waste of disk and CPU. Fixes
58 bug 23275; bugfix on 0.3.1.1-alpha.
60 o Minor bugfixes (robustness, error handling):
61 - Improve our handling of the cases where OpenSSL encounters a
62 memory error while encoding keys and certificates. We haven't
63 observed these errors in the wild, but if they do happen, we now
64 detect and respond better. Fixes bug 19418; bugfix on all versions
65 of Tor. Reported by Guido Vranken.
67 o Minor bugfixes (stability):
68 - Avoid crashing on a double-free when unable to load or process an
69 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
70 with the clang static analyzer.
72 o Minor bugfixes (testing):
73 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
74 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
75 - Port the hs_ntor handshake test to work correctly with recent
76 versions of the pysha3 module. Fixes bug 23071; bugfix
79 o Minor bugfixes (Windows service):
80 - When running as a Windows service, set the ID of the main thread
81 correctly. Failure to do so made us fail to send log messages to
82 the controller in 0.2.1.16-rc, slowed down controller event
83 delivery in 0.2.7.3-rc and later, and crash with an assertion
84 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
85 Patch and diagnosis from "Vort".
88 Changes in version 0.3.0.10 - 2017-08-02
89 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
90 from the current Tor alpha series. OpenBSD users and TPROXY users
91 should upgrade; others are probably okay sticking with 0.3.0.9.
93 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
94 - Tor's repository now includes a Travis Continuous Integration (CI)
95 configuration file (.travis.yml). This is meant to help new
96 developers and contributors who fork Tor to a Github repository be
97 better able to test their changes, and understand what we expect
98 to pass. To use this new build feature, you must fork Tor to your
99 Github account, then go into the "Integrations" menu in the
100 repository settings for your fork and enable Travis, then push
101 your changes. Closes ticket 22636.
103 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
104 - Fix a typo that had prevented TPROXY-based transparent proxying
105 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
106 Patch from "d4fq0fQAgoJ".
108 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
109 - Avoid an assertion failure bug affecting our implementation of
110 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
111 handling of "0xbar" differs from what we had expected. Fixes bug
112 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
114 o Minor features (backport from 0.3.1.5-alpha):
115 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
118 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
119 - Roll over monthly accounting at the configured hour and minute,
120 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
121 Found by Andrey Karpov with PVS-Studio.
123 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
124 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
125 bugfix on 0.2.8.1-alpha.
126 - Fix warnings when building with libscrypt and openssl scrypt
127 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
128 - When building with certain versions of the mingw C header files,
129 avoid float-conversion warnings when calling the C functions
130 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
133 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
134 - Backport a fix for an "unused variable" warning that appeared
135 in some versions of mingw. Fixes bug 22838; bugfix on
138 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
139 - Avoid Coverity build warnings related to our BUG() macro. By
140 default, Coverity treats BUG() as the Linux kernel does: an
141 instant abort(). We need to override that so our BUG() macro
142 doesn't prevent Coverity from analyzing functions that use it.
143 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
145 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
146 - When rejecting a router descriptor for running an obsolete version
147 of Tor without ntor support, warn about the obsolete tor version,
148 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
150 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
151 - Avoid a sandbox failure when trying to re-bind to a socket and
152 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
154 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
155 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
156 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
159 Changes in version 0.3.1.5-alpha - 2017-08-01
160 Tor 0.3.1.5-alpha improves the performance of consensus diff
161 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
162 several other bugs. If no serious bugs are found in this version, the
163 next version will be a release candidate.
165 This release also marks the end of support for the Tor 0.2.4.x,
166 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
167 further bug or security fixes. Anyone still running or distributing
168 one of those versions should upgrade.
170 o Major features (build system, continuous integration):
171 - Tor's repository now includes a Travis Continuous Integration (CI)
172 configuration file (.travis.yml). This is meant to help new
173 developers and contributors who fork Tor to a Github repository be
174 better able to test their changes, and understand what we expect
175 to pass. To use this new build feature, you must fork Tor to your
176 Github account, then go into the "Integrations" menu in the
177 repository settings for your fork and enable Travis, then push
178 your changes. Closes ticket 22636.
180 o Major bugfixes (openbsd, denial-of-service):
181 - Avoid an assertion failure bug affecting our implementation of
182 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
183 handling of "0xbar" differs from what we had expected. Fixes bug
184 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
186 o Major bugfixes (relay, performance):
187 - Perform circuit handshake operations at a higher priority than we
188 use for consensus diff creation and compression. This should
189 prevent circuits from starving when a relay or bridge receives a
190 new consensus, especially on lower-powered machines. Fixes bug
191 22883; bugfix on 0.3.1.1-alpha.
193 o Minor features (bridge authority):
194 - Add "fingerprint" lines to the networkstatus-bridges file produced
195 by bridge authorities. Closes ticket 22207.
197 o Minor features (directory cache, consensus diff):
198 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
199 operators with low-resource environments to adjust the number of
200 consensuses they'll store and generate diffs from. Most cache
201 operators should leave it unchanged. Helps to work around
204 o Minor features (geoip):
205 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
208 o Minor features (relay, performance):
209 - Always start relays with at least two worker threads, to prevent
210 priority inversion on slow tasks. Part of the fix for bug 22883.
211 - Allow background work to be queued with different priorities, so
212 that a big pile of slow low-priority jobs will not starve out
213 higher priority jobs. This lays the groundwork for a fix for
216 o Minor bugfixes (build system, rust):
217 - Fix a problem where Rust toolchains were not being found when
218 building without --enable-cargo-online-mode, due to setting the
219 $HOME environment variable instead of $CARGO_HOME. Fixes bug
220 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
222 o Minor bugfixes (compatibility, zstd):
223 - Write zstd epilogues correctly when the epilogue requires
224 reallocation of the output buffer, even with zstd 1.3.0.
225 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
226 22927; bugfix on 0.3.1.1-alpha.
228 o Minor bugfixes (compilation warnings):
229 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
230 22915; bugfix on 0.2.8.1-alpha.
231 - Fix warnings when building with libscrypt and openssl scrypt
232 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
233 - Compile correctly when both openssl 1.1.0 and libscrypt are
234 detected. Previously this would cause an error. Fixes bug 22892;
235 bugfix on 0.3.1.1-alpha.
236 - When building with certain versions of the mingw C header files,
237 avoid float-conversion warnings when calling the C functions
238 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
241 o Minor bugfixes (coverity build support):
242 - Avoid Coverity build warnings related to our BUG() macro. By
243 default, Coverity treats BUG() as the Linux kernel does: an
244 instant abort(). We need to override that so our BUG() macro
245 doesn't prevent Coverity from analyzing functions that use it.
246 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
248 o Minor bugfixes (directory authority):
249 - When a directory authority rejects a descriptor or extrainfo with
250 a given digest, mark that digest as undownloadable, so that we do
251 not attempt to download it again over and over. We previously
252 tried to avoid downloading such descriptors by other means, but we
253 didn't notice if we accidentally downloaded one anyway. This
254 behavior became problematic in 0.2.7.2-alpha, when authorities
255 began pinning Ed25519 keys. Fixes bug 22349; bugfix
258 o Minor bugfixes (error reporting, windows):
259 - When formatting Windows error messages, use the English format to
260 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
263 o Minor bugfixes (file limits, osx):
264 - When setting the maximum number of connections allowed by the OS,
265 always allow some extra file descriptors for other files. Fixes
266 bug 22797; bugfix on 0.2.0.10-alpha.
268 o Minor bugfixes (linux seccomp2 sandbox):
269 - Avoid a sandbox failure when trying to re-bind to a socket and
270 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
272 o Minor bugfixes (memory leaks):
273 - Fix a small memory leak when validating a configuration that uses
274 two or more AF_UNIX sockets for the same port type. Fixes bug
275 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
277 o Minor bugfixes (unit tests):
278 - test_consdiff_base64cmp would fail on OS X because while OS X
279 follows the standard of (less than zero/zero/greater than zero),
280 it doesn't follow the convention of (-1/0/+1). Make the test
281 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
282 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
283 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
286 Changes in version 0.3.1.4-alpha - 2017-06-29
287 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
288 to use a guard that was in the same network family as a chosen exit
289 relay. This is a security regression; all clients running earlier
290 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
293 This release also fixes several other bugs introduced in 0.3.0.x
294 and 0.3.1.x, including others that can affect bandwidth usage
298 - To build with zstd and lzma support, Tor now requires the
299 pkg-config tool at build time. (This requirement was new in
300 0.3.1.1-alpha, but was not noted at the time. Noting it here to
303 o Major bugfixes (path selection, security):
304 - When choosing which guard to use for a circuit, avoid the exit's
305 family along with the exit itself. Previously, the new guard
306 selection logic avoided the exit, but did not consider its family.
307 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
308 006 and CVE-2017-0377.
310 o Major bugfixes (compression, zstd):
311 - Correctly detect a full buffer when decompressing a large zstd-
312 compressed input. Previously, we would sometimes treat a full
313 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
315 o Major bugfixes (directory protocol):
316 - Ensure that we send "304 Not modified" as HTTP status code when a
317 client is attempting to fetch a consensus or consensus diff, and
318 the best one we can send them is one they already have. Fixes bug
319 22702; bugfix on 0.3.1.1-alpha.
321 o Major bugfixes (entry guards):
322 - When starting with an old consensus, do not add new entry guards
323 unless the consensus is "reasonably live" (under 1 day old). Fixes
324 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
326 o Minor features (bug mitigation, diagnostics, logging):
327 - Avoid an assertion failure, and log a better error message, when
328 unable to remove a file from the consensus cache on Windows.
329 Attempts to mitigate and diagnose bug 22752.
331 o Minor features (geoip):
332 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
335 o Minor bugfixes (compression):
336 - When compressing or decompressing a buffer, check for a failure to
337 create a compression object. Fixes bug 22626; bugfix
339 - When decompressing a buffer, check for extra data after the end of
340 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
341 - When decompressing an object received over an anonymous directory
342 connection, if we have already decompressed it using an acceptable
343 compression method, do not reject it for looking like an
344 unacceptable compression method. Fixes part of bug 22670; bugfix
346 - When serving directory votes compressed with zlib, do not claim to
347 have compressed them with zstd. Fixes bug 22669; bugfix
349 - When spooling compressed data to an output buffer, don't try to
350 spool more data when there is no more data to spool and we are not
351 trying to flush the input. Previously, we would sometimes launch
352 compression requests with nothing to do, which interferes with our
353 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
355 o Minor bugfixes (defensive programming):
356 - Detect and break out of infinite loops in our compression code. We
357 don't think that any such loops exist now, but it's best to be
358 safe. Closes ticket 22672.
359 - Fix a memset() off the end of an array when packing cells. This
360 bug should be harmless in practice, since the corrupted bytes are
361 still in the same structure, and are always padding bytes,
362 ignored, or immediately overwritten, depending on compiler
363 behavior. Nevertheless, because the memset()'s purpose is to make
364 sure that any other cell-handling bugs can't expose bytes to the
365 network, we need to fix it. Fixes bug 22737; bugfix on
366 0.2.4.11-alpha. Fixes CID 1401591.
368 o Minor bugfixes (linux seccomp2 sandbox):
369 - Permit the fchmod system call, to avoid crashing on startup when
370 starting with the seccomp2 sandbox and an unexpected set of
371 permissions on the data directory or its contents. Fixes bug
372 22516; bugfix on 0.2.5.4-alpha.
373 - Fix a crash in the LZMA module, when the sandbox was enabled, and
374 liblzma would allocate more than 16 MB of memory. We solve this by
375 bumping the mprotect() limit in the sandbox module from 16 MB to
376 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
378 o Minor bugfixes (logging):
379 - When decompressing, do not warn if we fail to decompress using a
380 compression method that we merely guessed. Fixes part of bug
381 22670; bugfix on 0.1.1.14-alpha.
382 - When decompressing, treat mismatch between content-encoding and
383 actual compression type as a protocol warning. Fixes part of bug
384 22670; bugfix on 0.1.1.9-alpha.
385 - Downgrade "assigned_to_cpuworker failed" message to info-level
386 severity. In every case that can reach it, either a better warning
387 has already been logged, or no warning is warranted. Fixes bug
388 22356; bugfix on 0.2.6.3-alpha.
389 - Demote a warn that was caused by libevent delays to info if
390 netflow padding is less than 4.5 seconds late, or to notice
391 if it is more (4.5 seconds is the amount of time that a netflow
392 record might be emitted after, if we chose the maximum timeout).
393 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
395 o Minor bugfixes (process behavior):
396 - When exiting because of an error, always exit with a nonzero exit
397 status. Previously, we would fail to report an error in our exit
398 status in cases related to __OwningControllerProcess failure,
399 lockfile contention, and Ed25519 key initialization. Fixes bug
400 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
401 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
405 - Add a manpage description for the key-pinning-journal file. Closes
407 - Correctly note that bandwidth accounting values are stored in the
408 state file, and the bw_accounting file is now obsolete. Closes
410 - Document more of the files in the Tor data directory, including
411 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
412 approved-routers, sr-random, and diff-cache. Found while fixing
416 Changes in version 0.3.0.9 - 2017-06-29
417 Tor 0.3.0.9 fixes a path selection bug that would allow a client
418 to use a guard that was in the same network family as a chosen exit
419 relay. This is a security regression; all clients running earlier
420 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
423 This release also backports several other bugfixes from the 0.3.1.x
426 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
427 - When choosing which guard to use for a circuit, avoid the exit's
428 family along with the exit itself. Previously, the new guard
429 selection logic avoided the exit, but did not consider its family.
430 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
431 006 and CVE-2017-0377.
433 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
434 - Don't block bootstrapping when a primary bridge is offline and we
435 can't get its descriptor. Fixes bug 22325; fixes one case of bug
436 21969; bugfix on 0.3.0.3-alpha.
438 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
439 - When starting with an old consensus, do not add new entry guards
440 unless the consensus is "reasonably live" (under 1 day old). Fixes
441 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
443 o Minor features (geoip):
444 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
447 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
448 - Reject version numbers with non-numeric prefixes (such as +, -, or
449 whitespace). Disallowing whitespace prevents differential version
450 parsing between POSIX-based and Windows platforms. Fixes bug 21507
451 and part of 21508; bugfix on 0.0.8pre1.
453 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
454 - Permit the fchmod system call, to avoid crashing on startup when
455 starting with the seccomp2 sandbox and an unexpected set of
456 permissions on the data directory or its contents. Fixes bug
457 22516; bugfix on 0.2.5.4-alpha.
459 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
460 - Fix a memset() off the end of an array when packing cells. This
461 bug should be harmless in practice, since the corrupted bytes are
462 still in the same structure, and are always padding bytes,
463 ignored, or immediately overwritten, depending on compiler
464 behavior. Nevertheless, because the memset()'s purpose is to make
465 sure that any other cell-handling bugs can't expose bytes to the
466 network, we need to fix it. Fixes bug 22737; bugfix on
467 0.2.4.11-alpha. Fixes CID 1401591.
470 Changes in version 0.3.1.3-alpha - 2017-06-08
471 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
472 remotely crash a hidden service with an assertion failure. Anyone
473 running a hidden service should upgrade to this version, or to some
474 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
476 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
477 that sometimes made relays unreliable, as well as several other
478 bugfixes described below.
480 o Major bugfixes (hidden service, relay, security):
481 - Fix a remotely triggerable assertion failure when a hidden service
482 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
483 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
484 - Fix a remotely triggerable assertion failure caused by receiving a
485 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
486 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
489 o Major bugfixes (relay, link handshake):
490 - When performing the v3 link handshake on a TLS connection, report
491 that we have the x509 certificate that we actually used on that
492 connection, even if we have changed certificates since that
493 connection was first opened. Previously, we would claim to have
494 used our most recent x509 link certificate, which would sometimes
495 make the link handshake fail. Fixes one case of bug 22460; bugfix
498 o Major bugfixes (relays, key management):
499 - Regenerate link and authentication certificates whenever the key
500 that signs them changes; also, regenerate link certificates
501 whenever the signed key changes. Previously, these processes were
502 only weakly coupled, and we relays could (for minutes to hours)
503 wind up with an inconsistent set of keys and certificates, which
504 other relays would not accept. Fixes two cases of bug 22460;
505 bugfix on 0.3.0.1-alpha.
506 - When sending an Ed25519 signing->link certificate in a CERTS cell,
507 send the certificate that matches the x509 certificate that we
508 used on the TLS connection. Previously, there was a race condition
509 if the TLS context rotated after we began the TLS handshake but
510 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
513 o Major bugfixes (torrc, crash):
514 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
515 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
517 o Minor features (code style):
518 - Add "Falls through" comments to our codebase, in order to silence
519 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
520 Stieger. Closes ticket 22446.
522 o Minor features (diagnostic):
523 - Add logging messages to try to diagnose a rare bug that seems to
524 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
525 think this is happening because of incorrect system clocks, but
526 we'd like to know for certain. Diagnostic for bug 22466.
528 o Minor bugfixes (correctness):
529 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
530 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
532 o Minor bugfixes (directory protocol):
533 - Check for libzstd >= 1.1, because older versions lack the
534 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
536 o Minor bugfixes (link handshake):
537 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
538 months, and regenerate it when it is within one month of expiring.
539 Previously, we had generated this certificate at startup with a
540 ten-year lifetime, but that could lead to weird behavior when Tor
541 was started with a grossly inaccurate clock. Mitigates bug 22466;
542 mitigation on 0.3.0.1-alpha.
544 o Minor bugfixes (storage directories):
545 - Always check for underflows in the cached storage directory usage.
546 If the usage does underflow, re-calculate it. Also, avoid a
547 separate underflow when the usage is not known. Fixes bug 22424;
548 bugfix on 0.3.1.1-alpha.
550 o Minor bugfixes (unit tests):
551 - The unit tests now pass on systems where localhost is misconfigured
552 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
556 - Clarify the manpage for the (deprecated) torify script. Closes
559 Changes in version 0.3.0.8 - 2017-06-08
560 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
561 remotely crash a hidden service with an assertion failure. Anyone
562 running a hidden service should upgrade to this version, or to some
563 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
565 Tor 0.3.0.8 also includes fixes for several key management bugs
566 that sometimes made relays unreliable, as well as several other
567 bugfixes described below.
569 o Major bugfixes (hidden service, relay, security, backport
571 - Fix a remotely triggerable assertion failure when a hidden service
572 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
573 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
574 - Fix a remotely triggerable assertion failure caused by receiving a
575 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
576 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
579 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
580 - When performing the v3 link handshake on a TLS connection, report
581 that we have the x509 certificate that we actually used on that
582 connection, even if we have changed certificates since that
583 connection was first opened. Previously, we would claim to have
584 used our most recent x509 link certificate, which would sometimes
585 make the link handshake fail. Fixes one case of bug 22460; bugfix
588 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
589 - Regenerate link and authentication certificates whenever the key
590 that signs them changes; also, regenerate link certificates
591 whenever the signed key changes. Previously, these processes were
592 only weakly coupled, and we relays could (for minutes to hours)
593 wind up with an inconsistent set of keys and certificates, which
594 other relays would not accept. Fixes two cases of bug 22460;
595 bugfix on 0.3.0.1-alpha.
596 - When sending an Ed25519 signing->link certificate in a CERTS cell,
597 send the certificate that matches the x509 certificate that we
598 used on the TLS connection. Previously, there was a race condition
599 if the TLS context rotated after we began the TLS handshake but
600 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
603 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
604 - Stop rejecting v3 hidden service descriptors because their size
605 did not match an old padding rule. Fixes bug 22447; bugfix on
608 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
609 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
610 December 2016 (of which ~126 were still functional) with a list of
611 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
612 2017. Resolves ticket 21564.
614 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
615 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
616 bug 22252; bugfix on 0.2.9.3-alpha.
618 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
619 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
620 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
622 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
623 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
624 months, and regenerate it when it is within one month of expiring.
625 Previously, we had generated this certificate at startup with a
626 ten-year lifetime, but that could lead to weird behavior when Tor
627 was started with a grossly inaccurate clock. Mitigates bug 22466;
628 mitigation on 0.3.0.1-alpha.
630 o Minor bugfixes (memory leak, directory authority, backport from
632 - When directory authorities reject a router descriptor due to
633 keypinning, free the router descriptor rather than leaking the
634 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
637 Changes in version 0.2.9.11 - 2017-06-08
638 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
639 remotely crash a hidden service with an assertion failure. Anyone
640 running a hidden service should upgrade to this version, or to some
641 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
642 are not affected by TROVE-2017-004.)
644 Tor 0.2.9.11 also backports fixes for several key management bugs
645 that sometimes made relays unreliable, as well as several other
646 bugfixes described below.
648 o Major bugfixes (hidden service, relay, security, backport
650 - Fix a remotely triggerable assertion failure caused by receiving a
651 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
652 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
655 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
656 - When performing the v3 link handshake on a TLS connection, report
657 that we have the x509 certificate that we actually used on that
658 connection, even if we have changed certificates since that
659 connection was first opened. Previously, we would claim to have
660 used our most recent x509 link certificate, which would sometimes
661 make the link handshake fail. Fixes one case of bug 22460; bugfix
664 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
665 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
666 December 2016 (of which ~126 were still functional) with a list of
667 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
668 2017. Resolves ticket 21564.
670 o Minor features (future-proofing, backport from 0.3.0.7):
671 - Tor no longer refuses to download microdescriptors or descriptors if
672 they are listed as "published in the future". This change will
673 eventually allow us to stop listing meaningful "published" dates
674 in microdescriptor consensuses, and thereby allow us to reduce the
675 resources required to download consensus diffs by over 50%.
676 Implements part of ticket 21642; implements part of proposal 275.
678 o Minor features (directory authorities, backport from 0.3.0.4-rc)
679 - Directory authorities now reject relays running versions
680 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
681 suffer from bug 20499 and don't keep their consensus cache
682 up-to-date. Resolves ticket 20509.
684 o Minor features (geoip):
685 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
688 o Minor bugfixes (control port, backport from 0.3.0.6):
689 - The GETINFO extra-info/digest/<digest> command was broken because
690 of a wrong base16 decode return value check, introduced when
691 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
693 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
694 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
695 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
697 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
698 - The getpid() system call is now permitted under the Linux seccomp2
699 sandbox, to avoid crashing with versions of OpenSSL (and other
700 libraries) that attempt to learn the process's PID by using the
701 syscall rather than the VDSO code. Fixes bug 21943; bugfix
704 o Minor bugfixes (memory leak, directory authority, backport
706 - When directory authorities reject a router descriptor due to
707 keypinning, free the router descriptor rather than leaking the
708 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
710 Changes in version 0.2.8.14 - 2017-06-08
711 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
712 remotely crash a hidden service with an assertion failure. Anyone
713 running a hidden service should upgrade to this version, or to some
714 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
715 are not affected by TROVE-2017-004.)
717 o Major bugfixes (hidden service, relay, security):
718 - Fix a remotely triggerable assertion failure caused by receiving a
719 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
720 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
723 o Minor features (geoip):
724 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
727 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
728 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
729 December 2016 (of which ~126 were still functional) with a list of
730 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
731 2017. Resolves ticket 21564.
733 o Minor bugfixes (correctness):
734 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
735 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
737 Changes in version 0.2.7.8 - 2017-06-08
738 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
739 remotely crash a hidden service with an assertion failure. Anyone
740 running a hidden service should upgrade to this version, or to some
741 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
742 are not affected by TROVE-2017-004.)
744 o Major bugfixes (hidden service, relay, security):
745 - Fix a remotely triggerable assertion failure caused by receiving a
746 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
747 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
750 o Minor features (geoip):
751 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
754 o Minor bugfixes (correctness):
755 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
756 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
759 Changes in version 0.2.6.12 - 2017-06-08
760 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
761 remotely crash a hidden service with an assertion failure. Anyone
762 running a hidden service should upgrade to this version, or to some
763 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
764 are not affected by TROVE-2017-004.)
766 o Major bugfixes (hidden service, relay, security):
767 - Fix a remotely triggerable assertion failure caused by receiving a
768 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
769 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
772 o Minor features (geoip):
773 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
776 o Minor bugfixes (correctness):
777 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
778 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
780 Changes in version 0.2.5.14 - 2017-06-08
781 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
782 remotely crash a hidden service with an assertion failure. Anyone
783 running a hidden service should upgrade to this version, or to some
784 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
785 are not affected by TROVE-2017-004.)
787 o Major bugfixes (hidden service, relay, security):
788 - Fix a remotely triggerable assertion failure caused by receiving a
789 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
790 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
793 o Minor features (geoip):
794 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
797 o Minor bugfixes (correctness):
798 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
799 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
801 Changes in version 0.2.4.29 - 2017-06-08
802 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
803 remotely crash a hidden service with an assertion failure. Anyone
804 running a hidden service should upgrade to this version, or to some
805 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
806 are not affected by TROVE-2017-004.)
808 o Major bugfixes (hidden service, relay, security):
809 - Fix a remotely triggerable assertion failure caused by receiving a
810 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
811 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
814 o Minor features (geoip):
815 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
818 o Minor bugfixes (correctness):
819 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
820 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
823 Changes in version 0.3.1.2-alpha - 2017-05-26
824 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
825 fixes a few bugs found while testing 0.3.1.1-alpha, including a
826 memory corruption bug that affected relay stability.
828 o Major bugfixes (crash, relay):
829 - Fix a memory-corruption bug in relays that set MyFamily.
830 Previously, they would double-free MyFamily elements when making
831 the next descriptor or when changing their configuration. Fixes
832 bug 22368; bugfix on 0.3.1.1-alpha.
834 o Minor bugfixes (logging):
835 - Log a better message when a directory authority replies to an
836 upload with an unexpected status code. Fixes bug 11121; bugfix
839 o Minor bugfixes (memory leak, directory authority):
840 - When directory authorities reject a router descriptor due to
841 keypinning, free the router descriptor rather than leaking the
842 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
845 Changes in version 0.3.1.1-alpha - 2017-05-22
846 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
847 reduces the bandwidth usage for Tor's directory protocol, adds some
848 basic padding to resist netflow-based traffic analysis and to serve as
849 the basis of other padding in the future, and adds rust support to the
852 It also contains numerous other small features and improvements to
853 security, correctness, and performance.
855 Below are the changes since 0.3.0.7.
857 o Major features (directory protocol):
858 - Tor relays and authorities can now serve clients an abbreviated
859 version of the consensus document, containing only the changes
860 since an older consensus document that the client holds. Clients
861 now request these documents when available. When both client and
862 server use this new protocol, they will use far less bandwidth (up
863 to 94% less) to keep the client's consensus up-to-date. Implements
864 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
865 - Tor can now compress directory traffic with lzma or with zstd
866 compression algorithms, which can deliver better bandwidth
867 performance. Because lzma is computationally expensive, it's only
868 used for documents that can be compressed once and served many
869 times. Support for these algorithms requires that tor is built
870 with the libzstd and/or liblzma libraries available. Implements
871 proposal 278; closes ticket 21662.
872 - Relays now perform the more expensive compression operations, and
873 consensus diff generation, in worker threads. This separation
874 avoids delaying the main thread when a new consensus arrives.
876 o Major features (experimental):
877 - Tor can now build modules written in Rust. To turn this on, pass
878 the "--enable-rust" flag to the configure script. It's not time to
879 get excited yet: currently, there is no actual Rust functionality
880 beyond some simple glue code, and a notice at startup to tell you
881 that Rust is running. Still, we hope that programmers and
882 packagers will try building Tor with Rust support, so that we can
883 find issues and solve portability problems. Closes ticket 22106.
885 o Major features (traffic analysis resistance):
886 - Connections between clients and relays now send a padding cell in
887 each direction every 1.5 to 9.5 seconds (tunable via consensus
888 parameters). This padding will not resist specialized
889 eavesdroppers, but it should be enough to make many ISPs' routine
890 network flow logging less useful in traffic analysis against
893 Padding is negotiated using Tor's link protocol, so both relays
894 and clients must upgrade for this to take effect. Clients may
895 still send padding despite the relay's version by setting
896 ConnectionPadding 1 in torrc, and may disable padding by setting
897 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
898 users with the torrc option ReducedConnectionPadding. Implements
899 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
900 - Relays will publish 24 hour totals of padding and non-padding cell
901 counts to their extra-info descriptors, unless PaddingStatistics 0
902 is set in torrc. These 24 hour totals are also rounded to
905 o Major bugfixes (connection usage):
906 - We use NETINFO cells to try to determine if both relays involved
907 in a connection will agree on the canonical status of that
908 connection. We prefer the connections where this is the case for
909 extend cells, and try to close connections where relays disagree
910 on their canonical status early. Also, we now prefer the oldest
911 valid connection for extend cells. These two changes should reduce
912 the number of long-term connections that are kept open between
913 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
914 - Relays now log hourly statistics (look for
915 "channel_check_for_duplicates" lines) on the total number of
916 connections to other relays. If the number of connections per
917 relay is unexpectedly large, this log message is at notice level.
918 Otherwise it is at info.
920 o Major bugfixes (entry guards):
921 - Don't block bootstrapping when a primary bridge is offline and we
922 can't get its descriptor. Fixes bug 22325; fixes one case of bug
923 21969; bugfix on 0.3.0.3-alpha.
925 o Major bugfixes (linux TPROXY support):
926 - Fix a typo that had prevented TPROXY-based transparent proxying
927 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
928 Patch from "d4fq0fQAgoJ".
930 o Minor features (security, windows):
931 - Enable a couple of pieces of Windows hardening: one
932 (HeapEnableTerminationOnCorruption) that has been on-by-default
933 since Windows 8, and unavailable before Windows 7; and one
934 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
935 affect us, but shouldn't do any harm. Closes ticket 21953.
937 o Minor features (config options):
938 - Allow "%include" directives in torrc configuration files. These
939 directives import the settings from other files, or from all the
940 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
941 - Make SAVECONF return an error when overwriting a torrc that has
942 includes. Using SAVECONF with the FORCE option will allow it to
943 overwrite torrc even if includes are used. Related to ticket 1922.
944 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
945 will work without the FORCE option. Related to ticket 1922.
947 o Minor features (controller):
948 - Warn the first time that a controller requests data in the long-
949 deprecated 'GETINFO network-status' format. Closes ticket 21703.
951 o Minor features (defaults):
952 - The default value for UseCreateFast is now 0: clients which
953 haven't yet received a consensus document will now use a proper
954 ntor handshake to talk to their directory servers whenever they
955 can. Closes ticket 21407.
956 - Onion key rotation and expiry intervals are now defined as a
957 network consensus parameter, per proposal 274. The default
958 lifetime of an onion key is increased from 7 to 28 days. Old onion
959 keys will expire after 7 days by default. This change will make
960 consensus diffs much smaller, and save significant bandwidth.
963 o Minor features (fallback directory list):
964 - Update the fallback directory mirror whitelist and blacklist based
965 on operator emails. Closes task 21121.
966 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
967 December 2016 (of which ~126 were still functional) with a list of
968 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
969 2017. Resolves ticket 21564.
971 o Minor features (hidden services, logging):
972 - Log a message when a hidden service descriptor has fewer
973 introduction points than specified in
974 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
975 - Log a message when a hidden service reaches its introduction point
976 circuit limit, and when that limit is reset. Follow up to ticket
977 21594; closes ticket 21622.
978 - Warn user if multiple entries in EntryNodes and at least one
979 HiddenService are used together. Pinning EntryNodes along with a
980 hidden service can be possibly harmful; for instance see ticket
981 14917 or 21155. Closes ticket 21155.
983 o Minor features (linux seccomp2 sandbox):
984 - We now have a document storage backend compatible with the Linux
985 seccomp2 sandbox. This backend is used for consensus documents and
986 diffs between them; in the long term, we'd like to use it for
987 unparseable directory material too. Closes ticket 21645
988 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
989 from 1MB to 16MB. This was necessary with the glibc allocator in
990 order to allow worker threads to allocate more memory -- which in
991 turn is necessary because of our new use of worker threads for
992 compression. Closes ticket 22096.
994 o Minor features (logging):
995 - Log files are no longer created world-readable by default.
996 (Previously, most distributors would store the logs in a non-
997 world-readable location to prevent inappropriate access. This
998 change is an extra precaution.) Closes ticket 21729; patch
1001 o Minor features (performance):
1002 - Our Keccak (SHA-3) implementation now accesses memory more
1003 efficiently, especially on little-endian systems. Closes
1005 - Add an O(1) implementation of channel_find_by_global_id(), to
1006 speed some controller functions.
1008 o Minor features (relay, configuration):
1009 - The MyFamily option may now be repeated as many times as desired,
1010 for relays that want to configure large families. Closes ticket
1011 4998; patch by Daniel Pinto.
1013 o Minor features (safety):
1014 - Add an explicit check to extrainfo_parse_entry_from_string() for
1015 NULL inputs. We don't believe this can actually happen, but it may
1016 help silence a warning from the Clang analyzer. Closes
1019 o Minor features (testing):
1020 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
1021 When Tor is compiled with this option, we disable a number of
1022 redundant memory-safety failsafes that are intended to stop bugs
1023 from becoming security issues. This makes it easier to hunt for
1024 bugs that would be security issues without the failsafes turned
1025 on. Closes ticket 21439.
1026 - Add a general event-tracing instrumentation support to Tor. This
1027 subsystem will enable developers and researchers to add fine-
1028 grained instrumentation to their Tor instances, for use when
1029 examining Tor network performance issues. There are no trace
1030 events yet, and event-tracing is off by default unless enabled at
1031 compile time. Implements ticket 13802.
1032 - Improve our version parsing tests: add tests for typical version
1033 components, add tests for invalid versions, including numeric
1034 range and non-numeric prefixes. Unit tests 21278, 21450, and
1035 21507. Partially implements 21470.
1037 o Minor bugfixes (bandwidth accounting):
1038 - Roll over monthly accounting at the configured hour and minute,
1039 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
1040 Found by Andrey Karpov with PVS-Studio.
1042 o Minor bugfixes (code correctness):
1043 - Accurately identify client connections by their lack of peer
1044 authentication. This means that we bail out earlier if asked to
1045 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
1048 o Minor bugfixes (configuration):
1049 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
1050 bug 22252; bugfix on 0.2.9.3-alpha.
1052 o Minor bugfixes (connection lifespan):
1053 - Allow more control over how long TLS connections are kept open:
1054 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
1055 single option called CircuitsAvailableTimeout. Also, allow the
1056 consensus to control the default values for both this preference
1057 and the lifespan of relay-to-relay connections. Fixes bug 17592;
1058 bugfix on 0.2.5.5-alpha.
1059 - Increase the initial circuit build timeout testing frequency, to
1060 help ensure that ReducedConnectionPadding clients finish learning
1061 a timeout before their orconn would expire. The initial testing
1062 rate was set back in the days of TAP and before the Tor Browser
1063 updater, when we had to be much more careful about new clients
1064 making lots of circuits. With this change, a circuit build timeout
1065 is learned in about 15-20 minutes, instead of 100-120 minutes.
1067 o Minor bugfixes (controller):
1068 - GETINFO onions/current and onions/detached no longer respond with
1069 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
1070 - Trigger HS descriptor events on the control port when the client
1071 fails to pick a hidden service directory for a hidden service.
1072 This can happen if all the hidden service directories are in
1073 ExcludeNodes, or they have all been queried within the last 15
1074 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
1076 o Minor bugfixes (directory authority):
1077 - When rejecting a router descriptor for running an obsolete version
1078 of Tor without ntor support, warn about the obsolete tor version,
1079 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
1080 - Prevent the shared randomness subsystem from asserting when
1081 initialized by a bridge authority with an incomplete configuration
1082 file. Fixes bug 21586; bugfix on 0.2.9.8.
1084 o Minor bugfixes (exit-side DNS):
1085 - Fix an untriggerable assertion that checked the output of a
1086 libevent DNS error, so that the assertion actually behaves as
1087 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
1088 Karpov using PVS-Studio.
1090 o Minor bugfixes (fallback directories):
1091 - Make the usage example in updateFallbackDirs.py actually work, and
1092 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
1093 - Decrease the guard flag average required to be a fallback. This
1094 allows us to keep relays that have their guard flag removed when
1095 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
1096 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
1097 bugfix on 0.2.8.1-alpha.
1098 - Make sure fallback directory mirrors have the same address, port,
1099 and relay identity key for at least 30 days before they are
1100 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
1102 o Minor bugfixes (hidden services):
1103 - Stop printing a cryptic warning when a hidden service gets a
1104 request to connect to a virtual port that it hasn't configured.
1105 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
1106 - Simplify hidden service descriptor creation by using an existing
1107 flag to check if an introduction point is established. Fixes bug
1108 21599; bugfix on 0.2.7.2-alpha.
1110 o Minor bugfixes (memory leak):
1111 - Fix a small memory leak at exit from the backtrace handler code.
1112 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
1114 o Minor bugfixes (protocol, logging):
1115 - Downgrade a log statement about unexpected relay cells from "bug"
1116 to "protocol warning", because there is at least one use case
1117 where it can be triggered by a buggy tor implementation. Fixes bug
1118 21293; bugfix on 0.1.1.14-alpha.
1120 o Minor bugfixes (testing):
1121 - Use unbuffered I/O for utility functions around the
1122 process_handle_t type. This fixes unit test failures reported on
1123 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
1124 - Make display of captured unit test log messages consistent. Fixes
1125 bug 21510; bugfix on 0.2.9.3-alpha.
1126 - Make test-network.sh always call chutney's test-network.sh.
1127 Previously, this only worked on systems which had bash installed,
1128 due to some bash-specific code in the script. Fixes bug 19699;
1129 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
1131 o Minor bugfixes (voting consistency):
1132 - Reject version numbers with non-numeric prefixes (such as +, -, or
1133 whitespace). Disallowing whitespace prevents differential version
1134 parsing between POSIX-based and Windows platforms. Fixes bug 21507
1135 and part of 21508; bugfix on 0.0.8pre1.
1137 o Minor bugfixes (windows, relay):
1138 - Resolve "Failure from drain_fd: No error" warnings on Windows
1139 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
1141 o Code simplification and refactoring:
1142 - Break up the 630-line function connection_dir_client_reached_eof()
1143 into a dozen smaller functions. This change should help
1144 maintainability and readability of the client directory code.
1145 - Isolate our use of the openssl headers so that they are only
1146 included from our crypto wrapper modules, and from tests that
1147 examine those modules' internals. Closes ticket 21841.
1148 - Simplify our API to launch directory requests, making it more
1149 extensible and less error-prone. Now it's easier to add extra
1150 headers to directory requests. Closes ticket 21646.
1151 - Our base64 decoding functions no longer overestimate the output
1152 space that they need when parsing unpadded inputs. Closes
1154 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
1155 Resolves ticket 22213.
1156 - The logic that directory caches use to spool request to clients,
1157 serving them one part at a time so as not to allocate too much
1158 memory, has been refactored for consistency. Previously there was
1159 a separate spooling implementation per type of spoolable data. Now
1160 there is one common spooling implementation, with extensible data
1161 types. Closes ticket 21651.
1162 - Tor's compression module now supports multiple backends. Part of
1163 the implementation for proposal 278; closes ticket 21663.
1166 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
1167 Closes ticket 21873.
1168 - Correct documentation about the default DataDirectory value.
1169 Closes ticket 21151.
1170 - Document the default behavior of NumEntryGuards and
1171 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
1173 - Document key=value pluggable transport arguments for Bridge lines
1174 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
1175 - Note that bandwidth-limiting options don't affect TCP headers or
1176 DNS. Closes ticket 17170.
1178 o Removed features (configuration options, all in ticket 22060):
1179 - These configuration options are now marked Obsolete, and no longer
1180 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
1181 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
1182 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
1183 in 0.2.9.2-alpha and have now been removed. The previous default
1184 behavior is now always chosen; the previous (less secure) non-
1185 default behavior is now unavailable.
1186 - CloseHSClientCircuitsImmediatelyOnTimeout and
1187 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
1188 0.2.9.2-alpha and now have been removed. HS circuits never close
1189 on circuit build timeout; they have a longer timeout period.
1190 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
1191 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
1192 (and others) to configure listen-only and advertise-only addresses.
1194 o Removed features (tools):
1195 - We've removed the tor-checkkey tool from src/tools. Long ago, we
1196 used it to help people detect RSA keys that were generated by
1197 versions of Debian affected by CVE-2008-0166. But those keys have
1198 been out of circulation for ages, and this tool is no longer
1199 required. Closes ticket 21842.
1202 Changes in version 0.3.0.7 - 2017-05-15
1203 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
1204 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
1205 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
1206 clients are not affected.
1208 o Major bugfixes (hidden service directory, security):
1209 - Fix an assertion failure in the hidden service directory code, which
1210 could be used by an attacker to remotely cause a Tor relay process to
1211 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
1212 should upgrade. This security issue is tracked as TROVE-2017-002.
1213 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
1216 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
1219 o Minor features (future-proofing):
1220 - Tor no longer refuses to download microdescriptors or descriptors
1221 if they are listed as "published in the future". This change will
1222 eventually allow us to stop listing meaningful "published" dates
1223 in microdescriptor consensuses, and thereby allow us to reduce the
1224 resources required to download consensus diffs by over 50%.
1225 Implements part of ticket 21642; implements part of proposal 275.
1227 o Minor bugfixes (Linux seccomp2 sandbox):
1228 - The getpid() system call is now permitted under the Linux seccomp2
1229 sandbox, to avoid crashing with versions of OpenSSL (and other
1230 libraries) that attempt to learn the process's PID by using the
1231 syscall rather than the VDSO code. Fixes bug 21943; bugfix
1235 Changes in version 0.3.0.6 - 2017-04-26
1236 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
1238 With the 0.3.0 series, clients and relays now use Ed25519 keys to
1239 authenticate their link connections to relays, rather than the old
1240 RSA1024 keys that they used before. (Circuit crypto has been
1241 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
1242 the guard selection and replacement algorithm to behave more robustly
1243 in the presence of unreliable networks, and to resist guard-
1246 This series also includes numerous other small features and bugfixes,
1247 along with more groundwork for the upcoming hidden-services revamp.
1249 Per our stable release policy, we plan to support the Tor 0.3.0
1250 release series for at least the next nine months, or for three months
1251 after the first stable release of the 0.3.1 series: whichever is
1252 longer. If you need a release with long-term support, we recommend
1253 that you stay with the 0.2.9 series.
1255 Below are the changes since 0.3.0.5-rc. For a list of all changes
1256 since 0.2.9, see the ReleaseNotes file.
1258 o Minor features (geoip):
1259 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
1262 o Minor bugfixes (control port):
1263 - The GETINFO extra-info/digest/<digest> command was broken because
1264 of a wrong base16 decode return value check, introduced when
1265 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
1267 o Minor bugfixes (crash prevention):
1268 - Fix a (currently untriggerable, but potentially dangerous) crash
1269 bug when base32-encoding inputs whose sizes are not a multiple of
1270 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
1273 Changes in version 0.3.0.5-rc - 2017-04-05
1274 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
1275 0.3.0 release series.
1277 This is the second release candidate in the Tor 0.3.0 series, and has
1278 much fewer changes than the first. If we find no new bugs or
1279 regressions here, the first stable 0.3.0 release will be nearly
1282 o Major bugfixes (crash, directory connections):
1283 - Fix a rare crash when sending a begin cell on a circuit whose
1284 linked directory connection had already been closed. Fixes bug
1285 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
1287 o Major bugfixes (guard selection):
1288 - Fix a guard selection bug where Tor would refuse to bootstrap in
1289 some cases if the user swapped a bridge for another bridge in
1290 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
1291 Reported by "torvlnt33r".
1293 o Minor features (geoip):
1294 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
1297 o Minor bugfix (compilation):
1298 - Fix a warning when compiling hs_service.c. Previously, it had no
1299 exported symbols when compiled for libor.a, resulting in a
1300 compilation warning from clang. Fixes bug 21825; bugfix
1303 o Minor bugfixes (hidden services):
1304 - Make hidden services check for failed intro point connections,
1305 even when they have exceeded their intro point creation limit.
1306 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
1307 - Make hidden services with 8 to 10 introduction points check for
1308 failed circuits immediately after startup. Previously, they would
1309 wait for 5 minutes before performing their first checks. Fixes bug
1310 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
1312 o Minor bugfixes (memory leaks):
1313 - Fix a memory leak when using GETCONF on a port option. Fixes bug
1314 21682; bugfix on 0.3.0.3-alpha.
1316 o Minor bugfixes (relay):
1317 - Avoid a double-marked-circuit warning that could happen when we
1318 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
1321 o Minor bugfixes (tests):
1322 - Run the entry_guard_parse_from_state_full() test with the time set
1323 to a specific date. (The guard state that this test was parsing
1324 contained guards that had expired since the test was first
1325 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
1328 - Update the description of the directory server options in the
1329 manual page, to clarify that a relay no longer needs to set
1330 DirPort in order to be a directory cache. Closes ticket 21720.
1334 Changes in version 0.2.8.13 - 2017-03-03
1335 Tor 0.2.8.13 backports a security fix from later Tor
1336 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
1337 this release, if for some reason they cannot upgrade to a later
1338 release series, and if they build Tor with the --enable-expensive-hardening
1341 Note that support for Tor 0.2.8.x is ending next year: we will not issue
1342 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
1343 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
1345 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
1346 - Fix an integer underflow bug when comparing malformed Tor
1347 versions. This bug could crash Tor when built with
1348 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1349 0.2.9.8, which were built with -ftrapv by default. In other cases
1350 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1351 on 0.0.8pre1. Found by OSS-Fuzz.
1353 o Minor features (geoip):
1354 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1358 Changes in version 0.2.7.7 - 2017-03-03
1359 Tor 0.2.7.7 backports a number of security fixes from later Tor
1360 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
1361 this release, if for some reason they cannot upgrade to a later
1364 Note that support for Tor 0.2.7.x is ending this year: we will not issue
1365 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
1366 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
1368 o Directory authority changes (backport from 0.2.8.5-rc):
1369 - Urras is no longer a directory authority. Closes ticket 19271.
1371 o Directory authority changes (backport from 0.2.9.2-alpha):
1372 - The "Tonga" bridge authority has been retired; the new bridge
1373 authority is "Bifroest". Closes tickets 19728 and 19690.
1375 o Directory authority key updates (backport from 0.2.8.1-alpha):
1376 - Update the V3 identity key for the dannenberg directory authority:
1377 it was changed on 18 November 2015. Closes task 17906. Patch
1380 o Major bugfixes (parsing, security, backport from 0.2.9.8):
1381 - Fix a bug in parsing that could cause clients to read a single
1382 byte past the end of an allocated region. This bug could be used
1383 to cause hardened clients (built with --enable-expensive-hardening)
1384 to crash if they tried to visit a hostile hidden service. Non-
1385 hardened clients are only affected depending on the details of
1386 their platform's memory allocator. Fixes bug 21018; bugfix on
1387 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
1388 2016-12-002 and as CVE-2016-1254.
1390 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
1391 - Stop a crash that could occur when a client running with DNSPort
1392 received a query with multiple address types, and the first
1393 address type was not supported. Found and fixed by Scott Dial.
1394 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
1395 - Prevent a class of security bugs caused by treating the contents
1396 of a buffer chunk as if they were a NUL-terminated string. At
1397 least one such bug seems to be present in all currently used
1398 versions of Tor, and would allow an attacker to remotely crash
1399 most Tor instances, especially those compiled with extra compiler
1400 hardening. With this defense in place, such bugs can't crash Tor,
1401 though we should still fix them as they occur. Closes ticket
1402 20384 (TROVE-2016-10-001).
1404 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
1405 - Avoid a difficult-to-trigger heap corruption attack when extending
1406 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
1407 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
1408 Reported by Guido Vranken.
1410 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
1411 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
1412 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
1414 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
1415 - If OpenSSL fails to generate an RSA key, do not retain a dangling
1416 pointer to the previous (uninitialized) key value. The impact here
1417 should be limited to a difficult-to-trigger crash, if OpenSSL is
1418 running an engine that makes key generation failures possible, or
1419 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
1420 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
1423 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
1424 - Fix an integer underflow bug when comparing malformed Tor
1425 versions. This bug could crash Tor when built with
1426 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1427 0.2.9.8, which were built with -ftrapv by default. In other cases
1428 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1429 on 0.0.8pre1. Found by OSS-Fuzz.
1431 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
1432 - Make memwipe() do nothing when passed a NULL pointer or buffer of
1433 zero size. Check size argument to memwipe() for underflow. Fixes
1434 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
1437 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
1438 - Make Tor survive errors involving connections without a
1439 corresponding event object. Previously we'd fail with an
1440 assertion; now we produce a log message. Related to bug 16248.
1442 o Minor features (geoip):
1443 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1447 Changes in version 0.2.6.11 - 2017-03-03
1448 Tor 0.2.6.11 backports a number of security fixes from later Tor
1449 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
1450 this release, if for some reason they cannot upgrade to a later
1453 Note that support for Tor 0.2.6.x is ending this year: we will not issue
1454 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
1455 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
1457 o Directory authority changes (backport from 0.2.8.5-rc):
1458 - Urras is no longer a directory authority. Closes ticket 19271.
1460 o Directory authority changes (backport from 0.2.9.2-alpha):
1461 - The "Tonga" bridge authority has been retired; the new bridge
1462 authority is "Bifroest". Closes tickets 19728 and 19690.
1464 o Directory authority key updates (backport from 0.2.8.1-alpha):
1465 - Update the V3 identity key for the dannenberg directory authority:
1466 it was changed on 18 November 2015. Closes task 17906. Patch
1469 o Major features (security fixes, backport from 0.2.9.4-alpha):
1470 - Prevent a class of security bugs caused by treating the contents
1471 of a buffer chunk as if they were a NUL-terminated string. At
1472 least one such bug seems to be present in all currently used
1473 versions of Tor, and would allow an attacker to remotely crash
1474 most Tor instances, especially those compiled with extra compiler
1475 hardening. With this defense in place, such bugs can't crash Tor,
1476 though we should still fix them as they occur. Closes ticket
1477 20384 (TROVE-2016-10-001).
1479 o Major bugfixes (parsing, security, backport from 0.2.9.8):
1480 - Fix a bug in parsing that could cause clients to read a single
1481 byte past the end of an allocated region. This bug could be used
1482 to cause hardened clients (built with --enable-expensive-hardening)
1483 to crash if they tried to visit a hostile hidden service. Non-
1484 hardened clients are only affected depending on the details of
1485 their platform's memory allocator. Fixes bug 21018; bugfix on
1486 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
1487 2016-12-002 and as CVE-2016-1254.
1489 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
1490 - Stop a crash that could occur when a client running with DNSPort
1491 received a query with multiple address types, and the first
1492 address type was not supported. Found and fixed by Scott Dial.
1493 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
1495 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
1496 - Fix an error that could cause us to read 4 bytes before the
1497 beginning of an openssl string. This bug could be used to cause
1498 Tor to crash on systems with unusual malloc implementations, or
1499 systems with unusual hardening installed. Fixes bug 17404; bugfix
1502 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
1503 - Avoid a difficult-to-trigger heap corruption attack when extending
1504 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
1505 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
1506 Reported by Guido Vranken.
1508 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
1509 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
1510 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
1512 o Major bugfixes (guard selection, backport from 0.2.7.6):
1513 - Actually look at the Guard flag when selecting a new directory
1514 guard. When we implemented the directory guard design, we
1515 accidentally started treating all relays as if they have the Guard
1516 flag during guard selection, leading to weaker anonymity and worse
1517 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
1520 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
1521 - If OpenSSL fails to generate an RSA key, do not retain a dangling
1522 pointer to the previous (uninitialized) key value. The impact here
1523 should be limited to a difficult-to-trigger crash, if OpenSSL is
1524 running an engine that makes key generation failures possible, or
1525 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
1526 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
1529 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
1530 - Fix an integer underflow bug when comparing malformed Tor
1531 versions. This bug could crash Tor when built with
1532 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1533 0.2.9.8, which were built with -ftrapv by default. In other cases
1534 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1535 on 0.0.8pre1. Found by OSS-Fuzz.
1537 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
1538 - Make memwipe() do nothing when passed a NULL pointer or buffer of
1539 zero size. Check size argument to memwipe() for underflow. Fixes
1540 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
1543 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
1544 - Make Tor survive errors involving connections without a
1545 corresponding event object. Previously we'd fail with an
1546 assertion; now we produce a log message. Related to bug 16248.
1548 o Minor features (geoip):
1549 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1552 o Minor bugfixes (compilation, backport from 0.2.7.6):
1553 - Fix a compilation warning with Clang 3.6: Do not check the
1554 presence of an address which can never be NULL. Fixes bug 17781.
1557 Changes in version 0.2.5.13 - 2017-03-03
1558 Tor 0.2.5.13 backports a number of security fixes from later Tor
1559 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
1560 this release, if for some reason they cannot upgrade to a later
1563 Note that support for Tor 0.2.5.x is ending next year: we will not issue
1564 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
1565 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
1567 o Directory authority changes (backport from 0.2.8.5-rc):
1568 - Urras is no longer a directory authority. Closes ticket 19271.
1570 o Directory authority changes (backport from 0.2.9.2-alpha):
1571 - The "Tonga" bridge authority has been retired; the new bridge
1572 authority is "Bifroest". Closes tickets 19728 and 19690.
1574 o Directory authority key updates (backport from 0.2.8.1-alpha):
1575 - Update the V3 identity key for the dannenberg directory authority:
1576 it was changed on 18 November 2015. Closes task 17906. Patch
1579 o Major features (security fixes, backport from 0.2.9.4-alpha):
1580 - Prevent a class of security bugs caused by treating the contents
1581 of a buffer chunk as if they were a NUL-terminated string. At
1582 least one such bug seems to be present in all currently used
1583 versions of Tor, and would allow an attacker to remotely crash
1584 most Tor instances, especially those compiled with extra compiler
1585 hardening. With this defense in place, such bugs can't crash Tor,
1586 though we should still fix them as they occur. Closes ticket
1587 20384 (TROVE-2016-10-001).
1589 o Major bugfixes (parsing, security, backport from 0.2.9.8):
1590 - Fix a bug in parsing that could cause clients to read a single
1591 byte past the end of an allocated region. This bug could be used
1592 to cause hardened clients (built with --enable-expensive-hardening)
1593 to crash if they tried to visit a hostile hidden service. Non-
1594 hardened clients are only affected depending on the details of
1595 their platform's memory allocator. Fixes bug 21018; bugfix on
1596 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
1597 2016-12-002 and as CVE-2016-1254.
1599 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
1600 - Stop a crash that could occur when a client running with DNSPort
1601 received a query with multiple address types, and the first
1602 address type was not supported. Found and fixed by Scott Dial.
1603 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
1605 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
1606 - Fix an error that could cause us to read 4 bytes before the
1607 beginning of an openssl string. This bug could be used to cause
1608 Tor to crash on systems with unusual malloc implementations, or
1609 systems with unusual hardening installed. Fixes bug 17404; bugfix
1612 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
1613 - Avoid a difficult-to-trigger heap corruption attack when extending
1614 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
1615 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
1616 Reported by Guido Vranken.
1618 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
1619 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
1620 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
1622 o Major bugfixes (guard selection, backport from 0.2.7.6):
1623 - Actually look at the Guard flag when selecting a new directory
1624 guard. When we implemented the directory guard design, we
1625 accidentally started treating all relays as if they have the Guard
1626 flag during guard selection, leading to weaker anonymity and worse
1627 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
1630 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
1631 - If OpenSSL fails to generate an RSA key, do not retain a dangling
1632 pointer to the previous (uninitialized) key value. The impact here
1633 should be limited to a difficult-to-trigger crash, if OpenSSL is
1634 running an engine that makes key generation failures possible, or
1635 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
1636 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
1639 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
1640 - Fix an integer underflow bug when comparing malformed Tor
1641 versions. This bug could crash Tor when built with
1642 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1643 0.2.9.8, which were built with -ftrapv by default. In other cases
1644 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1645 on 0.0.8pre1. Found by OSS-Fuzz.
1647 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
1648 - Make memwipe() do nothing when passed a NULL pointer or buffer of
1649 zero size. Check size argument to memwipe() for underflow. Fixes
1650 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
1653 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
1654 - Make Tor survive errors involving connections without a
1655 corresponding event object. Previously we'd fail with an
1656 assertion; now we produce a log message. Related to bug 16248.
1658 o Minor features (geoip):
1659 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1662 o Minor bugfixes (compilation, backport from 0.2.7.6):
1663 - Fix a compilation warning with Clang 3.6: Do not check the
1664 presence of an address which can never be NULL. Fixes bug 17781.
1666 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
1667 - Check for failures from crypto_early_init, and refuse to continue.
1668 A previous typo meant that we could keep going with an
1669 uninitialized crypto library, and would have OpenSSL initialize
1670 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
1671 when implementing ticket 4900. Patch by "teor".
1673 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
1674 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
1675 a client authorized hidden service. Fixes bug 15823; bugfix
1679 Changes in version 0.2.4.28 - 2017-03-03
1680 Tor 0.2.4.28 backports a number of security fixes from later Tor
1681 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
1682 this release, if for some reason they cannot upgrade to a later
1685 Note that support for Tor 0.2.4.x is ending soon: we will not issue
1686 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
1687 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
1689 o Directory authority changes (backport from 0.2.8.5-rc):
1690 - Urras is no longer a directory authority. Closes ticket 19271.
1692 o Directory authority changes (backport from 0.2.9.2-alpha):
1693 - The "Tonga" bridge authority has been retired; the new bridge
1694 authority is "Bifroest". Closes tickets 19728 and 19690.
1696 o Directory authority key updates (backport from 0.2.8.1-alpha):
1697 - Update the V3 identity key for the dannenberg directory authority:
1698 it was changed on 18 November 2015. Closes task 17906. Patch
1701 o Major features (security fixes, backport from 0.2.9.4-alpha):
1702 - Prevent a class of security bugs caused by treating the contents
1703 of a buffer chunk as if they were a NUL-terminated string. At
1704 least one such bug seems to be present in all currently used
1705 versions of Tor, and would allow an attacker to remotely crash
1706 most Tor instances, especially those compiled with extra compiler
1707 hardening. With this defense in place, such bugs can't crash Tor,
1708 though we should still fix them as they occur. Closes ticket
1709 20384 (TROVE-2016-10-001).
1711 o Major bugfixes (parsing, security, backport from 0.2.9.8):
1712 - Fix a bug in parsing that could cause clients to read a single
1713 byte past the end of an allocated region. This bug could be used
1714 to cause hardened clients (built with --enable-expensive-hardening)
1715 to crash if they tried to visit a hostile hidden service. Non-
1716 hardened clients are only affected depending on the details of
1717 their platform's memory allocator. Fixes bug 21018; bugfix on
1718 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
1719 2016-12-002 and as CVE-2016-1254.
1721 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
1722 - Fix an error that could cause us to read 4 bytes before the
1723 beginning of an openssl string. This bug could be used to cause
1724 Tor to crash on systems with unusual malloc implementations, or
1725 systems with unusual hardening installed. Fixes bug 17404; bugfix
1728 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
1729 - Avoid a difficult-to-trigger heap corruption attack when extending
1730 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
1731 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
1732 Reported by Guido Vranken.
1734 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
1735 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
1736 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
1738 o Major bugfixes (guard selection, backport from 0.2.7.6):
1739 - Actually look at the Guard flag when selecting a new directory
1740 guard. When we implemented the directory guard design, we
1741 accidentally started treating all relays as if they have the Guard
1742 flag during guard selection, leading to weaker anonymity and worse
1743 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
1746 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
1747 - If OpenSSL fails to generate an RSA key, do not retain a dangling
1748 pointer to the previous (uninitialized) key value. The impact here
1749 should be limited to a difficult-to-trigger crash, if OpenSSL is
1750 running an engine that makes key generation failures possible, or
1751 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
1752 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
1755 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
1756 - Fix an integer underflow bug when comparing malformed Tor
1757 versions. This bug could crash Tor when built with
1758 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1759 0.2.9.8, which were built with -ftrapv by default. In other cases
1760 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1761 on 0.0.8pre1. Found by OSS-Fuzz.
1763 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
1764 - Make memwipe() do nothing when passed a NULL pointer or buffer of
1765 zero size. Check size argument to memwipe() for underflow. Fixes
1766 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
1769 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
1770 - Make Tor survive errors involving connections without a
1771 corresponding event object. Previously we'd fail with an
1772 assertion; now we produce a log message. Related to bug 16248.
1774 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
1775 - Make it harder for attackers to overload hidden services with
1776 introductions, by blocking multiple introduction requests on the
1777 same circuit. Resolves ticket 15515.
1779 o Minor features (geoip):
1780 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1783 o Minor bugfixes (compilation, backport from 0.2.7.6):
1784 - Fix a compilation warning with Clang 3.6: Do not check the
1785 presence of an address which can never be NULL. Fixes bug 17781.
1787 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
1788 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
1789 a client authorized hidden service. Fixes bug 15823; bugfix
1793 Changes in version 0.3.0.4-rc - 2017-03-01
1794 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
1795 0.3.0 release series, and introduces a few reliability features to
1796 keep them from coming back.
1798 This is the first release candidate in the Tor 0.3.0 series. If we
1799 find no new bugs or regressions here, the first stable 0.3.0 release
1800 will be nearly identical to it.
1802 o Major bugfixes (bridges):
1803 - When the same bridge is configured multiple times with the same
1804 identity, but at different address:port combinations, treat those
1805 bridge instances as separate guards. This fix restores the ability
1806 of clients to configure the same bridge with multiple pluggable
1807 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
1809 o Major bugfixes (hidden service directory v3):
1810 - Stop crashing on a failed v3 hidden service descriptor lookup
1811 failure. Fixes bug 21471; bugfixes on tor-0.3.0.1-alpha.
1813 o Major bugfixes (parsing):
1814 - When parsing a malformed content-length field from an HTTP
1815 message, do not read off the end of the buffer. This bug was a
1816 potential remote denial-of-service attack against Tor clients and
1817 relays. A workaround was released in October 2016, to prevent this
1818 bug from crashing Tor. This is a fix for the underlying issue,
1819 which should no longer matter (if you applied the earlier patch).
1820 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
1821 using AFL (http://lcamtuf.coredump.cx/afl/).
1822 - Fix an integer underflow bug when comparing malformed Tor
1823 versions. This bug could crash Tor when built with
1824 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1825 0.2.9.8, which were built with -ftrapv by default. In other cases
1826 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1827 on 0.0.8pre1. Found by OSS-Fuzz.
1829 o Minor feature (protocol versioning):
1830 - Add new protocol version for proposal 224. HSIntro now advertises
1831 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
1833 o Minor features (directory authorities):
1834 - Directory authorities now reject descriptors that claim to be
1835 malformed versions of Tor. Helps prevent exploitation of
1837 - Reject version numbers with components that exceed INT32_MAX.
1838 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
1839 Fixes bug 21450; bugfix on 0.0.8pre1.
1840 - Directory authorities now reject relays running versions
1841 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
1842 suffer from bug 20499 and don't keep their consensus cache
1843 up-to-date. Resolves ticket 20509.
1845 o Minor features (geoip):
1846 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1849 o Minor features (reliability, crash):
1850 - Try better to detect problems in buffers where they might grow (or
1851 think they have grown) over 2 GB in size. Diagnostic for
1854 o Minor features (testing):
1855 - During 'make test-network-all', if tor logs any warnings, ask
1856 chutney to output them. Requires a recent version of chutney with
1857 the 21572 patch. Implements 21570.
1859 o Minor bugfixes (certificate expiration time):
1860 - Avoid using link certificates that don't become valid till some
1861 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
1863 o Minor bugfixes (code correctness):
1864 - Repair a couple of (unreachable or harmless) cases of the risky
1865 comparison-by-subtraction pattern that caused bug 21278.
1866 - Remove a redundant check for the UseEntryGuards option from the
1867 options_transition_affects_guards() function. Fixes bug 21492;
1868 bugfix on 0.3.0.1-alpha.
1870 o Minor bugfixes (directory mirrors):
1871 - Allow relays to use directory mirrors without a DirPort: these
1872 relays need to be contacted over their ORPorts using a begindir
1873 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
1874 - Clarify the message logged when a remote relay is unexpectedly
1875 missing an ORPort or DirPort: users were confusing this with a
1876 local port. Fixes another case of bug 20711; bugfix
1879 o Minor bugfixes (guards):
1880 - Don't warn about a missing guard state on timeout-measurement
1881 circuits: they aren't supposed to be using guards. Fixes an
1882 instance of bug 21007; bugfix on 0.3.0.1-alpha.
1883 - Silence a BUG() warning when attempting to use a guard whose
1884 descriptor we don't know, and make this scenario less likely to
1885 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
1887 o Minor bugfixes (hidden service):
1888 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
1889 cells. Previously, we were using sizeof() on a pointer, instead of
1890 the real destination buffer. Fortunately, that value was only used
1891 to double-check that there was enough room--which was already
1892 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
1894 o Minor bugfixes (testing):
1895 - Fix Raspbian build issues related to missing socket errno in
1896 test_util.c. Fixes bug 21116; bugfix on tor-0.2.8.2. Patch
1898 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
1899 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
1900 - Use bash in src/test/test-network.sh. This ensures we reliably
1901 call chutney's newer tools/test-network.sh when available. Fixes
1902 bug 21562; bugfix on 0.2.9.1-alpha.
1905 - Small fixes to the fuzzing documentation. Closes ticket 21472.
1908 Changes in version 0.2.9.10 - 2017-03-01
1909 Tor 0.2.9.10 backports a security fix from later Tor release. It also
1910 includes fixes for some major issues affecting directory authorities,
1911 LibreSSL compatibility, and IPv6 correctness.
1913 The Tor 0.2.9.x release series is now marked as a long-term-support
1914 series. We intend to backport security fixes to 0.2.9.x until at
1915 least January of 2020.
1917 o Major bugfixes (directory authority, 0.3.0.3-alpha):
1918 - During voting, when marking a relay as a probable sybil, do not
1919 clear its BadExit flag: sybils can still be bad in other ways
1920 too. (We still clear the other flags.) Fixes bug 21108; bugfix
1923 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
1924 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
1925 any IPv6 addresses. Instead, only reject a port over IPv6 if the
1926 exit policy rejects that port on more than an IPv6 /16 of
1927 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
1928 which rejected a relay's own IPv6 address by default. Fixes bug
1929 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
1931 o Major bugfixes (parsing, also in 0.3.0.4-rc):
1932 - Fix an integer underflow bug when comparing malformed Tor
1933 versions. This bug could crash Tor when built with
1934 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1935 0.2.9.8, which were built with -ftrapv by default. In other cases
1936 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1937 on 0.0.8pre1. Found by OSS-Fuzz.
1939 o Minor features (directory authorities, also in 0.3.0.4-rc):
1940 - Directory authorities now reject descriptors that claim to be
1941 malformed versions of Tor. Helps prevent exploitation of
1943 - Reject version numbers with components that exceed INT32_MAX.
1944 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
1945 Fixes bug 21450; bugfix on 0.0.8pre1.
1947 o Minor features (geoip):
1948 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1951 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
1952 - Autoconf now checks to determine if OpenSSL structures are opaque,
1953 instead of explicitly checking for OpenSSL version numbers. Part
1955 - Support building with recent LibreSSL code that uses opaque
1956 structures. Closes ticket 21359.
1958 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
1959 - Repair a couple of (unreachable or harmless) cases of the risky
1960 comparison-by-subtraction pattern that caused bug 21278.
1962 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
1963 - The tor-resolve command line tool now rejects hostnames over 255
1964 characters in length. Previously, it would silently truncate them,
1965 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
1966 Patch by "junglefowl".
1969 Changes in version 0.3.0.3-alpha - 2017-02-03
1970 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
1971 0.3.0.x development series, including some that could cause
1972 authorities to behave badly. There is also a fix for a longstanding
1973 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
1974 includes some smaller features and bugfixes.
1976 The Tor 0.3.0.x release series is now in patch-freeze: no additional
1977 features will be considered for inclusion in 0.3.0.x. We suspect that
1978 some bugs will probably remain, however, and we encourage people to
1981 o Major bugfixes (directory authority):
1982 - During voting, when marking a relay as a probable sybil, do not
1983 clear its BadExit flag: sybils can still be bad in other ways
1984 too. (We still clear the other flags.) Fixes bug 21108; bugfix
1986 - When deciding whether we have just found a router to be reachable,
1987 do not penalize it for not having performed an Ed25519 link
1988 handshake if it does not claim to support an Ed25519 handshake.
1989 Previously, we would treat such relays as non-running. Fixes bug
1990 21107; bugfix on 0.3.0.1-alpha.
1992 o Major bugfixes (entry guards):
1993 - Stop trying to build circuits through entry guards for which we
1994 have no descriptor. Also, stop crashing in the case that we *do*
1995 accidentally try to build a circuit in such a state. Fixes bug
1996 21242; bugfix on 0.3.0.1-alpha.
1998 o Major bugfixes (IPv6 Exits):
1999 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
2000 any IPv6 addresses. Instead, only reject a port over IPv6 if the
2001 exit policy rejects that port on more than an IPv6 /16 of
2002 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
2003 which rejected a relay's own IPv6 address by default. Fixes bug
2004 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
2006 o Minor feature (client):
2007 - Enable IPv6 traffic on the SocksPort by default. To disable this,
2008 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
2010 o Minor feature (fallback scripts):
2011 - Add a check_existing mode to updateFallbackDirs.py, which checks
2012 if fallbacks in the hard-coded list are working. Closes ticket
2013 20174. Patch by haxxpop.
2015 o Minor features (ciphersuite selection):
2016 - Clients now advertise a list of ciphersuites closer to the ones
2017 preferred by Firefox. Closes part of ticket 15426.
2018 - Allow relays to accept a wider range of ciphersuites, including
2019 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
2021 o Minor features (controller, configuration):
2022 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
2023 and so on, now comes with a __*Port variant that will not be saved
2024 to the torrc file by the controller's SAVECONF command. This
2025 change allows TorBrowser to set up a single-use domain socket for
2026 each time it launches Tor. Closes ticket 20956.
2027 - The GETCONF command can now query options that may only be
2028 meaningful in context-sensitive lists. This allows the controller
2029 to query the mixed SocksPort/__SocksPort style options introduced
2030 in feature 20956. Implements ticket 21300.
2032 o Minor features (portability, compilation):
2033 - Autoconf now checks to determine if OpenSSL structures are opaque,
2034 instead of explicitly checking for OpenSSL version numbers. Part
2036 - Support building with recent LibreSSL code that uses opaque
2037 structures. Closes ticket 21359.
2039 o Minor features (relay):
2040 - We now allow separation of exit and relay traffic to different
2041 source IP addresses, using the OutboundBindAddressExit and
2042 OutboundBindAddressOR options respectively. Closes ticket 17975.
2043 Written by Michael Sonntag.
2045 o Minor bugfix (logging):
2046 - Don't recommend the use of Tor2web in non-anonymous mode.
2047 Recommending Tor2web is a bad idea because the client loses all
2048 anonymity. Tor2web should only be used in specific cases by users
2049 who *know* and understand the issues. Fixes bug 21294; bugfix
2052 o Minor bugfixes (client):
2053 - Always recover from failures in extend_info_from_node(), in an
2054 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
2055 bugfix on 0.2.3.1-alpha.
2057 o Minor bugfixes (client, entry guards):
2058 - Fix a bug warning (with backtrace) when we fail a channel that
2059 circuits to fallback directories on it. Fixes bug 21128; bugfix
2061 - Fix a spurious bug warning (with backtrace) when removing an
2062 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
2063 - Fix a bug of the new guard algorithm where tor could stall for up
2064 to 10 minutes before retrying a guard after a long period of no
2065 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
2066 - Do not try to build circuits until we have descriptors for our
2067 primary entry guards. Related to fix for bug 21242.
2069 o Minor bugfixes (configure, autoconf):
2070 - Rename the configure option --enable-expensive-hardening to
2071 --enable-fragile-hardening. Expensive hardening makes the tor
2072 daemon abort when some kinds of issues are detected. Thus, it
2073 makes tor more at risk of remote crashes but safer against RCE or
2074 heartbleed bug category. We now try to explain this issue in a
2075 message from the configure script. Fixes bug 21290; bugfix
2078 o Minor bugfixes (controller):
2079 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
2080 20824; bugfix on 0.3.0.1-alpha.
2082 o Minor bugfixes (hidden service):
2083 - Clean up the code for expiring intro points with no associated
2084 circuits. It was causing, rarely, a service with some expiring
2085 introduction points to not open enough additional introduction
2086 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
2087 - Stop setting the torrc option HiddenServiceStatistics to "0" just
2088 because we're not a bridge or relay. Instead, we preserve whatever
2089 value the user set (or didn't set). Fixes bug 21150; bugfix
2091 - Resolve two possible underflows which could lead to creating and
2092 closing a lot of introduction point circuits in a non-stop loop.
2093 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
2095 o Minor bugfixes (portability):
2096 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
2097 It is supported by OpenBSD itself, and also by most OpenBSD
2098 variants (such as Bitrig). Fixes bug 20980; bugfix
2100 - When mapping a file of length greater than SIZE_MAX, do not
2101 silently truncate its contents. This issue could occur on 32 bit
2102 systems with large file support and files which are larger than 4
2103 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
2105 o Minor bugfixes (tor-resolve):
2106 - The tor-resolve command line tool now rejects hostnames over 255
2107 characters in length. Previously, it would silently truncate them,
2108 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
2109 Patch by "junglefowl".
2111 o Minor bugfixes (Windows services):
2112 - Be sure to initialize the monotonic time subsystem before using
2113 it, even when running as an NT service. Fixes bug 21356; bugfix
2117 Changes in version 0.3.0.2-alpha - 2017-01-23
2118 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
2119 cause relays and clients to crash, even if they were not built with
2120 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
2121 versions, and also affects 0.3.0.1-alpha: all relays running an affected
2122 version should upgrade.
2124 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
2125 time-to-live values, makes directory authorities enforce the 1-to-1
2126 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
2127 client-side onion service reachability bug, does better at selecting
2128 the set of fallback directories, and more.
2130 o Major bugfixes (security, also in 0.2.9.9):
2131 - Downgrade the "-ftrapv" option from "always on" to "only on when
2132 --enable-expensive-hardening is provided." This hardening option, like
2133 others, can turn survivable bugs into crashes--and having it on by
2134 default made a (relatively harmless) integer overflow bug into a
2135 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
2138 o Major features (security):
2139 - Change the algorithm used to decide DNS TTLs on client and server
2140 side, to better resist DNS-based correlation attacks like the
2141 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
2142 Feamster. Now relays only return one of two possible DNS TTL
2143 values, and clients are willing to believe DNS TTL values up to 3
2144 hours long. Closes ticket 19769.
2146 o Major features (directory authority, security):
2147 - The default for AuthDirPinKeys is now 1: directory authorities
2148 will reject relays where the RSA identity key matches a previously
2149 seen value, but the Ed25519 key has changed. Closes ticket 18319.
2151 o Major bugfixes (client, guard, crash):
2152 - In circuit_get_global_origin_list(), return the actual list of
2153 origin circuits. The previous version of this code returned the
2154 list of all the circuits, and could have caused strange bugs,
2155 including possible crashes. Fixes bug 21118; bugfix
2158 o Major bugfixes (client, onion service, also in 0.2.9.9):
2159 - Fix a client-side onion service reachability bug, where multiple
2160 socks requests to an onion service (or a single slow request)
2161 could cause us to mistakenly mark some of the service's
2162 introduction points as failed, and we cache that failure so
2163 eventually we run out and can't reach the service. Also resolves a
2164 mysterious "Remote server sent bogus reason code 65021" log
2165 warning. The bug was introduced in ticket 17218, where we tried to
2166 remember the circuit end reason as a uint16_t, which mangled
2167 negative values. Partially fixes bug 21056 and fixes bug 20307;
2168 bugfix on 0.2.8.1-alpha.
2170 o Major bugfixes (DNS):
2171 - Fix a bug that prevented exit nodes from caching DNS records for
2172 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
2174 o Minor features (controller):
2175 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
2176 shared-random values to the controller. Closes ticket 19925.
2178 o Minor features (entry guards):
2179 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
2180 break regression tests.
2181 - Require UseEntryGuards when UseBridges is set, in order to make
2182 sure bridges aren't bypassed. Resolves ticket 20502.
2184 o Minor features (fallback directories):
2185 - Select 200 fallback directories for each release. Closes
2187 - Allow 3 fallback relays per operator, which is safe now that we
2188 are choosing 200 fallback relays. Closes ticket 20912.
2189 - Exclude relays affected by bug 20499 from the fallback list.
2190 Exclude relays from the fallback list if they are running versions
2191 known to be affected by bug 20499, or if in our tests they deliver
2192 a stale consensus (i.e. one that expired more than 24 hours ago).
2193 Closes ticket 20539.
2194 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
2196 - Require fallback directories to have the same address and port for
2197 7 days (now that we have enough relays with this stability).
2198 Relays whose OnionOO stability timer is reset on restart by bug
2199 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
2200 this issue. Closes ticket 20880; maintains short-term fix
2202 - Require fallbacks to have flags for 90% of the time (weighted
2203 decaying average), rather than 95%. This allows at least 73% of
2204 clients to bootstrap in the first 5 seconds without contacting an
2205 authority. Part of ticket 18828.
2206 - Annotate updateFallbackDirs.py with the bandwidth and consensus
2207 weight for each candidate fallback. Closes ticket 20878.
2208 - Make it easier to change the output sort order of fallbacks.
2209 Closes ticket 20822.
2210 - Display the relay fingerprint when downloading consensuses from
2211 fallbacks. Closes ticket 20908.
2213 o Minor features (geoip, also in 0.2.9.9):
2214 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
2217 o Minor features (next-gen onion service directories):
2218 - Remove the "EnableOnionServicesV3" consensus parameter that we
2219 introduced in 0.3.0.1-alpha: relays are now always willing to act
2220 as v3 onion service directories. Resolves ticket 19899.
2222 o Minor features (linting):
2223 - Enhance the changes file linter to warn on Tor versions that are
2224 prefixed with "tor-". Closes ticket 21096.
2226 o Minor features (logging):
2227 - In several places, describe unset ed25519 keys as "<unset>",
2228 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
2230 o Minor bugfix (control protocol):
2231 - The reply to a "GETINFO config/names" request via the control
2232 protocol now spells the type "Dependent" correctly. This is a
2233 breaking change in the control protocol. (The field seems to be
2234 ignored by the most common known controllers.) Fixes bug 18146;
2235 bugfix on 0.1.1.4-alpha.
2237 o Minor bugfixes (bug resilience):
2238 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
2239 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
2240 Hans Jerry Illikainen.
2242 o Minor bugfixes (build):
2243 - Replace obsolete Autoconf macros with their modern equivalent and
2244 prevent similar issues in the future. Fixes bug 20990; bugfix
2247 o Minor bugfixes (client, guards):
2248 - Fix bug where Tor would think that there are circuits waiting for
2249 better guards even though those circuits have been freed. Fixes
2250 bug 21142; bugfix on 0.3.0.1-alpha.
2252 o Minor bugfixes (config):
2253 - Don't assert on startup when trying to get the options list and
2254 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
2255 options so of course they aren't ready yet. Fixes bug 21062;
2256 bugfix on 0.2.9.3-alpha.
2258 o Minor bugfixes (controller):
2259 - Make the GETINFO interface for inquiring about entry guards
2260 support the new guards backend. Fixes bug 20823; bugfix
2263 o Minor bugfixes (dead code):
2264 - Remove a redundant check for PidFile changes at runtime in
2265 options_transition_allowed(): this check is already performed
2266 regardless of whether the sandbox is active. Fixes bug 21123;
2267 bugfix on 0.2.5.4-alpha.
2269 o Minor bugfixes (documentation):
2270 - Update the tor manual page to document every option that can not
2271 be changed while tor is running. Fixes bug 21122.
2273 o Minor bugfixes (fallback directories):
2274 - Stop failing when a relay has no uptime data in
2275 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
2276 - Avoid checking fallback candidates' DirPorts if they are down in
2277 OnionOO. When a relay operator has multiple relays, this
2278 prioritizes relays that are up over relays that are down. Fixes
2279 bug 20926; bugfix on 0.2.8.3-alpha.
2280 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
2281 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
2283 o Minor bugfixes (guards, bootstrapping):
2284 - When connecting to a directory guard during bootstrap, do not mark
2285 the guard as successful until we receive a good-looking directory
2286 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
2288 o Minor bugfixes (onion services):
2289 - Fix the config reload pruning of old vs new services so it
2290 actually works when both ephemeral and non-ephemeral services are
2291 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
2292 - Allow the number of introduction points to be as low as 0, rather
2293 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
2295 o Minor bugfixes (IPv6):
2296 - Make IPv6-using clients try harder to find an IPv6 directory
2297 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
2298 - When IPv6 addresses have not been downloaded yet (microdesc
2299 consensus documents don't list relay IPv6 addresses), use hard-
2300 coded addresses for authorities, fallbacks, and configured
2301 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
2302 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
2304 o Minor bugfixes (memory leaks):
2305 - Fix a memory leak when configuring hidden services. Fixes bug
2306 20987; bugfix on 0.3.0.1-alpha.
2308 o Minor bugfixes (portability, also in 0.2.9.9):
2309 - Avoid crashing when Tor is built using headers that contain
2310 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
2311 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
2313 - Fix Libevent detection on platforms without Libevent 1 headers
2314 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
2316 o Minor bugfixes (relay):
2317 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
2318 initializing the keys would reset the DataDirectory to 0700
2319 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
2320 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
2322 o Minor bugfixes (testing):
2323 - Remove undefined behavior from the backtrace generator by removing
2324 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
2326 o Minor bugfixes (unit tests):
2327 - Allow the unit tests to pass even when DNS lookups of bogus
2328 addresses do not fail as expected. Fixes bug 20862 and 20863;
2329 bugfix on unit tests introduced in 0.2.8.1-alpha
2330 through 0.2.9.4-alpha.
2332 o Code simplification and refactoring:
2333 - Refactor code to manipulate global_origin_circuit_list into
2334 separate functions. Closes ticket 20921.
2336 o Documentation (formatting):
2337 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
2338 blocks were incorrectly appearing. Closes ticket 20885.
2340 o Documentation (man page):
2341 - Clarify many options in tor.1 and add some min/max values for
2342 HiddenService options. Closes ticket 21058.
2345 Changes in version 0.2.9.9 - 2017-01-23
2346 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
2347 cause relays and clients to crash, even if they were not built with
2348 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
2349 versions, and also affects 0.3.0.1-alpha: all relays running an affected
2350 version should upgrade.
2352 This release also resolves a client-side onion service reachability
2353 bug, and resolves a pair of small portability issues.
2355 o Major bugfixes (security):
2356 - Downgrade the "-ftrapv" option from "always on" to "only on when
2357 --enable-expensive-hardening is provided." This hardening option,
2358 like others, can turn survivable bugs into crashes -- and having
2359 it on by default made a (relatively harmless) integer overflow bug
2360 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
2361 bugfix on 0.2.9.1-alpha.
2363 o Major bugfixes (client, onion service):
2364 - Fix a client-side onion service reachability bug, where multiple
2365 socks requests to an onion service (or a single slow request)
2366 could cause us to mistakenly mark some of the service's
2367 introduction points as failed, and we cache that failure so
2368 eventually we run out and can't reach the service. Also resolves a
2369 mysterious "Remote server sent bogus reason code 65021" log
2370 warning. The bug was introduced in ticket 17218, where we tried to
2371 remember the circuit end reason as a uint16_t, which mangled
2372 negative values. Partially fixes bug 21056 and fixes bug 20307;
2373 bugfix on 0.2.8.1-alpha.
2375 o Minor features (geoip):
2376 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
2379 o Minor bugfixes (portability):
2380 - Avoid crashing when Tor is built using headers that contain
2381 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
2382 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
2384 - Fix Libevent detection on platforms without Libevent 1 headers
2385 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
2388 Changes in version 0.3.0.1-alpha - 2016-12-19
2389 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
2390 series. It strengthens Tor's link and circuit handshakes by
2391 identifying relays by their Ed25519 keys, improves the algorithm that
2392 clients use to choose and maintain their list of guards, and includes
2393 additional backend support for the next-generation hidden service
2394 design. It also contains numerous other small features and
2395 improvements to security, correctness, and performance.
2397 Below are the changes since 0.2.9.8.
2399 o Major features (guard selection algorithm):
2400 - Tor's guard selection algorithm has been redesigned from the
2401 ground up, to better support unreliable networks and restrictive
2402 sets of entry nodes, and to better resist guard-capture attacks by
2403 hostile local networks. Implements proposal 271; closes
2406 o Major features (next-generation hidden services):
2407 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
2408 prop224 aka "Next Generation Hidden Services". Service and clients
2409 don't use this functionality yet. Closes ticket 19043. Based on
2410 initial code by Alec Heifetz.
2411 - Relays now support the HSDir version 3 protocol, so that they can
2412 can store and serve v3 descriptors. This is part of the next-
2413 generation onion service work detailled in proposal 224. Closes
2416 o Major features (protocol, ed25519 identity keys):
2417 - Relays now use Ed25519 to prove their Ed25519 identities and to
2418 one another, and to clients. This algorithm is faster and more
2419 secure than the RSA-based handshake we've been doing until now.
2420 Implements the second big part of proposal 220; Closes
2422 - Clients now support including Ed25519 identity keys in the EXTEND2
2423 cells they generate. By default, this is controlled by a consensus
2424 parameter, currently disabled. You can turn this feature on for
2425 testing by setting ExtendByEd25519ID in your configuration. This
2426 might make your traffic appear different than the traffic
2427 generated by other users, however. Implements part of ticket
2428 15056; part of proposal 220.
2429 - Relays now understand requests to extend to other relays by their
2430 Ed25519 identity keys. When an Ed25519 identity key is included in
2431 an EXTEND2 cell, the relay will only extend the circuit if the
2432 other relay can prove ownership of that identity. Implements part
2433 of ticket 15056; part of proposal 220.
2435 o Major bugfixes (scheduler):
2436 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
2437 caused the channel scheduler to behave more or less randomly,
2438 rather than preferring channels with higher-priority circuits.
2439 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
2441 o Minor features (controller):
2442 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
2443 rather than "unrecognized." Closes ticket 20389; patch from
2446 o Minor features (diagnostic, directory client):
2447 - Warn when we find an unexpected inconsistency in directory
2448 download status objects. Prevents some negative consequences of
2451 o Minor features (directory authority):
2452 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
2453 default) to control whether authorities should try to probe relays
2454 by their Ed25519 link keys. This option will go away in a few
2455 releases--unless we encounter major trouble in our ed25519 link
2456 protocol rollout, in which case it will serve as a safety option.
2458 o Minor features (directory cache):
2459 - Relays and bridges will now refuse to serve the consensus they
2460 have if they know it is too old for a client to use. Closes
2463 o Minor features (ed25519 link handshake):
2464 - Advertise support for the ed25519 link handshake using the
2465 subprotocol-versions mechanism, so that clients can tell which
2466 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
2468 o Minor features (fingerprinting resistance, authentication):
2469 - Extend the length of RSA keys used for TLS link authentication to
2470 2048 bits. (These weren't used for forward secrecy; for forward
2471 secrecy, we used P256.) Closes ticket 13752.
2473 o Minor features (infrastructure):
2474 - Implement smartlist_add_strdup() function. Replaces the use of
2475 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
2477 o Minor bugfixes (client):
2478 - When clients that use bridges start up with a cached consensus on
2479 disk, they were ignoring it and downloading a new one. Now they
2480 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
2482 o Minor bugfixes (configuration):
2483 - Accept non-space whitespace characters after the severity level in
2484 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
2485 - Support "TByte" and "TBytes" units in options given in bytes.
2486 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
2487 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
2489 o Minor bugfixes (consensus weight):
2490 - Add new consensus method that initializes bw weights to 1 instead
2491 of 0. This prevents a zero weight from making it all the way to
2492 the end (happens in small testing networks) and causing an error.
2493 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
2495 o Minor bugfixes (descriptors):
2496 - Correctly recognise downloaded full descriptors as valid, even
2497 when using microdescriptors as circuits. This affects clients with
2498 FetchUselessDescriptors set, and may affect directory authorities.
2499 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
2501 o Minor bugfixes (directory system):
2502 - Download all consensus flavors, descriptors, and authority
2503 certificates when FetchUselessDescriptors is set, regardless of
2504 whether tor is a directory cache or not. Fixes bug 20667; bugfix
2505 on all recent tor versions.
2506 - Bridges and relays now use microdescriptors (like clients do)
2507 rather than old-style router descriptors. Now bridges will blend
2508 in with clients in terms of the circuits they build. Fixes bug
2509 6769; bugfix on 0.2.3.2-alpha.
2511 o Minor bugfixes (ed25519 certificates):
2512 - Correctly interpret ed25519 certificates that would expire some
2513 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
2515 o Minor bugfixes (hidden services):
2516 - Stop ignoring misconfigured hidden services. Instead, refuse to
2517 start tor until the misconfigurations have been corrected. Fixes
2518 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
2521 o Minor bugfixes (memory leak at exit):
2522 - Fix a small harmless memory leak at exit of the previously unused
2523 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
2526 o Minor bugfixes (util):
2527 - When finishing writing a file to disk, if we were about to replace
2528 the file with the temporary file created before and we fail to
2529 replace it, remove the temporary file so it doesn't stay on disk.
2530 Fixes bug 20646; bugfix on tor-0.2.0.7-alpha. Patch by fk.
2532 o Minor bugfixes (Windows):
2533 - Check for getpagesize before using it to mmap files. This fixes
2534 compilation in some MinGW environments. Fixes bug 20530; bugfix on
2535 0.1.2.1-alpha. Reported by "ice".
2537 o Code simplification and refactoring:
2538 - Abolish all global guard context in entrynodes.c; replace with new
2539 guard_selection_t structure as preparation for proposal 271.
2540 Closes ticket 19858.
2541 - Introduce rend_service_is_ephemeral() that tells if given onion
2542 service is ephemeral. Replace unclear NULL-checkings for service
2543 directory with this function. Closes ticket 20526.
2544 - Extract magic numbers in circuituse.c into defined variables.
2545 - Refactor circuit_is_available_for_use to remove unnecessary check.
2546 - Refactor circuit_predict_and_launch_new for readability and
2547 testability. Closes ticket 18873.
2548 - Refactor large if statement in purpose_needs_anonymity to use
2549 switch statement instead. Closes part of ticket 20077.
2550 - Refactor the hashing API to return negative values for errors, as
2551 is done as throughout the codebase. Closes ticket 20717.
2552 - Remove data structures that were used to index or_connection
2553 objects by their RSA identity digests. These structures are fully
2554 redundant with the similar structures used in the
2555 channel abstraction.
2556 - Remove duplicate code in the channel_write_*cell() functions.
2557 Closes ticket 13827; patch from Pingl.
2558 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
2559 use only purpose_needs_anonymity. Closes part of ticket 20077.
2560 - The code to generate and parse EXTEND and EXTEND2 cells has been
2561 replaced with code automatically generated by the
2565 - Include the "TBits" unit in Tor's man page. Fixes part of bug
2566 20622; bugfix on tor-0.2.5.1-alpha.
2567 - Change '1' to 'weight_scale' in consensus bw weights calculation
2568 comments, as that is reality. Closes ticket 20273. Patch
2570 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
2571 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
2572 on tor-0.2.5.6-alpha.
2573 - Stop the man page from incorrectly stating that HiddenServiceDir
2574 must already exist. Fixes 20486.
2575 - Clarify that when ClientRejectInternalAddresses is enabled (which
2576 is the default), multicast DNS hostnames for machines on the local
2577 network (of the form *.local) are also rejected. Closes
2581 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
2582 limit for relays running on a single IP applies to authority IP
2583 addresses as well as to non-authority IP addresses. Closes
2585 - The UseDirectoryGuards torrc option no longer exists: all users
2586 that use entry guards will also use directory guards. Related to
2587 proposal 271; implements part of ticket 20831.
2590 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
2591 from "overcaffeinated".
2592 - Perform the coding style checks when running the tests and fail
2593 when coding style violations are found. Closes ticket 5500.
2594 - Add tests for networkstatus_compute_bw_weights_v10.
2595 - Add unit tests circuit_predict_and_launch_new.
2596 - Extract dummy_origin_circuit_new so it can be used by other
2600 Changes in version 0.2.8.12 - 2016-12-19
2601 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
2602 below) where Tor clients could crash when attempting to visit a
2603 hostile hidden service. Clients are recommended to upgrade as packages
2604 become available for their systems.
2606 It also includes an updated list of fallback directories, backported
2609 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
2610 backported to 0.2.8 in the future.
2612 o Major bugfixes (parsing, security, backported from 0.2.9.8):
2613 - Fix a bug in parsing that could cause clients to read a single
2614 byte past the end of an allocated region. This bug could be used
2615 to cause hardened clients (built with --enable-expensive-hardening)
2616 to crash if they tried to visit a hostile hidden service. Non-
2617 hardened clients are only affected depending on the details of
2618 their platform's memory allocator. Fixes bug 21018; bugfix on
2619 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
2620 2016-12-002 and as CVE-2016-1254.
2622 o Minor features (fallback directory list, backported from 0.2.9.8):
2623 - Replace the 81 remaining fallbacks of the 100 originally
2624 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
2625 fallbacks (123 new, 54 existing, 27 removed) generated in December
2626 2016. Resolves ticket 20170.
2628 o Minor features (geoip, backported from 0.2.9.7-rc):
2629 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
2633 Changes in version 0.2.9.8 - 2016-12-19
2634 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
2636 The Tor 0.2.9 series makes mandatory a number of security features
2637 that were formerly optional. It includes support for a new shared-
2638 randomness protocol that will form the basis for next generation
2639 hidden services, includes a single-hop hidden service mode for
2640 optimizing .onion services that don't actually want to be hidden,
2641 tries harder not to overload the directory authorities with excessive
2642 downloads, and supports a better protocol versioning scheme for
2643 improved compatibility with other implementations of the Tor protocol.
2645 And of course, there are numerous other bugfixes and improvements.
2647 This release also includes a fix for a medium-severity issue (bug
2648 21018 below) where Tor clients could crash when attempting to visit a
2649 hostile hidden service. Clients are recommended to upgrade as packages
2650 become available for their systems.
2652 Below are the changes since 0.2.9.7-rc. For a list of all changes
2653 since 0.2.8, see the ReleaseNotes file.
2655 o Major bugfixes (parsing, security):
2656 - Fix a bug in parsing that could cause clients to read a single
2657 byte past the end of an allocated region. This bug could be used
2658 to cause hardened clients (built with --enable-expensive-hardening)
2659 to crash if they tried to visit a hostile hidden service. Non-
2660 hardened clients are only affected depending on the details of
2661 their platform's memory allocator. Fixes bug 21018; bugfix on
2662 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
2663 2016-12-002 and as CVE-2016-1254.
2665 o Minor features (fallback directory list):
2666 - Replace the 81 remaining fallbacks of the 100 originally
2667 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
2668 fallbacks (123 new, 54 existing, 27 removed) generated in December
2669 2016. Resolves ticket 20170.
2672 Changes in version 0.2.9.7-rc - 2016-12-12
2673 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
2674 including a few that had prevented tests from passing on
2677 o Minor features (geoip):
2678 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
2681 o Minor bugfix (build):
2682 - The current Git revision when building from a local repository is
2683 now detected correctly when using git worktrees. Fixes bug 20492;
2684 bugfix on 0.2.3.9-alpha.
2686 o Minor bugfixes (directory authority):
2687 - When computing old Tor protocol line version in protover, we were
2688 looking at 0.2.7.5 twice instead of a specific case for
2689 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
2691 o Minor bugfixes (download scheduling):
2692 - Resolve a "bug" warning when considering a download schedule whose
2693 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
2695 o Minor bugfixes (logging):
2696 - Downgrade a harmless log message about the
2697 pending_entry_connections list from "warn" to "info". Mitigates
2700 o Minor bugfixes (memory leak):
2701 - Fix a small memory leak when receiving AF_UNIX connections on a
2702 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
2703 - When moving a signed descriptor object from a source to an
2704 existing destination, free the allocated memory inside that
2705 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
2707 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
2708 - Fix a memory leak and use-after-free error when removing entries
2709 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
2710 0.2.5.5-alpha. Patch from "cypherpunks".
2712 o Minor bugfixes (portability):
2713 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
2714 Fixes bug 20935; bugfix on 0.2.9.6-rc.
2716 o Minor bugfixes (unit tests):
2717 - Stop expecting NetBSD unit tests to report success for ipfw. Part
2718 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
2719 - Fix tolerances in unit tests for monotonic time comparisons
2720 between nanoseconds and microseconds. Previously, we accepted a 10
2721 us difference only, which is not realistic on every platform's
2722 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
2723 - Remove a double-free in the single onion service unit test. Stop
2724 ignoring a return value. Make future changes less error-prone.
2725 Fixes bug 20864; bugfix on 0.2.9.6-rc.
2728 Changes in version 0.2.8.11 - 2016-12-08
2729 Tor 0.2.8.11 backports fixes for additional portability issues that
2730 could prevent Tor from building correctly on OSX Sierra, or with
2731 OpenSSL 1.1. Affected users should upgrade; others can safely stay
2734 o Minor bugfixes (portability):
2735 - Avoid compilation errors when building on OSX Sierra. Sierra began
2736 to support the getentropy() and clock_gettime() APIs, but created
2737 a few problems in doing so. Tor 0.2.9 has a more thorough set of
2738 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
2739 monotonic time interfaces. Fixes bug 20865. Bugfix
2742 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
2743 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
2744 architectures. Closes ticket 20588.
2747 Changes in version 0.2.8.10 - 2016-12-02
2748 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
2749 unusable after they left standby mode. It also backports fixes for
2750 a few portability issues and a small but problematic memory leak.
2752 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
2753 - When Tor leaves standby because of a new application request, open
2754 circuits as needed to serve that request. Previously, we would
2755 potentially wait a very long time. Fixes part of bug 19969; bugfix
2758 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
2759 - Clients now respond to new application stream requests immediately
2760 when they arrive, rather than waiting up to one second before
2761 starting to handle them. Fixes part of bug 19969; bugfix
2764 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
2765 - Work around a bug in the OSX 10.12 SDK that would prevent us from
2766 successfully targeting earlier versions of OSX. Resolves
2769 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
2770 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
2771 20551; bugfix on 0.2.1.1-alpha.
2773 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
2774 - Work around a memory leak in OpenSSL 1.1 when encoding public
2775 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
2777 o Minor features (geoip):
2778 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
2781 Changes in version 0.2.9.6-rc - 2016-12-02
2782 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
2783 version. We hope that it will be ready to become stable soon, and we
2784 encourage everyone to test this release. If no showstopper bugs are
2785 found here, the next 0.2.9 release will be stable.
2787 o Major bugfixes (relay, resolver, logging):
2788 - For relays that don't know their own address, avoid attempting a
2789 local hostname resolve for each descriptor we download. This
2790 will cut down on the number of "Success: chose address 'x.x.x.x'"
2791 log lines, and also avoid confusing clock jumps if the resolver
2792 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
2794 o Minor bugfixes (client, fascistfirewall):
2795 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
2796 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
2798 o Minor bugfixes (hidden services):
2799 - Stop ignoring the anonymity status of saved keys for hidden
2800 services and single onion services when first starting tor.
2801 Instead, refuse to start tor if any hidden service key has been
2802 used in a different hidden service anonymity mode. Fixes bug
2803 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
2805 o Minor bugfixes (portability):
2806 - Work around a bug in the OSX 10.12 SDK that would prevent us from
2807 successfully targeting earlier versions of OSX. Resolves
2809 - Run correctly when built on Windows build environments that
2810 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
2812 o Minor bugfixes (single onion services, Tor2web):
2813 - Stop complaining about long-term one-hop circuits deliberately
2814 created by single onion services and Tor2web. These log messages
2815 are intended to diagnose issue 8387, which relates to circuits
2816 hanging around forever for no reason. Fixes bug 20613; bugfix on
2817 0.2.9.1-alpha. Reported by "pastly".
2819 o Minor bugfixes (unit tests):
2820 - Stop spurious failures in the local interface address discovery
2821 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
2825 - Correct the minimum bandwidth value in torrc.sample, and queue a
2826 corresponding change for torrc.minimal. Closes ticket 20085.
2829 Changes in version 0.2.9.5-alpha - 2016-11-08
2830 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
2831 version. We believe one or two probably remain, and we encourage
2832 everyone to test this release.
2834 o Major bugfixes (client performance):
2835 - Clients now respond to new application stream requests immediately
2836 when they arrive, rather than waiting up to one second before
2837 starting to handle them. Fixes part of bug 19969; bugfix
2840 o Major bugfixes (client reliability):
2841 - When Tor leaves standby because of a new application request, open
2842 circuits as needed to serve that request. Previously, we would
2843 potentially wait a very long time. Fixes part of bug 19969; bugfix
2846 o Major bugfixes (download scheduling):
2847 - When using an exponential backoff schedule, do not give up on
2848 downloading just because we have failed a bunch of times. Since
2849 each delay is longer than the last, retrying indefinitely won't
2850 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
2851 - If a consensus expires while we are waiting for certificates to
2852 download, stop waiting for certificates.
2853 - If we stop waiting for certificates less than a minute after we
2854 started downloading them, do not consider the certificate download
2855 failure a separate failure. Fixes bug 20533; bugfix
2857 - Remove the maximum delay on exponential-backoff scheduling. Since
2858 we now allow an infinite number of failures (see ticket 20536), we
2859 must now allow the time to grow longer on each failure. Fixes part
2860 of bug 20534; bugfix on 0.2.9.1-alpha.
2861 - Make our initial download delays closer to those from 0.2.8. Fixes
2862 another part of bug 20534; bugfix on 0.2.9.1-alpha.
2863 - When determining when to download a directory object, handle times
2864 after 2038 if the operating system supports them. (Someday this
2865 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
2866 - When using exponential backoff in test networks, use a lower
2867 exponent, so the delays do not vary as much. This helps test
2868 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
2870 o Minor features (geoip):
2871 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
2874 o Minor bugfixes (client directory scheduling):
2875 - Treat "relay too busy to answer request" as a failed request and a
2876 reason to back off on our retry frequency. This is safe now that
2877 exponential backoffs retry indefinitely, and avoids a bug where we
2878 would reset our download schedule erroneously. Fixes bug 20593;
2879 bugfix on 0.2.9.1-alpha.
2881 o Minor bugfixes (client, logging):
2882 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
2883 assume all nodes support EXTEND2. Use ntor whenever a key is
2884 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
2885 - On DNSPort, stop logging a BUG warning on a failed hostname
2886 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
2888 o Minor bugfixes (hidden services):
2889 - When configuring hidden services, check every hidden service
2890 directory's permissions. Previously, we only checked the last
2891 hidden service. Fixes bug 20529; bugfix the work to fix 13942
2894 o Minor bugfixes (portability):
2895 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
2896 architectures. Closes ticket 20588.
2897 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
2898 removed the ECDH ciphers which caused the tests to fail on
2899 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
2900 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
2901 20551; bugfix on 0.2.1.1-alpha.
2903 o Minor bugfixes (relay bootstrap):
2904 - Ensure relays don't make multiple connections during bootstrap.
2905 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
2907 o Minor bugfixes (relay):
2908 - Work around a memory leak in OpenSSL 1.1 when encoding public
2909 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
2910 - Avoid a small memory leak when informing worker threads about
2911 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
2912 - Do not try to parallelize workers more than 16x without the user
2913 explicitly configuring us to do so, even if we do detect more than
2914 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
2916 o Minor bugfixes (single onion services):
2917 - Start correctly when creating a single onion service in a
2918 directory that did not previously exist. Fixes bug 20484; bugfix
2921 o Minor bugfixes (testing):
2922 - Avoid a unit test failure on systems with over 16 detectable CPU
2923 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
2926 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
2927 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
2928 - Module-level documentation for several more modules. Closes
2929 tickets 19287 and 19290.
2932 Changes in version 0.2.8.9 - 2016-10-17
2933 Tor 0.2.8.9 backports a fix for a security hole in previous versions
2934 of Tor that would allow a remote attacker to crash a Tor client,
2935 hidden service, relay, or authority. All Tor users should upgrade to
2936 this version, or to 0.2.9.4-alpha. Patches will be released for older
2939 o Major features (security fixes, also in 0.2.9.4-alpha):
2940 - Prevent a class of security bugs caused by treating the contents
2941 of a buffer chunk as if they were a NUL-terminated string. At
2942 least one such bug seems to be present in all currently used
2943 versions of Tor, and would allow an attacker to remotely crash
2944 most Tor instances, especially those compiled with extra compiler
2945 hardening. With this defense in place, such bugs can't crash Tor,
2946 though we should still fix them as they occur. Closes ticket
2947 20384 (TROVE-2016-10-001).
2949 o Minor features (geoip):
2950 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
2954 Changes in version 0.2.9.4-alpha - 2016-10-17
2955 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
2956 that would allow a remote attacker to crash a Tor client, hidden
2957 service, relay, or authority. All Tor users should upgrade to this
2958 version, or to 0.2.8.9. Patches will be released for older versions
2961 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
2962 previous versions of Tor, including the implementation of a feature to
2963 future- proof the Tor ecosystem against protocol changes, some bug
2964 fixes necessary for Tor Browser to use unix domain sockets correctly,
2965 and several portability improvements. We anticipate that this will be
2966 the last alpha in the Tor 0.2.9 series, and that the next release will
2967 be a release candidate.
2969 o Major features (security fixes):
2970 - Prevent a class of security bugs caused by treating the contents
2971 of a buffer chunk as if they were a NUL-terminated string. At
2972 least one such bug seems to be present in all currently used
2973 versions of Tor, and would allow an attacker to remotely crash
2974 most Tor instances, especially those compiled with extra compiler
2975 hardening. With this defense in place, such bugs can't crash Tor,
2976 though we should still fix them as they occur. Closes ticket
2977 20384 (TROVE-2016-10-001).
2979 o Major features (subprotocol versions):
2980 - Tor directory authorities now vote on a set of recommended
2981 subprotocol versions, and on a set of required subprotocol
2982 versions. Clients and relays that lack support for a _required_
2983 subprotocol version will not start; those that lack support for a
2984 _recommended_ subprotocol version will warn the user to upgrade.
2985 Closes ticket 19958; implements part of proposal 264.
2986 - Tor now uses "subprotocol versions" to indicate compatibility.
2987 Previously, versions of Tor looked at the declared Tor version of
2988 a relay to tell whether they could use a given feature. Now, they
2989 should be able to rely on its declared subprotocol versions. This
2990 change allows compatible implementations of the Tor protocol(s) to
2991 exist without pretending to be 100% bug-compatible with particular
2992 releases of Tor itself. Closes ticket 19958; implements part of
2995 o Minor feature (fallback directories):
2996 - Remove broken fallbacks from the hard-coded fallback directory
2997 list. Closes ticket 20190; patch by teor.
2999 o Minor features (client, directory):
3000 - Since authorities now omit all routers that lack the Running and
3001 Valid flags, we assume that any relay listed in the consensus must
3002 have those flags. Closes ticket 20001; implements part of
3005 o Minor features (compilation, portability):
3006 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
3009 o Minor features (development tools, etags):
3010 - Teach the "make tags" Makefile target how to correctly find
3011 "MOCK_IMPL" function definitions. Patch from nherring; closes
3014 o Minor features (geoip):
3015 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
3018 o Minor features (unix domain sockets):
3019 - When configuring a unix domain socket for a SocksPort,
3020 ControlPort, or Hidden service, you can now wrap the address in
3021 quotes, using C-style escapes inside the quotes. This allows unix
3022 domain socket paths to contain spaces.
3024 o Minor features (virtual addresses):
3025 - Increase the maximum number of bits for the IPv6 virtual network
3026 prefix from 16 to 104. In this way, the condition for address
3027 allocation is less restrictive. Closes ticket 20151; feature
3030 o Minor bugfixes (address discovery):
3031 - Stop reordering IP addresses returned by the OS. This makes it
3032 more likely that Tor will guess the same relay IP address every
3033 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
3034 Reported by René Mayrhofer, patch by "cypherpunks".
3036 o Minor bugfixes (client, unix domain sockets):
3037 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
3038 the client address is meaningless. Fixes bug 20261; bugfix
3041 o Minor bugfixes (compilation, OpenBSD):
3042 - Detect Libevent2 functions correctly on systems that provide
3043 libevent2, but where libevent1 is linked with -levent. Fixes bug
3044 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
3046 o Minor bugfixes (configuration):
3047 - When parsing quoted configuration values from the torrc file,
3048 handle windows line endings correctly. Fixes bug 19167; bugfix on
3049 0.2.0.16-alpha. Patch from "Pingl".
3051 o Minor bugfixes (getpass):
3052 - Defensively fix a non-triggerable heap corruption at do_getpass()
3053 to protect ourselves from mistakes in the future. Fixes bug
3054 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
3057 o Minor bugfixes (hidden service):
3058 - Allow hidden services to run on IPv6 addresses even when the
3059 IPv6Exit option is not set. Fixes bug 18357; bugfix
3063 - Add module-level internal documentation for 36 C files that
3064 previously didn't have a high-level overview. Closes ticket #20385.
3066 o Required libraries:
3067 - When building with OpenSSL, Tor now requires version 1.0.1 or
3068 later. OpenSSL 1.0.0 and earlier are no longer supported by the
3069 OpenSSL team, and should not be used. Closes ticket 20303.
3072 Changes in version 0.2.9.3-alpha - 2016-09-23
3073 Tor 0.2.9.3-alpha adds improved support for entities that want to make
3074 high-performance services available through the Tor .onion mechanism
3075 without themselves receiving anonymity as they host those services. It
3076 also tries harder to ensure that all steps on a circuit are using the
3077 strongest crypto possible, strengthens some TLS properties, and
3078 resolves several bugs -- including a pair of crash bugs from the 0.2.8
3079 series. Anybody running an earlier version of 0.2.9.x should upgrade.
3081 o Major bugfixes (crash, also in 0.2.8.8):
3082 - Fix a complicated crash bug that could affect Tor clients
3083 configured to use bridges when replacing a networkstatus consensus
3084 in which one of their bridges was mentioned. OpenBSD users saw
3085 more crashes here, but all platforms were potentially affected.
3086 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
3088 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
3089 - Fix a timing-dependent assertion failure that could occur when we
3090 tried to flush from a circuit after having freed its cells because
3091 of an out-of-memory condition. Fixes bug 20203; bugfix on
3092 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
3095 o Major features (circuit building, security):
3096 - Authorities, relays and clients now require ntor keys in all
3097 descriptors, for all hops (except for rare hidden service protocol
3098 cases), for all circuits, and for all other roles. Part of
3100 - Tor authorities, relays, and clients only use ntor, except for
3101 rare cases in the hidden service protocol. Part of ticket 19163.
3103 o Major features (single-hop "hidden" services):
3104 - Add experimental HiddenServiceSingleHopMode and
3105 HiddenServiceNonAnonymousMode options. When both are set to 1,
3106 every hidden service on a Tor instance becomes a non-anonymous
3107 Single Onion Service. Single Onions make one-hop (direct)
3108 connections to their introduction and renzedvous points. One-hop
3109 circuits make Single Onion servers easily locatable, but clients
3110 remain location-anonymous. This is compatible with the existing
3111 hidden service implementation, and works on the current tor
3112 network without any changes to older relays or clients. Implements
3113 proposal 260, completes ticket 17178. Patch by teor and asn.
3115 o Major features (resource management):
3116 - Tor can now notice it is about to run out of sockets, and
3117 preemptively close connections of lower priority. (This feature is
3118 off by default for now, since the current prioritizing method is
3119 yet not mature enough. You can enable it by setting
3120 "DisableOOSCheck 0", but watch out: it might close some sockets
3121 you would rather have it keep.) Closes ticket 18640.
3123 o Major bugfixes (circuit building):
3124 - Hidden service client-to-intro-point and service-to-rendezvous-
3125 point circuits use the TAP key supplied by the protocol, to avoid
3126 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
3128 o Major bugfixes (compilation, OpenBSD):
3129 - Fix a Libevent-detection bug in our autoconf script that would
3130 prevent Tor from linking successfully on OpenBSD. Patch from
3131 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
3133 o Major bugfixes (hidden services):
3134 - Clients now require hidden services to include the TAP keys for
3135 their intro points in the hidden service descriptor. This prevents
3136 an inadvertent upgrade to ntor, which a malicious hidden service
3137 could use to distinguish clients by consensus version. Fixes bug
3138 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
3140 o Minor features (security, TLS):
3141 - Servers no longer support clients that without AES ciphersuites.
3142 (3DES is no longer considered an acceptable cipher.) We believe
3143 that no such Tor clients currently exist, since Tor has required
3144 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
3146 o Minor feature (fallback directories):
3147 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
3148 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
3149 2016. Closes ticket 20190; patch by teor.
3151 o Minor features (geoip, also in 0.2.8.8):
3152 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
3155 o Minor feature (port flags):
3156 - Add new flags to the *Port options to finer control over which
3157 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
3158 and the synthetic flag OnionTrafficOnly, which is equivalent to
3159 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
3160 18693; patch by "teor".
3162 o Minor features (directory authority):
3163 - After voting, if the authorities decide that a relay is not
3164 "Valid", they no longer include it in the consensus at all. Closes
3165 ticket 20002; implements part of proposal 272.
3167 o Minor features (testing):
3168 - Disable memory protections on OpenBSD when performing our unit
3169 tests for memwipe(). The test deliberately invokes undefined
3170 behavior, and the OpenBSD protections interfere with this. Patch
3171 from "rubiate". Closes ticket 20066.
3173 o Minor features (testing, ipv6):
3174 - Add the single-onion and single-onion-ipv6 chutney targets to
3175 "make test-network-all". This requires a recent chutney version
3176 with the single onion network flavours (git c72a652 or later).
3177 Closes ticket 20072; patch by teor.
3178 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
3179 tests. Remove bridges+hs, as it's somewhat redundant. This
3180 requires a recent chutney version that supports IPv6 clients,
3181 relays, and authorities. Closes ticket 20069; patch by teor.
3183 o Minor features (Tor2web):
3184 - Make Tor2web clients respect ReachableAddresses. This feature was
3185 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
3186 0.2.8.7. Implements feature 20034. Patch by teor.
3188 o Minor features (unit tests):
3189 - We've done significant work to make the unit tests run faster.
3190 - Our link-handshake unit tests now check that when invalid
3191 handshakes fail, they fail with the error messages we expected.
3192 - Our unit testing code that captures log messages no longer
3193 prevents them from being written out if the user asked for them
3194 (by passing --debug or --info or or --notice --warn to the "test"
3195 binary). This change prevents us from missing unexpected log
3196 messages simply because we were looking for others. Related to
3198 - The unit tests now log all warning messages with the "BUG" flag.
3199 Previously, they only logged errors by default. This change will
3200 help us make our testing code more correct, and make sure that we
3201 only hit this code when we mean to. In the meantime, however,
3202 there will be more warnings in the unit test logs than before.
3203 This is preparatory work for ticket 19999.
3204 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
3205 assertion as a test failure.
3207 o Minor bug fixes (circuits):
3208 - Use the CircuitBuildTimeout option whenever
3209 LearnCircuitBuildTimeout is disabled. Previously, we would respect
3210 the option when a user disabled it, but not when it was disabled
3211 because some other option was set. Fixes bug 20073; bugfix on
3212 0.2.4.12-alpha. Patch by teor.
3214 o Minor bugfixes (allocation):
3215 - Change how we allocate memory for large chunks on buffers, to
3216 avoid a (currently impossible) integer overflow, and to waste less
3217 space when allocating unusually large chunks. Fixes bug 20081;
3218 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
3219 - Always include orconfig.h before including any other C headers.
3220 Sometimes, it includes macros that affect the behavior of the
3221 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
3222 first version to use AC_USE_SYSTEM_EXTENSIONS).
3223 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
3224 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
3225 Patch from Gisle Vanem.
3226 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
3227 They apparently require a set of annotations that we aren't
3228 currently using, and they create false positives in our pthreads
3229 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
3231 o Minor bugfixes (directory authority):
3232 - Die with a more useful error when the operator forgets to place
3233 the authority_signing_key file into the keys directory. This
3234 avoids an uninformative assert & traceback about having an invalid
3235 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
3236 - When allowing private addresses, mark Exits that only exit to
3237 private locations as such. Fixes bug 20064; bugfix
3240 o Minor bugfixes (documentation):
3241 - Document the default PathsNeededToBuildCircuits value that's used
3242 by clients when the directory authorities don't set
3243 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
3244 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
3245 - Fix manual for the User option: it takes a username, not a UID.
3246 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
3249 o Minor bugfixes (hidden services):
3250 - Stop logging intro point details to the client log on certain
3251 error conditions. Fixed as part of bug 20012; bugfix on
3252 0.2.4.8-alpha. Patch by teor.
3254 o Minor bugfixes (IPv6, testing):
3255 - Check for IPv6 correctly on Linux when running test networks.
3256 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
3258 o Minor bugfixes (Linux seccomp2 sandbox):
3259 - Add permission to run the sched_yield() and sigaltstack() system
3260 calls, in order to support versions of Tor compiled with asan or
3261 ubsan code that use these calls. Now "sandbox 1" and
3262 "--enable-expensive-hardening" should be compatible on more
3263 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
3265 o Minor bugfixes (logging):
3266 - When logging a message from the BUG() macro, be explicit about
3267 what we were asserting. Previously we were confusing what we were
3268 asserting with what the bug was. Fixes bug 20093; bugfix
3270 - When we are unable to remove the bw_accounting file, do not warn
3271 if the reason we couldn't remove it was that it didn't exist.
3272 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
3274 o Minor bugfixes (option parsing):
3275 - Count unix sockets when counting client listeners (SOCKS, Trans,
3276 NATD, and DNS). This has no user-visible behaviour changes: these
3277 options are set once, and never read. Required for correct
3278 behaviour in ticket 17178. Fixes bug 19677; bugfix on
3279 0.2.6.3-alpha. Patch by teor.
3281 o Minor bugfixes (options):
3282 - Check the consistency of UseEntryGuards and EntryNodes more
3283 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
3285 - Stop changing the configured value of UseEntryGuards on
3286 authorities and Tor2web clients. Fixes bug 20074; bugfix on
3287 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
3290 o Minor bugfixes (Tor2web):
3291 - Prevent Tor2web clients running hidden services, these services
3292 are not anonymous due to the one-hop client paths. Fixes bug
3293 19678. Patch by teor.
3295 o Minor bugfixes (unit tests):
3296 - Fix a shared-random unit test that was failing on big endian
3297 architectures due to internal representation of a integer copied
3298 to a buffer. The test is changed to take a full 32 bytes of data
3299 and use the output of a python script that make the COMMIT and
3300 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
3302 - The tor_tls_server_info_callback unit test no longer crashes when
3303 debug-level logging is turned on. Fixes bug 20041; bugfix
3307 Changes in version 0.2.8.8 - 2016-09-23
3308 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
3309 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
3310 who select public relays as their bridges.
3312 o Major bugfixes (crash):
3313 - Fix a complicated crash bug that could affect Tor clients
3314 configured to use bridges when replacing a networkstatus consensus
3315 in which one of their bridges was mentioned. OpenBSD users saw
3316 more crashes here, but all platforms were potentially affected.
3317 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
3319 o Major bugfixes (relay, OOM handler):
3320 - Fix a timing-dependent assertion failure that could occur when we
3321 tried to flush from a circuit after having freed its cells because
3322 of an out-of-memory condition. Fixes bug 20203; bugfix on
3323 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
3326 o Minor feature (fallback directories):
3327 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
3328 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
3329 2016. Closes ticket 20190; patch by teor.
3331 o Minor features (geoip):
3332 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
3336 Changes in version 0.2.9.2-alpha - 2016-08-24
3337 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
3338 several new features and bugfixes. It also includes an important
3339 authority update and an important bugfix from 0.2.8.7. Everyone who
3340 sets the ReachableAddresses option, and all bridges, are strongly
3341 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
3343 o Directory authority changes (also in 0.2.8.7):
3344 - The "Tonga" bridge authority has been retired; the new bridge
3345 authority is "Bifroest". Closes tickets 19728 and 19690.
3347 o Major bugfixes (client, security, also in 0.2.8.7):
3348 - Only use the ReachableAddresses option to restrict the first hop
3349 in a path. In earlier versions of 0.2.8.x, it would apply to
3350 every hop in the path, with a possible degradation in anonymity
3351 for anyone using an uncommon ReachableAddress setting. Fixes bug
3352 19973; bugfix on 0.2.8.2-alpha.
3354 o Major features (user interface):
3355 - Tor now supports the ability to declare options deprecated, so
3356 that we can recommend that people stop using them. Previously,
3357 this was done in an ad-hoc way. Closes ticket 19820.
3359 o Major bugfixes (directory downloads):
3360 - Avoid resetting download status for consensuses hourly, since we
3361 already have another, smarter retry mechanism. Fixes bug 8625;
3362 bugfix on 0.2.0.9-alpha.
3364 o Minor features (config):
3365 - Warn users when descriptor and port addresses are inconsistent.
3366 Mitigates bug 13953; patch by teor.
3368 o Minor features (geoip):
3369 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
3372 o Minor features (user interface):
3373 - There is a new --list-deprecated-options command-line option to
3374 list all of the deprecated options. Implemented as part of
3377 o Minor bugfixes (code style):
3378 - Fix an integer signedness conversion issue in the case conversion
3379 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
3381 o Minor bugfixes (compilation):
3382 - Build correctly on versions of libevent2 without support for
3383 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
3385 - Fix a compilation warning on GCC versions before 4.6. Our
3386 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
3387 when it is also required as an argument to the compiler pragma.
3388 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
3390 o Minor bugfixes (compilation, also in 0.2.8.7):
3391 - Remove an inappropriate "inline" in tortls.c that was causing
3392 warnings on older versions of GCC. Fixes bug 19903; bugfix
3395 o Minor bugfixes (fallback directories, also in 0.2.8.7):
3396 - Avoid logging a NULL string pointer when loading fallback
3397 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
3398 and 0.2.8.1-alpha. Report and patch by "rubiate".
3400 o Minor bugfixes (logging):
3401 - Log a more accurate message when we fail to dump a microdescriptor.
3402 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
3404 o Minor bugfixes (memory leak):
3405 - Fix a series of slow memory leaks related to parsing torrc files
3406 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
3408 o Deprecated features:
3409 - A number of DNS-cache-related sub-options for client ports are now
3410 deprecated for security reasons, and may be removed in a future
3411 version of Tor. (We believe that client-side DNS cacheing is a bad
3412 idea for anonymity, and you should not turn it on.) The options
3413 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
3414 UseIPv4Cache, and UseIPv6Cache.
3415 - A number of options are deprecated for security reasons, and may
3416 be removed in a future version of Tor. The options are:
3417 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
3418 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
3419 CloseHSClientCircuitsImmediatelyOnTimeout,
3420 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
3421 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
3422 UseNTorHandshake, and WarnUnsafeSocks.
3423 - The *ListenAddress options are now deprecated as unnecessary: the
3424 corresponding *Port options should be used instead. These options
3425 may someday be removed. The affected options are:
3426 ControlListenAddress, DNSListenAddress, DirListenAddress,
3427 NATDListenAddress, ORListenAddress, SocksListenAddress,
3428 and TransListenAddress.
3431 - Correct the IPv6 syntax in our documentation for the
3432 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
3435 - We no longer include the (dead, deprecated) bufferevent code in
3436 Tor. Closes ticket 19450. Based on a patch from U+039b.
3439 Changes in version 0.2.8.7 - 2016-08-24
3440 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
3441 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
3442 who sets the ReachableAddresses option, and all bridges, are strongly
3443 encouraged to upgrade.
3445 o Directory authority changes:
3446 - The "Tonga" bridge authority has been retired; the new bridge
3447 authority is "Bifroest". Closes tickets 19728 and 19690.
3449 o Major bugfixes (client, security):
3450 - Only use the ReachableAddresses option to restrict the first hop
3451 in a path. In earlier versions of 0.2.8.x, it would apply to
3452 every hop in the path, with a possible degradation in anonymity
3453 for anyone using an uncommon ReachableAddress setting. Fixes bug
3454 19973; bugfix on 0.2.8.2-alpha.
3456 o Minor features (geoip):
3457 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
3460 o Minor bugfixes (compilation):
3461 - Remove an inappropriate "inline" in tortls.c that was causing
3462 warnings on older versions of GCC. Fixes bug 19903; bugfix
3465 o Minor bugfixes (fallback directories):
3466 - Avoid logging a NULL string pointer when loading fallback
3467 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
3468 and 0.2.8.1-alpha. Report and patch by "rubiate".
3471 Changes in version 0.2.9.1-alpha - 2016-08-08
3472 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
3473 series. It improves our support for hardened builds and compiler
3474 warnings, deploys some critical infrastructure for improvements to
3475 hidden services, includes a new timing backend that we hope to use for
3476 better support for traffic padding, makes it easier for programmers to
3477 log unexpected events, and contains other small improvements to
3478 security, correctness, and performance.
3480 Below are the changes since 0.2.8.6.
3482 o New system requirements:
3483 - Tor now requires Libevent version 2.0.10-stable or later. Older
3484 versions of Libevent have less efficient backends for several
3485 platforms, and lack the DNS code that we use for our server-side
3486 DNS support. This implements ticket 19554.
3487 - Tor now requires zlib version 1.2 or later, for security,
3488 efficiency, and (eventually) gzip support. (Back when we started,
3489 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
3490 released in 2003. We recommend the latest version.)
3492 o Major features (build, hardening):
3493 - Tor now builds with -ftrapv by default on compilers that support
3494 it. This option detects signed integer overflow (which C forbids),
3495 and turns it into a hard-failure. We do not apply this option to
3496 code that needs to run in constant time to avoid side-channels;
3497 instead, we use -fwrapv in that code. Closes ticket 17983.
3498 - When --enable-expensive-hardening is selected, stop applying the
3499 clang/gcc sanitizers to code that needs to run in constant time.
3500 Although we are aware of no introduced side-channels, we are not
3501 able to prove that there are none. Related to ticket 17983.
3503 o Major features (compilation):
3504 - Our big list of extra GCC warnings is now enabled by default when
3505 building with GCC (or with anything like Clang that claims to be
3506 GCC-compatible). To make all warnings into fatal compilation
3507 errors, pass --enable-fatal-warnings to configure. Closes
3509 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
3510 turn on C and POSIX extensions. (Previously, we attempted to do
3511 this on an ad hoc basis.) Closes ticket 19139.
3513 o Major features (directory authorities, hidden services):
3514 - Directory authorities can now perform the shared randomness
3515 protocol specified by proposal 250. Using this protocol, directory
3516 authorities generate a global fresh random value every day. In the
3517 future, this value will be used by hidden services to select
3518 HSDirs. This release implements the directory authority feature;
3519 the hidden service side will be implemented in the future as part
3520 of proposal 224. Resolves ticket 16943; implements proposal 250.
3522 o Major features (downloading, random exponential backoff):
3523 - When we fail to download an object from a directory service, wait
3524 for an (exponentially increasing) randomized amount of time before
3525 retrying, rather than a fixed interval as we did before. This
3526 prevents a group of Tor instances from becoming too synchronized,
3527 or a single Tor instance from becoming too predictable, in its
3528 download schedule. Closes ticket 15942.
3530 o Major bugfixes (exit policies):
3531 - Avoid disclosing exit outbound bind addresses, configured port
3532 bind addresses, and local interface addresses in relay descriptors
3533 by default under ExitPolicyRejectPrivate. Instead, only reject
3534 these (otherwise unlisted) addresses if
3535 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
3536 0.2.7.2-alpha. Patch by teor.
3538 o Major bugfixes (hidden service client):
3539 - Allow Tor clients with appropriate controllers to work with
3540 FetchHidServDescriptors set to 0. Previously, this option also
3541 disabled descriptor cache lookup, thus breaking hidden services
3542 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
3544 o Minor features (build, hardening):
3545 - Detect and work around a libclang_rt problem that would prevent
3546 clang from finding __mulodi4() on some 32-bit platforms, and thus
3547 keep -ftrapv from linking on those systems. Closes ticket 19079.
3548 - When building on a system without runtime support for the runtime
3549 hardening options, try to log a useful warning at configuration
3550 time, rather than an incomprehensible warning at link time. If
3551 expensive hardening was requested, this warning becomes an error.
3552 Closes ticket 18895.
3554 o Minor features (code safety):
3555 - In our integer-parsing functions, ensure that maxiumum value we
3556 give is no smaller than the minimum value. Closes ticket 19063;
3559 o Minor features (controller):
3560 - Implement new GETINFO queries for all downloads that use
3561 download_status_t to schedule retries. This allows controllers to
3562 examine the schedule for pending downloads. Closes ticket 19323.
3563 - Allow controllers to configure basic client authorization on
3564 hidden services when they create them with the ADD_ONION control
3565 command. Implements ticket 15588. Patch by "special".
3566 - Fire a STATUS_SERVER controller event whenever the hibernation
3567 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
3569 o Minor features (directory authority):
3570 - Directory authorities now only give the Guard flag to a relay if
3571 they are also giving it the Stable flag. This change allows us to
3572 simplify path selection for clients. It should have minimal effect
3573 in practice, since >99% of Guards already have the Stable flag.
3574 Implements ticket 18624.
3575 - Directory authorities now write their v3-status-votes file out to
3576 disk earlier in the consensus process, so we have a record of the
3577 votes even if we abort the consensus process. Resolves
3580 o Minor features (hidden service):
3581 - Stop being so strict about the payload length of "rendezvous1"
3582 cells. We used to be locked in to the "TAP" handshake length, and
3583 now we can handle better handshakes like "ntor". Resolves
3586 o Minor features (infrastructure, time):
3587 - Tor now uses the operating system's monotonic timers (where
3588 available) for internal fine-grained timing. Previously we would
3589 look at the system clock, and then attempt to compensate for the
3590 clock running backwards. Closes ticket 18908.
3591 - Tor now includes an improved timer backend, so that we can
3592 efficiently support tens or hundreds of thousands of concurrent
3593 timers, as will be needed for some of our planned anti-traffic-
3594 analysis work. This code is based on William Ahern's "timeout.c"
3595 project, which implements a "tickless hierarchical timing wheel".
3596 Closes ticket 18365.
3598 o Minor features (logging):
3599 - Provide a more useful warning message when configured with an
3600 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
3601 - When dumping unparseable router descriptors, optionally store them
3602 in separate files, named by digest, up to a configurable size
3603 limit. You can change the size limit by setting the
3604 MaxUnparseableDescSizeToLog option, and disable this feature by
3605 setting that option to 0. Closes ticket 18322.
3606 - Add a set of macros to check nonfatal assertions, for internal
3607 use. Migrating more of our checks to these should help us avoid
3608 needless crash bugs. Closes ticket 18613.
3610 o Minor features (performance):
3611 - Changer the "optimistic data" extension from "off by default" to
3612 "on by default". The default was ordinarily overridden by a
3613 consensus option, but when clients were bootstrapping for the
3614 first time, they would not have a consensus to get the option
3615 from. Changing this default When fetching a consensus for the
3616 first time, use optimistic data. This saves a round-trip during
3617 startup. Closes ticket 18815.
3619 o Minor features (relay, usability):
3620 - When the directory authorities refuse a bad relay's descriptor,
3621 encourage the relay operator to contact us. Many relay operators
3622 won't notice this line in their logs, but it's a win if even a few
3623 learn why we don't like what their relay was doing. Resolves
3626 o Minor features (testing):
3627 - Let backtrace tests work correctly under AddressSanitizer. Fixes
3628 part of bug 18934; bugfix on 0.2.5.2-alpha.
3629 - Move the test-network.sh script to chutney, and modify tor's test-
3630 network.sh to call the (newer) chutney version when available.
3631 Resolves ticket 19116. Patch by teor.
3632 - Use the lcov convention for marking lines as unreachable, so that
3633 we don't count them when we're generating test coverage data.
3634 Update our coverage tools to understand this convention. Closes
3637 o Minor bugfixes (bootstrap):
3638 - Remember the directory we fetched the consensus or previous
3639 certificates from, and use it to fetch future authority
3640 certificates. This change improves bootstrapping performance.
3641 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
3643 o Minor bugfixes (build):
3644 - The test-stem and test-network makefile targets now depend only on
3645 the tor binary that they are testing. Previously, they depended on
3646 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
3647 patch from "cypherpunks".
3649 o Minor bugfixes (circuits):
3650 - Make sure extend_info_from_router() is only called on servers.
3651 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
3653 o Minor bugfixes (compilation):
3654 - When building with Clang, use a full set of GCC warnings.
3655 (Previously, we included only a subset, because of the way we
3656 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
3658 o Minor bugfixes (directory authority):
3659 - Authorities now sort the "package" lines in their votes, for ease
3660 of debugging. (They are already sorted in consensus documents.)
3661 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
3662 - When parsing a detached signature, make sure we use the length of
3663 the digest algorithm instead of an hardcoded DIGEST256_LEN in
3664 order to avoid comparing bytes out-of-bounds with a smaller digest
3665 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
3667 o Minor bugfixes (documentation):
3668 - Document the --passphrase-fd option in the tor manpage. Fixes bug
3669 19504; bugfix on 0.2.7.3-rc.
3670 - Fix the description of the --passphrase-fd option in the
3671 tor-gencert manpage. The option is used to pass the number of a
3672 file descriptor to read the passphrase from, not to read the file
3673 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
3675 o Minor bugfixes (ephemeral hidden service):
3676 - When deleting an ephemeral hidden service, close its intro points
3677 even if they are not completely open. Fixes bug 18604; bugfix
3680 o Minor bugfixes (guard selection):
3681 - Use a single entry guard even if the NumEntryGuards consensus
3682 parameter is not provided. Fixes bug 17688; bugfix
3684 - Don't mark guards as unreachable if connection_connect() fails.
3685 That function fails for local reasons, so it shouldn't reveal
3686 anything about the status of the guard. Fixes bug 14334; bugfix
3689 o Minor bugfixes (hidden service client):
3690 - Increase the minimum number of internal circuits we preemptively
3691 build from 2 to 3, so a circuit is available when a client
3692 connects to another onion service. Fixes bug 13239; bugfix
3695 o Minor bugfixes (logging):
3696 - When logging a directory ownership mismatch, log the owning
3697 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
3699 o Minor bugfixes (memory leaks):
3700 - Fix a small, uncommon memory leak that could occur when reading a
3701 truncated ed25519 key file. Fixes bug 18956; bugfix
3704 o Minor bugfixes (testing):
3705 - Allow clients to retry HSDirs much faster in test networks. Fixes
3706 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
3707 - Disable ASAN's detection of segmentation faults while running
3708 test_bt.sh, so that we can make sure that our own backtrace
3709 generation code works. Fixes another aspect of bug 18934; bugfix
3710 on 0.2.5.2-alpha. Patch from "cypherpunks".
3711 - Fix the test-network-all target on out-of-tree builds by using the
3712 correct path to the test driver script. Fixes bug 19421; bugfix
3715 o Minor bugfixes (time):
3716 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
3717 bugfix on all released tor versions.
3718 - When computing the difference between two times in milliseconds,
3719 we now round to the nearest millisecond correctly. Previously, we
3720 could sometimes round in the wrong direction. Fixes bug 19428;
3721 bugfix on 0.2.2.2-alpha.
3723 o Minor bugfixes (user interface):
3724 - Display a more accurate number of suppressed messages in the log
3725 rate-limiter. Previously, there was a potential integer overflow
3726 in the counter. Now, if the number of messages hits a maximum, the
3727 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
3729 - Fix a typo in the passphrase prompt for the ed25519 identity key.
3730 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
3732 o Code simplification and refactoring:
3733 - Remove redundant declarations of the MIN macro. Closes
3735 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
3736 Closes ticket 18462; patch from "icanhasaccount".
3737 - Split the 600-line directory_handle_command_get function into
3738 separate functions for different URL types. Closes ticket 16698.
3741 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
3742 ticket 19153. Patch from "U+039b".
3745 - Remove support for "GET /tor/bytes.txt" DirPort request, and
3746 "GETINFO dir-usage" controller request, which were only available
3747 via a compile-time option in Tor anyway. Feature was added in
3748 0.2.2.1-alpha. Resolves ticket 19035.
3749 - There is no longer a compile-time option to disable support for
3750 TransPort. (If you don't want TransPort; just don't use it.) Patch
3751 from "U+039b". Closes ticket 19449.
3754 - Run more workqueue tests as part of "make check". These had
3755 previously been implemented, but you needed to know special
3756 command-line options to enable them.
3757 - We now have unit tests for our code to reject zlib "compression
3758 bombs". (Fortunately, the code works fine.)
3761 Changes in version 0.2.8.6 - 2016-08-02
3763 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
3765 The Tor 0.2.8 series improves client bootstrapping performance,
3766 completes the authority-side implementation of improved identity
3767 keys for relays, and includes numerous bugfixes and performance
3768 improvements throughout the program. This release continues to
3769 improve the coverage of Tor's test suite. For a full list of
3770 changes since Tor 0.2.7, see the ReleaseNotes file.
3772 Changes since 0.2.8.5-rc:
3774 o Minor features (geoip):
3775 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
3778 o Minor bugfixes (compilation):
3779 - Fix a compilation warning in the unit tests on systems where char
3780 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
3782 o Minor bugfixes (fallback directories):
3783 - Remove 1 fallback that was on the hardcoded list, then opted-out,
3784 leaving 89 of the 100 fallbacks originally introduced in Tor
3785 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
3787 o Minor bugfixes (Linux seccomp2 sandbox):
3788 - Allow more syscalls when running with "Sandbox 1" enabled:
3789 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
3790 some systems, these are required for Tor to start. Fixes bug
3791 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
3792 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
3793 so that get_interface_address6_via_udp_socket_hack() can work.
3794 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
3797 Changes in version 0.2.8.5-rc - 2016-07-07
3798 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
3799 series. If we find no new bugs or regressions here, the first stable
3800 0.2.8 release will be identical to it. It has a few small bugfixes
3801 against previous versions.
3803 o Directory authority changes:
3804 - Urras is no longer a directory authority. Closes ticket 19271.
3806 o Major bugfixes (heartbeat):
3807 - Fix a regression that would crash Tor when the periodic
3808 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
3809 0.2.8.1-alpha. Reported by "kubaku".
3811 o Minor features (build):
3812 - Tor now again builds with the recent OpenSSL 1.1 development
3813 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
3814 - When building manual pages, set the timezone to "UTC", so that the
3815 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
3816 Patch from intrigeri.
3818 o Minor bugfixes (fallback directory selection):
3819 - Avoid errors during fallback selection if there are no eligible
3820 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
3823 o Minor bugfixes (IPv6, microdescriptors):
3824 - Don't check node addresses when we only have a routerstatus. This
3825 allows IPv6-only clients to bootstrap by fetching microdescriptors
3826 from fallback directory mirrors. (The microdescriptor consensus
3827 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
3830 o Minor bugfixes (logging):
3831 - Reduce pointlessly verbose log messages when directory servers
3832 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
3833 0.2.8.1-alpha. Patch by teor.
3834 - When a fallback directory changes its fingerprint from the hard-
3835 coded fingerprint, log a less severe, more explanatory log
3836 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
3838 o Minor bugfixes (Linux seccomp2 sandboxing):
3839 - Allow statistics to be written to disk when "Sandbox 1" is
3840 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
3841 0.2.6.1-alpha respectively.
3843 o Minor bugfixes (user interface):
3844 - Remove a warning message "Service [scrubbed] not found after
3845 descriptor upload". This message appears when one uses HSPOST
3846 control command to upload a service descriptor. Since there is
3847 only a descriptor and no service, showing this message is
3848 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
3850 o Fallback directory list:
3851 - Add a comment to the generated fallback directory list that
3852 explains how to comment out unsuitable fallbacks in a way that's
3853 compatible with the stem fallback parser.
3854 - Update fallback whitelist and blacklist based on relay operator
3855 emails. Blacklist unsuitable (non-working, over-volatile)
3856 fallbacks. Resolves ticket 19071. Patch by teor.
3857 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
3858 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
3859 ticket 19071; patch by teor.
3862 Changes in version 0.2.8.4-rc - 2016-06-15
3863 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
3864 If we find no new bugs or regressions here, the first stable 0.2.8
3865 release will be identical to it. It has a few small bugfixes against
3868 o Major bugfixes (user interface):
3869 - Correctly give a warning in the cases where a relay is specified
3870 by nickname, and one such relay is found, but it is not officially
3871 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
3873 o Minor features (build):
3874 - Tor now builds once again with the recent OpenSSL 1.1 development
3875 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
3877 o Minor features (geoip):
3878 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
3881 o Minor bugfixes (compilation):
3882 - Cause the unit tests to compile correctly on mingw64 versions that
3883 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
3885 o Minor bugfixes (downloading):
3886 - Predict more correctly whether we'll be downloading over HTTP when
3887 we determine the maximum length of a URL. This should avoid a
3888 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
3892 Changes in version 0.2.8.3-alpha - 2016-05-26
3893 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
3894 the course of the 0.2.8 development cycle. It improves the behavior of
3895 directory clients, fixes several crash bugs, fixes a gap in compiler
3896 hardening, and allows the full integration test suite to run on
3899 o Major bugfixes (security, client, DNS proxy):
3900 - Stop a crash that could occur when a client running with DNSPort
3901 received a query with multiple address types, and the first
3902 address type was not supported. Found and fixed by Scott Dial.
3903 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
3905 o Major bugfixes (security, compilation):
3906 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
3907 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
3908 cause a compiler warning, thereby making other checks fail, and
3909 needlessly disabling compiler-hardening support. Fixes one case of
3910 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
3912 o Major bugfixes (security, directory authorities):
3913 - Fix a crash and out-of-bounds write during authority voting, when
3914 the list of relays includes duplicate ed25519 identity keys. Fixes
3915 bug 19032; bugfix on 0.2.8.2-alpha.
3917 o Major bugfixes (client, bootstrapping):
3918 - Check if bootstrap consensus downloads are still needed when the
3919 linked connection attaches. This prevents tor making unnecessary
3920 begindir-style connections, which are the only directory
3921 connections tor clients make since the fix for 18483 was merged.
3922 - Fix some edge cases where consensus download connections may not
3923 have been closed, even though they were not needed. Related to fix
3925 - Make relays retry consensus downloads the correct number of times,
3926 rather than the more aggressive client retry count. Fixes part of
3928 - Stop downloading consensuses when we have a consensus, even if we
3929 don't have all the certificates for it yet. Fixes bug 18809;
3930 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
3932 o Major bugfixes (directory mirrors):
3933 - Decide whether to advertise begindir support in the the same way
3934 we decide whether to advertise our DirPort. Allowing these
3935 decisions to become out-of-sync led to surprising behavior like
3936 advertising begindir support when hibernation made us not
3937 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
3940 o Major bugfixes (IPv6 bridges, client):
3941 - Actually use IPv6 addresses when selecting directory addresses for
3942 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
3945 o Major bugfixes (key management):
3946 - If OpenSSL fails to generate an RSA key, do not retain a dangling
3947 pointer to the previous (uninitialized) key value. The impact here
3948 should be limited to a difficult-to-trigger crash, if OpenSSL is
3949 running an engine that makes key generation failures possible, or
3950 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
3951 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
3954 o Major bugfixes (testing):
3955 - Fix a bug that would block 'make test-network-all' on systems where
3956 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
3957 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
3958 bugfix on 0.2.8.1-alpha.
3960 o Minor features (clients):
3961 - Make clients, onion services, and bridge relays always use an
3962 encrypted begindir connection for directory requests. Resolves
3963 ticket 18483. Patch by "teor".
3965 o Minor features (fallback directory mirrors):
3966 - Give each fallback the same weight for client selection; restrict
3967 fallbacks to one per operator; report fallback directory detail
3968 changes when rebuilding list; add new fallback directory mirrors
3969 to the whitelist; and many other minor simplifications and fixes.
3970 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
3971 0.2.8.1-alpha; patch by "teor".
3972 - Replace the 21 fallbacks generated in January 2016 and included in
3973 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
3974 2016. Closes task 17158; patch by "teor".
3976 o Minor features (geoip):
3977 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
3980 o Minor bugfixes (assert, portability):
3981 - Fix an assertion failure in memarea.c on systems where "long" is
3982 shorter than the size of a pointer. Fixes bug 18716; bugfix
3985 o Minor bugfixes (bootstrap):
3986 - Consistently use the consensus download schedule for authority
3987 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
3989 o Minor bugfixes (build):
3990 - Remove a pair of redundant AM_CONDITIONAL declarations from
3991 configure.ac. Fixes one final case of bug 17744; bugfix
3993 - Resolve warnings when building on systems that are concerned with
3994 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
3996 - When libscrypt.h is found, but no libscrypt library can be linked,
3997 treat libscrypt as absent. Fixes bug 19161; bugfix
4000 o Minor bugfixes (client):
4001 - Turn all TestingClientBootstrap* into non-testing torrc options.
4002 This changes simply renames them by removing "Testing" in front of
4003 them and they do not require TestingTorNetwork to be enabled
4004 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
4005 - Make directory node selection more reliable, mainly for IPv6-only
4006 clients and clients with few reachable addresses. Fixes bug 18929;
4007 bugfix on 0.2.8.1-alpha. Patch by "teor".
4009 o Minor bugfixes (controller, microdescriptors):
4010 - Make GETINFO dir/status-vote/current/consensus conform to the
4011 control specification by returning "551 Could not open cached
4012 consensus..." when not caching consensuses. Fixes bug 18920;
4013 bugfix on 0.2.2.6-alpha.
4015 o Minor bugfixes (crypto, portability):
4016 - The SHA3 and SHAKE routines now produce the correct output on Big
4017 Endian systems. No code calls either algorithm yet, so this is
4018 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
4019 - Tor now builds again with the recent OpenSSL 1.1 development
4020 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
4023 o Minor bugfixes (directories):
4024 - When fetching extrainfo documents, compare their SHA256 digests
4025 and Ed25519 signing key certificates with the routerinfo that led
4026 us to fetch them, rather than with the most recent routerinfo.
4027 Otherwise we generate many spurious warnings about mismatches.
4028 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
4030 o Minor bugfixes (logging):
4031 - When we can't generate a signing key because OfflineMasterKey is
4032 set, do not imply that we should have been able to load it. Fixes
4033 bug 18133; bugfix on 0.2.7.2-alpha.
4034 - Stop periodic_event_dispatch() from blasting twelve lines per
4035 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
4036 - When rejecting a misformed INTRODUCE2 cell, only log at
4037 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
4039 o Minor bugfixes (pluggable transports):
4040 - Avoid reporting a spurious error when we decide that we don't need
4041 to terminate a pluggable transport because it has already exited.
4042 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
4044 o Minor bugfixes (pointer arithmetic):
4045 - Fix a bug in memarea_alloc() that could have resulted in remote
4046 heap write access, if Tor had ever passed an unchecked size to
4047 memarea_alloc(). Fortunately, all the sizes we pass to
4048 memarea_alloc() are pre-checked to be less than 128 kilobytes.
4049 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
4052 o Minor bugfixes (relays):
4053 - Consider more config options when relays decide whether to
4054 regenerate their descriptor. Fixes more of bug 12538; bugfix
4056 - Resolve some edge cases where we might launch an ORPort
4057 reachability check even when DisableNetwork is set. Noticed while
4058 fixing bug 18616; bugfix on 0.2.3.9-alpha.
4060 o Minor bugfixes (statistics):
4061 - We now include consensus downloads via IPv6 in our directory-
4062 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
4064 o Minor bugfixes (testing):
4065 - Allow directories in small networks to bootstrap by skipping
4066 DirPort checks when the consensus has no exits. Fixes bug 19003;
4067 bugfix on 0.2.8.1-alpha. Patch by teor.
4068 - Fix a small memory leak that would occur when the
4069 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
4070 bugfix on 0.2.5.2-alpha.
4072 o Minor bugfixes (time handling):
4073 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
4074 field. Otherwise, our unit tests crash on Windows. Fixes bug
4075 18977; bugfix on 0.2.2.25-alpha.
4078 - Document the contents of the 'datadir/keys' subdirectory in the
4079 manual page. Closes ticket 17621.
4080 - Stop recommending use of nicknames to identify relays in our
4081 MapAddress documentation. Closes ticket 18312.
4084 Changes in version 0.2.8.2-alpha - 2016-03-28
4085 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
4086 bugs in earlier versions of Tor, including some that prevented
4087 authorities using Tor 0.2.7.x from running correctly. IPv6 and
4088 directory support should also be much improved.
4090 o New system requirements:
4091 - Tor no longer supports versions of OpenSSL with a broken
4092 implementation of counter mode. (This bug was present in OpenSSL
4093 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
4094 longer runs with, these versions.
4095 - Tor no longer attempts to support platforms where the "time_t"
4096 type is unsigned. (To the best of our knowledge, only OpenVMS does
4097 this, and Tor has never actually built on OpenVMS.) Closes
4099 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
4100 later (released in 2008 and 2009 respectively). If you are
4101 building Tor from the git repository instead of from the source
4102 distribution, and your tools are older than this, you will need to
4103 upgrade. Closes ticket 17732.
4105 o Major bugfixes (security, pointers):
4106 - Avoid a difficult-to-trigger heap corruption attack when extending
4107 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4108 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4109 Reported by Guido Vranken.
4111 o Major bugfixes (bridges, pluggable transports):
4112 - Modify the check for OR connections to private addresses. Allow
4113 bridges on private addresses, including pluggable transports that
4114 ignore the (potentially private) address in the bridge line. Fixes
4115 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
4117 o Major bugfixes (compilation):
4118 - Repair hardened builds under the clang compiler. Previously, our
4119 use of _FORTIFY_SOURCE would conflict with clang's address
4120 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
4122 o Major bugfixes (crash on shutdown):
4123 - Correctly handle detaching circuits from muxes when shutting down.
4124 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
4125 - Fix an assert-on-exit bug related to counting memory usage in
4126 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
4128 o Major bugfixes (crash on startup):
4129 - Fix a segfault during startup: If a Unix domain socket was
4130 configured as listener (such as a ControlSocket or a SocksPort
4131 "unix:" socket), and tor was started as root but not configured to
4132 switch to another user, tor would segfault while trying to string
4133 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
4136 o Major bugfixes (dns proxy mode, crash):
4137 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4138 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4140 o Major bugfixes (relays, bridge clients):
4141 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
4142 bridge clients use the address configured in the bridge line.
4143 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
4146 o Major bugfixes (voting):
4147 - Actually enable support for authorities to match routers by their
4148 Ed25519 identities. Previously, the code had been written, but
4149 some debugging code that had accidentally been left in the
4150 codebase made it stay turned off. Fixes bug 17702; bugfix
4152 - When collating votes by Ed25519 identities, authorities now
4153 include a "NoEdConsensus" flag if the ed25519 value (or lack
4154 thereof) for a server does not reflect the majority consensus.
4155 Related to bug 17668; bugfix on 0.2.7.2-alpha.
4156 - When generating a vote with keypinning disabled, never include two
4157 entries for the same ed25519 identity. This bug was causing
4158 authorities to generate votes that they could not parse when a
4159 router violated key pinning by changing its RSA identity but
4160 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
4161 18318. Bugfix on 0.2.7.2-alpha.
4163 o Minor features (security, win32):
4164 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
4165 attack. Fixes bug 18123; bugfix on all tor versions. Patch
4168 o Minor features (bug-resistance):
4169 - Make Tor survive errors involving connections without a
4170 corresponding event object. Previously we'd fail with an
4171 assertion; now we produce a log message. Related to bug 16248.
4173 o Minor features (build):
4174 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
4175 as having possible IPFW support. Closes ticket 18448. Patch from
4178 o Minor features (code hardening):
4179 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
4180 level code, to harden against accidental failures to NUL-
4181 terminate. Part of ticket 17852. Patch from jsturgix. Found
4184 o Minor features (crypto):
4185 - Validate the hard-coded Diffie-Hellman parameters and ensure that
4186 p is a safe prime, and g is a suitable generator. Closes
4189 o Minor features (geoip):
4190 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
4193 o Minor features (hidden service directory):
4194 - Streamline relay-side hsdir handling: when relays consider whether
4195 to accept an uploaded hidden service descriptor, they no longer
4196 check whether they are one of the relays in the network that is
4197 "supposed" to handle that descriptor. Implements ticket 18332.
4199 o Minor features (IPv6):
4200 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
4201 to 1, tor prefers IPv6 directory addresses.
4202 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
4203 avoids using IPv4 for client OR and directory connections.
4204 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
4205 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
4206 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
4208 o Minor features (linux seccomp2 sandbox):
4209 - Reject attempts to change our Address with "Sandbox 1" enabled.
4210 Changing Address with Sandbox turned on would never actually work,
4211 but previously it would fail in strange and confusing ways. Found
4214 o Minor features (robustness):
4215 - Exit immediately with an error message if the code attempts to use
4216 Libevent without having initialized it. This should resolve some
4217 frequently-made mistakes in our unit tests. Closes ticket 18241.
4219 o Minor features (unix domain sockets):
4220 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
4221 Unix domain sockets without checking the permissions on the parent
4222 directory. (Tor checks permissions by default because some
4223 operating systems only check permissions on the parent directory.
4224 However, some operating systems do look at permissions on the
4225 socket, and tor's default check is unneeded.) Closes ticket 18458.
4228 o Minor bugfixes (exit policies, security):
4229 - Refresh an exit relay's exit policy when interface addresses
4230 change. Previously, tor only refreshed the exit policy when the
4231 configured external address changed. Fixes bug 18208; bugfix on
4232 0.2.7.3-rc. Patch by teor.
4234 o Minor bugfixes (security, hidden services):
4235 - Prevent hidden services connecting to client-supplied rendezvous
4236 addresses that are reserved as internal or multicast. Fixes bug
4237 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
4239 o Minor bugfixes (build):
4240 - Do not link the unit tests against both the testing and non-
4241 testing versions of the static libraries. Fixes bug 18490; bugfix
4243 - Avoid spurious failures from configure files related to calling
4244 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
4245 0.2.0.1-alpha. Patch from "cypherpunks".
4246 - Silence spurious clang-scan warnings in the ed25519_donna code by
4247 explicitly initializing some objects. Fixes bug 18384; bugfix on
4248 0.2.7.2-alpha. Patch by teor.
4250 o Minor bugfixes (client, bootstrap):
4251 - Count receipt of new microdescriptors as progress towards
4252 bootstrapping. Previously, with EntryNodes set, Tor might not
4253 successfully repopulate the guard set on bootstrapping. Fixes bug
4254 16825; bugfix on 0.2.3.1-alpha.
4256 o Minor bugfixes (code correctness):
4257 - Update to the latest version of Trunnel, which tries harder to
4258 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
4259 by clang address sanitizer. Fixes bug 18373; bugfix
4262 o Minor bugfixes (configuration):
4263 - Fix a tiny memory leak when parsing a port configuration ending in
4264 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
4266 o Minor bugfixes (containers):
4267 - If we somehow attempt to construct a heap with more than
4268 1073741822 elements, avoid an integer overflow when maintaining
4269 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
4271 o Minor bugfixes (correctness):
4272 - Fix a bad memory handling bug that would occur if we had queued a
4273 cell on a channel's incoming queue. Fortunately, we can't actually
4274 queue a cell like that as our code is constructed today, but it's
4275 best to avoid this kind of error, even if there isn't any code
4276 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
4278 o Minor bugfixes (directory):
4279 - When generating a URL for a directory server on an IPv6 address,
4280 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
4281 on 0.2.3.9-alpha. Patch from Malek.
4283 o Minor bugfixes (fallback directory mirrors):
4284 - When requesting extrainfo descriptors from a trusted directory
4285 server, check whether it is an authority or a fallback directory
4286 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
4287 0.2.4.7-alpha. Reported by atagar, patch by teor.
4289 o Minor bugfixes (hidden service, client):
4290 - Handle the case where the user makes several fast consecutive
4291 requests to the same .onion address. Previously, the first six
4292 requests would each trigger a descriptor fetch, each picking a
4293 directory (there are 6 overall) and the seventh one would fail
4294 because no directories were left, thereby triggering a close on
4295 all current directory connections asking for the hidden service.
4296 The solution here is to not close the connections if we have
4297 pending directory fetches. Fixes bug 15937; bugfix
4300 o Minor bugfixes (hidden service, control port):
4301 - Add the onion address to the HS_DESC event for the UPLOADED action
4302 both on success or failure. It was previously hardcoded with
4303 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
4305 o Minor bugfixes (hidden service, directory):
4306 - Bridges now refuse "rendezvous2" (hidden service descriptor)
4307 publish attempts. Suggested by ticket 18332.
4309 o Minor bugfixes (linux seccomp2 sandbox):
4310 - Allow the setrlimit syscall, and the prlimit and prlimit64
4311 syscalls, which some libc implementations use under the hood.
4312 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
4313 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
4314 enabled and no DNS resolvers configured. This should help TAILS
4315 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
4316 - Fix the sandbox's interoperability with unix domain sockets under
4317 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
4319 o Minor bugfixes (logging):
4320 - When logging information about an unparsable networkstatus vote or
4321 consensus, do not say "vote" when we mean consensus. Fixes bug
4322 18368; bugfix on 0.2.0.8-alpha.
4323 - Scrub service name in "unrecognized service ID" log messages.
4324 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
4325 - Downgrade logs and backtraces about IP versions to info-level.
4326 Only log backtraces once each time tor runs. Assists in diagnosing
4327 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
4328 Christian, patch by teor.
4330 o Minor bugfixes (memory safety):
4331 - Avoid freeing an uninitialized pointer when opening a socket fails
4332 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
4333 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
4335 - Correctly duplicate addresses in get_interface_address6_list().
4336 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
4337 patch by "cypherpunks".
4338 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
4340 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
4341 18672; bugfix on 0.2.5.1-alpha.
4343 o Minor bugfixes (private directory):
4344 - Prevent a race condition when creating private directories. Fixes
4345 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
4346 Patch from jsturgix. Found with Flawfinder.
4348 o Minor bugfixes (test networks, IPv6):
4349 - Allow internal IPv6 addresses in descriptors in test networks.
4350 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
4353 o Minor bugfixes (testing):
4354 - We no longer disable assertions in the unit tests when coverage is
4355 enabled. Instead, we require you to say --disable-asserts-in-tests
4356 to the configure script if you need assertions disabled in the
4357 unit tests (for example, if you want to perform branch coverage).
4358 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
4360 o Minor bugfixes (time parsing):
4361 - Avoid overflow in tor_timegm when parsing dates in and after 2038
4362 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
4363 0.0.2pre14. Patch by teor.
4365 o Minor bugfixes (tor-gencert):
4366 - Correctly handle the case where an authority operator enters a
4367 passphrase but sends an EOF before sending a newline. Fixes bug
4368 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
4370 o Code simplification and refactoring:
4371 - Quote all the string interpolations in configure.ac -- even those
4372 which we are pretty sure can't contain spaces. Closes ticket
4373 17744. Patch from zerosion.
4374 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
4375 inplace, so there's no need to have a separate implementation for
4376 the non-inplace code. Closes ticket 18258. Patch from Malek.
4377 - Simplify return types for some crypto functions that can't
4378 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
4381 - Change build messages to refer to "Fedora" instead of "Fedora
4382 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
4383 Patches from "icanhasaccount" and "cypherpunks".
4386 - We no longer maintain an internal freelist in memarea.c.
4387 Allocators should be good enough to make this code unnecessary,
4388 and it's doubtful that it ever had any performance benefit.
4391 - Fix several warnings from clang's address sanitizer produced in
4393 - Treat backtrace test failures as expected on FreeBSD until we
4394 solve bug 17808. Closes ticket 18204.
4397 Changes in version 0.2.8.1-alpha - 2016-02-04
4398 Tor 0.2.8.1-alpha is the first alpha release in its series. It
4399 includes numerous small features and bugfixes against previous Tor
4400 versions, and numerous small infrastructure improvements. The most
4401 notable features are a set of improvements to the directory subsystem.
4403 o Major features (security, Linux):
4404 - When Tor starts as root on Linux and is told to switch user ID, it
4405 can now retain the capability to bind to low ports. By default,
4406 Tor will do this only when it's switching user ID and some low
4407 ports have been configured. You can change this behavior with the
4408 new option KeepBindCapabilities. Closes ticket 8195.
4410 o Major features (directory system):
4411 - When bootstrapping multiple consensus downloads at a time, use the
4412 first one that starts downloading, and close the rest. This
4413 reduces failures when authorities or fallback directories are slow
4414 or down. Together with the code for feature 15775, this feature
4415 should reduces failures due to fallback churn. Implements ticket
4416 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
4417 "mikeperry" and "teor".
4418 - Include a trial list of 21 default fallback directories, generated
4419 in January 2016, based on an opt-in survey of suitable relays.
4420 Doing this should make clients bootstrap more quickly and reliably,
4421 and reduce the load on the directory authorities. Closes ticket
4422 15775. Patch by "teor".
4423 Candidates identified using an OnionOO script by "weasel", "teor",
4424 "gsathya", and "karsten".
4425 - Previously only relays that explicitly opened a directory port
4426 (DirPort) accepted directory requests from clients. Now all
4427 relays, with and without a DirPort, accept and serve tunneled
4428 directory requests that they receive through their ORPort. You can
4429 disable this behavior using the new DirCache option. Closes
4432 o Major key updates:
4433 - Update the V3 identity key for the dannenberg directory authority:
4434 it was changed on 18 November 2015. Closes task 17906. Patch
4437 o Minor features (security, clock):
4438 - Warn when the system clock appears to move back in time (when the
4439 state file was last written in the future). Tor doesn't know that
4440 consensuses have expired if the clock is in the past. Patch by
4441 "teor". Implements ticket 17188.
4443 o Minor features (security, exit policies):
4444 - ExitPolicyRejectPrivate now rejects more private addresses by
4445 default. Specifically, it now rejects the relay's outbound bind
4446 addresses (if configured), and the relay's configured port
4447 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
4448 0.2.0.11-alpha. Patch by "teor".
4450 o Minor features (security, memory erasure):
4451 - Set the unused entries in a smartlist to NULL. This helped catch
4452 a (harmless) bug, and shouldn't affect performance too much.
4453 Implements ticket 17026.
4454 - Use SecureMemoryWipe() function to securely clean memory on
4455 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
4456 Implements feature 17986.
4457 - Use explicit_bzero or memset_s when present. Previously, we'd use
4458 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
4459 from <logan@hackers.mu> and <selven@hackers.mu>.
4460 - Make memwipe() do nothing when passed a NULL pointer or buffer of
4461 zero size. Check size argument to memwipe() for underflow. Fixes
4462 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
4465 o Minor features (security, RNG):
4466 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
4467 positively are not allowed to fail. Previously we depended on
4468 internal details of OpenSSL's behavior. Closes ticket 17686.
4469 - Never use the system entropy output directly for anything besides
4470 seeding the PRNG. When we want to generate important keys, instead
4471 of using system entropy directly, we now hash it with the PRNG
4472 stream. This may help resist certain attacks based on broken OS
4473 entropy implementations. Closes part of ticket 17694.
4474 - Use modern system calls (like getentropy() or getrandom()) to
4475 generate strong entropy on platforms that have them. Closes
4478 o Minor features (accounting):
4479 - Added two modes to the AccountingRule option: One for limiting
4480 only the number of bytes sent ("AccountingRule out"), and one for
4481 limiting only the number of bytes received ("AccountingRule in").
4482 Closes ticket 15989; patch from "unixninja92".
4484 o Minor features (build):
4485 - Since our build process now uses "make distcheck", we no longer
4486 force "make dist" to depend on "make check". Closes ticket 17893;
4487 patch from "cypherpunks."
4488 - Tor now builds successfully with the recent OpenSSL 1.1
4489 development branch, and with the latest LibreSSL. Closes tickets
4490 17549, 17921, and 17984.
4492 o Minor features (controller):
4493 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
4494 tickets 16774 and 17817. Patch by George Tankersley.
4495 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
4496 service descriptor from a service's local hidden service
4497 descriptor cache. Closes ticket 14846.
4498 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
4499 controllers can examine the the reject rules added by
4500 ExitPolicyRejectPrivate. This makes it easier for stem to display
4503 o Minor features (crypto):
4504 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
4506 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
4507 - When allocating a digest state object, allocate no more space than
4508 we actually need. Previously, we would allocate as much space as
4509 the state for the largest algorithm would need. This change saves
4510 up to 672 bytes per circuit. Closes ticket 17796.
4511 - Improve performance when hashing non-multiple of 8 sized buffers,
4512 based on Andrew Moon's public domain SipHash-2-4 implementation.
4513 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
4515 o Minor features (directory downloads):
4516 - Wait for busy authorities and fallback directories to become non-
4517 busy when bootstrapping. (A similar change was made in 6c443e987d
4518 for directory caches chosen from the consensus.) Closes ticket
4519 17864; patch by "teor".
4520 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
4521 directory mirrors. The default is 1; set it to 0 to disable
4522 fallbacks. Implements ticket 17576. Patch by "teor".
4524 o Minor features (geoip):
4525 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
4528 o Minor features (IPv6):
4529 - Add an argument 'ipv6=address:orport' to the DirAuthority and
4530 FallbackDir torrc options, to specify an IPv6 address for an
4531 authority or fallback directory. Add hard-coded ipv6 addresses for
4532 directory authorities that have them. Closes ticket 17327; patch
4533 from Nick Mathewson and "teor".
4534 - Add address policy assume_action support for IPv6 addresses.
4535 - Limit IPv6 mask bits to 128.
4536 - Warn when comparing against an AF_UNSPEC address in a policy, it's
4537 almost always a bug. Closes ticket 17863; patch by "teor".
4538 - Allow users to configure directory authorities and fallback
4539 directory servers with IPv6 addresses and ORPorts. Resolves
4541 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
4542 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
4543 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
4544 17638; bugfix on 0.0.2pre8. Patch by "teor".
4546 o Minor features (logging):
4547 - When logging to syslog, allow a tag to be added to the syslog
4548 identity (the string prepended to every log message). The tag can
4549 be configured with SyslogIdentityTag and defaults to none. Setting
4550 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
4553 o Minor features (portability):
4554 - Use timingsafe_memcmp() where available. Closes ticket 17944;
4555 patch from <logan@hackers.mu>.
4557 o Minor features (relay, address discovery):
4558 - Add a family argument to get_interface_addresses_raw() and
4559 subfunctions to make network interface address interogation more
4560 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
4561 types of interfaces from the operating system. Resolves
4563 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
4564 fails to enumerate interface addresses using the platform-specific
4565 API, have it rely on the UDP socket fallback technique to try and
4566 find out what IP addresses (both IPv4 and IPv6) our machine has.
4567 Resolves ticket 17951.
4569 o Minor features (replay cache):
4570 - The replay cache now uses SHA256 instead of SHA1. Implements
4571 feature 8961. Patch by "teor", issue reported by "rransom".
4573 o Minor features (unix file permissions):
4574 - Defer creation of Unix sockets until after setuid. This avoids
4575 needing CAP_CHOWN and CAP_FOWNER when using systemd's
4576 CapabilityBoundingSet, or chown and fowner when using SELinux.
4577 Implements part of ticket 17562. Patch from Jamie Nguyen.
4578 - If any directory created by Tor is marked as group readable, the
4579 filesystem group is allowed to be either the default GID or the
4580 root user. Allowing root to read the DataDirectory prevents the
4581 need for CAP_READ_SEARCH when using systemd's
4582 CapabilityBoundingSet, or dac_read_search when using SELinux.
4583 Implements part of ticket 17562. Patch from Jamie Nguyen.
4584 - Introduce a new DataDirectoryGroupReadable option. If it is set to
4585 1, the DataDirectory will be made readable by the default GID.
4586 Implements part of ticket 17562. Patch from Jamie Nguyen.
4588 o Minor bugfixes (accounting):
4589 - The max bandwidth when using 'AccountRule sum' is now correctly
4590 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
4593 o Minor bugfixes (code correctness):
4594 - When closing an entry connection, generate a warning if we should
4595 have sent an end cell for it but we haven't. Fixes bug 17876;
4596 bugfix on 0.2.3.2-alpha.
4597 - Assert that allocated memory held by the reputation code is freed
4598 according to its internal counters. Fixes bug 17753; bugfix
4600 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
4603 o Minor bugfixes (compilation):
4604 - Mark all object files that include micro-revision.i as depending
4605 on it, so as to make parallel builds more reliable. Fixes bug
4606 17826; bugfix on 0.2.5.1-alpha.
4607 - Don't try to use the pthread_condattr_setclock() function unless
4608 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
4609 17819; bugfix on 0.2.6.3-alpha.
4610 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
4612 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
4613 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
4614 - Fix search for libevent libraries on OpenBSD (and other systems
4615 that install libevent 1 and libevent 2 in parallel). Fixes bug
4616 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
4617 - Isolate environment variables meant for tests from the rest of the
4618 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
4619 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
4621 - Remove config.log only from make distclean, not from make clean.
4622 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
4624 o Minor bugfixes (crypto):
4625 - Check the return value of HMAC() and assert on failure. Fixes bug
4626 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
4628 o Minor bugfixes (fallback directories):
4629 - Mark fallbacks as "too busy" when they return a 503 response,
4630 rather than just marking authorities. Fixes bug 17572; bugfix on
4631 0.2.4.7-alpha. Patch by "teor".
4633 o Minor bugfixes (IPv6):
4634 - Update the limits in max_dl_per_request for IPv6 address length.
4635 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
4637 o Minor bugfixes (linux seccomp2 sandbox):
4638 - Fix a crash when using offline master ed25519 keys with the Linux
4639 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
4641 o Minor bugfixes (logging):
4642 - In log messages that include a function name, use __FUNCTION__
4643 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
4644 with clang __PRETTY_FUNCTION__ has extra information we don't
4645 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
4647 - Remove needless quotes from a log message about unparseable
4648 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
4650 o Minor bugfixes (portability):
4651 - Remove an #endif from configure.ac so that we correctly detect the
4652 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
4655 o Minor bugfixes (relays):
4656 - Check that both the ORPort and DirPort (if present) are reachable
4657 before publishing a relay descriptor. Otherwise, relays publish a
4658 descriptor with DirPort 0 when the DirPort reachability test takes
4659 longer than the ORPort reachability test. Fixes bug 18050; bugfix
4660 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
4662 o Minor bugfixes (relays, hidden services):
4663 - Refuse connection requests to private OR addresses unless
4664 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
4665 then refuse to send any cells to a private address. Fixes bugs
4666 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
4668 o Minor bugfixes (safe logging):
4669 - When logging a malformed hostname received through socks4, scrub
4670 it if SafeLogging says we should. Fixes bug 17419; bugfix
4673 o Minor bugfixes (statistics code):
4674 - Consistently check for overflow in round_*_to_next_multiple_of
4675 functions, and add unit tests with additional and maximal values.
4676 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
4677 - Handle edge cases in the laplace functions: avoid division by
4678 zero, avoid taking the log of zero, and silence clang type
4679 conversion warnings using round and trunc. Add unit tests for edge
4680 cases with maximal values. Fixes part of bug 13192; bugfix
4683 o Minor bugfixes (testing):
4684 - The test for log_heartbeat was incorrectly failing in timezones
4685 with non-integer offsets. Instead of comparing the end of the time
4686 string against a constant, compare it to the output of
4687 format_local_iso_time when given the correct input. Fixes bug
4688 18039; bugfix on 0.2.5.4-alpha.
4689 - Make unit tests pass on IPv6-only systems, and systems without
4690 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
4691 bugfix on 0.2.7.3-rc. Patch by "teor".
4692 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
4694 - Check the full results of SHA256 and SHA512 digests in the unit
4695 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
4697 o Code simplification and refactoring:
4698 - Move logging of redundant policy entries in
4699 policies_parse_exit_policy_internal into its own function. Closes
4700 ticket 17608; patch from "juce".
4701 - Extract the more complicated parts of circuit_mark_for_close()
4702 into a new function that we run periodically before circuits are
4703 freed. This change removes more than half of the functions
4704 currently in the "blob". Closes ticket 17218.
4705 - Clean up a little duplicated code in
4706 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
4708 - Decouple the list of streams waiting to be attached to circuits
4709 from the overall connection list. This change makes it possible to
4710 attach streams quickly while simplifying Tor's callgraph and
4711 avoiding O(N) scans of the entire connection list. Closes
4713 - When a direct directory request fails immediately on launch,
4714 instead of relaunching that request from inside the code that
4715 launches it, instead mark the connection for teardown. This change
4716 simplifies Tor's callback and prevents the directory-request
4717 launching code from invoking itself recursively. Closes
4719 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
4720 use them. Closes ticket 17926.
4723 - Add a description of the correct use of the '--keygen' command-
4724 line option. Closes ticket 17583; based on text by 's7r'.
4725 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
4726 - Explain actual minima for BandwidthRate. Closes ticket 16382.
4727 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
4728 - Mention torspec URL in the manpage and point the reader to it
4729 whenever we mention a document that belongs in torspce. Fixes
4733 - Remove client-side support for connecting to Tor relays running
4734 versions of Tor before 0.2.3.6-alpha. These relays didn't support
4735 the v3 TLS handshake protocol, and are no longer allowed on the
4736 Tor network. Implements the client side of ticket 11150. Based on
4737 patches by Tom van der Woerdt.
4740 - Add unit tests to check for common RNG failure modes, such as
4741 returning all zeroes, identical values, or incrementing values
4742 (OpenSSL's rand_predictable feature). Patch by "teor".
4743 - Log more information when the backtrace tests fail. Closes ticket
4744 17892. Patch from "cypherpunks."
4745 - Always test both ed25519 backends, so that we can be sure that our
4746 batch-open replacement code works. Part of ticket 16794.
4747 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
4748 portion of ticket 16831.
4749 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
4750 util_format.c, directory.c, and options_validate.c. Closes tickets
4751 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
4753 - Unit tests for directory_handle_command_get. Closes ticket 17004.
4754 Patch from Reinaldo de Souza Jr.
4757 Changes in version 0.2.7.6 - 2015-12-10
4758 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
4759 well as a minor bug in hidden service reliability.
4761 o Major bugfixes (guard selection):
4762 - Actually look at the Guard flag when selecting a new directory
4763 guard. When we implemented the directory guard design, we
4764 accidentally started treating all relays as if they have the Guard
4765 flag during guard selection, leading to weaker anonymity and worse
4766 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
4769 o Minor features (geoip):
4770 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
4773 o Minor bugfixes (compilation):
4774 - When checking for net/pfvar.h, include netinet/in.h if possible.
4775 This fixes transparent proxy detection on OpenBSD. Fixes bug
4776 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
4777 - Fix a compilation warning with Clang 3.6: Do not check the
4778 presence of an address which can never be NULL. Fixes bug 17781.
4780 o Minor bugfixes (correctness):
4781 - When displaying an IPv6 exit policy, include the mask bits
4782 correctly even when the number is greater than 31. Fixes bug
4783 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
4784 - The wrong list was used when looking up expired intro points in a
4785 rend service object, causing what we think could be reachability
4786 issues for hidden services, and triggering a BUG log. Fixes bug
4787 16702; bugfix on 0.2.7.2-alpha.
4788 - Fix undefined behavior in the tor_cert_checksig function. Fixes
4789 bug 17722; bugfix on 0.2.7.2-alpha.
4792 Changes in version 0.2.7.5 - 2015-11-20
4793 The Tor 0.2.7 release series is dedicated to the memory of Tor user
4794 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
4795 tirelessly to advocate human rights regardless of national borders,
4796 and oppose the encroachments of mass surveillance. He opposed national
4797 exceptionalism, he brought clarity to legal and policy debates, he
4798 understood and predicted the impact of mass surveillance on the world,
4799 and he laid the groundwork for resisting it. While serving on the Tor
4800 Project's board of directors, he brought us his uncompromising focus
4801 on technical excellence in the service of humankind. Caspar was an
4802 inimitable force for good and a wonderful friend. He was kind,
4803 humorous, generous, gallant, and believed we should protect one
4804 another without exception. We honor him here for his ideals, his
4805 efforts, and his accomplishments. Please honor his memory with works
4806 that would make him proud.
4808 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
4810 The 0.2.7 series adds a more secure identity key type for relays,
4811 improves cryptography performance, resolves several longstanding
4812 hidden-service performance issues, improves controller support for
4813 hidden services, and includes small bugfixes and performance
4814 improvements throughout the program. This release series also includes
4815 more tests than before, and significant simplifications to which parts
4816 of Tor invoke which others.
4818 (This release contains no code changes since 0.2.7.4-rc.)
4821 Changes in version 0.2.7.4-rc - 2015-10-21
4822 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
4823 fixes some important memory leaks, and a scary-looking (but mostly
4824 harmless in practice) invalid-read bug. It also has a few small
4825 bugfixes, notably fixes for compilation and portability on different
4826 platforms. If no further significant bounds are found, the next
4827 release will the the official stable release.
4829 o Major bugfixes (security, correctness):
4830 - Fix an error that could cause us to read 4 bytes before the
4831 beginning of an openssl string. This bug could be used to cause
4832 Tor to crash on systems with unusual malloc implementations, or
4833 systems with unusual hardening installed. Fixes bug 17404; bugfix
4836 o Major bugfixes (correctness):
4837 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
4838 bug 17401; bugfix on 0.2.7.3-rc.
4840 o Major bugfixes (memory leaks):
4841 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
4842 17398; bugfix on 0.2.6.1-alpha.
4843 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
4844 17402; bugfix on 0.2.7.3-rc.
4845 - Fix a memory leak when reading an expired signing key from disk.
4846 Fixes bug 17403; bugfix on 0.2.7.2-rc.
4848 o Minor features (geoIP):
4849 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
4852 o Minor bugfixes (compilation):
4853 - Repair compilation with the most recent (unreleased, alpha)
4854 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
4855 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
4856 17251; bugfix on 0.2.7.2-alpha.
4857 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
4858 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
4860 o Minor bugfixes (portability):
4861 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
4862 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
4865 o Minor bugfixes (sandbox):
4866 - Add the "hidserv-stats" filename to our sandbox filter for the
4867 HiddenServiceStatistics option to work properly. Fixes bug 17354;
4868 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
4870 o Minor bugfixes (testing):
4871 - Add unit tests for get_interface_address* failure cases. Fixes bug
4872 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
4873 - Fix breakage when running 'make check' with BSD make. Fixes bug
4874 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
4875 - Make the get_ifaddrs_* unit tests more tolerant of different
4876 network configurations. (Don't assume every test box has an IPv4
4877 address, and don't assume every test box has a non-localhost
4878 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
4879 - Skip backtrace tests when backtrace support is not compiled in.
4880 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
4884 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
4885 - Note that HiddenServicePorts can take a unix domain socket. Closes
4889 Changes in version 0.2.7.3-rc - 2015-09-25
4890 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
4891 contains numerous usability fixes for Ed25519 keys, safeguards against
4892 several misconfiguration problems, significant simplifications to
4893 Tor's callgraph, and numerous bugfixes and small features.
4895 This is the most tested release of Tor to date. The unit tests cover
4896 39.40% of the code, and the integration tests (accessible with "make
4897 test-full-online", requiring stem and chutney and a network
4898 connection) raise the coverage to 64.49%.
4900 o Major features (security, hidden services):
4901 - Hidden services, if using the EntryNodes option, are required to
4902 use more than one EntryNode, in order to avoid a guard discovery
4903 attack. (This would only affect people who had configured hidden
4904 services and manually specified the EntryNodes option with a
4905 single entry-node. The impact was that it would be easy to
4906 remotely identify the guard node used by such a hidden service.
4907 See ticket for more information.) Fixes ticket 14917.
4909 o Major features (Ed25519 keys, keypinning):
4910 - The key-pinning option on directory authorities is now advisory-
4911 only by default. In a future version, or when the AuthDirPinKeys
4912 option is set, pins are enforced again. Disabling key-pinning
4913 seemed like a good idea so that we can survive the fallout of any
4914 usability problems associated with Ed25519 keys. Closes
4917 o Major features (Ed25519 performance):
4918 - Improve the speed of Ed25519 operations and Curve25519 keypair
4919 generation when built targeting 32 bit x86 platforms with SSE2
4920 available. Implements ticket 16535.
4921 - Improve the runtime speed of Ed25519 signature verification by
4922 using Ed25519-donna's batch verification support. Implements
4925 o Major features (performance testing):
4926 - The test-network.sh script now supports performance testing.
4927 Requires corresponding chutney performance testing changes. Patch
4928 by "teor". Closes ticket 14175.
4930 o Major features (relay, Ed25519):
4931 - Significant usability improvements for Ed25519 key management. Log
4932 messages are better, and the code can recover from far more
4933 failure conditions. Thanks to "s7r" for reporting and diagnosing
4935 - Add a new OfflineMasterKey option to tell Tor never to try loading
4936 or generating a secret Ed25519 identity key. You can use this in
4937 combination with tor --keygen to manage offline and/or encrypted
4938 Ed25519 keys. Implements ticket 16944.
4939 - Add a --newpass option to allow changing or removing the
4940 passphrase of an encrypted key with tor --keygen. Implements part
4942 - On receiving a HUP signal, check to see whether the Ed25519
4943 signing key has changed, and reload it if so. Closes ticket 16790.
4945 o Major bugfixes (relay, Ed25519):
4946 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
4947 0.2.7.2-alpha. Reported by "s7r".
4948 - Improve handling of expired signing keys with offline master keys.
4949 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
4951 o Minor features (client-side privacy):
4952 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
4953 lifespan when IsolateSOCKSAuth and streams with SOCKS
4954 authentication are attached to the circuit. This allows
4955 applications like TorBrowser to manage circuit lifetime on their
4956 own. Implements feature 15482.
4957 - When logging malformed hostnames from SOCKS5 requests, respect
4958 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
4960 o Minor features (compilation):
4961 - Give a warning as early as possible when trying to build with an
4962 unsupported OpenSSL version. Closes ticket 16901.
4963 - Fail during configure if we're trying to build against an OpenSSL
4964 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
4965 which started requiring ECC.
4967 o Minor features (geoip):
4968 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
4971 o Minor features (hidden services):
4972 - Relays need to have the Fast flag to get the HSDir flag. As this
4973 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
4974 drop. This change should make some attacks against the hidden
4975 service directory system harder. Fixes ticket 15963.
4976 - Turn on hidden service statistics collection by setting the torrc
4977 option HiddenServiceStatistics to "1" by default. (This keeps
4978 track only of the fraction of traffic used by hidden services, and
4979 the total number of hidden services in existence.) Closes
4981 - Client now uses an introduction point failure cache to know when
4982 to fetch or keep a descriptor in their cache. Previously, failures
4983 were recorded implicitly, but not explicitly remembered. Closes
4986 o Minor features (testing, authorities, documentation):
4987 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
4988 explicitly manage consensus flags in testing networks. Patch by
4989 "robgjansen", modified by "teor". Implements part of ticket 14882.
4991 o Minor bugfixes (security, exit policies):
4992 - ExitPolicyRejectPrivate now also rejects the relay's published
4993 IPv6 address (if any), and any publicly routable IPv4 or IPv6
4994 addresses on any local interfaces. ticket 17027. Patch by "teor".
4995 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
4997 o Minor bug fixes (torrc exit policies):
4998 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
4999 produce IPv6 wildcard addresses. Previously they would produce
5000 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
5001 of bug 16069; bugfix on 0.2.4.7-alpha.
5002 - When parsing torrc ExitPolicies, we now warn for a number of cases
5003 where the user's intent is likely to differ from Tor's actual
5004 behavior. These include: using an IPv4 address with an accept6 or
5005 reject6 line; using "private" on an accept6 or reject6 line; and
5006 including any ExitPolicy lines after accept *:* or reject *:*.
5007 Related to ticket 16069.
5008 - When parsing torrc ExitPolicies, we now issue an info-level
5009 message when expanding an "accept/reject *" line to include both
5010 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
5011 - In each instance above, usage advice is provided to avoid the
5012 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
5013 16069; bugfix on 0.2.4.7-alpha.
5015 o Minor bugfixes (authority):
5016 - Don't assign "HSDir" to a router if it isn't Valid and Running.
5017 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
5018 - Downgrade log messages about Ed25519 key issues if they are in old
5019 cached router descriptors. Fixes part of bug 16286; bugfix
5021 - When we find an Ed25519 key issue in a cached descriptor, stop
5022 saying the descriptor was just "uploaded". Fixes another part of
5023 bug 16286; bugfix on 0.2.7.2-alpha.
5025 o Minor bugfixes (control port):
5026 - Repair a warning and a spurious result when getting the maximum
5027 number of file descriptors from the controller. Fixes bug 16697;
5028 bugfix on 0.2.7.2-alpha.
5030 o Minor bugfixes (correctness):
5031 - When calling channel_free_list(), avoid calling smartlist_remove()
5032 while inside a FOREACH loop. This partially reverts commit
5033 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
5034 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
5036 o Minor bugfixes (documentation):
5037 - Advise users on how to configure separate IPv4 and IPv6 exit
5038 policies in the manpage and sample torrcs. Related to ticket 16069.
5039 - Fix the usage message of tor-resolve(1) so that it no longer lists
5040 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
5041 - Fix an error in the manual page and comments for
5042 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
5043 required "ORPort connectivity". While this is true, it is in no
5044 way unique to the HSDir flag. Of all the flags, only HSDirs need a
5045 DirPort configured in order for the authorities to assign that
5046 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
5049 o Minor bugfixes (Ed25519):
5050 - Fix a memory leak when reading router descriptors with expired
5051 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
5053 o Minor bugfixes (linux seccomp2 sandbox):
5054 - Allow bridge authorities to run correctly under the seccomp2
5055 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
5056 - Allow routers with ed25519 keys to run correctly under the
5057 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
5059 o Minor bugfixes (open file limit):
5060 - Fix set_max_file_descriptors() to set by default the max open file
5061 limit to the current limit when setrlimit() fails. Fixes bug
5062 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
5064 o Minor bugfixes (portability):
5065 - Try harder to normalize the exit status of the Tor process to the
5066 standard-provided range. Fixes bug 16975; bugfix on every version
5068 - Check correctly for Windows socket errors in the workqueue
5069 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
5070 - Fix the behavior of crypto_rand_time_range() when told to consider
5071 times before 1970. (These times were possible when running in a
5072 simulated network environment where time()'s output starts at
5073 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
5074 - Restore correct operation of TLS client-cipher detection on
5075 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
5077 o Minor bugfixes (relay):
5078 - Ensure that worker threads actually exit when a fatal error or
5079 shutdown is indicated. This fix doesn't currently affect the
5080 behavior of Tor, because Tor workers never indicates fatal error
5081 or shutdown except in the unit tests. Fixes bug 16868; bugfix
5083 - Unblock threads before releasing the work queue mutex to ensure
5084 predictable scheduling behavior. Fixes bug 16644; bugfix
5087 o Code simplification and refactoring:
5088 - Change the function that's called when we need to retry all
5089 downloads so that it only reschedules the downloads to happen
5090 immediately, rather than launching them all at once itself. This
5091 further simplifies Tor's callgraph.
5092 - Move some format-parsing functions out of crypto.c and
5093 crypto_curve25519.c into crypto_format.c and/or util_format.c.
5094 - Move the client-only parts of init_keys() into a separate
5095 function. Closes ticket 16763.
5096 - Simplify the microdesc_free() implementation so that it no longer
5097 appears (to code analysis tools) to potentially invoke a huge
5098 suite of other microdesc functions.
5099 - Simply the control graph further by deferring the inner body of
5100 directory_all_unreachable() into a callback. Closes ticket 16762.
5101 - Treat the loss of an owning controller as equivalent to a SIGTERM
5102 signal. This removes a tiny amount of duplicated code, and
5103 simplifies our callgraph. Closes ticket 16788.
5104 - When generating an event to send to the controller, we no longer
5105 put the event over the network immediately. Instead, we queue
5106 these events, and use a Libevent callback to deliver them. This
5107 change simplifies Tor's callgraph by reducing the number of
5108 functions from which all other Tor functions are reachable. Closes
5110 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
5111 that try to scan or compile every file on Unix won't decide that
5113 - Remove the unused "nulterminate" argument from buf_pullup().
5116 - Recommend a 40 GB example AccountingMax in torrc.sample rather
5117 than a 4 GB max. Closes ticket 16742.
5118 - Include the TUNING document in our source tarball. It is referred
5119 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
5123 - The internal pure-C tor-fw-helper tool is now removed from the Tor
5124 distribution, in favor of the pure-Go clone available from
5125 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
5126 used by the C tor-fw-helper are not, in our opinion, very
5127 confidence- inspiring in their secure-programming techniques.
5128 Closes ticket 13338.
5129 - Remove the code that would try to aggressively flush controller
5130 connections while writing to them. This code was introduced in
5131 0.1.2.7-alpha, in order to keep output buffers from exceeding
5132 their limits. But there is no longer a maximum output buffer size,
5133 and flushing data in this way caused some undesirable recursions
5134 in our call graph. Closes ticket 16480.
5137 - Make "bridges+hs" the default test network. This tests almost all
5138 tor functionality during make test-network, while allowing tests
5139 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
5140 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
5141 (chutney). Patches by "teor".
5142 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
5143 by-side in the same parent directory. Closes ticket 16903. Patch
5145 - Use environment variables rather than autoconf substitutions to
5146 send variables from the build system to the test scripts. This
5147 change should be easier to maintain, and cause 'make distcheck' to
5148 work better than before. Fixes bug 17148.
5149 - Add a new set of callgraph analysis scripts that use clang to
5150 produce a list of which Tor functions are reachable from which
5151 other Tor functions. We're planning to use these to help simplify
5152 our code structure by identifying illogical dependencies.
5153 - Add new 'test-full' and 'test-full-online' targets to run all
5154 tests, including integration tests with stem and chutney.
5155 - Make the test-workqueue test work on Windows by initializing the
5156 network before we begin.
5157 - New make target (make test-network-all) to run multiple applicable
5158 chutney test cases. Patch from Teor; closes 16953.
5159 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
5160 functions in dns.c. Implements a portion of ticket 16831.
5161 - When building Tor with testing coverage enabled, run Chutney tests
5162 (if any) using the 'tor-cov' coverage binary.
5163 - When running test-network or test-stem, check for the absence of
5164 stem/chutney before doing any build operations.
5167 Changes in version 0.2.7.2-alpha - 2015-07-27
5168 This, the second alpha in the Tor 0.2.7 series, has a number of new
5169 features, including a way to manually pick the number of introduction
5170 points for hidden services, and the much stronger Ed25519 signing key
5171 algorithm for regular Tor relays (including support for encrypted
5172 offline identity keys in the new algorithm).
5174 Support for Ed25519 on relays is currently limited to signing router
5175 descriptors; later alphas in this series will extend Ed25519 key
5176 support to more parts of the Tor protocol.
5178 o Major features (Ed25519 identity keys, Proposal 220):
5179 - All relays now maintain a stronger identity key, using the Ed25519
5180 elliptic curve signature format. This master key is designed so
5181 that it can be kept offline. Relays also generate an online
5182 signing key, and a set of other Ed25519 keys and certificates.
5183 These are all automatically regenerated and rotated as needed.
5184 Implements part of ticket 12498.
5185 - Directory authorities now vote on Ed25519 identity keys along with
5186 RSA1024 keys. Implements part of ticket 12498.
5187 - Directory authorities track which Ed25519 identity keys have been
5188 used with which RSA1024 identity keys, and do not allow them to
5189 vary freely. Implements part of ticket 12498.
5190 - Microdescriptors now include Ed25519 identity keys. Implements
5191 part of ticket 12498.
5192 - Add support for offline encrypted Ed25519 master keys. To use this
5193 feature on your tor relay, run "tor --keygen" to make a new master
5194 key (or to make a new signing key if you already have a master
5195 key). Closes ticket 13642.
5197 o Major features (Hidden services):
5198 - Add the torrc option HiddenServiceNumIntroductionPoints, to
5199 specify a fixed number of introduction points. Its maximum value
5200 is 10 and default is 3. Using this option can increase a hidden
5201 service's reliability under load, at the cost of making it more
5202 visible that the hidden service is facing extra load. Closes
5204 - Remove the adaptive algorithm for choosing the number of
5205 introduction points, which used to change the number of
5206 introduction points (poorly) depending on the number of
5207 connections the HS sees. Closes ticket 4862.
5209 o Major features (onion key cross-certification):
5210 - Relay descriptors now include signatures of their own identity
5211 keys, made using the TAP and ntor onion keys. These signatures
5212 allow relays to prove ownership of their own onion keys. Because
5213 of this change, microdescriptors will no longer need to include
5214 RSA identity keys. Implements proposal 228; closes ticket 12499.
5216 o Major features (performance):
5217 - Improve the runtime speed of Ed25519 operations by using the
5218 public-domain Ed25519-donna by Andrew M. ("floodyberry").
5219 Implements ticket 16467.
5220 - Improve the runtime speed of the ntor handshake by using an
5221 optimized curve25519 basepoint scalarmult implementation from the
5222 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
5223 ideas by Adam Langley. Implements ticket 9663.
5225 o Major bugfixes (client-side privacy, also in 0.2.6.9):
5226 - Properly separate out each SOCKSPort when applying stream
5227 isolation. The error occurred because each port's session group
5228 was being overwritten by a default value when the listener
5229 connection was initialized. Fixes bug 16247; bugfix on
5230 0.2.6.3-alpha. Patch by "jojelino".
5232 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
5233 - Stop refusing to store updated hidden service descriptors on a
5234 client. This reverts commit 9407040c59218 (which indeed fixed bug
5235 14219, but introduced a major hidden service reachability
5236 regression detailed in bug 16381). This is a temporary fix since
5237 we can live with the minor issue in bug 14219 (it just results in
5238 some load on the network) but the regression of 16381 is too much
5239 of a setback. First-round fix for bug 16381; bugfix
5242 o Major bugfixes (hidden services):
5243 - When cannibalizing a circuit for an introduction point, always
5244 extend to the chosen exit node (creating a 4 hop circuit).
5245 Previously Tor would use the current circuit exit node, which
5246 changed the original choice of introduction point, and could cause
5247 the hidden service to skip excluded introduction points or
5248 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
5251 o Major bugfixes (open file limit):
5252 - The open file limit wasn't checked before calling
5253 tor_accept_socket_nonblocking(), which would make Tor exceed the
5254 limit. Now, before opening a new socket, Tor validates the open
5255 file limit just before, and if the max has been reached, return an
5256 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
5258 o Major bugfixes (stability, also in 0.2.6.10):
5259 - Stop crashing with an assertion failure when parsing certain kinds
5260 of malformed or truncated microdescriptors. Fixes bug 16400;
5261 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
5262 by "cypherpunks_backup".
5263 - Stop random client-side assertion failures that could occur when
5264 connecting to a busy hidden service, or connecting to a hidden
5265 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
5268 o Minor features (directory authorities, security, also in 0.2.6.9):
5269 - The HSDir flag given by authorities now requires the Stable flag.
5270 For the current network, this results in going from 2887 to 2806
5271 HSDirs. Also, it makes it harder for an attacker to launch a sybil
5272 attack by raising the effort for a relay to become Stable to
5273 require at the very least 7 days, while maintaining the 96 hours
5274 uptime requirement for HSDir. Implements ticket 8243.
5276 o Minor features (client):
5277 - Relax the validation of hostnames in SOCKS5 requests, allowing the
5278 character '_' to appear, in order to cope with domains observed in
5279 the wild that are serving non-RFC compliant records. Resolves
5281 - Relax the validation done to hostnames in SOCKS5 requests, and
5282 allow a single trailing '.' to cope with clients that pass FQDNs
5283 using that syntax to explicitly indicate that the domain name is
5284 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
5285 - Add GroupWritable and WorldWritable options to unix-socket based
5286 SocksPort and ControlPort options. These options apply to a single
5287 socket, and override {Control,Socks}SocketsGroupWritable. Closes
5290 o Minor features (control protocol):
5291 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
5292 the control protocol. Resolves ticket 15358.
5294 o Minor features (directory authorities):
5295 - Directory authorities no longer vote against the "Fast", "Stable",
5296 and "HSDir" flags just because they were going to vote against
5297 "Running": if the consensus turns out to be that the router was
5298 running, then the authority's vote should count. Patch from Peter
5299 Retzlaff; closes issue 8712.
5301 o Minor features (geoip, also in 0.2.6.10):
5302 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
5303 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
5305 o Minor features (hidden services):
5306 - Add the new options "HiddenServiceMaxStreams" and
5307 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
5308 limit the maximum number of simultaneous streams per circuit, and
5309 optionally tear down the circuit when the limit is exceeded. Part
5312 o Minor features (portability):
5313 - Use C99 variadic macros when the compiler is not GCC. This avoids
5314 failing compilations on MSVC, and fixes a log-file-based race
5315 condition in our old workarounds. Original patch from Gisle Vanem.
5317 o Minor bugfixes (compilation, also in 0.2.6.9):
5318 - Build with --enable-systemd correctly when libsystemd is
5319 installed, but systemd is not. Fixes bug 16164; bugfix on
5320 0.2.6.3-alpha. Patch from Peter Palfrader.
5322 o Minor bugfixes (controller):
5323 - Add the descriptor ID in each HS_DESC control event. It was
5324 missing, but specified in control-spec.txt. Fixes bug 15881;
5325 bugfix on 0.2.5.2-alpha.
5327 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
5328 - Check for failures from crypto_early_init, and refuse to continue.
5329 A previous typo meant that we could keep going with an
5330 uninitialized crypto library, and would have OpenSSL initialize
5331 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
5332 when implementing ticket 4900. Patch by "teor".
5334 o Minor bugfixes (hidden services):
5335 - Fix a crash when reloading configuration while at least one
5336 configured and one ephemeral hidden service exists. Fixes bug
5337 16060; bugfix on 0.2.7.1-alpha.
5338 - Avoid crashing with a double-free bug when we create an ephemeral
5339 hidden service but adding it fails for some reason. Fixes bug
5340 16228; bugfix on 0.2.7.1-alpha.
5342 o Minor bugfixes (Linux seccomp2 sandbox):
5343 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
5344 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
5346 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
5347 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
5348 these when eventfd2() support is missing. Fixes bug 16363; bugfix
5349 on 0.2.6.3-alpha. Patch from "teor".
5351 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
5352 - Fix sandboxing to work when running as a relay, by allowing the
5353 renaming of secret_id_key, and allowing the eventfd2 and futex
5354 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
5356 - Allow systemd connections to work with the Linux seccomp2 sandbox
5357 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
5360 o Minor bugfixes (relay):
5361 - Fix a rarely-encountered memory leak when failing to initialize
5362 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
5365 o Minor bugfixes (systemd):
5366 - Fix an accidental formatting error that broke the systemd
5367 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
5368 - Tor's systemd unit file no longer contains extraneous spaces.
5369 These spaces would sometimes confuse tools like deb-systemd-
5370 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
5372 o Minor bugfixes (tests):
5373 - Use the configured Python executable when running test-stem-full.
5374 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
5376 o Minor bugfixes (tests, also in 0.2.6.9):
5377 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
5378 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
5380 o Minor bugfixes (threads, comments):
5381 - Always initialize return value in compute_desc_id in rendcommon.c
5382 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
5383 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
5384 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
5385 - Remove undefined directive-in-macro in test_util_writepid clang
5386 3.7 complains that using a preprocessor directive inside a macro
5387 invocation in test_util_writepid in test_util.c is undefined.
5388 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
5390 o Code simplification and refactoring:
5391 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
5392 to ensure they remain consistent and visible everywhere.
5393 - Remove some vestigial workarounds for the MSVC6 compiler. We
5394 haven't supported that in ages.
5395 - The link authentication code has been refactored for better
5396 testability and reliability. It now uses code generated with the
5397 "trunnel" binary encoding generator, to reduce the risk of bugs
5398 due to programmer error. Done as part of ticket 12498.
5401 - Include a specific and (hopefully) accurate documentation of the
5402 torrc file's meta-format in doc/torrc_format.txt. This is mainly
5403 of interest to people writing programs to parse or generate torrc
5404 files. This document is not a commitment to long-term
5405 compatibility; some aspects of the current format are a bit
5406 ridiculous. Closes ticket 2325.
5409 - Tor no longer supports copies of OpenSSL that are missing support
5410 for Elliptic Curve Cryptography. (We began using ECC when
5411 available in 0.2.4.8-alpha, for more safe and efficient key
5412 negotiation.) In particular, support for at least one of P256 or
5413 P224 is now required, with manual configuration needed if only
5414 P224 is available. Resolves ticket 16140.
5415 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
5416 on an operating system that has not upgraded to OpenSSL 1.0 or
5417 later, and you compile Tor from source, you will need to install a
5418 more recent OpenSSL to link Tor against.) These versions of
5419 OpenSSL are still supported by the OpenSSL, but the numerous
5420 cryptographic improvements in later OpenSSL releases makes them a
5421 clear choice. Resolves ticket 16034.
5422 - Remove the HidServDirectoryV2 option. Now all relays offer to
5423 store hidden service descriptors. Related to 16543.
5424 - Remove the VoteOnHidServDirectoriesV2 option, since all
5425 authorities have long set it to 1. Closes ticket 16543.
5428 - Document use of coverity, clang static analyzer, and clang dynamic
5429 undefined behavior and address sanitizers in doc/HACKING. Include
5430 detailed usage instructions in the blacklist. Patch by "teor".
5431 Closes ticket 15817.
5432 - The link authentication protocol code now has extensive tests.
5433 - The relay descriptor signature testing code now has
5435 - The test_workqueue program now runs faster, and is enabled by
5436 default as a part of "make check".
5437 - Now that OpenSSL has its own scrypt implementation, add an unit
5438 test that checks for interoperability between libscrypt_scrypt()
5439 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
5440 and rely on EVP_PBE_scrypt() whenever possible. Resolves
5444 Changes in version 0.2.6.10 - 2015-07-12
5445 Tor version 0.2.6.10 fixes some significant stability and hidden
5446 service client bugs, bulletproofs the cryptography init process, and
5447 fixes a bug when using the sandbox code with some older versions of
5448 Linux. Everyone running an older version, especially an older version
5449 of 0.2.6, should upgrade.
5451 o Major bugfixes (hidden service clients, stability):
5452 - Stop refusing to store updated hidden service descriptors on a
5453 client. This reverts commit 9407040c59218 (which indeed fixed bug
5454 14219, but introduced a major hidden service reachability
5455 regression detailed in bug 16381). This is a temporary fix since
5456 we can live with the minor issue in bug 14219 (it just results in
5457 some load on the network) but the regression of 16381 is too much
5458 of a setback. First-round fix for bug 16381; bugfix
5461 o Major bugfixes (stability):
5462 - Stop crashing with an assertion failure when parsing certain kinds
5463 of malformed or truncated microdescriptors. Fixes bug 16400;
5464 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
5465 by "cypherpunks_backup".
5466 - Stop random client-side assertion failures that could occur when
5467 connecting to a busy hidden service, or connecting to a hidden
5468 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
5471 o Minor features (geoip):
5472 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
5473 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
5475 o Minor bugfixes (crypto error-handling):
5476 - Check for failures from crypto_early_init, and refuse to continue.
5477 A previous typo meant that we could keep going with an
5478 uninitialized crypto library, and would have OpenSSL initialize
5479 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
5480 when implementing ticket 4900. Patch by "teor".
5482 o Minor bugfixes (Linux seccomp2 sandbox):
5483 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
5484 these when eventfd2() support is missing. Fixes bug 16363; bugfix
5485 on 0.2.6.3-alpha. Patch from "teor".
5488 Changes in version 0.2.6.9 - 2015-06-11
5489 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
5490 requirements for receiving an HSDir flag, and addresses some other small
5491 bugs in the systemd and sandbox code. Clients using circuit isolation
5492 should upgrade; all directory authorities should upgrade.
5494 o Major bugfixes (client-side privacy):
5495 - Properly separate out each SOCKSPort when applying stream
5496 isolation. The error occurred because each port's session group was
5497 being overwritten by a default value when the listener connection
5498 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
5501 o Minor feature (directory authorities, security):
5502 - The HSDir flag given by authorities now requires the Stable flag.
5503 For the current network, this results in going from 2887 to 2806
5504 HSDirs. Also, it makes it harder for an attacker to launch a sybil
5505 attack by raising the effort for a relay to become Stable which
5506 takes at the very least 7 days to do so and by keeping the 96
5507 hours uptime requirement for HSDir. Implements ticket 8243.
5509 o Minor bugfixes (compilation):
5510 - Build with --enable-systemd correctly when libsystemd is
5511 installed, but systemd is not. Fixes bug 16164; bugfix on
5512 0.2.6.3-alpha. Patch from Peter Palfrader.
5514 o Minor bugfixes (Linux seccomp2 sandbox):
5515 - Fix sandboxing to work when running as a relaymby renaming of
5516 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
5517 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
5518 - Allow systemd connections to work with the Linux seccomp2 sandbox
5519 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
5522 o Minor bugfixes (tests):
5523 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
5524 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
5527 Changes in version 0.2.6.8 - 2015-05-21
5528 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
5529 fixes an authority-side bug in assigning the HSDir flag. All directory
5530 authorities should upgrade.
5532 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
5533 - Revert commit that made directory authorities assign the HSDir
5534 flag to relays without a DirPort; this was bad because such relays
5535 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
5538 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
5539 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
5540 a client authorized hidden service. Fixes bug 15823; bugfix
5543 o Minor features (geoip):
5544 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
5545 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
5549 Changes in version 0.2.7.1-alpha - 2015-05-12
5550 Tor 0.2.7.1-alpha is the first alpha release in its series. It
5551 includes numerous small features and bugfixes against previous Tor
5552 versions, and numerous small infrastructure improvements. The most
5553 notable features are several new ways for controllers to interact with
5554 the hidden services subsystem.
5556 o New system requirements:
5557 - Tor no longer includes workarounds to support Libevent versions
5558 before 1.3e. Libevent 2.0 or later is recommended. Closes
5561 o Major features (controller):
5562 - Add the ADD_ONION and DEL_ONION commands that allow the creation
5563 and management of hidden services via the controller. Closes
5565 - New "GETINFO onions/current" and "GETINFO onions/detached"
5566 commands to get information about hidden services created via the
5567 controller. Part of ticket 6411.
5568 - New HSFETCH command to launch a request for a hidden service
5569 descriptor. Closes ticket 14847.
5570 - New HSPOST command to upload a hidden service descriptor. Closes
5571 ticket 3523. Patch by "DonnchaC".
5573 o Major bugfixes (hidden services):
5574 - Revert commit that made directory authorities assign the HSDir
5575 flag to relays without a DirPort; this was bad because such relays
5576 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
5579 o Minor features (clock-jump tolerance):
5580 - Recover better when our clock jumps back many hours, like might
5581 happen for Tails or Whonix users who start with a very wrong
5582 hardware clock, use Tor to discover a more accurate time, and then
5583 fix their clock. Resolves part of ticket 8766.
5585 o Minor features (command-line interface):
5586 - Make --hash-password imply --hush to prevent unnecessary noise.
5587 Closes ticket 15542. Patch from "cypherpunks".
5588 - Print a warning whenever we find a relative file path being used
5589 as torrc option. Resolves issue 14018.
5591 o Minor features (controller):
5592 - Add DirAuthority lines for default directory authorities to the
5593 output of the "GETINFO config/defaults" command if not already
5594 present. Implements ticket 14840.
5595 - Controllers can now use "GETINFO hs/client/desc/id/..." to
5596 retrieve items from the client's hidden service descriptor cache.
5597 Closes ticket 14845.
5598 - Implement a new controller command "GETINFO status/fresh-relay-
5599 descs" to fetch a descriptor/extrainfo pair that was generated on
5600 demand just for the controller's use. Implements ticket 14784.
5602 o Minor features (DoS-resistance):
5603 - Make it harder for attackers to overload hidden services with
5604 introductions, by blocking multiple introduction requests on the
5605 same circuit. Resolves ticket 15515.
5607 o Minor features (geoip):
5608 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
5609 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
5612 o Minor features (HS popularity countermeasure):
5613 - To avoid leaking HS popularity, don't cycle the introduction point
5614 when we've handled a fixed number of INTRODUCE2 cells but instead
5615 cycle it when a random number of introductions is reached, thus
5616 making it more difficult for an attacker to find out the amount of
5617 clients that have used the introduction point for a specific HS.
5618 Closes ticket 15745.
5620 o Minor features (logging):
5621 - Include the Tor version in all LD_BUG log messages, since people
5622 tend to cut and paste those into the bugtracker. Implements
5625 o Minor features (pluggable transports):
5626 - When launching managed pluggable transports on Linux systems,
5627 attempt to have the kernel deliver a SIGTERM on tor exit if the
5628 pluggable transport process is still running. Resolves
5630 - When launching managed pluggable transports, setup a valid open
5631 stdin in the child process that can be used to detect if tor has
5632 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
5633 can be used by implementations to detect this new behavior.
5634 Resolves ticket 15435.
5636 o Minor features (testing):
5637 - Add a test to verify that the compiler does not eliminate our
5638 memwipe() implementation. Closes ticket 15377.
5639 - Add make rule `check-changes` to verify the format of changes
5640 files. Closes ticket 15180.
5641 - Add unit tests for control_event_is_interesting(). Add a compile-
5642 time check that the number of events doesn't exceed the capacity
5643 of control_event_t.event_mask. Closes ticket 15431, checks for
5644 bugs similar to 13085. Patch by "teor".
5645 - Command-line argument tests moved to Stem. Resolves ticket 14806.
5646 - Integrate the ntor, backtrace, and zero-length keys tests into the
5647 automake test suite. Closes ticket 15344.
5648 - Remove assertions during builds to determine Tor's test coverage.
5649 We don't want to trigger these even in assertions, so including
5650 them artificially makes our branch coverage look worse than it is.
5651 This patch provides the new test-stem-full and coverage-html-full
5652 configure options. Implements ticket 15400.
5654 o Minor bugfixes (build):
5655 - Improve out-of-tree builds by making non-standard rules work and
5656 clean up additional files and directories. Fixes bug 15053; bugfix
5659 o Minor bugfixes (command-line interface):
5660 - When "--quiet" is provided along with "--validate-config", do not
5661 write anything to stdout on success. Fixes bug 14994; bugfix
5663 - When complaining about bad arguments to "--dump-config", use
5666 o Minor bugfixes (configuration, unit tests):
5667 - Only add the default fallback directories when the DirAuthorities,
5668 AlternateDirAuthority, and FallbackDir directory config options
5669 are set to their defaults. The default fallback directory list is
5670 currently empty, this fix will only change tor's behavior when it
5671 has default fallback directories. Includes unit tests for
5672 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
5673 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
5675 o Minor bugfixes (correctness):
5676 - For correctness, avoid modifying a constant string in
5677 handle_control_postdescriptor. Fixes bug 15546; bugfix
5679 - Remove side-effects from tor_assert() calls. This was harmless,
5680 because we never disable assertions, but it is bad style and
5681 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
5684 o Minor bugfixes (hidden service):
5685 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
5686 a client authorized hidden service. Fixes bug 15823; bugfix
5688 - Remove an extraneous newline character from the end of hidden
5689 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
5691 o Minor bugfixes (interface):
5692 - Print usage information for --dump-config when it is used without
5693 an argument. Also, fix the error message to use different wording
5694 and add newline at the end. Fixes bug 15541; bugfix
5697 o Minor bugfixes (logs):
5698 - When building Tor under Clang, do not include an extra set of
5699 parentheses in log messages that include function names. Fixes bug
5700 15269; bugfix on every released version of Tor when compiled with
5701 recent enough Clang.
5703 o Minor bugfixes (network):
5704 - When attempting to use fallback technique for network interface
5705 lookup, disregard loopback and multicast addresses since they are
5706 unsuitable for public communications.
5708 o Minor bugfixes (statistics):
5709 - Disregard the ConnDirectionStatistics torrc options when Tor is
5710 not a relay since in that mode of operation no sensible data is
5711 being collected and because Tor might run into measurement hiccups
5712 when running as a client for some time, then becoming a relay.
5713 Fixes bug 15604; bugfix on 0.2.2.35.
5715 o Minor bugfixes (test networks):
5716 - When self-testing reachability, use ExtendAllowPrivateAddresses to
5717 determine if local/private addresses imply reachability. The
5718 previous fix used TestingTorNetwork, which implies
5719 ExtendAllowPrivateAddresses, but this excluded rare configurations
5720 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
5721 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
5722 issue discovered by CJ Ess.
5724 o Minor bugfixes (testing):
5725 - Check for matching value in server response in ntor_ref.py. Fixes
5726 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
5728 - Set the severity correctly when testing
5729 get_interface_addresses_ifaddrs() and
5730 get_interface_addresses_win32(), so that the tests fail gracefully
5731 instead of triggering an assertion. Fixes bug 15759; bugfix on
5732 0.2.6.3-alpha. Reported by Nicolas Derive.
5734 o Code simplification and refactoring:
5735 - Move the hacky fallback code out of get_interface_address6() into
5736 separate function and get it covered with unit-tests. Resolves
5738 - Refactor hidden service client-side cache lookup to intelligently
5739 report its various failure cases, and disentangle failure cases
5740 involving a lack of introduction points. Closes ticket 14391.
5741 - Use our own Base64 encoder instead of OpenSSL's, to allow more
5742 control over the output. Part of ticket 15652.
5745 - Improve the descriptions of statistics-related torrc options in
5746 the manpage to describe rationale and possible uses cases. Fixes
5748 - Improve the layout and formatting of ./configure --help messages.
5749 Closes ticket 15024. Patch from "cypherpunks".
5750 - Standardize on the term "server descriptor" in the manual page.
5751 Previously, we had used "router descriptor", "server descriptor",
5752 and "relay descriptor" interchangeably. Part of ticket 14987.
5755 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
5756 and always use the internal Base64 decoder. The internal decoder
5757 has been part of tor since 0.2.0.10-alpha, and no one should
5758 be using the OpenSSL one. Part of ticket 15652.
5759 - Remove the 'tor_strclear()' function; use memwipe() instead.
5760 Closes ticket 14922.
5763 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
5764 fingerprinting we now recommend pluggable transports; for forward-
5765 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
5766 - Remove the undocumented "--digests" command-line option. It
5767 complicated our build process, caused subtle build issues on
5768 multiple platforms, and is now redundant since we started
5769 including git version identifiers. Closes ticket 14742.
5770 - Tor no longer contains checks for ancient directory cache versions
5771 that didn't know about microdescriptors.
5772 - Tor no longer contains workarounds for stat files generated by
5773 super-old versions of Tor that didn't choose guards sensibly.
5776 Changes in version 0.2.4.27 - 2015-04-06
5777 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
5778 could be used by an attacker to crash hidden services, or crash clients
5779 visiting hidden services. Hidden services should upgrade as soon as
5780 possible; clients should upgrade whenever packages become available.
5782 This release also backports a simple improvement to make hidden
5783 services a bit less vulnerable to denial-of-service attacks.
5785 o Major bugfixes (security, hidden service):
5786 - Fix an issue that would allow a malicious client to trigger an
5787 assertion failure and halt a hidden service. Fixes bug 15600;
5788 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
5789 - Fix a bug that could cause a client to crash with an assertion
5790 failure when parsing a malformed hidden service descriptor. Fixes
5791 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
5793 o Minor features (DoS-resistance, hidden service):
5794 - Introduction points no longer allow multiple INTRODUCE1 cells to
5795 arrive on the same circuit. This should make it more expensive for
5796 attackers to overwhelm hidden services with introductions.
5797 Resolves ticket 15515.
5800 Changes in version 0.2.5.12 - 2015-04-06
5801 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
5802 could be used by an attacker to crash hidden services, or crash clients
5803 visiting hidden services. Hidden services should upgrade as soon as
5804 possible; clients should upgrade whenever packages become available.
5806 This release also backports a simple improvement to make hidden
5807 services a bit less vulnerable to denial-of-service attacks.
5809 o Major bugfixes (security, hidden service):
5810 - Fix an issue that would allow a malicious client to trigger an
5811 assertion failure and halt a hidden service. Fixes bug 15600;
5812 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
5813 - Fix a bug that could cause a client to crash with an assertion
5814 failure when parsing a malformed hidden service descriptor. Fixes
5815 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
5817 o Minor features (DoS-resistance, hidden service):
5818 - Introduction points no longer allow multiple INTRODUCE1 cells to
5819 arrive on the same circuit. This should make it more expensive for
5820 attackers to overwhelm hidden services with introductions.
5821 Resolves ticket 15515.
5824 Changes in version 0.2.6.7 - 2015-04-06
5825 Tor 0.2.6.7 fixes two security issues that could be used by an
5826 attacker to crash hidden services, or crash clients visiting hidden
5827 services. Hidden services should upgrade as soon as possible; clients
5828 should upgrade whenever packages become available.
5830 This release also contains two simple improvements to make hidden
5831 services a bit less vulnerable to denial-of-service attacks.
5833 o Major bugfixes (security, hidden service):
5834 - Fix an issue that would allow a malicious client to trigger an
5835 assertion failure and halt a hidden service. Fixes bug 15600;
5836 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
5837 - Fix a bug that could cause a client to crash with an assertion
5838 failure when parsing a malformed hidden service descriptor. Fixes
5839 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
5841 o Minor features (DoS-resistance, hidden service):
5842 - Introduction points no longer allow multiple INTRODUCE1 cells to
5843 arrive on the same circuit. This should make it more expensive for
5844 attackers to overwhelm hidden services with introductions.
5845 Resolves ticket 15515.
5846 - Decrease the amount of reattempts that a hidden service performs
5847 when its rendezvous circuits fail. This reduces the computational
5848 cost for running a hidden service under heavy load. Resolves
5852 Changes in version 0.2.6.6 - 2015-03-24
5853 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
5855 It adds numerous safety, security, correctness, and performance
5856 improvements. Client programs can be configured to use more kinds of
5857 sockets, AutomapHosts works better, the multithreading backend is
5858 improved, cell transmission is refactored, test coverage is much
5859 higher, more denial-of-service attacks are handled, guard selection is
5860 improved to handle long-term guards better, pluggable transports
5861 should work a bit better, and some annoying hidden service performance
5862 bugs should be addressed.
5864 o Minor bugfixes (portability):
5865 - Use the correct datatype in the SipHash-2-4 function to prevent
5866 compilers from assuming any sort of alignment. Fixes bug 15436;
5867 bugfix on 0.2.5.3-alpha.
5869 Changes in version 0.2.6.5-rc - 2015-03-18
5870 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
5871 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
5873 o Major bugfixes (client):
5874 - Avoid crashing when making certain configuration option changes on
5875 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
5878 o Major bugfixes (pluggable transports):
5879 - Initialize the extended OR Port authentication cookie before
5880 launching pluggable transports. This prevents a race condition
5881 that occured when server-side pluggable transports would cache the
5882 authentication cookie before it has been (re)generated. Fixes bug
5883 15240; bugfix on 0.2.5.1-alpha.
5885 o Major bugfixes (portability):
5886 - Do not crash on startup when running on Solaris. Fixes a bug
5887 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
5890 o Minor features (heartbeat):
5891 - On relays, report how many connections we negotiated using each
5892 version of the Tor link protocols. This information will let us
5893 know if removing support for very old versions of the Tor
5894 protocols is harming the network. Closes ticket 15212.
5896 o Code simplification and refactoring:
5897 - Refactor main loop to extract the 'loop' part. This makes it
5898 easier to run Tor under Shadow. Closes ticket 15176.
5901 Changes in version 0.2.5.11 - 2015-03-17
5902 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
5904 It backports several bugfixes from the 0.2.6 branch, including a
5905 couple of medium-level security fixes for relays and exit nodes.
5906 It also updates the list of directory authorities.
5908 o Directory authority changes:
5909 - Remove turtles as a directory authority.
5910 - Add longclaw as a new (v3) directory authority. This implements
5911 ticket 13296. This keeps the directory authority count at 9.
5912 - The directory authority Faravahar has a new IP address. This
5913 closes ticket 14487.
5915 o Major bugfixes (crash, OSX, security):
5916 - Fix a remote denial-of-service opportunity caused by a bug in
5917 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
5920 o Major bugfixes (relay, stability, possible security):
5921 - Fix a bug that could lead to a relay crashing with an assertion
5922 failure if a buffer of exactly the wrong layout was passed to
5923 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
5924 0.2.0.10-alpha. Patch from 'cypherpunks'.
5925 - Do not assert if the 'data' pointer on a buffer is advanced to the
5926 very end of the buffer; log a BUG message instead. Only assert if
5927 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
5929 o Major bugfixes (exit node stability):
5930 - Fix an assertion failure that could occur under high DNS load.
5931 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
5932 diagnosed and fixed by "cypherpunks".
5934 o Major bugfixes (Linux seccomp2 sandbox):
5935 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
5936 crash during attempts to call wait4. Fixes bug 15088; bugfix on
5937 0.2.5.1-alpha. Patch from "sanic".
5939 o Minor features (controller):
5940 - New "GETINFO bw-event-cache" to get information about recent
5941 bandwidth events. Closes ticket 14128. Useful for controllers to
5942 get recent bandwidth history after the fix for ticket 13988.
5944 o Minor features (geoip):
5945 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
5946 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
5949 o Minor bugfixes (client, automapping):
5950 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
5951 no value follows the option. Fixes bug 14142; bugfix on
5952 0.2.4.7-alpha. Patch by "teor".
5953 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
5954 14195; bugfix on 0.1.0.1-rc.
5956 o Minor bugfixes (compilation):
5957 - Build without warnings with the stock OpenSSL srtp.h header, which
5958 has a duplicate declaration of SSL_get_selected_srtp_profile().
5959 Fixes bug 14220; this is OpenSSL's bug, not ours.
5961 o Minor bugfixes (directory authority):
5962 - Allow directory authorities to fetch more data from one another if
5963 they find themselves missing lots of votes. Previously, they had
5964 been bumping against the 10 MB queued data limit. Fixes bug 14261;
5965 bugfix on 0.1.2.5-alpha.
5966 - Enlarge the buffer to read bwauth generated files to avoid an
5967 issue when parsing the file in dirserv_read_measured_bandwidths().
5968 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
5970 o Minor bugfixes (statistics):
5971 - Increase period over which bandwidth observations are aggregated
5972 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
5974 o Minor bugfixes (preventative security, C safety):
5975 - When reading a hexadecimal, base-32, or base-64 encoded value from
5976 a string, always overwrite the whole output buffer. This prevents
5977 some bugs where we would look at (but fortunately, not reveal)
5978 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
5982 Changes in version 0.2.4.26 - 2015-03-17
5983 Tor 0.2.4.26 includes an updated list of directory authorities. It
5984 also backports a couple of stability and security bugfixes from 0.2.5
5987 o Directory authority changes:
5988 - Remove turtles as a directory authority.
5989 - Add longclaw as a new (v3) directory authority. This implements
5990 ticket 13296. This keeps the directory authority count at 9.
5991 - The directory authority Faravahar has a new IP address. This
5992 closes ticket 14487.
5994 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
5995 - Fix an assertion failure that could occur under high DNS load.
5996 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
5997 diagnosed and fixed by "cypherpunks".
5999 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
6000 - Fix a bug that could lead to a relay crashing with an assertion
6001 failure if a buffer of exactly the wrong layout was passed to
6002 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
6003 0.2.0.10-alpha. Patch from 'cypherpunks'.
6004 - Do not assert if the 'data' pointer on a buffer is advanced to the
6005 very end of the buffer; log a BUG message instead. Only assert if
6006 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
6008 o Minor features (geoip):
6009 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
6010 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
6013 Changes in version 0.2.6.4-rc - 2015-03-09
6014 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
6015 attacker might be able to use in order to crash certain Tor
6016 directories. It also resolves some minor issues left over from, or
6017 introduced in, Tor 0.2.6.3-alpha or earlier.
6019 o Major bugfixes (crash, OSX, security):
6020 - Fix a remote denial-of-service opportunity caused by a bug in
6021 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
6024 o Major bugfixes (relay, stability, possible security):
6025 - Fix a bug that could lead to a relay crashing with an assertion
6026 failure if a buffer of exactly the wrong layout is passed to
6027 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
6028 0.2.0.10-alpha. Patch from "cypherpunks".
6029 - Do not assert if the 'data' pointer on a buffer is advanced to the
6030 very end of the buffer; log a BUG message instead. Only assert if
6031 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
6033 o Major bugfixes (FreeBSD IPFW transparent proxy):
6034 - Fix address detection with FreeBSD transparent proxies, when
6035 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
6038 o Major bugfixes (Linux seccomp2 sandbox):
6039 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
6040 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
6042 - Allow AF_UNIX hidden services to be used with the seccomp2
6043 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
6044 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
6045 crash during attempts to call wait4. Fixes bug 15088; bugfix on
6046 0.2.5.1-alpha. Patch from "sanic".
6048 o Minor features (controller):
6049 - Messages about problems in the bootstrap process now include
6050 information about the server we were trying to connect to when we
6051 noticed the problem. Closes ticket 15006.
6053 o Minor features (geoip):
6054 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
6055 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
6058 o Minor features (logs):
6059 - Quiet some log messages in the heartbeat and at startup. Closes
6062 o Minor bugfixes (certificate handling):
6063 - If an authority operator accidentally makes a signing certificate
6064 with a future publication time, do not discard its real signing
6065 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
6066 - Remove any old authority certificates that have been superseded
6067 for at least two days. Previously, we would keep superseded
6068 certificates until they expired, if they were published close in
6069 time to the certificate that superseded them. Fixes bug 11454;
6070 bugfix on 0.2.1.8-alpha.
6072 o Minor bugfixes (compilation):
6073 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
6075 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
6078 o Minor bugfixes (testing):
6079 - Fix endianness issues in unit test for resolve_my_address() to
6080 have it pass on big endian systems. Fixes bug 14980; bugfix on
6082 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
6083 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
6084 - When running the new 'make test-stem' target, use the configured
6085 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
6087 - When running the zero-length-keys tests, do not use the default
6088 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
6091 o Directory authority IP change:
6092 - The directory authority Faravahar has a new IP address. This
6093 closes ticket 14487.
6096 - Remove some lingering dead code that once supported mempools.
6097 Mempools were disabled by default in 0.2.5, and removed entirely
6098 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
6102 Changes in version 0.2.6.3-alpha - 2015-02-19
6103 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
6104 the 0.2.6.x series. It introduces support for more kinds of sockets,
6105 makes it harder to accidentally run an exit, improves our
6106 multithreading backend, incorporates several fixes for the
6107 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
6109 If no major regressions or security holes are found in this version,
6110 the next version will be a release candidate.
6112 o Deprecated versions:
6113 - Tor relays older than 0.2.4.18-rc are no longer allowed to
6114 advertise themselves on the network. Closes ticket 13555.
6116 o Major features (security, unix domain sockets):
6117 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
6118 applications can reach Tor without having to create AF_INET or
6119 AF_INET6 sockets, meaning they can completely disable their
6120 ability to make non-Tor network connections. To create a socket of
6121 this type, use "SocksPort unix:/path/to/socket". Implements
6123 - Support mapping hidden service virtual ports to AF_UNIX sockets.
6124 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
6125 Implements ticket 11485.
6127 o Major features (changed defaults):
6128 - Prevent relay operators from unintentionally running exits: When a
6129 relay is configured as an exit node, we now warn the user unless
6130 the "ExitRelay" option is set to 1. We warn even more loudly if
6131 the relay is configured with the default exit policy, since this
6132 can indicate accidental misconfiguration. Setting "ExitRelay 0"
6133 stops Tor from running as an exit relay. Closes ticket 10067.
6135 o Major features (directory system):
6136 - When downloading server- or microdescriptors from a directory
6137 server, we no longer launch multiple simultaneous requests to the
6138 same server. This reduces load on the directory servers,
6139 especially when directory guards are in use. Closes ticket 9969.
6140 - When downloading server- or microdescriptors over a tunneled
6141 connection, do not limit the length of our requests to what the
6142 Squid proxy is willing to handle. Part of ticket 9969.
6143 - Authorities can now vote on the correct digests and latest
6144 versions for different software packages. This allows packages
6145 that include Tor to use the Tor authority system as a way to get
6146 notified of updates and their correct digests. Implements proposal
6147 227. Closes ticket 10395.
6149 o Major features (guards):
6150 - Introduce the Guardfraction feature to improves load balancing on
6151 guard nodes. Specifically, it aims to reduce the traffic gap that
6152 guard nodes experience when they first get the Guard flag. This is
6153 a required step if we want to increase the guard lifetime to 9
6154 months or greater. Closes ticket 9321.
6156 o Major features (performance):
6157 - Make the CPU worker implementation more efficient by avoiding the
6158 kernel and lengthening pipelines. The original implementation used
6159 sockets to transfer data from the main thread to the workers, and
6160 didn't allow any thread to be assigned more than a single piece of
6161 work at once. The new implementation avoids communications
6162 overhead by making requests in shared memory, avoiding kernel IO
6163 where possible, and keeping more requests in flight at once.
6164 Implements ticket 9682.
6166 o Major features (relay):
6167 - Raise the minimum acceptable configured bandwidth rate for bridges
6168 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
6169 20 KiB/sec.) Closes ticket 13822.
6171 o Major bugfixes (exit node stability):
6172 - Fix an assertion failure that could occur under high DNS load.
6173 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
6174 diagnosed and fixed by "cypherpunks".
6176 o Major bugfixes (mixed relay-client operation):
6177 - When running as a relay and client at the same time (not
6178 recommended), if we decide not to use a new guard because we want
6179 to retry older guards, only close the locally-originating circuits
6180 passing through that guard. Previously we would close all the
6181 circuits through that guard. Fixes bug 9819; bugfix on
6182 0.2.1.1-alpha. Reported by "skruffy".
6184 o Minor features (build):
6185 - New --disable-system-torrc compile-time option to prevent Tor from
6186 looking for the system-wide torrc or torrc-defaults files.
6187 Resolves ticket 13037.
6189 o Minor features (controller):
6190 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
6191 events so controllers can observe circuit isolation inputs. Closes
6193 - ControlPort now supports the unix:/path/to/socket syntax as an
6194 alternative to the ControlSocket option, for consistency with
6195 SocksPort and HiddenServicePort. Closes ticket 14451.
6196 - New "GETINFO bw-event-cache" to get information about recent
6197 bandwidth events. Closes ticket 14128. Useful for controllers to
6198 get recent bandwidth history after the fix for ticket 13988.
6200 o Minor features (Denial of service resistance):
6201 - Count the total number of bytes used storing hidden service
6202 descriptors against the value of MaxMemInQueues. If we're low on
6203 memory, and more than 20% of our memory is used holding hidden
6204 service descriptors, free them until no more than 10% of our
6205 memory holds hidden service descriptors. Free the least recently
6206 fetched descriptors first. Resolves ticket 13806.
6207 - When we have recently been under memory pressure (over 3/4 of
6208 MaxMemInQueues is allocated), then allocate smaller zlib objects
6209 for small requests. Closes ticket 11791.
6211 o Minor features (geoip):
6212 - Update geoip and geoip6 files to the January 7 2015 Maxmind
6213 GeoLite2 Country database.
6215 o Minor features (guard nodes):
6216 - Reduce the time delay before saving guard status to disk from 10
6217 minutes to 30 seconds (or from one hour to 10 minutes if
6218 AvoidDiskWrites is set). Closes ticket 12485.
6220 o Minor features (hidden service):
6221 - Make Sybil attacks against hidden services harder by changing the
6222 minimum time required to get the HSDir flag from 25 hours up to 96
6223 hours. Addresses ticket 14149.
6224 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
6225 services to disable the anti-scanning feature introduced in
6226 0.2.6.2-alpha. With this option not set, a connection to an
6227 unlisted port closes the circuit. With this option set, only a
6228 RELAY_DONE cell is sent. Closes ticket 14084.
6230 o Minor features (interface):
6231 - Implement "-f -" command-line option to read torrc configuration
6232 from standard input, if you don't want to store the torrc file in
6233 the file system. Implements feature 13865.
6235 o Minor features (logging):
6236 - Add a count of unique clients to the bridge heartbeat message.
6237 Resolves ticket 6852.
6238 - Suppress "router info incompatible with extra info" message when
6239 reading extrainfo documents from cache. (This message got loud
6240 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
6242 - Elevate hidden service authorized-client message from DEBUG to
6243 INFO. Closes ticket 14015.
6245 o Minor features (stability):
6246 - Add assertions in our hash-table iteration code to check for
6247 corrupted values that could cause infinite loops. Closes
6250 o Minor features (systemd):
6251 - Various improvements and modernizations in systemd hardening
6252 support. Closes ticket 13805. Patch from Craig Andrews.
6254 o Minor features (testing networks):
6255 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
6256 and the default on a testing network to 2 minutes. Drop the
6257 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
6258 keep the default on a testing network at 30 seconds. This reduces
6259 HS bootstrap time to around 25 seconds. Also, change the default
6260 time in test-network.sh to match. Closes ticket 13401. Patch
6262 - Create TestingDirAuthVoteHSDir to correspond to
6263 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
6264 HSDir flag for the listed relays regardless of uptime or ORPort
6265 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
6266 Partial implementation for ticket 14067. Patch by "teor".
6268 o Minor features (tor2web mode):
6269 - Introduce the config option Tor2webRendezvousPoints, which allows
6270 clients in Tor2webMode to select a specific Rendezvous Point to be
6271 used in HS circuits. This might allow better performance for
6272 Tor2Web nodes. Implements ticket 12844.
6274 o Minor bugfixes (client DNS):
6275 - Report the correct cached DNS expiration times on SOCKS port or in
6276 DNS replies. Previously, we would report everything as "never
6277 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
6278 - Avoid a small memory leak when we find a cached answer for a
6279 reverse DNS lookup in a client-side DNS cache. (Remember, client-
6280 side DNS caching is off by default, and is not recommended.) Fixes
6281 bug 14259; bugfix on 0.2.0.1-alpha.
6283 o Minor bugfixes (client, automapping):
6284 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
6285 no value follows the option. Fixes bug 14142; bugfix on
6286 0.2.4.7-alpha. Patch by "teor".
6287 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
6288 14195; bugfix on 0.1.0.1-rc.
6289 - Prevent changes to other options from removing the wildcard value
6290 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
6292 - Allow MapAddress and AutomapHostsOnResolve to work together when
6293 an address is mapped into another address type (like .onion) that
6294 must be automapped at resolve time. Fixes bug 7555; bugfix
6297 o Minor bugfixes (client, bridges):
6298 - When we are using bridges and we had a network connectivity
6299 problem, only retry connecting to our currently configured
6300 bridges, not all bridges we know about and remember using. Fixes
6301 bug 14216; bugfix on 0.2.2.17-alpha.
6303 o Minor bugfixes (client, IPv6):
6304 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
6305 flag is not set; and not because the NoIPv4Traffic flag was set.
6306 Previously we'd looked at the NoIPv4Traffic flag for both types of
6307 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
6309 o Minor bugfixes (compilation):
6310 - The address of an array in the middle of a structure will always
6311 be non-NULL. clang recognises this and complains. Disable the
6312 tautologous and redundant check to silence this warning. Fixes bug
6313 14001; bugfix on 0.2.1.2-alpha.
6314 - Avoid warnings when building with systemd 209 or later. Fixes bug
6315 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
6316 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
6317 Addresses ticket 14188.
6318 - Build without warnings with the stock OpenSSL srtp.h header, which
6319 has a duplicate declaration of SSL_get_selected_srtp_profile().
6320 Fixes bug 14220; this is OpenSSL's bug, not ours.
6321 - Do not compile any code related to Tor2Web mode when Tor2Web mode
6322 is not enabled at compile time. Previously, this code was included
6323 in a disabled state. See discussion on ticket 12844.
6324 - Remove the --disable-threads configure option again. It was
6325 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
6326 14819; bugfix on 0.2.6.2-alpha.
6328 o Minor bugfixes (controller):
6329 - Report "down" in response to the "GETINFO entry-guards" command
6330 when relays are down with an unreachable_since value. Previously,
6331 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
6332 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
6333 14116; bugfix on 0.2.2.9-alpha.
6334 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
6335 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
6337 o Minor bugfixes (directory authority):
6338 - Allow directory authorities to fetch more data from one another if
6339 they find themselves missing lots of votes. Previously, they had
6340 been bumping against the 10 MB queued data limit. Fixes bug 14261;
6341 bugfix on 0.1.2.5-alpha.
6342 - Do not attempt to download extrainfo documents which we will be
6343 unable to validate with a matching server descriptor. Fixes bug
6344 13762; bugfix on 0.2.0.1-alpha.
6345 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
6346 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
6347 - Enlarge the buffer to read bwauth generated files to avoid an
6348 issue when parsing the file in dirserv_read_measured_bandwidths().
6349 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
6351 o Minor bugfixes (file handling):
6352 - Stop failing when key files are zero-length. Instead, generate new
6353 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
6354 on all versions of Tor. Patch by "teor".
6355 - Stop generating a fresh .old RSA onion key file when the .old file
6356 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
6357 - Avoid overwriting .old key files with empty key files.
6358 - Skip loading zero-length extrainfo store, router store, stats,
6359 state, and key files.
6360 - Avoid crashing when trying to reload a torrc specified as a
6361 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
6364 o Minor bugfixes (hidden services):
6365 - Close the introduction circuit when we have no more usable intro
6366 points, instead of waiting for it to time out. This also ensures
6367 that no follow-up HS descriptor fetch is triggered when the
6368 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
6369 - When fetching a hidden service descriptor for a down service that
6370 was recently up, do not keep refetching until we try the same
6371 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
6372 - Successfully launch Tor with a nonexistent hidden service
6373 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
6374 14106; bugfix on 0.2.6.2-alpha.
6376 o Minor bugfixes (logging):
6377 - Avoid crashing when there are more log domains than entries in
6378 domain_list. Bugfix on 0.2.3.1-alpha.
6379 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
6381 - Don't log messages to stdout twice when starting up. Fixes bug
6382 13993; bugfix on 0.2.6.1-alpha.
6384 o Minor bugfixes (parsing):
6385 - Stop accepting milliseconds (or other junk) at the end of
6386 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
6387 - Support two-number and three-number version numbers correctly, in
6388 case we change the Tor versioning system in the future. Fixes bug
6389 13661; bugfix on 0.0.8pre1.
6391 o Minor bugfixes (path counting):
6392 - When deciding whether the consensus lists any exit nodes, count
6393 the number listed in the consensus, not the number we have
6394 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
6395 - When deciding whether we have any exit nodes, only examine
6396 ExitNodes when the ExitNodes option is actually set. Fixes part of
6397 bug 14918; bugfix on 0.2.6.2-alpha.
6398 - Get rid of redundant and possibly scary warnings that we are
6399 missing directory information while we bootstrap. Fixes part of
6400 bug 14918; bugfix on 0.2.6.2-alpha.
6402 o Minor bugfixes (portability):
6403 - Fix the ioctl()-based network interface lookup code so that it
6404 will work on systems that have variable-length struct ifreq, for
6406 - Fix scheduler compilation on targets where char is unsigned. Fixes
6407 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
6409 o Minor bugfixes (sandbox):
6410 - Allow glibc fatal errors to be sent to stderr before Tor exits.
6411 Previously, glibc would try to write them to /dev/tty, and the
6412 sandbox would trap the call and make Tor exit prematurely. Fixes
6413 bug 14759; bugfix on 0.2.5.1-alpha.
6415 o Minor bugfixes (shutdown):
6416 - When shutting down, always call event_del() on lingering read or
6417 write events before freeing them. Otherwise, we risk double-frees
6418 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
6421 o Minor bugfixes (small memory leaks):
6422 - Avoid leaking memory when using IPv6 virtual address mappings.
6423 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
6426 o Minor bugfixes (statistics):
6427 - Increase period over which bandwidth observations are aggregated
6428 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
6430 o Minor bugfixes (systemd support):
6431 - Fix detection and operation of systemd watchdog. Fixes part of bug
6432 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
6433 - Run correctly under systemd with the RunAsDaemon option set. Fixes
6434 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
6435 - Inform the systemd supervisor about more changes in the Tor
6436 process status. Implements part of ticket 14141. Patch from
6438 - Cause the "--disable-systemd" option to actually disable systemd
6439 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
6442 o Minor bugfixes (TLS):
6443 - Check more thoroughly throughout the TLS code for possible
6444 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
6446 o Minor bugfixes (transparent proxy):
6447 - Use getsockname, not getsockopt, to retrieve the address for a
6448 TPROXY-redirected connection. Fixes bug 13796; bugfix
6451 o Code simplification and refactoring:
6452 - Move fields related to isolating and configuring client ports into
6453 a shared structure. Previously, they were duplicated across
6454 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
6455 to copy them correctly had been the cause of at least one bug in
6456 the past. Closes ticket 8546.
6457 - Refactor the get_interface_addresses_raw() doom-function into
6458 multiple smaller and simpler subfunctions. Cover the resulting
6459 subfunctions with unit-tests. Fixes a significant portion of
6461 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
6462 only for version <= 0.2.2.24 which is now deprecated. Closes
6464 - Remove a test for a long-defunct broken version-one
6468 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
6469 for writing the OpenBSD-specific tips. Resolves ticket 13702.
6470 - Make the tor-resolve documentation match its help string and its
6471 options. Resolves part of ticket 14325.
6472 - Log a more useful error message from tor-resolve when failing to
6473 look up a hidden service address. Resolves part of ticket 14325.
6475 o Downgraded warnings:
6476 - Don't warn when we've attempted to contact a relay using the wrong
6477 ntor onion key. Closes ticket 9635.
6480 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
6481 longer silently accepted as an alias for "ExitNodes".
6482 - The --enable-mempool and --enable-buf-freelists options, which
6483 were originally created to work around bad malloc implementations,
6484 no longer exist. They were off-by-default in 0.2.5. Closes
6488 - Make the checkdir/perms test complete successfully even if the
6489 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
6490 - Test that tor does not fail when key files are zero-length. Check
6491 that tor generates new keys, and overwrites the empty key files.
6492 - Test that tor generates new keys when keys are missing
6493 (existing behavior).
6494 - Test that tor does not overwrite key files that already contain
6495 data (existing behavior). Tests bug 13111. Patch by "teor".
6496 - New "make test-stem" target to run stem integration tests.
6497 Requires that the "STEM_SOURCE_DIR" environment variable be set.
6498 Closes ticket 14107.
6499 - Make the test_cmdline_args.py script work correctly on Windows.
6500 Patch from Gisle Vanem.
6501 - Move the slower unit tests into a new "./src/test/test-slow"
6502 binary that can be run independently of the other tests. Closes
6504 - Avoid undefined behavior when sampling huge values from the
6505 Laplace distribution. This made unittests fail on Raspberry Pi.
6506 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
6509 Changes in version 0.2.6.2-alpha - 2014-12-31
6510 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
6511 It introduces a major new backend for deciding when to send cells on
6512 channels, which should lead down the road to big performance
6513 increases. It contains security and statistics features for better
6514 work on hidden services, and numerous bugfixes.
6516 This release contains many new unit tests, along with major
6517 performance improvements for running testing networks using Chutney.
6518 Thanks to a series of patches contributed by "teor", testing networks
6519 should now bootstrap in seconds, rather than minutes.
6521 o Major features (relay, infrastructure):
6522 - Complete revision of the code that relays use to decide which cell
6523 to send next. Formerly, we selected the best circuit to write on
6524 each channel, but we didn't select among channels in any
6525 sophisticated way. Now, we choose the best circuits globally from
6526 among those whose channels are ready to deliver traffic.
6528 This patch implements a new inter-cmux comparison API, a global
6529 high/low watermark mechanism and a global scheduler loop for
6530 transmission prioritization across all channels as well as among
6531 circuits on one channel. This schedule is currently tuned to
6532 (tolerantly) avoid making changes in network performance, but it
6533 should form the basis for major circuit performance increases in
6534 the future. Code by Andrea; tuning by Rob Jansen; implements
6537 o Major features (hidden services):
6538 - Make HS port scanning more difficult by immediately closing the
6539 circuit when a user attempts to connect to a nonexistent port.
6540 Closes ticket 13667.
6541 - Add a HiddenServiceStatistics option that allows Tor relays to
6542 gather and publish statistics about the overall size and volume of
6543 hidden service usage. Specifically, when this option is turned on,
6544 an HSDir will publish an approximate number of hidden services
6545 that have published descriptors to it the past 24 hours. Also, if
6546 a relay has acted as a hidden service rendezvous point, it will
6547 publish the approximate amount of rendezvous cells it has relayed
6548 the past 24 hours. The statistics themselves are obfuscated so
6549 that the exact values cannot be derived. For more details see
6550 proposal 238, "Better hidden service stats from Tor relays". This
6551 feature is currently disabled by default. Implements feature 13192.
6553 o Major bugfixes (client, automap):
6554 - Repair automapping with IPv6 addresses. This automapping should
6555 have worked previously, but one piece of debugging code that we
6556 inserted to detect a regression actually caused the regression to
6557 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
6558 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
6561 o Major bugfixes (hidden services):
6562 - When closing an introduction circuit that was opened in parallel
6563 with others, don't mark the introduction point as unreachable.
6564 Previously, the first successful connection to an introduction
6565 point would make the other introduction points get marked as
6566 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
6568 o Directory authority changes:
6569 - Remove turtles as a directory authority.
6570 - Add longclaw as a new (v3) directory authority. This implements
6571 ticket 13296. This keeps the directory authority count at 9.
6573 o Major removed features:
6574 - Tor clients no longer support connecting to hidden services
6575 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
6576 option has been removed. (There shouldn't be any hidden services
6577 running these versions on the network.) Closes ticket 7803.
6579 o Minor features (client):
6580 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
6581 is enabled, reject requests with IP addresses as hostnames.
6582 Resolves ticket 13315.
6584 o Minor features (controller):
6585 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
6586 write an unscheduled heartbeat message to the log. Implements
6589 o Minor features (geoip):
6590 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
6593 o Minor features (hidden services):
6594 - When re-enabling the network, don't try to build introduction
6595 circuits until we have successfully built a circuit. This makes
6596 hidden services come up faster when the network is re-enabled.
6597 Patch from "akwizgran". Closes ticket 13447.
6598 - When we fail to retrieve a hidden service descriptor, send the
6599 controller an "HS_DESC FAILED" controller event. Implements
6601 - New HiddenServiceDirGroupReadable option to cause hidden service
6602 directories and hostname files to be created group-readable. Patch
6603 from "anon", David Stainton, and "meejah". Closes ticket 11291.
6605 o Minor features (systemd):
6606 - Where supported, when running with systemd, report successful
6607 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
6608 - When running with systemd, support systemd watchdog messages. Part
6609 of ticket 11016. Patch by Michael Scherer.
6611 o Minor features (transparent proxy):
6612 - Update the transparent proxy option checks to allow for both ipfw
6613 and pf on OS X. Closes ticket 14002.
6614 - Use the correct option when using IPv6 with transparent proxy
6615 support on Linux. Resolves 13808. Patch by Francisco Blas
6618 o Minor bugfixes (preventative security, C safety):
6619 - When reading a hexadecimal, base-32, or base-64 encoded value from
6620 a string, always overwrite the whole output buffer. This prevents
6621 some bugs where we would look at (but fortunately, not reveal)
6622 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
6624 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
6625 just the part that's used. This makes it harder for data leak bugs
6626 to occur in the event of other programming failures. Resolves
6629 o Minor bugfixes (client, microdescriptors):
6630 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
6631 computing which microdescriptors to download. This keeps us from
6632 erroneous download behavior if two microdescriptor digests ever
6633 have the same first 160 bits. Fixes part of bug 13399; bugfix
6635 - Reset a router's status if its microdescriptor digest changes,
6636 even if the first 160 bits remain the same. Fixes part of bug
6637 13399; bugfix on 0.2.3.1-alpha.
6639 o Minor bugfixes (compilation):
6640 - Silence clang warnings under --enable-expensive-hardening,
6641 including implicit truncation of 64 bit values to 32 bit, const
6642 char assignment to self, tautological compare, and additional
6643 parentheses around equality tests. Fixes bug 13577; bugfix
6645 - Fix a clang warning about checking whether an address in the
6646 middle of a structure is NULL. Fixes bug 14001; bugfix
6649 o Minor bugfixes (hidden services):
6650 - Correctly send a controller event when we find that a rendezvous
6651 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
6652 - Pre-check directory permissions for new hidden-services to avoid
6653 at least one case of "Bug: Acting on config options left us in a
6654 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
6655 - When adding a new hidden service (for example, via SETCONF), Tor
6656 no longer congratulates the user for running a relay. Fixes bug
6657 13941; bugfix on 0.2.6.1-alpha.
6658 - When fetching hidden service descriptors, we now check not only
6659 for whether we got the hidden service we had in mind, but also
6660 whether we got the particular descriptors we wanted. This prevents
6661 a class of inefficient but annoying DoS attacks by hidden service
6662 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
6665 o Minor bugfixes (Linux seccomp2 sandbox):
6666 - Make transparent proxy support work along with the seccomp2
6667 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
6668 by Francisco Blas Izquierdo Riera.
6669 - Fix a memory leak in tor-resolve when running with the sandbox
6670 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
6672 o Minor bugfixes (logging):
6673 - Downgrade warnings about RSA signature failures to info log level.
6674 Emit a warning when an extra info document is found incompatible
6675 with a corresponding router descriptor. Fixes bug 9812; bugfix
6677 - Make connection_ap_handshake_attach_circuit() log the circuit ID
6678 correctly. Fixes bug 13701; bugfix on 0.0.6.
6680 o Minor bugfixes (misc):
6681 - Stop allowing invalid address patterns like "*/24" that contain
6682 both a wildcard address and a bit prefix length. This affects all
6683 our address-range parsing code. Fixes bug 7484; bugfix
6686 o Minor bugfixes (testing networks, fast startup):
6687 - Allow Tor to build circuits using a consensus with no exits. If
6688 the consensus has no exits (typical of a bootstrapping test
6689 network), allow Tor to build circuits once enough descriptors have
6690 been downloaded. This assists in bootstrapping a testing Tor
6691 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
6693 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
6694 header to directory servers. This allows us to obtain consensuses
6695 promptly when the consensus interval is very short. This assists
6696 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
6697 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
6698 - Stop assuming that private addresses are local when checking
6699 reachability in a TestingTorNetwork. Instead, when testing, assume
6700 all OR connections are remote. (This is necessary due to many test
6701 scenarios running all relays on localhost.) This assists in
6702 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
6703 0.1.0.1-rc. Patch by "teor".
6704 - Avoid building exit circuits from a consensus with no exits. Now
6705 thanks to our fix for 13718, we accept a no-exit network as not
6706 wholly lost, but we need to remember not to try to build exit
6707 circuits on it. Closes ticket 13814; patch by "teor".
6708 - Stop requiring exits to have non-zero bandwithcapacity in a
6709 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
6710 ignore exit bandwidthcapacity. This assists in bootstrapping a
6711 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
6712 on 0.2.0.3-alpha. Patch by "teor".
6713 - Add "internal" to some bootstrap statuses when no exits are
6714 available. If the consensus does not contain Exits, Tor will only
6715 build internal circuits. In this case, relevant statuses will
6716 contain the word "internal" as indicated in the Tor control-
6717 spec.txt. When bootstrap completes, Tor will be ready to build
6718 internal circuits. If a future consensus contains Exits, exit
6719 circuits may become available. Fixes part of bug 13718; bugfix on
6720 0.2.4.10-alpha. Patch by "teor".
6721 - Decrease minimum consensus interval to 10 seconds when
6722 TestingTorNetwork is set, or 5 seconds for the first consensus.
6723 Fix assumptions throughout the code that assume larger intervals.
6724 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
6726 - Avoid excluding guards from path building in minimal test
6727 networks, when we're in a test network and excluding guards would
6728 exclude all relays. This typically occurs in incredibly small tor
6729 networks, and those using "TestingAuthVoteGuard *". Fixes part of
6730 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
6732 o Code simplification and refactoring:
6733 - Stop using can_complete_circuits as a global variable; access it
6734 with a function instead.
6735 - Avoid using operators directly as macro arguments: this lets us
6736 apply coccinelle transformations to our codebase more directly.
6737 Closes ticket 13172.
6738 - Combine the functions used to parse ClientTransportPlugin and
6739 ServerTransportPlugin into a single function. Closes ticket 6456.
6740 - Add inline functions and convenience macros for inspecting channel
6741 state. Refactor the code to use convenience macros instead of
6742 checking channel state directly. Fixes issue 7356.
6743 - Document all members of was_router_added_t and rename
6744 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
6745 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
6746 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
6747 constant instead of hardcoded value. Fixes issue 13840.
6748 - Refactor our generic strmap and digestmap types into a single
6749 implementation, so that we can add a new digest256map
6753 - Document the bridge-authority-only 'networkstatus-bridges' file.
6754 Closes ticket 13713; patch from "tom".
6755 - Fix typo in PredictedPortsRelevanceTime option description in
6756 manpage. Resolves issue 13707.
6757 - Stop suggesting that users specify relays by nickname: it isn't a
6758 good idea. Also, properly cross-reference how to specify relays in
6759 all parts of manual documenting options that take a list of
6760 relays. Closes ticket 13381.
6761 - Clarify the HiddenServiceDir option description in manpage to make
6762 it clear that relative paths are taken with respect to the current
6763 working directory. Also clarify that this behavior is not
6764 guaranteed to remain indefinitely. Fixes issue 13913.
6767 - New tests for many parts of channel, relay, and circuitmux
6768 functionality. Code by Andrea; part of 9262.
6769 - New tests for parse_transport_line(). Part of ticket 6456.
6770 - In the unit tests, use chgrp() to change the group of the unit
6771 test temporary directory to the current user, so that the sticky
6772 bit doesn't interfere with tests that check directory groups.
6774 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
6778 Changes in version 0.2.6.1-alpha - 2014-10-30
6779 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
6780 includes numerous code cleanups and new tests, and fixes a large
6781 number of annoying bugs. Out-of-memory conditions are handled better
6782 than in 0.2.5, pluggable transports have improved proxy support, and
6783 clients now use optimistic data for contacting hidden services. Also,
6784 we are now more robust to changes in what we consider a parseable
6785 directory object, so that tightening restrictions does not have a risk
6786 of introducing infinite download loops.
6788 This is the first alpha release in a new series, so expect there to be
6789 bugs. Users who would rather test out a more stable branch should stay
6790 with 0.2.5.x for now.
6792 o New compiler and system requirements:
6793 - Tor 0.2.6.x requires that your compiler support more of the C99
6794 language standard than before. The 'configure' script now detects
6795 whether your compiler supports C99 mid-block declarations and
6796 designated initializers. If it does not, Tor will not compile.
6798 We may revisit this requirement if it turns out that a significant
6799 number of people need to build Tor with compilers that don't
6800 bother implementing a 15-year-old standard. Closes ticket 13233.
6801 - Tor no longer supports systems without threading support. When we
6802 began working on Tor, there were several systems that didn't have
6803 threads, or where the thread support wasn't able to run the
6804 threads of a single process on multiple CPUs. That no longer
6805 holds: every system where Tor needs to run well now has threading
6806 support. Resolves ticket 12439.
6808 o Removed platform support:
6809 - We no longer include special code to build on Windows CE; as far
6810 as we know, nobody has used Tor on Windows CE in a very long time.
6811 Closes ticket 11446.
6813 o Major features (bridges):
6814 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
6815 transports if they are configured via the "TOR_PT_PROXY"
6816 environment variable. Implements proposal 232. Resolves
6819 o Major features (client performance, hidden services):
6820 - Allow clients to use optimistic data when connecting to a hidden
6821 service, which should remove a round-trip from hidden service
6822 initialization. See proposal 181 for details. Implements
6825 o Major features (directory system):
6826 - Upon receiving an unparseable directory object, if its digest
6827 matches what we expected, then don't try to download it again.
6828 Previously, when we got a descriptor we didn't like, we would keep
6829 trying to download it over and over. Closes ticket 11243.
6831 o Major features (sample torrc):
6832 - Add a new, infrequently-changed "torrc.minimal". This file is
6833 similar to torrc.sample, but it will change as infrequently as
6834 possible, for the benefit of users whose systems prompt them for
6835 intervention whenever a default configuration file is changed.
6836 Making this change allows us to update torrc.sample to be a more
6837 generally useful "sample torrc".
6839 o Major bugfixes (directory authorities):
6840 - Do not assign the HSDir flag to relays if they are not Valid, or
6841 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
6843 o Major bugfixes (directory bandwidth performance):
6844 - Don't flush the zlib buffer aggressively when compressing
6845 directory information for clients. This should save about 7% of
6846 the bandwidth currently used for compressed descriptors and
6847 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
6849 o Minor features (security, memory wiping):
6850 - Ensure we securely wipe keys from memory after
6851 crypto_digest_get_digest and init_curve25519_keypair_from_file
6852 have finished using them. Resolves ticket 13477.
6854 o Minor features (security, out-of-memory handling):
6855 - When handling an out-of-memory condition, allocate less memory for
6856 temporary data structures. Fixes issue 10115.
6857 - When handling an out-of-memory condition, consider more types of
6858 buffers, including those on directory connections, and zlib
6859 buffers. Resolves ticket 11792.
6862 - When identity keypair is generated for first time, log a
6863 congratulatory message that links to the new relay lifecycle
6864 document. Implements feature 10427.
6866 o Minor features (client):
6867 - Clients are now willing to send optimistic data (before they
6868 receive a 'connected' cell) to relays of any version. (Relays
6869 without support for optimistic data are no longer supported on the
6870 Tor network.) Resolves ticket 13153.
6872 o Minor features (directory authorities):
6873 - Don't list relays with a bandwidth estimate of 0 in the consensus.
6874 Implements a feature proposed during discussion of bug 13000.
6875 - In tor-gencert, report an error if the user provides the same
6876 argument more than once.
6877 - If a directory authority can't find a best consensus method in the
6878 votes that it holds, it now falls back to its favorite consensus
6879 method. Previously, it fell back to method 1. Neither of these is
6880 likely to get enough signatures, but "fall back to favorite"
6881 doesn't require us to maintain support an obsolete consensus
6882 method. Implements part of proposal 215.
6884 o Minor features (logging):
6885 - On Unix-like systems, you can now use named pipes as the target of
6886 the Log option, and other options that try to append to files.
6887 Closes ticket 12061. Patch from "carlo von lynX".
6888 - When opening a log file at startup, send it every log message that
6889 we generated between startup and opening it. Previously, log
6890 messages that were generated before opening the log file were only
6891 logged to stdout. Closes ticket 6938.
6892 - Add a TruncateLogFile option to overwrite logs instead of
6893 appending to them. Closes ticket 5583.
6895 o Minor features (portability, Solaris):
6896 - Threads are no longer disabled by default on Solaris; we believe
6897 that the versions of Solaris with broken threading support are all
6898 obsolete by now. Resolves ticket 9495.
6900 o Minor features (relay):
6901 - Re-check our address after we detect a changed IP address from
6902 getsockname(). This ensures that the controller command "GETINFO
6903 address" will report the correct value. Resolves ticket 11582.
6905 - A new AccountingRule option lets Relays set whether they'd like
6906 AccountingMax to be applied separately to inbound and outbound
6907 traffic, or applied to the sum of inbound and outbound traffic.
6908 Resolves ticket 961. Patch by "chobe".
6910 o Minor features (testing networks):
6911 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
6912 the "Exit" flag regardless of their uptime, bandwidth, or exit
6913 policy. TestingTorNetwork must be set for this option to have any
6914 effect. Previously, authorities would take up to 35 minutes to
6915 give nodes the Exit flag in a test network. Partially implements
6918 o Minor features (validation):
6919 - Check all date/time values passed to tor_timegm and
6920 parse_rfc1123_time for validity, taking leap years into account.
6921 Improves HTTP header validation. Implemented with bug 13476.
6922 - In correct_tm(), limit the range of values returned by system
6923 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
6924 This means we don't have to deal with negative or too large dates,
6925 even if a clock is wrong. Otherwise we might fail to read a file
6926 written by us which includes such a date. Fixes bug 13476.
6928 o Minor bugfixes (bridge clients):
6929 - When configured to use a bridge without an identity digest (not
6930 recommended), avoid launching an extra channel to it when
6931 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
6933 o Minor bugfixes (bridges):
6934 - When DisableNetwork is set, do not launch pluggable transport
6935 plugins, and if any are running, terminate them. Fixes bug 13213;
6936 bugfix on 0.2.3.6-alpha.
6938 o Minor bugfixes (C correctness):
6939 - Fix several instances of possible integer overflow/underflow/NaN.
6940 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
6942 - In circuit_build_times_calculate_timeout() in circuitstats.c,
6943 avoid dividing by zero in the pareto calculations. This traps
6944 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
6946 - Fix an integer overflow in format_time_interval(). Fixes bug
6947 13393; bugfix on 0.2.0.10-alpha.
6948 - Set the correct day of year value when the system's localtime(_r)
6949 or gmtime(_r) functions fail to set struct tm. Not externally
6950 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
6951 - Avoid unlikely signed integer overflow in tor_timegm on systems
6952 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
6954 o Minor bugfixes (client):
6955 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
6956 BadExit flag are not considered worthy candidates. Fixes bug
6957 13066; bugfix on 0.1.2.3-alpha.
6958 - Use the consensus schedule for downloading consensuses, and not
6959 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
6960 - Handle unsupported or malformed SOCKS5 requests properly by
6961 responding with the appropriate error message before closing the
6962 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
6964 o Minor bugfixes (client, torrc):
6965 - Stop modifying the value of our DirReqStatistics torrc option just
6966 because we're not a bridge or relay. This bug was causing Tor
6967 Browser users to write "DirReqStatistics 0" in their torrc files
6968 as if they had chosen to change the config. Fixes bug 4244; bugfix
6970 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
6971 that our options have changed every time we SIGHUP. Fixes bug
6972 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
6974 o Minor bugfixes (controller):
6975 - Return an error when the second or later arguments of the
6976 "setevents" controller command are invalid events. Previously we
6977 would return success while silently skipping invalid events. Fixes
6978 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
6980 o Minor bugfixes (directory system):
6981 - Always believe that v3 directory authorities serve extra-info
6982 documents, whether they advertise "caches-extra-info" or not.
6983 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
6984 - When running as a v3 directory authority, advertise that you serve
6985 extra-info documents so that clients who want them can find them
6986 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
6987 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
6988 Previously, directories offering BRIDGE_DIRINFO and some other
6989 flag (i.e. microdescriptors or extrainfo) would be ignored when
6990 looking for bridges. Partially fixes bug 13163; bugfix
6993 o Minor bugfixes (networking):
6994 - Check for orconns and use connection_or_close_for_error() rather
6995 than connection_mark_for_close() directly in the getsockopt()
6996 failure case of connection_handle_write_impl(). Fixes bug 11302;
6997 bugfix on 0.2.4.4-alpha.
6999 o Minor bugfixes (relay):
7000 - When generating our family list, remove spaces from around the
7001 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
7002 - If our previous bandwidth estimate was 0 bytes, allow publishing a
7003 new relay descriptor immediately. Fixes bug 13000; bugfix
7006 o Minor bugfixes (testing networks):
7007 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
7008 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
7009 - Stop using the default authorities in networks which provide both
7010 AlternateDirAuthority and AlternateBridgeAuthority. Partially
7011 fixes bug 13163; bugfix on 0.2.0.13-alpha.
7013 o Minor bugfixes (testing):
7014 - Stop spawn test failures due to a race condition between the
7015 SIGCHLD handler updating the process status, and the test reading
7016 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
7018 o Minor bugfixes (testing, Windows):
7019 - Avoid passing an extra backslash when creating a temporary
7020 directory for running the unit tests on Windows. Fixes bug 12392;
7021 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
7023 o Minor bugfixes (windows):
7024 - Remove code to special-case handling of NTE_BAD_KEYSET when
7025 acquiring windows CryptoAPI context. This error can't actually
7026 occur for the parameters we're providing. Fixes bug 10816; bugfix
7029 o Minor bugfixes (zlib):
7030 - Avoid truncating a zlib stream when trying to finalize it with an
7031 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
7034 - Allow our configure script to build correctly with autoconf 2.62
7035 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
7036 - Improve the error message from ./configure to make it clear that
7037 when asciidoc has not been found, the user will have to either add
7038 --disable-asciidoc argument or install asciidoc. Resolves
7041 o Code simplification and refactoring:
7042 - Change the entry_is_live() function to take named bitfield
7043 elements instead of an unnamed list of booleans. Closes
7045 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
7046 Resolves ticket 12205.
7047 - Use calloc and reallocarray functions instead of multiply-
7048 then-malloc. This makes it less likely for us to fall victim to an
7049 integer overflow attack when allocating. Resolves ticket 12855.
7050 - Use the standard macro name SIZE_MAX, instead of our
7052 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
7053 functions which take them as arguments. Replace 0 with NO_DIRINFO
7054 in a function call for clarity. Seeks to prevent future issues
7056 - Avoid 4 null pointer errors under clang static analysis by using
7057 tor_assert() to prove that the pointers aren't null. Fixes
7059 - Rework the API of policies_parse_exit_policy() to use a bitmask to
7060 represent parsing options, instead of a confusing mess of
7061 booleans. Resolves ticket 8197.
7062 - Introduce a helper function to parse ExitPolicy in
7063 or_options_t structure.
7066 - Add a doc/TUNING document with tips for handling large numbers of
7067 TCP connections when running busy Tor relay. Update the warning
7068 message to point to this file when running out of sockets
7069 operating system is allowing to use simultaneously. Resolves
7073 - We no longer remind the user about configuration options that have
7074 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
7075 - Remove our old, non-weighted bandwidth-based node selection code.
7076 Previously, we used it as a fallback when we couldn't perform
7077 weighted bandwidth-based node selection. But that would only
7078 happen in the cases where we had no consensus, or when we had a
7079 consensus generated by buggy or ancient directory authorities. In
7080 either case, it's better to use the more modern, better maintained
7081 algorithm, with reasonable defaults for the weights. Closes
7083 - Remove the --disable-curve25519 configure option. Relays and
7084 clients now are required to support curve25519 and the
7086 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
7087 used to be deprecated synonyms for "StrictNodes", are now marked
7088 obsolete. Resolves ticket 12226.
7089 - Clients don't understand the BadDirectory flag in the consensus
7090 anymore, and ignore it.
7093 - Refactor the function that chooses guard nodes so that it can more
7094 easily be tested; write some tests for it.
7095 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
7096 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
7097 - Create unit tests for format_time_interval(). With bug 13393.
7098 - Add unit tests for tor_timegm signed overflow, tor_timegm and
7099 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
7100 tests (visible) fixes in bug 13476.
7101 - Add a "coverage-html" make target to generate HTML-visualized
7102 coverage results when building with --enable-coverage. (Requires
7103 lcov.) Patch from Kevin Murray.
7104 - Enable the backtrace handler (where supported) when running the
7106 - Revise all unit tests that used the legacy test_* macros to
7107 instead use the recommended tt_* macros. This patch was generated
7108 with coccinelle, to avoid manual errors. Closes ticket 13119.
7110 o Distribution (systemd):
7111 - systemd unit file: only allow tor to write to /var/lib/tor and
7112 /var/log/tor. The rest of the filesystem is accessible for reading
7113 only. Patch by intrigeri; resolves ticket 12751.
7114 - systemd unit file: ensure that the process and all its children
7115 can never gain new privileges. Patch by intrigeri; resolves
7117 - systemd unit file: set up /var/run/tor as writable for the Tor
7118 service. Patch by intrigeri; resolves ticket 13196.
7120 o Removed features (directory authorities):
7121 - Remove code that prevented authorities from listing Tor relays
7122 affected by CVE-2011-2769 as guards. These relays are already
7123 rejected altogether due to the minimum version requirement of
7124 0.2.3.16-alpha. Closes ticket 13152.
7125 - The "AuthDirRejectUnlisted" option no longer has any effect, as
7126 the fingerprints file (approved-routers) has been deprecated.
7127 - Directory authorities do not support being Naming dirauths anymore.
7128 The "NamingAuthoritativeDir" config option is now obsolete.
7129 - Directory authorities do not support giving out the BadDirectory
7131 - Directory authorities no longer advertise or support consensus
7132 methods 1 through 12 inclusive. These consensus methods were
7133 obsolete and/or insecure: maintaining the ability to support them
7134 served no good purpose. Implements part of proposal 215; closes
7137 o Testing (test-network.sh):
7138 - Stop using "echo -n", as some shells' built-in echo doesn't
7139 support "-n". Instead, use "/bin/echo -n". Partially fixes
7141 - Stop an apparent test-network hang when used with make -j2. Fixes
7143 - Add a --delay option to test-network.sh, which configures the
7144 delay before the chutney network tests for data transmission.
7145 Partially implements ticket 13161.
7148 Changes in version 0.2.5.10 - 2014-10-24
7149 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
7151 It adds several new security features, including improved
7152 denial-of-service resistance for relays, new compiler hardening
7153 options, and a system-call sandbox for hardened installations on Linux
7154 (requires seccomp2). The controller protocol has several new features,
7155 resolving IPv6 addresses should work better than before, and relays
7156 should be a little more CPU-efficient. We've added support for more
7157 OpenBSD and FreeBSD transparent proxy types. We've improved the build
7158 system and testing infrastructure to allow unit testing of more parts
7159 of the Tor codebase. Finally, we've addressed several nagging pluggable
7160 transport usability issues, and included numerous other small bugfixes
7161 and features mentioned below.
7163 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
7164 have accumulated many known flaws; everyone should upgrade.
7166 o Deprecated versions:
7167 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
7168 attention for some while.
7171 Changes in version 0.2.5.9-rc - 2014-10-20
7172 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
7173 series. It disables SSL3 in response to the recent "POODLE" attack
7174 (even though POODLE does not affect Tor). It also works around a crash
7175 bug caused by some operating systems' response to the "POODLE" attack
7176 (which does affect Tor). It also contains a few miscellaneous fixes.
7178 o Major security fixes:
7179 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
7180 today support TLS 1.0 or later, so we can safely turn off support
7181 for this old (and insecure) protocol. Fixes bug 13426.
7183 o Major bugfixes (openssl bug workaround):
7184 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
7185 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
7186 13471. This is a workaround for an OpenSSL bug.
7189 - Disable the sandbox name resolver cache when running tor-resolve:
7190 tor-resolve doesn't use the sandbox code, and turning it on was
7191 breaking attempts to do tor-resolve on a non-default server on
7192 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
7194 o Compilation fixes:
7195 - Build and run correctly on systems like OpenBSD-current that have
7196 patched OpenSSL to remove get_cipher_by_char and/or its
7197 implementations. Fixes issue 13325.
7199 o Downgraded warnings:
7200 - Downgrade the severity of the 'unexpected sendme cell from client'
7201 from 'warn' to 'protocol warning'. Closes ticket 8093.
7204 Changes in version 0.2.4.25 - 2014-10-20
7205 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
7206 (even though POODLE does not affect Tor). It also works around a crash
7207 bug caused by some operating systems' response to the "POODLE" attack
7208 (which does affect Tor).
7210 o Major security fixes (also in 0.2.5.9-rc):
7211 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
7212 today support TLS 1.0 or later, so we can safely turn off support
7213 for this old (and insecure) protocol. Fixes bug 13426.
7215 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
7216 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
7217 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
7218 13471. This is a workaround for an OpenSSL bug.
7221 Changes in version 0.2.5.8-rc - 2014-09-22
7222 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
7223 series. It fixes a bug that affects consistency and speed when
7224 connecting to hidden services, and it updates the location of one of
7225 the directory authorities.
7228 - Clients now send the correct address for their chosen rendezvous
7229 point when trying to access a hidden service. They used to send
7230 the wrong address, which would still work some of the time because
7231 they also sent the identity digest of the rendezvous point, and if
7232 the hidden service happened to try connecting to the rendezvous
7233 point from a relay that already had a connection open to it,
7234 the relay would reuse that connection. Now connections to hidden
7235 services should be more robust and faster. Also, this bug meant
7236 that clients were leaking to the hidden service whether they were
7237 on a little-endian (common) or big-endian (rare) system, which for
7238 some users might have reduced their anonymity. Fixes bug 13151;
7239 bugfix on 0.2.1.5-alpha.
7241 o Directory authority changes:
7242 - Change IP address for gabelmoo (v3 directory authority).
7245 Changes in version 0.2.4.24 - 2014-09-22
7246 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
7247 connecting to hidden services, and it updates the location of one of
7248 the directory authorities.
7251 - Clients now send the correct address for their chosen rendezvous
7252 point when trying to access a hidden service. They used to send
7253 the wrong address, which would still work some of the time because
7254 they also sent the identity digest of the rendezvous point, and if
7255 the hidden service happened to try connecting to the rendezvous
7256 point from a relay that already had a connection open to it,
7257 the relay would reuse that connection. Now connections to hidden
7258 services should be more robust and faster. Also, this bug meant
7259 that clients were leaking to the hidden service whether they were
7260 on a little-endian (common) or big-endian (rare) system, which for
7261 some users might have reduced their anonymity. Fixes bug 13151;
7262 bugfix on 0.2.1.5-alpha.
7264 o Directory authority changes:
7265 - Change IP address for gabelmoo (v3 directory authority).
7267 o Minor features (geoip):
7268 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
7272 Changes in version 0.2.5.7-rc - 2014-09-11
7273 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
7274 release series, and some long-standing bugs related to ORPort reachability
7275 testing and failure to send CREATE cells. It is the first release
7276 candidate for the Tor 0.2.5.x series.
7278 o Major bugfixes (client, startup):
7279 - Start making circuits as soon as DisabledNetwork is turned off.
7280 When Tor started with DisabledNetwork set, it would correctly
7281 conclude that it shouldn't build circuits, but it would mistakenly
7282 cache this conclusion, and continue believing it even when
7283 DisableNetwork is set to 0. Fixes the bug introduced by the fix
7284 for bug 11200; bugfix on 0.2.5.4-alpha.
7285 - Resume expanding abbreviations for command-line options. The fix
7286 for bug 4647 accidentally removed our hack from bug 586 that
7287 rewrote HashedControlPassword to __HashedControlSessionPassword
7288 when it appears on the commandline (which allowed the user to set
7289 her own HashedControlPassword in the torrc file while the
7290 controller generates a fresh session password for each run). Fixes
7291 bug 12948; bugfix on 0.2.5.1-alpha.
7292 - Warn about attempts to run hidden services and relays in the same
7293 process: that's probably not a good idea. Closes ticket 12908.
7295 o Major bugfixes (relay):
7296 - Avoid queuing or sending destroy cells for circuit ID zero when we
7297 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
7298 Found and fixed by "cypherpunks".
7299 - Fix ORPort reachability detection on relays running behind a
7300 proxy, by correctly updating the "local" mark on the controlling
7301 channel when changing the address of an or_connection_t after the
7302 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
7304 o Minor features (bridge):
7305 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
7306 cookie file for the ExtORPort g+r by default.
7308 o Minor features (geoip):
7309 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
7312 o Minor bugfixes (logging):
7313 - Reduce the log severity of the "Pluggable transport proxy does not
7314 provide any needed transports and will not be launched." message,
7315 since Tor Browser includes several ClientTransportPlugin lines in
7316 its torrc-defaults file, leading every Tor Browser user who looks
7317 at her logs to see these notices and wonder if they're dangerous.
7318 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
7319 - Downgrade "Unexpected onionskin length after decryption" warning
7320 to a protocol-warn, since there's nothing relay operators can do
7321 about a client that sends them a malformed create cell. Resolves
7322 bug 12996; bugfix on 0.0.6rc1.
7323 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
7324 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
7325 - When logging information about an EXTEND2 or EXTENDED2 cell, log
7326 their names correctly. Fixes part of bug 12700; bugfix
7328 - When logging information about a relay cell whose command we don't
7329 recognize, log its command as an integer. Fixes part of bug 12700;
7330 bugfix on 0.2.1.10-alpha.
7331 - Escape all strings from the directory connection before logging
7332 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
7334 o Minor bugfixes (controller):
7335 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
7336 bug 12864; bugfix on 0.2.5.1-alpha.
7337 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
7338 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
7341 o Minor bugfixes (compilation):
7342 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
7343 bugfix on 0.2.5.5-alpha.
7344 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
7345 0.2.5.1-alpha. Patch from "NewEraCracker".
7346 - In routerlist_assert_ok(), don't take the address of a
7347 routerinfo's cache_info member unless that routerinfo is non-NULL.
7348 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
7349 - Fix a large number of false positive warnings from the clang
7350 analyzer static analysis tool. This should make real warnings
7351 easier for clang analyzer to find. Patch from "teor". Closes
7354 o Distribution (systemd):
7355 - Verify configuration file via ExecStartPre in the systemd unit
7356 file. Patch from intrigeri; resolves ticket 12730.
7357 - Explicitly disable RunAsDaemon in the systemd unit file. Our
7358 current systemd unit uses "Type = simple", so systemd does not
7359 expect tor to fork. If the user has "RunAsDaemon 1" in their
7360 torrc, then things won't work as expected. This is e.g. the case
7361 on Debian (and derivatives), since there we pass "--defaults-torrc
7362 /usr/share/tor/tor-service-defaults-torrc" (that contains
7363 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
7367 - Adjust the URLs in the README to refer to the new locations of
7368 several documents on the website. Fixes bug 12830. Patch from
7370 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
7374 Changes in version 0.2.5.6-alpha - 2014-07-28
7375 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
7376 risk from guard rotation, and fixes a variety of other issues to get
7377 us closer to a release candidate.
7379 o Major features (also in 0.2.4.23):
7380 - Make the number of entry guards configurable via a new
7381 NumEntryGuards consensus parameter, and the number of directory
7382 guards configurable via a new NumDirectoryGuards consensus
7383 parameter. Implements ticket 12688.
7385 o Major bugfixes (also in 0.2.4.23):
7386 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
7387 implementation that caused incorrect results on 32-bit
7388 implementations when certain malformed inputs were used along with
7389 a small class of private ntor keys. This bug does not currently
7390 appear to allow an attacker to learn private keys or impersonate a
7391 Tor server, but it could provide a means to distinguish 32-bit Tor
7392 implementations from 64-bit Tor implementations. Fixes bug 12694;
7393 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
7397 - Perform circuit cleanup operations even when circuit
7398 construction operations are disabled (because the network is
7399 disabled, or because there isn't enough directory information).
7400 Previously, when we were not building predictive circuits, we
7401 were not closing expired circuits either. Fixes bug 8387; bugfix on
7402 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
7403 became more strict about when we have "enough directory information
7407 - Authorities now assign the Guard flag to the fastest 25% of the
7408 network (it used to be the fastest 50%). Also raise the consensus
7409 weight that guarantees the Guard flag from 250 to 2000. For the
7410 current network, this results in about 1100 guards, down from 2500.
7411 This step paves the way for moving the number of entry guards
7412 down to 1 (proposal 236) while still providing reasonable expected
7413 performance for most users. Implements ticket 12690.
7414 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
7416 - Slightly enhance the diagnostic message for bug 12184.
7418 o Minor bugfixes (also in 0.2.4.23):
7419 - Warn and drop the circuit if we receive an inbound 'relay early'
7420 cell. Those used to be normal to receive on hidden service circuits
7421 due to bug 1038, but the buggy Tor versions are long gone from
7422 the network so we can afford to resume watching for them. Resolves
7423 the rest of bug 1038; bugfix on 0.2.1.19.
7424 - Correct a confusing error message when trying to extend a circuit
7425 via the control protocol but we don't know a descriptor or
7426 microdescriptor for one of the specified relays. Fixes bug 12718;
7427 bugfix on 0.2.3.1-alpha.
7430 - Fix compilation when building with bufferevents enabled. (This
7431 configuration is still not expected to work, however.)
7432 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
7433 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
7435 - Compile correctly with builds and forks of OpenSSL (such as
7436 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
7437 0.2.1.1-alpha. Patch from "dhill".
7440 Changes in version 0.2.4.23 - 2014-07-28
7441 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
7442 guard rotation, and also backports several important fixes from the
7443 Tor 0.2.5 alpha release series.
7446 - Clients now look at the "usecreatefast" consensus parameter to
7447 decide whether to use CREATE_FAST or CREATE cells for the first hop
7448 of their circuit. This approach can improve security on connections
7449 where Tor's circuit handshake is stronger than the available TLS
7450 connection security levels, but the tradeoff is more computational
7451 load on guard relays. Implements proposal 221. Resolves ticket 9386.
7452 - Make the number of entry guards configurable via a new
7453 NumEntryGuards consensus parameter, and the number of directory
7454 guards configurable via a new NumDirectoryGuards consensus
7455 parameter. Implements ticket 12688.
7458 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
7459 implementation that caused incorrect results on 32-bit
7460 implementations when certain malformed inputs were used along with
7461 a small class of private ntor keys. This bug does not currently
7462 appear to allow an attacker to learn private keys or impersonate a
7463 Tor server, but it could provide a means to distinguish 32-bit Tor
7464 implementations from 64-bit Tor implementations. Fixes bug 12694;
7465 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
7469 - Warn and drop the circuit if we receive an inbound 'relay early'
7470 cell. Those used to be normal to receive on hidden service circuits
7471 due to bug 1038, but the buggy Tor versions are long gone from
7472 the network so we can afford to resume watching for them. Resolves
7473 the rest of bug 1038; bugfix on 0.2.1.19.
7474 - Correct a confusing error message when trying to extend a circuit
7475 via the control protocol but we don't know a descriptor or
7476 microdescriptor for one of the specified relays. Fixes bug 12718;
7477 bugfix on 0.2.3.1-alpha.
7478 - Avoid an illegal read from stack when initializing the TLS
7479 module using a version of OpenSSL without all of the ciphers
7480 used by the v2 link handshake. Fixes bug 12227; bugfix on
7481 0.2.4.8-alpha. Found by "starlight".
7484 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
7488 Changes in version 0.2.5.5-alpha - 2014-06-18
7489 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
7490 0.2.5.x release series, including a couple of DoS issues, some
7491 performance regressions, a large number of bugs affecting the Linux
7492 seccomp2 sandbox code, and various other bugfixes. It also adds
7493 diagnostic bugfixes for a few tricky issues that we're trying to
7496 o Major features (security, traffic analysis resistance):
7497 - Several major improvements to the algorithm used to decide when to
7498 close TLS connections. Previous versions of Tor closed connections
7499 at a fixed interval after the last time a non-padding cell was
7500 sent over the connection, regardless of the target of the
7501 connection. Now, we randomize the intervals by adding up to 50% of
7502 their base value, we measure the length of time since connection
7503 last had at least one circuit, and we allow connections to known
7504 ORs to remain open a little longer (15 minutes instead of 3
7505 minutes minimum). These changes should improve Tor's resistance
7506 against some kinds of traffic analysis, and lower some overhead
7507 from needlessly closed connections. Fixes ticket 6799.
7508 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
7510 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
7511 - Fix a memory leak that could occur if a microdescriptor parse
7512 fails during the tokenizing step. This bug could enable a memory
7513 exhaustion attack by directory servers. Fixes bug 11649; bugfix
7516 o Major bugfixes (security, directory authorities):
7517 - Directory authorities now include a digest of each relay's
7518 identity key as a part of its microdescriptor.
7520 This is a workaround for bug 11743 (reported by "cypherpunks"),
7521 where Tor clients do not support receiving multiple
7522 microdescriptors with the same SHA256 digest in the same
7523 consensus. When clients receive a consensus like this, they only
7524 use one of the relays. Without this fix, a hostile relay could
7525 selectively disable some client use of target relays by
7526 constructing a router descriptor with a different identity and the
7527 same microdescriptor parameters and getting the authorities to
7528 list it in a microdescriptor consensus. This fix prevents an
7529 attacker from causing a microdescriptor collision, because the
7530 router's identity is not forgeable.
7532 o Major bugfixes (relay):
7533 - Use a direct dirport connection when uploading non-anonymous
7534 descriptors to the directory authorities. Previously, relays would
7535 incorrectly use tunnel connections under a fairly wide variety of
7536 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
7537 - When a circuit accidentally has the same circuit ID for its
7538 forward and reverse direction, correctly detect the direction of
7539 cells using that circuit. Previously, this bug made roughly one
7540 circuit in a million non-functional. Fixes bug 12195; this is a
7541 bugfix on every version of Tor.
7543 o Major bugfixes (client, pluggable transports):
7544 - When managing pluggable transports, use OS notification facilities
7545 to learn if they have crashed, and don't attempt to kill any
7546 process that has already exited. Fixes bug 8746; bugfix
7549 o Minor features (diagnostic):
7550 - When logging a warning because of bug 7164, additionally check the
7551 hash table for consistency (as proposed on ticket 11737). This may
7552 help diagnose bug 7164.
7553 - When we log a heartbeat, log how many one-hop circuits we have
7554 that are at least 30 minutes old, and log status information about
7555 a few of them. This is an attempt to track down bug 8387.
7556 - When encountering an unexpected CR while writing text to a file on
7557 Windows, log the name of the file. Should help diagnosing
7559 - Give more specific warnings when a client notices that an onion
7560 handshake has failed. Fixes ticket 9635.
7561 - Add significant new logging code to attempt to diagnose bug 12184,
7562 where relays seem to run out of available circuit IDs.
7563 - Improve the diagnostic log message for bug 8387 even further to
7564 try to improve our odds of figuring out why one-hop directory
7565 circuits sometimes do not get closed.
7567 o Minor features (security, memory management):
7568 - Memory allocation tricks (mempools and buffer freelists) are now
7569 disabled by default. You can turn them back on with
7570 --enable-mempools and --enable-buf-freelists respectively. We're
7571 disabling these features because malloc performance is good enough
7572 on most platforms, and a similar feature in OpenSSL exacerbated
7573 exploitation of the Heartbleed attack. Resolves ticket 11476.
7575 o Minor features (security):
7576 - Apply the secure SipHash-2-4 function to the hash table mapping
7577 circuit IDs and channels to circuits. We missed this one when we
7578 were converting all the other hash functions to use SipHash back
7579 in 0.2.5.3-alpha. Resolves ticket 11750.
7581 o Minor features (build):
7582 - The configure script has a --disable-seccomp option to turn off
7583 support for libseccomp on systems that have it, in case it (or
7584 Tor's use of it) is broken. Resolves ticket 11628.
7586 o Minor features (other):
7587 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
7590 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
7591 - When running a hidden service, do not allow TunneledDirConns 0;
7592 this will keep the hidden service from running, and also
7593 make it publish its descriptors directly over HTTP. Fixes bug 10849;
7594 bugfix on 0.2.1.1-alpha.
7596 o Minor bugfixes (performance):
7597 - Avoid a bug where every successful connection made us recompute
7598 the flag telling us whether we have sufficient information to
7599 build circuits. Previously, we would forget our cached value
7600 whenever we successfully opened a channel (or marked a router as
7601 running or not running for any other reason), regardless of
7602 whether we had previously believed the router to be running. This
7603 forced us to run an expensive update operation far too often.
7604 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
7605 - Avoid using tor_memeq() for checking relay cell integrity. This
7606 removes a possible performance bottleneck. Fixes part of bug
7607 12169; bugfix on 0.2.1.31.
7609 o Minor bugfixes (compilation):
7610 - Fix compilation of test_status.c when building with MVSC. Bugfix
7611 on 0.2.5.4-alpha. Patch from Gisle Vanem.
7612 - Resolve GCC complaints on OpenBSD about discarding constness in
7613 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
7614 on 0.1.1.23. Patch from Dana Koch.
7615 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
7616 treatment of long and time_t as comparable types. Fixes part of
7617 bug 11633. Patch from Dana Koch.
7618 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
7619 11623; bugfix on 0.2.5.3-alpha.
7620 - When deciding whether to build the 64-bit curve25519
7621 implementation, detect platforms where we can compile 128-bit
7622 arithmetic but cannot link it. Fixes bug 11729; bugfix on
7623 0.2.4.8-alpha. Patch from "conradev".
7624 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
7625 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
7626 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
7629 o Minor bugfixes (Directory server):
7630 - When sending a compressed set of descriptors or microdescriptors,
7631 make sure to finalize the zlib stream. Previously, we would write
7632 all the compressed data, but if the last descriptor we wanted to
7633 send was missing or too old, we would not mark the stream as
7634 finished. This caused problems for decompression tools. Fixes bug
7635 11648; bugfix on 0.1.1.23.
7637 o Minor bugfixes (Linux seccomp sandbox):
7638 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
7639 11622; bugfix on 0.2.5.1-alpha.
7640 - Avoid crashing when re-opening listener ports with the seccomp
7641 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
7642 - Avoid crashing with the seccomp sandbox enabled along with
7643 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
7644 - When we receive a SIGHUP with the sandbox enabled, correctly
7645 support rotating our log files. Fixes bug 12032; bugfix
7647 - Avoid crash when running with sandboxing enabled and
7648 DirReqStatistics not disabled. Fixes bug 12035; bugfix
7650 - Fix a "BUG" warning when trying to write bridge-stats files with
7651 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
7653 - Prevent the sandbox from crashing on startup when run with the
7654 --enable-expensive-hardening configuration option. Fixes bug
7655 11477; bugfix on 0.2.5.4-alpha.
7656 - When running with DirPortFrontPage and sandboxing both enabled,
7657 reload the DirPortFrontPage correctly when restarting. Fixes bug
7658 12028; bugfix on 0.2.5.1-alpha.
7659 - Don't try to enable the sandbox when using the Tor binary to check
7660 its configuration, hash a passphrase, or so on. Doing so was
7661 crashing on startup for some users. Fixes bug 11609; bugfix
7663 - Avoid warnings when running with sandboxing and node statistics
7664 enabled at the same time. Fixes part of 12064; bugfix on
7665 0.2.5.1-alpha. Patch from Michael Wolf.
7666 - Avoid warnings when running with sandboxing enabled at the same
7667 time as cookie authentication, hidden services, or directory
7668 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
7669 - Do not allow options that require calls to exec to be enabled
7670 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
7671 bug 12043; bugfix on 0.2.5.1-alpha.
7672 - Handle failures in getpwnam()/getpwuid() when running with the
7673 User option set and the Linux syscall sandbox enabled. Fixes bug
7674 11946; bugfix on 0.2.5.1-alpha.
7675 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
7676 to avoid calling getaddrinfo() after installing the sandbox
7677 filters. Previously, it preloaded a cache with the IPv4 address
7678 for our hostname, and nothing else. Now, it loads the cache with
7679 every address that it used to initialize the Tor process. Fixes
7680 bug 11970; bugfix on 0.2.5.1-alpha.
7682 o Minor bugfixes (pluggable transports):
7683 - Enable the ExtORPortCookieAuthFile option, to allow changing the
7684 default location of the authentication token for the extended OR
7685 Port as used by sever-side pluggable transports. We had
7686 implemented this option before, but the code to make it settable
7687 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
7688 - Avoid another 60-second delay when starting Tor in a pluggable-
7689 transport-using configuration when we already have cached
7690 descriptors for our bridges. Fixes bug 11965; bugfix
7693 o Minor bugfixes (client):
7694 - Avoid "Tried to open a socket with DisableNetwork set" warnings
7695 when starting a client with bridges configured and DisableNetwork
7696 set. (Tor launcher starts Tor with DisableNetwork set the first
7697 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
7699 o Minor bugfixes (testing):
7700 - The Python parts of the test scripts now work on Python 3 as well
7701 as Python 2, so systems where '/usr/bin/python' is Python 3 will
7702 no longer have the tests break. Fixes bug 11608; bugfix
7704 - When looking for versions of python that we could run the tests
7705 with, check for "python2.7" and "python3.3"; previously we were
7706 only looking for "python", "python2", and "python3". Patch from
7707 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
7708 - Fix all valgrind warnings produced by the unit tests. There were
7709 over a thousand memory leak warnings previously, mostly produced
7710 by forgetting to free things in the unit test code. Fixes bug
7711 11618, bugfixes on many versions of Tor.
7713 o Minor bugfixes (tor-fw-helper):
7714 - Give a correct log message when tor-fw-helper fails to launch.
7715 (Previously, we would say something like "tor-fw-helper sent us a
7716 string we could not parse".) Fixes bug 9781; bugfix
7719 o Minor bugfixes (relay, threading):
7720 - Check return code on spawn_func() in cpuworker code, so that we
7721 don't think we've spawned a nonworking cpuworker and write junk to
7722 it forever. Fix related to bug 4345; bugfix on all released Tor
7723 versions. Found by "skruffy".
7724 - Use a pthread_attr to make sure that spawn_func() cannot return an
7725 error while at the same time launching a thread. Fix related to
7726 bug 4345; bugfix on all released Tor versions. Reported
7729 o Minor bugfixes (relay, oom prevention):
7730 - Correctly detect the total available system memory. We tried to do
7731 this in 0.2.5.4-alpha, but the code was set up to always return an
7732 error value, even on success. Fixes bug 11805; bugfix
7735 o Minor bugfixes (relay, other):
7736 - We now drop CREATE cells for already-existent circuit IDs and for
7737 zero-valued circuit IDs, regardless of other factors that might
7738 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
7740 - Avoid an illegal read from stack when initializing the TLS module
7741 using a version of OpenSSL without all of the ciphers used by the
7742 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
7744 - When rejecting DATA cells for stream_id zero, still count them
7745 against the circuit's deliver window so that we don't fail to send
7746 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
7748 o Minor bugfixes (logging):
7749 - Fix a misformatted log message about delayed directory fetches.
7750 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
7751 - Squelch a spurious LD_BUG message "No origin circuit for
7752 successful SOCKS stream" in certain hidden service failure cases;
7756 - Include a tor.service file in contrib/dist for use with systemd.
7757 Some distributions will be able to use this file unmodified;
7758 others will need to tweak it, or write their own. Patch from Jamie
7759 Nguyen; resolves ticket 8368.
7762 - Clean up several option names in the manpage to match their real
7763 names, add the missing documentation for a couple of testing and
7764 directory authority options, remove the documentation for a
7765 V2-directory fetching option that no longer exists. Resolves
7767 - Correct the documenation so that it lists the correct directory
7768 for the stats files. (They are in a subdirectory called "stats",
7770 - In the manpage, move more authority-only options into the
7771 directory authority section so that operators of regular directory
7772 caches don't get confused.
7775 - The contrib directory has been sorted and tidied. Before, it was
7776 an unsorted dumping ground for useful and not-so-useful things.
7777 Now, it is divided based on functionality, and the items which
7778 seemed to be nonfunctional or useless have been removed. Resolves
7779 ticket 8966; based on patches from "rl1987".
7782 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
7783 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
7784 - The TunnelDirConns and PreferTunnelledDirConns options no longer
7785 exist; tunneled directory connections have been available since
7786 0.1.2.5-alpha, and turning them off is not a good idea. This is a
7787 brute-force fix for 10849, where "TunnelDirConns 0" would break
7791 Changes in version 0.2.4.22 - 2014-05-16
7792 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
7793 alpha release series. These include blocking all authority signing
7794 keys that may have been affected by the OpenSSL "heartbleed" bug,
7795 choosing a far more secure set of TLS ciphersuites by default, closing
7796 a couple of memory leaks that could be used to run a target relay out
7797 of RAM, and several others.
7799 o Major features (security, backport from 0.2.5.4-alpha):
7800 - Block authority signing keys that were used on authorities
7801 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
7802 don't have any evidence that these keys _were_ compromised; we're
7803 doing this to be prudent.) Resolves ticket 11464.
7805 o Major bugfixes (security, OOM):
7806 - Fix a memory leak that could occur if a microdescriptor parse
7807 fails during the tokenizing step. This bug could enable a memory
7808 exhaustion attack by directory servers. Fixes bug 11649; bugfix
7811 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
7812 - The relay ciphersuite list is now generated automatically based on
7813 uniform criteria, and includes all OpenSSL ciphersuites with
7814 acceptable strength and forward secrecy. Previously, we had left
7815 some perfectly fine ciphersuites unsupported due to omission or
7816 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
7817 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
7818 - Relays now trust themselves to have a better view than clients of
7819 which TLS ciphersuites are better than others. (Thanks to bug
7820 11513, the relay list is now well-considered, whereas the client
7821 list has been chosen mainly for anti-fingerprinting purposes.)
7822 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
7823 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
7824 AES128. Resolves ticket 11528.
7825 - Clients now try to advertise the same list of ciphersuites as
7826 Firefox 28. This change enables selection of (fast) GCM
7827 ciphersuites, disables some strange old ciphers, and stops
7828 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
7829 Resolves ticket 11438.
7831 o Minor bugfixes (configuration, security):
7832 - When running a hidden service, do not allow TunneledDirConns 0:
7833 trying to set that option together with a hidden service would
7834 otherwise prevent the hidden service from running, and also make
7835 it publish its descriptors directly over HTTP. Fixes bug 10849;
7836 bugfix on 0.2.1.1-alpha.
7838 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
7839 - Avoid sending a garbage value to the controller when a circuit is
7840 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
7842 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
7843 - Stop leaking memory when we successfully resolve a PTR record.
7844 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
7846 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
7847 - Avoid 60-second delays in the bootstrapping process when Tor is
7848 launching for a second time while using bridges. Fixes bug 9229;
7849 bugfix on 0.2.0.3-alpha.
7851 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
7852 - Give the correct URL in the warning message when trying to run a
7853 relay on an ancient version of Windows. Fixes bug 9393.
7855 o Minor bugfixes (compilation):
7856 - Fix a compilation error when compiling with --disable-curve25519.
7857 Fixes bug 9700; bugfix on 0.2.4.17-rc.
7860 - Downgrade the warning severity for the the "md was still
7861 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
7862 for trying to diagnose this bug, and the current warning in
7863 earlier versions of tor achieves nothing useful. Addresses warning
7866 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
7867 - When we run out of usable circuit IDs on a channel, log only one
7868 warning for the whole channel, and describe how many circuits
7869 there were on the channel. Fixes part of ticket 11553.
7871 o Minor features (security, backport from 0.2.5.4-alpha):
7872 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
7873 leave the default at 8GBytes), to better support Raspberry Pi
7874 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
7876 o Documentation (backport from 0.2.5.4-alpha):
7877 - Correctly document that we search for a system torrc file before
7878 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
7882 Changes in version 0.2.5.4-alpha - 2014-04-25
7883 Tor 0.2.5.4-alpha includes several security and performance
7884 improvements for clients and relays, including blacklisting authority
7885 signing keys that were used while susceptible to the OpenSSL
7886 "heartbleed" bug, fixing two expensive functions on busy relays,
7887 improved TLS ciphersuite preference lists, support for run-time
7888 hardening on compilers that support AddressSanitizer, and more work on
7889 the Linux sandbox code.
7891 There are also several usability fixes for clients (especially clients
7892 that use bridges), two new TransPort protocols supported (one on
7893 OpenBSD, one on FreeBSD), and various other bugfixes.
7895 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
7896 have accumulated many known flaws; everyone should upgrade.
7898 o Major features (security):
7899 - If you don't specify MaxMemInQueues yourself, Tor now tries to
7900 pick a good value based on your total system memory. Previously,
7901 the default was always 8 GB. You can still override the default by
7902 setting MaxMemInQueues yourself. Resolves ticket 11396.
7903 - Block authority signing keys that were used on authorities
7904 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
7905 don't have any evidence that these keys _were_ compromised; we're
7906 doing this to be prudent.) Resolves ticket 11464.
7908 o Major features (relay performance):
7909 - Speed up server-side lookups of rendezvous and introduction point
7910 circuits by using hashtables instead of linear searches. These
7911 functions previously accounted between 3 and 7% of CPU usage on
7912 some busy relays. Resolves ticket 9841.
7913 - Avoid wasting CPU when extending a circuit over a channel that is
7914 nearly out of circuit IDs. Previously, we would do a linear scan
7915 over possible circuit IDs before finding one or deciding that we
7916 had exhausted our possibilities. Now, we try at most 64 random
7917 circuit IDs before deciding that we probably won't succeed. Fixes
7918 a possible root cause of ticket 11553.
7920 o Major features (seccomp2 sandbox, Linux only):
7921 - The seccomp2 sandbox can now run a test network for multiple hours
7922 without crashing. The sandbox is still experimental, and more bugs
7923 will probably turn up. To try it, enable "Sandbox 1" on a Linux
7924 host. Resolves ticket 11351.
7925 - Strengthen sandbox code: the sandbox can now test the arguments
7926 for rename(), and blocks _sysctl() entirely. Resolves another part
7928 - When the sandbox blocks a system call, it now tries to log a stack
7929 trace before exiting. Resolves ticket 11465.
7931 o Major bugfixes (TLS cipher selection):
7932 - The relay ciphersuite list is now generated automatically based on
7933 uniform criteria, and includes all OpenSSL ciphersuites with
7934 acceptable strength and forward secrecy. Previously, we had left
7935 some perfectly fine ciphersuites unsupported due to omission or
7936 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
7937 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
7938 - Relays now trust themselves to have a better view than clients of
7939 which TLS ciphersuites are better than others. (Thanks to bug
7940 11513, the relay list is now well-considered, whereas the client
7941 list has been chosen mainly for anti-fingerprinting purposes.)
7942 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
7943 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
7944 AES128. Resolves ticket 11528.
7945 - Clients now try to advertise the same list of ciphersuites as
7946 Firefox 28. This change enables selection of (fast) GCM
7947 ciphersuites, disables some strange old ciphers, and stops
7948 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
7949 Resolves ticket 11438.
7951 o Major bugfixes (bridge client):
7952 - Avoid 60-second delays in the bootstrapping process when Tor is
7953 launching for a second time while using bridges. Fixes bug 9229;
7954 bugfix on 0.2.0.3-alpha.
7956 o Minor features (transparent proxy, *BSD):
7957 - Support FreeBSD's ipfw firewall interface for TransPort ports on
7958 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
7959 10267; patch from "yurivict".
7960 - Support OpenBSD's divert-to rules with the pf firewall for
7961 transparent proxy ports. To enable it, set "TransProxyType
7962 pf-divert". This allows Tor to run a TransPort transparent proxy
7963 port on OpenBSD 4.4 or later without root privileges. See the
7964 pf.conf(5) manual page for information on configuring pf to use
7965 divert-to rules. Closes ticket 10896; patch from Dana Koch.
7967 o Minor features (security):
7968 - New --enable-expensive-hardening option to enable security
7969 hardening options that consume nontrivial amounts of CPU and
7970 memory. Right now, this includes AddressSanitizer and UbSan, which
7971 are supported in newer versions of GCC and Clang. Closes ticket
7974 o Minor features (log verbosity):
7975 - Demote the message that we give when a flushing connection times
7976 out for too long from NOTICE to INFO. It was usually meaningless.
7977 Resolves ticket 5286.
7978 - Don't log so many notice-level bootstrapping messages at startup
7979 about downloading descriptors. Previously, we'd log a notice
7980 whenever we learned about more routers. Now, we only log a notice
7981 at every 5% of progress. Fixes bug 9963.
7982 - Warn less verbosely when receiving a malformed
7983 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
7984 - When we run out of usable circuit IDs on a channel, log only one
7985 warning for the whole channel, and describe how many circuits
7986 there were on the channel. Fixes part of ticket 11553.
7988 o Minor features (relay):
7989 - If a circuit timed out for at least 3 minutes, check if we have a
7990 new external IP address, and publish a new descriptor with the new
7991 IP address if it changed. Resolves ticket 2454.
7993 o Minor features (controller):
7994 - Make the entire exit policy available from the control port via
7995 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
7997 - Because of the fix for ticket 11396, the real limit for memory
7998 usage may no longer match the configured MaxMemInQueues value. The
7999 real limit is now exposed via GETINFO limits/max-mem-in-queues.
8001 o Minor features (bridge client):
8002 - Report a more useful failure message when we can't connect to a
8003 bridge because we don't have the right pluggable transport
8004 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
8006 o Minor features (diagnostic):
8007 - Add more log messages to diagnose bug 7164, which causes
8008 intermittent "microdesc_free() called but md was still referenced"
8009 warnings. We now include more information, to figure out why we
8010 might be cleaning a microdescriptor for being too old if it's
8011 still referenced by a live node_t object.
8013 o Minor bugfixes (client, DNSPort):
8014 - When using DNSPort, try to respond to AAAA requests with AAAA
8015 answers. Previously, we hadn't looked at the request type when
8016 deciding which answer type to prefer. Fixes bug 10468; bugfix on
8018 - When receiving a DNS query for an unsupported record type, reply
8019 with no answer rather than with a NOTIMPL error. This behavior
8020 isn't correct either, but it will break fewer client programs, we
8021 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
8024 o Minor bugfixes (exit relay):
8025 - Stop leaking memory when we successfully resolve a PTR record.
8026 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
8028 o Minor bugfixes (bridge client):
8029 - Stop accepting bridge lines containing hostnames. Doing so would
8030 cause clients to perform DNS requests on the hostnames, which was
8031 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
8032 - Avoid a 60-second delay in the bootstrapping process when a Tor
8033 client with pluggable transports re-reads its configuration at
8034 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
8036 o Minor bugfixes (client, logging during bootstrap):
8037 - Warn only once if we start logging in an unsafe way. Previously,
8038 we complain as many times as we had problems. Fixes bug 9870;
8039 bugfix on 0.2.5.1-alpha.
8040 - Only report the first fatal bootstrap error on a given OR
8041 connection. This stops us from telling the controller bogus error
8042 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
8043 - Be more helpful when trying to run sandboxed on Linux without
8044 libseccomp. Instead of saying "Sandbox is not implemented on this
8045 platform", we now explain that we need to be built with
8046 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
8047 - Avoid generating spurious warnings when starting with
8048 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
8051 o Minor bugfixes (closing OR connections):
8052 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
8053 check if it's an or_connection_t and correctly call
8054 connection_or_close_for_error() rather than
8055 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
8057 - When closing all connections on setting DisableNetwork to 1, use
8058 connection_or_close_normally() rather than closing OR connections
8059 out from under the channel layer. Fixes bug 11306; bugfix on
8062 o Minor bugfixes (controller):
8063 - Avoid sending a garbage value to the controller when a circuit is
8064 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
8066 o Minor bugfixes (tor-fw-helper):
8067 - Allow tor-fw-helper to build again by adding src/ext to its
8068 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
8070 o Minor bugfixes (bridges):
8071 - Avoid potential crashes or bad behavior when launching a
8072 server-side managed proxy with ORPort or ExtORPort temporarily
8073 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
8075 o Minor bugfixes (platform-specific):
8076 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
8077 bug 11426; bugfix on 0.2.5.3-alpha.
8078 - When dumping a malformed directory object to disk, save it in
8079 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
8081 - Don't report failures from make_socket_reuseable() on incoming
8082 sockets on OSX: this can happen when incoming connections close
8083 early. Fixes bug 10081.
8085 o Minor bugfixes (trivial memory leaks):
8086 - Fix a small memory leak when signing a directory object. Fixes bug
8087 11275; bugfix on 0.2.4.13-alpha.
8088 - Free placeholder entries in our circuit table at exit; fixes a
8089 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
8090 - Don't re-initialize a second set of OpenSSL mutexes when starting
8091 up. Previously, we'd make one set of mutexes, and then immediately
8092 replace them with another. Fixes bug 11726; bugfix on
8094 - Resolve some memory leaks found by coverity in the unit tests, on
8095 exit in tor-gencert, and on a failure to compute digests for our
8096 own keys when generating a v3 networkstatus vote. These leaks
8097 should never have affected anyone in practice.
8099 o Minor bugfixes (hidden service):
8100 - Only retry attempts to connect to a chosen rendezvous point 8
8101 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
8103 o Minor bugfixes (misc code correctness):
8104 - Fix various instances of undefined behavior in channeltls.c,
8105 tor_memmem(), and eventdns.c that would cause us to construct
8106 pointers to memory outside an allocated object. (These invalid
8107 pointers were not accessed, but C does not even allow them to
8108 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
8109 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
8110 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
8111 fix some miscellaneous errors in our tests and codebase. Fixes bug
8112 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
8113 - Always check return values for unlink, munmap, UnmapViewOfFile;
8114 check strftime return values more often. In some cases all we can
8115 do is report a warning, but this may help prevent deeper bugs from
8116 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
8118 - Fix numerous warnings from the clang "scan-build" static analyzer.
8119 Some of these are programming style issues; some of them are false
8120 positives that indicated awkward code; some are undefined behavior
8121 cases related to constructing (but not using) invalid pointers;
8122 some are assumptions about API behavior; some are (harmlessly)
8123 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
8124 correct; and one or two are genuine bugs that weren't reachable
8125 from the rest of the program. Fixes bug 8793; bugfixes on many,
8129 - Build the torify.1 manpage again. Previously, we were only trying
8130 to build it when also building tor-fw-helper. That's why we didn't
8131 notice that we'd broken the ability to build it. Fixes bug 11321;
8132 bugfix on 0.2.5.1-alpha.
8133 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
8134 11061; bugfix on 0.2.4.7-alpha.
8135 - Correctly document that we search for a system torrc file before
8136 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
8138 - Resolve warnings from Doxygen.
8140 o Code simplifications and refactoring:
8141 - Remove is_internal_IP() function. Resolves ticket 4645.
8142 - Remove unused function circuit_dump_by_chan from circuitlist.c.
8143 Closes issue 9107; patch from "marek".
8144 - Change our use of the ENUM_BF macro to avoid declarations that
8147 o Deprecated versions:
8148 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
8149 attention for some while. Directory authorities no longer accept
8150 descriptors from relays running any version of Tor prior to Tor
8151 0.2.3.16-alpha. Resolves ticket 11149.
8154 - New macros in test.h to simplify writing mock-functions for unit
8155 tests. Part of ticket 11507. Patch from Dana Koch.
8156 - Complete tests for the status.c module. Resolves ticket 11507.
8157 Patch from Dana Koch.
8160 - Remove all code for the long unused v1 directory protocol.
8161 Resolves ticket 11070.
8164 Changes in version 0.2.5.3-alpha - 2014-03-22
8165 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
8166 two new anti-DoS features for Tor relays, resolves a bug that kept
8167 SOCKS5 support for IPv6 from working, fixes several annoying usability
8168 issues for bridge users, and removes more old code for unused
8171 The Tor 0.2.5.x release series is now in patch-freeze: no feature
8172 patches not already written will be considered for inclusion in 0.2.5.x.
8174 o Major features (relay security, DoS-resistance):
8175 - When deciding whether we have run out of memory and we need to
8176 close circuits, also consider memory allocated in buffers for
8177 streams attached to each circuit.
8179 This change, which extends an anti-DoS feature introduced in
8180 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
8181 better resist more memory-based DoS attacks than before. Since the
8182 MaxMemInCellQueues option now applies to all queues, it is renamed
8183 to MaxMemInQueues. This feature fixes bug 10169.
8184 - Avoid hash-flooding denial-of-service attacks by using the secure
8185 SipHash-2-4 hash function for our hashtables. Without this
8186 feature, an attacker could degrade performance of a targeted
8187 client or server by flooding their data structures with a large
8188 number of entries to be stored at the same hash table position,
8189 thereby slowing down the Tor instance. With this feature, hash
8190 table positions are derived from a randomized cryptographic key,
8191 and an attacker cannot predict which entries will collide. Closes
8193 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
8194 the default at 8GBytes), to better support Raspberry Pi users. Fixes
8195 bug 9686; bugfix on 0.2.4.14-alpha.
8197 o Minor features (bridges, pluggable transports):
8198 - Bridges now write the SHA1 digest of their identity key
8199 fingerprint (that is, a hash of a hash of their public key) to
8200 notice-level logs, and to a new hashed-fingerprint file. This
8201 information will help bridge operators look up their bridge in
8202 Globe and similar tools. Resolves ticket 10884.
8203 - Improve the message that Tor displays when running as a bridge
8204 using pluggable transports without an Extended ORPort listener.
8205 Also, log the message in the log file too. Resolves ticket 11043.
8207 o Minor features (other):
8208 - Add a new option, PredictedPortsRelevanceTime, to control how long
8209 after having received a request to connect to a given port Tor
8210 will try to keep circuits ready in anticipation of future requests
8211 for that port. Patch from "unixninja92"; implements ticket 9176.
8212 - Generate a warning if any ports are listed in the SocksPolicy,
8213 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
8214 AuthDirBadExit options. (These options only support address
8215 ranges.) Fixes part of ticket 11108.
8216 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
8219 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
8220 - Build without warnings under clang 3.4. (We have some macros that
8221 define static functions only some of which will get used later in
8222 the module. Starting with clang 3.4, these give a warning unless the
8223 unused attribute is set on them.) Resolves ticket 10904.
8224 - Fix build warnings about missing "a2x" comment when building the
8225 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
8226 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
8228 o Minor bugfixes (client):
8229 - Improve the log message when we can't connect to a hidden service
8230 because all of the hidden service directory nodes hosting its
8231 descriptor are excluded. Improves on our fix for bug 10722, which
8232 was a bugfix on 0.2.0.10-alpha.
8233 - Raise a control port warning when we fail to connect to all of
8234 our bridges. Previously, we didn't inform the controller, and
8235 the bootstrap process would stall. Fixes bug 11069; bugfix on
8237 - Exit immediately when a process-owning controller exits.
8238 Previously, tor relays would wait for a little while after their
8239 controller exited, as if they had gotten an INT signal -- but this
8240 was problematic, since there was no feedback for the user. To do a
8241 clean shutdown, controllers should send an INT signal and give Tor
8242 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
8243 - Stop attempting to connect to bridges before our pluggable
8244 transports are configured (harmless but resulted in some erroneous
8245 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
8246 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
8247 generating incorrect SOCKS5 responses, and confusing client
8248 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
8250 o Minor bugfixes (relays and bridges):
8251 - Avoid crashing on a malformed resolv.conf file when running a
8252 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
8253 - Non-exit relays no longer launch mock DNS requests to check for
8254 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
8255 non-exit relays stopped servicing DNS requests. Fixes bug 965;
8256 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
8257 - Bridges now report complete directory request statistics. Related
8258 to bug 5824; bugfix on 0.2.2.1-alpha.
8259 - Bridges now never collect statistics that were designed for
8260 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
8261 - Stop giving annoying warning messages when we decide not to launch
8262 a pluggable transport proxy that we don't need (because there are
8263 no bridges configured to use it). Resolves ticket 5018; bugfix
8265 - Give the correct URL in the warning message when trying to run a
8266 relay on an ancient version of Windows. Fixes bug 9393.
8268 o Minor bugfixes (backtrace support):
8269 - Support automatic backtraces on more platforms by using the
8270 "-fasynchronous-unwind-tables" compiler option. This option is
8271 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
8272 is on by default and table generation is not. This doesn't yet
8273 add Windows support; only Linux, OSX, and some BSDs are affected.
8274 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
8275 - Avoid strange behavior if two threads hit failed assertions at the
8276 same time and both try to log backtraces at once. (Previously, if
8277 this had happened, both threads would have stored their intermediate
8278 results in the same buffer, and generated junk outputs.) Reported by
8279 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
8280 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
8281 0.2.5.2-alpha; patch from Nick Hopper.
8283 o Minor bugfixes (unit tests):
8284 - Fix a small bug in the unit tests that might have made the tests
8285 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
8286 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
8289 - Remove all remaining code related to version-0 hidden service
8290 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
8291 the rest of bug 10841.
8294 - Document in the manpage that "KBytes" may also be written as
8295 "kilobytes" or "KB", that "Kbits" may also be written as
8296 "kilobits", and so forth. Closes ticket 9222.
8297 - Document that the ClientOnly config option overrides ORPort.
8298 Our old explanation made ClientOnly sound as though it did
8299 nothing at all. Resolves bug 9059.
8300 - Explain that SocksPolicy, DirPolicy, and similar options don't
8301 take port arguments. Fixes the other part of ticket 11108.
8302 - Fix a comment about the rend_server_descriptor_t.protocols field
8303 to more accurately describe its range. Also, make that field
8304 unsigned, to more accurately reflect its usage. Fixes bug 9099;
8305 bugfix on 0.2.1.5-alpha.
8306 - Fix the manpage's description of HiddenServiceAuthorizeClient:
8307 the maximum client name length is 16, not 19. Fixes bug 11118;
8308 bugfix on 0.2.1.6-alpha.
8310 o Code simplifications and refactoring:
8311 - Get rid of router->address, since in all cases it was just the
8312 string representation of router->addr. Resolves ticket 5528.
8314 o Test infrastructure:
8315 - Update to the latest version of tinytest.
8316 - Improve the tinytest implementation of string operation tests so
8317 that comparisons with NULL strings no longer crash the tests; they
8318 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
8321 Changes in version 0.2.4.21 - 2014-02-28
8322 Tor 0.2.4.21 further improves security against potential adversaries who
8323 find breaking 1024-bit crypto doable, and backports several stability
8324 and robustness patches from the 0.2.5 branch.
8326 o Major features (client security):
8327 - When we choose a path for a 3-hop circuit, make sure it contains
8328 at least one relay that supports the NTor circuit extension
8329 handshake. Otherwise, there is a chance that we're building
8330 a circuit that's worth attacking by an adversary who finds
8331 breaking 1024-bit crypto doable, and that chance changes the game
8332 theory. Implements ticket 9777.
8335 - Do not treat streams that fail with reason
8336 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
8337 since it could also indicate an ENETUNREACH connection error. Fixes
8338 part of bug 10777; bugfix on 0.2.4.8-alpha.
8340 o Code simplification and refactoring:
8341 - Remove data structures which were introduced to implement the
8342 CellStatistics option: they are now redundant with the new timestamp
8343 field in the regular packed_cell_t data structure, which we did
8344 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
8347 - Always clear OpenSSL bignums before freeing them -- even bignums
8348 that don't contain secrets. Resolves ticket 10793. Patch by
8350 - Build without warnings under clang 3.4. (We have some macros that
8351 define static functions only some of which will get used later in
8352 the module. Starting with clang 3.4, these give a warning unless the
8353 unused attribute is set on them.) Resolves ticket 10904.
8354 - Update geoip and geoip6 files to the February 7 2014 Maxmind
8355 GeoLite2 Country database.
8358 - Set the listen() backlog limit to the largest actually supported
8359 on the system, not to the value in a header file. Fixes bug 9716;
8360 bugfix on every released Tor.
8361 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
8362 exit node as a NOROUTE error, not an INTERNAL error, since they
8363 can apparently happen when trying to connect to the wrong sort
8364 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
8365 - Fix build warnings about missing "a2x" comment when building the
8366 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
8367 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
8368 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
8369 not entirely remove it from the connection lists. Fixes bug 9602;
8370 bugfix on 0.2.4.4-alpha.
8371 - Fix a segmentation fault in our benchmark code when running with
8372 Fedora's OpenSSL package, or any other OpenSSL that provides
8373 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
8374 - Turn "circuit handshake stats since last time" log messages into a
8375 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
8377 o Documentation fixes:
8378 - Document that all but one DirPort entry must have the NoAdvertise
8379 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
8382 Changes in version 0.2.5.2-alpha - 2014-02-13
8383 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
8384 like the "poor random number generation" fix and the "building too many
8385 circuits" fix. It also further improves security against potential
8386 adversaries who find breaking 1024-bit crypto doable, and launches
8387 pluggable transports on demand (which gets us closer to integrating
8388 pluggable transport support by default -- not to be confused with Tor
8389 bundles enabling pluggable transports and bridges by default).
8391 o Major features (client security):
8392 - When we choose a path for a 3-hop circuit, make sure it contains
8393 at least one relay that supports the NTor circuit extension
8394 handshake. Otherwise, there is a chance that we're building
8395 a circuit that's worth attacking by an adversary who finds
8396 breaking 1024-bit crypto doable, and that chance changes the game
8397 theory. Implements ticket 9777.
8398 - Clients now look at the "usecreatefast" consensus parameter to
8399 decide whether to use CREATE_FAST or CREATE cells for the first hop
8400 of their circuit. This approach can improve security on connections
8401 where Tor's circuit handshake is stronger than the available TLS
8402 connection security levels, but the tradeoff is more computational
8403 load on guard relays. Implements proposal 221. Resolves ticket 9386.
8405 o Major features (bridges):
8406 - Don't launch pluggable transport proxies if we don't have any
8407 bridges configured that would use them. Now we can list many
8408 pluggable transports, and Tor will dynamically start one when it
8409 hears a bridge address that needs it. Resolves ticket 5018.
8410 - The bridge directory authority now assigns status flags (Stable,
8411 Guard, etc) to bridges based on thresholds calculated over all
8412 Running bridges. Now bridgedb can finally make use of its features
8413 to e.g. include at least one Stable bridge in its answers. Fixes
8416 o Major features (other):
8417 - Extend ORCONN controller event to include an "ID" parameter,
8418 and add four new controller event types CONN_BW, CIRC_BW,
8419 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
8420 The new events are emitted in private Tor networks only, with the
8421 goal of being able to better track performance and load during
8422 full-network simulations. Implements proposal 218 and ticket 7359.
8423 - On some platforms (currently: recent OSX versions, glibc-based
8424 platforms that support the ELF format, and a few other
8425 Unix-like operating systems), Tor can now dump stack traces
8426 when a crash occurs or an assertion fails. By default, traces
8427 are dumped to stderr (if possible) and to any logs that are
8428 reporting errors. Implements ticket 9299.
8431 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
8432 not entirely remove it from the connection lists. Fixes bug 9602;
8433 bugfix on 0.2.4.4-alpha.
8434 - Do not treat streams that fail with reason
8435 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
8436 since it could also indicate an ENETUNREACH connection error. Fixes
8437 part of bug 10777; bugfix on 0.2.4.8-alpha.
8439 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
8440 - Do not allow OpenSSL engines to replace the PRNG, even when
8441 HardwareAccel is set. The only default builtin PRNG engine uses
8442 the Intel RDRAND instruction to replace the entire PRNG, and
8443 ignores all attempts to seed it with more entropy. That's
8444 cryptographically stupid: the right response to a new alleged
8445 entropy source is never to discard all previously used entropy
8446 sources. Fixes bug 10402; works around behavior introduced in
8447 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
8449 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
8450 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
8451 - Avoid launching spurious extra circuits when a stream is pending.
8452 This fixes a bug where any circuit that _wasn't_ unusable for new
8453 streams would be treated as if it were, causing extra circuits to
8454 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
8456 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
8457 - No longer stop reading or writing on cpuworker connections when
8458 our rate limiting buckets go empty. Now we should handle circuit
8459 handshake requests more promptly. Resolves bug 9731.
8460 - Stop trying to bootstrap all our directory information from
8461 only our first guard. Discovered while fixing bug 9946; bugfix
8464 o Minor features (bridges, pluggable transports):
8465 - Add threshold cutoffs to the networkstatus document created by
8466 the Bridge Authority. Fixes bug 1117.
8467 - On Windows, spawn background processes using the CREATE_NO_WINDOW
8468 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
8469 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
8470 Vidalia set this option for us.) Implements ticket 10297.
8472 o Minor features (security):
8473 - Always clear OpenSSL bignums before freeing them -- even bignums
8474 that don't contain secrets. Resolves ticket 10793. Patch by
8477 o Minor features (config options and command line):
8478 - Add an --allow-missing-torrc commandline option that tells Tor to
8479 run even if the configuration file specified by -f is not available.
8480 Implements ticket 10060.
8481 - Add support for the TPROXY transparent proxying facility on Linux.
8482 See documentation for the new TransProxyType option for more
8483 details. Implementation by "thomo". Closes ticket 10582.
8485 o Minor features (controller):
8486 - Add a new "HS_DESC" controller event that reports activities
8487 related to hidden service descriptors. Resolves ticket 8510.
8488 - New "DROPGUARDS" controller command to forget all current entry
8489 guards. Not recommended for ordinary use, since replacing guards
8490 too frequently makes several attacks easier. Resolves ticket 9934;
8493 o Minor features (build):
8494 - Assume that a user using ./configure --host wants to cross-compile,
8495 and give an error if we cannot find a properly named
8496 tool-chain. Add a --disable-tool-name-check option to proceed
8497 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
8498 - If we run ./configure and the compiler recognizes -fstack-protector
8499 but the linker rejects it, warn the user about a potentially missing
8500 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
8502 o Minor features (testing):
8503 - If Python is installed, "make check" now runs extra tests beyond
8504 the unit test scripts.
8505 - When bootstrapping a test network, sometimes very few relays get
8506 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
8507 specify a set of relays which should be voted Guard regardless of
8508 their uptime or bandwidth. Addresses ticket 9206.
8510 o Minor features (log messages):
8511 - When ServerTransportPlugin is set on a bridge, Tor can write more
8512 useful statistics about bridge use in its extrainfo descriptors,
8513 but only if the Extended ORPort ("ExtORPort") is set too. Add a
8514 log message to inform the user in this case. Resolves ticket 9651.
8515 - When receiving a new controller connection, log the origin address.
8516 Resolves ticket 9698; patch from "sigpipe".
8517 - When logging OpenSSL engine status at startup, log the status of
8518 more engines. Fixes ticket 10043; patch from Joshua Datko.
8519 - Turn "circuit handshake stats since last time" log messages into a
8520 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
8522 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
8523 - Improve the circuit queue out-of-memory handler. Previously, when
8524 we ran low on memory, we'd close whichever circuits had the most
8525 queued cells. Now, we close those that have the *oldest* queued
8526 cells, on the theory that those are most responsible for us
8527 running low on memory. Based on analysis from a forthcoming paper
8528 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
8529 - Generate bootstrapping status update events correctly when fetching
8530 microdescriptors. Fixes bug 9927.
8531 - Update to the October 2 2013 Maxmind GeoLite Country database.
8533 o Minor bugfixes (clients):
8534 - When closing a channel that has already been open, do not close
8535 pending circuits that were waiting to connect to the same relay.
8536 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
8539 o Minor bugfixes (relays):
8540 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
8541 exit node as a NOROUTE error, not an INTERNAL error, since they
8542 can apparently happen when trying to connect to the wrong sort
8543 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
8545 o Minor bugfixes (bridges):
8546 - Fix a bug where the first connection works to a bridge that uses a
8547 pluggable transport with client-side parameters, but we don't send
8548 the client-side parameters on subsequent connections. (We don't
8549 use any pluggable transports with client-side parameters yet,
8550 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
8551 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
8553 o Minor bugfixes (node selection):
8554 - If ExcludeNodes is set, consider non-excluded hidden service
8555 directory servers before excluded ones. Do not consider excluded
8556 hidden service directory servers at all if StrictNodes is
8557 set. (Previously, we would sometimes decide to connect to those
8558 servers, and then realize before we initiated a connection that
8559 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
8561 - If we set the ExitNodes option but it doesn't include any nodes
8562 that have the Exit flag, we would choose not to bootstrap. Now we
8563 bootstrap so long as ExitNodes includes nodes which can exit to
8564 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
8566 o Minor bugfixes (controller and command-line):
8567 - If changing a config option via "setconf" fails in a recoverable
8568 way, we used to nonetheless write our new control ports to the
8569 file described by the "ControlPortWriteToFile" option. Now we only
8570 write out that file if we successfully switch to the new config
8571 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
8572 - When a command-line option such as --version or --help that
8573 ordinarily implies --hush appears on the command line along with
8574 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
8575 only if it appeared later on the command line. Fixes bug 9578;
8576 bugfix on 0.2.5.1-alpha.
8578 o Minor bugfixes (code correctness):
8579 - Previously we used two temporary files when writing descriptors to
8580 disk; now we only use one. Fixes bug 1376.
8581 - Remove an erroneous (but impossible and thus harmless) pointer
8582 comparison that would have allowed compilers to skip a bounds
8583 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
8584 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
8585 - Fix an always-true assertion in pluggable transports code so it
8586 actually checks what it was trying to check. Fixes bug 10046;
8587 bugfix on 0.2.3.9-alpha. Found by "dcb".
8589 o Minor bugfixes (protocol correctness):
8590 - When receiving a VERSIONS cell with an odd number of bytes, close
8591 the connection immediately since the cell is malformed. Fixes bug
8592 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
8595 o Minor bugfixes (build):
8596 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
8597 turned off (that is, without support for v2 link handshakes). Fixes
8598 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
8599 - Fix compilation warnings and startup issues when running with
8600 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
8602 - Fix compilation on Solaris 9, which didn't like us having an
8603 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
8605 o Minor bugfixes (testing):
8606 - Fix a segmentation fault in our benchmark code when running with
8607 Fedora's OpenSSL package, or any other OpenSSL that provides
8608 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
8610 o Minor bugfixes (log messages):
8611 - Fix a bug where clients using bridges would report themselves
8612 as 50% bootstrapped even without a live consensus document.
8613 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
8614 - Suppress a warning where, if there's only one directory authority
8615 in the network, we would complain that votes and signatures cannot
8616 be uploaded to other directory authorities. Fixes bug 10842;
8617 bugfix on 0.2.2.26-beta.
8618 - Report bootstrapping progress correctly when we're downloading
8619 microdescriptors. We had updated our "do we have enough microdescs
8620 to begin building circuits?" logic most recently in 0.2.4.10-alpha
8621 (see bug 5956), but we left the bootstrap status event logic at
8622 "how far through getting 1/4 of them are we?" Fixes bug 9958;
8623 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
8625 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
8626 - Avoid a crash bug when starting with a corrupted microdescriptor
8627 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
8628 - If we fail to dump a previously cached microdescriptor to disk, avoid
8629 freeing duplicate data later on. Fixes bug 10423; bugfix on
8630 0.2.4.13-alpha. Spotted by "bobnomnom".
8632 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
8633 - Correctly log long IPv6 exit policies, instead of truncating them
8634 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
8635 - Our default TLS ecdhe groups were backwards: we meant to be using
8636 P224 for relays (for performance win) and P256 for bridges (since
8637 it is more common in the wild). Instead we had it backwards. After
8638 reconsideration, we decided that the default should be P256 on all
8639 hosts, since its security is probably better, and since P224 is
8640 reportedly used quite little in the wild. Found by "skruffy" on
8641 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
8642 - Free directory authority certificate download statuses on exit
8643 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
8645 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
8646 - If the guard we choose first doesn't answer, we would try the
8647 second guard, but once we connected to the second guard we would
8648 abandon it and retry the first one, slowing down bootstrapping.
8649 The fix is to treat all our initially chosen guards as acceptable
8650 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
8651 - Fix an assertion failure that would occur when disabling the
8652 ORPort setting on a running Tor process while accounting was
8653 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
8654 - When examining the list of network interfaces to find our address,
8655 do not consider non-running or disabled network interfaces. Fixes
8656 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
8657 - Avoid an off-by-one error when checking buffer boundaries when
8658 formatting the exit status of a pluggable transport helper.
8659 This is probably not an exploitable bug, but better safe than
8660 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
8663 o Removed code and features:
8664 - Clients now reject any directory authority certificates lacking
8665 a dir-key-crosscert element. These have been included since
8666 0.2.1.9-alpha, so there's no real reason for them to be optional
8667 any longer. Completes proposal 157. Resolves ticket 10162.
8668 - Remove all code that existed to support the v2 directory system,
8669 since there are no longer any v2 directory authorities. Resolves
8671 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
8672 options, which were used for designating authorities as "Hidden
8673 service authorities". There has been no use of hidden service
8674 authorities since 0.2.2.1-alpha, when we stopped uploading or
8675 downloading v0 hidden service descriptors. Fixes bug 10881; also
8676 part of a fix for bug 10841.
8678 o Code simplification and refactoring:
8679 - Remove some old fallback code designed to keep Tor clients working
8680 in a network with only two working relays. Elsewhere in the code we
8681 have long since stopped supporting such networks, so there wasn't
8682 much point in keeping it around. Addresses ticket 9926.
8683 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
8684 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
8685 - Remove data structures which were introduced to implement the
8686 CellStatistics option: they are now redundant with the addition
8687 of a timestamp to the regular packed_cell_t data structure, which
8688 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
8691 o Documentation (man page) fixes:
8692 - Update manpage to describe some of the files you can expect to
8693 find in Tor's DataDirectory. Addresses ticket 9839.
8694 - Document that all but one DirPort entry must have the NoAdvertise
8695 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
8697 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
8698 - Clarify the usage and risks of setting the ContactInfo torrc line
8699 for your relay or bridge. Resolves ticket 9854.
8700 - Add anchors to the manpage so we can link to the html version of
8701 the documentation for specific options. Resolves ticket 9866.
8702 - Replace remaining references to DirServer in man page and
8703 log entries. Resolves ticket 10124.
8706 - Make the "tor-gencert" tool used by directory authority operators
8707 create 2048-bit signing keys by default (rather than 1024-bit, since
8708 1024-bit is uncomfortably small these days). Addresses ticket 10324.
8711 Changes in version 0.2.4.20 - 2013-12-22
8712 Tor 0.2.4.20 fixes potentially poor random number generation for users
8713 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
8714 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
8715 and 4) have no state file in their DataDirectory (as would happen on
8716 first start). Users who generated relay or hidden service identity
8717 keys in such a situation should discard them and generate new ones.
8719 This release also fixes a logic error that caused Tor clients to build
8720 many more preemptive circuits than they actually need.
8723 - Do not allow OpenSSL engines to replace the PRNG, even when
8724 HardwareAccel is set. The only default builtin PRNG engine uses
8725 the Intel RDRAND instruction to replace the entire PRNG, and
8726 ignores all attempts to seed it with more entropy. That's
8727 cryptographically stupid: the right response to a new alleged
8728 entropy source is never to discard all previously used entropy
8729 sources. Fixes bug 10402; works around behavior introduced in
8730 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
8732 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
8733 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
8734 - Avoid launching spurious extra circuits when a stream is pending.
8735 This fixes a bug where any circuit that _wasn't_ unusable for new
8736 streams would be treated as if it were, causing extra circuits to
8737 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
8740 - Avoid a crash bug when starting with a corrupted microdescriptor
8741 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
8742 - If we fail to dump a previously cached microdescriptor to disk, avoid
8743 freeing duplicate data later on. Fixes bug 10423; bugfix on
8744 0.2.4.13-alpha. Spotted by "bobnomnom".
8747 Changes in version 0.2.4.19 - 2013-12-11
8748 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
8749 (1986-2013). Aaron worked on diverse projects including helping to guide
8750 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
8751 transparency to the U.S government's PACER documents, and contributing
8752 design and development for Tor and Tor2Web. Aaron was one of the latest
8753 martyrs in our collective fight for civil liberties and human rights,
8754 and his death is all the more painful because he was one of us.
8756 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
8757 a new circuit handshake and link encryption that use ECC to provide
8758 better security and efficiency; makes relays better manage circuit
8759 creation requests; uses "directory guards" to reduce client enumeration
8760 risks; makes bridges collect and report statistics about the pluggable
8761 transports they support; cleans up and improves our geoip database;
8762 gets much closer to IPv6 support for clients, bridges, and relays; makes
8763 directory authorities use measured bandwidths rather than advertised
8764 ones when computing flags and thresholds; disables client-side DNS
8765 caching to reduce tracking risks; and fixes a big bug in bridge
8766 reachability testing. This release introduces two new design
8767 abstractions in the code: a new "channel" abstraction between circuits
8768 and or_connections to allow for implementing alternate relay-to-relay
8769 transports, and a new "circuitmux" abstraction storing the queue of
8770 circuits for a channel. The release also includes many stability,
8771 security, and privacy fixes.
8774 Changes in version 0.2.4.18-rc - 2013-11-16
8775 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
8776 series. It takes a variety of fixes from the 0.2.5.x branch to improve
8777 stability, performance, and better handling of edge cases.
8780 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
8781 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
8782 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
8783 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
8784 them to solve bug 6033.)
8787 - No longer stop reading or writing on cpuworker connections when
8788 our rate limiting buckets go empty. Now we should handle circuit
8789 handshake requests more promptly. Resolves bug 9731.
8790 - If we are unable to save a microdescriptor to the journal, do not
8791 drop it from memory and then reattempt downloading it. Fixes bug
8792 9645; bugfix on 0.2.2.6-alpha.
8793 - Stop trying to bootstrap all our directory information from
8794 only our first guard. Discovered while fixing bug 9946; bugfix
8796 - The new channel code sometimes lost track of in-progress circuits,
8797 causing long-running clients to stop building new circuits. The
8798 fix is to always call circuit_n_chan_done(chan, 0) from
8799 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
8801 o Minor bugfixes (on 0.2.4.x):
8802 - Correctly log long IPv6 exit policies, instead of truncating them
8803 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
8804 - Our default TLS ecdhe groups were backwards: we meant to be using
8805 P224 for relays (for performance win) and P256 for bridges (since
8806 it is more common in the wild). Instead we had it backwards. After
8807 reconsideration, we decided that the default should be P256 on all
8808 hosts, since its security is probably better, and since P224 is
8809 reportedly used quite little in the wild. Found by "skruffy" on
8810 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
8811 - Free directory authority certificate download statuses on exit
8812 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
8814 o Minor bugfixes (on 0.2.3.x and earlier):
8815 - If the guard we choose first doesn't answer, we would try the
8816 second guard, but once we connected to the second guard we would
8817 abandon it and retry the first one, slowing down bootstrapping.
8818 The fix is to treat all our initially chosen guards as acceptable
8819 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
8820 - Fix an assertion failure that would occur when disabling the
8821 ORPort setting on a running Tor process while accounting was
8822 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
8823 - When examining the list of network interfaces to find our address,
8824 do not consider non-running or disabled network interfaces. Fixes
8825 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
8826 - Avoid an off-by-one error when checking buffer boundaries when
8827 formatting the exit status of a pluggable transport helper.
8828 This is probably not an exploitable bug, but better safe than
8829 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
8832 o Minor features (protecting client timestamps):
8833 - Clients no longer send timestamps in their NETINFO cells. These were
8834 not used for anything, and they provided one small way for clients
8835 to be distinguished from each other as they moved from network to
8836 network or behind NAT. Implements part of proposal 222.
8837 - Clients now round timestamps in INTRODUCE cells down to the nearest
8838 10 minutes. If a new Support022HiddenServices option is set to 0, or
8839 if it's set to "auto" and the feature is disabled in the consensus,
8840 the timestamp is sent as 0 instead. Implements part of proposal 222.
8841 - Stop sending timestamps in AUTHENTICATE cells. This is not such
8842 a big deal from a security point of view, but it achieves no actual
8843 good purpose, and isn't needed. Implements part of proposal 222.
8844 - Reduce down accuracy of timestamps in hidden service descriptors.
8845 Implements part of proposal 222.
8847 o Minor features (other):
8848 - Improve the circuit queue out-of-memory handler. Previously, when
8849 we ran low on memory, we'd close whichever circuits had the most
8850 queued cells. Now, we close those that have the *oldest* queued
8851 cells, on the theory that those are most responsible for us
8852 running low on memory. Based on analysis from a forthcoming paper
8853 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
8854 - Generate bootstrapping status update events correctly when fetching
8855 microdescriptors. Fixes bug 9927.
8856 - Update to the October 2 2013 Maxmind GeoLite Country database.
8858 o Documentation fixes:
8859 - Clarify the usage and risks of setting the ContactInfo torrc line
8860 for your relay or bridge. Resolves ticket 9854.
8861 - Add anchors to the manpage so we can link to the html version of
8862 the documentation for specific options. Resolves ticket 9866.
8863 - Replace remaining references to DirServer in man page and
8864 log entries. Resolves ticket 10124.
8867 Changes in version 0.2.5.1-alpha - 2013-10-02
8868 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
8869 on Linux, allows bridges that offer pluggable transports to report usage
8870 statistics, fixes many issues to make testing easier, and provides
8871 a pile of minor features and bugfixes that have been waiting for a
8872 release of the new branch.
8874 This is the first alpha release in a new series, so expect there to
8875 be bugs. Users who would rather test out a more stable branch should
8876 stay with 0.2.4.x for now.
8878 o Major features (security):
8879 - Use the seccomp2 syscall filtering facility on Linux to limit
8880 which system calls Tor can invoke. This is an experimental,
8881 Linux-only feature to provide defense-in-depth against unknown
8882 attacks. To try turning it on, set "Sandbox 1" in your torrc
8883 file. Please be ready to report bugs. We hope to add support
8884 for better sandboxing in the future, including more fine-grained
8885 filters, better division of responsibility, and support for more
8886 platforms. This work has been done by Cristian-Matei Toader for
8887 Google Summer of Code.
8888 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
8889 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
8890 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
8891 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
8892 them to solve bug 6033.)
8894 o Major features (other):
8895 - Add support for passing arguments to managed pluggable transport
8896 proxies. Implements ticket 3594.
8897 - Bridges now track GeoIP information and the number of their users
8898 even when pluggable transports are in use, and report usage
8899 statistics in their extra-info descriptors. Resolves tickets 4773
8901 - Make testing Tor networks bootstrap better: lower directory fetch
8902 retry schedules and maximum interval without directory requests,
8903 and raise maximum download tries. Implements ticket 6752.
8904 - Add make target 'test-network' to run tests on a Chutney network.
8905 Implements ticket 8530.
8906 - The ntor handshake is now on-by-default, no matter what the
8907 directory authorities recommend. Implements ticket 8561.
8910 - Instead of writing destroy cells directly to outgoing connection
8911 buffers, queue them and intersperse them with other outgoing cells.
8912 This can prevent a set of resource starvation conditions where too
8913 many pending destroy cells prevent data cells from actually getting
8914 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
8915 bugfix on 0.2.0.1-alpha.
8916 - If we are unable to save a microdescriptor to the journal, do not
8917 drop it from memory and then reattempt downloading it. Fixes bug
8918 9645; bugfix on 0.2.2.6-alpha.
8919 - The new channel code sometimes lost track of in-progress circuits,
8920 causing long-running clients to stop building new circuits. The
8921 fix is to always call circuit_n_chan_done(chan, 0) from
8922 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
8925 - Tor now builds each source file in two modes: a mode that avoids
8926 exposing identifiers needlessly, and another mode that exposes
8927 more identifiers for testing. This lets the compiler do better at
8928 optimizing the production code, while enabling us to take more
8929 radical measures to let the unit tests test things.
8930 - The production builds no longer include functions used only in
8931 the unit tests; all functions exposed from a module only for
8932 unit-testing are now static in production builds.
8933 - Add an --enable-coverage configuration option to make the unit
8934 tests (and a new src/or/tor-cov target) to build with gcov test
8938 - We now have rudimentary function mocking support that our unit
8939 tests can use to test functions in isolation. Function mocking
8940 lets the tests temporarily replace a function's dependencies with
8941 stub functions, so that the tests can check the function without
8942 invoking the other functions it calls.
8943 - Add more unit tests for the <circid,channel>->circuit map, and
8944 the destroy-cell-tracking code to fix bug 7912.
8945 - Unit tests for failing cases of the TAP onion handshake.
8946 - More unit tests for address-manipulation functions.
8948 o Minor features (protecting client timestamps):
8949 - Clients no longer send timestamps in their NETINFO cells. These were
8950 not used for anything, and they provided one small way for clients
8951 to be distinguished from each other as they moved from network to
8952 network or behind NAT. Implements part of proposal 222.
8953 - Clients now round timestamps in INTRODUCE cells down to the nearest
8954 10 minutes. If a new Support022HiddenServices option is set to 0, or
8955 if it's set to "auto" and the feature is disabled in the consensus,
8956 the timestamp is sent as 0 instead. Implements part of proposal 222.
8957 - Stop sending timestamps in AUTHENTICATE cells. This is not such
8958 a big deal from a security point of view, but it achieves no actual
8959 good purpose, and isn't needed. Implements part of proposal 222.
8960 - Reduce down accuracy of timestamps in hidden service descriptors.
8961 Implements part of proposal 222.
8963 o Minor features (config options):
8964 - Config (torrc) lines now handle fingerprints which are missing
8965 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
8966 - Support a --dump-config option to print some or all of the
8967 configured options. Mainly useful for debugging the command-line
8968 option parsing code. Helps resolve ticket 4647.
8969 - Raise awareness of safer logging: notify user of potentially
8970 unsafe config options, like logging more verbosely than severity
8971 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
8972 - Add a new configuration option TestingV3AuthVotingStartOffset
8973 that bootstraps a network faster by changing the timing for
8974 consensus votes. Addresses ticket 8532.
8975 - Add a new torrc option "ServerTransportOptions" that allows
8976 bridge operators to pass configuration parameters to their
8977 pluggable transports. Resolves ticket 8929.
8978 - The config (torrc) file now accepts bandwidth and space limits in
8979 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
8980 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
8983 o Minor features (build):
8984 - Add support for `--library-versions` flag. Implements ticket 6384.
8985 - Return the "unexpected sendme" warnings to a warn severity, but make
8986 them rate limited, to help diagnose ticket 8093.
8987 - Detect a missing asciidoc, and warn the user about it, during
8988 configure rather than at build time. Fixes issue 6506. Patch from
8991 o Minor features (other):
8992 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
8993 sockets in a single system call. Implements ticket 5129.
8994 - Log current accounting state (bytes sent and received + remaining
8995 time for the current accounting period) in the relay's heartbeat
8996 message. Implements ticket 5526; patch from Peter Retzlaff.
8997 - Implement the TRANSPORT_LAUNCHED control port event that
8998 notifies controllers about new launched pluggable
8999 transports. Resolves ticket 5609.
9000 - If we're using the pure-C 32-bit curve25519_donna implementation
9001 of curve25519, build it with the -fomit-frame-pointer option to
9002 make it go faster on register-starved hosts. This improves our
9003 handshake performance by about 6% on i386 hosts without nacl.
9005 - Update to the September 4 2013 Maxmind GeoLite Country database.
9008 - Set the listen() backlog limit to the largest actually supported
9009 on the system, not to the value in a header file. Fixes bug 9716;
9010 bugfix on every released Tor.
9011 - No longer accept malformed http headers when parsing urls from
9012 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
9013 bugfix on 0.0.6pre1.
9014 - In munge_extrainfo_into_routerinfo(), check the return value of
9015 memchr(). This would have been a serious issue if we ever passed
9016 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
9018 - On the chance that somebody manages to build Tor on a
9019 platform where time_t is unsigned, correct the way that
9020 microdesc_add_to_cache() handles negative time arguments.
9021 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
9022 - Reject relative control socket paths and emit a warning. Previously,
9023 single-component control socket paths would be rejected, but Tor
9024 would not log why it could not validate the config. Fixes bug 9258;
9025 bugfix on 0.2.3.16-alpha.
9027 o Minor bugfixes (command line):
9028 - Use a single command-line parser for parsing torrc options on the
9029 command line and for finding special command-line options to avoid
9030 inconsistent behavior for torrc option arguments that have the same
9031 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
9033 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
9034 9573; bugfix on 0.0.9pre5.
9036 o Minor fixes (build, auxiliary programs):
9037 - Stop preprocessing the "torify" script with autoconf, since
9038 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
9040 - The tor-fw-helper program now follows the standard convention and
9041 exits with status code "0" on success. Fixes bug 9030; bugfix on
9042 0.2.3.1-alpha. Patch by Arlo Breault.
9043 - Corrected ./configure advice for what openssl dev package you should
9044 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
9046 o Minor code improvements:
9047 - Remove constants and tests for PKCS1 padding; it's insecure and
9048 shouldn't be used for anything new. Fixes bug 8792; patch
9050 - Remove instances of strcpy() from the unit tests. They weren't
9051 hurting anything, since they were only in the unit tests, but it's
9052 embarassing to have strcpy() in the code at all, and some analysis
9053 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
9054 0.2.3.8-alpha. Patch from Arlo Breault.
9057 - Remove migration code from when we renamed the "cached-routers"
9058 file to "cached-descriptors" back in 0.2.0.8-alpha. This
9059 incidentally resolves ticket 6502 by cleaning up the related code
9060 a bit. Patch from Akshay Hebbar.
9062 o Code simplification and refactoring:
9063 - Extract the common duplicated code for creating a subdirectory
9064 of the data directory and writing to a file in it. Fixes ticket
9065 4282; patch from Peter Retzlaff.
9066 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
9067 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
9068 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
9069 - Add a set of accessor functions for the circuit timeout data
9070 structure. Fixes ticket 6153; patch from "piet".
9071 - Clean up exit paths from connection_listener_new(). Closes ticket
9072 8789. Patch from Arlo Breault.
9073 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
9074 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
9075 - Use a doubly-linked list to implement the global circuit list.
9076 Resolves ticket 9108. Patch from Marek Majkowski.
9077 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
9080 Changes in version 0.2.4.17-rc - 2013-09-05
9081 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
9082 series. It adds an emergency step to help us tolerate the massive
9083 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
9084 circuit-level handshakes now effectively jump the queue compared to
9085 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
9086 big bug hindering bridge reachability tests.
9089 - Relays now process the new "NTor" circuit-level handshake requests
9090 with higher priority than the old "TAP" circuit-level handshake
9091 requests. We still process some TAP requests to not totally starve
9092 0.2.3 clients when NTor becomes popular. A new consensus parameter
9093 "NumNTorsPerTAP" lets us tune the balance later if we need to.
9094 Implements ticket 9574.
9097 - If the circuit build timeout logic is disabled (via the consensus,
9098 or because we are an authority), then don't build testing circuits.
9099 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
9100 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
9101 previously they did not, which prevented them from receiving
9102 successful connections from relays for self-test or bandwidth
9103 testing. Also, when a relay is extending a circuit to a bridge,
9104 it needs to send a NETINFO cell, even when the bridge hasn't sent
9105 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
9106 - If the time to download the next old-style networkstatus is in
9107 the future, do not decline to consider whether to download the
9108 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
9112 - Avoid double-closing the listener socket in our socketpair()
9113 replacement (used on Windows) in the case where the addresses on
9114 our opened sockets don't match what we expected. Fixes bug 9400;
9115 bugfix on 0.0.2pre7. Found by Coverity.
9117 o Minor fixes (config options):
9118 - Avoid overflows when the user sets MaxCircuitDirtiness to a
9119 ridiculously high value, by imposing a (ridiculously high) 30-day
9120 maximum on MaxCircuitDirtiness.
9121 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
9122 message is logged at notice, not at info.
9123 - Warn and fail if a server is configured not to advertise any
9124 ORPorts at all. (We need *something* to put in our descriptor,
9125 or we just won't work.)
9128 - Track how many "TAP" and "NTor" circuit handshake requests we get,
9129 and how many we complete, and log it every hour to help relay
9130 operators follow trends in network load. Addresses ticket 9658.
9131 - Update to the August 7 2013 Maxmind GeoLite Country database.
9134 Changes in version 0.2.4.16-rc - 2013-08-10
9135 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
9136 series. It fixes several crash bugs in the 0.2.4 branch.
9139 - Fix a bug in the voting algorithm that could yield incorrect results
9140 when a non-naming authority declared too many flags. Fixes bug 9200;
9141 bugfix on 0.2.0.3-alpha.
9142 - Fix an uninitialized read that could in some cases lead to a remote
9143 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
9144 Anybody running a hidden service on the experimental 0.2.4.x
9145 branch should upgrade. (This is, so far as we know, unrelated to
9147 - Avoid an assertion failure when processing DNS replies without the
9148 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
9149 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
9150 0.2.4.15-rc. Found by stem integration tests.
9153 - Fix an invalid memory read that occured when a pluggable
9154 transport proxy failed its configuration protocol.
9155 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
9156 - When evaluating whether to use a connection that we haven't
9157 decided is canonical using a recent link protocol version,
9158 decide that it's canonical only if it used address _does_
9159 match the desired address. Fixes bug 9309; bugfix on
9160 0.2.4.4-alpha. Reported by skruffy.
9161 - Make the default behavior of NumDirectoryGuards be to track
9162 NumEntryGuards. Now a user who changes only NumEntryGuards will get
9163 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
9164 - Fix a spurious compilation warning with some older versions of
9165 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
9168 - Update to the July 3 2013 Maxmind GeoLite Country database.
9171 Changes in version 0.2.4.15-rc - 2013-07-01
9172 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
9173 series. It fixes a few smaller bugs, but generally appears stable.
9174 Please test it and let us know whether it is!
9177 - When receiving a new configuration file via the control port's
9178 LOADCONF command, do not treat the defaults file as absent.
9179 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
9182 - Issue a warning when running with the bufferevents backend enabled.
9183 It's still not stable, and people should know that they're likely
9184 to hit unexpected problems. Closes ticket 9147.
9187 Changes in version 0.2.4.14-alpha - 2013-06-18
9188 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
9189 present in 0.2.4.13-alpha.
9192 - When we have too much memory queued in circuits (according to a new
9193 MaxMemInCellQueues option), close the circuits consuming the most
9194 memory. This prevents us from running out of memory as a relay if
9195 circuits fill up faster than they can be drained. Fixes bug 9063;
9196 bugfix on the 54th commit of Tor. This bug is a further fix beyond
9197 bug 6252, whose fix was merged into 0.2.3.21-rc.
9199 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
9200 where we tried to solve this issue simply by imposing an upper limit
9201 on the number of queued cells for a single circuit. That approach
9202 proved to be problematic, since there are ways to provoke clients to
9203 send a number of cells in excess of any such reasonable limit. Fixes
9204 bug 9072; bugfix on 0.2.4.13-alpha.
9206 - Limit hidden service descriptors to at most ten introduction
9207 points, to slow one kind of guard enumeration. Fixes bug 9002;
9208 bugfix on 0.1.1.11-alpha.
9211 Changes in version 0.2.4.13-alpha - 2013-06-14
9212 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
9213 vulnerabilities, makes socks5 username/password circuit isolation
9214 actually actually work (this time for sure!), and cleans up a bunch
9215 of other issues in preparation for a release candidate.
9217 o Major bugfixes (robustness):
9218 - Close any circuit that has too many cells queued on it. Fixes
9219 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
9220 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
9221 - Prevent the get_freelists() function from running off the end of
9222 the list of freelists if it somehow gets an unrecognized
9223 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
9225 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
9226 when an exit connection with optimistic data succeeds immediately
9227 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
9229 - Fix a directory authority crash bug when building a consensus
9230 using an older consensus as its basis. Fixes bug 8833. Bugfix
9234 - Avoid a memory leak where we would leak a consensus body when we
9235 find that a consensus which we couldn't previously verify due to
9236 missing certificates is now verifiable. Fixes bug 8719; bugfix
9238 - We used to always request authority certificates by identity digest,
9239 meaning we'd get the newest one even when we wanted one with a
9240 different signing key. Then we would complain about being given
9241 a certificate we already had, and never get the one we really
9242 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
9243 resource to request the one we want. Fixes bug 5595; bugfix on
9245 - Follow the socks5 protocol when offering username/password
9246 authentication. The fix for bug 8117 exposed this bug, and it
9247 turns out real-world applications like Pidgin do care. Bugfix on
9248 0.2.3.2-alpha; fixes bug 8879.
9249 - Prevent failures on Windows Vista and later when rebuilding the
9250 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
9251 bugfix on 0.2.4.12-alpha.
9254 - Fix an impossible buffer overrun in the AES unit tests. Fixes
9255 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
9256 - If for some reason we fail to write a microdescriptor while
9257 rebuilding the cache, do not let the annotations from that
9258 microdescriptor linger in the cache file, and do not let the
9259 microdescriptor stay recorded as present in its old location.
9260 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
9261 - Fix a memory leak that would occur whenever a configuration
9262 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
9263 - Paste the description for PathBias parameters from the man
9264 page into or.h, so the code documents them too. Fixes bug 7982;
9265 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
9266 - Relays now treat a changed IPv6 ORPort as sufficient reason to
9267 publish an updated descriptor. Fixes bug 6026; bugfix on
9269 - When launching a resolve request on behalf of an AF_UNIX control
9270 socket, omit the address field of the new entry connection, used in
9271 subsequent controller events, rather than letting tor_dup_addr()
9272 set it to "<unknown address type>". Fixes bug 8639; bugfix on
9275 o Minor bugfixes (log messages):
9276 - Fix a scaling issue in the path bias accounting code that
9277 resulted in "Bug:" log messages from either
9278 pathbias_scale_close_rates() or pathbias_count_build_success().
9279 This represents a bugfix on a previous bugfix: the original fix
9280 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
9282 - Give a less useless error message when the user asks for an IPv4
9283 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
9287 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
9288 to tolerate bug 8093 for now.
9289 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
9290 in directory authority votes to describe whether they have enough
9291 measured bandwidths to ignore advertised (relay descriptor)
9292 bandwidth claims. Resolves ticket 8711.
9293 - Update to the June 5 2013 Maxmind GeoLite Country database.
9295 o Removed documentation:
9296 - Remove some of the older contents of doc/ as obsolete; move others
9297 to torspec.git. Fixes bug 8965.
9299 o Code simplification and refactoring:
9300 - Avoid using character buffers when constructing most directory
9301 objects: this approach was unwieldy and error-prone. Instead,
9302 build smartlists of strings, and concatenate them when done.
9305 Changes in version 0.2.4.12-alpha - 2013-04-18
9306 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
9307 process for lengthening the guard rotation period, makes directory
9308 authority opinions in the consensus a bit less gameable, makes socks5
9309 username/password circuit isolation actually work, and fixes a wide
9310 variety of other issues.
9313 - Raise the default time that a client keeps an entry guard from
9314 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
9315 2012 paper. (We would make it even longer, but we need better client
9316 load balancing first.) Also, make the guard lifetime controllable
9317 via a new GuardLifetime torrc option and a GuardLifetime consensus
9318 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
9319 - Directory authorities now prefer using measured bandwidths to
9320 advertised ones when computing flags and thresholds. Resolves
9322 - Directory authorities that have more than a threshold number
9323 of relays with measured bandwidths now treat relays with unmeasured
9324 bandwidths as having bandwidth 0. Resolves ticket 8435.
9326 o Major bugfixes (assert / resource use):
9327 - Avoid a bug where our response to TLS renegotiation under certain
9328 network conditions could lead to a busy-loop, with 100% CPU
9329 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
9330 - Avoid an assertion when we discover that we'd like to write a cell
9331 onto a closing connection: just discard the cell. Fixes another
9332 case of bug 7350; bugfix on 0.2.4.4-alpha.
9334 o Major bugfixes (client-side privacy):
9335 - When we mark a circuit as unusable for new circuits, have it
9336 continue to be unusable for new circuits even if MaxCircuitDirtiness
9337 is increased too much at the wrong time, or the system clock jumps
9338 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
9339 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
9340 which have resolved to internal addresses") is set, apply that
9341 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
9342 - When an exit relay rejects a stream with reason "exit policy", but
9343 we only know an exit policy summary (e.g. from the microdesc
9344 consensus) for it, do not mark the relay as useless for all exiting.
9345 Instead, mark just the circuit as unsuitable for that particular
9346 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
9347 - Allow applications to get proper stream isolation with
9348 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
9349 username/password authentication also offer "no authentication". Tor
9350 had previously preferred "no authentication", so the applications
9351 never actually sent Tor their auth details. Now Tor selects
9352 username/password authentication if it's offered. You can disable
9353 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
9354 bug 8117; bugfix on 0.2.3.3-alpha.
9356 o Major bugfixes (other):
9357 - When unable to find any working directory nodes to use as a
9358 directory guard, give up rather than adding the same non-working
9359 nodes to the directory guard list over and over. Fixes bug 8231;
9360 bugfix on 0.2.4.8-alpha.
9363 - Reject as invalid most directory objects containing a NUL.
9364 Belt-and-suspender fix for bug 8037.
9365 - In our testsuite, create temporary directories with a bit more
9366 entropy in their name to make name collisions less likely. Fixes
9368 - Add CACHED keyword to ADDRMAP events in the control protocol
9369 to indicate whether a DNS result will be cached or not. Resolves
9371 - Update to the April 3 2013 Maxmind GeoLite Country database.
9373 o Minor features (build):
9374 - Detect and reject attempts to build Tor with threading support
9375 when OpenSSL has been compiled without threading support.
9377 - Clarify that when autoconf is checking for nacl, it is checking
9378 specifically for nacl with a fast curve25519 implementation.
9380 - Warn if building on a platform with an unsigned time_t: there
9381 are too many places where Tor currently assumes that time_t can
9382 hold negative values. We'd like to fix them all, but probably
9385 o Minor bugfixes (build):
9386 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
9387 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
9388 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
9389 - Add the old src/or/micro-revision.i filename to CLEANFILES.
9390 On the off chance that somebody has one, it will go away as soon
9391 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
9392 - Build Tor correctly on 32-bit platforms where the compiler can build
9393 but not run code using the "uint128_t" construction. Fixes bug 8587;
9394 bugfix on 0.2.4.8-alpha.
9395 - Fix compilation warning with some versions of clang that would
9396 prefer the -Wswitch-enum compiler flag to warn about switch
9397 statements with missing enum values, even if those switch
9398 statements have a "default:" statement. Fixes bug 8598; bugfix
9401 o Minor bugfixes (protocol):
9402 - Fix the handling of a TRUNCATE cell when it arrives while the
9403 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
9404 - Fix a misframing issue when reading the version numbers in a
9405 VERSIONS cell. Previously we would recognize [00 01 00 02] as
9406 'version 1, version 2, and version 0x100', when it should have
9407 only included versions 1 and 2. Fixes bug 8059; bugfix on
9408 0.2.0.10-alpha. Reported pseudonymously.
9409 - Make the format and order of STREAM events for DNS lookups
9410 consistent among the various ways to launch DNS lookups. Fixes
9411 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
9412 - Correct our check for which versions of Tor support the EXTEND2
9413 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
9414 later, when support was really added in version 0.2.4.8-alpha.
9415 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
9417 o Minor bugfixes (other):
9418 - Correctly store microdescriptors and extrainfo descriptors with
9419 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
9420 Bug reported by "cypherpunks".
9421 - Increase the width of the field used to remember a connection's
9422 link protocol version to two bytes. Harmless for now, since the
9423 only currently recognized versions are one byte long. Reported
9424 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
9425 - If the state file's path bias counts are invalid (presumably from a
9426 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
9427 additional checks and log messages to the scaling of Path Bias
9428 counts, in case there still are remaining issues with scaling.
9429 Should help resolve bug 8235.
9430 - Eliminate several instances where we use "Nickname=ID" to refer to
9431 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
9432 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
9433 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
9435 o Minor bugfixes (syscalls):
9436 - Always check the return values of functions fcntl() and
9437 setsockopt(). We don't believe these are ever actually failing in
9438 practice, but better safe than sorry. Also, checking these return
9439 values should please analysis tools like Coverity. Patch from
9440 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
9441 - Use direct writes rather than stdio when building microdescriptor
9442 caches, in an attempt to mitigate bug 8031, or at least make it
9445 o Minor bugfixes (config):
9446 - When rejecting a configuration because we were unable to parse a
9447 quoted string, log an actual error message. Fixes bug 7950; bugfix
9449 - Behave correctly when the user disables LearnCircuitBuildTimeout
9450 but doesn't tell us what they would like the timeout to be. Fixes
9451 bug 6304; bugfix on 0.2.2.14-alpha.
9452 - When autodetecting the number of CPUs, use the number of available
9453 CPUs in preference to the number of configured CPUs. Inform the
9454 user if this reduces the number of available CPUs. Fixes bug 8002;
9455 bugfix on 0.2.3.1-alpha.
9456 - Make it an error when you set EntryNodes but disable UseGuardNodes,
9457 since it will (surprisingly to some users) ignore EntryNodes. Fixes
9458 bug 8180; bugfix on 0.2.3.11-alpha.
9459 - Allow TestingTorNetworks to override the 4096-byte minimum for
9460 the Fast threshold. Otherwise they can't bootstrap until they've
9461 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
9462 - Fix some logic errors when the user manually overrides the
9463 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
9466 o Minor bugfixes (log messages to help diagnose bugs):
9467 - If we fail to free a microdescriptor because of bug 7164, log
9468 the filename and line number from which we tried to free it.
9469 - Add another diagnostic to the heartbeat message: track and log
9470 overhead that TLS is adding to the data we write. If this is
9471 high, we are sending too little data to SSL_write at a time.
9472 Diagnostic for bug 7707.
9473 - Add more detail to a log message about relaxed timeouts, to help
9475 - Warn more aggressively when flushing microdescriptors to a
9476 microdescriptor cache fails, in an attempt to mitigate bug 8031,
9477 or at least make it more diagnosable.
9478 - Improve debugging output to help track down bug 8185 ("Bug:
9479 outgoing relay cell has n_chan==NULL. Dropping.")
9480 - Log the purpose of a path-bias testing circuit correctly.
9481 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
9483 o Minor bugfixes (0.2.4.x log messages that were too noisy):
9484 - Don't attempt to relax the timeout of already opened 1-hop circuits.
9485 They might never timeout. This should eliminate some/all cases of
9486 the relaxed timeout log message.
9487 - Use circuit creation time for network liveness evaluation. This
9488 should eliminate warning log messages about liveness caused
9489 by changes in timeout evaluation. Fixes bug 6572; bugfix on
9491 - Reduce a path bias length check from notice to info. The message
9492 is triggered when creating controller circuits. Fixes bug 8196;
9493 bugfix on 0.2.4.8-alpha.
9494 - Fix a path state issue that triggered a notice during relay startup.
9495 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
9496 - Reduce occurrences of warns about circuit purpose in
9497 connection_ap_expire_building(). Fixes bug 8477; bugfix on
9500 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
9501 - If we encounter a write failure on a SOCKS connection before we
9502 finish our SOCKS handshake, don't warn that we closed the
9503 connection before we could send a SOCKS reply. Fixes bug 8427;
9504 bugfix on 0.1.0.1-rc.
9505 - Correctly recognize that [::1] is a loopback address. Fixes
9506 bug 8377; bugfix on 0.2.1.3-alpha.
9507 - Fix a directory authority warn caused when we have a large amount
9508 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
9509 - Don't log inappropriate heartbeat messages when hibernating: a
9510 hibernating node is _expected_ to drop out of the consensus,
9511 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
9512 bugfix on 0.2.3.1-alpha.
9513 - Don't complain about bootstrapping problems while hibernating.
9514 These complaints reflect a general code problem, but not one
9515 with any problematic effects (no connections are actually
9516 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
9518 o Documentation fixes:
9519 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
9520 names match. Fixes bug 7768.
9521 - Make the torify manpage no longer refer to tsocks; torify hasn't
9522 supported tsocks since 0.2.3.14-alpha.
9523 - Make the tor manpage no longer reference tsocks.
9524 - Fix the GeoIPExcludeUnknown documentation to refer to
9525 ExcludeExitNodes rather than the currently nonexistent
9526 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
9529 - The tor-tsocks.conf is no longer distributed or installed. We
9530 recommend that tsocks users use torsocks instead. Resolves
9534 Changes in version 0.2.4.11-alpha - 2013-03-11
9535 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
9536 more robust, makes hidden service authentication work again, and
9537 resolves a DPI fingerprint for Tor's SSL transport.
9539 o Major features (directory authorities):
9540 - Directory authorities now support a new consensus method (17)
9541 where they cap the published bandwidth of servers for which
9542 insufficient bandwidth measurements exist. Fixes part of bug 2286.
9543 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
9544 serve any v2 directory information. Now we can test disabling the
9545 old deprecated v2 directory format, and see whether doing so has
9546 any effect on network load. Begins to fix bug 6783.
9547 - Directory authorities now include inside each vote a statement of
9548 the performance thresholds they used when assigning flags.
9549 Implements ticket 8151.
9551 o Major bugfixes (directory authorities):
9552 - Stop marking every relay as having been down for one hour every
9553 time we restart a directory authority. These artificial downtimes
9554 were messing with our Stable and Guard flag calculations. Fixes
9555 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
9557 o Major bugfixes (hidden services):
9558 - Allow hidden service authentication to succeed again. When we
9559 refactored the hidden service introduction code back
9560 in 0.2.4.1-alpha, we didn't update the code that checks
9561 whether authentication information is present, causing all
9562 authentication checks to return "false". Fix for bug 8207; bugfix
9563 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
9565 o Minor features (relays, bridges):
9566 - Make bridge relays check once a minute for whether their IP
9567 address has changed, rather than only every 15 minutes. Resolves
9569 - Refactor resolve_my_address() so it returns the method by which we
9570 decided our public IP address (explicitly configured, resolved from
9571 explicit hostname, guessed from interfaces, learned by gethostname).
9572 Now we can provide more helpful log messages when a relay guesses
9573 its IP address incorrectly (e.g. due to unexpected lines in
9574 /etc/hosts). Resolves ticket 2267.
9575 - Teach bridge-using clients to avoid 0.2.2 bridges when making
9576 microdescriptor-related dir requests, and only fall back to normal
9577 descriptors if none of their bridges can handle microdescriptors
9578 (as opposed to the fix in ticket 4013, which caused them to fall
9579 back to normal descriptors if *any* of their bridges preferred
9580 them). Resolves ticket 4994.
9581 - Randomize the lifetime of our SSL link certificate, so censors can't
9582 use the static value for filtering Tor flows. Resolves ticket 8443;
9583 related to ticket 4014 which was included in 0.2.2.33.
9584 - Support a new version of the link protocol that allows 4-byte circuit
9585 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
9586 a possible resource exhaustion issue. Closes ticket 7351; implements
9589 o Minor features (portability):
9590 - Tweak the curve25519-donna*.c implementations to tolerate systems
9591 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
9592 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
9593 the signs of types during autoconf. This is better than our old
9594 approach, which didn't work when cross-compiling.
9595 - Detect the sign of enum values, rather than assuming that MSC is the
9596 only compiler where enum types are all signed. Fixes bug 7727;
9597 bugfix on 0.2.4.10-alpha.
9599 o Minor features (other):
9600 - Say "KBytes" rather than "KB" in the man page (for various values
9601 of K), to further reduce confusion about whether Tor counts in
9602 units of memory or fractions of units of memory. Resolves ticket 7054.
9603 - Clear the high bit on curve25519 public keys before passing them to
9604 our backend, in case we ever wind up using a backend that doesn't do
9605 so itself. If we used such a backend, and *didn't* clear the high bit,
9606 we could wind up in a situation where users with such backends would
9607 be distinguishable from users without. Fixes bug 8121; bugfix on
9609 - Update to the March 6 2013 Maxmind GeoLite Country database.
9611 o Minor bugfixes (clients):
9612 - When we receive a RELAY_END cell with the reason DONE, or with no
9613 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
9614 status as "connection refused". Previously we reported these cases
9615 as success but then immediately closed the connection. Fixes bug
9616 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
9617 - Downgrade an assertion in connection_ap_expire_beginning to an
9618 LD_BUG message. The fix for bug 8024 should prevent this message
9619 from displaying, but just in case, a warn that we can diagnose
9620 is better than more assert crashes. Fixes bug 8065; bugfix on
9622 - Lower path use bias thresholds to .80 for notice and .60 for warn.
9623 Also make the rate limiting flags for the path use bias log messages
9624 independent from the original path bias flags. Fixes bug 8161;
9625 bugfix on 0.2.4.10-alpha.
9627 o Minor bugfixes (relays):
9628 - Stop trying to resolve our hostname so often (e.g. every time we
9629 think about doing a directory fetch). Now we reuse the cached
9630 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
9631 and 2410 (bugfix on 0.1.2.2-alpha).
9632 - Stop sending a stray "(null)" in some cases for the server status
9633 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
9635 - When choosing which stream on a formerly stalled circuit to wake
9636 first, make better use of the platform's weak RNG. Previously,
9637 we had been using the % ("modulo") operator to try to generate a
9638 1/N chance of picking each stream, but this behaves badly with
9639 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
9641 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
9642 Irix's random() only return 15 bits; Solaris's random() returns more
9643 bits but its RAND_MAX says it only returns 15, and so on. Motivated
9644 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
9646 o Minor bugfixes (directory authorities):
9647 - Directory authorities now use less space when formatting identical
9648 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
9651 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
9652 - Avoid leaking memory if we fail to compute a consensus signature
9653 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
9654 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
9656 - Fix a memory leak during safe-cookie controller authentication.
9657 Bugfix on 0.2.3.13-alpha.
9658 - Avoid memory leak of IPv6 policy content if we fail to format it into
9659 a router descriptor. Bugfix on 0.2.4.7-alpha.
9661 o Minor bugfixes (other code correctness issues):
9662 - Avoid a crash if we fail to generate an extrainfo descriptor.
9663 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
9665 - When detecting the largest possible file descriptor (in order to
9666 close all file descriptors when launching a new program), actually
9667 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
9668 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
9670 - Fix a copy-and-paste error when adding a missing A1 to a routerset
9671 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
9672 Bugfix on 0.2.4.10-alpha.
9673 - Fix an impossible-to-trigger integer overflow when estimating how
9674 long our onionskin queue would take. (This overflow would require us
9675 to accept 4 million onionskins before processing 100 of them.) Fixes
9676 bug 8210; bugfix on 0.2.4.10-alpha.
9678 o Code simplification and refactoring:
9679 - Add a wrapper function for the common "log a message with a
9683 Changes in version 0.2.4.10-alpha - 2013-02-04
9684 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
9685 certain attacks that flood the network with relays; changes the queue
9686 for circuit create requests from a sized-based limit to a time-based
9687 limit; resumes building with MSVC on Windows; and fixes a wide variety
9690 o Major bugfixes (directory authority):
9691 - When computing directory thresholds, ignore any rejected-as-sybil
9692 nodes during the computation so that they can't influence Fast,
9693 Guard, etc. (We should have done this for proposal 109.) Fixes
9695 - When marking a node as a likely sybil, reset its uptime metrics
9696 to zero, so that it cannot time towards getting marked as Guard,
9697 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
9701 - When a TLS write is partially successful but incomplete, remember
9702 that the flushed part has been flushed, and notice that bytes were
9703 actually written. Reported and fixed pseudonymously. Fixes bug
9704 7708; bugfix on Tor 0.1.0.5-rc.
9705 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
9706 ID: these could be used to create unexpected streams and circuits
9707 which would count as "present" to some parts of Tor but "absent"
9708 to others, leading to zombie circuits and streams or to a bandwidth
9709 denial-of-service. Fixes bug 7889; bugfix on every released version
9710 of Tor. Reported by "oftc_must_be_destroyed".
9711 - Rename all macros in our local copy of queue.h to begin with "TOR_".
9712 This change seems the only good way to permanently prevent conflicts
9713 with queue.h on various operating systems. Fixes bug 8107; bugfix
9716 o Major features (relay):
9717 - Instead of limiting the number of queued onionskins (aka circuit
9718 create requests) to a fixed, hard-to-configure number, we limit
9719 the size of the queue based on how many we expect to be able to
9720 process in a given amount of time. We estimate the time it will
9721 take to process an onionskin based on average processing time
9722 of previous onionskins. Closes ticket 7291. You'll never have to
9723 configure MaxOnionsPending again.
9725 o Major features (portability):
9726 - Resume building correctly with MSVC and Makefile.nmake. This patch
9727 resolves numerous bugs and fixes reported by ultramage, including
9728 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
9729 - Make the ntor and curve25519 code build correctly with MSVC.
9730 Fix on 0.2.4.8-alpha.
9733 - When directory authorities are computing thresholds for flags,
9734 never let the threshold for the Fast flag fall below 4096
9735 bytes. Also, do not consider nodes with extremely low bandwidths
9736 when deciding thresholds for various directory flags. This change
9737 should raise our threshold for Fast relays, possibly in turn
9738 improving overall network performance; see ticket 1854. Resolves
9740 - The Tor client now ignores sub-domain components of a .onion
9741 address. This change makes HTTP "virtual" hosting
9742 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
9743 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
9744 hosted on the same hidden service. Implements proposal 204.
9745 - We compute the overhead from passing onionskins back and forth to
9746 cpuworkers, and report it when dumping statistics in response to
9747 SIGUSR1. Supports ticket 7291.
9749 o Minor features (path selection):
9750 - When deciding whether we have enough descriptors to build circuits,
9751 instead of looking at raw relay counts, look at which fraction
9752 of (bandwidth-weighted) paths we're able to build. This approach
9753 keeps clients from building circuits if their paths are likely to
9754 stand out statistically. The default fraction of paths needed is
9755 taken from the consensus directory; you can override it with the
9756 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
9757 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
9758 and we have GeoIP information, also exclude all nodes with unknown
9759 countries "??" and "A1". This behavior is controlled by the
9760 new GeoIPExcludeUnknown option: you can make such nodes always
9761 excluded with "GeoIPExcludeUnknown 1", and disable the feature
9762 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
9763 gets you the default behavior. Implements feature 7706.
9764 - Path Use Bias: Perform separate accounting for successful circuit
9765 use. Keep separate statistics on stream attempt rates versus stream
9766 success rates for each guard. Provide configurable thresholds to
9767 determine when to emit log messages or disable use of guards that
9768 fail too many stream attempts. Resolves ticket 7802.
9770 o Minor features (log messages):
9771 - When learning a fingerprint for a bridge, log its corresponding
9772 transport type. Implements ticket 7896.
9773 - Improve the log message when "Bug/attack: unexpected sendme cell
9774 from client" occurs, to help us track bug 8093.
9777 - Remove a couple of extraneous semicolons that were upsetting the
9778 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
9779 bugfix on 0.2.2.1-alpha.
9780 - Remove a source of rounding error during path bias count scaling;
9781 don't count cannibalized circuits as used for path bias until we
9782 actually try to use them; and fix a circuit_package_relay_cell()
9783 warning message about n_chan==NULL. Fixes bug 7802.
9784 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
9785 actually link against nacl when we're configured to use it. Fixes
9786 bug 7972; bugfix on 0.2.4.8-alpha.
9787 - Compile correctly with the --disable-curve25519 option. Fixes
9788 bug 8153; bugfix on 0.2.4.8-alpha.
9790 o Build improvements:
9791 - Do not report status verbosely from autogen.sh unless the -v flag
9792 is specified. Fixes issue 4664. Patch from Onizuka.
9793 - Replace all calls to snprintf() outside of src/ext with
9794 tor_snprintf(). Also remove the #define to replace snprintf with
9795 _snprintf on Windows; they have different semantics, and all of
9796 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
9797 - Try to detect if we are ever building on a platform where
9798 memset(...,0,...) does not set the value of a double to 0.0. Such
9799 platforms are permitted by the C standard, though in practice
9800 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
9801 currently support them, but it's better to detect them and fail
9802 than to perform erroneously.
9805 - Stop exporting estimates of v2 and v3 directory traffic shares
9806 in extrainfo documents. They were unneeded and sometimes inaccurate.
9807 Also stop exporting any v2 directory request statistics. Resolves
9809 - Drop support for detecting and warning about versions of Libevent
9810 before 1.3e. Nothing reasonable ships with them any longer;
9811 warning the user about them shouldn't be needed. Resolves ticket
9814 o Code simplifications and refactoring:
9815 - Rename "isin" functions to "contains", for grammar. Resolves
9817 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
9818 with the natural logarithm function from the system libm. Resolves
9822 Changes in version 0.2.4.9-alpha - 2013-01-15
9823 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
9827 - Fix backward compatibility logic when receiving an embedded ntor
9828 handshake tunneled in a CREATE cell. This clears up the "Bug:
9829 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
9833 Changes in version 0.2.4.8-alpha - 2013-01-14
9834 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
9835 risks, adds a new stronger and faster circuit handshake, and offers
9836 stronger and faster link encryption when both sides support it.
9839 - Preliminary support for directory guards (proposal 207): when
9840 possible, clients now use their entry guards for non-anonymous
9841 directory requests. This can help prevent client enumeration. Note
9842 that this behavior only works when we have a usable consensus
9843 directory, and when options about what to download are more or less
9844 standard. In the future we should re-bootstrap from our guards,
9845 rather than re-bootstrapping from the preconfigured list of
9846 directory sources that ships with Tor. Resolves ticket 6526.
9847 - Tor relays and clients now support a better CREATE/EXTEND cell
9848 format, allowing the sender to specify multiple address, identity,
9849 and handshake types. Implements Robert Ransom's proposal 200;
9852 o Major features (new circuit handshake):
9853 - Tor now supports a new circuit extension handshake designed by Ian
9854 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
9855 circuit extension handshake, later called "TAP", was a bit slow
9856 (especially on the relay side), had a fragile security proof, and
9857 used weaker keys than we'd now prefer. The new circuit handshake
9858 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
9859 function, making it significantly more secure than the older
9860 handshake, and significantly faster. Tor can use one of two built-in
9861 pure-C curve25519-donna implementations by Adam Langley, or it
9862 can link against the "nacl" library for a tuned version if present.
9864 The built-in version is very fast for 64-bit systems when building
9865 with GCC. The built-in 32-bit version is still faster than the
9866 old TAP protocol, but using libnacl is better on most such hosts.
9868 Clients don't currently use this protocol by default, since
9869 comparatively few clients support it so far. To try it, set
9870 UseNTorHandshake to 1.
9872 Implements proposal 216; closes ticket 7202.
9874 o Major features (better link encryption):
9875 - Relays can now enable the ECDHE TLS ciphersuites when available
9876 and appropriate. These ciphersuites let us negotiate forward-secure
9877 TLS secret keys more safely and more efficiently than with our
9878 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
9879 public relays prefer the (faster) P224 group, and bridges prefer
9880 the (more common) P256 group; you can override this with the
9883 Enabling these ciphers was a little tricky, since for a long time,
9884 clients had been claiming to support them without actually doing
9885 so, in order to foil fingerprinting. But with the client-side
9886 implementation of proposal 198 in 0.2.3.17-beta, clients can now
9887 match the ciphers from recent Firefox versions *and* list the
9888 ciphers they actually mean, so relays can believe such clients
9889 when they advertise ECDHE support in their TLS ClientHello messages.
9891 This feature requires clients running 0.2.3.17-beta or later,
9892 and requires both sides to be running OpenSSL 1.0.0 or later
9893 with ECC support. OpenSSL 1.0.1, with the compile-time option
9894 "enable-ec_nistp_64_gcc_128", is highly recommended.
9896 Implements the relay side of proposal 198; closes ticket 7200.
9899 - Avoid crashing when, as a relay without IPv6-exit support, a
9900 client insists on getting an IPv6 address or nothing. Fixes bug
9901 7814; bugfix on 0.2.4.7-alpha.
9904 - Improve circuit build timeout handling for hidden services.
9905 In particular: adjust build timeouts more accurately depending
9906 upon the number of hop-RTTs that a particular circuit type
9907 undergoes. Additionally, launch intro circuits in parallel
9908 if they timeout, and take the first one to reply as valid.
9909 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
9910 separate error codes; or at least, don't break for that reason.
9911 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
9912 - Update to the January 2 2013 Maxmind GeoLite Country database.
9914 o Minor features (testing):
9915 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
9916 (P-256) Diffie-Hellman handshakes to src/or/bench.
9917 - Add benchmark functions to test onion handshake performance.
9919 o Minor features (path bias detection):
9920 - Alter the Path Bias log messages to be more descriptive in terms
9921 of reporting timeouts and other statistics.
9922 - Create three levels of Path Bias log messages, as opposed to just
9923 two. These are configurable via consensus as well as via the torrc
9924 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
9925 The default values are 0.70, 0.50, and 0.30 respectively.
9926 - Separate the log message levels from the decision to drop guards,
9927 which also is available via torrc option PathBiasDropGuards.
9928 PathBiasDropGuards still defaults to 0 (off).
9929 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
9930 in combination with PathBiasExtremeRate.
9931 - Increase the default values for PathBiasScaleThreshold and
9932 PathBiasCircThreshold from (200, 20) to (300, 150).
9933 - Add in circuit usage accounting to path bias. If we try to use a
9934 built circuit but fail for any reason, it counts as path bias.
9935 Certain classes of circuits where the adversary gets to pick your
9936 destination node are exempt from this accounting. Usage accounting
9937 can be specifically disabled via consensus parameter or torrc.
9938 - Convert all internal path bias state to double-precision floating
9939 point, to avoid roundoff error and other issues.
9940 - Only record path bias information for circuits that have completed
9941 *two* hops. Assuming end-to-end tagging is the attack vector, this
9942 makes us more resilient to ambient circuit failure without any
9943 detection capability loss.
9945 o Minor bugfixes (log messages):
9946 - Rate-limit the "No circuits are opened. Relaxed timeout for a
9947 circuit with channel state open..." message to once per hour to
9948 keep it from filling the notice logs. Mitigates bug 7799 but does
9949 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
9950 - Avoid spurious warnings when configuring multiple client ports of
9951 which only some are nonlocal. Previously, we had claimed that some
9952 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
9955 o Code simplifications and refactoring:
9956 - Get rid of a couple of harmless clang warnings, where we compared
9957 enums to ints. These warnings are newly introduced in clang 3.2.
9958 - Split the onion.c file into separate modules for the onion queue
9959 and the different handshakes it supports.
9960 - Remove the marshalling/unmarshalling code for sending requests to
9961 cpuworkers over a socket, and instead just send structs. The
9962 recipient will always be the same Tor binary as the sender, so
9963 any encoding is overkill.
9966 Changes in version 0.2.4.7-alpha - 2012-12-24
9967 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
9968 directory mirrors for more robust bootstrapping; fixes more issues where
9969 clients with changing network conditions refuse to make any circuits;
9970 adds initial support for exiting to IPv6 addresses; resumes being able
9971 to update our GeoIP database, and includes the geoip6 file this time;
9972 turns off the client-side DNS cache by default due to privacy risks;
9973 and fixes a variety of other issues.
9975 o Major features (client resilience):
9976 - Add a new "FallbackDir" torrc option to use when we can't use
9977 a directory mirror from the consensus (either because we lack a
9978 consensus, or because they're all down). Currently, all authorities
9979 are fallbacks by default, and there are no other default fallbacks,
9980 but that will change. This option will allow us to give clients a
9981 longer list of servers to try to get a consensus from when first
9982 connecting to the Tor network, and thereby reduce load on the
9983 directory authorities. Implements proposal 206, "Preconfigured
9984 directory sources for bootstrapping". We also removed the old
9985 "FallbackNetworkstatus" option, since we never got it working well
9986 enough to use it. Closes bug 572.
9987 - If we have no circuits open, use a relaxed timeout (the
9988 95-percentile cutoff) until a circuit succeeds. This heuristic
9989 should allow Tor to succeed at building circuits even when the
9990 network connection drastically changes. Should help with bug 3443.
9992 o Major features (IPv6):
9993 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
9994 connectivity, then set the IPv6Exit flag to 1. Also make sure your
9995 exit policy reads as you would like: the address * applies to all
9996 address families, whereas *4 is IPv4 address only, and *6 is IPv6
9997 addresses only. On the client side, you'll need to wait until the
9998 authorities have upgraded, wait for enough exits to support IPv6,
9999 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
10000 ticket 5547, implements proposal 117 as revised in proposal 208.
10002 We DO NOT recommend that clients with actual anonymity needs start
10003 using IPv6 over Tor yet, since not enough exits support it yet.
10005 o Major features (geoip database):
10006 - Maxmind began labelling Tor relays as being in country "A1",
10007 which breaks by-country node selection inside Tor. Now we use a
10008 script to replace "A1" ("Anonymous Proxy") entries in our geoip
10009 file with real country codes. This script fixes about 90% of "A1"
10010 entries automatically and uses manual country code assignments to
10011 fix the remaining 10%. See src/config/README.geoip for details.
10012 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
10013 Country database, as modified above.
10015 o Major bugfixes (client-side DNS):
10016 - Turn off the client-side DNS cache by default. Updating and using
10017 the DNS cache is now configurable on a per-client-port
10018 level. SOCKSPort, DNSPort, etc lines may now contain
10019 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
10020 cache these types of DNS answers when we receive them from an
10021 exit node in response to an application request on this port, and
10022 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
10023 cached DNS answers of these types, we shouldn't use them. It's
10024 potentially risky to use cached DNS answers at the client, since
10025 doing so can indicate to one exit what answers we've gotten
10026 for DNS lookups in the past. With IPv6, this becomes especially
10027 problematic. Using cached DNS answers for requests on the same
10028 circuit would present less linkability risk, since all traffic
10029 on a circuit is already linkable, but it would also provide
10030 little performance benefit: the exit node caches DNS replies
10031 too. Implements a simplified version of Proposal 205. Implements
10034 o Major bugfixes (other):
10035 - Alter circuit build timeout measurement to start at the point
10036 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
10037 initialization). This should make our timeout measurements more
10038 uniform. Previously, we were sometimes including ORconn setup time
10039 in our circuit build time measurements. Should resolve bug 3443.
10040 - Fix an assertion that could trigger in hibernate_go_dormant() when
10041 closing an or_connection_t: call channel_mark_for_close() rather
10042 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
10044 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
10045 7655; bugfix on 0.2.4.6-alpha.
10048 - Add a new torrc option "ServerTransportListenAddr" to let bridge
10049 operators select the address where their pluggable transports will
10050 listen for connections. Resolves ticket 7013.
10051 - Allow an optional $ before the node identity digest in the
10052 controller command GETINFO ns/id/<identity>, for consistency with
10053 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
10054 - Log packaged cell fullness as part of the heartbeat message.
10055 Diagnosis to try to determine the extent of bug 7743.
10057 o Minor features (IPv6):
10058 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
10059 prefer to hand out virtual IPv6 addresses, since there are more of
10060 them and we can't run out. To override this behavior and make IPv4
10061 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
10062 or DNSPort you're using for resolving. Implements ticket 7571.
10063 - AutomapHostsOnResolve responses are now randomized, to avoid
10064 annoying situations where Tor is restarted and applications
10065 connect to the wrong addresses.
10066 - Never try more than 1000 times to pick a new virtual address when
10067 AutomapHostsOnResolve is set. That's good enough so long as we
10068 aren't close to handing out our entire virtual address space;
10069 if you're getting there, it's best to switch to IPv6 virtual
10073 - The ADDRMAP command can no longer generate an ill-formed error
10074 code on a failed MAPADDRESS. It now says "internal" rather than
10075 an English sentence fragment with spaces in the middle. Bugfix on
10076 Tor 0.2.0.19-alpha.
10077 - Fix log messages and comments to avoid saying "GMT" when we mean
10078 "UTC". Fixes bug 6113.
10079 - Compile on win64 using mingw64. Fixes bug 7260; patches from
10081 - Fix a crash when debugging unit tests on Windows: deallocate a
10082 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
10083 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
10086 - The DirServer option is now DirAuthority, for consistency with
10087 current naming patterns. You can still use the old DirServer form.
10089 o Code simplification and refactoring:
10090 - Move the client-side address-map/virtual-address/DNS-cache code
10091 out of connection_edge.c into a new addressmap.c module.
10092 - Remove unused code for parsing v1 directories and "running routers"
10093 documents. Fixes bug 6887.
10096 Changes in version 0.2.3.25 - 2012-11-19
10097 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
10098 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
10099 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
10100 programmer, and friend. Unstinting in his dedication to the cause of
10101 freedom, he inspired and helped many of us as we began our work on
10102 anonymity, and inspires us still. Please honor his memory by writing
10103 software to protect people's freedoms, and by helping others to do so.
10105 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
10106 significantly reduced directory overhead (via microdescriptors),
10107 enormous crypto performance improvements for fast relays on new
10108 enough hardware, a new v3 TLS handshake protocol that can better
10109 resist fingerprinting, support for protocol obfuscation plugins (aka
10110 pluggable transports), better scalability for hidden services, IPv6
10111 support for bridges, performance improvements like allowing clients
10112 to skip the first round-trip on the circuit ("optimistic data") and
10113 refilling token buckets more often, a new "stream isolation" design
10114 to isolate different applications on different circuits, and many
10115 stability, security, and privacy fixes.
10118 - Tor tries to wipe potentially sensitive data after using it, so
10119 that if some subsequent security failure exposes Tor's memory,
10120 the damage will be limited. But we had a bug where the compiler
10121 was eliminating these wipe operations when it decided that the
10122 memory was no longer visible to a (correctly running) program,
10123 hence defeating our attempt at defense in depth. We fix that
10124 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
10125 is unlikely to optimize away. Future versions of Tor may use
10126 a less ridiculously heavy approach for this. Fixes bug 7352.
10127 Reported in an article by Andrey Karpov.
10130 - Fix a harmless bug when opting against publishing a relay descriptor
10131 because DisableNetwork is set. Fixes bug 7464; bugfix on
10135 Changes in version 0.2.4.6-alpha - 2012-11-13
10136 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
10137 makes our defense-in-depth memory wiping more reliable, and begins to
10138 count IPv6 addresses in bridge statistics,
10141 - Fix an assertion failure that could occur when closing a connection
10142 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
10144 - Tor tries to wipe potentially sensitive data after using it, so
10145 that if some subsequent security failure exposes Tor's memory,
10146 the damage will be limited. But we had a bug where the compiler
10147 was eliminating these wipe operations when it decided that the
10148 memory was no longer visible to a (correctly running) program,
10149 hence defeating our attempt at defense in depth. We fix that
10150 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
10151 is unlikely to optimize away. Future versions of Tor may use
10152 a less ridiculously heavy approach for this. Fixes bug 7352.
10153 Reported in an article by Andrey Karpov.
10156 - Add GeoIP database for IPv6 addresses. The new config option
10158 - Bridge statistics now count bridge clients connecting over IPv6:
10159 bridge statistics files now list "bridge-ip-versions" and
10160 extra-info documents list "geoip6-db-digest". The control protocol
10161 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
10162 implementation by "shkoo", addressing ticket 5055.
10165 - Warn when we are binding low ports when hibernation is enabled;
10166 previously we had warned when we were _advertising_ low ports with
10167 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
10168 - Fix a harmless bug when opting against publishing a relay descriptor
10169 because DisableNetwork is set. Fixes bug 7464; bugfix on
10171 - Add warning message when a managed proxy dies during configuration.
10172 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
10173 - Fix a linking error when building tor-fw-helper without miniupnp.
10174 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
10175 - Check for closing an or_connection_t without going through correct
10176 channel functions; emit a warning and then call
10177 connection_or_close_for_error() so we don't assert as in bugs 7212
10179 - Compile correctly on compilers without C99 designated initializer
10180 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
10181 - Avoid a possible assert that can occur when channel_send_destroy() is
10182 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
10183 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
10184 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
10185 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
10186 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
10188 o Code simplification and refactoring:
10189 - Start using OpenBSD's implementation of queue.h, so that we don't
10190 need to hand-roll our own pointer and list structures whenever we
10191 need them. (We can't rely on a sys/queue.h, since some operating
10192 systems don't have them, and the ones that do have them don't all
10193 present the same extensions.)
10196 Changes in version 0.2.4.5-alpha - 2012-10-25
10197 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
10198 two important security vulnerabilities that could lead to remotely
10199 triggerable relay crashes, fix a major bug that was preventing clients
10200 from choosing suitable exit nodes, and refactor some of our code.
10202 o Major bugfixes (security, also in 0.2.3.24-rc):
10203 - Fix a group of remotely triggerable assertion failures related to
10204 incorrect link protocol negotiation. Found, diagnosed, and fixed
10205 by "some guy from France". Fix for CVE-2012-2250; bugfix on
10207 - Fix a denial of service attack by which any directory authority
10208 could crash all the others, or by which a single v2 directory
10209 authority could crash everybody downloading v2 directory
10210 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
10212 o Major bugfixes (also in 0.2.3.24-rc):
10213 - When parsing exit policy summaries from microdescriptors, we had
10214 previously been ignoring the last character in each one, so that
10215 "accept 80,443,8080" would be treated by clients as indicating
10216 a node that allows access to ports 80, 443, and 808. That would
10217 lead to clients attempting connections that could never work,
10218 and ignoring exit nodes that would support their connections. Now
10219 clients parse these exit policy summaries correctly. Fixes bug 7192;
10220 bugfix on 0.2.3.1-alpha.
10222 o Minor bugfixes (also in 0.2.3.24-rc):
10223 - Clients now consider the ClientRejectInternalAddresses config option
10224 when using a microdescriptor consensus stanza to decide whether
10225 an exit relay would allow exiting to an internal address. Fixes
10226 bug 7190; bugfix on 0.2.3.1-alpha.
10229 - Only disable TLS session ticket support when running as a TLS
10230 server. Now clients will blend better with regular Firefox
10231 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
10233 o Code simplification and refactoring:
10234 - Start using OpenBSD's implementation of queue.h (originally by
10236 - Move the entry node code from circuitbuild.c to its own file.
10237 - Move the circuit build timeout tracking code from circuitbuild.c
10241 Changes in version 0.2.3.24-rc - 2012-10-25
10242 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
10243 could lead to remotely triggerable relay crashes, and fixes
10244 a major bug that was preventing clients from choosing suitable exit
10247 o Major bugfixes (security):
10248 - Fix a group of remotely triggerable assertion failures related to
10249 incorrect link protocol negotiation. Found, diagnosed, and fixed
10250 by "some guy from France". Fix for CVE-2012-2250; bugfix on
10252 - Fix a denial of service attack by which any directory authority
10253 could crash all the others, or by which a single v2 directory
10254 authority could crash everybody downloading v2 directory
10255 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
10258 - When parsing exit policy summaries from microdescriptors, we had
10259 previously been ignoring the last character in each one, so that
10260 "accept 80,443,8080" would be treated by clients as indicating
10261 a node that allows access to ports 80, 443, and 808. That would
10262 lead to clients attempting connections that could never work,
10263 and ignoring exit nodes that would support their connections. Now
10264 clients parse these exit policy summaries correctly. Fixes bug 7192;
10265 bugfix on 0.2.3.1-alpha.
10268 - Clients now consider the ClientRejectInternalAddresses config option
10269 when using a microdescriptor consensus stanza to decide whether
10270 an exit relay would allow exiting to an internal address. Fixes
10271 bug 7190; bugfix on 0.2.3.1-alpha.
10274 Changes in version 0.2.4.4-alpha - 2012-10-20
10275 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
10276 vulnerability introduced by a change in OpenSSL, fixes a remotely
10277 triggerable assert, and adds new channel_t and circuitmux_t abstractions
10278 that will make it easier to test new connection transport and cell
10279 scheduling algorithms.
10281 o New directory authorities (also in 0.2.3.23-rc):
10282 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
10283 authority. Closes ticket 5749.
10285 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
10286 - Disable TLS session tickets. OpenSSL's implementation was giving
10287 our TLS session keys the lifetime of our TLS context objects, when
10288 perfect forward secrecy would want us to discard anything that
10289 could decrypt a link connection as soon as the link connection
10290 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
10291 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
10292 - Discard extraneous renegotiation attempts once the V3 link
10293 protocol has been initiated. Failure to do so left us open to
10294 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
10295 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
10297 o Internal abstraction features:
10298 - Introduce new channel_t abstraction between circuits and
10299 or_connection_t to allow for implementing alternate OR-to-OR
10300 transports. A channel_t is an abstract object which can either be a
10301 cell-bearing channel, which is responsible for authenticating and
10302 handshaking with the remote OR and transmitting cells to and from
10303 it, or a listening channel, which spawns new cell-bearing channels
10304 at the request of remote ORs. Implements part of ticket 6465.
10305 - Also new is the channel_tls_t subclass of channel_t, adapting it
10306 to the existing or_connection_t code. The V2/V3 protocol handshaking
10307 code which formerly resided in command.c has been moved below the
10308 channel_t abstraction layer and may be found in channeltls.c now.
10309 Implements the rest of ticket 6465.
10310 - Introduce new circuitmux_t storing the queue of circuits for
10311 a channel; this encapsulates and abstracts the queue logic and
10312 circuit selection policy, and allows the latter to be overridden
10313 easily by switching out a policy object. The existing EWMA behavior
10314 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
10316 o Required libraries:
10317 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
10318 strongly recommended.
10321 - Warn users who run hidden services on a Tor client with
10322 UseEntryGuards disabled that their hidden services will be
10323 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
10324 attack which motivated Tor to support entry guards in the first
10325 place). Resolves ticket 6889.
10326 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
10327 dhill. Resolves ticket 6982.
10328 - Option OutboundBindAddress can be specified multiple times and
10329 accepts IPv6 addresses. Resolves ticket 6876.
10331 o Minor bugfixes (also in 0.2.3.23-rc):
10332 - Don't serve or accept v2 hidden service descriptors over a
10333 relay's DirPort. It's never correct to do so, and disabling it
10334 might make it more annoying to exploit any bugs that turn up in the
10335 descriptor-parsing code. Fixes bug 7149.
10336 - Fix two cases in src/or/transports.c where we were calling
10337 fmt_addr() twice in a parameter list. Bug found by David
10338 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
10339 - Fix memory leaks whenever we logged any message about the "path
10340 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
10341 - When relays refuse a "create" cell because their queue of pending
10342 create cells is too big (typically because their cpu can't keep up
10343 with the arrival rate), send back reason "resource limit" rather
10344 than reason "internal", so network measurement scripts can get a
10345 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
10348 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
10349 - Free some more still-in-use memory at exit, to make hunting for
10350 memory leaks easier. Resolves bug 7029.
10351 - When a Tor client gets a "truncated" relay cell, the first byte of
10352 its payload specifies why the circuit was truncated. We were
10353 ignoring this 'reason' byte when tearing down the circuit, resulting
10354 in the controller not being told why the circuit closed. Now we
10355 pass the reason from the truncated cell to the controller. Bugfix
10356 on 0.1.2.3-alpha; fixes bug 7039.
10357 - Downgrade "Failed to hand off onionskin" messages to "debug"
10358 severity, since they're typically redundant with the "Your computer
10359 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
10360 - Make clients running with IPv6 bridges connect over IPv6 again,
10361 even without setting new config options ClientUseIPv6 and
10362 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
10363 - Use square brackets around IPv6 addresses in numerous places
10364 that needed them, including log messages, HTTPS CONNECT proxy
10365 requests, TransportProxy statefile entries, and pluggable transport
10366 extra-info lines. Fixes bug 7011; patch by David Fifield.
10368 o Code refactoring and cleanup:
10369 - Source files taken from other packages now reside in src/ext;
10370 previously they were scattered around the rest of Tor.
10371 - Avoid use of reserved identifiers in our C code. The C standard
10372 doesn't like us declaring anything that starts with an
10373 underscore, so let's knock it off before we get in trouble. Fix
10374 for bug 1031; bugfix on the first Tor commit.
10377 Changes in version 0.2.3.23-rc - 2012-10-20
10378 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
10379 vulnerability introduced by a change in OpenSSL, and fixes a variety
10380 of smaller bugs in preparation for the release.
10382 o New directory authorities:
10383 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
10384 authority. Closes ticket 5749.
10386 o Major bugfixes (security/privacy):
10387 - Disable TLS session tickets. OpenSSL's implementation was giving
10388 our TLS session keys the lifetime of our TLS context objects, when
10389 perfect forward secrecy would want us to discard anything that
10390 could decrypt a link connection as soon as the link connection
10391 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
10392 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
10393 - Discard extraneous renegotiation attempts once the V3 link
10394 protocol has been initiated. Failure to do so left us open to
10395 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
10396 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
10399 - Fix a possible crash bug when checking for deactivated circuits
10400 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
10401 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
10403 o Minor bugfixes (on 0.2.3.x):
10404 - Fix two cases in src/or/transports.c where we were calling
10405 fmt_addr() twice in a parameter list. Bug found by David
10406 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
10407 - Convert an assert in the pathbias code to a log message. The assert
10408 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
10409 bugfix on 0.2.3.17-beta.
10410 - Fix memory leaks whenever we logged any message about the "path
10411 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
10413 o Minor bugfixes (on 0.2.2.x and earlier):
10414 - Don't serve or accept v2 hidden service descriptors over a relay's
10415 DirPort. It's never correct to do so, and disabling it might
10416 make it more annoying to exploit any bugs that turn up in the
10417 descriptor-parsing code. Fixes bug 7149.
10418 - When relays refuse a "create" cell because their queue of pending
10419 create cells is too big (typically because their cpu can't keep up
10420 with the arrival rate), send back reason "resource limit" rather
10421 than reason "internal", so network measurement scripts can get a
10422 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
10423 - Correct file sizes when reading binary files on Cygwin, to avoid
10424 a bug where Tor would fail to read its state file. Fixes bug 6844;
10425 bugfix on 0.1.2.7-alpha.
10426 - Avoid undefined behavior when parsing the list of supported
10427 rendezvous/introduction protocols in a hidden service descriptor.
10428 Previously, Tor would have confused (as-yet-unused) protocol version
10429 numbers greater than 32 with lower ones on many platforms. Fixes
10430 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
10432 o Documentation fixes:
10433 - Clarify that hidden services are TCP only. Fixes bug 6024.
10436 Changes in version 0.2.4.3-alpha - 2012-09-22
10437 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
10438 assertion, resumes letting relays test reachability of their DirPort,
10439 and cleans up a bunch of smaller bugs.
10442 - Fix an assertion failure in tor_timegm() that could be triggered
10443 by a badly formatted directory object. Bug found by fuzzing with
10444 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
10447 - Fix a possible crash bug when checking for deactivated circuits
10448 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
10449 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
10450 - Allow routers to detect that their own DirPorts are running. When
10451 we removed support for versions_supports_begindir, we also
10452 accidentally removed the mechanism we used to self-test our
10453 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
10454 bugfix on 0.2.4.2-alpha.
10456 o Security features:
10457 - Switch to a completely time-invariant approach for picking nodes
10458 weighted by bandwidth. Our old approach would run through the
10459 part of the loop after it had made its choice slightly slower
10460 than it ran through the part of the loop before it had made its
10461 choice. Addresses ticket 6538.
10462 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
10463 by tor2web clients allows hidden services to identify tor2web
10464 clients through their repeated selection of the same rendezvous
10465 and introduction point circuit endpoints (their guards). Resolves
10469 - Enable Tor to read configuration, state, and key information from
10470 a FIFO. Previously Tor would only read from files with a positive
10471 stat.st_size. Code from meejah; fixes bug 6044.
10474 - Correct file sizes when reading binary files on Cygwin, to avoid
10475 a bug where Tor would fail to read its state file. Fixes bug 6844;
10476 bugfix on 0.1.2.7-alpha.
10477 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
10478 bugfix on 0.2.0.3-alpha.
10479 - When complaining about a client port on a public address, log
10480 which address we're complaining about. Fixes bug 4020; bugfix on
10481 0.2.3.3-alpha. Patch by Tom Fitzhenry.
10482 - Convert an assert in the pathbias code to a log message. The assert
10483 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
10484 bugfix on 0.2.3.17-beta.
10485 - Our new buildsystem was overzealous about rebuilding manpages: it
10486 would rebuild them all whenever any one of them changed. Now our
10487 dependency checking should be correct. Fixes bug 6843; bugfix on
10489 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
10490 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
10491 - Correct log printout about which address family is preferred
10492 when connecting to a bridge with both an IPv4 and IPv6 OR port.
10493 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
10495 o Minor bugfixes (code cleanliness):
10496 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
10497 with large values. This situation was untriggered, but nevertheless
10498 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
10499 - Reject consensus votes with more than 64 known-flags. We aren't even
10500 close to that limit yet, and our code doesn't handle it correctly.
10501 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
10502 - Avoid undefined behavior when parsing the list of supported
10503 rendezvous/introduction protocols in a hidden service descriptor.
10504 Previously, Tor would have confused (as-yet-unused) protocol version
10505 numbers greater than 32 with lower ones on many platforms. Fixes
10506 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
10507 - Fix handling of rendezvous client authorization types over 8.
10508 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
10509 - Fix building with older versions of GCC (2.95, for one) that don't
10510 like preprocessor directives inside macro arguments. Found by
10511 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
10512 - Switch weighted node selection rule from using a list of doubles
10513 to using a list of int64_t. This change should make the process
10514 slightly easier to debug and maintain. Needed to finish ticket 6538.
10516 o Code simplification and refactoring:
10517 - Move the generic "config" code into a new file, and have "config.c"
10518 hold only torrc- and state-related code. Resolves ticket 6823.
10519 - Move the core of our "choose a weighted element at random" logic
10520 into its own function, and give it unit tests. Now the logic is
10521 testable, and a little less fragile too.
10522 - Removed the testing_since field of node_t, which hasn't been used
10523 for anything since 0.2.0.9-alpha.
10525 o Documentation fixes:
10526 - Clarify that hidden services are TCP only. Fixes bug 6024.
10527 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
10531 Changes in version 0.2.3.22-rc - 2012-09-11
10532 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
10536 - Fix an assertion failure in tor_timegm() that could be triggered
10537 by a badly formatted directory object. Bug found by fuzzing with
10538 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
10541 - Avoid segfault when starting up having run with an extremely old
10542 version of Tor and parsing its state file. Fixes bug 6801; bugfix
10546 Changes in version 0.2.2.39 - 2012-09-11
10547 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
10551 - Fix an assertion failure in tor_timegm() that could be triggered
10552 by a badly formatted directory object. Bug found by fuzzing with
10553 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
10554 - Do not crash when comparing an address with port value 0 to an
10555 address policy. This bug could have been used to cause a remote
10556 assertion failure by or against directory authorities, or to
10557 allow some applications to crash clients. Fixes bug 6690; bugfix
10561 Changes in version 0.2.4.2-alpha - 2012-09-10
10562 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
10563 raises the default rate limiting even more, and makes the bootstrapping
10564 log messages less noisy.
10567 - Automatically forward the TCP ports of pluggable transport
10568 proxies using tor-fw-helper if PortForwarding is enabled. Implements
10572 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
10573 to 1GB/1GB. The previous defaults were intended to be "basically
10574 infinite", but it turns out they're now limiting our 100mbit+
10575 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
10576 last time we raised it).
10579 - Detect when we're running with a version of OpenSSL other than the
10580 one we compiled with. This has occasionally given people hard-to-
10582 - Log fewer lines at level "notice" about our OpenSSL and Libevent
10583 versions and capabilities when everything is going right. Resolves
10584 part of ticket 6736.
10585 - Directory authorities no long accept descriptors for any version of
10586 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
10587 These versions are insecure, unsupported, or both. Implements
10591 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
10592 to start with a triple-underscore so the controller won't touch it.
10593 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
10594 - Avoid segfault when starting up having run with an extremely old
10595 version of Tor and parsing its state file. Fixes bug 6801; bugfix
10597 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
10598 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
10599 - Don't follow the NULL pointer if microdescriptor generation fails.
10600 (This does not appear to be triggerable, but it's best to be safe.)
10601 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
10602 - Fix mis-declared dependencies on src/common/crypto.c and
10603 src/or/tor_main.c that could break out-of-tree builds under some
10604 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
10605 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
10606 6778; bugfix on 0.2.4.1-alpha.
10607 - Fix a harmless (in this case) build warning for implicitly
10608 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
10610 o Removed features:
10611 - Now that all versions before 0.2.2.x are disallowed, we no longer
10612 need to work around their missing features. Thus we can remove a
10613 bunch of compatibility code.
10615 o Code refactoring:
10616 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
10617 TCP ports to forward. In the past it only accepted two ports:
10618 the ORPort and the DirPort.
10621 Changes in version 0.2.4.1-alpha - 2012-09-05
10622 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
10623 bridgedb; lets relays use IPv6 addresses and directory authorities
10624 advertise them; and switches to a cleaner build interface.
10626 This is the first alpha release in a new series, so expect there to
10627 be bugs. Users who would rather test out a more stable branch should
10628 stay with 0.2.3.x for now.
10630 o Major features (bridges):
10631 - Bridges now report the pluggable transports they support to the
10632 bridge authority, so it can pass the supported transports on to
10633 bridgedb and/or eventually do reachability testing. Implements
10636 o Major features (IPv6):
10637 - Bridge authorities now accept IPv6 bridge addresses and include
10638 them in network status documents. Implements ticket 5534.
10639 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
10640 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
10641 to happen. Implements ticket 5535.
10642 - All kind of relays, not just bridges, can now advertise an IPv6
10643 OR port. Implements ticket 6362.
10644 - Directory authorities vote on IPv6 OR ports using the new consensus
10645 method 14. Implements ticket 6363.
10647 o Major features (build):
10648 - Switch to a nonrecursive Makefile structure. Now instead of each
10649 Makefile.am invoking other Makefile.am's, there is a master
10650 Makefile.am that includes the others. This change makes our build
10651 process slightly more maintainable, and improves parallelism for
10652 building with make -j. Original patch by Stewart Smith; various
10653 fixes by Jim Meyering.
10654 - Where available, we now use automake's "silent" make rules by
10655 default, so that warnings are easier to spot. You can get the old
10656 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
10658 o Minor features (code security and spec conformance):
10659 - Clear keys and key-derived material left on the stack in
10660 rendservice.c and rendclient.c. Check return value of
10661 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
10662 These fixes should make us more forward-secure against cold-boot
10663 attacks and the like. Fixes bug 2385.
10664 - Reject EXTEND cells sent to nonexistent streams. According to the
10665 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
10666 we were only checking for stream IDs that were currently in use.
10667 Found while hunting for more instances of bug 6271. Bugfix on
10668 0.0.2pre8, which introduced incremental circuit construction.
10670 o Minor features (streamlining);
10671 - No longer include the "opt" prefix when generating routerinfos
10672 or v2 directories: it has been needless since Tor 0.1.2. Closes
10674 - Remove some now-needless code that tried to aggressively flush
10675 OR connections as data was added to them. Since 0.2.0.1-alpha, our
10676 cell queue logic has saved us from the failure mode that this code
10677 was supposed to prevent. Removing this code will limit the number
10678 of baroque control flow paths through Tor's network logic. Reported
10679 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
10681 o Minor features (controller):
10682 - Add a "GETINFO signal/names" control port command. Implements
10684 - Provide default values for all options via "GETINFO config/defaults".
10685 Implements ticket 4971.
10687 o Minor features (IPv6):
10688 - New config option "AuthDirHasIPv6Connectivity 1" that directory
10689 authorities should set if they have IPv6 connectivity and want to
10690 do reachability tests for IPv6 relays. Implements feature 5974.
10691 - A relay with an IPv6 OR port now sends that address in NETINFO
10692 cells (in addition to its other address). Implements ticket 6364.
10694 o Minor features (log messages):
10695 - Omit the first heartbeat log message, because it never has anything
10696 useful to say, and it clutters up the bootstrapping messages.
10697 Resolves ticket 6758.
10698 - Don't log about reloading the microdescriptor cache at startup. Our
10699 bootstrap warnings are supposed to tell the user when there's a
10700 problem, and our bootstrap notices say when there isn't. Resolves
10701 ticket 6759; bugfix on 0.2.2.6-alpha.
10702 - Don't log "I learned some more directory information" when we're
10703 reading cached directory information. Reserve it for when new
10704 directory information arrives in response to a fetch. Resolves
10706 - Prevent rounding error in path bias counts when scaling
10707 them down, and use the correct scale factor default. Also demote
10708 some path bias related log messages down a level and make others
10709 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
10710 - We no longer warn so much when generating manpages from their
10713 o Code simplifications and refactoring:
10714 - Enhance our internal sscanf replacement so that we can eliminate
10715 the last remaining uses of the system sscanf. (Though those uses
10716 of sscanf were safe, sscanf itself is generally error prone, so
10717 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
10719 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
10720 - Move last_reachable and testing_since from routerinfo_t to node_t.
10721 Implements ticket 5529.
10722 - Add replaycache_t structure, functions and unit tests, then refactor
10723 rend_service_introduce() to be more clear to read, improve, debug,
10724 and test. Resolves bug 6177.
10725 - Finally remove support for malloc_good_size and malloc_usable_size.
10726 We had hoped that these functions would let us eke a little more
10727 memory out of our malloc implementation. Unfortunately, the only
10728 implementations that provided these functions are also ones that
10729 are already efficient about not overallocation: they never got us
10730 more than 7 or so bytes per allocation. Removing them saves us a
10731 little code complexity and a nontrivial amount of build complexity.
10733 o New requirements:
10734 - Tor maintainers now require Automake version 1.9 or later to build
10735 Tor from the Git repository. (Automake is not required when building
10736 from a source distribution.)
10739 Changes in version 0.2.3.21-rc - 2012-09-05
10740 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
10741 series. It fixes a trio of potential security bugs, fixes a bug where
10742 we were leaving some of the fast relays out of the microdescriptor
10743 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
10744 and cleans up other smaller issues.
10746 o Major bugfixes (security):
10747 - Tear down the circuit if we get an unexpected SENDME cell. Clients
10748 could use this trick to make their circuits receive cells faster
10749 than our flow control would have allowed, or to gum up the network,
10750 or possibly to do targeted memory denial-of-service attacks on
10751 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
10752 from July 2002, before the release of Tor 0.0.0. We had committed
10753 this patch previously, but we had to revert it because of bug 6271.
10754 Now that 6271 is fixed, this patch appears to work.
10755 - Reject any attempt to extend to an internal address. Without
10756 this fix, a router could be used to probe addresses on an internal
10757 network to see whether they were accepting connections. Fixes bug
10758 6710; bugfix on 0.0.8pre1.
10759 - Do not crash when comparing an address with port value 0 to an
10760 address policy. This bug could have been used to cause a remote
10761 assertion failure by or against directory authorities, or to
10762 allow some applications to crash clients. Fixes bug 6690; bugfix
10766 - Remove the upper bound on microdescriptor length. We were hitting
10767 the limit for routers with complex exit policies or family
10768 declarations, causing clients to not use them. Fixes the first
10769 piece of bug 6404; fix on 0.2.2.6-alpha.
10770 - Detect "ORPort 0" as meaning, uniformly, that we're not running
10771 as a relay. Previously, some of our code would treat the presence
10772 of any ORPort line as meaning that we should act like a relay,
10773 even though our new listener code would correctly not open any
10774 ORPorts for ORPort 0. Similar bugs in other Port options are also
10775 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
10778 - Avoid a pair of double-free and use-after-mark bugs that can
10779 occur with certain timings in canceled and re-received DNS
10780 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
10781 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
10782 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
10783 - Allow one-hop directory fetching circuits the full "circuit build
10784 timeout" period, rather than just half of it, before failing them
10785 and marking the relay down. This fix should help reduce cases where
10786 clients declare relays (or worse, bridges) unreachable because
10787 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
10788 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
10790 - Authorities no longer include any router in their microdescriptor
10791 consensuses for which they couldn't generate or agree on a
10792 microdescriptor. Fixes the second piece of bug 6404; fix on
10794 - Detect and reject attempts to specify both "FooPort" and
10795 "FooPort 0" in the same configuration domain. (It's still okay
10796 to have a FooPort in your configuration file, and use "FooPort 0"
10797 on the command line to disable it.) Fixes the second half of bug
10798 6507; bugfix on 0.2.3.3-alpha.
10799 - Make wildcarded addresses (that is, ones beginning with "*.") work
10800 when provided via the controller's MapAddress command. Previously,
10801 they were accepted, but we never actually noticed that they were
10802 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
10803 - Avoid crashing on a malformed state file where EntryGuardPathBias
10804 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
10805 - Add a (probably redundant) memory clear between iterations of
10806 the router status voting loop, to prevent future coding errors
10807 where data might leak between iterations of the loop. Resolves
10810 o Minor bugfixes (log messages):
10811 - Downgrade "set buildtimeout to low value" messages to "info"
10812 severity; they were never an actual problem, there was never
10813 anything reasonable to do about them, and they tended to spam logs
10814 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
10815 - Downgrade path-bias warning messages to "info". We'll try to get
10816 them working better in 0.2.4. Add internal circuit construction
10817 state to protect against the noisy warn message "Unexpectedly high
10818 circuit_successes". Also add some additional rate-limited notice
10819 messages to help determine the root cause of the warn. Fixes bug
10820 6475. Bugfix against 0.2.3.17-beta.
10821 - Move log message when unable to find a microdesc in a routerstatus
10822 entry to parse time. Previously we'd spam this warning every time
10823 we tried to figure out which microdescriptors to download. Fixes
10824 the third piece of bug 6404; fix on 0.2.3.18-rc.
10827 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
10828 change when the authority is deciding whether to accept a newly
10829 uploaded descriptor. Implements ticket 6423.
10830 - Add missing documentation for consensus and microdesc files.
10831 Resolves ticket 6732.
10834 Changes in version 0.2.2.38 - 2012-08-12
10835 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
10836 attack that could in theory leak path information.
10839 - Avoid an uninitialized memory read when reading a vote or consensus
10840 document that has an unrecognized flavor name. This read could
10841 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
10842 - Try to leak less information about what relays a client is
10843 choosing to a side-channel attacker. Previously, a Tor client would
10844 stop iterating through the list of available relays as soon as it
10845 had chosen one, thus finishing a little earlier when it picked
10846 a router earlier in the list. If an attacker can recover this
10847 timing information (nontrivial but not proven to be impossible),
10848 they could learn some coarse-grained information about which relays
10849 a client was picking (middle nodes in particular are likelier to
10850 be affected than exits). The timing attack might be mitigated by
10851 other factors (see bug 6537 for some discussion), but it's best
10852 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
10855 Changes in version 0.2.3.20-rc - 2012-08-05
10856 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
10857 series. It fixes a pair of code security bugs and a potential anonymity
10858 issue, updates our RPM spec files, and cleans up other smaller issues.
10861 - Avoid read-from-freed-memory and double-free bugs that could occur
10862 when a DNS request fails while launching it. Fixes bug 6480;
10863 bugfix on 0.2.0.1-alpha.
10864 - Avoid an uninitialized memory read when reading a vote or consensus
10865 document that has an unrecognized flavor name. This read could
10866 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
10867 - Try to leak less information about what relays a client is
10868 choosing to a side-channel attacker. Previously, a Tor client would
10869 stop iterating through the list of available relays as soon as it
10870 had chosen one, thus finishing a little earlier when it picked
10871 a router earlier in the list. If an attacker can recover this
10872 timing information (nontrivial but not proven to be impossible),
10873 they could learn some coarse-grained information about which relays
10874 a client was picking (middle nodes in particular are likelier to
10875 be affected than exits). The timing attack might be mitigated by
10876 other factors (see bug 6537 for some discussion), but it's best
10877 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
10880 - Try to make the warning when giving an obsolete SOCKSListenAddress
10881 a little more useful.
10882 - Terminate active server managed proxies if Tor stops being a
10883 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
10884 - Provide a better error message about possible OSX Asciidoc failure
10885 reasons. Fixes bug 6436.
10886 - Warn when Tor is configured to use accounting in a way that can
10887 link a hidden service to some other hidden service or public
10888 address. Resolves ticket 6490.
10891 - Check return value of fputs() when writing authority certificate
10892 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
10893 - Ignore ServerTransportPlugin lines when Tor is not configured as
10894 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
10895 - When disabling guards for having too high a proportion of failed
10896 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
10900 - Update our default RPM spec files to work with mock and rpmbuild
10901 on RHEL/Fedora. They have an updated set of dependencies and
10902 conflicts, a fix for an ancient typo when creating the "_tor"
10903 user, and better instructions. Thanks to Ondrej Mikle for the
10904 patch series. Fixes bug 6043.
10907 - Make it possible to set the TestingTorNetwork configuration
10908 option using AlternateDirAuthority and AlternateBridgeAuthority
10909 as an alternative to setting DirServer. Addresses ticket 6377.
10912 - Clarify the documentation for the Alternate*Authority options.
10914 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
10916 o Code simplification and refactoring:
10917 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
10918 10 lines. Also, don't nest them. Doing so in the past has
10919 led to hard-to-debug code. The new style is to use the
10920 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
10923 Changes in version 0.2.3.19-rc - 2012-07-06
10924 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
10925 series. It fixes the compile on Windows, reverts to a GeoIP database
10926 that isn't as broken, and fixes a flow control bug that has been around
10927 since the beginning of Tor.
10930 - Fix a bug handling SENDME cells on nonexistent streams that could
10931 result in bizarre window values. Report and patch contributed
10932 pseudonymously. Fixes part of bug 6271. This bug was introduced
10933 before the first Tor release, in svn commit r152.
10934 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
10935 June 2012 database, Maxmind marked many Tor relays as country "A1",
10936 which will cause risky behavior for clients that set EntryNodes
10937 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
10938 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
10939 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
10942 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
10943 bugfix on 0.2.1.10-alpha.
10946 Changes in version 0.2.3.18-rc - 2012-06-28
10947 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
10948 series. It fixes a few smaller bugs, but generally appears stable.
10949 Please test it and let us know whether it is!
10952 - Allow wildcarded mapaddress targets to be specified on the
10953 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
10954 - Make our linker option detection code more robust against linkers
10955 such as on FreeBSD 8, where a bad combination of options completes
10956 successfully but makes an unrunnable binary. Fixes bug 6173;
10957 bugfix on 0.2.3.17-beta.
10959 o Minor bugfixes (on 0.2.2.x and earlier):
10960 - Avoid a false positive in the util/threads unit test by increasing
10961 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
10962 - Replace "Sending publish request" log messages with "Launching
10963 upload", so that they no longer confusingly imply that we're
10964 sending something to a directory we might not even be connected
10965 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
10966 - Make sure to set *socket_error in all error cases in
10967 connection_connect(), so it can't produce a warning about
10968 errno being zero from errno_to_orconn_end_reason(). Bugfix on
10969 0.2.1.1-alpha; resolves ticket 6028.
10970 - Downgrade "Got a certificate, but we already have it" log messages
10971 from warning to info, except when we're a dirauth. Fixes bug 5238;
10972 bugfix on 0.2.1.7-alpha.
10973 - When checking for requested signatures on the latest consensus
10974 before serving it to a client, make sure to check the right
10975 consensus flavor. Bugfix on 0.2.2.6-alpha.
10976 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
10977 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
10979 o Minor bugfixes (on 0.2.3.x):
10980 - Make format_helper_exit_status() avoid unnecessary space padding
10981 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
10983 - Downgrade a message about cleaning the microdescriptor cache to
10984 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
10985 - Log a BUG message at severity INFO if we have a networkstatus with
10986 a missing entry for some microdescriptor. Continues on a patch
10988 - Improve the log message when a managed proxy fails to launch. Fixes
10989 bug 5099; bugfix on 0.2.3.6-alpha.
10990 - Don't do DNS lookups when parsing corrupted managed proxy protocol
10991 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
10992 - When formatting wildcarded address mappings for the controller,
10993 be sure to include "*." as appropriate. Partially fixes bug 6244;
10994 bugfix on 0.2.3.9-alpha.
10995 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
10996 Bugfix on 0.2.3.13-alpha.
10997 - Stop logging messages about running with circuit timeout learning
10998 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
10999 - Disable a spurious warning about reading on a marked and flushing
11000 connection. We shouldn't be doing that, but apparently we
11001 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
11002 - Fix a bug that stopped AllowDotExit from working on addresses
11003 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
11006 o Code simplification, refactoring, unit tests:
11007 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
11008 Libevent's notion of cached time when possible.
11009 - Remove duplicate code for invoking getrlimit() from control.c.
11010 - Add a unit test for the environment_variable_names_equal function.
11013 - Document the --defaults-torrc option, and the new (in 0.2.3)
11014 semantics for overriding, extending, and clearing lists of
11015 options. Closes bug 4748.
11018 Changes in version 0.2.3.17-beta - 2012-06-15
11019 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
11020 gets our TLS handshake back on track for being able to blend in with
11021 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
11022 with Vidalia, and otherwise continues to get us closer to a release
11026 - Enable gcc and ld hardening by default. Resolves ticket 5210.
11027 - Update TLS cipher list to match Firefox 8 and later. Resolves
11029 - Implement the client side of proposal 198: remove support for
11030 clients falsely claiming to support standard ciphersuites that
11031 they can actually provide. As of modern OpenSSL versions, it's not
11032 necessary to fake any standard ciphersuite, and doing so prevents
11033 us from using better ciphersuites in the future, since servers
11034 can't know whether an advertised ciphersuite is really supported or
11035 not. Some hosts -- notably, ones with very old versions of OpenSSL
11036 or where OpenSSL has been built with ECC disabled -- will stand
11037 out because of this change; TBB users should not be affected.
11040 - Change the default value for DynamicDHGroups (introduced in
11041 0.2.3.9-alpha) to 0. This feature can make Tor relays less
11042 identifiable by their use of the mod_ssl DH group, but at
11043 the cost of some usability (#4721) and bridge tracing (#6087)
11044 regressions. Resolves ticket 5598.
11045 - Send a CRLF at the end of each STATUS_* control protocol event. This
11046 bug tickled a bug in Vidalia which would make it freeze. Fixes
11047 bug 6094; bugfix on 0.2.3.16-alpha.
11050 - Disable writing on marked-for-close connections when they are
11051 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
11052 bug 5263; bugfix on 0.0.2pre13, where we first added a special
11053 case for flushing marked connections.
11054 - Detect SSL handshake even when the initial attempt to write the
11055 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
11056 - Change the AllowDotExit rules so they should actually work.
11057 We now enforce AllowDotExit only immediately after receiving an
11058 address via SOCKS or DNSPort: other sources are free to provide
11059 .exit addresses after the resolution occurs. Fixes bug 3940;
11060 bugfix on 0.2.2.1-alpha.
11061 - Fix a (harmless) integer overflow in cell statistics reported by
11062 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
11063 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
11064 right places and never depends on the consensus parameters or
11065 computes adaptive timeouts when it is disabled. Fixes bug 5049;
11066 bugfix on 0.2.2.14-alpha.
11067 - When building Tor on Windows with -DUNICODE (not default), ensure
11068 that error messages, filenames, and DNS server names are always
11069 NUL-terminated when we convert them to a single-byte encoding.
11070 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
11071 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
11072 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
11073 - Fix an edge case where TestingTorNetwork is set but the authorities
11074 and relays all have an uptime of zero, where the private Tor network
11075 could briefly lack support for hidden services. Fixes bug 3886;
11076 bugfix on 0.2.2.18-alpha.
11077 - Correct the manpage's descriptions for the default values of
11078 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
11080 - Fix the documentation for the --hush and --quiet command line
11081 options, which changed their behavior back in 0.2.3.3-alpha.
11082 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
11086 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
11087 more information to it, so that we can track it down in case it
11088 returns again. Mitigates bug 5235.
11089 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
11090 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
11091 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
11092 - Warn the user when HTTPProxy, but no other proxy type, is
11093 configured. This can cause surprising behavior: it doesn't send
11094 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
11095 directory traffic only. Resolves ticket 4663.
11096 - Issue a notice if a guard completes less than 40% of your circuits.
11097 Threshold is configurable by torrc option PathBiasNoticeRate and
11098 consensus parameter pb_noticepct. There is additional, off-by-
11099 default code to disable guards which fail too many circuits.
11100 Addresses ticket 5458.
11101 - Update to the June 6 2012 Maxmind GeoLite Country database.
11103 o Code simplifications and refactoring:
11104 - Remove validate_pluggable_transports_config(): its warning
11105 message is now handled by connection_or_connect().
11108 Changes in version 0.2.2.37 - 2012-06-06
11109 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
11110 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
11114 - Work around a bug in OpenSSL that broke renegotiation with TLS
11115 1.1 and TLS 1.2. Without this workaround, all attempts to speak
11116 the v2 Tor connection protocol when both sides were using OpenSSL
11117 1.0.1 would fail. Resolves ticket 6033.
11118 - When waiting for a client to renegotiate, don't allow it to add
11119 any bytes to the input buffer. This fixes a potential DoS issue.
11120 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
11121 - Fix an edge case where if we fetch or publish a hidden service
11122 descriptor, we might build a 4-hop circuit and then use that circuit
11123 for exiting afterwards -- even if the new last hop doesn't obey our
11124 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
11127 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
11128 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
11131 - Tell GCC and Clang to check for any errors in format strings passed
11132 to the tor_v*(print|scan)f functions.
11135 Changes in version 0.2.3.16-alpha - 2012-06-05
11136 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
11137 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
11138 currently). It also fixes a variety of smaller bugs and other cleanups
11139 that get us closer to a release candidate.
11141 o Major bugfixes (general):
11142 - Work around a bug in OpenSSL that broke renegotiation with TLS
11143 1.1 and TLS 1.2. Without this workaround, all attempts to speak
11144 the v2 Tor connection protocol when both sides were using OpenSSL
11145 1.0.1 would fail. Resolves ticket 6033.
11146 - When waiting for a client to renegotiate, don't allow it to add
11147 any bytes to the input buffer. This fixes a potential DoS issue.
11148 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
11149 - Pass correct OR address to managed proxies (like obfsproxy),
11150 even when ORListenAddress is used. Fixes bug 4865; bugfix on
11152 - The advertised platform of a router now includes only its operating
11153 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
11154 service pack level (for Windows) or its CPU architecture (for Unix).
11155 We also no longer include the "git-XYZ" tag in the version. Resolves
11158 o Major bugfixes (clients):
11159 - If we are unable to find any exit that supports our predicted ports,
11160 stop calling them predicted, so that we don't loop and build
11161 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
11162 which introduced predicted ports.
11163 - Fix an edge case where if we fetch or publish a hidden service
11164 descriptor, we might build a 4-hop circuit and then use that circuit
11165 for exiting afterwards -- even if the new last hop doesn't obey our
11166 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
11167 - Check at each new consensus whether our entry guards were picked
11168 long enough ago that we should rotate them. Previously, we only
11169 did this check at startup, which could lead to us holding a guard
11170 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
11171 - When fetching a bridge descriptor from a bridge authority,
11172 always do so anonymously, whether we have been able to open
11173 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
11174 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
11175 but we'll need to wait for bug 6010 before it's actually usable.
11177 o Major bugfixes (directory authorities):
11178 - When computing weight parameters, behave more robustly in the
11179 presence of a bad bwweightscale value. Previously, the authorities
11180 would crash if they agreed on a sufficiently broken weight_scale
11181 value: now, they use a reasonable default and carry on. Partial
11182 fix for 5786; bugfix on 0.2.2.17-alpha.
11183 - Check more thoroughly to prevent a rogue authority from
11184 double-voting on any consensus directory parameter. Previously,
11185 authorities would crash in this case if the total number of
11186 votes for any parameter exceeded the number of active voters,
11187 but would let it pass otherwise. Partial fix for bug 5786; bugfix
11191 - Rate-limit log messages when asked to connect anonymously to
11192 a private address. When these hit, they tended to hit fast and
11193 often. Also, don't bother trying to connect to addresses that we
11194 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
11195 reply makes us think we have been lied to, even when the address the
11196 client tried to connect to was "localhost." Resolves ticket 2822.
11197 - Allow packagers to insert an extra string in server descriptor
11198 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
11199 Resolves the rest of ticket 2988.
11200 - Raise the threshold of server descriptors needed (75%) and exit
11201 server descriptors needed (50%) before we will declare ourselves
11202 bootstrapped. This will make clients start building circuits a
11203 little later, but makes the initially constructed circuits less
11204 skewed and less in conflict with further directory fetches. Fixes
11206 - Close any connection that sends unrecognized junk before the
11207 handshake. Solves an issue noted in bug 4369.
11208 - Improve log messages about managed transports. Resolves ticket 5070.
11209 - Tag a bridge's descriptor as "never to be sent unencrypted".
11210 This shouldn't matter, since bridges don't open non-anonymous
11211 connections to the bridge authority and don't allow unencrypted
11212 directory connections from clients, but we might as well make
11213 sure. Closes bug 5139.
11214 - Expose our view of whether we have gone dormant to the controller,
11215 via a new "GETINFO dormant" value. Torbutton and other controllers
11216 can use this to avoid doing periodic requests through Tor while
11217 it's dormant (bug 4718). Fixes bug 5954.
11218 - Tell GCC and Clang to check for any errors in format strings passed
11219 to the tor_v*(print|scan)f functions.
11220 - Update to the May 1 2012 Maxmind GeoLite Country database.
11222 o Minor bugfixes (already included in 0.2.2.36):
11223 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
11224 Fixes bug 5346; bugfix on 0.0.8pre3.
11225 - Correct parsing of certain date types in parse_http_time().
11226 Without this patch, If-Modified-Since would behave
11227 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
11228 Esteban Manchado Velázques.
11229 - Make our number-parsing functions always treat too-large values
11230 as an error, even when those values exceed the width of the
11231 underlying type. Previously, if the caller provided these
11232 functions with minima or maxima set to the extreme values of the
11233 underlying integer type, these functions would return those
11234 values on overflow rather than treating overflow as an error.
11235 Fixes part of bug 5786; bugfix on 0.0.9.
11236 - If we hit the error case where routerlist_insert() replaces an
11237 existing (old) server descriptor, make sure to remove that
11238 server descriptor from the old_routers list. Fix related to bug
11239 1776. Bugfix on 0.2.2.18-alpha.
11240 - Clarify the behavior of MaxCircuitDirtiness with hidden service
11241 circuits. Fixes issue 5259.
11243 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
11244 - Prevent a null-pointer dereference when receiving a data cell
11245 for a nonexistent stream when the circuit in question has an
11246 empty deliver window. We don't believe this is triggerable,
11247 since we don't currently allow deliver windows to become empty,
11248 but the logic is tricky enough that it's better to make the code
11249 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
11250 - Fix a memory leak when trying to launch a DNS request when the
11251 network is disabled or the nameservers are unconfigurable. Fixes
11252 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
11253 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
11254 - Don't hold a Windows file handle open for every file mapping;
11255 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
11257 - Avoid O(n^2) performance characteristics when parsing a large
11258 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
11259 - Format more doubles with %f, not %lf. Patch from grarpamp to make
11260 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
11262 - Make our replacement implementation of strtok_r() compatible with
11263 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
11264 bugfix on 0.2.2.1-alpha.
11265 - Fix a NULL-pointer dereference on a badly formed
11266 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
11267 bugfix on 0.2.2.9-alpha.
11268 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
11269 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
11270 - Defensively refactor rend_mid_rendezvous() so that protocol
11271 violations and length checks happen in the beginning. Fixes
11273 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
11274 that IPv6 stuff will compile on MSVC, and compilation issues
11275 will be easier to track down. Fixes bug 5861.
11277 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
11278 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
11279 resource exhaustion, so that clients can adjust their load to
11280 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
11281 started using END_STREAM_REASON_RESOURCELIMIT.
11282 - Don't check for whether the address we're using for outbound
11283 connections has changed until after the outbound connection has
11284 completed. On Windows, getsockname() doesn't succeed until the
11285 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
11286 - If the configuration tries to set MyFamily on a bridge, refuse to
11287 do so, and warn about the security implications. Fixes bug 4657;
11288 bugfix on 0.2.0.3-alpha.
11289 - If the client fails to set a reasonable set of ciphersuites
11290 during its v2 handshake renegotiation, allow the renegotiation to
11291 continue nevertheless (i.e. send all the required certificates).
11292 Fixes bug 4591; bugfix on 0.2.0.20-rc.
11293 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
11294 option is set to 0 (which Vidalia version 0.2.16 now does when
11295 a SAVECONF attempt fails), perform other actions that SIGHUP
11296 usually causes (like reopening the logs). Fixes bug 5095; bugfix
11298 - If we fail to write a microdescriptor to the disk cache, do not
11299 continue replacing the old microdescriptor file. Fixes bug 2954;
11300 bugfix on 0.2.2.6-alpha.
11301 - Exit nodes don't need to fetch certificates for authorities that
11302 they don't recognize; only directory authorities, bridges,
11303 and caches need to do that. Fixes part of bug 2297; bugfix on
11305 - Correctly handle checking the permissions on the parent
11306 directory of a control socket in the root directory. Bug found
11307 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
11309 - When told to add a bridge with the same digest as a preexisting
11310 bridge but a different addr:port, change the addr:port as
11311 requested. Previously we would not notice the change. Fixes half
11312 of bug 5603; fix on 0.2.2.26-beta.
11313 - End AUTHCHALLENGE error messages (in the control protocol) with
11314 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
11316 o Minor bugfixes (on 0.2.3.x):
11317 - Turn an assertion (that the number of handshakes received as a
11318 server is not < 1) into a warning. Fixes bug 4873; bugfix on
11320 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
11321 we had reversed them when the answer was cached.) Fixes bug
11322 5723; bugfix on 0.2.3.1-alpha.
11323 - Work correctly on Linux systems with accept4 support advertised in
11324 their headers, but without accept4 support in the kernel. Fix
11325 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
11326 - When told to add a bridge with the same addr:port as a preexisting
11327 bridge but a different transport, change the transport as
11328 requested. Previously we would not notice the change. Fixes half
11329 of bug 5603; fix on 0.2.3.2-alpha.
11330 - Avoid a "double-reply" warning when replying to a SOCKS request
11331 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
11332 bugfix on 0.2.3.4-alpha.
11333 - Fix a bug where a bridge authority crashes if it has seen no
11334 directory requests when it's time to write statistics to disk.
11335 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
11337 - Don't try to open non-control listeners when DisableNetwork is set.
11338 Previously, we'd open all listeners, then immediately close them.
11339 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
11340 - Don't abort the managed proxy protocol if the managed proxy
11341 sends us an unrecognized line; ignore it instead. Fixes bug
11342 5910; bugfix on 0.2.3.9-alpha.
11343 - Fix a compile warning in crypto.c when compiling with clang 3.1.
11344 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
11345 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
11346 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
11347 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
11348 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
11349 - Resolve numerous small warnings and build issues with MSVC. Resolves
11352 o Documentation fixes:
11353 - Improve the manual's documentation for the NT Service command-line
11354 options. Addresses ticket 3964.
11355 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
11356 - Document the changes to the ORPort and DirPort options, and the
11357 fact that {OR/Dir}ListenAddress is now unnecessary (and
11358 therefore deprecated). Resolves ticket 5597.
11361 - Remove the torrc.bridge file: we don't use it for anything, and
11362 it had become badly desynchronized from torrc.sample. Resolves
11366 Changes in version 0.2.2.36 - 2012-05-24
11367 Tor 0.2.2.36 updates the addresses for two of the eight directory
11368 authorities, fixes some potential anonymity and security issues,
11369 and fixes several crash bugs.
11371 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
11372 known flaws, and nobody should be using them. You should upgrade. If
11373 you're using a Linux or BSD and its packages are obsolete, stop using
11374 those packages and upgrade anyway.
11376 o Directory authority changes:
11377 - Change IP address for maatuska (v3 directory authority).
11378 - Change IP address for ides (v3 directory authority), and rename
11382 - When building or running with any version of OpenSSL earlier
11383 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
11384 versions have a bug (CVE-2011-4576) in which their block cipher
11385 padding includes uninitialized data, potentially leaking sensitive
11386 information to any peer with whom they make a SSLv3 connection. Tor
11387 does not use SSL v3 by default, but a hostile client or server
11388 could force an SSLv3 connection in order to gain information that
11389 they shouldn't have been able to get. The best solution here is to
11390 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
11391 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
11392 to make sure that the bug can't happen.
11393 - Never use a bridge or a controller-supplied node as an exit, even
11394 if its exit policy allows it. Found by wanoskarnet. Fixes bug
11395 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
11396 and 0.2.0.3-alpha (for bridge-purpose descriptors).
11397 - Only build circuits if we have a sufficient threshold of the total
11398 descriptors that are marked in the consensus with the "Exit"
11399 flag. This mitigates an attack proposed by wanoskarnet, in which
11400 all of a client's bridges collude to restrict the exit nodes that
11401 the client knows about. Fixes bug 5343.
11402 - Provide controllers with a safer way to implement the cookie
11403 authentication mechanism. With the old method, if another locally
11404 running program could convince a controller that it was the Tor
11405 process, then that program could trick the controller into telling
11406 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
11407 authentication method uses a challenge-response approach to prevent
11408 this attack. Fixes bug 5185; implements proposal 193.
11411 - Avoid logging uninitialized data when unable to decode a hidden
11412 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
11413 - Avoid a client-side assertion failure when receiving an INTRODUCE2
11414 cell on a general purpose circuit. Fixes bug 5644; bugfix on
11416 - Fix builds when the path to sed, openssl, or sha1sum contains
11417 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
11419 - Correct our replacements for the timeradd() and timersub() functions
11420 on platforms that lack them (for example, Windows). The timersub()
11421 function is used when expiring circuits, while timeradd() is
11422 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
11423 bugfix on 0.2.2.24-alpha.
11424 - Fix the SOCKET_OK test that we use to tell when socket
11425 creation fails so that it works on Win64. Fixes part of bug 4533;
11426 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
11429 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
11430 Fixes bug 5346; bugfix on 0.0.8pre3.
11431 - Make our number-parsing functions always treat too-large values
11432 as an error, even when those values exceed the width of the
11433 underlying type. Previously, if the caller provided these
11434 functions with minima or maxima set to the extreme values of the
11435 underlying integer type, these functions would return those
11436 values on overflow rather than treating overflow as an error.
11437 Fixes part of bug 5786; bugfix on 0.0.9.
11438 - Older Linux kernels erroneously respond to strange nmap behavior
11439 by having accept() return successfully with a zero-length
11440 socket. When this happens, just close the connection. Previously,
11441 we would try harder to learn the remote address: but there was
11442 no such remote address to learn, and our method for trying to
11443 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
11444 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
11445 - Correct parsing of certain date types in parse_http_time().
11446 Without this patch, If-Modified-Since would behave
11447 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
11448 Esteban Manchado Velázques.
11449 - Change the BridgePassword feature (part of the "bridge community"
11450 design, which is not yet implemented) to use a time-independent
11451 comparison. The old behavior might have allowed an adversary
11452 to use timing to guess the BridgePassword value. Fixes bug 5543;
11453 bugfix on 0.2.0.14-alpha.
11454 - Detect and reject certain misformed escape sequences in
11455 configuration values. Previously, these values would cause us
11456 to crash if received in a torrc file or over an authenticated
11457 control port. Bug found by Esteban Manchado Velázquez, and
11458 independently by Robert Connolly from Matta Consulting who further
11459 noted that it allows a post-authentication heap overflow. Patch
11460 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
11461 bugfix on 0.2.0.16-alpha.
11462 - Fix a compile warning when using the --enable-openbsd-malloc
11463 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
11464 - During configure, detect when we're building with clang version
11465 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
11466 CFLAGS. clang doesn't support them yet.
11467 - When sending an HTTP/1.1 proxy request, include a Host header.
11468 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
11469 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
11470 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
11471 - If we hit the error case where routerlist_insert() replaces an
11472 existing (old) server descriptor, make sure to remove that
11473 server descriptor from the old_routers list. Fix related to bug
11474 1776. Bugfix on 0.2.2.18-alpha.
11476 o Minor bugfixes (documentation and log messages):
11477 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
11478 Fixes bug 4856; bugfix on Tor 0.0.6.
11479 - Update "ClientOnly" man page entry to explain that there isn't
11480 really any point to messing with it. Resolves ticket 5005.
11481 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
11482 directory authority option (introduced in Tor 0.2.2.34).
11483 - Downgrade the "We're missing a certificate" message from notice
11484 to info: people kept mistaking it for a real problem, whereas it
11485 is seldom the problem even when we are failing to bootstrap. Fixes
11486 bug 5067; bugfix on 0.2.0.10-alpha.
11487 - Correctly spell "connect" in a log message on failure to create a
11488 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
11489 - Clarify the behavior of MaxCircuitDirtiness with hidden service
11490 circuits. Fixes issue 5259.
11493 - Directory authorities now reject versions of Tor older than
11494 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
11495 inclusive. These versions accounted for only a small fraction of
11496 the Tor network, and have numerous known security issues. Resolves
11498 - Update to the May 1 2012 Maxmind GeoLite Country database.
11501 - When sending or relaying a RELAY_EARLY cell, we used to convert
11502 it to a RELAY cell if the connection was using the v1 link
11503 protocol. This was a workaround for older versions of Tor, which
11504 didn't handle RELAY_EARLY cells properly. Now that all supported
11505 versions can handle RELAY_EARLY cells, and now that we're enforcing
11506 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
11507 remove this workaround. Addresses bug 4786.
11510 Changes in version 0.2.3.15-alpha - 2012-04-30
11511 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
11512 the development branch build on Windows again.
11514 o Minor bugfixes (on 0.2.2.x and earlier):
11515 - Make sure that there are no unhandled pending TLS errors before
11516 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
11517 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
11518 Bugfix on 0.1.0.5-rc; fixes bug 4528.
11519 - Fix an assert that directory authorities could trigger on sighup
11520 during some configuration state transitions. We now don't treat
11521 it as a fatal error when the new descriptor we just generated in
11522 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
11523 - After we pick a directory mirror, we would refuse to use it if
11524 it's in our ExcludeExitNodes list, resulting in mysterious failures
11525 to bootstrap for people who just wanted to avoid exiting from
11526 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
11527 - When building with --enable-static-tor on OpenBSD, do not
11528 erroneously attempt to link -lrt. Fixes bug 5103.
11530 o Minor bugfixes (on 0.2.3.x):
11531 - When Tor is built with kernel headers from a recent (last few
11532 years) Linux kernel, do not fail to run on older (pre-2.6.28
11533 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
11534 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
11535 and 0.2.3.12-alpha.
11536 - Fix compilation with miniupnpc version 1.6; patch from
11537 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
11538 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
11539 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
11540 - Fix compilation on platforms without unistd.h, or where environ
11541 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
11544 - Directory authorities are now a little more lenient at accepting
11545 older router descriptors, or newer router descriptors that don't
11546 make big changes. This should help ameliorate past and future
11547 issues where routers think they have uploaded valid descriptors,
11548 but the authorities don't think so. Fix for ticket 2479.
11549 - Make the code that clients use to detect an address change be
11550 IPv6-aware, so that it won't fill clients' logs with error
11551 messages when trying to get the IPv4 address of an IPv6
11552 connection. Implements ticket 5537.
11554 o Removed features:
11555 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
11556 authorities needed to use it for a while to keep the network working
11557 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
11558 that was six months ago. As of now, it should no longer be needed
11562 Changes in version 0.2.3.14-alpha - 2012-04-23
11563 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
11564 candidate. It also dramatically speeds up AES: fast relays should
11565 consider switching to the newer OpenSSL library.
11567 o Directory authority changes:
11568 - Change IP address for ides (v3 directory authority), and rename
11572 - Avoid logging uninitialized data when unable to decode a hidden
11573 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
11574 - Avoid a client-side assertion failure when receiving an INTRODUCE2
11575 cell on a general purpose circuit. Fixes bug 5644; bugfix on
11577 - If authorities are unable to get a v2 consensus document from other
11578 directory authorities, they no longer fall back to fetching
11579 them from regular directory caches. Fixes bug 5635; bugfix on
11580 0.2.2.26-beta, where routers stopped downloading v2 consensus
11581 documents entirely.
11582 - When we start a Tor client with a normal consensus already cached,
11583 be willing to download a microdescriptor consensus. Fixes bug 4011;
11584 fix on 0.2.3.1-alpha.
11586 o Major features (performance):
11587 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
11588 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
11589 vectorized AES implementations as appropriate. These can be much,
11590 much faster than other AES implementations.
11592 o Minor bugfixes (0.2.2.x and earlier):
11593 - Don't launch more than 10 service-side introduction-point circuits
11594 for a hidden service in five minutes. Previously, we would consider
11595 launching more introduction-point circuits if at least one second
11596 had passed without any introduction-point circuits failing. Fixes
11597 bug 4607; bugfix on 0.0.7pre1.
11598 - Change the BridgePassword feature (part of the "bridge community"
11599 design, which is not yet implemented) to use a time-independent
11600 comparison. The old behavior might have allowed an adversary
11601 to use timing to guess the BridgePassword value. Fixes bug 5543;
11602 bugfix on 0.2.0.14-alpha.
11603 - Enforce correct return behavior of tor_vsscanf() when the '%%'
11604 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
11605 - When sending an HTTP/1.1 proxy request, include a Host header.
11606 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
11607 - Don't log that we have "decided to publish new relay descriptor"
11608 unless we are actually publishing a descriptor. Fixes bug 3942;
11609 bugfix on 0.2.2.28-beta.
11611 o Minor bugfixes (0.2.3.x):
11612 - Fix a bug where a bridge authority crashes (on a failed assert)
11613 if it has seen no directory requests when it's time to write
11614 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
11615 - Fix bug stomping on ORPort option NoListen and ignoring option
11616 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
11617 - In the testsuite, provide a large enough buffer in the tor_sscanf
11618 unit test. Otherwise we'd overrun that buffer and crash during
11619 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
11621 - Make sure we create the keys directory if it doesn't exist and we're
11622 about to store the dynamic Diffie-Hellman parameters. Fixes bug
11623 5572; bugfix on 0.2.3.13-alpha.
11624 - Fix a small memory leak when trying to decode incorrect base16
11625 authenticator during SAFECOOKIE authentication. Found by
11626 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
11629 - Add more information to a log statement that might help track down
11630 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
11631 non-IP address" messages (or any Bug messages, for that matter!),
11632 please let us know about it.
11633 - Relays now understand an IPv6 address when they get one from a
11634 directory server. Resolves ticket 4875.
11635 - Resolve IPv6 addresses in bridge and entry statistics to country
11636 code "??" which means we at least count them. Resolves ticket 5053;
11637 improves on 0.2.3.9-alpha.
11638 - Update to the April 3 2012 Maxmind GeoLite Country database.
11639 - Begin a doc/state-contents.txt file to explain the contents of
11640 the Tor state file. Fixes bug 2987.
11642 o Default torrc changes:
11643 - Stop listing "socksport 9050" in torrc.sample. We open a socks
11644 port on 9050 by default anyway, so this should not change anything
11646 - Stop mentioning the deprecated *ListenAddress options in
11647 torrc.sample. Fixes bug 5438.
11648 - Document unit of bandwidth related options in sample torrc.
11651 o Removed features:
11652 - The "torify" script no longer supports the "tsocks" socksifier
11653 tool, since tsocks doesn't support DNS and UDP right for Tor.
11654 Everyone should be using torsocks instead. Fixes bugs 3530 and
11655 5180. Based on a patch by "ugh".
11657 o Code refactoring:
11658 - Change the symmetric cipher interface so that creating and
11659 initializing a stream cipher are no longer separate functions.
11660 - Remove all internal support for unpadded RSA. We never used it, and
11661 it would be a bad idea to start.
11664 Changes in version 0.2.3.13-alpha - 2012-03-26
11665 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
11666 in managed pluggable transports, as well as providing other cleanups
11667 that get us closer to a release candidate.
11669 o Directory authority changes:
11670 - Change IP address for maatuska (v3 directory authority).
11673 - Provide controllers with a safer way to implement the cookie
11674 authentication mechanism. With the old method, if another locally
11675 running program could convince a controller that it was the Tor
11676 process, then that program could trick the controller into telling
11677 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
11678 authentication method uses a challenge-response approach to prevent
11679 this attack. Fixes bug 5185, implements proposal 193.
11680 - Never use a bridge or a controller-supplied node as an exit, even
11681 if its exit policy allows it. Found by wanoskarnet. Fixes bug
11682 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
11683 and 0.2.0.3-alpha (for bridge-purpose descriptors).
11684 - Only build circuits if we have a sufficient threshold of the total
11685 descriptors that are marked in the consensus with the "Exit"
11686 flag. This mitigates an attack proposed by wanoskarnet, in which
11687 all of a client's bridges collude to restrict the exit nodes that
11688 the client knows about. Fixes bug 5343.
11690 o Major bugfixes (on Tor 0.2.3.x):
11691 - Avoid an assert when managed proxies like obfsproxy are configured,
11692 and we receive HUP signals or setconf attempts too rapidly. This
11693 situation happens most commonly when Vidalia tries to attach to
11694 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
11695 bugfix on 0.2.3.6-alpha.
11696 - Fix a relay-side pluggable transports bug where managed proxies were
11697 unreachable from the Internet, because Tor asked them to bind on
11698 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
11699 - Stop discarding command-line arguments when TestingTorNetwork
11700 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
11701 0.2.3.9-alpha, where task 4552 added support for two layers of
11703 - Resume allowing the unit tests to run in gdb. This was accidentally
11704 made impossible when the DisableDebuggerAttachment option was
11705 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
11706 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
11707 0.2.3.11-alpha. Reported by Anthony G. Basile.
11709 o Minor bugfixes (on 0.2.2.x and earlier):
11710 - Ensure we don't cannibalize circuits that are longer than three hops
11711 already, so we don't end up making circuits with 5 or more
11712 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
11713 0.1.0.1-rc which introduced cannibalization.
11714 - Detect and reject certain misformed escape sequences in
11715 configuration values. Previously, these values would cause us
11716 to crash if received in a torrc file or over an authenticated
11717 control port. Bug found by Esteban Manchado Velázquez, and
11718 independently by Robert Connolly from Matta Consulting who further
11719 noted that it allows a post-authentication heap overflow. Patch
11720 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
11721 bugfix on 0.2.0.16-alpha.
11722 - Fix a compile warning when using the --enable-openbsd-malloc
11723 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
11724 - Directory caches no longer refuse to clean out descriptors because
11725 of missing v2 networkstatus documents, unless they're configured
11726 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
11727 0.2.2.26-beta. Patch by Daniel Bryg.
11728 - Update to the latest version of the tinytest unit testing framework.
11729 This includes a couple of bugfixes that can be relevant for
11730 running forked unit tests on Windows, and removes all reserved
11733 o Minor bugfixes (on 0.2.3.x):
11734 - On a failed pipe() call, don't leak file descriptors. Fixes bug
11735 4296; bugfix on 0.2.3.1-alpha.
11736 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
11737 until after we have received a CERTS cell. Fixes bug 4361; bugfix
11738 on 0.2.3.6-alpha. Patch by "frosty".
11739 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
11740 option, so that the IP stack doesn't decide to use it for IPv4
11741 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
11742 - Ensure that variables set in Tor's environment cannot override
11743 environment variables that Tor passes to a managed
11744 pluggable-transport proxy. Previously, Tor would pass every
11745 variable in its environment to managed proxies along with the new
11746 ones, in such a way that on many operating systems, the inherited
11747 environment variables would override those which Tor tried to
11748 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
11749 bugfix on 0.2.3.9-alpha for Windows.
11752 - A wide variety of new unit tests by Esteban Manchado Velázquez.
11753 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
11754 - Update to the March 6 2012 Maxmind GeoLite Country database.
11757 Changes in version 0.2.3.12-alpha - 2012-02-13
11758 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
11759 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
11760 when Tor is configured to use a pluggable transport like obfsproxy.
11763 - Fix builds when the path to sed, openssl, or sha1sum contains
11764 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
11766 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
11767 connections. This change should allow busy exit relays to stop
11768 running out of available sockets as quickly. Fixes bug 4950;
11769 bugfix on 0.2.2.26-beta.
11770 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
11771 would ask the bridge for microdescriptors, which are only supported
11772 in 0.2.3.x, and then fail to bootstrap when it didn't get the
11773 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
11774 - Properly set up obfsproxy's environment when in managed mode. The
11775 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
11776 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
11777 5076 and 5082; bugfix on 0.2.3.6-alpha.
11780 - Use the dead_strip option when building Tor on OS X. This reduces
11781 binary size by almost 19% when linking openssl and libevent
11782 statically, which we do for Tor Browser Bundle.
11783 - Fix broken URLs in the sample torrc file, and tell readers about
11784 the OutboundBindAddress, ExitPolicyRejectPrivate, and
11785 PublishServerDescriptor options. Addresses bug 4652.
11786 - Update to the February 7 2012 Maxmind GeoLite Country database.
11789 - Downgrade the "We're missing a certificate" message from notice
11790 to info: people kept mistaking it for a real problem, whereas it
11791 is seldom the problem even when we are failing to bootstrap. Fixes
11792 bug 5067; bugfix on 0.2.0.10-alpha.
11793 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
11794 managed pluggable transport server proxy's environment.
11795 Previously, we would put it there, even though Tor doesn't
11796 implement an 'extended server port' yet, and even though Tor
11797 almost certainly isn't listening at that address. For now, we set
11798 it to an empty string to avoid crashing older obfsproxies. Bugfix
11800 - Log the heartbeat message every HeartbeatPeriod seconds, not every
11801 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
11802 0.2.3.1-alpha. Bug reported by Scott Bennett.
11803 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
11804 bugfix on 0.2.3.11-alpha.
11805 - Update "ClientOnly" man page entry to explain that there isn't
11806 really any point to messing with it. Resolves ticket 5005.
11807 - Use the correct CVE number for CVE-2011-4576 in our comments and
11808 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
11811 o Code simplifications and refactoring:
11812 - Use the _WIN32 macro throughout our code to detect Windows.
11813 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
11817 Changes in version 0.2.3.11-alpha - 2012-01-22
11818 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
11819 the last step of the plan to limit maximum circuit length, includes
11820 a wide variety of hidden service performance and correctness fixes,
11821 works around an OpenSSL security flaw if your distro is too stubborn
11822 to upgrade, and fixes a bunch of smaller issues.
11825 - Now that Tor 0.2.0.x is completely deprecated, enable the final
11826 part of "Proposal 110: Avoiding infinite length circuits" by
11827 refusing all circuit-extend requests that do not use a relay_early
11828 cell. This change helps Tor resist a class of denial-of-service
11829 attacks by limiting the maximum circuit length.
11830 - Adjust the number of introduction points that a hidden service
11831 will try to maintain based on how long its introduction points
11832 remain in use and how many introductions they handle. Fixes
11834 - Try to use system facilities for enumerating local interface
11835 addresses, before falling back to our old approach (which was
11836 binding a UDP socket, and calling getsockname() on it). That
11837 approach was scaring OS X users whose draconian firewall
11838 software warned about binding to UDP sockets, regardless of
11839 whether packets were sent. Now we try to use getifaddrs(),
11840 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
11841 system supports. Resolves ticket 1827.
11843 o Major security workaround:
11844 - When building or running with any version of OpenSSL earlier
11845 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
11846 versions have a bug (CVE-2011-4576) in which their block cipher
11847 padding includes uninitialized data, potentially leaking sensitive
11848 information to any peer with whom they make a SSLv3 connection. Tor
11849 does not use SSL v3 by default, but a hostile client or server
11850 could force an SSLv3 connection in order to gain information that
11851 they shouldn't have been able to get. The best solution here is to
11852 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
11853 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
11854 to make sure that the bug can't happen.
11857 - Fix the SOCKET_OK test that we use to tell when socket
11858 creation fails so that it works on Win64. Fixes part of bug 4533;
11859 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
11860 - Correct our replacements for the timeradd() and timersub() functions
11861 on platforms that lack them (for example, Windows). The timersub()
11862 function is used when expiring circuits, while timeradd() is
11863 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
11864 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
11865 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
11866 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
11867 bug at runtime, not compile time, because some distributions hack
11868 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
11869 on 0.2.3.9-alpha. Found by Pascal.
11871 o Minor features (controller):
11872 - Use absolute path names when reporting the torrc filename in the
11873 control protocol, so a controller can more easily find the torrc
11874 file. Resolves bug 1101.
11875 - Extend the control protocol to report flags that control a circuit's
11876 path selection in CIRC events and in replies to 'GETINFO
11877 circuit-status'. Implements part of ticket 2411.
11878 - Extend the control protocol to report the hidden service address
11879 and current state of a hidden-service-related circuit in CIRC
11880 events and in replies to 'GETINFO circuit-status'. Implements part
11882 - When reporting the path to the cookie file to the controller,
11883 give an absolute path. Resolves ticket 4881.
11884 - Allow controllers to request an event notification whenever a
11885 circuit is cannibalized or its purpose is changed. Implements
11886 part of ticket 3457.
11887 - Include the creation time of a circuit in CIRC and CIRC2
11888 control-port events and the list produced by the 'GETINFO
11889 circuit-status' control-port command.
11891 o Minor features (directory authorities):
11892 - Directory authorities now reject versions of Tor older than
11893 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
11894 inclusive. These versions accounted for only a small fraction of
11895 the Tor network, and have numerous known security issues. Resolves
11897 - Authority operators can now vote for all relays in a given
11898 set of countries to be BadDir/BadExit/Invalid/Rejected.
11899 - Provide two consensus parameters (FastFlagMinThreshold and
11900 FastFlagMaxThreshold) to control the range of allowable bandwidths
11901 for the Fast directory flag. These allow authorities to run
11902 experiments on appropriate requirements for being a "Fast" node.
11903 The AuthDirFastGuarantee config value still applies. Implements
11905 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
11906 directory authority option (introduced in Tor 0.2.2.34).
11908 o Minor features (other):
11909 - Don't disable the DirPort when we cannot exceed our AccountingMax
11910 limit during this interval because the effective bandwidthrate is
11911 low enough. This is useful in a situation where AccountMax is only
11912 used as an additional safeguard or to provide statistics.
11913 - Prepend an informative header to generated dynamic_dh_params files.
11914 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
11915 EntryNodes will have no effect. Resolves issue 2571.
11916 - Log more useful messages when we fail to disable debugger
11918 - Log which authority we're missing votes from when we go to fetch
11919 them from the other auths.
11920 - Log (at debug level) whenever a circuit's purpose is changed.
11921 - Add missing documentation for the MaxClientCircuitsPending,
11922 UseMicrodescriptors, UserspaceIOCPBuffers, and
11923 _UseFilteringSSLBufferevents options, all introduced during
11924 the 0.2.3.x series.
11925 - Update to the January 3 2012 Maxmind GeoLite Country database.
11927 o Minor bugfixes (hidden services):
11928 - Don't close hidden service client circuits which have almost
11929 finished connecting to their destination when they reach
11930 the normal circuit-build timeout. Previously, we would close
11931 introduction circuits which are waiting for an acknowledgement
11932 from the introduction point, and rendezvous circuits which have
11933 been specified in an INTRODUCE1 cell sent to a hidden service,
11934 after the normal CBT. Now, we mark them as 'timed out', and launch
11935 another rendezvous attempt in parallel. This behavior change can
11936 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
11937 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
11938 - Don't close hidden-service-side rendezvous circuits when they
11939 reach the normal circuit-build timeout. This behavior change can
11940 be disabled using the new
11941 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
11942 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
11943 - Make sure we never mark the wrong rendezvous circuit as having
11944 had its introduction cell acknowleged by the introduction-point
11945 relay. Previously, when we received an INTRODUCE_ACK cell on a
11946 client-side hidden-service introduction circuit, we might have
11947 marked a rendezvous circuit other than the one we specified in
11948 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
11949 a warning message and interfered with the hidden service
11950 connection-establishment process. Fixes bug 4759; bugfix on
11951 0.2.3.3-alpha, when we added the stream-isolation feature which
11952 might cause Tor to open multiple rendezvous circuits for the same
11954 - Don't trigger an assertion failure when we mark a new client-side
11955 hidden-service introduction circuit for close during the process
11956 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
11959 o Minor bugfixes (log messages):
11960 - Correctly spell "connect" in a log message on failure to create a
11961 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
11963 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
11964 Fixes bug 4856; bugfix on Tor 0.0.6.
11965 - Fix the log message describing how we work around discovering
11966 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
11967 4837; bugfix on 0.2.2.9-alpha.
11968 - When logging about a disallowed .exit name, do not also call it
11969 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
11971 o Minor bugfixes (build fixes):
11972 - During configure, detect when we're building with clang version
11973 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
11974 CFLAGS. clang doesn't support them yet.
11975 - During configure, search for library containing cos function as
11976 libm lives in libcore on some platforms (BeOS/Haiku). Linking
11977 against libm was hard-coded before. Fixes the first part of bug
11978 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
11980 - Detect attempts to build Tor on (as yet hypothetical) versions
11981 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
11982 fix for bug 4533. Bugfix on 0.2.2.28-beta.
11983 - Preprocessor directives should not be put inside the arguments
11984 of a macro. This would break compilation with GCC releases prior
11985 to version 3.3. We would never recommend such an old GCC version,
11986 but it is apparently required for binary compatibility on some
11987 platforms (namely, certain builds of Haiku). Fixes the other part
11988 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
11991 o Minor bugfixes (other):
11992 - Older Linux kernels erroneously respond to strange nmap behavior
11993 by having accept() return successfully with a zero-length
11994 socket. When this happens, just close the connection. Previously,
11995 we would try harder to learn the remote address: but there was
11996 no such remote address to learn, and our method for trying to
11997 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
11998 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
11999 - Fix null-pointer access that could occur if TLS allocation failed.
12000 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
12001 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
12002 accidentally been reverted.
12003 - Fix our implementation of crypto_random_hostname() so it can't
12004 overflow on ridiculously large inputs. (No Tor version has ever
12005 provided this kind of bad inputs, but let's be correct in depth.)
12006 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
12007 - Find more places in the code that should have been testing for
12008 invalid sockets using the SOCKET_OK macro. Required for a fix
12009 for bug 4533. Bugfix on 0.2.2.28-beta.
12010 - Fix an assertion failure when, while running with bufferevents, a
12011 connection finishes connecting after it is marked for close, but
12012 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
12013 - test_util_spawn_background_ok() hardcoded the expected value
12014 for ENOENT to 2. This isn't portable as error numbers are
12015 platform specific, and particularly the hurd has ENOENT at
12016 0x40000002. Construct expected string at runtime, using the correct
12017 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
12018 - Reject attempts to disable DisableDebuggerAttachment while Tor is
12019 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
12020 - Use an appropriate-width type for sockets in tor-fw-helper on
12021 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
12024 - When sending or relaying a RELAY_EARLY cell, we used to convert
12025 it to a RELAY cell if the connection was using the v1 link
12026 protocol. This was a workaround for older versions of Tor, which
12027 didn't handle RELAY_EARLY cells properly. Now that all supported
12028 versions can handle RELAY_EARLY cells, and now that we're enforcing
12029 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
12030 remove this workaround. Addresses bug 4786.
12032 o Code simplifications and refactoring:
12033 - Use OpenSSL's built-in SSL_state_string_long() instead of our
12034 own homebrewed ssl_state_to_string() replacement. Patch from
12035 Emile Snyder. Fixes bug 4653.
12036 - Use macros to indicate OpenSSL versions, so we don't need to worry
12037 about accidental hexadecimal bit shifts.
12038 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
12040 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
12041 - Use the smartlist_add_asprintf() alias more consistently.
12042 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
12043 invalid value, rather than just -1.
12044 - Rename a handful of old identifiers, mostly related to crypto
12045 structures and crypto functions. By convention, our "create an
12046 object" functions are called "type_new()", our "free an object"
12047 functions are called "type_free()", and our types indicate that
12048 they are types only with a final "_t". But a handful of older
12049 types and functions broke these rules, with function names like
12050 "type_create" or "subsystem_op_type", or with type names like
12054 Changes in version 0.2.3.10-alpha - 2011-12-16
12055 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
12056 Tor's buffers code. Absolutely everybody should upgrade.
12058 The bug relied on an incorrect calculation when making data continuous
12059 in one of our IO buffers, if the first chunk of the buffer was
12060 misaligned by just the wrong amount. The miscalculation would allow an
12061 attacker to overflow a piece of heap-allocated memory. To mount this
12062 attack, the attacker would need to either open a SOCKS connection to
12063 Tor's SocksPort (usually restricted to localhost), or target a Tor
12064 instance configured to make its connections through a SOCKS proxy
12065 (which Tor does not do by default).
12067 Good security practice requires that all heap-overflow bugs should be
12068 presumed to be exploitable until proven otherwise, so we are treating
12069 this as a potential code execution attack. Please upgrade immediately!
12070 This bug does not affect bufferevents-based builds of Tor. Special
12071 thanks to "Vektor" for reporting this issue to us!
12073 This release also contains a few minor bugfixes for issues discovered
12077 - Fix a heap overflow bug that could occur when trying to pull
12078 data into the first chunk of a buffer, when that chunk had
12079 already had some data drained from it. Fixes CVE-2011-2778;
12080 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
12083 - If we can't attach streams to a rendezvous circuit when we
12084 finish connecting to a hidden service, clear the rendezvous
12085 circuit's stream-isolation state and try to attach streams
12086 again. Previously, we cleared rendezvous circuits' isolation
12087 state either too early (if they were freshly built) or not at all
12088 (if they had been built earlier and were cannibalized). Bugfix on
12089 0.2.3.3-alpha; fixes bug 4655.
12090 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
12091 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
12092 - Fix an assertion failure when a relay with accounting enabled
12093 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
12096 - Update to the December 6 2011 Maxmind GeoLite Country database.
12099 Changes in version 0.2.2.35 - 2011-12-16
12100 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
12101 buffers code. Absolutely everybody should upgrade.
12103 The bug relied on an incorrect calculation when making data continuous
12104 in one of our IO buffers, if the first chunk of the buffer was
12105 misaligned by just the wrong amount. The miscalculation would allow an
12106 attacker to overflow a piece of heap-allocated memory. To mount this
12107 attack, the attacker would need to either open a SOCKS connection to
12108 Tor's SocksPort (usually restricted to localhost), or target a Tor
12109 instance configured to make its connections through a SOCKS proxy
12110 (which Tor does not do by default).
12112 Good security practice requires that all heap-overflow bugs should be
12113 presumed to be exploitable until proven otherwise, so we are treating
12114 this as a potential code execution attack. Please upgrade immediately!
12115 This bug does not affect bufferevents-based builds of Tor. Special
12116 thanks to "Vektor" for reporting this issue to us!
12118 Tor 0.2.2.35 also fixes several bugs in previous versions, including
12119 crash bugs for unusual configurations, and a long-term bug that
12120 would prevent Tor from starting on Windows machines with draconian
12123 With this release, we remind everyone that 0.2.0.x has reached its
12124 formal end-of-life. Those Tor versions have many known flaws, and
12125 nobody should be using them. You should upgrade -- ideally to the
12126 0.2.2.x series. If you're using a Linux or BSD and its packages are
12127 obsolete, stop using those packages and upgrade anyway.
12129 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
12130 longer receive support after some time in early 2012.
12133 - Fix a heap overflow bug that could occur when trying to pull
12134 data into the first chunk of a buffer, when that chunk had
12135 already had some data drained from it. Fixes CVE-2011-2778;
12136 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
12137 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
12138 that it doesn't attempt to allocate a socketpair. This could cause
12139 some problems on Windows systems with overzealous firewalls. Fix for
12140 bug 4457; workaround for Libevent versions 2.0.1-alpha through
12142 - If we mark an OR connection for close based on a cell we process,
12143 don't process any further cells on it. We already avoid further
12144 reads on marked-for-close connections, but now we also discard the
12145 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
12146 which was the first version where we might mark a connection for
12147 close based on processing a cell on it.
12148 - Correctly sanity-check that we don't underflow on a memory
12149 allocation (and then assert) for hidden service introduction
12150 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
12151 bugfix on 0.2.1.5-alpha.
12152 - Fix a memory leak when we check whether a hidden service
12153 descriptor has any usable introduction points left. Fixes bug
12154 4424. Bugfix on 0.2.2.25-alpha.
12155 - Don't crash when we're running as a relay and don't have a GeoIP
12156 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
12157 we've had in the 0.2.3.x branch already.
12158 - When running as a client, do not print a misleading (and plain
12159 wrong) log message that we're collecting "directory request"
12160 statistics: clients don't collect statistics. Also don't create a
12161 useless (because empty) stats file in the stats/ directory. Fixes
12162 bug 4353; bugfix on 0.2.2.34.
12165 - Detect failure to initialize Libevent. This fix provides better
12166 detection for future instances of bug 4457.
12167 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
12168 function. This was eating up hideously large amounts of time on some
12169 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
12170 - Resolve an integer overflow bug in smartlist_ensure_capacity().
12171 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
12173 - Don't warn about unused log_mutex in log.c when building with
12174 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
12175 0.1.0.6-rc which introduced --disable-threads.
12176 - When configuring, starting, or stopping an NT service, stop
12177 immediately after the service configuration attempt has succeeded
12178 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
12179 - When sending a NETINFO cell, include the original address
12180 received for the other side, not its canonical address. Found
12181 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
12182 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
12183 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
12184 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
12185 occurred when a client tried to fetch a descriptor for a bridge
12186 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
12187 - Backport fixes for a pair of compilation warnings on Windows.
12188 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
12189 - If we had ever tried to call tor_addr_to_str on an address of
12190 unknown type, we would have done a strdup on an uninitialized
12191 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
12192 Reported by "troll_un".
12193 - Correctly detect and handle transient lookup failures from
12194 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
12195 Reported by "troll_un".
12196 - Fix null-pointer access that could occur if TLS allocation failed.
12197 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
12198 - Use tor_socket_t type for listener argument to accept(). Fixes bug
12199 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
12202 - Add two new config options for directory authorities:
12203 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
12204 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
12205 that is always sufficient to satisfy the bandwidth requirement for
12206 the Guard flag. Now it will be easier for researchers to simulate
12207 Tor networks with different values. Resolves ticket 4484.
12208 - When Tor ignores a hidden service specified in its configuration,
12209 include the hidden service's directory in the warning message.
12210 Previously, we would only tell the user that some hidden service
12211 was ignored. Bugfix on 0.0.6; fixes bug 4426.
12212 - Update to the December 6 2011 Maxmind GeoLite Country database.
12214 o Packaging changes:
12215 - Make it easier to automate expert package builds on Windows,
12216 by removing an absolute path from makensis.exe command.
12219 Changes in version 0.2.1.32 - 2011-12-16
12220 Tor 0.2.1.32 backports important security and privacy fixes for
12221 oldstable. This release is intended only for package maintainers and
12222 others who cannot use the 0.2.2 stable series. All others should be
12223 using Tor 0.2.2.x or newer.
12225 The Tor 0.2.1.x series will reach formal end-of-life some time in
12226 early 2012; we will stop releasing patches for it then.
12228 o Major bugfixes (also included in 0.2.2.x):
12229 - Correctly sanity-check that we don't underflow on a memory
12230 allocation (and then assert) for hidden service introduction
12231 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
12232 bugfix on 0.2.1.5-alpha.
12233 - Fix a heap overflow bug that could occur when trying to pull
12234 data into the first chunk of a buffer, when that chunk had
12235 already had some data drained from it. Fixes CVE-2011-2778;
12236 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
12239 - Update to the December 6 2011 Maxmind GeoLite Country database.
12242 Changes in version 0.2.3.9-alpha - 2011-12-08
12243 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
12244 a "DisableNetwork" security feature that bundles can use to avoid
12245 touching the network until bridges are configured, moves forward on
12246 the pluggable transport design, fixes a flaw in the hidden service
12247 design that unnecessarily prevented clients with wrong clocks from
12248 reaching hidden services, and fixes a wide variety of other issues.
12251 - Clients can now connect to private bridges over IPv6. Bridges
12252 still need at least one IPv4 address in order to connect to
12253 other relays. Note that we don't yet handle the case where the
12254 user has two bridge lines for the same bridge (one IPv4, one
12255 IPv6). Implements parts of proposal 186.
12256 - New "DisableNetwork" config option to prevent Tor from launching any
12257 connections or accepting any connections except on a control port.
12258 Bundles and controllers can set this option before letting Tor talk
12259 to the rest of the network, for example to prevent any connections
12260 to a non-bridge address. Packages like Orbot can also use this
12261 option to instruct Tor to save power when the network is off.
12262 - Clients and bridges can now be configured to use a separate
12263 "transport" proxy. This approach makes the censorship arms race
12264 easier by allowing bridges to use protocol obfuscation plugins. It
12265 implements the "managed proxy" part of proposal 180 (ticket 3472).
12266 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
12267 implementation. It makes AES_CTR about 7% faster than our old one
12268 (which was about 10% faster than the one OpenSSL used to provide).
12269 Resolves ticket 4526.
12270 - Add a "tor2web mode" for clients that want to connect to hidden
12271 services non-anonymously (and possibly more quickly). As a safety
12272 measure to try to keep users from turning this on without knowing
12273 what they are doing, tor2web mode must be explicitly enabled at
12274 compile time, and a copy of Tor compiled to run in tor2web mode
12275 cannot be used as a normal Tor client. Implements feature 2553.
12276 - Add experimental support for running on Windows with IOCP and no
12277 kernel-space socket buffers. This feature is controlled by a new
12278 "UserspaceIOCPBuffers" config option (off by default), which has
12279 no effect unless Tor has been built with support for bufferevents,
12280 is running on Windows, and has enabled IOCP. This may, in the long
12281 run, help solve or mitigate bug 98.
12282 - Use a more secure consensus parameter voting algorithm. Now at
12283 least three directory authorities or a majority of them must
12284 vote on a given parameter before it will be included in the
12285 consensus. Implements proposal 178.
12288 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
12289 They used to check that the timestamp was within 30 minutes
12290 of their system clock, so they could cap the size of their
12291 replay-detection cache, but that approach unnecessarily refused
12292 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
12293 the v3 intro-point protocol (the first one which sent a timestamp
12294 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
12295 - Only use the EVP interface when AES acceleration is enabled,
12296 to avoid a 5-7% performance regression. Resolves issue 4525;
12297 bugfix on 0.2.3.8-alpha.
12299 o Privacy/anonymity features (bridge detection):
12300 - Make bridge SSL certificates a bit more stealthy by using random
12301 serial numbers, in the same fashion as OpenSSL when generating
12302 self-signed certificates. Implements ticket 4584.
12303 - Introduce a new config option "DynamicDHGroups", enabled by
12304 default, which provides each bridge with a unique prime DH modulus
12305 to be used during SSL handshakes. This option attempts to help
12306 against censors who might use the Apache DH modulus as a static
12307 identifier for bridges. Addresses ticket 4548.
12309 o Minor features (new/different config options):
12310 - New configuration option "DisableDebuggerAttachment" (on by default)
12311 to prevent basic debugging attachment attempts by other processes.
12312 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
12313 - Allow MapAddress directives to specify matches against super-domains,
12314 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
12315 Implements issue 933.
12316 - Slightly change behavior of "list" options (that is, config
12317 options that can appear more than once) when they appear both in
12318 torrc and on the command line. Previously, the command-line options
12319 would be appended to the ones from torrc. Now, the command-line
12320 options override the torrc options entirely. This new behavior
12321 allows the user to override list options (like exit policies and
12322 ports to listen on) from the command line, rather than simply
12323 appending to the list.
12324 - You can get the old (appending) command-line behavior for "list"
12325 options by prefixing the option name with a "+".
12326 - You can remove all the values for a "list" option from the command
12327 line without adding any new ones by prefixing the option name
12329 - Add experimental support for a "defaults" torrc file to be parsed
12330 before the regular torrc. Torrc options override the defaults file's
12331 options in the same way that the command line overrides the torrc.
12332 The SAVECONF controller command saves only those options which
12333 differ between the current configuration and the defaults file. HUP
12334 reloads both files. (Note: This is an experimental feature; its
12335 behavior will probably be refined in future 0.2.3.x-alpha versions
12336 to better meet packagers' needs.) Implements task 4552.
12339 - Try to make the introductory warning message that Tor prints on
12340 startup more useful for actually finding help and information.
12341 Resolves ticket 2474.
12342 - Running "make version" now displays the version of Tor that
12343 we're about to build. Idea from katmagic; resolves issue 4400.
12344 - Expire old or over-used hidden service introduction points.
12345 Required by fix for bug 3460.
12346 - Move the replay-detection cache for the RSA-encrypted parts of
12347 INTRODUCE2 cells to the introduction point data structures.
12348 Previously, we would use one replay-detection cache per hidden
12349 service. Required by fix for bug 3460.
12350 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
12351 public key replay-detection cache from 60 minutes to 5 minutes. This
12352 replay-detection cache is now used only to detect multiple
12353 INTRODUCE2 cells specifying the same rendezvous point, so we can
12354 avoid launching multiple simultaneous attempts to connect to it.
12356 o Minor bugfixes (on Tor 0.2.2.x and earlier):
12357 - Resolve an integer overflow bug in smartlist_ensure_capacity().
12358 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
12360 - Fix a minor formatting issue in one of tor-gencert's error messages.
12362 - Prevent a false positive from the check-spaces script, by disabling
12363 the "whitespace between function name and (" check for functions
12365 - Fix a log message suggesting that people contact a non-existent
12366 email address. Fixes bug 3448.
12367 - Fix null-pointer access that could occur if TLS allocation failed.
12368 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
12369 - Report a real bootstrap problem to the controller on router
12370 identity mismatch. Previously we just said "foo", which probably
12371 made a lot of sense at the time. Fixes bug 4169; bugfix on
12373 - If we had ever tried to call tor_addr_to_str() on an address of
12374 unknown type, we would have done a strdup() on an uninitialized
12375 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
12376 Reported by "troll_un".
12377 - Correctly detect and handle transient lookup failures from
12378 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
12379 Reported by "troll_un".
12380 - Use tor_socket_t type for listener argument to accept(). Fixes bug
12381 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
12382 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
12383 bug 4532; found by "troll_un".
12385 o Minor bugfixes (on Tor 0.2.3.x):
12386 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
12388 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
12389 circuit for use as a hidden service client's rendezvous point.
12390 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
12391 with help from wanoskarnet.
12392 - Restore behavior of overriding SocksPort, ORPort, and similar
12393 options from the command line. Bugfix on 0.2.3.3-alpha.
12396 - Properly handle the case where the build-tree is not the same
12397 as the source tree when generating src/common/common_sha1.i,
12398 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
12399 bugfix on 0.2.0.1-alpha.
12401 o Code simplifications, cleanups, and refactorings:
12402 - Remove the pure attribute from all functions that used it
12403 previously. In many cases we assigned it incorrectly, because the
12404 functions might assert or call impure functions, and we don't have
12405 evidence that keeping the pure attribute is worthwhile. Implements
12406 changes suggested in ticket 4421.
12407 - Remove some dead code spotted by coverity. Fixes cid 432.
12408 Bugfix on 0.2.3.1-alpha, closes bug 4637.
12411 Changes in version 0.2.3.8-alpha - 2011-11-22
12412 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
12413 socketpair-related bug that has been bothering Windows users. It adds
12414 support to serve microdescriptors to controllers, so Vidalia's network
12415 map can resume listing relays (once Vidalia implements its side),
12416 and adds better support for hardware AES acceleration. Finally, it
12417 starts the process of adjusting the bandwidth cutoff for getting the
12418 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
12419 that tiny relays harm performance more than they help network capacity.
12422 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
12423 that it doesn't attempt to allocate a socketpair. This could cause
12424 some problems on Windows systems with overzealous firewalls. Fix for
12425 bug 4457; workaround for Libevent versions 2.0.1-alpha through
12427 - Correctly sanity-check that we don't underflow on a memory
12428 allocation (and then assert) for hidden service introduction
12429 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
12430 bugfix on 0.2.1.5-alpha.
12431 - Remove the artificially low cutoff of 20KB to guarantee the Fast
12432 flag. In the past few years the average relay speed has picked
12433 up, and while the "top 7/8 of the network get the Fast flag" and
12434 "all relays with 20KB or more of capacity get the Fast flag" rules
12435 used to have the same result, now the top 7/8 of the network has
12436 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
12437 - Fix a rare assertion failure when checking whether a v0 hidden
12438 service descriptor has any usable introduction points left, and
12439 we don't have enough information to build a circuit to the first
12440 intro point named in the descriptor. The HS client code in
12441 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
12442 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
12443 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
12444 - Make bridge authorities not crash when they are asked for their own
12445 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
12446 - When running as a client, do not print a misleading (and plain
12447 wrong) log message that we're collecting "directory request"
12448 statistics: clients don't collect statistics. Also don't create a
12449 useless (because empty) stats file in the stats/ directory. Fixes
12450 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
12453 - Allow Tor controllers like Vidalia to obtain the microdescriptor
12454 for a relay by identity digest or nickname. Previously,
12455 microdescriptors were only available by their own digests, so a
12456 controller would have to ask for and parse the whole microdescriptor
12457 consensus in order to look up a single relay's microdesc. Fixes
12458 bug 3832; bugfix on 0.2.3.1-alpha.
12459 - Use OpenSSL's EVP interface for AES encryption, so that all AES
12460 operations can use hardware acceleration (if present). Resolves
12463 o Minor bugfixes (on 0.2.2.x and earlier):
12464 - Detect failure to initialize Libevent. This fix provides better
12465 detection for future instances of bug 4457.
12466 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
12467 function. This was eating up hideously large amounts of time on some
12468 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
12469 - Don't warn about unused log_mutex in log.c when building with
12470 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
12471 0.1.0.6-rc which introduced --disable-threads.
12472 - Allow manual 'authenticate' commands to the controller interface
12473 from netcat (nc) as well as telnet. We were rejecting them because
12474 they didn't come with the expected whitespace at the end of the
12475 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
12476 - Fix some (not actually triggerable) buffer size checks in usage of
12477 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
12479 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
12480 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
12481 - When configuring, starting, or stopping an NT service, stop
12482 immediately after the service configuration attempt has succeeded
12483 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
12484 - When sending a NETINFO cell, include the original address
12485 received for the other side, not its canonical address. Found
12486 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
12487 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
12488 can pick them up when the tests aren't disabled. Bugfix on
12489 0.2.2.4-alpha which introduced tinytest.
12490 - Fix a memory leak when we check whether a hidden service
12491 descriptor has any usable introduction points left. Fixes bug
12492 4424. Bugfix on 0.2.2.25-alpha.
12493 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
12494 occurred when a client tried to fetch a descriptor for a bridge
12495 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
12497 o Minor bugfixes (on 0.2.3.x):
12498 - Make util unit tests build correctly with MSVC. Bugfix on
12499 0.2.3.3-alpha. Patch by Gisle Vanem.
12500 - Successfully detect AUTH_CHALLENGE cells with no recognized
12501 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
12502 Found by frosty_un.
12503 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
12504 it should still send a NETINFO cell to allow the connection to
12505 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
12507 - Log less loudly when we get an invalid authentication certificate
12508 from a source other than a directory authority: it's not unusual
12509 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
12511 - Tolerate servers with more clock skew in their authentication
12512 certificates than previously. Fixes bug 4371; bugfix on
12514 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
12515 on 0.2.3.4-alpha and 0.2.3.6-alpha.
12518 - Add two new config options for directory authorities:
12519 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
12520 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
12521 that is always sufficient to satisfy the bandwidth requirement for
12522 the Guard flag. Now it will be easier for researchers to simulate
12523 Tor networks with different values. Resolves ticket 4484.
12524 - When Tor ignores a hidden service specified in its configuration,
12525 include the hidden service's directory in the warning message.
12526 Previously, we would only tell the user that some hidden service
12527 was ignored. Bugfix on 0.0.6; fixes bug 4426.
12528 - When we fail to initialize Libevent, retry with IOCP disabled so we
12529 don't need to turn on multi-threading support in Libevent, which in
12530 turn requires a working socketpair(). This is a workaround for bug
12531 4457, which affects Libevent versions from 2.0.1-alpha through
12533 - Detect when we try to build on a platform that doesn't define
12534 AF_UNSPEC to 0. We don't work there, so refuse to compile.
12535 - Update to the November 1 2011 Maxmind GeoLite Country database.
12537 o Packaging changes:
12538 - Make it easier to automate expert package builds on Windows,
12539 by removing an absolute path from makensis.exe command.
12541 o Code simplifications and refactoring:
12542 - Remove some redundant #include directives throughout the code.
12543 Patch from Andrea Gelmini.
12544 - Unconditionally use OpenSSL's AES implementation instead of our
12545 old built-in one. OpenSSL's AES has been better for a while, and
12546 relatively few servers should still be on any version of OpenSSL
12547 that doesn't have good optimized assembly AES.
12548 - Use the name "CERTS" consistently to refer to the new cell type;
12549 we were calling it CERT in some places and CERTS in others.
12552 - Numerous new unit tests for functions in util.c and address.c by
12554 - The long-disabled benchmark tests are now split into their own
12555 ./src/test/bench binary.
12556 - The benchmark tests can now use more accurate timers than
12557 gettimeofday() when such timers are available.
12560 Changes in version 0.2.3.7-alpha - 2011-10-30
12561 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
12562 the new v3 handshake. It also resolves yet another bridge address
12566 - If we mark an OR connection for close based on a cell we process,
12567 don't process any further cells on it. We already avoid further
12568 reads on marked-for-close connections, but now we also discard the
12569 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
12570 which was the first version where we might mark a connection for
12571 close based on processing a cell on it.
12572 - Fix a double-free bug that would occur when we received an invalid
12573 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
12574 bugfix on 0.2.3.6-alpha.
12575 - Bridges no longer include their address in NETINFO cells on outgoing
12576 OR connections, to allow them to blend in better with clients.
12577 Removes another avenue for enumerating bridges. Reported by
12578 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
12579 cells were introduced.
12582 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
12583 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
12586 Changes in version 0.2.3.6-alpha - 2011-10-26
12587 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
12588 anonymity vulnerability where an attacker can deanonymize Tor
12589 users. Everybody should upgrade.
12591 This release also features support for a new v3 connection handshake
12592 protocol, and fixes to make hidden service connections more robust.
12595 - Implement a new handshake protocol (v3) for authenticating Tors to
12596 each other over TLS. It should be more resistant to fingerprinting
12597 than previous protocols, and should require less TLS hacking for
12598 future Tor implementations. Implements proposal 176.
12599 - Allow variable-length padding cells to disguise the length of
12600 Tor's TLS records. Implements part of proposal 184.
12602 o Privacy/anonymity fixes (clients):
12603 - Clients and bridges no longer send TLS certificate chains on
12604 outgoing OR connections. Previously, each client or bridge would
12605 use the same cert chain for all outgoing OR connections until
12606 its IP address changes, which allowed any relay that the client
12607 or bridge contacted to determine which entry guards it is using.
12608 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
12609 - If a relay receives a CREATE_FAST cell on a TLS connection, it
12610 no longer considers that connection as suitable for satisfying a
12611 circuit EXTEND request. Now relays can protect clients from the
12612 CVE-2011-2768 issue even if the clients haven't upgraded yet.
12613 - Directory authorities no longer assign the Guard flag to relays
12614 that haven't upgraded to the above "refuse EXTEND requests
12615 to client connections" fix. Now directory authorities can
12616 protect clients from the CVE-2011-2768 issue even if neither
12617 the clients nor the relays have upgraded yet. There's a new
12618 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
12619 to let us transition smoothly, else tomorrow there would be no
12622 o Major bugfixes (hidden services):
12623 - Improve hidden service robustness: when an attempt to connect to
12624 a hidden service ends, be willing to refetch its hidden service
12625 descriptors from each of the HSDir relays responsible for them
12626 immediately. Previously, we would not consider refetching the
12627 service's descriptors from each HSDir for 15 minutes after the last
12628 fetch, which was inconvenient if the hidden service was not running
12629 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
12630 - When one of a hidden service's introduction points appears to be
12631 unreachable, stop trying it. Previously, we would keep trying
12632 to build circuits to the introduction point until we lost the
12633 descriptor, usually because the user gave up and restarted Tor.
12634 Partly fixes bug 3825.
12635 - Don't launch a useless circuit after failing to use one of a
12636 hidden service's introduction points. Previously, we would
12637 launch a new introduction circuit, but not set the hidden service
12638 which that circuit was intended to connect to, so it would never
12639 actually be used. A different piece of code would then create a
12640 new introduction circuit correctly. Bug reported by katmagic and
12641 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
12643 o Major bugfixes (other):
12644 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
12645 that they initiated. Relays could distinguish incoming bridge
12646 connections from client connections, creating another avenue for
12647 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
12648 Found by "frosty_un".
12649 - Don't update the AccountingSoftLimitHitAt state file entry whenever
12650 tor gets started. This prevents a wrong average bandwidth
12651 estimate, which would cause relays to always start a new accounting
12652 interval at the earliest possible moment. Fixes bug 2003; bugfix
12653 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
12654 immensely in tracking this bug down.
12655 - Fix a crash bug when changing node restrictions while a DNS lookup
12656 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
12659 o Minor bugfixes (on 0.2.2.x and earlier):
12660 - When a hidden service turns an extra service-side introduction
12661 circuit into a general-purpose circuit, free the rend_data and
12662 intro_key fields first, so we won't leak memory if the circuit
12663 is cannibalized for use as another service-side introduction
12664 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
12665 - Rephrase the log message emitted if the TestSocks check is
12666 successful. Patch from Fabian Keil; fixes bug 4094.
12667 - Bridges now skip DNS self-tests, to act a little more stealthily.
12668 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
12669 bridges. Patch by "warms0x".
12670 - Remove a confusing dollar sign from the example fingerprint in the
12671 man page, and also make the example fingerprint a valid one. Fixes
12672 bug 4309; bugfix on 0.2.1.3-alpha.
12673 - Fix internal bug-checking logic that was supposed to catch
12674 failures in digest generation so that it will fail more robustly
12675 if we ask for a nonexistent algorithm. Found by Coverity Scan.
12676 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
12677 - Report any failure in init_keys() calls launched because our
12678 IP address has changed. Spotted by Coverity Scan. Bugfix on
12679 0.1.1.4-alpha; fixes CID 484.
12681 o Minor bugfixes (on 0.2.3.x):
12682 - Fix a bug in configure.in that kept it from building a configure
12683 script with autoconf versions earlier than 2.61. Fixes bug 2430;
12684 bugfix on 0.2.3.1-alpha.
12685 - Don't warn users that they are exposing a client port to the
12686 Internet if they have specified an RFC1918 address. Previously,
12687 we would warn if the user had specified any non-loopback
12688 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
12689 - Fix memory leaks in the failing cases of the new SocksPort and
12690 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
12691 fixes coverity CIDs 485, 486, and 487.
12694 - When a hidden service's introduction point times out, consider
12695 trying it again during the next attempt to connect to the
12696 HS. Previously, we would not try it again unless a newly fetched
12697 descriptor contained it. Required by fixes for bugs 1297 and 3825.
12698 - The next version of Windows will be called Windows 8, and it has
12699 a major version of 6, minor version of 2. Correctly identify that
12700 version instead of calling it "Very recent version". Resolves
12701 ticket 4153; reported by funkstar.
12702 - The Bridge Authority now writes statistics on how many bridge
12703 descriptors it gave out in total, and how many unique descriptors
12704 it gave out. It also lists how often the most and least commonly
12705 fetched descriptors were given out, as well as the median and
12706 25th/75th percentile. Implements tickets 4200 and 4294.
12707 - Update to the October 4 2011 Maxmind GeoLite Country database.
12709 o Code simplifications and refactoring:
12710 - Remove some old code to remember statistics about which descriptors
12711 we've served as a directory mirror. The feature wasn't used and
12712 is outdated now that microdescriptors are around.
12713 - Rename Tor functions that turn strings into addresses, so that
12714 "parse" indicates that no hostname resolution occurs, and
12715 "lookup" indicates that hostname resolution may occur. This
12716 should help prevent mistakes in the future. Fixes bug 3512.
12719 Changes in version 0.2.2.34 - 2011-10-26
12720 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
12721 can deanonymize Tor users. Everybody should upgrade.
12723 The attack relies on four components: 1) Clients reuse their TLS cert
12724 when talking to different relays, so relays can recognize a user by
12725 the identity key in her cert. 2) An attacker who knows the client's
12726 identity key can probe each guard relay to see if that identity key
12727 is connected to that guard relay right now. 3) A variety of active
12728 attacks in the literature (starting from "Low-Cost Traffic Analysis
12729 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
12730 discover the guard relays that a Tor user visiting the website is using.
12731 4) Clients typically pick three guards at random, so the set of guards
12732 for a given user could well be a unique fingerprint for her. This
12733 release fixes components #1 and #2, which is enough to block the attack;
12734 the other two remain as open research problems. Special thanks to
12735 "frosty_un" for reporting the issue to us!
12737 Clients should upgrade so they are no longer recognizable by the TLS
12738 certs they present. Relays should upgrade so they no longer allow a
12739 remote attacker to probe them to test whether unpatched clients are
12740 currently connected to them.
12742 This release also fixes several vulnerabilities that allow an attacker
12743 to enumerate bridge relays. Some bridge enumeration attacks still
12744 remain; see for example proposal 188.
12746 o Privacy/anonymity fixes (clients):
12747 - Clients and bridges no longer send TLS certificate chains on
12748 outgoing OR connections. Previously, each client or bridge would
12749 use the same cert chain for all outgoing OR connections until
12750 its IP address changes, which allowed any relay that the client
12751 or bridge contacted to determine which entry guards it is using.
12752 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
12753 - If a relay receives a CREATE_FAST cell on a TLS connection, it
12754 no longer considers that connection as suitable for satisfying a
12755 circuit EXTEND request. Now relays can protect clients from the
12756 CVE-2011-2768 issue even if the clients haven't upgraded yet.
12757 - Directory authorities no longer assign the Guard flag to relays
12758 that haven't upgraded to the above "refuse EXTEND requests
12759 to client connections" fix. Now directory authorities can
12760 protect clients from the CVE-2011-2768 issue even if neither
12761 the clients nor the relays have upgraded yet. There's a new
12762 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
12763 to let us transition smoothly, else tomorrow there would be no
12766 o Privacy/anonymity fixes (bridge enumeration):
12767 - Bridge relays now do their directory fetches inside Tor TLS
12768 connections, like all the other clients do, rather than connecting
12769 directly to the DirPort like public relays do. Removes another
12770 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
12771 - Bridges relays now build circuits for themselves in a more similar
12772 way to how clients build them. Removes another avenue for
12773 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
12774 when bridges were introduced.
12775 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
12776 that they initiated. Relays could distinguish incoming bridge
12777 connections from client connections, creating another avenue for
12778 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
12779 Found by "frosty_un".
12782 - Fix a crash bug when changing node restrictions while a DNS lookup
12783 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
12785 - Don't launch a useless circuit after failing to use one of a
12786 hidden service's introduction points. Previously, we would
12787 launch a new introduction circuit, but not set the hidden service
12788 which that circuit was intended to connect to, so it would never
12789 actually be used. A different piece of code would then create a
12790 new introduction circuit correctly. Bug reported by katmagic and
12791 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
12794 - Change an integer overflow check in the OpenBSD_Malloc code so
12795 that GCC is less likely to eliminate it as impossible. Patch
12796 from Mansour Moufid. Fixes bug 4059.
12797 - When a hidden service turns an extra service-side introduction
12798 circuit into a general-purpose circuit, free the rend_data and
12799 intro_key fields first, so we won't leak memory if the circuit
12800 is cannibalized for use as another service-side introduction
12801 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
12802 - Bridges now skip DNS self-tests, to act a little more stealthily.
12803 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
12804 bridges. Patch by "warms0x".
12805 - Fix internal bug-checking logic that was supposed to catch
12806 failures in digest generation so that it will fail more robustly
12807 if we ask for a nonexistent algorithm. Found by Coverity Scan.
12808 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
12809 - Report any failure in init_keys() calls launched because our
12810 IP address has changed. Spotted by Coverity Scan. Bugfix on
12811 0.1.1.4-alpha; fixes CID 484.
12813 o Minor bugfixes (log messages and documentation):
12814 - Remove a confusing dollar sign from the example fingerprint in the
12815 man page, and also make the example fingerprint a valid one. Fixes
12816 bug 4309; bugfix on 0.2.1.3-alpha.
12817 - The next version of Windows will be called Windows 8, and it has
12818 a major version of 6, minor version of 2. Correctly identify that
12819 version instead of calling it "Very recent version". Resolves
12820 ticket 4153; reported by funkstar.
12821 - Downgrade log messages about circuit timeout calibration from
12822 "notice" to "info": they don't require or suggest any human
12823 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
12824 bugfix on 0.2.2.14-alpha.
12827 - Turn on directory request statistics by default and include them in
12828 extra-info descriptors. Don't break if we have no GeoIP database.
12829 Backported from 0.2.3.1-alpha; implements ticket 3951.
12830 - Update to the October 4 2011 Maxmind GeoLite Country database.
12833 Changes in version 0.2.1.31 - 2011-10-26
12834 Tor 0.2.1.31 backports important security and privacy fixes for
12835 oldstable. This release is intended only for package maintainers and
12836 others who cannot use the 0.2.2 stable series. All others should be
12837 using Tor 0.2.2.x or newer.
12839 o Security fixes (also included in 0.2.2.x):
12840 - Replace all potentially sensitive memory comparison operations
12841 with versions whose runtime does not depend on the data being
12842 compared. This will help resist a class of attacks where an
12843 adversary can use variations in timing information to learn
12844 sensitive data. Fix for one case of bug 3122. (Safe memcmp
12845 implementation by Robert Ransom based partially on code by DJB.)
12846 - Fix an assert in parsing router descriptors containing IPv6
12847 addresses. This one took down the directory authorities when
12848 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
12850 o Privacy/anonymity fixes (also included in 0.2.2.x):
12851 - Clients and bridges no longer send TLS certificate chains on
12852 outgoing OR connections. Previously, each client or bridge would
12853 use the same cert chain for all outgoing OR connections until
12854 its IP address changes, which allowed any relay that the client
12855 or bridge contacted to determine which entry guards it is using.
12856 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
12857 - If a relay receives a CREATE_FAST cell on a TLS connection, it
12858 no longer considers that connection as suitable for satisfying a
12859 circuit EXTEND request. Now relays can protect clients from the
12860 CVE-2011-2768 issue even if the clients haven't upgraded yet.
12861 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
12862 that they initiated. Relays could distinguish incoming bridge
12863 connections from client connections, creating another avenue for
12864 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
12865 Found by "frosty_un".
12866 - When receiving a hidden service descriptor, check that it is for
12867 the hidden service we wanted. Previously, Tor would store any
12868 hidden service descriptors that a directory gave it, whether it
12869 wanted them or not. This wouldn't have let an attacker impersonate
12870 a hidden service, but it did let directories pre-seed a client
12871 with descriptors that it didn't want. Bugfix on 0.0.6.
12872 - Avoid linkability based on cached hidden service descriptors: forget
12873 all hidden service descriptors cached as a client when processing a
12874 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
12875 - Make the bridge directory authority refuse to answer directory
12876 requests for "all" descriptors. It used to include bridge
12877 descriptors in its answer, which was a major information leak.
12878 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
12879 - Don't attach new streams to old rendezvous circuits after SIGNAL
12880 NEWNYM. Previously, we would keep using an existing rendezvous
12881 circuit if it remained open (i.e. if it were kept open by a
12882 long-lived stream, or if a new stream were attached to it before
12883 Tor could notice that it was old and no longer in use). Bugfix on
12884 0.1.1.15-rc; fixes bug 3375.
12886 o Minor bugfixes (also included in 0.2.2.x):
12887 - When we restart our relay, we might get a successful connection
12888 from the outside before we've started our reachability tests,
12889 triggering a warning: "ORPort found reachable, but I have no
12890 routerinfo yet. Failing to inform controller of success." This
12891 bug was harmless unless Tor is running under a controller
12892 like Vidalia, in which case the controller would never get a
12893 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
12895 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
12896 enabled. Fixes bug 1526.
12897 - Remove undocumented option "-F" from tor-resolve: it hasn't done
12898 anything since 0.2.1.16-rc.
12899 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
12900 None of the cases where we did this before were wrong, but by making
12901 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
12902 - Fix a rare crash bug that could occur when a client was configured
12903 with a large number of bridges. Fixes bug 2629; bugfix on
12904 0.2.1.2-alpha. Bugfix by trac user "shitlei".
12905 - Correct the warning displayed when a rendezvous descriptor exceeds
12906 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
12908 - Fix an uncommon assertion failure when running with DNSPort under
12909 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
12910 - When warning about missing zlib development packages during compile,
12911 give the correct package names. Bugfix on 0.2.0.1-alpha.
12912 - Require that introduction point keys and onion keys have public
12913 exponent 65537. Bugfix on 0.2.0.10-alpha.
12914 - Do not crash when our configuration file becomes unreadable, for
12915 example due to a permissions change, between when we start up
12916 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
12918 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
12920 - Always NUL-terminate the sun_path field of a sockaddr_un before
12921 passing it to the kernel. (Not a security issue: kernels are
12922 smart enough to reject bad sockaddr_uns.) Found by Coverity;
12923 CID #428. Bugfix on Tor 0.2.0.3-alpha.
12924 - Don't stack-allocate the list of supplementary GIDs when we're
12925 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
12926 could take up to 256K, which is way too much stack. Found by
12927 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
12929 o Minor bugfixes (only in 0.2.1.x):
12930 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
12931 rely on them. Bugfix on 0.2.1.30.
12932 - Use git revisions instead of svn revisions when generating our
12933 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
12935 o Minor features (also included in 0.2.2.x):
12936 - Adjust the expiration time on our SSL session certificates to
12937 better match SSL certs seen in the wild. Resolves ticket 4014.
12938 - Allow nameservers with IPv6 address. Resolves bug 2574.
12939 - Update to the October 4 2011 Maxmind GeoLite Country database.
12942 Changes in version 0.2.3.5-alpha - 2011-09-28
12943 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
12944 bridge relays; fixes an assertion error that many users started hitting
12945 today; and adds the ability to refill token buckets more often than
12946 once per second, allowing significant performance improvements.
12949 - Bridge relays now do their directory fetches inside Tor TLS
12950 connections, like all the other clients do, rather than connecting
12951 directly to the DirPort like public relays do. Removes another
12952 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
12953 - Bridges relays now build circuits for themselves in a more similar
12954 way to how clients build them. Removes another avenue for
12955 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
12956 when bridges were introduced.
12959 - Fix an "Assertion md->held_by_node == 1 failed" error that could
12960 occur when the same microdescriptor was referenced by two node_t
12961 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
12963 o Major features (networking):
12964 - Add a new TokenBucketRefillInterval option to refill token buckets
12965 more frequently than once per second. This should improve network
12966 performance, alleviate queueing problems, and make traffic less
12967 bursty. Implements proposal 183; closes ticket 3630. Design by
12968 Florian Tschorsch and Björn Scheuermann; implementation by
12972 - Change an integer overflow check in the OpenBSD_Malloc code so
12973 that GCC is less likely to eliminate it as impossible. Patch
12974 from Mansour Moufid. Fixes bug 4059.
12976 o Minor bugfixes (usability):
12977 - Downgrade log messages about circuit timeout calibration from
12978 "notice" to "info": they don't require or suggest any human
12979 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
12980 bugfix on 0.2.2.14-alpha.
12982 o Minor features (diagnostics):
12983 - When the system call to create a listener socket fails, log the
12984 error message explaining why. This may help diagnose bug 4027.
12987 Changes in version 0.2.3.4-alpha - 2011-09-13
12988 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
12989 tweak to Tor's TLS handshake that makes relays and bridges that run
12990 this new version reachable from Iran again. It also fixes a few new
12991 bugs in 0.2.3.x, and teaches relays to recognize when they're not
12992 listed in the network consensus and republish.
12994 o Major bugfixes (also part of 0.2.2.33):
12995 - Avoid an assertion failure when reloading a configuration with
12996 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
12997 3923; bugfix on 0.2.2.25-alpha.
12999 o Minor features (security, also part of 0.2.2.33):
13000 - Check for replays of the public-key encrypted portion of an
13001 INTRODUCE1 cell, in addition to the current check for replays of
13002 the g^x value. This prevents a possible class of active attacks
13003 by an attacker who controls both an introduction point and a
13004 rendezvous point, and who uses the malleability of AES-CTR to
13005 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
13006 that these attacks are infeasible (requiring the attacker to send
13007 on the order of zettabytes of altered cells in a short interval),
13008 but we'd rather block them off in case there are any classes of
13009 this attack that we missed. Reported by Willem Pinckaers.
13011 o Minor features (also part of 0.2.2.33):
13012 - Adjust the expiration time on our SSL session certificates to
13013 better match SSL certs seen in the wild. Resolves ticket 4014.
13014 - Change the default required uptime for a relay to be accepted as
13015 a HSDir (hidden service directory) from 24 hours to 25 hours.
13016 Improves on 0.2.0.10-alpha; resolves ticket 2649.
13017 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
13018 authorities to abstain from voting on assignment of the HSDir
13019 consensus flag. Related to bug 2649.
13020 - Update to the September 6 2011 Maxmind GeoLite Country database.
13022 o Minor bugfixes (also part of 0.2.2.33):
13023 - Demote the 'replay detected' log message emitted when a hidden
13024 service receives the same Diffie-Hellman public key in two different
13025 INTRODUCE2 cells to info level. A normal Tor client can cause that
13026 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
13027 fixes part of bug 2442.
13028 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
13029 level. There is nothing that a hidden service's operator can do
13030 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
13032 - Clarify a log message specifying the characters permitted in
13033 HiddenServiceAuthorizeClient client names. Previously, the log
13034 message said that "[A-Za-z0-9+-_]" were permitted; that could have
13035 given the impression that every ASCII character between "+" and "_"
13036 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
13038 o Build fixes (also part of 0.2.2.33):
13039 - Clean up some code issues that prevented Tor from building on older
13040 BSDs. Fixes bug 3894; reported by "grarpamp".
13041 - Search for a platform-specific version of "ar" when cross-compiling.
13042 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
13045 - Fix a bug where the SocksPort option (for example) would get
13046 ignored and replaced by the default if a SocksListenAddress
13047 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
13051 - Relays now try regenerating and uploading their descriptor more
13052 frequently if they are not listed in the consensus, or if the
13053 version of their descriptor listed in the consensus is too
13054 old. This fix should prevent situations where a server declines
13055 to re-publish itself because it has done so too recently, even
13056 though the authorities decided not to list its recent-enough
13057 descriptor. Fix for bug 3327.
13060 - Relays now include a reason for regenerating their descriptors
13061 in an HTTP header when uploading to the authorities. This will
13062 make it easier to debug descriptor-upload issues in the future.
13063 - When starting as root and then changing our UID via the User
13064 control option, and we have a ControlSocket configured, make sure
13065 that the ControlSocket is owned by the same account that Tor will
13066 run under. Implements ticket 3421; fix by Jérémy Bobbio.
13069 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
13070 utility function used in the control-port code). This shouldn't
13071 ever happen unless Tor is completely out of memory, but if it did
13072 happen and Tor somehow recovered from it, Tor could have sent a log
13073 message to a control port in the middle of a reply to a controller
13074 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
13075 - Make 'FetchUselessDescriptors' cause all descriptor types and
13076 all consensus types (including microdescriptors) to get fetched.
13077 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
13079 o Code refactoring:
13080 - Make a new "entry connection" struct as an internal subtype of "edge
13081 connection", to simplify the code and make exit connections smaller.
13084 Changes in version 0.2.2.33 - 2011-09-13
13085 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
13086 TLS handshake that makes relays and bridges that run this new version
13087 reachable from Iran again.
13090 - Avoid an assertion failure when reloading a configuration with
13091 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
13092 3923; bugfix on 0.2.2.25-alpha.
13094 o Minor features (security):
13095 - Check for replays of the public-key encrypted portion of an
13096 INTRODUCE1 cell, in addition to the current check for replays of
13097 the g^x value. This prevents a possible class of active attacks
13098 by an attacker who controls both an introduction point and a
13099 rendezvous point, and who uses the malleability of AES-CTR to
13100 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
13101 that these attacks are infeasible (requiring the attacker to send
13102 on the order of zettabytes of altered cells in a short interval),
13103 but we'd rather block them off in case there are any classes of
13104 this attack that we missed. Reported by Willem Pinckaers.
13107 - Adjust the expiration time on our SSL session certificates to
13108 better match SSL certs seen in the wild. Resolves ticket 4014.
13109 - Change the default required uptime for a relay to be accepted as
13110 a HSDir (hidden service directory) from 24 hours to 25 hours.
13111 Improves on 0.2.0.10-alpha; resolves ticket 2649.
13112 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
13113 authorities to abstain from voting on assignment of the HSDir
13114 consensus flag. Related to bug 2649.
13115 - Update to the September 6 2011 Maxmind GeoLite Country database.
13117 o Minor bugfixes (documentation and log messages):
13118 - Correct the man page to explain that HashedControlPassword and
13119 CookieAuthentication can both be set, in which case either method
13120 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
13121 when we decided to allow these config options to both be set. Issue
13122 raised by bug 3898.
13123 - Demote the 'replay detected' log message emitted when a hidden
13124 service receives the same Diffie-Hellman public key in two different
13125 INTRODUCE2 cells to info level. A normal Tor client can cause that
13126 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
13127 fixes part of bug 2442.
13128 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
13129 level. There is nothing that a hidden service's operator can do
13130 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
13132 - Clarify a log message specifying the characters permitted in
13133 HiddenServiceAuthorizeClient client names. Previously, the log
13134 message said that "[A-Za-z0-9+-_]" were permitted; that could have
13135 given the impression that every ASCII character between "+" and "_"
13136 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
13139 - Provide a substitute implementation of lround() for MSVC, which
13140 apparently lacks it. Patch from Gisle Vanem.
13141 - Clean up some code issues that prevented Tor from building on older
13142 BSDs. Fixes bug 3894; reported by "grarpamp".
13143 - Search for a platform-specific version of "ar" when cross-compiling.
13144 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
13147 Changes in version 0.2.3.3-alpha - 2011-09-01
13148 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
13149 security, and provides client-side support for the microdescriptor
13150 and optimistic data features introduced earlier in the 0.2.3.x
13151 series. It also includes numerous critical bugfixes in the (optional)
13152 bufferevent-based networking backend.
13154 o Major features (stream isolation):
13155 - You can now configure Tor so that streams from different
13156 applications are isolated on different circuits, to prevent an
13157 attacker who sees your streams as they leave an exit node from
13158 linking your sessions to one another. To do this, choose some way
13159 to distinguish the applications: have them connect to different
13160 SocksPorts, or have one of them use SOCKS4 while the other uses
13161 SOCKS5, or have them pass different authentication strings to the
13162 SOCKS proxy. Then, use the new SocksPort syntax to configure the
13163 degree of isolation you need. This implements Proposal 171.
13164 - There's a new syntax for specifying multiple client ports (such as
13165 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
13166 multiple *Port entries with full addr:port syntax on each.
13167 The old *ListenAddress format is still supported, but you can't
13168 mix it with the new *Port syntax.
13170 o Major features (other):
13171 - Enable microdescriptor fetching by default for clients. This allows
13172 clients to download a much smaller amount of directory information.
13173 To disable it (and go back to the old-style consensus and
13174 descriptors), set "UseMicrodescriptors 0" in your torrc file.
13175 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
13176 "PortForwarding" config option), now supports Windows.
13177 - When using an exit relay running 0.2.3.x, clients can now
13178 "optimistically" send data before the exit relay reports that
13179 the stream has opened. This saves a round trip when starting
13180 connections where the client speaks first (such as web browsing).
13181 This behavior is controlled by a consensus parameter (currently
13182 disabled). To turn it on or off manually, use the "OptimisticData"
13183 torrc option. Implements proposal 181; code by Ian Goldberg.
13185 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
13186 - When using IOCP on Windows, we need to enable Libevent windows
13188 - The IOCP backend now works even when the user has not specified
13189 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
13190 Fixes part of bug 3752.
13191 - Correctly record the bytes we've read and written when using
13192 bufferevents, so that we can include them in our bandwidth history
13193 and advertised bandwidth. Fixes bug 3803.
13194 - Apply rate-limiting only at the bottom of a chain of filtering
13195 bufferevents. This prevents us from filling up internal read
13196 buffers and violating rate-limits when filtering bufferevents
13197 are enabled. Fixes part of bug 3804.
13198 - Add high-watermarks to the output buffers for filtered
13199 bufferevents. This prevents us from filling up internal write
13200 buffers and wasting CPU cycles when filtering bufferevents are
13201 enabled. Fixes part of bug 3804.
13202 - Correctly notice when data has been written from a bufferevent
13203 without flushing it completely. Fixes bug 3805.
13204 - Fix a bug where server-side tunneled bufferevent-based directory
13205 streams would get closed prematurely. Fixes bug 3814.
13206 - Fix a use-after-free error with per-connection rate-limiting
13207 buckets. Fixes bug 3888.
13209 o Major bugfixes (also part of 0.2.2.31-rc):
13210 - If we're configured to write our ControlPorts to disk, only write
13211 them after switching UID and creating the data directory. This way,
13212 we don't fail when starting up with a nonexistent DataDirectory
13213 and a ControlPortWriteToFile setting based on that directory. Fixes
13214 bug 3747; bugfix on Tor 0.2.2.26-beta.
13217 - Added a new CONF_CHANGED event so that controllers can be notified
13218 of any configuration changes made by other controllers, or by the
13219 user. Implements ticket 1692.
13220 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
13221 leak when using bufferevents, and lets Libevent worry about how to
13222 best copy data out of a buffer.
13223 - Replace files in stats/ rather than appending to them. Now that we
13224 include statistics in extra-info descriptors, it makes no sense to
13225 keep old statistics forever. Implements ticket 2930.
13227 o Minor features (build compatibility):
13228 - Limited, experimental support for building with nmake and MSVC.
13229 - Provide a substitute implementation of lround() for MSVC, which
13230 apparently lacks it. Patch from Gisle Vanem.
13232 o Minor features (also part of 0.2.2.31-rc):
13233 - Update to the August 2 2011 Maxmind GeoLite Country database.
13235 o Minor bugfixes (on 0.2.3.x-alpha):
13236 - Fix a spurious warning when parsing SOCKS requests with
13237 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
13238 - Get rid of a harmless warning that could happen on relays running
13239 with bufferevents. The warning was caused by someone doing an http
13240 request to a relay's orport. Also don't warn for a few related
13241 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
13243 o Minor bugfixes (on 2.2.x and earlier):
13244 - Correct the man page to explain that HashedControlPassword and
13245 CookieAuthentication can both be set, in which case either method
13246 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
13247 when we decided to allow these config options to both be set. Issue
13248 raised by bug 3898.
13249 - The "--quiet" and "--hush" options now apply not only to Tor's
13250 behavior before logs are configured, but also to Tor's behavior in
13251 the absense of configured logs. Fixes bug 3550; bugfix on
13254 o Minor bugfixes (also part of 0.2.2.31-rc):
13255 - Write several files in text mode, on OSes that distinguish text
13256 mode from binary mode (namely, Windows). These files are:
13257 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
13258 that collect those statistics; 'client_keys' and 'hostname' for
13259 hidden services that use authentication; and (in the tor-gencert
13260 utility) newly generated identity and signing keys. Previously,
13261 we wouldn't specify text mode or binary mode, leading to an
13262 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
13263 the DirRecordUsageByCountry option which would have triggered
13264 the assertion failure was added), although this assertion failure
13265 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
13266 - Selectively disable deprecation warnings on OS X because Lion
13267 started deprecating the shipped copy of openssl. Fixes bug 3643.
13268 - Remove an extra pair of quotation marks around the error
13269 message in control-port STATUS_GENERAL BUG events. Bugfix on
13270 0.1.2.6-alpha; fixes bug 3732.
13271 - When unable to format an address as a string, report its value
13272 as "???" rather than reusing the last formatted address. Bugfix
13275 o Code simplifications and refactoring:
13276 - Rewrite the listener-selection logic so that parsing which ports
13277 we want to listen on is now separate from binding to the ports
13281 - Building Tor with bufferevent support now requires Libevent
13282 2.0.13-stable or later. Previous versions of Libevent had bugs in
13283 SSL-related bufferevents and related issues that would make Tor
13284 work badly with bufferevents. Requiring 2.0.13-stable also allows
13285 Tor with bufferevents to take advantage of Libevent APIs
13286 introduced after 2.0.8-rc.
13289 Changes in version 0.2.2.32 - 2011-08-27
13290 The Tor 0.2.2 release series is dedicated to the memory of Andreas
13291 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
13292 a founder of the PETS community, a leader in our field, a mentor,
13293 and a friend. He left us with these words: "I had the possibility
13294 to contribute to this world that is not as it should be. I hope I
13295 could help in some areas to make the world a better place, and that
13296 I could also encourage other people to be engaged in improving the
13297 world. Please, stay engaged. This world needs you, your love, your
13298 initiative -- now I cannot be part of that anymore."
13300 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
13301 ready. More than two years in the making, this release features improved
13302 client performance and hidden service reliability, better compatibility
13303 for Android, correct behavior for bridges that listen on more than
13304 one address, more extensible and flexible directory object handling,
13305 better reporting of network statistics, improved code security, and
13306 many many other features and bugfixes.
13309 Changes in version 0.2.2.31-rc - 2011-08-17
13310 Tor 0.2.2.31-rc is the second and hopefully final release candidate
13311 for the Tor 0.2.2.x series.
13314 - Remove an extra pair of quotation marks around the error
13315 message in control-port STATUS_GENERAL BUG events. Bugfix on
13316 0.1.2.6-alpha; fixes bug 3732.
13317 - If we're configured to write our ControlPorts to disk, only write
13318 them after switching UID and creating the data directory. This way,
13319 we don't fail when starting up with a nonexistent DataDirectory
13320 and a ControlPortWriteToFile setting based on that directory. Fixes
13321 bug 3747; bugfix on Tor 0.2.2.26-beta.
13324 - Update to the August 2 2011 Maxmind GeoLite Country database.
13327 - Allow GETINFO fingerprint to return a fingerprint even when
13328 we have not yet built a router descriptor. Fixes bug 3577;
13329 bugfix on 0.2.0.1-alpha.
13330 - Write several files in text mode, on OSes that distinguish text
13331 mode from binary mode (namely, Windows). These files are:
13332 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
13333 that collect those statistics; 'client_keys' and 'hostname' for
13334 hidden services that use authentication; and (in the tor-gencert
13335 utility) newly generated identity and signing keys. Previously,
13336 we wouldn't specify text mode or binary mode, leading to an
13337 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
13338 the DirRecordUsageByCountry option which would have triggered
13339 the assertion failure was added), although this assertion failure
13340 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
13341 - Selectively disable deprecation warnings on OS X because Lion
13342 started deprecating the shipped copy of openssl. Fixes bug 3643.
13343 - When unable to format an address as a string, report its value
13344 as "???" rather than reusing the last formatted address. Bugfix
13348 Changes in version 0.2.3.2-alpha - 2011-07-18
13349 Tor 0.2.3.2-alpha introduces two new experimental features:
13350 microdescriptors and pluggable transports. It also continues cleaning
13351 up a variety of recently introduced features.
13354 - Clients can now use microdescriptors instead of regular descriptors
13355 to build circuits. Microdescriptors are authority-generated
13356 summaries of regular descriptors' contents, designed to change
13357 very rarely (see proposal 158 for details). This feature is
13358 designed to save bandwidth, especially for clients on slow internet
13359 connections. It's off by default for now, since nearly no caches
13360 support it, but it will be on-by-default for clients in a future
13361 version. You can use the UseMicrodescriptors option to turn it on.
13362 - Tor clients using bridges can now be configured to use a separate
13363 'transport' proxy for each bridge. This approach helps to resist
13364 censorship by allowing bridges to use protocol obfuscation
13365 plugins. It implements part of proposal 180. Implements ticket 2841.
13366 - While we're trying to bootstrap, record how many TLS connections
13367 fail in each state, and report which states saw the most failures
13368 in response to any bootstrap failures. This feature may speed up
13369 diagnosis of censorship events. Implements ticket 3116.
13371 o Major bugfixes (on 0.2.3.1-alpha):
13372 - When configuring a large set of nodes in EntryNodes (as with
13373 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
13374 random subset to be guards, and choose them in random
13375 order. Fixes bug 2798.
13376 - Tor could crash when remembering a consensus in a non-used consensus
13377 flavor without having a current consensus set. Fixes bug 3361.
13378 - Comparing an unknown address to a microdescriptor's shortened exit
13379 policy would always give a "rejected" result. Fixes bug 3599.
13380 - Using microdescriptors as a client no longer prevents Tor from
13381 uploading and downloading hidden service descriptors. Fixes
13385 - Allow nameservers with IPv6 address. Resolves bug 2574.
13386 - Accept attempts to include a password authenticator in the
13387 handshake, as supported by SOCKS5. This handles SOCKS clients that
13388 don't know how to omit a password when authenticating. Resolves
13390 - When configuring a large set of nodes in EntryNodes, and there are
13391 enough of them listed as Guard so that we don't need to consider
13392 the non-guard entries, prefer the ones listed with the Guard flag.
13393 - Check for and recover from inconsistency in the microdescriptor
13394 cache. This will make it harder for us to accidentally free a
13395 microdescriptor without removing it from the appropriate data
13396 structures. Fixes issue 3135; issue noted by "wanoskarnet".
13397 - Log SSL state transitions at log level DEBUG, log domain
13398 HANDSHAKE. This can be useful for debugging censorship events.
13399 Implements ticket 3264.
13400 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
13401 implements ticket 3439.
13403 o Minor bugfixes (on 0.2.3.1-alpha):
13404 - Do not free all general-purpose regular descriptors just
13405 because microdescriptor use is enabled. Fixes bug 3113.
13406 - Correctly link libevent_openssl when --enable-static-libevent
13407 is passed to configure. Fixes bug 3118.
13408 - Bridges should not complain during their heartbeat log messages that
13409 they are unlisted in the consensus: that's more or less the point
13410 of being a bridge. Fixes bug 3183.
13411 - Report a SIGNAL event to controllers when acting on a delayed
13412 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
13413 event to the controller if we acted on a SIGNAL NEWNYM command
13414 immediately, and otherwise not report a SIGNAL event for the
13415 command at all. Fixes bug 3349.
13416 - Fix a crash when handling the SIGNAL controller command or
13417 reporting ERR-level status events with bufferevents enabled. Found
13418 by Robert Ransom. Fixes bug 3367.
13419 - Always ship the tor-fw-helper manpage in our release tarballs.
13420 Fixes bug 3389. Reported by Stephen Walker.
13421 - Fix a class of double-mark-for-close bugs when bufferevents
13422 are enabled. Fixes bug 3403.
13423 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
13424 - Add SIGNAL to the list returned by the 'GETINFO events/names'
13425 control-port command. Fixes part of bug 3465.
13426 - Prevent using negative indices during unit test runs when read_all()
13427 fails. Spotted by coverity.
13428 - Fix a rare memory leak when checking the nodelist without it being
13429 present. Found by coverity.
13430 - Only try to download a microdescriptor-flavored consensus from
13431 a directory cache that provides them.
13433 o Minor bugfixes (on 0.2.2.x and earlier):
13434 - Assert that hidden-service-related operations are not performed
13435 using single-hop circuits. Previously, Tor would assert that
13436 client-side streams are not attached to single-hop circuits,
13437 but not that other sensitive operations on the client and service
13438 side are not performed using single-hop circuits. Fixes bug 3332;
13440 - Don't publish a new relay descriptor when we reload our onion key,
13441 unless the onion key has actually changed. Fixes bug 3263 and
13442 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
13443 - Allow GETINFO fingerprint to return a fingerprint even when
13444 we have not yet built a router descriptor. Fixes bug 3577;
13445 bugfix on 0.2.0.1-alpha.
13446 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
13447 on 0.2.2.4-alpha; fixes bug 3427.
13449 o Code simplification and refactoring:
13450 - Use tor_sscanf() in place of scanf() in more places through the
13451 code. This makes us a little more locale-independent, and
13452 should help shut up code-analysis tools that can't tell
13453 a safe sscanf string from a dangerous one.
13454 - Use tt_assert(), not tor_assert(), for checking for test failures.
13455 This makes the unit tests more able to go on in the event that
13457 - Split connection_about_to_close() into separate functions for each
13461 - On Windows, we now define the _WIN32_WINNT macros only if they
13462 are not already defined. This lets the person building Tor decide,
13463 if they want, to require a later version of Windows.
13466 Changes in version 0.2.2.30-rc - 2011-07-07
13467 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
13468 series. It fixes a few smaller bugs, but generally appears stable.
13469 Please test it and let us know whether it is!
13472 - Send a SUCCEEDED stream event to the controller when a reverse
13473 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
13474 discovered by katmagic.
13475 - Always NUL-terminate the sun_path field of a sockaddr_un before
13476 passing it to the kernel. (Not a security issue: kernels are
13477 smart enough to reject bad sockaddr_uns.) Found by Coverity;
13478 CID #428. Bugfix on Tor 0.2.0.3-alpha.
13479 - Don't stack-allocate the list of supplementary GIDs when we're
13480 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
13481 could take up to 256K, which is way too much stack. Found by
13482 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
13483 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
13484 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
13485 fixes part of bug 3465.
13486 - Fix a memory leak when receiving a descriptor for a hidden
13487 service we didn't ask for. Found by Coverity; CID #30. Bugfix
13491 - Update to the July 1 2011 Maxmind GeoLite Country database.
13494 Changes in version 0.2.2.29-beta - 2011-06-20
13495 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
13496 have bridge lines in their torrc but don't want to use them; gets
13497 us closer to having the control socket feature working on Debian;
13498 and fixes a variety of smaller bugs.
13501 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
13502 When we changed the default behavior to "use bridges if any
13503 are listed in the torrc", we surprised users who had bridges
13504 in their torrc files but who didn't actually want to use them.
13505 Partial resolution for bug 3354.
13508 - Don't attach new streams to old rendezvous circuits after SIGNAL
13509 NEWNYM. Previously, we would keep using an existing rendezvous
13510 circuit if it remained open (i.e. if it were kept open by a
13511 long-lived stream, or if a new stream were attached to it before
13512 Tor could notice that it was old and no longer in use). Bugfix on
13513 0.1.1.15-rc; fixes bug 3375.
13516 - Fix a bug when using ControlSocketsGroupWritable with User. The
13517 directory's group would be checked against the current group, not
13518 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
13519 bugfix on 0.2.2.26-beta.
13520 - Make connection_printf_to_buf()'s behavior sane. Its callers
13521 expect it to emit a CRLF iff the format string ends with CRLF;
13522 it actually emitted a CRLF iff (a) the format string ended with
13523 CRLF or (b) the resulting string was over 1023 characters long or
13524 (c) the format string did not end with CRLF *and* the resulting
13525 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
13526 fixes part of bug 3407.
13527 - Make send_control_event_impl()'s behavior sane. Its callers
13528 expect it to always emit a CRLF at the end of the string; it
13529 might have emitted extra control characters as well. Bugfix on
13530 0.1.1.9-alpha; fixes another part of bug 3407.
13531 - Make crypto_rand_int() check the value of its input correctly.
13532 Previously, it accepted values up to UINT_MAX, but could return a
13533 negative number if given a value above INT_MAX+1. Found by George
13534 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
13535 - Avoid a segfault when reading a malformed circuit build state
13536 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
13538 - When asked about a DNS record type we don't support via a
13539 client DNSPort, reply with NOTIMPL rather than an empty
13540 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
13541 - Fix a rare memory leak during stats writing. Found by coverity.
13544 - Update to the June 1 2011 Maxmind GeoLite Country database.
13546 o Code simplifications and refactoring:
13547 - Remove some dead code as indicated by coverity.
13548 - Remove a few dead assignments during router parsing. Found by
13550 - Add some forgotten return value checks during unit tests. Found
13552 - Don't use 1-bit wide signed bit fields. Found by coverity.
13555 Changes in version 0.2.2.28-beta - 2011-06-04
13556 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
13557 fixed a big bug in whether relays stay in the consensus consistently,
13558 we moved closer to handling bridges and hidden services correctly,
13559 and we started the process of better handling the dreaded "my Vidalia
13560 died, and now my Tor demands a password when I try to reconnect to it"
13564 - Don't decide to make a new descriptor when receiving a HUP signal.
13565 This bug has caused a lot of 0.2.2.x relays to disappear from the
13566 consensus periodically. Fixes the most common case of triggering
13567 bug 1810; bugfix on 0.2.2.7-alpha.
13568 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
13569 - Don't try to build descriptors if "ORPort auto" is set and we
13570 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
13572 - Resolve a crash that occurred when setting BridgeRelay to 1 with
13573 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
13574 - Apply circuit timeouts to opened hidden-service-related circuits
13575 based on the correct start time. Previously, we would apply the
13576 circuit build timeout based on time since the circuit's creation;
13577 it was supposed to be applied based on time since the circuit
13578 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
13579 - Use the same circuit timeout for client-side introduction
13580 circuits as for other four-hop circuits, rather than the timeout
13581 for single-hop directory-fetch circuits; the shorter timeout may
13582 have been appropriate with the static circuit build timeout in
13583 0.2.1.x and earlier, but caused many hidden service access attempts
13584 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
13585 on 0.2.2.2-alpha; fixes another part of bug 1297.
13586 - In ticket 2511 we fixed a case where you could use an unconfigured
13587 bridge if you had configured it as a bridge the last time you ran
13588 Tor. Now fix another edge case: if you had configured it as a bridge
13589 but then switched to a different bridge via the controller, you
13590 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
13594 - Add an __OwningControllerProcess configuration option and a
13595 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
13596 that when it exits, Tor will shut down. Implements feature 3049.
13597 - If "UseBridges 1" is set and no bridges are configured, Tor will
13598 now refuse to build any circuits until some bridges are set.
13599 If "UseBridges auto" is set, Tor will use bridges if they are
13600 configured and we are not running as a server, but otherwise will
13601 make circuits as usual. The new default is "auto". Patch by anonym,
13602 so the Tails LiveCD can stop automatically revealing you as a Tor
13606 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
13607 - Remove a trailing asterisk from "exit-policy/default" in the
13608 output of the control port command "GETINFO info/names". Bugfix
13610 - Use a wide type to hold sockets when built for 64-bit Windows builds.
13612 - Warn when the user configures two HiddenServiceDir lines that point
13613 to the same directory. Bugfix on 0.0.6 (the version introducing
13614 HiddenServiceDir); fixes bug 3289.
13615 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
13616 part of bug 2748; bugfix on 0.2.0.10-alpha.
13617 - Log malformed requests for rendezvous descriptors as protocol
13618 warnings, not warnings. Also, use a more informative log message
13619 in case someone sees it at log level warning without prior
13620 info-level messages. Fixes the other part of bug 2748; bugfix
13622 - Clear the table recording the time of the last request for each
13623 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
13624 Previously, we would clear our HS descriptor cache on SIGNAL
13625 NEWNYM, but if we had previously retrieved a descriptor (or tried
13626 to) from every directory responsible for it, we would refuse to
13627 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
13629 - Fix a log message that said "bits" while displaying a value in
13630 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
13632 - When checking for 1024-bit keys, check for 1024 bits, not 128
13633 bytes. This allows Tor to correctly discard keys of length 1017
13634 through 1023. Bugfix on 0.0.9pre5.
13637 - Relays now log the reason for publishing a new relay descriptor,
13638 so we have a better chance of hunting down instances of bug 1810.
13639 Resolves ticket 3252.
13640 - Revise most log messages that refer to nodes by nickname to
13641 instead use the "$key=nickname at address" format. This should be
13642 more useful, especially since nicknames are less and less likely
13643 to be unique. Resolves ticket 3045.
13644 - Log (at info level) when purging pieces of hidden-service-client
13645 state because of SIGNAL NEWNYM.
13648 - Remove undocumented option "-F" from tor-resolve: it hasn't done
13649 anything since 0.2.1.16-rc.
13652 Changes in version 0.2.2.27-beta - 2011-05-18
13653 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
13654 release, and also adds a few more general bugfixes.
13657 - Fix a crash bug when changing bridges in a running Tor process.
13658 Fixes bug 3213; bugfix on 0.2.2.26-beta.
13659 - When the controller configures a new bridge, don't wait 10 to 60
13660 seconds before trying to fetch its descriptor. Bugfix on
13661 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
13664 - Require that onion keys have exponent 65537 in microdescriptors too.
13665 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
13666 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
13667 Changed the limit to 512 characters by removing base64 newlines.
13668 Fixes bug 2752. Fix by Michael Yakubovich.
13669 - When a client starts or stops using bridges, never use a circuit
13670 that was built before the configuration change. This behavior could
13671 put at risk a user who uses bridges to ensure that her traffic
13672 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
13676 Changes in version 0.2.2.26-beta - 2011-05-17
13677 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
13678 also introduces a new "socksport auto" approach that should make it
13679 easier to run multiple Tors on the same system, and does a lot of
13680 cleanup to get us closer to a release candidate.
13682 o Security/privacy fixes:
13683 - Replace all potentially sensitive memory comparison operations
13684 with versions whose runtime does not depend on the data being
13685 compared. This will help resist a class of attacks where an
13686 adversary can use variations in timing information to learn
13687 sensitive data. Fix for one case of bug 3122. (Safe memcmp
13688 implementation by Robert Ransom based partially on code by DJB.)
13689 - When receiving a hidden service descriptor, check that it is for
13690 the hidden service we wanted. Previously, Tor would store any
13691 hidden service descriptors that a directory gave it, whether it
13692 wanted them or not. This wouldn't have let an attacker impersonate
13693 a hidden service, but it did let directories pre-seed a client
13694 with descriptors that it didn't want. Bugfix on 0.0.6.
13695 - On SIGHUP, do not clear out all TrackHostExits mappings, client
13696 DNS cache entries, and virtual address mappings: that's what
13697 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
13700 - The options SocksPort, ControlPort, and so on now all accept a
13701 value "auto" that opens a socket on an OS-selected port. A
13702 new ControlPortWriteToFile option tells Tor to write its
13703 actual control port or ports to a chosen file. If the option
13704 ControlPortFileGroupReadable is set, the file is created as
13705 group-readable. Now users can run two Tor clients on the same
13706 system without needing to manually mess with parameters. Resolves
13707 part of ticket 3076.
13708 - Set SO_REUSEADDR on all sockets, not just listeners. This should
13709 help busy exit nodes avoid running out of useable ports just
13710 because all the ports have been used in the near past. Resolves
13714 - New "GETINFO net/listeners/(type)" controller command to return
13715 a list of addresses and ports that are bound for listeners for a
13716 given connection type. This is useful when the user has configured
13717 "SocksPort auto" and the controller needs to know which port got
13718 chosen. Resolves another part of ticket 3076.
13719 - Add a new ControlSocketsGroupWritable configuration option: when
13720 it is turned on, ControlSockets are group-writeable by the default
13721 group of the current user. Patch by Jérémy Bobbio; implements
13723 - Tor now refuses to create a ControlSocket in a directory that is
13724 world-readable (or group-readable if ControlSocketsGroupWritable
13725 is 0). This is necessary because some operating systems do not
13726 enforce permissions on an AF_UNIX sockets. Permissions on the
13727 directory holding the socket, however, seems to work everywhere.
13728 - Rate-limit a warning about failures to download v2 networkstatus
13729 documents. Resolves part of bug 1352.
13730 - Backport code from 0.2.3.x that allows directory authorities to
13731 clean their microdescriptor caches. Needed to resolve bug 2230.
13732 - When an HTTPS proxy reports "403 Forbidden", we now explain
13733 what it means rather than calling it an unexpected status code.
13734 Closes bug 2503. Patch from Michael Yakubovich.
13735 - Update to the May 1 2011 Maxmind GeoLite Country database.
13738 - Authorities now clean their microdesc cache periodically and when
13739 reading from disk initially, not only when adding new descriptors.
13740 This prevents a bug where we could lose microdescriptors. Bugfix
13741 on 0.2.2.6-alpha. Fixes bug 2230.
13742 - Do not crash when our configuration file becomes unreadable, for
13743 example due to a permissions change, between when we start up
13744 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
13746 - Avoid a bug that would keep us from replacing a microdescriptor
13747 cache on Windows. (We would try to replace the file while still
13748 holding it open. That's fine on Unix, but Windows doesn't let us
13749 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
13750 - Add missing explanations for the authority-related torrc options
13751 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
13752 man page. Resolves issue 2379.
13753 - As an authority, do not upload our own vote or signature set to
13754 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
13755 it would get flagged as a duplicate. Resolves bug 3026.
13756 - Accept hidden service descriptors if we think we might be a hidden
13757 service directory, regardless of what our consensus says. This
13758 helps robustness, since clients and hidden services can sometimes
13759 have a more up-to-date view of the network consensus than we do,
13760 and if they think that the directory authorities list us a HSDir,
13761 we might actually be one. Related to bug 2732; bugfix on
13763 - When a controller changes TrackHostExits, remove mappings for
13764 hosts that should no longer have their exits tracked. Bugfix on
13766 - When a controller changes VirtualAddrNetwork, remove any mappings
13767 for hosts that were automapped to the old network. Bugfix on
13769 - When a controller changes one of the AutomapHosts* options, remove
13770 any mappings for hosts that should no longer be automapped. Bugfix
13772 - Do not reset the bridge descriptor download status every time we
13773 re-parse our configuration or get a configuration change. Fixes
13774 bug 3019; bugfix on 0.2.0.3-alpha.
13776 o Minor bugfixes (code cleanup):
13777 - When loading the microdesc journal, remember its current size.
13778 In 0.2.2, this helps prevent the microdesc journal from growing
13779 without limit on authorities (who are the only ones to use it in
13780 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
13781 Fix posted by "cypherpunks."
13782 - The microdesc journal is supposed to get rebuilt only if it is
13783 at least _half_ the length of the store, not _twice_ the length
13784 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
13785 - Fix a potential null-pointer dereference while computing a
13786 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
13788 - Avoid a possible null-pointer dereference when rebuilding the mdesc
13789 cache without actually having any descriptors to cache. Bugfix on
13790 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
13791 - If we fail to compute the identity digest of a v3 legacy keypair,
13792 warn, and don't use a buffer-full of junk instead. Bugfix on
13793 0.2.1.1-alpha; fixes bug 3106.
13794 - Resolve an untriggerable issue in smartlist_string_num_isin(),
13795 where if the function had ever in the future been used to check
13796 for the presence of a too-large number, it would have given an
13797 incorrect result. (Fortunately, we only used it for 16-bit
13798 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
13799 - Require that introduction point keys and onion handshake keys
13800 have a public exponent of 65537. Starts to fix bug 3207; bugfix
13803 o Removed features:
13804 - Caches no longer download and serve v2 networkstatus documents
13805 unless FetchV2Networkstatus flag is set: these documents haven't
13806 haven't been used by clients or relays since 0.2.0.x. Resolves
13810 Changes in version 0.2.3.1-alpha - 2011-05-05
13811 Tor 0.2.3.1-alpha adds some new experimental features, including support
13812 for an improved network IO backend, IOCP networking on Windows,
13813 microdescriptor caching, "fast-start" support for streams, and automatic
13814 home router configuration. There are also numerous internal improvements
13815 to try to make the code easier for developers to work with.
13817 This is the first alpha release in a new series, so expect there to be
13818 bugs. Users who would rather test out a more stable branch should
13819 stay with 0.2.2.x for now.
13822 - Tor can now optionally build with the "bufferevents" buffered IO
13823 backend provided by Libevent 2. To use this feature, make sure you
13824 have the latest possible version of Libevent, and pass the
13825 --enable-bufferevents flag to configure when building Tor from
13826 source. This feature will make our networking code more flexible,
13827 let us stack layers on each other, and let us use more efficient
13828 zero-copy transports where available.
13829 - As an experimental feature, Tor can use IOCP for networking on Windows.
13830 Once this code is tuned and optimized, it promises much better
13831 performance than the select-based backend we've used in the past. To
13832 try this feature, you must build Tor with Libevent 2, configure Tor
13833 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
13834 your torrc. There are known bugs here: only try this if you can help
13835 debug it as it breaks.
13836 - The EntryNodes option can now include country codes like {de} or IP
13837 addresses or network masks. Previously we had disallowed these options
13838 because we didn't have an efficient way to keep the list up to
13839 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
13840 - Exit nodes now accept and queue data on not-yet-connected streams.
13841 Previously, the client wasn't allowed to send data until the stream was
13842 connected, which slowed down all connections. This change will enable
13843 clients to perform a "fast-start" on streams and send data without
13844 having to wait for a confirmation that the stream has opened. (Patch
13845 from Ian Goldberg; implements the server side of Proposal 174.)
13846 - Tor now has initial support for automatic port mapping on the many
13847 home routers that support NAT-PMP or UPnP. (Not yet supported on
13848 Windows). To build the support code, you'll need to have libnatpnp
13849 library and/or the libminiupnpc library, and you'll need to enable the
13850 feature specifically by passing "--enable-upnp" and/or
13851 "--enable-natpnp" to configure. To turn it on, use the new
13852 PortForwarding option.
13853 - Caches now download, cache, and serve multiple "flavors" of the
13854 consensus, including a flavor that describes microdescriptors.
13855 - Caches now download, cache, and serve microdescriptors -- small
13856 summaries of router descriptors that are authenticated by all of the
13857 directory authorities. Once enough caches are running this code,
13858 clients will be able to save significant amounts of directory bandwidth
13859 by downloading microdescriptors instead of router descriptors.
13862 - Make logging resolution configurable with a new LogTimeGranularity
13863 option, and change the default from 1 millisecond to 1 second.
13864 Implements enhancement 1668.
13865 - We log which torrc file we're using on startup. Implements ticket
13867 - Ordinarily, Tor does not count traffic from private addresses (like
13868 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
13869 There is now a new option, CountPrivateBandwidth, to disable this
13870 behavior. Patch from Daniel Cagara.
13871 - New --enable-static-tor configure option for building Tor as
13872 statically as possible. Idea, general hackery and thoughts from
13873 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
13875 - If you set the NumCPUs option to 0, Tor will now try to detect how
13876 many CPUs you have. This is the new default behavior.
13877 - Turn on directory request statistics by default and include them in
13878 extra-info descriptors. Don't break if we have no GeoIP database.
13879 - Relays that set "ConnDirectionStatistics 1" write statistics on the
13880 bidirectional use of connections to disk every 24 hours.
13881 - Add a GeoIP file digest to the extra-info descriptor. Implements
13883 - The NodeFamily option -- which let you declare that you want to
13884 consider nodes to be part of a family whether they list themselves
13885 that way or not -- now allows IP address ranges and country codes.
13886 - Add a new 'Heartbeat' log message type to periodically log a message
13887 describing Tor's status at level Notice. This feature is meant for
13888 operators who log at notice, and want to make sure that their Tor
13889 server is still working. Implementation by George Kadianakis.
13891 o Minor bugfixes (on 0.2.2.25-alpha):
13892 - When loading the microdesc journal, remember its current size.
13893 In 0.2.2, this helps prevent the microdesc journal from growing
13894 without limit on authorities (who are the only ones to use it in
13895 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
13896 Fix posted by "cypherpunks."
13897 - The microdesc journal is supposed to get rebuilt only if it is
13898 at least _half_ the length of the store, not _twice_ the length
13899 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
13900 - If as an authority we fail to compute the identity digest of a v3
13901 legacy keypair, warn, and don't use a buffer-full of junk instead.
13902 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
13903 - Authorities now clean their microdesc cache periodically and when
13904 reading from disk initially, not only when adding new descriptors.
13905 This prevents a bug where we could lose microdescriptors. Bugfix
13908 o Minor features (controller):
13909 - Add a new SIGNAL event to the controller interface so that
13910 controllers can be notified when Tor handles a signal. Resolves
13911 issue 1955. Patch by John Brooks.
13912 - Add a new GETINFO option to get total bytes read and written. Patch
13913 from pipe, revised by atagar. Resolves ticket 2345.
13914 - Implement some GETINFO controller fields to provide information about
13915 the Tor process's pid, euid, username, and resource limits.
13918 - Our build system requires automake 1.6 or later to create the
13919 Makefile.in files. Previously, you could have used 1.4.
13920 This only affects developers and people building Tor from git;
13921 people who build Tor from the source distribution without changing
13922 the Makefile.am files should be fine.
13923 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
13924 so on. This is more robust against some of the failure modes
13925 associated with running the autotools pieces on their own.
13927 o Minor packaging issues:
13928 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
13929 already created. Patch from Andreas Stieger. Fixes bug 2573.
13931 o Code simplifications and refactoring:
13932 - A major revision to our internal node-selecting and listing logic.
13933 Tor already had at least two major ways to look at the question of
13934 "which Tor servers do we know about": a list of router descriptors,
13935 and a list of entries in the current consensus. With
13936 microdescriptors, we're adding a third. Having so many systems
13937 without an abstraction layer over them was hurting the codebase.
13938 Now, we have a new "node_t" abstraction that presents a consistent
13939 interface to a client's view of a Tor node, and holds (nearly) all
13940 of the mutable state formerly in routerinfo_t and routerstatus_t.
13941 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
13942 no longer link against Libevent: they never used it, but
13943 our library structure used to force them to link it.
13945 o Removed features:
13946 - Remove some old code to work around even older versions of Tor that
13947 used forked processes to handle DNS requests. Such versions of Tor
13948 are no longer in use as servers.
13950 o Documentation fixes:
13951 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
13952 - Add missing documentation for the authority-related torrc options
13953 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
13957 Changes in version 0.2.2.25-alpha - 2011-04-29
13958 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
13959 robust, routers no longer overreport their bandwidth, Win7 should crash
13960 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
13961 now prevents hidden service-related activity from being linkable. It
13962 provides more information to Vidalia so you can see if your bridge is
13963 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
13964 StrictNodes configuration options to make them more reliable, more
13965 understandable, and more regularly applied. If you use those options,
13966 please see the revised documentation for them in the manual page.
13969 - Relays were publishing grossly inflated bandwidth values because
13970 they were writing their state files wrong--now they write the
13971 correct value. Also, resume reading bandwidth history from the
13972 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
13973 - Improve hidden service robustness: When we find that we have
13974 extended a hidden service's introduction circuit to a relay not
13975 listed as an introduction point in the HS descriptor we currently
13976 have, retry with an introduction point from the current
13977 descriptor. Previously we would just give up. Fixes bugs 1024 and
13978 1930; bugfix on 0.2.0.10-alpha.
13979 - Clients now stop trying to use an exit node associated with a given
13980 destination by TrackHostExits if they fail to reach that exit node.
13981 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
13982 - Fix crash bug on platforms where gmtime and localtime can return
13983 NULL. Windows 7 users were running into this one. Fixes part of bug
13984 2077. Bugfix on all versions of Tor. Found by boboper.
13986 o Security and stability fixes:
13987 - Don't double-free a parsable, but invalid, microdescriptor, even if
13988 it is followed in the blob we're parsing by an unparsable
13989 microdescriptor. Fixes an issue reported in a comment on bug 2954.
13990 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
13991 - If the Nickname configuration option isn't given, Tor would pick a
13992 nickname based on the local hostname as the nickname for a relay.
13993 Because nicknames are not very important in today's Tor and the
13994 "Unnamed" nickname has been implemented, this is now problematic
13995 behavior: It leaks information about the hostname without being
13996 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
13997 introduced the Unnamed nickname. Reported by tagnaq.
13998 - Fix an uncommon assertion failure when running with DNSPort under
13999 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
14000 - Avoid linkability based on cached hidden service descriptors: forget
14001 all hidden service descriptors cached as a client when processing a
14002 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
14005 - Export GeoIP information on bridge usage to controllers even if we
14006 have not yet been running for 24 hours. Now Vidalia bridge operators
14007 can get more accurate and immediate feedback about their
14008 contributions to the network.
14010 o Major features and bugfixes (node selection):
14011 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
14012 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
14013 options. Previously, we had been ambiguous in describing what
14014 counted as an "exit" node, and what operations exactly "StrictNodes
14015 0" would permit. This created confusion when people saw nodes built
14016 through unexpected circuits, and made it hard to tell real bugs from
14017 surprises. Now the intended behavior is:
14018 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
14019 a node that delivers user traffic outside the Tor network.
14020 . "Entry", in the context of EntryNodes, means a node used as the
14021 first hop of a multihop circuit. It doesn't include direct
14022 connections to directory servers.
14023 . "ExcludeNodes" applies to all nodes.
14024 . "StrictNodes" changes the behavior of ExcludeNodes only. When
14025 StrictNodes is set, Tor should avoid all nodes listed in
14026 ExcludeNodes, even when it will make user requests fail. When
14027 StrictNodes is *not* set, then Tor should follow ExcludeNodes
14028 whenever it can, except when it must use an excluded node to
14029 perform self-tests, connect to a hidden service, provide a
14030 hidden service, fulfill a .exit request, upload directory
14031 information, or fetch directory information.
14032 Collectively, the changes to implement the behavior fix bug 1090.
14033 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
14034 a node is listed in both, it's treated as excluded.
14035 - ExcludeNodes now applies to directory nodes -- as a preference if
14036 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
14037 Don't exclude all the directory authorities and set StrictNodes to 1
14038 unless you really want your Tor to break.
14039 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
14040 - ExcludeExitNodes now overrides .exit requests.
14041 - We don't use bridges listed in ExcludeNodes.
14042 - When StrictNodes is 1:
14043 . We now apply ExcludeNodes to hidden service introduction points
14044 and to rendezvous points selected by hidden service users. This
14045 can make your hidden service less reliable: use it with caution!
14046 . If we have used ExcludeNodes on ourself, do not try relay
14047 reachability self-tests.
14048 . If we have excluded all the directory authorities, we will not
14049 even try to upload our descriptor if we're a relay.
14050 . Do not honor .exit requests to an excluded node.
14051 - Remove a misfeature that caused us to ignore the Fast/Stable flags
14052 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
14053 - When the set of permitted nodes changes, we now remove any mappings
14054 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
14056 - We never cannibalize a circuit that had excluded nodes on it, even
14057 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
14058 - Revert a change where we would be laxer about attaching streams to
14059 circuits than when building the circuits. This was meant to prevent
14060 a set of bugs where streams were never attachable, but our improved
14061 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
14062 - Keep track of how many times we launch a new circuit to handle a
14063 given stream. Too many launches could indicate an inconsistency
14064 between our "launch a circuit to handle this stream" logic and our
14065 "attach this stream to one of the available circuits" logic.
14066 - Improve log messages related to excluded nodes.
14069 - Fix a spurious warning when moving from a short month to a long
14070 month on relays with month-based BandwidthAccounting. Bugfix on
14071 0.2.2.17-alpha; fixes bug 3020.
14072 - When a client finds that an origin circuit has run out of 16-bit
14073 stream IDs, we now mark it as unusable for new streams. Previously,
14074 we would try to close the entire circuit. Bugfix on 0.0.6.
14075 - Add a forgotten cast that caused a compile warning on OS X 10.6.
14076 Bugfix on 0.2.2.24-alpha.
14077 - Be more careful about reporting the correct error from a failed
14078 connect() system call. Under some circumstances, it was possible to
14079 look at an incorrect value for errno when sending the end reason.
14080 Bugfix on 0.1.0.1-rc.
14081 - Correctly handle an "impossible" overflow cases in connection byte
14082 counting, where we write or read more than 4GB on an edge connection
14083 in a single second. Bugfix on 0.1.2.8-beta.
14084 - Correct the warning displayed when a rendezvous descriptor exceeds
14085 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
14087 - Clients and hidden services now use HSDir-flagged relays for hidden
14088 service descriptor downloads and uploads even if the relays have no
14089 DirPort set and the client has disabled TunnelDirConns. This will
14090 eventually allow us to give the HSDir flag to relays with no
14091 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
14092 - Downgrade "no current certificates known for authority" message from
14093 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
14094 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
14095 2917. Bugfix on 0.1.1.1-alpha.
14096 - Only limit the lengths of single HS descriptors, even when multiple
14097 HS descriptors are published to an HSDir relay in a single POST
14098 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
14099 - Write the current time into the LastWritten line in our state file,
14100 rather than the time from the previous write attempt. Also, stop
14101 trying to use a time of -1 in our log statements. Fixes bug 3039;
14102 bugfix on 0.2.2.14-alpha.
14103 - Be more consistent in our treatment of file system paths. "~" should
14104 get expanded to the user's home directory in the Log config option.
14105 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
14106 feature for the -f and --DataDirectory options.
14109 - Make sure every relay writes a state file at least every 12 hours.
14110 Previously, a relay could go for weeks without writing its state
14111 file, and on a crash could lose its bandwidth history, capacity
14112 estimates, client country statistics, and so on. Addresses bug 3012.
14113 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
14114 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
14115 clients are already deprecated because of security bugs.
14116 - Don't allow v0 hidden service authorities to act as clients.
14117 Required by fix for bug 3000.
14118 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
14119 by fix for bug 3000.
14120 - Ensure that no empty [dirreq-](read|write)-history lines are added
14121 to an extrainfo document. Implements ticket 2497.
14123 o Code simplification and refactoring:
14124 - Remove workaround code to handle directory responses from servers
14125 that had bug 539 (they would send HTTP status 503 responses _and_
14126 send a body too). Since only server versions before
14127 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
14128 keep the workaround in place.
14129 - Remove the old 'fuzzy time' logic. It was supposed to be used for
14130 handling calculations where we have a known amount of clock skew and
14131 an allowed amount of unknown skew. But we only used it in three
14132 places, and we never adjusted the known/unknown skew values. This is
14133 still something we might want to do someday, but if we do, we'll
14134 want to do it differently.
14135 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
14136 None of the cases where we did this before were wrong, but by making
14137 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
14138 - Use GetTempDir to find the proper temporary directory location on
14139 Windows when generating temporary files for the unit tests. Patch by
14143 Changes in version 0.2.2.24-alpha - 2011-04-08
14144 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
14145 prevented Tor clients from effectively using "multihomed" bridges,
14146 that is, bridges that listen on multiple ports or IP addresses so users
14147 can continue to use some of their addresses even if others get blocked.
14150 - Fix a bug where bridge users who configure the non-canonical
14151 address of a bridge automatically switch to its canonical
14152 address. If a bridge listens at more than one address, it should be
14153 able to advertise those addresses independently and any non-blocked
14154 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
14156 - If you configured Tor to use bridge A, and then quit and
14157 configured Tor to use bridge B instead, it would happily continue
14158 to use bridge A if it's still reachable. While this behavior is
14159 a feature if your goal is connectivity, in some scenarios it's a
14160 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
14161 - Directory authorities now use data collected from their own
14162 uptime observations when choosing whether to assign the HSDir flag
14163 to relays, instead of trusting the uptime value the relay reports in
14164 its descriptor. This change helps prevent an attack where a small
14165 set of nodes with frequently-changing identity keys can blackhole
14166 a hidden service. (Only authorities need upgrade; others will be
14167 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
14170 - When we restart our relay, we might get a successful connection
14171 from the outside before we've started our reachability tests,
14172 triggering a warning: "ORPort found reachable, but I have no
14173 routerinfo yet. Failing to inform controller of success." This
14174 bug was harmless unless Tor is running under a controller
14175 like Vidalia, in which case the controller would never get a
14176 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
14178 - Make directory authorities more accurate at recording when
14179 relays that have failed several reachability tests became
14180 unreachable, so we can provide more accuracy at assigning Stable,
14181 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
14182 - Fix an issue that prevented static linking of libevent on
14183 some platforms (notably Linux). Fixes bug 2698; bugfix on
14184 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
14185 the --with-static-libevent configure option).
14186 - We now ask the other side of a stream (the client or the exit)
14187 for more data on that stream when the amount of queued data on
14188 that stream dips low enough. Previously, we wouldn't ask the
14189 other side for more data until either it sent us more data (which
14190 it wasn't supposed to do if it had exhausted its window!) or we
14191 had completely flushed all our queued data. This flow control fix
14192 should improve throughput. Fixes bug 2756; bugfix on the earliest
14193 released versions of Tor (svn commit r152).
14194 - Avoid a double-mark-for-free warning when failing to attach a
14195 transparent proxy connection. (We thought we had fixed this in
14196 0.2.2.23-alpha, but it turns out our fix was checking the wrong
14197 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
14198 bug) and 0.2.2.23-alpha (the incorrect fix).
14199 - When warning about missing zlib development packages during compile,
14200 give the correct package names. Bugfix on 0.2.0.1-alpha.
14203 - Directory authorities now log the source of a rejected POSTed v3
14204 networkstatus vote.
14205 - Make compilation with clang possible when using
14206 --enable-gcc-warnings by removing two warning options that clang
14207 hasn't implemented yet and by fixing a few warnings. Implements
14209 - When expiring circuits, use microsecond timers rather than
14210 one-second timers. This can avoid an unpleasant situation where a
14211 circuit is launched near the end of one second and expired right
14212 near the beginning of the next, and prevent fluctuations in circuit
14214 - Use computed circuit-build timeouts to decide when to launch
14215 parallel introduction circuits for hidden services. (Previously,
14216 we would retry after 15 seconds.)
14217 - Update to the April 1 2011 Maxmind GeoLite Country database.
14220 - Create the /var/run/tor directory on startup on OpenSUSE if it is
14221 not already created. Patch from Andreas Stieger. Fixes bug 2573.
14223 o Documentation changes:
14224 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
14225 - Resolve all doxygen warnings except those for missing documentation.
14227 - Add doxygen documentation for more functions, fields, and types.
14230 Changes in version 0.2.2.23-alpha - 2011-03-08
14231 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
14232 they restart they don't lose their bandwidth capacity estimate. This
14233 release also fixes a diverse set of user-facing bugs, ranging from
14234 relays overrunning their rate limiting to clients falsely warning about
14235 clock skew to bridge descriptor leaks by our bridge directory authority.
14238 - Stop sending a CLOCK_SKEW controller status event whenever
14239 we fetch directory information from a relay that has a wrong clock.
14240 Instead, only inform the controller when it's a trusted authority
14241 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
14242 the rest of bug 1074.
14243 - Fix an assert in parsing router descriptors containing IPv6
14244 addresses. This one took down the directory authorities when
14245 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
14246 - Make the bridge directory authority refuse to answer directory
14247 requests for "all" descriptors. It used to include bridge
14248 descriptors in its answer, which was a major information leak.
14249 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
14250 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
14251 Tor would ignore their RelayBandwidthBurst setting,
14252 potentially using more bandwidth than expected. Bugfix on
14253 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
14254 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
14255 hidserv" in her torrc. The 'hidserv' argument never controlled
14256 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
14259 - Relays now save observed peak bandwidth throughput rates to their
14260 state file (along with total usage, which was already saved)
14261 so that they can determine their correct estimated bandwidth on
14262 restart. Resolves bug 1863, where Tor relays would reset their
14263 estimated bandwidth to 0 after restarting.
14264 - Directory authorities now take changes in router IP address and
14265 ORPort into account when determining router stability. Previously,
14266 if a router changed its IP or ORPort, the authorities would not
14267 treat it as having any downtime for the purposes of stability
14268 calculation, whereas clients would experience downtime since the
14269 change could take a while to propagate to them. Resolves issue 1035.
14270 - Enable Address Space Layout Randomization (ASLR) and Data Execution
14271 Prevention (DEP) by default on Windows to make it harder for
14272 attackers to exploit vulnerabilities. Patch from John Brooks.
14274 o Minor bugfixes (on 0.2.1.x and earlier):
14275 - Fix a rare crash bug that could occur when a client was configured
14276 with a large number of bridges. Fixes bug 2629; bugfix on
14277 0.2.1.2-alpha. Bugfix by trac user "shitlei".
14278 - Avoid a double mark-for-free warning when failing to attach a
14279 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
14281 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
14282 found by "cypherpunks". This bug was introduced before the first
14283 Tor release, in svn commit r110.
14284 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
14285 don't mention them in the manpage. Fixes bug 2450; issue
14286 spotted by keb and G-Lo.
14287 - Fix a bug in bandwidth history state parsing that could have been
14288 triggered if a future version of Tor ever changed the timing
14289 granularity at which bandwidth history is measured. Bugfix on
14290 Tor 0.1.1.11-alpha.
14291 - When a relay decides that its DNS is too broken for it to serve
14292 as an exit server, it advertised itself as a non-exit, but
14293 continued to act as an exit. This could create accidental
14294 partitioning opportunities for users. Instead, if a relay is
14295 going to advertise reject *:* as its exit policy, it should
14296 really act with exit policy "reject *:*". Fixes bug 2366.
14297 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
14298 - In the special case where you configure a public exit relay as your
14299 bridge, Tor would be willing to use that exit relay as the last
14300 hop in your circuit as well. Now we fail that circuit instead.
14301 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
14302 - Fix a bug with our locking implementation on Windows that couldn't
14303 correctly detect when a file was already locked. Fixes bug 2504,
14304 bugfix on 0.2.1.6-alpha.
14305 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
14306 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
14308 - Set target port in get_interface_address6() correctly. Bugfix
14309 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
14310 - Directory authorities are now more robust to hops back in time
14311 when calculating router stability. Previously, if a run of uptime
14312 or downtime appeared to be negative, the calculation could give
14313 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
14315 - Fix an assert that got triggered when using the TestingTorNetwork
14316 configuration option and then issuing a GETINFO config-text control
14317 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
14319 o Minor bugfixes (on 0.2.2.x):
14320 - Clients should not weight BadExit nodes as Exits in their node
14321 selection. Similarly, directory authorities should not count BadExit
14322 bandwidth as Exit bandwidth when computing bandwidth-weights.
14323 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
14324 - Correctly clear our dir_read/dir_write history when there is an
14325 error parsing any bw history value from the state file. Bugfix on
14326 Tor 0.2.2.15-alpha.
14327 - Resolve a bug in verifying signatures of directory objects
14328 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
14329 Fixes bug 2409. Found by "piebeer".
14330 - Bridge authorities no longer crash on SIGHUP when they try to
14331 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
14335 - Log less aggressively about circuit timeout changes, and improve
14336 some other circuit timeout messages. Resolves bug 2004.
14337 - Log a little more clearly about the times at which we're no longer
14338 accepting new connections. Resolves bug 2181.
14339 - Reject attempts at the client side to open connections to private
14340 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
14341 a randomly chosen exit node. Attempts to do so are always
14342 ill-defined, generally prevented by exit policies, and usually
14343 in error. This will also help to detect loops in transparent
14344 proxy configurations. You can disable this feature by setting
14345 "ClientRejectInternalAddresses 0" in your torrc.
14346 - Always treat failure to allocate an RSA key as an unrecoverable
14348 - Update to the March 1 2011 Maxmind GeoLite Country database.
14350 o Minor features (log subsystem):
14351 - Add documentation for configuring logging at different severities in
14352 different log domains. We've had this feature since 0.2.1.1-alpha,
14353 but for some reason it never made it into the manpage. Fixes
14355 - Make it simpler to specify "All log domains except for A and B".
14356 Previously you needed to say "[*,~A,~B]". Now you can just say
14358 - Add a "LogMessageDomains 1" option to include the domains of log
14359 messages along with the messages. Without this, there's no way
14360 to use log domains without reading the source or doing a lot
14363 o Packaging changes:
14364 - Stop shipping the Tor specs files and development proposal documents
14365 in the tarball. They are now in a separate git repository at
14366 git://git.torproject.org/torspec.git
14369 Changes in version 0.2.1.30 - 2011-02-23
14370 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
14371 change is a slight tweak to Tor's TLS handshake that makes relays
14372 and bridges that run this new version reachable from Iran again.
14373 We don't expect this tweak will win the arms race long-term, but it
14374 buys us time until we roll out a better solution.
14377 - Stop sending a CLOCK_SKEW controller status event whenever
14378 we fetch directory information from a relay that has a wrong clock.
14379 Instead, only inform the controller when it's a trusted authority
14380 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
14381 the rest of bug 1074.
14382 - Fix a bounds-checking error that could allow an attacker to
14383 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
14384 Found by "piebeer".
14385 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
14386 Tor would ignore their RelayBandwidthBurst setting,
14387 potentially using more bandwidth than expected. Bugfix on
14388 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
14389 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
14390 hidserv" in her torrc. The 'hidserv' argument never controlled
14391 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
14394 - Adjust our TLS Diffie-Hellman parameters to match those used by
14396 - Update to the February 1 2011 Maxmind GeoLite Country database.
14399 - Check for and reject overly long directory certificates and
14400 directory tokens before they have a chance to hit any assertions.
14401 Bugfix on 0.2.1.28. Found by "doorss".
14402 - Bring the logic that gathers routerinfos and assesses the
14403 acceptability of circuits into line. This prevents a Tor OP from
14404 getting locked in a cycle of choosing its local OR as an exit for a
14405 path (due to a .exit request) and then rejecting the circuit because
14406 its OR is not listed yet. It also prevents Tor clients from using an
14407 OR running in the same instance as an exit (due to a .exit request)
14408 if the OR does not meet the same requirements expected of an OR
14409 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
14411 o Packaging changes:
14412 - Stop shipping the Tor specs files and development proposal documents
14413 in the tarball. They are now in a separate git repository at
14414 git://git.torproject.org/torspec.git
14415 - Do not include Git version tags as though they are SVN tags when
14416 generating a tarball from inside a repository that has switched
14417 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
14420 Changes in version 0.2.2.22-alpha - 2011-01-25
14421 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
14422 main other change is a slight tweak to Tor's TLS handshake that makes
14423 relays and bridges that run this new version reachable from Iran again.
14424 We don't expect this tweak will win the arms race long-term, but it
14425 will buy us a bit more time until we roll out a better solution.
14428 - Fix a bounds-checking error that could allow an attacker to
14429 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
14430 Found by "piebeer".
14431 - Don't assert when changing from bridge to relay or vice versa
14432 via the controller. The assert happened because we didn't properly
14433 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
14434 bug 2433. Reported by bastik.
14437 - Adjust our TLS Diffie-Hellman parameters to match those used by
14439 - Provide a log message stating which geoip file we're parsing
14440 instead of just stating that we're parsing the geoip file.
14441 Implements ticket 2432.
14444 - Check for and reject overly long directory certificates and
14445 directory tokens before they have a chance to hit any assertions.
14446 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
14449 Changes in version 0.2.2.21-alpha - 2011-01-15
14450 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
14451 continues our recent code security audit work. The main fix resolves
14452 a remote heap overflow vulnerability that can allow remote code
14453 execution (CVE-2011-0427). Other fixes address a variety of assert
14454 and crash bugs, most of which we think are hard to exploit remotely.
14456 o Major bugfixes (security), also included in 0.2.1.29:
14457 - Fix a heap overflow bug where an adversary could cause heap
14458 corruption. This bug probably allows remote code execution
14459 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
14461 - Prevent a denial-of-service attack by disallowing any
14462 zlib-compressed data whose compression factor is implausibly
14463 high. Fixes part of bug 2324; reported by "doorss".
14464 - Zero out a few more keys in memory before freeing them. Fixes
14465 bug 2384 and part of bug 2385. These key instances found by
14466 "cypherpunks", based on Andrew Case's report about being able
14467 to find sensitive data in Tor's memory space if you have enough
14468 permissions. Bugfix on 0.0.2pre9.
14470 o Major bugfixes (crashes), also included in 0.2.1.29:
14471 - Prevent calls to Libevent from inside Libevent log handlers.
14472 This had potential to cause a nasty set of crashes, especially
14473 if running Libevent with debug logging enabled, and running
14474 Tor with a controller watching for low-severity log messages.
14475 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
14476 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
14477 underflow errors there too. Fixes the other part of bug 2324.
14478 - Fix a bug where we would assert if we ever had a
14479 cached-descriptors.new file (or another file read directly into
14480 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
14481 on 0.2.1.25. Found by doorss.
14482 - Fix some potential asserts and parsing issues with grossly
14483 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
14486 o Minor bugfixes (other), also included in 0.2.1.29:
14487 - Fix a bug with handling misformed replies to reverse DNS lookup
14488 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
14489 bug reported by doorss.
14490 - Fix compilation on mingw when a pthreads compatibility library
14491 has been installed. (We don't want to use it, so we shouldn't
14492 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
14493 - Fix a bug where we would declare that we had run out of virtual
14494 addresses when the address space was only half-exhausted. Bugfix
14496 - Correctly handle the case where AutomapHostsOnResolve is set but
14497 no virtual addresses are available. Fixes bug 2328; bugfix on
14498 0.1.2.1-alpha. Bug found by doorss.
14499 - Correctly handle wrapping around when we run out of virtual
14500 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
14502 o Minor features, also included in 0.2.1.29:
14503 - Update to the January 1 2011 Maxmind GeoLite Country database.
14504 - Introduce output size checks on all of our decryption functions.
14506 o Build changes, also included in 0.2.1.29:
14507 - Tor does not build packages correctly with Automake 1.6 and earlier;
14508 added a check to Makefile.am to make sure that we're building with
14509 Automake 1.7 or later.
14510 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
14511 because we built it with a too-old version of automake. Thus that
14512 release broke ./configure --enable-openbsd-malloc, which is popular
14513 among really fast exit relays on Linux.
14515 o Major bugfixes, new in 0.2.2.21-alpha:
14516 - Prevent crash/heap corruption when the cbtnummodes consensus
14517 parameter is set to 0 or large values. Fixes bug 2317; bugfix
14520 o Major features, new in 0.2.2.21-alpha:
14521 - Introduce minimum/maximum values that clients will believe
14522 from the consensus. Now we'll have a better chance to avoid crashes
14523 or worse when a consensus param has a weird value.
14525 o Minor features, new in 0.2.2.21-alpha:
14526 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
14527 used on bridges, and it makes bridge scanning somewhat easier.
14528 - If writing the state file to disk fails, wait up to an hour before
14529 retrying again, rather than trying again each second. Fixes bug
14530 2346; bugfix on Tor 0.1.1.3-alpha.
14531 - Make Libevent log messages get delivered to controllers later,
14532 and not from inside the Libevent log handler. This prevents unsafe
14533 reentrant Libevent calls while still letting the log messages
14535 - Detect platforms that brokenly use a signed size_t, and refuse to
14536 build there. Found and analyzed by doorss and rransom.
14537 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
14540 o Minor bugfixes, new in 0.2.2.21-alpha:
14541 - Handle SOCKS messages longer than 128 bytes long correctly, rather
14542 than waiting forever for them to finish. Fixes bug 2330; bugfix
14543 on 0.2.0.16-alpha. Found by doorss.
14544 - Add assertions to check for overflow in arguments to
14545 base32_encode() and base32_decode(); fix a signed-unsigned
14546 comparison there too. These bugs are not actually reachable in Tor,
14547 but it's good to prevent future errors too. Found by doorss.
14548 - Correctly detect failures to create DNS requests when using Libevent
14549 versions before v2. (Before Libevent 2, we used our own evdns
14550 implementation. Its return values for Libevent's evdns_resolve_*()
14551 functions are not consistent with those from Libevent.) Fixes bug
14552 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
14554 o Documentation, new in 0.2.2.21-alpha:
14555 - Document the default socks host and port (127.0.0.1:9050) for
14559 Changes in version 0.2.1.29 - 2011-01-15
14560 Tor 0.2.1.29 continues our recent code security audit work. The main
14561 fix resolves a remote heap overflow vulnerability that can allow remote
14562 code execution. Other fixes address a variety of assert and crash bugs,
14563 most of which we think are hard to exploit remotely.
14565 o Major bugfixes (security):
14566 - Fix a heap overflow bug where an adversary could cause heap
14567 corruption. This bug probably allows remote code execution
14568 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
14570 - Prevent a denial-of-service attack by disallowing any
14571 zlib-compressed data whose compression factor is implausibly
14572 high. Fixes part of bug 2324; reported by "doorss".
14573 - Zero out a few more keys in memory before freeing them. Fixes
14574 bug 2384 and part of bug 2385. These key instances found by
14575 "cypherpunks", based on Andrew Case's report about being able
14576 to find sensitive data in Tor's memory space if you have enough
14577 permissions. Bugfix on 0.0.2pre9.
14579 o Major bugfixes (crashes):
14580 - Prevent calls to Libevent from inside Libevent log handlers.
14581 This had potential to cause a nasty set of crashes, especially
14582 if running Libevent with debug logging enabled, and running
14583 Tor with a controller watching for low-severity log messages.
14584 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
14585 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
14586 underflow errors there too. Fixes the other part of bug 2324.
14587 - Fix a bug where we would assert if we ever had a
14588 cached-descriptors.new file (or another file read directly into
14589 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
14590 on 0.2.1.25. Found by doorss.
14591 - Fix some potential asserts and parsing issues with grossly
14592 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
14595 o Minor bugfixes (other):
14596 - Fix a bug with handling misformed replies to reverse DNS lookup
14597 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
14598 bug reported by doorss.
14599 - Fix compilation on mingw when a pthreads compatibility library
14600 has been installed. (We don't want to use it, so we shouldn't
14601 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
14602 - Fix a bug where we would declare that we had run out of virtual
14603 addresses when the address space was only half-exhausted. Bugfix
14605 - Correctly handle the case where AutomapHostsOnResolve is set but
14606 no virtual addresses are available. Fixes bug 2328; bugfix on
14607 0.1.2.1-alpha. Bug found by doorss.
14608 - Correctly handle wrapping around to when we run out of virtual
14609 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
14610 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
14611 because we built it with a too-old version of automake. Thus that
14612 release broke ./configure --enable-openbsd-malloc, which is popular
14613 among really fast exit relays on Linux.
14616 - Update to the January 1 2011 Maxmind GeoLite Country database.
14617 - Introduce output size checks on all of our decryption functions.
14620 - Tor does not build packages correctly with Automake 1.6 and earlier;
14621 added a check to Makefile.am to make sure that we're building with
14622 Automake 1.7 or later.
14625 Changes in version 0.2.2.20-alpha - 2010-12-17
14626 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
14627 exploitable bugs. We also fix a variety of other significant bugs,
14628 change the IP address for one of our directory authorities, and update
14629 the minimum version that Tor relays must run to join the network.
14632 - Fix a remotely exploitable bug that could be used to crash instances
14633 of Tor remotely by overflowing on the heap. Remote-code execution
14634 hasn't been confirmed, but can't be ruled out. Everyone should
14635 upgrade. Bugfix on the 0.1.1 series and later.
14636 - Fix a bug that could break accounting on 64-bit systems with large
14637 time_t values, making them hibernate for impossibly long intervals.
14638 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
14639 - Fix a logic error in directory_fetches_from_authorities() that
14640 would cause all _non_-exits refusing single-hop-like circuits
14641 to fetch from authorities, when we wanted to have _exits_ fetch
14642 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
14644 - Fix a stream fairness bug that would cause newer streams on a given
14645 circuit to get preference when reading bytes from the origin or
14646 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
14647 introduced before the first Tor release, in svn revision r152.
14649 o Directory authority changes:
14650 - Change IP address and ports for gabelmoo (v3 directory authority).
14653 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
14654 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
14655 - Fix an off-by-one error in calculating some controller command
14656 argument lengths. Fortunately, this mistake is harmless since
14657 the controller code does redundant NUL termination too. Found by
14658 boboper. Bugfix on 0.1.1.1-alpha.
14659 - Do not dereference NULL if a bridge fails to build its
14660 extra-info descriptor. Found by an anonymous commenter on
14661 Trac. Bugfix on 0.2.2.19-alpha.
14664 - Update to the December 1 2010 Maxmind GeoLite Country database.
14665 - Directory authorities now reject relays running any versions of
14666 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
14667 known bugs that keep RELAY_EARLY cells from working on rendezvous
14668 circuits. Followup to fix for bug 2081.
14669 - Directory authorities now reject relays running any version of Tor
14670 older than 0.2.0.26-rc. That version is the earliest that fetches
14671 current directory information correctly. Fixes bug 2156.
14672 - Report only the top 10 ports in exit-port stats in order not to
14673 exceed the maximum extra-info descriptor length of 50 KB. Implements
14677 Changes in version 0.2.1.28 - 2010-12-17
14678 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
14679 exploitable bugs. We also took this opportunity to change the IP address
14680 for one of our directory authorities, and to update the geoip database
14684 - Fix a remotely exploitable bug that could be used to crash instances
14685 of Tor remotely by overflowing on the heap. Remote-code execution
14686 hasn't been confirmed, but can't be ruled out. Everyone should
14687 upgrade. Bugfix on the 0.1.1 series and later.
14689 o Directory authority changes:
14690 - Change IP address and ports for gabelmoo (v3 directory authority).
14693 - Update to the December 1 2010 Maxmind GeoLite Country database.
14696 Changes in version 0.2.1.27 - 2010-11-23
14697 Yet another OpenSSL security patch broke its compatibility with Tor:
14698 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
14699 also took this opportunity to fix several crash bugs, integrate a new
14700 directory authority, and update the bundled GeoIP database.
14703 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
14704 No longer set the tlsext_host_name extension on server SSL objects;
14705 but continue to set it on client SSL objects. Our goal in setting
14706 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
14707 bugfix on 0.2.1.1-alpha.
14708 - Do not log messages to the controller while shrinking buffer
14709 freelists. Doing so would sometimes make the controller connection
14710 try to allocate a buffer chunk, which would mess up the internals
14711 of the freelist and cause an assertion failure. Fixes bug 1125;
14712 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
14713 - Learn our external IP address when we're a relay or bridge, even if
14714 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
14715 where we introduced bridge relays that don't need to publish to
14716 be useful. Fixes bug 2050.
14717 - Do even more to reject (and not just ignore) annotations on
14718 router descriptors received anywhere but from the cache. Previously
14719 we would ignore such annotations at first, but cache them to disk
14720 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
14721 - When you're using bridges and your network goes away and your
14722 bridges get marked as down, recover when you attempt a new socks
14723 connection (if the network is back), rather than waiting up to an
14724 hour to try fetching new descriptors for your bridges. Bugfix on
14725 0.2.0.3-alpha; fixes bug 1981.
14728 - Move to the November 2010 Maxmind GeoLite country db (rather
14729 than the June 2009 ip-to-country GeoIP db) for our statistics that
14730 count how many users relays are seeing from each country. Now we'll
14731 have more accurate data, especially for many African countries.
14733 o New directory authorities:
14734 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
14738 - Fix an assertion failure that could occur in directory caches or
14739 bridge users when using a very short voting interval on a testing
14740 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
14742 - Enforce multiplicity rules when parsing annotations. Bugfix on
14743 0.2.0.8-alpha. Found by piebeer.
14744 - Allow handshaking OR connections to take a full KeepalivePeriod
14745 seconds to handshake. Previously, we would close them after
14746 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
14747 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
14749 - When building with --enable-gcc-warnings on OpenBSD, disable
14750 warnings in system headers. This makes --enable-gcc-warnings
14751 pass on OpenBSD 4.8.
14754 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
14755 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
14756 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
14757 Servers can start sending this code when enough clients recognize
14758 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
14759 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
14760 Patch from mingw-san.
14763 - Remove the old debian/ directory from the main Tor distribution.
14764 The official Tor-for-debian git repository lives at the URL
14765 https://git.torproject.org/debian/tor.git
14766 - Stop shipping the old doc/website/ directory in the tarball. We
14767 changed the website format in late 2010, and what we shipped in
14768 0.2.1.26 really wasn't that useful anyway.
14771 Changes in version 0.2.2.19-alpha - 2010-11-22
14772 Yet another OpenSSL security patch broke its compatibility with Tor:
14773 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
14776 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
14777 No longer set the tlsext_host_name extension on server SSL objects;
14778 but continue to set it on client SSL objects. Our goal in setting
14779 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
14780 bugfix on 0.2.1.1-alpha.
14783 - Try harder not to exceed the maximum length of 50 KB when writing
14784 statistics to extra-info descriptors. This bug was triggered by very
14785 fast relays reporting exit-port, entry, and dirreq statistics.
14786 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
14787 - Publish a router descriptor even if generating an extra-info
14788 descriptor fails. Previously we would not publish a router
14789 descriptor without an extra-info descriptor; this can cause fast
14790 exit relays collecting exit-port statistics to drop from the
14791 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
14794 Changes in version 0.2.2.18-alpha - 2010-11-16
14795 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
14796 us lately, makes unpublished bridge relays able to detect their IP
14797 address, and fixes a wide variety of other bugs to get us much closer
14798 to a stable release.
14801 - Do even more to reject (and not just ignore) annotations on
14802 router descriptors received anywhere but from the cache. Previously
14803 we would ignore such annotations at first, but cache them to disk
14804 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
14805 - Do not log messages to the controller while shrinking buffer
14806 freelists. Doing so would sometimes make the controller connection
14807 try to allocate a buffer chunk, which would mess up the internals
14808 of the freelist and cause an assertion failure. Fixes bug 1125;
14809 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
14810 - Learn our external IP address when we're a relay or bridge, even if
14811 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
14812 where we introduced bridge relays that don't need to publish to
14813 be useful. Fixes bug 2050.
14814 - Maintain separate TLS contexts and certificates for incoming and
14815 outgoing connections in bridge relays. Previously we would use the
14816 same TLS contexts and certs for incoming and outgoing connections.
14817 Bugfix on 0.2.0.3-alpha; addresses bug 988.
14818 - Maintain separate identity keys for incoming and outgoing TLS
14819 contexts in bridge relays. Previously we would use the same
14820 identity keys for incoming and outgoing TLS contexts. Bugfix on
14821 0.2.0.3-alpha; addresses the other half of bug 988.
14822 - Avoid an assertion failure when we as an authority receive a
14823 duplicate upload of a router descriptor that we already have,
14824 but which we previously considered an obsolete descriptor.
14825 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
14826 - Avoid a crash bug triggered by looking at a dangling pointer while
14827 setting the network status consensus. Found by Robert Ransom.
14828 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
14829 - Fix a logic error where servers that _didn't_ act as exits would
14830 try to keep their server lists more aggressively up to date than
14831 exits, when it was supposed to be the other way around. Bugfix
14834 o Minor bugfixes (on Tor 0.2.1.x and earlier):
14835 - When we're trying to guess whether we know our IP address as
14836 a relay, we would log various ways that we failed to guess
14837 our address, but never log that we ended up guessing it
14838 successfully. Now add a log line to help confused and anxious
14839 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
14840 - Bring the logic that gathers routerinfos and assesses the
14841 acceptability of circuits into line. This prevents a Tor OP from
14842 getting locked in a cycle of choosing its local OR as an exit for a
14843 path (due to a .exit request) and then rejecting the circuit because
14844 its OR is not listed yet. It also prevents Tor clients from using an
14845 OR running in the same instance as an exit (due to a .exit request)
14846 if the OR does not meet the same requirements expected of an OR
14847 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
14848 - Correctly describe errors that occur when generating a TLS object.
14849 Previously we would attribute them to a failure while generating a
14850 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
14852 - Enforce multiplicity rules when parsing annotations. Bugfix on
14853 0.2.0.8-alpha. Found by piebeer.
14854 - Fix warnings that newer versions of autoconf produced during
14855 ./autogen.sh. These warnings appear to be harmless in our case,
14856 but they were extremely verbose. Fixes bug 2020.
14858 o Minor bugfixes (on Tor 0.2.2.x):
14859 - Enable protection of small arrays whenever we build with gcc
14860 hardening features, not only when also building with warnings
14861 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
14864 - Make hidden services work better in private Tor networks by not
14865 requiring any uptime to join the hidden service descriptor
14866 DHT. Implements ticket 2088.
14867 - Rate-limit the "your application is giving Tor only an IP address"
14868 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
14869 - When AllowSingleHopExits is set, print a warning to explain to the
14870 relay operator why most clients are avoiding her relay.
14871 - Update to the November 1 2010 Maxmind GeoLite Country database.
14873 o Code simplifications and refactoring:
14874 - When we fixed bug 1038 we had to put in a restriction not to send
14875 RELAY_EARLY cells on rend circuits. This was necessary as long
14876 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
14877 active. Now remove this obsolete check. Resolves bug 2081.
14878 - Some options used different conventions for uppercasing of acronyms
14879 when comparing manpage and source. Fix those in favor of the
14880 manpage, as it makes sense to capitalize acronyms.
14881 - Remove the torrc.complete file. It hasn't been kept up to date
14882 and users will have better luck checking out the manpage.
14883 - Remove the obsolete "NoPublish" option; it has been flagged
14884 as obsolete and has produced a warning since 0.1.1.18-rc.
14885 - Remove everything related to building the expert bundle for OS X.
14886 It has confused many users, doesn't work right on OS X 10.6,
14887 and is hard to get rid of once installed. Resolves bug 1274.
14890 Changes in version 0.2.2.17-alpha - 2010-09-30
14891 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
14892 to use one-hop circuits (which can put the exit relays at higher risk,
14893 plus unbalance the network); fixes a big bug in bandwidth accounting
14894 for relays that want to limit their monthly bandwidth use; fixes a
14895 big pile of bugs in how clients tolerate temporary network failure;
14896 and makes our adaptive circuit build timeout feature (which improves
14897 client performance if your network is fast while not breaking things
14898 if your network is slow) better handle bad networks.
14901 - Exit relays now try harder to block exit attempts from unknown
14902 relays, to make it harder for people to use them as one-hop proxies
14903 a la tortunnel. Controlled by the refuseunknownexits consensus
14904 parameter (currently enabled), or you can override it on your
14905 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
14907 o Major bugfixes (0.2.1.x and earlier):
14908 - Fix a bug in bandwidth accounting that could make us use twice
14909 the intended bandwidth when our interval start changes due to
14910 daylight saving time. Now we tolerate skew in stored vs computed
14911 interval starts: if the start of the period changes by no more than
14912 50% of the period's duration, we remember bytes that we transferred
14913 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
14914 - Always search the Windows system directory for system DLLs, and
14915 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
14916 - When you're using bridges and your network goes away and your
14917 bridges get marked as down, recover when you attempt a new socks
14918 connection (if the network is back), rather than waiting up to an
14919 hour to try fetching new descriptors for your bridges. Bugfix on
14920 0.2.0.3-alpha; fixes bug 1981.
14922 o Major bugfixes (on 0.2.2.x):
14923 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
14925 - Fix a segfault that could happen when operating a bridge relay with
14926 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
14927 - The consensus bandwidth-weights (used by clients to choose fast
14928 relays) entered an unexpected edge case in September where
14929 Exits were much scarcer than Guards, resulting in bad weight
14930 recommendations. Now we compute them using new constraints that
14931 should succeed in all cases. Also alter directory authorities to
14932 not include the bandwidth-weights line if they fail to produce
14933 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
14934 - When weighting bridges during path selection, we used to trust
14935 the bandwidths they provided in their descriptor, only capping them
14936 at 10MB/s. This turned out to be problematic for two reasons:
14937 Bridges could claim to handle a lot more traffic then they
14938 actually would, thus making more clients pick them and have a
14939 pretty effective DoS attack. The other issue is that new bridges
14940 that might not have a good estimate for their bw capacity yet
14941 would not get used at all unless no other bridges are available
14942 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
14944 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
14945 - Ignore cannibalized circuits when recording circuit build times.
14946 This should provide for a minor performance improvement for hidden
14947 service users using 0.2.2.14-alpha, and should remove two spurious
14948 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
14949 - Simplify the logic that causes us to decide if the network is
14950 unavailable for purposes of recording circuit build times. If we
14951 receive no cells whatsoever for the entire duration of a circuit's
14952 full measured lifetime, the network is probably down. Also ignore
14953 one-hop directory fetching circuit timeouts when calculating our
14954 circuit build times. These changes should hopefully reduce the
14955 cases where we see ridiculous circuit build timeouts for people
14956 with spotty wireless connections. Fixes part of bug 1772; bugfix
14958 - Prevent the circuit build timeout from becoming larger than
14959 the maximum build time we have ever seen. Also, prevent the time
14960 period for measurement circuits from becoming larger than twice that
14961 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
14964 - When we run out of directory information such that we can't build
14965 circuits, but then get enough that we can build circuits, log when
14966 we actually construct a circuit, so the user has a better chance of
14967 knowing what's going on. Fixes bug 1362.
14968 - Be more generous with how much bandwidth we'd use up (with
14969 accounting enabled) before entering "soft hibernation". Previously,
14970 we'd refuse new connections and circuits once we'd used up 95% of
14971 our allotment. Now, we use up 95% of our allotment, AND make sure
14972 that we have no more than 500MB (or 3 hours of expected traffic,
14973 whichever is lower) remaining before we enter soft hibernation.
14974 - If we've configured EntryNodes and our network goes away and/or all
14975 our entrynodes get marked down, optimistically retry them all when
14976 a new socks application request appears. Fixes bug 1882.
14977 - Add some more defensive programming for architectures that can't
14978 handle unaligned integer accesses. We don't know of any actual bugs
14979 right now, but that's the best time to fix them. Fixes bug 1943.
14980 - Support line continuations in the torrc config file. If a line
14981 ends with a single backslash character, the newline is ignored, and
14982 the configuration value is treated as continuing on the next line.
14985 o Minor bugfixes (on 0.2.1.x and earlier):
14986 - For bandwidth accounting, calculate our expected bandwidth rate
14987 based on the time during which we were active and not in
14988 soft-hibernation during the last interval. Previously, we were
14989 also considering the time spent in soft-hibernation. If this
14990 was a long time, we would wind up underestimating our bandwidth
14991 by a lot, and skewing our wakeup time towards the start of the
14992 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
14994 o Minor bugfixes (on 0.2.2.x):
14995 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
14996 which were disabled by the circuit build timeout changes in
14997 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
14998 - Make sure we don't warn about missing bandwidth weights when
14999 choosing bridges or other relays not in the consensus. Bugfix on
15000 0.2.2.10-alpha; fixes bug 1805.
15001 - In our logs, do not double-report signatures from unrecognized
15002 authorities both as "from unknown authority" and "not
15003 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
15006 Changes in version 0.2.2.16-alpha - 2010-09-17
15007 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
15008 evident at exit relays), and also continues to resolve all the little
15009 bugs that have been filling up trac lately.
15011 o Major bugfixes (stream-level fairness):
15012 - When receiving a circuit-level SENDME for a blocked circuit, try
15013 to package cells fairly from all the streams that had previously
15014 been blocked on that circuit. Previously, we had started with the
15015 oldest stream, and allowed each stream to potentially exhaust
15016 the circuit's package window. This gave older streams on any
15017 given circuit priority over newer ones. Fixes bug 1937. Detected
15018 originally by Camilo Viecco. This bug was introduced before the
15019 first Tor release, in svn commit r152: it is the new winner of
15020 the longest-lived bug prize.
15021 - When the exit relay got a circuit-level sendme cell, it started
15022 reading on the exit streams, even if had 500 cells queued in the
15023 circuit queue already, so the circuit queue just grew and grew in
15024 some cases. We fix this by not re-enabling reading on receipt of a
15025 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
15026 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
15028 - Newly created streams were allowed to read cells onto circuits,
15029 even if the circuit's cell queue was blocked and waiting to drain.
15030 This created potential unfairness, as older streams would be
15031 blocked, but newer streams would gladly fill the queue completely.
15032 We add code to detect this situation and prevent any stream from
15033 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
15037 - Update to the September 1 2010 Maxmind GeoLite Country database.
15038 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
15039 not. This would lead to a cookie that is still not group readable.
15040 Closes bug 1843. Suggested by katmagic.
15041 - When logging a rate-limited warning, we now mention how many messages
15042 got suppressed since the last warning.
15043 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
15044 do individual connection-level rate limiting of clients. The torrc
15045 config options with the same names trump the consensus params, if
15046 both are present. Replaces the old "bwconnrate" and "bwconnburst"
15047 consensus params which were broken from 0.2.2.7-alpha through
15048 0.2.2.14-alpha. Closes bug 1947.
15049 - When a router changes IP address or port, authorities now launch
15050 a new reachability test for it. Implements ticket 1899.
15051 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
15052 2 no signature, 4 required" messages about consensus signatures
15053 easier to read, and make sure they get logged at the same severity
15054 as the messages explaining which keys are which. Fixes bug 1290.
15055 - Don't warn when we have a consensus that we can't verify because
15056 of missing certificates, unless those certificates are ones
15057 that we have been trying and failing to download. Fixes bug 1145.
15058 - If you configure your bridge with a known identity fingerprint,
15059 and the bridge authority is unreachable (as it is in at least
15060 one country now), fall back to directly requesting the descriptor
15061 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
15063 - When building with --enable-gcc-warnings on OpenBSD, disable
15064 warnings in system headers. This makes --enable-gcc-warnings
15065 pass on OpenBSD 4.8.
15067 o Minor bugfixes (on 0.2.1.x and earlier):
15068 - Authorities will now attempt to download consensuses if their
15069 own efforts to make a live consensus have failed. This change
15070 means authorities that restart will fetch a valid consensus, and
15071 it means authorities that didn't agree with the current consensus
15072 will still fetch and serve it if it has enough signatures. Bugfix
15073 on 0.2.0.9-alpha; fixes bug 1300.
15074 - Ensure DNS requests launched by "RESOLVE" commands from the
15075 controller respect the __LeaveStreamsUnattached setconf options. The
15076 same goes for requests launched via DNSPort or transparent
15077 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
15078 - Allow handshaking OR connections to take a full KeepalivePeriod
15079 seconds to handshake. Previously, we would close them after
15080 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
15081 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
15083 - Rate-limit "Failed to hand off onionskin" warnings.
15084 - Never relay a cell for a circuit we have already destroyed.
15085 Between marking a circuit as closeable and finally closing it,
15086 it may have been possible for a few queued cells to get relayed,
15087 even though they would have been immediately dropped by the next
15088 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
15089 - Never queue a cell for a circuit that's already been marked
15091 - Never vote for a server as "Running" if we have a descriptor for
15092 it claiming to be hibernating, and that descriptor was published
15093 more recently than our last contact with the server. Bugfix on
15094 0.2.0.3-alpha; fixes bug 911.
15095 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
15098 o Minor bugfixes (on 0.2.2.x):
15099 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
15100 down if a directory fetch fails and you've configured either
15101 bridges or EntryNodes. The intent was to mark the relay as down
15102 _unless_ you're using bridges or EntryNodes, since if you are
15103 then you could quickly run out of entry points.
15104 - Fix the Windows directory-listing code. A bug introduced in
15105 0.2.2.14-alpha could make Windows directory servers forget to load
15106 some of their cached v2 networkstatus files.
15107 - Really allow clients to use relays as bridges. Fixes bug 1776;
15108 bugfix on 0.2.2.15-alpha.
15109 - Demote a warn to info that happens when the CellStatistics option
15110 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
15111 Reported by Moritz Bartl.
15112 - On Windows, build correctly either with or without Unicode support.
15113 This is necessary so that Tor can support fringe platforms like
15114 Windows 98 (which has no Unicode), or Windows CE (which has no
15115 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
15118 - Add a unit test for cross-platform directory-listing code.
15121 Changes in version 0.2.2.15-alpha - 2010-08-18
15122 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
15123 fixes a variety of other bugs that were preventing performance
15124 experiments from moving forward, fixes several bothersome memory leaks,
15125 and generally closes a lot of smaller bugs that have been filling up
15129 - Stop assigning the HSDir flag to relays that disable their
15130 DirPort (and thus will refuse to answer directory requests). This
15131 fix should dramatically improve the reachability of hidden services:
15132 hidden services and hidden service clients pick six HSDir relays
15133 to store and retrieve the hidden service descriptor, and currently
15134 about half of the HSDir relays will refuse to work. Bugfix on
15135 0.2.0.10-alpha; fixes part of bug 1693.
15136 - The PerConnBWRate and Burst config options, along with the
15137 bwconnrate and bwconnburst consensus params, initialized each conn's
15138 token bucket values only when the connection is established. Now we
15139 update them if the config options change, and update them every time
15140 we get a new consensus. Otherwise we can encounter an ugly edge
15141 case where we initialize an OR conn to client-level bandwidth,
15142 but then later the relay joins the consensus and we leave it
15143 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
15144 - Fix a regression that caused Tor to rebind its ports if it receives
15145 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
15148 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
15149 should give us approximately 40-50% more Guard-flagged nodes,
15150 improving the anonymity the Tor network can provide and also
15151 decreasing the dropoff in throughput that relays experience when
15152 they first get the Guard flag.
15153 - Allow enabling or disabling the *Statistics config options while
15157 - Update to the August 1 2010 Maxmind GeoLite Country database.
15158 - Have the controller interface give a more useful message than
15159 "Internal Error" in response to failed GETINFO requests.
15160 - Warn when the same option is provided more than once in a torrc
15161 file, on the command line, or in a single SETCONF statement, and
15162 the option is one that only accepts a single line. Closes bug 1384.
15163 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
15164 Patch from mingw-san.
15165 - Add support for the country code "{??}" in torrc options like
15166 ExcludeNodes, to indicate all routers of unknown country. Closes
15168 - Relays report the number of bytes spent on answering directory
15169 requests in extra-info descriptors similar to {read,write}-history.
15170 Implements enhancement 1790.
15172 o Minor bugfixes (on 0.2.1.x and earlier):
15173 - Complain if PublishServerDescriptor is given multiple arguments that
15174 include 0 or 1. This configuration will be rejected in the future.
15175 Bugfix on 0.2.0.1-alpha; closes bug 1107.
15176 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
15177 Bugfix on 0.2.0.13-alpha; closes bug 928.
15178 - Change "Application request when we're believed to be offline."
15179 notice to "Application request when we haven't used client
15180 functionality lately.", to clarify that it's not an error. Bugfix
15181 on 0.0.9.3; fixes bug 1222.
15182 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
15183 would return "551 Internal error" rather than "552 Unrecognized key
15184 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
15185 - Users can't configure a regular relay to be their bridge. It didn't
15186 work because when Tor fetched the bridge descriptor, it found
15187 that it already had it, and didn't realize that the purpose of the
15188 descriptor had changed. Now we replace routers with a purpose other
15189 than bridge with bridge descriptors when fetching them. Bugfix on
15190 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
15191 refetch the descriptor with router purpose 'general', disabling
15193 - Fix a rare bug in rend_fn unit tests: we would fail a test when
15194 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
15195 on 0.2.0.10-alpha; fixes bug 1808.
15196 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
15197 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
15198 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
15199 Servers can start sending this code when enough clients recognize
15200 it. Also update the spec to reflect this new reason. Bugfix on
15201 0.1.0.1-rc; fixes part of bug 1793.
15202 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
15203 when we switch from being a public relay to a bridge. Otherwise
15204 there will still be clients that see the relay in their consensus,
15205 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
15207 - Instead of giving an assertion failure on an internal mismatch
15208 on estimated freelist size, just log a BUG warning and try later.
15209 Mitigates but does not fix bug 1125.
15210 - Fix an assertion failure that could occur in caches or bridge users
15211 when using a very short voting interval on a testing network.
15212 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
15214 o Minor bugfixes (on 0.2.2.x):
15215 - Alter directory authorities to always consider Exit-flagged nodes
15216 as potential Guard nodes in their votes. The actual decision to
15217 use Exits as Guards is done in the consensus bandwidth weights.
15218 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
15219 - When the controller is reporting the purpose of circuits that
15220 didn't finish building before the circuit build timeout, it was
15221 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
15222 - Our libevent version parsing code couldn't handle versions like
15223 1.4.14b-stable and incorrectly warned the user about using an
15224 old and broken version of libevent. Treat 1.4.14b-stable like
15225 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
15227 - Don't use substitution references like $(VAR:MOD) when
15228 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
15229 '$(:x)' to 'x' rather than the empty string. This bites us in
15230 doc/ when configured with --disable-asciidoc. Bugfix on
15231 0.2.2.9-alpha; fixes bug 1773.
15232 - Remove a spurious hidden service server-side log notice about
15233 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
15235 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
15237 - Correctly report written bytes on linked connections. Found while
15238 implementing 1790. Bugfix on 0.2.2.4-alpha.
15239 - Fix three memory leaks: one in circuit_build_times_parse_state(),
15240 one in dirvote_add_signatures_to_pending_consensus(), and one every
15241 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
15242 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
15244 o Code simplifications and refactoring:
15245 - Take a first step towards making or.h smaller by splitting out
15246 function definitions for all source files in src/or/. Leave
15247 structures and defines in or.h for now.
15248 - Remove a bunch of unused function declarations as well as a block of
15249 #if 0'd code from the unit tests. Closes bug 1824.
15250 - New unit tests for exit-port history statistics; refactored exit
15251 statistics code to be more easily tested.
15252 - Remove the old debian/ directory from the main Tor distribution.
15253 The official Tor-for-debian git repository lives at the URL
15254 https://git.torproject.org/debian/tor.git
15257 Changes in version 0.2.2.14-alpha - 2010-07-12
15258 Tor 0.2.2.14-alpha greatly improves client-side handling of
15259 circuit build timeouts, which are used to estimate speed and improve
15260 performance. We also move to a much better GeoIP database, port Tor to
15261 Windows CE, introduce new compile flags that improve code security,
15262 add an eighth v3 directory authority, and address a lot of more
15266 - Tor directory authorities no longer crash when started with a
15267 cached-microdesc-consensus file in their data directory. Bugfix
15268 on 0.2.2.6-alpha; fixes bug 1532.
15269 - Treat an unset $HOME like an empty $HOME rather than triggering an
15270 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
15271 - Ignore negative and large circuit build timeout values that can
15272 happen during a suspend or hibernate. These values caused various
15273 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
15274 - Alter calculation of Pareto distribution parameter 'Xm' for
15275 Circuit Build Timeout learning to use the weighted average of the
15276 top N=3 modes (because we have three entry guards). Considering
15277 multiple modes should improve the timeout calculation in some cases,
15278 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
15280 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
15281 right censored distribution model. This approach improves over the
15282 synthetic timeout generation approach that was producing insanely
15283 high timeout values. Now we calculate build timeouts using truncated
15284 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
15285 - Do not close circuits that are under construction when they reach
15286 the circuit build timeout. Instead, leave them building (but do not
15287 use them) for up until the time corresponding to the 95th percentile
15288 on the Pareto CDF or 60 seconds, whichever is greater. This is done
15289 to provide better data for the new Pareto model. This percentile
15290 can be controlled by the consensus.
15293 - Move to the June 2010 Maxmind GeoLite country db (rather than the
15294 June 2009 ip-to-country GeoIP db) for our statistics that count
15295 how many users relays are seeing from each country. Now we have
15296 more accurate data for many African countries.
15297 - Port Tor to build and run correctly on Windows CE systems, using
15298 the wcecompat library. Contributed by Valerio Lupi.
15299 - New "--enable-gcc-hardening" ./configure flag (off by default)
15300 to turn on gcc compile time hardening options. It ensures
15301 that signed ints have defined behavior (-fwrapv), enables
15302 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
15303 with canaries (-fstack-protector-all), turns on ASLR protection if
15304 supported by the kernel (-fPIE, -pie), and adds additional security
15305 related warnings. Verified to work on Mac OS X and Debian Lenny.
15306 - New "--enable-linker-hardening" ./configure flag (off by default)
15307 to turn on ELF specific hardening features (relro, now). This does
15308 not work with Mac OS X or any other non-ELF binary format.
15310 o New directory authorities:
15311 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
15315 - New config option "WarnUnsafeSocks 0" disables the warning that
15316 occurs whenever Tor receives a socks handshake using a version of
15317 the socks protocol that can only provide an IP address (rather
15318 than a hostname). Setups that do DNS locally over Tor are fine,
15319 and we shouldn't spam the logs in that case.
15320 - Convert the HACKING file to asciidoc, and add a few new sections
15321 to it, explaining how we use Git, how we make changelogs, and
15322 what should go in a patch.
15323 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
15324 event, to give information on the current rate of circuit timeouts
15325 over our stored history.
15326 - Add ability to disable circuit build time learning via consensus
15327 parameter and via a LearnCircuitBuildTimeout config option. Also
15328 automatically disable circuit build time calculation if we are
15329 either a AuthoritativeDirectory, or if we fail to write our state
15330 file. Fixes bug 1296.
15331 - More gracefully handle corrupt state files, removing asserts
15332 in favor of saving a backup and resetting state.
15333 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
15337 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
15339 - When a2x fails, mention that the user could disable manpages instead
15340 of trying to fix their asciidoc installation.
15341 - Where available, use Libevent 2.0's periodic timers so that our
15342 once-per-second cleanup code gets called even more closely to
15343 once per second than it would otherwise. Fixes bug 943.
15344 - If you run a bridge that listens on multiple IP addresses, and
15345 some user configures a bridge address that uses a different IP
15346 address than your bridge writes in its router descriptor, and the
15347 user doesn't specify an identity key, their Tor would discard the
15348 descriptor because "it isn't one of our configured bridges", and
15349 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
15350 Bugfix on 0.2.0.3-alpha.
15351 - If OpenSSL fails to make a duplicate of a private or public key, log
15352 an error message and try to exit cleanly. May help with debugging
15353 if bug 1209 ever remanifests.
15354 - Save a couple bytes in memory allocation every time we escape
15355 certain characters in a string. Patch from Florian Zumbiehl.
15356 - Make it explicit that we don't cannibalize one-hop circuits. This
15357 happens in the wild, but doesn't turn out to be a problem because
15358 we fortunately don't use those circuits. Many thanks to outofwords
15359 for the initial analysis and to swissknife who confirmed that
15360 two-hop circuits are actually created.
15361 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
15362 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
15363 - Eliminate a case where a circuit build time warning was displayed
15364 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
15367 Changes in version 0.2.1.26 - 2010-05-02
15368 Tor 0.2.1.26 addresses the recent connection and memory overload
15369 problems we've been seeing on relays, especially relays with their
15370 DirPort open. If your relay has been crashing, or you turned it off
15371 because it used too many resources, give this release a try.
15373 This release also fixes yet another instance of broken OpenSSL libraries
15374 that was causing some relays to drop out of the consensus.
15377 - Teach relays to defend themselves from connection overload. Relays
15378 now close idle circuits early if it looks like they were intended
15379 for directory fetches. Relays are also more aggressive about closing
15380 TLS connections that have no circuits on them. Such circuits are
15381 unlikely to be re-used, and tens of thousands of them were piling
15382 up at the fast relays, causing the relays to run out of sockets
15383 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
15384 their directory fetches over TLS).
15385 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
15386 that claim to be earlier than 0.9.8m, but which have in reality
15387 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
15388 behavior. Possible fix for some cases of bug 1346.
15389 - Directory mirrors were fetching relay descriptors only from v2
15390 directory authorities, rather than v3 authorities like they should.
15391 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
15392 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
15395 - Finally get rid of the deprecated and now harmful notion of "clique
15396 mode", where directory authorities maintain TLS connections to
15400 - In the util/threads test, no longer free the test_mutex before all
15401 worker threads have finished. Bugfix on 0.2.1.6-alpha.
15402 - The master thread could starve the worker threads quite badly on
15403 certain systems, causing them to run only partially in the allowed
15404 window. This resulted in test failures. Now the master thread sleeps
15405 occasionally for a few microseconds while the two worker-threads
15406 compete for the mutex. Bugfix on 0.2.0.1-alpha.
15409 Changes in version 0.2.2.13-alpha - 2010-04-24
15410 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
15411 problems we've been seeing on relays, especially relays with their
15412 DirPort open. If your relay has been crashing, or you turned it off
15413 because it used too many resources, give this release a try.
15416 - Teach relays to defend themselves from connection overload. Relays
15417 now close idle circuits early if it looks like they were intended
15418 for directory fetches. Relays are also more aggressive about closing
15419 TLS connections that have no circuits on them. Such circuits are
15420 unlikely to be re-used, and tens of thousands of them were piling
15421 up at the fast relays, causing the relays to run out of sockets
15422 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
15423 their directory fetches over TLS).
15426 - Finally get rid of the deprecated and now harmful notion of "clique
15427 mode", where directory authorities maintain TLS connections to
15429 - Directory authorities now do an immediate reachability check as soon
15430 as they hear about a new relay. This change should slightly reduce
15431 the time between setting up a relay and getting listed as running
15432 in the consensus. It should also improve the time between setting
15433 up a bridge and seeing use by bridge users.
15434 - Directory authorities no longer launch a TLS connection to every
15435 relay as they startup. Now that we have 2k+ descriptors cached,
15436 the resulting network hiccup is becoming a burden. Besides,
15437 authorities already avoid voting about Running for the first half
15438 hour of their uptime.
15441 Changes in version 0.2.2.12-alpha - 2010-04-20
15442 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
15443 handle and vote on descriptors. It was causing relays to drop out of
15447 - Many relays have been falling out of the consensus lately because
15448 not enough authorities know about their descriptor for them to get
15449 a majority of votes. When we deprecated the v2 directory protocol,
15450 we got rid of the only way that v3 authorities can hear from each
15451 other about other descriptors. Now authorities examine every v3
15452 vote for new descriptors, and fetch them from that authority. Bugfix
15454 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
15455 and a warning in or.h related to bandwidth_weight_rule_t that
15456 prevented clean compile on OS X. Fixes bug 1363; bugfix on
15458 - Fix a segfault on relays when DirReqStatistics is enabled
15459 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
15463 - Demote a confusing TLS warning that relay operators might get when
15464 someone tries to talk to their OrPort. It is neither the operator's
15465 fault nor can they do anything about it. Fixes bug 1364; bugfix
15469 Changes in version 0.2.2.11-alpha - 2010-04-15
15470 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
15471 libraries that was causing some relays to drop out of the consensus.
15474 - Directory mirrors were fetching relay descriptors only from v2
15475 directory authorities, rather than v3 authorities like they should.
15476 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
15477 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
15478 - Fix a parsing error that made every possible value of
15479 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
15480 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
15481 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
15482 about the option without breaking older ones.
15483 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
15484 that claim to be earlier than 0.9.8m, but which have in reality
15485 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
15486 behavior. Possible fix for some cases of bug 1346.
15489 - Experiment with a more aggressive approach to preventing clients
15490 from making one-hop exit streams. Exit relays who want to try it
15491 out can set "RefuseUnknownExits 1" in their torrc, and then look
15492 for "Attempt by %s to open a stream" log messages. Let us know
15494 - Add support for statically linking zlib by specifying
15495 --enable-static-zlib, to go with our support for statically linking
15496 openssl and libevent. Resolves bug 1358.
15499 - Fix a segfault that happens whenever a Tor client that is using
15500 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
15502 - When we cleaned up the contrib/tor-exit-notice.html file, we left
15503 out the first line. Fixes bug 1295.
15504 - When building the manpage from a tarball, we required asciidoc, but
15505 the asciidoc -> roff/html conversion was already done for the
15506 tarball. Make 'make' complain only when we need asciidoc (either
15507 because we're compiling directly from git, or because we altered
15508 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
15509 - When none of the directory authorities vote on any params, Tor
15510 segfaulted when trying to make the consensus from the votes. We
15511 didn't trigger the bug in practice, because authorities do include
15512 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
15515 - In the util/threads test, no longer free the test_mutex before all
15516 worker threads have finished. Bugfix on 0.2.1.6-alpha.
15517 - The master thread could starve the worker threads quite badly on
15518 certain systems, causing them to run only partially in the allowed
15519 window. This resulted in test failures. Now the master thread sleeps
15520 occasionally for a few microseconds while the two worker-threads
15521 compete for the mutex. Bugfix on 0.2.0.1-alpha.
15524 Changes in version 0.2.2.10-alpha - 2010-03-07
15525 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
15526 could prevent relays from guessing their IP address correctly. It also
15527 starts the groundwork for another client-side performance boost, since
15528 currently we're not making efficient use of relays that have both the
15529 Guard flag and the Exit flag.
15532 - Fix a regression from our patch for bug 1244 that caused relays
15533 to guess their IP address incorrectly if they didn't set Address
15534 in their torrc and/or their address fails to resolve. Bugfix on
15535 0.2.2.9-alpha; fixes bug 1269.
15537 o Major features (performance):
15538 - Directory authorities now compute consensus weightings that instruct
15539 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
15540 and no flag. Clients that use these weightings will distribute
15541 network load more evenly across these different relay types. The
15542 weightings are in the consensus so we can change them globally in
15543 the future. Extra thanks to "outofwords" for finding some nasty
15544 security bugs in the first implementation of this feature.
15546 o Minor features (performance):
15547 - Always perform router selections using weighted relay bandwidth,
15548 even if we don't need a high capacity circuit at the time. Non-fast
15549 circuits now only differ from fast ones in that they can use relays
15550 not marked with the Fast flag. This "feature" could turn out to
15551 be a horrible bug; we should investigate more before it goes into
15555 - Allow disabling building of the manpages. Skipping the manpage
15556 speeds up the build considerably.
15558 o Minor bugfixes (on 0.2.2.x):
15559 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
15560 Bugfix on 0.2.2.9-alpha.
15561 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
15562 config option. Bugfix on 0.2.2.7-alpha.
15563 - Ship the asciidoc-helper file in the tarball, so that people can
15564 build from source if they want to, and touching the .1.txt files
15565 doesn't break the build. Bugfix on 0.2.2.9-alpha.
15567 o Minor bugfixes (on 0.2.1.x or earlier):
15568 - Fix a dereference-then-NULL-check sequence when publishing
15569 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
15571 - Fix another dereference-then-NULL-check sequence. Bugfix on
15572 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
15573 - Make sure we treat potentially not NUL-terminated strings correctly.
15574 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
15576 o Code simplifications and refactoring:
15577 - Fix some urls in the exit notice file and make it XHTML1.1 strict
15578 compliant. Based on a patch from Christian Kujau.
15579 - Don't use sed in asciidoc-helper anymore.
15580 - Make the build process fail if asciidoc cannot be found and
15581 building with asciidoc isn't disabled.
15584 Changes in version 0.2.2.9-alpha - 2010-02-22
15585 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
15586 location of a directory authority, and cleans up a bunch of small bugs.
15588 o Directory authority changes:
15589 - Change IP address for dannenberg (v3 directory authority), and
15590 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
15591 service directory authority) from the list.
15594 - Make Tor work again on the latest OS X: when deciding whether to
15595 use strange flags to turn TLS renegotiation on, detect the OpenSSL
15596 version at run-time, not compile time. We need to do this because
15597 Apple doesn't update its dev-tools headers when it updates its
15598 libraries in a security patch.
15599 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
15600 that could happen on 32-bit platforms with 64-bit time_t. Also fix
15601 a memory leak when requesting a hidden service descriptor we've
15602 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
15604 - Authorities could be tricked into giving out the Exit flag to relays
15605 that didn't allow exiting to any ports. This bug could screw
15606 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
15607 1238. Bug discovered by Martin Kowalczyk.
15608 - When freeing a session key, zero it out completely. We only zeroed
15609 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
15610 patched by ekir. Fixes bug 1254.
15613 - Fix static compilation by listing the openssl libraries in the right
15614 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
15615 - Resume handling .exit hostnames in a special way: originally we
15616 stripped the .exit part and used the requested exit relay. In
15617 0.2.2.1-alpha we stopped treating them in any special way, meaning
15618 if you use a .exit address then Tor will pass it on to the exit
15619 relay. Now we reject the .exit stream outright, since that behavior
15620 might be more expected by the user. Found and diagnosed by Scott
15621 Bennett and Downie on or-talk.
15622 - Don't spam the controller with events when we have no file
15623 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
15624 for log messages was already solved from bug 748.)
15625 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
15627 - Make the DNSPort option work with libevent 2.x. Don't alter the
15628 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
15629 - Emit a GUARD DROPPED controller event for a case we missed.
15630 - Make more fields in the controller protocol case-insensitive, since
15631 control-spec.txt said they were.
15632 - Refactor resolve_my_address() to not use gethostbyname() anymore.
15633 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
15634 - Fix a spec conformance issue: the network-status-version token
15635 must be the first token in a v3 consensus or vote. Discovered by
15636 parakeep. Bugfix on 0.2.0.3-alpha.
15638 o Code simplifications and refactoring:
15639 - Generate our manpage and HTML documentation using Asciidoc. This
15640 change should make it easier to maintain the documentation, and
15641 produce nicer HTML.
15642 - Remove the --enable-iphone option. According to reports from Marco
15643 Bonetti, Tor builds fine without any special tweaking on recent
15644 iPhone SDK versions.
15645 - Removed some unnecessary files from the source distribution. The
15646 AUTHORS file has now been merged into the people page on the
15647 website. The roadmaps and design doc can now be found in the
15648 projects directory in svn.
15649 - Enabled various circuit build timeout constants to be controlled
15650 by consensus parameters. Also set better defaults for these
15651 parameters based on experimentation on broadband and simulated
15652 high latency links.
15655 - The 'EXTENDCIRCUIT' control port command can now be used with
15656 a circ id of 0 and no path. This feature will cause Tor to build
15657 a new 'fast' general purpose circuit using its own path selection
15659 - Added a BUILDTIMEOUT_SET controller event to describe changes
15660 to the circuit build timeout.
15661 - Future-proof the controller protocol a bit by ignoring keyword
15662 arguments we do not recognize.
15663 - Expand homedirs passed to tor-checkkey. This should silence a
15664 coverity complaint about passing a user-supplied string into
15665 open() without checking it.
15668 Changes in version 0.2.1.25 - 2010-03-16
15669 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
15670 prevent relays from guessing their IP address correctly. It also fixes
15671 several minor potential security bugs.
15674 - Fix a regression from our patch for bug 1244 that caused relays
15675 to guess their IP address incorrectly if they didn't set Address
15676 in their torrc and/or their address fails to resolve. Bugfix on
15677 0.2.1.23; fixes bug 1269.
15678 - When freeing a session key, zero it out completely. We only zeroed
15679 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
15680 patched by ekir. Fixes bug 1254.
15683 - Fix a dereference-then-NULL-check sequence when publishing
15684 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
15686 - Fix another dereference-then-NULL-check sequence. Bugfix on
15687 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
15688 - Make sure we treat potentially not NUL-terminated strings correctly.
15689 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
15693 Changes in version 0.2.1.24 - 2010-02-21
15694 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
15698 - Work correctly out-of-the-box with even more vendor-patched versions
15699 of OpenSSL. In particular, make it so Debian and OS X don't need
15700 customized patches to run/build.
15703 Changes in version 0.2.1.23 - 2010-02-13
15704 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
15705 again on the latest OS X, and updates the location of a directory
15708 o Major bugfixes (performance):
15709 - We were selecting our guards uniformly at random, and then weighting
15710 which of our guards we'd use uniformly at random. This imbalance
15711 meant that Tor clients were severely limited on throughput (and
15712 probably latency too) by the first hop in their circuit. Now we
15713 select guards weighted by currently advertised bandwidth. We also
15714 automatically discard guards picked using the old algorithm. Fixes
15715 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
15718 - Make Tor work again on the latest OS X: when deciding whether to
15719 use strange flags to turn TLS renegotiation on, detect the OpenSSL
15720 version at run-time, not compile time. We need to do this because
15721 Apple doesn't update its dev-tools headers when it updates its
15722 libraries in a security patch.
15723 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
15724 that could happen on 32-bit platforms with 64-bit time_t. Also fix
15725 a memory leak when requesting a hidden service descriptor we've
15726 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
15729 o Directory authority changes:
15730 - Change IP address for dannenberg (v3 directory authority), and
15731 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
15732 service directory authority) from the list.
15735 - Refactor resolve_my_address() to not use gethostbyname() anymore.
15736 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
15739 - Avoid a mad rush at the beginning of each month when each client
15740 rotates half of its guards. Instead we spread the rotation out
15741 throughout the month, but we still avoid leaving a precise timestamp
15742 in the state file about when we first picked the guard. Improves
15743 over the behavior introduced in 0.1.2.17.
15746 Changes in version 0.2.2.8-alpha - 2010-01-26
15747 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
15748 causing bridge relays to disappear. If you're running a bridge,
15752 - Fix a memory corruption bug on bridges that occured during the
15753 inclusion of stats data in extra-info descriptors. Also fix the
15754 interface for geoip_get_bridge_stats* to prevent similar bugs in
15755 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
15756 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
15759 - Ignore OutboundBindAddress when connecting to localhost.
15760 Connections to localhost need to come _from_ localhost, or else
15761 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
15765 Changes in version 0.2.2.7-alpha - 2010-01-19
15766 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
15767 as laying the groundwork for further relay-side performance fixes. It
15768 also starts cleaning up client behavior with respect to the EntryNodes,
15769 ExitNodes, and StrictNodes config options.
15771 This release also rotates two directory authority keys, due to a
15772 security breach of some of the Torproject servers.
15774 o Directory authority changes:
15775 - Rotate keys (both v3 identity and relay identity) for moria1
15778 o Major features (performance):
15779 - We were selecting our guards uniformly at random, and then weighting
15780 which of our guards we'd use uniformly at random. This imbalance
15781 meant that Tor clients were severely limited on throughput (and
15782 probably latency too) by the first hop in their circuit. Now we
15783 select guards weighted by currently advertised bandwidth. We also
15784 automatically discard guards picked using the old algorithm. Fixes
15785 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
15786 - When choosing which cells to relay first, relays can now favor
15787 circuits that have been quiet recently, to provide lower latency
15788 for low-volume circuits. By default, relays enable or disable this
15789 feature based on a setting in the consensus. You can override
15790 this default by using the new "CircuitPriorityHalflife" config
15791 option. Design and code by Ian Goldberg, Can Tang, and Chris
15793 - Add separate per-conn write limiting to go with the per-conn read
15794 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
15795 but never per-conn write limits.
15796 - New consensus params "bwconnrate" and "bwconnburst" to let us
15797 rate-limit client connections as they enter the network. It's
15798 controlled in the consensus so we can turn it on and off for
15799 experiments. It's starting out off. Based on proposal 163.
15801 o Major features (relay selection options):
15802 - Switch to a StrictNodes config option, rather than the previous
15803 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
15804 "StrictExcludeNodes" option.
15805 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
15806 change during a config reload, mark and discard all our origin
15807 circuits. This fix should address edge cases where we change the
15808 config options and but then choose a circuit that we created before
15810 - If EntryNodes or ExitNodes are set, be more willing to use an
15811 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
15813 - Make EntryNodes config option much more aggressive even when
15814 StrictNodes is not set. Before it would prepend your requested
15815 entrynodes to your list of guard nodes, but feel free to use others
15816 after that. Now it chooses only from your EntryNodes if any of
15817 those are available, and only falls back to others if a) they're
15818 all down and b) StrictNodes is not set.
15819 - Now we refresh your entry guards from EntryNodes at each consensus
15820 fetch -- rather than just at startup and then they slowly rot as
15821 the network changes.
15824 - Stop bridge directory authorities from answering dbg-stability.txt
15825 directory queries, which would let people fetch a list of all
15826 bridge identities they track. Bugfix on 0.2.1.6-alpha.
15829 - Log a notice when we get a new control connection. Now it's easier
15830 for security-conscious users to recognize when a local application
15831 is knocking on their controller door. Suggested by bug 1196.
15832 - New config option "CircuitStreamTimeout" to override our internal
15833 timeout schedule for how many seconds until we detach a stream from
15834 a circuit and try a new circuit. If your network is particularly
15835 slow, you might want to set this to a number like 60.
15836 - New controller command "getinfo config-text". It returns the
15837 contents that Tor would write if you send it a SAVECONF command,
15838 so the controller can write the file to disk itself.
15839 - New options for SafeLogging to allow scrubbing only log messages
15840 generated while acting as a relay.
15841 - Ship the bridges spec file in the tarball too.
15842 - Avoid a mad rush at the beginning of each month when each client
15843 rotates half of its guards. Instead we spread the rotation out
15844 throughout the month, but we still avoid leaving a precise timestamp
15845 in the state file about when we first picked the guard. Improves
15846 over the behavior introduced in 0.1.2.17.
15848 o Minor bugfixes (compiling):
15849 - Fix compilation on OS X 10.3, which has a stub mlockall() but
15850 hides it. Bugfix on 0.2.2.6-alpha.
15851 - Fix compilation on Solaris by removing support for the
15852 DisableAllSwap config option. Solaris doesn't have an rlimit for
15853 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
15856 o Minor bugfixes (crashes):
15857 - Do not segfault when writing buffer stats when we haven't observed
15858 a single circuit to report about. Found by Fabian Lanze. Bugfix on
15860 - If we're in the pathological case where there's no exit bandwidth
15861 but there is non-exit bandwidth, or no guard bandwidth but there
15862 is non-guard bandwidth, don't crash during path selection. Bugfix
15864 - Fix an impossible-to-actually-trigger buffer overflow in relay
15865 descriptor generation. Bugfix on 0.1.0.15.
15867 o Minor bugfixes (privacy):
15868 - Fix an instance where a Tor directory mirror might accidentally
15869 log the IP address of a misbehaving Tor client. Bugfix on
15871 - Don't list Windows capabilities in relay descriptors. We never made
15872 use of them, and maybe it's a bad idea to publish them. Bugfix
15875 o Minor bugfixes (other):
15876 - Resolve an edge case in path weighting that could make us misweight
15877 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
15878 - Fix statistics on client numbers by country as seen by bridges that
15879 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
15880 intervals instead of variable 12-to-48-hour intervals.
15881 - After we free an internal connection structure, overwrite it
15882 with a different memory value than we use for overwriting a freed
15883 internal circuit structure. Should help with debugging. Suggested
15885 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
15888 o Removed features:
15889 - Remove the HSAuthorityRecordStats option that version 0 hidden
15890 service authorities could have used to track statistics of overall
15891 hidden service usage.
15894 Changes in version 0.2.1.22 - 2010-01-19
15895 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
15896 authorities -- it would tell you its whole history of bridge descriptors
15897 if you make the right directory request. This stable update also
15898 rotates two of the seven v3 directory authority keys and locations.
15900 o Directory authority changes:
15901 - Rotate keys (both v3 identity and relay identity) for moria1
15905 - Stop bridge directory authorities from answering dbg-stability.txt
15906 directory queries, which would let people fetch a list of all
15907 bridge identities they track. Bugfix on 0.2.1.6-alpha.
15910 Changes in version 0.2.1.21 - 2009-12-21
15911 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
15912 library. If you use Tor on Linux / Unix and you're getting SSL
15913 renegotiation errors, upgrading should help. We also recommend an
15914 upgrade if you're an exit relay.
15917 - Work around a security feature in OpenSSL 0.9.8l that prevents our
15918 handshake from working unless we explicitly tell OpenSSL that we
15919 are using SSL renegotiation safely. We are, of course, but OpenSSL
15920 0.9.8l won't work unless we say we are.
15921 - Avoid crashing if the client is trying to upload many bytes and the
15922 circuit gets torn down at the same time, or if the flip side
15923 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
15926 - Do not refuse to learn about authority certs and v2 networkstatus
15927 documents that are older than the latest consensus. This bug might
15928 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
15929 Spotted and fixed by xmux.
15930 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
15931 trigger platform-specific option misparsing case found by Coverity
15933 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
15934 trigger assert. Fixes bug 1173.
15937 Changes in version 0.2.2.6-alpha - 2009-11-19
15938 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
15939 support for the new lower-footprint "microdescriptor" directory design,
15940 future-proofing our consensus format against new hash functions or
15941 other changes, and an Android port. It also makes Tor compatible with
15942 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
15945 - Directory authorities can now create, vote on, and serve multiple
15946 parallel formats of directory data as part of their voting process.
15947 Partially implements Proposal 162: "Publish the consensus in
15949 - Directory authorities can now agree on and publish small summaries
15950 of router information that clients can use in place of regular
15951 server descriptors. This transition will eventually allow clients
15952 to use far less bandwidth for downloading information about the
15953 network. Begins the implementation of Proposal 158: "Clients
15954 download consensus + microdescriptors".
15955 - The directory voting system is now extensible to use multiple hash
15956 algorithms for signatures and resource selection. Newer formats
15957 are signed with SHA256, with a possibility for moving to a better
15958 hash algorithm in the future.
15959 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
15960 current and future memory pages via mlockall(). On supported
15961 platforms (modern Linux and probably BSD but not Windows or OS X),
15962 this should effectively disable any and all attempts to page out
15963 memory. This option requires that you start your Tor as root --
15964 if you use DisableAllSwap, please consider using the User option
15965 to properly reduce the privileges of your Tor.
15966 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
15967 to help Tor build correctly for Android phones.
15970 - Work around a security feature in OpenSSL 0.9.8l that prevents our
15971 handshake from working unless we explicitly tell OpenSSL that we
15972 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
15973 won't work unless we say we are.
15976 - Fix a crash bug when trying to initialize the evdns module in
15977 Libevent 2. Bugfix on 0.2.1.16-rc.
15978 - Stop logging at severity 'warn' when some other Tor client tries
15979 to establish a circuit with us using weak DH keys. It's a protocol
15980 violation, but that doesn't mean ordinary users need to hear about
15981 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
15982 - Do not refuse to learn about authority certs and v2 networkstatus
15983 documents that are older than the latest consensus. This bug might
15984 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
15985 Spotted and fixed by xmux.
15986 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
15987 - If all authorities restart at once right before a consensus vote,
15988 nobody will vote about "Running", and clients will get a consensus
15989 with no usable relays. Instead, authorities refuse to build a
15990 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
15991 - If your relay can't keep up with the number of incoming create
15992 cells, it would log one warning per failure into your logs. Limit
15993 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
15994 - Bridges now use "reject *:*" as their default exit policy. Bugfix
15995 on 0.2.0.3-alpha; fixes bug 1113.
15996 - Fix a memory leak on directory authorities during voting that was
15997 introduced in 0.2.2.1-alpha. Found via valgrind.
16000 Changes in version 0.2.1.20 - 2009-10-15
16001 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
16002 services at once, prepares for more performance improvements, and
16003 fixes a bunch of smaller bugs.
16005 The Windows and OS X bundles also include a more recent Vidalia,
16006 and switch from Privoxy to Polipo.
16008 The OS X installers are now drag and drop. It's best to un-install
16009 Tor/Vidalia and then install this new bundle, rather than upgrade. If
16010 you want to upgrade, you'll need to update the paths for Tor and Polipo
16011 in the Vidalia Settings window.
16014 - Send circuit or stream sendme cells when our window has decreased
16015 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
16016 by Karsten when testing the "reduce circuit window" performance
16017 patch. Bugfix on the 54th commit on Tor -- from July 2002,
16018 before the release of Tor 0.0.0. This is the new winner of the
16020 - Fix a remotely triggerable memory leak when a consensus document
16021 contains more than one signature from the same voter. Bugfix on
16023 - Avoid segfault in rare cases when finishing an introduction circuit
16024 as a client and finding out that we don't have an introduction key
16025 for it. Fixes bug 1073. Reported by Aaron Swartz.
16028 - Tor now reads the "circwindow" parameter out of the consensus,
16029 and uses that value for its circuit package window rather than the
16030 default of 1000 cells. Begins the implementation of proposal 168.
16032 o New directory authorities:
16033 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
16035 - Move moria1 and tonga to alternate IP addresses.
16038 - Fix a signed/unsigned compile warning in 0.2.1.19.
16039 - Fix possible segmentation fault on directory authorities. Bugfix on
16041 - Fix an extremely rare infinite recursion bug that could occur if
16042 we tried to log a message after shutting down the log subsystem.
16043 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
16044 - Fix an obscure bug where hidden services on 64-bit big-endian
16045 systems might mis-read the timestamp in v3 introduce cells, and
16046 refuse to connect back to the client. Discovered by "rotor".
16047 Bugfix on 0.2.1.6-alpha.
16048 - We were triggering a CLOCK_SKEW controller status event whenever
16049 we connect via the v2 connection protocol to any relay that has
16050 a wrong clock. Instead, we should only inform the controller when
16051 it's a trusted authority that claims our clock is wrong. Bugfix
16052 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
16053 - We were telling the controller about CHECKING_REACHABILITY and
16054 REACHABILITY_FAILED status events whenever we launch a testing
16055 circuit or notice that one has failed. Instead, only tell the
16056 controller when we want to inform the user of overall success or
16057 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
16059 - Don't warn when we're using a circuit that ends with a node
16060 excluded in ExcludeExitNodes, but the circuit is not used to access
16061 the outside world. This should help fix bug 1090. Bugfix on
16063 - Work around a small memory leak in some versions of OpenSSL that
16064 stopped the memory used by the hostname TLS extension from being
16068 - Add a "getinfo status/accepted-server-descriptor" controller
16069 command, which is the recommended way for controllers to learn
16070 whether our server descriptor has been successfully received by at
16071 least on directory authority. Un-recommend good-server-descriptor
16072 getinfo and status events until we have a better design for them.
16075 Changes in version 0.2.2.5-alpha - 2009-10-11
16076 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
16079 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
16081 o Directory authorities:
16082 - Temporarily (just for this release) move dizum to an alternate
16086 Changes in version 0.2.2.4-alpha - 2009-10-10
16087 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
16088 introduces a new unit test framework, shifts directry authority
16089 addresses around to reduce the impact from recent blocking events,
16090 and fixes a few smaller bugs.
16093 - Fix several more asserts in the circuit_build_times code, for
16094 example one that causes Tor to fail to start once we have
16095 accumulated 5000 build times in the state file. Bugfixes on
16096 0.2.2.2-alpha; fixes bug 1108.
16098 o New directory authorities:
16099 - Move moria1 and Tonga to alternate IP addresses.
16102 - Log SSL state transitions at debug level during handshake, and
16103 include SSL states in error messages. This may help debug future
16104 SSL handshake issues.
16105 - Add a new "Handshake" log domain for activities that happen
16106 during the TLS handshake.
16107 - Revert to the "June 3 2009" ip-to-country file. The September one
16108 seems to have removed most US IP addresses.
16109 - Directory authorities now reject Tor relays with versions less than
16110 0.1.2.14. This step cuts out four relays from the current network,
16111 none of which are very big.
16114 - Fix a couple of smaller issues with gathering statistics. Bugfixes
16116 - Fix two memory leaks in the error case of
16117 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
16118 - Don't count one-hop circuits when we're estimating how long it
16119 takes circuits to build on average. Otherwise we'll set our circuit
16120 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
16121 - Directory authorities no longer change their opinion of, or vote on,
16122 whether a router is Running, unless they have themselves been
16123 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
16126 o Code simplifications and refactoring:
16127 - Revise our unit tests to use the "tinytest" framework, so we
16128 can run tests in their own processes, have smarter setup/teardown
16129 code, and so on. The unit test code has moved to its own
16130 subdirectory, and has been split into multiple modules.
16133 Changes in version 0.2.2.3-alpha - 2009-09-23
16134 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
16137 - Fix an overzealous assert in our new circuit build timeout code.
16138 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
16141 - If the networkstatus consensus tells us that we should use a
16142 negative circuit package window, ignore it. Otherwise we'll
16143 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
16146 Changes in version 0.2.2.2-alpha - 2009-09-21
16147 Tor 0.2.2.2-alpha introduces our latest performance improvement for
16148 clients: Tor tracks the average time it takes to build a circuit, and
16149 avoids using circuits that take too long to build. For fast connections,
16150 this feature can cut your expected latency in half. For slow or flaky
16151 connections, it could ruin your Tor experience. Let us know if it does!
16154 - Tor now tracks how long it takes to build client-side circuits
16155 over time, and adapts its timeout to local network performance.
16156 Since a circuit that takes a long time to build will also provide
16157 bad performance, we get significant latency improvements by
16158 discarding the slowest 20% of circuits. Specifically, Tor creates
16159 circuits more aggressively than usual until it has enough data
16160 points for a good timeout estimate. Implements proposal 151.
16161 We are especially looking for reports (good and bad) from users with
16162 both EDGE and broadband connections that can move from broadband
16163 to EDGE and find out if the build-time data in the .tor/state gets
16164 reset without loss of Tor usability. You should also see a notice
16165 log message telling you that Tor has reset its timeout.
16166 - Directory authorities can now vote on arbitary integer values as
16167 part of the consensus process. This is designed to help set
16168 network-wide parameters. Implements proposal 167.
16169 - Tor now reads the "circwindow" parameter out of the consensus,
16170 and uses that value for its circuit package window rather than the
16171 default of 1000 cells. Begins the implementation of proposal 168.
16174 - Fix a remotely triggerable memory leak when a consensus document
16175 contains more than one signature from the same voter. Bugfix on
16179 - Fix an extremely rare infinite recursion bug that could occur if
16180 we tried to log a message after shutting down the log subsystem.
16181 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
16182 - Fix parsing for memory or time units given without a space between
16183 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
16184 - A networkstatus vote must contain exactly one signature. Spec
16185 conformance issue. Bugfix on 0.2.0.3-alpha.
16186 - Fix an obscure bug where hidden services on 64-bit big-endian
16187 systems might mis-read the timestamp in v3 introduce cells, and
16188 refuse to connect back to the client. Discovered by "rotor".
16189 Bugfix on 0.2.1.6-alpha.
16190 - We were triggering a CLOCK_SKEW controller status event whenever
16191 we connect via the v2 connection protocol to any relay that has
16192 a wrong clock. Instead, we should only inform the controller when
16193 it's a trusted authority that claims our clock is wrong. Bugfix
16194 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
16195 - We were telling the controller about CHECKING_REACHABILITY and
16196 REACHABILITY_FAILED status events whenever we launch a testing
16197 circuit or notice that one has failed. Instead, only tell the
16198 controller when we want to inform the user of overall success or
16199 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
16201 - Don't warn when we're using a circuit that ends with a node
16202 excluded in ExcludeExitNodes, but the circuit is not used to access
16203 the outside world. This should help fix bug 1090, but more problems
16204 remain. Bugfix on 0.2.1.6-alpha.
16205 - Work around a small memory leak in some versions of OpenSSL that
16206 stopped the memory used by the hostname TLS extension from being
16208 - Make our 'torify' script more portable; if we have only one of
16209 'torsocks' or 'tsocks' installed, don't complain to the user;
16210 and explain our warning about tsocks better.
16213 - Add a "getinfo status/accepted-server-descriptor" controller
16214 command, which is the recommended way for controllers to learn
16215 whether our server descriptor has been successfully received by at
16216 least on directory authority. Un-recommend good-server-descriptor
16217 getinfo and status events until we have a better design for them.
16218 - Update to the "September 4 2009" ip-to-country file.
16221 Changes in version 0.2.2.1-alpha - 2009-08-26
16222 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
16223 Tor clients to bootstrap on networks where only port 80 is reachable,
16224 makes it more straightforward to support hardware crypto accelerators,
16225 and starts the groundwork for gathering stats safely at relays.
16228 - Start the process of disabling ".exit" address notation, since it
16229 can be used for a variety of esoteric application-level attacks
16230 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
16233 o New directory authorities:
16234 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
16238 - New AccelName and AccelDir options add support for dynamic OpenSSL
16239 hardware crypto acceleration engines.
16240 - Tor now supports tunneling all of its outgoing connections over
16241 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
16242 configuration options. Code by Christopher Davis.
16245 - Send circuit or stream sendme cells when our window has decreased
16246 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
16247 by Karsten when testing the "reduce circuit window" performance
16248 patch. Bugfix on the 54th commit on Tor -- from July 2002,
16249 before the release of Tor 0.0.0. This is the new winner of the
16252 o New options for gathering stats safely:
16253 - Directory mirrors that set "DirReqStatistics 1" write statistics
16254 about directory requests to disk every 24 hours. As compared to the
16255 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
16256 1) stats are written to disk exactly every 24 hours; 2) estimated
16257 shares of v2 and v3 requests are determined as mean values, not at
16258 the end of a measurement period; 3) unresolved requests are listed
16259 with country code '??'; 4) directories also measure download times.
16260 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
16261 number of exit streams and transferred bytes per port to disk every
16263 - Relays that set "CellStatistics 1" write statistics on how long
16264 cells spend in their circuit queues to disk every 24 hours.
16265 - Entry nodes that set "EntryStatistics 1" write statistics on the
16266 rough number and origins of connecting clients to disk every 24
16268 - Relays that write any of the above statistics to disk and set
16269 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
16270 their extra-info documents.
16273 - New --digests command-line switch to output the digests of the
16274 source files Tor was built with.
16275 - The "torify" script now uses torsocks where available.
16276 - The memarea code now uses a sentinel value at the end of each area
16277 to make sure nothing writes beyond the end of an area. This might
16278 help debug some conceivable causes of bug 930.
16279 - Time and memory units in the configuration file can now be set to
16280 fractional units. For example, "2.5 GB" is now a valid value for
16282 - Certain Tor clients (such as those behind check.torproject.org) may
16283 want to fetch the consensus in an extra early manner. To enable this
16284 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
16285 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
16286 as only certain clients who must have this information sooner should
16288 - Instead of adding the svn revision to the Tor version string, report
16289 the git commit (when we're building from a git checkout).
16292 - If any of the v3 certs we download are unparseable, we should
16293 actually notice the failure so we don't retry indefinitely. Bugfix
16294 on 0.2.0.x; reported by "rotator".
16295 - If the cached cert file is unparseable, warn but don't exit.
16296 - Fix possible segmentation fault on directory authorities. Bugfix on
16298 - When Tor fails to parse a descriptor of any kind, dump it to disk.
16299 Might help diagnosing bug 1051.
16301 o Deprecated and removed features:
16302 - The controller no longer accepts the old obsolete "addr-mappings/"
16303 or "unregistered-servers-" GETINFO values.
16304 - Hidden services no longer publish version 0 descriptors, and clients
16305 do not request or use version 0 descriptors. However, the old hidden
16306 service authorities still accept and serve version 0 descriptors
16307 when contacted by older hidden services/clients.
16308 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
16309 always on; using them is necessary for correct forward-compatible
16311 - Remove support for .noconnect style addresses. Nobody was using
16312 them, and they provided another avenue for detecting Tor users
16313 via application-level web tricks.
16315 o Packaging changes:
16316 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
16317 installer bundles. See
16318 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
16319 for details of what's new in Vidalia 0.2.3.
16320 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
16321 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
16322 configuration file, rather than the old Privoxy.
16323 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
16324 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
16325 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
16326 better compatibility with OS X 10.6, aka Snow Leopard.
16327 - OS X Vidalia Bundle: The multi-package installer is now replaced
16328 by a simple drag and drop to the /Applications folder. This change
16329 occurred with the upgrade to Vidalia 0.2.3.
16332 Changes in version 0.2.1.19 - 2009-07-28
16333 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
16334 services on Tor 0.2.1.3-alpha through 0.2.1.18.
16337 - Make accessing hidden services on 0.2.1.x work right again.
16338 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
16339 part of patch provided by "optimist".
16342 - When a relay/bridge is writing out its identity key fingerprint to
16343 the "fingerprint" file and to its logs, write it without spaces. Now
16344 it will look like the fingerprints in our bridges documentation,
16345 and confuse fewer users.
16348 - Relays no longer publish a new server descriptor if they change
16349 their MaxAdvertisedBandwidth config option but it doesn't end up
16350 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
16351 fixes bug 1026. Patch from Sebastian.
16352 - Avoid leaking memory every time we get a create cell but we have
16353 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
16354 fixes bug 1034. Reported by BarkerJr.
16357 Changes in version 0.2.1.18 - 2009-07-24
16358 Tor 0.2.1.18 lays the foundations for performance improvements,
16359 adds status events to help users diagnose bootstrap problems, adds
16360 optional authentication/authorization for hidden services, fixes a
16361 variety of potential anonymity problems, and includes a huge pile of
16362 other features and bug fixes.
16365 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
16368 Changes in version 0.2.1.17-rc - 2009-07-07
16369 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
16370 candidate for the 0.2.1.x series. It lays the groundwork for further
16371 client performance improvements, and also fixes a big bug with directory
16372 authorities that were causing them to assign Guard and Stable flags
16375 The Windows bundles also finally include the geoip database that we
16376 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
16377 should actually install Torbutton rather than giving you a cryptic
16378 failure message (oops).
16381 - Clients now use the bandwidth values in the consensus, rather than
16382 the bandwidth values in each relay descriptor. This approach opens
16383 the door to more accurate bandwidth estimates once the directory
16384 authorities start doing active measurements. Implements more of
16388 - When Tor clients restart after 1-5 days, they discard all their
16389 cached descriptors as too old, but they still use the cached
16390 consensus document. This approach is good for robustness, but
16391 bad for performance: since they don't know any bandwidths, they
16392 end up choosing at random rather than weighting their choice by
16393 speed. Fixed by the above feature of putting bandwidths in the
16394 consensus. Bugfix on 0.2.0.x.
16395 - Directory authorities were neglecting to mark relays down in their
16396 internal histories if the relays fall off the routerlist without
16397 ever being found unreachable. So there were relays in the histories
16398 that haven't been seen for eight months, and are listed as being
16399 up for eight months. This wreaked havoc on the "median wfu"
16400 and "median mtbf" calculations, in turn making Guard and Stable
16401 flags very wrong, hurting network performance. Fixes bugs 696 and
16402 969. Bugfix on 0.2.0.6-alpha.
16405 - Serve the DirPortFrontPage page even when we have been approaching
16406 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
16407 - The control port would close the connection before flushing long
16408 replies, such as the network consensus, if a QUIT command was issued
16409 before the reply had completed. Now, the control port flushes all
16410 pending replies before closing the connection. Also fixed a spurious
16411 warning when a QUIT command is issued after a malformed or rejected
16412 AUTHENTICATE command, but before the connection was closed. Patch
16413 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
16414 - When we can't find an intro key for a v2 hidden service descriptor,
16415 fall back to the v0 hidden service descriptor and log a bug message.
16416 Workaround for bug 1024.
16417 - Fix a log message that did not respect the SafeLogging option.
16421 - If we're a relay and we change our IP address, be more verbose
16422 about the reason that made us change. Should help track down
16423 further bugs for relays on dynamic IP addresses.
16426 Changes in version 0.2.0.35 - 2009-06-24
16428 - Avoid crashing in the presence of certain malformed descriptors.
16429 Found by lark, and by automated fuzzing.
16430 - Fix an edge case where a malicious exit relay could convince a
16431 controller that the client's DNS question resolves to an internal IP
16432 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
16435 - Finally fix the bug where dynamic-IP relays disappear when their
16436 IP address changes: directory mirrors were mistakenly telling
16437 them their old address if they asked via begin_dir, so they
16438 never got an accurate answer about their new address, so they
16439 just vanished after a day. For belt-and-suspenders, relays that
16440 don't set Address in their config now avoid using begin_dir for
16441 all direct connections. Should fix bugs 827, 883, and 900.
16442 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
16443 that would occur on some exit nodes when DNS failures and timeouts
16444 occurred in certain patterns. Fix for bug 957.
16447 - When starting with a cache over a few days old, do not leak
16448 memory for the obsolete router descriptors in it. Bugfix on
16449 0.2.0.33; fixes bug 672.
16450 - Hidden service clients didn't use a cached service descriptor that
16451 was older than 15 minutes, but wouldn't fetch a new one either,
16452 because there was already one in the cache. Now, fetch a v2
16453 descriptor unless the same descriptor was added to the cache within
16454 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
16457 Changes in version 0.2.1.16-rc - 2009-06-20
16458 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
16459 a bunch of minor bugs.
16462 - Fix an edge case where a malicious exit relay could convince a
16463 controller that the client's DNS question resolves to an internal IP
16464 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
16466 o Major performance improvements (on 0.2.0.x):
16467 - Disable and refactor some debugging checks that forced a linear scan
16468 over the whole server-side DNS cache. These accounted for over 50%
16469 of CPU time on a relatively busy exit node's gprof profile. Found
16471 - Disable some debugging checks that appeared in exit node profile
16475 - Update to the "June 3 2009" ip-to-country file.
16476 - Do not have tor-resolve automatically refuse all .onion addresses;
16477 if AutomapHostsOnResolve is set in your torrc, this will work fine.
16479 o Minor bugfixes (on 0.2.0.x):
16480 - Log correct error messages for DNS-related network errors on
16482 - Fix a race condition that could cause crashes or memory corruption
16483 when running as a server with a controller listening for log
16485 - Avoid crashing when we have a policy specified in a DirPolicy or
16486 SocksPolicy or ReachableAddresses option with ports set on it,
16487 and we re-load the policy. May fix bug 996.
16488 - Hidden service clients didn't use a cached service descriptor that
16489 was older than 15 minutes, but wouldn't fetch a new one either,
16490 because there was already one in the cache. Now, fetch a v2
16491 descriptor unless the same descriptor was added to the cache within
16492 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
16494 o Minor bugfixes (on 0.2.1.x):
16495 - Don't warn users about low port and hibernation mix when they
16496 provide a *ListenAddress directive to fix that. Bugfix on
16498 - When switching back and forth between bridge mode, do not start
16499 gathering GeoIP data until two hours have passed.
16500 - Do not complain that the user has requested an excluded node as
16501 an exit when the node is not really an exit. This could happen
16502 because the circuit was for testing, or an introduction point.
16506 Changes in version 0.2.1.15-rc - 2009-05-25
16507 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
16508 series. It fixes a major bug on fast exit relays, as well as a variety
16509 of more minor bugs.
16511 o Major bugfixes (on 0.2.0.x):
16512 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
16513 that would occur on some exit nodes when DNS failures and timeouts
16514 occurred in certain patterns. Fix for bug 957.
16516 o Minor bugfixes (on 0.2.0.x):
16517 - Actually return -1 in the error case for read_bandwidth_usage().
16518 Harmless bug, since we currently don't care about the return value
16519 anywhere. Bugfix on 0.2.0.9-alpha.
16520 - Provide a more useful log message if bug 977 (related to buffer
16521 freelists) ever reappears, and do not crash right away.
16522 - Fix an assertion failure on 64-bit platforms when we allocated
16523 memory right up to the end of a memarea, then realigned the memory
16524 one step beyond the end. Fixes a possible cause of bug 930.
16525 - Protect the count of open sockets with a mutex, so we can't
16526 corrupt it when two threads are closing or opening sockets at once.
16527 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
16528 - Don't allow a bridge to publish its router descriptor to a
16529 non-bridge directory authority. Fixes part of bug 932.
16530 - When we change to or from being a bridge, reset our counts of
16531 client usage by country. Fixes bug 932.
16532 - Fix a bug that made stream bandwidth get misreported to the
16534 - Stop using malloc_usable_size() to use more area than we had
16535 actually allocated: it was safe, but made valgrind really unhappy.
16536 - Fix a memory leak when v3 directory authorities load their keys
16537 and cert from disk. Bugfix on 0.2.0.1-alpha.
16539 o Minor bugfixes (on 0.2.1.x):
16540 - Fix use of freed memory when deciding to mark a non-addable
16541 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
16544 Changes in version 0.2.1.14-rc - 2009-04-12
16545 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
16546 series. It begins fixing some major performance problems, and also
16547 finally addresses the bug that was causing relays on dynamic IP
16548 addresses to fall out of the directory.
16551 - Clients replace entry guards that were chosen more than a few months
16552 ago. This change should significantly improve client performance,
16553 especially once more people upgrade, since relays that have been
16554 a guard for a long time are currently overloaded.
16556 o Major bugfixes (on 0.2.0):
16557 - Finally fix the bug where dynamic-IP relays disappear when their
16558 IP address changes: directory mirrors were mistakenly telling
16559 them their old address if they asked via begin_dir, so they
16560 never got an accurate answer about their new address, so they
16561 just vanished after a day. For belt-and-suspenders, relays that
16562 don't set Address in their config now avoid using begin_dir for
16563 all direct connections. Should fix bugs 827, 883, and 900.
16564 - Relays were falling out of the networkstatus consensus for
16565 part of a day if they changed their local config but the
16566 authorities discarded their new descriptor as "not sufficiently
16567 different". Now directory authorities accept a descriptor as changed
16568 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
16569 patch by Sebastian.
16570 - Avoid crashing in the presence of certain malformed descriptors.
16571 Found by lark, and by automated fuzzing.
16574 - When generating circuit events with verbose nicknames for
16575 controllers, try harder to look up nicknames for routers on a
16576 circuit. (Previously, we would look in the router descriptors we had
16577 for nicknames, but not in the consensus.) Partial fix for bug 941.
16578 - If the bridge config line doesn't specify a port, assume 443.
16579 This makes bridge lines a bit smaller and easier for users to
16581 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
16582 bytes (aka 20KB/s), to match our documentation. Also update
16583 directory authorities so they always assign the Fast flag to relays
16584 with 20KB/s of capacity. Now people running relays won't suddenly
16585 find themselves not seeing any use, if the network gets faster
16587 - Update to the "April 3 2009" ip-to-country file.
16590 - Avoid trying to print raw memory to the logs when we decide to
16591 give up on downloading a given relay descriptor. Bugfix on
16593 - In tor-resolve, when the Tor client to use is specified by
16594 <hostname>:<port>, actually use the specified port rather than
16595 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
16596 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
16597 - When starting with a cache over a few days old, do not leak
16598 memory for the obsolete router descriptors in it. Bugfix on
16600 - Avoid double-free on list of successfully uploaded hidden
16601 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
16602 - Change memarea_strndup() implementation to work even when
16603 duplicating a string at the end of a page. This bug was
16604 harmless for now, but could have meant crashes later. Fix by
16605 lark. Bugfix on 0.2.1.1-alpha.
16606 - Limit uploaded directory documents to be 16M rather than 500K.
16607 The directory authorities were refusing v3 consensus votes from
16608 other authorities, since the votes are now 504K. Fixes bug 959;
16609 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
16610 - Directory authorities should never send a 503 "busy" response to
16611 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
16615 Changes in version 0.2.1.13-alpha - 2009-03-09
16616 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
16617 cleanups. We're finally getting close to a release candidate.
16620 - Correctly update the list of which countries we exclude as
16621 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
16622 lark. Bugfix on 0.2.1.6-alpha.
16624 o Minor bugfixes (on 0.2.0.x and earlier):
16625 - Automatically detect MacOSX versions earlier than 10.4.0, and
16626 disable kqueue from inside Tor when running with these versions.
16627 We previously did this from the startup script, but that was no
16628 help to people who didn't use the startup script. Resolves bug 863.
16629 - When we had picked an exit node for a connection, but marked it as
16630 "optional", and it turned out we had no onion key for the exit,
16631 stop wanting that exit and try again. This situation may not
16632 be possible now, but will probably become feasible with proposal
16633 158. Spotted by rovv. Fixes another case of bug 752.
16634 - Clients no longer cache certificates for authorities they do not
16635 recognize. Bugfix on 0.2.0.9-alpha.
16636 - When we can't transmit a DNS request due to a network error, retry
16637 it after a while, and eventually transmit a failing response to
16638 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
16639 - If the controller claimed responsibility for a stream, but that
16640 stream never finished making its connection, it would live
16641 forever in circuit_wait state. Now we close it after SocksTimeout
16642 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
16643 - Drop begin cells to a hidden service if they come from the middle
16644 of a circuit. Patch from lark.
16645 - When we erroneously receive two EXTEND cells for the same circuit
16646 ID on the same connection, drop the second. Patch from lark.
16647 - Fix a crash that occurs on exit nodes when a nameserver request
16648 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
16649 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
16651 - Do not assume that a stack-allocated character array will be
16652 64-bit aligned on platforms that demand that uint64_t access is
16653 aligned. Possible fix for bug 604.
16654 - Parse dates and IPv4 addresses in a locale- and libc-independent
16655 manner, to avoid platform-dependent behavior on malformed input.
16656 - Build correctly when configured to build outside the main source
16657 path. Patch from Michael Gold.
16658 - We were already rejecting relay begin cells with destination port
16659 of 0. Now also reject extend cells with destination port or address
16660 of 0. Suggested by lark.
16662 o Minor bugfixes (on 0.2.1.x):
16663 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
16664 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
16665 - If we're an exit node, scrub the IP address to which we are exiting
16666 in the logs. Bugfix on 0.2.1.8-alpha.
16669 - On Linux, use the prctl call to re-enable core dumps when the user
16671 - New controller event NEWCONSENSUS that lists the networkstatus
16672 lines for every recommended relay. Now controllers like Torflow
16673 can keep up-to-date on which relays they should be using.
16674 - Update to the "February 26 2009" ip-to-country file.
16677 Changes in version 0.2.0.34 - 2009-02-08
16678 Tor 0.2.0.34 features several more security-related fixes. You should
16679 upgrade, especially if you run an exit relay (remote crash) or a
16680 directory authority (remote infinite loop), or you're on an older
16681 (pre-XP) or not-recently-patched Windows (remote exploit).
16683 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
16684 have many known flaws, and nobody should be using them. You should
16685 upgrade. If you're using a Linux or BSD and its packages are obsolete,
16686 stop using those packages and upgrade anyway.
16689 - Fix an infinite-loop bug on handling corrupt votes under certain
16690 circumstances. Bugfix on 0.2.0.8-alpha.
16691 - Fix a temporary DoS vulnerability that could be performed by
16692 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
16693 - Avoid a potential crash on exit nodes when processing malformed
16694 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
16695 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
16696 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
16699 - Fix compilation on systems where time_t is a 64-bit integer.
16700 Patch from Matthias Drochner.
16701 - Don't consider expiring already-closed client connections. Fixes
16702 bug 893. Bugfix on 0.0.2pre20.
16705 Changes in version 0.2.1.12-alpha - 2009-02-08
16706 Tor 0.2.1.12-alpha features several more security-related fixes. You
16707 should upgrade, especially if you run an exit relay (remote crash) or
16708 a directory authority (remote infinite loop), or you're on an older
16709 (pre-XP) or not-recently-patched Windows (remote exploit). It also
16710 includes a big pile of minor bugfixes and cleanups.
16713 - Fix an infinite-loop bug on handling corrupt votes under certain
16714 circumstances. Bugfix on 0.2.0.8-alpha.
16715 - Fix a temporary DoS vulnerability that could be performed by
16716 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
16717 - Avoid a potential crash on exit nodes when processing malformed
16718 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
16721 - Let controllers actually ask for the "clients_seen" event for
16722 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
16723 reported by Matt Edman.
16724 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
16726 - Fix a bug in address parsing that was preventing bridges or hidden
16727 service targets from being at IPv6 addresses.
16728 - Solve a bug that kept hardware crypto acceleration from getting
16729 enabled when accounting was turned on. Fixes bug 907. Bugfix on
16731 - Remove a bash-ism from configure.in to build properly on non-Linux
16732 platforms. Bugfix on 0.2.1.1-alpha.
16733 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
16734 headers. Bugfix on 0.2.0.10-alpha.
16735 - Don't consider expiring already-closed client connections. Fixes
16736 bug 893. Bugfix on 0.0.2pre20.
16737 - Fix another interesting corner-case of bug 891 spotted by rovv:
16738 Previously, if two hosts had different amounts of clock drift, and
16739 one of them created a new connection with just the wrong timing,
16740 the other might decide to deprecate the new connection erroneously.
16741 Bugfix on 0.1.1.13-alpha.
16742 - Resolve a very rare crash bug that could occur when the user forced
16743 a nameserver reconfiguration during the middle of a nameserver
16744 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
16745 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
16746 Bugfix on 0.2.1.7-alpha.
16747 - If we're using bridges and our network goes away, be more willing
16748 to forgive our bridges and try again when we get an application
16749 request. Bugfix on 0.2.0.x.
16752 - Support platforms where time_t is 64 bits long. (Congratulations,
16753 NetBSD!) Patch from Matthias Drochner.
16754 - Add a 'getinfo status/clients-seen' controller command, in case
16755 controllers want to hear clients_seen events but connect late.
16758 - Disable GCC's strict alias optimization by default, to avoid the
16759 likelihood of its introducing subtle bugs whenever our code violates
16760 the letter of C99's alias rules.
16763 Changes in version 0.2.0.33 - 2009-01-21
16764 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
16765 useful to users. It also finally fixes a bug where a relay or client
16766 that's been off for many days would take a long time to bootstrap.
16768 This update also fixes an important security-related bug reported by
16769 Ilja van Sprundel. You should upgrade. (We'll send out more details
16770 about the bug once people have had some time to upgrade.)
16773 - Fix a heap-corruption bug that may be remotely triggerable on
16774 some platforms. Reported by Ilja van Sprundel.
16777 - When a stream at an exit relay is in state "resolving" or
16778 "connecting" and it receives an "end" relay cell, the exit relay
16779 would silently ignore the end cell and not close the stream. If
16780 the client never closes the circuit, then the exit relay never
16781 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
16782 reported by "wood".
16783 - When sending CREATED cells back for a given circuit, use a 64-bit
16784 connection ID to find the right connection, rather than an addr:port
16785 combination. Now that we can have multiple OR connections between
16786 the same ORs, it is no longer possible to use addr:port to uniquely
16787 identify a connection.
16788 - Bridge relays that had DirPort set to 0 would stop fetching
16789 descriptors shortly after startup, and then briefly resume
16790 after a new bandwidth test and/or after publishing a new bridge
16791 descriptor. Bridge users that try to bootstrap from them would
16792 get a recent networkstatus but would get descriptors from up to
16793 18 hours earlier, meaning most of the descriptors were obsolete
16794 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
16795 - Prevent bridge relays from serving their 'extrainfo' document
16796 to anybody who asks, now that extrainfo docs include potentially
16797 sensitive aggregated client geoip summaries. Bugfix on
16799 - If the cached networkstatus consensus is more than five days old,
16800 discard it rather than trying to use it. In theory it could be
16801 useful because it lists alternate directory mirrors, but in practice
16802 it just means we spend many minutes trying directory mirrors that
16803 are long gone from the network. Also discard router descriptors as
16804 we load them if they are more than five days old, since the onion
16805 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
16808 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
16809 could make gcc generate non-functional binary search code. Bugfix
16811 - Build correctly on platforms without socklen_t.
16812 - Compile without warnings on solaris.
16813 - Avoid potential crash on internal error during signature collection.
16814 Fixes bug 864. Patch from rovv.
16815 - Correct handling of possible malformed authority signing key
16816 certificates with internal signature types. Fixes bug 880.
16817 Bugfix on 0.2.0.3-alpha.
16818 - Fix a hard-to-trigger resource leak when logging credential status.
16820 - When we can't initialize DNS because the network is down, do not
16821 automatically stop Tor from starting. Instead, we retry failed
16822 dns_init() every 10 minutes, and change the exit policy to reject
16823 *:* until one succeeds. Fixes bug 691.
16824 - Use 64 bits instead of 32 bits for connection identifiers used with
16825 the controller protocol, to greatly reduce risk of identifier reuse.
16826 - When we're choosing an exit node for a circuit, and we have
16827 no pending streams, choose a good general exit rather than one that
16828 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
16829 - Fix another case of assuming, when a specific exit is requested,
16830 that we know more than the user about what hosts it allows.
16831 Fixes one case of bug 752. Patch from rovv.
16832 - Clip the MaxCircuitDirtiness config option to a minimum of 10
16833 seconds. Warn the user if lower values are given in the
16834 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
16835 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
16836 user if lower values are given in the configuration. Bugfix on
16837 0.1.1.17-rc. Patch by Sebastian.
16838 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
16839 the cache because we already had a v0 descriptor with the same ID.
16840 Bugfix on 0.2.0.18-alpha.
16841 - Fix a race condition when freeing keys shared between main thread
16842 and CPU workers that could result in a memory leak. Bugfix on
16843 0.1.0.1-rc. Fixes bug 889.
16844 - Send a valid END cell back when a client tries to connect to a
16845 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
16846 840. Patch from rovv.
16847 - Check which hops rendezvous stream cells are associated with to
16848 prevent possible guess-the-streamid injection attacks from
16849 intermediate hops. Fixes another case of bug 446. Based on patch
16851 - If a broken client asks a non-exit router to connect somewhere,
16852 do not even do the DNS lookup before rejecting the connection.
16853 Fixes another case of bug 619. Patch from rovv.
16854 - When a relay gets a create cell it can't decrypt (e.g. because it's
16855 using the wrong onion key), we were dropping it and letting the
16856 client time out. Now actually answer with a destroy cell. Fixes
16857 bug 904. Bugfix on 0.0.2pre8.
16859 o Minor bugfixes (hidden services):
16860 - Do not throw away existing introduction points on SIGHUP. Bugfix on
16861 0.0.6pre1. Patch by Karsten. Fixes bug 874.
16864 - Report the case where all signatures in a detached set are rejected
16865 differently than the case where there is an error handling the
16867 - When we realize that another process has modified our cached
16868 descriptors, print out a more useful error message rather than
16869 triggering an assertion. Fixes bug 885. Patch from Karsten.
16870 - Implement the 0x20 hack to better resist DNS poisoning: set the
16871 case on outgoing DNS requests randomly, and reject responses that do
16872 not match the case correctly. This logic can be disabled with the
16873 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
16874 of servers that do not reliably preserve case in replies. See
16875 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
16877 - Check DNS replies for more matching fields to better resist DNS
16879 - Never use OpenSSL compression: it wastes RAM and CPU trying to
16880 compress cells, which are basically all encrypted, compressed, or
16884 Changes in version 0.2.1.11-alpha - 2009-01-20
16885 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
16886 week it will take a long time to bootstrap again" bug. It also fixes
16887 an important security-related bug reported by Ilja van Sprundel. You
16888 should upgrade. (We'll send out more details about the bug once people
16889 have had some time to upgrade.)
16892 - Fix a heap-corruption bug that may be remotely triggerable on
16893 some platforms. Reported by Ilja van Sprundel.
16896 - Discard router descriptors as we load them if they are more than
16897 five days old. Otherwise if Tor is off for a long time and then
16898 starts with cached descriptors, it will try to use the onion
16899 keys in those obsolete descriptors when building circuits. Bugfix
16900 on 0.2.0.x. Fixes bug 887.
16903 - Try to make sure that the version of Libevent we're running with
16904 is binary-compatible with the one we built with. May address bug
16906 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
16907 for bug 905. Bugfix on 0.2.1.7-alpha.
16908 - Add a new --enable-local-appdata configuration switch to change
16909 the default location of the datadir on win32 from APPDATA to
16910 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
16911 entirely. Patch from coderman.
16914 - Make outbound DNS packets respect the OutboundBindAddress setting.
16915 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
16916 - When our circuit fails at the first hop (e.g. we get a destroy
16917 cell back), avoid using that OR connection anymore, and also
16918 tell all the one-hop directory requests waiting for it that they
16919 should fail. Bugfix on 0.2.1.3-alpha.
16920 - In the torify(1) manpage, mention that tsocks will leak your
16924 Changes in version 0.2.1.10-alpha - 2009-01-06
16925 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
16926 would make the bridge relay not so useful if it had DirPort set to 0,
16927 and one that could let an attacker learn a little bit of information
16928 about the bridge's users), and a bug that would cause your Tor relay
16929 to ignore a circuit create request it can't decrypt (rather than reply
16930 with an error). It also fixes a wide variety of other bugs.
16933 - If the cached networkstatus consensus is more than five days old,
16934 discard it rather than trying to use it. In theory it could
16935 be useful because it lists alternate directory mirrors, but in
16936 practice it just means we spend many minutes trying directory
16937 mirrors that are long gone from the network. Helps bug 887 a bit;
16939 - Bridge relays that had DirPort set to 0 would stop fetching
16940 descriptors shortly after startup, and then briefly resume
16941 after a new bandwidth test and/or after publishing a new bridge
16942 descriptor. Bridge users that try to bootstrap from them would
16943 get a recent networkstatus but would get descriptors from up to
16944 18 hours earlier, meaning most of the descriptors were obsolete
16945 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
16946 - Prevent bridge relays from serving their 'extrainfo' document
16947 to anybody who asks, now that extrainfo docs include potentially
16948 sensitive aggregated client geoip summaries. Bugfix on
16952 - New controller event "clients_seen" to report a geoip-based summary
16953 of which countries we've seen clients from recently. Now controllers
16954 like Vidalia can show bridge operators that they're actually making
16956 - Build correctly against versions of OpenSSL 0.9.8 or later built
16957 without support for deprecated functions.
16958 - Update to the "December 19 2008" ip-to-country file.
16960 o Minor bugfixes (on 0.2.0.x):
16961 - Authorities now vote for the Stable flag for any router whose
16962 weighted MTBF is at least 5 days, regardless of the mean MTBF.
16963 - Do not remove routers as too old if we do not have any consensus
16964 document. Bugfix on 0.2.0.7-alpha.
16965 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
16966 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
16967 - When an exit relay resolves a stream address to a local IP address,
16968 do not just keep retrying that same exit relay over and
16969 over. Instead, just close the stream. Addresses bug 872. Bugfix
16970 on 0.2.0.32. Patch from rovv.
16971 - If a hidden service sends us an END cell, do not consider
16972 retrying the connection; just close it. Patch from rovv.
16973 - When we made bridge authorities stop serving bridge descriptors over
16974 unencrypted links, we also broke DirPort reachability testing for
16975 bridges. So bridges with a non-zero DirPort were printing spurious
16976 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
16977 - When a relay gets a create cell it can't decrypt (e.g. because it's
16978 using the wrong onion key), we were dropping it and letting the
16979 client time out. Now actually answer with a destroy cell. Fixes
16980 bug 904. Bugfix on 0.0.2pre8.
16981 - Squeeze 2-5% out of client performance (according to oprofile) by
16982 improving the implementation of some policy-manipulation functions.
16984 o Minor bugfixes (on 0.2.1.x):
16985 - Make get_interface_address() function work properly again; stop
16986 guessing the wrong parts of our address as our address.
16987 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
16988 send on that circuit. Otherwise we might violate the proposal-110
16989 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
16991 - When we're sending non-EXTEND cells to the first hop in a circuit,
16992 for example to use an encrypted directory connection, we don't need
16993 to use RELAY_EARLY cells: the first hop knows what kind of cell
16994 it is, and nobody else can even see the cell type. Conserving
16995 RELAY_EARLY cells makes it easier to cannibalize circuits like
16997 - Stop logging nameserver addresses in reverse order.
16998 - If we are retrying a directory download slowly over and over, do
16999 not automatically give up after the 254th failure. Bugfix on
17001 - Resume reporting accurate "stream end" reasons to the local control
17002 port. They were lost in the changes for Proposal 148. Bugfix on
17005 o Deprecated and removed features:
17006 - The old "tor --version --version" command, which would print out
17007 the subversion "Id" of most of the source files, is now removed. It
17008 turned out to be less useful than we'd expected, and harder to
17011 o Code simplifications and refactoring:
17012 - Change our header file guard macros to be less likely to conflict
17013 with system headers. Adam Langley noticed that we were conflicting
17014 with log.h on Android.
17015 - Tool-assisted documentation cleanup. Nearly every function or
17016 static variable in Tor should have its own documentation now.
17019 Changes in version 0.2.1.9-alpha - 2008-12-25
17020 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
17022 o New directory authorities:
17023 - gabelmoo (the authority run by Karsten Loesing) now has a new
17027 - Never use a connection with a mismatched address to extend a
17028 circuit, unless that connection is canonical. A canonical
17029 connection is one whose address is authenticated by the router's
17030 identity key, either in a NETINFO cell or in a router descriptor.
17031 - Avoid a possible memory corruption bug when receiving hidden service
17032 descriptors. Bugfix on 0.2.1.6-alpha.
17035 - Fix a logic error that would automatically reject all but the first
17036 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
17037 part of bug 813/868. Bug spotted by coderman.
17038 - When a stream at an exit relay is in state "resolving" or
17039 "connecting" and it receives an "end" relay cell, the exit relay
17040 would silently ignore the end cell and not close the stream. If
17041 the client never closes the circuit, then the exit relay never
17042 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
17043 reported by "wood".
17044 - When we can't initialize DNS because the network is down, do not
17045 automatically stop Tor from starting. Instead, retry failed
17046 dns_init() every 10 minutes, and change the exit policy to reject
17047 *:* until one succeeds. Fixes bug 691.
17050 - Give a better error message when an overzealous init script says
17051 "sudo -u username tor --user username". Makes Bug 882 easier for
17053 - When a directory authority gives us a new guess for our IP address,
17054 log which authority we used. Hopefully this will help us debug
17055 the recent complaints about bad IP address guesses.
17056 - Detect svn revision properly when we're using git-svn.
17057 - Try not to open more than one descriptor-downloading connection
17058 to an authority at once. This should reduce load on directory
17059 authorities. Fixes bug 366.
17060 - Add cross-certification to newly generated certificates, so that
17061 a signing key is enough information to look up a certificate.
17062 Partial implementation of proposal 157.
17063 - Start serving certificates by <identity digest, signing key digest>
17064 pairs. Partial implementation of proposal 157.
17065 - Clients now never report any stream end reason except 'MISC'.
17066 Implements proposal 148.
17067 - On platforms with a maximum syslog string length, truncate syslog
17068 messages to that length ourselves, rather than relying on the
17069 system to do it for us.
17070 - Optimize out calls to time(NULL) that occur for every IO operation,
17071 or for every cell. On systems where time() is a slow syscall,
17072 this fix will be slightly helpful.
17073 - Exit servers can now answer resolve requests for ip6.arpa addresses.
17074 - When we download a descriptor that we then immediately (as
17075 a directory authority) reject, do not retry downloading it right
17076 away. Should save some bandwidth on authorities. Fix for bug
17077 888. Patch by Sebastian Hahn.
17078 - When a download gets us zero good descriptors, do not notify
17079 Tor that new directory information has arrived.
17080 - Avoid some nasty corner cases in the logic for marking connections
17081 as too old or obsolete or noncanonical for circuits. Partial
17084 o Minor features (controller):
17085 - New CONSENSUS_ARRIVED event to note when a new consensus has
17086 been fetched and validated.
17087 - When we realize that another process has modified our cached
17088 descriptors file, print out a more useful error message rather
17089 than triggering an assertion. Fixes bug 885. Patch from Karsten.
17090 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
17091 controllers to prevent SIGHUP from reloading the
17092 configuration. Fixes bug 856.
17095 - Resume using the correct "REASON=" stream when telling the
17096 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
17097 - When a canonical connection appears later in our internal list
17098 than a noncanonical one for a given OR ID, always use the
17099 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
17101 - Clip the MaxCircuitDirtiness config option to a minimum of 10
17102 seconds. Warn the user if lower values are given in the
17103 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
17104 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
17105 user if lower values are given in the configuration. Bugfix on
17106 0.1.1.17-rc. Patch by Sebastian.
17107 - Fix a race condition when freeing keys shared between main thread
17108 and CPU workers that could result in a memory leak. Bugfix on
17109 0.1.0.1-rc. Fixes bug 889.
17111 o Minor bugfixes (hidden services):
17112 - Do not throw away existing introduction points on SIGHUP (bugfix on
17113 0.0.6pre1); also, do not stall hidden services because we're
17114 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
17115 by John Brooks. Patch by Karsten. Fixes bug 874.
17116 - Fix a memory leak when we decline to add a v2 rendezvous
17117 descriptor to the cache because we already had a v0 descriptor
17118 with the same ID. Bugfix on 0.2.0.18-alpha.
17120 o Deprecated and removed features:
17121 - RedirectExits has been removed. It was deprecated since
17123 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
17124 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
17125 - Cell pools are now always enabled; --disable-cell-pools is ignored.
17127 o Code simplifications and refactoring:
17128 - Rename the confusing or_is_obsolete field to the more appropriate
17129 is_bad_for_new_circs, and move it to or_connection_t where it
17131 - Move edge-only flags from connection_t to edge_connection_t: not
17132 only is this better coding, but on machines of plausible alignment,
17133 it should save 4-8 bytes per connection_t. "Every little bit helps."
17134 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
17135 for consistency; keep old option working for backward compatibility.
17136 - Simplify the code for finding connections to use for a circuit.
17139 Changes in version 0.2.1.8-alpha - 2008-12-08
17140 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
17141 builds better on unusual platforms like Solaris and old OS X, and
17142 fixes a variety of other issues.
17145 - New DirPortFrontPage option that takes an html file and publishes
17146 it as "/" on the DirPort. Now relay operators can provide a
17147 disclaimer without needing to set up a separate webserver. There's
17148 a sample disclaimer in contrib/tor-exit-notice.html.
17151 - When the client is choosing entry guards, now it selects at most
17152 one guard from a given relay family. Otherwise we could end up with
17153 all of our entry points into the network run by the same operator.
17154 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
17157 - Fix a DOS opportunity during the voting signature collection process
17158 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
17159 - Fix a possible segfault when establishing an exit connection. Bugfix
17163 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
17165 - Made Tor a little less aggressive about deleting expired
17166 certificates. Partial fix for bug 854.
17167 - Stop doing unaligned memory access that generated bus errors on
17168 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
17169 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
17170 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
17171 - Make USR2 log-level switch take effect immediately. Bugfix on
17173 - If one win32 nameserver fails to get added, continue adding the
17174 rest, and don't automatically fail.
17175 - Use fcntl() for locking when flock() is not available. Should fix
17176 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
17177 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
17178 could make gcc generate non-functional binary search code. Bugfix
17180 - Build correctly on platforms without socklen_t.
17181 - Avoid potential crash on internal error during signature collection.
17182 Fixes bug 864. Patch from rovv.
17183 - Do not use C's stdio library for writing to log files. This will
17184 improve logging performance by a minute amount, and will stop
17185 leaking fds when our disk is full. Fixes bug 861.
17186 - Stop erroneous use of O_APPEND in cases where we did not in fact
17187 want to re-seek to the end of a file before every last write().
17188 - Correct handling of possible malformed authority signing key
17189 certificates with internal signature types. Fixes bug 880. Bugfix
17191 - Fix a hard-to-trigger resource leak when logging credential status.
17195 - Directory mirrors no longer fetch the v1 directory or
17196 running-routers files. They are obsolete, and nobody asks for them
17197 anymore. This is the first step to making v1 authorities obsolete.
17199 o Minor features (controller):
17200 - Return circuit purposes in response to GETINFO circuit-status. Fixes
17204 Changes in version 0.2.0.32 - 2008-11-20
17205 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
17206 packages (and maybe other packages) noticed by Theo de Raadt, fixes
17207 a smaller security flaw that might allow an attacker to access local
17208 services, further improves hidden service performance, and fixes a
17209 variety of other issues.
17212 - The "User" and "Group" config options did not clear the
17213 supplementary group entries for the Tor process. The "User" option
17214 is now more robust, and we now set the groups to the specified
17215 user's primary group. The "Group" option is now ignored. For more
17216 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
17217 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
17218 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
17219 - The "ClientDNSRejectInternalAddresses" config option wasn't being
17220 consistently obeyed: if an exit relay refuses a stream because its
17221 exit policy doesn't allow it, we would remember what IP address
17222 the relay said the destination address resolves to, even if it's
17223 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
17226 - Fix a DOS opportunity during the voting signature collection process
17227 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
17229 o Major bugfixes (hidden services):
17230 - When fetching v0 and v2 rendezvous service descriptors in parallel,
17231 we were failing the whole hidden service request when the v0
17232 descriptor fetch fails, even if the v2 fetch is still pending and
17233 might succeed. Similarly, if the last v2 fetch fails, we were
17234 failing the whole hidden service request even if a v0 fetch is
17235 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
17236 - When extending a circuit to a hidden service directory to upload a
17237 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
17238 requests failed, because the router descriptor has not been
17239 downloaded yet. In these cases, do not attempt to upload the
17240 rendezvous descriptor, but wait until the router descriptor is
17241 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
17242 descriptor from a hidden service directory for which the router
17243 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
17247 - Fix several infrequent memory leaks spotted by Coverity.
17248 - When testing for libevent functions, set the LDFLAGS variable
17249 correctly. Found by Riastradh.
17250 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
17251 bootstrapping with tunneled directory connections. Bugfix on
17252 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
17253 - When asked to connect to A.B.exit:80, if we don't know the IP for A
17254 and we know that server B rejects most-but-not all connections to
17255 port 80, we would previously reject the connection. Now, we assume
17256 the user knows what they were asking for. Fixes bug 752. Bugfix
17257 on 0.0.9rc5. Diagnosed by BarkerJr.
17258 - If we overrun our per-second write limits a little, count this as
17259 having used up our write allocation for the second, and choke
17260 outgoing directory writes. Previously, we had only counted this when
17261 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
17262 Bugfix on 0.2.0.x (??).
17263 - Remove the old v2 directory authority 'lefkada' from the default
17264 list. It has been gone for many months.
17265 - Stop doing unaligned memory access that generated bus errors on
17266 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
17267 - Make USR2 log-level switch take effect immediately. Bugfix on
17270 o Minor bugfixes (controller):
17271 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
17272 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
17275 Changes in version 0.2.1.7-alpha - 2008-11-08
17276 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
17277 packages (and maybe other packages) noticed by Theo de Raadt, fixes
17278 a smaller security flaw that might allow an attacker to access local
17279 services, adds better defense against DNS poisoning attacks on exit
17280 relays, further improves hidden service performance, and fixes a
17281 variety of other issues.
17284 - The "ClientDNSRejectInternalAddresses" config option wasn't being
17285 consistently obeyed: if an exit relay refuses a stream because its
17286 exit policy doesn't allow it, we would remember what IP address
17287 the relay said the destination address resolves to, even if it's
17288 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
17289 - The "User" and "Group" config options did not clear the
17290 supplementary group entries for the Tor process. The "User" option
17291 is now more robust, and we now set the groups to the specified
17292 user's primary group. The "Group" option is now ignored. For more
17293 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
17294 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
17295 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
17296 - Do not use or believe expired v3 authority certificates. Patch
17297 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
17300 - Now NodeFamily and MyFamily config options allow spaces in
17301 identity fingerprints, so it's easier to paste them in.
17302 Suggested by Lucky Green.
17303 - Implement the 0x20 hack to better resist DNS poisoning: set the
17304 case on outgoing DNS requests randomly, and reject responses that do
17305 not match the case correctly. This logic can be disabled with the
17306 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
17307 of servers that do not reliably preserve case in replies. See
17308 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
17310 - Preserve case in replies to DNSPort requests in order to support
17311 the 0x20 hack for resisting DNS poisoning attacks.
17313 o Hidden service performance improvements:
17314 - When the client launches an introduction circuit, retry with a
17315 new circuit after 30 seconds rather than 60 seconds.
17316 - Launch a second client-side introduction circuit in parallel
17317 after a delay of 15 seconds (based on work by Christian Wilms).
17318 - Hidden services start out building five intro circuits rather
17319 than three, and when the first three finish they publish a service
17320 descriptor using those. Now we publish our service descriptor much
17321 faster after restart.
17324 - Minor fix in the warning messages when you're having problems
17325 bootstrapping; also, be more forgiving of bootstrap problems when
17326 we're still making incremental progress on a given bootstrap phase.
17327 - When we're choosing an exit node for a circuit, and we have
17328 no pending streams, choose a good general exit rather than one that
17329 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
17330 - Send a valid END cell back when a client tries to connect to a
17331 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
17332 840. Patch from rovv.
17333 - If a broken client asks a non-exit router to connect somewhere,
17334 do not even do the DNS lookup before rejecting the connection.
17335 Fixes another case of bug 619. Patch from rovv.
17336 - Fix another case of assuming, when a specific exit is requested,
17337 that we know more than the user about what hosts it allows.
17338 Fixes another case of bug 752. Patch from rovv.
17339 - Check which hops rendezvous stream cells are associated with to
17340 prevent possible guess-the-streamid injection attacks from
17341 intermediate hops. Fixes another case of bug 446. Based on patch
17343 - Avoid using a negative right-shift when comparing 32-bit
17344 addresses. Possible fix for bug 845 and bug 811.
17345 - Make the assert_circuit_ok() function work correctly on circuits that
17346 have already been marked for close.
17347 - Fix read-off-the-end-of-string error in unit tests when decoding
17348 introduction points.
17349 - Fix uninitialized size field for memory area allocation: may improve
17350 memory performance during directory parsing.
17351 - Treat duplicate certificate fetches as failures, so that we do
17352 not try to re-fetch an expired certificate over and over and over.
17353 - Do not say we're fetching a certificate when we'll in fact skip it
17354 because of a pending download.
17357 Changes in version 0.2.1.6-alpha - 2008-09-30
17358 Tor 0.2.1.6-alpha further improves performance and robustness of
17359 hidden services, starts work on supporting per-country relay selection,
17360 and fixes a variety of smaller issues.
17363 - Implement proposal 121: make it possible to build hidden services
17364 that only certain clients are allowed to connect to. This is
17365 enforced at several points, so that unauthorized clients are unable
17366 to send INTRODUCE cells to the service, or even (depending on the
17367 type of authentication) to learn introduction points. This feature
17368 raises the bar for certain kinds of active attacks against hidden
17369 services. Code by Karsten Loesing.
17370 - Relays now store and serve v2 hidden service descriptors by default,
17371 i.e., the new default value for HidServDirectoryV2 is 1. This is
17372 the last step in proposal 114, which aims to make hidden service
17373 lookups more reliable.
17374 - Start work to allow node restrictions to include country codes. The
17375 syntax to exclude nodes in a country with country code XX is
17376 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
17377 refinement to decide what config options should take priority if
17378 you ask to both use a particular node and exclude it.
17379 - Allow ExitNodes list to include IP ranges and country codes, just
17380 like the Exclude*Nodes lists. Patch from Robert Hogan.
17383 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
17384 Tor to fail to start if you had it configured to use a bridge
17385 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
17386 - When extending a circuit to a hidden service directory to upload a
17387 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
17388 requests failed, because the router descriptor had not been
17389 downloaded yet. In these cases, we now wait until the router
17390 descriptor is downloaded, and then retry. Likewise, clients
17391 now skip over a hidden service directory if they don't yet have
17392 its router descriptor, rather than futilely requesting it and
17393 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
17395 - When fetching v0 and v2 rendezvous service descriptors in parallel,
17396 we were failing the whole hidden service request when the v0
17397 descriptor fetch fails, even if the v2 fetch is still pending and
17398 might succeed. Similarly, if the last v2 fetch fails, we were
17399 failing the whole hidden service request even if a v0 fetch is
17400 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
17401 - DNS replies need to have names matching their requests, but
17402 these names should be in the questions section, not necessarily
17403 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
17406 - Update to the "September 1 2008" ip-to-country file.
17407 - Allow ports 465 and 587 in the default exit policy again. We had
17408 rejected them in 0.1.0.15, because back in 2005 they were commonly
17409 misconfigured and ended up as spam targets. We hear they are better
17410 locked down these days.
17411 - Use a lockfile to make sure that two Tor processes are not
17412 simultaneously running with the same datadir.
17413 - Serve the latest v3 networkstatus consensus via the control
17414 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
17415 - Better logging about stability/reliability calculations on directory
17417 - Drop the requirement to have an open dir port for storing and
17418 serving v2 hidden service descriptors.
17419 - Directory authorities now serve a /tor/dbg-stability.txt URL to
17420 help debug WFU and MTBF calculations.
17421 - Implement most of Proposal 152: allow specialized servers to permit
17422 single-hop circuits, and clients to use those servers to build
17423 single-hop circuits when using a specialized controller. Patch
17424 from Josh Albrecht. Resolves feature request 768.
17425 - Add a -p option to tor-resolve for specifying the SOCKS port: some
17426 people find host:port too confusing.
17427 - Make TrackHostExit mappings expire a while after their last use, not
17428 after their creation. Patch from Robert Hogan.
17429 - Provide circuit purposes along with circuit events to the controller.
17432 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
17434 - Fixed some memory leaks -- some quite frequent, some almost
17435 impossible to trigger -- based on results from Coverity.
17436 - When testing for libevent functions, set the LDFLAGS variable
17437 correctly. Found by Riastradh.
17438 - Fix an assertion bug in parsing policy-related options; possible fix
17440 - Catch and report a few more bootstrapping failure cases when Tor
17441 fails to establish a TCP connection. Cleanup on 0.2.1.x.
17442 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
17443 bootstrapping with tunneled directory connections. Bugfix on
17444 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
17445 - When asked to connect to A.B.exit:80, if we don't know the IP for A
17446 and we know that server B rejects most-but-not all connections to
17447 port 80, we would previously reject the connection. Now, we assume
17448 the user knows what they were asking for. Fixes bug 752. Bugfix
17449 on 0.0.9rc5. Diagnosed by BarkerJr.
17450 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
17451 service directories if they have no advertised dir port. Bugfix
17453 - If we overrun our per-second write limits a little, count this as
17454 having used up our write allocation for the second, and choke
17455 outgoing directory writes. Previously, we had only counted this when
17456 we had met our limits precisely. Fixes bug 824. Patch by rovv.
17457 Bugfix on 0.2.0.x (??).
17458 - Avoid a "0 divided by 0" calculation when calculating router uptime
17459 at directory authorities. Bugfix on 0.2.0.8-alpha.
17460 - Make DNS resolved controller events into "CLOSED", not
17461 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
17463 - Fix a bug where an unreachable relay would establish enough
17464 reachability testing circuits to do a bandwidth test -- if
17465 we already have a connection to the middle hop of the testing
17466 circuit, then it could establish the last hop by using the existing
17467 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
17468 circuits no longer use entry guards in 0.2.1.3-alpha.
17469 - If we have correct permissions on $datadir, we complain to stdout
17470 and fail to start. But dangerous permissions on
17471 $datadir/cached-status/ would cause us to open a log and complain
17472 there. Now complain to stdout and fail to start in both cases. Fixes
17473 bug 820, reported by seeess.
17474 - Remove the old v2 directory authority 'lefkada' from the default
17475 list. It has been gone for many months.
17477 o Code simplifications and refactoring:
17478 - Revise the connection_new functions so that a more typesafe variant
17479 exists. This will work better with Coverity, and let us find any
17480 actual mistakes we're making here.
17481 - Refactor unit testing logic so that dmalloc can be used sensibly
17482 with unit tests to check for memory leaks.
17483 - Move all hidden-service related fields from connection and circuit
17484 structure to substructures: this way they won't eat so much memory.
17487 Changes in version 0.2.0.31 - 2008-09-03
17488 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
17489 a big bug we're seeing where in rare cases traffic from one Tor stream
17490 gets mixed into another stream, and fixes a variety of smaller issues.
17493 - Make sure that two circuits can never exist on the same connection
17494 with the same circuit ID, even if one is marked for close. This
17495 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
17496 - Relays now reject risky extend cells: if the extend cell includes
17497 a digest of all zeroes, or asks to extend back to the relay that
17498 sent the extend cell, tear down the circuit. Ideas suggested
17500 - If not enough of our entry guards are available so we add a new
17501 one, we might use the new one even if it overlapped with the
17502 current circuit's exit relay (or its family). Anonymity bugfix
17503 pointed out by rovv.
17506 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
17507 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
17508 - Correctly detect the presence of the linux/netfilter_ipv4.h header
17509 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
17510 - Pick size of default geoip filename string correctly on windows.
17511 Fixes bug 806. Bugfix on 0.2.0.30.
17512 - Make the autoconf script accept the obsolete --with-ssl-dir
17513 option as an alias for the actually-working --with-openssl-dir
17514 option. Fix the help documentation to recommend --with-openssl-dir.
17515 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
17516 - When using the TransPort option on OpenBSD, and using the User
17517 option to change UID and drop privileges, make sure to open
17518 /dev/pf before dropping privileges. Fixes bug 782. Patch from
17519 Christopher Davis. Bugfix on 0.1.2.1-alpha.
17520 - Try to attach connections immediately upon receiving a RENDEZVOUS2
17521 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
17522 on the client side when connecting to a hidden service. Bugfix
17523 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
17524 - When closing an application-side connection because its circuit is
17525 getting torn down, generate the stream event correctly. Bugfix on
17526 0.1.2.x. Anonymous patch.
17529 Changes in version 0.2.1.5-alpha - 2008-08-31
17530 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
17531 in a lot of the infrastructure for adding authorization to hidden
17532 services, lays the groundwork for having clients read their load
17533 balancing information out of the networkstatus consensus rather than
17534 the individual router descriptors, addresses two potential anonymity
17535 issues, and fixes a variety of smaller issues.
17538 - Convert many internal address representations to optionally hold
17540 - Generate and accept IPv6 addresses in many protocol elements.
17541 - Make resolver code handle nameservers located at ipv6 addresses.
17542 - Begin implementation of proposal 121 ("Client authorization for
17543 hidden services"): configure hidden services with client
17544 authorization, publish descriptors for them, and configure
17545 authorization data for hidden services at clients. The next
17546 step is to actually access hidden services that perform client
17548 - More progress toward proposal 141: Network status consensus
17549 documents and votes now contain bandwidth information for each
17550 router and a summary of that router's exit policy. Eventually this
17551 will be used by clients so that they do not have to download every
17552 known descriptor before building circuits.
17554 o Major bugfixes (on 0.2.0.x and before):
17555 - When sending CREATED cells back for a given circuit, use a 64-bit
17556 connection ID to find the right connection, rather than an addr:port
17557 combination. Now that we can have multiple OR connections between
17558 the same ORs, it is no longer possible to use addr:port to uniquely
17559 identify a connection.
17560 - Relays now reject risky extend cells: if the extend cell includes
17561 a digest of all zeroes, or asks to extend back to the relay that
17562 sent the extend cell, tear down the circuit. Ideas suggested
17564 - If not enough of our entry guards are available so we add a new
17565 one, we might use the new one even if it overlapped with the
17566 current circuit's exit relay (or its family). Anonymity bugfix
17567 pointed out by rovv.
17570 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
17571 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
17572 - When using the TransPort option on OpenBSD, and using the User
17573 option to change UID and drop privileges, make sure to open /dev/pf
17574 before dropping privileges. Fixes bug 782. Patch from Christopher
17575 Davis. Bugfix on 0.1.2.1-alpha.
17576 - Correctly detect the presence of the linux/netfilter_ipv4.h header
17577 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
17578 - Add a missing safe_str() call for a debug log message.
17579 - Use 64 bits instead of 32 bits for connection identifiers used with
17580 the controller protocol, to greatly reduce risk of identifier reuse.
17581 - Make the autoconf script accept the obsolete --with-ssl-dir
17582 option as an alias for the actually-working --with-openssl-dir
17583 option. Fix the help documentation to recommend --with-openssl-dir.
17584 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
17587 - Rate-limit too-many-sockets messages: when they happen, they happen
17588 a lot. Resolves bug 748.
17589 - Resist DNS poisoning a little better by making sure that names in
17590 answer sections match.
17591 - Print the SOCKS5 error message string as well as the error code
17592 when a tor-resolve request fails. Patch from Jacob.
17595 Changes in version 0.2.1.4-alpha - 2008-08-04
17596 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
17599 - The address part of exit policies was not correctly written
17600 to router descriptors. This generated router descriptors that failed
17601 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
17603 - Tor triggered a false assert when extending a circuit to a relay
17604 but we already have a connection open to that relay. Noticed by
17605 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
17608 - Fix a hidden service logging bug: in some edge cases, the router
17609 descriptor of a previously picked introduction point becomes
17610 obsolete and we need to give up on it rather than continually
17611 complaining that it has become obsolete. Observed by xiando. Bugfix
17614 o Removed features:
17615 - Take out the TestVia config option, since it was a workaround for
17616 a bug that was fixed in Tor 0.1.1.21.
17619 Changes in version 0.2.1.3-alpha - 2008-08-03
17620 Tor 0.2.1.3-alpha implements most of the pieces to prevent
17621 infinite-length circuit attacks (see proposal 110); fixes a bug that
17622 might cause exit relays to corrupt streams they send back; allows
17623 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
17624 ExcludeExitNodes config options; and fixes a big pile of bugs.
17626 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
17627 - Send a bootstrap problem "warn" event on the first problem if the
17628 reason is NO_ROUTE (that is, our network is down).
17631 - Implement most of proposal 110: The first K cells to be sent
17632 along a circuit are marked as special "early" cells; only K "early"
17633 cells will be allowed. Once this code is universal, we can block
17634 certain kinds of DOS attack by requiring that EXTEND commands must
17635 be sent using an "early" cell.
17638 - Try to attach connections immediately upon receiving a RENDEZVOUS2
17639 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
17640 on the client side when connecting to a hidden service. Bugfix
17641 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
17642 - Ensure that two circuits can never exist on the same connection
17643 with the same circuit ID, even if one is marked for close. This
17644 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
17647 - When relays do their initial bandwidth measurement, don't limit
17648 to just our entry guards for the test circuits. Otherwise we tend
17649 to have multiple test circuits going through a single entry guard,
17650 which makes our bandwidth test less accurate. Fixes part of bug 654;
17651 patch contributed by Josh Albrecht.
17652 - Add an ExcludeExitNodes option so users can list a set of nodes
17653 that should be be excluded from the exit node position, but
17654 allowed elsewhere. Implements proposal 151.
17655 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
17656 ExcludeNodes and ExcludeExitNodes lists.
17657 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
17658 be more efficient. Formerly it was quadratic in the number of
17659 servers; now it should be linear. Fixes bug 509.
17660 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
17661 and n_conn_id_digest fields into a separate structure that's
17662 only needed when the circuit has not yet attached to an n_conn.
17665 - Change the contrib/tor.logrotate script so it makes the new
17666 logs as "_tor:_tor" rather than the default, which is generally
17667 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
17668 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
17669 warnings (occasionally), but it can also cause the compiler to
17670 eliminate error-checking code. Suggested by Peter Gutmann.
17671 - When a hidden service is giving up on an introduction point candidate
17672 that was not included in the last published rendezvous descriptor,
17673 don't reschedule publication of the next descriptor. Fixes bug 763.
17675 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
17676 HiddenServiceExcludeNodes as obsolete: they never worked properly,
17677 and nobody claims to be using them. Fixes bug 754. Bugfix on
17678 0.1.0.1-rc. Patch from Christian Wilms.
17679 - Fix a small alignment and memory-wasting bug on buffer chunks.
17682 o Minor bugfixes (controller):
17683 - When closing an application-side connection because its circuit
17684 is getting torn down, generate the stream event correctly.
17685 Bugfix on 0.1.2.x. Anonymous patch.
17687 o Removed features:
17688 - Remove all backward-compatibility code to support relays running
17689 versions of Tor so old that they no longer work at all on the
17693 Changes in version 0.2.0.30 - 2008-07-15
17695 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
17696 warnings (occasionally), but it can also cause the compiler to
17697 eliminate error-checking code. Suggested by Peter Gutmann.
17700 Changes in version 0.2.0.29-rc - 2008-07-08
17701 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
17702 hidden-service performance bugs, and fixes a bunch of smaller bugs.
17705 - If you have more than one bridge but don't know their keys,
17706 you would only launch a request for the descriptor of the first one
17707 on your list. (Tor considered launching requests for the others, but
17708 found that it already had a connection on the way for $0000...0000
17709 so it didn't open another.) Bugfix on 0.2.0.x.
17710 - If you have more than one bridge but don't know their keys, and the
17711 connection to one of the bridges failed, you would cancel all
17712 pending bridge connections. (After all, they all have the same
17713 digest.) Bugfix on 0.2.0.x.
17714 - When a hidden service was trying to establish an introduction point,
17715 and Tor had built circuits preemptively for such purposes, we
17716 were ignoring all the preemptive circuits and launching a new one
17717 instead. Bugfix on 0.2.0.14-alpha.
17718 - When a hidden service was trying to establish an introduction point,
17719 and Tor *did* manage to reuse one of the preemptively built
17720 circuits, it didn't correctly remember which one it used,
17721 so it asked for another one soon after, until there were no
17722 more preemptive circuits, at which point it launched one from
17723 scratch. Bugfix on 0.0.9.x.
17724 - Make directory servers include the X-Your-Address-Is: http header in
17725 their responses even for begin_dir conns. Now clients who only
17726 ever use begin_dir connections still have a way to learn their IP
17727 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
17730 - Fix a macro/CPP interaction that was confusing some compilers:
17731 some GCCs don't like #if/#endif pairs inside macro arguments.
17733 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
17734 Fixes bug 704; fix from Steven Murdoch.
17735 - When opening /dev/null in finish_daemonize(), do not pass the
17736 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
17737 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
17738 - Correctly detect transparent proxy support on Linux hosts that
17739 require in.h to be included before netfilter_ipv4.h. Patch
17741 - Disallow session resumption attempts during the renegotiation
17742 stage of the v2 handshake protocol. Clients should never be trying
17743 session resumption at this point, but apparently some did, in
17744 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
17745 found by Geoff Goodell.
17748 Changes in version 0.2.1.2-alpha - 2008-06-20
17749 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
17750 make it easier to set up your own private Tor network; fixes several
17751 big bugs with using more than one bridge relay; fixes a big bug with
17752 offering hidden services quickly after Tor starts; and uses a better
17753 API for reporting potential bootstrapping problems to the controller.
17756 - New TestingTorNetwork config option to allow adjustment of
17757 previously constant values that, while reasonable, could slow
17758 bootstrapping. Implements proposal 135. Patch from Karsten.
17761 - If you have more than one bridge but don't know their digests,
17762 you would only learn a request for the descriptor of the first one
17763 on your list. (Tor considered launching requests for the others, but
17764 found that it already had a connection on the way for $0000...0000
17765 so it didn't open another.) Bugfix on 0.2.0.x.
17766 - If you have more than one bridge but don't know their digests,
17767 and the connection to one of the bridges failed, you would cancel
17768 all pending bridge connections. (After all, they all have the
17769 same digest.) Bugfix on 0.2.0.x.
17770 - When establishing a hidden service, introduction points that
17771 originate from cannibalized circuits are completely ignored and not
17772 included in rendezvous service descriptors. This might be another
17773 reason for delay in making a hidden service available. Bugfix
17774 from long ago (0.0.9.x?)
17777 - Allow OpenSSL to use dynamic locks if it wants.
17778 - When building a consensus, do not include routers that are down.
17779 This will cut down 30% to 40% on consensus size. Implements
17781 - In directory authorities' approved-routers files, allow
17782 fingerprints with or without space.
17783 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
17784 controller can query our current bootstrap state in case it attaches
17785 partway through and wants to catch up.
17786 - Send an initial "Starting" bootstrap status event, so we have a
17787 state to start out in.
17790 - Asking for a conditional consensus at .../consensus/<fingerprints>
17791 would crash a dirserver if it did not already have a
17792 consensus. Bugfix on 0.2.1.1-alpha.
17793 - Clean up some macro/CPP interactions: some GCC versions don't like
17794 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
17797 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
17798 - Directory authorities shouldn't complain about bootstrapping
17799 problems just because they do a lot of reachability testing and
17800 some of the connection attempts fail.
17801 - Start sending "count" and "recommendation" key/value pairs in
17802 bootstrap problem status events, so the controller can hear about
17803 problems even before Tor decides they're worth reporting for sure.
17804 - If you're using bridges, generate "bootstrap problem" warnings
17805 as soon as you run out of working bridges, rather than waiting
17806 for ten failures -- which will never happen if you have less than
17808 - If we close our OR connection because there's been a circuit
17809 pending on it for too long, we were telling our bootstrap status
17810 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
17813 Changes in version 0.2.1.1-alpha - 2008-06-13
17814 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
17815 were making the Tor process bloat especially on Linux; makes our TLS
17816 handshake blend in better; sends "bootstrap phase" status events to
17817 the controller, so it can keep the user informed of progress (and
17818 problems) fetching directory information and establishing circuits;
17819 and adds a variety of smaller features.
17822 - More work on making our TLS handshake blend in: modify the list
17823 of ciphers advertised by OpenSSL in client mode to even more
17824 closely resemble a common web browser. We cheat a little so that
17825 we can advertise ciphers that the locally installed OpenSSL doesn't
17827 - Start sending "bootstrap phase" status events to the controller,
17828 so it can keep the user informed of progress fetching directory
17829 information and establishing circuits. Also inform the controller
17830 if we think we're stuck at a particular bootstrap phase. Implements
17832 - Resume using OpenSSL's RAND_poll() for better (and more portable)
17833 cross-platform entropy collection again. We used to use it, then
17834 stopped using it because of a bug that could crash systems that
17835 called RAND_poll when they had a lot of fds open. It looks like the
17836 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
17837 at startup, and to call RAND_poll() when we reseed later only if
17838 we have a non-buggy OpenSSL version.
17841 - When we choose to abandon a new entry guard because we think our
17842 older ones might be better, close any circuits pending on that
17843 new entry guard connection. This fix should make us recover much
17844 faster when our network is down and then comes back. Bugfix on
17845 0.1.2.8-beta; found by lodger.
17847 o Memory fixes and improvements:
17848 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
17849 to avoid unused RAM in buffer chunks and memory pools.
17850 - Speed up parsing and cut down on memory fragmentation by using
17851 stack-style allocations for parsing directory objects. Previously,
17852 this accounted for over 40% of allocations from within Tor's code
17853 on a typical directory cache.
17854 - Use a Bloom filter rather than a digest-based set to track which
17855 descriptors we need to keep around when we're cleaning out old
17856 router descriptors. This speeds up the computation significantly,
17857 and may reduce fragmentation.
17858 - Reduce the default smartlist size from 32 to 16; it turns out that
17859 most smartlists hold around 8-12 elements tops.
17860 - Make dumpstats() log the fullness and size of openssl-internal
17862 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
17863 patch to their OpenSSL, turn it on to save memory on servers. This
17864 patch will (with any luck) get included in a mainline distribution
17866 - Never use OpenSSL compression: it wastes RAM and CPU trying to
17867 compress cells, which are basically all encrypted, compressed,
17871 - Stop reloading the router list from disk for no reason when we
17872 run out of reachable directory mirrors. Once upon a time reloading
17873 it would set the 'is_running' flag back to 1 for them. It hasn't
17874 done that for a long time.
17875 - In very rare situations new hidden service descriptors were
17876 published earlier than 30 seconds after the last change to the
17877 service. (We currently think that a hidden service descriptor
17878 that's been stable for 30 seconds is worth publishing.)
17881 - Allow separate log levels to be configured for different logging
17882 domains. For example, this allows one to log all notices, warnings,
17883 or errors, plus all memory management messages of level debug or
17884 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
17885 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
17886 and stop using a warning that had become unfixably verbose under
17888 - New --hush command-line option similar to --quiet. While --quiet
17889 disables all logging to the console on startup, --hush limits the
17890 output to messages of warning and error severity.
17891 - Servers support a new URL scheme for consensus downloads that
17892 allows the client to specify which authorities are trusted.
17893 The server then only sends the consensus if the client will trust
17894 it. Otherwise a 404 error is sent back. Clients use this
17895 new scheme when the server supports it (meaning it's running
17896 0.2.1.1-alpha or later). Implements proposal 134.
17897 - New configure/torrc options (--enable-geoip-stats,
17898 DirRecordUsageByCountry) to record how many IPs we've served
17899 directory info to in each country code, how many status documents
17900 total we've sent to each country code, and what share of the total
17901 directory requests we should expect to see.
17902 - Use the TLS1 hostname extension to more closely resemble browser
17904 - Lots of new unit tests.
17905 - Add a macro to implement the common pattern of iterating through
17906 two parallel lists in lockstep.
17909 Changes in version 0.2.0.28-rc - 2008-06-13
17910 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
17911 performance bug, and fixes a bunch of smaller bugs.
17914 - Fix a bug where, when we were choosing the 'end stream reason' to
17915 put in our relay end cell that we send to the exit relay, Tor
17916 clients on Windows were sometimes sending the wrong 'reason'. The
17917 anonymity problem is that exit relays may be able to guess whether
17918 the client is running Windows, thus helping partition the anonymity
17919 set. Down the road we should stop sending reasons to exit relays,
17920 or otherwise prevent future versions of this bug.
17923 - While setting up a hidden service, some valid introduction circuits
17924 were overlooked and abandoned. This might be the reason for
17925 the long delay in making a hidden service available. Bugfix on
17929 - Update to the "June 9 2008" ip-to-country file.
17930 - Run 'make test' as part of 'make dist', so we stop releasing so
17931 many development snapshots that fail their unit tests.
17934 - When we're checking if we have enough dir info for each relay
17935 to begin establishing circuits, make sure that we actually have
17936 the descriptor listed in the consensus, not just any descriptor.
17938 - Bridge relays no longer print "xx=0" in their extrainfo document
17939 for every single country code in the geoip db. Bugfix on
17941 - Only warn when we fail to load the geoip file if we were planning to
17942 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
17943 - If we change our MaxAdvertisedBandwidth and then reload torrc,
17944 Tor won't realize it should publish a new relay descriptor. Fixes
17945 bug 688, reported by mfr. Bugfix on 0.1.2.x.
17946 - When we haven't had any application requests lately, don't bother
17947 logging that we have expired a bunch of descriptors. Bugfix
17949 - Make relay cells written on a connection count as non-padding when
17950 tracking how long a connection has been in use. Bugfix on
17951 0.2.0.1-alpha. Spotted by lodger.
17952 - Fix unit tests in 0.2.0.27-rc.
17953 - Fix compile on Windows.
17956 Changes in version 0.2.0.27-rc - 2008-06-03
17957 Tor 0.2.0.27-rc adds a few features we left out of the earlier
17958 release candidates. In particular, we now include an IP-to-country
17959 GeoIP database, so controllers can easily look up what country a
17960 given relay is in, and so bridge relays can give us some sanitized
17961 summaries about which countries are making use of bridges. (See proposal
17962 126-geoip-fetching.txt for details.)
17965 - Include an IP-to-country GeoIP file in the tarball, so bridge
17966 relays can report sanitized summaries of the usage they're seeing.
17969 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
17970 Robert Hogan. Fixes the first part of bug 681.
17971 - Make bridge authorities never serve extrainfo docs.
17972 - Add support to detect Libevent versions in the 1.4.x series
17974 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
17975 - Include a new contrib/tor-exit-notice.html file that exit relay
17976 operators can put on their website to help reduce abuse queries.
17979 - When tunneling an encrypted directory connection, and its first
17980 circuit fails, do not leave it unattached and ask the controller
17981 to deal. Fixes the second part of bug 681.
17982 - Make bridge authorities correctly expire old extrainfo documents
17986 Changes in version 0.2.0.26-rc - 2008-05-13
17987 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
17988 in Debian's OpenSSL packages. All users running any 0.2.0.x version
17989 should upgrade, whether they're running Debian or not.
17991 o Major security fixes:
17992 - Use new V3 directory authority keys on the tor26, gabelmoo, and
17993 moria1 V3 directory authorities. The old keys were generated with
17994 a vulnerable version of Debian's OpenSSL package, and must be
17995 considered compromised. Other authorities' keys were not generated
17996 with an affected version of OpenSSL.
17999 - List authority signatures as "unrecognized" based on DirServer
18000 lines, not on cert cache. Bugfix on 0.2.0.x.
18003 - Add a new V3AuthUseLegacyKey option to make it easier for
18004 authorities to change their identity keys if they have to.
18007 Changes in version 0.2.0.25-rc - 2008-04-23
18008 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
18011 - Remember to initialize threading before initializing logging.
18012 Otherwise, many BSD-family implementations will crash hard on
18013 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
18016 - Authorities correctly free policies on bad servers on
18017 exit. Fixes bug 672. Bugfix on 0.2.0.x.
18020 Changes in version 0.2.0.24-rc - 2008-04-22
18021 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
18022 v3 directory authority, makes relays with dynamic IP addresses and no
18023 DirPort notice more quickly when their IP address changes, fixes a few
18024 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
18026 o New directory authorities:
18027 - Take lefkada out of the list of v3 directory authorities, since
18028 it has been down for months.
18029 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
18033 - Detect address changes more quickly on non-directory mirror
18034 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
18036 o Minor features (security):
18037 - Reject requests for reverse-dns lookup of names that are in
18038 a private address space. Patch from lodger.
18039 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
18042 o Minor bugfixes (crashes):
18043 - Avoid a rare assert that can trigger when Tor doesn't have much
18044 directory information yet and it tries to fetch a v2 hidden
18045 service descriptor. Fixes bug 651, reported by nwf.
18046 - Initialize log mutex before initializing dmalloc. Otherwise,
18047 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
18048 - Use recursive pthread mutexes in order to avoid deadlock when
18049 logging debug-level messages to a controller. Bug spotted by nwf,
18050 bugfix on 0.2.0.16-alpha.
18052 o Minor bugfixes (resource management):
18053 - Keep address policies from leaking memory: start their refcount
18054 at 1, not 2. Bugfix on 0.2.0.16-alpha.
18055 - Free authority certificates on exit, so they don't look like memory
18056 leaks. Bugfix on 0.2.0.19-alpha.
18057 - Free static hashtables for policy maps and for TLS connections on
18058 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
18059 - Avoid allocating extra space when computing consensuses on 64-bit
18060 platforms. Bug spotted by aakova.
18062 o Minor bugfixes (misc):
18063 - Do not read the configuration file when we've only been told to
18064 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
18065 based on patch from Sebastian Hahn.
18066 - Exit relays that are used as a client can now reach themselves
18067 using the .exit notation, rather than just launching an infinite
18068 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
18069 - When attempting to open a logfile fails, tell us why.
18070 - Fix a dumb bug that was preventing us from knowing that we should
18071 preemptively build circuits to handle expected directory requests.
18072 Fixes bug 660. Bugfix on 0.1.2.x.
18073 - Warn less verbosely about clock skew from netinfo cells from
18074 untrusted sources. Fixes bug 663.
18075 - Make controller stream events for DNS requests more consistent,
18076 by adding "new stream" events for DNS requests, and removing
18077 spurious "stream closed" events" for cached reverse resolves.
18078 Patch from mwenge. Fixes bug 646.
18079 - Correctly notify one-hop connections when a circuit build has
18080 failed. Possible fix for bug 669. Found by lodger.
18083 Changes in version 0.2.0.23-rc - 2008-03-24
18084 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
18085 makes bootstrapping faster if the first directory mirror you contact
18086 is down. The bundles also include the new Vidalia 0.1.2 release.
18089 - When a tunneled directory request is made to a directory server
18090 that's down, notice after 30 seconds rather than 120 seconds. Also,
18091 fail any begindir streams that are pending on it, so they can
18092 retry elsewhere. This was causing multi-minute delays on bootstrap.
18095 Changes in version 0.2.0.22-rc - 2008-03-18
18096 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
18097 enables encrypted directory connections by default for non-relays, fixes
18098 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
18099 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
18102 - Enable encrypted directory connections by default for non-relays,
18103 so censor tools that block Tor directory connections based on their
18104 plaintext patterns will no longer work. This means Tor works in
18105 certain censored countries by default again.
18108 - Make sure servers always request certificates from clients during
18109 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
18110 - Do not enter a CPU-eating loop when a connection is closed in
18111 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
18112 diagnosed by lodger; bugfix on 0.2.0.20-rc.
18113 - Fix assertion failure that could occur when a blocked circuit
18114 became unblocked, and it had pending client DNS requests. Bugfix
18115 on 0.2.0.1-alpha. Fixes bug 632.
18117 o Minor bugfixes (on 0.1.2.x):
18118 - Generate "STATUS_SERVER" events rather than misspelled
18119 "STATUS_SEVER" events. Caught by mwenge.
18120 - When counting the number of bytes written on a TLS connection,
18121 look at the BIO actually used for writing to the network, not
18122 at the BIO used (sometimes) to buffer data for the network.
18123 Looking at different BIOs could result in write counts on the
18124 order of ULONG_MAX. Fixes bug 614.
18125 - On Windows, correctly detect errors when listing the contents of
18126 a directory. Fix from lodger.
18128 o Minor bugfixes (on 0.2.0.x):
18129 - Downgrade "sslv3 alert handshake failure" message to INFO.
18130 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
18131 left BandwidthRate and BandwidthBurst at the default, we would be
18132 silently limited by those defaults. Now raise them to match the
18133 RelayBandwidth* values.
18134 - Fix the SVK version detection logic to work correctly on a branch.
18135 - Make --enable-openbsd-malloc work correctly on Linux with alpha
18136 CPUs. Fixes bug 625.
18137 - Logging functions now check that the passed severity is sane.
18138 - Use proper log levels in the testsuite call of
18139 get_interface_address6().
18140 - When using a nonstandard malloc, do not use the platform values for
18141 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
18142 - Make the openbsd malloc code use 8k pages on alpha CPUs and
18144 - Detect mismatched page sizes when using --enable-openbsd-malloc.
18145 - Avoid double-marked-for-close warning when certain kinds of invalid
18146 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
18147 for bug 617. Bugfix on 0.2.0.1-alpha.
18148 - Make sure that the "NULL-means-reject *:*" convention is followed by
18149 all the policy manipulation functions, avoiding some possible crash
18150 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
18151 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
18152 actually works, and doesn't warn about every single reverse lookup.
18153 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
18156 - Only log guard node status when guard node status has changed.
18157 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
18158 make "INFO" 75% less verbose.
18161 Changes in version 0.2.0.21-rc - 2008-03-02
18162 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
18163 makes Tor work well with Vidalia again, fixes a rare assert bug,
18164 and fixes a pair of more minor bugs. The bundles also include Vidalia
18165 0.1.0 and Torbutton 1.1.16.
18168 - The control port should declare that it requires password auth
18169 when HashedControlSessionPassword is set too. Patch from Matt Edman;
18170 bugfix on 0.2.0.20-rc. Fixes bug 615.
18171 - Downgrade assert in connection_buckets_decrement() to a log message.
18172 This may help us solve bug 614, and in any case will make its
18173 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
18174 - We were sometimes miscounting the number of bytes read from the
18175 network, causing our rate limiting to not be followed exactly.
18176 Bugfix on 0.2.0.16-alpha. Reported by lodger.
18179 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
18180 OpenSSL versions should have been working fine. Diagnosis and patch
18181 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
18182 Bugfix on 0.2.0.20-rc.
18185 Changes in version 0.2.0.20-rc - 2008-02-24
18186 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
18187 makes more progress towards normalizing Tor's TLS handshake, makes
18188 hidden services work better again, helps relays bootstrap if they don't
18189 know their IP address, adds optional support for linking in openbsd's
18190 allocator or tcmalloc, allows really fast relays to scale past 15000
18191 sockets, and fixes a bunch of minor bugs reported by Veracode.
18194 - Enable the revised TLS handshake based on the one designed by
18195 Steven Murdoch in proposal 124, as revised in proposal 130. It
18196 includes version negotiation for OR connections as described in
18197 proposal 105. The new handshake is meant to be harder for censors
18198 to fingerprint, and it adds the ability to detect certain kinds of
18199 man-in-the-middle traffic analysis attacks. The version negotiation
18200 feature will allow us to improve Tor's link protocol more safely
18202 - Choose which bridge to use proportional to its advertised bandwidth,
18203 rather than uniformly at random. This should speed up Tor for
18204 bridge users. Also do this for people who set StrictEntryNodes.
18205 - When a TrackHostExits-chosen exit fails too many times in a row,
18206 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
18209 - Resolved problems with (re-)fetching hidden service descriptors.
18210 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
18211 and 0.2.0.19-alpha.
18212 - If we only ever used Tor for hidden service lookups or posts, we
18213 would stop building circuits and start refusing connections after
18214 24 hours, since we falsely believed that Tor was dormant. Reported
18215 by nwf; bugfix on 0.1.2.x.
18216 - Servers that don't know their own IP address should go to the
18217 authorities for their first directory fetch, even if their DirPort
18218 is off or if they don't know they're reachable yet. This will help
18219 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
18220 - When counting the number of open sockets, count not only the number
18221 of sockets we have received from the socket() call, but also
18222 the number we've gotten from accept() and socketpair(). This bug
18223 made us fail to count all sockets that we were using for incoming
18224 connections. Bugfix on 0.2.0.x.
18225 - Fix code used to find strings within buffers, when those strings
18226 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
18227 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
18228 - Add a new __HashedControlSessionPassword option for controllers
18229 to use for one-off session password hashes that shouldn't get
18230 saved to disk by SAVECONF --- Vidalia users were accumulating a
18231 pile of HashedControlPassword lines in their torrc files, one for
18232 each time they had restarted Tor and then clicked Save. Make Tor
18233 automatically convert "HashedControlPassword" to this new option but
18234 only when it's given on the command line. Partial fix for bug 586.
18236 o Minor features (performance):
18237 - Tune parameters for cell pool allocation to minimize amount of
18239 - Add OpenBSD malloc code from phk as an optional malloc
18240 replacement on Linux: some glibc libraries do very poorly
18241 with Tor's memory allocation patterns. Pass
18242 --enable-openbsd-malloc to get the replacement malloc code.
18243 - Add a --with-tcmalloc option to the configure script to link
18244 against tcmalloc (if present). Does not yet search for
18245 non-system include paths.
18246 - Stop imposing an arbitrary maximum on the number of file descriptors
18247 used for busy servers. Bug reported by Olaf Selke; patch from
18250 o Minor features (other):
18251 - When SafeLogging is disabled, log addresses along with all TLS
18253 - When building with --enable-gcc-warnings, check for whether Apple's
18254 warning "-Wshorten-64-to-32" is available.
18255 - Add a --passphrase-fd argument to the tor-gencert command for
18258 o Minor bugfixes (memory leaks and code problems):
18259 - We were leaking a file descriptor if Tor started with a zero-length
18260 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
18261 - Detect size overflow in zlib code. Reported by Justin Ferguson and
18263 - We were comparing the raw BridgePassword entry with a base64'ed
18264 version of it, when handling a "/tor/networkstatus-bridges"
18265 directory request. Now compare correctly. Noticed by Veracode.
18266 - Recover from bad tracked-since value in MTBF-history file.
18267 Should fix bug 537.
18268 - Alter the code that tries to recover from unhandled write
18269 errors, to not try to flush onto a socket that's given us
18270 unhandled errors. Bugfix on 0.1.2.x.
18271 - Make Unix controlsockets work correctly on OpenBSD. Patch from
18272 tup. Bugfix on 0.2.0.3-alpha.
18274 o Minor bugfixes (other):
18275 - If we have an extra-info document for our server, always make
18276 it available on the control port, even if we haven't gotten
18277 a copy of it from an authority yet. Patch from mwenge.
18278 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
18279 - Directory mirrors no longer include a guess at the client's IP
18280 address if the connection appears to be coming from the same /24
18281 network; it was producing too many wrong guesses.
18282 - Make the new hidden service code respect the SafeLogging setting.
18283 Bugfix on 0.2.0.x. Patch from Karsten.
18284 - When starting as an authority, do not overwrite all certificates
18285 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
18286 - If we're trying to flush the last bytes on a connection (for
18287 example, when answering a directory request), reset the
18288 time-to-give-up timeout every time we manage to write something
18289 on the socket. Bugfix on 0.1.2.x.
18290 - Change the behavior of "getinfo status/good-server-descriptor"
18291 so it doesn't return failure when any authority disappears.
18292 - Even though the man page said that "TrackHostExits ." should
18293 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
18294 - Report TLS "zero return" case as a "clean close" and "IO error"
18295 as a "close". Stop calling closes "unexpected closes": existing
18296 Tors don't use SSL_close(), so having a connection close without
18297 the TLS shutdown handshake is hardly unexpected.
18298 - Send NAMESERVER_STATUS messages for a single failed nameserver
18301 o Code simplifications and refactoring:
18302 - Remove the tor_strpartition function: its logic was confused,
18303 and it was only used for one thing that could be implemented far
18307 Changes in version 0.2.0.19-alpha - 2008-02-09
18308 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
18309 handshake, makes path selection for relays more secure and IP address
18310 guessing more robust, and generally fixes a lot of bugs in preparation
18311 for calling the 0.2.0 branch stable.
18314 - Do not include recognizeable strings in the commonname part of
18315 Tor's x509 certificates.
18318 - If we're a relay, avoid picking ourselves as an introduction point,
18319 a rendezvous point, or as the final hop for internal circuits. Bug
18320 reported by taranis and lodger. Bugfix on 0.1.2.x.
18321 - Patch from "Andrew S. Lists" to catch when we contact a directory
18322 mirror at IP address X and he says we look like we're coming from
18323 IP address X. Bugfix on 0.1.2.x.
18325 o Minor features (security):
18326 - Be more paranoid about overwriting sensitive memory on free(),
18327 as a defensive programming tactic to ensure forward secrecy.
18329 o Minor features (directory authority):
18330 - Actually validate the options passed to AuthDirReject,
18331 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
18332 - Reject router descriptors with out-of-range bandwidthcapacity or
18333 bandwidthburst values.
18335 o Minor features (controller):
18336 - Reject controller commands over 1MB in length. This keeps rogue
18337 processes from running us out of memory.
18339 o Minor features (misc):
18340 - Give more descriptive well-formedness errors for out-of-range
18341 hidden service descriptor/protocol versions.
18342 - Make memory debugging information describe more about history
18343 of cell allocation, so we can help reduce our memory use.
18345 o Deprecated features (controller):
18346 - The status/version/num-versioning and status/version/num-concurring
18347 GETINFO options are no longer useful in the v3 directory protocol:
18348 treat them as deprecated, and warn when they're used.
18351 - When our consensus networkstatus has been expired for a while, stop
18352 being willing to build circuits using it. Fixes bug 401. Bugfix
18354 - Directory caches now fetch certificates from all authorities
18355 listed in a networkstatus consensus, even when they do not
18356 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
18357 - When connecting to a bridge without specifying its key, insert
18358 the connection into the identity-to-connection map as soon as
18359 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
18360 - Detect versions of OS X where malloc_good_size() is present in the
18361 library but never actually declared. Resolves bug 587. Bugfix
18363 - Stop incorrectly truncating zlib responses to directory authority
18364 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
18365 - Stop recommending that every server operator send mail to tor-ops.
18366 Resolves bug 597. Bugfix on 0.1.2.x.
18367 - Don't trigger an assert if we start a directory authority with a
18368 private IP address (like 127.0.0.1).
18369 - Avoid possible failures when generating a directory with routers
18370 with over-long versions strings, or too many flags set. Bugfix
18372 - If an attempt to launch a DNS resolve request over the control
18373 port fails because we have overrun the limit on the number of
18374 connections, tell the controller that the request has failed.
18375 - Avoid using too little bandwidth when our clock skips a few
18376 seconds. Bugfix on 0.1.2.x.
18377 - Fix shell error when warning about missing packages in configure
18378 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
18379 - Do not become confused when receiving a spurious VERSIONS-like
18380 cell from a confused v1 client. Bugfix on 0.2.0.x.
18381 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
18382 introduction points for a hidden service have failed. Patch from
18383 Karsten Loesing. Bugfix on 0.2.0.x.
18385 o Code simplifications and refactoring:
18386 - Remove some needless generality from cpuworker code, for improved
18388 - Stop overloading the circuit_t.onionskin field for both "onionskin
18389 from a CREATE cell that we are waiting for a cpuworker to be
18390 assigned" and "onionskin from an EXTEND cell that we are going to
18391 send to an OR as soon as we are connected". Might help with bug 600.
18392 - Add an in-place version of aes_crypt() so that we can avoid doing a
18393 needless memcpy() call on each cell payload.
18396 Changes in version 0.2.0.18-alpha - 2008-01-25
18397 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
18398 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
18399 that can warn or reject connections to ports generally associated with
18400 vulnerable-plaintext protocols.
18402 o New directory authorities:
18403 - Set up dannenberg (run by CCC) as the sixth v3 directory
18407 - Fix a major memory leak when attempting to use the v2 TLS
18408 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
18409 - We accidentally enabled the under-development v2 TLS handshake
18410 code, which was causing log entries like "TLS error while
18411 renegotiating handshake". Disable it again. Resolves bug 590.
18412 - We were computing the wrong Content-Length: header for directory
18413 responses that need to be compressed on the fly, causing clients
18414 asking for those items to always fail. Bugfix on 0.2.0.x; partially
18418 - Avoid going directly to the directory authorities even if you're a
18419 relay, if you haven't found yourself reachable yet or if you've
18420 decided not to advertise your dirport yet. Addresses bug 556.
18421 - If we've gone 12 hours since our last bandwidth check, and we
18422 estimate we have less than 50KB bandwidth capacity but we could
18423 handle more, do another bandwidth test.
18424 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
18425 Tor can warn and/or refuse connections to ports commonly used with
18426 vulnerable-plaintext protocols. Currently we warn on ports 23,
18427 109, 110, and 143, but we don't reject any.
18430 - When we setconf ClientOnly to 1, close any current OR and Dir
18431 listeners. Reported by mwenge.
18432 - When we get a consensus that's been signed by more people than
18433 we expect, don't log about it; it's not a big deal. Reported
18437 - Don't answer "/tor/networkstatus-bridges" directory requests if
18438 the request isn't encrypted.
18439 - Make "ClientOnly 1" config option disable directory ports too.
18440 - Patches from Karsten Loesing to make v2 hidden services more
18441 robust: work even when there aren't enough HSDir relays available;
18442 retry when a v2 rend desc fetch fails; but don't retry if we
18443 already have a usable v0 rend desc.
18446 Changes in version 0.2.0.17-alpha - 2008-01-17
18447 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
18450 - Make the tor-gencert man page get included correctly in the tarball.
18453 Changes in version 0.2.0.16-alpha - 2008-01-17
18454 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
18455 Loesing, and generally cleans up a lot of features and minor bugs.
18457 o New directory authorities:
18458 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
18461 o Major performance improvements:
18462 - Switch our old ring buffer implementation for one more like that
18463 used by free Unix kernels. The wasted space in a buffer with 1mb
18464 of data will now be more like 8k than 1mb. The new implementation
18465 also avoids realloc();realloc(); patterns that can contribute to
18466 memory fragmentation.
18469 - Configuration files now accept C-style strings as values. This
18470 helps encode characters not allowed in the current configuration
18471 file format, such as newline or #. Addresses bug 557.
18472 - Although we fixed bug 539 (where servers would send HTTP status 503
18473 responses _and_ send a body too), there are still servers out
18474 there that haven't upgraded. Therefore, make clients parse such
18475 bodies when they receive them.
18476 - When we're not serving v2 directory information, there is no reason
18477 to actually keep any around. Remove the obsolete files and directory
18478 on startup if they are very old and we aren't going to serve them.
18480 o Minor performance improvements:
18481 - Reference-count and share copies of address policy entries; only 5%
18482 of them were actually distinct.
18483 - Never walk through the list of logs if we know that no log is
18484 interested in a given message.
18487 - When an authority has not signed a consensus, do not try to
18488 download a nonexistent "certificate with key 00000000". Bugfix
18489 on 0.2.0.x. Fixes bug 569.
18490 - Fix a rare assert error when we're closing one of our threads:
18491 use a mutex to protect the list of logs, so we never write to the
18492 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
18493 bug 575, which is kind of the revenge of bug 222.
18494 - Patch from Karsten Loesing to complain less at both the client
18495 and the relay when a relay used to have the HSDir flag but doesn't
18496 anymore, and we try to upload a hidden service descriptor.
18497 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
18499 - Do not try to download missing certificates until we have tried
18500 to check our fallback consensus. Fixes bug 583.
18501 - Make bridges round reported GeoIP stats info up to the nearest
18502 estimate, not down. Now we can distinguish between "0 people from
18503 this country" and "1 person from this country".
18504 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
18505 - Avoid possible segfault if key generation fails in
18506 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
18507 - Avoid segfault in the case where a badly behaved v2 versioning
18508 directory sends a signed networkstatus with missing client-versions.
18510 - Avoid segfaults on certain complex invocations of
18511 router_get_by_hexdigest(). Bugfix on 0.1.2.
18512 - Correct bad index on array access in parse_http_time(). Bugfix
18514 - Fix possible bug in vote generation when server versions are present
18515 but client versions are not.
18516 - Fix rare bug on REDIRECTSTREAM control command when called with no
18517 port set: it could erroneously report an error when none had
18519 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
18520 compressing large objects and find ourselves with more than 4k
18521 left over. Bugfix on 0.2.0.
18522 - Fix a small memory leak when setting up a hidden service.
18523 - Fix a few memory leaks that could in theory happen under bizarre
18525 - Fix an assert if we post a general-purpose descriptor via the
18526 control port but that descriptor isn't mentioned in our current
18527 network consensus. Bug reported by Jon McLachlan; bugfix on
18530 o Minor features (controller):
18531 - Get NS events working again. Patch from tup.
18532 - The GETCONF command now escapes and quotes configuration values
18533 that don't otherwise fit into the torrc file.
18534 - The SETCONF command now handles quoted values correctly.
18536 o Minor features (directory authorities):
18537 - New configuration options to override default maximum number of
18538 servers allowed on a single IP address. This is important for
18539 running a test network on a single host.
18540 - Actually implement the -s option to tor-gencert.
18541 - Add a manual page for tor-gencert.
18543 o Minor features (bridges):
18544 - Bridge authorities no longer serve bridge descriptors over
18545 unencrypted connections.
18547 o Minor features (other):
18548 - Add hidden services and DNSPorts to the list of things that make
18549 Tor accept that it has running ports. Change starting Tor with no
18550 ports from a fatal error to a warning; we might change it back if
18551 this turns out to confuse anybody. Fixes bug 579.
18554 Changes in version 0.1.2.19 - 2008-01-17
18555 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
18556 exit policy a little bit more conservative so it's safer to run an
18557 exit relay on a home system, and fixes a variety of smaller issues.
18560 - Exit policies now reject connections that are addressed to a
18561 relay's public (external) IP address too, unless
18562 ExitPolicyRejectPrivate is turned off. We do this because too
18563 many relays are running nearby to services that trust them based
18564 on network address.
18567 - When the clock jumps forward a lot, do not allow the bandwidth
18568 buckets to become negative. Fixes bug 544.
18569 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
18570 on every successful resolve. Reported by Mike Perry.
18571 - Purge old entries from the "rephist" database and the hidden
18572 service descriptor database even when DirPort is zero.
18573 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
18574 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
18575 crashing or mis-answering these requests.
18576 - When we decide to send a 503 response to a request for servers, do
18577 not then also send the server descriptors: this defeats the whole
18578 purpose. Fixes bug 539.
18581 - Changing the ExitPolicyRejectPrivate setting should cause us to
18582 rebuild our server descriptor.
18583 - Fix handling of hex nicknames when answering controller requests for
18584 networkstatus by name, or when deciding whether to warn about
18585 unknown routers in a config option. (Patch from mwenge.)
18586 - Fix a couple of hard-to-trigger autoconf problems that could result
18587 in really weird results on platforms whose sys/types.h files define
18588 nonstandard integer types.
18589 - Don't try to create the datadir when running --verify-config or
18590 --hash-password. Resolves bug 540.
18591 - If we were having problems getting a particular descriptor from the
18592 directory caches, and then we learned about a new descriptor for
18593 that router, we weren't resetting our failure count. Reported
18595 - Although we fixed bug 539 (where servers would send HTTP status 503
18596 responses _and_ send a body too), there are still servers out there
18597 that haven't upgraded. Therefore, make clients parse such bodies
18598 when they receive them.
18599 - Run correctly on systems where rlim_t is larger than unsigned long.
18600 This includes some 64-bit systems.
18601 - Run correctly on platforms (like some versions of OS X 10.5) where
18602 the real limit for number of open files is OPEN_FILES, not rlim_max
18603 from getrlimit(RLIMIT_NOFILES).
18604 - Avoid a spurious free on base64 failure.
18605 - Avoid segfaults on certain complex invocations of
18606 router_get_by_hexdigest().
18607 - Fix rare bug on REDIRECTSTREAM control command when called with no
18608 port set: it could erroneously report an error when none had
18612 Changes in version 0.2.0.15-alpha - 2007-12-25
18613 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
18614 features added in 0.2.0.13-alpha.
18617 - Fix several remotely triggerable asserts based on DirPort requests
18618 for a v2 or v3 networkstatus object before we were prepared. This
18619 was particularly bad for 0.2.0.13 and later bridge relays, who
18620 would never have a v2 networkstatus and would thus always crash
18621 when used. Bugfixes on 0.2.0.x.
18622 - Estimate the v3 networkstatus size more accurately, rather than
18623 estimating it at zero bytes and giving it artificially high priority
18624 compared to other directory requests. Bugfix on 0.2.0.x.
18627 - Fix configure.in logic for cross-compilation.
18628 - When we load a bridge descriptor from the cache, and it was
18629 previously unreachable, mark it as retriable so we won't just
18630 ignore it. Also, try fetching a new copy immediately. Bugfixes
18632 - The bridge GeoIP stats were counting other relays, for example
18633 self-reachability and authority-reachability tests.
18636 - Support compilation to target iPhone; patch from cjacker huang.
18637 To build for iPhone, pass the --enable-iphone option to configure.
18640 Changes in version 0.2.0.14-alpha - 2007-12-23
18642 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
18643 without a datadirectory from a previous Tor install. Reported
18645 - Fix a crash when we fetch a descriptor that turns out to be
18646 unexpected (it used to be in our networkstatus when we started
18647 fetching it, but it isn't in our current networkstatus), and we
18648 aren't using bridges. Bugfix on 0.2.0.x.
18649 - Fix a crash when accessing hidden services: it would work the first
18650 time you use a given introduction point for your service, but
18651 on subsequent requests we'd be using garbage memory. Fixed by
18652 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
18653 - Fix a crash when we load a bridge descriptor from disk but we don't
18654 currently have a Bridge line for it in our torrc. Bugfix on
18658 - If bridge authorities set BridgePassword, they will serve a
18659 snapshot of known bridge routerstatuses from their DirPort to
18660 anybody who knows that password. Unset by default.
18663 - Make the unit tests build again.
18664 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
18665 - Make PublishServerDescriptor default to 1, so the default doesn't
18666 have to change as we invent new directory protocol versions.
18667 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
18668 be included unless sys/time.h is already included. Fixes
18669 bug 553. Bugfix on 0.2.0.x.
18670 - If we receive a general-purpose descriptor and then receive an
18671 identical bridge-purpose descriptor soon after, don't discard
18672 the next one as a duplicate.
18675 - If BridgeRelay is set to 1, then the default for
18676 PublishServerDescriptor is now "bridge" rather than "v2,v3".
18677 - If the user sets RelayBandwidthRate but doesn't set
18678 RelayBandwidthBurst, then make them equal rather than erroring out.
18681 Changes in version 0.2.0.13-alpha - 2007-12-21
18682 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
18683 Goodell, fixes many more bugs, and adds a lot of infrastructure for
18686 o New directory authorities:
18687 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
18691 - Only update guard status (usable / not usable) once we have
18692 enough directory information. This was causing us to always pick
18693 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
18694 causing us to discard all our guards on startup if we hadn't been
18695 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
18696 - Purge old entries from the "rephist" database and the hidden
18697 service descriptor databases even when DirPort is zero. Bugfix
18699 - We were ignoring our RelayBandwidthRate for the first 30 seconds
18700 after opening a circuit -- even a relayed circuit. Bugfix on
18702 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
18703 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
18704 crashing or mis-answering these types of requests.
18705 - Relays were publishing their server descriptor to v1 and v2
18706 directory authorities, but they didn't try publishing to v3-only
18707 authorities. Fix this; and also stop publishing to v1 authorities.
18709 - When we were reading router descriptors from cache, we were ignoring
18710 the annotations -- so for example we were reading in bridge-purpose
18711 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
18712 - When we decided to send a 503 response to a request for servers, we
18713 were then also sending the server descriptors: this defeats the
18714 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
18717 - Bridge relays now behave like clients with respect to time
18718 intervals for downloading new consensus documents -- otherwise they
18719 stand out. Bridge users now wait until the end of the interval,
18720 so their bridge relay will be sure to have a new consensus document.
18721 - Three new config options (AlternateDirAuthority,
18722 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
18723 user selectively replace the default directory authorities by type,
18724 rather than the all-or-nothing replacement that DirServer offers.
18725 - Tor can now be configured to read a GeoIP file from disk in one
18726 of two formats. This can be used by controllers to map IP addresses
18727 to countries. Eventually, it may support exit-by-country.
18728 - When possible, bridge relays remember which countries users
18729 are coming from, and report aggregate information in their
18730 extra-info documents, so that the bridge authorities can learn
18731 where Tor is blocked.
18732 - Bridge directory authorities now do reachability testing on the
18733 bridges they know. They provide router status summaries to the
18734 controller via "getinfo ns/purpose/bridge", and also dump summaries
18735 to a file periodically.
18736 - Stop fetching directory info so aggressively if your DirPort is
18737 on but your ORPort is off; stop fetching v2 dir info entirely.
18738 You can override these choices with the new FetchDirInfoEarly
18742 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
18743 consensus documents when there are too many relays at a single
18744 IP address. Now clear it in v2 network status documents too, and
18745 also clear it in routerinfo_t when the relay is no longer listed
18746 in the relevant networkstatus document.
18747 - Don't crash if we get an unexpected value for the
18748 PublishServerDescriptor config option. Reported by Matt Edman;
18749 bugfix on 0.2.0.9-alpha.
18750 - Our new v2 hidden service descriptor format allows descriptors
18751 that have no introduction points. But Tor crashed when we tried
18752 to build a descriptor with no intro points (and it would have
18753 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
18754 by Karsten Loesing.
18755 - Fix building with dmalloc 5.5.2 with glibc.
18756 - Reject uploaded descriptors and extrainfo documents if they're
18757 huge. Otherwise we'll cache them all over the network and it'll
18758 clog everything up. Reported by Aljosha Judmayer.
18759 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
18760 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
18761 - When the DANGEROUS_VERSION controller status event told us we're
18762 running an obsolete version, it used the string "OLD" to describe
18763 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
18764 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
18765 - If we can't expand our list of entry guards (e.g. because we're
18766 using bridges or we have StrictEntryNodes set), don't mark relays
18767 down when they fail a directory request. Otherwise we're too quick
18768 to mark all our entry points down. Bugfix on 0.1.2.x.
18769 - Fix handling of hex nicknames when answering controller requests for
18770 networkstatus by name, or when deciding whether to warn about unknown
18771 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
18772 - Fix a couple of hard-to-trigger autoconf problems that could result
18773 in really weird results on platforms whose sys/types.h files define
18774 nonstandard integer types. Bugfix on 0.1.2.x.
18775 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
18776 - Don't crash on name lookup when we have no current consensus. Fixes
18777 bug 538; bugfix on 0.2.0.x.
18778 - Only Tors that want to mirror the v2 directory info should
18779 create the "cached-status" directory in their datadir. (All Tors
18780 used to create it.) Bugfix on 0.2.0.9-alpha.
18781 - Directory authorities should only automatically download Extra Info
18782 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
18785 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
18786 consumers. (We already do this on HUP.)
18787 - Authorities and caches fetch the v2 networkstatus documents
18788 less often, now that v3 is encouraged.
18789 - Add a new config option BridgeRelay that specifies you want to
18790 be a bridge relay. Right now the only difference is that it makes
18791 you answer begin_dir requests, and it makes you cache dir info,
18792 even if your DirPort isn't on.
18793 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
18794 ask about source, timestamp of arrival, purpose, etc. We need
18795 something like this to help Vidalia not do GeoIP lookups on bridge
18797 - Allow multiple HashedControlPassword config lines, to support
18798 multiple controller passwords.
18799 - Authorities now decide whether they're authoritative for a given
18800 router based on the router's purpose.
18801 - New config options AuthDirBadDir and AuthDirListBadDirs for
18802 authorities to mark certain relays as "bad directories" in the
18803 networkstatus documents. Also supports the "!baddir" directive in
18804 the approved-routers file.
18807 Changes in version 0.2.0.12-alpha - 2007-11-16
18808 This twelfth development snapshot fixes some more build problems as
18809 well as a few minor bugs.
18812 - Make it build on OpenBSD again. Patch from tup.
18813 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
18814 package-building for Red Hat, OS X, etc.
18816 o Minor bugfixes (on 0.1.2.x):
18817 - Changing the ExitPolicyRejectPrivate setting should cause us to
18818 rebuild our server descriptor.
18820 o Minor bugfixes (on 0.2.0.x):
18821 - When we're lacking a consensus, don't try to perform rendezvous
18822 operations. Reported by Karsten Loesing.
18823 - Fix a small memory leak whenever we decide against using a
18824 newly picked entry guard. Reported by Mike Perry.
18825 - When authorities detected more than two relays running on the same
18826 IP address, they were clearing all the status flags but forgetting
18827 to clear the "hsdir" flag. So clients were being told that a
18828 given relay was the right choice for a v2 hsdir lookup, yet they
18829 never had its descriptor because it was marked as 'not running'
18831 - If we're trying to fetch a bridge descriptor and there's no way
18832 the bridge authority could help us (for example, we don't know
18833 a digest, or there is no bridge authority), don't be so eager to
18834 fall back to asking the bridge authority.
18835 - If we're using bridges or have strictentrynodes set, and our
18836 chosen exit is in the same family as all our bridges/entry guards,
18837 then be flexible about families.
18840 - When we negotiate a v2 link-layer connection (not yet implemented),
18841 accept RELAY_EARLY cells and turn them into RELAY cells if we've
18842 negotiated a v1 connection for their next step. Initial code for
18846 Changes in version 0.2.0.11-alpha - 2007-11-12
18847 This eleventh development snapshot fixes some build problems with
18848 the previous snapshot. It also includes a more secure-by-default exit
18849 policy for relays, fixes an enormous memory leak for exit relays, and
18850 fixes another bug where servers were falling out of the directory list.
18853 - Exit policies now reject connections that are addressed to a
18854 relay's public (external) IP address too, unless
18855 ExitPolicyRejectPrivate is turned off. We do this because too
18856 many relays are running nearby to services that trust them based
18857 on network address. Bugfix on 0.1.2.x.
18860 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
18861 on every successful resolve. Reported by Mike Perry; bugfix
18863 - On authorities, never downgrade to old router descriptors simply
18864 because they're listed in the consensus. This created a catch-22
18865 where we wouldn't list a new descriptor because there was an
18866 old one in the consensus, and we couldn't get the new one in the
18867 consensus because we wouldn't list it. Possible fix for bug 548.
18868 Also, this might cause bug 543 to appear on authorities; if so,
18869 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
18871 o Packaging fixes on 0.2.0.10-alpha:
18872 - We were including instructions about what to do with the
18873 src/config/fallback-consensus file, but we weren't actually
18874 including it in the tarball. Disable all of that for now.
18877 - Allow people to say PreferTunnelledDirConns rather than
18878 PreferTunneledDirConns, for those alternate-spellers out there.
18881 - Don't reevaluate all the information from our consensus document
18882 just because we've downloaded a v2 networkstatus that we intend
18883 to cache. Fixes bug 545; bugfix on 0.2.0.x.
18886 Changes in version 0.2.0.10-alpha - 2007-11-10
18887 This tenth development snapshot adds a third v3 directory authority
18888 run by Mike Perry, adds most of Karsten Loesing's new hidden service
18889 descriptor format, fixes a bad crash bug and new bridge bugs introduced
18890 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
18891 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
18892 addresses many more minor issues.
18894 o New directory authorities:
18895 - Set up ides (run by Mike Perry) as the third v3 directory authority.
18898 - Allow tunnelled directory connections to ask for an encrypted
18899 "begin_dir" connection or an anonymized "uses a full Tor circuit"
18900 connection independently. Now we can make anonymized begin_dir
18901 connections for (e.g.) more secure hidden service posting and
18903 - More progress on proposal 114: code from Karsten Loesing to
18904 implement new hidden service descriptor format.
18905 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
18906 accommodate the growing number of servers that use the default
18907 and are reaching it.
18908 - Directory authorities use a new formula for selecting which nodes
18909 to advertise as Guards: they must be in the top 7/8 in terms of
18910 how long we have known about them, and above the median of those
18911 nodes in terms of weighted fractional uptime.
18912 - Make "not enough dir info yet" warnings describe *why* Tor feels
18913 it doesn't have enough directory info yet.
18916 - Stop servers from crashing if they set a Family option (or
18917 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
18919 - Make bridge users work again -- the move to v3 directories in
18920 0.2.0.9-alpha had introduced a number of bugs that made bridges
18921 no longer work for clients.
18922 - When the clock jumps forward a lot, do not allow the bandwidth
18923 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
18925 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
18926 - When the consensus lists a router descriptor that we previously were
18927 mirroring, but that we considered non-canonical, reload the
18928 descriptor as canonical. This fixes bug 543 where Tor servers
18929 would start complaining after a few days that they don't have
18930 enough directory information to build a circuit.
18931 - Consider replacing the current consensus when certificates arrive
18932 that make the pending consensus valid. Previously, we were only
18933 considering replacement when the new certs _didn't_ help.
18934 - Fix an assert error on startup if we didn't already have the
18935 consensus and certs cached in our datadirectory: we were caching
18936 the consensus in consensus_waiting_for_certs but then free'ing it
18938 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
18939 Request) if we need more v3 certs but we've already got pending
18940 requests for all of them.
18941 - Correctly back off from failing certificate downloads. Fixes
18943 - Authorities don't vote on the Running flag if they have been running
18944 for less than 30 minutes themselves. Fixes bug 547, where a newly
18945 started authority would vote that everyone was down.
18947 o New requirements:
18948 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
18949 it, it had no AES, and it hasn't seen any security patches since
18953 - Clients now hold circuitless TLS connections open for 1.5 times
18954 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
18955 rebuild a new circuit over them within that timeframe. Previously,
18956 they held them open only for KeepalivePeriod (5 minutes).
18957 - Use "If-Modified-Since" to avoid retrieving consensus
18958 networkstatuses that we already have.
18959 - When we have no consensus, check FallbackNetworkstatusFile (defaults
18960 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
18961 we start knowing some directory caches.
18962 - When we receive a consensus from the future, warn about skew.
18963 - Improve skew reporting: try to give the user a better log message
18964 about how skewed they are, and how much this matters.
18965 - When we have a certificate for an authority, believe that
18966 certificate's claims about the authority's IP address.
18967 - New --quiet command-line option to suppress the default console log.
18968 Good in combination with --hash-password.
18969 - Authorities send back an X-Descriptor-Not-New header in response to
18970 an accepted-but-discarded descriptor upload. Partially implements
18972 - Make the log message for "tls error. breaking." more useful.
18973 - Better log messages about certificate downloads, to attempt to
18974 track down the second incarnation of bug 546.
18976 o Minor features (bridges):
18977 - If bridge users set UpdateBridgesFromAuthority, but the digest
18978 they ask for is a 404 from the bridge authority, they now fall
18979 back to trying the bridge directly.
18980 - Bridges now use begin_dir to publish their server descriptor to
18981 the bridge authority, even when they haven't set TunnelDirConns.
18983 o Minor features (controller):
18984 - When reporting clock skew, and we know that the clock is _at least
18985 as skewed_ as some value, but we don't know the actual value,
18986 report the value as a "minimum skew."
18989 - Update linux-tor-prio.sh script to allow QoS based on the uid of
18990 the Tor process. Patch from Marco Bonetti with tweaks from Mike
18994 - Refuse to start if both ORPort and UseBridges are set. Bugfix
18995 on 0.2.0.x, suggested by Matt Edman.
18996 - Don't stop fetching descriptors when FetchUselessDescriptors is
18997 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
18998 reported by tup and ioerror.
18999 - Better log message on vote from unknown authority.
19000 - Don't log "Launching 0 request for 0 router" message.
19002 o Minor bugfixes (memory leaks):
19003 - Stop leaking memory every time we parse a v3 certificate. Bugfix
19005 - Stop leaking memory every time we load a v3 certificate. Bugfix
19006 on 0.2.0.1-alpha. Fixes bug 536.
19007 - Stop leaking a cached networkstatus on exit. Bugfix on
19009 - Stop leaking voter information every time we free a consensus.
19010 Bugfix on 0.2.0.3-alpha.
19011 - Stop leaking signed data every time we check a voter signature.
19012 Bugfix on 0.2.0.3-alpha.
19013 - Stop leaking a signature every time we fail to parse a consensus or
19014 a vote. Bugfix on 0.2.0.3-alpha.
19015 - Stop leaking v2_download_status_map on shutdown. Bugfix on
19017 - Stop leaking conn->nickname every time we make a connection to a
19018 Tor relay without knowing its expected identity digest (e.g. when
19019 using bridges). Bugfix on 0.2.0.3-alpha.
19021 - Minor bugfixes (portability):
19022 - Run correctly on platforms where rlim_t is larger than unsigned
19023 long, and/or where the real limit for number of open files is
19024 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
19025 particular, these may be needed for OS X 10.5.
19028 Changes in version 0.1.2.18 - 2007-10-28
19029 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
19030 hidden service introduction that were causing huge delays, and a big
19031 bug that was causing some servers to disappear from the network status
19032 lists for a few hours each day.
19034 o Major bugfixes (crashes):
19035 - If a connection is shut down abruptly because of something that
19036 happened inside connection_flushed_some(), do not call
19037 connection_finished_flushing(). Should fix bug 451:
19038 "connection_stop_writing: Assertion conn->write_event failed"
19039 Bugfix on 0.1.2.7-alpha.
19040 - Fix possible segfaults in functions called from
19041 rend_process_relay_cell().
19043 o Major bugfixes (hidden services):
19044 - Hidden services were choosing introduction points uniquely by
19045 hexdigest, but when constructing the hidden service descriptor
19046 they merely wrote the (potentially ambiguous) nickname.
19047 - Clients now use the v2 intro format for hidden service
19048 connections: they specify their chosen rendezvous point by identity
19049 digest rather than by (potentially ambiguous) nickname. These
19050 changes could speed up hidden service connections dramatically.
19052 o Major bugfixes (other):
19053 - Stop publishing a new server descriptor just because we get a
19054 HUP signal. This led (in a roundabout way) to some servers getting
19055 dropped from the networkstatus lists for a few hours each day.
19056 - When looking for a circuit to cannibalize, consider family as well
19057 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
19058 circuit cannibalization).
19059 - When a router wasn't listed in a new networkstatus, we were leaving
19060 the flags for that router alone -- meaning it remained Named,
19061 Running, etc -- even though absence from the networkstatus means
19062 that it shouldn't be considered to exist at all anymore. Now we
19063 clear all the flags for routers that fall out of the networkstatus
19064 consensus. Fixes bug 529.
19067 - Don't try to access (or alter) the state file when running
19068 --list-fingerprint or --verify-config or --hash-password. Resolves
19070 - When generating information telling us how to extend to a given
19071 router, do not try to include the nickname if it is
19072 absent. Resolves bug 467.
19073 - Fix a user-triggerable segfault in expand_filename(). (There isn't
19074 a way to trigger this remotely.)
19075 - When sending a status event to the controller telling it that an
19076 OR address is reachable, set the port correctly. (Previously we
19077 were reporting the dir port.)
19078 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
19079 command. Bugfix on 0.1.2.17.
19080 - When loading bandwidth history, do not believe any information in
19081 the future. Fixes bug 434.
19082 - When loading entry guard information, do not believe any information
19084 - When we have our clock set far in the future and generate an
19085 onion key, then re-set our clock to be correct, we should not stop
19086 the onion key from getting rotated.
19087 - On some platforms, accept() can return a broken address. Detect
19088 this more quietly, and deal accordingly. Fixes bug 483.
19089 - It's not actually an error to find a non-pending entry in the DNS
19090 cache when canceling a pending resolve. Don't log unless stuff
19091 is fishy. Resolves bug 463.
19092 - Don't reset trusted dir server list when we set a configuration
19093 option. Patch from Robert Hogan.
19094 - Don't try to create the datadir when running --verify-config or
19095 --hash-password. Resolves bug 540.
19098 Changes in version 0.2.0.9-alpha - 2007-10-24
19099 This ninth development snapshot switches clients to the new v3 directory
19100 system; allows servers to be listed in the network status even when they
19101 have the same nickname as a registered server; and fixes many other
19102 bugs including a big one that was causing some servers to disappear
19103 from the network status lists for a few hours each day.
19105 o Major features (directory system):
19106 - Clients now download v3 consensus networkstatus documents instead
19107 of v2 networkstatus documents. Clients and caches now base their
19108 opinions about routers on these consensus documents. Clients only
19109 download router descriptors listed in the consensus.
19110 - Authorities now list servers who have the same nickname as
19111 a different named server, but list them with a new flag,
19112 "Unnamed". Now we can list servers that happen to pick the same
19113 nickname as a server that registered two years ago and then
19114 disappeared. Partially implements proposal 122.
19115 - If the consensus lists a router as "Unnamed", the name is assigned
19116 to a different router: do not identify the router by that name.
19117 Partially implements proposal 122.
19118 - Authorities can now come to a consensus on which method to use to
19119 compute the consensus. This gives us forward compatibility.
19122 - Stop publishing a new server descriptor just because we HUP or
19123 when we find our DirPort to be reachable but won't actually publish
19124 it. New descriptors without any real changes are dropped by the
19125 authorities, and can screw up our "publish every 18 hours" schedule.
19127 - When a router wasn't listed in a new networkstatus, we were leaving
19128 the flags for that router alone -- meaning it remained Named,
19129 Running, etc -- even though absence from the networkstatus means
19130 that it shouldn't be considered to exist at all anymore. Now we
19131 clear all the flags for routers that fall out of the networkstatus
19132 consensus. Fixes bug 529; bugfix on 0.1.2.x.
19133 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
19134 extrainfo documents and then discard them immediately for not
19135 matching the latest router. Bugfix on 0.2.0.1-alpha.
19137 o Minor features (v3 directory protocol):
19138 - Allow tor-gencert to generate a new certificate without replacing
19140 - Allow certificates to include an address.
19141 - When we change our directory-cache settings, reschedule all voting
19142 and download operations.
19143 - Reattempt certificate downloads immediately on failure, as long as
19144 we haven't failed a threshold number of times yet.
19145 - Delay retrying consensus downloads while we're downloading
19146 certificates to verify the one we just got. Also, count getting a
19147 consensus that we already have (or one that isn't valid) as a failure,
19148 and count failing to get the certificates after 20 minutes as a
19150 - Build circuits and download descriptors even if our consensus is a
19151 little expired. (This feature will go away once authorities are
19154 o Minor features (router descriptor cache):
19155 - If we find a cached-routers file that's been sitting around for more
19156 than 28 days unmodified, then most likely it's a leftover from
19157 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
19159 - When we (as a cache) download a descriptor because it was listed
19160 in a consensus, remember when the consensus was supposed to expire,
19161 and don't expire the descriptor until then.
19163 o Minor features (performance):
19164 - Call routerlist_remove_old_routers() much less often. This should
19165 speed startup, especially on directory caches.
19166 - Don't try to launch new descriptor downloads quite so often when we
19167 already have enough directory information to build circuits.
19168 - Base64 decoding was actually showing up on our profile when parsing
19169 the initial descriptor file; switch to an in-process all-at-once
19170 implementation that's about 3.5x times faster than calling out to
19173 o Minor features (compilation):
19174 - Detect non-ASCII platforms (if any still exist) and refuse to
19175 build there: some of our code assumes that 'A' is 65 and so on.
19177 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
19178 - Make the "next period" votes into "current period" votes immediately
19179 after publishing the consensus; avoid a heisenbug that made them
19180 stick around indefinitely.
19181 - When we discard a vote as a duplicate, do not report this as
19183 - Treat missing v3 keys or certificates as an error when running as a
19184 v3 directory authority.
19185 - When we're configured to be a v3 authority, but we're only listed
19186 as a non-v3 authority in our DirServer line for ourself, correct
19188 - If an authority doesn't have a qualified hostname, just put
19189 its address in the vote. This fixes the problem where we referred to
19190 "moria on moria:9031."
19191 - Distinguish between detached signatures for the wrong period, and
19192 detached signatures for a divergent vote.
19193 - Fix a small memory leak when computing a consensus.
19194 - When there's no concensus, we were forming a vote every 30
19195 minutes, but writing the "valid-after" line in our vote based
19196 on our configured V3AuthVotingInterval: so unless the intervals
19197 matched up, we immediately rejected our own vote because it didn't
19198 start at the voting interval that caused us to construct a vote.
19200 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
19201 - Delete unverified-consensus when the real consensus is set.
19202 - Consider retrying a consensus networkstatus fetch immediately
19203 after one fails: don't wait 60 seconds to notice.
19204 - When fetching a consensus as a cache, wait until a newer consensus
19205 should exist before trying to replace the current one.
19206 - Use a more forgiving schedule for retrying failed consensus
19207 downloads than for other types.
19209 o Minor bugfixes (other directory issues):
19210 - Correct the implementation of "download votes by digest." Bugfix on
19212 - Authorities no longer send back "400 you're unreachable please fix
19213 it" errors to Tor servers that aren't online all the time. We're
19214 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
19216 o Minor bugfixes (controller):
19217 - Don't reset trusted dir server list when we set a configuration
19218 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
19219 - Respond to INT and TERM SIGNAL commands before we execute the
19220 signal, in case the signal shuts us down. We had a patch in
19221 0.1.2.1-alpha that tried to do this by queueing the response on
19222 the connection's buffer before shutting down, but that really
19223 isn't the same thing at all. Bug located by Matt Edman.
19225 o Minor bugfixes (misc):
19226 - Correctly check for bad options to the "PublishServerDescriptor"
19227 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
19228 - Stop leaking memory on failing case of base32_decode, and make
19229 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
19230 - Don't try to download extrainfo documents when we're trying to
19231 fetch enough directory info to build a circuit: having enough
19232 info should get priority. Bugfix on 0.2.0.x.
19233 - Don't complain that "your server has not managed to confirm that its
19234 ports are reachable" if we haven't been able to build any circuits
19235 yet. Bug found by spending four hours without a v3 consensus. Bugfix
19237 - Detect the reason for failing to mmap a descriptor file we just
19238 wrote, and give a more useful log message. Fixes bug 533. Bugfix
19241 o Code simplifications and refactoring:
19242 - Remove support for the old bw_accounting file: we've been storing
19243 bandwidth accounting information in the state file since
19244 0.1.2.5-alpha. This may result in bandwidth accounting errors
19245 if you try to upgrade from 0.1.1.x or earlier, or if you try to
19246 downgrade to 0.1.1.x or earlier.
19247 - New convenience code to locate a file within the DataDirectory.
19248 - Move non-authority functionality out of dirvote.c.
19249 - Refactor the arguments for router_pick_{directory_|trusteddir}server
19250 so that they all take the same named flags.
19253 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
19254 Unix users an easy way to script their Tor process (e.g. by
19255 adjusting bandwidth based on the time of the day).
19258 Changes in version 0.2.0.8-alpha - 2007-10-12
19259 This eighth development snapshot fixes a crash bug that's been bothering
19260 us since February 2007, lets bridge authorities store a list of bridge
19261 descriptors they've seen, gets v3 directory voting closer to working,
19262 starts caching v3 directory consensus documents on directory mirrors,
19263 and fixes a variety of smaller issues including some minor memory leaks.
19265 o Major features (router descriptor cache):
19266 - Store routers in a file called cached-descriptors instead of in
19267 cached-routers. Initialize cached-descriptors from cached-routers
19268 if the old format is around. The new format allows us to store
19269 annotations along with descriptors.
19270 - Use annotations to record the time we received each descriptor, its
19271 source, and its purpose.
19272 - Disable the SETROUTERPURPOSE controller command: it is now
19274 - Controllers should now specify cache=no or cache=yes when using
19275 the +POSTDESCRIPTOR command.
19276 - Bridge authorities now write bridge descriptors to disk, meaning
19277 we can export them to other programs and begin distributing them
19280 o Major features (directory authorities):
19281 - When a v3 authority is missing votes or signatures, it now tries
19283 - Directory authorities track weighted fractional uptime as well as
19284 weighted mean-time-between failures. WFU is suitable for deciding
19285 whether a node is "usually up", while MTBF is suitable for deciding
19286 whether a node is "likely to stay up." We need both, because
19287 "usually up" is a good requirement for guards, while "likely to
19288 stay up" is a good requirement for long-lived connections.
19290 o Major features (v3 directory system):
19291 - Caches now download v3 network status documents as needed,
19292 and download the descriptors listed in them.
19293 - All hosts now attempt to download and keep fresh v3 authority
19294 certificates, and re-attempt after failures.
19295 - More internal-consistency checks for vote parsing.
19297 o Major bugfixes (crashes):
19298 - If a connection is shut down abruptly because of something that
19299 happened inside connection_flushed_some(), do not call
19300 connection_finished_flushing(). Should fix bug 451. Bugfix on
19303 o Major bugfixes (performance):
19304 - Fix really bad O(n^2) performance when parsing a long list of
19305 routers: Instead of searching the entire list for an "extra-info "
19306 string which usually wasn't there, once for every routerinfo
19307 we read, just scan lines forward until we find one we like.
19309 - When we add data to a write buffer in response to the data on that
19310 write buffer getting low because of a flush, do not consider the
19311 newly added data as a candidate for immediate flushing, but rather
19312 make it wait until the next round of writing. Otherwise, we flush
19313 and refill recursively, and a single greedy TLS connection can
19314 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
19316 o Minor features (v3 authority system):
19317 - Add more ways for tools to download the votes that lead to the
19319 - Send a 503 when low on bandwidth and a vote, consensus, or
19320 certificate is requested.
19321 - If-modified-since is now implemented properly for all kinds of
19322 certificate requests.
19324 o Minor bugfixes (network statuses):
19325 - Tweak the implementation of proposal 109 slightly: allow at most
19326 two Tor servers on the same IP address, except if it's the location
19327 of a directory authority, in which case allow five. Bugfix on
19330 o Minor bugfixes (controller):
19331 - When sending a status event to the controller telling it that an
19332 OR address is reachable, set the port correctly. (Previously we
19333 were reporting the dir port.) Bugfix on 0.1.2.x.
19335 o Minor bugfixes (v3 directory system):
19336 - Fix logic to look up a cert by its signing key digest. Bugfix on
19338 - Only change the reply to a vote to "OK" if it's not already
19339 set. This gets rid of annoying "400 OK" log messages, which may
19340 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
19341 - When we get a valid consensus, recompute the voting schedule.
19342 - Base the valid-after time of a vote on the consensus voting
19343 schedule, not on our preferred schedule.
19344 - Make the return values and messages from signature uploads and
19345 downloads more sensible.
19346 - Fix a memory leak when serving votes and consensus documents, and
19347 another when serving certificates.
19349 o Minor bugfixes (performance):
19350 - Use a slightly simpler string hashing algorithm (copying Python's
19351 instead of Java's) and optimize our digest hashing algorithm to take
19352 advantage of 64-bit platforms and to remove some possibly-costly
19354 - Fix a minor memory leak whenever we parse guards from our state
19355 file. Bugfix on 0.2.0.7-alpha.
19356 - Fix a minor memory leak whenever we write out a file. Bugfix on
19358 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
19359 command. Bugfix on 0.2.0.5-alpha.
19361 o Minor bugfixes (portability):
19362 - On some platforms, accept() can return a broken address. Detect
19363 this more quietly, and deal accordingly. Fixes bug 483.
19364 - Stop calling tor_strlower() on uninitialized memory in some cases.
19365 Bugfix in 0.2.0.7-alpha.
19367 o Minor bugfixes (usability):
19368 - Treat some 403 responses from directory servers as INFO rather than
19369 WARN-severity events.
19370 - It's not actually an error to find a non-pending entry in the DNS
19371 cache when canceling a pending resolve. Don't log unless stuff is
19372 fishy. Resolves bug 463.
19374 o Minor bugfixes (anonymity):
19375 - Never report that we've used more bandwidth than we're willing to
19376 relay: it leaks how much non-relay traffic we're using. Resolves
19378 - When looking for a circuit to cannibalize, consider family as well
19379 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
19380 circuit cannibalization).
19382 o Code simplifications and refactoring:
19383 - Make a bunch of functions static. Remove some dead code.
19384 - Pull out about a third of the really big routerlist.c; put it in a
19385 new module, networkstatus.c.
19386 - Merge the extra fields in local_routerstatus_t back into
19387 routerstatus_t: we used to need one routerstatus_t for each
19388 authority's opinion, plus a local_routerstatus_t for the locally
19389 computed consensus opinion. To save space, we put the locally
19390 modified fields into local_routerstatus_t, and only the common
19391 stuff into routerstatus_t. But once v3 directories are in use,
19392 clients and caches will no longer need to hold authority opinions;
19393 thus, the rationale for keeping the types separate is now gone.
19394 - Make the code used to reschedule and reattempt downloads more
19396 - Turn all 'Are we a directory server/mirror?' logic into a call to
19398 - Remove the code to generate the oldest (v1) directory format.
19399 The code has been disabled since 0.2.0.5-alpha.
19402 Changes in version 0.2.0.7-alpha - 2007-09-21
19403 This seventh development snapshot makes bridges work again, makes bridge
19404 authorities work for the first time, fixes two huge performance flaws
19405 in hidden services, and fixes a variety of minor issues.
19407 o New directory authorities:
19408 - Set up moria1 and tor26 as the first v3 directory authorities. See
19409 doc/spec/dir-spec.txt for details on the new directory design.
19411 o Major bugfixes (crashes):
19412 - Fix possible segfaults in functions called from
19413 rend_process_relay_cell(). Bugfix on 0.1.2.x.
19415 o Major bugfixes (bridges):
19416 - Fix a bug that made servers send a "404 Not found" in response to
19417 attempts to fetch their server descriptor. This caused Tor servers
19418 to take many minutes to establish reachability for their DirPort,
19419 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
19420 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
19421 users configure that and specify a bridge with an identity
19422 fingerprint, now they will lookup the bridge descriptor at the
19423 default bridge authority via a one-hop tunnel, but once circuits
19424 are established they will switch to a three-hop tunnel for later
19425 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
19427 o Major bugfixes (hidden services):
19428 - Hidden services were choosing introduction points uniquely by
19429 hexdigest, but when constructing the hidden service descriptor
19430 they merely wrote the (potentially ambiguous) nickname.
19431 - Clients now use the v2 intro format for hidden service
19432 connections: they specify their chosen rendezvous point by identity
19433 digest rather than by (potentially ambiguous) nickname. Both
19434 are bugfixes on 0.1.2.x, and they could speed up hidden service
19435 connections dramatically. Thanks to Karsten Loesing.
19437 o Minor features (security):
19438 - As a client, do not believe any server that tells us that an
19439 address maps to an internal address space.
19440 - Make it possible to enable HashedControlPassword and
19441 CookieAuthentication at the same time.
19443 o Minor features (guard nodes):
19444 - Tag every guard node in our state file with the version that
19445 we believe added it, or with our own version if we add it. This way,
19446 if a user temporarily runs an old version of Tor and then switches
19447 back to a new one, she doesn't automatically lose her guards.
19449 o Minor features (speed):
19450 - When implementing AES counter mode, update only the portions of the
19451 counter buffer that need to change, and don't keep separate
19452 network-order and host-order counters when they are the same (i.e.,
19453 on big-endian hosts.)
19455 o Minor features (controller):
19456 - Accept LF instead of CRLF on controller, since some software has a
19457 hard time generating real Internet newlines.
19458 - Add GETINFO values for the server status events
19459 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
19462 o Removed features:
19463 - Routers no longer include bandwidth-history lines in their
19464 descriptors; this information is already available in extra-info
19465 documents, and including it in router descriptors took up 60%
19466 (!) of compressed router descriptor downloads. Completes
19467 implementation of proposal 104.
19468 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
19469 and TorControl.py, as they use the old v0 controller protocol,
19470 and are obsoleted by TorFlow anyway.
19471 - Drop support for v1 rendezvous descriptors, since we never used
19472 them anyway, and the code has probably rotted by now. Based on
19473 patch from Karsten Loesing.
19474 - On OSX, stop warning the user that kqueue support in libevent is
19475 "experimental", since it seems to have worked fine for ages.
19478 - When generating information telling us how to extend to a given
19479 router, do not try to include the nickname if it is absent. Fixes
19480 bug 467. Bugfix on 0.2.0.3-alpha.
19481 - Fix a user-triggerable (but not remotely-triggerable) segfault
19482 in expand_filename(). Bugfix on 0.1.2.x.
19483 - Fix a memory leak when freeing incomplete requests from DNSPort.
19484 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
19485 - Don't try to access (or alter) the state file when running
19486 --list-fingerprint or --verify-config or --hash-password. (Resolves
19487 bug 499.) Bugfix on 0.1.2.x.
19488 - Servers used to decline to publish their DirPort if their
19489 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
19490 were below a threshold. Now they only look at BandwidthRate and
19491 RelayBandwidthRate. Bugfix on 0.1.2.x.
19492 - Remove an optimization in the AES counter-mode code that assumed
19493 that the counter never exceeded 2^68. When the counter can be set
19494 arbitrarily as an IV (as it is by Karsten's new hidden services
19495 code), this assumption no longer holds. Bugfix on 0.1.2.x.
19496 - Resume listing "AUTHORITY" flag for authorities in network status.
19497 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
19499 o Code simplifications and refactoring:
19500 - Revamp file-writing logic so we don't need to have the entire
19501 contents of a file in memory at once before we write to disk. Tor,
19503 - Turn "descriptor store" into a full-fledged type.
19504 - Move all NT services code into a separate source file.
19505 - Unify all code that computes medians, percentile elements, etc.
19506 - Get rid of a needless malloc when parsing address policies.
19509 Changes in version 0.1.2.17 - 2007-08-30
19510 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
19511 X bundles. Vidalia 0.0.14 makes authentication required for the
19512 ControlPort in the default configuration, which addresses important
19513 security risks. Everybody who uses Vidalia (or another controller)
19516 In addition, this Tor update fixes major load balancing problems with
19517 path selection, which should speed things up a lot once many people
19520 o Major bugfixes (security):
19521 - We removed support for the old (v0) control protocol. It has been
19522 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
19523 become more of a headache than it's worth.
19525 o Major bugfixes (load balancing):
19526 - When choosing nodes for non-guard positions, weight guards
19527 proportionally less, since they already have enough load. Patch
19529 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
19530 will allow fast Tor servers to get more attention.
19531 - When we're upgrading from an old Tor version, forget our current
19532 guards and pick new ones according to the new weightings. These
19533 three load balancing patches could raise effective network capacity
19534 by a factor of four. Thanks to Mike Perry for measurements.
19536 o Major bugfixes (stream expiration):
19537 - Expire not-yet-successful application streams in all cases if
19538 they've been around longer than SocksTimeout. Right now there are
19539 some cases where the stream will live forever, demanding a new
19540 circuit every 15 seconds. Fixes bug 454; reported by lodger.
19542 o Minor features (controller):
19543 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
19544 is valid before any authentication has been received. It tells
19545 a controller what kind of authentication is expected, and what
19546 protocol is spoken. Implements proposal 119.
19548 o Minor bugfixes (performance):
19549 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
19550 greatly speeding up loading cached-routers from disk on startup.
19551 - Disable sentinel-based debugging for buffer code: we squashed all
19552 the bugs that this was supposed to detect a long time ago, and now
19553 its only effect is to change our buffer sizes from nice powers of
19554 two (which platform mallocs tend to like) to values slightly over
19555 powers of two (which make some platform mallocs sad).
19557 o Minor bugfixes (misc):
19558 - If exit bandwidth ever exceeds one third of total bandwidth, then
19559 use the correct formula to weight exit nodes when choosing paths.
19560 Based on patch from Mike Perry.
19561 - Choose perfectly fairly among routers when choosing by bandwidth and
19562 weighting by fraction of bandwidth provided by exits. Previously, we
19563 would choose with only approximate fairness, and correct ourselves
19564 if we ran off the end of the list.
19565 - If we require CookieAuthentication but we fail to write the
19566 cookie file, we would warn but not exit, and end up in a state
19567 where no controller could authenticate. Now we exit.
19568 - If we require CookieAuthentication, stop generating a new cookie
19569 every time we change any piece of our config.
19570 - Refuse to start with certain directory authority keys, and
19571 encourage people using them to stop.
19572 - Terminate multi-line control events properly. Original patch
19574 - Fix a minor memory leak when we fail to find enough suitable
19575 servers to choose a circuit.
19576 - Stop leaking part of the descriptor when we run into a particularly
19577 unparseable piece of it.
19580 Changes in version 0.2.0.6-alpha - 2007-08-26
19581 This sixth development snapshot features a new Vidalia version in the
19582 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
19583 the ControlPort in the default configuration, which addresses important
19586 In addition, this snapshot fixes major load balancing problems
19587 with path selection, which should speed things up a lot once many
19588 people have upgraded. The directory authorities also use a new
19589 mean-time-between-failure approach to tracking which servers are stable,
19590 rather than just looking at the most recent uptime.
19592 o New directory authorities:
19593 - Set up Tonga as the default bridge directory authority.
19596 - Directory authorities now track servers by weighted
19597 mean-times-between-failures. When we have 4 or more days of data,
19598 use measured MTBF rather than declared uptime to decide whether
19599 to call a router Stable. Implements proposal 108.
19601 o Major bugfixes (load balancing):
19602 - When choosing nodes for non-guard positions, weight guards
19603 proportionally less, since they already have enough load. Patch
19605 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
19606 will allow fast Tor servers to get more attention.
19607 - When we're upgrading from an old Tor version, forget our current
19608 guards and pick new ones according to the new weightings. These
19609 three load balancing patches could raise effective network capacity
19610 by a factor of four. Thanks to Mike Perry for measurements.
19612 o Major bugfixes (descriptor parsing):
19613 - Handle unexpected whitespace better in malformed descriptors. Bug
19614 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
19617 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
19618 GETINFO for Torstat to use until it can switch to using extrainfos.
19619 - Optionally (if built with -DEXPORTMALLINFO) export the output
19620 of mallinfo via http, as tor/mallinfo.txt. Only accessible
19624 - Do not intermix bridge routers with controller-added
19625 routers. (Bugfix on 0.2.0.x)
19626 - Do not fail with an assert when accept() returns an unexpected
19627 address family. Addresses but does not wholly fix bug 483. (Bugfix
19629 - Let directory authorities startup even when they can't generate
19630 a descriptor immediately, e.g. because they don't know their
19632 - Stop putting the authentication cookie in a file called "0"
19633 in your working directory if you don't specify anything for the
19634 new CookieAuthFile option. Reported by Matt Edman.
19635 - Make it possible to read the PROTOCOLINFO response in a way that
19636 conforms to our control-spec. Reported by Matt Edman.
19637 - Fix a minor memory leak when we fail to find enough suitable
19638 servers to choose a circuit. Bugfix on 0.1.2.x.
19639 - Stop leaking part of the descriptor when we run into a particularly
19640 unparseable piece of it. Bugfix on 0.1.2.x.
19641 - Unmap the extrainfo cache file on exit.
19644 Changes in version 0.2.0.5-alpha - 2007-08-19
19645 This fifth development snapshot fixes compilation on Windows again;
19646 fixes an obnoxious client-side bug that slowed things down and put
19647 extra load on the network; gets us closer to using the v3 directory
19648 voting scheme; makes it easier for Tor controllers to use cookie-based
19649 authentication; and fixes a variety of other bugs.
19651 o Removed features:
19652 - Version 1 directories are no longer generated in full. Instead,
19653 authorities generate and serve "stub" v1 directories that list
19654 no servers. This will stop Tor versions 0.1.0.x and earlier from
19655 working, but (for security reasons) nobody should be running those
19658 o Major bugfixes (compilation, 0.2.0.x):
19659 - Try to fix Win32 compilation again: improve checking for IPv6 types.
19660 - Try to fix MSVC compilation: build correctly on platforms that do
19661 not define s6_addr16 or s6_addr32.
19662 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
19665 o Major bugfixes (stream expiration):
19666 - Expire not-yet-successful application streams in all cases if
19667 they've been around longer than SocksTimeout. Right now there are
19668 some cases where the stream will live forever, demanding a new
19669 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
19670 reported by lodger.
19672 o Minor features (directory servers):
19673 - When somebody requests a list of statuses or servers, and we have
19674 none of those, return a 404 rather than an empty 200.
19676 o Minor features (directory voting):
19677 - Store v3 consensus status consensuses on disk, and reload them
19680 o Minor features (security):
19681 - Warn about unsafe ControlPort configurations.
19682 - Refuse to start with certain directory authority keys, and
19683 encourage people using them to stop.
19685 o Minor features (controller):
19686 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
19687 is valid before any authentication has been received. It tells
19688 a controller what kind of authentication is expected, and what
19689 protocol is spoken. Implements proposal 119.
19690 - New config option CookieAuthFile to choose a new location for the
19691 cookie authentication file, and config option
19692 CookieAuthFileGroupReadable to make it group-readable.
19694 o Minor features (unit testing):
19695 - Add command-line arguments to unit-test executable so that we can
19696 invoke any chosen test from the command line rather than having
19697 to run the whole test suite at once; and so that we can turn on
19698 logging for the unit tests.
19700 o Minor bugfixes (on 0.1.2.x):
19701 - If we require CookieAuthentication but we fail to write the
19702 cookie file, we would warn but not exit, and end up in a state
19703 where no controller could authenticate. Now we exit.
19704 - If we require CookieAuthentication, stop generating a new cookie
19705 every time we change any piece of our config.
19706 - When loading bandwidth history, do not believe any information in
19707 the future. Fixes bug 434.
19708 - When loading entry guard information, do not believe any information
19710 - When we have our clock set far in the future and generate an
19711 onion key, then re-set our clock to be correct, we should not stop
19712 the onion key from getting rotated.
19713 - Clean up torrc sample config file.
19714 - Do not automatically run configure from autogen.sh. This
19715 non-standard behavior tended to annoy people who have built other
19718 o Minor bugfixes (on 0.2.0.x):
19719 - Fix a bug with AutomapHostsOnResolve that would always cause
19720 the second request to fail. Bug reported by Kate. Bugfix on
19722 - Fix a bug in ADDRMAP controller replies that would sometimes
19723 try to print a NULL. Patch from tup.
19724 - Read v3 directory authority keys from the right location.
19725 - Numerous bugfixes to directory voting code.
19728 Changes in version 0.1.2.16 - 2007-08-01
19729 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
19730 remote attacker in certain situations to rewrite the user's torrc
19731 configuration file. This can completely compromise anonymity of users
19732 in most configurations, including those running the Vidalia bundles,
19733 TorK, etc. Or worse.
19735 o Major security fixes:
19736 - Close immediately after missing authentication on control port;
19737 do not allow multiple authentication attempts.
19740 Changes in version 0.2.0.4-alpha - 2007-08-01
19741 This fourth development snapshot fixes a critical security vulnerability
19742 for most users, specifically those running Vidalia, TorK, etc. Everybody
19743 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
19745 o Major security fixes:
19746 - Close immediately after missing authentication on control port;
19747 do not allow multiple authentication attempts.
19749 o Major bugfixes (compilation):
19750 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
19753 o Minor features (performance):
19754 - Be even more aggressive about releasing RAM from small
19755 empty buffers. Thanks to our free-list code, this shouldn't be too
19756 performance-intensive.
19757 - Disable sentinel-based debugging for buffer code: we squashed all
19758 the bugs that this was supposed to detect a long time ago, and
19759 now its only effect is to change our buffer sizes from nice
19760 powers of two (which platform mallocs tend to like) to values
19761 slightly over powers of two (which make some platform mallocs sad).
19762 - Log malloc statistics from mallinfo() on platforms where it
19766 Changes in version 0.2.0.3-alpha - 2007-07-29
19767 This third development snapshot introduces new experimental
19768 blocking-resistance features and a preliminary version of the v3
19769 directory voting design, and includes many other smaller features
19773 - The first pieces of our "bridge" design for blocking-resistance
19774 are implemented. People can run bridge directory authorities;
19775 people can run bridges; and people can configure their Tor clients
19776 with a set of bridges to use as the first hop into the Tor network.
19777 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
19779 - Create listener connections before we setuid to the configured
19780 User and Group. Now non-Windows users can choose port values
19781 under 1024, start Tor as root, and have Tor bind those ports
19782 before it changes to another UID. (Windows users could already
19784 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
19785 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
19786 on "vserver" accounts. (Patch from coderman.)
19787 - Be even more aggressive about separating local traffic from relayed
19788 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
19790 o Major features (experimental):
19791 - First cut of code for "v3 dir voting": directory authorities will
19792 vote on a common network status document rather than each publishing
19793 their own opinion. This code needs more testing and more corner-case
19794 handling before it's ready for use.
19797 - Directory authorities now call routers Fast if their bandwidth is
19798 at least 100KB/s, and consider their bandwidth adequate to be a
19799 Guard if it is at least 250KB/s, no matter the medians. This fix
19800 complements proposal 107. [Bugfix on 0.1.2.x]
19801 - Directory authorities now never mark more than 3 servers per IP as
19802 Valid and Running. (Implements proposal 109, by Kevin Bauer and
19804 - Minor change to organizationName and commonName generation
19805 procedures in TLS certificates during Tor handshakes, to invalidate
19806 some earlier censorware approaches. This is not a long-term
19807 solution, but applying it will give us a bit of time to look into
19808 the epidemiology of countermeasures as they spread.
19810 o Major bugfixes (directory):
19811 - Rewrite directory tokenization code to never run off the end of
19812 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
19814 o Minor features (controller):
19815 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
19816 match requests to applications. (Patch from Robert Hogan.)
19817 - Report address and port correctly on connections to DNSPort. (Patch
19818 from Robert Hogan.)
19819 - Add a RESOLVE command to launch hostname lookups. (Original patch
19820 from Robert Hogan.)
19821 - Add GETINFO status/enough-dir-info to let controllers tell whether
19822 Tor has downloaded sufficient directory information. (Patch
19824 - You can now use the ControlSocket option to tell Tor to listen for
19825 controller connections on Unix domain sockets on systems that
19826 support them. (Patch from Peter Palfrader.)
19827 - STREAM NEW events are generated for DNSPort requests and for
19828 tunneled directory connections. (Patch from Robert Hogan.)
19829 - New "GETINFO address-mappings/*" command to get address mappings
19830 with expiry information. "addr-mappings/*" is now deprecated.
19833 o Minor features (misc):
19834 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
19836 - The tor-gencert tool for v3 directory authorities now creates all
19837 files as readable to the file creator only, and write-protects
19838 the authority identity key.
19839 - When dumping memory usage, list bytes used in buffer memory
19841 - When running with dmalloc, dump more stats on hup and on exit.
19842 - Directory authorities now fail quickly and (relatively) harmlessly
19843 if they generate a network status document that is somehow
19846 o Traffic load balancing improvements:
19847 - If exit bandwidth ever exceeds one third of total bandwidth, then
19848 use the correct formula to weight exit nodes when choosing paths.
19849 (Based on patch from Mike Perry.)
19850 - Choose perfectly fairly among routers when choosing by bandwidth and
19851 weighting by fraction of bandwidth provided by exits. Previously, we
19852 would choose with only approximate fairness, and correct ourselves
19853 if we ran off the end of the list. [Bugfix on 0.1.2.x]
19855 o Performance improvements:
19856 - Be more aggressive with freeing buffer RAM or putting it on the
19858 - Use Critical Sections rather than Mutexes for synchronizing threads
19859 on win32; Mutexes are heavier-weight, and designed for synchronizing
19862 o Deprecated and removed features:
19863 - RedirectExits is now deprecated.
19864 - Stop allowing address masks that do not correspond to bit prefixes.
19865 We have warned about these for a really long time; now it's time
19866 to reject them. (Patch from croup.)
19868 o Minor bugfixes (directory):
19869 - Fix another crash bug related to extra-info caching. (Bug found by
19870 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
19871 - Directories no longer return a "304 not modified" when they don't
19872 have the networkstatus the client asked for. Also fix a memory
19873 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
19874 - We had accidentally labelled 0.1.2.x directory servers as not
19875 suitable for begin_dir requests, and had labelled no directory
19876 servers as suitable for uploading extra-info documents. [Bugfix
19879 o Minor bugfixes (dns):
19880 - Fix a crash when DNSPort is set more than once. (Patch from Robert
19881 Hogan.) [Bugfix on 0.2.0.2-alpha]
19882 - Add DNSPort connections to the global connection list, so that we
19883 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
19885 - Fix a dangling reference that could lead to a crash when DNSPort is
19886 changed or closed (Patch from Robert Hogan.) [Bugfix on
19889 o Minor bugfixes (controller):
19890 - Provide DNS expiry times in GMT, not in local time. For backward
19891 compatibility, ADDRMAP events only provide GMT expiry in an extended
19892 field. "GETINFO address-mappings" always does the right thing.
19893 - Use CRLF line endings properly in NS events.
19894 - Terminate multi-line control events properly. (Original patch
19895 from tup.) [Bugfix on 0.1.2.x-alpha]
19896 - Do not include spaces in SOURCE_ADDR fields in STREAM
19897 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
19900 Changes in version 0.1.2.15 - 2007-07-17
19901 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
19902 problems, fixes compilation on BSD, and fixes a variety of other
19903 bugs. Everybody should upgrade.
19905 o Major bugfixes (compilation):
19906 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
19908 o Major bugfixes (crashes):
19909 - Try even harder not to dereference the first character after
19910 an mmap(). Reported by lodger.
19911 - Fix a crash bug in directory authorities when we re-number the
19912 routerlist while inserting a new router.
19913 - When the cached-routers file is an even multiple of the page size,
19914 don't run off the end and crash. (Fixes bug 455; based on idea
19916 - Fix eventdns.c behavior on Solaris: It is critical to include
19917 orconfig.h _before_ sys/types.h, so that we can get the expected
19918 definition of _FILE_OFFSET_BITS.
19920 o Major bugfixes (security):
19921 - Fix a possible buffer overrun when using BSD natd support. Bug
19923 - When sending destroy cells from a circuit's origin, don't include
19924 the reason for tearing down the circuit. The spec says we didn't,
19925 and now we actually don't. Reported by lodger.
19926 - Keep streamids from different exits on a circuit separate. This
19927 bug may have allowed other routers on a given circuit to inject
19928 cells into streams. Reported by lodger; fixes bug 446.
19929 - If there's a never-before-connected-to guard node in our list,
19930 never choose any guards past it. This way we don't expand our
19931 guard list unless we need to.
19933 o Minor bugfixes (guard nodes):
19934 - Weight guard selection by bandwidth, so that low-bandwidth nodes
19935 don't get overused as guards.
19937 o Minor bugfixes (directory):
19938 - Correctly count the number of authorities that recommend each
19939 version. Previously, we were under-counting by 1.
19940 - Fix a potential crash bug when we load many server descriptors at
19941 once and some of them make others of them obsolete. Fixes bug 458.
19943 o Minor bugfixes (hidden services):
19944 - Stop tearing down the whole circuit when the user asks for a
19945 connection to a port that the hidden service didn't configure.
19948 o Minor bugfixes (misc):
19949 - On Windows, we were preventing other processes from reading
19950 cached-routers while Tor was running. Reported by janbar.
19951 - Fix a possible (but very unlikely) bug in picking routers by
19952 bandwidth. Add a log message to confirm that it is in fact
19953 unlikely. Patch from lodger.
19954 - Backport a couple of memory leak fixes.
19955 - Backport miscellaneous cosmetic bugfixes.
19958 Changes in version 0.2.0.2-alpha - 2007-06-02
19959 o Major bugfixes on 0.2.0.1-alpha:
19960 - Fix an assertion failure related to servers without extra-info digests.
19961 Resolves bugs 441 and 442.
19963 o Minor features (directory):
19964 - Support "If-Modified-Since" when answering HTTP requests for
19965 directories, running-routers documents, and network-status documents.
19966 (There's no need to support it for router descriptors, since those
19967 are downloaded by descriptor digest.)
19969 o Minor build issues:
19970 - Clear up some MIPSPro compiler warnings.
19971 - When building from a tarball on a machine that happens to have SVK
19972 installed, report the micro-revision as whatever version existed
19973 in the tarball, not as "x".
19976 Changes in version 0.2.0.1-alpha - 2007-06-01
19977 This early development snapshot provides new features for people running
19978 Tor as both a client and a server (check out the new RelayBandwidth
19979 config options); lets Tor run as a DNS proxy; and generally moves us
19980 forward on a lot of fronts.
19982 o Major features, server usability:
19983 - New config options RelayBandwidthRate and RelayBandwidthBurst:
19984 a separate set of token buckets for relayed traffic. Right now
19985 relayed traffic is defined as answers to directory requests, and
19986 OR connections that don't have any local circuits on them.
19988 o Major features, client usability:
19989 - A client-side DNS proxy feature to replace the need for
19990 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
19991 for DNS requests on port 9999, use the Tor network to resolve them
19992 anonymously, and send the reply back like a regular DNS server.
19993 The code still only implements a subset of DNS.
19994 - Make PreferTunneledDirConns and TunnelDirConns work even when
19995 we have no cached directory info. This means Tor clients can now
19996 do all of their connections protected by TLS.
19998 o Major features, performance and efficiency:
19999 - Directory authorities accept and serve "extra info" documents for
20000 routers. These documents contain fields from router descriptors
20001 that aren't usually needed, and that use a lot of excess
20002 bandwidth. Once these fields are removed from router descriptors,
20003 the bandwidth savings should be about 60%. [Partially implements
20005 - Servers upload extra-info documents to any authority that accepts
20006 them. Authorities (and caches that have been configured to download
20007 extra-info documents) download them as needed. [Partially implements
20009 - Change the way that Tor buffers data that it is waiting to write.
20010 Instead of queueing data cells in an enormous ring buffer for each
20011 client->OR or OR->OR connection, we now queue cells on a separate
20012 queue for each circuit. This lets us use less slack memory, and
20013 will eventually let us be smarter about prioritizing different kinds
20015 - Use memory pools to allocate cells with better speed and memory
20016 efficiency, especially on platforms where malloc() is inefficient.
20017 - Stop reading on edge connections when their corresponding circuit
20018 buffers are full; start again as the circuits empty out.
20020 o Major features, other:
20021 - Add an HSAuthorityRecordStats option that hidden service authorities
20022 can use to track statistics of overall hidden service usage without
20023 logging information that would be very useful to an attacker.
20024 - Start work implementing multi-level keys for directory authorities:
20025 Add a standalone tool to generate key certificates. (Proposal 103.)
20028 - Directory authorities now call routers Stable if they have an
20029 uptime of at least 30 days, even if that's not the median uptime
20030 in the network. Implements proposal 107, suggested by Kevin Bauer
20033 o Minor fixes (resource management):
20034 - Count the number of open sockets separately from the number
20035 of active connection_t objects. This will let us avoid underusing
20036 our allocated connection limit.
20037 - We no longer use socket pairs to link an edge connection to an
20038 anonymous directory connection or a DirPort test connection.
20039 Instead, we track the link internally and transfer the data
20040 in-process. This saves two sockets per "linked" connection (at the
20041 client and at the server), and avoids the nasty Windows socketpair()
20043 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
20044 for every single inactive connection_t. Free items from the
20045 4k/16k-buffer free lists when they haven't been used for a while.
20047 o Minor features (build):
20048 - Make autoconf search for libevent, openssl, and zlib consistently.
20049 - Update deprecated macros in configure.in.
20050 - When warning about missing headers, tell the user to let us
20051 know if the compile succeeds anyway, so we can downgrade the
20053 - Include the current subversion revision as part of the version
20054 string: either fetch it directly if we're in an SVN checkout, do
20055 some magic to guess it if we're in an SVK checkout, or use
20056 the last-detected version if we're building from a .tar.gz.
20057 Use this version consistently in log messages.
20059 o Minor features (logging):
20060 - Always prepend "Bug: " to any log message about a bug.
20061 - Put a platform string (e.g. "Linux i686") in the startup log
20062 message, so when people paste just their logs, we know if it's
20063 OpenBSD or Windows or what.
20064 - When logging memory usage, break down memory used in buffers by
20067 o Minor features (directory system):
20068 - New config option V2AuthoritativeDirectory that all directory
20069 authorities should set. This will let future authorities choose
20070 not to serve V2 directory information.
20071 - Directory authorities allow multiple router descriptors and/or extra
20072 info documents to be uploaded in a single go. This will make
20073 implementing proposal 104 simpler.
20075 o Minor features (controller):
20076 - Add a new config option __DisablePredictedCircuits designed for
20077 use by the controller, when we don't want Tor to build any circuits
20079 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
20080 so we can exit from the middle of the circuit.
20081 - Implement "getinfo status/circuit-established".
20082 - Implement "getinfo status/version/..." so a controller can tell
20083 whether the current version is recommended, and whether any versions
20084 are good, and how many authorities agree. (Patch from shibz.)
20086 o Minor features (hidden services):
20087 - Allow multiple HiddenServicePort directives with the same virtual
20088 port; when they occur, the user is sent round-robin to one
20089 of the target ports chosen at random. Partially fixes bug 393 by
20090 adding limited ad-hoc round-robining.
20092 o Minor features (other):
20094 - Add a new AutomapHostsOnResolve option: when it is enabled, any
20095 resolve request for hosts matching a given pattern causes Tor to
20096 generate an internal virtual address mapping for that host. This
20097 allows DNSPort to work sensibly with hidden service users. By
20098 default, .exit and .onion addresses are remapped; the list of
20099 patterns can be reconfigured with AutomapHostsSuffixes.
20100 - Add an "-F" option to tor-resolve to force a resolve for a .onion
20101 address. Thanks to the AutomapHostsOnResolve option, this is no
20102 longer a completely silly thing to do.
20103 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
20104 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
20105 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
20106 minus 1 byte: the actual maximum declared bandwidth.
20108 o Removed features:
20109 - Removed support for the old binary "version 0" controller protocol.
20110 This has been deprecated since 0.1.1, and warnings have been issued
20111 since 0.1.2. When we encounter a v0 control message, we now send
20112 back an error and close the connection.
20113 - Remove the old "dns worker" server DNS code: it hasn't been default
20114 since 0.1.2.2-alpha, and all the servers seem to be using the new
20117 o Minor bugfixes (portability):
20118 - Even though Windows is equally happy with / and \ as path separators,
20119 try to use \ consistently on Windows and / consistently on Unix: it
20120 makes the log messages nicer.
20121 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
20122 - Read resolv.conf files correctly on platforms where read() returns
20123 partial results on small file reads.
20125 o Minor bugfixes (directory):
20126 - Correctly enforce that elements of directory objects do not appear
20127 more often than they are allowed to appear.
20128 - When we are reporting the DirServer line we just parsed, we were
20129 logging the second stanza of the key fingerprint, not the first.
20131 o Minor bugfixes (logging):
20132 - When we hit an EOF on a log (probably because we're shutting down),
20133 don't try to remove the log from the list: just mark it as
20134 unusable. (Bulletproofs against bug 222.)
20136 o Minor bugfixes (other):
20137 - In the exitlist script, only consider the most recently published
20138 server descriptor for each server. Also, when the user requests
20139 a list of servers that _reject_ connections to a given address,
20140 explicitly exclude the IPs that also have servers that accept
20141 connections to that address. (Resolves bug 405.)
20142 - Stop allowing hibernating servers to be "stable" or "fast".
20143 - On Windows, we were preventing other processes from reading
20144 cached-routers while Tor was running. (Reported by janbar)
20145 - Make the NodeFamilies config option work. (Reported by
20146 lodger -- it has never actually worked, even though we added it
20148 - Check return values from pthread_mutex functions.
20149 - Don't save non-general-purpose router descriptors to the disk cache,
20150 because we have no way of remembering what their purpose was when
20152 - Add even more asserts to hunt down bug 417.
20153 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
20154 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
20155 Add a log message to confirm that it is in fact unlikely.
20157 o Minor bugfixes (controller):
20158 - Make 'getinfo fingerprint' return a 551 error if we're not a
20159 server, so we match what the control spec claims we do. Reported
20161 - Fix a typo in an error message when extendcircuit fails that
20162 caused us to not follow the \r\n-based delimiter protocol. Reported
20165 o Code simplifications and refactoring:
20166 - Stop passing around circuit_t and crypt_path_t pointers that are
20167 implicit in other procedure arguments.
20168 - Drop the old code to choke directory connections when the
20169 corresponding OR connections got full: thanks to the cell queue
20170 feature, OR conns don't get full any more.
20171 - Make dns_resolve() handle attaching connections to circuits
20172 properly, so the caller doesn't have to.
20173 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
20174 - Keep the connection array as a dynamic smartlist_t, rather than as
20175 a fixed-sized array. This is important, as the number of connections
20176 is becoming increasingly decoupled from the number of sockets.
20179 Changes in version 0.1.2.14 - 2007-05-25
20180 Tor 0.1.2.14 changes the addresses of two directory authorities (this
20181 change especially affects those who serve or use hidden services),
20182 and fixes several other crash- and security-related bugs.
20184 o Directory authority changes:
20185 - Two directory authorities (moria1 and moria2) just moved to new
20186 IP addresses. This change will particularly affect those who serve
20187 or use hidden services.
20189 o Major bugfixes (crashes):
20190 - If a directory server runs out of space in the connection table
20191 as it's processing a begin_dir request, it will free the exit stream
20192 but leave it attached to the circuit, leading to unpredictable
20193 behavior. (Reported by seeess, fixes bug 425.)
20194 - Fix a bug in dirserv_remove_invalid() that would cause authorities
20195 to corrupt memory under some really unlikely scenarios.
20196 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
20197 - Avoid segfaults when reading from mmaped descriptor file. (Reported
20200 o Major bugfixes (security):
20201 - When choosing an entry guard for a circuit, avoid using guards
20202 that are in the same family as the chosen exit -- not just guards
20203 that are exactly the chosen exit. (Reported by lodger.)
20205 o Major bugfixes (resource management):
20206 - If a directory authority is down, skip it when deciding where to get
20207 networkstatus objects or descriptors. Otherwise we keep asking
20208 every 10 seconds forever. Fixes bug 384.
20209 - Count it as a failure if we fetch a valid network-status but we
20210 don't want to keep it. Otherwise we'll keep fetching it and keep
20211 not wanting to keep it. Fixes part of bug 422.
20212 - If all of our dirservers have given us bad or no networkstatuses
20213 lately, then stop hammering them once per minute even when we
20214 think they're failed. Fixes another part of bug 422.
20217 - Actually set the purpose correctly for descriptors inserted with
20218 purpose=controller.
20219 - When we have k non-v2 authorities in our DirServer config,
20220 we ignored the last k authorities in the list when updating our
20222 - Correctly back-off from requesting router descriptors that we are
20223 having a hard time downloading.
20224 - Read resolv.conf files correctly on platforms where read() returns
20225 partial results on small file reads.
20226 - Don't rebuild the entire router store every time we get 32K of
20227 routers: rebuild it when the journal gets very large, or when
20228 the gaps in the store get very large.
20231 - When routers publish SVN revisions in their router descriptors,
20232 authorities now include those versions correctly in networkstatus
20234 - Warn when using a version of libevent before 1.3b to run a server on
20235 OSX or BSD: these versions interact badly with userspace threads.
20238 Changes in version 0.1.2.13 - 2007-04-24
20239 This release features some major anonymity fixes, such as safer path
20240 selection; better client performance; faster bootstrapping, better
20241 address detection, and better DNS support for servers; write limiting as
20242 well as read limiting to make servers easier to run; and a huge pile of
20243 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
20245 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
20246 of the Freenode IRC network, remembering his patience and vision for
20247 free speech on the Internet.
20250 - Fix a memory leak when we ask for "all" networkstatuses and we
20251 get one we don't recognize.
20252 - Add more asserts to hunt down bug 417.
20253 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
20256 Changes in version 0.1.2.12-rc - 2007-03-16
20258 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
20259 directory information requested inside Tor connections (i.e. via
20260 begin_dir cells). It only triggered when the same connection was
20261 serving other data at the same time. Reported by seeess.
20264 - When creating a circuit via the controller, send a 'launched'
20265 event when we're done, so we follow the spec better.
20268 Changes in version 0.1.2.11-rc - 2007-03-15
20269 o Minor bugfixes (controller), reported by daejees:
20270 - Correct the control spec to match how the code actually responds
20271 to 'getinfo addr-mappings/*'.
20272 - The control spec described a GUARDS event, but the code
20273 implemented a GUARD event. Standardize on GUARD, but let people
20274 ask for GUARDS too.
20277 Changes in version 0.1.2.10-rc - 2007-03-07
20278 o Major bugfixes (Windows):
20279 - Do not load the NT services library functions (which may not exist)
20280 just to detect if we're a service trying to shut down. Now we run
20281 on Win98 and friends again.
20283 o Minor bugfixes (other):
20284 - Clarify a couple of log messages.
20285 - Fix a misleading socks5 error number.
20288 Changes in version 0.1.2.9-rc - 2007-03-02
20289 o Major bugfixes (Windows):
20290 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
20291 of the usual GCC "%llu". This prevents a bug when saving 64-bit
20292 int configuration values: the high-order 32 bits would get
20293 truncated. In particular, we were being bitten by the default
20294 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
20295 and maybe also bug 397.)
20297 o Minor bugfixes (performance):
20298 - Use OpenSSL's AES implementation on platforms where it's faster.
20299 This could save us as much as 10% CPU usage.
20301 o Minor bugfixes (server):
20302 - Do not rotate onion key immediately after setting it for the first
20305 o Minor bugfixes (directory authorities):
20306 - Stop calling servers that have been hibernating for a long time
20307 "stable". Also, stop letting hibernating or obsolete servers affect
20308 uptime and bandwidth cutoffs.
20309 - Stop listing hibernating servers in the v1 directory.
20311 o Minor bugfixes (hidden services):
20312 - Upload hidden service descriptors slightly less often, to reduce
20313 load on authorities.
20315 o Minor bugfixes (other):
20316 - Fix an assert that could trigger if a controller quickly set then
20317 cleared EntryNodes. Bug found by Udo van den Heuvel.
20318 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
20320 - Fix a potential race condition in the rpm installer. Found by
20322 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
20323 of 2 as indicating that the server is completely bad; it sometimes
20324 means that the server is just bad for the request in question. (may fix
20325 the last of bug 326.)
20326 - Disable encrypted directory connections when we don't have a server
20327 descriptor for the destination. We'll get this working again in
20331 Changes in version 0.1.2.8-beta - 2007-02-26
20332 o Major bugfixes (crashes):
20333 - Stop crashing when the controller asks us to resetconf more than
20334 one config option at once. (Vidalia 0.0.11 does this.)
20335 - Fix a crash that happened on Win98 when we're given command-line
20336 arguments: don't try to load NT service functions from advapi32.dll
20337 except when we need them. (Bug introduced in 0.1.2.7-alpha;
20339 - Fix a longstanding obscure crash bug that could occur when
20340 we run out of DNS worker processes. (Resolves bug 390.)
20342 o Major bugfixes (hidden services):
20343 - Correctly detect whether hidden service descriptor downloads are
20344 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
20346 o Major bugfixes (accounting):
20347 - When we start during an accounting interval before it's time to wake
20348 up, remember to wake up at the correct time. (May fix bug 342.)
20350 o Minor bugfixes (controller):
20351 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
20352 clear the corresponding on_circuit variable, and remember later
20353 that we don't need to send a redundant CLOSED event. Resolves part
20355 - Report events where a resolve succeeded or where we got a socks
20356 protocol error correctly, rather than calling both of them
20358 - Change reported stream target addresses to IP consistently when
20359 we finally get the IP from an exit node.
20360 - Send log messages to the controller even if they happen to be very
20363 o Minor bugfixes (other):
20364 - Display correct results when reporting which versions are
20365 recommended, and how recommended they are. (Resolves bug 383.)
20366 - Improve our estimates for directory bandwidth to be less random:
20367 guess that an unrecognized directory will have the average bandwidth
20368 from all known directories, not that it will have the average
20369 bandwidth from those directories earlier than it on the list.
20370 - If we start a server with ClientOnly 1, then set ClientOnly to 0
20371 and hup, stop triggering an assert based on an empty onion_key.
20372 - On platforms with no working mmap() equivalent, don't warn the
20373 user when cached-routers doesn't exist.
20374 - Warn the user when mmap() [or its equivalent] fails for some reason
20375 other than file-not-found.
20376 - Don't warn the user when cached-routers.new doesn't exist: that's
20377 perfectly fine when starting up for the first time.
20378 - When EntryNodes are configured, rebuild the guard list to contain,
20379 in order: the EntryNodes that were guards before; the rest of the
20380 EntryNodes; the nodes that were guards before.
20381 - Mask out all signals in sub-threads; only the libevent signal
20382 handler should be processing them. This should prevent some crashes
20383 on some machines using pthreads. (Patch from coderman.)
20384 - Fix switched arguments on memset in the implementation of
20385 tor_munmap() for systems with no mmap() call.
20386 - When Tor receives a router descriptor that it asked for, but
20387 no longer wants (because it has received fresh networkstatuses
20388 in the meantime), do not warn the user. Cache the descriptor if
20389 we're a cache; drop it if we aren't.
20390 - Make earlier entry guards _really_ get retried when the network
20392 - On a malformed DNS reply, always give an error to the corresponding
20394 - Build with recent libevents on platforms that do not define the
20395 nonstandard types "u_int8_t" and friends.
20397 o Minor features (controller):
20398 - Warn the user when an application uses the obsolete binary v0
20399 control protocol. We're planning to remove support for it during
20400 the next development series, so it's good to give people some
20402 - Add STREAM_BW events to report per-entry-stream bandwidth
20403 use. (Patch from Robert Hogan.)
20404 - Rate-limit SIGNEWNYM signals in response to controllers that
20405 impolitely generate them for every single stream. (Patch from
20406 mwenge; closes bug 394.)
20407 - Make REMAP stream events have a SOURCE (cache or exit), and
20408 make them generated in every case where we get a successful
20409 connected or resolved cell.
20411 o Minor bugfixes (performance):
20412 - Call router_have_min_dir_info half as often. (This is showing up in
20413 some profiles, but not others.)
20414 - When using GCC, make log_debug never get called at all, and its
20415 arguments never get evaluated, when no debug logs are configured.
20416 (This is showing up in some profiles, but not others.)
20419 - Remove some never-implemented options. Mark PathlenCoinWeight as
20421 - Implement proposal 106: Stop requiring clients to have well-formed
20422 certificates; stop checking nicknames in certificates. (Clients
20423 have certificates so that they can look like Tor servers, but in
20424 the future we might want to allow them to look like regular TLS
20425 clients instead. Nicknames in certificates serve no purpose other
20426 than making our protocol easier to recognize on the wire.)
20427 - Revise messages on handshake failure again to be even more clear about
20428 which are incoming connections and which are outgoing.
20429 - Discard any v1 directory info that's over 1 month old (for
20430 directories) or over 1 week old (for running-routers lists).
20431 - Do not warn when individual nodes in the configuration's EntryNodes,
20432 ExitNodes, etc are down: warn only when all possible nodes
20433 are down. (Fixes bug 348.)
20434 - Always remove expired routers and networkstatus docs before checking
20435 whether we have enough information to build circuits. (Fixes
20437 - Put a lower-bound on MaxAdvertisedBandwidth.
20440 Changes in version 0.1.2.7-alpha - 2007-02-06
20441 o Major bugfixes (rate limiting):
20442 - Servers decline directory requests much more aggressively when
20443 they're low on bandwidth. Otherwise they end up queueing more and
20444 more directory responses, which can't be good for latency.
20445 - But never refuse directory requests from local addresses.
20446 - Fix a memory leak when sending a 503 response for a networkstatus
20448 - Be willing to read or write on local connections (e.g. controller
20449 connections) even when the global rate limiting buckets are empty.
20450 - If our system clock jumps back in time, don't publish a negative
20451 uptime in the descriptor. Also, don't let the global rate limiting
20452 buckets go absurdly negative.
20453 - Flush local controller connection buffers periodically as we're
20454 writing to them, so we avoid queueing 4+ megabytes of data before
20457 o Major bugfixes (NT services):
20458 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
20459 command-line flag so that admins can override the default by saying
20460 "tor --service install --user "SomeUser"". This will not affect
20461 existing installed services. Also, warn the user that the service
20462 will look for its configuration file in the service user's
20463 %appdata% directory. (We can't do the 'hardwire the user's appdata
20464 directory' trick any more, since we may not have read access to that
20467 o Major bugfixes (other):
20468 - Previously, we would cache up to 16 old networkstatus documents
20469 indefinitely, if they came from nontrusted authorities. Now we
20470 discard them if they are more than 10 days old.
20471 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
20473 - Detect and reject malformed DNS responses containing circular
20475 - If exits are rare enough that we're not marking exits as guards,
20476 ignore exit bandwidth when we're deciding the required bandwidth
20478 - When we're handling a directory connection tunneled over Tor,
20479 don't fill up internal memory buffers with all the data we want
20480 to tunnel; instead, only add it if the OR connection that will
20481 eventually receive it has some room for it. (This can lead to
20482 slowdowns in tunneled dir connections; a better solution will have
20483 to wait for 0.2.0.)
20485 o Minor bugfixes (dns):
20486 - Add some defensive programming to eventdns.c in an attempt to catch
20487 possible memory-stomping bugs.
20488 - Detect and reject DNS replies containing IPv4 or IPv6 records with
20489 an incorrect number of bytes. (Previously, we would ignore the
20491 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
20492 in the correct order, and doesn't crash.
20493 - Free memory held in recently-completed DNS lookup attempts on exit.
20494 This was not a memory leak, but may have been hiding memory leaks.
20495 - Handle TTL values correctly on reverse DNS lookups.
20496 - Treat failure to parse resolv.conf as an error.
20498 o Minor bugfixes (other):
20499 - Fix crash with "tor --list-fingerprint" (reported by seeess).
20500 - When computing clock skew from directory HTTP headers, consider what
20501 time it was when we finished asking for the directory, not what
20503 - Expire socks connections if they spend too long waiting for the
20504 handshake to finish. Previously we would let them sit around for
20505 days, if the connecting application didn't close them either.
20506 - And if the socks handshake hasn't started, don't send a
20507 "DNS resolve socks failed" handshake reply; just close it.
20508 - Stop using C functions that OpenBSD's linker doesn't like.
20509 - Don't launch requests for descriptors unless we have networkstatuses
20510 from at least half of the authorities. This delays the first
20511 download slightly under pathological circumstances, but can prevent
20512 us from downloading a bunch of descriptors we don't need.
20513 - Do not log IPs with TLS failures for incoming TLS
20514 connections. (Fixes bug 382.)
20515 - If the user asks to use invalid exit nodes, be willing to use
20517 - Stop using the reserved ac_cv namespace in our configure script.
20518 - Call stat() slightly less often; use fstat() when possible.
20519 - Refactor the way we handle pending circuits when an OR connection
20520 completes or fails, in an attempt to fix a rare crash bug.
20521 - Only rewrite a conn's address based on X-Forwarded-For: headers
20522 if it's a parseable public IP address; and stop adding extra quotes
20523 to the resulting address.
20526 - Weight directory requests by advertised bandwidth. Now we can
20527 let servers enable write limiting but still allow most clients to
20528 succeed at their directory requests. (We still ignore weights when
20529 choosing a directory authority; I hope this is a feature.)
20532 - Create a new file ReleaseNotes which was the old ChangeLog. The
20533 new ChangeLog file now includes the summaries for all development
20535 - Check for addresses with invalid characters at the exit as well
20536 as at the client, and warn less verbosely when they fail. You can
20537 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
20538 - Adapt a patch from goodell to let the contrib/exitlist script
20539 take arguments rather than require direct editing.
20540 - Inform the server operator when we decide not to advertise a
20541 DirPort due to AccountingMax enabled or a low BandwidthRate. It
20542 was confusing Zax, so now we're hopefully more helpful.
20543 - Bring us one step closer to being able to establish an encrypted
20544 directory tunnel without knowing a descriptor first. Still not
20545 ready yet. As part of the change, now assume we can use a
20546 create_fast cell if we don't know anything about a router.
20547 - Allow exit nodes to use nameservers running on ports other than 53.
20548 - Servers now cache reverse DNS replies.
20549 - Add an --ignore-missing-torrc command-line option so that we can
20550 get the "use sensible defaults if the configuration file doesn't
20551 exist" behavior even when specifying a torrc location on the command
20554 o Minor features (controller):
20555 - Track reasons for OR connection failure; make these reasons
20556 available via the controller interface. (Patch from Mike Perry.)
20557 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
20558 can learn when clients are sending malformed hostnames to Tor.
20559 - Clean up documentation for controller status events.
20560 - Add a REMAP status to stream events to note that a stream's
20561 address has changed because of a cached address or a MapAddress
20565 Changes in version 0.1.2.6-alpha - 2007-01-09
20567 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
20568 connection handles more than 4 gigs in either direction, we crash.
20569 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
20570 advertised exit node, somebody might try to exit from us when
20571 we're bootstrapping and before we've built our descriptor yet.
20572 Refuse the connection rather than crashing.
20575 - Warn if we (as a server) find that we've resolved an address that we
20576 weren't planning to resolve.
20577 - Warn that using select() on any libevent version before 1.1 will be
20578 unnecessarily slow (even for select()).
20579 - Flush ERR-level controller status events just like we currently
20580 flush ERR-level log events, so that a Tor shutdown doesn't prevent
20581 the controller from learning about current events.
20583 o Minor features (more controller status events):
20584 - Implement EXTERNAL_ADDRESS server status event so controllers can
20585 learn when our address changes.
20586 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
20587 can learn when directories reject our descriptor.
20588 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
20589 can learn when a client application is speaking a non-socks protocol
20591 - Implement DANGEROUS_SOCKS client status event so controllers
20592 can learn when a client application is leaking DNS addresses.
20593 - Implement BUG general status event so controllers can learn when
20594 Tor is unhappy about its internal invariants.
20595 - Implement CLOCK_SKEW general status event so controllers can learn
20596 when Tor thinks the system clock is set incorrectly.
20597 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
20598 server status events so controllers can learn when their descriptors
20599 are accepted by a directory.
20600 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
20601 server status events so controllers can learn about Tor's progress in
20602 deciding whether it's reachable from the outside.
20603 - Implement BAD_LIBEVENT general status event so controllers can learn
20604 when we have a version/method combination in libevent that needs to
20606 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
20607 and DNS_USELESS server status events so controllers can learn
20608 about changes to DNS server status.
20610 o Minor features (directory):
20611 - Authorities no longer recommend exits as guards if this would shift
20612 too much load to the exit nodes.
20615 Changes in version 0.1.2.5-alpha - 2007-01-06
20617 - Enable write limiting as well as read limiting. Now we sacrifice
20618 capacity if we're pushing out lots of directory traffic, rather
20619 than overrunning the user's intended bandwidth limits.
20620 - Include TLS overhead when counting bandwidth usage; previously, we
20621 would count only the bytes sent over TLS, but not the bytes used
20623 - Support running the Tor service with a torrc not in the same
20624 directory as tor.exe and default to using the torrc located in
20625 the %appdata%\Tor\ of the user who installed the service. Patch
20627 - Servers now check for the case when common DNS requests are going to
20628 wildcarded addresses (i.e. all getting the same answer), and change
20629 their exit policy to reject *:* if it's happening.
20630 - Implement BEGIN_DIR cells, so we can connect to the directory
20631 server via TLS to do encrypted directory requests rather than
20632 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
20633 config options if you like.
20635 o Minor features (config and docs):
20636 - Start using the state file to store bandwidth accounting data:
20637 the bw_accounting file is now obsolete. We'll keep generating it
20638 for a while for people who are still using 0.1.2.4-alpha.
20639 - Try to batch changes to the state file so that we do as few
20640 disk writes as possible while still storing important things in
20642 - The state file and the bw_accounting file get saved less often when
20643 the AvoidDiskWrites config option is set.
20644 - Make PIDFile work on Windows (untested).
20645 - Add internal descriptions for a bunch of configuration options:
20646 accessible via controller interface and in comments in saved
20648 - Reject *:563 (NNTPS) in the default exit policy. We already reject
20649 NNTP by default, so this seems like a sensible addition.
20650 - Clients now reject hostnames with invalid characters. This should
20651 avoid some inadvertent info leaks. Add an option
20652 AllowNonRFC953Hostnames to disable this behavior, in case somebody
20653 is running a private network with hosts called @, !, and #.
20654 - Add a maintainer script to tell us which options are missing
20655 documentation: "make check-docs".
20656 - Add a new address-spec.txt document to describe our special-case
20657 addresses: .exit, .onion, and .noconnnect.
20659 o Minor features (DNS):
20660 - Ongoing work on eventdns infrastructure: now it has dns server
20661 and ipv6 support. One day Tor will make use of it.
20662 - Add client-side caching for reverse DNS lookups.
20663 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
20664 - When we change nameservers or IP addresses, reset and re-launch
20665 our tests for DNS hijacking.
20667 o Minor features (directory):
20668 - Authorities now specify server versions in networkstatus. This adds
20669 about 2% to the size of compressed networkstatus docs, and allows
20670 clients to tell which servers support BEGIN_DIR and which don't.
20671 The implementation is forward-compatible with a proposed future
20672 protocol version scheme not tied to Tor versions.
20673 - DirServer configuration lines now have an orport= option so
20674 clients can open encrypted tunnels to the authorities without
20675 having downloaded their descriptors yet. Enabled for moria1,
20676 moria2, tor26, and lefkada now in the default configuration.
20677 - Directory servers are more willing to send a 503 "busy" if they
20678 are near their write limit, especially for v1 directory requests.
20679 Now they can use their limited bandwidth for actual Tor traffic.
20680 - Clients track responses with status 503 from dirservers. After a
20681 dirserver has given us a 503, we try not to use it until an hour has
20682 gone by, or until we have no dirservers that haven't given us a 503.
20683 - When we get a 503 from a directory, and we're not a server, we don't
20684 count the failure against the total number of failures allowed
20685 for the thing we're trying to download.
20686 - Report X-Your-Address-Is correctly from tunneled directory
20687 connections; don't report X-Your-Address-Is when it's an internal
20688 address; and never believe reported remote addresses when they're
20690 - Protect against an unlikely DoS attack on directory servers.
20691 - Add a BadDirectory flag to network status docs so that authorities
20692 can (eventually) tell clients about caches they believe to be
20695 o Minor features (controller):
20696 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
20697 - Reimplement GETINFO so that info/names stays in sync with the
20699 - Implement "GETINFO fingerprint".
20700 - Implement "SETEVENTS GUARD" so controllers can get updates on
20701 entry guard status as it changes.
20703 o Minor features (clean up obsolete pieces):
20704 - Remove some options that have been deprecated since at least
20705 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
20706 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
20707 to set log options.
20708 - We no longer look for identity and onion keys in "identity.key" and
20709 "onion.key" -- these were replaced by secret_id_key and
20710 secret_onion_key in 0.0.8pre1.
20711 - We no longer require unrecognized directory entries to be
20714 o Major bugfixes (security):
20715 - Stop sending the HttpProxyAuthenticator string to directory
20716 servers when directory connections are tunnelled through Tor.
20717 - Clients no longer store bandwidth history in the state file.
20718 - Do not log introduction points for hidden services if SafeLogging
20720 - When generating bandwidth history, round down to the nearest
20721 1k. When storing accounting data, round up to the nearest 1k.
20722 - When we're running as a server, remember when we last rotated onion
20723 keys, so that we will rotate keys once they're a week old even if
20724 we never stay up for a week ourselves.
20726 o Major bugfixes (other):
20727 - Fix a longstanding bug in eventdns that prevented the count of
20728 timed-out resolves from ever being reset. This bug caused us to
20729 give up on a nameserver the third time it timed out, and try it
20730 10 seconds later... and to give up on it every time it timed out
20732 - Take out the '5 second' timeout from the connection retry
20733 schedule. Now the first connect attempt will wait a full 10
20734 seconds before switching to a new circuit. Perhaps this will help
20735 a lot. Based on observations from Mike Perry.
20736 - Fix a bug on the Windows implementation of tor_mmap_file() that
20737 would prevent the cached-routers file from ever loading. Reported
20741 - Fix an assert failure when a directory authority sets
20742 AuthDirRejectUnlisted and then receives a descriptor from an
20743 unlisted router. Reported by seeess.
20744 - Avoid a double-free when parsing malformed DirServer lines.
20745 - Fix a bug when a BSD-style PF socket is first used. Patch from
20747 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
20748 to resolve an address at a given exit node even when they ask for
20750 - Servers no longer ever list themselves in their "family" line,
20751 even if configured to do so. This makes it easier to configure
20752 family lists conveniently.
20753 - When running as a server, don't fall back to 127.0.0.1 when no
20754 nameservers are configured in /etc/resolv.conf; instead, make the
20755 user fix resolv.conf or specify nameservers explicitly. (Resolves
20757 - Stop accepting certain malformed ports in configured exit policies.
20758 - Don't re-write the fingerprint file every restart, unless it has
20760 - Stop warning when a single nameserver fails: only warn when _all_ of
20761 our nameservers have failed. Also, when we only have one nameserver,
20762 raise the threshold for deciding that the nameserver is dead.
20763 - Directory authorities now only decide that routers are reachable
20764 if their identity keys are as expected.
20765 - When the user uses bad syntax in the Log config line, stop
20766 suggesting other bad syntax as a replacement.
20767 - Correctly detect ipv6 DNS capability on OpenBSD.
20769 o Minor bugfixes (controller):
20770 - Report the circuit number correctly in STREAM CLOSED events. Bug
20771 reported by Mike Perry.
20772 - Do not report bizarre values for results of accounting GETINFOs
20773 when the last second's write or read exceeds the allotted bandwidth.
20774 - Report "unrecognized key" rather than an empty string when the
20775 controller tries to fetch a networkstatus that doesn't exist.
20778 Changes in version 0.1.1.26 - 2006-12-14
20779 o Security bugfixes:
20780 - Stop sending the HttpProxyAuthenticator string to directory
20781 servers when directory connections are tunnelled through Tor.
20782 - Clients no longer store bandwidth history in the state file.
20783 - Do not log introduction points for hidden services if SafeLogging
20787 - Fix an assert failure when a directory authority sets
20788 AuthDirRejectUnlisted and then receives a descriptor from an
20789 unlisted router (reported by seeess).
20792 Changes in version 0.1.2.4-alpha - 2006-12-03
20794 - Add support for using natd; this allows FreeBSDs earlier than
20795 5.1.2 to have ipfw send connections through Tor without using
20796 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
20799 - Make all connections to addresses of the form ".noconnect"
20800 immediately get closed. This lets application/controller combos
20801 successfully test whether they're talking to the same Tor by
20802 watching for STREAM events.
20803 - Make cross.sh cross-compilation script work even when autogen.sh
20804 hasn't been run. (Patch from Michael Mohr.)
20805 - Statistics dumped by -USR2 now include a breakdown of public key
20806 operations, for profiling.
20809 - Fix a major leak when directory authorities parse their
20810 approved-routers list, a minor memory leak when we fail to pick
20811 an exit node, and a few rare leaks on errors.
20812 - Handle TransPort connections even when the server sends data before
20813 the client sends data. Previously, the connection would just hang
20814 until the client sent data. (Patch from tup based on patch from
20816 - Avoid assert failure when our cached-routers file is empty on
20820 - Don't log spurious warnings when we see a circuit close reason we
20821 don't recognize; it's probably just from a newer version of Tor.
20822 - Have directory authorities allow larger amounts of drift in uptime
20823 without replacing the server descriptor: previously, a server that
20824 restarted every 30 minutes could have 48 "interesting" descriptors
20826 - Start linking to the Tor specification and Tor reference manual
20827 correctly in the Windows installer.
20828 - Add Vidalia to the OS X uninstaller script, so when we uninstall
20829 Tor/Privoxy we also uninstall Vidalia.
20830 - Resume building on Irix64, and fix a lot of warnings from its
20831 MIPSpro C compiler.
20832 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
20833 when we're running as a client.
20836 Changes in version 0.1.1.25 - 2006-11-04
20838 - When a client asks us to resolve (rather than connect to)
20839 an address, and we have a cached answer, give them the cached
20840 answer. Previously, we would give them no answer at all.
20841 - We were building exactly the wrong circuits when we predict
20842 hidden service requirements, meaning Tor would have to build all
20843 its circuits on demand.
20844 - If none of our live entry guards have a high uptime, but we
20845 require a guard with a high uptime, try adding a new guard before
20846 we give up on the requirement. This patch should make long-lived
20847 connections more stable on average.
20848 - When testing reachability of our DirPort, don't launch new
20849 tests when there's already one in progress -- unreachable
20850 servers were stacking up dozens of testing streams.
20852 o Security bugfixes:
20853 - When the user sends a NEWNYM signal, clear the client-side DNS
20854 cache too. Otherwise we continue to act on previous information.
20857 - Avoid a memory corruption bug when creating a hash table for
20859 - Avoid possibility of controller-triggered crash when misusing
20860 certain commands from a v0 controller on platforms that do not
20861 handle printf("%s",NULL) gracefully.
20862 - Avoid infinite loop on unexpected controller input.
20863 - Don't log spurious warnings when we see a circuit close reason we
20864 don't recognize; it's probably just from a newer version of Tor.
20865 - Add Vidalia to the OS X uninstaller script, so when we uninstall
20866 Tor/Privoxy we also uninstall Vidalia.
20869 Changes in version 0.1.2.3-alpha - 2006-10-29
20871 - Prepare for servers to publish descriptors less often: never
20872 discard a descriptor simply for being too old until either it is
20873 recommended by no authorities, or until we get a better one for
20874 the same router. Make caches consider retaining old recommended
20875 routers for even longer.
20876 - If most authorities set a BadExit flag for a server, clients
20877 don't think of it as a general-purpose exit. Clients only consider
20878 authorities that advertise themselves as listing bad exits.
20879 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
20880 headers for content, so that we can work better in the presence of
20881 caching HTTP proxies.
20882 - Allow authorities to list nodes as bad exits by fingerprint or by
20885 o Minor features, controller:
20886 - Add a REASON field to CIRC events; for backward compatibility, this
20887 field is sent only to controllers that have enabled the extended
20888 event format. Also, add additional reason codes to explain why
20889 a given circuit has been destroyed or truncated. (Patches from
20891 - Add a REMOTE_REASON field to extended CIRC events to tell the
20892 controller about why a remote OR told us to close a circuit.
20893 - Stream events also now have REASON and REMOTE_REASON fields,
20894 working much like those for circuit events.
20895 - There's now a GETINFO ns/... field so that controllers can ask Tor
20896 about the current status of a router.
20897 - A new event type "NS" to inform a controller when our opinion of
20898 a router's status has changed.
20899 - Add a GETINFO events/names and GETINFO features/names so controllers
20900 can tell which events and features are supported.
20901 - A new CLEARDNSCACHE signal to allow controllers to clear the
20902 client-side DNS cache without expiring circuits.
20904 o Security bugfixes:
20905 - When the user sends a NEWNYM signal, clear the client-side DNS
20906 cache too. Otherwise we continue to act on previous information.
20909 - Avoid sending junk to controllers or segfaulting when a controller
20910 uses EVENT_NEW_DESC with verbose nicknames.
20911 - Stop triggering asserts if the controller tries to extend hidden
20912 service circuits (reported by mwenge).
20913 - Avoid infinite loop on unexpected controller input.
20914 - When the controller does a "GETINFO network-status", tell it
20915 about even those routers whose descriptors are very old, and use
20916 long nicknames where appropriate.
20917 - Change NT service functions to be loaded on demand. This lets us
20918 build with MinGW without breaking Tor for Windows 98 users.
20919 - Do DirPort reachability tests less often, since a single test
20920 chews through many circuits before giving up.
20921 - In the hidden service example in torrc.sample, stop recommending
20922 esoteric and discouraged hidden service options.
20923 - When stopping an NT service, wait up to 10 sec for it to actually
20924 stop. Patch from Matt Edman; resolves bug 295.
20925 - Fix handling of verbose nicknames with ORCONN controller events:
20926 make them show up exactly when requested, rather than exactly when
20928 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
20929 printing a duplicate "$" in the keys we send (reported by mwenge).
20930 - Correctly set maximum connection limit on Cygwin. (This time
20932 - Try to detect Windows correctly when cross-compiling.
20933 - Detect the size of the routers file correctly even if it is
20934 corrupted (on systems without mmap) or not page-aligned (on systems
20935 with mmap). This bug was harmless.
20936 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
20937 to open a stream fails; now we do in more cases. This should
20938 make clients able to find a good exit faster in some cases, since
20939 unhandleable requests will now get an error rather than timing out.
20940 - Resolve two memory leaks when rebuilding the on-disk router cache
20941 (reported by fookoowa).
20942 - Clean up minor code warnings suggested by the MIPSpro C compiler,
20943 and reported by some Centos users.
20944 - Controller signals now work on non-Unix platforms that don't define
20945 SIGUSR1 and SIGUSR2 the way we expect.
20946 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
20947 values before failing, and always enables eventdns.
20948 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
20949 Try to fix this in configure.in by checking for most functions
20950 before we check for libevent.
20953 Changes in version 0.1.2.2-alpha - 2006-10-07
20955 - Make our async eventdns library on-by-default for Tor servers,
20956 and plan to deprecate the separate dnsworker threads.
20957 - Add server-side support for "reverse" DNS lookups (using PTR
20958 records so clients can determine the canonical hostname for a given
20959 IPv4 address). Only supported by servers using eventdns; servers
20960 now announce in their descriptors whether they support eventdns.
20961 - Specify and implement client-side SOCKS5 interface for reverse DNS
20962 lookups (see doc/socks-extensions.txt).
20963 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
20964 connect to directory servers through Tor. Previously, clients needed
20965 to find Tor exits to make private connections to directory servers.
20966 - Avoid choosing Exit nodes for entry or middle hops when the
20967 total bandwidth available from non-Exit nodes is much higher than
20968 the total bandwidth available from Exit nodes.
20969 - Workaround for name servers (like Earthlink's) that hijack failing
20970 DNS requests and replace the no-such-server answer with a "helpful"
20971 redirect to an advertising-driven search portal. Also work around
20972 DNS hijackers who "helpfully" decline to hijack known-invalid
20973 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
20974 lets you turn it off.
20975 - Send out a burst of long-range padding cells once we've established
20976 that we're reachable. Spread them over 4 circuits, so hopefully
20977 a few will be fast. This exercises our bandwidth and bootstraps
20978 us into the directory more quickly.
20980 o New/improved config options:
20981 - Add new config option "ResolvConf" to let the server operator
20982 choose an alternate resolve.conf file when using eventdns.
20983 - Add an "EnforceDistinctSubnets" option to control our "exclude
20984 servers on the same /16" behavior. It's still on by default; this
20985 is mostly for people who want to operate private test networks with
20986 all the machines on the same subnet.
20987 - If one of our entry guards is on the ExcludeNodes list, or the
20988 directory authorities don't think it's a good guard, treat it as
20989 if it were unlisted: stop using it as a guard, and throw it off
20990 the guards list if it stays that way for a long time.
20991 - Allow directory authorities to be marked separately as authorities
20992 for the v1 directory protocol, the v2 directory protocol, and
20993 as hidden service directories, to make it easier to retire old
20994 authorities. V1 authorities should set "HSAuthoritativeDir 1"
20995 to continue being hidden service authorities too.
20996 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
20998 o Minor features, controller:
20999 - Fix CIRC controller events so that controllers can learn the
21000 identity digests of non-Named servers used in circuit paths.
21001 - Let controllers ask for more useful identifiers for servers. Instead
21002 of learning identity digests for un-Named servers and nicknames
21003 for Named servers, the new identifiers include digest, nickname,
21004 and indication of Named status. Off by default; see control-spec.txt
21005 for more information.
21006 - Add a "getinfo address" controller command so it can display Tor's
21007 best guess to the user.
21008 - New controller event to alert the controller when our server
21009 descriptor has changed.
21010 - Give more meaningful errors on controller authentication failure.
21012 o Minor features, other:
21013 - When asked to resolve a hostname, don't use non-exit servers unless
21014 requested to do so. This allows servers with broken DNS to be
21015 useful to the network.
21016 - Divide eventdns log messages into warn and info messages.
21017 - Reserve the nickname "Unnamed" for routers that can't pick
21018 a hostname: any router can call itself Unnamed; directory
21019 authorities will never allocate Unnamed to any particular router;
21020 clients won't believe that any router is the canonical Unnamed.
21021 - Only include function names in log messages for info/debug messages.
21022 For notice/warn/err, the content of the message should be clear on
21023 its own, and printing the function name only confuses users.
21024 - Avoid some false positives during reachability testing: don't try
21025 to test via a server that's on the same /24 as us.
21026 - If we fail to build a circuit to an intended enclave, and it's
21027 not mandatory that we use that enclave, stop wanting it.
21028 - When eventdns is enabled, allow multithreaded builds on NetBSD and
21029 OpenBSD. (We had previously disabled threads on these platforms
21030 because they didn't have working thread-safe resolver functions.)
21032 o Major bugfixes, anonymity/security:
21033 - If a client asked for a server by name, and there's a named server
21034 in our network-status but we don't have its descriptor yet, we
21035 could return an unnamed server instead.
21036 - Fix NetBSD bug that could allow someone to force uninitialized RAM
21037 to be sent to a server's DNS resolver. This only affects NetBSD
21038 and other platforms that do not bounds-check tolower().
21039 - Reject (most) attempts to use Tor circuits with length one. (If
21040 many people start using Tor as a one-hop proxy, exit nodes become
21041 a more attractive target for compromise.)
21042 - Just because your DirPort is open doesn't mean people should be
21043 able to remotely teach you about hidden service descriptors. Now
21044 only accept rendezvous posts if you've got HSAuthoritativeDir set.
21046 o Major bugfixes, other:
21047 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
21048 - When a client asks the server to resolve (not connect to)
21049 an address, and it has a cached answer, give them the cached answer.
21050 Previously, the server would give them no answer at all.
21051 - Allow really slow clients to not hang up five minutes into their
21052 directory downloads (suggested by Adam J. Richter).
21053 - We were building exactly the wrong circuits when we anticipated
21054 hidden service requirements, meaning Tor would have to build all
21055 its circuits on demand.
21056 - Avoid crashing when we mmap a router cache file of size 0.
21057 - When testing reachability of our DirPort, don't launch new
21058 tests when there's already one in progress -- unreachable
21059 servers were stacking up dozens of testing streams.
21061 o Minor bugfixes, correctness:
21062 - If we're a directory mirror and we ask for "all" network status
21063 documents, we would discard status documents from authorities
21064 we don't recognize.
21065 - Avoid a memory corruption bug when creating a hash table for
21067 - Avoid controller-triggered crash when misusing certain commands
21068 from a v0 controller on platforms that do not handle
21069 printf("%s",NULL) gracefully.
21070 - Don't crash when a controller sends a third argument to an
21071 "extendcircuit" request.
21072 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
21073 response; fix error code when "getinfo dir/status/" fails.
21074 - Avoid crash when telling controller stream-status and a stream
21076 - Patch from Adam Langley to fix assert() in eventdns.c.
21077 - Fix a debug log message in eventdns to say "X resolved to Y"
21078 instead of "X resolved to X".
21079 - Make eventdns give strings for DNS errors, not just error numbers.
21080 - Track unreachable entry guards correctly: don't conflate
21081 'unreachable by us right now' with 'listed as down by the directory
21082 authorities'. With the old code, if a guard was unreachable by
21083 us but listed as running, it would clog our guard list forever.
21084 - Behave correctly in case we ever have a network with more than
21085 2GB/s total advertised capacity.
21086 - Make TrackExitHosts case-insensitive, and fix the behavior of
21087 ".suffix" TrackExitHosts items to avoid matching in the middle of
21089 - Finally fix the openssl warnings from newer gccs that believe that
21090 ignoring a return value is okay, but casting a return value and
21091 then ignoring it is a sign of madness.
21092 - Prevent the contrib/exitlist script from printing the same
21093 result more than once.
21094 - Patch from Steve Hildrey: Generate network status correctly on
21095 non-versioning dirservers.
21096 - Don't listen to the X-Your-Address-Is hint if you did the lookup
21097 via Tor; otherwise you'll think you're the exit node's IP address.
21099 o Minor bugfixes, performance:
21100 - Two small performance improvements on parsing descriptors.
21101 - Major performance improvement on inserting descriptors: change
21102 algorithm from O(n^2) to O(n).
21103 - Make the common memory allocation path faster on machines where
21104 malloc(0) returns a pointer.
21105 - Start remembering X-Your-Address-Is directory hints even if you're
21106 a client, so you can become a server more smoothly.
21107 - Avoid duplicate entries on MyFamily line in server descriptor.
21109 o Packaging, features:
21110 - Remove architecture from OS X builds. The official builds are
21111 now universal binaries.
21112 - The Debian package now uses --verify-config when (re)starting,
21113 to distinguish configuration errors from other errors.
21114 - Update RPMs to require libevent 1.1b.
21116 o Packaging, bugfixes:
21117 - Patches so Tor builds with MinGW on Windows.
21118 - Patches so Tor might run on Cygwin again.
21119 - Resume building on non-gcc compilers and ancient gcc. Resume
21120 building with the -O0 compile flag. Resume building cleanly on
21122 - Run correctly on OS X platforms with case-sensitive filesystems.
21123 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
21124 - Add autoconf checks so Tor can build on Solaris x86 again.
21127 - Documented (and renamed) ServerDNSSearchDomains and
21128 ServerDNSResolvConfFile options.
21129 - Be clearer that the *ListenAddress directives can be repeated
21133 Changes in version 0.1.1.24 - 2006-09-29
21135 - Allow really slow clients to not hang up five minutes into their
21136 directory downloads (suggested by Adam J. Richter).
21137 - Fix major performance regression from 0.1.0.x: instead of checking
21138 whether we have enough directory information every time we want to
21139 do something, only check when the directory information has changed.
21140 This should improve client CPU usage by 25-50%.
21141 - Don't crash if, after a server has been running for a while,
21142 it can't resolve its hostname.
21145 - Allow Tor to start when RunAsDaemon is set but no logs are set.
21146 - Don't crash when the controller receives a third argument to an
21147 "extendcircuit" request.
21148 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
21149 response; fix error code when "getinfo dir/status/" fails.
21150 - Fix configure.in to not produce broken configure files with
21151 more recent versions of autoconf. Thanks to Clint for his auto*
21153 - Fix security bug on NetBSD that could allow someone to force
21154 uninitialized RAM to be sent to a server's DNS resolver. This
21155 only affects NetBSD and other platforms that do not bounds-check
21157 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
21158 methods: these are known to be buggy.
21159 - If we're a directory mirror and we ask for "all" network status
21160 documents, we would discard status documents from authorities
21161 we don't recognize.
21164 Changes in version 0.1.2.1-alpha - 2006-08-27
21166 - Add "eventdns" async dns library from Adam Langley, tweaked to
21167 build on OSX and Windows. Only enabled if you pass the
21168 --enable-eventdns argument to configure.
21169 - Allow servers with no hostname or IP address to learn their
21170 IP address by asking the directory authorities. This code only
21171 kicks in when you would normally have exited with a "no address"
21172 error. Nothing's authenticated, so use with care.
21173 - Rather than waiting a fixed amount of time between retrying
21174 application connections, we wait only 5 seconds for the first,
21175 10 seconds for the second, and 15 seconds for each retry after
21176 that. Hopefully this will improve the expected user experience.
21177 - Patch from Tup to add support for transparent AP connections:
21178 this basically bundles the functionality of trans-proxy-tor
21179 into the Tor mainline. Now hosts with compliant pf/netfilter
21180 implementations can redirect TCP connections straight to Tor
21181 without diverting through SOCKS. Needs docs.
21182 - Busy directory servers save lots of memory by spooling server
21183 descriptors, v1 directories, and v2 networkstatus docs to buffers
21184 as needed rather than en masse. Also mmap the cached-routers
21185 files, so we don't need to keep the whole thing in memory too.
21186 - Automatically avoid picking more than one node from the same
21187 /16 network when constructing a circuit.
21188 - Revise and clean up the torrc.sample that we ship with; add
21189 a section for BandwidthRate and BandwidthBurst.
21192 - Split circuit_t into origin_circuit_t and or_circuit_t, and
21193 split connection_t into edge, or, dir, control, and base structs.
21194 These will save quite a bit of memory on busy servers, and they'll
21195 also help us track down bugs in the code and bugs in the spec.
21196 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
21197 or later. Log when we are doing this, so we can diagnose it when
21198 it fails. (Also, recommend libevent 1.1b for kqueue and
21199 win32 methods; deprecate libevent 1.0b harder; make libevent
21200 recommendation system saner.)
21201 - Start being able to build universal binaries on OS X (thanks
21203 - Export the default exit policy via the control port, so controllers
21204 don't need to guess what it is / will be later.
21205 - Add a man page entry for ProtocolWarnings.
21206 - Add TestVia config option to the man page.
21207 - Remove even more protocol-related warnings from Tor server logs,
21208 such as bad TLS handshakes and malformed begin cells.
21209 - Stop fetching descriptors if you're not a dir mirror and you
21210 haven't tried to establish any circuits lately. [This currently
21211 causes some dangerous behavior, because when you start up again
21212 you'll use your ancient server descriptors.]
21213 - New DirPort behavior: if you have your dirport set, you download
21214 descriptors aggressively like a directory mirror, whether or not
21215 your ORPort is set.
21216 - Get rid of the router_retry_connections notion. Now routers
21217 no longer try to rebuild long-term connections to directory
21218 authorities, and directory authorities no longer try to rebuild
21219 long-term connections to all servers. We still don't hang up
21220 connections in these two cases though -- we need to look at it
21221 more carefully to avoid flapping, and we likely need to wait til
21222 0.1.1.x is obsolete.
21223 - Drop compatibility with obsolete Tors that permit create cells
21224 to have the wrong circ_id_type.
21225 - Re-enable per-connection rate limiting. Get rid of the "OP
21226 bandwidth" concept. Lay groundwork for "bandwidth classes" --
21227 separate global buckets that apply depending on what sort of conn
21229 - Start publishing one minute or so after we find our ORPort
21230 to be reachable. This will help reduce the number of descriptors
21231 we have for ourselves floating around, since it's quite likely
21232 other things (e.g. DirPort) will change during that minute too.
21233 - Fork the v1 directory protocol into its own spec document,
21234 and mark dir-spec.txt as the currently correct (v2) spec.
21237 - When we find our DirPort to be reachable, publish a new descriptor
21238 so we'll tell the world (reported by pnx).
21239 - Publish a new descriptor after we hup/reload. This is important
21240 if our config has changed such that we'll want to start advertising
21241 our DirPort now, etc.
21242 - Allow Tor to start when RunAsDaemon is set but no logs are set.
21243 - When we have a state file we cannot parse, tell the user and
21244 move it aside. Now we avoid situations where the user starts
21245 Tor in 1904, Tor writes a state file with that timestamp in it,
21246 the user fixes her clock, and Tor refuses to start.
21247 - Fix configure.in to not produce broken configure files with
21248 more recent versions of autoconf. Thanks to Clint for his auto*
21250 - "tor --verify-config" now exits with -1(255) or 0 depending on
21251 whether the config options are bad or good.
21252 - Resolve bug 321 when using dnsworkers: append a period to every
21253 address we resolve at the exit node, so that we do not accidentally
21254 pick up local addresses, and so that failing searches are retried
21255 in the resolver search domains. (This is already solved for
21256 eventdns.) (This breaks Blossom servers for now.)
21257 - If we are using an exit enclave and we can't connect, e.g. because
21258 its webserver is misconfigured to not listen on localhost, then
21259 back off and try connecting from somewhere else before we fail.
21262 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
21263 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
21264 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
21265 when the IP address is mapped through MapAddress to a hostname.
21266 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
21267 useless IPv6 DNS resolves.
21268 - Patch suggested by Karsten Loesing: respond to SIGNAL command
21269 before we execute the signal, in case the signal shuts us down.
21270 - Clean up AllowInvalidNodes man page entry.
21271 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
21272 - Add more asserts to track down an assert error on a windows Tor
21273 server with connection_add being called with socket == -1.
21274 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
21275 - Fix misleading log messages: an entry guard that is "unlisted",
21276 as well as not known to be "down" (because we've never heard
21277 of it), is not therefore "up".
21278 - Remove code to special-case "-cvs" ending, since it has not
21279 actually mattered since 0.0.9.
21280 - Make our socks5 handling more robust to broken socks clients:
21281 throw out everything waiting on the buffer in between socks
21282 handshake phases, since they can't possibly (so the theory
21283 goes) have predicted what we plan to respond to them.
21286 Changes in version 0.1.1.23 - 2006-07-30
21288 - Fast Tor servers, especially exit nodes, were triggering asserts
21289 due to a bug in handling the list of pending DNS resolves. Some
21290 bugs still remain here; we're hunting them.
21291 - Entry guards could crash clients by sending unexpected input.
21292 - More fixes on reachability testing: if you find yourself reachable,
21293 then don't ever make any client requests (so you stop predicting
21294 circuits), then hup or have your clock jump, then later your IP
21295 changes, you won't think circuits are working, so you won't try to
21296 test reachability, so you won't publish.
21299 - Avoid a crash if the controller does a resetconf firewallports
21300 and then a setconf fascistfirewall=1.
21301 - Avoid an integer underflow when the dir authority decides whether
21302 a router is stable: we might wrongly label it stable, and compute
21303 a slightly wrong median stability, when a descriptor is published
21305 - Fix a place where we might trigger an assert if we can't build our
21306 own server descriptor yet.
21309 Changes in version 0.1.1.22 - 2006-07-05
21311 - Fix a big bug that was causing servers to not find themselves
21312 reachable if they changed IP addresses. Since only 0.1.1.22+
21313 servers can do reachability testing correctly, now we automatically
21314 make sure to test via one of these.
21315 - Fix to allow clients and mirrors to learn directory info from
21316 descriptor downloads that get cut off partway through.
21317 - Directory authorities had a bug in deciding if a newly published
21318 descriptor was novel enough to make everybody want a copy -- a few
21319 servers seem to be publishing new descriptors many times a minute.
21321 - Fix a rare bug that was causing some servers to complain about
21322 "closing wedged cpuworkers" and skip some circuit create requests.
21323 - Make the Exit flag in directory status documents actually work.
21326 Changes in version 0.1.1.21 - 2006-06-10
21327 o Crash and assert fixes from 0.1.1.20:
21328 - Fix a rare crash on Tor servers that have enabled hibernation.
21329 - Fix a seg fault on startup for Tor networks that use only one
21330 directory authority.
21331 - Fix an assert from a race condition that occurs on Tor servers
21332 while exiting, where various threads are trying to log that they're
21333 exiting, and delete the logs, at the same time.
21334 - Make our unit tests pass again on certain obscure platforms.
21337 - Add support for building SUSE RPM packages.
21338 - Speed up initial bootstrapping for clients: if we are making our
21339 first ever connection to any entry guard, then don't mark it down
21341 - When only one Tor server in the network is labelled as a guard,
21342 and we've already picked him, we would cycle endlessly picking him
21343 again, being unhappy about it, etc. Now we specifically exclude
21344 current guards when picking a new guard.
21345 - Servers send create cells more reliably after the TLS connection
21346 is established: we were sometimes forgetting to send half of them
21347 when we had more than one pending.
21348 - If we get a create cell that asks us to extend somewhere, but the
21349 Tor server there doesn't match the expected digest, we now send
21350 a destroy cell back, rather than silently doing nothing.
21351 - Make options->RedirectExit work again.
21352 - Make cookie authentication for the controller work again.
21353 - Stop being picky about unusual characters in the arguments to
21354 mapaddress. It's none of our business.
21355 - Add a new config option "TestVia" that lets you specify preferred
21356 middle hops to use for test circuits. Perhaps this will let me
21357 debug the reachability problems better.
21359 o Log / documentation fixes:
21360 - If we're a server and some peer has a broken TLS certificate, don't
21361 log about it unless ProtocolWarnings is set, i.e., we want to hear
21362 about protocol violations by others.
21363 - Fix spelling of VirtualAddrNetwork in man page.
21364 - Add a better explanation at the top of the autogenerated torrc file
21365 about what happened to our old torrc.
21368 Changes in version 0.1.1.20 - 2006-05-23
21370 - Downgrade a log severity where servers complain that they're
21372 - Avoid a compile warning on FreeBSD.
21373 - Remove string size limit on NEWDESC messages; solve bug 291.
21374 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
21375 more thoroughly when we're running on windows.
21378 Changes in version 0.1.1.19-rc - 2006-05-03
21380 - Regenerate our local descriptor if it's dirty and we try to use
21381 it locally (e.g. if it changes during reachability detection).
21382 - If we setconf our ORPort to 0, we continued to listen on the
21383 old ORPort and receive connections.
21384 - Avoid a second warning about machine/limits.h on Debian
21386 - Be willing to add our own routerinfo into the routerlist.
21387 Now authorities will include themselves in their directories
21388 and network-statuses.
21389 - Stop trying to upload rendezvous descriptors to every
21390 directory authority: only try the v1 authorities.
21391 - Servers no longer complain when they think they're not
21392 registered with the directory authorities. There were too many
21394 - Backport dist-rpm changes so rpms can be built without errors.
21397 - Implement an option, VirtualAddrMask, to set which addresses
21398 get handed out in response to mapaddress requests. This works
21399 around a bug in tsocks where 127.0.0.0/8 is never socksified.
21402 Changes in version 0.1.1.18-rc - 2006-04-10
21404 - Work harder to download live network-statuses from all the
21405 directory authorities we know about. Improve the threshold
21406 decision logic so we're more robust to edge cases.
21407 - When fetching rendezvous descriptors, we were willing to ask
21408 v2 authorities too, which would always return 404.
21411 - Stop listing down or invalid nodes in the v1 directory. This will
21412 reduce its bulk by about 1/3, and reduce load on directory
21414 - When deciding whether a router is Fast or Guard-worthy, consider
21415 his advertised BandwidthRate and not just the BandwidthCapacity.
21416 - No longer ship INSTALL and README files -- they are useless now.
21417 - Force rpmbuild to behave and honor target_cpu.
21418 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
21419 - Start to include translated versions of the tor-doc-*.html
21420 files, along with the screenshots. Still needs more work.
21421 - Start sending back 512 and 451 errors if mapaddress fails,
21422 rather than not sending anything back at all.
21423 - When we fail to bind or listen on an incoming or outgoing
21424 socket, we should close it before failing. otherwise we just
21425 leak it. (thanks to weasel for finding.)
21426 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
21427 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
21428 - Make NoPublish (even though deprecated) work again.
21429 - Fix a minor security flaw where a versioning auth dirserver
21430 could list a recommended version many times in a row to make
21431 clients more convinced that it's recommended.
21432 - Fix crash bug if there are two unregistered servers running
21433 with the same nickname, one of them is down, and you ask for
21434 them by nickname in your EntryNodes or ExitNodes. Also, try
21435 to pick the one that's running rather than an arbitrary one.
21436 - Fix an infinite loop we could hit if we go offline for too long.
21437 - Complain when we hit WSAENOBUFS on recv() or write() too.
21438 Perhaps this will help us hunt the bug.
21439 - If you're not a versioning dirserver, don't put the string
21440 "client-versions \nserver-versions \n" in your network-status.
21441 - Lower the minimum required number of file descriptors to 1000,
21442 so we can have some overhead for Valgrind on Linux, where the
21443 default ulimit -n is 1024.
21446 - Add tor.dizum.com as the fifth authoritative directory server.
21447 - Add a new config option FetchUselessDescriptors, off by default,
21448 for when you plan to run "exitlist" on your client and you want
21449 to know about even the non-running descriptors.
21452 Changes in version 0.1.1.17-rc - 2006-03-28
21454 - Clients and servers since 0.1.1.10-alpha have been expiring
21455 connections whenever they are idle for 5 minutes and they *do*
21456 have circuits on them. Oops. With this new version, clients will
21457 discard their previous entry guard choices and avoid choosing
21458 entry guards running these flawed versions.
21459 - Fix memory leak when uncompressing concatenated zlib streams. This
21460 was causing substantial leaks over time on Tor servers.
21461 - The v1 directory was including servers as much as 48 hours old,
21462 because that's how the new routerlist->routers works. Now only
21463 include them if they're 20 hours old or less.
21466 - Resume building on irix64, netbsd 2.0, etc.
21467 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
21469 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
21470 and it is confusing some users.
21471 - Mirrors stop caching the v1 directory so often.
21472 - Make the max number of old descriptors that a cache will hold
21473 rise with the number of directory authorities, so we can scale.
21474 - Change our win32 uname() hack to be more forgiving about what
21475 win32 versions it thinks it's found.
21478 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
21480 - When the controller's *setconf commands fail, collect an error
21481 message in a string and hand it back to the controller.
21482 - Make the v2 dir's "Fast" flag based on relative capacity, just
21483 like "Stable" is based on median uptime. Name everything in the
21484 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
21485 - Log server fingerprint on startup, so new server operators don't
21486 have to go hunting around their filesystem for it.
21487 - Return a robots.txt on our dirport to discourage google indexing.
21488 - Let the controller ask for GETINFO dir/status/foo so it can ask
21489 directly rather than connecting to the dir port. Only works when
21490 dirport is set for now.
21492 o New config options rather than constants in the code:
21493 - SocksTimeout: How long do we let a socks connection wait
21494 unattached before we fail it?
21495 - CircuitBuildTimeout: Cull non-open circuits that were born
21496 at least this many seconds ago.
21497 - CircuitIdleTimeout: Cull open clean circuits that were born
21498 at least this many seconds ago.
21501 Changes in version 0.1.1.16-rc - 2006-03-18
21502 o Bugfixes on 0.1.1.15-rc:
21503 - Fix assert when the controller asks to attachstream a connect-wait
21504 or resolve-wait stream.
21505 - Now do address rewriting when the controller asks us to attach
21506 to a particular circuit too. This will let Blossom specify
21507 "moria2.exit" without having to learn what moria2's IP address is.
21508 - Make the "tor --verify-config" command-line work again, so people
21509 can automatically check if their torrc will parse.
21510 - Authoritative dirservers no longer require an open connection from
21511 a server to consider him "reachable". We need this change because
21512 when we add new auth dirservers, old servers won't know not to
21514 - Let Tor build on Sun CC again.
21515 - Fix an off-by-one buffer size in dirserv.c that magically never
21516 hit our three authorities but broke sjmurdoch's own tor network.
21517 - If we as a directory mirror don't know of any v1 directory
21518 authorities, then don't try to cache any v1 directories.
21519 - Stop warning about unknown servers in our family when they are
21520 given as hex digests.
21521 - Stop complaining as quickly to the server operator that he
21522 hasn't registered his nickname/key binding.
21523 - Various cleanups so we can add new V2 Auth Dirservers.
21524 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
21525 reflect the updated flags in our v2 dir protocol.
21526 - Resume allowing non-printable characters for exit streams (both
21527 for connecting and for resolving). Now we tolerate applications
21528 that don't follow the RFCs. But continue to block malformed names
21531 o Bugfixes on 0.1.0.x:
21532 - Fix assert bug in close_logs(): when we close and delete logs,
21533 remove them all from the global "logfiles" list.
21534 - Fix minor integer overflow in calculating when we expect to use up
21535 our bandwidth allocation before hibernating.
21536 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
21537 there are multiple SSLs installed with different versions.
21538 - When we try to be a server and Address is not explicitly set and
21539 our hostname resolves to a private IP address, try to use an
21540 interface address if it has a public address. Now Windows machines
21541 that think of themselves as localhost can work by default.
21544 - Let the controller ask for GETINFO dir/server/foo so it can ask
21545 directly rather than connecting to the dir port.
21546 - Let the controller tell us about certain router descriptors
21547 that it doesn't want Tor to use in circuits. Implement
21548 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
21549 - New config option SafeSocks to reject all application connections
21550 using unsafe socks protocols. Defaults to off.
21553 Changes in version 0.1.1.15-rc - 2006-03-11
21554 o Bugfixes and cleanups:
21555 - When we're printing strings from the network, don't try to print
21556 non-printable characters. This protects us against shell escape
21557 sequence exploits, and also against attacks to fool humans into
21558 misreading their logs.
21559 - Fix a bug where Tor would fail to establish any connections if you
21560 left it off for 24 hours and then started it: we were happy with
21561 the obsolete network statuses, but they all referred to router
21562 descriptors that were too old to fetch, so we ended up with no
21563 valid router descriptors.
21564 - Fix a seg fault in the controller's "getinfo orconn-status"
21565 command while listing status on incoming handshaking connections.
21566 Introduce a status name "NEW" for these connections.
21567 - If we get a linelist or linelist_s config option from the torrc
21568 (e.g. ExitPolicy) and it has no value, warn and skip rather than
21569 silently resetting it to its default.
21570 - Don't abandon entry guards until they've been down or gone for
21572 - Cleaner and quieter log messages.
21575 - New controller signal NEWNYM that makes new application requests
21576 use clean circuits.
21577 - Add a new circuit purpose 'controller' to let the controller ask
21578 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
21579 controller command to let you specify the purpose if you're
21580 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
21581 command to let you change a circuit's purpose after it's been
21583 - Accept "private:*" in routerdesc exit policies; not generated yet
21584 because older Tors do not understand it.
21585 - Add BSD-style contributed startup script "rc.subr" from Peter
21589 Changes in version 0.1.1.14-alpha - 2006-02-20
21590 o Bugfixes on 0.1.1.x:
21591 - Don't die if we ask for a stdout or stderr log (even implicitly)
21592 and we're set to RunAsDaemon -- just warn.
21593 - We still had a few bugs in the OR connection rotation code that
21594 caused directory servers to slowly aggregate connections to other
21595 fast Tor servers. This time for sure!
21596 - Make log entries on Win32 include the name of the function again.
21597 - We were treating a pair of exit policies if they were equal even
21598 if one said accept and the other said reject -- causing us to
21599 not always publish a new descriptor since we thought nothing
21601 - Retry pending server downloads as well as pending networkstatus
21602 downloads when we unexpectedly get a socks request.
21603 - We were ignoring the IS_FAST flag in the directory status,
21604 meaning we were willing to pick trivial-bandwidth nodes for "fast"
21606 - If the controller's SAVECONF command fails (e.g. due to file
21607 permissions), let the controller know that it failed.
21610 - If we're trying to be a Tor server and running Windows 95/98/ME
21611 as a server, explain that we'll likely crash.
21612 - When we're a server, a client asks for an old-style directory,
21613 and our write bucket is empty, don't give it to him. This way
21614 small servers can continue to serve the directory *sometimes*,
21615 without getting overloaded.
21616 - Compress exit policies even more -- look for duplicate lines
21618 - Clients now honor the "guard" flag in the router status when
21619 picking entry guards, rather than looking at is_fast or is_stable.
21620 - Retain unrecognized lines in $DATADIR/state file, so that we can
21621 be forward-compatible.
21622 - Generate 18.0.0.0/8 address policy format in descs when we can;
21623 warn when the mask is not reducible to a bit-prefix.
21624 - Let the user set ControlListenAddress in the torrc. This can be
21625 dangerous, but there are some cases (like a secured LAN) where it
21627 - Split ReachableAddresses into ReachableDirAddresses and
21628 ReachableORAddresses, so we can restrict Dir conns to port 80
21629 and OR conns to port 443.
21630 - Now we can target arch and OS in rpm builds (contributed by
21631 Phobos). Also make the resulting dist-rpm filename match the
21633 - New config options to help controllers: FetchServerDescriptors
21634 and FetchHidServDescriptors for whether to fetch server
21635 info and hidserv info or let the controller do it, and
21636 PublishServerDescriptor and PublishHidServDescriptors.
21637 - Also let the controller set the __AllDirActionsPrivate config
21638 option if you want all directory fetches/publishes to happen via
21639 Tor (it assumes your controller bootstraps your circuits).
21642 Changes in version 0.1.0.17 - 2006-02-17
21643 o Crash bugfixes on 0.1.0.x:
21644 - When servers with a non-zero DirPort came out of hibernation,
21645 sometimes they would trigger an assert.
21647 o Other important bugfixes:
21648 - On platforms that don't have getrlimit (like Windows), we were
21649 artificially constraining ourselves to a max of 1024
21650 connections. Now just assume that we can handle as many as 15000
21651 connections. Hopefully this won't cause other problems.
21653 o Backported features:
21654 - When we're a server, a client asks for an old-style directory,
21655 and our write bucket is empty, don't give it to him. This way
21656 small servers can continue to serve the directory *sometimes*,
21657 without getting overloaded.
21658 - Whenever you get a 503 in response to a directory fetch, try
21659 once more. This will become important once servers start sending
21660 503's whenever they feel busy.
21661 - Fetch a new directory every 120 minutes, not every 40 minutes.
21662 Now that we have hundreds of thousands of users running the old
21663 directory algorithm, it's starting to hurt a lot.
21664 - Bump up the period for forcing a hidden service descriptor upload
21665 from 20 minutes to 1 hour.
21668 Changes in version 0.1.1.13-alpha - 2006-02-09
21669 o Crashes in 0.1.1.x:
21670 - When you tried to setconf ORPort via the controller, Tor would
21671 crash. So people using TorCP to become a server were sad.
21672 - Solve (I hope) the stack-smashing bug that we were seeing on fast
21673 servers. The problem appears to be something do with OpenSSL's
21674 random number generation, or how we call it, or something. Let me
21675 know if the crashes continue.
21676 - Turn crypto hardware acceleration off by default, until we find
21677 somebody smart who can test it for us. (It appears to produce
21678 seg faults in at least some cases.)
21679 - Fix a rare assert error when we've tried all intro points for
21680 a hidden service and we try fetching the service descriptor again:
21681 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
21684 - Fix a major load balance bug: we were round-robining in 16 KB
21685 chunks, and servers with bandwidthrate of 20 KB, while downloading
21686 a 600 KB directory, would starve their other connections. Now we
21687 try to be a bit more fair.
21688 - Dir authorities and mirrors were never expiring the newest
21689 descriptor for each server, causing memory and directory bloat.
21690 - Fix memory-bloating and connection-bloating bug on servers: We
21691 were never closing any connection that had ever had a circuit on
21692 it, because we were checking conn->n_circuits == 0, yet we had a
21693 bug that let it go negative.
21694 - Make Tor work using squid as your http proxy again -- squid
21695 returns an error if you ask for a URL that's too long, and it uses
21696 a really generic error message. Plus, many people are behind a
21697 transparent squid so they don't even realize it.
21698 - On platforms that don't have getrlimit (like Windows), we were
21699 artificially constraining ourselves to a max of 1024
21700 connections. Now just assume that we can handle as many as 15000
21701 connections. Hopefully this won't cause other problems.
21702 - Add a new config option ExitPolicyRejectPrivate which defaults to
21703 1. This means all exit policies will begin with rejecting private
21704 addresses, unless the server operator explicitly turns it off.
21707 - Clients no longer download descriptors for non-running
21709 - Before we add new directory authorities, we should make it
21710 clear that only v1 authorities should receive/publish hidden
21711 service descriptors.
21714 - As soon as we've fetched some more directory info, immediately
21715 try to download more server descriptors. This way we don't have
21716 a 10 second pause during initial bootstrapping.
21717 - Remove even more loud log messages that the server operator can't
21719 - When we're running an obsolete or un-recommended version, make
21720 the log message more clear about what the problem is and what
21721 versions *are* still recommended.
21722 - Provide a more useful warn message when our onion queue gets full:
21723 the CPU is too slow or the exit policy is too liberal.
21724 - Don't warn when we receive a 503 from a dirserver/cache -- this
21725 will pave the way for them being able to refuse if they're busy.
21726 - When we fail to bind a listener, try to provide a more useful
21727 log message: e.g., "Is Tor already running?"
21728 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
21729 Goldberg can prove things about our handshake protocol more
21731 - MaxConn has been obsolete for a while now. Document the ConnLimit
21732 config option, which is a *minimum* number of file descriptors
21733 that must be available else Tor refuses to start.
21734 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
21735 if you log to syslog and want something other than LOG_DAEMON.
21736 - Make dirservers generate a separate "guard" flag to mean,
21737 "would make a good entry guard". Make clients parse it and vote
21738 on it. Not used by clients yet.
21739 - Implement --with-libevent-dir option to ./configure. Also, improve
21740 search techniques to find libevent, and use those for openssl too.
21741 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
21742 - Only start testing reachability once we've established a
21743 circuit. This will make startup on dirservers less noisy.
21744 - Don't try to upload hidden service descriptors until we have
21745 established a circuit.
21746 - Fix the controller's "attachstream 0" command to treat conn like
21747 it just connected, doing address remapping, handling .exit and
21748 .onion idioms, and so on. Now we're more uniform in making sure
21749 that the controller hears about new and closing connections.
21752 Changes in version 0.1.1.12-alpha - 2006-01-11
21753 o Bugfixes on 0.1.1.x:
21754 - The fix to close duplicate server connections was closing all
21755 Tor client connections if they didn't establish a circuit
21756 quickly enough. Oops.
21757 - Fix minor memory issue (double-free) that happened on exit.
21759 o Bugfixes on 0.1.0.x:
21760 - Tor didn't warn when it failed to open a log file.
21763 Changes in version 0.1.1.11-alpha - 2006-01-10
21764 o Crashes in 0.1.1.x:
21765 - Include all the assert/crash fixes from 0.1.0.16.
21766 - If you start Tor and then quit very quickly, there were some
21767 races that tried to free things that weren't allocated yet.
21768 - Fix a rare memory stomp if you're running hidden services.
21769 - Fix segfault when specifying DirServer in config without nickname.
21770 - Fix a seg fault when you finish connecting to a server but at
21771 that moment you dump his server descriptor.
21772 - Extendcircuit and Attachstream controller commands would
21773 assert/crash if you don't give them enough arguments.
21774 - Fix an assert error when we're out of space in the connection_list
21775 and we try to post a hidden service descriptor (reported by weasel).
21776 - If you specify a relative torrc path and you set RunAsDaemon in
21777 your torrc, then it chdir()'s to the new directory. If you HUP,
21778 it tries to load the new torrc location, fails, and exits.
21779 The fix: no longer allow a relative path to torrc using -f.
21782 - Implement "entry guards": automatically choose a handful of entry
21783 nodes and stick with them for all circuits. Only pick new guards
21784 when the ones you have are unsuitable, and if the old guards
21785 become suitable again, switch back. This will increase security
21786 dramatically against certain end-point attacks. The EntryNodes
21787 config option now provides some hints about which entry guards you
21788 want to use most; and StrictEntryNodes means to only use those.
21789 - New directory logic: download by descriptor digest, not by
21790 fingerprint. Caches try to download all listed digests from
21791 authorities; clients try to download "best" digests from caches.
21792 This avoids partitioning and isolating attacks better.
21793 - Make the "stable" router flag in network-status be the median of
21794 the uptimes of running valid servers, and make clients pay
21795 attention to the network-status flags. Thus the cutoff adapts
21796 to the stability of the network as a whole, making IRC, IM, etc
21797 connections more reliable.
21800 - Tor servers with dynamic IP addresses were needing to wait 18
21801 hours before they could start doing reachability testing using
21802 the new IP address and ports. This is because they were using
21803 the internal descriptor to learn what to test, yet they were only
21804 rebuilding the descriptor once they decided they were reachable.
21805 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
21806 to download certain server descriptors, throw them away, and then
21807 fetch them again after 30 minutes. Now mirrors throw away these
21808 server descriptors so clients can't get them.
21809 - We were leaving duplicate connections to other ORs open for a week,
21810 rather than closing them once we detect a duplicate. This only
21811 really affected authdirservers, but it affected them a lot.
21812 - Spread the authdirservers' reachability testing over the entire
21813 testing interval, so we don't try to do 500 TLS's at once every
21817 - If the network is down, and we try to connect to a conn because
21818 we have a circuit in mind, and we timeout (30 seconds) because the
21819 network never answers, we were expiring the circuit, but we weren't
21820 obsoleting the connection or telling the entry_guards functions.
21821 - Some Tor servers process billions of cells per day. These statistics
21822 need to be uint64_t's.
21823 - Check for integer overflows in more places, when adding elements
21824 to smartlists. This could possibly prevent a buffer overflow
21825 on malicious huge inputs. I don't see any, but I haven't looked
21827 - ReachableAddresses kept growing new "reject *:*" lines on every
21829 - When you "setconf log" via the controller, it should remove all
21830 logs. We were automatically adding back in a "log notice stdout".
21831 - Newly bootstrapped Tor networks couldn't establish hidden service
21832 circuits until they had nodes with high uptime. Be more tolerant.
21833 - We were marking servers down when they could not answer every piece
21834 of the directory request we sent them. This was far too harsh.
21835 - Fix the torify (tsocks) config file to not use Tor for localhost
21837 - Directory authorities now go to the proper authority when asking for
21838 a networkstatus, even when they want a compressed one.
21839 - Fix a harmless bug that was causing Tor servers to log
21840 "Got an end because of misc error, but we're not an AP. Closing."
21841 - Authorities were treating their own descriptor changes as cosmetic,
21842 meaning the descriptor available in the network-status and the
21843 descriptor that clients downloaded were different.
21844 - The OS X installer was adding a symlink for tor_resolve but
21845 the binary was called tor-resolve (reported by Thomas Hardly).
21846 - Workaround a problem with some http proxies where they refuse GET
21847 requests that specify "Content-Length: 0" (reported by Adrian).
21848 - Fix wrong log message when you add a "HiddenServiceNodes" config
21849 line without any HiddenServiceDir line (reported by Chris Thomas).
21852 - Write the TorVersion into the state file so we have a prayer of
21853 keeping forward and backward compatibility.
21854 - Revive the FascistFirewall config option rather than eliminating it:
21855 now it's a synonym for ReachableAddresses *:80,*:443.
21856 - Clients choose directory servers from the network status lists,
21857 not from their internal list of router descriptors. Now they can
21858 go to caches directly rather than needing to go to authorities
21860 - Directory authorities ignore router descriptors that have only
21861 cosmetic differences: do this for 0.1.0.x servers now too.
21862 - Add a new flag to network-status indicating whether the server
21863 can answer v2 directory requests too.
21864 - Authdirs now stop whining so loudly about bad descriptors that
21865 they fetch from other dirservers. So when there's a log complaint,
21866 it's for sure from a freshly uploaded descriptor.
21867 - Reduce memory requirements in our structs by changing the order
21869 - There used to be two ways to specify your listening ports in a
21870 server descriptor: on the "router" line and with a separate "ports"
21871 line. Remove support for the "ports" line.
21872 - New config option "AuthDirRejectUnlisted" for auth dirservers as
21873 a panic button: if we get flooded with unusable servers we can
21874 revert to only listing servers in the approved-routers file.
21875 - Auth dir servers can now mark a fingerprint as "!reject" or
21876 "!invalid" in the approved-routers file (as its nickname), to
21877 refuse descriptors outright or include them but marked as invalid.
21878 - Servers store bandwidth history across restarts/crashes.
21879 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
21880 get a better idea of why their circuits failed. Not used yet.
21881 - Directory mirrors now cache up to 16 unrecognized network-status
21882 docs. Now we can add new authdirservers and they'll be cached too.
21883 - When picking a random directory, prefer non-authorities if any
21885 - New controller option "getinfo desc/all-recent" to fetch the
21886 latest server descriptor for every router that Tor knows about.
21889 Changes in version 0.1.0.16 - 2006-01-02
21890 o Crash bugfixes on 0.1.0.x:
21891 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
21892 corrupting the heap, losing FDs, or crashing when we need to resize
21893 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
21894 - It turns out sparc64 platforms crash on unaligned memory access
21895 too -- so detect and avoid this.
21896 - Handle truncated compressed data correctly (by detecting it and
21898 - Fix possible-but-unlikely free(NULL) in control.c.
21899 - When we were closing connections, there was a rare case that
21900 stomped on memory, triggering seg faults and asserts.
21901 - Avoid potential infinite recursion when building a descriptor. (We
21902 don't know that it ever happened, but better to fix it anyway.)
21903 - We were neglecting to unlink marked circuits from soon-to-close OR
21904 connections, which caused some rare scribbling on freed memory.
21905 - Fix a memory stomping race bug when closing the joining point of two
21906 rendezvous circuits.
21907 - Fix an assert in time parsing found by Steven Murdoch.
21909 o Other bugfixes on 0.1.0.x:
21910 - When we're doing reachability testing, provide more useful log
21911 messages so the operator knows what to expect.
21912 - Do not check whether DirPort is reachable when we are suppressing
21913 advertising it because of hibernation.
21914 - When building with -static or on Solaris, we sometimes needed -ldl.
21915 - When we're deciding whether a stream has enough circuits around
21916 that can handle it, count the freshly dirty ones and not the ones
21917 that are so dirty they won't be able to handle it.
21918 - When we're expiring old circuits, we had a logic error that caused
21919 us to close new rendezvous circuits rather than old ones.
21920 - Give a more helpful log message when you try to change ORPort via
21921 the controller: you should upgrade Tor if you want that to work.
21922 - We were failing to parse Tor versions that start with "Tor ".
21923 - Tolerate faulty streams better: when a stream fails for reason
21924 exitpolicy, stop assuming that the router is lying about his exit
21925 policy. When a stream fails for reason misc, allow it to retry just
21926 as if it was resolvefailed. When a stream has failed three times,
21927 reset its failure count so we can try again and get all three tries.
21930 Changes in version 0.1.1.10-alpha - 2005-12-11
21931 o Correctness bugfixes on 0.1.0.x:
21932 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
21933 corrupting the heap, losing FDs, or crashing when we need to resize
21934 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
21935 - Stop doing the complex voodoo overkill checking for insecure
21936 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
21937 - When we were closing connections, there was a rare case that
21938 stomped on memory, triggering seg faults and asserts.
21939 - We were neglecting to unlink marked circuits from soon-to-close OR
21940 connections, which caused some rare scribbling on freed memory.
21941 - When we're deciding whether a stream has enough circuits around
21942 that can handle it, count the freshly dirty ones and not the ones
21943 that are so dirty they won't be able to handle it.
21944 - Recover better from TCP connections to Tor servers that are
21945 broken but don't tell you (it happens!); and rotate TLS
21946 connections once a week.
21947 - When we're expiring old circuits, we had a logic error that caused
21948 us to close new rendezvous circuits rather than old ones.
21949 - Fix a scary-looking but apparently harmless bug where circuits
21950 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
21951 servers, and never switch to state CIRCUIT_STATE_OPEN.
21952 - When building with -static or on Solaris, we sometimes needed to
21954 - Give a useful message when people run Tor as the wrong user,
21955 rather than telling them to start chowning random directories.
21956 - We were failing to inform the controller about new .onion streams.
21958 o Security bugfixes on 0.1.0.x:
21959 - Refuse server descriptors if the fingerprint line doesn't match
21960 the included identity key. Tor doesn't care, but other apps (and
21961 humans) might actually be trusting the fingerprint line.
21962 - We used to kill the circuit when we receive a relay command we
21963 don't recognize. Now we just drop it.
21964 - Start obeying our firewall options more rigorously:
21965 . If we can't get to a dirserver directly, try going via Tor.
21966 . Don't ever try to connect (as a client) to a place our
21967 firewall options forbid.
21968 . If we specify a proxy and also firewall options, obey the
21969 firewall options even when we're using the proxy: some proxies
21970 can only proxy to certain destinations.
21971 - Fix a bug found by Lasse Overlier: when we were making internal
21972 circuits (intended to be cannibalized later for rendezvous and
21973 introduction circuits), we were picking them so that they had
21974 useful exit nodes. There was no need for this, and it actually
21975 aids some statistical attacks.
21976 - Start treating internal circuits and exit circuits separately.
21977 It's important to keep them separate because internal circuits
21978 have their last hops picked like middle hops, rather than like
21979 exit hops. So exiting on them will break the user's expectations.
21981 o Bugfixes on 0.1.1.x:
21982 - Take out the mis-feature where we tried to detect IP address
21983 flapping for people with DynDNS, and chose not to upload a new
21984 server descriptor sometimes.
21985 - Try to be compatible with OpenSSL 0.9.6 again.
21986 - Log fix: when the controller is logging about .onion addresses,
21987 sometimes it didn't include the ".onion" part of the address.
21988 - Don't try to modify options->DirServers internally -- if the
21989 user didn't specify any, just add the default ones directly to
21990 the trusted dirserver list. This fixes a bug where people running
21991 controllers would use SETCONF on some totally unrelated config
21992 option, and Tor would start yelling at them about changing their
21994 - Let the controller's redirectstream command specify a port, in
21995 case the controller wants to change that too.
21996 - When we requested a pile of server descriptors, we sometimes
21997 accidentally launched a duplicate request for the first one.
21998 - Bugfix for trackhostexits: write down the fingerprint of the
21999 chosen exit, not its nickname, because the chosen exit might not
22001 - When parsing foo.exit, if foo is unknown, and we are leaving
22002 circuits unattached, set the chosen_exit field and leave the
22003 address empty. This matters because controllers got confused
22005 - Directory authorities no longer try to download server
22006 descriptors that they know they will reject.
22008 o Features and updates:
22009 - Replace balanced trees with hash tables: this should make stuff
22010 significantly faster.
22011 - Resume using the AES counter-mode implementation that we ship,
22012 rather than OpenSSL's. Ours is significantly faster.
22013 - Many other CPU and memory improvements.
22014 - Add a new config option FastFirstHopPK (on by default) so clients
22015 do a trivial crypto handshake for their first hop, since TLS has
22016 already taken care of confidentiality and authentication.
22017 - Add a new config option TestSocks so people can see if their
22018 applications are using socks4, socks4a, socks5-with-ip, or
22019 socks5-with-hostname. This way they don't have to keep mucking
22020 with tcpdump and wondering if something got cached somewhere.
22021 - Warn when listening on a public address for socks. I suspect a
22022 lot of people are setting themselves up as open socks proxies,
22023 and they have no idea that jerks on the Internet are using them,
22024 since they simply proxy the traffic into the Tor network.
22025 - Add "private:*" as an alias in configuration for policies. Now
22026 you can simplify your exit policy rather than needing to list
22027 every single internal or nonroutable network space.
22028 - Add a new controller event type that allows controllers to get
22029 all server descriptors that were uploaded to a router in its role
22030 as authoritative dirserver.
22031 - Start shipping socks-extensions.txt, tor-doc-unix.html,
22032 tor-doc-server.html, and stylesheet.css in the tarball.
22033 - Stop shipping tor-doc.html in the tarball.
22036 Changes in version 0.1.1.9-alpha - 2005-11-15
22037 o Usability improvements:
22038 - Start calling it FooListenAddress rather than FooBindAddress,
22039 since few of our users know what it means to bind an address
22041 - Reduce clutter in server logs. We're going to try to make
22042 them actually usable now. New config option ProtocolWarnings that
22043 lets you hear about how _other Tors_ are breaking the protocol. Off
22045 - Divide log messages into logging domains. Once we put some sort
22046 of interface on this, it will let people looking at more verbose
22047 log levels specify the topics they want to hear more about.
22048 - Make directory servers return better http 404 error messages
22049 instead of a generic "Servers unavailable".
22050 - Check for even more Windows version flags when writing the platform
22051 string in server descriptors, and note any we don't recognize.
22052 - Clean up more of the OpenSSL memory when exiting, so we can detect
22053 memory leaks better.
22054 - Make directory authorities be non-versioning, non-naming by
22055 default. Now we can add new directory servers without requiring
22056 their operators to pay close attention.
22057 - When logging via syslog, include the pid whenever we provide
22058 a log entry. Suggested by Todd Fries.
22060 o Performance improvements:
22061 - Directory servers now silently throw away new descriptors that
22062 haven't changed much if the timestamps are similar. We do this to
22063 tolerate older Tor servers that upload a new descriptor every 15
22064 minutes. (It seemed like a good idea at the time.)
22065 - Inline bottleneck smartlist functions; use fast versions by default.
22066 - Add a "Map from digest to void*" abstraction digestmap_t so we
22067 can do less hex encoding/decoding. Use it in router_get_by_digest()
22068 to resolve a performance bottleneck.
22069 - Allow tor_gzip_uncompress to extract as much as possible from
22070 truncated compressed data. Try to extract as many
22071 descriptors as possible from truncated http responses (when
22072 DIR_PURPOSE_FETCH_ROUTERDESC).
22073 - Make circ->onionskin a pointer, not a static array. moria2 was using
22074 125000 circuit_t's after it had been up for a few weeks, which
22075 translates to 20+ megs of wasted space.
22076 - The private half of our EDH handshake keys are now chosen out
22077 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
22079 o Security improvements:
22080 - Start making directory caches retain old routerinfos, so soon
22081 clients can start asking by digest of descriptor rather than by
22082 fingerprint of server.
22083 - Add half our entropy from RAND_poll in OpenSSL. This knows how
22084 to use egd (if present), openbsd weirdness (if present), vms/os2
22085 weirdness (if we ever port there), and more in the future.
22087 o Bugfixes on 0.1.0.x:
22088 - Do round-robin writes of at most 16 kB per write. This might be
22089 more fair on loaded Tor servers, and it might resolve our Windows
22090 crash bug. It might also slow things down.
22091 - Our TLS handshakes were generating a single public/private
22092 keypair for the TLS context, rather than making a new one for
22093 each new connections. Oops. (But we were still rotating them
22094 periodically, so it's not so bad.)
22095 - When we were cannibalizing a circuit with a particular exit
22096 node in mind, we weren't checking to see if that exit node was
22097 already present earlier in the circuit. Oops.
22098 - When a Tor server's IP changes (e.g. from a dyndns address),
22099 upload a new descriptor so clients will learn too.
22100 - Really busy servers were keeping enough circuits open on stable
22101 connections that they were wrapping around the circuit_id
22102 space. (It's only two bytes.) This exposed a bug where we would
22103 feel free to reuse a circuit_id even if it still exists but has
22104 been marked for close. Try to fix this bug. Some bug remains.
22105 - If we would close a stream early (e.g. it asks for a .exit that
22106 we know would refuse it) but the LeaveStreamsUnattached config
22107 option is set by the controller, then don't close it.
22109 o Bugfixes on 0.1.1.8-alpha:
22110 - Fix a big pile of memory leaks, some of them serious.
22111 - Do not try to download a routerdesc if we would immediately reject
22113 - Resume inserting a newline between all router descriptors when
22114 generating (old style) signed directories, since our spec says
22116 - When providing content-type application/octet-stream for
22117 server descriptors using .z, we were leaving out the
22118 content-encoding header. Oops. (Everything tolerated this just
22119 fine, but that doesn't mean we need to be part of the problem.)
22120 - Fix a potential seg fault in getconf and getinfo using version 1
22121 of the controller protocol.
22122 - Avoid crash: do not check whether DirPort is reachable when we
22123 are suppressing it because of hibernation.
22124 - Make --hash-password not crash on exit.
22127 Changes in version 0.1.1.8-alpha - 2005-10-07
22128 o New features (major):
22129 - Clients don't download or use the directory anymore. Now they
22130 download and use network-statuses from the trusted dirservers,
22131 and fetch individual server descriptors as needed from mirrors.
22132 See dir-spec.txt for all the gory details.
22133 - Be more conservative about whether to advertise our DirPort.
22134 The main change is to not advertise if we're running at capacity
22135 and either a) we could hibernate or b) our capacity is low and
22136 we're using a default DirPort.
22137 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
22139 o New features (minor):
22140 - Try to be smart about when to retry network-status and
22141 server-descriptor fetches. Still needs some tuning.
22142 - Stop parsing, storing, or using running-routers output (but
22143 mirrors still cache and serve it).
22144 - Consider a threshold of versioning dirservers (dirservers who have
22145 an opinion about which Tor versions are still recommended) before
22146 deciding whether to warn the user that he's obsolete.
22147 - Dirservers can now reject/invalidate by key and IP, with the
22148 config options "AuthDirInvalid" and "AuthDirReject". This is
22149 useful since currently we automatically list servers as running
22150 and usable even if we know they're jerks.
22151 - Provide dire warnings to any users who set DirServer; move it out
22152 of torrc.sample and into torrc.complete.
22153 - Add MyFamily to torrc.sample in the server section.
22154 - Add nicknames to the DirServer line, so we can refer to them
22155 without requiring all our users to memorize their IP addresses.
22156 - When we get an EOF or a timeout on a directory connection, note
22157 how many bytes of serverdesc we are dropping. This will help
22158 us determine whether it is smart to parse incomplete serverdesc
22160 - Add a new function to "change pseudonyms" -- that is, to stop
22161 using any currently-dirty circuits for new streams, so we don't
22162 link new actions to old actions. Currently it's only called on
22163 HUP (or SIGNAL RELOAD).
22164 - On sighup, if UseHelperNodes changed to 1, use new circuits.
22165 - Start using RAND_bytes rather than RAND_pseudo_bytes from
22166 OpenSSL. Also, reseed our entropy every hour, not just at
22167 startup. And entropy in 512-bit chunks, not 160-bit chunks.
22169 o Fixes on 0.1.1.7-alpha:
22170 - Nobody ever implemented EVENT_ADDRMAP for control protocol
22171 version 0, so don't let version 0 controllers ask for it.
22172 - If you requested something with too many newlines via the
22173 v1 controller protocol, you could crash tor.
22174 - Fix a number of memory leaks, including some pretty serious ones.
22175 - Re-enable DirPort testing again, so Tor servers will be willing
22176 to advertise their DirPort if it's reachable.
22177 - On TLS handshake, only check the other router's nickname against
22178 its expected nickname if is_named is set.
22180 o Fixes forward-ported from 0.1.0.15:
22181 - Don't crash when we don't have any spare file descriptors and we
22182 try to spawn a dns or cpu worker.
22183 - Make the numbers in read-history and write-history into uint64s,
22184 so they don't overflow and publish negatives in the descriptor.
22186 o Fixes on 0.1.0.x:
22187 - For the OS X package's modified privoxy config file, comment
22188 out the "logfile" line so we don't log everything passed
22190 - We were whining about using socks4 or socks5-with-local-lookup
22191 even when it's an IP in the "virtual" range we designed exactly
22193 - We were leaking some memory every time the client changes IPs.
22194 - Never call free() on tor_malloc()d memory. This will help us
22195 use dmalloc to detect memory leaks.
22196 - Check for named servers when looking them up by nickname;
22197 warn when we'recalling a non-named server by its nickname;
22198 don't warn twice about the same name.
22199 - Try to list MyFamily elements by key, not by nickname, and warn
22200 if we've not heard of the server.
22201 - Make windows platform detection (uname equivalent) smarter.
22202 - It turns out sparc64 doesn't like unaligned access either.
22205 Changes in version 0.1.0.15 - 2005-09-23
22206 o Bugfixes on 0.1.0.x:
22207 - Reject ports 465 and 587 (spam targets) in default exit policy.
22208 - Don't crash when we don't have any spare file descriptors and we
22209 try to spawn a dns or cpu worker.
22210 - Get rid of IgnoreVersion undocumented config option, and make us
22211 only warn, never exit, when we're running an obsolete version.
22212 - Don't try to print a null string when your server finds itself to
22213 be unreachable and the Address config option is empty.
22214 - Make the numbers in read-history and write-history into uint64s,
22215 so they don't overflow and publish negatives in the descriptor.
22216 - Fix a minor memory leak in smartlist_string_remove().
22217 - We were only allowing ourselves to upload a server descriptor at
22218 most every 20 minutes, even if it changed earlier than that.
22219 - Clean up log entries that pointed to old URLs.
22222 Changes in version 0.1.1.7-alpha - 2005-09-14
22223 o Fixes on 0.1.1.6-alpha:
22224 - Exit servers were crashing when people asked them to make a
22225 connection to an address not in their exit policy.
22226 - Looking up a non-existent stream for a v1 control connection would
22228 - Fix a seg fault if we ask a dirserver for a descriptor by
22229 fingerprint but he doesn't know about him.
22230 - SETCONF was appending items to linelists, not clearing them.
22231 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
22232 out and refuse the setconf if it would fail.
22233 - Downgrade the dirserver log messages when whining about
22237 - Add Peter Palfrader's check-tor script to tor/contrib/
22238 It lets you easily check whether a given server (referenced by
22239 nickname) is reachable by you.
22240 - Numerous changes to move towards client-side v2 directories. Not
22243 o Fixes on 0.1.0.x:
22244 - If the user gave tor an odd number of command-line arguments,
22245 we were silently ignoring the last one. Now we complain and fail.
22246 [This wins the oldest-bug prize -- this bug has been present since
22247 November 2002, as released in Tor 0.0.0.]
22248 - Do not use unaligned memory access on alpha, mips, or mipsel.
22249 It *works*, but is very slow, so we treat them as if it doesn't.
22250 - Retry directory requests if we fail to get an answer we like
22251 from a given dirserver (we were retrying before, but only if
22252 we fail to connect).
22253 - When writing the RecommendedVersions line, sort them first.
22254 - When the client asked for a rendezvous port that the hidden
22255 service didn't want to provide, we were sending an IP address
22256 back along with the end cell. Fortunately, it was zero. But stop
22258 - Correct "your server is reachable" log entries to indicate that
22259 it was self-testing that told us so.
22262 Changes in version 0.1.1.6-alpha - 2005-09-09
22263 o Fixes on 0.1.1.5-alpha:
22264 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
22265 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
22266 - Fix bug with tor_memmem finding a match at the end of the string.
22267 - Make unit tests run without segfaulting.
22268 - Resolve some solaris x86 compile warnings.
22269 - Handle duplicate lines in approved-routers files without warning.
22270 - Fix bug where as soon as a server refused any requests due to his
22271 exit policy (e.g. when we ask for localhost and he tells us that's
22272 127.0.0.1 and he won't do it), we decided he wasn't obeying his
22273 exit policy using him for any exits.
22274 - Only do openssl hardware accelerator stuff if openssl version is
22277 o New controller features/fixes:
22278 - Add a "RESETCONF" command so you can set config options like
22279 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
22280 a config option in the torrc with no value, then it clears it
22281 entirely (rather than setting it to its default).
22282 - Add a "GETINFO config-file" to tell us where torrc is.
22283 - Avoid sending blank lines when GETINFO replies should be empty.
22284 - Add a QUIT command for the controller (for using it manually).
22285 - Fix a bug in SAVECONF that was adding default dirservers and
22286 other redundant entries to the torrc file.
22288 o Start on the new directory design:
22289 - Generate, publish, cache, serve new network-status format.
22290 - Publish individual descriptors (by fingerprint, by "all", and by
22292 - Publish client and server recommended versions separately.
22293 - Allow tor_gzip_uncompress() to handle multiple concatenated
22294 compressed strings. Serve compressed groups of router
22295 descriptors. The compression logic here could be more
22297 - Distinguish v1 authorities (all currently trusted directories)
22298 from v2 authorities (all trusted directories).
22299 - Change DirServers config line to note which dirs are v1 authorities.
22300 - Add configuration option "V1AuthoritativeDirectory 1" which
22301 moria1, moria2, and tor26 should set.
22302 - Remove option when getting directory cache to see whether they
22303 support running-routers; they all do now. Replace it with one
22304 to see whether caches support v2 stuff.
22307 - Dirservers now do their own external reachability testing of each
22308 Tor server, and only list them as running if they've been found to
22309 be reachable. We also send back warnings to the server's logs if
22310 it uploads a descriptor that we already believe is unreachable.
22311 - Implement exit enclaves: if we know an IP address for the
22312 destination, and there's a running Tor server at that address
22313 which allows exit to the destination, then extend the circuit to
22314 that exit first. This provides end-to-end encryption and end-to-end
22315 authentication. Also, if the user wants a .exit address or enclave,
22316 use 4 hops rather than 3, and cannibalize a general circ for it
22318 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
22319 controller. Also, rotate dns and cpu workers if the controller
22320 changes options that will affect them; and initialize the dns
22321 worker cache tree whether or not we start out as a server.
22322 - Only upload a new server descriptor when options change, 18
22323 hours have passed, uptime is reset, or bandwidth changes a lot.
22324 - Check [X-]Forwarded-For headers in HTTP requests when generating
22325 log messages. This lets people run dirservers (and caches) behind
22326 Apache but still know which IP addresses are causing warnings.
22328 o Config option changes:
22329 - Replace (Fascist)Firewall* config options with a new
22330 ReachableAddresses option that understands address policies.
22331 For example, "ReachableAddresses *:80,*:443"
22332 - Get rid of IgnoreVersion undocumented config option, and make us
22333 only warn, never exit, when we're running an obsolete version.
22334 - Make MonthlyAccountingStart config option truly obsolete now.
22336 o Fixes on 0.1.0.x:
22337 - Reject ports 465 and 587 in the default exit policy, since
22338 people have started using them for spam too.
22339 - It turns out we couldn't bootstrap a network since we added
22340 reachability detection in 0.1.0.1-rc. Good thing the Tor network
22341 has never gone down. Add an AssumeReachable config option to let
22342 servers and dirservers bootstrap. When we're trying to build a
22343 high-uptime or high-bandwidth circuit but there aren't enough
22344 suitable servers, try being less picky rather than simply failing.
22345 - Our logic to decide if the OR we connected to was the right guy
22346 was brittle and maybe open to a mitm for unverified routers.
22347 - We weren't cannibalizing circuits correctly for
22348 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
22349 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
22350 build those from scratch. This should make hidden services faster.
22351 - Predict required circuits better, with an eye toward making hidden
22352 services faster on the service end.
22353 - Retry streams if the exit node sends back a 'misc' failure. This
22354 should result in fewer random failures. Also, after failing
22355 from resolve failed or misc, reset the num failures, so we give
22356 it a fair shake next time we try.
22357 - Clean up the rendezvous warn log msgs, and downgrade some to info.
22358 - Reduce severity on logs about dns worker spawning and culling.
22359 - When we're shutting down and we do something like try to post a
22360 server descriptor or rendezvous descriptor, don't complain that
22361 we seem to be unreachable. Of course we are, we're shutting down.
22362 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
22363 We don't use them yet, but maybe one day our DNS resolver will be
22364 able to discover them.
22365 - Make ContactInfo mandatory for authoritative directory servers.
22366 - Require server descriptors to list IPv4 addresses -- hostnames
22367 are no longer allowed. This also fixes some potential security
22368 problems with people providing hostnames as their address and then
22369 preferentially resolving them to partition users.
22370 - Change log line for unreachability to explicitly suggest /etc/hosts
22371 as the culprit. Also make it clearer what IP address and ports we're
22372 testing for reachability.
22373 - Put quotes around user-supplied strings when logging so users are
22374 more likely to realize if they add bad characters (like quotes)
22376 - Let auth dir servers start without specifying an Address config
22378 - Make unit tests (and other invocations that aren't the real Tor)
22379 run without launching listeners, creating subdirectories, and so on.
22382 Changes in version 0.1.1.5-alpha - 2005-08-08
22383 o Bugfixes included in 0.1.0.14.
22385 o Bugfixes on 0.1.0.x:
22386 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
22387 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
22388 it would silently using ignore the 6668.
22391 Changes in version 0.1.0.14 - 2005-08-08
22392 o Bugfixes on 0.1.0.x:
22393 - Fix the other half of the bug with crypto handshakes
22395 - Fix an assert trigger if you send a 'signal term' via the
22396 controller when it's listening for 'event info' messages.
22399 Changes in version 0.1.1.4-alpha - 2005-08-04
22400 o Bugfixes included in 0.1.0.13.
22403 - Improve tor_gettimeofday() granularity on windows.
22404 - Make clients regenerate their keys when their IP address changes.
22405 - Implement some more GETINFO goodness: expose helper nodes, config
22406 options, getinfo keys.
22409 Changes in version 0.1.0.13 - 2005-08-04
22410 o Bugfixes on 0.1.0.x:
22411 - Fix a critical bug in the security of our crypto handshakes.
22412 - Fix a size_t underflow in smartlist_join_strings2() that made
22413 it do bad things when you hand it an empty smartlist.
22414 - Fix Windows installer to ship Tor license (thanks to Aphex for
22415 pointing out this oversight) and put a link to the doc directory
22417 - Explicitly set no-unaligned-access for sparc: it turns out the
22418 new gcc's let you compile broken code, but that doesn't make it
22422 Changes in version 0.1.1.3-alpha - 2005-07-23
22423 o Bugfixes on 0.1.1.2-alpha:
22424 - Fix a bug in handling the controller's "post descriptor"
22426 - Fix several bugs in handling the controller's "extend circuit"
22428 - Fix a bug in handling the controller's "stream status" event.
22429 - Fix an assert failure if we have a controller listening for
22430 circuit events and we go offline.
22431 - Re-allow hidden service descriptors to publish 0 intro points.
22432 - Fix a crash when generating your hidden service descriptor if
22433 you don't have enough intro points already.
22435 o New features on 0.1.1.2-alpha:
22436 - New controller function "getinfo accounting", to ask how
22437 many bytes we've used in this time period.
22438 - Experimental support for helper nodes: a lot of the risk from
22439 a small static adversary comes because users pick new random
22440 nodes every time they rebuild a circuit. Now users will try to
22441 stick to the same small set of entry nodes if they can. Not
22442 enabled by default yet.
22444 o Bugfixes on 0.1.0.12:
22445 - If you're an auth dir server, always publish your dirport,
22446 even if you haven't yet found yourself to be reachable.
22447 - Fix a size_t underflow in smartlist_join_strings2() that made
22448 it do bad things when you hand it an empty smartlist.
22451 Changes in version 0.1.0.12 - 2005-07-18
22452 o New directory servers:
22453 - tor26 has changed IP address.
22455 o Bugfixes on 0.1.0.x:
22456 - Fix a possible double-free in tor_gzip_uncompress().
22457 - When --disable-threads is set, do not search for or link against
22458 pthreads libraries.
22459 - Don't trigger an assert if an authoritative directory server
22460 claims its dirport is 0.
22461 - Fix bug with removing Tor as an NT service: some people were
22462 getting "The service did not return an error." Thanks to Matt
22466 Changes in version 0.1.1.2-alpha - 2005-07-15
22467 o New directory servers:
22468 - tor26 has changed IP address.
22470 o Bugfixes on 0.1.0.x, crashes/leaks:
22471 - Port the servers-not-obeying-their-exit-policies fix from
22473 - Fix an fd leak in start_daemon().
22474 - On Windows, you can't always reopen a port right after you've
22475 closed it. So change retry_listeners() to only close and re-open
22476 ports that have changed.
22477 - Fix a possible double-free in tor_gzip_uncompress().
22479 o Bugfixes on 0.1.0.x, usability:
22480 - When tor_socketpair() fails in Windows, give a reasonable
22481 Windows-style errno back.
22482 - Let people type "tor --install" as well as "tor -install" when
22484 want to make it an NT service.
22485 - NT service patch from Matt Edman to improve error messages.
22486 - When the controller asks for a config option with an abbreviated
22487 name, give the full name in our response.
22488 - Correct the man page entry on TrackHostExitsExpire.
22489 - Looks like we were never delivering deflated (i.e. compressed)
22490 running-routers lists, even when asked. Oops.
22491 - When --disable-threads is set, do not search for or link against
22492 pthreads libraries.
22494 o Bugfixes on 0.1.1.x:
22495 - Fix a seg fault with autodetecting which controller version is
22499 - New hidden service descriptor format: put a version in it, and
22500 let people specify introduction/rendezvous points that aren't
22501 in "the directory" (which is subjective anyway).
22502 - Allow the DEBUG controller event to work again. Mark certain log
22503 entries as "don't tell this to controllers", so we avoid cycles.
22506 Changes in version 0.1.0.11 - 2005-06-30
22507 o Bugfixes on 0.1.0.x:
22508 - Fix major security bug: servers were disregarding their
22509 exit policies if clients behaved unexpectedly.
22510 - Make OS X init script check for missing argument, so we don't
22511 confuse users who invoke it incorrectly.
22512 - Fix a seg fault in "tor --hash-password foo".
22513 - The MAPADDRESS control command was broken.
22516 Changes in version 0.1.1.1-alpha - 2005-06-29
22518 - Make OS X init script check for missing argument, so we don't
22519 confuse users who invoke it incorrectly.
22520 - Fix a seg fault in "tor --hash-password foo".
22521 - Fix a possible way to DoS dirservers.
22522 - When we complain that your exit policy implicitly allows local or
22523 private address spaces, name them explicitly so operators can
22525 - Make the log message less scary when all the dirservers are
22526 temporarily unreachable.
22527 - We were printing the number of idle dns workers incorrectly when
22531 - Revised controller protocol (version 1) that uses ascii rather
22532 than binary. Add supporting libraries in python and java so you
22533 can use the controller from your applications without caring how
22534 our protocol works.
22535 - Spiffy new support for crypto hardware accelerators. Can somebody
22539 Changes in version 0.0.9.10 - 2005-06-16
22540 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
22541 - Refuse relay cells that claim to have a length larger than the
22542 maximum allowed. This prevents a potential attack that could read
22543 arbitrary memory (e.g. keys) from an exit server's process
22547 Changes in version 0.1.0.10 - 2005-06-14
22548 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
22549 libevent before 1.1a.
22552 Changes in version 0.1.0.9-rc - 2005-06-09
22554 - Reset buf->highwater every time buf_shrink() is called, not just on
22555 a successful shrink. This was causing significant memory bloat.
22556 - Fix buffer overflow when checking hashed passwords.
22557 - Security fix: if seeding the RNG on Win32 fails, quit.
22558 - Allow seeding the RNG on Win32 even when you're not running as
22560 - Disable threading on Solaris too. Something is wonky with it,
22561 cpuworkers, and reentrant libs.
22562 - Reenable the part of the code that tries to flush as soon as an
22563 OR outbuf has a full TLS record available. Perhaps this will make
22564 OR outbufs not grow as huge except in rare cases, thus saving lots
22565 of CPU time plus memory.
22566 - Reject malformed .onion addresses rather then passing them on as
22567 normal web requests.
22568 - Adapt patch from Adam Langley: fix possible memory leak in
22569 tor_lookup_hostname().
22570 - Initialize libevent later in the startup process, so the logs are
22571 already established by the time we start logging libevent warns.
22572 - Use correct errno on win32 if libevent fails.
22573 - Check and warn about known-bad/slow libevent versions.
22574 - Pay more attention to the ClientOnly config option.
22575 - Have torctl.in/tor.sh.in check for location of su binary (needed
22577 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
22578 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
22579 HttpProxyAuthenticator
22580 - Stop warning about sigpipes in the logs. We're going to
22581 pretend that getting these occassionally is normal and fine.
22582 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
22584 installer screens; and don't put stuff into StartupItems unless
22585 the user asks you to.
22586 - Require servers that use the default dirservers to have public IP
22587 addresses. We have too many servers that are configured with private
22588 IPs and their admins never notice the log entries complaining that
22589 their descriptors are being rejected.
22590 - Add OSX uninstall instructions. An actual uninstall script will
22594 Changes in version 0.1.0.8-rc - 2005-05-23
22596 - It turns out that kqueue on OS X 10.3.9 was causing kernel
22597 panics. Disable kqueue on all OS X Tors.
22598 - Fix RPM: remove duplicate line accidentally added to the rpm
22600 - Disable threads on openbsd too, since its gethostaddr is not
22602 - Tolerate libevent 0.8 since it still works, even though it's
22604 - Enable building on Red Hat 9.0 again.
22605 - Allow the middle hop of the testing circuit to be running any
22606 version, now that most of them have the bugfix to let them connect
22607 to unknown servers. This will allow reachability testing to work
22608 even when 0.0.9.7-0.0.9.9 become obsolete.
22609 - Handle relay cells with rh.length too large. This prevents
22610 a potential attack that could read arbitrary memory (maybe even
22611 keys) from the exit server's process.
22612 - We screwed up the dirport reachability testing when we don't yet
22613 have a cached version of the directory. Hopefully now fixed.
22614 - Clean up router_load_single_router() (used by the controller),
22615 so it doesn't seg fault on error.
22616 - Fix a minor memory leak when somebody establishes an introduction
22617 point at your Tor server.
22618 - If a socks connection ends because read fails, don't warn that
22619 you're not sending a socks reply back.
22622 - Add HttpProxyAuthenticator config option too, that works like
22623 the HttpsProxyAuthenticator config option.
22624 - Encode hashed controller passwords in hex instead of base64,
22625 to make it easier to write controllers.
22628 Changes in version 0.1.0.7-rc - 2005-05-17
22630 - Fix a bug in the OS X package installer that prevented it from
22631 installing on Tiger.
22632 - Fix a script bug in the OS X package installer that made it
22633 complain during installation.
22634 - Find libevent even if it's hiding in /usr/local/ and your
22635 CFLAGS and LDFLAGS don't tell you to look there.
22636 - Be able to link with libevent as a shared library (the default
22637 after 1.0d), even if it's hiding in /usr/local/lib and even
22638 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
22639 assuming you're running gcc. Otherwise fail and give a useful
22641 - Fix a bug in the RPM packager: set home directory for _tor to
22642 something more reasonable when first installing.
22643 - Free a minor amount of memory that is still reachable on exit.
22646 Changes in version 0.1.0.6-rc - 2005-05-14
22648 - Implement --disable-threads configure option. Disable threads on
22649 netbsd by default, because it appears to have no reentrant resolver
22651 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
22652 release (1.1) detects and disables kqueue if it's broken.
22653 - Append default exit policy before checking for implicit internal
22654 addresses. Now we don't log a bunch of complaints on startup
22655 when using the default exit policy.
22656 - Some people were putting "Address " in their torrc, and they had
22657 a buggy resolver that resolved " " to 0.0.0.0. Oops.
22658 - If DataDir is ~/.tor, and that expands to /.tor, then default to
22659 LOCALSTATEDIR/tor instead.
22660 - Fix fragmented-message bug in TorControl.py.
22661 - Resolve a minor bug which would prevent unreachable dirports
22662 from getting suppressed in the published descriptor.
22663 - When the controller gave us a new descriptor, we weren't resolving
22664 it immediately, so Tor would think its address was 0.0.0.0 until
22665 we fetched a new directory.
22666 - Fix an uppercase/lowercase case error in suppressing a bogus
22667 libevent warning on some Linuxes.
22670 - Begin scrubbing sensitive strings from logs by default. Turn off
22671 the config option SafeLogging if you need to do debugging.
22672 - Switch to a new buffer management algorithm, which tries to avoid
22673 reallocing and copying quite as much. In first tests it looks like
22674 it uses *more* memory on average, but less cpu.
22675 - First cut at support for "create-fast" cells. Clients can use
22676 these when extending to their first hop, since the TLS already
22677 provides forward secrecy and authentication. Not enabled on
22679 - When dirservers refuse a router descriptor, we now log its
22680 contactinfo, platform, and the poster's IP address.
22681 - Call tor_free_all instead of connections_free_all after forking, to
22682 save memory on systems that need to fork.
22683 - Whine at you if you're a server and you don't set your contactinfo.
22684 - Implement --verify-config command-line option to check if your torrc
22685 is valid without actually launching Tor.
22686 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
22687 rather than just rejecting it.
22690 Changes in version 0.1.0.5-rc - 2005-04-27
22692 - Stop trying to print a null pointer if an OR conn fails because
22693 we didn't like its cert.
22695 - Switch our internal buffers implementation to use a ring buffer,
22696 to hopefully improve performance for fast servers a lot.
22697 - Add HttpsProxyAuthenticator support (basic auth only), based
22698 on patch from Adam Langley.
22699 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
22700 the fast servers that have been joining lately.
22701 - Give hidden service accesses extra time on the first attempt,
22702 since 60 seconds is often only barely enough. This might improve
22704 - Improve performance for dirservers: stop re-parsing the whole
22705 directory every time you regenerate it.
22706 - Add more debugging info to help us find the weird dns freebsd
22707 pthreads bug; cleaner debug messages to help track future issues.
22710 Changes in version 0.0.9.9 - 2005-04-23
22711 o Bugfixes on 0.0.9.x:
22712 - If unofficial Tor clients connect and send weird TLS certs, our
22713 Tor server triggers an assert. This release contains a minimal
22714 backport from the broader fix that we put into 0.1.0.4-rc.
22717 Changes in version 0.1.0.4-rc - 2005-04-23
22719 - If unofficial Tor clients connect and send weird TLS certs, our
22720 Tor server triggers an assert. Stop asserting, and start handling
22721 TLS errors better in other situations too.
22722 - When the controller asks us to tell it about all the debug-level
22723 logs, it turns out we were generating debug-level logs while
22724 telling it about them, which turns into a bad loop. Now keep
22725 track of whether you're sending a debug log to the controller,
22726 and don't log when you are.
22727 - Fix the "postdescriptor" feature of the controller interface: on
22728 non-complete success, only say "done" once.
22730 - Clients are now willing to load balance over up to 2mB, not 1mB,
22731 of advertised bandwidth capacity.
22732 - Add a NoPublish config option, so you can be a server (e.g. for
22733 testing running Tor servers in other Tor networks) without
22734 publishing your descriptor to the primary dirservers.
22737 Changes in version 0.1.0.3-rc - 2005-04-08
22738 o Improvements on 0.1.0.2-rc:
22739 - Client now retries when streams end early for 'hibernating' or
22740 'resource limit' reasons, rather than failing them.
22741 - More automated handling for dirserver operators:
22742 - Automatically approve nodes running 0.1.0.2-rc or later,
22743 now that the the reachability detection stuff is working.
22744 - Now we allow two unverified servers with the same nickname
22745 but different keys. But if a nickname is verified, only that
22746 nickname+key are allowed.
22747 - If you're an authdirserver connecting to an address:port,
22748 and it's not the OR you were expecting, forget about that
22749 descriptor. If he *was* the one you were expecting, then forget
22750 about all other descriptors for that address:port.
22751 - Allow servers to publish descriptors from 12 hours in the future.
22752 Corollary: only whine about clock skew from the dirserver if
22753 he's a trusted dirserver (since now even verified servers could
22754 have quite wrong clocks).
22755 - Adjust maximum skew and age for rendezvous descriptors: let skew
22756 be 48 hours rather than 90 minutes.
22757 - Efficiency improvements:
22758 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
22759 it much faster to look up a circuit for each relay cell.
22760 - Remove most calls to assert_all_pending_dns_resolves_ok(),
22761 since they're eating our cpu on exit nodes.
22762 - Stop wasting time doing a case insensitive comparison for every
22763 dns name every time we do any lookup. Canonicalize the names to
22764 lowercase and be done with it.
22765 - Start sending 'truncated' cells back rather than destroy cells,
22766 if the circuit closes in front of you. This means we won't have
22767 to abandon partially built circuits.
22768 - Only warn once per nickname from add_nickname_list_to_smartlist
22769 per failure, so an entrynode or exitnode choice that's down won't
22771 - Put a note in the torrc about abuse potential with the default
22773 - Revise control spec and implementation to allow all log messages to
22774 be sent to controller with their severities intact (suggested by
22775 Matt Edman). Update TorControl to handle new log event types.
22776 - Provide better explanation messages when controller's POSTDESCRIPTOR
22778 - Stop putting nodename in the Platform string in server descriptors.
22779 It doesn't actually help, and it is confusing/upsetting some people.
22781 o Bugfixes on 0.1.0.2-rc:
22782 - We were printing the host mask wrong in exit policies in server
22783 descriptors. This isn't a critical bug though, since we were still
22784 obeying the exit policy internally.
22785 - Fix Tor when compiled with libevent but without pthreads: move
22786 connection_unregister() from _connection_free() to
22788 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
22789 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
22790 when we look through the connection array, we'll find any of the
22791 cpu/dnsworkers. This is no good.
22793 o Bugfixes on 0.0.9.8:
22794 - Fix possible bug on threading platforms (e.g. win32) which was
22795 leaking a file descriptor whenever a cpuworker or dnsworker died.
22796 - When using preferred entry or exit nodes, ignore whether the
22797 circuit wants uptime or capacity. They asked for the nodes, they
22799 - chdir() to your datadirectory at the *end* of the daemonize process,
22800 not the beginning. This was a problem because the first time you
22801 run tor, if your datadir isn't there, and you have runasdaemon set
22802 to 1, it will try to chdir to it before it tries to create it. Oops.
22803 - Handle changed router status correctly when dirserver reloads
22804 fingerprint file. We used to be dropping all unverified descriptors
22805 right then. The bug was hidden because we would immediately
22806 fetch a directory from another dirserver, which would include the
22807 descriptors we just dropped.
22808 - When we're connecting to an OR and he's got a different nickname/key
22809 than we were expecting, only complain loudly if we're an OP or a
22810 dirserver. Complaining loudly to the OR admins just confuses them.
22811 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
22812 artificially capped at 500kB.
22815 Changes in version 0.0.9.8 - 2005-04-07
22816 o Bugfixes on 0.0.9.x:
22817 - We have a bug that I haven't found yet. Sometimes, very rarely,
22818 cpuworkers get stuck in the 'busy' state, even though the cpuworker
22819 thinks of itself as idle. This meant that no new circuits ever got
22820 established. Here's a workaround to kill any cpuworker that's been
22821 busy for more than 100 seconds.
22824 Changes in version 0.1.0.2-rc - 2005-04-01
22825 o Bugfixes on 0.1.0.1-rc:
22826 - Fixes on reachability detection:
22827 - Don't check for reachability while hibernating.
22828 - If ORPort is reachable but DirPort isn't, still publish the
22829 descriptor, but zero out DirPort until it's found reachable.
22830 - When building testing circs for ORPort testing, use only
22831 high-bandwidth nodes, so fewer circuits fail.
22832 - Complain about unreachable ORPort separately from unreachable
22833 DirPort, so the user knows what's going on.
22834 - Make sure we only conclude ORPort reachability if we didn't
22835 initiate the conn. Otherwise we could falsely conclude that
22836 we're reachable just because we connected to the guy earlier
22837 and he used that same pipe to extend to us.
22838 - Authdirservers shouldn't do ORPort reachability detection,
22839 since they're in clique mode, so it will be rare to find a
22840 server not already connected to them.
22841 - When building testing circuits, always pick middle hops running
22842 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
22843 bug. (This is a kludge; it will go away when 0.0.9.x becomes
22845 - When we decide we're reachable, actually publish our descriptor
22847 - Fix bug in redirectstream in the controller.
22848 - Fix the state descriptor strings so logs don't claim edge streams
22849 are in a different state than they actually are.
22850 - Use recent libevent features when possible (this only really affects
22851 win32 and osx right now, because the new libevent with these
22852 features hasn't been released yet). Add code to suppress spurious
22854 - Prevent possible segfault in connection_close_unattached_ap().
22855 - Fix newlines on torrc in win32.
22856 - Improve error msgs when tor-resolve fails.
22858 o Improvements on 0.0.9.x:
22859 - New experimental script tor/contrib/ExerciseServer.py (needs more
22860 work) that uses the controller interface to build circuits and
22861 fetch pages over them. This will help us bootstrap servers that
22862 have lots of capacity but haven't noticed it yet.
22863 - New experimental script tor/contrib/PathDemo.py (needs more work)
22864 that uses the controller interface to let you choose whole paths
22866 "<hostname>.<path,separated by dots>.<length of path>.path"
22867 - When we've connected to an OR and handshaked but didn't like
22868 the result, we were closing the conn without sending destroy
22869 cells back for pending circuits. Now send those destroys.
22872 Changes in version 0.0.9.7 - 2005-04-01
22873 o Bugfixes on 0.0.9.x:
22874 - Fix another race crash bug (thanks to Glenn Fink for reporting).
22875 - Compare identity to identity, not to nickname, when extending to
22876 a router not already in the directory. This was preventing us from
22877 extending to unknown routers. Oops.
22878 - Make sure to create OS X Tor user in <500 range, so we aren't
22879 creating actual system users.
22880 - Note where connection-that-hasn't-sent-end was marked, and fix
22881 a few really loud instances of this harmless bug (it's fixed more
22885 Changes in version 0.1.0.1-rc - 2005-03-28
22887 - Add reachability testing. Your Tor server will automatically try
22888 to see if its ORPort and DirPort are reachable from the outside,
22889 and it won't upload its descriptor until it decides they are.
22890 - Handle unavailable hidden services better. Handle slow or busy
22891 hidden services better.
22892 - Add support for CONNECTing through https proxies, with "HttpsProxy"
22894 - New exit policy: accept most low-numbered ports, rather than
22895 rejecting most low-numbered ports.
22896 - More Tor controller support (still experimental). See
22897 http://tor.eff.org/doc/control-spec.txt for all the new features,
22898 including signals to emulate unix signals from any platform;
22899 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
22900 closestream; closecircuit; etc.
22901 - Make nt services work and start on startup on win32 (based on
22902 patch by Matt Edman).
22903 - Add a new AddressMap config directive to rewrite incoming socks
22904 addresses. This lets you, for example, declare an implicit
22905 required exit node for certain sites.
22906 - Add a new TrackHostExits config directive to trigger addressmaps
22907 for certain incoming socks addresses -- for sites that break when
22908 your exit keeps changing (based on patch by Mike Perry).
22909 - Redo the client-side dns cache so it's just an addressmap too.
22910 - Notice when our IP changes, and reset stats/uptime/reachability.
22911 - When an application is using socks5, give him the whole variety of
22912 potential socks5 responses (connect refused, host unreachable, etc),
22913 rather than just "success" or "failure".
22914 - A more sane version numbering system. See
22915 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
22916 - New contributed script "exitlist": a simple python script to
22917 parse directories and find Tor nodes that exit to listed
22919 - New contributed script "privoxy-tor-toggle" to toggle whether
22920 Privoxy uses Tor. Seems to be configured for Debian by default.
22921 - Report HTTP reasons to client when getting a response from directory
22922 servers -- so you can actually know what went wrong.
22923 - New config option MaxAdvertisedBandwidth which lets you advertise
22924 a low bandwidthrate (to not attract as many circuits) while still
22925 allowing a higher bandwidthrate in reality.
22927 o Robustness/stability fixes:
22928 - Make Tor use Niels Provos's libevent instead of its current
22929 poll-but-sometimes-select mess. This will let us use faster async
22930 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
22932 - pthread support now too. This was forced because when we forked,
22933 we ended up wasting a lot of duplicate ram over time. Also switch
22934 to foo_r versions of some library calls to allow reentry and
22936 - Better handling for heterogeneous / unreliable nodes:
22937 - Annotate circuits w/ whether they aim to contain high uptime nodes
22938 and/or high capacity nodes. When building circuits, choose
22940 - This means that every single node in an intro rend circuit,
22941 not just the last one, will have a minimum uptime.
22942 - New config option LongLivedPorts to indicate application streams
22943 that will want high uptime circuits.
22944 - Servers reset uptime when a dir fetch entirely fails. This
22945 hopefully reflects stability of the server's network connectivity.
22946 - If somebody starts his tor server in Jan 2004 and then fixes his
22947 clock, don't make his published uptime be a year.
22948 - Reset published uptime when you wake up from hibernation.
22949 - Introduce a notion of 'internal' circs, which are chosen without
22950 regard to the exit policy of the last hop. Intro and rendezvous
22951 circs must be internal circs, to avoid leaking information. Resolve
22952 and connect streams can use internal circs if they want.
22953 - New circuit pooling algorithm: make sure to have enough circs around
22954 to satisfy any predicted ports, and also make sure to have 2 internal
22955 circs around if we've required internal circs lately (and with high
22956 uptime if we've seen that lately too).
22957 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
22958 which describes how often we retry making new circuits if current
22959 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
22960 how long we're willing to make use of an already-dirty circuit.
22961 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
22962 circ as necessary, if there are any completed ones lying around
22963 when we try to launch one.
22964 - Make hidden services try to establish a rendezvous for 30 seconds,
22965 rather than for n (where n=3) attempts to build a circuit.
22966 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
22967 "ShutdownWaitLength".
22968 - Try to be more zealous about calling connection_edge_end when
22969 things go bad with edge conns in connection.c.
22970 - Revise tor-spec to add more/better stream end reasons.
22971 - Revise all calls to connection_edge_end to avoid sending "misc",
22972 and to take errno into account where possible.
22975 - Fix a race condition that can trigger an assert, when we have a
22976 pending create cell and an OR connection fails right then.
22977 - Fix several double-mark-for-close bugs, e.g. where we were finding
22978 a conn for a cell even if that conn is already marked for close.
22979 - Make sequence of log messages when starting on win32 with no config
22980 file more reasonable.
22981 - When choosing an exit node for a new non-internal circ, don't take
22982 into account whether it'll be useful for any pending x.onion
22983 addresses -- it won't.
22984 - Turn addr_policy_compare from a tristate to a quadstate; this should
22985 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
22986 for google.com" problem.
22987 - Make "platform" string in descriptor more accurate for Win32 servers,
22988 so it's not just "unknown platform".
22989 - Fix an edge case in parsing config options (thanks weasel).
22990 If they say "--" on the commandline, it's not an option.
22991 - Reject odd-looking addresses at the client (e.g. addresses that
22992 contain a colon), rather than having the server drop them because
22994 - tor-resolve requests were ignoring .exit if there was a working circuit
22995 they could use instead.
22996 - REUSEADDR on normal platforms means you can rebind to the port
22997 right after somebody else has let it go. But REUSEADDR on win32
22998 means to let you bind to the port _even when somebody else
22999 already has it bound_! So, don't do that on Win32.
23000 - Change version parsing logic: a version is "obsolete" if it is not
23001 recommended and (1) there is a newer recommended version in the
23002 same series, or (2) there are no recommended versions in the same
23003 series, but there are some recommended versions in a newer series.
23004 A version is "new" if it is newer than any recommended version in
23006 - Stop most cases of hanging up on a socks connection without sending
23010 - Require BandwidthRate to be at least 20kB/s for servers.
23011 - When a dirserver causes you to give a warn, mention which dirserver
23013 - New config option DirAllowPrivateAddresses for authdirservers.
23014 Now by default they refuse router descriptors that have non-IP or
23015 private-IP addresses.
23016 - Stop publishing socksport in the directory, since it's not
23017 actually meant to be public. For compatibility, publish a 0 there
23019 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
23020 smart" value, that is low for servers and high for clients.
23021 - If our clock jumps forward by 100 seconds or more, assume something
23022 has gone wrong with our network and abandon all not-yet-used circs.
23023 - Warn when exit policy implicitly allows local addresses.
23024 - If we get an incredibly skewed timestamp from a dirserver mirror
23025 that isn't a verified OR, don't warn -- it's probably him that's
23027 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
23028 cookies to disk and doesn't log each web request to disk. (Thanks
23029 to Brett Carrington for pointing this out.)
23030 - When a client asks us for a dir mirror and we don't have one,
23031 launch an attempt to get a fresh one.
23032 - If we're hibernating and we get a SIGINT, exit immediately.
23033 - Add --with-dmalloc ./configure option, to track memory leaks.
23034 - And try to free all memory on closing, so we can detect what
23036 - Cache local dns resolves correctly even when they're .exit
23038 - Give a better warning when some other server advertises an
23039 ORPort that is actually an apache running ssl.
23040 - Add "opt hibernating 1" to server descriptor to make it clearer
23041 whether the server is hibernating.
23044 Changes in version 0.0.9.6 - 2005-03-24
23045 o Bugfixes on 0.0.9.x (crashes and asserts):
23046 - Add new end stream reasons to maintainance branch. Fix bug where
23047 reason (8) could trigger an assert. Prevent bug from recurring.
23048 - Apparently win32 stat wants paths to not end with a slash.
23049 - Fix assert triggers in assert_cpath_layer_ok(), where we were
23050 blowing away the circuit that conn->cpath_layer points to, then
23051 checking to see if the circ is well-formed. Backport check to make
23052 sure we dont use the cpath on a closed connection.
23053 - Prevent circuit_resume_edge_reading_helper() from trying to package
23054 inbufs for marked-for-close streams.
23055 - Don't crash on hup if your options->address has become unresolvable.
23056 - Some systems (like OS X) sometimes accept() a connection and tell
23057 you the remote host is 0.0.0.0:0. If this happens, due to some
23058 other mis-features, we get confused; so refuse the conn for now.
23060 o Bugfixes on 0.0.9.x (other):
23061 - Fix harmless but scary "Unrecognized content encoding" warn message.
23062 - Add new stream error reason: TORPROTOCOL reason means "you are not
23063 speaking a version of Tor I understand; say bye-bye to your stream."
23064 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
23065 into the future, now that we are more tolerant of skew. This
23066 resolves a bug where a Tor server would refuse to cache a directory
23067 because all the directories it gets are too far in the future;
23068 yet the Tor server never logs any complaints about clock skew.
23069 - Mac packaging magic: make man pages useable, and do not overwrite
23070 existing torrc files.
23071 - Make OS X log happily to /var/log/tor/tor.log
23074 Changes in version 0.0.9.5 - 2005-02-22
23075 o Bugfixes on 0.0.9.x:
23076 - Fix an assert race at exit nodes when resolve requests fail.
23077 - Stop picking unverified dir mirrors--it only leads to misery.
23078 - Patch from Matt Edman to make NT services work better. Service
23079 support is still not compiled into the executable by default.
23080 - Patch from Dmitri Bely so the Tor service runs better under
23081 the win32 SYSTEM account.
23082 - Make tor-resolve actually work (?) on Win32.
23083 - Fix a sign bug when getrlimit claims to have 4+ billion
23084 file descriptors available.
23085 - Stop refusing to start when bandwidthburst == bandwidthrate.
23086 - When create cells have been on the onion queue more than five
23087 seconds, just send back a destroy and take them off the list.
23090 Changes in version 0.0.9.4 - 2005-02-03
23091 o Bugfixes on 0.0.9:
23092 - Fix an assert bug that took down most of our servers: when
23093 a server claims to have 1 GB of bandwidthburst, don't
23095 - Don't crash as badly if we have spawned the max allowed number
23096 of dnsworkers, or we're out of file descriptors.
23097 - Block more file-sharing ports in the default exit policy.
23098 - MaxConn is now automatically set to the hard limit of max
23099 file descriptors we're allowed (ulimit -n), minus a few for
23101 - Give a clearer message when servers need to raise their
23102 ulimit -n when they start running out of file descriptors.
23103 - SGI Compatibility patches from Jan Schaumann.
23104 - Tolerate a corrupt cached directory better.
23105 - When a dirserver hasn't approved your server, list which one.
23106 - Go into soft hibernation after 95% of the bandwidth is used,
23107 not 99%. This is especially important for daily hibernators who
23108 have a small accounting max. Hopefully it will result in fewer
23109 cut connections when the hard hibernation starts.
23110 - Load-balance better when using servers that claim more than
23111 800kB/s of capacity.
23112 - Make NT services work (experimental, only used if compiled in).
23115 Changes in version 0.0.9.3 - 2005-01-21
23116 o Bugfixes on 0.0.9:
23117 - Backport the cpu use fixes from main branch, so busy servers won't
23118 need as much processor time.
23119 - Work better when we go offline and then come back, or when we
23120 run Tor at boot before the network is up. We do this by
23121 optimistically trying to fetch a new directory whenever an
23122 application request comes in and we think we're offline -- the
23123 human is hopefully a good measure of when the network is back.
23124 - Backport some minimal hidserv bugfixes: keep rend circuits open as
23125 long as you keep using them; actually publish hidserv descriptors
23126 shortly after they change, rather than waiting 20-40 minutes.
23127 - Enable Mac startup script by default.
23128 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
23129 - When you update AllowUnverifiedNodes or FirewallPorts via the
23130 controller's setconf feature, we were always appending, never
23132 - When you update HiddenServiceDir via setconf, it was screwing up
23133 the order of reading the lines, making it fail.
23134 - Do not rewrite a cached directory back to the cache; otherwise we
23135 will think it is recent and not fetch a newer one on startup.
23136 - Workaround for webservers that lie about Content-Encoding: Tor
23137 now tries to autodetect compressed directories and compression
23138 itself. This lets us Proxypass dir fetches through apache.
23141 Changes in version 0.0.9.2 - 2005-01-04
23142 o Bugfixes on 0.0.9 (crashes and asserts):
23143 - Fix an assert on startup when the disk is full and you're logging
23145 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
23146 style address, then we'd crash.
23147 - Fix an assert trigger when the running-routers string we get from
23148 a dirserver is broken.
23149 - Make worker threads start and run on win32. Now win32 servers
23151 - Bandaid (not actually fix, but now it doesn't crash) an assert
23152 where the dns worker dies mysteriously and the main Tor process
23153 doesn't remember anything about the address it was resolving.
23155 o Bugfixes on 0.0.9 (Win32):
23156 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
23157 name out of the warning/assert messages.
23158 - Fix a superficial "unhandled error on read" bug on win32.
23159 - The win32 installer no longer requires a click-through for our
23160 license, since our Free Software license grants rights but does not
23162 - Win32: When connecting to a dirserver fails, try another one
23163 immediately. (This was already working for non-win32 Tors.)
23164 - Stop trying to parse $HOME on win32 when hunting for default
23166 - Make tor-resolve.c work on win32 by calling network_init().
23168 o Bugfixes on 0.0.9 (other):
23169 - Make 0.0.9.x build on Solaris again.
23170 - Due to a fencepost error, we were blowing away the \n when reporting
23171 confvalue items in the controller. So asking for multiple config
23172 values at once couldn't work.
23173 - When listing circuits that are pending on an opening OR connection,
23174 if we're an OR we were listing circuits that *end* at us as
23175 being pending on every listener, dns/cpu worker, etc. Stop that.
23176 - Dirservers were failing to create 'running-routers' or 'directory'
23177 strings if we had more than some threshold of routers. Fix them so
23178 they can handle any number of routers.
23179 - Fix a superficial "Duplicate mark for close" bug.
23180 - Stop checking for clock skew for OR connections, even for servers.
23181 - Fix a fencepost error that was chopping off the last letter of any
23182 nickname that is the maximum allowed nickname length.
23183 - Update URLs in log messages so they point to the new website.
23184 - Fix a potential problem in mangling server private keys while
23185 writing to disk (not triggered yet, as far as we know).
23186 - Include the licenses for other free software we include in Tor,
23187 now that we're shipping binary distributions more regularly.
23190 Changes in version 0.0.9.1 - 2004-12-15
23191 o Bugfixes on 0.0.9:
23192 - Make hibernation actually work.
23193 - Make HashedControlPassword config option work.
23194 - When we're reporting event circuit status to a controller,
23195 don't use the stream status code.
23198 Changes in version 0.0.9 - 2004-12-12
23200 - Clean up manpage and torrc.sample file.
23201 - Clean up severities and text of log warnings.
23203 - Make servers trigger an assert when they enter hibernation.
23206 Changes in version 0.0.9rc7 - 2004-12-08
23207 o Bugfixes on 0.0.9rc:
23208 - Fix a stack-trashing crash when an exit node begins hibernating.
23209 - Avoid looking at unallocated memory while considering which
23210 ports we need to build circuits to cover.
23211 - Stop a sigpipe: when an 'end' cell races with eof from the app,
23212 we shouldn't hold-open-until-flush if the eof arrived first.
23213 - Fix a bug with init_cookie_authentication() in the controller.
23214 - When recommending new-format log lines, if the upper bound is
23215 LOG_ERR, leave it implicit.
23217 o Bugfixes on 0.0.8.1:
23218 - Fix a whole slew of memory leaks.
23219 - Fix isspace() and friends so they still make Solaris happy
23220 but also so they don't trigger asserts on win32.
23221 - Fix parse_iso_time on platforms without strptime (eg win32).
23222 - win32: tolerate extra "readable" events better.
23223 - win32: when being multithreaded, leave parent fdarray open.
23224 - Make unit tests work on win32.
23227 Changes in version 0.0.9rc6 - 2004-12-06
23228 o Bugfixes on 0.0.9pre:
23229 - Clean up some more integer underflow opportunities (not exploitable
23231 - While hibernating, hup should not regrow our listeners.
23232 - Send an end to the streams we close when we hibernate, rather
23233 than just chopping them off.
23234 - React to eof immediately on non-open edge connections.
23236 o Bugfixes on 0.0.8.1:
23237 - Calculate timeout for waiting for a connected cell from the time
23238 we sent the begin cell, not from the time the stream started. If
23239 it took a long time to establish the circuit, we would time out
23240 right after sending the begin cell.
23241 - Fix router_compare_addr_to_addr_policy: it was not treating a port
23242 of * as always matching, so we were picking reject *:* nodes as
23243 exit nodes too. Oops.
23246 - New circuit building strategy: keep a list of ports that we've
23247 used in the past 6 hours, and always try to have 2 circuits open
23248 or on the way that will handle each such port. Seed us with port
23249 80 so web users won't complain that Tor is "slow to start up".
23250 - Make kill -USR1 dump more useful stats about circuits.
23251 - When warning about retrying or giving up, print the address, so
23252 the user knows which one it's talking about.
23253 - If you haven't used a clean circuit in an hour, throw it away,
23254 just to be on the safe side. (This means after 6 hours a totally
23255 unused Tor client will have no circuits open.)
23258 Changes in version 0.0.9rc5 - 2004-12-01
23259 o Bugfixes on 0.0.8.1:
23260 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
23261 - Let resolve conns retry/expire also, rather than sticking around
23263 - If we are using select, make sure we stay within FD_SETSIZE.
23265 o Bugfixes on 0.0.9pre:
23266 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
23267 but doesn't seem to be currently; thanks to Ilja van Sprundel for
23269 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
23270 instead. Impose minima and maxima for all *Period options; impose
23271 even tighter maxima for fetching if we are a caching dirserver.
23272 Clip rather than rejecting.
23273 - Fetch cached running-routers from servers that serve it (that is,
23274 authdirservers and servers running 0.0.9rc5-cvs or later.)
23277 - Accept *:706 (silc) in default exit policy.
23278 - Implement new versioning format for post 0.1.
23279 - Support "foo.nickname.exit" addresses, to let Alice request the
23280 address "foo" as viewed by exit node "nickname". Based on a patch
23282 - Make tor --version --version dump the cvs Id of every file.
23285 Changes in version 0.0.9rc4 - 2004-11-28
23286 o Bugfixes on 0.0.8.1:
23287 - Make windows sockets actually non-blocking (oops), and handle
23288 win32 socket errors better.
23290 o Bugfixes on 0.0.9rc1:
23291 - Actually catch the -USR2 signal.
23294 Changes in version 0.0.9rc3 - 2004-11-25
23295 o Bugfixes on 0.0.8.1:
23296 - Flush the log file descriptor after we print "Tor opening log file",
23297 so we don't see those messages days later.
23299 o Bugfixes on 0.0.9rc1:
23300 - Make tor-resolve work again.
23301 - Avoid infinite loop in tor-resolve if tor hangs up on it.
23302 - Fix an assert trigger for clients/servers handling resolves.
23305 Changes in version 0.0.9rc2 - 2004-11-24
23306 o Bugfixes on 0.0.9rc1:
23307 - I broke socks5 support while fixing the eof bug.
23308 - Allow unitless bandwidths and intervals; they default to bytes
23310 - New servers don't start out hibernating; they are active until
23311 they run out of bytes, so they have a better estimate of how
23312 long it takes, and so their operators can know they're working.
23315 Changes in version 0.0.9rc1 - 2004-11-23
23316 o Bugfixes on 0.0.8.1:
23317 - Finally fix a bug that's been plaguing us for a year:
23318 With high load, circuit package window was reaching 0. Whenever
23319 we got a circuit-level sendme, we were reading a lot on each
23320 socket, but only writing out a bit. So we would eventually reach
23321 eof. This would be noticed and acted on even when there were still
23322 bytes sitting in the inbuf.
23323 - When poll() is interrupted, we shouldn't believe the revents values.
23325 o Bugfixes on 0.0.9pre6:
23326 - Fix hibernate bug that caused pre6 to be broken.
23327 - Don't keep rephist info for routers that haven't had activity for
23328 24 hours. (This matters now that clients have keys, since we track
23330 - Never call close_temp_logs while validating log options.
23331 - Fix backslash-escaping on tor.sh.in and torctl.in.
23334 - Implement weekly/monthly/daily accounting: now you specify your
23335 hibernation properties by
23336 AccountingMax N bytes|KB|MB|GB|TB
23337 AccountingStart day|week|month [day] HH:MM
23338 Defaults to "month 1 0:00".
23339 - Let bandwidth and interval config options be specified as 5 bytes,
23340 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
23341 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
23342 get back to normal.)
23343 - If your requested entry or exit node has advertised bandwidth 0,
23345 - Be more greedy about filling up relay cells -- we try reading again
23346 once we've processed the stuff we read, in case enough has arrived
23347 to fill the last cell completely.
23348 - Apply NT service patch from Osamu Fujino. Still needs more work.
23351 Changes in version 0.0.9pre6 - 2004-11-15
23352 o Bugfixes on 0.0.8.1:
23353 - Fix assert failure on malformed socks4a requests.
23354 - Use identity comparison, not nickname comparison, to choose which
23355 half of circuit-ID-space each side gets to use. This is needed
23356 because sometimes we think of a router as a nickname, and sometimes
23357 as a hex ID, and we can't predict what the other side will do.
23358 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
23359 write() call will fail and we handle it there.
23360 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
23361 and smartlist_len, which are two major profiling offenders.
23363 o Bugfixes on 0.0.9pre5:
23364 - Fix a bug in read_all that was corrupting config files on windows.
23365 - When we're raising the max number of open file descriptors to
23366 'unlimited', don't log that we just raised it to '-1'.
23367 - Include event code with events, as required by control-spec.txt.
23368 - Don't give a fingerprint when clients do --list-fingerprint:
23369 it's misleading, because it will never be the same again.
23370 - Stop using strlcpy in tor_strndup, since it was slowing us
23372 - Remove warn on startup about missing cached-directory file.
23373 - Make kill -USR1 work again.
23374 - Hibernate if we start tor during the "wait for wakeup-time" phase
23375 of an accounting interval. Log our hibernation plans better.
23376 - Authoritative dirservers now also cache their directory, so they
23377 have it on start-up.
23380 - Fetch running-routers; cache running-routers; compress
23381 running-routers; serve compressed running-routers.z
23382 - Add NSI installer script contributed by J Doe.
23383 - Commit VC6 and VC7 workspace/project files.
23384 - Commit a tor.spec for making RPM files, with help from jbash.
23385 - Add contrib/torctl.in contributed by Glenn Fink.
23386 - Implement the control-spec's SAVECONF command, to write your
23387 configuration to torrc.
23388 - Get cookie authentication for the controller closer to working.
23389 - Include control-spec.txt in the tarball.
23390 - When set_conf changes our server descriptor, upload a new copy.
23391 But don't upload it too often if there are frequent changes.
23392 - Document authentication config in man page, and document signals
23394 - Clean up confusing parts of man page and torrc.sample.
23395 - Make expand_filename handle ~ and ~username.
23396 - Use autoconf to enable largefile support where necessary. Use
23397 ftello where available, since ftell can fail at 2GB.
23398 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
23399 log more informatively.
23400 - Give a slightly more useful output for "tor -h".
23401 - Refuse application socks connections to port 0.
23402 - Check clock skew for verified servers, but allow unverified
23403 servers and clients to have any clock skew.
23404 - Break DirFetchPostPeriod into:
23405 - DirFetchPeriod for fetching full directory,
23406 - StatusFetchPeriod for fetching running-routers,
23407 - DirPostPeriod for posting server descriptor,
23408 - RendPostPeriod for posting hidden service descriptors.
23409 - Make sure the hidden service descriptors are at a random offset
23410 from each other, to hinder linkability.
23413 Changes in version 0.0.9pre5 - 2004-11-09
23414 o Bugfixes on 0.0.9pre4:
23415 - Fix a seg fault in unit tests (doesn't affect main program).
23416 - Fix an assert bug where a hidden service provider would fail if
23417 the first hop of his rendezvous circuit was down.
23418 - Hidden service operators now correctly handle version 1 style
23419 INTRODUCE1 cells (nobody generates them still, so not a critical
23421 - If do_hup fails, actually notice.
23422 - Handle more errnos from accept() without closing the listener.
23423 Some OpenBSD machines were closing their listeners because
23424 they ran out of file descriptors.
23425 - Send resolve cells to exit routers that are running a new
23426 enough version of the resolve code to work right.
23427 - Better handling of winsock includes on non-MSV win32 compilers.
23428 - Some people had wrapped their tor client/server in a script
23429 that would restart it whenever it died. This did not play well
23430 with our "shut down if your version is obsolete" code. Now people
23431 don't fetch a new directory if their local cached version is
23433 - Make our autogen.sh work on ksh as well as bash.
23436 - Hibernation: New config option "AccountingMaxKB" lets you
23437 set how many KBytes per month you want to allow your server to
23438 consume. Rather than spreading those bytes out evenly over the
23439 month, we instead hibernate for some of the month and pop up
23440 at a deterministic time, work until the bytes are consumed, then
23441 hibernate again. Config option "MonthlyAccountingStart" lets you
23442 specify which day of the month your billing cycle starts on.
23443 - Control interface: a separate program can now talk to your
23444 client/server over a socket, and get/set config options, receive
23445 notifications of circuits and streams starting/finishing/dying,
23446 bandwidth used, etc. The next step is to get some GUIs working.
23447 Let us know if you want to help out. See doc/control-spec.txt .
23448 - Ship a contrib/tor-control.py as an example script to interact
23449 with the control port.
23450 - "tor --hash-password zzyxz" will output a salted password for
23451 use in authenticating to the control interface.
23452 - New log format in config:
23453 "Log minsev[-maxsev] stdout|stderr|syslog" or
23454 "Log minsev[-maxsev] file /var/foo"
23457 - DirPolicy config option, to let people reject incoming addresses
23458 from their dirserver.
23459 - "tor --list-fingerprint" will list your identity key fingerprint
23461 - Add "pass" target for RedirectExit, to make it easier to break
23462 out of a sequence of RedirectExit rules.
23463 - Clients now generate a TLS cert too, in preparation for having
23464 them act more like real nodes.
23465 - Ship src/win32/ in the tarball, so people can use it to build.
23466 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
23468 - New "router-status" line in directory, to better bind each verified
23469 nickname to its identity key.
23470 - Deprecate unofficial config option abbreviations, and abbreviations
23471 not on the command line.
23472 - Add a pure-C tor-resolve implementation.
23473 - Use getrlimit and friends to ensure we can reach MaxConn (currently
23474 1024) file descriptors.
23476 o Code security improvements, inspired by Ilja:
23477 - Replace sprintf with snprintf. (I think they were all safe, but
23479 - Replace strcpy/strncpy with strlcpy in more places.
23480 - Avoid strcat; use snprintf or strlcat instead.
23481 - snprintf wrapper with consistent (though not C99) overflow behavior.
23484 Changes in version 0.0.9pre4 - 2004-10-17
23485 o Bugfixes on 0.0.9pre3:
23486 - If the server doesn't specify an exit policy, use the real default
23487 exit policy, not reject *:*.
23488 - Ignore fascistfirewall when uploading/downloading hidden service
23489 descriptors, since we go through Tor for those; and when using
23490 an HttpProxy, since we assume it can reach them all.
23491 - When looking for an authoritative dirserver, use only the ones
23492 configured at boot. Don't bother looking in the directory.
23493 - The rest of the fix for get_default_conf_file() on older win32.
23494 - Make 'Routerfile' config option obsolete.
23497 - New 'MyFamily nick1,...' config option for a server to
23498 specify other servers that shouldn't be used in the same circuit
23499 with it. Only believed if nick1 also specifies us.
23500 - New 'NodeFamily nick1,nick2,...' config option for a client to
23501 specify nodes that it doesn't want to use in the same circuit.
23502 - New 'Redirectexit pattern address:port' config option for a
23503 server to redirect exit connections, e.g. to a local squid.
23506 Changes in version 0.0.9pre3 - 2004-10-13
23507 o Bugfixes on 0.0.8.1:
23508 - Better torrc example lines for dirbindaddress and orbindaddress.
23509 - Improved bounds checking on parsed ints (e.g. config options and
23510 the ones we find in directories.)
23511 - Better handling of size_t vs int, so we're more robust on 64
23513 - Fix the rest of the bug where a newly started OR would appear
23514 as unverified even after we've added his fingerprint and hupped
23516 - Fix a bug from 0.0.7: when read() failed on a stream, we would
23517 close it without sending back an end. So 'connection refused'
23518 would simply be ignored and the user would get no response.
23520 o Bugfixes on 0.0.9pre2:
23521 - Serving the cached-on-disk directory to people is bad. We now
23522 provide no directory until we've fetched a fresh one.
23523 - Workaround for bug on windows where cached-directories get crlf
23525 - Make get_default_conf_file() work on older windows too.
23526 - If we write a *:* exit policy line in the descriptor, don't write
23527 any more exit policy lines.
23530 - Use only 0.0.9pre1 and later servers for resolve cells.
23531 - Make the dirservers file obsolete.
23532 - Include a dir-signing-key token in directories to tell the
23533 parsing entity which key is being used to sign.
23534 - Remove the built-in bulky default dirservers string.
23535 - New config option "Dirserver %s:%d [fingerprint]", which can be
23536 repeated as many times as needed. If no dirservers specified,
23537 default to moria1,moria2,tor26.
23538 - Make moria2 advertise a dirport of 80, so people behind firewalls
23539 will be able to get a directory.
23540 - Http proxy support
23541 - Dirservers translate requests for http://%s:%d/x to /x
23542 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
23543 be routed through this host.
23544 - Clients ask for /tor/x rather than /x for new enough dirservers.
23545 This way we can one day coexist peacefully with apache.
23546 - Clients specify a "Host: %s%d" http header, to be compatible
23547 with more proxies, and so running squid on an exit node can work.
23550 Changes in version 0.0.8.1 - 2004-10-13
23552 - Fix a seg fault that can be triggered remotely for Tor
23553 clients/servers with an open dirport.
23554 - Fix a rare assert trigger, where routerinfos for entries in
23555 our cpath would expire while we're building the path.
23556 - Fix a bug in OutboundBindAddress so it (hopefully) works.
23557 - Fix a rare seg fault for people running hidden services on
23558 intermittent connections.
23559 - Fix a bug in parsing opt keywords with objects.
23560 - Fix a stale pointer assert bug when a stream detaches and
23562 - Fix a string format vulnerability (probably not exploitable)
23563 in reporting stats locally.
23564 - Fix an assert trigger: sometimes launching circuits can fail
23565 immediately, e.g. because too many circuits have failed recently.
23566 - Fix a compile warning on 64 bit platforms.
23569 Changes in version 0.0.9pre2 - 2004-10-03
23571 - Make fetching a cached directory work for 64-bit platforms too.
23572 - Make zlib.h a required header, not an optional header.
23575 Changes in version 0.0.9pre1 - 2004-10-01
23577 - Stop using separate defaults for no-config-file and
23578 empty-config-file. Now you have to explicitly turn off SocksPort,
23579 if you don't want it open.
23580 - Fix a bug in OutboundBindAddress so it (hopefully) works.
23581 - Improve man page to mention more of the 0.0.8 features.
23582 - Fix a rare seg fault for people running hidden services on
23583 intermittent connections.
23584 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
23586 - Fix more dns related bugs: send back resolve_failed and end cells
23587 more reliably when the resolve fails, rather than closing the
23588 circuit and then trying to send the cell. Also attach dummy resolve
23589 connections to a circuit *before* calling dns_resolve(), to fix
23590 a bug where cached answers would never be sent in RESOLVED cells.
23591 - When we run out of disk space, or other log writing error, don't
23592 crash. Just stop logging to that log and continue.
23593 - We were starting to daemonize before we opened our logs, so if
23594 there were any problems opening logs, we would complain to stderr,
23595 which wouldn't work, and then mysteriously exit.
23596 - Fix a rare bug where sometimes a verified OR would connect to us
23597 before he'd uploaded his descriptor, which would cause us to
23598 assign conn->nickname as though he's unverified. Now we look through
23599 the fingerprint list to see if he's there.
23600 - Fix a rare assert trigger, where routerinfos for entries in
23601 our cpath would expire while we're building the path.
23604 - Clients can ask dirservers for /dir.z to get a compressed version
23605 of the directory. Only works for servers running 0.0.9, of course.
23606 - Make clients cache directories and use them to seed their router
23607 lists at startup. This means clients have a datadir again.
23608 - Configuration infrastructure support for warning on obsolete
23610 - Respond to content-encoding headers by trying to uncompress as
23612 - Reply with a deflated directory when a client asks for "dir.z".
23613 We could use allow-encodings instead, but allow-encodings isn't
23614 specified in HTTP 1.0.
23615 - Raise the max dns workers from 50 to 100.
23616 - Discourage people from setting their dirfetchpostperiod more often
23617 than once per minute.
23618 - Protect dirservers from overzealous descriptor uploading -- wait
23619 10 seconds after directory gets dirty, before regenerating.
23622 Changes in version 0.0.8 - 2004-08-25
23623 o Port it to SunOS 5.9 / Athena
23626 Changes in version 0.0.8rc2 - 2004-08-20
23627 o Make it compile on cygwin again.
23628 o When picking unverified routers, skip those with low uptime and/or
23629 low bandwidth, depending on what properties you care about.
23632 Changes in version 0.0.8rc1 - 2004-08-18
23633 o Changes from 0.0.7.3:
23635 - Fix assert triggers: if the other side returns an address 0.0.0.0,
23636 don't put it into the client dns cache.
23637 - If a begin failed due to exit policy, but we believe the IP address
23638 should have been allowed, switch that router to exitpolicy reject *:*
23639 until we get our next directory.
23641 - Clients choose nodes proportional to advertised bandwidth.
23642 - Avoid using nodes with low uptime as introduction points.
23643 - Handle servers with dynamic IP addresses: don't replace
23644 options->Address with the resolved one at startup, and
23645 detect our address right before we make a routerinfo each time.
23646 - 'FascistFirewall' option to pick dirservers and ORs on specific
23647 ports; plus 'FirewallPorts' config option to tell FascistFirewall
23648 which ports are open. (Defaults to 80,443)
23649 - Be more aggressive about trying to make circuits when the network
23650 has changed (e.g. when you unsuspend your laptop).
23651 - Check for time skew on http headers; report date in response to
23653 - If the entrynode config line has only one node, don't pick it as
23655 - Add strict{entry|exit}nodes config options. If set to 1, then
23656 we refuse to build circuits that don't include the specified entry
23658 - OutboundBindAddress config option, to bind to a specific
23659 IP address for outgoing connect()s.
23660 - End truncated log entries (e.g. directories) with "[truncated]".
23662 o Patches to 0.0.8preX:
23664 - Patches to compile and run on win32 again (maybe)?
23665 - Fix crash when looking for ~/.torrc with no $HOME set.
23666 - Fix a race bug in the unit tests.
23667 - Handle verified/unverified name collisions better when new
23668 routerinfo's arrive in a directory.
23669 - Sometimes routers were getting entered into the stats before
23670 we'd assigned their identity_digest. Oops.
23671 - Only pick and establish intro points after we've gotten a
23674 - AllowUnverifiedNodes config option to let circuits choose no-name
23675 routers in entry,middle,exit,introduction,rendezvous positions.
23676 Allow middle and rendezvous positions by default.
23677 - Add a man page for tor-resolve.
23680 Changes in version 0.0.7.3 - 2004-08-12
23681 o Stop dnsworkers from triggering an assert failure when you
23682 ask them to resolve the host "".
23685 Changes in version 0.0.8pre3 - 2004-08-09
23686 o Changes from 0.0.7.2:
23687 - Allow multiple ORs with same nickname in routerlist -- now when
23688 people give us one identity key for a nickname, then later
23689 another, we don't constantly complain until the first expires.
23690 - Remember used bandwidth (both in and out), and publish 15-minute
23691 snapshots for the past day into our descriptor.
23692 - You can now fetch $DIRURL/running-routers to get just the
23693 running-routers line, not the whole descriptor list. (But
23694 clients don't use this yet.)
23695 - When people mistakenly use Tor as an http proxy, point them
23696 at the tor-doc.html rather than the INSTALL.
23697 - Remove our mostly unused -- and broken -- hex_encode()
23698 function. Use base16_encode() instead. (Thanks to Timo Lindfors
23699 for pointing out this bug.)
23700 - Rotate onion keys every 12 hours, not every 2 hours, so we have
23701 fewer problems with people using the wrong key.
23702 - Change the default exit policy to reject the default edonkey,
23703 kazaa, gnutella ports.
23704 - Add replace_file() to util.[ch] to handle win32's rename().
23706 o Changes from 0.0.8preX:
23707 - Fix two bugs in saving onion keys to disk when rotating, so
23708 hopefully we'll get fewer people using old onion keys.
23709 - Fix an assert error that was making SocksPolicy not work.
23710 - Be willing to expire routers that have an open dirport -- it's
23711 just the authoritative dirservers we want to not forget.
23712 - Reject tor-resolve requests for .onion addresses early, so we
23713 don't build a whole rendezvous circuit and then fail.
23714 - When you're warning a server that he's unverified, don't cry
23715 wolf unpredictably.
23716 - Fix a race condition: don't try to extend onto a connection
23717 that's still handshaking.
23718 - For servers in clique mode, require the conn to be open before
23719 you'll choose it for your path.
23720 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
23721 end relay cell, etc.
23722 - Measure bandwidth capacity over the last 24 hours, not just 12
23723 - Bugfix: authoritative dirservers were making and signing a new
23724 directory for each client, rather than reusing the cached one.
23727 Changes in version 0.0.8pre2 - 2004-08-04
23728 o Changes from 0.0.7.2:
23730 - Check directory signature _before_ you decide whether you're
23731 you're running an obsolete version and should exit.
23732 - Check directory signature _before_ you parse the running-routers
23733 list to decide who's running or verified.
23734 - Bugfixes and features:
23735 - Check return value of fclose while writing to disk, so we don't
23736 end up with broken files when servers run out of disk space.
23737 - Log a warning if the user uses an unsafe socks variant, so people
23738 are more likely to learn about privoxy or socat.
23739 - Dirservers now include RFC1123-style dates in the HTTP headers,
23740 which one day we will use to better detect clock skew.
23742 o Changes from 0.0.8pre1:
23743 - Make it compile without warnings again on win32.
23744 - Log a warning if you're running an unverified server, to let you
23745 know you might want to get it verified.
23746 - Only pick a default nickname if you plan to be a server.
23749 Changes in version 0.0.8pre1 - 2004-07-23
23751 - Made our unit tests compile again on OpenBSD 3.5, and tor
23752 itself compile again on OpenBSD on a sparc64.
23753 - We were neglecting milliseconds when logging on win32, so
23754 everything appeared to happen at the beginning of each second.
23756 o Protocol changes:
23757 - 'Extend' relay cell payloads now include the digest of the
23758 intended next hop's identity key. Now we can verify that we're
23759 extending to the right router, and also extend to routers we
23760 hadn't heard of before.
23763 - Tor nodes can now act as relays (with an advertised ORPort)
23764 without being manually verified by the dirserver operators.
23765 - Uploaded descriptors of unverified routers are now accepted
23766 by the dirservers, and included in the directory.
23767 - Verified routers are listed by nickname in the running-routers
23768 list; unverified routers are listed as "$<fingerprint>".
23769 - We now use hash-of-identity-key in most places rather than
23770 nickname or addr:port, for improved security/flexibility.
23771 - To avoid Sybil attacks, paths still use only verified servers.
23772 But now we have a chance to play around with hybrid approaches.
23773 - Nodes track bandwidth usage to estimate capacity (not used yet).
23774 - ClientOnly option for nodes that never want to become servers.
23775 - Directory caching.
23776 - "AuthoritativeDir 1" option for the official dirservers.
23777 - Now other nodes (clients and servers) will cache the latest
23778 directory they've pulled down.
23779 - They can enable their DirPort to serve it to others.
23780 - Clients will pull down a directory from any node with an open
23781 DirPort, and check the signature/timestamp correctly.
23782 - Authoritative dirservers now fetch directories from other
23783 authdirservers, to stay better synced.
23784 - Running-routers list tells who's down also, along with noting
23785 if they're verified (listed by nickname) or unverified (listed
23787 - Allow dirservers to serve running-router list separately.
23788 This isn't used yet.
23789 - ORs connect-on-demand to other ORs
23790 - If you get an extend cell to an OR you're not connected to,
23791 connect, handshake, and forward the create cell.
23792 - The authoritative dirservers stay connected to everybody,
23793 and everybody stays connected to 0.0.7 servers, but otherwise
23794 clients/servers expire unused connections after 5 minutes.
23795 - When servers get a sigint, they delay 30 seconds (refusing new
23796 connections) then exit. A second sigint causes immediate exit.
23797 - File and name management:
23798 - Look for .torrc if no CONFDIR "torrc" is found.
23799 - If no datadir is defined, then choose, make, and secure ~/.tor
23801 - If torrc not found, exitpolicy reject *:*.
23802 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
23803 - If no nickname is defined, derive default from hostname.
23804 - Rename secret key files, e.g. identity.key -> secret_id_key,
23805 to discourage people from mailing their identity key to tor-ops.
23806 - Refuse to build a circuit before the directory has arrived --
23807 it won't work anyway, since you won't know the right onion keys
23809 - Try other dirservers immediately if the one you try is down. This
23810 should tolerate down dirservers better now.
23811 - Parse tor version numbers so we can do an is-newer-than check
23812 rather than an is-in-the-list check.
23813 - New socks command 'resolve', to let us shim gethostbyname()
23815 - A 'tor_resolve' script to access the socks resolve functionality.
23816 - A new socks-extensions.txt doc file to describe our
23817 interpretation and extensions to the socks protocols.
23818 - Add a ContactInfo option, which gets published in descriptor.
23819 - Publish OR uptime in descriptor (and thus in directory) too.
23820 - Write tor version at the top of each log file
23821 - New docs in the tarball:
23823 - Document that you should proxy your SSL traffic too.
23826 Changes in version 0.0.7.2 - 2004-07-07
23827 o A better fix for the 0.0.0.0 problem, that will hopefully
23828 eliminate the remaining related assertion failures.
23831 Changes in version 0.0.7.1 - 2004-07-04
23832 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
23833 since internally we use 0.0.0.0 to signify "not yet resolved".
23836 Changes in version 0.0.7 - 2004-06-07
23837 o Updated the man page to reflect the new features.
23840 Changes in version 0.0.7rc2 - 2004-06-06
23841 o Changes from 0.0.7rc1:
23842 - Make it build on Win32 again.
23843 o Changes from 0.0.6.2:
23844 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
23848 Changes in version 0.0.7rc1 - 2004-06-02
23850 - On sighup, we were adding another log without removing the first
23851 one. So log messages would get duplicated n times for n sighups.
23852 - Several cases of using a connection after we'd freed it. The
23853 problem was that connections that are pending resolve are in both
23854 the pending_resolve tree, and also the circuit's resolving_streams
23855 list. When you want to remove one, you must remove it from both.
23856 - Fix a double-mark-for-close where an end cell arrived for a
23857 resolving stream, and then the resolve failed.
23858 - Check directory signatures based on name of signer, not on whom
23859 we got the directory from. This will let us cache directories more
23862 - Crank up some of our constants to handle more users.
23865 Changes in version 0.0.7pre1 - 2004-06-02
23866 o Fixes for crashes and other obnoxious bugs:
23867 - Fix an epipe bug: sometimes when directory connections failed
23868 to connect, we would give them a chance to flush before closing
23870 - When we detached from a circuit because of resolvefailed, we
23871 would immediately try the same circuit twice more, and then
23872 give up on the resolve thinking we'd tried three different
23874 - Limit the number of intro circuits we'll attempt to build for a
23875 hidden service per 15-minute period.
23876 - Check recommended-software string *early*, before actually parsing
23877 the directory. Thus we can detect an obsolete version and exit,
23878 even if the new directory format doesn't parse.
23879 o Fixes for security bugs:
23880 - Remember which nodes are dirservers when you startup, and if a
23881 random OR enables his dirport, don't automatically assume he's
23882 a trusted dirserver.
23884 - Directory connections were asking the wrong poll socket to
23885 start writing, and not asking themselves to start writing.
23886 - When we detached from a circuit because we sent a begin but
23887 didn't get a connected, we would use it again the first time;
23888 but after that we would correctly switch to a different one.
23889 - Stop warning when the first onion decrypt attempt fails; they
23890 will sometimes legitimately fail now that we rotate keys.
23891 - Override unaligned-access-ok check when $host_cpu is ia64 or
23892 arm. Apparently they allow it but the kernel whines.
23893 - Dirservers try to reconnect periodically too, in case connections
23895 - Fix some memory leaks in directory servers.
23896 - Allow backslash in Win32 filenames.
23897 - Made Tor build complain-free on FreeBSD, hopefully without
23898 breaking other BSD builds. We'll see.
23900 - Doxygen markup on all functions and global variables.
23901 - Make directory functions update routerlist, not replace it. So
23902 now directory disagreements are not so critical a problem.
23903 - Remove the upper limit on number of descriptors in a dirserver's
23904 directory (not that we were anywhere close).
23905 - Allow multiple logfiles at different severity ranges.
23906 - Allow *BindAddress to specify ":port" rather than setting *Port
23907 separately. Allow multiple instances of each BindAddress config
23908 option, so you can bind to multiple interfaces if you want.
23909 - Allow multiple exit policy lines, which are processed in order.
23910 Now we don't need that huge line with all the commas in it.
23911 - Enable accept/reject policies on SOCKS connections, so you can bind
23912 to 0.0.0.0 but still control who can use your OP.
23915 Changes in version 0.0.6.2 - 2004-05-16
23916 o Our integrity-checking digest was checking only the most recent cell,
23917 not the previous cells like we'd thought.
23918 Thanks to Stefan Mark for finding the flaw!
23921 Changes in version 0.0.6.1 - 2004-05-06
23922 o Fix two bugs in our AES counter-mode implementation (this affected
23923 onion-level stream encryption, but not TLS-level). It turns
23924 out we were doing something much more akin to a 16-character
23925 polyalphabetic cipher. Oops.
23926 Thanks to Stefan Mark for finding the flaw!
23927 o Retire moria3 as a directory server, and add tor26 as a directory
23931 Changes in version 0.0.6 - 2004-05-02
23932 [version bump only]
23935 Changes in version 0.0.6rc4 - 2004-05-01
23936 o Update the built-in dirservers list to use the new directory format
23937 o Fix a rare seg fault: if a node offering a hidden service attempts
23938 to build a circuit to Alice's rendezvous point and fails before it
23939 reaches the last hop, it retries with a different circuit, but
23941 o Handle windows socket errors correctly.
23944 Changes in version 0.0.6rc3 - 2004-04-28
23945 o Don't expire non-general excess circuits (if we had enough
23946 circuits open, we were expiring rendezvous circuits -- even
23947 when they had a stream attached. oops.)
23948 o Fetch randomness from /dev/urandom better (not via fopen/fread)
23949 o Better debugging for tls errors
23950 o Some versions of openssl have an SSL_pending function that erroneously
23951 returns bytes when there is a non-application record pending.
23952 o Set Content-Type on the directory and hidserv descriptor.
23953 o Remove IVs from cipher code, since AES-ctr has none.
23954 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
23955 o We were using an array of length zero in a few places.
23956 o win32's gethostbyname can't resolve an IP to an IP.
23957 o win32's close can't close a socket.
23960 Changes in version 0.0.6rc2 - 2004-04-26
23961 o Fix a bug where we were closing tls connections intermittently.
23962 It turns out openssl keeps its errors around -- so if an error
23963 happens, and you don't ask about it, and then another openssl
23964 operation happens and succeeds, and you ask if there was an error,
23965 it tells you about the first error. Fun fun.
23966 o Fix a bug that's been lurking since 27 may 03 (!)
23967 When passing back a destroy cell, we would use the wrong circ id.
23968 'Mostly harmless', but still worth fixing.
23969 o Since we don't support truncateds much, don't bother sending them;
23970 just close the circ.
23971 o check for <machine/limits.h> so we build on NetBSD again (I hope).
23972 o don't crash if a conn that sent a begin has suddenly lost its circuit
23973 (this was quite rare).
23976 Changes in version 0.0.6rc1 - 2004-04-25
23977 o We now rotate link (tls context) keys and onion keys.
23978 o CREATE cells now include oaep padding, so you can tell
23979 if you decrypted them correctly.
23980 o Add bandwidthburst to server descriptor.
23981 o Directories now say which dirserver signed them.
23982 o Use a tor_assert macro that logs failed assertions too.
23985 Changes in version 0.0.6pre5 - 2004-04-18
23986 o changes from 0.0.6pre4:
23987 - make tor build on broken freebsd 5.2 installs
23988 - fix a failed assert when you try an intro point, get a nack, and try
23989 a second one and it works.
23990 - when alice uses a port that the hidden service doesn't accept,
23991 it now sends back an end cell (denied by exit policy). otherwise
23992 alice would just have to wait to time out.
23993 - fix another rare bug: when we had tried all the intro
23994 points for a hidden service, we fetched the descriptor
23995 again, but we left our introcirc thinking it had already
23996 sent an intro, so it kept waiting for a response...
23997 - bugfix: when you sleep your hidden-service laptop, as soon
23998 as it wakes up it tries to upload a service descriptor, but
23999 socketpair fails for some reason (localhost not up yet?).
24000 now we simply give up on that upload, and we'll try again later.
24001 i'd still like to find the bug though.
24002 - if an intro circ waiting for an ack dies before getting one, then
24004 - we were reusing stale service descriptors and refetching usable
24008 Changes in version 0.0.6pre4 - 2004-04-14
24009 o changes from 0.0.6pre3:
24010 - when bob fails to connect to the rendezvous point, and his
24011 circ didn't fail because of the rendezvous point itself, then
24012 he retries a couple of times
24013 - we expire introduction and rendezvous circs more thoroughly
24014 (sometimes they were hanging around forever)
24015 - we expire unattached rendezvous streams that have been around
24016 too long (they were sticking around forever).
24017 - fix a measly fencepost error that was crashing everybody with
24021 Changes in version 0.0.6pre3 - 2004-04-14
24022 o changes from 0.0.6pre2:
24023 - make hup work again
24024 - fix some memory leaks for dirservers
24025 - allow more skew in rendezvous descriptor timestamps, to help
24026 handle people like blanu who don't know what time it is
24027 - normal circs are 3 hops, but some rend/intro circs are 4, if
24028 the initiator doesn't get to choose the last hop
24029 - send acks for introductions, so alice can know whether to try
24031 - bob publishes intro points more correctly
24032 o changes from 0.0.5:
24033 - fix an assert trigger that's been plaguing us since the days
24034 of 0.0.2prexx (thanks weasel!)
24035 - retry stream correctly when we fail to connect because of
24036 exit-policy-reject (should try another) or can't-resolve-address
24037 (also should try another, because dns on random internet servers
24039 - when we hup a dirserver and we've *removed* a server from the
24040 approved-routers list, now we remove that server from the
24041 in-memory directories too
24044 Changes in version 0.0.6pre2 - 2004-04-08
24045 o We fixed our base32 implementation. Now it works on all architectures.
24048 Changes in version 0.0.6pre1 - 2004-04-08
24050 - Hidden services and rendezvous points are implemented. Go to
24051 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
24052 hidden services. (This only works via a socks4a proxy such as
24053 Privoxy, and currently it's quite slow.)
24056 Changes in version 0.0.5 - 2004-03-30
24057 [version bump only]
24060 Changes in version 0.0.5rc3 - 2004-03-29
24061 o Install torrc as torrc.sample -- we no longer clobber your
24063 o Re-enable recommendedversion checking (we broke it in rc2, oops)
24064 o Add in a 'notice' log level for things the operator should hear
24065 but that aren't warnings
24068 Changes in version 0.0.5rc2 - 2004-03-29
24069 o Hold socks connection open until reply is flushed (if possible)
24070 o Make exit nodes resolve IPs to IPs immediately, rather than asking
24071 the dns farm to do it.
24072 o Fix c99 aliasing warnings in rephist.c
24073 o Don't include server descriptors that are older than 24 hours in the
24075 o Give socks 'reject' replies their whole 15s to attempt to flush,
24076 rather than seeing the 60s timeout and assuming the flush had failed.
24077 o Clean automake droppings from the cvs repository
24080 Changes in version 0.0.5rc1 - 2004-03-28
24081 o Fix mangled-state bug in directory fetching (was causing sigpipes).
24082 o Only build circuits after we've fetched the directory: clients were
24083 using only the directory servers before they'd fetched a directory.
24084 This also means longer startup time; so it goes.
24085 o Fix an assert trigger where an OP would fail to handshake, and we'd
24086 expect it to have a nickname.
24087 o Work around a tsocks bug: do a socks reject when AP connection dies
24088 early, else tsocks goes into an infinite loop.
24091 Changes in version 0.0.4 - 2004-03-26
24092 o When connecting to a dirserver or OR and the network is down,
24096 Changes in version 0.0.3 - 2004-03-26
24097 o Warn and fail if server chose a nickname with illegal characters
24098 o Port to Solaris and Sparc:
24099 - include missing header fcntl.h
24100 - have autoconf find -lsocket -lnsl automatically
24101 - deal with hardware word alignment
24102 - make uname() work (solaris has a different return convention)
24103 - switch from using signal() to sigaction()
24104 o Preliminary work on reputation system:
24105 - Keep statistics on success/fail of connect attempts; they're published
24106 by kill -USR1 currently.
24107 - Add a RunTesting option to try to learn link state by creating test
24108 circuits, even when SocksPort is off.
24109 - Remove unused open circuits when there are too many.
24112 Changes in version 0.0.2 - 2004-03-19
24113 - Include strlcpy and strlcat for safer string ops
24114 - define INADDR_NONE so we compile (but still not run) on solaris
24117 Changes in version 0.0.2pre27 - 2004-03-14
24119 - Allow internal tor networks (we were rejecting internal IPs,
24120 now we allow them if they're set explicitly).
24121 - And fix a few endian issues.
24124 Changes in version 0.0.2pre26 - 2004-03-14
24126 - If a stream times out after 15s without a connected cell, don't
24127 try that circuit again: try a new one.
24128 - Retry streams at most 4 times. Then give up.
24129 - When a dirserver gets a descriptor from an unknown router, it
24130 logs its fingerprint (so the dirserver operator can choose to
24131 accept it even without mail from the server operator).
24132 - Inform unapproved servers when we reject their descriptors.
24133 - Make tor build on Windows again. It works as a client, who knows
24135 - Clearer instructions in the torrc for how to set up a server.
24136 - Be more efficient about reading fd's when our global token bucket
24137 (used for rate limiting) becomes empty.
24139 - Stop asserting that computers always go forward in time. It's
24141 - When we sent a cell (e.g. destroy) and then marked an OR connection
24142 expired, we might close it before finishing a flush if the other
24143 side isn't reading right then.
24144 - Don't allow dirservers to start if they haven't defined
24145 RecommendedVersions
24146 - We were caching transient dns failures. Oops.
24147 - Prevent servers from publishing an internal IP as their address.
24148 - Address a strcat vulnerability in circuit.c
24151 Changes in version 0.0.2pre25 - 2004-03-04
24153 - Put the OR's IP in its router descriptor, not its fqdn. That way
24154 we'll stop being stalled by gethostbyname for nodes with flaky dns,
24157 - If the user typed in an address that didn't resolve, the server
24161 Changes in version 0.0.2pre24 - 2004-03-03
24163 - Fix an assertion failure in dns.c, where we were trying to dequeue
24164 a pending dns resolve even if it wasn't pending
24165 - Fix a spurious socks5 warning about still trying to write after the
24166 connection is finished.
24167 - Hold certain marked_for_close connections open until they're finished
24168 flushing, rather than losing bytes by closing them too early.
24169 - Correctly report the reason for ending a stream
24170 - Remove some duplicate calls to connection_mark_for_close
24171 - Put switch_id and start_daemon earlier in the boot sequence, so it
24172 will actually try to chdir() to options.DataDirectory
24173 - Make 'make test' exit(1) if a test fails; fix some unit tests
24174 - Make tor fail when you use a config option it doesn't know about,
24175 rather than warn and continue.
24176 - Make --version work
24177 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
24180 Changes in version 0.0.2pre23 - 2004-02-29
24182 - Print a statement when the first circ is finished, so the user
24183 knows it's working.
24184 - If a relay cell is unrecognized at the end of the circuit,
24185 send back a destroy. (So attacks to mutate cells are more
24187 - New config option 'excludenodes' to avoid certain nodes for circuits.
24188 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
24189 so you can collect coredumps there.
24191 - Fix a bug in tls flushing where sometimes data got wedged and
24192 didn't flush until more data got sent. Hopefully this bug was
24193 a big factor in the random delays we were seeing.
24194 - Make 'connected' cells include the resolved IP, so the client
24195 dns cache actually gets populated.
24196 - Disallow changing from ORPort=0 to ORPort>0 on hup.
24197 - When we time-out on a stream and detach from the circuit, send an
24198 end cell down it first.
24199 - Only warn about an unknown router (in exitnodes, entrynodes,
24200 excludenodes) after we've fetched a directory.
24203 Changes in version 0.0.2pre22 - 2004-02-26
24205 - Servers publish less revealing uname information in descriptors.
24206 - More memory tracking and assertions, to crash more usefully when
24208 - If the default torrc isn't there, just use some default defaults.
24209 Plus provide an internal dirservers file if they don't have one.
24210 - When the user tries to use Tor as an http proxy, give them an http
24211 501 failure explaining that we're a socks proxy.
24212 - Dump a new router.desc on hup, to help confused people who change
24213 their exit policies and then wonder why router.desc doesn't reflect
24215 - Clean up the generic tor.sh init script that we ship with.
24217 - If the exit stream is pending on the resolve, and a destroy arrives,
24218 then the stream wasn't getting removed from the pending list. I
24219 think this was the one causing recent server crashes.
24220 - Use a more robust poll on OSX 10.3, since their poll is flaky.
24221 - When it couldn't resolve any dirservers, it was useless from then on.
24222 Now it reloads the RouterFile (or default dirservers) if it has no
24224 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
24225 many users don't even *have* a /usr/local/sbin/.
24228 Changes in version 0.0.2pre21 - 2004-02-18
24230 - There's a ChangeLog file that actually reflects the changelog.
24231 - There's a 'torify' wrapper script, with an accompanying
24232 tor-tsocks.conf, that simplifies the process of using tsocks for
24233 tor. It even has a man page.
24234 - The tor binary gets installed to sbin rather than bin now.
24235 - Retry streams where the connected cell hasn't arrived in 15 seconds
24236 - Clean up exit policy handling -- get the default out of the torrc,
24237 so we can update it without forcing each server operator to fix
24239 - Allow imaps and pop3s in default exit policy
24241 - Prevent picking middleman nodes as the last node in the circuit
24244 Changes in version 0.0.2pre20 - 2004-01-30
24246 - We now have a deb package, and it's in debian unstable. Go to
24247 it, apt-getters. :)
24248 - I've split the TotalBandwidth option into BandwidthRate (how many
24249 bytes per second you want to allow, long-term) and
24250 BandwidthBurst (how many bytes you will allow at once before the cap
24251 kicks in). This better token bucket approach lets you, say, set
24252 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
24253 performance while not exceeding your monthly bandwidth quota.
24254 - Push out a tls record's worth of data once you've got it, rather
24255 than waiting until you've read everything waiting to be read. This
24256 may improve performance by pipelining better. We'll see.
24257 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
24258 from failed circuits (if they haven't been connected yet) and attach
24260 - Expire old streams that haven't managed to connect. Some day we'll
24261 have them reattach to new circuits instead.
24264 - Fix several memory leaks that were causing servers to become bloated
24266 - Fix a few very rare assert triggers. A few more remain.
24267 - Setuid to User _before_ complaining about running as root.
24270 Changes in version 0.0.2pre19 - 2004-01-07
24272 - Fix deadlock condition in dns farm. We were telling a child to die by
24273 closing the parent's file descriptor to him. But newer children were
24274 inheriting the open file descriptor from the parent, and since they
24275 weren't closing it, the socket never closed, so the child never read
24276 eof, so he never knew to exit. Similarly, dns workers were holding
24277 open other sockets, leading to all sorts of chaos.
24278 - New cleaner daemon() code for forking and backgrounding.
24279 - If you log to a file, it now prints an entry at the top of the
24280 logfile so you know it's working.
24281 - The onionskin challenge length was 30 bytes longer than necessary.
24282 - Started to patch up the spec so it's not quite so out of date.
24285 Changes in version 0.0.2pre18 - 2004-01-02
24287 - Fix endian issues with the 'integrity' field in the relay header.
24288 - Fix a potential bug where connections in state
24289 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
24292 Changes in version 0.0.2pre17 - 2003-12-30
24294 - Made --debuglogfile (or any second log file, actually) work.
24295 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
24296 adversary could force us into an infinite loop.
24299 - Each onionskin handshake now includes a hash of the computed key,
24300 to prove the server's identity and help perfect forward secrecy.
24301 - Changed cell size from 256 to 512 bytes (working toward compatibility
24303 - Changed cell length to 2 bytes, and moved it to the relay header.
24304 - Implemented end-to-end integrity checking for the payloads of
24306 - Separated streamid from 'recognized' (otherwise circuits will get
24307 messed up when we try to have streams exit from the middle). We
24308 use the integrity-checking to confirm that a cell is addressed to
24310 - Randomize the initial circid and streamid values, so an adversary who
24311 breaks into a node can't learn how many circuits or streams have
24315 Changes in version 0.0.2pre16 - 2003-12-14
24317 - Fixed a bug that made HUP trigger an assert
24318 - Fixed a bug where a circuit that immediately failed wasn't being
24319 counted as a failed circuit in counting retries.
24322 - Now we close the circuit when we get a truncated cell: otherwise we're
24323 open to an anonymity attack where a bad node in the path truncates
24324 the circuit and then we open streams at him.
24325 - Add port ranges to exit policies
24326 - Add a conservative default exit policy
24327 - Warn if you're running tor as root
24328 - on HUP, retry OR connections and close/rebind listeners
24329 - options.EntryNodes: try these nodes first when picking the first node
24330 - options.ExitNodes: if your best choices happen to include any of
24331 your preferred exit nodes, you choose among just those preferred
24333 - options.ExcludedNodes: nodes that are never picked in path building
24336 Changes in version 0.0.2pre15 - 2003-12-03
24337 o Robustness and bugfixes:
24338 - Sometimes clients would cache incorrect DNS resolves, which would
24339 really screw things up.
24340 - An OP that goes offline would slowly leak all its sockets and stop
24342 - A wide variety of bugfixes in exit node selection, exit policy
24343 handling, and processing pending streams when a new circuit is
24345 - Pick nodes for a path only from those the directory says are up
24346 - Choose randomly from all running dirservers, not always the first one
24347 - Increase allowed http header size for directory fetch.
24348 - Stop writing to stderr (if we're daemonized it will be closed).
24349 - Enable -g always, so cores will be more useful to me.
24350 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
24353 - Wrote a man page. It lists commonly used options.
24356 - Change default loglevel to warn.
24357 - Make PidFile default to null rather than littering in your CWD.
24358 - OnionRouter config option is now obsolete. Instead it just checks
24360 - Moved to a single unified torrc file for both clients and servers.
24363 Changes in version 0.0.2pre14 - 2003-11-29
24364 o Robustness and bugfixes:
24365 - Force the admin to make the DataDirectory himself
24366 - to get ownership/permissions right
24367 - so clients no longer make a DataDirectory and then never use it
24368 - fix bug where a client who was offline for 45 minutes would never
24369 pull down a directory again
24370 - fix (or at least hide really well) the dns assert bug that was
24371 causing server crashes
24372 - warnings and improved robustness wrt clockskew for certs
24373 - use the native daemon(3) to daemonize, when available
24374 - exit if bind() fails
24375 - exit if neither socksport nor orport is defined
24376 - include our own tor_timegm (Win32 doesn't have its own)
24377 - bugfix for win32 with lots of connections
24378 - fix minor bias in PRNG
24379 - make dirserver more robust to corrupt cached directory
24382 - Wrote the design document (woo)
24384 o Circuit building and exit policies:
24385 - Circuits no longer try to use nodes that the directory has told them
24387 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
24388 bitcounts (18.0.0.0/8).
24389 - Make AP connections standby for a circuit if no suitable circuit
24390 exists, rather than failing
24391 - Circuits choose exit node based on addr/port, exit policies, and
24392 which AP connections are standing by
24393 - Bump min pathlen from 2 to 3
24394 - Relay end cells have a payload to describe why the stream ended.
24395 - If the stream failed because of exit policy, try again with a new
24397 - Clients have a dns cache to remember resolved addresses.
24398 - Notice more quickly when we have no working circuits
24401 - APPort is now called SocksPort
24402 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
24404 - RecommendedVersions is now a config variable rather than
24405 hardcoded (for dirservers)
24406 - Reloads config on HUP
24407 - Usage info on -h or --help
24408 - If you set User and Group config vars, it'll setu/gid to them.
24411 Changes in version 0.0.2pre13 - 2003-10-19
24412 o General stability:
24413 - SSL_write no longer fails when it returns WANTWRITE and the number
24414 of bytes in the buf has changed by the next SSL_write call.
24415 - Fix segfault fetching directory when network is down
24416 - Fix a variety of minor memory leaks
24417 - Dirservers reload the fingerprints file on HUP, so I don't have
24418 to take down the network when I approve a new router
24419 - Default server config file has explicit Address line to specify fqdn
24422 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
24423 - Make listener connections not ever alloc bufs
24425 o Autoconf improvements:
24426 - don't clobber an external CFLAGS in ./configure
24427 - Make install now works
24428 - create var/lib/tor on make install
24429 - autocreate a tor.sh initscript to help distribs
24430 - autocreate the torrc and sample-server-torrc with correct paths
24432 o Log files and Daemonizing now work:
24433 - If --DebugLogFile is specified, log to it at -l debug
24434 - If --LogFile is specified, use it instead of commandline
24435 - If --RunAsDaemon is set, tor forks and backgrounds on startup