1 Changes in version 0.3.0.11 - 2017-09-18
2 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
5 Most significantly, it includes a fix for TROVE-2017-008, a
6 security bug that affects hidden services running with the
7 SafeLogging option disabled. For more information, see
8 https://trac.torproject.org/projects/tor/ticket/23490
10 o Minor features (code style, backport from 0.3.1.7):
11 - Add "Falls through" comments to our codebase, in order to silence
12 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
13 Stieger. Closes ticket 22446.
16 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
19 o Minor bugfixes (compilation, backport from 0.3.1.7):
20 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
21 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
23 o Minor bugfixes (controller, backport from 0.3.1.7):
24 - Do not crash when receiving a HSPOST command with an empty body.
25 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
26 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
27 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
29 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
30 - When setting the maximum number of connections allowed by the OS,
31 always allow some extra file descriptors for other files. Fixes
32 bug 22797; bugfix on 0.2.0.10-alpha.
34 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
35 - Remove a forgotten debugging message when an introduction point
36 successfully establishes a hidden service prop224 circuit with
38 - Change three other log_warn() for an introduction point to
39 protocol warnings, because they can be failure from the network
40 and are not relevant to the operator. Fixes bug 23078; bugfix on
41 0.3.0.1-alpha and 0.3.0.2-alpha.
44 Changes in version 0.3.0.10 - 2017-08-02
45 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
46 from the current Tor alpha series. OpenBSD users and TPROXY users
47 should upgrade; others are probably okay sticking with 0.3.0.9.
49 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
50 - Tor's repository now includes a Travis Continuous Integration (CI)
51 configuration file (.travis.yml). This is meant to help new
52 developers and contributors who fork Tor to a Github repository be
53 better able to test their changes, and understand what we expect
54 to pass. To use this new build feature, you must fork Tor to your
55 Github account, then go into the "Integrations" menu in the
56 repository settings for your fork and enable Travis, then push
57 your changes. Closes ticket 22636.
59 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
60 - Fix a typo that had prevented TPROXY-based transparent proxying
61 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
62 Patch from "d4fq0fQAgoJ".
64 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
65 - Avoid an assertion failure bug affecting our implementation of
66 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
67 handling of "0xfoo" differs from what we had expected. Fixes bug
68 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
70 o Minor features (backport from 0.3.1.5-alpha):
71 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
74 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
75 - Roll over monthly accounting at the configured hour and minute,
76 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
77 Found by Andrey Karpov with PVS-Studio.
79 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
80 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
81 bugfix on 0.2.8.1-alpha.
82 - Fix warnings when building with libscrypt and openssl scrypt
83 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
84 - When building with certain versions of the mingw C header files,
85 avoid float-conversion warnings when calling the C functions
86 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
89 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
90 - Backport a fix for an "unused variable" warning that appeared
91 in some versions of mingw. Fixes bug 22838; bugfix on
94 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
95 - Avoid Coverity build warnings related to our BUG() macro. By
96 default, Coverity treats BUG() as the Linux kernel does: an
97 instant abort(). We need to override that so our BUG() macro
98 doesn't prevent Coverity from analyzing functions that use it.
99 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
101 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
102 - When rejecting a router descriptor for running an obsolete version
103 of Tor without ntor support, warn about the obsolete tor version,
104 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
106 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
107 - Avoid a sandbox failure when trying to re-bind to a socket and
108 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
110 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
111 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
112 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
115 Changes in version 0.3.0.9 - 2017-06-29
116 Tor 0.3.0.9 fixes a path selection bug that would allow a client
117 to use a guard that was in the same network family as a chosen exit
118 relay. This is a security regression; all clients running earlier
119 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
122 This release also backports several other bugfixes from the 0.3.1.x
125 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
126 - When choosing which guard to use for a circuit, avoid the exit's
127 family along with the exit itself. Previously, the new guard
128 selection logic avoided the exit, but did not consider its family.
129 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
130 006 and CVE-2017-0377.
132 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
133 - Don't block bootstrapping when a primary bridge is offline and we
134 can't get its descriptor. Fixes bug 22325; fixes one case of bug
135 21969; bugfix on 0.3.0.3-alpha.
137 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
138 - When starting with an old consensus, do not add new entry guards
139 unless the consensus is "reasonably live" (under 1 day old). Fixes
140 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
142 o Minor features (geoip):
143 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
146 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
147 - Reject version numbers with non-numeric prefixes (such as +, -, or
148 whitespace). Disallowing whitespace prevents differential version
149 parsing between POSIX-based and Windows platforms. Fixes bug 21507
150 and part of 21508; bugfix on 0.0.8pre1.
152 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
153 - Permit the fchmod system call, to avoid crashing on startup when
154 starting with the seccomp2 sandbox and an unexpected set of
155 permissions on the data directory or its contents. Fixes bug
156 22516; bugfix on 0.2.5.4-alpha.
158 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
159 - Fix a memset() off the end of an array when packing cells. This
160 bug should be harmless in practice, since the corrupted bytes are
161 still in the same structure, and are always padding bytes,
162 ignored, or immediately overwritten, depending on compiler
163 behavior. Nevertheless, because the memset()'s purpose is to make
164 sure that any other cell-handling bugs can't expose bytes to the
165 network, we need to fix it. Fixes bug 22737; bugfix on
166 0.2.4.11-alpha. Fixes CID 1401591.
169 Changes in version 0.3.0.8 - 2017-06-08
170 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
171 remotely crash a hidden service with an assertion failure. Anyone
172 running a hidden service should upgrade to this version, or to some
173 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
175 Tor 0.3.0.8 also includes fixes for several key management bugs
176 that sometimes made relays unreliable, as well as several other
177 bugfixes described below.
179 o Major bugfixes (hidden service, relay, security, backport
181 - Fix a remotely triggerable assertion failure when a hidden service
182 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
183 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
184 - Fix a remotely triggerable assertion failure caused by receiving a
185 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
186 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
189 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
190 - When performing the v3 link handshake on a TLS connection, report
191 that we have the x509 certificate that we actually used on that
192 connection, even if we have changed certificates since that
193 connection was first opened. Previously, we would claim to have
194 used our most recent x509 link certificate, which would sometimes
195 make the link handshake fail. Fixes one case of bug 22460; bugfix
198 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
199 - Regenerate link and authentication certificates whenever the key
200 that signs them changes; also, regenerate link certificates
201 whenever the signed key changes. Previously, these processes were
202 only weakly coupled, and we relays could (for minutes to hours)
203 wind up with an inconsistent set of keys and certificates, which
204 other relays would not accept. Fixes two cases of bug 22460;
205 bugfix on 0.3.0.1-alpha.
206 - When sending an Ed25519 signing->link certificate in a CERTS cell,
207 send the certificate that matches the x509 certificate that we
208 used on the TLS connection. Previously, there was a race condition
209 if the TLS context rotated after we began the TLS handshake but
210 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
213 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
214 - Stop rejecting v3 hidden service descriptors because their size
215 did not match an old padding rule. Fixes bug 22447; bugfix on
218 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
219 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
220 December 2016 (of which ~126 were still functional) with a list of
221 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
222 2017. Resolves ticket 21564.
224 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
225 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
226 bug 22252; bugfix on 0.2.9.3-alpha.
228 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
229 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
230 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
232 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
233 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
234 months, and regenerate it when it is within one month of expiring.
235 Previously, we had generated this certificate at startup with a
236 ten-year lifetime, but that could lead to weird behavior when Tor
237 was started with a grossly inaccurate clock. Mitigates bug 22466;
238 mitigation on 0.3.0.1-alpha.
240 o Minor bugfixes (memory leak, directory authority, backport from
242 - When directory authorities reject a router descriptor due to
243 keypinning, free the router descriptor rather than leaking the
244 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
248 Changes in version 0.3.0.7 - 2017-05-15
249 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
250 of Tor 0.3.0.x, where an attacker could cause a Tor relay process to
251 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
252 clients are not affected.
254 o Major bugfixes (hidden service directory, security):
255 - Fix an assertion failure in the hidden service directory code,
256 which could be used by an attacker to remotely cause a Tor relay
257 process to exit. Relays running earlier versions of Tor 0.3.0.x
258 should upgrade. This security issue is tracked as TROVE-2017-002.
259 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
262 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
265 o Minor features (future-proofing):
266 - Tor no longer refuses to download microdescriptors or descriptors
267 if they are listed as "published in the future". This change will
268 eventually allow us to stop listing meaningful "published" dates
269 in microdescriptor consensuses, and thereby allow us to reduce the
270 resources required to download consensus diffs by over 50%.
271 Implements part of ticket 21642; implements part of proposal 275.
273 o Minor bugfixes (Linux seccomp2 sandbox):
274 - The getpid() system call is now permitted under the Linux seccomp2
275 sandbox, to avoid crashing with versions of OpenSSL (and other
276 libraries) that attempt to learn the process's PID by using the
277 syscall rather than the VDSO code. Fixes bug 21943; bugfix
281 Changes in version 0.3.0.6 - 2017-04-26
282 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
284 With the 0.3.0 series, clients and relays now use Ed25519 keys to
285 authenticate their link connections to relays, rather than the old
286 RSA1024 keys that they used before. (Circuit crypto has been
287 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
288 the guard selection and replacement algorithm to behave more robustly
289 in the presence of unreliable networks, and to resist guard-
292 This series also includes numerous other small features and bugfixes,
293 along with more groundwork for the upcoming hidden-services revamp.
295 Per our stable release policy, we plan to support the Tor 0.3.0
296 release series for at least the next nine months, or for three months
297 after the first stable release of the 0.3.1 series: whichever is
298 longer. If you need a release with long-term support, we recommend
299 that you stay with the 0.2.9 series.
301 Below are the changes since 0.3.0.5-rc. For a list of all changes
302 since 0.2.9, see the ReleaseNotes file.
304 o Minor features (geoip):
305 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
308 o Minor bugfixes (control port):
309 - The GETINFO extra-info/digest/<digest> command was broken because
310 of a wrong base16 decode return value check, introduced when
311 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
313 o Minor bugfixes (crash prevention):
314 - Fix a (currently untriggerable, but potentially dangerous) crash
315 bug when base32-encoding inputs whose sizes are not a multiple of
316 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
319 Changes in version 0.3.0.5-rc - 2017-04-05
320 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
321 0.3.0 release series.
323 This is the second release candidate in the Tor 0.3.0 series, and has
324 much fewer changes than the first. If we find no new bugs or
325 regressions here, the first stable 0.3.0 release will be nearly
328 o Major bugfixes (crash, directory connections):
329 - Fix a rare crash when sending a begin cell on a circuit whose
330 linked directory connection had already been closed. Fixes bug
331 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
333 o Major bugfixes (guard selection):
334 - Fix a guard selection bug where Tor would refuse to bootstrap in
335 some cases if the user swapped a bridge for another bridge in
336 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
337 Reported by "torvlnt33r".
339 o Minor features (geoip):
340 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
343 o Minor bugfix (compilation):
344 - Fix a warning when compiling hs_service.c. Previously, it had no
345 exported symbols when compiled for libor.a, resulting in a
346 compilation warning from clang. Fixes bug 21825; bugfix
349 o Minor bugfixes (hidden services):
350 - Make hidden services check for failed intro point connections,
351 even when they have exceeded their intro point creation limit.
352 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
353 - Make hidden services with 8 to 10 introduction points check for
354 failed circuits immediately after startup. Previously, they would
355 wait for 5 minutes before performing their first checks. Fixes bug
356 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
358 o Minor bugfixes (memory leaks):
359 - Fix a memory leak when using GETCONF on a port option. Fixes bug
360 21682; bugfix on 0.3.0.3-alpha.
362 o Minor bugfixes (relay):
363 - Avoid a double-marked-circuit warning that could happen when we
364 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
367 o Minor bugfixes (tests):
368 - Run the entry_guard_parse_from_state_full() test with the time set
369 to a specific date. (The guard state that this test was parsing
370 contained guards that had expired since the test was first
371 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
374 - Update the description of the directory server options in the
375 manual page, to clarify that a relay no longer needs to set
376 DirPort in order to be a directory cache. Closes ticket 21720.
379 Changes in version 0.3.0.4-rc - 2017-03-01
380 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
381 0.3.0 release series, and introduces a few reliability features to
382 keep them from coming back.
384 This is the first release candidate in the Tor 0.3.0 series. If we
385 find no new bugs or regressions here, the first stable 0.3.0 release
386 will be nearly identical to it.
388 o Major bugfixes (bridges):
389 - When the same bridge is configured multiple times with the same
390 identity, but at different address:port combinations, treat those
391 bridge instances as separate guards. This fix restores the ability
392 of clients to configure the same bridge with multiple pluggable
393 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
395 o Major bugfixes (hidden service directory v3):
396 - Stop crashing on a failed v3 hidden service descriptor lookup
397 failure. Fixes bug 21471; bugfixes on tor-0.3.0.1-alpha.
399 o Major bugfixes (parsing):
400 - When parsing a malformed content-length field from an HTTP
401 message, do not read off the end of the buffer. This bug was a
402 potential remote denial-of-service attack against Tor clients and
403 relays. A workaround was released in October 2016, to prevent this
404 bug from crashing Tor. This is a fix for the underlying issue,
405 which should no longer matter (if you applied the earlier patch).
406 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
407 using AFL (http://lcamtuf.coredump.cx/afl/).
408 - Fix an integer underflow bug when comparing malformed Tor
409 versions. This bug could crash Tor when built with
410 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
411 0.2.9.8, which were built with -ftrapv by default. In other cases
412 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
413 on 0.0.8pre1. Found by OSS-Fuzz.
415 o Minor feature (protocol versioning):
416 - Add new protocol version for proposal 224. HSIntro now advertises
417 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
419 o Minor features (directory authorities):
420 - Directory authorities now reject descriptors that claim to be
421 malformed versions of Tor. Helps prevent exploitation of
423 - Reject version numbers with components that exceed INT32_MAX.
424 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
425 Fixes bug 21450; bugfix on 0.0.8pre1.
427 o Minor features (geoip):
428 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
431 o Minor features (reliability, crash):
432 - Try better to detect problems in buffers where they might grow (or
433 think they have grown) over 2 GB in size. Diagnostic for
436 o Minor features (testing):
437 - During 'make test-network-all', if tor logs any warnings, ask
438 chutney to output them. Requires a recent version of chutney with
439 the 21572 patch. Implements 21570.
441 o Minor bugfixes (certificate expiration time):
442 - Avoid using link certificates that don't become valid till some
443 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
445 o Minor bugfixes (code correctness):
446 - Repair a couple of (unreachable or harmless) cases of the risky
447 comparison-by-subtraction pattern that caused bug 21278.
448 - Remove a redundant check for the UseEntryGuards option from the
449 options_transition_affects_guards() function. Fixes bug 21492;
450 bugfix on 0.3.0.1-alpha.
452 o Minor bugfixes (directory mirrors):
453 - Allow relays to use directory mirrors without a DirPort: these
454 relays need to be contacted over their ORPorts using a begindir
455 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
456 - Clarify the message logged when a remote relay is unexpectedly
457 missing an ORPort or DirPort: users were confusing this with a
458 local port. Fixes another case of bug 20711; bugfix
461 o Minor bugfixes (guards):
462 - Don't warn about a missing guard state on timeout-measurement
463 circuits: they aren't supposed to be using guards. Fixes an
464 instance of bug 21007; bugfix on 0.3.0.1-alpha.
465 - Silence a BUG() warning when attempting to use a guard whose
466 descriptor we don't know, and make this scenario less likely to
467 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
469 o Minor bugfixes (hidden service):
470 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
471 cells. Previously, we were using sizeof() on a pointer, instead of
472 the real destination buffer. Fortunately, that value was only used
473 to double-check that there was enough room--which was already
474 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
476 o Minor bugfixes (testing):
477 - Fix Raspbian build issues related to missing socket errno in
478 test_util.c. Fixes bug 21116; bugfix on tor-0.2.8.2. Patch
480 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
481 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
482 - Use bash in src/test/test-network.sh. This ensures we reliably
483 call chutney's newer tools/test-network.sh when available. Fixes
484 bug 21562; bugfix on 0.2.9.1-alpha.
487 - Small fixes to the fuzzing documentation. Closes ticket 21472.
490 Changes in version 0.2.9.10 - 2017-03-01
491 Tor 0.2.9.10 backports a security fix from later Tor release. It also
492 includes fixes for some major issues affecting directory authorities,
493 LibreSSL compatibility, and IPv6 correctness.
495 The Tor 0.2.9.x release series is now marked as a long-term-support
496 series. We intend to backport security fixes to 0.2.9.x until at
497 least January of 2020.
499 o Major bugfixes (directory authority, 0.3.0.3-alpha):
500 - During voting, when marking a relay as a probable sybil, do not
501 clear its BadExit flag: sybils can still be bad in other ways
502 too. (We still clear the other flags.) Fixes bug 21108; bugfix
505 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
506 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
507 any IPv6 addresses. Instead, only reject a port over IPv6 if the
508 exit policy rejects that port on more than an IPv6 /16 of
509 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
510 which rejected a relay's own IPv6 address by default. Fixes bug
511 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
513 o Major bugfixes (parsing, also in 0.3.0.4-rc):
514 - Fix an integer underflow bug when comparing malformed Tor
515 versions. This bug could crash Tor when built with
516 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
517 0.2.9.8, which were built with -ftrapv by default. In other cases
518 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
519 on 0.0.8pre1. Found by OSS-Fuzz.
521 o Minor features (directory authorities, also in 0.3.0.4-rc):
522 - Directory authorities now reject descriptors that claim to be
523 malformed versions of Tor. Helps prevent exploitation of
525 - Reject version numbers with components that exceed INT32_MAX.
526 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
527 Fixes bug 21450; bugfix on 0.0.8pre1.
529 o Minor features (geoip):
530 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
533 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
534 - Autoconf now checks to determine if OpenSSL structures are opaque,
535 instead of explicitly checking for OpenSSL version numbers. Part
537 - Support building with recent LibreSSL code that uses opaque
538 structures. Closes ticket 21359.
540 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
541 - Repair a couple of (unreachable or harmless) cases of the risky
542 comparison-by-subtraction pattern that caused bug 21278.
544 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
545 - The tor-resolve command line tool now rejects hostnames over 255
546 characters in length. Previously, it would silently truncate them,
547 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
548 Patch by "junglefowl".
551 Changes in version 0.3.0.3-alpha - 2017-02-03
552 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
553 0.3.0.x development series, including some that could cause
554 authorities to behave badly. There is also a fix for a longstanding
555 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
556 includes some smaller features and bugfixes.
558 The Tor 0.3.0.x release series is now in patch-freeze: no additional
559 features will be considered for inclusion in 0.3.0.x. We suspect that
560 some bugs will probably remain, however, and we encourage people to
563 o Major bugfixes (directory authority):
564 - During voting, when marking a relay as a probable sybil, do not
565 clear its BadExit flag: sybils can still be bad in other ways
566 too. (We still clear the other flags.) Fixes bug 21108; bugfix
568 - When deciding whether we have just found a router to be reachable,
569 do not penalize it for not having performed an Ed25519 link
570 handshake if it does not claim to support an Ed25519 handshake.
571 Previously, we would treat such relays as non-running. Fixes bug
572 21107; bugfix on 0.3.0.1-alpha.
574 o Major bugfixes (entry guards):
575 - Stop trying to build circuits through entry guards for which we
576 have no descriptor. Also, stop crashing in the case that we *do*
577 accidentally try to build a circuit in such a state. Fixes bug
578 21242; bugfix on 0.3.0.1-alpha.
580 o Major bugfixes (IPv6 Exits):
581 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
582 any IPv6 addresses. Instead, only reject a port over IPv6 if the
583 exit policy rejects that port on more than an IPv6 /16 of
584 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
585 which rejected a relay's own IPv6 address by default. Fixes bug
586 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
588 o Minor feature (client):
589 - Enable IPv6 traffic on the SocksPort by default. To disable this,
590 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
592 o Minor feature (fallback scripts):
593 - Add a check_existing mode to updateFallbackDirs.py, which checks
594 if fallbacks in the hard-coded list are working. Closes ticket
595 20174. Patch by haxxpop.
597 o Minor features (ciphersuite selection):
598 - Clients now advertise a list of ciphersuites closer to the ones
599 preferred by Firefox. Closes part of ticket 15426.
600 - Allow relays to accept a wider range of ciphersuites, including
601 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
603 o Minor features (controller, configuration):
604 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
605 and so on, now comes with a __*Port variant that will not be saved
606 to the torrc file by the controller's SAVECONF command. This
607 change allows TorBrowser to set up a single-use domain socket for
608 each time it launches Tor. Closes ticket 20956.
609 - The GETCONF command can now query options that may only be
610 meaningful in context-sensitive lists. This allows the controller
611 to query the mixed SocksPort/__SocksPort style options introduced
612 in feature 20956. Implements ticket 21300.
614 o Minor features (portability, compilation):
615 - Autoconf now checks to determine if OpenSSL structures are opaque,
616 instead of explicitly checking for OpenSSL version numbers. Part
618 - Support building with recent LibreSSL code that uses opaque
619 structures. Closes ticket 21359.
621 o Minor features (relay):
622 - We now allow separation of exit and relay traffic to different
623 source IP addresses, using the OutboundBindAddressExit and
624 OutboundBindAddressOR options respectively. Closes ticket 17975.
625 Written by Michael Sonntag.
627 o Minor bugfix (logging):
628 - Don't recommend the use of Tor2web in non-anonymous mode.
629 Recommending Tor2web is a bad idea because the client loses all
630 anonymity. Tor2web should only be used in specific cases by users
631 who *know* and understand the issues. Fixes bug 21294; bugfix
634 o Minor bugfixes (client):
635 - Always recover from failures in extend_info_from_node(), in an
636 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
637 bugfix on 0.2.3.1-alpha.
639 o Minor bugfixes (client, entry guards):
640 - Fix a bug warning (with backtrace) when we fail a channel that
641 circuits to fallback directories on it. Fixes bug 21128; bugfix
643 - Fix a spurious bug warning (with backtrace) when removing an
644 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
645 - Fix a bug of the new guard algorithm where tor could stall for up
646 to 10 minutes before retrying a guard after a long period of no
647 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
648 - Do not try to build circuits until we have descriptors for our
649 primary entry guards. Related to fix for bug 21242.
651 o Minor bugfixes (configure, autoconf):
652 - Rename the configure option --enable-expensive-hardening to
653 --enable-fragile-hardening. Expensive hardening makes the tor
654 daemon abort when some kinds of issues are detected. Thus, it
655 makes tor more at risk of remote crashes but safer against RCE or
656 heartbleed bug category. We now try to explain this issue in a
657 message from the configure script. Fixes bug 21290; bugfix
660 o Minor bugfixes (controller):
661 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
662 20824; bugfix on 0.3.0.1-alpha.
664 o Minor bugfixes (hidden service):
665 - Clean up the code for expiring intro points with no associated
666 circuits. It was causing, rarely, a service with some expiring
667 introduction points to not open enough additional introduction
668 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
669 - Stop setting the torrc option HiddenServiceStatistics to "0" just
670 because we're not a bridge or relay. Instead, we preserve whatever
671 value the user set (or didn't set). Fixes bug 21150; bugfix
673 - Resolve two possible underflows which could lead to creating and
674 closing a lot of introduction point circuits in a non-stop loop.
675 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
677 o Minor bugfixes (portability):
678 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
679 It is supported by OpenBSD itself, and also by most OpenBSD
680 variants (such as Bitrig). Fixes bug 20980; bugfix
682 - When mapping a file of length greater than SIZE_MAX, do not
683 silently truncate its contents. This issue could occur on 32 bit
684 systems with large file support and files which are larger than 4
685 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
687 o Minor bugfixes (tor-resolve):
688 - The tor-resolve command line tool now rejects hostnames over 255
689 characters in length. Previously, it would silently truncate them,
690 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
691 Patch by "junglefowl".
693 o Minor bugfixes (Windows services):
694 - Be sure to initialize the monotonic time subsystem before using
695 it, even when running as an NT service. Fixes bug 21356; bugfix
699 Changes in version 0.3.0.2-alpha - 2017-01-23
700 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
701 cause relays and clients to crash, even if they were not built with
702 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
703 versions, and also affects 0.3.0.1-alpha: all relays running an affected
704 version should upgrade.
706 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
707 time-to-live values, makes directory authorities enforce the 1-to-1
708 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
709 client-side onion service reachability bug, does better at selecting
710 the set of fallback directories, and more.
712 o Major bugfixes (security, also in 0.2.9.9):
713 - Downgrade the "-ftrapv" option from "always on" to "only on when
714 --enable-expensive-hardening is provided." This hardening option, like
715 others, can turn survivable bugs into crashes--and having it on by
716 default made a (relatively harmless) integer overflow bug into a
717 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
720 o Major features (security):
721 - Change the algorithm used to decide DNS TTLs on client and server
722 side, to better resist DNS-based correlation attacks like the
723 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
724 Feamster. Now relays only return one of two possible DNS TTL
725 values, and clients are willing to believe DNS TTL values up to 3
726 hours long. Closes ticket 19769.
728 o Major features (directory authority, security):
729 - The default for AuthDirPinKeys is now 1: directory authorities
730 will reject relays where the RSA identity key matches a previously
731 seen value, but the Ed25519 key has changed. Closes ticket 18319.
733 o Major bugfixes (client, guard, crash):
734 - In circuit_get_global_origin_list(), return the actual list of
735 origin circuits. The previous version of this code returned the
736 list of all the circuits, and could have caused strange bugs,
737 including possible crashes. Fixes bug 21118; bugfix
740 o Major bugfixes (client, onion service, also in 0.2.9.9):
741 - Fix a client-side onion service reachability bug, where multiple
742 socks requests to an onion service (or a single slow request)
743 could cause us to mistakenly mark some of the service's
744 introduction points as failed, and we cache that failure so
745 eventually we run out and can't reach the service. Also resolves a
746 mysterious "Remote server sent bogus reason code 65021" log
747 warning. The bug was introduced in ticket 17218, where we tried to
748 remember the circuit end reason as a uint16_t, which mangled
749 negative values. Partially fixes bug 21056 and fixes bug 20307;
750 bugfix on 0.2.8.1-alpha.
752 o Major bugfixes (DNS):
753 - Fix a bug that prevented exit nodes from caching DNS records for
754 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
756 o Minor features (controller):
757 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
758 shared-random values to the controller. Closes ticket 19925.
760 o Minor features (entry guards):
761 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
762 break regression tests.
763 - Require UseEntryGuards when UseBridges is set, in order to make
764 sure bridges aren't bypassed. Resolves ticket 20502.
766 o Minor features (fallback directories):
767 - Select 200 fallback directories for each release. Closes
769 - Allow 3 fallback relays per operator, which is safe now that we
770 are choosing 200 fallback relays. Closes ticket 20912.
771 - Exclude relays affected by bug 20499 from the fallback list.
772 Exclude relays from the fallback list if they are running versions
773 known to be affected by bug 20499, or if in our tests they deliver
774 a stale consensus (i.e. one that expired more than 24 hours ago).
776 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
778 - Require fallback directories to have the same address and port for
779 7 days (now that we have enough relays with this stability).
780 Relays whose OnionOO stability timer is reset on restart by bug
781 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
782 this issue. Closes ticket 20880; maintains short-term fix
784 - Require fallbacks to have flags for 90% of the time (weighted
785 decaying average), rather than 95%. This allows at least 73% of
786 clients to bootstrap in the first 5 seconds without contacting an
787 authority. Part of ticket 18828.
788 - Annotate updateFallbackDirs.py with the bandwidth and consensus
789 weight for each candidate fallback. Closes ticket 20878.
790 - Make it easier to change the output sort order of fallbacks.
792 - Display the relay fingerprint when downloading consensuses from
793 fallbacks. Closes ticket 20908.
795 o Minor features (geoip, also in 0.2.9.9):
796 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
799 o Minor features (next-gen onion service directories):
800 - Remove the "EnableOnionServicesV3" consensus parameter that we
801 introduced in 0.3.0.1-alpha: relays are now always willing to act
802 as v3 onion service directories. Resolves ticket 19899.
804 o Minor features (linting):
805 - Enhance the changes file linter to warn on Tor versions that are
806 prefixed with "tor-". Closes ticket 21096.
808 o Minor features (logging):
809 - In several places, describe unset ed25519 keys as "<unset>",
810 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
812 o Minor bugfix (control protocol):
813 - The reply to a "GETINFO config/names" request via the control
814 protocol now spells the type "Dependent" correctly. This is a
815 breaking change in the control protocol. (The field seems to be
816 ignored by the most common known controllers.) Fixes bug 18146;
817 bugfix on 0.1.1.4-alpha.
819 o Minor bugfixes (bug resilience):
820 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
821 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
822 Hans Jerry Illikainen.
824 o Minor bugfixes (build):
825 - Replace obsolete Autoconf macros with their modern equivalent and
826 prevent similar issues in the future. Fixes bug 20990; bugfix
829 o Minor bugfixes (client, guards):
830 - Fix bug where Tor would think that there are circuits waiting for
831 better guards even though those circuits have been freed. Fixes
832 bug 21142; bugfix on 0.3.0.1-alpha.
834 o Minor bugfixes (config):
835 - Don't assert on startup when trying to get the options list and
836 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
837 options so of course they aren't ready yet. Fixes bug 21062;
838 bugfix on 0.2.9.3-alpha.
840 o Minor bugfixes (controller):
841 - Make the GETINFO interface for inquiring about entry guards
842 support the new guards backend. Fixes bug 20823; bugfix
845 o Minor bugfixes (dead code):
846 - Remove a redundant check for PidFile changes at runtime in
847 options_transition_allowed(): this check is already performed
848 regardless of whether the sandbox is active. Fixes bug 21123;
849 bugfix on 0.2.5.4-alpha.
851 o Minor bugfixes (documentation):
852 - Update the tor manual page to document every option that can not
853 be changed while tor is running. Fixes bug 21122.
855 o Minor bugfixes (fallback directories):
856 - Stop failing when a relay has no uptime data in
857 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
858 - Avoid checking fallback candidates' DirPorts if they are down in
859 OnionOO. When a relay operator has multiple relays, this
860 prioritizes relays that are up over relays that are down. Fixes
861 bug 20926; bugfix on 0.2.8.3-alpha.
862 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
863 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
865 o Minor bugfixes (guards, bootstrapping):
866 - When connecting to a directory guard during bootstrap, do not mark
867 the guard as successful until we receive a good-looking directory
868 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
870 o Minor bugfixes (onion services):
871 - Fix the config reload pruning of old vs new services so it
872 actually works when both ephemeral and non-ephemeral services are
873 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
874 - Allow the number of introduction points to be as low as 0, rather
875 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
877 o Minor bugfixes (IPv6):
878 - Make IPv6-using clients try harder to find an IPv6 directory
879 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
880 - When IPv6 addresses have not been downloaded yet (microdesc
881 consensus documents don't list relay IPv6 addresses), use hard-
882 coded addresses for authorities, fallbacks, and configured
883 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
884 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
886 o Minor bugfixes (memory leaks):
887 - Fix a memory leak when configuring hidden services. Fixes bug
888 20987; bugfix on 0.3.0.1-alpha.
890 o Minor bugfixes (portability, also in 0.2.9.9):
891 - Avoid crashing when Tor is built using headers that contain
892 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
893 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
895 - Fix Libevent detection on platforms without Libevent 1 headers
896 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
898 o Minor bugfixes (relay):
899 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
900 initializing the keys would reset the DataDirectory to 0700
901 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
902 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
904 o Minor bugfixes (testing):
905 - Remove undefined behavior from the backtrace generator by removing
906 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
908 o Minor bugfixes (unit tests):
909 - Allow the unit tests to pass even when DNS lookups of bogus
910 addresses do not fail as expected. Fixes bug 20862 and 20863;
911 bugfix on unit tests introduced in 0.2.8.1-alpha
912 through 0.2.9.4-alpha.
914 o Code simplification and refactoring:
915 - Refactor code to manipulate global_origin_circuit_list into
916 separate functions. Closes ticket 20921.
918 o Documentation (formatting):
919 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
920 blocks were incorrectly appearing. Closes ticket 20885.
922 o Documentation (man page):
923 - Clarify many options in tor.1 and add some min/max values for
924 HiddenService options. Closes ticket 21058.
927 Changes in version 0.2.9.9 - 2017-01-23
928 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
929 cause relays and clients to crash, even if they were not built with
930 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
931 versions, and also affects 0.3.0.1-alpha: all relays running an affected
932 version should upgrade.
934 This release also resolves a client-side onion service reachability
935 bug, and resolves a pair of small portability issues.
937 o Major bugfixes (security):
938 - Downgrade the "-ftrapv" option from "always on" to "only on when
939 --enable-expensive-hardening is provided." This hardening option,
940 like others, can turn survivable bugs into crashes -- and having
941 it on by default made a (relatively harmless) integer overflow bug
942 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
943 bugfix on 0.2.9.1-alpha.
945 o Major bugfixes (client, onion service):
946 - Fix a client-side onion service reachability bug, where multiple
947 socks requests to an onion service (or a single slow request)
948 could cause us to mistakenly mark some of the service's
949 introduction points as failed, and we cache that failure so
950 eventually we run out and can't reach the service. Also resolves a
951 mysterious "Remote server sent bogus reason code 65021" log
952 warning. The bug was introduced in ticket 17218, where we tried to
953 remember the circuit end reason as a uint16_t, which mangled
954 negative values. Partially fixes bug 21056 and fixes bug 20307;
955 bugfix on 0.2.8.1-alpha.
957 o Minor features (geoip):
958 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
961 o Minor bugfixes (portability):
962 - Avoid crashing when Tor is built using headers that contain
963 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
964 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
966 - Fix Libevent detection on platforms without Libevent 1 headers
967 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
970 Changes in version 0.3.0.1-alpha - 2016-12-19
971 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
972 series. It strengthens Tor's link and circuit handshakes by
973 identifying relays by their Ed25519 keys, improves the algorithm that
974 clients use to choose and maintain their list of guards, and includes
975 additional backend support for the next-generation hidden service
976 design. It also contains numerous other small features and
977 improvements to security, correctness, and performance.
979 Below are the changes since 0.2.9.8.
981 o Major features (guard selection algorithm):
982 - Tor's guard selection algorithm has been redesigned from the
983 ground up, to better support unreliable networks and restrictive
984 sets of entry nodes, and to better resist guard-capture attacks by
985 hostile local networks. Implements proposal 271; closes
988 o Major features (next-generation hidden services):
989 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
990 prop224 aka "Next Generation Hidden Services". Service and clients
991 don't use this functionality yet. Closes ticket 19043. Based on
992 initial code by Alec Heifetz.
993 - Relays now support the HSDir version 3 protocol, so that they can
994 can store and serve v3 descriptors. This is part of the next-
995 generation onion service work detailled in proposal 224. Closes
998 o Major features (protocol, ed25519 identity keys):
999 - Relays now use Ed25519 to prove their Ed25519 identities and to
1000 one another, and to clients. This algorithm is faster and more
1001 secure than the RSA-based handshake we've been doing until now.
1002 Implements the second big part of proposal 220; Closes
1004 - Clients now support including Ed25519 identity keys in the EXTEND2
1005 cells they generate. By default, this is controlled by a consensus
1006 parameter, currently disabled. You can turn this feature on for
1007 testing by setting ExtendByEd25519ID in your configuration. This
1008 might make your traffic appear different than the traffic
1009 generated by other users, however. Implements part of ticket
1010 15056; part of proposal 220.
1011 - Relays now understand requests to extend to other relays by their
1012 Ed25519 identity keys. When an Ed25519 identity key is included in
1013 an EXTEND2 cell, the relay will only extend the circuit if the
1014 other relay can prove ownership of that identity. Implements part
1015 of ticket 15056; part of proposal 220.
1017 o Major bugfixes (scheduler):
1018 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
1019 caused the channel scheduler to behave more or less randomly,
1020 rather than preferring channels with higher-priority circuits.
1021 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
1023 o Minor features (controller):
1024 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
1025 rather than "unrecognized." Closes ticket 20389; patch from
1028 o Minor features (diagnostic, directory client):
1029 - Warn when we find an unexpected inconsistency in directory
1030 download status objects. Prevents some negative consequences of
1033 o Minor features (directory authority):
1034 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
1035 default) to control whether authorities should try to probe relays
1036 by their Ed25519 link keys. This option will go away in a few
1037 releases--unless we encounter major trouble in our ed25519 link
1038 protocol rollout, in which case it will serve as a safety option.
1040 o Minor features (directory cache):
1041 - Relays and bridges will now refuse to serve the consensus they
1042 have if they know it is too old for a client to use. Closes
1045 o Minor features (ed25519 link handshake):
1046 - Advertise support for the ed25519 link handshake using the
1047 subprotocol-versions mechanism, so that clients can tell which
1048 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
1050 o Minor features (fingerprinting resistence, authentication):
1051 - Extend the length of RSA keys used for TLS link authentication to
1052 2048 bits. (These weren't used for forward secrecy; for forward
1053 secrecy, we used P256.) Closes ticket 13752.
1055 o Minor features (infrastructure):
1056 - Implement smartlist_add_strdup() function. Replaces the use of
1057 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
1059 o Minor bugfixes (client):
1060 - When clients that use bridges start up with a cached consensus on
1061 disk, they were ignoring it and downloading a new one. Now they
1062 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
1064 o Minor bugfixes (configuration):
1065 - Accept non-space whitespace characters after the severity level in
1066 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
1067 - Support "TByte" and "TBytes" units in options given in bytes.
1068 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
1069 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
1071 o Minor bugfixes (consensus weight):
1072 - Add new consensus method that initializes bw weights to 1 instead
1073 of 0. This prevents a zero weight from making it all the way to
1074 the end (happens in small testing networks) and causing an error.
1075 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
1077 o Minor bugfixes (descriptors):
1078 - Correctly recognise downloaded full descriptors as valid, even
1079 when using microdescriptors as circuits. This affects clients with
1080 FetchUselessDescriptors set, and may affect directory authorities.
1081 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
1083 o Minor bugfixes (directory system):
1084 - Download all consensus flavors, descriptors, and authority
1085 certificates when FetchUselessDescriptors is set, regardless of
1086 whether tor is a directory cache or not. Fixes bug 20667; bugfix
1087 on all recent tor versions.
1088 - Bridges and relays now use microdescriptors (like clients do)
1089 rather than old-style router descriptors. Now bridges will blend
1090 in with clients in terms of the circuits they build. Fixes bug
1091 6769; bugfix on 0.2.3.2-alpha.
1093 o Minor bugfixes (ed25519 certificates):
1094 - Correctly interpret ed25519 certificates that would expire some
1095 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
1097 o Minor bugfixes (hidden services):
1098 - Stop ignoring misconfigured hidden services. Instead, refuse to
1099 start tor until the misconfigurations have been corrected. Fixes
1100 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
1103 o Minor bugfixes (memory leak at exit):
1104 - Fix a small harmless memory leak at exit of the previously unused
1105 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
1108 o Minor bugfixes (util):
1109 - When finishing writing a file to disk, if we were about to replace
1110 the file with the temporary file created before and we fail to
1111 replace it, remove the temporary file so it doesn't stay on disk.
1112 Fixes bug 20646; bugfix on tor-0.2.0.7-alpha. Patch by fk.
1114 o Minor bugfixes (Windows):
1115 - Check for getpagesize before using it to mmap files. This fixes
1116 compilation in some MinGW environments. Fixes bug 20530; bugfix on
1117 0.1.2.1-alpha. Reported by "ice".
1119 o Code simplification and refactoring:
1120 - Abolish all global guard context in entrynodes.c; replace with new
1121 guard_selection_t structure as preparation for proposal 271.
1122 Closes ticket 19858.
1123 - Introduce rend_service_is_ephemeral() that tells if given onion
1124 service is ephemeral. Replace unclear NULL-checkings for service
1125 directory with this function. Closes ticket 20526.
1126 - Extract magic numbers in circuituse.c into defined variables.
1127 - Refactor circuit_is_available_for_use to remove unnecessary check.
1128 - Refactor circuit_predict_and_launch_new for readability and
1129 testability. Closes ticket 18873.
1130 - Refactor large if statement in purpose_needs_anonymity to use
1131 switch statement instead. Closes part of ticket 20077.
1132 - Refactor the hashing API to return negative values for errors, as
1133 is done as throughout the codebase. Closes ticket 20717.
1134 - Remove data structures that were used to index or_connection
1135 objects by their RSA identity digests. These structures are fully
1136 redundant with the similar structures used in the
1137 channel abstraction.
1138 - Remove duplicate code in the channel_write_*cell() functions.
1139 Closes ticket 13827; patch from Pingl.
1140 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
1141 use only purpose_needs_anonymity. Closes part of ticket 20077.
1142 - The code to generate and parse EXTEND and EXTEND2 cells has been
1143 replaced with code automatically generated by the
1147 - Include the "TBits" unit in Tor's man page. Fixes part of bug
1148 20622; bugfix on tor-0.2.5.1-alpha.
1149 - Change '1' to 'weight_scale' in consensus bw weights calculation
1150 comments, as that is reality. Closes ticket 20273. Patch
1152 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
1153 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
1154 on tor-0.2.5.6-alpha.
1155 - Stop the man page from incorrectly stating that HiddenServiceDir
1156 must already exist. Fixes 20486.
1157 - Clarify that when ClientRejectInternalAddresses is enabled (which
1158 is the default), multicast DNS hostnames for machines on the local
1159 network (of the form *.local) are also rejected. Closes
1163 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
1164 limit for relays running on a single IP applies to authority IP
1165 addresses as well as to non-authority IP addresses. Closes
1167 - The UseDirectoryGuards torrc option no longer exists: all users
1168 that use entry guards will also use directory guards. Related to
1169 proposal 271; implements part of ticket 20831.
1172 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
1173 from "overcaffeinated".
1174 - Perform the coding style checks when running the tests and fail
1175 when coding style violations are found. Closes ticket 5500.
1176 - Add tests for networkstatus_compute_bw_weights_v10.
1177 - Add unit tests circuit_predict_and_launch_new.
1178 - Extract dummy_origin_circuit_new so it can be used by other
1182 Changes in version 0.2.8.12 - 2016-12-19
1183 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
1184 below) where Tor clients could crash when attempting to visit a
1185 hostile hidden service. Clients are recommended to upgrade as packages
1186 become available for their systems.
1188 It also includes an updated list of fallback directories, backported
1191 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
1192 backported to 0.2.8 in the future.
1194 o Major bugfixes (parsing, security, backported from 0.2.9.8):
1195 - Fix a bug in parsing that could cause clients to read a single
1196 byte past the end of an allocated region. This bug could be used
1197 to cause hardened clients (built with --enable-expensive-hardening)
1198 to crash if they tried to visit a hostile hidden service. Non-
1199 hardened clients are only affected depending on the details of
1200 their platform's memory allocator. Fixes bug 21018; bugfix on
1201 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
1202 2016-12-002 and as CVE-2016-1254.
1204 o Minor features (fallback directory list, backported from 0.2.9.8):
1205 - Replace the 81 remaining fallbacks of the 100 originally
1206 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
1207 fallbacks (123 new, 54 existing, 27 removed) generated in December
1208 2016. Resolves ticket 20170.
1210 o Minor features (geoip, backported from 0.2.9.7-rc):
1211 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
1215 Changes in version 0.2.9.8 - 2016-12-19
1216 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
1218 The Tor 0.2.9 series makes mandatory a number of security features
1219 that were formerly optional. It includes support for a new shared-
1220 randomness protocol that will form the basis for next generation
1221 hidden services, includes a single-hop hidden service mode for
1222 optimizing .onion services that don't actually want to be hidden,
1223 tries harder not to overload the directory authorities with excessive
1224 downloads, and supports a better protocol versioning scheme for
1225 improved compatibility with other implementations of the Tor protocol.
1227 And of course, there are numerous other bugfixes and improvements.
1229 This release also includes a fix for a medium-severity issue (bug
1230 21018 below) where Tor clients could crash when attempting to visit a
1231 hostile hidden service. Clients are recommended to upgrade as packages
1232 become available for their systems.
1234 Below are the changes since 0.2.9.7-rc. For a list of all changes
1235 since 0.2.8, see the ReleaseNotes file.
1237 o Major bugfixes (parsing, security):
1238 - Fix a bug in parsing that could cause clients to read a single
1239 byte past the end of an allocated region. This bug could be used
1240 to cause hardened clients (built with --enable-expensive-hardening)
1241 to crash if they tried to visit a hostile hidden service. Non-
1242 hardened clients are only affected depending on the details of
1243 their platform's memory allocator. Fixes bug 21018; bugfix on
1244 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
1245 2016-12-002 and as CVE-2016-1254.
1247 o Minor features (fallback directory list):
1248 - Replace the 81 remaining fallbacks of the 100 originally
1249 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
1250 fallbacks (123 new, 54 existing, 27 removed) generated in December
1251 2016. Resolves ticket 20170.
1254 Changes in version 0.2.9.7-rc - 2016-12-12
1255 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
1256 including a few that had prevented tests from passing on
1259 o Minor features (geoip):
1260 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
1263 o Minor bugfix (build):
1264 - The current Git revision when building from a local repository is
1265 now detected correctly when using git worktrees. Fixes bug 20492;
1266 bugfix on 0.2.3.9-alpha.
1268 o Minor bugfixes (directory authority):
1269 - When computing old Tor protocol line version in protover, we were
1270 looking at 0.2.7.5 twice instead of a specific case for
1271 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
1273 o Minor bugfixes (download scheduling):
1274 - Resolve a "bug" warning when considering a download schedule whose
1275 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
1277 o Minor bugfixes (logging):
1278 - Downgrade a harmless log message about the
1279 pending_entry_connections list from "warn" to "info". Mitigates
1282 o Minor bugfixes (memory leak):
1283 - Fix a small memory leak when receiving AF_UNIX connections on a
1284 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
1285 - When moving a signed descriptor object from a source to an
1286 existing destination, free the allocated memory inside that
1287 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
1289 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
1290 - Fix a memory leak and use-after-free error when removing entries
1291 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
1292 0.2.5.5-alpha. Patch from "cypherpunks".
1294 o Minor bugfixes (portability):
1295 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
1296 Fixes bug 20935; bugfix on 0.2.9.6-rc.
1298 o Minor bugfixes (unit tests):
1299 - Stop expecting NetBSD unit tests to report success for ipfw. Part
1300 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
1301 - Fix tolerances in unit tests for monotonic time comparisons
1302 between nanoseconds and microseconds. Previously, we accepted a 10
1303 us difference only, which is not realistic on every platform's
1304 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
1305 - Remove a double-free in the single onion service unit test. Stop
1306 ignoring a return value. Make future changes less error-prone.
1307 Fixes bug 20864; bugfix on 0.2.9.6-rc.
1310 Changes in version 0.2.8.11 - 2016-12-08
1311 Tor 0.2.8.11 backports fixes for additional portability issues that
1312 could prevent Tor from building correctly on OSX Sierra, or with
1313 OpenSSL 1.1. Affected users should upgrade; others can safely stay
1316 o Minor bugfixes (portability):
1317 - Avoid compilation errors when building on OSX Sierra. Sierra began
1318 to support the getentropy() and clock_gettime() APIs, but created
1319 a few problems in doing so. Tor 0.2.9 has a more thorough set of
1320 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
1321 monotonic time interfaces. Fixes bug 20865. Bugfix
1324 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
1325 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
1326 architectures. Closes ticket 20588.
1329 Changes in version 0.2.8.10 - 2016-12-02
1330 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
1331 unusable after they left standby mode. It also backports fixes for
1332 a few portability issues and a small but problematic memory leak.
1334 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
1335 - When Tor leaves standby because of a new application request, open
1336 circuits as needed to serve that request. Previously, we would
1337 potentially wait a very long time. Fixes part of bug 19969; bugfix
1340 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
1341 - Clients now respond to new application stream requests immediately
1342 when they arrive, rather than waiting up to one second before
1343 starting to handle them. Fixes part of bug 19969; bugfix
1346 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
1347 - Work around a bug in the OSX 10.12 SDK that would prevent us from
1348 successfully targeting earlier versions of OSX. Resolves
1351 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
1352 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
1353 20551; bugfix on 0.2.1.1-alpha.
1355 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
1356 - Work around a memory leak in OpenSSL 1.1 when encoding public
1357 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
1359 o Minor features (geoip):
1360 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
1363 Changes in version 0.2.9.6-rc - 2016-12-02
1364 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
1365 version. We hope that it will be ready to become stable soon, and we
1366 encourage everyone to test this release. If no showstopper bugs are
1367 found here, the next 0.2.9 release will be stable.
1369 o Major bugfixes (relay, resolver, logging):
1370 - For relays that don't know their own address, avoid attempting a
1371 local hostname resolve for each descriptor we download. This
1372 will cut down on the number of "Success: chose address 'x.x.x.x'"
1373 log lines, and also avoid confusing clock jumps if the resolver
1374 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
1376 o Minor bugfixes (client, fascistfirewall):
1377 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
1378 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
1380 o Minor bugfixes (hidden services):
1381 - Stop ignoring the anonymity status of saved keys for hidden
1382 services and single onion services when first starting tor.
1383 Instead, refuse to start tor if any hidden service key has been
1384 used in a different hidden service anonymity mode. Fixes bug
1385 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
1387 o Minor bugfixes (portability):
1388 - Work around a bug in the OSX 10.12 SDK that would prevent us from
1389 successfully targeting earlier versions of OSX. Resolves
1391 - Run correctly when built on Windows build environments that
1392 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
1394 o Minor bugfixes (single onion services, Tor2web):
1395 - Stop complaining about long-term one-hop circuits deliberately
1396 created by single onion services and Tor2web. These log messages
1397 are intended to diagnose issue 8387, which relates to circuits
1398 hanging around forever for no reason. Fixes bug 20613; bugfix on
1399 0.2.9.1-alpha. Reported by "pastly".
1401 o Minor bugfixes (unit tests):
1402 - Stop spurious failures in the local interface address discovery
1403 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
1407 - Correct the minimum bandwidth value in torrc.sample, and queue a
1408 corresponding change for torrc.minimal. Closes ticket 20085.
1411 Changes in version 0.2.9.5-alpha - 2016-11-08
1412 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
1413 version. We believe one or two probably remain, and we encourage
1414 everyone to test this release.
1416 o Major bugfixes (client performance):
1417 - Clients now respond to new application stream requests immediately
1418 when they arrive, rather than waiting up to one second before
1419 starting to handle them. Fixes part of bug 19969; bugfix
1422 o Major bugfixes (client reliability):
1423 - When Tor leaves standby because of a new application request, open
1424 circuits as needed to serve that request. Previously, we would
1425 potentially wait a very long time. Fixes part of bug 19969; bugfix
1428 o Major bugfixes (download scheduling):
1429 - When using an exponential backoff schedule, do not give up on
1430 downloading just because we have failed a bunch of times. Since
1431 each delay is longer than the last, retrying indefinitely won't
1432 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
1433 - If a consensus expires while we are waiting for certificates to
1434 download, stop waiting for certificates.
1435 - If we stop waiting for certificates less than a minute after we
1436 started downloading them, do not consider the certificate download
1437 failure a separate failure. Fixes bug 20533; bugfix
1439 - Remove the maximum delay on exponential-backoff scheduling. Since
1440 we now allow an infinite number of failures (see ticket 20536), we
1441 must now allow the time to grow longer on each failure. Fixes part
1442 of bug 20534; bugfix on 0.2.9.1-alpha.
1443 - Make our initial download delays closer to those from 0.2.8. Fixes
1444 another part of bug 20534; bugfix on 0.2.9.1-alpha.
1445 - When determining when to download a directory object, handle times
1446 after 2038 if the operating system supports them. (Someday this
1447 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
1448 - When using exponential backoff in test networks, use a lower
1449 exponent, so the delays do not vary as much. This helps test
1450 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
1452 o Minor features (geoip):
1453 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
1456 o Minor bugfixes (client directory scheduling):
1457 - Treat "relay too busy to answer request" as a failed request and a
1458 reason to back off on our retry frequency. This is safe now that
1459 exponential backoffs retry indefinitely, and avoids a bug where we
1460 would reset our download schedule erroneously. Fixes bug 20593;
1461 bugfix on 0.2.9.1-alpha.
1463 o Minor bugfixes (client, logging):
1464 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
1465 assume all nodes support EXTEND2. Use ntor whenever a key is
1466 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
1467 - On DNSPort, stop logging a BUG warning on a failed hostname
1468 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
1470 o Minor bugfixes (hidden services):
1471 - When configuring hidden services, check every hidden service
1472 directory's permissions. Previously, we only checked the last
1473 hidden service. Fixes bug 20529; bugfix the work to fix 13942
1476 o Minor bugfixes (portability):
1477 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
1478 architectures. Closes ticket 20588.
1479 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
1480 removed the ECDH ciphers which caused the tests to fail on
1481 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
1482 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
1483 20551; bugfix on 0.2.1.1-alpha.
1485 o Minor bugfixes (relay bootstrap):
1486 - Ensure relays don't make multiple connections during bootstrap.
1487 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
1489 o Minor bugfixes (relay):
1490 - Work around a memory leak in OpenSSL 1.1 when encoding public
1491 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
1492 - Avoid a small memory leak when informing worker threads about
1493 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
1494 - Do not try to parallelize workers more than 16x without the user
1495 explicitly configuring us to do so, even if we do detect more than
1496 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
1498 o Minor bugfixes (single onion services):
1499 - Start correctly when creating a single onion service in a
1500 directory that did not previously exist. Fixes bug 20484; bugfix
1503 o Minor bugfixes (testing):
1504 - Avoid a unit test failure on systems with over 16 detectable CPU
1505 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
1508 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
1509 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
1510 - Module-level documentation for several more modules. Closes
1511 tickets 19287 and 19290.
1514 Changes in version 0.2.8.9 - 2016-10-17
1515 Tor 0.2.8.9 backports a fix for a security hole in previous versions
1516 of Tor that would allow a remote attacker to crash a Tor client,
1517 hidden service, relay, or authority. All Tor users should upgrade to
1518 this version, or to 0.2.9.4-alpha. Patches will be released for older
1521 o Major features (security fixes, also in 0.2.9.4-alpha):
1522 - Prevent a class of security bugs caused by treating the contents
1523 of a buffer chunk as if they were a NUL-terminated string. At
1524 least one such bug seems to be present in all currently used
1525 versions of Tor, and would allow an attacker to remotely crash
1526 most Tor instances, especially those compiled with extra compiler
1527 hardening. With this defense in place, such bugs can't crash Tor,
1528 though we should still fix them as they occur. Closes ticket
1529 20384 (TROVE-2016-10-001).
1531 o Minor features (geoip):
1532 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
1536 Changes in version 0.2.9.4-alpha - 2016-10-17
1537 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
1538 that would allow a remote attacker to crash a Tor client, hidden
1539 service, relay, or authority. All Tor users should upgrade to this
1540 version, or to 0.2.8.9. Patches will be released for older versions
1543 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
1544 previous versions of Tor, including the implementation of a feature to
1545 future- proof the Tor ecosystem against protocol changes, some bug
1546 fixes necessary for Tor Browser to use unix domain sockets correctly,
1547 and several portability improvements. We anticipate that this will be
1548 the last alpha in the Tor 0.2.9 series, and that the next release will
1549 be a release candidate.
1551 o Major features (security fixes):
1552 - Prevent a class of security bugs caused by treating the contents
1553 of a buffer chunk as if they were a NUL-terminated string. At
1554 least one such bug seems to be present in all currently used
1555 versions of Tor, and would allow an attacker to remotely crash
1556 most Tor instances, especially those compiled with extra compiler
1557 hardening. With this defense in place, such bugs can't crash Tor,
1558 though we should still fix them as they occur. Closes ticket
1559 20384 (TROVE-2016-10-001).
1561 o Major features (subprotocol versions):
1562 - Tor directory authorities now vote on a set of recommended
1563 subprotocol versions, and on a set of required subprotocol
1564 versions. Clients and relays that lack support for a _required_
1565 subprotocol version will not start; those that lack support for a
1566 _recommended_ subprotocol version will warn the user to upgrade.
1567 Closes ticket 19958; implements part of proposal 264.
1568 - Tor now uses "subprotocol versions" to indicate compatibility.
1569 Previously, versions of Tor looked at the declared Tor version of
1570 a relay to tell whether they could use a given feature. Now, they
1571 should be able to rely on its declared subprotocol versions. This
1572 change allows compatible implementations of the Tor protocol(s) to
1573 exist without pretending to be 100% bug-compatible with particular
1574 releases of Tor itself. Closes ticket 19958; implements part of
1577 o Minor feature (fallback directories):
1578 - Remove broken fallbacks from the hard-coded fallback directory
1579 list. Closes ticket 20190; patch by teor.
1581 o Minor features (client, directory):
1582 - Since authorities now omit all routers that lack the Running and
1583 Valid flags, we assume that any relay listed in the consensus must
1584 have those flags. Closes ticket 20001; implements part of
1587 o Minor features (compilation, portability):
1588 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
1591 o Minor features (development tools, etags):
1592 - Teach the "make tags" Makefile target how to correctly find
1593 "MOCK_IMPL" function definitions. Patch from nherring; closes
1596 o Minor features (geoip):
1597 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
1600 o Minor features (unix domain sockets):
1601 - When configuring a unix domain socket for a SocksPort,
1602 ControlPort, or Hidden service, you can now wrap the address in
1603 quotes, using C-style escapes inside the quotes. This allows unix
1604 domain socket paths to contain spaces.
1606 o Minor features (virtual addresses):
1607 - Increase the maximum number of bits for the IPv6 virtual network
1608 prefix from 16 to 104. In this way, the condition for address
1609 allocation is less restrictive. Closes ticket 20151; feature
1612 o Minor bugfixes (address discovery):
1613 - Stop reordering IP addresses returned by the OS. This makes it
1614 more likely that Tor will guess the same relay IP address every
1615 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
1616 Reported by René Mayrhofer, patch by "cypherpunks".
1618 o Minor bugfixes (client, unix domain sockets):
1619 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
1620 the client address is meaningless. Fixes bug 20261; bugfix
1623 o Minor bugfixes (compilation, OpenBSD):
1624 - Detect Libevent2 functions correctly on systems that provide
1625 libevent2, but where libevent1 is linked with -levent. Fixes bug
1626 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
1628 o Minor bugfixes (configuration):
1629 - When parsing quoted configuration values from the torrc file,
1630 handle windows line endings correctly. Fixes bug 19167; bugfix on
1631 0.2.0.16-alpha. Patch from "Pingl".
1633 o Minor bugfixes (getpass):
1634 - Defensively fix a non-triggerable heap corruption at do_getpass()
1635 to protect ourselves from mistakes in the future. Fixes bug
1636 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
1639 o Minor bugfixes (hidden service):
1640 - Allow hidden services to run on IPv6 addresses even when the
1641 IPv6Exit option is not set. Fixes bug 18357; bugfix
1645 - Add module-level internal documentation for 36 C files that
1646 previously didn't have a high-level overview. Closes ticket #20385.
1648 o Required libraries:
1649 - When building with OpenSSL, Tor now requires version 1.0.1 or
1650 later. OpenSSL 1.0.0 and earlier are no longer supported by the
1651 OpenSSL team, and should not be used. Closes ticket 20303.
1654 Changes in version 0.2.9.3-alpha - 2016-09-23
1655 Tor 0.2.9.3-alpha adds improved support for entities that want to make
1656 high-performance services available through the Tor .onion mechanism
1657 without themselves receiving anonymity as they host those services. It
1658 also tries harder to ensure that all steps on a circuit are using the
1659 strongest crypto possible, strengthens some TLS properties, and
1660 resolves several bugs -- including a pair of crash bugs from the 0.2.8
1661 series. Anybody running an earlier version of 0.2.9.x should upgrade.
1663 o Major bugfixes (crash, also in 0.2.8.8):
1664 - Fix a complicated crash bug that could affect Tor clients
1665 configured to use bridges when replacing a networkstatus consensus
1666 in which one of their bridges was mentioned. OpenBSD users saw
1667 more crashes here, but all platforms were potentially affected.
1668 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
1670 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
1671 - Fix a timing-dependent assertion failure that could occur when we
1672 tried to flush from a circuit after having freed its cells because
1673 of an out-of-memory condition. Fixes bug 20203; bugfix on
1674 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
1677 o Major features (circuit building, security):
1678 - Authorities, relays and clients now require ntor keys in all
1679 descriptors, for all hops (except for rare hidden service protocol
1680 cases), for all circuits, and for all other roles. Part of
1682 - Tor authorities, relays, and clients only use ntor, except for
1683 rare cases in the hidden service protocol. Part of ticket 19163.
1685 o Major features (single-hop "hidden" services):
1686 - Add experimental HiddenServiceSingleHopMode and
1687 HiddenServiceNonAnonymousMode options. When both are set to 1,
1688 every hidden service on a Tor instance becomes a non-anonymous
1689 Single Onion Service. Single Onions make one-hop (direct)
1690 connections to their introduction and renzedvous points. One-hop
1691 circuits make Single Onion servers easily locatable, but clients
1692 remain location-anonymous. This is compatible with the existing
1693 hidden service implementation, and works on the current tor
1694 network without any changes to older relays or clients. Implements
1695 proposal 260, completes ticket 17178. Patch by teor and asn.
1697 o Major features (resource management):
1698 - Tor can now notice it is about to run out of sockets, and
1699 preemptively close connections of lower priority. (This feature is
1700 off by default for now, since the current prioritizing method is
1701 yet not mature enough. You can enable it by setting
1702 "DisableOOSCheck 0", but watch out: it might close some sockets
1703 you would rather have it keep.) Closes ticket 18640.
1705 o Major bugfixes (circuit building):
1706 - Hidden service client-to-intro-point and service-to-rendezvous-
1707 point circuits use the TAP key supplied by the protocol, to avoid
1708 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
1710 o Major bugfixes (compilation, OpenBSD):
1711 - Fix a Libevent-detection bug in our autoconf script that would
1712 prevent Tor from linking successfully on OpenBSD. Patch from
1713 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
1715 o Major bugfixes (hidden services):
1716 - Clients now require hidden services to include the TAP keys for
1717 their intro points in the hidden service descriptor. This prevents
1718 an inadvertent upgrade to ntor, which a malicious hidden service
1719 could use to distinguish clients by consensus version. Fixes bug
1720 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
1722 o Minor features (security, TLS):
1723 - Servers no longer support clients that without AES ciphersuites.
1724 (3DES is no longer considered an acceptable cipher.) We believe
1725 that no such Tor clients currently exist, since Tor has required
1726 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
1728 o Minor feature (fallback directories):
1729 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
1730 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
1731 2016. Closes ticket 20190; patch by teor.
1733 o Minor features (geoip, also in 0.2.8.8):
1734 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
1737 o Minor feature (port flags):
1738 - Add new flags to the *Port options to finer control over which
1739 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
1740 and the synthetic flag OnionTrafficOnly, which is equivalent to
1741 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
1742 18693; patch by "teor".
1744 o Minor features (directory authority):
1745 - After voting, if the authorities decide that a relay is not
1746 "Valid", they no longer include it in the consensus at all. Closes
1747 ticket 20002; implements part of proposal 272.
1749 o Minor features (testing):
1750 - Disable memory protections on OpenBSD when performing our unit
1751 tests for memwipe(). The test deliberately invokes undefined
1752 behavior, and the OpenBSD protections interfere with this. Patch
1753 from "rubiate". Closes ticket 20066.
1755 o Minor features (testing, ipv6):
1756 - Add the single-onion and single-onion-ipv6 chutney targets to
1757 "make test-network-all". This requires a recent chutney version
1758 with the single onion network flavours (git c72a652 or later).
1759 Closes ticket 20072; patch by teor.
1760 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
1761 tests. Remove bridges+hs, as it's somewhat redundant. This
1762 requires a recent chutney version that supports IPv6 clients,
1763 relays, and authorities. Closes ticket 20069; patch by teor.
1765 o Minor features (Tor2web):
1766 - Make Tor2web clients respect ReachableAddresses. This feature was
1767 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
1768 0.2.8.7. Implements feature 20034. Patch by teor.
1770 o Minor features (unit tests):
1771 - We've done significant work to make the unit tests run faster.
1772 - Our link-handshake unit tests now check that when invalid
1773 handshakes fail, they fail with the error messages we expected.
1774 - Our unit testing code that captures log messages no longer
1775 prevents them from being written out if the user asked for them
1776 (by passing --debug or --info or or --notice --warn to the "test"
1777 binary). This change prevents us from missing unexpected log
1778 messages simply because we were looking for others. Related to
1780 - The unit tests now log all warning messages with the "BUG" flag.
1781 Previously, they only logged errors by default. This change will
1782 help us make our testing code more correct, and make sure that we
1783 only hit this code when we mean to. In the meantime, however,
1784 there will be more warnings in the unit test logs than before.
1785 This is preparatory work for ticket 19999.
1786 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
1787 assertion as a test failure.
1789 o Minor bug fixes (circuits):
1790 - Use the CircuitBuildTimeout option whenever
1791 LearnCircuitBuildTimeout is disabled. Previously, we would respect
1792 the option when a user disabled it, but not when it was disabled
1793 because some other option was set. Fixes bug 20073; bugfix on
1794 0.2.4.12-alpha. Patch by teor.
1796 o Minor bugfixes (allocation):
1797 - Change how we allocate memory for large chunks on buffers, to
1798 avoid a (currently impossible) integer overflow, and to waste less
1799 space when allocating unusually large chunks. Fixes bug 20081;
1800 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
1801 - Always include orconfig.h before including any other C headers.
1802 Sometimes, it includes macros that affect the behavior of the
1803 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
1804 first version to use AC_USE_SYSTEM_EXTENSIONS).
1805 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
1806 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
1807 Patch from Gisle Vanem.
1808 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
1809 They apparently require a set of annotations that we aren't
1810 currently using, and they create false positives in our pthreads
1811 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
1813 o Minor bugfixes (directory authority):
1814 - Die with a more useful error when the operator forgets to place
1815 the authority_signing_key file into the keys directory. This
1816 avoids an uninformative assert & traceback about having an invalid
1817 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
1818 - When allowing private addresses, mark Exits that only exit to
1819 private locations as such. Fixes bug 20064; bugfix
1822 o Minor bugfixes (documentation):
1823 - Document the default PathsNeededToBuildCircuits value that's used
1824 by clients when the directory authorities don't set
1825 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
1826 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
1827 - Fix manual for the User option: it takes a username, not a UID.
1828 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
1831 o Minor bugfixes (hidden services):
1832 - Stop logging intro point details to the client log on certain
1833 error conditions. Fixed as part of bug 20012; bugfix on
1834 0.2.4.8-alpha. Patch by teor.
1836 o Minor bugfixes (IPv6, testing):
1837 - Check for IPv6 correctly on Linux when running test networks.
1838 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
1840 o Minor bugfixes (Linux seccomp2 sandbox):
1841 - Add permission to run the sched_yield() and sigaltstack() system
1842 calls, in order to support versions of Tor compiled with asan or
1843 ubsan code that use these calls. Now "sandbox 1" and
1844 "--enable-expensive-hardening" should be compatible on more
1845 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
1847 o Minor bugfixes (logging):
1848 - When logging a message from the BUG() macro, be explicit about
1849 what we were asserting. Previously we were confusing what we were
1850 asserting with what the bug was. Fixes bug 20093; bugfix
1852 - When we are unable to remove the bw_accounting file, do not warn
1853 if the reason we couldn't remove it was that it didn't exist.
1854 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
1856 o Minor bugfixes (option parsing):
1857 - Count unix sockets when counting client listeners (SOCKS, Trans,
1858 NATD, and DNS). This has no user-visible behaviour changes: these
1859 options are set once, and never read. Required for correct
1860 behaviour in ticket 17178. Fixes bug 19677; bugfix on
1861 0.2.6.3-alpha. Patch by teor.
1863 o Minor bugfixes (options):
1864 - Check the consistency of UseEntryGuards and EntryNodes more
1865 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
1867 - Stop changing the configured value of UseEntryGuards on
1868 authorities and Tor2web clients. Fixes bug 20074; bugfix on
1869 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
1872 o Minor bugfixes (Tor2web):
1873 - Prevent Tor2web clients running hidden services, these services
1874 are not anonymous due to the one-hop client paths. Fixes bug
1875 19678. Patch by teor.
1877 o Minor bugfixes (unit tests):
1878 - Fix a shared-random unit test that was failing on big endian
1879 architectures due to internal representation of a integer copied
1880 to a buffer. The test is changed to take a full 32 bytes of data
1881 and use the output of a python script that make the COMMIT and
1882 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
1884 - The tor_tls_server_info_callback unit test no longer crashes when
1885 debug-level logging is turned on. Fixes bug 20041; bugfix
1889 Changes in version 0.2.8.8 - 2016-09-23
1890 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
1891 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
1892 who select public relays as their bridges.
1894 o Major bugfixes (crash):
1895 - Fix a complicated crash bug that could affect Tor clients
1896 configured to use bridges when replacing a networkstatus consensus
1897 in which one of their bridges was mentioned. OpenBSD users saw
1898 more crashes here, but all platforms were potentially affected.
1899 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
1901 o Major bugfixes (relay, OOM handler):
1902 - Fix a timing-dependent assertion failure that could occur when we
1903 tried to flush from a circuit after having freed its cells because
1904 of an out-of-memory condition. Fixes bug 20203; bugfix on
1905 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
1908 o Minor feature (fallback directories):
1909 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
1910 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
1911 2016. Closes ticket 20190; patch by teor.
1913 o Minor features (geoip):
1914 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
1918 Changes in version 0.2.9.2-alpha - 2016-08-24
1919 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
1920 several new features and bugfixes. It also includes an important
1921 authority update and an important bugfix from 0.2.8.7. Everyone who
1922 sets the ReachableAddresses option, and all bridges, are strongly
1923 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
1925 o Directory authority changes (also in 0.2.8.7):
1926 - The "Tonga" bridge authority has been retired; the new bridge
1927 authority is "Bifroest". Closes tickets 19728 and 19690.
1929 o Major bugfixes (client, security, also in 0.2.8.7):
1930 - Only use the ReachableAddresses option to restrict the first hop
1931 in a path. In earlier versions of 0.2.8.x, it would apply to
1932 every hop in the path, with a possible degradation in anonymity
1933 for anyone using an uncommon ReachableAddress setting. Fixes bug
1934 19973; bugfix on 0.2.8.2-alpha.
1936 o Major features (user interface):
1937 - Tor now supports the ability to declare options deprecated, so
1938 that we can recommend that people stop using them. Previously,
1939 this was done in an ad-hoc way. Closes ticket 19820.
1941 o Major bugfixes (directory downloads):
1942 - Avoid resetting download status for consensuses hourly, since we
1943 already have another, smarter retry mechanism. Fixes bug 8625;
1944 bugfix on 0.2.0.9-alpha.
1946 o Minor features (config):
1947 - Warn users when descriptor and port addresses are inconsistent.
1948 Mitigates bug 13953; patch by teor.
1950 o Minor features (geoip):
1951 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
1954 o Minor features (user interface):
1955 - There is a new --list-deprecated-options command-line option to
1956 list all of the deprecated options. Implemented as part of
1959 o Minor bugfixes (code style):
1960 - Fix an integer signedness conversion issue in the case conversion
1961 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
1963 o Minor bugfixes (compilation):
1964 - Build correctly on versions of libevent2 without support for
1965 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
1967 - Fix a compilation warning on GCC versions before 4.6. Our
1968 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
1969 when it is also required as an argument to the compiler pragma.
1970 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
1972 o Minor bugfixes (compilation, also in 0.2.8.7):
1973 - Remove an inappropriate "inline" in tortls.c that was causing
1974 warnings on older versions of GCC. Fixes bug 19903; bugfix
1977 o Minor bugfixes (fallback directories, also in 0.2.8.7):
1978 - Avoid logging a NULL string pointer when loading fallback
1979 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
1980 and 0.2.8.1-alpha. Report and patch by "rubiate".
1982 o Minor bugfixes (logging):
1983 - Log a more accurate message when we fail to dump a microdescriptor.
1984 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
1986 o Minor bugfixes (memory leak):
1987 - Fix a series of slow memory leaks related to parsing torrc files
1988 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
1990 o Deprecated features:
1991 - A number of DNS-cache-related sub-options for client ports are now
1992 deprecated for security reasons, and may be removed in a future
1993 version of Tor. (We believe that client-side DNS cacheing is a bad
1994 idea for anonymity, and you should not turn it on.) The options
1995 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
1996 UseIPv4Cache, and UseIPv6Cache.
1997 - A number of options are deprecated for security reasons, and may
1998 be removed in a future version of Tor. The options are:
1999 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
2000 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
2001 CloseHSClientCircuitsImmediatelyOnTimeout,
2002 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
2003 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
2004 UseNTorHandshake, and WarnUnsafeSocks.
2005 - The *ListenAddress options are now deprecated as unnecessary: the
2006 corresponding *Port options should be used instead. These options
2007 may someday be removed. The affected options are:
2008 ControlListenAddress, DNSListenAddress, DirListenAddress,
2009 NATDListenAddress, ORListenAddress, SocksListenAddress,
2010 and TransListenAddress.
2013 - Correct the IPv6 syntax in our documentation for the
2014 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
2017 - We no longer include the (dead, deprecated) bufferevent code in
2018 Tor. Closes ticket 19450. Based on a patch from U+039b.
2021 Changes in version 0.2.8.7 - 2016-08-24
2022 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
2023 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
2024 who sets the ReachableAddresses option, and all bridges, are strongly
2025 encouraged to upgrade.
2027 o Directory authority changes:
2028 - The "Tonga" bridge authority has been retired; the new bridge
2029 authority is "Bifroest". Closes tickets 19728 and 19690.
2031 o Major bugfixes (client, security):
2032 - Only use the ReachableAddresses option to restrict the first hop
2033 in a path. In earlier versions of 0.2.8.x, it would apply to
2034 every hop in the path, with a possible degradation in anonymity
2035 for anyone using an uncommon ReachableAddress setting. Fixes bug
2036 19973; bugfix on 0.2.8.2-alpha.
2038 o Minor features (geoip):
2039 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
2042 o Minor bugfixes (compilation):
2043 - Remove an inappropriate "inline" in tortls.c that was causing
2044 warnings on older versions of GCC. Fixes bug 19903; bugfix
2047 o Minor bugfixes (fallback directories):
2048 - Avoid logging a NULL string pointer when loading fallback
2049 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
2050 and 0.2.8.1-alpha. Report and patch by "rubiate".
2053 Changes in version 0.2.9.1-alpha - 2016-08-08
2054 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
2055 series. It improves our support for hardened builds and compiler
2056 warnings, deploys some critical infrastructure for improvements to
2057 hidden services, includes a new timing backend that we hope to use for
2058 better support for traffic padding, makes it easier for programmers to
2059 log unexpected events, and contains other small improvements to
2060 security, correctness, and performance.
2062 Below are the changes since 0.2.8.6.
2064 o New system requirements:
2065 - Tor now requires Libevent version 2.0.10-stable or later. Older
2066 versions of Libevent have less efficient backends for several
2067 platforms, and lack the DNS code that we use for our server-side
2068 DNS support. This implements ticket 19554.
2069 - Tor now requires zlib version 1.2 or later, for security,
2070 efficiency, and (eventually) gzip support. (Back when we started,
2071 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
2072 released in 2003. We recommend the latest version.)
2074 o Major features (build, hardening):
2075 - Tor now builds with -ftrapv by default on compilers that support
2076 it. This option detects signed integer overflow (which C forbids),
2077 and turns it into a hard-failure. We do not apply this option to
2078 code that needs to run in constant time to avoid side-channels;
2079 instead, we use -fwrapv in that code. Closes ticket 17983.
2080 - When --enable-expensive-hardening is selected, stop applying the
2081 clang/gcc sanitizers to code that needs to run in constant time.
2082 Although we are aware of no introduced side-channels, we are not
2083 able to prove that there are none. Related to ticket 17983.
2085 o Major features (compilation):
2086 - Our big list of extra GCC warnings is now enabled by default when
2087 building with GCC (or with anything like Clang that claims to be
2088 GCC-compatible). To make all warnings into fatal compilation
2089 errors, pass --enable-fatal-warnings to configure. Closes
2091 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
2092 turn on C and POSIX extensions. (Previously, we attempted to do
2093 this on an ad hoc basis.) Closes ticket 19139.
2095 o Major features (directory authorities, hidden services):
2096 - Directory authorities can now perform the shared randomness
2097 protocol specified by proposal 250. Using this protocol, directory
2098 authorities generate a global fresh random value every day. In the
2099 future, this value will be used by hidden services to select
2100 HSDirs. This release implements the directory authority feature;
2101 the hidden service side will be implemented in the future as part
2102 of proposal 224. Resolves ticket 16943; implements proposal 250.
2104 o Major features (downloading, random exponential backoff):
2105 - When we fail to download an object from a directory service, wait
2106 for an (exponentially increasing) randomized amount of time before
2107 retrying, rather than a fixed interval as we did before. This
2108 prevents a group of Tor instances from becoming too synchronized,
2109 or a single Tor instance from becoming too predictable, in its
2110 download schedule. Closes ticket 15942.
2112 o Major bugfixes (exit policies):
2113 - Avoid disclosing exit outbound bind addresses, configured port
2114 bind addresses, and local interface addresses in relay descriptors
2115 by default under ExitPolicyRejectPrivate. Instead, only reject
2116 these (otherwise unlisted) addresses if
2117 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
2118 0.2.7.2-alpha. Patch by teor.
2120 o Major bugfixes (hidden service client):
2121 - Allow Tor clients with appropriate controllers to work with
2122 FetchHidServDescriptors set to 0. Previously, this option also
2123 disabled descriptor cache lookup, thus breaking hidden services
2124 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
2126 o Minor features (build, hardening):
2127 - Detect and work around a libclang_rt problem that would prevent
2128 clang from finding __mulodi4() on some 32-bit platforms, and thus
2129 keep -ftrapv from linking on those systems. Closes ticket 19079.
2130 - When building on a system without runtime support for the runtime
2131 hardening options, try to log a useful warning at configuration
2132 time, rather than an incomprehensible warning at link time. If
2133 expensive hardening was requested, this warning becomes an error.
2134 Closes ticket 18895.
2136 o Minor features (code safety):
2137 - In our integer-parsing functions, ensure that maxiumum value we
2138 give is no smaller than the minimum value. Closes ticket 19063;
2141 o Minor features (controller):
2142 - Implement new GETINFO queries for all downloads that use
2143 download_status_t to schedule retries. This allows controllers to
2144 examine the schedule for pending downloads. Closes ticket 19323.
2145 - Allow controllers to configure basic client authorization on
2146 hidden services when they create them with the ADD_ONION control
2147 command. Implements ticket 15588. Patch by "special".
2148 - Fire a STATUS_SERVER controller event whenever the hibernation
2149 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
2151 o Minor features (directory authority):
2152 - Directory authorities now only give the Guard flag to a relay if
2153 they are also giving it the Stable flag. This change allows us to
2154 simplify path selection for clients. It should have minimal effect
2155 in practice, since >99% of Guards already have the Stable flag.
2156 Implements ticket 18624.
2157 - Directory authorities now write their v3-status-votes file out to
2158 disk earlier in the consensus process, so we have a record of the
2159 votes even if we abort the consensus process. Resolves
2162 o Minor features (hidden service):
2163 - Stop being so strict about the payload length of "rendezvous1"
2164 cells. We used to be locked in to the "TAP" handshake length, and
2165 now we can handle better handshakes like "ntor". Resolves
2168 o Minor features (infrastructure, time):
2169 - Tor now uses the operating system's monotonic timers (where
2170 available) for internal fine-grained timing. Previously we would
2171 look at the system clock, and then attempt to compensate for the
2172 clock running backwards. Closes ticket 18908.
2173 - Tor now includes an improved timer backend, so that we can
2174 efficiently support tens or hundreds of thousands of concurrent
2175 timers, as will be needed for some of our planned anti-traffic-
2176 analysis work. This code is based on William Ahern's "timeout.c"
2177 project, which implements a "tickless hierarchical timing wheel".
2178 Closes ticket 18365.
2180 o Minor features (logging):
2181 - Provide a more useful warning message when configured with an
2182 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
2183 - When dumping unparseable router descriptors, optionally store them
2184 in separate files, named by digest, up to a configurable size
2185 limit. You can change the size limit by setting the
2186 MaxUnparseableDescSizeToLog option, and disable this feature by
2187 setting that option to 0. Closes ticket 18322.
2188 - Add a set of macros to check nonfatal assertions, for internal
2189 use. Migrating more of our checks to these should help us avoid
2190 needless crash bugs. Closes ticket 18613.
2192 o Minor features (performance):
2193 - Changer the "optimistic data" extension from "off by default" to
2194 "on by default". The default was ordinarily overridden by a
2195 consensus option, but when clients were bootstrapping for the
2196 first time, they would not have a consensus to get the option
2197 from. Changing this default When fetching a consensus for the
2198 first time, use optimistic data. This saves a round-trip during
2199 startup. Closes ticket 18815.
2201 o Minor features (relay, usability):
2202 - When the directory authorities refuse a bad relay's descriptor,
2203 encourage the relay operator to contact us. Many relay operators
2204 won't notice this line in their logs, but it's a win if even a few
2205 learn why we don't like what their relay was doing. Resolves
2208 o Minor features (testing):
2209 - Let backtrace tests work correctly under AddressSanitizer. Fixes
2210 part of bug 18934; bugfix on 0.2.5.2-alpha.
2211 - Move the test-network.sh script to chutney, and modify tor's test-
2212 network.sh to call the (newer) chutney version when available.
2213 Resolves ticket 19116. Patch by teor.
2214 - Use the lcov convention for marking lines as unreachable, so that
2215 we don't count them when we're generating test coverage data.
2216 Update our coverage tools to understand this convention. Closes
2219 o Minor bugfixes (bootstrap):
2220 - Remember the directory we fetched the consensus or previous
2221 certificates from, and use it to fetch future authority
2222 certificates. This change improves bootstrapping performance.
2223 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
2225 o Minor bugfixes (build):
2226 - The test-stem and test-network makefile targets now depend only on
2227 the tor binary that they are testing. Previously, they depended on
2228 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
2229 patch from "cypherpunks".
2231 o Minor bugfixes (circuits):
2232 - Make sure extend_info_from_router() is only called on servers.
2233 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
2235 o Minor bugfixes (compilation):
2236 - When building with Clang, use a full set of GCC warnings.
2237 (Previously, we included only a subset, because of the way we
2238 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
2240 o Minor bugfixes (directory authority):
2241 - Authorities now sort the "package" lines in their votes, for ease
2242 of debugging. (They are already sorted in consensus documents.)
2243 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
2244 - When parsing a detached signature, make sure we use the length of
2245 the digest algorithm instead of an hardcoded DIGEST256_LEN in
2246 order to avoid comparing bytes out-of-bounds with a smaller digest
2247 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
2249 o Minor bugfixes (documentation):
2250 - Document the --passphrase-fd option in the tor manpage. Fixes bug
2251 19504; bugfix on 0.2.7.3-rc.
2252 - Fix the description of the --passphrase-fd option in the
2253 tor-gencert manpage. The option is used to pass the number of a
2254 file descriptor to read the passphrase from, not to read the file
2255 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
2257 o Minor bugfixes (ephemeral hidden service):
2258 - When deleting an ephemeral hidden service, close its intro points
2259 even if they are not completely open. Fixes bug 18604; bugfix
2262 o Minor bugfixes (guard selection):
2263 - Use a single entry guard even if the NumEntryGuards consensus
2264 parameter is not provided. Fixes bug 17688; bugfix
2266 - Don't mark guards as unreachable if connection_connect() fails.
2267 That function fails for local reasons, so it shouldn't reveal
2268 anything about the status of the guard. Fixes bug 14334; bugfix
2271 o Minor bugfixes (hidden service client):
2272 - Increase the minimum number of internal circuits we preemptively
2273 build from 2 to 3, so a circuit is available when a client
2274 connects to another onion service. Fixes bug 13239; bugfix
2277 o Minor bugfixes (logging):
2278 - When logging a directory ownership mismatch, log the owning
2279 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
2281 o Minor bugfixes (memory leaks):
2282 - Fix a small, uncommon memory leak that could occur when reading a
2283 truncated ed25519 key file. Fixes bug 18956; bugfix
2286 o Minor bugfixes (testing):
2287 - Allow clients to retry HSDirs much faster in test networks. Fixes
2288 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
2289 - Disable ASAN's detection of segmentation faults while running
2290 test_bt.sh, so that we can make sure that our own backtrace
2291 generation code works. Fixes another aspect of bug 18934; bugfix
2292 on 0.2.5.2-alpha. Patch from "cypherpunks".
2293 - Fix the test-network-all target on out-of-tree builds by using the
2294 correct path to the test driver script. Fixes bug 19421; bugfix
2297 o Minor bugfixes (time):
2298 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
2299 bugfix on all released tor versions.
2300 - When computing the difference between two times in milliseconds,
2301 we now round to the nearest millisecond correctly. Previously, we
2302 could sometimes round in the wrong direction. Fixes bug 19428;
2303 bugfix on 0.2.2.2-alpha.
2305 o Minor bugfixes (user interface):
2306 - Display a more accurate number of suppressed messages in the log
2307 rate-limiter. Previously, there was a potential integer overflow
2308 in the counter. Now, if the number of messages hits a maximum, the
2309 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
2311 - Fix a typo in the passphrase prompt for the ed25519 identity key.
2312 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
2314 o Code simplification and refactoring:
2315 - Remove redundant declarations of the MIN macro. Closes
2317 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
2318 Closes ticket 18462; patch from "icanhasaccount".
2319 - Split the 600-line directory_handle_command_get function into
2320 separate functions for different URL types. Closes ticket 16698.
2323 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
2324 ticket 19153. Patch from "U+039b".
2327 - Remove support for "GET /tor/bytes.txt" DirPort request, and
2328 "GETINFO dir-usage" controller request, which were only available
2329 via a compile-time option in Tor anyway. Feature was added in
2330 0.2.2.1-alpha. Resolves ticket 19035.
2331 - There is no longer a compile-time option to disable support for
2332 TransPort. (If you don't want TransPort; just don't use it.) Patch
2333 from "U+039b". Closes ticket 19449.
2336 - Run more workqueue tests as part of "make check". These had
2337 previously been implemented, but you needed to know special
2338 command-line options to enable them.
2339 - We now have unit tests for our code to reject zlib "compression
2340 bombs". (Fortunately, the code works fine.)
2343 Changes in version 0.2.8.6 - 2016-08-02
2345 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
2347 The Tor 0.2.8 series improves client bootstrapping performance,
2348 completes the authority-side implementation of improved identity
2349 keys for relays, and includes numerous bugfixes and performance
2350 improvements throughout the program. This release continues to
2351 improve the coverage of Tor's test suite. For a full list of
2352 changes since Tor 0.2.7, see the ReleaseNotes file.
2354 Changes since 0.2.8.5-rc:
2356 o Minor features (geoip):
2357 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
2360 o Minor bugfixes (compilation):
2361 - Fix a compilation warning in the unit tests on systems where char
2362 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
2364 o Minor bugfixes (fallback directories):
2365 - Remove 1 fallback that was on the hardcoded list, then opted-out,
2366 leaving 89 of the 100 fallbacks originally introduced in Tor
2367 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
2369 o Minor bugfixes (Linux seccomp2 sandbox):
2370 - Allow more syscalls when running with "Sandbox 1" enabled:
2371 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
2372 some systems, these are required for Tor to start. Fixes bug
2373 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
2374 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
2375 so that get_interface_address6_via_udp_socket_hack() can work.
2376 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
2379 Changes in version 0.2.8.5-rc - 2016-07-07
2380 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
2381 series. If we find no new bugs or regressions here, the first stable
2382 0.2.8 release will be identical to it. It has a few small bugfixes
2383 against previous versions.
2385 o Directory authority changes:
2386 - Urras is no longer a directory authority. Closes ticket 19271.
2388 o Major bugfixes (heartbeat):
2389 - Fix a regression that would crash Tor when the periodic
2390 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
2391 0.2.8.1-alpha. Reported by "kubaku".
2393 o Minor features (build):
2394 - Tor now again builds with the recent OpenSSL 1.1 development
2395 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
2396 - When building manual pages, set the timezone to "UTC", so that the
2397 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
2398 Patch from intrigeri.
2400 o Minor bugfixes (fallback directory selection):
2401 - Avoid errors during fallback selection if there are no eligible
2402 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
2405 o Minor bugfixes (IPv6, microdescriptors):
2406 - Don't check node addresses when we only have a routerstatus. This
2407 allows IPv6-only clients to bootstrap by fetching microdescriptors
2408 from fallback directory mirrors. (The microdescriptor consensus
2409 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
2412 o Minor bugfixes (logging):
2413 - Reduce pointlessly verbose log messages when directory servers
2414 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
2415 0.2.8.1-alpha. Patch by teor.
2416 - When a fallback directory changes its fingerprint from the hard-
2417 coded fingerprint, log a less severe, more explanatory log
2418 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
2420 o Minor bugfixes (Linux seccomp2 sandboxing):
2421 - Allow statistics to be written to disk when "Sandbox 1" is
2422 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
2423 0.2.6.1-alpha respectively.
2425 o Minor bugfixes (user interface):
2426 - Remove a warning message "Service [scrubbed] not found after
2427 descriptor upload". This message appears when one uses HSPOST
2428 control command to upload a service descriptor. Since there is
2429 only a descriptor and no service, showing this message is
2430 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
2432 o Fallback directory list:
2433 - Add a comment to the generated fallback directory list that
2434 explains how to comment out unsuitable fallbacks in a way that's
2435 compatible with the stem fallback parser.
2436 - Update fallback whitelist and blacklist based on relay operator
2437 emails. Blacklist unsuitable (non-working, over-volatile)
2438 fallbacks. Resolves ticket 19071. Patch by teor.
2439 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
2440 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
2441 ticket 19071; patch by teor.
2444 Changes in version 0.2.8.4-rc - 2016-06-15
2445 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
2446 If we find no new bugs or regressions here, the first stable 0.2.8
2447 release will be identical to it. It has a few small bugfixes against
2450 o Major bugfixes (user interface):
2451 - Correctly give a warning in the cases where a relay is specified
2452 by nickname, and one such relay is found, but it is not officially
2453 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
2455 o Minor features (build):
2456 - Tor now builds once again with the recent OpenSSL 1.1 development
2457 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
2459 o Minor features (geoip):
2460 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
2463 o Minor bugfixes (compilation):
2464 - Cause the unit tests to compile correctly on mingw64 versions that
2465 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
2467 o Minor bugfixes (downloading):
2468 - Predict more correctly whether we'll be downloading over HTTP when
2469 we determine the maximum length of a URL. This should avoid a
2470 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
2474 Changes in version 0.2.8.3-alpha - 2016-05-26
2475 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
2476 the course of the 0.2.8 development cycle. It improves the behavior of
2477 directory clients, fixes several crash bugs, fixes a gap in compiler
2478 hardening, and allows the full integration test suite to run on
2481 o Major bugfixes (security, client, DNS proxy):
2482 - Stop a crash that could occur when a client running with DNSPort
2483 received a query with multiple address types, and the first
2484 address type was not supported. Found and fixed by Scott Dial.
2485 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
2487 o Major bugfixes (security, compilation):
2488 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
2489 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
2490 cause a compiler warning, thereby making other checks fail, and
2491 needlessly disabling compiler-hardening support. Fixes one case of
2492 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
2494 o Major bugfixes (security, directory authorities):
2495 - Fix a crash and out-of-bounds write during authority voting, when
2496 the list of relays includes duplicate ed25519 identity keys. Fixes
2497 bug 19032; bugfix on 0.2.8.2-alpha.
2499 o Major bugfixes (client, bootstrapping):
2500 - Check if bootstrap consensus downloads are still needed when the
2501 linked connection attaches. This prevents tor making unnecessary
2502 begindir-style connections, which are the only directory
2503 connections tor clients make since the fix for 18483 was merged.
2504 - Fix some edge cases where consensus download connections may not
2505 have been closed, even though they were not needed. Related to fix
2507 - Make relays retry consensus downloads the correct number of times,
2508 rather than the more aggressive client retry count. Fixes part of
2510 - Stop downloading consensuses when we have a consensus, even if we
2511 don't have all the certificates for it yet. Fixes bug 18809;
2512 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
2514 o Major bugfixes (directory mirrors):
2515 - Decide whether to advertise begindir support in the the same way
2516 we decide whether to advertise our DirPort. Allowing these
2517 decisions to become out-of-sync led to surprising behavior like
2518 advertising begindir support when hibernation made us not
2519 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
2522 o Major bugfixes (IPv6 bridges, client):
2523 - Actually use IPv6 addresses when selecting directory addresses for
2524 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
2527 o Major bugfixes (key management):
2528 - If OpenSSL fails to generate an RSA key, do not retain a dangling
2529 pointer to the previous (uninitialized) key value. The impact here
2530 should be limited to a difficult-to-trigger crash, if OpenSSL is
2531 running an engine that makes key generation failures possible, or
2532 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
2533 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
2536 o Major bugfixes (testing):
2537 - Fix a bug that would block 'make test-network-all' on systems where
2538 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
2539 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
2540 bugfix on 0.2.8.1-alpha.
2542 o Minor features (clients):
2543 - Make clients, onion services, and bridge relays always use an
2544 encrypted begindir connection for directory requests. Resolves
2545 ticket 18483. Patch by "teor".
2547 o Minor features (fallback directory mirrors):
2548 - Give each fallback the same weight for client selection; restrict
2549 fallbacks to one per operator; report fallback directory detail
2550 changes when rebuilding list; add new fallback directory mirrors
2551 to the whitelist; and many other minor simplifications and fixes.
2552 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
2553 0.2.8.1-alpha; patch by "teor".
2554 - Replace the 21 fallbacks generated in January 2016 and included in
2555 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
2556 2016. Closes task 17158; patch by "teor".
2558 o Minor features (geoip):
2559 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
2562 o Minor bugfixes (assert, portability):
2563 - Fix an assertion failure in memarea.c on systems where "long" is
2564 shorter than the size of a pointer. Fixes bug 18716; bugfix
2567 o Minor bugfixes (bootstrap):
2568 - Consistently use the consensus download schedule for authority
2569 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
2571 o Minor bugfixes (build):
2572 - Remove a pair of redundant AM_CONDITIONAL declarations from
2573 configure.ac. Fixes one final case of bug 17744; bugfix
2575 - Resolve warnings when building on systems that are concerned with
2576 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
2578 - When libscrypt.h is found, but no libscrypt library can be linked,
2579 treat libscrypt as absent. Fixes bug 19161; bugfix
2582 o Minor bugfixes (client):
2583 - Turn all TestingClientBootstrap* into non-testing torrc options.
2584 This changes simply renames them by removing "Testing" in front of
2585 them and they do not require TestingTorNetwork to be enabled
2586 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
2587 - Make directory node selection more reliable, mainly for IPv6-only
2588 clients and clients with few reachable addresses. Fixes bug 18929;
2589 bugfix on 0.2.8.1-alpha. Patch by "teor".
2591 o Minor bugfixes (controller, microdescriptors):
2592 - Make GETINFO dir/status-vote/current/consensus conform to the
2593 control specification by returning "551 Could not open cached
2594 consensus..." when not caching consensuses. Fixes bug 18920;
2595 bugfix on 0.2.2.6-alpha.
2597 o Minor bugfixes (crypto, portability):
2598 - The SHA3 and SHAKE routines now produce the correct output on Big
2599 Endian systems. No code calls either algorithm yet, so this is
2600 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
2601 - Tor now builds again with the recent OpenSSL 1.1 development
2602 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
2605 o Minor bugfixes (directories):
2606 - When fetching extrainfo documents, compare their SHA256 digests
2607 and Ed25519 signing key certificates with the routerinfo that led
2608 us to fetch them, rather than with the most recent routerinfo.
2609 Otherwise we generate many spurious warnings about mismatches.
2610 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
2612 o Minor bugfixes (logging):
2613 - When we can't generate a signing key because OfflineMasterKey is
2614 set, do not imply that we should have been able to load it. Fixes
2615 bug 18133; bugfix on 0.2.7.2-alpha.
2616 - Stop periodic_event_dispatch() from blasting twelve lines per
2617 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
2618 - When rejecting a misformed INTRODUCE2 cell, only log at
2619 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
2621 o Minor bugfixes (pluggable transports):
2622 - Avoid reporting a spurious error when we decide that we don't need
2623 to terminate a pluggable transport because it has already exited.
2624 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
2626 o Minor bugfixes (pointer arithmetic):
2627 - Fix a bug in memarea_alloc() that could have resulted in remote
2628 heap write access, if Tor had ever passed an unchecked size to
2629 memarea_alloc(). Fortunately, all the sizes we pass to
2630 memarea_alloc() are pre-checked to be less than 128 kilobytes.
2631 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
2634 o Minor bugfixes (relays):
2635 - Consider more config options when relays decide whether to
2636 regenerate their descriptor. Fixes more of bug 12538; bugfix
2638 - Resolve some edge cases where we might launch an ORPort
2639 reachability check even when DisableNetwork is set. Noticed while
2640 fixing bug 18616; bugfix on 0.2.3.9-alpha.
2642 o Minor bugfixes (statistics):
2643 - We now include consensus downloads via IPv6 in our directory-
2644 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
2646 o Minor bugfixes (testing):
2647 - Allow directories in small networks to bootstrap by skipping
2648 DirPort checks when the consensus has no exits. Fixes bug 19003;
2649 bugfix on 0.2.8.1-alpha. Patch by teor.
2650 - Fix a small memory leak that would occur when the
2651 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
2652 bugfix on 0.2.5.2-alpha.
2654 o Minor bugfixes (time handling):
2655 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
2656 field. Otherwise, our unit tests crash on Windows. Fixes bug
2657 18977; bugfix on 0.2.2.25-alpha.
2660 - Document the contents of the 'datadir/keys' subdirectory in the
2661 manual page. Closes ticket 17621.
2662 - Stop recommending use of nicknames to identify relays in our
2663 MapAddress documentation. Closes ticket 18312.
2666 Changes in version 0.2.8.2-alpha - 2016-03-28
2667 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
2668 bugs in earlier versions of Tor, including some that prevented
2669 authorities using Tor 0.2.7.x from running correctly. IPv6 and
2670 directory support should also be much improved.
2672 o New system requirements:
2673 - Tor no longer supports versions of OpenSSL with a broken
2674 implementation of counter mode. (This bug was present in OpenSSL
2675 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
2676 longer runs with, these versions.
2677 - Tor no longer attempts to support platforms where the "time_t"
2678 type is unsigned. (To the best of our knowledge, only OpenVMS does
2679 this, and Tor has never actually built on OpenVMS.) Closes
2681 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
2682 later (released in 2008 and 2009 respectively). If you are
2683 building Tor from the git repository instead of from the source
2684 distribution, and your tools are older than this, you will need to
2685 upgrade. Closes ticket 17732.
2687 o Major bugfixes (security, pointers):
2688 - Avoid a difficult-to-trigger heap corruption attack when extending
2689 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
2690 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
2691 Reported by Guido Vranken.
2693 o Major bugfixes (bridges, pluggable transports):
2694 - Modify the check for OR connections to private addresses. Allow
2695 bridges on private addresses, including pluggable transports that
2696 ignore the (potentially private) address in the bridge line. Fixes
2697 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
2699 o Major bugfixes (compilation):
2700 - Repair hardened builds under the clang compiler. Previously, our
2701 use of _FORTIFY_SOURCE would conflict with clang's address
2702 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
2704 o Major bugfixes (crash on shutdown):
2705 - Correctly handle detaching circuits from muxes when shutting down.
2706 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
2707 - Fix an assert-on-exit bug related to counting memory usage in
2708 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
2710 o Major bugfixes (crash on startup):
2711 - Fix a segfault during startup: If a Unix domain socket was
2712 configured as listener (such as a ControlSocket or a SocksPort
2713 "unix:" socket), and tor was started as root but not configured to
2714 switch to another user, tor would segfault while trying to string
2715 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
2718 o Major bugfixes (dns proxy mode, crash):
2719 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
2720 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
2722 o Major bugfixes (relays, bridge clients):
2723 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
2724 bridge clients use the address configured in the bridge line.
2725 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
2728 o Major bugfixes (voting):
2729 - Actually enable support for authorities to match routers by their
2730 Ed25519 identities. Previously, the code had been written, but
2731 some debugging code that had accidentally been left in the
2732 codebase made it stay turned off. Fixes bug 17702; bugfix
2734 - When collating votes by Ed25519 identities, authorities now
2735 include a "NoEdConsensus" flag if the ed25519 value (or lack
2736 thereof) for a server does not reflect the majority consensus.
2737 Related to bug 17668; bugfix on 0.2.7.2-alpha.
2738 - When generating a vote with keypinning disabled, never include two
2739 entries for the same ed25519 identity. This bug was causing
2740 authorities to generate votes that they could not parse when a
2741 router violated key pinning by changing its RSA identity but
2742 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
2743 18318. Bugfix on 0.2.7.2-alpha.
2745 o Minor features (security, win32):
2746 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
2747 attack. Fixes bug 18123; bugfix on all tor versions. Patch
2750 o Minor features (bug-resistance):
2751 - Make Tor survive errors involving connections without a
2752 corresponding event object. Previously we'd fail with an
2753 assertion; now we produce a log message. Related to bug 16248.
2755 o Minor features (build):
2756 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
2757 as having possible IPFW support. Closes ticket 18448. Patch from
2760 o Minor features (code hardening):
2761 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
2762 level code, to harden against accidental failures to NUL-
2763 terminate. Part of ticket 17852. Patch from jsturgix. Found
2766 o Minor features (crypto):
2767 - Validate the hard-coded Diffie-Hellman parameters and ensure that
2768 p is a safe prime, and g is a suitable generator. Closes
2771 o Minor features (geoip):
2772 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
2775 o Minor features (hidden service directory):
2776 - Streamline relay-side hsdir handling: when relays consider whether
2777 to accept an uploaded hidden service descriptor, they no longer
2778 check whether they are one of the relays in the network that is
2779 "supposed" to handle that descriptor. Implements ticket 18332.
2781 o Minor features (IPv6):
2782 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
2783 to 1, tor prefers IPv6 directory addresses.
2784 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
2785 avoids using IPv4 for client OR and directory connections.
2786 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
2787 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
2788 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
2790 o Minor features (linux seccomp2 sandbox):
2791 - Reject attempts to change our Address with "Sandbox 1" enabled.
2792 Changing Address with Sandbox turned on would never actually work,
2793 but previously it would fail in strange and confusing ways. Found
2796 o Minor features (robustness):
2797 - Exit immediately with an error message if the code attempts to use
2798 Libevent without having initialized it. This should resolve some
2799 frequently-made mistakes in our unit tests. Closes ticket 18241.
2801 o Minor features (unix domain sockets):
2802 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
2803 Unix domain sockets without checking the permissions on the parent
2804 directory. (Tor checks permissions by default because some
2805 operating systems only check permissions on the parent directory.
2806 However, some operating systems do look at permissions on the
2807 socket, and tor's default check is unneeded.) Closes ticket 18458.
2810 o Minor bugfixes (exit policies, security):
2811 - Refresh an exit relay's exit policy when interface addresses
2812 change. Previously, tor only refreshed the exit policy when the
2813 configured external address changed. Fixes bug 18208; bugfix on
2814 0.2.7.3-rc. Patch by teor.
2816 o Minor bugfixes (security, hidden services):
2817 - Prevent hidden services connecting to client-supplied rendezvous
2818 addresses that are reserved as internal or multicast. Fixes bug
2819 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
2821 o Minor bugfixes (build):
2822 - Do not link the unit tests against both the testing and non-
2823 testing versions of the static libraries. Fixes bug 18490; bugfix
2825 - Avoid spurious failures from configure files related to calling
2826 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
2827 0.2.0.1-alpha. Patch from "cypherpunks".
2828 - Silence spurious clang-scan warnings in the ed25519_donna code by
2829 explicitly initializing some objects. Fixes bug 18384; bugfix on
2830 0.2.7.2-alpha. Patch by teor.
2832 o Minor bugfixes (client, bootstrap):
2833 - Count receipt of new microdescriptors as progress towards
2834 bootstrapping. Previously, with EntryNodes set, Tor might not
2835 successfully repopulate the guard set on bootstrapping. Fixes bug
2836 16825; bugfix on 0.2.3.1-alpha.
2838 o Minor bugfixes (code correctness):
2839 - Update to the latest version of Trunnel, which tries harder to
2840 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
2841 by clang address sanitizer. Fixes bug 18373; bugfix
2844 o Minor bugfixes (configuration):
2845 - Fix a tiny memory leak when parsing a port configuration ending in
2846 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
2848 o Minor bugfixes (containers):
2849 - If we somehow attempt to construct a heap with more than
2850 1073741822 elements, avoid an integer overflow when maintaining
2851 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
2853 o Minor bugfixes (correctness):
2854 - Fix a bad memory handling bug that would occur if we had queued a
2855 cell on a channel's incoming queue. Fortunately, we can't actually
2856 queue a cell like that as our code is constructed today, but it's
2857 best to avoid this kind of error, even if there isn't any code
2858 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
2860 o Minor bugfixes (directory):
2861 - When generating a URL for a directory server on an IPv6 address,
2862 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
2863 on 0.2.3.9-alpha. Patch from Malek.
2865 o Minor bugfixes (fallback directory mirrors):
2866 - When requesting extrainfo descriptors from a trusted directory
2867 server, check whether it is an authority or a fallback directory
2868 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
2869 0.2.4.7-alpha. Reported by atagar, patch by teor.
2871 o Minor bugfixes (hidden service, client):
2872 - Handle the case where the user makes several fast consecutive
2873 requests to the same .onion address. Previously, the first six
2874 requests would each trigger a descriptor fetch, each picking a
2875 directory (there are 6 overall) and the seventh one would fail
2876 because no directories were left, thereby triggering a close on
2877 all current directory connections asking for the hidden service.
2878 The solution here is to not close the connections if we have
2879 pending directory fetches. Fixes bug 15937; bugfix
2882 o Minor bugfixes (hidden service, control port):
2883 - Add the onion address to the HS_DESC event for the UPLOADED action
2884 both on success or failure. It was previously hardcoded with
2885 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
2887 o Minor bugfixes (hidden service, directory):
2888 - Bridges now refuse "rendezvous2" (hidden service descriptor)
2889 publish attempts. Suggested by ticket 18332.
2891 o Minor bugfixes (linux seccomp2 sandbox):
2892 - Allow the setrlimit syscall, and the prlimit and prlimit64
2893 syscalls, which some libc implementations use under the hood.
2894 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
2895 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
2896 enabled and no DNS resolvers configured. This should help TAILS
2897 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
2898 - Fix the sandbox's interoperability with unix domain sockets under
2899 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
2901 o Minor bugfixes (logging):
2902 - When logging information about an unparsable networkstatus vote or
2903 consensus, do not say "vote" when we mean consensus. Fixes bug
2904 18368; bugfix on 0.2.0.8-alpha.
2905 - Scrub service name in "unrecognized service ID" log messages.
2906 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
2907 - Downgrade logs and backtraces about IP versions to info-level.
2908 Only log backtraces once each time tor runs. Assists in diagnosing
2909 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
2910 Christian, patch by teor.
2912 o Minor bugfixes (memory safety):
2913 - Avoid freeing an uninitialized pointer when opening a socket fails
2914 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
2915 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
2917 - Correctly duplicate addresses in get_interface_address6_list().
2918 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
2919 patch by "cypherpunks".
2920 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
2922 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
2923 18672; bugfix on 0.2.5.1-alpha.
2925 o Minor bugfixes (private directory):
2926 - Prevent a race condition when creating private directories. Fixes
2927 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
2928 Patch from jsturgix. Found with Flawfinder.
2930 o Minor bugfixes (test networks, IPv6):
2931 - Allow internal IPv6 addresses in descriptors in test networks.
2932 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
2935 o Minor bugfixes (testing):
2936 - We no longer disable assertions in the unit tests when coverage is
2937 enabled. Instead, we require you to say --disable-asserts-in-tests
2938 to the configure script if you need assertions disabled in the
2939 unit tests (for example, if you want to perform branch coverage).
2940 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
2942 o Minor bugfixes (time parsing):
2943 - Avoid overflow in tor_timegm when parsing dates in and after 2038
2944 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
2945 0.0.2pre14. Patch by teor.
2947 o Minor bugfixes (tor-gencert):
2948 - Correctly handle the case where an authority operator enters a
2949 passphrase but sends an EOF before sending a newline. Fixes bug
2950 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
2952 o Code simplification and refactoring:
2953 - Quote all the string interpolations in configure.ac -- even those
2954 which we are pretty sure can't contain spaces. Closes ticket
2955 17744. Patch from zerosion.
2956 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
2957 inplace, so there's no need to have a separate implementation for
2958 the non-inplace code. Closes ticket 18258. Patch from Malek.
2959 - Simplify return types for some crypto functions that can't
2960 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
2963 - Change build messages to refer to "Fedora" instead of "Fedora
2964 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
2965 Patches from "icanhasaccount" and "cypherpunks".
2968 - We no longer maintain an internal freelist in memarea.c.
2969 Allocators should be good enough to make this code unnecessary,
2970 and it's doubtful that it ever had any performance benefit.
2973 - Fix several warnings from clang's address sanitizer produced in
2975 - Treat backtrace test failures as expected on FreeBSD until we
2976 solve bug 17808. Closes ticket 18204.
2979 Changes in version 0.2.8.1-alpha - 2016-02-04
2980 Tor 0.2.8.1-alpha is the first alpha release in its series. It
2981 includes numerous small features and bugfixes against previous Tor
2982 versions, and numerous small infrastructure improvements. The most
2983 notable features are a set of improvements to the directory subsystem.
2985 o Major features (security, Linux):
2986 - When Tor starts as root on Linux and is told to switch user ID, it
2987 can now retain the capability to bind to low ports. By default,
2988 Tor will do this only when it's switching user ID and some low
2989 ports have been configured. You can change this behavior with the
2990 new option KeepBindCapabilities. Closes ticket 8195.
2992 o Major features (directory system):
2993 - When bootstrapping multiple consensus downloads at a time, use the
2994 first one that starts downloading, and close the rest. This
2995 reduces failures when authorities or fallback directories are slow
2996 or down. Together with the code for feature 15775, this feature
2997 should reduces failures due to fallback churn. Implements ticket
2998 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
2999 "mikeperry" and "teor".
3000 - Include a trial list of 21 default fallback directories, generated
3001 in January 2016, based on an opt-in survey of suitable relays.
3002 Doing this should make clients bootstrap more quickly and reliably,
3003 and reduce the load on the directory authorities. Closes ticket
3004 15775. Patch by "teor".
3005 Candidates identified using an OnionOO script by "weasel", "teor",
3006 "gsathya", and "karsten".
3007 - Previously only relays that explicitly opened a directory port
3008 (DirPort) accepted directory requests from clients. Now all
3009 relays, with and without a DirPort, accept and serve tunneled
3010 directory requests that they receive through their ORPort. You can
3011 disable this behavior using the new DirCache option. Closes
3014 o Major key updates:
3015 - Update the V3 identity key for the dannenberg directory authority:
3016 it was changed on 18 November 2015. Closes task 17906. Patch
3019 o Minor features (security, clock):
3020 - Warn when the system clock appears to move back in time (when the
3021 state file was last written in the future). Tor doesn't know that
3022 consensuses have expired if the clock is in the past. Patch by
3023 "teor". Implements ticket 17188.
3025 o Minor features (security, exit policies):
3026 - ExitPolicyRejectPrivate now rejects more private addresses by
3027 default. Specifically, it now rejects the relay's outbound bind
3028 addresses (if configured), and the relay's configured port
3029 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
3030 0.2.0.11-alpha. Patch by "teor".
3032 o Minor features (security, memory erasure):
3033 - Set the unused entries in a smartlist to NULL. This helped catch
3034 a (harmless) bug, and shouldn't affect performance too much.
3035 Implements ticket 17026.
3036 - Use SecureMemoryWipe() function to securely clean memory on
3037 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
3038 Implements feature 17986.
3039 - Use explicit_bzero or memset_s when present. Previously, we'd use
3040 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
3041 from <logan@hackers.mu> and <selven@hackers.mu>.
3042 - Make memwipe() do nothing when passed a NULL pointer or buffer of
3043 zero size. Check size argument to memwipe() for underflow. Fixes
3044 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
3047 o Minor features (security, RNG):
3048 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
3049 positively are not allowed to fail. Previously we depended on
3050 internal details of OpenSSL's behavior. Closes ticket 17686.
3051 - Never use the system entropy output directly for anything besides
3052 seeding the PRNG. When we want to generate important keys, instead
3053 of using system entropy directly, we now hash it with the PRNG
3054 stream. This may help resist certain attacks based on broken OS
3055 entropy implementations. Closes part of ticket 17694.
3056 - Use modern system calls (like getentropy() or getrandom()) to
3057 generate strong entropy on platforms that have them. Closes
3060 o Minor features (accounting):
3061 - Added two modes to the AccountingRule option: One for limiting
3062 only the number of bytes sent ("AccountingRule out"), and one for
3063 limiting only the number of bytes received ("AccountingRule in").
3064 Closes ticket 15989; patch from "unixninja92".
3066 o Minor features (build):
3067 - Since our build process now uses "make distcheck", we no longer
3068 force "make dist" to depend on "make check". Closes ticket 17893;
3069 patch from "cypherpunks."
3070 - Tor now builds successfully with the recent OpenSSL 1.1
3071 development branch, and with the latest LibreSSL. Closes tickets
3072 17549, 17921, and 17984.
3074 o Minor features (controller):
3075 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
3076 tickets 16774 and 17817. Patch by George Tankersley.
3077 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
3078 service descriptor from a service's local hidden service
3079 descriptor cache. Closes ticket 14846.
3080 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
3081 controllers can examine the the reject rules added by
3082 ExitPolicyRejectPrivate. This makes it easier for stem to display
3085 o Minor features (crypto):
3086 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
3088 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
3089 - When allocating a digest state object, allocate no more space than
3090 we actually need. Previously, we would allocate as much space as
3091 the state for the largest algorithm would need. This change saves
3092 up to 672 bytes per circuit. Closes ticket 17796.
3093 - Improve performance when hashing non-multiple of 8 sized buffers,
3094 based on Andrew Moon's public domain SipHash-2-4 implementation.
3095 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
3097 o Minor features (directory downloads):
3098 - Wait for busy authorities and fallback directories to become non-
3099 busy when bootstrapping. (A similar change was made in 6c443e987d
3100 for directory caches chosen from the consensus.) Closes ticket
3101 17864; patch by "teor".
3102 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
3103 directory mirrors. The default is 1; set it to 0 to disable
3104 fallbacks. Implements ticket 17576. Patch by "teor".
3106 o Minor features (geoip):
3107 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
3110 o Minor features (IPv6):
3111 - Add an argument 'ipv6=address:orport' to the DirAuthority and
3112 FallbackDir torrc options, to specify an IPv6 address for an
3113 authority or fallback directory. Add hard-coded ipv6 addresses for
3114 directory authorities that have them. Closes ticket 17327; patch
3115 from Nick Mathewson and "teor".
3116 - Add address policy assume_action support for IPv6 addresses.
3117 - Limit IPv6 mask bits to 128.
3118 - Warn when comparing against an AF_UNSPEC address in a policy, it's
3119 almost always a bug. Closes ticket 17863; patch by "teor".
3120 - Allow users to configure directory authorities and fallback
3121 directory servers with IPv6 addresses and ORPorts. Resolves
3123 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
3124 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
3125 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
3126 17638; bugfix on 0.0.2pre8. Patch by "teor".
3128 o Minor features (logging):
3129 - When logging to syslog, allow a tag to be added to the syslog
3130 identity (the string prepended to every log message). The tag can
3131 be configured with SyslogIdentityTag and defaults to none. Setting
3132 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
3135 o Minor features (portability):
3136 - Use timingsafe_memcmp() where available. Closes ticket 17944;
3137 patch from <logan@hackers.mu>.
3139 o Minor features (relay, address discovery):
3140 - Add a family argument to get_interface_addresses_raw() and
3141 subfunctions to make network interface address interogation more
3142 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
3143 types of interfaces from the operating system. Resolves
3145 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
3146 fails to enumerate interface addresses using the platform-specific
3147 API, have it rely on the UDP socket fallback technique to try and
3148 find out what IP addresses (both IPv4 and IPv6) our machine has.
3149 Resolves ticket 17951.
3151 o Minor features (replay cache):
3152 - The replay cache now uses SHA256 instead of SHA1. Implements
3153 feature 8961. Patch by "teor", issue reported by "rransom".
3155 o Minor features (unix file permissions):
3156 - Defer creation of Unix sockets until after setuid. This avoids
3157 needing CAP_CHOWN and CAP_FOWNER when using systemd's
3158 CapabilityBoundingSet, or chown and fowner when using SELinux.
3159 Implements part of ticket 17562. Patch from Jamie Nguyen.
3160 - If any directory created by Tor is marked as group readable, the
3161 filesystem group is allowed to be either the default GID or the
3162 root user. Allowing root to read the DataDirectory prevents the
3163 need for CAP_READ_SEARCH when using systemd's
3164 CapabilityBoundingSet, or dac_read_search when using SELinux.
3165 Implements part of ticket 17562. Patch from Jamie Nguyen.
3166 - Introduce a new DataDirectoryGroupReadable option. If it is set to
3167 1, the DataDirectory will be made readable by the default GID.
3168 Implements part of ticket 17562. Patch from Jamie Nguyen.
3170 o Minor bugfixes (accounting):
3171 - The max bandwidth when using 'AccountRule sum' is now correctly
3172 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
3175 o Minor bugfixes (code correctness):
3176 - When closing an entry connection, generate a warning if we should
3177 have sent an end cell for it but we haven't. Fixes bug 17876;
3178 bugfix on 0.2.3.2-alpha.
3179 - Assert that allocated memory held by the reputation code is freed
3180 according to its internal counters. Fixes bug 17753; bugfix
3182 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
3185 o Minor bugfixes (compilation):
3186 - Mark all object files that include micro-revision.i as depending
3187 on it, so as to make parallel builds more reliable. Fixes bug
3188 17826; bugfix on 0.2.5.1-alpha.
3189 - Don't try to use the pthread_condattr_setclock() function unless
3190 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
3191 17819; bugfix on 0.2.6.3-alpha.
3192 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
3194 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
3195 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
3196 - Fix search for libevent libraries on OpenBSD (and other systems
3197 that install libevent 1 and libevent 2 in parallel). Fixes bug
3198 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
3199 - Isolate environment variables meant for tests from the rest of the
3200 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
3201 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
3203 - Remove config.log only from make distclean, not from make clean.
3204 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
3206 o Minor bugfixes (crypto):
3207 - Check the return value of HMAC() and assert on failure. Fixes bug
3208 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
3210 o Minor bugfixes (fallback directories):
3211 - Mark fallbacks as "too busy" when they return a 503 response,
3212 rather than just marking authorities. Fixes bug 17572; bugfix on
3213 0.2.4.7-alpha. Patch by "teor".
3215 o Minor bugfixes (IPv6):
3216 - Update the limits in max_dl_per_request for IPv6 address length.
3217 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
3219 o Minor bugfixes (linux seccomp2 sandbox):
3220 - Fix a crash when using offline master ed25519 keys with the Linux
3221 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
3223 o Minor bugfixes (logging):
3224 - In log messages that include a function name, use __FUNCTION__
3225 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
3226 with clang __PRETTY_FUNCTION__ has extra information we don't
3227 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
3229 - Remove needless quotes from a log message about unparseable
3230 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
3232 o Minor bugfixes (portability):
3233 - Remove an #endif from configure.ac so that we correctly detect the
3234 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
3237 o Minor bugfixes (relays):
3238 - Check that both the ORPort and DirPort (if present) are reachable
3239 before publishing a relay descriptor. Otherwise, relays publish a
3240 descriptor with DirPort 0 when the DirPort reachability test takes
3241 longer than the ORPort reachability test. Fixes bug 18050; bugfix
3242 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
3244 o Minor bugfixes (relays, hidden services):
3245 - Refuse connection requests to private OR addresses unless
3246 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
3247 then refuse to send any cells to a private address. Fixes bugs
3248 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
3250 o Minor bugfixes (safe logging):
3251 - When logging a malformed hostname received through socks4, scrub
3252 it if SafeLogging says we should. Fixes bug 17419; bugfix
3255 o Minor bugfixes (statistics code):
3256 - Consistently check for overflow in round_*_to_next_multiple_of
3257 functions, and add unit tests with additional and maximal values.
3258 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
3259 - Handle edge cases in the laplace functions: avoid division by
3260 zero, avoid taking the log of zero, and silence clang type
3261 conversion warnings using round and trunc. Add unit tests for edge
3262 cases with maximal values. Fixes part of bug 13192; bugfix
3265 o Minor bugfixes (testing):
3266 - The test for log_heartbeat was incorrectly failing in timezones
3267 with non-integer offsets. Instead of comparing the end of the time
3268 string against a constant, compare it to the output of
3269 format_local_iso_time when given the correct input. Fixes bug
3270 18039; bugfix on 0.2.5.4-alpha.
3271 - Make unit tests pass on IPv6-only systems, and systems without
3272 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
3273 bugfix on 0.2.7.3-rc. Patch by "teor".
3274 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
3276 - Check the full results of SHA256 and SHA512 digests in the unit
3277 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
3279 o Code simplification and refactoring:
3280 - Move logging of redundant policy entries in
3281 policies_parse_exit_policy_internal into its own function. Closes
3282 ticket 17608; patch from "juce".
3283 - Extract the more complicated parts of circuit_mark_for_close()
3284 into a new function that we run periodically before circuits are
3285 freed. This change removes more than half of the functions
3286 currently in the "blob". Closes ticket 17218.
3287 - Clean up a little duplicated code in
3288 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
3290 - Decouple the list of streams waiting to be attached to circuits
3291 from the overall connection list. This change makes it possible to
3292 attach streams quickly while simplifying Tor's callgraph and
3293 avoiding O(N) scans of the entire connection list. Closes
3295 - When a direct directory request fails immediately on launch,
3296 instead of relaunching that request from inside the code that
3297 launches it, instead mark the connection for teardown. This change
3298 simplifies Tor's callback and prevents the directory-request
3299 launching code from invoking itself recursively. Closes
3301 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
3302 use them. Closes ticket 17926.
3305 - Add a description of the correct use of the '--keygen' command-
3306 line option. Closes ticket 17583; based on text by 's7r'.
3307 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
3308 - Explain actual minima for BandwidthRate. Closes ticket 16382.
3309 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
3310 - Mention torspec URL in the manpage and point the reader to it
3311 whenever we mention a document that belongs in torspce. Fixes
3315 - Remove client-side support for connecting to Tor relays running
3316 versions of Tor before 0.2.3.6-alpha. These relays didn't support
3317 the v3 TLS handshake protocol, and are no longer allowed on the
3318 Tor network. Implements the client side of ticket 11150. Based on
3319 patches by Tom van der Woerdt.
3322 - Add unit tests to check for common RNG failure modes, such as
3323 returning all zeroes, identical values, or incrementing values
3324 (OpenSSL's rand_predictable feature). Patch by "teor".
3325 - Log more information when the backtrace tests fail. Closes ticket
3326 17892. Patch from "cypherpunks."
3327 - Always test both ed25519 backends, so that we can be sure that our
3328 batch-open replacement code works. Part of ticket 16794.
3329 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
3330 portion of ticket 16831.
3331 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
3332 util_format.c, directory.c, and options_validate.c. Closes tickets
3333 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
3335 - Unit tests for directory_handle_command_get. Closes ticket 17004.
3336 Patch from Reinaldo de Souza Jr.
3339 Changes in version 0.2.7.6 - 2015-12-10
3340 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
3341 well as a minor bug in hidden service reliability.
3343 o Major bugfixes (guard selection):
3344 - Actually look at the Guard flag when selecting a new directory
3345 guard. When we implemented the directory guard design, we
3346 accidentally started treating all relays as if they have the Guard
3347 flag during guard selection, leading to weaker anonymity and worse
3348 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
3351 o Minor features (geoip):
3352 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
3355 o Minor bugfixes (compilation):
3356 - When checking for net/pfvar.h, include netinet/in.h if possible.
3357 This fixes transparent proxy detection on OpenBSD. Fixes bug
3358 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
3359 - Fix a compilation warning with Clang 3.6: Do not check the
3360 presence of an address which can never be NULL. Fixes bug 17781.
3362 o Minor bugfixes (correctness):
3363 - When displaying an IPv6 exit policy, include the mask bits
3364 correctly even when the number is greater than 31. Fixes bug
3365 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
3366 - The wrong list was used when looking up expired intro points in a
3367 rend service object, causing what we think could be reachability
3368 issues for hidden services, and triggering a BUG log. Fixes bug
3369 16702; bugfix on 0.2.7.2-alpha.
3370 - Fix undefined behavior in the tor_cert_checksig function. Fixes
3371 bug 17722; bugfix on 0.2.7.2-alpha.
3374 Changes in version 0.2.7.5 - 2015-11-20
3375 The Tor 0.2.7 release series is dedicated to the memory of Tor user
3376 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
3377 tirelessly to advocate human rights regardless of national borders,
3378 and oppose the encroachments of mass surveillance. He opposed national
3379 exceptionalism, he brought clarity to legal and policy debates, he
3380 understood and predicted the impact of mass surveillance on the world,
3381 and he laid the groundwork for resisting it. While serving on the Tor
3382 Project's board of directors, he brought us his uncompromising focus
3383 on technical excellence in the service of humankind. Caspar was an
3384 inimitable force for good and a wonderful friend. He was kind,
3385 humorous, generous, gallant, and believed we should protect one
3386 another without exception. We honor him here for his ideals, his
3387 efforts, and his accomplishments. Please honor his memory with works
3388 that would make him proud.
3390 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
3392 The 0.2.7 series adds a more secure identity key type for relays,
3393 improves cryptography performance, resolves several longstanding
3394 hidden-service performance issues, improves controller support for
3395 hidden services, and includes small bugfixes and performance
3396 improvements throughout the program. This release series also includes
3397 more tests than before, and significant simplifications to which parts
3398 of Tor invoke which others.
3400 (This release contains no code changes since 0.2.7.4-rc.)
3403 Changes in version 0.2.7.4-rc - 2015-10-21
3404 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
3405 fixes some important memory leaks, and a scary-looking (but mostly
3406 harmless in practice) invalid-read bug. It also has a few small
3407 bugfixes, notably fixes for compilation and portability on different
3408 platforms. If no further significant bounds are found, the next
3409 release will the the official stable release.
3411 o Major bugfixes (security, correctness):
3412 - Fix an error that could cause us to read 4 bytes before the
3413 beginning of an openssl string. This bug could be used to cause
3414 Tor to crash on systems with unusual malloc implementations, or
3415 systems with unusual hardening installed. Fixes bug 17404; bugfix
3418 o Major bugfixes (correctness):
3419 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
3420 bug 17401; bugfix on 0.2.7.3-rc.
3422 o Major bugfixes (memory leaks):
3423 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
3424 17398; bugfix on 0.2.6.1-alpha.
3425 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
3426 17402; bugfix on 0.2.7.3-rc.
3427 - Fix a memory leak when reading an expired signing key from disk.
3428 Fixes bug 17403; bugfix on 0.2.7.2-rc.
3430 o Minor features (geoIP):
3431 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
3434 o Minor bugfixes (compilation):
3435 - Repair compilation with the most recent (unreleased, alpha)
3436 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
3437 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
3438 17251; bugfix on 0.2.7.2-alpha.
3439 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
3440 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
3442 o Minor bugfixes (portability):
3443 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
3444 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
3447 o Minor bugfixes (sandbox):
3448 - Add the "hidserv-stats" filename to our sandbox filter for the
3449 HiddenServiceStatistics option to work properly. Fixes bug 17354;
3450 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
3452 o Minor bugfixes (testing):
3453 - Add unit tests for get_interface_address* failure cases. Fixes bug
3454 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
3455 - Fix breakage when running 'make check' with BSD make. Fixes bug
3456 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
3457 - Make the get_ifaddrs_* unit tests more tolerant of different
3458 network configurations. (Don't assume every test box has an IPv4
3459 address, and don't assume every test box has a non-localhost
3460 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
3461 - Skip backtrace tests when backtrace support is not compiled in.
3462 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
3466 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
3467 - Note that HiddenServicePorts can take a unix domain socket. Closes
3471 Changes in version 0.2.7.3-rc - 2015-09-25
3472 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
3473 contains numerous usability fixes for Ed25519 keys, safeguards against
3474 several misconfiguration problems, significant simplifications to
3475 Tor's callgraph, and numerous bugfixes and small features.
3477 This is the most tested release of Tor to date. The unit tests cover
3478 39.40% of the code, and the integration tests (accessible with "make
3479 test-full-online", requiring stem and chutney and a network
3480 connection) raise the coverage to 64.49%.
3482 o Major features (security, hidden services):
3483 - Hidden services, if using the EntryNodes option, are required to
3484 use more than one EntryNode, in order to avoid a guard discovery
3485 attack. (This would only affect people who had configured hidden
3486 services and manually specified the EntryNodes option with a
3487 single entry-node. The impact was that it would be easy to
3488 remotely identify the guard node used by such a hidden service.
3489 See ticket for more information.) Fixes ticket 14917.
3491 o Major features (Ed25519 keys, keypinning):
3492 - The key-pinning option on directory authorities is now advisory-
3493 only by default. In a future version, or when the AuthDirPinKeys
3494 option is set, pins are enforced again. Disabling key-pinning
3495 seemed like a good idea so that we can survive the fallout of any
3496 usability problems associated with Ed25519 keys. Closes
3499 o Major features (Ed25519 performance):
3500 - Improve the speed of Ed25519 operations and Curve25519 keypair
3501 generation when built targeting 32 bit x86 platforms with SSE2
3502 available. Implements ticket 16535.
3503 - Improve the runtime speed of Ed25519 signature verification by
3504 using Ed25519-donna's batch verification support. Implements
3507 o Major features (performance testing):
3508 - The test-network.sh script now supports performance testing.
3509 Requires corresponding chutney performance testing changes. Patch
3510 by "teor". Closes ticket 14175.
3512 o Major features (relay, Ed25519):
3513 - Significant usability improvements for Ed25519 key management. Log
3514 messages are better, and the code can recover from far more
3515 failure conditions. Thanks to "s7r" for reporting and diagnosing
3517 - Add a new OfflineMasterKey option to tell Tor never to try loading
3518 or generating a secret Ed25519 identity key. You can use this in
3519 combination with tor --keygen to manage offline and/or encrypted
3520 Ed25519 keys. Implements ticket 16944.
3521 - Add a --newpass option to allow changing or removing the
3522 passphrase of an encrypted key with tor --keygen. Implements part
3524 - On receiving a HUP signal, check to see whether the Ed25519
3525 signing key has changed, and reload it if so. Closes ticket 16790.
3527 o Major bugfixes (relay, Ed25519):
3528 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
3529 0.2.7.2-alpha. Reported by "s7r".
3530 - Improve handling of expired signing keys with offline master keys.
3531 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
3533 o Minor features (client-side privacy):
3534 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
3535 lifespan when IsolateSOCKSAuth and streams with SOCKS
3536 authentication are attached to the circuit. This allows
3537 applications like TorBrowser to manage circuit lifetime on their
3538 own. Implements feature 15482.
3539 - When logging malformed hostnames from SOCKS5 requests, respect
3540 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
3542 o Minor features (compilation):
3543 - Give a warning as early as possible when trying to build with an
3544 unsupported OpenSSL version. Closes ticket 16901.
3545 - Fail during configure if we're trying to build against an OpenSSL
3546 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
3547 which started requiring ECC.
3549 o Minor features (geoip):
3550 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
3553 o Minor features (hidden services):
3554 - Relays need to have the Fast flag to get the HSDir flag. As this
3555 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
3556 drop. This change should make some attacks against the hidden
3557 service directory system harder. Fixes ticket 15963.
3558 - Turn on hidden service statistics collection by setting the torrc
3559 option HiddenServiceStatistics to "1" by default. (This keeps
3560 track only of the fraction of traffic used by hidden services, and
3561 the total number of hidden services in existence.) Closes
3563 - Client now uses an introduction point failure cache to know when
3564 to fetch or keep a descriptor in their cache. Previously, failures
3565 were recorded implicitly, but not explicitly remembered. Closes
3568 o Minor features (testing, authorities, documentation):
3569 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
3570 explicitly manage consensus flags in testing networks. Patch by
3571 "robgjansen", modified by "teor". Implements part of ticket 14882.
3573 o Minor bugfixes (security, exit policies):
3574 - ExitPolicyRejectPrivate now also rejects the relay's published
3575 IPv6 address (if any), and any publicly routable IPv4 or IPv6
3576 addresses on any local interfaces. ticket 17027. Patch by "teor".
3577 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
3579 o Minor bug fixes (torrc exit policies):
3580 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
3581 produce IPv6 wildcard addresses. Previously they would produce
3582 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
3583 of bug 16069; bugfix on 0.2.4.7-alpha.
3584 - When parsing torrc ExitPolicies, we now warn for a number of cases
3585 where the user's intent is likely to differ from Tor's actual
3586 behavior. These include: using an IPv4 address with an accept6 or
3587 reject6 line; using "private" on an accept6 or reject6 line; and
3588 including any ExitPolicy lines after accept *:* or reject *:*.
3589 Related to ticket 16069.
3590 - When parsing torrc ExitPolicies, we now issue an info-level
3591 message when expanding an "accept/reject *" line to include both
3592 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
3593 - In each instance above, usage advice is provided to avoid the
3594 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
3595 16069; bugfix on 0.2.4.7-alpha.
3597 o Minor bugfixes (authority):
3598 - Don't assign "HSDir" to a router if it isn't Valid and Running.
3599 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
3600 - Downgrade log messages about Ed25519 key issues if they are in old
3601 cached router descriptors. Fixes part of bug 16286; bugfix
3603 - When we find an Ed25519 key issue in a cached descriptor, stop
3604 saying the descriptor was just "uploaded". Fixes another part of
3605 bug 16286; bugfix on 0.2.7.2-alpha.
3607 o Minor bugfixes (control port):
3608 - Repair a warning and a spurious result when getting the maximum
3609 number of file descriptors from the controller. Fixes bug 16697;
3610 bugfix on 0.2.7.2-alpha.
3612 o Minor bugfixes (correctness):
3613 - When calling channel_free_list(), avoid calling smartlist_remove()
3614 while inside a FOREACH loop. This partially reverts commit
3615 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
3616 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
3618 o Minor bugfixes (documentation):
3619 - Advise users on how to configure separate IPv4 and IPv6 exit
3620 policies in the manpage and sample torrcs. Related to ticket 16069.
3621 - Fix the usage message of tor-resolve(1) so that it no longer lists
3622 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
3623 - Fix an error in the manual page and comments for
3624 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
3625 required "ORPort connectivity". While this is true, it is in no
3626 way unique to the HSDir flag. Of all the flags, only HSDirs need a
3627 DirPort configured in order for the authorities to assign that
3628 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
3631 o Minor bugfixes (Ed25519):
3632 - Fix a memory leak when reading router descriptors with expired
3633 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
3635 o Minor bugfixes (linux seccomp2 sandbox):
3636 - Allow bridge authorities to run correctly under the seccomp2
3637 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
3638 - Allow routers with ed25519 keys to run correctly under the
3639 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
3641 o Minor bugfixes (open file limit):
3642 - Fix set_max_file_descriptors() to set by default the max open file
3643 limit to the current limit when setrlimit() fails. Fixes bug
3644 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
3646 o Minor bugfixes (portability):
3647 - Try harder to normalize the exit status of the Tor process to the
3648 standard-provided range. Fixes bug 16975; bugfix on every version
3650 - Check correctly for Windows socket errors in the workqueue
3651 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
3652 - Fix the behavior of crypto_rand_time_range() when told to consider
3653 times before 1970. (These times were possible when running in a
3654 simulated network environment where time()'s output starts at
3655 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
3656 - Restore correct operation of TLS client-cipher detection on
3657 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
3659 o Minor bugfixes (relay):
3660 - Ensure that worker threads actually exit when a fatal error or
3661 shutdown is indicated. This fix doesn't currently affect the
3662 behavior of Tor, because Tor workers never indicates fatal error
3663 or shutdown except in the unit tests. Fixes bug 16868; bugfix
3665 - Unblock threads before releasing the work queue mutex to ensure
3666 predictable scheduling behavior. Fixes bug 16644; bugfix
3669 o Code simplification and refactoring:
3670 - Change the function that's called when we need to retry all
3671 downloads so that it only reschedules the downloads to happen
3672 immediately, rather than launching them all at once itself. This
3673 further simplifies Tor's callgraph.
3674 - Move some format-parsing functions out of crypto.c and
3675 crypto_curve25519.c into crypto_format.c and/or util_format.c.
3676 - Move the client-only parts of init_keys() into a separate
3677 function. Closes ticket 16763.
3678 - Simplify the microdesc_free() implementation so that it no longer
3679 appears (to code analysis tools) to potentially invoke a huge
3680 suite of other microdesc functions.
3681 - Simply the control graph further by deferring the inner body of
3682 directory_all_unreachable() into a callback. Closes ticket 16762.
3683 - Treat the loss of an owning controller as equivalent to a SIGTERM
3684 signal. This removes a tiny amount of duplicated code, and
3685 simplifies our callgraph. Closes ticket 16788.
3686 - When generating an event to send to the controller, we no longer
3687 put the event over the network immediately. Instead, we queue
3688 these events, and use a Libevent callback to deliver them. This
3689 change simplifies Tor's callgraph by reducing the number of
3690 functions from which all other Tor functions are reachable. Closes
3692 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
3693 that try to scan or compile every file on Unix won't decide that
3695 - Remove the unused "nulterminate" argument from buf_pullup().
3698 - Recommend a 40 GB example AccountingMax in torrc.sample rather
3699 than a 4 GB max. Closes ticket 16742.
3700 - Include the TUNING document in our source tarball. It is referred
3701 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
3705 - The internal pure-C tor-fw-helper tool is now removed from the Tor
3706 distribution, in favor of the pure-Go clone available from
3707 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
3708 used by the C tor-fw-helper are not, in our opinion, very
3709 confidence- inspiring in their secure-programming techniques.
3710 Closes ticket 13338.
3711 - Remove the code that would try to aggressively flush controller
3712 connections while writing to them. This code was introduced in
3713 0.1.2.7-alpha, in order to keep output buffers from exceeding
3714 their limits. But there is no longer a maximum output buffer size,
3715 and flushing data in this way caused some undesirable recursions
3716 in our call graph. Closes ticket 16480.
3719 - Make "bridges+hs" the default test network. This tests almost all
3720 tor functionality during make test-network, while allowing tests
3721 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
3722 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
3723 (chutney). Patches by "teor".
3724 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
3725 by-side in the same parent directory. Closes ticket 16903. Patch
3727 - Use environment variables rather than autoconf substitutions to
3728 send variables from the build system to the test scripts. This
3729 change should be easier to maintain, and cause 'make distcheck' to
3730 work better than before. Fixes bug 17148.
3731 - Add a new set of callgraph analysis scripts that use clang to
3732 produce a list of which Tor functions are reachable from which
3733 other Tor functions. We're planning to use these to help simplify
3734 our code structure by identifying illogical dependencies.
3735 - Add new 'test-full' and 'test-full-online' targets to run all
3736 tests, including integration tests with stem and chutney.
3737 - Make the test-workqueue test work on Windows by initializing the
3738 network before we begin.
3739 - New make target (make test-network-all) to run multiple applicable
3740 chutney test cases. Patch from Teor; closes 16953.
3741 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
3742 functions in dns.c. Implements a portion of ticket 16831.
3743 - When building Tor with testing coverage enabled, run Chutney tests
3744 (if any) using the 'tor-cov' coverage binary.
3745 - When running test-network or test-stem, check for the absence of
3746 stem/chutney before doing any build operations.
3749 Changes in version 0.2.7.2-alpha - 2015-07-27
3750 This, the second alpha in the Tor 0.2.7 series, has a number of new
3751 features, including a way to manually pick the number of introduction
3752 points for hidden services, and the much stronger Ed25519 signing key
3753 algorithm for regular Tor relays (including support for encrypted
3754 offline identity keys in the new algorithm).
3756 Support for Ed25519 on relays is currently limited to signing router
3757 descriptors; later alphas in this series will extend Ed25519 key
3758 support to more parts of the Tor protocol.
3760 o Major features (Ed25519 identity keys, Proposal 220):
3761 - All relays now maintain a stronger identity key, using the Ed25519
3762 elliptic curve signature format. This master key is designed so
3763 that it can be kept offline. Relays also generate an online
3764 signing key, and a set of other Ed25519 keys and certificates.
3765 These are all automatically regenerated and rotated as needed.
3766 Implements part of ticket 12498.
3767 - Directory authorities now vote on Ed25519 identity keys along with
3768 RSA1024 keys. Implements part of ticket 12498.
3769 - Directory authorities track which Ed25519 identity keys have been
3770 used with which RSA1024 identity keys, and do not allow them to
3771 vary freely. Implements part of ticket 12498.
3772 - Microdescriptors now include Ed25519 identity keys. Implements
3773 part of ticket 12498.
3774 - Add support for offline encrypted Ed25519 master keys. To use this
3775 feature on your tor relay, run "tor --keygen" to make a new master
3776 key (or to make a new signing key if you already have a master
3777 key). Closes ticket 13642.
3779 o Major features (Hidden services):
3780 - Add the torrc option HiddenServiceNumIntroductionPoints, to
3781 specify a fixed number of introduction points. Its maximum value
3782 is 10 and default is 3. Using this option can increase a hidden
3783 service's reliability under load, at the cost of making it more
3784 visible that the hidden service is facing extra load. Closes
3786 - Remove the adaptive algorithm for choosing the number of
3787 introduction points, which used to change the number of
3788 introduction points (poorly) depending on the number of
3789 connections the HS sees. Closes ticket 4862.
3791 o Major features (onion key cross-certification):
3792 - Relay descriptors now include signatures of their own identity
3793 keys, made using the TAP and ntor onion keys. These signatures
3794 allow relays to prove ownership of their own onion keys. Because
3795 of this change, microdescriptors will no longer need to include
3796 RSA identity keys. Implements proposal 228; closes ticket 12499.
3798 o Major features (performance):
3799 - Improve the runtime speed of Ed25519 operations by using the
3800 public-domain Ed25519-donna by Andrew M. ("floodyberry").
3801 Implements ticket 16467.
3802 - Improve the runtime speed of the ntor handshake by using an
3803 optimized curve25519 basepoint scalarmult implementation from the
3804 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
3805 ideas by Adam Langley. Implements ticket 9663.
3807 o Major bugfixes (client-side privacy, also in 0.2.6.9):
3808 - Properly separate out each SOCKSPort when applying stream
3809 isolation. The error occurred because each port's session group
3810 was being overwritten by a default value when the listener
3811 connection was initialized. Fixes bug 16247; bugfix on
3812 0.2.6.3-alpha. Patch by "jojelino".
3814 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
3815 - Stop refusing to store updated hidden service descriptors on a
3816 client. This reverts commit 9407040c59218 (which indeed fixed bug
3817 14219, but introduced a major hidden service reachability
3818 regression detailed in bug 16381). This is a temporary fix since
3819 we can live with the minor issue in bug 14219 (it just results in
3820 some load on the network) but the regression of 16381 is too much
3821 of a setback. First-round fix for bug 16381; bugfix
3824 o Major bugfixes (hidden services):
3825 - When cannibalizing a circuit for an introduction point, always
3826 extend to the chosen exit node (creating a 4 hop circuit).
3827 Previously Tor would use the current circuit exit node, which
3828 changed the original choice of introduction point, and could cause
3829 the hidden service to skip excluded introduction points or
3830 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
3833 o Major bugfixes (open file limit):
3834 - The open file limit wasn't checked before calling
3835 tor_accept_socket_nonblocking(), which would make Tor exceed the
3836 limit. Now, before opening a new socket, Tor validates the open
3837 file limit just before, and if the max has been reached, return an
3838 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
3840 o Major bugfixes (stability, also in 0.2.6.10):
3841 - Stop crashing with an assertion failure when parsing certain kinds
3842 of malformed or truncated microdescriptors. Fixes bug 16400;
3843 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
3844 by "cypherpunks_backup".
3845 - Stop random client-side assertion failures that could occur when
3846 connecting to a busy hidden service, or connecting to a hidden
3847 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
3850 o Minor features (directory authorities, security, also in 0.2.6.9):
3851 - The HSDir flag given by authorities now requires the Stable flag.
3852 For the current network, this results in going from 2887 to 2806
3853 HSDirs. Also, it makes it harder for an attacker to launch a sybil
3854 attack by raising the effort for a relay to become Stable to
3855 require at the very least 7 days, while maintaining the 96 hours
3856 uptime requirement for HSDir. Implements ticket 8243.
3858 o Minor features (client):
3859 - Relax the validation of hostnames in SOCKS5 requests, allowing the
3860 character '_' to appear, in order to cope with domains observed in
3861 the wild that are serving non-RFC compliant records. Resolves
3863 - Relax the validation done to hostnames in SOCKS5 requests, and
3864 allow a single trailing '.' to cope with clients that pass FQDNs
3865 using that syntax to explicitly indicate that the domain name is
3866 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
3867 - Add GroupWritable and WorldWritable options to unix-socket based
3868 SocksPort and ControlPort options. These options apply to a single
3869 socket, and override {Control,Socks}SocketsGroupWritable. Closes
3872 o Minor features (control protocol):
3873 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
3874 the control protocol. Resolves ticket 15358.
3876 o Minor features (directory authorities):
3877 - Directory authorities no longer vote against the "Fast", "Stable",
3878 and "HSDir" flags just because they were going to vote against
3879 "Running": if the consensus turns out to be that the router was
3880 running, then the authority's vote should count. Patch from Peter
3881 Retzlaff; closes issue 8712.
3883 o Minor features (geoip, also in 0.2.6.10):
3884 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
3885 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
3887 o Minor features (hidden services):
3888 - Add the new options "HiddenServiceMaxStreams" and
3889 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
3890 limit the maximum number of simultaneous streams per circuit, and
3891 optionally tear down the circuit when the limit is exceeded. Part
3894 o Minor features (portability):
3895 - Use C99 variadic macros when the compiler is not GCC. This avoids
3896 failing compilations on MSVC, and fixes a log-file-based race
3897 condition in our old workarounds. Original patch from Gisle Vanem.
3899 o Minor bugfixes (compilation, also in 0.2.6.9):
3900 - Build with --enable-systemd correctly when libsystemd is
3901 installed, but systemd is not. Fixes bug 16164; bugfix on
3902 0.2.6.3-alpha. Patch from Peter Palfrader.
3904 o Minor bugfixes (controller):
3905 - Add the descriptor ID in each HS_DESC control event. It was
3906 missing, but specified in control-spec.txt. Fixes bug 15881;
3907 bugfix on 0.2.5.2-alpha.
3909 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
3910 - Check for failures from crypto_early_init, and refuse to continue.
3911 A previous typo meant that we could keep going with an
3912 uninitialized crypto library, and would have OpenSSL initialize
3913 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
3914 when implementing ticket 4900. Patch by "teor".
3916 o Minor bugfixes (hidden services):
3917 - Fix a crash when reloading configuration while at least one
3918 configured and one ephemeral hidden service exists. Fixes bug
3919 16060; bugfix on 0.2.7.1-alpha.
3920 - Avoid crashing with a double-free bug when we create an ephemeral
3921 hidden service but adding it fails for some reason. Fixes bug
3922 16228; bugfix on 0.2.7.1-alpha.
3924 o Minor bugfixes (Linux seccomp2 sandbox):
3925 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
3926 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
3928 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
3929 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
3930 these when eventfd2() support is missing. Fixes bug 16363; bugfix
3931 on 0.2.6.3-alpha. Patch from "teor".
3933 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
3934 - Fix sandboxing to work when running as a relay, by allowing the
3935 renaming of secret_id_key, and allowing the eventfd2 and futex
3936 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
3938 - Allow systemd connections to work with the Linux seccomp2 sandbox
3939 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
3942 o Minor bugfixes (relay):
3943 - Fix a rarely-encountered memory leak when failing to initialize
3944 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
3947 o Minor bugfixes (systemd):
3948 - Fix an accidental formatting error that broke the systemd
3949 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
3950 - Tor's systemd unit file no longer contains extraneous spaces.
3951 These spaces would sometimes confuse tools like deb-systemd-
3952 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
3954 o Minor bugfixes (tests):
3955 - Use the configured Python executable when running test-stem-full.
3956 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
3958 o Minor bugfixes (tests, also in 0.2.6.9):
3959 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
3960 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
3962 o Minor bugfixes (threads, comments):
3963 - Always initialize return value in compute_desc_id in rendcommon.c
3964 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
3965 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
3966 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
3967 - Remove undefined directive-in-macro in test_util_writepid clang
3968 3.7 complains that using a preprocessor directive inside a macro
3969 invocation in test_util_writepid in test_util.c is undefined.
3970 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
3972 o Code simplification and refactoring:
3973 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
3974 to ensure they remain consistent and visible everywhere.
3975 - Remove some vestigial workarounds for the MSVC6 compiler. We
3976 haven't supported that in ages.
3977 - The link authentication code has been refactored for better
3978 testability and reliability. It now uses code generated with the
3979 "trunnel" binary encoding generator, to reduce the risk of bugs
3980 due to programmer error. Done as part of ticket 12498.
3983 - Include a specific and (hopefully) accurate documentation of the
3984 torrc file's meta-format in doc/torrc_format.txt. This is mainly
3985 of interest to people writing programs to parse or generate torrc
3986 files. This document is not a commitment to long-term
3987 compatibility; some aspects of the current format are a bit
3988 ridiculous. Closes ticket 2325.
3991 - Tor no longer supports copies of OpenSSL that are missing support
3992 for Elliptic Curve Cryptography. (We began using ECC when
3993 available in 0.2.4.8-alpha, for more safe and efficient key
3994 negotiation.) In particular, support for at least one of P256 or
3995 P224 is now required, with manual configuration needed if only
3996 P224 is available. Resolves ticket 16140.
3997 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
3998 on an operating system that has not upgraded to OpenSSL 1.0 or
3999 later, and you compile Tor from source, you will need to install a
4000 more recent OpenSSL to link Tor against.) These versions of
4001 OpenSSL are still supported by the OpenSSL, but the numerous
4002 cryptographic improvements in later OpenSSL releases makes them a
4003 clear choice. Resolves ticket 16034.
4004 - Remove the HidServDirectoryV2 option. Now all relays offer to
4005 store hidden service descriptors. Related to 16543.
4006 - Remove the VoteOnHidServDirectoriesV2 option, since all
4007 authorities have long set it to 1. Closes ticket 16543.
4010 - Document use of coverity, clang static analyzer, and clang dynamic
4011 undefined behavior and address sanitizers in doc/HACKING. Include
4012 detailed usage instructions in the blacklist. Patch by "teor".
4013 Closes ticket 15817.
4014 - The link authentication protocol code now has extensive tests.
4015 - The relay descriptor signature testing code now has
4017 - The test_workqueue program now runs faster, and is enabled by
4018 default as a part of "make check".
4019 - Now that OpenSSL has its own scrypt implementation, add an unit
4020 test that checks for interoperability between libscrypt_scrypt()
4021 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
4022 and rely on EVP_PBE_scrypt() whenever possible. Resolves
4026 Changes in version 0.2.6.10 - 2015-07-12
4027 Tor version 0.2.6.10 fixes some significant stability and hidden
4028 service client bugs, bulletproofs the cryptography init process, and
4029 fixes a bug when using the sandbox code with some older versions of
4030 Linux. Everyone running an older version, especially an older version
4031 of 0.2.6, should upgrade.
4033 o Major bugfixes (hidden service clients, stability):
4034 - Stop refusing to store updated hidden service descriptors on a
4035 client. This reverts commit 9407040c59218 (which indeed fixed bug
4036 14219, but introduced a major hidden service reachability
4037 regression detailed in bug 16381). This is a temporary fix since
4038 we can live with the minor issue in bug 14219 (it just results in
4039 some load on the network) but the regression of 16381 is too much
4040 of a setback. First-round fix for bug 16381; bugfix
4043 o Major bugfixes (stability):
4044 - Stop crashing with an assertion failure when parsing certain kinds
4045 of malformed or truncated microdescriptors. Fixes bug 16400;
4046 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
4047 by "cypherpunks_backup".
4048 - Stop random client-side assertion failures that could occur when
4049 connecting to a busy hidden service, or connecting to a hidden
4050 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
4053 o Minor features (geoip):
4054 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
4055 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
4057 o Minor bugfixes (crypto error-handling):
4058 - Check for failures from crypto_early_init, and refuse to continue.
4059 A previous typo meant that we could keep going with an
4060 uninitialized crypto library, and would have OpenSSL initialize
4061 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
4062 when implementing ticket 4900. Patch by "teor".
4064 o Minor bugfixes (Linux seccomp2 sandbox):
4065 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
4066 these when eventfd2() support is missing. Fixes bug 16363; bugfix
4067 on 0.2.6.3-alpha. Patch from "teor".
4070 Changes in version 0.2.6.9 - 2015-06-11
4071 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
4072 requirements for receiving an HSDir flag, and addresses some other small
4073 bugs in the systemd and sandbox code. Clients using circuit isolation
4074 should upgrade; all directory authorities should upgrade.
4076 o Major bugfixes (client-side privacy):
4077 - Properly separate out each SOCKSPort when applying stream
4078 isolation. The error occurred because each port's session group was
4079 being overwritten by a default value when the listener connection
4080 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
4083 o Minor feature (directory authorities, security):
4084 - The HSDir flag given by authorities now requires the Stable flag.
4085 For the current network, this results in going from 2887 to 2806
4086 HSDirs. Also, it makes it harder for an attacker to launch a sybil
4087 attack by raising the effort for a relay to become Stable which
4088 takes at the very least 7 days to do so and by keeping the 96
4089 hours uptime requirement for HSDir. Implements ticket 8243.
4091 o Minor bugfixes (compilation):
4092 - Build with --enable-systemd correctly when libsystemd is
4093 installed, but systemd is not. Fixes bug 16164; bugfix on
4094 0.2.6.3-alpha. Patch from Peter Palfrader.
4096 o Minor bugfixes (Linux seccomp2 sandbox):
4097 - Fix sandboxing to work when running as a relaymby renaming of
4098 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
4099 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
4100 - Allow systemd connections to work with the Linux seccomp2 sandbox
4101 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
4104 o Minor bugfixes (tests):
4105 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
4106 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
4109 Changes in version 0.2.6.8 - 2015-05-21
4110 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
4111 fixes an authority-side bug in assigning the HSDir flag. All directory
4112 authorities should upgrade.
4114 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
4115 - Revert commit that made directory authorities assign the HSDir
4116 flag to relay without a DirPort; this was bad because such relays
4117 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
4120 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
4121 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
4122 a client authorized hidden service. Fixes bug 15823; bugfix
4125 o Minor features (geoip):
4126 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
4127 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
4131 Changes in version 0.2.7.1-alpha - 2015-05-12
4132 Tor 0.2.7.1-alpha is the first alpha release in its series. It
4133 includes numerous small features and bugfixes against previous Tor
4134 versions, and numerous small infrastructure improvements. The most
4135 notable features are several new ways for controllers to interact with
4136 the hidden services subsystem.
4138 o New system requirements:
4139 - Tor no longer includes workarounds to support Libevent versions
4140 before 1.3e. Libevent 2.0 or later is recommended. Closes
4143 o Major features (controller):
4144 - Add the ADD_ONION and DEL_ONION commands that allow the creation
4145 and management of hidden services via the controller. Closes
4147 - New "GETINFO onions/current" and "GETINFO onions/detached"
4148 commands to get information about hidden services created via the
4149 controller. Part of ticket 6411.
4150 - New HSFETCH command to launch a request for a hidden service
4151 descriptor. Closes ticket 14847.
4152 - New HSPOST command to upload a hidden service descriptor. Closes
4153 ticket 3523. Patch by "DonnchaC".
4155 o Major bugfixes (hidden services):
4156 - Revert commit that made directory authorities assign the HSDir
4157 flag to relay without a DirPort; this was bad because such relays
4158 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
4161 o Minor features (clock-jump tolerance):
4162 - Recover better when our clock jumps back many hours, like might
4163 happen for Tails or Whonix users who start with a very wrong
4164 hardware clock, use Tor to discover a more accurate time, and then
4165 fix their clock. Resolves part of ticket 8766.
4167 o Minor features (command-line interface):
4168 - Make --hash-password imply --hush to prevent unnecessary noise.
4169 Closes ticket 15542. Patch from "cypherpunks".
4170 - Print a warning whenever we find a relative file path being used
4171 as torrc option. Resolves issue 14018.
4173 o Minor features (controller):
4174 - Add DirAuthority lines for default directory authorities to the
4175 output of the "GETINFO config/defaults" command if not already
4176 present. Implements ticket 14840.
4177 - Controllers can now use "GETINFO hs/client/desc/id/..." to
4178 retrieve items from the client's hidden service descriptor cache.
4179 Closes ticket 14845.
4180 - Implement a new controller command "GETINFO status/fresh-relay-
4181 descs" to fetch a descriptor/extrainfo pair that was generated on
4182 demand just for the controller's use. Implements ticket 14784.
4184 o Minor features (DoS-resistance):
4185 - Make it harder for attackers to overload hidden services with
4186 introductions, by blocking multiple introduction requests on the
4187 same circuit. Resolves ticket 15515.
4189 o Minor features (geoip):
4190 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
4191 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
4194 o Minor features (HS popularity countermeasure):
4195 - To avoid leaking HS popularity, don't cycle the introduction point
4196 when we've handled a fixed number of INTRODUCE2 cells but instead
4197 cycle it when a random number of introductions is reached, thus
4198 making it more difficult for an attacker to find out the amount of
4199 clients that have used the introduction point for a specific HS.
4200 Closes ticket 15745.
4202 o Minor features (logging):
4203 - Include the Tor version in all LD_BUG log messages, since people
4204 tend to cut and paste those into the bugtracker. Implements
4207 o Minor features (pluggable transports):
4208 - When launching managed pluggable transports on Linux systems,
4209 attempt to have the kernel deliver a SIGTERM on tor exit if the
4210 pluggable transport process is still running. Resolves
4212 - When launching managed pluggable transports, setup a valid open
4213 stdin in the child process that can be used to detect if tor has
4214 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
4215 can be used by implementations to detect this new behavior.
4216 Resolves ticket 15435.
4218 o Minor features (testing):
4219 - Add a test to verify that the compiler does not eliminate our
4220 memwipe() implementation. Closes ticket 15377.
4221 - Add make rule `check-changes` to verify the format of changes
4222 files. Closes ticket 15180.
4223 - Add unit tests for control_event_is_interesting(). Add a compile-
4224 time check that the number of events doesn't exceed the capacity
4225 of control_event_t.event_mask. Closes ticket 15431, checks for
4226 bugs similar to 13085. Patch by "teor".
4227 - Command-line argument tests moved to Stem. Resolves ticket 14806.
4228 - Integrate the ntor, backtrace, and zero-length keys tests into the
4229 automake test suite. Closes ticket 15344.
4230 - Remove assertions during builds to determine Tor's test coverage.
4231 We don't want to trigger these even in assertions, so including
4232 them artificially makes our branch coverage look worse than it is.
4233 This patch provides the new test-stem-full and coverage-html-full
4234 configure options. Implements ticket 15400.
4236 o Minor bugfixes (build):
4237 - Improve out-of-tree builds by making non-standard rules work and
4238 clean up additional files and directories. Fixes bug 15053; bugfix
4241 o Minor bugfixes (command-line interface):
4242 - When "--quiet" is provided along with "--validate-config", do not
4243 write anything to stdout on success. Fixes bug 14994; bugfix
4245 - When complaining about bad arguments to "--dump-config", use
4248 o Minor bugfixes (configuration, unit tests):
4249 - Only add the default fallback directories when the DirAuthorities,
4250 AlternateDirAuthority, and FallbackDir directory config options
4251 are set to their defaults. The default fallback directory list is
4252 currently empty, this fix will only change tor's behavior when it
4253 has default fallback directories. Includes unit tests for
4254 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
4255 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
4257 o Minor bugfixes (correctness):
4258 - For correctness, avoid modifying a constant string in
4259 handle_control_postdescriptor. Fixes bug 15546; bugfix
4261 - Remove side-effects from tor_assert() calls. This was harmless,
4262 because we never disable assertions, but it is bad style and
4263 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
4266 o Minor bugfixes (hidden service):
4267 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
4268 a client authorized hidden service. Fixes bug 15823; bugfix
4270 - Remove an extraneous newline character from the end of hidden
4271 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
4273 o Minor bugfixes (interface):
4274 - Print usage information for --dump-config when it is used without
4275 an argument. Also, fix the error message to use different wording
4276 and add newline at the end. Fixes bug 15541; bugfix
4279 o Minor bugfixes (logs):
4280 - When building Tor under Clang, do not include an extra set of
4281 parentheses in log messages that include function names. Fixes bug
4282 15269; bugfix on every released version of Tor when compiled with
4283 recent enough Clang.
4285 o Minor bugfixes (network):
4286 - When attempting to use fallback technique for network interface
4287 lookup, disregard loopback and multicast addresses since they are
4288 unsuitable for public communications.
4290 o Minor bugfixes (statistics):
4291 - Disregard the ConnDirectionStatistics torrc options when Tor is
4292 not a relay since in that mode of operation no sensible data is
4293 being collected and because Tor might run into measurement hiccups
4294 when running as a client for some time, then becoming a relay.
4295 Fixes bug 15604; bugfix on 0.2.2.35.
4297 o Minor bugfixes (test networks):
4298 - When self-testing reachability, use ExtendAllowPrivateAddresses to
4299 determine if local/private addresses imply reachability. The
4300 previous fix used TestingTorNetwork, which implies
4301 ExtendAllowPrivateAddresses, but this excluded rare configurations
4302 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
4303 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
4304 issue discovered by CJ Ess.
4306 o Minor bugfixes (testing):
4307 - Check for matching value in server response in ntor_ref.py. Fixes
4308 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
4310 - Set the severity correctly when testing
4311 get_interface_addresses_ifaddrs() and
4312 get_interface_addresses_win32(), so that the tests fail gracefully
4313 instead of triggering an assertion. Fixes bug 15759; bugfix on
4314 0.2.6.3-alpha. Reported by Nicolas Derive.
4316 o Code simplification and refactoring:
4317 - Move the hacky fallback code out of get_interface_address6() into
4318 separate function and get it covered with unit-tests. Resolves
4320 - Refactor hidden service client-side cache lookup to intelligently
4321 report its various failure cases, and disentangle failure cases
4322 involving a lack of introduction points. Closes ticket 14391.
4323 - Use our own Base64 encoder instead of OpenSSL's, to allow more
4324 control over the output. Part of ticket 15652.
4327 - Improve the descriptions of statistics-related torrc options in
4328 the manpage to describe rationale and possible uses cases. Fixes
4330 - Improve the layout and formatting of ./configure --help messages.
4331 Closes ticket 15024. Patch from "cypherpunks".
4332 - Standardize on the term "server descriptor" in the manual page.
4333 Previously, we had used "router descriptor", "server descriptor",
4334 and "relay descriptor" interchangeably. Part of ticket 14987.
4337 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
4338 and always use the internal Base64 decoder. The internal decoder
4339 has been part of tor since 0.2.0.10-alpha, and no one should
4340 be using the OpenSSL one. Part of ticket 15652.
4341 - Remove the 'tor_strclear()' function; use memwipe() instead.
4342 Closes ticket 14922.
4345 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
4346 fingerprinting we now recommend pluggable transports; for forward-
4347 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
4348 - Remove the undocumented "--digests" command-line option. It
4349 complicated our build process, caused subtle build issues on
4350 multiple platforms, and is now redundant since we started
4351 including git version identifiers. Closes ticket 14742.
4352 - Tor no longer contains checks for ancient directory cache versions
4353 that didn't know about microdescriptors.
4354 - Tor no longer contains workarounds for stat files generated by
4355 super-old versions of Tor that didn't choose guards sensibly.
4358 Changes in version 0.2.4.27 - 2015-04-06
4359 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
4360 could be used by an attacker to crash hidden services, or crash clients
4361 visiting hidden services. Hidden services should upgrade as soon as
4362 possible; clients should upgrade whenever packages become available.
4364 This release also backports a simple improvement to make hidden
4365 services a bit less vulnerable to denial-of-service attacks.
4367 o Major bugfixes (security, hidden service):
4368 - Fix an issue that would allow a malicious client to trigger an
4369 assertion failure and halt a hidden service. Fixes bug 15600;
4370 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
4371 - Fix a bug that could cause a client to crash with an assertion
4372 failure when parsing a malformed hidden service descriptor. Fixes
4373 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
4375 o Minor features (DoS-resistance, hidden service):
4376 - Introduction points no longer allow multiple INTRODUCE1 cells to
4377 arrive on the same circuit. This should make it more expensive for
4378 attackers to overwhelm hidden services with introductions.
4379 Resolves ticket 15515.
4382 Changes in version 0.2.5.12 - 2015-04-06
4383 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
4384 could be used by an attacker to crash hidden services, or crash clients
4385 visiting hidden services. Hidden services should upgrade as soon as
4386 possible; clients should upgrade whenever packages become available.
4388 This release also backports a simple improvement to make hidden
4389 services a bit less vulnerable to denial-of-service attacks.
4391 o Major bugfixes (security, hidden service):
4392 - Fix an issue that would allow a malicious client to trigger an
4393 assertion failure and halt a hidden service. Fixes bug 15600;
4394 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
4395 - Fix a bug that could cause a client to crash with an assertion
4396 failure when parsing a malformed hidden service descriptor. Fixes
4397 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
4399 o Minor features (DoS-resistance, hidden service):
4400 - Introduction points no longer allow multiple INTRODUCE1 cells to
4401 arrive on the same circuit. This should make it more expensive for
4402 attackers to overwhelm hidden services with introductions.
4403 Resolves ticket 15515.
4406 Changes in version 0.2.6.7 - 2015-04-06
4407 Tor 0.2.6.7 fixes two security issues that could be used by an
4408 attacker to crash hidden services, or crash clients visiting hidden
4409 services. Hidden services should upgrade as soon as possible; clients
4410 should upgrade whenever packages become available.
4412 This release also contains two simple improvements to make hidden
4413 services a bit less vulnerable to denial-of-service attacks.
4415 o Major bugfixes (security, hidden service):
4416 - Fix an issue that would allow a malicious client to trigger an
4417 assertion failure and halt a hidden service. Fixes bug 15600;
4418 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
4419 - Fix a bug that could cause a client to crash with an assertion
4420 failure when parsing a malformed hidden service descriptor. Fixes
4421 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
4423 o Minor features (DoS-resistance, hidden service):
4424 - Introduction points no longer allow multiple INTRODUCE1 cells to
4425 arrive on the same circuit. This should make it more expensive for
4426 attackers to overwhelm hidden services with introductions.
4427 Resolves ticket 15515.
4428 - Decrease the amount of reattempts that a hidden service performs
4429 when its rendezvous circuits fail. This reduces the computational
4430 cost for running a hidden service under heavy load. Resolves
4434 Changes in version 0.2.6.6 - 2015-03-24
4435 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
4437 It adds numerous safety, security, correctness, and performance
4438 improvements. Client programs can be configured to use more kinds of
4439 sockets, AutomapHosts works better, the multithreading backend is
4440 improved, cell transmission is refactored, test coverage is much
4441 higher, more denial-of-service attacks are handled, guard selection is
4442 improved to handle long-term guards better, pluggable transports
4443 should work a bit better, and some annoying hidden service performance
4444 bugs should be addressed.
4446 o Minor bugfixes (portability):
4447 - Use the correct datatype in the SipHash-2-4 function to prevent
4448 compilers from assuming any sort of alignment. Fixes bug 15436;
4449 bugfix on 0.2.5.3-alpha.
4451 Changes in version 0.2.6.5-rc - 2015-03-18
4452 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
4453 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
4455 o Major bugfixes (client):
4456 - Avoid crashing when making certain configuration option changes on
4457 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
4460 o Major bugfixes (pluggable transports):
4461 - Initialize the extended OR Port authentication cookie before
4462 launching pluggable transports. This prevents a race condition
4463 that occured when server-side pluggable transports would cache the
4464 authentication cookie before it has been (re)generated. Fixes bug
4465 15240; bugfix on 0.2.5.1-alpha.
4467 o Major bugfixes (portability):
4468 - Do not crash on startup when running on Solaris. Fixes a bug
4469 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
4472 o Minor features (heartbeat):
4473 - On relays, report how many connections we negotiated using each
4474 version of the Tor link protocols. This information will let us
4475 know if removing support for very old versions of the Tor
4476 protocols is harming the network. Closes ticket 15212.
4478 o Code simplification and refactoring:
4479 - Refactor main loop to extract the 'loop' part. This makes it
4480 easier to run Tor under Shadow. Closes ticket 15176.
4483 Changes in version 0.2.5.11 - 2015-03-17
4484 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
4486 It backports several bugfixes from the 0.2.6 branch, including a
4487 couple of medium-level security fixes for relays and exit nodes.
4488 It also updates the list of directory authorities.
4490 o Directory authority changes:
4491 - Remove turtles as a directory authority.
4492 - Add longclaw as a new (v3) directory authority. This implements
4493 ticket 13296. This keeps the directory authority count at 9.
4494 - The directory authority Faravahar has a new IP address. This
4495 closes ticket 14487.
4497 o Major bugfixes (crash, OSX, security):
4498 - Fix a remote denial-of-service opportunity caused by a bug in
4499 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
4502 o Major bugfixes (relay, stability, possible security):
4503 - Fix a bug that could lead to a relay crashing with an assertion
4504 failure if a buffer of exactly the wrong layout was passed to
4505 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
4506 0.2.0.10-alpha. Patch from 'cypherpunks'.
4507 - Do not assert if the 'data' pointer on a buffer is advanced to the
4508 very end of the buffer; log a BUG message instead. Only assert if
4509 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
4511 o Major bugfixes (exit node stability):
4512 - Fix an assertion failure that could occur under high DNS load.
4513 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
4514 diagnosed and fixed by "cypherpunks".
4516 o Major bugfixes (Linux seccomp2 sandbox):
4517 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
4518 crash during attempts to call wait4. Fixes bug 15088; bugfix on
4519 0.2.5.1-alpha. Patch from "sanic".
4521 o Minor features (controller):
4522 - New "GETINFO bw-event-cache" to get information about recent
4523 bandwidth events. Closes ticket 14128. Useful for controllers to
4524 get recent bandwidth history after the fix for ticket 13988.
4526 o Minor features (geoip):
4527 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
4528 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
4531 o Minor bugfixes (client, automapping):
4532 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
4533 no value follows the option. Fixes bug 14142; bugfix on
4534 0.2.4.7-alpha. Patch by "teor".
4535 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
4536 14195; bugfix on 0.1.0.1-rc.
4538 o Minor bugfixes (compilation):
4539 - Build without warnings with the stock OpenSSL srtp.h header, which
4540 has a duplicate declaration of SSL_get_selected_srtp_profile().
4541 Fixes bug 14220; this is OpenSSL's bug, not ours.
4543 o Minor bugfixes (directory authority):
4544 - Allow directory authorities to fetch more data from one another if
4545 they find themselves missing lots of votes. Previously, they had
4546 been bumping against the 10 MB queued data limit. Fixes bug 14261;
4547 bugfix on 0.1.2.5-alpha.
4548 - Enlarge the buffer to read bwauth generated files to avoid an
4549 issue when parsing the file in dirserv_read_measured_bandwidths().
4550 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
4552 o Minor bugfixes (statistics):
4553 - Increase period over which bandwidth observations are aggregated
4554 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
4556 o Minor bugfixes (preventative security, C safety):
4557 - When reading a hexadecimal, base-32, or base-64 encoded value from
4558 a string, always overwrite the whole output buffer. This prevents
4559 some bugs where we would look at (but fortunately, not reveal)
4560 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
4564 Changes in version 0.2.4.26 - 2015-03-17
4565 Tor 0.2.4.26 includes an updated list of directory authorities. It
4566 also backports a couple of stability and security bugfixes from 0.2.5
4569 o Directory authority changes:
4570 - Remove turtles as a directory authority.
4571 - Add longclaw as a new (v3) directory authority. This implements
4572 ticket 13296. This keeps the directory authority count at 9.
4573 - The directory authority Faravahar has a new IP address. This
4574 closes ticket 14487.
4576 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
4577 - Fix an assertion failure that could occur under high DNS load.
4578 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
4579 diagnosed and fixed by "cypherpunks".
4581 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
4582 - Fix a bug that could lead to a relay crashing with an assertion
4583 failure if a buffer of exactly the wrong layout was passed to
4584 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
4585 0.2.0.10-alpha. Patch from 'cypherpunks'.
4586 - Do not assert if the 'data' pointer on a buffer is advanced to the
4587 very end of the buffer; log a BUG message instead. Only assert if
4588 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
4590 o Minor features (geoip):
4591 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
4592 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
4595 Changes in version 0.2.6.4-rc - 2015-03-09
4596 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
4597 attacker might be able to use in order to crash certain Tor
4598 directories. It also resolves some minor issues left over from, or
4599 introduced in, Tor 0.2.6.3-alpha or earlier.
4601 o Major bugfixes (crash, OSX, security):
4602 - Fix a remote denial-of-service opportunity caused by a bug in
4603 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
4606 o Major bugfixes (relay, stability, possible security):
4607 - Fix a bug that could lead to a relay crashing with an assertion
4608 failure if a buffer of exactly the wrong layout is passed to
4609 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
4610 0.2.0.10-alpha. Patch from "cypherpunks".
4611 - Do not assert if the 'data' pointer on a buffer is advanced to the
4612 very end of the buffer; log a BUG message instead. Only assert if
4613 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
4615 o Major bugfixes (FreeBSD IPFW transparent proxy):
4616 - Fix address detection with FreeBSD transparent proxies, when
4617 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
4620 o Major bugfixes (Linux seccomp2 sandbox):
4621 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
4622 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
4624 - Allow AF_UNIX hidden services to be used with the seccomp2
4625 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
4626 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
4627 crash during attempts to call wait4. Fixes bug 15088; bugfix on
4628 0.2.5.1-alpha. Patch from "sanic".
4630 o Minor features (controller):
4631 - Messages about problems in the bootstrap process now include
4632 information about the server we were trying to connect to when we
4633 noticed the problem. Closes ticket 15006.
4635 o Minor features (geoip):
4636 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
4637 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
4640 o Minor features (logs):
4641 - Quiet some log messages in the heartbeat and at startup. Closes
4644 o Minor bugfixes (certificate handling):
4645 - If an authority operator accidentally makes a signing certificate
4646 with a future publication time, do not discard its real signing
4647 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
4648 - Remove any old authority certificates that have been superseded
4649 for at least two days. Previously, we would keep superseded
4650 certificates until they expired, if they were published close in
4651 time to the certificate that superseded them. Fixes bug 11454;
4652 bugfix on 0.2.1.8-alpha.
4654 o Minor bugfixes (compilation):
4655 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
4657 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
4660 o Minor bugfixes (testing):
4661 - Fix endianness issues in unit test for resolve_my_address() to
4662 have it pass on big endian systems. Fixes bug 14980; bugfix on
4664 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
4665 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
4666 - When running the new 'make test-stem' target, use the configured
4667 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
4669 - When running the zero-length-keys tests, do not use the default
4670 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
4673 o Directory authority IP change:
4674 - The directory authority Faravahar has a new IP address. This
4675 closes ticket 14487.
4678 - Remove some lingering dead code that once supported mempools.
4679 Mempools were disabled by default in 0.2.5, and removed entirely
4680 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
4684 Changes in version 0.2.6.3-alpha - 2015-02-19
4685 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
4686 the 0.2.6.x series. It introduces support for more kinds of sockets,
4687 makes it harder to accidentally run an exit, improves our
4688 multithreading backend, incorporates several fixes for the
4689 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
4691 If no major regressions or security holes are found in this version,
4692 the next version will be a release candidate.
4694 o Deprecated versions:
4695 - Tor relays older than 0.2.4.18-rc are no longer allowed to
4696 advertise themselves on the network. Closes ticket 13555.
4698 o Major features (security, unix domain sockets):
4699 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
4700 applications can reach Tor without having to create AF_INET or
4701 AF_INET6 sockets, meaning they can completely disable their
4702 ability to make non-Tor network connections. To create a socket of
4703 this type, use "SocksPort unix:/path/to/socket". Implements
4705 - Support mapping hidden service virtual ports to AF_UNIX sockets.
4706 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
4707 Implements ticket 11485.
4709 o Major features (changed defaults):
4710 - Prevent relay operators from unintentionally running exits: When a
4711 relay is configured as an exit node, we now warn the user unless
4712 the "ExitRelay" option is set to 1. We warn even more loudly if
4713 the relay is configured with the default exit policy, since this
4714 can indicate accidental misconfiguration. Setting "ExitRelay 0"
4715 stops Tor from running as an exit relay. Closes ticket 10067.
4717 o Major features (directory system):
4718 - When downloading server- or microdescriptors from a directory
4719 server, we no longer launch multiple simultaneous requests to the
4720 same server. This reduces load on the directory servers,
4721 especially when directory guards are in use. Closes ticket 9969.
4722 - When downloading server- or microdescriptors over a tunneled
4723 connection, do not limit the length of our requests to what the
4724 Squid proxy is willing to handle. Part of ticket 9969.
4725 - Authorities can now vote on the correct digests and latest
4726 versions for different software packages. This allows packages
4727 that include Tor to use the Tor authority system as a way to get
4728 notified of updates and their correct digests. Implements proposal
4729 227. Closes ticket 10395.
4731 o Major features (guards):
4732 - Introduce the Guardfraction feature to improves load balancing on
4733 guard nodes. Specifically, it aims to reduce the traffic gap that
4734 guard nodes experience when they first get the Guard flag. This is
4735 a required step if we want to increase the guard lifetime to 9
4736 months or greater. Closes ticket 9321.
4738 o Major features (performance):
4739 - Make the CPU worker implementation more efficient by avoiding the
4740 kernel and lengthening pipelines. The original implementation used
4741 sockets to transfer data from the main thread to the workers, and
4742 didn't allow any thread to be assigned more than a single piece of
4743 work at once. The new implementation avoids communications
4744 overhead by making requests in shared memory, avoiding kernel IO
4745 where possible, and keeping more requests in flight at once.
4746 Implements ticket 9682.
4748 o Major features (relay):
4749 - Raise the minimum acceptable configured bandwidth rate for bridges
4750 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
4751 20 KiB/sec.) Closes ticket 13822.
4753 o Major bugfixes (exit node stability):
4754 - Fix an assertion failure that could occur under high DNS load.
4755 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
4756 diagnosed and fixed by "cypherpunks".
4758 o Major bugfixes (mixed relay-client operation):
4759 - When running as a relay and client at the same time (not
4760 recommended), if we decide not to use a new guard because we want
4761 to retry older guards, only close the locally-originating circuits
4762 passing through that guard. Previously we would close all the
4763 circuits through that guard. Fixes bug 9819; bugfix on
4764 0.2.1.1-alpha. Reported by "skruffy".
4766 o Minor features (build):
4767 - New --disable-system-torrc compile-time option to prevent Tor from
4768 looking for the system-wide torrc or torrc-defaults files.
4769 Resolves ticket 13037.
4771 o Minor features (controller):
4772 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
4773 events so controllers can observe circuit isolation inputs. Closes
4775 - ControlPort now supports the unix:/path/to/socket syntax as an
4776 alternative to the ControlSocket option, for consistency with
4777 SocksPort and HiddenServicePort. Closes ticket 14451.
4778 - New "GETINFO bw-event-cache" to get information about recent
4779 bandwidth events. Closes ticket 14128. Useful for controllers to
4780 get recent bandwidth history after the fix for ticket 13988.
4782 o Minor features (Denial of service resistance):
4783 - Count the total number of bytes used storing hidden service
4784 descriptors against the value of MaxMemInQueues. If we're low on
4785 memory, and more than 20% of our memory is used holding hidden
4786 service descriptors, free them until no more than 10% of our
4787 memory holds hidden service descriptors. Free the least recently
4788 fetched descriptors first. Resolves ticket 13806.
4789 - When we have recently been under memory pressure (over 3/4 of
4790 MaxMemInQueues is allocated), then allocate smaller zlib objects
4791 for small requests. Closes ticket 11791.
4793 o Minor features (geoip):
4794 - Update geoip and geoip6 files to the January 7 2015 Maxmind
4795 GeoLite2 Country database.
4797 o Minor features (guard nodes):
4798 - Reduce the time delay before saving guard status to disk from 10
4799 minutes to 30 seconds (or from one hour to 10 minutes if
4800 AvoidDiskWrites is set). Closes ticket 12485.
4802 o Minor features (hidden service):
4803 - Make Sybil attacks against hidden services harder by changing the
4804 minimum time required to get the HSDir flag from 25 hours up to 96
4805 hours. Addresses ticket 14149.
4806 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
4807 services to disable the anti-scanning feature introduced in
4808 0.2.6.2-alpha. With this option not set, a connection to an
4809 unlisted port closes the circuit. With this option set, only a
4810 RELAY_DONE cell is sent. Closes ticket 14084.
4812 o Minor features (interface):
4813 - Implement "-f -" command-line option to read torrc configuration
4814 from standard input, if you don't want to store the torrc file in
4815 the file system. Implements feature 13865.
4817 o Minor features (logging):
4818 - Add a count of unique clients to the bridge heartbeat message.
4819 Resolves ticket 6852.
4820 - Suppress "router info incompatible with extra info" message when
4821 reading extrainfo documents from cache. (This message got loud
4822 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
4824 - Elevate hidden service authorized-client message from DEBUG to
4825 INFO. Closes ticket 14015.
4827 o Minor features (stability):
4828 - Add assertions in our hash-table iteration code to check for
4829 corrupted values that could cause infinite loops. Closes
4832 o Minor features (systemd):
4833 - Various improvements and modernizations in systemd hardening
4834 support. Closes ticket 13805. Patch from Craig Andrews.
4836 o Minor features (testing networks):
4837 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
4838 and the default on a testing network to 2 minutes. Drop the
4839 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
4840 keep the default on a testing network at 30 seconds. This reduces
4841 HS bootstrap time to around 25 seconds. Also, change the default
4842 time in test-network.sh to match. Closes ticket 13401. Patch
4844 - Create TestingDirAuthVoteHSDir to correspond to
4845 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
4846 HSDir flag for the listed relays regardless of uptime or ORPort
4847 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
4848 Partial implementation for ticket 14067. Patch by "teor".
4850 o Minor features (tor2web mode):
4851 - Introduce the config option Tor2webRendezvousPoints, which allows
4852 clients in Tor2webMode to select a specific Rendezvous Point to be
4853 used in HS circuits. This might allow better performance for
4854 Tor2Web nodes. Implements ticket 12844.
4856 o Minor bugfixes (client DNS):
4857 - Report the correct cached DNS expiration times on SOCKS port or in
4858 DNS replies. Previously, we would report everything as "never
4859 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
4860 - Avoid a small memory leak when we find a cached answer for a
4861 reverse DNS lookup in a client-side DNS cache. (Remember, client-
4862 side DNS caching is off by default, and is not recommended.) Fixes
4863 bug 14259; bugfix on 0.2.0.1-alpha.
4865 o Minor bugfixes (client, automapping):
4866 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
4867 no value follows the option. Fixes bug 14142; bugfix on
4868 0.2.4.7-alpha. Patch by "teor".
4869 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
4870 14195; bugfix on 0.1.0.1-rc.
4871 - Prevent changes to other options from removing the wildcard value
4872 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
4874 - Allow MapAddress and AutomapHostsOnResolve to work together when
4875 an address is mapped into another address type (like .onion) that
4876 must be automapped at resolve time. Fixes bug 7555; bugfix
4879 o Minor bugfixes (client, bridges):
4880 - When we are using bridges and we had a network connectivity
4881 problem, only retry connecting to our currently configured
4882 bridges, not all bridges we know about and remember using. Fixes
4883 bug 14216; bugfix on 0.2.2.17-alpha.
4885 o Minor bugfixes (client, IPv6):
4886 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
4887 flag is not set; and not because the NoIPv4Traffic flag was set.
4888 Previously we'd looked at the NoIPv4Traffic flag for both types of
4889 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
4891 o Minor bugfixes (compilation):
4892 - The address of an array in the middle of a structure will always
4893 be non-NULL. clang recognises this and complains. Disable the
4894 tautologous and redundant check to silence this warning. Fixes bug
4895 14001; bugfix on 0.2.1.2-alpha.
4896 - Avoid warnings when building with systemd 209 or later. Fixes bug
4897 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
4898 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
4899 Addresses ticket 14188.
4900 - Build without warnings with the stock OpenSSL srtp.h header, which
4901 has a duplicate declaration of SSL_get_selected_srtp_profile().
4902 Fixes bug 14220; this is OpenSSL's bug, not ours.
4903 - Do not compile any code related to Tor2Web mode when Tor2Web mode
4904 is not enabled at compile time. Previously, this code was included
4905 in a disabled state. See discussion on ticket 12844.
4906 - Remove the --disable-threads configure option again. It was
4907 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
4908 14819; bugfix on 0.2.6.2-alpha.
4910 o Minor bugfixes (controller):
4911 - Report "down" in response to the "GETINFO entry-guards" command
4912 when relays are down with an unreachable_since value. Previously,
4913 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
4914 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
4915 14116; bugfix on 0.2.2.9-alpha.
4916 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
4917 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
4919 o Minor bugfixes (directory authority):
4920 - Allow directory authorities to fetch more data from one another if
4921 they find themselves missing lots of votes. Previously, they had
4922 been bumping against the 10 MB queued data limit. Fixes bug 14261;
4923 bugfix on 0.1.2.5-alpha.
4924 - Do not attempt to download extrainfo documents which we will be
4925 unable to validate with a matching server descriptor. Fixes bug
4926 13762; bugfix on 0.2.0.1-alpha.
4927 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
4928 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
4929 - Enlarge the buffer to read bwauth generated files to avoid an
4930 issue when parsing the file in dirserv_read_measured_bandwidths().
4931 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
4933 o Minor bugfixes (file handling):
4934 - Stop failing when key files are zero-length. Instead, generate new
4935 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
4936 on all versions of Tor. Patch by "teor".
4937 - Stop generating a fresh .old RSA onion key file when the .old file
4938 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
4939 - Avoid overwriting .old key files with empty key files.
4940 - Skip loading zero-length extrainfo store, router store, stats,
4941 state, and key files.
4942 - Avoid crashing when trying to reload a torrc specified as a
4943 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
4946 o Minor bugfixes (hidden services):
4947 - Close the introduction circuit when we have no more usable intro
4948 points, instead of waiting for it to time out. This also ensures
4949 that no follow-up HS descriptor fetch is triggered when the
4950 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
4951 - When fetching a hidden service descriptor for a down service that
4952 was recently up, do not keep refetching until we try the same
4953 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
4954 - Successfully launch Tor with a nonexistent hidden service
4955 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
4956 14106; bugfix on 0.2.6.2-alpha.
4958 o Minor bugfixes (logging):
4959 - Avoid crashing when there are more log domains than entries in
4960 domain_list. Bugfix on 0.2.3.1-alpha.
4961 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
4963 - Don't log messages to stdout twice when starting up. Fixes bug
4964 13993; bugfix on 0.2.6.1-alpha.
4966 o Minor bugfixes (parsing):
4967 - Stop accepting milliseconds (or other junk) at the end of
4968 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
4969 - Support two-number and three-number version numbers correctly, in
4970 case we change the Tor versioning system in the future. Fixes bug
4971 13661; bugfix on 0.0.8pre1.
4973 o Minor bugfixes (path counting):
4974 - When deciding whether the consensus lists any exit nodes, count
4975 the number listed in the consensus, not the number we have
4976 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
4977 - When deciding whether we have any exit nodes, only examine
4978 ExitNodes when the ExitNodes option is actually set. Fixes part of
4979 bug 14918; bugfix on 0.2.6.2-alpha.
4980 - Get rid of redundant and possibly scary warnings that we are
4981 missing directory information while we bootstrap. Fixes part of
4982 bug 14918; bugfix on 0.2.6.2-alpha.
4984 o Minor bugfixes (portability):
4985 - Fix the ioctl()-based network interface lookup code so that it
4986 will work on systems that have variable-length struct ifreq, for
4988 - Fix scheduler compilation on targets where char is unsigned. Fixes
4989 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
4991 o Minor bugfixes (sandbox):
4992 - Allow glibc fatal errors to be sent to stderr before Tor exits.
4993 Previously, glibc would try to write them to /dev/tty, and the
4994 sandbox would trap the call and make Tor exit prematurely. Fixes
4995 bug 14759; bugfix on 0.2.5.1-alpha.
4997 o Minor bugfixes (shutdown):
4998 - When shutting down, always call event_del() on lingering read or
4999 write events before freeing them. Otherwise, we risk double-frees
5000 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
5003 o Minor bugfixes (small memory leaks):
5004 - Avoid leaking memory when using IPv6 virtual address mappings.
5005 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
5008 o Minor bugfixes (statistics):
5009 - Increase period over which bandwidth observations are aggregated
5010 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
5012 o Minor bugfixes (systemd support):
5013 - Fix detection and operation of systemd watchdog. Fixes part of bug
5014 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
5015 - Run correctly under systemd with the RunAsDaemon option set. Fixes
5016 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
5017 - Inform the systemd supervisor about more changes in the Tor
5018 process status. Implements part of ticket 14141. Patch from
5020 - Cause the "--disable-systemd" option to actually disable systemd
5021 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
5024 o Minor bugfixes (TLS):
5025 - Check more thoroughly throughout the TLS code for possible
5026 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
5028 o Minor bugfixes (transparent proxy):
5029 - Use getsockname, not getsockopt, to retrieve the address for a
5030 TPROXY-redirected connection. Fixes bug 13796; bugfix
5033 o Code simplification and refactoring:
5034 - Move fields related to isolating and configuring client ports into
5035 a shared structure. Previously, they were duplicated across
5036 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
5037 to copy them correctly had been the cause of at least one bug in
5038 the past. Closes ticket 8546.
5039 - Refactor the get_interface_addresses_raw() doom-function into
5040 multiple smaller and simpler subfunctions. Cover the resulting
5041 subfunctions with unit-tests. Fixes a significant portion of
5043 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
5044 only for version <= 0.2.2.24 which is now deprecated. Closes
5046 - Remove a test for a long-defunct broken version-one
5050 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
5051 for writing the OpenBSD-specific tips. Resolves ticket 13702.
5052 - Make the tor-resolve documentation match its help string and its
5053 options. Resolves part of ticket 14325.
5054 - Log a more useful error message from tor-resolve when failing to
5055 look up a hidden service address. Resolves part of ticket 14325.
5057 o Downgraded warnings:
5058 - Don't warn when we've attempted to contact a relay using the wrong
5059 ntor onion key. Closes ticket 9635.
5062 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
5063 longer silently accepted as an alias for "ExitNodes".
5064 - The --enable-mempool and --enable-buf-freelists options, which
5065 were originally created to work around bad malloc implementations,
5066 no longer exist. They were off-by-default in 0.2.5. Closes
5070 - Make the checkdir/perms test complete successfully even if the
5071 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
5072 - Test that tor does not fail when key files are zero-length. Check
5073 that tor generates new keys, and overwrites the empty key files.
5074 - Test that tor generates new keys when keys are missing
5075 (existing behavior).
5076 - Test that tor does not overwrite key files that already contain
5077 data (existing behavior). Tests bug 13111. Patch by "teor".
5078 - New "make test-stem" target to run stem integration tests.
5079 Requires that the "STEM_SOURCE_DIR" environment variable be set.
5080 Closes ticket 14107.
5081 - Make the test_cmdline_args.py script work correctly on Windows.
5082 Patch from Gisle Vanem.
5083 - Move the slower unit tests into a new "./src/test/test-slow"
5084 binary that can be run independently of the other tests. Closes
5086 - Avoid undefined behavior when sampling huge values from the
5087 Laplace distribution. This made unittests fail on Raspberry Pi.
5088 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
5091 Changes in version 0.2.6.2-alpha - 2014-12-31
5092 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
5093 It introduces a major new backend for deciding when to send cells on
5094 channels, which should lead down the road to big performance
5095 increases. It contains security and statistics features for better
5096 work on hidden services, and numerous bugfixes.
5098 This release contains many new unit tests, along with major
5099 performance improvements for running testing networks using Chutney.
5100 Thanks to a series of patches contributed by "teor", testing networks
5101 should now bootstrap in seconds, rather than minutes.
5103 o Major features (relay, infrastructure):
5104 - Complete revision of the code that relays use to decide which cell
5105 to send next. Formerly, we selected the best circuit to write on
5106 each channel, but we didn't select among channels in any
5107 sophisticated way. Now, we choose the best circuits globally from
5108 among those whose channels are ready to deliver traffic.
5110 This patch implements a new inter-cmux comparison API, a global
5111 high/low watermark mechanism and a global scheduler loop for
5112 transmission prioritization across all channels as well as among
5113 circuits on one channel. This schedule is currently tuned to
5114 (tolerantly) avoid making changes in network performance, but it
5115 should form the basis for major circuit performance increases in
5116 the future. Code by Andrea; tuning by Rob Jansen; implements
5119 o Major features (hidden services):
5120 - Make HS port scanning more difficult by immediately closing the
5121 circuit when a user attempts to connect to a nonexistent port.
5122 Closes ticket 13667.
5123 - Add a HiddenServiceStatistics option that allows Tor relays to
5124 gather and publish statistics about the overall size and volume of
5125 hidden service usage. Specifically, when this option is turned on,
5126 an HSDir will publish an approximate number of hidden services
5127 that have published descriptors to it the past 24 hours. Also, if
5128 a relay has acted as a hidden service rendezvous point, it will
5129 publish the approximate amount of rendezvous cells it has relayed
5130 the past 24 hours. The statistics themselves are obfuscated so
5131 that the exact values cannot be derived. For more details see
5132 proposal 238, "Better hidden service stats from Tor relays". This
5133 feature is currently disabled by default. Implements feature 13192.
5135 o Major bugfixes (client, automap):
5136 - Repair automapping with IPv6 addresses. This automapping should
5137 have worked previously, but one piece of debugging code that we
5138 inserted to detect a regression actually caused the regression to
5139 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
5140 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
5143 o Major bugfixes (hidden services):
5144 - When closing an introduction circuit that was opened in parallel
5145 with others, don't mark the introduction point as unreachable.
5146 Previously, the first successful connection to an introduction
5147 point would make the other introduction points get marked as
5148 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
5150 o Directory authority changes:
5151 - Remove turtles as a directory authority.
5152 - Add longclaw as a new (v3) directory authority. This implements
5153 ticket 13296. This keeps the directory authority count at 9.
5155 o Major removed features:
5156 - Tor clients no longer support connecting to hidden services
5157 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
5158 option has been removed. (There shouldn't be any hidden services
5159 running these versions on the network.) Closes ticket 7803.
5161 o Minor features (client):
5162 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
5163 is enabled, reject requests with IP addresses as hostnames.
5164 Resolves ticket 13315.
5166 o Minor features (controller):
5167 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
5168 write an unscheduled heartbeat message to the log. Implements
5171 o Minor features (geoip):
5172 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
5175 o Minor features (hidden services):
5176 - When re-enabling the network, don't try to build introduction
5177 circuits until we have successfully built a circuit. This makes
5178 hidden services come up faster when the network is re-enabled.
5179 Patch from "akwizgran". Closes ticket 13447.
5180 - When we fail to retrieve a hidden service descriptor, send the
5181 controller an "HS_DESC FAILED" controller event. Implements
5183 - New HiddenServiceDirGroupReadable option to cause hidden service
5184 directories and hostname files to be created group-readable. Patch
5185 from "anon", David Stainton, and "meejah". Closes ticket 11291.
5187 o Minor features (systemd):
5188 - Where supported, when running with systemd, report successful
5189 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
5190 - When running with systemd, support systemd watchdog messages. Part
5191 of ticket 11016. Patch by Michael Scherer.
5193 o Minor features (transparent proxy):
5194 - Update the transparent proxy option checks to allow for both ipfw
5195 and pf on OS X. Closes ticket 14002.
5196 - Use the correct option when using IPv6 with transparent proxy
5197 support on Linux. Resolves 13808. Patch by Francisco Blas
5200 o Minor bugfixes (preventative security, C safety):
5201 - When reading a hexadecimal, base-32, or base-64 encoded value from
5202 a string, always overwrite the whole output buffer. This prevents
5203 some bugs where we would look at (but fortunately, not reveal)
5204 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
5206 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
5207 just the part that's used. This makes it harder for data leak bugs
5208 to occur in the event of other programming failures. Resolves
5211 o Minor bugfixes (client, microdescriptors):
5212 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
5213 computing which microdescriptors to download. This keeps us from
5214 erroneous download behavior if two microdescriptor digests ever
5215 have the same first 160 bits. Fixes part of bug 13399; bugfix
5217 - Reset a router's status if its microdescriptor digest changes,
5218 even if the first 160 bits remain the same. Fixes part of bug
5219 13399; bugfix on 0.2.3.1-alpha.
5221 o Minor bugfixes (compilation):
5222 - Silence clang warnings under --enable-expensive-hardening,
5223 including implicit truncation of 64 bit values to 32 bit, const
5224 char assignment to self, tautological compare, and additional
5225 parentheses around equality tests. Fixes bug 13577; bugfix
5227 - Fix a clang warning about checking whether an address in the
5228 middle of a structure is NULL. Fixes bug 14001; bugfix
5231 o Minor bugfixes (hidden services):
5232 - Correctly send a controller event when we find that a rendezvous
5233 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
5234 - Pre-check directory permissions for new hidden-services to avoid
5235 at least one case of "Bug: Acting on config options left us in a
5236 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
5237 - When adding a new hidden service (for example, via SETCONF), Tor
5238 no longer congratulates the user for running a relay. Fixes bug
5239 13941; bugfix on 0.2.6.1-alpha.
5240 - When fetching hidden service descriptors, we now check not only
5241 for whether we got the hidden service we had in mind, but also
5242 whether we got the particular descriptors we wanted. This prevents
5243 a class of inefficient but annoying DoS attacks by hidden service
5244 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
5247 o Minor bugfixes (Linux seccomp2 sandbox):
5248 - Make transparent proxy support work along with the seccomp2
5249 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
5250 by Francisco Blas Izquierdo Riera.
5251 - Fix a memory leak in tor-resolve when running with the sandbox
5252 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
5254 o Minor bugfixes (logging):
5255 - Downgrade warnings about RSA signature failures to info log level.
5256 Emit a warning when an extra info document is found incompatible
5257 with a corresponding router descriptor. Fixes bug 9812; bugfix
5259 - Make connection_ap_handshake_attach_circuit() log the circuit ID
5260 correctly. Fixes bug 13701; bugfix on 0.0.6.
5262 o Minor bugfixes (misc):
5263 - Stop allowing invalid address patterns like "*/24" that contain
5264 both a wildcard address and a bit prefix length. This affects all
5265 our address-range parsing code. Fixes bug 7484; bugfix
5268 o Minor bugfixes (testing networks, fast startup):
5269 - Allow Tor to build circuits using a consensus with no exits. If
5270 the consensus has no exits (typical of a bootstrapping test
5271 network), allow Tor to build circuits once enough descriptors have
5272 been downloaded. This assists in bootstrapping a testing Tor
5273 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
5275 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
5276 header to directory servers. This allows us to obtain consensuses
5277 promptly when the consensus interval is very short. This assists
5278 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
5279 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
5280 - Stop assuming that private addresses are local when checking
5281 reachability in a TestingTorNetwork. Instead, when testing, assume
5282 all OR connections are remote. (This is necessary due to many test
5283 scenarios running all relays on localhost.) This assists in
5284 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
5285 0.1.0.1-rc. Patch by "teor".
5286 - Avoid building exit circuits from a consensus with no exits. Now
5287 thanks to our fix for 13718, we accept a no-exit network as not
5288 wholly lost, but we need to remember not to try to build exit
5289 circuits on it. Closes ticket 13814; patch by "teor".
5290 - Stop requiring exits to have non-zero bandwithcapacity in a
5291 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
5292 ignore exit bandwidthcapacity. This assists in bootstrapping a
5293 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
5294 on 0.2.0.3-alpha. Patch by "teor".
5295 - Add "internal" to some bootstrap statuses when no exits are
5296 available. If the consensus does not contain Exits, Tor will only
5297 build internal circuits. In this case, relevant statuses will
5298 contain the word "internal" as indicated in the Tor control-
5299 spec.txt. When bootstrap completes, Tor will be ready to build
5300 internal circuits. If a future consensus contains Exits, exit
5301 circuits may become available. Fixes part of bug 13718; bugfix on
5302 0.2.4.10-alpha. Patch by "teor".
5303 - Decrease minimum consensus interval to 10 seconds when
5304 TestingTorNetwork is set, or 5 seconds for the first consensus.
5305 Fix assumptions throughout the code that assume larger intervals.
5306 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
5308 - Avoid excluding guards from path building in minimal test
5309 networks, when we're in a test network and excluding guards would
5310 exclude all relays. This typically occurs in incredibly small tor
5311 networks, and those using "TestingAuthVoteGuard *". Fixes part of
5312 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
5314 o Code simplification and refactoring:
5315 - Stop using can_complete_circuits as a global variable; access it
5316 with a function instead.
5317 - Avoid using operators directly as macro arguments: this lets us
5318 apply coccinelle transformations to our codebase more directly.
5319 Closes ticket 13172.
5320 - Combine the functions used to parse ClientTransportPlugin and
5321 ServerTransportPlugin into a single function. Closes ticket 6456.
5322 - Add inline functions and convenience macros for inspecting channel
5323 state. Refactor the code to use convenience macros instead of
5324 checking channel state directly. Fixes issue 7356.
5325 - Document all members of was_router_added_t and rename
5326 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
5327 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
5328 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
5329 constant instead of hardcoded value. Fixes issue 13840.
5330 - Refactor our generic strmap and digestmap types into a single
5331 implementation, so that we can add a new digest256map
5335 - Document the bridge-authority-only 'networkstatus-bridges' file.
5336 Closes ticket 13713; patch from "tom".
5337 - Fix typo in PredictedPortsRelevanceTime option description in
5338 manpage. Resolves issue 13707.
5339 - Stop suggesting that users specify relays by nickname: it isn't a
5340 good idea. Also, properly cross-reference how to specify relays in
5341 all parts of manual documenting options that take a list of
5342 relays. Closes ticket 13381.
5343 - Clarify the HiddenServiceDir option description in manpage to make
5344 it clear that relative paths are taken with respect to the current
5345 working directory. Also clarify that this behavior is not
5346 guaranteed to remain indefinitely. Fixes issue 13913.
5349 - New tests for many parts of channel, relay, and circuitmux
5350 functionality. Code by Andrea; part of 9262.
5351 - New tests for parse_transport_line(). Part of ticket 6456.
5352 - In the unit tests, use chgrp() to change the group of the unit
5353 test temporary directory to the current user, so that the sticky
5354 bit doesn't interfere with tests that check directory groups.
5356 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
5360 Changes in version 0.2.6.1-alpha - 2014-10-30
5361 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
5362 includes numerous code cleanups and new tests, and fixes a large
5363 number of annoying bugs. Out-of-memory conditions are handled better
5364 than in 0.2.5, pluggable transports have improved proxy support, and
5365 clients now use optimistic data for contacting hidden services. Also,
5366 we are now more robust to changes in what we consider a parseable
5367 directory object, so that tightening restrictions does not have a risk
5368 of introducing infinite download loops.
5370 This is the first alpha release in a new series, so expect there to be
5371 bugs. Users who would rather test out a more stable branch should stay
5372 with 0.2.5.x for now.
5374 o New compiler and system requirements:
5375 - Tor 0.2.6.x requires that your compiler support more of the C99
5376 language standard than before. The 'configure' script now detects
5377 whether your compiler supports C99 mid-block declarations and
5378 designated initializers. If it does not, Tor will not compile.
5380 We may revisit this requirement if it turns out that a significant
5381 number of people need to build Tor with compilers that don't
5382 bother implementing a 15-year-old standard. Closes ticket 13233.
5383 - Tor no longer supports systems without threading support. When we
5384 began working on Tor, there were several systems that didn't have
5385 threads, or where the thread support wasn't able to run the
5386 threads of a single process on multiple CPUs. That no longer
5387 holds: every system where Tor needs to run well now has threading
5388 support. Resolves ticket 12439.
5390 o Removed platform support:
5391 - We no longer include special code to build on Windows CE; as far
5392 as we know, nobody has used Tor on Windows CE in a very long time.
5393 Closes ticket 11446.
5395 o Major features (bridges):
5396 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
5397 transports if they are configured via the "TOR_PT_PROXY"
5398 environment variable. Implements proposal 232. Resolves
5401 o Major features (client performance, hidden services):
5402 - Allow clients to use optimistic data when connecting to a hidden
5403 service, which should remove a round-trip from hidden service
5404 initialization. See proposal 181 for details. Implements
5407 o Major features (directory system):
5408 - Upon receiving an unparseable directory object, if its digest
5409 matches what we expected, then don't try to download it again.
5410 Previously, when we got a descriptor we didn't like, we would keep
5411 trying to download it over and over. Closes ticket 11243.
5413 o Major features (sample torrc):
5414 - Add a new, infrequently-changed "torrc.minimal". This file is
5415 similar to torrc.sample, but it will change as infrequently as
5416 possible, for the benefit of users whose systems prompt them for
5417 intervention whenever a default configuration file is changed.
5418 Making this change allows us to update torrc.sample to be a more
5419 generally useful "sample torrc".
5421 o Major bugfixes (directory authorities):
5422 - Do not assign the HSDir flag to relays if they are not Valid, or
5423 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
5425 o Major bugfixes (directory bandwidth performance):
5426 - Don't flush the zlib buffer aggressively when compressing
5427 directory information for clients. This should save about 7% of
5428 the bandwidth currently used for compressed descriptors and
5429 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
5431 o Minor features (security, memory wiping):
5432 - Ensure we securely wipe keys from memory after
5433 crypto_digest_get_digest and init_curve25519_keypair_from_file
5434 have finished using them. Resolves ticket 13477.
5436 o Minor features (security, out-of-memory handling):
5437 - When handling an out-of-memory condition, allocate less memory for
5438 temporary data structures. Fixes issue 10115.
5439 - When handling an out-of-memory condition, consider more types of
5440 buffers, including those on directory connections, and zlib
5441 buffers. Resolves ticket 11792.
5444 - When identity keypair is generated for first time, log a
5445 congratulatory message that links to the new relay lifecycle
5446 document. Implements feature 10427.
5448 o Minor features (client):
5449 - Clients are now willing to send optimistic data (before they
5450 receive a 'connected' cell) to relays of any version. (Relays
5451 without support for optimistic data are no longer supported on the
5452 Tor network.) Resolves ticket 13153.
5454 o Minor features (directory authorities):
5455 - Don't list relays with a bandwidth estimate of 0 in the consensus.
5456 Implements a feature proposed during discussion of bug 13000.
5457 - In tor-gencert, report an error if the user provides the same
5458 argument more than once.
5459 - If a directory authority can't find a best consensus method in the
5460 votes that it holds, it now falls back to its favorite consensus
5461 method. Previously, it fell back to method 1. Neither of these is
5462 likely to get enough signatures, but "fall back to favorite"
5463 doesn't require us to maintain support an obsolete consensus
5464 method. Implements part of proposal 215.
5466 o Minor features (logging):
5467 - On Unix-like systems, you can now use named pipes as the target of
5468 the Log option, and other options that try to append to files.
5469 Closes ticket 12061. Patch from "carlo von lynX".
5470 - When opening a log file at startup, send it every log message that
5471 we generated between startup and opening it. Previously, log
5472 messages that were generated before opening the log file were only
5473 logged to stdout. Closes ticket 6938.
5474 - Add a TruncateLogFile option to overwrite logs instead of
5475 appending to them. Closes ticket 5583.
5477 o Minor features (portability, Solaris):
5478 - Threads are no longer disabled by default on Solaris; we believe
5479 that the versions of Solaris with broken threading support are all
5480 obsolete by now. Resolves ticket 9495.
5482 o Minor features (relay):
5483 - Re-check our address after we detect a changed IP address from
5484 getsockname(). This ensures that the controller command "GETINFO
5485 address" will report the correct value. Resolves ticket 11582.
5487 - A new AccountingRule option lets Relays set whether they'd like
5488 AccountingMax to be applied separately to inbound and outbound
5489 traffic, or applied to the sum of inbound and outbound traffic.
5490 Resolves ticket 961. Patch by "chobe".
5492 o Minor features (testing networks):
5493 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
5494 the "Exit" flag regardless of their uptime, bandwidth, or exit
5495 policy. TestingTorNetwork must be set for this option to have any
5496 effect. Previously, authorities would take up to 35 minutes to
5497 give nodes the Exit flag in a test network. Partially implements
5500 o Minor features (validation):
5501 - Check all date/time values passed to tor_timegm and
5502 parse_rfc1123_time for validity, taking leap years into account.
5503 Improves HTTP header validation. Implemented with bug 13476.
5504 - In correct_tm(), limit the range of values returned by system
5505 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
5506 This means we don't have to deal with negative or too large dates,
5507 even if a clock is wrong. Otherwise we might fail to read a file
5508 written by us which includes such a date. Fixes bug 13476.
5510 o Minor bugfixes (bridge clients):
5511 - When configured to use a bridge without an identity digest (not
5512 recommended), avoid launching an extra channel to it when
5513 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
5515 o Minor bugfixes (bridges):
5516 - When DisableNetwork is set, do not launch pluggable transport
5517 plugins, and if any are running, terminate them. Fixes bug 13213;
5518 bugfix on 0.2.3.6-alpha.
5520 o Minor bugfixes (C correctness):
5521 - Fix several instances of possible integer overflow/underflow/NaN.
5522 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
5524 - In circuit_build_times_calculate_timeout() in circuitstats.c,
5525 avoid dividing by zero in the pareto calculations. This traps
5526 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
5528 - Fix an integer overflow in format_time_interval(). Fixes bug
5529 13393; bugfix on 0.2.0.10-alpha.
5530 - Set the correct day of year value when the system's localtime(_r)
5531 or gmtime(_r) functions fail to set struct tm. Not externally
5532 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
5533 - Avoid unlikely signed integer overflow in tor_timegm on systems
5534 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
5536 o Minor bugfixes (client):
5537 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
5538 BadExit flag are not considered worthy candidates. Fixes bug
5539 13066; bugfix on 0.1.2.3-alpha.
5540 - Use the consensus schedule for downloading consensuses, and not
5541 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
5542 - Handle unsupported or malformed SOCKS5 requests properly by
5543 responding with the appropriate error message before closing the
5544 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
5546 o Minor bugfixes (client, torrc):
5547 - Stop modifying the value of our DirReqStatistics torrc option just
5548 because we're not a bridge or relay. This bug was causing Tor
5549 Browser users to write "DirReqStatistics 0" in their torrc files
5550 as if they had chosen to change the config. Fixes bug 4244; bugfix
5552 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
5553 that our options have changed every time we SIGHUP. Fixes bug
5554 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
5556 o Minor bugfixes (controller):
5557 - Return an error when the second or later arguments of the
5558 "setevents" controller command are invalid events. Previously we
5559 would return success while silently skipping invalid events. Fixes
5560 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
5562 o Minor bugfixes (directory system):
5563 - Always believe that v3 directory authorities serve extra-info
5564 documents, whether they advertise "caches-extra-info" or not.
5565 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
5566 - When running as a v3 directory authority, advertise that you serve
5567 extra-info documents so that clients who want them can find them
5568 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
5569 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
5570 Previously, directories offering BRIDGE_DIRINFO and some other
5571 flag (i.e. microdescriptors or extrainfo) would be ignored when
5572 looking for bridges. Partially fixes bug 13163; bugfix
5575 o Minor bugfixes (networking):
5576 - Check for orconns and use connection_or_close_for_error() rather
5577 than connection_mark_for_close() directly in the getsockopt()
5578 failure case of connection_handle_write_impl(). Fixes bug 11302;
5579 bugfix on 0.2.4.4-alpha.
5581 o Minor bugfixes (relay):
5582 - When generating our family list, remove spaces from around the
5583 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
5584 - If our previous bandwidth estimate was 0 bytes, allow publishing a
5585 new relay descriptor immediately. Fixes bug 13000; bugfix
5588 o Minor bugfixes (testing networks):
5589 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
5590 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
5591 - Stop using the default authorities in networks which provide both
5592 AlternateDirAuthority and AlternateBridgeAuthority. Partially
5593 fixes bug 13163; bugfix on 0.2.0.13-alpha.
5595 o Minor bugfixes (testing):
5596 - Stop spawn test failures due to a race condition between the
5597 SIGCHLD handler updating the process status, and the test reading
5598 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
5600 o Minor bugfixes (testing, Windows):
5601 - Avoid passing an extra backslash when creating a temporary
5602 directory for running the unit tests on Windows. Fixes bug 12392;
5603 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
5605 o Minor bugfixes (windows):
5606 - Remove code to special-case handling of NTE_BAD_KEYSET when
5607 acquiring windows CryptoAPI context. This error can't actually
5608 occur for the parameters we're providing. Fixes bug 10816; bugfix
5611 o Minor bugfixes (zlib):
5612 - Avoid truncating a zlib stream when trying to finalize it with an
5613 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
5616 - Allow our configure script to build correctly with autoconf 2.62
5617 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
5618 - Improve the error message from ./configure to make it clear that
5619 when asciidoc has not been found, the user will have to either add
5620 --disable-asciidoc argument or install asciidoc. Resolves
5623 o Code simplification and refactoring:
5624 - Change the entry_is_live() function to take named bitfield
5625 elements instead of an unnamed list of booleans. Closes
5627 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
5628 Resolves ticket 12205.
5629 - Use calloc and reallocarray functions instead of multiply-
5630 then-malloc. This makes it less likely for us to fall victim to an
5631 integer overflow attack when allocating. Resolves ticket 12855.
5632 - Use the standard macro name SIZE_MAX, instead of our
5634 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
5635 functions which take them as arguments. Replace 0 with NO_DIRINFO
5636 in a function call for clarity. Seeks to prevent future issues
5638 - Avoid 4 null pointer errors under clang static analysis by using
5639 tor_assert() to prove that the pointers aren't null. Fixes
5641 - Rework the API of policies_parse_exit_policy() to use a bitmask to
5642 represent parsing options, instead of a confusing mess of
5643 booleans. Resolves ticket 8197.
5644 - Introduce a helper function to parse ExitPolicy in
5645 or_options_t structure.
5648 - Add a doc/TUNING document with tips for handling large numbers of
5649 TCP connections when running busy Tor relay. Update the warning
5650 message to point to this file when running out of sockets
5651 operating system is allowing to use simultaneously. Resolves
5655 - We no longer remind the user about configuration options that have
5656 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
5657 - Remove our old, non-weighted bandwidth-based node selection code.
5658 Previously, we used it as a fallback when we couldn't perform
5659 weighted bandwidth-based node selection. But that would only
5660 happen in the cases where we had no consensus, or when we had a
5661 consensus generated by buggy or ancient directory authorities. In
5662 either case, it's better to use the more modern, better maintained
5663 algorithm, with reasonable defaults for the weights. Closes
5665 - Remove the --disable-curve25519 configure option. Relays and
5666 clients now are required to support curve25519 and the
5668 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
5669 used to be deprecated synonyms for "StrictNodes", are now marked
5670 obsolete. Resolves ticket 12226.
5671 - Clients don't understand the BadDirectory flag in the consensus
5672 anymore, and ignore it.
5675 - Refactor the function that chooses guard nodes so that it can more
5676 easily be tested; write some tests for it.
5677 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
5678 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
5679 - Create unit tests for format_time_interval(). With bug 13393.
5680 - Add unit tests for tor_timegm signed overflow, tor_timegm and
5681 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
5682 tests (visible) fixes in bug 13476.
5683 - Add a "coverage-html" make target to generate HTML-visualized
5684 coverage results when building with --enable-coverage. (Requires
5685 lcov.) Patch from Kevin Murray.
5686 - Enable the backtrace handler (where supported) when running the
5688 - Revise all unit tests that used the legacy test_* macros to
5689 instead use the recommended tt_* macros. This patch was generated
5690 with coccinelle, to avoid manual errors. Closes ticket 13119.
5692 o Distribution (systemd):
5693 - systemd unit file: only allow tor to write to /var/lib/tor and
5694 /var/log/tor. The rest of the filesystem is accessible for reading
5695 only. Patch by intrigeri; resolves ticket 12751.
5696 - systemd unit file: ensure that the process and all its children
5697 can never gain new privileges. Patch by intrigeri; resolves
5699 - systemd unit file: set up /var/run/tor as writable for the Tor
5700 service. Patch by intrigeri; resolves ticket 13196.
5702 o Removed features (directory authorities):
5703 - Remove code that prevented authorities from listing Tor relays
5704 affected by CVE-2011-2769 as guards. These relays are already
5705 rejected altogether due to the minimum version requirement of
5706 0.2.3.16-alpha. Closes ticket 13152.
5707 - The "AuthDirRejectUnlisted" option no longer has any effect, as
5708 the fingerprints file (approved-routers) has been deprecated.
5709 - Directory authorities do not support being Naming dirauths anymore.
5710 The "NamingAuthoritativeDir" config option is now obsolete.
5711 - Directory authorities do not support giving out the BadDirectory
5713 - Directory authorities no longer advertise or support consensus
5714 methods 1 through 12 inclusive. These consensus methods were
5715 obsolete and/or insecure: maintaining the ability to support them
5716 served no good purpose. Implements part of proposal 215; closes
5719 o Testing (test-network.sh):
5720 - Stop using "echo -n", as some shells' built-in echo doesn't
5721 support "-n". Instead, use "/bin/echo -n". Partially fixes
5723 - Stop an apparent test-network hang when used with make -j2. Fixes
5725 - Add a --delay option to test-network.sh, which configures the
5726 delay before the chutney network tests for data transmission.
5727 Partially implements ticket 13161.
5730 Changes in version 0.2.5.10 - 2014-10-24
5731 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
5733 It adds several new security features, including improved
5734 denial-of-service resistance for relays, new compiler hardening
5735 options, and a system-call sandbox for hardened installations on Linux
5736 (requires seccomp2). The controller protocol has several new features,
5737 resolving IPv6 addresses should work better than before, and relays
5738 should be a little more CPU-efficient. We've added support for more
5739 OpenBSD and FreeBSD transparent proxy types. We've improved the build
5740 system and testing infrastructure to allow unit testing of more parts
5741 of the Tor codebase. Finally, we've addressed several nagging pluggable
5742 transport usability issues, and included numerous other small bugfixes
5743 and features mentioned below.
5745 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
5746 have accumulated many known flaws; everyone should upgrade.
5748 o Deprecated versions:
5749 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
5750 attention for some while.
5753 Changes in version 0.2.5.9-rc - 2014-10-20
5754 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
5755 series. It disables SSL3 in response to the recent "POODLE" attack
5756 (even though POODLE does not affect Tor). It also works around a crash
5757 bug caused by some operating systems' response to the "POODLE" attack
5758 (which does affect Tor). It also contains a few miscellaneous fixes.
5760 o Major security fixes:
5761 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
5762 today support TLS 1.0 or later, so we can safely turn off support
5763 for this old (and insecure) protocol. Fixes bug 13426.
5765 o Major bugfixes (openssl bug workaround):
5766 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
5767 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
5768 13471. This is a workaround for an OpenSSL bug.
5771 - Disable the sandbox name resolver cache when running tor-resolve:
5772 tor-resolve doesn't use the sandbox code, and turning it on was
5773 breaking attempts to do tor-resolve on a non-default server on
5774 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
5776 o Compilation fixes:
5777 - Build and run correctly on systems like OpenBSD-current that have
5778 patched OpenSSL to remove get_cipher_by_char and/or its
5779 implementations. Fixes issue 13325.
5781 o Downgraded warnings:
5782 - Downgrade the severity of the 'unexpected sendme cell from client'
5783 from 'warn' to 'protocol warning'. Closes ticket 8093.
5786 Changes in version 0.2.4.25 - 2014-10-20
5787 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
5788 (even though POODLE does not affect Tor). It also works around a crash
5789 bug caused by some operating systems' response to the "POODLE" attack
5790 (which does affect Tor).
5792 o Major security fixes (also in 0.2.5.9-rc):
5793 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
5794 today support TLS 1.0 or later, so we can safely turn off support
5795 for this old (and insecure) protocol. Fixes bug 13426.
5797 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
5798 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
5799 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
5800 13471. This is a workaround for an OpenSSL bug.
5803 Changes in version 0.2.5.8-rc - 2014-09-22
5804 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
5805 series. It fixes a bug that affects consistency and speed when
5806 connecting to hidden services, and it updates the location of one of
5807 the directory authorities.
5810 - Clients now send the correct address for their chosen rendezvous
5811 point when trying to access a hidden service. They used to send
5812 the wrong address, which would still work some of the time because
5813 they also sent the identity digest of the rendezvous point, and if
5814 the hidden service happened to try connecting to the rendezvous
5815 point from a relay that already had a connection open to it,
5816 the relay would reuse that connection. Now connections to hidden
5817 services should be more robust and faster. Also, this bug meant
5818 that clients were leaking to the hidden service whether they were
5819 on a little-endian (common) or big-endian (rare) system, which for
5820 some users might have reduced their anonymity. Fixes bug 13151;
5821 bugfix on 0.2.1.5-alpha.
5823 o Directory authority changes:
5824 - Change IP address for gabelmoo (v3 directory authority).
5827 Changes in version 0.2.4.24 - 2014-09-22
5828 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
5829 connecting to hidden services, and it updates the location of one of
5830 the directory authorities.
5833 - Clients now send the correct address for their chosen rendezvous
5834 point when trying to access a hidden service. They used to send
5835 the wrong address, which would still work some of the time because
5836 they also sent the identity digest of the rendezvous point, and if
5837 the hidden service happened to try connecting to the rendezvous
5838 point from a relay that already had a connection open to it,
5839 the relay would reuse that connection. Now connections to hidden
5840 services should be more robust and faster. Also, this bug meant
5841 that clients were leaking to the hidden service whether they were
5842 on a little-endian (common) or big-endian (rare) system, which for
5843 some users might have reduced their anonymity. Fixes bug 13151;
5844 bugfix on 0.2.1.5-alpha.
5846 o Directory authority changes:
5847 - Change IP address for gabelmoo (v3 directory authority).
5849 o Minor features (geoip):
5850 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
5854 Changes in version 0.2.5.7-rc - 2014-09-11
5855 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
5856 release series, and some long-standing bugs related to ORPort reachability
5857 testing and failure to send CREATE cells. It is the first release
5858 candidate for the Tor 0.2.5.x series.
5860 o Major bugfixes (client, startup):
5861 - Start making circuits as soon as DisabledNetwork is turned off.
5862 When Tor started with DisabledNetwork set, it would correctly
5863 conclude that it shouldn't build circuits, but it would mistakenly
5864 cache this conclusion, and continue believing it even when
5865 DisableNetwork is set to 0. Fixes the bug introduced by the fix
5866 for bug 11200; bugfix on 0.2.5.4-alpha.
5867 - Resume expanding abbreviations for command-line options. The fix
5868 for bug 4647 accidentally removed our hack from bug 586 that
5869 rewrote HashedControlPassword to __HashedControlSessionPassword
5870 when it appears on the commandline (which allowed the user to set
5871 her own HashedControlPassword in the torrc file while the
5872 controller generates a fresh session password for each run). Fixes
5873 bug 12948; bugfix on 0.2.5.1-alpha.
5874 - Warn about attempts to run hidden services and relays in the same
5875 process: that's probably not a good idea. Closes ticket 12908.
5877 o Major bugfixes (relay):
5878 - Avoid queuing or sending destroy cells for circuit ID zero when we
5879 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
5880 Found and fixed by "cypherpunks".
5881 - Fix ORPort reachability detection on relays running behind a
5882 proxy, by correctly updating the "local" mark on the controlling
5883 channel when changing the address of an or_connection_t after the
5884 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
5886 o Minor features (bridge):
5887 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
5888 cookie file for the ExtORPort g+r by default.
5890 o Minor features (geoip):
5891 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
5894 o Minor bugfixes (logging):
5895 - Reduce the log severity of the "Pluggable transport proxy does not
5896 provide any needed transports and will not be launched." message,
5897 since Tor Browser includes several ClientTransportPlugin lines in
5898 its torrc-defaults file, leading every Tor Browser user who looks
5899 at her logs to see these notices and wonder if they're dangerous.
5900 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
5901 - Downgrade "Unexpected onionskin length after decryption" warning
5902 to a protocol-warn, since there's nothing relay operators can do
5903 about a client that sends them a malformed create cell. Resolves
5904 bug 12996; bugfix on 0.0.6rc1.
5905 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
5906 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
5907 - When logging information about an EXTEND2 or EXTENDED2 cell, log
5908 their names correctly. Fixes part of bug 12700; bugfix
5910 - When logging information about a relay cell whose command we don't
5911 recognize, log its command as an integer. Fixes part of bug 12700;
5912 bugfix on 0.2.1.10-alpha.
5913 - Escape all strings from the directory connection before logging
5914 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
5916 o Minor bugfixes (controller):
5917 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
5918 bug 12864; bugfix on 0.2.5.1-alpha.
5919 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
5920 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
5923 o Minor bugfixes (compilation):
5924 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
5925 bugfix on 0.2.5.5-alpha.
5926 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
5927 0.2.5.1-alpha. Patch from "NewEraCracker".
5928 - In routerlist_assert_ok(), don't take the address of a
5929 routerinfo's cache_info member unless that routerinfo is non-NULL.
5930 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
5931 - Fix a large number of false positive warnings from the clang
5932 analyzer static analysis tool. This should make real warnings
5933 easier for clang analyzer to find. Patch from "teor". Closes
5936 o Distribution (systemd):
5937 - Verify configuration file via ExecStartPre in the systemd unit
5938 file. Patch from intrigeri; resolves ticket 12730.
5939 - Explicitly disable RunAsDaemon in the systemd unit file. Our
5940 current systemd unit uses "Type = simple", so systemd does not
5941 expect tor to fork. If the user has "RunAsDaemon 1" in their
5942 torrc, then things won't work as expected. This is e.g. the case
5943 on Debian (and derivatives), since there we pass "--defaults-torrc
5944 /usr/share/tor/tor-service-defaults-torrc" (that contains
5945 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
5949 - Adjust the URLs in the README to refer to the new locations of
5950 several documents on the website. Fixes bug 12830. Patch from
5952 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
5956 Changes in version 0.2.5.6-alpha - 2014-07-28
5957 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
5958 risk from guard rotation, and fixes a variety of other issues to get
5959 us closer to a release candidate.
5961 o Major features (also in 0.2.4.23):
5962 - Make the number of entry guards configurable via a new
5963 NumEntryGuards consensus parameter, and the number of directory
5964 guards configurable via a new NumDirectoryGuards consensus
5965 parameter. Implements ticket 12688.
5967 o Major bugfixes (also in 0.2.4.23):
5968 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
5969 implementation that caused incorrect results on 32-bit
5970 implementations when certain malformed inputs were used along with
5971 a small class of private ntor keys. This bug does not currently
5972 appear to allow an attacker to learn private keys or impersonate a
5973 Tor server, but it could provide a means to distinguish 32-bit Tor
5974 implementations from 64-bit Tor implementations. Fixes bug 12694;
5975 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
5979 - Perform circuit cleanup operations even when circuit
5980 construction operations are disabled (because the network is
5981 disabled, or because there isn't enough directory information).
5982 Previously, when we were not building predictive circuits, we
5983 were not closing expired circuits either. Fixes bug 8387; bugfix on
5984 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
5985 became more strict about when we have "enough directory information
5989 - Authorities now assign the Guard flag to the fastest 25% of the
5990 network (it used to be the fastest 50%). Also raise the consensus
5991 weight that guarantees the Guard flag from 250 to 2000. For the
5992 current network, this results in about 1100 guards, down from 2500.
5993 This step paves the way for moving the number of entry guards
5994 down to 1 (proposal 236) while still providing reasonable expected
5995 performance for most users. Implements ticket 12690.
5996 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
5998 - Slightly enhance the diagnostic message for bug 12184.
6000 o Minor bugfixes (also in 0.2.4.23):
6001 - Warn and drop the circuit if we receive an inbound 'relay early'
6002 cell. Those used to be normal to receive on hidden service circuits
6003 due to bug 1038, but the buggy Tor versions are long gone from
6004 the network so we can afford to resume watching for them. Resolves
6005 the rest of bug 1038; bugfix on 0.2.1.19.
6006 - Correct a confusing error message when trying to extend a circuit
6007 via the control protocol but we don't know a descriptor or
6008 microdescriptor for one of the specified relays. Fixes bug 12718;
6009 bugfix on 0.2.3.1-alpha.
6012 - Fix compilation when building with bufferevents enabled. (This
6013 configuration is still not expected to work, however.)
6014 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
6015 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
6017 - Compile correctly with builds and forks of OpenSSL (such as
6018 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
6019 0.2.1.1-alpha. Patch from "dhill".
6022 Changes in version 0.2.4.23 - 2014-07-28
6023 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
6024 guard rotation, and also backports several important fixes from the
6025 Tor 0.2.5 alpha release series.
6028 - Clients now look at the "usecreatefast" consensus parameter to
6029 decide whether to use CREATE_FAST or CREATE cells for the first hop
6030 of their circuit. This approach can improve security on connections
6031 where Tor's circuit handshake is stronger than the available TLS
6032 connection security levels, but the tradeoff is more computational
6033 load on guard relays. Implements proposal 221. Resolves ticket 9386.
6034 - Make the number of entry guards configurable via a new
6035 NumEntryGuards consensus parameter, and the number of directory
6036 guards configurable via a new NumDirectoryGuards consensus
6037 parameter. Implements ticket 12688.
6040 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
6041 implementation that caused incorrect results on 32-bit
6042 implementations when certain malformed inputs were used along with
6043 a small class of private ntor keys. This bug does not currently
6044 appear to allow an attacker to learn private keys or impersonate a
6045 Tor server, but it could provide a means to distinguish 32-bit Tor
6046 implementations from 64-bit Tor implementations. Fixes bug 12694;
6047 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
6051 - Warn and drop the circuit if we receive an inbound 'relay early'
6052 cell. Those used to be normal to receive on hidden service circuits
6053 due to bug 1038, but the buggy Tor versions are long gone from
6054 the network so we can afford to resume watching for them. Resolves
6055 the rest of bug 1038; bugfix on 0.2.1.19.
6056 - Correct a confusing error message when trying to extend a circuit
6057 via the control protocol but we don't know a descriptor or
6058 microdescriptor for one of the specified relays. Fixes bug 12718;
6059 bugfix on 0.2.3.1-alpha.
6060 - Avoid an illegal read from stack when initializing the TLS
6061 module using a version of OpenSSL without all of the ciphers
6062 used by the v2 link handshake. Fixes bug 12227; bugfix on
6063 0.2.4.8-alpha. Found by "starlight".
6066 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
6070 Changes in version 0.2.5.5-alpha - 2014-06-18
6071 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
6072 0.2.5.x release series, including a couple of DoS issues, some
6073 performance regressions, a large number of bugs affecting the Linux
6074 seccomp2 sandbox code, and various other bugfixes. It also adds
6075 diagnostic bugfixes for a few tricky issues that we're trying to
6078 o Major features (security, traffic analysis resistance):
6079 - Several major improvements to the algorithm used to decide when to
6080 close TLS connections. Previous versions of Tor closed connections
6081 at a fixed interval after the last time a non-padding cell was
6082 sent over the connection, regardless of the target of the
6083 connection. Now, we randomize the intervals by adding up to 50% of
6084 their base value, we measure the length of time since connection
6085 last had at least one circuit, and we allow connections to known
6086 ORs to remain open a little longer (15 minutes instead of 3
6087 minutes minimum). These changes should improve Tor's resistance
6088 against some kinds of traffic analysis, and lower some overhead
6089 from needlessly closed connections. Fixes ticket 6799.
6090 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
6092 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
6093 - Fix a memory leak that could occur if a microdescriptor parse
6094 fails during the tokenizing step. This bug could enable a memory
6095 exhaustion attack by directory servers. Fixes bug 11649; bugfix
6098 o Major bugfixes (security, directory authorities):
6099 - Directory authorities now include a digest of each relay's
6100 identity key as a part of its microdescriptor.
6102 This is a workaround for bug 11743 (reported by "cypherpunks"),
6103 where Tor clients do not support receiving multiple
6104 microdescriptors with the same SHA256 digest in the same
6105 consensus. When clients receive a consensus like this, they only
6106 use one of the relays. Without this fix, a hostile relay could
6107 selectively disable some client use of target relays by
6108 constructing a router descriptor with a different identity and the
6109 same microdescriptor parameters and getting the authorities to
6110 list it in a microdescriptor consensus. This fix prevents an
6111 attacker from causing a microdescriptor collision, because the
6112 router's identity is not forgeable.
6114 o Major bugfixes (relay):
6115 - Use a direct dirport connection when uploading non-anonymous
6116 descriptors to the directory authorities. Previously, relays would
6117 incorrectly use tunnel connections under a fairly wide variety of
6118 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
6119 - When a circuit accidentally has the same circuit ID for its
6120 forward and reverse direction, correctly detect the direction of
6121 cells using that circuit. Previously, this bug made roughly one
6122 circuit in a million non-functional. Fixes bug 12195; this is a
6123 bugfix on every version of Tor.
6125 o Major bugfixes (client, pluggable transports):
6126 - When managing pluggable transports, use OS notification facilities
6127 to learn if they have crashed, and don't attempt to kill any
6128 process that has already exited. Fixes bug 8746; bugfix
6131 o Minor features (diagnostic):
6132 - When logging a warning because of bug 7164, additionally check the
6133 hash table for consistency (as proposed on ticket 11737). This may
6134 help diagnose bug 7164.
6135 - When we log a heartbeat, log how many one-hop circuits we have
6136 that are at least 30 minutes old, and log status information about
6137 a few of them. This is an attempt to track down bug 8387.
6138 - When encountering an unexpected CR while writing text to a file on
6139 Windows, log the name of the file. Should help diagnosing
6141 - Give more specific warnings when a client notices that an onion
6142 handshake has failed. Fixes ticket 9635.
6143 - Add significant new logging code to attempt to diagnose bug 12184,
6144 where relays seem to run out of available circuit IDs.
6145 - Improve the diagnostic log message for bug 8387 even further to
6146 try to improve our odds of figuring out why one-hop directory
6147 circuits sometimes do not get closed.
6149 o Minor features (security, memory management):
6150 - Memory allocation tricks (mempools and buffer freelists) are now
6151 disabled by default. You can turn them back on with
6152 --enable-mempools and --enable-buf-freelists respectively. We're
6153 disabling these features because malloc performance is good enough
6154 on most platforms, and a similar feature in OpenSSL exacerbated
6155 exploitation of the Heartbleed attack. Resolves ticket 11476.
6157 o Minor features (security):
6158 - Apply the secure SipHash-2-4 function to the hash table mapping
6159 circuit IDs and channels to circuits. We missed this one when we
6160 were converting all the other hash functions to use SipHash back
6161 in 0.2.5.3-alpha. Resolves ticket 11750.
6163 o Minor features (build):
6164 - The configure script has a --disable-seccomp option to turn off
6165 support for libseccomp on systems that have it, in case it (or
6166 Tor's use of it) is broken. Resolves ticket 11628.
6168 o Minor features (other):
6169 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
6172 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
6173 - When running a hidden service, do not allow TunneledDirConns 0;
6174 this will keep the hidden service from running, and also
6175 make it publish its descriptors directly over HTTP. Fixes bug 10849;
6176 bugfix on 0.2.1.1-alpha.
6178 o Minor bugfixes (performance):
6179 - Avoid a bug where every successful connection made us recompute
6180 the flag telling us whether we have sufficient information to
6181 build circuits. Previously, we would forget our cached value
6182 whenever we successfully opened a channel (or marked a router as
6183 running or not running for any other reason), regardless of
6184 whether we had previously believed the router to be running. This
6185 forced us to run an expensive update operation far too often.
6186 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
6187 - Avoid using tor_memeq() for checking relay cell integrity. This
6188 removes a possible performance bottleneck. Fixes part of bug
6189 12169; bugfix on 0.2.1.31.
6191 o Minor bugfixes (compilation):
6192 - Fix compilation of test_status.c when building with MVSC. Bugfix
6193 on 0.2.5.4-alpha. Patch from Gisle Vanem.
6194 - Resolve GCC complaints on OpenBSD about discarding constness in
6195 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
6196 on 0.1.1.23. Patch from Dana Koch.
6197 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
6198 treatment of long and time_t as comparable types. Fixes part of
6199 bug 11633. Patch from Dana Koch.
6200 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
6201 11623; bugfix on 0.2.5.3-alpha.
6202 - When deciding whether to build the 64-bit curve25519
6203 implementation, detect platforms where we can compile 128-bit
6204 arithmetic but cannot link it. Fixes bug 11729; bugfix on
6205 0.2.4.8-alpha. Patch from "conradev".
6206 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
6207 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
6208 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
6211 o Minor bugfixes (Directory server):
6212 - When sending a compressed set of descriptors or microdescriptors,
6213 make sure to finalize the zlib stream. Previously, we would write
6214 all the compressed data, but if the last descriptor we wanted to
6215 send was missing or too old, we would not mark the stream as
6216 finished. This caused problems for decompression tools. Fixes bug
6217 11648; bugfix on 0.1.1.23.
6219 o Minor bugfixes (Linux seccomp sandbox):
6220 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
6221 11622; bugfix on 0.2.5.1-alpha.
6222 - Avoid crashing when re-opening listener ports with the seccomp
6223 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
6224 - Avoid crashing with the seccomp sandbox enabled along with
6225 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
6226 - When we receive a SIGHUP with the sandbox enabled, correctly
6227 support rotating our log files. Fixes bug 12032; bugfix
6229 - Avoid crash when running with sandboxing enabled and
6230 DirReqStatistics not disabled. Fixes bug 12035; bugfix
6232 - Fix a "BUG" warning when trying to write bridge-stats files with
6233 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
6235 - Prevent the sandbox from crashing on startup when run with the
6236 --enable-expensive-hardening configuration option. Fixes bug
6237 11477; bugfix on 0.2.5.4-alpha.
6238 - When running with DirPortFrontPage and sandboxing both enabled,
6239 reload the DirPortFrontPage correctly when restarting. Fixes bug
6240 12028; bugfix on 0.2.5.1-alpha.
6241 - Don't try to enable the sandbox when using the Tor binary to check
6242 its configuration, hash a passphrase, or so on. Doing so was
6243 crashing on startup for some users. Fixes bug 11609; bugfix
6245 - Avoid warnings when running with sandboxing and node statistics
6246 enabled at the same time. Fixes part of 12064; bugfix on
6247 0.2.5.1-alpha. Patch from Michael Wolf.
6248 - Avoid warnings when running with sandboxing enabled at the same
6249 time as cookie authentication, hidden services, or directory
6250 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
6251 - Do not allow options that require calls to exec to be enabled
6252 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
6253 bug 12043; bugfix on 0.2.5.1-alpha.
6254 - Handle failures in getpwnam()/getpwuid() when running with the
6255 User option set and the Linux syscall sandbox enabled. Fixes bug
6256 11946; bugfix on 0.2.5.1-alpha.
6257 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
6258 to avoid calling getaddrinfo() after installing the sandbox
6259 filters. Previously, it preloaded a cache with the IPv4 address
6260 for our hostname, and nothing else. Now, it loads the cache with
6261 every address that it used to initialize the Tor process. Fixes
6262 bug 11970; bugfix on 0.2.5.1-alpha.
6264 o Minor bugfixes (pluggable transports):
6265 - Enable the ExtORPortCookieAuthFile option, to allow changing the
6266 default location of the authentication token for the extended OR
6267 Port as used by sever-side pluggable transports. We had
6268 implemented this option before, but the code to make it settable
6269 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
6270 - Avoid another 60-second delay when starting Tor in a pluggable-
6271 transport-using configuration when we already have cached
6272 descriptors for our bridges. Fixes bug 11965; bugfix
6275 o Minor bugfixes (client):
6276 - Avoid "Tried to open a socket with DisableNetwork set" warnings
6277 when starting a client with bridges configured and DisableNetwork
6278 set. (Tor launcher starts Tor with DisableNetwork set the first
6279 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
6281 o Minor bugfixes (testing):
6282 - The Python parts of the test scripts now work on Python 3 as well
6283 as Python 2, so systems where '/usr/bin/python' is Python 3 will
6284 no longer have the tests break. Fixes bug 11608; bugfix
6286 - When looking for versions of python that we could run the tests
6287 with, check for "python2.7" and "python3.3"; previously we were
6288 only looking for "python", "python2", and "python3". Patch from
6289 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
6290 - Fix all valgrind warnings produced by the unit tests. There were
6291 over a thousand memory leak warnings previously, mostly produced
6292 by forgetting to free things in the unit test code. Fixes bug
6293 11618, bugfixes on many versions of Tor.
6295 o Minor bugfixes (tor-fw-helper):
6296 - Give a correct log message when tor-fw-helper fails to launch.
6297 (Previously, we would say something like "tor-fw-helper sent us a
6298 string we could not parse".) Fixes bug 9781; bugfix
6301 o Minor bugfixes (relay, threading):
6302 - Check return code on spawn_func() in cpuworker code, so that we
6303 don't think we've spawned a nonworking cpuworker and write junk to
6304 it forever. Fix related to bug 4345; bugfix on all released Tor
6305 versions. Found by "skruffy".
6306 - Use a pthread_attr to make sure that spawn_func() cannot return an
6307 error while at the same time launching a thread. Fix related to
6308 bug 4345; bugfix on all released Tor versions. Reported
6311 o Minor bugfixes (relay, oom prevention):
6312 - Correctly detect the total available system memory. We tried to do
6313 this in 0.2.5.4-alpha, but the code was set up to always return an
6314 error value, even on success. Fixes bug 11805; bugfix
6317 o Minor bugfixes (relay, other):
6318 - We now drop CREATE cells for already-existent circuit IDs and for
6319 zero-valued circuit IDs, regardless of other factors that might
6320 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
6322 - Avoid an illegal read from stack when initializing the TLS module
6323 using a version of OpenSSL without all of the ciphers used by the
6324 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
6326 - When rejecting DATA cells for stream_id zero, still count them
6327 against the circuit's deliver window so that we don't fail to send
6328 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
6330 o Minor bugfixes (logging):
6331 - Fix a misformatted log message about delayed directory fetches.
6332 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
6333 - Squelch a spurious LD_BUG message "No origin circuit for
6334 successful SOCKS stream" in certain hidden service failure cases;
6338 - Include a tor.service file in contrib/dist for use with systemd.
6339 Some distributions will be able to use this file unmodified;
6340 others will need to tweak it, or write their own. Patch from Jamie
6341 Nguyen; resolves ticket 8368.
6344 - Clean up several option names in the manpage to match their real
6345 names, add the missing documentation for a couple of testing and
6346 directory authority options, remove the documentation for a
6347 V2-directory fetching option that no longer exists. Resolves
6349 - Correct the documenation so that it lists the correct directory
6350 for the stats files. (They are in a subdirectory called "stats",
6352 - In the manpage, move more authority-only options into the
6353 directory authority section so that operators of regular directory
6354 caches don't get confused.
6357 - The contrib directory has been sorted and tidied. Before, it was
6358 an unsorted dumping ground for useful and not-so-useful things.
6359 Now, it is divided based on functionality, and the items which
6360 seemed to be nonfunctional or useless have been removed. Resolves
6361 ticket 8966; based on patches from "rl1987".
6364 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
6365 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
6366 - The TunnelDirConns and PreferTunnelledDirConns options no longer
6367 exist; tunneled directory connections have been available since
6368 0.1.2.5-alpha, and turning them off is not a good idea. This is a
6369 brute-force fix for 10849, where "TunnelDirConns 0" would break
6373 Changes in version 0.2.4.22 - 2014-05-16
6374 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
6375 alpha release series. These include blocking all authority signing
6376 keys that may have been affected by the OpenSSL "heartbleed" bug,
6377 choosing a far more secure set of TLS ciphersuites by default, closing
6378 a couple of memory leaks that could be used to run a target relay out
6379 of RAM, and several others.
6381 o Major features (security, backport from 0.2.5.4-alpha):
6382 - Block authority signing keys that were used on authorities
6383 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
6384 don't have any evidence that these keys _were_ compromised; we're
6385 doing this to be prudent.) Resolves ticket 11464.
6387 o Major bugfixes (security, OOM):
6388 - Fix a memory leak that could occur if a microdescriptor parse
6389 fails during the tokenizing step. This bug could enable a memory
6390 exhaustion attack by directory servers. Fixes bug 11649; bugfix
6393 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
6394 - The relay ciphersuite list is now generated automatically based on
6395 uniform criteria, and includes all OpenSSL ciphersuites with
6396 acceptable strength and forward secrecy. Previously, we had left
6397 some perfectly fine ciphersuites unsupported due to omission or
6398 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
6399 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
6400 - Relays now trust themselves to have a better view than clients of
6401 which TLS ciphersuites are better than others. (Thanks to bug
6402 11513, the relay list is now well-considered, whereas the client
6403 list has been chosen mainly for anti-fingerprinting purposes.)
6404 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
6405 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
6406 AES128. Resolves ticket 11528.
6407 - Clients now try to advertise the same list of ciphersuites as
6408 Firefox 28. This change enables selection of (fast) GCM
6409 ciphersuites, disables some strange old ciphers, and stops
6410 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
6411 Resolves ticket 11438.
6413 o Minor bugfixes (configuration, security):
6414 - When running a hidden service, do not allow TunneledDirConns 0:
6415 trying to set that option together with a hidden service would
6416 otherwise prevent the hidden service from running, and also make
6417 it publish its descriptors directly over HTTP. Fixes bug 10849;
6418 bugfix on 0.2.1.1-alpha.
6420 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
6421 - Avoid sending a garbage value to the controller when a circuit is
6422 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
6424 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
6425 - Stop leaking memory when we successfully resolve a PTR record.
6426 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
6428 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
6429 - Avoid 60-second delays in the bootstrapping process when Tor is
6430 launching for a second time while using bridges. Fixes bug 9229;
6431 bugfix on 0.2.0.3-alpha.
6433 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
6434 - Give the correct URL in the warning message when trying to run a
6435 relay on an ancient version of Windows. Fixes bug 9393.
6437 o Minor bugfixes (compilation):
6438 - Fix a compilation error when compiling with --disable-curve25519.
6439 Fixes bug 9700; bugfix on 0.2.4.17-rc.
6442 - Downgrade the warning severity for the the "md was still
6443 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
6444 for trying to diagnose this bug, and the current warning in
6445 earlier versions of tor achieves nothing useful. Addresses warning
6448 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
6449 - When we run out of usable circuit IDs on a channel, log only one
6450 warning for the whole channel, and describe how many circuits
6451 there were on the channel. Fixes part of ticket 11553.
6453 o Minor features (security, backport from 0.2.5.4-alpha):
6454 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
6455 leave the default at 8GBytes), to better support Raspberry Pi
6456 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
6458 o Documentation (backport from 0.2.5.4-alpha):
6459 - Correctly document that we search for a system torrc file before
6460 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
6464 Changes in version 0.2.5.4-alpha - 2014-04-25
6465 Tor 0.2.5.4-alpha includes several security and performance
6466 improvements for clients and relays, including blacklisting authority
6467 signing keys that were used while susceptible to the OpenSSL
6468 "heartbleed" bug, fixing two expensive functions on busy relays,
6469 improved TLS ciphersuite preference lists, support for run-time
6470 hardening on compilers that support AddressSanitizer, and more work on
6471 the Linux sandbox code.
6473 There are also several usability fixes for clients (especially clients
6474 that use bridges), two new TransPort protocols supported (one on
6475 OpenBSD, one on FreeBSD), and various other bugfixes.
6477 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
6478 have accumulated many known flaws; everyone should upgrade.
6480 o Major features (security):
6481 - If you don't specify MaxMemInQueues yourself, Tor now tries to
6482 pick a good value based on your total system memory. Previously,
6483 the default was always 8 GB. You can still override the default by
6484 setting MaxMemInQueues yourself. Resolves ticket 11396.
6485 - Block authority signing keys that were used on authorities
6486 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
6487 don't have any evidence that these keys _were_ compromised; we're
6488 doing this to be prudent.) Resolves ticket 11464.
6490 o Major features (relay performance):
6491 - Speed up server-side lookups of rendezvous and introduction point
6492 circuits by using hashtables instead of linear searches. These
6493 functions previously accounted between 3 and 7% of CPU usage on
6494 some busy relays. Resolves ticket 9841.
6495 - Avoid wasting CPU when extending a circuit over a channel that is
6496 nearly out of circuit IDs. Previously, we would do a linear scan
6497 over possible circuit IDs before finding one or deciding that we
6498 had exhausted our possibilities. Now, we try at most 64 random
6499 circuit IDs before deciding that we probably won't succeed. Fixes
6500 a possible root cause of ticket 11553.
6502 o Major features (seccomp2 sandbox, Linux only):
6503 - The seccomp2 sandbox can now run a test network for multiple hours
6504 without crashing. The sandbox is still experimental, and more bugs
6505 will probably turn up. To try it, enable "Sandbox 1" on a Linux
6506 host. Resolves ticket 11351.
6507 - Strengthen sandbox code: the sandbox can now test the arguments
6508 for rename(), and blocks _sysctl() entirely. Resolves another part
6510 - When the sandbox blocks a system call, it now tries to log a stack
6511 trace before exiting. Resolves ticket 11465.
6513 o Major bugfixes (TLS cipher selection):
6514 - The relay ciphersuite list is now generated automatically based on
6515 uniform criteria, and includes all OpenSSL ciphersuites with
6516 acceptable strength and forward secrecy. Previously, we had left
6517 some perfectly fine ciphersuites unsupported due to omission or
6518 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
6519 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
6520 - Relays now trust themselves to have a better view than clients of
6521 which TLS ciphersuites are better than others. (Thanks to bug
6522 11513, the relay list is now well-considered, whereas the client
6523 list has been chosen mainly for anti-fingerprinting purposes.)
6524 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
6525 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
6526 AES128. Resolves ticket 11528.
6527 - Clients now try to advertise the same list of ciphersuites as
6528 Firefox 28. This change enables selection of (fast) GCM
6529 ciphersuites, disables some strange old ciphers, and stops
6530 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
6531 Resolves ticket 11438.
6533 o Major bugfixes (bridge client):
6534 - Avoid 60-second delays in the bootstrapping process when Tor is
6535 launching for a second time while using bridges. Fixes bug 9229;
6536 bugfix on 0.2.0.3-alpha.
6538 o Minor features (transparent proxy, *BSD):
6539 - Support FreeBSD's ipfw firewall interface for TransPort ports on
6540 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
6541 10267; patch from "yurivict".
6542 - Support OpenBSD's divert-to rules with the pf firewall for
6543 transparent proxy ports. To enable it, set "TransProxyType
6544 pf-divert". This allows Tor to run a TransPort transparent proxy
6545 port on OpenBSD 4.4 or later without root privileges. See the
6546 pf.conf(5) manual page for information on configuring pf to use
6547 divert-to rules. Closes ticket 10896; patch from Dana Koch.
6549 o Minor features (security):
6550 - New --enable-expensive-hardening option to enable security
6551 hardening options that consume nontrivial amounts of CPU and
6552 memory. Right now, this includes AddressSanitizer and UbSan, which
6553 are supported in newer versions of GCC and Clang. Closes ticket
6556 o Minor features (log verbosity):
6557 - Demote the message that we give when a flushing connection times
6558 out for too long from NOTICE to INFO. It was usually meaningless.
6559 Resolves ticket 5286.
6560 - Don't log so many notice-level bootstrapping messages at startup
6561 about downloading descriptors. Previously, we'd log a notice
6562 whenever we learned about more routers. Now, we only log a notice
6563 at every 5% of progress. Fixes bug 9963.
6564 - Warn less verbosely when receiving a malformed
6565 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
6566 - When we run out of usable circuit IDs on a channel, log only one
6567 warning for the whole channel, and describe how many circuits
6568 there were on the channel. Fixes part of ticket 11553.
6570 o Minor features (relay):
6571 - If a circuit timed out for at least 3 minutes, check if we have a
6572 new external IP address, and publish a new descriptor with the new
6573 IP address if it changed. Resolves ticket 2454.
6575 o Minor features (controller):
6576 - Make the entire exit policy available from the control port via
6577 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
6579 - Because of the fix for ticket 11396, the real limit for memory
6580 usage may no longer match the configured MaxMemInQueues value. The
6581 real limit is now exposed via GETINFO limits/max-mem-in-queues.
6583 o Minor features (bridge client):
6584 - Report a more useful failure message when we can't connect to a
6585 bridge because we don't have the right pluggable transport
6586 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
6588 o Minor features (diagnostic):
6589 - Add more log messages to diagnose bug 7164, which causes
6590 intermittent "microdesc_free() called but md was still referenced"
6591 warnings. We now include more information, to figure out why we
6592 might be cleaning a microdescriptor for being too old if it's
6593 still referenced by a live node_t object.
6595 o Minor bugfixes (client, DNSPort):
6596 - When using DNSPort, try to respond to AAAA requests with AAAA
6597 answers. Previously, we hadn't looked at the request type when
6598 deciding which answer type to prefer. Fixes bug 10468; bugfix on
6600 - When receiving a DNS query for an unsupported record type, reply
6601 with no answer rather than with a NOTIMPL error. This behavior
6602 isn't correct either, but it will break fewer client programs, we
6603 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
6606 o Minor bugfixes (exit relay):
6607 - Stop leaking memory when we successfully resolve a PTR record.
6608 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
6610 o Minor bugfixes (bridge client):
6611 - Stop accepting bridge lines containing hostnames. Doing so would
6612 cause clients to perform DNS requests on the hostnames, which was
6613 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
6614 - Avoid a 60-second delay in the bootstrapping process when a Tor
6615 client with pluggable transports re-reads its configuration at
6616 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
6618 o Minor bugfixes (client, logging during bootstrap):
6619 - Warn only once if we start logging in an unsafe way. Previously,
6620 we complain as many times as we had problems. Fixes bug 9870;
6621 bugfix on 0.2.5.1-alpha.
6622 - Only report the first fatal bootstrap error on a given OR
6623 connection. This stops us from telling the controller bogus error
6624 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
6625 - Be more helpful when trying to run sandboxed on Linux without
6626 libseccomp. Instead of saying "Sandbox is not implemented on this
6627 platform", we now explain that we need to be built with
6628 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
6629 - Avoid generating spurious warnings when starting with
6630 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
6633 o Minor bugfixes (closing OR connections):
6634 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
6635 check if it's an or_connection_t and correctly call
6636 connection_or_close_for_error() rather than
6637 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
6639 - When closing all connections on setting DisableNetwork to 1, use
6640 connection_or_close_normally() rather than closing OR connections
6641 out from under the channel layer. Fixes bug 11306; bugfix on
6644 o Minor bugfixes (controller):
6645 - Avoid sending a garbage value to the controller when a circuit is
6646 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
6648 o Minor bugfixes (tor-fw-helper):
6649 - Allow tor-fw-helper to build again by adding src/ext to its
6650 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
6652 o Minor bugfixes (bridges):
6653 - Avoid potential crashes or bad behavior when launching a
6654 server-side managed proxy with ORPort or ExtORPort temporarily
6655 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
6657 o Minor bugfixes (platform-specific):
6658 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
6659 bug 11426; bugfix on 0.2.5.3-alpha.
6660 - When dumping a malformed directory object to disk, save it in
6661 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
6663 - Don't report failures from make_socket_reuseable() on incoming
6664 sockets on OSX: this can happen when incoming connections close
6665 early. Fixes bug 10081.
6667 o Minor bugfixes (trivial memory leaks):
6668 - Fix a small memory leak when signing a directory object. Fixes bug
6669 11275; bugfix on 0.2.4.13-alpha.
6670 - Free placeholder entries in our circuit table at exit; fixes a
6671 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
6672 - Don't re-initialize a second set of OpenSSL mutexes when starting
6673 up. Previously, we'd make one set of mutexes, and then immediately
6674 replace them with another. Fixes bug 11726; bugfix on
6676 - Resolve some memory leaks found by coverity in the unit tests, on
6677 exit in tor-gencert, and on a failure to compute digests for our
6678 own keys when generating a v3 networkstatus vote. These leaks
6679 should never have affected anyone in practice.
6681 o Minor bugfixes (hidden service):
6682 - Only retry attempts to connect to a chosen rendezvous point 8
6683 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
6685 o Minor bugfixes (misc code correctness):
6686 - Fix various instances of undefined behavior in channeltls.c,
6687 tor_memmem(), and eventdns.c that would cause us to construct
6688 pointers to memory outside an allocated object. (These invalid
6689 pointers were not accessed, but C does not even allow them to
6690 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
6691 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
6692 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
6693 fix some miscellaneous errors in our tests and codebase. Fixes bug
6694 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
6695 - Always check return values for unlink, munmap, UnmapViewOfFile;
6696 check strftime return values more often. In some cases all we can
6697 do is report a warning, but this may help prevent deeper bugs from
6698 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
6700 - Fix numerous warnings from the clang "scan-build" static analyzer.
6701 Some of these are programming style issues; some of them are false
6702 positives that indicated awkward code; some are undefined behavior
6703 cases related to constructing (but not using) invalid pointers;
6704 some are assumptions about API behavior; some are (harmlessly)
6705 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
6706 correct; and one or two are genuine bugs that weren't reachable
6707 from the rest of the program. Fixes bug 8793; bugfixes on many,
6711 - Build the torify.1 manpage again. Previously, we were only trying
6712 to build it when also building tor-fw-helper. That's why we didn't
6713 notice that we'd broken the ability to build it. Fixes bug 11321;
6714 bugfix on 0.2.5.1-alpha.
6715 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
6716 11061; bugfix on 0.2.4.7-alpha.
6717 - Correctly document that we search for a system torrc file before
6718 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
6720 - Resolve warnings from Doxygen.
6722 o Code simplifications and refactoring:
6723 - Remove is_internal_IP() function. Resolves ticket 4645.
6724 - Remove unused function circuit_dump_by_chan from circuitlist.c.
6725 Closes issue 9107; patch from "marek".
6726 - Change our use of the ENUM_BF macro to avoid declarations that
6729 o Deprecated versions:
6730 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
6731 attention for some while. Directory authorities no longer accept
6732 descriptors from relays running any version of Tor prior to Tor
6733 0.2.3.16-alpha. Resolves ticket 11149.
6736 - New macros in test.h to simplify writing mock-functions for unit
6737 tests. Part of ticket 11507. Patch from Dana Koch.
6738 - Complete tests for the status.c module. Resolves ticket 11507.
6739 Patch from Dana Koch.
6742 - Remove all code for the long unused v1 directory protocol.
6743 Resolves ticket 11070.
6746 Changes in version 0.2.5.3-alpha - 2014-03-22
6747 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
6748 two new anti-DoS features for Tor relays, resolves a bug that kept
6749 SOCKS5 support for IPv6 from working, fixes several annoying usability
6750 issues for bridge users, and removes more old code for unused
6753 The Tor 0.2.5.x release series is now in patch-freeze: no feature
6754 patches not already written will be considered for inclusion in 0.2.5.x.
6756 o Major features (relay security, DoS-resistance):
6757 - When deciding whether we have run out of memory and we need to
6758 close circuits, also consider memory allocated in buffers for
6759 streams attached to each circuit.
6761 This change, which extends an anti-DoS feature introduced in
6762 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
6763 better resist more memory-based DoS attacks than before. Since the
6764 MaxMemInCellQueues option now applies to all queues, it is renamed
6765 to MaxMemInQueues. This feature fixes bug 10169.
6766 - Avoid hash-flooding denial-of-service attacks by using the secure
6767 SipHash-2-4 hash function for our hashtables. Without this
6768 feature, an attacker could degrade performance of a targeted
6769 client or server by flooding their data structures with a large
6770 number of entries to be stored at the same hash table position,
6771 thereby slowing down the Tor instance. With this feature, hash
6772 table positions are derived from a randomized cryptographic key,
6773 and an attacker cannot predict which entries will collide. Closes
6775 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
6776 the default at 8GBytes), to better support Raspberry Pi users. Fixes
6777 bug 9686; bugfix on 0.2.4.14-alpha.
6779 o Minor features (bridges, pluggable transports):
6780 - Bridges now write the SHA1 digest of their identity key
6781 fingerprint (that is, a hash of a hash of their public key) to
6782 notice-level logs, and to a new hashed-fingerprint file. This
6783 information will help bridge operators look up their bridge in
6784 Globe and similar tools. Resolves ticket 10884.
6785 - Improve the message that Tor displays when running as a bridge
6786 using pluggable transports without an Extended ORPort listener.
6787 Also, log the message in the log file too. Resolves ticket 11043.
6789 o Minor features (other):
6790 - Add a new option, PredictedPortsRelevanceTime, to control how long
6791 after having received a request to connect to a given port Tor
6792 will try to keep circuits ready in anticipation of future requests
6793 for that port. Patch from "unixninja92"; implements ticket 9176.
6794 - Generate a warning if any ports are listed in the SocksPolicy,
6795 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
6796 AuthDirBadExit options. (These options only support address
6797 ranges.) Fixes part of ticket 11108.
6798 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
6801 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
6802 - Build without warnings under clang 3.4. (We have some macros that
6803 define static functions only some of which will get used later in
6804 the module. Starting with clang 3.4, these give a warning unless the
6805 unused attribute is set on them.) Resolves ticket 10904.
6806 - Fix build warnings about missing "a2x" comment when building the
6807 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
6808 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
6810 o Minor bugfixes (client):
6811 - Improve the log message when we can't connect to a hidden service
6812 because all of the hidden service directory nodes hosting its
6813 descriptor are excluded. Improves on our fix for bug 10722, which
6814 was a bugfix on 0.2.0.10-alpha.
6815 - Raise a control port warning when we fail to connect to all of
6816 our bridges. Previously, we didn't inform the controller, and
6817 the bootstrap process would stall. Fixes bug 11069; bugfix on
6819 - Exit immediately when a process-owning controller exits.
6820 Previously, tor relays would wait for a little while after their
6821 controller exited, as if they had gotten an INT signal -- but this
6822 was problematic, since there was no feedback for the user. To do a
6823 clean shutdown, controllers should send an INT signal and give Tor
6824 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
6825 - Stop attempting to connect to bridges before our pluggable
6826 transports are configured (harmless but resulted in some erroneous
6827 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
6828 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
6829 generating incorrect SOCKS5 responses, and confusing client
6830 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
6832 o Minor bugfixes (relays and bridges):
6833 - Avoid crashing on a malformed resolv.conf file when running a
6834 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
6835 - Non-exit relays no longer launch mock DNS requests to check for
6836 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
6837 non-exit relays stopped servicing DNS requests. Fixes bug 965;
6838 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
6839 - Bridges now report complete directory request statistics. Related
6840 to bug 5824; bugfix on 0.2.2.1-alpha.
6841 - Bridges now never collect statistics that were designed for
6842 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
6843 - Stop giving annoying warning messages when we decide not to launch
6844 a pluggable transport proxy that we don't need (because there are
6845 no bridges configured to use it). Resolves ticket 5018; bugfix
6847 - Give the correct URL in the warning message when trying to run a
6848 relay on an ancient version of Windows. Fixes bug 9393.
6850 o Minor bugfixes (backtrace support):
6851 - Support automatic backtraces on more platforms by using the
6852 "-fasynchronous-unwind-tables" compiler option. This option is
6853 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
6854 is on by default and table generation is not. This doesn't yet
6855 add Windows support; only Linux, OSX, and some BSDs are affected.
6856 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
6857 - Avoid strange behavior if two threads hit failed assertions at the
6858 same time and both try to log backtraces at once. (Previously, if
6859 this had happened, both threads would have stored their intermediate
6860 results in the same buffer, and generated junk outputs.) Reported by
6861 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
6862 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
6863 0.2.5.2-alpha; patch from Nick Hopper.
6865 o Minor bugfixes (unit tests):
6866 - Fix a small bug in the unit tests that might have made the tests
6867 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
6868 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
6871 - Remove all remaining code related to version-0 hidden service
6872 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
6873 the rest of bug 10841.
6876 - Document in the manpage that "KBytes" may also be written as
6877 "kilobytes" or "KB", that "Kbits" may also be written as
6878 "kilobits", and so forth. Closes ticket 9222.
6879 - Document that the ClientOnly config option overrides ORPort.
6880 Our old explanation made ClientOnly sound as though it did
6881 nothing at all. Resolves bug 9059.
6882 - Explain that SocksPolicy, DirPolicy, and similar options don't
6883 take port arguments. Fixes the other part of ticket 11108.
6884 - Fix a comment about the rend_server_descriptor_t.protocols field
6885 to more accurately describe its range. Also, make that field
6886 unsigned, to more accurately reflect its usage. Fixes bug 9099;
6887 bugfix on 0.2.1.5-alpha.
6888 - Fix the manpage's description of HiddenServiceAuthorizeClient:
6889 the maximum client name length is 16, not 19. Fixes bug 11118;
6890 bugfix on 0.2.1.6-alpha.
6892 o Code simplifications and refactoring:
6893 - Get rid of router->address, since in all cases it was just the
6894 string representation of router->addr. Resolves ticket 5528.
6896 o Test infrastructure:
6897 - Update to the latest version of tinytest.
6898 - Improve the tinytest implementation of string operation tests so
6899 that comparisons with NULL strings no longer crash the tests; they
6900 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
6903 Changes in version 0.2.4.21 - 2014-02-28
6904 Tor 0.2.4.21 further improves security against potential adversaries who
6905 find breaking 1024-bit crypto doable, and backports several stability
6906 and robustness patches from the 0.2.5 branch.
6908 o Major features (client security):
6909 - When we choose a path for a 3-hop circuit, make sure it contains
6910 at least one relay that supports the NTor circuit extension
6911 handshake. Otherwise, there is a chance that we're building
6912 a circuit that's worth attacking by an adversary who finds
6913 breaking 1024-bit crypto doable, and that chance changes the game
6914 theory. Implements ticket 9777.
6917 - Do not treat streams that fail with reason
6918 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
6919 since it could also indicate an ENETUNREACH connection error. Fixes
6920 part of bug 10777; bugfix on 0.2.4.8-alpha.
6922 o Code simplification and refactoring:
6923 - Remove data structures which were introduced to implement the
6924 CellStatistics option: they are now redundant with the new timestamp
6925 field in the regular packed_cell_t data structure, which we did
6926 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
6929 - Always clear OpenSSL bignums before freeing them -- even bignums
6930 that don't contain secrets. Resolves ticket 10793. Patch by
6932 - Build without warnings under clang 3.4. (We have some macros that
6933 define static functions only some of which will get used later in
6934 the module. Starting with clang 3.4, these give a warning unless the
6935 unused attribute is set on them.) Resolves ticket 10904.
6936 - Update geoip and geoip6 files to the February 7 2014 Maxmind
6937 GeoLite2 Country database.
6940 - Set the listen() backlog limit to the largest actually supported
6941 on the system, not to the value in a header file. Fixes bug 9716;
6942 bugfix on every released Tor.
6943 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
6944 exit node as a NOROUTE error, not an INTERNAL error, since they
6945 can apparently happen when trying to connect to the wrong sort
6946 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
6947 - Fix build warnings about missing "a2x" comment when building the
6948 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
6949 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
6950 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
6951 not entirely remove it from the connection lists. Fixes bug 9602;
6952 bugfix on 0.2.4.4-alpha.
6953 - Fix a segmentation fault in our benchmark code when running with
6954 Fedora's OpenSSL package, or any other OpenSSL that provides
6955 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
6956 - Turn "circuit handshake stats since last time" log messages into a
6957 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
6959 o Documentation fixes:
6960 - Document that all but one DirPort entry must have the NoAdvertise
6961 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
6964 Changes in version 0.2.5.2-alpha - 2014-02-13
6965 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
6966 like the "poor random number generation" fix and the "building too many
6967 circuits" fix. It also further improves security against potential
6968 adversaries who find breaking 1024-bit crypto doable, and launches
6969 pluggable transports on demand (which gets us closer to integrating
6970 pluggable transport support by default -- not to be confused with Tor
6971 bundles enabling pluggable transports and bridges by default).
6973 o Major features (client security):
6974 - When we choose a path for a 3-hop circuit, make sure it contains
6975 at least one relay that supports the NTor circuit extension
6976 handshake. Otherwise, there is a chance that we're building
6977 a circuit that's worth attacking by an adversary who finds
6978 breaking 1024-bit crypto doable, and that chance changes the game
6979 theory. Implements ticket 9777.
6980 - Clients now look at the "usecreatefast" consensus parameter to
6981 decide whether to use CREATE_FAST or CREATE cells for the first hop
6982 of their circuit. This approach can improve security on connections
6983 where Tor's circuit handshake is stronger than the available TLS
6984 connection security levels, but the tradeoff is more computational
6985 load on guard relays. Implements proposal 221. Resolves ticket 9386.
6987 o Major features (bridges):
6988 - Don't launch pluggable transport proxies if we don't have any
6989 bridges configured that would use them. Now we can list many
6990 pluggable transports, and Tor will dynamically start one when it
6991 hears a bridge address that needs it. Resolves ticket 5018.
6992 - The bridge directory authority now assigns status flags (Stable,
6993 Guard, etc) to bridges based on thresholds calculated over all
6994 Running bridges. Now bridgedb can finally make use of its features
6995 to e.g. include at least one Stable bridge in its answers. Fixes
6998 o Major features (other):
6999 - Extend ORCONN controller event to include an "ID" parameter,
7000 and add four new controller event types CONN_BW, CIRC_BW,
7001 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
7002 The new events are emitted in private Tor networks only, with the
7003 goal of being able to better track performance and load during
7004 full-network simulations. Implements proposal 218 and ticket 7359.
7005 - On some platforms (currently: recent OSX versions, glibc-based
7006 platforms that support the ELF format, and a few other
7007 Unix-like operating systems), Tor can now dump stack traces
7008 when a crash occurs or an assertion fails. By default, traces
7009 are dumped to stderr (if possible) and to any logs that are
7010 reporting errors. Implements ticket 9299.
7013 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
7014 not entirely remove it from the connection lists. Fixes bug 9602;
7015 bugfix on 0.2.4.4-alpha.
7016 - Do not treat streams that fail with reason
7017 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
7018 since it could also indicate an ENETUNREACH connection error. Fixes
7019 part of bug 10777; bugfix on 0.2.4.8-alpha.
7021 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
7022 - Do not allow OpenSSL engines to replace the PRNG, even when
7023 HardwareAccel is set. The only default builtin PRNG engine uses
7024 the Intel RDRAND instruction to replace the entire PRNG, and
7025 ignores all attempts to seed it with more entropy. That's
7026 cryptographically stupid: the right response to a new alleged
7027 entropy source is never to discard all previously used entropy
7028 sources. Fixes bug 10402; works around behavior introduced in
7029 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
7031 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
7032 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
7033 - Avoid launching spurious extra circuits when a stream is pending.
7034 This fixes a bug where any circuit that _wasn't_ unusable for new
7035 streams would be treated as if it were, causing extra circuits to
7036 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
7038 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
7039 - No longer stop reading or writing on cpuworker connections when
7040 our rate limiting buckets go empty. Now we should handle circuit
7041 handshake requests more promptly. Resolves bug 9731.
7042 - Stop trying to bootstrap all our directory information from
7043 only our first guard. Discovered while fixing bug 9946; bugfix
7046 o Minor features (bridges, pluggable transports):
7047 - Add threshold cutoffs to the networkstatus document created by
7048 the Bridge Authority. Fixes bug 1117.
7049 - On Windows, spawn background processes using the CREATE_NO_WINDOW
7050 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
7051 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
7052 Vidalia set this option for us.) Implements ticket 10297.
7054 o Minor features (security):
7055 - Always clear OpenSSL bignums before freeing them -- even bignums
7056 that don't contain secrets. Resolves ticket 10793. Patch by
7059 o Minor features (config options and command line):
7060 - Add an --allow-missing-torrc commandline option that tells Tor to
7061 run even if the configuration file specified by -f is not available.
7062 Implements ticket 10060.
7063 - Add support for the TPROXY transparent proxying facility on Linux.
7064 See documentation for the new TransProxyType option for more
7065 details. Implementation by "thomo". Closes ticket 10582.
7067 o Minor features (controller):
7068 - Add a new "HS_DESC" controller event that reports activities
7069 related to hidden service descriptors. Resolves ticket 8510.
7070 - New "DROPGUARDS" controller command to forget all current entry
7071 guards. Not recommended for ordinary use, since replacing guards
7072 too frequently makes several attacks easier. Resolves ticket 9934;
7075 o Minor features (build):
7076 - Assume that a user using ./configure --host wants to cross-compile,
7077 and give an error if we cannot find a properly named
7078 tool-chain. Add a --disable-tool-name-check option to proceed
7079 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
7080 - If we run ./configure and the compiler recognizes -fstack-protector
7081 but the linker rejects it, warn the user about a potentially missing
7082 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
7084 o Minor features (testing):
7085 - If Python is installed, "make check" now runs extra tests beyond
7086 the unit test scripts.
7087 - When bootstrapping a test network, sometimes very few relays get
7088 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
7089 specify a set of relays which should be voted Guard regardless of
7090 their uptime or bandwidth. Addresses ticket 9206.
7092 o Minor features (log messages):
7093 - When ServerTransportPlugin is set on a bridge, Tor can write more
7094 useful statistics about bridge use in its extrainfo descriptors,
7095 but only if the Extended ORPort ("ExtORPort") is set too. Add a
7096 log message to inform the user in this case. Resolves ticket 9651.
7097 - When receiving a new controller connection, log the origin address.
7098 Resolves ticket 9698; patch from "sigpipe".
7099 - When logging OpenSSL engine status at startup, log the status of
7100 more engines. Fixes ticket 10043; patch from Joshua Datko.
7101 - Turn "circuit handshake stats since last time" log messages into a
7102 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
7104 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
7105 - Improve the circuit queue out-of-memory handler. Previously, when
7106 we ran low on memory, we'd close whichever circuits had the most
7107 queued cells. Now, we close those that have the *oldest* queued
7108 cells, on the theory that those are most responsible for us
7109 running low on memory. Based on analysis from a forthcoming paper
7110 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
7111 - Generate bootstrapping status update events correctly when fetching
7112 microdescriptors. Fixes bug 9927.
7113 - Update to the October 2 2013 Maxmind GeoLite Country database.
7115 o Minor bugfixes (clients):
7116 - When closing a channel that has already been open, do not close
7117 pending circuits that were waiting to connect to the same relay.
7118 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
7121 o Minor bugfixes (relays):
7122 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
7123 exit node as a NOROUTE error, not an INTERNAL error, since they
7124 can apparently happen when trying to connect to the wrong sort
7125 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
7127 o Minor bugfixes (bridges):
7128 - Fix a bug where the first connection works to a bridge that uses a
7129 pluggable transport with client-side parameters, but we don't send
7130 the client-side parameters on subsequent connections. (We don't
7131 use any pluggable transports with client-side parameters yet,
7132 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
7133 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
7135 o Minor bugfixes (node selection):
7136 - If ExcludeNodes is set, consider non-excluded hidden service
7137 directory servers before excluded ones. Do not consider excluded
7138 hidden service directory servers at all if StrictNodes is
7139 set. (Previously, we would sometimes decide to connect to those
7140 servers, and then realize before we initiated a connection that
7141 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
7143 - If we set the ExitNodes option but it doesn't include any nodes
7144 that have the Exit flag, we would choose not to bootstrap. Now we
7145 bootstrap so long as ExitNodes includes nodes which can exit to
7146 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
7148 o Minor bugfixes (controller and command-line):
7149 - If changing a config option via "setconf" fails in a recoverable
7150 way, we used to nonetheless write our new control ports to the
7151 file described by the "ControlPortWriteToFile" option. Now we only
7152 write out that file if we successfully switch to the new config
7153 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
7154 - When a command-line option such as --version or --help that
7155 ordinarily implies --hush appears on the command line along with
7156 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
7157 only if it appeared later on the command line. Fixes bug 9578;
7158 bugfix on 0.2.5.1-alpha.
7160 o Minor bugfixes (code correctness):
7161 - Previously we used two temporary files when writing descriptors to
7162 disk; now we only use one. Fixes bug 1376.
7163 - Remove an erroneous (but impossible and thus harmless) pointer
7164 comparison that would have allowed compilers to skip a bounds
7165 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
7166 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
7167 - Fix an always-true assertion in pluggable transports code so it
7168 actually checks what it was trying to check. Fixes bug 10046;
7169 bugfix on 0.2.3.9-alpha. Found by "dcb".
7171 o Minor bugfixes (protocol correctness):
7172 - When receiving a VERSIONS cell with an odd number of bytes, close
7173 the connection immediately since the cell is malformed. Fixes bug
7174 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
7177 o Minor bugfixes (build):
7178 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
7179 turned off (that is, without support for v2 link handshakes). Fixes
7180 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
7181 - Fix compilation warnings and startup issues when running with
7182 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
7184 - Fix compilation on Solaris 9, which didn't like us having an
7185 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
7187 o Minor bugfixes (testing):
7188 - Fix a segmentation fault in our benchmark code when running with
7189 Fedora's OpenSSL package, or any other OpenSSL that provides
7190 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
7192 o Minor bugfixes (log messages):
7193 - Fix a bug where clients using bridges would report themselves
7194 as 50% bootstrapped even without a live consensus document.
7195 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
7196 - Suppress a warning where, if there's only one directory authority
7197 in the network, we would complain that votes and signatures cannot
7198 be uploaded to other directory authorities. Fixes bug 10842;
7199 bugfix on 0.2.2.26-beta.
7200 - Report bootstrapping progress correctly when we're downloading
7201 microdescriptors. We had updated our "do we have enough microdescs
7202 to begin building circuits?" logic most recently in 0.2.4.10-alpha
7203 (see bug 5956), but we left the bootstrap status event logic at
7204 "how far through getting 1/4 of them are we?" Fixes bug 9958;
7205 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
7207 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
7208 - Avoid a crash bug when starting with a corrupted microdescriptor
7209 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
7210 - If we fail to dump a previously cached microdescriptor to disk, avoid
7211 freeing duplicate data later on. Fixes bug 10423; bugfix on
7212 0.2.4.13-alpha. Spotted by "bobnomnom".
7214 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
7215 - Correctly log long IPv6 exit policies, instead of truncating them
7216 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
7217 - Our default TLS ecdhe groups were backwards: we meant to be using
7218 P224 for relays (for performance win) and P256 for bridges (since
7219 it is more common in the wild). Instead we had it backwards. After
7220 reconsideration, we decided that the default should be P256 on all
7221 hosts, since its security is probably better, and since P224 is
7222 reportedly used quite little in the wild. Found by "skruffy" on
7223 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
7224 - Free directory authority certificate download statuses on exit
7225 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
7227 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
7228 - If the guard we choose first doesn't answer, we would try the
7229 second guard, but once we connected to the second guard we would
7230 abandon it and retry the first one, slowing down bootstrapping.
7231 The fix is to treat all our initially chosen guards as acceptable
7232 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
7233 - Fix an assertion failure that would occur when disabling the
7234 ORPort setting on a running Tor process while accounting was
7235 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
7236 - When examining the list of network interfaces to find our address,
7237 do not consider non-running or disabled network interfaces. Fixes
7238 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
7239 - Avoid an off-by-one error when checking buffer boundaries when
7240 formatting the exit status of a pluggable transport helper.
7241 This is probably not an exploitable bug, but better safe than
7242 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
7245 o Removed code and features:
7246 - Clients now reject any directory authority certificates lacking
7247 a dir-key-crosscert element. These have been included since
7248 0.2.1.9-alpha, so there's no real reason for them to be optional
7249 any longer. Completes proposal 157. Resolves ticket 10162.
7250 - Remove all code that existed to support the v2 directory system,
7251 since there are no longer any v2 directory authorities. Resolves
7253 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
7254 options, which were used for designating authorities as "Hidden
7255 service authorities". There has been no use of hidden service
7256 authorities since 0.2.2.1-alpha, when we stopped uploading or
7257 downloading v0 hidden service descriptors. Fixes bug 10881; also
7258 part of a fix for bug 10841.
7260 o Code simplification and refactoring:
7261 - Remove some old fallback code designed to keep Tor clients working
7262 in a network with only two working relays. Elsewhere in the code we
7263 have long since stopped supporting such networks, so there wasn't
7264 much point in keeping it around. Addresses ticket 9926.
7265 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
7266 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
7267 - Remove data structures which were introduced to implement the
7268 CellStatistics option: they are now redundant with the addition
7269 of a timestamp to the regular packed_cell_t data structure, which
7270 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
7273 o Documentation (man page) fixes:
7274 - Update manpage to describe some of the files you can expect to
7275 find in Tor's DataDirectory. Addresses ticket 9839.
7276 - Document that all but one DirPort entry must have the NoAdvertise
7277 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
7279 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
7280 - Clarify the usage and risks of setting the ContactInfo torrc line
7281 for your relay or bridge. Resolves ticket 9854.
7282 - Add anchors to the manpage so we can link to the html version of
7283 the documentation for specific options. Resolves ticket 9866.
7284 - Replace remaining references to DirServer in man page and
7285 log entries. Resolves ticket 10124.
7288 - Make the "tor-gencert" tool used by directory authority operators
7289 create 2048-bit signing keys by default (rather than 1024-bit, since
7290 1024-bit is uncomfortably small these days). Addresses ticket 10324.
7293 Changes in version 0.2.4.20 - 2013-12-22
7294 Tor 0.2.4.20 fixes potentially poor random number generation for users
7295 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
7296 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
7297 and 4) have no state file in their DataDirectory (as would happen on
7298 first start). Users who generated relay or hidden service identity
7299 keys in such a situation should discard them and generate new ones.
7301 This release also fixes a logic error that caused Tor clients to build
7302 many more preemptive circuits than they actually need.
7305 - Do not allow OpenSSL engines to replace the PRNG, even when
7306 HardwareAccel is set. The only default builtin PRNG engine uses
7307 the Intel RDRAND instruction to replace the entire PRNG, and
7308 ignores all attempts to seed it with more entropy. That's
7309 cryptographically stupid: the right response to a new alleged
7310 entropy source is never to discard all previously used entropy
7311 sources. Fixes bug 10402; works around behavior introduced in
7312 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
7314 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
7315 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
7316 - Avoid launching spurious extra circuits when a stream is pending.
7317 This fixes a bug where any circuit that _wasn't_ unusable for new
7318 streams would be treated as if it were, causing extra circuits to
7319 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
7322 - Avoid a crash bug when starting with a corrupted microdescriptor
7323 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
7324 - If we fail to dump a previously cached microdescriptor to disk, avoid
7325 freeing duplicate data later on. Fixes bug 10423; bugfix on
7326 0.2.4.13-alpha. Spotted by "bobnomnom".
7329 Changes in version 0.2.4.19 - 2013-12-11
7330 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
7331 (1986-2013). Aaron worked on diverse projects including helping to guide
7332 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
7333 transparency to the U.S government's PACER documents, and contributing
7334 design and development for Tor and Tor2Web. Aaron was one of the latest
7335 martyrs in our collective fight for civil liberties and human rights,
7336 and his death is all the more painful because he was one of us.
7338 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
7339 a new circuit handshake and link encryption that use ECC to provide
7340 better security and efficiency; makes relays better manage circuit
7341 creation requests; uses "directory guards" to reduce client enumeration
7342 risks; makes bridges collect and report statistics about the pluggable
7343 transports they support; cleans up and improves our geoip database;
7344 gets much closer to IPv6 support for clients, bridges, and relays; makes
7345 directory authorities use measured bandwidths rather than advertised
7346 ones when computing flags and thresholds; disables client-side DNS
7347 caching to reduce tracking risks; and fixes a big bug in bridge
7348 reachability testing. This release introduces two new design
7349 abstractions in the code: a new "channel" abstraction between circuits
7350 and or_connections to allow for implementing alternate relay-to-relay
7351 transports, and a new "circuitmux" abstraction storing the queue of
7352 circuits for a channel. The release also includes many stability,
7353 security, and privacy fixes.
7356 Changes in version 0.2.4.18-rc - 2013-11-16
7357 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
7358 series. It takes a variety of fixes from the 0.2.5.x branch to improve
7359 stability, performance, and better handling of edge cases.
7362 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
7363 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
7364 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
7365 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
7366 them to solve bug 6033.)
7369 - No longer stop reading or writing on cpuworker connections when
7370 our rate limiting buckets go empty. Now we should handle circuit
7371 handshake requests more promptly. Resolves bug 9731.
7372 - If we are unable to save a microdescriptor to the journal, do not
7373 drop it from memory and then reattempt downloading it. Fixes bug
7374 9645; bugfix on 0.2.2.6-alpha.
7375 - Stop trying to bootstrap all our directory information from
7376 only our first guard. Discovered while fixing bug 9946; bugfix
7378 - The new channel code sometimes lost track of in-progress circuits,
7379 causing long-running clients to stop building new circuits. The
7380 fix is to always call circuit_n_chan_done(chan, 0) from
7381 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
7383 o Minor bugfixes (on 0.2.4.x):
7384 - Correctly log long IPv6 exit policies, instead of truncating them
7385 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
7386 - Our default TLS ecdhe groups were backwards: we meant to be using
7387 P224 for relays (for performance win) and P256 for bridges (since
7388 it is more common in the wild). Instead we had it backwards. After
7389 reconsideration, we decided that the default should be P256 on all
7390 hosts, since its security is probably better, and since P224 is
7391 reportedly used quite little in the wild. Found by "skruffy" on
7392 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
7393 - Free directory authority certificate download statuses on exit
7394 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
7396 o Minor bugfixes (on 0.2.3.x and earlier):
7397 - If the guard we choose first doesn't answer, we would try the
7398 second guard, but once we connected to the second guard we would
7399 abandon it and retry the first one, slowing down bootstrapping.
7400 The fix is to treat all our initially chosen guards as acceptable
7401 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
7402 - Fix an assertion failure that would occur when disabling the
7403 ORPort setting on a running Tor process while accounting was
7404 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
7405 - When examining the list of network interfaces to find our address,
7406 do not consider non-running or disabled network interfaces. Fixes
7407 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
7408 - Avoid an off-by-one error when checking buffer boundaries when
7409 formatting the exit status of a pluggable transport helper.
7410 This is probably not an exploitable bug, but better safe than
7411 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
7414 o Minor features (protecting client timestamps):
7415 - Clients no longer send timestamps in their NETINFO cells. These were
7416 not used for anything, and they provided one small way for clients
7417 to be distinguished from each other as they moved from network to
7418 network or behind NAT. Implements part of proposal 222.
7419 - Clients now round timestamps in INTRODUCE cells down to the nearest
7420 10 minutes. If a new Support022HiddenServices option is set to 0, or
7421 if it's set to "auto" and the feature is disabled in the consensus,
7422 the timestamp is sent as 0 instead. Implements part of proposal 222.
7423 - Stop sending timestamps in AUTHENTICATE cells. This is not such
7424 a big deal from a security point of view, but it achieves no actual
7425 good purpose, and isn't needed. Implements part of proposal 222.
7426 - Reduce down accuracy of timestamps in hidden service descriptors.
7427 Implements part of proposal 222.
7429 o Minor features (other):
7430 - Improve the circuit queue out-of-memory handler. Previously, when
7431 we ran low on memory, we'd close whichever circuits had the most
7432 queued cells. Now, we close those that have the *oldest* queued
7433 cells, on the theory that those are most responsible for us
7434 running low on memory. Based on analysis from a forthcoming paper
7435 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
7436 - Generate bootstrapping status update events correctly when fetching
7437 microdescriptors. Fixes bug 9927.
7438 - Update to the October 2 2013 Maxmind GeoLite Country database.
7440 o Documentation fixes:
7441 - Clarify the usage and risks of setting the ContactInfo torrc line
7442 for your relay or bridge. Resolves ticket 9854.
7443 - Add anchors to the manpage so we can link to the html version of
7444 the documentation for specific options. Resolves ticket 9866.
7445 - Replace remaining references to DirServer in man page and
7446 log entries. Resolves ticket 10124.
7449 Changes in version 0.2.5.1-alpha - 2013-10-02
7450 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
7451 on Linux, allows bridges that offer pluggable transports to report usage
7452 statistics, fixes many issues to make testing easier, and provides
7453 a pile of minor features and bugfixes that have been waiting for a
7454 release of the new branch.
7456 This is the first alpha release in a new series, so expect there to
7457 be bugs. Users who would rather test out a more stable branch should
7458 stay with 0.2.4.x for now.
7460 o Major features (security):
7461 - Use the seccomp2 syscall filtering facility on Linux to limit
7462 which system calls Tor can invoke. This is an experimental,
7463 Linux-only feature to provide defense-in-depth against unknown
7464 attacks. To try turning it on, set "Sandbox 1" in your torrc
7465 file. Please be ready to report bugs. We hope to add support
7466 for better sandboxing in the future, including more fine-grained
7467 filters, better division of responsibility, and support for more
7468 platforms. This work has been done by Cristian-Matei Toader for
7469 Google Summer of Code.
7470 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
7471 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
7472 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
7473 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
7474 them to solve bug 6033.)
7476 o Major features (other):
7477 - Add support for passing arguments to managed pluggable transport
7478 proxies. Implements ticket 3594.
7479 - Bridges now track GeoIP information and the number of their users
7480 even when pluggable transports are in use, and report usage
7481 statistics in their extra-info descriptors. Resolves tickets 4773
7483 - Make testing Tor networks bootstrap better: lower directory fetch
7484 retry schedules and maximum interval without directory requests,
7485 and raise maximum download tries. Implements ticket 6752.
7486 - Add make target 'test-network' to run tests on a Chutney network.
7487 Implements ticket 8530.
7488 - The ntor handshake is now on-by-default, no matter what the
7489 directory authorities recommend. Implements ticket 8561.
7492 - Instead of writing destroy cells directly to outgoing connection
7493 buffers, queue them and intersperse them with other outgoing cells.
7494 This can prevent a set of resource starvation conditions where too
7495 many pending destroy cells prevent data cells from actually getting
7496 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
7497 bugfix on 0.2.0.1-alpha.
7498 - If we are unable to save a microdescriptor to the journal, do not
7499 drop it from memory and then reattempt downloading it. Fixes bug
7500 9645; bugfix on 0.2.2.6-alpha.
7501 - The new channel code sometimes lost track of in-progress circuits,
7502 causing long-running clients to stop building new circuits. The
7503 fix is to always call circuit_n_chan_done(chan, 0) from
7504 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
7507 - Tor now builds each source file in two modes: a mode that avoids
7508 exposing identifiers needlessly, and another mode that exposes
7509 more identifiers for testing. This lets the compiler do better at
7510 optimizing the production code, while enabling us to take more
7511 radical measures to let the unit tests test things.
7512 - The production builds no longer include functions used only in
7513 the unit tests; all functions exposed from a module only for
7514 unit-testing are now static in production builds.
7515 - Add an --enable-coverage configuration option to make the unit
7516 tests (and a new src/or/tor-cov target) to build with gcov test
7520 - We now have rudimentary function mocking support that our unit
7521 tests can use to test functions in isolation. Function mocking
7522 lets the tests temporarily replace a function's dependencies with
7523 stub functions, so that the tests can check the function without
7524 invoking the other functions it calls.
7525 - Add more unit tests for the <circid,channel>->circuit map, and
7526 the destroy-cell-tracking code to fix bug 7912.
7527 - Unit tests for failing cases of the TAP onion handshake.
7528 - More unit tests for address-manipulation functions.
7530 o Minor features (protecting client timestamps):
7531 - Clients no longer send timestamps in their NETINFO cells. These were
7532 not used for anything, and they provided one small way for clients
7533 to be distinguished from each other as they moved from network to
7534 network or behind NAT. Implements part of proposal 222.
7535 - Clients now round timestamps in INTRODUCE cells down to the nearest
7536 10 minutes. If a new Support022HiddenServices option is set to 0, or
7537 if it's set to "auto" and the feature is disabled in the consensus,
7538 the timestamp is sent as 0 instead. Implements part of proposal 222.
7539 - Stop sending timestamps in AUTHENTICATE cells. This is not such
7540 a big deal from a security point of view, but it achieves no actual
7541 good purpose, and isn't needed. Implements part of proposal 222.
7542 - Reduce down accuracy of timestamps in hidden service descriptors.
7543 Implements part of proposal 222.
7545 o Minor features (config options):
7546 - Config (torrc) lines now handle fingerprints which are missing
7547 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
7548 - Support a --dump-config option to print some or all of the
7549 configured options. Mainly useful for debugging the command-line
7550 option parsing code. Helps resolve ticket 4647.
7551 - Raise awareness of safer logging: notify user of potentially
7552 unsafe config options, like logging more verbosely than severity
7553 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
7554 - Add a new configuration option TestingV3AuthVotingStartOffset
7555 that bootstraps a network faster by changing the timing for
7556 consensus votes. Addresses ticket 8532.
7557 - Add a new torrc option "ServerTransportOptions" that allows
7558 bridge operators to pass configuration parameters to their
7559 pluggable transports. Resolves ticket 8929.
7560 - The config (torrc) file now accepts bandwidth and space limits in
7561 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
7562 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
7565 o Minor features (build):
7566 - Add support for `--library-versions` flag. Implements ticket 6384.
7567 - Return the "unexpected sendme" warnings to a warn severity, but make
7568 them rate limited, to help diagnose ticket 8093.
7569 - Detect a missing asciidoc, and warn the user about it, during
7570 configure rather than at build time. Fixes issue 6506. Patch from
7573 o Minor features (other):
7574 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
7575 sockets in a single system call. Implements ticket 5129.
7576 - Log current accounting state (bytes sent and received + remaining
7577 time for the current accounting period) in the relay's heartbeat
7578 message. Implements ticket 5526; patch from Peter Retzlaff.
7579 - Implement the TRANSPORT_LAUNCHED control port event that
7580 notifies controllers about new launched pluggable
7581 transports. Resolves ticket 5609.
7582 - If we're using the pure-C 32-bit curve25519_donna implementation
7583 of curve25519, build it with the -fomit-frame-pointer option to
7584 make it go faster on register-starved hosts. This improves our
7585 handshake performance by about 6% on i386 hosts without nacl.
7587 - Update to the September 4 2013 Maxmind GeoLite Country database.
7590 - Set the listen() backlog limit to the largest actually supported
7591 on the system, not to the value in a header file. Fixes bug 9716;
7592 bugfix on every released Tor.
7593 - No longer accept malformed http headers when parsing urls from
7594 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
7595 bugfix on 0.0.6pre1.
7596 - In munge_extrainfo_into_routerinfo(), check the return value of
7597 memchr(). This would have been a serious issue if we ever passed
7598 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
7600 - On the chance that somebody manages to build Tor on a
7601 platform where time_t is unsigned, correct the way that
7602 microdesc_add_to_cache() handles negative time arguments.
7603 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
7604 - Reject relative control socket paths and emit a warning. Previously,
7605 single-component control socket paths would be rejected, but Tor
7606 would not log why it could not validate the config. Fixes bug 9258;
7607 bugfix on 0.2.3.16-alpha.
7609 o Minor bugfixes (command line):
7610 - Use a single command-line parser for parsing torrc options on the
7611 command line and for finding special command-line options to avoid
7612 inconsistent behavior for torrc option arguments that have the same
7613 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
7615 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
7616 9573; bugfix on 0.0.9pre5.
7618 o Minor fixes (build, auxiliary programs):
7619 - Stop preprocessing the "torify" script with autoconf, since
7620 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
7622 - The tor-fw-helper program now follows the standard convention and
7623 exits with status code "0" on success. Fixes bug 9030; bugfix on
7624 0.2.3.1-alpha. Patch by Arlo Breault.
7625 - Corrected ./configure advice for what openssl dev package you should
7626 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
7628 o Minor code improvements:
7629 - Remove constants and tests for PKCS1 padding; it's insecure and
7630 shouldn't be used for anything new. Fixes bug 8792; patch
7632 - Remove instances of strcpy() from the unit tests. They weren't
7633 hurting anything, since they were only in the unit tests, but it's
7634 embarassing to have strcpy() in the code at all, and some analysis
7635 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
7636 0.2.3.8-alpha. Patch from Arlo Breault.
7639 - Remove migration code from when we renamed the "cached-routers"
7640 file to "cached-descriptors" back in 0.2.0.8-alpha. This
7641 incidentally resolves ticket 6502 by cleaning up the related code
7642 a bit. Patch from Akshay Hebbar.
7644 o Code simplification and refactoring:
7645 - Extract the common duplicated code for creating a subdirectory
7646 of the data directory and writing to a file in it. Fixes ticket
7647 4282; patch from Peter Retzlaff.
7648 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
7649 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
7650 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
7651 - Add a set of accessor functions for the circuit timeout data
7652 structure. Fixes ticket 6153; patch from "piet".
7653 - Clean up exit paths from connection_listener_new(). Closes ticket
7654 8789. Patch from Arlo Breault.
7655 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
7656 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
7657 - Use a doubly-linked list to implement the global circuit list.
7658 Resolves ticket 9108. Patch from Marek Majkowski.
7659 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
7662 Changes in version 0.2.4.17-rc - 2013-09-05
7663 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
7664 series. It adds an emergency step to help us tolerate the massive
7665 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
7666 circuit-level handshakes now effectively jump the queue compared to
7667 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
7668 big bug hindering bridge reachability tests.
7671 - Relays now process the new "NTor" circuit-level handshake requests
7672 with higher priority than the old "TAP" circuit-level handshake
7673 requests. We still process some TAP requests to not totally starve
7674 0.2.3 clients when NTor becomes popular. A new consensus parameter
7675 "NumNTorsPerTAP" lets us tune the balance later if we need to.
7676 Implements ticket 9574.
7679 - If the circuit build timeout logic is disabled (via the consensus,
7680 or because we are an authority), then don't build testing circuits.
7681 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
7682 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
7683 previously they did not, which prevented them from receiving
7684 successful connections from relays for self-test or bandwidth
7685 testing. Also, when a relay is extending a circuit to a bridge,
7686 it needs to send a NETINFO cell, even when the bridge hasn't sent
7687 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
7688 - If the time to download the next old-style networkstatus is in
7689 the future, do not decline to consider whether to download the
7690 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
7694 - Avoid double-closing the listener socket in our socketpair()
7695 replacement (used on Windows) in the case where the addresses on
7696 our opened sockets don't match what we expected. Fixes bug 9400;
7697 bugfix on 0.0.2pre7. Found by Coverity.
7699 o Minor fixes (config options):
7700 - Avoid overflows when the user sets MaxCircuitDirtiness to a
7701 ridiculously high value, by imposing a (ridiculously high) 30-day
7702 maximum on MaxCircuitDirtiness.
7703 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
7704 message is logged at notice, not at info.
7705 - Warn and fail if a server is configured not to advertise any
7706 ORPorts at all. (We need *something* to put in our descriptor,
7707 or we just won't work.)
7710 - Track how many "TAP" and "NTor" circuit handshake requests we get,
7711 and how many we complete, and log it every hour to help relay
7712 operators follow trends in network load. Addresses ticket 9658.
7713 - Update to the August 7 2013 Maxmind GeoLite Country database.
7716 Changes in version 0.2.4.16-rc - 2013-08-10
7717 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
7718 series. It fixes several crash bugs in the 0.2.4 branch.
7721 - Fix a bug in the voting algorithm that could yield incorrect results
7722 when a non-naming authority declared too many flags. Fixes bug 9200;
7723 bugfix on 0.2.0.3-alpha.
7724 - Fix an uninitialized read that could in some cases lead to a remote
7725 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
7726 Anybody running a hidden service on the experimental 0.2.4.x
7727 branch should upgrade. (This is, so far as we know, unrelated to
7729 - Avoid an assertion failure when processing DNS replies without the
7730 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
7731 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
7732 0.2.4.15-rc. Found by stem integration tests.
7735 - Fix an invalid memory read that occured when a pluggable
7736 transport proxy failed its configuration protocol.
7737 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
7738 - When evaluating whether to use a connection that we haven't
7739 decided is canonical using a recent link protocol version,
7740 decide that it's canonical only if it used address _does_
7741 match the desired address. Fixes bug 9309; bugfix on
7742 0.2.4.4-alpha. Reported by skruffy.
7743 - Make the default behavior of NumDirectoryGuards be to track
7744 NumEntryGuards. Now a user who changes only NumEntryGuards will get
7745 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
7746 - Fix a spurious compilation warning with some older versions of
7747 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
7750 - Update to the July 3 2013 Maxmind GeoLite Country database.
7753 Changes in version 0.2.4.15-rc - 2013-07-01
7754 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
7755 series. It fixes a few smaller bugs, but generally appears stable.
7756 Please test it and let us know whether it is!
7759 - When receiving a new configuration file via the control port's
7760 LOADCONF command, do not treat the defaults file as absent.
7761 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
7764 - Issue a warning when running with the bufferevents backend enabled.
7765 It's still not stable, and people should know that they're likely
7766 to hit unexpected problems. Closes ticket 9147.
7769 Changes in version 0.2.4.14-alpha - 2013-06-18
7770 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
7771 present in 0.2.4.13-alpha.
7774 - When we have too much memory queued in circuits (according to a new
7775 MaxMemInCellQueues option), close the circuits consuming the most
7776 memory. This prevents us from running out of memory as a relay if
7777 circuits fill up faster than they can be drained. Fixes bug 9063;
7778 bugfix on the 54th commit of Tor. This bug is a further fix beyond
7779 bug 6252, whose fix was merged into 0.2.3.21-rc.
7781 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
7782 where we tried to solve this issue simply by imposing an upper limit
7783 on the number of queued cells for a single circuit. That approach
7784 proved to be problematic, since there are ways to provoke clients to
7785 send a number of cells in excess of any such reasonable limit. Fixes
7786 bug 9072; bugfix on 0.2.4.13-alpha.
7788 - Limit hidden service descriptors to at most ten introduction
7789 points, to slow one kind of guard enumeration. Fixes bug 9002;
7790 bugfix on 0.1.1.11-alpha.
7793 Changes in version 0.2.4.13-alpha - 2013-06-14
7794 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
7795 vulnerabilities, makes socks5 username/password circuit isolation
7796 actually actually work (this time for sure!), and cleans up a bunch
7797 of other issues in preparation for a release candidate.
7799 o Major bugfixes (robustness):
7800 - Close any circuit that has too many cells queued on it. Fixes
7801 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
7802 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
7803 - Prevent the get_freelists() function from running off the end of
7804 the list of freelists if it somehow gets an unrecognized
7805 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
7807 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
7808 when an exit connection with optimistic data succeeds immediately
7809 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
7811 - Fix a directory authority crash bug when building a consensus
7812 using an older consensus as its basis. Fixes bug 8833. Bugfix
7816 - Avoid a memory leak where we would leak a consensus body when we
7817 find that a consensus which we couldn't previously verify due to
7818 missing certificates is now verifiable. Fixes bug 8719; bugfix
7820 - We used to always request authority certificates by identity digest,
7821 meaning we'd get the newest one even when we wanted one with a
7822 different signing key. Then we would complain about being given
7823 a certificate we already had, and never get the one we really
7824 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
7825 resource to request the one we want. Fixes bug 5595; bugfix on
7827 - Follow the socks5 protocol when offering username/password
7828 authentication. The fix for bug 8117 exposed this bug, and it
7829 turns out real-world applications like Pidgin do care. Bugfix on
7830 0.2.3.2-alpha; fixes bug 8879.
7831 - Prevent failures on Windows Vista and later when rebuilding the
7832 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
7833 bugfix on 0.2.4.12-alpha.
7836 - Fix an impossible buffer overrun in the AES unit tests. Fixes
7837 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
7838 - If for some reason we fail to write a microdescriptor while
7839 rebuilding the cache, do not let the annotations from that
7840 microdescriptor linger in the cache file, and do not let the
7841 microdescriptor stay recorded as present in its old location.
7842 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
7843 - Fix a memory leak that would occur whenever a configuration
7844 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
7845 - Paste the description for PathBias parameters from the man
7846 page into or.h, so the code documents them too. Fixes bug 7982;
7847 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
7848 - Relays now treat a changed IPv6 ORPort as sufficient reason to
7849 publish an updated descriptor. Fixes bug 6026; bugfix on
7851 - When launching a resolve request on behalf of an AF_UNIX control
7852 socket, omit the address field of the new entry connection, used in
7853 subsequent controller events, rather than letting tor_dup_addr()
7854 set it to "<unknown address type>". Fixes bug 8639; bugfix on
7857 o Minor bugfixes (log messages):
7858 - Fix a scaling issue in the path bias accounting code that
7859 resulted in "Bug:" log messages from either
7860 pathbias_scale_close_rates() or pathbias_count_build_success().
7861 This represents a bugfix on a previous bugfix: the original fix
7862 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
7864 - Give a less useless error message when the user asks for an IPv4
7865 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
7869 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
7870 to tolerate bug 8093 for now.
7871 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
7872 in directory authority votes to describe whether they have enough
7873 measured bandwidths to ignore advertised (relay descriptor)
7874 bandwidth claims. Resolves ticket 8711.
7875 - Update to the June 5 2013 Maxmind GeoLite Country database.
7877 o Removed documentation:
7878 - Remove some of the older contents of doc/ as obsolete; move others
7879 to torspec.git. Fixes bug 8965.
7881 o Code simplification and refactoring:
7882 - Avoid using character buffers when constructing most directory
7883 objects: this approach was unwieldy and error-prone. Instead,
7884 build smartlists of strings, and concatenate them when done.
7887 Changes in version 0.2.4.12-alpha - 2013-04-18
7888 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
7889 process for lengthening the guard rotation period, makes directory
7890 authority opinions in the consensus a bit less gameable, makes socks5
7891 username/password circuit isolation actually work, and fixes a wide
7892 variety of other issues.
7895 - Raise the default time that a client keeps an entry guard from
7896 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
7897 2012 paper. (We would make it even longer, but we need better client
7898 load balancing first.) Also, make the guard lifetime controllable
7899 via a new GuardLifetime torrc option and a GuardLifetime consensus
7900 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
7901 - Directory authorities now prefer using measured bandwidths to
7902 advertised ones when computing flags and thresholds. Resolves
7904 - Directory authorities that have more than a threshold number
7905 of relays with measured bandwidths now treat relays with unmeasured
7906 bandwidths as having bandwidth 0. Resolves ticket 8435.
7908 o Major bugfixes (assert / resource use):
7909 - Avoid a bug where our response to TLS renegotiation under certain
7910 network conditions could lead to a busy-loop, with 100% CPU
7911 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
7912 - Avoid an assertion when we discover that we'd like to write a cell
7913 onto a closing connection: just discard the cell. Fixes another
7914 case of bug 7350; bugfix on 0.2.4.4-alpha.
7916 o Major bugfixes (client-side privacy):
7917 - When we mark a circuit as unusable for new circuits, have it
7918 continue to be unusable for new circuits even if MaxCircuitDirtiness
7919 is increased too much at the wrong time, or the system clock jumps
7920 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
7921 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
7922 which have resolved to internal addresses") is set, apply that
7923 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
7924 - When an exit relay rejects a stream with reason "exit policy", but
7925 we only know an exit policy summary (e.g. from the microdesc
7926 consensus) for it, do not mark the relay as useless for all exiting.
7927 Instead, mark just the circuit as unsuitable for that particular
7928 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
7929 - Allow applications to get proper stream isolation with
7930 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
7931 username/password authentication also offer "no authentication". Tor
7932 had previously preferred "no authentication", so the applications
7933 never actually sent Tor their auth details. Now Tor selects
7934 username/password authentication if it's offered. You can disable
7935 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
7936 bug 8117; bugfix on 0.2.3.3-alpha.
7938 o Major bugfixes (other):
7939 - When unable to find any working directory nodes to use as a
7940 directory guard, give up rather than adding the same non-working
7941 nodes to the directory guard list over and over. Fixes bug 8231;
7942 bugfix on 0.2.4.8-alpha.
7945 - Reject as invalid most directory objects containing a NUL.
7946 Belt-and-suspender fix for bug 8037.
7947 - In our testsuite, create temporary directories with a bit more
7948 entropy in their name to make name collisions less likely. Fixes
7950 - Add CACHED keyword to ADDRMAP events in the control protocol
7951 to indicate whether a DNS result will be cached or not. Resolves
7953 - Update to the April 3 2013 Maxmind GeoLite Country database.
7955 o Minor features (build):
7956 - Detect and reject attempts to build Tor with threading support
7957 when OpenSSL has been compiled without threading support.
7959 - Clarify that when autoconf is checking for nacl, it is checking
7960 specifically for nacl with a fast curve25519 implementation.
7962 - Warn if building on a platform with an unsigned time_t: there
7963 are too many places where Tor currently assumes that time_t can
7964 hold negative values. We'd like to fix them all, but probably
7967 o Minor bugfixes (build):
7968 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
7969 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
7970 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
7971 - Add the old src/or/micro-revision.i filename to CLEANFILES.
7972 On the off chance that somebody has one, it will go away as soon
7973 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
7974 - Build Tor correctly on 32-bit platforms where the compiler can build
7975 but not run code using the "uint128_t" construction. Fixes bug 8587;
7976 bugfix on 0.2.4.8-alpha.
7977 - Fix compilation warning with some versions of clang that would
7978 prefer the -Wswitch-enum compiler flag to warn about switch
7979 statements with missing enum values, even if those switch
7980 statements have a "default:" statement. Fixes bug 8598; bugfix
7983 o Minor bugfixes (protocol):
7984 - Fix the handling of a TRUNCATE cell when it arrives while the
7985 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
7986 - Fix a misframing issue when reading the version numbers in a
7987 VERSIONS cell. Previously we would recognize [00 01 00 02] as
7988 'version 1, version 2, and version 0x100', when it should have
7989 only included versions 1 and 2. Fixes bug 8059; bugfix on
7990 0.2.0.10-alpha. Reported pseudonymously.
7991 - Make the format and order of STREAM events for DNS lookups
7992 consistent among the various ways to launch DNS lookups. Fixes
7993 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
7994 - Correct our check for which versions of Tor support the EXTEND2
7995 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
7996 later, when support was really added in version 0.2.4.8-alpha.
7997 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
7999 o Minor bugfixes (other):
8000 - Correctly store microdescriptors and extrainfo descriptors with
8001 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
8002 Bug reported by "cypherpunks".
8003 - Increase the width of the field used to remember a connection's
8004 link protocol version to two bytes. Harmless for now, since the
8005 only currently recognized versions are one byte long. Reported
8006 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
8007 - If the state file's path bias counts are invalid (presumably from a
8008 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
8009 additional checks and log messages to the scaling of Path Bias
8010 counts, in case there still are remaining issues with scaling.
8011 Should help resolve bug 8235.
8012 - Eliminate several instances where we use "Nickname=ID" to refer to
8013 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
8014 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
8015 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
8017 o Minor bugfixes (syscalls):
8018 - Always check the return values of functions fcntl() and
8019 setsockopt(). We don't believe these are ever actually failing in
8020 practice, but better safe than sorry. Also, checking these return
8021 values should please analysis tools like Coverity. Patch from
8022 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
8023 - Use direct writes rather than stdio when building microdescriptor
8024 caches, in an attempt to mitigate bug 8031, or at least make it
8027 o Minor bugfixes (config):
8028 - When rejecting a configuration because we were unable to parse a
8029 quoted string, log an actual error message. Fixes bug 7950; bugfix
8031 - Behave correctly when the user disables LearnCircuitBuildTimeout
8032 but doesn't tell us what they would like the timeout to be. Fixes
8033 bug 6304; bugfix on 0.2.2.14-alpha.
8034 - When autodetecting the number of CPUs, use the number of available
8035 CPUs in preference to the number of configured CPUs. Inform the
8036 user if this reduces the number of available CPUs. Fixes bug 8002;
8037 bugfix on 0.2.3.1-alpha.
8038 - Make it an error when you set EntryNodes but disable UseGuardNodes,
8039 since it will (surprisingly to some users) ignore EntryNodes. Fixes
8040 bug 8180; bugfix on 0.2.3.11-alpha.
8041 - Allow TestingTorNetworks to override the 4096-byte minimum for
8042 the Fast threshold. Otherwise they can't bootstrap until they've
8043 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
8044 - Fix some logic errors when the user manually overrides the
8045 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
8048 o Minor bugfixes (log messages to help diagnose bugs):
8049 - If we fail to free a microdescriptor because of bug 7164, log
8050 the filename and line number from which we tried to free it.
8051 - Add another diagnostic to the heartbeat message: track and log
8052 overhead that TLS is adding to the data we write. If this is
8053 high, we are sending too little data to SSL_write at a time.
8054 Diagnostic for bug 7707.
8055 - Add more detail to a log message about relaxed timeouts, to help
8057 - Warn more aggressively when flushing microdescriptors to a
8058 microdescriptor cache fails, in an attempt to mitigate bug 8031,
8059 or at least make it more diagnosable.
8060 - Improve debugging output to help track down bug 8185 ("Bug:
8061 outgoing relay cell has n_chan==NULL. Dropping.")
8062 - Log the purpose of a path-bias testing circuit correctly.
8063 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
8065 o Minor bugfixes (0.2.4.x log messages that were too noisy):
8066 - Don't attempt to relax the timeout of already opened 1-hop circuits.
8067 They might never timeout. This should eliminate some/all cases of
8068 the relaxed timeout log message.
8069 - Use circuit creation time for network liveness evaluation. This
8070 should eliminate warning log messages about liveness caused
8071 by changes in timeout evaluation. Fixes bug 6572; bugfix on
8073 - Reduce a path bias length check from notice to info. The message
8074 is triggered when creating controller circuits. Fixes bug 8196;
8075 bugfix on 0.2.4.8-alpha.
8076 - Fix a path state issue that triggered a notice during relay startup.
8077 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
8078 - Reduce occurrences of warns about circuit purpose in
8079 connection_ap_expire_building(). Fixes bug 8477; bugfix on
8082 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
8083 - If we encounter a write failure on a SOCKS connection before we
8084 finish our SOCKS handshake, don't warn that we closed the
8085 connection before we could send a SOCKS reply. Fixes bug 8427;
8086 bugfix on 0.1.0.1-rc.
8087 - Correctly recognize that [::1] is a loopback address. Fixes
8088 bug 8377; bugfix on 0.2.1.3-alpha.
8089 - Fix a directory authority warn caused when we have a large amount
8090 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
8091 - Don't log inappropriate heartbeat messages when hibernating: a
8092 hibernating node is _expected_ to drop out of the consensus,
8093 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
8094 bugfix on 0.2.3.1-alpha.
8095 - Don't complain about bootstrapping problems while hibernating.
8096 These complaints reflect a general code problem, but not one
8097 with any problematic effects (no connections are actually
8098 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
8100 o Documentation fixes:
8101 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
8102 names match. Fixes bug 7768.
8103 - Make the torify manpage no longer refer to tsocks; torify hasn't
8104 supported tsocks since 0.2.3.14-alpha.
8105 - Make the tor manpage no longer reference tsocks.
8106 - Fix the GeoIPExcludeUnknown documentation to refer to
8107 ExcludeExitNodes rather than the currently nonexistent
8108 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
8111 - The tor-tsocks.conf is no longer distributed or installed. We
8112 recommend that tsocks users use torsocks instead. Resolves
8116 Changes in version 0.2.4.11-alpha - 2013-03-11
8117 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
8118 more robust, makes hidden service authentication work again, and
8119 resolves a DPI fingerprint for Tor's SSL transport.
8121 o Major features (directory authorities):
8122 - Directory authorities now support a new consensus method (17)
8123 where they cap the published bandwidth of servers for which
8124 insufficient bandwidth measurements exist. Fixes part of bug 2286.
8125 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
8126 serve any v2 directory information. Now we can test disabling the
8127 old deprecated v2 directory format, and see whether doing so has
8128 any effect on network load. Begins to fix bug 6783.
8129 - Directory authorities now include inside each vote a statement of
8130 the performance thresholds they used when assigning flags.
8131 Implements ticket 8151.
8133 o Major bugfixes (directory authorities):
8134 - Stop marking every relay as having been down for one hour every
8135 time we restart a directory authority. These artificial downtimes
8136 were messing with our Stable and Guard flag calculations. Fixes
8137 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
8139 o Major bugfixes (hidden services):
8140 - Allow hidden service authentication to succeed again. When we
8141 refactored the hidden service introduction code back
8142 in 0.2.4.1-alpha, we didn't update the code that checks
8143 whether authentication information is present, causing all
8144 authentication checks to return "false". Fix for bug 8207; bugfix
8145 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
8147 o Minor features (relays, bridges):
8148 - Make bridge relays check once a minute for whether their IP
8149 address has changed, rather than only every 15 minutes. Resolves
8151 - Refactor resolve_my_address() so it returns the method by which we
8152 decided our public IP address (explicitly configured, resolved from
8153 explicit hostname, guessed from interfaces, learned by gethostname).
8154 Now we can provide more helpful log messages when a relay guesses
8155 its IP address incorrectly (e.g. due to unexpected lines in
8156 /etc/hosts). Resolves ticket 2267.
8157 - Teach bridge-using clients to avoid 0.2.2 bridges when making
8158 microdescriptor-related dir requests, and only fall back to normal
8159 descriptors if none of their bridges can handle microdescriptors
8160 (as opposed to the fix in ticket 4013, which caused them to fall
8161 back to normal descriptors if *any* of their bridges preferred
8162 them). Resolves ticket 4994.
8163 - Randomize the lifetime of our SSL link certificate, so censors can't
8164 use the static value for filtering Tor flows. Resolves ticket 8443;
8165 related to ticket 4014 which was included in 0.2.2.33.
8166 - Support a new version of the link protocol that allows 4-byte circuit
8167 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
8168 a possible resource exhaustion issue. Closes ticket 7351; implements
8171 o Minor features (portability):
8172 - Tweak the curve25519-donna*.c implementations to tolerate systems
8173 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
8174 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
8175 the signs of types during autoconf. This is better than our old
8176 approach, which didn't work when cross-compiling.
8177 - Detect the sign of enum values, rather than assuming that MSC is the
8178 only compiler where enum types are all signed. Fixes bug 7727;
8179 bugfix on 0.2.4.10-alpha.
8181 o Minor features (other):
8182 - Say "KBytes" rather than "KB" in the man page (for various values
8183 of K), to further reduce confusion about whether Tor counts in
8184 units of memory or fractions of units of memory. Resolves ticket 7054.
8185 - Clear the high bit on curve25519 public keys before passing them to
8186 our backend, in case we ever wind up using a backend that doesn't do
8187 so itself. If we used such a backend, and *didn't* clear the high bit,
8188 we could wind up in a situation where users with such backends would
8189 be distinguishable from users without. Fixes bug 8121; bugfix on
8191 - Update to the March 6 2013 Maxmind GeoLite Country database.
8193 o Minor bugfixes (clients):
8194 - When we receive a RELAY_END cell with the reason DONE, or with no
8195 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
8196 status as "connection refused". Previously we reported these cases
8197 as success but then immediately closed the connection. Fixes bug
8198 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
8199 - Downgrade an assertion in connection_ap_expire_beginning to an
8200 LD_BUG message. The fix for bug 8024 should prevent this message
8201 from displaying, but just in case, a warn that we can diagnose
8202 is better than more assert crashes. Fixes bug 8065; bugfix on
8204 - Lower path use bias thresholds to .80 for notice and .60 for warn.
8205 Also make the rate limiting flags for the path use bias log messages
8206 independent from the original path bias flags. Fixes bug 8161;
8207 bugfix on 0.2.4.10-alpha.
8209 o Minor bugfixes (relays):
8210 - Stop trying to resolve our hostname so often (e.g. every time we
8211 think about doing a directory fetch). Now we reuse the cached
8212 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
8213 and 2410 (bugfix on 0.1.2.2-alpha).
8214 - Stop sending a stray "(null)" in some cases for the server status
8215 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
8217 - When choosing which stream on a formerly stalled circuit to wake
8218 first, make better use of the platform's weak RNG. Previously,
8219 we had been using the % ("modulo") operator to try to generate a
8220 1/N chance of picking each stream, but this behaves badly with
8221 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
8223 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
8224 Irix's random() only return 15 bits; Solaris's random() returns more
8225 bits but its RAND_MAX says it only returns 15, and so on. Motivated
8226 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
8228 o Minor bugfixes (directory authorities):
8229 - Directory authorities now use less space when formatting identical
8230 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
8233 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
8234 - Avoid leaking memory if we fail to compute a consensus signature
8235 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
8236 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
8238 - Fix a memory leak during safe-cookie controller authentication.
8239 Bugfix on 0.2.3.13-alpha.
8240 - Avoid memory leak of IPv6 policy content if we fail to format it into
8241 a router descriptor. Bugfix on 0.2.4.7-alpha.
8243 o Minor bugfixes (other code correctness issues):
8244 - Avoid a crash if we fail to generate an extrainfo descriptor.
8245 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
8247 - When detecting the largest possible file descriptor (in order to
8248 close all file descriptors when launching a new program), actually
8249 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
8250 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
8252 - Fix a copy-and-paste error when adding a missing A1 to a routerset
8253 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
8254 Bugfix on 0.2.4.10-alpha.
8255 - Fix an impossible-to-trigger integer overflow when estimating how
8256 long our onionskin queue would take. (This overflow would require us
8257 to accept 4 million onionskins before processing 100 of them.) Fixes
8258 bug 8210; bugfix on 0.2.4.10-alpha.
8260 o Code simplification and refactoring:
8261 - Add a wrapper function for the common "log a message with a
8265 Changes in version 0.2.4.10-alpha - 2013-02-04
8266 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
8267 certain attacks that flood the network with relays; changes the queue
8268 for circuit create requests from a sized-based limit to a time-based
8269 limit; resumes building with MSVC on Windows; and fixes a wide variety
8272 o Major bugfixes (directory authority):
8273 - When computing directory thresholds, ignore any rejected-as-sybil
8274 nodes during the computation so that they can't influence Fast,
8275 Guard, etc. (We should have done this for proposal 109.) Fixes
8277 - When marking a node as a likely sybil, reset its uptime metrics
8278 to zero, so that it cannot time towards getting marked as Guard,
8279 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
8283 - When a TLS write is partially successful but incomplete, remember
8284 that the flushed part has been flushed, and notice that bytes were
8285 actually written. Reported and fixed pseudonymously. Fixes bug
8286 7708; bugfix on Tor 0.1.0.5-rc.
8287 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
8288 ID: these could be used to create unexpected streams and circuits
8289 which would count as "present" to some parts of Tor but "absent"
8290 to others, leading to zombie circuits and streams or to a bandwidth
8291 denial-of-service. Fixes bug 7889; bugfix on every released version
8292 of Tor. Reported by "oftc_must_be_destroyed".
8293 - Rename all macros in our local copy of queue.h to begin with "TOR_".
8294 This change seems the only good way to permanently prevent conflicts
8295 with queue.h on various operating systems. Fixes bug 8107; bugfix
8298 o Major features (relay):
8299 - Instead of limiting the number of queued onionskins (aka circuit
8300 create requests) to a fixed, hard-to-configure number, we limit
8301 the size of the queue based on how many we expect to be able to
8302 process in a given amount of time. We estimate the time it will
8303 take to process an onionskin based on average processing time
8304 of previous onionskins. Closes ticket 7291. You'll never have to
8305 configure MaxOnionsPending again.
8307 o Major features (portability):
8308 - Resume building correctly with MSVC and Makefile.nmake. This patch
8309 resolves numerous bugs and fixes reported by ultramage, including
8310 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
8311 - Make the ntor and curve25519 code build correctly with MSVC.
8312 Fix on 0.2.4.8-alpha.
8315 - When directory authorities are computing thresholds for flags,
8316 never let the threshold for the Fast flag fall below 4096
8317 bytes. Also, do not consider nodes with extremely low bandwidths
8318 when deciding thresholds for various directory flags. This change
8319 should raise our threshold for Fast relays, possibly in turn
8320 improving overall network performance; see ticket 1854. Resolves
8322 - The Tor client now ignores sub-domain components of a .onion
8323 address. This change makes HTTP "virtual" hosting
8324 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
8325 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
8326 hosted on the same hidden service. Implements proposal 204.
8327 - We compute the overhead from passing onionskins back and forth to
8328 cpuworkers, and report it when dumping statistics in response to
8329 SIGUSR1. Supports ticket 7291.
8331 o Minor features (path selection):
8332 - When deciding whether we have enough descriptors to build circuits,
8333 instead of looking at raw relay counts, look at which fraction
8334 of (bandwidth-weighted) paths we're able to build. This approach
8335 keeps clients from building circuits if their paths are likely to
8336 stand out statistically. The default fraction of paths needed is
8337 taken from the consensus directory; you can override it with the
8338 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
8339 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
8340 and we have GeoIP information, also exclude all nodes with unknown
8341 countries "??" and "A1". This behavior is controlled by the
8342 new GeoIPExcludeUnknown option: you can make such nodes always
8343 excluded with "GeoIPExcludeUnknown 1", and disable the feature
8344 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
8345 gets you the default behavior. Implements feature 7706.
8346 - Path Use Bias: Perform separate accounting for successful circuit
8347 use. Keep separate statistics on stream attempt rates versus stream
8348 success rates for each guard. Provide configurable thresholds to
8349 determine when to emit log messages or disable use of guards that
8350 fail too many stream attempts. Resolves ticket 7802.
8352 o Minor features (log messages):
8353 - When learning a fingerprint for a bridge, log its corresponding
8354 transport type. Implements ticket 7896.
8355 - Improve the log message when "Bug/attack: unexpected sendme cell
8356 from client" occurs, to help us track bug 8093.
8359 - Remove a couple of extraneous semicolons that were upsetting the
8360 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
8361 bugfix on 0.2.2.1-alpha.
8362 - Remove a source of rounding error during path bias count scaling;
8363 don't count cannibalized circuits as used for path bias until we
8364 actually try to use them; and fix a circuit_package_relay_cell()
8365 warning message about n_chan==NULL. Fixes bug 7802.
8366 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
8367 actually link against nacl when we're configured to use it. Fixes
8368 bug 7972; bugfix on 0.2.4.8-alpha.
8369 - Compile correctly with the --disable-curve25519 option. Fixes
8370 bug 8153; bugfix on 0.2.4.8-alpha.
8372 o Build improvements:
8373 - Do not report status verbosely from autogen.sh unless the -v flag
8374 is specified. Fixes issue 4664. Patch from Onizuka.
8375 - Replace all calls to snprintf() outside of src/ext with
8376 tor_snprintf(). Also remove the #define to replace snprintf with
8377 _snprintf on Windows; they have different semantics, and all of
8378 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
8379 - Try to detect if we are ever building on a platform where
8380 memset(...,0,...) does not set the value of a double to 0.0. Such
8381 platforms are permitted by the C standard, though in practice
8382 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
8383 currently support them, but it's better to detect them and fail
8384 than to perform erroneously.
8387 - Stop exporting estimates of v2 and v3 directory traffic shares
8388 in extrainfo documents. They were unneeded and sometimes inaccurate.
8389 Also stop exporting any v2 directory request statistics. Resolves
8391 - Drop support for detecting and warning about versions of Libevent
8392 before 1.3e. Nothing reasonable ships with them any longer;
8393 warning the user about them shouldn't be needed. Resolves ticket
8396 o Code simplifications and refactoring:
8397 - Rename "isin" functions to "contains", for grammar. Resolves
8399 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
8400 with the natural logarithm function from the system libm. Resolves
8404 Changes in version 0.2.4.9-alpha - 2013-01-15
8405 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
8409 - Fix backward compatibility logic when receiving an embedded ntor
8410 handshake tunneled in a CREATE cell. This clears up the "Bug:
8411 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
8415 Changes in version 0.2.4.8-alpha - 2013-01-14
8416 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
8417 risks, adds a new stronger and faster circuit handshake, and offers
8418 stronger and faster link encryption when both sides support it.
8421 - Preliminary support for directory guards (proposal 207): when
8422 possible, clients now use their entry guards for non-anonymous
8423 directory requests. This can help prevent client enumeration. Note
8424 that this behavior only works when we have a usable consensus
8425 directory, and when options about what to download are more or less
8426 standard. In the future we should re-bootstrap from our guards,
8427 rather than re-bootstrapping from the preconfigured list of
8428 directory sources that ships with Tor. Resolves ticket 6526.
8429 - Tor relays and clients now support a better CREATE/EXTEND cell
8430 format, allowing the sender to specify multiple address, identity,
8431 and handshake types. Implements Robert Ransom's proposal 200;
8434 o Major features (new circuit handshake):
8435 - Tor now supports a new circuit extension handshake designed by Ian
8436 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
8437 circuit extension handshake, later called "TAP", was a bit slow
8438 (especially on the relay side), had a fragile security proof, and
8439 used weaker keys than we'd now prefer. The new circuit handshake
8440 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
8441 function, making it significantly more secure than the older
8442 handshake, and significantly faster. Tor can use one of two built-in
8443 pure-C curve25519-donna implementations by Adam Langley, or it
8444 can link against the "nacl" library for a tuned version if present.
8446 The built-in version is very fast for 64-bit systems when building
8447 with GCC. The built-in 32-bit version is still faster than the
8448 old TAP protocol, but using libnacl is better on most such hosts.
8450 Clients don't currently use this protocol by default, since
8451 comparatively few clients support it so far. To try it, set
8452 UseNTorHandshake to 1.
8454 Implements proposal 216; closes ticket 7202.
8456 o Major features (better link encryption):
8457 - Relays can now enable the ECDHE TLS ciphersuites when available
8458 and appropriate. These ciphersuites let us negotiate forward-secure
8459 TLS secret keys more safely and more efficiently than with our
8460 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
8461 public relays prefer the (faster) P224 group, and bridges prefer
8462 the (more common) P256 group; you can override this with the
8465 Enabling these ciphers was a little tricky, since for a long time,
8466 clients had been claiming to support them without actually doing
8467 so, in order to foil fingerprinting. But with the client-side
8468 implementation of proposal 198 in 0.2.3.17-beta, clients can now
8469 match the ciphers from recent Firefox versions *and* list the
8470 ciphers they actually mean, so relays can believe such clients
8471 when they advertise ECDHE support in their TLS ClientHello messages.
8473 This feature requires clients running 0.2.3.17-beta or later,
8474 and requires both sides to be running OpenSSL 1.0.0 or later
8475 with ECC support. OpenSSL 1.0.1, with the compile-time option
8476 "enable-ec_nistp_64_gcc_128", is highly recommended.
8478 Implements the relay side of proposal 198; closes ticket 7200.
8481 - Avoid crashing when, as a relay without IPv6-exit support, a
8482 client insists on getting an IPv6 address or nothing. Fixes bug
8483 7814; bugfix on 0.2.4.7-alpha.
8486 - Improve circuit build timeout handling for hidden services.
8487 In particular: adjust build timeouts more accurately depending
8488 upon the number of hop-RTTs that a particular circuit type
8489 undergoes. Additionally, launch intro circuits in parallel
8490 if they timeout, and take the first one to reply as valid.
8491 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
8492 separate error codes; or at least, don't break for that reason.
8493 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
8494 - Update to the January 2 2013 Maxmind GeoLite Country database.
8496 o Minor features (testing):
8497 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
8498 (P-256) Diffie-Hellman handshakes to src/or/bench.
8499 - Add benchmark functions to test onion handshake performance.
8501 o Minor features (path bias detection):
8502 - Alter the Path Bias log messages to be more descriptive in terms
8503 of reporting timeouts and other statistics.
8504 - Create three levels of Path Bias log messages, as opposed to just
8505 two. These are configurable via consensus as well as via the torrc
8506 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
8507 The default values are 0.70, 0.50, and 0.30 respectively.
8508 - Separate the log message levels from the decision to drop guards,
8509 which also is available via torrc option PathBiasDropGuards.
8510 PathBiasDropGuards still defaults to 0 (off).
8511 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
8512 in combination with PathBiasExtremeRate.
8513 - Increase the default values for PathBiasScaleThreshold and
8514 PathBiasCircThreshold from (200, 20) to (300, 150).
8515 - Add in circuit usage accounting to path bias. If we try to use a
8516 built circuit but fail for any reason, it counts as path bias.
8517 Certain classes of circuits where the adversary gets to pick your
8518 destination node are exempt from this accounting. Usage accounting
8519 can be specifically disabled via consensus parameter or torrc.
8520 - Convert all internal path bias state to double-precision floating
8521 point, to avoid roundoff error and other issues.
8522 - Only record path bias information for circuits that have completed
8523 *two* hops. Assuming end-to-end tagging is the attack vector, this
8524 makes us more resilient to ambient circuit failure without any
8525 detection capability loss.
8527 o Minor bugfixes (log messages):
8528 - Rate-limit the "No circuits are opened. Relaxed timeout for a
8529 circuit with channel state open..." message to once per hour to
8530 keep it from filling the notice logs. Mitigates bug 7799 but does
8531 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
8532 - Avoid spurious warnings when configuring multiple client ports of
8533 which only some are nonlocal. Previously, we had claimed that some
8534 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
8537 o Code simplifications and refactoring:
8538 - Get rid of a couple of harmless clang warnings, where we compared
8539 enums to ints. These warnings are newly introduced in clang 3.2.
8540 - Split the onion.c file into separate modules for the onion queue
8541 and the different handshakes it supports.
8542 - Remove the marshalling/unmarshalling code for sending requests to
8543 cpuworkers over a socket, and instead just send structs. The
8544 recipient will always be the same Tor binary as the sender, so
8545 any encoding is overkill.
8548 Changes in version 0.2.4.7-alpha - 2012-12-24
8549 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
8550 directory mirrors for more robust bootstrapping; fixes more issues where
8551 clients with changing network conditions refuse to make any circuits;
8552 adds initial support for exiting to IPv6 addresses; resumes being able
8553 to update our GeoIP database, and includes the geoip6 file this time;
8554 turns off the client-side DNS cache by default due to privacy risks;
8555 and fixes a variety of other issues.
8557 o Major features (client resilience):
8558 - Add a new "FallbackDir" torrc option to use when we can't use
8559 a directory mirror from the consensus (either because we lack a
8560 consensus, or because they're all down). Currently, all authorities
8561 are fallbacks by default, and there are no other default fallbacks,
8562 but that will change. This option will allow us to give clients a
8563 longer list of servers to try to get a consensus from when first
8564 connecting to the Tor network, and thereby reduce load on the
8565 directory authorities. Implements proposal 206, "Preconfigured
8566 directory sources for bootstrapping". We also removed the old
8567 "FallbackNetworkstatus" option, since we never got it working well
8568 enough to use it. Closes bug 572.
8569 - If we have no circuits open, use a relaxed timeout (the
8570 95-percentile cutoff) until a circuit succeeds. This heuristic
8571 should allow Tor to succeed at building circuits even when the
8572 network connection drastically changes. Should help with bug 3443.
8574 o Major features (IPv6):
8575 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
8576 connectivity, then set the IPv6Exit flag to 1. Also make sure your
8577 exit policy reads as you would like: the address * applies to all
8578 address families, whereas *4 is IPv4 address only, and *6 is IPv6
8579 addresses only. On the client side, you'll need to wait until the
8580 authorities have upgraded, wait for enough exits to support IPv6,
8581 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
8582 ticket 5547, implements proposal 117 as revised in proposal 208.
8584 We DO NOT recommend that clients with actual anonymity needs start
8585 using IPv6 over Tor yet, since not enough exits support it yet.
8587 o Major features (geoip database):
8588 - Maxmind began labelling Tor relays as being in country "A1",
8589 which breaks by-country node selection inside Tor. Now we use a
8590 script to replace "A1" ("Anonymous Proxy") entries in our geoip
8591 file with real country codes. This script fixes about 90% of "A1"
8592 entries automatically and uses manual country code assignments to
8593 fix the remaining 10%. See src/config/README.geoip for details.
8594 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
8595 Country database, as modified above.
8597 o Major bugfixes (client-side DNS):
8598 - Turn off the client-side DNS cache by default. Updating and using
8599 the DNS cache is now configurable on a per-client-port
8600 level. SOCKSPort, DNSPort, etc lines may now contain
8601 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
8602 cache these types of DNS answers when we receive them from an
8603 exit node in response to an application request on this port, and
8604 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
8605 cached DNS answers of these types, we shouldn't use them. It's
8606 potentially risky to use cached DNS answers at the client, since
8607 doing so can indicate to one exit what answers we've gotten
8608 for DNS lookups in the past. With IPv6, this becomes especially
8609 problematic. Using cached DNS answers for requests on the same
8610 circuit would present less linkability risk, since all traffic
8611 on a circuit is already linkable, but it would also provide
8612 little performance benefit: the exit node caches DNS replies
8613 too. Implements a simplified version of Proposal 205. Implements
8616 o Major bugfixes (other):
8617 - Alter circuit build timeout measurement to start at the point
8618 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
8619 initialization). This should make our timeout measurements more
8620 uniform. Previously, we were sometimes including ORconn setup time
8621 in our circuit build time measurements. Should resolve bug 3443.
8622 - Fix an assertion that could trigger in hibernate_go_dormant() when
8623 closing an or_connection_t: call channel_mark_for_close() rather
8624 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
8626 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
8627 7655; bugfix on 0.2.4.6-alpha.
8630 - Add a new torrc option "ServerTransportListenAddr" to let bridge
8631 operators select the address where their pluggable transports will
8632 listen for connections. Resolves ticket 7013.
8633 - Allow an optional $ before the node identity digest in the
8634 controller command GETINFO ns/id/<identity>, for consistency with
8635 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
8636 - Log packaged cell fullness as part of the heartbeat message.
8637 Diagnosis to try to determine the extent of bug 7743.
8639 o Minor features (IPv6):
8640 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
8641 prefer to hand out virtual IPv6 addresses, since there are more of
8642 them and we can't run out. To override this behavior and make IPv4
8643 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
8644 or DNSPort you're using for resolving. Implements ticket 7571.
8645 - AutomapHostsOnResolve responses are now randomized, to avoid
8646 annoying situations where Tor is restarted and applications
8647 connect to the wrong addresses.
8648 - Never try more than 1000 times to pick a new virtual address when
8649 AutomapHostsOnResolve is set. That's good enough so long as we
8650 aren't close to handing out our entire virtual address space;
8651 if you're getting there, it's best to switch to IPv6 virtual
8655 - The ADDRMAP command can no longer generate an ill-formed error
8656 code on a failed MAPADDRESS. It now says "internal" rather than
8657 an English sentence fragment with spaces in the middle. Bugfix on
8659 - Fix log messages and comments to avoid saying "GMT" when we mean
8660 "UTC". Fixes bug 6113.
8661 - Compile on win64 using mingw64. Fixes bug 7260; patches from
8663 - Fix a crash when debugging unit tests on Windows: deallocate a
8664 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
8665 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
8668 - The DirServer option is now DirAuthority, for consistency with
8669 current naming patterns. You can still use the old DirServer form.
8671 o Code simplification and refactoring:
8672 - Move the client-side address-map/virtual-address/DNS-cache code
8673 out of connection_edge.c into a new addressmap.c module.
8674 - Remove unused code for parsing v1 directories and "running routers"
8675 documents. Fixes bug 6887.
8678 Changes in version 0.2.3.25 - 2012-11-19
8679 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
8680 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
8681 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
8682 programmer, and friend. Unstinting in his dedication to the cause of
8683 freedom, he inspired and helped many of us as we began our work on
8684 anonymity, and inspires us still. Please honor his memory by writing
8685 software to protect people's freedoms, and by helping others to do so.
8687 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
8688 significantly reduced directory overhead (via microdescriptors),
8689 enormous crypto performance improvements for fast relays on new
8690 enough hardware, a new v3 TLS handshake protocol that can better
8691 resist fingerprinting, support for protocol obfuscation plugins (aka
8692 pluggable transports), better scalability for hidden services, IPv6
8693 support for bridges, performance improvements like allowing clients
8694 to skip the first round-trip on the circuit ("optimistic data") and
8695 refilling token buckets more often, a new "stream isolation" design
8696 to isolate different applications on different circuits, and many
8697 stability, security, and privacy fixes.
8700 - Tor tries to wipe potentially sensitive data after using it, so
8701 that if some subsequent security failure exposes Tor's memory,
8702 the damage will be limited. But we had a bug where the compiler
8703 was eliminating these wipe operations when it decided that the
8704 memory was no longer visible to a (correctly running) program,
8705 hence defeating our attempt at defense in depth. We fix that
8706 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
8707 is unlikely to optimize away. Future versions of Tor may use
8708 a less ridiculously heavy approach for this. Fixes bug 7352.
8709 Reported in an article by Andrey Karpov.
8712 - Fix a harmless bug when opting against publishing a relay descriptor
8713 because DisableNetwork is set. Fixes bug 7464; bugfix on
8717 Changes in version 0.2.4.6-alpha - 2012-11-13
8718 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
8719 makes our defense-in-depth memory wiping more reliable, and begins to
8720 count IPv6 addresses in bridge statistics,
8723 - Fix an assertion failure that could occur when closing a connection
8724 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
8726 - Tor tries to wipe potentially sensitive data after using it, so
8727 that if some subsequent security failure exposes Tor's memory,
8728 the damage will be limited. But we had a bug where the compiler
8729 was eliminating these wipe operations when it decided that the
8730 memory was no longer visible to a (correctly running) program,
8731 hence defeating our attempt at defense in depth. We fix that
8732 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
8733 is unlikely to optimize away. Future versions of Tor may use
8734 a less ridiculously heavy approach for this. Fixes bug 7352.
8735 Reported in an article by Andrey Karpov.
8738 - Add GeoIP database for IPv6 addresses. The new config option
8740 - Bridge statistics now count bridge clients connecting over IPv6:
8741 bridge statistics files now list "bridge-ip-versions" and
8742 extra-info documents list "geoip6-db-digest". The control protocol
8743 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
8744 implementation by "shkoo", addressing ticket 5055.
8747 - Warn when we are binding low ports when hibernation is enabled;
8748 previously we had warned when we were _advertising_ low ports with
8749 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
8750 - Fix a harmless bug when opting against publishing a relay descriptor
8751 because DisableNetwork is set. Fixes bug 7464; bugfix on
8753 - Add warning message when a managed proxy dies during configuration.
8754 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
8755 - Fix a linking error when building tor-fw-helper without miniupnp.
8756 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
8757 - Check for closing an or_connection_t without going through correct
8758 channel functions; emit a warning and then call
8759 connection_or_close_for_error() so we don't assert as in bugs 7212
8761 - Compile correctly on compilers without C99 designated initializer
8762 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
8763 - Avoid a possible assert that can occur when channel_send_destroy() is
8764 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
8765 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
8766 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
8767 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
8768 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
8770 o Code simplification and refactoring:
8771 - Start using OpenBSD's implementation of queue.h, so that we don't
8772 need to hand-roll our own pointer and list structures whenever we
8773 need them. (We can't rely on a sys/queue.h, since some operating
8774 systems don't have them, and the ones that do have them don't all
8775 present the same extensions.)
8778 Changes in version 0.2.4.5-alpha - 2012-10-25
8779 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
8780 two important security vulnerabilities that could lead to remotely
8781 triggerable relay crashes, fix a major bug that was preventing clients
8782 from choosing suitable exit nodes, and refactor some of our code.
8784 o Major bugfixes (security, also in 0.2.3.24-rc):
8785 - Fix a group of remotely triggerable assertion failures related to
8786 incorrect link protocol negotiation. Found, diagnosed, and fixed
8787 by "some guy from France". Fix for CVE-2012-2250; bugfix on
8789 - Fix a denial of service attack by which any directory authority
8790 could crash all the others, or by which a single v2 directory
8791 authority could crash everybody downloading v2 directory
8792 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
8794 o Major bugfixes (also in 0.2.3.24-rc):
8795 - When parsing exit policy summaries from microdescriptors, we had
8796 previously been ignoring the last character in each one, so that
8797 "accept 80,443,8080" would be treated by clients as indicating
8798 a node that allows access to ports 80, 443, and 808. That would
8799 lead to clients attempting connections that could never work,
8800 and ignoring exit nodes that would support their connections. Now
8801 clients parse these exit policy summaries correctly. Fixes bug 7192;
8802 bugfix on 0.2.3.1-alpha.
8804 o Minor bugfixes (also in 0.2.3.24-rc):
8805 - Clients now consider the ClientRejectInternalAddresses config option
8806 when using a microdescriptor consensus stanza to decide whether
8807 an exit relay would allow exiting to an internal address. Fixes
8808 bug 7190; bugfix on 0.2.3.1-alpha.
8811 - Only disable TLS session ticket support when running as a TLS
8812 server. Now clients will blend better with regular Firefox
8813 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
8815 o Code simplification and refactoring:
8816 - Start using OpenBSD's implementation of queue.h (originally by
8818 - Move the entry node code from circuitbuild.c to its own file.
8819 - Move the circuit build timeout tracking code from circuitbuild.c
8823 Changes in version 0.2.3.24-rc - 2012-10-25
8824 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
8825 could lead to remotely triggerable relay crashes, and fixes
8826 a major bug that was preventing clients from choosing suitable exit
8829 o Major bugfixes (security):
8830 - Fix a group of remotely triggerable assertion failures related to
8831 incorrect link protocol negotiation. Found, diagnosed, and fixed
8832 by "some guy from France". Fix for CVE-2012-2250; bugfix on
8834 - Fix a denial of service attack by which any directory authority
8835 could crash all the others, or by which a single v2 directory
8836 authority could crash everybody downloading v2 directory
8837 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
8840 - When parsing exit policy summaries from microdescriptors, we had
8841 previously been ignoring the last character in each one, so that
8842 "accept 80,443,8080" would be treated by clients as indicating
8843 a node that allows access to ports 80, 443, and 808. That would
8844 lead to clients attempting connections that could never work,
8845 and ignoring exit nodes that would support their connections. Now
8846 clients parse these exit policy summaries correctly. Fixes bug 7192;
8847 bugfix on 0.2.3.1-alpha.
8850 - Clients now consider the ClientRejectInternalAddresses config option
8851 when using a microdescriptor consensus stanza to decide whether
8852 an exit relay would allow exiting to an internal address. Fixes
8853 bug 7190; bugfix on 0.2.3.1-alpha.
8856 Changes in version 0.2.4.4-alpha - 2012-10-20
8857 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
8858 vulnerability introduced by a change in OpenSSL, fixes a remotely
8859 triggerable assert, and adds new channel_t and circuitmux_t abstractions
8860 that will make it easier to test new connection transport and cell
8861 scheduling algorithms.
8863 o New directory authorities (also in 0.2.3.23-rc):
8864 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
8865 authority. Closes ticket 5749.
8867 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
8868 - Disable TLS session tickets. OpenSSL's implementation was giving
8869 our TLS session keys the lifetime of our TLS context objects, when
8870 perfect forward secrecy would want us to discard anything that
8871 could decrypt a link connection as soon as the link connection
8872 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
8873 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
8874 - Discard extraneous renegotiation attempts once the V3 link
8875 protocol has been initiated. Failure to do so left us open to
8876 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
8877 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
8879 o Internal abstraction features:
8880 - Introduce new channel_t abstraction between circuits and
8881 or_connection_t to allow for implementing alternate OR-to-OR
8882 transports. A channel_t is an abstract object which can either be a
8883 cell-bearing channel, which is responsible for authenticating and
8884 handshaking with the remote OR and transmitting cells to and from
8885 it, or a listening channel, which spawns new cell-bearing channels
8886 at the request of remote ORs. Implements part of ticket 6465.
8887 - Also new is the channel_tls_t subclass of channel_t, adapting it
8888 to the existing or_connection_t code. The V2/V3 protocol handshaking
8889 code which formerly resided in command.c has been moved below the
8890 channel_t abstraction layer and may be found in channeltls.c now.
8891 Implements the rest of ticket 6465.
8892 - Introduce new circuitmux_t storing the queue of circuits for
8893 a channel; this encapsulates and abstracts the queue logic and
8894 circuit selection policy, and allows the latter to be overridden
8895 easily by switching out a policy object. The existing EWMA behavior
8896 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
8898 o Required libraries:
8899 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
8900 strongly recommended.
8903 - Warn users who run hidden services on a Tor client with
8904 UseEntryGuards disabled that their hidden services will be
8905 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
8906 attack which motivated Tor to support entry guards in the first
8907 place). Resolves ticket 6889.
8908 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
8909 dhill. Resolves ticket 6982.
8910 - Option OutboundBindAddress can be specified multiple times and
8911 accepts IPv6 addresses. Resolves ticket 6876.
8913 o Minor bugfixes (also in 0.2.3.23-rc):
8914 - Don't serve or accept v2 hidden service descriptors over a
8915 relay's DirPort. It's never correct to do so, and disabling it
8916 might make it more annoying to exploit any bugs that turn up in the
8917 descriptor-parsing code. Fixes bug 7149.
8918 - Fix two cases in src/or/transports.c where we were calling
8919 fmt_addr() twice in a parameter list. Bug found by David
8920 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
8921 - Fix memory leaks whenever we logged any message about the "path
8922 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
8923 - When relays refuse a "create" cell because their queue of pending
8924 create cells is too big (typically because their cpu can't keep up
8925 with the arrival rate), send back reason "resource limit" rather
8926 than reason "internal", so network measurement scripts can get a
8927 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
8930 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
8931 - Free some more still-in-use memory at exit, to make hunting for
8932 memory leaks easier. Resolves bug 7029.
8933 - When a Tor client gets a "truncated" relay cell, the first byte of
8934 its payload specifies why the circuit was truncated. We were
8935 ignoring this 'reason' byte when tearing down the circuit, resulting
8936 in the controller not being told why the circuit closed. Now we
8937 pass the reason from the truncated cell to the controller. Bugfix
8938 on 0.1.2.3-alpha; fixes bug 7039.
8939 - Downgrade "Failed to hand off onionskin" messages to "debug"
8940 severity, since they're typically redundant with the "Your computer
8941 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
8942 - Make clients running with IPv6 bridges connect over IPv6 again,
8943 even without setting new config options ClientUseIPv6 and
8944 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
8945 - Use square brackets around IPv6 addresses in numerous places
8946 that needed them, including log messages, HTTPS CONNECT proxy
8947 requests, TransportProxy statefile entries, and pluggable transport
8948 extra-info lines. Fixes bug 7011; patch by David Fifield.
8950 o Code refactoring and cleanup:
8951 - Source files taken from other packages now reside in src/ext;
8952 previously they were scattered around the rest of Tor.
8953 - Avoid use of reserved identifiers in our C code. The C standard
8954 doesn't like us declaring anything that starts with an
8955 underscore, so let's knock it off before we get in trouble. Fix
8956 for bug 1031; bugfix on the first Tor commit.
8959 Changes in version 0.2.3.23-rc - 2012-10-20
8960 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
8961 vulnerability introduced by a change in OpenSSL, and fixes a variety
8962 of smaller bugs in preparation for the release.
8964 o New directory authorities:
8965 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
8966 authority. Closes ticket 5749.
8968 o Major bugfixes (security/privacy):
8969 - Disable TLS session tickets. OpenSSL's implementation was giving
8970 our TLS session keys the lifetime of our TLS context objects, when
8971 perfect forward secrecy would want us to discard anything that
8972 could decrypt a link connection as soon as the link connection
8973 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
8974 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
8975 - Discard extraneous renegotiation attempts once the V3 link
8976 protocol has been initiated. Failure to do so left us open to
8977 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
8978 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
8981 - Fix a possible crash bug when checking for deactivated circuits
8982 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
8983 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
8985 o Minor bugfixes (on 0.2.3.x):
8986 - Fix two cases in src/or/transports.c where we were calling
8987 fmt_addr() twice in a parameter list. Bug found by David
8988 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
8989 - Convert an assert in the pathbias code to a log message. The assert
8990 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
8991 bugfix on 0.2.3.17-beta.
8992 - Fix memory leaks whenever we logged any message about the "path
8993 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
8995 o Minor bugfixes (on 0.2.2.x and earlier):
8996 - Don't serve or accept v2 hidden service descriptors over a relay's
8997 DirPort. It's never correct to do so, and disabling it might
8998 make it more annoying to exploit any bugs that turn up in the
8999 descriptor-parsing code. Fixes bug 7149.
9000 - When relays refuse a "create" cell because their queue of pending
9001 create cells is too big (typically because their cpu can't keep up
9002 with the arrival rate), send back reason "resource limit" rather
9003 than reason "internal", so network measurement scripts can get a
9004 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
9005 - Correct file sizes when reading binary files on Cygwin, to avoid
9006 a bug where Tor would fail to read its state file. Fixes bug 6844;
9007 bugfix on 0.1.2.7-alpha.
9008 - Avoid undefined behavior when parsing the list of supported
9009 rendezvous/introduction protocols in a hidden service descriptor.
9010 Previously, Tor would have confused (as-yet-unused) protocol version
9011 numbers greater than 32 with lower ones on many platforms. Fixes
9012 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
9014 o Documentation fixes:
9015 - Clarify that hidden services are TCP only. Fixes bug 6024.
9018 Changes in version 0.2.4.3-alpha - 2012-09-22
9019 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
9020 assertion, resumes letting relays test reachability of their DirPort,
9021 and cleans up a bunch of smaller bugs.
9024 - Fix an assertion failure in tor_timegm() that could be triggered
9025 by a badly formatted directory object. Bug found by fuzzing with
9026 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
9029 - Fix a possible crash bug when checking for deactivated circuits
9030 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
9031 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
9032 - Allow routers to detect that their own DirPorts are running. When
9033 we removed support for versions_supports_begindir, we also
9034 accidentally removed the mechanism we used to self-test our
9035 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
9036 bugfix on 0.2.4.2-alpha.
9038 o Security features:
9039 - Switch to a completely time-invariant approach for picking nodes
9040 weighted by bandwidth. Our old approach would run through the
9041 part of the loop after it had made its choice slightly slower
9042 than it ran through the part of the loop before it had made its
9043 choice. Addresses ticket 6538.
9044 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
9045 by tor2web clients allows hidden services to identify tor2web
9046 clients through their repeated selection of the same rendezvous
9047 and introduction point circuit endpoints (their guards). Resolves
9051 - Enable Tor to read configuration, state, and key information from
9052 a FIFO. Previously Tor would only read from files with a positive
9053 stat.st_size. Code from meejah; fixes bug 6044.
9056 - Correct file sizes when reading binary files on Cygwin, to avoid
9057 a bug where Tor would fail to read its state file. Fixes bug 6844;
9058 bugfix on 0.1.2.7-alpha.
9059 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
9060 bugfix on 0.2.0.3-alpha.
9061 - When complaining about a client port on a public address, log
9062 which address we're complaining about. Fixes bug 4020; bugfix on
9063 0.2.3.3-alpha. Patch by Tom Fitzhenry.
9064 - Convert an assert in the pathbias code to a log message. The assert
9065 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
9066 bugfix on 0.2.3.17-beta.
9067 - Our new buildsystem was overzealous about rebuilding manpages: it
9068 would rebuild them all whenever any one of them changed. Now our
9069 dependency checking should be correct. Fixes bug 6843; bugfix on
9071 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
9072 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
9073 - Correct log printout about which address family is preferred
9074 when connecting to a bridge with both an IPv4 and IPv6 OR port.
9075 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
9077 o Minor bugfixes (code cleanliness):
9078 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
9079 with large values. This situation was untriggered, but nevertheless
9080 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
9081 - Reject consensus votes with more than 64 known-flags. We aren't even
9082 close to that limit yet, and our code doesn't handle it correctly.
9083 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
9084 - Avoid undefined behavior when parsing the list of supported
9085 rendezvous/introduction protocols in a hidden service descriptor.
9086 Previously, Tor would have confused (as-yet-unused) protocol version
9087 numbers greater than 32 with lower ones on many platforms. Fixes
9088 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
9089 - Fix handling of rendezvous client authorization types over 8.
9090 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
9091 - Fix building with older versions of GCC (2.95, for one) that don't
9092 like preprocessor directives inside macro arguments. Found by
9093 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
9094 - Switch weighted node selection rule from using a list of doubles
9095 to using a list of int64_t. This change should make the process
9096 slightly easier to debug and maintain. Needed to finish ticket 6538.
9098 o Code simplification and refactoring:
9099 - Move the generic "config" code into a new file, and have "config.c"
9100 hold only torrc- and state-related code. Resolves ticket 6823.
9101 - Move the core of our "choose a weighted element at random" logic
9102 into its own function, and give it unit tests. Now the logic is
9103 testable, and a little less fragile too.
9104 - Removed the testing_since field of node_t, which hasn't been used
9105 for anything since 0.2.0.9-alpha.
9107 o Documentation fixes:
9108 - Clarify that hidden services are TCP only. Fixes bug 6024.
9109 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
9113 Changes in version 0.2.3.22-rc - 2012-09-11
9114 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
9118 - Fix an assertion failure in tor_timegm() that could be triggered
9119 by a badly formatted directory object. Bug found by fuzzing with
9120 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
9123 - Avoid segfault when starting up having run with an extremely old
9124 version of Tor and parsing its state file. Fixes bug 6801; bugfix
9128 Changes in version 0.2.2.39 - 2012-09-11
9129 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
9133 - Fix an assertion failure in tor_timegm() that could be triggered
9134 by a badly formatted directory object. Bug found by fuzzing with
9135 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
9136 - Do not crash when comparing an address with port value 0 to an
9137 address policy. This bug could have been used to cause a remote
9138 assertion failure by or against directory authorities, or to
9139 allow some applications to crash clients. Fixes bug 6690; bugfix
9143 Changes in version 0.2.4.2-alpha - 2012-09-10
9144 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
9145 raises the default rate limiting even more, and makes the bootstrapping
9146 log messages less noisy.
9149 - Automatically forward the TCP ports of pluggable transport
9150 proxies using tor-fw-helper if PortForwarding is enabled. Implements
9154 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
9155 to 1GB/1GB. The previous defaults were intended to be "basically
9156 infinite", but it turns out they're now limiting our 100mbit+
9157 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
9158 last time we raised it).
9161 - Detect when we're running with a version of OpenSSL other than the
9162 one we compiled with. This has occasionally given people hard-to-
9164 - Log fewer lines at level "notice" about our OpenSSL and Libevent
9165 versions and capabilities when everything is going right. Resolves
9166 part of ticket 6736.
9167 - Directory authorities no long accept descriptors for any version of
9168 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
9169 These versions are insecure, unsupported, or both. Implements
9173 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
9174 to start with a triple-underscore so the controller won't touch it.
9175 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
9176 - Avoid segfault when starting up having run with an extremely old
9177 version of Tor and parsing its state file. Fixes bug 6801; bugfix
9179 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
9180 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
9181 - Don't follow the NULL pointer if microdescriptor generation fails.
9182 (This does not appear to be triggerable, but it's best to be safe.)
9183 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
9184 - Fix mis-declared dependencies on src/common/crypto.c and
9185 src/or/tor_main.c that could break out-of-tree builds under some
9186 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
9187 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
9188 6778; bugfix on 0.2.4.1-alpha.
9189 - Fix a harmless (in this case) build warning for implicitly
9190 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
9193 - Now that all versions before 0.2.2.x are disallowed, we no longer
9194 need to work around their missing features. Thus we can remove a
9195 bunch of compatibility code.
9198 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
9199 TCP ports to forward. In the past it only accepted two ports:
9200 the ORPort and the DirPort.
9203 Changes in version 0.2.4.1-alpha - 2012-09-05
9204 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
9205 bridgedb; lets relays use IPv6 addresses and directory authorities
9206 advertise them; and switches to a cleaner build interface.
9208 This is the first alpha release in a new series, so expect there to
9209 be bugs. Users who would rather test out a more stable branch should
9210 stay with 0.2.3.x for now.
9212 o Major features (bridges):
9213 - Bridges now report the pluggable transports they support to the
9214 bridge authority, so it can pass the supported transports on to
9215 bridgedb and/or eventually do reachability testing. Implements
9218 o Major features (IPv6):
9219 - Bridge authorities now accept IPv6 bridge addresses and include
9220 them in network status documents. Implements ticket 5534.
9221 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
9222 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
9223 to happen. Implements ticket 5535.
9224 - All kind of relays, not just bridges, can now advertise an IPv6
9225 OR port. Implements ticket 6362.
9226 - Directory authorities vote on IPv6 OR ports using the new consensus
9227 method 14. Implements ticket 6363.
9229 o Major features (build):
9230 - Switch to a nonrecursive Makefile structure. Now instead of each
9231 Makefile.am invoking other Makefile.am's, there is a master
9232 Makefile.am that includes the others. This change makes our build
9233 process slightly more maintainable, and improves parallelism for
9234 building with make -j. Original patch by Stewart Smith; various
9235 fixes by Jim Meyering.
9236 - Where available, we now use automake's "silent" make rules by
9237 default, so that warnings are easier to spot. You can get the old
9238 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
9240 o Minor features (code security and spec conformance):
9241 - Clear keys and key-derived material left on the stack in
9242 rendservice.c and rendclient.c. Check return value of
9243 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
9244 These fixes should make us more forward-secure against cold-boot
9245 attacks and the like. Fixes bug 2385.
9246 - Reject EXTEND cells sent to nonexistent streams. According to the
9247 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
9248 we were only checking for stream IDs that were currently in use.
9249 Found while hunting for more instances of bug 6271. Bugfix on
9250 0.0.2pre8, which introduced incremental circuit construction.
9252 o Minor features (streamlining);
9253 - No longer include the "opt" prefix when generating routerinfos
9254 or v2 directories: it has been needless since Tor 0.1.2. Closes
9256 - Remove some now-needless code that tried to aggressively flush
9257 OR connections as data was added to them. Since 0.2.0.1-alpha, our
9258 cell queue logic has saved us from the failure mode that this code
9259 was supposed to prevent. Removing this code will limit the number
9260 of baroque control flow paths through Tor's network logic. Reported
9261 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
9263 o Minor features (controller):
9264 - Add a "GETINFO signal/names" control port command. Implements
9266 - Provide default values for all options via "GETINFO config/defaults".
9267 Implements ticket 4971.
9269 o Minor features (IPv6):
9270 - New config option "AuthDirHasIPv6Connectivity 1" that directory
9271 authorities should set if they have IPv6 connectivity and want to
9272 do reachability tests for IPv6 relays. Implements feature 5974.
9273 - A relay with an IPv6 OR port now sends that address in NETINFO
9274 cells (in addition to its other address). Implements ticket 6364.
9276 o Minor features (log messages):
9277 - Omit the first heartbeat log message, because it never has anything
9278 useful to say, and it clutters up the bootstrapping messages.
9279 Resolves ticket 6758.
9280 - Don't log about reloading the microdescriptor cache at startup. Our
9281 bootstrap warnings are supposed to tell the user when there's a
9282 problem, and our bootstrap notices say when there isn't. Resolves
9283 ticket 6759; bugfix on 0.2.2.6-alpha.
9284 - Don't log "I learned some more directory information" when we're
9285 reading cached directory information. Reserve it for when new
9286 directory information arrives in response to a fetch. Resolves
9288 - Prevent rounding error in path bias counts when scaling
9289 them down, and use the correct scale factor default. Also demote
9290 some path bias related log messages down a level and make others
9291 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
9292 - We no longer warn so much when generating manpages from their
9295 o Code simplifications and refactoring:
9296 - Enhance our internal sscanf replacement so that we can eliminate
9297 the last remaining uses of the system sscanf. (Though those uses
9298 of sscanf were safe, sscanf itself is generally error prone, so
9299 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
9301 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
9302 - Move last_reachable and testing_since from routerinfo_t to node_t.
9303 Implements ticket 5529.
9304 - Add replaycache_t structure, functions and unit tests, then refactor
9305 rend_service_introduce() to be more clear to read, improve, debug,
9306 and test. Resolves bug 6177.
9307 - Finally remove support for malloc_good_size and malloc_usable_size.
9308 We had hoped that these functions would let us eke a little more
9309 memory out of our malloc implementation. Unfortunately, the only
9310 implementations that provided these functions are also ones that
9311 are already efficient about not overallocation: they never got us
9312 more than 7 or so bytes per allocation. Removing them saves us a
9313 little code complexity and a nontrivial amount of build complexity.
9316 - Tor maintainers now require Automake version 1.9 or later to build
9317 Tor from the Git repository. (Automake is not required when building
9318 from a source distribution.)
9321 Changes in version 0.2.3.21-rc - 2012-09-05
9322 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
9323 series. It fixes a trio of potential security bugs, fixes a bug where
9324 we were leaving some of the fast relays out of the microdescriptor
9325 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
9326 and cleans up other smaller issues.
9328 o Major bugfixes (security):
9329 - Tear down the circuit if we get an unexpected SENDME cell. Clients
9330 could use this trick to make their circuits receive cells faster
9331 than our flow control would have allowed, or to gum up the network,
9332 or possibly to do targeted memory denial-of-service attacks on
9333 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
9334 from July 2002, before the release of Tor 0.0.0. We had committed
9335 this patch previously, but we had to revert it because of bug 6271.
9336 Now that 6271 is fixed, this patch appears to work.
9337 - Reject any attempt to extend to an internal address. Without
9338 this fix, a router could be used to probe addresses on an internal
9339 network to see whether they were accepting connections. Fixes bug
9340 6710; bugfix on 0.0.8pre1.
9341 - Do not crash when comparing an address with port value 0 to an
9342 address policy. This bug could have been used to cause a remote
9343 assertion failure by or against directory authorities, or to
9344 allow some applications to crash clients. Fixes bug 6690; bugfix
9348 - Remove the upper bound on microdescriptor length. We were hitting
9349 the limit for routers with complex exit policies or family
9350 declarations, causing clients to not use them. Fixes the first
9351 piece of bug 6404; fix on 0.2.2.6-alpha.
9352 - Detect "ORPort 0" as meaning, uniformly, that we're not running
9353 as a relay. Previously, some of our code would treat the presence
9354 of any ORPort line as meaning that we should act like a relay,
9355 even though our new listener code would correctly not open any
9356 ORPorts for ORPort 0. Similar bugs in other Port options are also
9357 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
9360 - Avoid a pair of double-free and use-after-mark bugs that can
9361 occur with certain timings in canceled and re-received DNS
9362 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
9363 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
9364 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
9365 - Allow one-hop directory fetching circuits the full "circuit build
9366 timeout" period, rather than just half of it, before failing them
9367 and marking the relay down. This fix should help reduce cases where
9368 clients declare relays (or worse, bridges) unreachable because
9369 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
9370 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
9372 - Authorities no longer include any router in their microdescriptor
9373 consensuses for which they couldn't generate or agree on a
9374 microdescriptor. Fixes the second piece of bug 6404; fix on
9376 - Detect and reject attempts to specify both "FooPort" and
9377 "FooPort 0" in the same configuration domain. (It's still okay
9378 to have a FooPort in your configuration file, and use "FooPort 0"
9379 on the command line to disable it.) Fixes the second half of bug
9380 6507; bugfix on 0.2.3.3-alpha.
9381 - Make wildcarded addresses (that is, ones beginning with "*.") work
9382 when provided via the controller's MapAddress command. Previously,
9383 they were accepted, but we never actually noticed that they were
9384 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
9385 - Avoid crashing on a malformed state file where EntryGuardPathBias
9386 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
9387 - Add a (probably redundant) memory clear between iterations of
9388 the router status voting loop, to prevent future coding errors
9389 where data might leak between iterations of the loop. Resolves
9392 o Minor bugfixes (log messages):
9393 - Downgrade "set buildtimeout to low value" messages to "info"
9394 severity; they were never an actual problem, there was never
9395 anything reasonable to do about them, and they tended to spam logs
9396 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
9397 - Downgrade path-bias warning messages to "info". We'll try to get
9398 them working better in 0.2.4. Add internal circuit construction
9399 state to protect against the noisy warn message "Unexpectedly high
9400 circuit_successes". Also add some additional rate-limited notice
9401 messages to help determine the root cause of the warn. Fixes bug
9402 6475. Bugfix against 0.2.3.17-beta.
9403 - Move log message when unable to find a microdesc in a routerstatus
9404 entry to parse time. Previously we'd spam this warning every time
9405 we tried to figure out which microdescriptors to download. Fixes
9406 the third piece of bug 6404; fix on 0.2.3.18-rc.
9409 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
9410 change when the authority is deciding whether to accept a newly
9411 uploaded descriptor. Implements ticket 6423.
9412 - Add missing documentation for consensus and microdesc files.
9413 Resolves ticket 6732.
9416 Changes in version 0.2.2.38 - 2012-08-12
9417 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
9418 attack that could in theory leak path information.
9421 - Avoid an uninitialized memory read when reading a vote or consensus
9422 document that has an unrecognized flavor name. This read could
9423 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
9424 - Try to leak less information about what relays a client is
9425 choosing to a side-channel attacker. Previously, a Tor client would
9426 stop iterating through the list of available relays as soon as it
9427 had chosen one, thus finishing a little earlier when it picked
9428 a router earlier in the list. If an attacker can recover this
9429 timing information (nontrivial but not proven to be impossible),
9430 they could learn some coarse-grained information about which relays
9431 a client was picking (middle nodes in particular are likelier to
9432 be affected than exits). The timing attack might be mitigated by
9433 other factors (see bug 6537 for some discussion), but it's best
9434 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
9437 Changes in version 0.2.3.20-rc - 2012-08-05
9438 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
9439 series. It fixes a pair of code security bugs and a potential anonymity
9440 issue, updates our RPM spec files, and cleans up other smaller issues.
9443 - Avoid read-from-freed-memory and double-free bugs that could occur
9444 when a DNS request fails while launching it. Fixes bug 6480;
9445 bugfix on 0.2.0.1-alpha.
9446 - Avoid an uninitialized memory read when reading a vote or consensus
9447 document that has an unrecognized flavor name. This read could
9448 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
9449 - Try to leak less information about what relays a client is
9450 choosing to a side-channel attacker. Previously, a Tor client would
9451 stop iterating through the list of available relays as soon as it
9452 had chosen one, thus finishing a little earlier when it picked
9453 a router earlier in the list. If an attacker can recover this
9454 timing information (nontrivial but not proven to be impossible),
9455 they could learn some coarse-grained information about which relays
9456 a client was picking (middle nodes in particular are likelier to
9457 be affected than exits). The timing attack might be mitigated by
9458 other factors (see bug 6537 for some discussion), but it's best
9459 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
9462 - Try to make the warning when giving an obsolete SOCKSListenAddress
9463 a little more useful.
9464 - Terminate active server managed proxies if Tor stops being a
9465 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
9466 - Provide a better error message about possible OSX Asciidoc failure
9467 reasons. Fixes bug 6436.
9468 - Warn when Tor is configured to use accounting in a way that can
9469 link a hidden service to some other hidden service or public
9470 address. Resolves ticket 6490.
9473 - Check return value of fputs() when writing authority certificate
9474 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
9475 - Ignore ServerTransportPlugin lines when Tor is not configured as
9476 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
9477 - When disabling guards for having too high a proportion of failed
9478 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
9482 - Update our default RPM spec files to work with mock and rpmbuild
9483 on RHEL/Fedora. They have an updated set of dependencies and
9484 conflicts, a fix for an ancient typo when creating the "_tor"
9485 user, and better instructions. Thanks to Ondrej Mikle for the
9486 patch series. Fixes bug 6043.
9489 - Make it possible to set the TestingTorNetwork configuration
9490 option using AlternateDirAuthority and AlternateBridgeAuthority
9491 as an alternative to setting DirServer. Addresses ticket 6377.
9494 - Clarify the documentation for the Alternate*Authority options.
9496 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
9498 o Code simplification and refactoring:
9499 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
9500 10 lines. Also, don't nest them. Doing so in the past has
9501 led to hard-to-debug code. The new style is to use the
9502 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
9505 Changes in version 0.2.3.19-rc - 2012-07-06
9506 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
9507 series. It fixes the compile on Windows, reverts to a GeoIP database
9508 that isn't as broken, and fixes a flow control bug that has been around
9509 since the beginning of Tor.
9512 - Fix a bug handling SENDME cells on nonexistent streams that could
9513 result in bizarre window values. Report and patch contributed
9514 pseudonymously. Fixes part of bug 6271. This bug was introduced
9515 before the first Tor release, in svn commit r152.
9516 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
9517 June 2012 database, Maxmind marked many Tor relays as country "A1",
9518 which will cause risky behavior for clients that set EntryNodes
9519 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
9520 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
9521 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
9524 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
9525 bugfix on 0.2.1.10-alpha.
9528 Changes in version 0.2.3.18-rc - 2012-06-28
9529 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
9530 series. It fixes a few smaller bugs, but generally appears stable.
9531 Please test it and let us know whether it is!
9534 - Allow wildcarded mapaddress targets to be specified on the
9535 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
9536 - Make our linker option detection code more robust against linkers
9537 such as on FreeBSD 8, where a bad combination of options completes
9538 successfully but makes an unrunnable binary. Fixes bug 6173;
9539 bugfix on 0.2.3.17-beta.
9541 o Minor bugfixes (on 0.2.2.x and earlier):
9542 - Avoid a false positive in the util/threads unit test by increasing
9543 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
9544 - Replace "Sending publish request" log messages with "Launching
9545 upload", so that they no longer confusingly imply that we're
9546 sending something to a directory we might not even be connected
9547 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
9548 - Make sure to set *socket_error in all error cases in
9549 connection_connect(), so it can't produce a warning about
9550 errno being zero from errno_to_orconn_end_reason(). Bugfix on
9551 0.2.1.1-alpha; resolves ticket 6028.
9552 - Downgrade "Got a certificate, but we already have it" log messages
9553 from warning to info, except when we're a dirauth. Fixes bug 5238;
9554 bugfix on 0.2.1.7-alpha.
9555 - When checking for requested signatures on the latest consensus
9556 before serving it to a client, make sure to check the right
9557 consensus flavor. Bugfix on 0.2.2.6-alpha.
9558 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
9559 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
9561 o Minor bugfixes (on 0.2.3.x):
9562 - Make format_helper_exit_status() avoid unnecessary space padding
9563 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
9565 - Downgrade a message about cleaning the microdescriptor cache to
9566 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
9567 - Log a BUG message at severity INFO if we have a networkstatus with
9568 a missing entry for some microdescriptor. Continues on a patch
9570 - Improve the log message when a managed proxy fails to launch. Fixes
9571 bug 5099; bugfix on 0.2.3.6-alpha.
9572 - Don't do DNS lookups when parsing corrupted managed proxy protocol
9573 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
9574 - When formatting wildcarded address mappings for the controller,
9575 be sure to include "*." as appropriate. Partially fixes bug 6244;
9576 bugfix on 0.2.3.9-alpha.
9577 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
9578 Bugfix on 0.2.3.13-alpha.
9579 - Stop logging messages about running with circuit timeout learning
9580 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
9581 - Disable a spurious warning about reading on a marked and flushing
9582 connection. We shouldn't be doing that, but apparently we
9583 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
9584 - Fix a bug that stopped AllowDotExit from working on addresses
9585 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
9588 o Code simplification, refactoring, unit tests:
9589 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
9590 Libevent's notion of cached time when possible.
9591 - Remove duplicate code for invoking getrlimit() from control.c.
9592 - Add a unit test for the environment_variable_names_equal function.
9595 - Document the --defaults-torrc option, and the new (in 0.2.3)
9596 semantics for overriding, extending, and clearing lists of
9597 options. Closes bug 4748.
9600 Changes in version 0.2.3.17-beta - 2012-06-15
9601 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
9602 gets our TLS handshake back on track for being able to blend in with
9603 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
9604 with Vidalia, and otherwise continues to get us closer to a release
9608 - Enable gcc and ld hardening by default. Resolves ticket 5210.
9609 - Update TLS cipher list to match Firefox 8 and later. Resolves
9611 - Implement the client side of proposal 198: remove support for
9612 clients falsely claiming to support standard ciphersuites that
9613 they can actually provide. As of modern OpenSSL versions, it's not
9614 necessary to fake any standard ciphersuite, and doing so prevents
9615 us from using better ciphersuites in the future, since servers
9616 can't know whether an advertised ciphersuite is really supported or
9617 not. Some hosts -- notably, ones with very old versions of OpenSSL
9618 or where OpenSSL has been built with ECC disabled -- will stand
9619 out because of this change; TBB users should not be affected.
9622 - Change the default value for DynamicDHGroups (introduced in
9623 0.2.3.9-alpha) to 0. This feature can make Tor relays less
9624 identifiable by their use of the mod_ssl DH group, but at
9625 the cost of some usability (#4721) and bridge tracing (#6087)
9626 regressions. Resolves ticket 5598.
9627 - Send a CRLF at the end of each STATUS_* control protocol event. This
9628 bug tickled a bug in Vidalia which would make it freeze. Fixes
9629 bug 6094; bugfix on 0.2.3.16-alpha.
9632 - Disable writing on marked-for-close connections when they are
9633 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
9634 bug 5263; bugfix on 0.0.2pre13, where we first added a special
9635 case for flushing marked connections.
9636 - Detect SSL handshake even when the initial attempt to write the
9637 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
9638 - Change the AllowDotExit rules so they should actually work.
9639 We now enforce AllowDotExit only immediately after receiving an
9640 address via SOCKS or DNSPort: other sources are free to provide
9641 .exit addresses after the resolution occurs. Fixes bug 3940;
9642 bugfix on 0.2.2.1-alpha.
9643 - Fix a (harmless) integer overflow in cell statistics reported by
9644 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
9645 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
9646 right places and never depends on the consensus parameters or
9647 computes adaptive timeouts when it is disabled. Fixes bug 5049;
9648 bugfix on 0.2.2.14-alpha.
9649 - When building Tor on Windows with -DUNICODE (not default), ensure
9650 that error messages, filenames, and DNS server names are always
9651 NUL-terminated when we convert them to a single-byte encoding.
9652 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
9653 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
9654 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
9655 - Fix an edge case where TestingTorNetwork is set but the authorities
9656 and relays all have an uptime of zero, where the private Tor network
9657 could briefly lack support for hidden services. Fixes bug 3886;
9658 bugfix on 0.2.2.18-alpha.
9659 - Correct the manpage's descriptions for the default values of
9660 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
9662 - Fix the documentation for the --hush and --quiet command line
9663 options, which changed their behavior back in 0.2.3.3-alpha.
9664 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
9668 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
9669 more information to it, so that we can track it down in case it
9670 returns again. Mitigates bug 5235.
9671 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
9672 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
9673 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
9674 - Warn the user when HTTPProxy, but no other proxy type, is
9675 configured. This can cause surprising behavior: it doesn't send
9676 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
9677 directory traffic only. Resolves ticket 4663.
9678 - Issue a notice if a guard completes less than 40% of your circuits.
9679 Threshold is configurable by torrc option PathBiasNoticeRate and
9680 consensus parameter pb_noticepct. There is additional, off-by-
9681 default code to disable guards which fail too many circuits.
9682 Addresses ticket 5458.
9683 - Update to the June 6 2012 Maxmind GeoLite Country database.
9685 o Code simplifications and refactoring:
9686 - Remove validate_pluggable_transports_config(): its warning
9687 message is now handled by connection_or_connect().
9690 Changes in version 0.2.2.37 - 2012-06-06
9691 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
9692 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
9696 - Work around a bug in OpenSSL that broke renegotiation with TLS
9697 1.1 and TLS 1.2. Without this workaround, all attempts to speak
9698 the v2 Tor connection protocol when both sides were using OpenSSL
9699 1.0.1 would fail. Resolves ticket 6033.
9700 - When waiting for a client to renegotiate, don't allow it to add
9701 any bytes to the input buffer. This fixes a potential DoS issue.
9702 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
9703 - Fix an edge case where if we fetch or publish a hidden service
9704 descriptor, we might build a 4-hop circuit and then use that circuit
9705 for exiting afterwards -- even if the new last hop doesn't obey our
9706 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
9709 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
9710 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
9713 - Tell GCC and Clang to check for any errors in format strings passed
9714 to the tor_v*(print|scan)f functions.
9717 Changes in version 0.2.3.16-alpha - 2012-06-05
9718 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
9719 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
9720 currently). It also fixes a variety of smaller bugs and other cleanups
9721 that get us closer to a release candidate.
9723 o Major bugfixes (general):
9724 - Work around a bug in OpenSSL that broke renegotiation with TLS
9725 1.1 and TLS 1.2. Without this workaround, all attempts to speak
9726 the v2 Tor connection protocol when both sides were using OpenSSL
9727 1.0.1 would fail. Resolves ticket 6033.
9728 - When waiting for a client to renegotiate, don't allow it to add
9729 any bytes to the input buffer. This fixes a potential DoS issue.
9730 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
9731 - Pass correct OR address to managed proxies (like obfsproxy),
9732 even when ORListenAddress is used. Fixes bug 4865; bugfix on
9734 - The advertised platform of a router now includes only its operating
9735 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
9736 service pack level (for Windows) or its CPU architecture (for Unix).
9737 We also no longer include the "git-XYZ" tag in the version. Resolves
9740 o Major bugfixes (clients):
9741 - If we are unable to find any exit that supports our predicted ports,
9742 stop calling them predicted, so that we don't loop and build
9743 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
9744 which introduced predicted ports.
9745 - Fix an edge case where if we fetch or publish a hidden service
9746 descriptor, we might build a 4-hop circuit and then use that circuit
9747 for exiting afterwards -- even if the new last hop doesn't obey our
9748 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
9749 - Check at each new consensus whether our entry guards were picked
9750 long enough ago that we should rotate them. Previously, we only
9751 did this check at startup, which could lead to us holding a guard
9752 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
9753 - When fetching a bridge descriptor from a bridge authority,
9754 always do so anonymously, whether we have been able to open
9755 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
9756 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
9757 but we'll need to wait for bug 6010 before it's actually usable.
9759 o Major bugfixes (directory authorities):
9760 - When computing weight parameters, behave more robustly in the
9761 presence of a bad bwweightscale value. Previously, the authorities
9762 would crash if they agreed on a sufficiently broken weight_scale
9763 value: now, they use a reasonable default and carry on. Partial
9764 fix for 5786; bugfix on 0.2.2.17-alpha.
9765 - Check more thoroughly to prevent a rogue authority from
9766 double-voting on any consensus directory parameter. Previously,
9767 authorities would crash in this case if the total number of
9768 votes for any parameter exceeded the number of active voters,
9769 but would let it pass otherwise. Partial fix for bug 5786; bugfix
9773 - Rate-limit log messages when asked to connect anonymously to
9774 a private address. When these hit, they tended to hit fast and
9775 often. Also, don't bother trying to connect to addresses that we
9776 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
9777 reply makes us think we have been lied to, even when the address the
9778 client tried to connect to was "localhost." Resolves ticket 2822.
9779 - Allow packagers to insert an extra string in server descriptor
9780 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
9781 Resolves the rest of ticket 2988.
9782 - Raise the threshold of server descriptors needed (75%) and exit
9783 server descriptors needed (50%) before we will declare ourselves
9784 bootstrapped. This will make clients start building circuits a
9785 little later, but makes the initially constructed circuits less
9786 skewed and less in conflict with further directory fetches. Fixes
9788 - Close any connection that sends unrecognized junk before the
9789 handshake. Solves an issue noted in bug 4369.
9790 - Improve log messages about managed transports. Resolves ticket 5070.
9791 - Tag a bridge's descriptor as "never to be sent unencrypted".
9792 This shouldn't matter, since bridges don't open non-anonymous
9793 connections to the bridge authority and don't allow unencrypted
9794 directory connections from clients, but we might as well make
9795 sure. Closes bug 5139.
9796 - Expose our view of whether we have gone dormant to the controller,
9797 via a new "GETINFO dormant" value. Torbutton and other controllers
9798 can use this to avoid doing periodic requests through Tor while
9799 it's dormant (bug 4718). Fixes bug 5954.
9800 - Tell GCC and Clang to check for any errors in format strings passed
9801 to the tor_v*(print|scan)f functions.
9802 - Update to the May 1 2012 Maxmind GeoLite Country database.
9804 o Minor bugfixes (already included in 0.2.2.36):
9805 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
9806 Fixes bug 5346; bugfix on 0.0.8pre3.
9807 - Correct parsing of certain date types in parse_http_time().
9808 Without this patch, If-Modified-Since would behave
9809 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
9810 Esteban Manchado Velázques.
9811 - Make our number-parsing functions always treat too-large values
9812 as an error, even when those values exceed the width of the
9813 underlying type. Previously, if the caller provided these
9814 functions with minima or maxima set to the extreme values of the
9815 underlying integer type, these functions would return those
9816 values on overflow rather than treating overflow as an error.
9817 Fixes part of bug 5786; bugfix on 0.0.9.
9818 - If we hit the error case where routerlist_insert() replaces an
9819 existing (old) server descriptor, make sure to remove that
9820 server descriptor from the old_routers list. Fix related to bug
9821 1776. Bugfix on 0.2.2.18-alpha.
9822 - Clarify the behavior of MaxCircuitDirtiness with hidden service
9823 circuits. Fixes issue 5259.
9825 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
9826 - Prevent a null-pointer dereference when receiving a data cell
9827 for a nonexistent stream when the circuit in question has an
9828 empty deliver window. We don't believe this is triggerable,
9829 since we don't currently allow deliver windows to become empty,
9830 but the logic is tricky enough that it's better to make the code
9831 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
9832 - Fix a memory leak when trying to launch a DNS request when the
9833 network is disabled or the nameservers are unconfigurable. Fixes
9834 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
9835 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
9836 - Don't hold a Windows file handle open for every file mapping;
9837 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
9839 - Avoid O(n^2) performance characteristics when parsing a large
9840 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
9841 - Format more doubles with %f, not %lf. Patch from grarpamp to make
9842 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
9844 - Make our replacement implementation of strtok_r() compatible with
9845 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
9846 bugfix on 0.2.2.1-alpha.
9847 - Fix a NULL-pointer dereference on a badly formed
9848 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
9849 bugfix on 0.2.2.9-alpha.
9850 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
9851 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
9852 - Defensively refactor rend_mid_rendezvous() so that protocol
9853 violations and length checks happen in the beginning. Fixes
9855 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
9856 that IPv6 stuff will compile on MSVC, and compilation issues
9857 will be easier to track down. Fixes bug 5861.
9859 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
9860 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
9861 resource exhaustion, so that clients can adjust their load to
9862 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
9863 started using END_STREAM_REASON_RESOURCELIMIT.
9864 - Don't check for whether the address we're using for outbound
9865 connections has changed until after the outbound connection has
9866 completed. On Windows, getsockname() doesn't succeed until the
9867 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
9868 - If the configuration tries to set MyFamily on a bridge, refuse to
9869 do so, and warn about the security implications. Fixes bug 4657;
9870 bugfix on 0.2.0.3-alpha.
9871 - If the client fails to set a reasonable set of ciphersuites
9872 during its v2 handshake renegotiation, allow the renegotiation to
9873 continue nevertheless (i.e. send all the required certificates).
9874 Fixes bug 4591; bugfix on 0.2.0.20-rc.
9875 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
9876 option is set to 0 (which Vidalia version 0.2.16 now does when
9877 a SAVECONF attempt fails), perform other actions that SIGHUP
9878 usually causes (like reopening the logs). Fixes bug 5095; bugfix
9880 - If we fail to write a microdescriptor to the disk cache, do not
9881 continue replacing the old microdescriptor file. Fixes bug 2954;
9882 bugfix on 0.2.2.6-alpha.
9883 - Exit nodes don't need to fetch certificates for authorities that
9884 they don't recognize; only directory authorities, bridges,
9885 and caches need to do that. Fixes part of bug 2297; bugfix on
9887 - Correctly handle checking the permissions on the parent
9888 directory of a control socket in the root directory. Bug found
9889 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
9891 - When told to add a bridge with the same digest as a preexisting
9892 bridge but a different addr:port, change the addr:port as
9893 requested. Previously we would not notice the change. Fixes half
9894 of bug 5603; fix on 0.2.2.26-beta.
9895 - End AUTHCHALLENGE error messages (in the control protocol) with
9896 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
9898 o Minor bugfixes (on 0.2.3.x):
9899 - Turn an assertion (that the number of handshakes received as a
9900 server is not < 1) into a warning. Fixes bug 4873; bugfix on
9902 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
9903 we had reversed them when the answer was cached.) Fixes bug
9904 5723; bugfix on 0.2.3.1-alpha.
9905 - Work correctly on Linux systems with accept4 support advertised in
9906 their headers, but without accept4 support in the kernel. Fix
9907 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
9908 - When told to add a bridge with the same addr:port as a preexisting
9909 bridge but a different transport, change the transport as
9910 requested. Previously we would not notice the change. Fixes half
9911 of bug 5603; fix on 0.2.3.2-alpha.
9912 - Avoid a "double-reply" warning when replying to a SOCKS request
9913 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
9914 bugfix on 0.2.3.4-alpha.
9915 - Fix a bug where a bridge authority crashes if it has seen no
9916 directory requests when it's time to write statistics to disk.
9917 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
9919 - Don't try to open non-control listeners when DisableNetwork is set.
9920 Previously, we'd open all listeners, then immediately close them.
9921 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
9922 - Don't abort the managed proxy protocol if the managed proxy
9923 sends us an unrecognized line; ignore it instead. Fixes bug
9924 5910; bugfix on 0.2.3.9-alpha.
9925 - Fix a compile warning in crypto.c when compiling with clang 3.1.
9926 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
9927 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
9928 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
9929 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
9930 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
9931 - Resolve numerous small warnings and build issues with MSVC. Resolves
9934 o Documentation fixes:
9935 - Improve the manual's documentation for the NT Service command-line
9936 options. Addresses ticket 3964.
9937 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
9938 - Document the changes to the ORPort and DirPort options, and the
9939 fact that {OR/Dir}ListenAddress is now unnecessary (and
9940 therefore deprecated). Resolves ticket 5597.
9943 - Remove the torrc.bridge file: we don't use it for anything, and
9944 it had become badly desynchronized from torrc.sample. Resolves
9948 Changes in version 0.2.2.36 - 2012-05-24
9949 Tor 0.2.2.36 updates the addresses for two of the eight directory
9950 authorities, fixes some potential anonymity and security issues,
9951 and fixes several crash bugs.
9953 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
9954 known flaws, and nobody should be using them. You should upgrade. If
9955 you're using a Linux or BSD and its packages are obsolete, stop using
9956 those packages and upgrade anyway.
9958 o Directory authority changes:
9959 - Change IP address for maatuska (v3 directory authority).
9960 - Change IP address for ides (v3 directory authority), and rename
9964 - When building or running with any version of OpenSSL earlier
9965 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
9966 versions have a bug (CVE-2011-4576) in which their block cipher
9967 padding includes uninitialized data, potentially leaking sensitive
9968 information to any peer with whom they make a SSLv3 connection. Tor
9969 does not use SSL v3 by default, but a hostile client or server
9970 could force an SSLv3 connection in order to gain information that
9971 they shouldn't have been able to get. The best solution here is to
9972 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
9973 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
9974 to make sure that the bug can't happen.
9975 - Never use a bridge or a controller-supplied node as an exit, even
9976 if its exit policy allows it. Found by wanoskarnet. Fixes bug
9977 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
9978 and 0.2.0.3-alpha (for bridge-purpose descriptors).
9979 - Only build circuits if we have a sufficient threshold of the total
9980 descriptors that are marked in the consensus with the "Exit"
9981 flag. This mitigates an attack proposed by wanoskarnet, in which
9982 all of a client's bridges collude to restrict the exit nodes that
9983 the client knows about. Fixes bug 5343.
9984 - Provide controllers with a safer way to implement the cookie
9985 authentication mechanism. With the old method, if another locally
9986 running program could convince a controller that it was the Tor
9987 process, then that program could trick the controller into telling
9988 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
9989 authentication method uses a challenge-response approach to prevent
9990 this attack. Fixes bug 5185; implements proposal 193.
9993 - Avoid logging uninitialized data when unable to decode a hidden
9994 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
9995 - Avoid a client-side assertion failure when receiving an INTRODUCE2
9996 cell on a general purpose circuit. Fixes bug 5644; bugfix on
9998 - Fix builds when the path to sed, openssl, or sha1sum contains
9999 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
10001 - Correct our replacements for the timeradd() and timersub() functions
10002 on platforms that lack them (for example, Windows). The timersub()
10003 function is used when expiring circuits, while timeradd() is
10004 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
10005 bugfix on 0.2.2.24-alpha.
10006 - Fix the SOCKET_OK test that we use to tell when socket
10007 creation fails so that it works on Win64. Fixes part of bug 4533;
10008 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
10011 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
10012 Fixes bug 5346; bugfix on 0.0.8pre3.
10013 - Make our number-parsing functions always treat too-large values
10014 as an error, even when those values exceed the width of the
10015 underlying type. Previously, if the caller provided these
10016 functions with minima or maxima set to the extreme values of the
10017 underlying integer type, these functions would return those
10018 values on overflow rather than treating overflow as an error.
10019 Fixes part of bug 5786; bugfix on 0.0.9.
10020 - Older Linux kernels erroneously respond to strange nmap behavior
10021 by having accept() return successfully with a zero-length
10022 socket. When this happens, just close the connection. Previously,
10023 we would try harder to learn the remote address: but there was
10024 no such remote address to learn, and our method for trying to
10025 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
10026 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
10027 - Correct parsing of certain date types in parse_http_time().
10028 Without this patch, If-Modified-Since would behave
10029 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
10030 Esteban Manchado Velázques.
10031 - Change the BridgePassword feature (part of the "bridge community"
10032 design, which is not yet implemented) to use a time-independent
10033 comparison. The old behavior might have allowed an adversary
10034 to use timing to guess the BridgePassword value. Fixes bug 5543;
10035 bugfix on 0.2.0.14-alpha.
10036 - Detect and reject certain misformed escape sequences in
10037 configuration values. Previously, these values would cause us
10038 to crash if received in a torrc file or over an authenticated
10039 control port. Bug found by Esteban Manchado Velázquez, and
10040 independently by Robert Connolly from Matta Consulting who further
10041 noted that it allows a post-authentication heap overflow. Patch
10042 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
10043 bugfix on 0.2.0.16-alpha.
10044 - Fix a compile warning when using the --enable-openbsd-malloc
10045 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
10046 - During configure, detect when we're building with clang version
10047 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
10048 CFLAGS. clang doesn't support them yet.
10049 - When sending an HTTP/1.1 proxy request, include a Host header.
10050 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
10051 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
10052 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
10053 - If we hit the error case where routerlist_insert() replaces an
10054 existing (old) server descriptor, make sure to remove that
10055 server descriptor from the old_routers list. Fix related to bug
10056 1776. Bugfix on 0.2.2.18-alpha.
10058 o Minor bugfixes (documentation and log messages):
10059 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
10060 Fixes bug 4856; bugfix on Tor 0.0.6.
10061 - Update "ClientOnly" man page entry to explain that there isn't
10062 really any point to messing with it. Resolves ticket 5005.
10063 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
10064 directory authority option (introduced in Tor 0.2.2.34).
10065 - Downgrade the "We're missing a certificate" message from notice
10066 to info: people kept mistaking it for a real problem, whereas it
10067 is seldom the problem even when we are failing to bootstrap. Fixes
10068 bug 5067; bugfix on 0.2.0.10-alpha.
10069 - Correctly spell "connect" in a log message on failure to create a
10070 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
10071 - Clarify the behavior of MaxCircuitDirtiness with hidden service
10072 circuits. Fixes issue 5259.
10075 - Directory authorities now reject versions of Tor older than
10076 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
10077 inclusive. These versions accounted for only a small fraction of
10078 the Tor network, and have numerous known security issues. Resolves
10080 - Update to the May 1 2012 Maxmind GeoLite Country database.
10083 - When sending or relaying a RELAY_EARLY cell, we used to convert
10084 it to a RELAY cell if the connection was using the v1 link
10085 protocol. This was a workaround for older versions of Tor, which
10086 didn't handle RELAY_EARLY cells properly. Now that all supported
10087 versions can handle RELAY_EARLY cells, and now that we're enforcing
10088 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
10089 remove this workaround. Addresses bug 4786.
10092 Changes in version 0.2.3.15-alpha - 2012-04-30
10093 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
10094 the development branch build on Windows again.
10096 o Minor bugfixes (on 0.2.2.x and earlier):
10097 - Make sure that there are no unhandled pending TLS errors before
10098 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
10099 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
10100 Bugfix on 0.1.0.5-rc; fixes bug 4528.
10101 - Fix an assert that directory authorities could trigger on sighup
10102 during some configuration state transitions. We now don't treat
10103 it as a fatal error when the new descriptor we just generated in
10104 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
10105 - After we pick a directory mirror, we would refuse to use it if
10106 it's in our ExcludeExitNodes list, resulting in mysterious failures
10107 to bootstrap for people who just wanted to avoid exiting from
10108 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
10109 - When building with --enable-static-tor on OpenBSD, do not
10110 erroneously attempt to link -lrt. Fixes bug 5103.
10112 o Minor bugfixes (on 0.2.3.x):
10113 - When Tor is built with kernel headers from a recent (last few
10114 years) Linux kernel, do not fail to run on older (pre-2.6.28
10115 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
10116 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
10117 and 0.2.3.12-alpha.
10118 - Fix compilation with miniupnpc version 1.6; patch from
10119 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
10120 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
10121 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
10122 - Fix compilation on platforms without unistd.h, or where environ
10123 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
10126 - Directory authorities are now a little more lenient at accepting
10127 older router descriptors, or newer router descriptors that don't
10128 make big changes. This should help ameliorate past and future
10129 issues where routers think they have uploaded valid descriptors,
10130 but the authorities don't think so. Fix for ticket 2479.
10131 - Make the code that clients use to detect an address change be
10132 IPv6-aware, so that it won't fill clients' logs with error
10133 messages when trying to get the IPv4 address of an IPv6
10134 connection. Implements ticket 5537.
10136 o Removed features:
10137 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
10138 authorities needed to use it for a while to keep the network working
10139 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
10140 that was six months ago. As of now, it should no longer be needed
10144 Changes in version 0.2.3.14-alpha - 2012-04-23
10145 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
10146 candidate. It also dramatically speeds up AES: fast relays should
10147 consider switching to the newer OpenSSL library.
10149 o Directory authority changes:
10150 - Change IP address for ides (v3 directory authority), and rename
10154 - Avoid logging uninitialized data when unable to decode a hidden
10155 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
10156 - Avoid a client-side assertion failure when receiving an INTRODUCE2
10157 cell on a general purpose circuit. Fixes bug 5644; bugfix on
10159 - If authorities are unable to get a v2 consensus document from other
10160 directory authorities, they no longer fall back to fetching
10161 them from regular directory caches. Fixes bug 5635; bugfix on
10162 0.2.2.26-beta, where routers stopped downloading v2 consensus
10163 documents entirely.
10164 - When we start a Tor client with a normal consensus already cached,
10165 be willing to download a microdescriptor consensus. Fixes bug 4011;
10166 fix on 0.2.3.1-alpha.
10168 o Major features (performance):
10169 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
10170 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
10171 vectorized AES implementations as appropriate. These can be much,
10172 much faster than other AES implementations.
10174 o Minor bugfixes (0.2.2.x and earlier):
10175 - Don't launch more than 10 service-side introduction-point circuits
10176 for a hidden service in five minutes. Previously, we would consider
10177 launching more introduction-point circuits if at least one second
10178 had passed without any introduction-point circuits failing. Fixes
10179 bug 4607; bugfix on 0.0.7pre1.
10180 - Change the BridgePassword feature (part of the "bridge community"
10181 design, which is not yet implemented) to use a time-independent
10182 comparison. The old behavior might have allowed an adversary
10183 to use timing to guess the BridgePassword value. Fixes bug 5543;
10184 bugfix on 0.2.0.14-alpha.
10185 - Enforce correct return behavior of tor_vsscanf() when the '%%'
10186 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
10187 - When sending an HTTP/1.1 proxy request, include a Host header.
10188 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
10189 - Don't log that we have "decided to publish new relay descriptor"
10190 unless we are actually publishing a descriptor. Fixes bug 3942;
10191 bugfix on 0.2.2.28-beta.
10193 o Minor bugfixes (0.2.3.x):
10194 - Fix a bug where a bridge authority crashes (on a failed assert)
10195 if it has seen no directory requests when it's time to write
10196 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
10197 - Fix bug stomping on ORPort option NoListen and ignoring option
10198 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
10199 - In the testsuite, provide a large enough buffer in the tor_sscanf
10200 unit test. Otherwise we'd overrun that buffer and crash during
10201 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
10203 - Make sure we create the keys directory if it doesn't exist and we're
10204 about to store the dynamic Diffie-Hellman parameters. Fixes bug
10205 5572; bugfix on 0.2.3.13-alpha.
10206 - Fix a small memory leak when trying to decode incorrect base16
10207 authenticator during SAFECOOKIE authentication. Found by
10208 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
10211 - Add more information to a log statement that might help track down
10212 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
10213 non-IP address" messages (or any Bug messages, for that matter!),
10214 please let us know about it.
10215 - Relays now understand an IPv6 address when they get one from a
10216 directory server. Resolves ticket 4875.
10217 - Resolve IPv6 addresses in bridge and entry statistics to country
10218 code "??" which means we at least count them. Resolves ticket 5053;
10219 improves on 0.2.3.9-alpha.
10220 - Update to the April 3 2012 Maxmind GeoLite Country database.
10221 - Begin a doc/state-contents.txt file to explain the contents of
10222 the Tor state file. Fixes bug 2987.
10224 o Default torrc changes:
10225 - Stop listing "socksport 9050" in torrc.sample. We open a socks
10226 port on 9050 by default anyway, so this should not change anything
10228 - Stop mentioning the deprecated *ListenAddress options in
10229 torrc.sample. Fixes bug 5438.
10230 - Document unit of bandwidth related options in sample torrc.
10233 o Removed features:
10234 - The "torify" script no longer supports the "tsocks" socksifier
10235 tool, since tsocks doesn't support DNS and UDP right for Tor.
10236 Everyone should be using torsocks instead. Fixes bugs 3530 and
10237 5180. Based on a patch by "ugh".
10239 o Code refactoring:
10240 - Change the symmetric cipher interface so that creating and
10241 initializing a stream cipher are no longer separate functions.
10242 - Remove all internal support for unpadded RSA. We never used it, and
10243 it would be a bad idea to start.
10246 Changes in version 0.2.3.13-alpha - 2012-03-26
10247 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
10248 in managed pluggable transports, as well as providing other cleanups
10249 that get us closer to a release candidate.
10251 o Directory authority changes:
10252 - Change IP address for maatuska (v3 directory authority).
10255 - Provide controllers with a safer way to implement the cookie
10256 authentication mechanism. With the old method, if another locally
10257 running program could convince a controller that it was the Tor
10258 process, then that program could trick the controller into telling
10259 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
10260 authentication method uses a challenge-response approach to prevent
10261 this attack. Fixes bug 5185, implements proposal 193.
10262 - Never use a bridge or a controller-supplied node as an exit, even
10263 if its exit policy allows it. Found by wanoskarnet. Fixes bug
10264 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
10265 and 0.2.0.3-alpha (for bridge-purpose descriptors).
10266 - Only build circuits if we have a sufficient threshold of the total
10267 descriptors that are marked in the consensus with the "Exit"
10268 flag. This mitigates an attack proposed by wanoskarnet, in which
10269 all of a client's bridges collude to restrict the exit nodes that
10270 the client knows about. Fixes bug 5343.
10272 o Major bugfixes (on Tor 0.2.3.x):
10273 - Avoid an assert when managed proxies like obfsproxy are configured,
10274 and we receive HUP signals or setconf attempts too rapidly. This
10275 situation happens most commonly when Vidalia tries to attach to
10276 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
10277 bugfix on 0.2.3.6-alpha.
10278 - Fix a relay-side pluggable transports bug where managed proxies were
10279 unreachable from the Internet, because Tor asked them to bind on
10280 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
10281 - Stop discarding command-line arguments when TestingTorNetwork
10282 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
10283 0.2.3.9-alpha, where task 4552 added support for two layers of
10285 - Resume allowing the unit tests to run in gdb. This was accidentally
10286 made impossible when the DisableDebuggerAttachment option was
10287 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
10288 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
10289 0.2.3.11-alpha. Reported by Anthony G. Basile.
10291 o Minor bugfixes (on 0.2.2.x and earlier):
10292 - Ensure we don't cannibalize circuits that are longer than three hops
10293 already, so we don't end up making circuits with 5 or more
10294 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
10295 0.1.0.1-rc which introduced cannibalization.
10296 - Detect and reject certain misformed escape sequences in
10297 configuration values. Previously, these values would cause us
10298 to crash if received in a torrc file or over an authenticated
10299 control port. Bug found by Esteban Manchado Velázquez, and
10300 independently by Robert Connolly from Matta Consulting who further
10301 noted that it allows a post-authentication heap overflow. Patch
10302 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
10303 bugfix on 0.2.0.16-alpha.
10304 - Fix a compile warning when using the --enable-openbsd-malloc
10305 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
10306 - Directory caches no longer refuse to clean out descriptors because
10307 of missing v2 networkstatus documents, unless they're configured
10308 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
10309 0.2.2.26-beta. Patch by Daniel Bryg.
10310 - Update to the latest version of the tinytest unit testing framework.
10311 This includes a couple of bugfixes that can be relevant for
10312 running forked unit tests on Windows, and removes all reserved
10315 o Minor bugfixes (on 0.2.3.x):
10316 - On a failed pipe() call, don't leak file descriptors. Fixes bug
10317 4296; bugfix on 0.2.3.1-alpha.
10318 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
10319 until after we have received a CERTS cell. Fixes bug 4361; bugfix
10320 on 0.2.3.6-alpha. Patch by "frosty".
10321 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
10322 option, so that the IP stack doesn't decide to use it for IPv4
10323 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
10324 - Ensure that variables set in Tor's environment cannot override
10325 environment variables that Tor passes to a managed
10326 pluggable-transport proxy. Previously, Tor would pass every
10327 variable in its environment to managed proxies along with the new
10328 ones, in such a way that on many operating systems, the inherited
10329 environment variables would override those which Tor tried to
10330 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
10331 bugfix on 0.2.3.9-alpha for Windows.
10334 - A wide variety of new unit tests by Esteban Manchado Velázquez.
10335 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
10336 - Update to the March 6 2012 Maxmind GeoLite Country database.
10339 Changes in version 0.2.3.12-alpha - 2012-02-13
10340 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
10341 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
10342 when Tor is configured to use a pluggable transport like obfsproxy.
10345 - Fix builds when the path to sed, openssl, or sha1sum contains
10346 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
10348 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
10349 connections. This change should allow busy exit relays to stop
10350 running out of available sockets as quickly. Fixes bug 4950;
10351 bugfix on 0.2.2.26-beta.
10352 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
10353 would ask the bridge for microdescriptors, which are only supported
10354 in 0.2.3.x, and then fail to bootstrap when it didn't get the
10355 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
10356 - Properly set up obfsproxy's environment when in managed mode. The
10357 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
10358 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
10359 5076 and 5082; bugfix on 0.2.3.6-alpha.
10362 - Use the dead_strip option when building Tor on OS X. This reduces
10363 binary size by almost 19% when linking openssl and libevent
10364 statically, which we do for Tor Browser Bundle.
10365 - Fix broken URLs in the sample torrc file, and tell readers about
10366 the OutboundBindAddress, ExitPolicyRejectPrivate, and
10367 PublishServerDescriptor options. Addresses bug 4652.
10368 - Update to the February 7 2012 Maxmind GeoLite Country database.
10371 - Downgrade the "We're missing a certificate" message from notice
10372 to info: people kept mistaking it for a real problem, whereas it
10373 is seldom the problem even when we are failing to bootstrap. Fixes
10374 bug 5067; bugfix on 0.2.0.10-alpha.
10375 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
10376 managed pluggable transport server proxy's environment.
10377 Previously, we would put it there, even though Tor doesn't
10378 implement an 'extended server port' yet, and even though Tor
10379 almost certainly isn't listening at that address. For now, we set
10380 it to an empty string to avoid crashing older obfsproxies. Bugfix
10382 - Log the heartbeat message every HeartbeatPeriod seconds, not every
10383 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
10384 0.2.3.1-alpha. Bug reported by Scott Bennett.
10385 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
10386 bugfix on 0.2.3.11-alpha.
10387 - Update "ClientOnly" man page entry to explain that there isn't
10388 really any point to messing with it. Resolves ticket 5005.
10389 - Use the correct CVE number for CVE-2011-4576 in our comments and
10390 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
10393 o Code simplifications and refactoring:
10394 - Use the _WIN32 macro throughout our code to detect Windows.
10395 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
10399 Changes in version 0.2.3.11-alpha - 2012-01-22
10400 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
10401 the last step of the plan to limit maximum circuit length, includes
10402 a wide variety of hidden service performance and correctness fixes,
10403 works around an OpenSSL security flaw if your distro is too stubborn
10404 to upgrade, and fixes a bunch of smaller issues.
10407 - Now that Tor 0.2.0.x is completely deprecated, enable the final
10408 part of "Proposal 110: Avoiding infinite length circuits" by
10409 refusing all circuit-extend requests that do not use a relay_early
10410 cell. This change helps Tor resist a class of denial-of-service
10411 attacks by limiting the maximum circuit length.
10412 - Adjust the number of introduction points that a hidden service
10413 will try to maintain based on how long its introduction points
10414 remain in use and how many introductions they handle. Fixes
10416 - Try to use system facilities for enumerating local interface
10417 addresses, before falling back to our old approach (which was
10418 binding a UDP socket, and calling getsockname() on it). That
10419 approach was scaring OS X users whose draconian firewall
10420 software warned about binding to UDP sockets, regardless of
10421 whether packets were sent. Now we try to use getifaddrs(),
10422 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
10423 system supports. Resolves ticket 1827.
10425 o Major security workaround:
10426 - When building or running with any version of OpenSSL earlier
10427 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
10428 versions have a bug (CVE-2011-4576) in which their block cipher
10429 padding includes uninitialized data, potentially leaking sensitive
10430 information to any peer with whom they make a SSLv3 connection. Tor
10431 does not use SSL v3 by default, but a hostile client or server
10432 could force an SSLv3 connection in order to gain information that
10433 they shouldn't have been able to get. The best solution here is to
10434 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
10435 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
10436 to make sure that the bug can't happen.
10439 - Fix the SOCKET_OK test that we use to tell when socket
10440 creation fails so that it works on Win64. Fixes part of bug 4533;
10441 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
10442 - Correct our replacements for the timeradd() and timersub() functions
10443 on platforms that lack them (for example, Windows). The timersub()
10444 function is used when expiring circuits, while timeradd() is
10445 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
10446 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
10447 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
10448 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
10449 bug at runtime, not compile time, because some distributions hack
10450 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
10451 on 0.2.3.9-alpha. Found by Pascal.
10453 o Minor features (controller):
10454 - Use absolute path names when reporting the torrc filename in the
10455 control protocol, so a controller can more easily find the torrc
10456 file. Resolves bug 1101.
10457 - Extend the control protocol to report flags that control a circuit's
10458 path selection in CIRC events and in replies to 'GETINFO
10459 circuit-status'. Implements part of ticket 2411.
10460 - Extend the control protocol to report the hidden service address
10461 and current state of a hidden-service-related circuit in CIRC
10462 events and in replies to 'GETINFO circuit-status'. Implements part
10464 - When reporting the path to the cookie file to the controller,
10465 give an absolute path. Resolves ticket 4881.
10466 - Allow controllers to request an event notification whenever a
10467 circuit is cannibalized or its purpose is changed. Implements
10468 part of ticket 3457.
10469 - Include the creation time of a circuit in CIRC and CIRC2
10470 control-port events and the list produced by the 'GETINFO
10471 circuit-status' control-port command.
10473 o Minor features (directory authorities):
10474 - Directory authorities now reject versions of Tor older than
10475 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
10476 inclusive. These versions accounted for only a small fraction of
10477 the Tor network, and have numerous known security issues. Resolves
10479 - Authority operators can now vote for all relays in a given
10480 set of countries to be BadDir/BadExit/Invalid/Rejected.
10481 - Provide two consensus parameters (FastFlagMinThreshold and
10482 FastFlagMaxThreshold) to control the range of allowable bandwidths
10483 for the Fast directory flag. These allow authorities to run
10484 experiments on appropriate requirements for being a "Fast" node.
10485 The AuthDirFastGuarantee config value still applies. Implements
10487 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
10488 directory authority option (introduced in Tor 0.2.2.34).
10490 o Minor features (other):
10491 - Don't disable the DirPort when we cannot exceed our AccountingMax
10492 limit during this interval because the effective bandwidthrate is
10493 low enough. This is useful in a situation where AccountMax is only
10494 used as an additional safeguard or to provide statistics.
10495 - Prepend an informative header to generated dynamic_dh_params files.
10496 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
10497 EntryNodes will have no effect. Resolves issue 2571.
10498 - Log more useful messages when we fail to disable debugger
10500 - Log which authority we're missing votes from when we go to fetch
10501 them from the other auths.
10502 - Log (at debug level) whenever a circuit's purpose is changed.
10503 - Add missing documentation for the MaxClientCircuitsPending,
10504 UseMicrodescriptors, UserspaceIOCPBuffers, and
10505 _UseFilteringSSLBufferevents options, all introduced during
10506 the 0.2.3.x series.
10507 - Update to the January 3 2012 Maxmind GeoLite Country database.
10509 o Minor bugfixes (hidden services):
10510 - Don't close hidden service client circuits which have almost
10511 finished connecting to their destination when they reach
10512 the normal circuit-build timeout. Previously, we would close
10513 introduction circuits which are waiting for an acknowledgement
10514 from the introduction point, and rendezvous circuits which have
10515 been specified in an INTRODUCE1 cell sent to a hidden service,
10516 after the normal CBT. Now, we mark them as 'timed out', and launch
10517 another rendezvous attempt in parallel. This behavior change can
10518 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
10519 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
10520 - Don't close hidden-service-side rendezvous circuits when they
10521 reach the normal circuit-build timeout. This behavior change can
10522 be disabled using the new
10523 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
10524 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
10525 - Make sure we never mark the wrong rendezvous circuit as having
10526 had its introduction cell acknowleged by the introduction-point
10527 relay. Previously, when we received an INTRODUCE_ACK cell on a
10528 client-side hidden-service introduction circuit, we might have
10529 marked a rendezvous circuit other than the one we specified in
10530 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
10531 a warning message and interfered with the hidden service
10532 connection-establishment process. Fixes bug 4759; bugfix on
10533 0.2.3.3-alpha, when we added the stream-isolation feature which
10534 might cause Tor to open multiple rendezvous circuits for the same
10536 - Don't trigger an assertion failure when we mark a new client-side
10537 hidden-service introduction circuit for close during the process
10538 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
10541 o Minor bugfixes (log messages):
10542 - Correctly spell "connect" in a log message on failure to create a
10543 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
10545 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
10546 Fixes bug 4856; bugfix on Tor 0.0.6.
10547 - Fix the log message describing how we work around discovering
10548 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
10549 4837; bugfix on 0.2.2.9-alpha.
10550 - When logging about a disallowed .exit name, do not also call it
10551 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
10553 o Minor bugfixes (build fixes):
10554 - During configure, detect when we're building with clang version
10555 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
10556 CFLAGS. clang doesn't support them yet.
10557 - During configure, search for library containing cos function as
10558 libm lives in libcore on some platforms (BeOS/Haiku). Linking
10559 against libm was hard-coded before. Fixes the first part of bug
10560 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
10562 - Detect attempts to build Tor on (as yet hypothetical) versions
10563 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
10564 fix for bug 4533. Bugfix on 0.2.2.28-beta.
10565 - Preprocessor directives should not be put inside the arguments
10566 of a macro. This would break compilation with GCC releases prior
10567 to version 3.3. We would never recommend such an old GCC version,
10568 but it is apparently required for binary compatibility on some
10569 platforms (namely, certain builds of Haiku). Fixes the other part
10570 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
10573 o Minor bugfixes (other):
10574 - Older Linux kernels erroneously respond to strange nmap behavior
10575 by having accept() return successfully with a zero-length
10576 socket. When this happens, just close the connection. Previously,
10577 we would try harder to learn the remote address: but there was
10578 no such remote address to learn, and our method for trying to
10579 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
10580 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
10581 - Fix null-pointer access that could occur if TLS allocation failed.
10582 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
10583 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
10584 accidentally been reverted.
10585 - Fix our implementation of crypto_random_hostname() so it can't
10586 overflow on ridiculously large inputs. (No Tor version has ever
10587 provided this kind of bad inputs, but let's be correct in depth.)
10588 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
10589 - Find more places in the code that should have been testing for
10590 invalid sockets using the SOCKET_OK macro. Required for a fix
10591 for bug 4533. Bugfix on 0.2.2.28-beta.
10592 - Fix an assertion failure when, while running with bufferevents, a
10593 connection finishes connecting after it is marked for close, but
10594 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
10595 - test_util_spawn_background_ok() hardcoded the expected value
10596 for ENOENT to 2. This isn't portable as error numbers are
10597 platform specific, and particularly the hurd has ENOENT at
10598 0x40000002. Construct expected string at runtime, using the correct
10599 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
10600 - Reject attempts to disable DisableDebuggerAttachment while Tor is
10601 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
10602 - Use an appropriate-width type for sockets in tor-fw-helper on
10603 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
10606 - When sending or relaying a RELAY_EARLY cell, we used to convert
10607 it to a RELAY cell if the connection was using the v1 link
10608 protocol. This was a workaround for older versions of Tor, which
10609 didn't handle RELAY_EARLY cells properly. Now that all supported
10610 versions can handle RELAY_EARLY cells, and now that we're enforcing
10611 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
10612 remove this workaround. Addresses bug 4786.
10614 o Code simplifications and refactoring:
10615 - Use OpenSSL's built-in SSL_state_string_long() instead of our
10616 own homebrewed ssl_state_to_string() replacement. Patch from
10617 Emile Snyder. Fixes bug 4653.
10618 - Use macros to indicate OpenSSL versions, so we don't need to worry
10619 about accidental hexadecimal bit shifts.
10620 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
10622 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
10623 - Use the smartlist_add_asprintf() alias more consistently.
10624 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
10625 invalid value, rather than just -1.
10626 - Rename a handful of old identifiers, mostly related to crypto
10627 structures and crypto functions. By convention, our "create an
10628 object" functions are called "type_new()", our "free an object"
10629 functions are called "type_free()", and our types indicate that
10630 they are types only with a final "_t". But a handful of older
10631 types and functions broke these rules, with function names like
10632 "type_create" or "subsystem_op_type", or with type names like
10636 Changes in version 0.2.3.10-alpha - 2011-12-16
10637 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
10638 Tor's buffers code. Absolutely everybody should upgrade.
10640 The bug relied on an incorrect calculation when making data continuous
10641 in one of our IO buffers, if the first chunk of the buffer was
10642 misaligned by just the wrong amount. The miscalculation would allow an
10643 attacker to overflow a piece of heap-allocated memory. To mount this
10644 attack, the attacker would need to either open a SOCKS connection to
10645 Tor's SocksPort (usually restricted to localhost), or target a Tor
10646 instance configured to make its connections through a SOCKS proxy
10647 (which Tor does not do by default).
10649 Good security practice requires that all heap-overflow bugs should be
10650 presumed to be exploitable until proven otherwise, so we are treating
10651 this as a potential code execution attack. Please upgrade immediately!
10652 This bug does not affect bufferevents-based builds of Tor. Special
10653 thanks to "Vektor" for reporting this issue to us!
10655 This release also contains a few minor bugfixes for issues discovered
10659 - Fix a heap overflow bug that could occur when trying to pull
10660 data into the first chunk of a buffer, when that chunk had
10661 already had some data drained from it. Fixes CVE-2011-2778;
10662 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
10665 - If we can't attach streams to a rendezvous circuit when we
10666 finish connecting to a hidden service, clear the rendezvous
10667 circuit's stream-isolation state and try to attach streams
10668 again. Previously, we cleared rendezvous circuits' isolation
10669 state either too early (if they were freshly built) or not at all
10670 (if they had been built earlier and were cannibalized). Bugfix on
10671 0.2.3.3-alpha; fixes bug 4655.
10672 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
10673 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
10674 - Fix an assertion failure when a relay with accounting enabled
10675 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
10678 - Update to the December 6 2011 Maxmind GeoLite Country database.
10681 Changes in version 0.2.2.35 - 2011-12-16
10682 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
10683 buffers code. Absolutely everybody should upgrade.
10685 The bug relied on an incorrect calculation when making data continuous
10686 in one of our IO buffers, if the first chunk of the buffer was
10687 misaligned by just the wrong amount. The miscalculation would allow an
10688 attacker to overflow a piece of heap-allocated memory. To mount this
10689 attack, the attacker would need to either open a SOCKS connection to
10690 Tor's SocksPort (usually restricted to localhost), or target a Tor
10691 instance configured to make its connections through a SOCKS proxy
10692 (which Tor does not do by default).
10694 Good security practice requires that all heap-overflow bugs should be
10695 presumed to be exploitable until proven otherwise, so we are treating
10696 this as a potential code execution attack. Please upgrade immediately!
10697 This bug does not affect bufferevents-based builds of Tor. Special
10698 thanks to "Vektor" for reporting this issue to us!
10700 Tor 0.2.2.35 also fixes several bugs in previous versions, including
10701 crash bugs for unusual configurations, and a long-term bug that
10702 would prevent Tor from starting on Windows machines with draconian
10705 With this release, we remind everyone that 0.2.0.x has reached its
10706 formal end-of-life. Those Tor versions have many known flaws, and
10707 nobody should be using them. You should upgrade -- ideally to the
10708 0.2.2.x series. If you're using a Linux or BSD and its packages are
10709 obsolete, stop using those packages and upgrade anyway.
10711 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
10712 longer receive support after some time in early 2012.
10715 - Fix a heap overflow bug that could occur when trying to pull
10716 data into the first chunk of a buffer, when that chunk had
10717 already had some data drained from it. Fixes CVE-2011-2778;
10718 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
10719 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
10720 that it doesn't attempt to allocate a socketpair. This could cause
10721 some problems on Windows systems with overzealous firewalls. Fix for
10722 bug 4457; workaround for Libevent versions 2.0.1-alpha through
10724 - If we mark an OR connection for close based on a cell we process,
10725 don't process any further cells on it. We already avoid further
10726 reads on marked-for-close connections, but now we also discard the
10727 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
10728 which was the first version where we might mark a connection for
10729 close based on processing a cell on it.
10730 - Correctly sanity-check that we don't underflow on a memory
10731 allocation (and then assert) for hidden service introduction
10732 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
10733 bugfix on 0.2.1.5-alpha.
10734 - Fix a memory leak when we check whether a hidden service
10735 descriptor has any usable introduction points left. Fixes bug
10736 4424. Bugfix on 0.2.2.25-alpha.
10737 - Don't crash when we're running as a relay and don't have a GeoIP
10738 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
10739 we've had in the 0.2.3.x branch already.
10740 - When running as a client, do not print a misleading (and plain
10741 wrong) log message that we're collecting "directory request"
10742 statistics: clients don't collect statistics. Also don't create a
10743 useless (because empty) stats file in the stats/ directory. Fixes
10744 bug 4353; bugfix on 0.2.2.34.
10747 - Detect failure to initialize Libevent. This fix provides better
10748 detection for future instances of bug 4457.
10749 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
10750 function. This was eating up hideously large amounts of time on some
10751 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
10752 - Resolve an integer overflow bug in smartlist_ensure_capacity().
10753 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
10755 - Don't warn about unused log_mutex in log.c when building with
10756 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
10757 0.1.0.6-rc which introduced --disable-threads.
10758 - When configuring, starting, or stopping an NT service, stop
10759 immediately after the service configuration attempt has succeeded
10760 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
10761 - When sending a NETINFO cell, include the original address
10762 received for the other side, not its canonical address. Found
10763 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
10764 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
10765 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
10766 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
10767 occurred when a client tried to fetch a descriptor for a bridge
10768 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
10769 - Backport fixes for a pair of compilation warnings on Windows.
10770 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
10771 - If we had ever tried to call tor_addr_to_str on an address of
10772 unknown type, we would have done a strdup on an uninitialized
10773 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
10774 Reported by "troll_un".
10775 - Correctly detect and handle transient lookup failures from
10776 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
10777 Reported by "troll_un".
10778 - Fix null-pointer access that could occur if TLS allocation failed.
10779 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
10780 - Use tor_socket_t type for listener argument to accept(). Fixes bug
10781 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
10784 - Add two new config options for directory authorities:
10785 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
10786 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
10787 that is always sufficient to satisfy the bandwidth requirement for
10788 the Guard flag. Now it will be easier for researchers to simulate
10789 Tor networks with different values. Resolves ticket 4484.
10790 - When Tor ignores a hidden service specified in its configuration,
10791 include the hidden service's directory in the warning message.
10792 Previously, we would only tell the user that some hidden service
10793 was ignored. Bugfix on 0.0.6; fixes bug 4426.
10794 - Update to the December 6 2011 Maxmind GeoLite Country database.
10796 o Packaging changes:
10797 - Make it easier to automate expert package builds on Windows,
10798 by removing an absolute path from makensis.exe command.
10801 Changes in version 0.2.1.32 - 2011-12-16
10802 Tor 0.2.1.32 backports important security and privacy fixes for
10803 oldstable. This release is intended only for package maintainers and
10804 others who cannot use the 0.2.2 stable series. All others should be
10805 using Tor 0.2.2.x or newer.
10807 The Tor 0.2.1.x series will reach formal end-of-life some time in
10808 early 2012; we will stop releasing patches for it then.
10810 o Major bugfixes (also included in 0.2.2.x):
10811 - Correctly sanity-check that we don't underflow on a memory
10812 allocation (and then assert) for hidden service introduction
10813 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
10814 bugfix on 0.2.1.5-alpha.
10815 - Fix a heap overflow bug that could occur when trying to pull
10816 data into the first chunk of a buffer, when that chunk had
10817 already had some data drained from it. Fixes CVE-2011-2778;
10818 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
10821 - Update to the December 6 2011 Maxmind GeoLite Country database.
10824 Changes in version 0.2.3.9-alpha - 2011-12-08
10825 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
10826 a "DisableNetwork" security feature that bundles can use to avoid
10827 touching the network until bridges are configured, moves forward on
10828 the pluggable transport design, fixes a flaw in the hidden service
10829 design that unnecessarily prevented clients with wrong clocks from
10830 reaching hidden services, and fixes a wide variety of other issues.
10833 - Clients can now connect to private bridges over IPv6. Bridges
10834 still need at least one IPv4 address in order to connect to
10835 other relays. Note that we don't yet handle the case where the
10836 user has two bridge lines for the same bridge (one IPv4, one
10837 IPv6). Implements parts of proposal 186.
10838 - New "DisableNetwork" config option to prevent Tor from launching any
10839 connections or accepting any connections except on a control port.
10840 Bundles and controllers can set this option before letting Tor talk
10841 to the rest of the network, for example to prevent any connections
10842 to a non-bridge address. Packages like Orbot can also use this
10843 option to instruct Tor to save power when the network is off.
10844 - Clients and bridges can now be configured to use a separate
10845 "transport" proxy. This approach makes the censorship arms race
10846 easier by allowing bridges to use protocol obfuscation plugins. It
10847 implements the "managed proxy" part of proposal 180 (ticket 3472).
10848 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
10849 implementation. It makes AES_CTR about 7% faster than our old one
10850 (which was about 10% faster than the one OpenSSL used to provide).
10851 Resolves ticket 4526.
10852 - Add a "tor2web mode" for clients that want to connect to hidden
10853 services non-anonymously (and possibly more quickly). As a safety
10854 measure to try to keep users from turning this on without knowing
10855 what they are doing, tor2web mode must be explicitly enabled at
10856 compile time, and a copy of Tor compiled to run in tor2web mode
10857 cannot be used as a normal Tor client. Implements feature 2553.
10858 - Add experimental support for running on Windows with IOCP and no
10859 kernel-space socket buffers. This feature is controlled by a new
10860 "UserspaceIOCPBuffers" config option (off by default), which has
10861 no effect unless Tor has been built with support for bufferevents,
10862 is running on Windows, and has enabled IOCP. This may, in the long
10863 run, help solve or mitigate bug 98.
10864 - Use a more secure consensus parameter voting algorithm. Now at
10865 least three directory authorities or a majority of them must
10866 vote on a given parameter before it will be included in the
10867 consensus. Implements proposal 178.
10870 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
10871 They used to check that the timestamp was within 30 minutes
10872 of their system clock, so they could cap the size of their
10873 replay-detection cache, but that approach unnecessarily refused
10874 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
10875 the v3 intro-point protocol (the first one which sent a timestamp
10876 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
10877 - Only use the EVP interface when AES acceleration is enabled,
10878 to avoid a 5-7% performance regression. Resolves issue 4525;
10879 bugfix on 0.2.3.8-alpha.
10881 o Privacy/anonymity features (bridge detection):
10882 - Make bridge SSL certificates a bit more stealthy by using random
10883 serial numbers, in the same fashion as OpenSSL when generating
10884 self-signed certificates. Implements ticket 4584.
10885 - Introduce a new config option "DynamicDHGroups", enabled by
10886 default, which provides each bridge with a unique prime DH modulus
10887 to be used during SSL handshakes. This option attempts to help
10888 against censors who might use the Apache DH modulus as a static
10889 identifier for bridges. Addresses ticket 4548.
10891 o Minor features (new/different config options):
10892 - New configuration option "DisableDebuggerAttachment" (on by default)
10893 to prevent basic debugging attachment attempts by other processes.
10894 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
10895 - Allow MapAddress directives to specify matches against super-domains,
10896 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
10897 Implements issue 933.
10898 - Slightly change behavior of "list" options (that is, config
10899 options that can appear more than once) when they appear both in
10900 torrc and on the command line. Previously, the command-line options
10901 would be appended to the ones from torrc. Now, the command-line
10902 options override the torrc options entirely. This new behavior
10903 allows the user to override list options (like exit policies and
10904 ports to listen on) from the command line, rather than simply
10905 appending to the list.
10906 - You can get the old (appending) command-line behavior for "list"
10907 options by prefixing the option name with a "+".
10908 - You can remove all the values for a "list" option from the command
10909 line without adding any new ones by prefixing the option name
10911 - Add experimental support for a "defaults" torrc file to be parsed
10912 before the regular torrc. Torrc options override the defaults file's
10913 options in the same way that the command line overrides the torrc.
10914 The SAVECONF controller command saves only those options which
10915 differ between the current configuration and the defaults file. HUP
10916 reloads both files. (Note: This is an experimental feature; its
10917 behavior will probably be refined in future 0.2.3.x-alpha versions
10918 to better meet packagers' needs.) Implements task 4552.
10921 - Try to make the introductory warning message that Tor prints on
10922 startup more useful for actually finding help and information.
10923 Resolves ticket 2474.
10924 - Running "make version" now displays the version of Tor that
10925 we're about to build. Idea from katmagic; resolves issue 4400.
10926 - Expire old or over-used hidden service introduction points.
10927 Required by fix for bug 3460.
10928 - Move the replay-detection cache for the RSA-encrypted parts of
10929 INTRODUCE2 cells to the introduction point data structures.
10930 Previously, we would use one replay-detection cache per hidden
10931 service. Required by fix for bug 3460.
10932 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
10933 public key replay-detection cache from 60 minutes to 5 minutes. This
10934 replay-detection cache is now used only to detect multiple
10935 INTRODUCE2 cells specifying the same rendezvous point, so we can
10936 avoid launching multiple simultaneous attempts to connect to it.
10938 o Minor bugfixes (on Tor 0.2.2.x and earlier):
10939 - Resolve an integer overflow bug in smartlist_ensure_capacity().
10940 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
10942 - Fix a minor formatting issue in one of tor-gencert's error messages.
10944 - Prevent a false positive from the check-spaces script, by disabling
10945 the "whitespace between function name and (" check for functions
10947 - Fix a log message suggesting that people contact a non-existent
10948 email address. Fixes bug 3448.
10949 - Fix null-pointer access that could occur if TLS allocation failed.
10950 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
10951 - Report a real bootstrap problem to the controller on router
10952 identity mismatch. Previously we just said "foo", which probably
10953 made a lot of sense at the time. Fixes bug 4169; bugfix on
10955 - If we had ever tried to call tor_addr_to_str() on an address of
10956 unknown type, we would have done a strdup() on an uninitialized
10957 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
10958 Reported by "troll_un".
10959 - Correctly detect and handle transient lookup failures from
10960 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
10961 Reported by "troll_un".
10962 - Use tor_socket_t type for listener argument to accept(). Fixes bug
10963 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
10964 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
10965 bug 4532; found by "troll_un".
10967 o Minor bugfixes (on Tor 0.2.3.x):
10968 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
10970 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
10971 circuit for use as a hidden service client's rendezvous point.
10972 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
10973 with help from wanoskarnet.
10974 - Restore behavior of overriding SocksPort, ORPort, and similar
10975 options from the command line. Bugfix on 0.2.3.3-alpha.
10978 - Properly handle the case where the build-tree is not the same
10979 as the source tree when generating src/common/common_sha1.i,
10980 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
10981 bugfix on 0.2.0.1-alpha.
10983 o Code simplifications, cleanups, and refactorings:
10984 - Remove the pure attribute from all functions that used it
10985 previously. In many cases we assigned it incorrectly, because the
10986 functions might assert or call impure functions, and we don't have
10987 evidence that keeping the pure attribute is worthwhile. Implements
10988 changes suggested in ticket 4421.
10989 - Remove some dead code spotted by coverity. Fixes cid 432.
10990 Bugfix on 0.2.3.1-alpha, closes bug 4637.
10993 Changes in version 0.2.3.8-alpha - 2011-11-22
10994 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
10995 socketpair-related bug that has been bothering Windows users. It adds
10996 support to serve microdescriptors to controllers, so Vidalia's network
10997 map can resume listing relays (once Vidalia implements its side),
10998 and adds better support for hardware AES acceleration. Finally, it
10999 starts the process of adjusting the bandwidth cutoff for getting the
11000 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
11001 that tiny relays harm performance more than they help network capacity.
11004 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
11005 that it doesn't attempt to allocate a socketpair. This could cause
11006 some problems on Windows systems with overzealous firewalls. Fix for
11007 bug 4457; workaround for Libevent versions 2.0.1-alpha through
11009 - Correctly sanity-check that we don't underflow on a memory
11010 allocation (and then assert) for hidden service introduction
11011 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
11012 bugfix on 0.2.1.5-alpha.
11013 - Remove the artificially low cutoff of 20KB to guarantee the Fast
11014 flag. In the past few years the average relay speed has picked
11015 up, and while the "top 7/8 of the network get the Fast flag" and
11016 "all relays with 20KB or more of capacity get the Fast flag" rules
11017 used to have the same result, now the top 7/8 of the network has
11018 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
11019 - Fix a rare assertion failure when checking whether a v0 hidden
11020 service descriptor has any usable introduction points left, and
11021 we don't have enough information to build a circuit to the first
11022 intro point named in the descriptor. The HS client code in
11023 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
11024 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
11025 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
11026 - Make bridge authorities not crash when they are asked for their own
11027 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
11028 - When running as a client, do not print a misleading (and plain
11029 wrong) log message that we're collecting "directory request"
11030 statistics: clients don't collect statistics. Also don't create a
11031 useless (because empty) stats file in the stats/ directory. Fixes
11032 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
11035 - Allow Tor controllers like Vidalia to obtain the microdescriptor
11036 for a relay by identity digest or nickname. Previously,
11037 microdescriptors were only available by their own digests, so a
11038 controller would have to ask for and parse the whole microdescriptor
11039 consensus in order to look up a single relay's microdesc. Fixes
11040 bug 3832; bugfix on 0.2.3.1-alpha.
11041 - Use OpenSSL's EVP interface for AES encryption, so that all AES
11042 operations can use hardware acceleration (if present). Resolves
11045 o Minor bugfixes (on 0.2.2.x and earlier):
11046 - Detect failure to initialize Libevent. This fix provides better
11047 detection for future instances of bug 4457.
11048 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
11049 function. This was eating up hideously large amounts of time on some
11050 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
11051 - Don't warn about unused log_mutex in log.c when building with
11052 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
11053 0.1.0.6-rc which introduced --disable-threads.
11054 - Allow manual 'authenticate' commands to the controller interface
11055 from netcat (nc) as well as telnet. We were rejecting them because
11056 they didn't come with the expected whitespace at the end of the
11057 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
11058 - Fix some (not actually triggerable) buffer size checks in usage of
11059 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
11061 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
11062 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
11063 - When configuring, starting, or stopping an NT service, stop
11064 immediately after the service configuration attempt has succeeded
11065 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
11066 - When sending a NETINFO cell, include the original address
11067 received for the other side, not its canonical address. Found
11068 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
11069 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
11070 can pick them up when the tests aren't disabled. Bugfix on
11071 0.2.2.4-alpha which introduced tinytest.
11072 - Fix a memory leak when we check whether a hidden service
11073 descriptor has any usable introduction points left. Fixes bug
11074 4424. Bugfix on 0.2.2.25-alpha.
11075 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
11076 occurred when a client tried to fetch a descriptor for a bridge
11077 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
11079 o Minor bugfixes (on 0.2.3.x):
11080 - Make util unit tests build correctly with MSVC. Bugfix on
11081 0.2.3.3-alpha. Patch by Gisle Vanem.
11082 - Successfully detect AUTH_CHALLENGE cells with no recognized
11083 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
11084 Found by frosty_un.
11085 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
11086 it should still send a NETINFO cell to allow the connection to
11087 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
11089 - Log less loudly when we get an invalid authentication certificate
11090 from a source other than a directory authority: it's not unusual
11091 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
11093 - Tolerate servers with more clock skew in their authentication
11094 certificates than previously. Fixes bug 4371; bugfix on
11096 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
11097 on 0.2.3.4-alpha and 0.2.3.6-alpha.
11100 - Add two new config options for directory authorities:
11101 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
11102 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
11103 that is always sufficient to satisfy the bandwidth requirement for
11104 the Guard flag. Now it will be easier for researchers to simulate
11105 Tor networks with different values. Resolves ticket 4484.
11106 - When Tor ignores a hidden service specified in its configuration,
11107 include the hidden service's directory in the warning message.
11108 Previously, we would only tell the user that some hidden service
11109 was ignored. Bugfix on 0.0.6; fixes bug 4426.
11110 - When we fail to initialize Libevent, retry with IOCP disabled so we
11111 don't need to turn on multi-threading support in Libevent, which in
11112 turn requires a working socketpair(). This is a workaround for bug
11113 4457, which affects Libevent versions from 2.0.1-alpha through
11115 - Detect when we try to build on a platform that doesn't define
11116 AF_UNSPEC to 0. We don't work there, so refuse to compile.
11117 - Update to the November 1 2011 Maxmind GeoLite Country database.
11119 o Packaging changes:
11120 - Make it easier to automate expert package builds on Windows,
11121 by removing an absolute path from makensis.exe command.
11123 o Code simplifications and refactoring:
11124 - Remove some redundant #include directives throughout the code.
11125 Patch from Andrea Gelmini.
11126 - Unconditionally use OpenSSL's AES implementation instead of our
11127 old built-in one. OpenSSL's AES has been better for a while, and
11128 relatively few servers should still be on any version of OpenSSL
11129 that doesn't have good optimized assembly AES.
11130 - Use the name "CERTS" consistently to refer to the new cell type;
11131 we were calling it CERT in some places and CERTS in others.
11134 - Numerous new unit tests for functions in util.c and address.c by
11136 - The long-disabled benchmark tests are now split into their own
11137 ./src/test/bench binary.
11138 - The benchmark tests can now use more accurate timers than
11139 gettimeofday() when such timers are available.
11142 Changes in version 0.2.3.7-alpha - 2011-10-30
11143 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
11144 the new v3 handshake. It also resolves yet another bridge address
11148 - If we mark an OR connection for close based on a cell we process,
11149 don't process any further cells on it. We already avoid further
11150 reads on marked-for-close connections, but now we also discard the
11151 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
11152 which was the first version where we might mark a connection for
11153 close based on processing a cell on it.
11154 - Fix a double-free bug that would occur when we received an invalid
11155 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
11156 bugfix on 0.2.3.6-alpha.
11157 - Bridges no longer include their address in NETINFO cells on outgoing
11158 OR connections, to allow them to blend in better with clients.
11159 Removes another avenue for enumerating bridges. Reported by
11160 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
11161 cells were introduced.
11164 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
11165 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
11168 Changes in version 0.2.3.6-alpha - 2011-10-26
11169 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
11170 anonymity vulnerability where an attacker can deanonymize Tor
11171 users. Everybody should upgrade.
11173 This release also features support for a new v3 connection handshake
11174 protocol, and fixes to make hidden service connections more robust.
11177 - Implement a new handshake protocol (v3) for authenticating Tors to
11178 each other over TLS. It should be more resistant to fingerprinting
11179 than previous protocols, and should require less TLS hacking for
11180 future Tor implementations. Implements proposal 176.
11181 - Allow variable-length padding cells to disguise the length of
11182 Tor's TLS records. Implements part of proposal 184.
11184 o Privacy/anonymity fixes (clients):
11185 - Clients and bridges no longer send TLS certificate chains on
11186 outgoing OR connections. Previously, each client or bridge would
11187 use the same cert chain for all outgoing OR connections until
11188 its IP address changes, which allowed any relay that the client
11189 or bridge contacted to determine which entry guards it is using.
11190 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
11191 - If a relay receives a CREATE_FAST cell on a TLS connection, it
11192 no longer considers that connection as suitable for satisfying a
11193 circuit EXTEND request. Now relays can protect clients from the
11194 CVE-2011-2768 issue even if the clients haven't upgraded yet.
11195 - Directory authorities no longer assign the Guard flag to relays
11196 that haven't upgraded to the above "refuse EXTEND requests
11197 to client connections" fix. Now directory authorities can
11198 protect clients from the CVE-2011-2768 issue even if neither
11199 the clients nor the relays have upgraded yet. There's a new
11200 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
11201 to let us transition smoothly, else tomorrow there would be no
11204 o Major bugfixes (hidden services):
11205 - Improve hidden service robustness: when an attempt to connect to
11206 a hidden service ends, be willing to refetch its hidden service
11207 descriptors from each of the HSDir relays responsible for them
11208 immediately. Previously, we would not consider refetching the
11209 service's descriptors from each HSDir for 15 minutes after the last
11210 fetch, which was inconvenient if the hidden service was not running
11211 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
11212 - When one of a hidden service's introduction points appears to be
11213 unreachable, stop trying it. Previously, we would keep trying
11214 to build circuits to the introduction point until we lost the
11215 descriptor, usually because the user gave up and restarted Tor.
11216 Partly fixes bug 3825.
11217 - Don't launch a useless circuit after failing to use one of a
11218 hidden service's introduction points. Previously, we would
11219 launch a new introduction circuit, but not set the hidden service
11220 which that circuit was intended to connect to, so it would never
11221 actually be used. A different piece of code would then create a
11222 new introduction circuit correctly. Bug reported by katmagic and
11223 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
11225 o Major bugfixes (other):
11226 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
11227 that they initiated. Relays could distinguish incoming bridge
11228 connections from client connections, creating another avenue for
11229 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
11230 Found by "frosty_un".
11231 - Don't update the AccountingSoftLimitHitAt state file entry whenever
11232 tor gets started. This prevents a wrong average bandwidth
11233 estimate, which would cause relays to always start a new accounting
11234 interval at the earliest possible moment. Fixes bug 2003; bugfix
11235 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
11236 immensely in tracking this bug down.
11237 - Fix a crash bug when changing node restrictions while a DNS lookup
11238 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
11241 o Minor bugfixes (on 0.2.2.x and earlier):
11242 - When a hidden service turns an extra service-side introduction
11243 circuit into a general-purpose circuit, free the rend_data and
11244 intro_key fields first, so we won't leak memory if the circuit
11245 is cannibalized for use as another service-side introduction
11246 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
11247 - Rephrase the log message emitted if the TestSocks check is
11248 successful. Patch from Fabian Keil; fixes bug 4094.
11249 - Bridges now skip DNS self-tests, to act a little more stealthily.
11250 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
11251 bridges. Patch by "warms0x".
11252 - Remove a confusing dollar sign from the example fingerprint in the
11253 man page, and also make the example fingerprint a valid one. Fixes
11254 bug 4309; bugfix on 0.2.1.3-alpha.
11255 - Fix internal bug-checking logic that was supposed to catch
11256 failures in digest generation so that it will fail more robustly
11257 if we ask for a nonexistent algorithm. Found by Coverity Scan.
11258 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
11259 - Report any failure in init_keys() calls launched because our
11260 IP address has changed. Spotted by Coverity Scan. Bugfix on
11261 0.1.1.4-alpha; fixes CID 484.
11263 o Minor bugfixes (on 0.2.3.x):
11264 - Fix a bug in configure.in that kept it from building a configure
11265 script with autoconf versions earlier than 2.61. Fixes bug 2430;
11266 bugfix on 0.2.3.1-alpha.
11267 - Don't warn users that they are exposing a client port to the
11268 Internet if they have specified an RFC1918 address. Previously,
11269 we would warn if the user had specified any non-loopback
11270 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
11271 - Fix memory leaks in the failing cases of the new SocksPort and
11272 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
11273 fixes coverity CIDs 485, 486, and 487.
11276 - When a hidden service's introduction point times out, consider
11277 trying it again during the next attempt to connect to the
11278 HS. Previously, we would not try it again unless a newly fetched
11279 descriptor contained it. Required by fixes for bugs 1297 and 3825.
11280 - The next version of Windows will be called Windows 8, and it has
11281 a major version of 6, minor version of 2. Correctly identify that
11282 version instead of calling it "Very recent version". Resolves
11283 ticket 4153; reported by funkstar.
11284 - The Bridge Authority now writes statistics on how many bridge
11285 descriptors it gave out in total, and how many unique descriptors
11286 it gave out. It also lists how often the most and least commonly
11287 fetched descriptors were given out, as well as the median and
11288 25th/75th percentile. Implements tickets 4200 and 4294.
11289 - Update to the October 4 2011 Maxmind GeoLite Country database.
11291 o Code simplifications and refactoring:
11292 - Remove some old code to remember statistics about which descriptors
11293 we've served as a directory mirror. The feature wasn't used and
11294 is outdated now that microdescriptors are around.
11295 - Rename Tor functions that turn strings into addresses, so that
11296 "parse" indicates that no hostname resolution occurs, and
11297 "lookup" indicates that hostname resolution may occur. This
11298 should help prevent mistakes in the future. Fixes bug 3512.
11301 Changes in version 0.2.2.34 - 2011-10-26
11302 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
11303 can deanonymize Tor users. Everybody should upgrade.
11305 The attack relies on four components: 1) Clients reuse their TLS cert
11306 when talking to different relays, so relays can recognize a user by
11307 the identity key in her cert. 2) An attacker who knows the client's
11308 identity key can probe each guard relay to see if that identity key
11309 is connected to that guard relay right now. 3) A variety of active
11310 attacks in the literature (starting from "Low-Cost Traffic Analysis
11311 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
11312 discover the guard relays that a Tor user visiting the website is using.
11313 4) Clients typically pick three guards at random, so the set of guards
11314 for a given user could well be a unique fingerprint for her. This
11315 release fixes components #1 and #2, which is enough to block the attack;
11316 the other two remain as open research problems. Special thanks to
11317 "frosty_un" for reporting the issue to us!
11319 Clients should upgrade so they are no longer recognizable by the TLS
11320 certs they present. Relays should upgrade so they no longer allow a
11321 remote attacker to probe them to test whether unpatched clients are
11322 currently connected to them.
11324 This release also fixes several vulnerabilities that allow an attacker
11325 to enumerate bridge relays. Some bridge enumeration attacks still
11326 remain; see for example proposal 188.
11328 o Privacy/anonymity fixes (clients):
11329 - Clients and bridges no longer send TLS certificate chains on
11330 outgoing OR connections. Previously, each client or bridge would
11331 use the same cert chain for all outgoing OR connections until
11332 its IP address changes, which allowed any relay that the client
11333 or bridge contacted to determine which entry guards it is using.
11334 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
11335 - If a relay receives a CREATE_FAST cell on a TLS connection, it
11336 no longer considers that connection as suitable for satisfying a
11337 circuit EXTEND request. Now relays can protect clients from the
11338 CVE-2011-2768 issue even if the clients haven't upgraded yet.
11339 - Directory authorities no longer assign the Guard flag to relays
11340 that haven't upgraded to the above "refuse EXTEND requests
11341 to client connections" fix. Now directory authorities can
11342 protect clients from the CVE-2011-2768 issue even if neither
11343 the clients nor the relays have upgraded yet. There's a new
11344 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
11345 to let us transition smoothly, else tomorrow there would be no
11348 o Privacy/anonymity fixes (bridge enumeration):
11349 - Bridge relays now do their directory fetches inside Tor TLS
11350 connections, like all the other clients do, rather than connecting
11351 directly to the DirPort like public relays do. Removes another
11352 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
11353 - Bridges relays now build circuits for themselves in a more similar
11354 way to how clients build them. Removes another avenue for
11355 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
11356 when bridges were introduced.
11357 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
11358 that they initiated. Relays could distinguish incoming bridge
11359 connections from client connections, creating another avenue for
11360 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
11361 Found by "frosty_un".
11364 - Fix a crash bug when changing node restrictions while a DNS lookup
11365 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
11367 - Don't launch a useless circuit after failing to use one of a
11368 hidden service's introduction points. Previously, we would
11369 launch a new introduction circuit, but not set the hidden service
11370 which that circuit was intended to connect to, so it would never
11371 actually be used. A different piece of code would then create a
11372 new introduction circuit correctly. Bug reported by katmagic and
11373 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
11376 - Change an integer overflow check in the OpenBSD_Malloc code so
11377 that GCC is less likely to eliminate it as impossible. Patch
11378 from Mansour Moufid. Fixes bug 4059.
11379 - When a hidden service turns an extra service-side introduction
11380 circuit into a general-purpose circuit, free the rend_data and
11381 intro_key fields first, so we won't leak memory if the circuit
11382 is cannibalized for use as another service-side introduction
11383 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
11384 - Bridges now skip DNS self-tests, to act a little more stealthily.
11385 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
11386 bridges. Patch by "warms0x".
11387 - Fix internal bug-checking logic that was supposed to catch
11388 failures in digest generation so that it will fail more robustly
11389 if we ask for a nonexistent algorithm. Found by Coverity Scan.
11390 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
11391 - Report any failure in init_keys() calls launched because our
11392 IP address has changed. Spotted by Coverity Scan. Bugfix on
11393 0.1.1.4-alpha; fixes CID 484.
11395 o Minor bugfixes (log messages and documentation):
11396 - Remove a confusing dollar sign from the example fingerprint in the
11397 man page, and also make the example fingerprint a valid one. Fixes
11398 bug 4309; bugfix on 0.2.1.3-alpha.
11399 - The next version of Windows will be called Windows 8, and it has
11400 a major version of 6, minor version of 2. Correctly identify that
11401 version instead of calling it "Very recent version". Resolves
11402 ticket 4153; reported by funkstar.
11403 - Downgrade log messages about circuit timeout calibration from
11404 "notice" to "info": they don't require or suggest any human
11405 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
11406 bugfix on 0.2.2.14-alpha.
11409 - Turn on directory request statistics by default and include them in
11410 extra-info descriptors. Don't break if we have no GeoIP database.
11411 Backported from 0.2.3.1-alpha; implements ticket 3951.
11412 - Update to the October 4 2011 Maxmind GeoLite Country database.
11415 Changes in version 0.2.1.31 - 2011-10-26
11416 Tor 0.2.1.31 backports important security and privacy fixes for
11417 oldstable. This release is intended only for package maintainers and
11418 others who cannot use the 0.2.2 stable series. All others should be
11419 using Tor 0.2.2.x or newer.
11421 o Security fixes (also included in 0.2.2.x):
11422 - Replace all potentially sensitive memory comparison operations
11423 with versions whose runtime does not depend on the data being
11424 compared. This will help resist a class of attacks where an
11425 adversary can use variations in timing information to learn
11426 sensitive data. Fix for one case of bug 3122. (Safe memcmp
11427 implementation by Robert Ransom based partially on code by DJB.)
11428 - Fix an assert in parsing router descriptors containing IPv6
11429 addresses. This one took down the directory authorities when
11430 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
11432 o Privacy/anonymity fixes (also included in 0.2.2.x):
11433 - Clients and bridges no longer send TLS certificate chains on
11434 outgoing OR connections. Previously, each client or bridge would
11435 use the same cert chain for all outgoing OR connections until
11436 its IP address changes, which allowed any relay that the client
11437 or bridge contacted to determine which entry guards it is using.
11438 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
11439 - If a relay receives a CREATE_FAST cell on a TLS connection, it
11440 no longer considers that connection as suitable for satisfying a
11441 circuit EXTEND request. Now relays can protect clients from the
11442 CVE-2011-2768 issue even if the clients haven't upgraded yet.
11443 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
11444 that they initiated. Relays could distinguish incoming bridge
11445 connections from client connections, creating another avenue for
11446 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
11447 Found by "frosty_un".
11448 - When receiving a hidden service descriptor, check that it is for
11449 the hidden service we wanted. Previously, Tor would store any
11450 hidden service descriptors that a directory gave it, whether it
11451 wanted them or not. This wouldn't have let an attacker impersonate
11452 a hidden service, but it did let directories pre-seed a client
11453 with descriptors that it didn't want. Bugfix on 0.0.6.
11454 - Avoid linkability based on cached hidden service descriptors: forget
11455 all hidden service descriptors cached as a client when processing a
11456 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
11457 - Make the bridge directory authority refuse to answer directory
11458 requests for "all" descriptors. It used to include bridge
11459 descriptors in its answer, which was a major information leak.
11460 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
11461 - Don't attach new streams to old rendezvous circuits after SIGNAL
11462 NEWNYM. Previously, we would keep using an existing rendezvous
11463 circuit if it remained open (i.e. if it were kept open by a
11464 long-lived stream, or if a new stream were attached to it before
11465 Tor could notice that it was old and no longer in use). Bugfix on
11466 0.1.1.15-rc; fixes bug 3375.
11468 o Minor bugfixes (also included in 0.2.2.x):
11469 - When we restart our relay, we might get a successful connection
11470 from the outside before we've started our reachability tests,
11471 triggering a warning: "ORPort found reachable, but I have no
11472 routerinfo yet. Failing to inform controller of success." This
11473 bug was harmless unless Tor is running under a controller
11474 like Vidalia, in which case the controller would never get a
11475 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
11477 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
11478 enabled. Fixes bug 1526.
11479 - Remove undocumented option "-F" from tor-resolve: it hasn't done
11480 anything since 0.2.1.16-rc.
11481 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
11482 None of the cases where we did this before were wrong, but by making
11483 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
11484 - Fix a rare crash bug that could occur when a client was configured
11485 with a large number of bridges. Fixes bug 2629; bugfix on
11486 0.2.1.2-alpha. Bugfix by trac user "shitlei".
11487 - Correct the warning displayed when a rendezvous descriptor exceeds
11488 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
11490 - Fix an uncommon assertion failure when running with DNSPort under
11491 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
11492 - When warning about missing zlib development packages during compile,
11493 give the correct package names. Bugfix on 0.2.0.1-alpha.
11494 - Require that introduction point keys and onion keys have public
11495 exponent 65537. Bugfix on 0.2.0.10-alpha.
11496 - Do not crash when our configuration file becomes unreadable, for
11497 example due to a permissions change, between when we start up
11498 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
11500 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
11502 - Always NUL-terminate the sun_path field of a sockaddr_un before
11503 passing it to the kernel. (Not a security issue: kernels are
11504 smart enough to reject bad sockaddr_uns.) Found by Coverity;
11505 CID #428. Bugfix on Tor 0.2.0.3-alpha.
11506 - Don't stack-allocate the list of supplementary GIDs when we're
11507 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
11508 could take up to 256K, which is way too much stack. Found by
11509 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
11511 o Minor bugfixes (only in 0.2.1.x):
11512 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
11513 rely on them. Bugfix on 0.2.1.30.
11514 - Use git revisions instead of svn revisions when generating our
11515 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
11517 o Minor features (also included in 0.2.2.x):
11518 - Adjust the expiration time on our SSL session certificates to
11519 better match SSL certs seen in the wild. Resolves ticket 4014.
11520 - Allow nameservers with IPv6 address. Resolves bug 2574.
11521 - Update to the October 4 2011 Maxmind GeoLite Country database.
11524 Changes in version 0.2.3.5-alpha - 2011-09-28
11525 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
11526 bridge relays; fixes an assertion error that many users started hitting
11527 today; and adds the ability to refill token buckets more often than
11528 once per second, allowing significant performance improvements.
11531 - Bridge relays now do their directory fetches inside Tor TLS
11532 connections, like all the other clients do, rather than connecting
11533 directly to the DirPort like public relays do. Removes another
11534 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
11535 - Bridges relays now build circuits for themselves in a more similar
11536 way to how clients build them. Removes another avenue for
11537 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
11538 when bridges were introduced.
11541 - Fix an "Assertion md->held_by_node == 1 failed" error that could
11542 occur when the same microdescriptor was referenced by two node_t
11543 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
11545 o Major features (networking):
11546 - Add a new TokenBucketRefillInterval option to refill token buckets
11547 more frequently than once per second. This should improve network
11548 performance, alleviate queueing problems, and make traffic less
11549 bursty. Implements proposal 183; closes ticket 3630. Design by
11550 Florian Tschorsch and Björn Scheuermann; implementation by
11554 - Change an integer overflow check in the OpenBSD_Malloc code so
11555 that GCC is less likely to eliminate it as impossible. Patch
11556 from Mansour Moufid. Fixes bug 4059.
11558 o Minor bugfixes (usability):
11559 - Downgrade log messages about circuit timeout calibration from
11560 "notice" to "info": they don't require or suggest any human
11561 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
11562 bugfix on 0.2.2.14-alpha.
11564 o Minor features (diagnostics):
11565 - When the system call to create a listener socket fails, log the
11566 error message explaining why. This may help diagnose bug 4027.
11569 Changes in version 0.2.3.4-alpha - 2011-09-13
11570 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
11571 tweak to Tor's TLS handshake that makes relays and bridges that run
11572 this new version reachable from Iran again. It also fixes a few new
11573 bugs in 0.2.3.x, and teaches relays to recognize when they're not
11574 listed in the network consensus and republish.
11576 o Major bugfixes (also part of 0.2.2.33):
11577 - Avoid an assertion failure when reloading a configuration with
11578 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
11579 3923; bugfix on 0.2.2.25-alpha.
11581 o Minor features (security, also part of 0.2.2.33):
11582 - Check for replays of the public-key encrypted portion of an
11583 INTRODUCE1 cell, in addition to the current check for replays of
11584 the g^x value. This prevents a possible class of active attacks
11585 by an attacker who controls both an introduction point and a
11586 rendezvous point, and who uses the malleability of AES-CTR to
11587 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
11588 that these attacks are infeasible (requiring the attacker to send
11589 on the order of zettabytes of altered cells in a short interval),
11590 but we'd rather block them off in case there are any classes of
11591 this attack that we missed. Reported by Willem Pinckaers.
11593 o Minor features (also part of 0.2.2.33):
11594 - Adjust the expiration time on our SSL session certificates to
11595 better match SSL certs seen in the wild. Resolves ticket 4014.
11596 - Change the default required uptime for a relay to be accepted as
11597 a HSDir (hidden service directory) from 24 hours to 25 hours.
11598 Improves on 0.2.0.10-alpha; resolves ticket 2649.
11599 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
11600 authorities to abstain from voting on assignment of the HSDir
11601 consensus flag. Related to bug 2649.
11602 - Update to the September 6 2011 Maxmind GeoLite Country database.
11604 o Minor bugfixes (also part of 0.2.2.33):
11605 - Demote the 'replay detected' log message emitted when a hidden
11606 service receives the same Diffie-Hellman public key in two different
11607 INTRODUCE2 cells to info level. A normal Tor client can cause that
11608 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
11609 fixes part of bug 2442.
11610 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
11611 level. There is nothing that a hidden service's operator can do
11612 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
11614 - Clarify a log message specifying the characters permitted in
11615 HiddenServiceAuthorizeClient client names. Previously, the log
11616 message said that "[A-Za-z0-9+-_]" were permitted; that could have
11617 given the impression that every ASCII character between "+" and "_"
11618 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
11620 o Build fixes (also part of 0.2.2.33):
11621 - Clean up some code issues that prevented Tor from building on older
11622 BSDs. Fixes bug 3894; reported by "grarpamp".
11623 - Search for a platform-specific version of "ar" when cross-compiling.
11624 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
11627 - Fix a bug where the SocksPort option (for example) would get
11628 ignored and replaced by the default if a SocksListenAddress
11629 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
11633 - Relays now try regenerating and uploading their descriptor more
11634 frequently if they are not listed in the consensus, or if the
11635 version of their descriptor listed in the consensus is too
11636 old. This fix should prevent situations where a server declines
11637 to re-publish itself because it has done so too recently, even
11638 though the authorities decided not to list its recent-enough
11639 descriptor. Fix for bug 3327.
11642 - Relays now include a reason for regenerating their descriptors
11643 in an HTTP header when uploading to the authorities. This will
11644 make it easier to debug descriptor-upload issues in the future.
11645 - When starting as root and then changing our UID via the User
11646 control option, and we have a ControlSocket configured, make sure
11647 that the ControlSocket is owned by the same account that Tor will
11648 run under. Implements ticket 3421; fix by Jérémy Bobbio.
11651 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
11652 utility function used in the control-port code). This shouldn't
11653 ever happen unless Tor is completely out of memory, but if it did
11654 happen and Tor somehow recovered from it, Tor could have sent a log
11655 message to a control port in the middle of a reply to a controller
11656 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
11657 - Make 'FetchUselessDescriptors' cause all descriptor types and
11658 all consensus types (including microdescriptors) to get fetched.
11659 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
11661 o Code refactoring:
11662 - Make a new "entry connection" struct as an internal subtype of "edge
11663 connection", to simplify the code and make exit connections smaller.
11666 Changes in version 0.2.2.33 - 2011-09-13
11667 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
11668 TLS handshake that makes relays and bridges that run this new version
11669 reachable from Iran again.
11672 - Avoid an assertion failure when reloading a configuration with
11673 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
11674 3923; bugfix on 0.2.2.25-alpha.
11676 o Minor features (security):
11677 - Check for replays of the public-key encrypted portion of an
11678 INTRODUCE1 cell, in addition to the current check for replays of
11679 the g^x value. This prevents a possible class of active attacks
11680 by an attacker who controls both an introduction point and a
11681 rendezvous point, and who uses the malleability of AES-CTR to
11682 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
11683 that these attacks are infeasible (requiring the attacker to send
11684 on the order of zettabytes of altered cells in a short interval),
11685 but we'd rather block them off in case there are any classes of
11686 this attack that we missed. Reported by Willem Pinckaers.
11689 - Adjust the expiration time on our SSL session certificates to
11690 better match SSL certs seen in the wild. Resolves ticket 4014.
11691 - Change the default required uptime for a relay to be accepted as
11692 a HSDir (hidden service directory) from 24 hours to 25 hours.
11693 Improves on 0.2.0.10-alpha; resolves ticket 2649.
11694 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
11695 authorities to abstain from voting on assignment of the HSDir
11696 consensus flag. Related to bug 2649.
11697 - Update to the September 6 2011 Maxmind GeoLite Country database.
11699 o Minor bugfixes (documentation and log messages):
11700 - Correct the man page to explain that HashedControlPassword and
11701 CookieAuthentication can both be set, in which case either method
11702 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
11703 when we decided to allow these config options to both be set. Issue
11704 raised by bug 3898.
11705 - Demote the 'replay detected' log message emitted when a hidden
11706 service receives the same Diffie-Hellman public key in two different
11707 INTRODUCE2 cells to info level. A normal Tor client can cause that
11708 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
11709 fixes part of bug 2442.
11710 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
11711 level. There is nothing that a hidden service's operator can do
11712 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
11714 - Clarify a log message specifying the characters permitted in
11715 HiddenServiceAuthorizeClient client names. Previously, the log
11716 message said that "[A-Za-z0-9+-_]" were permitted; that could have
11717 given the impression that every ASCII character between "+" and "_"
11718 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
11721 - Provide a substitute implementation of lround() for MSVC, which
11722 apparently lacks it. Patch from Gisle Vanem.
11723 - Clean up some code issues that prevented Tor from building on older
11724 BSDs. Fixes bug 3894; reported by "grarpamp".
11725 - Search for a platform-specific version of "ar" when cross-compiling.
11726 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
11729 Changes in version 0.2.3.3-alpha - 2011-09-01
11730 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
11731 security, and provides client-side support for the microdescriptor
11732 and optimistic data features introduced earlier in the 0.2.3.x
11733 series. It also includes numerous critical bugfixes in the (optional)
11734 bufferevent-based networking backend.
11736 o Major features (stream isolation):
11737 - You can now configure Tor so that streams from different
11738 applications are isolated on different circuits, to prevent an
11739 attacker who sees your streams as they leave an exit node from
11740 linking your sessions to one another. To do this, choose some way
11741 to distinguish the applications: have them connect to different
11742 SocksPorts, or have one of them use SOCKS4 while the other uses
11743 SOCKS5, or have them pass different authentication strings to the
11744 SOCKS proxy. Then, use the new SocksPort syntax to configure the
11745 degree of isolation you need. This implements Proposal 171.
11746 - There's a new syntax for specifying multiple client ports (such as
11747 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
11748 multiple *Port entries with full addr:port syntax on each.
11749 The old *ListenAddress format is still supported, but you can't
11750 mix it with the new *Port syntax.
11752 o Major features (other):
11753 - Enable microdescriptor fetching by default for clients. This allows
11754 clients to download a much smaller amount of directory information.
11755 To disable it (and go back to the old-style consensus and
11756 descriptors), set "UseMicrodescriptors 0" in your torrc file.
11757 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
11758 "PortForwarding" config option), now supports Windows.
11759 - When using an exit relay running 0.2.3.x, clients can now
11760 "optimistically" send data before the exit relay reports that
11761 the stream has opened. This saves a round trip when starting
11762 connections where the client speaks first (such as web browsing).
11763 This behavior is controlled by a consensus parameter (currently
11764 disabled). To turn it on or off manually, use the "OptimisticData"
11765 torrc option. Implements proposal 181; code by Ian Goldberg.
11767 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
11768 - When using IOCP on Windows, we need to enable Libevent windows
11770 - The IOCP backend now works even when the user has not specified
11771 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
11772 Fixes part of bug 3752.
11773 - Correctly record the bytes we've read and written when using
11774 bufferevents, so that we can include them in our bandwidth history
11775 and advertised bandwidth. Fixes bug 3803.
11776 - Apply rate-limiting only at the bottom of a chain of filtering
11777 bufferevents. This prevents us from filling up internal read
11778 buffers and violating rate-limits when filtering bufferevents
11779 are enabled. Fixes part of bug 3804.
11780 - Add high-watermarks to the output buffers for filtered
11781 bufferevents. This prevents us from filling up internal write
11782 buffers and wasting CPU cycles when filtering bufferevents are
11783 enabled. Fixes part of bug 3804.
11784 - Correctly notice when data has been written from a bufferevent
11785 without flushing it completely. Fixes bug 3805.
11786 - Fix a bug where server-side tunneled bufferevent-based directory
11787 streams would get closed prematurely. Fixes bug 3814.
11788 - Fix a use-after-free error with per-connection rate-limiting
11789 buckets. Fixes bug 3888.
11791 o Major bugfixes (also part of 0.2.2.31-rc):
11792 - If we're configured to write our ControlPorts to disk, only write
11793 them after switching UID and creating the data directory. This way,
11794 we don't fail when starting up with a nonexistent DataDirectory
11795 and a ControlPortWriteToFile setting based on that directory. Fixes
11796 bug 3747; bugfix on Tor 0.2.2.26-beta.
11799 - Added a new CONF_CHANGED event so that controllers can be notified
11800 of any configuration changes made by other controllers, or by the
11801 user. Implements ticket 1692.
11802 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
11803 leak when using bufferevents, and lets Libevent worry about how to
11804 best copy data out of a buffer.
11805 - Replace files in stats/ rather than appending to them. Now that we
11806 include statistics in extra-info descriptors, it makes no sense to
11807 keep old statistics forever. Implements ticket 2930.
11809 o Minor features (build compatibility):
11810 - Limited, experimental support for building with nmake and MSVC.
11811 - Provide a substitute implementation of lround() for MSVC, which
11812 apparently lacks it. Patch from Gisle Vanem.
11814 o Minor features (also part of 0.2.2.31-rc):
11815 - Update to the August 2 2011 Maxmind GeoLite Country database.
11817 o Minor bugfixes (on 0.2.3.x-alpha):
11818 - Fix a spurious warning when parsing SOCKS requests with
11819 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
11820 - Get rid of a harmless warning that could happen on relays running
11821 with bufferevents. The warning was caused by someone doing an http
11822 request to a relay's orport. Also don't warn for a few related
11823 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
11825 o Minor bugfixes (on 2.2.x and earlier):
11826 - Correct the man page to explain that HashedControlPassword and
11827 CookieAuthentication can both be set, in which case either method
11828 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
11829 when we decided to allow these config options to both be set. Issue
11830 raised by bug 3898.
11831 - The "--quiet" and "--hush" options now apply not only to Tor's
11832 behavior before logs are configured, but also to Tor's behavior in
11833 the absense of configured logs. Fixes bug 3550; bugfix on
11836 o Minor bugfixes (also part of 0.2.2.31-rc):
11837 - Write several files in text mode, on OSes that distinguish text
11838 mode from binary mode (namely, Windows). These files are:
11839 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
11840 that collect those statistics; 'client_keys' and 'hostname' for
11841 hidden services that use authentication; and (in the tor-gencert
11842 utility) newly generated identity and signing keys. Previously,
11843 we wouldn't specify text mode or binary mode, leading to an
11844 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
11845 the DirRecordUsageByCountry option which would have triggered
11846 the assertion failure was added), although this assertion failure
11847 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
11848 - Selectively disable deprecation warnings on OS X because Lion
11849 started deprecating the shipped copy of openssl. Fixes bug 3643.
11850 - Remove an extra pair of quotation marks around the error
11851 message in control-port STATUS_GENERAL BUG events. Bugfix on
11852 0.1.2.6-alpha; fixes bug 3732.
11853 - When unable to format an address as a string, report its value
11854 as "???" rather than reusing the last formatted address. Bugfix
11857 o Code simplifications and refactoring:
11858 - Rewrite the listener-selection logic so that parsing which ports
11859 we want to listen on is now separate from binding to the ports
11863 - Building Tor with bufferevent support now requires Libevent
11864 2.0.13-stable or later. Previous versions of Libevent had bugs in
11865 SSL-related bufferevents and related issues that would make Tor
11866 work badly with bufferevents. Requiring 2.0.13-stable also allows
11867 Tor with bufferevents to take advantage of Libevent APIs
11868 introduced after 2.0.8-rc.
11871 Changes in version 0.2.2.32 - 2011-08-27
11872 The Tor 0.2.2 release series is dedicated to the memory of Andreas
11873 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
11874 a founder of the PETS community, a leader in our field, a mentor,
11875 and a friend. He left us with these words: "I had the possibility
11876 to contribute to this world that is not as it should be. I hope I
11877 could help in some areas to make the world a better place, and that
11878 I could also encourage other people to be engaged in improving the
11879 world. Please, stay engaged. This world needs you, your love, your
11880 initiative -- now I cannot be part of that anymore."
11882 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
11883 ready. More than two years in the making, this release features improved
11884 client performance and hidden service reliability, better compatibility
11885 for Android, correct behavior for bridges that listen on more than
11886 one address, more extensible and flexible directory object handling,
11887 better reporting of network statistics, improved code security, and
11888 many many other features and bugfixes.
11891 Changes in version 0.2.2.31-rc - 2011-08-17
11892 Tor 0.2.2.31-rc is the second and hopefully final release candidate
11893 for the Tor 0.2.2.x series.
11896 - Remove an extra pair of quotation marks around the error
11897 message in control-port STATUS_GENERAL BUG events. Bugfix on
11898 0.1.2.6-alpha; fixes bug 3732.
11899 - If we're configured to write our ControlPorts to disk, only write
11900 them after switching UID and creating the data directory. This way,
11901 we don't fail when starting up with a nonexistent DataDirectory
11902 and a ControlPortWriteToFile setting based on that directory. Fixes
11903 bug 3747; bugfix on Tor 0.2.2.26-beta.
11906 - Update to the August 2 2011 Maxmind GeoLite Country database.
11909 - Allow GETINFO fingerprint to return a fingerprint even when
11910 we have not yet built a router descriptor. Fixes bug 3577;
11911 bugfix on 0.2.0.1-alpha.
11912 - Write several files in text mode, on OSes that distinguish text
11913 mode from binary mode (namely, Windows). These files are:
11914 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
11915 that collect those statistics; 'client_keys' and 'hostname' for
11916 hidden services that use authentication; and (in the tor-gencert
11917 utility) newly generated identity and signing keys. Previously,
11918 we wouldn't specify text mode or binary mode, leading to an
11919 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
11920 the DirRecordUsageByCountry option which would have triggered
11921 the assertion failure was added), although this assertion failure
11922 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
11923 - Selectively disable deprecation warnings on OS X because Lion
11924 started deprecating the shipped copy of openssl. Fixes bug 3643.
11925 - When unable to format an address as a string, report its value
11926 as "???" rather than reusing the last formatted address. Bugfix
11930 Changes in version 0.2.3.2-alpha - 2011-07-18
11931 Tor 0.2.3.2-alpha introduces two new experimental features:
11932 microdescriptors and pluggable transports. It also continues cleaning
11933 up a variety of recently introduced features.
11936 - Clients can now use microdescriptors instead of regular descriptors
11937 to build circuits. Microdescriptors are authority-generated
11938 summaries of regular descriptors' contents, designed to change
11939 very rarely (see proposal 158 for details). This feature is
11940 designed to save bandwidth, especially for clients on slow internet
11941 connections. It's off by default for now, since nearly no caches
11942 support it, but it will be on-by-default for clients in a future
11943 version. You can use the UseMicrodescriptors option to turn it on.
11944 - Tor clients using bridges can now be configured to use a separate
11945 'transport' proxy for each bridge. This approach helps to resist
11946 censorship by allowing bridges to use protocol obfuscation
11947 plugins. It implements part of proposal 180. Implements ticket 2841.
11948 - While we're trying to bootstrap, record how many TLS connections
11949 fail in each state, and report which states saw the most failures
11950 in response to any bootstrap failures. This feature may speed up
11951 diagnosis of censorship events. Implements ticket 3116.
11953 o Major bugfixes (on 0.2.3.1-alpha):
11954 - When configuring a large set of nodes in EntryNodes (as with
11955 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
11956 random subset to be guards, and choose them in random
11957 order. Fixes bug 2798.
11958 - Tor could crash when remembering a consensus in a non-used consensus
11959 flavor without having a current consensus set. Fixes bug 3361.
11960 - Comparing an unknown address to a microdescriptor's shortened exit
11961 policy would always give a "rejected" result. Fixes bug 3599.
11962 - Using microdescriptors as a client no longer prevents Tor from
11963 uploading and downloading hidden service descriptors. Fixes
11967 - Allow nameservers with IPv6 address. Resolves bug 2574.
11968 - Accept attempts to include a password authenticator in the
11969 handshake, as supported by SOCKS5. This handles SOCKS clients that
11970 don't know how to omit a password when authenticating. Resolves
11972 - When configuring a large set of nodes in EntryNodes, and there are
11973 enough of them listed as Guard so that we don't need to consider
11974 the non-guard entries, prefer the ones listed with the Guard flag.
11975 - Check for and recover from inconsistency in the microdescriptor
11976 cache. This will make it harder for us to accidentally free a
11977 microdescriptor without removing it from the appropriate data
11978 structures. Fixes issue 3135; issue noted by "wanoskarnet".
11979 - Log SSL state transitions at log level DEBUG, log domain
11980 HANDSHAKE. This can be useful for debugging censorship events.
11981 Implements ticket 3264.
11982 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
11983 implements ticket 3439.
11985 o Minor bugfixes (on 0.2.3.1-alpha):
11986 - Do not free all general-purpose regular descriptors just
11987 because microdescriptor use is enabled. Fixes bug 3113.
11988 - Correctly link libevent_openssl when --enable-static-libevent
11989 is passed to configure. Fixes bug 3118.
11990 - Bridges should not complain during their heartbeat log messages that
11991 they are unlisted in the consensus: that's more or less the point
11992 of being a bridge. Fixes bug 3183.
11993 - Report a SIGNAL event to controllers when acting on a delayed
11994 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
11995 event to the controller if we acted on a SIGNAL NEWNYM command
11996 immediately, and otherwise not report a SIGNAL event for the
11997 command at all. Fixes bug 3349.
11998 - Fix a crash when handling the SIGNAL controller command or
11999 reporting ERR-level status events with bufferevents enabled. Found
12000 by Robert Ransom. Fixes bug 3367.
12001 - Always ship the tor-fw-helper manpage in our release tarballs.
12002 Fixes bug 3389. Reported by Stephen Walker.
12003 - Fix a class of double-mark-for-close bugs when bufferevents
12004 are enabled. Fixes bug 3403.
12005 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
12006 - Add SIGNAL to the list returned by the 'GETINFO events/names'
12007 control-port command. Fixes part of bug 3465.
12008 - Prevent using negative indices during unit test runs when read_all()
12009 fails. Spotted by coverity.
12010 - Fix a rare memory leak when checking the nodelist without it being
12011 present. Found by coverity.
12012 - Only try to download a microdescriptor-flavored consensus from
12013 a directory cache that provides them.
12015 o Minor bugfixes (on 0.2.2.x and earlier):
12016 - Assert that hidden-service-related operations are not performed
12017 using single-hop circuits. Previously, Tor would assert that
12018 client-side streams are not attached to single-hop circuits,
12019 but not that other sensitive operations on the client and service
12020 side are not performed using single-hop circuits. Fixes bug 3332;
12022 - Don't publish a new relay descriptor when we reload our onion key,
12023 unless the onion key has actually changed. Fixes bug 3263 and
12024 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
12025 - Allow GETINFO fingerprint to return a fingerprint even when
12026 we have not yet built a router descriptor. Fixes bug 3577;
12027 bugfix on 0.2.0.1-alpha.
12028 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
12029 on 0.2.2.4-alpha; fixes bug 3427.
12031 o Code simplification and refactoring:
12032 - Use tor_sscanf() in place of scanf() in more places through the
12033 code. This makes us a little more locale-independent, and
12034 should help shut up code-analysis tools that can't tell
12035 a safe sscanf string from a dangerous one.
12036 - Use tt_assert(), not tor_assert(), for checking for test failures.
12037 This makes the unit tests more able to go on in the event that
12039 - Split connection_about_to_close() into separate functions for each
12043 - On Windows, we now define the _WIN32_WINNT macros only if they
12044 are not already defined. This lets the person building Tor decide,
12045 if they want, to require a later version of Windows.
12048 Changes in version 0.2.2.30-rc - 2011-07-07
12049 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
12050 series. It fixes a few smaller bugs, but generally appears stable.
12051 Please test it and let us know whether it is!
12054 - Send a SUCCEEDED stream event to the controller when a reverse
12055 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
12056 discovered by katmagic.
12057 - Always NUL-terminate the sun_path field of a sockaddr_un before
12058 passing it to the kernel. (Not a security issue: kernels are
12059 smart enough to reject bad sockaddr_uns.) Found by Coverity;
12060 CID #428. Bugfix on Tor 0.2.0.3-alpha.
12061 - Don't stack-allocate the list of supplementary GIDs when we're
12062 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
12063 could take up to 256K, which is way too much stack. Found by
12064 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
12065 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
12066 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
12067 fixes part of bug 3465.
12068 - Fix a memory leak when receiving a descriptor for a hidden
12069 service we didn't ask for. Found by Coverity; CID #30. Bugfix
12073 - Update to the July 1 2011 Maxmind GeoLite Country database.
12076 Changes in version 0.2.2.29-beta - 2011-06-20
12077 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
12078 have bridge lines in their torrc but don't want to use them; gets
12079 us closer to having the control socket feature working on Debian;
12080 and fixes a variety of smaller bugs.
12083 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
12084 When we changed the default behavior to "use bridges if any
12085 are listed in the torrc", we surprised users who had bridges
12086 in their torrc files but who didn't actually want to use them.
12087 Partial resolution for bug 3354.
12090 - Don't attach new streams to old rendezvous circuits after SIGNAL
12091 NEWNYM. Previously, we would keep using an existing rendezvous
12092 circuit if it remained open (i.e. if it were kept open by a
12093 long-lived stream, or if a new stream were attached to it before
12094 Tor could notice that it was old and no longer in use). Bugfix on
12095 0.1.1.15-rc; fixes bug 3375.
12098 - Fix a bug when using ControlSocketsGroupWritable with User. The
12099 directory's group would be checked against the current group, not
12100 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
12101 bugfix on 0.2.2.26-beta.
12102 - Make connection_printf_to_buf()'s behavior sane. Its callers
12103 expect it to emit a CRLF iff the format string ends with CRLF;
12104 it actually emitted a CRLF iff (a) the format string ended with
12105 CRLF or (b) the resulting string was over 1023 characters long or
12106 (c) the format string did not end with CRLF *and* the resulting
12107 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
12108 fixes part of bug 3407.
12109 - Make send_control_event_impl()'s behavior sane. Its callers
12110 expect it to always emit a CRLF at the end of the string; it
12111 might have emitted extra control characters as well. Bugfix on
12112 0.1.1.9-alpha; fixes another part of bug 3407.
12113 - Make crypto_rand_int() check the value of its input correctly.
12114 Previously, it accepted values up to UINT_MAX, but could return a
12115 negative number if given a value above INT_MAX+1. Found by George
12116 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
12117 - Avoid a segfault when reading a malformed circuit build state
12118 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
12120 - When asked about a DNS record type we don't support via a
12121 client DNSPort, reply with NOTIMPL rather than an empty
12122 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
12123 - Fix a rare memory leak during stats writing. Found by coverity.
12126 - Update to the June 1 2011 Maxmind GeoLite Country database.
12128 o Code simplifications and refactoring:
12129 - Remove some dead code as indicated by coverity.
12130 - Remove a few dead assignments during router parsing. Found by
12132 - Add some forgotten return value checks during unit tests. Found
12134 - Don't use 1-bit wide signed bit fields. Found by coverity.
12137 Changes in version 0.2.2.28-beta - 2011-06-04
12138 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
12139 fixed a big bug in whether relays stay in the consensus consistently,
12140 we moved closer to handling bridges and hidden services correctly,
12141 and we started the process of better handling the dreaded "my Vidalia
12142 died, and now my Tor demands a password when I try to reconnect to it"
12146 - Don't decide to make a new descriptor when receiving a HUP signal.
12147 This bug has caused a lot of 0.2.2.x relays to disappear from the
12148 consensus periodically. Fixes the most common case of triggering
12149 bug 1810; bugfix on 0.2.2.7-alpha.
12150 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
12151 - Don't try to build descriptors if "ORPort auto" is set and we
12152 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
12154 - Resolve a crash that occurred when setting BridgeRelay to 1 with
12155 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
12156 - Apply circuit timeouts to opened hidden-service-related circuits
12157 based on the correct start time. Previously, we would apply the
12158 circuit build timeout based on time since the circuit's creation;
12159 it was supposed to be applied based on time since the circuit
12160 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
12161 - Use the same circuit timeout for client-side introduction
12162 circuits as for other four-hop circuits, rather than the timeout
12163 for single-hop directory-fetch circuits; the shorter timeout may
12164 have been appropriate with the static circuit build timeout in
12165 0.2.1.x and earlier, but caused many hidden service access attempts
12166 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
12167 on 0.2.2.2-alpha; fixes another part of bug 1297.
12168 - In ticket 2511 we fixed a case where you could use an unconfigured
12169 bridge if you had configured it as a bridge the last time you ran
12170 Tor. Now fix another edge case: if you had configured it as a bridge
12171 but then switched to a different bridge via the controller, you
12172 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
12176 - Add an __OwningControllerProcess configuration option and a
12177 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
12178 that when it exits, Tor will shut down. Implements feature 3049.
12179 - If "UseBridges 1" is set and no bridges are configured, Tor will
12180 now refuse to build any circuits until some bridges are set.
12181 If "UseBridges auto" is set, Tor will use bridges if they are
12182 configured and we are not running as a server, but otherwise will
12183 make circuits as usual. The new default is "auto". Patch by anonym,
12184 so the Tails LiveCD can stop automatically revealing you as a Tor
12188 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
12189 - Remove a trailing asterisk from "exit-policy/default" in the
12190 output of the control port command "GETINFO info/names". Bugfix
12192 - Use a wide type to hold sockets when built for 64-bit Windows builds.
12194 - Warn when the user configures two HiddenServiceDir lines that point
12195 to the same directory. Bugfix on 0.0.6 (the version introducing
12196 HiddenServiceDir); fixes bug 3289.
12197 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
12198 part of bug 2748; bugfix on 0.2.0.10-alpha.
12199 - Log malformed requests for rendezvous descriptors as protocol
12200 warnings, not warnings. Also, use a more informative log message
12201 in case someone sees it at log level warning without prior
12202 info-level messages. Fixes the other part of bug 2748; bugfix
12204 - Clear the table recording the time of the last request for each
12205 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
12206 Previously, we would clear our HS descriptor cache on SIGNAL
12207 NEWNYM, but if we had previously retrieved a descriptor (or tried
12208 to) from every directory responsible for it, we would refuse to
12209 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
12211 - Fix a log message that said "bits" while displaying a value in
12212 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
12214 - When checking for 1024-bit keys, check for 1024 bits, not 128
12215 bytes. This allows Tor to correctly discard keys of length 1017
12216 through 1023. Bugfix on 0.0.9pre5.
12219 - Relays now log the reason for publishing a new relay descriptor,
12220 so we have a better chance of hunting down instances of bug 1810.
12221 Resolves ticket 3252.
12222 - Revise most log messages that refer to nodes by nickname to
12223 instead use the "$key=nickname at address" format. This should be
12224 more useful, especially since nicknames are less and less likely
12225 to be unique. Resolves ticket 3045.
12226 - Log (at info level) when purging pieces of hidden-service-client
12227 state because of SIGNAL NEWNYM.
12230 - Remove undocumented option "-F" from tor-resolve: it hasn't done
12231 anything since 0.2.1.16-rc.
12234 Changes in version 0.2.2.27-beta - 2011-05-18
12235 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
12236 release, and also adds a few more general bugfixes.
12239 - Fix a crash bug when changing bridges in a running Tor process.
12240 Fixes bug 3213; bugfix on 0.2.2.26-beta.
12241 - When the controller configures a new bridge, don't wait 10 to 60
12242 seconds before trying to fetch its descriptor. Bugfix on
12243 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
12246 - Require that onion keys have exponent 65537 in microdescriptors too.
12247 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
12248 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
12249 Changed the limit to 512 characters by removing base64 newlines.
12250 Fixes bug 2752. Fix by Michael Yakubovich.
12251 - When a client starts or stops using bridges, never use a circuit
12252 that was built before the configuration change. This behavior could
12253 put at risk a user who uses bridges to ensure that her traffic
12254 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
12258 Changes in version 0.2.2.26-beta - 2011-05-17
12259 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
12260 also introduces a new "socksport auto" approach that should make it
12261 easier to run multiple Tors on the same system, and does a lot of
12262 cleanup to get us closer to a release candidate.
12264 o Security/privacy fixes:
12265 - Replace all potentially sensitive memory comparison operations
12266 with versions whose runtime does not depend on the data being
12267 compared. This will help resist a class of attacks where an
12268 adversary can use variations in timing information to learn
12269 sensitive data. Fix for one case of bug 3122. (Safe memcmp
12270 implementation by Robert Ransom based partially on code by DJB.)
12271 - When receiving a hidden service descriptor, check that it is for
12272 the hidden service we wanted. Previously, Tor would store any
12273 hidden service descriptors that a directory gave it, whether it
12274 wanted them or not. This wouldn't have let an attacker impersonate
12275 a hidden service, but it did let directories pre-seed a client
12276 with descriptors that it didn't want. Bugfix on 0.0.6.
12277 - On SIGHUP, do not clear out all TrackHostExits mappings, client
12278 DNS cache entries, and virtual address mappings: that's what
12279 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
12282 - The options SocksPort, ControlPort, and so on now all accept a
12283 value "auto" that opens a socket on an OS-selected port. A
12284 new ControlPortWriteToFile option tells Tor to write its
12285 actual control port or ports to a chosen file. If the option
12286 ControlPortFileGroupReadable is set, the file is created as
12287 group-readable. Now users can run two Tor clients on the same
12288 system without needing to manually mess with parameters. Resolves
12289 part of ticket 3076.
12290 - Set SO_REUSEADDR on all sockets, not just listeners. This should
12291 help busy exit nodes avoid running out of useable ports just
12292 because all the ports have been used in the near past. Resolves
12296 - New "GETINFO net/listeners/(type)" controller command to return
12297 a list of addresses and ports that are bound for listeners for a
12298 given connection type. This is useful when the user has configured
12299 "SocksPort auto" and the controller needs to know which port got
12300 chosen. Resolves another part of ticket 3076.
12301 - Add a new ControlSocketsGroupWritable configuration option: when
12302 it is turned on, ControlSockets are group-writeable by the default
12303 group of the current user. Patch by Jérémy Bobbio; implements
12305 - Tor now refuses to create a ControlSocket in a directory that is
12306 world-readable (or group-readable if ControlSocketsGroupWritable
12307 is 0). This is necessary because some operating systems do not
12308 enforce permissions on an AF_UNIX sockets. Permissions on the
12309 directory holding the socket, however, seems to work everywhere.
12310 - Rate-limit a warning about failures to download v2 networkstatus
12311 documents. Resolves part of bug 1352.
12312 - Backport code from 0.2.3.x that allows directory authorities to
12313 clean their microdescriptor caches. Needed to resolve bug 2230.
12314 - When an HTTPS proxy reports "403 Forbidden", we now explain
12315 what it means rather than calling it an unexpected status code.
12316 Closes bug 2503. Patch from Michael Yakubovich.
12317 - Update to the May 1 2011 Maxmind GeoLite Country database.
12320 - Authorities now clean their microdesc cache periodically and when
12321 reading from disk initially, not only when adding new descriptors.
12322 This prevents a bug where we could lose microdescriptors. Bugfix
12323 on 0.2.2.6-alpha. Fixes bug 2230.
12324 - Do not crash when our configuration file becomes unreadable, for
12325 example due to a permissions change, between when we start up
12326 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
12328 - Avoid a bug that would keep us from replacing a microdescriptor
12329 cache on Windows. (We would try to replace the file while still
12330 holding it open. That's fine on Unix, but Windows doesn't let us
12331 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
12332 - Add missing explanations for the authority-related torrc options
12333 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
12334 man page. Resolves issue 2379.
12335 - As an authority, do not upload our own vote or signature set to
12336 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
12337 it would get flagged as a duplicate. Resolves bug 3026.
12338 - Accept hidden service descriptors if we think we might be a hidden
12339 service directory, regardless of what our consensus says. This
12340 helps robustness, since clients and hidden services can sometimes
12341 have a more up-to-date view of the network consensus than we do,
12342 and if they think that the directory authorities list us a HSDir,
12343 we might actually be one. Related to bug 2732; bugfix on
12345 - When a controller changes TrackHostExits, remove mappings for
12346 hosts that should no longer have their exits tracked. Bugfix on
12348 - When a controller changes VirtualAddrNetwork, remove any mappings
12349 for hosts that were automapped to the old network. Bugfix on
12351 - When a controller changes one of the AutomapHosts* options, remove
12352 any mappings for hosts that should no longer be automapped. Bugfix
12354 - Do not reset the bridge descriptor download status every time we
12355 re-parse our configuration or get a configuration change. Fixes
12356 bug 3019; bugfix on 0.2.0.3-alpha.
12358 o Minor bugfixes (code cleanup):
12359 - When loading the microdesc journal, remember its current size.
12360 In 0.2.2, this helps prevent the microdesc journal from growing
12361 without limit on authorities (who are the only ones to use it in
12362 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
12363 Fix posted by "cypherpunks."
12364 - The microdesc journal is supposed to get rebuilt only if it is
12365 at least _half_ the length of the store, not _twice_ the length
12366 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
12367 - Fix a potential null-pointer dereference while computing a
12368 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
12370 - Avoid a possible null-pointer dereference when rebuilding the mdesc
12371 cache without actually having any descriptors to cache. Bugfix on
12372 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
12373 - If we fail to compute the identity digest of a v3 legacy keypair,
12374 warn, and don't use a buffer-full of junk instead. Bugfix on
12375 0.2.1.1-alpha; fixes bug 3106.
12376 - Resolve an untriggerable issue in smartlist_string_num_isin(),
12377 where if the function had ever in the future been used to check
12378 for the presence of a too-large number, it would have given an
12379 incorrect result. (Fortunately, we only used it for 16-bit
12380 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
12381 - Require that introduction point keys and onion handshake keys
12382 have a public exponent of 65537. Starts to fix bug 3207; bugfix
12385 o Removed features:
12386 - Caches no longer download and serve v2 networkstatus documents
12387 unless FetchV2Networkstatus flag is set: these documents haven't
12388 haven't been used by clients or relays since 0.2.0.x. Resolves
12392 Changes in version 0.2.3.1-alpha - 2011-05-05
12393 Tor 0.2.3.1-alpha adds some new experimental features, including support
12394 for an improved network IO backend, IOCP networking on Windows,
12395 microdescriptor caching, "fast-start" support for streams, and automatic
12396 home router configuration. There are also numerous internal improvements
12397 to try to make the code easier for developers to work with.
12399 This is the first alpha release in a new series, so expect there to be
12400 bugs. Users who would rather test out a more stable branch should
12401 stay with 0.2.2.x for now.
12404 - Tor can now optionally build with the "bufferevents" buffered IO
12405 backend provided by Libevent 2. To use this feature, make sure you
12406 have the latest possible version of Libevent, and pass the
12407 --enable-bufferevents flag to configure when building Tor from
12408 source. This feature will make our networking code more flexible,
12409 let us stack layers on each other, and let us use more efficient
12410 zero-copy transports where available.
12411 - As an experimental feature, Tor can use IOCP for networking on Windows.
12412 Once this code is tuned and optimized, it promises much better
12413 performance than the select-based backend we've used in the past. To
12414 try this feature, you must build Tor with Libevent 2, configure Tor
12415 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
12416 your torrc. There are known bugs here: only try this if you can help
12417 debug it as it breaks.
12418 - The EntryNodes option can now include country codes like {de} or IP
12419 addresses or network masks. Previously we had disallowed these options
12420 because we didn't have an efficient way to keep the list up to
12421 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
12422 - Exit nodes now accept and queue data on not-yet-connected streams.
12423 Previously, the client wasn't allowed to send data until the stream was
12424 connected, which slowed down all connections. This change will enable
12425 clients to perform a "fast-start" on streams and send data without
12426 having to wait for a confirmation that the stream has opened. (Patch
12427 from Ian Goldberg; implements the server side of Proposal 174.)
12428 - Tor now has initial support for automatic port mapping on the many
12429 home routers that support NAT-PMP or UPnP. (Not yet supported on
12430 Windows). To build the support code, you'll need to have libnatpnp
12431 library and/or the libminiupnpc library, and you'll need to enable the
12432 feature specifically by passing "--enable-upnp" and/or
12433 "--enable-natpnp" to configure. To turn it on, use the new
12434 PortForwarding option.
12435 - Caches now download, cache, and serve multiple "flavors" of the
12436 consensus, including a flavor that describes microdescriptors.
12437 - Caches now download, cache, and serve microdescriptors -- small
12438 summaries of router descriptors that are authenticated by all of the
12439 directory authorities. Once enough caches are running this code,
12440 clients will be able to save significant amounts of directory bandwidth
12441 by downloading microdescriptors instead of router descriptors.
12444 - Make logging resolution configurable with a new LogTimeGranularity
12445 option, and change the default from 1 millisecond to 1 second.
12446 Implements enhancement 1668.
12447 - We log which torrc file we're using on startup. Implements ticket
12449 - Ordinarily, Tor does not count traffic from private addresses (like
12450 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
12451 There is now a new option, CountPrivateBandwidth, to disable this
12452 behavior. Patch from Daniel Cagara.
12453 - New --enable-static-tor configure option for building Tor as
12454 statically as possible. Idea, general hackery and thoughts from
12455 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
12457 - If you set the NumCPUs option to 0, Tor will now try to detect how
12458 many CPUs you have. This is the new default behavior.
12459 - Turn on directory request statistics by default and include them in
12460 extra-info descriptors. Don't break if we have no GeoIP database.
12461 - Relays that set "ConnDirectionStatistics 1" write statistics on the
12462 bidirectional use of connections to disk every 24 hours.
12463 - Add a GeoIP file digest to the extra-info descriptor. Implements
12465 - The NodeFamily option -- which let you declare that you want to
12466 consider nodes to be part of a family whether they list themselves
12467 that way or not -- now allows IP address ranges and country codes.
12468 - Add a new 'Heartbeat' log message type to periodically log a message
12469 describing Tor's status at level Notice. This feature is meant for
12470 operators who log at notice, and want to make sure that their Tor
12471 server is still working. Implementation by George Kadianakis.
12473 o Minor bugfixes (on 0.2.2.25-alpha):
12474 - When loading the microdesc journal, remember its current size.
12475 In 0.2.2, this helps prevent the microdesc journal from growing
12476 without limit on authorities (who are the only ones to use it in
12477 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
12478 Fix posted by "cypherpunks."
12479 - The microdesc journal is supposed to get rebuilt only if it is
12480 at least _half_ the length of the store, not _twice_ the length
12481 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
12482 - If as an authority we fail to compute the identity digest of a v3
12483 legacy keypair, warn, and don't use a buffer-full of junk instead.
12484 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
12485 - Authorities now clean their microdesc cache periodically and when
12486 reading from disk initially, not only when adding new descriptors.
12487 This prevents a bug where we could lose microdescriptors. Bugfix
12490 o Minor features (controller):
12491 - Add a new SIGNAL event to the controller interface so that
12492 controllers can be notified when Tor handles a signal. Resolves
12493 issue 1955. Patch by John Brooks.
12494 - Add a new GETINFO option to get total bytes read and written. Patch
12495 from pipe, revised by atagar. Resolves ticket 2345.
12496 - Implement some GETINFO controller fields to provide information about
12497 the Tor process's pid, euid, username, and resource limits.
12500 - Our build system requires automake 1.6 or later to create the
12501 Makefile.in files. Previously, you could have used 1.4.
12502 This only affects developers and people building Tor from git;
12503 people who build Tor from the source distribution without changing
12504 the Makefile.am files should be fine.
12505 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
12506 so on. This is more robust against some of the failure modes
12507 associated with running the autotools pieces on their own.
12509 o Minor packaging issues:
12510 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
12511 already created. Patch from Andreas Stieger. Fixes bug 2573.
12513 o Code simplifications and refactoring:
12514 - A major revision to our internal node-selecting and listing logic.
12515 Tor already had at least two major ways to look at the question of
12516 "which Tor servers do we know about": a list of router descriptors,
12517 and a list of entries in the current consensus. With
12518 microdescriptors, we're adding a third. Having so many systems
12519 without an abstraction layer over them was hurting the codebase.
12520 Now, we have a new "node_t" abstraction that presents a consistent
12521 interface to a client's view of a Tor node, and holds (nearly) all
12522 of the mutable state formerly in routerinfo_t and routerstatus_t.
12523 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
12524 no longer link against Libevent: they never used it, but
12525 our library structure used to force them to link it.
12527 o Removed features:
12528 - Remove some old code to work around even older versions of Tor that
12529 used forked processes to handle DNS requests. Such versions of Tor
12530 are no longer in use as servers.
12532 o Documentation fixes:
12533 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
12534 - Add missing documentation for the authority-related torrc options
12535 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
12539 Changes in version 0.2.2.25-alpha - 2011-04-29
12540 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
12541 robust, routers no longer overreport their bandwidth, Win7 should crash
12542 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
12543 now prevents hidden service-related activity from being linkable. It
12544 provides more information to Vidalia so you can see if your bridge is
12545 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
12546 StrictNodes configuration options to make them more reliable, more
12547 understandable, and more regularly applied. If you use those options,
12548 please see the revised documentation for them in the manual page.
12551 - Relays were publishing grossly inflated bandwidth values because
12552 they were writing their state files wrong--now they write the
12553 correct value. Also, resume reading bandwidth history from the
12554 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
12555 - Improve hidden service robustness: When we find that we have
12556 extended a hidden service's introduction circuit to a relay not
12557 listed as an introduction point in the HS descriptor we currently
12558 have, retry with an introduction point from the current
12559 descriptor. Previously we would just give up. Fixes bugs 1024 and
12560 1930; bugfix on 0.2.0.10-alpha.
12561 - Clients now stop trying to use an exit node associated with a given
12562 destination by TrackHostExits if they fail to reach that exit node.
12563 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
12564 - Fix crash bug on platforms where gmtime and localtime can return
12565 NULL. Windows 7 users were running into this one. Fixes part of bug
12566 2077. Bugfix on all versions of Tor. Found by boboper.
12568 o Security and stability fixes:
12569 - Don't double-free a parsable, but invalid, microdescriptor, even if
12570 it is followed in the blob we're parsing by an unparsable
12571 microdescriptor. Fixes an issue reported in a comment on bug 2954.
12572 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
12573 - If the Nickname configuration option isn't given, Tor would pick a
12574 nickname based on the local hostname as the nickname for a relay.
12575 Because nicknames are not very important in today's Tor and the
12576 "Unnamed" nickname has been implemented, this is now problematic
12577 behavior: It leaks information about the hostname without being
12578 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
12579 introduced the Unnamed nickname. Reported by tagnaq.
12580 - Fix an uncommon assertion failure when running with DNSPort under
12581 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
12582 - Avoid linkability based on cached hidden service descriptors: forget
12583 all hidden service descriptors cached as a client when processing a
12584 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
12587 - Export GeoIP information on bridge usage to controllers even if we
12588 have not yet been running for 24 hours. Now Vidalia bridge operators
12589 can get more accurate and immediate feedback about their
12590 contributions to the network.
12592 o Major features and bugfixes (node selection):
12593 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
12594 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
12595 options. Previously, we had been ambiguous in describing what
12596 counted as an "exit" node, and what operations exactly "StrictNodes
12597 0" would permit. This created confusion when people saw nodes built
12598 through unexpected circuits, and made it hard to tell real bugs from
12599 surprises. Now the intended behavior is:
12600 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
12601 a node that delivers user traffic outside the Tor network.
12602 . "Entry", in the context of EntryNodes, means a node used as the
12603 first hop of a multihop circuit. It doesn't include direct
12604 connections to directory servers.
12605 . "ExcludeNodes" applies to all nodes.
12606 . "StrictNodes" changes the behavior of ExcludeNodes only. When
12607 StrictNodes is set, Tor should avoid all nodes listed in
12608 ExcludeNodes, even when it will make user requests fail. When
12609 StrictNodes is *not* set, then Tor should follow ExcludeNodes
12610 whenever it can, except when it must use an excluded node to
12611 perform self-tests, connect to a hidden service, provide a
12612 hidden service, fulfill a .exit request, upload directory
12613 information, or fetch directory information.
12614 Collectively, the changes to implement the behavior fix bug 1090.
12615 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
12616 a node is listed in both, it's treated as excluded.
12617 - ExcludeNodes now applies to directory nodes -- as a preference if
12618 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
12619 Don't exclude all the directory authorities and set StrictNodes to 1
12620 unless you really want your Tor to break.
12621 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
12622 - ExcludeExitNodes now overrides .exit requests.
12623 - We don't use bridges listed in ExcludeNodes.
12624 - When StrictNodes is 1:
12625 . We now apply ExcludeNodes to hidden service introduction points
12626 and to rendezvous points selected by hidden service users. This
12627 can make your hidden service less reliable: use it with caution!
12628 . If we have used ExcludeNodes on ourself, do not try relay
12629 reachability self-tests.
12630 . If we have excluded all the directory authorities, we will not
12631 even try to upload our descriptor if we're a relay.
12632 . Do not honor .exit requests to an excluded node.
12633 - Remove a misfeature that caused us to ignore the Fast/Stable flags
12634 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
12635 - When the set of permitted nodes changes, we now remove any mappings
12636 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
12638 - We never cannibalize a circuit that had excluded nodes on it, even
12639 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
12640 - Revert a change where we would be laxer about attaching streams to
12641 circuits than when building the circuits. This was meant to prevent
12642 a set of bugs where streams were never attachable, but our improved
12643 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
12644 - Keep track of how many times we launch a new circuit to handle a
12645 given stream. Too many launches could indicate an inconsistency
12646 between our "launch a circuit to handle this stream" logic and our
12647 "attach this stream to one of the available circuits" logic.
12648 - Improve log messages related to excluded nodes.
12651 - Fix a spurious warning when moving from a short month to a long
12652 month on relays with month-based BandwidthAccounting. Bugfix on
12653 0.2.2.17-alpha; fixes bug 3020.
12654 - When a client finds that an origin circuit has run out of 16-bit
12655 stream IDs, we now mark it as unusable for new streams. Previously,
12656 we would try to close the entire circuit. Bugfix on 0.0.6.
12657 - Add a forgotten cast that caused a compile warning on OS X 10.6.
12658 Bugfix on 0.2.2.24-alpha.
12659 - Be more careful about reporting the correct error from a failed
12660 connect() system call. Under some circumstances, it was possible to
12661 look at an incorrect value for errno when sending the end reason.
12662 Bugfix on 0.1.0.1-rc.
12663 - Correctly handle an "impossible" overflow cases in connection byte
12664 counting, where we write or read more than 4GB on an edge connection
12665 in a single second. Bugfix on 0.1.2.8-beta.
12666 - Correct the warning displayed when a rendezvous descriptor exceeds
12667 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
12669 - Clients and hidden services now use HSDir-flagged relays for hidden
12670 service descriptor downloads and uploads even if the relays have no
12671 DirPort set and the client has disabled TunnelDirConns. This will
12672 eventually allow us to give the HSDir flag to relays with no
12673 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
12674 - Downgrade "no current certificates known for authority" message from
12675 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
12676 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
12677 2917. Bugfix on 0.1.1.1-alpha.
12678 - Only limit the lengths of single HS descriptors, even when multiple
12679 HS descriptors are published to an HSDir relay in a single POST
12680 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
12681 - Write the current time into the LastWritten line in our state file,
12682 rather than the time from the previous write attempt. Also, stop
12683 trying to use a time of -1 in our log statements. Fixes bug 3039;
12684 bugfix on 0.2.2.14-alpha.
12685 - Be more consistent in our treatment of file system paths. "~" should
12686 get expanded to the user's home directory in the Log config option.
12687 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
12688 feature for the -f and --DataDirectory options.
12691 - Make sure every relay writes a state file at least every 12 hours.
12692 Previously, a relay could go for weeks without writing its state
12693 file, and on a crash could lose its bandwidth history, capacity
12694 estimates, client country statistics, and so on. Addresses bug 3012.
12695 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
12696 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
12697 clients are already deprecated because of security bugs.
12698 - Don't allow v0 hidden service authorities to act as clients.
12699 Required by fix for bug 3000.
12700 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
12701 by fix for bug 3000.
12702 - Ensure that no empty [dirreq-](read|write)-history lines are added
12703 to an extrainfo document. Implements ticket 2497.
12705 o Code simplification and refactoring:
12706 - Remove workaround code to handle directory responses from servers
12707 that had bug 539 (they would send HTTP status 503 responses _and_
12708 send a body too). Since only server versions before
12709 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
12710 keep the workaround in place.
12711 - Remove the old 'fuzzy time' logic. It was supposed to be used for
12712 handling calculations where we have a known amount of clock skew and
12713 an allowed amount of unknown skew. But we only used it in three
12714 places, and we never adjusted the known/unknown skew values. This is
12715 still something we might want to do someday, but if we do, we'll
12716 want to do it differently.
12717 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
12718 None of the cases where we did this before were wrong, but by making
12719 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
12720 - Use GetTempDir to find the proper temporary directory location on
12721 Windows when generating temporary files for the unit tests. Patch by
12725 Changes in version 0.2.2.24-alpha - 2011-04-08
12726 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
12727 prevented Tor clients from effectively using "multihomed" bridges,
12728 that is, bridges that listen on multiple ports or IP addresses so users
12729 can continue to use some of their addresses even if others get blocked.
12732 - Fix a bug where bridge users who configure the non-canonical
12733 address of a bridge automatically switch to its canonical
12734 address. If a bridge listens at more than one address, it should be
12735 able to advertise those addresses independently and any non-blocked
12736 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
12738 - If you configured Tor to use bridge A, and then quit and
12739 configured Tor to use bridge B instead, it would happily continue
12740 to use bridge A if it's still reachable. While this behavior is
12741 a feature if your goal is connectivity, in some scenarios it's a
12742 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
12743 - Directory authorities now use data collected from their own
12744 uptime observations when choosing whether to assign the HSDir flag
12745 to relays, instead of trusting the uptime value the relay reports in
12746 its descriptor. This change helps prevent an attack where a small
12747 set of nodes with frequently-changing identity keys can blackhole
12748 a hidden service. (Only authorities need upgrade; others will be
12749 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
12752 - When we restart our relay, we might get a successful connection
12753 from the outside before we've started our reachability tests,
12754 triggering a warning: "ORPort found reachable, but I have no
12755 routerinfo yet. Failing to inform controller of success." This
12756 bug was harmless unless Tor is running under a controller
12757 like Vidalia, in which case the controller would never get a
12758 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
12760 - Make directory authorities more accurate at recording when
12761 relays that have failed several reachability tests became
12762 unreachable, so we can provide more accuracy at assigning Stable,
12763 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
12764 - Fix an issue that prevented static linking of libevent on
12765 some platforms (notably Linux). Fixes bug 2698; bugfix on
12766 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
12767 the --with-static-libevent configure option).
12768 - We now ask the other side of a stream (the client or the exit)
12769 for more data on that stream when the amount of queued data on
12770 that stream dips low enough. Previously, we wouldn't ask the
12771 other side for more data until either it sent us more data (which
12772 it wasn't supposed to do if it had exhausted its window!) or we
12773 had completely flushed all our queued data. This flow control fix
12774 should improve throughput. Fixes bug 2756; bugfix on the earliest
12775 released versions of Tor (svn commit r152).
12776 - Avoid a double-mark-for-free warning when failing to attach a
12777 transparent proxy connection. (We thought we had fixed this in
12778 0.2.2.23-alpha, but it turns out our fix was checking the wrong
12779 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
12780 bug) and 0.2.2.23-alpha (the incorrect fix).
12781 - When warning about missing zlib development packages during compile,
12782 give the correct package names. Bugfix on 0.2.0.1-alpha.
12785 - Directory authorities now log the source of a rejected POSTed v3
12786 networkstatus vote.
12787 - Make compilation with clang possible when using
12788 --enable-gcc-warnings by removing two warning options that clang
12789 hasn't implemented yet and by fixing a few warnings. Implements
12791 - When expiring circuits, use microsecond timers rather than
12792 one-second timers. This can avoid an unpleasant situation where a
12793 circuit is launched near the end of one second and expired right
12794 near the beginning of the next, and prevent fluctuations in circuit
12796 - Use computed circuit-build timeouts to decide when to launch
12797 parallel introduction circuits for hidden services. (Previously,
12798 we would retry after 15 seconds.)
12799 - Update to the April 1 2011 Maxmind GeoLite Country database.
12802 - Create the /var/run/tor directory on startup on OpenSUSE if it is
12803 not already created. Patch from Andreas Stieger. Fixes bug 2573.
12805 o Documentation changes:
12806 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
12807 - Resolve all doxygen warnings except those for missing documentation.
12809 - Add doxygen documentation for more functions, fields, and types.
12812 Changes in version 0.2.2.23-alpha - 2011-03-08
12813 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
12814 they restart they don't lose their bandwidth capacity estimate. This
12815 release also fixes a diverse set of user-facing bugs, ranging from
12816 relays overrunning their rate limiting to clients falsely warning about
12817 clock skew to bridge descriptor leaks by our bridge directory authority.
12820 - Stop sending a CLOCK_SKEW controller status event whenever
12821 we fetch directory information from a relay that has a wrong clock.
12822 Instead, only inform the controller when it's a trusted authority
12823 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
12824 the rest of bug 1074.
12825 - Fix an assert in parsing router descriptors containing IPv6
12826 addresses. This one took down the directory authorities when
12827 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
12828 - Make the bridge directory authority refuse to answer directory
12829 requests for "all" descriptors. It used to include bridge
12830 descriptors in its answer, which was a major information leak.
12831 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
12832 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
12833 Tor would ignore their RelayBandwidthBurst setting,
12834 potentially using more bandwidth than expected. Bugfix on
12835 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
12836 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
12837 hidserv" in her torrc. The 'hidserv' argument never controlled
12838 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
12841 - Relays now save observed peak bandwidth throughput rates to their
12842 state file (along with total usage, which was already saved)
12843 so that they can determine their correct estimated bandwidth on
12844 restart. Resolves bug 1863, where Tor relays would reset their
12845 estimated bandwidth to 0 after restarting.
12846 - Directory authorities now take changes in router IP address and
12847 ORPort into account when determining router stability. Previously,
12848 if a router changed its IP or ORPort, the authorities would not
12849 treat it as having any downtime for the purposes of stability
12850 calculation, whereas clients would experience downtime since the
12851 change could take a while to propagate to them. Resolves issue 1035.
12852 - Enable Address Space Layout Randomization (ASLR) and Data Execution
12853 Prevention (DEP) by default on Windows to make it harder for
12854 attackers to exploit vulnerabilities. Patch from John Brooks.
12856 o Minor bugfixes (on 0.2.1.x and earlier):
12857 - Fix a rare crash bug that could occur when a client was configured
12858 with a large number of bridges. Fixes bug 2629; bugfix on
12859 0.2.1.2-alpha. Bugfix by trac user "shitlei".
12860 - Avoid a double mark-for-free warning when failing to attach a
12861 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
12863 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
12864 found by "cypherpunks". This bug was introduced before the first
12865 Tor release, in svn commit r110.
12866 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
12867 don't mention them in the manpage. Fixes bug 2450; issue
12868 spotted by keb and G-Lo.
12869 - Fix a bug in bandwidth history state parsing that could have been
12870 triggered if a future version of Tor ever changed the timing
12871 granularity at which bandwidth history is measured. Bugfix on
12872 Tor 0.1.1.11-alpha.
12873 - When a relay decides that its DNS is too broken for it to serve
12874 as an exit server, it advertised itself as a non-exit, but
12875 continued to act as an exit. This could create accidental
12876 partitioning opportunities for users. Instead, if a relay is
12877 going to advertise reject *:* as its exit policy, it should
12878 really act with exit policy "reject *:*". Fixes bug 2366.
12879 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
12880 - In the special case where you configure a public exit relay as your
12881 bridge, Tor would be willing to use that exit relay as the last
12882 hop in your circuit as well. Now we fail that circuit instead.
12883 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
12884 - Fix a bug with our locking implementation on Windows that couldn't
12885 correctly detect when a file was already locked. Fixes bug 2504,
12886 bugfix on 0.2.1.6-alpha.
12887 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
12888 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
12890 - Set target port in get_interface_address6() correctly. Bugfix
12891 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
12892 - Directory authorities are now more robust to hops back in time
12893 when calculating router stability. Previously, if a run of uptime
12894 or downtime appeared to be negative, the calculation could give
12895 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
12897 - Fix an assert that got triggered when using the TestingTorNetwork
12898 configuration option and then issuing a GETINFO config-text control
12899 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
12901 o Minor bugfixes (on 0.2.2.x):
12902 - Clients should not weight BadExit nodes as Exits in their node
12903 selection. Similarly, directory authorities should not count BadExit
12904 bandwidth as Exit bandwidth when computing bandwidth-weights.
12905 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
12906 - Correctly clear our dir_read/dir_write history when there is an
12907 error parsing any bw history value from the state file. Bugfix on
12908 Tor 0.2.2.15-alpha.
12909 - Resolve a bug in verifying signatures of directory objects
12910 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
12911 Fixes bug 2409. Found by "piebeer".
12912 - Bridge authorities no longer crash on SIGHUP when they try to
12913 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
12917 - Log less aggressively about circuit timeout changes, and improve
12918 some other circuit timeout messages. Resolves bug 2004.
12919 - Log a little more clearly about the times at which we're no longer
12920 accepting new connections. Resolves bug 2181.
12921 - Reject attempts at the client side to open connections to private
12922 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
12923 a randomly chosen exit node. Attempts to do so are always
12924 ill-defined, generally prevented by exit policies, and usually
12925 in error. This will also help to detect loops in transparent
12926 proxy configurations. You can disable this feature by setting
12927 "ClientRejectInternalAddresses 0" in your torrc.
12928 - Always treat failure to allocate an RSA key as an unrecoverable
12930 - Update to the March 1 2011 Maxmind GeoLite Country database.
12932 o Minor features (log subsystem):
12933 - Add documentation for configuring logging at different severities in
12934 different log domains. We've had this feature since 0.2.1.1-alpha,
12935 but for some reason it never made it into the manpage. Fixes
12937 - Make it simpler to specify "All log domains except for A and B".
12938 Previously you needed to say "[*,~A,~B]". Now you can just say
12940 - Add a "LogMessageDomains 1" option to include the domains of log
12941 messages along with the messages. Without this, there's no way
12942 to use log domains without reading the source or doing a lot
12945 o Packaging changes:
12946 - Stop shipping the Tor specs files and development proposal documents
12947 in the tarball. They are now in a separate git repository at
12948 git://git.torproject.org/torspec.git
12951 Changes in version 0.2.1.30 - 2011-02-23
12952 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
12953 change is a slight tweak to Tor's TLS handshake that makes relays
12954 and bridges that run this new version reachable from Iran again.
12955 We don't expect this tweak will win the arms race long-term, but it
12956 buys us time until we roll out a better solution.
12959 - Stop sending a CLOCK_SKEW controller status event whenever
12960 we fetch directory information from a relay that has a wrong clock.
12961 Instead, only inform the controller when it's a trusted authority
12962 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
12963 the rest of bug 1074.
12964 - Fix a bounds-checking error that could allow an attacker to
12965 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
12966 Found by "piebeer".
12967 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
12968 Tor would ignore their RelayBandwidthBurst setting,
12969 potentially using more bandwidth than expected. Bugfix on
12970 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
12971 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
12972 hidserv" in her torrc. The 'hidserv' argument never controlled
12973 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
12976 - Adjust our TLS Diffie-Hellman parameters to match those used by
12978 - Update to the February 1 2011 Maxmind GeoLite Country database.
12981 - Check for and reject overly long directory certificates and
12982 directory tokens before they have a chance to hit any assertions.
12983 Bugfix on 0.2.1.28. Found by "doorss".
12984 - Bring the logic that gathers routerinfos and assesses the
12985 acceptability of circuits into line. This prevents a Tor OP from
12986 getting locked in a cycle of choosing its local OR as an exit for a
12987 path (due to a .exit request) and then rejecting the circuit because
12988 its OR is not listed yet. It also prevents Tor clients from using an
12989 OR running in the same instance as an exit (due to a .exit request)
12990 if the OR does not meet the same requirements expected of an OR
12991 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
12993 o Packaging changes:
12994 - Stop shipping the Tor specs files and development proposal documents
12995 in the tarball. They are now in a separate git repository at
12996 git://git.torproject.org/torspec.git
12997 - Do not include Git version tags as though they are SVN tags when
12998 generating a tarball from inside a repository that has switched
12999 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
13002 Changes in version 0.2.2.22-alpha - 2011-01-25
13003 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
13004 main other change is a slight tweak to Tor's TLS handshake that makes
13005 relays and bridges that run this new version reachable from Iran again.
13006 We don't expect this tweak will win the arms race long-term, but it
13007 will buy us a bit more time until we roll out a better solution.
13010 - Fix a bounds-checking error that could allow an attacker to
13011 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
13012 Found by "piebeer".
13013 - Don't assert when changing from bridge to relay or vice versa
13014 via the controller. The assert happened because we didn't properly
13015 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
13016 bug 2433. Reported by bastik.
13019 - Adjust our TLS Diffie-Hellman parameters to match those used by
13021 - Provide a log message stating which geoip file we're parsing
13022 instead of just stating that we're parsing the geoip file.
13023 Implements ticket 2432.
13026 - Check for and reject overly long directory certificates and
13027 directory tokens before they have a chance to hit any assertions.
13028 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
13031 Changes in version 0.2.2.21-alpha - 2011-01-15
13032 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
13033 continues our recent code security audit work. The main fix resolves
13034 a remote heap overflow vulnerability that can allow remote code
13035 execution (CVE-2011-0427). Other fixes address a variety of assert
13036 and crash bugs, most of which we think are hard to exploit remotely.
13038 o Major bugfixes (security), also included in 0.2.1.29:
13039 - Fix a heap overflow bug where an adversary could cause heap
13040 corruption. This bug probably allows remote code execution
13041 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
13043 - Prevent a denial-of-service attack by disallowing any
13044 zlib-compressed data whose compression factor is implausibly
13045 high. Fixes part of bug 2324; reported by "doorss".
13046 - Zero out a few more keys in memory before freeing them. Fixes
13047 bug 2384 and part of bug 2385. These key instances found by
13048 "cypherpunks", based on Andrew Case's report about being able
13049 to find sensitive data in Tor's memory space if you have enough
13050 permissions. Bugfix on 0.0.2pre9.
13052 o Major bugfixes (crashes), also included in 0.2.1.29:
13053 - Prevent calls to Libevent from inside Libevent log handlers.
13054 This had potential to cause a nasty set of crashes, especially
13055 if running Libevent with debug logging enabled, and running
13056 Tor with a controller watching for low-severity log messages.
13057 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
13058 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
13059 underflow errors there too. Fixes the other part of bug 2324.
13060 - Fix a bug where we would assert if we ever had a
13061 cached-descriptors.new file (or another file read directly into
13062 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
13063 on 0.2.1.25. Found by doorss.
13064 - Fix some potential asserts and parsing issues with grossly
13065 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
13068 o Minor bugfixes (other), also included in 0.2.1.29:
13069 - Fix a bug with handling misformed replies to reverse DNS lookup
13070 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
13071 bug reported by doorss.
13072 - Fix compilation on mingw when a pthreads compatibility library
13073 has been installed. (We don't want to use it, so we shouldn't
13074 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
13075 - Fix a bug where we would declare that we had run out of virtual
13076 addresses when the address space was only half-exhausted. Bugfix
13078 - Correctly handle the case where AutomapHostsOnResolve is set but
13079 no virtual addresses are available. Fixes bug 2328; bugfix on
13080 0.1.2.1-alpha. Bug found by doorss.
13081 - Correctly handle wrapping around when we run out of virtual
13082 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
13084 o Minor features, also included in 0.2.1.29:
13085 - Update to the January 1 2011 Maxmind GeoLite Country database.
13086 - Introduce output size checks on all of our decryption functions.
13088 o Build changes, also included in 0.2.1.29:
13089 - Tor does not build packages correctly with Automake 1.6 and earlier;
13090 added a check to Makefile.am to make sure that we're building with
13091 Automake 1.7 or later.
13092 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
13093 because we built it with a too-old version of automake. Thus that
13094 release broke ./configure --enable-openbsd-malloc, which is popular
13095 among really fast exit relays on Linux.
13097 o Major bugfixes, new in 0.2.2.21-alpha:
13098 - Prevent crash/heap corruption when the cbtnummodes consensus
13099 parameter is set to 0 or large values. Fixes bug 2317; bugfix
13102 o Major features, new in 0.2.2.21-alpha:
13103 - Introduce minimum/maximum values that clients will believe
13104 from the consensus. Now we'll have a better chance to avoid crashes
13105 or worse when a consensus param has a weird value.
13107 o Minor features, new in 0.2.2.21-alpha:
13108 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
13109 used on bridges, and it makes bridge scanning somewhat easier.
13110 - If writing the state file to disk fails, wait up to an hour before
13111 retrying again, rather than trying again each second. Fixes bug
13112 2346; bugfix on Tor 0.1.1.3-alpha.
13113 - Make Libevent log messages get delivered to controllers later,
13114 and not from inside the Libevent log handler. This prevents unsafe
13115 reentrant Libevent calls while still letting the log messages
13117 - Detect platforms that brokenly use a signed size_t, and refuse to
13118 build there. Found and analyzed by doorss and rransom.
13119 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
13122 o Minor bugfixes, new in 0.2.2.21-alpha:
13123 - Handle SOCKS messages longer than 128 bytes long correctly, rather
13124 than waiting forever for them to finish. Fixes bug 2330; bugfix
13125 on 0.2.0.16-alpha. Found by doorss.
13126 - Add assertions to check for overflow in arguments to
13127 base32_encode() and base32_decode(); fix a signed-unsigned
13128 comparison there too. These bugs are not actually reachable in Tor,
13129 but it's good to prevent future errors too. Found by doorss.
13130 - Correctly detect failures to create DNS requests when using Libevent
13131 versions before v2. (Before Libevent 2, we used our own evdns
13132 implementation. Its return values for Libevent's evdns_resolve_*()
13133 functions are not consistent with those from Libevent.) Fixes bug
13134 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
13136 o Documentation, new in 0.2.2.21-alpha:
13137 - Document the default socks host and port (127.0.0.1:9050) for
13141 Changes in version 0.2.1.29 - 2011-01-15
13142 Tor 0.2.1.29 continues our recent code security audit work. The main
13143 fix resolves a remote heap overflow vulnerability that can allow remote
13144 code execution. Other fixes address a variety of assert and crash bugs,
13145 most of which we think are hard to exploit remotely.
13147 o Major bugfixes (security):
13148 - Fix a heap overflow bug where an adversary could cause heap
13149 corruption. This bug probably allows remote code execution
13150 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
13152 - Prevent a denial-of-service attack by disallowing any
13153 zlib-compressed data whose compression factor is implausibly
13154 high. Fixes part of bug 2324; reported by "doorss".
13155 - Zero out a few more keys in memory before freeing them. Fixes
13156 bug 2384 and part of bug 2385. These key instances found by
13157 "cypherpunks", based on Andrew Case's report about being able
13158 to find sensitive data in Tor's memory space if you have enough
13159 permissions. Bugfix on 0.0.2pre9.
13161 o Major bugfixes (crashes):
13162 - Prevent calls to Libevent from inside Libevent log handlers.
13163 This had potential to cause a nasty set of crashes, especially
13164 if running Libevent with debug logging enabled, and running
13165 Tor with a controller watching for low-severity log messages.
13166 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
13167 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
13168 underflow errors there too. Fixes the other part of bug 2324.
13169 - Fix a bug where we would assert if we ever had a
13170 cached-descriptors.new file (or another file read directly into
13171 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
13172 on 0.2.1.25. Found by doorss.
13173 - Fix some potential asserts and parsing issues with grossly
13174 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
13177 o Minor bugfixes (other):
13178 - Fix a bug with handling misformed replies to reverse DNS lookup
13179 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
13180 bug reported by doorss.
13181 - Fix compilation on mingw when a pthreads compatibility library
13182 has been installed. (We don't want to use it, so we shouldn't
13183 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
13184 - Fix a bug where we would declare that we had run out of virtual
13185 addresses when the address space was only half-exhausted. Bugfix
13187 - Correctly handle the case where AutomapHostsOnResolve is set but
13188 no virtual addresses are available. Fixes bug 2328; bugfix on
13189 0.1.2.1-alpha. Bug found by doorss.
13190 - Correctly handle wrapping around to when we run out of virtual
13191 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
13192 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
13193 because we built it with a too-old version of automake. Thus that
13194 release broke ./configure --enable-openbsd-malloc, which is popular
13195 among really fast exit relays on Linux.
13198 - Update to the January 1 2011 Maxmind GeoLite Country database.
13199 - Introduce output size checks on all of our decryption functions.
13202 - Tor does not build packages correctly with Automake 1.6 and earlier;
13203 added a check to Makefile.am to make sure that we're building with
13204 Automake 1.7 or later.
13207 Changes in version 0.2.2.20-alpha - 2010-12-17
13208 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
13209 exploitable bugs. We also fix a variety of other significant bugs,
13210 change the IP address for one of our directory authorities, and update
13211 the minimum version that Tor relays must run to join the network.
13214 - Fix a remotely exploitable bug that could be used to crash instances
13215 of Tor remotely by overflowing on the heap. Remote-code execution
13216 hasn't been confirmed, but can't be ruled out. Everyone should
13217 upgrade. Bugfix on the 0.1.1 series and later.
13218 - Fix a bug that could break accounting on 64-bit systems with large
13219 time_t values, making them hibernate for impossibly long intervals.
13220 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
13221 - Fix a logic error in directory_fetches_from_authorities() that
13222 would cause all _non_-exits refusing single-hop-like circuits
13223 to fetch from authorities, when we wanted to have _exits_ fetch
13224 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
13226 - Fix a stream fairness bug that would cause newer streams on a given
13227 circuit to get preference when reading bytes from the origin or
13228 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
13229 introduced before the first Tor release, in svn revision r152.
13231 o Directory authority changes:
13232 - Change IP address and ports for gabelmoo (v3 directory authority).
13235 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
13236 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
13237 - Fix an off-by-one error in calculating some controller command
13238 argument lengths. Fortunately, this mistake is harmless since
13239 the controller code does redundant NUL termination too. Found by
13240 boboper. Bugfix on 0.1.1.1-alpha.
13241 - Do not dereference NULL if a bridge fails to build its
13242 extra-info descriptor. Found by an anonymous commenter on
13243 Trac. Bugfix on 0.2.2.19-alpha.
13246 - Update to the December 1 2010 Maxmind GeoLite Country database.
13247 - Directory authorities now reject relays running any versions of
13248 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
13249 known bugs that keep RELAY_EARLY cells from working on rendezvous
13250 circuits. Followup to fix for bug 2081.
13251 - Directory authorities now reject relays running any version of Tor
13252 older than 0.2.0.26-rc. That version is the earliest that fetches
13253 current directory information correctly. Fixes bug 2156.
13254 - Report only the top 10 ports in exit-port stats in order not to
13255 exceed the maximum extra-info descriptor length of 50 KB. Implements
13259 Changes in version 0.2.1.28 - 2010-12-17
13260 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
13261 exploitable bugs. We also took this opportunity to change the IP address
13262 for one of our directory authorities, and to update the geoip database
13266 - Fix a remotely exploitable bug that could be used to crash instances
13267 of Tor remotely by overflowing on the heap. Remote-code execution
13268 hasn't been confirmed, but can't be ruled out. Everyone should
13269 upgrade. Bugfix on the 0.1.1 series and later.
13271 o Directory authority changes:
13272 - Change IP address and ports for gabelmoo (v3 directory authority).
13275 - Update to the December 1 2010 Maxmind GeoLite Country database.
13278 Changes in version 0.2.1.27 - 2010-11-23
13279 Yet another OpenSSL security patch broke its compatibility with Tor:
13280 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
13281 also took this opportunity to fix several crash bugs, integrate a new
13282 directory authority, and update the bundled GeoIP database.
13285 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
13286 No longer set the tlsext_host_name extension on server SSL objects;
13287 but continue to set it on client SSL objects. Our goal in setting
13288 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
13289 bugfix on 0.2.1.1-alpha.
13290 - Do not log messages to the controller while shrinking buffer
13291 freelists. Doing so would sometimes make the controller connection
13292 try to allocate a buffer chunk, which would mess up the internals
13293 of the freelist and cause an assertion failure. Fixes bug 1125;
13294 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
13295 - Learn our external IP address when we're a relay or bridge, even if
13296 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
13297 where we introduced bridge relays that don't need to publish to
13298 be useful. Fixes bug 2050.
13299 - Do even more to reject (and not just ignore) annotations on
13300 router descriptors received anywhere but from the cache. Previously
13301 we would ignore such annotations at first, but cache them to disk
13302 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
13303 - When you're using bridges and your network goes away and your
13304 bridges get marked as down, recover when you attempt a new socks
13305 connection (if the network is back), rather than waiting up to an
13306 hour to try fetching new descriptors for your bridges. Bugfix on
13307 0.2.0.3-alpha; fixes bug 1981.
13310 - Move to the November 2010 Maxmind GeoLite country db (rather
13311 than the June 2009 ip-to-country GeoIP db) for our statistics that
13312 count how many users relays are seeing from each country. Now we'll
13313 have more accurate data, especially for many African countries.
13315 o New directory authorities:
13316 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
13320 - Fix an assertion failure that could occur in directory caches or
13321 bridge users when using a very short voting interval on a testing
13322 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
13324 - Enforce multiplicity rules when parsing annotations. Bugfix on
13325 0.2.0.8-alpha. Found by piebeer.
13326 - Allow handshaking OR connections to take a full KeepalivePeriod
13327 seconds to handshake. Previously, we would close them after
13328 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
13329 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
13331 - When building with --enable-gcc-warnings on OpenBSD, disable
13332 warnings in system headers. This makes --enable-gcc-warnings
13333 pass on OpenBSD 4.8.
13336 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
13337 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
13338 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
13339 Servers can start sending this code when enough clients recognize
13340 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
13341 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
13342 Patch from mingw-san.
13345 - Remove the old debian/ directory from the main Tor distribution.
13346 The official Tor-for-debian git repository lives at the URL
13347 https://git.torproject.org/debian/tor.git
13348 - Stop shipping the old doc/website/ directory in the tarball. We
13349 changed the website format in late 2010, and what we shipped in
13350 0.2.1.26 really wasn't that useful anyway.
13353 Changes in version 0.2.2.19-alpha - 2010-11-22
13354 Yet another OpenSSL security patch broke its compatibility with Tor:
13355 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
13358 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
13359 No longer set the tlsext_host_name extension on server SSL objects;
13360 but continue to set it on client SSL objects. Our goal in setting
13361 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
13362 bugfix on 0.2.1.1-alpha.
13365 - Try harder not to exceed the maximum length of 50 KB when writing
13366 statistics to extra-info descriptors. This bug was triggered by very
13367 fast relays reporting exit-port, entry, and dirreq statistics.
13368 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
13369 - Publish a router descriptor even if generating an extra-info
13370 descriptor fails. Previously we would not publish a router
13371 descriptor without an extra-info descriptor; this can cause fast
13372 exit relays collecting exit-port statistics to drop from the
13373 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
13376 Changes in version 0.2.2.18-alpha - 2010-11-16
13377 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
13378 us lately, makes unpublished bridge relays able to detect their IP
13379 address, and fixes a wide variety of other bugs to get us much closer
13380 to a stable release.
13383 - Do even more to reject (and not just ignore) annotations on
13384 router descriptors received anywhere but from the cache. Previously
13385 we would ignore such annotations at first, but cache them to disk
13386 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
13387 - Do not log messages to the controller while shrinking buffer
13388 freelists. Doing so would sometimes make the controller connection
13389 try to allocate a buffer chunk, which would mess up the internals
13390 of the freelist and cause an assertion failure. Fixes bug 1125;
13391 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
13392 - Learn our external IP address when we're a relay or bridge, even if
13393 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
13394 where we introduced bridge relays that don't need to publish to
13395 be useful. Fixes bug 2050.
13396 - Maintain separate TLS contexts and certificates for incoming and
13397 outgoing connections in bridge relays. Previously we would use the
13398 same TLS contexts and certs for incoming and outgoing connections.
13399 Bugfix on 0.2.0.3-alpha; addresses bug 988.
13400 - Maintain separate identity keys for incoming and outgoing TLS
13401 contexts in bridge relays. Previously we would use the same
13402 identity keys for incoming and outgoing TLS contexts. Bugfix on
13403 0.2.0.3-alpha; addresses the other half of bug 988.
13404 - Avoid an assertion failure when we as an authority receive a
13405 duplicate upload of a router descriptor that we already have,
13406 but which we previously considered an obsolete descriptor.
13407 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
13408 - Avoid a crash bug triggered by looking at a dangling pointer while
13409 setting the network status consensus. Found by Robert Ransom.
13410 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
13411 - Fix a logic error where servers that _didn't_ act as exits would
13412 try to keep their server lists more aggressively up to date than
13413 exits, when it was supposed to be the other way around. Bugfix
13416 o Minor bugfixes (on Tor 0.2.1.x and earlier):
13417 - When we're trying to guess whether we know our IP address as
13418 a relay, we would log various ways that we failed to guess
13419 our address, but never log that we ended up guessing it
13420 successfully. Now add a log line to help confused and anxious
13421 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
13422 - Bring the logic that gathers routerinfos and assesses the
13423 acceptability of circuits into line. This prevents a Tor OP from
13424 getting locked in a cycle of choosing its local OR as an exit for a
13425 path (due to a .exit request) and then rejecting the circuit because
13426 its OR is not listed yet. It also prevents Tor clients from using an
13427 OR running in the same instance as an exit (due to a .exit request)
13428 if the OR does not meet the same requirements expected of an OR
13429 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
13430 - Correctly describe errors that occur when generating a TLS object.
13431 Previously we would attribute them to a failure while generating a
13432 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
13434 - Enforce multiplicity rules when parsing annotations. Bugfix on
13435 0.2.0.8-alpha. Found by piebeer.
13436 - Fix warnings that newer versions of autoconf produced during
13437 ./autogen.sh. These warnings appear to be harmless in our case,
13438 but they were extremely verbose. Fixes bug 2020.
13440 o Minor bugfixes (on Tor 0.2.2.x):
13441 - Enable protection of small arrays whenever we build with gcc
13442 hardening features, not only when also building with warnings
13443 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
13446 - Make hidden services work better in private Tor networks by not
13447 requiring any uptime to join the hidden service descriptor
13448 DHT. Implements ticket 2088.
13449 - Rate-limit the "your application is giving Tor only an IP address"
13450 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
13451 - When AllowSingleHopExits is set, print a warning to explain to the
13452 relay operator why most clients are avoiding her relay.
13453 - Update to the November 1 2010 Maxmind GeoLite Country database.
13455 o Code simplifications and refactoring:
13456 - When we fixed bug 1038 we had to put in a restriction not to send
13457 RELAY_EARLY cells on rend circuits. This was necessary as long
13458 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
13459 active. Now remove this obsolete check. Resolves bug 2081.
13460 - Some options used different conventions for uppercasing of acronyms
13461 when comparing manpage and source. Fix those in favor of the
13462 manpage, as it makes sense to capitalize acronyms.
13463 - Remove the torrc.complete file. It hasn't been kept up to date
13464 and users will have better luck checking out the manpage.
13465 - Remove the obsolete "NoPublish" option; it has been flagged
13466 as obsolete and has produced a warning since 0.1.1.18-rc.
13467 - Remove everything related to building the expert bundle for OS X.
13468 It has confused many users, doesn't work right on OS X 10.6,
13469 and is hard to get rid of once installed. Resolves bug 1274.
13472 Changes in version 0.2.2.17-alpha - 2010-09-30
13473 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
13474 to use one-hop circuits (which can put the exit relays at higher risk,
13475 plus unbalance the network); fixes a big bug in bandwidth accounting
13476 for relays that want to limit their monthly bandwidth use; fixes a
13477 big pile of bugs in how clients tolerate temporary network failure;
13478 and makes our adaptive circuit build timeout feature (which improves
13479 client performance if your network is fast while not breaking things
13480 if your network is slow) better handle bad networks.
13483 - Exit relays now try harder to block exit attempts from unknown
13484 relays, to make it harder for people to use them as one-hop proxies
13485 a la tortunnel. Controlled by the refuseunknownexits consensus
13486 parameter (currently enabled), or you can override it on your
13487 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
13489 o Major bugfixes (0.2.1.x and earlier):
13490 - Fix a bug in bandwidth accounting that could make us use twice
13491 the intended bandwidth when our interval start changes due to
13492 daylight saving time. Now we tolerate skew in stored vs computed
13493 interval starts: if the start of the period changes by no more than
13494 50% of the period's duration, we remember bytes that we transferred
13495 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
13496 - Always search the Windows system directory for system DLLs, and
13497 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
13498 - When you're using bridges and your network goes away and your
13499 bridges get marked as down, recover when you attempt a new socks
13500 connection (if the network is back), rather than waiting up to an
13501 hour to try fetching new descriptors for your bridges. Bugfix on
13502 0.2.0.3-alpha; fixes bug 1981.
13504 o Major bugfixes (on 0.2.2.x):
13505 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
13507 - Fix a segfault that could happen when operating a bridge relay with
13508 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
13509 - The consensus bandwidth-weights (used by clients to choose fast
13510 relays) entered an unexpected edge case in September where
13511 Exits were much scarcer than Guards, resulting in bad weight
13512 recommendations. Now we compute them using new constraints that
13513 should succeed in all cases. Also alter directory authorities to
13514 not include the bandwidth-weights line if they fail to produce
13515 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
13516 - When weighting bridges during path selection, we used to trust
13517 the bandwidths they provided in their descriptor, only capping them
13518 at 10MB/s. This turned out to be problematic for two reasons:
13519 Bridges could claim to handle a lot more traffic then they
13520 actually would, thus making more clients pick them and have a
13521 pretty effective DoS attack. The other issue is that new bridges
13522 that might not have a good estimate for their bw capacity yet
13523 would not get used at all unless no other bridges are available
13524 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
13526 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
13527 - Ignore cannibalized circuits when recording circuit build times.
13528 This should provide for a minor performance improvement for hidden
13529 service users using 0.2.2.14-alpha, and should remove two spurious
13530 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
13531 - Simplify the logic that causes us to decide if the network is
13532 unavailable for purposes of recording circuit build times. If we
13533 receive no cells whatsoever for the entire duration of a circuit's
13534 full measured lifetime, the network is probably down. Also ignore
13535 one-hop directory fetching circuit timeouts when calculating our
13536 circuit build times. These changes should hopefully reduce the
13537 cases where we see ridiculous circuit build timeouts for people
13538 with spotty wireless connections. Fixes part of bug 1772; bugfix
13540 - Prevent the circuit build timeout from becoming larger than
13541 the maximum build time we have ever seen. Also, prevent the time
13542 period for measurement circuits from becoming larger than twice that
13543 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
13546 - When we run out of directory information such that we can't build
13547 circuits, but then get enough that we can build circuits, log when
13548 we actually construct a circuit, so the user has a better chance of
13549 knowing what's going on. Fixes bug 1362.
13550 - Be more generous with how much bandwidth we'd use up (with
13551 accounting enabled) before entering "soft hibernation". Previously,
13552 we'd refuse new connections and circuits once we'd used up 95% of
13553 our allotment. Now, we use up 95% of our allotment, AND make sure
13554 that we have no more than 500MB (or 3 hours of expected traffic,
13555 whichever is lower) remaining before we enter soft hibernation.
13556 - If we've configured EntryNodes and our network goes away and/or all
13557 our entrynodes get marked down, optimistically retry them all when
13558 a new socks application request appears. Fixes bug 1882.
13559 - Add some more defensive programming for architectures that can't
13560 handle unaligned integer accesses. We don't know of any actual bugs
13561 right now, but that's the best time to fix them. Fixes bug 1943.
13562 - Support line continuations in the torrc config file. If a line
13563 ends with a single backslash character, the newline is ignored, and
13564 the configuration value is treated as continuing on the next line.
13567 o Minor bugfixes (on 0.2.1.x and earlier):
13568 - For bandwidth accounting, calculate our expected bandwidth rate
13569 based on the time during which we were active and not in
13570 soft-hibernation during the last interval. Previously, we were
13571 also considering the time spent in soft-hibernation. If this
13572 was a long time, we would wind up underestimating our bandwidth
13573 by a lot, and skewing our wakeup time towards the start of the
13574 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
13576 o Minor bugfixes (on 0.2.2.x):
13577 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
13578 which were disabled by the circuit build timeout changes in
13579 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
13580 - Make sure we don't warn about missing bandwidth weights when
13581 choosing bridges or other relays not in the consensus. Bugfix on
13582 0.2.2.10-alpha; fixes bug 1805.
13583 - In our logs, do not double-report signatures from unrecognized
13584 authorities both as "from unknown authority" and "not
13585 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
13588 Changes in version 0.2.2.16-alpha - 2010-09-17
13589 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
13590 evident at exit relays), and also continues to resolve all the little
13591 bugs that have been filling up trac lately.
13593 o Major bugfixes (stream-level fairness):
13594 - When receiving a circuit-level SENDME for a blocked circuit, try
13595 to package cells fairly from all the streams that had previously
13596 been blocked on that circuit. Previously, we had started with the
13597 oldest stream, and allowed each stream to potentially exhaust
13598 the circuit's package window. This gave older streams on any
13599 given circuit priority over newer ones. Fixes bug 1937. Detected
13600 originally by Camilo Viecco. This bug was introduced before the
13601 first Tor release, in svn commit r152: it is the new winner of
13602 the longest-lived bug prize.
13603 - When the exit relay got a circuit-level sendme cell, it started
13604 reading on the exit streams, even if had 500 cells queued in the
13605 circuit queue already, so the circuit queue just grew and grew in
13606 some cases. We fix this by not re-enabling reading on receipt of a
13607 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
13608 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
13610 - Newly created streams were allowed to read cells onto circuits,
13611 even if the circuit's cell queue was blocked and waiting to drain.
13612 This created potential unfairness, as older streams would be
13613 blocked, but newer streams would gladly fill the queue completely.
13614 We add code to detect this situation and prevent any stream from
13615 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
13619 - Update to the September 1 2010 Maxmind GeoLite Country database.
13620 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
13621 not. This would lead to a cookie that is still not group readable.
13622 Closes bug 1843. Suggested by katmagic.
13623 - When logging a rate-limited warning, we now mention how many messages
13624 got suppressed since the last warning.
13625 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
13626 do individual connection-level rate limiting of clients. The torrc
13627 config options with the same names trump the consensus params, if
13628 both are present. Replaces the old "bwconnrate" and "bwconnburst"
13629 consensus params which were broken from 0.2.2.7-alpha through
13630 0.2.2.14-alpha. Closes bug 1947.
13631 - When a router changes IP address or port, authorities now launch
13632 a new reachability test for it. Implements ticket 1899.
13633 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
13634 2 no signature, 4 required" messages about consensus signatures
13635 easier to read, and make sure they get logged at the same severity
13636 as the messages explaining which keys are which. Fixes bug 1290.
13637 - Don't warn when we have a consensus that we can't verify because
13638 of missing certificates, unless those certificates are ones
13639 that we have been trying and failing to download. Fixes bug 1145.
13640 - If you configure your bridge with a known identity fingerprint,
13641 and the bridge authority is unreachable (as it is in at least
13642 one country now), fall back to directly requesting the descriptor
13643 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
13645 - When building with --enable-gcc-warnings on OpenBSD, disable
13646 warnings in system headers. This makes --enable-gcc-warnings
13647 pass on OpenBSD 4.8.
13649 o Minor bugfixes (on 0.2.1.x and earlier):
13650 - Authorities will now attempt to download consensuses if their
13651 own efforts to make a live consensus have failed. This change
13652 means authorities that restart will fetch a valid consensus, and
13653 it means authorities that didn't agree with the current consensus
13654 will still fetch and serve it if it has enough signatures. Bugfix
13655 on 0.2.0.9-alpha; fixes bug 1300.
13656 - Ensure DNS requests launched by "RESOLVE" commands from the
13657 controller respect the __LeaveStreamsUnattached setconf options. The
13658 same goes for requests launched via DNSPort or transparent
13659 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
13660 - Allow handshaking OR connections to take a full KeepalivePeriod
13661 seconds to handshake. Previously, we would close them after
13662 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
13663 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
13665 - Rate-limit "Failed to hand off onionskin" warnings.
13666 - Never relay a cell for a circuit we have already destroyed.
13667 Between marking a circuit as closeable and finally closing it,
13668 it may have been possible for a few queued cells to get relayed,
13669 even though they would have been immediately dropped by the next
13670 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
13671 - Never queue a cell for a circuit that's already been marked
13673 - Never vote for a server as "Running" if we have a descriptor for
13674 it claiming to be hibernating, and that descriptor was published
13675 more recently than our last contact with the server. Bugfix on
13676 0.2.0.3-alpha; fixes bug 911.
13677 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
13680 o Minor bugfixes (on 0.2.2.x):
13681 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
13682 down if a directory fetch fails and you've configured either
13683 bridges or EntryNodes. The intent was to mark the relay as down
13684 _unless_ you're using bridges or EntryNodes, since if you are
13685 then you could quickly run out of entry points.
13686 - Fix the Windows directory-listing code. A bug introduced in
13687 0.2.2.14-alpha could make Windows directory servers forget to load
13688 some of their cached v2 networkstatus files.
13689 - Really allow clients to use relays as bridges. Fixes bug 1776;
13690 bugfix on 0.2.2.15-alpha.
13691 - Demote a warn to info that happens when the CellStatistics option
13692 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
13693 Reported by Moritz Bartl.
13694 - On Windows, build correctly either with or without Unicode support.
13695 This is necessary so that Tor can support fringe platforms like
13696 Windows 98 (which has no Unicode), or Windows CE (which has no
13697 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
13700 - Add a unit test for cross-platform directory-listing code.
13703 Changes in version 0.2.2.15-alpha - 2010-08-18
13704 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
13705 fixes a variety of other bugs that were preventing performance
13706 experiments from moving forward, fixes several bothersome memory leaks,
13707 and generally closes a lot of smaller bugs that have been filling up
13711 - Stop assigning the HSDir flag to relays that disable their
13712 DirPort (and thus will refuse to answer directory requests). This
13713 fix should dramatically improve the reachability of hidden services:
13714 hidden services and hidden service clients pick six HSDir relays
13715 to store and retrieve the hidden service descriptor, and currently
13716 about half of the HSDir relays will refuse to work. Bugfix on
13717 0.2.0.10-alpha; fixes part of bug 1693.
13718 - The PerConnBWRate and Burst config options, along with the
13719 bwconnrate and bwconnburst consensus params, initialized each conn's
13720 token bucket values only when the connection is established. Now we
13721 update them if the config options change, and update them every time
13722 we get a new consensus. Otherwise we can encounter an ugly edge
13723 case where we initialize an OR conn to client-level bandwidth,
13724 but then later the relay joins the consensus and we leave it
13725 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
13726 - Fix a regression that caused Tor to rebind its ports if it receives
13727 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
13730 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
13731 should give us approximately 40-50% more Guard-flagged nodes,
13732 improving the anonymity the Tor network can provide and also
13733 decreasing the dropoff in throughput that relays experience when
13734 they first get the Guard flag.
13735 - Allow enabling or disabling the *Statistics config options while
13739 - Update to the August 1 2010 Maxmind GeoLite Country database.
13740 - Have the controller interface give a more useful message than
13741 "Internal Error" in response to failed GETINFO requests.
13742 - Warn when the same option is provided more than once in a torrc
13743 file, on the command line, or in a single SETCONF statement, and
13744 the option is one that only accepts a single line. Closes bug 1384.
13745 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
13746 Patch from mingw-san.
13747 - Add support for the country code "{??}" in torrc options like
13748 ExcludeNodes, to indicate all routers of unknown country. Closes
13750 - Relays report the number of bytes spent on answering directory
13751 requests in extra-info descriptors similar to {read,write}-history.
13752 Implements enhancement 1790.
13754 o Minor bugfixes (on 0.2.1.x and earlier):
13755 - Complain if PublishServerDescriptor is given multiple arguments that
13756 include 0 or 1. This configuration will be rejected in the future.
13757 Bugfix on 0.2.0.1-alpha; closes bug 1107.
13758 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
13759 Bugfix on 0.2.0.13-alpha; closes bug 928.
13760 - Change "Application request when we're believed to be offline."
13761 notice to "Application request when we haven't used client
13762 functionality lately.", to clarify that it's not an error. Bugfix
13763 on 0.0.9.3; fixes bug 1222.
13764 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
13765 would return "551 Internal error" rather than "552 Unrecognized key
13766 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
13767 - Users can't configure a regular relay to be their bridge. It didn't
13768 work because when Tor fetched the bridge descriptor, it found
13769 that it already had it, and didn't realize that the purpose of the
13770 descriptor had changed. Now we replace routers with a purpose other
13771 than bridge with bridge descriptors when fetching them. Bugfix on
13772 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
13773 refetch the descriptor with router purpose 'general', disabling
13775 - Fix a rare bug in rend_fn unit tests: we would fail a test when
13776 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
13777 on 0.2.0.10-alpha; fixes bug 1808.
13778 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
13779 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
13780 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
13781 Servers can start sending this code when enough clients recognize
13782 it. Also update the spec to reflect this new reason. Bugfix on
13783 0.1.0.1-rc; fixes part of bug 1793.
13784 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
13785 when we switch from being a public relay to a bridge. Otherwise
13786 there will still be clients that see the relay in their consensus,
13787 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
13789 - Instead of giving an assertion failure on an internal mismatch
13790 on estimated freelist size, just log a BUG warning and try later.
13791 Mitigates but does not fix bug 1125.
13792 - Fix an assertion failure that could occur in caches or bridge users
13793 when using a very short voting interval on a testing network.
13794 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
13796 o Minor bugfixes (on 0.2.2.x):
13797 - Alter directory authorities to always consider Exit-flagged nodes
13798 as potential Guard nodes in their votes. The actual decision to
13799 use Exits as Guards is done in the consensus bandwidth weights.
13800 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
13801 - When the controller is reporting the purpose of circuits that
13802 didn't finish building before the circuit build timeout, it was
13803 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
13804 - Our libevent version parsing code couldn't handle versions like
13805 1.4.14b-stable and incorrectly warned the user about using an
13806 old and broken version of libevent. Treat 1.4.14b-stable like
13807 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
13809 - Don't use substitution references like $(VAR:MOD) when
13810 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
13811 '$(:x)' to 'x' rather than the empty string. This bites us in
13812 doc/ when configured with --disable-asciidoc. Bugfix on
13813 0.2.2.9-alpha; fixes bug 1773.
13814 - Remove a spurious hidden service server-side log notice about
13815 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
13817 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
13819 - Correctly report written bytes on linked connections. Found while
13820 implementing 1790. Bugfix on 0.2.2.4-alpha.
13821 - Fix three memory leaks: one in circuit_build_times_parse_state(),
13822 one in dirvote_add_signatures_to_pending_consensus(), and one every
13823 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
13824 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
13826 o Code simplifications and refactoring:
13827 - Take a first step towards making or.h smaller by splitting out
13828 function definitions for all source files in src/or/. Leave
13829 structures and defines in or.h for now.
13830 - Remove a bunch of unused function declarations as well as a block of
13831 #if 0'd code from the unit tests. Closes bug 1824.
13832 - New unit tests for exit-port history statistics; refactored exit
13833 statistics code to be more easily tested.
13834 - Remove the old debian/ directory from the main Tor distribution.
13835 The official Tor-for-debian git repository lives at the URL
13836 https://git.torproject.org/debian/tor.git
13839 Changes in version 0.2.2.14-alpha - 2010-07-12
13840 Tor 0.2.2.14-alpha greatly improves client-side handling of
13841 circuit build timeouts, which are used to estimate speed and improve
13842 performance. We also move to a much better GeoIP database, port Tor to
13843 Windows CE, introduce new compile flags that improve code security,
13844 add an eighth v3 directory authority, and address a lot of more
13848 - Tor directory authorities no longer crash when started with a
13849 cached-microdesc-consensus file in their data directory. Bugfix
13850 on 0.2.2.6-alpha; fixes bug 1532.
13851 - Treat an unset $HOME like an empty $HOME rather than triggering an
13852 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
13853 - Ignore negative and large circuit build timeout values that can
13854 happen during a suspend or hibernate. These values caused various
13855 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
13856 - Alter calculation of Pareto distribution parameter 'Xm' for
13857 Circuit Build Timeout learning to use the weighted average of the
13858 top N=3 modes (because we have three entry guards). Considering
13859 multiple modes should improve the timeout calculation in some cases,
13860 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
13862 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
13863 right censored distribution model. This approach improves over the
13864 synthetic timeout generation approach that was producing insanely
13865 high timeout values. Now we calculate build timeouts using truncated
13866 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
13867 - Do not close circuits that are under construction when they reach
13868 the circuit build timeout. Instead, leave them building (but do not
13869 use them) for up until the time corresponding to the 95th percentile
13870 on the Pareto CDF or 60 seconds, whichever is greater. This is done
13871 to provide better data for the new Pareto model. This percentile
13872 can be controlled by the consensus.
13875 - Move to the June 2010 Maxmind GeoLite country db (rather than the
13876 June 2009 ip-to-country GeoIP db) for our statistics that count
13877 how many users relays are seeing from each country. Now we have
13878 more accurate data for many African countries.
13879 - Port Tor to build and run correctly on Windows CE systems, using
13880 the wcecompat library. Contributed by Valerio Lupi.
13881 - New "--enable-gcc-hardening" ./configure flag (off by default)
13882 to turn on gcc compile time hardening options. It ensures
13883 that signed ints have defined behavior (-fwrapv), enables
13884 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
13885 with canaries (-fstack-protector-all), turns on ASLR protection if
13886 supported by the kernel (-fPIE, -pie), and adds additional security
13887 related warnings. Verified to work on Mac OS X and Debian Lenny.
13888 - New "--enable-linker-hardening" ./configure flag (off by default)
13889 to turn on ELF specific hardening features (relro, now). This does
13890 not work with Mac OS X or any other non-ELF binary format.
13892 o New directory authorities:
13893 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
13897 - New config option "WarnUnsafeSocks 0" disables the warning that
13898 occurs whenever Tor receives a socks handshake using a version of
13899 the socks protocol that can only provide an IP address (rather
13900 than a hostname). Setups that do DNS locally over Tor are fine,
13901 and we shouldn't spam the logs in that case.
13902 - Convert the HACKING file to asciidoc, and add a few new sections
13903 to it, explaining how we use Git, how we make changelogs, and
13904 what should go in a patch.
13905 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
13906 event, to give information on the current rate of circuit timeouts
13907 over our stored history.
13908 - Add ability to disable circuit build time learning via consensus
13909 parameter and via a LearnCircuitBuildTimeout config option. Also
13910 automatically disable circuit build time calculation if we are
13911 either a AuthoritativeDirectory, or if we fail to write our state
13912 file. Fixes bug 1296.
13913 - More gracefully handle corrupt state files, removing asserts
13914 in favor of saving a backup and resetting state.
13915 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
13919 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
13921 - When a2x fails, mention that the user could disable manpages instead
13922 of trying to fix their asciidoc installation.
13923 - Where available, use Libevent 2.0's periodic timers so that our
13924 once-per-second cleanup code gets called even more closely to
13925 once per second than it would otherwise. Fixes bug 943.
13926 - If you run a bridge that listens on multiple IP addresses, and
13927 some user configures a bridge address that uses a different IP
13928 address than your bridge writes in its router descriptor, and the
13929 user doesn't specify an identity key, their Tor would discard the
13930 descriptor because "it isn't one of our configured bridges", and
13931 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
13932 Bugfix on 0.2.0.3-alpha.
13933 - If OpenSSL fails to make a duplicate of a private or public key, log
13934 an error message and try to exit cleanly. May help with debugging
13935 if bug 1209 ever remanifests.
13936 - Save a couple bytes in memory allocation every time we escape
13937 certain characters in a string. Patch from Florian Zumbiehl.
13938 - Make it explicit that we don't cannibalize one-hop circuits. This
13939 happens in the wild, but doesn't turn out to be a problem because
13940 we fortunately don't use those circuits. Many thanks to outofwords
13941 for the initial analysis and to swissknife who confirmed that
13942 two-hop circuits are actually created.
13943 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
13944 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
13945 - Eliminate a case where a circuit build time warning was displayed
13946 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
13949 Changes in version 0.2.1.26 - 2010-05-02
13950 Tor 0.2.1.26 addresses the recent connection and memory overload
13951 problems we've been seeing on relays, especially relays with their
13952 DirPort open. If your relay has been crashing, or you turned it off
13953 because it used too many resources, give this release a try.
13955 This release also fixes yet another instance of broken OpenSSL libraries
13956 that was causing some relays to drop out of the consensus.
13959 - Teach relays to defend themselves from connection overload. Relays
13960 now close idle circuits early if it looks like they were intended
13961 for directory fetches. Relays are also more aggressive about closing
13962 TLS connections that have no circuits on them. Such circuits are
13963 unlikely to be re-used, and tens of thousands of them were piling
13964 up at the fast relays, causing the relays to run out of sockets
13965 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
13966 their directory fetches over TLS).
13967 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
13968 that claim to be earlier than 0.9.8m, but which have in reality
13969 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
13970 behavior. Possible fix for some cases of bug 1346.
13971 - Directory mirrors were fetching relay descriptors only from v2
13972 directory authorities, rather than v3 authorities like they should.
13973 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
13974 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
13977 - Finally get rid of the deprecated and now harmful notion of "clique
13978 mode", where directory authorities maintain TLS connections to
13982 - In the util/threads test, no longer free the test_mutex before all
13983 worker threads have finished. Bugfix on 0.2.1.6-alpha.
13984 - The master thread could starve the worker threads quite badly on
13985 certain systems, causing them to run only partially in the allowed
13986 window. This resulted in test failures. Now the master thread sleeps
13987 occasionally for a few microseconds while the two worker-threads
13988 compete for the mutex. Bugfix on 0.2.0.1-alpha.
13991 Changes in version 0.2.2.13-alpha - 2010-04-24
13992 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
13993 problems we've been seeing on relays, especially relays with their
13994 DirPort open. If your relay has been crashing, or you turned it off
13995 because it used too many resources, give this release a try.
13998 - Teach relays to defend themselves from connection overload. Relays
13999 now close idle circuits early if it looks like they were intended
14000 for directory fetches. Relays are also more aggressive about closing
14001 TLS connections that have no circuits on them. Such circuits are
14002 unlikely to be re-used, and tens of thousands of them were piling
14003 up at the fast relays, causing the relays to run out of sockets
14004 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
14005 their directory fetches over TLS).
14008 - Finally get rid of the deprecated and now harmful notion of "clique
14009 mode", where directory authorities maintain TLS connections to
14011 - Directory authorities now do an immediate reachability check as soon
14012 as they hear about a new relay. This change should slightly reduce
14013 the time between setting up a relay and getting listed as running
14014 in the consensus. It should also improve the time between setting
14015 up a bridge and seeing use by bridge users.
14016 - Directory authorities no longer launch a TLS connection to every
14017 relay as they startup. Now that we have 2k+ descriptors cached,
14018 the resulting network hiccup is becoming a burden. Besides,
14019 authorities already avoid voting about Running for the first half
14020 hour of their uptime.
14023 Changes in version 0.2.2.12-alpha - 2010-04-20
14024 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
14025 handle and vote on descriptors. It was causing relays to drop out of
14029 - Many relays have been falling out of the consensus lately because
14030 not enough authorities know about their descriptor for them to get
14031 a majority of votes. When we deprecated the v2 directory protocol,
14032 we got rid of the only way that v3 authorities can hear from each
14033 other about other descriptors. Now authorities examine every v3
14034 vote for new descriptors, and fetch them from that authority. Bugfix
14036 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
14037 and a warning in or.h related to bandwidth_weight_rule_t that
14038 prevented clean compile on OS X. Fixes bug 1363; bugfix on
14040 - Fix a segfault on relays when DirReqStatistics is enabled
14041 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
14045 - Demote a confusing TLS warning that relay operators might get when
14046 someone tries to talk to their OrPort. It is neither the operator's
14047 fault nor can they do anything about it. Fixes bug 1364; bugfix
14051 Changes in version 0.2.2.11-alpha - 2010-04-15
14052 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
14053 libraries that was causing some relays to drop out of the consensus.
14056 - Directory mirrors were fetching relay descriptors only from v2
14057 directory authorities, rather than v3 authorities like they should.
14058 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
14059 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
14060 - Fix a parsing error that made every possible value of
14061 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
14062 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
14063 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
14064 about the option without breaking older ones.
14065 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
14066 that claim to be earlier than 0.9.8m, but which have in reality
14067 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
14068 behavior. Possible fix for some cases of bug 1346.
14071 - Experiment with a more aggressive approach to preventing clients
14072 from making one-hop exit streams. Exit relays who want to try it
14073 out can set "RefuseUnknownExits 1" in their torrc, and then look
14074 for "Attempt by %s to open a stream" log messages. Let us know
14076 - Add support for statically linking zlib by specifying
14077 --enable-static-zlib, to go with our support for statically linking
14078 openssl and libevent. Resolves bug 1358.
14081 - Fix a segfault that happens whenever a Tor client that is using
14082 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
14084 - When we cleaned up the contrib/tor-exit-notice.html file, we left
14085 out the first line. Fixes bug 1295.
14086 - When building the manpage from a tarball, we required asciidoc, but
14087 the asciidoc -> roff/html conversion was already done for the
14088 tarball. Make 'make' complain only when we need asciidoc (either
14089 because we're compiling directly from git, or because we altered
14090 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
14091 - When none of the directory authorities vote on any params, Tor
14092 segfaulted when trying to make the consensus from the votes. We
14093 didn't trigger the bug in practice, because authorities do include
14094 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
14097 - In the util/threads test, no longer free the test_mutex before all
14098 worker threads have finished. Bugfix on 0.2.1.6-alpha.
14099 - The master thread could starve the worker threads quite badly on
14100 certain systems, causing them to run only partially in the allowed
14101 window. This resulted in test failures. Now the master thread sleeps
14102 occasionally for a few microseconds while the two worker-threads
14103 compete for the mutex. Bugfix on 0.2.0.1-alpha.
14106 Changes in version 0.2.2.10-alpha - 2010-03-07
14107 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
14108 could prevent relays from guessing their IP address correctly. It also
14109 starts the groundwork for another client-side performance boost, since
14110 currently we're not making efficient use of relays that have both the
14111 Guard flag and the Exit flag.
14114 - Fix a regression from our patch for bug 1244 that caused relays
14115 to guess their IP address incorrectly if they didn't set Address
14116 in their torrc and/or their address fails to resolve. Bugfix on
14117 0.2.2.9-alpha; fixes bug 1269.
14119 o Major features (performance):
14120 - Directory authorities now compute consensus weightings that instruct
14121 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
14122 and no flag. Clients that use these weightings will distribute
14123 network load more evenly across these different relay types. The
14124 weightings are in the consensus so we can change them globally in
14125 the future. Extra thanks to "outofwords" for finding some nasty
14126 security bugs in the first implementation of this feature.
14128 o Minor features (performance):
14129 - Always perform router selections using weighted relay bandwidth,
14130 even if we don't need a high capacity circuit at the time. Non-fast
14131 circuits now only differ from fast ones in that they can use relays
14132 not marked with the Fast flag. This "feature" could turn out to
14133 be a horrible bug; we should investigate more before it goes into
14137 - Allow disabling building of the manpages. Skipping the manpage
14138 speeds up the build considerably.
14140 o Minor bugfixes (on 0.2.2.x):
14141 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
14142 Bugfix on 0.2.2.9-alpha.
14143 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
14144 config option. Bugfix on 0.2.2.7-alpha.
14145 - Ship the asciidoc-helper file in the tarball, so that people can
14146 build from source if they want to, and touching the .1.txt files
14147 doesn't break the build. Bugfix on 0.2.2.9-alpha.
14149 o Minor bugfixes (on 0.2.1.x or earlier):
14150 - Fix a dereference-then-NULL-check sequence when publishing
14151 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
14153 - Fix another dereference-then-NULL-check sequence. Bugfix on
14154 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
14155 - Make sure we treat potentially not NUL-terminated strings correctly.
14156 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
14158 o Code simplifications and refactoring:
14159 - Fix some urls in the exit notice file and make it XHTML1.1 strict
14160 compliant. Based on a patch from Christian Kujau.
14161 - Don't use sed in asciidoc-helper anymore.
14162 - Make the build process fail if asciidoc cannot be found and
14163 building with asciidoc isn't disabled.
14166 Changes in version 0.2.2.9-alpha - 2010-02-22
14167 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
14168 location of a directory authority, and cleans up a bunch of small bugs.
14170 o Directory authority changes:
14171 - Change IP address for dannenberg (v3 directory authority), and
14172 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
14173 service directory authority) from the list.
14176 - Make Tor work again on the latest OS X: when deciding whether to
14177 use strange flags to turn TLS renegotiation on, detect the OpenSSL
14178 version at run-time, not compile time. We need to do this because
14179 Apple doesn't update its dev-tools headers when it updates its
14180 libraries in a security patch.
14181 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
14182 that could happen on 32-bit platforms with 64-bit time_t. Also fix
14183 a memory leak when requesting a hidden service descriptor we've
14184 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
14186 - Authorities could be tricked into giving out the Exit flag to relays
14187 that didn't allow exiting to any ports. This bug could screw
14188 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
14189 1238. Bug discovered by Martin Kowalczyk.
14190 - When freeing a session key, zero it out completely. We only zeroed
14191 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
14192 patched by ekir. Fixes bug 1254.
14195 - Fix static compilation by listing the openssl libraries in the right
14196 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
14197 - Resume handling .exit hostnames in a special way: originally we
14198 stripped the .exit part and used the requested exit relay. In
14199 0.2.2.1-alpha we stopped treating them in any special way, meaning
14200 if you use a .exit address then Tor will pass it on to the exit
14201 relay. Now we reject the .exit stream outright, since that behavior
14202 might be more expected by the user. Found and diagnosed by Scott
14203 Bennett and Downie on or-talk.
14204 - Don't spam the controller with events when we have no file
14205 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
14206 for log messages was already solved from bug 748.)
14207 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
14209 - Make the DNSPort option work with libevent 2.x. Don't alter the
14210 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
14211 - Emit a GUARD DROPPED controller event for a case we missed.
14212 - Make more fields in the controller protocol case-insensitive, since
14213 control-spec.txt said they were.
14214 - Refactor resolve_my_address() to not use gethostbyname() anymore.
14215 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
14216 - Fix a spec conformance issue: the network-status-version token
14217 must be the first token in a v3 consensus or vote. Discovered by
14218 parakeep. Bugfix on 0.2.0.3-alpha.
14220 o Code simplifications and refactoring:
14221 - Generate our manpage and HTML documentation using Asciidoc. This
14222 change should make it easier to maintain the documentation, and
14223 produce nicer HTML.
14224 - Remove the --enable-iphone option. According to reports from Marco
14225 Bonetti, Tor builds fine without any special tweaking on recent
14226 iPhone SDK versions.
14227 - Removed some unnecessary files from the source distribution. The
14228 AUTHORS file has now been merged into the people page on the
14229 website. The roadmaps and design doc can now be found in the
14230 projects directory in svn.
14231 - Enabled various circuit build timeout constants to be controlled
14232 by consensus parameters. Also set better defaults for these
14233 parameters based on experimentation on broadband and simulated
14234 high latency links.
14237 - The 'EXTENDCIRCUIT' control port command can now be used with
14238 a circ id of 0 and no path. This feature will cause Tor to build
14239 a new 'fast' general purpose circuit using its own path selection
14241 - Added a BUILDTIMEOUT_SET controller event to describe changes
14242 to the circuit build timeout.
14243 - Future-proof the controller protocol a bit by ignoring keyword
14244 arguments we do not recognize.
14245 - Expand homedirs passed to tor-checkkey. This should silence a
14246 coverity complaint about passing a user-supplied string into
14247 open() without checking it.
14250 Changes in version 0.2.1.25 - 2010-03-16
14251 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
14252 prevent relays from guessing their IP address correctly. It also fixes
14253 several minor potential security bugs.
14256 - Fix a regression from our patch for bug 1244 that caused relays
14257 to guess their IP address incorrectly if they didn't set Address
14258 in their torrc and/or their address fails to resolve. Bugfix on
14259 0.2.1.23; fixes bug 1269.
14260 - When freeing a session key, zero it out completely. We only zeroed
14261 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
14262 patched by ekir. Fixes bug 1254.
14265 - Fix a dereference-then-NULL-check sequence when publishing
14266 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
14268 - Fix another dereference-then-NULL-check sequence. Bugfix on
14269 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
14270 - Make sure we treat potentially not NUL-terminated strings correctly.
14271 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
14275 Changes in version 0.2.1.24 - 2010-02-21
14276 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
14280 - Work correctly out-of-the-box with even more vendor-patched versions
14281 of OpenSSL. In particular, make it so Debian and OS X don't need
14282 customized patches to run/build.
14285 Changes in version 0.2.1.23 - 2010-02-13
14286 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
14287 again on the latest OS X, and updates the location of a directory
14290 o Major bugfixes (performance):
14291 - We were selecting our guards uniformly at random, and then weighting
14292 which of our guards we'd use uniformly at random. This imbalance
14293 meant that Tor clients were severely limited on throughput (and
14294 probably latency too) by the first hop in their circuit. Now we
14295 select guards weighted by currently advertised bandwidth. We also
14296 automatically discard guards picked using the old algorithm. Fixes
14297 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
14300 - Make Tor work again on the latest OS X: when deciding whether to
14301 use strange flags to turn TLS renegotiation on, detect the OpenSSL
14302 version at run-time, not compile time. We need to do this because
14303 Apple doesn't update its dev-tools headers when it updates its
14304 libraries in a security patch.
14305 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
14306 that could happen on 32-bit platforms with 64-bit time_t. Also fix
14307 a memory leak when requesting a hidden service descriptor we've
14308 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
14311 o Directory authority changes:
14312 - Change IP address for dannenberg (v3 directory authority), and
14313 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
14314 service directory authority) from the list.
14317 - Refactor resolve_my_address() to not use gethostbyname() anymore.
14318 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
14321 - Avoid a mad rush at the beginning of each month when each client
14322 rotates half of its guards. Instead we spread the rotation out
14323 throughout the month, but we still avoid leaving a precise timestamp
14324 in the state file about when we first picked the guard. Improves
14325 over the behavior introduced in 0.1.2.17.
14328 Changes in version 0.2.2.8-alpha - 2010-01-26
14329 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
14330 causing bridge relays to disappear. If you're running a bridge,
14334 - Fix a memory corruption bug on bridges that occured during the
14335 inclusion of stats data in extra-info descriptors. Also fix the
14336 interface for geoip_get_bridge_stats* to prevent similar bugs in
14337 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
14338 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
14341 - Ignore OutboundBindAddress when connecting to localhost.
14342 Connections to localhost need to come _from_ localhost, or else
14343 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
14347 Changes in version 0.2.2.7-alpha - 2010-01-19
14348 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
14349 as laying the groundwork for further relay-side performance fixes. It
14350 also starts cleaning up client behavior with respect to the EntryNodes,
14351 ExitNodes, and StrictNodes config options.
14353 This release also rotates two directory authority keys, due to a
14354 security breach of some of the Torproject servers.
14356 o Directory authority changes:
14357 - Rotate keys (both v3 identity and relay identity) for moria1
14360 o Major features (performance):
14361 - We were selecting our guards uniformly at random, and then weighting
14362 which of our guards we'd use uniformly at random. This imbalance
14363 meant that Tor clients were severely limited on throughput (and
14364 probably latency too) by the first hop in their circuit. Now we
14365 select guards weighted by currently advertised bandwidth. We also
14366 automatically discard guards picked using the old algorithm. Fixes
14367 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
14368 - When choosing which cells to relay first, relays can now favor
14369 circuits that have been quiet recently, to provide lower latency
14370 for low-volume circuits. By default, relays enable or disable this
14371 feature based on a setting in the consensus. You can override
14372 this default by using the new "CircuitPriorityHalflife" config
14373 option. Design and code by Ian Goldberg, Can Tang, and Chris
14375 - Add separate per-conn write limiting to go with the per-conn read
14376 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
14377 but never per-conn write limits.
14378 - New consensus params "bwconnrate" and "bwconnburst" to let us
14379 rate-limit client connections as they enter the network. It's
14380 controlled in the consensus so we can turn it on and off for
14381 experiments. It's starting out off. Based on proposal 163.
14383 o Major features (relay selection options):
14384 - Switch to a StrictNodes config option, rather than the previous
14385 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
14386 "StrictExcludeNodes" option.
14387 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
14388 change during a config reload, mark and discard all our origin
14389 circuits. This fix should address edge cases where we change the
14390 config options and but then choose a circuit that we created before
14392 - If EntryNodes or ExitNodes are set, be more willing to use an
14393 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
14395 - Make EntryNodes config option much more aggressive even when
14396 StrictNodes is not set. Before it would prepend your requested
14397 entrynodes to your list of guard nodes, but feel free to use others
14398 after that. Now it chooses only from your EntryNodes if any of
14399 those are available, and only falls back to others if a) they're
14400 all down and b) StrictNodes is not set.
14401 - Now we refresh your entry guards from EntryNodes at each consensus
14402 fetch -- rather than just at startup and then they slowly rot as
14403 the network changes.
14406 - Stop bridge directory authorities from answering dbg-stability.txt
14407 directory queries, which would let people fetch a list of all
14408 bridge identities they track. Bugfix on 0.2.1.6-alpha.
14411 - Log a notice when we get a new control connection. Now it's easier
14412 for security-conscious users to recognize when a local application
14413 is knocking on their controller door. Suggested by bug 1196.
14414 - New config option "CircuitStreamTimeout" to override our internal
14415 timeout schedule for how many seconds until we detach a stream from
14416 a circuit and try a new circuit. If your network is particularly
14417 slow, you might want to set this to a number like 60.
14418 - New controller command "getinfo config-text". It returns the
14419 contents that Tor would write if you send it a SAVECONF command,
14420 so the controller can write the file to disk itself.
14421 - New options for SafeLogging to allow scrubbing only log messages
14422 generated while acting as a relay.
14423 - Ship the bridges spec file in the tarball too.
14424 - Avoid a mad rush at the beginning of each month when each client
14425 rotates half of its guards. Instead we spread the rotation out
14426 throughout the month, but we still avoid leaving a precise timestamp
14427 in the state file about when we first picked the guard. Improves
14428 over the behavior introduced in 0.1.2.17.
14430 o Minor bugfixes (compiling):
14431 - Fix compilation on OS X 10.3, which has a stub mlockall() but
14432 hides it. Bugfix on 0.2.2.6-alpha.
14433 - Fix compilation on Solaris by removing support for the
14434 DisableAllSwap config option. Solaris doesn't have an rlimit for
14435 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
14438 o Minor bugfixes (crashes):
14439 - Do not segfault when writing buffer stats when we haven't observed
14440 a single circuit to report about. Found by Fabian Lanze. Bugfix on
14442 - If we're in the pathological case where there's no exit bandwidth
14443 but there is non-exit bandwidth, or no guard bandwidth but there
14444 is non-guard bandwidth, don't crash during path selection. Bugfix
14446 - Fix an impossible-to-actually-trigger buffer overflow in relay
14447 descriptor generation. Bugfix on 0.1.0.15.
14449 o Minor bugfixes (privacy):
14450 - Fix an instance where a Tor directory mirror might accidentally
14451 log the IP address of a misbehaving Tor client. Bugfix on
14453 - Don't list Windows capabilities in relay descriptors. We never made
14454 use of them, and maybe it's a bad idea to publish them. Bugfix
14457 o Minor bugfixes (other):
14458 - Resolve an edge case in path weighting that could make us misweight
14459 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
14460 - Fix statistics on client numbers by country as seen by bridges that
14461 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
14462 intervals instead of variable 12-to-48-hour intervals.
14463 - After we free an internal connection structure, overwrite it
14464 with a different memory value than we use for overwriting a freed
14465 internal circuit structure. Should help with debugging. Suggested
14467 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
14470 o Removed features:
14471 - Remove the HSAuthorityRecordStats option that version 0 hidden
14472 service authorities could have used to track statistics of overall
14473 hidden service usage.
14476 Changes in version 0.2.1.22 - 2010-01-19
14477 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
14478 authorities -- it would tell you its whole history of bridge descriptors
14479 if you make the right directory request. This stable update also
14480 rotates two of the seven v3 directory authority keys and locations.
14482 o Directory authority changes:
14483 - Rotate keys (both v3 identity and relay identity) for moria1
14487 - Stop bridge directory authorities from answering dbg-stability.txt
14488 directory queries, which would let people fetch a list of all
14489 bridge identities they track. Bugfix on 0.2.1.6-alpha.
14492 Changes in version 0.2.1.21 - 2009-12-21
14493 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
14494 library. If you use Tor on Linux / Unix and you're getting SSL
14495 renegotiation errors, upgrading should help. We also recommend an
14496 upgrade if you're an exit relay.
14499 - Work around a security feature in OpenSSL 0.9.8l that prevents our
14500 handshake from working unless we explicitly tell OpenSSL that we
14501 are using SSL renegotiation safely. We are, of course, but OpenSSL
14502 0.9.8l won't work unless we say we are.
14503 - Avoid crashing if the client is trying to upload many bytes and the
14504 circuit gets torn down at the same time, or if the flip side
14505 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
14508 - Do not refuse to learn about authority certs and v2 networkstatus
14509 documents that are older than the latest consensus. This bug might
14510 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
14511 Spotted and fixed by xmux.
14512 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
14513 trigger platform-specific option misparsing case found by Coverity
14515 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
14516 trigger assert. Fixes bug 1173.
14519 Changes in version 0.2.2.6-alpha - 2009-11-19
14520 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
14521 support for the new lower-footprint "microdescriptor" directory design,
14522 future-proofing our consensus format against new hash functions or
14523 other changes, and an Android port. It also makes Tor compatible with
14524 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
14527 - Directory authorities can now create, vote on, and serve multiple
14528 parallel formats of directory data as part of their voting process.
14529 Partially implements Proposal 162: "Publish the consensus in
14531 - Directory authorities can now agree on and publish small summaries
14532 of router information that clients can use in place of regular
14533 server descriptors. This transition will eventually allow clients
14534 to use far less bandwidth for downloading information about the
14535 network. Begins the implementation of Proposal 158: "Clients
14536 download consensus + microdescriptors".
14537 - The directory voting system is now extensible to use multiple hash
14538 algorithms for signatures and resource selection. Newer formats
14539 are signed with SHA256, with a possibility for moving to a better
14540 hash algorithm in the future.
14541 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
14542 current and future memory pages via mlockall(). On supported
14543 platforms (modern Linux and probably BSD but not Windows or OS X),
14544 this should effectively disable any and all attempts to page out
14545 memory. This option requires that you start your Tor as root --
14546 if you use DisableAllSwap, please consider using the User option
14547 to properly reduce the privileges of your Tor.
14548 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
14549 to help Tor build correctly for Android phones.
14552 - Work around a security feature in OpenSSL 0.9.8l that prevents our
14553 handshake from working unless we explicitly tell OpenSSL that we
14554 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
14555 won't work unless we say we are.
14558 - Fix a crash bug when trying to initialize the evdns module in
14559 Libevent 2. Bugfix on 0.2.1.16-rc.
14560 - Stop logging at severity 'warn' when some other Tor client tries
14561 to establish a circuit with us using weak DH keys. It's a protocol
14562 violation, but that doesn't mean ordinary users need to hear about
14563 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
14564 - Do not refuse to learn about authority certs and v2 networkstatus
14565 documents that are older than the latest consensus. This bug might
14566 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
14567 Spotted and fixed by xmux.
14568 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
14569 - If all authorities restart at once right before a consensus vote,
14570 nobody will vote about "Running", and clients will get a consensus
14571 with no usable relays. Instead, authorities refuse to build a
14572 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
14573 - If your relay can't keep up with the number of incoming create
14574 cells, it would log one warning per failure into your logs. Limit
14575 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
14576 - Bridges now use "reject *:*" as their default exit policy. Bugfix
14577 on 0.2.0.3-alpha; fixes bug 1113.
14578 - Fix a memory leak on directory authorities during voting that was
14579 introduced in 0.2.2.1-alpha. Found via valgrind.
14582 Changes in version 0.2.1.20 - 2009-10-15
14583 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
14584 services at once, prepares for more performance improvements, and
14585 fixes a bunch of smaller bugs.
14587 The Windows and OS X bundles also include a more recent Vidalia,
14588 and switch from Privoxy to Polipo.
14590 The OS X installers are now drag and drop. It's best to un-install
14591 Tor/Vidalia and then install this new bundle, rather than upgrade. If
14592 you want to upgrade, you'll need to update the paths for Tor and Polipo
14593 in the Vidalia Settings window.
14596 - Send circuit or stream sendme cells when our window has decreased
14597 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
14598 by Karsten when testing the "reduce circuit window" performance
14599 patch. Bugfix on the 54th commit on Tor -- from July 2002,
14600 before the release of Tor 0.0.0. This is the new winner of the
14602 - Fix a remotely triggerable memory leak when a consensus document
14603 contains more than one signature from the same voter. Bugfix on
14605 - Avoid segfault in rare cases when finishing an introduction circuit
14606 as a client and finding out that we don't have an introduction key
14607 for it. Fixes bug 1073. Reported by Aaron Swartz.
14610 - Tor now reads the "circwindow" parameter out of the consensus,
14611 and uses that value for its circuit package window rather than the
14612 default of 1000 cells. Begins the implementation of proposal 168.
14614 o New directory authorities:
14615 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
14617 - Move moria1 and tonga to alternate IP addresses.
14620 - Fix a signed/unsigned compile warning in 0.2.1.19.
14621 - Fix possible segmentation fault on directory authorities. Bugfix on
14623 - Fix an extremely rare infinite recursion bug that could occur if
14624 we tried to log a message after shutting down the log subsystem.
14625 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
14626 - Fix an obscure bug where hidden services on 64-bit big-endian
14627 systems might mis-read the timestamp in v3 introduce cells, and
14628 refuse to connect back to the client. Discovered by "rotor".
14629 Bugfix on 0.2.1.6-alpha.
14630 - We were triggering a CLOCK_SKEW controller status event whenever
14631 we connect via the v2 connection protocol to any relay that has
14632 a wrong clock. Instead, we should only inform the controller when
14633 it's a trusted authority that claims our clock is wrong. Bugfix
14634 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
14635 - We were telling the controller about CHECKING_REACHABILITY and
14636 REACHABILITY_FAILED status events whenever we launch a testing
14637 circuit or notice that one has failed. Instead, only tell the
14638 controller when we want to inform the user of overall success or
14639 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
14641 - Don't warn when we're using a circuit that ends with a node
14642 excluded in ExcludeExitNodes, but the circuit is not used to access
14643 the outside world. This should help fix bug 1090. Bugfix on
14645 - Work around a small memory leak in some versions of OpenSSL that
14646 stopped the memory used by the hostname TLS extension from being
14650 - Add a "getinfo status/accepted-server-descriptor" controller
14651 command, which is the recommended way for controllers to learn
14652 whether our server descriptor has been successfully received by at
14653 least on directory authority. Un-recommend good-server-descriptor
14654 getinfo and status events until we have a better design for them.
14657 Changes in version 0.2.2.5-alpha - 2009-10-11
14658 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
14661 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
14663 o Directory authorities:
14664 - Temporarily (just for this release) move dizum to an alternate
14668 Changes in version 0.2.2.4-alpha - 2009-10-10
14669 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
14670 introduces a new unit test framework, shifts directry authority
14671 addresses around to reduce the impact from recent blocking events,
14672 and fixes a few smaller bugs.
14675 - Fix several more asserts in the circuit_build_times code, for
14676 example one that causes Tor to fail to start once we have
14677 accumulated 5000 build times in the state file. Bugfixes on
14678 0.2.2.2-alpha; fixes bug 1108.
14680 o New directory authorities:
14681 - Move moria1 and Tonga to alternate IP addresses.
14684 - Log SSL state transitions at debug level during handshake, and
14685 include SSL states in error messages. This may help debug future
14686 SSL handshake issues.
14687 - Add a new "Handshake" log domain for activities that happen
14688 during the TLS handshake.
14689 - Revert to the "June 3 2009" ip-to-country file. The September one
14690 seems to have removed most US IP addresses.
14691 - Directory authorities now reject Tor relays with versions less than
14692 0.1.2.14. This step cuts out four relays from the current network,
14693 none of which are very big.
14696 - Fix a couple of smaller issues with gathering statistics. Bugfixes
14698 - Fix two memory leaks in the error case of
14699 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
14700 - Don't count one-hop circuits when we're estimating how long it
14701 takes circuits to build on average. Otherwise we'll set our circuit
14702 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
14703 - Directory authorities no longer change their opinion of, or vote on,
14704 whether a router is Running, unless they have themselves been
14705 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
14708 o Code simplifications and refactoring:
14709 - Revise our unit tests to use the "tinytest" framework, so we
14710 can run tests in their own processes, have smarter setup/teardown
14711 code, and so on. The unit test code has moved to its own
14712 subdirectory, and has been split into multiple modules.
14715 Changes in version 0.2.2.3-alpha - 2009-09-23
14716 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
14719 - Fix an overzealous assert in our new circuit build timeout code.
14720 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
14723 - If the networkstatus consensus tells us that we should use a
14724 negative circuit package window, ignore it. Otherwise we'll
14725 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
14728 Changes in version 0.2.2.2-alpha - 2009-09-21
14729 Tor 0.2.2.2-alpha introduces our latest performance improvement for
14730 clients: Tor tracks the average time it takes to build a circuit, and
14731 avoids using circuits that take too long to build. For fast connections,
14732 this feature can cut your expected latency in half. For slow or flaky
14733 connections, it could ruin your Tor experience. Let us know if it does!
14736 - Tor now tracks how long it takes to build client-side circuits
14737 over time, and adapts its timeout to local network performance.
14738 Since a circuit that takes a long time to build will also provide
14739 bad performance, we get significant latency improvements by
14740 discarding the slowest 20% of circuits. Specifically, Tor creates
14741 circuits more aggressively than usual until it has enough data
14742 points for a good timeout estimate. Implements proposal 151.
14743 We are especially looking for reports (good and bad) from users with
14744 both EDGE and broadband connections that can move from broadband
14745 to EDGE and find out if the build-time data in the .tor/state gets
14746 reset without loss of Tor usability. You should also see a notice
14747 log message telling you that Tor has reset its timeout.
14748 - Directory authorities can now vote on arbitary integer values as
14749 part of the consensus process. This is designed to help set
14750 network-wide parameters. Implements proposal 167.
14751 - Tor now reads the "circwindow" parameter out of the consensus,
14752 and uses that value for its circuit package window rather than the
14753 default of 1000 cells. Begins the implementation of proposal 168.
14756 - Fix a remotely triggerable memory leak when a consensus document
14757 contains more than one signature from the same voter. Bugfix on
14761 - Fix an extremely rare infinite recursion bug that could occur if
14762 we tried to log a message after shutting down the log subsystem.
14763 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
14764 - Fix parsing for memory or time units given without a space between
14765 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
14766 - A networkstatus vote must contain exactly one signature. Spec
14767 conformance issue. Bugfix on 0.2.0.3-alpha.
14768 - Fix an obscure bug where hidden services on 64-bit big-endian
14769 systems might mis-read the timestamp in v3 introduce cells, and
14770 refuse to connect back to the client. Discovered by "rotor".
14771 Bugfix on 0.2.1.6-alpha.
14772 - We were triggering a CLOCK_SKEW controller status event whenever
14773 we connect via the v2 connection protocol to any relay that has
14774 a wrong clock. Instead, we should only inform the controller when
14775 it's a trusted authority that claims our clock is wrong. Bugfix
14776 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
14777 - We were telling the controller about CHECKING_REACHABILITY and
14778 REACHABILITY_FAILED status events whenever we launch a testing
14779 circuit or notice that one has failed. Instead, only tell the
14780 controller when we want to inform the user of overall success or
14781 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
14783 - Don't warn when we're using a circuit that ends with a node
14784 excluded in ExcludeExitNodes, but the circuit is not used to access
14785 the outside world. This should help fix bug 1090, but more problems
14786 remain. Bugfix on 0.2.1.6-alpha.
14787 - Work around a small memory leak in some versions of OpenSSL that
14788 stopped the memory used by the hostname TLS extension from being
14790 - Make our 'torify' script more portable; if we have only one of
14791 'torsocks' or 'tsocks' installed, don't complain to the user;
14792 and explain our warning about tsocks better.
14795 - Add a "getinfo status/accepted-server-descriptor" controller
14796 command, which is the recommended way for controllers to learn
14797 whether our server descriptor has been successfully received by at
14798 least on directory authority. Un-recommend good-server-descriptor
14799 getinfo and status events until we have a better design for them.
14800 - Update to the "September 4 2009" ip-to-country file.
14803 Changes in version 0.2.2.1-alpha - 2009-08-26
14804 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
14805 Tor clients to bootstrap on networks where only port 80 is reachable,
14806 makes it more straightforward to support hardware crypto accelerators,
14807 and starts the groundwork for gathering stats safely at relays.
14810 - Start the process of disabling ".exit" address notation, since it
14811 can be used for a variety of esoteric application-level attacks
14812 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
14815 o New directory authorities:
14816 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
14820 - New AccelName and AccelDir options add support for dynamic OpenSSL
14821 hardware crypto acceleration engines.
14822 - Tor now supports tunneling all of its outgoing connections over
14823 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
14824 configuration options. Code by Christopher Davis.
14827 - Send circuit or stream sendme cells when our window has decreased
14828 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
14829 by Karsten when testing the "reduce circuit window" performance
14830 patch. Bugfix on the 54th commit on Tor -- from July 2002,
14831 before the release of Tor 0.0.0. This is the new winner of the
14834 o New options for gathering stats safely:
14835 - Directory mirrors that set "DirReqStatistics 1" write statistics
14836 about directory requests to disk every 24 hours. As compared to the
14837 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
14838 1) stats are written to disk exactly every 24 hours; 2) estimated
14839 shares of v2 and v3 requests are determined as mean values, not at
14840 the end of a measurement period; 3) unresolved requests are listed
14841 with country code '??'; 4) directories also measure download times.
14842 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
14843 number of exit streams and transferred bytes per port to disk every
14845 - Relays that set "CellStatistics 1" write statistics on how long
14846 cells spend in their circuit queues to disk every 24 hours.
14847 - Entry nodes that set "EntryStatistics 1" write statistics on the
14848 rough number and origins of connecting clients to disk every 24
14850 - Relays that write any of the above statistics to disk and set
14851 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
14852 their extra-info documents.
14855 - New --digests command-line switch to output the digests of the
14856 source files Tor was built with.
14857 - The "torify" script now uses torsocks where available.
14858 - The memarea code now uses a sentinel value at the end of each area
14859 to make sure nothing writes beyond the end of an area. This might
14860 help debug some conceivable causes of bug 930.
14861 - Time and memory units in the configuration file can now be set to
14862 fractional units. For example, "2.5 GB" is now a valid value for
14864 - Certain Tor clients (such as those behind check.torproject.org) may
14865 want to fetch the consensus in an extra early manner. To enable this
14866 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
14867 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
14868 as only certain clients who must have this information sooner should
14870 - Instead of adding the svn revision to the Tor version string, report
14871 the git commit (when we're building from a git checkout).
14874 - If any of the v3 certs we download are unparseable, we should
14875 actually notice the failure so we don't retry indefinitely. Bugfix
14876 on 0.2.0.x; reported by "rotator".
14877 - If the cached cert file is unparseable, warn but don't exit.
14878 - Fix possible segmentation fault on directory authorities. Bugfix on
14880 - When Tor fails to parse a descriptor of any kind, dump it to disk.
14881 Might help diagnosing bug 1051.
14883 o Deprecated and removed features:
14884 - The controller no longer accepts the old obsolete "addr-mappings/"
14885 or "unregistered-servers-" GETINFO values.
14886 - Hidden services no longer publish version 0 descriptors, and clients
14887 do not request or use version 0 descriptors. However, the old hidden
14888 service authorities still accept and serve version 0 descriptors
14889 when contacted by older hidden services/clients.
14890 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
14891 always on; using them is necessary for correct forward-compatible
14893 - Remove support for .noconnect style addresses. Nobody was using
14894 them, and they provided another avenue for detecting Tor users
14895 via application-level web tricks.
14897 o Packaging changes:
14898 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
14899 installer bundles. See
14900 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
14901 for details of what's new in Vidalia 0.2.3.
14902 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
14903 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
14904 configuration file, rather than the old Privoxy.
14905 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
14906 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
14907 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
14908 better compatibility with OS X 10.6, aka Snow Leopard.
14909 - OS X Vidalia Bundle: The multi-package installer is now replaced
14910 by a simple drag and drop to the /Applications folder. This change
14911 occurred with the upgrade to Vidalia 0.2.3.
14914 Changes in version 0.2.1.19 - 2009-07-28
14915 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
14916 services on Tor 0.2.1.3-alpha through 0.2.1.18.
14919 - Make accessing hidden services on 0.2.1.x work right again.
14920 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
14921 part of patch provided by "optimist".
14924 - When a relay/bridge is writing out its identity key fingerprint to
14925 the "fingerprint" file and to its logs, write it without spaces. Now
14926 it will look like the fingerprints in our bridges documentation,
14927 and confuse fewer users.
14930 - Relays no longer publish a new server descriptor if they change
14931 their MaxAdvertisedBandwidth config option but it doesn't end up
14932 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
14933 fixes bug 1026. Patch from Sebastian.
14934 - Avoid leaking memory every time we get a create cell but we have
14935 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
14936 fixes bug 1034. Reported by BarkerJr.
14939 Changes in version 0.2.1.18 - 2009-07-24
14940 Tor 0.2.1.18 lays the foundations for performance improvements,
14941 adds status events to help users diagnose bootstrap problems, adds
14942 optional authentication/authorization for hidden services, fixes a
14943 variety of potential anonymity problems, and includes a huge pile of
14944 other features and bug fixes.
14947 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
14950 Changes in version 0.2.1.17-rc - 2009-07-07
14951 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
14952 candidate for the 0.2.1.x series. It lays the groundwork for further
14953 client performance improvements, and also fixes a big bug with directory
14954 authorities that were causing them to assign Guard and Stable flags
14957 The Windows bundles also finally include the geoip database that we
14958 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
14959 should actually install Torbutton rather than giving you a cryptic
14960 failure message (oops).
14963 - Clients now use the bandwidth values in the consensus, rather than
14964 the bandwidth values in each relay descriptor. This approach opens
14965 the door to more accurate bandwidth estimates once the directory
14966 authorities start doing active measurements. Implements more of
14970 - When Tor clients restart after 1-5 days, they discard all their
14971 cached descriptors as too old, but they still use the cached
14972 consensus document. This approach is good for robustness, but
14973 bad for performance: since they don't know any bandwidths, they
14974 end up choosing at random rather than weighting their choice by
14975 speed. Fixed by the above feature of putting bandwidths in the
14976 consensus. Bugfix on 0.2.0.x.
14977 - Directory authorities were neglecting to mark relays down in their
14978 internal histories if the relays fall off the routerlist without
14979 ever being found unreachable. So there were relays in the histories
14980 that haven't been seen for eight months, and are listed as being
14981 up for eight months. This wreaked havoc on the "median wfu"
14982 and "median mtbf" calculations, in turn making Guard and Stable
14983 flags very wrong, hurting network performance. Fixes bugs 696 and
14984 969. Bugfix on 0.2.0.6-alpha.
14987 - Serve the DirPortFrontPage page even when we have been approaching
14988 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
14989 - The control port would close the connection before flushing long
14990 replies, such as the network consensus, if a QUIT command was issued
14991 before the reply had completed. Now, the control port flushes all
14992 pending replies before closing the connection. Also fixed a spurious
14993 warning when a QUIT command is issued after a malformed or rejected
14994 AUTHENTICATE command, but before the connection was closed. Patch
14995 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
14996 - When we can't find an intro key for a v2 hidden service descriptor,
14997 fall back to the v0 hidden service descriptor and log a bug message.
14998 Workaround for bug 1024.
14999 - Fix a log message that did not respect the SafeLogging option.
15003 - If we're a relay and we change our IP address, be more verbose
15004 about the reason that made us change. Should help track down
15005 further bugs for relays on dynamic IP addresses.
15008 Changes in version 0.2.0.35 - 2009-06-24
15010 - Avoid crashing in the presence of certain malformed descriptors.
15011 Found by lark, and by automated fuzzing.
15012 - Fix an edge case where a malicious exit relay could convince a
15013 controller that the client's DNS question resolves to an internal IP
15014 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
15017 - Finally fix the bug where dynamic-IP relays disappear when their
15018 IP address changes: directory mirrors were mistakenly telling
15019 them their old address if they asked via begin_dir, so they
15020 never got an accurate answer about their new address, so they
15021 just vanished after a day. For belt-and-suspenders, relays that
15022 don't set Address in their config now avoid using begin_dir for
15023 all direct connections. Should fix bugs 827, 883, and 900.
15024 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
15025 that would occur on some exit nodes when DNS failures and timeouts
15026 occurred in certain patterns. Fix for bug 957.
15029 - When starting with a cache over a few days old, do not leak
15030 memory for the obsolete router descriptors in it. Bugfix on
15031 0.2.0.33; fixes bug 672.
15032 - Hidden service clients didn't use a cached service descriptor that
15033 was older than 15 minutes, but wouldn't fetch a new one either,
15034 because there was already one in the cache. Now, fetch a v2
15035 descriptor unless the same descriptor was added to the cache within
15036 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
15039 Changes in version 0.2.1.16-rc - 2009-06-20
15040 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
15041 a bunch of minor bugs.
15044 - Fix an edge case where a malicious exit relay could convince a
15045 controller that the client's DNS question resolves to an internal IP
15046 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
15048 o Major performance improvements (on 0.2.0.x):
15049 - Disable and refactor some debugging checks that forced a linear scan
15050 over the whole server-side DNS cache. These accounted for over 50%
15051 of CPU time on a relatively busy exit node's gprof profile. Found
15053 - Disable some debugging checks that appeared in exit node profile
15057 - Update to the "June 3 2009" ip-to-country file.
15058 - Do not have tor-resolve automatically refuse all .onion addresses;
15059 if AutomapHostsOnResolve is set in your torrc, this will work fine.
15061 o Minor bugfixes (on 0.2.0.x):
15062 - Log correct error messages for DNS-related network errors on
15064 - Fix a race condition that could cause crashes or memory corruption
15065 when running as a server with a controller listening for log
15067 - Avoid crashing when we have a policy specified in a DirPolicy or
15068 SocksPolicy or ReachableAddresses option with ports set on it,
15069 and we re-load the policy. May fix bug 996.
15070 - Hidden service clients didn't use a cached service descriptor that
15071 was older than 15 minutes, but wouldn't fetch a new one either,
15072 because there was already one in the cache. Now, fetch a v2
15073 descriptor unless the same descriptor was added to the cache within
15074 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
15076 o Minor bugfixes (on 0.2.1.x):
15077 - Don't warn users about low port and hibernation mix when they
15078 provide a *ListenAddress directive to fix that. Bugfix on
15080 - When switching back and forth between bridge mode, do not start
15081 gathering GeoIP data until two hours have passed.
15082 - Do not complain that the user has requested an excluded node as
15083 an exit when the node is not really an exit. This could happen
15084 because the circuit was for testing, or an introduction point.
15088 Changes in version 0.2.1.15-rc - 2009-05-25
15089 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
15090 series. It fixes a major bug on fast exit relays, as well as a variety
15091 of more minor bugs.
15093 o Major bugfixes (on 0.2.0.x):
15094 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
15095 that would occur on some exit nodes when DNS failures and timeouts
15096 occurred in certain patterns. Fix for bug 957.
15098 o Minor bugfixes (on 0.2.0.x):
15099 - Actually return -1 in the error case for read_bandwidth_usage().
15100 Harmless bug, since we currently don't care about the return value
15101 anywhere. Bugfix on 0.2.0.9-alpha.
15102 - Provide a more useful log message if bug 977 (related to buffer
15103 freelists) ever reappears, and do not crash right away.
15104 - Fix an assertion failure on 64-bit platforms when we allocated
15105 memory right up to the end of a memarea, then realigned the memory
15106 one step beyond the end. Fixes a possible cause of bug 930.
15107 - Protect the count of open sockets with a mutex, so we can't
15108 corrupt it when two threads are closing or opening sockets at once.
15109 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
15110 - Don't allow a bridge to publish its router descriptor to a
15111 non-bridge directory authority. Fixes part of bug 932.
15112 - When we change to or from being a bridge, reset our counts of
15113 client usage by country. Fixes bug 932.
15114 - Fix a bug that made stream bandwidth get misreported to the
15116 - Stop using malloc_usable_size() to use more area than we had
15117 actually allocated: it was safe, but made valgrind really unhappy.
15118 - Fix a memory leak when v3 directory authorities load their keys
15119 and cert from disk. Bugfix on 0.2.0.1-alpha.
15121 o Minor bugfixes (on 0.2.1.x):
15122 - Fix use of freed memory when deciding to mark a non-addable
15123 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
15126 Changes in version 0.2.1.14-rc - 2009-04-12
15127 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
15128 series. It begins fixing some major performance problems, and also
15129 finally addresses the bug that was causing relays on dynamic IP
15130 addresses to fall out of the directory.
15133 - Clients replace entry guards that were chosen more than a few months
15134 ago. This change should significantly improve client performance,
15135 especially once more people upgrade, since relays that have been
15136 a guard for a long time are currently overloaded.
15138 o Major bugfixes (on 0.2.0):
15139 - Finally fix the bug where dynamic-IP relays disappear when their
15140 IP address changes: directory mirrors were mistakenly telling
15141 them their old address if they asked via begin_dir, so they
15142 never got an accurate answer about their new address, so they
15143 just vanished after a day. For belt-and-suspenders, relays that
15144 don't set Address in their config now avoid using begin_dir for
15145 all direct connections. Should fix bugs 827, 883, and 900.
15146 - Relays were falling out of the networkstatus consensus for
15147 part of a day if they changed their local config but the
15148 authorities discarded their new descriptor as "not sufficiently
15149 different". Now directory authorities accept a descriptor as changed
15150 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
15151 patch by Sebastian.
15152 - Avoid crashing in the presence of certain malformed descriptors.
15153 Found by lark, and by automated fuzzing.
15156 - When generating circuit events with verbose nicknames for
15157 controllers, try harder to look up nicknames for routers on a
15158 circuit. (Previously, we would look in the router descriptors we had
15159 for nicknames, but not in the consensus.) Partial fix for bug 941.
15160 - If the bridge config line doesn't specify a port, assume 443.
15161 This makes bridge lines a bit smaller and easier for users to
15163 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
15164 bytes (aka 20KB/s), to match our documentation. Also update
15165 directory authorities so they always assign the Fast flag to relays
15166 with 20KB/s of capacity. Now people running relays won't suddenly
15167 find themselves not seeing any use, if the network gets faster
15169 - Update to the "April 3 2009" ip-to-country file.
15172 - Avoid trying to print raw memory to the logs when we decide to
15173 give up on downloading a given relay descriptor. Bugfix on
15175 - In tor-resolve, when the Tor client to use is specified by
15176 <hostname>:<port>, actually use the specified port rather than
15177 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
15178 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
15179 - When starting with a cache over a few days old, do not leak
15180 memory for the obsolete router descriptors in it. Bugfix on
15182 - Avoid double-free on list of successfully uploaded hidden
15183 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
15184 - Change memarea_strndup() implementation to work even when
15185 duplicating a string at the end of a page. This bug was
15186 harmless for now, but could have meant crashes later. Fix by
15187 lark. Bugfix on 0.2.1.1-alpha.
15188 - Limit uploaded directory documents to be 16M rather than 500K.
15189 The directory authorities were refusing v3 consensus votes from
15190 other authorities, since the votes are now 504K. Fixes bug 959;
15191 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
15192 - Directory authorities should never send a 503 "busy" response to
15193 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
15197 Changes in version 0.2.1.13-alpha - 2009-03-09
15198 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
15199 cleanups. We're finally getting close to a release candidate.
15202 - Correctly update the list of which countries we exclude as
15203 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
15204 lark. Bugfix on 0.2.1.6-alpha.
15206 o Minor bugfixes (on 0.2.0.x and earlier):
15207 - Automatically detect MacOSX versions earlier than 10.4.0, and
15208 disable kqueue from inside Tor when running with these versions.
15209 We previously did this from the startup script, but that was no
15210 help to people who didn't use the startup script. Resolves bug 863.
15211 - When we had picked an exit node for a connection, but marked it as
15212 "optional", and it turned out we had no onion key for the exit,
15213 stop wanting that exit and try again. This situation may not
15214 be possible now, but will probably become feasible with proposal
15215 158. Spotted by rovv. Fixes another case of bug 752.
15216 - Clients no longer cache certificates for authorities they do not
15217 recognize. Bugfix on 0.2.0.9-alpha.
15218 - When we can't transmit a DNS request due to a network error, retry
15219 it after a while, and eventually transmit a failing response to
15220 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
15221 - If the controller claimed responsibility for a stream, but that
15222 stream never finished making its connection, it would live
15223 forever in circuit_wait state. Now we close it after SocksTimeout
15224 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
15225 - Drop begin cells to a hidden service if they come from the middle
15226 of a circuit. Patch from lark.
15227 - When we erroneously receive two EXTEND cells for the same circuit
15228 ID on the same connection, drop the second. Patch from lark.
15229 - Fix a crash that occurs on exit nodes when a nameserver request
15230 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
15231 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
15233 - Do not assume that a stack-allocated character array will be
15234 64-bit aligned on platforms that demand that uint64_t access is
15235 aligned. Possible fix for bug 604.
15236 - Parse dates and IPv4 addresses in a locale- and libc-independent
15237 manner, to avoid platform-dependent behavior on malformed input.
15238 - Build correctly when configured to build outside the main source
15239 path. Patch from Michael Gold.
15240 - We were already rejecting relay begin cells with destination port
15241 of 0. Now also reject extend cells with destination port or address
15242 of 0. Suggested by lark.
15244 o Minor bugfixes (on 0.2.1.x):
15245 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
15246 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
15247 - If we're an exit node, scrub the IP address to which we are exiting
15248 in the logs. Bugfix on 0.2.1.8-alpha.
15251 - On Linux, use the prctl call to re-enable core dumps when the user
15253 - New controller event NEWCONSENSUS that lists the networkstatus
15254 lines for every recommended relay. Now controllers like Torflow
15255 can keep up-to-date on which relays they should be using.
15256 - Update to the "February 26 2009" ip-to-country file.
15259 Changes in version 0.2.0.34 - 2009-02-08
15260 Tor 0.2.0.34 features several more security-related fixes. You should
15261 upgrade, especially if you run an exit relay (remote crash) or a
15262 directory authority (remote infinite loop), or you're on an older
15263 (pre-XP) or not-recently-patched Windows (remote exploit).
15265 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
15266 have many known flaws, and nobody should be using them. You should
15267 upgrade. If you're using a Linux or BSD and its packages are obsolete,
15268 stop using those packages and upgrade anyway.
15271 - Fix an infinite-loop bug on handling corrupt votes under certain
15272 circumstances. Bugfix on 0.2.0.8-alpha.
15273 - Fix a temporary DoS vulnerability that could be performed by
15274 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
15275 - Avoid a potential crash on exit nodes when processing malformed
15276 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
15277 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
15278 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
15281 - Fix compilation on systems where time_t is a 64-bit integer.
15282 Patch from Matthias Drochner.
15283 - Don't consider expiring already-closed client connections. Fixes
15284 bug 893. Bugfix on 0.0.2pre20.
15287 Changes in version 0.2.1.12-alpha - 2009-02-08
15288 Tor 0.2.1.12-alpha features several more security-related fixes. You
15289 should upgrade, especially if you run an exit relay (remote crash) or
15290 a directory authority (remote infinite loop), or you're on an older
15291 (pre-XP) or not-recently-patched Windows (remote exploit). It also
15292 includes a big pile of minor bugfixes and cleanups.
15295 - Fix an infinite-loop bug on handling corrupt votes under certain
15296 circumstances. Bugfix on 0.2.0.8-alpha.
15297 - Fix a temporary DoS vulnerability that could be performed by
15298 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
15299 - Avoid a potential crash on exit nodes when processing malformed
15300 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
15303 - Let controllers actually ask for the "clients_seen" event for
15304 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
15305 reported by Matt Edman.
15306 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
15308 - Fix a bug in address parsing that was preventing bridges or hidden
15309 service targets from being at IPv6 addresses.
15310 - Solve a bug that kept hardware crypto acceleration from getting
15311 enabled when accounting was turned on. Fixes bug 907. Bugfix on
15313 - Remove a bash-ism from configure.in to build properly on non-Linux
15314 platforms. Bugfix on 0.2.1.1-alpha.
15315 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
15316 headers. Bugfix on 0.2.0.10-alpha.
15317 - Don't consider expiring already-closed client connections. Fixes
15318 bug 893. Bugfix on 0.0.2pre20.
15319 - Fix another interesting corner-case of bug 891 spotted by rovv:
15320 Previously, if two hosts had different amounts of clock drift, and
15321 one of them created a new connection with just the wrong timing,
15322 the other might decide to deprecate the new connection erroneously.
15323 Bugfix on 0.1.1.13-alpha.
15324 - Resolve a very rare crash bug that could occur when the user forced
15325 a nameserver reconfiguration during the middle of a nameserver
15326 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
15327 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
15328 Bugfix on 0.2.1.7-alpha.
15329 - If we're using bridges and our network goes away, be more willing
15330 to forgive our bridges and try again when we get an application
15331 request. Bugfix on 0.2.0.x.
15334 - Support platforms where time_t is 64 bits long. (Congratulations,
15335 NetBSD!) Patch from Matthias Drochner.
15336 - Add a 'getinfo status/clients-seen' controller command, in case
15337 controllers want to hear clients_seen events but connect late.
15340 - Disable GCC's strict alias optimization by default, to avoid the
15341 likelihood of its introducing subtle bugs whenever our code violates
15342 the letter of C99's alias rules.
15345 Changes in version 0.2.0.33 - 2009-01-21
15346 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
15347 useful to users. It also finally fixes a bug where a relay or client
15348 that's been off for many days would take a long time to bootstrap.
15350 This update also fixes an important security-related bug reported by
15351 Ilja van Sprundel. You should upgrade. (We'll send out more details
15352 about the bug once people have had some time to upgrade.)
15355 - Fix a heap-corruption bug that may be remotely triggerable on
15356 some platforms. Reported by Ilja van Sprundel.
15359 - When a stream at an exit relay is in state "resolving" or
15360 "connecting" and it receives an "end" relay cell, the exit relay
15361 would silently ignore the end cell and not close the stream. If
15362 the client never closes the circuit, then the exit relay never
15363 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
15364 reported by "wood".
15365 - When sending CREATED cells back for a given circuit, use a 64-bit
15366 connection ID to find the right connection, rather than an addr:port
15367 combination. Now that we can have multiple OR connections between
15368 the same ORs, it is no longer possible to use addr:port to uniquely
15369 identify a connection.
15370 - Bridge relays that had DirPort set to 0 would stop fetching
15371 descriptors shortly after startup, and then briefly resume
15372 after a new bandwidth test and/or after publishing a new bridge
15373 descriptor. Bridge users that try to bootstrap from them would
15374 get a recent networkstatus but would get descriptors from up to
15375 18 hours earlier, meaning most of the descriptors were obsolete
15376 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
15377 - Prevent bridge relays from serving their 'extrainfo' document
15378 to anybody who asks, now that extrainfo docs include potentially
15379 sensitive aggregated client geoip summaries. Bugfix on
15381 - If the cached networkstatus consensus is more than five days old,
15382 discard it rather than trying to use it. In theory it could be
15383 useful because it lists alternate directory mirrors, but in practice
15384 it just means we spend many minutes trying directory mirrors that
15385 are long gone from the network. Also discard router descriptors as
15386 we load them if they are more than five days old, since the onion
15387 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
15390 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
15391 could make gcc generate non-functional binary search code. Bugfix
15393 - Build correctly on platforms without socklen_t.
15394 - Compile without warnings on solaris.
15395 - Avoid potential crash on internal error during signature collection.
15396 Fixes bug 864. Patch from rovv.
15397 - Correct handling of possible malformed authority signing key
15398 certificates with internal signature types. Fixes bug 880.
15399 Bugfix on 0.2.0.3-alpha.
15400 - Fix a hard-to-trigger resource leak when logging credential status.
15402 - When we can't initialize DNS because the network is down, do not
15403 automatically stop Tor from starting. Instead, we retry failed
15404 dns_init() every 10 minutes, and change the exit policy to reject
15405 *:* until one succeeds. Fixes bug 691.
15406 - Use 64 bits instead of 32 bits for connection identifiers used with
15407 the controller protocol, to greatly reduce risk of identifier reuse.
15408 - When we're choosing an exit node for a circuit, and we have
15409 no pending streams, choose a good general exit rather than one that
15410 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
15411 - Fix another case of assuming, when a specific exit is requested,
15412 that we know more than the user about what hosts it allows.
15413 Fixes one case of bug 752. Patch from rovv.
15414 - Clip the MaxCircuitDirtiness config option to a minimum of 10
15415 seconds. Warn the user if lower values are given in the
15416 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
15417 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
15418 user if lower values are given in the configuration. Bugfix on
15419 0.1.1.17-rc. Patch by Sebastian.
15420 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
15421 the cache because we already had a v0 descriptor with the same ID.
15422 Bugfix on 0.2.0.18-alpha.
15423 - Fix a race condition when freeing keys shared between main thread
15424 and CPU workers that could result in a memory leak. Bugfix on
15425 0.1.0.1-rc. Fixes bug 889.
15426 - Send a valid END cell back when a client tries to connect to a
15427 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
15428 840. Patch from rovv.
15429 - Check which hops rendezvous stream cells are associated with to
15430 prevent possible guess-the-streamid injection attacks from
15431 intermediate hops. Fixes another case of bug 446. Based on patch
15433 - If a broken client asks a non-exit router to connect somewhere,
15434 do not even do the DNS lookup before rejecting the connection.
15435 Fixes another case of bug 619. Patch from rovv.
15436 - When a relay gets a create cell it can't decrypt (e.g. because it's
15437 using the wrong onion key), we were dropping it and letting the
15438 client time out. Now actually answer with a destroy cell. Fixes
15439 bug 904. Bugfix on 0.0.2pre8.
15441 o Minor bugfixes (hidden services):
15442 - Do not throw away existing introduction points on SIGHUP. Bugfix on
15443 0.0.6pre1. Patch by Karsten. Fixes bug 874.
15446 - Report the case where all signatures in a detached set are rejected
15447 differently than the case where there is an error handling the
15449 - When we realize that another process has modified our cached
15450 descriptors, print out a more useful error message rather than
15451 triggering an assertion. Fixes bug 885. Patch from Karsten.
15452 - Implement the 0x20 hack to better resist DNS poisoning: set the
15453 case on outgoing DNS requests randomly, and reject responses that do
15454 not match the case correctly. This logic can be disabled with the
15455 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
15456 of servers that do not reliably preserve case in replies. See
15457 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
15459 - Check DNS replies for more matching fields to better resist DNS
15461 - Never use OpenSSL compression: it wastes RAM and CPU trying to
15462 compress cells, which are basically all encrypted, compressed, or
15466 Changes in version 0.2.1.11-alpha - 2009-01-20
15467 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
15468 week it will take a long time to bootstrap again" bug. It also fixes
15469 an important security-related bug reported by Ilja van Sprundel. You
15470 should upgrade. (We'll send out more details about the bug once people
15471 have had some time to upgrade.)
15474 - Fix a heap-corruption bug that may be remotely triggerable on
15475 some platforms. Reported by Ilja van Sprundel.
15478 - Discard router descriptors as we load them if they are more than
15479 five days old. Otherwise if Tor is off for a long time and then
15480 starts with cached descriptors, it will try to use the onion
15481 keys in those obsolete descriptors when building circuits. Bugfix
15482 on 0.2.0.x. Fixes bug 887.
15485 - Try to make sure that the version of Libevent we're running with
15486 is binary-compatible with the one we built with. May address bug
15488 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
15489 for bug 905. Bugfix on 0.2.1.7-alpha.
15490 - Add a new --enable-local-appdata configuration switch to change
15491 the default location of the datadir on win32 from APPDATA to
15492 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
15493 entirely. Patch from coderman.
15496 - Make outbound DNS packets respect the OutboundBindAddress setting.
15497 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
15498 - When our circuit fails at the first hop (e.g. we get a destroy
15499 cell back), avoid using that OR connection anymore, and also
15500 tell all the one-hop directory requests waiting for it that they
15501 should fail. Bugfix on 0.2.1.3-alpha.
15502 - In the torify(1) manpage, mention that tsocks will leak your
15506 Changes in version 0.2.1.10-alpha - 2009-01-06
15507 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
15508 would make the bridge relay not so useful if it had DirPort set to 0,
15509 and one that could let an attacker learn a little bit of information
15510 about the bridge's users), and a bug that would cause your Tor relay
15511 to ignore a circuit create request it can't decrypt (rather than reply
15512 with an error). It also fixes a wide variety of other bugs.
15515 - If the cached networkstatus consensus is more than five days old,
15516 discard it rather than trying to use it. In theory it could
15517 be useful because it lists alternate directory mirrors, but in
15518 practice it just means we spend many minutes trying directory
15519 mirrors that are long gone from the network. Helps bug 887 a bit;
15521 - Bridge relays that had DirPort set to 0 would stop fetching
15522 descriptors shortly after startup, and then briefly resume
15523 after a new bandwidth test and/or after publishing a new bridge
15524 descriptor. Bridge users that try to bootstrap from them would
15525 get a recent networkstatus but would get descriptors from up to
15526 18 hours earlier, meaning most of the descriptors were obsolete
15527 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
15528 - Prevent bridge relays from serving their 'extrainfo' document
15529 to anybody who asks, now that extrainfo docs include potentially
15530 sensitive aggregated client geoip summaries. Bugfix on
15534 - New controller event "clients_seen" to report a geoip-based summary
15535 of which countries we've seen clients from recently. Now controllers
15536 like Vidalia can show bridge operators that they're actually making
15538 - Build correctly against versions of OpenSSL 0.9.8 or later built
15539 without support for deprecated functions.
15540 - Update to the "December 19 2008" ip-to-country file.
15542 o Minor bugfixes (on 0.2.0.x):
15543 - Authorities now vote for the Stable flag for any router whose
15544 weighted MTBF is at least 5 days, regardless of the mean MTBF.
15545 - Do not remove routers as too old if we do not have any consensus
15546 document. Bugfix on 0.2.0.7-alpha.
15547 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
15548 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
15549 - When an exit relay resolves a stream address to a local IP address,
15550 do not just keep retrying that same exit relay over and
15551 over. Instead, just close the stream. Addresses bug 872. Bugfix
15552 on 0.2.0.32. Patch from rovv.
15553 - If a hidden service sends us an END cell, do not consider
15554 retrying the connection; just close it. Patch from rovv.
15555 - When we made bridge authorities stop serving bridge descriptors over
15556 unencrypted links, we also broke DirPort reachability testing for
15557 bridges. So bridges with a non-zero DirPort were printing spurious
15558 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
15559 - When a relay gets a create cell it can't decrypt (e.g. because it's
15560 using the wrong onion key), we were dropping it and letting the
15561 client time out. Now actually answer with a destroy cell. Fixes
15562 bug 904. Bugfix on 0.0.2pre8.
15563 - Squeeze 2-5% out of client performance (according to oprofile) by
15564 improving the implementation of some policy-manipulation functions.
15566 o Minor bugfixes (on 0.2.1.x):
15567 - Make get_interface_address() function work properly again; stop
15568 guessing the wrong parts of our address as our address.
15569 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
15570 send on that circuit. Otherwise we might violate the proposal-110
15571 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
15573 - When we're sending non-EXTEND cells to the first hop in a circuit,
15574 for example to use an encrypted directory connection, we don't need
15575 to use RELAY_EARLY cells: the first hop knows what kind of cell
15576 it is, and nobody else can even see the cell type. Conserving
15577 RELAY_EARLY cells makes it easier to cannibalize circuits like
15579 - Stop logging nameserver addresses in reverse order.
15580 - If we are retrying a directory download slowly over and over, do
15581 not automatically give up after the 254th failure. Bugfix on
15583 - Resume reporting accurate "stream end" reasons to the local control
15584 port. They were lost in the changes for Proposal 148. Bugfix on
15587 o Deprecated and removed features:
15588 - The old "tor --version --version" command, which would print out
15589 the subversion "Id" of most of the source files, is now removed. It
15590 turned out to be less useful than we'd expected, and harder to
15593 o Code simplifications and refactoring:
15594 - Change our header file guard macros to be less likely to conflict
15595 with system headers. Adam Langley noticed that we were conflicting
15596 with log.h on Android.
15597 - Tool-assisted documentation cleanup. Nearly every function or
15598 static variable in Tor should have its own documentation now.
15601 Changes in version 0.2.1.9-alpha - 2008-12-25
15602 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
15604 o New directory authorities:
15605 - gabelmoo (the authority run by Karsten Loesing) now has a new
15609 - Never use a connection with a mismatched address to extend a
15610 circuit, unless that connection is canonical. A canonical
15611 connection is one whose address is authenticated by the router's
15612 identity key, either in a NETINFO cell or in a router descriptor.
15613 - Avoid a possible memory corruption bug when receiving hidden service
15614 descriptors. Bugfix on 0.2.1.6-alpha.
15617 - Fix a logic error that would automatically reject all but the first
15618 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
15619 part of bug 813/868. Bug spotted by coderman.
15620 - When a stream at an exit relay is in state "resolving" or
15621 "connecting" and it receives an "end" relay cell, the exit relay
15622 would silently ignore the end cell and not close the stream. If
15623 the client never closes the circuit, then the exit relay never
15624 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
15625 reported by "wood".
15626 - When we can't initialize DNS because the network is down, do not
15627 automatically stop Tor from starting. Instead, retry failed
15628 dns_init() every 10 minutes, and change the exit policy to reject
15629 *:* until one succeeds. Fixes bug 691.
15632 - Give a better error message when an overzealous init script says
15633 "sudo -u username tor --user username". Makes Bug 882 easier for
15635 - When a directory authority gives us a new guess for our IP address,
15636 log which authority we used. Hopefully this will help us debug
15637 the recent complaints about bad IP address guesses.
15638 - Detect svn revision properly when we're using git-svn.
15639 - Try not to open more than one descriptor-downloading connection
15640 to an authority at once. This should reduce load on directory
15641 authorities. Fixes bug 366.
15642 - Add cross-certification to newly generated certificates, so that
15643 a signing key is enough information to look up a certificate.
15644 Partial implementation of proposal 157.
15645 - Start serving certificates by <identity digest, signing key digest>
15646 pairs. Partial implementation of proposal 157.
15647 - Clients now never report any stream end reason except 'MISC'.
15648 Implements proposal 148.
15649 - On platforms with a maximum syslog string length, truncate syslog
15650 messages to that length ourselves, rather than relying on the
15651 system to do it for us.
15652 - Optimize out calls to time(NULL) that occur for every IO operation,
15653 or for every cell. On systems where time() is a slow syscall,
15654 this fix will be slightly helpful.
15655 - Exit servers can now answer resolve requests for ip6.arpa addresses.
15656 - When we download a descriptor that we then immediately (as
15657 a directory authority) reject, do not retry downloading it right
15658 away. Should save some bandwidth on authorities. Fix for bug
15659 888. Patch by Sebastian Hahn.
15660 - When a download gets us zero good descriptors, do not notify
15661 Tor that new directory information has arrived.
15662 - Avoid some nasty corner cases in the logic for marking connections
15663 as too old or obsolete or noncanonical for circuits. Partial
15666 o Minor features (controller):
15667 - New CONSENSUS_ARRIVED event to note when a new consensus has
15668 been fetched and validated.
15669 - When we realize that another process has modified our cached
15670 descriptors file, print out a more useful error message rather
15671 than triggering an assertion. Fixes bug 885. Patch from Karsten.
15672 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
15673 controllers to prevent SIGHUP from reloading the
15674 configuration. Fixes bug 856.
15677 - Resume using the correct "REASON=" stream when telling the
15678 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
15679 - When a canonical connection appears later in our internal list
15680 than a noncanonical one for a given OR ID, always use the
15681 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
15683 - Clip the MaxCircuitDirtiness config option to a minimum of 10
15684 seconds. Warn the user if lower values are given in the
15685 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
15686 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
15687 user if lower values are given in the configuration. Bugfix on
15688 0.1.1.17-rc. Patch by Sebastian.
15689 - Fix a race condition when freeing keys shared between main thread
15690 and CPU workers that could result in a memory leak. Bugfix on
15691 0.1.0.1-rc. Fixes bug 889.
15693 o Minor bugfixes (hidden services):
15694 - Do not throw away existing introduction points on SIGHUP (bugfix on
15695 0.0.6pre1); also, do not stall hidden services because we're
15696 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
15697 by John Brooks. Patch by Karsten. Fixes bug 874.
15698 - Fix a memory leak when we decline to add a v2 rendezvous
15699 descriptor to the cache because we already had a v0 descriptor
15700 with the same ID. Bugfix on 0.2.0.18-alpha.
15702 o Deprecated and removed features:
15703 - RedirectExits has been removed. It was deprecated since
15705 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
15706 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
15707 - Cell pools are now always enabled; --disable-cell-pools is ignored.
15709 o Code simplifications and refactoring:
15710 - Rename the confusing or_is_obsolete field to the more appropriate
15711 is_bad_for_new_circs, and move it to or_connection_t where it
15713 - Move edge-only flags from connection_t to edge_connection_t: not
15714 only is this better coding, but on machines of plausible alignment,
15715 it should save 4-8 bytes per connection_t. "Every little bit helps."
15716 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
15717 for consistency; keep old option working for backward compatibility.
15718 - Simplify the code for finding connections to use for a circuit.
15721 Changes in version 0.2.1.8-alpha - 2008-12-08
15722 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
15723 builds better on unusual platforms like Solaris and old OS X, and
15724 fixes a variety of other issues.
15727 - New DirPortFrontPage option that takes an html file and publishes
15728 it as "/" on the DirPort. Now relay operators can provide a
15729 disclaimer without needing to set up a separate webserver. There's
15730 a sample disclaimer in contrib/tor-exit-notice.html.
15733 - When the client is choosing entry guards, now it selects at most
15734 one guard from a given relay family. Otherwise we could end up with
15735 all of our entry points into the network run by the same operator.
15736 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
15739 - Fix a DOS opportunity during the voting signature collection process
15740 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
15741 - Fix a possible segfault when establishing an exit connection. Bugfix
15745 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
15747 - Made Tor a little less aggressive about deleting expired
15748 certificates. Partial fix for bug 854.
15749 - Stop doing unaligned memory access that generated bus errors on
15750 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
15751 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
15752 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
15753 - Make USR2 log-level switch take effect immediately. Bugfix on
15755 - If one win32 nameserver fails to get added, continue adding the
15756 rest, and don't automatically fail.
15757 - Use fcntl() for locking when flock() is not available. Should fix
15758 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
15759 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
15760 could make gcc generate non-functional binary search code. Bugfix
15762 - Build correctly on platforms without socklen_t.
15763 - Avoid potential crash on internal error during signature collection.
15764 Fixes bug 864. Patch from rovv.
15765 - Do not use C's stdio library for writing to log files. This will
15766 improve logging performance by a minute amount, and will stop
15767 leaking fds when our disk is full. Fixes bug 861.
15768 - Stop erroneous use of O_APPEND in cases where we did not in fact
15769 want to re-seek to the end of a file before every last write().
15770 - Correct handling of possible malformed authority signing key
15771 certificates with internal signature types. Fixes bug 880. Bugfix
15773 - Fix a hard-to-trigger resource leak when logging credential status.
15777 - Directory mirrors no longer fetch the v1 directory or
15778 running-routers files. They are obsolete, and nobody asks for them
15779 anymore. This is the first step to making v1 authorities obsolete.
15781 o Minor features (controller):
15782 - Return circuit purposes in response to GETINFO circuit-status. Fixes
15786 Changes in version 0.2.0.32 - 2008-11-20
15787 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
15788 packages (and maybe other packages) noticed by Theo de Raadt, fixes
15789 a smaller security flaw that might allow an attacker to access local
15790 services, further improves hidden service performance, and fixes a
15791 variety of other issues.
15794 - The "User" and "Group" config options did not clear the
15795 supplementary group entries for the Tor process. The "User" option
15796 is now more robust, and we now set the groups to the specified
15797 user's primary group. The "Group" option is now ignored. For more
15798 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
15799 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
15800 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
15801 - The "ClientDNSRejectInternalAddresses" config option wasn't being
15802 consistently obeyed: if an exit relay refuses a stream because its
15803 exit policy doesn't allow it, we would remember what IP address
15804 the relay said the destination address resolves to, even if it's
15805 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
15808 - Fix a DOS opportunity during the voting signature collection process
15809 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
15811 o Major bugfixes (hidden services):
15812 - When fetching v0 and v2 rendezvous service descriptors in parallel,
15813 we were failing the whole hidden service request when the v0
15814 descriptor fetch fails, even if the v2 fetch is still pending and
15815 might succeed. Similarly, if the last v2 fetch fails, we were
15816 failing the whole hidden service request even if a v0 fetch is
15817 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
15818 - When extending a circuit to a hidden service directory to upload a
15819 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
15820 requests failed, because the router descriptor has not been
15821 downloaded yet. In these cases, do not attempt to upload the
15822 rendezvous descriptor, but wait until the router descriptor is
15823 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
15824 descriptor from a hidden service directory for which the router
15825 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
15829 - Fix several infrequent memory leaks spotted by Coverity.
15830 - When testing for libevent functions, set the LDFLAGS variable
15831 correctly. Found by Riastradh.
15832 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
15833 bootstrapping with tunneled directory connections. Bugfix on
15834 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
15835 - When asked to connect to A.B.exit:80, if we don't know the IP for A
15836 and we know that server B rejects most-but-not all connections to
15837 port 80, we would previously reject the connection. Now, we assume
15838 the user knows what they were asking for. Fixes bug 752. Bugfix
15839 on 0.0.9rc5. Diagnosed by BarkerJr.
15840 - If we overrun our per-second write limits a little, count this as
15841 having used up our write allocation for the second, and choke
15842 outgoing directory writes. Previously, we had only counted this when
15843 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
15844 Bugfix on 0.2.0.x (??).
15845 - Remove the old v2 directory authority 'lefkada' from the default
15846 list. It has been gone for many months.
15847 - Stop doing unaligned memory access that generated bus errors on
15848 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
15849 - Make USR2 log-level switch take effect immediately. Bugfix on
15852 o Minor bugfixes (controller):
15853 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
15854 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
15857 Changes in version 0.2.1.7-alpha - 2008-11-08
15858 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
15859 packages (and maybe other packages) noticed by Theo de Raadt, fixes
15860 a smaller security flaw that might allow an attacker to access local
15861 services, adds better defense against DNS poisoning attacks on exit
15862 relays, further improves hidden service performance, and fixes a
15863 variety of other issues.
15866 - The "ClientDNSRejectInternalAddresses" config option wasn't being
15867 consistently obeyed: if an exit relay refuses a stream because its
15868 exit policy doesn't allow it, we would remember what IP address
15869 the relay said the destination address resolves to, even if it's
15870 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
15871 - The "User" and "Group" config options did not clear the
15872 supplementary group entries for the Tor process. The "User" option
15873 is now more robust, and we now set the groups to the specified
15874 user's primary group. The "Group" option is now ignored. For more
15875 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
15876 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
15877 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
15878 - Do not use or believe expired v3 authority certificates. Patch
15879 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
15882 - Now NodeFamily and MyFamily config options allow spaces in
15883 identity fingerprints, so it's easier to paste them in.
15884 Suggested by Lucky Green.
15885 - Implement the 0x20 hack to better resist DNS poisoning: set the
15886 case on outgoing DNS requests randomly, and reject responses that do
15887 not match the case correctly. This logic can be disabled with the
15888 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
15889 of servers that do not reliably preserve case in replies. See
15890 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
15892 - Preserve case in replies to DNSPort requests in order to support
15893 the 0x20 hack for resisting DNS poisoning attacks.
15895 o Hidden service performance improvements:
15896 - When the client launches an introduction circuit, retry with a
15897 new circuit after 30 seconds rather than 60 seconds.
15898 - Launch a second client-side introduction circuit in parallel
15899 after a delay of 15 seconds (based on work by Christian Wilms).
15900 - Hidden services start out building five intro circuits rather
15901 than three, and when the first three finish they publish a service
15902 descriptor using those. Now we publish our service descriptor much
15903 faster after restart.
15906 - Minor fix in the warning messages when you're having problems
15907 bootstrapping; also, be more forgiving of bootstrap problems when
15908 we're still making incremental progress on a given bootstrap phase.
15909 - When we're choosing an exit node for a circuit, and we have
15910 no pending streams, choose a good general exit rather than one that
15911 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
15912 - Send a valid END cell back when a client tries to connect to a
15913 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
15914 840. Patch from rovv.
15915 - If a broken client asks a non-exit router to connect somewhere,
15916 do not even do the DNS lookup before rejecting the connection.
15917 Fixes another case of bug 619. Patch from rovv.
15918 - Fix another case of assuming, when a specific exit is requested,
15919 that we know more than the user about what hosts it allows.
15920 Fixes another case of bug 752. Patch from rovv.
15921 - Check which hops rendezvous stream cells are associated with to
15922 prevent possible guess-the-streamid injection attacks from
15923 intermediate hops. Fixes another case of bug 446. Based on patch
15925 - Avoid using a negative right-shift when comparing 32-bit
15926 addresses. Possible fix for bug 845 and bug 811.
15927 - Make the assert_circuit_ok() function work correctly on circuits that
15928 have already been marked for close.
15929 - Fix read-off-the-end-of-string error in unit tests when decoding
15930 introduction points.
15931 - Fix uninitialized size field for memory area allocation: may improve
15932 memory performance during directory parsing.
15933 - Treat duplicate certificate fetches as failures, so that we do
15934 not try to re-fetch an expired certificate over and over and over.
15935 - Do not say we're fetching a certificate when we'll in fact skip it
15936 because of a pending download.
15939 Changes in version 0.2.1.6-alpha - 2008-09-30
15940 Tor 0.2.1.6-alpha further improves performance and robustness of
15941 hidden services, starts work on supporting per-country relay selection,
15942 and fixes a variety of smaller issues.
15945 - Implement proposal 121: make it possible to build hidden services
15946 that only certain clients are allowed to connect to. This is
15947 enforced at several points, so that unauthorized clients are unable
15948 to send INTRODUCE cells to the service, or even (depending on the
15949 type of authentication) to learn introduction points. This feature
15950 raises the bar for certain kinds of active attacks against hidden
15951 services. Code by Karsten Loesing.
15952 - Relays now store and serve v2 hidden service descriptors by default,
15953 i.e., the new default value for HidServDirectoryV2 is 1. This is
15954 the last step in proposal 114, which aims to make hidden service
15955 lookups more reliable.
15956 - Start work to allow node restrictions to include country codes. The
15957 syntax to exclude nodes in a country with country code XX is
15958 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
15959 refinement to decide what config options should take priority if
15960 you ask to both use a particular node and exclude it.
15961 - Allow ExitNodes list to include IP ranges and country codes, just
15962 like the Exclude*Nodes lists. Patch from Robert Hogan.
15965 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
15966 Tor to fail to start if you had it configured to use a bridge
15967 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
15968 - When extending a circuit to a hidden service directory to upload a
15969 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
15970 requests failed, because the router descriptor had not been
15971 downloaded yet. In these cases, we now wait until the router
15972 descriptor is downloaded, and then retry. Likewise, clients
15973 now skip over a hidden service directory if they don't yet have
15974 its router descriptor, rather than futilely requesting it and
15975 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
15977 - When fetching v0 and v2 rendezvous service descriptors in parallel,
15978 we were failing the whole hidden service request when the v0
15979 descriptor fetch fails, even if the v2 fetch is still pending and
15980 might succeed. Similarly, if the last v2 fetch fails, we were
15981 failing the whole hidden service request even if a v0 fetch is
15982 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
15983 - DNS replies need to have names matching their requests, but
15984 these names should be in the questions section, not necessarily
15985 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
15988 - Update to the "September 1 2008" ip-to-country file.
15989 - Allow ports 465 and 587 in the default exit policy again. We had
15990 rejected them in 0.1.0.15, because back in 2005 they were commonly
15991 misconfigured and ended up as spam targets. We hear they are better
15992 locked down these days.
15993 - Use a lockfile to make sure that two Tor processes are not
15994 simultaneously running with the same datadir.
15995 - Serve the latest v3 networkstatus consensus via the control
15996 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
15997 - Better logging about stability/reliability calculations on directory
15999 - Drop the requirement to have an open dir port for storing and
16000 serving v2 hidden service descriptors.
16001 - Directory authorities now serve a /tor/dbg-stability.txt URL to
16002 help debug WFU and MTBF calculations.
16003 - Implement most of Proposal 152: allow specialized servers to permit
16004 single-hop circuits, and clients to use those servers to build
16005 single-hop circuits when using a specialized controller. Patch
16006 from Josh Albrecht. Resolves feature request 768.
16007 - Add a -p option to tor-resolve for specifying the SOCKS port: some
16008 people find host:port too confusing.
16009 - Make TrackHostExit mappings expire a while after their last use, not
16010 after their creation. Patch from Robert Hogan.
16011 - Provide circuit purposes along with circuit events to the controller.
16014 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
16016 - Fixed some memory leaks -- some quite frequent, some almost
16017 impossible to trigger -- based on results from Coverity.
16018 - When testing for libevent functions, set the LDFLAGS variable
16019 correctly. Found by Riastradh.
16020 - Fix an assertion bug in parsing policy-related options; possible fix
16022 - Catch and report a few more bootstrapping failure cases when Tor
16023 fails to establish a TCP connection. Cleanup on 0.2.1.x.
16024 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
16025 bootstrapping with tunneled directory connections. Bugfix on
16026 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
16027 - When asked to connect to A.B.exit:80, if we don't know the IP for A
16028 and we know that server B rejects most-but-not all connections to
16029 port 80, we would previously reject the connection. Now, we assume
16030 the user knows what they were asking for. Fixes bug 752. Bugfix
16031 on 0.0.9rc5. Diagnosed by BarkerJr.
16032 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
16033 service directories if they have no advertised dir port. Bugfix
16035 - If we overrun our per-second write limits a little, count this as
16036 having used up our write allocation for the second, and choke
16037 outgoing directory writes. Previously, we had only counted this when
16038 we had met our limits precisely. Fixes bug 824. Patch by rovv.
16039 Bugfix on 0.2.0.x (??).
16040 - Avoid a "0 divided by 0" calculation when calculating router uptime
16041 at directory authorities. Bugfix on 0.2.0.8-alpha.
16042 - Make DNS resolved controller events into "CLOSED", not
16043 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
16045 - Fix a bug where an unreachable relay would establish enough
16046 reachability testing circuits to do a bandwidth test -- if
16047 we already have a connection to the middle hop of the testing
16048 circuit, then it could establish the last hop by using the existing
16049 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
16050 circuits no longer use entry guards in 0.2.1.3-alpha.
16051 - If we have correct permissions on $datadir, we complain to stdout
16052 and fail to start. But dangerous permissions on
16053 $datadir/cached-status/ would cause us to open a log and complain
16054 there. Now complain to stdout and fail to start in both cases. Fixes
16055 bug 820, reported by seeess.
16056 - Remove the old v2 directory authority 'lefkada' from the default
16057 list. It has been gone for many months.
16059 o Code simplifications and refactoring:
16060 - Revise the connection_new functions so that a more typesafe variant
16061 exists. This will work better with Coverity, and let us find any
16062 actual mistakes we're making here.
16063 - Refactor unit testing logic so that dmalloc can be used sensibly
16064 with unit tests to check for memory leaks.
16065 - Move all hidden-service related fields from connection and circuit
16066 structure to substructures: this way they won't eat so much memory.
16069 Changes in version 0.2.0.31 - 2008-09-03
16070 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
16071 a big bug we're seeing where in rare cases traffic from one Tor stream
16072 gets mixed into another stream, and fixes a variety of smaller issues.
16075 - Make sure that two circuits can never exist on the same connection
16076 with the same circuit ID, even if one is marked for close. This
16077 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
16078 - Relays now reject risky extend cells: if the extend cell includes
16079 a digest of all zeroes, or asks to extend back to the relay that
16080 sent the extend cell, tear down the circuit. Ideas suggested
16082 - If not enough of our entry guards are available so we add a new
16083 one, we might use the new one even if it overlapped with the
16084 current circuit's exit relay (or its family). Anonymity bugfix
16085 pointed out by rovv.
16088 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
16089 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
16090 - Correctly detect the presence of the linux/netfilter_ipv4.h header
16091 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
16092 - Pick size of default geoip filename string correctly on windows.
16093 Fixes bug 806. Bugfix on 0.2.0.30.
16094 - Make the autoconf script accept the obsolete --with-ssl-dir
16095 option as an alias for the actually-working --with-openssl-dir
16096 option. Fix the help documentation to recommend --with-openssl-dir.
16097 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
16098 - When using the TransPort option on OpenBSD, and using the User
16099 option to change UID and drop privileges, make sure to open
16100 /dev/pf before dropping privileges. Fixes bug 782. Patch from
16101 Christopher Davis. Bugfix on 0.1.2.1-alpha.
16102 - Try to attach connections immediately upon receiving a RENDEZVOUS2
16103 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
16104 on the client side when connecting to a hidden service. Bugfix
16105 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
16106 - When closing an application-side connection because its circuit is
16107 getting torn down, generate the stream event correctly. Bugfix on
16108 0.1.2.x. Anonymous patch.
16111 Changes in version 0.2.1.5-alpha - 2008-08-31
16112 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
16113 in a lot of the infrastructure for adding authorization to hidden
16114 services, lays the groundwork for having clients read their load
16115 balancing information out of the networkstatus consensus rather than
16116 the individual router descriptors, addresses two potential anonymity
16117 issues, and fixes a variety of smaller issues.
16120 - Convert many internal address representations to optionally hold
16122 - Generate and accept IPv6 addresses in many protocol elements.
16123 - Make resolver code handle nameservers located at ipv6 addresses.
16124 - Begin implementation of proposal 121 ("Client authorization for
16125 hidden services"): configure hidden services with client
16126 authorization, publish descriptors for them, and configure
16127 authorization data for hidden services at clients. The next
16128 step is to actually access hidden services that perform client
16130 - More progress toward proposal 141: Network status consensus
16131 documents and votes now contain bandwidth information for each
16132 router and a summary of that router's exit policy. Eventually this
16133 will be used by clients so that they do not have to download every
16134 known descriptor before building circuits.
16136 o Major bugfixes (on 0.2.0.x and before):
16137 - When sending CREATED cells back for a given circuit, use a 64-bit
16138 connection ID to find the right connection, rather than an addr:port
16139 combination. Now that we can have multiple OR connections between
16140 the same ORs, it is no longer possible to use addr:port to uniquely
16141 identify a connection.
16142 - Relays now reject risky extend cells: if the extend cell includes
16143 a digest of all zeroes, or asks to extend back to the relay that
16144 sent the extend cell, tear down the circuit. Ideas suggested
16146 - If not enough of our entry guards are available so we add a new
16147 one, we might use the new one even if it overlapped with the
16148 current circuit's exit relay (or its family). Anonymity bugfix
16149 pointed out by rovv.
16152 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
16153 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
16154 - When using the TransPort option on OpenBSD, and using the User
16155 option to change UID and drop privileges, make sure to open /dev/pf
16156 before dropping privileges. Fixes bug 782. Patch from Christopher
16157 Davis. Bugfix on 0.1.2.1-alpha.
16158 - Correctly detect the presence of the linux/netfilter_ipv4.h header
16159 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
16160 - Add a missing safe_str() call for a debug log message.
16161 - Use 64 bits instead of 32 bits for connection identifiers used with
16162 the controller protocol, to greatly reduce risk of identifier reuse.
16163 - Make the autoconf script accept the obsolete --with-ssl-dir
16164 option as an alias for the actually-working --with-openssl-dir
16165 option. Fix the help documentation to recommend --with-openssl-dir.
16166 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
16169 - Rate-limit too-many-sockets messages: when they happen, they happen
16170 a lot. Resolves bug 748.
16171 - Resist DNS poisoning a little better by making sure that names in
16172 answer sections match.
16173 - Print the SOCKS5 error message string as well as the error code
16174 when a tor-resolve request fails. Patch from Jacob.
16177 Changes in version 0.2.1.4-alpha - 2008-08-04
16178 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
16181 - The address part of exit policies was not correctly written
16182 to router descriptors. This generated router descriptors that failed
16183 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
16185 - Tor triggered a false assert when extending a circuit to a relay
16186 but we already have a connection open to that relay. Noticed by
16187 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
16190 - Fix a hidden service logging bug: in some edge cases, the router
16191 descriptor of a previously picked introduction point becomes
16192 obsolete and we need to give up on it rather than continually
16193 complaining that it has become obsolete. Observed by xiando. Bugfix
16196 o Removed features:
16197 - Take out the TestVia config option, since it was a workaround for
16198 a bug that was fixed in Tor 0.1.1.21.
16201 Changes in version 0.2.1.3-alpha - 2008-08-03
16202 Tor 0.2.1.3-alpha implements most of the pieces to prevent
16203 infinite-length circuit attacks (see proposal 110); fixes a bug that
16204 might cause exit relays to corrupt streams they send back; allows
16205 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
16206 ExcludeExitNodes config options; and fixes a big pile of bugs.
16208 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
16209 - Send a bootstrap problem "warn" event on the first problem if the
16210 reason is NO_ROUTE (that is, our network is down).
16213 - Implement most of proposal 110: The first K cells to be sent
16214 along a circuit are marked as special "early" cells; only K "early"
16215 cells will be allowed. Once this code is universal, we can block
16216 certain kinds of DOS attack by requiring that EXTEND commands must
16217 be sent using an "early" cell.
16220 - Try to attach connections immediately upon receiving a RENDEZVOUS2
16221 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
16222 on the client side when connecting to a hidden service. Bugfix
16223 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
16224 - Ensure that two circuits can never exist on the same connection
16225 with the same circuit ID, even if one is marked for close. This
16226 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
16229 - When relays do their initial bandwidth measurement, don't limit
16230 to just our entry guards for the test circuits. Otherwise we tend
16231 to have multiple test circuits going through a single entry guard,
16232 which makes our bandwidth test less accurate. Fixes part of bug 654;
16233 patch contributed by Josh Albrecht.
16234 - Add an ExcludeExitNodes option so users can list a set of nodes
16235 that should be be excluded from the exit node position, but
16236 allowed elsewhere. Implements proposal 151.
16237 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
16238 ExcludeNodes and ExcludeExitNodes lists.
16239 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
16240 be more efficient. Formerly it was quadratic in the number of
16241 servers; now it should be linear. Fixes bug 509.
16242 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
16243 and n_conn_id_digest fields into a separate structure that's
16244 only needed when the circuit has not yet attached to an n_conn.
16247 - Change the contrib/tor.logrotate script so it makes the new
16248 logs as "_tor:_tor" rather than the default, which is generally
16249 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
16250 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
16251 warnings (occasionally), but it can also cause the compiler to
16252 eliminate error-checking code. Suggested by Peter Gutmann.
16253 - When a hidden service is giving up on an introduction point candidate
16254 that was not included in the last published rendezvous descriptor,
16255 don't reschedule publication of the next descriptor. Fixes bug 763.
16257 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
16258 HiddenServiceExcludeNodes as obsolete: they never worked properly,
16259 and nobody claims to be using them. Fixes bug 754. Bugfix on
16260 0.1.0.1-rc. Patch from Christian Wilms.
16261 - Fix a small alignment and memory-wasting bug on buffer chunks.
16264 o Minor bugfixes (controller):
16265 - When closing an application-side connection because its circuit
16266 is getting torn down, generate the stream event correctly.
16267 Bugfix on 0.1.2.x. Anonymous patch.
16269 o Removed features:
16270 - Remove all backward-compatibility code to support relays running
16271 versions of Tor so old that they no longer work at all on the
16275 Changes in version 0.2.0.30 - 2008-07-15
16277 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
16278 warnings (occasionally), but it can also cause the compiler to
16279 eliminate error-checking code. Suggested by Peter Gutmann.
16282 Changes in version 0.2.0.29-rc - 2008-07-08
16283 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
16284 hidden-service performance bugs, and fixes a bunch of smaller bugs.
16287 - If you have more than one bridge but don't know their keys,
16288 you would only launch a request for the descriptor of the first one
16289 on your list. (Tor considered launching requests for the others, but
16290 found that it already had a connection on the way for $0000...0000
16291 so it didn't open another.) Bugfix on 0.2.0.x.
16292 - If you have more than one bridge but don't know their keys, and the
16293 connection to one of the bridges failed, you would cancel all
16294 pending bridge connections. (After all, they all have the same
16295 digest.) Bugfix on 0.2.0.x.
16296 - When a hidden service was trying to establish an introduction point,
16297 and Tor had built circuits preemptively for such purposes, we
16298 were ignoring all the preemptive circuits and launching a new one
16299 instead. Bugfix on 0.2.0.14-alpha.
16300 - When a hidden service was trying to establish an introduction point,
16301 and Tor *did* manage to reuse one of the preemptively built
16302 circuits, it didn't correctly remember which one it used,
16303 so it asked for another one soon after, until there were no
16304 more preemptive circuits, at which point it launched one from
16305 scratch. Bugfix on 0.0.9.x.
16306 - Make directory servers include the X-Your-Address-Is: http header in
16307 their responses even for begin_dir conns. Now clients who only
16308 ever use begin_dir connections still have a way to learn their IP
16309 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
16312 - Fix a macro/CPP interaction that was confusing some compilers:
16313 some GCCs don't like #if/#endif pairs inside macro arguments.
16315 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
16316 Fixes bug 704; fix from Steven Murdoch.
16317 - When opening /dev/null in finish_daemonize(), do not pass the
16318 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
16319 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
16320 - Correctly detect transparent proxy support on Linux hosts that
16321 require in.h to be included before netfilter_ipv4.h. Patch
16323 - Disallow session resumption attempts during the renegotiation
16324 stage of the v2 handshake protocol. Clients should never be trying
16325 session resumption at this point, but apparently some did, in
16326 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
16327 found by Geoff Goodell.
16330 Changes in version 0.2.1.2-alpha - 2008-06-20
16331 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
16332 make it easier to set up your own private Tor network; fixes several
16333 big bugs with using more than one bridge relay; fixes a big bug with
16334 offering hidden services quickly after Tor starts; and uses a better
16335 API for reporting potential bootstrapping problems to the controller.
16338 - New TestingTorNetwork config option to allow adjustment of
16339 previously constant values that, while reasonable, could slow
16340 bootstrapping. Implements proposal 135. Patch from Karsten.
16343 - If you have more than one bridge but don't know their digests,
16344 you would only learn a request for the descriptor of the first one
16345 on your list. (Tor considered launching requests for the others, but
16346 found that it already had a connection on the way for $0000...0000
16347 so it didn't open another.) Bugfix on 0.2.0.x.
16348 - If you have more than one bridge but don't know their digests,
16349 and the connection to one of the bridges failed, you would cancel
16350 all pending bridge connections. (After all, they all have the
16351 same digest.) Bugfix on 0.2.0.x.
16352 - When establishing a hidden service, introduction points that
16353 originate from cannibalized circuits are completely ignored and not
16354 included in rendezvous service descriptors. This might be another
16355 reason for delay in making a hidden service available. Bugfix
16356 from long ago (0.0.9.x?)
16359 - Allow OpenSSL to use dynamic locks if it wants.
16360 - When building a consensus, do not include routers that are down.
16361 This will cut down 30% to 40% on consensus size. Implements
16363 - In directory authorities' approved-routers files, allow
16364 fingerprints with or without space.
16365 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
16366 controller can query our current bootstrap state in case it attaches
16367 partway through and wants to catch up.
16368 - Send an initial "Starting" bootstrap status event, so we have a
16369 state to start out in.
16372 - Asking for a conditional consensus at .../consensus/<fingerprints>
16373 would crash a dirserver if it did not already have a
16374 consensus. Bugfix on 0.2.1.1-alpha.
16375 - Clean up some macro/CPP interactions: some GCC versions don't like
16376 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
16379 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
16380 - Directory authorities shouldn't complain about bootstrapping
16381 problems just because they do a lot of reachability testing and
16382 some of the connection attempts fail.
16383 - Start sending "count" and "recommendation" key/value pairs in
16384 bootstrap problem status events, so the controller can hear about
16385 problems even before Tor decides they're worth reporting for sure.
16386 - If you're using bridges, generate "bootstrap problem" warnings
16387 as soon as you run out of working bridges, rather than waiting
16388 for ten failures -- which will never happen if you have less than
16390 - If we close our OR connection because there's been a circuit
16391 pending on it for too long, we were telling our bootstrap status
16392 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
16395 Changes in version 0.2.1.1-alpha - 2008-06-13
16396 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
16397 were making the Tor process bloat especially on Linux; makes our TLS
16398 handshake blend in better; sends "bootstrap phase" status events to
16399 the controller, so it can keep the user informed of progress (and
16400 problems) fetching directory information and establishing circuits;
16401 and adds a variety of smaller features.
16404 - More work on making our TLS handshake blend in: modify the list
16405 of ciphers advertised by OpenSSL in client mode to even more
16406 closely resemble a common web browser. We cheat a little so that
16407 we can advertise ciphers that the locally installed OpenSSL doesn't
16409 - Start sending "bootstrap phase" status events to the controller,
16410 so it can keep the user informed of progress fetching directory
16411 information and establishing circuits. Also inform the controller
16412 if we think we're stuck at a particular bootstrap phase. Implements
16414 - Resume using OpenSSL's RAND_poll() for better (and more portable)
16415 cross-platform entropy collection again. We used to use it, then
16416 stopped using it because of a bug that could crash systems that
16417 called RAND_poll when they had a lot of fds open. It looks like the
16418 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
16419 at startup, and to call RAND_poll() when we reseed later only if
16420 we have a non-buggy OpenSSL version.
16423 - When we choose to abandon a new entry guard because we think our
16424 older ones might be better, close any circuits pending on that
16425 new entry guard connection. This fix should make us recover much
16426 faster when our network is down and then comes back. Bugfix on
16427 0.1.2.8-beta; found by lodger.
16429 o Memory fixes and improvements:
16430 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
16431 to avoid unused RAM in buffer chunks and memory pools.
16432 - Speed up parsing and cut down on memory fragmentation by using
16433 stack-style allocations for parsing directory objects. Previously,
16434 this accounted for over 40% of allocations from within Tor's code
16435 on a typical directory cache.
16436 - Use a Bloom filter rather than a digest-based set to track which
16437 descriptors we need to keep around when we're cleaning out old
16438 router descriptors. This speeds up the computation significantly,
16439 and may reduce fragmentation.
16440 - Reduce the default smartlist size from 32 to 16; it turns out that
16441 most smartlists hold around 8-12 elements tops.
16442 - Make dumpstats() log the fullness and size of openssl-internal
16444 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
16445 patch to their OpenSSL, turn it on to save memory on servers. This
16446 patch will (with any luck) get included in a mainline distribution
16448 - Never use OpenSSL compression: it wastes RAM and CPU trying to
16449 compress cells, which are basically all encrypted, compressed,
16453 - Stop reloading the router list from disk for no reason when we
16454 run out of reachable directory mirrors. Once upon a time reloading
16455 it would set the 'is_running' flag back to 1 for them. It hasn't
16456 done that for a long time.
16457 - In very rare situations new hidden service descriptors were
16458 published earlier than 30 seconds after the last change to the
16459 service. (We currently think that a hidden service descriptor
16460 that's been stable for 30 seconds is worth publishing.)
16463 - Allow separate log levels to be configured for different logging
16464 domains. For example, this allows one to log all notices, warnings,
16465 or errors, plus all memory management messages of level debug or
16466 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
16467 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
16468 and stop using a warning that had become unfixably verbose under
16470 - New --hush command-line option similar to --quiet. While --quiet
16471 disables all logging to the console on startup, --hush limits the
16472 output to messages of warning and error severity.
16473 - Servers support a new URL scheme for consensus downloads that
16474 allows the client to specify which authorities are trusted.
16475 The server then only sends the consensus if the client will trust
16476 it. Otherwise a 404 error is sent back. Clients use this
16477 new scheme when the server supports it (meaning it's running
16478 0.2.1.1-alpha or later). Implements proposal 134.
16479 - New configure/torrc options (--enable-geoip-stats,
16480 DirRecordUsageByCountry) to record how many IPs we've served
16481 directory info to in each country code, how many status documents
16482 total we've sent to each country code, and what share of the total
16483 directory requests we should expect to see.
16484 - Use the TLS1 hostname extension to more closely resemble browser
16486 - Lots of new unit tests.
16487 - Add a macro to implement the common pattern of iterating through
16488 two parallel lists in lockstep.
16491 Changes in version 0.2.0.28-rc - 2008-06-13
16492 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
16493 performance bug, and fixes a bunch of smaller bugs.
16496 - Fix a bug where, when we were choosing the 'end stream reason' to
16497 put in our relay end cell that we send to the exit relay, Tor
16498 clients on Windows were sometimes sending the wrong 'reason'. The
16499 anonymity problem is that exit relays may be able to guess whether
16500 the client is running Windows, thus helping partition the anonymity
16501 set. Down the road we should stop sending reasons to exit relays,
16502 or otherwise prevent future versions of this bug.
16505 - While setting up a hidden service, some valid introduction circuits
16506 were overlooked and abandoned. This might be the reason for
16507 the long delay in making a hidden service available. Bugfix on
16511 - Update to the "June 9 2008" ip-to-country file.
16512 - Run 'make test' as part of 'make dist', so we stop releasing so
16513 many development snapshots that fail their unit tests.
16516 - When we're checking if we have enough dir info for each relay
16517 to begin establishing circuits, make sure that we actually have
16518 the descriptor listed in the consensus, not just any descriptor.
16520 - Bridge relays no longer print "xx=0" in their extrainfo document
16521 for every single country code in the geoip db. Bugfix on
16523 - Only warn when we fail to load the geoip file if we were planning to
16524 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
16525 - If we change our MaxAdvertisedBandwidth and then reload torrc,
16526 Tor won't realize it should publish a new relay descriptor. Fixes
16527 bug 688, reported by mfr. Bugfix on 0.1.2.x.
16528 - When we haven't had any application requests lately, don't bother
16529 logging that we have expired a bunch of descriptors. Bugfix
16531 - Make relay cells written on a connection count as non-padding when
16532 tracking how long a connection has been in use. Bugfix on
16533 0.2.0.1-alpha. Spotted by lodger.
16534 - Fix unit tests in 0.2.0.27-rc.
16535 - Fix compile on Windows.
16538 Changes in version 0.2.0.27-rc - 2008-06-03
16539 Tor 0.2.0.27-rc adds a few features we left out of the earlier
16540 release candidates. In particular, we now include an IP-to-country
16541 GeoIP database, so controllers can easily look up what country a
16542 given relay is in, and so bridge relays can give us some sanitized
16543 summaries about which countries are making use of bridges. (See proposal
16544 126-geoip-fetching.txt for details.)
16547 - Include an IP-to-country GeoIP file in the tarball, so bridge
16548 relays can report sanitized summaries of the usage they're seeing.
16551 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
16552 Robert Hogan. Fixes the first part of bug 681.
16553 - Make bridge authorities never serve extrainfo docs.
16554 - Add support to detect Libevent versions in the 1.4.x series
16556 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
16557 - Include a new contrib/tor-exit-notice.html file that exit relay
16558 operators can put on their website to help reduce abuse queries.
16561 - When tunneling an encrypted directory connection, and its first
16562 circuit fails, do not leave it unattached and ask the controller
16563 to deal. Fixes the second part of bug 681.
16564 - Make bridge authorities correctly expire old extrainfo documents
16568 Changes in version 0.2.0.26-rc - 2008-05-13
16569 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
16570 in Debian's OpenSSL packages. All users running any 0.2.0.x version
16571 should upgrade, whether they're running Debian or not.
16573 o Major security fixes:
16574 - Use new V3 directory authority keys on the tor26, gabelmoo, and
16575 moria1 V3 directory authorities. The old keys were generated with
16576 a vulnerable version of Debian's OpenSSL package, and must be
16577 considered compromised. Other authorities' keys were not generated
16578 with an affected version of OpenSSL.
16581 - List authority signatures as "unrecognized" based on DirServer
16582 lines, not on cert cache. Bugfix on 0.2.0.x.
16585 - Add a new V3AuthUseLegacyKey option to make it easier for
16586 authorities to change their identity keys if they have to.
16589 Changes in version 0.2.0.25-rc - 2008-04-23
16590 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
16593 - Remember to initialize threading before initializing logging.
16594 Otherwise, many BSD-family implementations will crash hard on
16595 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
16598 - Authorities correctly free policies on bad servers on
16599 exit. Fixes bug 672. Bugfix on 0.2.0.x.
16602 Changes in version 0.2.0.24-rc - 2008-04-22
16603 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
16604 v3 directory authority, makes relays with dynamic IP addresses and no
16605 DirPort notice more quickly when their IP address changes, fixes a few
16606 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
16608 o New directory authorities:
16609 - Take lefkada out of the list of v3 directory authorities, since
16610 it has been down for months.
16611 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
16615 - Detect address changes more quickly on non-directory mirror
16616 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
16618 o Minor features (security):
16619 - Reject requests for reverse-dns lookup of names that are in
16620 a private address space. Patch from lodger.
16621 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
16624 o Minor bugfixes (crashes):
16625 - Avoid a rare assert that can trigger when Tor doesn't have much
16626 directory information yet and it tries to fetch a v2 hidden
16627 service descriptor. Fixes bug 651, reported by nwf.
16628 - Initialize log mutex before initializing dmalloc. Otherwise,
16629 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
16630 - Use recursive pthread mutexes in order to avoid deadlock when
16631 logging debug-level messages to a controller. Bug spotted by nwf,
16632 bugfix on 0.2.0.16-alpha.
16634 o Minor bugfixes (resource management):
16635 - Keep address policies from leaking memory: start their refcount
16636 at 1, not 2. Bugfix on 0.2.0.16-alpha.
16637 - Free authority certificates on exit, so they don't look like memory
16638 leaks. Bugfix on 0.2.0.19-alpha.
16639 - Free static hashtables for policy maps and for TLS connections on
16640 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
16641 - Avoid allocating extra space when computing consensuses on 64-bit
16642 platforms. Bug spotted by aakova.
16644 o Minor bugfixes (misc):
16645 - Do not read the configuration file when we've only been told to
16646 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
16647 based on patch from Sebastian Hahn.
16648 - Exit relays that are used as a client can now reach themselves
16649 using the .exit notation, rather than just launching an infinite
16650 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
16651 - When attempting to open a logfile fails, tell us why.
16652 - Fix a dumb bug that was preventing us from knowing that we should
16653 preemptively build circuits to handle expected directory requests.
16654 Fixes bug 660. Bugfix on 0.1.2.x.
16655 - Warn less verbosely about clock skew from netinfo cells from
16656 untrusted sources. Fixes bug 663.
16657 - Make controller stream events for DNS requests more consistent,
16658 by adding "new stream" events for DNS requests, and removing
16659 spurious "stream closed" events" for cached reverse resolves.
16660 Patch from mwenge. Fixes bug 646.
16661 - Correctly notify one-hop connections when a circuit build has
16662 failed. Possible fix for bug 669. Found by lodger.
16665 Changes in version 0.2.0.23-rc - 2008-03-24
16666 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
16667 makes bootstrapping faster if the first directory mirror you contact
16668 is down. The bundles also include the new Vidalia 0.1.2 release.
16671 - When a tunneled directory request is made to a directory server
16672 that's down, notice after 30 seconds rather than 120 seconds. Also,
16673 fail any begindir streams that are pending on it, so they can
16674 retry elsewhere. This was causing multi-minute delays on bootstrap.
16677 Changes in version 0.2.0.22-rc - 2008-03-18
16678 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
16679 enables encrypted directory connections by default for non-relays, fixes
16680 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
16681 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
16684 - Enable encrypted directory connections by default for non-relays,
16685 so censor tools that block Tor directory connections based on their
16686 plaintext patterns will no longer work. This means Tor works in
16687 certain censored countries by default again.
16690 - Make sure servers always request certificates from clients during
16691 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
16692 - Do not enter a CPU-eating loop when a connection is closed in
16693 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
16694 diagnosed by lodger; bugfix on 0.2.0.20-rc.
16695 - Fix assertion failure that could occur when a blocked circuit
16696 became unblocked, and it had pending client DNS requests. Bugfix
16697 on 0.2.0.1-alpha. Fixes bug 632.
16699 o Minor bugfixes (on 0.1.2.x):
16700 - Generate "STATUS_SERVER" events rather than misspelled
16701 "STATUS_SEVER" events. Caught by mwenge.
16702 - When counting the number of bytes written on a TLS connection,
16703 look at the BIO actually used for writing to the network, not
16704 at the BIO used (sometimes) to buffer data for the network.
16705 Looking at different BIOs could result in write counts on the
16706 order of ULONG_MAX. Fixes bug 614.
16707 - On Windows, correctly detect errors when listing the contents of
16708 a directory. Fix from lodger.
16710 o Minor bugfixes (on 0.2.0.x):
16711 - Downgrade "sslv3 alert handshake failure" message to INFO.
16712 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
16713 left BandwidthRate and BandwidthBurst at the default, we would be
16714 silently limited by those defaults. Now raise them to match the
16715 RelayBandwidth* values.
16716 - Fix the SVK version detection logic to work correctly on a branch.
16717 - Make --enable-openbsd-malloc work correctly on Linux with alpha
16718 CPUs. Fixes bug 625.
16719 - Logging functions now check that the passed severity is sane.
16720 - Use proper log levels in the testsuite call of
16721 get_interface_address6().
16722 - When using a nonstandard malloc, do not use the platform values for
16723 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
16724 - Make the openbsd malloc code use 8k pages on alpha CPUs and
16726 - Detect mismatched page sizes when using --enable-openbsd-malloc.
16727 - Avoid double-marked-for-close warning when certain kinds of invalid
16728 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
16729 for bug 617. Bugfix on 0.2.0.1-alpha.
16730 - Make sure that the "NULL-means-reject *:*" convention is followed by
16731 all the policy manipulation functions, avoiding some possible crash
16732 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
16733 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
16734 actually works, and doesn't warn about every single reverse lookup.
16735 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
16738 - Only log guard node status when guard node status has changed.
16739 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
16740 make "INFO" 75% less verbose.
16743 Changes in version 0.2.0.21-rc - 2008-03-02
16744 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
16745 makes Tor work well with Vidalia again, fixes a rare assert bug,
16746 and fixes a pair of more minor bugs. The bundles also include Vidalia
16747 0.1.0 and Torbutton 1.1.16.
16750 - The control port should declare that it requires password auth
16751 when HashedControlSessionPassword is set too. Patch from Matt Edman;
16752 bugfix on 0.2.0.20-rc. Fixes bug 615.
16753 - Downgrade assert in connection_buckets_decrement() to a log message.
16754 This may help us solve bug 614, and in any case will make its
16755 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
16756 - We were sometimes miscounting the number of bytes read from the
16757 network, causing our rate limiting to not be followed exactly.
16758 Bugfix on 0.2.0.16-alpha. Reported by lodger.
16761 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
16762 OpenSSL versions should have been working fine. Diagnosis and patch
16763 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
16764 Bugfix on 0.2.0.20-rc.
16767 Changes in version 0.2.0.20-rc - 2008-02-24
16768 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
16769 makes more progress towards normalizing Tor's TLS handshake, makes
16770 hidden services work better again, helps relays bootstrap if they don't
16771 know their IP address, adds optional support for linking in openbsd's
16772 allocator or tcmalloc, allows really fast relays to scale past 15000
16773 sockets, and fixes a bunch of minor bugs reported by Veracode.
16776 - Enable the revised TLS handshake based on the one designed by
16777 Steven Murdoch in proposal 124, as revised in proposal 130. It
16778 includes version negotiation for OR connections as described in
16779 proposal 105. The new handshake is meant to be harder for censors
16780 to fingerprint, and it adds the ability to detect certain kinds of
16781 man-in-the-middle traffic analysis attacks. The version negotiation
16782 feature will allow us to improve Tor's link protocol more safely
16784 - Choose which bridge to use proportional to its advertised bandwidth,
16785 rather than uniformly at random. This should speed up Tor for
16786 bridge users. Also do this for people who set StrictEntryNodes.
16787 - When a TrackHostExits-chosen exit fails too many times in a row,
16788 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
16791 - Resolved problems with (re-)fetching hidden service descriptors.
16792 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
16793 and 0.2.0.19-alpha.
16794 - If we only ever used Tor for hidden service lookups or posts, we
16795 would stop building circuits and start refusing connections after
16796 24 hours, since we falsely believed that Tor was dormant. Reported
16797 by nwf; bugfix on 0.1.2.x.
16798 - Servers that don't know their own IP address should go to the
16799 authorities for their first directory fetch, even if their DirPort
16800 is off or if they don't know they're reachable yet. This will help
16801 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
16802 - When counting the number of open sockets, count not only the number
16803 of sockets we have received from the socket() call, but also
16804 the number we've gotten from accept() and socketpair(). This bug
16805 made us fail to count all sockets that we were using for incoming
16806 connections. Bugfix on 0.2.0.x.
16807 - Fix code used to find strings within buffers, when those strings
16808 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
16809 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
16810 - Add a new __HashedControlSessionPassword option for controllers
16811 to use for one-off session password hashes that shouldn't get
16812 saved to disk by SAVECONF --- Vidalia users were accumulating a
16813 pile of HashedControlPassword lines in their torrc files, one for
16814 each time they had restarted Tor and then clicked Save. Make Tor
16815 automatically convert "HashedControlPassword" to this new option but
16816 only when it's given on the command line. Partial fix for bug 586.
16818 o Minor features (performance):
16819 - Tune parameters for cell pool allocation to minimize amount of
16821 - Add OpenBSD malloc code from phk as an optional malloc
16822 replacement on Linux: some glibc libraries do very poorly
16823 with Tor's memory allocation patterns. Pass
16824 --enable-openbsd-malloc to get the replacement malloc code.
16825 - Add a --with-tcmalloc option to the configure script to link
16826 against tcmalloc (if present). Does not yet search for
16827 non-system include paths.
16828 - Stop imposing an arbitrary maximum on the number of file descriptors
16829 used for busy servers. Bug reported by Olaf Selke; patch from
16832 o Minor features (other):
16833 - When SafeLogging is disabled, log addresses along with all TLS
16835 - When building with --enable-gcc-warnings, check for whether Apple's
16836 warning "-Wshorten-64-to-32" is available.
16837 - Add a --passphrase-fd argument to the tor-gencert command for
16840 o Minor bugfixes (memory leaks and code problems):
16841 - We were leaking a file descriptor if Tor started with a zero-length
16842 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
16843 - Detect size overflow in zlib code. Reported by Justin Ferguson and
16845 - We were comparing the raw BridgePassword entry with a base64'ed
16846 version of it, when handling a "/tor/networkstatus-bridges"
16847 directory request. Now compare correctly. Noticed by Veracode.
16848 - Recover from bad tracked-since value in MTBF-history file.
16849 Should fix bug 537.
16850 - Alter the code that tries to recover from unhandled write
16851 errors, to not try to flush onto a socket that's given us
16852 unhandled errors. Bugfix on 0.1.2.x.
16853 - Make Unix controlsockets work correctly on OpenBSD. Patch from
16854 tup. Bugfix on 0.2.0.3-alpha.
16856 o Minor bugfixes (other):
16857 - If we have an extra-info document for our server, always make
16858 it available on the control port, even if we haven't gotten
16859 a copy of it from an authority yet. Patch from mwenge.
16860 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
16861 - Directory mirrors no longer include a guess at the client's IP
16862 address if the connection appears to be coming from the same /24
16863 network; it was producing too many wrong guesses.
16864 - Make the new hidden service code respect the SafeLogging setting.
16865 Bugfix on 0.2.0.x. Patch from Karsten.
16866 - When starting as an authority, do not overwrite all certificates
16867 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
16868 - If we're trying to flush the last bytes on a connection (for
16869 example, when answering a directory request), reset the
16870 time-to-give-up timeout every time we manage to write something
16871 on the socket. Bugfix on 0.1.2.x.
16872 - Change the behavior of "getinfo status/good-server-descriptor"
16873 so it doesn't return failure when any authority disappears.
16874 - Even though the man page said that "TrackHostExits ." should
16875 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
16876 - Report TLS "zero return" case as a "clean close" and "IO error"
16877 as a "close". Stop calling closes "unexpected closes": existing
16878 Tors don't use SSL_close(), so having a connection close without
16879 the TLS shutdown handshake is hardly unexpected.
16880 - Send NAMESERVER_STATUS messages for a single failed nameserver
16883 o Code simplifications and refactoring:
16884 - Remove the tor_strpartition function: its logic was confused,
16885 and it was only used for one thing that could be implemented far
16889 Changes in version 0.2.0.19-alpha - 2008-02-09
16890 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
16891 handshake, makes path selection for relays more secure and IP address
16892 guessing more robust, and generally fixes a lot of bugs in preparation
16893 for calling the 0.2.0 branch stable.
16896 - Do not include recognizeable strings in the commonname part of
16897 Tor's x509 certificates.
16900 - If we're a relay, avoid picking ourselves as an introduction point,
16901 a rendezvous point, or as the final hop for internal circuits. Bug
16902 reported by taranis and lodger. Bugfix on 0.1.2.x.
16903 - Patch from "Andrew S. Lists" to catch when we contact a directory
16904 mirror at IP address X and he says we look like we're coming from
16905 IP address X. Bugfix on 0.1.2.x.
16907 o Minor features (security):
16908 - Be more paranoid about overwriting sensitive memory on free(),
16909 as a defensive programming tactic to ensure forward secrecy.
16911 o Minor features (directory authority):
16912 - Actually validate the options passed to AuthDirReject,
16913 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
16914 - Reject router descriptors with out-of-range bandwidthcapacity or
16915 bandwidthburst values.
16917 o Minor features (controller):
16918 - Reject controller commands over 1MB in length. This keeps rogue
16919 processes from running us out of memory.
16921 o Minor features (misc):
16922 - Give more descriptive well-formedness errors for out-of-range
16923 hidden service descriptor/protocol versions.
16924 - Make memory debugging information describe more about history
16925 of cell allocation, so we can help reduce our memory use.
16927 o Deprecated features (controller):
16928 - The status/version/num-versioning and status/version/num-concurring
16929 GETINFO options are no longer useful in the v3 directory protocol:
16930 treat them as deprecated, and warn when they're used.
16933 - When our consensus networkstatus has been expired for a while, stop
16934 being willing to build circuits using it. Fixes bug 401. Bugfix
16936 - Directory caches now fetch certificates from all authorities
16937 listed in a networkstatus consensus, even when they do not
16938 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
16939 - When connecting to a bridge without specifying its key, insert
16940 the connection into the identity-to-connection map as soon as
16941 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
16942 - Detect versions of OS X where malloc_good_size() is present in the
16943 library but never actually declared. Resolves bug 587. Bugfix
16945 - Stop incorrectly truncating zlib responses to directory authority
16946 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
16947 - Stop recommending that every server operator send mail to tor-ops.
16948 Resolves bug 597. Bugfix on 0.1.2.x.
16949 - Don't trigger an assert if we start a directory authority with a
16950 private IP address (like 127.0.0.1).
16951 - Avoid possible failures when generating a directory with routers
16952 with over-long versions strings, or too many flags set. Bugfix
16954 - If an attempt to launch a DNS resolve request over the control
16955 port fails because we have overrun the limit on the number of
16956 connections, tell the controller that the request has failed.
16957 - Avoid using too little bandwidth when our clock skips a few
16958 seconds. Bugfix on 0.1.2.x.
16959 - Fix shell error when warning about missing packages in configure
16960 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
16961 - Do not become confused when receiving a spurious VERSIONS-like
16962 cell from a confused v1 client. Bugfix on 0.2.0.x.
16963 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
16964 introduction points for a hidden service have failed. Patch from
16965 Karsten Loesing. Bugfix on 0.2.0.x.
16967 o Code simplifications and refactoring:
16968 - Remove some needless generality from cpuworker code, for improved
16970 - Stop overloading the circuit_t.onionskin field for both "onionskin
16971 from a CREATE cell that we are waiting for a cpuworker to be
16972 assigned" and "onionskin from an EXTEND cell that we are going to
16973 send to an OR as soon as we are connected". Might help with bug 600.
16974 - Add an in-place version of aes_crypt() so that we can avoid doing a
16975 needless memcpy() call on each cell payload.
16978 Changes in version 0.2.0.18-alpha - 2008-01-25
16979 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
16980 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
16981 that can warn or reject connections to ports generally associated with
16982 vulnerable-plaintext protocols.
16984 o New directory authorities:
16985 - Set up dannenberg (run by CCC) as the sixth v3 directory
16989 - Fix a major memory leak when attempting to use the v2 TLS
16990 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
16991 - We accidentally enabled the under-development v2 TLS handshake
16992 code, which was causing log entries like "TLS error while
16993 renegotiating handshake". Disable it again. Resolves bug 590.
16994 - We were computing the wrong Content-Length: header for directory
16995 responses that need to be compressed on the fly, causing clients
16996 asking for those items to always fail. Bugfix on 0.2.0.x; partially
17000 - Avoid going directly to the directory authorities even if you're a
17001 relay, if you haven't found yourself reachable yet or if you've
17002 decided not to advertise your dirport yet. Addresses bug 556.
17003 - If we've gone 12 hours since our last bandwidth check, and we
17004 estimate we have less than 50KB bandwidth capacity but we could
17005 handle more, do another bandwidth test.
17006 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
17007 Tor can warn and/or refuse connections to ports commonly used with
17008 vulnerable-plaintext protocols. Currently we warn on ports 23,
17009 109, 110, and 143, but we don't reject any.
17012 - When we setconf ClientOnly to 1, close any current OR and Dir
17013 listeners. Reported by mwenge.
17014 - When we get a consensus that's been signed by more people than
17015 we expect, don't log about it; it's not a big deal. Reported
17019 - Don't answer "/tor/networkstatus-bridges" directory requests if
17020 the request isn't encrypted.
17021 - Make "ClientOnly 1" config option disable directory ports too.
17022 - Patches from Karsten Loesing to make v2 hidden services more
17023 robust: work even when there aren't enough HSDir relays available;
17024 retry when a v2 rend desc fetch fails; but don't retry if we
17025 already have a usable v0 rend desc.
17028 Changes in version 0.2.0.17-alpha - 2008-01-17
17029 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
17032 - Make the tor-gencert man page get included correctly in the tarball.
17035 Changes in version 0.2.0.16-alpha - 2008-01-17
17036 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
17037 Loesing, and generally cleans up a lot of features and minor bugs.
17039 o New directory authorities:
17040 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
17043 o Major performance improvements:
17044 - Switch our old ring buffer implementation for one more like that
17045 used by free Unix kernels. The wasted space in a buffer with 1mb
17046 of data will now be more like 8k than 1mb. The new implementation
17047 also avoids realloc();realloc(); patterns that can contribute to
17048 memory fragmentation.
17051 - Configuration files now accept C-style strings as values. This
17052 helps encode characters not allowed in the current configuration
17053 file format, such as newline or #. Addresses bug 557.
17054 - Although we fixed bug 539 (where servers would send HTTP status 503
17055 responses _and_ send a body too), there are still servers out
17056 there that haven't upgraded. Therefore, make clients parse such
17057 bodies when they receive them.
17058 - When we're not serving v2 directory information, there is no reason
17059 to actually keep any around. Remove the obsolete files and directory
17060 on startup if they are very old and we aren't going to serve them.
17062 o Minor performance improvements:
17063 - Reference-count and share copies of address policy entries; only 5%
17064 of them were actually distinct.
17065 - Never walk through the list of logs if we know that no log is
17066 interested in a given message.
17069 - When an authority has not signed a consensus, do not try to
17070 download a nonexistent "certificate with key 00000000". Bugfix
17071 on 0.2.0.x. Fixes bug 569.
17072 - Fix a rare assert error when we're closing one of our threads:
17073 use a mutex to protect the list of logs, so we never write to the
17074 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
17075 bug 575, which is kind of the revenge of bug 222.
17076 - Patch from Karsten Loesing to complain less at both the client
17077 and the relay when a relay used to have the HSDir flag but doesn't
17078 anymore, and we try to upload a hidden service descriptor.
17079 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
17081 - Do not try to download missing certificates until we have tried
17082 to check our fallback consensus. Fixes bug 583.
17083 - Make bridges round reported GeoIP stats info up to the nearest
17084 estimate, not down. Now we can distinguish between "0 people from
17085 this country" and "1 person from this country".
17086 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
17087 - Avoid possible segfault if key generation fails in
17088 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
17089 - Avoid segfault in the case where a badly behaved v2 versioning
17090 directory sends a signed networkstatus with missing client-versions.
17092 - Avoid segfaults on certain complex invocations of
17093 router_get_by_hexdigest(). Bugfix on 0.1.2.
17094 - Correct bad index on array access in parse_http_time(). Bugfix
17096 - Fix possible bug in vote generation when server versions are present
17097 but client versions are not.
17098 - Fix rare bug on REDIRECTSTREAM control command when called with no
17099 port set: it could erroneously report an error when none had
17101 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
17102 compressing large objects and find ourselves with more than 4k
17103 left over. Bugfix on 0.2.0.
17104 - Fix a small memory leak when setting up a hidden service.
17105 - Fix a few memory leaks that could in theory happen under bizarre
17107 - Fix an assert if we post a general-purpose descriptor via the
17108 control port but that descriptor isn't mentioned in our current
17109 network consensus. Bug reported by Jon McLachlan; bugfix on
17112 o Minor features (controller):
17113 - Get NS events working again. Patch from tup.
17114 - The GETCONF command now escapes and quotes configuration values
17115 that don't otherwise fit into the torrc file.
17116 - The SETCONF command now handles quoted values correctly.
17118 o Minor features (directory authorities):
17119 - New configuration options to override default maximum number of
17120 servers allowed on a single IP address. This is important for
17121 running a test network on a single host.
17122 - Actually implement the -s option to tor-gencert.
17123 - Add a manual page for tor-gencert.
17125 o Minor features (bridges):
17126 - Bridge authorities no longer serve bridge descriptors over
17127 unencrypted connections.
17129 o Minor features (other):
17130 - Add hidden services and DNSPorts to the list of things that make
17131 Tor accept that it has running ports. Change starting Tor with no
17132 ports from a fatal error to a warning; we might change it back if
17133 this turns out to confuse anybody. Fixes bug 579.
17136 Changes in version 0.1.2.19 - 2008-01-17
17137 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
17138 exit policy a little bit more conservative so it's safer to run an
17139 exit relay on a home system, and fixes a variety of smaller issues.
17142 - Exit policies now reject connections that are addressed to a
17143 relay's public (external) IP address too, unless
17144 ExitPolicyRejectPrivate is turned off. We do this because too
17145 many relays are running nearby to services that trust them based
17146 on network address.
17149 - When the clock jumps forward a lot, do not allow the bandwidth
17150 buckets to become negative. Fixes bug 544.
17151 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
17152 on every successful resolve. Reported by Mike Perry.
17153 - Purge old entries from the "rephist" database and the hidden
17154 service descriptor database even when DirPort is zero.
17155 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
17156 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
17157 crashing or mis-answering these requests.
17158 - When we decide to send a 503 response to a request for servers, do
17159 not then also send the server descriptors: this defeats the whole
17160 purpose. Fixes bug 539.
17163 - Changing the ExitPolicyRejectPrivate setting should cause us to
17164 rebuild our server descriptor.
17165 - Fix handling of hex nicknames when answering controller requests for
17166 networkstatus by name, or when deciding whether to warn about
17167 unknown routers in a config option. (Patch from mwenge.)
17168 - Fix a couple of hard-to-trigger autoconf problems that could result
17169 in really weird results on platforms whose sys/types.h files define
17170 nonstandard integer types.
17171 - Don't try to create the datadir when running --verify-config or
17172 --hash-password. Resolves bug 540.
17173 - If we were having problems getting a particular descriptor from the
17174 directory caches, and then we learned about a new descriptor for
17175 that router, we weren't resetting our failure count. Reported
17177 - Although we fixed bug 539 (where servers would send HTTP status 503
17178 responses _and_ send a body too), there are still servers out there
17179 that haven't upgraded. Therefore, make clients parse such bodies
17180 when they receive them.
17181 - Run correctly on systems where rlim_t is larger than unsigned long.
17182 This includes some 64-bit systems.
17183 - Run correctly on platforms (like some versions of OS X 10.5) where
17184 the real limit for number of open files is OPEN_FILES, not rlim_max
17185 from getrlimit(RLIMIT_NOFILES).
17186 - Avoid a spurious free on base64 failure.
17187 - Avoid segfaults on certain complex invocations of
17188 router_get_by_hexdigest().
17189 - Fix rare bug on REDIRECTSTREAM control command when called with no
17190 port set: it could erroneously report an error when none had
17194 Changes in version 0.2.0.15-alpha - 2007-12-25
17195 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
17196 features added in 0.2.0.13-alpha.
17199 - Fix several remotely triggerable asserts based on DirPort requests
17200 for a v2 or v3 networkstatus object before we were prepared. This
17201 was particularly bad for 0.2.0.13 and later bridge relays, who
17202 would never have a v2 networkstatus and would thus always crash
17203 when used. Bugfixes on 0.2.0.x.
17204 - Estimate the v3 networkstatus size more accurately, rather than
17205 estimating it at zero bytes and giving it artificially high priority
17206 compared to other directory requests. Bugfix on 0.2.0.x.
17209 - Fix configure.in logic for cross-compilation.
17210 - When we load a bridge descriptor from the cache, and it was
17211 previously unreachable, mark it as retriable so we won't just
17212 ignore it. Also, try fetching a new copy immediately. Bugfixes
17214 - The bridge GeoIP stats were counting other relays, for example
17215 self-reachability and authority-reachability tests.
17218 - Support compilation to target iPhone; patch from cjacker huang.
17219 To build for iPhone, pass the --enable-iphone option to configure.
17222 Changes in version 0.2.0.14-alpha - 2007-12-23
17224 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
17225 without a datadirectory from a previous Tor install. Reported
17227 - Fix a crash when we fetch a descriptor that turns out to be
17228 unexpected (it used to be in our networkstatus when we started
17229 fetching it, but it isn't in our current networkstatus), and we
17230 aren't using bridges. Bugfix on 0.2.0.x.
17231 - Fix a crash when accessing hidden services: it would work the first
17232 time you use a given introduction point for your service, but
17233 on subsequent requests we'd be using garbage memory. Fixed by
17234 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
17235 - Fix a crash when we load a bridge descriptor from disk but we don't
17236 currently have a Bridge line for it in our torrc. Bugfix on
17240 - If bridge authorities set BridgePassword, they will serve a
17241 snapshot of known bridge routerstatuses from their DirPort to
17242 anybody who knows that password. Unset by default.
17245 - Make the unit tests build again.
17246 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
17247 - Make PublishServerDescriptor default to 1, so the default doesn't
17248 have to change as we invent new directory protocol versions.
17249 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
17250 be included unless sys/time.h is already included. Fixes
17251 bug 553. Bugfix on 0.2.0.x.
17252 - If we receive a general-purpose descriptor and then receive an
17253 identical bridge-purpose descriptor soon after, don't discard
17254 the next one as a duplicate.
17257 - If BridgeRelay is set to 1, then the default for
17258 PublishServerDescriptor is now "bridge" rather than "v2,v3".
17259 - If the user sets RelayBandwidthRate but doesn't set
17260 RelayBandwidthBurst, then make them equal rather than erroring out.
17263 Changes in version 0.2.0.13-alpha - 2007-12-21
17264 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
17265 Goodell, fixes many more bugs, and adds a lot of infrastructure for
17268 o New directory authorities:
17269 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
17273 - Only update guard status (usable / not usable) once we have
17274 enough directory information. This was causing us to always pick
17275 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
17276 causing us to discard all our guards on startup if we hadn't been
17277 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
17278 - Purge old entries from the "rephist" database and the hidden
17279 service descriptor databases even when DirPort is zero. Bugfix
17281 - We were ignoring our RelayBandwidthRate for the first 30 seconds
17282 after opening a circuit -- even a relayed circuit. Bugfix on
17284 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
17285 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
17286 crashing or mis-answering these types of requests.
17287 - Relays were publishing their server descriptor to v1 and v2
17288 directory authorities, but they didn't try publishing to v3-only
17289 authorities. Fix this; and also stop publishing to v1 authorities.
17291 - When we were reading router descriptors from cache, we were ignoring
17292 the annotations -- so for example we were reading in bridge-purpose
17293 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
17294 - When we decided to send a 503 response to a request for servers, we
17295 were then also sending the server descriptors: this defeats the
17296 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
17299 - Bridge relays now behave like clients with respect to time
17300 intervals for downloading new consensus documents -- otherwise they
17301 stand out. Bridge users now wait until the end of the interval,
17302 so their bridge relay will be sure to have a new consensus document.
17303 - Three new config options (AlternateDirAuthority,
17304 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
17305 user selectively replace the default directory authorities by type,
17306 rather than the all-or-nothing replacement that DirServer offers.
17307 - Tor can now be configured to read a GeoIP file from disk in one
17308 of two formats. This can be used by controllers to map IP addresses
17309 to countries. Eventually, it may support exit-by-country.
17310 - When possible, bridge relays remember which countries users
17311 are coming from, and report aggregate information in their
17312 extra-info documents, so that the bridge authorities can learn
17313 where Tor is blocked.
17314 - Bridge directory authorities now do reachability testing on the
17315 bridges they know. They provide router status summaries to the
17316 controller via "getinfo ns/purpose/bridge", and also dump summaries
17317 to a file periodically.
17318 - Stop fetching directory info so aggressively if your DirPort is
17319 on but your ORPort is off; stop fetching v2 dir info entirely.
17320 You can override these choices with the new FetchDirInfoEarly
17324 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
17325 consensus documents when there are too many relays at a single
17326 IP address. Now clear it in v2 network status documents too, and
17327 also clear it in routerinfo_t when the relay is no longer listed
17328 in the relevant networkstatus document.
17329 - Don't crash if we get an unexpected value for the
17330 PublishServerDescriptor config option. Reported by Matt Edman;
17331 bugfix on 0.2.0.9-alpha.
17332 - Our new v2 hidden service descriptor format allows descriptors
17333 that have no introduction points. But Tor crashed when we tried
17334 to build a descriptor with no intro points (and it would have
17335 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
17336 by Karsten Loesing.
17337 - Fix building with dmalloc 5.5.2 with glibc.
17338 - Reject uploaded descriptors and extrainfo documents if they're
17339 huge. Otherwise we'll cache them all over the network and it'll
17340 clog everything up. Reported by Aljosha Judmayer.
17341 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
17342 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
17343 - When the DANGEROUS_VERSION controller status event told us we're
17344 running an obsolete version, it used the string "OLD" to describe
17345 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
17346 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
17347 - If we can't expand our list of entry guards (e.g. because we're
17348 using bridges or we have StrictEntryNodes set), don't mark relays
17349 down when they fail a directory request. Otherwise we're too quick
17350 to mark all our entry points down. Bugfix on 0.1.2.x.
17351 - Fix handling of hex nicknames when answering controller requests for
17352 networkstatus by name, or when deciding whether to warn about unknown
17353 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
17354 - Fix a couple of hard-to-trigger autoconf problems that could result
17355 in really weird results on platforms whose sys/types.h files define
17356 nonstandard integer types. Bugfix on 0.1.2.x.
17357 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
17358 - Don't crash on name lookup when we have no current consensus. Fixes
17359 bug 538; bugfix on 0.2.0.x.
17360 - Only Tors that want to mirror the v2 directory info should
17361 create the "cached-status" directory in their datadir. (All Tors
17362 used to create it.) Bugfix on 0.2.0.9-alpha.
17363 - Directory authorities should only automatically download Extra Info
17364 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
17367 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
17368 consumers. (We already do this on HUP.)
17369 - Authorities and caches fetch the v2 networkstatus documents
17370 less often, now that v3 is encouraged.
17371 - Add a new config option BridgeRelay that specifies you want to
17372 be a bridge relay. Right now the only difference is that it makes
17373 you answer begin_dir requests, and it makes you cache dir info,
17374 even if your DirPort isn't on.
17375 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
17376 ask about source, timestamp of arrival, purpose, etc. We need
17377 something like this to help Vidalia not do GeoIP lookups on bridge
17379 - Allow multiple HashedControlPassword config lines, to support
17380 multiple controller passwords.
17381 - Authorities now decide whether they're authoritative for a given
17382 router based on the router's purpose.
17383 - New config options AuthDirBadDir and AuthDirListBadDirs for
17384 authorities to mark certain relays as "bad directories" in the
17385 networkstatus documents. Also supports the "!baddir" directive in
17386 the approved-routers file.
17389 Changes in version 0.2.0.12-alpha - 2007-11-16
17390 This twelfth development snapshot fixes some more build problems as
17391 well as a few minor bugs.
17394 - Make it build on OpenBSD again. Patch from tup.
17395 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
17396 package-building for Red Hat, OS X, etc.
17398 o Minor bugfixes (on 0.1.2.x):
17399 - Changing the ExitPolicyRejectPrivate setting should cause us to
17400 rebuild our server descriptor.
17402 o Minor bugfixes (on 0.2.0.x):
17403 - When we're lacking a consensus, don't try to perform rendezvous
17404 operations. Reported by Karsten Loesing.
17405 - Fix a small memory leak whenever we decide against using a
17406 newly picked entry guard. Reported by Mike Perry.
17407 - When authorities detected more than two relays running on the same
17408 IP address, they were clearing all the status flags but forgetting
17409 to clear the "hsdir" flag. So clients were being told that a
17410 given relay was the right choice for a v2 hsdir lookup, yet they
17411 never had its descriptor because it was marked as 'not running'
17413 - If we're trying to fetch a bridge descriptor and there's no way
17414 the bridge authority could help us (for example, we don't know
17415 a digest, or there is no bridge authority), don't be so eager to
17416 fall back to asking the bridge authority.
17417 - If we're using bridges or have strictentrynodes set, and our
17418 chosen exit is in the same family as all our bridges/entry guards,
17419 then be flexible about families.
17422 - When we negotiate a v2 link-layer connection (not yet implemented),
17423 accept RELAY_EARLY cells and turn them into RELAY cells if we've
17424 negotiated a v1 connection for their next step. Initial code for
17428 Changes in version 0.2.0.11-alpha - 2007-11-12
17429 This eleventh development snapshot fixes some build problems with
17430 the previous snapshot. It also includes a more secure-by-default exit
17431 policy for relays, fixes an enormous memory leak for exit relays, and
17432 fixes another bug where servers were falling out of the directory list.
17435 - Exit policies now reject connections that are addressed to a
17436 relay's public (external) IP address too, unless
17437 ExitPolicyRejectPrivate is turned off. We do this because too
17438 many relays are running nearby to services that trust them based
17439 on network address. Bugfix on 0.1.2.x.
17442 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
17443 on every successful resolve. Reported by Mike Perry; bugfix
17445 - On authorities, never downgrade to old router descriptors simply
17446 because they're listed in the consensus. This created a catch-22
17447 where we wouldn't list a new descriptor because there was an
17448 old one in the consensus, and we couldn't get the new one in the
17449 consensus because we wouldn't list it. Possible fix for bug 548.
17450 Also, this might cause bug 543 to appear on authorities; if so,
17451 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
17453 o Packaging fixes on 0.2.0.10-alpha:
17454 - We were including instructions about what to do with the
17455 src/config/fallback-consensus file, but we weren't actually
17456 including it in the tarball. Disable all of that for now.
17459 - Allow people to say PreferTunnelledDirConns rather than
17460 PreferTunneledDirConns, for those alternate-spellers out there.
17463 - Don't reevaluate all the information from our consensus document
17464 just because we've downloaded a v2 networkstatus that we intend
17465 to cache. Fixes bug 545; bugfix on 0.2.0.x.
17468 Changes in version 0.2.0.10-alpha - 2007-11-10
17469 This tenth development snapshot adds a third v3 directory authority
17470 run by Mike Perry, adds most of Karsten Loesing's new hidden service
17471 descriptor format, fixes a bad crash bug and new bridge bugs introduced
17472 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
17473 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
17474 addresses many more minor issues.
17476 o New directory authorities:
17477 - Set up ides (run by Mike Perry) as the third v3 directory authority.
17480 - Allow tunnelled directory connections to ask for an encrypted
17481 "begin_dir" connection or an anonymized "uses a full Tor circuit"
17482 connection independently. Now we can make anonymized begin_dir
17483 connections for (e.g.) more secure hidden service posting and
17485 - More progress on proposal 114: code from Karsten Loesing to
17486 implement new hidden service descriptor format.
17487 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
17488 accommodate the growing number of servers that use the default
17489 and are reaching it.
17490 - Directory authorities use a new formula for selecting which nodes
17491 to advertise as Guards: they must be in the top 7/8 in terms of
17492 how long we have known about them, and above the median of those
17493 nodes in terms of weighted fractional uptime.
17494 - Make "not enough dir info yet" warnings describe *why* Tor feels
17495 it doesn't have enough directory info yet.
17498 - Stop servers from crashing if they set a Family option (or
17499 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
17501 - Make bridge users work again -- the move to v3 directories in
17502 0.2.0.9-alpha had introduced a number of bugs that made bridges
17503 no longer work for clients.
17504 - When the clock jumps forward a lot, do not allow the bandwidth
17505 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
17507 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
17508 - When the consensus lists a router descriptor that we previously were
17509 mirroring, but that we considered non-canonical, reload the
17510 descriptor as canonical. This fixes bug 543 where Tor servers
17511 would start complaining after a few days that they don't have
17512 enough directory information to build a circuit.
17513 - Consider replacing the current consensus when certificates arrive
17514 that make the pending consensus valid. Previously, we were only
17515 considering replacement when the new certs _didn't_ help.
17516 - Fix an assert error on startup if we didn't already have the
17517 consensus and certs cached in our datadirectory: we were caching
17518 the consensus in consensus_waiting_for_certs but then free'ing it
17520 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
17521 Request) if we need more v3 certs but we've already got pending
17522 requests for all of them.
17523 - Correctly back off from failing certificate downloads. Fixes
17525 - Authorities don't vote on the Running flag if they have been running
17526 for less than 30 minutes themselves. Fixes bug 547, where a newly
17527 started authority would vote that everyone was down.
17529 o New requirements:
17530 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
17531 it, it had no AES, and it hasn't seen any security patches since
17535 - Clients now hold circuitless TLS connections open for 1.5 times
17536 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
17537 rebuild a new circuit over them within that timeframe. Previously,
17538 they held them open only for KeepalivePeriod (5 minutes).
17539 - Use "If-Modified-Since" to avoid retrieving consensus
17540 networkstatuses that we already have.
17541 - When we have no consensus, check FallbackNetworkstatusFile (defaults
17542 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
17543 we start knowing some directory caches.
17544 - When we receive a consensus from the future, warn about skew.
17545 - Improve skew reporting: try to give the user a better log message
17546 about how skewed they are, and how much this matters.
17547 - When we have a certificate for an authority, believe that
17548 certificate's claims about the authority's IP address.
17549 - New --quiet command-line option to suppress the default console log.
17550 Good in combination with --hash-password.
17551 - Authorities send back an X-Descriptor-Not-New header in response to
17552 an accepted-but-discarded descriptor upload. Partially implements
17554 - Make the log message for "tls error. breaking." more useful.
17555 - Better log messages about certificate downloads, to attempt to
17556 track down the second incarnation of bug 546.
17558 o Minor features (bridges):
17559 - If bridge users set UpdateBridgesFromAuthority, but the digest
17560 they ask for is a 404 from the bridge authority, they now fall
17561 back to trying the bridge directly.
17562 - Bridges now use begin_dir to publish their server descriptor to
17563 the bridge authority, even when they haven't set TunnelDirConns.
17565 o Minor features (controller):
17566 - When reporting clock skew, and we know that the clock is _at least
17567 as skewed_ as some value, but we don't know the actual value,
17568 report the value as a "minimum skew."
17571 - Update linux-tor-prio.sh script to allow QoS based on the uid of
17572 the Tor process. Patch from Marco Bonetti with tweaks from Mike
17576 - Refuse to start if both ORPort and UseBridges are set. Bugfix
17577 on 0.2.0.x, suggested by Matt Edman.
17578 - Don't stop fetching descriptors when FetchUselessDescriptors is
17579 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
17580 reported by tup and ioerror.
17581 - Better log message on vote from unknown authority.
17582 - Don't log "Launching 0 request for 0 router" message.
17584 o Minor bugfixes (memory leaks):
17585 - Stop leaking memory every time we parse a v3 certificate. Bugfix
17587 - Stop leaking memory every time we load a v3 certificate. Bugfix
17588 on 0.2.0.1-alpha. Fixes bug 536.
17589 - Stop leaking a cached networkstatus on exit. Bugfix on
17591 - Stop leaking voter information every time we free a consensus.
17592 Bugfix on 0.2.0.3-alpha.
17593 - Stop leaking signed data every time we check a voter signature.
17594 Bugfix on 0.2.0.3-alpha.
17595 - Stop leaking a signature every time we fail to parse a consensus or
17596 a vote. Bugfix on 0.2.0.3-alpha.
17597 - Stop leaking v2_download_status_map on shutdown. Bugfix on
17599 - Stop leaking conn->nickname every time we make a connection to a
17600 Tor relay without knowing its expected identity digest (e.g. when
17601 using bridges). Bugfix on 0.2.0.3-alpha.
17603 - Minor bugfixes (portability):
17604 - Run correctly on platforms where rlim_t is larger than unsigned
17605 long, and/or where the real limit for number of open files is
17606 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
17607 particular, these may be needed for OS X 10.5.
17610 Changes in version 0.1.2.18 - 2007-10-28
17611 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
17612 hidden service introduction that were causing huge delays, and a big
17613 bug that was causing some servers to disappear from the network status
17614 lists for a few hours each day.
17616 o Major bugfixes (crashes):
17617 - If a connection is shut down abruptly because of something that
17618 happened inside connection_flushed_some(), do not call
17619 connection_finished_flushing(). Should fix bug 451:
17620 "connection_stop_writing: Assertion conn->write_event failed"
17621 Bugfix on 0.1.2.7-alpha.
17622 - Fix possible segfaults in functions called from
17623 rend_process_relay_cell().
17625 o Major bugfixes (hidden services):
17626 - Hidden services were choosing introduction points uniquely by
17627 hexdigest, but when constructing the hidden service descriptor
17628 they merely wrote the (potentially ambiguous) nickname.
17629 - Clients now use the v2 intro format for hidden service
17630 connections: they specify their chosen rendezvous point by identity
17631 digest rather than by (potentially ambiguous) nickname. These
17632 changes could speed up hidden service connections dramatically.
17634 o Major bugfixes (other):
17635 - Stop publishing a new server descriptor just because we get a
17636 HUP signal. This led (in a roundabout way) to some servers getting
17637 dropped from the networkstatus lists for a few hours each day.
17638 - When looking for a circuit to cannibalize, consider family as well
17639 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
17640 circuit cannibalization).
17641 - When a router wasn't listed in a new networkstatus, we were leaving
17642 the flags for that router alone -- meaning it remained Named,
17643 Running, etc -- even though absence from the networkstatus means
17644 that it shouldn't be considered to exist at all anymore. Now we
17645 clear all the flags for routers that fall out of the networkstatus
17646 consensus. Fixes bug 529.
17649 - Don't try to access (or alter) the state file when running
17650 --list-fingerprint or --verify-config or --hash-password. Resolves
17652 - When generating information telling us how to extend to a given
17653 router, do not try to include the nickname if it is
17654 absent. Resolves bug 467.
17655 - Fix a user-triggerable segfault in expand_filename(). (There isn't
17656 a way to trigger this remotely.)
17657 - When sending a status event to the controller telling it that an
17658 OR address is reachable, set the port correctly. (Previously we
17659 were reporting the dir port.)
17660 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
17661 command. Bugfix on 0.1.2.17.
17662 - When loading bandwidth history, do not believe any information in
17663 the future. Fixes bug 434.
17664 - When loading entry guard information, do not believe any information
17666 - When we have our clock set far in the future and generate an
17667 onion key, then re-set our clock to be correct, we should not stop
17668 the onion key from getting rotated.
17669 - On some platforms, accept() can return a broken address. Detect
17670 this more quietly, and deal accordingly. Fixes bug 483.
17671 - It's not actually an error to find a non-pending entry in the DNS
17672 cache when canceling a pending resolve. Don't log unless stuff
17673 is fishy. Resolves bug 463.
17674 - Don't reset trusted dir server list when we set a configuration
17675 option. Patch from Robert Hogan.
17676 - Don't try to create the datadir when running --verify-config or
17677 --hash-password. Resolves bug 540.
17680 Changes in version 0.2.0.9-alpha - 2007-10-24
17681 This ninth development snapshot switches clients to the new v3 directory
17682 system; allows servers to be listed in the network status even when they
17683 have the same nickname as a registered server; and fixes many other
17684 bugs including a big one that was causing some servers to disappear
17685 from the network status lists for a few hours each day.
17687 o Major features (directory system):
17688 - Clients now download v3 consensus networkstatus documents instead
17689 of v2 networkstatus documents. Clients and caches now base their
17690 opinions about routers on these consensus documents. Clients only
17691 download router descriptors listed in the consensus.
17692 - Authorities now list servers who have the same nickname as
17693 a different named server, but list them with a new flag,
17694 "Unnamed". Now we can list servers that happen to pick the same
17695 nickname as a server that registered two years ago and then
17696 disappeared. Partially implements proposal 122.
17697 - If the consensus lists a router as "Unnamed", the name is assigned
17698 to a different router: do not identify the router by that name.
17699 Partially implements proposal 122.
17700 - Authorities can now come to a consensus on which method to use to
17701 compute the consensus. This gives us forward compatibility.
17704 - Stop publishing a new server descriptor just because we HUP or
17705 when we find our DirPort to be reachable but won't actually publish
17706 it. New descriptors without any real changes are dropped by the
17707 authorities, and can screw up our "publish every 18 hours" schedule.
17709 - When a router wasn't listed in a new networkstatus, we were leaving
17710 the flags for that router alone -- meaning it remained Named,
17711 Running, etc -- even though absence from the networkstatus means
17712 that it shouldn't be considered to exist at all anymore. Now we
17713 clear all the flags for routers that fall out of the networkstatus
17714 consensus. Fixes bug 529; bugfix on 0.1.2.x.
17715 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
17716 extrainfo documents and then discard them immediately for not
17717 matching the latest router. Bugfix on 0.2.0.1-alpha.
17719 o Minor features (v3 directory protocol):
17720 - Allow tor-gencert to generate a new certificate without replacing
17722 - Allow certificates to include an address.
17723 - When we change our directory-cache settings, reschedule all voting
17724 and download operations.
17725 - Reattempt certificate downloads immediately on failure, as long as
17726 we haven't failed a threshold number of times yet.
17727 - Delay retrying consensus downloads while we're downloading
17728 certificates to verify the one we just got. Also, count getting a
17729 consensus that we already have (or one that isn't valid) as a failure,
17730 and count failing to get the certificates after 20 minutes as a
17732 - Build circuits and download descriptors even if our consensus is a
17733 little expired. (This feature will go away once authorities are
17736 o Minor features (router descriptor cache):
17737 - If we find a cached-routers file that's been sitting around for more
17738 than 28 days unmodified, then most likely it's a leftover from
17739 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
17741 - When we (as a cache) download a descriptor because it was listed
17742 in a consensus, remember when the consensus was supposed to expire,
17743 and don't expire the descriptor until then.
17745 o Minor features (performance):
17746 - Call routerlist_remove_old_routers() much less often. This should
17747 speed startup, especially on directory caches.
17748 - Don't try to launch new descriptor downloads quite so often when we
17749 already have enough directory information to build circuits.
17750 - Base64 decoding was actually showing up on our profile when parsing
17751 the initial descriptor file; switch to an in-process all-at-once
17752 implementation that's about 3.5x times faster than calling out to
17755 o Minor features (compilation):
17756 - Detect non-ASCII platforms (if any still exist) and refuse to
17757 build there: some of our code assumes that 'A' is 65 and so on.
17759 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
17760 - Make the "next period" votes into "current period" votes immediately
17761 after publishing the consensus; avoid a heisenbug that made them
17762 stick around indefinitely.
17763 - When we discard a vote as a duplicate, do not report this as
17765 - Treat missing v3 keys or certificates as an error when running as a
17766 v3 directory authority.
17767 - When we're configured to be a v3 authority, but we're only listed
17768 as a non-v3 authority in our DirServer line for ourself, correct
17770 - If an authority doesn't have a qualified hostname, just put
17771 its address in the vote. This fixes the problem where we referred to
17772 "moria on moria:9031."
17773 - Distinguish between detached signatures for the wrong period, and
17774 detached signatures for a divergent vote.
17775 - Fix a small memory leak when computing a consensus.
17776 - When there's no concensus, we were forming a vote every 30
17777 minutes, but writing the "valid-after" line in our vote based
17778 on our configured V3AuthVotingInterval: so unless the intervals
17779 matched up, we immediately rejected our own vote because it didn't
17780 start at the voting interval that caused us to construct a vote.
17782 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
17783 - Delete unverified-consensus when the real consensus is set.
17784 - Consider retrying a consensus networkstatus fetch immediately
17785 after one fails: don't wait 60 seconds to notice.
17786 - When fetching a consensus as a cache, wait until a newer consensus
17787 should exist before trying to replace the current one.
17788 - Use a more forgiving schedule for retrying failed consensus
17789 downloads than for other types.
17791 o Minor bugfixes (other directory issues):
17792 - Correct the implementation of "download votes by digest." Bugfix on
17794 - Authorities no longer send back "400 you're unreachable please fix
17795 it" errors to Tor servers that aren't online all the time. We're
17796 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
17798 o Minor bugfixes (controller):
17799 - Don't reset trusted dir server list when we set a configuration
17800 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
17801 - Respond to INT and TERM SIGNAL commands before we execute the
17802 signal, in case the signal shuts us down. We had a patch in
17803 0.1.2.1-alpha that tried to do this by queueing the response on
17804 the connection's buffer before shutting down, but that really
17805 isn't the same thing at all. Bug located by Matt Edman.
17807 o Minor bugfixes (misc):
17808 - Correctly check for bad options to the "PublishServerDescriptor"
17809 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
17810 - Stop leaking memory on failing case of base32_decode, and make
17811 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
17812 - Don't try to download extrainfo documents when we're trying to
17813 fetch enough directory info to build a circuit: having enough
17814 info should get priority. Bugfix on 0.2.0.x.
17815 - Don't complain that "your server has not managed to confirm that its
17816 ports are reachable" if we haven't been able to build any circuits
17817 yet. Bug found by spending four hours without a v3 consensus. Bugfix
17819 - Detect the reason for failing to mmap a descriptor file we just
17820 wrote, and give a more useful log message. Fixes bug 533. Bugfix
17823 o Code simplifications and refactoring:
17824 - Remove support for the old bw_accounting file: we've been storing
17825 bandwidth accounting information in the state file since
17826 0.1.2.5-alpha. This may result in bandwidth accounting errors
17827 if you try to upgrade from 0.1.1.x or earlier, or if you try to
17828 downgrade to 0.1.1.x or earlier.
17829 - New convenience code to locate a file within the DataDirectory.
17830 - Move non-authority functionality out of dirvote.c.
17831 - Refactor the arguments for router_pick_{directory_|trusteddir}server
17832 so that they all take the same named flags.
17835 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
17836 Unix users an easy way to script their Tor process (e.g. by
17837 adjusting bandwidth based on the time of the day).
17840 Changes in version 0.2.0.8-alpha - 2007-10-12
17841 This eighth development snapshot fixes a crash bug that's been bothering
17842 us since February 2007, lets bridge authorities store a list of bridge
17843 descriptors they've seen, gets v3 directory voting closer to working,
17844 starts caching v3 directory consensus documents on directory mirrors,
17845 and fixes a variety of smaller issues including some minor memory leaks.
17847 o Major features (router descriptor cache):
17848 - Store routers in a file called cached-descriptors instead of in
17849 cached-routers. Initialize cached-descriptors from cached-routers
17850 if the old format is around. The new format allows us to store
17851 annotations along with descriptors.
17852 - Use annotations to record the time we received each descriptor, its
17853 source, and its purpose.
17854 - Disable the SETROUTERPURPOSE controller command: it is now
17856 - Controllers should now specify cache=no or cache=yes when using
17857 the +POSTDESCRIPTOR command.
17858 - Bridge authorities now write bridge descriptors to disk, meaning
17859 we can export them to other programs and begin distributing them
17862 o Major features (directory authorities):
17863 - When a v3 authority is missing votes or signatures, it now tries
17865 - Directory authorities track weighted fractional uptime as well as
17866 weighted mean-time-between failures. WFU is suitable for deciding
17867 whether a node is "usually up", while MTBF is suitable for deciding
17868 whether a node is "likely to stay up." We need both, because
17869 "usually up" is a good requirement for guards, while "likely to
17870 stay up" is a good requirement for long-lived connections.
17872 o Major features (v3 directory system):
17873 - Caches now download v3 network status documents as needed,
17874 and download the descriptors listed in them.
17875 - All hosts now attempt to download and keep fresh v3 authority
17876 certificates, and re-attempt after failures.
17877 - More internal-consistency checks for vote parsing.
17879 o Major bugfixes (crashes):
17880 - If a connection is shut down abruptly because of something that
17881 happened inside connection_flushed_some(), do not call
17882 connection_finished_flushing(). Should fix bug 451. Bugfix on
17885 o Major bugfixes (performance):
17886 - Fix really bad O(n^2) performance when parsing a long list of
17887 routers: Instead of searching the entire list for an "extra-info "
17888 string which usually wasn't there, once for every routerinfo
17889 we read, just scan lines forward until we find one we like.
17891 - When we add data to a write buffer in response to the data on that
17892 write buffer getting low because of a flush, do not consider the
17893 newly added data as a candidate for immediate flushing, but rather
17894 make it wait until the next round of writing. Otherwise, we flush
17895 and refill recursively, and a single greedy TLS connection can
17896 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
17898 o Minor features (v3 authority system):
17899 - Add more ways for tools to download the votes that lead to the
17901 - Send a 503 when low on bandwidth and a vote, consensus, or
17902 certificate is requested.
17903 - If-modified-since is now implemented properly for all kinds of
17904 certificate requests.
17906 o Minor bugfixes (network statuses):
17907 - Tweak the implementation of proposal 109 slightly: allow at most
17908 two Tor servers on the same IP address, except if it's the location
17909 of a directory authority, in which case allow five. Bugfix on
17912 o Minor bugfixes (controller):
17913 - When sending a status event to the controller telling it that an
17914 OR address is reachable, set the port correctly. (Previously we
17915 were reporting the dir port.) Bugfix on 0.1.2.x.
17917 o Minor bugfixes (v3 directory system):
17918 - Fix logic to look up a cert by its signing key digest. Bugfix on
17920 - Only change the reply to a vote to "OK" if it's not already
17921 set. This gets rid of annoying "400 OK" log messages, which may
17922 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
17923 - When we get a valid consensus, recompute the voting schedule.
17924 - Base the valid-after time of a vote on the consensus voting
17925 schedule, not on our preferred schedule.
17926 - Make the return values and messages from signature uploads and
17927 downloads more sensible.
17928 - Fix a memory leak when serving votes and consensus documents, and
17929 another when serving certificates.
17931 o Minor bugfixes (performance):
17932 - Use a slightly simpler string hashing algorithm (copying Python's
17933 instead of Java's) and optimize our digest hashing algorithm to take
17934 advantage of 64-bit platforms and to remove some possibly-costly
17936 - Fix a minor memory leak whenever we parse guards from our state
17937 file. Bugfix on 0.2.0.7-alpha.
17938 - Fix a minor memory leak whenever we write out a file. Bugfix on
17940 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
17941 command. Bugfix on 0.2.0.5-alpha.
17943 o Minor bugfixes (portability):
17944 - On some platforms, accept() can return a broken address. Detect
17945 this more quietly, and deal accordingly. Fixes bug 483.
17946 - Stop calling tor_strlower() on uninitialized memory in some cases.
17947 Bugfix in 0.2.0.7-alpha.
17949 o Minor bugfixes (usability):
17950 - Treat some 403 responses from directory servers as INFO rather than
17951 WARN-severity events.
17952 - It's not actually an error to find a non-pending entry in the DNS
17953 cache when canceling a pending resolve. Don't log unless stuff is
17954 fishy. Resolves bug 463.
17956 o Minor bugfixes (anonymity):
17957 - Never report that we've used more bandwidth than we're willing to
17958 relay: it leaks how much non-relay traffic we're using. Resolves
17960 - When looking for a circuit to cannibalize, consider family as well
17961 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
17962 circuit cannibalization).
17964 o Code simplifications and refactoring:
17965 - Make a bunch of functions static. Remove some dead code.
17966 - Pull out about a third of the really big routerlist.c; put it in a
17967 new module, networkstatus.c.
17968 - Merge the extra fields in local_routerstatus_t back into
17969 routerstatus_t: we used to need one routerstatus_t for each
17970 authority's opinion, plus a local_routerstatus_t for the locally
17971 computed consensus opinion. To save space, we put the locally
17972 modified fields into local_routerstatus_t, and only the common
17973 stuff into routerstatus_t. But once v3 directories are in use,
17974 clients and caches will no longer need to hold authority opinions;
17975 thus, the rationale for keeping the types separate is now gone.
17976 - Make the code used to reschedule and reattempt downloads more
17978 - Turn all 'Are we a directory server/mirror?' logic into a call to
17980 - Remove the code to generate the oldest (v1) directory format.
17981 The code has been disabled since 0.2.0.5-alpha.
17984 Changes in version 0.2.0.7-alpha - 2007-09-21
17985 This seventh development snapshot makes bridges work again, makes bridge
17986 authorities work for the first time, fixes two huge performance flaws
17987 in hidden services, and fixes a variety of minor issues.
17989 o New directory authorities:
17990 - Set up moria1 and tor26 as the first v3 directory authorities. See
17991 doc/spec/dir-spec.txt for details on the new directory design.
17993 o Major bugfixes (crashes):
17994 - Fix possible segfaults in functions called from
17995 rend_process_relay_cell(). Bugfix on 0.1.2.x.
17997 o Major bugfixes (bridges):
17998 - Fix a bug that made servers send a "404 Not found" in response to
17999 attempts to fetch their server descriptor. This caused Tor servers
18000 to take many minutes to establish reachability for their DirPort,
18001 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
18002 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
18003 users configure that and specify a bridge with an identity
18004 fingerprint, now they will lookup the bridge descriptor at the
18005 default bridge authority via a one-hop tunnel, but once circuits
18006 are established they will switch to a three-hop tunnel for later
18007 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
18009 o Major bugfixes (hidden services):
18010 - Hidden services were choosing introduction points uniquely by
18011 hexdigest, but when constructing the hidden service descriptor
18012 they merely wrote the (potentially ambiguous) nickname.
18013 - Clients now use the v2 intro format for hidden service
18014 connections: they specify their chosen rendezvous point by identity
18015 digest rather than by (potentially ambiguous) nickname. Both
18016 are bugfixes on 0.1.2.x, and they could speed up hidden service
18017 connections dramatically. Thanks to Karsten Loesing.
18019 o Minor features (security):
18020 - As a client, do not believe any server that tells us that an
18021 address maps to an internal address space.
18022 - Make it possible to enable HashedControlPassword and
18023 CookieAuthentication at the same time.
18025 o Minor features (guard nodes):
18026 - Tag every guard node in our state file with the version that
18027 we believe added it, or with our own version if we add it. This way,
18028 if a user temporarily runs an old version of Tor and then switches
18029 back to a new one, she doesn't automatically lose her guards.
18031 o Minor features (speed):
18032 - When implementing AES counter mode, update only the portions of the
18033 counter buffer that need to change, and don't keep separate
18034 network-order and host-order counters when they are the same (i.e.,
18035 on big-endian hosts.)
18037 o Minor features (controller):
18038 - Accept LF instead of CRLF on controller, since some software has a
18039 hard time generating real Internet newlines.
18040 - Add GETINFO values for the server status events
18041 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
18044 o Removed features:
18045 - Routers no longer include bandwidth-history lines in their
18046 descriptors; this information is already available in extra-info
18047 documents, and including it in router descriptors took up 60%
18048 (!) of compressed router descriptor downloads. Completes
18049 implementation of proposal 104.
18050 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
18051 and TorControl.py, as they use the old v0 controller protocol,
18052 and are obsoleted by TorFlow anyway.
18053 - Drop support for v1 rendezvous descriptors, since we never used
18054 them anyway, and the code has probably rotted by now. Based on
18055 patch from Karsten Loesing.
18056 - On OSX, stop warning the user that kqueue support in libevent is
18057 "experimental", since it seems to have worked fine for ages.
18060 - When generating information telling us how to extend to a given
18061 router, do not try to include the nickname if it is absent. Fixes
18062 bug 467. Bugfix on 0.2.0.3-alpha.
18063 - Fix a user-triggerable (but not remotely-triggerable) segfault
18064 in expand_filename(). Bugfix on 0.1.2.x.
18065 - Fix a memory leak when freeing incomplete requests from DNSPort.
18066 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
18067 - Don't try to access (or alter) the state file when running
18068 --list-fingerprint or --verify-config or --hash-password. (Resolves
18069 bug 499.) Bugfix on 0.1.2.x.
18070 - Servers used to decline to publish their DirPort if their
18071 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
18072 were below a threshold. Now they only look at BandwidthRate and
18073 RelayBandwidthRate. Bugfix on 0.1.2.x.
18074 - Remove an optimization in the AES counter-mode code that assumed
18075 that the counter never exceeded 2^68. When the counter can be set
18076 arbitrarily as an IV (as it is by Karsten's new hidden services
18077 code), this assumption no longer holds. Bugfix on 0.1.2.x.
18078 - Resume listing "AUTHORITY" flag for authorities in network status.
18079 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
18081 o Code simplifications and refactoring:
18082 - Revamp file-writing logic so we don't need to have the entire
18083 contents of a file in memory at once before we write to disk. Tor,
18085 - Turn "descriptor store" into a full-fledged type.
18086 - Move all NT services code into a separate source file.
18087 - Unify all code that computes medians, percentile elements, etc.
18088 - Get rid of a needless malloc when parsing address policies.
18091 Changes in version 0.1.2.17 - 2007-08-30
18092 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
18093 X bundles. Vidalia 0.0.14 makes authentication required for the
18094 ControlPort in the default configuration, which addresses important
18095 security risks. Everybody who uses Vidalia (or another controller)
18098 In addition, this Tor update fixes major load balancing problems with
18099 path selection, which should speed things up a lot once many people
18102 o Major bugfixes (security):
18103 - We removed support for the old (v0) control protocol. It has been
18104 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
18105 become more of a headache than it's worth.
18107 o Major bugfixes (load balancing):
18108 - When choosing nodes for non-guard positions, weight guards
18109 proportionally less, since they already have enough load. Patch
18111 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
18112 will allow fast Tor servers to get more attention.
18113 - When we're upgrading from an old Tor version, forget our current
18114 guards and pick new ones according to the new weightings. These
18115 three load balancing patches could raise effective network capacity
18116 by a factor of four. Thanks to Mike Perry for measurements.
18118 o Major bugfixes (stream expiration):
18119 - Expire not-yet-successful application streams in all cases if
18120 they've been around longer than SocksTimeout. Right now there are
18121 some cases where the stream will live forever, demanding a new
18122 circuit every 15 seconds. Fixes bug 454; reported by lodger.
18124 o Minor features (controller):
18125 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
18126 is valid before any authentication has been received. It tells
18127 a controller what kind of authentication is expected, and what
18128 protocol is spoken. Implements proposal 119.
18130 o Minor bugfixes (performance):
18131 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
18132 greatly speeding up loading cached-routers from disk on startup.
18133 - Disable sentinel-based debugging for buffer code: we squashed all
18134 the bugs that this was supposed to detect a long time ago, and now
18135 its only effect is to change our buffer sizes from nice powers of
18136 two (which platform mallocs tend to like) to values slightly over
18137 powers of two (which make some platform mallocs sad).
18139 o Minor bugfixes (misc):
18140 - If exit bandwidth ever exceeds one third of total bandwidth, then
18141 use the correct formula to weight exit nodes when choosing paths.
18142 Based on patch from Mike Perry.
18143 - Choose perfectly fairly among routers when choosing by bandwidth and
18144 weighting by fraction of bandwidth provided by exits. Previously, we
18145 would choose with only approximate fairness, and correct ourselves
18146 if we ran off the end of the list.
18147 - If we require CookieAuthentication but we fail to write the
18148 cookie file, we would warn but not exit, and end up in a state
18149 where no controller could authenticate. Now we exit.
18150 - If we require CookieAuthentication, stop generating a new cookie
18151 every time we change any piece of our config.
18152 - Refuse to start with certain directory authority keys, and
18153 encourage people using them to stop.
18154 - Terminate multi-line control events properly. Original patch
18156 - Fix a minor memory leak when we fail to find enough suitable
18157 servers to choose a circuit.
18158 - Stop leaking part of the descriptor when we run into a particularly
18159 unparseable piece of it.
18162 Changes in version 0.2.0.6-alpha - 2007-08-26
18163 This sixth development snapshot features a new Vidalia version in the
18164 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
18165 the ControlPort in the default configuration, which addresses important
18168 In addition, this snapshot fixes major load balancing problems
18169 with path selection, which should speed things up a lot once many
18170 people have upgraded. The directory authorities also use a new
18171 mean-time-between-failure approach to tracking which servers are stable,
18172 rather than just looking at the most recent uptime.
18174 o New directory authorities:
18175 - Set up Tonga as the default bridge directory authority.
18178 - Directory authorities now track servers by weighted
18179 mean-times-between-failures. When we have 4 or more days of data,
18180 use measured MTBF rather than declared uptime to decide whether
18181 to call a router Stable. Implements proposal 108.
18183 o Major bugfixes (load balancing):
18184 - When choosing nodes for non-guard positions, weight guards
18185 proportionally less, since they already have enough load. Patch
18187 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
18188 will allow fast Tor servers to get more attention.
18189 - When we're upgrading from an old Tor version, forget our current
18190 guards and pick new ones according to the new weightings. These
18191 three load balancing patches could raise effective network capacity
18192 by a factor of four. Thanks to Mike Perry for measurements.
18194 o Major bugfixes (descriptor parsing):
18195 - Handle unexpected whitespace better in malformed descriptors. Bug
18196 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
18199 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
18200 GETINFO for Torstat to use until it can switch to using extrainfos.
18201 - Optionally (if built with -DEXPORTMALLINFO) export the output
18202 of mallinfo via http, as tor/mallinfo.txt. Only accessible
18206 - Do not intermix bridge routers with controller-added
18207 routers. (Bugfix on 0.2.0.x)
18208 - Do not fail with an assert when accept() returns an unexpected
18209 address family. Addresses but does not wholly fix bug 483. (Bugfix
18211 - Let directory authorities startup even when they can't generate
18212 a descriptor immediately, e.g. because they don't know their
18214 - Stop putting the authentication cookie in a file called "0"
18215 in your working directory if you don't specify anything for the
18216 new CookieAuthFile option. Reported by Matt Edman.
18217 - Make it possible to read the PROTOCOLINFO response in a way that
18218 conforms to our control-spec. Reported by Matt Edman.
18219 - Fix a minor memory leak when we fail to find enough suitable
18220 servers to choose a circuit. Bugfix on 0.1.2.x.
18221 - Stop leaking part of the descriptor when we run into a particularly
18222 unparseable piece of it. Bugfix on 0.1.2.x.
18223 - Unmap the extrainfo cache file on exit.
18226 Changes in version 0.2.0.5-alpha - 2007-08-19
18227 This fifth development snapshot fixes compilation on Windows again;
18228 fixes an obnoxious client-side bug that slowed things down and put
18229 extra load on the network; gets us closer to using the v3 directory
18230 voting scheme; makes it easier for Tor controllers to use cookie-based
18231 authentication; and fixes a variety of other bugs.
18233 o Removed features:
18234 - Version 1 directories are no longer generated in full. Instead,
18235 authorities generate and serve "stub" v1 directories that list
18236 no servers. This will stop Tor versions 0.1.0.x and earlier from
18237 working, but (for security reasons) nobody should be running those
18240 o Major bugfixes (compilation, 0.2.0.x):
18241 - Try to fix Win32 compilation again: improve checking for IPv6 types.
18242 - Try to fix MSVC compilation: build correctly on platforms that do
18243 not define s6_addr16 or s6_addr32.
18244 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
18247 o Major bugfixes (stream expiration):
18248 - Expire not-yet-successful application streams in all cases if
18249 they've been around longer than SocksTimeout. Right now there are
18250 some cases where the stream will live forever, demanding a new
18251 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
18252 reported by lodger.
18254 o Minor features (directory servers):
18255 - When somebody requests a list of statuses or servers, and we have
18256 none of those, return a 404 rather than an empty 200.
18258 o Minor features (directory voting):
18259 - Store v3 consensus status consensuses on disk, and reload them
18262 o Minor features (security):
18263 - Warn about unsafe ControlPort configurations.
18264 - Refuse to start with certain directory authority keys, and
18265 encourage people using them to stop.
18267 o Minor features (controller):
18268 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
18269 is valid before any authentication has been received. It tells
18270 a controller what kind of authentication is expected, and what
18271 protocol is spoken. Implements proposal 119.
18272 - New config option CookieAuthFile to choose a new location for the
18273 cookie authentication file, and config option
18274 CookieAuthFileGroupReadable to make it group-readable.
18276 o Minor features (unit testing):
18277 - Add command-line arguments to unit-test executable so that we can
18278 invoke any chosen test from the command line rather than having
18279 to run the whole test suite at once; and so that we can turn on
18280 logging for the unit tests.
18282 o Minor bugfixes (on 0.1.2.x):
18283 - If we require CookieAuthentication but we fail to write the
18284 cookie file, we would warn but not exit, and end up in a state
18285 where no controller could authenticate. Now we exit.
18286 - If we require CookieAuthentication, stop generating a new cookie
18287 every time we change any piece of our config.
18288 - When loading bandwidth history, do not believe any information in
18289 the future. Fixes bug 434.
18290 - When loading entry guard information, do not believe any information
18292 - When we have our clock set far in the future and generate an
18293 onion key, then re-set our clock to be correct, we should not stop
18294 the onion key from getting rotated.
18295 - Clean up torrc sample config file.
18296 - Do not automatically run configure from autogen.sh. This
18297 non-standard behavior tended to annoy people who have built other
18300 o Minor bugfixes (on 0.2.0.x):
18301 - Fix a bug with AutomapHostsOnResolve that would always cause
18302 the second request to fail. Bug reported by Kate. Bugfix on
18304 - Fix a bug in ADDRMAP controller replies that would sometimes
18305 try to print a NULL. Patch from tup.
18306 - Read v3 directory authority keys from the right location.
18307 - Numerous bugfixes to directory voting code.
18310 Changes in version 0.1.2.16 - 2007-08-01
18311 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
18312 remote attacker in certain situations to rewrite the user's torrc
18313 configuration file. This can completely compromise anonymity of users
18314 in most configurations, including those running the Vidalia bundles,
18315 TorK, etc. Or worse.
18317 o Major security fixes:
18318 - Close immediately after missing authentication on control port;
18319 do not allow multiple authentication attempts.
18322 Changes in version 0.2.0.4-alpha - 2007-08-01
18323 This fourth development snapshot fixes a critical security vulnerability
18324 for most users, specifically those running Vidalia, TorK, etc. Everybody
18325 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
18327 o Major security fixes:
18328 - Close immediately after missing authentication on control port;
18329 do not allow multiple authentication attempts.
18331 o Major bugfixes (compilation):
18332 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
18335 o Minor features (performance):
18336 - Be even more aggressive about releasing RAM from small
18337 empty buffers. Thanks to our free-list code, this shouldn't be too
18338 performance-intensive.
18339 - Disable sentinel-based debugging for buffer code: we squashed all
18340 the bugs that this was supposed to detect a long time ago, and
18341 now its only effect is to change our buffer sizes from nice
18342 powers of two (which platform mallocs tend to like) to values
18343 slightly over powers of two (which make some platform mallocs sad).
18344 - Log malloc statistics from mallinfo() on platforms where it
18348 Changes in version 0.2.0.3-alpha - 2007-07-29
18349 This third development snapshot introduces new experimental
18350 blocking-resistance features and a preliminary version of the v3
18351 directory voting design, and includes many other smaller features
18355 - The first pieces of our "bridge" design for blocking-resistance
18356 are implemented. People can run bridge directory authorities;
18357 people can run bridges; and people can configure their Tor clients
18358 with a set of bridges to use as the first hop into the Tor network.
18359 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
18361 - Create listener connections before we setuid to the configured
18362 User and Group. Now non-Windows users can choose port values
18363 under 1024, start Tor as root, and have Tor bind those ports
18364 before it changes to another UID. (Windows users could already
18366 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
18367 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
18368 on "vserver" accounts. (Patch from coderman.)
18369 - Be even more aggressive about separating local traffic from relayed
18370 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
18372 o Major features (experimental):
18373 - First cut of code for "v3 dir voting": directory authorities will
18374 vote on a common network status document rather than each publishing
18375 their own opinion. This code needs more testing and more corner-case
18376 handling before it's ready for use.
18379 - Directory authorities now call routers Fast if their bandwidth is
18380 at least 100KB/s, and consider their bandwidth adequate to be a
18381 Guard if it is at least 250KB/s, no matter the medians. This fix
18382 complements proposal 107. [Bugfix on 0.1.2.x]
18383 - Directory authorities now never mark more than 3 servers per IP as
18384 Valid and Running. (Implements proposal 109, by Kevin Bauer and
18386 - Minor change to organizationName and commonName generation
18387 procedures in TLS certificates during Tor handshakes, to invalidate
18388 some earlier censorware approaches. This is not a long-term
18389 solution, but applying it will give us a bit of time to look into
18390 the epidemiology of countermeasures as they spread.
18392 o Major bugfixes (directory):
18393 - Rewrite directory tokenization code to never run off the end of
18394 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
18396 o Minor features (controller):
18397 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
18398 match requests to applications. (Patch from Robert Hogan.)
18399 - Report address and port correctly on connections to DNSPort. (Patch
18400 from Robert Hogan.)
18401 - Add a RESOLVE command to launch hostname lookups. (Original patch
18402 from Robert Hogan.)
18403 - Add GETINFO status/enough-dir-info to let controllers tell whether
18404 Tor has downloaded sufficient directory information. (Patch
18406 - You can now use the ControlSocket option to tell Tor to listen for
18407 controller connections on Unix domain sockets on systems that
18408 support them. (Patch from Peter Palfrader.)
18409 - STREAM NEW events are generated for DNSPort requests and for
18410 tunneled directory connections. (Patch from Robert Hogan.)
18411 - New "GETINFO address-mappings/*" command to get address mappings
18412 with expiry information. "addr-mappings/*" is now deprecated.
18415 o Minor features (misc):
18416 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
18418 - The tor-gencert tool for v3 directory authorities now creates all
18419 files as readable to the file creator only, and write-protects
18420 the authority identity key.
18421 - When dumping memory usage, list bytes used in buffer memory
18423 - When running with dmalloc, dump more stats on hup and on exit.
18424 - Directory authorities now fail quickly and (relatively) harmlessly
18425 if they generate a network status document that is somehow
18428 o Traffic load balancing improvements:
18429 - If exit bandwidth ever exceeds one third of total bandwidth, then
18430 use the correct formula to weight exit nodes when choosing paths.
18431 (Based on patch from Mike Perry.)
18432 - Choose perfectly fairly among routers when choosing by bandwidth and
18433 weighting by fraction of bandwidth provided by exits. Previously, we
18434 would choose with only approximate fairness, and correct ourselves
18435 if we ran off the end of the list. [Bugfix on 0.1.2.x]
18437 o Performance improvements:
18438 - Be more aggressive with freeing buffer RAM or putting it on the
18440 - Use Critical Sections rather than Mutexes for synchronizing threads
18441 on win32; Mutexes are heavier-weight, and designed for synchronizing
18444 o Deprecated and removed features:
18445 - RedirectExits is now deprecated.
18446 - Stop allowing address masks that do not correspond to bit prefixes.
18447 We have warned about these for a really long time; now it's time
18448 to reject them. (Patch from croup.)
18450 o Minor bugfixes (directory):
18451 - Fix another crash bug related to extra-info caching. (Bug found by
18452 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
18453 - Directories no longer return a "304 not modified" when they don't
18454 have the networkstatus the client asked for. Also fix a memory
18455 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
18456 - We had accidentally labelled 0.1.2.x directory servers as not
18457 suitable for begin_dir requests, and had labelled no directory
18458 servers as suitable for uploading extra-info documents. [Bugfix
18461 o Minor bugfixes (dns):
18462 - Fix a crash when DNSPort is set more than once. (Patch from Robert
18463 Hogan.) [Bugfix on 0.2.0.2-alpha]
18464 - Add DNSPort connections to the global connection list, so that we
18465 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
18467 - Fix a dangling reference that could lead to a crash when DNSPort is
18468 changed or closed (Patch from Robert Hogan.) [Bugfix on
18471 o Minor bugfixes (controller):
18472 - Provide DNS expiry times in GMT, not in local time. For backward
18473 compatibility, ADDRMAP events only provide GMT expiry in an extended
18474 field. "GETINFO address-mappings" always does the right thing.
18475 - Use CRLF line endings properly in NS events.
18476 - Terminate multi-line control events properly. (Original patch
18477 from tup.) [Bugfix on 0.1.2.x-alpha]
18478 - Do not include spaces in SOURCE_ADDR fields in STREAM
18479 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
18482 Changes in version 0.1.2.15 - 2007-07-17
18483 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
18484 problems, fixes compilation on BSD, and fixes a variety of other
18485 bugs. Everybody should upgrade.
18487 o Major bugfixes (compilation):
18488 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
18490 o Major bugfixes (crashes):
18491 - Try even harder not to dereference the first character after
18492 an mmap(). Reported by lodger.
18493 - Fix a crash bug in directory authorities when we re-number the
18494 routerlist while inserting a new router.
18495 - When the cached-routers file is an even multiple of the page size,
18496 don't run off the end and crash. (Fixes bug 455; based on idea
18498 - Fix eventdns.c behavior on Solaris: It is critical to include
18499 orconfig.h _before_ sys/types.h, so that we can get the expected
18500 definition of _FILE_OFFSET_BITS.
18502 o Major bugfixes (security):
18503 - Fix a possible buffer overrun when using BSD natd support. Bug
18505 - When sending destroy cells from a circuit's origin, don't include
18506 the reason for tearing down the circuit. The spec says we didn't,
18507 and now we actually don't. Reported by lodger.
18508 - Keep streamids from different exits on a circuit separate. This
18509 bug may have allowed other routers on a given circuit to inject
18510 cells into streams. Reported by lodger; fixes bug 446.
18511 - If there's a never-before-connected-to guard node in our list,
18512 never choose any guards past it. This way we don't expand our
18513 guard list unless we need to.
18515 o Minor bugfixes (guard nodes):
18516 - Weight guard selection by bandwidth, so that low-bandwidth nodes
18517 don't get overused as guards.
18519 o Minor bugfixes (directory):
18520 - Correctly count the number of authorities that recommend each
18521 version. Previously, we were under-counting by 1.
18522 - Fix a potential crash bug when we load many server descriptors at
18523 once and some of them make others of them obsolete. Fixes bug 458.
18525 o Minor bugfixes (hidden services):
18526 - Stop tearing down the whole circuit when the user asks for a
18527 connection to a port that the hidden service didn't configure.
18530 o Minor bugfixes (misc):
18531 - On Windows, we were preventing other processes from reading
18532 cached-routers while Tor was running. Reported by janbar.
18533 - Fix a possible (but very unlikely) bug in picking routers by
18534 bandwidth. Add a log message to confirm that it is in fact
18535 unlikely. Patch from lodger.
18536 - Backport a couple of memory leak fixes.
18537 - Backport miscellaneous cosmetic bugfixes.
18540 Changes in version 0.2.0.2-alpha - 2007-06-02
18541 o Major bugfixes on 0.2.0.1-alpha:
18542 - Fix an assertion failure related to servers without extra-info digests.
18543 Resolves bugs 441 and 442.
18545 o Minor features (directory):
18546 - Support "If-Modified-Since" when answering HTTP requests for
18547 directories, running-routers documents, and network-status documents.
18548 (There's no need to support it for router descriptors, since those
18549 are downloaded by descriptor digest.)
18551 o Minor build issues:
18552 - Clear up some MIPSPro compiler warnings.
18553 - When building from a tarball on a machine that happens to have SVK
18554 installed, report the micro-revision as whatever version existed
18555 in the tarball, not as "x".
18558 Changes in version 0.2.0.1-alpha - 2007-06-01
18559 This early development snapshot provides new features for people running
18560 Tor as both a client and a server (check out the new RelayBandwidth
18561 config options); lets Tor run as a DNS proxy; and generally moves us
18562 forward on a lot of fronts.
18564 o Major features, server usability:
18565 - New config options RelayBandwidthRate and RelayBandwidthBurst:
18566 a separate set of token buckets for relayed traffic. Right now
18567 relayed traffic is defined as answers to directory requests, and
18568 OR connections that don't have any local circuits on them.
18570 o Major features, client usability:
18571 - A client-side DNS proxy feature to replace the need for
18572 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
18573 for DNS requests on port 9999, use the Tor network to resolve them
18574 anonymously, and send the reply back like a regular DNS server.
18575 The code still only implements a subset of DNS.
18576 - Make PreferTunneledDirConns and TunnelDirConns work even when
18577 we have no cached directory info. This means Tor clients can now
18578 do all of their connections protected by TLS.
18580 o Major features, performance and efficiency:
18581 - Directory authorities accept and serve "extra info" documents for
18582 routers. These documents contain fields from router descriptors
18583 that aren't usually needed, and that use a lot of excess
18584 bandwidth. Once these fields are removed from router descriptors,
18585 the bandwidth savings should be about 60%. [Partially implements
18587 - Servers upload extra-info documents to any authority that accepts
18588 them. Authorities (and caches that have been configured to download
18589 extra-info documents) download them as needed. [Partially implements
18591 - Change the way that Tor buffers data that it is waiting to write.
18592 Instead of queueing data cells in an enormous ring buffer for each
18593 client->OR or OR->OR connection, we now queue cells on a separate
18594 queue for each circuit. This lets us use less slack memory, and
18595 will eventually let us be smarter about prioritizing different kinds
18597 - Use memory pools to allocate cells with better speed and memory
18598 efficiency, especially on platforms where malloc() is inefficient.
18599 - Stop reading on edge connections when their corresponding circuit
18600 buffers are full; start again as the circuits empty out.
18602 o Major features, other:
18603 - Add an HSAuthorityRecordStats option that hidden service authorities
18604 can use to track statistics of overall hidden service usage without
18605 logging information that would be very useful to an attacker.
18606 - Start work implementing multi-level keys for directory authorities:
18607 Add a standalone tool to generate key certificates. (Proposal 103.)
18610 - Directory authorities now call routers Stable if they have an
18611 uptime of at least 30 days, even if that's not the median uptime
18612 in the network. Implements proposal 107, suggested by Kevin Bauer
18615 o Minor fixes (resource management):
18616 - Count the number of open sockets separately from the number
18617 of active connection_t objects. This will let us avoid underusing
18618 our allocated connection limit.
18619 - We no longer use socket pairs to link an edge connection to an
18620 anonymous directory connection or a DirPort test connection.
18621 Instead, we track the link internally and transfer the data
18622 in-process. This saves two sockets per "linked" connection (at the
18623 client and at the server), and avoids the nasty Windows socketpair()
18625 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
18626 for every single inactive connection_t. Free items from the
18627 4k/16k-buffer free lists when they haven't been used for a while.
18629 o Minor features (build):
18630 - Make autoconf search for libevent, openssl, and zlib consistently.
18631 - Update deprecated macros in configure.in.
18632 - When warning about missing headers, tell the user to let us
18633 know if the compile succeeds anyway, so we can downgrade the
18635 - Include the current subversion revision as part of the version
18636 string: either fetch it directly if we're in an SVN checkout, do
18637 some magic to guess it if we're in an SVK checkout, or use
18638 the last-detected version if we're building from a .tar.gz.
18639 Use this version consistently in log messages.
18641 o Minor features (logging):
18642 - Always prepend "Bug: " to any log message about a bug.
18643 - Put a platform string (e.g. "Linux i686") in the startup log
18644 message, so when people paste just their logs, we know if it's
18645 OpenBSD or Windows or what.
18646 - When logging memory usage, break down memory used in buffers by
18649 o Minor features (directory system):
18650 - New config option V2AuthoritativeDirectory that all directory
18651 authorities should set. This will let future authorities choose
18652 not to serve V2 directory information.
18653 - Directory authorities allow multiple router descriptors and/or extra
18654 info documents to be uploaded in a single go. This will make
18655 implementing proposal 104 simpler.
18657 o Minor features (controller):
18658 - Add a new config option __DisablePredictedCircuits designed for
18659 use by the controller, when we don't want Tor to build any circuits
18661 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
18662 so we can exit from the middle of the circuit.
18663 - Implement "getinfo status/circuit-established".
18664 - Implement "getinfo status/version/..." so a controller can tell
18665 whether the current version is recommended, and whether any versions
18666 are good, and how many authorities agree. (Patch from shibz.)
18668 o Minor features (hidden services):
18669 - Allow multiple HiddenServicePort directives with the same virtual
18670 port; when they occur, the user is sent round-robin to one
18671 of the target ports chosen at random. Partially fixes bug 393 by
18672 adding limited ad-hoc round-robining.
18674 o Minor features (other):
18676 - Add a new AutomapHostsOnResolve option: when it is enabled, any
18677 resolve request for hosts matching a given pattern causes Tor to
18678 generate an internal virtual address mapping for that host. This
18679 allows DNSPort to work sensibly with hidden service users. By
18680 default, .exit and .onion addresses are remapped; the list of
18681 patterns can be reconfigured with AutomapHostsSuffixes.
18682 - Add an "-F" option to tor-resolve to force a resolve for a .onion
18683 address. Thanks to the AutomapHostsOnResolve option, this is no
18684 longer a completely silly thing to do.
18685 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
18686 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
18687 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
18688 minus 1 byte: the actual maximum declared bandwidth.
18690 o Removed features:
18691 - Removed support for the old binary "version 0" controller protocol.
18692 This has been deprecated since 0.1.1, and warnings have been issued
18693 since 0.1.2. When we encounter a v0 control message, we now send
18694 back an error and close the connection.
18695 - Remove the old "dns worker" server DNS code: it hasn't been default
18696 since 0.1.2.2-alpha, and all the servers seem to be using the new
18699 o Minor bugfixes (portability):
18700 - Even though Windows is equally happy with / and \ as path separators,
18701 try to use \ consistently on Windows and / consistently on Unix: it
18702 makes the log messages nicer.
18703 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
18704 - Read resolv.conf files correctly on platforms where read() returns
18705 partial results on small file reads.
18707 o Minor bugfixes (directory):
18708 - Correctly enforce that elements of directory objects do not appear
18709 more often than they are allowed to appear.
18710 - When we are reporting the DirServer line we just parsed, we were
18711 logging the second stanza of the key fingerprint, not the first.
18713 o Minor bugfixes (logging):
18714 - When we hit an EOF on a log (probably because we're shutting down),
18715 don't try to remove the log from the list: just mark it as
18716 unusable. (Bulletproofs against bug 222.)
18718 o Minor bugfixes (other):
18719 - In the exitlist script, only consider the most recently published
18720 server descriptor for each server. Also, when the user requests
18721 a list of servers that _reject_ connections to a given address,
18722 explicitly exclude the IPs that also have servers that accept
18723 connections to that address. (Resolves bug 405.)
18724 - Stop allowing hibernating servers to be "stable" or "fast".
18725 - On Windows, we were preventing other processes from reading
18726 cached-routers while Tor was running. (Reported by janbar)
18727 - Make the NodeFamilies config option work. (Reported by
18728 lodger -- it has never actually worked, even though we added it
18730 - Check return values from pthread_mutex functions.
18731 - Don't save non-general-purpose router descriptors to the disk cache,
18732 because we have no way of remembering what their purpose was when
18734 - Add even more asserts to hunt down bug 417.
18735 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
18736 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
18737 Add a log message to confirm that it is in fact unlikely.
18739 o Minor bugfixes (controller):
18740 - Make 'getinfo fingerprint' return a 551 error if we're not a
18741 server, so we match what the control spec claims we do. Reported
18743 - Fix a typo in an error message when extendcircuit fails that
18744 caused us to not follow the \r\n-based delimiter protocol. Reported
18747 o Code simplifications and refactoring:
18748 - Stop passing around circuit_t and crypt_path_t pointers that are
18749 implicit in other procedure arguments.
18750 - Drop the old code to choke directory connections when the
18751 corresponding OR connections got full: thanks to the cell queue
18752 feature, OR conns don't get full any more.
18753 - Make dns_resolve() handle attaching connections to circuits
18754 properly, so the caller doesn't have to.
18755 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
18756 - Keep the connection array as a dynamic smartlist_t, rather than as
18757 a fixed-sized array. This is important, as the number of connections
18758 is becoming increasingly decoupled from the number of sockets.
18761 Changes in version 0.1.2.14 - 2007-05-25
18762 Tor 0.1.2.14 changes the addresses of two directory authorities (this
18763 change especially affects those who serve or use hidden services),
18764 and fixes several other crash- and security-related bugs.
18766 o Directory authority changes:
18767 - Two directory authorities (moria1 and moria2) just moved to new
18768 IP addresses. This change will particularly affect those who serve
18769 or use hidden services.
18771 o Major bugfixes (crashes):
18772 - If a directory server runs out of space in the connection table
18773 as it's processing a begin_dir request, it will free the exit stream
18774 but leave it attached to the circuit, leading to unpredictable
18775 behavior. (Reported by seeess, fixes bug 425.)
18776 - Fix a bug in dirserv_remove_invalid() that would cause authorities
18777 to corrupt memory under some really unlikely scenarios.
18778 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
18779 - Avoid segfaults when reading from mmaped descriptor file. (Reported
18782 o Major bugfixes (security):
18783 - When choosing an entry guard for a circuit, avoid using guards
18784 that are in the same family as the chosen exit -- not just guards
18785 that are exactly the chosen exit. (Reported by lodger.)
18787 o Major bugfixes (resource management):
18788 - If a directory authority is down, skip it when deciding where to get
18789 networkstatus objects or descriptors. Otherwise we keep asking
18790 every 10 seconds forever. Fixes bug 384.
18791 - Count it as a failure if we fetch a valid network-status but we
18792 don't want to keep it. Otherwise we'll keep fetching it and keep
18793 not wanting to keep it. Fixes part of bug 422.
18794 - If all of our dirservers have given us bad or no networkstatuses
18795 lately, then stop hammering them once per minute even when we
18796 think they're failed. Fixes another part of bug 422.
18799 - Actually set the purpose correctly for descriptors inserted with
18800 purpose=controller.
18801 - When we have k non-v2 authorities in our DirServer config,
18802 we ignored the last k authorities in the list when updating our
18804 - Correctly back-off from requesting router descriptors that we are
18805 having a hard time downloading.
18806 - Read resolv.conf files correctly on platforms where read() returns
18807 partial results on small file reads.
18808 - Don't rebuild the entire router store every time we get 32K of
18809 routers: rebuild it when the journal gets very large, or when
18810 the gaps in the store get very large.
18813 - When routers publish SVN revisions in their router descriptors,
18814 authorities now include those versions correctly in networkstatus
18816 - Warn when using a version of libevent before 1.3b to run a server on
18817 OSX or BSD: these versions interact badly with userspace threads.
18820 Changes in version 0.1.2.13 - 2007-04-24
18821 This release features some major anonymity fixes, such as safer path
18822 selection; better client performance; faster bootstrapping, better
18823 address detection, and better DNS support for servers; write limiting as
18824 well as read limiting to make servers easier to run; and a huge pile of
18825 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
18827 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
18828 of the Freenode IRC network, remembering his patience and vision for
18829 free speech on the Internet.
18832 - Fix a memory leak when we ask for "all" networkstatuses and we
18833 get one we don't recognize.
18834 - Add more asserts to hunt down bug 417.
18835 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
18838 Changes in version 0.1.2.12-rc - 2007-03-16
18840 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
18841 directory information requested inside Tor connections (i.e. via
18842 begin_dir cells). It only triggered when the same connection was
18843 serving other data at the same time. Reported by seeess.
18846 - When creating a circuit via the controller, send a 'launched'
18847 event when we're done, so we follow the spec better.
18850 Changes in version 0.1.2.11-rc - 2007-03-15
18851 o Minor bugfixes (controller), reported by daejees:
18852 - Correct the control spec to match how the code actually responds
18853 to 'getinfo addr-mappings/*'.
18854 - The control spec described a GUARDS event, but the code
18855 implemented a GUARD event. Standardize on GUARD, but let people
18856 ask for GUARDS too.
18859 Changes in version 0.1.2.10-rc - 2007-03-07
18860 o Major bugfixes (Windows):
18861 - Do not load the NT services library functions (which may not exist)
18862 just to detect if we're a service trying to shut down. Now we run
18863 on Win98 and friends again.
18865 o Minor bugfixes (other):
18866 - Clarify a couple of log messages.
18867 - Fix a misleading socks5 error number.
18870 Changes in version 0.1.2.9-rc - 2007-03-02
18871 o Major bugfixes (Windows):
18872 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
18873 of the usual GCC "%llu". This prevents a bug when saving 64-bit
18874 int configuration values: the high-order 32 bits would get
18875 truncated. In particular, we were being bitten by the default
18876 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
18877 and maybe also bug 397.)
18879 o Minor bugfixes (performance):
18880 - Use OpenSSL's AES implementation on platforms where it's faster.
18881 This could save us as much as 10% CPU usage.
18883 o Minor bugfixes (server):
18884 - Do not rotate onion key immediately after setting it for the first
18887 o Minor bugfixes (directory authorities):
18888 - Stop calling servers that have been hibernating for a long time
18889 "stable". Also, stop letting hibernating or obsolete servers affect
18890 uptime and bandwidth cutoffs.
18891 - Stop listing hibernating servers in the v1 directory.
18893 o Minor bugfixes (hidden services):
18894 - Upload hidden service descriptors slightly less often, to reduce
18895 load on authorities.
18897 o Minor bugfixes (other):
18898 - Fix an assert that could trigger if a controller quickly set then
18899 cleared EntryNodes. Bug found by Udo van den Heuvel.
18900 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
18902 - Fix a potential race condition in the rpm installer. Found by
18904 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
18905 of 2 as indicating that the server is completely bad; it sometimes
18906 means that the server is just bad for the request in question. (may fix
18907 the last of bug 326.)
18908 - Disable encrypted directory connections when we don't have a server
18909 descriptor for the destination. We'll get this working again in
18913 Changes in version 0.1.2.8-beta - 2007-02-26
18914 o Major bugfixes (crashes):
18915 - Stop crashing when the controller asks us to resetconf more than
18916 one config option at once. (Vidalia 0.0.11 does this.)
18917 - Fix a crash that happened on Win98 when we're given command-line
18918 arguments: don't try to load NT service functions from advapi32.dll
18919 except when we need them. (Bug introduced in 0.1.2.7-alpha;
18921 - Fix a longstanding obscure crash bug that could occur when
18922 we run out of DNS worker processes. (Resolves bug 390.)
18924 o Major bugfixes (hidden services):
18925 - Correctly detect whether hidden service descriptor downloads are
18926 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
18928 o Major bugfixes (accounting):
18929 - When we start during an accounting interval before it's time to wake
18930 up, remember to wake up at the correct time. (May fix bug 342.)
18932 o Minor bugfixes (controller):
18933 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
18934 clear the corresponding on_circuit variable, and remember later
18935 that we don't need to send a redundant CLOSED event. Resolves part
18937 - Report events where a resolve succeeded or where we got a socks
18938 protocol error correctly, rather than calling both of them
18940 - Change reported stream target addresses to IP consistently when
18941 we finally get the IP from an exit node.
18942 - Send log messages to the controller even if they happen to be very
18945 o Minor bugfixes (other):
18946 - Display correct results when reporting which versions are
18947 recommended, and how recommended they are. (Resolves bug 383.)
18948 - Improve our estimates for directory bandwidth to be less random:
18949 guess that an unrecognized directory will have the average bandwidth
18950 from all known directories, not that it will have the average
18951 bandwidth from those directories earlier than it on the list.
18952 - If we start a server with ClientOnly 1, then set ClientOnly to 0
18953 and hup, stop triggering an assert based on an empty onion_key.
18954 - On platforms with no working mmap() equivalent, don't warn the
18955 user when cached-routers doesn't exist.
18956 - Warn the user when mmap() [or its equivalent] fails for some reason
18957 other than file-not-found.
18958 - Don't warn the user when cached-routers.new doesn't exist: that's
18959 perfectly fine when starting up for the first time.
18960 - When EntryNodes are configured, rebuild the guard list to contain,
18961 in order: the EntryNodes that were guards before; the rest of the
18962 EntryNodes; the nodes that were guards before.
18963 - Mask out all signals in sub-threads; only the libevent signal
18964 handler should be processing them. This should prevent some crashes
18965 on some machines using pthreads. (Patch from coderman.)
18966 - Fix switched arguments on memset in the implementation of
18967 tor_munmap() for systems with no mmap() call.
18968 - When Tor receives a router descriptor that it asked for, but
18969 no longer wants (because it has received fresh networkstatuses
18970 in the meantime), do not warn the user. Cache the descriptor if
18971 we're a cache; drop it if we aren't.
18972 - Make earlier entry guards _really_ get retried when the network
18974 - On a malformed DNS reply, always give an error to the corresponding
18976 - Build with recent libevents on platforms that do not define the
18977 nonstandard types "u_int8_t" and friends.
18979 o Minor features (controller):
18980 - Warn the user when an application uses the obsolete binary v0
18981 control protocol. We're planning to remove support for it during
18982 the next development series, so it's good to give people some
18984 - Add STREAM_BW events to report per-entry-stream bandwidth
18985 use. (Patch from Robert Hogan.)
18986 - Rate-limit SIGNEWNYM signals in response to controllers that
18987 impolitely generate them for every single stream. (Patch from
18988 mwenge; closes bug 394.)
18989 - Make REMAP stream events have a SOURCE (cache or exit), and
18990 make them generated in every case where we get a successful
18991 connected or resolved cell.
18993 o Minor bugfixes (performance):
18994 - Call router_have_min_dir_info half as often. (This is showing up in
18995 some profiles, but not others.)
18996 - When using GCC, make log_debug never get called at all, and its
18997 arguments never get evaluated, when no debug logs are configured.
18998 (This is showing up in some profiles, but not others.)
19001 - Remove some never-implemented options. Mark PathlenCoinWeight as
19003 - Implement proposal 106: Stop requiring clients to have well-formed
19004 certificates; stop checking nicknames in certificates. (Clients
19005 have certificates so that they can look like Tor servers, but in
19006 the future we might want to allow them to look like regular TLS
19007 clients instead. Nicknames in certificates serve no purpose other
19008 than making our protocol easier to recognize on the wire.)
19009 - Revise messages on handshake failure again to be even more clear about
19010 which are incoming connections and which are outgoing.
19011 - Discard any v1 directory info that's over 1 month old (for
19012 directories) or over 1 week old (for running-routers lists).
19013 - Do not warn when individual nodes in the configuration's EntryNodes,
19014 ExitNodes, etc are down: warn only when all possible nodes
19015 are down. (Fixes bug 348.)
19016 - Always remove expired routers and networkstatus docs before checking
19017 whether we have enough information to build circuits. (Fixes
19019 - Put a lower-bound on MaxAdvertisedBandwidth.
19022 Changes in version 0.1.2.7-alpha - 2007-02-06
19023 o Major bugfixes (rate limiting):
19024 - Servers decline directory requests much more aggressively when
19025 they're low on bandwidth. Otherwise they end up queueing more and
19026 more directory responses, which can't be good for latency.
19027 - But never refuse directory requests from local addresses.
19028 - Fix a memory leak when sending a 503 response for a networkstatus
19030 - Be willing to read or write on local connections (e.g. controller
19031 connections) even when the global rate limiting buckets are empty.
19032 - If our system clock jumps back in time, don't publish a negative
19033 uptime in the descriptor. Also, don't let the global rate limiting
19034 buckets go absurdly negative.
19035 - Flush local controller connection buffers periodically as we're
19036 writing to them, so we avoid queueing 4+ megabytes of data before
19039 o Major bugfixes (NT services):
19040 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
19041 command-line flag so that admins can override the default by saying
19042 "tor --service install --user "SomeUser"". This will not affect
19043 existing installed services. Also, warn the user that the service
19044 will look for its configuration file in the service user's
19045 %appdata% directory. (We can't do the 'hardwire the user's appdata
19046 directory' trick any more, since we may not have read access to that
19049 o Major bugfixes (other):
19050 - Previously, we would cache up to 16 old networkstatus documents
19051 indefinitely, if they came from nontrusted authorities. Now we
19052 discard them if they are more than 10 days old.
19053 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
19055 - Detect and reject malformed DNS responses containing circular
19057 - If exits are rare enough that we're not marking exits as guards,
19058 ignore exit bandwidth when we're deciding the required bandwidth
19060 - When we're handling a directory connection tunneled over Tor,
19061 don't fill up internal memory buffers with all the data we want
19062 to tunnel; instead, only add it if the OR connection that will
19063 eventually receive it has some room for it. (This can lead to
19064 slowdowns in tunneled dir connections; a better solution will have
19065 to wait for 0.2.0.)
19067 o Minor bugfixes (dns):
19068 - Add some defensive programming to eventdns.c in an attempt to catch
19069 possible memory-stomping bugs.
19070 - Detect and reject DNS replies containing IPv4 or IPv6 records with
19071 an incorrect number of bytes. (Previously, we would ignore the
19073 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
19074 in the correct order, and doesn't crash.
19075 - Free memory held in recently-completed DNS lookup attempts on exit.
19076 This was not a memory leak, but may have been hiding memory leaks.
19077 - Handle TTL values correctly on reverse DNS lookups.
19078 - Treat failure to parse resolv.conf as an error.
19080 o Minor bugfixes (other):
19081 - Fix crash with "tor --list-fingerprint" (reported by seeess).
19082 - When computing clock skew from directory HTTP headers, consider what
19083 time it was when we finished asking for the directory, not what
19085 - Expire socks connections if they spend too long waiting for the
19086 handshake to finish. Previously we would let them sit around for
19087 days, if the connecting application didn't close them either.
19088 - And if the socks handshake hasn't started, don't send a
19089 "DNS resolve socks failed" handshake reply; just close it.
19090 - Stop using C functions that OpenBSD's linker doesn't like.
19091 - Don't launch requests for descriptors unless we have networkstatuses
19092 from at least half of the authorities. This delays the first
19093 download slightly under pathological circumstances, but can prevent
19094 us from downloading a bunch of descriptors we don't need.
19095 - Do not log IPs with TLS failures for incoming TLS
19096 connections. (Fixes bug 382.)
19097 - If the user asks to use invalid exit nodes, be willing to use
19099 - Stop using the reserved ac_cv namespace in our configure script.
19100 - Call stat() slightly less often; use fstat() when possible.
19101 - Refactor the way we handle pending circuits when an OR connection
19102 completes or fails, in an attempt to fix a rare crash bug.
19103 - Only rewrite a conn's address based on X-Forwarded-For: headers
19104 if it's a parseable public IP address; and stop adding extra quotes
19105 to the resulting address.
19108 - Weight directory requests by advertised bandwidth. Now we can
19109 let servers enable write limiting but still allow most clients to
19110 succeed at their directory requests. (We still ignore weights when
19111 choosing a directory authority; I hope this is a feature.)
19114 - Create a new file ReleaseNotes which was the old ChangeLog. The
19115 new ChangeLog file now includes the summaries for all development
19117 - Check for addresses with invalid characters at the exit as well
19118 as at the client, and warn less verbosely when they fail. You can
19119 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
19120 - Adapt a patch from goodell to let the contrib/exitlist script
19121 take arguments rather than require direct editing.
19122 - Inform the server operator when we decide not to advertise a
19123 DirPort due to AccountingMax enabled or a low BandwidthRate. It
19124 was confusing Zax, so now we're hopefully more helpful.
19125 - Bring us one step closer to being able to establish an encrypted
19126 directory tunnel without knowing a descriptor first. Still not
19127 ready yet. As part of the change, now assume we can use a
19128 create_fast cell if we don't know anything about a router.
19129 - Allow exit nodes to use nameservers running on ports other than 53.
19130 - Servers now cache reverse DNS replies.
19131 - Add an --ignore-missing-torrc command-line option so that we can
19132 get the "use sensible defaults if the configuration file doesn't
19133 exist" behavior even when specifying a torrc location on the command
19136 o Minor features (controller):
19137 - Track reasons for OR connection failure; make these reasons
19138 available via the controller interface. (Patch from Mike Perry.)
19139 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
19140 can learn when clients are sending malformed hostnames to Tor.
19141 - Clean up documentation for controller status events.
19142 - Add a REMAP status to stream events to note that a stream's
19143 address has changed because of a cached address or a MapAddress
19147 Changes in version 0.1.2.6-alpha - 2007-01-09
19149 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
19150 connection handles more than 4 gigs in either direction, we crash.
19151 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
19152 advertised exit node, somebody might try to exit from us when
19153 we're bootstrapping and before we've built our descriptor yet.
19154 Refuse the connection rather than crashing.
19157 - Warn if we (as a server) find that we've resolved an address that we
19158 weren't planning to resolve.
19159 - Warn that using select() on any libevent version before 1.1 will be
19160 unnecessarily slow (even for select()).
19161 - Flush ERR-level controller status events just like we currently
19162 flush ERR-level log events, so that a Tor shutdown doesn't prevent
19163 the controller from learning about current events.
19165 o Minor features (more controller status events):
19166 - Implement EXTERNAL_ADDRESS server status event so controllers can
19167 learn when our address changes.
19168 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
19169 can learn when directories reject our descriptor.
19170 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
19171 can learn when a client application is speaking a non-socks protocol
19173 - Implement DANGEROUS_SOCKS client status event so controllers
19174 can learn when a client application is leaking DNS addresses.
19175 - Implement BUG general status event so controllers can learn when
19176 Tor is unhappy about its internal invariants.
19177 - Implement CLOCK_SKEW general status event so controllers can learn
19178 when Tor thinks the system clock is set incorrectly.
19179 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
19180 server status events so controllers can learn when their descriptors
19181 are accepted by a directory.
19182 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
19183 server status events so controllers can learn about Tor's progress in
19184 deciding whether it's reachable from the outside.
19185 - Implement BAD_LIBEVENT general status event so controllers can learn
19186 when we have a version/method combination in libevent that needs to
19188 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
19189 and DNS_USELESS server status events so controllers can learn
19190 about changes to DNS server status.
19192 o Minor features (directory):
19193 - Authorities no longer recommend exits as guards if this would shift
19194 too much load to the exit nodes.
19197 Changes in version 0.1.2.5-alpha - 2007-01-06
19199 - Enable write limiting as well as read limiting. Now we sacrifice
19200 capacity if we're pushing out lots of directory traffic, rather
19201 than overrunning the user's intended bandwidth limits.
19202 - Include TLS overhead when counting bandwidth usage; previously, we
19203 would count only the bytes sent over TLS, but not the bytes used
19205 - Support running the Tor service with a torrc not in the same
19206 directory as tor.exe and default to using the torrc located in
19207 the %appdata%\Tor\ of the user who installed the service. Patch
19209 - Servers now check for the case when common DNS requests are going to
19210 wildcarded addresses (i.e. all getting the same answer), and change
19211 their exit policy to reject *:* if it's happening.
19212 - Implement BEGIN_DIR cells, so we can connect to the directory
19213 server via TLS to do encrypted directory requests rather than
19214 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
19215 config options if you like.
19217 o Minor features (config and docs):
19218 - Start using the state file to store bandwidth accounting data:
19219 the bw_accounting file is now obsolete. We'll keep generating it
19220 for a while for people who are still using 0.1.2.4-alpha.
19221 - Try to batch changes to the state file so that we do as few
19222 disk writes as possible while still storing important things in
19224 - The state file and the bw_accounting file get saved less often when
19225 the AvoidDiskWrites config option is set.
19226 - Make PIDFile work on Windows (untested).
19227 - Add internal descriptions for a bunch of configuration options:
19228 accessible via controller interface and in comments in saved
19230 - Reject *:563 (NNTPS) in the default exit policy. We already reject
19231 NNTP by default, so this seems like a sensible addition.
19232 - Clients now reject hostnames with invalid characters. This should
19233 avoid some inadvertent info leaks. Add an option
19234 AllowNonRFC953Hostnames to disable this behavior, in case somebody
19235 is running a private network with hosts called @, !, and #.
19236 - Add a maintainer script to tell us which options are missing
19237 documentation: "make check-docs".
19238 - Add a new address-spec.txt document to describe our special-case
19239 addresses: .exit, .onion, and .noconnnect.
19241 o Minor features (DNS):
19242 - Ongoing work on eventdns infrastructure: now it has dns server
19243 and ipv6 support. One day Tor will make use of it.
19244 - Add client-side caching for reverse DNS lookups.
19245 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
19246 - When we change nameservers or IP addresses, reset and re-launch
19247 our tests for DNS hijacking.
19249 o Minor features (directory):
19250 - Authorities now specify server versions in networkstatus. This adds
19251 about 2% to the size of compressed networkstatus docs, and allows
19252 clients to tell which servers support BEGIN_DIR and which don't.
19253 The implementation is forward-compatible with a proposed future
19254 protocol version scheme not tied to Tor versions.
19255 - DirServer configuration lines now have an orport= option so
19256 clients can open encrypted tunnels to the authorities without
19257 having downloaded their descriptors yet. Enabled for moria1,
19258 moria2, tor26, and lefkada now in the default configuration.
19259 - Directory servers are more willing to send a 503 "busy" if they
19260 are near their write limit, especially for v1 directory requests.
19261 Now they can use their limited bandwidth for actual Tor traffic.
19262 - Clients track responses with status 503 from dirservers. After a
19263 dirserver has given us a 503, we try not to use it until an hour has
19264 gone by, or until we have no dirservers that haven't given us a 503.
19265 - When we get a 503 from a directory, and we're not a server, we don't
19266 count the failure against the total number of failures allowed
19267 for the thing we're trying to download.
19268 - Report X-Your-Address-Is correctly from tunneled directory
19269 connections; don't report X-Your-Address-Is when it's an internal
19270 address; and never believe reported remote addresses when they're
19272 - Protect against an unlikely DoS attack on directory servers.
19273 - Add a BadDirectory flag to network status docs so that authorities
19274 can (eventually) tell clients about caches they believe to be
19277 o Minor features (controller):
19278 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
19279 - Reimplement GETINFO so that info/names stays in sync with the
19281 - Implement "GETINFO fingerprint".
19282 - Implement "SETEVENTS GUARD" so controllers can get updates on
19283 entry guard status as it changes.
19285 o Minor features (clean up obsolete pieces):
19286 - Remove some options that have been deprecated since at least
19287 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
19288 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
19289 to set log options.
19290 - We no longer look for identity and onion keys in "identity.key" and
19291 "onion.key" -- these were replaced by secret_id_key and
19292 secret_onion_key in 0.0.8pre1.
19293 - We no longer require unrecognized directory entries to be
19296 o Major bugfixes (security):
19297 - Stop sending the HttpProxyAuthenticator string to directory
19298 servers when directory connections are tunnelled through Tor.
19299 - Clients no longer store bandwidth history in the state file.
19300 - Do not log introduction points for hidden services if SafeLogging
19302 - When generating bandwidth history, round down to the nearest
19303 1k. When storing accounting data, round up to the nearest 1k.
19304 - When we're running as a server, remember when we last rotated onion
19305 keys, so that we will rotate keys once they're a week old even if
19306 we never stay up for a week ourselves.
19308 o Major bugfixes (other):
19309 - Fix a longstanding bug in eventdns that prevented the count of
19310 timed-out resolves from ever being reset. This bug caused us to
19311 give up on a nameserver the third time it timed out, and try it
19312 10 seconds later... and to give up on it every time it timed out
19314 - Take out the '5 second' timeout from the connection retry
19315 schedule. Now the first connect attempt will wait a full 10
19316 seconds before switching to a new circuit. Perhaps this will help
19317 a lot. Based on observations from Mike Perry.
19318 - Fix a bug on the Windows implementation of tor_mmap_file() that
19319 would prevent the cached-routers file from ever loading. Reported
19323 - Fix an assert failure when a directory authority sets
19324 AuthDirRejectUnlisted and then receives a descriptor from an
19325 unlisted router. Reported by seeess.
19326 - Avoid a double-free when parsing malformed DirServer lines.
19327 - Fix a bug when a BSD-style PF socket is first used. Patch from
19329 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
19330 to resolve an address at a given exit node even when they ask for
19332 - Servers no longer ever list themselves in their "family" line,
19333 even if configured to do so. This makes it easier to configure
19334 family lists conveniently.
19335 - When running as a server, don't fall back to 127.0.0.1 when no
19336 nameservers are configured in /etc/resolv.conf; instead, make the
19337 user fix resolv.conf or specify nameservers explicitly. (Resolves
19339 - Stop accepting certain malformed ports in configured exit policies.
19340 - Don't re-write the fingerprint file every restart, unless it has
19342 - Stop warning when a single nameserver fails: only warn when _all_ of
19343 our nameservers have failed. Also, when we only have one nameserver,
19344 raise the threshold for deciding that the nameserver is dead.
19345 - Directory authorities now only decide that routers are reachable
19346 if their identity keys are as expected.
19347 - When the user uses bad syntax in the Log config line, stop
19348 suggesting other bad syntax as a replacement.
19349 - Correctly detect ipv6 DNS capability on OpenBSD.
19351 o Minor bugfixes (controller):
19352 - Report the circuit number correctly in STREAM CLOSED events. Bug
19353 reported by Mike Perry.
19354 - Do not report bizarre values for results of accounting GETINFOs
19355 when the last second's write or read exceeds the allotted bandwidth.
19356 - Report "unrecognized key" rather than an empty string when the
19357 controller tries to fetch a networkstatus that doesn't exist.
19360 Changes in version 0.1.1.26 - 2006-12-14
19361 o Security bugfixes:
19362 - Stop sending the HttpProxyAuthenticator string to directory
19363 servers when directory connections are tunnelled through Tor.
19364 - Clients no longer store bandwidth history in the state file.
19365 - Do not log introduction points for hidden services if SafeLogging
19369 - Fix an assert failure when a directory authority sets
19370 AuthDirRejectUnlisted and then receives a descriptor from an
19371 unlisted router (reported by seeess).
19374 Changes in version 0.1.2.4-alpha - 2006-12-03
19376 - Add support for using natd; this allows FreeBSDs earlier than
19377 5.1.2 to have ipfw send connections through Tor without using
19378 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
19381 - Make all connections to addresses of the form ".noconnect"
19382 immediately get closed. This lets application/controller combos
19383 successfully test whether they're talking to the same Tor by
19384 watching for STREAM events.
19385 - Make cross.sh cross-compilation script work even when autogen.sh
19386 hasn't been run. (Patch from Michael Mohr.)
19387 - Statistics dumped by -USR2 now include a breakdown of public key
19388 operations, for profiling.
19391 - Fix a major leak when directory authorities parse their
19392 approved-routers list, a minor memory leak when we fail to pick
19393 an exit node, and a few rare leaks on errors.
19394 - Handle TransPort connections even when the server sends data before
19395 the client sends data. Previously, the connection would just hang
19396 until the client sent data. (Patch from tup based on patch from
19398 - Avoid assert failure when our cached-routers file is empty on
19402 - Don't log spurious warnings when we see a circuit close reason we
19403 don't recognize; it's probably just from a newer version of Tor.
19404 - Have directory authorities allow larger amounts of drift in uptime
19405 without replacing the server descriptor: previously, a server that
19406 restarted every 30 minutes could have 48 "interesting" descriptors
19408 - Start linking to the Tor specification and Tor reference manual
19409 correctly in the Windows installer.
19410 - Add Vidalia to the OS X uninstaller script, so when we uninstall
19411 Tor/Privoxy we also uninstall Vidalia.
19412 - Resume building on Irix64, and fix a lot of warnings from its
19413 MIPSpro C compiler.
19414 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
19415 when we're running as a client.
19418 Changes in version 0.1.1.25 - 2006-11-04
19420 - When a client asks us to resolve (rather than connect to)
19421 an address, and we have a cached answer, give them the cached
19422 answer. Previously, we would give them no answer at all.
19423 - We were building exactly the wrong circuits when we predict
19424 hidden service requirements, meaning Tor would have to build all
19425 its circuits on demand.
19426 - If none of our live entry guards have a high uptime, but we
19427 require a guard with a high uptime, try adding a new guard before
19428 we give up on the requirement. This patch should make long-lived
19429 connections more stable on average.
19430 - When testing reachability of our DirPort, don't launch new
19431 tests when there's already one in progress -- unreachable
19432 servers were stacking up dozens of testing streams.
19434 o Security bugfixes:
19435 - When the user sends a NEWNYM signal, clear the client-side DNS
19436 cache too. Otherwise we continue to act on previous information.
19439 - Avoid a memory corruption bug when creating a hash table for
19441 - Avoid possibility of controller-triggered crash when misusing
19442 certain commands from a v0 controller on platforms that do not
19443 handle printf("%s",NULL) gracefully.
19444 - Avoid infinite loop on unexpected controller input.
19445 - Don't log spurious warnings when we see a circuit close reason we
19446 don't recognize; it's probably just from a newer version of Tor.
19447 - Add Vidalia to the OS X uninstaller script, so when we uninstall
19448 Tor/Privoxy we also uninstall Vidalia.
19451 Changes in version 0.1.2.3-alpha - 2006-10-29
19453 - Prepare for servers to publish descriptors less often: never
19454 discard a descriptor simply for being too old until either it is
19455 recommended by no authorities, or until we get a better one for
19456 the same router. Make caches consider retaining old recommended
19457 routers for even longer.
19458 - If most authorities set a BadExit flag for a server, clients
19459 don't think of it as a general-purpose exit. Clients only consider
19460 authorities that advertise themselves as listing bad exits.
19461 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
19462 headers for content, so that we can work better in the presence of
19463 caching HTTP proxies.
19464 - Allow authorities to list nodes as bad exits by fingerprint or by
19467 o Minor features, controller:
19468 - Add a REASON field to CIRC events; for backward compatibility, this
19469 field is sent only to controllers that have enabled the extended
19470 event format. Also, add additional reason codes to explain why
19471 a given circuit has been destroyed or truncated. (Patches from
19473 - Add a REMOTE_REASON field to extended CIRC events to tell the
19474 controller about why a remote OR told us to close a circuit.
19475 - Stream events also now have REASON and REMOTE_REASON fields,
19476 working much like those for circuit events.
19477 - There's now a GETINFO ns/... field so that controllers can ask Tor
19478 about the current status of a router.
19479 - A new event type "NS" to inform a controller when our opinion of
19480 a router's status has changed.
19481 - Add a GETINFO events/names and GETINFO features/names so controllers
19482 can tell which events and features are supported.
19483 - A new CLEARDNSCACHE signal to allow controllers to clear the
19484 client-side DNS cache without expiring circuits.
19486 o Security bugfixes:
19487 - When the user sends a NEWNYM signal, clear the client-side DNS
19488 cache too. Otherwise we continue to act on previous information.
19491 - Avoid sending junk to controllers or segfaulting when a controller
19492 uses EVENT_NEW_DESC with verbose nicknames.
19493 - Stop triggering asserts if the controller tries to extend hidden
19494 service circuits (reported by mwenge).
19495 - Avoid infinite loop on unexpected controller input.
19496 - When the controller does a "GETINFO network-status", tell it
19497 about even those routers whose descriptors are very old, and use
19498 long nicknames where appropriate.
19499 - Change NT service functions to be loaded on demand. This lets us
19500 build with MinGW without breaking Tor for Windows 98 users.
19501 - Do DirPort reachability tests less often, since a single test
19502 chews through many circuits before giving up.
19503 - In the hidden service example in torrc.sample, stop recommending
19504 esoteric and discouraged hidden service options.
19505 - When stopping an NT service, wait up to 10 sec for it to actually
19506 stop. Patch from Matt Edman; resolves bug 295.
19507 - Fix handling of verbose nicknames with ORCONN controller events:
19508 make them show up exactly when requested, rather than exactly when
19510 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
19511 printing a duplicate "$" in the keys we send (reported by mwenge).
19512 - Correctly set maximum connection limit on Cygwin. (This time
19514 - Try to detect Windows correctly when cross-compiling.
19515 - Detect the size of the routers file correctly even if it is
19516 corrupted (on systems without mmap) or not page-aligned (on systems
19517 with mmap). This bug was harmless.
19518 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
19519 to open a stream fails; now we do in more cases. This should
19520 make clients able to find a good exit faster in some cases, since
19521 unhandleable requests will now get an error rather than timing out.
19522 - Resolve two memory leaks when rebuilding the on-disk router cache
19523 (reported by fookoowa).
19524 - Clean up minor code warnings suggested by the MIPSpro C compiler,
19525 and reported by some Centos users.
19526 - Controller signals now work on non-Unix platforms that don't define
19527 SIGUSR1 and SIGUSR2 the way we expect.
19528 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
19529 values before failing, and always enables eventdns.
19530 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
19531 Try to fix this in configure.in by checking for most functions
19532 before we check for libevent.
19535 Changes in version 0.1.2.2-alpha - 2006-10-07
19537 - Make our async eventdns library on-by-default for Tor servers,
19538 and plan to deprecate the separate dnsworker threads.
19539 - Add server-side support for "reverse" DNS lookups (using PTR
19540 records so clients can determine the canonical hostname for a given
19541 IPv4 address). Only supported by servers using eventdns; servers
19542 now announce in their descriptors whether they support eventdns.
19543 - Specify and implement client-side SOCKS5 interface for reverse DNS
19544 lookups (see doc/socks-extensions.txt).
19545 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
19546 connect to directory servers through Tor. Previously, clients needed
19547 to find Tor exits to make private connections to directory servers.
19548 - Avoid choosing Exit nodes for entry or middle hops when the
19549 total bandwidth available from non-Exit nodes is much higher than
19550 the total bandwidth available from Exit nodes.
19551 - Workaround for name servers (like Earthlink's) that hijack failing
19552 DNS requests and replace the no-such-server answer with a "helpful"
19553 redirect to an advertising-driven search portal. Also work around
19554 DNS hijackers who "helpfully" decline to hijack known-invalid
19555 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
19556 lets you turn it off.
19557 - Send out a burst of long-range padding cells once we've established
19558 that we're reachable. Spread them over 4 circuits, so hopefully
19559 a few will be fast. This exercises our bandwidth and bootstraps
19560 us into the directory more quickly.
19562 o New/improved config options:
19563 - Add new config option "ResolvConf" to let the server operator
19564 choose an alternate resolve.conf file when using eventdns.
19565 - Add an "EnforceDistinctSubnets" option to control our "exclude
19566 servers on the same /16" behavior. It's still on by default; this
19567 is mostly for people who want to operate private test networks with
19568 all the machines on the same subnet.
19569 - If one of our entry guards is on the ExcludeNodes list, or the
19570 directory authorities don't think it's a good guard, treat it as
19571 if it were unlisted: stop using it as a guard, and throw it off
19572 the guards list if it stays that way for a long time.
19573 - Allow directory authorities to be marked separately as authorities
19574 for the v1 directory protocol, the v2 directory protocol, and
19575 as hidden service directories, to make it easier to retire old
19576 authorities. V1 authorities should set "HSAuthoritativeDir 1"
19577 to continue being hidden service authorities too.
19578 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
19580 o Minor features, controller:
19581 - Fix CIRC controller events so that controllers can learn the
19582 identity digests of non-Named servers used in circuit paths.
19583 - Let controllers ask for more useful identifiers for servers. Instead
19584 of learning identity digests for un-Named servers and nicknames
19585 for Named servers, the new identifiers include digest, nickname,
19586 and indication of Named status. Off by default; see control-spec.txt
19587 for more information.
19588 - Add a "getinfo address" controller command so it can display Tor's
19589 best guess to the user.
19590 - New controller event to alert the controller when our server
19591 descriptor has changed.
19592 - Give more meaningful errors on controller authentication failure.
19594 o Minor features, other:
19595 - When asked to resolve a hostname, don't use non-exit servers unless
19596 requested to do so. This allows servers with broken DNS to be
19597 useful to the network.
19598 - Divide eventdns log messages into warn and info messages.
19599 - Reserve the nickname "Unnamed" for routers that can't pick
19600 a hostname: any router can call itself Unnamed; directory
19601 authorities will never allocate Unnamed to any particular router;
19602 clients won't believe that any router is the canonical Unnamed.
19603 - Only include function names in log messages for info/debug messages.
19604 For notice/warn/err, the content of the message should be clear on
19605 its own, and printing the function name only confuses users.
19606 - Avoid some false positives during reachability testing: don't try
19607 to test via a server that's on the same /24 as us.
19608 - If we fail to build a circuit to an intended enclave, and it's
19609 not mandatory that we use that enclave, stop wanting it.
19610 - When eventdns is enabled, allow multithreaded builds on NetBSD and
19611 OpenBSD. (We had previously disabled threads on these platforms
19612 because they didn't have working thread-safe resolver functions.)
19614 o Major bugfixes, anonymity/security:
19615 - If a client asked for a server by name, and there's a named server
19616 in our network-status but we don't have its descriptor yet, we
19617 could return an unnamed server instead.
19618 - Fix NetBSD bug that could allow someone to force uninitialized RAM
19619 to be sent to a server's DNS resolver. This only affects NetBSD
19620 and other platforms that do not bounds-check tolower().
19621 - Reject (most) attempts to use Tor circuits with length one. (If
19622 many people start using Tor as a one-hop proxy, exit nodes become
19623 a more attractive target for compromise.)
19624 - Just because your DirPort is open doesn't mean people should be
19625 able to remotely teach you about hidden service descriptors. Now
19626 only accept rendezvous posts if you've got HSAuthoritativeDir set.
19628 o Major bugfixes, other:
19629 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
19630 - When a client asks the server to resolve (not connect to)
19631 an address, and it has a cached answer, give them the cached answer.
19632 Previously, the server would give them no answer at all.
19633 - Allow really slow clients to not hang up five minutes into their
19634 directory downloads (suggested by Adam J. Richter).
19635 - We were building exactly the wrong circuits when we anticipated
19636 hidden service requirements, meaning Tor would have to build all
19637 its circuits on demand.
19638 - Avoid crashing when we mmap a router cache file of size 0.
19639 - When testing reachability of our DirPort, don't launch new
19640 tests when there's already one in progress -- unreachable
19641 servers were stacking up dozens of testing streams.
19643 o Minor bugfixes, correctness:
19644 - If we're a directory mirror and we ask for "all" network status
19645 documents, we would discard status documents from authorities
19646 we don't recognize.
19647 - Avoid a memory corruption bug when creating a hash table for
19649 - Avoid controller-triggered crash when misusing certain commands
19650 from a v0 controller on platforms that do not handle
19651 printf("%s",NULL) gracefully.
19652 - Don't crash when a controller sends a third argument to an
19653 "extendcircuit" request.
19654 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
19655 response; fix error code when "getinfo dir/status/" fails.
19656 - Avoid crash when telling controller stream-status and a stream
19658 - Patch from Adam Langley to fix assert() in eventdns.c.
19659 - Fix a debug log message in eventdns to say "X resolved to Y"
19660 instead of "X resolved to X".
19661 - Make eventdns give strings for DNS errors, not just error numbers.
19662 - Track unreachable entry guards correctly: don't conflate
19663 'unreachable by us right now' with 'listed as down by the directory
19664 authorities'. With the old code, if a guard was unreachable by
19665 us but listed as running, it would clog our guard list forever.
19666 - Behave correctly in case we ever have a network with more than
19667 2GB/s total advertised capacity.
19668 - Make TrackExitHosts case-insensitive, and fix the behavior of
19669 ".suffix" TrackExitHosts items to avoid matching in the middle of
19671 - Finally fix the openssl warnings from newer gccs that believe that
19672 ignoring a return value is okay, but casting a return value and
19673 then ignoring it is a sign of madness.
19674 - Prevent the contrib/exitlist script from printing the same
19675 result more than once.
19676 - Patch from Steve Hildrey: Generate network status correctly on
19677 non-versioning dirservers.
19678 - Don't listen to the X-Your-Address-Is hint if you did the lookup
19679 via Tor; otherwise you'll think you're the exit node's IP address.
19681 o Minor bugfixes, performance:
19682 - Two small performance improvements on parsing descriptors.
19683 - Major performance improvement on inserting descriptors: change
19684 algorithm from O(n^2) to O(n).
19685 - Make the common memory allocation path faster on machines where
19686 malloc(0) returns a pointer.
19687 - Start remembering X-Your-Address-Is directory hints even if you're
19688 a client, so you can become a server more smoothly.
19689 - Avoid duplicate entries on MyFamily line in server descriptor.
19691 o Packaging, features:
19692 - Remove architecture from OS X builds. The official builds are
19693 now universal binaries.
19694 - The Debian package now uses --verify-config when (re)starting,
19695 to distinguish configuration errors from other errors.
19696 - Update RPMs to require libevent 1.1b.
19698 o Packaging, bugfixes:
19699 - Patches so Tor builds with MinGW on Windows.
19700 - Patches so Tor might run on Cygwin again.
19701 - Resume building on non-gcc compilers and ancient gcc. Resume
19702 building with the -O0 compile flag. Resume building cleanly on
19704 - Run correctly on OS X platforms with case-sensitive filesystems.
19705 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
19706 - Add autoconf checks so Tor can build on Solaris x86 again.
19709 - Documented (and renamed) ServerDNSSearchDomains and
19710 ServerDNSResolvConfFile options.
19711 - Be clearer that the *ListenAddress directives can be repeated
19715 Changes in version 0.1.1.24 - 2006-09-29
19717 - Allow really slow clients to not hang up five minutes into their
19718 directory downloads (suggested by Adam J. Richter).
19719 - Fix major performance regression from 0.1.0.x: instead of checking
19720 whether we have enough directory information every time we want to
19721 do something, only check when the directory information has changed.
19722 This should improve client CPU usage by 25-50%.
19723 - Don't crash if, after a server has been running for a while,
19724 it can't resolve its hostname.
19727 - Allow Tor to start when RunAsDaemon is set but no logs are set.
19728 - Don't crash when the controller receives a third argument to an
19729 "extendcircuit" request.
19730 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
19731 response; fix error code when "getinfo dir/status/" fails.
19732 - Fix configure.in to not produce broken configure files with
19733 more recent versions of autoconf. Thanks to Clint for his auto*
19735 - Fix security bug on NetBSD that could allow someone to force
19736 uninitialized RAM to be sent to a server's DNS resolver. This
19737 only affects NetBSD and other platforms that do not bounds-check
19739 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
19740 methods: these are known to be buggy.
19741 - If we're a directory mirror and we ask for "all" network status
19742 documents, we would discard status documents from authorities
19743 we don't recognize.
19746 Changes in version 0.1.2.1-alpha - 2006-08-27
19748 - Add "eventdns" async dns library from Adam Langley, tweaked to
19749 build on OSX and Windows. Only enabled if you pass the
19750 --enable-eventdns argument to configure.
19751 - Allow servers with no hostname or IP address to learn their
19752 IP address by asking the directory authorities. This code only
19753 kicks in when you would normally have exited with a "no address"
19754 error. Nothing's authenticated, so use with care.
19755 - Rather than waiting a fixed amount of time between retrying
19756 application connections, we wait only 5 seconds for the first,
19757 10 seconds for the second, and 15 seconds for each retry after
19758 that. Hopefully this will improve the expected user experience.
19759 - Patch from Tup to add support for transparent AP connections:
19760 this basically bundles the functionality of trans-proxy-tor
19761 into the Tor mainline. Now hosts with compliant pf/netfilter
19762 implementations can redirect TCP connections straight to Tor
19763 without diverting through SOCKS. Needs docs.
19764 - Busy directory servers save lots of memory by spooling server
19765 descriptors, v1 directories, and v2 networkstatus docs to buffers
19766 as needed rather than en masse. Also mmap the cached-routers
19767 files, so we don't need to keep the whole thing in memory too.
19768 - Automatically avoid picking more than one node from the same
19769 /16 network when constructing a circuit.
19770 - Revise and clean up the torrc.sample that we ship with; add
19771 a section for BandwidthRate and BandwidthBurst.
19774 - Split circuit_t into origin_circuit_t and or_circuit_t, and
19775 split connection_t into edge, or, dir, control, and base structs.
19776 These will save quite a bit of memory on busy servers, and they'll
19777 also help us track down bugs in the code and bugs in the spec.
19778 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
19779 or later. Log when we are doing this, so we can diagnose it when
19780 it fails. (Also, recommend libevent 1.1b for kqueue and
19781 win32 methods; deprecate libevent 1.0b harder; make libevent
19782 recommendation system saner.)
19783 - Start being able to build universal binaries on OS X (thanks
19785 - Export the default exit policy via the control port, so controllers
19786 don't need to guess what it is / will be later.
19787 - Add a man page entry for ProtocolWarnings.
19788 - Add TestVia config option to the man page.
19789 - Remove even more protocol-related warnings from Tor server logs,
19790 such as bad TLS handshakes and malformed begin cells.
19791 - Stop fetching descriptors if you're not a dir mirror and you
19792 haven't tried to establish any circuits lately. [This currently
19793 causes some dangerous behavior, because when you start up again
19794 you'll use your ancient server descriptors.]
19795 - New DirPort behavior: if you have your dirport set, you download
19796 descriptors aggressively like a directory mirror, whether or not
19797 your ORPort is set.
19798 - Get rid of the router_retry_connections notion. Now routers
19799 no longer try to rebuild long-term connections to directory
19800 authorities, and directory authorities no longer try to rebuild
19801 long-term connections to all servers. We still don't hang up
19802 connections in these two cases though -- we need to look at it
19803 more carefully to avoid flapping, and we likely need to wait til
19804 0.1.1.x is obsolete.
19805 - Drop compatibility with obsolete Tors that permit create cells
19806 to have the wrong circ_id_type.
19807 - Re-enable per-connection rate limiting. Get rid of the "OP
19808 bandwidth" concept. Lay groundwork for "bandwidth classes" --
19809 separate global buckets that apply depending on what sort of conn
19811 - Start publishing one minute or so after we find our ORPort
19812 to be reachable. This will help reduce the number of descriptors
19813 we have for ourselves floating around, since it's quite likely
19814 other things (e.g. DirPort) will change during that minute too.
19815 - Fork the v1 directory protocol into its own spec document,
19816 and mark dir-spec.txt as the currently correct (v2) spec.
19819 - When we find our DirPort to be reachable, publish a new descriptor
19820 so we'll tell the world (reported by pnx).
19821 - Publish a new descriptor after we hup/reload. This is important
19822 if our config has changed such that we'll want to start advertising
19823 our DirPort now, etc.
19824 - Allow Tor to start when RunAsDaemon is set but no logs are set.
19825 - When we have a state file we cannot parse, tell the user and
19826 move it aside. Now we avoid situations where the user starts
19827 Tor in 1904, Tor writes a state file with that timestamp in it,
19828 the user fixes her clock, and Tor refuses to start.
19829 - Fix configure.in to not produce broken configure files with
19830 more recent versions of autoconf. Thanks to Clint for his auto*
19832 - "tor --verify-config" now exits with -1(255) or 0 depending on
19833 whether the config options are bad or good.
19834 - Resolve bug 321 when using dnsworkers: append a period to every
19835 address we resolve at the exit node, so that we do not accidentally
19836 pick up local addresses, and so that failing searches are retried
19837 in the resolver search domains. (This is already solved for
19838 eventdns.) (This breaks Blossom servers for now.)
19839 - If we are using an exit enclave and we can't connect, e.g. because
19840 its webserver is misconfigured to not listen on localhost, then
19841 back off and try connecting from somewhere else before we fail.
19844 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
19845 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
19846 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
19847 when the IP address is mapped through MapAddress to a hostname.
19848 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
19849 useless IPv6 DNS resolves.
19850 - Patch suggested by Karsten Loesing: respond to SIGNAL command
19851 before we execute the signal, in case the signal shuts us down.
19852 - Clean up AllowInvalidNodes man page entry.
19853 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
19854 - Add more asserts to track down an assert error on a windows Tor
19855 server with connection_add being called with socket == -1.
19856 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
19857 - Fix misleading log messages: an entry guard that is "unlisted",
19858 as well as not known to be "down" (because we've never heard
19859 of it), is not therefore "up".
19860 - Remove code to special-case "-cvs" ending, since it has not
19861 actually mattered since 0.0.9.
19862 - Make our socks5 handling more robust to broken socks clients:
19863 throw out everything waiting on the buffer in between socks
19864 handshake phases, since they can't possibly (so the theory
19865 goes) have predicted what we plan to respond to them.
19868 Changes in version 0.1.1.23 - 2006-07-30
19870 - Fast Tor servers, especially exit nodes, were triggering asserts
19871 due to a bug in handling the list of pending DNS resolves. Some
19872 bugs still remain here; we're hunting them.
19873 - Entry guards could crash clients by sending unexpected input.
19874 - More fixes on reachability testing: if you find yourself reachable,
19875 then don't ever make any client requests (so you stop predicting
19876 circuits), then hup or have your clock jump, then later your IP
19877 changes, you won't think circuits are working, so you won't try to
19878 test reachability, so you won't publish.
19881 - Avoid a crash if the controller does a resetconf firewallports
19882 and then a setconf fascistfirewall=1.
19883 - Avoid an integer underflow when the dir authority decides whether
19884 a router is stable: we might wrongly label it stable, and compute
19885 a slightly wrong median stability, when a descriptor is published
19887 - Fix a place where we might trigger an assert if we can't build our
19888 own server descriptor yet.
19891 Changes in version 0.1.1.22 - 2006-07-05
19893 - Fix a big bug that was causing servers to not find themselves
19894 reachable if they changed IP addresses. Since only 0.1.1.22+
19895 servers can do reachability testing correctly, now we automatically
19896 make sure to test via one of these.
19897 - Fix to allow clients and mirrors to learn directory info from
19898 descriptor downloads that get cut off partway through.
19899 - Directory authorities had a bug in deciding if a newly published
19900 descriptor was novel enough to make everybody want a copy -- a few
19901 servers seem to be publishing new descriptors many times a minute.
19903 - Fix a rare bug that was causing some servers to complain about
19904 "closing wedged cpuworkers" and skip some circuit create requests.
19905 - Make the Exit flag in directory status documents actually work.
19908 Changes in version 0.1.1.21 - 2006-06-10
19909 o Crash and assert fixes from 0.1.1.20:
19910 - Fix a rare crash on Tor servers that have enabled hibernation.
19911 - Fix a seg fault on startup for Tor networks that use only one
19912 directory authority.
19913 - Fix an assert from a race condition that occurs on Tor servers
19914 while exiting, where various threads are trying to log that they're
19915 exiting, and delete the logs, at the same time.
19916 - Make our unit tests pass again on certain obscure platforms.
19919 - Add support for building SUSE RPM packages.
19920 - Speed up initial bootstrapping for clients: if we are making our
19921 first ever connection to any entry guard, then don't mark it down
19923 - When only one Tor server in the network is labelled as a guard,
19924 and we've already picked him, we would cycle endlessly picking him
19925 again, being unhappy about it, etc. Now we specifically exclude
19926 current guards when picking a new guard.
19927 - Servers send create cells more reliably after the TLS connection
19928 is established: we were sometimes forgetting to send half of them
19929 when we had more than one pending.
19930 - If we get a create cell that asks us to extend somewhere, but the
19931 Tor server there doesn't match the expected digest, we now send
19932 a destroy cell back, rather than silently doing nothing.
19933 - Make options->RedirectExit work again.
19934 - Make cookie authentication for the controller work again.
19935 - Stop being picky about unusual characters in the arguments to
19936 mapaddress. It's none of our business.
19937 - Add a new config option "TestVia" that lets you specify preferred
19938 middle hops to use for test circuits. Perhaps this will let me
19939 debug the reachability problems better.
19941 o Log / documentation fixes:
19942 - If we're a server and some peer has a broken TLS certificate, don't
19943 log about it unless ProtocolWarnings is set, i.e., we want to hear
19944 about protocol violations by others.
19945 - Fix spelling of VirtualAddrNetwork in man page.
19946 - Add a better explanation at the top of the autogenerated torrc file
19947 about what happened to our old torrc.
19950 Changes in version 0.1.1.20 - 2006-05-23
19952 - Downgrade a log severity where servers complain that they're
19954 - Avoid a compile warning on FreeBSD.
19955 - Remove string size limit on NEWDESC messages; solve bug 291.
19956 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
19957 more thoroughly when we're running on windows.
19960 Changes in version 0.1.1.19-rc - 2006-05-03
19962 - Regenerate our local descriptor if it's dirty and we try to use
19963 it locally (e.g. if it changes during reachability detection).
19964 - If we setconf our ORPort to 0, we continued to listen on the
19965 old ORPort and receive connections.
19966 - Avoid a second warning about machine/limits.h on Debian
19968 - Be willing to add our own routerinfo into the routerlist.
19969 Now authorities will include themselves in their directories
19970 and network-statuses.
19971 - Stop trying to upload rendezvous descriptors to every
19972 directory authority: only try the v1 authorities.
19973 - Servers no longer complain when they think they're not
19974 registered with the directory authorities. There were too many
19976 - Backport dist-rpm changes so rpms can be built without errors.
19979 - Implement an option, VirtualAddrMask, to set which addresses
19980 get handed out in response to mapaddress requests. This works
19981 around a bug in tsocks where 127.0.0.0/8 is never socksified.
19984 Changes in version 0.1.1.18-rc - 2006-04-10
19986 - Work harder to download live network-statuses from all the
19987 directory authorities we know about. Improve the threshold
19988 decision logic so we're more robust to edge cases.
19989 - When fetching rendezvous descriptors, we were willing to ask
19990 v2 authorities too, which would always return 404.
19993 - Stop listing down or invalid nodes in the v1 directory. This will
19994 reduce its bulk by about 1/3, and reduce load on directory
19996 - When deciding whether a router is Fast or Guard-worthy, consider
19997 his advertised BandwidthRate and not just the BandwidthCapacity.
19998 - No longer ship INSTALL and README files -- they are useless now.
19999 - Force rpmbuild to behave and honor target_cpu.
20000 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
20001 - Start to include translated versions of the tor-doc-*.html
20002 files, along with the screenshots. Still needs more work.
20003 - Start sending back 512 and 451 errors if mapaddress fails,
20004 rather than not sending anything back at all.
20005 - When we fail to bind or listen on an incoming or outgoing
20006 socket, we should close it before failing. otherwise we just
20007 leak it. (thanks to weasel for finding.)
20008 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
20009 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
20010 - Make NoPublish (even though deprecated) work again.
20011 - Fix a minor security flaw where a versioning auth dirserver
20012 could list a recommended version many times in a row to make
20013 clients more convinced that it's recommended.
20014 - Fix crash bug if there are two unregistered servers running
20015 with the same nickname, one of them is down, and you ask for
20016 them by nickname in your EntryNodes or ExitNodes. Also, try
20017 to pick the one that's running rather than an arbitrary one.
20018 - Fix an infinite loop we could hit if we go offline for too long.
20019 - Complain when we hit WSAENOBUFS on recv() or write() too.
20020 Perhaps this will help us hunt the bug.
20021 - If you're not a versioning dirserver, don't put the string
20022 "client-versions \nserver-versions \n" in your network-status.
20023 - Lower the minimum required number of file descriptors to 1000,
20024 so we can have some overhead for Valgrind on Linux, where the
20025 default ulimit -n is 1024.
20028 - Add tor.dizum.com as the fifth authoritative directory server.
20029 - Add a new config option FetchUselessDescriptors, off by default,
20030 for when you plan to run "exitlist" on your client and you want
20031 to know about even the non-running descriptors.
20034 Changes in version 0.1.1.17-rc - 2006-03-28
20036 - Clients and servers since 0.1.1.10-alpha have been expiring
20037 connections whenever they are idle for 5 minutes and they *do*
20038 have circuits on them. Oops. With this new version, clients will
20039 discard their previous entry guard choices and avoid choosing
20040 entry guards running these flawed versions.
20041 - Fix memory leak when uncompressing concatenated zlib streams. This
20042 was causing substantial leaks over time on Tor servers.
20043 - The v1 directory was including servers as much as 48 hours old,
20044 because that's how the new routerlist->routers works. Now only
20045 include them if they're 20 hours old or less.
20048 - Resume building on irix64, netbsd 2.0, etc.
20049 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
20051 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
20052 and it is confusing some users.
20053 - Mirrors stop caching the v1 directory so often.
20054 - Make the max number of old descriptors that a cache will hold
20055 rise with the number of directory authorities, so we can scale.
20056 - Change our win32 uname() hack to be more forgiving about what
20057 win32 versions it thinks it's found.
20060 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
20062 - When the controller's *setconf commands fail, collect an error
20063 message in a string and hand it back to the controller.
20064 - Make the v2 dir's "Fast" flag based on relative capacity, just
20065 like "Stable" is based on median uptime. Name everything in the
20066 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
20067 - Log server fingerprint on startup, so new server operators don't
20068 have to go hunting around their filesystem for it.
20069 - Return a robots.txt on our dirport to discourage google indexing.
20070 - Let the controller ask for GETINFO dir/status/foo so it can ask
20071 directly rather than connecting to the dir port. Only works when
20072 dirport is set for now.
20074 o New config options rather than constants in the code:
20075 - SocksTimeout: How long do we let a socks connection wait
20076 unattached before we fail it?
20077 - CircuitBuildTimeout: Cull non-open circuits that were born
20078 at least this many seconds ago.
20079 - CircuitIdleTimeout: Cull open clean circuits that were born
20080 at least this many seconds ago.
20083 Changes in version 0.1.1.16-rc - 2006-03-18
20084 o Bugfixes on 0.1.1.15-rc:
20085 - Fix assert when the controller asks to attachstream a connect-wait
20086 or resolve-wait stream.
20087 - Now do address rewriting when the controller asks us to attach
20088 to a particular circuit too. This will let Blossom specify
20089 "moria2.exit" without having to learn what moria2's IP address is.
20090 - Make the "tor --verify-config" command-line work again, so people
20091 can automatically check if their torrc will parse.
20092 - Authoritative dirservers no longer require an open connection from
20093 a server to consider him "reachable". We need this change because
20094 when we add new auth dirservers, old servers won't know not to
20096 - Let Tor build on Sun CC again.
20097 - Fix an off-by-one buffer size in dirserv.c that magically never
20098 hit our three authorities but broke sjmurdoch's own tor network.
20099 - If we as a directory mirror don't know of any v1 directory
20100 authorities, then don't try to cache any v1 directories.
20101 - Stop warning about unknown servers in our family when they are
20102 given as hex digests.
20103 - Stop complaining as quickly to the server operator that he
20104 hasn't registered his nickname/key binding.
20105 - Various cleanups so we can add new V2 Auth Dirservers.
20106 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
20107 reflect the updated flags in our v2 dir protocol.
20108 - Resume allowing non-printable characters for exit streams (both
20109 for connecting and for resolving). Now we tolerate applications
20110 that don't follow the RFCs. But continue to block malformed names
20113 o Bugfixes on 0.1.0.x:
20114 - Fix assert bug in close_logs(): when we close and delete logs,
20115 remove them all from the global "logfiles" list.
20116 - Fix minor integer overflow in calculating when we expect to use up
20117 our bandwidth allocation before hibernating.
20118 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
20119 there are multiple SSLs installed with different versions.
20120 - When we try to be a server and Address is not explicitly set and
20121 our hostname resolves to a private IP address, try to use an
20122 interface address if it has a public address. Now Windows machines
20123 that think of themselves as localhost can work by default.
20126 - Let the controller ask for GETINFO dir/server/foo so it can ask
20127 directly rather than connecting to the dir port.
20128 - Let the controller tell us about certain router descriptors
20129 that it doesn't want Tor to use in circuits. Implement
20130 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
20131 - New config option SafeSocks to reject all application connections
20132 using unsafe socks protocols. Defaults to off.
20135 Changes in version 0.1.1.15-rc - 2006-03-11
20136 o Bugfixes and cleanups:
20137 - When we're printing strings from the network, don't try to print
20138 non-printable characters. This protects us against shell escape
20139 sequence exploits, and also against attacks to fool humans into
20140 misreading their logs.
20141 - Fix a bug where Tor would fail to establish any connections if you
20142 left it off for 24 hours and then started it: we were happy with
20143 the obsolete network statuses, but they all referred to router
20144 descriptors that were too old to fetch, so we ended up with no
20145 valid router descriptors.
20146 - Fix a seg fault in the controller's "getinfo orconn-status"
20147 command while listing status on incoming handshaking connections.
20148 Introduce a status name "NEW" for these connections.
20149 - If we get a linelist or linelist_s config option from the torrc
20150 (e.g. ExitPolicy) and it has no value, warn and skip rather than
20151 silently resetting it to its default.
20152 - Don't abandon entry guards until they've been down or gone for
20154 - Cleaner and quieter log messages.
20157 - New controller signal NEWNYM that makes new application requests
20158 use clean circuits.
20159 - Add a new circuit purpose 'controller' to let the controller ask
20160 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
20161 controller command to let you specify the purpose if you're
20162 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
20163 command to let you change a circuit's purpose after it's been
20165 - Accept "private:*" in routerdesc exit policies; not generated yet
20166 because older Tors do not understand it.
20167 - Add BSD-style contributed startup script "rc.subr" from Peter
20171 Changes in version 0.1.1.14-alpha - 2006-02-20
20172 o Bugfixes on 0.1.1.x:
20173 - Don't die if we ask for a stdout or stderr log (even implicitly)
20174 and we're set to RunAsDaemon -- just warn.
20175 - We still had a few bugs in the OR connection rotation code that
20176 caused directory servers to slowly aggregate connections to other
20177 fast Tor servers. This time for sure!
20178 - Make log entries on Win32 include the name of the function again.
20179 - We were treating a pair of exit policies if they were equal even
20180 if one said accept and the other said reject -- causing us to
20181 not always publish a new descriptor since we thought nothing
20183 - Retry pending server downloads as well as pending networkstatus
20184 downloads when we unexpectedly get a socks request.
20185 - We were ignoring the IS_FAST flag in the directory status,
20186 meaning we were willing to pick trivial-bandwidth nodes for "fast"
20188 - If the controller's SAVECONF command fails (e.g. due to file
20189 permissions), let the controller know that it failed.
20192 - If we're trying to be a Tor server and running Windows 95/98/ME
20193 as a server, explain that we'll likely crash.
20194 - When we're a server, a client asks for an old-style directory,
20195 and our write bucket is empty, don't give it to him. This way
20196 small servers can continue to serve the directory *sometimes*,
20197 without getting overloaded.
20198 - Compress exit policies even more -- look for duplicate lines
20200 - Clients now honor the "guard" flag in the router status when
20201 picking entry guards, rather than looking at is_fast or is_stable.
20202 - Retain unrecognized lines in $DATADIR/state file, so that we can
20203 be forward-compatible.
20204 - Generate 18.0.0.0/8 address policy format in descs when we can;
20205 warn when the mask is not reducible to a bit-prefix.
20206 - Let the user set ControlListenAddress in the torrc. This can be
20207 dangerous, but there are some cases (like a secured LAN) where it
20209 - Split ReachableAddresses into ReachableDirAddresses and
20210 ReachableORAddresses, so we can restrict Dir conns to port 80
20211 and OR conns to port 443.
20212 - Now we can target arch and OS in rpm builds (contributed by
20213 Phobos). Also make the resulting dist-rpm filename match the
20215 - New config options to help controllers: FetchServerDescriptors
20216 and FetchHidServDescriptors for whether to fetch server
20217 info and hidserv info or let the controller do it, and
20218 PublishServerDescriptor and PublishHidServDescriptors.
20219 - Also let the controller set the __AllDirActionsPrivate config
20220 option if you want all directory fetches/publishes to happen via
20221 Tor (it assumes your controller bootstraps your circuits).
20224 Changes in version 0.1.0.17 - 2006-02-17
20225 o Crash bugfixes on 0.1.0.x:
20226 - When servers with a non-zero DirPort came out of hibernation,
20227 sometimes they would trigger an assert.
20229 o Other important bugfixes:
20230 - On platforms that don't have getrlimit (like Windows), we were
20231 artificially constraining ourselves to a max of 1024
20232 connections. Now just assume that we can handle as many as 15000
20233 connections. Hopefully this won't cause other problems.
20235 o Backported features:
20236 - When we're a server, a client asks for an old-style directory,
20237 and our write bucket is empty, don't give it to him. This way
20238 small servers can continue to serve the directory *sometimes*,
20239 without getting overloaded.
20240 - Whenever you get a 503 in response to a directory fetch, try
20241 once more. This will become important once servers start sending
20242 503's whenever they feel busy.
20243 - Fetch a new directory every 120 minutes, not every 40 minutes.
20244 Now that we have hundreds of thousands of users running the old
20245 directory algorithm, it's starting to hurt a lot.
20246 - Bump up the period for forcing a hidden service descriptor upload
20247 from 20 minutes to 1 hour.
20250 Changes in version 0.1.1.13-alpha - 2006-02-09
20251 o Crashes in 0.1.1.x:
20252 - When you tried to setconf ORPort via the controller, Tor would
20253 crash. So people using TorCP to become a server were sad.
20254 - Solve (I hope) the stack-smashing bug that we were seeing on fast
20255 servers. The problem appears to be something do with OpenSSL's
20256 random number generation, or how we call it, or something. Let me
20257 know if the crashes continue.
20258 - Turn crypto hardware acceleration off by default, until we find
20259 somebody smart who can test it for us. (It appears to produce
20260 seg faults in at least some cases.)
20261 - Fix a rare assert error when we've tried all intro points for
20262 a hidden service and we try fetching the service descriptor again:
20263 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
20266 - Fix a major load balance bug: we were round-robining in 16 KB
20267 chunks, and servers with bandwidthrate of 20 KB, while downloading
20268 a 600 KB directory, would starve their other connections. Now we
20269 try to be a bit more fair.
20270 - Dir authorities and mirrors were never expiring the newest
20271 descriptor for each server, causing memory and directory bloat.
20272 - Fix memory-bloating and connection-bloating bug on servers: We
20273 were never closing any connection that had ever had a circuit on
20274 it, because we were checking conn->n_circuits == 0, yet we had a
20275 bug that let it go negative.
20276 - Make Tor work using squid as your http proxy again -- squid
20277 returns an error if you ask for a URL that's too long, and it uses
20278 a really generic error message. Plus, many people are behind a
20279 transparent squid so they don't even realize it.
20280 - On platforms that don't have getrlimit (like Windows), we were
20281 artificially constraining ourselves to a max of 1024
20282 connections. Now just assume that we can handle as many as 15000
20283 connections. Hopefully this won't cause other problems.
20284 - Add a new config option ExitPolicyRejectPrivate which defaults to
20285 1. This means all exit policies will begin with rejecting private
20286 addresses, unless the server operator explicitly turns it off.
20289 - Clients no longer download descriptors for non-running
20291 - Before we add new directory authorities, we should make it
20292 clear that only v1 authorities should receive/publish hidden
20293 service descriptors.
20296 - As soon as we've fetched some more directory info, immediately
20297 try to download more server descriptors. This way we don't have
20298 a 10 second pause during initial bootstrapping.
20299 - Remove even more loud log messages that the server operator can't
20301 - When we're running an obsolete or un-recommended version, make
20302 the log message more clear about what the problem is and what
20303 versions *are* still recommended.
20304 - Provide a more useful warn message when our onion queue gets full:
20305 the CPU is too slow or the exit policy is too liberal.
20306 - Don't warn when we receive a 503 from a dirserver/cache -- this
20307 will pave the way for them being able to refuse if they're busy.
20308 - When we fail to bind a listener, try to provide a more useful
20309 log message: e.g., "Is Tor already running?"
20310 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
20311 Goldberg can prove things about our handshake protocol more
20313 - MaxConn has been obsolete for a while now. Document the ConnLimit
20314 config option, which is a *minimum* number of file descriptors
20315 that must be available else Tor refuses to start.
20316 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
20317 if you log to syslog and want something other than LOG_DAEMON.
20318 - Make dirservers generate a separate "guard" flag to mean,
20319 "would make a good entry guard". Make clients parse it and vote
20320 on it. Not used by clients yet.
20321 - Implement --with-libevent-dir option to ./configure. Also, improve
20322 search techniques to find libevent, and use those for openssl too.
20323 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
20324 - Only start testing reachability once we've established a
20325 circuit. This will make startup on dirservers less noisy.
20326 - Don't try to upload hidden service descriptors until we have
20327 established a circuit.
20328 - Fix the controller's "attachstream 0" command to treat conn like
20329 it just connected, doing address remapping, handling .exit and
20330 .onion idioms, and so on. Now we're more uniform in making sure
20331 that the controller hears about new and closing connections.
20334 Changes in version 0.1.1.12-alpha - 2006-01-11
20335 o Bugfixes on 0.1.1.x:
20336 - The fix to close duplicate server connections was closing all
20337 Tor client connections if they didn't establish a circuit
20338 quickly enough. Oops.
20339 - Fix minor memory issue (double-free) that happened on exit.
20341 o Bugfixes on 0.1.0.x:
20342 - Tor didn't warn when it failed to open a log file.
20345 Changes in version 0.1.1.11-alpha - 2006-01-10
20346 o Crashes in 0.1.1.x:
20347 - Include all the assert/crash fixes from 0.1.0.16.
20348 - If you start Tor and then quit very quickly, there were some
20349 races that tried to free things that weren't allocated yet.
20350 - Fix a rare memory stomp if you're running hidden services.
20351 - Fix segfault when specifying DirServer in config without nickname.
20352 - Fix a seg fault when you finish connecting to a server but at
20353 that moment you dump his server descriptor.
20354 - Extendcircuit and Attachstream controller commands would
20355 assert/crash if you don't give them enough arguments.
20356 - Fix an assert error when we're out of space in the connection_list
20357 and we try to post a hidden service descriptor (reported by weasel).
20358 - If you specify a relative torrc path and you set RunAsDaemon in
20359 your torrc, then it chdir()'s to the new directory. If you HUP,
20360 it tries to load the new torrc location, fails, and exits.
20361 The fix: no longer allow a relative path to torrc using -f.
20364 - Implement "entry guards": automatically choose a handful of entry
20365 nodes and stick with them for all circuits. Only pick new guards
20366 when the ones you have are unsuitable, and if the old guards
20367 become suitable again, switch back. This will increase security
20368 dramatically against certain end-point attacks. The EntryNodes
20369 config option now provides some hints about which entry guards you
20370 want to use most; and StrictEntryNodes means to only use those.
20371 - New directory logic: download by descriptor digest, not by
20372 fingerprint. Caches try to download all listed digests from
20373 authorities; clients try to download "best" digests from caches.
20374 This avoids partitioning and isolating attacks better.
20375 - Make the "stable" router flag in network-status be the median of
20376 the uptimes of running valid servers, and make clients pay
20377 attention to the network-status flags. Thus the cutoff adapts
20378 to the stability of the network as a whole, making IRC, IM, etc
20379 connections more reliable.
20382 - Tor servers with dynamic IP addresses were needing to wait 18
20383 hours before they could start doing reachability testing using
20384 the new IP address and ports. This is because they were using
20385 the internal descriptor to learn what to test, yet they were only
20386 rebuilding the descriptor once they decided they were reachable.
20387 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
20388 to download certain server descriptors, throw them away, and then
20389 fetch them again after 30 minutes. Now mirrors throw away these
20390 server descriptors so clients can't get them.
20391 - We were leaving duplicate connections to other ORs open for a week,
20392 rather than closing them once we detect a duplicate. This only
20393 really affected authdirservers, but it affected them a lot.
20394 - Spread the authdirservers' reachability testing over the entire
20395 testing interval, so we don't try to do 500 TLS's at once every
20399 - If the network is down, and we try to connect to a conn because
20400 we have a circuit in mind, and we timeout (30 seconds) because the
20401 network never answers, we were expiring the circuit, but we weren't
20402 obsoleting the connection or telling the entry_guards functions.
20403 - Some Tor servers process billions of cells per day. These statistics
20404 need to be uint64_t's.
20405 - Check for integer overflows in more places, when adding elements
20406 to smartlists. This could possibly prevent a buffer overflow
20407 on malicious huge inputs. I don't see any, but I haven't looked
20409 - ReachableAddresses kept growing new "reject *:*" lines on every
20411 - When you "setconf log" via the controller, it should remove all
20412 logs. We were automatically adding back in a "log notice stdout".
20413 - Newly bootstrapped Tor networks couldn't establish hidden service
20414 circuits until they had nodes with high uptime. Be more tolerant.
20415 - We were marking servers down when they could not answer every piece
20416 of the directory request we sent them. This was far too harsh.
20417 - Fix the torify (tsocks) config file to not use Tor for localhost
20419 - Directory authorities now go to the proper authority when asking for
20420 a networkstatus, even when they want a compressed one.
20421 - Fix a harmless bug that was causing Tor servers to log
20422 "Got an end because of misc error, but we're not an AP. Closing."
20423 - Authorities were treating their own descriptor changes as cosmetic,
20424 meaning the descriptor available in the network-status and the
20425 descriptor that clients downloaded were different.
20426 - The OS X installer was adding a symlink for tor_resolve but
20427 the binary was called tor-resolve (reported by Thomas Hardly).
20428 - Workaround a problem with some http proxies where they refuse GET
20429 requests that specify "Content-Length: 0" (reported by Adrian).
20430 - Fix wrong log message when you add a "HiddenServiceNodes" config
20431 line without any HiddenServiceDir line (reported by Chris Thomas).
20434 - Write the TorVersion into the state file so we have a prayer of
20435 keeping forward and backward compatibility.
20436 - Revive the FascistFirewall config option rather than eliminating it:
20437 now it's a synonym for ReachableAddresses *:80,*:443.
20438 - Clients choose directory servers from the network status lists,
20439 not from their internal list of router descriptors. Now they can
20440 go to caches directly rather than needing to go to authorities
20442 - Directory authorities ignore router descriptors that have only
20443 cosmetic differences: do this for 0.1.0.x servers now too.
20444 - Add a new flag to network-status indicating whether the server
20445 can answer v2 directory requests too.
20446 - Authdirs now stop whining so loudly about bad descriptors that
20447 they fetch from other dirservers. So when there's a log complaint,
20448 it's for sure from a freshly uploaded descriptor.
20449 - Reduce memory requirements in our structs by changing the order
20451 - There used to be two ways to specify your listening ports in a
20452 server descriptor: on the "router" line and with a separate "ports"
20453 line. Remove support for the "ports" line.
20454 - New config option "AuthDirRejectUnlisted" for auth dirservers as
20455 a panic button: if we get flooded with unusable servers we can
20456 revert to only listing servers in the approved-routers file.
20457 - Auth dir servers can now mark a fingerprint as "!reject" or
20458 "!invalid" in the approved-routers file (as its nickname), to
20459 refuse descriptors outright or include them but marked as invalid.
20460 - Servers store bandwidth history across restarts/crashes.
20461 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
20462 get a better idea of why their circuits failed. Not used yet.
20463 - Directory mirrors now cache up to 16 unrecognized network-status
20464 docs. Now we can add new authdirservers and they'll be cached too.
20465 - When picking a random directory, prefer non-authorities if any
20467 - New controller option "getinfo desc/all-recent" to fetch the
20468 latest server descriptor for every router that Tor knows about.
20471 Changes in version 0.1.0.16 - 2006-01-02
20472 o Crash bugfixes on 0.1.0.x:
20473 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
20474 corrupting the heap, losing FDs, or crashing when we need to resize
20475 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
20476 - It turns out sparc64 platforms crash on unaligned memory access
20477 too -- so detect and avoid this.
20478 - Handle truncated compressed data correctly (by detecting it and
20480 - Fix possible-but-unlikely free(NULL) in control.c.
20481 - When we were closing connections, there was a rare case that
20482 stomped on memory, triggering seg faults and asserts.
20483 - Avoid potential infinite recursion when building a descriptor. (We
20484 don't know that it ever happened, but better to fix it anyway.)
20485 - We were neglecting to unlink marked circuits from soon-to-close OR
20486 connections, which caused some rare scribbling on freed memory.
20487 - Fix a memory stomping race bug when closing the joining point of two
20488 rendezvous circuits.
20489 - Fix an assert in time parsing found by Steven Murdoch.
20491 o Other bugfixes on 0.1.0.x:
20492 - When we're doing reachability testing, provide more useful log
20493 messages so the operator knows what to expect.
20494 - Do not check whether DirPort is reachable when we are suppressing
20495 advertising it because of hibernation.
20496 - When building with -static or on Solaris, we sometimes needed -ldl.
20497 - When we're deciding whether a stream has enough circuits around
20498 that can handle it, count the freshly dirty ones and not the ones
20499 that are so dirty they won't be able to handle it.
20500 - When we're expiring old circuits, we had a logic error that caused
20501 us to close new rendezvous circuits rather than old ones.
20502 - Give a more helpful log message when you try to change ORPort via
20503 the controller: you should upgrade Tor if you want that to work.
20504 - We were failing to parse Tor versions that start with "Tor ".
20505 - Tolerate faulty streams better: when a stream fails for reason
20506 exitpolicy, stop assuming that the router is lying about his exit
20507 policy. When a stream fails for reason misc, allow it to retry just
20508 as if it was resolvefailed. When a stream has failed three times,
20509 reset its failure count so we can try again and get all three tries.
20512 Changes in version 0.1.1.10-alpha - 2005-12-11
20513 o Correctness bugfixes on 0.1.0.x:
20514 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
20515 corrupting the heap, losing FDs, or crashing when we need to resize
20516 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
20517 - Stop doing the complex voodoo overkill checking for insecure
20518 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
20519 - When we were closing connections, there was a rare case that
20520 stomped on memory, triggering seg faults and asserts.
20521 - We were neglecting to unlink marked circuits from soon-to-close OR
20522 connections, which caused some rare scribbling on freed memory.
20523 - When we're deciding whether a stream has enough circuits around
20524 that can handle it, count the freshly dirty ones and not the ones
20525 that are so dirty they won't be able to handle it.
20526 - Recover better from TCP connections to Tor servers that are
20527 broken but don't tell you (it happens!); and rotate TLS
20528 connections once a week.
20529 - When we're expiring old circuits, we had a logic error that caused
20530 us to close new rendezvous circuits rather than old ones.
20531 - Fix a scary-looking but apparently harmless bug where circuits
20532 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
20533 servers, and never switch to state CIRCUIT_STATE_OPEN.
20534 - When building with -static or on Solaris, we sometimes needed to
20536 - Give a useful message when people run Tor as the wrong user,
20537 rather than telling them to start chowning random directories.
20538 - We were failing to inform the controller about new .onion streams.
20540 o Security bugfixes on 0.1.0.x:
20541 - Refuse server descriptors if the fingerprint line doesn't match
20542 the included identity key. Tor doesn't care, but other apps (and
20543 humans) might actually be trusting the fingerprint line.
20544 - We used to kill the circuit when we receive a relay command we
20545 don't recognize. Now we just drop it.
20546 - Start obeying our firewall options more rigorously:
20547 . If we can't get to a dirserver directly, try going via Tor.
20548 . Don't ever try to connect (as a client) to a place our
20549 firewall options forbid.
20550 . If we specify a proxy and also firewall options, obey the
20551 firewall options even when we're using the proxy: some proxies
20552 can only proxy to certain destinations.
20553 - Fix a bug found by Lasse Overlier: when we were making internal
20554 circuits (intended to be cannibalized later for rendezvous and
20555 introduction circuits), we were picking them so that they had
20556 useful exit nodes. There was no need for this, and it actually
20557 aids some statistical attacks.
20558 - Start treating internal circuits and exit circuits separately.
20559 It's important to keep them separate because internal circuits
20560 have their last hops picked like middle hops, rather than like
20561 exit hops. So exiting on them will break the user's expectations.
20563 o Bugfixes on 0.1.1.x:
20564 - Take out the mis-feature where we tried to detect IP address
20565 flapping for people with DynDNS, and chose not to upload a new
20566 server descriptor sometimes.
20567 - Try to be compatible with OpenSSL 0.9.6 again.
20568 - Log fix: when the controller is logging about .onion addresses,
20569 sometimes it didn't include the ".onion" part of the address.
20570 - Don't try to modify options->DirServers internally -- if the
20571 user didn't specify any, just add the default ones directly to
20572 the trusted dirserver list. This fixes a bug where people running
20573 controllers would use SETCONF on some totally unrelated config
20574 option, and Tor would start yelling at them about changing their
20576 - Let the controller's redirectstream command specify a port, in
20577 case the controller wants to change that too.
20578 - When we requested a pile of server descriptors, we sometimes
20579 accidentally launched a duplicate request for the first one.
20580 - Bugfix for trackhostexits: write down the fingerprint of the
20581 chosen exit, not its nickname, because the chosen exit might not
20583 - When parsing foo.exit, if foo is unknown, and we are leaving
20584 circuits unattached, set the chosen_exit field and leave the
20585 address empty. This matters because controllers got confused
20587 - Directory authorities no longer try to download server
20588 descriptors that they know they will reject.
20590 o Features and updates:
20591 - Replace balanced trees with hash tables: this should make stuff
20592 significantly faster.
20593 - Resume using the AES counter-mode implementation that we ship,
20594 rather than OpenSSL's. Ours is significantly faster.
20595 - Many other CPU and memory improvements.
20596 - Add a new config option FastFirstHopPK (on by default) so clients
20597 do a trivial crypto handshake for their first hop, since TLS has
20598 already taken care of confidentiality and authentication.
20599 - Add a new config option TestSocks so people can see if their
20600 applications are using socks4, socks4a, socks5-with-ip, or
20601 socks5-with-hostname. This way they don't have to keep mucking
20602 with tcpdump and wondering if something got cached somewhere.
20603 - Warn when listening on a public address for socks. I suspect a
20604 lot of people are setting themselves up as open socks proxies,
20605 and they have no idea that jerks on the Internet are using them,
20606 since they simply proxy the traffic into the Tor network.
20607 - Add "private:*" as an alias in configuration for policies. Now
20608 you can simplify your exit policy rather than needing to list
20609 every single internal or nonroutable network space.
20610 - Add a new controller event type that allows controllers to get
20611 all server descriptors that were uploaded to a router in its role
20612 as authoritative dirserver.
20613 - Start shipping socks-extensions.txt, tor-doc-unix.html,
20614 tor-doc-server.html, and stylesheet.css in the tarball.
20615 - Stop shipping tor-doc.html in the tarball.
20618 Changes in version 0.1.1.9-alpha - 2005-11-15
20619 o Usability improvements:
20620 - Start calling it FooListenAddress rather than FooBindAddress,
20621 since few of our users know what it means to bind an address
20623 - Reduce clutter in server logs. We're going to try to make
20624 them actually usable now. New config option ProtocolWarnings that
20625 lets you hear about how _other Tors_ are breaking the protocol. Off
20627 - Divide log messages into logging domains. Once we put some sort
20628 of interface on this, it will let people looking at more verbose
20629 log levels specify the topics they want to hear more about.
20630 - Make directory servers return better http 404 error messages
20631 instead of a generic "Servers unavailable".
20632 - Check for even more Windows version flags when writing the platform
20633 string in server descriptors, and note any we don't recognize.
20634 - Clean up more of the OpenSSL memory when exiting, so we can detect
20635 memory leaks better.
20636 - Make directory authorities be non-versioning, non-naming by
20637 default. Now we can add new directory servers without requiring
20638 their operators to pay close attention.
20639 - When logging via syslog, include the pid whenever we provide
20640 a log entry. Suggested by Todd Fries.
20642 o Performance improvements:
20643 - Directory servers now silently throw away new descriptors that
20644 haven't changed much if the timestamps are similar. We do this to
20645 tolerate older Tor servers that upload a new descriptor every 15
20646 minutes. (It seemed like a good idea at the time.)
20647 - Inline bottleneck smartlist functions; use fast versions by default.
20648 - Add a "Map from digest to void*" abstraction digestmap_t so we
20649 can do less hex encoding/decoding. Use it in router_get_by_digest()
20650 to resolve a performance bottleneck.
20651 - Allow tor_gzip_uncompress to extract as much as possible from
20652 truncated compressed data. Try to extract as many
20653 descriptors as possible from truncated http responses (when
20654 DIR_PURPOSE_FETCH_ROUTERDESC).
20655 - Make circ->onionskin a pointer, not a static array. moria2 was using
20656 125000 circuit_t's after it had been up for a few weeks, which
20657 translates to 20+ megs of wasted space.
20658 - The private half of our EDH handshake keys are now chosen out
20659 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
20661 o Security improvements:
20662 - Start making directory caches retain old routerinfos, so soon
20663 clients can start asking by digest of descriptor rather than by
20664 fingerprint of server.
20665 - Add half our entropy from RAND_poll in OpenSSL. This knows how
20666 to use egd (if present), openbsd weirdness (if present), vms/os2
20667 weirdness (if we ever port there), and more in the future.
20669 o Bugfixes on 0.1.0.x:
20670 - Do round-robin writes of at most 16 kB per write. This might be
20671 more fair on loaded Tor servers, and it might resolve our Windows
20672 crash bug. It might also slow things down.
20673 - Our TLS handshakes were generating a single public/private
20674 keypair for the TLS context, rather than making a new one for
20675 each new connections. Oops. (But we were still rotating them
20676 periodically, so it's not so bad.)
20677 - When we were cannibalizing a circuit with a particular exit
20678 node in mind, we weren't checking to see if that exit node was
20679 already present earlier in the circuit. Oops.
20680 - When a Tor server's IP changes (e.g. from a dyndns address),
20681 upload a new descriptor so clients will learn too.
20682 - Really busy servers were keeping enough circuits open on stable
20683 connections that they were wrapping around the circuit_id
20684 space. (It's only two bytes.) This exposed a bug where we would
20685 feel free to reuse a circuit_id even if it still exists but has
20686 been marked for close. Try to fix this bug. Some bug remains.
20687 - If we would close a stream early (e.g. it asks for a .exit that
20688 we know would refuse it) but the LeaveStreamsUnattached config
20689 option is set by the controller, then don't close it.
20691 o Bugfixes on 0.1.1.8-alpha:
20692 - Fix a big pile of memory leaks, some of them serious.
20693 - Do not try to download a routerdesc if we would immediately reject
20695 - Resume inserting a newline between all router descriptors when
20696 generating (old style) signed directories, since our spec says
20698 - When providing content-type application/octet-stream for
20699 server descriptors using .z, we were leaving out the
20700 content-encoding header. Oops. (Everything tolerated this just
20701 fine, but that doesn't mean we need to be part of the problem.)
20702 - Fix a potential seg fault in getconf and getinfo using version 1
20703 of the controller protocol.
20704 - Avoid crash: do not check whether DirPort is reachable when we
20705 are suppressing it because of hibernation.
20706 - Make --hash-password not crash on exit.
20709 Changes in version 0.1.1.8-alpha - 2005-10-07
20710 o New features (major):
20711 - Clients don't download or use the directory anymore. Now they
20712 download and use network-statuses from the trusted dirservers,
20713 and fetch individual server descriptors as needed from mirrors.
20714 See dir-spec.txt for all the gory details.
20715 - Be more conservative about whether to advertise our DirPort.
20716 The main change is to not advertise if we're running at capacity
20717 and either a) we could hibernate or b) our capacity is low and
20718 we're using a default DirPort.
20719 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
20721 o New features (minor):
20722 - Try to be smart about when to retry network-status and
20723 server-descriptor fetches. Still needs some tuning.
20724 - Stop parsing, storing, or using running-routers output (but
20725 mirrors still cache and serve it).
20726 - Consider a threshold of versioning dirservers (dirservers who have
20727 an opinion about which Tor versions are still recommended) before
20728 deciding whether to warn the user that he's obsolete.
20729 - Dirservers can now reject/invalidate by key and IP, with the
20730 config options "AuthDirInvalid" and "AuthDirReject". This is
20731 useful since currently we automatically list servers as running
20732 and usable even if we know they're jerks.
20733 - Provide dire warnings to any users who set DirServer; move it out
20734 of torrc.sample and into torrc.complete.
20735 - Add MyFamily to torrc.sample in the server section.
20736 - Add nicknames to the DirServer line, so we can refer to them
20737 without requiring all our users to memorize their IP addresses.
20738 - When we get an EOF or a timeout on a directory connection, note
20739 how many bytes of serverdesc we are dropping. This will help
20740 us determine whether it is smart to parse incomplete serverdesc
20742 - Add a new function to "change pseudonyms" -- that is, to stop
20743 using any currently-dirty circuits for new streams, so we don't
20744 link new actions to old actions. Currently it's only called on
20745 HUP (or SIGNAL RELOAD).
20746 - On sighup, if UseHelperNodes changed to 1, use new circuits.
20747 - Start using RAND_bytes rather than RAND_pseudo_bytes from
20748 OpenSSL. Also, reseed our entropy every hour, not just at
20749 startup. And entropy in 512-bit chunks, not 160-bit chunks.
20751 o Fixes on 0.1.1.7-alpha:
20752 - Nobody ever implemented EVENT_ADDRMAP for control protocol
20753 version 0, so don't let version 0 controllers ask for it.
20754 - If you requested something with too many newlines via the
20755 v1 controller protocol, you could crash tor.
20756 - Fix a number of memory leaks, including some pretty serious ones.
20757 - Re-enable DirPort testing again, so Tor servers will be willing
20758 to advertise their DirPort if it's reachable.
20759 - On TLS handshake, only check the other router's nickname against
20760 its expected nickname if is_named is set.
20762 o Fixes forward-ported from 0.1.0.15:
20763 - Don't crash when we don't have any spare file descriptors and we
20764 try to spawn a dns or cpu worker.
20765 - Make the numbers in read-history and write-history into uint64s,
20766 so they don't overflow and publish negatives in the descriptor.
20768 o Fixes on 0.1.0.x:
20769 - For the OS X package's modified privoxy config file, comment
20770 out the "logfile" line so we don't log everything passed
20772 - We were whining about using socks4 or socks5-with-local-lookup
20773 even when it's an IP in the "virtual" range we designed exactly
20775 - We were leaking some memory every time the client changes IPs.
20776 - Never call free() on tor_malloc()d memory. This will help us
20777 use dmalloc to detect memory leaks.
20778 - Check for named servers when looking them up by nickname;
20779 warn when we'recalling a non-named server by its nickname;
20780 don't warn twice about the same name.
20781 - Try to list MyFamily elements by key, not by nickname, and warn
20782 if we've not heard of the server.
20783 - Make windows platform detection (uname equivalent) smarter.
20784 - It turns out sparc64 doesn't like unaligned access either.
20787 Changes in version 0.1.0.15 - 2005-09-23
20788 o Bugfixes on 0.1.0.x:
20789 - Reject ports 465 and 587 (spam targets) in default exit policy.
20790 - Don't crash when we don't have any spare file descriptors and we
20791 try to spawn a dns or cpu worker.
20792 - Get rid of IgnoreVersion undocumented config option, and make us
20793 only warn, never exit, when we're running an obsolete version.
20794 - Don't try to print a null string when your server finds itself to
20795 be unreachable and the Address config option is empty.
20796 - Make the numbers in read-history and write-history into uint64s,
20797 so they don't overflow and publish negatives in the descriptor.
20798 - Fix a minor memory leak in smartlist_string_remove().
20799 - We were only allowing ourselves to upload a server descriptor at
20800 most every 20 minutes, even if it changed earlier than that.
20801 - Clean up log entries that pointed to old URLs.
20804 Changes in version 0.1.1.7-alpha - 2005-09-14
20805 o Fixes on 0.1.1.6-alpha:
20806 - Exit servers were crashing when people asked them to make a
20807 connection to an address not in their exit policy.
20808 - Looking up a non-existent stream for a v1 control connection would
20810 - Fix a seg fault if we ask a dirserver for a descriptor by
20811 fingerprint but he doesn't know about him.
20812 - SETCONF was appending items to linelists, not clearing them.
20813 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
20814 out and refuse the setconf if it would fail.
20815 - Downgrade the dirserver log messages when whining about
20819 - Add Peter Palfrader's check-tor script to tor/contrib/
20820 It lets you easily check whether a given server (referenced by
20821 nickname) is reachable by you.
20822 - Numerous changes to move towards client-side v2 directories. Not
20825 o Fixes on 0.1.0.x:
20826 - If the user gave tor an odd number of command-line arguments,
20827 we were silently ignoring the last one. Now we complain and fail.
20828 [This wins the oldest-bug prize -- this bug has been present since
20829 November 2002, as released in Tor 0.0.0.]
20830 - Do not use unaligned memory access on alpha, mips, or mipsel.
20831 It *works*, but is very slow, so we treat them as if it doesn't.
20832 - Retry directory requests if we fail to get an answer we like
20833 from a given dirserver (we were retrying before, but only if
20834 we fail to connect).
20835 - When writing the RecommendedVersions line, sort them first.
20836 - When the client asked for a rendezvous port that the hidden
20837 service didn't want to provide, we were sending an IP address
20838 back along with the end cell. Fortunately, it was zero. But stop
20840 - Correct "your server is reachable" log entries to indicate that
20841 it was self-testing that told us so.
20844 Changes in version 0.1.1.6-alpha - 2005-09-09
20845 o Fixes on 0.1.1.5-alpha:
20846 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
20847 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
20848 - Fix bug with tor_memmem finding a match at the end of the string.
20849 - Make unit tests run without segfaulting.
20850 - Resolve some solaris x86 compile warnings.
20851 - Handle duplicate lines in approved-routers files without warning.
20852 - Fix bug where as soon as a server refused any requests due to his
20853 exit policy (e.g. when we ask for localhost and he tells us that's
20854 127.0.0.1 and he won't do it), we decided he wasn't obeying his
20855 exit policy using him for any exits.
20856 - Only do openssl hardware accelerator stuff if openssl version is
20859 o New controller features/fixes:
20860 - Add a "RESETCONF" command so you can set config options like
20861 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
20862 a config option in the torrc with no value, then it clears it
20863 entirely (rather than setting it to its default).
20864 - Add a "GETINFO config-file" to tell us where torrc is.
20865 - Avoid sending blank lines when GETINFO replies should be empty.
20866 - Add a QUIT command for the controller (for using it manually).
20867 - Fix a bug in SAVECONF that was adding default dirservers and
20868 other redundant entries to the torrc file.
20870 o Start on the new directory design:
20871 - Generate, publish, cache, serve new network-status format.
20872 - Publish individual descriptors (by fingerprint, by "all", and by
20874 - Publish client and server recommended versions separately.
20875 - Allow tor_gzip_uncompress() to handle multiple concatenated
20876 compressed strings. Serve compressed groups of router
20877 descriptors. The compression logic here could be more
20879 - Distinguish v1 authorities (all currently trusted directories)
20880 from v2 authorities (all trusted directories).
20881 - Change DirServers config line to note which dirs are v1 authorities.
20882 - Add configuration option "V1AuthoritativeDirectory 1" which
20883 moria1, moria2, and tor26 should set.
20884 - Remove option when getting directory cache to see whether they
20885 support running-routers; they all do now. Replace it with one
20886 to see whether caches support v2 stuff.
20889 - Dirservers now do their own external reachability testing of each
20890 Tor server, and only list them as running if they've been found to
20891 be reachable. We also send back warnings to the server's logs if
20892 it uploads a descriptor that we already believe is unreachable.
20893 - Implement exit enclaves: if we know an IP address for the
20894 destination, and there's a running Tor server at that address
20895 which allows exit to the destination, then extend the circuit to
20896 that exit first. This provides end-to-end encryption and end-to-end
20897 authentication. Also, if the user wants a .exit address or enclave,
20898 use 4 hops rather than 3, and cannibalize a general circ for it
20900 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
20901 controller. Also, rotate dns and cpu workers if the controller
20902 changes options that will affect them; and initialize the dns
20903 worker cache tree whether or not we start out as a server.
20904 - Only upload a new server descriptor when options change, 18
20905 hours have passed, uptime is reset, or bandwidth changes a lot.
20906 - Check [X-]Forwarded-For headers in HTTP requests when generating
20907 log messages. This lets people run dirservers (and caches) behind
20908 Apache but still know which IP addresses are causing warnings.
20910 o Config option changes:
20911 - Replace (Fascist)Firewall* config options with a new
20912 ReachableAddresses option that understands address policies.
20913 For example, "ReachableAddresses *:80,*:443"
20914 - Get rid of IgnoreVersion undocumented config option, and make us
20915 only warn, never exit, when we're running an obsolete version.
20916 - Make MonthlyAccountingStart config option truly obsolete now.
20918 o Fixes on 0.1.0.x:
20919 - Reject ports 465 and 587 in the default exit policy, since
20920 people have started using them for spam too.
20921 - It turns out we couldn't bootstrap a network since we added
20922 reachability detection in 0.1.0.1-rc. Good thing the Tor network
20923 has never gone down. Add an AssumeReachable config option to let
20924 servers and dirservers bootstrap. When we're trying to build a
20925 high-uptime or high-bandwidth circuit but there aren't enough
20926 suitable servers, try being less picky rather than simply failing.
20927 - Our logic to decide if the OR we connected to was the right guy
20928 was brittle and maybe open to a mitm for unverified routers.
20929 - We weren't cannibalizing circuits correctly for
20930 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
20931 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
20932 build those from scratch. This should make hidden services faster.
20933 - Predict required circuits better, with an eye toward making hidden
20934 services faster on the service end.
20935 - Retry streams if the exit node sends back a 'misc' failure. This
20936 should result in fewer random failures. Also, after failing
20937 from resolve failed or misc, reset the num failures, so we give
20938 it a fair shake next time we try.
20939 - Clean up the rendezvous warn log msgs, and downgrade some to info.
20940 - Reduce severity on logs about dns worker spawning and culling.
20941 - When we're shutting down and we do something like try to post a
20942 server descriptor or rendezvous descriptor, don't complain that
20943 we seem to be unreachable. Of course we are, we're shutting down.
20944 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
20945 We don't use them yet, but maybe one day our DNS resolver will be
20946 able to discover them.
20947 - Make ContactInfo mandatory for authoritative directory servers.
20948 - Require server descriptors to list IPv4 addresses -- hostnames
20949 are no longer allowed. This also fixes some potential security
20950 problems with people providing hostnames as their address and then
20951 preferentially resolving them to partition users.
20952 - Change log line for unreachability to explicitly suggest /etc/hosts
20953 as the culprit. Also make it clearer what IP address and ports we're
20954 testing for reachability.
20955 - Put quotes around user-supplied strings when logging so users are
20956 more likely to realize if they add bad characters (like quotes)
20958 - Let auth dir servers start without specifying an Address config
20960 - Make unit tests (and other invocations that aren't the real Tor)
20961 run without launching listeners, creating subdirectories, and so on.
20964 Changes in version 0.1.1.5-alpha - 2005-08-08
20965 o Bugfixes included in 0.1.0.14.
20967 o Bugfixes on 0.1.0.x:
20968 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
20969 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
20970 it would silently using ignore the 6668.
20973 Changes in version 0.1.0.14 - 2005-08-08
20974 o Bugfixes on 0.1.0.x:
20975 - Fix the other half of the bug with crypto handshakes
20977 - Fix an assert trigger if you send a 'signal term' via the
20978 controller when it's listening for 'event info' messages.
20981 Changes in version 0.1.1.4-alpha - 2005-08-04
20982 o Bugfixes included in 0.1.0.13.
20985 - Improve tor_gettimeofday() granularity on windows.
20986 - Make clients regenerate their keys when their IP address changes.
20987 - Implement some more GETINFO goodness: expose helper nodes, config
20988 options, getinfo keys.
20991 Changes in version 0.1.0.13 - 2005-08-04
20992 o Bugfixes on 0.1.0.x:
20993 - Fix a critical bug in the security of our crypto handshakes.
20994 - Fix a size_t underflow in smartlist_join_strings2() that made
20995 it do bad things when you hand it an empty smartlist.
20996 - Fix Windows installer to ship Tor license (thanks to Aphex for
20997 pointing out this oversight) and put a link to the doc directory
20999 - Explicitly set no-unaligned-access for sparc: it turns out the
21000 new gcc's let you compile broken code, but that doesn't make it
21004 Changes in version 0.1.1.3-alpha - 2005-07-23
21005 o Bugfixes on 0.1.1.2-alpha:
21006 - Fix a bug in handling the controller's "post descriptor"
21008 - Fix several bugs in handling the controller's "extend circuit"
21010 - Fix a bug in handling the controller's "stream status" event.
21011 - Fix an assert failure if we have a controller listening for
21012 circuit events and we go offline.
21013 - Re-allow hidden service descriptors to publish 0 intro points.
21014 - Fix a crash when generating your hidden service descriptor if
21015 you don't have enough intro points already.
21017 o New features on 0.1.1.2-alpha:
21018 - New controller function "getinfo accounting", to ask how
21019 many bytes we've used in this time period.
21020 - Experimental support for helper nodes: a lot of the risk from
21021 a small static adversary comes because users pick new random
21022 nodes every time they rebuild a circuit. Now users will try to
21023 stick to the same small set of entry nodes if they can. Not
21024 enabled by default yet.
21026 o Bugfixes on 0.1.0.12:
21027 - If you're an auth dir server, always publish your dirport,
21028 even if you haven't yet found yourself to be reachable.
21029 - Fix a size_t underflow in smartlist_join_strings2() that made
21030 it do bad things when you hand it an empty smartlist.
21033 Changes in version 0.1.0.12 - 2005-07-18
21034 o New directory servers:
21035 - tor26 has changed IP address.
21037 o Bugfixes on 0.1.0.x:
21038 - Fix a possible double-free in tor_gzip_uncompress().
21039 - When --disable-threads is set, do not search for or link against
21040 pthreads libraries.
21041 - Don't trigger an assert if an authoritative directory server
21042 claims its dirport is 0.
21043 - Fix bug with removing Tor as an NT service: some people were
21044 getting "The service did not return an error." Thanks to Matt
21048 Changes in version 0.1.1.2-alpha - 2005-07-15
21049 o New directory servers:
21050 - tor26 has changed IP address.
21052 o Bugfixes on 0.1.0.x, crashes/leaks:
21053 - Port the servers-not-obeying-their-exit-policies fix from
21055 - Fix an fd leak in start_daemon().
21056 - On Windows, you can't always reopen a port right after you've
21057 closed it. So change retry_listeners() to only close and re-open
21058 ports that have changed.
21059 - Fix a possible double-free in tor_gzip_uncompress().
21061 o Bugfixes on 0.1.0.x, usability:
21062 - When tor_socketpair() fails in Windows, give a reasonable
21063 Windows-style errno back.
21064 - Let people type "tor --install" as well as "tor -install" when
21066 want to make it an NT service.
21067 - NT service patch from Matt Edman to improve error messages.
21068 - When the controller asks for a config option with an abbreviated
21069 name, give the full name in our response.
21070 - Correct the man page entry on TrackHostExitsExpire.
21071 - Looks like we were never delivering deflated (i.e. compressed)
21072 running-routers lists, even when asked. Oops.
21073 - When --disable-threads is set, do not search for or link against
21074 pthreads libraries.
21076 o Bugfixes on 0.1.1.x:
21077 - Fix a seg fault with autodetecting which controller version is
21081 - New hidden service descriptor format: put a version in it, and
21082 let people specify introduction/rendezvous points that aren't
21083 in "the directory" (which is subjective anyway).
21084 - Allow the DEBUG controller event to work again. Mark certain log
21085 entries as "don't tell this to controllers", so we avoid cycles.
21088 Changes in version 0.1.0.11 - 2005-06-30
21089 o Bugfixes on 0.1.0.x:
21090 - Fix major security bug: servers were disregarding their
21091 exit policies if clients behaved unexpectedly.
21092 - Make OS X init script check for missing argument, so we don't
21093 confuse users who invoke it incorrectly.
21094 - Fix a seg fault in "tor --hash-password foo".
21095 - The MAPADDRESS control command was broken.
21098 Changes in version 0.1.1.1-alpha - 2005-06-29
21100 - Make OS X init script check for missing argument, so we don't
21101 confuse users who invoke it incorrectly.
21102 - Fix a seg fault in "tor --hash-password foo".
21103 - Fix a possible way to DoS dirservers.
21104 - When we complain that your exit policy implicitly allows local or
21105 private address spaces, name them explicitly so operators can
21107 - Make the log message less scary when all the dirservers are
21108 temporarily unreachable.
21109 - We were printing the number of idle dns workers incorrectly when
21113 - Revised controller protocol (version 1) that uses ascii rather
21114 than binary. Add supporting libraries in python and java so you
21115 can use the controller from your applications without caring how
21116 our protocol works.
21117 - Spiffy new support for crypto hardware accelerators. Can somebody
21121 Changes in version 0.0.9.10 - 2005-06-16
21122 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
21123 - Refuse relay cells that claim to have a length larger than the
21124 maximum allowed. This prevents a potential attack that could read
21125 arbitrary memory (e.g. keys) from an exit server's process
21129 Changes in version 0.1.0.10 - 2005-06-14
21130 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
21131 libevent before 1.1a.
21134 Changes in version 0.1.0.9-rc - 2005-06-09
21136 - Reset buf->highwater every time buf_shrink() is called, not just on
21137 a successful shrink. This was causing significant memory bloat.
21138 - Fix buffer overflow when checking hashed passwords.
21139 - Security fix: if seeding the RNG on Win32 fails, quit.
21140 - Allow seeding the RNG on Win32 even when you're not running as
21142 - Disable threading on Solaris too. Something is wonky with it,
21143 cpuworkers, and reentrant libs.
21144 - Reenable the part of the code that tries to flush as soon as an
21145 OR outbuf has a full TLS record available. Perhaps this will make
21146 OR outbufs not grow as huge except in rare cases, thus saving lots
21147 of CPU time plus memory.
21148 - Reject malformed .onion addresses rather then passing them on as
21149 normal web requests.
21150 - Adapt patch from Adam Langley: fix possible memory leak in
21151 tor_lookup_hostname().
21152 - Initialize libevent later in the startup process, so the logs are
21153 already established by the time we start logging libevent warns.
21154 - Use correct errno on win32 if libevent fails.
21155 - Check and warn about known-bad/slow libevent versions.
21156 - Pay more attention to the ClientOnly config option.
21157 - Have torctl.in/tor.sh.in check for location of su binary (needed
21159 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
21160 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
21161 HttpProxyAuthenticator
21162 - Stop warning about sigpipes in the logs. We're going to
21163 pretend that getting these occassionally is normal and fine.
21164 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
21166 installer screens; and don't put stuff into StartupItems unless
21167 the user asks you to.
21168 - Require servers that use the default dirservers to have public IP
21169 addresses. We have too many servers that are configured with private
21170 IPs and their admins never notice the log entries complaining that
21171 their descriptors are being rejected.
21172 - Add OSX uninstall instructions. An actual uninstall script will
21176 Changes in version 0.1.0.8-rc - 2005-05-23
21178 - It turns out that kqueue on OS X 10.3.9 was causing kernel
21179 panics. Disable kqueue on all OS X Tors.
21180 - Fix RPM: remove duplicate line accidentally added to the rpm
21182 - Disable threads on openbsd too, since its gethostaddr is not
21184 - Tolerate libevent 0.8 since it still works, even though it's
21186 - Enable building on Red Hat 9.0 again.
21187 - Allow the middle hop of the testing circuit to be running any
21188 version, now that most of them have the bugfix to let them connect
21189 to unknown servers. This will allow reachability testing to work
21190 even when 0.0.9.7-0.0.9.9 become obsolete.
21191 - Handle relay cells with rh.length too large. This prevents
21192 a potential attack that could read arbitrary memory (maybe even
21193 keys) from the exit server's process.
21194 - We screwed up the dirport reachability testing when we don't yet
21195 have a cached version of the directory. Hopefully now fixed.
21196 - Clean up router_load_single_router() (used by the controller),
21197 so it doesn't seg fault on error.
21198 - Fix a minor memory leak when somebody establishes an introduction
21199 point at your Tor server.
21200 - If a socks connection ends because read fails, don't warn that
21201 you're not sending a socks reply back.
21204 - Add HttpProxyAuthenticator config option too, that works like
21205 the HttpsProxyAuthenticator config option.
21206 - Encode hashed controller passwords in hex instead of base64,
21207 to make it easier to write controllers.
21210 Changes in version 0.1.0.7-rc - 2005-05-17
21212 - Fix a bug in the OS X package installer that prevented it from
21213 installing on Tiger.
21214 - Fix a script bug in the OS X package installer that made it
21215 complain during installation.
21216 - Find libevent even if it's hiding in /usr/local/ and your
21217 CFLAGS and LDFLAGS don't tell you to look there.
21218 - Be able to link with libevent as a shared library (the default
21219 after 1.0d), even if it's hiding in /usr/local/lib and even
21220 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
21221 assuming you're running gcc. Otherwise fail and give a useful
21223 - Fix a bug in the RPM packager: set home directory for _tor to
21224 something more reasonable when first installing.
21225 - Free a minor amount of memory that is still reachable on exit.
21228 Changes in version 0.1.0.6-rc - 2005-05-14
21230 - Implement --disable-threads configure option. Disable threads on
21231 netbsd by default, because it appears to have no reentrant resolver
21233 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
21234 release (1.1) detects and disables kqueue if it's broken.
21235 - Append default exit policy before checking for implicit internal
21236 addresses. Now we don't log a bunch of complaints on startup
21237 when using the default exit policy.
21238 - Some people were putting "Address " in their torrc, and they had
21239 a buggy resolver that resolved " " to 0.0.0.0. Oops.
21240 - If DataDir is ~/.tor, and that expands to /.tor, then default to
21241 LOCALSTATEDIR/tor instead.
21242 - Fix fragmented-message bug in TorControl.py.
21243 - Resolve a minor bug which would prevent unreachable dirports
21244 from getting suppressed in the published descriptor.
21245 - When the controller gave us a new descriptor, we weren't resolving
21246 it immediately, so Tor would think its address was 0.0.0.0 until
21247 we fetched a new directory.
21248 - Fix an uppercase/lowercase case error in suppressing a bogus
21249 libevent warning on some Linuxes.
21252 - Begin scrubbing sensitive strings from logs by default. Turn off
21253 the config option SafeLogging if you need to do debugging.
21254 - Switch to a new buffer management algorithm, which tries to avoid
21255 reallocing and copying quite as much. In first tests it looks like
21256 it uses *more* memory on average, but less cpu.
21257 - First cut at support for "create-fast" cells. Clients can use
21258 these when extending to their first hop, since the TLS already
21259 provides forward secrecy and authentication. Not enabled on
21261 - When dirservers refuse a router descriptor, we now log its
21262 contactinfo, platform, and the poster's IP address.
21263 - Call tor_free_all instead of connections_free_all after forking, to
21264 save memory on systems that need to fork.
21265 - Whine at you if you're a server and you don't set your contactinfo.
21266 - Implement --verify-config command-line option to check if your torrc
21267 is valid without actually launching Tor.
21268 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
21269 rather than just rejecting it.
21272 Changes in version 0.1.0.5-rc - 2005-04-27
21274 - Stop trying to print a null pointer if an OR conn fails because
21275 we didn't like its cert.
21277 - Switch our internal buffers implementation to use a ring buffer,
21278 to hopefully improve performance for fast servers a lot.
21279 - Add HttpsProxyAuthenticator support (basic auth only), based
21280 on patch from Adam Langley.
21281 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
21282 the fast servers that have been joining lately.
21283 - Give hidden service accesses extra time on the first attempt,
21284 since 60 seconds is often only barely enough. This might improve
21286 - Improve performance for dirservers: stop re-parsing the whole
21287 directory every time you regenerate it.
21288 - Add more debugging info to help us find the weird dns freebsd
21289 pthreads bug; cleaner debug messages to help track future issues.
21292 Changes in version 0.0.9.9 - 2005-04-23
21293 o Bugfixes on 0.0.9.x:
21294 - If unofficial Tor clients connect and send weird TLS certs, our
21295 Tor server triggers an assert. This release contains a minimal
21296 backport from the broader fix that we put into 0.1.0.4-rc.
21299 Changes in version 0.1.0.4-rc - 2005-04-23
21301 - If unofficial Tor clients connect and send weird TLS certs, our
21302 Tor server triggers an assert. Stop asserting, and start handling
21303 TLS errors better in other situations too.
21304 - When the controller asks us to tell it about all the debug-level
21305 logs, it turns out we were generating debug-level logs while
21306 telling it about them, which turns into a bad loop. Now keep
21307 track of whether you're sending a debug log to the controller,
21308 and don't log when you are.
21309 - Fix the "postdescriptor" feature of the controller interface: on
21310 non-complete success, only say "done" once.
21312 - Clients are now willing to load balance over up to 2mB, not 1mB,
21313 of advertised bandwidth capacity.
21314 - Add a NoPublish config option, so you can be a server (e.g. for
21315 testing running Tor servers in other Tor networks) without
21316 publishing your descriptor to the primary dirservers.
21319 Changes in version 0.1.0.3-rc - 2005-04-08
21320 o Improvements on 0.1.0.2-rc:
21321 - Client now retries when streams end early for 'hibernating' or
21322 'resource limit' reasons, rather than failing them.
21323 - More automated handling for dirserver operators:
21324 - Automatically approve nodes running 0.1.0.2-rc or later,
21325 now that the the reachability detection stuff is working.
21326 - Now we allow two unverified servers with the same nickname
21327 but different keys. But if a nickname is verified, only that
21328 nickname+key are allowed.
21329 - If you're an authdirserver connecting to an address:port,
21330 and it's not the OR you were expecting, forget about that
21331 descriptor. If he *was* the one you were expecting, then forget
21332 about all other descriptors for that address:port.
21333 - Allow servers to publish descriptors from 12 hours in the future.
21334 Corollary: only whine about clock skew from the dirserver if
21335 he's a trusted dirserver (since now even verified servers could
21336 have quite wrong clocks).
21337 - Adjust maximum skew and age for rendezvous descriptors: let skew
21338 be 48 hours rather than 90 minutes.
21339 - Efficiency improvements:
21340 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
21341 it much faster to look up a circuit for each relay cell.
21342 - Remove most calls to assert_all_pending_dns_resolves_ok(),
21343 since they're eating our cpu on exit nodes.
21344 - Stop wasting time doing a case insensitive comparison for every
21345 dns name every time we do any lookup. Canonicalize the names to
21346 lowercase and be done with it.
21347 - Start sending 'truncated' cells back rather than destroy cells,
21348 if the circuit closes in front of you. This means we won't have
21349 to abandon partially built circuits.
21350 - Only warn once per nickname from add_nickname_list_to_smartlist
21351 per failure, so an entrynode or exitnode choice that's down won't
21353 - Put a note in the torrc about abuse potential with the default
21355 - Revise control spec and implementation to allow all log messages to
21356 be sent to controller with their severities intact (suggested by
21357 Matt Edman). Update TorControl to handle new log event types.
21358 - Provide better explanation messages when controller's POSTDESCRIPTOR
21360 - Stop putting nodename in the Platform string in server descriptors.
21361 It doesn't actually help, and it is confusing/upsetting some people.
21363 o Bugfixes on 0.1.0.2-rc:
21364 - We were printing the host mask wrong in exit policies in server
21365 descriptors. This isn't a critical bug though, since we were still
21366 obeying the exit policy internally.
21367 - Fix Tor when compiled with libevent but without pthreads: move
21368 connection_unregister() from _connection_free() to
21370 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
21371 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
21372 when we look through the connection array, we'll find any of the
21373 cpu/dnsworkers. This is no good.
21375 o Bugfixes on 0.0.9.8:
21376 - Fix possible bug on threading platforms (e.g. win32) which was
21377 leaking a file descriptor whenever a cpuworker or dnsworker died.
21378 - When using preferred entry or exit nodes, ignore whether the
21379 circuit wants uptime or capacity. They asked for the nodes, they
21381 - chdir() to your datadirectory at the *end* of the daemonize process,
21382 not the beginning. This was a problem because the first time you
21383 run tor, if your datadir isn't there, and you have runasdaemon set
21384 to 1, it will try to chdir to it before it tries to create it. Oops.
21385 - Handle changed router status correctly when dirserver reloads
21386 fingerprint file. We used to be dropping all unverified descriptors
21387 right then. The bug was hidden because we would immediately
21388 fetch a directory from another dirserver, which would include the
21389 descriptors we just dropped.
21390 - When we're connecting to an OR and he's got a different nickname/key
21391 than we were expecting, only complain loudly if we're an OP or a
21392 dirserver. Complaining loudly to the OR admins just confuses them.
21393 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
21394 artificially capped at 500kB.
21397 Changes in version 0.0.9.8 - 2005-04-07
21398 o Bugfixes on 0.0.9.x:
21399 - We have a bug that I haven't found yet. Sometimes, very rarely,
21400 cpuworkers get stuck in the 'busy' state, even though the cpuworker
21401 thinks of itself as idle. This meant that no new circuits ever got
21402 established. Here's a workaround to kill any cpuworker that's been
21403 busy for more than 100 seconds.
21406 Changes in version 0.1.0.2-rc - 2005-04-01
21407 o Bugfixes on 0.1.0.1-rc:
21408 - Fixes on reachability detection:
21409 - Don't check for reachability while hibernating.
21410 - If ORPort is reachable but DirPort isn't, still publish the
21411 descriptor, but zero out DirPort until it's found reachable.
21412 - When building testing circs for ORPort testing, use only
21413 high-bandwidth nodes, so fewer circuits fail.
21414 - Complain about unreachable ORPort separately from unreachable
21415 DirPort, so the user knows what's going on.
21416 - Make sure we only conclude ORPort reachability if we didn't
21417 initiate the conn. Otherwise we could falsely conclude that
21418 we're reachable just because we connected to the guy earlier
21419 and he used that same pipe to extend to us.
21420 - Authdirservers shouldn't do ORPort reachability detection,
21421 since they're in clique mode, so it will be rare to find a
21422 server not already connected to them.
21423 - When building testing circuits, always pick middle hops running
21424 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
21425 bug. (This is a kludge; it will go away when 0.0.9.x becomes
21427 - When we decide we're reachable, actually publish our descriptor
21429 - Fix bug in redirectstream in the controller.
21430 - Fix the state descriptor strings so logs don't claim edge streams
21431 are in a different state than they actually are.
21432 - Use recent libevent features when possible (this only really affects
21433 win32 and osx right now, because the new libevent with these
21434 features hasn't been released yet). Add code to suppress spurious
21436 - Prevent possible segfault in connection_close_unattached_ap().
21437 - Fix newlines on torrc in win32.
21438 - Improve error msgs when tor-resolve fails.
21440 o Improvements on 0.0.9.x:
21441 - New experimental script tor/contrib/ExerciseServer.py (needs more
21442 work) that uses the controller interface to build circuits and
21443 fetch pages over them. This will help us bootstrap servers that
21444 have lots of capacity but haven't noticed it yet.
21445 - New experimental script tor/contrib/PathDemo.py (needs more work)
21446 that uses the controller interface to let you choose whole paths
21448 "<hostname>.<path,separated by dots>.<length of path>.path"
21449 - When we've connected to an OR and handshaked but didn't like
21450 the result, we were closing the conn without sending destroy
21451 cells back for pending circuits. Now send those destroys.
21454 Changes in version 0.0.9.7 - 2005-04-01
21455 o Bugfixes on 0.0.9.x:
21456 - Fix another race crash bug (thanks to Glenn Fink for reporting).
21457 - Compare identity to identity, not to nickname, when extending to
21458 a router not already in the directory. This was preventing us from
21459 extending to unknown routers. Oops.
21460 - Make sure to create OS X Tor user in <500 range, so we aren't
21461 creating actual system users.
21462 - Note where connection-that-hasn't-sent-end was marked, and fix
21463 a few really loud instances of this harmless bug (it's fixed more
21467 Changes in version 0.1.0.1-rc - 2005-03-28
21469 - Add reachability testing. Your Tor server will automatically try
21470 to see if its ORPort and DirPort are reachable from the outside,
21471 and it won't upload its descriptor until it decides they are.
21472 - Handle unavailable hidden services better. Handle slow or busy
21473 hidden services better.
21474 - Add support for CONNECTing through https proxies, with "HttpsProxy"
21476 - New exit policy: accept most low-numbered ports, rather than
21477 rejecting most low-numbered ports.
21478 - More Tor controller support (still experimental). See
21479 http://tor.eff.org/doc/control-spec.txt for all the new features,
21480 including signals to emulate unix signals from any platform;
21481 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
21482 closestream; closecircuit; etc.
21483 - Make nt services work and start on startup on win32 (based on
21484 patch by Matt Edman).
21485 - Add a new AddressMap config directive to rewrite incoming socks
21486 addresses. This lets you, for example, declare an implicit
21487 required exit node for certain sites.
21488 - Add a new TrackHostExits config directive to trigger addressmaps
21489 for certain incoming socks addresses -- for sites that break when
21490 your exit keeps changing (based on patch by Mike Perry).
21491 - Redo the client-side dns cache so it's just an addressmap too.
21492 - Notice when our IP changes, and reset stats/uptime/reachability.
21493 - When an application is using socks5, give him the whole variety of
21494 potential socks5 responses (connect refused, host unreachable, etc),
21495 rather than just "success" or "failure".
21496 - A more sane version numbering system. See
21497 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
21498 - New contributed script "exitlist": a simple python script to
21499 parse directories and find Tor nodes that exit to listed
21501 - New contributed script "privoxy-tor-toggle" to toggle whether
21502 Privoxy uses Tor. Seems to be configured for Debian by default.
21503 - Report HTTP reasons to client when getting a response from directory
21504 servers -- so you can actually know what went wrong.
21505 - New config option MaxAdvertisedBandwidth which lets you advertise
21506 a low bandwidthrate (to not attract as many circuits) while still
21507 allowing a higher bandwidthrate in reality.
21509 o Robustness/stability fixes:
21510 - Make Tor use Niels Provos's libevent instead of its current
21511 poll-but-sometimes-select mess. This will let us use faster async
21512 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
21514 - pthread support now too. This was forced because when we forked,
21515 we ended up wasting a lot of duplicate ram over time. Also switch
21516 to foo_r versions of some library calls to allow reentry and
21518 - Better handling for heterogeneous / unreliable nodes:
21519 - Annotate circuits w/ whether they aim to contain high uptime nodes
21520 and/or high capacity nodes. When building circuits, choose
21522 - This means that every single node in an intro rend circuit,
21523 not just the last one, will have a minimum uptime.
21524 - New config option LongLivedPorts to indicate application streams
21525 that will want high uptime circuits.
21526 - Servers reset uptime when a dir fetch entirely fails. This
21527 hopefully reflects stability of the server's network connectivity.
21528 - If somebody starts his tor server in Jan 2004 and then fixes his
21529 clock, don't make his published uptime be a year.
21530 - Reset published uptime when you wake up from hibernation.
21531 - Introduce a notion of 'internal' circs, which are chosen without
21532 regard to the exit policy of the last hop. Intro and rendezvous
21533 circs must be internal circs, to avoid leaking information. Resolve
21534 and connect streams can use internal circs if they want.
21535 - New circuit pooling algorithm: make sure to have enough circs around
21536 to satisfy any predicted ports, and also make sure to have 2 internal
21537 circs around if we've required internal circs lately (and with high
21538 uptime if we've seen that lately too).
21539 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
21540 which describes how often we retry making new circuits if current
21541 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
21542 how long we're willing to make use of an already-dirty circuit.
21543 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
21544 circ as necessary, if there are any completed ones lying around
21545 when we try to launch one.
21546 - Make hidden services try to establish a rendezvous for 30 seconds,
21547 rather than for n (where n=3) attempts to build a circuit.
21548 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
21549 "ShutdownWaitLength".
21550 - Try to be more zealous about calling connection_edge_end when
21551 things go bad with edge conns in connection.c.
21552 - Revise tor-spec to add more/better stream end reasons.
21553 - Revise all calls to connection_edge_end to avoid sending "misc",
21554 and to take errno into account where possible.
21557 - Fix a race condition that can trigger an assert, when we have a
21558 pending create cell and an OR connection fails right then.
21559 - Fix several double-mark-for-close bugs, e.g. where we were finding
21560 a conn for a cell even if that conn is already marked for close.
21561 - Make sequence of log messages when starting on win32 with no config
21562 file more reasonable.
21563 - When choosing an exit node for a new non-internal circ, don't take
21564 into account whether it'll be useful for any pending x.onion
21565 addresses -- it won't.
21566 - Turn addr_policy_compare from a tristate to a quadstate; this should
21567 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
21568 for google.com" problem.
21569 - Make "platform" string in descriptor more accurate for Win32 servers,
21570 so it's not just "unknown platform".
21571 - Fix an edge case in parsing config options (thanks weasel).
21572 If they say "--" on the commandline, it's not an option.
21573 - Reject odd-looking addresses at the client (e.g. addresses that
21574 contain a colon), rather than having the server drop them because
21576 - tor-resolve requests were ignoring .exit if there was a working circuit
21577 they could use instead.
21578 - REUSEADDR on normal platforms means you can rebind to the port
21579 right after somebody else has let it go. But REUSEADDR on win32
21580 means to let you bind to the port _even when somebody else
21581 already has it bound_! So, don't do that on Win32.
21582 - Change version parsing logic: a version is "obsolete" if it is not
21583 recommended and (1) there is a newer recommended version in the
21584 same series, or (2) there are no recommended versions in the same
21585 series, but there are some recommended versions in a newer series.
21586 A version is "new" if it is newer than any recommended version in
21588 - Stop most cases of hanging up on a socks connection without sending
21592 - Require BandwidthRate to be at least 20kB/s for servers.
21593 - When a dirserver causes you to give a warn, mention which dirserver
21595 - New config option DirAllowPrivateAddresses for authdirservers.
21596 Now by default they refuse router descriptors that have non-IP or
21597 private-IP addresses.
21598 - Stop publishing socksport in the directory, since it's not
21599 actually meant to be public. For compatibility, publish a 0 there
21601 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
21602 smart" value, that is low for servers and high for clients.
21603 - If our clock jumps forward by 100 seconds or more, assume something
21604 has gone wrong with our network and abandon all not-yet-used circs.
21605 - Warn when exit policy implicitly allows local addresses.
21606 - If we get an incredibly skewed timestamp from a dirserver mirror
21607 that isn't a verified OR, don't warn -- it's probably him that's
21609 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
21610 cookies to disk and doesn't log each web request to disk. (Thanks
21611 to Brett Carrington for pointing this out.)
21612 - When a client asks us for a dir mirror and we don't have one,
21613 launch an attempt to get a fresh one.
21614 - If we're hibernating and we get a SIGINT, exit immediately.
21615 - Add --with-dmalloc ./configure option, to track memory leaks.
21616 - And try to free all memory on closing, so we can detect what
21618 - Cache local dns resolves correctly even when they're .exit
21620 - Give a better warning when some other server advertises an
21621 ORPort that is actually an apache running ssl.
21622 - Add "opt hibernating 1" to server descriptor to make it clearer
21623 whether the server is hibernating.
21626 Changes in version 0.0.9.6 - 2005-03-24
21627 o Bugfixes on 0.0.9.x (crashes and asserts):
21628 - Add new end stream reasons to maintainance branch. Fix bug where
21629 reason (8) could trigger an assert. Prevent bug from recurring.
21630 - Apparently win32 stat wants paths to not end with a slash.
21631 - Fix assert triggers in assert_cpath_layer_ok(), where we were
21632 blowing away the circuit that conn->cpath_layer points to, then
21633 checking to see if the circ is well-formed. Backport check to make
21634 sure we dont use the cpath on a closed connection.
21635 - Prevent circuit_resume_edge_reading_helper() from trying to package
21636 inbufs for marked-for-close streams.
21637 - Don't crash on hup if your options->address has become unresolvable.
21638 - Some systems (like OS X) sometimes accept() a connection and tell
21639 you the remote host is 0.0.0.0:0. If this happens, due to some
21640 other mis-features, we get confused; so refuse the conn for now.
21642 o Bugfixes on 0.0.9.x (other):
21643 - Fix harmless but scary "Unrecognized content encoding" warn message.
21644 - Add new stream error reason: TORPROTOCOL reason means "you are not
21645 speaking a version of Tor I understand; say bye-bye to your stream."
21646 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
21647 into the future, now that we are more tolerant of skew. This
21648 resolves a bug where a Tor server would refuse to cache a directory
21649 because all the directories it gets are too far in the future;
21650 yet the Tor server never logs any complaints about clock skew.
21651 - Mac packaging magic: make man pages useable, and do not overwrite
21652 existing torrc files.
21653 - Make OS X log happily to /var/log/tor/tor.log
21656 Changes in version 0.0.9.5 - 2005-02-22
21657 o Bugfixes on 0.0.9.x:
21658 - Fix an assert race at exit nodes when resolve requests fail.
21659 - Stop picking unverified dir mirrors--it only leads to misery.
21660 - Patch from Matt Edman to make NT services work better. Service
21661 support is still not compiled into the executable by default.
21662 - Patch from Dmitri Bely so the Tor service runs better under
21663 the win32 SYSTEM account.
21664 - Make tor-resolve actually work (?) on Win32.
21665 - Fix a sign bug when getrlimit claims to have 4+ billion
21666 file descriptors available.
21667 - Stop refusing to start when bandwidthburst == bandwidthrate.
21668 - When create cells have been on the onion queue more than five
21669 seconds, just send back a destroy and take them off the list.
21672 Changes in version 0.0.9.4 - 2005-02-03
21673 o Bugfixes on 0.0.9:
21674 - Fix an assert bug that took down most of our servers: when
21675 a server claims to have 1 GB of bandwidthburst, don't
21677 - Don't crash as badly if we have spawned the max allowed number
21678 of dnsworkers, or we're out of file descriptors.
21679 - Block more file-sharing ports in the default exit policy.
21680 - MaxConn is now automatically set to the hard limit of max
21681 file descriptors we're allowed (ulimit -n), minus a few for
21683 - Give a clearer message when servers need to raise their
21684 ulimit -n when they start running out of file descriptors.
21685 - SGI Compatibility patches from Jan Schaumann.
21686 - Tolerate a corrupt cached directory better.
21687 - When a dirserver hasn't approved your server, list which one.
21688 - Go into soft hibernation after 95% of the bandwidth is used,
21689 not 99%. This is especially important for daily hibernators who
21690 have a small accounting max. Hopefully it will result in fewer
21691 cut connections when the hard hibernation starts.
21692 - Load-balance better when using servers that claim more than
21693 800kB/s of capacity.
21694 - Make NT services work (experimental, only used if compiled in).
21697 Changes in version 0.0.9.3 - 2005-01-21
21698 o Bugfixes on 0.0.9:
21699 - Backport the cpu use fixes from main branch, so busy servers won't
21700 need as much processor time.
21701 - Work better when we go offline and then come back, or when we
21702 run Tor at boot before the network is up. We do this by
21703 optimistically trying to fetch a new directory whenever an
21704 application request comes in and we think we're offline -- the
21705 human is hopefully a good measure of when the network is back.
21706 - Backport some minimal hidserv bugfixes: keep rend circuits open as
21707 long as you keep using them; actually publish hidserv descriptors
21708 shortly after they change, rather than waiting 20-40 minutes.
21709 - Enable Mac startup script by default.
21710 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
21711 - When you update AllowUnverifiedNodes or FirewallPorts via the
21712 controller's setconf feature, we were always appending, never
21714 - When you update HiddenServiceDir via setconf, it was screwing up
21715 the order of reading the lines, making it fail.
21716 - Do not rewrite a cached directory back to the cache; otherwise we
21717 will think it is recent and not fetch a newer one on startup.
21718 - Workaround for webservers that lie about Content-Encoding: Tor
21719 now tries to autodetect compressed directories and compression
21720 itself. This lets us Proxypass dir fetches through apache.
21723 Changes in version 0.0.9.2 - 2005-01-04
21724 o Bugfixes on 0.0.9 (crashes and asserts):
21725 - Fix an assert on startup when the disk is full and you're logging
21727 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
21728 style address, then we'd crash.
21729 - Fix an assert trigger when the running-routers string we get from
21730 a dirserver is broken.
21731 - Make worker threads start and run on win32. Now win32 servers
21733 - Bandaid (not actually fix, but now it doesn't crash) an assert
21734 where the dns worker dies mysteriously and the main Tor process
21735 doesn't remember anything about the address it was resolving.
21737 o Bugfixes on 0.0.9 (Win32):
21738 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
21739 name out of the warning/assert messages.
21740 - Fix a superficial "unhandled error on read" bug on win32.
21741 - The win32 installer no longer requires a click-through for our
21742 license, since our Free Software license grants rights but does not
21744 - Win32: When connecting to a dirserver fails, try another one
21745 immediately. (This was already working for non-win32 Tors.)
21746 - Stop trying to parse $HOME on win32 when hunting for default
21748 - Make tor-resolve.c work on win32 by calling network_init().
21750 o Bugfixes on 0.0.9 (other):
21751 - Make 0.0.9.x build on Solaris again.
21752 - Due to a fencepost error, we were blowing away the \n when reporting
21753 confvalue items in the controller. So asking for multiple config
21754 values at once couldn't work.
21755 - When listing circuits that are pending on an opening OR connection,
21756 if we're an OR we were listing circuits that *end* at us as
21757 being pending on every listener, dns/cpu worker, etc. Stop that.
21758 - Dirservers were failing to create 'running-routers' or 'directory'
21759 strings if we had more than some threshold of routers. Fix them so
21760 they can handle any number of routers.
21761 - Fix a superficial "Duplicate mark for close" bug.
21762 - Stop checking for clock skew for OR connections, even for servers.
21763 - Fix a fencepost error that was chopping off the last letter of any
21764 nickname that is the maximum allowed nickname length.
21765 - Update URLs in log messages so they point to the new website.
21766 - Fix a potential problem in mangling server private keys while
21767 writing to disk (not triggered yet, as far as we know).
21768 - Include the licenses for other free software we include in Tor,
21769 now that we're shipping binary distributions more regularly.
21772 Changes in version 0.0.9.1 - 2004-12-15
21773 o Bugfixes on 0.0.9:
21774 - Make hibernation actually work.
21775 - Make HashedControlPassword config option work.
21776 - When we're reporting event circuit status to a controller,
21777 don't use the stream status code.
21780 Changes in version 0.0.9 - 2004-12-12
21782 - Clean up manpage and torrc.sample file.
21783 - Clean up severities and text of log warnings.
21785 - Make servers trigger an assert when they enter hibernation.
21788 Changes in version 0.0.9rc7 - 2004-12-08
21789 o Bugfixes on 0.0.9rc:
21790 - Fix a stack-trashing crash when an exit node begins hibernating.
21791 - Avoid looking at unallocated memory while considering which
21792 ports we need to build circuits to cover.
21793 - Stop a sigpipe: when an 'end' cell races with eof from the app,
21794 we shouldn't hold-open-until-flush if the eof arrived first.
21795 - Fix a bug with init_cookie_authentication() in the controller.
21796 - When recommending new-format log lines, if the upper bound is
21797 LOG_ERR, leave it implicit.
21799 o Bugfixes on 0.0.8.1:
21800 - Fix a whole slew of memory leaks.
21801 - Fix isspace() and friends so they still make Solaris happy
21802 but also so they don't trigger asserts on win32.
21803 - Fix parse_iso_time on platforms without strptime (eg win32).
21804 - win32: tolerate extra "readable" events better.
21805 - win32: when being multithreaded, leave parent fdarray open.
21806 - Make unit tests work on win32.
21809 Changes in version 0.0.9rc6 - 2004-12-06
21810 o Bugfixes on 0.0.9pre:
21811 - Clean up some more integer underflow opportunities (not exploitable
21813 - While hibernating, hup should not regrow our listeners.
21814 - Send an end to the streams we close when we hibernate, rather
21815 than just chopping them off.
21816 - React to eof immediately on non-open edge connections.
21818 o Bugfixes on 0.0.8.1:
21819 - Calculate timeout for waiting for a connected cell from the time
21820 we sent the begin cell, not from the time the stream started. If
21821 it took a long time to establish the circuit, we would time out
21822 right after sending the begin cell.
21823 - Fix router_compare_addr_to_addr_policy: it was not treating a port
21824 of * as always matching, so we were picking reject *:* nodes as
21825 exit nodes too. Oops.
21828 - New circuit building strategy: keep a list of ports that we've
21829 used in the past 6 hours, and always try to have 2 circuits open
21830 or on the way that will handle each such port. Seed us with port
21831 80 so web users won't complain that Tor is "slow to start up".
21832 - Make kill -USR1 dump more useful stats about circuits.
21833 - When warning about retrying or giving up, print the address, so
21834 the user knows which one it's talking about.
21835 - If you haven't used a clean circuit in an hour, throw it away,
21836 just to be on the safe side. (This means after 6 hours a totally
21837 unused Tor client will have no circuits open.)
21840 Changes in version 0.0.9rc5 - 2004-12-01
21841 o Bugfixes on 0.0.8.1:
21842 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
21843 - Let resolve conns retry/expire also, rather than sticking around
21845 - If we are using select, make sure we stay within FD_SETSIZE.
21847 o Bugfixes on 0.0.9pre:
21848 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
21849 but doesn't seem to be currently; thanks to Ilja van Sprundel for
21851 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
21852 instead. Impose minima and maxima for all *Period options; impose
21853 even tighter maxima for fetching if we are a caching dirserver.
21854 Clip rather than rejecting.
21855 - Fetch cached running-routers from servers that serve it (that is,
21856 authdirservers and servers running 0.0.9rc5-cvs or later.)
21859 - Accept *:706 (silc) in default exit policy.
21860 - Implement new versioning format for post 0.1.
21861 - Support "foo.nickname.exit" addresses, to let Alice request the
21862 address "foo" as viewed by exit node "nickname". Based on a patch
21864 - Make tor --version --version dump the cvs Id of every file.
21867 Changes in version 0.0.9rc4 - 2004-11-28
21868 o Bugfixes on 0.0.8.1:
21869 - Make windows sockets actually non-blocking (oops), and handle
21870 win32 socket errors better.
21872 o Bugfixes on 0.0.9rc1:
21873 - Actually catch the -USR2 signal.
21876 Changes in version 0.0.9rc3 - 2004-11-25
21877 o Bugfixes on 0.0.8.1:
21878 - Flush the log file descriptor after we print "Tor opening log file",
21879 so we don't see those messages days later.
21881 o Bugfixes on 0.0.9rc1:
21882 - Make tor-resolve work again.
21883 - Avoid infinite loop in tor-resolve if tor hangs up on it.
21884 - Fix an assert trigger for clients/servers handling resolves.
21887 Changes in version 0.0.9rc2 - 2004-11-24
21888 o Bugfixes on 0.0.9rc1:
21889 - I broke socks5 support while fixing the eof bug.
21890 - Allow unitless bandwidths and intervals; they default to bytes
21892 - New servers don't start out hibernating; they are active until
21893 they run out of bytes, so they have a better estimate of how
21894 long it takes, and so their operators can know they're working.
21897 Changes in version 0.0.9rc1 - 2004-11-23
21898 o Bugfixes on 0.0.8.1:
21899 - Finally fix a bug that's been plaguing us for a year:
21900 With high load, circuit package window was reaching 0. Whenever
21901 we got a circuit-level sendme, we were reading a lot on each
21902 socket, but only writing out a bit. So we would eventually reach
21903 eof. This would be noticed and acted on even when there were still
21904 bytes sitting in the inbuf.
21905 - When poll() is interrupted, we shouldn't believe the revents values.
21907 o Bugfixes on 0.0.9pre6:
21908 - Fix hibernate bug that caused pre6 to be broken.
21909 - Don't keep rephist info for routers that haven't had activity for
21910 24 hours. (This matters now that clients have keys, since we track
21912 - Never call close_temp_logs while validating log options.
21913 - Fix backslash-escaping on tor.sh.in and torctl.in.
21916 - Implement weekly/monthly/daily accounting: now you specify your
21917 hibernation properties by
21918 AccountingMax N bytes|KB|MB|GB|TB
21919 AccountingStart day|week|month [day] HH:MM
21920 Defaults to "month 1 0:00".
21921 - Let bandwidth and interval config options be specified as 5 bytes,
21922 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
21923 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
21924 get back to normal.)
21925 - If your requested entry or exit node has advertised bandwidth 0,
21927 - Be more greedy about filling up relay cells -- we try reading again
21928 once we've processed the stuff we read, in case enough has arrived
21929 to fill the last cell completely.
21930 - Apply NT service patch from Osamu Fujino. Still needs more work.
21933 Changes in version 0.0.9pre6 - 2004-11-15
21934 o Bugfixes on 0.0.8.1:
21935 - Fix assert failure on malformed socks4a requests.
21936 - Use identity comparison, not nickname comparison, to choose which
21937 half of circuit-ID-space each side gets to use. This is needed
21938 because sometimes we think of a router as a nickname, and sometimes
21939 as a hex ID, and we can't predict what the other side will do.
21940 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
21941 write() call will fail and we handle it there.
21942 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
21943 and smartlist_len, which are two major profiling offenders.
21945 o Bugfixes on 0.0.9pre5:
21946 - Fix a bug in read_all that was corrupting config files on windows.
21947 - When we're raising the max number of open file descriptors to
21948 'unlimited', don't log that we just raised it to '-1'.
21949 - Include event code with events, as required by control-spec.txt.
21950 - Don't give a fingerprint when clients do --list-fingerprint:
21951 it's misleading, because it will never be the same again.
21952 - Stop using strlcpy in tor_strndup, since it was slowing us
21954 - Remove warn on startup about missing cached-directory file.
21955 - Make kill -USR1 work again.
21956 - Hibernate if we start tor during the "wait for wakeup-time" phase
21957 of an accounting interval. Log our hibernation plans better.
21958 - Authoritative dirservers now also cache their directory, so they
21959 have it on start-up.
21962 - Fetch running-routers; cache running-routers; compress
21963 running-routers; serve compressed running-routers.z
21964 - Add NSI installer script contributed by J Doe.
21965 - Commit VC6 and VC7 workspace/project files.
21966 - Commit a tor.spec for making RPM files, with help from jbash.
21967 - Add contrib/torctl.in contributed by Glenn Fink.
21968 - Implement the control-spec's SAVECONF command, to write your
21969 configuration to torrc.
21970 - Get cookie authentication for the controller closer to working.
21971 - Include control-spec.txt in the tarball.
21972 - When set_conf changes our server descriptor, upload a new copy.
21973 But don't upload it too often if there are frequent changes.
21974 - Document authentication config in man page, and document signals
21976 - Clean up confusing parts of man page and torrc.sample.
21977 - Make expand_filename handle ~ and ~username.
21978 - Use autoconf to enable largefile support where necessary. Use
21979 ftello where available, since ftell can fail at 2GB.
21980 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
21981 log more informatively.
21982 - Give a slightly more useful output for "tor -h".
21983 - Refuse application socks connections to port 0.
21984 - Check clock skew for verified servers, but allow unverified
21985 servers and clients to have any clock skew.
21986 - Break DirFetchPostPeriod into:
21987 - DirFetchPeriod for fetching full directory,
21988 - StatusFetchPeriod for fetching running-routers,
21989 - DirPostPeriod for posting server descriptor,
21990 - RendPostPeriod for posting hidden service descriptors.
21991 - Make sure the hidden service descriptors are at a random offset
21992 from each other, to hinder linkability.
21995 Changes in version 0.0.9pre5 - 2004-11-09
21996 o Bugfixes on 0.0.9pre4:
21997 - Fix a seg fault in unit tests (doesn't affect main program).
21998 - Fix an assert bug where a hidden service provider would fail if
21999 the first hop of his rendezvous circuit was down.
22000 - Hidden service operators now correctly handle version 1 style
22001 INTRODUCE1 cells (nobody generates them still, so not a critical
22003 - If do_hup fails, actually notice.
22004 - Handle more errnos from accept() without closing the listener.
22005 Some OpenBSD machines were closing their listeners because
22006 they ran out of file descriptors.
22007 - Send resolve cells to exit routers that are running a new
22008 enough version of the resolve code to work right.
22009 - Better handling of winsock includes on non-MSV win32 compilers.
22010 - Some people had wrapped their tor client/server in a script
22011 that would restart it whenever it died. This did not play well
22012 with our "shut down if your version is obsolete" code. Now people
22013 don't fetch a new directory if their local cached version is
22015 - Make our autogen.sh work on ksh as well as bash.
22018 - Hibernation: New config option "AccountingMaxKB" lets you
22019 set how many KBytes per month you want to allow your server to
22020 consume. Rather than spreading those bytes out evenly over the
22021 month, we instead hibernate for some of the month and pop up
22022 at a deterministic time, work until the bytes are consumed, then
22023 hibernate again. Config option "MonthlyAccountingStart" lets you
22024 specify which day of the month your billing cycle starts on.
22025 - Control interface: a separate program can now talk to your
22026 client/server over a socket, and get/set config options, receive
22027 notifications of circuits and streams starting/finishing/dying,
22028 bandwidth used, etc. The next step is to get some GUIs working.
22029 Let us know if you want to help out. See doc/control-spec.txt .
22030 - Ship a contrib/tor-control.py as an example script to interact
22031 with the control port.
22032 - "tor --hash-password zzyxz" will output a salted password for
22033 use in authenticating to the control interface.
22034 - New log format in config:
22035 "Log minsev[-maxsev] stdout|stderr|syslog" or
22036 "Log minsev[-maxsev] file /var/foo"
22039 - DirPolicy config option, to let people reject incoming addresses
22040 from their dirserver.
22041 - "tor --list-fingerprint" will list your identity key fingerprint
22043 - Add "pass" target for RedirectExit, to make it easier to break
22044 out of a sequence of RedirectExit rules.
22045 - Clients now generate a TLS cert too, in preparation for having
22046 them act more like real nodes.
22047 - Ship src/win32/ in the tarball, so people can use it to build.
22048 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
22050 - New "router-status" line in directory, to better bind each verified
22051 nickname to its identity key.
22052 - Deprecate unofficial config option abbreviations, and abbreviations
22053 not on the command line.
22054 - Add a pure-C tor-resolve implementation.
22055 - Use getrlimit and friends to ensure we can reach MaxConn (currently
22056 1024) file descriptors.
22058 o Code security improvements, inspired by Ilja:
22059 - Replace sprintf with snprintf. (I think they were all safe, but
22061 - Replace strcpy/strncpy with strlcpy in more places.
22062 - Avoid strcat; use snprintf or strlcat instead.
22063 - snprintf wrapper with consistent (though not C99) overflow behavior.
22066 Changes in version 0.0.9pre4 - 2004-10-17
22067 o Bugfixes on 0.0.9pre3:
22068 - If the server doesn't specify an exit policy, use the real default
22069 exit policy, not reject *:*.
22070 - Ignore fascistfirewall when uploading/downloading hidden service
22071 descriptors, since we go through Tor for those; and when using
22072 an HttpProxy, since we assume it can reach them all.
22073 - When looking for an authoritative dirserver, use only the ones
22074 configured at boot. Don't bother looking in the directory.
22075 - The rest of the fix for get_default_conf_file() on older win32.
22076 - Make 'Routerfile' config option obsolete.
22079 - New 'MyFamily nick1,...' config option for a server to
22080 specify other servers that shouldn't be used in the same circuit
22081 with it. Only believed if nick1 also specifies us.
22082 - New 'NodeFamily nick1,nick2,...' config option for a client to
22083 specify nodes that it doesn't want to use in the same circuit.
22084 - New 'Redirectexit pattern address:port' config option for a
22085 server to redirect exit connections, e.g. to a local squid.
22088 Changes in version 0.0.9pre3 - 2004-10-13
22089 o Bugfixes on 0.0.8.1:
22090 - Better torrc example lines for dirbindaddress and orbindaddress.
22091 - Improved bounds checking on parsed ints (e.g. config options and
22092 the ones we find in directories.)
22093 - Better handling of size_t vs int, so we're more robust on 64
22095 - Fix the rest of the bug where a newly started OR would appear
22096 as unverified even after we've added his fingerprint and hupped
22098 - Fix a bug from 0.0.7: when read() failed on a stream, we would
22099 close it without sending back an end. So 'connection refused'
22100 would simply be ignored and the user would get no response.
22102 o Bugfixes on 0.0.9pre2:
22103 - Serving the cached-on-disk directory to people is bad. We now
22104 provide no directory until we've fetched a fresh one.
22105 - Workaround for bug on windows where cached-directories get crlf
22107 - Make get_default_conf_file() work on older windows too.
22108 - If we write a *:* exit policy line in the descriptor, don't write
22109 any more exit policy lines.
22112 - Use only 0.0.9pre1 and later servers for resolve cells.
22113 - Make the dirservers file obsolete.
22114 - Include a dir-signing-key token in directories to tell the
22115 parsing entity which key is being used to sign.
22116 - Remove the built-in bulky default dirservers string.
22117 - New config option "Dirserver %s:%d [fingerprint]", which can be
22118 repeated as many times as needed. If no dirservers specified,
22119 default to moria1,moria2,tor26.
22120 - Make moria2 advertise a dirport of 80, so people behind firewalls
22121 will be able to get a directory.
22122 - Http proxy support
22123 - Dirservers translate requests for http://%s:%d/x to /x
22124 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
22125 be routed through this host.
22126 - Clients ask for /tor/x rather than /x for new enough dirservers.
22127 This way we can one day coexist peacefully with apache.
22128 - Clients specify a "Host: %s%d" http header, to be compatible
22129 with more proxies, and so running squid on an exit node can work.
22132 Changes in version 0.0.8.1 - 2004-10-13
22134 - Fix a seg fault that can be triggered remotely for Tor
22135 clients/servers with an open dirport.
22136 - Fix a rare assert trigger, where routerinfos for entries in
22137 our cpath would expire while we're building the path.
22138 - Fix a bug in OutboundBindAddress so it (hopefully) works.
22139 - Fix a rare seg fault for people running hidden services on
22140 intermittent connections.
22141 - Fix a bug in parsing opt keywords with objects.
22142 - Fix a stale pointer assert bug when a stream detaches and
22144 - Fix a string format vulnerability (probably not exploitable)
22145 in reporting stats locally.
22146 - Fix an assert trigger: sometimes launching circuits can fail
22147 immediately, e.g. because too many circuits have failed recently.
22148 - Fix a compile warning on 64 bit platforms.
22151 Changes in version 0.0.9pre2 - 2004-10-03
22153 - Make fetching a cached directory work for 64-bit platforms too.
22154 - Make zlib.h a required header, not an optional header.
22157 Changes in version 0.0.9pre1 - 2004-10-01
22159 - Stop using separate defaults for no-config-file and
22160 empty-config-file. Now you have to explicitly turn off SocksPort,
22161 if you don't want it open.
22162 - Fix a bug in OutboundBindAddress so it (hopefully) works.
22163 - Improve man page to mention more of the 0.0.8 features.
22164 - Fix a rare seg fault for people running hidden services on
22165 intermittent connections.
22166 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
22168 - Fix more dns related bugs: send back resolve_failed and end cells
22169 more reliably when the resolve fails, rather than closing the
22170 circuit and then trying to send the cell. Also attach dummy resolve
22171 connections to a circuit *before* calling dns_resolve(), to fix
22172 a bug where cached answers would never be sent in RESOLVED cells.
22173 - When we run out of disk space, or other log writing error, don't
22174 crash. Just stop logging to that log and continue.
22175 - We were starting to daemonize before we opened our logs, so if
22176 there were any problems opening logs, we would complain to stderr,
22177 which wouldn't work, and then mysteriously exit.
22178 - Fix a rare bug where sometimes a verified OR would connect to us
22179 before he'd uploaded his descriptor, which would cause us to
22180 assign conn->nickname as though he's unverified. Now we look through
22181 the fingerprint list to see if he's there.
22182 - Fix a rare assert trigger, where routerinfos for entries in
22183 our cpath would expire while we're building the path.
22186 - Clients can ask dirservers for /dir.z to get a compressed version
22187 of the directory. Only works for servers running 0.0.9, of course.
22188 - Make clients cache directories and use them to seed their router
22189 lists at startup. This means clients have a datadir again.
22190 - Configuration infrastructure support for warning on obsolete
22192 - Respond to content-encoding headers by trying to uncompress as
22194 - Reply with a deflated directory when a client asks for "dir.z".
22195 We could use allow-encodings instead, but allow-encodings isn't
22196 specified in HTTP 1.0.
22197 - Raise the max dns workers from 50 to 100.
22198 - Discourage people from setting their dirfetchpostperiod more often
22199 than once per minute.
22200 - Protect dirservers from overzealous descriptor uploading -- wait
22201 10 seconds after directory gets dirty, before regenerating.
22204 Changes in version 0.0.8 - 2004-08-25
22205 o Port it to SunOS 5.9 / Athena
22208 Changes in version 0.0.8rc2 - 2004-08-20
22209 o Make it compile on cygwin again.
22210 o When picking unverified routers, skip those with low uptime and/or
22211 low bandwidth, depending on what properties you care about.
22214 Changes in version 0.0.8rc1 - 2004-08-18
22215 o Changes from 0.0.7.3:
22217 - Fix assert triggers: if the other side returns an address 0.0.0.0,
22218 don't put it into the client dns cache.
22219 - If a begin failed due to exit policy, but we believe the IP address
22220 should have been allowed, switch that router to exitpolicy reject *:*
22221 until we get our next directory.
22223 - Clients choose nodes proportional to advertised bandwidth.
22224 - Avoid using nodes with low uptime as introduction points.
22225 - Handle servers with dynamic IP addresses: don't replace
22226 options->Address with the resolved one at startup, and
22227 detect our address right before we make a routerinfo each time.
22228 - 'FascistFirewall' option to pick dirservers and ORs on specific
22229 ports; plus 'FirewallPorts' config option to tell FascistFirewall
22230 which ports are open. (Defaults to 80,443)
22231 - Be more aggressive about trying to make circuits when the network
22232 has changed (e.g. when you unsuspend your laptop).
22233 - Check for time skew on http headers; report date in response to
22235 - If the entrynode config line has only one node, don't pick it as
22237 - Add strict{entry|exit}nodes config options. If set to 1, then
22238 we refuse to build circuits that don't include the specified entry
22240 - OutboundBindAddress config option, to bind to a specific
22241 IP address for outgoing connect()s.
22242 - End truncated log entries (e.g. directories) with "[truncated]".
22244 o Patches to 0.0.8preX:
22246 - Patches to compile and run on win32 again (maybe)?
22247 - Fix crash when looking for ~/.torrc with no $HOME set.
22248 - Fix a race bug in the unit tests.
22249 - Handle verified/unverified name collisions better when new
22250 routerinfo's arrive in a directory.
22251 - Sometimes routers were getting entered into the stats before
22252 we'd assigned their identity_digest. Oops.
22253 - Only pick and establish intro points after we've gotten a
22256 - AllowUnverifiedNodes config option to let circuits choose no-name
22257 routers in entry,middle,exit,introduction,rendezvous positions.
22258 Allow middle and rendezvous positions by default.
22259 - Add a man page for tor-resolve.
22262 Changes in version 0.0.7.3 - 2004-08-12
22263 o Stop dnsworkers from triggering an assert failure when you
22264 ask them to resolve the host "".
22267 Changes in version 0.0.8pre3 - 2004-08-09
22268 o Changes from 0.0.7.2:
22269 - Allow multiple ORs with same nickname in routerlist -- now when
22270 people give us one identity key for a nickname, then later
22271 another, we don't constantly complain until the first expires.
22272 - Remember used bandwidth (both in and out), and publish 15-minute
22273 snapshots for the past day into our descriptor.
22274 - You can now fetch $DIRURL/running-routers to get just the
22275 running-routers line, not the whole descriptor list. (But
22276 clients don't use this yet.)
22277 - When people mistakenly use Tor as an http proxy, point them
22278 at the tor-doc.html rather than the INSTALL.
22279 - Remove our mostly unused -- and broken -- hex_encode()
22280 function. Use base16_encode() instead. (Thanks to Timo Lindfors
22281 for pointing out this bug.)
22282 - Rotate onion keys every 12 hours, not every 2 hours, so we have
22283 fewer problems with people using the wrong key.
22284 - Change the default exit policy to reject the default edonkey,
22285 kazaa, gnutella ports.
22286 - Add replace_file() to util.[ch] to handle win32's rename().
22288 o Changes from 0.0.8preX:
22289 - Fix two bugs in saving onion keys to disk when rotating, so
22290 hopefully we'll get fewer people using old onion keys.
22291 - Fix an assert error that was making SocksPolicy not work.
22292 - Be willing to expire routers that have an open dirport -- it's
22293 just the authoritative dirservers we want to not forget.
22294 - Reject tor-resolve requests for .onion addresses early, so we
22295 don't build a whole rendezvous circuit and then fail.
22296 - When you're warning a server that he's unverified, don't cry
22297 wolf unpredictably.
22298 - Fix a race condition: don't try to extend onto a connection
22299 that's still handshaking.
22300 - For servers in clique mode, require the conn to be open before
22301 you'll choose it for your path.
22302 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
22303 end relay cell, etc.
22304 - Measure bandwidth capacity over the last 24 hours, not just 12
22305 - Bugfix: authoritative dirservers were making and signing a new
22306 directory for each client, rather than reusing the cached one.
22309 Changes in version 0.0.8pre2 - 2004-08-04
22310 o Changes from 0.0.7.2:
22312 - Check directory signature _before_ you decide whether you're
22313 you're running an obsolete version and should exit.
22314 - Check directory signature _before_ you parse the running-routers
22315 list to decide who's running or verified.
22316 - Bugfixes and features:
22317 - Check return value of fclose while writing to disk, so we don't
22318 end up with broken files when servers run out of disk space.
22319 - Log a warning if the user uses an unsafe socks variant, so people
22320 are more likely to learn about privoxy or socat.
22321 - Dirservers now include RFC1123-style dates in the HTTP headers,
22322 which one day we will use to better detect clock skew.
22324 o Changes from 0.0.8pre1:
22325 - Make it compile without warnings again on win32.
22326 - Log a warning if you're running an unverified server, to let you
22327 know you might want to get it verified.
22328 - Only pick a default nickname if you plan to be a server.
22331 Changes in version 0.0.8pre1 - 2004-07-23
22333 - Made our unit tests compile again on OpenBSD 3.5, and tor
22334 itself compile again on OpenBSD on a sparc64.
22335 - We were neglecting milliseconds when logging on win32, so
22336 everything appeared to happen at the beginning of each second.
22338 o Protocol changes:
22339 - 'Extend' relay cell payloads now include the digest of the
22340 intended next hop's identity key. Now we can verify that we're
22341 extending to the right router, and also extend to routers we
22342 hadn't heard of before.
22345 - Tor nodes can now act as relays (with an advertised ORPort)
22346 without being manually verified by the dirserver operators.
22347 - Uploaded descriptors of unverified routers are now accepted
22348 by the dirservers, and included in the directory.
22349 - Verified routers are listed by nickname in the running-routers
22350 list; unverified routers are listed as "$<fingerprint>".
22351 - We now use hash-of-identity-key in most places rather than
22352 nickname or addr:port, for improved security/flexibility.
22353 - To avoid Sybil attacks, paths still use only verified servers.
22354 But now we have a chance to play around with hybrid approaches.
22355 - Nodes track bandwidth usage to estimate capacity (not used yet).
22356 - ClientOnly option for nodes that never want to become servers.
22357 - Directory caching.
22358 - "AuthoritativeDir 1" option for the official dirservers.
22359 - Now other nodes (clients and servers) will cache the latest
22360 directory they've pulled down.
22361 - They can enable their DirPort to serve it to others.
22362 - Clients will pull down a directory from any node with an open
22363 DirPort, and check the signature/timestamp correctly.
22364 - Authoritative dirservers now fetch directories from other
22365 authdirservers, to stay better synced.
22366 - Running-routers list tells who's down also, along with noting
22367 if they're verified (listed by nickname) or unverified (listed
22369 - Allow dirservers to serve running-router list separately.
22370 This isn't used yet.
22371 - ORs connect-on-demand to other ORs
22372 - If you get an extend cell to an OR you're not connected to,
22373 connect, handshake, and forward the create cell.
22374 - The authoritative dirservers stay connected to everybody,
22375 and everybody stays connected to 0.0.7 servers, but otherwise
22376 clients/servers expire unused connections after 5 minutes.
22377 - When servers get a sigint, they delay 30 seconds (refusing new
22378 connections) then exit. A second sigint causes immediate exit.
22379 - File and name management:
22380 - Look for .torrc if no CONFDIR "torrc" is found.
22381 - If no datadir is defined, then choose, make, and secure ~/.tor
22383 - If torrc not found, exitpolicy reject *:*.
22384 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
22385 - If no nickname is defined, derive default from hostname.
22386 - Rename secret key files, e.g. identity.key -> secret_id_key,
22387 to discourage people from mailing their identity key to tor-ops.
22388 - Refuse to build a circuit before the directory has arrived --
22389 it won't work anyway, since you won't know the right onion keys
22391 - Try other dirservers immediately if the one you try is down. This
22392 should tolerate down dirservers better now.
22393 - Parse tor version numbers so we can do an is-newer-than check
22394 rather than an is-in-the-list check.
22395 - New socks command 'resolve', to let us shim gethostbyname()
22397 - A 'tor_resolve' script to access the socks resolve functionality.
22398 - A new socks-extensions.txt doc file to describe our
22399 interpretation and extensions to the socks protocols.
22400 - Add a ContactInfo option, which gets published in descriptor.
22401 - Publish OR uptime in descriptor (and thus in directory) too.
22402 - Write tor version at the top of each log file
22403 - New docs in the tarball:
22405 - Document that you should proxy your SSL traffic too.
22408 Changes in version 0.0.7.2 - 2004-07-07
22409 o A better fix for the 0.0.0.0 problem, that will hopefully
22410 eliminate the remaining related assertion failures.
22413 Changes in version 0.0.7.1 - 2004-07-04
22414 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
22415 since internally we use 0.0.0.0 to signify "not yet resolved".
22418 Changes in version 0.0.7 - 2004-06-07
22419 o Updated the man page to reflect the new features.
22422 Changes in version 0.0.7rc2 - 2004-06-06
22423 o Changes from 0.0.7rc1:
22424 - Make it build on Win32 again.
22425 o Changes from 0.0.6.2:
22426 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
22430 Changes in version 0.0.7rc1 - 2004-06-02
22432 - On sighup, we were adding another log without removing the first
22433 one. So log messages would get duplicated n times for n sighups.
22434 - Several cases of using a connection after we'd freed it. The
22435 problem was that connections that are pending resolve are in both
22436 the pending_resolve tree, and also the circuit's resolving_streams
22437 list. When you want to remove one, you must remove it from both.
22438 - Fix a double-mark-for-close where an end cell arrived for a
22439 resolving stream, and then the resolve failed.
22440 - Check directory signatures based on name of signer, not on whom
22441 we got the directory from. This will let us cache directories more
22444 - Crank up some of our constants to handle more users.
22447 Changes in version 0.0.7pre1 - 2004-06-02
22448 o Fixes for crashes and other obnoxious bugs:
22449 - Fix an epipe bug: sometimes when directory connections failed
22450 to connect, we would give them a chance to flush before closing
22452 - When we detached from a circuit because of resolvefailed, we
22453 would immediately try the same circuit twice more, and then
22454 give up on the resolve thinking we'd tried three different
22456 - Limit the number of intro circuits we'll attempt to build for a
22457 hidden service per 15-minute period.
22458 - Check recommended-software string *early*, before actually parsing
22459 the directory. Thus we can detect an obsolete version and exit,
22460 even if the new directory format doesn't parse.
22461 o Fixes for security bugs:
22462 - Remember which nodes are dirservers when you startup, and if a
22463 random OR enables his dirport, don't automatically assume he's
22464 a trusted dirserver.
22466 - Directory connections were asking the wrong poll socket to
22467 start writing, and not asking themselves to start writing.
22468 - When we detached from a circuit because we sent a begin but
22469 didn't get a connected, we would use it again the first time;
22470 but after that we would correctly switch to a different one.
22471 - Stop warning when the first onion decrypt attempt fails; they
22472 will sometimes legitimately fail now that we rotate keys.
22473 - Override unaligned-access-ok check when $host_cpu is ia64 or
22474 arm. Apparently they allow it but the kernel whines.
22475 - Dirservers try to reconnect periodically too, in case connections
22477 - Fix some memory leaks in directory servers.
22478 - Allow backslash in Win32 filenames.
22479 - Made Tor build complain-free on FreeBSD, hopefully without
22480 breaking other BSD builds. We'll see.
22482 - Doxygen markup on all functions and global variables.
22483 - Make directory functions update routerlist, not replace it. So
22484 now directory disagreements are not so critical a problem.
22485 - Remove the upper limit on number of descriptors in a dirserver's
22486 directory (not that we were anywhere close).
22487 - Allow multiple logfiles at different severity ranges.
22488 - Allow *BindAddress to specify ":port" rather than setting *Port
22489 separately. Allow multiple instances of each BindAddress config
22490 option, so you can bind to multiple interfaces if you want.
22491 - Allow multiple exit policy lines, which are processed in order.
22492 Now we don't need that huge line with all the commas in it.
22493 - Enable accept/reject policies on SOCKS connections, so you can bind
22494 to 0.0.0.0 but still control who can use your OP.
22497 Changes in version 0.0.6.2 - 2004-05-16
22498 o Our integrity-checking digest was checking only the most recent cell,
22499 not the previous cells like we'd thought.
22500 Thanks to Stefan Mark for finding the flaw!
22503 Changes in version 0.0.6.1 - 2004-05-06
22504 o Fix two bugs in our AES counter-mode implementation (this affected
22505 onion-level stream encryption, but not TLS-level). It turns
22506 out we were doing something much more akin to a 16-character
22507 polyalphabetic cipher. Oops.
22508 Thanks to Stefan Mark for finding the flaw!
22509 o Retire moria3 as a directory server, and add tor26 as a directory
22513 Changes in version 0.0.6 - 2004-05-02
22514 [version bump only]
22517 Changes in version 0.0.6rc4 - 2004-05-01
22518 o Update the built-in dirservers list to use the new directory format
22519 o Fix a rare seg fault: if a node offering a hidden service attempts
22520 to build a circuit to Alice's rendezvous point and fails before it
22521 reaches the last hop, it retries with a different circuit, but
22523 o Handle windows socket errors correctly.
22526 Changes in version 0.0.6rc3 - 2004-04-28
22527 o Don't expire non-general excess circuits (if we had enough
22528 circuits open, we were expiring rendezvous circuits -- even
22529 when they had a stream attached. oops.)
22530 o Fetch randomness from /dev/urandom better (not via fopen/fread)
22531 o Better debugging for tls errors
22532 o Some versions of openssl have an SSL_pending function that erroneously
22533 returns bytes when there is a non-application record pending.
22534 o Set Content-Type on the directory and hidserv descriptor.
22535 o Remove IVs from cipher code, since AES-ctr has none.
22536 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
22537 o We were using an array of length zero in a few places.
22538 o win32's gethostbyname can't resolve an IP to an IP.
22539 o win32's close can't close a socket.
22542 Changes in version 0.0.6rc2 - 2004-04-26
22543 o Fix a bug where we were closing tls connections intermittently.
22544 It turns out openssl keeps its errors around -- so if an error
22545 happens, and you don't ask about it, and then another openssl
22546 operation happens and succeeds, and you ask if there was an error,
22547 it tells you about the first error. Fun fun.
22548 o Fix a bug that's been lurking since 27 may 03 (!)
22549 When passing back a destroy cell, we would use the wrong circ id.
22550 'Mostly harmless', but still worth fixing.
22551 o Since we don't support truncateds much, don't bother sending them;
22552 just close the circ.
22553 o check for <machine/limits.h> so we build on NetBSD again (I hope).
22554 o don't crash if a conn that sent a begin has suddenly lost its circuit
22555 (this was quite rare).
22558 Changes in version 0.0.6rc1 - 2004-04-25
22559 o We now rotate link (tls context) keys and onion keys.
22560 o CREATE cells now include oaep padding, so you can tell
22561 if you decrypted them correctly.
22562 o Add bandwidthburst to server descriptor.
22563 o Directories now say which dirserver signed them.
22564 o Use a tor_assert macro that logs failed assertions too.
22567 Changes in version 0.0.6pre5 - 2004-04-18
22568 o changes from 0.0.6pre4:
22569 - make tor build on broken freebsd 5.2 installs
22570 - fix a failed assert when you try an intro point, get a nack, and try
22571 a second one and it works.
22572 - when alice uses a port that the hidden service doesn't accept,
22573 it now sends back an end cell (denied by exit policy). otherwise
22574 alice would just have to wait to time out.
22575 - fix another rare bug: when we had tried all the intro
22576 points for a hidden service, we fetched the descriptor
22577 again, but we left our introcirc thinking it had already
22578 sent an intro, so it kept waiting for a response...
22579 - bugfix: when you sleep your hidden-service laptop, as soon
22580 as it wakes up it tries to upload a service descriptor, but
22581 socketpair fails for some reason (localhost not up yet?).
22582 now we simply give up on that upload, and we'll try again later.
22583 i'd still like to find the bug though.
22584 - if an intro circ waiting for an ack dies before getting one, then
22586 - we were reusing stale service descriptors and refetching usable
22590 Changes in version 0.0.6pre4 - 2004-04-14
22591 o changes from 0.0.6pre3:
22592 - when bob fails to connect to the rendezvous point, and his
22593 circ didn't fail because of the rendezvous point itself, then
22594 he retries a couple of times
22595 - we expire introduction and rendezvous circs more thoroughly
22596 (sometimes they were hanging around forever)
22597 - we expire unattached rendezvous streams that have been around
22598 too long (they were sticking around forever).
22599 - fix a measly fencepost error that was crashing everybody with
22603 Changes in version 0.0.6pre3 - 2004-04-14
22604 o changes from 0.0.6pre2:
22605 - make hup work again
22606 - fix some memory leaks for dirservers
22607 - allow more skew in rendezvous descriptor timestamps, to help
22608 handle people like blanu who don't know what time it is
22609 - normal circs are 3 hops, but some rend/intro circs are 4, if
22610 the initiator doesn't get to choose the last hop
22611 - send acks for introductions, so alice can know whether to try
22613 - bob publishes intro points more correctly
22614 o changes from 0.0.5:
22615 - fix an assert trigger that's been plaguing us since the days
22616 of 0.0.2prexx (thanks weasel!)
22617 - retry stream correctly when we fail to connect because of
22618 exit-policy-reject (should try another) or can't-resolve-address
22619 (also should try another, because dns on random internet servers
22621 - when we hup a dirserver and we've *removed* a server from the
22622 approved-routers list, now we remove that server from the
22623 in-memory directories too
22626 Changes in version 0.0.6pre2 - 2004-04-08
22627 o We fixed our base32 implementation. Now it works on all architectures.
22630 Changes in version 0.0.6pre1 - 2004-04-08
22632 - Hidden services and rendezvous points are implemented. Go to
22633 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
22634 hidden services. (This only works via a socks4a proxy such as
22635 Privoxy, and currently it's quite slow.)
22638 Changes in version 0.0.5 - 2004-03-30
22639 [version bump only]
22642 Changes in version 0.0.5rc3 - 2004-03-29
22643 o Install torrc as torrc.sample -- we no longer clobber your
22645 o Re-enable recommendedversion checking (we broke it in rc2, oops)
22646 o Add in a 'notice' log level for things the operator should hear
22647 but that aren't warnings
22650 Changes in version 0.0.5rc2 - 2004-03-29
22651 o Hold socks connection open until reply is flushed (if possible)
22652 o Make exit nodes resolve IPs to IPs immediately, rather than asking
22653 the dns farm to do it.
22654 o Fix c99 aliasing warnings in rephist.c
22655 o Don't include server descriptors that are older than 24 hours in the
22657 o Give socks 'reject' replies their whole 15s to attempt to flush,
22658 rather than seeing the 60s timeout and assuming the flush had failed.
22659 o Clean automake droppings from the cvs repository
22662 Changes in version 0.0.5rc1 - 2004-03-28
22663 o Fix mangled-state bug in directory fetching (was causing sigpipes).
22664 o Only build circuits after we've fetched the directory: clients were
22665 using only the directory servers before they'd fetched a directory.
22666 This also means longer startup time; so it goes.
22667 o Fix an assert trigger where an OP would fail to handshake, and we'd
22668 expect it to have a nickname.
22669 o Work around a tsocks bug: do a socks reject when AP connection dies
22670 early, else tsocks goes into an infinite loop.
22673 Changes in version 0.0.4 - 2004-03-26
22674 o When connecting to a dirserver or OR and the network is down,
22678 Changes in version 0.0.3 - 2004-03-26
22679 o Warn and fail if server chose a nickname with illegal characters
22680 o Port to Solaris and Sparc:
22681 - include missing header fcntl.h
22682 - have autoconf find -lsocket -lnsl automatically
22683 - deal with hardware word alignment
22684 - make uname() work (solaris has a different return convention)
22685 - switch from using signal() to sigaction()
22686 o Preliminary work on reputation system:
22687 - Keep statistics on success/fail of connect attempts; they're published
22688 by kill -USR1 currently.
22689 - Add a RunTesting option to try to learn link state by creating test
22690 circuits, even when SocksPort is off.
22691 - Remove unused open circuits when there are too many.
22694 Changes in version 0.0.2 - 2004-03-19
22695 - Include strlcpy and strlcat for safer string ops
22696 - define INADDR_NONE so we compile (but still not run) on solaris
22699 Changes in version 0.0.2pre27 - 2004-03-14
22701 - Allow internal tor networks (we were rejecting internal IPs,
22702 now we allow them if they're set explicitly).
22703 - And fix a few endian issues.
22706 Changes in version 0.0.2pre26 - 2004-03-14
22708 - If a stream times out after 15s without a connected cell, don't
22709 try that circuit again: try a new one.
22710 - Retry streams at most 4 times. Then give up.
22711 - When a dirserver gets a descriptor from an unknown router, it
22712 logs its fingerprint (so the dirserver operator can choose to
22713 accept it even without mail from the server operator).
22714 - Inform unapproved servers when we reject their descriptors.
22715 - Make tor build on Windows again. It works as a client, who knows
22717 - Clearer instructions in the torrc for how to set up a server.
22718 - Be more efficient about reading fd's when our global token bucket
22719 (used for rate limiting) becomes empty.
22721 - Stop asserting that computers always go forward in time. It's
22723 - When we sent a cell (e.g. destroy) and then marked an OR connection
22724 expired, we might close it before finishing a flush if the other
22725 side isn't reading right then.
22726 - Don't allow dirservers to start if they haven't defined
22727 RecommendedVersions
22728 - We were caching transient dns failures. Oops.
22729 - Prevent servers from publishing an internal IP as their address.
22730 - Address a strcat vulnerability in circuit.c
22733 Changes in version 0.0.2pre25 - 2004-03-04
22735 - Put the OR's IP in its router descriptor, not its fqdn. That way
22736 we'll stop being stalled by gethostbyname for nodes with flaky dns,
22739 - If the user typed in an address that didn't resolve, the server
22743 Changes in version 0.0.2pre24 - 2004-03-03
22745 - Fix an assertion failure in dns.c, where we were trying to dequeue
22746 a pending dns resolve even if it wasn't pending
22747 - Fix a spurious socks5 warning about still trying to write after the
22748 connection is finished.
22749 - Hold certain marked_for_close connections open until they're finished
22750 flushing, rather than losing bytes by closing them too early.
22751 - Correctly report the reason for ending a stream
22752 - Remove some duplicate calls to connection_mark_for_close
22753 - Put switch_id and start_daemon earlier in the boot sequence, so it
22754 will actually try to chdir() to options.DataDirectory
22755 - Make 'make test' exit(1) if a test fails; fix some unit tests
22756 - Make tor fail when you use a config option it doesn't know about,
22757 rather than warn and continue.
22758 - Make --version work
22759 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
22762 Changes in version 0.0.2pre23 - 2004-02-29
22764 - Print a statement when the first circ is finished, so the user
22765 knows it's working.
22766 - If a relay cell is unrecognized at the end of the circuit,
22767 send back a destroy. (So attacks to mutate cells are more
22769 - New config option 'excludenodes' to avoid certain nodes for circuits.
22770 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
22771 so you can collect coredumps there.
22773 - Fix a bug in tls flushing where sometimes data got wedged and
22774 didn't flush until more data got sent. Hopefully this bug was
22775 a big factor in the random delays we were seeing.
22776 - Make 'connected' cells include the resolved IP, so the client
22777 dns cache actually gets populated.
22778 - Disallow changing from ORPort=0 to ORPort>0 on hup.
22779 - When we time-out on a stream and detach from the circuit, send an
22780 end cell down it first.
22781 - Only warn about an unknown router (in exitnodes, entrynodes,
22782 excludenodes) after we've fetched a directory.
22785 Changes in version 0.0.2pre22 - 2004-02-26
22787 - Servers publish less revealing uname information in descriptors.
22788 - More memory tracking and assertions, to crash more usefully when
22790 - If the default torrc isn't there, just use some default defaults.
22791 Plus provide an internal dirservers file if they don't have one.
22792 - When the user tries to use Tor as an http proxy, give them an http
22793 501 failure explaining that we're a socks proxy.
22794 - Dump a new router.desc on hup, to help confused people who change
22795 their exit policies and then wonder why router.desc doesn't reflect
22797 - Clean up the generic tor.sh init script that we ship with.
22799 - If the exit stream is pending on the resolve, and a destroy arrives,
22800 then the stream wasn't getting removed from the pending list. I
22801 think this was the one causing recent server crashes.
22802 - Use a more robust poll on OSX 10.3, since their poll is flaky.
22803 - When it couldn't resolve any dirservers, it was useless from then on.
22804 Now it reloads the RouterFile (or default dirservers) if it has no
22806 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
22807 many users don't even *have* a /usr/local/sbin/.
22810 Changes in version 0.0.2pre21 - 2004-02-18
22812 - There's a ChangeLog file that actually reflects the changelog.
22813 - There's a 'torify' wrapper script, with an accompanying
22814 tor-tsocks.conf, that simplifies the process of using tsocks for
22815 tor. It even has a man page.
22816 - The tor binary gets installed to sbin rather than bin now.
22817 - Retry streams where the connected cell hasn't arrived in 15 seconds
22818 - Clean up exit policy handling -- get the default out of the torrc,
22819 so we can update it without forcing each server operator to fix
22821 - Allow imaps and pop3s in default exit policy
22823 - Prevent picking middleman nodes as the last node in the circuit
22826 Changes in version 0.0.2pre20 - 2004-01-30
22828 - We now have a deb package, and it's in debian unstable. Go to
22829 it, apt-getters. :)
22830 - I've split the TotalBandwidth option into BandwidthRate (how many
22831 bytes per second you want to allow, long-term) and
22832 BandwidthBurst (how many bytes you will allow at once before the cap
22833 kicks in). This better token bucket approach lets you, say, set
22834 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
22835 performance while not exceeding your monthly bandwidth quota.
22836 - Push out a tls record's worth of data once you've got it, rather
22837 than waiting until you've read everything waiting to be read. This
22838 may improve performance by pipelining better. We'll see.
22839 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
22840 from failed circuits (if they haven't been connected yet) and attach
22842 - Expire old streams that haven't managed to connect. Some day we'll
22843 have them reattach to new circuits instead.
22846 - Fix several memory leaks that were causing servers to become bloated
22848 - Fix a few very rare assert triggers. A few more remain.
22849 - Setuid to User _before_ complaining about running as root.
22852 Changes in version 0.0.2pre19 - 2004-01-07
22854 - Fix deadlock condition in dns farm. We were telling a child to die by
22855 closing the parent's file descriptor to him. But newer children were
22856 inheriting the open file descriptor from the parent, and since they
22857 weren't closing it, the socket never closed, so the child never read
22858 eof, so he never knew to exit. Similarly, dns workers were holding
22859 open other sockets, leading to all sorts of chaos.
22860 - New cleaner daemon() code for forking and backgrounding.
22861 - If you log to a file, it now prints an entry at the top of the
22862 logfile so you know it's working.
22863 - The onionskin challenge length was 30 bytes longer than necessary.
22864 - Started to patch up the spec so it's not quite so out of date.
22867 Changes in version 0.0.2pre18 - 2004-01-02
22869 - Fix endian issues with the 'integrity' field in the relay header.
22870 - Fix a potential bug where connections in state
22871 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
22874 Changes in version 0.0.2pre17 - 2003-12-30
22876 - Made --debuglogfile (or any second log file, actually) work.
22877 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
22878 adversary could force us into an infinite loop.
22881 - Each onionskin handshake now includes a hash of the computed key,
22882 to prove the server's identity and help perfect forward secrecy.
22883 - Changed cell size from 256 to 512 bytes (working toward compatibility
22885 - Changed cell length to 2 bytes, and moved it to the relay header.
22886 - Implemented end-to-end integrity checking for the payloads of
22888 - Separated streamid from 'recognized' (otherwise circuits will get
22889 messed up when we try to have streams exit from the middle). We
22890 use the integrity-checking to confirm that a cell is addressed to
22892 - Randomize the initial circid and streamid values, so an adversary who
22893 breaks into a node can't learn how many circuits or streams have
22897 Changes in version 0.0.2pre16 - 2003-12-14
22899 - Fixed a bug that made HUP trigger an assert
22900 - Fixed a bug where a circuit that immediately failed wasn't being
22901 counted as a failed circuit in counting retries.
22904 - Now we close the circuit when we get a truncated cell: otherwise we're
22905 open to an anonymity attack where a bad node in the path truncates
22906 the circuit and then we open streams at him.
22907 - Add port ranges to exit policies
22908 - Add a conservative default exit policy
22909 - Warn if you're running tor as root
22910 - on HUP, retry OR connections and close/rebind listeners
22911 - options.EntryNodes: try these nodes first when picking the first node
22912 - options.ExitNodes: if your best choices happen to include any of
22913 your preferred exit nodes, you choose among just those preferred
22915 - options.ExcludedNodes: nodes that are never picked in path building
22918 Changes in version 0.0.2pre15 - 2003-12-03
22919 o Robustness and bugfixes:
22920 - Sometimes clients would cache incorrect DNS resolves, which would
22921 really screw things up.
22922 - An OP that goes offline would slowly leak all its sockets and stop
22924 - A wide variety of bugfixes in exit node selection, exit policy
22925 handling, and processing pending streams when a new circuit is
22927 - Pick nodes for a path only from those the directory says are up
22928 - Choose randomly from all running dirservers, not always the first one
22929 - Increase allowed http header size for directory fetch.
22930 - Stop writing to stderr (if we're daemonized it will be closed).
22931 - Enable -g always, so cores will be more useful to me.
22932 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
22935 - Wrote a man page. It lists commonly used options.
22938 - Change default loglevel to warn.
22939 - Make PidFile default to null rather than littering in your CWD.
22940 - OnionRouter config option is now obsolete. Instead it just checks
22942 - Moved to a single unified torrc file for both clients and servers.
22945 Changes in version 0.0.2pre14 - 2003-11-29
22946 o Robustness and bugfixes:
22947 - Force the admin to make the DataDirectory himself
22948 - to get ownership/permissions right
22949 - so clients no longer make a DataDirectory and then never use it
22950 - fix bug where a client who was offline for 45 minutes would never
22951 pull down a directory again
22952 - fix (or at least hide really well) the dns assert bug that was
22953 causing server crashes
22954 - warnings and improved robustness wrt clockskew for certs
22955 - use the native daemon(3) to daemonize, when available
22956 - exit if bind() fails
22957 - exit if neither socksport nor orport is defined
22958 - include our own tor_timegm (Win32 doesn't have its own)
22959 - bugfix for win32 with lots of connections
22960 - fix minor bias in PRNG
22961 - make dirserver more robust to corrupt cached directory
22964 - Wrote the design document (woo)
22966 o Circuit building and exit policies:
22967 - Circuits no longer try to use nodes that the directory has told them
22969 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
22970 bitcounts (18.0.0.0/8).
22971 - Make AP connections standby for a circuit if no suitable circuit
22972 exists, rather than failing
22973 - Circuits choose exit node based on addr/port, exit policies, and
22974 which AP connections are standing by
22975 - Bump min pathlen from 2 to 3
22976 - Relay end cells have a payload to describe why the stream ended.
22977 - If the stream failed because of exit policy, try again with a new
22979 - Clients have a dns cache to remember resolved addresses.
22980 - Notice more quickly when we have no working circuits
22983 - APPort is now called SocksPort
22984 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
22986 - RecommendedVersions is now a config variable rather than
22987 hardcoded (for dirservers)
22988 - Reloads config on HUP
22989 - Usage info on -h or --help
22990 - If you set User and Group config vars, it'll setu/gid to them.
22993 Changes in version 0.0.2pre13 - 2003-10-19
22994 o General stability:
22995 - SSL_write no longer fails when it returns WANTWRITE and the number
22996 of bytes in the buf has changed by the next SSL_write call.
22997 - Fix segfault fetching directory when network is down
22998 - Fix a variety of minor memory leaks
22999 - Dirservers reload the fingerprints file on HUP, so I don't have
23000 to take down the network when I approve a new router
23001 - Default server config file has explicit Address line to specify fqdn
23004 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
23005 - Make listener connections not ever alloc bufs
23007 o Autoconf improvements:
23008 - don't clobber an external CFLAGS in ./configure
23009 - Make install now works
23010 - create var/lib/tor on make install
23011 - autocreate a tor.sh initscript to help distribs
23012 - autocreate the torrc and sample-server-torrc with correct paths
23014 o Log files and Daemonizing now work:
23015 - If --DebugLogFile is specified, log to it at -l debug
23016 - If --LogFile is specified, use it instead of commandline
23017 - If --RunAsDaemon is set, tor forks and backgrounds on startup